diff --git a/translations/de-DE/content/actions/creating-actions/about-actions.md b/translations/de-DE/content/actions/creating-actions/about-actions.md index 4388166f979cd..5290b4c566ab3 100644 --- a/translations/de-DE/content/actions/creating-actions/about-actions.md +++ b/translations/de-DE/content/actions/creating-actions/about-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 4ad7b6a49e7b0..f9ba9a461bed8 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -93,7 +94,7 @@ Before you begin, you'll create a {% data variables.product.product_name %} repo git push ``` -1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)." +1. From your terminal, add a tag. This example uses a tag called `v1`. Weitere Informationen finden Sie unter „[Informationen zu Aktionen](/actions/creating-actions/about-actions#using-release-management-for-actions)“. ```shell git tag -a -m "Description of this release" v1 diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md index 37c36fd7d09a4..d3404b356be37 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md index d0e537f72bdb5..022e09d5298a7 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md index bfb8a7a6295de..d6a161918988c 100644 --- a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] Um `args` aus der Metadaten-Datei der Aktion an einen Docker Container zu übergeben, der die _exec_-Form im `ENTRYPOINT` verwendet, empfehlen wir, ein Shell-Skript namens `entrypoint.sh` zu erstellen und dieses von der `ENTRYPOINT`-Anweisung aus anrufen: ##### Beispiel *Dockerfile* -``` -# Container-Image, das Deinen Code ausführt +``` +# Container image that runs your code FROM debian:9.5-slim -# Kopiert Deine Code-Datei aus Deinem Aktions-Repository in den Dateisystem-Pfad `/` des Containers +# Copies your code file from your action repository to the filesystem path `/` of the container COPY entrypoint.sh /entrypoint.sh -# Ruft `entrypoint.sh` wenn der Docker-Container hochfaehrt +# Executes `entrypoint.sh` when the Docker container starts up ENTRYPOINT ["/entrypoint.sh"] ``` @@ -78,14 +79,14 @@ Mit dem obigen Dockerfile-Beispiel sendet {% data variables.product.product_name ``` sh #!/bin/sh -# `$*` erweitert die in einem `array` gelieferten `args` individuell -# oder teilt einen String `args` an Whitespaces in Teil-Strings auf. +# `$*` expands the `args` supplied in an `array` individually +# or splits `args` in a string separated by whitespace. sh -c "echo $*" ``` Dein Code muss ausführbar sein. Stelle sicher, dass die Datei `entrypoint.sh` die Berechtigunge `execute` hat, bevor Du sie in einem Workflow verwendest. Du kannst die Berechtigung von Deinem Terminal aus mit diesem Befehl ändern: ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` Wenn ein `ENTRYPOINT`-Shell-Skript nicht ausführbar ist, erhältst Du einen Fehler, der ungefähr so aussieht: diff --git a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 2cc9deb2121b6..7066aa27b02e4 100644 --- a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -103,16 +104,16 @@ outputs: {% raw %} ```yaml -Outputs: - Zufallszahl: - Beschreibung: "Zufallszahl" - Wert:{{ steps.random-number-generator.outputs.random-id }} -läuft: - mit: "composite" - Schritten: - - id: zuzufälliger Zahlengenerator - ausführen: echo "::set-output name=random-id::'(echo $RANDOM)" - Shell: bash +outputs: + random-number: + description: "Random number" + value: ${{ steps.random-number-generator.outputs.random-id }} +runs: + using: "composite" + steps: + - id: random-number-generator + run: echo "::set-output name=random-id::$(echo $RANDOM)" + shell: bash ``` {% endraw %} @@ -211,22 +212,22 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern: {% raw %} ```yaml -läuft: - mit: "composite" - Schritte: - - ausführen:{{ github.action_path }}/test/script.sh - Shell: bash +runs: + using: "composite" + steps: + - run: ${{ github.action_path }}/test/script.sh + shell: bash ``` {% endraw %} Alternatively, you can use `$GITHUB_ACTION_PATH`: ```yaml -läuft: - verwenden: "composite" - Schritte: - - ausführen: $GITHUB_ACTION_PATH/script.sh - Shell: bash +runs: + using: "composite" + steps: + - run: $GITHUB_ACTION_PATH/script.sh + shell: bash ``` For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". @@ -258,7 +259,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### Beispiel für die Nutzung eines Dockerfiles in Deinem Repository ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -266,9 +267,9 @@ runs: #### Beispiel zur Nutzung des öffentlichen Docker-Registry-Containers ```yaml -läuft: - mit: 'docker' - Image: 'docker://debian:stretch-slim' +runs: + using: 'docker' + image: 'docker://debian:stretch-slim' ``` #### `runs.using` diff --git a/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index b555e2cb21284..a453885d6c094 100644 --- a/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. diff --git a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md index 6d1b3974b91f8..bfc443e25e67a 100644 --- a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/about-continuous-integration.md b/translations/de-DE/content/actions/guides/about-continuous-integration.md index 937a8a60fa56f..276fb3a4ea200 100644 --- a/translations/de-DE/content/actions/guides/about-continuous-integration.md +++ b/translations/de-DE/content/actions/guides/about-continuous-integration.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md index 31dcbc4d9846c..0a74fc42edc6b 100644 --- a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/about-service-containers.md b/translations/de-DE/content/actions/guides/about-service-containers.md index 5c98fde1e6c3e..ec29114eef892 100644 --- a/translations/de-DE/content/actions/guides/about-service-containers.md +++ b/translations/de-DE/content/actions/guides/about-service-containers.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md index dce32aa29859d..0ba1f17391af7 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md index 08b9be1fb7a8e..3d713bc131492 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md index d22fdc1c4b773..25029c9c1ae40 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-net.md b/translations/de-DE/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..763ac81bedf34 --- /dev/null +++ b/translations/de-DE/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Building and testing .NET +intro: You can create a continuous integration (CI) workflow to build and test your .NET project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Einführung + +This guide shows you how to build, test, and publish a .NET package. + +{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners). + +### Vorrausetzungen + +You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. Weitere Informationen findest Du unter „[Workflow Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." + +We recommend that you have a basic understanding of the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn). + +### Starting with the .NET workflow template + +{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet). + +Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein. + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Specifying a .NET version + +To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. + +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Using multiple .NET versions + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Using a specific .NET version + +You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### Abhängigkeiten installieren + +{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Abhängigkeiten „cachen“ (zwischenspeichern) + +You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package. + +For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project. + +{% endnote %} + +{% endif %} + +### Deinen Code bauen und testen + +Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deinen Code zu erstellen und zu testen. This example demonstrates how to use `dotnet build` and `dotnet test` in a job: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### Workflow-Daten als Artefakte paketieren + +After a workflow completes, you can upload the resulting artifacts for analysis. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. The following example demonstrates how you can use the `upload-artifact` action to upload test results. + +Weitere Informationen findest Du unter "[Workflow-Daten mittels Artefakten persistieren](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### In Paket-Registries veröffentlichen + +You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md index b3830e286f021..fa5b29c599fb6 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +37,11 @@ Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ Der einfachste Weg, eine Node.js-Version anzugeben, ist die Aktion `setup-node` Die Aktion `setup-node` nimmt eine Node.js-Version als Eingabe und konfiguriert diese Version auf dem Runner. Die Aktion `setup-node` findet auf jedem Runner eine bestimmte Version von Node.js aus dem Tools-Cache und legt die notwendigen Binärdateien im `PATH` ab, wo sie für den Rest des Jobs bestehen bleiben. Für Node.js mit {% data variables.product.prodname_actions %} wird empfohlen, die Aktion `setup-node` zu verwenden, weil dadurch über verschiedenen Runner und verschiedenen Versionen von Node.js hinweg ein konsistentes Verhalten sicherstellt wird. Wenn Du einen selbst gehosteten Runner verwendest, musst Du Node.js installieren und zum `PATH` hinzufügen. -Die Vorlage enthält eine Matrix-Strategie, die Deinen Code mit drei Node.js-Versionen baut und testet: 8.x, 10.x und 12.x. Das 'x' ist ein Platzhalterzeichen, für das neueste Minor- und Patch-Release des jeweiligen Major-Releases steht. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Jede Version von Node.js, die im Array `node-version` festgelegt ist, erstellt einen Job, der die gleichen Schritte ausführt. +The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Jede Version von Node.js, die im Array `node-version` festgelegt ist, erstellt einen Job, der die gleichen Schritte ausführt. Jeder Job in der Matrix kann mithilfe des `Matrix`-Kontexts auf den im Array `node-version` definierten Wert zugreifen. Die Aktion `setup-node` verwendet den Kontext als Eingabe für `node-version`. Die Aktion `setup-node` konfiguriert jeden Job mit einer anderen Node.js-Version bevor sie den Code baut und testet. Weitere Informationen zu Matrix-Strategien und Kontexten findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)“ und „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. @@ -77,7 +80,7 @@ Jeder Job in der Matrix kann mithilfe des `Matrix`-Kontexts auf den im Array `no ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} 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 41224c77d2b36..2e398c4b81b06 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 @@ -7,6 +7,7 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-python.md b/translations/de-DE/content/actions/guides/building-and-testing-python.md index 116de816ed359..f8f785f49063c 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-python.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-python.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -122,7 +123,7 @@ jobs: #### Eine bestimmten Python-Version verwenden -Du kannst eine bestimmte Version von Python konfigurieren, For example, 3.8. Alternativ kannst Du auch Syntax für semantische Versionierung verwenden, um das neuste Minor Release zu erhalten. Dieses Beispiel verwendet das neueste Minor Release von Python 3. +Du kannst eine bestimmte Version von Python konfigurieren, For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. Dieses Beispiel verwendet das neueste Minor Release von Python 3. {% raw %} ```yaml diff --git a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md index 9a4f590d679ab..92c0146bc6e35 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 9c5646ca31a10..aa8068a2077f5 100644 --- a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: 'tutorial' --- ### Informationen zum Zwischenspeichern von Workflow-Abhängigkeiten diff --git a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md index 11f08f5217d69..dd87337ef7355 100644 --- a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/creating-redis-service-containers.md b/translations/de-DE/content/actions/guides/creating-redis-service-containers.md index dc950efcda0ab..e121a41e5ffe1 100644 --- a/translations/de-DE/content/actions/guides/creating-redis-service-containers.md +++ b/translations/de-DE/content/actions/guides/creating-redis-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/index.md b/translations/de-DE/content/actions/guides/index.md index 71541c512f14c..c432c2ebb3764 100644 --- a/translations/de-DE/content/actions/guides/index.md +++ b/translations/de-DE/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Creating custom continuous integration workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous integration (CI) workflows that build and test projects written in different programming languages. - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### Creating custom continuous deployment workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous deployment (CD) workflows that deploy projects to a number of cloud partner ecosystems. - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### Publishing software packages - -You can automate publishing software packages as part your continuous delivery (CD) workflow. Packages can be published to any package host and to {% data reusables.gated-features.packages %}. - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### Workflow-Daten speichern und zwischenspeichern - -Abhängigkeiten zwischenspeichern und Artefakte speichern, um Deinen Workflow effizienter ablaufen zu lassen. - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### Using service containers in a workflow - -Connect services to your workflow using service containers. - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/de-DE/content/actions/guides/publishing-docker-images.md b/translations/de-DE/content/actions/guides/publishing-docker-images.md index 9b4ec5ef26e0b..c987e76b81246 100644 --- a/translations/de-DE/content/actions/guides/publishing-docker-images.md +++ b/translations/de-DE/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md index d2478ac17e951..9b36a08e0c799 100644 --- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md index d676a182f73f6..5eb7aa29d7a24 100644 --- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} 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 ace0c5b58821e..4eb37d6e8bd5c 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -87,9 +88,28 @@ always-auth=true Jedes Mal, wenn Du ein neues Release erstellst, kannst Du einen Workflow anstoßen, um Dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel läuft jedes Mal, wenn das Ereignis `release` vom Typ `created` auftritt. Der Workflow veröffentlicht das Paket in {% data variables.product.prodname_registry %} , wenn die CI-Tests bestanden wurden. -Standardmäßig veröffentlicht die {% data variables.product.prodname_registry %} ein Paket in dem Repository auf {% data variables.product.prodname_dotcom %}, das Du im Feld `name` der Datei *package.json* angibst. Ein Paket namens `@my-org/test` würde beispielsweise im Repository `my-org/test` auf {% data variables.product.prodname_dotcom %} veröffentlicht. Weitere Informationen finden Sie unter [„`npm-scope`“ (npm-Gültigkeitsbereich)](https://docs.npmjs.com/misc/scope) in der npm-Dokumentation. +#### Configuring the destination repository -Um authentifizierte Vorgänge für die Registry {% data variables.product.prodname_registry %} in Deinem Workflow kannst Du den `GITHUB_TOKEN` verwenden. Der `GITHUB_TOKEN` existiert standardmäßig in Deinem Repository und hat Lese- und Schreibrechte für Pakete in dem Repository, in dem der Workflow läuft. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“. +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. + +However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Authenticating to the destination repository + +To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." + +If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +#### Example workflow Dieses Beispiel speichert das Geheimnis `GITHUB_TOKEN` in der Umgebungsvariablen `NODE_AUTH_TOKEN`. Wenn die Aktion `setup-node` eine Datei *.npmrc* erzeugt, referenziert sie das Token aus der Umgebungsvariable `NODE_AUTH_TOKEN`. 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 3e47530f79a9a..2959a60a934d9 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md index f3b152a41811e..5f55719cb2fa0 100644 --- a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index cb99f1f536321..2e52517e8145d 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index d842ec2ab113e..9077336371d8b 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,11 +7,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +Du kannst einen selbst-gehosteten Runner zu {{ site.data.variables.product.prodname_actions }} hinzufügen. + +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. + For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% warning %} @@ -44,6 +49,8 @@ Du kannst selbst-gehostete Runner auf Organisationsebene hinzufügen, wo sie ver {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### Adding a self-hosted runner to an enterprise You can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. @@ -62,3 +69,13 @@ To add a self-hosted runner at the enterprise level of 1. Click **Add new**, then click **New runner**. New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Making enterprise runners available to repositories + +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. + +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. + +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index 550739f07e0cc..ce89a29489494 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 30fe4c80a312a..43197fc6f8a01 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 0da2809fc0c64..e9e6c495a12a3 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index da2421c07b107..b72add66798fc 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index c42ffba1c9896..d4a3eaaa3f3ab 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 8ccc6c9ee6df2..f246f40c54bec 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,6 +4,7 @@ intro: Mit Labels kannst Du Deine selbst-gehosteten Runner nach ihren Eigenschaf versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 760e31a44bf4a..2d324d5f3f155 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md index eaaa18463e911..dc998f2abfc35 100644 --- a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,6 +5,7 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md index cb3484592f444..5014f264916be 100644 --- a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -76,7 +77,7 @@ Schritte: #### Using branches -Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`: +Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`: ```yaml steps: 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 9d9e77a00f094..12d906bf92c13 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 @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md index 0107907fab748..fa4f83f75e1f6 100644 --- a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md @@ -5,6 +5,7 @@ intro: 'This guide shows you how to use the advanced features of {% data variabl versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -154,6 +155,15 @@ For more information, see ["Using labels with self-hosted runners](/actions/hos You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." {% endif %} +### Verwenden einer Workflowvorlage + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. Wenn Ihr Repository bereits über vorhandene Workflows verfügt: Klicken Sie in der linken oberen Ecke auf **Neuer Workflow**. ![Erstelle einen neuen Workflow](/assets/images/help/repository/actions-new-workflow.png) +1. Klicke unter dem Namen der zu verwendenden Vorlage auf **Set up this workflow** (Workflow einrichten). ![Einrichten dieses Workflows](/assets/images/help/settings/actions-create-starter-workflow.png) + ### Nächste Schritte: To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 49502318782ad..7b7a59aac1fcc 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -324,4 +325,3 @@ jobs: Aktionen zur Verwendung in Deinem Workflow findest du entweder auf dem [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) oder Du kannst eigene Aktionen erstellen. For more information, see "[Creating actions](/actions/creating-actions)." - diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 3c3851b9fabc6..0a43eadf823fa 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 683f5152ed1ae..038f98e77dab0 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,6 +4,7 @@ intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share sev versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index be29098f280bc..d94f5ca2749a9 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -166,7 +167,7 @@ Jenkins-Pipeline maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Jenkins-Pipeline needs: job1 job3: needs: [job1, job2] - + ``` diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index a026ce8b6ea0c..a88b435055c0c 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- ### Einführung diff --git a/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 5981b685d154d..53a5a74c032ad 100644 --- a/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 79410dd69d63e..90fe19e2a82c9 100644 --- a/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -31,11 +32,11 @@ In diesem Verfahren wird veranschaulicht, wie eine Workflowvorlage und eine Meta Diese Datei mit dem Namen `octo-organization-ci.yml` veranschaulicht beispielsweise einen grundlegenden Workflow. ```yaml - Name: Octo Organization CI + name: Octo Organization CI on: push: - branch: [ $default-branch ] + branches: [ $default-branch ] pull_request: branches: [ $default-branch ] @@ -44,10 +45,10 @@ In diesem Verfahren wird veranschaulicht, wie eine Workflowvorlage und eine Meta runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. Erstellen Sie eine Metadatendatei im `Workflow-Vorlagen` Verzeichnis. Die Metadatendatei muss denselben Namen wie die Workflowdatei haben, aber anstelle der Erweiterung `.yml` muss sie mit `.properties.json`angehängt werden. Diese Datei mit dem Namen `octo-organization-ci.properties.json enthält` beispielsweise die Metadaten für eine Workflowdatei mit dem Namen `octo-organization-ci.yml`: ```yaml @@ -75,7 +76,7 @@ Um eine weitere Workflowvorlage hinzuzufügen, fügen Sie Ihre Dateien `Workflow ![Workflow-Vorlagendateien](/assets/images/help/images/workflow-template-files.png) -### Verwenden einer Workflowvorlage +### Using a workflow template from your organization In diesem Verfahren wird veranschaulicht, wie ein Mitglied Ihrer Organisation eine Workflowvorlage finden und verwenden kann, um einen neuen Workflow zu erstellen. Die Workflowvorlagen einer Organisation können von jedem Benutzer verwendet werden, der Mitglied der Organisation ist. diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 5d97596d00993..5aa7046bab34d 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -66,9 +66,9 @@ Committing the workflow file in your repository triggers the `push` event and ru {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Nächste Schritte: @@ -120,7 +120,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workfow you want to run. +1. In the left sidebar, click the workflow you want to run. ![Select say hello job](/assets/images/help/repository/say-hello-job.png) 1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow. ![Trigger the manual workflow](/assets/images/help/repository/manual-workflow-trigger.png) @@ -131,9 +131,9 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o 1. In the workflow logs, expand the 'Run echo "Hello World!"' section. ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Next steps diff --git a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md index e53cad90c5fc8..ea04f4ed54479 100644 --- a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,9 +75,13 @@ Bei der Eigenschaftsdereferenzierungs-Syntax muss der Eigenschaftsname - mit `a-Z` oder `_` beginnen, - mit `a-Z`, `0-9`, `-` oder `_` weitergehen. +#### Determining when to use contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### `github`-Kontext -Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereignis, das den Lauf ausgelöst hat. Sie können die meisten `github`-Kontextdaten in Umgebungsvariablen lesen. Weitere Informationen über Umgebungsvariablen findest Du unter „[Umgebungsvariablen verwenden](/actions/automating-your-workflow-with-github-actions/using-environment-variables)“. +Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereignis, das den Lauf ausgelöst hat. Du kannst die meisten `github`-Kontextdaten in Umgebungsvariablen lesen. Weitere Informationen über Umgebungsvariablen findest Du unter „[Umgebungsvariablen verwenden](/actions/automating-your-workflow-with-github-actions/using-environment-variables)“. {% data reusables.github-actions.github-context-warning %} @@ -107,15 +111,14 @@ Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereigni Der `env`-Kontext enthält Umgebungsvariablen, die in einem Workflow, Job oder Schritt gesetzt wurden. Weitere Informationen über das Setzen von Umgebungsvariablen in Deinem Workflow findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)“. -Mit der Syntax für den `env`-Kontext kannst Du den Wert einer Umgebungsvariable in Deiner Workflow-Datei verwenden. Wenn Du den Wert einer Umgebungsvariable innerhalb eines Runners verwenden willst, dann verwende die normale Methode des Runner-Betriebssystems zum Lesen von Umgebungsvariablen. +Mit der Syntax für den `env`-Kontext kannst Du den Wert einer Umgebungsvariable in Deiner Workflow-Datei verwenden. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. Weitere Informationen zur Syntax für Schritte findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)“. -Du kannst den `env`-Kontext nur im Wert der Schlüssel `with` und `name` verwenden oder in der `if`-Bedingung eines Schritts. Weitere Informationen zur Syntax für Schritte findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)“. +Wenn Du den Wert einer Umgebungsvariable innerhalb eines Runners verwenden willst, dann verwende die normale Methode des Runner-Betriebssystems zum Lesen von Umgebungsvariablen. | Name der Eigenschaft | Typ | Beschreibung | | ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | `env` | `Objekt` | Dieser Kontext ändert sich bei jedem Schritt in einem Auftrag. Du kannst bei jedem Schritt in einem Auftrag auf diesen Kontext zugreifen. | -| `env.` | `string` | Der Wert einer bestimmten Umgebungsvariable. | - +| `env.` | `string` | Der Wert einer bestimmten Umgebungsvariable. | #### `job`-Kontext @@ -135,7 +138,7 @@ Der `job`-Kontext enthält Informationen zum gerade ausgeführten Auftrag. #### `steps`-Kontext -Der `steps`-Kontext enthält Informationen zu den Schritten im aktuellen Auftrag, die bereits ausgeführt wurden. +Der `steps`-Kontext enthält Informationen zu den Schritten im aktuellen Job, die bereits ausgeführt wurden. | Name der Eigenschaft | Typ | Beschreibung | | --------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -168,7 +171,7 @@ Der `needs`-Kontext enthält Ausgaben von allen Jobs, die als Abhängigkeit des #### Beispiel für die Ausgabe von Kontextinformationen in der Protokolldatei -Mit dem folgenden Beispiel einer Workflow-Datei können Sie die Informationen prüfen, auf die in den einzelnen Kontexten zugegriffen werden kann. +Mit dem folgenden Beispiel einer Workflow-Datei kannst Du die Informationen einsehen, auf die in den einzelnen Kontexten zugegriffen werden kann. {% data reusables.github-actions.github-context-warning %} @@ -269,7 +272,7 @@ env: ### Funktionen -{% data variables.product.prodname_dotcom %} bietet integrierte Funktionen, die Sie in Ausdrücken verwenden können. Manche Funktionen übergeben Werte an einen String, um Vergleiche durchzuführen. {% data variables.product.prodname_dotcom %} übergibt Datentypen anhand der folgenden Umwandlungen an einen String: +{% data variables.product.prodname_dotcom %} bietet integrierte Funktionen, die Du in Ausdrücken verwenden kannst. Manche Funktionen verwandeln Werte an einen String, um Vergleiche durchzuführen. {% data variables.product.prodname_dotcom %} verwandelt Daten verschiedener Typen folgendermaßen in einen String: | Typ | Ergebnis | | ------- | ------------------------------------------------- | @@ -283,7 +286,7 @@ env: `contains( search, item )` -Gibt `true` zurück, wenn der `item` in `search` enthalten ist. Wenn `search` ein Array ist, gibt diese Funktion `true` zurück, wenn der `item` ein Element im Array ist. Wenn `search` ein String ist, gibt diese Funktion `true` zurück, wenn der `item` ein Teilstring von `search` ist. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Übergibt Werte an einen String. +Gibt `true` zurück, wenn der `item` in `search` enthalten ist. Wenn `search` ein Array ist, gibt diese Funktion `true` zurück, wenn der `item` ein Element im Array ist. Wenn `search` ein String ist, gibt diese Funktion `true` zurück, wenn der `item` ein Teilstring von `search` ist. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Wandelt Werte in einen String um. ##### Beispiel mit einem Array @@ -297,7 +300,7 @@ Gibt `true` zurück, wenn der `item` in `search` enthalten ist. Wenn `search` ei `startsWith( searchString, searchValue )` -Gibt `true` zurück, wenn der `searchString` mit `searchValue` beginnt. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Übergibt Werte an einen String. +Gibt `true` zurück, wenn der `searchString` mit `searchValue` beginnt. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Wandelt Werte in einen String um. ##### Beispiel @@ -307,7 +310,7 @@ Gibt `true` zurück, wenn der `searchString` mit `searchValue` beginnt. Bei dies `endsWith( searchString, searchValue )` -Gibt `true` zurück, wenn der `searchString` mit `searchValue` endet. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Übergibt Werte an einen String. +Gibt `true` zurück, wenn der `searchString` mit `searchValue` endet. Bei dieser Funktion wird die Groß- und Kleinschreibung nicht berücksichtigt. Wandelt Werte in einen String um. ##### Beispiel @@ -317,7 +320,7 @@ Gibt `true` zurück, wenn der `searchString` mit `searchValue` endet. Bei dieser `format( string, replaceValue0, replaceValue1, ..., replaceValueN)` -Ersetzt die Werte im `string` durch die Variable `replaceValueN`. Variablen im `string` werden mit der `{N}`-Syntax festgelegt, wobei `N` eine Ganzzahl ist. Sie müssen mindestens einen `replaceValue` und `string` festlegen. Sie können eine unbegrenzte Anzahl an Variablen (`replaceValueN`) verwenden. Maskieren Sie geschweifte Klammern mit doppelten Klammern. +Ersetzt die Werte im `string` durch die Variable `replaceValueN`. Variablen im `string` werden mit der `{N}`-Syntax festgelegt, wobei `N` eine Ganzzahl ist. Du musst mindestens einen `replaceValue` und `string` festlegen. Du kannst eine unbegrenzte Anzahl an Variablen (`replaceValueN`) verwenden. Maskiere geschweifte Klammern mit doppelten Klammern. ##### Beispiel @@ -339,7 +342,7 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `join( array, optionalSeparator )` -Der Wert für `array` kann ein Array oder ein String sein. Alle Werte im `array` werden in einem String zusammengeführt. Wenn Du `optionalSeparator` angibst, wird er zwischen den verketteten Werten eingefügt. Andernfalls wird der Standard-Trennzeichen `,` verwendet. Übergibt Werte an einen String. +Der Wert für `array` kann ein Array oder ein String sein. Alle Werte im `array` werden in einem String zusammengeführt. Wenn Du `optionalSeparator` angibst, wird er zwischen den verketteten Werten eingefügt. Andernfalls wird der Standard-Trennzeichen `,` verwendet. Wandelt Werte in einen String um. ##### Beispiel @@ -349,7 +352,7 @@ Der Wert für `array` kann ein Array oder ein String sein. Alle Werte im `array` `toJSON(value)` -Gibt eine Pretty-Print-JSON-Darstellung von `value` zurück. Mit dieser Funktion können Sie die in Kontexten enthaltenen Informationen debuggen. +Gibt eine Pretty-Print-JSON-Darstellung von `value` zurück. Diese Funktion hilft Dir bei der Fehlersuche in den Informationen, die in Kontexten enthalten sind. ##### Beispiel @@ -409,7 +412,7 @@ Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repos ### Funktionen zur Prüfung des Job-Status -Sie können die nachfolgenden Statuscheckfunktionen als Ausdrücke in `if`-Bedingungen verwenden. Wenn der `if`-Ausdruck keine Statusfunktion enthält, wird automatisch das Ergebnis `success()` zurückgegeben. Weitere Informationen zu `if`-Anweisungen finden Sie unter „[Workflow-Syntax für GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)“. +Du kannst die nachfolgenden Funktionen zum Statuscheck als Ausdrücke in `if`-Bedingungen verwenden. Wenn Dein `if`-Ausdruck keine Statusfunktion enthält, wird automatisch das Ergebnis `success()` zurückgegeben. Weitere Informationen zu `if`-Anweisungen finden Sie unter „[Workflow-Syntax für GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)“. #### success (Erfolg) @@ -426,7 +429,7 @@ steps: #### always -Gibt immer `true`zurück, sogar bei Abbruch. Ein Auftrag oder Schritt wird nicht ausgeführt, wenn ein kritischer Fehler die Ausführung der Aufgabe verhindert. Beispiel: Quellen konnten nicht abgerufen werden. +Gibt immer `true`zurück, sogar bei Abbruch. Ein Job oder Schritt wird nicht ausgeführt, wenn ein kritischer Fehler die Ausführung der Aufgabe verhindert. Beispiel: Quellen konnten nicht abgerufen werden. ##### Beispiel @@ -459,7 +462,7 @@ steps: ### Objektfilter -Mit der `*`-Syntax können Sie einen Filter anwenden und passende Elemente in einer Sammlung auswählen. +Mit der Syntax `*` kannst Du einen Filter anwenden und passende Elemente in einer Sammlung auswählen. Betrachten Sie beispielsweise das Objekt-Array `fruits`. diff --git a/translations/de-DE/content/actions/reference/environment-variables.md b/translations/de-DE/content/actions/reference/environment-variables.md index 527ed72afc12a..6c4e302fd9793 100644 --- a/translations/de-DE/content/actions/reference/environment-variables.md +++ b/translations/de-DE/content/actions/reference/environment-variables.md @@ -57,6 +57,16 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d | `GITHUB_API_URL` | Gibt die API-URL zurück. For example: `https://api.github.com`. | | `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. For example: `https://api.github.com/graphql`. | +{% tip %} + +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determining when to use default environment variables or contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### Namens-Konventionen für Umgebungsvariablen {% note %} 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 8a8a79a0f2b1d..b3a15a02948fc 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 @@ -80,6 +80,8 @@ In den fünf Feldern stehen die folgenden Operatoren zur Auswahl: Mit [crontab guru](https://crontab.guru/) können Sie die Cron-Syntax erzeugen und den Ausführungszeitpunkt bestätigen. Als Einstiegshilfe steht eine Liste mit [crontab-guru-Beispielen](https://crontab.guru/examples.html) bereit. +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." + ### Manual events You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event. @@ -145,7 +147,7 @@ jobs: Mit der {% data variables.product.product_name %}-API können Sie das Webhook-Ereignis [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) auslösen, wenn ein Workflow für eine Aktivität ausgelöst werden soll, die außerhalb von {% data variables.product.prodname_dotcom %} abläuft. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)." -Soll das benutzerdefinierte Webhook-Ereignis `repository_dispatch` ausgelöst werden, senden Sie eine `POST`-Anfrage an einen {% data variables.product.product_name %}-API-Endpunkt, und geben Sie den Namen für einen `event_type` als Beschreibung für den Aktivitätstyp an. Soll ein Workflow-Lauf ausgelöst werden, konfigurieren Sie außerdem den Workflow für die Verwendung des Ereignisses `repository_dispatch`. +Soll das benutzerdefinierte Webhook-Ereignis `repository_dispatch` ausgelöst werden, senden Sie eine `POST`-Anfrage an einen {% data variables.product.product_name %}-API-Endpunkt, und geben Sie den Namen für einen `event_type` als Beschreibung für den Aktivitätstyp an. Soll ein Workflow-Lauf ausgelöst werden, konfigurierest Du außerdem Deinen Workflow für die Verwendung des Ereignisses `repository_dispatch`. ##### Beispiel @@ -364,7 +366,7 @@ Führt den Workflow aus, wenn das Ereignis `issues` eintritt. {% data reusables. {% data reusables.developer-site.limit_workflow_to_activity_types %} -Du kannst einen Workflow beispielsweise ausführen, wenn ein Problem geöffnet (`opened`) oder bearbeitet (`edited`) wurde oder wenn dafür ein Meilenstein gesetzt wurde (`milestoned`). +Sie können einen Workflow beispielsweise ausführen, wenn ein Issue geöffnet (`opened`) oder bearbeitet (`edited`) oder wenn ein Meilenstein gesetzt (`milestoned`) wurde. ```yaml on: @@ -394,7 +396,7 @@ on: #### `Meilensteine` -Führt Deinen Workflow aus, wenn das Ereignis `milestone` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." +Führt den Workflow aus, wenn das Ereignis `milestone` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)." {% data reusables.github-actions.branch-requirement %} @@ -451,7 +453,7 @@ on: #### `project_card` -Führt den Workflow aus, wenn das Ereignis `project_card` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." +Führt den Workflow aus, wenn das Ereignis `project_ticket` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)." {% data reusables.github-actions.branch-requirement %} @@ -471,7 +473,7 @@ on: #### `project_column` -Führt Deinen Workflow aus, wenn das Ereignis `project_column` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." +Führt den Workflow aus, wenn das Ereignis `project_column` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)." {% data reusables.github-actions.branch-requirement %} @@ -481,7 +483,7 @@ Führt Deinen Workflow aus, wenn das Ereignis `project_column` eintritt. {% data {% data reusables.developer-site.limit_workflow_to_activity_types %} -Du kannst einen Workflow beispielsweise ausführen, wenn eine Projektspalte erstellt (`created`) oder gelöscht (`deleted`) wurde. +Sie können einen Workflow beispielsweise ausführen, wenn eine Projektspalte erstellt (`created`) oder gelöscht (`deleted`) wurde. ```yaml on: @@ -491,7 +493,7 @@ on: #### `public` -Führt Deinen Workflow aus, wenn ein Benutzer ein privates Repository öffentlich macht, wodurch das Ereignis `public` ausgelöst wird. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." +Führt den Workflow aus, wenn ein Benutzer ein privates Repository öffentlich macht, wodurch das Ereignis `public` ausgelöst wird. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)." {% data reusables.github-actions.branch-requirement %} @@ -499,7 +501,7 @@ Führt Deinen Workflow aus, wenn ein Benutzer ein privates Repository öffentlic | -------------------------------------------- | --------------- | --------------------------------- | --------------- | | [`public`](/webhooks/event-payloads/#public) | – | Letzter Commit im Standard-Branch | Standard-Branch | -Du kannst einen Workflow beispielsweise ausführen, wenn das Ereignis `public` eintritt. +Sie können einen Workflow beispielsweise ausführen, wenn das Ereignis `public` eintritt. ```yaml on: @@ -508,11 +510,11 @@ on: #### `pull_request` -Führt Deinen Workflow aus, wenn das Ereignis `pull_request` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." +Führt den Workflow aus, wenn das Ereignis `pull_request` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)." {% note %} -**Note:** By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. Sollen Workflows für weitere Aktivitätstypen ausgelöst werden, verwende das Schlüsselwort `types`. +**Hinweis:** Standardmäßig wird ein Workflow nur dann ausgeführt, wenn der `pull_request` den Aktivitätstyp `opened`, `synchronize` oder `reopened` aufweist. Sollen Workflows für weitere Aktivitätstypen ausgelöst werden, geben Sie das Stichwort `types` an. {% endnote %} @@ -588,12 +590,13 @@ This event runs in the context of the base of the pull request, rather than in t | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -------------- | | [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `opened`
- `edited`
- `closed`
- `reopened`
- `synchronize`
- `ready_for_review`
- `locked`
- `unlocked`
- `review_requested`
- `review_request_removed` | Last commit on the PR base branch | PR base branch | -By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. Sollen Workflows für weitere Aktivitätstypen ausgelöst werden, verwende das Schlüsselwort `types`. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)“. +By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. Sollen Workflows für weitere Aktivitätstypen ausgelöst werden, geben Sie das Stichwort `types` an. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)“. Du kannst einen Workflow beispielsweise dann ausführen, wenn ein Pull Request zugewiesen (`assigned`), geöffnet (`opened`), synchronisiert (`synchronize`) oder erneut geöffnet (`reopened`) wurde. ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` 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 124ad94aa5c3d..a48b7494e64dc 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 @@ -83,44 +83,11 @@ Wenn Sie ein bestimmtes Tool anfordern möchten, öffnen Sie bitte einen Issue u {% endnote %} -Windows- und Ubuntu-Runner werden in Azure gehostet und haben die gleichen IP-Adressbereiche wie Azure-Rechenzentren. Derzeit befinden sich alle {% data variables.product.prodname_dotcom %}-gehosteten Windows- und Ubuntu-Runner in den folgenden Azure-Regionen: - -- Ost-USA (`eastus`) -- Ost-USA 2 (`eastus`) -- West-US 2 (`westus2`) -- Zentral-USA (`centralus`) -- Süd-Zentral-USA (`southcentralus`) - -Microsoft aktualisiert die Azure-IP-Adressbereiche wöchentlich in einer JSON-Datei. Diese können Sie auf der Website [Azure IP Ranges and Service Tags - Public Cloud](https://www.microsoft.com/en-us/download/details.aspx?id=56519) herunterladen. Sie können diesen IP-Adressbereich verwenden, falls Sie eine Positivliste vorschreiben, um den nicht autorisierten Zugriff auf Ihre internen Ressourcen zu verhindern. - -Die JSON-Datei enthält einen Array mit der Bezeichnung `values`. Innerhalb dieses Arrays findest Du die unterstützten IP-Adressen in einem Objekt mit `name` und `id` der Azure-Region, z.B. `"AzureCloud.eastus2"`. - -Die unterstützten IP-Adressbereiche befinden sich im Objekt `"addressPrefixes"`. Dies ist ein komprimiertes Beispiel der JSON-Datei. - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. + +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. + +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### File systems 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 a30b826201013..03fbfb9cd48dd 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 @@ -187,7 +187,7 @@ Weitere Informationen zur Cron-Syntax findest Du unter „[Ereignisse, die Workf ### `env` -Eine `map` mit Umgebungsvariablen, die für alle Jobs und Schritte im Workflow verfügbar sind. Darüber hinaus kannst Du auch Umgebungsvariablen festlegen, die ausschließlich für einen Job oder Schritt bereitstehen. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} @@ -639,14 +639,15 @@ Mit dem Schlüsselwort`working-directory` gibst Du das Arbeitsverzeichnis an, in Du kannst die Einstellungen zur Standard-Shell im Betriebssystem des Läufers mit dem Schlüsselwort `shell` überschreiben. Sie können die integrierten `shell`-Stichwörter verwenden oder eine benutzerdefinierte Reihe von Shell-Optionen definieren. -| Unterstützte Plattform | Parameter `shell` | Beschreibung | Intern ausgeführter Befehl | -| ---------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| Alle | `bash` | Die standardmäßige Shell für alle Plattformen außer Windows mit einem Fallback zu `sh`. Wenn eine Bash-Shell für Windows angegeben wird, wird die in Git für Windows enthaltene Bash-Shell verwendet. | `bash --noprofile --norc -eo pipefail {0}` | -| Alle | `pwsh` | Der PowerShell Core. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. | `pwsh -command ". '{0}'"` | -| Alle | `python` | Führt den Befehl Python aus. | `python {0}` | -| Linux / macOS | `sh` | Das Fallback-Verhalten für alle Betriebssystem-Plattformen außer Windows, falls keine Shell angegeben ist und `bash` nicht im Pfad gefunden wird. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.cmd` an Deinen Skriptnamen an und ersetzt `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | Dies ist die standardmäßig für Windows verwendete Shell. Die Desktop PowerShell. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. | `powershell -command ". '{0}'"`. | +| Unterstützte Plattform | Parameter `shell` | Beschreibung | Intern ausgeführter Befehl | +| ---------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Alle | `bash` | Die standardmäßige Shell für alle Plattformen außer Windows mit einem Fallback zu `sh`. Wenn eine Bash-Shell für Windows angegeben wird, wird die in Git für Windows enthaltene Bash-Shell verwendet. | `bash --noprofile --norc -eo pipefail {0}` | +| Alle | `pwsh` | Der PowerShell Core. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. | `pwsh -command ". '{0}'"` | +| Alle | `python` | Führt den Befehl Python aus. | `python {0}` | +| Linux / macOS | `sh` | Das Fallback-Verhalten für alle Betriebssystem-Plattformen außer Windows, falls keine Shell angegeben ist und `bash` nicht im Pfad gefunden wird. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.cmd` an Deinen Skriptnamen an und ersetzt `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | Dies ist die standardmäßig für Windows verwendete Shell. Der PowerShell Core. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. | `powershell -command ". '{0}'"`. | #### Beispiel zur Ausführung eines Skripts mittels Bash @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### Beispiel zur Ausführung eines Python-Skripts ```yaml @@ -1149,7 +1159,7 @@ Die Pfad-, Branch- und Tag-Filter können bestimmte Sonderzeichen umfassen. - `**`: Steht für kein Zeichen oder mehrere beliebige Zeichen. - `?`: Steht für kein Zeichen oder ein einzelnes Zeichen. Zum Beispiel passt `Oktoc?t` auf `Oktocat`. - `+`: Matches one or more of the preceding character. -- `[]` Steht für irgend ein Zeichen, das in den Klammern aufgelistet ist oder das in einen in den Klammern enthalten Bereich fällt. Mögliche Bereiche sind ausschließlich `a-z`, `A-Z` und `0-9`. Zum Beispiel entspricht der Bereich`[0-9a-f]` beliebigen Ziffern oder Kleinbuchstaben. Zum Beispiel passt `[CB]at` sowohl zu `Cat` als auch zu `Bat` und `[1-2]00` passt sowohl zu `100` als auch zu `200`. +- `[]` Steht für irgend ein Zeichen, das in den Klammern aufgelistet ist oder das in einen in den Klammern enthalten Bereich fällt. Mögliche Bereiche sind ausschließlich `a-z`, `A-Z` und `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. Zum Beispiel passt `[CB]at` sowohl zu `Cat` als auch zu `Bat` und `[1-2]00` passt sowohl zu `100` als auch zu `200`. - `!`: Am Anfang eines Musters stehend negiert es das Muster in sein Gegenteil. Es hat keine besondere Bedeutung, wenn es nicht das erste Zeichen ist. Die Zeichen `*`, `[` und `!` sind Sonderzeichen in YAML. Wenn ein Muster mit `*`, `[` oder `!` beginnen soll, schließen Sie das Muster in Anführungszeichen ein. @@ -1167,35 +1177,35 @@ Weitere Informationen zur Syntax für Branch-, Tag- und Pfadfilter finden Sie un #### Muster für den Abgleich von Branches und Tags -| Muster | Beschreibung | Beispiele für Übereinstimmungen | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `feature/*` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). | -`feature/my-branch`
-`feature/your-branch` | -| `feature/**` | Das Platzhalterzeichen `**` steht für ein beliebiges Zeichen, also auch für den Schrägstrich (`/`), in Branch- und Tag-Namen. | -`feature/beta-a/my-branch`
-`feature/your-branch`
-`feature/mona/the/octocat` | -| -`main`
-`releases/mona-the-octcat` | Abgleich mit dem exakten Branch- oder Tag-Namen. | -`main`
-`releases/mona-the-octocat` | -| `'*'` | Abgleich mit allen Branch- und Tag-Namen, die keinen Schrägstrich (`/`) enthalten. Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | -`main`
-`releases` | -| `'**'` | Abgleich mit allen Branch- und Tag-Namen. Dies ist das Standardverhalten, wenn Sie keinen `branches`- oder `tags`-Filter angeben. | -`all/the/branches`
-`every/tag` | -| `'*feature'` | Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | -`mona-feature`
-`feature`
-`ver-10-feature` | -| `v2*` | Abgleich mit Branch- und Tag-Namen, die mit `v2` beginnen. | -`v2`
-`v2.0`
-`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Abgleich mit allen semantischen Versions-Tags mit der Hauptversion 1 oder 2. | -`v1.10.1`
-`v2.0.0` | +| Muster | Beschreibung | Beispiele für Übereinstimmungen | +| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). | `feature/my-branch`

`feature/your-branch` | +| `feature/**` | Das Platzhalterzeichen `**` steht für ein beliebiges Zeichen, also auch für den Schrägstrich (`/`), in Branch- und Tag-Namen. | `feature/beta-a/my-branch`

`feature/your-branch`

`feature/mona/the/octocat` | +| `main`

`releases/mona-the-octcat` | Abgleich mit dem exakten Branch- oder Tag-Namen. | `main`

`releases/mona-the-octocat` | +| `'*'` | Abgleich mit allen Branch- und Tag-Namen, die keinen Schrägstrich (`/`) enthalten. Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | `main`

`releases` | +| `'**'` | Abgleich mit allen Branch- und Tag-Namen. Dies ist das Standardverhalten, wenn Sie keinen `branches`- oder `tags`-Filter angeben. | `all/the/branches`

`every/tag` | +| `'*feature'` | Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | `mona-feature`

`feature`

`ver-10-feature` | +| `v2*` | Abgleich mit Branch- und Tag-Namen, die mit `v2` beginnen. | `v2`

`v2.0`

`v2.9` | +| `v[12].[0-9]+.[0-9]+` | Abgleich mit allen semantischen Versions-Tags mit der Hauptversion 1 oder 2. | `v1.10.1`

`v2.0.0` | #### Muster für den Abgleich von Dateinamen Pfadmuster müssen mit dem gesamten Pfad übereinstimmen und mit dem Root des Repositorys beginnen. -| Muster | Beschreibung der Übereinstimmungen | Beispiele für Übereinstimmungen | -| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | -| `'*'` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | -`README.md`
-`server.rb` | -| `'*.jsx?'` | Das Zeichen `?` steht für null Instanzen oder genau eine Instanz des vorangegangenen Zeichens. | -`page.js`
-`page.jsx` | -| `'**'` | Das Platzhalterzeichen `**` steht für ein beliebiges Zeichen, auch für den Schrägstrich (`/`). Dies ist das Standardverhalten, wenn Sie keinen `path`-Filter angeben. | -`all/the/files.md` | -| `'*.js'` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). Abgleich mit allen `.js`-Dateien im Root des Repositorys. | -`app.js`
-`index.js` | -| `'**.js'` | Abgleich mit allen `.js`-Dateien im Repository. | -`index.js`
-`js/index.js`
-`src/js/app.js` | -| `docs/*` | Alle Dateien im Root des Verzeichnisses `docs` im Root des Repositorys. | -`docs/README.md`
-`docs/file.txt` | -| `docs/**` | Beliebige Dateien im Verzeichnis `docs` im Root des Repositorys. | -`docs/README.md`
-`docs/mona/octocat.txt` | -| `docs/**/*.md` | Eine Datei mit dem Suffix `.md` an beliebiger Stelle im Verzeichnis `docs`. | -`docs/README.md`
-`docs/mona/hello-world.md`
-`docs/a/markdown/file.md` | -| `'**/docs/**'` | Beliebige Dateien im Verzeichnis `docs` an beliebiger Stelle im Repository. | -`/docs/hello.md`
-`dir/docs/my-file.txt`
-`space/docs/plan/space.doc` | -| `'**/README.md'` | Eine Datei mit dem Namen „README.md“ an beliebiger Stelle im Repository. | -`README.md`
-`js/README.md` | -| `'**/*src/**'` | Eine beliebige Datei in einem Ordner mit dem Suffix `src` an beliebiger Stelle im Repository. | -`a/src/app.js`
-`my-src/code/js/app.js` | -| `'**/*-post.md'` | Eine Datei mit dem Suffix `-post.md` an beliebiger Stelle im Repository. | -`my-post.md`
-`path/their-post.md` | -| `'**/migrate-*.sql'` | Eine Datei mit dem Präfix `migrate-` und dem Suffix `.sql` an beliebiger Stelle im Repository. | -`migrate-10909.sql`
-`db/migrate-v1.0.sql`
-`db/sept/migrate-v1.sql` | -| -`*.md`
-`!README.md` | Ein Ausrufezeichen (`!`) vor einem Muster negiert das Muster. Wenn eine Datei sowohl mit einem Muster übereinstimmt als auch mit einem negativen Muster, das später in der Datei definiert ist, wird die Datei nicht berücksichtigt. | -`hello.md`
_Kein Abgleich mit_
-`README.md`
-`docs/hello.md` | -| -`*.md`
-`!README.md`
-`README*` | Die Muster werden sequenziell geprüft. Wenn ein Muster ein vorangegangenes Muster negiert, werden die Dateipfade wieder berücksichtigt. | -`hello.md`
-`README.md`
-`README.doc` | +| Muster | Beschreibung der Übereinstimmungen | Beispiele für Übereinstimmungen | +| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | `README.md`

`server.rb` | +| `'*.jsx?'` | Das Zeichen `?` steht für null Instanzen oder genau eine Instanz des vorangegangenen Zeichens. | `page.js`

`page.jsx` | +| `'**'` | Das Platzhalterzeichen `**` steht für ein beliebiges Zeichen, auch für den Schrägstrich (`/`). Dies ist das Standardverhalten, wenn Sie keinen `path`-Filter angeben. | `all/the/files.md` | +| `'*.js'` | Das Platzhalterzeichen `*` steht für ein beliebiges Zeichen, nicht jedoch für den Schrägstrich (`/`). Abgleich mit allen `.js`-Dateien im Root des Repositorys. | `app.js`

`index.js` | +| `'**.js'` | Abgleich mit allen `.js`-Dateien im Repository. | `index.js`

`js/index.js`

`src/js/app.js` | +| `docs/*` | Alle Dateien im Root des Verzeichnisses `docs` im Root des Repositorys. | `docs/README.md`

`docs/file.txt` | +| `docs/**` | Beliebige Dateien im Verzeichnis `docs` im Root des Repositorys. | `docs/README.md`

`docs/mona/octocat.txt` | +| `docs/**/*.md` | Eine Datei mit dem Suffix `.md` an beliebiger Stelle im Verzeichnis `docs`. | `docs/README.md`

`docs/mona/hello-world.md`

`docs/a/markdown/file.md` | +| `'**/docs/**'` | Beliebige Dateien im Verzeichnis `docs` an beliebiger Stelle im Repository. | `/docs/hello.md`

`dir/docs/my-file.txt`

`space/docs/plan/space.doc` | +| `'**/README.md'` | Eine Datei mit dem Namen „README.md“ an beliebiger Stelle im Repository. | `README.md`

`js/README.md` | +| `'**/*src/**'` | Eine beliebige Datei in einem Ordner mit dem Suffix `src` an beliebiger Stelle im Repository. | `a/src/app.js`

`my-src/code/js/app.js` | +| `'**/*-post.md'` | Eine Datei mit dem Suffix `-post.md` an beliebiger Stelle im Repository. | `my-post.md`

`path/their-post.md` | +| `'**/migrate-*.sql'` | Eine Datei mit dem Präfix `migrate-` und dem Suffix `.sql` an beliebiger Stelle im Repository. | `migrate-10909.sql`

`db/migrate-v1.0.sql`

`db/sept/migrate-v1.sql` | +| `*.md`

`!README.md` | Ein Ausrufezeichen (`!`) vor einem Muster negiert das Muster. Wenn eine Datei sowohl mit einem Muster übereinstimmt als auch mit einem negativen Muster, das später in der Datei definiert ist, wird die Datei nicht berücksichtigt. | `hello.md`

_Does not match_

`README.md`

`docs/hello.md` | +| `*.md`

`!README.md`

`README*` | Die Muster werden sequenziell geprüft. Wenn ein Muster ein vorangegangenes Muster negiert, werden die Dateipfade wieder berücksichtigt. | `hello.md`

`README.md`

`README.doc` | diff --git a/translations/de-DE/content/admin/authentication/using-saml.md b/translations/de-DE/content/admin/authentication/using-saml.md index 3559146f1a652..5e7bbc769c0d0 100644 --- a/translations/de-DE/content/admin/authentication/using-saml.md +++ b/translations/de-DE/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod ### SAML-Metadaten -Die Service Provider-Metadaten Ihrer {% data variables.product.prodname_ghe_server %}-Instanzen sind unter `http(s)://[hostname]/saml/metadata` verfügbar. +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. Wenn Sie Ihren Identity Provider manuell konfigurieren möchten, lautet die Assertionsverbraucherdienst-URL (ACS) `http(s)://[hostname]/saml/consume`. Dafür wird die Bindung `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` verwendet. diff --git a/translations/de-DE/content/admin/configuration/command-line-utilities.md b/translations/de-DE/content/admin/configuration/command-line-utilities.md index 13f73e1976f3e..3a1ac0f2c26ef 100644 --- a/translations/de-DE/content/admin/configuration/command-line-utilities.md +++ b/translations/de-DE/content/admin/configuration/command-line-utilities.md @@ -468,18 +468,21 @@ ghe-webhook-logs ``` Um alle fehlgeschlagenen Hook-Auslieferungen vom Vortag anzuzeigen: +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -Um die vollständige Hook-Nutzlast, das Ergebnis und alle Ausnahmen für die Lieferung anzuzeigen: +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -Um globale Webhook-Lieferungen anzuzeigen: +Um die vollständige Hook-Nutzlast, das Ergebnis und alle Ausnahmen für die Lieferung anzuzeigen: ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### Clustering diff --git a/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index 377e5d092117a..f6f7da850c586 100644 --- a/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ Wenn ein Proxyserver für {% data variables.product.product_location %} aktivier {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. Geben Sie unter **HTTP Proxy Server** (HTTP-Proxyserver) die URL Ihres Proxyservers ein. ![Feld zur Eingabe der HTTP-Proxyserver-URL](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Geben Sie optional unter **HTTP Proxy Exclusion** (HTTP-Proxyausschluss) die Hosts ein, für die kein Proxyzugriff erforderlich ist. Trennen Sie dabei die Hosts durch Kommas voneinander. ![Feld zur Eingabe von HTTP-Proxyausschlüssen](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. Geben Sie optional unter **HTTP Proxy Exclusion** (HTTP-Proxyausschluss) die Hosts ein, für die kein Proxyzugriff erforderlich ist. Trennen Sie dabei die Hosts durch Kommas voneinander. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Feld zur Eingabe von HTTP-Proxyausschlüssen](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md index 90871eecd8a18..5f0c982b6b78c 100644 --- a/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ Wenn sich Backup-Versuche überschneiden, wird der Befehl `ghe-backup` mit einer Im Falle eines längeren Ausfalls oder einer Katastrophe am Hauptstandort können Sie {% data variables.product.product_location %} wiederherstellen. Stellen Sie dazu eine andere {% data variables.product.prodname_enterprise %}-Appliance bereit, und führen Sie auf dem Backup-Host eine Wiederherstellung aus. Sie müssen der Ziel-{% data variables.product.prodname_enterprise %}-Appliance den SSH-Schlüssel des Backup-Hosts als einen autorisierten SSH-Schlüssel hinzufügen, bevor Sie eine Appliance wiederherstellen. +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + Führen Sie den Befehl `ghe-restore` aus, um den letzten erfolgreichen {% data variables.product.product_location %}-Snapshot wiederherzustellen. Es sollte in etwa folgende Ausgabe angezeigt werden: ```shell diff --git a/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index aac1ea1f29ecd..4f1447b1153d7 100644 --- a/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ For the users of {% data variables.product.product_location %} to be able to ena {% data reusables.enterprise_site_admin_settings.management-console %} 1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features including {% data variables.product.prodname_code_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. +{% data reusables.enterprise_management_console.advanced-security-license %} ### {% data variables.product.prodname_code_scanning %} aktivieren -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ If you can't see **{% data variables.product.prodname_advanced_security %}** in #### Setting up a self-hosted runner -If you are enrolled in the {% data variables.product.prodname_actions %} beta, then {% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." +{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions. -#### Provisioning the action -To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate action must be available locally. You can make the action available in three ways. +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisioning the actions +To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended** You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. -- You can create a local copy of the action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository with the action. For example, if you want to use the {% data variables.product.prodname_codeql %} action, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. - +- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. ##### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} - 1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. Weitere Informationen findest Du unter "[selbst-gehostete Runner hinzufügen](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configuring {% data variables.product.prodname_codeql %} on a server without internet access +If the server on which you are running +{% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} Action sync tool to copy the {% data variables.product.prodname_codeql %} actions and query bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -After you configure a self-hosted runner, users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file. +#### Enabling code scanning for individual repositories +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file. ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} -If your organization isn't taking part in the beta for {% data variables.product.prodname_actions %}, or if you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. +If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, 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)." ### Disabling {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/de-DE/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..9c60b3b35af44 --- /dev/null +++ b/translations/de-DE/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configuring secret scanning for your appliance +shortTitle: Configuring secret scanning +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### Informationen zu {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +### Vorrausetzungen + +To use {% data variables.product.prodname_secret_scanning %} in {% data variables.product.product_location %} you need these two prerequisites. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- You need an {% data variables.product.prodname_advanced_security %} license. + +#### Checking support for the SSSE3 flag on your vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. + +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Enter the following command: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling secret scanning](#enabling-secret-scanning)" below. + +If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. + +#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### {% data variables.product.prodname_secret_scanning %} aktivieren + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Disabling {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md b/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md index f827bfe63bdc0..fc5e47af874e1 100644 --- a/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ Die Subdomain-Isolation mindert Cross-Site-Scripting und andere verwandte Schwac Bei aktivierter Subdomain-Isolation ersetzt {% data variables.product.prodname_ghe_server %} verschiedene Pfade durch Subdomains. -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} To use Docker with {% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Pfad ohne Subdomain-Isolation | Pfad mit Subdomain-Isolation | -| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled. | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Pfad ohne Subdomain-Isolation | Pfad mit Subdomain-Isolation | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled for the {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### Vorrausetzungen diff --git a/translations/de-DE/content/admin/configuration/index.md b/translations/de-DE/content/admin/configuration/index.md index 1311a4e24153a..b163fd881b8ed 100644 --- a/translations/de-DE/content/admin/configuration/index.md +++ b/translations/de-DE/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..dae548ac462e5 --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Managing GitHub for mobile for your enterprise +intro: You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}. +permissions: Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Informationen zu {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} For more information, see "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." + +Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data. + +### Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/de-DE/content/admin/enterprise-management/about-clustering.md b/translations/de-DE/content/admin/enterprise-management/about-clustering.md index 5fdea1646ceda..c9915c6aa3c22 100644 --- a/translations/de-DE/content/admin/enterprise-management/about-clustering.md +++ b/translations/de-DE/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ Learn more about [services required for clustering](/enterprise/{{ currentVersio Clustering bietet Redundanz, ist jedoch nicht dazu vorgesehen, eine Hochverfügbarkeitskonfiguration zu ersetzen. Weitere Informationen finden Sie unter „[Hochverfügbarkeitskonfiguration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)“. Eine Konfiguration mit einer primären/sekundären Failover-Instanz ist viel einfacher als Clustering und erfüllt die Anforderungen vieler Organisationen. Weitere Informationen finden Sie unter „[Unterschiede zwischen Clustering und Hochverfügbarkeit](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)“. +{% data reusables.package_registry.packages-cluster-support %} + ### Wie kann ich auf Clustering zugreifen? Clustering ist für bestimmte Skalierungssituationen vorgesehen, nicht aber für jede Organisation. Wenn Du Clustering in Betracht ziehen möchtest, wende Dich bitte an Deinen {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/de-DE/content/admin/enterprise-management/index.md b/translations/de-DE/content/admin/enterprise-management/index.md index 50a77b9262650..03ad40741b0e2 100644 --- a/translations/de-DE/content/admin/enterprise-management/index.md +++ b/translations/de-DE/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md index 7afcdb9112816..696d116bfc427 100644 --- a/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + + {% endnote %} + {% endif %} diff --git a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md index d546338d27730..ad24cbb741ab8 100644 --- a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ Weitere Informationen finden Sie unter „[Befehlszeilenprogramme](/enterprise/{ #### Rollback einer Feature-Veröffentlichung durchführen Um ein Rollback von einer Feature-Veröffentlichung durchzuführen, stellen Sie diese über einen VM-Snapshot wieder her, um sicherzustellen, dass die Root- und Datenpartitionen einen konsistenten Zustand aufweisen. Weitere Informationen finden Sie unter „[Snapshot erstellen](#taking-a-snapshot)“. + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Weiterführende Informationen + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md index b8858b30bc625..1d20da25fefcd 100644 --- a/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md @@ -59,7 +59,9 @@ Nachdem Du Deine Supportanfrage eingereicht hast, können wir Dich bitten, unser - `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %}-Konfigurationsprotokolle, - `collectd/logs/collectd.log`: Collectd-Protokolle, - `mail-logs/mail.log`: SMTP-E-Mail-Zustellprotokolle, +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`: Webhook-Auslieferungsfehler. +{% endif %} Weitere Informationen finden Sie unter „[Auditprotokollierung](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)“. diff --git a/translations/de-DE/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..3b3b6da7eb2e0 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: About using actions on GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. + +{% data reusables.actions.enterprise-no-internet-actions %} + +### Official actions bundled with {% data variables.product.prodname_ghe_server %} + +Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. + +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. + +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. + +{% note %} + +**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.prodname_ghe_server %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." + +{% endnote %} + +### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} + +If users on your enterprise instance need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. + +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} + +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..ca8cd4f13168c --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Advanced configuration and troubleshooting +intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..a2556020e8d72 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. + +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: + +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. +1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 02a717ae8601b..83e4ac0df7daf 100644 --- a/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can connect {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} using {% data variables.product.prodname_github_connect %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions @@ -23,3 +23,4 @@ Before enabling access to all actions from {% data variables.product.prodname_do {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..097155565b393 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..b5724bcdfcfe5 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with Amazon S3 storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Vorrausetzungen + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..592a1435b9358 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Enabling GitHub Actions with Azure Blob storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Vorrausetzungen + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..244d20d5f86a6 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Vorrausetzungen + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. +* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 37a543f948384..d47cc8b225a01 100644 --- a/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### About {% data variables.product.prodname_actions %} permissions for your enterprise diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..65174fa7d80d6 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. + +### Review hardware considerations + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### External storage requirements + +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. + +{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} supports these storage providers: + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Amazon S3 permissions + +{% data reusables.actions.enterprise-s3-permission %} + +### Enabling {% data variables.product.prodname_actions %} + +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/). + +### Weiterführende Informationen + +- "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +### Selbst-gehostete Runner hinzufügen + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. Weitere Informationen findest Du unter "[selbst-gehostete Runner hinzufügen](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." + +### General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." + +{% endif %} diff --git a/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md b/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..2fb921667a35c --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: High availability for GitHub Actions +intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +versions: + enterprise-server: '>=3.0' +--- + +### Replication or redundancy of your {% data variables.product.prodname_actions %} data + +{% data reusables.actions.enterprise-storage-ha-backups %} + +We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: + +* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### High availability replicas + +#### Promoting a replica + +When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. + +For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." + +#### Hochverfügbarkeitsreplikat entfernen + +Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. diff --git a/translations/de-DE/content/admin/github-actions/index.md b/translations/de-DE/content/admin/github-actions/index.md index 82a9556aa841d..bd6c1ef06cb82 100644 --- a/translations/de-DE/content/admin/github-actions/index.md +++ b/translations/de-DE/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### Inhaltsverzeichnis -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 6ac6a0c8d783c..3f219520639cf 100644 --- a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -To make specific actions from {% data variables.product.prodname_dotcom_the_website %} available to use in workflows, you can use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. ### About the `actions-sync` tool diff --git a/translations/de-DE/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/de-DE/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..a9a1541c59249 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' +versions: + enterprise-server: '>=3.0' +--- + +### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + +#### Installing the certificate on the runner machine + +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. + +For the steps required to install a certificate, refer to the documentation for your runner's operating system. + +#### Configuring Node.JS to use the certificate + +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +Ein Beispiel: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. Weitere Informationen findest Du unter „[selbst-gehostete Runner entfernen](/actions/hosting-your-own-runners/removing-self-hosted-runners)“ und „[selbst-gehostete Runner hinzufügen](/actions/hosting-your-own-runners/adding-self-hosted-runners)“. + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md b/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..6cadc89ba9e37 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Ein Beispiel: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Ein Beispiel: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-aws.md index f33f1d81549ba..a3d4d77dbe107 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ Den primären und Replikatinstanzen sollten in Hochverfügbarkeitskonfiguratione ### Weiterführende Informationen -- „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-azure.md index ea12c1bf74945..53afeb9f4b18c 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ Sie sollten einen DS v2-Instanztyp mit mindestens 14 GB RAM verwenden. Sie könn {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### Weiterführende Informationen - ### Weiterführende Informationen - - - „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index b248f44c1e562..48a3ad9f547ce 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ Zum Erstellen der {% data variables.product.prodname_ghe_server %}-Instanz müss ### Weiterführende Informationen -- „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index 996a3ea72f023..f48212a2c9b4b 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### Weiterführende Informationen - - „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index c8adf86b42518..41b58012ad93d 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ versions: ### Weiterführende Informationen - - „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 705c5bee8a355..3f00907377680 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### Weiterführende Informationen - - „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 5113c2e1724bd..9ea9a236d5b1b 100644 --- a/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/de-DE/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### Weiterführende Informationen - - „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“ +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md b/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md index 7b39e1e1bdd67..51a436877b367 100644 --- a/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ Zum sorgfältigen Testen einer {% data variables.product.prodname_ghe_server %}- 1. Führen Sie mithilfe von {% data variables.product.prodname_enterprise_backup_utilities %} ein Backup Ihrer Produktionsinstanz durch. Weitere Informationen finden Sie im Abschnitt „Informationen zu {% data variables.product.prodname_enterprise_backup_utilities %}“ unter „[Backups auf Ihrer Appliance konfigurieren](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)“. 2. Richten Sie eine neue Instanz ein, die als Ihre Staging-Umgebung fungiert. Sie können dieselben Leitfäden zum Bereitstellen und Installieren Ihrer Testinstanz verwenden, die Sie für Ihre Produktionsinstanz verwenden. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %}-Instanz einrichten](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)“. 3. Stellen Sie Ihr Backup auf Ihrer Testinstanz wieder her. Weitere Informationen finden Sie im Abschnitt „Backup wiederherstellen“ unter „[Backups auf Ihrer Appliance konfigurieren](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)“. + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Weiterführende Informationen + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..d294816750637 --- /dev/null +++ b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### Weiterführende Informationen + +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository diff --git a/translations/de-DE/content/admin/overview/index.md b/translations/de-DE/content/admin/overview/index.md index 980813ad654ad..fd42df580faea 100644 --- a/translations/de-DE/content/admin/overview/index.md +++ b/translations/de-DE/content/admin/overview/index.md @@ -15,5 +15,6 @@ Weitere Informationen zu oder zum Kauf von {% data variables.product.prodname_en {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..0aba2b7b48886 --- /dev/null +++ b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. For more information, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**. ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| Source | Destination | Port | Typ | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### Nächste Schritte: + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..75e9711a8c1bb --- /dev/null +++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnungen:** +- It is critical that you configure any restrictive access policies you need 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 to 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 %} + +### Vorrausetzungen + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the S3 endpoint URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the S3 bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for S3. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for S3. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for S3. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Nächste Schritte: + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..0529a68935afb --- /dev/null +++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**Warnungen:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} + +### Vorrausetzungen + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### Nächste Schritte: + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..c2697377ad76a --- /dev/null +++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnungen:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} +### Vorrausetzungen +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Nächste Schritte: + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..46a402df723f4 --- /dev/null +++ b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`. + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." diff --git a/translations/de-DE/content/admin/packages/index.md b/translations/de-DE/content/admin/packages/index.md index f73f907259955..9808ef3fde913 100644 --- a/translations/de-DE/content/admin/packages/index.md +++ b/translations/de-DE/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..32bd229f6771c --- /dev/null +++ b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your third-party storage solution. + +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. + +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). + +### 1. Choose a MinIO mode for your needs + +| MinIO mode | Optimized for | Storage infrastructure required | +| ----------------------------------------------- | ------------------------------ | ------------------------------------ | +| Standalone MinIO (on a single host) | Fast setup | N/A | +| MinIO as a NAS gateway | NAS (Network-attached storage) | NAS devices | +| Clustered MinIO (also called Distributed MinIO) | Data security | Storage servers running in a cluster | + +For more information about your options, see the official [MinIO docs](https://docs.min.io/). + +### 2. Install, run, and sign in to MinIO + +1. Set up your preferred environment variables for MinIO. + + These examples use `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Install MinIO. + + ```shell + $ docker pull minio/minio + ``` + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." + +3. Sign in to MinIO using your MinIO access key and secret. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + You can access your MinIO keys using the environment variables: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Run MinIO in your chosen mode. + + * Run MinIO using Docker on a single host: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." + + * Run MinIO using Docker as a NAS gateway: + + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + For more information, see "[MinIO Gateway for NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)." + + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} + +1. Install the MinIO client. + + ```shell + $ docker pull minio/mc + ``` + +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. + + * Local deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + This example can be used for MinIO standalone or MinIO as a NAS gateway. + + * Clustered deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### Nächste Schritte: + +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/de-DE/content/admin/user-management/audited-actions.md b/translations/de-DE/content/admin/user-management/audited-actions.md index a0af914b5f004..aa50b69ea703c 100644 --- a/translations/de-DE/content/admin/user-management/audited-actions.md +++ b/translations/de-DE/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### Teams -| Name | Beschreibung | -| --------------:| ------------------------------------------------------------------- | -| `team.create` | Einem Team wurde ein Benutzerkonto oder ein Repository hinzugefügt. | -| `team.delete` | Ein Benutzerkonto oder Repository wurde aus einem Team entfernt. | -| `team.destroy` | Ein Team wurde gelöscht. | +| Name | Beschreibung | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | Einem Team wurde ein Benutzerkonto oder ein Repository hinzugefügt. | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### Benutzer -| Name | Beschreibung | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | Einem Benutzerkonto wurde eine E-Mail-Adresse hinzugefügt. | -| `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` | Ein neues Benutzerkonto wurde erstellt. | -| `user.delete` | Ein Benutzerkonto wurde durch einen asynchronen Auftrag vernichtet. | -| `user.demote` | Ein Websiteadministrator wurde auf ein gewöhnliches Benutzerkonto zurückgestuft. | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | Ein Benutzer hat versucht, sich mit einem falschen Benutzernamen, Passwort oder Zwei-Faktor-Authentifizierungscode anzumelden. | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | Ein Benutzer hat sich angemeldet. | -| `user.promote` | Ein gewöhnliches Benutzerkonto wurde auf einen Websiteadministrator hochgestuft. | -| `user.remove_email` | Eine E-Mail-Adresse wurde aus einem Benutzerkonto entfernt. | -| `user.rename` | Ein Benutzernamen wurde geändert. | -| `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` | Ein Websiteadministrator hat die Sperrung eines Benutzerkontos aufgehoben. | +| Name | Beschreibung | +| -------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | Einem Benutzerkonto wurde eine E-Mail-Adresse hinzugefügt. | +| `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` | Ein neues Benutzerkonto wurde erstellt. | +| `user.delete` | Ein Benutzerkonto wurde durch einen asynchronen Auftrag vernichtet. | +| `user.demote` | Ein Websiteadministrator wurde auf ein gewöhnliches Benutzerkonto zurückgestuft. | +| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | Ein Benutzer hat versucht, sich mit einem falschen Benutzernamen, Passwort oder Zwei-Faktor-Authentifizierungscode anzumelden. | +| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} +| `user.login` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `user.promote` | Ein gewöhnliches Benutzerkonto wurde auf einen Websiteadministrator hochgestuft. | +| `user.remove_email` | Eine E-Mail-Adresse wurde aus einem Benutzerkonto entfernt. | +| `user.rename` | Ein Benutzernamen wurde geändert. | +| `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` | Ein Websiteadministrator hat die Sperrung eines Benutzerkontos aufgehoben. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [Deployment-Schlüssel]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index aee1962af8094..11c571cc703dc 100644 --- a/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,13 +4,18 @@ 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: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -Mittels Markdown können Sie Ihre Meldung formatieren. Weitere Informationen finden Sie unter „[Informationen zum Schreiben und Formatieren bei {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)“. +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ Mittels Markdown können Sie Ihre Meldung formatieren. Weitere Informationen fin {% endnote %} +Mittels Markdown können Sie Ihre Meldung formatieren. Weitere Informationen finden Sie unter „[Informationen zum Schreiben und Formatieren bei {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)“. + ### Benutzerdefinierte Meldung für Anmeldung erstellen {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Klicken Sie unter „Sign in page“ (Anmeldeseite) auf **Add message** (Meldung hinzufügen) oder **Edit message** (Meldung bearbeiten). ![Schaltfläche „Edit message“ (Meldung bearbeiten)](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Geben Sie unter **Sign in message** (Meldung für Anmeldung) die Meldung an, die Benutzern angezeigt werden soll. ![Meldung für Anmeldung](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Geben Sie unter **Sign in message** (Meldung für Anmeldung) die Meldung an, die Benutzern angezeigt werden soll. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Schaltfläche „Preview“ (Vorschau)](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. Überprüfen Sie die dargestellte Meldung. ![Dargestellte Meldung für Anmeldung](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### Benutzerdefinierte Meldung für Abmeldung erstellen @@ -37,12 +45,35 @@ Mittels Markdown können Sie Ihre Meldung formatieren. Weitere Informationen fin {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Klicken Sie unter „Sign out page“ (Abmeldeseite) auf **Add message** (Meldung hinzufügen) oder **Edit message** (Meldung bearbeiten). ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Geben Sie unter **Sign out message** (Meldung für Abmeldung) die Meldung an, die Benutzern angezeigt werden soll. ![two_factor_auth_header-Meldung signieren](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Geben Sie unter **Sign out message** (Meldung für Abmeldung) die Meldung an, die Benutzern angezeigt werden soll. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Schaltfläche „Preview“ (Vorschau)](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. Überprüfen Sie die dargestellte Meldung. ![Dargestellte Meldung für Abmeldung](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Creating a global announcement banner @@ -50,9 +81,8 @@ Mittels Markdown können Sie Ihre Meldung formatieren. Weitere Informationen fin You can set a global announcement banner to be displayed to all users at the top of every page. {% 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)." - +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)." {% else %} You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." @@ -62,9 +92,8 @@ You can also set an announcement banner in the administrative shell using a comm {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. Klicken Sie unter „Sign in page“ (Anmeldeseite) auf **Add message** (Meldung hinzufügen) oder **Edit message** (Meldung bearbeiten). ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Schaltfläche „Add message“ (Meldung hinzufügen)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", use the calendar drop-down menu, and select an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. Optionally, to see what the banner will look like, click **Preview**. ![Schaltfläche „Preview“ (Vorschau)](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Klicke auf **Save changes** (Änderungen speichern). ![Schaltfläche „Edit message“ (Meldung bearbeiten)](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md b/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md index 70b79256766f6..cc3826e2c1a77 100644 --- a/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ Exchange this `code` for an access token: ##### Parameters -| Name | Typ | Beschreibung | -| --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `Code` | `string` | **Required.** The code you received as a response to Step 1. | -| `redirect_uri` | `string` | The URL in your application where users are sent after authorization. | -| `state` | `string` | The unguessable random string you provided in Step 1. | +| Name | Typ | Beschreibung | +| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `Code` | `string` | **Required.** The code you received as a response to Step 1. | +| `redirect_uri` | `string` | The URL in your application where users are sent after authorization. | +| `state` | `string` | The unguessable random string you provided in Step 1. | ##### Response @@ -213,7 +213,7 @@ Once the user has authorized, the app will receive an access token that can be u #### Rate limits for the device flow -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). diff --git a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 9bbbd7e6f06a5..74fe373fdace8 100644 --- a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ A CI server hosts code that runs CI tests such as code linters (which check styl The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: diff --git a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md index b1331ee4fb425..a3468779eb1a3 100644 --- a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Available scopes -| Name | Beschreibung | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Name | Beschreibung | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | -|  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | -|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | +| **`repo`** | 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](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | -|  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | -|  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | -| **`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. | -| **`benachrichtigungen`** | 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. | -| **`Benutzer`** | 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. | +|  `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% 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. | +| **`benachrichtigungen`** | 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. | +| **`Benutzer`** | 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)". | +| **`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. | +| **`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 %} diff --git a/translations/de-DE/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 15ede21ee3044..592796f7b2f9c 100644 --- a/translations/de-DE/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/de-DE/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Viewing transactions for your listing -intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transations 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.' +intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index fe8fb67ade47f..098f07762a54a 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ You can archive a classroom that you no longer use on {% data variables.product. {% data reusables.classroom.click-settings %} 1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **Lies die Warnungen.**. -1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md index 14b39274adde3..e53db4553c172 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -18,7 +18,7 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to directly replace the outdated dependency with the new version. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." -If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% data reusables.dependabot.dependabot-tos %} @@ -43,3 +43,7 @@ You can configure version updates for repositories that contain a dependency man {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." diff --git a/translations/de-DE/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/de-DE/content/github/administering-a-repository/about-merge-methods-on-github.md index beacd385c679c..e38c784314054 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/de-DE/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -Die Standard-Mergemethode erzeugt einen Merge-Commit. Du kannst verhindern, dass Merge-Commits an einen geschützten Branch übertragen werden, indem Du einen linearen Commit-Verlauf erzwingst. Weitere Informationen findest Du unter „[Einen linearen Commit-Verlauf verlangen](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +Die Standard-Mergemethode erzeugt einen Merge-Commit. Du kannst verhindern, dass Merge-Commits an einen geschützten Branch übertragen werden, indem Du einen linearen Commit-Verlauf erzwingst. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### Deine Merge-Commits squashen diff --git a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md index 3a1bc4712a419..d27a13c8e0151 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,142 @@ --- title: Informationen zu geschützten Branches -intro: 'Mit geschützten Branches wird sichergestellt, dass Mitarbeiter auf Deinem Repository keine unwiderruflichen Änderungen an Branches vornehmen. Durch die Aktivierung geschützter Branches kannst Du außerdem weitere optionale Prüfungen und Anforderungen aktivieren, beispielsweise erforderliche Statuschecks und erforderliche Reviews.' +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### Informationen zu geschützten Branches +### About branch protection rules -{% data reusables.pull_requests.about-protected-branches %} Du kannst entscheiden, Einschränkungen zu erzwingen über die Art und Weise, wie ein Pull Request in Dein Repository zusammengeführt wird. +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -Durch das Erstellen von Regeln für geschützte Branches können Repository-Inhaber und Personen mit Administratorberechtigung für ein Repository bestimmte Workflows oder Anforderungen erzwingen, bevor ein Mitarbeiter einen Branch in Dein Repository überführen kann. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -{% data reusables.repositories.branch-rules-example %} Weitere Informationen findest Du unter „[Geschützte Branches konfigurieren](/articles/configuring-protected-branches/).“ +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -### Priorisierung von Regeln für geschützte Branches +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. Weitere Informationen über den Basisbranch findest Du unter „[Über Pull Requests](/articles/about-pull-requests)." + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. Weitere Informationen finden Sie unter „[Einen Pull-Request-Review ablehnen](/articles/dismissing-a-pull-request-review)“. + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +Mithilfe von erforderlichen Statuschecks wird sichergestellt, dass alle erforderlichen CI-Tests bestanden werden, bevor Mitarbeiter Änderungen an einem geschützten Branch vornehmen können. Weitere Informationen findest Du unter „[Geschützte Branches konfigurieren](/articles/configuring-protected-branches/)“ und „[Erforderliche Statuschecks aktivieren](/articles/enabling-required-status-checks)“. Weitere Informationen findest Du unter „[Über Statuschecks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." + +Bevor Du erforderliche Statusprüfungen aktivieren kannst, musst Du das Repository für die Verwendung des Status-API konfigurieren. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. Nachdem alle erforderlichen Statuschecks durchlaufen sind, müssen alle Commits entweder in einen anderen Branch übertragen und dann zusammengeführt oder direkt in den geschützten Branch übertragen werden. + +{% note %} + +**Hinweis:** Jede Person oder Integration mit Schreibberechtigungen auf ein Repository kann den Zustand von Statuschecks im Repository festlegen. {% data variables.product.company_short %} verifiziert nicht, dass der Autor eines Checks autorisiert ist, einen Check mit einem bestimmten Namen zu erstellen oder einen vorhandenen Status zu ändern. Vor dem Zusammenführen eines Pull Request solltest Du überprüfen, dass der Autor jedes im Merge-Feld aufgeführten Status erwartet wird. + +{% endnote %} + +Du kannst die erforderlichen Statusprüfungen entweder als "loose" (locker) oder als "strict" (streng) einrichten. The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| Art des erforderlichen Statuschecks | Einstellung | Merge-Anforderungen | Erwägungen | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Streng** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist aktiviert. | Der Branch **muss** vor dem Zusammenführen auf dem Stand des Basisbranches sein. | Dies ist das Standardverhalten für erforderliche Statuschecks. Weitere Builds können erforderlich sein, da Du den Head-Branch auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests in den geschützten Basisbranch überführt haben. | +| **Locker** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist **nicht** aktiviert. | Der Branch muss vor dem Zusammenführen **nicht** auf dem Stand des Basisbranches sein. | Es sind weniger Builds erforderlich, da Du den Head-Branch nicht auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests überführt haben. Statuschecks schlagen nach dem Zusammenführen Deines Branches möglicherweise fehl, wenn inkompatible Änderungen am Basisbranch vorliegen. | +| **Deaktiviert** | Das Kontrollkästchen **Require status checks to pass before merging** (Statuschecks müssen vor dem Zusammenführen bestanden werden) ist **deaktiviert**. | Für den Branch gelten keine Merge-Einschränkungen. | Wenn die erforderlichen Statuschecks nicht aktiviert sind, können Mitarbeiter den Branch unabhängig von seinem Stand gegenüber dem Basisbranch jederzeit zusammenführen. Die Wahrscheinlich inkompatibler Änderungen erhöht sich dadurch jedoch. | + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### Require signed commits + +When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. Weitere Informationen findest Du unter „[Über die Verifikation von Commit-Signaturen](/articles/about-commit-signature-verification)." + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +Du kannst jederzeit lokale Commits zum Branch übertragen, wenn die Commits signiert und verifiziert sind. {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. Weitere Informationen findest Du unter "[Pull Requests lokal ausckecken](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)." + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. Dies bedeutet, dass alle Pull Requests, die in den geschützten Branch zusammengeführt sind, einen Squash-Merge oder einen Rebase-Merge verwenden müssen. A strictly linear commit history can help teams reverse changes more easily. Weitere Informationen über Merge-Methoden findest Du unter „[Über Pull-Request-Merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + +Bevor Du einen linearen Commit-Verlauf verlangen kannst, muss Dein Repository Squash-Merge oder Rebase-Merge erlauben. Weitere Informationen findest Du unter „[Konfigurieren von Pull-Request-Merges](/github/administering-a-repository/configuring-pull-request-merges)." + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using +{% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. + +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. + +#### Allow force pushes -Wenn es für ein Repository mehrere Regeln für geschützte Branches gibt, die dieselben Branches betreffen, haben die Regeln, die einen spezifischen Branch-Namen enthalten, die höchste Priorität. Wenn es mehr als eine Regel für geschützte Branches gibt, die auf den gleichen spezifischen Branch-Namen verweist, hat die zuerst erstellte Branch-Regel eine höhere Priorität. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. Wenn Du erzwungene Pushes zu einem geschützten Branch aktivierst, kann jeder Benutzer mit mindestens Schreibberechtigungen im Repository Pushes zum Branch erzwingen, inbegriffen Benutzer mit Administratorberechtigungen. -Regeln für geschützte Branches mit einem Sonderzeichen, wie `*`, `?` oder `]`, werden in der Reihenfolge ihrer Erstellung angewendet, sodass ältere Regeln mit diesen Zeichen eine höhere Priorität haben. +Das Aktivieren erzwungener Pushes wird keine anderen Branch-Schutzregeln überschreiben. Wenn ein Branch beispielsweise einen linearen Commit-Verlauf verlangt, kannst Du keine Merge-Commit-Pushes zu diesem Branch erzwingen. -### Einstellungen für geschützte Branches +{% 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. Weitere Informationen findest Du unter „[Blockieren von erzwungenen Pushes zu Repositorys, die einem Benutzerkonto oder einer Organisation gehören](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -When you create a branch protection rule in a repository, collaborators cannot force push to the protected branch or delete the branch{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}. Du kannst andere Branch-Schutzeinstellungen aktivieren. Weitere Informationen findest Du unter „[Definieren der Zusammenführbarkeit von Pull Requests](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)." +Wenn ein Websiteadministrator erzwungene Pushes nur auf den Standardbranch blockiert hat, kannst Du erzwungene Pushes trotzdem für jeden anderen geschützten Branch aktivieren.{% endif %} -### Weiterführende Informationen +#### Allow deletions -- „[Informationen zu erforderlichen Statuschecks](/articles/about-required-status-checks)“ -- „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests)“ -- „[Informationen zur obligatorischen Commit-Signatur](/articles/about-required-commit-signing)“ +Standardmäßig kannst Du einen geschützten Branch nicht löschen. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/de-DE/content/github/administering-a-repository/about-releases.md b/translations/de-DE/content/github/administering-a-repository/about-releases.md index 3484d2fdaa3c9..13e7d66859b62 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-releases.md +++ b/translations/de-DE/content/github/administering-a-repository/about-releases.md @@ -25,7 +25,7 @@ Du kannst Benachrichtigungen erhalten, wenn neue Releases in einem Repository ve Alle Personen mit Lesezugriff auf ein Repository können Releases anzeigen und vergleichen, aber nur Personen mit Schreibberechtigungen für ein Repository können Releases verwalten. Weitere Informationen findest Du unter „[Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md b/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md index e695704f83be3..91c5473fb9eb5 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + Wenn Dein Projekt mit einem externen Dienst kommuniziert, verwende allenfalls ein Token oder einen privaten Schlüssel für die Authentifizierung. Token und private Schlüssel sind Beispiele für Geheimnisse, die ein Dienstanbieter ausstellen kann. Wenn Du ein Geheimnis in ein Repository einfügst, kann jedermann mit Lesezugriff auf das Repository das Geheimnis verwenden, um mit Deinen Privilegien auf den externen Dienst zuzugreifen. Wir empfehlen, dass Du Geheimnisse an einem dedizierten, sicheren Ort außerhalb Deines Projekt-Repositorys speicherst. +Service providers can partner with -Wenn jemand ein Geheimnis von einem {% data variables.product.company_short %}-Partner in ein öffentliches oder privates Repository einfügt, dann kann {% data variables.product.prodname_secret_scanning %} das Geheimnis entdecken und Dir helfen, die Auswirkungen des Lecks zu mildern. +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} -Dienstleister können mit {% data variables.product.company_short %} zusammenarbeiten, um ihre geheimen Formate zum Durchsuchen bereitzustellen. For more information, see "[Secret scanning](/partnerships/secret-scanning)." +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### Informationen über {% data variables.product.prodname_secret_scanning %} für öffentliche Repositorys - {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)." +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. Wenn Du in ein öffentliches Repository überträgst, wird {% data variables.product.product_name %} den Inhalt des Commit auf Geheimnisse durchsuchen. Wenn Du ein privates Repository auf öffentlich umstellst, wird {% data variables.product.product_name %} das gesamte Repository nach Geheimnissen durchsuchen. -Wenn Du in ein öffentliches Repository überträgst, wird {% data variables.product.product_name %} den Inhalt des Commit auf Geheimnisse durchsuchen. Wenn Du ein privates Repository auf öffentlich umstellst, wird {% data variables.product.product_name %} das gesamte Repository nach Geheimnissen durchsuchen. - -Wenn {% data variables.product.prodname_secret_scanning %} einen Satz von Anmeldeinformationen erkennt, benachrichtigen wir den Dienstanbieter, der das Geheimnis ausgegeben hat. Der Dienstanbieter prüft die Anmeldeinformationen und entscheidet dann, ob er das Geheimnis widerrufen, ein neues Geheimnis ausstellen oder sich direkt an Dich wenden soll, was von den damit verbundenen Risiken für Dich oder den Dienstleister abhängt. +Wenn {% data variables.product.prodname_secret_scanning %} einen Satz von Anmeldeinformationen erkennt, benachrichtigen wir den Dienstanbieter, der das Geheimnis ausgegeben hat. Der Dienstanbieter prüft die Anmeldeinformationen und entscheidet dann, ob er das Geheimnis widerrufen, ein neues Geheimnis ausstellen oder sich direkt an Dich wenden soll, was von den damit verbundenen Risiken für Dich oder den Dienstleister abhängt. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." {% data variables.product.product_name %} durchsucht derzeit öffentliche Repositorys nach Geheimnissen, die von den folgenden Dienstanbietern veröffentlicht wurden. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### Informationen zu {% data variables.product.prodname_secret_scanning %} für private Repositorys +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for private repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization. {% data variables.product.prodname_secret_scanning_caps %} is not available for user account-owned private repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} -Wenn Du Commits in ein privates Repository überträgst, das {% data variables.product.prodname_secret_scanning %} aktiviert hat, wird {% data variables.product.product_name %} den Inhalt des Commits nach Geheimnissen durchsuchen. +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." -Wenn {% data variables.product.prodname_secret_scanning %} ein Geheimnis in einem privaten Repository entdeckt, wird {% data variables.product.prodname_dotcom %} Warnungen senden. +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. + +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. - {% data variables.product.prodname_dotcom %} sendet E-Mail-Warnungen zu den Repository-Administratoren und den Organisations-Inhabern. - {% data variables.product.prodname_dotcom %} zeigt eine Warnung im Repository an. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." - -To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." - -{% data variables.product.product_name %} durchsucht derzeit private Repositorys nach Geheimnissen, die von den folgenden Dienstanbietern veröffentlicht wurden. - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} @@ -128,4 +71,4 @@ To monitor results from {% data variables.product.prodname_secret_scanning %} ac ### Weiterführende Informationen - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- „[Ihr Konto und Ihre Daten schützen](/github/authenticating-to-github/keeping-your-account-and-data-secure)“ +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md b/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md index e8389335b49c7..abb3eb130d521 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md @@ -3,6 +3,7 @@ title: About securing your repository intro: '{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Setting up your repository securely @@ -13,6 +14,7 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +{% if currentVersion == "free-pro-team@latest" %} - **Security policy** Make it easy for people to confidentially report security vulnerabilities they've found in your repository. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)“. @@ -24,18 +26,32 @@ The first step to securing a repository is to set up who can see and modify your - **{% data variables.product.prodname_dependabot_alerts %} and security updates** View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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)." + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **{% data variables.product.prodname_dependabot %} version updates** +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. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)“. + {% endif %} - 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. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)“. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** +View any secrets that - View any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: diff --git a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md index 78d33ab7d6c4d..4b70f591e8928 100644 --- a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..370e25d0358c7 --- /dev/null +++ b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +Du kannst eine *secret_scanning.yml*-Datei verwenden, um Verzeichnisse von {% data variables.product.prodname_secret_scanning %} auszuschließen. Beispielsweise kannst Du Verzeichnisse ausschließen, welche Tests oder zufällig generierte Inhalte enthalten. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. Gib im Feld „Dateiname" *.github/secret_scanning.yml* ein. +4. Gib unter **Edit new file** (Neue Datei bearbeiten) `paths-ignore:` ein, gefolgt von den Pfaden, die Du von {% data variables.product.prodname_secret_scanning %} ausschließen willst. + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + Du kannst Sonderzeichen wie `*` verwenden, um Pfade zu filtern. Weitere Informationen zu Filtermustern findest Du unter „[Workflow-Syntax für GitHub-Aktionen](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)." + + {% note %} + + **Hinweise:** + - Wenn es mehr als 1.000 Einträge in `paths-ignore` gibt, wird {% data variables.product.prodname_secret_scanning %} nur die ersten 1.000 Verzeichnisse von Scans ausschließen. + - Wenn *secret_scanning.yml* größer als 1 MB ist, wird {% data variables.product.prodname_secret_scanning %} die ganze Datei ignorieren. + + {% endnote %} + +Du kannst auch einzelne Warnungen von {% data variables.product.prodname_secret_scanning %} ignorieren. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)." + +### Weiterführende Informationen + +- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/de-DE/content/github/administering-a-repository/index.md b/translations/de-DE/content/github/administering-a-repository/index.md index 45b6724fc5a3f..e4aa25b154942 100644 --- a/translations/de-DE/content/github/administering-a-repository/index.md +++ b/translations/de-DE/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/de-DE/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/de-DE/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..874688fa030ad --- /dev/null +++ b/translations/de-DE/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Weil {% data variables.product.company_short %} das `File::FNM_PATHNAME`-Flag für die `File.fnmatch`-Syntax verwendet, wird der Platzhalter das Verzeichnistrennzeichen (`/`) nicht abgleichen. Zum Beispiel wird `qa/*` alle Branches mit `qa/` abgleichen und einen einzigen Schrägstrich enthalten. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. Weitere Informationen zu den Syntax-Optionen für Branch-Regeln findest Du in der [fnmatch-Dokumentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). + +Wenn es für ein Repository mehrere Regeln für geschützte Branches gibt, die dieselben Branches betreffen, haben die Regeln, die einen spezifischen Branch-Namen enthalten, die höchste Priorität. Wenn es mehr als eine Regel für geschützte Branches gibt, die auf den gleichen spezifischen Branch-Namen verweist, hat die zuerst erstellte Branch-Regel eine höhere Priorität. + +Regeln für geschützte Branches mit einem Sonderzeichen, wie `*`, `?` oder `]`, werden in der Reihenfolge ihrer Erstellung angewendet, sodass ältere Regeln mit diesen Zeichen eine höhere Priorität haben. + +Um eine Ausnahme für eine vorhandene Branch-Regel zu erstellen, erstellst Du eine neue Branch-Schutzregel mit höherer Priorität, z. B. eine Branch-Regel für einen bestimmten Branch-Namen. + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Kontrollkästchen für Einschränkungen bei Pull-Request-Reviews](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Dropdownmenü zur Auswahl der Anzahl an erforderlichen genehmigenden Reviews](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![Kontrollkästchen „Dismiss stale pull request approvals when new commits are pushed“ (Alte Pull-Request-Genehmigungen verwerfen, wenn neue Commits übertragen werden)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. Weitere Informationen findest Du unter „[Über Codeinhaber](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Review von Codeinhabern erforderlich](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. Weitere Informationen findest Du unter „[Einen Pull-Request-Review ablehnen](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review).“ ![Kontrollkästchen „Restrict who can dismiss pull request reviews“ (Einschränken, wer Pull-Request-Reviews verwerfen kann)](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. + - Aktivieren Sie **Require status checks to pass before merging** (Statuschecks müssen vor dem Mergen bestanden werden). ![Option für erforderliche Statuschecks](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![Kontrollkästchen für lockere oder strenge erforderliche Statuschecks](/assets/images/help/repository/protecting-branch-loose-status.png) + - Wähle aus der Liste der verfügbaren Statuschecks diejenigen Prüfungen, die Du verlangen willst. ![Liste der verfügbaren Statuschecks](/assets/images/help/repository/required-statuses-list.png) +1. Optionally, select **Require signed commits**. ![Option „Require signed commits“ (Verlange signierte Commits)](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. ![Option „Required linear history" (Erforderter linearer Verlauf)](/assets/images/help/repository/required-linear-history.png) +1. Optional wähle **Include administrators** (Administratoren einbeziehen) aus. ![Kontrollkästchen „Include administrators“ (Administratoren einbeziehen)](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. ![Kontrollkästchen „Branch restriction" (Branch-Einschränkung)](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![Suche für die Branch-Einschränkung](/assets/images/help/repository/restrict-branch-search.png) +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Option „Allow force pushes" (Erlaube erzwungene Pushes)](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. ![Option „Allow branch deletions" (Erlaube Branch-Löschungen)](/assets/images/help/repository/allow-branch-deletions.png) +1. Klicke auf **Create** (Erstellen). + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to edit, click **Edit**. ![Schaltfläche „Edit" (Bearbeiten)](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Klicke auf **Save changes** (Änderungen speichern). ![Schaltfläche „Edit message“ (Meldung bearbeiten)](/assets/images/help/repository/save-branch-protection-rule.png) + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to delete, click **Delete**. ![Schaltfläche „Delete" (Löschen)](/assets/images/help/repository/delete-branch-protection-rule.png) 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 e6e30e49301f3..2bd8ee83ac451 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 @@ -4,6 +4,7 @@ intro: Du kannst Warnungen für Geheimnisse, welche in Deinem Repository geprüf product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. Klicke in der linken Seitenleiste auf **Detected secrets** (Erkannte Geheimnisse). ![Schaltfläche "Detected secrets" (Erkannte Geheimnisse)](/assets/images/help/repository/sidebar-secrets.png) -4. Klicke unter „Secret scanning" (nach Geheimnissen durchsuchen) auf die Warnung, die Du ansehen willst. ![Liste der Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Benutze optional das Dropdownmenü „Resolve" (Auflösen) und klicke auf den Grund für die Auflösung der Warnung. ![Dropdownmenü für das Auflösen von Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. Klicke unter „Secret scanning" (nach Geheimnissen durchsuchen) auf die Warnung, die Du ansehen willst. + {% if currentVersion == "free-pro-team@latest" %} + ![Liste der Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Liste der Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![Dropdownmenü für das Auflösen von Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Dropdownmenü für das Auflösen von Warnungen aus „secret scanning" (Durchsuchen nach Geheimnissen)](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### Kompromittierte Geheimnisse sichern Sobald ein Geheimnis an ein Repository übergeben wurde, solltest Du das Geheimnis als kompromittiert betrachten. {% data variables.product.prodname_dotcom %} empfiehlt die folgenden Aktionen für kompromittierte Geheimnisse: - Bei einem kompromittierten, persönlichen {% data variables.product.prodname_dotcom %}-Zugriffstoken, lösche das kompromittierte Token, erstelle ein neues Token und aktualisiere alle Dienste, die das alte Token verwenden. Weitere Informationen findest Du unter „[Ein persönliches Zugriffstoken für die Befehlszeile erstellen](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line).“ -- Für alle anderen Geheimnisse überprüfe zuerst, dass das zu {% data variables.product.prodname_dotcom %} übergebene Geheimnis gültig ist. Falls ja, erstelle ein neues Geheimnis, aktualisiere alle Dienste, die das alte Geheimnis nutzen und lösche dann das alte Geheimnis. +- Für alle anderen Geheimnisse überprüfe zuerst, dass das zu {% data variables.product.product_name %} übergebene Geheimnis gültig ist. Falls ja, erstelle ein neues Geheimnis, aktualisiere alle Dienste, die das alte Geheimnis nutzen und lösche dann das alte Geheimnis. diff --git a/translations/de-DE/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index 957b83f2df9a9..95e2c23fe462a 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -5,7 +5,7 @@ intro: 'You can choose whether {% data variables.large_files.product_name_long % permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ versions: {% data variables.product.product_name %} creates source code archives of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. -{% if currentVersion != "github-ae@latest" %} +{% if currentVersion == "free-pro-team@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. Each account receives {% data variables.large_files.initial_bandwidth_quota %} per month of bandwidth for free, and you can pay for additional usage. For more information, see "[About storage and bandwidth usage](/github/managing-large-files/about-storage-and-bandwidth-usage)" and "[Managing billing for {% 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 %} diff --git a/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md index 4ccc4a820c4b3..fa275b7bc0b1f 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### About release management diff --git a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 8440bfee12a89..25c042da2db3a 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### Sicherheits- und Analysefunktionen aktivieren oder deaktivieren +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### Zugriff auf Sicherheitsmeldungen gewähren @@ -35,7 +53,13 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. ![Suchfeld, um Personen oder Teams Zugriff auf Sicherheitsmeldungen zu gewähren](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. + {% if currentVersion == "free-pro-team@latest" %} + ![Suchfeld, um Personen oder Teams Zugriff auf Sicherheitsmeldungen zu gewähren](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Suchfeld, um Personen oder Teams Zugriff auf Sicherheitsmeldungen zu gewähren](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. Klicke auf **Save changes** (Änderungen speichern). ![Schaltfläche "Save changes" (Änderungen speichern) für Änderungen an den Einstellungen der Sicherheitsmeldungen](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### Zugriff auf Sicherheitsmeldungen entfernen @@ -43,7 +67,14 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. ![Schaltfläche "x" um den Zugriff einer Person auf Sicherheitsmeldungen Deines Repository zu entfernen](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + ![Schaltfläche "x" um den Zugriff einer Person auf Sicherheitsmeldungen Deines Repository zu entfernen](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Schaltfläche "x" um den Zugriff einer Person auf Sicherheitsmeldungen Deines Repository zu entfernen](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) diff --git a/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md b/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md index 5d8569526d021..eb895dec72ff4 100644 --- a/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,8 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ We recommend reviewing the following caveats before you change the visibility of #### Repository als öffentlich festlegen * {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Sobald Dein Repository der Öffentlichkeit zugänglich ist, kannst Du im Community-Profil des Repositorys überprüfen, ob Dein Projekt die Best Practices zur Unterstützung von Mitarbeitern erfüllt. Weitere Informationen finden Sie unter „[Community-Profil anzeigen](/articles/viewing-your-community-profile)“.{% endif %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Sobald Dein Repository der Öffentlichkeit zugänglich ist, kannst Du im Community-Profil des Repositorys überprüfen, ob Dein Projekt die Best Practices zur Unterstützung von Mitarbeitern erfüllt. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} diff --git a/translations/de-DE/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/de-DE/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..ec24c36aceb55 --- /dev/null +++ b/translations/de-DE/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: Fehlerbehebung von erforderlichen Statuschecks +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. Dadurch wird sichergestellt, dass Dein Branch mit dem neuesten Code aus dem Basisbranch getestet wurde. Wenn Dein Branch veraltet ist, musst Du den Basisbranch in Deinen Branch zusammenführen. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ + +{% note %} + +**Note:** Mit Git rebase kannst Du Deinen Branch auch auf den Basisbranch aktualisieren. Weitere Informationen findest Du unter „[Informationen zu Git rebase](/github/using-git/about-git-rebase).“ + +{% endnote %} + +Du kannst lokale Änderungen erst dann an einen geschützten Branch übertragen, wenn alle erforderlichen Statuschecks bestanden sind. Ansonsten erhalten Sie eine Fehlermeldung ähnlich der folgenden. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. Dies kann ohne Statuschecks erfolgen, die auf dem Merge-Commit selbst ausgeführt werden. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +Manchmal werden sich die Ergebnisse der Statuschecks für den Test-Merge-Commit und Head-Commit widersprechen. If the test merge commit has a status, the test merge commit must pass. Anderenfalls muss der Status des Head-Commit bestanden sein, bevor Du den Branch zusammenführen kannst. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![Branch mit widersprüchlichen Merge-Commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md index a06df387640b1..3d9f4b836e45f 100644 --- a/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -19,15 +19,17 @@ Du kannst Commits und Tags lokal signieren, sodass andere Personen überprüfen Wenn ein Commit oder Tag eine Signatur hat, die nicht verifiziert werden kann, wird der Commit oder das Tag von {% data variables.product.product_name %} als nicht verifiziert gekennzeichnet. -Repository-Administratoren können die obligatorische Commit-Signatur auf einem Branch erzwingen, um alle Commits zu blockieren, die nicht signiert und verifiziert sind. Weitere Informationen findest Du unter „[Informationen zur obligatorischen Commit-Signatur](/articles/about-required-commit-signing).“ +Repository-Administratoren können die obligatorische Commit-Signatur auf einem Branch erzwingen, um alle Commits zu blockieren, die nicht signiert und verifiziert sind. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-signed-commits).“ Du kannst den Verifizierungsstatus Deines signierten Commits oder Tags auf {% data variables.product.product_name %} überprüfen und sehen, warum Deine Commit-Signaturen möglicherweise nicht verifiziert sind. Weitere Informationen findest Du unter „[Verifizierungsstatus Deiner Commit- und Tag-Signaturen überprüfen](/articles/checking-your-commit-and-tag-signature-verification-status).“ -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. Commits, die von {% data variables.product.product_name %} signiert sind, werden auf {% data variables.product.product_name %} einen verifizierten Status haben. Du kannst die Signatur lokal mit dem unter https://github.com/web-flow.gpg verfügbaren öffentlichen Schlüssel verifizieren.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits, die von {% data variables.product.product_name %} signiert sind, werden auf {% data variables.product.product_name %} einen verifizierten Status haben. Sie können die Signatur lokal mit dem unter https://github.com/web-flow.gpg verfügbaren öffentlichen Schlüssel verifizieren. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} ### GPG-Verifizierung einer Commit-Signatur -Du kannst GPG verwenden, um Commits mit einem GPG-Schlüssel zu signieren, den Du selbst generierst. +Sie können GPG verwenden, um Commits mit einem GPG-Schlüssel zu signieren, den Sie selbst generieren. {% data variables.product.product_name %} verwendet OpenPGP-Bibliotheken, um zu bestätigen, dass Deine lokal signierten Commits und Tags kryptographisch mit einem öffentlichen Schlüssel verifizierbar sind, den Du zu Deinem {% data variables.product.product_name %}-Konto hinzugefügt hast. @@ -42,19 +44,19 @@ Um Commits mit GPG zu signieren und diese Commits auf {% data variables.product. ### S/MIME-Verifizierung einer Commit-Signatur -Du kannst S/MIME verwenden, um Commits mit einem von Deiner Organisation ausgegebenen X.509-Schlüssel zu signieren. +Sie können S/MIME verwenden, um Commits mit einem von Ihrer Organisation ausgegebenen X.509-Schlüssel zu signieren. -{% data variables.product.product_name %} verwendet [das Debian-CA-Zertifikatspaket](https://packages.debian.org/hu/jessie/ca-certificates), den gleichen Trust Store, der auch von Mozilla-Browsern verwendet wird, um zu bestätigen, dass Deine lokal signierten Commits und Tags kryptographisch mit einem öffentlichen Schlüssel in einem vertrauenswürdigen Stammzertifikat verifizierbar sind. +{% data variables.product.product_name %} verwendet [das Debian-CA-Zertifikatpaket](https://packages.debian.org/hu/jessie/ca-certificates), den gleichen Trust Store, der auch von Mozilla-Browsern verwendet wird, um zu bestätigen, dass Ihre lokal signierten Commits und Tags kryptographisch mit einem öffentlichen Schlüssel in einem vertrauenswürdigen Stammzertifikat verifizierbar sind. {% data reusables.gpg.smime-git-version %} -Um Commits mit S/MIME zu signieren und diese Commits auf {% data variables.product.product_name %} verifizieren zu lassen, führe die folgenden Schritte aus: +Um Commits mit S/MIME zu signieren und diese Commits auf {% data variables.product.product_name %} verifizieren zu lassen, führen Sie die folgenden Schritte aus: 1. [Informiere Git über Deinen Signaturschlüssel](/articles/telling-git-about-your-signing-key) 2. [Signiere Commits](/articles/signing-commits) 3. [Signiere Tags](/articles/signing-tags) -Du musst Deinen öffentlichen Schlüssel nicht auf {% data variables.product.product_name %} hochladen. +Sie müssen Ihren öffentlichen Schlüssel nicht auf {% data variables.product.product_name %} hochladen. {% if currentVersion == "free-pro-team@latest" %} ### Signaturverifizierung für Bots diff --git a/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md index 9204a9374750d..234da34d92fcb 100644 --- a/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -39,13 +39,14 @@ The events listed in your security log are triggered by your actions. Actions ar | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} | [`account_recovery_token`](#account_recovery_token-category-actions) | Umfasst alle Aktivitäten in Verbindung mit dem [Hinzufügen eines Wiederherstellungstokens](/articles/configuring-two-factor-authentication-recovery-methods). | | [`Abrechnung`](#billing-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Ihren Abrechnungsinformationen. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)." | | [`marketplace_agreement_signature (Unterzeichnung Marketplace-Vereinbarung)`](#marketplace_agreement_signature-category-actions) | Umfasst alle Aktivitäten in Verbindung mit der Signierung der {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung. | | [`marketplace_listing (Eintrag auf Marketplace)`](#marketplace_listing-category-actions) | Umfasst alle Aktivitäten in Verbindung mit dem Eintragen von Apps auf {% 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) | Umfasst alle Aktivitäten in Verbindung mit der Bezahlung Ihres {% data variables.product.prodname_dotcom %}-Abonnements.{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Ihrem Profilbild. | +| [`payment_method`](#payment_method-category-actions) | Umfasst alle Aktivitäten in Verbindung mit der Bezahlung Deines {% data variables.product.prodname_dotcom %}-Abonnements.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Deinem Profilbild. | | [`project (Projekt)`](#project-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Projektboards. | -| [`public_key`](#public_key-category-actions) | Umfasst alle Aktivitäten in Verbindung mit [Ihren öffentlichen SSH-Schlüsseln](/articles/adding-a-new-ssh-key-to-your-github-account). | +| [`public_key`](#public_key-category-actions) | Umfasst alle Aktivitäten in Verbindung mit [Deinen öffentlichen SSH-Schlüsseln](/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" %} @@ -82,6 +83,12 @@ An overview of some of the most common actions that are recorded as events in th | `change_billing_type` | Wird ausgelöst, wenn Sie Ihre [Zahlungsmethode](/articles/adding-or-editing-a-payment-method) für {% data variables.product.prodname_dotcom %} ändern. | | `change_email` | Wird ausgelöst, wenn Du [Deine E-Mail-Adresse änderst](/articles/changing-your-primary-email-address). | +#### `codespaces` category actions + +| Aktion | Beschreibung | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### `marketplace_agreement_signature` category actions | Aktion | Beschreibung | @@ -227,26 +234,25 @@ An overview of some of the most common actions that are recorded as events in th #### `user` category actions -| Aktion | Beschreibung | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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` | Wird ausgelöst, wenn Sie Ihr Passwort ändern. | -| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} -| `hide_private_contributions_count` | Wird ausgelöst, wenn Sie [private Beiträge in Ihrem Profil verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | -| `login` | Wird ausgelöst, wenn Du Dich bei {% data variables.product.product_location %} anmeldest. | -| `failed_login` | Wird ausgelöst, wenn Ihre Anmeldung fehlschlägt. | -| `remove_email` | Wird ausgelöst, wenn Sie eine E-Mail-Adresse entfernen. | -| `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} -| `report_content` | Wird ausgelöst, wenn Sie [ein Issue oder einen Pull Request bzw. einen Kommentar zu einem Issue, einem Pull Request oder einem Commit melden](/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 %} +| Aktion | Beschreibung | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} +| `create` | Triggered when you create a new user account.{% if currentVersion != "github-ae@latest" %} +| `change_password` | Wird ausgelöst, wenn Sie Ihr Passwort ändern. | +| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count` | Wird ausgelöst, wenn Sie [private Beiträge in Ihrem Profil verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | +| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -#### `user_status` category actions -| Aktion | Beschreibung | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `aktualisieren` | Wird ausgelöst, wenn Du den Status Deines Profils festlegst oder änderst. Weitere Informationen findest Du unter „[Status festlegen](/articles/personalizing-your-profile/#setting-a-status).“ | -| `destroy` | Wird ausgelöst, wenn Du den Status Deines Profils löschst. | +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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 +| Aktion | Beschreibung | +| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aktualisieren` | Wird ausgelöst, wenn Sie den Status Ihres Profils festlegen oder ändern. Weitere Informationen findest Du unter „[Status festlegen](/articles/personalizing-your-profile/#setting-a-status).“ | +| `destroy` | Wird ausgelöst, wenn Sie den Status Ihres Profils löschen. | diff --git a/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index e1669792972b2..c79520dcf678a 100644 --- a/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ Wenn jemand Zugriff auf Deinen Computer erlangt, kann er mit SSH-Schlüsseln zud Durch Eingabe des folgenden Befehls kannst Du die Passphrase für einen vorhandenen privaten Schlüssel ändern, ohne das Schlüsselpaar erneut zu genieren: ```shell -$ ssh-keygen -p -# Start des Prozesses zur SSH-Schluesselerstellung -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/de-DE/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/de-DE/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index 0a176775054f2..b89d8cd19c1ff 100644 --- a/translations/de-DE/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/de-DE/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ If the code of conduct you want to use isn't available in the provided templates 3. In the file name field, type the name and extension for the file. ![New code of conduct file name](/assets/images/help/repository/new-code-of-conduct-file-name.png) - To make your code of conduct visible in the repository's root directory, type *CODE_OF_CONDUCT* in the file name field. - To make your code of conduct visible in the repository's `docs` directory, type *docs/CODE_OF_CONDUCT*. - - To make your code of conduct visible in the respository's `.github` directory, type *.github/CODE_OF_CONDUCT*. + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. 4. In the new file, add your custom code of conduct. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 24a0da89bf53e..e0a7999833ebd 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,7 +74,7 @@ Wenn ein Branch geschützt ist, trifft Folgendes zu: - Wenn die erforderlichen Statuschecks für den Branch aktiviert sind, kannst Du Änderungen erst dann in den Branch zusammenführen, wenn alle erforderlichen CI-Tests bestanden sind. Weitere Informationen findest Du unter „[Informationen zu Statuschecks](/articles/about-status-checks).“ - Wenn erforderliche Pull-Request-Reviews auf dem Branch aktiviert sind, kannst Du Änderungen erst dann in den Branch zusammenführen, wenn alle Anforderungen der Richtlinie für Pull-Request-Reviews erfüllt sind. Weitere Informationen findest Du unter „[Einen Pull Request zusammenführen](/articles/merging-a-pull-request).“ - Wenn der erforderliche Review von einem Codeinhaber auf einem Branch aktiviert ist und der Code mit einem Inhaber durch einen Pull Request geändert wird, muss ein Codeinhaber den Pull Request genehmigen, bevor er zusammengeführt werden kann. Weitere Informationen findest Du unter „[Informationen zu Codeinhabern](/articles/about-code-owners).“ -- Wenn die obligatorische Commit-Signatur auf einem Branch aktiviert ist, kannst Du keine Commits an den Branch übertragen, die nicht signiert und verifiziert sind. 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" %} +- Wenn die obligatorische Commit-Signatur auf einem Branch aktiviert ist, kannst Du keine Commits an den Branch übertragen, die nicht signiert und verifiziert sind. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. Weitere Informationen findest Du unter „[Einen Mergekonflikt auf {% data variables.product.prodname_dotcom %} beheben](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github).“{% endif %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 9a38cbb4817ff..dcccbd4762e4e 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,9 +44,7 @@ Du kannst alle Reviews eines Pull Requests in der Zeitleiste der Unterhaltung an ### Erforderliche Reviews -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -Weitere Informationen findest Du unter „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests).“ +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% tip %} @@ -57,6 +55,5 @@ Weitere Informationen findest Du unter „[Informationen zu erforderlichen Revie ### Weiterführende Informationen - „[Vorgeschlagene Änderungen in einem Pull Request prüfen](/articles/reviewing-proposed-changes-in-a-pull-request)“ -- „[Erforderliche Reviews für Pull Requests aktivieren](/articles/enabling-required-reviews-for-pull-requests)“ - „[Einen Pull-Request-Review anzeigen](/articles/viewing-a-pull-request-review)“ - „[Richtlinien für Repository-Mitarbeiter festlegen](/articles/setting-guidelines-for-repository-contributors)“ diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index df67ea62132dc..d54bb12fffb89 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -Weitere Informationen zu erforderlichen Reviews findest Du unter „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests).“ +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -Du kannst Pull Requests kommentieren, die Änderungen genehmigen oder vor der Genehmigung Verbesserungen anfordern. Weitere Informationen findest Du unter „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests)“ und „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request).“ +Du kannst Pull Requests kommentieren, die Änderungen genehmigen oder vor der Genehmigung Verbesserungen anfordern. Weitere Informationen findest Du unter „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request).“ {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ Du kannst Pull Requests kommentieren, die Änderungen genehmigen oder vor der Ge ### Weiterführende Informationen -- „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests)“ - „[Vorgeschlagene Änderungen in einem Pull Request prüfen](/articles/reviewing-proposed-changes-in-a-pull-request)“ - „[Einen Pull Request kommentieren](/articles/commenting-on-a-pull-request)“ diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 8395d69192344..76f9c9e9d5b7f 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ Commits sind nur an Pull-Request-Branches möglich, auf die Folgendes zutrifft: - sie sind in einem Repository geöffnet, auf das Du Push-Zugriff hast, und wurden von einem Fork dieses Repositorys erstellt - sie sind auf einer benutzereigenen Fork - sie haben die Berechtigung des Pull-Request-Erstellers erhalten -- sie haben keine [Branch-Einschränkungen](/articles/about-branch-restrictions), die Dich am freigeben hindern +- Für sie gelten keine [Branch-Einschränkungen](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches), die das Committen verhindern. Nur der Benutzer, der den Pull Request erstellt hat, kann Dir die Erlaubnis erteilen, Commits zu seinem Branch zu übertragen. Weitere Informationen findest Du unter „[Änderungen an einem Pull-Request-Branch zulassen, der von einem Fork erstellt wurde](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork).“ diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index b9a4d2fac6528..d2ed5484824d9 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Einen Pull-Request-Review verwerfen -intro: 'Wenn Dein Repository [Reviews voraussetzt](/articles/about-required-reviews-for-pull-requests), kannst Du Pull-Request-Reviews verwerfen, die nicht mehr gültig sind oder vom Reviewer nicht genehmigt werden können.' +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ Dies ändert den Status des Reviews zu einem Review-Kommentar. Wenn Du einen Rev - „[Informationen zu Pull-Request-Reviews](/articles/about-pull-request-reviews)“ - „[Vorgeschlagene Änderungen in einem Pull Request prüfen](/articles/reviewing-proposed-changes-in-a-pull-request)“ -- „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests)“ +- „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)“ \ No newline at end of file diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index 637323575aa5a..4556636078773 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### Den GitHub-Flow befolgen 1. [Erstelle einen Branch](/articles/creating-and-deleting-branches-within-your-repository) vom Repository. -2. [Erstelle](/articles/creating-new-files) und [bearbeite](/articles/editing-files) Dateien, [benenne sie um](/articles/renaming-a-file), [verschiebe](/articles/moving-a-file-to-a-new-location) oder [lösche sie](/articles/deleting-files). +2. [Erstelle](/articles/creating-new-files) und [bearbeite](/articles/editing-files) Dateien, [benenne sie um](/articles/renaming-a-file), [verschiebe](/articles/moving-a-file-to-a-new-location) oder [lösche sie](/github/managing-files-in-a-repository/deleting-files-in-a-repository). 3. [Sende einen Pull Request](/articles/creating-a-pull-request) von Deinem Branch, der Deine vorgeschlagenen Änderungen enthält, um eine Diskussion anzustoßen. 4. Nimm nach Bedarf Änderungen an Deinem Branch vor. Dein Pull Request wird automatisch aktualisiert werden. 5. [Führe den Pull Request zusammen](/articles/merging-a-pull-request), sobald der Branch für den Merge bereit ist. diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 57c71e9a466f9..6d7925179017c 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### Informationen zum Zusammenführen von Pull Requests -Mit einem Pull Request schlägst Du vor, dass Änderungen, die Du an einem Head-Branch gemacht hast, in einen Basis-Branch zusammengeführt werden sollten. {% data reusables.pull_requests.about-protected-branches %} Es kann jedoch Einschränkungen geben, wann Du einen Pull Request zu einem bestimmten Branch zusammenführen kannst. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“ +Mit einem Pull Request schlägst Du vor, dass Änderungen, die Du an einem Head-Branch gemacht hast, in einen Basis-Branch zusammengeführt werden sollten. Standardmäßig kann jeder Pull Request jederzeit zusammengeführt werden, es sei denn, der Head-Branch steht in Konflikt mit dem Basisbranch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“ {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 308d7f0f335ce..3d042481667c5 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ Dependency review supports the same languages and package management ecosystems ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ Dependency review supports the same languages and package management ecosystems * The severity of the vulnerability. * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. -1. You can return to the original view of the file by clicking the source diff button. - - ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 16b08f16b6fe1..1b6c3dec11faa 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,9 +36,11 @@ If the pull request contains changes to dependencies you can use the dependency {% data reusables.repositories.changed-files %} -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### Datei als „gesehen“ markieren @@ -65,5 +67,5 @@ Wenn Sie den Review der Dateien des Pull Requesta abgeschlossen haben, senden Si ### Weiterführende Informationen -- „[Informationen zu erforderlichen Reviews für Pull Requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)“ +- „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)“ - „[Pull Requests nach Review-Status filtern](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)“ diff --git a/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 46a73a0c89b88..40a3796589bc1 100644 --- a/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/de-DE/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,9 +26,19 @@ Organisationen können die E-Mail-Adresse `name@organization.com` als öffentlic ### Commits mit einem `on-behalf-of`-Badge in der Befehlszeile erstellen -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Gib Deine Commit-Mitteilung ein und eine kurze, aussagekräftige Beschreibung Deiner Änderungen. Füge nach Deiner Commit-Beschreibung zwei Leerzeilen statt eines abschließenden Anführungszeichens hinzu. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} -2. Gib in der nächsten Zeile der Commit-Mitteilung `on-behalf-of: @org ` ein, gefolgt von einem abschließenden Anführungszeichen. +2. Geben Sie in der nächsten Zeile der Commit-Mitteilung `on-behalf-of: @org ` ein, gefolgt von einem abschließenden Anführungszeichen. ```shell $ git commit -m "Refactor usability tests. 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 5617bd73201f0..01f1b8027193f 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 @@ -39,7 +39,17 @@ Sie können mit {% data variables.product.prodname_desktop %} einen Commit mit e {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Gib Deine Commit-Mitteilung ein und eine kurze, aussagekräftige Beschreibung Deiner Änderungen. Füge nach Deiner Commit-Beschreibung zwei Leerzeilen statt eines abschließenden Anführungszeichens hinzu. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tipp:** Wenn Du auf der Befehlszeile einen Texteditor verwendest, um Deine Commit-Mitteilung einzugeben, stelle sicher, dass es zwei Zeilenumbrüche hat zwischen dem Ende Deiner Commit-Beschreibung und dem `Co-authored-by:` Commit-Trailer. + + {% endtip %} 3. Gib in der nächsten Zeile der Commit-Mitteilung `Co-authored-by: name ` mit spezifischen Informationen zu jedem Co-Autor ein. Füge nach den Angaben zu den Co-Autoren ein abschließendes Anführungszeichen ein. diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 1d19152e5dee2..48d5d43d9c47c 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -19,7 +19,7 @@ Die Personen, die Du als Codeinhaber auswählst, müssen Schreibberechtigung fü Code-Besitzer werden automatisch zur Überprüfung aufgefordert, wenn jemand einen Pull Request öffnet, der den Code ändert, den sie besitzen. Code-Besitzer werden nicht automatisch aufgefordert, Entwürfe für Pull Requests zu überprüfen. Weitere Informationen zu Entwürfen von Pull Requests finden Sie unter „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)“. Code-Besitzer werden nicht automatisch aufgefordert, Entwürfe für Pull Requests zu überprüfen. Wenn Du einen Pull Request in einen Entwurf konvertierst, werden Personen, die bereits Benachrichtigungen abonniert haben, nicht automatisch abgemeldet. Weitere Informationen findest Du unter „[Den Zustand eines Pull Requests ändern](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request).“ -Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlichen Reviews aktiviert hat, kann er optional auch die Genehmigung von einem Codeinhaber anfordern, bevor der Autor einen Pull Request im Repository zusammenführen kann. Weitere Informationen findest Du unter „[Erforderliche Reviews für Pull Requests aktivieren](/github/administering-a-repository/enabling-required-reviews-for-pull-requests).“ +Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlichen Reviews aktiviert hat, kann er optional auch die Genehmigung von einem Codeinhaber anfordern, bevor der Autor einen Pull Request im Repository zusammenführen kann. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).“ {% 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. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index c0202a16e9f85..d7b2f8d472e06 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ Jede Person und Organisation kann unbegrenzte Repositorys besitzen und eine unbe {% endif %} You can use repositories to manage your work and collaborate with others. -- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." -- {% data reusables.discussions.you-can-use-discussions %} +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - You can use pull requests to propose changes to a repository. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).“ - You can use project boards to organize and prioritize your issues and pull requests. Weitere Informationen findest Du unter „[Informationen zu Projektboards](/github/managing-your-work-on-github/about-project-boards).“ diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 94d8995a0c38a..d8f6cd3596982 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ Wenn Du nach einer Lizenz einer Familie suchst, enthalten die Suchergebnisse all ### Eine Lizenz erkennen -[Das Open-Source-Ruby-Gem Licensee](https://github.com/benbalter/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/rest/reference/licenses) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](http://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[Das Open-Source-Ruby-Gem Licensee](https://github.com/licensee/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/rest/reference/licenses) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](http://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). Wenn Dein Repository eine Lizenz verwendet, die auf der Website „Choose a License“ (Wähle eine Lizenz) aufgeführt ist, und die Lizenz nicht deutlich sichtbar oben auf der Repository-Seite angezeigt wird, enthält das Repository möglicherweise mehrere Lizenzen oder es liegt eine andere Komplexität vor. Damit Deine Lizenz erkannt wird, vereinfache Deine *LICENSE*-Datei und notiere die Komplexität an anderer Stelle, beispielsweise in der *README*-Datei Deines Repositorys. diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/de-DE/content/github/developing-online-with-codespaces/about-codespaces.md index d7c5252b3575f..2e5b61490b605 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ Jeder Entwickler kann ein oder mehrere Codespaces für jedes öffentliche Reposi {% data reusables.codespaces.about-personalization %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Konto personalisieren](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/index.md b/translations/de-DE/content/github/developing-online-with-codespaces/index.md index 1497ebfb4efd8..927e9f54d1dca 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/index.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/de-DE/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/de-DE/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/de-DE/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..dd0f0e6b17a97 --- /dev/null +++ b/translations/de-DE/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Klicke auf **Save changes** (Änderungen speichern). + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Lies die Warnung, dann klicke auf **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/de-DE/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/de-DE/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/de-DE/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index 7a5472fa47981..bddff961c832b 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ Weiter Informationen findest Du unter „[Personalisierung](https://docs.microso {% endnote %} +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." ### Weiterführende Informationen 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 c492e3a3a9637..783872b8ad838 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)." @@ -54,7 +54,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam ### Weiterführende Informationen -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[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 diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index d11a128b1c2ea..612c2f62274d4 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -238,7 +238,9 @@ 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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +The settings in the file are written in YAML format. #### Specifying additional queries 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 6a4690f25589b..d805244f6bd59 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 @@ -40,13 +40,16 @@ You decide how you generate {% data variables.product.prodname_code_scanning %} 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. +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + ### Viewing the logging output from {% 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. {% 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'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 24c418cc57516..43b0e6fa7d5b2 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ You can use the {% data variables.product.prodname_codeql_runner %} to run {% da The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**Hinweise:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} ### Downloading the {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi ### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux In addition to this, each CI server also needs: -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." +- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: 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 521a9cb1faf79..ff5dc52758714 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 @@ -15,7 +15,7 @@ versions: In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the 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. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository 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)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. Weitere Informationen finden Sie unter „[Informationen zu erforderlichen Statuschecks](/github/administering-a-repository/about-required-status-checks)“. +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index 05cc0e7610ba4..9f9f6427bb61b 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### The `init` command takes too long 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 b383522e984e1..ffa47cf1c12ac 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Automatic build for a compiled language fails @@ -83,17 +84,6 @@ For more information about specifying build steps, see "[Configuring the {% data The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. 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)." -### Error: "Server error" - -If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. - -### Error: "Out of disk" or "Out of memory" -On very large projects, - -{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - ### The build takes too long If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. @@ -128,3 +118,54 @@ If you are analyzing code written in Python, you may see different results depen On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." {% endif %} + +### Error: "Server error" + +If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. + +### Error: "Out of disk" or "Out of memory" +On very large projects, + +{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 08bef64061859..dcbfce7282878 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -27,6 +27,8 @@ You can upload the results using {% data variables.product.prodname_actions %}{% - {% data variables.product.prodname_dotcom %} will display {% data variables.product.prodname_code_scanning %} alerts from the uploaded SARIF file in your repository. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, 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)"). - The SARIF file can be generated from a SARIF-compatible analysis tool that you run in the same {% data variables.product.prodname_actions %} workflow used to upload the file. Alternatively, when the file is generated as an artifact outside of your repository, you can push the SARIF file directly to a repository and use a workflow to upload the SARIF file. +{% data reusables.code-scanning.not-available %} + ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %} To upload a third-party SARIF file to {% data variables.product.prodname_dotcom %}, you'll need a {% data variables.product.prodname_actions %} workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..85086387140eb --- /dev/null +++ b/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### Informationen zu {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)“. + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md b/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md index 608c5b1d8db52..acdd8f16296cc 100644 --- a/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: GitHub für Mobilgeräte -intro: 'Du kannst Deine Arbeit auf {% data variables.product.company_short %} von Mobilgeräten her bewerten und verwalten und mit Personen zusammenarbeiten.' +intro: 'Du kannst Deine Arbeit auf {% data variables.product.product_name %} von Mobilgeräten her bewerten und verwalten und mit Personen zusammenarbeiten.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### Informationen zu {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} ist momentan verfügbar für {% data variables.product.prodname_dotcom_the_website %}-Benutzer als Android- und iOS-App. +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} gibt dir die Möglichkeit, schnell und von überall her hochwertige Arbeit auf{% data variables.product.prodname_dotcom %} zu leisten. {% data variables.product.prodname_mobile %} ist ein sicherer Weg für den Zugriff auf Deine {% data variables.product.prodname_dotcom %}-Daten über eine vertrauenswürdige Client-Anwendung aus erster Hand. +{% data variables.product.prodname_mobile %} gibt dir die Möglichkeit, schnell und von überall her hochwertige Arbeit auf{% data variables.product.product_name %} zu leisten. {% data variables.product.prodname_mobile %} ist ein sicherer Weg für den Zugriff auf Deine {% data variables.product.product_name %}-Daten über eine vertrauenswürdige Client-Anwendung aus erster Hand. Mit {% data variables.product.prodname_mobile %} kannst Du: - Verwalten, bewerten und löschen von Benachrichtigungen @@ -23,12 +26,38 @@ Weitere Informationen über Benachrichtigungen für {% data variables.product.pr Für die Installation von {% data variables.product.prodname_mobile %} für Android oder iOS findest Du weitere Informationen auf [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### Vorrausetzungen + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + ### Supported languages for {% data variables.product.prodname_mobile %} {% data variables.product.prodname_mobile %} is available in the following languages. +- Englisch - Japanisch - Brazilian Portuguese +- Simplified Chinese - Spanisch If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. @@ -37,9 +66,9 @@ If you configure the language on your device to a supported language, {% data va {% data variables.product.prodname_mobile %} aktiviert automatisch Universal Links für iOS. Wenn Du auf einen {% data variables.product.product_name %}-Link tippst, wird die Ziel-URL in {% data variables.product.prodname_mobile %} anstatt in Safari geöffnet. Weitere Informationen findest Du unter [Universal Links](https://developer.apple.com/ios/universal-links/) auf der Apple Entwickler Website. -To disable Universal Links, long-press any {% data variables.product.prodname_dotcom %} link, then tap **Open**. Ab jetzt wird jedes Mal, wenn Du auf einen {% data variables.product.prodname_dotcom %}-Link tippst, die Ziel-URL in Safari geöffnet statt in {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Ab jetzt wird jedes Mal, wenn Du auf einen {% data variables.product.product_name %}-Link tippst, die Ziel-URL in Safari geöffnet statt in {% data variables.product.prodname_mobile %}. -Um Universal Links wieder zu aktivieren, drücke lange auf einen {% data variables.product.prodname_dotcom %}-Link und tippe dann auf **Öffnen in {% data variables.product.prodname_dotcom %}**. +Um Universal Links wieder zu aktivieren, drücke lange auf einen {% data variables.product.product_name %}-Link und tippe dann auf **Öffnen in {% data variables.product.prodname_dotcom %}**. ### Feedback teilen diff --git a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md index 7fa752c0cf5c4..189af98ef4a33 100644 --- a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md +++ b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: Produkte von GitHub +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ Um weitere Informationen über das Hosten Deiner eigenen [{% data variables.prod - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} - [{% data variables.product.prodname_learning %} für Organisationen](https://lab.github.com/organizations) -Weitere Informationen zur Anmeldung für {% data variables.product.prodname_ghe_one %} erhältst Du beim [{% data variables.product.product_name %}-Vertriebsteam](https://enterprise.github.com/contact). +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/de-DE/content/github/getting-started-with-github/index.md b/translations/de-DE/content/github/getting-started-with-github/index.md index 9b70ebbe0d9cb..f594e7c215c56 100644 --- a/translations/de-DE/content/github/getting-started-with-github/index.md +++ b/translations/de-DE/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/de-DE/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/de-DE/content/github/getting-started-with-github/keyboard-shortcuts.md index f3f7cbdb3b693..2983f732dc685 100644 --- a/translations/de-DE/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/de-DE/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -33,7 +33,7 @@ Below is a list of some of the available keyboard shortcuts. |-----------|------------ |g c | Go to the **Code** tab |g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." -|g p | Go to the **Pull requests** tab. 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" %} +|g p | Go to the **Pull requests** tab. 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" %} |g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} |g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." |g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." @@ -159,6 +159,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ |command + space or control + space | In the workflow editor, get suggestions for your workflow file. +|g f | Go to the workflow file +|shift + t or T | Toggle timestamps in logs +|shift + f or F | Toggle fullscreen logs +|esc | Exit fullscreen logs {% endif %} diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..22949694da38c --- /dev/null +++ b/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).“ + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. Weitere Informationen finden Sie unter „[Sensible Daten aus einem Repository entfernen](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)“. + +### Deleting a file + +1. Navigiere zu der Datei in Deinem Repository, die Du löschen möchtest. +2. At the top of the file, click +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/index.md b/translations/de-DE/content/github/managing-files-in-a-repository/index.md index 1e00f814a602c..b4bedcaefeac9 100644 --- a/translations/de-DE/content/github/managing-files-in-a-repository/index.md +++ b/translations/de-DE/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/de-DE/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index 31415dbe2c676..57df124c89304 100644 --- a/translations/de-DE/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/de-DE/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ Durch Klicken auf die Zeilennummer kannst Du eine bestimmte Zeile verknüpfen, o ### Daten durchsuchen -Wenn Du in Deinem Datensatz einen bestimmten Wert suchst, gib einfach den Anfang des gesuchten Werts in die Suchleiste über der Datei ein. Die Zeilen werden daraufhin automatisch gefiltert: +Wenn Du in Deinem Datensatz einen bestimmten Wert suchst, gib einfach den Anfang des gesuchten Werts in die Suchleiste über der Datei ein. The rows will filter automatically: ![Suche nach Werten](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/de-DE/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/de-DE/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 214d52fbe7261..73c6d8de1e463 100644 --- a/translations/de-DE/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/de-DE/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ Ein Beispiel: - Wenn Sie eine 500-MB-Datei an {% data variables.large_files.product_name_short %} pushen, nutzen Sie 500 MB Ihres verfügbaren Speichers und keine Bandbreite. Wenn Du eine Änderung von 1 Byte vornimmst und die Datei erneut überträgst, nutzt Du weitere 500 MB Speicherplatz und keine Bandbreite, wodurch Deine Gesamtnutzung für diese beiden Pushes bei 1 GB Speicherplatz und Null Bandbreite liegt. - Wenn Du eine 500-MB-Datei herunterlädst, die mit LFS verfolgt wird, verwendest Du 500 MB der vom Repository-Inhaber zur Verfügung gestellten Bandbreite. Wenn ein Mitarbeiter eine Änderung an eine Datei überträgt und Du die neue Version in Dein lokales Repository lädst, verwendest Du weitere 500 MB Bandbreite, wodurch die Gesamtnutzung für diese beiden Downloads bei 1 GB Bandbreite liegt. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/de-DE/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/de-DE/content/github/managing-large-files/configuring-git-large-file-storage.md index a75c3756ad464..d89fe21b559c6 100644 --- a/translations/de-DE/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/de-DE/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ Wenn in Ihrem Repository bereits Dateien vorhanden sind, für die Sie {% data va ### Weiterführende Informationen -- "[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" %} +- "[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@3.0" or currentVersion == "github-ae@latest" %} - "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 5225874dd2b44..81d619cc6ea03 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -57,7 +57,7 @@ When {% 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)." +{% 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. Weitere Informationen findest Du unter „[ Über {% 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" %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index da8bdc6710be4..b8f9853405df8 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -33,3 +33,7 @@ When you merge a pull request that contains a security update, the corresponding ### Informationen zu Kompatibilitätsbewertungen {% 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. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." \ No newline at end of file diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md index f686f2002b1c9..c1ff39f326486 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -17,7 +17,7 @@ By checking the dependency reviews on pull requests you can avoid introducing vu {% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed 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.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | #### {% data variables.product.prodname_dependabot_security_updates %} -When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." #### {% data variables.product.prodname_dependabot_version_updates %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index 117f8b86ade33..e921768346376 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -13,7 +13,7 @@ versions: ### About configuring {% 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)." +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. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." You can disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository or for all repositories owned by your user account or organization. For more information, see "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories](#managing-dependabot-security-updates-for-your-repositories)" below. @@ -42,16 +42,18 @@ If security updates are not enabled for your repository and you don't know why, ### Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories -You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository. +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} 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)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. Weitere Informationen findest Du unter „[Unterstützte Repositorys](#supported-repositories)." +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Above the list of alerts, use the drop-down menu and select or unselect **{% data variables.product.prodname_dependabot %} security updates**. ![Drop-down menu with the option to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 3bd8bae1cbd78..997e8fce26abc 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ You can configure notification settings for yourself or your organization from t {% note %} -**Note:** You can filter your {% data variables.product.company_short %} inbox notifications to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)." +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." {% endnote %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index dd179ef0df0c7..c6d6ca09fe44a 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,13 +78,15 @@ The best way to resolve this error is to merge or close some of the existing pul #### {% data variables.product.prodname_dependabot %} can't resolve your dependency files -**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a 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**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index d780c025d9a53..9c006c46b109e 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -11,7 +11,7 @@ versions: Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. Mithilfe des Dropdownmenü kannst Du die Liste der Warnungen sortieren, und Du kannst auf bestimmte Warnungen klicken, um weitere Details anzuzeigen. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | -You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% data reusables.repositories.dependency-review %} diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index e5902fcbd6c15..7575b47baada1 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Benachrichtigungen und Abonnements Über ein Abonnement kannst Du festlegen, dass Du Aktualisierungen zu bestimmten Aktivitäten auf {% data variables.product.product_name %} erhalten willst. Benachrichtigungen sind Aktualisierungen, die Du für bestimmte Aktivitäten erhältst, die Du abonniert hast. @@ -50,7 +54,7 @@ Um für Unterhaltungen, die Du automatisch abonniert hast, keine Benachrichtigun ### Benachrichtigungen und Abonnements anpassen -You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. Konfiguriere Deine Benachrichtigungseinstellungen, um die Art von Aktualisierungen anzupassen, die Du erhalten möchtest, und wohin sie gesendet werden sollen. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).” @@ -58,7 +62,7 @@ Um Deine Abonnements übersichtlich zu halten, überprüfe Deine Abonnements und Um anzupassen, wie Du Aktualisierungen für bestimmte Pull Requests oder Issues erhalten möchtest, kannst Du Deine Einstellungen innerhalb des Issues oder Pull Requests konfigurieren. Weitere Informationen findest Du unter „[Eine einzelne Benachrichtigung selektieren](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).” -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} You can enable push notifications in the {% data variables.product.prodname_mobile %} app. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." {% endif %} @@ -89,7 +93,7 @@ Aus Deinem Posteingang heraus kannst Du auch mehrere Benachrichtigungen auf einm ### Deinen Posteingang für Benachrichtigungen anpassen -To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. Zum Beispiel kannst Du einen benutzerdefinierten Filter für ein Open-Source-Projekt erstellen, zu dem Du beiträgst, und nur Benachrichtigungen für das Repository sehen, in dem Du erwähnt bist. Weitere Informationen findest du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." Weitere Beispiele für die Anpassung Deines Selektions-Workflows findest Du unter „[Einen Workflow für das Selektieren Deiner Benachrichtigungen anpassen](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. Zum Beispiel kannst Du einen benutzerdefinierten Filter für ein Open-Source-Projekt erstellen, zu dem Du beiträgst, und nur Benachrichtigungen für das Repository sehen, in dem Du erwähnt bist. Weitere Informationen findest du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." Weitere Beispiele für die Anpassung Deines Selektions-Workflows findest Du unter „[Einen Workflow für das Selektieren Deiner Benachrichtigungen anpassen](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Richtlinie zur Aufbewahrung von Benachrichtigungen diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index fd0b772b8f063..858887a8c543a 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Zustellungsoptionen für Benachrichtigungen You can receive notifications for activity on {% data variables.product.product_name %} in the following locations. - - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Weitere Informationen findest Du auf „[Deine Benachrichtigungseinstellungen wählen](#choosing-your-notification-settings)." {% endif %} @@ -35,7 +39,7 @@ You can receive notifications for activity on {% data variables.product.product_ #### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - Selektieren mehrerer Benachrichtigungen auf einmal. - Erledigte Benachrichtigungen als **Done** (Erledigt) markieren und aus dem Posteingang entfernen. Um alle Deine Benachrichtigungen anzuzeigen, die als **Done** markiert sind, verwende die Abfrage mit `is:done`. - Sichere eine Benachrichtigung für späteren Review. Gesicherte Benachrichtigungen sind in Deinem Posteingang markiert und werden auf unbestimmte Zeit gehalten. Um alle Deine gesicherten Benachrichtigungen zu sehen, benutze die Abfrage mit `is:saved`. @@ -45,7 +49,7 @@ The notifications inbox on {% data variables.product.product_name %}{% if curren - Erstelle benutzerdefinierte Filter, um auf Wunsch auf verschiedene Benachrichtigungen fokussieren zu können. - Gruppiere Benachrichtigungen in Deinem Posteingang nach Repository oder Datum, um einen schnellen Überblick mit weniger Kontextwechseln zu erhalten -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} In addition, the notifications inbox on {% data variables.product.prodname_mobile %} allows you to triage notifications in dark mode and receive push notifications for direct mentions. Weitere Informationen findest Du auf „[Push-Benachrichtigungen mit GitHub for mobile einrichten](#enabling-push-notifications-with-github-for-mobile)" oder auf „[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." {% endif %} @@ -77,7 +81,7 @@ You can customize notifications for a repository, for example, you can choose to #### Participating in conversations Jedes Mal, wenn Du in einer Unterhaltung kommentierst oder wenn jemand Deinen Benutzernamen @erwähnt, bist Du _Teilnehmer_ in einer Unterhaltung. Standardmäßig abonnierst Du automatisch eine Unterhaltung, wenn Du daran teilnimmst. Du kannst Dich manuell von einer Unterhaltung abmelden, an der Du teilgenommen hast, indem Du auf dem Issue oder Pull Request auf **Unsubscribe** (Abmelden) klickst oder durch die Option **Unsubscribe** (Abmelden) im Posteingang für Benachrichtigungen. -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %}. +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. ![Optionen für Teilnahme- und Beobachtungs-Benachrichtigungen](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -85,7 +89,7 @@ Ein Beispiel: - Wenn Du nicht möchtest, dass Benachrichtigungen an Deine E-Mail gesendet werden, deaktiviere **email** (E-Mail) für die Teilnahme und das Beobachten von Benachrichtigungen. - Wenn Du Benachrichtigungen per E-Mail erhalten möchtest, wenn Du an einer Unterhaltung teilgenommen hast, kannst du **email** (E-Mail) unter „Participating" (Teilnehmen) auswählen. -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}, then your notifications inbox will not have any updates. +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. ### E-Mail-Benachrichtigungen anpassen @@ -197,13 +201,15 @@ Wähle, wie Du Aktualisierungen für Workflow-Ausführungen erhalten willst für {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Push-Benachrichtigungen mit {% data variables.product.prodname_mobile %} aktivieren Wenn Du {% data variables.product.prodname_mobile %} installierst, bist Du automatisch für Web-Benachrichtigungen abonniert. Du kannst dann Push-Benachrichtigungen aktivieren für direkte Erwähnungen innerhalb der App. Du kannst im Moment nur Benachrichtigungen für Pushes an Repositorys auf {% data variables.product.prodname_mobile %} erhalten. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Push-Benachrichtigungen mit {% data variables.product.prodname_ios %} aktivieren 1. Oberhalb von „Home", tippe auf Dein Profilfoto. @@ -211,9 +217,11 @@ Du kannst im Moment nur Benachrichtigungen für Pushes an Repositorys auf {% dat 3. Um Deine Benachrichtigungseinstellungen anzupassen, tippe auf **Push notifications** (Push-Benachrichtigungen). 4. Um Push-Benachrichtigungen für direkte Erwähnungen einzuschalten, verwende den Schalter **Direct Mentions** (Direkte Erwähnung). +{% if currentVersion == "free-pro-team@latest" %} #### Push-Benachrichtigungen mit {% data variables.product.prodname_android %} aktivieren 1. Oberhalb von „Home", tippe auf Dein Profilfoto. 2. Um deine Einstellungen zu sehen, tippe auf {% octicon "gear" aria-label="The Gear icon" %}. ![Einstellungssymbol für GitHub for Android](/assets/images/help/mobile/android-settings-icon.png) 3. Um Push-Benachrichtigungen für direkte Erwähnungen einzuschalten, verwende den Schalter **Direct mentions** (Direkte Erwähnung). {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 8a45110eb43b3..88989a4e4d3d8 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: Benachrichtigungen über Deinen Posteingang verwalten -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}.' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Über Deinen Posteingang -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings).“ {% endif %} @@ -86,31 +90,16 @@ Benutzerdefinierte Filter unterstützen im Moment nicht: ### Unterstützte Abfragen für benutzerdefinierte Filter -Es gibt drei Arten von Filtern, die Du verwenden kannst: +These are the types of filters that you can use: - Nach Repository filtern mit `Repo:` - Nach Diskussionstyp filtern mit `is:` - - Nach Benachrichtigungsgrund filtern mit `reason:` - -Um einen `repo:`-Filter hinzuzufügen, musst Du den Inhaber des Repository in der Abfrage einschließen. Beispielsweise repräsentiert `repo:atom/atom` alle Atom-Repositorys, die im Besitz der Atom-Organisation sind. + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -#### Unterstützte `reason:`-Abfragen +#### Supported `repo:` queries -Um Benachrichtigungen nach dem Grund zu filtern, weshalb Du eine Aktualisierung erhalten hast, kannst Du die Abfrage `reason:` (Grund) verwenden. Um beispielsweise Benachrichtigungen zu sehen, in denen Du (oder ein Team, dem Du angehörst) zu einem Pull-Request-Review aufgefordert bist, benutze die Abfrage `reason:review-requested`. Weitere Informationen findest Du unter „[Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications).“ - -| Abfrage | Beschreibung | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| `reason:assign` | Wenn es eine Aktualisierung zu einem Issue oder Pull Request gibt, denen Du zugewiesen bist. | -| `reason:author` | Wenn es eine Aktualisierung oder einen neuen Kommentar zu einem Pull Request oder Issue gibt, die Du eröffnet hast. | -| `reason:comment` | Wenn Du einen Issue, einen Pull Request oder eine Teamdiskussion kommentiert hast. | -| `reason:participating` | Wenn Du einen Issue, einen Pull Request oder eine Teamdiskussion kommentiert hast, oder wenn Du @erwähnt wurdest. | -| `reason:invitation` | Wenn Du in ein Team, eine Organisation oder ein Repository eingeladen wirst. | -| `reason:manual` | Wenn Du auf einem Issue oder Pull Request **Subscribe** (Abonnieren) klickst, die Du noch nicht abonniert hattest. | -| `reason:mention` | Du wurdest direkt @erwähnt. | -| `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:state-change` | Wenn der Status eines Pull Request oder Issue geändert wird. Beispielsweise wird ein Issue geschlossen oder ein Pull Request zusammengeführt. | -| `reason:team-mention` | Wenn ein Team, dem Du angehörst, @erwähnt wird. | -| `reason:ci-activity` | Wenn ein Repository CI-Aktualisierungen hat, wie beispielsweise einen neuen Status für eine Workflow-Ausführung. | +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. #### Unterstützte `is:`-Abfragen @@ -138,3 +127,59 @@ Du kannst die Abfrage `is:` auch verwenden, um zu beschreiben, wie die Benachric - `is:done` - `is:unread` - `is:read` + +#### Unterstützte `reason:`-Abfragen + +Um Benachrichtigungen nach dem Grund zu filtern, weshalb Du eine Aktualisierung erhalten hast, kannst Du die Abfrage `reason:` (Grund) verwenden. Um beispielsweise Benachrichtigungen zu sehen, in denen Du (oder ein Team, dem Du angehörst) zu einem Pull-Request-Review aufgefordert bist, benutze die Abfrage `reason:review-requested`. Weitere Informationen findest Du unter „[Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications).“ + +| Abfrage | Beschreibung | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| `reason:assign` | Wenn es eine Aktualisierung zu einem Issue oder Pull Request gibt, denen Du zugewiesen bist. | +| `reason:author` | Wenn es eine Aktualisierung oder einen neuen Kommentar zu einem Pull Request oder Issue gibt, die Du eröffnet hast. | +| `reason:comment` | Wenn Du einen Issue, einen Pull Request oder eine Teamdiskussion kommentiert hast. | +| `reason:participating` | Wenn Du einen Issue, einen Pull Request oder eine Teamdiskussion kommentiert hast, oder wenn Du @erwähnt wurdest. | +| `reason:invitation` | Wenn Du in ein Team, eine Organisation oder ein Repository eingeladen wirst. | +| `reason:manual` | Wenn Du auf einem Issue oder Pull Request **Subscribe** (Abonnieren) klickst, die Du noch nicht abonniert hattest. | +| `reason:mention` | Du wurdest direkt @erwähnt. | +| `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:state-change` | Wenn der Status eines Pull Request oder Issue geändert wird. Beispielsweise wird ein Issue geschlossen oder ein Pull Request zusammengeführt. | +| `reason:team-mention` | Wenn ein Team, dem Du angehörst, @erwähnt wird. | +| `reason:ci-activity` | Wenn ein Repository CI-Aktualisierungen hat, wie beispielsweise einen neuen Status für eine Workflow-Ausführung. | + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index a38e1da3862e9..45ed766ecd2cb 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ Wenn Du Benachrichtigungen in Deinem Posteingang abmeldest, werden diese automat {% data reusables.notifications.access_notifications %} 1. Wähle im Posteingang für Benachrichtigungen diejenige Benachrichtigungen aus, die Du abmelden möchtest. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Option „Unsubscribe" (Abmelden) aus dem Hauptposteingang](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Abmeldung von Benachrichtigungen auf der Abonnementseite @@ -64,4 +64,4 @@ Wenn Du ein Repository nicht mehr beobachtest, meldest Du Dich von zukünftigen - ein Repository nicht mehr beobachten - ignoriere alle Benachrichtigungen für ein Repository - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md index f58e1b0df4a26..ac56b82cc69d6 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md @@ -14,9 +14,11 @@ versions: Du kannst Feedback von Benutzern sammeln, Softwarefehler melden und Aufgaben organisieren, die Du mit Issues in einem Repository durchführen möchtest. Issues sind mehr als nur ein Ort zum Melden von Softwarefehlern. +{% if currentVersion == "free-pro-team@latest" %} Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/de-DE/content/github/managing-your-work-on-github/changing-project-board-visibility.md index 6b9928cdd6cdb..c7f4cb8750009 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Sichtbarkeit des Projektboards ändern -intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du ein Projektboard als öffentlich oder privat festlegen.' +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**Tipp:** Wenn Du Dein Projektboard als öffentlich festlegst, erhalten Organisationsmitglieder standardmäßig Lesezugriff. Du kannst bestimmten Organisationsmitgliedern Schreib- oder Administratorberechtigungen erteilen, indem Du Teams, denen diese Mitglieder angehören, Zugriff auf das Projektboard gewährst oder die gewünschten Mitglieder als Mitarbeiter zum Projektboard hinzufügst. Weitere Informationen finden Sie unter „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“. +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. Du kannst bestimmten Organisationsmitgliedern Schreib- oder Administratorberechtigungen erteilen, indem Du Teams, denen diese Mitglieder angehören, Zugriff auf das Projektboard gewährst oder die gewünschten Mitglieder als Mitarbeiter zum Projektboard hinzufügst. Weitere Informationen finden Sie unter „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“. {% endtip %} -1. Navigiere zu dem Projektboard, das Du als öffentlich oder privat festlegen möchtest. +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. Wähle unter „Visibility“ (Sichtbarkeit) **Public** (Öffentlich) oder **Private** (Privat) aus. Klicke anschließend auf **Save** (Speichern). ![Optionsfelder „Public“ (Öffentlich) und „Private“ (Privat)](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/de-DE/content/github/managing-your-work-on-github/copying-a-project-board.md index 775ddd114a4f4..2b54a7ba924a0 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ Die Automatisierung eines Projektboards wird ebenfalls standardmäßig aktiviert 5. Optional kannst Du unter „Project board name“ (Name des Projektboards) den Namen des kopierten Projektboards eingeben. ![Feld zum Eingeben eines Namens für das kopierte Projektboard](/assets/images/help/projects/copied-project-board-name.png) 6. Optional kannst Du unter „Description“ (Beschreibung) eine Beschreibung des kopierten Projektboards eingeben, die anderen Benutzern angezeigt wird. ![Feld zum Eingeben einer Beschreibung für das kopierte Projektboard](/assets/images/help/projects/copied-project-board-description.png) 7. Optional kannst Du unter „Automation settings“ (Automatisierungseinstellungen) auswählen, ob Du die konfigurierten automatischen Workflows kopieren möchtest. Die Option ist standardmäßig aktiviert. Weitere Informationen findest Du unter „[Informationen zur Automatisierung für Projektboards](/articles/about-automation-for-project-boards/).“ ![Automatisierungseinstellungen für das kopierte Projektboard auswählen](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. Wenn Du ein Projektboard kopierst, das im Besitz der Organisation ist, wähle unter „Visibility“ (Sichtbarkeit) aus, ob das kopierte Projektboard privat oder öffentlich sein soll. ![Sichtbarkeitseinstellungen für das kopierte Projektboard auswählen](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. Klicke auf **Copy project** (Projekt kopieren). ![Schaltfläche zum Bestätigen des Kopiervorgangs](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md index 792b178fbc6ce..496909dc36b8b 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ Du kannst auch Workflows automatisieren, um Dein Projektboard mit dem Status der {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ Du kannst auch Workflows automatisieren, um Dein Projektboard mit dem Status der {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/de-DE/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 92b5d8f54b5f1..d68ebdb26044c 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: Du kannst die Pull-Request-Liste eines Repositorys filtern, um folgende Pull Requests zu finden: - Pull Requests, deren [Review](/articles/about-pull-request-reviews) noch aussteht -- Pull Requests, für die vor dem Merge [ein Review erforderlich ist](/articles/about-required-reviews-for-pull-requests) +- Pull Requests, für die vor dem Merge [ein Review erforderlich ist](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) - Pull Requests, die ein Reviewer genehmigt hat - Pull Requests, bei denen ein Reviewer um Änderungen gebeten hat - Pull Requests, die Du überprüft hast diff --git a/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md index 3b2956f832ef0..16e806d75a2c8 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: Sie können Ihre Arbeit auf {% data variables.product.product_name %} verwalten, indem Sie Kennzeichnungen für die Kategorisierung von Issues und Pull Requests erstellen. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. -Alle Benutzer mit Lesezugriff auf ein Repository können die Kennzeichnungen des Repositorys einsehen und durchsuchen. Um eine Kennzeichnung zu erstellen, zu bearbeiten, anzuwenden oder zu löschen, benötigst Du Schreibzugriff auf das Repository. +Alle Benutzer mit Lesezugriff auf ein Repository können die Kennzeichnungen des Repositorys einsehen und durchsuchen. Anyone with triage access to a repository can apply/dismiss existing labels. Um eine Kennzeichnung zu erstellen, zu bearbeiten, anzuwenden oder zu löschen, benötigst Du Schreibzugriff auf das Repository. ### About default labels @@ -91,7 +91,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### Weiterführende Informationen -- „[Informationen zu Kennzeichnungen](/articles/about-labels)“ - "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 92e100bcdf184..b5ae45ce70249 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -36,7 +36,7 @@ Für Issues kannst Du die Suche auf für folgendes benutzen: Bei Pull Requests kannst Du die Suche auch verwenden, um: - Pull Requests mit dem Status [Entwurf](/articles/about-pull-requests#draft-pull-requests) zu filtern: `is:draft` - Pull Requests zu filtern, die noch keinem [Review](/articles/about-pull-request-reviews) unterzogen wurden: `state:open type:pr review:none` -- Pull Requests zu filtern, für die ein [Review erforderlich ist](/articles/about-required-reviews-for-pull-requests), bevor sie zusammengeführt werden können: `state:open type:pr review:required` +- Pull Requests zu filtern, für die ein [Review erforderlich ist](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging), bevor sie gemergt werden können: `state:open type:pr review:required`, - Von einem Reviewer genehmigte Pull Requests zu filtern: `state:open type:pr review:approved` - Pull Requests zu filtern, in denen ein Reviewer um Änderungen gebeten hat: `state:open type:pr review:changes_requested` - Pull Requests nach [Reviewer](/articles/about-pull-request-reviews/) zu filtern: `state:open type:pr reviewed-by:octocat` diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-commits.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-commits.md index 8e30daa5c5bed..907942af04333 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-commits.md @@ -48,10 +48,10 @@ Mit den Qualifizierern `author-date` und `committer-date` kannst Du Commits such {% data reusables.search.date_gt_lt %} -| Qualifizierer | Beispiel | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) sucht Commits, die vor dem 1. Januar 2016 verfasst wurden. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) sucht Commits, die nach dem 1. Januar 2016 festgeschrieben wurden. | +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) sucht Commits, die vor dem 1. Januar 2016 verfasst wurden. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | ### Merge-Commits filtern diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index c8bbc96a6f0c9..6f96ab86508e0 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: Auch nachdem Du SAML SSO konfiguriert hast, werden Mitglieder Deiner {% data variables.product.prodname_dotcom %}-Organisation sich weiterhin auf {% data variables.product.prodname_dotcom %} in ihre Benutzerkonten anmelden. Wenn ein Mitglied auf Ressourcen Deiner SAML SSO einsetzenden Organisation zugreift, wird {% data variables.product.prodname_dotcom %} den Benutzer zwecks Authentifizierung zu Deinem IdP umleiten. Nach erfolgreicher Authentifizierung leitet Dein IdP den Benutzer zurück zu {% data variables.product.prodname_dotcom %}, wo er dann auf die Ressourcen Deiner Organisation zugreifen kann. -Enterprise-Inhaber können SAML SSO auch für alle Organisationen in einem Enterprise-Konto erzwingen. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. Weitere Informationen findest Du unter „[SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ If members are signed in with a SAML SSO session when they create a new reposito Organisationsmitglieder müssen auch eine aktive SAML-Sitzung haben, um eine {% data variables.product.prodname_oauth_app %} zu autorisieren. Du kannst Dich von dieser Anforderung abmelden, indem Du {% data variables.contact.contact_support %} kontaktierst. {% data variables.product.product_name %} empfiehlt nicht, sich von dieser Anforderung abzumelden, weil dies Deine Organisation einem höheren Risiko von Kontoübernahmen und potenziellen Datenverlust aussetzt. +{% data reusables.saml.saml-single-logout-not-supported %} + ### Unterstützte SAML-Dienste {% data reusables.saml.saml-supported-idps %} @@ -40,14 +42,14 @@ Einige IdPs unterstützen die Bereitstellung von Zugriffen auf eine {% data var ### Mitglieder zu einer Organisation mit SAML SSO hinzufügen -Nachdem Sie SAML SSO aktiviert haben, gibt es mehrere Möglichkeiten, wie Sie neue Mitglieder zu Ihrer Organisation hinzufügen können. Organisationsinhaber können neue Mitglieder manuell auf {% data variables.product.product_name %} oder über die API einladen. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." - -{% data reusables.organizations.team-synchronization %} +Nachdem Sie SAML SSO aktiviert haben, gibt es mehrere Möglichkeiten, wie Sie neue Mitglieder zu Ihrer Organisation hinzufügen können. Organisationsinhaber können neue Mitglieder manuell auf {% data variables.product.product_name %} oder über das API einladen. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." Um neue Benutzer ohne Einladung eines Organisationsinhabers hinzuzufügen, kannst Du die URL `https://github.com/orgs/ORGANIZATION/sso/sign_up` verwenden und _ORGANIZATION_ durch den Namen Deiner Organisation ersetzen. Du kannst beispielsweise Deinen IdP so konfigurieren, dass jeder, der Zugriff auf den IdP hat, auf einen Link im Dashboard des IdP klicken kann, um Deiner {% data variables.product.prodname_dotcom %}-Organisation beizutreten. Wenn Dein IdP SCIM unterstützt, kann {% data variables.product.prodname_dotcom %} automatisch Mitglieder einladen, Deiner Organisation beizutreten, wenn Du den Zugriff auf Deine IdP erlaubst. Wenn Du den Zugriff eines Mitglieds auf Deine {% data variables.product.prodname_dotcom %}-Organisation auf Deinem SAML IdP entfernst, wird das Mitglied automatisch aus der {% data variables.product.prodname_dotcom %}-Organisation entfernt. Weitere Informationen findest Du unter „[Über SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index cd5d13669cba2..2af131331ad08 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ These identity providers are compatible with the {% data variables.product.produ - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index b99a151cbfd5e..55c5832771d0c 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ Für jeden ausstehenden Mitarbeiter kannst Du alle Einladungen zur Teilnahme an {% data reusables.organizations.people_tab_outside_collaborators %} 5. Klicke auf **X pending collaborators** (X ausstehende Mitarbeiter). ![Schaltfläche "Pending collaborators" (ausstehende Mitarbeiter)](/assets/images/help/organizations/pending-collaborator-list.png) 6. Klicke rechts neben der Person, für die Du Einladungen stornieren möchtest, auf **Cancel invitations** (Einladungen zurückziehen). ![Schaltfläche "Cancel invitation" (Einladung zurückziehen)](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Klicke auf **Cancel invitations for pending collaborators** (Ziehe Einladungen für ausstehende Mitarbeiter zurück). ![Schaltfläche zur Bestätigung der Stornierung](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. Klicke auf **Cancel invitations for pending collaborators** (Ziehe Einladungen für ausstehende Mitarbeiter zurück). ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md index 0e3b701d1711a..6130f88b2c50d 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} @@ -122,7 +121,7 @@ versions: {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} {% link_in_list /connecting-your-identity-provider-to-your-organization %} - {% link_in_list /connecting-your-identity-provider-to-your-organization %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-using-okta %} {% link_in_list /enabling-and-testing-saml-single-sign-on-for-your-organization %} {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 06737d53feb9f..7c807260e6e99 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Managing security and analysis settings for your organization intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.' permissions: Organization owners can manage security and analysis settings for repositories in the organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### About management of security and analysis settings -{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. +{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Enabling or disabling a feature for all existing repositories +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -### Enabling or disabling a feature for all new repositories when they are added +### Enabling or disabling a feature automatically when new repositories are added 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Allowing Dependabot to access private repositories -{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." 1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) 1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. 1. Click **Select repositories**. - +{% endif %} ### Weiterführende Informationen -{% if currentVersion == "free-pro-team@latest" %}- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)" -- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} +- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" - "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index fc0341ae47ab6..ccf3a7fa00c90 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ Wenn ein Organisationsinhaber beispielsweise allen Organisationsmitgliedern Lese ### Sichtbarkeit des Projektboards -{% data reusables.project-management.project-board-visibility %} Du kannst die Sichtbarkeit des Projektboards von privat auf öffentlich und wieder zurück ändern. Weitere Informationen finden Sie unter „[Sichtbarkeit des Projektboards ändern](/articles/changing-project-board-visibility)“. +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Weitere Informationen finden Sie unter „[Sichtbarkeit des Projektboards ändern](/articles/changing-project-board-visibility)“. ### Weiterführende Informationen 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 bac9364ad5d34..7701ea1ecd767 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,91 +43,94 @@ 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** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %}{% if currentVersion == "free-pro-team@latest" %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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 %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| 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#granting-access-to-security-alerts) 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** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### 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 fcb5bd5ba785a..dd8a9367f69c5 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 @@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`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 %} +| [`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 %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. | [`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: @@ -197,7 +197,7 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. #### `dependabot_security_updates` category actions @@ -218,14 +218,14 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `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. +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. {% endif %} @@ -324,10 +324,12 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|-------------------{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). | `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} +| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} | `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. | `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} | `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} @@ -451,7 +453,9 @@ For more information, see "[Restricting publication of {% data variables.product |------------------|------------------- | `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} | `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. @@ -527,7 +531,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `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" %} @@ -536,7 +540,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. +| `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 @@ -559,7 +563,7 @@ For more information, see "[Restricting publication of {% data variables.product | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `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)") @@ -568,7 +572,6 @@ For more information, see "[Restricting publication of {% data variables.product | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` category actions | Action | Description @@ -577,11 +580,12 @@ For more information, see "[Restricting publication of {% data variables.product | `add_repository` | Triggered when a team is given control of a repository. | `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | `change_privacy` | Triggered when a team's privacy level is changed. -| `create` | Triggered when a new team is created. -| `destroy` | Triggered when a team is deleted from the organization. +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} +| `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. -{% endif %} #### `team_discussions` category actions diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 13993ae64ba59..a33aae51d270d 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: Du kannst bis zu fünf IdP-Gruppen mit einem {% data variables.product.prodname_dotcom %} -Team verbinden. Eine IdP-Gruppe kann ohne Einschränkung mehreren {% data variables.product.prodname_dotcom %}-Teams zugewiesen werden. +Team synchronization does not support IdP groups with more than 5000 members. + Sobald ein {% data variables.product.prodname_dotcom %}-Team mit einer IdP-Gruppe verbunden ist, muss Dein IdP-Administrator Änderungen an der Teammitgliedschaft über den Identitätsanbieter durchführen. Du kannst die Teammitgliedschaft nicht mehr über {% data variables.product.product_name %} oder das API verwalten. Alle über den IdP vorgenommenen Änderungen an der Teammitgliedschaft werden im Auditprotokoll von {% data variables.product.product_name %} als Änderungen des Teamsynchronisierungs-Bots angezeigt. Dein IdP wird die Daten der Teammitgliedschaft einmal pro Stunde an {% data variables.product.prodname_dotcom %} senden. Beim Verbinden eines Teams mit einer IdP-Gruppe werden unter Umständen einige Teammitglieder entfernt. Weitere Informationen findest Du unter „[Anforderungen an Mitglieder synchronisierter Teams](#requirements-for-members-of-synchronized-teams).“ @@ -27,21 +29,24 @@ Du kannst die Teamsynchronisierung auch mit dem API verwalten. For more informat ### Anforderungen an Mitglieder synchronisierter Teams -Nachdem Du ein Team mit einer IdP-Gruppe verbunden hast, werden Mitgliederdaten für jedes Teammitglied synchronisiert, wenn die Person sich weiterhin mit SAML SSO mit der gleichen SSO-Identität auf {% data variables.product.prodname_dotcom %} authentifiziert, und wenn die Person ein Mitglied der verbundenen IdP-Gruppe bleibt. +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -Bestehende Teams oder Gruppenmitglieder können auf {% data variables.product.prodname_dotcom %} automatisch aus dem Team entfernt werden. Bestehende Teams oder Gruppenmitglieder, die sich nicht beim Organisations- oder Enterprise-Konto mit SSO authentifizieren, können den Zugriff auf Repositorys verlieren. Alle existierenden Teams oder Gruppenmitglieder, die nicht in der verbundenen IdP-Gruppe sind, können möglicherweise den Zugriff auf Repositorys verlieren. +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." Sobald sich das entfernte Teammitglied jedoch wieder mit SSO bei der Organisations oder beim Enterprise-Konto authentifiziert und der verbundenen IdP-Gruppe hinzugefügt ist, kann es automatisch wieder in das Team aufgenommen werden. -Um zu verhindern, dass Teammitglieder versehentlich aus einem Team entfernt werden, empfehlen wir innerhalb der Organisations oder dem Enterprise-Konto die Erzwingung des SAML SSO, die Erstellung neuer Teams zur Synchronisierung der Mitgliederdaten und die Überprüfung der IdP-Gruppenmitgliedschaften vor der Synchronisierung bestehender Teams. Weitere Informationen findest Du unter „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization).“ +Um zu verhindern, dass Teammitglieder versehentlich aus einem Team entfernt werden, empfehlen wir innerhalb der Organisations oder dem Enterprise-Konto die Erzwingung des SAML SSO, die Erstellung neuer Teams zur Synchronisierung der Mitgliederdaten und die Überprüfung der IdP-Gruppenmitgliedschaften vor der Synchronisierung bestehender Teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Wenn Deine Organisation im Besitz eines Enterprise-Kontos ist, wird die Aktivierung der Teamsynchronisierung für das Enterprise-Konto Deine Einstellungen für die Teamsynchronisierung auf Organisationsebene überschreiben. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Wenn Deine Organisation im Besitz eines Enterprise-Kontos ist, wird die Aktivierung der Teamsynchronisierung für das Enterprise-Konto Deine Einstellungen für die Teamsynchronisierung auf Organisationsebene überschreiben. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." ### Vorrausetzungen -Bevor Du ein Team mit einer Identitätsanbieter-Gruppe verbinden kannst, muss ein Organisations- oder Enterprise-Inhaber die Teamsynchronisierung für Dein Organisations- oder Enterprise-Konto aktivieren. Weitere Informationen findest Du unter „[Teamsynchronisierung für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" und „[Sicherheitseinstellungen für Dein Enterprise-Konto durchsetzen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Bevor Du ein Team mit einer Identitätsanbieter-Gruppe verbinden kannst, muss ein Organisations- oder Enterprise-Inhaber die Teamsynchronisierung für Dein Organisations- oder Enterprise-Konto aktivieren. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." -Um zu vermeiden, dass Team-Mitglieder unbeabsichtigt entfernt werden, besuche das administrative Portal Deines IdP und bestätige, dass jedes aktuelle Teammitglied auch in der IdP-Gruppe vorhanden ist, die Du mit diesem Team verbinden willst. Wenn Du keinen Zugriff auf das Administratorenportal Deines Identitätsanbieters hast, bitte Deinen IdP-Administrator um die Überprüfung. +Um zu vermeiden, dass Team-Mitglieder unbeabsichtigt entfernt werden, besuche das administrative Portal Deines IdP und bestätige, dass jedes aktuelle Teammitglied auch in der IdP-Gruppe vorhanden ist, die Du mit diesem Team verbinden willst. Wenn Sie keinen Zugriff auf das Administratorportal Ihres Identity Providers haben, bitten Sie Ihren IdP-Administrator um die Überprüfung. Du musst Dich mit SAML SSO authentifizieren. Weitere Informationen findest Du unter „[Authentifizierung mit SAML Single Sign-On](/articles/authenticating-with-saml-single-sign-on).“ diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index b592016e5bcda..ef08a475e5ff0 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ Du kannst die verknüpfte Identität, die aktiven Sitzungen und die autorisierte {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..f8e9441c103dc --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. + +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..9ffac5db1a019 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. + +For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: + +- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). +- Cancel any existing invitations for the user to join an organization owned by your enterprise account. + +For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: + +- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. + +If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." + +To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index c58eab41758ea..a45c7a75f437a 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ Nachdem Du SCIM aktiviert hast, stehen Dir folgende Bereitstellungsfunktionen f 1. To the right of the drop-down menu, type `.*.*`. 1. Klicke auf **Save** (Speichern). {% data reusables.saml.okta-view-setup-instructions %} -1. Enable SAML for your enterprise account using the information in the setup instructions. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +1. Enable SAML for your enterprise account using the information in the setup instructions. Weitere Informationen findest Du unter „[SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." ### Creating groups in Okta diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..5719127314291 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %} Weitere Informationen findest Du unter „[Informationen über Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)." + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %} Weitere Informationen findest Du auf „[Anzeigen und Verwalten des SAML-Zugriffs eines Benutzers auf Dein Enterprise-Konto](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Hinweis:** Wenn Du die Authentifizierung mit SAML Single Sign-On für Dein Enterprise-Konto aktivierst, werden alle bestehenden SAML-Konfigurationen auf Organisationsebene überschrieben. + +{% endnote %} + +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Wähle unter „SAML single sign-on“ (SAML Single Sign-On) **Enable SAML authentication** (SAML-Authentifizierung aktivieren) aus. ![Kontrollkästchen zum Aktivieren von SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. Gib im Feld **Sign on URL** (Sign-On-URL) den HTTPS-Endpunkt für Deinen IdP für Single Sign-On-Anforderungen ein. Diesen Wert findest Du in der IdP-Konfiguration. ![Feld für die URL, auf die Mitglieder bei der Anmeldung weitergeleitet werden](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Feld für den Namen des SAML-Ausstellers](/assets/images/help/saml/saml_issuer.png) +8. Füge unter **Public Certificate** (Öffentliches Zertifikat) ein Zertifikat ein, um die SAML-Antworten zu verifizieren. ![Feld für das öffentliche Zertifikat des Identity Providers](/assets/images/help/saml/saml_public_certificate.png) +9. Um die Integrität der Anforderungen von Ihrem SAML-Aussteller zu überprüfen, klicken Sie auf {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Dropdownmenüs für die Hash-Algorithmen für die Signaturmethode und Digest-Methode, die Dein SAML-Aussteller verwendet](/assets/images/help/saml/saml_hashing_method.png) +10. Bevor Du SAML SSO für Dein Unternehmen aktivierst, klicke auf **Test SAML configuration** (SAML-Konfiguration testen), um sicherzustellen, dass die eingegebenen Informationen korrekt sind. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/saml/saml_test.png) +11. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 8d2a072103818..4a7599411410c 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ Du kannst auch zugelassene IP-Adressen für eine einzelne Organisation konfiguri {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren - -{% data reusables.saml.dotcom-saml-explanation %} Weitere Informationen findest Du unter „[Informationen über Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)." - -Enterprise-Inhaber können SAML SSO und zentralisierte Authentifizierung über einen SAML IdP in allen Organisationen eines Enterprise-Kontos ermöglichen. Wenn Du SAML SSO für Dein Enterprise-Konto aktiviert hast, wird SAML SSO standardmäßig für alle Organisationen Deines Enterprise-Kontos aktiviert. Alle Mitglieder müssen sich über SAML SSO authentifizieren, um auf die Organisationen zuzugreifen, bei denen sie Mitglied sind. Enterprise-Inhaber müssen sich über SAML SSO authentifizieren, wenn sie auf ein Enterprise-Konto zugreifen. - -{% data reusables.saml.about-saml-access-enterprise-account %} Weitere Informationen findest Du auf „[Anzeigen und Verwalten des SAML-Zugriffs eines Benutzers auf Dein Enterprise-Konto](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[Managing user provisioning for organizations in your enterprise account](#managing-user-provisioning-for-organizations-in-your-enterprise-account)." - -{% note %} - -**Hinweis:** Wenn Du die Authentifizierung mit SAML Single Sign-On für Dein Enterprise-Konto aktivierst, werden alle bestehenden SAML-Konfigurationen auf Organisationsebene überschrieben. - -{% endnote %} - -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Wähle unter „SAML single sign-on“ (SAML Single Sign-On) **Enable SAML authentication** (SAML-Authentifizierung aktivieren) aus. ![Kontrollkästchen zum Aktivieren von SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. Gib im Feld **Sign on URL** (Sign-On-URL) den HTTPS-Endpunkt für Deinen IdP für Single Sign-On-Anforderungen ein. Diesen Wert findest Du in der IdP-Konfiguration. ![Feld für die URL, auf die Mitglieder bei der Anmeldung weitergeleitet werden](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Gib optional im Feld **Issuer** (Aussteller) den Namen Deines SAML-Ausstellers ein. Dadurch wird die Authentizität versendeter Nachrichten verifiziert. ![Feld für den Namen des SAML-Ausstellers](/assets/images/help/saml/saml_issuer.png) -8. Füge unter **Public Certificate** (Öffentliches Zertifikat) ein Zertifikat ein, um die SAML-Antworten zu verifizieren. ![Feld für das öffentliche Zertifikat des Identity Providers](/assets/images/help/saml/saml_public_certificate.png) -9. Um die Integrität der Anforderungen von Ihrem SAML-Aussteller zu überprüfen, klicken Sie auf {% octicon "pencil" aria-label="The edit icon" %}. Wähle dann in den Dropdownmenüs „Signature Method“ (Signaturmethode) und „Digest Method“ (Digest-Methode) den Hash-Algorithmus aus, den Dein SAML-Aussteller verwendet. ![Dropdownmenüs für die Hash-Algorithmen für die Signaturmethode und Digest-Methode, die Dein SAML-Aussteller verwendet](/assets/images/help/saml/saml_hashing_method.png) -10. Bevor Du SAML SSO für Dein Unternehmen aktivierst, klicke auf **Test SAML configuration** (SAML-Konfiguration testen), um sicherzustellen, dass die eingegebenen Informationen korrekt sind. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/saml/saml_test.png) -11. Klicke auf **Save** (Speichern). - -### Managing user provisioning for organizations in your enterprise account - -Enterprise owners can manage organization membership in an enterprise account directly from an identity provider (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. - -If you configure SCIM in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. - -For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: - -- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). -- Cancel any existing invitations for the user to join an organization owned by your enterprise account. - -For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: - -- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. - -If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." - -To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." - -### Teamsynchronisierung für Organisationen in Deinem Enterprise-Konto verwalten - -Enterprise-Inhaber können die Teamsynchronisierung zwischen einem IdP und {% data variables.product.product_name %} ermöglichen, um Organisationsinhabern und Teambetreuern die Verbindung von Teams in den Organisationen Deines Enterprise-Kontos mit IdP-Gruppen zu ermöglichen. - -{% data reusables.identity-and-permissions.about-team-sync %} - -Mit Deinem Enterprise-Konto kannst Du die Teamsynchronisation mit Azure AD verwenden. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -Du kannst auch die Teamsynchronisation für eine einzelne Organisation konfigurieren und verwalten. Weitere Informationen findest Du unter „[Teamsynchronisation für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." - -#### Vorrausetzungen - -Bevor Du die Teamsynchronisierung für Dein Enterprise-Konto aktivieren kannst: - - müssen Du oder Dein Azure AD-Administrator ein Global-Administrator oder ein Privileged Role-Administrator in Azure AD sein. - - musst Du SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto mit Deinem unterstützten IdP aktivieren. Weitere Informationen findest Du unter „[SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." - - musst Du mit SAML SSO und der unterstützten IdP zu Deinem Enterprise-Konto authentifizieren. Weitere Informationen findest Du unter „[Authentifizierung mit SAML Single Sign-On](/articles/authenticating-with-saml-single-sign-on).“ - -#### Teamsynchronisation für Azure AD verwalten - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Überprüfe die Mandanteninformation des Identitätsanbieters, den Du zu Deinem Enterprise-Konto verbinden willst, dann klicke auf **Approve** (Genehmigen). ![Ausstehende Anforderung zum Aktivieren der Teamsynchronisierung für einen IdP-Mandanten mit der Option zur Genehmigung oder Ablehnung](/assets/images/help/teams/approve-team-synchronization.png) -8. Um die Teamsynchronisation zu deaktivieren, klicke auf **Disable team synchronization** (Teamsynchronisation deaktivieren). ![Deaktivieren der Teamsynchronisierung](/assets/images/help/teams/disable-team-synchronization.png) - ### SSH-Zertifizierungsstellen Ihres Enterprise-Kontos verwalten Enterprise-Inhaber können die SSH-Zertifizierungsstellen eines Enterprise-Kontos hinzufügen und löschen. @@ -203,3 +112,7 @@ Das Löschen einer Zertifizierungsstelle kann nicht rückgängig gemacht werden. {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### Weiterführende Informationen + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md index 1bf2a1db9a978..1e48a7671126d 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + 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 03908489c36a9..db737dff12e30 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 @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. Weitere Informationen zu {% data variables.product.prodname_enterprise %} finden Sie unter „[Produkte von {% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)“. For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." @@ -27,11 +29,13 @@ Weitere Informationen zu {% data variables.product.prodname_enterprise %} finden 3. On {% data variables.product.prodname_dotcom_the_website %}, create at least one organization owned by your enterprise account. For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." -4. The subscriber must create a user account on {% data variables.product.prodname_dotcom_the_website %}, and the email address for the account must be the same email address as the email address in the {% data variables.product.prodname_vs %} portal. For more information, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." - ### Inviting a subscriber to use {% data variables.product.prodname_enterprise %} -To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber must join an organization owned by your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Organization owners can invite new members to an organization. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." ### Viewing {% data variables.product.prodname_enterprise %} licensing diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..df641859b7020 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Teamsynchronisierung für Organisationen in Deinem Enterprise-Konto verwalten +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +Du kannst auch die Teamsynchronisation für eine einzelne Organisation konfigurieren und verwalten. Weitere Informationen findest Du unter „[Teamsynchronisation für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." + +### Vorrausetzungen + +müssen Du oder Dein Azure AD-Administrator ein Global-Administrator oder ein Privileged Role-Administrator in Azure AD sein. + +musst Du SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto mit Deinem unterstützten IdP aktivieren. Weitere Informationen findest Du unter „[SAML Single Sign-On für Organisationen in Deinem Enterprise-Konto aktivieren](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +musst Du mit SAML SSO und der unterstützten IdP zu Deinem Enterprise-Konto authentifizieren. Weitere Informationen findest Du unter „[Authentifizierung mit SAML Single Sign-On](/articles/authenticating-with-saml-single-sign-on).“ + +### Teamsynchronisation für Azure AD verwalten + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Ausstehende Anforderung zum Aktivieren der Teamsynchronisierung für einen IdP-Mandanten mit der Option zur Genehmigung oder Ablehnung](/assets/images/help/teams/approve-team-synchronization.png) +8. Um die Teamsynchronisation zu deaktivieren, klicke auf **Disable team synchronization** (Teamsynchronisation deaktivieren). ![Deaktivieren der Teamsynchronisierung](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index c0732494a210e..5ac9d2f572908 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." {% data reusables.enterprise-accounts.access-enterprise %} 2. To the right of the search field, click **X unowned**. ![Button to view unowned organizations](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 8c3d98d41f987..f6ea900c3bad2 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,6 +18,8 @@ Wenn Du SAML Single Sign-On für Dein Enterprise-Konto aktivierst, kann jedes En {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 5fff3ad0a3466..4fe05845a6767 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -22,8 +22,8 @@ For more information about managing billing managers, see "[Inviting people to m {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Under "User +1. 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. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Lizenz- und Abonnementinformationen in Enterprise-Abrechnungseinstellungen](/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 %}**. +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index 51f0f437f9ec1..0d05cd74327a5 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -39,20 +39,20 @@ Mit dem Befehl `git show` und dem Flag `--pretty=fuller` kannst Du überprüfen, $ git show Your commit SHA number --pretty=fuller commit Your commit SHA number Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` Weichen das Erstellungs- und Commit-Datum voneinander ab, kannst Du das Commit-Datum in der URL manuell ändern, um die Commit-Details anzuzeigen. Ein Beispiel: -- Die folgende URL verwendet das Erstellungsdatum `2016-07-13`: +- Die folgende URL verwendet das Verfassungsdatum `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- Die folgende URL verwendet das Commit-Datum `2016-07-19`: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- Die folgende URL verwendet das Commit-Datum `2018-04-10`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` Wenn Du die URL mit dem korrigierten Commit-Datum aufrufst, werden die Commit-Details angezeigt. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index ad81c8aacc97d..6abdfb2305d99 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### Gezählte Beiträge -#### Issues und Pull Requests +#### Issues, pull requests and discussions -Issues und Pull Requests werden in Deinem Beteiligungsdiagramm angezeigt, falls sie in einem eigenständigen Repository und nicht in einem Fork geöffnet wurden. +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. #### Commits Commits werden in Deinem Beteiligungsdiagramm angezeigt, falls sie **alle** folgenden Bedingungen erfüllen: diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index fc29fa5774d7e..f2c721ea22c8b 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,7 +14,7 @@ versions: For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. {% data reusables.user_settings.access_settings %} -1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) 1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index d43c45d0cf7fe..16d6ee1e10624 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,7 +30,8 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | „[Mitarbeiter in ein persönliches Repository einladen](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)“ | | | Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews | „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches)“ | | Das Repository löschen | „[Repository löschen](/github/administering-a-repository/deleting-a-repository)“ | | Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} @@ -63,7 +64,8 @@ Collaborators can also perform the following actions. | Aktion | Weitere Informationen | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | „[Über Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Create, edit, and delete comments on commits, pull requests, and issues in the repository |
  • "[About issues](/github/managing-your-work-on-github/about-issues)"
  • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
| | Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | | Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 48d8b54b9963e..0f3f1a6504be1 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ Für Projektboard-Mitarbeiter gibt es drei Berechtigungsstufen: Der Projektboard-Inhaber und die Mitarbeiter mit Administratorzugriff besitzen die vollständige Kontrolle über das Projektboard. Neben den Berechtigungen, die auch Projektboard-Mitarbeitern erteilt werden, stehen einem Projektboard-Inhaber und Mitarbeitern mit Administratorzugriff zusätzlich folgende Möglichkeiten zur Verfügung: - [Mitarbeiter verwalten, anzeigen und hinzufügen](/articles/managing-access-to-your-user-account-s-project-boards) -- [Ein Projektboard als öffentliches oder privates Projektboard konfigurieren](/articles/changing-project-board-visibility) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) - [Ein Projektboard löschen](/articles/deleting-a-project-board/) - [Ein Projektboard schließen](/articles/closing-a-project-board/) - [Ein geschlossenes Projektboard erneut öffnen](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ Mitarbeiter mit Schreibzugriff auf ein Benutzer-Projektboard können Folgendes t ### Sichtbarkeit des Projektboards -Du kannst die Sichtbarkeit des Projektboards von privat in öffentlich und umgekehrt ändern. Standardmäßig sind Benutzer-Projektboards privat. Weitere Informationen finden Sie unter „[Sichtbarkeit des Projektboards ändern](/articles/changing-project-board-visibility)“. +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Standardmäßig sind Benutzer-Projektboards privat. Weitere Informationen finden Sie unter „[Sichtbarkeit des Projektboards ändern](/articles/changing-project-board-visibility)“. ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/site-policy/github-and-trade-controls.md b/translations/de-DE/content/github/site-policy/github-and-trade-controls.md index 5e0c9d317de74..10ae8accf43b3 100644 --- a/translations/de-DE/content/github/site-policy/github-and-trade-controls.md +++ b/translations/de-DE/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com, GitHub Enterprise Server und die Informationen, die Sie auf eines der beiden Produkte hochladen, können Handelskontrollbestimmungen unterliegen, einschließlich der Bestimmungen der U.S. Export Administration Regulations (EAR). Export Administration Regulations (the EAR). -GitHub verfolgt die Vision, die globale Plattform für die Zusammenarbeit von Entwicklern zu sein, unabhängig davon, wo diese ansässig sind. Wir nehmen unsere Verantwortung ernst, staatliche Mandate gründlich zu prüfen, um sicher zu sein, dass Benutzer und Kunden nicht über das gesetzlich vorgeschriebene Maß hinaus beeinträchtigt werden. Dazu gehört, dass die Dienste öffentlicher Repositorys, einschließlich derer für Open-Source-Projekte, verfügbar und zugänglich bleiben, um die persönliche Kommunikation mit Entwicklern in sanktionierten Regionen zu unterstützen. +GitHub verfolgt die Vision, die globale Plattform für die Zusammenarbeit von Entwicklern zu sein, unabhängig davon, wo diese ansässig sind. Wir nehmen unsere Verantwortung ernst, staatliche Mandate gründlich zu prüfen, um sicher zu sein, dass Benutzer und Kunden nicht über das gesetzlich vorgeschriebene Maß hinaus beeinträchtigt werden. This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. -To comply with U.S. Um den US-Handelskontrollgesetzen zu entsprechen, hat GitHub einige erforderliche Änderungen an der Art und Weise vorgenommen, wie wir unsere Dienstleistungen erbringen. As U.S. trade controls laws evolve, we will continue to work with U.S. Im Zuge der Weiterentwicklung der US-Handelskontrollgesetze werden wir weiterhin mit den US-Regulierungsbehörden zusammenarbeiten, um zu prüfen, inwieweit wir Entwicklern in sanktionierten Märkten kostenlose Code-Kooperationsdienste anbieten können. Wir glauben, dass das Angebot dieser kostenlosen Dienste die US-Außenpolitik zur Förderung des freien Informationsflusses und der freien Meinungsäußerung in diesen Regionen unterstützt. Wir glauben, dass das Angebot dieser kostenlosen Dienste die US-Außenpolitik unterstützt, den freien Informationsfluss und die freie Meinungsäußerung in diesen Märkten zu fördern. Weitere Einzelheiten über unseren Ansatz und darüber, wie sich Sanktionen auf die globale Software-Zusammenarbeit auswirken, finden Sie in unserem [Blog über Sanktionen](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Auch wenn wir die nachfolgenden Informationen zu Ihrer Bequemlichkeit zur Verfügung gestellt haben, liegt es letztendlich in Ihrer Verantwortung sicherzustellen, dass Ihre Nutzung der Produkte und Dienste von GitHub allen geltenden Gesetzen und Vorschriften, einschließlich der US-Exportkontrollgesetze, entspricht. export control laws. @@ -25,9 +25,9 @@ Im Rahmen unserer [ Nutzungsbedingungen](/articles/github-terms-of-service) dür Die Benutzer sind dafür verantwortlich, sicherzustellen, dass die Inhalte, die sie entwickeln und auf GitHub.com teilen, den US-Exportkontrollgesetzen, einschließlich der EAR und den U.S. International Traffic in Arms Regulations (ITAR), entsprechen. export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). Das unter [GitHub.com](https://github.com) verfügbare Cloud-Hosting-Angebot wurde nicht für das Hosting von Daten konzipiert, die dem ITAR unterliegen, und bietet derzeit nicht die Möglichkeit, den Repository-Zugang nach Ländern zu beschränken. Wenn Sie an ITAR- oder anderen exportkontrollierten Daten mitarbeiten möchten, empfehlen wir Ihnen [GitHub Enterprise Server](https://enterprise.github.com), das lokale Angebot von GitHub. -U.S. US-Handelskontrollgesetze beschränken, welche GitHub.com Dienste für Benutzer in bestimmten Ländern und Gebieten zur Verfügung gestellt werden können. GitHub may allow users in or ordinarily resident in countries and territories subject to U.S. GitHub kann Nutzern in Ländern und Gebieten, die US-Sanktionen unterliegen, den Zugang zu bestimmten kostenlosen GitHub.com Diensten zur persönlichen Kommunikation gemäß den Genehmigungen des Office of Foreign Assets Controls (OFAC) des US-Finanzministeriums gestatten. Treasury Department’s Office of Foreign Assets Controls (OFAC). Personen in diesen Ländern und Gebieten, die sich in diesen Ländern und Gebieten aufhalten oder gewöhnlich dort ansässig sind, ist es untersagt, IP-Proxys, VPNs oder andere Methoden zu verwenden, um ihren Standort beim Zugriff auf GitHub.com Dienste zu verschleiern, und sie dürfen GitHub.com nur für nicht-kommerzielle, persönliche Kommunikation verwenden. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs) und andere "denied or blocked parties" gemäß US-amerikanischem und anderen anwendbaren Gesetzen dürfen nicht auf GitHub.com zugreifen oder es nutzen. and other applicable law are prohibited from accessing or using GitHub.com. Darüber hinaus dürfen Benutzer GitHub.com nicht für oder im Namen solcher Parteien nutzen, einschließlich der Regierungen von sanktionierten Ländern. Des Weiteren darf GitHub.com nicht für Zwecke verwendet werden, die nach den geltenden Exportkontrollgesetzen verboten sind, einschließlich verbotener Endnutzungen, die in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) beschrieben sind. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Darüber hinaus dürfen Benutzer GitHub.com nicht für oder im Namen solcher Parteien nutzen, einschließlich der Regierungen von sanktionierten Ländern. Des Weiteren darf GitHub.com nicht für Zwecke verwendet werden, die nach den geltenden Exportkontrollgesetzen verboten sind, einschließlich verbotener Endnutzungen, die in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) beschrieben sind. #### GitHub Enterprise Server @@ -41,7 +41,7 @@ GitHub Enterprise Server darf nicht in Länder, die in der Ländergruppe E:1 in #### On which countries and territories are U.S. government sanctions applied? -Krim, Kuba, Iran, Nordkorea und Syrien. +Krim, Kuba, Iran, Nordkorea und Syrien. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. #### Wie stellt GitHub sicher, dass Personen, die nicht in den sanktionierten Ländern und Gebieten leben bzw. professionelle Verbindungen zu den sanktionierten Ländern und Gebieten haben, immer noch Zugang oder die Möglichkeit haben, Berufung einzulegen? @@ -55,23 +55,23 @@ Reisen in diese Regionen können sich auf Ihren Kontostatus auswirken, aber die #### Was ist verfügbar und nicht verfügbar? -GitHub hat sich verpflichtet, Entwicklern mit Einzelpersonen- und Organisationskonten in von den USA sanktionierten Regionen weiterhin kostenlose öffentliche Repository-Dienste anzubieten. Dazu gehören der eingeschränkte Zugriff zu kostenlosen Diensten, wie z. B. öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten, nur für die persönliche Kommunikation und nicht für kommerzielle Zwecke. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -However, due to U.S. Aufgrund der Restriktionen unter dem amerikanischen Handelskontrollgesetz kann GitHub keine Dienstleistungen für private Repositorys oder bezahlte Dienstleistungen für Konten in von den USA sanktionierten Regionen anbieten. sanctioned regions like North Korea, Iran, Syria, and Crimea. Die Einschränkung unterbindet den Zugang zu privaten Repository-Diensten und bezahlten Diensten, wie z.B. die Verfügbarkeit kostenloser oder kostenpflichtiger privater Repositorys, vertraulicher Gists, kostenpflichtiger Aktionsminuten, Sponsoren und GitHub-Marketplace-Diensten. +GitHub hat sich verpflichtet, Entwicklern mit Einzelpersonen- und Organisationskonten in von den USA sanktionierten Regionen weiterhin kostenlose öffentliche Repository-Dienste anzubieten. Dazu gehören der eingeschränkte Zugriff zu kostenlosen Diensten, wie z. B. öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten, nur für die persönliche Kommunikation und nicht für kommerzielle Zwecke. -Bei kostenpflichtigen Organisationskonten in sanktionierten Regionen haben Benutzer möglicherweise eingeschränkten Zugriff auf ihre öffentlichen Repositorys, die zu archivierten schreibgeschützten Repositorys herabgestuft wurden. Bei kostenlosen Organisationskonten in sanktionierten Regionen haben die Benutzer jedoch weiterhin vollen Zugriff auf kostenlose öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten. +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. GitHub wird sich weiterhin bei den US-Regulierungsbehörden für den größtmöglichen Zugang zu kostenlosen Code-Zusammenarbeitsdienste für Entwickler in sanktionierten Regionen einsetzen, einschließlich kostenloser privater Repositorys. Wir glauben, dass das Angebot dieser kostenlosen Dienste die US-Außenpolitik zur Förderung des freien Informationsflusses und der freien Meinungsäußerung in diesen Regionen unterstützt. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. #### Wie definieren Sie diese spezifischen Benutzer? -If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. +If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. #### Inwiefern sind Organisationskonten betroffen? -If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. economic sanctions, then the organization account and the affiliated owner account will be restricted. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. -Die Einschränkung unterbindet den Zugang zu privaten Repository-Diensten und bezahlten Diensten, wie z.B. die Verfügbarkeit kostenloser oder kostenpflichtiger privater Repositorys, vertraulicher Gists, kostenpflichtiger Aktionsminuten, Sponsoren und GitHub-Marketplace-Diensten. Bei kostenpflichtigen Organisationskonten, die mit sanktionierten Regionen verbunden sind, haben Benutzer möglicherweise eingeschränkten Zugriff auf ihre öffentlichen Repositorys, die zu archivierten schreibgeschützten Repositorys herabgestuft wurden. Bei kostenlosen Organisationskonten, die mit sanktionierten Regionen verbunden sind, haben die Benutzer jedoch weiterhin vollen Zugriff auf kostenlose öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten. +Die Einschränkung unterbindet den Zugang zu privaten Repository-Diensten und bezahlten Diensten, wie z.B. die Verfügbarkeit kostenloser oder kostenpflichtiger privater Repositorys, vertraulicher Gists, kostenpflichtiger Aktionsminuten, Sponsoren und GitHub-Marketplace-Diensten. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### Können private Repositorys von Benutzern mit Handelsbeschränkungen veröffentlicht werden? @@ -81,3 +81,16 @@ Free individual account users can make restricted private repositories public, f Unfortunately, our understanding of the law does not give us the option to allow downloads or deletion of private repository content, until otherwise authorized by the U.S. government. government. We will strongly advocate, with U.S. We will strongly advocate, with U.S. regulators, for the right of trade-restricted users to secure the contents of their private repositories. We will also advocate for more availability of GitHub services for developers in sanctioned markets, and further underscore the importance of code collaboration in supporting personal communications for developers globally. +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/de-DE/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/de-DE/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index a1db9e3f24b38..c3603f1842af0 100644 --- a/translations/de-DE/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/de-DE/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ Sollten dennoch rechtliche Schritte von einer dritten Partei, einschließlich St ### 3. Begrenzter Verzicht auf andere Website-Richtlinien -Sollten Ihre Aktivitäten zur Sicherheitsuntersuchung nicht mit bestimmten Beschränkungen in unseren [relevanten Website Richtlinien](/categories/site-policy/) übereinstimmen, aber mit den Vorgaben unseres Bug-Bounty-Programms vereinbar sein, befreien wir Sie von diesen Einschränkungen, und zwar zu dem einzigen und begrenzten Zweck, Ihre Sicherheitsuntersuchung im Rahmen dieses Bug-Bounty-Programms zu ermöglichen. Genau wie oben, sollten Sie im Zweifelsfall zuerst uns fragen! +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Genau wie oben, sollten Sie im Zweifelsfall zuerst uns fragen! diff --git a/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md index b56123fec3d4f..25cbc9fbb5bbe 100644 --- a/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **December 30, 2020** +Effective date: **January 6, 2021** GitHub bietet viel Transparenz darüber, wie wir Ihre Daten verwenden, wie wir Ihre Daten sammeln und mit wem wir Ihre Daten teilen. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -25,12 +25,9 @@ Wenn wir Ihre Daten an Unterauftragsverarbeiter, wie z. B. unsere Anbieter und D | Braintree (PayPal) | Kreditkarten-Zahlungsabwicklung | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Clearbit | Marketing-Datenanreicherungsservice | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Discourse | Community-Forum-Softwareanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| DiscoverOrg | Marketing-Datenanreicherungsservice | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Eloqua | Automatisierung von Marketingkampagnen | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Google Apps | Interne Unternehmensinfrastruktur | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Google Analytics | Analytics and performance | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| LinkedIn Navigator | Data enrichment service | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Magic Robot | Kampagnenberichte (Salesforce Add-on) | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | MailChimp | Kunden-Ticketing-E-Mail Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Mailgun | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Microsoft | Microsoft Services | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | diff --git a/translations/de-DE/content/github/site-policy/index.md b/translations/de-DE/content/github/site-policy/index.md index d21ec07883f6c..2f470c8570224 100644 --- a/translations/de-DE/content/github/site-policy/index.md +++ b/translations/de-DE/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 9e2a747ffee4f..7d11091b44f01 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ Du kannst Analysen zu Deinen aktuellen und vergangenen Sponsorings einsehen, die ### Letzte Sponsoring-Aktivitäten anzeigen {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. Klicke in der linken Seitenleiste auf **Activity** (Aktivitäten). ![Registerkarte „Activity" (Aktivitäten)](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### Deine Sponsoring-Daten exportieren -If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Klicke auf **Export all** (Alles exportieren). ![Schaltfläche „Export all" (Alles exportieren)](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Schaltfläche „Export"](/assets/images/help/sponsors/export-all.png) 1. Wähle einen Zeitrahmen und ein Format für die zu exportierenden Daten und klicke dann auf **Start export** (Export starten). ![Optionen für den Datenexport](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index f4eb09e59f09d..e685b18ddea3b 100644 --- a/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/de-DE/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -21,7 +21,7 @@ When you enable data use for your private repository, you'll be able to access t {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/using-git/adding-a-remote.md b/translations/de-DE/content/github/using-git/adding-a-remote.md index 5933881f825b9..36eb0d70d9eb2 100644 --- a/translations/de-DE/content/github/using-git/adding-a-remote.md +++ b/translations/de-DE/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ Beim Hinzufügen eines Remote-Repositorys können folgende Fehler auftreten. Dieser Fehler bedeutet, dass Du versucht hast, ein Remote-Repository hinzuzufügen, dessen Name bereits im lokalen Repository vorhanden ist: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/de-DE/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/de-DE/content/github/using-git/using-git-rebase-on-the-command-line.md index 411c896b154ae..0ccb8ed9c2632 100644 --- a/translations/de-DE/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/de-DE/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,6 +124,10 @@ Git zeigt erneut die zu bearbeitende Commit-Mitteilung an. Du kannst den Text (` Der gewöhnliche Befehl `git push origin` funktioniert **nicht**, da Du den Git-Verlauf geändert hast. Du musst den Befehl ändern, indem Du Deine neuesten Änderungen per erzwungenem Push-Vorgang überträgst: ```shell +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes $ git push origin main --force ``` diff --git a/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 34faab8c6baff..6a6793c3529b8 100644 --- a/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ Dein Design umfasst standardmäßige Layouts, Includes und Stylesheets, die auto {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### Nächste Schritte: {% data reusables.pages.add-jekyll-theme %} Weitere Informationen findest Du unter „[Ein Design zu Deiner {% data variables.product.prodname_pages %}-Website mit Jekyll hinzufügen](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll).“ diff --git a/translations/de-DE/content/github/working-with-github-support/about-github-support.md b/translations/de-DE/content/github/working-with-github-support/about-github-support.md index c66785c11742f..7dda44c21386e 100644 --- a/translations/de-DE/content/github/working-with-github-support/about-github-support.md +++ b/translations/de-DE/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ Um zu prüfen, ob es derzeit Probleme gibt, die die Dienstleistungen von {% data ### {% data variables.contact.github_support %} kontaktieren -Benutzer- und Organisationskonten von {% data variables.product.prodname_free_user %} können das {% data variables.contact.community_support_forum %} verwenden, um Themen zu durchsuchen, Fragen zu stellen, Lösungen zu teilen und direkt mit {% data variables.contact.community_support %} zu interagieren. Du kannst {% data variables.contact.contact_support %} auch kontaktieren, um Issues mit Konten, Sicherheit oder Missbrauch zu melden. +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -Mit einem bezahlten Konto kannst du entweder {% data variables.contact.contact_support %} kontaktieren oder in Abhängigkeit von Deinem Plan auch {% data variables.contact.premium_support %} oder {% data variables.contact.contact_ent_support %}. Weitere Informationen zum Kontaktieren von {% data variables.contact.premium_support %} findest Du unter „[Über {% data variables.contact.premium_support %} für {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)" oder „[Über {% data variables.contact.premium_support %} für {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)." +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. ### {% data variables.contact.github_support %} temporären Zugriff auf ein privates Repository gewähren diff --git a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index b6b2f56155bd3..74d261678365b 100644 --- a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -215,7 +215,7 @@ Du kannst Emojis einfügen, indem Du `:EMOJICODE:` eingeben. Bei der Eingabe von `:` wird eine Liste mit Vorschlägen für Emojis angezeigt. Die Liste wird während der Eingabe gefiltert. Wenn Du den gewünschten Emoji siehst, drücke die **Tabulator-** oder **Eingabetaste**, um das markierte Ergebnis zu vervollständigen. -Eine komplette Liste der verfügbaren Emojis und Codes findest Du unter [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). ### Paragraphen diff --git a/translations/de-DE/content/github/writing-on-github/creating-gists.md b/translations/de-DE/content/github/writing-on-github/creating-gists.md index 58362dd3042f4..2ad548522630a 100644 --- a/translations/de-DE/content/github/writing-on-github/creating-gists.md +++ b/translations/de-DE/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- title: Gists erstellen -intro: 'Du kannst zwei Arten von Gists erstellen: öffentliche und geheime. Erstelle einen öffentlichen Gist, wenn Du Deine Ideen für andere freigeben möchtest. Andernfalls kannst Du einen geheimen Gist erstellen.' +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,13 @@ versions: ### Informationen zu Gists -Jeder Gist ist ein Git-Repository, d. h., er kann geforkt und geklont werden. Wenn Sie bei der Erstellung eines Gists bei {% data variables.product.product_name %} angemeldet sind, wird der Gist mit Ihrem Konto verknüpft und in der Liste Ihrer Gists angezeigt, wenn Sie Ihre {% data variables.gists.gist_homepage %} aufrufen. +Jeder Gist ist ein Git-Repository, d. h., er kann geforkt und geklont werden. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -Gists können öffentlich oder geheim sein. Öffentliche Gists werden in {% data variables.gists.discover_url %} angezeigt, wo Benutzer neue Gists nach der Erstellung durchsuchen können. Gists können auch gesucht werden, Du kannst sie also verwenden, wenn Du möchtest, dass andere Benutzer Deine Arbeit finden und ansehen können. {% data reusables.gist.cannot-convert-public-gists-to-secret %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. Gists können auch gesucht werden, Du kannst sie also verwenden, wenn Du möchtest, dass andere Benutzer Deine Arbeit finden und ansehen können. -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 %} Geheime Gists sind nicht privat. Wenn Du die URL eines geheimen Gists an einen Freund sendest, kann er den Gist sehen. Wenn jemand, den Du nicht kennst, die URL findet, kann er Deinen Gist ebenfalls sehen. Wenn Du nicht möchtest, dass Dein Code von anderen gesehen werden kann, kannst Du stattdessen [ein privates Repository erstellen](/articles/creating-a-new-repository). +Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. Wenn Du nicht möchtest, dass Dein Code von anderen gesehen werden kann, kannst Du stattdessen [ein privates Repository erstellen](/articles/creating-a-new-repository). + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -35,11 +37,11 @@ In folgenden Fällen erhältst Du eine Benachrichtigung: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -Du kannst Gists an Deinem Profil anheften, damit andere Personen sie leichter sehen. Weitere Informationen findest Du unter „[Elemente an Dein Profil anheften](/articles/pinning-items-to-your-profile).“ +Du kannst Gists an Deinem Profil anheften, damit andere Personen sie leichter sehen. Weitere Informationen finden Sie unter „[Elemente an Ihr Profil anheften](/articles/pinning-items-to-your-profile)“. {% endif %} -Um Gists zu entdecken, die von anderen Benutzern erstellt wurden, rufe die {% data variables.gists.gist_homepage %} auf und klicke dort auf **All Gists** (Alle Gists). Daraufhin wird eine Seite mit allen Gists angezeigt, die nach dem Zeitpunkt der Erstellung oder Aktualisierung sortiert sind. Mit der {% data variables.gists.gist_search_url %} können Sie Gists auch nach Sprache suchen. Die Gist-Suche nutzt dieselbe Suchsyntax wie [die Codesuche](/articles/searching-code). +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Daraufhin wird eine Seite mit allen Gists angezeigt, die nach dem Zeitpunkt der Erstellung oder Aktualisierung sortiert sind. Mit der {% data variables.gists.gist_search_url %} können Sie Gists auch nach Sprache suchen. Die Gist-Suche nutzt dieselbe Suchsyntax wie [die Codesuche](/articles/searching-code). Da es sich bei Gists um Git-Repositorys handelt, kannst Du ihren vollständigen Commit-Verlauf anzeigen, einschließlich der Diffs. Du kannst Gists auch forken oder klonen. Weitere Informationen findest Du unter „[Gists forken und klonen](/articles/forking-and-cloning-gists)“. @@ -69,12 +71,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 4. Gib den Text für den Gist in das Gist-Textfeld ein. ![Gist-Textfeld](/assets/images/help/gist/gist_text_box.png) -5. Führe einen der folgenden Schritte durch: - - Um einen öffentlichen Gist zu erstellen, klicke auf **Create public gist** (Erstelle öffentlichen Gist). - - Um einen geheimen Gist zu erstellen, klicke auf **Create secret gist** (Erstelle geheimen Gist). ![Schaltfläche zum Erstellen des Gists](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **Hinweis:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/de-DE/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/de-DE/content/github/writing-on-github/forking-and-cloning-gists.md index d5c523254b5a5..a62611c847756 100644 --- a/translations/de-DE/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/de-DE/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Gists forken -Jeder Gist gibt an, bei welchen Forks es Aktivitäten gibt, sodass Du leicht interessante Änderungen von Mitarbeitern oder unbekannten Benutzern finden kannst. +Each gist indicates which forks have activity, making it easy to find interesting changes from others. ![Gist-Forks](/assets/images/help/gist/gist_forks.png) diff --git a/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md index a385f038004c8..b4ee6c26fa30f 100644 --- a/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ Mutations are structured like this: 
mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. diff --git a/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md index e32d52aead847..33d36b5262d3d 100644 --- a/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." @@ -30,8 +30,6 @@ Before you can use the Docker registry on {% data variables.product.prodname_reg ### Bei {% data variables.product.prodname_registry %} authentifizieren -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### Authenticating with a personal access token @@ -51,11 +49,25 @@ To keep your credentials secure, we recommend you save your personal access toke {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} {% raw %} ```shell $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. @@ -94,9 +106,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell If you haven't already built a docker image for the package, build the image, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with package version at build time, and PATH to the image if it isn't in the current working directory. ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, {% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. @@ -105,9 +127,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. Publish the image to {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen #### Example publishing a Docker image -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. @@ -197,9 +246,19 @@ You can use the `docker pull` command to install a docker image from {% data var $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 12c2c3fee6061..68ce9bd2dd031 100644 --- a/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -79,10 +79,35 @@ If your instance has subdomain isolation disabled: ### Ein Paket veröffentlichen -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +2. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. + {% data reusables.package_registry.authenticate-step %} 2. Create a new project. ```shell @@ -119,6 +144,8 @@ You can publish a package to {% data variables.product.prodname_registry %} by a dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### Publishing multiple packages to the same repository To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. diff --git a/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md index e3070fd048ec9..bdc452091a27a 100644 --- a/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -209,6 +209,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### Weiterführende Informationen - "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md index f22346e1111f5..4b7e44ca6ba82 100644 --- a/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. diff --git a/translations/de-DE/content/packages/guides/using-github-packages-with-github-actions.md b/translations/de-DE/content/packages/guides/using-github-packages-with-github-actions.md index bb4ed48ec696c..8f9a3f5c6d7a9 100644 --- a/translations/de-DE/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/de-DE/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,274 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{ ### Publishing a package using an action -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
+ +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
+ +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
+ +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
+ +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
+ +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
+ +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
+ +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
+ +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
+ +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Installing a package using an action You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. diff --git a/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md index a5ad7b873e0f9..62d6517de7197 100644 --- a/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ You can integrate {% data variables.product.prodname_registry %} with {% data va You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)“. {% 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) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ Weitere Informationen findest Du unter: ### Managing packages -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/de-DE/content/rest/overview/api-previews.md b/translations/de-DE/content/rest/overview/api-previews.md index 01b907bb1f6a9..cf823678c9fcc 100644 --- a/translations/de-DE/content/rest/overview/api-previews.md +++ b/translations/de-DE/content/rest/overview/api-previews.md @@ -70,14 +70,6 @@ Manage [projects](/rest/reference/projects). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} -### User blocking - -Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. - -**Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - ### Repository topics View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md index 6f14bb96cf5d4..6dc2e0240c261 100644 --- a/translations/de-DE/content/rest/overview/libraries.md +++ b/translations/de-DE/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 cd0b1f0231fdb..a3d2cc5f8735e 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 @@ -30,7 +30,7 @@ For information about GitHub's GraphQL API, see the [v4 documentation](/graphql) sent and received as JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -124,7 +124,7 @@ Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated- Authenticating with invalid credentials will return `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -324,7 +324,7 @@ Note that [the Search API has custom rate limit rules](/rest/reference/search#ra The returned HTTP headers of any API request show your current rate limit status: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -422,7 +422,7 @@ User-Agent: Awesome-Octocat-App cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -449,7 +449,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -460,7 +460,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -471,7 +471,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -489,7 +489,7 @@ The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any Here's a sample request sent from a browser hitting `http://example.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval @@ -498,7 +498,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra This is what the CORS preflight request looks like: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With diff --git a/translations/de-DE/content/rest/reference/code-scanning.md b/translations/de-DE/content/rest/reference/code-scanning.md index 42f1f093fec7e..efd7f361f7cf1 100644 --- a/translations/de-DE/content/rest/reference/code-scanning.md +++ b/translations/de-DE/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Code scanning redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml index 957eaf642c79d..f67f6c68d16c1 100644 --- a/translations/de-DE/data/glossaries/external.yml +++ b/translations/de-DE/data/glossaries/external.yml @@ -123,7 +123,7 @@ - term: Commit description: >- - Ein Commit (oder „Revision“) ist eine einzelne Änderung an einer Datei (oder an einer Reihe von Dateien). Wenn Sie einen Commit durchführen, um Ihre Arbeit zu speichern, erstellt Git eine eindeutige ID (die auch als „SHA“ oder „Hash“ bezeichnet wird). Dadurch können Sie den Überblick dahingehend behalten, wer die spezifischen Änderungen wann durchgeführt hat. Commits enthalten in der Regel eine Commit-Mitteilung, in der die vorgenommenen Änderungen kurz beschrieben werden. + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. - term: Commit-Autor description: Der Benutzer, der den Commit durchführt. @@ -137,7 +137,7 @@ - term: Commit-Mitteilung description: >- - Ein kurzer, beschreibender Text zu einem Commit, in dem die Änderung kommuniziert wird, die der Commit nach sich zieht. + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. - term: Branch vergleichen description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - Ein Gist ist eine Datei, die freigegeben werden kann, die Sie auf GitHub bearbeiten, klonen und forken können. Sie können festlegen, dass ein Gist öffentlich oder geheim ist. Geheime Gists stehen jedoch allen Personen zur Verfügung, die über die entsprechende URL verfügen. + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- @@ -436,7 +436,7 @@ - term: Benachrichtigung description: >- - Aktualisierungen, die je nach Ihren Einstellungen per Web oder E-Mail bereitgestellt wurden, die Ihnen die Informationen zu den für Sie relevanten Aktivitäten bereitstellen. + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. - term: OAuth App description: >- diff --git a/translations/de-DE/data/glossaries/internal.yml b/translations/de-DE/data/glossaries/internal.yml index e4a0db597fae9..b382089ff34d1 100644 --- a/translations/de-DE/data/glossaries/internal.yml +++ b/translations/de-DE/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: CPU. - term: Credential-Helper - description: Ein Programm, das Git-Anmeldeinformation speichert und abruft. + description: A program that stores and fetches Git credentials. - term: Creole description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - What You See Is What You Get (WYSIWYG, Vorschau). Ein Akronym, das bedeutet, dass der Bildschirmtext genauso aussieht, wenn er dargestellt wird. + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. - term: XenServer description: Eine Virtualisierungsplattform. diff --git a/translations/de-DE/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/de-DE/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..278487e189817 --- /dev/null +++ b/translations/de-DE/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: Access to package version deletion + description: >- + This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Bereitstellungen + description: >- + This preview adds support for deployments mutations and new deployments features. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - More detailed information about a pull request's merge state. + description: >- + This preview adds support for accessing fields that provide more detailed information about a pull request's merge state. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Update multiple refs in a single operation. + description: This preview adds support for updating multiple refs in a single operation. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Project Event Details + description: >- + This preview adds project, project card, and project column details to project-related issue events. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Create content attachments + description: This preview adds support for creating content attachments. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Pinned Issues Preview + description: This preview adds support for pinned issues. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Labels Preview + description: >- + This preview adds support for adding, updating, creating and deleting labels. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Import Project + description: This preview adds support for importing projects. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Team Review Assignments Preview + description: >- + This preview adds support for updating the settings for team review assignment. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/de-DE/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..10f9989a1239f --- /dev/null +++ b/translations/de-DE/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +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.' + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + 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.' + 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.' + 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.' + 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 + owner: nplasterer diff --git a/translations/de-DE/data/learning-tracks/actions.yml b/translations/de-DE/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..e13873512c5ee --- /dev/null +++ b/translations/de-DE/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Get started with {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'Du kannst selbst-gehostete Runner erstellen, um Workflows in einer hochgradig anpassbaren Umgebung zu betreiben.' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/de-DE/data/release-notes/2-22/0.yml b/translations/de-DE/data/release-notes/2-22/0.yml index cb67278fcae8a..5231cfd2ae3b6 100644 --- a/translations/de-DE/data/release-notes/2-22/0.yml +++ b/translations/de-DE/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/3-0/0-rc.yml b/translations/de-DE/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..4794284f4ac0a --- /dev/null +++ b/translations/de-DE/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/de-DE/data/reusables/actions/enterprise-actions-permissions.md b/translations/de-DE/data/reusables/actions/enterprise-actions-permissions.md index 72c38f66bcaed..e66c8787334c4 100644 --- a/translations/de-DE/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/de-DE/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. Under "Policies", select an option. ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/de-DE/data/reusables/actions/enterprise-beta.md b/translations/de-DE/data/reusables/actions/enterprise-beta.md index 5c456da70dfdc..b10237e2827ed 100644 --- a/translations/de-DE/data/reusables/actions/enterprise-beta.md +++ b/translations/de-DE/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..ee9ba1dca8396 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **Note:** {% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md b/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md b/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md b/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md b/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..e2f4ed9452634 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." diff --git a/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..fa46b836cb7e6 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### Nächste Schritte: + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md b/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/de-DE/data/reusables/actions/enterprise-s3-support-warning.md b/translations/de-DE/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md b/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/de-DE/data/reusables/actions/workflow-template-overview.md b/translations/de-DE/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..bb95b397dcf5d --- /dev/null +++ b/translations/de-DE/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. Wenn Dein Repository beispielsweise Node.js-Code enthält, werden Vorschläge für Node.js-Projekte angezeigt. Du kannst Workflow-Vorlagen als Ausgangspunkt verwenden, um Deinen benutzerdefinierten Workflow zu erstellen, oder Du kannst sie unverändert zu verwenden. + +You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. diff --git a/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md b/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..1a1db1c703664 --- /dev/null +++ b/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)“. +{% endif %} diff --git a/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/code-scanning/beta.md b/translations/de-DE/data/reusables/code-scanning/beta.md index ab0f5c162f2da..7d1b5dbc94798 100644 --- a/translations/de-DE/data/reusables/code-scanning/beta.md +++ b/translations/de-DE/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Hinweis:** {% data variables.product.prodname_code_scanning_capc %} befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern. For more information about taking part in the beta, [sign up here](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/de-DE/data/reusables/code-scanning/not-available.md b/translations/de-DE/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..6531f5e1d0875 --- /dev/null +++ b/translations/de-DE/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." + +{% endnote %} +{% endif %} diff --git a/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md index b8d2b78cbceae..18554c0ce1388 100644 --- a/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. 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#allowing-dependabot-to-access-private-repositories)." +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. 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#allowing-dependabot-to-access-private-repositories)." -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/de-DE/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/de-DE/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index f57ed274394cc..e9533a00f72ff 100644 --- a/translations/de-DE/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/de-DE/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Note:** User provisioning for enterprise accounts is currently in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). {% endnote %} diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index e1c8e17ba40ce..ff0495b8e9007 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Minimum requirements](#minimum-requirements) -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [Speicher](#storage) - [CPU and memory](#cpu-and-memory) @@ -7,10 +8,10 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“. -- You must configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +- You must configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Maximum jobs per minute | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ We recommend a high-performance SSD with high input/output operations per second Your instance requires a persistent data disk separate from the root disk. Weitere Informationen findest Du unter „[Systemübersicht](/enterprise/admin/guides/installation/system-overview)“. -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable the beta of {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 2.22, you'll need to configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endif %} @@ -48,4 +49,4 @@ You can resize your instance's root disk by building a new instance or using an {% endwarning %} -You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md index 776fb6a27809b..806110b5d1990 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage | +|:---------------------------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| +| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 2
or [**4**](#optional-features) | 16 GB
or [**32 GB**](#optional-features) | 100 GB
or [**150 GB**](#optional-features) | 200 GB | +| 10–3000 | 4
or [**8**](#optional-features) | 32 GB
or [**48 GB**](#optional-features) | 250 GB
or [**300 GB**](#optional-features) | 200 GB | +| 3000–5000 | 8
or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000–8000 | 12
or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000–10000+ | 16
or [**20**](#optional-features) | 128 GB
or [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage | |:---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------:| | Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 2{% if currentVersion == "enterprise-server@2.22" %}
or [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
or [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
or [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5000–8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
or [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000–10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
or [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
or [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/de-DE/data/reusables/enterprise_management_console/actions.md b/translations/de-DE/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..fa27dd40c618c --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. Klicke in der linken Seitenleiste auf **Actions** (Aktionen). ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..a999a5edfc417 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..4b1379243ea91 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +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. You should time this change carefully, to minimize downtime. + +{% endwarning %} diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..c8e6a6416156c --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Klicke auf **Save changes** (Änderungen speichern). ![Schaltfläche „Edit message“ (Meldung bearbeiten)](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/gated-features/code-scanning.md b/translations/de-DE/data/reusables/gated-features/code-scanning.md index 2bcd80c1d4af9..69e6abf27f4f7 100644 --- a/translations/de-DE/data/reusables/gated-features/code-scanning.md +++ b/translations/de-DE/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/de-DE/data/reusables/gated-features/environments.md b/translations/de-DE/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/de-DE/data/reusables/gated-features/environments.md +++ b/translations/de-DE/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/de-DE/data/reusables/gated-features/protected-branches.md b/translations/de-DE/data/reusables/gated-features/protected-branches.md index a9745fcec2b68..ffae769bab961 100644 --- a/translations/de-DE/data/reusables/gated-features/protected-branches.md +++ b/translations/de-DE/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 %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/de-DE/data/reusables/gated-features/secret-scanning.md b/translations/de-DE/data/reusables/gated-features/secret-scanning.md index bd279034eee82..7396ad8e24141 100644 --- a/translations/de-DE/data/reusables/gated-features/secret-scanning.md +++ b/translations/de-DE/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md index bb809e2711cf9..535fa5cd9df20 100644 --- a/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -Nachdem Du einen Gist erstellt hast, kannst Du ihn nicht von öffentlich in geheim umwandeln. +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..cd1cc8d5fec37 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." + +{% endnote %} diff --git a/translations/de-DE/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/de-DE/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..7fe8ea9619eea --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. For more information, see "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)." +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. Weitere Informationen finden Sie unter „[Kontexte](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)“. + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index 616be3885232d..a4acfe260d242 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -Um die Teamsynchronisierung für Azure AD zu ermöglichen, benötigt Deine Azure AD-Installation folgende Berechtigungen: +Um die Teamsynchronisierung für Azure AD zu ermöglichen, benötigt Deine Azure AD-Installation folgende Berechtigungen. - Vollständige Profile aller Benutzer lesen - Anmelden und Benutzerprofil lesen - Verzeichnisdaten lesen diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md index 997b4eafe3f4e..6ced0a075d4ae 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. Um die Teamsynchronisierung zu bestätigen: +5. Confirm team synchronization. - Wenn Du IdP-Zugriff hast, klicke auf **Enable team synchronization** (Teamsynchronisierung aktivieren). Du wirst auf die SAML SSO-Seite Deines Identity Providers weitergeleitet und dort zur Auswahl Deines Kontos und zur Überprüfung der angeforderten Berechtigungen aufgefordert. - Wenn Du keinen IdP-Zugriff hast, kopiere den IdP-Weiterleitungs-Link und teile ihm mit Deinem IdP-Administrator, um weiterhin die Teamsynchronisierung aktivieren zu können. ![Weiterleitungs-Schaltfläche „Enable team synchronization" (Aktivieren der Teamsynchronisierung)](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md index d63ea5bb6d0a2..e9ee6e5220b96 100644 --- a/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/de-DE/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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} You can choose whether {% 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. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/de-DE/data/reusables/mobile/about-mobile.md b/translations/de-DE/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/de-DE/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/de-DE/data/reusables/mobile/ghes-release-phase.md b/translations/de-DE/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/de-DE/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md b/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md b/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md index 6da37763232e5..1ed5f3afb99ac 100644 --- a/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -You can require that members use SSH certificates to access organization resources,, unless SSH is disabled in your repository. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/de-DE/data/reusables/organizations/click-codespaces.md b/translations/de-DE/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/de-DE/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/de-DE/data/reusables/organizations/team-synchronization.md b/translations/de-DE/data/reusables/organizations/team-synchronization.md index 9c40edbe6c1f7..1afc947114f0c 100644 --- a/translations/de-DE/data/reusables/organizations/team-synchronization.md +++ b/translations/de-DE/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -Mithilfe der Teamsynchronisierung kannst Du Teammitglieder in einer Organisation automatisch über einen Identitätsanbieter hinzufügen und entfernen. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md b/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/de-DE/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/de-DE/data/reusables/package_registry/packages-ghes-release-stage.md index 03d9b25f84162..04e4ffd9ea459 100644 --- a/translations/de-DE/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/de-DE/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your instance, use the [sign-up form](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/de-DE/data/reusables/project-management/choose-visibility.md b/translations/de-DE/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..9e597aa2a3074 --- /dev/null +++ b/translations/de-DE/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. Weitere Informationen findest Du unter „[Sichtbarkeit des Projektboards ändern](/github/managing-your-work-on-github/changing-project-board-visibility).“ ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/de-DE/data/reusables/project-management/project-board-visibility.md b/translations/de-DE/data/reusables/project-management/project-board-visibility.md index 06bc31b917bc1..d36296f1d7e80 100644 --- a/translations/de-DE/data/reusables/project-management/project-board-visibility.md +++ b/translations/de-DE/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -Standardmäßig ist Dein Projektboard privat und nur für Personen mit Lese-, Schreib- oder Administratorberechtigungen für das Projektboard sichtbar. Ein öffentliches Projektboard ist für jeden sichtbar, der die URL des Projektboards hat. +Standardmäßig ist Dein Projektboard privat und nur für Personen mit Lese-, Schreib- oder Administratorberechtigungen für das Projektboard sichtbar. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index 4a9dcfb0f7c33..aa768c04f2aa2 100644 --- a/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -Wenn Statusprüfungen für ein Repository erforderlich sind, müssen die erforderlichen Statusprüfungen bestanden werden, bevor Du Deinen Branch mit der geschützten Branch zusammenführen kannst. Weitere Informationen findest Du unter „[Informationen zu erforderlichen Statuschecks](/articles/about-required-status-checks).“ +Wenn Statusprüfungen für ein Repository erforderlich sind, müssen die erforderlichen Statusprüfungen bestanden werden, bevor Du Deinen Branch mit der geschützten Branch zusammenführen kannst. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ diff --git a/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md index b211ad20450bf..3526e39a78da3 100644 --- a/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -Repository-Administratoren können verlangen, dass alle Pull Requests eine bestimmte Anzahl von genehmigenden Reviews von Personen mit *write* oder *admin* Berechtigungen im Repository oder von einem benannten Codeinhaber erhalten, bevor sie in einen geschützten Branch zusammengeführt werden. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/articles/about-protected-branches).“ - -Wenn erforderliche Reviews aktiviert sind, kann jeder mit Zugriff auf das Repository Änderungen in einem Pull Request genehmigen. Du kannst Deinen Pull Request jedoch nicht zusammenführen, bevor die erforderliche Anzahl von Bearbeitern mit *write-* oder *admin* Berechtigungen im Repository die Änderungen Deines Pull Request in ihrer Reviews genehmigt hat. Weitere Informationen zu Repository-Berechtigungsebenen findest Du unter „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization/)“. Wenn ein Review durch einen designierten Codeinhaber erforderlich ist und sich der Pull Request auf Code auswirkt, der einen designierten Inhaber aufweist, ist eine Genehmigung dieses Inhabers erforderlich. +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/de-DE/data/reusables/repositories/branch-rules-example.md b/translations/de-DE/data/reusables/repositories/branch-rules-example.md index d1ff2af6da49a..ea81704455211 100644 --- a/translations/de-DE/data/reusables/repositories/branch-rules-example.md +++ b/translations/de-DE/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -Du kannst eine Branch-Regel erstellen in einem Repository für einen bestimmten Branch, für alle Branches oder für irgendeinen Branch, der einem Namensmuster entspricht, das mit der fnmatch Syntax spezifiziert ist. Wenn Du beispielsweise verlangen willst, das jeder Branch, der das Wort `release` enthält, vor dem Zusammenführen mindestens zwei Pull-Request-Reviews haben muss, kannst Du eine Branch-Regel für `*release*` erstellen. +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/de-DE/data/reusables/repositories/return-to-source-diff.md b/translations/de-DE/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..c918830348fb3 --- /dev/null +++ b/translations/de-DE/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md index 11da65d34e68f..cfe413d8a0cef 100644 --- a/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -Nachdem alle erforderlichen Reviewer einen Pull Request genehmigt haben, kannst Du ihn trotzdem nicht zusammenführen, wenn es andere offene Pull Requests mit ausstehenden oder abgelehnten Reviews gibt und diese Pull Requests einen Head-Branch haben, der auf denselben Commit verweist. Jemand mit *write* (Schreib-) oder *admin* (Administrations-) Berechtigungen muss den blockierenden Review auf dem anderen Pull Request genehmigen oder verwerfen, bevor Du sie zusammenführen kannst. +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 1f8290d074ddf..ba73880189979 100644 --- a/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. Weitere Informationen findest Du unter „[Einen linearen Commit-Verlauf verlangen](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/de-DE/data/reusables/repositories/workflow-notifications.md b/translations/de-DE/data/reusables/repositories/workflow-notifications.md index 495b1a1b6990c..d24b2d265374f 100644 --- a/translations/de-DE/data/reusables/repositories/workflow-notifications.md +++ b/translations/de-DE/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ Wenn Sie E-Mail- oder Webbenachrichtigungen für {% data variables.product.prodname_actions %} aktivieren, erhalten Sie eine Benachrichtigung, wenn ein von Ihnen ausgelöster Workflow abgeschlossen ist. Die Benachrichtigung enthält den Status der Workflow-Ausführung (einschließlich erfolgreicher, fehlgeschlagener, neutraler und abgebrochener Ausführungen). Sie können auch auswählen, ob Sie nur dann eine Benachrichtigung erhalten möchten, wenn eine Workflow-Ausführung fehlgeschlagen ist. -Sie können den Status von Workflow-Ausführungen auch auf der Registerkarte „Actions“ (Aktionen) eines Repositorys einsehen. Weitere Informationen findest Du unter „[Eine Workflow-Ausführung verwalten](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + +Du kannst den Status von Workflow-Ausführungen auch auf der Registerkarte „Actions“ (Aktionen) eines Repositorys einsehen. Weitere Informationen findest Du unter „[Eine Workflow-Ausführung verwalten](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." diff --git a/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..45f1db2365ed3 --- /dev/null +++ b/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Enterprise-Inhaber können SAML SSO und zentralisierte Authentifizierung über einen SAML IdP in allen Organisationen eines Enterprise-Kontos ermöglichen. Wenn Du SAML SSO für Dein Enterprise-Konto aktiviert hast, wird SAML SSO standardmäßig für alle Organisationen Deines Enterprise-Kontos aktiviert. Alle Mitglieder müssen sich über SAML SSO authentifizieren, um auf die Organisationen zuzugreifen, bei denen sie Mitglied sind. Enterprise-Inhaber müssen sich über SAML SSO authentifizieren, wenn sie auf ein Enterprise-Konto zugreifen. diff --git a/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md b/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md index b02da8aa168d8..be784eeb4f31c 100644 --- a/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML-SSO bietet Organisations- und Enterprise-Inhabern auf {% data variables.product.prodname_dotcom %} die Möglichkeit, den Zugriff auf Organisationsressourcen wie Repositorys, Issues oder Pull Requests zu kontrollieren und zu sichern. +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/de-DE/data/reusables/secret-scanning/about-secret-scanning.md b/translations/de-DE/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/de-DE/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/de-DE/data/reusables/secret-scanning/beta.md b/translations/de-DE/data/reusables/secret-scanning/beta.md index f6e29075319f5..82fdadded9388 100644 --- a/translations/de-DE/data/reusables/secret-scanning/beta.md +++ b/translations/de-DE/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% 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. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..eb0329e7fe346 --- /dev/null +++ b/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8a58fa7bd5b16 --- /dev/null +++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| – | JSON Web Token | json_web_token | +| – | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index cdeb4b9bc3c34..951ef47a10394 100644 --- a/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Hinweis:**Einige Sicherheits- und Analysefunktionen, die standardmäßig für öffentliche Repositorys aktiviert sind, lassen sich nicht deaktivieren. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/sponsors/activity-tab.md b/translations/de-DE/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..c5917c988dedf --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. Klicke in der linken Seitenleiste auf **Activity** (Aktivitäten). ![Registerkarte „Activity" (Aktivitäten)](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/support/ghae-priorities.md b/translations/de-DE/data/reusables/support/ghae-priorities.md index 126c802c76d5f..55be73fa2d2bc 100644 --- a/translations/de-DE/data/reusables/support/ghae-priorities.md +++ b/translations/de-DE/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Priorität | Beschreibung | Beispiele | |:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

_After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
  • Fehler oder Ausfälle, die sich auf die Kernfunktionen von Git- oder Web-Anwendungen aller Benutzer auswirken
  • Severe network or performance degradation for majority of users
  • Voller oder sich schnell füllender Speicher
  • Known security incidents or a breach of access
| -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
  • Leistungsverschlechterung, die die Produktivität vieler Benutzer reduziert
  • Reduced redundancy concerns from failures or service degradation
  • Production-impacting bugs or errors
  • {% data variables.product.product_name %} configuraton security concerns
| +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
  • Leistungsverschlechterung, die die Produktivität vieler Benutzer reduziert
  • Reduced redundancy concerns from failures or service degradation
  • Production-impacting bugs or errors
  • {% data variables.product.product_name %} configuration security concerns
| | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
  • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
  • Issues with user tools and data collection methods
  • Upgrades
  • Bug reports, general security questions, or other feature related questions
    • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
    • Feature requests and product feedback
    • General questions on overall configuration or use of {% data variables.product.product_name %}
    • Notifying {% data variables.contact.github_support %} of any planned changes
    | diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md b/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-tab.md b/translations/de-DE/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/de-DE/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml index 543dbe963260c..459188439c8b1 100644 --- a/translations/de-DE/data/ui.yml +++ b/translations/de-DE/data/ui.yml @@ -4,7 +4,7 @@ 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.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' 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. early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,15 @@ product_landing: quick_start: Schnellstart reference_guides: Reference guides overview: Übersicht +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: more guides + guideTypes: + overview: Übersicht + quick_start: Schnellstart + tutorial: Tutorial + how_to: How-to guide + reference: Referenz diff --git a/translations/de-DE/data/variables/action_code_examples.yml b/translations/de-DE/data/variables/action_code_examples.yml index 317c8d5fe411d..affbfdb18ae96 100644 --- a/translations/de-DE/data/variables/action_code_examples.yml +++ b/translations/de-DE/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/de-DE/data/variables/gists.yml b/translations/de-DE/data/variables/gists.yml index 9d1fea10acf46..12c745fd3ceb3 100644 --- a/translations/de-DE/data/variables/gists.yml +++ b/translations/de-DE/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml index 411bb22546ba1..c9d8fb72640a4 100644 --- a/translations/de-DE/data/variables/product.yml +++ b/translations/de-DE/data/variables/product.yml @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'GitHub Sponsors Matching Fund' #GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/de-DE/data/variables/release_candidate.yml b/translations/de-DE/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/de-DE/data/variables/release_candidate.yml +++ b/translations/de-DE/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/es-ES/content/actions/creating-actions/about-actions.md b/translations/es-ES/content/actions/creating-actions/about-actions.md new file mode 100644 index 0000000000000..b0a3fae16ab13 --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/about-actions.md @@ -0,0 +1,168 @@ +--- +title: Acerca de acciones +intro: 'Las acciones son tareas individuales que puedes combinar para crear trabajos y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/about-actions + - /github/automating-your-workflow-with-github-actions/about-actions + - /actions/automating-your-workflow-with-github-actions/about-actions + - /actions/building-actions/about-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de acciones + +Puedes crear acciones por medio de a escritura de un código personalizado que interactúe con tu repositorio de la manera que desees, incluida la integración con las API de {% data variables.product.prodname_dotcom %} y cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción. + +{% if currentVersion == "free-pro-team@latest" %} +Puedes escribir tus propias acciones para utilizarlas en tu flujo de trabajo o compartir las acciones que hayas creado con la +comunidad de {% data variables.product.prodname_dotcom %}. Para compartir las acciones que creaste, tu repositorio debe ser público. +{% endif %} + +Las acciones pueden ejecutarse directamente en una máquina o en un contenedor Docker. Puedes definir las entradas, salidas y variables de entorno de una acción. + +### Tipos de acciones + +Puedes crear acciones de contenedor Docker y JavaScript. Las acciones requieren un archivo de metadatos para definir las entradas, salidas y puntos de entrada para tu acción. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)" + +| Type | Sistema operativo | +| ----------------------------- | --------------------- | +| Contenedor Docker | Linux | +| JavaScript | Linux, macOS, Windows | +| Pasos de ejecución compuestos | Linux, macOS, Windows | + +#### Acciones del contenedor Docker + +Los contenedores Docker empaquetan el entorno con el código de las {% data variables.product.prodname_actions %}. Esto crea una unidad de trabajo más consistente y confiable, ya que el consumidor de la acción no necesita preocuparse por las herramientas o las dependencias. + +Un contenedor Docker te permite usar versiones específicas de un sistema operativo, dependencias, herramientas y código. Para las acciones que se deben ejecutar en una configuración de entorno específica, Docker es una opción ideal porque puedes personalizar el sistema operativo y las herramientas. Debido a la latencia para crear y recuperar el contenedor, las acciones del contenedor Docker son más lentas que las acciones de JavaScript. + +Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %} + +#### Acciones de JavaScript + +Las acciones de JavaScript pueden ejecutarse directamente en una máquina del ejecutor y separar el código de acción del entorno utilizado para ejecutar el código. El uso de una acción de JavaScript simplifica el código de acción y se ejecuta más rápido que una acción de contenedor Docker. + +{% data reusables.github-actions.pure-javascript %} + +Si estás desarrollando un proyecto Node.js, el conjunto de herramientas de las {% data variables.product.prodname_actions %} te ofrece paquetes que puedes usar en tu proyecto para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). + +#### Acciones compuestas de los pasos de ejecución + +Una acción para los _pasos de ejecución compuestos_ te permite combinar varios pasos de ejecuciónes de flujo de trabajo en una misma acción. Por ejemplo, puedes utilizar esta característica para agrupar varios comandos de ejecución en una acción y después tener un flujo de trabajo que ejecute estos comandos agrupados en un solo paso utilizando esta acción. Para ver un ejemplo, revisa la sección "[Crear una acción de pasos de ejecución compuestos](/actions/creating-actions/creating-a-composite-run-steps-action)". + +### Elegir una ubicación para tu acción + +Si estás desarrollando una acción para que otras personas la utilicen, te recomendamos mantener la acción en su propio repositorio en lugar de agruparla con otro código de aplicación. Esto te permite versionar, rastrear y lanzar la acción como cualquier otro software. + +{% if currentVersion == "free-pro-team@latest" %} +El almacenar una acción en su propio repositorio facilita a +la comunidad de {% data variables.product.prodname_dotcom %} el descubrirla, disminuye el alcance de la base de código para los desarrolladores que solucionan los problemas y que extienden la acción, y desacopla el versionamiento de la acción de aquél que hiciera el código de otra aplicación. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %}Si estás creando una acción que no piensas poner disponible públicamente, puedes {% else %} puedes {% endif %} almacenar los archivos de dicha acción en cualquier ubicación de tu repositorio. Si tienes la intención de combinar la acción, el flujo de trabajo y el código de aplicación en un único repositorio, es recomendable que almacenes las acciones en el directorio `.github`. Por ejemplo, `.github/actions/action-a` y `.github/actions/action-b`. + +### Utilizar la administración de lanzamientos para las acciones + +Para garantizar de que tu acción es compatible con {% data variables.product.prodname_ghe_server %}, debes asegurarte de que no utilices ninguna referencia escrita a mano para las URL de la API de {% data variables.product.prodname_dotcom %}. En vez de esto, utiliza variables de ambiente para referirte a la API de {% data variables.product.prodname_dotcom %}: + +- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`). +- Para el caso de GraphQL, utiliza la variable de ambiente `GITHUB_GRAPHQL_URL`. + +Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)." + +### Utilizar la administración de lanzamientos para las acciones + +Esta sección explica cómo puedes utilizar la administración de lanzamientos para distribuir actualizaciones a tus acciones de forma predecible. + +#### Buenas prácticas para la administración de lanzamientos + +Si estás desarrollando una acción para que la utilicen otras personas, te recomendamos utilizar la administración de lanzamientos para controlar cómo distribuyes las actualizaciones. Los usuarios pueden esperar que una versión mayor de una acción incluya correcciones críticas y parches de seguridad necesarios y que se mantenga compatible con los flujos de trabajo existentes. Deberías considerar lanzar una versión mayor cada que tus cambios afecten la compatibilidad. + +Bajo este acercamiento de administración de lanzamientos, los usuarios no deberían referenciar una rama predeterminada de una acción, ya que es probable que contenga el código más reciente y, en consecuencia, podría ser inestable. En vez de esto, puedes recomendar a tus usuarios que especifiquen una versión mayor cuando utilicen tu acción, y únicamente dirigirlos a una versión más específica si encuentran algún problema. + +Para utilizar una versión específica de la acción, los usuarios pueden configurar su flujo de trabajo de {% data variables.product.prodname_actions %} para apuntar a una etiqueta, el SHA de una confirmación o a una rama denominada para un lanzamiento. + +#### Utilizar etiquetas para la administración de lanzamientos + +Te recomendamos utilizar etiquetas para la administración de lanzamientos de acciones. Al utilizar este acercamiento, tus usuarios pueden distinguir claramente entre las versiones mayores y menores: + +- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`). +- Crear un lanzamiento utilizando un versionamiento semántico. Para obtener más información, consulta "[Creating releases](/articles/creating-a-label/) (Crear lanzamientos)". +- Mover la etiqueta de versión mayor (tal como `v1`, `v2`) para apuntar a la referencia de Git en el lanzamiento actual. Para obtener más información, consulta [Conceptos básicos de Git: etiquetas](https://git-scm.com/book/en/v2/Git-Basics-Tagging)". +- Introducir una etiqueta de versión mayor (`v2`) para los cambios que modificarán sustancialmente los flujos de trabajo existentes. Por ejemplo, un cambio importante será cambiar las entradas de una acción. +- Las versiones mayores pueden lanzarse inicialmente con una etiqueta de `beta` para indicar su estado, por ejemplo, `v2-beta`. La etiqueta `-beta` puede eliminarse entonces cuando esté listo. + +Este ejemplo ilustra como un usuario puede referenciar una etiqueta de un lanzamiento mayor: + +```yaml +steps: + - uses: actions/javascript-action@v1 +``` + +Este ejemplo ilustra como un usuario puede referenciar una etiqueta de lanzamiento de un parche específico: + +```yaml +steps: + - uses: actions/javascript-action@v1.0.1 +``` + +#### Utilizar ramas para la administración de lanzamientos + +Si prefieres utilizar nombres de rama para la administración de lanzamientos, este ejemplo demuestra como referenciar una rama nombrada: + +```yaml +steps: + - uses: actions/javascript-action@v1-beta +``` + +#### Utilizar el SHA de las confirmaciones para la administración de lanzamientos + +Cada confirmación de Git recibe un valor calculado de SHA, el cual es único e inmutable. Los usuarios de tus acciones podrían preferir obtener un valor de SHA para la confirmación, ya que este acercamiento puede ser más confiable que especificar una etiqueta, la cual podría borrarse o moverse. Sin embargo, esto significa que los usuarios no recibirán ls actualizaciones posteriores que se hagan a la acción. Utilizar el valor completo de SHA de una confirmación en vez de su valor abreviado puede ayudar a prevenir que las personas utilicen una confirmación malintencionada que utilice la misma abreviación. + +```yaml +steps: + - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89 +``` + +### Crear un archivo README para tu acción + +Si tienes la intención de compartir públicamente tu acción, te recomendamos crear un archivo README para ayudar a las personas a que aprendan a usar tu acción. Puedes incluir esta información en tu `README.md`: + +- Una descripción detallada de lo que hace la acción. +- Argumentos necesarios de entrada y salida. +- Argumentos opcionales de entrada y salida. +- Secretos que utiliza la acción. +- Variables de entorno que utiliza la acción. +- Un ejemplo de cómo usar tu acción en un flujo de trabajo. + +### Comparar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_github_apps %} + +{% data variables.product.prodname_marketplace %} ofrece herramientas para mejorar tu flujo de trabajo. Comprender las diferencias y los beneficios de cada herramienta te permitirá seleccionar la mejor herramienta para tu trabajo. Para obtener más información acerca de la creación de apps, consulta "[Acerca de las apps](/apps/about-apps/)". + +#### Fortalezas de las acciones y las aplicaciones de GitHub + +Mientras que tanto las {% data variables.product.prodname_actions %} como las {% data variables.product.prodname_github_app %} proporcionan formas de construir herramientas de automatización y flujo de trabajo, cada una tiene fortalezas que las hacen útiles de diferentes maneras. + +{% data variables.product.prodname_github_apps %}: +* Se ejecutan de manera persistente y pueden reaccionar rápidamente a los eventos. +* Funcionan bien cuando se necesitan datos de manera persistente. +* Funcionan mejor con las solicitudes de API que no consumen mucho tiempo. +* Se ejecutan en un servidor o infraestructura de computación que proporciones. + +{% data variables.product.prodname_actions %}: +* Brindan automatización que puede realizar una integración continua y una implementación continua. +* Pueden ejecutarse directamente en máquinas de ejecutor o en contenedores Docker. +* Pueden incluir acceso a un clon de tu repositorio, lo que permite que las herramientas de implementación y publicación, los formateadores de código y las herramientas de la línea de comando accedan a tu código. +* No necesitan que implementas un código o que sirvas una aplicación. +* Tienen una interfaz simple para crear y usar secretos, que permite que las acciones interactúen con servicios de terceros sin la necesidad de almacenar las credenciales de la persona que utiliza la acción. + +### Further reading + +- "[Herramientas de desarrollo para {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)" diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md new file mode 100644 index 0000000000000..d31c1b8402bc8 --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -0,0 +1,130 @@ +--- +title: Crear una acción para pasos de ejecución compuestos +intro: 'En esta guía aprenderás cómo crear una acción para los pasos de ejecución compuestos.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +En esta guía aprenderás sobre los componentes básicos que se requieren para crear y utilizar una acción de pasos de ejecución compuestos empacada. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" y después "Goodbye", o si proporcionas un nombre personalizado, imprime "Hello [who-to-greet]" y luego "Goodbye". La acción también mapea un número aleatorio hacia la variable de salida `random-number`, y ejecuta un script denominado `goodbye.sh`. + +Una vez que completes este proyecto, deberás entender cómo construir tu accion para pasos de ejecución compuestos para probarla en un flujo de trabajo. + +### Prerrequisitos + +Antes de que comiences, crearás un repositorio de {% data variables.product.product_name %}. + +1. Crea un repositorio público nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o utilizar el siguiente ejemplo de `hello-world-composite-run-steps-action`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". + +1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". + +1. Desde tu terminal, cambia los directorios en el repositorio nuevo. + + ```shell + cd hello-world-composite-run-steps-action + ``` + +2. En el repositorio `hello-world-composite-run-steps-action`, crea un archivo nuevo que se llame `goodbye.sh` y agrega el siguiente código de ejemplo: + + ```bash + echo "Goodbye" + ``` + +3. Desde tu terminal, haz ejecutable a `goodbye.sh`. + + ```shell + chmod +x goodbye.sh + ``` + +1. Desde tu terminal, ingresa tu archivo `goodbye.sh`. + ```shell + git add goodbye.sh + git commit -m "Add goodbye script" + git push + ``` + +### Crear un archivo de metadatos de una acción + +1. En el repositorio `hello-world-composite-run-steps-action`, crea un archivo nuevo que se llame `action.yml` y agrega el siguiente código de ejemplo. Para obtener más información acerca de esta sintaxis, consulta la sección de "[`runs` para encontrar los pasos de ejecución compuestos](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-run-steps-actions)". + + {% raw %} + **action.yml** + ```yaml + name: 'Hello World' + description: 'Greet someone' + inputs: + who-to-greet: # id of input + description: 'Who to greet' + required: true + default: 'World' + outputs: + random-number: + description: "Random number" + value: ${{ steps.random-number-generator.outputs.random-id }} + runs: + using: "composite" + steps: + - run: echo Hello ${{ inputs.who-to-greet }}. + shell: bash + - id: random-number-generator + run: echo "::set-output name=random-id::$(echo $RANDOM)" + shell: bash + - run: ${{ github.action_path }}/goodbye.sh + shell: bash + ``` + {% endraw %} + Este archivo define la entrada `who-to-greet`, mapea el número generado aleatoriamente en la variable de salida `random-number` y ejecuta el script de `goodbye.sh`. También le dice al ejecutor cómo ejecutar la acción de los pasos de ejecución compuestos. + + Para obtener más información acerca de cómo administrar las alidas, consulta la secicón "[`outputs` para los pasos de ejecución compuestos](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-run-steps-actions)". + + Para obtener más información acerca de cómo utilizar `github.action_path`, consulta la sección "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". + +1. Desde tu terminal, ingresa tu archivo `action.yml`. + + ```shell + git add action.yml + git commit -m "Add action" + git push + ``` + +1. Desde tu terminal, agrega una etiqueta. Este ejemplo utiliza una etiqueta que se llama `v1`. Para obtener más información, consulta la sección "[Acerca de las acciones](/actions/creating-actions/about-actions#using-release-management-for-actions)". + + ```shell + git tag -a -m "Description of this release" v1 + git push --follow-tags + ``` + +### Probar tu acción en un flujo de trabajo + +El siguiente código de flujo de trabajo utiliza la acción completada de "hello world" que hiciste previamente en "[Crear un archivo de metadatos para la acción](/actions/creating-actions/creating-a-composite-run-steps-action#creating-an-action-metadata-file)". + +Copia el código del flujo de trabajo en un archivo de `.github/workflows/main.yml` en otro repositorio, pero reemplaza `actions/hello-world-composite-run-steps-action@v1` con el repositorio y etiqueta que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre. + +{% raw %} +**.github/workflows/main.yml** +```yaml +on: [push] + +jobs: + hello_world_job: + runs-on: ubuntu-latest + name: A job to say hello + steps: + - uses: actions/checkout@v2 + - id: foo + uses: actions/hello-world-composite-run-steps-action@v1 + with: + who-to-greet: 'Mona the Octocat' + - run: echo random-number ${{ steps.foo.outputs.random-number }} + shell: bash +``` +{% endraw %} + +Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. La salida deberá incluir "Hello Mona the Octocat", el resultado del script de "Goodbye" y un número aleatorio. diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md new file mode 100644 index 0000000000000..75c588f069aa5 --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md @@ -0,0 +1,236 @@ +--- +title: Crear una acción de contenedor de Docker +intro: 'Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor Docker.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/creating-a-docker-container-action + - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action + - /actions/automating-your-workflow-with-github-actions/creating-a-docker-container-action + - /actions/building-actions/creating-a-docker-container-action +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor de Docker. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado. + +Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de contenedor Docker y probarla en un flujo de trabajo. + +{% data reusables.github-actions.self-hosted-runner-reqs-docker %} + +### Prerrequisitos + +Puede ser útil tener un entendimiento básico de variables de entorno de las {% data variables.product.prodname_actions %} y del sistema de archivos de contenedor Docker: + +- "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" +- "[Entornos virtuales para {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" + +Antes de comenzar, necesitarás crear un repositorio GitHub. + +1. Crea un repositorio nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o usar "hello-world-docker-action" como este ejemplo. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". + +1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". + +1. Desde tu terminal, cambia los directorios en el repositorio nuevo. + + ```shell + cd hello-world-docker-action + ``` + +### Crear un Dockerfile + +En tu nuevo directorio `hello-world-docker-action`, crea un nuevo archivo `Dockerfile`. Para obtener más información, consulta al "[Sporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)". + +**Dockerfile** +```dockerfile +# Imagen del contenedor que ejecuta tu código +FROM alpine:3.10 + +# Copias tu archivo de código de tu repositorio de acción a la ruta `/`del contenedor +COPY entrypoint.sh /entrypoint.sh + +# Archivo del código a ejecutar cuando comienza el contedor del docker (`entrypoint.sh`) +ENTRYPOINT ["/entrypoint.sh"] +``` + +### Crear un archivo de metadatos de una acción + +Crear un nuevo archivo `action.yml` en el directorio `hello-world-docker` que creaste anteriormente. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)". + +{% raw %} +**action.yml** +```yaml +# action.yml +name: 'Hello World' +description: 'Greet someone and record the time' +inputs: + who-to-greet: # id of input + description: 'Who to greet' + required: true + default: 'World' +outputs: + time: # id of output + description: 'The time we greeted you' +runs: + using: 'docker' + image: 'Dockerfile' + args: + - ${{ inputs.who-to-greet }} +``` +{% endraw %} + +Este metado define un parámetro de entrada `who-to-greet` y uno de salida `time`. Para pasar las entradas al contenedor Docker, debes declarar la entrada usando `inputs` y pasar la entrada a la palabra clave `args`. + +{% data variables.product.prodname_dotcom %} creará una imagen desde tu `Dockerfile` y ejecutar comandos en nuevo contenedor usando esta imagen. + +### Escribir el código de la acción + +Puedes elegir cualquier imagen de Docker base y, por lo tanto, cualquier idioma para tu acción. El siguiente ejemplo de script shell usa la variable de entrada `who-to-greet` para imprimir "Hello [who-to-greet]" en el archivo de registro. + +A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo. Para que {% data variables.product.prodname_dotcom %} reconozca las variables de salida, debes usar un comando de flujo de trabajo en una sintaxis específica: `echo ":: set-Output Name =::"`. Para obtener más información, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)". + +1. Crea un archivo `entrypoint.sh` nuevo en el directorio `hello-world-docker-action`. + +1. Convierte tu archivo `entrypoint.sh` en ejecutable: + + ```shell + chmod +x entrypoint.sh + ``` + +1. Agrega el siguiente código a tu archivo `entrypoint.sh`. + + **entrypoint.sh** + ```shell + #!/bin/sh -l + + echo "Hello $1" + time=$(date) + echo "::set-output name=time::$time" + ``` + + Si `entrypoint.sh` se ejecuta sin errores, el estado de la acción se establece en `exitoso`. También puedes establecer explícitamente códigos de salida en el código de tu acción para proporcionar el estado de una acción. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)". + +### Crear un README + +Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción. + +En tu directorio <`hello-world-docker-action`, crea un archivo `README.md` que especifique la siguiente información: + +- Una descripción detallada de lo que hace la acción. +- Argumentos necesarios de entrada y salida. +- Argumentos opcionales de entrada y salida. +- Secretos que utiliza la acción. +- Variables de entorno que utiliza la acción. +- Un ejemplo de cómo usar tu acción en un flujo de trabajo. + +**README.md** +```markdown +# Acción de docker Hello world + +Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. + +## Entradas + +### `who-to-greet` + +**Obligatorio** El nombre de la persona a quien saludar. Default `"World"`. + +## Outputs + +### `time` + +El tiempo en que lo saludamos. + +## Ejemplo de uso + +uses: actions/hello-world-docker-action@v1 +with: + who-to-greet: 'Mona the Octocat' +``` + +### Confirmar, etiquetar y subir tu acción a GitHub + +Desde tu terminal, confirma tus archivos `action.yml`, `entrypoint.sh`, `Dockerfile`, y `README.md`. + +También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". + +```shell +git add action.yml entrypoint.sh Dockerfile README.md +git commit -m "Mi primera acción está lista" +git tag -a -m "Mi primera versión de acción" v1 +git push --follow-tags +``` + +### Probar tu acción en un flujo de trabajo + +Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio. + +{% data reusables.actions.enterprise-marketplace-actions %} + +#### Ejemplo usando una acción pública + +El siguiente código de flujo de trabajo usa la acción completa hello world en el repositorio público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copia el siguiente código de ejemplo de flujo de trabajo en un archivo `.github/workflows/main.yml`, pero reemplaza `actions/hello-world-docker-action` por tu nombre de repositorio y acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. + +{% raw %} +**.github/workflows/main.yml** +```yaml +on: [push] + +jobs: + hello_world_job: + runs-on: ubuntu-latest + name: A job to say hello + steps: + - name: Hello world action step + id: hello + uses: actions/hello-world-docker-action@v1 + with: + who-to-greet: 'Mona the Octocat' + # Use the output from the `hello` step + - name: Get the output time + run: echo "The time was ${{ steps.hello.outputs.time }}" +``` +{% endraw %} + +#### Ejemplo usando una acción privada + +Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. + +{% raw %} +**.github/workflows/main.yml** +```yaml +on: [push] + +jobs: + hello_world_job: + runs-on: ubuntu-latest + name: A job to say hello + steps: + # To use this repository's private action, + # you must check out the repository + - name: Checkout + uses: actions/checkout@v2 + - name: Hello world action step + uses: ./ # Uses an action in the root directory + id: hello + with: + who-to-greet: 'Mona the Octocat' + # Use the output from the `hello` step + - name: Get the output time + run: echo "The time was ${{ steps.hello.outputs.time }}" +``` +{% endraw %} + +Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Debajo de **Jobs** o en la gráfica de visualización, da clic en **A job to say hello**. {% endif %}Debrás ver la frase "Hello Mona the Octocat" o el nombre que utilizaste para la entrada `who-to-greet` y la marca de tiempo impresa en la bitácora. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} +![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md new file mode 100644 index 0000000000000..70427bb27411b --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md @@ -0,0 +1,268 @@ +--- +title: Crear una acción de JavaScript +intro: 'En esta guía, aprenderás como desarrollar una acción de JavaScript usando el kit de herramientas de acciones.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/creating-a-javascript-action + - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action + - /actions/automating-your-workflow-with-github-actions/creating-a-javascript-action + - /actions/building-actions/creating-a-javascript-action +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +En esta guía, aprenderás acerca de los componentes básicos necesarios para crear y usar una acción de JavaScript empaquetada. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado. + +Esta guía usa el módulo Node.js del kit de herramientas {% data variables.product.prodname_actions %} para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). + +Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de JavaScript y probarla en un flujo de trabajo. + +{% data reusables.github-actions.pure-javascript %} + +### Prerrequisitos + +Antes de comenzar, necesitarás descargar Node.js y crear un repositorio GitHub. + +1. Descarga e instala Node.js 12.x, que incluye npm. + + https://nodejs.org/en/download/current/ + +1. Crea un repositorio nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o usar "hello-world-javascript-action" como este ejemplo. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". + +1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". + +1. Desde tu terminal, cambia los directorios en el repositorio nuevo. + + ```shell + cd hello-world-javascript-action + ``` + +1. Desde tu terminal, inicializa el directorio con un archivo `package.json`. + + ```shell + npm init -y + ``` + +### Crear un archivo de metadatos de una acción + +Crea un nuevo archivo `action.yml` en el directorio `hello-world-javascript-action` con el siguiente código de ejemplo. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)". + + +**action.yml** +```yaml +name: 'Hello World' +description: 'Greet someone and record the time' +inputs: + who-to-greet: # id of input + description: 'Who to greet' + required: true + default: 'World' +outputs: + time: # id of output + description: 'The time we greeted you' +runs: + using: 'node12' + main: 'index.js' +``` + +Este archivo define la entrada `who-to-greet` y la salida `time`. También informa al ejecutador de la acción cómo empezar a ejecutar esta acción de JavaScript. + +### Añadir paquetes de kit de herramientas de acciones + +El kit de herramientas de acciones es una recopilación de los paquetes Node.js que te permiten desarrollar rápidamente acciones de JavaScript con más consistencia. + +El paquete del kit de herramientas [`@actions/Core`](https://github.com/actions/toolkit/tree/main/packages/core) proporciona una interfaz a los comandos del flujo de trabajo, a las variables de entrada y de salida, a los estados de salida y a los mensajes de depuración. + +El kit de herramientas también ofrece un paquete [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) que devuelve un cliente Octokit REST autenticado así como el acceso a los contextos de las GitHub Actions. + +El kit de herramientas ofrece más de un paquete `core` y `github`. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). + +En tu terminal, instala los paquetes `core` and `github` del kit de herramientas de acciones. + +```shell +npm install @actions/core +npm install @actions/github +``` + +Ahora deberías ver un directorio `node_modules` con los módulos que acabas de instalar y un archivo `package-lock.json` con las dependencias del módulo instalado y las versiones de cada módulo instalado. + +### Escribir el código de la acción + +Esta acción usa el kit de herramientas para obtener la variable de entrada `who-to-greet` requerida en el archivo de metadatos de la acción e imprime "Hello [who-to-greet]" en un mensaje de depuración del registro. A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo. + +Las Acciones de GitHub proporcionan información de contexto sobre el evento de webhooks, las referencias de Git, el flujo de trabajo, la acción y la persona que activó el flujo de trabajo. Para acceder a la información de contexto, puedes usar el paquete `github`. La acción que escribirás imprimirá el evento de webhook que carga el registro. + +Agrega un archivo nuevo denominado `index.js`, con el siguiente código. + +**index.js** +```javascript +const core = require('@actions/core'); +const github = require('@actions/github'); + +try { + // `who-to-greet` input defined in action metadata file + const nameToGreet = core.getInput('who-to-greet'); + console.log(`Hello ${nameToGreet}!`); + const time = (new Date()).toTimeString(); + core.setOutput("time", time); + // Get the JSON webhook payload for the event that triggered the workflow + const payload = JSON.stringify(github.context.payload, undefined, 2) + console.log(`The event payload: ${payload}`); +} catch (error) { + core.setFailed(error.message); +} +``` + +Si en el ejemplo anterior de `index.js` ocurre un error, entonces `core.setFailed(error.message);` utilizará el paquete [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) del kit de herramientas de las acciones para registrar un mensaje y configurar un código de salida defectuoso. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)". + + +### Crear un README + +Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción. + +En tu directorio `hello-world-javascript-action`, crea un archivo `README.md` que especifique la siguiente información: + +- Una descripción detallada de lo que hace la acción. +- Argumentos necesarios de entrada y salida. +- Argumentos opcionales de entrada y salida. +- Secretos que utiliza la acción. +- Variables de entorno que utiliza la acción. +- Un ejemplo de cómo usar tu acción en un flujo de trabajo. + +**README.md** +```markdown +# Hello world docker action + +Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. + +## Entradas + +### `who-to-greet` + +**Obligatorio** El nombre de la persona a quien saludar. Default `"World"`. + +## Outputs + +### `time` + +El tiempo en que lo saludamos. + +## Example usage + +uses: actions/hello-world-javascript-action@v1.1 +with: + who-to-greet: 'Mona the Octocat' +``` + +### Confirmar, etiquetar y subir tu acción a GitHub + +{% data variables.product.product_name %} descarga cada acción ejecutada en un flujo de trabajo durante el tiempo de ejecución y la ejecuta como un paquete completo de código antes de que puedas usar comandos de flujo de trabajo como `run` para interactuar con la máquina del ejecutor. Eso significa que debes incluir cualquier dependencia del paquete requerida para ejecutar el código de JavaScript. Necesitarás verificar los paquetes `core` y `github` del kit de herramientas para el repositorio de tu acción. + +Desde tu terminal, confirma tus archivos `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json` y `README.md`. Si agregaste un archivo `.gitignore` que enumera `node_modules`, deberás eliminar esa línea para confirmar el directorio `node_modules`. + +También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". + + +```shell +git add action.yml index.js node_modules/* package.json package-lock.json README.md +git commit -m "Mi primera acción está lista" +git tag -a -m "Mi primera versión de acción" v1 +git push --follow-tags +``` + +Ingresar tu directorio de `node_modules` puede causar problemas. Como alternativa, puedes utilizar una herramienta que se llama [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar tu código y módulos en un archivo que se utilice para distribución. + +1. Instala `vercel/ncc` ejecutando este comando en tu terminal. `npm i -g @vercel/ncc` + +1. Compila tu archivo `index.js`. `ncc build index.js --license licenses.txt` + + Verás un nuevo archivo `dist/index.js` con tu código y los módulos compilados. También verás un archivo asociado de `dist/licenses.txt` que contiene todas las licencias de los `node_modules` que estás utilizando. + +1. Cambia la palabra clave `main` en tu archivo `action.yml` para usar el nuevo archivo `dist/index.js`. `main: 'dist/index.js'` + +1. Si ya has comprobado tu directorio `node_modules`, eliminínalo. `rm -rf node_modules/*` + +1. Desde tu terminal, confirma las actualizaciones para tu `action.yml`, `dist/index.js` y `node_modules`. +```shell +git add action.yml dist/index.js node_modules/* +git commit -m "Use vercel/ncc" +git tag -a -m "My first action release" v1 +git push --follow-tags +``` + +### Probar tu acción en un flujo de trabajo + +Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio. + +{% data reusables.actions.enterprise-marketplace-actions %} + +#### Ejemplo usando una acción pública + +El siguiente código de flujo de trabajo usa la acción hello world completada en el repositorio `actions/hello-world-javascript-action`. Copia el código de flujo de trabajo en un archivo `.github/workflows/main.yml`, pero reemplaza el repositorio `actions/hello-world-javascript-action` con el repositorio que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre. + +{% raw %} +**.github/workflows/main.yml** +```yaml +on: [push] + +jobs: + hello_world_job: + runs-on: ubuntu-latest + name: A job to say hello + steps: + - name: Hello world action step + id: hello + uses: actions/hello-world-javascript-action@v1.1 + with: + who-to-greet: 'Mona the Octocat' + # Use the output from the `hello` step + - name: Get the output time + run: echo "The time was ${{ steps.hello.outputs.time }}" +``` +{% endraw %} + +#### Ejemplo usando una acción privada + +Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. + +{% raw %} +**.github/workflows/main.yml** +```yaml +on: [push] + +jobs: + hello_world_job: + runs-on: ubuntu-latest + name: A job to say hello + steps: + # To use this repository's private action, + # you must check out the repository + - name: Checkout + uses: actions/checkout@v2 + - name: Hello world action step + uses: ./ # Uses an action in the root directory + id: hello + with: + who-to-greet: 'Mona the Octocat' + # Use the output from the `hello` step + - name: Get the output time + run: echo "The time was ${{ steps.hello.outputs.time }}" +``` +{% endraw %} + +Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Debajo de **Jobs** o en la gráfica de visualización, da clic en **A job to say hello**. {% endif %}Debrás ver la frase "Hello Mona the Octocat" o el nombre que utilizaste para la entrada `who-to-greet` y la marca de tiempo impresa en la bitácora. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} +![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run-updated.png) +{% else %} +![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run.png) +{% endif %} diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md new file mode 100644 index 0000000000000..16760fb16ecdf --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -0,0 +1,108 @@ +--- +title: Soporte de Dockerfile para GitHub Actions +shortTitle: Docker +intro: 'Cuando creas un "Dockerfile" para una acción de un contenedor de Docker, debes estar consciente de cómo interactúan algunas instrucciones de Docker con GitHub Actions y con el archivo de metadatos de la acción.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/building-actions/dockerfile-support-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'reference' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de las instrucciones de Dockerfile + +Un `Dockerfile` contiene instrucciones y argumentos que definen el contenido y comportamiento inicial de un contenedor de Docker. Para obtener más información acerca de las instrucciones compatibles con Docker, consulta la sección "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" en la documentación de Docker. + +### Instrucciones e invalidaciones de Dockerfile + +Algunas instrucciones de Docker interactúan con GitHub Actions, y un archivo de metadatos de la acción puede invalidar algunas instrucciones de Docker. Asegúrate de que estás familiarizado con la manera en que tu Dockerfile interactúa con {% data variables.product.prodname_actions %} para prevenir cualquier comportamiento inesperado. + +#### USER + +Las acciones de Docker deben ejecutarse mediante el usuario predeterminado de Docker (root). No utilices la instrucción `USER` en tu `Dockerfile`, ya que no podrás acceder a `GITHUB_WORKSPACE`. Para obtener más información, consulta la sección "[Utilizar variables del ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [USER reference](https://docs.docker.com/engine/reference/builder/#user) en la documentación de Docker. + +#### FROM + +La primera instrucción en el `Dockerfile` debe ser `FROM`, la cual selecciona una imagen base de Docker. Para obtener más información, consulta la sección "[FROM reference](https://docs.docker.com/engine/reference/builder/#from) en la documentación de Docker. + +Estas son algunas de las mejores prácticas para configurar el argumento `FROM`: + +- Se recomienda utilizar imágenes oficiales de Docker. Por ejemplo, `python` o `ruby`. +- Utiliza una etiqueta de versión si es que existe, preferentemente con una versión mayor. Por ejemplo, utiliza `node:10` en vez de `node:latest`. +- Se recomienda utilizar imágenes de Docker que se basen en el sistema operativo [Debian](https://www.debian.org/). + +#### WORKDIR + +{% data variables.product.product_name %} configura la ruta del directorio de trabajo en la variable de ambiente `GITHUB_WORKSPACE`. No se recomienda utilizar la instrucción `WORKDIR` en tu `Dockerfile`. Antes de que se ejecute la acción, {% data variables.product.product_name %} montará el directorio `GITHUB_WORKSPACE`sobre cualquiera que fuera la ubicación en la imagen de Docker y configurará a `GITHUB_WORKSPACE` como el directorio de trabajo. Para obtener más información, consulta la sección "[Utilizar variables de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) en la documentación de Docker. + +#### ENTRYPOINT + +Si defines el `entrypoint` en un archivo de metadatos de una acción, este invalidará el `ENTRYPOINT` definido en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)". + +La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker. + +Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`. + +``` +ENTRYPOINT ["echo $GITHUB_SHA"] +``` + + Si quieres la sustitución de variables, entonces puedes utilizar la forma _shell_ o ejecutar el shell directamente. Por ejemplo, al utilizar el siguiente formato _exec_ puedes ejecutar un shell para imprimir el valor almacenado en la variable de ambiente `GITHUB_SHA`. + +``` +ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] +``` + + Para proporcionar el `args` que se definió en el archivo de metadatos de la acción en un contenedor de Docker que utiliza la forma _exec_ en el `ENTRYPOINT`, recomendamos crear un script de shell llamado `entrypoint.sh` al que puedas llamar desde la instrucción `ENTRYPOINT`: + +##### *Dockerfile* de ejemplo +``` +# Container image that runs your code +FROM debian:9.5-slim + +# Copies your code file from your action repository to the filesystem path `/` of the container +COPY entrypoint.sh /entrypoint.sh + +# Executes `entrypoint.sh` when the Docker container starts up +ENTRYPOINT ["/entrypoint.sh"] +``` + +##### Archivo *entrypoint.sh* de ejemplo + +Al utilizar el Dockerfile de ejemplo que se muestra anteriormente, {% data variables.product.product_name %} enviará el `args` configurado en el archivo de metadatos de la acción como un argumento de `entrypoint.sh`. Agrega el `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) hasta arriba del archivo `entrypoint.sh` para utilizar explicitamente el shell compilante [POSIX](https://en.wikipedia.org/wiki/POSIX) del sistema. + +``` sh +#!/bin/sh + +# `$*` expands the `args` supplied in an `array` individually +# or splits `args` in a string separated by whitespace. +sh -c "echo $*" +``` + +Tu código debe ser ejecutable. Asegúrate que el archivo `entrypoint.sh` tiene permisos de `execute` antes de utilizarlo en un flujo de trabajo. Puedes modificar los permisos de tu terminal si utilizas este comando: + ``` sh + chmod +x entrypoint.sh + ``` + +Cuando un script de shell de `ENTRYPOINT` no es ejecutable, recibirás un error similar al siguiente: + +``` sh +Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown +``` + +#### CMD + +Si defines el `args` en el archivo de metadatos de la acción, éste invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)". + +Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos: + +{% data reusables.github-actions.dockerfile-guidelines %} + +### Capacidades de Linux compatibles + +{% data variables.product.prodname_actions %} es compatible con las capacidades predeterminadas de Linux que acepta Docker. Estas capacidades no se pueden añadir ni eliminar. Para obtener más información acerca de las capacidades predeterminadas de Linux con las cuales es compatible Docker, consulta "[Runtime priovilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" en la documentación de Docker. Para conocer más acerca de las capacidades de Linux, consulta "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html) en las páginas man de Linux. diff --git a/translations/es-ES/content/actions/creating-actions/index.md b/translations/es-ES/content/actions/creating-actions/index.md new file mode 100644 index 0000000000000..0aea79ca6540b --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/index.md @@ -0,0 +1,25 @@ +--- +title: Crear acciones +intro: 'Puedes crear tus propias acciones, usar y personalizar acciones compartidas por la comunidad {% data variables.product.prodname_dotcom %} o escribir y compartir las acciones que construyes.' +redirect_from: + - /articles/building-actions + - /github/automating-your-workflow-with-github-actions/building-actions + - /actions/automating-your-workflow-with-github-actions/building-actions + - /actions/building-actions + - /articles/creating-a-github-action/ +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% link_in_list /about-actions %} +{% link_in_list /creating-a-docker-container-action %} +{% link_in_list /creating-a-javascript-action %} +{% link_in_list /creating-a-composite-run-steps-action %} +{% link_in_list /metadata-syntax-for-github-actions %} +{% link_in_list /dockerfile-support-for-github-actions %} +{% link_in_list /setting-exit-codes-for-actions %} +{% link_in_list /publishing-actions-in-github-marketplace %} diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md new file mode 100644 index 0000000000000..6200ec5b7925f --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -0,0 +1,762 @@ +--- +title: Sintaxis de metadatos para acciones de GitHub +shortTitle: Sintaxis de metadatos +intro: Puedes crear acciones para realizar tareas en tu repositorio. Las acciones requieren un archivo de metadatos que use la sintaxis YAML. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/metadata-syntax-for-github-actions + - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions + - /actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions + - /actions/building-actions/metadata-syntax-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'reference' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %} + +Las acciones Docker y JavaScript requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos del archivo de metadatos definen las entradas, las salidas y el punto de entrada principal para tu acción. + +Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." + +### `name` + +**Requerido** El nombre de tu acción. {% data variables.product.prodname_dotcom %} muestra el `name` (nombre) en la pestaña **Actions** (Acciones) para ayudarte a identificar visualmente las acciones en cada trabajo. + +### `author` + +**Opcional** El nombre del autor de las acciones. + +### `description` + +**Requerido** Una descripción breve de la acción. + +### `inputs` + +**Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas. + +#### Ejemplo + +Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with`, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". + +```yaml +inputs: + numOctocats: + description: 'Number of Octocats' + required: false + default: '1' + octocatEyeColor: + description: 'Eye color of the Octocats' + required: true +``` + +Cuando especificas una entrada para una acción en un archivo de flujo de trabajo o usas un valor de entrada predeterminado, {% data variables.product.prodname_dotcom %} crea una variable de entorno para la entrada con el nombre `INPUT_`. La variable de entorno creada convierte los nombre de entrada en letras mayúscula y reemplaza los espacios con los caracteres `_`. + +Por ejemplo, si un flujo de trabajo definió las entradas numOctocats y octocatEyeColor, el código de acción podría leer los valores de las entradas usando las variables de entorno `INPUT_NUMOCTOCATS` y `INPUT_OCTOCATEYECOLOR`. + +#### `inputs.` + +**Requerido** Un identificador `string` (cadena) para asociar con la entrada. El valor de `` es un mapa con los metadatos de la entrada. `` debe ser un identificador único dentro del objeto `inputs` (entradas). El ``> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. + +#### `inputs..description` + +**Requerido** Una descripción de `string` del parámetro de entrada. + +#### `inputs..required` + +**Requerido** Un `boolean` (booleano) para indicar si la acción requiere el parámetro de entrada. Establecer en `true` cuando se requiera el parámetro. + +#### `inputs..default` + +**Opcional** Una `string` que representa el valor predeterminado. El valor predeterminado se usa cuando un parámetro de entrada no se especifica en un archivo de flujo de trabajo. + +### `outputs (salidas)` + +**Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior. Por ejemplo, si se realizó una acción además de las dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada. + +Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)". + +#### Ejemplo + +```yaml +outputs: + sum: # id of the output + description: 'The sum of the inputs' +``` + +#### `outputs.` + +**Requerido** Un identificador `string` para asociar con la salida. El valor de `` es un mapa con los metadatos de la salida. `` debe ser un identificador único dentro del objeto `outputs` (salidas). El ``> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. + +#### `outputs..description` + +**Requerido** Una descripción de `string` del parámetro de salida. + +### `outputs` para con de pasos de ejecución compuestos + +Los `outputs` **Opcionales** utilizan los mismos parámetros que los `outputs.` and los `outputs..description` (consulta la sección "[`outputs` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), pero también incluyen el token de `value`. + +#### Ejemplo + +{% raw %} +```yaml +outputs: + random-number: + description: "Random number" + value: ${{ steps.random-number-generator.outputs.random-id }} +runs: + using: "composite" + steps: + - id: random-number-generator + run: echo "::set-output name=random-id::$(echo $RANDOM)" + shell: bash +``` +{% endraw %} + +#### `outputs..value` + +**Requerido** El valor al cual se mapeará el parámetro de salida. Puedes configurarlo a una `string` o a una expresión con contexto. Por ejemplo, puedes utilizar el contexto `steps` para configurar el `value` de una salida al valor de salida de un paso. + +Para obtener más información sobre cómo utilizar la sintaxis de contexto y de expresión, consulta la sección "[Sintaxis de contexto y de expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +### `runs` para acciones de JavaScript + +**Requerido** Configura la ruta al código de la acción y a la aplicación que se utiliza para ejecutar dicho código. + +#### Ejemplo usando Node.js + +```yaml +runs: + using: 'node12' + main: 'main.js' +``` + +#### `runs.using` + +**Requerido** La aplicación utilizada para el código especificado en [`main`](#runsmain). + +#### `runs.main` + +**Requerido** El archivo que contiene tu código de acción. La aplicación especificada en [`using`](#runsusing) ejecuta este archivo. + +#### `pre` + +**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-if). + +En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`: + +```yaml +runs: + using: 'node12' + pre: 'setup.js' + main: 'index.js' + post: 'cleanup.js' +``` + +#### `pre-if` + +**Opcional** Te permite definir las condiciones para la ejecución de la acción `pre:`. La acción `pre:` únicamente se ejecutará si se cumplen las condiciones en `pre-if`. Si no se configura, `pre-if` se configurará predefinidamente como `always()`. Nota que el contexto `step` no está disponible, ya que no se ha ejecutado ningún paso todavía. + +En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados en linux: + +```yaml + pre: 'cleanup.js' + pre-if: 'runner.os == linux' +``` + +#### `post` + +**Opcional** Te permite ejecutar un script al final de un job, una vez que se haya completado la acción `main:`. Por ejemplo, puedes utilizar `post:` para finalizar algunos procesos o eliminar los archivos innecesarios. La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. + +En este ejemplo, la acción `post:` ejecuta un script llamado `cleanup.js`: + +```yaml +runs: + using: 'node12' + main: 'index.js' + post: 'cleanup.js' +``` + +La acción `post:` siempre se ejecuta predeterminadamente, pero la puedes invalidar utilizando `post-if`. + +#### `post-if` + +**Opcional** Te permite definir condiciones para la ejecución de la acción `post:`. La acción `post` únicamente se ejecutará si se cumplen las condiciones en `post-if`. Si no se configura, `pre-if` se configurará predeterminadamente como `always()`. + +Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados en Linux: + +```yaml + post: 'cleanup.js' + post-if: 'runner.os == linux' +``` + +### `runs` para acciones con pasos de ejecución compuestos + +**Requerido** Configura la ruta a la acción compuesta, y la aplicación que se utiliza para ejecutar el código. + +#### `runs.using` + +**Requerido** Para utilizar una acción de pasos de ejecución compuestos, configúrala como `"composite"`. + +#### `runs.steps` + +**Requerido** Los pasos de ejecución que planeas ejecutar en esta acción. + +##### `runs.steps[*].run` + +**Requerido** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción: + +{% raw %} +```yaml +runs: + using: "composite" + steps: + - run: ${{ github.action_path }}/test/script.sh + shell: bash +``` +{% endraw %} + +Como alternativa, puedes utilizar `$GITHUB_ACTION_PATH`: + +```yaml +runs: + using: "composite" + steps: + - run: $GITHUB_ACTION_PATH/script.sh + shell: bash +``` + +Para obtener más información, consulta la sección "[``](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". + +##### `runs.steps[*].shell` + +**Requerido** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). + +##### `runs.steps[*].name` + +**Opcional** El nombre del paso de ejecución compuesto. + +##### `runs.steps[*].id` + +**Opcional** Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +##### `runs.steps[*].env` + +**Opcional** Configura un `map` de variables de ambiente únicamente para este paso. Si quieres modificar las variables de ambiente que se almacenan en el flujo de trabajo, utiliza {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} en un paso de ejecución compuesto. + +##### `runs.steps[*].working-directory` + +**Opcional** Especifica el directorio de trabajo en donde se ejecuta un comando. + +### `runs` para acciones de Docker + +**Requerido** Configura la imagen utilizada para la acción de Docker. + +#### Ejemplo utilizando un Dockerfile en tu repositorio + +```yaml +runs: + using: 'docker' + image: 'Dockerfile' +``` + +#### Ejemplo usando un contenedor de registro Docker público + +```yaml +runs: + using: 'docker' + image: 'docker://debian:stretch-slim' +``` + +#### `runs.using` + +**Requerido** Debes configurar este valor como `'docker'`. + +#### `pre-entrypoint` + +**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente pero la puedes invalidar utilizando [`pre-if`](#pre-if). + +La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. + +En este ejemplo, la acción `pre.entrypoint:` ejecuta un script llamado `setup.sh`: + +```yaml +runs: + using: 'docker' + image: 'Dockerfile' + args: + - 'bzz' + pre-entrypoint: 'setup.sh' + entrypoint: 'main.sh' +``` + +#### `runs.image` + +**Requerido** La imagen de Docker a utilizar como el contenedor para ejecutar la acción. El valor puede ser el nombre de la imagen base de Docker, un `Dockerfile` local en tu repositorio, o una imagen pública en Docker Hub u otro registro. Para referenciar un `Dockerfile` local a tu repositorio, utiliza una ruta relativa a tu archivo de metadatos de la acción. La aplicación `docker` ejecutará este archivo. + +#### `runs.env` + +**Opcional** Especifica mapa clave/de valores de las variables del ambiente para configurar en el ambiente del contenedor. + +#### `runs.entrypoint` + +**Opcional** Invalida el `ENTRYPOINT` de Docker en el `Dockerfile`, o lo configura si no se había especificado anteriormente. Utiliza `entrypoint` cuando el `Dockerfile` no especifique un `ENTRYPOINT` o cuando quieras invalidar la instrucción de `ENTRYPOINT`. Si omites el `entrypoint`, se ejecutarán los comandos que especifiques en la instrucción `ENTRYPOINT` de Docker. La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. + +Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)". + +#### `post-entrypoint` + +**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes invalidarla utilizando [`post-if`](#post-if). + +```yaml +runs: + using: 'docker' + image: 'Dockerfile' + args: + - 'bzz' + entrypoint: 'main.sh' + post-entrypoint: 'cleanup.sh' +``` + +#### `runs.args` + +**Opcional** Una matriz de secuencias que defina las entradas para un contenedor de Docker. Las entradas pueden incluir cadenas codificadas de forma rígida. {% data variables.product.prodname_dotcom %} comunica los `args` en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor. + +Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia: + +{% data reusables.github-actions.dockerfile-guidelines %} + +Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos. + +Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)". + +##### Ejemplo + +{% raw %} +```yaml +runs: + using: 'docker' + image: 'Dockerfile' + args: + - ${{ inputs.greeting }} + - 'foo' + - 'bar' +``` +{% endraw %} + +### `branding (marca)` + +Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). + +#### Ejemplo + +```yaml +branding: + icon: 'award' + color: 'green' +``` + +#### `branding.color` + +El color de fondo de la insignia. Puede ser: `blanco`, `amarillow`, `azul`, `verde`, `anaranjado`, `rojo`, `púrpura` o `gris oscuro`. + +#### `branding.icon` + +El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    actividadradiodifusiónalerta-círculoalerta-octágono
    alerta-triánguloalinear-centroalinear-justificaralinear-izquierda
    alinear-derechaanclaaperturaarchivo
    flecha-abajo-círculoflecha-abajo-izquierdaflecha-abajo-derechaflecha-abajo
    flecha-izquierda-círculoflecha-izquierdaflecha-derecha-círculoflecha-derecha
    flecha-arriba-círculoflecha-arriba-izquierdaflecha-arriba-derechaflecha-arriba
    en-cartelpremiobarra-cuadro-2barra-cuadro
    batería-cargabateríacampana-apagadocampana
    bluetoothnegritalibro-abiertolibro
    marcadorcajamaletíncalendario
    cámara-apagadocámaramoldeverificar-círculo
    verificar-cuadradoverificarcomilla angular-abajocomilla angular-izquierda
    comillas angulares-derehcacomilla angular- arribacomillas angulares-abajocomillas angulares-izquierda
    comillas angulares-derechacomillas angulares- arribacírculoportapapeles
    relojnube-lloviznanube-rayonube-apagado
    nube-lluvianube-nievenubecódigo
    comandobrújulacopiarángulo-abajo-izquierdo
    ángulo-abajo-derechoángulo-izquierdo-abajoángulo-arriba-izquierdoángulo-derecho-abajo
    ángulo-derecho-arribaángulo-arriba-izquierdoángulo-arriba-derechacpu
    tarjeta-de-créditocortarpunto de mirabase de datos
    eliminardiscodólar-signodescargar-nube
    descargargotaeditar-2editar-3
    editarexterno-enlacedesviar la miradaojo
    facebookavance-rápidoplumaarchivo-menos
    archivo-másarchivo-textoarchivopelícula
    filtrobanderacarpeta-menoscarpeta-más
    carpetaobsequiogit-ramagit-confirmar
    git-fusionargit-solicitud-extracciónglobocuadrícula
    disco-durohashauricularescorazón
    ayuda-círculohogarimagenbandeja de entrada
    infocursivacapasdiseño
    vida-boyaenlace-2enlacelista
    cargadorbloqueariniciar-sesióncerrar-sesión
    correoasignar-pinasignarmaximizar-2
    maximizar +menúmensaje-círculomensaje-cuadrado
    mic-apagadomicminimizar-2minimizar
    menos-círculomenos-cuadradomenosmonitor
    lunamás-horizontalmás-verticalmover
    músicanavegación-2navegaciónoctágono
    paquetesujetapapelespausa-círculopausar
    porcentajellamada-telefónicateléfono-transferenciateléfono-entrante
    teléfono-perdidoteléfono-apagadoteléfono-salidateléfono
    gráfico-circularreproducir-círculoreproducirmás-círculo
    más-cuadradomásbolsillopotencia
    impresoraradioactualizar-ccwactualizar-cw
    repetirrebobinarrotar-ccwrotar-cw
    rssguardartijerasbuscar
    enviarservidorparámetroscompartir-2
    compartirescudo-apagarescudobolsa-de-compras
    carro-de-comprasaleatoriobarra lateralomitir-atrás
    omitir-adelantebarradeslizadoressmartphone
    parlantecuadradoestrelladetener-círculo
    solamaneceratardecertablet
    etiquetadestinoterminaltermómetro
    pulgares-abajopulgares-arribaalternar-izquierdaalternar-derecha
    papelera-2papeleratendencia-abajotendencia-arriba
    triángulocamiónTVtype
    paraguassubrayardesbloquearcargar-nube
    cargarusuario-comprobarusuario-menosusuario-más
    usuario-xusuariousersvideo-apagar
    videocorreo de vozvolumen-1volumen-2
    volumen-xvolumenobservarwifi-apagar
    wifivientox-círculox-cuadrado
    xdestruir-apagadodestruiracercarse
    alejarse
    diff --git a/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md new file mode 100644 index 0000000000000..b91625f2ccb3c --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -0,0 +1,56 @@ +--- +title: Publicar acciones en GitHub Marketplace +intro: 'Puedes publicar acciones en {% data variables.product.prodname_marketplace %} y compartir acciones que has creado con la comunidad de {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /github/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace + - /actions/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace + - /actions/building-actions/publishing-actions-in-github-marketplace +versions: + free-pro-team: '*' +type: 'how_to' +--- + +Debes aceptar los términos de servicio para publicar acciones en {% data variables.product.prodname_marketplace %}. + +### Acerca de la publicación de acciones + +Antes de que puedas publicar una acción, deberás crear una acción en tu repositorio. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)". + +Cuando planeas publicar tu acción en {% data variables.product.prodname_marketplace %}, necesitarás asegurarte de que el repositorio solo incluya el archivo de metadatos, el código y los archivos necesarios para la acción. Crear un repositorio único para la acción te permite etiquetar, lanzar y empaquetar el código en una sola unidad. {% data variables.product.prodname_dotcom %} también usa los metadatos de la acción en tu página de {% data variables.product.prodname_marketplace %}. + +Las acciones se publican en {% data variables.product.prodname_marketplace %} inmediatamente y no son revisadas por {% data variables.product.prodname_dotcom %} siempre que cumplan con estos requisitos: + +- La acción debe estar en un repositorio público. +- Cada repositorio debe contener una única acción. +- El archivo de metadatos de la acción (`action.yml` o `action.yaml`) debe estar en el directorio raíz del repositorio. +- El `Nombre` en el archivo de metadatos de la acción debe ser único. + - El `Nombre` no debe coincidir con el nombre de una acción existente publicada en {% data variables.product.prodname_marketplace %}. + - El `Nombre` no debe coincidir con un usuario u organización en {% data variables.product.prodname_dotcom %}, excepto que el usuario o el propietario de la organización publique la acción. Por ejemplo, solo la organización {% data variables.product.prodname_dotcom %} puede publicar una acción denominada `Github`. + - El `Nombre` no debe coincidir con una categoría existente de {% data variables.product.prodname_marketplace %}. + - {% data variables.product.prodname_dotcom %} reserva los nombres de las funciones de {% data variables.product.prodname_dotcom %}. + +### Publicar una acción + +Puedes agregar la acción que has creado para {% data variables.product.prodname_marketplace %} etiquetándola como un lanzamiento nuevo y publicándola. + +Para preparar un nuevo lanzamiento y publicar la acción en {% data variables.product.prodname_marketplace %}, sigue estas instrucciones: + +{% data reusables.repositories.navigate-to-repo %} +1. Cuando un repositorio contiene un archivo de metadatos de acción (`action.yml` o `action.yaml`), verás un mensaje emergente para publicar la acción en {% data variables.product.prodname_marketplace %}. Haz clic en **Draft a release (Crear el borrador de un lanzamiento)**. ![Publicar esta acción en el botón de Marketplace](/assets/images/help/repository/publish-github-action-to-markeplace-button.png) +1. Selecciona **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}**. Si no puedes seleccionar la casilla de verificación **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}**, deberás leer y aceptar el acuerdo primero {% data variables.product.prodname_marketplace %}. ![Selecciona publicar en Marketplace](/assets/images/help/repository/marketplace_actions_publish.png) +1. Si las etiquetas en tu archivo de metadatos contienen algún problema, verás un mensaje de error. ![Ver notificación](/assets/images/help/repository/marketplace_actions_fixerrors.png) +1. Si ves alguna sugerencia en pantalla, la solucionas actualizando tu archivo de metadatos. Una vez que esté completo, verás un mensaje "Everything looks Good" (Todo se ve bien). ![Corregir errores](/assets/images/help/repository/marketplace_actions_looksgood.png) +1. Elige una "Primary Category" (Categoría principal) y, de manera opcional, "Another Category" (Otra categoría) que ayudará a las personas a encontrar tu acción en {% data variables.product.prodname_marketplace %}. ![Elegir categoría](/assets/images/help/repository/marketplace_actions_categories.png) +1. Etiqueta tu acción con una versión y agrega un título de lanzamiento. Esto permite que las personas conozcan qué cambios o características incluye el lanzamiento. Las personas verán la versión en la página dedicada a la acción de {% data variables.product.prodname_marketplace %}. ![Etiquetar una versión](/assets/images/help/repository/marketplace_actions_version.png) +1. Completa todos los demás campos y haz clic en **Publish release (Publicar versión)**. La publicación requiere que uses la autenticación de dos factores. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication/)". ![Publica el lanzamiento](/assets/images/help/repository/marketplace_actions_publishrelease.png) + +### Eliminar una acción de {% data variables.product.prodname_marketplace %} + +Para eliminar una acción publicada del {% data variables.product.prodname_marketplace %}, necesitarás actualizar cada lanzamiento publicado. Realiza los siguientes pasos para cada lanzamiento de la acción que has publicado en {% data variables.product.prodname_marketplace %}. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. En la página Lanzamientos, a la derecha del lanzamiento que deseas editar, haz clic en **Editar**. ![Botón Editar lanzamiento](/assets/images/help/releases/release-edit-btn.png) +4. Selecciona **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}** para eliminar el tilde de la casilla. ![Botón para publicar esta acción](/assets/images/help/repository/actions-marketplace-unpublish.png) +5. Haz clic en **Update release (Actualizar versión)** en la parte inferior de la página. ![Botón para actualizar el lanzamiento](/assets/images/help/repository/actions-marketplace-update-release.png) diff --git a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md new file mode 100644 index 0000000000000..970913b379554 --- /dev/null +++ b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -0,0 +1,51 @@ +--- +title: Configurar códigos de salida para acciones +shortTitle: Configurar códigos de salida +intro: 'Puedes usar códigos de salida para establecer el estado de una acción. {% data variables.product.prodname_dotcom %} muestra los estados para indicar las acciones que se pasan o fallan.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/building-actions/setting-exit-codes-for-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'how_to' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los códigos de salida + +{% data variables.product.prodname_dotcom %} utiliza el código de salida para configurar el estado de verificación de ejecución de las acciones, el cual puede ser `success` o `failure`. + +| Estado de salida | Estado de ejecución de verificación | Descripción | +| ---------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `0` | `success` | La acción se completó con éxito y pueden comenzar otras tareas que dependen de ella. | +| Valor distinto de cero | `failure` | Cualquier otro código de salida indica que la acción fracasó. Cuando una acción fracasa, todas las acciones simultáneas se cancelan y las acciones futuras se omiten. La ejecución de verificación y el conjunto de verificaciones obtienen un estado `failure`. | + +### Establecer un código de salida fallida en una acción JavaScript + +Si vas a crear una acción JavaScript, puedes usar el paquete del kit de herramientas [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) para registrar un mensaje y establecer un código de salida fallida. Por ejemplo: + +```javascript +try { + // something +} catch (error) { + core.setFailed(error.message); +} +``` + +Para obtener más información, consulta "[Crear una acción JavaScript](/articles/creating-a-javascript-action)". + +### Establecer un código de salida fallida en una acción de contenedor Docker + +Si vas a crear una acción de contenedor Docker, puedes establecer un código de salida fallida en tu script `entrypoint.sh`. Por ejemplo: + +``` +if ; then + echo "Game over!" + exit 1 +fi +``` + +Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)". diff --git a/translations/es-ES/content/actions/guides/about-continuous-integration.md b/translations/es-ES/content/actions/guides/about-continuous-integration.md new file mode 100644 index 0000000000000..133621c5a1fb9 --- /dev/null +++ b/translations/es-ES/content/actions/guides/about-continuous-integration.md @@ -0,0 +1,64 @@ +--- +title: Acerca de la integración continua +intro: 'Puedes crear flujos de trabajo de intgraciones contínuas (IC) personalizadas y despliegues contínuos (DC) directamente en tu repositorio de {% data variables.product.prodname_dotcom %} con las {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/about-continuous-integration + - /github/automating-your-workflow-with-github-actions/about-continuous-integration + - /actions/automating-your-workflow-with-github-actions/about-continuous-integration + - /actions/building-and-testing-code-with-continuous-integration/about-continuous-integration +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de la integración continua + +La integración continua (CI) es una práctica de software que requiere la confirmación de código de forma periódica en un repositorio compartido. La confirmación de código con mayor frecuencia detecta errores más rápido y reduce la cantidad de código que un desarrollador necesita depurar al encontrar la fuente de un error. Las actualizaciones frecuentes de código facilitan también la fusión de cambios de diferentes miembros de un equipo de desarrollo de software. Esto es excelente para los desarrolladores, que pueden dedicar más tiempo a escribir código y menos tiempo a depurar errores o resolver conflictos de fusión. + +Al confirmar el código en tu repositorio, puedes crear y probar el código continuamente para asegurarte de que la confirmación no introduzca errores. Tus pruebas pueden incluir limpiadores de código (que verifican el formato de estilo), verificaciones de seguridad, cobertura de código, pruebas funcionales y otras verificaciones personalizadas. + +Para crear y probar tu código es necesario un servidor. Puedes crear y probar las actualizaciones localmente antes de subir un código a un repositorio o puedes usar un servidor CI que verifique las nuevas confirmaciones de código en un repositorio. + +### Acerca de la integración continua utilizando {% data variables.product.prodname_actions %} + +La IC utilizando {% data variables.product.prodname_actions %} ofrece flujos de trabajo que pueden compilar el código en tu repositorio y ejecutar tus pruebas. Los flujos de trabajo pueden ejecutarse en máquinas virtuales hospedadas en {% data variables.product.prodname_dotcom %}, o en máquinas que hospedes tú mismo. Para obtener más información, consulta las secciones "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" y "[Acerca de los ejecutores auto-hospedados](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)". + +Puedes configurar tu flujo de trabajo de IC para que se ejecute cuando ocurre un evento de {% data variables.product.product_name %} (por ejemplo, cuando se sube código nuevo a tu repositorio), en una programación configurada, o cuando ocurre un evento externo utilizando el webhook de envío del repositorio. + +{% data variables.product.product_name %} ejecuta tus pruebas de IC y proporciona los resultados de cada prueba en la solicitud de extracción para que puedas ver si el cambio en tu rama introduce un error. Cuando se superan todas las pruebas de CI en un flujo de trabajo, los cambios que subiste están listos para su revisión por parte de un miembro del equipo o para su fusión. Cuando una prueba falla, es posible que uno de tus cambios haya causado la falla. + +Cuando configuras la IC en tu repositorio, {% data variables.product.product_name %} analiza el código en el mismo y recomienda flujos de trabajo de IC con base en el lenguaje y marco de trabajo de tu repositorio. Por ejemplo, si utilizas [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} te sugerirá un archivo de plantilla que instala tus paquetes de Node.js y ejecuta tus pruebas. Puedes utilizar la plantilla de flujo de trabajo de IC que {% data variables.product.product_name %} te sugiere, personalizarla, o crear tu propio archivo de flujo de trabajo personalizado para que ejecute tus pruebas de IC. + +![Captura de pantalla de plantillas de integración continua sugeridas](/assets/images/help/repository/ci-with-actions-template-picker.png) + +Adicionalmente a ayudarte a configurar los flujos de trabajo de IC para tu proyecto, puedes utilizar las {% data variables.product.prodname_actions %} para crear flujos de trabajo através de todo el ciclo de vida de desarrollo de software. Por ejemplo, puedes usar acciones para implementar, empaquetar o lanzar tu proyecto. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_actions %}](/articles/about-github-actions)". + +Para obtener una definición de términos comunes, consulta "[Conceptos básicos para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." + +### Lenguajes compatibles + +{% data variables.product.product_name %} ofrece plantillas de flujo de trabajo de IC para varios lenguajes y marcos de trabajo. + +Busca en la lista completa de plantillas de flujo de trabajo para IC que ofrece {% data variables.product.product_name %} en el repositorio [actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) de {% if currentVersion == "free-pro-team@latest" %}{% else %} repositorio `actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}. + +### Notificaciones para ejecuciones de flujo de trabajo + +{% data reusables.repositories.workflow-notifications %} + +### Distintivos de estado para ejecuciones de flujos de trabajo + +{% data reusables.repositories.actions-workflow-status-badge-into %} + +Para obtener más información, consulta "[ Configuración de flujo de trabajo](/articles/configuring-a-workflow)". + +### Further reading + +- "[Configurar la integración continua utilizando {% data variables.product.prodname_actions %}](/articles/setting-up-continuous-integration-using-github-actions)" +{% if currentVersion == "free-pro-team@latest" %} +- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md new file mode 100644 index 0000000000000..fe715f097c811 --- /dev/null +++ b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md @@ -0,0 +1,53 @@ +--- +title: Acerca del empaquetado con acciones de GitHub +intro: 'Puedes configurar flujos de trabajo en {% data variables.product.prodname_actions %} para generar paquetes y cargarlos en {% data variables.product.prodname_registry %} u otro proveedor de alojamiento del paquete.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions + - /actions/publishing-packages-with-github-actions/about-packaging-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los pasos de empaquetado + +Un paso de empaquetado es una parte común de un flujo de trabajo de integración continua o entrega continua. Después de construir y probar tu aplicación, se produce un artefacto ejecutable o desplegable en la forma de un paquete. Por ejemplo, un flujo de trabajo de integración continua para un proyecto Java puede ejecutar `mvn package` para generar un archivo JAR. O un flujo de trabajo de CI para una aplicación Node.js puede crear un contenedor Docker. + +Según el tipo de aplicación que estás construyendo, este paquete se puede descargar de forma local para pruebas manuales, disponible para que los usuarios los descarguen o se implementen en un entorno de ensayo o producción. + +### Empaquetado en flujos de trabajo de integración continua + +Crear un paquete al final de un flujo de trabajo de integración continua puede ayudar durante las revisiones de código en una solicitud de extracción. Después de construir y probar tu código, un paso de empaquetado puede generar un artefacto ejecutable o desplegable. Luego, tu flujo de trabajo puede tomar ese artefacto y cargarlo como parte del flujo de trabajo. + +Ahora, cuando revises una solicitud de extracción, podrás ver la ejecución del flujo de trabajo y descargar el artefacto que se produjo. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} +![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} + +Esto te permitirá ejecutar el código en la solicitud de extracción en tu máquina, lo que puede ayudar con la depuración o la prueba de la solicitud de extracción. + +### Flujos de trabajo para publicar paquetes + +Además de cargar artefactos de empaquetado para las pruebas en un flujo de trabajo de integración continua, puedes crear flujos de trabajo que construyan tu proyecto y publiquen paquetes en un registro de paquete. + +* **Publicar paquetes en el {% data variables.product.prodname_registry %}** + El {% data variables.product.prodname_registry %} puede actuar como un servicio de hospedaje para paquetes para varios tipos de éstos. Puedes elegir compartir tus paquetes con todos los {% data variables.product.prodname_dotcom %}, o paquetes privados para compartir con los colaboradores o una organización. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)". + + Es posible que desees publicar paquetes para el {% data variables.product.prodname_registry %} en cada subida a la rama predeterminada. Esto permitirá que los programadores en tu proyecto siempre puedan ejecutar y probar la última construcción fuera del principal fácilmente, instalándolo desde {% data variables.product.prodname_registry %}. + +* **Publicar paquetes en un registro de paquetes** + Para muchos proyectos, publicar en un registro de paquete se realiza cada vez que se lanza una nueva versión de un proyecto. Por ejemplo, un proyecto que produce un archivo JAR puede cargar nuevos lanzamientos en el repositorio central de Maven. O bien, un proyecto de .NET puede generar un paquete NuGet y cargarlo en la galería de NuGet. + + Puedes automatizar esto creando un flujo de trabajo que publique paquetes en un registro de paquetes en cada creación de lanzamiento. Para obtener más información, consulta "[Crear lanzamientos](/github/administering-a-repository/creating-releases)." + +### Further reading + +- "[Publicar paquetes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)" diff --git a/translations/es-ES/content/actions/guides/about-service-containers.md b/translations/es-ES/content/actions/guides/about-service-containers.md new file mode 100644 index 0000000000000..2d7a39ad2b7ab --- /dev/null +++ b/translations/es-ES/content/actions/guides/about-service-containers.md @@ -0,0 +1,116 @@ +--- +title: Acerca de los contenedores de servicios +intro: 'Puedes usar los contenedores de servicios para conectar las bases de datos, los servicios Web, las memorias caché y otras herramientas a tu flujo de trabajo.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/about-Service-containers + - /actions/configuring-and-managing-workflows/about-service-containers +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los contenedores de servicios + +Los contenedores de servicios son contenedores de Docker que ofrecen una manera sencilla y portátil de alojar servicios que probablemente necesites para probar o usar tu aplicación en un flujo de trabajo. Por ejemplo, es posible que tu flujo de trabajo tenga que ejecutar pruebas de integración que requieran acceso a una base de datos y a una memoria caché. + +Puedes configurar contenedores de servicios para cada trabajo en un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea un contenedor de Docker nuevo para cada servicio configurado en el flujo de trabajo y destruye el contenedor de servicios cuando se termina el trabajo. Los pasos de un trabajo pueden comunicarse con todos los contenedores de servicios que son parte del mismo trabajo. + +{% data reusables.github-actions.docker-container-os-support %} + +### Comunicarse con contenedores de servicios + +Puedes configurar trabajos en un flujo de trabajo para que se ejecuten directamente en una máquina del ejecutor o en un contenedor de Docker. La comunicación entre un trabajo y sus contenedores de servicios cambia en función de si un trabajo se ejecuta directamente en la máquina del ejecutor o en un contenedor. + +#### Ejecutar trabajos en un contenedor + +Cuando ejecutas trabajos en un contenedor, {% data variables.product.prodname_dotcom %} conecta los contenedores de servicios al trabajo mediante las redes de puente definidas por el usuario de Docker. Para obtener más información, consulta "[Usar redes de puente](https://docs.docker.com/network/bridge/)" en la documentación de Docker. + +Al ejecutar el trabajo y los servicios en un contenedor, se simplifica el acceso a la red. Puedes acceder a un contenedor de servicios usando la etiqueta que configuraste en el flujo de trabajo. El nombre del host del contenedor de servicios se correlaciona automáticamente con el nombre de la etiqueta. Por ejemplo, si creas un contenedor de servicios con la etiqueta `redis`, el nombre del host del contenedor de servicio será `redis`. + +No es necesario configurar ningún puerto para los contenedores de servicios. Por defecto, todos los contenedores que forman parte de la misma red de Docker se exponen los puertos entre sí, y no se exponen puertos por fuera de la red de Docker. + +#### Ejecutar trabajos en la máquina del ejecutor + +Cuando ejecutas trabajos directamente en la máquina del ejecutor, puedes acceder a los contenedores de servicios usando `localhost:` o `127.0.0.1`. {% data variables.product.prodname_dotcom %} configura la red de contenedores para habilitar la comunicación desde el contenedor de servicios hasta el host de Docker. + +Cuando un trabajo se ejecuta directamente en una máquina del ejecutor, el servicio que se ejecuta en el contenedor de Docker no expone sus puertos al trabajo del ejecutor por defecto. Debes asignar los puertos del contenedor de servicios al host de Docker. Para obtener más información, consulta "[Asignar puertos del host de Docker y del contenedor de servicios](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". + +### Crear contenedores de servicios + +Puedes usar la palabra clave `services` para crear contenedores de servicios que sean parte de un trabajo en tu flujo de trabajo. Para obtener más información, consulta [`jobs..services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices). + +Este ejemplo crea un servicio llamado `redis` en un trabajo llamado `container-job`. El host de Docker en este ejemplo es el contenedor `node: 10.18-jessie`. + +{% raw %} +```yaml +name: Redis container example +on: push + +jobs: + # Etiqueta del trabajo del contenedor + container-job: + # Los contenedores deben ejecutarse en sistemas operativos basados en Linux + runs-on: ubuntu-latest + # Imagen de Docker Hub que 'container-job' ejecuta en + el contendor: node:10.18-jessie + + # Contenedores de servicios para ejecutar con servicios de 'container-job': + # Etiqueta usada para acceder al contenedor de servicios + redis: + # Imagen de Docker Hub + image: redis +``` +{% endraw %} + +### Asignar puertos del host de Docker y del contenedor de servicios + +Si tu trabajo se ejecuta en un contenedor de Docker, no necesitas asignar puertos en el host o en el contenedor de servicios. Si tu trabajo se ejecuta directamente en la máquina del ejecutor, tendrás que asignar cualquier puerto requerido del contenedor de servicios a los puertos de la máquina del ejecutor del host. + +Puedes asignar puertos de contenedores de servicios al host de Docker utilizando la palabra clave `ports`. Para obtener más información, consulta [`jobs..services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices). + +| Valor de `ports` | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------- | +| `8080:80` | Asigna el puerto TCP 80 del contenedor al puerto 8080 del host de Docker. | +| `8080:80/UDP` | Asigna el puerto UDP 80 del contenedor al puerto 8080 del host de Docker. | +| `8080/UDP` | Asigna un puerto UDP elegido aleatoriamente del contenedor al puerto UDP 8080 del host de Docker. | + +Cuando asignas puertos utilizando la palabra clave `ports`, {% data variables.product.prodname_dotcom %} utiliza el comando `--publish` para publicar los puertos del contenedor en el host de Docker. Para obtener más información, consulta "[Redes de contenedores de Docker](https://docs.docker.com/config/containers/container-networking/)"en la documentación de Docker. + +Cuando especificas el puerto del host de Docker pero no el puerto del contenedor, el puerto del contenedor se asigna aleatoriamente a un puerto gratuito. {% data variables.product.prodname_dotcom %} establece el puerto del contenedor asignado en el contexto del contenedor de servicios. Por ejemplo, para un contenedor de servicios `redis`, si configuraste el puerto del host de Docker 5432, puedes acceder al puerto del contenedor correspondiente utilizando el contexto `job.services.redis.ports[5432]`. Para obtener más información, consulta "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-context)". + +#### Ejemplo de asignación de puertos Redis + +Este ejemplo asigna el puerto 6379 del contenedor de servicios `redis` al puerto 6379 del host de Docker. + +{% raw %} +```yaml +name: Redis Service Example +on: push + +Jobs: + # Etiqueta del trabajo del contenedor + runner-job: + # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor + runs-on: ubuntu-latest + + # Contenedores de servicios para ejecutar con servicios de 'runner-job': + # Etiqueta usada para acceder al contenedor de servicios + redis: + # Imagen de Docker Hub + image: redis + # + puertos: + # Abre el puerto tcp 6379 en el host y el contenedor de servicios + -6379:6379 +``` +{% endraw %} + +### Further reading + +- "[Crear contenedores de servicios Redis](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)" +- "[Crear contenedores de servicios PostgreSQL](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)" diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md new file mode 100644 index 0000000000000..f73b47f9ae300 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md @@ -0,0 +1,110 @@ +--- +title: Construir y probar Java con Ant +intro: Puedes crear un flujo de trabajo de integración continua (CI) en Acciones de GitHub para construir y probar tu proyecto Java con Ant. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/building-and-testing-java-with-ant +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo que realiza integración continua (CI) para tu proyecto de Java por medio del sistema de construcción Ant. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes ampliar tu flujo de trabajo de CI para cargar artefactos desde una ejecución de flujo de trabajo. + +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado, que incluye Java Development Kits (JDK) y Ant. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Ant, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Prerrequisitos + +Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta: +- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)" +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" + +Recomendamos que tengas un conocimiento básico de Java y de la estructura de Ant. Para obtener más información, consulta el [Manual de Apache Ant](https://ant.apache.org/manual/). + +{% data reusables.actions.enterprise-setup-prereq %} + +### Comenzar con una plantilla de flujo de trabajo de Ant + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Ant que funcionará para la mayoría de los proyectos de Java basados en Ant. Para obtener más información, consulta la [Plantilla de flujo de trabajo de Ant](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml). + +Para comenzar rápidamente, puedes elegir la plantilla de Ant preconfigurada cuando crees un nuevo flujo de trabajo. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)". + +También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. + +{% raw %} +```yaml +name: Java CI + +on: [push] + +jobs: + build: + runs-on: ubuntu-latest + + 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 %} + +Este flujo de trabajo realiza los siguientes pasos: + +1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor. +2. El paso `setup-java` configura el JDK de Java 1.8. +3. El paso "Build with Ant" (Construir con Ant) ejecuta el objetivo predeterminado en tu `build.xml` en el modo no interactivo. + +Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto. + +{% data reusables.github-actions.example-github-runner %} + +{% data reusables.github-actions.java-jvm-architecture %} + +### Construir y probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. + +El flujo de trabajo de inicio ejecutará el destino predeterminado especificado en tu archivo _build.xml_. Normalmente, tu objetivo predeterminado se configurará para crear clases, ejecutar pruebas y empaquetar clases en su formato distribuible, por ejemplo, un archivo JAR. + +Si usas diferentes comandos para construir tu proyecto, o si deseas ejecutar un objetivo diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el destino `jar` que está configurado en tu archivo _build-ci.xml_. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Run the Ant jar target + run: ant -noinput -buildfile build-ci.xml jar +``` +{% endraw %} + +### Empaquetar datos de flujo de trabajo como artefactos + +Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +Por lo general, Ant crea archivos de salida como JAR, EAR o WAR en el directorio `build/jar`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + - run: ant -noinput -buildfile build.xml + - uses: actions/upload-artifact@v2 + with: + name: Package + path: build/jar +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md new file mode 100644 index 0000000000000..c7701d50eb942 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md @@ -0,0 +1,135 @@ +--- +title: Construir y probar Java con Gradle +intro: Puedes crear un flujo de trabajo de integración continua (CI) en acciones de GitHub para construir y probar tu proyecto Java con Gradle. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/building-and-testing-java-with-gradle +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de trabajo de CI para almacenar en caché los archivos y cargar artefactos desde una ejecución de flujo de trabajo. + +Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con software preinstalado, que incluye kits de desarrollo de Java (JDK) y Gradle. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Gradle, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Prerrequisitos + +Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta: +- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)" +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" + +Te recomendamos que tengas una comprensión básica de Java y del marco de Gradle. Para obtener más información, consulta [Empezar](https://docs.gradle.org/current/userguide/getting_started.html) en la documentación de Gradle. + +{% data reusables.actions.enterprise-setup-prereq %} + +### Comenzar con una plantilla de flujo de trabajo de Gradle + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Gradle que funcionará para la mayoría de los proyectos Java basados en Gradle. Para obtener más información, consulta la [Plantilla de flujo de trabajo de Gradle](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml). + +Para comenzar rápidamente, puedes elegir la plantilla de Gradle preconfigurada cuando creas un nuevo flujo de trabajo. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)". + +También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. + +{% raw %} +```yaml +name: Java CI + +on: [push] + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Build with Gradle + run: ./gradlew build +``` +{% endraw %} + +Este flujo de trabajo realiza los siguientes pasos: + +1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor. +2. El paso `setup-java` configura el JDK de Java 1.8. +3. El paso "Build with Gradle" (construir con Gradle) ejecuta el script contenedor `gradlew` para asegurar que tu código se cree, las pruebas pasen y se pueda crear un paquete. + +Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto. + +{% data reusables.github-actions.example-github-runner %} + +{% data reusables.github-actions.java-jvm-architecture %} + +### Construir y probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. + +El flujo de trabajo de inicio ejecutará la tarea `build` por defecto. En la configuración de Gradle predeterminada, este comando descargará las dependencias, construirá clases, ejecutará pruebas y empaquetará las clases en su formato distribuible, por ejemplo, un archivo JAR. + +Si usas diferentes comandos para construir tu proyecto, o si quieres usar una tarea diferente, puedes especificarlo. Por ejemplo, es posible que desees ejecutar la tarea `package` que está configurada en tu archivo _ci.gradle_. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Run the Gradle package task + run: ./gradlew -b ci.gradle package +``` +{% endraw %} + +### Almacenar dependencias en caché + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu caché de paquete de Gradle local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, la caché se restaurará para que las dependencias no necesiten ser descargadas desde los repositorios de paquetes remotos. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Cache Gradle packages + uses: actions/cache@v2 + with: + path: ~/.gradle/caches + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} + restore-keys: ${{ runner.os }}-gradle + - name: Build with Gradle + run: ./gradlew build +``` +{% endraw %} + +Este flujo de trabajo guardará los contenidos de tu caché de paquete Gradle local, que se encuentra en el directorio `.gradle/caches` del directorio de inicio del ejecutor. La clave de caché será el contenido con hash de los archivos de construcción de Gradle, por lo que los cambios en ellos invalidarán la memoria caché. + +### Empaquetar datos de flujo de trabajo como artefactos + +Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +Por lo general, Gradle creará archivos de salida como JAR, EAR o WAR en el directorio `build/libs`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + - run: ./gradlew build + - uses: actions/upload-artifact@v2 + with: + name: Package + path: build/libs +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md new file mode 100644 index 0000000000000..daf23c710a082 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md @@ -0,0 +1,136 @@ +--- +title: Construir y probar Java con Maven +intro: Puedes crear un flujo de trabajo de integración continua (CI) en acciones de GitHub para construir y probar tu proyecto Java con Maven. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/building-and-testing-java-with-maven +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de trabajo de CI para almacenar en caché los archivos y cargar artefactos desde una ejecución de flujo de trabajo. + +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con un software preinstalado, que incluye kits de desarrollo de Java (JDK) y Maven. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Maven, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Prerrequisitos + +Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta: +- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)" +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" + +Te recomendamos que tengas una comprensión básica de Java y del marco de Maven. Para obtener más información, consulta el [Guía de introducción a Maven](http://maven.apache.org/guides/getting-started/index.html) en la documentación de Maven. + +{% data reusables.actions.enterprise-setup-prereq %} + +### Comenzar con una plantilla de flujo de trabajo de Maven + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Maven que funcionará para la mayoría de los proyectos Java basados en Maven. Para obtener más información, consulta la sección [Plantilla de flujo de trabajo de Maven](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml). + +Para comenzar rápidamente, puedes elegir la plantilla Maven preconfigurada cuando creas un nuevo flujo de trabajo. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)". + +También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. + +{% raw %} +```yaml +name: Java CI + +on: [push] + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Build with Maven + run: mvn --batch-mode --update-snapshots verify +``` +{% endraw %} + +Este flujo de trabajo realiza los siguientes pasos: + +1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor. +2. El paso `setup-java` configura el JDK de Java 1.8. +3. El paso "Build with Maven" (Construir con Maven) ejecuta el `paquete` destino de Maven en modo no interactivo para garantizar que tu código se compile, se superen las pruebas y se pueda crear un paquete. + +Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto. + +{% data reusables.github-actions.example-github-runner %} + +{% data reusables.github-actions.java-jvm-architecture %} + +### Construir y probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. + +El flujo de trabajo de inicio ejecutará el `paquete` destino por defecto. En la configuración predeterminada de Maven, este comando descargará dependencias, construirá clases, ejecutar pruebas y las clases de paquetes en su formato distribuible, por ejemplo, un archivo JAR. + +Si usas diferentes comandos para compilar tu proyecto, o si quieres usar un destino diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el objetivo `verify (verificar)` que está configurado en un archivo _pom-ci.xml_. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Run the Maven verify phase + run: mvn --batch-mode --update-snapshots verify +``` +{% endraw %} + +### Almacenar dependencias en caché + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu repositorio Maven local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, el caché se restaurará para que las dependencias no necesiten descargarse desde los repositorios remotos de Maven. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - name: Set up JDK 1.8 + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Cache Maven packages + uses: actions/cache@v2 + with: + path: ~/.m2 + key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} + restore-keys: ${{ runner.os }}-m2 + - name: Build with Maven + run: mvn --batch-mode --update-snapshots verify +``` +{% endraw %} + +Este flujo de trabajo guardará los contenidos de tu repositorio local de Maven, ubicado en el directorio `.m2` del directorio de inicio del ejecutor. La clave de caché será el contenido con hash de _pom.xml_, por lo que los cambios en _pom.xml_ invalidará el caché. + +### Empaquetar datos de flujo de trabajo como artefactos + +Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +Por lo general, Maven creará archivos de salida como tarros, orejas o guerras en el `Objetivo` Directorio. Para cargarlos como artefactos, puedes copiarlos en un nuevo directorio que contenga artefactos para cargar. Por ejemplo, puedes crear un directorio llamado `staging` (preparación). Luego puedes cargar los contenidos de ese directorio usando la acción `upload-artifact (cargar artefacto)`. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + - run: mvn --batch-mode --update-snapshots verify + - run: mkdir staging && cp target/*.jar staging + - uses: actions/upload-artifact@v2 + with: + name: Package + path: staging +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-net.md b/translations/es-ES/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..fd1643426e9f0 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Compilar y probar desarrollos en .NET +intro: Puedes crear un flujo de trabajo de integración continua (IC) para compilar y probar tu proyecto de .NET. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introducción + +Esta guía te muestra cómo construir, probar y publicar un paquete de .NET. + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado, el cual incluye .NET Core SDK. Para encontrar una lista completa de software actualizado y las versiones preinstaladas de .NET Core SDK, consulta la sección de [software instalado en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners). + +### Prerrequisitos + +Ya debes estar familiarizado con la sintaxis de YAML y con cómo se utiliza con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". + +Te recomendamos que tengas un entendimiento básico de .NET Core SDK. Para obtener más información, consulta la sección [Iniciar con .NET](https://dotnet.microsoft.com/learn). + +### Iniciar con la plantilla de flujo de trabajo de .NET + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de .NET que debería funcionar para la mayoría de los proyectos de .NET, y esta guía incluye ejemplos que te muestran cómo personalizar esta plantilla. Para obtener más información, consulta la [plantilla de flujo de trabajo de.NET](https://github.com/actions/setup-dotnet). + +Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Especificar una versión de .NET + +Para utilizar una versión preinstalada de .NET Core SDK en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}, utiliza la acción `setup-dotnet`. Esta acción encuentra una versión específica de .NET desde el caché de las herramientas en cada ejecutor y agrega los binarios necesarios a `PATH`. Estos cambios persistirán para el recordatorio del job. + +La acción `setup-dotnet` es la forma recomendada de utilizar .NET con las {% data variables.product.prodname_actions %}, porque garantiza el comportamiento consistente a través de diversos ejecutores y diversas versiones de .NET. Si estás utilizando un ejecutor auto-hospedado, debes instalar .NET y agregarlo a `PATH`. Para obtener más información, consulta la acción [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Utilizar versiones múltiples de .NET + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Utilizar una versión específica de .NET + +Puedes configurar tu job para que utilice una versión específica de .NET, tal como la `3.1.3`. Como alternativa, puedes utilizar una sintaxis de versión semántica para obtener el último lanzamiento menor. Este ejemplo utiliza el lanzamiento menor más reciente de .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### Instalar dependencias + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} cuentan con el administrador de paquetes NuGet ya instalado. Puedes utilizar el CLI de dotnet para instalar dependencias desde el registro de paquetes de NuGet antes de compilar y probar tu código. Por ejemplo, el siguiente YAML instala el paquete `Newtonsoft`. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Almacenar dependencias en caché + +Puedes guardar dependencias de NuGet en el caché utilizando una clave única, lo cual te permite restablecer las dependencias de los flujos de trabajo futures con la acción [`cache`](https://github.com/marketplace/actions/cache). Por ejemplo, el siguiente YAML instala el paquete `Newtonsoft`. + +Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/guides/caching-dependencies-to-speed-up-workflows)". + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**Nota:** Dependiendo de la cantidad de dependencias, puede ser más rápido usar la caché de dependencias. Los proyectos con muchas dependencias de gran tamaño deberían ver un aumento del rendimiento, ya que reduce el tiempo necesario para la descarga. Los proyectos con menos dependencias podrían no ver un incremento significativo del rendimiento e incluso podrían ver un ligero decremento, debido a cómo NuGet instala las dependencias almacenadas en el caché. El rendimiento varía de un proyecto a otro. + +{% endnote %} + +{% endif %} + +### Construir y probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. Este ejemplo demuestra cómo utilizar `dotnet build` y `dotnet test` en un job: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### Empaquetar datos de flujo de trabajo como artefactos + +Después de que se completa un flujo de trabajo, puedes cargar los artefactos que se den como resultado para su análisis. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. El siguiente ejemplo demuestra cómo puedes utilizar la acción `upload-artifact` para cargar los resultados de las pruebas. + +Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### Publicar en registros de paquetes + +Puedes configurar tu flujo de trabajo para publicar tu paquete de Dotnet a un registro de paquetes cuando pasen tus pruebas de IC. Puedes utilizar secretos de los repositorios para almacenar cualquier token o credenciales que se necesiten para publicar tu binario. El siguiente ejemplo crea y publica un paquete en el {% data variables.product.prodname_registry %} utilizando `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md new file mode 100644 index 0000000000000..4019bd6bf6b2c --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md @@ -0,0 +1,277 @@ +--- +title: Crear y probar en Node.js +intro: Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu proyecto Node.js. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions + - /actions/language-and-framework-guides/using-nodejs-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo de integración continua (CI) que construye y prueba código Node.js. Si tus pruebas de CI se superan, es posible que desees implementar tu código o publicar un paquete. + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de Node.js, YAML, las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta: + +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" +- "[Iniciar con Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)" + +{% data reusables.actions.enterprise-setup-prereq %} + +### Comenzar con una plantilla de flujo de trabajo de Node.js + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Node.js que funcionará para la mayoría de los proyectos Node.js. Esta guía incluye ejemplos de npm y Yarn que puedes usar para personalizar la plantilla. Para obtener más información, consulta la [Plantilla de flujo de trabajo Node.js](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml). + +Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. + +{% raw %} +```yaml{:copy} +name: Node.js CI + +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + +jobs: + build: + + runs-on: ubuntu-latest + + strategy: + matrix: + node-version: [10.x, 12.x, 14.x, 15.x] + + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - run: npm ci + - run: npm run build --if-present + - run: npm test +``` +{% endraw %} + +{% data reusables.github-actions.example-github-runner %} + +### Especificar la versión de Node.js + +La forma más fácil de especificar una versión de Node.js es por medio de la acción `setup-node` proporcionada por {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta [`setup-node`](https://github.com/actions/setup-node/). + +La acción `setup-node` toma una versión de Node.js como una entrada y configura esa versión en el ejecutor. La acción `setup-node` encuentra una versión específica de Node.js de la caché de herramientas en cada ejecutor y añade los binarios necesarios a `PATH`, que continúan para el resto del trabajo. Usar la acción `setup-node` es la forma recomendada de usar Node.js con {% data variables.product.prodname_actions %} porque asegura un comportamiento consistente a través de diferentes ejecutores y diferentes versiones de Node.js. Si estás usando un ejecutor autoalojado, debes instalar Node.js y añadirlo a `PATH`. + +La plantilla incluye una estrategia de matriz que crea y prueba tu código con cuatro versiones de Node.js: 10.x, 12.x, 14.x, y 15.x. La 'x' es un carácter comodín que coincide con el último lanzamiento menor y de parche disponible para una versión. Cada versión de Node.js especificada en la matriz `node-version` crea un trabajo que ejecuta los mismos pasos. + +Cada trabajo puede acceder al valor definido en la matriz `node-version` por medio del contexto `matrix`. La acción `setup-node` utiliza el contexto como la entrada `node-version`. La acción `setup-node` configura cada trabajo con una versión diferente de Node.js antes de construir y probar código. Para obtener más información acerca de las estrategias y los contextos de la matriz, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}"](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) y "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +{% raw %} +```yaml +strategy: + matrix: + node-version: [10.x, 12.x, 14.x, 15.x] + +steps: +- uses: actions/checkout@v2 +- name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} +``` +{% endraw %} + +Como alternativa, puedes construir y probar con las versiones exactas de Node.js. + +```yaml +strategy: + matrix: + node-version: [8.16.2, 10.17.0] +``` + +O bien, puedes construir y probar mediante una versión única de Node.js. + +{% raw %} +```yaml +name: Node.js CI + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' + - run: npm ci + - run: npm run build --if-present + - run: npm test +``` +{% endraw %} + +Si no especificas una versión de Node.js, {% data variables.product.prodname_dotcom %} utiliza la versión de Node.js por defecto del entorno. Para obtener más información, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Instalar dependencias + +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen instalados administradores de dependencias de npm y Yarn. Puedes usar npm y Yarn para instalar dependencias en tu flujo de trabajo antes de construir y probar tu código. Los ejecutores Windows y Linux alojados en {% data variables.product.prodname_dotcom %} también tienen instalado Grunt, Gulp y Bower. + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +#### Ejemplo con npm + +Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar npm`](https://docs.npmjs.com/cli/install). + +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- name: Install dependencies + run: npm install +``` + +Mediante `npm ci` se instalan las versiones en el archivo *package-lock.json* o *npm-shrinkwrap.json* y se evitan las actualizaciones al archivo de bloqueo. Usar `npm ci` generalmente es más rápido que ejecutar `npm install`. Para obtener más información, consulta [`npm ci`](https://docs.npmjs.com/cli/ci.html) e [Introducir `npm ci` para construcciones más rápidas y confiables](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)." + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- name: Install dependencies + run: npm ci +``` +{% endraw %} + +#### Ejemplo con Yarn + +Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar yarn`](https://yarnpkg.com/en/docs/cli/install). + +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- name: Install dependencies + run: yarn +``` + +De forma alternativa, puede pasar `--frozen-lockfile` para instalar las versiones en el archivo *yarn.lock* y evitar actualizaciones al archivo *yarn.lock*. + +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- name: Install dependencies + run: yarn --frozen-lockfile +``` + +#### Ejemplo de uso de un registro privado y la creación del archivo .npmrc + +{% data reusables.github-actions.setup-node-intro %} + +Para autenticar tu registro privado, necesitarás almacenar tu token de autenticación de npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +En el siguiente ejemplo, el secreto `NPM_TOKEN` almacena el token de autenticación npm. La acción `setup-node` configura el archivo *.npmrc* para leer el token de autenticación npm desde la variable de entorno `NODE_AUTH_TOKEN`. Cuando utilices la acción `setup-node` para crear un archivo *.npmrc*, debes configurar la variable de ambiente `NODE_AUTH_TOKEN` con el secreto que contiene tu token de autenticación de npm. + +Antes de instalar dependencias, utiliza la acción `setup-node` para crear el archivo *.npmrc*. La acción tiene dos parámetros de entrada. El parámetro `node-version` establece la versión de Node.js y el parámetro `registry-url` establece el registro predeterminado. Si tu registro de paquetes usa ámbitos, debes usar el parámetro `scope`. Para obtener más información, consulta [`npm-scope`](https://docs.npmjs.com/misc/scope). + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + always-auth: true + node-version: '12.x' + registry-url: https://registry.npmjs.org + scope: '@octocat' +- name: Install dependencies + run: npm ci + env: + NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}} +``` +{% endraw %} + +El ejemplo anterior crea un archivo *.npmrc* con el siguiente contenido: + +``` +//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} +@octocat:registry=https://registry.npmjs.org/ +always-auth=true +``` + +#### Ejemplo de dependencias en caché + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar las dependencias en el caché utilizando una clave única y restaurar las dependencias cuando ejecutes flujos de trabajo subsecuentes, utilizando la acción `cache`. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- name: Cache Node.js modules + uses: actions/cache@v2 + with: + # npm cache files are stored in `~/.npm` on Linux/macOS + path: ~/.npm + key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }} + restore-keys: | + ${{ runner.OS }}-node- + ${{ runner.OS }}- +- name: Install dependencies + run: npm ci +``` +{% endraw %} + +### Construir y probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. Por ejemplo, si ejecutas `npm run build` para ejecutar pasos de construcción definidos en tu archivo *package.json* y `npm test` para ejecutar tu conjunto de pruebas, añadirías esos comandos en tu archivo de flujo de trabajo. + +```yaml +steps: +- uses: actions/checkout@v2 +- name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' +- run: npm install +- run: npm run build --if-present +- run: npm test +``` + +### Empaquetar datos de flujo de trabajo como artefactos + +Puedes guardar los artefactos de tus pasos de construcción y prueba para verlos después de que se complete un trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +### Publicar en registros de paquetes + +Puedes configurar tu flujo de trabajo para que publique tu paquete Node.js en un registro de paquete después de que se aprueben tus pruebas de CI. Para obtener más información acerca de la publicación a npm y {% data variables.product.prodname_registry %}, consulta [Publicar paquetes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)." diff --git a/translations/es-ES/content/actions/guides/building-and-testing-powershell.md b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md new file mode 100644 index 0000000000000..72691f5028033 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md @@ -0,0 +1,243 @@ +--- +title: Compilar y probar PowerShell +intro: Puedes crear un flujo de trabajo de integración continua (IC) para compilar y probar tu proyecto de PowerShell. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +authors: + - potatoqualitee +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo utilizar PowerShell para la IC. Describimos cómo utilizar Pester, instalar dependencias, probar tu módulo y publicarlo en la galería de PowerShell. + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software pre-instalado, lo cual incluye a PowerShell y a Pester. Para encontrar una lista completa de software actualizdo y las versiones pre-instaladas de PowerShell y de Pester, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Prerrequisitos + +Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Te recomendamos tener un entendimiento básico de PowerShell y de Pester. Para obtener más información, consulta: +- [Iniciar con PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) +- [Pester](https://pester.dev) + +{% data reusables.actions.enterprise-setup-prereq %} + +### Agregar un flujo de trabajo para Pester + +Para automatizar tus pruebas con PowerShell y con Pester, puedes agregar un flujo de trabajo que se ejecute cada que se sube un cambio en tu repositorio. En el siguiente ejemplo, se utiliza `Test-Path` para verificar la presencia de un archivo que se llama `resultsfile.log`. + +Este ejemplo de archivo de flujo de trabajo debe agregarse al directorio `.github/workflows/` de tu repositorio: + +{% raw %} +```yaml +name: Test PowerShell on Ubuntu +on: push + +jobs: + pester-test: + name: Pester test + runs-on: ubuntu-latest + steps: + - name: Check out repository code + uses: actions/checkout@v2 + - name: Perform a Pester test from the command-line + shell: pwsh + run: Test-Path resultsfile.log | Should -Be $true + - name: Perform a Pester test from the Tests.ps1 file + shell: pwsh + run: | + Invoke-Pester Unit.Tests.ps1 -Passthru +``` +{% endraw %} + +* `shell: pwsh` - Configura el job para que utilice PowerShell cuando ejecutas los comandos de `run`. +* `run: Test-Path resultsfile.log` - Revisa si un archivo que se llama `resultsfile.log` está presente en el directorio raíz del repositorio. +* `Should -Be $true` - Utiliza Pester para definir un resultado esperado. Si el resultado es inesperado, entonces {% data variables.product.prodname_actions %} lo marca como una prueba fallida. Por ejemplo: + + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Prueba fallida de Pester](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} + ![Prueba fallida de Pester](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} + +* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Utiliza Pester para ejecutar las pruebas que se definen en un archivo que se llama `Unit.Tests.ps1`. Por ejempo, para realizar la misma prueba que se describe anteriormente, el `Unit.Tests.ps1` contendrá lo siguiente: + ``` + Describe "Check results file is present" { + It "Check results file is present" { + Test-Path resultsfile.log | Should -Be $true + } + } + ``` + +### Ubicaciones de los módulos de PowerShell + +En la siguiente tabla se describen las ubicaciones para varios módulos de PowerShell en cada ejecutor hospedado en {% data variables.product.prodname_dotcom %}. + +| | Ubuntu | macOS | Windows | +| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ | +| **Módulos de sistema de PowerShell** | `/opt/microsoft/powershell/7/Modules/*` | `/usr/local/microsoft/powershell/7/Modules/*` | `C:\program files\powershell\7\Modules\*` | +| **Módulos complementarios de PowerShell** | `/usr/local/share/powershell/Modules/*` | `/usr/local/share/powershell/Modules/*` | `C:\Modules\*` | +| **Módulos instalados por el usuario** | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` | + +### Instalar dependencias + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen PowerShell 7 y Pester instalados. Puedes utilizar `Install-Module` para instalar dependencias adicionales de la galería de PowerShell antes de compilar y probar tu código. + +{% note %} + +**Note:** Los paquetes pre-instalados (tales como Pester) que utilizan los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se actualizan frecuentemente y pueden introducir cambios significativos. Como resultado, se recomienda que siempre especifiques las versiones de los paquetes requeridos utilizando `Install-Module` con `-MaximumVersion`. + +{% endnote %} + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +Por ejemplo, el siguiente job instala los módulos de `SqlServer` y `PSScriptAnalyzer`: + +{% raw %} +```yaml +jobs: + install-dependencies: + name: Install dependencies + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Install from PSGallery + shell: pwsh + run: | + Set-PSRepository PSGallery -InstallationPolicy Trusted + Install-Module SqlServer, PSScriptAnalyzer +``` +{% endraw %} + +{% note %} + +**Note:** Predeterminadamente, PowerShell no confía en ningún repositorio. Cuando instales módulos desde la galería de PowerShell, debes configurar explícitamente la política de instalación de `PSGallery` en `Trusted`. + +{% endnote %} + +#### Almacenar dependencias en caché + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar dependencias de PowerShell en el caché utilizando una clave única, lo cual te permite restaurar las dependencias para flujos de trabajo futuros con la acción [`cache`](https://github.com/marketplace/actions/cache). Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +PowerShell guarda sus dependencias en caché en ubicaciones diferentes, dependiendo del sistema operativo del ejecutor. Por ejemplo, el `path` de la ubicación que se utiliza en el siguiente ejemplo de Ubuntu será diferente a aquél de un sistema operativo Windows. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - name: Setup PowerShell module cache + id: cacher + uses: actions/cache@v2 + with: + path: "~/.local/share/powershell/Modules" + key: ${{ runner.os }}-SqlServer-PSScriptAnalyzer + - name: Install required PowerShell modules + if: steps.cacher.outputs.cache-hit != 'true' + shell: pwsh + run: | + Set-PSRepository PSGallery -InstallationPolicy Trusted + Install-Module SqlServer, PSScriptAnalyzer -ErrorAction Stop +``` +{% endraw %} + +### Probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. + +#### Utilizar PSScriptAnalyzer para limpiar el código + +El siguiente ejemplo instala `PSScriptAnalyzer` y lo utiliza para limpiar todos los archivos `ps1` en el repositorio. Para obtener más información, consulta [PSScriptAnalyzer en GitHub](https://github.com/PowerShell/PSScriptAnalyzer). + +{% raw %} +```yaml + lint-with-PSScriptAnalyzer: + name: Install and run PSScriptAnalyzer + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Install PSScriptAnalyzer module + shell: pwsh + run: | + Set-PSRepository PSGallery -InstallationPolicy Trusted + Install-Module PSScriptAnalyzer -ErrorAction Stop + - name: Lint with PSScriptAnalyzer + shell: pwsh + run: | + Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues + $errors = $issues.Where({$_.Severity -eq 'Error'}) + $warnings = $issues.Where({$_.Severity -eq 'Warning'}) + if ($errors) { + Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop + } else { + Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total." + } +``` +{% endraw %} + +### Empaquetar datos de flujo de trabajo como artefactos + +Puedes cargar artefactos para ver después de que se complete un flujo de trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". + +El siguiente ejemplo ilustra cómo puedes utilizar la acción `upload-artifact` para archivar los resultados de las pruebas que se recibieron de `Invoke-Pester`. Para obtener más información, consulta la acción [`upload-artifact`](https://github.com/actions/upload-artifact). + +{% raw %} +```yaml +name: Upload artifact from Ubuntu + +on: [push] + +jobs: + upload-pester-results: + name: Run Pester and upload results + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Test with Pester + shell: pwsh + run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml + - name: Upload test results + uses: actions/upload-artifact@v2 + with: + name: ubuntu-Unit-Tests + path: Unit.Tests.xml + if: ${{ always() }} +``` +{% endraw %} + +La función `always()` configura el job para seguir el procesamiento aún si existen fallos en las pruebas. Para obtener más información, consulta "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)". + +### Publicar en la galería de PowerShell + +Puedes configurar tu flujo de trabajo para que publique tu módulo de PowerShell en la galería de PowerShell cuando pasen tus pruebas de IC. Puedes utilizar los secretos para almacenar cualquier token o credencial que se necesiten para publicar tu paquete. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +El siguiente ejemplo crea un paquete y utiliza a `Publish-Module` para publicarlo en la galería de PowerShell: + +{% raw %} +```yaml +name: Publish PowerShell Module + +on: + release: + types: [created] + +jobs: + publish-to-gallery: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Build and publish + env: + NUGET_KEY: ${{ secrets.NUGET_KEY }} + shell: pwsh + run: | + ./build.ps1 -Path /tmp/samplemodule + Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-python.md b/translations/es-ES/content/actions/guides/building-and-testing-python.md new file mode 100644 index 0000000000000..ea0353313a043 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-python.md @@ -0,0 +1,428 @@ +--- +title: Crear y probar en Python +intro: Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu proyecto de Python. +redirect_from: + - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions + - /actions/language-and-framework-guides/using-python-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo construir, probar y publicar un paquete de Python. + +Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con un software preinstalado, que incluye Python y PyPy. ¡No tienes que instalar nada! Para obtener una lista completa de software actualizado y de las versiones preinstaladas de Python y PyPy, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Prerrequisitos + +Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Te recomendamos que tengas una comprensión básica de Python, PyPy y pip. Para obtener más información, consulta: +- [Comenzar con Python](https://www.python.org/about/gettingstarted/) +- [PyPy](https://pypy.org/) +- [Administrador de paquetes pip](https://pypi.org/project/pip/) + +{% data reusables.actions.enterprise-setup-prereq %} + +### Comenzar con la plantilla de flujo de trabajo de Python + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Python que debería funcionar para la mayoría de los proyectos de Python. Esta guía incluye ejemplos que puedes usar para personalizar la plantilla. Para obtener más información, consulta la [Plantilla de flujo de trabajo de Python](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). + +Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + python-version: [2.7, 3.5, 3.6, 3.7, 3.8] + + steps: + - uses: actions/checkout@v2 + - name: Set up Python ${{ matrix.python-version }} + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install flake8 pytest + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi + - name: Lint with flake8 + run: | + # stop the build if there are Python syntax errors or undefined names + flake8 . --Count--Select = E9, F63, F7, F82--show-Source--Statistics + # exit-zero trata todos los errores como advertencias. El editor de GitHub es 127 chars de ancho + flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics + - name: Test with pytest + run: | + pytest +``` +{% endraw %} + +### Especificar una versión de Python + +Para usar una versión preinstalada de Python o PyPy en un ejecutor alojado {% data variables.product.prodname_dotcom %}, usa la acción `setup-python`. Esta acción encuentra una versión específica de Python o PyPy desde la caché de herramientas en cada ejecutor y agrega los binarios necesarios para `PATH`, que persiste durante el resto del trabajo. Si una versión específica de Python no está pre-instalada en el cache de herramientas, la acción `setup-python` se descargará y configurará la versión adecuada desde el repositorio `python-versions`. + +Usar el `setup-action` es la forma recomendada de usar Python con {% data variables.product.prodname_actions %} porque garantiza un comportamiento consistente a través de diferentes ejecutores y diferentes versiones de Python. Si estás usando un ejecutor alojado, debes instalar Python y añadirlo a `PATH`. Para obtener más información, consulta la acción [`setup-python`](https://github.com/marketplace/actions/setup-python). + +La tabla que aparece a continuación describe las ubicaciones de la caché de herramientas en cada ejecutor alojado {% data variables.product.prodname_dotcom %}. + +| | Ubuntu | Mac | Windows | +| --------------------------------------- | ------------------------------- | ---------------------------------------- | ------------------------------------------ | +| **Directorio de caché de herramientas** | `/opt/hostedtoolcache/*` | `/Users/runner/hostedtoolcache/*` | `C:\hostedtoolcache\windows\ *` | +| **Caché de herramientas de Python** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\ *` | +| **Caché de la herramienta de PyPy** | `/opt/hostedtoolcache/PyPy/*` | `/Users/runner/hostedtoolcache/PyPy/*` | `C:\hostedtoolcache\windows\PyPy\ *` | + +Si estás utilizando un ejecutor auto-hospedado, puedes configurarlo para utilizar la acción `setup-python` para administrar tus dependencias. Para obtener más información, consulta la sección [utilizar setup-python con un ejecutor auto-hospedado](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) en el README de `setup-python`. + +{% data variables.product.prodname_dotcom %} admite la sintaxis de control de versiones semántico. Para obtener más información, consulta "[Usar versiones semánticas](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" y "[Especificación de control de versiones semántico](https://semver.org/)." + +#### Usar múltiples versiones de Python + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + # Puedes usar las versiones de PyPy en python-version. + # For example, pypy2 and pypy3 + matrix: + python-version: [2.7, 3.5, 3.6, 3.7, 3.8] + + steps: + - uses: actions/checkout@v2 + - name: Set up Python ${{ matrix.python-version }} + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # You can test your matrix by printing the current Python version + - name: Display Python version + run: python -c "import sys; print(sys.version)" +``` +{% endraw %} + +#### Usar una versión de Python específica + +Puedes configurar una versión específica de Python. Por ejemplo, 3.8. Como alternativa, puedes utilizar una sintaxis de versión semántica para obtener el último lanzamiento menor. En este ejemplo se usa el último lanzamiento menor de Python 3. + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + - name: Set up Python 3.x + uses: actions/setup-python@v2 + with: + # Semantic version range syntax or exact version of a Python version + python-version: '3.x' + # Optional - x64 or x86 architecture, defaults to x64 + architecture: 'x64' + # You can test your matrix by printing the current Python version + - name: Display Python version + run: python -c "import sys; print(sys.version)" +``` +{% endraw %} + +#### Excluir una versión + +Si especificas una versión de Python que no está disponible, `setup-python` falla con un error como: `##[error]Versión 3.4 con Arch x64 not found`. El mensaje de error incluye las versiones disponibles. + +También puedes usar la palabra clave `exclude` en tu flujo de trabajo si hay una configuración de Python que no deseas ejecutar. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)". + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ${{ matrix.os }} + strategy: + matrix: + os: [ubuntu-latest, macos-latest, windows-latest] + python-version: [2.7, 3.6, 3.7, 3.8, pypy2, pypy3] + exclude: + - os: macos-latest + python-version: 3.6 + - os: windows-latest + python-version: 3.6 +``` +{% endraw %} + +#### Usar la versión de Python predeterminada + +Recomendamos usar `setup-python` para configurar la versión de Python que se usa en tus flujos de trabajo porque ayuda a hacer que tus dependencias sean explícitas. Si no usas `setup-python`, la versión predeterminada de Python establecida en `PATH` se usa en cualquier shell cuando llamas `python`. La versión predeterminada de Python varía entre los ejecutores alojados {% data variables.product.prodname_dotcom %}, que pueden causar cambios inesperados o usar una versión anterior a la esperada. + +| Ejecutor alojado {% data variables.product.prodname_dotcom %} | Descripción | +| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Ubuntu | Los ejecutores de Ubuntu tienen múltiples versiones de Python del sistema instaladas bajo `/usr/bin/python` y `/usr/bin/python3`. Las versiones de Python que vienen empaquetadas con Ubuntu se suman a las versiones que {% data variables.product.prodname_dotcom %} instala en la caché de herramientas. | +| Windows | Excluyendo las versiones de Python que están en la caché de herramientas, Windows no se envía con una versión equivalente de Python del sistema. Para mantener un comportamiento consistente con otros ejecutores y para permitir que Python se use de forma integrada sin la acción `setup-python`, {% data variables.product.prodname_dotcom %} agrega algunas versiones desde la caché de herramientas a `PATH`. | +| macOS | Los ejecutores de macOS tienen más de una versión de Python del sistema instalada, además de las versiones que son parte de la caché de las herramientas. Las versiones de Python del sistema se encuentran en el directorio `/usr/local/Cellar/python/*`. | + +### Instalar dependencias + +Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen instalado el administrador del paquete pip. Puedes usar pip para instalar dependencias desde el registro del paquete de PyPI antes de construir y probar tu código. Por ejemplo, el YAML que aparece a continuación instala o actualiza el instalador del paquete `pip` y los paquetes `setuptools` y `wheel`. + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' +- name: Install dependencies + run: python -m pip install --upgrade pip setuptools wheel +``` +{% endraw %} + +#### Archivo de requisitos + +Después de actualizar `pip`, un siguiente paso típico es instalar dependencias desde *requirements.txt*. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' +- name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install -r requirements.txt +``` +{% endraw %} + +#### Dependencias de almacenamiento en caché + +Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar las dependencias pip en el caché utilizando una clave única y restaurar las dependencias cuando ejecutes flujos de trabajo subsecuentes, utilizando la acción [`cache`](https://github.com/marketplace/actions/cache). Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +Pip almacena en caché las dependencias en diferentes ubicaciones, en función del sistema operativo del ejecutor. La ruta que necesitarás para almacenar en caché puede diferir del ejemplo de Ubuntu que aparece a continuación, según el sistema operativo que uses. Para obtener más información, consulta [Ejemplos de almacenamiento en caché de Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' +- name: Cache pip + uses: actions/cache@v2 + with: + # This path is specific to Ubuntu + path: ~/.cache/pip + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-pip-${{ hashFiles('requirements.txt') }} + restore-keys: | + ${{ runner.os }}-pip- + ${{ runner.os }}- +- name: Install dependencies + run: pip install -r requirements.txt +``` +{% endraw %} + +{% note %} + +**Nota:** Dependiendo de la cantidad de dependencias, puede ser más rápido usar la caché de dependencias. Los proyectos con muchas dependencias de gran tamaño deberían ver un aumento del rendimiento, ya que reduce el tiempo necesario para la descarga. Los proyectos con menos dependencias pueden no ver un aumento significativo del rendimiento e incluso pueden ver una ligera disminución debido a la manera en que pip instala las dependencias almacenadas en caché. El rendimiento varía de un proyecto a otro. + +{% endnote %} + +### Probar tu código + +Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. + +#### Pruebas con pytest y pytest-cov + +Este ejemplo instala o actualiza `pytest` y `pytest-cov`. A continuación, se ejecutan y se emiten pruebas en formato JUnit, mientras que los resultados de la cobertura de código se emiten en Cobertura. Para obtener más información, consulta [JUnit](https://junit.org/junit5/) y [Cobertura](https://cobertura.github.io/Cobertura/). + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' +- name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install -r requirements.txt +- name: Test with pytest + run: | + pip install pytest + pip install pytest-cov + pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html +``` +{% endraw %} + +#### Usar Flake8 para el código lint + +En el siguiente ejemplo se instala o actualiza `flake8` y se usa para limpiar todos los archivos. Para obtener más información, consulta [Flake8](http://flake8.pycqa.org/en/latest/). + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' +- name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install -r requirements.txt +- name: Lint with flake8 + run: | + pip install flake8 + flake8 . +``` +{% endraw %} + +#### Ejecutar pruebas con tox + +Con {% data variables.product.prodname_actions %}, puedes ejecutar pruebas con tox y repartir el trabajo a través de múltiples trabajos. Necesitarás invocar tox utilizando la opción `-e py` para elegir la versión de Python en tu `PATH`, en lugar de especificar una versión específica. Para obtener más información, consulta [tox](https://tox.readthedocs.io/en/latest/). + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + python: [2.7, 3.7, 3.8] + + steps: + - uses: actions/checkout@v2 + - name: Setup Python + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python }} + - name: Install Tox and any other packages + run: pip install tox + - name: Run Tox + # Run tox using the version of Python in `PATH` + run: tox -e py +``` +{% endraw %} + +### Empaquetar datos de flujo de trabajo como artefactos + +Puedes cargar artefactos para ver después de que se complete un flujo de trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". + +En el siguiente ejemplo se muestra cómo puedes usar la acción `upload-artifact` para archivar los resultados de las pruebas de ejecución `pytest`. Para obtener más información, consulta la acción [`upload-artifact`](https://github.com/actions/upload-artifact). + +{% raw %} +```yaml +name: Python package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + python-version: [2.7, 3.5, 3.6, 3.7, 3.8] + + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### Publicar en registros de paquetes + +Puedes configurar tu flujo de trabajo para que publique tu paquete de Python en cualquier registro de paquete que desees cuando pasen tus pruebas de CI. + +Puedes almacenar cualquier token de acceso o credenciales que se necesiten para publicar tu paquete utilizando secretos. En el siguiente ejemplo, se crea y se publica un paquete para PyPI mediante `twine` y `dist`. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +{% raw %} +```yaml +name: Upload Python Package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install setuptools wheel twine + - name: Build and publish + env: + TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }} + TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }} + run: | + python setup.py sdist bdist_wheel + twine upload dist/* +``` +{% endraw %} + +Para obtener más información acerca del flujo de trabajo de la plantilla, consulta [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). diff --git a/translations/es-ES/content/actions/guides/building-and-testing-ruby.md b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md new file mode 100644 index 0000000000000..51dbfec857746 --- /dev/null +++ b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md @@ -0,0 +1,319 @@ +--- +title: Crear y probar en Ruby +intro: Puedes crear un flujo de trabajo de integración continua (CI) para crear y probar tu proyecto de Ruby. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo de integración contínua (IC) que cree y pruebe una aplicación de Ruby. Si tus pruebas de IC pasan, podrías querer desplegar tu código o publicar una gema. + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de Ruby, YAML, las opciones de configuración de flujo de trabajo y de cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta: + +- [Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions) +- [Ruby en 20 minutos](https://www.ruby-lang.org/en/documentation/quickstart/) + +### Comenzar con la plantilla de flujo de trabajo de Ruby + +{% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Ruby que funcionará con la mayoría de los proyectos de Ruby. Para obtener más información, consulta la sección [Plantilla de flujo de trabajo de Ruby](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml). + +Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. + +{% 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 %} + +### Especificar la versión de Ruby + +La forma más fácil de especificar una versión de Ruby es utilizando la acción `ruby/setup-ruby` que se proporciona en la organización de Ruby en GitHub. Esta acción agrega cualquier versión compatible con Ruby al `PATH` de cada ejecución de un job en un flujo de trabajo. Para obtener más información, consulta [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). + +Se recomienda utilizar Ruby con GitHub Actions, ya sea mediante la acción `ruby/setup-ruby` de Ruby, o mediante la acción `actions/setup-ruby` de Github; debido a que esto garantiza el comportamiento consistente entre ejecutores y versiones distintas de Ruby. + +La acción `setup-ruby` toma una versión de Ruby como entrada y la configura en el ejecutor. + +{% 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 %} + +Como alternativa, puedes ingresar un archivo de `.ruby-version` en la raíz de tu repositorio y `setup-ruby` utilizará la versión que se defina en dicho archivo. + +### Hacer pruebas con varias versiones de Ruby + +Puedes agregar una estrategia de matriz para ejecutar tu flujo de trabajo con más de una versión de Ruby. Por ejemplo, puedes probar tu código contra los últimos lanzamientos de parche para las versiones 2.7, 2.6, y 2.5. La 'x' es un caracter de comodín que empata el último lanzamiento de parche disponible para una versión. + +{% raw %} +```yaml +strategy: + matrix: + ruby-version: [2.7.x, 2.6.x, 2.5.x] +``` +{% endraw %} + +Cad versión de Ruby que se especifica en el arreglo `ruby-version` crea un job que ejecuta los mismos pasos. El contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} se utiliza para acceder a la versión actual del job. Para obtener más información acerca de las estrategias y contextos de las matrices, consulta las secciones "Sintaxis de flujos de trabajo para las GitHub Actions" y "Sintaxis de contexto y expresiones para las GitHub Actions" + +El flujo de trabajo ya actualizado en su totalidad con una estrategia de matriz podría verse así: + +{% 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 %} + +### Instalar dependencias con Bundler + +La acción `setup-ruby` te instalará bundler automáticamente. La versión se determina de acuerdo con tu archivo `gemfile.lock`. Si no hay alguna versión presente en tu archivo de bloqueo, entonces se instalará la última versión compatible. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.6 +- run: bundle install +``` +{% endraw %} + +#### Almacenar dependencias en caché + +Si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, las acciones de `setup-ruby` proporcionarán un método para manejar automáticamente el guardado en caché de tus gemas entre ejecuciones. + +Para habilitar el guardado en caché, configura lo siguiente. + +{% raw %} +```yaml +steps: +- uses: ruby/setup-ruby@v1 + with: + bundler-cache: true +``` +{% endraw %} + +Esto configurará a bundler para que instale tus gemas en `vendor/cache`. Para cada ejecución exitosa de tu flujo de trabajo, Actions guardará esta carpeta en caché y volverá a descargarse para cualquier ejecución de flujo de trabajo subsecuente. Se utiliza un hash de tu gemfile.lock y de la versión de Ruby como la clave de caché. Si instalas cualquier gema nueva o cambias una versión, el caché se invalidará y bundler realizará una instalación desde cero. + +**Guardar en caché sin setup-ruby** + +Para tener un mejor control sobre el guardado en caché, si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes utilizar la acción `actions/cache` directamente. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +{% 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 %} + +Si estás utilizando una compilación de matriz, deberás incluir las variables de dicha matriz en tu clave de caché. Por ejemplo, si tienes una estrategia de matriz para versiones de Ruby diferentes (`matrix.ruby-version`) y sistemas operativos diferentes (`matrix.os`), tus pasos de flujo de trabajo podrían verse así: + +{% 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 %} + +### Probar tu código en matrices + +La siguiente matriz de ejemplo prueba todos los lanzamientos estables y versiones principales de MRI, JRuby y TruffleRuby en Ubuntu y 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 %} + +### Limpiar tu código + +El siguiente ejemplo instala `rubocop` y lo utiliza para limpiar todos los archivos. Para obtener más información, consulta la sección [Rubocop](https://github.com/rubocop-hq/rubocop). Puedes [configurar Rubocop](https://docs.rubocop.org/rubocop/configuration.html) para decidir cuáles serán las reglas de limpieza específicas. + +{% 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 %} + +### Publicar gemas + +Puedes configurar tu flujo de trabajo para publicar tu paquete de Ruby en cualquier registro de paquetes que quieras cuando pasen tus pruebas de IC. + +Puedes almacenar todos los tokens de acceso o credenciales necesarios para publicar tu paquete utilizando secretos del repositorio. Elsiguiente ejemplo crea y publica un paquete en el `Registro de Paquetes de Github` y en `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/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md new file mode 100644 index 0000000000000..3883e180dd5e6 --- /dev/null +++ b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -0,0 +1,193 @@ +--- +title: Almacenar en caché las dependencias para agilizar los flujos de trabajo +shortTitle: Almacenar dependencias en caché +intro: 'Para hacer que tus flujos de trabajo sean más rápidos y eficientes, puedes crear y usar cachés para las dependencias y otros archivos comúnmente reutilizados.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows + - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows + - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows +versions: + free-pro-team: '*' +type: 'tutorial' +--- + +### Acerca de almacenar en caché las dependencias de flujo de trabajo + +Las ejecuciones de flujo de trabajo a menudo reutilizan las mismas salidas o dependencias descargadas de una ejecución a otra. Por ejemplo, las herramientas de administración de paquetes y dependencias como Maven, Gradle, npm y Yarn mantienen una caché local de las dependencias descargadas. + +Los trabajos en los ejecutores alojados {% data variables.product.prodname_dotcom %} se inician en un entorno virtual limpio y deben descargar dependencias cada vez, lo que provoca una mayor utilización de la red, un tiempo de ejecución más largo y un mayor costo. Para ayudar a acelerar el tiempo que se tarda en volver a crear estos archivos, {% data variables.product.prodname_dotcom %} puede almacenar en caché las dependencias que utilizas con frecuencia en los flujos de trabajo. + +Para almacenar en caché las dependencias de un trabajo, deberás usar la acción de `caché` de {% data variables.product.prodname_dotcom %}. La acción recupera una caché identificada por una clave única. Para más información, consulta [`actions/cache`](https://github.com/actions/cache). + +{% warning %} + +**Advertencia**: Te recomendamos que no almacenes ninguna información confidencial en la caché de los repositorios públicos. Por ejemplo, la información confidencial puede incluir tokens de acceso o credenciales de inicio de sesión almacenados en un archivo en la ruta de la caché. Además, los programas de interfaz de línea de comando (CLI) como `docker login` pueden guardar las credenciales de acceso en un archivo de configuración. Cualquier persona con acceso de lectura puede crear una solicitud de extracción en un repositorio y acceder a los contenidos de la caché. Las bifurcaciones de un repositorio también pueden crear solicitudes de extracción en la rama base y acceder a las cachés en la rama base. + +{% endwarning %} + +### Comparar artefactos y caché de dependencias + +Los artefactos y el almacenamiento en caché son similares porque brindan la posibilidad de almacenar archivos en {% data variables.product.prodname_dotcom %}, pero cada característica ofrece diferentes casos de uso y no se puede usar indistintamente. + +- Usa el almacenamiento en caché cuando quieras reutilizar archivos que no cambien a menudo entre trabajos o ejecuciones de flujo de trabajo. +- Usa artefactos cuando quieras guardar los archivos producidos por un trabajo para ver después de que haya finalizado un flujo de trabajo. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". + +### Restricciones para acceder a una caché + +Con la `v2` de la acción `cache`, puedes acceder al caché en en los flujos de trabajo que cualquier evento que tenga un `GITHUB_REF` active. Si estás utilizando la `v1` de la acción `cache`, únicamente podrás acceder al caché en los flujos de trabajo que activen los eventos `push` y `pull_request`, con excepción de aquellos eventos `pull_request` `closed`. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". + +Un flujo de trabajo puede acceder y restaurar una caché creada en la rama actual, la rama base (incluidas las ramas base de los repositorios bifurcados) o la rama predeterminada (por lo general `main`). Por ejemplo, un caché creado en la rama predeterminada sería accesible desde cualquier solicitud de cambios. También, si la rama `feature-b` tiene la rama base `feature-a`, un flujo de trabajo activado en `feature-b` tendría acceso a las cachés creadas en la rama predeterminada (`main`), `feature-a` y `feature-b`. + +Las restricciones de acceso proporcionan seguridad y aislamiento de caché al crear un límite lógico entre diferentes flujos de trabajo y ramas. Por ejemplo, un caché creado para la rama `feature-a` (con la base `main`) no sería accesible para una solicitud de extracción para la rama `feature-b` (con la base `main`). + +### Usando la acción `cache` + +La acción `cache` intentará restaurar una memoria caché basada en la `key` (clave) que proporciones. Cuando la acción encuentra una memoria caché, la acción restaura los archivos almacenados en la caché al `path` (ruta) que configures. + +Si no hay una coincidencia exacta, la acción crea una nueva entrada de caché si el trabajo se completa correctamente. La nueva memoria caché usará la `key` que proporcionaste y contiene los archivos en el directorio del `path`. + +De manera opcional, puedes proporcionar una lista de `restore-keys` para usar cuando la `key` no coincida con una memoria caché existente. Una lista de `restore-keys` es útil cuando estás restaurando una caché desde otra rama porque `restore-keys` pueden coincidir parcialmente con claves de caché. Para obtener más información acerca de la coincidencia `restore-keys`, consulta [Hacer coincidir una clave de caché](#matching-a-cache-key)". + +Para más información, consulta [`actions/cache`](https://github.com/actions/cache). + +#### Parámetros de entrada para la acción `chache` + +- `key`: **Obligatorio** La clave que se crea cuando se guarda una memoria caché y la clave utilizada para buscar una caché. Puede ser cualquier combinación de variables, valores de contexto, cadenas estáticas y funciones. Las claves tienen una longitud máxima de 512 caracteres y las claves más largas que la longitud máxima provocarán un error en la acción. +- `path`: **Obligatorio** La ruta del archivo en el ejecutor para almacenar en caché o restaurar. La ruta debe ser absoluta o relativa al directorio de trabajo. + - Con la `v2` de la acción `cache`, puedes especificar una ruta única, o rutas múltiples en forma de lista. Las rutas pueden ser tanto directorios o solo archivos, y los patrones estilo glob son compatibles. + - Con la `v1` de la acción `cache`, solo se puede utilizar una ruta única, la cual debe ser un directorio. No puedes almacenar en caché un archivo único. +- `restore-keys`: **Opcional** Una lista ordenada de claves alternativas que se usan para encontrar la caché si no se ha producido ningún hit de caché para `key`. + +#### Parámetros de salida para la acción `cache` + +- `cache-hit`: Un valor booleano para indicar que se encontró una coincidencia exacta para la llave. + +#### Ejemplo de uso para la acción `cache` + +Este ejemplo crea una nueva memoria caché cuando los paquetes en el archivo `package-lock.json` cambian o cuando cambia el sistema operativo del ejecutor. La clave de caché usa contextos y expresiones para generar una clave que incluye el sistema operativo del ejecutor y un hash SHA-256 del archivo `package-lock.json`. + +{% raw %} +```yaml +name: Caching with npm + +on: push + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Cache node modules + uses: actions/cache@v2 + env: + cache-name: cache-node-modules + with: + # npm cache files are stored in `~/.npm` on Linux/macOS + path: ~/.npm + key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }} + restore-keys: | + ${{ runner.os }}-build-${{ env.cache-name }}- + ${{ runner.os }}-build- + ${{ runner.os }}- + + - name: Install Dependencies + run: npm install + + - name: Build + run: npm build + + - name: Test + run: npm test + +``` +{% endraw %} + +Cuando `key` coincide con una caché existente, se denomina hit de caché y la acción restaura los archivos almacenados en la caché al directorio `path`. + +Cuando `key` no coincide con una caché existente, se denomina una falta de caché y se crea una nueva memoria caché si el trabajo se completa correctamente. Cuando se produce una falta de caché, la acción busca claves alternativas llamadas `restore-keys`. + +1. Si proporcionas `restore-Keys`, la acción `cache` busca cualquier caché en forma secuencial que coincida con la lista de `restore-keys`. + - Cuando hay una coincidencia exacta, la acción restaura los archivos en la memoria caché al directorio `path`. + - Si no hay coincidencias exactas, la acción busca coincidencias parciales de las claves de restauración. Cuando la acción encuentra una coincidencia parcial, se restaura la caché más reciente al directorio `path`. +1. La acción `cache` se completa y el siguiente paso en el flujo de trabajo del job se ejecuta. +1. Si el trabajo se completa correctamente, la acción crea una nueva memoria caché con los contenidos del directorio `path`. + +Para almacenar en caché los archivos en más de un directorio, necesitarás un paso que use la acción [`cache`](https://github.com/actions/cache) para cada directorio. Una vez que creas una caché, no puedes cambiar los contenidos de una memoria caché existente, pero puedes crear una nueva caché con una clave nueva. + +#### Usar contextos para crear claves de caché + +Una clave de caché puede incluir cualquiera de los contextos, funciones, literales y operadores admitidos por {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +Usar expresiones para crear una `key` te permite crear automáticamente una nueva caché cuando las dependencias han cambiado. Por ejemplo, puedes crear una `key` utilizando una expresión que calcule el hash de un archivo `package-lock.json` de npm. + +{% raw %} +``` +npm-${{ hashFiles('package-lock.json') }} +``` +{% endraw %} + +{% data variables.product.prodname_dotcom %} evalúa la expresión `hash "package-lock.json"` para obtener la última `key`. + +``` +npm-d5ea0750 +``` + +### Hacer coincidir una clave de caché + +La acción `cache` busca primero las coincidencias de caché para `key` y `restore-keys` en la rama que contiene la ejecución del flujo de trabajo. Si no hay coincidencias en la rama actual, la acción `chache` busca a `key` y `restore-keys` en la rama padre y en las ramas ascendentes. + +Puedes proporcionar una lista de claves de restauración para usar cuando haya una falta de caché en `key`. Puedes crear múltiples claves de restauración ordenadas desde las más específicas hasta las menos específicas. La acción `cache` busca `restore-keys` en orden secuencial. Cuando una clave no coincide directamente, la acción busca las claves prefijadas con la clave de restauración. Si hay múltiples coincidencias parciales para una clave de restauración, la acción devuelve la caché que se creó más recientemente. + +#### Ejemplo usando múltiples claves de restauración + +{% raw %} +``` +restore-keys: | + npm-foobar-${{ hashFiles('package-lock.json') }} + npm-foobar- + npm- +``` +{% endraw %} + +El ejecutor evalúa las expresiones, que resuelven estas `restore-keys`: + +{% raw %} +``` +restore-keys: | + npm-foobar-d5ea0750 + npm-foobar- + npm- +``` +{% endraw %} + +La clave de restauración `npm-foobar-` coincide con cualquier clave que empiece con la cadena `npm-foobar-`. Por ejemplo, ambas claves `npm-foobar-fd3052de` y `npm-foobar-a9b253ff` coinciden con la clave de restauración. Se utilizará la caché con la fecha de creación más reciente. Las claves en este ejemplo se buscan en el siguiente orden: + +1. **`npm-foobar-d5ea0750`** coincide con un hash específico. +1. **`npm-foobar-`** coincide con claves de caché prefijadas con `npm-foobar-`. +1. **`npm`** coincide con cualquier clave prefijada con `npm`. + +##### Ejemplo de prioridad de búsqueda + +```yaml +key: + npm-feature-d5ea0750 +restore-keys: | + npm-feature- + npm- +``` + +Por ejemplo, si una solicitud de cambios contiene una rama `feature` (el alcance actual) y se dirige a la rama predeterminada (`main`), la acción busca a `key` y a `restore-keys` en el siguiente orden: + +1. Clave `npm-feature-d5ea0750` en el alcance de la rama `feature` +1. Clave `npm-feature-` en el alcance de la rama `feature` +2. Clave `npm` en el alcance de la rama `feature` +1. Clave `npm-feature-d5ea0750` en el alcance de la rama `main` +3. Clave `npm-feature-` en el alcance de la rama `main` +4. Clave `npm-` en el alcance de la rama `main` + +### Límites de uso y política de desalojo + +{% data variables.product.prodname_dotcom %} eliminará todas las entradas de caché a las que no se haya accedido en más de 7 días. No hay límite en la cantidad de cachés que puedes almacenar, pero el tamaño total de todas las cachés en un repositorio está limitado a 5 GB. Si excedes este límite, {% data variables.product.prodname_dotcom %} guardará tu caché, pero comenzará a desalojar las cachés hasta que el tamaño total sea inferior a 5 GB. diff --git a/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md new file mode 100644 index 0000000000000..64d589fb3e9d1 --- /dev/null +++ b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md @@ -0,0 +1,328 @@ +--- +title: Crear contenedores de servicios PostgreSQL +shortTitle: Contenedores de servicio de PostgreSQL +intro: Puedes crear un contenedor de servicios PostgreSQL para usar en tu flujo de trabajo. En esta guía se muestran ejemplos de cómo crear un servicio PostgreSQL para trabajos que se ejecutan en contenedores o, directamente, en la máquina del ejecutor. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Creating-PostgreSQL-Service-containers + - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +En esta guía se muestran ejemplos de flujos de trabajo que configuran un contenedor de servicios mediante la imagen `postgres` de Docker Hub. El flujo de trabajo ejecuta un script para crear un cliente de PostgreSQL y rellenarlo con datos. Para probar que el flujo de trabajo crea y rellena el cliente de PostgreSQL, el script imprime los datos del cliente en la consola. + +{% data reusables.github-actions.docker-container-os-support %} + +### Prerrequisitos + +{% data reusables.github-actions.service-container-prereqs %} + +También puede ser útil tener un conocimiento básico de YAML, la sintaxis para las {% data variables.product.prodname_actions %}, y de PostgreSQL. Para obtener más información, consulta: + +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" +- "[Tutorial de PostgreSQL](https://www.postgresqltutorial.com/)" en la documentación de PostgreSQL + +### Ejecutar trabajos en contenedores + +{% data reusables.github-actions.container-jobs-intro %} + +{% data reusables.github-actions.copy-workflow-file %} + +{% raw %} +```yaml +name: PostgreSQL service example +on: push + +Jobs: + # Etiqueta del trabajo del contenedor + container-job: + # Los contenedores deben ejecutarse en sistemas operativos basados en Linux + runs-on: Ubuntu-latest + # Imagen de Docker Hub que ejecuta 'container-job ' en + el contenedor: node:10.18-jessie + + # Contenedores de servicios para ejecutar con servicios de 'container-job ': + # Etiqueta usada para acceder al contenedor de servicios + Postgres: + # Imagen de Docker Hub + image: postgres + # Proporciona la contraseña para Postgres + env: + POSTGRES_PASSWORD: postgres + # Establece chequeos de estado para esperar hasta que postgres inicie las + opciones: >- + --health-cmd pg_isready + --health-interval 10s + --health-timeout 5s + --health-retries 5 + + Steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json' + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to PostgreSQL + # Ejecuta un script que crea un cliente de PostgreSQL, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script 'client.js' para crear un nuevo cliente de PostgreSQL. + env: + # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL + POSTGRES_HOST: Postgres + # Puerto PostgreSQL predeterminado + POSTGRES_PORT: 5432 +``` +{% endraw %} + +#### Configurar el trabajo del ejecutador + +{% data reusables.github-actions.service-container-host %} + +{% data reusables.github-actions.postgres-label-description %} + +```yaml +jobs: + # Etiqueta del trabajo del contenedor + container-job: + # Los contenedores deben ejecutarse en sistemas operativos basados en Linux + runs-on: ubuntu-latest + # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie + + # Contenedores de servicios para ejecutar con servicios de `container-job`: + # Etiqueta utilizada para acceder al contenedor de servicios + redis: + # Imagen de Docker Hub + image: redis + # Establece revisiones de estado para esperar hasta que Redis inicie las + opciones: >- + --health-cmd "redis-cli ping" + --health-interval 10s + --health-timeout 5s + --health-retries 5 +``` + +#### Configurar los pasos + +{% data reusables.github-actions.service-template-steps %} + +```yaml +steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json' + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to PostgreSQL + # Ejecuta un script que crea un cliente de PostgreSQL, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script 'client.js ' para crear + # un nuevo cliente de PostgreSQL. + env: + # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL + POSTGRES_HOST: Postgres + # Puerto PostgreSQL predeterminado + POSTGRES_PORT: 5432 +``` + +{% data reusables.github-actions.postgres-environment-variables %} + +El nombre del host del servicio PostgreSQL es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `postgres`. Dado que los contenedores de Docker de la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor de servicios en el puerto 5432 PostgreSQL predeterminado. + +### Ejecutar trabajos directamente en la máquina del ejecutor + +Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker. + +{% data reusables.github-actions.copy-workflow-file %} + +{% raw %} +```yaml +name: PostgreSQL Service Example +on: push + +Jobs: + # Etiqueta del trabajo del ejecutador + runner-job: + # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor + runs-on: ubuntu-latest + + # Contenedores de servicios para ejecutar con servicios de 'runner-job': + # Etiqueta usada para acceder al contenedor de servicios + postgres: + # Imagen de Docker Hub + image: postgres + # Proporciona la contraseña para postgres + env: + POSTGRES_PASSWORD: Postgres + # Establece chequeos de estado para esperar hasta que postgres inicie las + opciones: >- + --health-cmd pg_isready + --health-interval 10s + --health-timeout 5s + --health-retries 5 + ports: + # Asigna el puerto tcp 5432 del contenedor de servicios al host + -5432:5432 + + Steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json' + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to PostgreSQL + # Ejecuta un script que crea un cliente de PostgreSQL, rellena + # el cliente con datos y recupera datos + Run: node client.js + # Variable de entorno utilizada por el script 'client.js' para crear + # un nuevo cliente de PostgreSQL. + env: + # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL + POSTGRES_HOST: localhost + # Puerto PostgreSQL predeterminado + POSTGRES_PORT: 5432 +``` +{% endraw %} + +#### Configurar el trabajo del ejecutador + +{% data reusables.github-actions.service-container-host-runner %} + +{% data reusables.github-actions.postgres-label-description %} + +El flujo de trabajo asigna el puerto 5432 del contenedor de servicios PostgreSQL al host de Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". + +```yaml +jobs: + # Etiqueta del trabajo del ejecutador + Runner-Job: + # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor + runs-on: ubuntu-latest + + # Contenedores de servicios para ejecutar con servicios 'runner-job': + # Etiqueta usada para acceder al contenedor de servicios + Postgres: + # Imagen de Docker Hub + image: postgres + # Proporciona la contraseña para postgres + Env: + POSTGRES_PASSWORD: postgres + # Establece chequeos de estado para esperar hasta que postgres inicie las + opciones: >- + --health-cmd pg_isready + --health-interval 10s + --health-timeout 5s + --health-retries 5 + Ports: + # Asigna el puerto tcp 5432 del contenedor de servicios al host + -5432:5432 +``` + +#### Configurar los pasos + +{% data reusables.github-actions.service-template-steps %} + +```yaml +steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json' + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to PostgreSQL + # Ejecuta un script que crea un cliente de PostgreSQL, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script 'client.js ' para crear + # un nuevo cliente de PostgreSQL. + env: + # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL + POSTGRES_HOST: localhost + # Puerto PostgreSQL predeterminado + POSTGRES_PORT: 5432 +``` + +{% data reusables.github-actions.postgres-environment-variables %} + +{% data reusables.github-actions.service-container-localhost %} + +### Probar el contenedor de servicios de PostgreSQL + +Puedes probar tu flujo de trabajo usando el siguiente script, que crea un cliente de PostgreSQL y agrega una tabla nueva con algunos datos de marcador de posición. Luego, el script le imprime los valores almacenados en el cliente de PostgreSQL al terminal. Tu script puede usar el lenguaje que quieras, pero este ejemplo usa Node.js y el módulo npm de `pg`. Para obtener más información, consulta el [módulo npm de pg](https://www.npmjs.com/package/pg). + +Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que necesite tu flujo de trabajo. En este ejemplo, el script crea la instancia de cliente de PostgreSQL, crea una tabla, agrega datos de marcador de posición y luego recupera los datos. + +{% data reusables.github-actions.service-container-add-script %} + +```javascript +const { Client } = require('pg'); + +const pgclient = new Client({ + host: process.env.POSTGRES_HOST, + port: process.env.POSTGRES_PORT, + user: 'postgres', + password: 'postgres', + database: 'postgres' +}); + +pgclient.connect(); + +const table = 'CREATE TABLE student(id SERIAL PRIMARY KEY, firstName VARCHAR(40) NOT NULL, lastName VARCHAR(40) NOT NULL, age INT, address VARCHAR(80), email VARCHAR(40))' +const text = 'INSERT INTO student(firstname, lastname, age, address, email) VALUES($1, $2, $3, $4, $5) RETURNING *' +const values = ['Mona the', 'Octocat', 9, '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States', 'octocat@github.com'] + +pgclient.query(table, (err, res) => { + if (err) throw err +}); + +pgclient.query(text, values, (err, res) => { + if (err) throw err +}); + +pgclient.query('SELECT * FROM student', (err, res) => { + if (err) throw err + console.log(err, res.rows) // Print the data in student table + pgclient.end() +}); +``` + +El script crea un nuevo `Client` (cliente) de PostgreSQL, que acepta un `host` y un parámetro de `port` (puerto). El script usa las variables de entorno `POSTGRES_HOST` y `POSTGRES_PORT` para establecer la dirección IP y el puerto del cliente. Si `host` y `port` no están definidos, el host predeterminado es `localhost` y el puerto predeterminado es 5432. + +El script crea una tabla y la rellena con datos de marcador de posición. Para probar que la base de datos de PostgreSQL contenga los datos, el script imprime los contenidos de la tabla en el registro de la consola. + +Cuando ejecutes este flujo de trabajo, debes ver el siguiente resultado en el paso "Connect to PostgreSQL" (Conectar con PostgreSQL) que confirma que creaste el cliente de PostgreSQL y agregaste los datos: + +``` +null [ { id: 1, + firstname: 'Mona the', + lastname: 'Octocat', + age: 9, + address: + '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States', + email: 'octocat@github.com' } ] +``` diff --git a/translations/es-ES/content/actions/guides/creating-redis-service-containers.md b/translations/es-ES/content/actions/guides/creating-redis-service-containers.md new file mode 100644 index 0000000000000..7a639ad34188d --- /dev/null +++ b/translations/es-ES/content/actions/guides/creating-redis-service-containers.md @@ -0,0 +1,323 @@ +--- +title: Crear contenedores de servicio Redis +shortTitle: Contenedores de servicio de Redis +intro: Puedes usar los contenedores de servicio para crear un cliente Redis en tu flujo de trabajo. En esta guía se muestran ejemplos de cómo crear un servicio Redis para los trabajos que se ejecutan en contenedores o directamente en la máquina ejecutor. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers + - /actions/configuring-and-managing-workflows/creating-redis-service-containers +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +En esta guía se muestran ejemplos de flujo de trabajo que configuran un contenedor de servicio mediante la imagen `redis` de Docker Hub. El flujo de trabajo ejecuta un script para crear un cliente Redis y rellenar el cliente con datos. Para probar que el flujo de trabajo crea y rellena el cliente Redis, el script imprime los datos del cliente en la consola. + +{% data reusables.github-actions.docker-container-os-support %} + +### Prerrequisitos + +{% data reusables.github-actions.service-container-prereqs %} + +También puede ser útil tener una comprensión básica de YAML, la sintaxis para {% data variables.product.prodname_actions %}, y Redis. Para obtener más información, consulta: + +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" +- "[Comenzar con Redis](https://redislabs.com/get-started-with-redis/)"en la documentación de Redis + +### Ejecutar trabajos en contenedores + +{% data reusables.github-actions.container-jobs-intro %} + +{% data reusables.github-actions.copy-workflow-file %} + +{% raw %} +```yaml +name: Redis container example +on: push + +jobs: + # Etiqueta del trabajo del contenedor + container-job: + # Los contenedores deben ejecutarse en sistemas operativos basados en Linux + runs-on: ubuntu-latest + # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie + + # Contenedores de servicio para ejecutar con `container-job` + services: + # Etiqueta usada para acceder al contenedor de servicio redis: + # Imagen del contenedor Docker Hub + image: redis + # Establece revisiones de estado para esperar hasta que Redis haya comenzado + options: >- + --health-cmd "redis-cli ping" + --health-interval 10s + --health-timeout 5s + --health-retries 5 + + steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo `package.json` + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to Redis + # Ejecuta un script que crea un cliente Redis, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script `client.js` para crear un nuevo cliente Redis. + env: + # El nombre del host utilizado para comunicarse con el contenedor de servicio Redis + REDIS_HOST: redis + # El puerto Redis predeterminado + REDIS_PORT: 6379 +``` +{% endraw %} + +#### Configurar el trabajo del contenedor + +{% data reusables.github-actions.service-container-host %} + +{% data reusables.github-actions.redis-label-description %} + +```yaml +jobs: + # Etiqueta del trabajo del contenedor + container-job: + # Los contenedores deben ejecutarse en sistemas operativos basados en Linux + runs-on: ubuntu-latest + # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie + + # Contenedores de servicio para ejecutar con `container-job` + services: + # Etiqueta utilizada para acceder al contenedor de servicio + redis: + # Imagen de Docker Hub + image: redis + # Establece revisiones de estado para esperar hasta que Redis haya comenzado + options: >- + --health-cmd "redis-cli ping" + --health-interval 10s + --health-timeout 5s + --health-retries 5 +``` + +#### Configurar los pasos + +{% data reusables.github-actions.service-template-steps %} + +```yaml +steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo `package.json` + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to Redis + # Ejecuta un script que crea un cliente Redis, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script `client.js` para crear un nuevo cliente Redis. + env: + # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis + REDIS_HOST: redis + # El puerto Redis predeterminado + REDIS_PORT: 6379 +``` + +{% data reusables.github-actions.redis-environment-variables %} + +El nombre del host del servicio Redis es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `redis`. Dado que los contenedores Docker en la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor del servicio en el puerto Redis predeterminado 6379. + +### Ejecutar trabajos directamente en la máquina del ejecutor + +Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker. + +{% data reusables.github-actions.copy-workflow-file %} + +{% raw %} +```yaml +name: Redis runner example +on: push + +jobs: + # Etiqueta del trabajo del ejecutor + runner-job: + # Debes usar un entorno Linux cuando utilices contenedores de servicio o trabajos de contenedor + runs-on: ubuntu-latest + + # Contenedores de servicio para ejecutar con `runner-job` + services: + # Etiqueta usada para acceder al contenedor de servicio + redis: + # Imagen de Docker Hub + image: redis + # Establece revisiones de estado para esperar hasta que Redis haya comenzado + options: >- + --health-cmd "redis-cli ping" + --health-interval 10s + --health-timeout 5s + --health-retries 5 + ports: + # Asigna el puerto 6379 en el contenedor de servicio al host + - 6379:6379 + + steps: + # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo `package.json` + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to Redis + # Ejecuta un script que crea un cliente Redis, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script `client.js` para crear + # un nuevo cliente Redis. + env: + # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis + REDIS_HOST: localhost + # El puerto Redis predeterminado + REDIS_PORT: 6379 +``` +{% endraw %} + +#### Configurar el trabajo del ejecutador + +{% data reusables.github-actions.service-container-host-runner %} + +{% data reusables.github-actions.redis-label-description %} + +El flujo de trabajo asigna el puerto 6379 en el contenedor del servicio Redis al host Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". + +```yaml +jobs: + # Etiqueta del trabajo del ejecutor + runner-job: + # Debes usar un entorno Linux cuando utilices contenedores de servicio o trabajos de contenedor + runs-on: ubuntu-latest + + # Contenedores de servicio para ejecutar con `runner-job` + services: + # Etiqueta usada para acceder al contenedor de servicio + redis: + # Imagen de Docker Hub + image: redis + # Establece revisiones de estado para esperar hasta que Redis haya comenzado + options: >- + --health-cmd "redis-cli ping" + --health-interval 10s + --health-timeout 5s + --health-retries 5 + ports: + # Asigna el puerto 6379 en el contenedor de servicio al host + - 6379:6379 +``` + +#### Configurar los pasos + +{% data reusables.github-actions.service-template-steps %} + +```yaml +steps: + # Descarga una copia del código en tu repositorio antes de ejecutra pruebas de CI + - name: Check out repository code + uses: actions/checkout@v2 + + # Realiza una instalación limpia de todas las dependencias en el archivo `package.json` + # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html + - name: Install dependencies + run: npm ci + + - name: Connect to Redis + # Ejecuta un script que crea un cliente Redis, rellena + # el cliente con datos y recupera datos + run: node client.js + # Variable de entorno utilizada por el script `client.js` para crear + # un nuevo cliente Redis. + env: + # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis + REDIS_HOST: localhost + # El puerto Redis predeterminado + REDIS_PORT: 6379 +``` + +{% data reusables.github-actions.redis-environment-variables %} + +{% data reusables.github-actions.service-container-localhost %} + +### Probar el contenedor de servicio Redis + +Puedes probar tu flujo de trabajo usando el siguiente script, que crea un cliente Redis y rellena el cliente con algunos datos del marcador de posición. Luego, el script imprime los valores almacenados en el cliente Redis en el terminal. Tu script puede usar cualquier lenguaje que desees, pero este ejemplo usa Node.js y el módulo de npm `redis`. Para obtener más información, consulta el [Módulo Redis de npm](https://www.npmjs.com/package/redis). + +Puedes modificar *client.js* para incluir cualquier operación de Redis que necesite tu flujo de trabajo. En este ejemplo, el script crea la instancia del cliente Redis, agrega datos de marcador de posición y luego recupera los datos. + +{% data reusables.github-actions.service-container-add-script %} + +```javascript +const redis = require("redis"); + +// Crea un nuevo cliente Redis +// Si no se establece REDIS_HOST, el host predeterminado es localhost +// Si no se establece REDIS_PORT, el puerto predeterminado es 6379 +const redisClient = redis.createClient({ + host: process.env.REDIS_HOST, + port: process.env.REDIS_PORT +}); + +redisClient.on("error", function(err) { + console.log("Error " + err); +}); + +// Establece la clave "octocat" para un valor de "Mona the octocat" +redisClient.set("octocat", "Mona the Octocat", redis.print); +// Establece una clave "octocat", campo para "species" y "value" para "Cat and Octopus" +redisClient.hset("species", "octocat", "Cat and Octopus", redis.print); +// Establece una clave para "octocat", campo para "species" y "value" para "Dinosaur and Octopus" +redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print); +// Establece una clave para "octocat", campo para "species" y "value" para "Cat and Robot" +redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print); +// Obtiene todos los campos en la clave "species" + +redisClient.hkeys("species", function (err, replies) { + console.log(replies.length + " replies:"); + replies.forEach(function (reply, i) { + console.log(" " + i + ": " + reply); + }); + redisClient.quit(); +}); +``` + +El script crea un nuevo cliente Redis utilizando el método `createClient`, que acepta un parámetro de `host` y `port`. El script usa el `REDIS_HOST` y variables de entorno `REDIS_PORT` para establecer la dirección IP y el puerto del cliente. Si `host` y `port` no están definidos, el host predeterminado es `localhost` y el puerto predeterminado es 6379. + +El script usa los métodos `set` y `hset` para rellenar la base de datos con algunas claves, campos y valores. Para confirmar que el cliente Redis contiene los datos, el script imprime los contenidos de la base de datos en el registro de la consola. + +Cuando ejecutas este flujo de trabajo, deberías ver el siguiente resultado en el paso "Conectar con Redis" que confirma que creaste el cliente Redis y agregaste datos: + +``` +Reply: OK +Reply: 1 +Reply: 1 +Reply: 1 +3 replies: + 0: octocat + 1: dinotocat + 2: robotocat +``` diff --git a/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md new file mode 100644 index 0000000000000..8c1b0fbf2f8f8 --- /dev/null +++ b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -0,0 +1,148 @@ +--- +title: Desplegar hacia Amazon Elastic Container Service +intro: Puedes hacer despliegues para Amazon Elastic Container Service (ECS) como parte de tus flujos de trabajo de despliegue contínuo (DC). +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 %} + +### Introducción + +Esta guía te explica cómo utilizar {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla a [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), y desplegarla en [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). + +En cada lanzamiento nuevo de tu repositorio de {% data variables.product.company_short %}, el flujo de trabajo de {% data variables.product.prodname_actions %} crea y sube una imagen de contenedor nueva en Amazon ECR, y luego despliega una tarea nueva de definición en Amazon ECS. + +### Prerrequisitos + +Antes de que crees tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitas completar los siguientes pasos de configuración para Amazon ECR y ECS: + +1. Crea un repositorio de Amazon ECR para almacenar tus imágenes. + + Por ejemplo, utiliza [el CLI de AWS](https://aws.amazon.com/cli/): + + {% raw %}```bash{:copy} + aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION + ```{% endraw %} + + Asegúrate de que utilizas el mismo nombre de repositorio para amazon ECR (que se representa aquí como `MY_ECR_REPOSITORY`) para la variable `ECR_REPOSITORY` en el flujo de trabajo a continuación. + + Asegúrate de que utilizas el mismo valor de región de AWS para la variable `AWS_REGION` (que se representa aquí como `MY_AWS_REGION`) en el flujo de trabajo a continuación. + +2. Crea un servicio, agrupamiento y definición de tarea de Amazon ECS. + + Para obtener más detalles, sigue la sección [Asistente de inicio para la consola de Amazon ECS](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), o la [Guía de inicio](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) en la documentación de Amazon ECS. + + Asegúrate de anotar los nombres que configuraste para el servicio y agrupamiento de Amazon ECS y utilízalos para las variables `ECS_SERVICE` y `ECS_CLUSTER` en el flujo de trabajo a continuación. + +3. Almacena tu definición de tarea de Amazon ECS como un archivo JSON en tu repositorio de {% data variables.product.company_short %}. + + El formato del archivo debe ser el mismo que la salida que genera: + + {% raw %}```bash{:copy} + aws ecs register-task-definition --generate-cli-skeleton + ```{% endraw %} + + Asegúrate de configurar la variable `ECS_TASK_DEFINITION` en el flujo de trabajo a continuación como la ruta al archivo JSON. + + Asegúrate de configurar la variable `CONTAINER_NAME` en el flujo de trabajo a continuación como el nombre de contenedor en la sección `containerDefinitions` de la definición de tarea. + +4. Crea los secretos de {% data variables.product.prodname_actions %} con los nombres `AWS_ACCESS_KEY_ID` y `AWS_SECRET_ACCESS_KEY` para almacenar los valores de tu llave de acceso de Amazon IAM. + + Para obtener más información sobre cómo crear los secretos para {% data variables.product.prodname_actions %}, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". + + Consulta la documentación para cada acción que se utiliza a continuación para las políticas recomendadas de IAM para el usuario de IAM y los métodos para manejar las credenciales de las llaves de acceso. + +### Crear el flujo de trabajo + +Una vez que completes los prerrequisitos, puedes proceder con la creación del flujo de trabajo. + +El siguiente flujo de trabajo de ejemplo demuestra cómo construir una imagen de contenedor y subirla a Amazon ECR. Posteriormente, ésta actualiza la definición de la tarea con una ID de imagen nueva y despliega la definición de tarea a Amazon ECS. + +Asegúrate de que proporcionas tus propios valores para todas las variables en la clave `env` del flujo de trabajo. + +{% raw %} +```yaml{:copy} +name: Deploy to Amazon ECS + +on: + release: + types: [ created ] + +env: + AWS_REGION: MY_AWS_REGION # configura esto con tu región de AWS preferida, por ejemplo: us-west-1 + ECR_REPOSITORY: MY_ECR_REPOSITORY # configura esto con tu nombre de repositorio de Amzon ECR + ECS_SERVICE: MY_ECS_SERVICE # configura esto con tu nombre de servicio de Amazon ECS + ECS_CLUSTER: MY_ECS_CLUSTER # configura esto con tu nombre de agrupamiento de Amazon ECS + ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # configura esto con la ruta a tu definición de tarea de Amazon ECS + # archivo, por ejemplo: .aws/task-definition.json + CONTAINER_NAME: MY_CONTAINER_NAME # configura esto con el nombre del contenedor en la sección de + # containerDefinitions de tu definición de tarea + +defaults: + run: + shell: bash + +jobs: + deploy: + name: Deploy + runs-on: ubuntu-latest + + steps: + - name: Checkout + uses: actions/checkout@v2 + + - name: Configure AWS credentials + uses: aws-actions/configure-aws-credentials@v1 + with: + aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} + aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} + aws-region: $AWS_REGION + + - name: Login to Amazon ECR + id: login-ecr + uses: aws-actions/amazon-ecr-login@v1 + + - name: Build, tag, and push image to Amazon ECR + id: build-image + env: + ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} + IMAGE_TAG: ${{ github.sha }} + run: | + # Build a docker container and + # push it to ECR so that it can + # be deployed to ECS. + docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . + docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG + echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_ENV + + - name: Fill in the new image ID in the Amazon ECS task definition + id: task-def + uses: aws-actions/amazon-ecs-render-task-definition@v1 + with: + task-definition: $ECS_TASK_DEFINITION + container-name: $CONTAINER_NAME + image: ${{ steps.build-image.outputs.image }} + + - name: Deploy Amazon ECS task definition + uses: aws-actions/amazon-ecs-deploy-task-definition@v1 + with: + task-definition: ${{ steps.task-def.outputs.task-definition }} + service: $ECS_SERVICE + cluster: $ECS_CLUSTER + wait-for-service-stability: true +``` +{% endraw %} + +### Recursos adicionales + +Para obtener más información sobre los servicios que se utilizan en estos ejemplos, consulta la siguiente documentación: + +* "[Mejores prácticas de seguridad de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" en la documentación de AWS. +* Acción oficial de "[Configurar las credenciales de AWS](https://github.com/aws-actions/configure-aws-credentials)" de AWS. +* Acción oficial de ["Inicio de sesión" de Amazon ECR](https://github.com/aws-actions/amazon-ecr-login) de AWS. +* Acción oficial de ["Definición de tarea de renderización" de Amazon ECS](https://github.com/aws-actions/amazon-ecs-render-task-definition)de AWS. +* Acción oficial de ["Desplegar definición de tarea" de Amazon ECS](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) de AWS. diff --git a/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md b/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md new file mode 100644 index 0000000000000..561d3ea09ab55 --- /dev/null +++ b/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md @@ -0,0 +1,115 @@ +--- +title: Desplegar a Azure App Service +intro: Puedes desplegar hacia Azure App Service como parte de tus flujos de trabajo de despliegue continuo (DC). +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 %} + +### Introducción + +Esta guía te explica cómo utilizar {% data variables.product.prodname_actions %} para crear, probar y desplegar una aplicación en [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/). + +Azure App Service puede ejecutar apps web en varios lenguajes de programación, pero esta guía demuestra el despliegue en un proyecto existente que se encuentra en Node.js. + +### Prerrequisitos + +Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración: + +1. Crear un plan de Azure App Service. + + Por ejemplo, puedes utilizar el CLI de Azure para crear un plan de App Service nuevo: + + ```bash{:copy} + az appservice plan create \ + --resource-group MY_RESOURCE_GROUP \ + --name MY_APP_SERVICE_PLAN \ + --is-linux + ``` + + En el comando anterior, reemplaza `MY_RESOURCE_GROUP` con tu Grupo de Recursos de Azure preexistente y `MY_APP_SERVICE_PLAN` con un nombre nuevo para el plan de App Service. + + Consulta la documentación de Azure para obtener más información sobre cómo utilizar el [CLI de Azure](https://docs.microsoft.com/en-us/cli/azure/): + + * Para la autenticación, consulta "[Iniciar sesión con Azure CLI](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli)". + * Si necesitas crear un grupo de recursos nuevo, consulta lasección "[grupo az](https://docs.microsoft.com/en-us/cli/azure/group?view=azure-cli-latest#az_group_create)". + +2. Crea una app web. + + Por ejemplo, puedes utilizar el CLI de Azure para crear una app web de Azure App Service con un tiempo de ejecución de nodo: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "node|10.14" + ``` + + En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web. + +3. Configura un perfil de publicación de Azure y crea un secreto de `AZURE_WEBAPP_PUBLISH_PROFILE`. + + Genera tus credenciales de despliegue de Azure utilizando un perfil de publicación. Para obtener más información, consulta la sección "[Generar credenciales de despliegue](https://docs.microsoft.com/en-us/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" en la documentación de Azure. + + En tu repositorio de {% data variables.product.prodname_dotcom %}, crea un secreto que se llame `AZURE_WEBAPP_PUBLISH_PROFILE` que tenga el contenido del perfil de publicación. Para obtener más información sobre cómo crear secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". + +### Crear un flujo de trabajo + +Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo. + +El siguiente flujo de trabajo de ejemplo demuestra cómo crear, probar y desplegar el proyecto de Node.js en Azura App Service. + +Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. + +{% raw %} +```yaml{:copy} +on: + release: + types: [created] + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root + NODE_VERSION: '10.x' # set this to the node version to use + +jobs: + build-and-deploy: + name: Build and Deploy + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + + - name: Use Node.js ${{ env.NODE_VERSION }} + uses: actions/setup-node@v1 + with: + node-version: ${{ env.NODE_VERSION }} + + - name: npm install, build, and test + run: | + # Build and test the project, then + # deploy to Azure Web App. + npm install + npm run build --if-present + npm run test --if-present + + - name: 'Deploy to Azure WebApp' + uses: azure/webapps-deploy@v2 + with: + app-name: ${{ env.AZURE_WEBAPP_NAME }} + publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }} + package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }} +``` +{% endraw %} + +### Recursos adicionales + +Los siguientes recursos también pueden ser útiles: + +* Para el flujo de trabajo inicial original, consulta el archivo [`azure.yml`](https://github.com/actions/starter-workflows/blob/master/ci/azure.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}. +* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure. +* La guía rápida de "[Crear una app web de Node.js en Azure](https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs)" dentro de la documentación de la app web de Azure demuestra cómo utilizar VS Code con la [Extensión de Azure App Service](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). diff --git a/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md new file mode 100644 index 0000000000000..a0783e330a860 --- /dev/null +++ b/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -0,0 +1,177 @@ +--- +title: Desplegar a Google Kubernetes Engine +intro: Puedes desplegar hacia Google Kubernetes Engine como parte de tus flujos de trabajo de despliegue continuo (DC). +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 %} + +### Introducción + +Esta guía te explica cómo utilizar {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla al Registro de Contenedor de Google (GCR), y desplegarla hacia Google Kubernetes Engine (GKE). + +GKE es un agrupamiento administrado de Kubernetes de Google Cloud que puede hospedar tus cargas de trabajo contenerizadas en la nube o en tu propio centro de datos. Para obtener más información, consulta la página de [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). + +### Prerrequisitos + +Antes de proceder con la creación del flujo de trabajo, necesitarás completar los siguientes pasos par tu proyecto de Kubernetes. Esta guía asume que la raíz de tu proyecto ya tiene un `Dockerfile` y un archivo de configuración para el despliegue de Kubernetes. Para encontrar un ejemplo, consulta [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke). + +#### Crear un agrupamiento de GKE + +Para crear un agrupamiento de GKE, primero necesitarás autenticarte utilizando el CLI de `gcloud`. Para obtener más información sobre este paso, consulta los siguientes artículos: +- [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login) +- [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference) +- [`gcloud` CLI y Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk) + +Por ejemplo: + +{% raw %} +```bash{:copy} +$ gcloud container clusters create $GKE_CLUSTER \ + --project=$GKE_PROJECT \ + --zone=$GKE_ZONE +``` +{% endraw %} + +#### Habilitar las API + +Habilita las API de Kubernetes Engine y del Registro de Contenedor. Por ejemplo: + +{% raw %} +```bash{:copy} +$ gcloud services enable \ + containerregistry.googleapis.com \ + container.googleapis.com +``` +{% endraw %} + +#### Configurar una cuenta de servicio y almacenar sus crendenciales + +Este procedimiento demuestra cómo crear la cuenta de servicio para tu integración con GKE. Aquí se explica cómo crear la cuenta, agregarle los roles, recuperar su claves y almacenarlos como un [secreto de repositorio cifrado](/actions/reference/encrypted-secrets) cifrado en base64 con el nombre de `GKE_SA_KEY`. + +1. Crea una cuenta de servicio nueva: + {% raw %} + ``` + $ gcloud iam service-accounts create $SA_NAME + ``` + {% endraw %} +1. Recupera la dirección de correo electrónico en la cuenta de servicio que acabas de crear: + {% raw %} + ``` + $ gcloud iam service-accounts list + ``` + {% endraw %} +1. Agrega roles a la cuenta de servicio. Nota: Aplica roles más restrictivos para que se acoplen a tus requisitos. + {% raw %} + ``` + $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ + --member=serviceAccount:$SA_EMAIL \ + --role=roles/container.admin \ + --role=roles/storage.admin + ``` + {% endraw %} +1. Descarga el archivo de llave JSON para la cuenta de servicio: + {% raw %} + ``` + $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL + ``` + {% endraw %} +1. Almacena la ID de proyecto como un secreto que se llame `GKE_PROJECT`: + {% raw %} + ``` + $ export GKE_SA_KEY=$(cat key.json | base64) + ``` + {% endraw %} + +#### (Opcional) Configurar kustomize +Kustomize es una herramietna opcional que se utiliza para administrar las especificaciones YAML. Después de crear un archivo de _kustomization_, el flujo de trabajo que se muestra a continuación puede utilizarse para configurar dinámicamente los campos de la imagen y agregar el resultado a `kubectl`. Para obtener más información, consulta la sección [uso de kustomize](https://github.com/kubernetes-sigs/kustomize#usage). + +### Crear un flujo de trabajo + +Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo. + +El siguiente flujo de trabajo demuestra cómo crear una imagen de contenedor y cómo subirla a GCR. Utiliza entonces las herramientas de Kubernetes (tales como `kubectl` y `kustomize`) para extraer la imagen en el despliegue del agrupamiento. + +{% raw %} +```yaml{:copy} +name: Build and Deploy to GKE + +on: + release: + types: [created] + +env: + PROJECT_ID: ${{ secrets.GKE_PROJECT }} + GKE_CLUSTER: cluster-1 # Add your cluster name here. + GKE_ZONE: us-central1-c # Add your cluster zone here. + DEPLOYMENT_NAME: gke-test # Add your deployment name here. + IMAGE: static-site + +jobs: + setup-build-publish-deploy: + name: Setup, Build, Publish, and Deploy + runs-on: ubuntu-latest + steps: + + - name: Checkout + uses: actions/checkout@v2 + + # Setup gcloud CLI + - uses: google-github-actions/setup-gcloud@v0.2.0 + with: + service_account_key: ${{ secrets.GKE_SA_KEY }} + project_id: ${{ secrets.GKE_PROJECT }} + + # Configure docker to use the gcloud command-line tool as a credential helper + - run: |- + gcloud --quiet auth configure-docker + + # Get the GKE credentials so we can deploy to the cluster + - uses: google-github-actions/get-gke-credentials@v0.2.1 + with: + cluster_name: ${{ env.GKE_CLUSTER }} + location: ${{ env.GKE_ZONE }} + credentials: ${{ secrets.GKE_SA_KEY }} + + # Build the Docker image + - name: Build + run: |- + docker build \ + --tag "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" \ + --build-arg GITHUB_SHA="$GITHUB_SHA" \ + --build-arg GITHUB_REF="$GITHUB_REF" \ + . + + # Push the Docker image to Google Container Registry + - name: Publish + run: |- + docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" + + # Set up kustomize + - name: Set up Kustomize + run: |- + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 + chmod u+x ./kustomize + + # Deploy the Docker image to the GKE cluster + - name: Deploy + run: |- + ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA + ./kustomize build . | kubectl apply -f - + kubectl rollout status deployment/$DEPLOYMENT_NAME + kubectl get services -o wide +``` +{% endraw %} + +### Recursos adicionales + +Para obtener más información sobre las herramientas que se utilizan en estos ejemplos, consulta la siguiente documentación: + +* Para encontrar un flujo de trabajo inicial completo, consulta el [flujo de trabajo de "Crear y Desplegar hacia GKE"](https://github.com/actions/starter-workflows/blob/master/ci/google.yml). +* Para ver más flujos de trabajo iniciales y el código que los acompaña, consulta los [Flujos de trabajo de ejemplo de {% data variables.product.prodname_actions %}](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/) de Google. +* El motor de personalización de YAML de Kubernetes: [Kustomize](https://kustomize.io/). +* "[Desplegar una aplicación web contenerizada](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" en la documentación de Google Kubernetes Engine. diff --git a/translations/es-ES/content/actions/guides/index.md b/translations/es-ES/content/actions/guides/index.md new file mode 100644 index 0000000000000..47d062d2b1a48 --- /dev/null +++ b/translations/es-ES/content/actions/guides/index.md @@ -0,0 +1,51 @@ +--- +title: Guías +shortTitle: Guías +intro: 'Estas guías para {% data variables.product.prodname_actions %} incluyen casos de uso y ejemplos específicos que te ayudarán a configurar los flujos de trabajo.' +redirect_from: + - /actions/guides/caching-and-storing-workflow-data + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Using-Databases-and-Services + - /actions/configuring-and-managing-workflows/using-databases-and-service-containers + - /actions/guides/using-databases-and-service-containers + - /actions/language-and-framework-guides + - /actions/language-and-framework-guides/github-actions-for-docker + - /actions/language-and-framework-guides/github-actions-for-java + - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript + - /actions/language-and-framework-guides/github-actions-for-python + - /actions/publishing-packages-with-github-actions + - /actions/building-and-testing-code-with-continuous-integration +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding +--- + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/es-ES/content/actions/guides/publishing-docker-images.md b/translations/es-ES/content/actions/guides/publishing-docker-images.md new file mode 100644 index 0000000000000..98fa73875cc59 --- /dev/null +++ b/translations/es-ES/content/actions/guides/publishing-docker-images.md @@ -0,0 +1,159 @@ +--- +title: Publicar imágenes de Docker +intro: 'Puedes publicar imágenes de Docker en un registro, tale como Docker Hub o {% data variables.product.prodname_registry %}, como parte de tu flujo de trabajo de integración continua (IC).' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/publishing-docker-images +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo que realiza una compilación de Docker y posteriormente publica las imágenes de Docker en Docker Hub o {% data variables.product.prodname_registry %}. Con un solo flujo de trabajo, puedes publicar imágenes a un solo registro o a varios de ellos. + +{% note %} + +**Nota:** Si quieres subir otro registro de terceros de Docker, el ejemplo en la sección "[Publicar imágenes en {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" puede servir como plantilla. + +{% endnote %} + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +También puede que encuentres útil el tener un entendimiento básico de lo siguiente: + +- "[Secretos cifrados](/actions/reference/encrypted-secrets)" +- "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" +- "[Configurar Docker para su uso con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)" + +### Acerca de la configuración de imágenes + +Esta guía asume que tienes una definición completa de una imagen de Docker almacenada en un repositorio de {% data variables.product.prodname_dotcom %}. Por ejemplo, tu repositorio debe contener un _Dockerfile_, y cualquier otro archivo que se necesite para realizar una compilación de Docker para crear una imagen. + +En esta guía, utilizaremos la acción `build-push-action` de Docker para compilar la imagen de Docker y cargarla a uno o más registros de Docker. Para obtener más información, consulta la sección [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images). + +{% data reusables.actions.enterprise-marketplace-actions %} + +### Publicar imágenes en Docker Hub + +{% data reusables.github-actions.release-trigger-workflow %} + +En el siguiente ejemplo de flujo de trabajo, utilizamos la acción `build-push-action` de Docker para compilar la imagen de Docker y, si la compilación es exitosa, cargar la imagen compilada a Docker Hub. + +Para hacer una carga en Docker hub, necesitarás tener una cuenta de Docker Hub y haber creado un repositorio ahí mismo. Para obtener más información, consulta la sección "[Publicar una imagen de contenedor de Docker en Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" en la documentación de Docker. + +Las opciones de `build-push-action` que se requieren para Docker Hub son: + +* `username` y `password`: Este es tu nombre de usuario y contraseña de Docker Hub. Te recomendamos almacenar tu nombre de usuario y contraseña de Docker Hub como un secreto para que no se expongan en tu archivo de flujo de trabajo. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +* `repository`: Tu repositorio de Docker hub en el formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. + +{% raw %} +```yaml +name: Publish Docker image +on: + release: + types: [published] +jobs: + push_to_registry: + name: Push Docker image to Docker Hub + runs-on: ubuntu-latest + steps: + - name: Check out the repo + uses: actions/checkout@v2 + - name: Push to Docker Hub + uses: docker/build-push-action@v1 + with: + username: ${{ secrets.DOCKER_USERNAME }} + password: ${{ secrets.DOCKER_PASSWORD }} + repository: my-docker-hub-namespace/my-docker-hub-repository + tag_with_ref: true +``` +{% endraw %} + +{% data reusables.github-actions.docker-tag-with-ref %} + +### Publicar imágenes en {% data variables.product.prodname_registry %} + +{% data reusables.github-actions.release-trigger-workflow %} + +En el flujo de trabajo de ejemplo que se encuentra a continuación, utilizamos la acción `build-push-action` para compilar la imagen de Docker y, si la compilación es exitosa, cargar la imagen compilada a {% data variables.product.prodname_registry %}. + +Las opciones de `build-push-action` requeridas para {% data variables.product.prodname_registry %} son: + +* `username`: Puedes utilizar el contexto {% raw %}`${{ github.actor }}`{% endraw %} para utilizar automáticamente el nombre de usuario del usuario que desencadenó la ejecución del flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". +* `password`: Puedes utilizar el secreto generado automáticamente `GITHUB_TOKEN` para la contraseña. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +* `registry`: Debe configurarse como `docker.pkg.github.com`. +* `repository`: Debe configurarse en el formato `OWNER/REPOSITORY/IMAGE_NAME`. Por ejemplo, para una imagen nombrada como `octo-image` almacenada en {% data variables.product.prodname_dotcom %} en `http://github.com/octo-org/octo-repo`, la opción de `repository` debe configurarse como `octo-org/octo-repo/octo-image`. + +{% raw %} +```yaml +name: Publish Docker image +on: + release: + types: [published] +jobs: + push_to_registry: + name: Push Docker image to GitHub Packages + runs-on: ubuntu-latest + steps: + - name: Check out the repo + uses: actions/checkout@v2 + - name: Push to GitHub Packages + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: my-org/my-repo/my-image + tag_with_ref: true + +``` +{% endraw %} + +{% data reusables.github-actions.docker-tag-with-ref %} + +### Publicar imágenes en Docker Hub y en {% data variables.product.prodname_registry %} + +En un solo flujo de trabajo, puedes publicar tu imagen de Docker en varios registros utilizando la acción `build-push-action` para cada uno. + +El siguiente flujo de trabajo de ejemplo utiliza los pasos de `build-push-action` de las secciones anteriores ("[Publicar imágenes en Docker Hub](#publishing-images-to-docker-hub)" y "[Publicar imágenes en {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para crear un solo flujo de trabajo que cargue ambos registros. + +{% raw %} +```yaml +name: Publish Docker image +on: + release: + types: [published] +jobs: + push_to_registries: + name: Push Docker image to multiple registries + runs-on: ubuntu-latest + steps: + - name: Check out the repo + uses: actions/checkout@v2 + - name: Push to Docker Hub + uses: docker/build-push-action@v1 + with: + username: ${{ secrets.DOCKER_USERNAME }} + password: ${{ secrets.DOCKER_PASSWORD }} + repository: my-docker-hub-namespace/my-docker-hub-repository + tag_with_ref: true + - name: Push to GitHub Packages + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: my-org/my-repo/my-image + tag_with_ref: true +``` +{% endraw %} + +El flujo de trabajo anterior revisa el repositorio de {% data variables.product.prodname_dotcom %} y utiliza la acción `build-push-action` dos veces para crear y cargar la imagen de Docker a Docker Hub y {% data variables.product.prodname_registry %}. Para ambos pasos, configura la opción `build-push-action` [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) para etiquetar automáticamente la imagen de Docker con la referencia de Git para el evento del flujo de trabajo. Este flujo de trabajo se desencadena cuando se publica un lanzamiento de {% data variables.product.prodname_dotcom %}, así que la referencia para ambos registros será la etiqueta de Git para el lanzamiento. diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md new file mode 100644 index 0000000000000..f3cb1567e47e2 --- /dev/null +++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md @@ -0,0 +1,220 @@ +--- +title: Publicar paquetes Java con Gradle +intro: Puedes usar Gradle para publicar paquetes Java en un registro como parte de tu flujo de trabajo de integración continua (CI). +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/publishing-java-packages-with-gradle +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +{% data reusables.github-actions.publishing-java-packages-intro %} + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de los archivos de flujo de trabajo y las opciones de configuración. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Java con Gradle, consulta "[Construir y probar Java con Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)". + +También puede ser útil tener un entendimiento básico de lo siguiente: + +- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)" +- "[Variables de ambiente](/actions/reference/environment-variables)" +- "[Secretos cifrados](/actions/reference/encrypted-secrets)" +- "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" + +### Acerca de la configuración del paquete + +Los campos `groupId` y `artifactId` en la sección `MavenPublication` del archivo _build.gradle_ crean un identificador único para tu paquete que los registros usan para vincular tu paquete a un registro. Esto es similar a los campos `groupId` y `artifactId` del archivo _pom.xml_ de Maven. Para obtener más información, consulta "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" en la documentación de Gradle. + +El archivo _build.gradle_ también contiene la configuración de los repositorios de administración de distribución en los que Gradle publicará los paquetes. Cada repositorio debe tener un nombre, una URL de implementación y credenciales para la autenticación. + +### Publicar paquetes en el repositorio central de Maven + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el repositorio central de Maven si se pasan las pruebas de CI. Para obtener más información acerca del evento `release`, consulta "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release)". + +Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu archivo _build.gradle_ que apunta al repositorio de tu paquete. Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _build.gradle_ podría especificar un repositorio con el nombre `"OSSRH"`. + +{% raw %} +```groovy +publishing { + ... + + repositories { + maven { + name = "OSSRH" + url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/" + credentials { + username = System.getenv("MAVEN_USERNAME") + password = System.getenv("MAVEN_PASSWORD") + } + } + } +} +``` +{% endraw %} + +Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven al ejecutar el comando `gradle publish`. También deberás proporcionar variables de entorno que contengan el nombre de usuario y la contraseña para autenticarse en el repositorio. + +En el paso de implementación, necesitarás establecer variables de entorno para el nombre de usuario y la contraseña o token que usas para autenticar en el repositorio de Maven. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + + +{% raw %} +```yaml +name: Publish package to the Maven Central Repository +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Set up Java + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Publish package + run: gradle publish + env: + MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} + MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} +``` +{% endraw %} + +{% data reusables.github-actions.gradle-workflow-steps %} +1. Ejecuta el comando `gradle publish` para publicar en el repositorio Maven `OSSRH`. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". + +### Sube paquetes al {% data variables.product.prodname_registry %} + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el {% data variables.product.prodname_registry %} si se superan las pruebas de CI. Para obtener más información acerca del evento `release`, consulta "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release)". + +Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu _build.gradle_ que apunte a {% data variables.product.prodname_registry %}. En esa configuración de repositorio, también puedes aprovechar las variables de entorno establecidas en tu ejecución de flujo de trabajo de CI. Puedes usar la variable de entorno `GITHUB_ACTOR` como nombre de usuario y puedes establecer la variable de entorno `GITHUB_TOKEN` con tu `GITHUB_TOKEN` secreto. + +El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". + +Por ejemplo, si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación. + +{% raw %} +```groovy +publishing { + ... + + repositories { + maven { + name = "GitHubPackages" + url = "https://maven.pkg.github.com/octocat/hello-world" + credentials { + username = System.getenv("GITHUB_ACTOR") + password = System.getenv("GITHUB_TOKEN") + } + } + } +} +``` +{% endraw %} + +Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven al ejecutar el comando `gradle publish`. + +{% raw %} +```yaml +name: Publish package to GitHub Packages +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Publish package + run: gradle publish + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} + +{% data reusables.github-actions.gradle-workflow-steps %} +1. Ejecuta el comando `gradle publish` comando para publicar en {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". + +### Publicar paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %} + +Puedes publicar tus paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %} al configurar cada uno de ellos en tu archivo _build.gradle_. + +Asegúrate de que tu archivo _build.gradle_ incluya un repositorio para tu repositorio {% data variables.product.prodname_dotcom %} y para tu proveedor de repositorios centrales de Maven. + +Por ejemplo, si implementas el repositorio central a través del proyecto de alojamiento OSSRH, es posible que desees especificarlo en un repositorio de administración de distribución con el `name` establecido en `OSSRH`. Si implementas para {% data variables.product.prodname_registry %}, es posible que desees especificarlo en un repositorio de administración de distribución con el `name` establecido en `GitHubPackages`. + +Si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación. + +{% raw %} +```groovy +publishing { + ... + + repositories { + maven { + name = "OSSRH" + url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/" + credentials { + username = System.getenv("MAVEN_USERNAME") + password = System.getenv("MAVEN_PASSWORD") + } + } + maven { + name = "GitHubPackages" + url = "https://maven.pkg.github.com/octocat/hello-world" + credentials { + username = System.getenv("GITHUB_ACTOR") + password = System.getenv("GITHUB_TOKEN") + } + } + } +} +``` +{% endraw %} + +Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven y {% data variables.product.prodname_registry %} al ejecutar el comando `gradle publish`. + +{% raw %} +```yaml +name: Publish package to the Maven Central Repository and GitHub Packages +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Set up Java + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Publish to the Maven Central Repository + run: gradle publish + env: + MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} + MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} + +{% data reusables.github-actions.gradle-workflow-steps %} +1. Ejecuta el comando `gradle publish` para publicar en el repositorio Maven `OSSRH` y {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md new file mode 100644 index 0000000000000..64f52a2e57c52 --- /dev/null +++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md @@ -0,0 +1,211 @@ +--- +title: Publicar paquetes Java con Maven +intro: Puedes usar Maven para publicar paquetes Java en un registro como parte de tu flujo de trabajo de integración continua (CI). +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/language-and-framework-guides/publishing-java-packages-with-maven +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +{% data reusables.github-actions.publishing-java-packages-intro %} + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de los archivos de flujo de trabajo y las opciones de configuración. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Java con Maven, consulta "[Construir y probar Java con Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)". + +También puede ser útil tener un entendimiento básico de lo siguiente: + +- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)" +- "[Variables de ambiente](/actions/reference/environment-variables)" +- "[Secretos cifrados](/actions/reference/encrypted-secrets)" +- "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" + +### Acerca de la configuración del paquete + +Los campos `groupld` y `artifactId` del archivo _pom.xml_ crea un identificador único para tu paquete que los registros usan para vincular tu paquete a un registro. Para obtener más información, consulta [Guía para cargar artefactos en el repositorio central](http://maven.apache.org/repository/guide-central-repository-upload.html) en la documentación de Apache Maven. + +El archivo _pom.xml_ también contiene la configuración de los repositorios de administración de distribución en los que Maven implementará los paquetes. Cada repositorio debe tener un nombre y una URL de implementación. La autenticación para estos repositorios se puede configurar en el archivo _.m2/settings.xml_ del directorio de inicio del usuario que ejecuta Maven. + +Puedes usar la acción `setup-java` para configurar el repositorio de implementación, así como la autenticación para ese repositorio. Para obtener más información, consulta [`setup-java`](https://github.com/actions/setup-java). + +### Publicar paquetes en el repositorio central de Maven + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el repositorio central de Maven si se pasan las pruebas de CI. Para obtener más información acerca del evento `release`, consulta "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release)". + +En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión dada del JDK en el `PATH`, pero también configura un Maven _settings.xml_ para publicar paquetes. Por defecto, el archivo de configuraciones se configurará para {% data variables.product.prodname_registry %}, pero se puede configurar para que se implemente en otro registro de paquetes, como el repositorio central de Maven. Si ya tienes un repositorio de administración de distribución configurado en _pom.xml_, puedes especificar que `id` durante la acción de invocación `setup-java`. + +Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _pom.xml_ podría especificar un repositorio de administración de distribución con el `id` de `ossrh`. + +{% raw %} +```xml + + ... + + + ossrh + Central Repository OSSRH + https://oss.sonatype.org/service/local/staging/deploy/maven2/ + + + +``` +{% endraw %} + +Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven especificando la administración del repositorio `id` para la acción `setup-java`. También deberás proporcionar variables de entorno que contengan el nombre de usuario y la contraseña para autenticarse en el repositorio. + +En el paso de implementación, necesitarás establecer las variables de entorno para el nombre de usuario con el que te autenticaste en el repositorio y para el secreto que hayas configurado con la contraseña o el token con que autenticarse. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + + +{% raw %} +```yaml +name: Publish package to the Maven Central Repository +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Set up Maven Central Repository + uses: actions/setup-java@v1 + with: + java-version: 1.8 + server-id: ossrh + server-username: MAVEN_USERNAME + server-password: MAVEN_PASSWORD + - name: Publish package + run: mvn --batch-mode deploy + env: + MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} + MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} +``` +{% endraw %} + +Este flujo de trabajo realiza los siguientes pasos: + +1. Verifica una copia del repositorio del proyecto. +1. Configura el JDK de Java y también el archivo _settings. xml_ de Maven para agregarle autenticación al repositorio de `ossrh` utilizando las variables de entorno `MAVEN_USERNAME` y `MAVEN_PASSWORD`. +1. {% data reusables.github-actions.publish-to-maven-workflow-step %} + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". + +### Sube paquetes al {% data variables.product.prodname_registry %} + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el {% data variables.product.prodname_registry %} si se superan las pruebas de CI. Para obtener más información acerca del evento `release`, consulta "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release)". + +En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión determinada del JDK en el `PATH` y configura un _settings.xml_ de Maven para publicar el paquete en el {% data variables.product.prodname_registry %}. El _settings.sml_ generado define la autenticación para un servidor con una `id` de `github`, utilizando la variable de entorno `GITHUB_ACTOR` como nombre de usuario y la variable de entorno `GITHUB_TOKEN` como contraseña. + +El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". + +Para un proyecto basado en Maven, puedes hacer uso de estas configuraciones creando un repositorio de distribución en tu archivo _pom.xml_ con una `id` de `github` que apunta a tu extremo {% data variables.product.prodname_registry %}. + +Por ejemplo, si tu organización se llama "octocat", y tu repositorio se llama "hello-world", la configuración de {% data variables.product.prodname_registry %} en _pom.xml_ sería parecida al siguiente ejemplo. + +{% raw %} +```xml + + ... + + + github + GitHub Packages + https://maven.pkg.github.com/octocat/hello-world + + + +``` +{% endraw %} + +Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en {% data variables.product.prodname_registry %} haciendo uso del _settings.xml_ generado automáticamente. + +{% raw %} +```yaml +name: Publish package to GitHub Packages +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Publish package + run: mvn --batch-mode deploy + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} + +Este flujo de trabajo realiza los siguientes pasos: + +1. Verifica una copia del repositorio del proyecto. +1. Configura el JDK de Java y configura automáticamente el archivo _settings.xml_ de Maven para agregar autenticación para que el repositorio `github` de Maven utilice la variable de entorno `GITHUB_TOKEN`. +1. {% data reusables.github-actions.publish-to-packages-workflow-step %} + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". + +### Publicar paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %} + +Puedes publicar tus paquetes en el repositorio central de Maven y en el {% data variables.product.prodname_registry %} usando la acción `setup-java` para cada registro. + +Asegúrate de que tu archivo _pom.xml_ incluya un repositorio de administración de distribución para tu repositorio de {% data variables.product.prodname_dotcom %} y para tu proveedor de repositorios centrales de Maven. Por ejemplo, si implementas el repositorio central a través del proyecto de alojamiento de OSSRH, es posible que desees especificarlo en un repositorio de administración de distribución con la `id` establecida en `ossrh`, y que desees especificar el {% data variables.product.prodname_registry %} en un repositorio de administración de distribución con la `id` establecida en `github`. + +{% raw %} +```yaml +name: Publish package to the Maven Central Repository and GitHub Packages +on: + release: + types: [created] +jobs: + publish: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Set up Java for publishing to Maven Central Repository + uses: actions/setup-java@v1 + with: + java-version: 1.8 + server-id: ossrh + server-username: MAVEN_USERNAME + server-password: MAVEN_PASSWORD + - name: Publish to the Maven Central Repository + run: mvn --batch-mode deploy + env: + MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} + MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} + - name: Set up Java for publishing to GitHub Packages + uses: actions/setup-java@v1 + with: + java-version: 1.8 + - name: Publish to GitHub Packages + run: mvn --batch-mode deploy + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} + +Este flujo de trabajo llama a la acción `setup-java` dos veces. Cada vez que la acción `setup-java` se ejecuta, sobrescribe el archivo _settings.xml_ de Maven para publicar paquetes. Para la autenticación en el repositorio, el archivo _settings.xml_ hace referencia a la `id` del repositorio de administración de distribución y al nombre de usuario y contraseña. + +Este flujo de trabajo realiza los siguientes pasos: + +1. Verifica una copia del repositorio del proyecto. +1. Llama al `setup-java` la primera vez. Esto configura el archivo _settings.xml_ de Maven para el repositorio `ossrh` y establece las opciones de autenticación en las variables de entorno que se definen en el siguiente paso. +1. {% data reusables.github-actions.publish-to-maven-workflow-step %} +1. Llama al `setup-java` la segunda vez. Esto configura automáticamente el archivo _settings.xml_ de Maven para el {% data variables.product.prodname_registry %}. +1. {% data reusables.github-actions.publish-to-packages-workflow-step %} + + Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". diff --git a/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md new file mode 100644 index 0000000000000..fef802a477858 --- /dev/null +++ b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md @@ -0,0 +1,230 @@ +--- +title: Publicar paquetes Node.js +intro: Puedes publicar paquetes Node.js en un registro como parte de tu flujo de trabajo de integración continua (CI). +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages + - /actions/language-and-framework-guides/publishing-nodejs-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Esta guía te muestra cómo crear un flujo de trabajo que publique paquetes Node.js en el {% data variables.product.prodname_registry %} y registros npm después de que se aprueben las pruebas de integración continua (CI). Con un solo flujo de trabajo, puedes publicar paquetes en un solo registro o varios registros. + +### Prerrequisitos + +Te recomendamos que tengas una comprensión básica de las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Node.js, consulta "[Usar Node.js con las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)". + +También puede ser útil tener un entendimiento básico de lo siguiente: + +- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)" +- "[Variables de ambiente](/actions/reference/environment-variables)" +- "[Secretos cifrados](/actions/reference/encrypted-secrets)" +- "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" + +### Acerca de la configuración del paquete + + Los campos `Nombre` y `Versión` en el archivo *package.json* crean un identificador único que los registros usan para vincular tu paquete a un registro. Puedes agregar un resumen para la página de descripción del paquete al incluir un campo `Descripción` en el archivo *package.json*. Para obtener más información, consulta "[Crear un archivo package.json](https://docs.npmjs.com/creating-a-package-json-file) y [Crear módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)"en la documentación de npm. + +Cuando existe un archivo *.npmrc* local y tiene un valor especificado de `registro`, el comando `npm publish` usa el registro configurado en el archivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %} + +Puedes especificar la versión de Node.js instalada en el ejecutor utilizando la acción `setup-node`. + +Si agregas pasos en tu flujo de trabajo para configurar los campos `publishConfig` en tu archivo *package.json*, no es necesario que especifiques la Url del registro utilizando la acción `setup-node`, pero se limitará a publicar el paquete en un registro. Para obtener más información, consulta "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" en la documentación de npm. + +### Publicar paquetes en el registro npm + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el registro npm si se pasan las pruebas de CI. + +Para realizar operaciones autenticadas frente al registro npm en tu flujo de trabajo, necesitarás almacenar tu token de autenticación npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +Por defecto, npm usa el campo `Nombre` del archivo *package.json* para determinar el registro npm. Al publicar en un espacio de nombres global, solo necesitas incluir el nombre del paquete. Por ejemplo, publicarías un paquete llamado `npm-hello-world-test` en `https://www.npmjs.com/package/npm-hello-world-test`. + +Si estás publicando un paquete que incluye un prefijo de alcance, incluye el ámbito en el nombre de tu archivo *package.json*. Por ejemplo, si el prefijo del ámbito npm es octocat y el nombre del paquete es hello-world, el `nombre` en tu archivo *package.json* debe ser `@octocat/hello-world`. Si su paquete npm usa un prefijo de ámbito y el paquete es público, debes usar la opción `npm publish --access public`. Esta es una opción que npm requiere para evitar que alguien publique un paquete privado involuntariamente. + +Este ejemplo almacena el secreto `NPM_TOKEN` en la variable de entorno `NODE_AUTH_TOKEN`. Cuando la acción `setup-node` crea un archivo *.npmrc*, hace referencia al token de la variable de entorno `NODE_AUTH_TOKEN`. + +{% raw %} +```yaml +name: Node.js Package +on: + release: + types: [created] +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + # Configura el archivo .npmrc para publicar en npm + - uses: actions/setup-node@v1 + with: + node-version: '12.x' + registry-url: 'https://registry.npmjs.org' + - run: npm install + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} +``` +{% endraw %} + +En el ejemplo anterior, la acción `setup-node` crea un archivo *.npmrc* en el ejecutor con el siguiente contenido: + +``` +//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} +registry=https://registry.npmjs.org/ +always-auth=true +``` + +### Sube paquetes al {% data variables.product.prodname_registry %} + +Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cada vez que se produce el evento `lanzamiento` con tipo `creado`. El flujo de trabajo publica el paquete en el {% data variables.product.prodname_registry %} si se superan las pruebas de CI. + +#### Configurar el repositorio de destino + +Si no proporcionas la clave del `repository` en tu archivo *package.json*, entonces el {% data variables.product.prodname_registry %} publicará un paquete en el repositorio de {% data variables.product.prodname_dotcom %} que especifiques en el campo `name` del archivo *package.json*. Por ejemplo, un paquete denominado `@my-org/test` se publicará en el repositorio `my-org/test` de {% data variables.product.prodname_dotcom %}. + +Sin embargo, si no proporcionas la clave del `repository`, entonces el repositorio en esa clave se utilizará como el registro de npm de destino para el {% data variables.product.prodname_registry %}. Por ejemplo, el publicar el siguiente *package.json* dará como resultado un paquete denominado `my-amazing-package` que se publicará en el repositorio `octocat/my-other-repo` de {% data variables.product.prodname_dotcom %}. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Autenticarse en el repositorio de destino + +Para autenticarte en el registro de {% data variables.product.prodname_registry %} en tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN` desde tu repositorio. Este se crea automáticamente y tiene permisos tanto de _lectura_ como de _escritura_ para los paquetes en el repositorio en donde se ejecuta el flujo de trabajo. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)". + +Si quieres publicar tu paquete en un repositorio diferente, debes utilizar un token de acceso personal (PAT) que tenga permisos de escritura en los paquetes del repositorio destino. Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)". + +#### Ejemplo de flujo de trabajo + +Este ejemplo almacena el secreto `GITHUB_TOKEN` en la variable de entorno `NODE_AUTH_TOKEN`. Cuando la acción `setup-node` crea un archivo *.npmrc*, hace referencia al token de la variable de entorno `NODE_AUTH_TOKEN`. + +{% raw %} +```yaml +name: Node.js Package +on: + release: + types: [created] +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + # Setup .npmrc file to publish to GitHub Packages + - uses: actions/setup-node@v1 + with: + node-version: '12.x' + registry-url: 'https://npm.pkg.github.com' + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' + - run: npm install + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} + +La acción `setup-node` crea un archivo *.npmrc* en el ejecutor. Cuando utilizas la entrada `scope` a la acción `setup-node`, el archivo *.npmrc* incluye el prefijo de alcance. Por defecto, la acción `setup-node` establece el ámbito en el archivo *.npmrc* en la cuenta que contiene ese archivo de flujo de trabajo. + +``` +//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} +@octocat:registry=https://npm.pkg.github.com +always-auth=true +``` + +### Publicar paquetes mediante yarn + +Si usas el gestor de paquetes Yarn, puedes instalar y publicar paquetes mediante Yarn. + +{% raw %} +```yaml +name: Node.js Package +on: + release: + types: [created] +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + # Setup .npmrc file to publish to npm + - uses: actions/setup-node@v1 + with: + node-version: '12.x' + registry-url: 'https://registry.npmjs.org' + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' + - run: yarn + - run: yarn publish + env: + NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} +``` +{% endraw %} + +### Publicar paquetes en npm y {% data variables.product.prodname_registry %} + +{% note %} + +**Nota:** Si necesitas publicar en los registros que tienen diferentes prefijos de ámbito, deberás modificar el archivo *package.json* en el ejecutor para cambiar el prefijo de ámbito. Por ejemplo, si publicas un paquete en el ámbito `@mona` para npm y `@octocat` para {% data variables.product.prodname_registry %}, puedes reemplazar el ámbito `@mona` por `@octocat` en el archivo *package.json* del ejecutor después de publicar en npm y antes de publicar en {% data variables.product.prodname_registry %}. + +{% endnote %} + +Puedes publicar tus paquetes tanto en el registro npm como en {% data variables.product.prodname_registry %} mediante la acción `setup-node` para cada registro. + +Si publicas un paquete en ambos registros, tendrás que asegurarte de que tu prefijo de ámbito en npm coincida con tu nombre de usuario u organización de {% data variables.product.prodname_dotcom %}. Para publicar paquetes en un registro público con un prefijo de ámbito, puedes utilizar el comando `npm publish --access public`. Para obtener más información, consulta [`npm-scope`](https://docs.npmjs.com/misc/scope) y "[Crear y publicar paquetes públicos con ámbitos](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)" en la documentación de npm. + +Asegúrate de que tu archivo *package.json* incluya el ámbito de tu repositorio de {% data variables.product.prodname_dotcom %} y el registro de npm. Por ejemplo, si planeas publicar un paquete en el repositorio `octocat/npm-hello-world-test` en {% data variables.product.prodname_dotcom %} y https://www.npmjs. om/package/@octocat/npm-hello-world-test, el nombre en tu archivo *package.json* debería ser `"name": "@octocat/npm-hello-world-test"`. + +Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +Cuando utilizas la entrada `scope` a la acción `setup-node`, la acción crea un archivo *.npmrc* que incluye el prefijo de alcance. Por defecto, la acción `setup-node` establece el ámbito en el archivo *.npmrc* al usuario u organización que posee el archivo de flujo de trabajo. + +Este flujo de trabajo llama a la acción `setup-node` dos veces. Cada vez que se ejecuta la acción `setup-node`, sobrescribe el archivo *.npmrc*. El archivo *.npmrc* hace referencia al token que te permite realizar operaciones autenticadas frente al registro del paquete desde la variable de entorno `NODE_AUTH_TOKEN`. El flujo de trabajo establece la variable de entorno `NODE_AUTH_TOKEN` cada vez que se ejecuta el comando `npm publish`, primero con un token para publicar en el (`NPM_TOKEN`) de npm y luego con un token para publicar en el {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). + +{% raw %} +```yaml +name: Node.js Package +on: + release: + types: [created] +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + # Setup .npmrc file to publish to npm + - uses: actions/setup-node@v1 + with: + node-version: '10.x' + registry-url: 'https://registry.npmjs.org' + - run: npm install + # Publish to npm + - run: npm publish --access public + env: + NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} + # Setup .npmrc file to publish to GitHub Packages + - uses: actions/setup-node@v1 + with: + registry-url: 'https://npm.pkg.github.com' + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' + # Publish to GitHub Packages + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }} +``` +{% endraw %} diff --git a/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md new file mode 100644 index 0000000000000..69e2647f9ebf1 --- /dev/null +++ b/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -0,0 +1,44 @@ +--- +title: Configurar la integración contínua utilizando plantillas de flujo de trabajo +shortTitle: Configurar la IC utilizando plantillas +intro: Puedes configurar una integración continua para tu proyecto mediante el uso de una plantilla de flujo de trabajo que coincida con el idioma y las herramientas que deseas utilizar. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/setting-up-continuous-integration-using-github-actions + - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions + - /actions/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions + - /actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Cualquier persona con permiso de escritura en un repositorio puede configurar la integración continua (CI) utilizando {% data variables.product.prodname_actions %}. + +Una vez que hayas configurado la IC, puedes personalizar el flujo de trabajo para satisfacer tus necesidades. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. Busca la plantilla que coincida con el idioma y las herramientas que deseas utilizar; a continuación, haz clic en **Configurar este flujo de trabajo**. ![Configurar el botón de flujo de trabajo](/assets/images/help/repository/setup-workflow-button.png) +5. Haz clic en **Iniciar confirmación**. ![Botón Start commit (Iniciar confirmación)](/assets/images/help/repository/start-commit.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +Una vez que se hace una inserción en tu repositorio, puedes seguir el estado y los registros detallados de tu flujo de trabajo de integración continua ejecutado en {% data variables.product.prodname_dotcom %} y recibir notificaciones personalizadas. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)" y "[Administrar una ejecución de flujo de trabajo](/articles/managing-a-workflow-run)". + +{% data reusables.repositories.actions-workflow-status-badge-into %} + +Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +### Further reading + +- "[Acerca de la integración continua](/articles/about-continuous-integration)" +- "[Administrar una ejecución de flujo de trabajo](/articles/managing-a-workflow-run)" +{% if currentVersion == "free-pro-team@latest" %} +- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md new file mode 100644 index 0000000000000..c50cc4c73222d --- /dev/null +++ b/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -0,0 +1,253 @@ +--- +title: Almacenar los datos de los flujos de trabajo como artefactos +shortTitle: Almacenar artefactos de los flujos de trabajo +intro: Los artefactos te permiten compartir datos entre puestos en un flujo de trabajo y almacenar los datos una vez que se ha completado ese flujo de trabajo. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/persisting-workflow-data-using-artifacts + - /GitHub/Automating-Your-Workflow-with-GitHub-Actions/Persisting-Workflow-Data-using-Artifacts + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Persisting-Workflow-Data-using-Artifacts + - /actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los artefactos de flujo de trabajo + +Los artefactos te permiten hacer datos persistentes después de que se complete un job y comparten estos datos con otro job en el mismo flujo de trabajo. Un artefacto es un archivo o recopilación de archivos producidos durante una ejecución de flujo de trabajo. Por ejemplo, puedes utilizar artefactos para guardar tu compilación y probar el resultado después de que haya terminado una ejecución de flujo de trabajo. + +{% data reusables.github-actions.artifact-log-retention-statement %} El periodo de retención para una solicitud de cambios se reinicia cada vez que alguien sube una confirmación nueva en dicha solicitud. + +Estos son algunos de los artefactos comunes que puedes subir: + +- Archivos de registro y vaciados de memoria +- Resultados de prueba, fallas y capturas de pantalla +- Archivos binarios o comprimidos +- Resultados de la prueba de rendimiento y resultados de cobertura del código + +{% if currentVersion == "free-pro-team@latest" %} + +Almacenar artefactos consume espacio de almacenamiento en {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Administrar la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)". + +{% else %} + +Los artefactos caducan automáticamente después de 90 días, pero siempre puedes reclamar el almacenamiento utilizado de {% data variables.product.prodname_actions %} si borras artefactos antes de que caduquen en {% data variables.product.product_name %}. + +{% endif %} + +Los artefactos se cargan durante una ejecución de flujo de trabajo y puedes ver el nombre y tamaño de estos en la IU. Cuando se descarga un artefacto utilizando la IU de {% data variables.product.product_name %}, todos los archivos que se hayan subido de manera individual como parte del mismo se comprimirán en un solo archivo. Esto significa que los costos se calcularán con base en el tamaño del artefacto cargado y no en aquél del archivo comprimido. + +{% data variables.product.product_name %} proporciona dos acciones que puedes usar para cargar y descargar artefactos de construcción. Para obtener más información, consulta las acciones {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) y [download-artifact](https://github.com/actions/download-artifact){% else %} `actions/upload-artifact` y `download-artifact` en {% data variables.product.product_location %}{% endif %}. + +Para compartir datos entre jobs: + +* **Cargar archivos**: Asigna un nombre al archivo cargado y sube los datos antes de que termine el job. +* **Descargar archivos**: Solo puedes descargar artefactos que se hayan subido durante la misma ejecución del flujo de trabajo. Cuando descargas un archivo, puedes referenciarlo por su nombre. + +Los pasos de un job comparten el mismo ambiente en la máquina ejecutora, pero se ejecutan en su propio proceso individual. Para pasar datos entre pasos en un job, puedes usar entradas y salidas. Para obtener más información sobre entradas y salidas, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)". + +### Cargar artefactos de construcción y prueba + +Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu código. Para obtener más información acerca de cómo utilizar {% data variables.product.prodname_actions %} para realizar la IC, consulta la sección "[Acerca de la integración contínua](/articles/about-continuous-integration)". + +El resultado de la construcción y la prueba de tu código frecuentemente produce archivos que puedes usar para depurar fallas de prueba y códigos de producción que puedes implementar. Puedes configurar un flujo de trabajo para construir y probar el código subido a tu repositorio e informar un estado satisfactorio o de falla. Puedes cargar los resultados de construcción y prueba para usar en implementaciones, pruebas de depuración fallidas o fallos, y para visualizar la cobertura del conjunto de prueba. + +Puedes usar la acción `upload-Artifact` para cargar artefactos. Cuando cargues un artefacto, puedes especificar un archivo sencillo o un directorio, o varios archivos o directorios. También puedes excluir ciertos archivos o directorios y utilizar patrones de comodín. Te recomendamos que proporciones un nombre para cada artefacto pero, si no se lo das, entonces el nombre predeterminado que se utilizará será `artifact`. Para obtener más información sobre la sintaxis, consulta la acción {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact){% else %} `actions/upload-artifact` en {% data variables.product.product_location %}{% endif %}. + +#### Ejemplo + +Por ejemplo, tu repositorio o una aplicación web podrían contener archivos de SASS y TypeScript que debes convertir a CSS y JavaScript. Teniendo en cuenta que tu configuración de construcción envía los archivos compilados al directorio `dist`, puedes implementar los archivos en el directorio `dist` para tu servidor de aplicación web si todas las pruebas se completaron satisfactoriamente. + +``` +|-- hello-world (repository) +| └── dist +| └── tests +| └── src +| └── sass/app.scss +| └── app.ts +| └── output +| └── test +| +``` + +En este ejemplo se muestra cómo crear un flujo de trabajo para un proyecto Node.js que construye el código en el directorio `src` y ejecuta las pruebas en el directorio `tests`. Puedes suponer que la ejecución `npm test` produce un informe de cobertura de código denominado `code-coverage.html` almacenada en el directorio `output/test/`. + +El flujo de trabajo carga los artefactos de producción en el directorio `dist`, pero excluye cualquier archivo de markdown. También carga el reporte `code-coverage.html` como otro artefacto. + +```yaml +name: Node CI + +on: [push] + +jobs: + build_and_test: + runs-on: ubuntu-latest + steps: + - name: Checkout repository + uses: actions/checkout@v2 + - name: npm install, build, and test + run: | + npm install + npm run build --if-present + npm test + - name: Archive production artifacts + uses: actions/upload-artifact@v2 + with: + name: dist-without-markdown + path: | + dist + !dist/**/*.md + - name: Archive code coverage results + uses: actions/upload-artifact@v2 + with: + name: code-coverage-report + path: output/test/code-coverage.html +``` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Configurar un periodo de retención de artefactos personalizado + +Puedes definir un periodo de retención personalizado para los artefactos indivudales que crea un flujo de trabajo. Cuando utilices un flujo de trabajo para crear un artefacto nuevo, puedes utilizar `retention-days` con la acción `upload-artifact`. Este ejemplo ilustra cómo configurar un periodo de retención personalizado de 5 días para el artefacto que se llama `my-artifact`: + +``` + - name: 'Upload Artifact' + uses: actions/upload-artifact@v2 + with: + name: my-artifact + path: my_file.txt + retention-days: 5 +``` + +El valor `retention-days` no puede exceder el límite de retención que configuró el repositorio, organización o empresa. +{% endif %} + +### Descargar o eliminar artefactos + +Durante una ejecución de flujo de trabajo, puedes utilizar la acción [`download-artifact`](https://github.com/actions/download-artifact) para descargar los artefactos que se cargaron previamente en la misma ejecución de flujo de trabajo. + +Después de que se haya completado una ejecución de flujo de trabajo, puedes descargar o borrar los artefactos en {% data variables.product.prodname_dotcom %} o utilizando la API de REST. Para obtener más información, consulta las secciones "[Descargar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)", "[eliminar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/removing-workflow-artifacts)", y la "[API de REST de Artefactos](/rest/reference/actions#artifacts)". + +#### Descargar artefactos durante una ejecución de flujo de trabajo + +La acción [`actions/download-artifact`](https://github.com/actions/download-artifact) puede utilizarse para descargar artefactos que se hayan cargado previamente durante una ejecución de flujo de trabajo. + +{% note %} + +**Nota:** Solo podrás descargar los artefactos que se hayan cargado durante la misma ejecución de flujo de trabajo. + +{% endnote %} + +Especificar el nombre de un artefacto para descargar un artefacto individual. Si cargaste un artefacto sin especificar un nombre, el nombre predeterminado de éste será `artifact`. + +```yaml +- name: Download a single artifact + uses: actions/download-artifact@v2 + with: + name: my-artifact +``` + +También puedes descargar todos los artefactos en una ejecución de flujo de trabajo si no especificas un nombre para éstos. Esto puede ser útil si estás trabajando con muchos artefactos. + +```yaml +- name: Download all workflow run artifacts + uses: actions/download-artifact@v2 +``` + +Si descargas todos los artefactos de una ejecución de flujo de trabajo, se creará un directorio para cada uno de ellos utilizando su nombre. + +Para obtener más información sobre la sintaxis, consulta la acción {% if currentVersion == "free-pro-team@latest" %}[actions/download-artifact](https://github.com/actions/download-artifact){% else %} `actions/download-artifact` en {% data variables.product.product_location %}{% endif %}. + +### Pasar datos entre jobs en un flujo de trabajo + +Puedes usar las acciones `upload-artifact` y `download-artifact` para compartir datos entre jobs en un flujo de trabajo. Este flujo de trabajo de ejemplo ilustra cómo pasar datos entre jobs en el mismo flujo de trabajo. Para obtener más información, consulta las acciones {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) y [download-artifact](https://github.com/actions/download-artifact){% else %} `actions/upload-artifact` y `download-artifact` en {% data variables.product.product_location %}{% endif %}. + +Los jobs que dependen de los artefactos de un trabajo anterior deben esperar que el trabajo dependiente se complete exitosamente. Este flujo de trabajo usa la palabra clave `needs` para garantizar que `job_1`, `job_2` y `job_3` se ejecuten secuencialmente. Por ejemplo, `job_2` requiere `job_1` mediante la sintaxis `needs: job_1`. + +El job 1 realiza estos pasos: +- Realiza un cálculo matemático y guarda el resultado en un archivo de texto llamado `math-homework.txt`. +- Utiliza la acción `upload-artifact` para cargar el archivo `math-homework.txt` con el nombre de archivo `homework`. + +El job 2 usa el resultado del trabajo anterior: +- Descarga el artefacto `homework` cargado en el trabajo anterior. De manera predeterminada, la acción `download-artifact` descarga artefactos en el directorio del espacio de trabajo que ejecuta el paso. Puedes utilizar el parámetro de entrada `path` para especificar un directorio de descarga diferente. +- Lee el valor en el archivo `math-homework.txt`, realiza un cálculo matemático, y guarda el resultado en `math-homework.txt` nuevamente, sobreescribiendo su contenido. +- Carga el archivo `math-homework.txt`. Esta carga sobreescribe el artefacto que se cargó previamente, ya que comparten el mismo nombre. + +El job 3 muestra el resultado cargado en el trabajo anterior: +- Descarga el artefacto `homework`. +- Imprime el resultado de la ecuación matemática en el registro. + +La operación matemática completa realizada en este ejemplo de flujo de trabajo es `(3 + 7) x 9 = 90`. + +```yaml +name: Share data between jobs + +on: [push] + +jobs: + job_1: + name: Add 3 and 7 + runs-on: ubuntu-latest + steps: + - shell: bash + run: | + expr 3 + 7 > math-homework.txt + - name: Upload math result for job 1 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt + + job_2: + name: Multiply by 9 + needs: job_1 + runs-on: windows-latest + steps: + - name: Download math result for job 1 + uses: actions/download-artifact@v2 + with: + name: homework + - shell: bash + run: | + value=`cat math-homework.txt` + expr $value \* 9 > math-homework.txt + - name: Upload math result for job 2 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt + + job_3: + name: Display results + needs: job_2 + runs-on: macOS-latest + steps: + - name: Download math result for job 2 + uses: actions/download-artifact@v2 + with: + name: homework + - name: Print the final result + shell: bash + run: | + value=`cat math-homework.txt` + echo The result is $value +``` + +La ejecución de flujo de trabajo archivará cualquier artefacto que haya generado. Para obtener más información sobre cómo descargar los artefactos archivados, consulta la sección "[Descargar artefactos de flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Flujo de trabajo que pasa datos entre jobs para realizar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} +![Flujo de trabajo que pasa datos entre jobs para realizar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Further reading + +- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)". + +{% endif %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md new file mode 100644 index 0000000000000..1f1f621acf933 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -0,0 +1,139 @@ +--- +title: Acerca de los ejecutores autoalojados +intro: 'Puedes alojar tus propios ejecutores y personalizar el entorno utilizado para ejecutar trabajos en tus flujos de trabajo de {% data variables.product.prodname_actions %}.' +redirect_from: + - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners + - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los ejecutores autoalojados + +{% data reusables.github-actions.self-hosted-runner-description %} Los ejecutores auto-hospedados pueden ser físicos, virtuales, estar en un contenedor, en los servidores del usuario, o en la nube. + +Puedes agregar ejecutores auto-hospedados en varios niveles dentro de la jerarquía de administración: +- Los ejecutores a nivel de repositorio están dedicados a un solo repositorio. +- Los ejecutores a nivel de organización pueden procesar jobs para varios repositorios dentro de una organización. +- Los ejecutores a nivel de empresa puede asignarse a varias organizaciones en una cuenta empresarial. + +La máquina de tu ejecutor se conecta a{% data variables.product.product_name %} utilizando la aplicación para ejecutores auto-hospedados de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Cuando se lanza una nueva versión, la aplicación del ejecutor se actualiza automáticamente cuando se asigna un job al ejecutor, o dentro de una semana de lanzamiento si dicho ejecutor no se ha asignado a ningún job. + +{% data reusables.github-actions.self-hosted-runner-auto-removal %} + +Para obtener más información acerca de la instalación y el uso de los ejecutores auto-alojados, consulta la sección "[Agregar ejecutores auto-alojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores auto-alojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)". + +### Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados + +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen una manera más rápida y sencilla de ejecutar tus flujos de trabajo, mientras que estos son una manera altamente configurable de ejecutar flujos de trabajo en tu propio entorno personalizado. + +**Ejecutores alojados en {% data variables.product.prodname_dotcom %}:** +- Reciben actualizaciones automáticas para el sistema operativo, paquetes y herramientas pre-instalados, y la aplicación del ejecutor auto-hospedado. +- Son administrados y mantenidos por {% data variables.product.prodname_dotcom %}. +- Proporcionan una instancia limpia para cada ejecución de trabajo. +- Usan minutos libres en tu plan de {% data variables.product.prodname_dotcom %}, con tarifas por minuto aplicadas después de superar los minutos libres. + +**Ejecutores auto-hospedados:** +- Reciben actualizaciones automáticas únicamente para la aplicación del ejecutor auto-hospedado. Eres responsable de actualizar el sistema operativo y el resto del software. +- Puedes usar los servicios en la nube o las máquinas locales que ya pagas. +- Son personalizables para tu hardware, sistema operativo, software y requisitos de seguridad. +- No es necesario tener una instancia limpia para cada ejecución de trabajo. +- Son de uso gratuito con las {% data variables.product.prodname_actions %}, pero eres responsable del costo de mantener tus máquinas de ejecutores. + +### Requisitos para máquinas de ejecutores autoalojados + +Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con estos requisitos: + +* Puedes instalar y ejecutar la aplicación del ejecutor autoalojado en la máquina. Para obtener más información, consulta "[Sistemas operativos compatibles para ejecutores autoalojados](#supported-operating-systems-for-self-hosted-runners)." +* La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." +* La máquina tiene suficientes recursos de hardware para el tipo de flujos de trabajo que planeas ejecutar. La propia aplicación del ejecutor autoalojado solo requiere unos recursos mínimos. +* Si quieres ejecutar flujos de trabajo que usan acciones del contenedor Docker o contenedores de servicio, debes usar una máquina Linux y Docker debe estar instalado. + +### Límites de uso + +Hay algunos límites para el uso de las {% data variables.product.prodname_actions %} cuando se utilizan ejecutores auto-hospedados. Estos límites están sujetos a cambios. + +{% data reusables.github-actions.usage-workflow-run-time %} +- **Tiempo de cola de espera para el job** - Cada job para ejecutores auto-hospedados puede ponerse en cola de espera por un máximo de 24 horas. Si un ejecutor auto-hospedado no comienza a ejecutar el job dentro de este límite de tiempo, dicho job se terminará y no se podrá completar. +{% data reusables.github-actions.usage-api-requests %} +- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %} + +### Sistemas operativos compatibles para ejecutores autoalojados + +Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor auto-hospedado. + +#### Linux + +- Red Hat Enterprise Linux 7 +- CentOS 7 +- Oracle Linux 7 +- Fedora 29 o posterior +- Debian 9 o posterior +- Ubuntu 16.04 o posterior +- Linux Mint 18 o posterior +- openSUSE 15 o posterior +- SUSE Enterprise Linux (SLES) 12 SP2 o posterior + +#### Windows + +- Windows 7 64-bit +- Windows 8.1 64-bit +- Windows 10 64-bit +- Windows Server 2012 R2 64-bit +- Windows Server 2016 64-bit +- Windows Server 2019 64-bit + +#### macOS + +- macOS 10.13 (High Sierra) o posterior + +{% if enterpriseServerVersions contains currentVersion %} + +### La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} + +La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." + +{% endif %} + +### La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %} + +El ejecutor auto-hospedado sondea a {% data variables.product.product_name %} para solicitar actualizaciones de aplicaciones y para revisar si hay jobs en cola para su procesamiento. El ejecutor auto-hospedado utiliza un _sondeo largo_ de HTTPS que abre una conexión a {% data variables.product.product_name %} por 50 segundos, y si no recibe respuesta alguna, expira y crea un nuevo sondeo largo. La aplicación debe estar ejecutándose en la máquina para aceptar y ejecutar jobs de {% data variables.product.prodname_actions %}. + +{% if currentVersion == "free-pro-team@latest" %} + +Debes asegurarte de que la máquina tiene el acceso a la red adecuado para comunicarte con las URL de {% data variables.product.prodname_dotcom %} listadas a continuación. + +``` +github.com +api.github.com +*.actions.githubusercontent.com +codeload.github.com +``` + +Si utilizas un listado de direcciones IP permitidas para tu cuenta organizacional o empresarial de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" o "[Hacer cumplir los parámetros de seguridad en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". + +{% else %} + +Debes asegurarte de que la máquina tenga el acceso de red adecuado para comunicarse con {% data variables.product.product_location %}. + +{% endif %} + +También puedes usar ejecutores autoalojados con un servidor proxy. Para obtener más información, consulta "[Usar un servidor proxy con ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." + +### Seguridad de ejecutores autoalojdados con repositorios públicos + +{% data reusables.github-actions.self-hosted-runner-security %} + +Este no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, ya que cada uno de ellos siempre constituye una máquina virtual limpia y aislada, la cual se destruya al final de la ejecución del job. + +Los flujos de trabajo que no son de confianza y se ejecutan en tu ejecutor autoalojado plantean riesgos de seguridad considerables para tu máquina y entorno de red, en especial si tu máquina se mantiene en su entorno entre trabajos. Algunos de los riesgos incluyen: + +* Programas maliciosos que se ejecutan en la máquina. +* Escapar del entorno Sandbox del ejecutor de la máquina. +* Exponer el acceso al entorno de red de la máquina. +* Mantener datos peligrosos o no deseados en la máquina. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md new file mode 100644 index 0000000000000..2f2ab7e709421 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -0,0 +1,81 @@ +--- +title: Agregar ejecutores autoalojados +intro: 'Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}.' +redirect_from: + - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners + - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}. + +So eres un administrador de alguna organización o empresa, podría que quisieras agregar tus ejecutores auto-hospedados a nivel organizacional o empresarial. Este acercamiento hace que el ejecutor esté disponible para múltiples repositorios en tu organización o empresa y también te permite administrar tus ejecutores en un solo lugar. + +Para obtener información sobre los sistemas operativos compatibles con los ejecutores auto-hospedados o sobre el uso de ejecutores auto-hospedados con un servidor proxy, consulta "[Acerca de los ejecutores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)". + +{% warning %} + +**Advertencia:** {% data reusables.github-actions.self-hosted-runner-security %} + +Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)". + +{% endwarning %} + +### Agregar un ejecutor auto-hospedado a un repositorio + +Puedes agregar ejecutores auto-hospedados a un solo repositorio. Para agregar un ejecutor auto-hospedado a un repositorio de usuario, debes ser el dueño del mismo. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +1. Debajo de "ejecutores auto-hospedados", da clic en **Agregar ejecutor**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +### Agregar un ejecutor auto-hospedado a una organización + +Puedes agregar ejecutores auto-hospedados a nivel organizacional, en donde se podrán utilizar para procesar jobs para varios repositorios en una organización. Para agregar un ejecutor auto-hospedado a una organización, debes ser el dueño de la misma. + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Debajo de "Ejecutores auto-hospedados", da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +### Agregar un ejecutor auto-hospedado a una empresa + +Puedes agregar ejecutores auto-hospedados a una empresa, en donde pueden asignarse a organizaciones múltiples. Los administradores de la organización podrán controlar entonces qué repositorios pueden utilizarlo. + +{% if currentVersion == "free-pro-team@latest" %} +Para agregar un ejecutor auto-hospedado a una cuenta empresarial, debes ser un propietario de la empresa. +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} +Para agregar un ejecutor auto-hospedado a nivel empresarial de +{% data variables.product.product_location %}, debes ser un administrador de sitio. +{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Da clic en la pestaña de **Ejecutores auto-hospedados**. +1. Da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. Los ejecutores nuevos se asignan al grupo predeterminado. Puedes modificar el grupo del ejecutor después de que lo hayas registrado. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". +{% data reusables.github-actions.self-hosted-runner-configure %} +{% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Hacer que los ejecutores empresariales estén disponibles para los repositorios + +Predeterminadamente, los ejecutores en un grupo de ejecutores auto hospedados "Predeterminado" de una empresa se encontrarán disponibles para todas las organizaciones de ésta, pero no así para todos los repositorios en cada una de las organizaciones. + +Para que un grupo de ejecutores auto-hospedados a nivel empresarial se encuentre disponible para el repositorio de una organización, podría que necesites cambiar la configuración heredada de dicha organización para que el grupo de ejecutores pueda poner el ejecutor disponible para sus repositorios. + +Para obtener más información acerca de cómo cambiar la configuración de acceso en un grupo de ejecutores, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados utilizando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md new file mode 100644 index 0000000000000..b6fcbe01fd47c --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -0,0 +1,176 @@ +--- +title: Configurar la aplicación del ejecutor autoalojado como un servicio +intro: Puedes configurar la aplicación del ejecutor autoalojado como un servicio para iniciar automáticamente la aplicación del ejecutor cuando se inicia la máquina. +redirect_from: + - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +defaultPlatform: linux +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% capture service_first_step %}1. Detén la aplicación del ejecutor autoalojado si se está ejecutando actualmente.{% endcapture %} +{% capture service_non_windows_intro_shell %}En la máquina del ejecutor, abre un shell en el directorio en el que instalaste la aplicación del ejecutor autoalojado. Usa los comandos que se indican a continuación para instalar y administrar el servicio de ejecutor autoalojado.{% endcapture %} +{% capture service_nonwindows_intro %} Debes agregar un ejecutor a {% data variables.product.product_name %} antes de que puedas configurar la aplicación del ejecutor auto-hospedado como servicio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %} +{% capture service_win_name %}actions.runner.*{% endcapture %} + + +{% linux %} + +{{ service_nonwindows_intro }} + +Para los sistemas Linux que usan `systemd`, puedes usar el script `svc.sh` distribuido con la aplicación del ejecutor autoalojado para instalar y administrar el uso de la aplicación como un servicio. + +{{ service_non_windows_intro_shell }} + +{% endlinux %} + +{% windows %} + +{% note %} + +**Nota:** Configurar la aplicación del ejecutor autoalojado como un servicio en Windows es parte del proceso de configuración de la aplicación. Si ya configuraste la aplicación del ejecutor auto-hospedado pero no elegiste configurarla como servicio, debes eliminar el ejecutor de {% data variables.product.prodname_dotcom %} y volver a configurar la aplicación. Cuando vuelvas a configurar la aplicación, elige la opción para configurar la aplicación como un servicio. + +Para obtener más información, consulta "[Eliminar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners) y [Agregar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)." + +{% endnote %} + +Puedes administrar el servicio de ejecutor en la aplicación de **Servicios** de Windows, o puedes usar PowerShell para ejecutar los comandos que se indican a continuación. + +{% endwindows %} + +{% mac %} + +{{ service_nonwindows_intro }} + +{{ service_non_windows_intro_shell }} + +{% endmac %} + +{% linux %} + +### Instalar el servicio + +{{ service_first_step }} +1. Instala el servicio con el siguiente comando: + + ```shell + sudo ./svc.sh install + ``` + +{% endlinux %} +{% mac %} + +### Instalar el servicio + +{{ service_first_step }} +1. Instala el servicio con el siguiente comando: + + ```shell + ./svc.sh install + ``` +{% endmac %} + +### Iniciar el servicio + +Inicia el servicio con el siguiente comando: + +{% linux %} +```shell +sudo ./svc.sh start +``` +{% endlinux %} +{% windows %} +```shell +Start-Service "{{ service_win_name }}" +``` +{% endwindows %} +{% mac %} +```shell +./svc.sh start +``` +{% endmac %} + +### Comprobar el estado del servicio + +Verifica el estado del servicio con el siguiente comando: + +{% linux %} +```shell +sudo ./svc.sh status +``` +{% endlinux %} +{% windows %} +```shell +Get-Service "{{ service_win_name }}" +``` +{% endwindows %} +{% mac %} +```shell +./svc.sh status +``` +{% endmac %} + + Para obtener más información sobre la visualización del estado de tu ejecutor auto-hospedado, consulta la sección "[Monitoreo y solución de problemas para ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)". + +### Detener el servicio + +Detiene el servicio con el siguiente comando: + +{% linux %} +```shell +sudo ./svc.sh stop +``` +{% endlinux %} +{% windows %} +```shell +Stop-Service "{{ service_win_name }}" +``` +{% endwindows %} +{% mac %} +```shell +./svc.sh stop +``` +{% endmac %} + +### Desinstalar el servicio + +1. Detiene el servicio si se está ejecutando actualmente. +1. Desinstala el servicio con el siguiente comando: + + {% linux %} + ```shell + sudo ./svc.sh uninstall + ``` + {% endlinux %} + {% windows %} + ```shell + Remove-Service "{{ service_win_name }}" + ``` + {% endwindows %} + {% mac %} + ```shell + ./svc.sh uninstall + ``` + {% endmac %} + + +{% linux %} + +### Personalizar el servicio del ejecutor auto-hospedado + +Si no quieres utilizar la configuración de servicio predeterminada para `systemd` antes mencionada, puedes crear un servicio personalizado o utilizar cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `serviced` en `actions-runner/bin/actions.runner.service.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`. + +{% endlinux %} + +{% mac %} + +### Personalizar el servicio del ejecutor auto-hospedado + +Si no quieres utilizar la configuración predeterminada del servicio launchd antes mencionada, puedes crear un servicio personalizado o cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `plist` en `actions-runner/bin/actions.runner.plist.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`. + +{% endmac %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/index.md b/translations/es-ES/content/actions/hosting-your-own-runners/index.md new file mode 100644 index 0000000000000..d455afd8f38d7 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/index.md @@ -0,0 +1,23 @@ +--- +title: Alojar tus propios corredores +intro: Puedes crear ejecutores autohospedados para ejecutar flujos de trabajo en un entorno altamente personalizable. +redirect_from: + - /GitHub/Automating-Your-Workflow-with-GitHub-Actions/Hosting-Your-Own-Runners + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Hosting-Your-Own-Runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% link_in_list /about-self-hosted-runners %} +{% link_in_list /adding-self-hosted-runners %} +{% link_in_list /configuring-the-self-hosted-runner-application-as-a-service %} +{% link_in_list/Using-a-Proxy-Server-With-Self-Hosted-Runners%} +{% link_in_list /using-labels-with-self-hosted-runners %} +{% link_in_list /using-self-hosted-runners-in-a-workflow %} +{% link_in_list /managing-access-to-self-hosted-runners-using-groups %} +{% link_in_list /monitoring-and-troubleshooting-self-hosted-runners %} +{% link_in_list /removing-self-hosted-runners %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md new file mode 100644 index 0000000000000..178ac602ff872 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -0,0 +1,116 @@ +--- +title: Administrar el acceso a los ejecutores auto-hospedados utilizando grupos +intro: Puedes utilizar políticas para limitar el acceso a los ejecutores auto-hospedados que se hayan agregado a una organización o empresa. +redirect_from: + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los grupos de ejecutores auto-hospedados + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:** Todas las organizaciones tienen un solo grupo de ejecutores auto-hospedados predeterminado. Solo las cuentas empresariales y las organizaciones que pertenezcan a una cuenta empresarial pueden crear y administrar grupos adicionales de ejecutores auto-hospedados. + +{% endnote %} +{% endif %} + +Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados a nivel de empresas y organizaciones. Los administradores de la empresa pueden configurar políticas de acceso que controlan qué organizaciones en la empresa tienen acceso al grupo de ejecutores. Los administradores de las organizaciones pueden configurar políticas de acceso que controlen qué repositorios en una organización tienen acceso al grupo de ejecutores. + +Cuando un administrador de empresa otorga acceso a una organización para un grupo de ejecutores, los administradores de organización pueden ver que dicho grupo se lista en la configuración del ejecutor auto-hospedado de la organización. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para repositorios granulares en el grupo de ejecutores de la empresa. + +Cuando se crean nuevos ejecutores, se asignan automáticamente al grupo predeterminado. Los ejecutores solo pueden estar en un grupo a la vez. Puedes mover los ejecutores del grupo predeterminado a otro grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](#moving-a-self-hosted-runner-to-a-group)". + +### Crear un grupo de ejecutores auto-hospedados para una organización + +Todas las organizaciones tienen un solo grupo predeterminado de ejecutores auto-hospedados. Las organizaciones dentro de una cuenta empresarial pueden crear grupos auto-hospedados adicionales. Los administradores de la organización pueden permitir el acceso de los repositorios individuales a un grupo de ejecutores. + +Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes mover un ejecutor del grupo predeterminado a cualquier grupo que crees. + +Cuando creas un grupo, debes elegir una política que defina qué repositorios tienen acceso al grupo ejecutor. + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. En la sección de **Ejecutores auto-hospedados** da clic en **Agregar nuevo** y luego en **Grupo nuevo**. + + ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group.png) +1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio. + + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Puedes configurar un grupo de ejecutores para que una lista específica de repositorios puedan acceder a éste, o para que todos los repositorios en la organización puedan hacerlo. Predeterminadamente, los repositorios no pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes utilizar la opción **Permitir repositorios públicos** para anular dicha política.{% else if currentVersion == "enterprise-server@2.22"%}Puedes configurar un grupo de ejecutores para que ya sea una lista específica de repositorios, todos los repositorios privados, o todos los repositorios de la organización puedan acceder a él.{% endif %} + + {% warning %} + + **Warning** + + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + + Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + {% endwarning %} + + ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group-options.png) +1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política. + +### Crear un grupo de ejecutores auto-hospedados para una empresa + +Las empresas pueden agregar sus ejecutores auto-hospedados a grupos para su administración de accesos. Las empresas pueden crear grupos de ejecutores auto-hospedados a los cuales puedan acceder organizaciones específicas en la cuenta empresarial. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para los repositorios granulares a estos grupos de ejecutores para las empresas. + +Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes asignar el ejecutor a un grupo específico durante el proceso de registro o puedes moverlo después desde el grupo predeterminado a un grupo personalizado. + +Cuando creas un grupo, debes elegir la política que defina qué organizaciones tienen acceso al grupo de ejecutores. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Da clic en la pestaña de **Ejecutores auto-hospedados**. +1. Da clic en **Agregar nuevo** y luego en **Grupo nuevo**. + + ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) +1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso organizacional. + + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Puedes configurar un grupo de ejecutores para que ya sea una lista específica de organizaciones o todas las organizaciones de la empresa puedan acceder a él. Predeterminadamente, los repositorios no pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes utilizar la opción **Permitir repositorios públicos** para anular dicha política.{% else if currentVersion == "enterprise-server@2.22"%}Puedes configurar un grupo de ejecutores para que todas las organizaciones de la empresa puedan acceder a él, o puedes elegir organizaciones específicas.{% endif %} + + {% warning %} + + **Warning** + + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + + Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + {% endwarning %} + + ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) +1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política. + +### Cambiar la política de acceso de un grupo de ejecutores auto-hospedados + +Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo. + +{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} + +### Mover un ejecutor auto-hospedado a un grupo + +Los ejecutores auto-hospedados nuevos se asignan automáticamente al grupo predeterminado y entonces pueden moverse a otro grupo. + +1. En la sección **Ejecutores auto-hospedados** de la página de configuración, ubica el grupo actual del ejecutor que quieras mover de grupo y expande la lista de miembros de dicho grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png) +1. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move.png) +1. Para mover el ejecutor, da clic en el grupo de destino. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) + +### Eliminar un grupo de ejecutores auto-hospedados + +Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina. + +1. En la sección de **Ejecutores auto-hospedados** de la página de configuración, ubica el grupo que quieras eliminar y da clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png) + +1. Para eliminar el grupo, da clic en **Eliminar grupo**. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-remove.png) + +1. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md new file mode 100644 index 0000000000000..9595ed6424a15 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -0,0 +1,195 @@ +--- +title: Monitorear y solucionar problemas para los ejecutores auto-hospedados +intro: Puedes monitorear tus ejecutores auto-hospedados para ver su actividad y diagnosticar problemas comunes. +redirect_from: + - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners + - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Checking-The-status-of-Self-Hosted-Runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +defaultPlatform: linux +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Comprobar el estado de un ejecutor autoalojado utilizando {{ site.data.variables.product.prodname_dotcom }} + +{% data reusables.github-actions.self-hosted-runner-management-permissions-required %} + +{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Debajo de "Ejecutores auto-hospedados", puedes ver una lista de ejecutores registrados, incluyendo su nombre, etiquetas y estado. + + ![Lista de ejecutores](/assets/images/help/settings/actions-runner-list.png) + + El estado puede ser uno de los siguientes: + + * **Idle (Inactivo)**: El ejecutor está conectado a {% data variables.product.product_name %} y está listo para ejecutar puestos de trabajo. + * **Active (Activo)**: Actualmente, el ejecutor está ejecutando un puesto de trabajo. + * **Offline (Sin conexión)**: El ejecutor no está conectado a {% data variables.product.product_name %}. Esto puede deberse a que la máquina está fuera de línea, la aplicación del ejecutor autoalojado no se está ejecutando en la máquina o la aplicación del ejecutor autoalojado no se puede comunicar con {% data variables.product.product_name %}. + + +### Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado + +Puedes monitorear el estado de la aplicación del ejecutor auto-hospedado y de sus actividades. Los archivos de bitácora se mantienen en el directorio `_diag`, y se genera uno nuevo cada que se inicia la aplicación. El nombre de archivo comienza con *Runner_*, y le sige una marca de tiempo UTC de cuando se inició la aplicación. + +Para obtener registros detallados sobre las ejecuciones de jobs en el flujo de trabajo, consulta la siguiente sección que describe los archivos *Worker_*. + +### Revisar el archivo de bitácora de un job + +La aplicación del ejecutor auto-hospedado crea un archivo de bitácora detallado para cada job que procesa. Estos archivos se guardan en el directorio `_diag`, y el nombre de archivo comienza con el prefijo *Worker_*. + +{% linux %} + +### Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado + +Para los ejecutores auto-hospedados basados en Linux que se ejecutan en la aplicación utilizando un servicio, puedes utilizar `journalctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en systemd utiliza la siguiente convención de nomenclatura: `actions.runner.-..service`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre de un servicio es revisando el archivo _.service_. Por ejemplo: + +```shell +$ cat ~/actions-runner/.service +actions.runner.octo-org-octo-repo.runner01.service +``` + +Puedes utilizar `journalctl` para monitorear la actividad del ejecutor auto-hospedado en tiempo real: + +```shell +$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f +``` + +En este ejemplo de salida, puedes ver como inicia `runner01`, recibe un job llamado `testAction`, y luego muestra el estado resultante: + +```shell +Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service +Feb 11 14:57:07 runner01 runsvc.sh[962]: Started listener process +Feb 11 14:57:07 runner01 runsvc.sh[962]: Started running service +Feb 11 14:57:16 runner01 runsvc.sh[962]: √ Connected to GitHub +Feb 11 14:57:17 runner01 runsvc.sh[962]: 2020-02-11 14:57:17Z: Listening for Jobs +Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: testAction +Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded +``` + +Para ver la configuración de systemd, puedes ubicar archivo de servicio aquí: `/etc/systemd/system/actions.runner.-..service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)". + +{% endlinux %} + +{% mac %} + +### Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado + +Para los ejecutores auto-hospedados basados en macOS que se ejecutan en la aplicación como un servicio, puedes utilizar `launchctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en launchd utiliza la siguiente convención de nomenclatura: `actions.runner.-.`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre del servicio es revisando el archivo _.service_ en el directorio del ejecutor: + +```shell +% cat ~/actions-runner/.service +/Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist +``` + +El script `svc.sh` utiliza `launchctl` para revisar si la aplicación se está ejecutando. Por ejemplo: + +```shell +$ ./svc.sh status +status actions.runner.example.runner01: +/Users/exampleUsername/Library/LaunchAgents/actions.runner.example.runner01.plist +Started: +379 0 actions.runner.example.runner01 +``` + +La salida generada incluye la ID del proceso y el nombre del servicio launchd de la aplicación. + +Para ver la configuración de launchd, puedes ubicar el archivo del servicio aquí: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)". + +{% endmac %} + + +{% windows %} + +### Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado + +Para los ejecutores auto-hospedados basados en Windows que se ejecuten en la aplicación como servicio, puedes utilizar PowerShell para monitorear su actividad en tiempo real. El servicio utiliza la convención de nomenclatura `GitHub Actions Runner (-.)`. También puedes encontrar el nombre del servicio si revisas el archivo _.service_ en el directorio del ejecutor: + +```shell +PS C:\actions-runner> Get-Content .service +actions.runner.octo-org-octo-repo.runner01.service +``` + +Puedes ver el estado del ejecutor en la aplicación _Services_ de Windows (`services.msc`). También puedes utilizar PowerShell para revisar si el servicio se está ejecutando: + +```shell +PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status +Name Status +---- ------ +actions.runner.octo-org-octo-repo.runner01.service Running +``` + +Puedes utilizar PowerShell para revisar la actividad reciente del ejecutor auto-hospedado. En este ejemplo de salida, puedes ver que la aplicación comienza, recibe un job llamado `testAction`, y después muestra el estado resultante: + +```shell +PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService + + Index Time EntryType Source InstanceID Message + ----- ---- --------- ------ ---------- ------- + 136 Mar 17 13:45 Information ActionsRunnerService 100 2020-03-17 13:45:48Z: Job Greeting completed with result: Succeeded + 135 Mar 17 13:45 Information ActionsRunnerService 100 2020-03-17 13:45:34Z: Running job: testAction + 134 Mar 17 13:41 Information ActionsRunnerService 100 2020-03-17 13:41:54Z: Listening for Jobs + 133 Mar 17 13:41 Information ActionsRunnerService 100 û Connected to GitHub + 132 Mar 17 13:41 Information ActionsRunnerService 0 Service started successfully. + 131 Mar 17 13:41 Information ActionsRunnerService 100 Starting Actions Runner listener + 130 Mar 17 13:41 Information ActionsRunnerService 100 Starting Actions Runner Service + 129 Mar 17 13:41 Information ActionsRunnerService 100 create event log trace source for actions-runner service +``` + +{% endwindows %} + +### Monitorear el proceso de actualización automática + +Te recomendamos que revises el proceso de actualización automático a menudo, ya que el ejecutor auto-hospedado no podrá procesar jobs si cae debajo de cierto umbral de versiones. La aplicación del ejecutor auto-hospedado se actualiza automáticamente, pero nota que este proceso no incluye ninguna actualización al sistema operativo ni a otro tipo de software; necesitarás administrar estas actualizaciones por separado. + +Puedes ver las actividades de actualización en los archivos de bitácora *Runner_*. Por ejemplo: + +```shell +[Feb 12 12:37:07 INFO SelfUpdater] An update is available. +``` + +Adicionalmente, puedes encontrar más información en los archivos de bitácora _SelfUpdate_ ubicados en el directorio `_diag`. + +{% linux %} + +### Solucionar problemas en los contenedores de los ejecutores auto-hospedados + +#### Revisar que se haya instalado Docker + +Si tus jobs necesitan contenedores, entonces el ejecutor auto-hospedado debe estar basado en Linux y necesita contar con Docker instalado. Revisa que tu ejecutor auto-hospedado tenga Docker instalado y que el servicio se esté ejecutando. + +Puedes utilizar `systemctl` para revisar el estado del servicio: + +```shell +$ sudo systemctl is-active docker.service +active +``` + +Si no se ha instalado Docker, entonces las acciones dependientes fallarán con los siguientes errores: + +```shell +[2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' +[2020-02-13 16:56:10Z INFO DockerCommandManager] Not found. +[2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' +``` + +#### Revisar los permisos de Docker + +Si tu job falla con el siguiente error: + +```shell +dial unix /var/run/docker.sock: connect: permission denied +``` + +Revisa que la cuenta de servicio del ejecutor auto-hospedado tenga permiso de utilizar el servicio de Docker. Puedes identificar esta cuenta revisando la configuración del ejecutor auto-hospedado en systemd. Por ejemplo: + +```shell +$ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service +User=runner-user +``` + +{% endlinux %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md new file mode 100644 index 0000000000000..11cd2331a282f --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -0,0 +1,77 @@ +--- +title: Eliminar ejecutores autoalojados +intro: 'Puedes eliminar permanentemente un ejecutor auto-hospedado de {{ site.data.variables.product.prodname_actions }}.' +redirect_from: + - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners + - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Eliminar un ejecutor de un repositorio + +{% note %} + +**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} + +{% data reusables.github-actions.self-hosted-runner-auto-removal %} + +{% endnote %} + +Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. + +{% data reusables.github-actions.self-hosted-runner-reusing %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} + +### Eliminar el ejecutor de una organización + +{% note %} + +**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} + +{% data reusables.github-actions.self-hosted-runner-auto-removal %} + +{% endnote %} + +Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. + +{% data reusables.github-actions.self-hosted-runner-reusing %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.repositories.settings-sidebar-actions %} +{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} + +### Eliminar un ejecutor de una empresa + +{% note %} + +**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} + +{% data reusables.github-actions.self-hosted-runner-auto-removal %} + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" %} +Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} +Para eliminar un ejecutor auto-hospedado a nivel empresarial de +{% data variables.product.product_location %}, debes ser un administrador de sitio. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +{% endif %} + +{% data reusables.github-actions.self-hosted-runner-reusing %} + + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md new file mode 100644 index 0000000000000..26cdbe92685d9 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -0,0 +1,50 @@ +--- +title: Usar un servidor proxy con ejecutores autoalojados +intro: 'Puedes configurar los ejecutores autoalojados para usar un servidor proxy para comunicarte con {% data variables.product.product_name %}.' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Configurar un servidor proxy mediante variables de entorno + +Si necesitas un ejecutor autoalojado para comunicarte a través de un servidor proxy, la aplicación del ejecutor autoalojado usa configuraciones de proxy establecidas en las siguientes variables de entorno: + +* `https_proxy`: URL del proxy para el tráfico HTTPS. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo: + * `http://proxy.local` + * `http://192.168.1.1:8080` + * `http://username:password@proxy.local` +* `http_proxy`: URL del proxy para el tráfico HTTP. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo: + * `http://proxy.local` + * `http://192.168.1.1:8080` + * `http://username:password@proxy.local` +* `no_proxy`: Lista de hosts separados por comas que no deberían usar un proxy. Solo se permiten nombres de host en `no_proxy`, no puedes usar direcciones IP. Por ejemplo: + * `example.com` + * `example.com,myserver.local:443,example.org` + +Las variables de entorno de proxy se leen cuando se inicia la aplicación del ejecutor autoalojado, por lo que debes establecer las variables de entorno antes de configurar o iniciar la aplicación del ejecutor autoalojado. Si cambia la configuración de tu proxy, debes reiniciar la aplicación del ejecutor autoalojado. + +En las máquinas Windows, los nombres de las variables de entorno proxy no distinguen mayúsculas de minúsculas. En las máquinas Linux y macOS, te recomendamos que uses todas las variables de entorno en minúsculas. Si tienes una variable de entorno tanto en minúsculas como en mayúsculas en Linux o macOS, por ejemplo `https_proxy` y `HTTPS_PROXY`, la aplicación del ejecutor autoalojado usa la variable de entorno en minúscula. + +### Usar un archivo.env para establecer la configuración del proxy + +Si establecer variables de entorno no es práctico, puedes establecer las variables de configuración de proxy en un archivo llamado _.env_ en el directorio de la aplicación del ejecutor autoalojado. Por ejemplo, esto puede ser necesario si deseas configurar la aplicación del ejecutor como un servicio en una cuenta de sistema. Cuando se inicia la aplicación del ejecutor, lee las variables establecidas en _.env_ para la configuración del proxy. + +A continuación se muestra un ejemplo de configuración del proxy _.env_: + +``` +https_proxy=http://proxy.local:8080 +no_proxy=example.com,myserver.local:443 +``` + +### Establecer la configuración del proxy para contenedores Docker + +Si usas las acciones del contenedor Docker o los contenedores de servicio en tus flujos de trabajo, es posible que también debas configurar Docker para usar tu servidor proxy además de establecer las variables de entorno anteriores. + +Para obtener información sobre la configuración de Docker que se necesita, consulta "[Configurar Docker para usar un servidor proxy](https://docs.docker.com/network/proxy/)" en la documentación de Docker. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md new file mode 100644 index 0000000000000..b2464231bf6e1 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -0,0 +1,63 @@ +--- +title: Utilizar etiquetas con ejecutores auto-hospedados +intro: Puedes utilizar etiquetas para organizar tus ejecutores auto-hospedados según sus características. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a tipos específicos de ejecutores auto-hospedados, consulta la sección "[Utilizar ejecutores auto-hospedados en un flujo de trabajo](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)". + +{% data reusables.github-actions.self-hosted-runner-management-permissions-required %} + +### Crear una etiqueta personalizada + +{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.self-hosted-runner-list %} +{% data reusables.github-actions.self-hosted-runner-list-group %} +{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} +1. En el campo "Filtrar etiquetas", teclea el nombre de tu nueva etiqueta y da clic en **Crear nueva etiqueta**. ![Etiqueta de agregar ejecutor](/assets/images/help/settings/actions-add-runner-label.png) + +La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %} + +### Asignar una etiqueta a un ejecutor auto-hospedado + +{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.self-hosted-runner-list %} +{% data reusables.github-actions.self-hosted-runner-list-group %} +{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} +1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado. + +### Eliminar una etiqueta personalizada de un ejecutor auto-hospedado + +{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.self-hosted-runner-list %} +{% data reusables.github-actions.self-hosted-runner-list-group %} +{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} +1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %} + +### Utilizar el script de configuración para crear y asignar etiquetas + +Puedes utilizar el script de configuración en el ejecutor auto-hospedado para crear y asignar etiquetas personalizadas. Por ejemplo, este comando asigna una etiqueta llamada `gpu` al ejecutor auto-hospedado. + +```shell +./config.sh --labels gpu +``` + +La etiqueta se creará si no existe. También puedes utilizar este acercamiento para asignar etiquetas predeterminadas a los ejecutores, tales como `x64` o `linux`. Cuando se asignan etiquetas predeterminadas utilizando el script de configuración, {% data variables.product.prodname_actions %} las acepta como asignadas y no valida si el ejecutor está utilizando ese sistema operativo o arquitectura. + +Puedes utilizar separación por comas para asignar etiquetas múltiples. Por ejemplo: + +```shell +./config.sh --labels gpu,x64,linux +``` + +{% note %} + +** Nota:** Si reemplazaste un ejecutor existente, entonces deberás volver a asignar cualquier etiqueta personalizada. + +{% endnote %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md new file mode 100644 index 0000000000000..524f5f3130846 --- /dev/null +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -0,0 +1,71 @@ +--- +title: Usar ejecutores autoalojados en un flujo de trabajo +intro: 'Para usar los ejecutores autoalojados en un flujo de trabajo, puedes usar etiquetas para especificar el tipo de ejecutores para un trabajo.' +redirect_from: + - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow + - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Para obtener más información sobre cómo crear etiquetas personalizadas y predeterminadas, consulta la sección "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". + +### Usar ejecutores autoalojados en un flujo de trabajo + +Las etiquetas te permiten enviar jobs de flujo de trabajo a tipos específicos de ejecutores auto-hospedados, de acuerdo con sus características compartidas. Por ejemplo, si tu job requiere una componente de hardware o paquete de software específico, puedes asignar una etiqueta personalizada a un ejecutor y después configurar tu job para que solo se ejecute en los ejecutores con esta etiqueta. + +{% data reusables.github-actions.self-hosted-runner-labels-runs-on %} + +Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)." + +### Utilizar etiquetas predeterminadas para enrutar jobs + +Un ejecutor auto-hospedado recibe ciertas etiquetas automáticamente cuando se agrega a {% data variables.product.prodname_actions %}. Estas se utilizan para indicar su sistema operativo y plataforma de hardware: + +* `autoalojado`: Etiqueta por defecto aplicada a todos los ejecutores autoalojados. +* `linux`, `windows`, o `macOS`: Se aplican dependiendo del sistema operativo. +* `x86`, `x64`, `ARM`, o `ARM64`: Se aplican dependiendo de la arquitectura del hardware. + +Puedes utilizar el YAML de tu flujo de trabajo para mandar jobs a las diferentes combinaciones de estas etiquetas. En este ejemplo, un ejecutor auto-hospedado que empate con las tres etiquetas será elegible para ejecutar el job: + +```yaml +runs-on: [self-hosted, linux, ARM64] +``` + +- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado. +- `linux` - Utiliza únicamente un ejecutor basado en Linux. +- `ARM64` - Utiliza únicamente un ejecutor basado en hardware ARM64. + +Las etiquetas predeterminadas son fijas y no se pueden cambiar ni eliminar. Considera utilizar etiquetas personalizadas si necesitas más control sobre el enrutamiento de los jobs. + +### Utilizar etiquetas personalizadas para enrutar jobs + +Puedes crear etiquetas personalizadas y asignarlas a tus ejecutores auto-hospedados en cualquier momento. Las etiquetas personalizadas te permiten enviar jobs a tipos particulares de ejecutores auto-hospedados, basándose en cómo se etiquetan. + +Por ejemplo, si tienes un job que requiere un tipo específico de hardware de gráficos, puedes crear una etiqueta personalizada llamada `gpu` y asignarla a los ejecutores que tengan instalado este hardware. Un ejecutor auto-hospedado que empate con las etiquetas asignadas será entonces elegible para ejecutar el job. + +Este ejemplo muestra un job que combina etiquetas predeterminadas y personalizadas: + +```yaml +runs-on: [self-hosted, linux, x64, gpu] +``` + +- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado. +- `linux` - Utiliza únicamente un ejecutor basado en Linux. +- `x64` - Utiliza únicamente un ejecutor basado en hardware x64. +- `gpu` - Esta etiqueta personalizada se asignó manualmente a los ejecutores auto-hospedados con hardware de GPU instalado. + +Estas etiquetas operan acumulativamente, así que las etiquetas de un ejecutor auto-hospedado deberán empatar con los cuatro criterios para poder ser elegibles para procesar el job. + +### Precedencia de enrutamiento para los ejecutores auto-hospedados + +Si utilizas ejecutores tanto a nivel de repositorio como a nivel de organización, {% data variables.product.prodname_dotcom %} sigue un orden de precedencia cuando enruta los jobs hacia los ejecutores auto-hospedados: + +1. Se procesan las etiquetas de `runs-on` del job. Entonces, {% data variables.product.prodname_dotcom %} intenta ubicar un ejecutor que coincida con los requisitos de la etiqueta: +2. El job se envía a un ejecutor a nivel de repositorio que coincida con las etiquetas del mismo. Si no hay un ejecutor a nivel de repositorio disponible (ya sea que esté ocupado, sin conexión, o no tenga etiquetas que coincidan): +3. El job se envía a un ejecutor de nivel organizacional que coincida con las etiquetas del mismo. Si hay un ejecutor de nivel organizacional disponible, el la solicitud del job falla con un error. diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md new file mode 100644 index 0000000000000..35c22cdf14d52 --- /dev/null +++ b/translations/es-ES/content/actions/index.md @@ -0,0 +1,85 @@ +--- +title: Documentación de GitHub Actions +shortTitle: GitHub Actions +intro: 'Automatiza, personaliza y ejecuta tus flujos de trabajo de desarrollo de software directamente en tu repositorio con {% data variables.product.prodname_actions %}. Puedes descubrir, crear y compartir acciones para realizar cualquier trabajo que quieras, incluido CI/CD, y combinar acciones en un flujo de trabajo completamente personalizado.' +introLinks: + quickstart: /actions/quickstart + reference: /actions/reference +featuredLinks: + guides: + - /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: Visualización de flujos de trabajo + date: '2020-12-08' + href: https://github.blog/changelog/2020-12-08-github-actions-workflow-visualization/ + - + title: Eliminación de los comandos de set-env y add-path en el 16 de Noviembre + date: '09-11-2020' + href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ + - + title: Los flujos de trabajo más recientes de Ubuntu utilizarán 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 +product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU +redirect_from: + - /articles/automating-your-workflow-with-github-actions/ + - /articles/customizing-your-project-with-github-actions/ + - /github/automating-your-workflow-with-github-actions + - /actions/automating-your-workflow-with-github-actions/ + - /categories/automating-your-workflow-with-github-actions + - /marketplace/actions +layout: product-landing +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + + + + + + + + + + +{% assign actionsCodeExamples = site.data.variables.action_code_examples %} +{% if actionsCodeExamples %} +
    +

    Ejemplos de código

    + +
    + +
    + +
    + {% render 'code-example-card' for actionsCodeExamples as example %} +
    + + + +
    +
    {% octicon "search" width="24" %}
    +

    Lo sentimos, no hay respultados para

    +

    Parece que no tenemos un ejemplo que se adapte a tu filtro.
    Intenta con otro filtro o agrega tu ejemplo de código

    + Aprende cómo agregar un ejemplo de código {% octicon "arrow-right" %} +
    +
    +{% endif %} diff --git a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md new file mode 100644 index 0000000000000..70c581c1ea63f --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -0,0 +1,96 @@ +--- +title: Características esenciales de las GitHub Actions +shortTitle: Características esenciales +intro: 'Las {% data variables.product.prodname_actions %} se diseñaron para ayudarte a crear automatizaciones robustas y dinámicas. Esta guía te mostrará cómo crear flujos de trabajo de {% data variables.product.prodname_actions %} que incluyan variables de ambiente, scripts personalizados, y más.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Las {% data variables.product.prodname_actions %} te permiten personalizar tus flujos de trabajo para satisfacer las necesidades específicas de tu aplicación y de tu equipo. En esta guía, presentaremos algunas de las técnicas de personalización esenciales, tales como el uso de variables, la ejecución de scripts, y el compartir datos y artefactos entre jobs. + +### Utilizar varibales en tus flujos de trabajo + +Las {% data variables.product.prodname_actions %} incluyen variables de ambiente predeterminadas para cada ejecución de flujo de trabajo. Si necesitas utilizar variables de ambiente personalizadas, puedes configurarlas en tu archivo de flujo de trabajo de YAML. Este ejemplo te muestra cómo crear variables personalizadas que se llamen `POSTGRES_HOST` y `POSTGRES_PORT`. Estas variables estarán entonces disponibles en el script `node client.js`. + +```yaml +jobs: + example-job: + steps: + - name: Connect to PostgreSQL + run: node client.js + env: + POSTGRES_HOST: postgres + POSTGRES_PORT: 5432 +``` + +Para obtener más información, consulta "[Usar variables de entorno](/actions/configuring-and-managing-workflows/using-environment-variables)". + +### Agregar scripts a tu flujo de trabajo + +Puedes utilizar acciones para ejecutar scripts y comandos de shell, los cuales se ejecutarán después en el ejecutor asignado. Este ejemplo muestra cómo una acción puede utilizar la palabra clave `run` para ejecutar `npm install -g bats` en el ejecutor. + +```yaml +jobs: + example-job: + steps: + - run: npm install -g bats +``` + +Por ejemplo, para ejecutar un script como una acción, puedes almacenarlo en tu repositorio e indicar la ruta y tipo de shell. + +```yaml +jobs: + example-job: + steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash +``` + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". + +### Compartir datos entre jobs + +Si tu job genera archivos que quieras compartir con otro job en el mismo flujo de trabajo, o si quieres guardar los archivos para su referencia futura, puedes almacenarlos en {% data variables.product.prodname_dotcom %} como _artefactos_. Los artefactos son los archivos que se crean cuando desarrollas y pruebas tu código. Por ejemplo, los artefactos podrían incluir archivos binarios o de paquete, resultados de pruebas, capturas de pantalla o archivos de registro. Los artefactos se asocian con la ejecución del flujo de trabajo en donde se crearon y otro job puede utilizarlos. + +Por ejemplo, puedes crear un archivo y luego subirlo como un artefacto. + +```yaml +jobs: + example-job: + name: Save output + steps: + - shell: bash + run: | + expr 1 + 1 > output.log + - name: Upload output file + uses: actions/upload-artifact@v1 + with: + name: output-log-file + path: output.log +``` + +Para descargar un artefacto de una ejecución de flujo de trabajo independiente, puedes utilizar la acción `actions/download-artifact`. Por ejemplo, puedes descargar el artefacto que se llama `output-log-file`. + +```yaml +jobs: + example-job: + steps: + - name: Download a single artifact + uses: actions/download-artifact@v2 + with: + name: output-log-file +``` + +Para obtener más información acerca de los artefactos, consulta la sección "[Persistir datos de flujos de trabajo utilizando artefactos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)". + +### Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows)". diff --git a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md new file mode 100644 index 0000000000000..33bcb0b94ff63 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -0,0 +1,157 @@ +--- +title: Encontrar y personalizar las acciones +shortTitle: Encontrar y personalizar las acciones +intro: 'Las acciones son los componentes básicos que hacen funcionar a tu flujo de trabajo. Un flujo de trabajo puede contener acciones que cree la comunidad, o puedes crear tus propias acciones directamente dentro del repositorio de tu aplicación. Esta guía te mostrará cómo descubrir, utilizar y personalizar las acciones.' +redirect_from: + - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions + - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow + - /actions/getting-started-with-github-actions/using-actions-from-github-marketplace + - /actions/getting-started-with-github-actions/using-community-workflows-and-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'how_to' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Las acciones que utilizas en tu flujo de trabajo pueden definirse en: + +- Un repositorio público +- El mismo repositorio en donde tu archivo de flujo de trabajo hace referencia a la acción +- Una imagen del contenedor Docker publicada en Docker Hub + +{% data variables.product.prodname_marketplace %} es una ubicación central para que encuentres las acciones que crea la comunidad de {% data variables.product.prodname_dotcom %}. La [Página de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/actions/) te permite filtrar las acciones por categoría. + +{% data reusables.actions.enterprise-marketplace-actions %} + +### Buscar las acciones de Marketplace en el editor de flujo de trabajo + +Puedes buscar acciones manualmente o por coincidencia exacta directamente en el editor de flujo de datos de tu repositorio. Desde la barra lateral, puedes buscar una acción específica, ver las acciones destacadas, y buscar manualmente las categorías destacadas. También puedes ver la cantidad de estrellas que la comunidad de {% data variables.product.prodname_dotcom %} ha otorgado a una acción. + +1. En tu repositorio, navega hasta el archivo de flujo de trabajo que deseas editar. +1. En el ángulo superior derecho de la vista del archivo, para abrir el editor de flujo de trabajo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.![Botón para editar un archivo de flujo de trabajo](/assets/images/help/repository/actions-edit-workflow-file.png) +1. A la derecha del editor, utiliza la barra lateral de {% data variables.product.prodname_marketplace %} para buscar las acciones. Las acciones con la insignia de {% octicon "verified" aria-label="The verified badge" %} indican que {% data variables.product.prodname_dotcom %} verificó que el creador de la acción es una organización asociada. ![Barra lateral del flujo de trabajo de Marketplace](/assets/images/help/repository/actions-marketplace-sidebar.png) + +### Agregar una acción a tu flujo de trabajo + +Las páginas de listado de acciones incluyen la versión de la acción y la sintaxis de flujo de trabajo que se requiere para utilizar dicha acción. Para mantener estable a tu flujo de trabajo, aún cuando se hagan actualizaciones en una acción, puedes referenciar la versión de la acción a utilizar si especificas el número de etiqueta de Git o de Docker en tu archivo de flujo de trabajo. + +1. Navega hasta la acción que deseas usar en tu flujo de trabajo. +1. En "Installation" (Instalación), haz clic en {% octicon "clippy" aria-label="The edit icon" %} para copiar la sintaxis del flujo de trabajo. ![Ver descripción de la acción](/assets/images/help/repository/actions-sidebar-detailed-view.png) +1. Pega la sintaxis como un nuevo paso en tu flujo de trabajo. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." +1. Si la accion requiere que proprociones información de entrada, configúrala en tu flujo de trabajo. Para saber más sobre la información de entrada que pudiera requerir una acción, consulta la sección "[Utilizar entradas y salidas con una acción](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)". + +{% if currentVersion == "free-pro-team@latest" %} + +{% data reusables.dependabot.version-updates-for-actions %} + +{% endif %} + +### Utilizar la administración de lanzamientos para tus acciones personalizadas + +Los creadores de una acción comunitaria tienen la opción de utilizar etiquetas, ramas, o valores de SHA para administrar los lanzamientos de la acción. Similar a cualquier dependencia, debes indicar la versión de la acción que te gustaría utilizar basándote en tu comodidad con aceptar automáticamente las actualizaciones para dicha acción. + +Designarás la versión de la acción en tu archivo de flujo de trabajo. Revisa la documentación de la acción para encontrar información de su enfoque sobre la administración de lanzamientos, y para ver qué etiqueta, rama, o valor de SHA debes utilizar. + +#### Utilizar etiquetas + +Las etiquetas son útiles para que te permitan decidir cuándo cambiar entre versiones mayores y menores, pero son más efímeras y el mantenedor puede moverlas o borrarlas. Este ejemplo te muestra cómo seleccionar una acción que se ha marcado como `v1.0.1`: + +```yaml +steps: + - uses: actions/javascript-action@v1.0.1 +``` + +#### Utilizar SHAs + +Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. Este ejemplo apunta al SHA de una acción: + +```yaml +steps: + - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89 +``` + +#### Utilizar ramas + +El especificar una rama destino para la acción significa que ésta siempre ejecutará la versión que se encuentre actualmente en dicha rama. Este acercamiento puede crear problemas si una actualización a la rama incluye cambios importantes. Este ejemplo apunta a una rama que se llama `@main`: + +```yaml +steps: + - uses: actions/javascript-action@main +``` + +Para obtener más información, consulta la sección "[Utilizar la administración de lanzamientos para las acciones](/actions/creating-actions/about-actions#using-release-management-for-actions)". + +### Utilizar entradas y salidas con una acción + +Una acción a menudo acepta o requiere entradas y genera salidas que puedes utilizar. Por ejemplo, una acción podría requerir que especifiques una ruta a un archivo, el nombre de una etiqueta, u otros datos que utilizará como parte del procesamiento de la misma. + +Para ver las entradas y salidas de una acción, revisa el `action.yml` o el `action.yaml` en el directorio raíz del repositorio. + +En este `action.yml` de ejemplo, la palabra clave `inputs` define una entrada requerida que se llama `file-path`, e incluye un valor predeterminado que se utilizará si ésta no se especifica. La palabra clave `outputs` define una salida que se llama `results-file`, la cual te dice en dónde se ubican los resultados. + +```yaml +name: 'Example' +description: 'Receives file and generates output' +inputs: + file-path: # id of input + description: "Path to test script" + required: true + default: 'test-file.js' +outputs: + results-file: # id of output + description: "Path to results file" +``` + +### Hacer referencia a una acción en el mismo repositorio en el que un archivo de flujo de trabajo usa la acción + +Si se define una acción en el mismo repositorio en el que tu archivo de flujo de trabajo usa la acción, puedes hacer referencia a la acción con ‌`{owner}/{repo}@{ref}` o la sintaxis `./path/to/dir` en tu archivo de flujo de trabajo. + +Ejemplo de estructura de archivo de repositorio: + +``` +|-- hello-world (repository) +| |__ .github +| └── workflows +| └── my-first-workflow.yml +| └── actions +| |__ hello-world-action +| └── action.yml +``` + +Ejemplo de archivo de flujo de trabajo: + +```yaml +jobs: + build: + runs-on: ubuntu-latest + steps: + # Este paso revisa una copia de tu repositorio. + - uses: actions/checkout@v2 + # Este paso hace referencia al directorio que contiene la acción. + - uses: ./.github/actions/hello-world-action +``` + +El archivo `action.yml` se utiliza para proporcionar metadatos para la acción. Aprende sobre el contenido de este archivo en la sección "[Sintaxis de metadatos para las GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)" + +### Hacer referencia a un contenedor en Docker Hub + +Si se define una acción en una imagen de contenedor Docker publicada en Docker Hub, debes hacer referencia a la acción con la sintaxis `docker://{image}:{tag}` en tu archivo de flujo de trabajo. Para proteger tu código y tus datos, te recomendamos que verifiques la integridad de la imagen del contenedor Docker de Docker Hub antes de usarla en tu flujo de trabajo. + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + uses: docker://alpine:3.8 +``` + +Para encontrar algunos ejemplos de acciones de Docker, consulta el [flujo de trabajo de Docker-image.yml](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) y la sección "[Crear una acción de contenedor de Docker](/articles/creating-a-docker-container-action)". + +### Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Características esenciales de las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)". diff --git a/translations/es-ES/content/actions/learn-github-actions/index.md b/translations/es-ES/content/actions/learn-github-actions/index.md new file mode 100644 index 0000000000000..9b160c33a62b6 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/index.md @@ -0,0 +1,43 @@ +--- +title: Aprende sobre las GitHub Actions +shortTitle: Aprende sobre las GitHub Actions +intro: 'Ya sea que seas nuevo en el uso de {% data variables.product.prodname_actions %} o que te interese aprender sobre todo lo que pueden ofrecer, esta guía te ayudará a utilizar las {% data variables.product.prodname_actions %} para acelerar tus flujos de trabajo de desarrollo de aplicaciones.' +redirect_from: + - /articles/about-github-actions + - /GitHub/Automating-Your-Workflow-with-GitHub-Actions/about-GitHub-Actions + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/about-GitHub-Actions + - /actions/getting-started-with-github-actions + - /actions/getting-started-with-github-actions/about-github-actions + - /actions/getting-started-with-github-actions/overview + - /actions/getting-started-with-github-actions/getting-started-with-github-actions + - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/ + - /actions/configuring-and-managing-workflows/configuring-a-workflow + - /articles/creating-a-workflow-with-github-actions/ + - /articles/configuring-a-workflow + - /github/automating-your-workflow-with-github-actions/configuring-a-workflow + - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow + - /actions/creating-workflows/workflow-configuration-options + - /articles/configuring-workflows + - /github/automating-your-workflow-with-github-actions/configuring-workflows + - /actions/automating-your-workflow-with-github-actions/configuring-workflows + - /github/automating-your-workflow-with-github-actions/getting-started-with-github-actions + - /actions/automating-your-workflow-with-github-actions/getting-started-with-github-actions + - /actions/configuring-and-managing-workflows + - /articles/getting-started-with-github-actions + - /actions/migrating-to-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% link_with_intro /introduction-to-github-actions %} +{% link_with_intro /finding-and-customizing-actions %} +{% link_with_intro /essential-features-of-github-actions %} +{% link_with_intro /managing-complex-workflows %} +{% link_with_intro /sharing-workflows-with-your-organization %} +{% link_with_intro /security-hardening-for-github-actions %} +{% link_with_intro /migrating-from-azure-pipelines-to-github-actions %} +{% link_with_intro /migrating-from-circleci-to-github-actions %} +{% link_with_intro /migrating-from-gitlab-cicd-to-github-actions %} +{% link_with_intro /migrating-from-jenkins-to-github-actions %} +{% link_with_intro /migrating-from-travis-ci-to-github-actions %} \ No newline at end of file diff --git a/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md new file mode 100644 index 0000000000000..a527a8e3a8e0d --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -0,0 +1,231 @@ +--- +title: Introducción a GitHub Actions +shortTitle: Introducción a GitHub Actions +intro: 'Aprende sobre los conceptos centrales y sobre los diversos componentes de las {% data variables.product.prodname_actions %}, y ve un ejemplo que te muestra cómo incluir automatizaciones en tu repositorio.' +redirect_from: + - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions + - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions + - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Las {% data variables.product.prodname_actions %} te ayudan a automatizar tareas dentro de tu ciclo de vida de desarrollo de software. Las {% data variables.product.prodname_actions %} se manejan por eventos, lo cual significa que puedes ejecutar una serie de comandos después de que haya ocurrido un evento especificado. Por ejemplo, cada vez que alguien crea una solicitud de cambios para un repositorio, puedes ejecutar automáticamente un comando que ejecute un script de prueba de software. + +Este diagrama ilustra como puedes utilizar las {% data variables.product.prodname_actions %} para ejecutar automáticamente tus scripts de pruebas de software. Un evento activa el _flujo de trabajo_ automáticamente, el cual contiene un _job_. Entonces, el job utiliza _pasos_ para controlar el orden en el que se ejecutan las _acciones_. Estas acciones son los comandos que automatizan las pruebas de tu software. + +![Resumen del flujo de trabajo](/assets/images/help/images/overview-actions-simple.png) + +### Los componentes de las {% data variables.product.prodname_actions %} + +A continuación, encontrarás una lista de los diferentes componentes de las {% data variables.product.prodname_actions %} que funcionan en conjunto para ejecutar jobs. Puedes ver cómo dichos componentes interactúan entre ellos. + +![Resumen de componentes y servicios](/assets/images/help/images/overview-actions-design.png) + +#### Flujos de trabajo + +El flujo de trabajo es un procedimiento automatizado que agregas a tu repositorio. Los flujos de trabajo se componen de uno o más jobs y pueden programarse o activarse a través de un evento. El flujo de trabajo se puede utilizar para crear, probar, empacar, lanzar o desplegar un proyecto en {% data variables.product.prodname_dotcom %}. + +#### Eventos + +En evento es una actividad específica que activa un flujo de trabajo. Por ejemplo, la actividad se puede originar desde {% data variables.product.prodname_dotcom %} cuando alguien sube una confirmación a un repositorio o cuando se crea una propuesta o solicitud de extracción. También puedes utilizar el [webhook de envío del repositorio](/rest/reference/repos#create-a-repository-dispatch-event) para activar un flujo de trabajo cuando ocurra un evento externo. Para encontrar una lista de eventos completa que puede utilizarse para activar flujos de trabajo, consulta los [Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows). + +#### Jobs + +Un job es un conjunto de pasos que se ejecutan en el mismo ejecutor. Predeterminadamente, un flujode trabajo con varios jobs los ejecutará en paralelo. También puedes configurar el flujo de trabajo para que los ejecute secuencialmente. Por ejemplo, un flujo de trabajo puede tener dos trabajos consecutivos para desarrollar y probar el código. El trabajo de prueba depende del estado del trabajo de desarrollo. Si el trabajo de desarrollo falla, no se ejecutará el trabajo de prueba. + +#### Pasos + +Un paso es una tarea individual que puede ejecutar comandos en un job. Un paso puede ser tanto una _acción_ como un comando de shell. Cada paso en un job se ejecuta en el mismo ejecutor, lo cual permite que las acciones en dicho job compartan datos entre ellas. + +#### Acciones + +Las _Acciones_ son comandos independientes que se combinan en _pasos_ para crear un _job_. Las acciones son el componente portable más pequeño de un flujo de trabajo. Puedes crear tus propias acciones, o utilizar acciones que haya creado la comunidad de {% data variables.product.prodname_dotcom %}. Para utilizar una acción en un flujo de trabajo, debes incluirla como paso. + +#### Ejecutores + +Un ejecutor es un servidor que tiene instalada la [aplilcación de ejecutor de {% data variables.product.prodname_actions %}](https://github.com/actions/runner). Puedes utilizar un ejecutor que esté hospedado en {% data variables.product.prodname_dotcom %}, o puedes hospedar el tuyo propio. Un ejecutor escucha a los jobs disponibles, ejecuta un job a la vez, y reporta el progreso, bitácoras y resultados de vuelta a {% data variables.product.prodname_dotcom %}. Para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, cada job en un flujo de trabajo se ejecuta en un ambiente virtual nuevo. + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se basan en Ubuntu Linux, Microsoft Windows, y macOS. Para encontrar más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Ambientes virtuales para ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/virtual-environments-for-github-hosted-runners)". Si necesitas un sistema operativo diferente o si requieres de una configuración de hardware específica, puedes hospedar tus propios ejecutores. Para obtener información sobre los ejecutores auto-hospedados, consulta la sección "[Hospedar tus propios ejecutores](/actions/hosting-your-own-runners)". + +### Crear un flujo de trabajo de ejemplo + +Las {% data variables.product.prodname_actions %} usan la sintaxis de YAML para definir los eventos, jobs y pasos. Estos archivos de YAML se almacenan en el repositorio de tu código, en un directorio que se llama `.github/workflows`. + +Puedes crear un flujo de trabajo de ejemplo en tu repositorio que active automáticamente una serie de comandos cada que se suba código. En este flujo de trabajo, las {% data variables.product.prodname_actions %} verifican el código que se subió, instalan las dependencias de software, y ejecutan `bats -v`. + +1. En tu repositorio, crea el directorio `.github/workflows/` para almacenar tus archivos de flujo de trabajo. +1. En el directorio `.github/workflows/`, crea un archivo nuevo que se llame `learn-github-actions.yml` y agrega el siguiente código. + ```yaml + name: learn-github-actions + on: [push] + jobs: + check-bats-version: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + - run: npm install -g bats + - run: bats -v + ``` +1. Confirma estos cambios y cárgalos a tu repositorio de {% data variables.product.prodname_dotcom %}. + +Tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %} nuevo estará ahora instalado en tu repositorio y se ejecutará automáticamente cada que alguien suba un cambio a éste. Para encontrar los detalles sobre el historial de ejecución un job, consulta la sección "[Visualizar la actividad del flujo de trabajo](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)". + +### Entender el archivo de flujo de trabajo + +Para ayudarte a entender cómo se utiliza la sintaxis de YAML para crear un flujo de trabajo, esta sección explica cada línea del ejemplo de la introducción: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + ```yaml + name: learn-github-actions + ``` + + Opcional - El nombre del flujo de trabajo ta como aparece en la pestaña de Acciones del repositorio de {% data variables.product.prodname_dotcom %}. +
    + + ```yaml + on: [push] + ``` + + Especifica el evento que activa automáticamente el archivo de flujo de trabajo. Este ejemplo utiliza el evento push, para que los jobs se ejecuten cada que alguien sube un cambio al repositorio. Puedes configurar el flujo de trabajo para que solo se ejecuten en ciertas ramas, rutas, o etiquetas. Para encontrar ejemplos de sintaxis que incluyan o excluyan ramas, rutas, o etiquetas, consulta la sección "Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}". +
    + + ```yaml + jobs: + ``` + + Agrupa los jobs que se ejecutan en el archivo de flujo de trabajo learn-github-actions. +
    + + ```yaml + check-bats-version: + ``` + + Define el nombre del job check-bats-version que se almacena en la sección jobs. +
    + + ```yaml + runs-on: ubuntu-latest + ``` + + Configura el job para ejecutarse en un ejecutor Ubuntu Linux. Esto significa que el job se ejecutará en una máquina virtual nueva que se hospede en GitHub. Para encontrar ejemplos de sintaxis que utilicen otros ejecutores, consulta la sección "Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}". +
    + + ```yaml + steps: + ``` + + Agrupa todos los pasos que se ejecutan en el job check-bats-version. Cada línea anidada bajo esta sección es una acción por separado. +
    + + ```yaml + - uses: actions/checkout@v2 + ``` + + La palabra clave uses le dice al job que recupere la v2 de la acción comunitaria que se llama actions/checkout@v2. Esta es una acción que revisa tu repositorio y lo descarga al ejecutor, lo que te permite ejecutar acciones contra tu código (tales como las herramientas de prueba). Debes utilizar la acción de verificación cada que tu flujo de trabajo se ejecute contra el código del repositorio o cada que estés utilizando una acción definida en el repositorio. +
    + + ```yaml + - uses: actions/setup-node@v1 + ``` + + Esta acción instala el paquete de software de node en el ejecutor, otorgándote acceso al comando npm. +
    + + ```yaml + - run: npm install -g bats + ``` + + La palabra clave run le dice al job que ejecute un comando en el ejecutor. Ene ste caso, estás utilizando npm para instalar el paquete de pruebas del software bats. +
    + + ```yaml + - run: bats -v + ``` + + Finalmente, ejecutarás el comando bats con un parámetro que producirá la versión del software. +
    + +#### Visualizar el archivo de flujo de trabajo + +En este diagrama, puedes ver el archivo de flujo de trabajo que acabas de crear, así como la forma en que los componentes de {% data variables.product.prodname_actions %} se organizan en una jerarquía. Cada paso ejecuta una acción simple o un comando de shell. Los pasos 1 y 2 utilizan acciones comunitarias preconstruidas. Los pasos 3 y 4 ejecutan comandos de shell directamente en el ejecutor. Para encontrar más acciones preconstruidas para tus flujos de trabajo, consulta la sección "[Encontrar y personalizar acciones](/actions/learn-github-actions/finding-and-customizing-actions)". + +![Resumen del flujo de trabajo](/assets/images/help/images/overview-actions-event.png) + + +### Visualizar la actividad de un job + +Una vez que tu job ha comenzado a ejecutarse, podrás{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}ver una gráfica de visualización del progreso de dicha ejecución y {% endif %}ver la actividad de cada paso en {% data variables.product.prodname_dotcom %}. + +{% data reusables.repositories.navigate-to-repo %} +1. Debajo del nombre de tu repositorio, da clic en **Acciones**. ![Navegar al repositorio](/assets/images/help/images/learn-github-actions-repository.png) +1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieras ver. ![Impresión de pantalla de los resultados del flujo de trabajo](/assets/images/help/images/learn-github-actions-workflow.png) +1. Debajo de "Ejecuciones de flujo de trabajo", da clic en el nombre de la ejecución que quieres ver. ![Captura de pantalla de las ejecuciones del flujo de trabajo](/assets/images/help/images/learn-github-actions-run.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Debajo de **Jobs** o en la gráfica de visualización, da clic en el job que quieras ver. ![Seleccionar job](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Ve los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} +1. Da clic en el nombre del job para ver los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result-updated.png) +{% else %} +1. Da clic en el nombre del job para ver los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result.png) +{% endif %} + +### Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)". + +### Contactar con soporte técnico + +{% data reusables.github-actions.contacting-support %} diff --git a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md new file mode 100644 index 0000000000000..e73669ebcf689 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md @@ -0,0 +1,169 @@ +--- +title: Administrar flujos de trabajo complejos +shortTitle: Administrar flujos de trabajo complejos +intro: 'Esta guía te muestra cómo utilizar las características avanzadas de {% data variables.product.prodname_actions %} con administración de secretos, jobs dependientes, almacenamiento en caché, matrices de compilación,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ambientes,{% endif %}y etiquetas.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'how_to' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Este artículo describe algunas de las características avanzadas de las {% data variables.product.prodname_actions %} que te ayuden a crear flujos de trabajo más complejos. + +### Almacenar secretos + +Si tus flujos de trabajo utilizan datos sensibles tales como contraseñas o certificados, puedes guardarlos en {% data variables.product.prodname_dotcom %} como _secretos_ y luego usarlos en tus flujos de trabajo como variables de ambiente. Esto significa que podrás crear y compartir flujos de trabajo sin tener que embeber valores sensibles directamente en el flujo de trabajo de YAML. + +Esta acción de ejemplo ilustra cómo referenciar un secreto existente como una variable de ambiente y enviarla como parámetro a un comando de ejemplo. + +{% raw %} +```yaml +jobs: + example-job: + runs-on: ubuntu-latest + steps: + - name: Retrieve secret + env: + super_secret: ${{ secrets.SUPERSECRET }} + run: | + example-command "$super_secret" +``` +{% endraw %} + +Para obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". + +### Crear jobs dependientes + +Predeterminadamente, los jobs en tu flujo de trabajo se ejecutan todos en paralelo y al mismo tiempo. Así que, si tienes un job que solo debe ejecutarse después de que se complete otro job, puedes utilizar la palabra clave `needs` para crear esta dependencia. Si un de los jobs falla, todos los jobs dependientes se omitirán; sin embargo, si necesitas que los jobs sigan, puedes definir esto utilizando la declaración condicional [`if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif). + +En este ejemplo, los jobs de `setup`, `build`, y `test` se ejecutan en serie, y `build` y `test` son dependientes de que el job que las precede se complete con éxito: + +```yaml +jobs: + setup: + runs-on: ubuntu-latest + steps: + - run: ./setup_server.sh + build: + needs: setup + runs-on: ubuntu-latest + steps: + - run: ./build_server.sh + test: + needs: build + runs-on: ubuntu-latest + steps: + - run: ./test_server.sh +``` + +Para obtener más información, consulta la parte de [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). + +### Utilizar una matriz de compilaciones + +Puedes utilizar una matriz de compilaciones si quieres que tu flujo de trabajo ejecute pruebas a través de varias combinaciones de sistemas operativos, plataformas y lenguajes. La matriz de compilaciones se crea utilizando la palabra clave `strategy`, la cual recibe las opciones de compilación como un arreglo. Por ejemplo, esta matriz de compilaciones ejecutará el job varias veces, utilizando diferentes versiones de Node.js: + +{% raw %} +```yaml +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + node: [6, 8, 10] + steps: + - uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node }} +``` +{% endraw %} + +Para obtener más información, consulta la parte de [`jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). + +### Almacenar dependencias en caché + +Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se inician como ambientes nuevos para cada job, así que, si tus jobs utilizan dependencias a menudo, puedes considerar almacenar estos archivos en caché para ayudarles a mejorar el rendimiento. Una vez que se crea el caché, estará disponible para todos los flujos de trabajo en el mismo repositorio. + +Este ejemplo ilustra cómo almacenar el directorio `~/.npm` en el caché: + +{% raw %} +```yaml +jobs: + example-job: + steps: + - name: Cache node modules + uses: actions/cache@v2 + env: + cache-name: cache-node-modules + with: + path: ~/.npm + key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }} + restore-keys: | + ${{ runner.os }}-build-${{ env.cache-name }}- +``` +{% endraw %} + +Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +### Usar bases de datos y contenedores de servicio + +Si tu job requiere de un servicio de caché o de base de datos, puedes utilizar la palabra clave [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) para crear un contenedor efímero para almacenar el servicio; el contenedor resultante estará entonces disponible para todos los pasos de ese job y se eliminará cuando el job se haya completado. Este ejemplo ilustra como un job puede utilizar `services` para crear un contenedor de `postgres` y luego utilizar a `node` para conectarse al servicio. + +```yaml +jobs: + container-job: + runs-on: ubuntu-latest + container: node:10.18-jessie + services: + postgres: + image: postgres + steps: + - name: Check out repository code + uses: actions/checkout@v2 + - name: Install dependencies + run: npm ci + - name: Connect to PostgreSQL + run: node client.js + env: + POSTGRES_HOST: postgres + POSTGRES_PORT: 5432 +``` + +Para obtener más información, consulta la sección "[Utilizar bases de datos y contenedores de servicios](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)". + +### Utilizar etiquetas para enrutar los flujos de trabajo + +Esta característica te ayuda a asignar jobs a un ejecutor auto-hospedado específico. Si quieres asegurarte de que un tipo específico de ejecutor procesará tu job, puedes utilizar etiquetas para controlar donde se ejecutan los jobs. Puedes asignar etiquetas a un ejecutor auto-hospedado y luego referirte a estas etiquetas en tu flujo de trabajo de YAML, garantizado que el job se enrute de una forma predecible. + +Este ejemplo muestra como un flujo de trabajo puede utilizar etiquetas para especificar el ejecutor requerido: + +```yaml +jobs: + example-job: + runs-on: [self-hosted, linux, x64, gpu] +``` + +Para obtener más información, consulta la sección ["Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Utilizar ambientes + +Puedes configurr ambientes con reglas de protección y secretos. Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. Para obtener más información, consulta la sección "[Ambientes](/actions/reference/environments)". +{% endif %} + +### Utilizar una plantilla de flujo de trabajo + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. Si tu repositorio ya cuenta con flujos de trabajo: En la esquina superior izquierda, da clic sobre **Flujo de trabajo nuevo**. ![Crear un nuevo flujo de trabajo](/assets/images/help/repository/actions-new-workflow.png) +1. Debajo del nombre de la plantilla que deseas utilizar, da clic en **Configurar este flujo de trabajo**. ![Configurar este flujo de trabajo](/assets/images/help/settings/actions-create-starter-workflow.png) + +### Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Compartir flujos de trabajo con tu organización](/actions/learn-github-actions/sharing-workflows-with-your-organization)". diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md new file mode 100644 index 0000000000000..14ff67e491eeb --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -0,0 +1,327 @@ +--- +title: Migrar de Azure Pipelines a GitHub Actions +intro: '{% data variables.product.prodname_actions %} y Azure Pipelines comparten varias configuraciones similares, lo cual hace que migrar a {% data variables.product.prodname_actions %} sea relativamente sencillo.' +redirect_from: + - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Tanto Azure Pipelines como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. Azure Pipelines y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo: + +- Los archivos de configuración de flujo de trabajo están escritas en YAML y se almacenan en el repositorio del código. +- Los flujos de trabajo incluyen uno o más jobs. +- Los jobs incluyen uno o más pasos o comandos individuales. +- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad. + +Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)". + +### Diferencias clave + +Cuando migres desde Azure Pipelines, considera las siguientes diferencias: + +- Azure Pipelines soporta un _editor clásico_ tradicional, lo cual te permite definir tu configuración de IC en un editor de GUI en vez de crear la definición de mapa en un archivo YAML. {% data variables.product.prodname_actions %} utiliza archivos YAML para definir flujos de trabajo y no es compatible con un editor gráfico. +- Azure Pipelines te permite omitir parte de la estructura en las definiciones de jobs. Por ejemplo, si solo tienes un job, no necesitas definirlo y solo necesitas definir sus pasos. {% data variables.product.prodname_actions %} requiere una configuración específica y no se puede omitir la estructura de YAML. +- Azure Pipelines es compatible con las _etapas_ que se definen en el archivo YAML, las cuales se pueden utilizar para crear flujos de trabajo de despliegue. {% data variables.product.prodname_actions %} necesita que separes las etapas en archivos de flujo de trabajo de YAML diferentes. +- Azure Pipelines instalado localmente compila agentes que pueden seleccionarse con capacidades. Los ejecutores auto-hospedados de {% data variables.product.prodname_actions %} pueden seleccionarse con etiquetas. + +### Migrar jobs y pasos + +Los jobs y los pasos en Azure Pipelines son muy similares a aquellos en {% data variables.product.prodname_actions %}. En ambos sistemas, los jobs tienen las siguientes características: + +* Los jobs contienen una serie de pasos que se ejecutan en secuencia. +* Los jobs se ejecutan en máquinas virtuales separadas o en contenedores separados. +* Los jobs se ejecutan en paralelo predeterminadamente, pero pueden configurarse para ejecutarse en secuencia. + +### Migrar los pasos de un script + +Puedes ejecutar un script o comando de shell como un paso en un flujo de trabajo. En Azure Pipelines, los pasos de un script pueden especificarse utilizando la clave `script`, o con las claves `bash`, `powershell`, o `pwsh`. Los scripts también pueden especificarse como una entrada a la [tarea Bash](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) o la [tarea PowerShell](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops). + +En {% data variables.product.prodname_actions %}, todos los scripts se especifican utilizando la clave `run`. Para seleccionar un shell en particular, puedes especificar la clave `shell` cuando proporciones el script. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Azure Pipelines + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +jobs: +- job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + scripts: + runs-on: windows-latest + steps: + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell +``` +{% endraw %} +
    + +### Diferencias en el manejo de errores de los scripts + +En Azure Pipelines, los scripts se pueden configurar para generar un error si cualquier salida se envía a `stderr`. {% data variables.product.prodname_actions %} no es compatible con esta configuración. + +{% data variables.product.prodname_actions %} configura shells para que "fallen rápidamente" cuando sea posible, lo cual detiene el script inmediatamente si alguno de los comandos en éste sale con un código de error. En contraste, Azure Pipelines requiere de una configuración explícita para salir inmediatamente en caso de error. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)". + +### Diferencias con el shell predeterminado de Windows + +En Azure Pipelines, el shell predeterminado para los scripts en plataformas Windows es el Símbolo de Sistema (_cmd.exe_). En {% data variables.product.prodname_actions %}, el shell predeterminado para los scripts en plataformas Windows es PowerShell. PowerShell tiene varias diferencias en comandos integrados, expansión de variables y control de flujo. + +Si estás utilizando un comando simple, es posible que puedas ejecutar un script de Símbolo de Sistema en PowerShell sin tener que realizar cambios. Pero en la mayoría de los casos, tendrás que actualizar tu script con la sintaxis de PowerShell o dar la instrucción a {% data variables.product.prodname_actions %} para ejecutar el script con el Símbolo de Sistema en vez de con PowerShell. Puedes hacer esto especificando `shell` como `cmd`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Azure Pipelines + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +jobs: +- job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + run_command: + runs-on: windows-latest + steps: + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)". + +### Migrar la sintaxis de expresión y los condicionales + +Tanto Azure Pipelines como {% data variables.product.prodname_actions %} pueden ejecutar pasos condicionalmente. En Azure Pipelines, las expresiones condicionales se especifican utilizando la clave `condition`. En {% data variables.product.prodname_actions %}, las expresiones condicionales se especifican utilizando la clave `if`. + +Azure Pipelines utiliza funciones dentro de las expresiones para ejecutar los pasos condicionalmente. En contraste, {% data variables.product.prodname_actions %} utiliza una notación infija. Por ejemplo, puedes reemplazar la función `eq` en Azure Pipelines con el operador `==` en {% data variables.product.prodname_actions %}. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Azure Pipelines + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +jobs: +- job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + conditional: + runs-on: ubuntu-latest + steps: + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} +``` +{% endraw %} +
    + +Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +### Dependencias entre jobs + +Tanto Azure Pipelines como {% data variables.product.prodname_actions %} te permiten configurar dependencias par un job. En ambos sistemas, los jobs se ejecutan en paralelo predeterminadamente, pero las dependencias de estos pueden especificarse explícitamente. En Azure Pipelines, esto se hace con la clave `dependsOn`. En {% data variables.product.prodname_actions %}, esto se hace con la clave `needs`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema. El flujo de trabajo comienza un primer job llamado `initial`, y cuando este job se completa, se ejecutarán dos jobs llamados `fanout1` y `fanout2`. Finalmente, cuando se completen estos dos jobs, se ejecutará el job `fanin`. + + + + + + + + + + +
    +Azure Pipelines + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +jobs: +- job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." +- job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." +- job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." +- job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + initial: + runs-on: ubuntu-latest + steps: + - run: echo "This job will be run first." + fanout1: + runs-on: ubuntu-latest + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout2." + fanout2: + runs-on: ubuntu-latest + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout1." + fanin: + runs-on: ubuntu-latest + needs: [fanout1, fanout2] + steps: + - run: echo "This job will run after fanout1 and fanout2 have finished." +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". + +### Migrar las tareas a acciones + +Azure Pipelines utiliza _tareas_, que son componentes de las aplicaciones que pueden reutilizarse en varios flujos de trabajo. {% data variables.product.prodname_actions %} utiliza_acciones_, que se pueden utilizar para realizar tareas y personalizar tu flujo de trabajo. En ambos sistemas, puedes especificar el nombre de la tarea o acción a ejecutar junto con cualquier entrada requerida como pares de clave/valor. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Azure Pipelines + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +jobs: +- job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + run_python: + runs-on: ubuntu-latest + steps: + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py +``` +{% endraw %} +
    + +Puedes encontrar acciones que puedas utilizar en tu flujo de trabajo en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), o puedes crear tus propias acciones. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)". diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md new file mode 100644 index 0000000000000..cd1348761a736 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -0,0 +1,448 @@ +--- +title: Migrar de CircleCI a GitHub Actions +intro: 'GitHub Actions y CircleCi comparten varias configuraciones similares, lo cual hace que migrar a GitHub Actions sea relativamente fácil.' +redirect_from: + - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Tanto CircleCi como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. CircleCI y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo: + +- Los archivos de configuración de flujo de trabajo están escritos en YAML y se almacenan en el repositorio. +- Los flujos de trabajo incluyen uno o más jobs. +- Los jobs incluyen uno o más pasos o comandos individuales. +- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad. + +Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)". + +### Diferencias clave + +Cuando migres desde CircleCI, considera las siguientes diferencias: + +- El paralelismo automático de pruebas de CircleCI agrupa las pruebas automáticamente de acuerdo con las reglas que el usuario haya especificado o el historial de información de tiempos. Esta funcionalidad no se incluye en {% data variables.product.prodname_actions %}. +- Las acciones que se ejecutan en los contenedores de Docker distinguen entre problemas de permisos, ya que los contenedores tienen un mapeo de usuarios diferente. Puedes evitar muchos de estos problemas si no utilizas la instrucción `USER` en tu *Dockerfile*. Para obtener más información acerca del sistema de archivos de Docker, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)". + +### Migrar flujos de trabajo y jobs + +CircleCi define los `workflows` en el archivo *config.yml*, lo cual te permite configurar más de un flujo de trabajo. {% data variables.product.product_name %} requiere tratar los flujos de trabajo uno por uno y, como consecuencia, no necesita que declares los `workflows`. Necesitarás crear un nuevo archivo de flujo de trabajo para cada flujo que se haya configurado en *config.yml*. + +Tanto CircleCI como {% data variables.product.prodname_actions %} configuran `jobs` en el archivo de configuración utilizando una sintaxis similar. Si configurars cualquier dependencia entre jobs utilizando `requires` en tu flujo de trabajo de CircleCI, puedes utilizar la sintaxis de {% data variables.product.prodname_actions %} equivalente "`needs`". Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". + +### Mirgrar orbes a acciones + +Tanto CircleCI como {% data variables.product.prodname_actions %} proporcionan un mecanismo para reutilizar y compartir tareas en un flujo de trabajo. CircleCi utiliza un concepto llamado orbes (orbs), escrito en YAML, que proporciona tareas que las personas pueden reutilizar en un flujo de trabajo. {% data variables.product.prodname_actions %} cuenta con componentes reutilizables poderosos y flexibles llamados acciones (actions), los cuales compilas ya sea con archivos de JavaScript o con imagenes de Docker. Puedes crear acciones por medio de a escritura de un código personalizado que interactúe con tu repositorio de la manera que desees, incluida la integración con las API de {% data variables.product.product_name %} y cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)". + +Circle CI puede reutilizar partes de los flujos de trabajo con anclas y alias. {% data variables.product.prodname_actions %} es compatible con las necesidades de reutilización más comunes utilizando matrices de compilación. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)". + +### Utilizar imágenes de Docker + + +Tanto CircleCi como {% data variables.product.prodname_actions %} son compatibles con la ejecución de pasos dentro de una imagen de Docker. + +CircleCi proporciona un conjunto de imágenes pre-compiladas con dependencias comunes. Estas imágenes cuentan con el `USER` configurado como `circleci`, lo cual ocasiona que los permisos choquen con {% data variables.product.prodname_actions %}. + +Recomendamos que te retires de las imágenes pre-compiladas de CircleCi cuando migres a {% data variables.product.prodname_actions %}. En muchos casos, puedes utilizar acciones para instalar dependencias adicionales que necesites. + +Para obtener más información acerca del sistema de archivos de Docker, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)". + +Para obtener más información acerca de las herramientas y paquetes disponibles en los ambientes virtuales hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +### Utilizar variables y secretos + +CircleCi y {% data variables.product.prodname_actions %} son compatibles con la configuración de variables de ambiente en el archivo de configuración y con la creación de secretos utilizando la IU de CircleCI o de {% data variables.product.product_name %}. + +Para obtener más información, consulta la sección "[Utilizar variables de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y "[Crear y utilizar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". + +### Almacenamiento en caché + +CircleCI y {% data variables.product.prodname_actions %} proporcionan un método para almacenar archivos en cahcé manualmente en el archivo de configuración. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema. + + + + + + + + + + +
    +CircleCI + +GitHub Actions +
    +{% raw %} +```yaml +- restore_cache: + keys: + - v1-npm-deps-{{ checksum "package-lock.json" }} + - v1-npm-deps- +``` +{% endraw %} + +{% raw %} +```yaml +- name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- +``` +{% endraw %} +
    + +El almacenamiento en caché de {% data variables.product.prodname_actions %} solo aplica a los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +{% data variables.product.prodname_actions %} no tiene un equivalente al Almacenamiento en Caché por Capas de Docker (o DLC, por sus siglas en inglés) que tiene CircleCI. + +### Datos persistentes entre jobs + +Tanto CircleCi como {% data variables.product.prodname_actions %} proporcionan mecanismos para persistir datos entre jobs. + +A continuación puedes encontrar un ejemplo de la sintaxis de configuración de CircleCi y de {% data variables.product.prodname_actions %}. + + + + + + + + + + +
    +CircleCI + +GitHub Actions +
    +{% raw %} +```yaml +- persist_to_workspace: + root: workspace + paths: + - math-homework.txt + +... + +- attach_workspace: + at: /tmp/workspace +``` +{% endraw %} + +{% raw %} +```yaml +- name: Upload math result for job 1 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt + +... + +- name: Download math result for job 1 + uses: actions/download-artifact@v2 + with: + name: homework +``` +{% endraw %} +
    + +Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)." + +### Usar bases de datos y contenedores de servicio + +Ambos sistemas te permiten incluir contenedores adicionales para bases de datos, almacenamiento en caché, u otras dependencias. + +En CircleCi, la primera imagen listada en el *config.yaml* es la imagen primaria que se utiliza para ejecutar comandos. {% data variables.product.prodname_actions %} utiliza secciones explícitas: utiliza `container` para el contenedor primario, y lista contenedores adicionales en `services`. + +A continuación puedes encontrar un ejemplo de la sintaxis de configuración de CircleCi y de {% data variables.product.prodname_actions %}. + + + + + + + + + + +
    +CircleCI + +GitHub Actions +
    +{% raw %} +```yaml +--- +version: 2.1 + +jobs: + + ruby-26: + docker: + - image: circleci/ruby:2.6.3-node-browsers-legacy + environment: + PGHOST: localhost + PGUSER: administrate + RAILS_ENV: test + - image: postgres:10.1-alpine + environment: + POSTGRES_USER: administrate + POSTGRES_DB: ruby26 + POSTGRES_PASSWORD: "" + + working_directory: ~/administrate + + steps: + - checkout + + # Bundle install dependencies + - run: bundle install --path vendor/bundle + + # Wait for DB + - run: dockerize -wait tcp://localhost:5432 -timeout 1m + + # Setup the environment + - run: cp .sample.env .env + + # Setup the database + - run: bundle exec rake db:setup + + # Run the tests + - run: bundle exec rake + + +workflows: + version: 2 + build: + jobs: + - ruby-26 +... + +- attach_workspace: + at: /tmp/workspace +``` +{% endraw %} + +{% raw %} +```yaml +name: Containers + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + container: circleci/ruby:2.6.3-node-browsers-legacy + + env: + PGHOST: postgres + PGUSER: administrate + RAILS_ENV: test + + services: + postgres: + image: postgres:10.1-alpine + env: + POSTGRES_USER: administrate + POSTGRES_DB: ruby25 + POSTGRES_PASSWORD: "" + ports: + - 5432:5432 + # Add a health check + options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 + + steps: + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Acerca de los contenedores de servicio](/actions/configuring-and-managing-workflows/about-service-containers)". + +### Ejemplo Completo + +A continuación encontrarás un ejemplo real. A la izquierda puedes ver el *config.yml* real de CircleCi para el repositorio [thoughtbot/administrator](https://github.com/thoughtbot/administrate). La derecha muestra el equivalente en {% data variables.product.prodname_actions %}. + + + + + + + + + + +
    +CircleCI + +GitHub Actions +
    +{% raw %} +```yaml +--- +version: 2.1 + +commands: + shared_steps: + steps: + - checkout + + # Restore Cached Dependencies + - restore_cache: + name: Restore bundle cache + key: administrate-{{ checksum "Gemfile.lock" }} + + # Bundle install dependencies + - run: bundle install --path vendor/bundle + + # Cache Dependencies + - save_cache: + name: Store bundle cache + key: administrate-{{ checksum "Gemfile.lock" }} + paths: + - vendor/bundle + + # Wait for DB + - run: dockerize -wait tcp://localhost:5432 -timeout 1m + + # Setup the environment + - run: cp .sample.env .env + + # Setup the database + - run: bundle exec rake db:setup + + # Run the tests + - run: bundle exec rake + +default_job: &default_job + working_directory: ~/administrate + steps: + - shared_steps + # Run the tests against multiple versions of Rails + - run: bundle exec appraisal install + - run: bundle exec appraisal rake + +jobs: + ruby-25: + <<: *default_job + docker: + - image: circleci/ruby:2.5.0-node-browsers + environment: + PGHOST: localhost + PGUSER: administrate + RAILS_ENV: test + - image: postgres:10.1-alpine + environment: + POSTGRES_USER: administrate + POSTGRES_DB: ruby25 + POSTGRES_PASSWORD: "" + + ruby-26: + <<: *default_job + docker: + - image: circleci/ruby:2.6.3-node-browsers-legacy + environment: + PGHOST: localhost + PGUSER: administrate + RAILS_ENV: test + - image: postgres:10.1-alpine + environment: + POSTGRES_USER: administrate + POSTGRES_DB: ruby26 + POSTGRES_PASSWORD: "" + + +workflows: + version: 2 + multiple-rubies: + jobs: + - ruby-26 + - ruby-25 +``` +{% endraw %} + +{% raw %} +```yaml +name: Containers + +on: [push] + +jobs: + build: + + strategy: + matrix: + ruby: [2.5, 2.6.3] + + runs-on: ubuntu-latest + + env: + PGHOST: localhost + PGUSER: administrate + RAILS_ENV: test + + services: + postgres: + image: postgres:10.1-alpine + env: + POSTGRES_USER: administrate + POSTGRES_DB: ruby25 + POSTGRES_PASSWORD: "" + ports: + - 5432:5432 + # Add a health check + options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 + + steps: + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake +``` +{% endraw %} +
    diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md new file mode 100644 index 0000000000000..8ddea2c002b6b --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -0,0 +1,477 @@ +--- +title: Migrarse desde la IC/EC de GitLab a GitHub Actions +intro: '{% data variables.product.prodname_actions %} y la IC/EC de GitLab comparten varias similitudes de configuración, lo cual hace que el migrarse a {% data variables.product.prodname_actions %} sea relativamente simple.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que crean, prueban, publican, lanzan y despliegan código automáticamente. La IC/EC de GitLab y las {% data variables.product.prodname_actions %} comparten algunas similitudes en la configuración de los flujos de trabajo: + +- Los archivos de configuración de flujo de trabajo están escritas en YAML y se almacenan en el repositorio del código. +- Los flujos de trabajo incluyen uno o más jobs. +- Los jobs incluyen uno o más pasos o comandos individuales. +- Los jobs pueden ejecutarse ya sea en máquinas administradas o auto-hospedadas. + +Hay unas cuantas diferencias, y esta guía te mostrará las diferencias importantes para que puedas migrar tu flujo de trabajo a {% data variables.product.prodname_actions %}. + +### Jobs + +Los jobs en la IC/EC de GitLab son muy similares a aquellos en {% data variables.product.prodname_actions %}. En ambos sistemas, los jobs tienen las siguientes características: + +* Los jobs contienen una serie de pasos o scripts que se ejecutan secuencialmente. +* Los jobs pueden ejecutarse en máquinas o contenedores separados. +* Los jobs se ejecutan en paralelo predeterminadamente, pero pueden configurarse para ejecutarse en secuencia. + +Puedes ejecutar un script o un comando de shell en un job. En la IC/EC de GitLab, los pasos de los scripts se especifican utilizando la clave `script`. En {% data variables.product.prodname_actions %}, todos los scripts se especifican utilizando la clave `run`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +job1: + variables: + GIT_CHECKOUT: "true" + script: + - echo "Run your script here" +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + job1: + steps: + - uses: actions/checkout@v2 + - run: echo "Run your script here" +``` +{% endraw %} +
    + +### Ejecutores + +Los ejecutores son máquinas en donde se ejecutan los jobs. Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} ofrecen variantes administradas y auto-hospedadas de los ejecutores. En la IC/EC de GitLab, se utilizan las `tags` para ejecutar jobs en plataformas diferentes, mientras que en las {% data variables.product.prodname_actions %} todo se realiza con la clave `runs-on`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +windows_job: + tags: + - windows + script: + - echo Hello, %USERNAME%! + +linux_job: + tags: + - linux + script: + - echo "Hello, $USER!" +``` +{% endraw %} + +{% raw %} +```yaml +windows_job: + runs-on : windows-latest + steps: + - run: echo Hello, %USERNAME%! + +linux_job: + runs-on: ubuntu-latest + steps: + - run: echo "Hello, $USER!" +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)". + +### Imágenes de Docker + +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} son compatibles con la ejecución de jobs en una imagen de Docker. En la IC/EC de GitLab, las imágenes de Docker se definen con una clave de `image`, mientras que en las {% data variables.product.prodname_actions %} se hace con la clave `container`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +my_job: + image: node:10.16-jessie +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + my_job: + container: node:10.16-jessie +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)". + +### Sintaxis de condiciones y expresiones + +La IC/EC de GitLab utiliza `rules` para determinar si un job se ejecutará para una condición específica. Las {% data variables.product.prodname_actions %} utilizan la palabra clave `if` para prevenir que un job se ejecute a menos de que se cumpla con una condición. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +deploy_prod: + stage: deploy + script: + - echo "Deploy to production server" + rules: + - if: '$CI_COMMIT_BRANCH == "master"' +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + deploy_prod: + if: contains( github.ref, 'master') + runs-on: ubuntu-latest + steps: + - run: echo "Deploy to production server" +``` +{% endraw %} +
    + +Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +### Dependencias entre los Jobs + +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten configurar dependencias para un job. En ambos sistemas, los jobs se ejecutan en paralelo predeterminadamente, pero las dependencias de éstos en las {% data variables.product.prodname_actions %} se pueden especificar explícitamente con la clave `needs`. La IC/EC de GitLab también tiene un concepto de `stages`, en donde los jobs de una etapa se ejecutan simultáneamente, pero la siguiente etapa comenzaría cuando todos los jobs de la etapa previa se hayan completado. Puedes crecrear este escenario en las {% data variables.product.prodname_actions %} con la palabra clave `needs`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema. Los flujos de trabajo comienzan con dos jobs que se llaman `build_a` y `build_b` ejecutándose en paralelo y, cuando estos jobs se completan, se ejecutará otro job llamado `test_ab`. Finalmente, cuando se completa el `test_ab`, se ejecutará el job `deploy_ab`. + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +stages: + - build + - test + - deploy + +build_a: + stage: build + script: + - echo "This job will run first." + +build_b: + stage: build + script: + - echo "This job will run first, in parallel with build_a." + +test_ab: + stage: test + script: + - echo "This job will run after build_a and build_b have finished." + +deploy_ab: + stage: deploy + script: + - echo "This job will run after test_ab is complete" +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + build_a: + runs-on: ubuntu-latest + steps: + - run: echo "This job will be run first." + + build_b: + runs-on: ubuntu-latest + steps: + - run: echo "This job will be run first, in parallel with build_a" + + test_ab: + runs-on: ubuntu-latest + needs: [build_a,build_b] + steps: + - run: echo "This job will run after build_a and build_b have finished" + + deploy_ab: + runs-on: ubuntu-latest + needs: [test_ab] + steps: + - run: echo "This job will run after test_ab is complete" +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". + +### Programar flujos de trabajo + +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten ejecutar flujos de trabajo en un intervalo específico. En la IC/EC de GitLab, las programaciones de mapa se configuran con la IU, mientras que en las {% data variables.product.prodname_actions %} puedes activar un flujo de trabajo en un intervalo programado con la clave "on". + +Para obtener más información, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#scheduled-events)". + +### Variables y secretos + +La IC/EC de GitLab y las {% data variables.product.prodname_actions %} son compatibles con la configuración de variables de ambiente en el mapa o en el archivo de configuración de flujo de trabajo, y con la creación de secretos utilizando la IU de GitLab o de {% data variables.product.product_name %}. + +Para obtener más información, consulta las secciones "[Variables de ambiente](/actions/reference/environment-variables)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)". + +### Almacenamiento en caché + +La IC/EC de GitLab y las {% data variables.product.prodname_actions %} proporcionan un método en el archivo de configuración para guardar los archivos de flujo de trabajo manualmente en el caché. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +image: node:latest + +cache: + key: $CI_COMMIT_REF_SLUG + paths: + - .npm/ + +before_script: + - npm ci --cache .npm --prefer-offline + +test_async: + script: + - node ./specs/start.js ./specs/async.spec.js +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + test_async: + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- +``` +{% endraw %} +
    + +El almacenamiento en caché de {% data variables.product.prodname_actions %} solo aplica a los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +### Artefactos + +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} pueden cargar como artefactos los archivos y directorios que creen los jobs. En las {% data variables.product.prodname_actions %}, los artefactos pueden utilizarse para persistir los datos a través de varios jobs. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +script: +artifacts: + paths: + - math-homework.txt +``` +{% endraw %} + +{% raw %} +```yaml +- name: Upload math result for job 1 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Almacenar los datos de los flujos de trabajo como artefactos](/actions/guides/storing-workflow-data-as-artifacts)". + +### Bases de datos y contenedores de servicios + +Ambos sistemas te permiten incluir contenedores adicionales para bases de datos, almacenamiento en caché, u otras dependencias. + +En la IC/EC de GitLab, un contenedor para el job se especifica con la clave `image` key, mientras que las {% data variables.product.prodname_actions %} utilizan la clave `container`. En ambos sistemas se especifican contenedores de servicio adicionales con la clave `services`. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +IC/EC de GitLab + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +container-job: + variables: + POSTGRES_PASSWORD: postgres + # The hostname used to communicate with the + # PostgreSQL service container + POSTGRES_HOST: postgres + # The default PostgreSQL port + POSTGRES_PORT: 5432 + image: node:10.18-jessie + services: + - postgres + script: + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js + tags: + - docker +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + container-job: + runs-on: ubuntu-latest + container: node:10.18-jessie + + services: + postgres: + image: postgres + env: + POSTGRES_PASSWORD: postgres + + steps: + - name: Check out repository code + uses: actions/checkout@v2 + + # Performs a clean installation of all dependencies + # in the `package.json` file + - name: Install dependencies + run: npm ci + + - name: Connect to PostgreSQL + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + run: node client.js + env: + # The hostname used to communicate with the + # PostgreSQL service container + POSTGRES_HOST: postgres + # The default PostgreSQL port + POSTGRES_PORT: 5432 +``` +{% endraw %} +
    + +Para obtener más información, consulta la sección "[Acerca de los contenedores de servicio](/actions/guides/about-service-containers)". diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md new file mode 100644 index 0000000000000..119a408105830 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -0,0 +1,292 @@ +--- +title: Migrar de Jenkins a GitHub Actions +intro: '{% data variables.product.prodname_actions %} y Jenkins comparten varias similaridades, lo cual hace que migrar a {% data variables.product.prodname_actions %} sea relativamente sencillo.' +redirect_from: + - /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Tanto Jenkins como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. Jenkins y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo: + +- Jenkins crea flujos de trabajo utilizando _Mapas Declarativos_, los cuales son similares a los archivos de flujo de trabajo de {% data variables.product.prodname_actions %}. +- Jenkins utiliza _etapas_ para ejecutar un conjunto de pasos, mientras que {% data variables.product.prodname_actions %} utiliza jobs para agrupar uno o mas pasos o comandos individuales. +- Jenkins y {% data variables.product.prodname_actions %} son compatibles con compilaciones basadas en el contenedor. Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)". +- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad. + +Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)". + +### Diferencias clave + +- Jenkins tiene dos tipos de sintaxis para crear mapas: Mapa Declarativo y Mapa de Script. {% data variables.product.prodname_actions %} utiliza YAML para crear flujos de trabajo y archivos de configuración. Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)". +- Los despliegues de jenkins son típicamente auto-hospedados y los usuarios mantienen los servidores en sus propios centros de datos. {% data variables.product.prodname_actions %} ofrece un acercamiento híbrido en la nube, hospedando sus propios ejecutores que puedes utilizar para ejecutar jobs, mientras que también son compatibles con ejecutores auto-hospedados. Para obtener más información, consulta la sección [Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners). + +### Comparación de capacidades + +#### Distribuir tus compilaciones + +Jenkis te permite enviar compilaciones a un agente de compilación sencilla, o puedes distribuirlas a través de varios agentes. También puedes clasificar estos agentes de acuerdo con diversos atributos, tales como los tipos de sistema operativo. + +De forma similar, las {% data variables.product.prodname_actions %} pueden enviar jobs a los ejecutores auto-hospedados u hospedados en {% data variables.product.prodname_dotcom %}, y puedes utilizar etiquetas para clasificar los ejecutores de acuerdo con diversos atributos. La siguiente tabla compara cómo se implementa el concepto de compilación distribuido tanto para Jenkins como para {% data variables.product.prodname_actions %}. + +| Jenkins | {% data variables.product.prodname_actions %} +| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | + +#### Utilizar secciones para organizar mapas + +Jenkins divide sus Mapas Declarativos en varias secciones. De forma similar, las {% data variables.product.prodname_actions %} organizan sus flujos de trabajo en secciones separadas. En esta tabla se comparan las secciones de Jenkins con el flujo de trabajo de {% data variables.product.prodname_actions %}. + +| Directivas de Jenkins | {% data variables.product.prodname_actions %} +| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent) | [`jobs..runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)
    [`jobs..container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) | +| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post) | | +| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`Trabajos`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | +| [`pasos`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | + + +### Utilizar directivas + +Jenkins utiliza directivas para administrar los _Mapas Declarativos_. Estas directivas definen las características de tu flujo de trabajo y la manera en que se ejecuta. La tabla siguiente demuestra cómo dichas directivas mapean los conceptos en {% data variables.product.prodname_actions %}. + +| Directivas de Jenkins | {% data variables.product.prodname_actions %} +| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
    [`jobs..steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) | +| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
    [`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
    [`jobs..timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) | +| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
    [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) | +| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on)
    [`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
    [on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)
    [on..paths](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) | +| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs..needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) | +| [Sintaxis de Jenkins cron](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax) | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) | +| [`stage`](https://jenkins.io/doc/book/pipeline/syntax/#stage) | [`jobs.`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id)
    [`jobs..name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname) | +| [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools) | [Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | +| [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs (entrada)`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | +| [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | + + +### Utilizar etapas secuenciales + +#### Proceso paralelo de jobs + +Jenkins puede ejecutar las `stages` y `steps` en paralelo, mientras que, actualmente, {% data variables.product.prodname_actions %} solo ejecuta jobs en paralelo. + +| Jenkins en Paralelo | {% data variables.product.prodname_actions %} +| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs..strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) | + +#### Matriz de compilaciones + +Tanto {% data variables.product.prodname_actions %} como Jenkins te permiten utilizar una matriz de compilaciones para definir diversas combinaciones de sistema. + +| Jenkins | {% data variables.product.prodname_actions %} +| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes) | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)
    [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) | +| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) | +| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) | | + +#### Utilizar pasos para ejecutar tareas + +Jenkins agrupa los `steps` en `stages`. Cada uno de estos pasos puede ser un script, función, o comando, entre otros. De manera similar, {% data variables.product.prodname_actions %} utiliza `jobs` para ejecutar grupos específicos de `steps`. + +| Pasos de Jenkins | {% data variables.product.prodname_actions %} +| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | +| [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs..steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) | + +### Ejemplos de tareas comunes + +#### Programar un mapa para ejecutarse con `cron` + + + + + + + + + + +
    +Mapa de Jenkins + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    + + ```yaml + pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } + } + ``` + + + + ```yaml + on: + schedule: + - cron: '*/15 * * * 1-5' + ``` + +
    + +#### Configurar variables de ambiente en un mapa + + + + + + + + + + +
    +Mapa de Jenkins + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    + + ```yaml + pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' + } + } + ``` + + + + ```yaml + jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' + + ``` + +
    + +#### Compilar desde proyectos ascendentes + + + + + + + + + + +
    +Mapa de Jenkins + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    + + ```yaml + pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS) + } + } + } + + ``` + + + + ```yaml + jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] + + ``` + +
    + +#### Compilar con sistemas operativos múltiples + + + + + + + + + + +
    +Mapa de Jenkins + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    + + ```yaml +pipeline { +agent none +stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } + } + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } + } + } + } + } + } +} +} + ``` + + + +{% raw %} + ```yaml + name: demo-workflow + on: + push: + jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp + ``` +{% endraw %} + +
    diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md new file mode 100644 index 0000000000000..28fa760331319 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -0,0 +1,415 @@ +--- +title: Migrarse de Travis CI a GitHub Actions +intro: '{% data variables.product.prodname_actions %} y Travis CI comparte muchas similitudes, lo cual hace que el migrarse a {% data variables.product.prodname_actions %} sea relativamente fácil.' +redirect_from: + - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'tutorial' +--- + +### Introducción + +Esta guía te ayuda a migrar de Travis CI a {% data variables.product.prodname_actions %}. Aquí se comparan sus conceptos y sintaxis, se describen sus similitudes y se demuestran sus acercamientos distintos para las tareas comunes. + +### Antes de comenzar + +Antes de que comiences tu migración a {% data variables.product.prodname_actions %}, sería útil familiarizarse con la forma en la que funciona: + +- Para encontrar un ejemplo rápido que ilustre un job de {% data variables.product.prodname_actions %}, consulta la sección "[Guía de inicio rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)". +- Para aprender los conceptos básicos de {% data variables.product.prodname_actions %}, consulta la sección "[Introducción a GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)". + +### Comparar la ejecución de jobs + +Para darte control sobre cuándo se ejecutarán las tareas de IC, un _flujo de trabajo_ de {% data variables.product.prodname_actions %} utiliza _jobs_ que se ejecutan en paralelo predeterminadamente. Cada job contiene _pasos_ que se ejecutan en una secuencia que tú defines. Si necesitas ejecutar acciones de configuración y limpieza para un job, puedes definir pasos en cada job para que esto se lleve a cabo. + +### Similitudes en las claves + +{% data variables.product.prodname_actions %} y Travis CI comparten algunas similitudes y entenderlas con anticipación puede ayudar a agilizar el proceso de migración. + +#### Utilizar la sintaxis de YAML + +Tanto Travis CI como {% data variables.product.prodname_actions %} utilizan YAML para crear jobs y flujos de trabajo y estos archivos se almacenan en el repositorio del código. Para obtener más información sobre cómo las {% data variables.product.prodname_actions %} utilizan YAML, consulta la sección "[Crear un archivo de flujo de trabajo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)". + +#### Variables de ambiente personalizadas + +Travis CI te permite configurar variables de ambiente y compartirlas entre etapas. De forma similar, las {% data variables.product.prodname_actions %} te permiten definir las variables de ambiente para un paso, job o flujo de trabajo. Para obtener más información, consulta la sección "[Variables de ambiente](/actions/reference/environment-variables)". + +#### Variables de entorno predeterminadas + +Tanto Travis CI como {% data variables.product.prodname_actions %} incluyen variables de ambiente predeterminadas que puedes utilizar en tus archivos de YAML. En el caso de las {% data variables.product.prodname_actions %}, puedes encontrarlas listadas en la sección "[Variables de ambiente predeterminadas](/actions/reference/environment-variables#default-environment-variables)". + +#### Proceso paralelo de jobs + +Travis CI puede utilizar `stages` para ejecutar jobs en paralelo. De forma similar, las {% data variables.product.prodname_actions %} ejecutan `jobs` en paralelo. Para obtener más información, consulta la sección "[Crear jobs dependientes](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)". + +#### Insignias de estado + +Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con las insignias de estado, lo cual te permite indicar si una compilación pasa o falla. Para obtener más información, consulta la sección "[Agregar una insignia de estado de un flujo de trabajo a tu repositorio](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". + +#### Utilizar una matriz de compilaciones + +Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con matrices de compilación, lo cual te permite realizar pruebas utilizando combinaciones de sistemas operativos y paquetes de software. Para obtener más información, consulta "[Utilizar una matriz de compilaciones](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". + +A continuación podrás encontrar un ejemplo que compara la sintaxis para cada sistema: + + + + + + + + + + +
    +Travis CI + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +matrix: + include: + - rvm: 2.5 + - rvm: 2.6.3 +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + build: + strategy: + matrix: + ruby: [2.5, 2.6.3] +``` +{% endraw %} +
    + +#### Apuntar a ramas específicas + +Tanto Travis CI como {% data variables.product.prodname_actions %} te permiten apuntar tu IC a una rama específica. Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Travis CI + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +branches: + only: + - main + - 'mona/octocat' +``` +{% endraw %} + +{% raw %} +```yaml +on: + push: + branches: + - main + - 'mona/octocat' +``` +{% endraw %} +
    + +#### Verificar submódulos + +Tanto Travis CI como {% data variables.product.prodname_actions %} te permiten controlar si los submódulos se incluirán en los clones de los repositorios. + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Travis CI + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +git: + submodules: false +``` +{% endraw %} + +{% raw %} +```yaml + - uses: actions/checkout@v2 + with: + submodules: false +``` +{% endraw %} +
    + +#### Utilizar variables de ambiente en una matriz + +Tanto {% data variables.product.prodname_actions %} como Travis CI pueden agregar variables de ambiente personalizadas a una matriz de pruebas, lo cual te permite referirte a la variable en un paso subsecuente. + +En {% data variables.product.prodname_actions %}, puedes utilizar la clave `include` para agregar variables de ambiente personalizadas a una matriz. {% data reusables.github-actions.matrix-variable-example %} + +### Características clave en {% data variables.product.prodname_actions %} + +Cuando te migres de Travis CI, consider las siguientes características clave en {% data variables.product.prodname_actions %}: + +#### Almacenar secretos + +{% data variables.product.prodname_actions %} te permite almacenar secretos y referenciarlos en tus jobs. Las organizaciones de {% data variables.product.prodname_actions %} pueden limitar qué repositorios pueden acceder a sus secretos. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Las reglas de protección de ambiente pueden requerir aprobación manual para que un flujo de trabajo acceda a los secretos del ambiente. {% endif %}Para obtener más información, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)". + +#### Compartir archivos entre jobs y flujos de trabajo + +{% data variables.product.prodname_actions %} incluye compatibilidad integrada para almacenamiento de artefactos, lo cual te permite compartir archivos entre jobs en un flujo de trabajo. También puedes guardar los archivos resultantes y compartirlos con otros flujos de trabajo. Para obtener más información, consulta la sección "[Compartir datos entre jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)". + +#### Alojar tus propios corredores + +Si tus jobs requieren de hardware o software específico, {% data variables.product.prodname_actions %} te permite almacenar tus propios ejecutores y enviar tus jobs para que éstos los procesen. {% data variables.product.prodname_actions %} también te permite utilizar políticas para controlar cómo se accede a estos ejecutores, otorgando acceso a nivel de organización o de repositorio. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/hosting-your-own-runners)". + +#### Tiempo de ejecución y jobs simultáneos + +Los jobs simultáneos y los tiempos de ejecución de los flujos de trabajo en {% data variables.product.prodname_actions %} pueden variad dependiendo de tu plan de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration)." + +#### Utilizar lenguajes diferentes en {% data variables.product.prodname_actions %} + +Cuando trabajas con lenguajes diferentes en {% data variables.product.prodname_actions %}, pueeds crear un paso en tu job para configurar tus dependencias de lenguaje. Para obtener más información acerca de cómo trabajar con un lenguaje en particular, consulta la guía específica: + - [Crear y probar en Node.js](/actions/guides/building-and-testing-nodejs) + - [Compilar y probar PowerShell](/actions/guides/building-and-testing-powershell) + - [Crear y probar en Python](/actions/guides/building-and-testing-python) + - [Construir y probar Java con Maven](/actions/guides/building-and-testing-java-with-maven) + - [Construir y probar Java con Gradle](/actions/guides/building-and-testing-java-with-gradle) + - [Construir y probar Java con Ant](/actions/guides/building-and-testing-java-with-ant) + +### Ejecutar scripts + +{% data variables.product.prodname_actions %} puede utilizar pasos de `run` para ejecutar scripts o comandos de shell. Para utilizar un shell en particular, puedes especificar el tipo de `shell` cuando proporciones la ruta al script. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". + +Por ejemplo: + +```yaml + steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash +``` + +### Manejo de errores en {% data variables.product.prodname_actions %} + +Cuando te migras a {% data variables.product.prodname_actions %}, hay varios acercamientos al manejo de errores que puede que necesites tener en mente. + +#### Manejo de errores en scripts + +{% data variables.product.prodname_actions %} detiene un job inmediatamente si alguno de los pasos regresa un código de error. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)". + +#### Manejo de errores en jobs + +{% data variables.product.prodname_actions %} utiliza condicionales de tipo `if` para ejecutar jobs o pasos en ciertas situaciones. Por ejemplo, puedes ejecutar un paso cuando otro paso da `failure()` como resultado. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)". También puedes utilizar [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) para prevenir que una ejecución de flujo de trabajo se detenga cuando falla un job. + +### Sintaxis de migración para condicionales y expresiones + +Para ejecutar jobs bajo expresiones condicionales, Travis CI y {% data variables.product.prodname_actions %} comparten una sintaxis condicional de tipo `if` similar. {% data variables.product.prodname_actions %} te permite utilizar la condicional `if` para prevenir que un paso o un job se ejecuten a menos de que se cumpla con la condición. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +Este ejemplo demuestra cómo una condicional de tipo `if` puede controlar si un paso se ejecuta o no: + +```yaml +jobs: + conditional: + runs-on: ubuntu-latest + steps: + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: env.str == 'ABC' && env.num == 123 +``` + +### Migrar las fases a pasos + +Mientras que Travis CI utiliza _fases_ para ejecutar _pasos_, {% data variables.product.prodname_actions %} tiene _pasos_ que pueden ejecutar _acciones_. Puedes encontrar acciones preconstruidas en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), o puedes crear tus propias acciones. Para obtener más información, consulta la sección "[Crear acciones](/actions/building-actions)". + +Puedes encontrar un ejemplo de la sintaxis para cada sistema: + + + + + + + + + + +
    +Travis CI + +{% data variables.product.prodname_actions %} +
    +{% raw %} +```yaml +language: python +python: + - "3.7" + +script: + - python script.py +``` +{% endraw %} + +{% raw %} +```yaml +jobs: + run_python: + runs-on: ubuntu-latest + steps: + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py +``` +{% endraw %} +
    + +### Almacenar dependencias en caché + +Travis CI y {% data variables.product.prodname_actions %} te permiten guardar dependencias en caché manualmente para reutilizarlas posteriormente. Este ejemplo ilustra la sintaxis de caché para cada sistema. + + + + + + + + + + +
    +Travis CI + +GitHub Actions +
    +{% raw %} +```yaml +language: node_js +cache: npm +``` +{% endraw %} + +{% raw %} +```yaml +- name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- +``` +{% endraw %} +
    + +El almacenamiento en caché de {% data variables.product.prodname_actions %} solo aplica a los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "Almacenar las dependencias en caché para agilizar los flujos de trabajo". + +### Ejemplos de tareas comunes + +Esta sección compara cómo {% data variables.product.prodname_actions %} y Travis CI realizan tareas en común. + +#### Configurar variables de ambiente + +Puedes crear variables de ambiente personalizadas en un job de {% data variables.product.prodname_actions %}. Por ejemplo: + + + + + + + + + + +
    +Travis CI + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    + + ```yaml +env: + - MAVEN_PATH="/usr/local/maven" + ``` + + + + ```yaml + jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' + ``` + +
    + +#### Compilar con Node.js + + + + + + + + + + +
    +Travis CI + +Flujo de trabajo de {% data variables.product.prodname_actions %} +
    +{% raw %} + ```yaml +install: + - npm install +script: + - npm run build + - npm test + ``` +{% endraw %} + +{% raw %} + ```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Use Node.js + uses: actions/setup-node@v1 + with: + node-version: '12.x' + - run: npm install + - run: npm run build + - run: npm test + ``` +{% endraw %} +
    + +### Pasos siguientes + +Para seguir aprendiendo sobre las características principales de {% data variables.product.prodname_actions %}, consulta la sección "[Aprender sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". diff --git a/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md new file mode 100644 index 0000000000000..2d6cf97b8ccb3 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -0,0 +1,143 @@ +--- +title: Fortalecimiento de seguridad para GitHub Actions +shortTitle: Fortalecimiento de seguridad +intro: 'Buenas prácticas de seguridad para utilizar las características de las {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/getting-started-with-github-actions/security-hardening-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'resumen' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Esta guía explica cómo configurar el fortalecimiento de seguridad para ciertas características de las {% data variables.product.prodname_actions %}. Si no estás familiarizado con los conceptos de las {% data variables.product.prodname_actions %}, consulta la sección "[Conceptos principales para GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)". + +### Utilizar secretos + +Los valores sensibles jamás deben almacenarse como texto simple e archivos de flujo de trabajo, sino más bien como secretos. Los [Secretos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) pueden configurarse a nivel de la organización% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio o ambiente{% else %} o repositorio{% endif %}, y permitirte almacenar información sensible en {% data variables.product.product_name %}. + +Los secretos utilizan [Cajas selladas de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) de manera que se cifran antes de llegar a {% data variables.product.product_name %}. Esto ocurre cuando el secreto se emite [utilizando la IU](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) o a través de la [API de REST](/rest/reference/actions#secrets). Este cifrado del lado del cliente ayuda a minimizar los riesgos relacionados con el registro accidental (por ejemplo, bitácoras de exepción y de solicitud, entre otras) dentro de la infraestructura de {% data variables.product.product_name %}. Una vez que se carga el secreto, {% data variables.product.product_name %} puede entonces descifrarlo para que se pueda inyectar en el tiempo de ejecución del flujo de trabajo. + +Para ayudar a prevenir la divulgación accidental, {% data variables.product.product_name %} utiliza un mecanismo que intenta redactar cualquier secreto que aparezca en las bitácoras de ejecución. La redacción busca coincidencias exactas de cualquier secreto configurado, así como los cifrados comunes de los valores, tales como Base64. Sin embargo, ya que hay varias formas en las que se puede transformar el valor de un secreto, esta redacción no está garantizada. Como resultado, hay ciertos pasos proactivos y buenas prácticas que debes seguir para ayudarte a garantizar que se redacten los secretos, y para limitar otros riesgos asociados con ellos: + +- **Nunca uses datos estructurados como un secreto** + - Los datos estructurados pueden causar que la redacción de secretos dentro de las bitácoras falle, ya que la redacción depende ampliamente de encontrar una coincidencia exacta para el valor específico del secreto. Por ejemplo, no utilices un blob de JSON, XML, o YAML (o similares) para encapsular el valor de un secreto, ya que esto reduce significativamente la probablidad de que los secretos se redacten adecuadamente. En vez de esto, crea secretos individuales para cada valor sensible. +- **Registra todos los secretos que se utilizan dentro de los flujos de trabajo** + - Si los secretos se utilizan para generar otro valor sensible dentro de un flujo de trabajo, este valor generado debe [registrarse como un secreto](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret) formalmente para que se pueda redactar si llega a aparecer en las bitácoras. Por ejemplo, si utilizas una llave privada para generar un JWT firmado para acceder a una API web, asegúrate registrar este JWT como un secreto, de lo contrario, este no se redactará si es que llega a ingresar en la salida de la bitácora. + - El registrar secretos aplica también a cualquier tipo de transformación/cifrado. Si tu secreto se transforma de alguna manera (como en el cifrado URL o de Base64), asegúrate de registrar el valor nuevo como un secreto también. +- **Audita cómo se manejan los secretos** + - Audita cómo se utilizan los secretos para ayudarte a garantizar que se manejan como lo esperas. Puedes hacer esto si revisas el código fuente del rpositorio que ejecuta el flujo de trabajo y verificas cualquier acción que se utilice en dicho flujo de trabajo. Por ejemplo, verifica que no se estén enviando a hosts no deseados, o que no se estén imprimiendo explícitamente en la salida de una bitácora. + - Visualiza las bitácoras de ejecución de tu flujo de trabajo después de probar las entradas válidas/no válidas y verifica que los secretos se redacten adecuadamente o que no se muestren. No siempre es obvio la forma en la que una herramienta o un comando que estés invocando enviará los errores a `STDOUT` o a `STDERR`, y los secretos pueden terminar siendo bitácoras de errores después. Por consiguiente, es una buena práctica el revisar manualmente las bitácoras de flujo de trabajo después de probar las entradas válidas y no válidas. +- **Utiliza credenciales que tengan alcances mínimos** + - Asegúrate de que las credenciales que estás utilizando dentro de los flujos de trabajo tengan los menores privilegios requeridos y ten en mente que cualquier usuario con acceso de escritura en tu repositorio tiene acceso de lectura para todos los secretos que has configurado en éste. +- **Audita y rota los secretos registrados** + - Revisa con frecuencia los secretos que se han registrado para confirmar que aún se requieran. Elimina aquellos que ya no se necesiten. + - Rota los secretos con frecuencia para reducir la ventana de tiempo en la que un secreto puesto en riesgo es aún válido. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +- **Considera requerir revisiones para el acceso a los secretos** + - Puedes utilizar revisiones requeridas para proteger los secretos del ambiente. Un job del flujo de trabajo no podrá acceder a los secretos del ambiente hasta que el revisor otorgue la aprobación. Para obtener más información acerca de almacenar secretos en los ambientes o requerir revisiones para ellos, consulta las secciones "[Secretos cifrados](/actions/reference/encrypted-secrets)" y "[Ambientes](/actions/reference/environments)". +{% endif %} + +### Utilizar acciones de terceros + +Los jobs individuales en un flujo de trabajo pueden interactuar con (y ponerse enriesgo con) otros jobs. Por ejemplo, un job que consulta las variables de mabiente que se utilizan por otro job subsecuente, escribir archivos en un directorio compartido que el job subsecuente procesa, o aún de forma ás directa si interactúa con el conector de Docker e inspecciona a otros contenedores en ejecución y ejecuta comandos en ellos. + +Esto significa que el poner en riesgo una sola acción dentro de un flujo de trabajo puede ser bastante significativo, ya que dicha acción en riesgo tendrá acceso a todos los secretos que configuras en tu repositorio, y puede utilizar el `GITHUB_TOKEN` para escribir en el repositorio. Por consiguiente, hay un riesgo significativo en suministrar acciones de repositorios de terceros en {% data variables.product.prodname_dotcom %}. Puedes ayudar a mitigar este riesgo si sigues estas buenas prácticas: + +* **Fija las acciones a un SHA de confirmación de longitud completa** + + Fijar una acción a un SHA de confirmación de longitud completa es actualmente la única forma de utilizar una acción como un lanzamiento inmutable. Fijar las acciones a un SHA en particular ayuda a mitigar el riesgo de que un actor malinencionado agregue una puerta trasera al repositorio de la acción, ya que necesitarían generar una colisión de SHA-1 para una carga útil vlálida de un objeto de Git. + + {% warning %} + + **Advertencia:** La versión corta del SHA de confirmación no es segura y jamás debería utilizarse para especificar la referencia de Git de una acción. Debido a cómo funcionan las redes de los repositorios, cualquier usuario puede bifurcar el repositorio y cargar una confirmación creada a éste, la cual colisione con el SHA corto. Esto causa que fallen los clones subsecuentes a ese SHA, debido a que se convierte en una confirmación ambigua. Como resultado, cualquier flujo de trabajo que utilice el SHA acortado fallará de inmediato. + + {% endwarning %} + + +* **Audita el código fuente de la acción** + + Asegúrate de que la acción está manejando los secretos y el contenido de tu repositorio como se espera. Por ejemplo, verifica que los secretos no se envíen a hosts no deseados, o que no se registren inadvertidamente. + +* **Fija las acciones a una etiqueta únicamente si confías en el creador** + + Aunque fijar el SHA de una confirmación es la opción más segura, especificar una etiqueta es más conveniente y se utiliza ampliamente. Si te gustaría especificar una etiqueta, entonces asegúrate de que confías en los creadores de la acción. La insignia de ‘Verified creator’ en {% data variables.product.prodname_marketplace %} es una señal útil, ya que te indica que la acción viene de un equipo cuya identidad verificó {% data variables.product.prodname_dotcom %}. Nota que este acercamiento sí tiene riesgos aún si confías en el autor, ya que una etiqueta se puede mover o borrar en caso de que un actor malicioso consiga acceso al repositorio que almacena la acción. + +### Considerar acceso entre repositorios + +{% data variables.product.product_name %} tiene un alcance intencional para un solo repositorio por vez. El `GITHUB_TOKEN` otorga el mismo nivel de acceso de un usuario con permisos de escritura, ya que cualquier usuario con dicho permisopuede acceder a este token si crea o modifica los archivos del flujo de trabajo. Los usuarios tienen permisos específicos para cada repositorio, así que, el hacer que el `GITHUB_TOKEN` para un repositorio otorgue acceso a otro impactaría el modelo de permisos de {% data variables.product.prodname_dotcom %} si no se implementa cuidadosamente. De forma similar, se debe tener cuidado al agregar tokens de autenticación de {% data variables.product.prodname_dotcom %} a un flujo de trabajo, ya que esto también puede afectar el modelo de permisos de {% data variables.product.prodname_dotcom %} al otorgar inadvertidamente un acceso amplio a los colaboradores. + +Tenemos [un plan en el itinerario de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap/issues/74) para compatibilizar un flujo que permita acceso entre repositorios dentro de {% data variables.product.product_name %}, pero aún no es una característica compatible. Actualmente, la única forma de realizar interacciones privilegiadas entre repositorios es colocar un token de autenticación de {% data variables.product.prodname_dotcom %} o llave SSH como un secreto dentro del flujo de trabajo. Ya que muchos tipos de tokens de autenticación no permiten el acceso granular a recursos específicos, existe un riesgo significativo en el utilizar el tipo incorrecto de token, ya que puede otorgr un acceso mucho más amplio que lo que se espera. + +Esta lista describe los acercamientos recomendatos para acceder alos datos de un repositorio dentro de un flujo de trabjajo, en orden descendente de preferencia: + +1. **El `GITHUB_TOKEN`** + - Este token tiene un alcance intencional para el repositorio único que invocó el flujo de trabajo, y tiene el mismo nivel de acceso que el de un usuario con acceso de escritura en el repositorio. El token se crea antes de que inicie cada job y caduca cuando dicho job finaliza. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". + - El `GITHUB_TOKEN` debe utilizarse cada que sea posible. +2. **Llave de despliegue del repositorio** + - Las llaves de despliegue son uno de los únicos tipos de credenciales que otorgan acceso de lectura o escritura en un solo repositorio, y pueden utilizarse para interactuar con otro repositorio dentro de un flujo de trabajo. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys#deploy-keys)". + - Nota que las llaves de despliegue solo pueden clonarse y subirse al repositorio utilizando Git, y no pueden utilizarse para interactuar con las API de REST o de GraphQL, así que puede no sean adecuadas para tus necesidades. +3. **Tokens de {% data variables.product.prodname_github_app %}** + - Las {% data variables.product.prodname_github_apps %} pueden instalarse en los repositorios seleccionados, e incluso tienen permisos granulares en los recursos dentro de ellos. Puedes crear una {% data variables.product.prodname_github_app %} interna a tu organización, instalarla en los repositorios a los que necesites tener acceso dentro de tu flujo de trabajo, y autenticarte como la instalación dentro del flujo de trabajo para acceder a esos repositorios. +4. **Tokens de acceso personal** + - Jamás debes utilizar tokens de acceso personal desde tu propia cuenta. Estos tokens otorgan acceso a todos los repositorios dentro de las organizaciones a las cuales tienes acceso, así como a los repositorios en tu cuenta de usuario. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Adicionalmente, si sales de una organización más adelante, los flujos de trabajo que utilicen este token fallarán inmediatamente, y depurar este problema puede ser difícil. + - Si se utiliza un token de acceso personal, debe ser uno que se haya generado para una cuenta nueva a la que solo se le haya otorgado acceso para los repositorios específicos que se requieren para el flujo de trabajo. Nota que este acercamiento no es escalable y debe evitarse para favorecer otras alternativas, tales como las llaves de despliegue. +5. **Llaves SSH en una cuenta de usuario** + - Los flujos de trabajo nunca deben utilizar las llaves SSH en una cuenta de usuario. De forma similar a los tokens de acceso personal, estas otorgan permisos de lectura/escritura a todos tus repositorios personales así como a todos los repositorios a los que tengas acceso mediante la membercía de organización. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Si pretendes utilizar una llave SSH porque solo necesitas llevar a cabo clonados de repositorio o subidas a éste, y no necesitas interactuar con una API pública, entonces mejor deberías utilizar llaves de despliegue individuales. + +### Fortalecimiento para los ejecutores auto-hospedados + +Los ejecutores **hospedados en {% data variables.product.prodname_dotcom %}** ejecutan código dentro de máquinas virtuales aisladas, limpias y efímeras, lo cual significa que no hay forma de poner este ambiente en riesgo de forma persistente, o de obtener acceso de otra forma a más información de la que se colocó en este ambiente durante el proceso de arranque. + +Los ejecutores **auto-hospedados** eb {% data variables.product.product_name %} no tienen garantías sobre la ejecución en máquinas virtuales limpias y efímeras, y pueden estar en riesgo persistentemente debido al código no confiable en un flujo de trabajo. + +Como resultado, los ejecutores auto-hospedados no deberán [utilizarse casi nunca para repositorios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) en {% data variables.product.product_name %}, ya que cualquier usuario puede abrir solicitudes de extracción contra este repositorio y poner en riesgo el ambiente. De forma similar, ten cuidado cuando utilices ejecutores auto-hospedados en repositorios privados, ya que cualquiera que pueda bifurcar el repositorio y abrir una solicitud de extracción (generalmente aquellos con acceso de lectura en el repositorio) podrá también poner en riesgo el ambiente del ejecutor auto-hospedado, incluyendo el obtener acceso a los secretos y al `GITHUB_TOKEN` más privilegiado que otorga permisos de acceso de escritura en el repositorio. + +Cuando se define un ejecutor auto-hospedado a nivel de organización o de empresa, {% data variables.product.product_name %} puede programar flujos de trabajo de repositorios múltiples en el mismo ejecutor. Como consecuencia, si se pone en riesgo la seguridad de estos ambientes, se puede ocasionar un impacto amplio. Para ayudar a reducir el alcance de esta vulneración, puedes crear límites si organizas tus ejecutores auto-hospedados en grupos separados. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". + +También deberás considerar el ambiente de las máquinas del ejecutor auto-hospedado: +- ¿Qué información sensible reside en la máquina configurada como el ejecutor auto-hospedado? Por ejemplo, llaves SSH privadas, tokens de acceso a la API, entre otros. +- ¿La máquina tiene acceso a la red para servicios sensibles? Por ejemplo, servicios de metadatos de Azure o de AWS. La cantidad de información sensible en este ambiente debe ser mínima, y siempre debes estar consciente de que cualquier usuario capaz de invocar flujos de trabajo tendrá acceso a este ambiente. + +Algunos clientes podrían intentar mitigar estos riesgos parcialmente implementando sistemas que destruyan al ejecutor auto-hospedado automáticamente después de cada ejecución de un job. Sin embargo, este acercamiento podría no ser tan efectivo como se pretende, ya que no hay forma de garantizar que un ejecutor auto-hospedado ejecute solamente un job. + +### Auditar eventos de {% data variables.product.prodname_actions %} + +Puedes utilizar la bitácora de auditoría para monitorear las tareas administrativas en una organización. La bitácora de auditoría registra el tipo de acción, cuándo se ejecutó, y qué cuenta de usuario la realizó. + +Por ejemplo, puedes utilizar la bitácora de auditoría para rastrear el evento `action:org.update_actions_secret`, el cual rastrea los cambios a los secretos de la organización: ![Entradas de la bitácora de auditoría](/assets/images/help/repository/audit-log-entries.png) + +Las siguientes tablas describen los eventos de {% data variables.product.prodname_actions %} que puedes encontrar en la bitácora de auditoría. Para obtener más información sobre cómo utilizar la bitácora de auditoría, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". + +#### Eventos para la administración de secretos +| Acción | Descripción | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action:org.create_actions_secret` | Se activa cuando un administrador de la organización [crea un secreto de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). | +| `action:org.remove_actions_secret` | Se activa cuando un administrador de la organización elimina un secreto de {% data variables.product.prodname_actions %}. | +| `action:org.update_actions_secret` | Se activa cuando un administrador de la organización actualiza un secreto de {% data variables.product.prodname_actions %}. | +| `action:repo.create_actions_secret` | Se activa cuando un administrador del repositorio [crea un secreto de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository). | +| `action:repo.remove_actions_secret` | Se activa cuando un administrador del repositorio elimina un secreto de {% data variables.product.prodname_actions %}. | +| `action:repo.update_actions_secret` | Se activa cuando un administrador del repositorio actualiza un secreto de {% data variables.product.prodname_actions %}. | + +#### Eventos para ejecutores auto-hospedados +| Acción | Descripción | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `action:org.register_self_hosted_runner` | Se activa cuando un propietario de la organización [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | +| `action:org.remove_self_hosted_runner` | Se activa cuando un propietario de la organización [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `action:repo.register_self_hosted_runner` | Se activa cuando un administrador del repositorio [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `action:repo.remove_self_hosted_runner` | Se activa cuando un administrador del repositorio [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). | + +#### Eventos para grupos de ejecutores auto-hospedados +| Acción | Descripción | +| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action:org.runner_group_created` | Se activa cuando un administrador de la organización [crea un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization). | +| `action:org.runner_group_removed` | Se activa cuando un administrador de la organización elimina el grupo de ejecutores auto-hospedados. | +| `action:org.runner_group_renamed` | Se activa cuando un administrador de la organización renombra un grupo de ejecutores auto-hospedados. | +| `action:org.runner_group_runners_added` | Se activa cuando un administrador de la organización [agrega un ejecutor auto-hospedado a un 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` | Se activa cuando un administrador de la organización elimina un ejecutor auto-hospedado de un grupo. | diff --git a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md new file mode 100644 index 0000000000000..731e6f1e1843b --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -0,0 +1,115 @@ +--- +title: Compartir flujos de trabajo con tu organización +shortTitle: Compartir flujos de trabajo con tu organización +intro: 'Aprende cómo puedes utilizar características de la organización para colaborar con tu equipo al compartir plantillas de flujos de trabajo, secretos y ejecutores auto-hospedados.' +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +type: 'how_to' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Resumen + +Si necesitas compartir flujos de trabajo y otras características de {% data variables.product.prodname_actions %} con tu equipo, entonces considera colaborar dentrod e una organización de {% data variables.product.prodname_dotcom %}. Una organización te permite almacenar centralmente y administrar secretos, artefactos y ejecutores auto-hospedados. También puedes crear plantillas de flujo de trabajo en el repositorio de `.github` y compartirlas con otros usuarios en tu organización. + +### Crear una plantilla de flujo de trabajo + +Los usuarios con acceso de escritura en el repositorio `.github` de la organización pueden crear plantillas de flujo de trabajo. Los miembros de la organización que tengan permisos para crear flujos de trabajo podrán entonces utilizar estas plantillas. Las plantillas de flujo de trabajo pueden utilizarse para crear flujos de trabajo nuevos en los repositorios públicos de una organización; para utilizar estas plantillas para crear flujos de trabajo en repositorios privados, la organización deberá pertenecer a un plan empresarial o a un plan de GitHub One. + +Este procedimiento muestra cómo crear una plantilla de flujo de trabajo y un archivo de metadatos. El archivo de metadatos describe cómo se presenta la plantilla a los usuarios cuando están creando un flujo de trabajo nuevo. + +1. En caso de que no exista previamente, crea en tu organización un repositorio público nuevo que se llame `.github`. +1. Crea un directorio que se llame `workflow-templates`. +1. Crea tu nuevo archivo de flujo de trabajo dentro del directorio `workflow-templates`. + + Si necesitas referirte a la rama predeterminada de un repositorio, puedes utilizar el marcador de posición `$default-branch`. Cuando se crea un flujo de trabajo utilizando tu plantilla, el marcador de posición se reemplazará automáticamente con el nombre de la rama predeterminada del repositorio. + + Por ejemplo, este archivo de nombre `octo-organization-ci.yml` ilustra un flujo de trabajo básico. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +1. Crea un archivo de metadatos dentro del directorio `workflow-templates`. El archivo de metadatos debe tener el mismo nombre que el archivo de flujo de trabajo, pero en vez de tener la extensión `.yml`, este deberá encontrarse adjunto en `.properties.json`. Por ejemplo, este archivo que se llama `octo-organization-ci.properties.json` contiene los metadatos para un archivo de flujo de trabajo de nombre `octo-organization-ci.yml`: + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **Requerido.** El nombre de la plantilla de flujo de trabajo. Este se muestra en la lista de plantillas disponibles. + * `description` - **Requerido.** La descripción de la plantilla de flujo de trabajo. Este se muestra en la lista de plantillas disponibles. + * `iconName` - **Requerido.** Define un icono en la lista de plantillas para la entrada del flujo de trabajo. El `iconName` debe ser un icono en SVG del mismo nombre y se debe almacenar en el directorio `workflow-templates`. Por ejemplo, un archivo de tipo SVG que se nombre `example-icon.svg` se referenciará como `example-icon`. + * `categories` - **Opcional.** Define la categoría de lenguaje del flujo de trabajo. Cuando un usuario visualiza las plantillas disponibles, aquellas que empaten con el mismo lenguaje se presentarán con mayor prominencia. Para obtener información sobre las categorías de lenguaje disponibles, consulta https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Opcional.** Permite que se utilice la plantilla si el repositorio del usuario contiene un archivo en su directorio raíz, el cual empate con una expresión regular definida. + +Para agregar otra plantilla de flujo de trabajo, agrega tus archivos al mismo directorio de `workflow-templates`. Por ejemplo: + +![Archivos de plantilla de flujo de trabajo](/assets/images/help/images/workflow-template-files.png) + +### Utilizar una plantilla de flujo de trabajo desde tu organización + +Este procedimiento ilustra cómo un miembro de tu organización puede encontrar y utilizar una plantilla de flujo de trabajo para crear un flujo de trabajo nuevo. Cualquiera que sea un miembro de la organización podrá utilizar las plantillas de flujo de trabajo de ésta. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. Si tu repositorio ya cuenta con flujos de trabajo: En la esquina superior izquierda, da clic sobre **Flujo de trabajo nuevo**. ![Crear un nuevo flujo de trabajo](/assets/images/help/repository/actions-new-workflow.png) +1. Tus plantillas de flujo de trabajo de la organización se ubican en su propia sección, la cual se titula "Flujos de trabajo creados por _nombre de la organización_". Debajo del nombre de la plantilla que deseas utilizar, da clic en **Configurar este flujo de trabajo**. ![Configurar este flujo de trabajo](/assets/images/help/settings/actions-create-starter-workflow.png) + + +### Compartir secretos dentro de una organización + +Puedes admnistrar tus secretos centralmente dentro de una organización y hacerlos disponibles para repositorios específicos. Esto también significa que púedes actualizar un secreto en una ubicación y hacer que el cambio aplique a todos los flujos de trabajo del repositorio que lo utilicen. + +Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Da clic en **Secreto nuevo**. +1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. +1. Ingresa el **Valor** para tu secreto. +1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. +1. Haz clic en **Agregar secreto** (Agregar secreto). + +### Compartir ejecutores auto-hospedados dentro de una organización + +Los administradores de las organizaciones pueden agregar sus ejecutores auto-hospedados a grupos y luego crear políticas que controlen qué repositorios pueden acceder al grupo. + +Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". + + +### Pasos siguientes + +Para seguir aprendiendo sobre {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". diff --git a/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md new file mode 100644 index 0000000000000..550b6a04759a1 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -0,0 +1,63 @@ +--- +title: Agregar una insignia de estado de flujo de trabajo +intro: Puedes mostrar una insignia de estado en tu repositorio para indicar el estado de tus flujos de trabajo. +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 %} + +{% data reusables.repositories.actions-workflow-status-badge-into %} + +Si tu flujo de trabajo usa la palabra clave `Nombre`, debes hacer referencia al flujo de trabajo por nombre. Si el nombre de tu flujo de trabajo contiene un espacio en blanco, deberás reemplazar el espacio con la cadena que codifica la URL `%20`. Para obtener más información sobre la palabra clave `name` (nombre), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#name)". + +``` +https://github.com///workflows//badge.svg +``` + +Como alternativa, si tu flujo de trabajo no tiene un `Nombre`, debes hacer referencia al archivo de flujo de trabajo usando la ruta del archivo en relación con el directorio raíz del repositorio. + +{% note %} + +**Nota:** Hacer referencia al archivo de flujo de trabajo mediante la ruta del archivo no funciona si el flujo de trabajo tiene un `Nombre`. + +{% endnote %} + +``` +https://github.com///workflows//badge.svg +``` + +### Utilizar un nombre de flujo de trabajo + +Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabajo con el nombre "Greet Everyone". El `PROPIETARIO` del repositorio es la organización `actions` y el nombre del `REPOSITORIO` es `hello-world`. + +``` +![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) +``` + +### Utilizar una ruta de archivo de flujo de trabajo + +Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabajo con la ruta de archivo `.github/workflows/main.yml`. El `PROPIETARIO` del repositorio es la organización `actions` y el nombre del `REPOSITORIO` es `hello-world`. + +``` +![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) +``` + +### Utilizar el parámetro `branch` + +Este ejemplo de Markdown añade un distintivo de estado para una rama con el nombre `feature-1`. + +``` +![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) +``` + +### Utilizar el parámetro `event` + +Este ejemplo de Markdown agrega un distintivo que muestra el estado de las ejecuciones de flujo de trabajo activadas por el evento `pull_request`. + +``` +![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) +``` diff --git a/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md new file mode 100644 index 0000000000000..97d4d6ecc9802 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -0,0 +1,36 @@ +--- +title: Cancelar un flujo de trabajo +intro: 'Puedes cancelar una ejecución de flujo de trabajo que esté en curso. Cuando cancelas una ejecución de flujo de trabajo, {% data variables.product.prodname_dotcom %} cancela todsos los jobs y pasos que son parte de ésta.' +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 %} + +{% data reusables.repositories.permissions-statement-write %} + +### Cancelar una ejecución de flujo de trabajo + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +1. Desde la lista de ejecuciones de flujo de trabajo, da clic en el nombre de la ejecución en estado de `queued` o `in progress` que quieras cancelar. ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/in-progress-run.png) +1. En la esquina superior derecha del flujo de trabajo, da clic en **Cancelar flujo de trabajo**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Botón de cancelar el conjunto de verificaciones](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![Botón de cancelar el conjunto de verificaciones](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} + +### Pasos que toma {% data variables.product.prodname_dotcom %} para cancelar una ejecución de flujo de trabajo + +Cuando cancelas una ejecución de flujo de trabajo, tal vez estés ejecutando otro software que utiliza recursos que se relacionan con ésta. Para ayudarte a liberar los recursos relacionados con dicha ejecución de flujo de trabajo, podría ser útil entender los pasos que realiza {% data variables.product.prodname_dotcom %} para cancelar una ejecución de flujo de trabajo. + +1. Para cancelar una ejecución de flujo de trabajo, el servidor vuelve a evaluar las condiciones `if` para todos los jobs que se ejecutan actualmente. Si la condición se evalúa como `true`, el job no se cancelará. Por ejemplo, la condición `if: always()` se evaluaría como "true" y el job continuaría ejecutándose. Cuando no hay condición, esto es equivalente a una condición `if: success()`, la cual solo se ejecutará si el paso anterior finalizó con éxito. +2. Para los jobs que necesitan cancelarse, el servidor envía un mensaje de cancelación a todas las máquinas ejecutoras con jobs que necesitan cancelarse. +3. Para los jobs que siguen ejecutándose, el servidor vuelve a evaluar las condiciones `if` para los pasos sin finalizar. Si la condición se evalúa como `true`, el paso seguirá ejecutándose. +4. Para los pasos que necesitan cancelarse, la máquina ejecutora manda un `SIGINT/Ctrl-C` al proceso de entrada del paso (`node` para una acción de javascript, `docker` para una acción de contenedor, y `bash/cmd/pwd` cuando se utiliza `run` en un paso). Si el proceso no sale en 7500 ms, el ejecutor mandará un `SIGTERM/Ctrl-Break` al proceso y luego esperará por 2500 ms para que el proceso salga. Si el proceso aún está ejecutándose, el ejecutor finalizará abruptamente el árbol de proceso. +5. Después de los 5 minutos del periodo de expiración de plazo de cancelación, el servidor forzará la terminación de todos los jobs y pasos que no hayan finalizado la ejecución o que hayan fallado en completar el proceso de cancelación. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md new file mode 100644 index 0000000000000..7e02a50f498f0 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -0,0 +1,23 @@ +--- +title: Borrar una ejecución de flujo de trabajo +intro: 'Puedes borrar una ejecución de flujo de trabajo que se haya completado o que tenga más de dos semanas de antigüedad.' +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 %} + +{% data reusables.repositories.permissions-statement-write %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +1. Para eliminar una ejecución de flujo de trabajo, utiliza el menú desplegable de {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Borrar una ejecución de flujo de trabajo**. + + ![Borrar una ejecución de flujo de trabajo](/assets/images/help/settings/workflow-delete-run.png) +2. Revisa el mensaje de confirmación y da clic en **Sí, borrar esta ejecución de flujo de trabajo permanentemente**. + + ![Borrar una confirmación de ejecución de flujo de trabajo](/assets/images/help/settings/workflow-delete-run-confirmation.png) diff --git a/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md new file mode 100644 index 0000000000000..d009495547a9d --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -0,0 +1,45 @@ +--- +title: Inhabilitar y habilitar un flujo de trabajo +intro: 'Puedes inhabilitar y volver a habilitar un flujo de trabajo utilizando {% data variables.product.prodname_dotcom %} o la API de REST.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Inhabilitar un flujo de trabajo te permite impedir que se active sin tener que borrar el archivo del repositorio. Puedes habilitar el flujo de trabajo de nuevo fácilmente en {% data variables.product.prodname_dotcom %}. También puedes inhabilitar y habilitar un flujo de trabajo utilizando la API de REST. Para obtener más información, consulta la sección "[API de REST de Acciones](/rest/reference/actions#workflows)". + +Inhabilitar un flujo de trabajo temporalmente puede ser útil en varios escenarios. Estos son algunos cuantos ejemplos en donde inhabilitar un flujo de trabajo podría ser útil: + +- Existe un error en el flujo de trabajo, el cual produce demasiadas solicitudes erróneas, lo cual impacta negativamente los servicios externos. +- Hay un flujo de trabajo que no es crítico y que está consumiendo demasiados minutos en tu cuenta. +- Hay un flujo de trabajo que envía solicitudes a un servicio que está inactivo. +- Hay flujos de trabajo en un repositorio bifurcado que no se necesitan (por ejemplo, flujos de trabajo programados). + +{% warning %} + +**Advertencia:** {% data reusables.actions.scheduled-workflows-disabled %} + +{% endwarning %} + +### Inhabilitar un flujo de trabajo + +Puedes inhabilitar un flujo de trabajo manualmente para que no ejecute ninguna ejecución del mismo. Un flujo de trabajo inhabilitado no se borrará y puede volver a habilitarse. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. En la barra lateral, da clic en el flujo de trabajo que quieras inhabilitar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png) +1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![menú de kebab de las acciones](/assets/images/help/repository/actions-workflow-menu-kebab.png) +1. Da clic en **Inhabilitar flujo de trabajo**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)El flujo de trabajo inhabilitado se marca con {% octicon "stop" aria-label="The stop icon" %} para indicar su estado. ![lista de acciones del flujo de trabajo inhabilitado](/assets/images/help/repository/actions-find-disabled-workflow.png) + +### Habilitar un flujo de trabajo + +Puedes volver a habilitar un flujo de trabajo que se había inhabilitado previamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres habiitar. ![acciones para seleccional el flujo de trabajo inhabilitado](/assets/images/help/repository/actions-select-disabled-workflow.png) +1. Da clic en **Habilitar flujo de trabajo**. ![acciones para habilitar flujo de trabajo](/assets/images/help/repository/actions-enable-workflow.png) diff --git a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md new file mode 100644 index 0000000000000..0cccbdf92a800 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -0,0 +1,27 @@ +--- +title: Descargar los artefactos del flujo de trabajo +intro: Puedes descargar artefactos archivados antes de que venzan automáticamente. +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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Predeterminadamente, {% data variables.product.product_name %} almacena las bitácoras de compilación y los artefactos por 90 días, y puedes personalizar este periodo de retención dependiendo del tipo de repositorio. Para obtener más información, consulta la sección "[Configurar el periodo de retención para los artefactos y las bitácoras de las GitHub Actions en tu repositorio](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %} +{% if currentVersion == "enterprise-server@2.22" %} Las {% data variables.product.product_name %} almacenan las bitácoras y los artefactos por 90 días.{% endif %} + +{% data reusables.repositories.permissions-statement-read %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +1. Debajo de **Artefactos**, da clic en aquél que quieras descargar. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/enabling-debug-logging.md b/translations/es-ES/content/actions/managing-workflow-runs/enabling-debug-logging.md new file mode 100644 index 0000000000000..2e4ce43df12f1 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/enabling-debug-logging.md @@ -0,0 +1,41 @@ +--- +title: Habilitar registro de depuración +intro: 'Si los registros de flujo de trabajo no proporcionan suficiente detalle para diagnosticar por qué un flujo de trabajo o paso no funciona como se espera, puedes habilitar más registros de depuración.' +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 %} + +Estas bitácoras extra se habilitan configurando los secretos en el repositorio que contiene el flujo de trabajo, así que aplicarán los mismos requisitos de los permisos: + +- {% data reusables.github-actions.permissions-statement-secrets-repository %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +- {% data reusables.github-actions.permissions-statement-secrets-environment %} +{% endif %} +- {% data reusables.github-actions.permissions-statement-secrets-organization %} +- {% data reusables.github-actions.permissions-statement-secrets-api %} + +Para obtener más información sobre cómo establecer secretos, consulta la sección "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." + +### Habilitar el registro de diagnóstico del ejecutor + +El registro de diagnósticos de ejecución proprociona archivos de bitácora adicionales que contienen información acera de cómo un ejecutor está ejecutando un job. Dos archivos de registro adicionales se agregan al archivo de registro: + +* El registro del proceso del ejecutor, que incluye información acerca de la coordinación y la configuración de los ejecutores para ejecutar tareas. +* El registro del proceso del trabajador, que registra la ejecución de una tarea. + +1. Para habilitar el registro de diagnóstico del ejecutor, establece el siguiente secreto en el repositorio que contiene el flujo de trabajo: `ACTIONS_RUNNER_DEBUG` en `true`. + +1. Para descargar los registros de diagnóstico del ejecutor, descarga el archivo de registro del flujo de trabajo. Los registros de diagnóstico del ejecutor se encuentran en la carpeta `correner-diagnostic-logs`. Para obtener más información sobre cómo descargar bitácoras, consulta la sección "[Descargar bitácoras](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)". + +### Habilitar el registro de depuración del paso + +El registro de depuración del paso aumenta el nivel de detalle de los registros de un trabajo durante y después de la ejecución de una tarea. + +1. Para habilitar el registro de depuración del paso, debes establecer el siguiente secreto en el repositorio que contiene el flujo de trabajo: `ACTIONS_RUNNER_DEBUG` en `true`. + +1. Después de establecer el secreto, se muestran más eventos de depuración en los registros del paso. Para obtener más información, consulta ["Ver registros para diagnosticar fallas"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures). diff --git a/translations/es-ES/content/actions/managing-workflow-runs/index.md b/translations/es-ES/content/actions/managing-workflow-runs/index.md new file mode 100644 index 0000000000000..f4812678a1950 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/index.md @@ -0,0 +1,34 @@ +--- +title: Administrar ejecuciones de flujo de trabajo +shortTitle: Administrar ejecuciones de flujo de trabajo +intro: 'Puedes ver el estado y resultados de cada paso en tu flujo de trabajo, cancelar un flujo de trabajo pendiente, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}revisar los despliegues, {% endif %}ver los minutos de ejecución facturables de los jobs, depurar y volver a ejecutar un flujo de trabajo fallido, buscar y descargar bitácoras, y descargar artefactos.' +redirect_from: + - /actions/configuring-and-managing-workflows/managing-a-workflow-run + - /articles/viewing-your-repository-s-workflows + - /articles/viewing-your-repositorys-workflows + - /articles/managing-a-workflow-run + - /github/automating-your-workflow-with-github-actions/managing-a-workflow-run + - /actions/automating-your-workflow-with-github-actions/managing-a-workflow-run + - /actions/configuring-and-managing-workflows/configuring-and-managing-workflow-files-and-runs +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} +{% link_in_list /viewing-workflow-run-history %} +{% link_in_list /using-workflow-run-logs %} +{% link_in_list /manually-running-a-workflow %} +{% link_in_list /re-running-a-workflow %} +{% link_in_list /canceling-a-workflow %} +{% link_in_list /reviewing-deployments %} +{% link_in_list /disabling-and-enabling-a-workflow %} +{% link_in_list /deleting-a-workflow-run %} +{% link_in_list /viewing-job-execution-time %} +{% link_in_list /downloading-workflow-artifacts %} +{% link_in_list /removing-workflow-artifacts %} +{% link_in_list /enabling-debug-logging %} +{% link_in_list /adding-a-workflow-status-badge %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md new file mode 100644 index 0000000000000..147233f0e64b5 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -0,0 +1,33 @@ +--- +title: Ejecutar un flujo de trabajo manualmente +intro: 'Cuando se configura un flujo de trabajo para ejecutarse en un evento de `workflow_dispatch`, puedes ejecutarlo utilizando la API de REST desde la pestaña de acciones en {% data variables.product.prodname_dotcom %}.' +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 %} + +### Configurar un flujo de trabajo para que se ejecute manualmente + +Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para ejecutarse en el evento `workflow_dispatch`. Para obtener más información sobre cómo configurar el evento `workflow_dispatch`, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". + +### Ejecutar un flujo de trabajo en {% data variables.product.prodname_dotcom %} + +Para activar el evento `workflow_dispatch` en {% data variables.product.prodname_dotcom %}, tu flujo de trabajo deberá estar en la rama predeterminada. Sigue estos pasos para activar una ejecución de flujo de trabajo manualmente. + +{% data reusables.repositories.permissions-statement-read %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. En la barra lateral izquierda, da clic ene l flujo de trabajo que quieras ejecutar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png) +1. Sobre la lista de ejecuciones de flujo de trabajo, selecciona **Ejecutar flujo de trabajo**. ![envío del flujo de trabajo de las acciónes](/assets/images/actions-workflow-dispatch.png) +1. Selecciona la rama en donde el flujo de trabajo se ejecutará y teclea los parámetros de entrada que éste utiliza. Da clic en **Ejecutar flujo de trabajo**. ![flujo de trabajo de la ejecución manual de las acciones](/assets/images/actions-manually-run-workflow.png) + +### Ejecutar un flujo de trabajo utilizando la API de REST + +Para obtener más información acerca de cómo utilizar la API de REST, consulta la sección [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Si omites las entradas, se utilizarán los valores predeterminados que se hayan definido en el flujo de trabajo. + +Puedes activar el evento de `workflow_dispatch` desde la pestaña de Acciones en {{ site.data.variables.product.prodname_dotcom }} o utilizar la API de REST. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md new file mode 100644 index 0000000000000..e8834f4654fdb --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -0,0 +1,19 @@ +--- +title: Volver a ejecutar un flujo de trabajo +intro: Puedes volver a ejecutar una instancia de un flujo de trabajo. Volver a ejecutar un flujo de trabajo utiliza el mismo `GITHUB_SHA`(SHA de confirmación) y `GITHUB_REF` (referencia de Git) que el evento original que activó la ejecución de flujo de trabajo. +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 %} + +{% data reusables.repositories.permissions-statement-write %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +1. En la esquina superior derecha del flujo de trabajo, utiliza el menú desplegable de **volver a ejecutar los jobs** y selecciona **volver a ejecutar todos los jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md new file mode 100644 index 0000000000000..ef9d64738bf28 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -0,0 +1,47 @@ +--- +title: Eliminar artefactos de flujo de trabajo +intro: 'Puedes reclamar el almacenamiento de {% data variables.product.prodname_actions %} que se haya utilizado si borras los artefactos antes de que venzan en {% data variables.product.product_name %}.' +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 %} + +### Borrar un artefacto + +{% warning %} + +**Advertencia:** Una vez que eliminas un artefacto, no se puede restaurar. + +{% endwarning %} + +{% data reusables.repositories.permissions-statement-write %} + +{% data reusables.github-actions.artifact-log-retention-statement %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +1. Debajo de **Artefactos**, da clic en +el {% octicon "trashcan" aria-label="The trashcan icon" %} junto al artefacto que quieras eliminar. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menú desplegable Delete artifact (Eliminar artefacto)](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![Menú desplegable Delete artifact (Eliminar artefacto)](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Configurar el periodo de retención para un artefacto + +Los periodos de retención para los artefactos y las bitácoras pueden configurarse a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección "[Límites de uso y administración](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)". + +También puedes definir un periodo de retención personalizado para los artefactos individuales que utilizan la acción `actions/upload-artifact` en un flujo de trabajo. Para obtener más información, consulta la sección "[Almacenar datos del flujo de trabajo como artefactos](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)". + +### Encontrar la fecha de vencimiento de un artefacto + +Puedes utilizar la API para confirmar la fecha de programación para el borrado de un artefacto. Para obtener más información, consulta el valor de `expires_at` que devuelve la acción "[Listar artefactos para un repositorio](/rest/reference/actions#artifacts)". +{% endif %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md new file mode 100644 index 0000000000000..843de1ff9cd78 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -0,0 +1,25 @@ +--- +title: Revisar los despliegues +intro: Puedes aprobar o rechazar jobs que estén esperando una revisión. +product: '{% data reusables.gated-features.environments %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.environments-beta %} + +### Acerca de las revisiones requeridas en los flujos de trabajo + +Los jobs que referencian un ambiente configurado con revisores requeridos esperarán por una aprobación antes de comenzar. Mientras que un job espera su revisión, tendrá un estado de "Waiting". Si un job no se aprueba dentro de 30 días, la ejecución del flujo de trabajo se cancelará automáticamente. + +Para obtener más información acerca de los ambientes y aprobaciones requeridas, consulta la sección "[Ambientes](/actions/reference/environments)". + +### Aprobar o rechazar un job + +1. Navega a la ejecución de flujo de trabajo que requiere revisión. Para obtener más información acerca de navegar a una ejecución de flujo de trabajo, consulta la sección "[Visualizar el historial de la ejecución del flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". +2. Da clic en **Revisar despliegues**. ![Revisar despliegues](/assets/images/actions-review-deployments.png) +3. Selecciona el(los) ambiente(s) para aprobar o rechazar. Opcionalmente, deja un comentario. ![Aprobar despliegues](/assets/images/actions-approve-deployments.png) +4. Aprueba o rechaza: + - Para aprobar el job, da clic en **Aprobar y desplegar**. Una vez que el job se apruebe (y que cualquier otra regla de protección del ambiente haya pasado), el job procederá. En este punto, el job puede acceder a cualquier secreto que esté almacenado en el ambiente. + - Para rechazar el job, da clic en **Rechazar**. Si se rechaza un job, el flujo de trabajo fallará. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/es-ES/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000000..a9bdc8c9e3df7 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Utilizar la gráfica de visualización +intro: Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. Puedes utilizar esta gráfica para monitorear y depurar los flujos de trabajo. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. La gráfica muestra cda job en el flujo de trabajo. Un icono a la izquierda del nombre del job indica el estado del mismo. Las líneas entre los jobs indican las dependencias. ![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph.png) + +2. Da clic en un job para ver la bitácora del mismo.![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md new file mode 100644 index 0000000000000..4c1505fb0a49d --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -0,0 +1,107 @@ +--- +title: Utilizar bitácoras de ejecución de flujo de trabajo +intro: 'Puedes ver, buscar y descargar las bitácoras de cada job en una ejecución de flujo de trabajo.' +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 %} + +Puedes ver si una ejecución de flujo de trabajo está en curso o completa desde la página de ejecución del flujo de trabajo. Debes haber iniciado sesión en una cuenta de {% data variables.product.prodname_dotcom %} para ver la información de ejecución del flujo de trabajo, incluyendo los casos de repositorios públicos. Para obtener más información, consulta "[Permisos de acceso en GitHub](/articles/access-permissions-on-github)". + +Si la ejecución está completa, puedes ver si el resultado fue exitoso, fallido, cancelado o neutral. Si la ejecución falló, puedes ver y buscar en los registros de construcción para diagnosticar la falla y volver a ejecutar el flujo de trabajo. También puedes ver los minutos de ejecución facturables para jobs, o descargar bitácoras y artefactos de compilación. + +{% data variables.product.prodname_actions %} usa la API de verificaciones para generar estados, resultados y registros para un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea una nueva comprobación de suite para cada ejecución de flujo de trabajo. La comprobación de suite contiene una ejecución de comprobación para cada trabajo en el flujo de trabajo, y cada trabajo incluye diferentes pasos. {% data variables.product.prodname_actions %} se ejecutan como un paso en un flujo de trabajo. Para obtener más información acerca de la API de Verificaciones, consulta la sección "[Verificaciones](/rest/reference/checks)". + +{% data reusables.github-actions.invalid-workflow-files %} + +### Ver registros para diagnosticar fallas + +Si falla la ejecución de su flujo de trabajo, puedes ver qué paso provocó el error y revisar los registros de construcción del paso que falló para solucionar el problema. Puedes ver el tiempo que demoró cada paso en ejecutarse. También puedes copiar un enlace permanente a una línea específica en el archivo de registro para compartir con tu equipo. {% data reusables.repositories.permissions-statement-read %} + +Adicionalmente a los pasos que se configuraron en el archivo de flujo de trabajo, {% data variables.product.prodname_dotcom %} agrega dos pasos adicionales a cada job para configurar y completar la ejecución del flujo de trabajo. Estos pasos se registran en la ejecución del flujo de trabajo con los nombres de "Set up job" y "Complete job". + +Para jobs que se ejecutan en ejecutores hospedados en {% data variables.product.prodname_dotcom %}, "Set up job" registra los detalles del ambiente virtual del ejecutor, e incluye un enlace a la lista de herramientas pre-instaladas que estuvieron presentes en la máquina del ejecutor. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow-superlinter %} +{% data reusables.repositories.view-run-superlinter %} +{% data reusables.repositories.navigate-to-job-superlinter %} +{% data reusables.repositories.view-failed-job-results-superlinter %} +{% data reusables.repositories.view-specific-line-superlinter %} + +### Buscar registros + +Puedes buscar en los registros de construcción un paso en particular. Cuando buscas registros, solo los pasos ampliados se incluyen en los resultados. {% data reusables.repositories.permissions-statement-read %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow-superlinter %} +{% data reusables.repositories.view-run-superlinter %} +{% data reusables.repositories.navigate-to-job-superlinter %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +1. En el cuadro de búsqueda **Buscar registros** en la esquina superior derecha de la salida del registro, escribe una consulta de búsqueda. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Cuadro de búsqueda para buscar registros](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![Cuadro de búsqueda para buscar registros](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} +{% else %} +1. Para expandir cada paso que deseas incluir en tu búsqueda, haz clic en el paso. ![Nombre del paso](/assets/images/help/repository/failed-check-step.png) +1. En el cuadro de búsqueda **Buscar registros** en la esquina superior derecha de la salida del registro, escribe una consulta de búsqueda. ![Cuadro de búsqueda para buscar registros](/assets/images/help/repository/search-log-box.png) +{% endif %} + +### Descargar bitácoras + +Puedes descargar los archivos de bitácora desde tu ejecución de flujo de trabajo. También puedes descargar los artefactos de un flujo de trabajo. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow-superlinter %} +{% data reusables.repositories.view-run-superlinter %} +{% data reusables.repositories.navigate-to-job-superlinter %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +1. En la esquina superior derecha, da clic en +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} y selecciona **Desgargar archivo de bitácora**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} + ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} +{% else %} +1. En la esquina superior derecha, da clic en +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Descargar archivo de bitácora**. + ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down.png) +{% endif %} + +### Borrar bitácoras + +Puedes borrar los archivos de bitácora de tu ejecución de flujo de trabajo. {% data reusables.repositories.permissions-statement-write %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow-superlinter %} +{% data reusables.repositories.view-run-superlinter %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +1. En la esquina superior derecha, da clic en +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. Para borrar los archivos de bitácora, da clic en el botón **Borrar todas las bitácoras** y revisa el aviso de confirmación. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Borrar todas las bitácoras](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Borrar todas las bitácoras](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +Después de borrar las bitácoras, el botón de **Borrar todas las bitácoras** se elimina para indicar que ya no quedan archivos en la ejecución de flujo de trabajo. +{% else %} +1. En la esquina superior derecha, da clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) +2. Para borrar los archivos de bitácora, da clic en el botón **Borrar todas las bitácoras** y revisa el aviso de confirmación. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) Después de que se hayan borrado las bitácoras, el botón de **Borrar todas las bitácoras** se elimina para indicar que no queda ningún archivo de bitácora en la ejecución del flujo de trabajo. +{% endif %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/es-ES/content/actions/managing-workflow-runs/viewing-job-execution-time.md new file mode 100644 index 0000000000000..486e2c79ff8d4 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -0,0 +1,24 @@ +--- +title: Visualizar el tiempo de ejecución de un job +intro: 'Puedes ver el tiempo de ejecución de un job, incluyendo los minutos facturables que este job ha acumulado.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Los minutos de ejecución facturables para un job solo se muestran en aquellos jobs que se ejecutan en repositorios privados que utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %}. No hay minutos facturables cuando se utiliza {% data variables.product.prodname_actions %} en repositorios públicos o para trabajos que se ejecutan en ejecutores auto-hospedados. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +1. Debajo del resumen del job, puedes ver el tiempo de ejecución del mismo. Para ver los detalles sobre el tiempo facturable de la ejecución de jobs, da clic en el tiempo que se muestra debajo de **tiempo facturable**. ![Enlace para los detalles de tiempo facturable y de ejecución](/assets/images/help/repository/view-run-billable-time.png) + + {% note %} + + **Nota:** El tiempo facturable que se muestra no incluye ningún multiplicador de minutos o de redondeo. Para ver tu uso total de {% data variables.product.prodname_actions %}, incluyendo los multiplicadores de minutos y de redondeo, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage)". + + {% endnote %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md new file mode 100644 index 0000000000000..fbdfabfb59c72 --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md @@ -0,0 +1,18 @@ +--- +title: Visualizar el historial de ejecución del flujo de trabajo +intro: Puedes ver las bitácoras de cada ejecución de un flujo de trabajo. Las bitácoras incluyen el estado de cada job y de cada paso en un flujo de trabajo. +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 %} + +{% data reusables.repositories.permissions-statement-read %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} diff --git a/translations/es-ES/content/actions/quickstart.md b/translations/es-ES/content/actions/quickstart.md new file mode 100644 index 0000000000000..6b8a94b79b743 --- /dev/null +++ b/translations/es-ES/content/actions/quickstart.md @@ -0,0 +1,145 @@ +--- +title: Guía de inicio rápido para GitHub Actions +intro: 'Agrega un flujo de trabajo de {% data variables.product.prodname_actions %} a un repositorio existente en 5 minutos o menos.' +allowTitleToDifferFromFilename: verdadero +redirect_from: + - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Introducción + +Solo necesitas tener un repositorio de {% data variables.product.prodname_dotcom %} para crear y ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}. En esta guía, agregarás un flujo de trabajo que limpia varios lenguajes de programación utilizando la [Acción de Super-Linter de {% data variables.product.prodname_dotcom %}](https://github.com/github/super-linter). El flujo de trabajo utiliza Super-Linter para validar tu código fuente cada que se sube una confirmación a tu repositorio. + +### Crear tu primer flujo de trabajo + +1. Desde tu repositorio en {% data variables.product.prodname_dotcom %}, crea un archivo nuevo en el directorio `.github/workflows` que se llame `superlinter.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." +2. Copia el siguiente contenido de YAML en el arcvhivo `superlinter.yml`. **Nota:** Si tu rama predeterminada no es `main`, actualiza el valor de `DEFAULT_BRANCH` para que refleje el nombre de la rama predeterminada de tu repositorio. + {% raw %} + ```yaml{:copy} + name: Super-Linter + + # Run this workflow every time a new commit pushed to your repository + on: push + + jobs: + # Set the job key. The key is displayed as the job name + # when a job name is not provided + super-lint: + # Name the Job + name: Lint code base + # Set the type of machine to run on + runs-on: ubuntu-latest + + steps: + # Checks out a copy of your repository on the ubuntu-latest machine + - name: Checkout code + uses: actions/checkout@v2 + + # Runs the Super-Linter action + - name: Run Super-Linter + uses: github/super-linter@v3 + env: + DEFAULT_BRANCH: main + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + ``` + {% endraw %} +3. Para ejecutar tu flujo de trabajo, desplázate al final de la página y selecciona **Crear una rama nueva para esta confirmación e iniciar una solicitud de cambios**. Después, para crear una solicitud de cambios, da clic en **Proponer un archivo nuevo**. ![Archivo de flujo de trabajo de la confirmación](/assets/images/commit-workflow-file.png) + +El confirmar el flujo de trabajo en tu repositorio activará el evento de `push` y ejecutará tu flujo de trabajo. + +### Ver los resultados de tu flujo de trabajo + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow-superlinter %} +{% data reusables.repositories.view-run-superlinter %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Debajo de **Jobs** o en la gráfica de visualización, da clic en el job de **Limpiar base de código**. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% else %} +1. En la barra lateral, da clic en el job de **Lint code base**. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job.png) +{% endif %} +{% data reusables.repositories.view-failed-job-results-superlinter %} + +### Más plantillas de flujo de trabajo + +{% data reusables.actions.workflow-template-overview %} + +### Pasos siguientes + +El flujo de trabajo de super-linter que acabas de agregar se ejecuta en cualquier momento en que se suba cópdigo a tu repositorio para ayudarte a detectar los errores y las coincidencias del mismo. Pero esto es solo el inicio de lo que puedes hacer con {% data variables.product.prodname_actions %}. Tu repositorio puede contener varios flujos de trabajo que activen jobs diferentes basándose en eventos diferentes. {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu s procesos de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_actions %}: + +- "[Aprende más sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" con este tutorial detallado +- "[Guías](/actions/guides)" para casos de uso específico y ejemplos +- [github/super-linter](https://github.com/github/super-linter) para obtener más detalles sobre la configuración de la acción de Super-Linter + + diff --git a/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md new file mode 100644 index 0000000000000..caf4d1320fe07 --- /dev/null +++ b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md @@ -0,0 +1,98 @@ +--- +title: Autenticación en un flujo de trabajo +intro: '{% data variables.product.prodname_dotcom %} proporciona un token que puedes usar para autenticar en nombre de {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token + - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token + - /actions/configuring-and-managing-workflows/authenticating-with-the-github_token +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca del secreto del `GITHUB_TOKEN` + +{% data variables.product.prodname_dotcom %} automáticamente crea un secreto de `GITHUB_TOKEN` para utilizar en tu flujo de trabajo. Puedes usar el `GITHUB_TOKEN` para autenticarte en una ejecución de flujo de trabajo. + +Cuando habilitas {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} instala una {% data variables.product.prodname_github_app %} en tu repositorio. El secreto del `GITHUB_TOKEN` es un token de acceso de instalación de {% data variables.product.prodname_github_app %}. Puedes usar el token de acceso de instalación para autenticarte en nombre de la {% data variables.product.prodname_github_app %} instalado en tu repositorio. Los permisos del token están limitados al repositorio que contiene tu flujo de trabajo. Para obtener más información, consulta "[Permisos para el `GITHUB_TOKEN`](#permissions-for-the-github_token)." + +Antes de que comience cada job, {% data variables.product.prodname_dotcom %} extrae un token de acceso de instalación para éste. El token expira cuando el trabajo termina. + +El token también está disponible en el contexto `github.token`. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +### Usar el `GITHUB_TOKEN` en un flujo de trabajo + +Para usar el secreto del `GITHUB_TOKEN`, debes hacer referencia a él en tu archivo de flujo de trabajo. Usar un token puede incluir pasar el token como entrada a una acción que lo requiere o hacer llamadas autenticadas de la API {% data variables.product.prodname_dotcom %}. + +{% data reusables.github-actions.actions-do-not-trigger-workflows %} + +#### Ejemplo de pase de `GITHUB_TOKEN` como una entrada + +Este flujo de trabajo de ejemplo usa la [acción de etiquetadora](https://github.com/actions/labeler), que necesita el `GITHUB_TOKEN` como el valor para el parámetro de entrada `repo-token`: + + {% raw %} + ```yaml + name: Pull request labeler + on: + - pull_request + jobs: + triage: + runs-on: ubuntu-latest + steps: + - uses: actions/labeler@v2 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + ``` + {% endraw %} + +#### Ejemplo de llamada a la API REST + +Puedes usar el `GITHUB_TOKEN` para realizar llamadas API autenticadas. Este flujo de trabajo de ejemplo crea una propuesta mediante la API REST del {% data variables.product.prodname_dotcom %}: + + {% raw %} + ```yaml + name: Create issue on commit + on: + - push + jobs: + create_commit: + runs-on: ubuntu-latest + steps: + - name: Create issue using REST API + run: | + curl --request POST \ + --url https://api.github.com/repos/${{ github.repository }}/issues \ + --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \ + --header 'content-type: application/json' \ + --data '{ + "title": "Automated issue for commit: ${{ github.sha }}", + "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_." + }' + ``` + {% endraw %} + +### Permisos para el `GITHUB_TOKEN` + +Para obtener información sobre los puntos finales de la API a los que {% data variables.product.prodname_github_apps %} puede acceder con cada permiso, consulta la sección "[ Permisos de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)". + +| Permiso | Tipo de acceso | Acceso por repositorios bifurcados | +| ------------------------- | ----------------- | ---------------------------------- | +| acciones | lectura/escritura | lectura | +| verificaciones | lectura/escritura | lectura | +| contenidos | lectura/escritura | lectura | +| implementaciones | lectura/escritura | lectura | +| propuestas | lectura/escritura | lectura | +| metadata | lectura | lectura | +| packages | lectura/escritura | lectura | +| solicitudes de extracción | lectura/escritura | lectura | +| proyectos de repositorio | lectura/escritura | lectura | +| estados | lectura/escritura | lectura | + +Si necesitas un token que requiere permisos que no están disponibles en el `GITHUB_TOKEN`, puedes crear un token de acceso personal y establecerlo como un secreto en tu repositorio: + +1. Usa o crea un token con los permisos adecuados para ese repositorio. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +1. Añade el token como un secreto en el repositorio de tu flujo de trabajo y haz referencia a él mediante la sintaxis {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %}. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." diff --git a/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md new file mode 100644 index 0000000000000..9a918bacdd10c --- /dev/null +++ b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -0,0 +1,477 @@ +--- +title: Sintaxis de contexto y de expresiones para acciones de GitHub +shortTitle: Sintaxis de contexto y de expresiones +intro: Puedes acceder a información de contexto y evaluar expresiones en flujos de trabajo y acciones. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/contexts-and-expression-syntax-for-github-actions + - /github/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions + - /actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions + - /actions/reference/contexts-and-expression-syntax-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los contextos y las expresiones + +Puedes usar expresiones para establecer variables programáticamente en archivos de flujo de trabajo y contextos de acceso. Una expresión puede ser cualquier combinación de valores literales, referencias a un contexto, o funciones. Puedes combinar literales, referencias de contexto y funciones usando operadores. + +Las expresiones se utilizan comúnmente con la palabra clave condicional `if` en un archivo de flujo de trabajo para determinar si un paso debe ejecutar. Cuando un condicional `if` es `true`, se ejecutará el paso. + +Debes usar una sintaxis específica para decirle a {% data variables.product.prodname_dotcom %} que evalúe una expresión en vez de tratarla como cadena. + +{% raw %} +`${{ }}` +{% endraw %} + +{% data reusables.github-actions.expression-syntax-if %} Para obtener más información acerca de los condicionales `if`, consulta la sección "[sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)". + +#### Expresión de ejemplo en un condicional `if` + +```yaml +steps: + - uses: actions/hello-world-javascript-action@v1.1 + if: {% raw %}${{ }}{% endraw %} +``` + +#### Ejemplo de parámetros en una variable de entorno + +{% raw %} +```yaml +env: + my_env_var: ${{ }} +``` +{% endraw %} + +### Contextos + +Los contextos son una manera de acceder a información acerca de las ejecuciones de flujo de trabajo, los entornos del ejecutor, los trabajos y los pasos. Los contextos usan la sintaxis de expresión. + +{% raw %} +`${{ }}` +{% endraw %} + +| Nombre del contexto | Tipo | Descripción | +| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `github` | `objeto` | Información sobre la ejecución del flujo de trabajo. Para obtener más información, consulta [github context](#github-context). | +| `env` | `objeto` | Contiene variables de entorno establecidas en un flujo de trabajo, trabajo o paso. Para obtener más información, consulta contexto de [`env`](#env-context). | +| `job` | `objeto` | Información sobre el trabajo actualmente en ejecución. Para obtener más información, consulta contexto de [`job`](#job-context). | +| `pasos` | `objeto` | Información sobre los pasos que se han ejecutado en este trabajo. Para obtener más información, consulta contexto de [`steps`](#steps-context). | +| `runner` | `objeto` | Incluye información sobre el ejecutor que está realizando el trabajo actual. Para más información, consulta [Contexto del `ejecutador (runner)`](#runner-context). | +| `secrets` | `objeto` | Habilita el acceso a los secretos. Para más información sobre secretos, consulta "[Creando y usando secretos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." | +| `strategy` | `objeto` | Brinda acceso a los parámetros de estrategia configurados y a la información sobre el puesto actual. Los parámetros de estrategia incluyen `fail-fast`, `job-index`, `job-total` y `max-parallel`. | +| `matrix` | `objeto` | Brinda acceso a los parámetros de la matriz que configuraste para el puesto actual. Por ejemplo, si configuraste una matriz de construcción con las versiones `os` y `node`, el objeto de contexto `matrix` incluye las versiones `os` y `node` del puesto actual. | +| `needs` | `objeto` | Habilita el acceso de las salidas de todos los jobs que se definen como una dependencia para el job actual. Para obtener más información, consulta [`needs` context](#needs-context). | + +Como parte de una expresión, puedes acceder a la información del contexto usando una de dos sintaxis. +- Sintaxis de índice: `github['sha']` +- Sintaxis de desreferencia de propiedad: `github.sha` + +Para usar la sintaxis de desreferencia de propiedad, el nombre de la propiedad debe cumplir con lo siguiente: +- comenzar con `a-Z` o `_`. +- estar seguida por `a-Z` `0-9` `-` o `_`. + +#### Determinar cuándo utilizar contextos + +{% data reusables.github-actions.using-context-or-environment-variables %} + +#### contexto de `github` + +El contexto de `github` contiene información sobre la ejecución del flujo de trabajo y el evento que desencadenó la ejecución. Puedes leer la mayoría de los datos de contexto de `github` en las variables del entorno. Para más información sobre las variables de entorno, consulta "[Utilizando variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." + +{% data reusables.github-actions.github-context-warning %} + +| Nombre de la propiedad | Tipo | Descripción | +| ------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `github` | `objeto` | El contexto de nivel superior disponible durante cualquier trabajo o paso en un flujo de trabajo. | +| `github.action` | `secuencia` | El nombre de la acción que se está ejecutando actualmente. {% data variables.product.prodname_dotcom %} elimina caracteres especiales o usa el nombre `run` cuando el paso actual ejecuta un script. Si usas la misma acción más de una vez en el mismo trabajo, el nombre incluirá un sufijo con el número de secuencia. Por ejemplo, el primer script que ejecutes tendrá el nombre `run1`, y el segundo script será nombrado `run2`. Del mismo modo, la segunda invocación de `actions/checkout` será `actionscheckout2`. | +| `github.action_path` | `secuencia` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder fácilmente a los archivos ubicados en el mismo repositorio que tu acción. Este atributo solo es compatible con las acciones de los pasos de ejecución compuestos. | +| `github.actor` | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo. | +| `github.base_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es una `pull_request`. | +| `github.event` | `objeto` | La carga de webhook del evento completo. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/articles/events-that-trigger-workflows/)". "Puedes acceder a propiedades individuales del evento que utiliza este contexto. | +| `github.event_name` | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo. | +| `github.event_path` | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor. | +| `github.head_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es una `pull_request`. | +| `github.job` | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | +| `github.ref` | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. Para las ramas, está en el formato `refs/heads/`, y para las etiquetas está en `refs/tags/`. | +| `github.repository` | `secuencia` | El nombre del repositorio y del propietario. Por ejemplo, `Codertocat/Hello-World`. | +| `github.repository_owner` | `secuencia` | El nombre del propietario del repositorio. Por ejemplo, `Codertocat`. | +| `github. run_id` | `secuencia` | {% data reusables.github-actions.run_id_description %} +| `github. run_number` | `secuencia` | {% data reusables.github-actions.run_number_description %} +| `github.sha` | `secuencia` | El SHA de confirmación que activó la ejecución del flujo de trabajo. | +| `github.token` | `secuencia` | Un token para autenticar en nombre de la aplicación de GitHub instalada en tu repositorio. Esto es funcionalmente equivalente al secreto de `GITHUB_TOKEN`. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | +| `github.workflow` | `secuencia` | El nombre del flujo de trabajo. Si el archivo de flujo de trabajo no especifica un `nombre`, el valor de esta propiedad es la ruta completa del archivo del flujo de trabajo en el repositorio. | +| `github.workspace` | `secuencia` | El directorio de trabajo predeterminado para los pasos y la ubicación predeterminada de tu repositorio cuando usas la acción [`checkout`](https://github.com/actions/checkout). | + +#### contexto de `env` + +El contexto de `Env` contiene las variables de entorno que se han establecido en un flujo de trabajo, puesto o paso. Para obtener más información acerca de la configuración de variables de entorno en tu flujo de trabajo, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". + +La sintaxis de contexto `env` te permite usar el valor de una variable de entorno en tu archivo de flujo de trabajo. Puedes utilizar el contexto `env` en el valor de cualquier clave en un **paso**, con excepción de las claves `id` y `uses`. Para obtener más información sobre la sintaxis del paso, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". + +Si quieres usar el valor de una variable de entorno dentro de un ejecutor, usa el método normal del sistema operativo del ejecutor para leer las variables de entorno. + +| Nombre de la propiedad | Tipo | Descripción | +| ---------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- | +| `env` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | +| `Env.` | `secuencia` | El valor de una variable de entorno específica. | + +#### contexto de `job` + +El contexto de `job` contiene información sobre el trabajo de ejecución actual. + +| Nombre de la propiedad | Tipo | Descripción | +| ----------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `job` | `objeto` | Este contexto cambia para cada trabajo de una ejecución de flujo de trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | +| `job.container` | `objeto` | Información sobre el contenedor del trabajo. Para obtener más información sobre los contenedores, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)". | +| `job.container.id` | `secuencia` | La Id de la red del contenedor. | +| `job.container.network` | `secuencia` | La Id. de la red del contenedor. El ejecutor crea la red usada por todos los contenedores en un trabajo. | +| `job.services` | `objeto` | Los contenedores de servicio creados para un trabajo. Para obtener más información sobre los contenedores de servicios, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)". | +| `job.services..id` | `secuencia` | La Id del contenedor de servicio. | +| `job.services..network` | `secuencia` | La Id. de la red del contenedor de servicios. El ejecutor crea la red usada por todos los contenedores en un trabajo. | +| `job.services..ports` | `objeto` | Los puertos expuestos del contenedor del servicio. | +| `job.status` | `secuencia` | El estado actual del trabajo. Los valores posibles son `success`, `failure` o `cancelled`. | + +#### contexto de `steps` + +El contexto de `steps` contiene información sobre los pasos del trabajo actual que ya se han ejecutado. + +| Nombre de la propiedad | Tipo | Descripción | +| --------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pasos` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | +| `steps..outputs` | `objeto` | El conjunto de salidas definido para el paso. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". | +| `steps..conclusion` | `secuencia` | El resultado de un paso completado después de que se aplica [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | +| `steps..outcome` | `secuencia` | El resultado de un paso completado antes de que se aplique [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | +| `steps..outputs.` | `secuencia` | El valor de un resultado específico. | + +#### Contexto de `runner` + +El contexto `runner` contiene información sobre el ejecutador (runner) que está ejecutando el trabajo actual. + +| Nombre de la propiedad | Tipo | Descripción | +| ---------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.os` | `secuencia` | El sistema operativo del ejecutor que ejecuta el trabajo. Los valores posibles son `Linux`, `Windows` o `macOS`. | +| `runner.temp` | `secuencia` | La ruta del directorio temporal para el ejecutor. Se garantiza que este directorio estará vacío al inicio de cada trabajo, incluso en los ejecutores autoalojados. | +| `runner.tool_cache` | `secuencia` | La ruta del directorio que contiene algunas de las herramientas preinstaladas para los ejecutores alojados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". | + +#### Contexto `needs` + +El contexto `needs` contiene salidas de todos los jobs que se definen como dependencia del job actual. Para obtener más información sobre la definición de dependencias de jobs, consulta la sección "[Sintaxis de flujos de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". + +| Nombre de la propiedad | Tipo | Descripción | +| -------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------- | +| `needs.` | `objeto` | Un solo job del cual depende el job actual. | +| `needs..outputs` | `objeto` | El conjunto de resultados de un job del cual depende el job actual. | +| `needs..outputs.` | `secuencia` | El valor de un resultado específico para un job del cual depende el job actual. | +| `needs..result` | `secuencia` | El resultado de un job del cual depende el job actual. Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. | + +#### Ejemplo de impresión de información de contexto de un archivo de registro + +Para inspeccionar la información accesible en cada contexto, puedes utilizar este ejemplo de archivo de flujo de trabajo. + +{% data reusables.github-actions.github-context-warning %} + +**.github/workflows/main.yml** +{% raw %} +```yaml +on: push + +jobs: + one: + runs-on: ubuntu-latest + steps: + - name: Dump GitHub context + env: + GITHUB_CONTEXT: ${{ toJson(github) }} + run: echo "$GITHUB_CONTEXT" + - name: Dump job context + env: + JOB_CONTEXT: ${{ toJson(job) }} + run: echo "$JOB_CONTEXT" + - name: Dump steps context + env: + STEPS_CONTEXT: ${{ toJson(steps) }} + run: echo "$STEPS_CONTEXT" + - name: Dump runner context + env: + RUNNER_CONTEXT: ${{ toJson(runner) }} + run: echo "$RUNNER_CONTEXT" + - name: Dump strategy context + env: + STRATEGY_CONTEXT: ${{ toJson(strategy) }} + run: echo "$STRATEGY_CONTEXT" + - name: Dump matrix context + env: + MATRIX_CONTEXT: ${{ toJson(matrix) }} + run: echo "$MATRIX_CONTEXT" +``` +{% endraw %} + +### Literales + +Como parte de una expresión, puedes usar tipos de datos `boolean`, `null`, `number` o `string`. Los literales booleanos no distinguen minúsculas de mayúsculas, por lo que puedes usar `true` o `True`. + +| Tipo de datos | Valor literal | +| ------------- | --------------------------------------------------------------------------------------- | +| `boolean` | `verdadero` o `falso` | +| `null` | `null` | +| `number` | Cualquier formato de número compatible con JSON. | +| `secuencia` | Debes usar comillas simples. Escapar comillas simples literales con una comilla simple. | + +#### Ejemplo + +{% raw %} +```yaml +env: + myNull: ${{ null }} + myBoolean: ${{ false }} + myIntegerNumber: ${{ 711 }} + myFloatNumber: ${{ -9.2 }} + myHexNumber: ${{ 0xff }} + myExponentialNumber: ${{ -2.99-e2 }} + myString: ${{ 'Mona the Octocat' }} + myEscapedString: ${{ 'It''s open source!' } }} +``` +{% endraw %} + +### Operadores + +| Operador | Descripción | +| ------------------------- | -------------------------- | +| `( )` | Agrupación lógica | +| `[ ]` | Índice | +| `.` | Desreferencia de propiedad | +| `!` | No | +| `<` | Menos que | +| `<` | Menor o igual | +| `>` | Mayor que | +| `>=` | Mayor o igual | +| `==` | Igual | +| `!=` | No es igual | +| `&&` | Y | +| \|\| | O | + +{% data variables.product.prodname_dotcom %} realiza comparaciones de igualdad flexible. + +* Si los tipos no coinciden, {% data variables.product.prodname_dotcom %} fuerza el tipo a un número. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con un número usando estas conversiones: + + | Tipo | Resultado | + | --------- | ------------------------------------------------------------------------------------------------------------------------------- | + | Nulo | `0` | + | Booleano | `verdadero` devuelve `1`
    `falso` devuelve `0` | + | Secuencia | Analizado desde cualquier formato de número JSON legal, de lo contrario `NaN`.
    Nota: la cadena vacía devuelve `0`. | + | Arreglo | `NaN` | + | Objeto | `NaN` | +* Una comparación de un `NaN` con otro `NaN` no genera `true`. Para obtener más información, consulta "[Documentos de Mozilla NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)". +* {% data variables.product.prodname_dotcom %} ignora las mayúsculas y minúsculas al comparar cadenas. +* Los objetos y matrices solo se consideran iguales cuando son la misma instancia. + +### Funciones + +{% data variables.product.prodname_dotcom %} ofrece un conjunto de funciones integradas que puedes usar en expresiones. Algunas funciones fusionan valores en una cadena para realizar las comparaciones. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con una cadena usando estas conversiones: + +| Tipo | Resultado | +| -------- | ------------------------------------------------- | +| Nulo | `''` | +| Booleano | `'verdadero'` o `'falso'` | +| Number | Formato decimal, exponencial para grandes números | +| Arreglo | Las matrices no se convierten en cadenas | +| Objeto | Los objetos no se convierten en cadenas | + +#### Contiene + +`contiene (buscar, elemento)` + +Arroja `true` si `search` contiene `item`. Si `search` es una matriz, esta función arroja `true` si el `item` es un elemento de la matriz. Si `search` es una cadena, esta función arroja `true` si el `item` es una subcadena de `search`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. + +##### Ejemplo usando una matriz + +`contains(github.event.issue.labels.*.name, 'bug')` + +##### Ejemplo usando una cadena + +`contains('Hello world', 'llo')` devuelve `verdadero` + +#### startsWith + +`startsWith( searchString, searchValue )` + +Devuelve `verdadero` cuando `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. + +##### Ejemplo + +`startsWith('Hello world', 'He')` regresa a `verdadero` + +#### endsWith + +`endsWith( searchString, searchValue )` + +Devuelve `verdadero` si `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. + +##### Ejemplo + +`endsWith('Hello world', 'He')` devuelve `verdadero` + +#### format + +`format( string, replaceValue0, replaceValue1, ..., replaceValueN)` + +Reemplaza valores en la `cadena`, con la variable `replaceValueN`. Las variables en la `cadena` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `cadena`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar llaves usando llaves dobles. + +##### Ejemplo + +Devuelve 'Hello Mona the Octocat' + +`format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')` + +##### Ejemplo de evasión de llaves + +Devuelve '{Hello Mona the Octocat!}' + +{% raw %} +```js +format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') +``` +{% endraw %} + +#### join + +`join( array, optionalSeparator )` + +El valor para `array` puede ser una matriz o una cadena. Todos los valores en `array` se concatenan en una cadena. Si proporcionas `optionalSeparator`, se inserta entre los valores concatenados. De lo contrario, se usa el separador predeterminado `,`. Fusiona valores en una cadena. + +##### Ejemplo + +`join(github.event.issue.labels.*.name, ', ')` puede devolver 'bug, help wanted' + +#### toJson + +`toJSON(value)` + +Devuelve una representación JSON con formato mejorado de `valor`. Puedes usar esta función para depurar la información suministrada en contextos. + +##### Ejemplo + +`toJSON(job)` puede devolver `{ "status": "Success" }` + +#### fromJson + +`fromJSON(value)` + +Devuelve un objeto de JSON para `value`. Puedes utilizar esta función para proporcionar un objeto de JSON como una expresión evaluada. + +##### Ejemplo + +Este flujo de trabajo configura una matriz de JSON en un job, y lo pasa al siguiente job utilizando un resultado y `fromJSON`. + +{% raw %} +```yaml +name: build +on: push +jobs: + job1: + runs-on: ubuntu-latest + outputs: + matrix: ${{ steps.set-matrix.outputs.matrix }} + steps: + - id: set-matrix + run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" + job2: + needs: job1 + runs-on: ubuntu-latest + strategy: + matrix: ${{fromJson(needs.job1.outputs.matrix)}} + steps: + - run: build +``` +{% endraw %} + +#### hashFiles + +`hashFiles(path)` + +Arroja un solo hash para el conjunto de archivos que coincide con el patrón de `path`. Puedes proporcionar un patrón de `path` o `path` múltiples se parados por comas. El `path` está relacionado con el directorio `GITHUB_WORKSPACE` y solo puede incluir archivos dentro del directorio `GITHUB_WORKSPACE`. Esta función calcula un hash SHA-256 individual para cada archivo coincidente, y luego usa esos hashes para calcular un hash SHA-256 final para el conjunto de archivos. Para más información sobre SHA-256, consulta "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". + +Puedes usar caracteres de coincidencia de patrones para encontrar nombres de archivos. La coincidencia de patrones no distingue mayúsculas de minúsculas en Windows. Para obtener más información acerca de los caracteres compatibles con los patrones, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)". + +##### Ejemplo con un solo patrón + +Encuentra cualquier archivo `package-lock.json` en el repositorio. + +`hashFiles('**/package-lock.json')` + +##### Ejemplo con patrones múltiples + +Crea un hash para cualquier archivo de `package-lock.json` y de `Gemfile.lock` en el repositorio. + +`hashFiles('**/package-lock.json', '**/Gemfile.lock')` + +### Funciones de verificación de estado del trabajo + +Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if` (si). Si la expresión `if` no contiene ninguna de las funciones de estado, se obtendrá automáticamente con `success()`. Para obtener información sobre los condicionales `if`, consulta "[Sintaxis de flujo de trabajo para acciones de GitHub](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)". + +#### success + +Arroja `true` cuando no falló ni se canceló ninguno de los pasos anteriores. + +##### Ejemplo + +```yaml +Pasos: + ... + - name: The job has succeeded + if: {% raw %}${{ success() }}{% endraw %} +``` + +#### always + +Siempre arroja `true`, incluso cuando se cancela. No se ejecutará un trabajo o paso cuando una falla crítica impida que la tarea se ejecute. Por ejemplo, si fallaron las fuentes. + +##### Ejemplo + +```yaml +if: {% raw %}${{ always() }}{% endraw %} +``` + +#### cancelled + +Devuelve `verdadero` si se canceló el flujo de trabajo. + +##### Ejemplo + +```yaml +if: {% raw %}${{ cancelled() }}{% endraw %} +``` + +#### failure + +Arroja `true` cuando falla cualquiera de los pasos anteriores de un trabajo. + +##### Ejemplo + +```yaml +Pasos: + ... + - name: The job has failed + if: {% raw %}${{ failure() }}{% endraw %} +``` + +### Filtros de objetos + +Puedes usar la sintaxis `*` para aplicar un filtro y seleccionar los elementos coincidentes en una recopilación. + +Por ejemplo, considera una matriz de objetos llamada `fruits`. + +```json +[ + { "name": "apple", "quantity": 1 }, + { "name": "orange", "quantity": 2 }, + { "name": "pear", "quantity": 1 } +] +``` + +El filtro `fruits.*.name` devuelve la matriz `[ "apple", "orange", "pear" ]` diff --git a/translations/es-ES/content/actions/reference/encrypted-secrets.md b/translations/es-ES/content/actions/reference/encrypted-secrets.md new file mode 100644 index 0000000000000..680bf62da6044 --- /dev/null +++ b/translations/es-ES/content/actions/reference/encrypted-secrets.md @@ -0,0 +1,248 @@ +--- +title: Secretos cifrados +intro: Los secretos cifrados te permiten almacenar información sensible en tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio o ambientes de repositorio{% else %} o repositorio{% endif %}. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets + - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets + - /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.environments-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los secretos cifrados + +Los secretos son variables de ambiente cifradas que creas en una organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio, o ambiente de repositorio{% else %} o repositorio{% endif %}. Los secretos que creas están disponibles para utilizarse en los flujos de trabajo de {% data variables.product.prodname_actions %}. {% data variables.product.prodname_dotcom %} utiliza una [caja sellada de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para ayudarte a garantizar que los secretos se cifran antes de llegar a {% data variables.product.prodname_dotcom %} y que permanezcan cifrados hasta que los utilices en un flujo de trabajo. + +{% data reusables.github-actions.secrets-org-level-overview %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Para que los secretos se almacenen a nivel de ambiente, puedes habilitar los revisores requeridos para controlar el acceso a los secretos. Un job de flujo de trabajo no puede acceder a los secretos del ambiente hasta que los revisores requeridos le otorguen aprobación. +{% endif %} + +#### Nombrar tus secretos + +Las siguientes reglas aplican a los nombres secretos: + +* Los nombres secretos solo contienen caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) o guiones bajos (`_`). No se permiten espacios. +* Los nombres secretos no deben comenzar con el prefijo `GITHUB_`. +* Los nombres secretos no deben comenzar con un número. +* Los nombres de secreto no distinguen entre mayúsculas y minúsculas. +* Los nombres secretos deben ser únicos en el nivel en el que se hayan creado. Por ejemplo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}un secreto que se creó a nivel de ambiente debe tener un nombre único en éste, {% endif %}un secreto que se creó a nivel de repositorio debe tener un nombre único en éste, y un secreto que se creó a nivel de organización debe tener un nombre único en este nivel. + + Si un secreto con el mismo nombre existe en varios niveles, aquél en el nivel más bajo tomará presedencia. Por ejemplo, si un secreto a nivel de organización tiene el mismo nombre que uno a nivel de repositorio, entonces aquél a nivel de repositorio tomará precedencia.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} De forma similar, si tanto una organización, como un repositorio, como un ambiente tienen un secreto con el mismo nombre, aquél a nivel de ambiente tomará precedencia.{% endif %} + +Para ayudarte a garantizar que {% data variables.product.prodname_dotcom %} redacta tus secretos en bitácoras, evita utilizar datos estructurados como los valores de los secretos. Por ejemplo, evita crear secretos que contengan JSON o blobs de Git codificados. + +#### Acceder a tus secretos + +Para hacer que un secreto esté disponible para una acción, debes configurar el secreto como una variable de entrada o de entorno en tu archivo de flujo de trabajo. Revisa el archivo README de la acción para saber qué variables de entrada y de entorno espera la acción. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)". + +Puedes usar y leer secretos cifrados en un archivo de flujo de trabajo si tienes acceso para editar el archivo. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)." + +{% warning %} + +**Advertencia:** {% data variables.product.prodname_dotcom %} redacta automáticamente secretos impresos en el registro, pero debes evitar imprimir secretos en el registro intencionalmente. + +{% endwarning %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Los secretos de organización y de repositorio se leen cuando una ejecución de flujo de trabajo está en cola y los secretos de ambiente se leen cuando un job que referencia el ambiente comienza. +{% endif %} + +También puedes administrar secretos utilizando la API de REST. Para obtener más información, consulta la sección "[Secretos](/rest/reference/actions#secrets)". + +#### Limitar permisos de credenciales + +Cuando generes credenciales, te recomendamos que otorgues los mínimos permisos posibles. Por ejemplo, en lugar de usar credenciales personales, usa [implementar claves](/developers/overview/managing-deploy-keys#deploy-keys) o una cuenta de servicio. Considera otorgar permisos de solo lectura si eso es todo lo que se necesita, y limita el acceso lo máximo posible. Cuando generes un token de acceso personal (PAT), selecciona el menor número de ámbitos necesarios. + +### Crear secretos cifrados para un repositorio + +{% data reusables.github-actions.permissions-statement-secrets-repository %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Da clic en **Secreto de repositorio nuevo**. +1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. +1. Ingresa el valor de tu secreto. +1. Haz clic en **Agregar secreto** (Agregar secreto). + +Si tu repositorio {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}tiene secretos de ambiente o {% endif %}puede acceder a los secretos de la organización padre, entonces estos secretos también se listan en esta página. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Crear secretos cifrados para un ambiente + +{% data reusables.github-actions.permissions-statement-secrets-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Da clic en el ambiente al cual quieras agregar un secreto. +1. Debajo de **Secretos de ambiente**, da clic en **Agregar secreto**. +1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. +1. Ingresa el valor de tu secreto. +1. Haz clic en **Agregar secreto** (Agregar secreto). +{% endif %} + +### Crear secretos cifrados para una organización + +Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Da clic en **Secreto de organización nuevo**. +1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. +1. Ingresa el **Valor** para tu secreto. +1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. +1. Haz clic en **Agregar secreto** (Agregar secreto). + +### Revisar el acceso a los secretos de nivel organizacional + +Puedes revisar qué políticas de acceso se están aplicando a un secreto en tu organización. + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: ![Lista de secretos](/assets/images/help/settings/actions-org-secrets-list.png) +1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**. + +### Usar secretos cifrados en un flujo de trabajo + +{% data reusables.actions.forked-secrets %} + +Para proporcionar una acción con un secreto como variable de entrada o de entorno, puedes usar el contexto de `secrets` para acceder a los secretos que has creado en tu repositorio. Para obtener más información, consulta "[Sintaxis de contexto y de expresiones para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions) y [Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". + +{% raw %} +```yaml +steps: + - name: Hello world action + with: # Set the secret as an input + super_secret: ${{ secrets.SuperSecret }} + env: # Or as an environment variable + super_secret: ${{ secrets.SuperSecret }} +``` +{% endraw %} + +Evita pasar secretos entre procesos desde la línea de comando, siempre que sea posible. Los procesos de la línea de comando pueden ser visibles para otros usuarios (utilizando el comando `ps`) o ser capturados por [eventos de auditoría de seguridad](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). Para ayudar a proteger los secretos, considera usar variables de entorno, `STDIN` u otros mecanismos admitidos por el proceso de destino. + +Si debes pasar secretos dentro de una línea de comando, enciérralos usando las normas de uso de comillas adecuadas. Los secretos suelen contener caracteres especiales que pueden afectar involuntariamente a tu shell. Para evitar estos caracteres especiales, usa comillas en tus variables de entorno. Por ejemplo: + +#### Ejemplo usando Bash + +{% raw %} +```yaml +steps: + - shell: bash + env: + SUPER_SECRET: ${{ secrets.SuperSecret }} + run: | + example-command "$SUPER_SECRET" +``` +{% endraw %} + +#### Ejemplo usando PowerShell + +{% raw %} +```yaml +steps: + - shell: pwsh + env: + SUPER_SECRET: ${{ secrets.SuperSecret }} + run: | + example-command "$env:SUPER_SECRET" +``` +{% endraw %} + +#### Ejemplo usando Cmd.exe + +{% raw %} +```yaml +steps: + - shell: cmd + env: + SUPER_SECRET: ${{ secrets.SuperSecret }} + run: | + example-command "%SUPER_SECRET%" +``` +{% endraw %} + +### Límites para los secretos + +Puedes almacenar hasta 1,000 secretos por organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, 100 secretos por repositorio y 100 secretos por ambiente{% else %} y 100 secretos por repositorio{% endif %}. Un flujo de trabajo podría utilizar hasta 100 secretos de organización y 100 secretos de repositorio.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Adicionalmente, un job que referencia un ambiente puede utilizar hasta 100 secretos de ambiente.{% endif %} + +Los secretos tienen un tamaño máximo de 64 KB. Para usar secretos de un tamaño mayor a 64 KB, puedes almacenar los secretos cifrados en tu repositorio y guardar la contraseña de descifrado como un secreto en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes usar `gpg` para cifrar tus credenciales de manera local antes de verificar el archivo en tu repositorio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la página del manual "[gpg](https://www.gnupg.org/gph/de/manual/r1023.html)". + +{% warning %} + +**Advertencia**: Evita que tus secretos se impriman cuando se ejecute tu acción. Cuando usas esta solución, {% data variables.product.prodname_dotcom %} no redacta los secretos que están impresos en los registros. + +{% endwarning %} + +1. Ejecuta el siguiente comando en tu terminal para cifrar el archivo `my_secret.json` usando `gpg` y el algoritmo de cifras AES256. + + ``` shell + $ gpg --symmetric --cipher-algo AES256 my_secret.json + ``` + +1. Se te pedirá que ingreses una contraseña. Recuerda la contraseña, porque deberás crear un nuevo secreto en {% data variables.product.prodname_dotcom %} que use esa contraseña como valor. + +1. Crear un nuevo secreto que contiene la frase de acceso. Por ejemplo, crea un nuevo secreto con el nombre `LARGE_SECRET_PASSPHRASE` y establece el valor del secreto para la contraseña que seleccionaste en el paso anterior. + +1. Copia tu archivo cifrado en tu repositorio y confírmalo. En este ejemplo, el archivo cifrado es `my_secret.json.gpg`. + +1. Crea un script shell para descifrar la contraseña. Guarda este archivo como `decrypt_secret.sh`. + + ``` shell + #!/bin/sh + + # Decrypt the file + mkdir $HOME/secrets + # --batch to prevent interactive command + # --yes to assume "yes" for questions + gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \ + --output $HOME/secrets/my_secret.json my_secret.json.gpg + ``` + +1. Asegúrate de que tu shell script sea ejecutable antes de verificarlo en tu repositorio. + + ``` shell + $ chmod +x decrypt_secret.sh + $ git add decrypt_secret.sh + $ git commit -m "Add new decryption script" + $ git push + ``` + +1. En tu flujo de trabajo, usa un `step` para llamar al shell script y descifrar el secreto. Para tener una copia de tu repositorio en el entorno en el que se ejecuta tu flujo de trabajo, deberás usar la acción [`code>actions/checkout`](https://github.com/actions/checkout). Haz referencia a tu shell script usando el comando `run` relacionado con la raíz de tu repositorio. + +{% raw %} + ```yaml + name: Workflows with large secrets + + on: push + + jobs: + my-job: + name: My Job + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Decrypt large secret + run: ./.github/scripts/decrypt_secret.sh + env: + LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }} + # Este comando es solo un ejemplo para mostrar cómo se imprime tu secreto. + # Asegúrate de eliminar las declaraciones impresas de tus secretos. GitHub + # no oculta los secretos que usan esta solución. + - name: Test printing your secret (Elimina este paso en la producción) + run: cat $HOME/secrets/my_secret.json + ``` +{% endraw %} diff --git a/translations/es-ES/content/actions/reference/environment-variables.md b/translations/es-ES/content/actions/reference/environment-variables.md new file mode 100644 index 0000000000000..18a21c10f46d3 --- /dev/null +++ b/translations/es-ES/content/actions/reference/environment-variables.md @@ -0,0 +1,78 @@ +--- +title: Variables del entorno +intro: '{% data variables.product.prodname_dotcom %} establece variables de entorno predeterminadas para cada ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}. También puedes establecer variables de entorno personalizadas en tu archivo de flujo de trabajo.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /github/automating-your-workflow-with-github-actions/using-environment-variables + - /actions/automating-your-workflow-with-github-actions/using-environment-variables + - /actions/configuring-and-managing-workflows/using-environment-variables +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de las variables de entorno + +{% data variables.product.prodname_dotcom %} establece las variables de entorno predeterminadas que están disponibles para cada paso en una ejecución de flujo de trabajo. Las variables de entorno distinguen mayúsculas de minúsculas. Los comandos que se ejecutan en acciones o pasos pueden crear, leer y modificar variables de entorno. + +Para establecer variables de entorno personalizadas, debes especificar las variables en el archivo de flujo de trabajo. Puedes definir variables de ambiente para un paso, job o para todo el flujo de trabajo si utilizas las palabras clave [`jobs..steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs..env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), y [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env). Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)". + +```yaml +steps: + - name: Hello world + run: echo Hello world $FIRST_NAME $middle_name $Last_Name! + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat +``` + +Tambièn puedes utilizar el archivo de ambiente de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV`{% else %} el comando de flujo de trabajo `set-env`{% endif %} para configurar una variable de ambiente que pueda utilizar los siguientes pasos en un flujo de trabajo. El {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}archivo de ambiente{% else %} comando `set-env`{% endif %} puede utilizarse directamente a travès de una acciòn o como un comando de shell en un archivo de trabajo utilizando la palabra clave `run`. Para obtener más información, consulta "[Comandos de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)." + +### Variables de entorno predeterminadas + +Te recomendamos encarecidamente que las acciones usen variables de entorno para acceder al sistema de archivos en lugar de usar rutas de archivo codificadas de forma rígida. {% data variables.product.prodname_dotcom %} establece variables de entorno para que las acciones se utilicen en todos los entornos del ejecutador. + +| Variable de entorno | Descripción | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `CI` | Siempre configurar en `true`. | +| `GITHUB_WORKFLOW` | El nombre del flujo de trabajo. | +| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} +| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} +| `GITHUB_ACTION` | El único identificador (`id`) de la acción. | +| `GITHUB_ACTIONS` | Siempre establecido en `true` cuando {% data variables.product.prodname_actions %} está ejecutando el flujo de trabajo. Puedes usar esta variable para diferenciar cuando las pruebas se ejecutan de forma local o mediante {% data variables.product.prodname_actions %}. | +| `GITHUB_ACTOR` | El nombre de la persona o de la aplicación que inició el flujo de trabajo. Por ejemplo, `octocat`. | +| `GITHUB_REPOSITORY` | El nombre del repositorio y del propietario. Por ejemplo, `octocat/Hello-World`. | +| `GITHUB_EVENT_NAME` | El nombre del evento webhook que activó el flujo de trabajo. | +| `GITHUB_EVENT_PATH` | La ruta del archivo con la carga completa del evento webhook. Por ejemplo, `/github/workflow/event.json`. | +| `GITHUB_WORKSPACE` | La ruta del directorio del espacio de trabajo de {% data variables.product.prodname_dotcom %}. El directorio de espacio de trabajo es una copia de tu repositorio si tu flujo de trabajo utiliza la acciòn [actions/checkout](https://github.com/actions/checkout). Si no usas la acción `actions/checkout`, el directorio estará vacío. Por ejemplo, `/home/runner/work/my-repo-name/my-repo-name`. | +| `GITHUB_SHA` | El SHA de confirmación que activó el flujo de trabajo. Por ejemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | +| `GITHUB_REF` | La referencia de etiqueta o rama que activó el flujo de trabajo. Por ejemplo, `refs/heads/feature-branch-1`. Si no hay una rama o una etiqueta disponible para el tipo de evento, la variable no existirá. | +| `GITHUB_HEAD_REF` | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama principal. | +| `GITHUB_BASE_REF` | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama base. | +| `GITHUB_SERVER_URL` | Devuelve la URL del servidor de {% data variables.product.product_name %}. Por ejemplo: `https://github.com`. | +| `GITHUB_API_URL` | Devuelve la URL de la API. Por ejemplo: `https://api.github.com`. | +| `GITHUB_GRAPHQL_URL` | Devuelve la URL de la API de GraphQL. Por ejemplo: `https://api.github.com/graphql`. | + +{% tip %} + +**Nota:** Si necesitas utilizar la URL de la ejecución de un flujo de trabajo desde dentro de un job, puedes combinar estas variables de ambiente: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determinar cuándo utilizar las variables de ambiente o contextos predeterminados + +{% data reusables.github-actions.using-context-or-environment-variables %} + +### Convenciones de nomenclatura para las variables de entorno + +{% note %} + +**Nota:**{% data variables.product.prodname_dotcom %} reserva el prefijo de la variable de ambiente `GITHUB_` para uso interno de {% data variables.product.prodname_dotcom %}. Configurar una variable de entorno o secreto con el prefijo `GITHUB_` dará como resultado un error. + +{% endnote %} + +Toda variable de entorno nueva que configures y que apunte a una ubicación en el sistema de archivos debe tener un sufijo `_PATH`. Las variables predeterminadas `HOME` y `GITHUB_WORKSPACE` son excepciones a esta convención, porque las palabras "inicio" (home) y "espacio de trabajo" (workspace) ya implican una ubicación. diff --git a/translations/es-ES/content/actions/reference/environments.md b/translations/es-ES/content/actions/reference/environments.md new file mode 100644 index 0000000000000..da3e8dcbf08fd --- /dev/null +++ b/translations/es-ES/content/actions/reference/environments.md @@ -0,0 +1,69 @@ +--- +title: Ambientes +intro: Puedes configurr ambientes con reglas de protección y secretos. Un job de un flujo de trabajo puede referenciar un ambiente para utilizar las reglas de protección y secretos de dicho ambiente. +product: '{% data reusables.gated-features.environments %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.environments-beta %} + +### Acerca de los ambientes + +Puedes configurr ambientes con reglas de protección y secretos. Cuando un job de un flujo de trabajo referencia un ambiente, el job no comenzará hasta que todas las reglas de protección del ambiente pasen. Un job tampoco puede acceder a los secretos que se definen en un ambiente sino hasta que todas las reglas de protección de dicho ambiente pasen. + +{% if currentVersion == "free-pro-team@latest" %} +Las reglas de protección del ambiente y secretos de ambiente solo se encuentran disponibles en los repositorios públicos. Si conviertes un repositorio de público a privado, cualquier regla de protección o secretos de ambiente que hubieses configurado se ingorarán y no podrás configurar ningún ambiente. Si conviertes tu repositorio en público nuevamente, tendrás acceso a cualquier regla de protección y secreto de ambiente que hubieras configurado previamente. +{% endif %} + +#### Reglas de protección de ambiente + +Las reglas de protección de ambiente requieren que pasen condiciones específicas antes de que un job que referencia al ambiente pueda proceder. Puedes utilizar reglas de protección de ambiente para requerir aprobaciones manuales o para retrasar un job. + +##### Revisores requeridos + +Utiliza los revisores requeridos para requerir que una persona o equipo específicos aprueben los jobs del flujo de trabajo que referencian el ambiente. Puedes listar hasta seis usuarios o equipos como revisores. Los revisores deben tener acceso de lectura en el repositorio como mínimo. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder. + +Para obtener más información sobre cómo revisar jobs que referencian un ambiente con revisores requeridos, consulta la sección "[revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". + +##### Temporizador de espera + +Utiliza un temporizador de espera para retrasar un job durante una cantidad de tiempo específica después de que el job se active inicialmente. El tiempo (en minutos) debe ser un número entero entre 0 y 43,200 (30 días). + +#### Secretos de ambiente + +Los secretos que se almacenan en un ambiente sólo se encuentran disponibles para los jobs de flujo de trabajo que referencien el ambiente. Si el ambiente requiere aprobación, un job no puede acceder a secretos de ambiente hasta que uno de los revisores requeridos lo apruebe. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)". + +### Crear un ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Da clic en **Ambiente nuevo**. +1. Ingresa un nombre para el ambiente y luego da clic en **Configurar ambiente**. Los nombres de ambiente no distinguen entre mayúsculas y minúsculas. Un nombre de ambiente no deberá exceder los 255 caracteres y deberá ser único dentro del repositorio. +1. Configura cualquier regla de protección o secreto de ambiente. + +El ejecutar un flujo de trabajo que referencie un ambiente que no existe creará un ambiente con el nombre referenciado. El ambiente recién creado no tendrá configurada ninguna regla de protección o secreto. Cualquiera que pueda editar flujos de trabajo en el repositorio podrá crear ambientes a través de un archivo de flujo de trabajo, pero solo los administradoresd e repositorio pueden configurar el ambiente. + +### Referenciar un ambiente + +Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. Cuando el job se envía al ejecutor, éste puede acceder a los secretos del ambiente. + +Para obtener más información sobre la sintaxis para referenciar ambientes en los flujos de trabajo, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment)". Para obtener más información sobre cómo revisar jobs que referencian un ambiente con revisores requeridos, consulta la sección "[revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". + +Cuando un flujo de trabajo referencia un ambiente, éste aparecerá en los despliegues del repositorio. Para obtener más información acerca de visualizar los despliegues actuales y previos, consulta la sección "[Visualizar el historial de despliegues](/developers/overview/viewing-deployment-history)". + +### Borrar un ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +El borrar un ambiente borrará todos los secretos y reglas de protección asociadas con éste. Cualquier job que esté actualmente en espera porque depende de las reglas de protección del ambiente que se borró, fallará automáticamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Junto al ambiente que quieres borrar, da clic en {% octicon "trashcan" aria-label="The trashcan icon" %}. +2. Da clic en **Entiendo, borra este ambiente**. diff --git a/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md new file mode 100644 index 0000000000000..f35d0991036cf --- /dev/null +++ b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md @@ -0,0 +1,737 @@ +--- +title: Eventos que desencadenan flujos de trabajo +intro: 'Puedes configurar tus flujos de trabajo para que se ejecuten cuando ocurre una actividad específica en {% data variables.product.product_name %}, en un horario programado o cuando se produce un evento fuera de {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.actions %}' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/events-that-trigger-workflows + - /github/automating-your-workflow-with-github-actions/events-that-trigger-workflows + - /actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Configurar los eventos del flujo de trabajo + +Puedes configurar los flujos de trabajo para que se ejecuten una o más veces utilizando la sintaxis de flujo de trabajo `on`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)". + +{% data reusables.github-actions.actions-on-examples %} + +{% note %} + +**Nota:** No puedes activar nuevas ejecuciones de flujo de trabajo usando el `GITHUB_TOKEN`. Para obtener más información, consulta "[Activar nuevos flujos de trabajo mediante un token de acceso personal](#triggering-new-workflows-using-a-personal-access-token)". + +{% endnote %} + +Los siguientes pasos se producen para activar una ejecución de flujo de trabajo: + +1. Se produce un evento en tu repositorio, y el evento resultante tiene una confirmación de SHA y una referencia de Git asociadas. +2. El directorio `.github/workflows` en tu repositorio se busca para los archivos de flujo de trabajo en la confirmación SHA o la referencia de Git asociadas. Los archivos de flujo de trabajo deben estar presentes en la confirmación SHA o la referencia de Git que se debe tener en cuenta. + + Por ejemplo, si el evento se produjo en una rama particular del repositorio, los archivos de flujo de trabajo deben estar presentes en el repositorio en esa rama. +1. Se inspeccionarán los archivos de flujo de trabajo para esa confirmación de SHA y referencia de Git, y se activará una nueva ejecución de flujo de trabajo para cualquier flujo de trabajo que tenga valores `on:` que coincidan con el evento desencadenante. + + El flujo de trabajo se ejecuta en el código de tu repositorio en la misma confirmación SHA y la referencia de Git que desencadenó el evento. Cuando se ejecuta un flujo de trabajo, {% data variables.product.product_name %} establece las variables de entorno `GITHUB_SHA` (confirmar SHA) y `GITHUB_REF` (referencia de Git) en el entorno del ejecutor. Para obtener más información, consulta "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". + +### Eventos programados + +El evento `schedule` te permite activar un flujo de trabajo en una hora programada. + +#### `schedule` + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------ | ------------------ | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n/a | n/a | Última confirmación en la rama predeterminada | Rama por defecto | Cuando se establece la ejecución del flujo de trabajo programado. Un flujo de trabajo programado usa[sintaxis cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Para obtener más información, consulta "[Desencadenar un flujo de trabajo con eventos](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)". | + +{% data reusables.repositories.actions-scheduled-workflow-example %} + +La sintaxis de cron tiene cinco campos separados por un espacio, y cada campo representa una unidad de tiempo. + +``` +┌───────────── minuto (0 - 59) +│ ┌───────────── hora (0 - 23) +│ │ ┌───────────── día del mes (1 - 31) +│ │ │ ┌───────────── mes (1 - 12 o EN-DIC) +│ │ │ │ ┌───────────── día de la semana (0 - 6 o DOM-SÁB) +│ │ │ │ │ +│ │ │ │ │ +│ │ │ │ │ +* * * * * +``` + +Puedes usar estos operadores en cualquiera de los cinco campos: + +| Operador | Descripción | Ejemplo | +| -------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------- | +| * | Cualquier valor | `* * * * *` se ejecuta todos los días a cada minuto. | +| , | Separador de la lista de valores | `2,10 4,5 * * *` se ejecuta en el minuto 2 y 10 de la cuarta y quinta hora de cada día. | +| - | Rango de valores | `0 4-6 * * *` se ejecuta en el minuto 0 de la cuarta, quinta y sexta hora. | +| / | Valores del paso | `20/15 * * * *` se ejecuta cada 15 minutos a partir del minuto 20 hasta el minuto 59 (minutos 20, 35 y 50). | + +{% note %} + +**Nota:** {% data variables.product.prodname_actions %} no es compatible con la sintaxis que no es estándar `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly` y `@reboot`. + +{% endnote %} + +Puedes usar [contrab guru](https://crontab.guru/) para generar tu sintaxis de cron y confirmar a qué hora se ejecutará. Para que puedas comenzar, hay también una lista de [ejemplos de crontab guru](https://crontab.guru/examples.html). + +Las notificaciones para los flujos de trabajo programados se envían al usuario que modificó por última vez la sintaxis de cron en el archivo de flujo de trabajo. Para obtener más información, por favor consulta la sección "[Notificaciones para las ejecuciones de flujo de trabajo](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)". + +### Eventos manuales + +Puedes activar ejecuciones de flujo de trabajo manualmente. Para activar flujos de trabajo específicos en un repositorio, utiliza el evento `workflow_dispatch`. Para activar más de un flujo de trabajo en un repositorio y crear eventos personalizados y tipos de eventos, utiliza el evento `repository_dispatch`. + +#### `workflow_dispatch` + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------------------- | ------------------ | ---------------------------------------------- | ------------------------- | +| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Última confirmacion en la rama de `GITHUB_REF` | Rama que recibió el envío | + +Puedes configurar propiedades de entrada definidas personalmente, valores de entrada predeterminados y entradas requeridas para el evento directamente en tu flujo de trabajo. Cuando se ejecuta el flujod e trabajo, puedes acceder a los valores de entrada en el contexto de `github.event.inputs`. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +Puedes activar una ejecución de flujo de trabajo manualmente si utilizas la API de {% data variables.product.product_name %} y desde {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Ejecutar un flujo de trabajo manualmente](/actions/managing-workflow-runs/manually-running-a-workflow)". + + Cuando activas el evento en {% data variables.product.prodname_dotcom %}, puedes proporcionar la `ref` y cualquier `input` directamente en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Utilizar entradas y salidas con una acción](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)". + + Para activar el evento de webhook personalizado de `workflow_dispatch` utilizando la API de REST, debes enviar una solicitud de `POST` a la terminal de la API de {% data variables.product.prodname_dotcom %} y proporcionar la `ref` y cualquier `input` relacionado. Para obtener más información, consulta terminal "[Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)" de la API de REST. + +##### Ejemplo + +Para utilizar el evento de `workflow_dispatch`, necesitas incluirlo como un activador en tu archivo de flujo de trabajo de GitHub Actions. El siguiente ejemplo ejecuta el flujo de trabajo únicamente cuando se activa manualmente: + +```yaml +on: workflow_dispatch +``` + +##### Ejemplo de configuración de flujo de trabajo + +Este ejemplo define las entradas `name` y `home` y las imprime utilizando los contextos `github.event.inputs.name` y `github.event.inputs.home`. Si no se proporciona un `home`, se imprime el valor predeterminado 'The Octoverse'. + +{% raw %} +```yaml +name: Manually triggered workflow +on: + workflow_dispatch: + inputs: + name: + description: 'Person to greet' + required: true + default: 'Mona the Octocat' + home: + description: 'location' + required: false + default: 'The Octoverse' + +jobs: + say_hello: + runs-on: ubuntu-latest + steps: + - run: | + echo "Hello ${{ github.event.inputs.name }}!" + echo "- in ${{ github.event.inputs.home }}!" +``` +{% endraw %} + +#### `repository_dispatch` + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.github-actions.branch-requirement %} + +Puedes utilizar la API de {% data variables.product.product_name %} para desencadenar un evento de webhook llamado [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) cuando quieras desencadenar un flujo de trabajo para una actividad que sucede fuera de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)" en." + +Para desencadenar el evento de webhook `repository_dispatch` personalizado, debes enviar una solicitud de `POST` a un punto final de una API de {% data variables.product.product_name %} y dar un nombre de `event_type` para describir el tipo de actividad. Para desencadenar la ejecución de un flujo de trabajo, también debes configurar tu flujo de trabajo para usar el evento `repository_dispatch`. + +##### Ejemplo + +Predeterminadamente, todos los `event_types` desencadenan la ejecución de un flujo de trabajo. Puedes limitar tu flujo de trabajo para que se ejecute cuando un valor específico de `event_type` se envíe en la carga útil del webhook de `repository_dispatch`. Tú defines los tipos de evento enviados en la carga útil de `repository_dispatch` cuando creas el repositorio. + +```yaml +on: + repository_dispatch: + types: [opened, deleted] +``` + +### Eventos de webhook + +Puedes configurar tu flujo de trabajo para que se ejecute cuando se crean eventos de webhook en GitHub. Algunos eventos tienen más de un tipo de actividad que activa el evento. Si más de un tipo de actividad activa el evento, puedes especificar qué tipos de actividad activarán el flujo de trabajo para que se ejecute. Para obtener más información, consulta la sección "[webhooks](/webhooks)". + +#### `check_run` + +Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `check_run`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Ejecuciones de verificación](/rest/reference/checks#runs)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`
    - `rerequested`
    - `completed`
    - `requested_action` | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `requested_action`. + +```yaml +on: + check_run: + types: [rerequested, requested_action] +``` + +#### `check_suite` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `check_suite`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección de "[conjuntos de verificaciones](/rest/reference/checks#suites)". + +{% data reusables.github-actions.branch-requirement %} + +{% note %} + +**Nota:** Para evitar flujos de trabajo recurrentes, este evento no activa flujos de trabajo si la comprobación de suite fue creada por {% data variables.product.prodname_actions %}. + +{% endnote %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------------ | -------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`
    - `requested`
    - `rerequested`
    | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `completada`. + +```yaml +on: + check_suite: + types: [rerequested, completed] +``` + +#### `create (crear)` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, lo que activa el evento `crear`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una referencia](/rest/reference/git#create-a-reference)". + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------- | ------------------ | ------------------------------------------------ | ---------------------- | +| [`create (crear)`](/webhooks/event-payloads/#create) | n/a | Última confirmación en la rama o etiqueta creada | Rama o etiqueta creada | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `crear`. + +```yaml +on: + create +``` + +#### `eliminar` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, lo que activa el evento `delete`. Para obtener más información sobre la API de REST, consulta la sección "[Borrar una referencia](/rest/reference/git#delete-a-reference)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [`eliminar`](/webhooks/event-payloads/#delete) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `delete`. + +```yaml +on: + delete +``` + +#### `deployment` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una implementación, lo que activa el evento `deployment`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------- | ------------------ | ------------------------------ | ------------------------------------------------------------------ | +| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `deployment`. + +```yaml +on: + deployment +``` + +#### `deployment_status` + +Ejecuta tu flujo de trabajo en cualquier momento en que un tercero proporcione un estado de implementación, lo que activa un evento `deployment_status`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Crear un estado de despliegue](/rest/reference/repos#create-a-deployment-status)". + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------------------------ | ------------------ | ------------------------------ | ------------------------------------------------------------------ | +| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `deployment`. + +```yaml +on: + deployment_status +``` + +#### `fork` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien bifurque un repositorio, lo que activa el evento de `fork`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una bifurcación](/rest/reference/repos#create-a-fork)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [`fork`](/webhooks/event-payloads/#fork) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `fork`. + +```yaml +on: + fork +``` + +#### `gollum` + +Ejecuta tu flujo de trabajo cuando alguien crea o actualiza una página Wiki, lo que activa el evento `gollum`. + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `gollum`. + +```yaml +on: + gollum +``` + +#### `comentario_propuesta` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `issue_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[comentarios de un informe de problemas](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`comentario_propuesta`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `created` (creada) o `deleted` (eliminada). + +```yaml +on: + issue_comment: + types: [created, deleted] +``` + +El evento `issue_comment` ocurre para los comentarios tanto en propuestas como en solicitudes de cambios. Para determinar si el evento `issue_comment` se activó desde una propuesta o solicitud de cambios, puedes verificar la carga útil del evento para la propiedad `issue.pull_request` y utilizarla como condición para saltarse un job. + +Por ejemplo, puedes elegir ejecutar el job `pr_commented` cuando ocurren los comentarios de evento en una solicitud de cambios, y el job `issue_commented` cuando ocurran eventos de comentarios en una propuesta. + +{% raw %} +```yaml +on: issue_comment + +jobs: + pr_commented: + # This job only runs for pull request comments + name: PR comment + if: ${{ github.event.issue.pull_request }} + runs-on: ubuntu-latest + steps: + - run: | + echo "Comment on PR #${{ github.event.issue.number }}" + + issue-commented: + # This job only runs for issue comments + name: Issue comment + if: ${{ !github.event.issue.pull_request }} + runs-on: ubuntu-latest + steps: + - run: | + echo "Comment on issue #${{ github.event.issue.number }}" +``` +{% endraw %} + +#### `propuestas` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `issues`. {% data reusables.developer-site.multiple_activity_types %} Para obtener información acerca de la API de REST, consulta la sección "[informes de problemas](/rest/reference/issues)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`propuestas`](/webhooks/event-payloads/#issues) | - `opened`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `closed`
    - `reopened`
    - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `milestoned`
    - `demilestoned` | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `opened` (abierta), `edited` (editada), o `milestoned` (marcada como hito). + +```yaml +on: + issues: + types: [opened, edited, milestoned] +``` + +#### `label` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `label`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Etiquetas](/rest/reference/issues#labels)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------ | ----------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`label`](/webhooks/event-payloads/#label) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una etiqueta ha sido `created` (creada) o `deleted` (eliminada). + +```yaml +on: + label: + types: [created, deleted] +``` + +#### `milestone` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `milestone`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Hitos](/rest/reference/issues#milestones)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`milestone`](/webhooks/event-payloads/#milestone) | - `created`
    - `closed`
    - `opened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando un hito ha sido `opened` o `deleted`. + +```yaml +on: + milestone: + types: [opened, deleted] +``` + +#### `page_build` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien suba a una rama habilitada para páginas {% data variables.product.product_name %}, lo que activa el evento `page_build`. Para obtener información acerca de la API de REST, consulta la sección "[Páginas](/rest/reference/repos#pages)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------- | ------------------ | --------------------------------------------- | ------------ | +| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Última confirmación en la rama predeterminada | n/a | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `page_build`. + +```yaml +on: + page_build +``` + +#### `project` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Proyectos](/rest/reference/projects)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`project`](/webhooks/event-payloads/#project) | - `created`
    - `updated`
    - `closed`
    - `reopened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `created` o `deleted`. + +```yaml +on: + project: + types: [created, deleted] +``` + +#### `project_card` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_card`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Tarjetas de proyecto](/rest/reference/projects#cards)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`
    - `moved`
    - `converted` to an issue
    - `edited`
    - `deleted` | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una tarjeta de proyecto ha sido `opened` o `deleted`. + +```yaml +on: + project_card: + types: [opened, deleted] +``` + +#### `project_column` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_column`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Columnas de proyecto](/rest/reference/projects#columns)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------------------ | --------------------------------------------------------------------------- | --------------------------------------------- | ---------------- | +| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`
    - `updated`
    - `moved`
    - `deleted` | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una columna de proyecto ha sido `created` o `deleted`. + +```yaml +on: + project_column: + types: [created, deleted] +``` + +#### `public` + +Ejecuta tu flujo de trabajo en cualquier momento en que alguien haga público un repositorio privado, lo que activa el evento `public`. Para obtener más información acerca de la API de REST, consulta la sección "[Editar repositorios](/rest/reference/repos#edit)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [`public`](/webhooks/event-payloads/#public) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `public`. + +```yaml +on: + public +``` + +#### `solicitud_extracción` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `pull_request`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Solicitudes de extraccións](/rest/reference/pulls)". + +{% note %} + +**Nota:** Por defecto, un flujo de trabajo solo se ejecuta cuando un tipo de actividad de `pull_request` es `opened` (abierta), `synchronize` (sincronizada) o `reopened` (reabierta). Para activar los flujos de trabajo para más tipos de actividad, usa la palabra clave `types`. + +{% endnote %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | +| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | + +Puedes extender o limitar los tipos de actividad predeterminados usando la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. + +```yaml +on: + pull_request: + types: [assigned, opened, synchronize, reopened] +``` + +{% data reusables.developer-site.pull_request_forked_repos_link %} + +#### `revisión_solicitud de extracción` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `pull_request_review`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Revisiones de solicitudes de extracción](/rest/reference/pulls#reviews)". + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ----------------------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | +| [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review) | - `submitted`
    - `edited`
    - `dismissed` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una revisión de solicitud de extracción ha sido `edited` (editada) o `dismissed` (descartada). + +```yaml +on: + pull_request_review: + types: [edited, dismissed] +``` + +{% data reusables.developer-site.pull_request_forked_repos_link %} + +#### `comentarios _revisiones_solicitudes de extracción` + +Ejecuta tu flujo de trabajo en cualquier momento en que se modifique una diferencia unificada de solicitud de extracción, que activa el evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección [Revisar comentarios](/rest/reference/pulls#comments). + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ----------------------------------------------------- | ------------------------------------------------ | +| [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`
    - `edited`
    - `deleted` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando un comentario de revisión de solicitud de extracción ha sido `created` o `deleted`. + +```yaml +on: + pull_request_review_comment: + types: [created, deleted] +``` + +{% data reusables.developer-site.pull_request_forked_repos_link %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +#### `pull_request_target` + +Este evento se ejecuta en el contexto de la base de la solicitud de cambios en vez de en la confirmación fusionada como lo hace el evento `pull_request`. Esto previene que se ejecute el código inseguro del flujo de trabajo desde el encabezado de la solicitud de cambios, el cual pudiera alterar a tu repositorio, o borrar cualquier secreto que utilices en tu flujo de trabajo. Este evento te permite hacer cosas como crear flujos de trabajo que etiquetan y comentan las solicitudes de cambios, con base en el contenido de la carga útil del evento. + +{% warning %} + +**Advertencia:** Se otorga un token de repositorio con permisos de lectura/escritura al evento `pull_request_target` y éste puede acceder a los secretos, aún cuando se activa desde una bifurcación. Aunque las ejecuciones de flujo de trabajo se ejecutan en el contexto de la base de la solicitud de cambios, debes asegurarte de que no revisas, compilas o ejecutas código no confiable desde ella con este evento. Adicionalmente, cualquier caché comparte el mismo alcance que la rama base y, para ayudar a prevenir que se vicie el caché, no deberías guardarlo si existe una posibilidad de que su contenido se haya alterado. + +{% endwarning %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------- | +| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed` | Última confirmación en la rama base de la solicitud de extracción | Rama base de la solicitud de extracción | + +Predeterminadamente, un flujo de trabajo se ejecuta únicamente cuando el tipo de actividad de un `pull_request_target` se encuentra como `opened`, `synchronize`, o `reopened`. Para activar los flujos de trabajo para más tipos de actividad, usa la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. + +```yaml +on: + pull_request_target: + types: [assigned, opened, synchronize, reopened] +``` + +{% endif %} + +#### `push` + +{% note %} + +**Nota:** La carga disponible del webhook para las acciones de GitHub no incluye los atributos `added`, `removed` y `modified` en el objeto `commit`. Puedes recuperar el objeto de confirmación completo usando la API REST. Para obtener más información, consulta la sección "[Obtener una sola confirmación](/rest/reference/repos#get-a-single-commit)". + +{% endnote %} + +Ejecuta tu flujo de trabajo cuando alguien sube a una rama de repositorio, lo que activa el evento `push`. + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------- | --------------- | +| [`push`](/webhooks/event-payloads/#push) | n/a | Confirmación subida, a menos que se elimine una rama (cuando se trata de la rama por defecto) | Ref actualizado | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `push`. + +```yaml +on: + push +``` + +#### `registry_package` + +Ejecuta tu flujo de trabajo en cualquier momento en que un paquete es `publish` (publicado) o `updated` (actualizado). Para obtener más información, consulta "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)." + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------------------- | ----------------------------------- | ---------------------------------- | ------------------------------------- | +| [`registry_package`](/webhooks/event-payloads/#package) | - `published`
    - `updated` | Confirmación del paquete publicado | Rama o etiqueta del paquete publicado | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando un paquete ha sido `publicado`. + +```yaml +on: + registry_package: + types: [published] +``` + +#### `release` + +{% note %} + +**Nota:** El evento `release` no se activará para los lanzamientos en borrador. + +{% endnote %} + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `release`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Lanzamientos](/rest/reference/repos#releases)". + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- | +| [`release`](/webhooks/event-payloads/#release) | - `published`
    - `unpublished`
    - `created`
    - `edited`
    - `deleted`
    - `prereleased`
    - `released` | Última confirmación en el lanzamiento etiquetado | Etiqueta de lanzamiento | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando un lanzamiento ha sido `publish`. + +```yaml +on: + release: + types: [published] +``` + +#### `status` + +Ejecuta tu flujo de trabajo en cualquier momento en que cambia el estado de una confirmación de Git, lo que activa el evento `status`. Para obtener más información acerca de la API de REST, consulta la sección "[Estados](/rest/reference/repos#statuses)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------- | ------------------ | --------------------------------------------- | ------------ | +| [`status`](/webhooks/event-payloads/#status) | n/a | Última confirmación en la rama predeterminada | n/a | + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `status`. + +```yaml +on: + status +``` + +#### `watch` + +Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `watch`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Marcar con una estrella](/rest/reference/activity#starring)". + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------ | ------------------ | --------------------------------------------- | ---------------- | +| [`watch`](/webhooks/event-payloads/#watch) | - `started` | Última confirmación en la rama predeterminada | Rama por defecto | + +{% data reusables.developer-site.limit_workflow_to_activity_types %} + +Por ejemplo, puedes ejecutar un flujo de trabajo cuando alguien coloca una estrella en un repositorio, que es el tipo de actividad `started` que activa el evento Ver. + +```yaml +on: + watch: + types: [started] +``` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +#### `workflow_run` + +{% data reusables.webhooks.workflow_run_desc %} + +{% data reusables.github-actions.branch-requirement %} + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | +| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | Última confirmación en la rama predeterminada | Rama por defecto | + +Si necesitas filtrar las ramas de este evento, puedes utilizar `branches` o `branches-ignore`. + +En este ejemplo, se configuró la ejecución de un flujo de trabajo después de que se completen las "Pruebas de ejecución" por separado para el mismo. + +```yaml +on: + workflow_run: + workflows: ["Run Tests"] + branches: [main] + types: + - completed + - requested +``` + +{% endif %} + +### Activar nuevos flujos de trabajo mediante un token de acceso personal + +{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". + +Si deseas activar un flujo de trabajo desde una ejecución de flujo de trabajo, puedes desencadenar el evento mediante un token de acceso personal. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. Para obtener más información sobre almacenr un token de acceso personal como secreto, consulta la sección "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". diff --git a/translations/es-ES/content/actions/reference/index.md b/translations/es-ES/content/actions/reference/index.md new file mode 100644 index 0000000000000..f3518d5bbda79 --- /dev/null +++ b/translations/es-ES/content/actions/reference/index.md @@ -0,0 +1,57 @@ +--- +title: Referencia +intro: 'Documentación de referencia para crear flujos de trabajo utilizando autenticación y ejecutores hospedados en Github.' +redirect_from: + - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Sintaxis de flujos de trabajo + +El archivo de flujo de trabajo se escribe en YAML. En el archivo de flujo de trabajo de YAML, puedes utilizar la sintaxis de expresión para evaluar la información contextual, literales, operadores y funciones. La información contextual incluye flujos de trabajo, variables de ambiente, secretos y los eventos que activaron el flujo de trabajo. Cuando utilizas [`run`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun) en un paso del flujo de trabajo para ejecutar comandos de shell, puedes utilizar una sintaxis específica de comandos de flujo de trabajo para configurar variables de ambiente, configurar parámetros para los pasos subsecuentes y configurar mensajes de error o de depuración. + +{% link_in_list /workflow-syntax-for-github-actions %} +{% link_in_list/context-and-expression-syntax-for-github-actions%} +{% link_in_list /workflow-commands-for-github-actions %} + +### Eventos + +Puedes configurar flujos de trabajo para que se ejecuten cuando ocurren eventos específicos de GitHub, en un tiempo programado, manualmente, o cuando los eventos ocurren fuera de GitHub. + +{% link_in_list /events-that-trigger-workflows %} + +### Autenticación y secretos + +{% data variables.product.prodname_dotcom %} proporciona un token que puedes usar para autenticar en nombre de {% data variables.product.prodname_actions %}. También puedes almacenar información sensible como un secreto en tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio o ambiente{% else %} o repositorio{% endif %}. {% data variables.product.prodname_dotcom %} cifra todos los secretos. + +{% link_in_list /authentication-in-a-workflow %} +{% link_in_list /encrypted-secrets %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Ambientes + +Los jobs de un flujo de trabajo pueden referenciar ambientes que tienen reglas de protección o secretos de ambiente específico. + +{% link_in_list /environments %} +{% endif %} + +### Ejecutores alojados {% data variables.product.prodname_dotcom %} + +GitHub ofrece máquinas virtuales hospedadas para ejecutar flujos de trabajo. La máquina virtual contiene un ambiente con herramientas, paquetes y variables de ambiente para que las utilicen las GitHub Actions. + +{% link_in_list /environment-variables %} +{% link_in_list /specifications-for-github-hosted-runners %} + +{% if currentVersion == "free-pro-team@latest" %} +### Administración + +Cuando ejecutas flujos de trabajo en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, hay límites de uso y cargos de uso potenciales. También puedes inhabilitar o restringir el uso de las {% data variables.product.prodname_actions %} en un repositorio y en una organización. + +{% link_in_list /usage-limits-billing-and-administration %} + +{% endif %} diff --git a/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md new file mode 100644 index 0000000000000..cc043d46a4acd --- /dev/null +++ b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md @@ -0,0 +1,119 @@ +--- +title: Especificaciones para los ejecutores hospedados en GitHub +intro: '{% data variables.product.prodname_dotcom %} ofrece máquinas virtuales alojadas para ejecutar flujos de trabajo. La máquina virtual contiene un entorno de herramientas, paquetes y configuraciones disponibles para que {% data variables.product.prodname_actions %} los utilice.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/virtual-environments-for-github-actions + - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions + - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners + - /actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners + - /actions/reference/virtual-environments-for-github-hosted-runners + - /actions/reference/software-installed-on-github-hosted-runners +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de ejecutores alojados en {% data variables.product.prodname_dotcom %} + +Un ejecutor alojado en {% data variables.product.prodname_dotcom %} es una máquina virtual alojada por {% data variables.product.prodname_dotcom %} con la aplicación del ejecutor {% data variables.product.prodname_actions %} instalada. {% data variables.product.prodname_dotcom %} ofrece ejecutores con sistemas operativos Linux, Windows y macOS. + +Cuando usas un ejecutor alojado en {% data variables.product.prodname_dotcom %}, se contemplan el mantenimiento de la máquina y las actualizaciones. Puedes ejecutar flujos de trabajo directamente en la máquina virtual o en un contenedor Docker. + +Puedes especificar el tipo de ejecutor para cada puesto en un flujo de trabajo. Cada puesto en un flujo de trabajo se ejecuta en una instancia nueva de la máquina virtual. Todos los pasos del trabajo se ejecutan en la misma instancia de la máquina virtual, lo que permite que las acciones de ese trabajo compartan información usando el sistema de archivos. + +{% data reusables.github-actions.runner-app-open-source %} + +#### Hosts en la nube para ejecutores alojados en {% data variables.product.prodname_dotcom %} + +{% data variables.product.prodname_dotcom %} aloja ejecutores de Linux y Windows en máquinas virtuales Standard_DS2_v2 en Microsoft Azure con la aplicación del ejecutor de {% data variables.product.prodname_actions %} instalada. La aplicación del ejecutor alojada en {% data variables.product.prodname_dotcom %} es una bifurcación del agente de Azure Pipelines. Los paquetes ICMP entrantes están bloqueados para todas las máquinas virtuales de Azure, por lo tanto, es posible que los comandos ping o traceroute no funcionen. Para obtener más información acerca de los recursos de la máquina Standard_DS2_v2, consulta "[Dv2 y DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)"en la documentación de Microsoft Azure. + +{% data variables.product.prodname_dotcom %} hospeda ejecutores de macOS en la nube de macOS propia de {% data variables.product.prodname_dotcom %}. + +#### Privilegios administrativos de los ejecutores alojados en {% data variables.product.prodname_dotcom %} + +Las máquinas virtuales Linux y macPS se ejecutan sin la contraseña `sudo`. Cuando necesitas ejecutar comandos o instalar herramientas que requieren más privilegios que el usuario actual, puedes usar `sudo` sin la necesidad de brindar una contraseña. Para obtener más información, consulta "[Manual de sudo](https://www.sudo.ws/man/1.8.27/sudo.man.html)." + +Las máquinas virtuales de Windows están configuradas para ejecutarse como administradores con el control de cuentas de usuario (UAC) inhabilitado. Para obtener más información, consulta "[Cómo funciona el control de cuentas de usuario](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" en la documentación de Windows. + +### Ejecutores y recursos de hardware compatibles + +Cada máquina virtual tiene los mismos recursos de hardware disponibles. + +- CPU de 2 núcleos +- 7 GB de memoria RAM +- 14 GB de espacio en el disco SSD + +{% data reusables.github-actions.supported-github-runners %} + +{% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} + +Las bitácoras de flujos de trabajo listan los ejecutores que se usan para ejecutar un job. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". + +### Software compatible + +Las herramientas de software que se incluyen en los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se actualizan semanalmente. Para obtener la lista más reciente de herramientas incluidas para cada sistema operativo de ejecutor, consulta los enlaces que figuran a continuación: + +* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md) +* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) +* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) +* [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) + +{% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} + +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} incluyen las herramientas integradas predeterminadas del sistema operativo, además de los paquetes enumerados en las referencias anteriores. Por ejemplo, los ejecutores de Ubuntu y macOS incluyen `grep`, `find` y `which`, entre otras herramientas predeterminadas. + +Las bitácoras de flujo de trabajo incluyen un enlace a las herramientas preinstaladas en el ejecutor. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". + +Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). + +### Direcciones IP + +{% note %} + +**Nota:** Si usas una lista de direcciones IP permitidas para tu cuenta de organización o de empresa {% data variables.product.prodname_dotcom %}, no puedes usar ejecutores alojados en {% data variables.product.prodname_dotcom %} y, en su lugar, debes usar ejecutores autoalojados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." + +{% endnote %} + +Los ejecutores de Windows y de Ubuntu se hospedan en Azure y, subsecuentemente, tienen los mismos rangos de direcciones IP que los centros de datos de Azure. Los ejecutores de macOS se hospedan en la nube de macOS propia de {% data variables.product.prodname_dotcom %}. + +Para obtener una lista de los rangos de direcciones IP que utiliza {% data variables.product.prodname_actions %} para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la clave `actions` en la respuesta de la terminal de [Obtener información meta de GitHub](/rest/reference/meta#get-github-meta-information)". Puedes utilizar esta lista de direcciones IP si requieres prevenir acceso no autorizados a tus recursos internos mediante una lista de direcciones IP permitidas. + +La lista de direcciones IP permitidas de {% data variables.product.prodname_actions %} que devuelve la API se actualiza una vez por semana. + +### Sistemas de archivos + +{% data variables.product.prodname_dotcom %} ejecuta acciones y comandos de shell en directorios específicos en la máquina virtual. Las rutas de archivo en las máquinas virtuales no son estáticas. Usa las variables de entorno que proporciona {% data variables.product.prodname_dotcom %} para construir rutas de archivo para los directorios `home`, `workspace` y `workflow`. + +| Directorio | Variable de entorno | Descripción | +| --------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `hogar` | `HOME` | Contiene datos relacionados con el usuario. Por ejemplo, este directorio podría contener las credenciales de un intento de inicio de sesión. | +| `workspace` | `GITHUB_WORKSPACE` | Las acciones y los comandos del shell se ejecutan en este directorio. Una acción puede modificar los contenidos de este directorio, al que pueden tener acceso acciones posteriores. | +| `workflow/event.json` | `GITHUB_EVENT_PATH` | La carga `POST` del evento de webhook que activó el flujo de trabajo. {% data variables.product.prodname_dotcom %} reescribe esto cada vez que se ejecuta una acción para aislar el contenido del archivo entre acciones. | + +Para obtener una lista de las variables de entorno que crea {% data variables.product.prodname_dotcom %} para cada flujo de trabajo, consulta "[Usar variables de entorno](/github/automating-your-workflow-with-github-actions/using-environment-variables)". + +#### Sistema de archivos del contenedor de Docker + +Las acciones que se ejecutan en contenedores Docker tienen directorios estáticos en la ruta `/github`. Sin embargo, te recomendamos encarecidamente que uses las variables de entorno predeterminadas para construir rutas de archivos en contenedores de Docker. + +{% data variables.product.prodname_dotcom %} se reserva el prefijo de ruta `/github` y crea tres directorios para las acciones. + +- `/github/home` +- `/github/workspace` - {% data reusables.repositories.action-root-user-required %} +- `/github/workflow` + +{% if currentVersion == "free-pro-team@latest" %} + +### Leer más +- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" + +{% endif %} diff --git a/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md new file mode 100644 index 0000000000000..bd59ab6f52ae4 --- /dev/null +++ b/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md @@ -0,0 +1,90 @@ +--- +title: 'Límites de uso, facturación y administración' +intro: 'Hay límites de uso para los flujos de trabajo de {% data variables.product.prodname_actions %}. Los cargos de uso aplican a los repositorios que salen de la cantidad de minutos y almacenamiento gratuitos de un repositorio.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de la facturación para {% data variables.product.prodname_actions %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". +{% else %} +El uso de GitHub Actions es gratuito para +{% data variables.product.prodname_ghe_server %} que utilicen ejecutores auto-hospedados. +{% endif %} + +### Límites de uso + +{% if currentVersion == "free-pro-team@latest" %} +Hay algunos límites para +el uso de {% data variables.product.prodname_actions %} cuando se utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Estos límites están sujetos a cambios. + +{% note %} + +**Nota:** Para los ejecutores auto-hospedados, pueden aplicarse límites de uso distintos. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)." + +{% endnote %} + +- **Tiempo de ejecución de jobs** - Cada job en un flujo de trabajo puede ejecutarse hasta por 6 horas en tiempo de ejecución. Si un job llega a este límite, éste se terminará y fallará en completarse. +{% data reusables.github-actions.usage-workflow-run-time %} +{% data reusables.github-actions.usage-api-requests %} +- **Jobs simultáneos** - La cantidad de jobs que puedes ejecutar simultáneamente en tu cuenta depende de tu plan de GitHub, como se indica en la siguiente tabla. Si eso se excede, cualquier job adicional se pondrá en cola de espera. + + | Plan de GitHub | Jobs simultáneos totales | Jobs simultáneos de macOS máximos | + | -------------- | ------------------------ | --------------------------------- | + | Free | 20 | 5 | + | Pro | 40 | 5 | + | Team | 60 | 5 | + | Empresa | 180 | 50 | +- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %} +{% else %} +Los límites de uso aplican a los ejecutores auto-hospedados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Política de uso +Adicionalmente a los límites de uso, debes garantizar que utilizas + +{% data variables.product.prodname_actions %} de acuerdo con las [Condiciones de servicio de Github](/articles/github-terms-of-service/). Para obtener más información sobre los términos específicos de las {% data variables.product.prodname_actions %}, consulta los [Términos adicionales de producto de GitHub](/github/site-policy/github-additional-product-terms#a-actions-usage). +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Polìtica de retenciòn de artefactos y bitàcoras + +Puedes configurar el periodo de retenciòn de artefactos y bitàcoras para tu repositorio, organizaciòn o cuenta empresarial. + +{% data reusables.actions.about-artifact-log-retention %} + +Para obtener más información, consulta: + +- [Configurar el periodo de retenciòn de las {% data variables.product.prodname_actions %} para los artefactos y bitàcoras en tu repositorio](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) +- [Configurar el periodo de retenciòn de las {% data variables.product.prodname_actions %} para los artefactos y bitàcoras en tu organizaciòn](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Configurar el periodo de retenciòn de las {% data variables.product.prodname_actions %} para los artefactos y bitàcoras en tu empresa](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) +{% endif %} + +### Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu repositorio u organización + +{% data reusables.github-actions.disabling-github-actions %} + +Para obtener más información, consulta: +- "[Inhabilitar o limitar {% data variables.product.prodname_actions %} para un repositorio](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" +- "[Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[Requerir políticas de {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" para {% data variables.product.prodname_ghe_cloud %}{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Inhabilitar y habilitar flujos de trabajo + +Puedes habilitar e inhabilitar flujos de trabajo independientes en tu repositorio en {% data variables.product.prodname_dotcom %}. + +{% data reusables.actions.scheduled-workflows-disabled %} + +Para obtener más información, consulta la sección "[Inhabilitar y habilitar un flujo de trabajo](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)". +{% endif %} diff --git a/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md new file mode 100644 index 0000000000000..5bcecfdcae62c --- /dev/null +++ b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md @@ -0,0 +1,317 @@ +--- +title: Comandos de flujo de trabajo para Acciones de GitHub +shortTitle: Comandos de flujo de trabajo +intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/development-tools-for-github-actions + - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions + - /actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions + - /actions/reference/development-tools-for-github-actions + - /actions/reference/logging-commands-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los comandos de flujo + +Las acciones pueden comunicarse con la máquina del ejecutor para establecer variables de entorno, valores de salida utilizados por otras acciones, agregar mensajes de depuración a los registros de salida y otras tareas. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. Para obtener más información, consulta la sección ["Archivos de ambiente".](#environment-files) +{% else %} +Los comandos de flujo de trabajo usan el comando `echo` en un formato específico. +{% endif %} + +``` bash +echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value}" +``` + +{% note %} + +**Nota:** los nombres de comandos y parámetros de flujo de trabajo no distinguen mayúsculas de minúsculas. + +{% endnote %} + +{% warning %} + +**Advertencia:** si estás usando el símbolo del sistema, omite los caracteres de comillas dobles (`"`) cuando uses comandos de flujo de trabajo. + +{% endwarning %} + +### Utilizar comandos de flujo de trabajo para acceder a las funciones de toolkit + +El [actions/toolkit](https://github.com/actions/toolkit) incluye varias funciones que se pueden ejecutar como comandos de flujo de trabajo. Utiliza la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro de tu archivo YAML; estos comandos se envían entonces a través de `stdout`. Por ejemplo, en vez de utilizar código para configurar una salida, como se muestra aquí: + +```javascript +core.setOutput('SELECTED_COLOR', 'green'); +``` + +Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar el mismo valor: + +{% raw %} +``` yaml + - name: Set selected color + run: echo '::set-output name=SELECTED_COLOR::green' + id: random-color-generator + - name: Get color + run: echo "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}" +``` +{% endraw %} + +La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo: + +| Funcion del Toolkit | Comando equivalente del flujo de trabajo | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | +| `core.addPath` | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Accesible utilizando el archivo de ambiente `GITHUB_PATH`{% else %} `add-path` {% endif %} | | +| | | +| `core.debug` | `debug` | +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Accesible utilizando el archivo de ambiente`GITHUB_ENV`{% else %} `set-env` {% endif %} | | +| | | +| `core.getInput` | Accesible utilizando la variable de ambiente `INPUT_{NAME}` | +| `core.getState` | Accesible utilizando la variable de ambiente`STATE_{NAME}` | +| `core.isDebug` | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` | +| `core.saveState` | `save-state` | +| `core.setFailed` | Utilizada como un atajo para `::error` y `exit 1` | +| `core.setOutput` | `set-output` | +| `core.setSecret` | `add-mask` | +| `core.startGroup` | `group` | +| `core.warning` | `warning file` | + +{% if currentVersion ver_lt "enterprise-server@2.23" %} +### Configurar una variable de ambiente + +`::set-env name={name}::{value}` + +Crea o actualiza una variable de entorno para todas las acciones que se ejecutan a continuación en un puesto. La acción que crea o actualiza la variable de entorno no tiene acceso al nuevo valor, pero todas las acciones subsiguientes en un puesto tendrán acceso. Las variables de entorno distinguen mayúsculas de minúsculas y puedes incluir puntuación. + +#### Ejemplo + +``` bash +echo "::set-env name=action_state::yellow" +``` +{% endif %} + +### Configurar un parámetro de salida + +`::set-output name={name}::{value}` + +Establece un parámetro de salida de la acción. + +Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". + +#### Ejemplo + +``` bash +echo "::set-output name=action_fruit::strawberry" +``` + +{% if currentVersion ver_lt "enterprise-server@2.23" %} +### Agregar una ruta de sistema + +`::add-path::{path}` + +Anexa un directorio a la variable de `RUTA` del sistema para todas las acciones subsiguientes en el puesto actual. La acción que se ejecuta actualmente no puede acceder a la nueva variable de ruta. + +#### Ejemplo + +``` bash +echo "::add-path::/path/to/dir" +``` +{% endif %} + +### Agregar un mensaje de depuración + +`::debug::{message}` + +Imprime un mensaje de depuración para el registro. Debes crear un archivo `ACTIONS_STEP_DEBUG` designado secretamente con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)." + +#### Ejemplo + +``` bash +echo "::debug::Set the Octocat variable" +``` + +### Configurar un mensaje de advertencia + +`::warning file={name},line={line},col={col}::{message}` + +Crea un mensaje de advertencia e imprime el mensaje en el registro. Opcionalmente, puedes brindar un nombre de archivo (`file`), número de línea (`line`), y columna (`col`) donde se produjo la advertencia. + +#### Ejemplo + +``` bash +echo "::warning file=app.js,line=1,col=5::Missing semicolon" +``` + +### Configurar un mensaje de error + +`::error file={name},line={line},col={col}::{message}` + +Crea un mensaje de error e imprime el mensaje en el registro. Opcionalmente, puedes proporcionar un nombre de archivo (`file`), nùmero de lìnea (`line`), y nùmero de columna (`col`) de donde se suscitò el error. + +#### Ejemplo + +``` bash +echo "::error file=app.js,line=10,col=15::Something went wrong" +``` + +### Agrupar líneas de las bitácoras + +``` +::group::{title} +::endgroup:: +``` + +Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma. + +#### Ejemplo + +```bash +echo "::group::My title" +echo "Inside group" +echo "::endgroup::" +``` + +![Grupo plegable en la bitácora de una ejecución de flujo de trabajo](/assets/images/actions-log-group.png) + +### Enmascarar un valor en el registro + +`::add-mask::{value}` + +El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. + +#### Ejemplo de enmascaramiento de una cadena + +Cuando imprimas `"Mona The Octocat"` en el registro, verás `"***"`. + +```bash +echo "::add-mask::Mona The Octocat" +``` + +#### Ejemplo de enmascaramiento de una variable de entorno + +Cuando imprimes la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verás `"***"` en lugar de `"Mona The Octocat"`. + +```bash +MY_NAME="Mona The Octocat" +echo "::add-mask::$MY_NAME" +``` + +### Detener e iniciar comandos de flujo de trabajo + +`::stop-commands::{endtoken}` + +Deja de procesar cualquier comando de flujo de trabajo. Este comando especial te permite registrar lo que sea sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios. + +#### Ejemplo deteniendo comandos de flujo de trabajo + +``` bash +echo "::stop-commands::pause-logging" +``` + +Para iniciar los comandos de flujo de trabajo, pasa el token que usaste para detenerlos. + +`::{endtoken}::` + +#### Ejemplo de inicio de comandos de flujo + +``` bash +echo "::pause-logging::" +``` + +### Enviar valores a las acciones pre y post + +Puedes utilizar el comando `save-state` para crear variables de ambiente para compartir con tus acciones `pre:` o `post:` de flujo de trabajo. Por ejemplo, puedes crear un archivo con la acción `pre:`, pasar la ubicación del archivo a la acción `main:`, y después, utilizar la acción `post:` para borrar el archivo. Como alternativa, puedes crear un archivo con la acción `main:`, pasar la ubicación del archivo a la acción `post:`, y también utilizar la acción `post:` para borrar el archivo. + +Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor que se guardó en la acción donde se utilizó `save-state`. Para obtener más información sobre la acción `post:`, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)". + +El comando `save-state` solo puede ejecutarse dentro de una acción y no está disponible para archivos YAML. El valor guardado se almacena en un valor de ambiente con el prefijo `STATE_`. + +Este ejemplo utiliza JavaScript para ejecutar el comando `save-state`. La variable de ambiente resultante se nombra `STATE_processID` con el valor de `12345`: + +``` javascript +console.log('::save-state name=processID::12345') +``` + +La variable `STATE_processID` se encontrará entonces exclusivamente disponible para el script de limpieza que se ejecuta bajo la acción `main`. Este ejemplo se ejecuta en `main` y utiliza JavaScript para mostrar el valor asignado a la variable de ambiente `STATE_processID`: + +``` javascript +console.log("The running PID from the main action is: " + process.env.STATE_processID); +``` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +## Archivos de ambiente + +Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos temporales que pueden utilizarse para llevar a cabo ciertas acciones. La ruta a estos archivos se expone a través de variables de ambiente. Necesitarás utilizar codificación UTF-8 cuando escribas en estos archivos para garantizar el procesamiento adecuado de los comandos. Se pueden escribir varios comandos en el mismo archivo, separados por líneas nuevas. + +{% warning %} + +**Advertencia:** Powershell no utiliza UTF-8 predeterminadamente. Asegúrate que escribes los archivos utilizando la codificación correcta. Por ejemplo, necesitas configurar la codificación UTF-8 cuando configuras la ruta: + +``` +steps: + - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append +``` + +{% endwarning %} + +### Configurar una variable de ambiente + +`echo "{name}={value}" >> $GITHUB_ENV` + +Crea o actualiza una variable de entorno para todas las acciones que se ejecutan a continuación en un puesto. La acción que crea o actualiza la variable de entorno no tiene acceso al nuevo valor, pero todas las acciones subsiguientes en un puesto tendrán acceso. Las variables de entorno distinguen mayúsculas de minúsculas y puedes incluir puntuación. + +#### Ejemplo + +```bash +echo "action_state=yellow" >> $GITHUB_ENV +``` + +Cuando ejecutes `$action_state` en un paso subsecuente ahora se devolverá `yellow` + +#### Secuencias de línea múltiple + +Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la siguiente sintaxis. + +``` +{name}<<{delimiter} +{value} +{delimiter} +``` + +##### Ejemplo + +En este ejemplo, utilizamos `EOF` como delimitador y configuramos la variable de ambiente `JSON_RESPONSE` para el valor de la respuesta de curl. +``` +steps: + - name: Set the value + id: step_one + run: | + echo 'JSON_RESPONSE<> $GITHUB_ENV + curl https://httpbin.org/json >> $GITHUB_ENV + echo 'EOF' >> $GITHUB_ENV +``` + +### Agregar una ruta de sistema + +`echo "{path}" >> $GITHUB_PATH` + +Antepone un directorio a la variable `PATH` del sistema y la hace disponible para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción. + +#### Ejemplo + +Este ejemplo demuestra cómo agregar el directorio `$HOME/.local/bin` del usuario al `PATH`: + +``` bash +echo "$HOME/.local/bin" >> $GITHUB_PATH +``` +{% endif %} diff --git a/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md new file mode 100644 index 0000000000000..552de34ad4a4b --- /dev/null +++ b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md @@ -0,0 +1,1211 @@ +--- +title: Sintaxis de flujo de trabajo para acciones de GitHub +shortTitle: Sintaxis de flujos de trabajo +intro: Un flujo de trabajo es un proceso automatizado configurable formado por uno o más trabajos. Debes crear un archivo YAML para definir tu configuración de flujo de trabajo. +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /articles/workflow-syntax-for-github-actions + - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions + - /actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de la sintaxis de YAML para flujos de trabajo + +Los archivos de flujo de trabajo usan la sintaxis YAML y deben tener una extensión de archivo `.yml` o `.yaml`. Si eres nuevo en YAML y deseas conocer más, consulta "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". + +Debes almacenar los archivos de flujos de trabajo en el directorio `.github/workflows` en tu repositorio. + +### `name (nombre)` + +El nombre de tu flujo de trabajo. {% data variables.product.prodname_dotcom %} muestra los nombres de tus flujos de trabajo en la página de acciones de tu repositorio. Si omites `nombre`, {% data variables.product.prodname_dotcom %} lo establece en la ruta del archivo de flujo de trabajo en relación con la raíz del repositorio. + +### `on` + +**Obligatorio** El nombre del evento {% data variables.product.prodname_dotcom %} que activa el flujo de trabajo. Puedes proporcionar una única `cadena` de eventos, `matriz` de eventos, `matriz` de `tipos` de eventos o `mapa` de configuración de eventos que programe un flujo de trabajo o restrinja la ejecución de un flujo de trabajo para archivos, etiquetas o cambios de rama específicos. Para obtener una lista de eventos disponibles, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows)". + +{% data reusables.github-actions.actions-on-examples %} + +### `on..types` + +Selecciona los tipos de actividad que desencadenarán una ejecución de flujo de trabajo. La mayoría de los eventos GitHub son desencadenados por más de un tipo de actividad. Por ejemplo, el evento para el recurso release (lanzamiento) se activa cuando se `publica`, `se cancela la publicación`, `se crea`, `edita`, `elimina` o `lanza previamente` una publicación. La palabra clave `types` (tipos) te permite reducir la actividad que hace que se ejecute el flujo de trabajo. Cuando solo un tipo de actividad activa el evento webhook, la palabra clave `types` (tipos) es innecesaria. + +Puedes usar una matriz de `tipos` de eventos. Para obtener más información acerca de cada evento y sus tipos de actividad, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows#webhook-events)". + +```yaml +# Activa el flujo de trabajo en la actividad de la solicitud de extracción +on: + release: + # Solo usa la palabra clave de tipos para reducir los tipos de actividad que activarán tus flujos de trabajo. + types: [published, created, edited] +``` + +### `on..` + +Cuando uses los eventos `push` y `pull_request` debes configurar un flujo de trabajo para ejecutarlo en ramas o etiquetas específicas. Para un evento `pull_request`, solo se evalúan las ramas y las etiquetas en la base. Si defines solo `etiquetas` o solo `ramas`, el flujo de trabajo no se ejecutará para los eventos que afecten a la ref de Git indefinida. + +Las palabras clave `branches`, `branches-ignore`, `tags` y `tags-ignore` aceptan patrones globales que usan los caracteres comodines `*` y `**` para encontrar más de un nombre de rama o etiqueta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](#filter-pattern-cheat-sheet)". + +#### Ejemplo que incluye ramas y etiquetas + +Los patrones definidos en `branches` y `tags` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**` encontrará la ref de Git `refs/heads/releases/10`. + +```yaml +on: + push: + # Sequence of patterns matched against refs/heads + branches: + # Push events on main branch + - main + # Push events to branches matching refs/heads/mona/octocat + - 'mona/octocat' + # Push events to branches matching refs/heads/releases/10 + - 'releases/**' + # Sequence of patterns matched against refs/tags + tags: + - v1 # Push events to v1 tag + - v1.* # Push events to v1.0, v1.1, and v1.9 tags +``` + +#### Ejemplo de ignorar ramas y etiquetas + +Cada vez que un patrón coincida con el patrón `branches-ignore` o `tags-ignore`, no se ejecutará el flujo de trabajo. Los patrones definidos en `branches-ignore` y `tags-ignore` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**-alpha` en `branches` encontrará la ref de Git `refs/releases/beta/3-alpha`. + +```yaml +on: + push: + # Sequence of patterns matched against refs/heads + branches-ignore: + # Push events to branches matching refs/heads/mona/octocat + - 'mona/octocat' + # Push events to branches matching refs/heads/releases/beta/3-alpha + - 'releases/**-alpha' + # Sequence of patterns matched against refs/tags + tags-ignore: + - v1.* # Push events to tags v1.0, v1.1, and v1.9 +``` + +#### Excluir ramas y etiquetas + +Puedes usar dos tipos de filtros para evitar que un flujo de trabajo se ejecute en las subidas y las solicitudes de extracción a las etiquetas y las ramas. +- `branches` o `branches-ignore`: no puedes usar ambos filtros `branches` y `branches-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `branches` cuando debas filtrar ramas de coincidencias positivas y para excluir ramas. Usa el filtro `branches-ignore` cuando solo debas excluir nombres de ramas. +- `tags` o `tags-ignore`: no puedes usar ambos filtros `tags` y `tags-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `tags` cuando debas filtrar etiquetas de coincidencias positivas y para excluir etiquetas. Usa el filtro `tags-ignore` cuando solo debas excluir nombres de etiquetas. + +#### Ejemplo de uso de patrones positivos y negativos + +Puedes excluir `etiquetas` y `ramas` usando el caracter `!`. El orden en que defines los patrones importa. + - Un patrón negativo de coincidencia (con prefijo `!`) luego de una coincidencia positiva excluirá la ref de Git. + - Un patrón positivo de coincidencia luego de una coincidencia negativa volverá a incluir la ref de Git. + +El siguiente flujo de trabajo se ejecutará en las subidas a `releases/10` o `releases/beta/mona`, pero no en `releases/10-alpha` o `releases/beta/3-alpha` porque el patrón negativo `!releases/**-alpha` le sigue al patrón positivo. + +```yaml +on: + push: + branches: + - 'releases/**' + - '!releases/**-alpha' +``` + +### `on..paths` + +Cuando uses los eventos `push` y `pull_request`, puedes configurar que se ejecute un flujo de trabajo cuando al menos un archivo no coincida con `paths-ignore` o al menos uno de los archivos modificados coincida con las `rutas` configuradas. Los filtros de ruta no se evalúan para las subidas a etiquetas. + +Las palabras clave `paths-ignore` y `paths` aceptan los patrones globales que usan los caracteres comodines `*` y `**` para encontrar más de un nombre de ruta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](#filter-pattern-cheat-sheet)". + +#### Ejemplo de ignorar rutas + +Cada vez que un nombre de ruta coincida con `paths-ignore`, no se ejecutará el flujo de trabajo. {% data variables.product.prodname_dotcom %} evalúa los patrones definidos en `paths-ignore` para compararlos con el nombre de ruta. Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio. + +```yaml +on: + push: + paths-ignore: + - 'docs/**' +``` + +#### Ejemplo de incluir rutas + +Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta el flujo de trabajo. Para desencadenar una compilación cada vez que subes un archivo JavaScript, puedes usar un patrón comodín. + +```yaml +on: + push: + paths: + - '**.js' +``` + +#### Excluir rutas + +Puedes excluir rutas usando dos tipos de filtros. No puedes usar ambos filtros para el mismo evento de un flujo de trabajo. +- `paths-ignore`: usa el filtro `paths-ignore` cuando solo debas excluir nombres de ruta. +- `paths`: usa el filtro `paths` cuando debas filtrar rutas de coincidencias positivas y excluir rutas. + +#### Ejemplo de uso de patrones positivos y negativos + +Puedes excluir `rutas` usando el caracter `!`. El orden en que defines los patrones importa: + - Una coincidencia de patrón negativo (con prefijo `!`) luego de una coincidencia positiva excluirá la ruta. + - Un patrón de coincidencia positiva luego de una coincidencia negativa excluirá nuevamente la ruta. + +Este ejemplo se ejecuta cada vez que el evento de `subida` incluye un archivo en el directorio `sub-project` o sus subdirectorios, a menos que el archivo esté en el directorio `sub-project/docs`. Por ejemplo, una subida que haya cambiado `sub-project/index.js` o `sub-project/src/index.js` desencadenará una ejecución de flujo de trabajo, pero una subida que cambie solo `sub-project/docs/readme.md` no lo hará. + +```yaml +on: + push: + paths: + - 'sub-project/**' + - '!sub-project/docs/**' +``` + +#### Comparaciones de diferencias de Git + +{% note %} + +**Nota:** Si subes más de 1.000 confirmaciones, o si {% data variables.product.prodname_dotcom %} no genera la diferencia debido a una interrupción (diferencias que son diferencias demasiado grandes), siempre se ejecutará el flujo de trabajo. + +{% endnote %} + +El filtro determina si un flujo de trabajo se debe ejecutar al evaluar los archivos modificados y al ejecutarlos comparándolos con la lista de `paths-ignore` o `paths`. Si no hay archivos modificados, no se ejecutará el flujo de trabajo. + +{% data variables.product.prodname_dotcom %} genera la lista de archivos modificados usando diferencias de dos puntos para las subidas y de tres puntos para las solicitudes de extracción: +- **Solicitudes de extracción:** las diferencias de tres puntos son una comparación entre la versión más reciente de la rama de tema y la confirmación, cuando la rama de tema se sincronizó por última vez con la rama base. +- **Subidas a ramas existentes:** una diferencia de dos puntos compara las SHA de encabezado y de base directamente entre sí. +- **Subidas a ramas nuevas:** una diferencia de dos puntos comparada con el padre del antepasado de la confirmación más profunda subida. + +Para obtener más información, consulta "[Acerca de comparar ramas en las solicitudes de extracción](/articles/about-comparing-branches-in-pull-requests)". + +### `on.schedule` + +{% data reusables.repositories.actions-scheduled-workflow-example %} + +Para obtener más información acerca de la sintaxis cron, consulta "[Eventos que activan flujos de trabajo](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." + +### `env` + +Un `map` de las variables de ambiente que se encuentran disponibles para los pasos de todos los jobs en el flujo de trabajo. También puedes configurar variables de ambiente que solo estén disponibles para los pasos en un solo job o en un solo paso. Para obtener más información, consulta [`jobs..env`](#jobsjob_idenv) y [`jobs..steps[*].env`](#jobsjob_idstepsenv). + +{% data reusables.repositories.actions-env-var-note %} + +#### Ejemplo + +```yaml +env: + SERVER: production +``` + +### `defaults` + +Un `map` de configuración predeterminada que se aplicará a todos los jobs en el flujo de trabajo. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs..defaults`](#jobsjob_iddefaults). + +{% data reusables.github-actions.defaults-override %} + +### `defaults.run` + +Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un flujo de trabajo. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs..defaults.run`](#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. + +{% data reusables.github-actions.defaults-override %} + +#### Ejemplo + +```yaml +defaults: + run: + shell: bash + working-directory: scripts +``` + +### `Trabajos` + +Una ejecución de flujo de trabajo está compuesta por uno o más trabajos. De forma predeterminada, los trabajos se ejecutan en paralelo. Para ejecutar trabajos de manera secuencial, puedes definir dependencias en otros trabajos utilizando la palabra clave `jobs..needs`. + +Cada job se ejecuta en un ambiente ejecutor que especifica `runs-on`. + +Puedes ejecutar una cantidad ilimitada de trabajos siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados. + +Si necesitas encontrar el identificador único de un trabajo que se ejecuta en una ejecución de flujo de trabajo, puedes usar el API {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Jobs de los Flujos de Trabajo](/rest/reference/actions#workflow-jobs)". + +### `jobs.` + +Cada trabajo debe tener una identificación para asociarse con el trabajo. La clave `job_id` es una cadena y su valor es un mapa de los datos de configuración del trabajo. Debes reemplazar `` con una cadena que sea exclusiva del objeto `jobs`. El `` debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. + +#### Ejemplo + +```yaml +jobs: + my_first_job: + name: My first job + my_second_job: + name: My second job +``` + +### `jobs..name` + +El nombre del trabajo que se muestra en {% data variables.product.prodname_dotcom %}. + +### `jobs..needs` + +Identifica los trabajos que se deben completar con éxito antes de que se ejecute este trabajo. Puede ser una cadena o matriz de cadenas. Si un job falla, se saltarán todos los jobs que lo necesiten a menos de que éstos utilicen una expresión condicional que ocasione que el job continúe. + +#### Ejemplo que requiere que los jobs dependientes sean exitosos + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +``` + +En este ejemplo, `job1` debe completarse con éxito antes de que `job2` comience, y `job3` espera a que`job1` y `job2` se completen. + +En este ejemplo, los trabajos se ejecutan de manera secuencial: + +1. `job1` +2. `job2` +3. `job3` + +#### Ejemplo que no requiere que los jobs dependientes sean exitosos + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + needs: [job1, job2] +``` + +En este ejemplo, `job3` utiliza la expresión condicional `always()` para que siempre se ejecute después de que el `job1` y el `job2` se hayan completado, sin importar si tuvieron éxito o no. Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". + +### `jobs..runs-on` + +**Obligatorio** El tipo de máquina en la que se ejecuta el trabajo. La máquina puede ser un ejecutor alojado {% data variables.product.prodname_dotcom %} o un ejecutor autoalojado. + +{% data reusables.actions.enterprise-github-hosted-runners %} + +#### Ejecutores alojados {% data variables.product.prodname_dotcom %} + +Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada trabajo se ejecuta en una nueva instancia de un entorno virtual especificado por `runs-on`. + +Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} disponibles son: + +{% data reusables.github-actions.supported-github-runners %} + +{% data reusables.github-actions.ubuntu-runner-preview %} + +##### Ejemplo + +```yaml +runs-on: ubuntu-latest +``` + +Para obtener más información, consulta "[Entornos virtuales para ejecutores alojados de {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". + +#### Ejecutores autoalojados + +{% data reusables.github-actions.self-hosted-runner-labels-runs-on %} + +##### Ejemplo + +```yaml +runs-on: [self-hosted, linux] +``` + +Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" y "[Usar ejecutores autoalojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### `jobs..environment` + +El ambiente que referencia el job. Todas las reglas de protección del ambiente deben pasar antes de que un job que referencie dicho ambiente se envie a un ejecutor. Para obtener más información, consulta la sección "[Ambientes](/actions/reference/environments)". + +Puedes proporcionar el ambiente como solo el `name` de éste, o como un objeto de ambiente con el `name` y `url`. La URL mapea hacia `environment_url` en la API de despliegues. Para obtener más información sobre la API de despliegues, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". + +##### Ejemplo utilizando solo el nombre de un ambiente + +```yaml +environment: staging_environment +``` + +##### Ejemplo utilizando un nombre y URL del ambiente + +```yaml +environment: + name: production_environment + url: https://github.com +``` + +La URL puede ser una expresión y puede utilizar cualquier contexto con excepción del contexto `secrets`. Para obtener más información acerca de las expresiones, consulta la sección "[Contexto y sintaxis de expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +#### Ejemplo +{% raw %} +```yaml +environment: + name: production_environment + url: ${{ steps.step_name.outputs.url_output }} +``` +{% endraw %} +{% endif %} + +### `jobs..outputs` + +Un `map` de salidas para un job. Las salidas de un job se encuentran disponibles para todos los jobs descendentes que dependan de este job. Para obtener más información sobre la definición de dependencias, consulta [`jobs..needs`](#jobsjob_idneeds). + +Las salidas de un job son secuencias, y las salidas de un job que contienen expresiones se evalúan en el ejecutor al final de cada job. Las salidas que contienen secretos se redactan en el ejecutor y no se envían a {% data variables.product.prodname_actions %}. + +Para utilizar salidas de jobs en un job dependiente, puedes utilizar el contexto `needs`. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)." + +#### Ejemplo + +{% raw %} +```yaml +jobs: + job1: + runs-on: ubuntu-latest + # Map a step output to a job output + outputs: + output1: ${{ steps.step1.outputs.test }} + output2: ${{ steps.step2.outputs.test }} + steps: + - id: step1 + run: echo "::set-output name=test::hello" + - id: step2 + run: echo "::set-output name=test::world" + job2: + runs-on: ubuntu-latest + needs: job1 + steps: + - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}} +``` +{% endraw %} + +### `jobs..env` + +Un `mapa` de las variables de entorno que están disponibles para todos los pasos de la tarea. También puedes establecer las variables de entorno para todo el flujo de trabajo o para un paso en particular. Para obtener más información, consulta la sección [`env`](#env) y [`jobs..steps[*].env`](#jobsjob_idstepsenv). + +{% data reusables.repositories.actions-env-var-note %} + +#### Ejemplo + +```yaml +jobs: + job1: + env: + FIRST_NAME: Mona +``` + +### `jobs..defaults` + +Un `map` de configuración predeterminada que se aplicará a todos los pasos del job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](#defaults). + +{% data reusables.github-actions.defaults-override %} + +### `jobs..defaults.run` + +Proporciona `shell` y `working-directory` predeterminados a todos los pasos de `run` en el job. No se permiten las expresiones ni contexto en esta sección. + +Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un job. También puedes configurar ajustes predeterminados para `run` para todo el flujo de trabajo. Para obtener más información, consulta [`jobs.defaults.run`](#defaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. + +{% data reusables.github-actions.defaults-override %} + +#### Ejemplo + +```yaml +jobs: + job1: + runs-on: ubuntu-latest + defaults: + run: + shell: bash + working-directory: scripts +``` + +### `jobs..if` + +Puedes usar el condicional `if` para impedir que se ejecute una tarea si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. + +{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +### `jobs..steps` + +Un trabajo contiene una secuencia de tareas llamadas `pasos`. Los pasos pueden ejecutar comandos, tareas de configuración o una acción en tu repositorio, un repositorio público o una acción publicada en un registro de Docker. Not all steps run actions, but all actions run as a step. Cada paso se ejecuta en su propio proceso en el entorno del ejecutor y tiene acceso al espacio de trabajo y al sistema de archivos. Debido a que los pasos se ejecutan en su propio proceso, los cambios en las variables de entorno no se conservan entre los pasos. {% data variables.product.prodname_dotcom %} proporciona pasos integrados para configurar y completar un trabajo. + +Puedes ejecutar un número de pasos ilimitado siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados. + +#### Ejemplo + +{% raw %} +```yaml +name: Greeting from Mona + +on: push + +jobs: + my-job: + name: My Job + runs-on: ubuntu-latest + steps: + - name: Print a greeting + env: + MY_VAR: Hi there! My name is + FIRST_NAME: Mona + MIDDLE_NAME: The + LAST_NAME: Octocat + run: | + echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME. +``` +{% endraw %} + +### `jobs..steps[*].id` + +Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +### `jobs..steps[*].if` + +Puedes usar el condiciona `if` para impedir que se ejecute un paso si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. + +{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +#### Ejemplos usando contextos + + Este paso solo se ejecuta cuando el tipo de evento es una `pull_request` y la acción del evento está `sin asignar`. + + ```yaml +steps: + - name: My first step + if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %} + run: echo This event is a pull request that had an assignee removed. +``` + +#### Ejemplo usando funciones de verificación de estado + +El `paso mi copia de seguridad` solo se ejecuta cuando se produce un error en el paso anterior de un trabajo. Para obtener más información, consulta "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". + +```yaml +steps: + - name: My first step + uses: monacorp/action-name@main + - name: My backup step + if: {% raw %}${{ failure() }}{% endraw %} + uses: actions/heroku@1.0.0 +``` + +### `jobs..steps[*].name` + +Un nombre para que tu paso se muestre en {% data variables.product.prodname_dotcom %}. + +### `jobs..steps[*].uses` + +Selecciona una acción para ejecutar como parte de un paso en tu trabajo. Una acción es una unidad de código reutilizable. Puedes usar una acción definida en el mismo repositorio que el flujo de trabajo, un repositorio público o en una [imagen del contenedor Docker publicada](https://hub.docker.com/). + +Te recomendamos encarecidamente que incluyas la versión de la acción que estás utilizando y especifiques un número de etiqueta de Git ref, SHA o Docker. Si no especificas una versión, podrías interrumpir tus flujos de trabajo o provocar un comportamiento inesperado cuando el propietario de la acción publique una actualización. +- El uso del SHA de confirmación de una versión de acción lanzada es lo más seguro para la estabilidad y la seguridad. +- Usar la versión de acción principal específica te permite recibir correcciones críticas y parches de seguridad y al mismo tiempo mantener la compatibilidad. También asegura que tu flujo de trabajo aún debería funcionar. +- Puede ser conveniente utilizar la rama predeterminada de una acciòn, pero si alguien lanza una versiòn principal nueva con un cambio importante, tu flujo de trabajo podrìa fallar. + +Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](#jobsjob_idstepswith) (con). Revisa el archivo README de la acción para determinar las entradas requeridas. + +Las acciones son archivos JavaScript o contenedores Docker. Si la acción que estás usando es un contenedor Docker, debes ejecutar el trabajo en un entorno Linux. Para obtener más detalles, consulta [`runs-on`](#jobsjob_idruns-on). + +#### Ejemplo usando acciones versionadas + +```yaml +steps: + # Reference a specific commit + - uses: actions/setup-node@74bc508 + # Reference the major version of a release + - uses: actions/setup-node@v1 + # Reference a minor version of a release + - uses: actions/setup-node@v1.2 + # Reference a branch + - uses: actions/setup-node@main +``` + +#### Ejemplo usando una acción pública + +`{owner}/{repo}@{ref}` + +Puedes usar ramas, ref o SHA específicos en un repositorio público {% data variables.product.prodname_dotcom %}. + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + # 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 +``` + +#### Ejemplo usando una acción pública en un subdirectorio + +`{owner}/{repo}/{path}@{ref}` + +Un subdirectorio en un repositorio público de {% data variables.product.prodname_dotcom %} en una rama específica, ref o SHA. + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + uses: actions/aws/ec2@main +``` + +#### Ejemplo usando la acción en el mismo repositorio que el flujo de trabajo + +`./path/to/dir` + +La ruta al directorio que contiene la acción en el repositorio de tu flujo de trabajo. Debes revisar tu repositorio antes de usar la acción. + +```yaml +jobs: + my_first_job: + steps: + - name: Check out repository + uses: actions/checkout@v2 + - name: Use local my-action + uses: ./.github/actions/my-action +``` + +#### Ejemplo usando una acción Docker Hub + +`docker://{image}:{tag}` + +Una imagen de Docker publicada en [Docker Hub](https://hub.docker.com/). + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + uses: docker://alpine:3.8 +``` + +#### Ejemplo usando una acción de registro público de Docker + +`docker://{host}/{image}:{tag}` + +Una imagen de Docker en un registro público. + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + uses: docker://gcr.io/cloud-builders/gradle +``` + +### `jobs..steps[*].run` + +Ejecuta programas de la línea de comandos usando el shell del sistema operativo. Si no proporcionas un `nombre`, el paso de establecimiento de nombre se completará por defecto con el texto especificado en el comando `run`. + +Por defecto, los comandos se ejecutan utilizando shells sin inicio de sesión. Puedes elegir un shell diferente y personalizar el shell utilizado para ejecutar los comandos. Para obtener más información, consulta "[Usar un shell específico](#using-a-specific-shell)". + +Cada palabra clave `run` representa un nuevo proceso y shell en el entorno del ejecutor. Cuando proporcionas comandos de varias líneas, cada línea se ejecuta en el mismo shell. Por ejemplo: + +* Comando de una sola línea: + + ```yaml + - name: Install Dependencies + run: npm install + ``` + +* Comando de varias líneas: + + ```yaml + - name: Clean install dependencies and build + run: | + npm ci + npm run build + ``` + +Usando la palabra clave `working-directory`, puedes especificar el directorio de trabajo de dónde ejecutar el comando. + +```yaml +- name: Clean temp directory + run: rm -rf * + working-directory: ./temp +``` + +#### Uso de un shell específico + +Puedes anular los parámetros predeterminados del shell en el sistema operativo del ejecutor utilizando la palabra clave `shell`. Puedes usar palabras clave incorporadas de `shell` keywords, o puedes definir un conjunto personalizado de opciones de shell. + +| Plataforma compatible | parámetro `shell` | Descripción | Comando ejecutado interamente | +| --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Todas | `bash` | El shell predeterminado en plataformas que no son de Windows con una reserva para `sh`. Al especificar un bash shell en Windows, se usa el bash shell incluido con Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | +| Todas | `pwsh` | Powershell Core. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `pwsh -command ". '{0}'"` | +| Todas | `python` | Ejecuta el comando python. | `python {0}` | +| Linux / macOS | `sh` | El comportamiento de reserva para plataformas que no son Windows si no se proporciona un shell y `bash` no se encuentra en la ruta. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} agrega la extensión `.cmd` a tu nombre de script y la sustituye por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | Este es el shell predeterminado que se usa en Windows. Powershell Core. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. Si tu ejecutor auto-hospedado de Windows no tiene instalado _PowerShell Core_, entonces se utilizará _PowerShell Desktop_ en su lugar. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | El PowerShell Desktop. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `powershell -command ". '{0}'"`. | + +#### Ejemplo de ejecución de un script mediante bash + +```yaml +steps: + - name: Display the path + run: echo $PATH + shell: bash +``` + +#### Ejemplo de ejecución de un script mediante `cmd` de Windows + +```yaml +steps: + - name: Display the path + run: echo %PATH% + shell: cmd +``` + +#### Ejemplo de ejecución de un script mediante PowerShell Core + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: pwsh +``` + +#### Ejemplo: Utilizar PowerShell Desktop para ejecutar un script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + +#### Ejemplo de ejecución de un script de python + +```yaml +steps: + - name: Display the path + run: | + import os + print(os.environ['PATH']) + shell: python +``` + +#### Shell personalizado + +Puede establecer el valor `shell` en una cadena de plantilla utilizando el comando `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interpreta la primera palabra delimitada por espacios en blanco de la cadena como el comando, e inserta el nombre del archivo para el script temporal en `{0}`. + +#### Códigos de salida y preferencia de acción de error + +Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutores alojados {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts shell. + +- `bash`/`sh`: + - Comportamiento a prueba de fallos utilizando `set -e o pipefail`: valor predeterminado para `bash` y `shell` incorporado. También es el valor predeterminado cuando no proporcionas una opción en plataformas que no son de Windows. + - Puedes excluir la función de falla rápida y tomar el control total al proporcionar una cadena de plantilla a las opciones del shell. Por ejemplo, `bash {0}`. + - Los shells tipo sh salen con el código de salida del último comando ejecutado en un script, que también es el comportamiento predeterminado para las acciones. El ejecutor informará el estado del paso como fallido o exitoso según este código de salida. + +- `powershell`/`pwsh` + - Comportamiento de falla rápida cuando sea posible. Para el shell incorporado `pwsh` y `powershell`, vamos a anteponer `$ErrorActionPreference = 'stop'` a los contenidos del script. + - Añadimos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a los scripts de powershell para que los estados de acción reflejen el último código de salida del script. + - Los usuarios siempre pueden optar por no usar el shell incorporado y proporcionar una opción de shell personalizada como: `pwsh -File {0}`, o `powershell -Command "& '{0}'"`, según la necesidad. + +- `cmd` + - No parece haber una manera de optar por completo por un comportamiento de falla rápida que no sea escribir tu script para verificar cada código de error y responder en consecuencia. Debido a que en realidad no podemos proporcionar ese comportamiento por defecto, debes escribir este comportamiento en tu script. + - `cmd.exe` saldrá con el nivel de error del último programa que ejecutó y devolverá el código de error al ejecutor. Este comportamiento es internamente coherente con el comportamiento predeterminado anterior `sh` y `pwsh` y es el valor predeterminado `cmd.exe`, por lo que este comportamiento permanece intacto. + +### `jobs..steps[*].with` + +Un `mapa` de los parámetros de entrada definidos por la acción. Cada parámetro de entrada es un par clave/valor. Los parámetros de entrada se establecen como variables del entorno. La variable tiene el prefijo `INPUT_` y se convierte en mayúsculas. + +#### Ejemplo + +Define los tres parámetros de entrada (`first_name`, `middle_name`, and `last_name`) definidos por la acción `hello_world`. Es posible acceder a estas variables de entrada con la acción `hello-world` como `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` y las variables de entorno `INPUT_LAST_NAME`. + +```yaml +jobs: + my_first_job: + steps: + - name: My first step + uses: actions/hello_world@main + with: + first_name: Mona + middle_name: The + last_name: Octocat +``` + +### `jobs..steps[*].with.args` + +Una `cadena` que define las entradas para un contenedor Docker. {% data variables.product.prodname_dotcom %} comunica los `args` en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor. Una `matriz de cadenas` no es compatible para este parámetro. + +#### Ejemplo + +{% raw %} +```yaml +steps: + - name: Explain why this job ran + uses: monacorp/action-name@main + with: + entrypoint: /bin/echo + args: The ${{ github.event_name }} event triggered this step. +``` +{% endraw %} + +Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia: + +1. Los documentos requerían argumentos en el README de las acciones y las omiten desde la instrucción `CMD`. +1. Usa los valores predeterminados que permiten usar la acción sin especificar ningún `args`. +1. Si la acción expone un indicador `--help` o algo similar, usa ese como el valor predeterminado para que la acción se documente automáticamente. + +### `jobs..steps[*].with.entrypoint` + +Anula el Docker `ENTRYPOINT` en el `Dockerfile` o lo establece si es que no tiene uno especificado. A diferencia de la instrucción Docker `ENTRYPOINT` que tiene un shell y formulario de ejecución, la palabra clave `entrypoint` acepta solo una cadena que define el ejecutable que se ejecutará. + +#### Ejemplo + +```yaml +steps: + - name: Run a custom command + uses: monacorp/action-name@main + with: + entrypoint: /a/different/executable +``` + +Se pretende que la palabra clave `entrypoint` se utilice con acciones de contenedor de Docker, pero también puedes utilizarla con acciones de JavaScript que no definan ninguna entrada. + +### `jobs..steps[*].env` + +Establece variables de entorno para los pasos a utilizar en el entorno del ejecutor. También puedes establecer las variables de entorno para todo el flujo de trabajo o para una tarea. Para obtener más información, consulta [`env`](#env) y [`jobs..env`](#jobsjob_idenv). + +{% data reusables.repositories.actions-env-var-note %} + +Es posible que las acciones públicas especifiquen las variables de entorno esperadas en el archivo README. Si estás estableciendo un secreto en una variable de entorno, debes establecer secretos usando el contexto `secretos`. Para obtener más información, consulta "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" y "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". + +#### Ejemplo + +{% raw %} +```yaml +steps: + - name: My first action + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + FIRST_NAME: Mona + LAST_NAME: Octocat +``` +{% endraw %} + +### `jobs..steps[*].continue-on-error` + +Impide que un trabajo falle cuando falla un paso. Se lo debe establecer en `true` para permitir que un trabajo pase cuando falla este paso. + +### `jobs..steps[*].timeout-minutes` + +El número máximo de minutos para ejecutar el paso antes de terminar el proceso. + +### `jobs..timeout-minutes` + +La cantidad máxima de minutos para permitir que un trabajo se ejecute antes que {% data variables.product.prodname_dotcom %} lo cancele automáticamente. Predeterminado: 360 + +### `jobs..strategy` + +Una estrategia crea una matriz de construcción para tus trabajos. Puedes definir variaciones diferentes para que ejecuten cada job. + +### `jobs..strategy.matrix` + +Puedes definir una matriz de diferentes configuraciones de trabajo. Una matriz te permite crear múltiples trabajos realizando la sustitución de variables en una definición de trabajo único. Por ejemplo, puedes usar una matriz para crear trabajos para más de una versión compatible de un lenguaje de programación, sistema operativo o herramienta. Una matriz reutiliza la configuración del trabajo y crea un trabajo para cada matriz que configuras. + +{% data reusables.github-actions.usage-matrix-limits %} + +Cada opción que definas en la `matriz` tiene una clave y un valor. Las claves que defines se convierten en propiedades en el contexto `matriz` y puedes hacer referencia a la propiedad en otras áreas de tu archivo de flujo de trabajo. Por ejemplo, si defines la clave `os` que contiene una matriz de sistemas operativos, puedes usar la propiedad `matrix.os` como el valor de la palabra clave `runs-on` para crear un trabajo para cada sistema operativo. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." + +El orden en que defines una `matriz` importa. La primera opción que definas será el primer trabajo que se ejecuta en tu flujo de trabajo. + +#### Ejemplo de ejecución con más de una versión de Node.js + +Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 6, 8 y 10 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`. + +Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para una matriz de tres versiones de Node.js. Para usar la matriz, el ejemplo establece la propiedad de contexto `matrix.node` como el valor del parámetro `node-version` de la entrada de la acción `setup-node`. Como resultado, se ejecutarán tres trabajos, cada uno usando una versión diferente de Node.js. + +{% raw %} +```yaml +strategy: + matrix: + node: [6, 8, 10] +steps: + # Configura la versión del nodo usada en los ejecutores alojados de GitHub + - uses: actions/setup-node@v1 + with: + # La versión de Node.js a configurar + node-version: ${{ matrix.node }} +``` +{% endraw %} + +La acción `setup-node` es la forma recomendada de configurar una versión de Node.js cuando se usan ejecutores alojados {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la acción [`setup-node`](https://github.com/actions/setup-node). + +#### Ejemplo de ejecución con más de un sistema operativo + +Puedes crear una matriz para ejecutar flujos de trabajo en más de un sistema operativo del ejecutor. También puedes especificar más de una configuración de matriz. Este ejemplo crea una matriz de 6 trabajos: + +- 2 sistemas operativos especificados en la matriz `os` +- 3 versiones de Node.js especificadas en la matriz `node` + +{% data reusables.repositories.actions-matrix-builds-os %} + +{% raw %} +```yaml +runs-on: ${{ matrix.os }} +strategy: + matrix: + os: [ubuntu-16.04, ubuntu-18.04] + node: [6, 8, 10] +steps: + - uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node }} +``` +{% endraw %} + +Para encontrar opciones de configuración compatibles para ejecutores alojados {% data variables.product.prodname_dotcom %}, consulta "[Entornos virtuales para ejecutores alojados {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". + +#### Ejemplo que incluye valores adicionales en combinaciones + +Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 4 de `node`, puedes usar `incluir` para especificar esa opción adicional. + +{% raw %} +```yaml +runs-on: ${{ matrix.os }} +strategy: + matrix: + os: [macos-latest, windows-latest, ubuntu-18.04] + node: [4, 6, 8, 10] + include: + # includes a new variable of npm with a value of 2 + # for the matrix leg matching the os and version + - os: windows-latest + node: 4 + npm: 2 +``` +{% endraw %} + +#### Ejemplo que incluye combinaciones nuevas + +Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 12 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 13 en Ubintu, puedes utilizar `include` para especificar este job adicional. + +{% raw %} +```yaml +runs-on: ${{ matrix.os }} +strategy: + matrix: + node: [12] + os: [macos-latest, windows-latest, ubuntu-18.04] + include: + - node: 13 + os: ubuntu-18.04 + experimental: true +``` +{% endraw %} + +#### Ejemplos que excluyen configuraciones de una matriz + +Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `exclude`. Si usas `exclude`, se elimina un puesto definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`exclude`). + +{% raw %} +```yaml +runs-on: ${{ matrix.os }} +strategy: + matrix: + os: [macos-latest, windows-latest, ubuntu-18.04] + node: [4, 6, 8, 10] + exclude: + # excluye el nodo 4 en macOS + - os: macos-latest + node: 4 +``` +{% endraw %} + +{% note %} + +**Nota:** Todas las combinaciones de `include` se procesan después de `exclude`. Esto te permite utilizar `include` para volver a agregar combinaciones que se excluyeron previamente. + +{% endnote %} + +##### Utilizar variables de ambiente en una matriz + +Puedes agregar variables de ambiente personalizadas para cada combinación de prueba si utilizas la clave `include`. Posteriormente, puedes referirte a las variables de ambiente personalizadas en un paso subsecuente. + +{% data reusables.github-actions.matrix-variable-example %} + +### `jobs..strategy.fail-fast` + +Cuando se establece en `verdadero`, {% data variables.product.prodname_dotcom %} cancela todos los trabajos en curso si falla cualquier trabajo de `matriz`. Predeterminado: `true` + +### `jobs..strategy.max-parallel` + +La cantidad máxima de trabajos que se pueden ejecutar de manera simultánea cuando se utiliza una estrategia de trabajo `matrix`. Por defecto, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}. + +```yaml +strategy: + max-parallel: 2 +``` + +### `jobs..continue-on-error` + +Previene que una ejecución de flujo de trabajo falle cuando un job falle. Configúralo como `true` para permitir que la ejecución del flujo de trabajo pase cuando este job falle. + +#### Ejemplo que previene que un job específico de una matiz fallida haga que falle una ejecución de flujo de trabajo + +Puedes permitir que ciertos jobs en una matriz de jobs fallen sin que la ejecución de flujo de trabajo falle. Por ejemplo, si querías permitir que fallara únicamente un job experimental con el `node` configurado en `13` sin que fallara la ejecución del flujo de trabajo. + +{% raw %} +```yaml +runs-on: ${{ matrix.os }} +continue-on-error: ${{ matrix.experimental }} +strategy: + fail-fast: false + matrix: + node: [11, 12] + os: [macos-latest, ubuntu-18.04] + experimental: [false] + include: + - node: 13 + os: ubuntu-18.04 + experimental: true +``` +{% endraw %} + +### `jobs..container` + +Un contenedor para ejecutar todos los pasos de un trabajo que aún no especifica un contenedor. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen. + +Si no configuras un `container`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor. + +#### Ejemplo + +```yaml +jobs: + my_job: + container: + image: node:10.16-jessie + env: + NODE_ENV: development + ports: + - 80 + volumes: + - my_docker_volume:/volume_mount + options: --cpus 1 +``` + +Cuando solo especificas una imagen de contenedor, puedes omitir la palabra clave `image`. + +```yaml +jobs: + my_job: + container: node:10.16-jessie +``` + +### `jobs..container.image` + +La imagen de Docker para usar como el contenedor para ejecutar la acción. El valor puede ser el nombre de la imagen de Docker Hub o un {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} nombre de registro público{% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### `jobs..container.credentials` + +{% data reusables.actions.registry-credentials %} + +#### Ejemplo + +{% raw %} +```yaml +container: + image: ghcr.io/owner/image + credentials: + username: ${{ github.actor }} + password: ${{ secrets.ghcr_token }} +``` +{% endraw %} +{% endif %} + +### `jobs..container.env` + +Establece una `mapa` de variables de entorno en el contenedor. + +### `jobs..container.ports` + +Establece una `matriz` de puertos para exponer en el contenedor. + +### `jobs..container.volumes` + +Establece una `matriz` de volúmenes para que el contenedor los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. + +Para especificar un volumen, especifica la ruta de origen y destino: + +`:`. + +`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. + +#### Ejemplo + +```yaml +volumes: + - my_docker_volume:/volume_mount + - /data/my_data + - /source/directory:/destination/directory +``` + +### `jobs..container.options` + +Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". + +### `jobs..services` + +{% data reusables.github-actions.docker-container-os-support %} + +Se usa para hospedar contenedores de servicio para un trabajo en un flujo de trabajo. Los contenedores de servicio son útiles para crear bases de datos o servicios de caché como Redis. El ejecutor crea automáticamente una red Docker y administra el ciclo de vida de los contenedores de servicio. + +Si configuras tu trabajo para que se ejecute en un contenedor, o si tu paso usa acciones del contenedor, no necesitas asignar puertos para acceder al servicio o a la acción. Docker expone automáticamente todos los puertos entre contenedores en la misma red de puente definida por el usuario de Docker. Puedes hacer referencia directamente al contenedor de servicio por su nombre de host. El nombre del host se correlaciona automáticamente con el nombre de la etiqueta que configuraste para el servicio en el flujo de trabajo. + +Si configuras el trabajo para que se ejecute directamente en la máquina del ejecutor y tu paso no usa una acción de contenedor, debes asignar cualquier puerto del contenedor de servicio Docker que sea necesario para el host Docker (la máquina del ejecutor). Puedes acceder al contenedor de servicio utilizando host local y el puerto asignado. + +Para obtener más información acerca de las diferencias entre los contenedores de servicios de red, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers)". + +#### Ejemplo de uso de host local + +Este ejemplo crea dos servicios: nginx y Redis. Cuando especificas el puerto del host de Docker pero no el puerto del contenedor, el puerto del contenedor se asigna aleatoriamente a un puerto gratuito. {% data variables.product.prodname_dotcom %} establece el puerto del contenedor asignado en el contexto {% raw %}`$ {{job.services..ports}}`{% endraw %}. En este ejemplo, puedes acceder a los puertos del contenedor de servicio utilizando los contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} y {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. + +```yaml +services: + nginx: + image: nginx + # Asignar puerto 8080 en el host de Docker al puerto 80 en el contenedor nginx + ports: + - 8080:80 + redis: + image: redis + # Asignar puerto TCP 6379 en el host de Docker a un puerto gratuito aleatorio en el contenedor Redis + ports: + - 6379/tcp +``` + +### `jobs..services..image` + +La imagen de Docker para usar como el contenedor de servicios para ejecutar la acción. El valor puede ser el nombre de la imagen de Docker Hub o un {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} nombre de registro público{% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### `jobs..services..credentials` + +{% data reusables.actions.registry-credentials %} + +#### Ejemplo + +{% raw %} +```yaml +services: + myservice1: + image: ghcr.io/owner/myservice1 + credentials: + username: ${{ github.actor }} + password: ${{ secrets.ghcr_token }} + myservice2: + image: dockerhub_org/myservice2 + credentials: + username: ${{ secrets.DOCKER_USER }} + password: ${{ secrets.DOCKER_PASSWORD }} +``` +{% endraw %} +{% endif %} + +### `jobs..services..env` + +Establece un `mapa` de variables de entorno en el contenedor de servicio. + +### `jobs..services..ports` + +Establece una `matriz` de puertos para exponer en el contenedor de servicios. + +### `jobs..services..volumes` + +Establece una `matriz` de volúmenes para que el contenedor de servicios los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. + +Para especificar un volumen, especifica la ruta de origen y destino: + +`:`. + +`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. + +#### Ejemplo + +```yaml +volumes: + - my_docker_volume:/volume_mount + - /data/my_data + - /source/directory:/destination/directory +``` + +### `jobs..services..options` + +Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". + +### Hoja de referencia de patrones de filtro + +Puedes usar caracteres especiales en los filtros de ruta, de rama y de etiqueta. + +- `*`: Coincide con cero o más caracteres, pero no coincide con el caracter `/`. Por ejemplo, `Octo*` coincide con `Octocat`. +- `**`: Coincide con cero o más de cualquier caracter. +- `?`: Coincide con cero o un solo carácter. Por ejemplo, `Octoc?t` coincide con `Octocat`. +- `+`: Empata con uno o más de los caracteres precedentes. +- `[]` Coincide con un caracter que aparece en los corchetes o que se incluye en los rangos. Los rangos solo pueden incluir `a-z`, `A-Z` y `0-9`. Por ejemplo, el rango`[0-9a-z]` empata con cualquier dígito o letra en minúscula. Por ejemplo, `[CB]at` coincide con `Cat` o `Bat` y `[1-2]00` coincide con `100` y `200`. +- `!`: Al comienzo de un patrón hace que niegue los patrones positivos previos. No tiene ningún significado especial si no es el primer caracter. + +Los caracteres `*`, `[` y `!` son caracteres especiales en YAML. Si comienzas un patrón con `*`, `[` o `!`, tienes que encerrar el patrón entre comillas. + +```yaml +# Valid +- '**/README.md' + +# Invalid - creates a parse error that +# prevents your workflow from running. +- **/README.md +``` + +Para obtener más información acerca de la sintaxis de filtro de ramas, de etiquetas y de rutas, consulta "[`on..`](#onpushpull_requestbranchestags)" y "[`on..paths`](#onpushpull_requestpaths)". + +#### Patrones para encontrar ramas y etiquetas + +| Patrón | Descripción | Ejemplo de coincidencias | +| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). | `feature/my-branch`

    `feature/your-branch` | +| `feature/**` | El comodín `**` encuentra cualquier caracter, incluida la barra (`/`) en los nombres de ramas y etiquetas. | `feature/beta-a/my-branch`

    `feature/your-branch`

    `feature/mona/the/octocat` | +| `main`

    `releases/mona-the-octcat` | Encuentra el nombre exacto de una rama o el nombre de etiqueta. | `main`

    `releases/mona-the-octocat` | +| `'*'` | Encuentra todos los nombres de rama o de etiqueta que no contienen barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `main`

    `releases` | +| `'**'` | Encuentra todos los nombres de rama y de etiqueta. Este es el comportamiento predeterminado cuando no usas un filtro de `ramas` o `etiquetas`. | `all/the/branches`

    `every/tag` | +| `'*feature'` | El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `mona-feature`

    `feature`

    `ver-10-feature` | +| `v2*` | Encuentra los nombres de rama y de etiqueta que comienzan con `v2`. | `v2`

    `v2.0`

    `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Encuentra todas las etiquetas de versión semántica con las versiones principales 1 o 2 | `v1.10.1`

    `v2.0.0` | + +#### Patrones para encontrar rutas de archivos + +Los patrones de ruta deben coincidir con toda la ruta y comenzar desde la raíz del repositorio. + +| Patrón | Descripción de coincidencias | Ejemplo de coincidencias | +| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | `README.md`

    `server.rb` | +| `'*.jsx?'` | El caracter `?` encuentra cero o uno de los caracteres de procedimiento. | `page.js`

    `page.jsx` | +| `'**'` | El comodín `*` encuentra cualquier caracter, incluida la barra (`/`). Este es el comportamiento predeterminado cuando no usas un filtro de `rutas`. | `all/the/files.md` | +| `'*.js'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). Encuentra todos los archivos `.js` en la raíz del repositorio. | `app.js`

    `index.js` | +| `'**.js'` | Encuentra todos los archivos `.js` en el repositorio. | `index.js`

    `js/index.js`

    `src/js/app.js` | +| `docs/*` | Todos los archivos dentro de la raíz del directorio `docs` en la raíz del repositorio. | `docs/README.md`

    `docs/file.txt` | +| `docs/**` | Todos los archivos en el directorio `docs` en la raíz del repositorio. | `docs/README.md`

    `docs/mona/octocat.txt` | +| `docs/**/*.md` | Un archivo con un sufijo `.md` en cualquier parte del directorio `docs`. | `docs/README.md`

    `docs/mona/hello-world.md`

    `docs/a/markdown/file.md` | +| `'**/docs/**'` | Cualquier archivo en un directorio `docs` en cualquier parte del repositorio. | `/docs/hello.md`

    `dir/docs/my-file.txt`

    `space/docs/plan/space.doc` | +| `'**/README.md'` | Un archivo README.md en cualquier parte del repositorio. | `README.md`

    `js/README.md` | +| `'**/*src/**'` | Cualquier archivo en una carpeta con un sufijo `src` en cualquier parte del repositorio. | `a/src/app.js`

    `my-src/code/js/app.js` | +| `'**/*-post.md'` | Un archivo con el sufijo `-post.md` en cualquier parte del repositorio. | `my-post.md`

    `path/their-post.md` | +| `'**/migrate-*.sql'` | Un archivo con el prefijo `migrate-` y el sufijo `.sql` en cualquier parte del repositorio. | `migrate-10909.sql`

    `db/migrate-v1.0.sql`

    `db/sept/migrate-v1.sql` | +| `*.md`

    `!README.md` | Usar un signo de exclamación (`!`) frente a un patrón lo niega. Cuando un archivo coincida con un patrón y también coincida con un patrón negativo definido más adelante en el archivo, no se incluirá el archivo. | `hello.md`

    _Does not match_

    `README.md`

    `docs/hello.md` | +| `*.md`

    `!README.md`

    `README*` | Los patrones se marcan de forma secuencial. Un patrón que niega un patrón previo volverá a incluir las rutas del archivo. | `hello.md`

    `README.md`

    `README.doc` | diff --git a/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md new file mode 100644 index 0000000000000..840380259fccf --- /dev/null +++ b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md @@ -0,0 +1,27 @@ +--- +title: Acerca de la administración de identidades y de accesos para tu empresa +shortTitle: Acerca de la administración de identidad y de acceso +intro: 'Puedes utilizar la autenticación incluida en {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}, o elegir entre CAS, LDAP, o SAML{% else %}el inicio de sesión único de SAML (SSO) y el Sistema para la Administración de Identidad entre Dominios (SCIM){% endif %} para administrar el acceso centralmente {% if currentVersion == "free-pro-team@latest" %}para las organizaciones que pertenezcan a tu empresa en {% 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: '*' +--- + +### Acerca de la administración de identidades y de accesos para tu empresa + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.saml.ae-uses-saml-sso %}{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} + +Después de que configuras la aplicación para {% data variables.product.product_name %} en tu IdP, puedes otorgar acceso a {% data variables.product.product_location %} si asignas la aplicación a los usuarios en tu IdP. Para obtener más información acerca del SSO de SAML para {% data variables.product.product_name %}, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". + +{% data reusables.scim.after-you-configure-saml %} Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". + +Para aprender cómo configurar tanto la autenticación como el aprovisionamiento de usuarios para {% data variables.product.product_location %} con tu IdP específico, consulta la sección "[Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". + +{% endif %} + +### Further reading + +- [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio de OASIS +- [Sistema para la Administración de Identidad entre Dominios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF diff --git a/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md new file mode 100644 index 0000000000000..91943c3c72034 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md @@ -0,0 +1,50 @@ +--- +title: Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad +intro: 'Puedes configurar una autenticación integrada para autenticar usuarios que no tienen acceso a tu proveedor de identidad que usa LDAP, SAML o CAS.' +redirect_from: + - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider + - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider +versions: + enterprise-server: '*' +--- + +### Acerca de la autenticación integrada para usuarios fuera de tu proveedor de identidad + +Puedes utilizar la autenticación integrada para usuarios externos cuando no puedes agregar cuentas específicas a tu proveedor de identidad (IdP), como cuentas para contratistas o usuarios de equipos. También puedes usar la autenticación integrada para acceder a una cuenta de reserva si el proveedor de identidad no está disponible. + +Una vez que se configura la autenticación integrada y un usuario autentica exitosamente con SAML o CAS, ya no tendrá la opción de autenticar con un nombre de usuario y una contraseña. Si un usuario autentica exitosamente con LDAP, las credenciales ya no se consideran internas. + +La autenticación integrada para un IdP se desactiva por defecto. + +{% warning %} + +**Advertencia:** Si desactivas la autenticación integrada, debes suspender individualmente a todo usuario que ya no debe tener acceso a la instancia. Para obtener más información, consulta [Suspender y anular suspensión de usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)." + +{% endwarning %} + +### Configurar autenticación integrada para usuarios fuera de tu proveedor de identidad + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +4. Selecciona tu proveedor de identidad. ![Seleccionar la opción proveedor de identidad](/assets/images/enterprise/management-console/identity-provider-select.gif) +5. Selecciona **Permitir la creación de cuentas con autenticación integrada**. ![Seleccionar la opción autenticación integrada](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png) +6. Lee la advertencia, luego haz clic en **Aceptar**. + +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.2fa_is_available %} + +### Invitar a usuarios fuera de tu proveedor de identidad a autenticar tu instancia + +Cuando un usuario acepta la invitación, puede utilizar su nombre de usuario y contraseña para iniciar sesión en lugar de iniciar sesión a través del IdP. + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} +{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} + +### Further reading + +- "[Usar LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap)" +- "[Usar SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml)" +- "[Usar CAS](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-cas)" diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md new file mode 100644 index 0000000000000..60dc277c78eaa --- /dev/null +++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md @@ -0,0 +1,15 @@ +--- +title: Autenticar usuarios para tu instancia de servidor de GitHub Enterprise +intro: 'Puedes usar la autenticación integrada de {% data variables.product.prodname_ghe_server %} o elegir entre CAS, LDAP o SAML para integrar tus cuentas existentes y administrar centralmente el acceso de usuarios para {% data variables.product.product_location %}.' +redirect_from: + - /enterprise/admin/categories/authentication/ + - /enterprise/admin/guides/installation/user-authentication/ + - /enterprise/admin/articles/inviting-users/ + - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/ + - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance + - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/authentication/changing-authentication-methods.md b/translations/es-ES/content/admin/authentication/changing-authentication-methods.md new file mode 100644 index 0000000000000..d6783331e7aae --- /dev/null +++ b/translations/es-ES/content/admin/authentication/changing-authentication-methods.md @@ -0,0 +1,33 @@ +--- +title: Modificar los métodos de autenticación +intro: 'Puedes modificar la manera en que {% data variables.product.prodname_ghe_server %} se autentica con tus cuentas existentes en cualquier momento.' +redirect_from: + - /enterprise/admin/user-management/changing-authentication-methods + - /enterprise/admin/authentication/changing-authentication-methods +versions: + enterprise-server: '*' +--- + +Cuando modificas el método de autenticación, las cuentas de usuario en {% data variables.product.product_location %} se conservan y los usuarios seguirán iniciando sesión en la misma cuenta siempre que su nombre de usuario no cambie. + +Si el nuevo método de autenticación modifica los nombres de usuario, se crearán nuevas cuentas. Como administrador, puedes renombrar a los usuarios a través de la configuración de administrador de sitio, o utilizando [La API de Administración de Usuarios](/rest/reference/enterprise-admin#update-the-username-for-a-user). + +Otras cuestiones que deberías tener en cuenta son las siguientes: + +* **Contraseñas:** Si comienzas a usar la autenticación integrada para tu instancia, los usuarios deben [configurar una contraseña](/enterprise/user/articles/how-can-i-reset-my-password/) una vez completado el cambio. + +* **Administradores del sitio:** Los privilegios administrativos son [controlados por tu proveedor de identidad cuando usas SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) y pueden ser [controlados por los miembros del grupo cuando usas LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance). + +* **Miembros del equipo:** Solo LDAP te permite [controlar los miembros del equipo](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) desde tu servidor de directorios. + +* **Suspensión de usuario:** cuando usas LDAP para autenticar, se puede controlar el acceso al {% data variables.product.prodname_ghe_server %} mediante _grupos restringidos_. Después de cambiar a LDAP, si se configuran grupos restringidos, los usuarios existentes que no estén en uno de esos grupos serán suspendidos. La suspensión ocurrirá cuando inicien sesión o durante la siguiente sincronización LDAP. + +* **Miembros del grupo:** Cuando usas LDAP para autenticar, [se suspende y se anula la suspensión](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) de los usuarios automáticamente, en función de los miembros del grupo con restricciones y los estados de cuenta con Active Directory. + +* **Autenticación Git:** SAML y CAS solo admiten la autenticación Git a través de HTTP o HTTPS usando un [token de acceso personal](/articles/creating-an-access-token-for-command-line-use). No se admite la autenticación de contraseña a través de HTTP o HTTPS. LDAP admite la autenticación Git basada en contraseña por defecto, pero te recomendamos [desactivar ese método](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) y forzar la autenticación mediante un token de acceso personal o clave SSH. + +* **Autenticación de API:** SAML y CAS solo admiten la autenticación de API usando un [token de acceso personal](/articles/creating-an-access-token-for-command-line-use). No se admite la autenticación básica. + +* **Autenticación de dos factores:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} + +* **Autenticación integrada para usuarios fuera de tu proveedor de identidad:** Puedes invitar usuarios a autenticar {% data variables.product.product_location %} sin agregarlos a tu proveedor de identidad. Para obtener más información, consulta "[Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md new file mode 100644 index 0000000000000..4752b437de8cc --- /dev/null +++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -0,0 +1,41 @@ +--- +title: Configurar la autenticación y el aprovisionamiento para tu empresa utilizando Azure AD +shortTitle: Configurar con Azure AD +intro: Puedes utilizar un inquilino en Azure Active Directory (Azure AD) como proveedor de identidad (IdP) para administrar centralmente la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_location %}. +permissions: Los propietarios de empresas pueden configurar la autenticación y el aprovisionamiento para una empresa en {% data variables.product.product_name %}. +product: '{% data reusables.gated-features.saml-sso %}' +versions: + github-ae: '*' +--- + +### Acerca de la autenticación y el aprovisionamiento de usuarios con Azure AD + +Azure Active Directory (Azure AD) es un servicio de Microsoft que te permite administrar centralmente las cuentas de usuario y el acceso a las aplicaciones web. Para obtener más información, consult ala sección [¿Qué es Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) en los Documentos de Microsoft. + +Para administrar la identidad y el acceso para {% data variables.product.product_name %}, puedes utilizar un inquilino en Azure AD como un IdP de SAML para la autenticación. También puedes configurar a Azure AD para que aprovisione el acceso y las cuentas automáticamente con SCIM. Esta configuración te permite asignar o desasignar la aplicación de {% data variables.product.prodname_ghe_managed %} para una cuenta de usuario en tu inquilino de Azure AD para crear automáticamente, otorgar acceso a, o desactivar una cuenta de usuario correspondiente en {% data variables.product.product_name %}. + +Para obtener más información acerca de la administración de identidades y de accesos para tu empresa en {% data variables.product.product_location %}, consulta la sección "[Administrar la identidad y el acceso para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". + +### Prerrequisitos + +Para configurar la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_name %} utilizando Azure AD, debes tener una cuenta y un inquilino en Azure AD. Para obtener más información, consulta el [Sitio Web de Azure AD](https://azure.microsoft.com/free/active-directory) y el [Inicio rápido: Creación de un inquilino en Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) en los Documentos de Microsoft. + +{% data reusables.saml.assert-the-administrator-attribute %} Para obtener más información acerca de cómo incluir el atributo `administrator` en la solicitud de SAML desde Azure AD, consulta la sección [Cómo: personalizar las notificaciones emitidas en el token SAML para aplicaciones empresariales](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) en los Documentos de Microsoft. + +{% data reusables.saml.create-a-machine-user %} + +### Configurar la autenticación y el aprovisionamiento de usuarios con Azure AD + +{% if currentVersion == "github-ae@latest" %} + +1. En Azure AD, agrega {% data variables.product.ae_azure_ad_app_link %} a tu inquilino y configura el inicio de sesión único. Para obtener más información, consulta la sección [Tutorial: Integración del inicio de sesión único (SSO) de Active Directory con {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) en los documentos de Microsoft. + +1. En {% data variables.product.prodname_ghe_managed %}, ingresa los detalles para tu inquilino de Azure AD. + + - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} + + - Si ya configuraste el SSO de SAML para {% data variables.product.product_location %} utilizando otro IdP y quieres utilizar Azure AD en vez de este, puedes editar tu configuración. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)". + +1. Habilita el aprovisionamiento de usuarios en {% data variables.product.product_name %} y configura el aprovisionamiento de usurios en Azure AD. Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)". + +{% endif %} diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md new file mode 100644 index 0000000000000..abc663192cc08 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md @@ -0,0 +1,8 @@ +--- +title: Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad +intro: Puedes utilizar un proveedor de identidad (IdP) que sea compatible tanto con el inicio de sesión único (SSO) de SAML y con el Sistema para la Administración de Identidad entre Dominios (SCIM) para configurar la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_location %}. +mapTopic: verdadero +versions: + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md new file mode 100644 index 0000000000000..17a43519debe8 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -0,0 +1,104 @@ +--- +title: Configurar el inicio de sesión único de SAML para tu empresa +shortTitle: Configurar el SSO de SAML +intro: Puedes configurar el inicio de sesión único (SSO) de SAML para tu empresa, el cual te permite controlar la autenticación centralmente para {% data variables.product.product_location %} utilizando tu proveedor de identidad (IdP). +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Los propietarios de las empresas pueden configurar el SSO de SAML para una empresa en {% data variables.product.product_name %}. +versions: + github-ae: '*' +--- + +### Acerca de SAML SSO + +{% if currentVersion == "github-ae@latest" %} + +El SSO de SAML te permite controlar centralmente y asegurar el acceso a {% data variables.product.product_location %}desde tu IdP de SAML. Cuando un usuario no autenticado vista {% data variables.product.product_location %} en un buscador, {% data variables.product.product_name %} lo redirigirá a tu IdP de SAML para autenticarse. Después de que el usuario se autentica exitosamente con una cuenta en el IdP, éste lo redirige de regreso a {% data variables.product.product_location %}. {% data variables.product.product_name %} valida la respuesta de tu IdP y luego le otorga acceso al usuario. + +Después de autenticarse exitosamente en tu IdP, la sesión de SAML del usuario para {% data variables.product.product_location %} se encuentra activa en el buscador por 24 horas. Después de 24 horas, el usuario debe autenticarse nuevamente con tu IdP. + +{% data reusables.saml.assert-the-administrator-attribute %} + +{% data reusables.scim.after-you-configure-saml %} Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". + +{% endif %} + +### Proveedores de identidad compatibles + +{% data variables.product.product_name %} es compatible con el SSO de SAML para los IdP que implementen SAML 2.0 estándar. Para obtener más información, consulta la sección [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio web de OASIS. + +{% data variables.product.company_short %} ha probado el SSO de SAML para {% data variables.product.product_name %} con los siguientes IdP. + +{% if currentVersion == "github-ae@latest" %} +- Azure AD +{% endif %} + +### Habilitar el SSO de SAML + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} + +Los siguientes IdP proporcionan documentación sobre cómo configurar el SSO de SAML para {% data variables.product.product_name %}. Si no se lista tu IdP, por favor, contáctalo para solicitar soporte para {% data variables.product.product_name %}. + + | IdP | Más información | + |:-------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Integración del inicio de sesión único (SSO) de Azure Active Directory con {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) en los Documentos de Microsoft | + +Durante la inicialización para {% data variables.product.product_name %}, debes configurar a {% data variables.product.product_name %} como un proveedor de servicios (SP) de SAML en tu IdP. Debes ingresar varios valores únicos en tu IdP para configurar {% data variables.product.product_name %} como un SP válido. + +| Valor | Otros nombres | Descripción | Ejemplo | +|:--------------------------------------------------------- |:---------------- |:--------------------------------------------------------------------------------- |:------------------------- | +| ID de Entidad de SP | URL de SP | Tu URL de más alto nivel para {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME | +| URL del Servicio de Consumidor de Aserciones (ACS) del SP | URL de respuesta | URL a la que el IdP enviará respuestas de SAML | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | +| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | https://YOUR-GITHUB-AE-HOSTNAME/sso | + +{% endif %} + +### Editar la configuración del SSO de SAML + +Si los detalles de tu IdP cambian, necesitarás editar la configuración de SSO de SAML para {% data variables.product.product_location %}. Por ejemplo, si el certificado de tu IdP expira, puedes editar el valor del certificado público. + +{% if currentVersion == "github-ae@latest" %} + +{% note %} + +**Nota**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Debajo de "Inicio de sesión único de SAML", teclea los detalles nuevos de tu IdP. ![Campos de entrada de texto con los detalles del IdP para la configuración del SSO de SAML para una empresa](/assets/images/help/saml/ae-edit-idp-details.png) +1. Opcionalmente, da clic en {% octicon "pencil" aria-label="The edit icon" %} para configurar una firma nueva o método de resumen. ![Icono de editar para cambiar la firma y el método de resumen](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) + + - Utiliza los menús desplegables y elige la nueva firma o método de resumen. ![Menús desplegables para elegir una firma nueva o método de resumen](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. Para garantizar que la información que ingresaste es correcta, da clic en **Probar la configuración de SAML**. ![Botón de "Probar la configuración de SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración del SSO de SAML](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Opcionalmente, para aprovisionar y desaprovisionar automáticamente las cuentas de usuario para {% data variables.product.product_location %}, vuelve a configurar el aprovisionamiento de usuarios con SCIM. Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". + +{% endif %} + +### Inhabilitar el SSO de SAML + +{% if currentVersion == "github-ae@latest" %} + +{% warning %} + +**Advertencia**: Si inhabilitas el SSO de SAML para {% data variables.product.product_location %}, los usuarios sin sesiones existentes del SSO de SAML no podrán ingresar en {% data variables.product.product_location %}. Las sesiones del SSO de SAML en {% data variables.product.product_location %} finalizan después de 24 horas. + +{% endwarning %} + +{% note %} + +**Nota**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. En "inicio de sesión único SAML", deselecciona **Habilitar autenticación SAML**. ![Casilla de verificación para "Habilitar la autenticación de SAML"](/assets/images/help/saml/ae-saml-disabled.png) +1. Para inhabilitar el SSO de SAML y requerir el inicio de sesión con la cuenta de usuario integrada que creaste durante la inicialización, da clic en **Guardar**. ![Botón de "Guardar" para la configuración del SSO de SAML](/assets/images/help/saml/ae-saml-disabled-save.png) + +{% endif %} diff --git a/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md new file mode 100644 index 0000000000000..b59a5ec67f361 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -0,0 +1,80 @@ +--- +title: Configurar el aprovisionamiento de usuarios para tu empresa +shortTitle: Configurar el aprovisionamiento de usuarios +intro: Puedes configurar el Sistema para la Administración de Identidad entre Dominios (SCIM) para tu empresa, el cual aprovisiona las cuentas de usuario automáticamente en {% data variables.product.product_location %} cuando asignas la aplicación para {% data variables.product.product_location %} a un usuario en tu proveedor de identidad (IdP). +permissions: Los propietarios de empresas pueden configurar el aprovisionamiento de usuarios para una empresa en {% data variables.product.product_name %}. +product: '{% data reusables.gated-features.saml-sso %}' +versions: + github-ae: '*' +--- + +### Acerca del aprovisionamiento de usuarios para tu empresa + +{% data reusables.saml.ae-uses-saml-sso %} Para obtener más información, consulta la sección "[Configurar el incio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". + +{% data reusables.scim.after-you-configure-saml %} Para obtener más información acerca del SCIM, consulta la sección [Sistema para la Administración de Identidad entre Dominios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF. + +{% if currentVersion == "github-ae@latest" %} + +Configurar el aprovisionamiento le permite a tu IdP comunicarse con {% data variables.product.product_location %} cuando asignas o desasignas la aplicación para {% data variables.product.product_name %} a un usuario en tu IdP. Cuando asignas la aplicación, tu IdP pedirá que {% data variables.product.product_location %} cree una cuenta y enviará un correo electrónico de incorporación al usuario. Cuando desasignas la aplicación, tu IdP se comunicará con {% data variables.product.product_name %} para invalidad cualquier sesión de SAML e inhabilitar la cuenta del miembro. + +Para configurar el aprovisionamiento para tu empresa, debes inhabilitar el aprovisionamiento en {% data variables.product.product_name %} y posteriormente instalar y configurar una aplicación de aprovisionamiento en tu IdP. + +La aplicación de aprovisionamiento en tu IdP se comunica con {% data variables.product.product_name %} a través de nuestra API de SCIM para empresas. Para obtener más información, consulta la sección "[Adminsitración de GitHub Enterprise](/rest/reference/enterprise-admin#scim)" en la documentación de la API de REST de {% data variables.product.prodname_dotcom %}. + +{% endif %} + +### Proveedores de identidad compatibles + +{% data reusables.scim.supported-idps %} + +### Prerrequisitos + +{% if currentVersion == "github-ae@latest" %} + +Para aprovisionar y desaprovisionar automáticamente el acceso a {% data variables.product.product_location %} desde tu IdP, primero debes configurar el SSO de SAML cuando inicializas {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". + +Debes tener acceso administrativo en tu IdP para configurar la aplicación para el aprovisionamiento de usuarios para {% data variables.product.product_name %}. + +{% endif %} + +### Habilitar el aprovisionamiento de usuarios para tu empresa + +{% if currentVersion == "github-ae@latest" %} + +1. Mientras tienes una sesión activa en + +{% data variables.product.product_location %} como un propietario de empresa, crea un token de acceso personal con el alcance **admin:enterprise**. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + {% note %} + + **Notas**: + - Para crear el token de acceso personal, te recomendamos utilizar la cuenta para el primer propietario empresarial que creaste durante la inicialización. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". + - Necesitarás que este token de accesopersonal configure la aplicación para SCIM en tu IdP. Almacena el token de manera segura en un administrador de contraseñas hasta que lo necesites nuevamente más adelante en estas instrucciones. + + {% endnote %} + {% warning %} + + **Advertencia**: Si la cuenta de usuario para el propietario de la empresa que crea el token de acceso personal se desactiva o desaprovisiona, tu IdP ya no aprovisionará ni desaprovisionará cuentas de usuario para tu empresa automáticamente. Otro propietario de empresa deberá crear un token de acceso personal nuevo y reconfigurar el aprovisionamiento en el IdP. + + {% endwarning %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Debajo de "Aprovisionamiento de usuario de SCIM", selecciona **Requerir el aprovisionamiento de usuario de SCIM**. ![Casilla de verificación para "Requerir aprovisionamiento de usuarios de SCIM" dentro de la configuración de seguridad empresarial](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. Haz clic en **Save ** (guardar). ![Botón de guardar debajo de "Requerir aprovisionamiento de usuarios de SCIM" dentro de la configuración de seguridad de la empresa](/assets/images/help/enterprises/settings-scim-save.png) +1. Configura el aprovisionamiento de usuarios en la aplicación para {% data variables.product.product_name %} en tu IdP. + + Los siguientes IdP proporcionan documentación acerca de cómo configurar el aprovisionamiento para {% data variables.product.product_name %}. Si no se lista tu IdP, por favor, contáctalo para solicitar soporte para {% data variables.product.product_name %}. + + | IdP | Más información | + |:-------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | [Tutorial: Configurar a {% data variables.product.prodname_ghe_managed %} para el aprovisionamiento automático de usuarios](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) en los documentos de Microsoft | + + La aplicación en tu IdP requiere dos valores para aprovisionar o desaprovisionar las cuentas de usuario en {% data variables.product.product_location %}. + + | Valor | Otros nombres | Descripción | Ejemplo | + |:------------------ |:--------------------------------------- |:--------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------- | + | URL | URL de inquilino | URL para la API de aprovisionamiento de SCIM para tu empresa en {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | + | Secreto compartido | Token de acceso personal, token secreto | Toekn para que la aplicación en tu IdP realice las tareas de aprovisionamiento en nombre de un propietario de empresa | Token de acceso personal que creaste en el paso 1 | + +{% endif %} diff --git a/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md new file mode 100644 index 0000000000000..b9e0ddec61505 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md @@ -0,0 +1,16 @@ +--- +title: Desactivar los registros no autenticados +redirect_from: + - /enterprise/admin/articles/disabling-sign-ups/ + - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups + - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups +intro: 'Si usas la autenticación integrada, puedes impedir que las personas no autenticadas puedan crear una cuenta.' +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Quita la marca de selección en **Activar registro**. ![Habilitar casilla de registro](/assets/images/enterprise/management-console/enable-sign-up.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/authentication/index.md b/translations/es-ES/content/admin/authentication/index.md new file mode 100644 index 0000000000000..18d0107ffe4d1 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/index.md @@ -0,0 +1,27 @@ +--- +title: Autenticación +intro: Puedes configurar ingresan los usuarios en {% data variables.product.product_name %}. +redirect_from: + - /enterprise/admin/authentication +versions: + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /authenticating-users-for-your-github-enterprise-server-instance %} + {% link_in_list /using-built-in-authentication %} + {% link_in_list /disabling-unauthenticated-sign-ups %} + {% link_in_list /using-cas %} + {% link_in_list /using-saml %} + {% link_in_list /using-ldap %} + {% link_in_list /allowing-built-in-authentication-for-users-outside-your-identity-provider %} + {% link_in_list /changing-authentication-methods %} +{% topic_link_in_list /managing-identity-and-access-for-your-enterprise %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise %} + {% link_in_list /configuring-saml-single-sign-on-for-your-enterprise %} + {% link_in_list /configuring-user-provisioning-for-your-enterprise %} +{% topic_link_in_list /configuring-authentication-and-provisioning-with-your-identity-provider %} + {% link_in_list /configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad %} diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md new file mode 100644 index 0000000000000..98864a299f0bf --- /dev/null +++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md @@ -0,0 +1,9 @@ +--- +title: Administrar la identidad y el acceso para tu empresa +shortTitle: Administrar el acceso y la identidad +intro: Puedes adminsitrar centralmente el acceso y las cuentas en {% data variables.product.product_location %}. +mapTopic: verdadero +versions: + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/authentication/using-built-in-authentication.md b/translations/es-ES/content/admin/authentication/using-built-in-authentication.md new file mode 100644 index 0000000000000..900fa95d1fa1d --- /dev/null +++ b/translations/es-ES/content/admin/authentication/using-built-in-authentication.md @@ -0,0 +1,31 @@ +--- +title: Usar la autenticación integrada +intro: 'Cuando usas el método de autenticación predeterminado, todos los detalles de autenticación se almacenan dentro de {% data variables.product.product_location %}. La autenticación integrada es el método predeterminado, si ya no tienes un proveedor de autenticación establecido, como LDAP, SAML o CAS.' +redirect_from: + - /enterprise/admin/user-management/using-built-in-authentication + - /enterprise/admin/authentication/using-built-in-authentication +versions: + enterprise-server: '*' +--- + +Puedes crear mensajes personalizados que los usuarios verán en las páginas de inicio de sesión y de cierre de sesión. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)." + +### Configurar la autenticación integrada + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +4. Selecciona **Autenticación integrada**. ![Seleccionar la opción autenticación integrada](/assets/images/enterprise/management-console/built-in-auth-select.png) + +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.2fa_is_available %} + +### Crear tu cuenta y agregar usuarios + +Una vez que se ha creado tu instancia, necesitarás crear tu propia cuenta de administrador y usarla para aprovisionar usuarios. + +1. En la página "Crear cuenta de administrador " en `http(s)://[hostname]/join`, elige tu nombre de usuario, contraseña y dirección de correo electrónico, luego haz clic en **Crear una cuenta**. ![Crear cuenta de administrador](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} +{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} diff --git a/translations/es-ES/content/admin/authentication/using-cas.md b/translations/es-ES/content/admin/authentication/using-cas.md new file mode 100644 index 0000000000000..d045dfb79865d --- /dev/null +++ b/translations/es-ES/content/admin/authentication/using-cas.md @@ -0,0 +1,44 @@ +--- +title: Usar CAS +redirect_from: + - /enterprise/admin/articles/configuring-cas-authentication/ + - /enterprise/admin/articles/about-cas-authentication/ + - /enterprise/admin/user-management/using-cas + - /enterprise/admin/authentication/using-cas +intro: 'CAS es un protocolo de inicio de sesión único (SSO) para varias aplicaciones web. Una cuenta de usuario de CAS no ocupa una licencia de usuario de {% if currentVersion ver_gt "enterprise-server@2.16" %}{% else %}plaza{% endif %} hasta que el usuario inicie sesión.' +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_user_management.built-in-authentication %} + +### Consideraciones sobre el nombre de usuario con CAS + +{% data reusables.enterprise_management_console.username_normalization %} + +{% data reusables.enterprise_management_console.username_normalization_sample %} + +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.external_auth_disables_2fa %} + +### Atributos de CAS + +Están disponibles los siguientes atributos. + +| Nombre del atributo | Type | Descripción | +| ------------------- | --------- | ------------------------------------------------------------------------ | +| `username` | Requerido | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | + +### Configurar CAS +{% warning %} + +**Advertencia:** Antes de configurar CAS en {% data variables.product.product_location %}, ten en cuenta que los usuarios no podrán usar sus nombres de usuario ni contraseñas CAS para autenticar las solicitudes de API o las operaciones Git a través de HTTP/HTTPS. En cambio, será necesario que [creen un token de acceso](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use). + +{% endwarning %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Selecciona **CAS**. ![Seleccionar CAS](/assets/images/enterprise/management-console/cas-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada](/assets/images/enterprise/management-console/cas-built-in-authentication.png) +5. En el campo **URL del servidor**, escribe la URL completa de tu servidor CAS. Si tu servidor CAS usa un certificado que no puede ser validado por {% data variables.product.prodname_ghe_server %}, puedes usar el comando `ghe-ssl-ca-certificate-install` para instalarlo como un certificado de confianza. diff --git a/translations/es-ES/content/admin/authentication/using-ldap.md b/translations/es-ES/content/admin/authentication/using-ldap.md new file mode 100644 index 0000000000000..9c8ae4de214c6 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/using-ldap.md @@ -0,0 +1,197 @@ +--- +title: Usar LDAP +redirect_from: + - /enterprise/admin/articles/configuring-ldap-authentication/ + - /enterprise/admin/articles/about-ldap-authentication/ + - /enterprise/admin/articles/viewing-ldap-users/ + - /enterprise/admin/hidden/enabling-ldap-sync/ + - /enterprise/admin/hidden/ldap-sync/ + - /enterprise/admin/user-management/using-ldap + - /enterprise/admin/authentication/using-ldap +intro: 'LDAP te permite autenticar el {% data variables.product.prodname_ghe_server %} en tus cuentas existentes y administrar de manera centralizada el acceso a los repositorios. LDAP es un protocolo de aplicación popular para acceder a servicios de información de directorios y mantenerlos, y uno de los protocolos más comunes que se usan para integrar software de terceros con directorios de usuarios de empresas grandes.' +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_user_management.built-in-authentication %} + +### Servicios LDAP admitidos + +El {% data variables.product.prodname_ghe_server %} se integra con los siguientes servicios LDAP: + +* Active Directory +* FreeIPA +* Oracle Directory Server Enterprise Edition +* OpenLDAP +* Open Directory +* 389-ds + +### Consideraciones sobre el nombre de usuario con LDAP + +{% data reusables.enterprise_management_console.username_normalization %} + +{% data reusables.enterprise_management_console.username_normalization_sample %} + +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.2fa_is_available %} + +### Configurar LDAP con {% data variables.product.product_location %} + +Una vez configurado LDAP, los usuarios podrán iniciar sesión en tu instancia con sus credenciales LDAP. Cuando los usuarios inician sesión por primera vez, sus nombres de perfil, direcciones de correo electrónico y claves SSH se establecen con los atributos de LDAP desde tu directorio. + +Cuando configuras el acceso de LDAP para los usuarios a través de {% data variables.enterprise.management_console %}, tus licencias de usuario no se utilizarán sino hasta que los usuarios ingresen en tu instancia por primera vez. Sin embargo, si creas una cuenta manualmente utilizando la configuración de administrador para el sitio, esta licencia de usuario se tomará en cuenta. + +{% warning %} + +**Advertencia:** Antes de configurar LDAP en {% data variables.product.product_location %}, asegúrate de que tu servicio LDAP admita resultados paginados. + +{% endwarning %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. En "Authentication" (Autenticación), selecciona **LDAP**. ![Seleccionar LDAP](/assets/images/enterprise/management-console/ldap-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada LDAP](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) +5. Agrega tus parámetros de configuración. + +### Atributos de LDAP +Usa estos atributos para terminar de configurar LDAP para {% data variables.product.product_location %}. + +| Nombre del atributo | Type | Descripción | +| --------------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Host` | Requerido | El host LDAP, p. ej. `ldap.example.com` o `10.0.0.30`. Si el nombre del host solo está disponible desde tu red interna, es posible que primero debas configurar el DNS de {% data variables.product.product_location %} para que pueda resolver el nombre del host usando tus servidores de nombres internos. | +| `Port (Puerto)` | Requerido | El puerto que están escuchando los servicios LDAP. Los ejemplos incluyen: 389 y 636 (para LDAPS). | +| `Encryption (Cifrado)` | Requerido | El método de cifrado usado para garantizar las comunicaciones con el servidor LDAP. Los ejemplos incluyen el normal (sin cifrado), el SSL/LDAPS (cifrado desde el principio) y el StartTLS (se actualiza a comunicación cifrada una vez que se conecta). | +| `Usuario de búsqueda de dominio` | Opcional | El usuario LDAP que realiza las búsquedas de usuario para autenticar otros usuarios cuando inician sesión. Esto suele ser una cuenta de servicio creada específicamente para integraciones de terceros. Usa un nombre certificado completo, como `cn=Administrator,cn=Users,dc=Example,dc=com`. Con Active Directory, también puedes usar la sintaxis `[DOMAIN]\[USERNAME]` (p. ej.,`WINDOWS\Administrator`) para el usuario de búsqueda de dominio. | +| `Domain search password (Contraseña de búsqueda de dominio)` | Opcional | La contraseña para el usuario de búsqueda de dominio. | +| `Grupo de administradores` | Opcional | Los usuarios de este grupo son promovidos a administradores del sitio cuando inician sesión en tu aparato. Si no configuras un Grupo de administradores LDAP, la primera cuenta de usuario LDAP que inicie sesión en tu aparato será promovida automáticamente a administrador del sitio. | +| `Domain base (Base de dominio)` | Requerido | El `Nombre Distintivo` (DN) completamente calificado de un subárbol LDAP que quieras buscar para usuarios y grupos. Puedes agregar tantos como quieras; sin embargo, cada grupo debe estar definido en la misma base de dominio que los usuarios que le pertenecen. Si especificas grupos de usuarios con restricciones, solo los usuarios que pertenecen a esos grupo estarán al alcance. Te recomendamos que especifiques el primer nivel de tu árbol de directorios LDAP como tu base de dominio y que uses grupos de usuarios con restricciones para controlar el acceso. | +| `Restricted user groups (Grupos de usuarios con restricciones)` | Opcional | Si se especifica, solo los usuarios de estos grupos tendrán permiso para iniciar sesión. Solo necesitas especificar los nombres comunes (CN) de los grupos y puedes agregar tantos grupos como quieras. Si no se especifica ningún grupo, *todos* los usuarios dentro del alcance de la base de dominio especificada podrán iniciar sesión en tu instancia del {% data variables.product.prodname_ghe_server %}. | +| `User ID (Identificación de usuario)` | Requerido | El atributo de LDAP que identifica al usuario LDAP que intenta una autenticación. Una vez que se establece una asignación, los usuarios pueden modificar sus nombres de usuario del {% data variables.product.prodname_ghe_server %}. El campo debería ser `sAMAccountName` para la mayoría de las instalaciones de Active Directory, pero puede ser `uid` para otras soluciones LDAP, como OpenLDAP. El valor predeterminado es `uid`. | +| `Nombre de perfil` | Opcional | El nombre que aparecerá en la página de perfil del {% data variables.product.prodname_ghe_server %} del usuario. A menos que la sincronización LDAP esté activada, los usuarios pueden modificar sus nombres de perfil. | +| `Emails (Correos electrónicos)` | Opcional | Las direcciones de correo electrónico para la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | +| `SSH keys (Claves SSH)` | Opcional | Las claves SSH públicas vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. Las claves deben ser en formato OpenSSH. | +| `Claves GPG` | Opcional | Las claves GPG vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | +| `Disable LDAP authentication for Git operations (Desactivar la autenticación LDAP para las operaciones de Git)` | Opcional | Si está seleccionado, [desactiva](#disabling-password-authentication-for-git-operations) la posibilidad del usuario de usar contraseñas LDAP para autenticar las operaciones de Git. | +| `Enable LDAP certificate verification (Activar la verificación de certificado LDAP)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-certificate-verification) la verificación de certificado LDAP. | +| `Synchronization (Sincronización)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-sync) la sincronización LDAP. | + +#### Desactivar la autenticación de contraseña para las operaciones de Git + +Selecciona **Disable username and password authentication for Git operations** (Desactivar la autenticación de nombre de usuario y contraseña para las operaciones de Git) en los parámetros de tu LDAP para implementar el uso de los tokens de acceso personal o las claves SSH para el acceso a Git, que pueden ayudarte a prevenir que tu servidor se sobrecargue de solicitudes de autenticación LDAP. Recomendamos esta configuración, ya que un servidor LDAP de respuesta lenta, en especial combinado con una gran cantidad de solicitudes debido al sondeo, suele ser una causa de problemas e interrupciones. + +![Desactivar la casilla de verificación autenticación de contraseña LDAP](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) + +Cuando se selecciona esta opción, si un usuario intenta usar una contraseña para las operaciones de Git a través de la línea de comando, recibirá un mensaje de error que dice: `La autenticación de contraseña no está permitida para las operaciones de Git. Debes usar un token de acceso personal.` + +#### Activar la verificación de certificado LDAP + +Selecciona **Enable LDAP certificate verification** (Activar verificación de certificado LDAP) en tus parámetros LDAP para validar el certificado del servidor LDAP que usas con TLS. + +![Casilla de verificación de certificado LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) + +Cuando se selecciona esta opción, el certificado se valida para garantizar que: +- Si el certificado contiene al menos un nombre alternativo del firmante (SAN), uno de los SAN coincida con el nombre del host de LDAP. De lo contrario, que el nombre común (CN) coincida con el nombre del host de LDAP. +- El certificado no haya vencido. +- El certificado esté firmado por una entidad de certificación (CA) de confianza. + +#### Activar la sincronización LDAP + +{% note %} + +**Nota:** Los equipos que utilizan sincronizaciòn de LDAP se limitan a un màximo de 1499 miembros. + +{% endnote %} + +La sincronización LDAP te permite sincronizar usuarios y miembros del equipo del {% data variables.product.prodname_ghe_server %} con tus grupos LDAP establecidos. Esto te permite establecer un control de acceso basado en roles para los usuarios desde tu servidor LDAP, en lugar de hacerlo de forma manual dentro del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Crear equipos](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)". + +Para activar la sincronización LDAP, en tus parámetros LDAP, selecciona **Synchronize Emails** (Sincronizar correos electrónicos), **Synchronize SSH Keys** (Sincronizar claves SSH) o **Synchronize GPG Keys** (Sincronizar claves GPG). + +![Casilla de verificación de Sincronización](/assets/images/enterprise/management-console/ldap-synchronize.png) + +Una vez que actives la sincronización LDAP, se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada cuenta de usuario: + +- Si has permitido la autenticación integrada para usuarios externos a tu proveedor de identidad, y el usuario está usando la autenticación integrada, pasa al siguiente usuario. +- Si no existe una asignación LDAP para el usuario, intenta asignar el usuario a una entrada LDAP en el directorio. Si el usuario no se puede asignar a una entrada LDAP, suspéndelo y pasa al siguiente usuario. +- Si hay una asignación LDAP y falta la entrada LDAP correspondiente en el directorio, suspende el usuario y pasa al siguiente usuario. +- Si la entrada LDAP correspondiente se marcó como desactivada, y el usuario aún no se suspendió, suspéndelo y pasa al siguiente usuario. +- Si la entrada LDAP correspondiente no se marcó como desactivada, el usuario está suspendido y _Reactivate suspended users_ (Reactivar usuarios suspendidos) está activado en el centro de administración, anula la suspensión del usuario. +- Si la entrada LDAP correspondiente incluye un atributo `name`, actualiza el nombre de perfil del usuario. +- Si la entrada LDAP correspondiente está en el grupo de administradores, promueve al usuario a administrador del sitio. +- Si la entrada LDAP correspondiente no está en el grupo de administradores, degrada al usuario a una cuenta normal. +- Si un campo de usuario LDAP está definido para correos electrónicos, sincroniza los parámetros del correo electrónico del usuario con la entrada LDAP. Establece la primera entrada `mail` LDAP como el correo electrónico principal. +- Si un campo de usuario LDAP está definido para claves públicas SSH, sincroniza las claves SSH públicas del usuario con la entrada LDAP. +- Si un campo de usuario LDAP está definido para claves GPG, sincroniza las claves GPG del usuario con la entrada LDAP. + +{% note %} + +**Nota**: Las entradas LDAP solo pueden estar marcadas como desactivadas si usas Active Directory y el atributo `userAccountControl` está presente y marcado con `ACCOUNTDISABLE`. + +{% endnote %} + +También se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada equipo que haya sido asignado a un grupo LDAP: + +- Si se eliminó el grupo LDAP correspondiente de un equipo, elimina todos los miembros del equipo. +- Si las entradas de miembros LDAP se eliminaron del grupo LDAP, elimina los usuarios correspondientes del equipo. Si como resultado el usuario pierde acceso a algún repositorio, elimina toda bifurcación privada que el usuario tenga de esos repositorios. +- Si las entradas de miembros LDAP se agregaron al grupo LDAP, agrega los usuarios correspondientes al equipo. Si como resultado el usuario recupera el acceso a algún repositorio, restablece toda bifurcación privada de los repositorios que haya sido eliminada debido a que el usuario perdió acceso en los últimos 90 días. + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +{% warning %} + +**Advertencia de seguridad:** + +Cuando la sincronización LDAP está activada, los administradores del sitio y los propietarios de la organización pueden buscar en el directorio LDAP los grupos a los cuales asignar el equipo. + +Esto posibilita divulgar información organizativa confidencial a contratistas u otros usuarios sin privilegios, incluidos los siguientes: + +- La existencia de grupos LDAP específicos visibles para el *Usuario de búsqueda de dominio*. +- Los miembros del grupo LDAP que tienen cuentas de usuario del {% data variables.product.prodname_ghe_server %}, que se divulga cuando se crea un equipo sincronizado con ese grupo LDAP. + +Si no se desea divulgar dicha información, su empresa u organización debe restringir los permisos del *Usuario de búsqueda de dominio* en la consola de administración. Si no es posible aplicar dicha restricción, comuníquese con el {% data variables.contact.contact_ent_support %}. + +{% endwarning %} + +#### Clases de objetos del grupo LDAP admitidas + +El {% data variables.product.prodname_ghe_server %} admite estas clases de objetos del grupo LDAP. Los grupos se pueden anidar. + +- `group` +- `groupOfNames` +- `groupOfUniqueNames` +- `posixGroup` + +### Ver y crear usuarios LDAP + +Puedes ver la lista completa de usuarios LDAP que tienen acceso a tu instancia y aprovisionar nuevos usuarios. + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. En la barra lateral izquierda, haz clic en **LDAP users** (Usuarios LDAP). ![Pestaña LDAP users (Usuarios LDAP)](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) +4. Para buscar un usuario, escribe un nombre de usuario completo o parcial y haz clic en **Search** (Buscar). Se mostrarán los usuarios existentes en los resultados de búsqueda. Si un usuario no existe, haz clic en **Create** (Crear) para aprovisionar la nueva cuenta de usuario. ![Búsqueda LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.png) + +### Actualizar cuentas LDAP + +A menos que [la sincronización LDAP esté activada](#enabling-ldap-sync), las modificaciones de las cuentas LDAP no se sincronizan automáticamente con el {% data variables.product.prodname_ghe_server %}. + +* Para usar un nuevo grupo de administración LDAP, los usuarios deben ser promovidos y degradados de forma manual en el {% data variables.product.prodname_ghe_server %} para reflejar las modificaciones en LDAP. +* Para agregar o eliminar cuentas LDAP de los grupos de administración LDAP, [promueve o degrada las cuentas en el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator). +* Para eliminar las cuentas LDAP, [suspende las cuentas del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users). + +#### Sincronizar cuentas LDAP de forma manual + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. En "LDAP", haz clic en **Sync now** (Sincronizar ahora) para actualizar de forma manual la cuenta con los datos de tu servidor LDAP. ![Botón LDAP sync now (Sincronizar LDAP ahora)](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) + +También puedes [utilizar la API para activar una sincronización manual](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap). + +### Revocar acceso a {% data variables.product.product_location %} + +Si [la sincronización LDAP está activada](#enabling-ldap-sync), al eliminar las credenciales LDAP de un usuario, se suspenderá su cuenta hasta la siguiente ejecución de sincronización. + +Si la sincronización LDAP **no** está activada, debes suspender de forma manual la cuenta del {% data variables.product.prodname_ghe_server %} después de eliminar las credenciales LDAP. Para obtener más información, consulta [Suspender y anular suspensión de usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/translations/es-ES/content/admin/authentication/using-saml.md b/translations/es-ES/content/admin/authentication/using-saml.md new file mode 100644 index 0000000000000..86cfa84660317 --- /dev/null +++ b/translations/es-ES/content/admin/authentication/using-saml.md @@ -0,0 +1,181 @@ +--- +title: Usar SAML +redirect_from: + - /enterprise/admin/articles/configuring-saml-authentication/ + - /enterprise/admin/articles/about-saml-authentication/ + - /enterprise/admin/user-management/using-saml + - /enterprise/admin/authentication/using-saml +intro: 'SAML es un estándar basado en XML para autenticación y autorización. {% data variables.product.prodname_ghe_server %} puede actuar como un proveedor de servicios (SP) con tu proveedor de identidad (IdP) SAML interno.' +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_user_management.built-in-authentication %} + +### Servicios SAML admitidos + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Consideraciones sobre el nombre de usuario con SAML + +Cada nombre de usuario {% data variables.product.prodname_ghe_server %} lo determina una de las siguientes aserciones en la respuesta SAML, ordenadas por prioridad: + +- El atributo de nombre de usuario personalizado, si está definido y si hay uno. +- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, si hay una. +- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, si hay una. +- El elemento `NameID`. + +Se requiere el elemento `NameID`, incluso si hay otros atributos. + +Se crea un mapeo entre la `NameID` y el nombre de usuario de {% data variables.product.prodname_ghe_server %}, para que la `NameID` deba ser persistente, única, y no estar sujeta a cambios para el ciclo de vida del usuario. + +{% note %} + +**Nota**: Si la `NameID` de un usuario sí cambia en el IdP, el usuario verá un mensaje de error cuando intente ingresar en tu instancia de {% data variables.product.prodname_ghe_server %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Para restablecer el acceso del usuario, necesitarás actualizar el mapeo de `NameID` de la cuenta de usuario. Para obtener más información, consulta la sección "[Actualizar la `NameID`](#updating-a-users-saml-nameid) de SAML de un usuario.{% else %} Para obtener más información, consulta "[Error: 'Another user already owns the account'](#error-another-user-already-owns-the-account)".{% endif %} + +{% endnote %} + +{% data reusables.enterprise_management_console.username_normalization %} + +{% data reusables.enterprise_management_console.username_normalization_sample %} + +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.external_auth_disables_2fa %} + +### Metadatos SAML + +Los metadatos del provedor de servicios de tu instancia de {% data variables.product.prodname_ghe_server %} se encuentran disponibles en `http(s)://[hostname]/saml/metadata`. + +Para configurar tu proveedor de identidad de forma manual, la URL del Servicio de consumidor de aserciones (ACS) es `http(s)://[hostname]/saml/consume`. Esta usa el enlace `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. + +### Atributos de SAML + +Estos atributos están disponibles. Puedes modificar el nombre del atributo en [Consola de administración](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), a excepción del atributo `administrator`. + +| Nombre de atributo predeterminado | Type | Descripción | +| --------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ID del nombre` | Requerido | Un identificador de usuario persistente. Se puede usar cualquier formato de identificador de nombre persistente. El elemento `NameID` se usará para un nombre de usuario {% data variables.product.prodname_ghe_server %}, a menos que se proporcione una de las aserciones alternativas. | +| `administrator` | Opcional | Cuando el valor es "true", el usuario será promovido automáticamente como un administrador. Cualquier otro valor o un valor no existente degradará al usuario a una cuenta de usuario normal. | +| `username` | Opcional | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | +| `nombre_completo` | Opcional | El nombre del usuario que se muestra en su página de perfil. Los usuarios pueden cambiar sus nombres después del aprovisionamiento. | +| `emails` | Opcional | Las direcciones de correo electrónico para el usuario. Se puede especificar más de una. | +| `claves_públicas` | Opcional | Las claves SSH públicas para el usuario. Se puede especificar más de una. | +| `gpg_keys` | Opcional | Las claves GPG para el usuario. Se puede especificar más de una. | + +### Configurar parámetros SAML + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Selecciona **SAML**. ![Autenticación SAML](/assets/images/enterprise/management-console/auth-select-saml.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación Autenticación integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +5. Opcionalmente, para activar el SSO de respuesta no solicitada, selecciona **IdP initiated SSO**. Por defecto, {% data variables.product.prodname_ghe_server %} responderá a una solicitud iniciada por un proveedor de identidad (IdP) no solicitada con una `AuthnRequest` de vuelta al IdP. ![SSO del IdP SAML](/assets/images/enterprise/management-console/saml-idp-sso.png) + + {% tip %} + + **Nota**: Te recomendamos mantener este valor **sin seleccionar**. Debes activar esta función **solo** en el caso inusual que tu implementación SAML no admita el SSO iniciado del proveedor de servicios y que {% data variables.contact.enterprise_support %} lo aconseje. + + {% endtip %} + +5. Selecciona **Disable administrator demotion/promotion (Desactivar la degradación/promoción del administrador)** si **no** quieres que tu proveedor de SAML determine los derechos del administrador para los usuarios en {% data variables.product.product_location %}. ![Configuración de administración para desactivar SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +6. En el campo **URL de inicio de sesión único**, escribe la HTTP o el extremo HTTPS en tu IdP para las solicitudes de inicio de sesión único. Este valor lo provee la configuración de tu IdP. Si el host solo está disponible desde tu red interna, es posible que sea necesario [configurar {% data variables.product.product_location %} para usar los servidores de nombres internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticación SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) +7. También puedes escribir tu nombre de emisor de SAML en el campo **Emisor**. Esto verifica la autenticidad de los mensajes enviados a {% data variables.product.product_location %}. ![Emisor SAML](/assets/images/enterprise/management-console/saml-issuer.png) +8. En los menúes desplegables **Método de firma** y **Método de resumen**, elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las respuestas desde {% data variables.product.product_location %}. Especifica el formato con el menú desplegable **Formato de identificador de nombre**. ![Método SAML](/assets/images/enterprise/management-console/saml-method.png) +9. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. ![Autenticación SAML](/assets/images/enterprise/management-console/saml-verification-cert.png) +10. Modifica los nombres de atributo de SAML para hacerlos coincidir con tu IdP, si es necesario, o acepta los nombres predeterminados. ![Nombres de atributo de SAML](/assets/images/enterprise/management-console/saml-attributes.png) + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +### Revocar acceso a {{ site.data.variables.product.product_location_enterprise }} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Selecciona **SAML**. ![Elemento de "Todos los usuarios" en la barra lateral en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/all-users.png) +3. En la lista de usuarios, da clic en el nombre de usuario del cual te gustaría actualizar el mapeo de la `NameID`. ![Nombre de usuario en la lista de cuentas de usuario de la instancia](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) +{% data reusables.enterprise_site_admin_settings.security-tab %} +5. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. ![Botón de "Editar" debajo de "Autenticación de SAML" y a la derecha de "Actualizar la NameID de SAML"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) +6. En el campo de "NameID", teclea la `NameID` nueva para el usuario. ![Campo de "NameID" en diálogo modal con el valor de NameID ingresado](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) +7. Da clic en **Actualizar NameID**. ![Botón de "Actualizar NameID" debajo del valor actualizado de la NameID dentro del modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) + +{% endif %} + +### Revocar acceso a {% data variables.product.product_location %} + +Si eliminas un usuario desde tu proveedor de identidad, también debes suspenderlos de forma manual. De lo contrario, seguirán estando disponibles para autenticarse usando los tokens de acceso o las claves SSH. Para obtener más información, consulta "[Suspender y anular suspensión de usuarios](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". + +### Requisitos para los mensajes de respuesta + +El mensaje de respuesta debe cumplir con los siguientes requisitos: + +- Se debe proporcionar el elemento `` en el documento de respuesta raíz y empatar la URL ACS únicamente cuando dicho documento se firme. Si la aserción está firmada, ésta se ignorará. +- Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Ésta es la URL para la instancia de {% data variables.product.prodname_ghe_server %}, tal como `https://ghe.corp.example.com`. +- Cada aserción en la respuesta **debe** estar protegida por una firma digital. Esto se puede lograr firmando cada elemento `` individual o firmando el elemento ``. +- Un elemento `` se debe proporcionar como parte del elemento ``. Se puede usar cualquier formato de identificador de nombre persistente. +- El atributo `Recipient` debe estar presente y establecido en la URL ACS. Por ejemplo: + +```xml + + + + ... + + + + + + + monalisa + + + + +``` + +### Autenticación SAML + +de entidad del {% data variables.product.prodname_ghe_server %}, se presentará el siguiente mensaje de error en el registro de autenticación: Para obtener más información sobre los requisitos de respuesta de SAML, consulta la sección "[Requisitos de mensaje de respuesta](#response-message-requirements)". + +#### Error: "Another user already owns the account" + +Cuando un usuario ingresa en {% data variables.product.prodname_ghe_server %} por primera vez con la autenticación de SAML, {% data variables.product.prodname_ghe_server %} crea una cuenta de usuario en la instancia y mapea la `NameID` de SAML hacia la cuenta. + +Cuando el usuario vuelve a ingresar, {% data variables.product.prodname_ghe_server %} compara el mapeo de la `NameID` de la cuenta con la respuesta del IdP. Si la `NameID` en la respuesta del IdP ya no empata con la `NameID` que {% data variables.product.prodname_ghe_server %} espera para el usuario, el inicio de sesión fallará. El usuario verá el siguiente mensaje. + +> Another user already owns the account. Please have your administrator check the authentication log. + +Este mensaje habitualmente indica que el nombre de usuario o dirección de correo electrónico cambió en el IdP. {% if currentVersion ver_gt "enterprise-server@2.21" %}Asegúrate de que el mapeo de la `NameID` para la cuenta de usuario en {% data variables.product.prodname_ghe_server %} concuerde con la `NameID` del usuario en tu IdP. Para obtener más información, consulta la sección "[Actualizar la `NameID` de SAML de un usuario](#updating-a-users-saml-nameid)".{% else %}Para encontrar ayuda para actualizar el mapeo de la `NameID`, contacta a {% data variables.contact.contact_ent_support %}.{% endif %} + +#### Si la respuesta SAML no está firmada o la firma no coincide con los contenidos, se presentará el siguiente mensaje de error en el registro de autenticación: + +Si el `Recipient` no coincide con la URL ACS, se presentará el siguiente mensaje de error en el registro de autenticación: + +``` +El destinatario en la respuesta SAML no debe estar en blanco. +``` + +``` +El destinatario en la respuesta SAML no era válido. +``` + +Asegúrate de que configuraste el valor para `Recipient` en tu IdP como la URL de ACS completa para tu instancia de {% data variables.product.prodname_ghe_server %}. Por ejemplo, `https://ghe.corp.example.com/saml/consume`. + +#### Error: "SAML Response is not signed or has been modified" + +Si tu IdP no firma la respuesta de SAML, o si la firma no empata con el contenido, se mostrará el siguiente mensaje de error en la bitácora de autenticación. + +``` +SAML Response is not signed or has been modified. +``` + +Asegúrate de haber configurado aserciones firmadas para la aplicación de {% data variables.product.prodname_ghe_server %} en tu IdP. + +#### Error: "Audience is invalid" or "No assertion found" + +Si la respuesta del IdP carece o tiene un valor incorrecto para `Audience`, se mostrará el siguiente mensaje de error en la bitácora de autenticación. + +```shell +La audiencia es no válida. Audience attribute does not match https://YOUR-INSTANCE-URL +``` + +Asegúrate de haber configurado el valor para `Audience` en tu IdP como la `EntityId` para tu instancia de {% data variables.product.prodname_ghe_server %}, la cual es la URL completa para tu instancia de {% data variables.product.prodname_ghe_server %}. Por ejemplo, `https://ghe.corp.example.com`. diff --git a/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md new file mode 100644 index 0000000000000..b1b42b95f5988 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md @@ -0,0 +1,31 @@ +--- +title: Acerca de la configuración empresarial +intro: 'Puedes utilizar el panel de administrador de sitio{% if enterpriseServerVersions contains currentVersion %}, {% data variables.enterprise.management_console %}, y el shell administrativo (SSH) {% elsif currentVersion == "github-ae@latest" %} y la configuración empresarial o contactar a soporte{% endif %} para administrar tu empresa.' +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %} Para obtener más información, consulta la sección "[Panel de administrador de sitio](/admin/configuration/site-admin-dashboard)". + +{% data reusables.enterprise_site_admin_settings.about-the-management-console %} Para obtener más información, consulta la sección "[Acceder a la consola de administración](/admin/configuration/accessing-the-management-console)". + +{% data reusables.enterprise_site_admin_settings.about-ssh-access %} Para obtener más información, consulta la sección "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +La primera vez que accedes a tu empresa, completarás una configuración inicial para hacer que +{% data variables.product.product_name %} esté listo para utilizarse. Esta configuración inicial incluye el conectarse a tu empresa con un IdP, autenticarse con el SSO de SAML, y configurar las políticas para los repositorios y organizaciones en tu empresa. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". + +Para que los usuarios reciban cualquier tipo de correo electrónico de {% data variables.product.product_name %} después de la configuración inicial, debes pedir a {% data variables.contact.github_support %} que configure la compatibilidad con el correo electrónico externo con tu servidor de SMTP. Para obtener más información, consulta la sección "[Configurar las notificaciones de correo electrónico](/admin/configuration/configuring-email-for-notifications)". + +Posteriormente, puedes utilizar el panel de administrador de sitio y la configuración empresarial para seguir configurando tu empresa, administrar usuarios, organizaciones y repositorios, y para configurar políticas que reducen los riesgos e incrementan la calidad. + +Todas las empresas se configuran con aislamiento de subdominios y compatibilidad con TLS 1.2 y superior únicamente para el tráfico cifrado. +{% endif %} + +### Further reading + +- "[Administrar usuarios, organizaciones y repositorios](/admin/user-management)" +- "[Configurar políticas para tu empresa](/admin/policies)" diff --git a/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md new file mode 100644 index 0000000000000..384ac19598415 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md @@ -0,0 +1,72 @@ +--- +title: Acceder al shell administrativo (SSH) +redirect_from: + - /enterprise/admin/articles/ssh-access/ + - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access/ + - /enterprise/admin/guides/installation/administrative-shell-ssh-access/ + - /enterprise/admin/articles/troubleshooting-ssh-permission-denied-publickey/ + - /enterprise/admin/2.13/articles/troubleshooting-ssh-permission-denied-publickey/ + - /enterprise/admin/2.14/articles/troubleshooting-ssh-permission-denied-publickey/ + - /enterprise/admin/2.15/articles/troubleshooting-ssh-permission-denied-publickey/ + - /enterprise/admin/installation/accessing-the-administrative-shell-ssh + - /enterprise/admin/configuration/accessing-the-administrative-shell-ssh +intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}' +versions: + enterprise-server: '*' +--- + +### Acerca del acceso al shell administrativo + +Si tienes acceso SSH al shell administrativo, puedes ejecutar las utilidades de la línea de comando del {% data variables.product.prodname_ghe_server %}. El acceso SSH también es útil para la solución de problemas, para ejecutar copias de seguridad y para configurar la replicación. El acceso SSH administrativo se administra por separado desde el acceso SSH de Git y es accesible solo desde el puerto 122. + +### Habilitar el acceso al shell administrativo por medio de SSH + +Para habilitar el acceso SSH administrativo, debes agregar tu llave pública SSH a tu lista de llaves autorizadas de la instancia. + +{% tip %} + +**Consejo:** Los cambios en las claves SSH entran en vigor de inmediato. + +{% endtip %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. En "SSH access" (Acceso SSH), pega tu clave en el cuadro de texto, luego haz clic en **Add key** (Agregar clave). ![Cuadro te texto y botón para agregar una clave SSH](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Conectarse con el shell administrativo por SSH + +Después de que hayas agregado tu clave SSH a la lista, conéctate a la instancia por SSH como el usuario `admin` en el puerto 122. + +```shell +$ ssh -p 122 admin@github.example.com +Último inicio de sesión: dom 9 de nov 07:53:29 2014 desde 169.254.1.1 +admin@github-example-com:~$ █ +``` + +#### Solucionar problemas de conexión al SSH + +Si te encuentras con el error `Permiso denegado (publickey)` cuando intentas conectarte a {% data variables.product.product_location %} por medio de SSH, confirma que te estés conectando por el puerto 122. Puede que debas especificar de manera explícita qué clave SSH privada utilizar. + +Para especificar una clave SSH utilizando la línea de comando, ejecuta `ssh` con el argumento `-i`. + +```shell +ssh -i /path/to/ghe_private_key -p 122 admin@hostname +``` + +También puedes especificar una clave SSH privada utilizando el archivo de configuración de SSH (`~/.ssh/config`). + +```shell +Host hostname + IdentityFile /path/to/ghe_private_key + Usuario Admin + Puerto 122 +``` + +### Acceder al shell administrativo utilizando la consola local + +En una situación de emergencia, por ejemplo, si el SSH no está disponible, puedes acceder al shell administrativo de manera local. Inicia sesión como usuario `admin` y utiliza la contraseña establecida durante la configuración inicial de {% data variables.product.prodname_ghe_server %}. + +### Limitaciones de acceso al shell administrativo + +El acceso al shell administrativo se permite solo para la solución de problemas y para realizar procedimientos de operaciones documentadas. Si modificas archivos del sistema y de la aplicación, ejecutas programas o instalas paquetes de software incompatibles se puede invalidar tu contrato de asistencia. Contáctate con {% data variables.contact.contact_ent_support %} si tienes alguna pregunta acerca de las actividades que permite tu contrato de asistencia. diff --git a/translations/es-ES/content/admin/configuration/accessing-the-management-console.md b/translations/es-ES/content/admin/configuration/accessing-the-management-console.md new file mode 100644 index 0000000000000..4071e71be871c --- /dev/null +++ b/translations/es-ES/content/admin/configuration/accessing-the-management-console.md @@ -0,0 +1,50 @@ +--- +title: Acceder a la consola de administración +intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}' +redirect_from: + - /enterprise/admin/articles/about-the-management-console/ + - /enterprise/admin/articles/management-console-for-emergency-recovery/ + - /enterprise/admin/articles/web-based-management-console/ + - /enterprise/admin/categories/management-console/ + - /enterprise/admin/articles/accessing-the-management-console/ + - /enterprise/admin/guides/installation/web-based-management-console/ + - /enterprise/admin/installation/accessing-the-management-console + - /enterprise/admin/configuration/accessing-the-management-console +versions: + enterprise-server: '*' +--- + +### Acerca de {% data variables.enterprise.management_console %} + +Utiliza {% data variables.enterprise.management_console %} para las actividades administrativas básicas: +- **Configuración inicial**: Atraviesa el proceso de configuración inicial durante el primer lanzamiento {% data variables.product.product_location %} visitando la dirección IP de {% data variables.product.product_location %} en tu navegador. +- **Establecer configuraciones básicas para tu instancia**: Configura DNS, nombre del host, SSL, autenticación de usuario, correo electrónico, servicios de monitoreo y redireccionamiento de registro en la página de Configuraciones. +- **Programar ventanas de mantenimiento**: Trabaja sin conexión en tu {% data variables.product.product_location %} mientras realizas mantenimiento con {% data variables.enterprise.management_console %} o el shell administrativo. +- **Solucionar problemas**: Genera un paquete de soporte o visualiza la información de diagnóstico de alto nivel. +- **Administración de licencias**: Visualiza o actualiza tu licencia {% data variables.product.prodname_enterprise %}. + +También puedes acceder a {% data variables.enterprise.management_console %} utilizando la dirección IP de {% data variables.product.product_location %}, incluso cuando la instancia se encuentre en modo de mantenimiento o si ocurre una falla crítica en la aplicación o si están mal configurados el nombre del host o la SSL. + +Para acceder a {% data variables.enterprise.management_console %}, debes utilizar la contraseña de administrador establecida durante la configuración inicial de {% data variables.product.product_location %}. También debes poder conectarte con el host de la máquina virtual en el puerto 8443. Si tienes problemas para acceder a {% data variables.enterprise.management_console %}, controla las configuraciones del firewall intermedio y del grupo de seguridad. + +### Acceder a la {% data variables.enterprise.management_console %} como administrador del sitio + +La primera vez que accedas a la {% data variables.enterprise.management_console %} como administrador de sitio, deberás cargar tu archivo de licencia de {% data variables.product.prodname_enterprise %} para autenticarte en la app. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license)". + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} + +### Acceder a {% data variables.enterprise.management_console %} como usuario sin autenticación + +1. Visita esta URL en tu navegador, reemplazando el `nombre del host` por tu nombre del host o tu dirección IP actuales {% data variables.product.prodname_ghe_server %}: + ```shell + http(s)://HOSTNAME/setup + ``` +{% data reusables.enterprise_management_console.type-management-console-password %} + +### Desbloquear {% data variables.enterprise.management_console %} después de los intentos de inicio de sesión fallidos + +Los bloqueos de la {% data variables.enterprise.management_console %} después de diez intentos de inicio de sesión fallidos se hacen en el transcurso de diez minutos. Debes esperar para que la pantalla de inicio de sesión se desbloquee automáticamente antes de intentar iniciar sesión nuevamente. La pantalla de inicio de sesión se desbloquea automáticamente siempre que el período de diez minutos previo contenga menos de diez intentos de inicio de sesión fallidos. El contador se reinicia después de que ocurra un inicio de sesión exitoso. + +Para desbloquear de inmediato la {% data variables.enterprise.management_console %}, utilice el comando `ghe-reactivate-admin-login` a través del shell administrativo. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." diff --git a/translations/es-ES/content/admin/configuration/command-line-utilities.md b/translations/es-ES/content/admin/configuration/command-line-utilities.md new file mode 100644 index 0000000000000..2a56337bca88e --- /dev/null +++ b/translations/es-ES/content/admin/configuration/command-line-utilities.md @@ -0,0 +1,821 @@ +--- +title: Utilidades de la línea de comando +intro: '{% data variables.product.prodname_ghe_server %} incluye una gama de utilidades para ayudar a resolver problemas particulares o realizar tareas específicas.' +redirect_from: + - /enterprise/admin/articles/viewing-all-services/ + - /enterprise/admin/articles/command-line-utilities/ + - /enterprise/admin/installation/command-line-utilities + - /enterprise/admin/configuration/command-line-utilities +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '*' +--- + +Puedes ejecutar estos comandos desde cualquier lugar en la VM después de iniciar sesión como usuario administrador de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." + +### General + +#### ghe-announce + +Esta utilidad establece un mensaje emergente en la parte superior de cada página {% data variables.product.prodname_enterprise %}. Puedes usarlo para difundir un mensaje entre tus usuarios. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} +También puedes configurar un letrero de anuncio utilizando la configuración empresarial en +{% data variables.product.product_name %}. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)." +{% endif %} + +```shell +# Establece un mensaje que es visible para todos +$ ghe-announce -s MESSAGE +> Mensaje de anuncio establecido. +# Elimina un mensaje establecido previamente +$ ghe-announce -u +> Eliminó el mensaje de anuncio +``` + +#### ghe-check-disk-usage + +Esta utilidad busca en el disco los archivos grandes o los archivos que se han eliminado, pero siguen teniendo identificadores de archivo abiertos. Esto se debería ejecutar cuando intentes liberar espacio en la partición raíz. + +```shell +ghe-check-disk-usage +``` + +#### ghe-cleanup-caches + +Esta utilidad borra una variedad de cachés que podrían ocupar espacio extra del disco en el volumen raíz. Si notas que el uso del espacio de disco del volumen raíz aumenta de manera considerable, sería buena idea ejecutar esta utilidad para ver si ayuda a reducir el uso general. + +```shell +ghe-cleanup-caches +``` +#### ghe-cleanup-settings + +Esta utilidad borra todas las configuraciones {% data variables.enterprise.management_console %} existentes. + +{% tip %} + +**Consejo**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} + +{% endtip %} + +```shell +ghe-cleanup-settings +``` + +#### ghe-config + +Con esta utilidad, puedes recuperar y modificar los ajustes de configuración de {% data variables.product.product_location %}. + +```shell +$ ghe-config core.github-hostname +# Obtiene el valor de configuración de `core.github-hostname` +$ ghe-config core.github-hostname 'example.com' +# Establece el valor de configuración de `core.github-hostname` en `example.com` +$ ghe-config -l +# Detalla todos los valores de configuración +``` +Te permite encontrar el uuid de tu nodo en `cluster.conf`. + +``` shell + $ ghe-config _hostname_.uuid +``` + +{% if currentVersion ver_gt "enterprise-server@2.21" %} +Te permite eximir una lista de usuarios de los límites de tasa de la API. Para obtener más información, consulta la sección "[Limites de tasa](/enterprise/{{ page.version }}/v3/#rate-limiting)." + +``` shell +$ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions" +# Exempts the users hubot and github-actions from rate limits +``` +{% endif %} + +#### ghe-config-apply + +Esta utilidad aplica configuraciones {% data variables.enterprise.management_console %}, vuelve a cargar servicios del sistema, prepara un dispositivo de almacenamiento y ejecuta cualquier migración de base de datos pendiente. Es equivalente a dar clic en **Guardar configuración** en la IU web de {% data variables.enterprise.management_console %} o a enviar una solicitud de POST a [la terminal `/setup/api/configure`](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console). + +Probablemente, nunca la debas ejecutar en forma manual, pero está disponible si quieres automatizar el proceso de guardar tus configuraciones a través de SSH. + +```shell +ghe-config-apply +``` + +#### ghe-console + +Esta utilidad abre la consola GitHub Rails en tu aparato {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} + +```shell +ghe-console +``` + +#### ghe-dbconsole + +Esta utilidad abre una sesión de base de datos de MySQL en tu aparato {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} + +```shell +ghe-dbconsole +``` + +#### ghe-es-index-status +Esta utilidad genera un resumen de los índices de Elasticsearch en formato CSV. + +Imprime un resumen de los índices con un encabezado para `STDOUT`: +```shell +$ ghe-es-index-status -do +> warning: parser/current is loading parser/ruby23, which recognizes +> warning: 2.3.3-compliant syntax, but you are running 2.3.4. +> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri. +> Name,Primary,Searchable,Writable,UpToDate,RepairProgress,Version +> code-search-1,true,true,true,true,100.0,72e27df7c631b45e026b42bfef059328fa040e17 +> commits-5,true,true,true,true,100.0,7ed28813100c47813ef654c0ee2bb9abf21ab744 +> gists-4,true,true,true,true,100.0,cf8e7d04fcf2564c902e2873c424a279cc41079d +> issues-4,false,false,false,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76 +> issues-5,true,true,true,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76 +> projects-2,true,true,true,true,100.0,c5cac1c4b3c66d42e609d088d174dbc3dd44469a +> pull-requests-6,true,true,true,true,100.0,6a466ad6b896a3499509990979bf9a18d7d41de3 +> repos-6,true,true,true,true,100.0,6c8b5fbba0fc1e409558db411d05e092c1387082 +> users-5,true,true,true,true,100.0,38984875552bb826c9ec42999f409cb2e95556eb +> wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234 +``` + +Imprime un resumen de los índices y canaliza los resultados en `columnas` para mejor legibilidad: + +```shell +$ ghe-es-index-status -do | column -ts, +> warning: parser/current is loading parser/ruby23, which recognizes +> warning: 2.3.3-compliant syntax, but you are running 2.3.4. +> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri. +> Nombre Principal Se puede buscar Editable Actualizado Avance reparación Versión +> code-search-1 true true true true 100.0 72e27df7c631b45e026b42bfef059328fa040e17 +> commits-5 true true true true 100.0 7ed28813100c47813ef654c0ee2bb9abf21ab744 +> gists-4 true true true true 100.0 cf8e7d04fcf2564c902e2873c424a279cc41079d +> issues-4 falso falso falso true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76 +> issues-5 true true true true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76 +> projects-2 true true true true 100.0 c5cac1c4b3c66d42e609d088d174dbc3dd44469a +> pull-requests-6 true true true true 100.0 6a466ad6b896a3499509990979bf9a18d7d41de3 +> repos-6 true true true true 100.0 6c8b5fbba0fc1e409558db411d05e092c1387082 +> users-5 true true true true 100.0 38984875552bb826c9ec42999f409cb2e95556eb +> wikis-4 true true true true 100.0 2613dec44bd14e14577803ac1f9e4b7e07a7c234 +``` + +#### ghe-legacy-github-services-report + +Esta utilidad enumera los repositorios de tu aparato que usan Servicios {% data variables.product.prodname_dotcom %}, un método de integración que se interrumpirá el 1 de octubre de 2018. Los usuarios de tu aparato pueden tener configurados servicios {% data variables.product.prodname_dotcom %} para crear notificaciones de subidas a determinados repositorios. Para obtener más información, consulta la sección "[Anunciar la obsoletización de servicios de {% data variables.product.prodname_dotcom %} ](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" en {% data variables.product.prodname_blog %} o la sección "[Reemplazar servicios de {% data variables.product.prodname_dotcom %}](/developers/overview/replacing-github-services)". Para obtener más información acerca de este comando o para conocer otras opciones, utiliza la marca `-h`. + +```shell +ghe-legacy-github-services-report + +``` + +#### ghe-logs-tail + +Esta utilidad te permite hacer un registro final de todos los archivos de registro relevantes desde tu instalación. Puedes aprobar opciones para limitar los registros a conjuntos específicos. Utiliza la marca -h para más opciones. + +```shell +ghe-logs-tail +``` + +#### ghe-maintenance + +Esta utilidad te permite controlar el estado del modo de mantenimiento de la instalación. Está diseñada para que la use principalmente la {% data variables.enterprise.management_console %} en segundo plano, pero también se puede usar directamente. + +```shell +ghe-maintenance -h +``` + +#### ghe-motd + +Esta utilidad vuelve a mostrar el mensaje del día (MOTD) en el que los administradores ven cuando se accede a la isntancia a través del shell administrativo. El resultado contiene un resumen del estado de la instancia. + +```shell +ghe-motd +``` + +#### ghe-nwo + +Esta utilidad genera un nombre y propietario de repositorio en función del Id. del repositorio. + +```shell +ghe-nwo REPOSITORY_ID +``` + +#### ghe-org-admin-promote + +Usa este comando para otorgarles privilegios de propietario de la organización a los usuarios con privilegios de administrador del sitio sobre el aparato o para otorgarle privilegios de propietario de la organización a cualquier usuario único de una organización única. Debes especificar un usuario o una organización. El comando `ghe-org-admin-promote` siempre pedirá confirmación antes de ejecutarse, a menos que uses la marca `-y` para omitir la confirmación. + +Puedes usar las siguientes opciones con la utilidad: + +- La marca `-u` especifica un nombre de usuario. Usa esta marca para otorgarle privilegios de propietario de la organización a un usuario específico. Omite la marca `-u` para promover todos los administradores del sitio a la organización específica. +- La marca `-o` especifica una organización. Usa esta marca para otorgar privilegios de propietario en una organización específica. Omite la marca `-o` para otorgarle permisos de propietario en todas las organizaciones al administrador del sitio especificado. +- La marca `-a` otorga privilegios de propietario en todas las organizaciones a todos los administradores del sitio. +- La marca `-y` omite la confirmación manual. + +Esta utilidad no puede promover una cuenta de usuario que no sea administrador del sitio a propietario de todas las organizaciones. Puedes promover una cuenta de usuario común a administrador del sitio con [ghe-user-promote](#ghe-user-promote). + +Otorga privilegios de propietario de la organización en una organización específica a un usuario único + +```shell +ghe-org-admin-promote -u USERNAME -o ORGANIZATION +``` + +Otorga privilegios de propietario de la organización en todas las organizaciones a un administrador del sitio específico + +```shell +ghe-org-admin-promote -u USERNAME +``` + +Otorga privilegios de propietario de la organización en una organización específica a todos los administradores del sitio + +```shell +ghe-org-admin-promote -o ORGANIZATION +``` + +Otorga privilegios de propietario de la organización en todas las organizaciones a todos los administradores del sitio + +```shell +ghe-org-admin-promote -a +``` + +#### ghe-reactivate-admin-login + +Usa este comando para desbloquear de inmediato la {% data variables.enterprise.management_console %} después de 10 intentos fallidos de inicio de sesión en el transcurso de 10 minutos. + +```shell +$ ghe-reactivate-admin-login +``` + +#### ghe-resque-info + +Esta utilidad muestra información sobre los trabajos en segundo plano, tanto activos como en cola. Proporciona las mismas cantidades de recuento de trabajos que la barra de estado del administrador que aparece en la parte superior de cada página. + +Esta utilidad puede ayudar a identificar si el servidor Resque está teniendo problemas para procesar los trabajos de segundo plano. Cualquiera de los siguientes escenarios puede ser indicativo de un problema con Reque: + +* Aumenta la cantidad de trabajos de segundo plano, pero los trabajos activos siguen siendo los mismos. +* Las fuentes de eventos no se actualizan. +* Los webhooks no se están activando. +* La interfaz web no se actualiza después de una subida de Git. + +Si sospechas que Resque está fallando, contáctate con {% data variables.contact.contact_ent_support %} para obtener ayuda. + +Con este comando, también puedes detener o reanudar los trabajos en cola. + +```shell +$ ghe-resque-info +# detalla las colas y la cantidad de trabajos actualmente en cola +$ ghe-resque-info -p QUEUE +# detiene la cola especificada +$ ghe-resque-info -r QUEUE +# reanuda la cola especificada +``` + +#### ghe-saml-mapping-csv + +Esta utilidad puede ayudar a mapear los registros de SAML. + +Para crear un archivo CSV que contenga todo el mapeo de SAML para tus usuarios de {% data variables.product.product_name %}: +```shell +$ ghe-saml-mapping-csv -d +``` + +Para realizar una simulación de actualización de mapeo de SAML con nuevos valores: +```shell +$ ghe-saml-mapping-csv -u -n -f /path/to/file +``` + +Para actualizar el mapeo de SAML con nuevos valores: +```shell +$ ghe-saml-mapping-csv -u -f /path/to/file +``` + +#### ghe-service-list + +Esta utilidad enumera todos los servicios que se han iniciado o detenido (en ejecución o en espera) en tu aparato. + +```shell +$ ghe-service-list +start/running + - github-resqued, process 12711 + - github-unicorn, process 12726 + - github-gitauth, process 12743 + - git-daemon, process 12755 + - babeld, process 12771 + - github-svn-proxy, process 12802 + - gist-unicorn, process 12832 + - gist-resqued, process 12881 + - render-unicorn, process 12939 + - hookshot-unicorn, process 13076 + - nodeload2, process 13192 + - slumlord-unicorn, process 13304 + - ghe-storage, process 2012 + - enterprise-manage-unicorn, process 2024 + - enterprise-manage-resque, process 2053 + +stop/waiting + - ghe-replica-mode +``` + +{% tip %} + +Los nombres de servicio que se generen con este comando se pueden utilizar con comandos [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) para detener, iniciar o restablecer estos servicios manualmente si así se requiere. Por ejemplo: + +```shell +$ sudo systemctl restart github-resqued +``` + +Detener los servicios generará un tiempo de inactividad en tu instalación, así que recomendamos que te contactes con {% data variables.contact.contact_ent_support %} antes de detener o reiniciar cualquier servicio. + +{% endtip %} + +#### ghe-set-password + +Con `ghe-set-password`, puedes establecer una contraseña nueva para autenticarla en la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). + +```shell +ghe-set-password +``` + +#### ghe-ssh-check-host-keys + +Esta utilidad compara las claves del host de SSH existentes con la lista de claves del host de SHH filtradas conocidas. + +```shell +$ ghe-ssh-check-host-keys +``` + +Si se encuentra una clave del host filtrada, se cierra la utilidad en un estado `1` y con un mensaje: +```shell +> Una o más de tus claves del host de SHH aparecen en la lista negra. +> Restablece tus claves del host usando ghe-ssh-roll-host-keys. +``` + +Si no se encontró una clave del host filtrada, se cierra la utilidad en un estado `0` y con un mensaje: +```shell +> Las claves del host de SSH no se encontraron en la lista negra de claves del host de SSH. +> No se requieren/recomiendan más pasos en este momento. +``` + +#### ghe-ssh-roll-host-keys + +Esta utilidad rota las claves del host de SSH y las reemplaza con claves que se generan nuevas. + +```shell +$ sudo ghe-ssh-roll-host-keys +¿Quieres proceder con la rotación de claves del host de SSH? Esto eliminará las +las claves existentes en /etc/ssh/ssh_host_* y generará nuevas. [y/N] + +# Presiona 'Y' para confirmar la eliminación o utiliza el modificador -y para omitir esta pregunta + +> Las claves del host de SSH se han rotado con éxito. +``` + +#### ghe-ssh-weak-fingerprints + +Esta utilidad genera un informe de claves de SSH débiles conocidas que están almacenadas en el aparato {% data variables.product.prodname_enterprise %}. Opcionalmente, puedes revocar las claves de usuario como acción masiva. La utilidad informará las claves de sistema débiles que puedes revocar en forma manual en la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). + +```shell +# Imprime un informe de usuario y claves SSH del sistema débiles +$ ghe-ssh-weak-fingerprints + +# Revoca todas las claves de usuario débiles +$ ghe-ssh-weak-fingerprints --revoke +``` + +#### ghe-ssl-acme + +Esta utilidad te permite instalar un certificado de Let's Encrypt en tu aparato {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." + +Puede utilizar la etiqueta `-x` para eliminar la configuración ACME. + +```shell +ghe-ssl-acme -e +``` + +#### ghe-ssl-ca-certificate-install + +Esta utilidad te termine instalar un certificado CA de raíz personalizado en tu servidor {% data variables.product.prodname_enterprise %}. El certificado debe tener un formato PEM. Además, si tu proveedor de certificación incluye varios certificados CA en un único archivo, debes separarlos en archivos individuales que luego pasarás a `ghe-ssl-ca-certificate-install` de a uno por vez. + +Ejecuta esta utilidad para agregar una cadena de certificación para la verificación de firma de confirmación S/MIME. Para obtener más información, consulta "[Acerca de la verificación de firma de confirmación](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)." + +Ejecuta esta utilidad cuando {% data variables.product.product_location %} no pueda conectarse con otro servidor porque el segundo está usando un certificado SSL autofirmado o un certificado SSL para el cual no proporciona el paquete de soporte CA necesario. Una manera de confirmar esto es ejecutar `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` desde {% data variables.product.product_location %}. Si el certificado SSL del servidor remoto se puede verificar, tu `SSL-Session` debe tener un código de retorno de 0, como se muestra a continuación. + +``` +SSL-Session: + Protocol : TLSv1 + Cipher : AES128-SHA + Session-ID: C794EBCC3CBC10F747C9AFC029C03C1048FC99CFC34D13D7444E0F267C58DF4C + Session-ID-ctx: + Master-Key: 02A7C47CFD6EEC87D3C710E9DD87390E04EF82DDD7514AE03127D5DC1945FC0CAEFB5395791AEA598667EFA61B9EA8C5 + Key-Arg : None + Start Time: 1394581597 + Timeout : 300 (sec) + Verify return code: 0 (ok) +``` + +Si por el contrario, el certificado SSL del servidor remoto *no* se puede verificar, entonces tu `SSL-Session` debe tener un código de retorno distinto a cero: + +``` +SSL-Session: + Protocol : TLSv1 + Cipher : AES128-SHA + Session-ID: 82CB288051A6DB66094C50A69CF1292AEE7E54C6B01B659B98AB336F8C33863E + Session-ID-ctx: + Master-Key: 01B025B2F764043A27919A8D1355AAECD8844FF0831B1D664042334790574A6F4025BAB085D4ED71D71AAB3091B849E5 + Key-Arg : None + Start Time: 1394581782 + Timeout : 300 (sec) + Verify return code: 27 (certificate not trusted) +``` + +Puedes usar estas opciones adicionales con la utilidad: +- La marca `-r` te permite desinstalar un certificado CA. +- La marca `-h` muestra más información de uso. + +```shell +ghe-ssl-ca-certificate-install -c /path/to/certificate +``` + +#### ghe-ssl-generate-csr + +Esta utilidad te permite generar una clave privada y una solicitud de firma de certificado (CSR), que puedes compartir con una autoridad de certificación comercial o privada para obtener un certificado válido para utilizar con tu instancia. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." + +Para obtener más información acerca de este comando o para conocer otras opciones, utiliza la marca `-h`. + +```shell +ghe-ssl-generate-csr +``` + +#### ghe-storage-extend + +Algunas plataformas exigen este script para ampliar el volumen de usuarios. Para obtener más información, consulta "[Aumentar la capacidad de almacenamiento](/enterprise/admin/guides/installation/increasing-storage-capacity/)". + +```shell +$ ghe-storage-extend +``` + +#### ghe-version + +Esta utilidad imprime la versión, la plataforma y la compilación de {% data variables.product.product_location %}. + +```shell +$ ghe-version +``` + +#### ghe-webhook-logs + +Esta utilidad genera registros de entregas de webhooks para que los administradores los revisen e identifiquen cualquier problema. + +```shell +ghe-webhook-logs +``` + +Para mostrar todas las entregas fallidas del gancho en el día anterior: +{% if currentVersion ver_gt "enterprise-server@2.22" %} +```shell +ghe-webhook-logs -f -a YYYY-MM-DD +``` + +El formato de fecha debe ser `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, o `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} +```shell +ghe-webhook-logs -f -a YYYYMMDD +``` +{% endif %} + +Para mostrar todos los resultados, carga útil y excepciones del gancho para la entrega: +```shell +ghe-webhook-logs -g delivery-guid -v +``` + +### Agrupación + +#### estado ghe-dpages + +Esta utilidad le permite gestionar el servidor {% data variables.product.prodname_pages %} distribuido. + +```shell +$ ghe-cluster-status +``` + +#### ghe-cluster-support-bundle + +Esta utilidad crea un tarball de paquetes de soporte que contiene registros importantes de cada nodo, tanto en la configuración de Replicación geográfica como de Agrupación. + +Por defecto, el comando crea el tarball en */tmp*, pero también puedes tener `cat` el tarball en `STDOUT` para una fácil transmisión por SSH. Esto es útil en caso de que la UI web no responda o que no funcione descargar un paquete de soporte desde */setup/support*. Debes usar este comando si quieres generar un paquete *ampliado* que contenga registros antiguos. También puedes usar este comando para cargar el paquete de soporte de agrupación directamente para {% data variables.product.prodname_enterprise %} recibir asistencia. + +Para crear un paquete estándar: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz +``` + +Para crear un paquete extendido: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz +``` + +Para mandar un paquete a {% data variables.contact.github_support %}: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -u' +``` + +Para mandar un paquete a {% data variables.contact.github_support %} y asociarlo con un ticket: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -t ticket-id' +``` + +{% if currentVersion ver_gt "enterprise-server@2.21" %} +#### ghe-cluster-failover + +Recuperación de fallos de los nodos de clúster activos a los pasivos. Para obtener más información, consulta la sección "[Iniciar una respuesta ante los fallos para tu clúster de réplica](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)". + +```shell +ghe-cluster-failover +``` +{% endif %} + +#### ghe-dpages + +Esta utilidad le permite gestionar el servidor {% data variables.product.prodname_pages %} distribuido. + +```shell +ghe-dpages +``` + +Para mostrar un resumen de la ubicación y salud del repositorio: +```shell +estado ghe-dpages +``` + +Para evacuar un servicio de almacenamiento {% data variables.product.prodname_pages %} antes de evacuar un nodo de agrupación: +``` shell +ghe-dpages evacuate pages-server- +``` + +#### ghe-spokes + +Esta utilidad te permite administrar las tres copias de cada repositorio en los servidores de git distribuidos. + +```shell +ghe-spokes +``` + +Para mostrar un resumen de la ubicación y salud del repositorio: + +```shell +estado ghe-spokes +``` + +Para mostrar los servidores en donde el repositorio se encuentra almacenado: + +```shell +ruta ghe-spokes +``` + +Para evacuar los servicios de almacenamiento en un nodo de la agrupación: + +``` shell +ghe-spokes server evacuate git-server- +``` + +#### ghe-storage + +Esta utilidad te permite evacuar todos los servicios de almacenamiento antes de evacuar un nodo de agrupación. + +``` shell +ghe-storage evacuate storage-server- +``` + +### Git + +#### ghe-btop + +Una interfaz del tipo `top` para las operaciones actuales de Git. + +```shell +ghe-btop [ | --help | --usage ] +``` + +#### ghe-repo + +Esta utilidad te permite cambiar a un directorio del repositorio y abrir un shell interactivo como el de usuario de `git`. Puedes realizar inspecciones o mantenimientos manuales de un repositorio a través de comandos como `git-*` o `git-nw-*`. + +```shell +ghe-repo username/reponame +``` + +#### ghe-repo-gc + +Esta utilidad reempaqueta en forma manual una red de repositorios para optimizar el almacenamiento de paquetes. Si tienes un repositorio grande, ejecutar este comando puede ayudar a reducir su tamaño general. {% data variables.product.prodname_enterprise %} ejecuta en forma automática este comando durante toda tu interacción con una red de repositorios. + +Puedes agregar el argumento opcional `--prune` para eliminar los objetos de Git inaccesibles que no están referenciados desde una rama, una etiqueta o cualquier otra referencia. Esto es útil, en especial, para eliminar de inmediato [información sensible previamente suprimida](/enterprise/user/articles/remove-sensitive-data/). + +```shell +ghe-repo-gc username/reponame +``` + +### Importar y exportar + +#### ghe-migrator + +`ghe-migrator` es una herramienta de alta fidelidad que te ayuda a realizar migraciones desde una instancia de GitHub a otra. Puedes consolidar tus instancias o mover tu organización, usuarios, equipos y repositorios desde GitHub.com a {% data variables.product.prodname_enterprise %}. + +Para obtener más información, consulta nuestra guía en [migrar datos de usuarios, organizaciones y repositorios](/enterprise/admin/guides/migrations/). + +#### git-import-detect + +Con una URL, detecta qué tipo de sistema de administración de control de fuente hay en el otro extremo. Durante una importación manual, probablemente ya lo sepas, pero puede ser muy útil en scripts automáticos. +```shell +git-import-detect +``` + +#### git-import-hg-raw + +Esta utilidad importa un repositorio de Mercurial a este repositorio de Git. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." +```shell +git-import-hg-raw +``` + +#### git-import-svn-raw + +Esta utilidad importa los datos del archivo y el historial de Subversion en una rama de Git. Es una copia exacta del árbol, que ignora cualquier distinción de tronco o rama. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." +```shell +git-import-svn-raw +``` + +#### git-import-tfs-raw + +Esta utilidad importa desde el Control de Versiones de Team Foundation. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." +```shell +git-import-tfs-raw +``` + +#### git-import-rewrite + +Esta utilidad reescribe el repositorio importado. Esto te permite renombrar a los autores y, en el caso de TFS y Subversion, produce ramas de Git basadas en carpetas. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." +```shell +git-import-rewrite +``` + +### Asistencia + +#### ghe-diagnostics + +Esta utilidad realiza varias comprobaciones y reúne información acerca de tu instalación que puedes enviar a la asistencia para que te ayude a diagnosticar los problemas que tienes. + +Actualmente, el resultado de esta utilidad es similar a descargar la información de diagnóstico en la {% data variables.enterprise.management_console %}, pero con el tiempo se pueden agregar otras mejoras que no están disponibles en la UI web. Para obtener más información, consulta "[Crear y compartir archivos de diagnóstico](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)." + +```shell +ghe-diagnostics +``` + +#### ghe-support-bundle + +{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} +Esta utilidad crea un tarball de paquetes de soporte que contiene registros importantes de tu instancia. + +Por defecto, el comando crea el tarball en */tmp*, pero también puedes tener `cat` el tarball en `STDOUT` para una fácil transmisión por SSH. Esto es útil en caso de que la UI web no responda o que no funcione descargar un paquete de soporte desde */setup/support*. Debes usar este comando si quieres generar un paquete *ampliado* que contenga registros antiguos. También puedes usar este comando para cargar el paquete de soporte directamente para recibir asistencia {% data variables.product.prodname_enterprise %}. + +Para crear un paquete estándar: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz +``` + +Para crear un paquete extendido: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -x -o' > support-bundle.tgz +``` + +Para mandar un paquete a {% data variables.contact.github_support %}: +```shell +$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -u' +``` + +Para mandar un paquete a {% data variables.contact.github_support %} y asociarlo con un ticket: + +```shell +$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -t ticket-id' +``` + +#### ghe-support-upload + +Esta utilidad envía información desde tu aparato para recibir asistencia {% data variables.product.prodname_enterprise %}. Puedes especificar un archivo local u ofrecer una transmisión de hasta 100MB de datos a través de `STDIN`. Opcionalmente, los datos cargados se pueden asociar con un ticket de asistencia. + +Para enviar un archivo a {% data variables.contact.github_support %} y asociarlo con un ticket: +```shell +ghe-support-upload -f path/to/your/file -t ticket-id +``` + +Para subir datos a través de `STDIN` y asociarlos con un ticket: +```shell +ghe-repl-status -vv | ghe-support-upload -t ticket-id -d "Verbose Replication Status" +``` + +En este ejemplo, `ghe-repl-status -vv` envía información de estado detallada desde un aparato réplica. Debes reemplazar `ghe-repl-status -vv` con los datos específicos que quieras transmitir a `STDIN` y `Verbose Replication Status` (Estado de replicación detallado) con una breve descripción de los datos. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} + +### Actualizar {% data variables.product.prodname_ghe_server %} + +#### ghe-upgrade + +Esta utilidad instala o verifica un paquete actualizado. También puedes usar esta utilidad para revertir un lanzamiento de patch si falla o se interrumpe una actualización. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)." + +Para verificar un paquete de mejora: +```shell +ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME +``` + +Para instalar un paquete de mejora: +```shell +ghe-upgrade UPGRADE-PACKAGE-FILENAME +``` + +{% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} + +#### ghe-upgrade-scheduler + +Esta utilidad administra la instalación programada de paquetes de actualización. Puedes mostrar, crear nuevas o eliminar las actualizaciones programadas. Debes crear cronogramas usando expresiones cron. Para obtener más información, consulta [Entrada de Cron en Wikipedia](https://en.wikipedia.org/wiki/Cron#Overview). + +Para programar una nueva instalación para un paquete: +```shell +$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME +``` + +Para mostrar las instalaciones programadas para un paquete: +```shell +$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME +> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 +``` + +Para eliminar las instalaciones programadas para un paquete: +```shell +$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME +``` + +#### ghe-update-check + +Esta utilidad buscará si hay disponible un nuevo lanzamiento de patch de {% data variables.product.prodname_enterprise %}. Si lo hay, y si hay espacio disponible en tu instancia, descargará el paquete. Por defecto, se guarda en */var/lib/ghe-updates*. Luego, un administrador puede [realizar la actualización](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/). + +En */var/lib/ghe-updates/ghe-update-check.status* puedes acceder a un archivo que contiene el estado de la descarga. + +Para buscar el último lanzamiento {% data variables.product.prodname_enterprise %}, usa el modificador `-i`. + +```shell +$ ssh -p 122 admin@hostname -- 'ghe-update-check' +``` + +### Gestión de usuarios + +#### ghe-license-usage + +Esta utilidad exporta una lista de los usuarios de la instalación en formato JSON. Si tu instancia se conecta a {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} utiliza esta información para reportar la información de licencia a {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Conectar {% data variables.product.prodname_ghe_server %} a{% data variables.product.prodname_ghe_cloud %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". + +Predeterminadamente, la lista de usuarios en el JSON resultante se encuentra cifrada. Usa la marca `-h` para obtener más opciones. + +```shell +ghe-license-usage +``` + +#### ghe-org-membership-update + +Esta utilidad aplicará la visibilidad de membresía de la organización predeterminada mostrando todos los miembros de tu instancia. Para obtener más información, consulta la sección "[Configurar la visibilidad para la membrecía de la organización](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)". Las opciones de configuración son `public` o `private`. + +```shell +ghe-org-membership-update --visibility=SETTING +``` + +#### ghe-user-csv + +Esta utilidad exporta una lista de todos los usuarios en la instalación a un formato CSV. El archivo CSV incluye las direcciones de correo electrónico, el tipo de usuario que son (p. ej., administrador, usuario), cuántos repositorios tienen, cuántas claves SSH tienen, la cantidad de membresías a la organización, la última dirección IP que inició sesión, etc. Usa la marca `-h` para obtener más opciones. + +```shell +ghe-user-csv -o > users.csv +``` + +#### ghe-user-demote + +Esta utilidad degrada el usuario especificado desde el estado de administrador al de usuario normal. Recomendamos usar la UI web para realizar esta acción, pero proporcionamos esta utilidad en caso de que la utilidad `ghe-user-promote` se ejecute con error, y debas volver a bajar de categoría a un usuario desde la CLI (interfaz de línea de comandos). + +```shell +ghe-user-demote some-user-name +``` + +#### ghe-user-promote + +Esta utilidad promueve la cuenta de usuario especificada a administrador del sitio. + +```shell +ghe-user-promote some-user-name +``` + +#### ghe-user-suspend + +Esta utilidad suspende el usuario especificado, evitando que inicie sesión, suba o extraiga datos de tu repositorio. + +```shell +ghe-user-suspend some-user-name +``` + +#### ghe-user-unsuspend + +Esta utilidad anula la suspensión del usuario especificado, otorgándole acceso para iniciar sesión, subir o extraer datos de tu repositorio. + +```shell +ghe-user-unsuspend some-user-name +``` diff --git a/translations/es-ES/content/admin/configuration/configuring-a-hostname.md b/translations/es-ES/content/admin/configuration/configuring-a-hostname.md new file mode 100644 index 0000000000000..a9be7c18886a8 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-a-hostname.md @@ -0,0 +1,26 @@ +--- +title: Configurar un nombre del host +intro: Recomendamos establecer un nombre del host para tu aparato en lugar de utilizar una dirección IP codificada de forma rígida. +redirect_from: + - /enterprise/admin/guides/installation/configuring-hostnames/ + - /enterprise/admin/installation/configuring-a-hostname + - /enterprise/admin/configuration/configuring-a-hostname +versions: + enterprise-server: '*' +--- + +Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location %} sin afectar a los usuarios o al software del cliente. + +La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. Por ejemplo, tu configuración de nombre del host podría ser `github.companyname.com.` También recomendamos habilitar el aislamiento de subdominio para el nombre del host elegido a fin de mitigar varias vulnerabilidades del estilo cross-site scripting. Para obtener más información, consulta [Sección 2.1 del HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). + +{% data reusables.enterprise_installation.changing-hostname-not-supported %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Escribe el nombre del host que quieres establecer para {% data variables.product.product_location %}. ![Campo para establecer un nombre del host](/assets/images/enterprise/management-console/hostname-field.png) +5. Para probar las configuraciones de DNS y SSL para el nombre del host nuevo, haz clic en **Configuraciones del dominio de prueba**. ![Botón Test domain settings (Probar configuraciones del dominio)](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} + +Después de configurar un nombre del host, recomendamos que habilites el aislamiento de subdominio para {% data variables.product.product_location %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md new file mode 100644 index 0000000000000..6bf41924b8abb --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md @@ -0,0 +1,11 @@ +--- +title: Configurar las características de seguridad avanzada +shortTitle: Configurar la seguridad avanzada +intro: 'Puedes habilitar o inhabilitar las características de {% data variables.product.prodname_advanced_security %}, tales como el {% data variables.product.prodname_code_scanning %}, en tu instancia.' +mapTopic: verdadero +redirect_from: + - /enterprise/admin/configuration/configuring-advanced-security-features +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md new file mode 100644 index 0000000000000..cfa310d559547 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -0,0 +1,27 @@ +--- +title: Configurar un servidor proxy web fuera de banda +intro: 'Un servidor proxy proporciona otro nivel de seguridad para {% data variables.product.product_location %}.' +redirect_from: + - /enterprise/admin/guides/installation/configuring-a-proxy-server/ + - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server + - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server +versions: + enterprise-server: '*' +--- + +Cuando se habilita un servidor proxy para {% data variables.product.product_location %}, primero {% data variables.product.prodname_ghe_server %} envía mensajes fuera de banda a través del servidor proxy, a menos que el host de destino se agregue como una exclusión de servidor proxy HTTP. Los tipos de mensajes fuera de banda incluyen webhooks salientes, carga de paquetes y extracción de avatares heredados. La URL del servidor proxy es el protocolo, dominio o dirección IP más el número de puerto, por ejemplo `http://127.0.0.1:8123`. + +{% note %} + +**Nota:** Para conectarte a {% data variables.product.product_location %} para {% data variables.product.prodname_dotcom_the_website %}, tu configuración proxy debe permitir la conectividad a `github.com` y a `api.github.com`. Para obtener más información, consulta "[Conectarse a {% data variables.product.prodname_ghe_server %} para {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)." + +{% endnote %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +4. En **Servidor proxy HTTP**, escribe la URL de tu servidor proxy. ![Campo para escribir la URL del servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) + +5. De manera opcional, en **Exclusión de servidor proxy HTTP**, escribe cualquier host que no exija acceso proxy, separando los hosts con comas. Para excluir a todos los hosts en un dominio de que requieran acceso por proxy, puedes utilizar `.` como un prefijo de comodín. Por ejemplo: `.octo-org.tentacle` ![Campo para escribir cualquier Exclusión de Proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/configuring-applications.md b/translations/es-ES/content/admin/configuration/configuring-applications.md new file mode 100644 index 0000000000000..584ba1f39b3da --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-applications.md @@ -0,0 +1,21 @@ +--- +title: Configurar aplicaciones +intro: 'Puedes establecer configuraciones de solicitud interna para {% data variables.product.product_location %}.' +redirect_from: + - /enterprise/admin/installation/configuring-applications + - /enterprise/admin/configuration/configuring-applications +versions: + enterprise-server: '*' +--- + +### Ajustar el almacenamiento en caché de las imágenes + +Puedes elegir la cantidad de tiempo que {% data variables.product.product_location %} almacena en caché los avatares. Cuando aumentas el tiempo de almacenamiento en caché, aumentas la cantidad de tiempo que tardará en cargar el avatar de un usuario. Configurar el tiempo de almacenamiento en caché con un valor demasiado bajo puede sobrecargar {% data variables.product.product_location %} los procesos de trabajo. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de solicitudes de la barra lateral de configuraciones](/assets/images/enterprise/management-console/sidebar-applications.png) +4. Debajo de "Tiempo de caché de imágen de avatar (segundos)", teclea la cantidad de segundos que quisieras que +{% data variables.product.product_location %} guarde en caché para las imágenes de avatar. +![Campo de formulario de almacenamiento en caché de imagen de avatar](/assets/images/enterprise/management-console/add-image-caching-value-field.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md new file mode 100644 index 0000000000000..4a75e8e43cf43 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -0,0 +1,119 @@ +--- +title: Configurar copias de seguridad en tu aparato +redirect_from: + - /enterprise/admin/categories/backups-and-restores/ + - /enterprise/admin/articles/backup-and-recovery/ + - /enterprise/admin/articles/backing-up-github-enterprise/ + - /enterprise/admin/articles/restoring-github-enterprise/ + - /enterprise/admin/articles/backing-up-repository-data/ + - /enterprise/admin/articles/restoring-enterprise-data/ + - /enterprise/admin/articles/restoring-repository-data/ + - /enterprise/admin/articles/backing-up-enterprise-data/ + - /enterprise/admin/guides/installation/backups-and-disaster-recovery/ + - /enterprise/admin/installation/configuring-backups-on-your-appliance + - /enterprise/admin/configuration/configuring-backups-on-your-appliance +intro: 'Como parte de un plan de recuperación ante desastres, puedes proteger los datos de producción en {% data variables.product.product_location %} configurando copias de seguridad automáticas.' +versions: + enterprise-server: '*' +--- + +### Acerca de {% data variables.product.prodname_enterprise_backup_utilities %} + +{% data variables.product.prodname_enterprise_backup_utilities %} es un sistema de copias de seguridad que instalas en un host separado, el cual realiza instantáneas de copias de seguridad de {% data variables.product.product_location %} en intervalos regulares a través de una conexión de red SSH segura. Puedes utilizar una instantánea para restablecer una instancia existente del {% data variables.product.prodname_ghe_server %} a su estado previo desde el host de copias de seguridad. + +Solo se transferirán por la red y ocuparán espacio de almacenamiento físico adicional los datos que se hayan agregado después de esa última instantánea. Para minimizar el impacto en el rendimiento, las copias de seguridad se realizan en línea con la prioridad CPU/IO más baja. No necesitas programar una ventana de mantenimiento para realizar una copia de seguridad. + +Para obtener información más detallada sobre las funciones, los requisitos y el uso avanzado, consulta [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme). + +### Prerrequisitos + +Para utilizar {% data variables.product.prodname_enterprise_backup_utilities %}, debes tener un sistema de host Linux o Unix separado de {% data variables.product.product_location %}. + +También puedes incorporar {% data variables.product.prodname_enterprise_backup_utilities %} en un entorno existente para almacenar los datos críticos de manera permanente y a largo plazo. + +Recomendamos que exista una distancia geográfica entre el host de copias de seguridad y {% data variables.product.product_location %}. Esto asegura que las copias de seguridad estén disponibles para su recuperación en el caso de que ocurra un desastre significativo o una interrupción de red en el sitio principal. + +Los requisitos de almacenamiento físico variarán en función del uso del disco del repositorio de Git y de los patrones de crecimiento esperados: + +| Hardware | Recomendación | +| ------------------ | ---------------------------------------------------------------- | +| **vCPU** | 2 | +| **Memoria** | 2 GB | +| **Almacenamiento** | Cinco veces el almacenamiento asignado de la instancia principal | + +Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas. + +### Instalar {% data variables.product.prodname_enterprise_backup_utilities %} + +{% note %} + +**Nota:** Para asegurar que un aparato recuperado esté disponible de inmediato, realiza copias de seguridad apuntando a la instancia principal, incluso en una configuración de replicación geográfica. + +{% endnote %} + +1. Desgarga el último lanzamiento de [{% data variables.product.prodname_enterprise_backup_utilities %} ](https://github.com/github/backup-utils/releases) y extrae el archivo con el comando `tar`. + ```shell + $ tar -xzvf /path/to/github-backup-utils-vMAJOR.MINOR.PATCH.tar.gz + ``` +2. Copia el archivo incluido `backup.config-example` en `backup.config` y ábrelo en un editor. +3. Configura el valor `GHE_HOSTNAME` al {% data variables.product.prodname_ghe_server %} primario del nombre del host de tu instancia o dirección IP. +4. Configura el valor `GHE_DATA_DIR` en la ubicación del sistema de archivos donde deseas almacenar las instantáneas de copia de seguridad. +5. Abre la página de configuración de tu instancia primaria en `https://HOSTNAME/setup/settings` y agrega la clave SSH del host de copia de seguridad a la lista de claves SSH autorizadas. Para obtener más información, consulta [Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/). +5. Verifica la conectividad SSH con {% data variables.product.product_location %} con el comando `ghe-host-check`. + ```shell + $ bin/ghe-host-check + ``` + 6. Para crear una copia de respaldo completa inicial, ejecuta el comando `ghe-backup`. + ```shell + $ bin/ghe-backup + ``` + +Para obtener más información sobre uso avanzado, consulta el archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). + +### Programar una copia de seguridad + +Puedes programar copias de seguridad regulares en el host de copia de seguridad utilizando el comando `cron(8)` o un servicio de programación de comando similar. La frecuencia de copias de seguridad configurada dictará el peor caso de Punto Objetivo de Recuperación (RPO) de tu plan de recuperación. Por ejemplo, si has programado que la copia de seguridad se ejecute todos los días a la medianoche, podrías perder hasta 24 horas de datos en un escenario de desastre. Recomendamos comenzar con un cronograma de copias de seguridad por hora, que garantice un peor caso máximo de una hora de pérdida de datos, si los datos del sitio principal se destruyen. + +Si los intentos de copias de seguridad se superponen, el comando `ghe-backup` se detendrá con un mensaje de error que indicará la existencia de una copia de seguridad simultánea. Si esto ocurre, recomendamos que disminuyas la frecuencia de tus copias de seguridad programadas. Para obtener más información, consulta la sección "Programar copias de seguridad" del archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#scheduling-backups). + +### Recuperar una copia de seguridad + +En el caso de una interrupción de red prolongada o de un evento catastrófico en el sitio principal, puedes restablecer {% data variables.product.product_location %} proporcionando otro aparato para {% data variables.product.prodname_enterprise %} y haciendo un restablecimiento desde el host de copias de seguridad. Debes agregar la clave SSH del host de copias de seguridad en el aparato objetivo {% data variables.product.prodname_enterprise %} como una clave SSH autorizada antes de restablecer un aparato. + +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Nota:** Si {% data variables.product.product_location %} cuenta con {% data variables.product.prodname_actions %} habilitadas, primero deberás configurar el proveedor de almacenamiento externo de las {% data variables.product.prodname_actions %} en el aplicativo de reemplazo antes de ejecutar el comando `ghe-restore`. Para obtener más información, consulta la sección "[Respaldar y restablecer a {% data variables.product.prodname_ghe_server %} con las {% data variables.product.prodname_actions %} habilitadas](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)". + +{% endnote %} +{% endif %} + +Para restablecer {% data variables.product.product_location %} desde la última instantánea exitosa, usa el comando `ghe-restore`. Debes ver un resultado similar a este: + +```shell +$ ghe-restore -c 169.154.1.1 +> Comprobando claves filtradas en la instantánea de respaldo que se está restableciendo ... +> * No se encontraron claves filtradas +> Conectarse a 169.154.1.1:122 OK (v2.9.0) + +> ADVERTENCIA: Todos los datos del aparato GitHub Enterprise 169.154.1.1 (v2.9.0) +> se sobrescribirán con los datos de la instantánea 20170329T150710. +> Antes de continuar, verifica que sea el host de restauración correcto. +> Escribe 'yes' (sí) para continuar: yes + +> Comenzando la restauración de 169.154.1.1:122 desde la instantánea 20170329T150710 +# ...resultado truncado +> Restauración completa de 169.154.1.1:122 desde la instantánea 20170329T150710 +> Visita https://169.154.1.1/setup/settings para revisar la configuración del aparato. +``` + +{% note %} + +**Nota:** Los ajustes de red están excluidos de la instantánea de copias de seguridad. Debes configurar manualmente la red en el aparato objetivo para el {% data variables.product.prodname_ghe_server %} como obligatoria para tu entorno. + +{% endnote %} + +Puedes utilizar estas otras opciones con el comando `ghe-restore`: +- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. Para obtener más información, consulta la sección "Utilizar una copia de seguridad y restablecer los comandos" de [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands). +- La marca `-s` te permite seleccionar otra instantánea de copias de seguridad. + diff --git a/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md new file mode 100644 index 0000000000000..b59b2d7f35897 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md @@ -0,0 +1,116 @@ +--- +title: Configurar las reglas de firewall incorporado +intro: 'Puedes ver las reglas de firewall predeterminadas y personalizar reglas para {% data variables.product.product_location %}.' +redirect_from: + - /enterprise/admin/guides/installation/configuring-firewall-settings/ + - /enterprise/admin/installation/configuring-built-in-firewall-rules + - /enterprise/admin/configuration/configuring-built-in-firewall-rules +versions: + enterprise-server: '*' +--- + +### Acerca del firewell de {% data variables.product.product_location %} + +{% data variables.product.prodname_ghe_server %} utiliza Ubuntu's Uncomplicated Firewall (UFW) en el aparato virtual. Para obtener más información, consulta "[UFW](https://help.ubuntu.com/community/UFW)" en la documentación de Ubuntu. Con cada lanzamiento, {% data variables.product.prodname_ghe_server %} actualiza automáticamente la lista blanca de los servicios permitidos del firewell. + +Después de que instales {% data variables.product.prodname_ghe_server %}, se abren automáticamente todos los puertos de red obligatorios para aceptar las conexiones. Cada puerto no obligatorio se configura automáticamente en `deny` (rechazar), y la directiva predeterminada resultante se configura en `allow` (permitir). Se habilita el rastreo con estado para todas las conexiones nuevas. Estas suelen ser paquetes de red con el conjunto de bits `SYN`. Para obtener más información, consulta "[Puertos de red](/enterprise/admin/guides/installation/network-ports)." + +El firewall de UFW también abre varios puertos más que son obligatorios para que {% data variables.product.prodname_ghe_server %} funcione correctamente. Para obtener más información sobre el conjunto de reglas de UFW, consulta [el README de UFW](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). + +### Ver las reglas de firewell predeterminadas + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Para ver las reglas de firewall predeterminadas, utiliza el comando `sudo ufw status`. Debes ver un resultado similar a este: + ```shell + $ sudo ufw status + > Status: active + > To Action From + > -- ------ ---- + > ghe-1194 ALLOW Anywhere + > ghe-122 ALLOW Anywhere + > ghe-161 ALLOW Anywhere + > ghe-22 ALLOW Anywhere + > ghe-25 ALLOW Anywhere + > ghe-443 ALLOW Anywhere + > ghe-80 ALLOW Anywhere + > ghe-8080 ALLOW Anywhere + > ghe-8443 ALLOW Anywhere + > ghe-9418 ALLOW Anywhere + > ghe-1194 (v6) ALLOW Anywhere (v6) + > ghe-122 (v6) ALLOW Anywhere (v6) + > ghe-161 (v6) ALLOW Anywhere (v6) + > ghe-22 (v6) ALLOW Anywhere (v6) + > ghe-25 (v6) ALLOW Anywhere (v6) + > ghe-443 (v6) ALLOW Anywhere (v6) + > ghe-80 (v6) ALLOW Anywhere (v6) + > ghe-8080 (v6) ALLOW Anywhere (v6) + > ghe-8443 (v6) ALLOW Anywhere (v6) + > ghe-9418 (v6) ALLOW Anywhere (v6) + ``` + +### Agregar reglas de firewell personalizadas + +{% warning %} + +**Advertencia:** Antes de que agregues reglas de cortafuegos personalizadas, respalda tus reglas actuales en caso de que necesites restablecerlas a algún punto funcional. Si estás bloqueado de tu servidor, comunícate con {% data variables.contact.contact_ent_support %} para reconfigurar las reglas originales del firewall. Restaurar las reglas originales del firewall implica tiempo de inactividad para tu servidor. + +{% endwarning %} + +1. Configura una regla de firewall personalizada. +2. Verifica el estado de cada nueva regla con el comando `estado numerado`. + ```shell + $ sudo ufw status numbered + ``` +3. Para hacer una copia de seguridad de tus reglas de firewall personalizadas, utiliza el comando `cp` para pasar las reglas a un archivo nuevo. + ```shell + $ sudo cp -r /lib/ufw ~/ufw.backup + ``` + +Después de actualizar {% data variables.product.product_location %}, debes volver a aplicar tus reglas de firewall personalizadas. Recomendamos que crees un script para volver a aplicar las reglas de firewall personalizadas. + +### Restaurar las reglas de firewell predeterminadas + +Si algo sale mal después de que cambies las reglas de firewell, puedes restablecer las reglas desde la copia de seguridad original. + +{% warning %} + +**Advertencia:** Si no respaldaste las reglas originales antes de hacer cambios al cortafuegos. contacta a {% data variables.contact.contact_ent_support %} para obtener más asistencia. + +{% endwarning %} + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Para restablecer las reglas de la copia de seguridad anterior, vuélvelas a copiar en el firewell con el comando `cp`. + ```shell + $ sudo cp -f ~/ufw.backup/*rules /lib/ufw + ``` +3. Vuelve a iniciar el firewell con el comando `systemctl`. + ```shell + $ sudo systemctl restart ufw + ``` +4. Confirma que las reglas recuperaron su forma predeterminada con el comando `ufw status` (estado de ufw). + ```shell + $ sudo ufw status + > Status: active + > To Action From + > -- ------ ---- + > ghe-1194 ALLOW Anywhere + > ghe-122 ALLOW Anywhere + > ghe-161 ALLOW Anywhere + > ghe-22 ALLOW Anywhere + > ghe-25 ALLOW Anywhere + > ghe-443 ALLOW Anywhere + > ghe-80 ALLOW Anywhere + > ghe-8080 ALLOW Anywhere + > ghe-8443 ALLOW Anywhere + > ghe-9418 ALLOW Anywhere + > ghe-1194 (v6) ALLOW Anywhere (v6) + > ghe-122 (v6) ALLOW Anywhere (v6) + > ghe-161 (v6) ALLOW Anywhere (v6) + > ghe-22 (v6) ALLOW Anywhere (v6) + > ghe-25 (v6) ALLOW Anywhere (v6) + > ghe-443 (v6) ALLOW Anywhere (v6) + > ghe-80 (v6) ALLOW Anywhere (v6) + > ghe-8080 (v6) ALLOW Anywhere (v6) + > ghe-8443 (v6) ALLOW Anywhere (v6) + > ghe-9418 (v6) ALLOW Anywhere (v6) + ``` diff --git a/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..338a70ea4b2f2 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -0,0 +1,93 @@ +--- +title: Configurar el escaneo de código para tu aplicativo +shortTitle: Configurar el escaneo de código +intro: 'Puedes habilitar, configurar e inhabilitar el {% data variables.product.prodname_code_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} permite que los usuarios escaneen el código para encontrar vulnerabilidades y errores.' +product: '{% data reusables.gated-features.code-scanning %}' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} + +### Acerca de {% data variables.product.prodname_code_scanning %} + +{% data reusables.code-scanning.about-code-scanning %} + +La tabla siguiente resume los tipos disponibles de análisis para {% data variables.product.prodname_code_scanning %}, y proporciona enlaces sobre el habilitar la característica para los repositorios individuales. + +{% data reusables.code-scanning.enabling-options %} + +Para los que los usuarios de {% data variables.product.product_location %} puedan habilitar y utilizar el {% data variables.product.prodname_code_scanning %} en sus repositorios, necesitarás, como administrador, habilitar esta característica para todo el aplicativo. + +### ¿Cómo sé si el {% data variables.product.prodname_code_scanning %} se encuentra habilitado para mi aplicativo? + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Verifica si hay una entrada de **{% data variables.product.prodname_advanced_security %}** en la barra lateral izquierda. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### Habilitar las {% data variables.product.prodname_code_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Debajo de " +{% data variables.product.prodname_advanced_security %}," da clic en **{% data variables.product.prodname_code_scanning_capc %}**. +![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + + +### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_actions %} + +#### Configurar un ejecutor auto-hospedado + +{% data variables.product.prodname_ghe_server %} puede ejecutar un {% data variables.product.prodname_code_scanning %} utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}. Primero, necesitas aprovisionar uno o más ejecutores auto-hospedados de {% data variables.product.prodname_actions %} en tu ambiente. Puedes aprovisionar ejecutores auto-hospedados a nivel de repositorio, organización o empresa. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". + +Debes asegurarte de que Git esté en la variable de "PATH" de cualquier ejecutor auto-hospedado que utilices para ejecutar las acciones de {% data variables.product.prodname_codeql %}. + +{% if currentVersion == "enterprise-server@2.22" %} +#### Aprovisionar las acciones +Para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_ghe_server %} con las {% data variables.product.prodname_actions %}, las acciones adecuadas deben estar disponibles localmente. Puedes hacer que las acciones estén disponibles en tres formas. + +- **Recomendada**: Puedes utilizar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para descargar acciones automáticamente desde {% data variables.product.prodname_dotcom_the_website %}. La máquina que hospeda tu instancia debe poder acceder a {% data variables.product.prodname_dotcom_the_website %}. Este enfoque garantiza que obtengas el software más reciente de forma automática. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_github_connect %} para que se sincronice con {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". +- Si quieres utilizar el {% data variables.product.prodname_codeql_workflow %}, puedes sincronizar el repositorio de {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.prodname_ghe_server %}, utilizando la herramienta de sincronización de acciones de {% data variables.product.prodname_codeql %} en [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Puedes utilizar esta herramienta sin importar si {% data variables.product.product_location %} o tus ejecutores de {% data variables.product.prodname_actions %} tienen acceso a internet, siempre y cuando puedas acceder tanto a {% data variables.product.product_location %} como a {% data variables.product.prodname_dotcom_the_website %} de forma simultánea en tu computadora. +- Puedes crear una copia local del repositorio de una accion en tu servidor si clonas el repositorio de {% data variables.product.prodname_dotcom_the_website %} que contiene la acción. Por ejemplo, si quieres utilizar acciones para el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, puedes crear un repositorio en tu instancia, el cual se llame `github/codeql-action`, y luego clonar el [repositorio](https://github.com/github/codeql-action) desde {% data variables.product.prodname_dotcom_the_website %} y posteriormente subir ese repositorio en el de `github/codeql-action` de tu instancia. También necesitarás descargar cualquiera de los lanzamientos del repositorio en {% data variables.product.prodname_dotcom_the_website %} y cargarlos en el repositorio de `github/codeql-action` de tu instancia como lanzamientos. + +##### Configurar {% data variables.product.prodname_github_connect %} para sincronizarse con {% data variables.product.prodname_actions %} +1. Si quieres descargar flujos de trabajo de acciones por petición desde {% data variables.product.prodname_dotcom_the_website %}, necesitarás habilitar {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)". +2. También tendrás que habilitar {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". +3. El siguiente paso es configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +4. Agrega un ejecutor auto-hospedado a tu repositorio, organización, o cuenta empresarial. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configurar el {% data variables.product.prodname_codeql %} en un servidor sin acceso a internet +Si el servidor en donde estás ejecutando +{% data variables.product.prodname_ghe_server %} no está conectado a internet y quieres permitir que los usuarios habiliten el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} para sus repositorios, debes utilizar la herramienta de sincronización de la acción de {% data variables.product.prodname_codeql %} para copiar las acciones de {% data variables.product.prodname_codeql %} y conjunto de consultas desde {% data variables.product.prodname_dotcom_the_website %} hacia tu servidor. La herramienta y los detalles de su uso se encuentran disponibles en [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} + +#### Habilitar el escaneo de código para los repositorios individuales +Después de que configuras un ejecutor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}y aprovisionas las acciones,{% endif %} los usuarios pueden habilitar el {% data variables.product.prodname_code_scanning %} para los repositorios individuales de {% data variables.product.product_location %}. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. + +### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %} +Si no quieres utilizar {% data variables.product.prodname_actions %}, puedes ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}. + +El {% data variables.product.prodname_codeql_runner %} es una herramienta de línea de comandos que puedes agregar a tu sistema de IC/CD de terceros. Esta herramienta ejecuta el análisis de {% data variables.product.prodname_codeql %} en un control de un repositorio de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". + +### Inhabilitar las {% data variables.product.prodname_code_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Debajo de " +{% data variables.product.prodname_advanced_security %}", deselecciona **{% data variables.product.prodname_code_scanning_capc %}**. +![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/code-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md new file mode 100644 index 0000000000000..9f74d8795857e --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -0,0 +1,71 @@ +--- +title: Configurar el cifrado de datos para tu empresa +shortTitle: Configurar el cifrado de datos +intro: 'Para el cifrado estático, puedes proporcionar tu propia llave de cifrado para cifrar tus datos bajo tus políticas de cifrado.' +versions: + github-ae: '*' +--- + +{% note %} + +**Nota:** La configuración de cifrado estático con una llave que administre el usuario se encuentra actualmente en beta y está sujeto a cambios. + +{% endnote %} + +### Acerca del cifrado de datos + +Para proporcionar un nivel alto de seguridad, {% data variables.product.product_name %} cifra tus datos mientras están estáticos en los centros de datos y mientras tus datos se encuentran en tránsito entre las máquinas de los usuarios y los centros de datos. + +Para el cifrado en tránsito, {% data variables.product.product_name %} utiliza la Seguridad de Capas de Transporte (TLS). Para el cifrado estático, {% data variables.product.product_name %} proporciona una llave RSA predeterminada. Después de que hayas inicializado tu empresa, puedes elegir mejor proporcionar tu propia llave. Tu llave debe ser una llave privada de RSA de 2048 bits en formato PEM. + +La llave que proporciones se almacena en un módulo de seguridad de hardware (HSM) en una bóveda de llaves que administra {% data variables.product.company_short %}. + +Para configurar tu llave de cifrado, utiliza la API de REST. Existen varias terminales de la API, por ejemplo, para verificar el estado de cifrado, actualiza tu llave de cifrado y bórrala. Nota que el borrar tu llave hará que tu empresa se congele. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST. + +### Agregar o actualizar una llave de cifrado + +Puedes agregar una llave de cifrado nueva tan frecuentemente como lo necesites. Cuando agregas una llave nueva, la llave anterior se descarta. Tu empresa no tendrá ningún tiempo de inactividad cuando actualices la llave. + +Tu llave privada de RSA de 2048 bits deberá estar en formato PEM, por ejemplo, en un archivo que se llama _private-key.pem_. + + ``` + -----BEGIN RSA PRIVATE KEY----- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + -----END RSA PRIVATE KEY----- + ``` + +1. Para agregar tu llave, utiliza la terminal `PATCH /enterprise/encryption`, reemplazando *~/private-key.pem* con la ruta a tu llave privada. + + ```shell + curl -X PATCH http(s)://hostname/api/v3/enterprise/encryption \ + -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }" + ``` + +2. Opcionalmente, verifica el estado de la operación de actualización. + + ```shell + curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id + ``` + +### Borrar tu llave de cifrado + +Para congelar tu empresa, por ejemplo, en caso de alguna irrupción, puedes inhabilitar el cifrado estático si borras tu llave de cifrado. + +Para descongelar tu empresa después de que hayas borrado tu llave de cifrado, contacta a soporte. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". + +1. Para borrar tu llave e inhabilitar el cifrado estático, utiliza la terminal `DELETE /enterprise/encryption`. + + ```shell + curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption + ``` + +2. Opcionalmente, verifica el estado de la operación de borrado. + + ```shell + curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id + ``` + +### Further reading + +- "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST diff --git a/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md b/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md new file mode 100644 index 0000000000000..d7b8b059fe43d --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md @@ -0,0 +1,34 @@ +--- +title: Configurar servidores de nombres DNS +intro: '{% data variables.product.prodname_ghe_server %} utiliza el protocolo de configuración dinámica de host (DHCP) para los ajustes DNS cuando las concesiones de DHCP ofrecen servidores de nombres. Si una concesión del protocolo de configuración dinámica de host (DHCP) no proporciona los servidores de nombres o si debes utilizar ajustes DNS particulares, puedes especificar los servidores de nombres de manera manual.' +redirect_from: + - /enterprise/admin/guides/installation/about-dns-nameservers/ + - /enterprise/admin/installation/configuring-dns-nameservers + - /enterprise/admin/configuration/configuring-dns-nameservers +versions: + enterprise-server: '*' +--- + +Los servidores de nombres que especifiques deben resolver el nombre del host de {% data variables.product.product_location %}. + +{% data reusables.enterprise_installation.changing-hostname-not-supported %} + +### Configurar servidores de nombres utilizando la consola de la máquina virtual + +{% data reusables.enterprise_installation.open-vm-console-start %} +2. Configurar servidores de nombres para tu instancia. +{% data reusables.enterprise_installation.vm-console-done %} + +### Configurar servidores de nombres utilizando el shell administrativo + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Para editar tus servidores de nombres, ingresa lo siguiente: + ```shell + $ sudo vim /etc/resolvconf/resolv.conf.d/head + ``` +3. Agrega cualquier entrada de `nameserver` (servidor de nombres) y luego guarda el archivo. +4. Después de verificar tus cambios, guarda el archivo. +5. Para agregar tus entradas nuevas de servidores de nombres en {% data variables.product.product_location %}, ingresa lo siguiente: + ```shell + $ sudo service resolvconf restart + ``` diff --git a/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md new file mode 100644 index 0000000000000..be89739f5b792 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md @@ -0,0 +1,168 @@ +--- +title: Configurar el correo electrónico para notificaciones +redirect_from: + - /enterprise/admin/guides/installation/email-configuration/ + - /enterprise/admin/articles/configuring-email/ + - /enterprise/admin/articles/troubleshooting-email/ + - /enterprise/admin/articles/email-configuration-and-troubleshooting/ + - /enterprise/admin/user-management/configuring-email-for-notifications +intro: 'Para facilitar que los usuarios respondan rápidamente a la actividad de {% data variables.product.product_name %}, puedes configurar tu empresa para que envíe notificaciones por correo electrónico sobre las propuestas, solicitudes de cambios, y comentarios de confirmaciones{% if enterpriseServerVersions contains currentVersion %}, así como puedes configurar ajustes adicionales para permitir las respuestas de correo externo{% endif %}.' +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Los correos electrónicos para notificaciones se envían si hay una actividad en un repositorio que un usuario está observando, si hay una actividad en una solicitud de extracción o en una propuesta en la que están participando o si el usuario o equipo del que son un miembro son @mencionados en un comentario. + +{% if currentVersion == "github-ae@latest" %} +Tu administrador de cuenta técnico dedicado en +{% data variables.contact.github_support %} puede configurar el correo electrónico para que las notificaciones se envíen a través de tu servidor de SMTP. Asegúrate de incluir los siguientes detalles en tu solicitud de soporte. + +- La dirección de tu servidor SMTP +- Información de inicio de sesión para autenticarse en el servidor: nombre de usuario y contraseña +- El puerto que utiliza tu servidor SMTP para enviar correos electrónicos +- El nombre del dominio que tu servidor SMTP enviará con una respuesta de HELO, en caso de que exista +- El tipo de cifrado que utiliza tu servidor SMTP +- La dirección de correo electrónico de "no-reply" a utilizar en los campos `From` y `To` para todas las notificaciones + +Para obtener más información sobre contactar a soporte, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)". +{% else %} +### Configurar SMTP + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En la parte superior de la página, haz clic en **Parámetros**. ![Pestaña Parámetros](/assets/images/enterprise/management-console/settings-tab.png) +3. En la barra lateral de la izquierda, haz clic en **Correo electrónico**. ![Pestaña Correo electrónico](/assets/images/enterprise/management-console/email-sidebar.png) +4. Selecciona **Activar correo electrónico**. Esto activará tanto el correo electrónico de salida como el de entrada, sin embargo para trabajar con el correo electrónico entrante también necesitarás configurar los parámetros de tu DNS como se describe a continuación en ["Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". ![Activar correo electrónico de salida](/assets/images/enterprise/management-console/enable-outbound-email.png) +5. Completa los parámetros de tu servidor de correo electrónico: + - En el campo **Dirección del servidor**, escribe la dirección de tu servidor SMTP. + - En el campo **Puerto**, escribe el puerto que usa tu servidor SMTP para enviar correo electrónico. + - En el campo **Dominio**, escribe el nombre de dominio que enviará tu servidor SMTP con una respuesta HELO, de ser el caso. + - En el desplegable **Autenticación**, elige el tipo de cifrado usado por tu servidor SMTP. + - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones. + + {% note %} + + **Nota:** si seleccionas la casilla de verificación **Send from author (Enviar desde autor)** en el webhook del correo electrónico **Services (Servicios)** de un repositorio, el correo electrónico de salida para ese repositorio se enviará desde el autor y no desde el correo electrónico sin respuesta. Para obtener más información, consulta la sección "[Acerca de las notificaciones por correo electrónico para las cargas a tu repositorio](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". + + {% endnote %} + +6. Si quieres descartar todos los correos electrónicos entrantes que estén dirigidos al correo electrónico sin respuesta, selecciona **Descartar correo electrónico dirigido a la dirección de correo electrónico sin respuesta**. ![Casilla de verificación para descartar los correos electrónicos dirigidos a la dirección de correo electrónico sin respuesta](/assets/images/enterprise/management-console/discard-noreply-emails.png) +7. En **Soporte**, elige un tipo de enlace para ofrecer un soporte adicional a tus usuarios: + - **Correo electrónico:** Una dirección de correo electrónico interna. + - **URL:** Un enlace a un sitio de soporte interno. Debes incluir tanto `http://` como `https://`. ![Correo de soporte técnico o URL](/assets/images/enterprise/management-console/support-email-url.png) +8. [Prueba de entrega del correo electrónico](#testing-email-delivery). + +### Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes + +Si quieres permitir respuestas de correo electrónico para las notificaciones, debes configurar los parámetros de tu DNS. + +1. Asegúrate de que el puerto 25 en la instancia esté accesible para tu servidor SMTP. +2. Crea un registro A que apunte a `reply.[hostname]`. Dependiendo de tu proveedor DNS y de la configuración del host de instancia, es posible que puedas crear un registro A único que apunte a `*.[hostname]`. +3. Crea un registro MX que apunte a `reply.[hostname]` para que los correos electrónicos para ese dominio sean enrutados a la instancia. +4. Crea un registro MX que apunte a `noreply.[hostname]` para `[hostname]` para que las respuestas a la dirección `cc` en los correos electrónicos para notificación sean enrutados a la instancia. Para obtener más información, consulta la sección {% if currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}." + +Con la configuración de tu DNS, ahora puedes probar si la configuración funciona. + +### Probar entrega del correo electrónico + +1. En la parte superior de la sección **Correo electrónico**, haz clic en **Probar parámetros del correo electrónico**. ![Probar parámetros del correo electrónico](/assets/images/enterprise/management-console/test-email.png) +2. En el campo **Enviar correo electrónico de prueba**, escribe una dirección donde enviar el correo electrónico de prueba. ![Probar dirección de correo electrónico](/assets/images/enterprise/management-console/test-email-address.png) +3. Haz clic en **Enviar correo electrónico de prueba**. ![Enviar correo electrónico de prueba](/assets/images/enterprise/management-console/test-email-address-send.png) + + {% tip %} + + **Sugerencia:** Si ocurren errores SMTP mientras se envía un correo electrónico de prueba, como un error de entrega inmediato o un error de configuración del correo saliente, los verás en el cuadro de diálogo de los parámetros del Correo electrónico de prueba. + + {% endtip %} + +4. Si el correo electrónico de prueba falla, [soluciona los problemas de los parámetros de tu correo electrónico](#troubleshooting-email-delivery). +5. Cuando el correo electrónico de prueba es exitoso, en la parte inferior de la página, haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/enterprise/management-console/save-settings.png) +6. Espera que se complete la fase de configuración. ![Configurar tu instancia](/assets/images/enterprise/management-console/configuration-run.png) + +### Solución de problemas de entrega de correo electrónico + +#### Crea un Paquete de soporte + +Si no puedes determinar qué está mal desde el mensaje de error mostrado, puedes descargar un [paquete de soporte](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) que contiene toda la conversación SMTP entre tu servidor de correo y {% data variables.product.prodname_ghe_server %}. Una vez que hayas descargado el paquete, verifica las entradas en *enterprise-manage-logs/unicorn.log* de todo el registro de conversación SMTP y cualquier error relacionado. + +El registro unicornio debería mostrar una transacción similar a la siguiente: + +```shell +This is a test email generated from https://10.0.0.68/setup/settings +Connection opened: smtp.yourdomain.com:587 +-> "220 smtp.yourdomain.com ESMTP nt3sm2942435pbc.14\r\n" +<- "EHLO yourdomain.com\r\n" +-> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n" +-> "250-SIZE 35882577\r\n" +-> "250-8BITMIME\r\n" +-> "250-STARTTLS\r\n" +-> "250-ENHANCEDSTATUSCODES\r\n" +-> "250 PIPELINING\r\n" +<- "STARTTLS\r\n" +-> "220 2.0.0 Ready to start TLS\r\n" +TLS connection started +<- "EHLO yourdomain.com\r\n" +-> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n" +-> "250-SIZE 35882577\r\n" +-> "250-8BITMIME\r\n" +-> "250-AUTH LOGIN PLAIN XOAUTH\r\n" +-> "250-ENHANCEDSTATUSCODES\r\n" +-> "250 PIPELINING\r\n" +<- "AUTH LOGIN\r\n" +-> "334 VXNlcm5hbWU6\r\n" +<- "dGhpc2lzbXlAYWRkcmVzcy5jb20=\r\n" +-> "334 UGFzc3dvcmQ6\r\n" +<- "aXRyZWFsbHl3YXM=\r\n" +-> "535-5.7.1 Username and Password not accepted. Learn more at\r\n" +-> "535 5.7.1 http://support.yourdomain.com/smtp/auth-not-accepted nt3sm2942435pbc.14\r\n" +``` + +Este registro muestra que el aparato: + +* Abrió una conexión con el servidor SMTP (`Connection opened: smtp.yourdomain.com:587`). +* Realizó una conexión exitosa y eligió usar TLS (`TLS connection started`). +* Fue realizado el tipo de autenticación `login` (`<- "AUTH LOGIN\r\n"`). +* El servidor SMTP rechazó la autenticación como inválida (`-> "535-5.7.1 Username and Password not accepted.`). + +#### Consultar los registros {% data variables.product.product_location %} + +Si necesitas verificar que tu correo electrónico entrante está funcionando, hay dos archivos de registro que puedes examinar en tu instancia: para verificar */var/log/mail.log* y */var/log/mail-replies/metroplex.log*. + +*/var/log/mail.log* verifies that messages are reaching your server. Este es un ejemplo de una respuesta de correo electrónico exitosa: + +``` +Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250] +Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323: client=st11p06mm-asmtp002.mac.com[17.172.124.250] +Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id= +Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=, size=5048, nrcpt=1 (queue active) +Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (delivered to maildir) +Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed +Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asmtp002.mac.com[17.172.124.250] +``` + +Ten en cuenta que el cliente primero se conecta; luego, la cola se vuelve activa. Entonces, el mensaje es entregado, el cliente es retirado de la cola y la sesión se desconecta. + +*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Este es un ejemplo de un mensaje exitoso: + +``` +[2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing +[2014-10-30T00:47:23.333 DEBUG (5284) #] Matched /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie +[2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success +``` + +Notarás que `metroplex` captura el mensaje entrante, lo procesa y luego desplaza el archivo a `/data/user/incoming-mail/success`. + +#### Verificar los parámetros de tu DNS + +Para procesar los correos electrónicos entrantes de manera adecuada, debes configurar un Registro A válido (o CNAME), así como un Registro MX. Para obtener más información, consulta "[Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." + +#### Controlar los parámetros de AWS Security Group o firewall + +Si {% data variables.product.product_location %} está detrás de un firewall o está siendo servido a través de un AWS Security Group, asegúrate de que el puerto 25 esté abierto a todos los servidores de correo que envíen correos electrónicos a `reply@reply.[hostname]`. + +#### Contactar con soporte técnico +Si aún no puedes resolver el problema, contacta a + +{% data variables.contact.contact_ent_support %}. Adjunta el archivo de salida desde `http(s)://[hostname]/setup/diagnostics` en tu correo electrónico para ayudarnos a resolver tu problema. +{% endif %} diff --git a/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md new file mode 100644 index 0000000000000..0cbc689b8b1f1 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md @@ -0,0 +1,65 @@ +--- +title: Configurar GitHub Pages para tu empresa +intro: 'Puedes habilitar o inhabilitar {% data variables.product.prodname_pages %} para tu empresa y elegir si quieres hacer los sitios accesibles para el público en general.' +redirect_from: + - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ + - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ + - /enterprise/admin/installation/configuring-github-pages-on-your-appliance + - /enterprise/admin/configuration/configuring-github-pages-on-your-appliance + - /admin/configuration/configuring-github-pages-on-your-appliance + - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/ +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Habilitar los sitios públicos para {% data variables.product.prodname_pages %} + +{% if enterpriseServerVersions contains currentVersion %}Si se habilita el modo privado en tu empresa, el{% else %}El {% endif %}público en general no podrá acceder a los sitios de {% data variables.product.prodname_pages %} que se hospeden en tu empresa a menos de que habilites los sitios públicos. + +{% warning %} + +**Advertencia:** Si habilitas los sitios públicos para {% data variables.product.prodname_pages %}, cada sitio en cada repositorio de tu empresa será accesible para el público en general. + +{% endwarning %} + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +4. Selecciona **Public Pages** (Páginas públicas). ![Casilla de verificación para habilitar páginas públicas](/assets/images/enterprise/management-console/public-pages-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +{% elsif currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.pages-tab %} +5. Debajo de "Políticas de las páginas", selecciona **{% data variables.product.prodname_pages %} públicas**. ![Casilla de verificación para habilitar las {% 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 %} + +### Inhabilitar {% data variables.product.prodname_pages %} para tu empresa + +{% if enterpriseServerVersions contains currentVersion %} +Si se inhabilita el aislamiento de subdominios para tu empresa, también deberás inhabilitar +{% data variables.product.prodname_pages %} para protegerte de las vulnerabilidades de seguridad potenciales. Para obtener más información, consulta la sección "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)". +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +4. Anula la selección de **Enable Pages** (Habilitar páginas). ![Casilla de verificación para inhabilitar {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) +{% data reusables.enterprise_management_console.save-settings %} +{% elsif currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.pages-tab %} +5. Debajo de "Políticas de las páginas", deselecciona **Habilitar {% data variables.product.prodname_pages %}**. ![Casilla de verificación para inhabilitar {% 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 %} +### Further reading + +- "[Habilitar el modo privado](/admin/configuration/enabling-private-mode)" +{% endif %} diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings.md b/translations/es-ES/content/admin/configuration/configuring-network-settings.md new file mode 100644 index 0000000000000..4d78e874e71a8 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings.md @@ -0,0 +1,15 @@ +--- +title: Configurar los ajustes de red +redirect_from: + - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl/ + - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings/ + - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings/ + - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings/ + - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings + - /enterprise/admin/configuration/configuring-network-settings +intro: 'Configura {% data variables.product.prodname_ghe_server %} con los servidores de nombres y el nombre del host DNS necesarios para tu red. También puedes configurar un servidor proxy o reglas de firewall. Debes permitir el acceso a determinados puertos con fines administrativos y relacionados con el usuario.' +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/configuration/configuring-rate-limits.md b/translations/es-ES/content/admin/configuration/configuring-rate-limits.md new file mode 100644 index 0000000000000..d46aecd28c069 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-rate-limits.md @@ -0,0 +1,49 @@ +--- +title: Configurar límites de tasa +intro: 'Puedes configurar límites de tasa para {% data variables.product.prodname_ghe_server %} usando la {% data variables.enterprise.management_console %}.' +redirect_from: + - /enterprise/admin/installation/configuring-rate-limits + - /enterprise/admin/configuration/configuring-rate-limits +versions: + enterprise-server: '*' +--- + +### Habilitar límites de tasa para {% data variables.product.prodname_enterprise_api %} + +Habilitar límites de tasa en {% data variables.product.prodname_enterprise_api %} puede evitar el uso excesivo de recursos por parte de usuarios individuales o sin autenticación. Para obtener más información, consulta la sección "[Limites de tasa](/enterprise/{{ page.version }}/v3/#rate-limiting)." + +{% if currentVersion ver_gt "enterprise-server@2.21" %} +Puedes eximir a una lista de usuarios para que no tomen los límites de tasa de la API si utilizas la utilidad `ghe-config` en el shell administrativo. Para obtener más información, consulta la sección "[Utilidades de la línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-config)". +{% endif %} + +{% note %} + +**Nota:** La {% data variables.enterprise.management_console %} detalla el período de tiempo (por minuto o por hora) de cada límite de tasa. + +{% endnote %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En "Limitación de tasa", selecciona **Enable API Rate Limiting** (Habilitar la limitación de tasa de API). ![Casilla para habilitar la limitación de tasa de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) +3. Escribe los límites para las solicitudes autenticadas y no autenticadas para cada API o acepta los límites predeterminados que aparecen completados. +{% data reusables.enterprise_management_console.save-settings %} + +### Habilitar límites de tasa de abuso + +Establecer límites de tasa de abuso protege el nivel general de servicio en {% data variables.product.product_location %}. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En "Limitación de tasa", selecciona **Enable Abuse Rate Limiting** (Habilitar limitación de tasa de abuso). ![Casilla para habilitar la limitación de tasa de abuso](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png) +3. Escribe límites para las solicitudes totales, límite de CPU y límite de CPU para búsquedas, o acepta los límites predeterminados que aparecen completados. +{% data reusables.enterprise_management_console.save-settings %} + +### Habilitar límites de tasa de Git + +Puedes aplicar límites de tasa de Git por red de repositorios o por Id. de usuario. Los límites de tasa de Git se expresan en operaciones simultáneas por minuto y se adaptan en función de la carga de CPU actual. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En "Limitación de tasa", selecciona **Enable Git Rate Limiting** (Habilitar limitación de tasa de Git). ![Casilla para habilitar la limitación de tasa de Git](/assets/images/enterprise/management-console/git-rate-limits-checkbox.png) +3. Escribe los límites para cada red de repositorios o ID de usuario. ![Campos para la red de repositorios y límites de ID de usuario](/assets/images/enterprise/management-console/example-git-rate-limits.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..8c90a90f0ee51 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configurar el escaneo de secretos para tu aplicativo +shortTitle: Configurar el escaneo de secretos +intro: 'Puedes habilitar, configurar e inhabilitar el {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} permite a los usuarios escanear código para los secretos que se confirmaron por accidente.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### Acerca de {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} Para obtener más información, consulta la sección "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)". + +### Prerrequisitos + +Para utilizar el {% data variables.product.prodname_secret_scanning %} en {% data variables.product.product_location %}, necesitas estos dos prerequisitos. + +- Necesitas habilitar el marcador de CPU de las [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extenciones SIMD de Streaming Suplementario 3, por sus siglas en inglés) en el VM/KVM que ejecuta {% data variables.product.product_location %}. + +- Necesitas una licencia de {% data variables.product.prodname_advanced_security %}. + +#### Verificar la compatibilidad del marcador de las SSSE3 en tus vCPU + +El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variables.product.prodname_secret_scanning %} impulsa el patrón acelerado de hardware que empata para encontrar las credenciales potenciales que se confirmaron en tus repositorios de {% data variables.product.prodname_dotcom %}. Las SSSE3 se habilitan para la mayoría de los CPU modernos. Puedes verificar si las SSSE3 están habilitadas para los vCPU disponibles para tu instancia de {% data variables.product.prodname_ghe_server %}. + +1. Conéctate al shell administrativo para tu instancia de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Ingresa el siguiente comando: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +Si esto devuelve el valor `0`, esto significa que el marcador de SSSE3 se encuentra disponible y habilitado. Ahora puedes habilitar el {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Habilitar el escaneo de secretos](#enabling-secret-scanning)" a continuación. + +Si no se devuelve un `0`, entonces no se ha habilitado las SSSE3 en tu VM/KVM. Necesitarás referirte a la documentación del hardware/hípervisor para encontrar cómo habilitar el marcador o ponerlo disponible como VM invitadas. + +#### Verificar si tienes una licencia de {% data variables.product.prodname_advanced_security %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Verifica si hay una entrada de **{% data variables.product.prodname_advanced_security %}** en la barra lateral izquierda. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### Habilitar las {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Debajo de " +{% data variables.product.prodname_advanced_security %}," da clic en **{% data variables.product.prodname_secret_scanning_caps %}**. +![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Inhabilitar las {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Debajo de " +{% data variables.product.prodname_advanced_security %}", deselecciona **{% data variables.product.prodname_secret_scanning_caps %}**. +![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md new file mode 100644 index 0000000000000..03fe1b97e72a8 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md @@ -0,0 +1,22 @@ +--- +title: Configurar la dirección IP usando la consola de la máquina virtual +intro: 'Por defecto, {% data variables.product.prodname_ghe_server %} recupera las configuraciones de red a través del protocolo de configuración dinámica de host (DHCP). Si es compatible con tu plataforma, o si el DHCP no está disponible, también puedes establecer las configuraciones de red usando la consola de la máquina virtual.' +redirect_from: + - /enterprise/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console + - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console +versions: + enterprise-server: '*' +--- + +{% note %} + +**Nota:** No tenemos compatibilidad para agregar adaptadores de red adicionales a {% data variables.product.prodname_ghe_server %}. + +{% endnote %} + +{% data reusables.enterprise_installation.open-vm-console-start %} +3. Para configurar, elige el protocolo `IPv4` o `IPv6`. ![Opciones para elegir el protocolo IPv4 o el IPv6](/assets/images/enterprise/network-configuration/IPv4-or-IPv6-protocol.png) +4. Configura las opciones para el protocolo que elegiste. ![Menú con opciones de protocolo IP](/assets/images/enterprise/network-configuration/network-settings-selection.png) +{% data reusables.enterprise_installation.vm-console-done %} + + diff --git a/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md b/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md new file mode 100644 index 0000000000000..e557106ffee8a --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md @@ -0,0 +1,40 @@ +--- +title: Configurar la sincronización de hora +intro: '{% data variables.product.prodname_ghe_server %} sincroniza automáticamente el reloj conectándose con los servidores NTP. Puedes establecer los servidores NTP que se utilicen para sincronizar el reloj o puedes usar los servidores NTP predeterminados.' +redirect_from: + - /enterprise/admin/articles/adjusting-the-clock/ + - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings/ + - /enterprise/admin/articles/setting-ntp-servers/ + - /enterprise/admin/categories/time/ + - /enterprise/admin/installation/configuring-time-synchronization + - /enterprise/admin/configuration/configuring-time-synchronization +versions: + enterprise-server: '*' +--- + +### Cambiar los servidores NTP predeterminados + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En la barra lateral izquierda, haz clic en **Time** (Hora). ![El botón de la hora en la barra lateral {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/sidebar-time.png) +3. En "Servidor NTP principal", escribe el nombre del host del servidor NTP principal. En "Servidor NTP secundario", escribe el nombre del host del servidor NTP secundario. ![Los campos para los servidores NTP principal y secundario en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png) +4. Al final de la página, haz clic en **Save settings** (Guardar configuraciones). ![El botón de guardar en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png) +5. Espera a que la configuración se ejecute por completo. + +### Corregir un desface de tiempo prolongado + +El protocolo NTP corrige permanentemente las pequeñas discrepancias de sincronización de hora. Puedes usar el shell administrativo para sincronizar la hora de inmediato. + +{% note %} + +**Notas:** + - No puedes modificar la zona horaria universal coordinada (UTC). + - Debes evitar que tu hipervisor trate de configurar el reloj de la máquina virtual. Para obtener más información, consulta la documentación proporcionada por el proveedor de virtualización. + +{% endnote %} + +- Utiliza el comando `chronyc` para sincronizar el servidor con el servidor NTP configurado. Por ejemplo: + +```shell +$ sudo chronyc -a makestep +``` diff --git a/translations/es-ES/content/admin/configuration/configuring-tls.md b/translations/es-ES/content/admin/configuration/configuring-tls.md new file mode 100644 index 0000000000000..bfd4a4951afd2 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-tls.md @@ -0,0 +1,70 @@ +--- +title: Configurar TLS +intro: 'Puedes configurar la Seguridad de la capa de transporte (TLS) en {% data variables.product.product_location %} para poder usar un certificado firmado por una entidad de certificación confiable.' +redirect_from: + - /enterprise/admin/articles/ssl-configuration/ + - /enterprise/admin/guides/installation/about-tls/ + - /enterprise/admin/installation/configuring-tls + - /enterprise/admin/configuration/configuring-tls +versions: + enterprise-server: '*' +--- + +### Acerca de la Seguridad de la capa de transporte + +El TLS, que reemplazó al SSL, se habilita y configura con un certificado autofirmado cuando se inicia el {% data variables.product.prodname_ghe_server %} por primera vez. Como los certificados autofirmados no son confiables para los navegadores web y los clientes de Git, estos clientes informarán advertencias de certificados hasta que inhabilites TLS o cargues un certificado firmado por una entidad confiable, como Let's Encrypt. + +El aparato {% data variables.product.prodname_ghe_server %} enviará encabezados de Seguridad de transporte estricta de HTTP mientras SSL esté habilitado. Inhabilitar TLS hará que los usuarios pierdan acceso al aparato, porque sus navegadores no permitirán que un protocolo se degrade a HTTP. Para obtener más información, consulta "[Seguridad de transporte estricta de HTTP (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" en Wikipedia. + +{% data reusables.enterprise_installation.terminating-tls %} + +Para permitir que los usuarios utilicen FIDO U2F para la autenticación de dos factores, debes habilitar TLS para tu instancia. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". + +### Prerrequisitos + +Para utilizar TLS en la producción, debes tener un certificado en un formato de PEM no cifrado firmado por una entidad de certificación confiable. + +Tu certificado también deberá tener configurados Nombres alternativos de sujeto para los subdominios detallados en "[Habilitar aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" y deberá incluir toda la cadena de certificación si lo firmó una entidad de certificación intermedia. Para obtener más información, consulta "[Nombre alternativo de sujeto](http://en.wikipedia.org/wiki/SubjectAltName)" en Wikipedia. + +Puedes generar una solicitud de firma de certificados (CSR) para tu instancia usando el comando `ghe-ssl-generate-csr`. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." + +### Cargar un certificado TLS personalizado + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +4. En "TLS Protocol support" (Asistencia de protocolo TLS), selecciona los protocolos que quieres permitir. ![Botones de radio con opciones para elegir protocolos TLS](/assets/images/enterprise/management-console/tls-protocol-support.png) +5. En "Certificate" (Certificado), haz clic en **Choose File** (Elegir archivo) para elegir el certificado TLS o la cadena de certificación (en formato de PEM) que quieras instalar. Este archivo suele tener una extensión *.pem*, *.crt* o *.cer*. ![Botón para encontrar archivo de certificado TLS](/assets/images/enterprise/management-console/install-tls-certificate.png) +6. En "Unencrypted key" (Clave no cifrada), haz clic en **Choose File** (Elegir archivo) para elegir la clave TLS (en formato de PEM) que quieras instalar. Ese archivo suele tener una extensión *.key*. ![Botón para encontrar archivo de clave TLS](/assets/images/enterprise/management-console/install-tls-key.png) + + {% warning %} + + **Advertencia**: Tu clave TLS no debe tener contraseña. Para obtener más información, consulta "[Eliminar la contraseña de tu archivo clave](/enterprise/{{ currentVersion }}/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". + + {% endwarning %} +{% data reusables.enterprise_management_console.save-settings %} + +### Acerca de la asistencia de Let's Encrypt + +Let's Encrypt es una entidad de certificación pública que emite certificados TLS gratuitos y automáticos que son confiables para los navegadores que usan el protocolo ACME. De hecho, puedes obtener y renovar los certificados de Let's Encrypt para tu aparato sin la necesidad de realizar ningún mantenimiento manual. + +{% data reusables.enterprise_installation.lets-encrypt-prerequisites %} + +Cuando habilites la automatización de la gestión de certificado TLS con Let's Encrypt, {% data variables.product.product_location %} se contactará con los servidores de Let's Encrypt para obtener un certificado. Para renovar un certificado, los servidores de Let's Encrypt deben validar el control del nombre de dominio configurado con las solicitudes HTTP entrantes. + +También puedes usar la utilidad de la línea de comando `ghe-ssl-acme` en {% data variables.product.product_location %} para generar un certificado de Let's Encrypt de manera automática. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." + +### Configurar TLS usando Let's Encrypt + +{% data reusables.enterprise_installation.lets-encrypt-prerequisites %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +5. Selecciona **Enable automation of TLS certificate management using Let's Encrypt** (Habilitar la automatización de la gestión de certificado TLS con Let's Encrypt). ![Casilla de verificación para habilitar Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_management_console.privacy %} +7. Haz clic en **Request TLS certificate** (Solicitar certificado TLS). ![Botón para solicitar certificado TLS](/assets/images/enterprise/management-console/request-tls-button.png) +8. Haz clic en **Save configuration** (Guardar configuración). diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md new file mode 100644 index 0000000000000..f41abea7c8378 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md @@ -0,0 +1,16 @@ +--- +title: Configurar tu empresa +intro: "Después de que {% data variables.product.product_name %} se encuentre listo y funcionando, puedes configurar tu empresa de acuerdo con las necesidades de tu organización." +redirect_from: + - /enterprise/admin/guides/installation/basic-configuration/ + - /enterprise/admin/guides/installation/administrative-tools/ + - /enterprise/admin/articles/restricting-ssh-access-to-specific-hosts/ + - /enterprise/admin/guides/installation/configuring-the-github-enterprise-appliance/ + - /enterprise/admin/installation/configuring-the-github-enterprise-server-appliance + - /enterprise/admin/configuration/configuring-your-enterprise +mapTopic: verdadero +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md new file mode 100644 index 0000000000000..628ad089f7de3 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md @@ -0,0 +1,61 @@ +--- +title: Conectar el servidor de GitHub Enterprise a GitHub Enterprise Cloud +intro: 'Después de que habilites {% data variables.product.prodname_github_connect %}, puedes compartir características y flujos de trabajo específicos entre {% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que también sean dueños de una cuenta de organización o empresa de {% data variables.product.prodname_ghe_cloud %} podrán habilitar {% data variables.product.prodname_github_connect %}.' +versions: + enterprise-server: '*' +--- + +### Acerca de {% data variables.product.prodname_github_connect %} + +Para habilitar {% data variables.product.prodname_github_connect %}, debes configurar la conexión en ambos {% data variables.product.product_location_enterprise %} y en tu cuenta de empresa u organización de {% data variables.product.prodname_ghe_cloud %}. + +Para configurar una conexión, tu configuración proxy debe permitir la conectividad a `github.com` y `api.github.com`. Para obtener más información, consulta "[Configuring an outbound web proxy server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)." + +Después de habilitar {% data variables.product.prodname_github_connect %}, podrás habilitar características, como búsqueda unificada y contribuciones unificadas. Para obtener más información acerca de todas las características disponibles, consulta "[Administrar conexiones entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud)." + +Cuando conectas {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_ghe_cloud %}, un registro en {% data variables.product.prodname_dotcom_the_website %} almacena información sobre la conexión: +- La parte pública de la clave de tu licencia {% data variables.product.prodname_ghe_server %} +- Un hash de tu licencia {% data variables.product.prodname_ghe_server %} +- El nombre personalizado de tu licencia {% data variables.product.prodname_ghe_server %} +- El nombre del host de {% data variables.product.product_location_enterprise %} +- La versión de {% data variables.product.product_location_enterprise %} +- La cuenta de empresa u organización en {% data variables.product.prodname_dotcom_the_website %} está conectada a {% data variables.product.product_location_enterprise %} +- El token de autenticación que usa {% data variables.product.product_location_enterprise %} para hacerle solicitudes a {% data variables.product.prodname_dotcom_the_website %} + +Habilitar {% data variables.product.prodname_github_connect %} también crea un {% data variables.product.prodname_github_app %} cuyo dueño es la cuenta empresarial u organizacional de {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_ghe_server %} usa las credenciales de {% data variables.product.prodname_github_app %} para hacerle solicitudes a {% data variables.product.prodname_dotcom_the_website %}. + +{% data variables.product.prodname_ghe_server %} almacena credenciales desde la {% data variables.product.prodname_github_app %}. Estas credenciales se replicarán en cualquier entorno de alta disponibilidad o de agrupación y se almacenarán en cualquier copia de seguridad, incluidas las instantáneas creadas por {% data variables.product.prodname_enterprise_backup_utilities %}. +- Un token de autenticación, que es válido durante una hora +- Una clave privada, que se utiliza para generar un nuevo token de autenticación + +Habilitar {% data variables.product.prodname_github_connect %} no permitirá {% data variables.product.prodname_dotcom_the_website %} que los usuarios hagan cambios en {% data variables.product.prodname_ghe_server %}. + +Para obtener más información acerca de cómo administrar las cuentas empresariales utilizando la API de GraphQL, consulta la sección "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)". +### Habilitar {% data variables.product.prodname_github_connect %} + +1. Ingresa en + +{% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +5. En "{% data variables.product.prodname_dotcom_the_website %} aún no está habilitado", haz clic en **Enable {% data variables.product.prodname_github_connect %}** (Habilitar). Al hacer clic en **Enable {% data variables.product.prodname_github_connect %}** (Habilitar), aceptas el Anexo {% data variables.product.prodname_github_connect %} al Acuerdo de licencia {% data variables.product.prodname_enterprise %}. ![Habilitar el botón Conectar de GitHub](/assets/images/enterprise/business-accounts/enable-github-connect-button.png) +6. Al lado de la cuenta de usuario u organización a la que quieres conectarte, haz clic en **Connect** (Conectar). ![Conecta el botón junto a una cuenta de empresa o negocio](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +### Desconectar una {% data variables.product.prodname_ghe_cloud %} organización o cuenta de empresa de {% data variables.product.product_location_enterprise %} + +Cuando te desconectas de {% data variables.product.prodname_ghe_cloud %}, se elimina la {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} de tu cuenta de empresa u organización, y las credenciales almacenadas en {% data variables.product.product_location_enterprise %} se eliminan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +5. Al lado de la cuenta de empresa u organización de la que te quieres desconectar, haz clic en **Disable {% data variables.product.prodname_github_connect %}** (Inhabilitar {% data variables.product.prodname_github_connect %}). ![Inhabilitar el botón Conectar de GitHub para una cuenta de empresa o nombre de organización](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +6. Lee la información acerca de la desconexión y haz clic en **Disable {% data variables.product.prodname_github_connect %}** (Inhabilitar {% data variables.product.prodname_github_connect %}). ![Modal con información de advertencia acerca de la desconexión y el botón de confirmación](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) + diff --git a/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000000..81e9db4ee2403 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,76 @@ +--- +title: Habilitar las alertas para las dependencias vulnerables en GitHub Enterprise Server +intro: 'Puedes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_ghe_cloud %} y habilitar las {% if currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} para las dependencias vulnerables en los repositorios de tu instancia.' +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que también sean propietarios de la cuenta empresarial u organizacional de {% data variables.product.prodname_ghe_cloud %} conectada podrán habilitar las {% if currentVersion ver_gt "enterprise-server@2.21" %} alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}.' +versions: + enterprise-server: '*' +--- + +### Acerca de las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} + +{% data reusables.repositories.tracks-vulnerabilities %} Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +Puedes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom_the_website %} y luego sincronizar los datos de las vulnerabilidades con tu instancia y generar {% if currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} en los repositorios con una dependencia vulnerable. + +Después de conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom_the_website %} y de habilitar las{% if currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} para las dependencias vulnerables, los datos de las vulnerabilidade se sincronizan cada hora desde el {% data variables.product.prodname_dotcom_the_website %} a tu instancia. También puedes elegir sincronizar manualmente los datos de vulnerabilidad en cualquier momento. No se han cargado códigos o información sobre el código desde {% data variables.product.product_location %} hasta {% data variables.product.prodname_dotcom_the_website %}. + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Cuando {% data variables.product.product_location %} recibe información acerca de una vulnerabilidad, éste identificará los repositorios en tu instancia que utilicen la versión de la dependencia que presenta la afectación y generará {% data variables.product.prodname_dependabot_alerts %}. Puedes personalizar la forma en la que recibes las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Configurar notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)". +{% endif %} + +{% if currentVersion == "enterprise-server@2.21" %}Cuando {% data variables.product.product_location %}recibe información sobre una vulnerabilidad, éste identificará los repositorios en tu instancia que utilicen la versión afectada de la dependencia y generará alertas de seguridad. Puedes personalizar la forma en la que recibes las alertas de seguridad. Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)". +{% endif %} + +{% if currentVersion ver_lt "enterprise-server@2.21" %}Cuando {% data variables.product.product_location %}recibe información sobre una vulnerabilidad, éste identificará los repositorios en tu instancia que utilicen la versión afectada de la dependencia y generará alertas de seguridad. Puedes personalizar la forma en la que recibes las alertas de seguridad. Para obtener más información, consulta "[Elegir el método de entrega para tus notificaciones](/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" %} +### Habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} +{% else %} +### Habilitar alertas de seguridad para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} +{% endif %} + +Antes de habilitar {% if currentVersion ver_gt "enterprise-server@2.21" %}las alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} para las dependencias vulnerables en {% data variables.product.product_location %}, debes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." + +{% if currentVersion ver_gt "enterprise-server@2.20" %} + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Te recomendamos configurar las {% data variables.product.prodname_dependabot_alerts %} sin incluir notificaciones por los primeros días para evitar una sobrecarga de mensajes de correo electrónico. Después de algunos días, puedes habilitar las notificaciones para recibir las {% data variables.product.prodname_dependabot_alerts %} como de costumbre.{% endif %} + +{% if currentVersion == "enterprise-server@2.21" %}Te recomendamos configurar las alertas de seguridad sin incluir notificaciones por los primeros días para evitar una sobrecarga de mensajes de correo electrónico. Después de algunos cuantos días, puedes habilitar las notificaciones para recibir alertas de seguridad como de costumbre.{% endif %} + +{% endif %} + +{% data reusables.enterprise_site_admin_settings.sign-in %} + +1. En el shell administrativo, habilita las {% if currentVersion ver_gt "enterprise-server@2.21" %} alertas de seguridad del {% data variables.product.prodname_dependabot %}{% else %}{% endif %} para las dependencias vulnerables en {% data variables.product.product_location %}: + + ``` shell +$ ghe-dep-graph-enable +``` + {% note %} + + **Nota**: Para obtener más información acerca de cómo habilitar el acceso al shell administrativo por SSH, consulta la sección "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)". + + {% endnote %} + +3. Regresa a + +{% data variables.product.prodname_ghe_server %}. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% if currentVersion ver_gt "enterprise-server@2.20" %} +5. Debajo de "Los repositorios pueden escanearse par encontrar vulnerabilidades", utiliza el menú desplegable y selecciona **Habilitado sin notificaciones**. Opcionalmente, para habilitar las alertas con notificaciones, selecciona **Habilitado con notificaciones**.{% else %} +5. En "Los repositorios se pueden escanear para encontrar vulnerabilidades", usa el menú desplegable y selecciona **Enabled** (Habilitado). +{% endif %} + ![Menú desplegable para habilitar el escaneo de repositorios para buscar vulnerabilidades](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + +### Ver las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} + +Puedes ver todas las vulnerabilidades en {% data variables.product.product_location %} y sincronizar en forma manual los datos de vulnerabilidad desde {% data variables.product.prodname_dotcom_the_website %} para actualizar la lista. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. En la barra lateral izquierda, haz clic en **Vulnerabilities** (Vulnerabilidades). ![Pestaña de vulnerabilidades de la barra lateral del administrador del sitio](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. Para sincronizar los datos de vulnerabilidades, haz clic en **Sync Vulnerabilities now** (Sincronizar vulnerabilidades ahora). ![Botón de Sincronizar vulnerabilidades ahora](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md new file mode 100644 index 0000000000000..b1fc2ce69b347 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md @@ -0,0 +1,62 @@ +--- +title: Habilitar y programar el modo de mantenimiento +intro: 'Algunos procedimientos de mantenimiento estándar, como la actualización {% data variables.product.product_location %} o la restauración de copias de seguridad, exigen que la instancia esté sin conexión para el uso normal.' +redirect_from: + - /enterprise/admin/maintenance-mode/ + - /enterprise/admin/categories/maintenance-mode/ + - /enterprise/admin/articles/maintenance-mode/ + - /enterprise/admin/articles/enabling-maintenance-mode/ + - /enterprise/admin/articles/disabling-maintenance-mode/ + - /enterprise/admin/guides/installation/maintenance-mode/ + - /enterprise/admin/installation/enabling-and-scheduling-maintenance-mode + - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode +versions: + enterprise-server: '*' +--- + +### Acerca del modo de mantenimiento + +Algunos tipos de operaciones exigen que desconectes tu {% data variables.product.product_location %} y la pongas en modo de mantenimiento: +- Actualizar a una versión nueva de tu {% data variables.product.prodname_ghe_server %} +- Aumentar los recursos de CPU, memoria o almacenamiento asignados a la máquina virtual +- Migrar datos desde una máquina virtual a otra +- Restaurar datos desde una instantánea de {% data variables.product.prodname_enterprise_backup_utilities %} +- Solucionar ciertos tipos de problemas críticos de solicitud + +Recomendamos que programe una ventana de mantenimiento para, al menos, los siguientes 30 minutos para darle a los usuarios tiempo para prepararse. Cuando está programada una ventana de mantenimiento, todos los usuarios verán un mensaje emergente al acceder al sitio. + +![Mensaje emergente para el usuario final acerca del mantenimiento programado](/assets/images/enterprise/maintenance/maintenance-scheduled.png) + +Cuando la instancia está en modo de mantenimiento, se rechazan todos los accesos HTTP y Git. Las operaciones de extracción, clonación y subida de Git también se rechazan con un mensaje de error que indica que temporalmente el sitio no se encuentra disponible. Al visitar el sitio desde un navegador aparece una página de mantenimiento. + +![La pantalla de presentación del modo de mantenimiento](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) + +### Habilitar el modo de mantenimiento de inmediato o programar una ventana de mantenimiento para más tarde + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En la parte superior de la {% data variables.enterprise.management_console %}, haz clic en **Mantenimiento**. ![Pestaña de mantenimiento](/assets/images/enterprise/management-console/maintenance-tab.png) +3. En "Habilitar y Programar", decide si habilitas el modo de mantenimiento de inmediato o programas una ventana de mantenimiento para otro momento. + - Para habilitar el modo de mantenimiento de inmediato, usa el menú desplegable y haz clic en **now** (ahora). ![Menú desplegable con la opción para habilitar el modo de mantenimiento ahora seleccionado](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) + - Para programar una ventana de mantenimiento para otro momento, usa el menú desplegable y haz clic en un horario de inicio. ![Menú desplegable con la opción para programar una ventana de mantenimiento](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) +4. Selecciona **Habilitar el modo de mantenimiento**. ![Casilla de verificación para habilitar o programar el modo de mantenimiento](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Programar el modo de mantenimiento con {% data variables.product.prodname_enterprise_api %} + +Puedes programar el mantenimiento para horarios o días diferentes con {% data variables.product.prodname_enterprise_api %}. Para obtener más información, consulta la sección "[Consola de Administración](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)". + +### Habilitar o inhabilitar el modo de mantenimientos para todos los nodos de una agrupación + +Con la herramienta `ghe-cluster-maintenance`, puedes configurar o anular la configuración del modo de mantenimiento para cada nodo de una agrupación. + +```shell +$ ghe-cluster-maintenance -h +# Muestra opciones +$ ghe-cluster-maintenance -q +# Consulta el modo actual +$ ghe-cluster-maintenance -s +# Configura el modo de mantenimiento +$ ghe-cluster-maintenance -u +# Anula la configuración del modo de mantenimiento +``` diff --git a/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000000..e0eba629b65f6 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,25 @@ +--- +title: Habilitar la sincronización automática de licencias de usuario entre el servidor de GitHub Enterprise y GitHub Enterprise Cloud +intro: 'Puedes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_ghe_cloud %} y permitir que {% data variables.product.prodname_ghe_server %} cargue información de licencias de usuario en tu cuenta de empresa en {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que también sean dueños de la cuenta organizacional o empresarial conectada de {% data variables.product.prodname_ghe_cloud %} pueden habilitar la sincronización automática de la licencia del usuario.' +versions: + enterprise-server: '*' +--- + +### Acerca de la sincronización de licencias + +Después de que habilitas la sincronización de licencias, podrás ver el uso de licencias para toda tu cuenta empresarial, a través de {% data variables.product.prodname_ghe_server %} y de {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} sincroniza la licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} semanalmente. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{currentVersion}}/admin/installation/managing-your-github-enterprise-license)". + +También puedes cargar en forma manual información de licencias de usuario {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." + +### Habilitar la sincronización de licencias + +Antes de habilitar la sincronización de licencias en {% data variables.product.product_location_enterprise %}, debes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +5. En "El servidor puede sincronizar el recuento y uso de licencias de usuario", usa el menú desplegable y selecciona **Enabled** (Habilitado). ![Menú desplegable para habilitar la sincronización automática de licencias de usuario](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/es-ES/content/admin/configuration/enabling-private-mode.md b/translations/es-ES/content/admin/configuration/enabling-private-mode.md new file mode 100644 index 0000000000000..27beb1462b154 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-private-mode.md @@ -0,0 +1,24 @@ +--- +title: Habilitar el modo privado +intro: 'En el modo privado, {% data variables.product.prodname_ghe_server %} exige que todos los usuarios inicien sesión para acceder a la instalación.' +redirect_from: + - /enterprise/admin/articles/private-mode/ + - /enterprise/admin/guides/installation/security/ + - /enterprise/admin/guides/installation/securing-your-instance/ + - /enterprise/admin/installation/enabling-private-mode + - /enterprise/admin/configuration/enabling-private-mode +versions: + enterprise-server: '*' +--- + +Debes habilitar el modo privado si {% data variables.product.product_location %} es de acceso público por internet. En el modo privado, los usuarios no pueden clonar repositorios en forma anónima por `git://`. Si también está habilitada la autenticación incorporada, un administrador debe invitar a los nuevos usuarios para que creen una cuenta en la instancia. Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)." + +{% data reusables.enterprise_installation.image-urls-viewable-warning %} + +Con el modo privado habilitado, puedes permitir que operaciones de Git sin autenticación (y cualquiera con acceso de red a {% data variables.product.product_location %}) lean un código de repositorio público de tu instancia con acceso de lectura anónimo de Git habilitado. Para obtener más información, consulta "[Permitir que los administradores habiliten el acceso de lectura anónimo de Git para los repositorios públicos](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +4. Selecciona **Private mode** (Modo privado). ![Casilla de verificación para habilitar el modo privado](/assets/images/enterprise/management-console/private-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md b/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md new file mode 100644 index 0000000000000..dc9d5940814a9 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md @@ -0,0 +1,64 @@ +--- +title: Habilitar el aislamiento de subdominio +intro: 'Puedes configurar el aislamiento de subdominio para separar en forma segura el contenido suministrado por el usuario de las demás partes de tu aparato {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/guides/installation/about-subdomain-isolation/ + - /enterprise/admin/installation/enabling-subdomain-isolation + - /enterprise/admin/configuration/enabling-subdomain-isolation +versions: + enterprise-server: '*' +--- + +### Acerca del aislamiento de subdominio + +El aislamiento de subdominio mitiga las vulnerabilidades del estilo cross-site scripting y otras vulnerabilidades relacionadas. Para obtener más información, consulta "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" en Wikipedia. Es altamente recomendable que habilites el aislamiento de subdominio en {% data variables.product.product_location %}. + +Cuando el aislamiento de subdominio está habilitado, {% data variables.product.prodname_ghe_server %} reemplaza varias rutas con subdominios. + +{% if currentVersion == "enterprise-server@2.22" %} +Para utilizar docker con +el {% data variables.product.prodname_registry %}, también debes habilitar el aislamiento de subdominios. Para obtener más información, consulta la sección "[Configurar Docker para utilizarlo con {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)". + +{% data reusables.package_registry.packages-ghes-release-stage %} +| +{% endif %} +| Ruta sin aislamiento de subdominio | Ruta con aislamiento de subdominio | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker, en conjunto con el {% data variables.product.prodname_registry %} no funcionará con el aislamiento de subdominios inhabilitado para el {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} + +### Prerrequisitos + +{% data reusables.enterprise_installation.disable-github-pages-warning %} + +Antes de que habilites el aislamiento de subdominio, debes configurar tus ajustes de red para el nuevo dominio. + +- Especifica un nombre de dominio válido como tu nombre del host, en lugar de una dirección IP. Para obtener más información, consulta "[Configurar un nombre del host](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)." + +{% data reusables.enterprise_installation.changing-hostname-not-supported %} + +- Configura un registro de Sistema de nombres de dominio (DNS) de carácter comodín o registros DNS individuales para los subdominios detallados más arriba. Recomendamos crear un registro A para `*.HOSTNAME` que apunte a la dirección IP de tu servidor así no tienes que crear múltiples registros para cada subdominio. +- Obtén un certificado de Seguridad de la capa de transporte (TLS) de carácter comodín para `*.HOSTNAME` con un Nombre alternativo del firmante (SAN) para el `HOSTNAME` y para el `*.HOSTNAME` de dominio de carácter comodín. Por ejemplo, si tu nombre del host es `*.github.octoinc.com` obtén un certificado con el valor del nombre común configurado en `*.github.octoinc.com` y un valor SAN configurado en `github.octoinc.com` y `*.github.octoinc.com`. +- Habilita TLS en tu aparato. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)." + +### Habilitar el aislamiento de subdominio + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Selecciona **Subdomain isolation (recommended)** (Aislamiento de subdominio [recomendado]). ![Casilla de verificación para habilitar el aislamiento de subdominio](/assets/images/enterprise/management-console/subdomain-isolation.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md new file mode 100644 index 0000000000000..1bb84d32eed48 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md @@ -0,0 +1,32 @@ +--- +title: Habilitar aportes unificados entre el Servidor de GitHub Enterprise y GitHub.com +intro: 'Después de habilitar {% data variables.product.prodname_github_connect %}, puedes permitir {% data variables.product.prodname_ghe_cloud %} que los miembros destaquen su trabajo en {% data variables.product.prodname_ghe_server %} al enviar los recuentos de contribuciones a sus {% data variables.product.prodname_dotcom_the_website %} perfiles.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que también sean dueños de la cuenta organizacional o empresarial conectada de {% data variables.product.prodname_ghe_cloud %} pueden habilitar las contribuciones unificadas entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '*' +--- + +Como un administrador del sitio, puedes habilitar a los usuarios finales para que envíen sus recuentos de contribuciones de manera anónima por sus trabajos desde {% data variables.product.prodname_ghe_server %} a sus gráficos de contribuciones {% data variables.product.prodname_dotcom_the_website %}. + +Después de habilitar {% data variables.product.prodname_github_connect %} y habilitar {% data variables.product.prodname_unified_contributions %} en ambos entornos, los usuarios finales a tu instancia pueden conectarse a sus {% data variables.product.prodname_dotcom_the_website %} cuentas y enviar recuentos de contribuciones desde {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} Para obtener más información, consulta "[Enviar tus contribuciones {% data variables.product.prodname_ghe_server %} a tu perfil {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile/)." + +Si el administrador del sitio inhabilita la funcionalidad o la opción de los programadores de la conexión, los recuentos de contribuciones {% data variables.product.prodname_ghe_server %} se borrarán en {% data variables.product.prodname_dotcom_the_website %}. Si el programador vuelve a conectar sus perfiles luego de inhabilitarlos, se restablecerán los recuentos de contribución para los últimos 90 días. + +{% data variables.product.prodname_ghe_server %} **únicamente** envía el recuento de contribución y la fuente ({% data variables.product.prodname_ghe_server %}) de los usuarios conectados. No envía ningún tipo de información sobre la contribución o cómo se realizó. + +Antes de habilitar {% data variables.product.prodname_unified_contributions %} en {% data variables.product.product_location_enterprise %}, debes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectarse a {% data variables.product.prodname_ghe_server %} para {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)." + +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +4. En "Los usuarios pueden compartir recuentos de contribuciones en {% data variables.product.prodname_dotcom_the_website %}", haz clic en **Request access (Solicita acceso)**. ![Solicitud para acceder a la opción de contribuciones unificadas](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png) +5. [Inicia sesión](https://enterprise.github.com/login) en el sitio {% data variables.product.prodname_ghe_server %} para recibir más instrucciones. + +Cuando solicitas acceso, te redireccionaremos al sitio {% data variables.product.prodname_ghe_server %} para comprobar tus términos de servicio actuales. Si {% data variables.product.product_location_enterprise %} utiliza los términos de servicio estándar, la solicitud automáticamente te redireccionará a las instrucciones para habilitar {% data variables.product.prodname_unified_contributions %}. Si estás utilizando los términos de servicio personalizados, registraremos tu solicitud y te contactaremos para configurar el acceso. diff --git a/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md new file mode 100644 index 0000000000000..5cd302b850517 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md @@ -0,0 +1,30 @@ +--- +title: Habilitar la búsqueda unificada entre el Servidor de GitHub Enterprise y GitHub.com +intro: 'Después de habilitar {% data variables.product.prodname_github_connect %}, puedes permitir la búsqueda de {% data variables.product.prodname_dotcom_the_website %} desde {% data variables.product.product_location_enterprise %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que también sean dueños de la cuenta organizacional o empresarial conectada de {% data variables.product.prodname_ghe_cloud %} pueden habilitar la búsqueda unificada entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '*' +--- + +Cuando habilitas la búsqueda unificada, los usuarios pueden ver los resultados de la búsqueda desde contenido público y privado en {% data variables.product.prodname_dotcom_the_website %} cuando buscan desde {% data variables.product.product_location_enterprise %}. + +Los usuarios no podrán buscar {% data variables.product.product_location_enterprise %} desde {% data variables.product.prodname_dotcom_the_website %}, incluso si tienen acceso a ambos entornos. Los usuarios solo pueden buscar repositorios privados para los que hayas habilitado {% data variables.product.prodname_unified_search %} y a los que tengan acceso en las organizaciones conectadas {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "[Acerca de la búsqueda en {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" y "[Habilitar la búsqueda de repositorio privado {% data variables.product.prodname_dotcom_the_website %} en tu cuenta {% data variables.product.prodname_ghe_server %}](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)." + +Buscar a través de las API REST y GraphQL no incluye {% data variables.product.prodname_dotcom_the_website %} los resultados de búsqueda. No están admitidas la búsqueda avanzada y buscar wikis en {% data variables.product.prodname_dotcom_the_website %}. + +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +5. En "Los usuarios pueden buscar {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +6. De manera opcional, en "Users can search private repositories on (Los usuarios pueden buscar repositorios privados en) {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda de repositorios privados en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +### Further reading + +- "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)" diff --git a/translations/es-ES/content/admin/configuration/index.md b/translations/es-ES/content/admin/configuration/index.md new file mode 100644 index 0000000000000..0cf7ef6db2c7c --- /dev/null +++ b/translations/es-ES/content/admin/configuration/index.md @@ -0,0 +1,60 @@ +--- +title: Configurar GitHub Enterprise +shortTitle: Configurar GitHub Enterprise +intro: "Puedes configurar tu empresa para que se ajuste a las necesidades de tu organización." +redirect_from: + - /enterprise/admin/configuration +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Nota:** Para configurar {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %} para tu empresa, consulta la sección "[Administrar GitHub Actions para tu empresa](/admin/github-actions)" o la sección "[Administrar GitHub Packages para tu empresa](/admin/packages)." + +{% endnote %} +{% endif %} + +### Índice + +{% topic_link_in_list /configuring-your-enterprise %} + {% link_in_list /about-enterprise-configuration %} + {% link_in_list /initializing-github-ae %} + {% link_in_list /accessing-the-management-console %} + {% link_in_list /accessing-the-administrative-shell-ssh %} + {% link_in_list /configuring-data-encryption-for-your-enterprise %} + {% link_in_list /enabling-and-scheduling-maintenance-mode %} + {% link_in_list /configuring-backups-on-your-appliance %} + {% link_in_list /site-admin-dashboard %} + {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} + {% link_in_list /configuring-email-for-notifications %} + {% link_in_list /configuring-rate-limits %} + {% link_in_list /configuring-applications %} + {% link_in_list /troubleshooting-ssl-errors %} + {% link_in_list /configuring-time-synchronization %} + {% link_in_list /command-line-utilities %} + {% link_in_list /restricting-network-traffic-to-your-enterprise %} + {% link_in_list /configuring-github-pages-for-your-enterprise %} +{% topic_link_in_list /configuring-network-settings %} + {% link_in_list /configuring-the-ip-address-using-the-virtual-machine-console %} + {% link_in_list /configuring-dns-nameservers %} + {% link_in_list /configuring-a-hostname %} + {% link_in_list /validating-your-domain-settings %} + {% link_in_list /configuring-tls %} + {% link_in_list /enabling-subdomain-isolation %} + {% link_in_list /configuring-an-outbound-web-proxy-server %} + {% link_in_list /configuring-built-in-firewall-rules %} + {% link_in_list /network-ports %} + {% link_in_list /using-github-enterprise-server-with-a-load-balancer %} +{% topic_link_in_list /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud %} + {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} + {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} + {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} + {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} + {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} +{% topic_link_in_list /configuring-advanced-security-features %} + {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/es-ES/content/admin/configuration/initializing-github-ae.md b/translations/es-ES/content/admin/configuration/initializing-github-ae.md new file mode 100644 index 0000000000000..3fc4e757caf33 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/initializing-github-ae.md @@ -0,0 +1,73 @@ +--- +title: Inicializar GitHub AE +intro: 'Para poner a tu empresa lista para operar, puedes completar la configuración inicial de {% data variables.product.product_name %}.' +versions: + github-ae: '*' +--- + +### Acerca de la inicialización + +Antes de que puedas inicializar tue mpresa, debes comprar {% data variables.product.product_name %}. Para obtener más información, contacta a {% data variables.contact.contact_enterprise_sales %}. + +Después de haber comprado {% data variables.product.product_name %}, te pediremos que proporciones una dirección de correo electrónico y nombre de usuario de la persona que desea inicializar la empresa. Tu administrador de cuenta técnico dedicado en {% data variables.contact.enterprise_support %} creará una cuenta para el propietario de la empresa y le enviará un correo electrónico para ingresar en {% data variables.product.product_name %} y completar la inicialización. Asegúrate de que la información que proporciones empate en el IdP con aquella de quien se pretende sea el propietario. Para obtener más información acerca de los propietarios de las empresas, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". + +Durante la inicialización, el propietario de la empresa nombrará a tu empresa, configurará el SSO de SAML, creará políticas para todas las organizaciones dentro de la empresa y configurará un contacto de soporte para tus usuarios. + +### Prerrequisitos + +{% note %} + +**Nota**: Antes de que comiences la inicialización, alamacena el nombre de usuario y contraseña iniciales para {% data variables.product.prodname_ghe_managed %} de forma segura en un administrador de contraseñas. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} + +{% endnote %} + +1. Para inicializar {% data variables.product.product_location %}, debes tener un proveedor de identiddad (IdP) de SAML. {% data reusables.saml.ae-uses-saml-sso %} Para conectar tu IdP a tu empresa durante la inicialización, debes tener tu URL de ID de entidad (SSO) del IdP, URL de ID emisora, y certificado de firma público (cifrado en Base64). Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidades para tu empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)". + + {% note %} + + **Nota**: {% data reusables.saml.create-a-machine-user %} + + {% endnote %} + +2. {% data reusables.saml.assert-the-administrator-attribute %} + +### Iniciar sesión y nombrar a tu empresa + +1. Sigue las instrucciones en tu correo electrónico de bienvenida para llegar a tu empresa. +2. Teclea tus credenciales debajo de "Cambiar contraseña", luego da clic en **Cambiar contraseña**. +3. Debajo de "¿Cómo te gustaría llamar a tu cuenta empresarial?", teclea el nombre de la empresa y luego da clic en **Guardar y continuar**. ![Botón de "Guardar y continuar" para nombrar a una empresa](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) + +### Conectar tu IdP a tu empresa + +Para configurar la autenticación para {% data variables.product.product_name %}, debes proporcionar a {% data variables.product.product_name %} los detalles de tu IdP de SAML. {% data variables.product.company_short %} te recomienda utilizar Azure AD como tu IdP. Para obtener más información, consulta la sección "[Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". + +1. A la derecha de "Configurar tu proveedor de identidad", da clic en **Configurar**. ![Botón de "Configurar" para una configuración de IdP](/assets/images/enterprise/configuration/ae-idp-configure.png) +1. Debajo de "URL de ingreso", copia y pega la URL de tu IdP de SAML. ![Campo de texto para la URL de ingreso del IdP de SAML](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) +1. Debajo de "Emisor", copiay pega la URL emisora para tu IdP de SAML. ![Campo de texto para la URL del emisor del IdP de SAML](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) +1. Debajo de "Certificado público", copia y pega el certificado público para tu IdP de SAML. ![Campo de texto para el certificado público del IdP de SAML](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) +1. Da clic en **Probar la configuración de SAML** para garantizar que la información que ingresaste sea correcta. ![Botón de "Probar la configuración de SAML"](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) +1. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración del IdP](/assets/images/enterprise/configuration/ae-save.png) + +### Configurar las políticas de tu empresa + +El configurar políticas pondrá limitaciones para la administración de repositorios y organizaciones en tu empresa. Estas pueden volver a configurarse después del proceso de inicialización. + +1. A la derecha de "Configurar tus políticas empresariales", da clic en **Configurar**. ![Botón de "Configurar" para la configuración de políticas](/assets/images/enterprise/configuration/ae-policies-configure.png) +2. Debajo de "Permisos Predeterminados de los Repositorios", utiliza el menú desplegable y da clci en un nivel de permisos predeterminado para los repositorios de tu empresa. Si alguien tiene varios medios de acceso a una organización, ya sea indiviudalmente, a través de un equipo, o como un miembro de la misma, el permiso más alto anulará los permisos más bajos. Opcionalmente, para permitir que las organizaciones en tu empresa configuren sus permisos predeterminados para los repositorios, da clic en **Sin políticas** ![Menú desplegable para las opciones de permisos predeterminados del repositorio](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) +3. Debajo de "Creación de repositorios", elige si quieres permitir que los miembros creen repositorios o no. Opcionalmente, para permitir que las organizaciones dentro de tu empresa configuren los permisos, da clic en **Sin políticas**. ![Botón de "Los miembros pueden crear repositorios" para la configuración de las políticas empresariales](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) +4. Debajo de "Bifurcación de repositorios", elige si quieres permitir la bifurcación de repositorios privados e internos. Opcionalmente, para permitir que las organizaciones de tu empresa configuren los permisos, da clic en **Sin políticas** ![Menú desplegable para las opciones de permisos de bifurcación de repositorios](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) +5. Debajo de "invitaciones a los repositorios", elige si los miembros o propietarios de la organización pueden invitar colaboradores a los repositorios. Opcionalmente, para permitir que las organizaciones de tu empresa configuren los permisos, da clic en **Sin políticas** ![Menú desplegable para las opciones de los permisos de invitación a los repositorios](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) +6. Debajo de "Visibilidad predeterminada de los repositorios", utiliza el menú desplegable y da clic en el ajuste de visibilidad predeterminada para los repositorios nuevos. ![Menú desplegable para las opciones de visibilidad predeterminadas de los repositorios](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) +7. Debajo de "Los usuarios pueden crear organizaciones", utiliza el menú desplegable para habilitar o inhabilitar el acceso para la creación de organizaciones para los miembros de la empresa. ![Menú desplegable para las opciones de permisos de creación en las organizaciones](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) +8. Debajo de "subidas forzadas", utiliza el menú desplegable y elige si quieres permitir o bloquear las subidas forzadas. ![Menú desplegable para las opciones de configuración de subidas forzadas](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) +9. Debajo de "Acceso SSH a Git", utiliza el menú desplegable y elige si quieres habilitar el acceso por SSH a Git para todos los repositorios en la empresa. ![Menú desplegable para las opciones de acceso SSH a Git](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) +10. Haz clic en **Save (Guardar)** ![Botón de "Guardar" para la configuración de políticas empresariales](/assets/images/enterprise/configuration/ae-save.png) +11. Opcionalmente, para restablecer todas las selecciones, da clic en "Restablecer a las políticas predeterminadas". ![Enlace para restablecer todas las políticas predeterminadas](/assets/images/enterprise/configuration/ae-reset-default-options.png) + +### Configurar tu contacto de soporte interno + +Puedes configurar el método que tus usuarios utilizarán para contactar a tu equipo de soporte interno. Esto puede volver a configurarse después del proceso de inicialización. + +1. En la parte derecha de "Contacto de soporte interno", da clic en **Configurar**. ![Botón de "Configurar" para la configuración del contacto de soporte interno](/assets/images/enterprise/configuration/ae-support-configure.png) +2. Debajo de "Contacto de soporte interno", selecciona el método para que los usuarios de tu empresa contacten a soporte, a través de una URL o de una dirección de correo electrónico. Posteriormente, teclea la información de contacto para soporte. ![Campo de texto para la URL de contacto de soporte interno](/assets/images/enterprise/configuration/ae-support-link-url.png) +3. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración del contacto de soporte empresarial](/assets/images/enterprise/configuration/ae-save.png) diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000000..d02f27528ec96 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,15 @@ +--- +title: Administrar conexiones entre el servidor de GitHub Enterprise y GitHub Enterprise Cloud +intro: 'Con {% data variables.product.prodname_github_connect %}, puedes compartir determinadas características y datos entre {% data variables.product.product_location_enterprise %} y la cuenta de tu organización u emprendimiento {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}.' +mapTopic: verdadero +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..a595ff97f1ada --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Administrar a GitHub para móviles en tu empresa +intro: Puedes decidir si los usuarios autenticados pueden conectarse a {% data variables.product.product_location %} con {% data variables.product.prodname_mobile %}. +permissions: Los propietarios de las empresas pueden administrar a {% data variables.product.prodname_mobile %} para empresas en {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Acerca de {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} Para obtener más información, consulta la sección "[GitHub para móviles](/github/getting-started-with-github/github-for-mobile)." + +Los miembros de tu empresa pueden utilizar {% data variables.product.prodname_mobile %} para clasificar, colaborar y administrar el trabajo en {% data variables.product.product_location %} desde un dispositivo móvil. Predeterminadamente, {% data variables.product.prodname_mobile %} se encuentra habilitado para {% data variables.product.product_location %}. Puedes permitir o dejar de permitir que los miembros de la empresa utilicen {% data variables.product.prodname_mobile %} para autenticarse en {% data variables.product.product_location %} y accedan a tus datos empresariales. + +### Habilitar o inhabilitar {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. En la barra lateral, da clic en **Móvil**. !["Móvil" en la barra lateral izquierda para la consola de administración de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png) +1. Debajo de "GitHub para móviles", selecciona o deselecciona **Habilitar las apps de GitHub Móvil**. ![Casilla de verificación para "Habilitar las Apps de GitHub Móvil" en la consola de administración de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/configuration/network-ports.md b/translations/es-ES/content/admin/configuration/network-ports.md new file mode 100644 index 0000000000000..c48300f869840 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/network-ports.md @@ -0,0 +1,47 @@ +--- +title: Puertos de red +redirect_from: + - /enterprise/admin/articles/configuring-firewalls/ + - /enterprise/admin/articles/firewall/ + - /enterprise/admin/guides/installation/network-configuration/ + - /enterprise/admin/guides/installation/network-ports-to-open/ + - /enterprise/admin/installation/network-ports + - /enterprise/admin/configuration/network-ports +intro: 'Abre los puertos de red de forma selectiva en base a los servicios de red que necesitas exponer a los administradores, usuarios finales y apoyo de correo electrónico.' +versions: + enterprise-server: '*' +--- + +### Puertos administrativos + +Se requieren algunos puertos administrativos para configurar {% data variables.product.product_location %} y ejecutar determinadas funciones. No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales. + +| Port (Puerto) | Servicio | Descripción | +| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 8443 | HTTPS | {% data variables.enterprise.management_console %} segura basada en la web. Requerida para la instalación y la configuración básicas. | +| 8080 | HTTP | {% data variables.enterprise.management_console %} basada en la web de texto simple. No se requiere excepto que el SSL esté inhabilitado de forma manual. | +| 122 | SSH | Acceso shell para {% data variables.product.product_location %}. Se requiere para abrir las conexiones entrantes de todos los otros nodos en la configuración de alta disponibilidad. El puerto SSH predeterminado (22) está destinado al tráfico de red de la aplicación SSH y Git. | +| 1194/UDP | VPN | Túnel de red de replicación segura en la configuración de alta disponibilidad. Se requiere que esté abierto para todos los otros nodos en la configuración. | +| 123/UDP | NTP | Se requiere para operar el protocolo de tiempo. | +| 161/UDP | SNMP | Se requiere para operar el protocolo de revisión de red. | + +### Puertos de la aplicación para usuarios finales + +Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a las aplicaciones web. + +| Port (Puerto) | Servicio | Descripción | +| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 443 | HTTPS | Acceso a la aplicación web y a Git por HTTPS. | +| 80 | HTTP | Acceso a la aplicación web. Todas las solicitudes se redireccionan al puerto HTTPS cuando se habilita SSL. | +| 22 | SSH | Acceso a Git por SSH. Admite las operaciones clonar, extraer y subir a los repositorios privados y públicos. | +| 9418 | Git | El puerto de protocolo Git admite las operaciones clonar y extraer a los repositorios públicos con comunicación de red desencriptada. {% data reusables.enterprise_installation.when-9418-necessary %} + +{% data reusables.enterprise_installation.terminating-tls %} + +### Puertos de correo electrónico + +Los puertos de correo electrónico deben ser accesibles directamente o por medio de la retransmisión del correo electrónico entrante para los usuarios finales. + +| Port (Puerto) | Servicio | Descripción | +| ------------- | -------- | ---------------------------------------------- | +| 25 | SMTP | Soporte para SMTP con encriptación (STARTTLS). | diff --git a/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md new file mode 100644 index 0000000000000..c7ccec558dfff --- /dev/null +++ b/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -0,0 +1,11 @@ +--- +title: Restringir el tráfico de red en tu empresa +shortTitle: Restringir el tráfico de red +intro: 'Puedes restringir el acceso a tu empresa para las conexiones de direcciones IP específicas.' +versions: + github-ae: '*' +--- + +Predeterminadamente, los usuarios autorizados pueden acceder a tu empresa desde cualquier dirección IP. Puedes restringir el acceso para solo direcciones IP específicas, tales como la ubicación de tu oficina física, si contactas a soporte. + +Contacta a {% data variables.contact.github_support %} y envíales las direcciones IP que deberían tener permiso de acceder a tu empresa. Especifica los rangos de direcciones utilizando el formato estándar de CIDR (Enrutamiento sin Clases entre Dominios, por sus siglas en inglés). {% data variables.contact.github_support %} configurará las reglas de cortafuegos adecuadas para que tu empresa restrinja el acceso por HTTP, SSH, HTTPS, y SMTP. Para obtener más información, consulta la sección "[Recibir ayuda de {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/receiving-help-from-github-support)". diff --git a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md new file mode 100644 index 0000000000000..3a605dfe70379 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md @@ -0,0 +1,204 @@ +--- +title: Tablero de administración del sitio +intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}' +redirect_from: + - /enterprise/admin/articles/site-admin-dashboard/ + - /enterprise/admin/installation/site-admin-dashboard + - /enterprise/admin/configuration/site-admin-dashboard +versions: + enterprise-server: '*' +--- + +Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +### Search + +Aquí puedes iniciar la {{ site.data.variables.enterprise.management_console }} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. + +{% else %} + +### Información de la licencia & buscar + +Consulta esta sección del tablero de administración del sitio para controlar tu licencia {% data variables.product.prodname_enterprise %} actual, para buscar usuarios y repositorios y para consultar el [registro de auditoría](#audit-log). + +{% endif %} + +### {% data variables.enterprise.management_console %} + +Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. + +### Explorar + +Los datos para la [página de tendencia][] de GitHub se calculan en lapsos de tiempo diarios, semanales y mensuales para ambos repositorios y programadores. Puedes ver cuándo estos datos fueron almacenados en caché por última vez y poner en cola las tareas nuevas de cálculo de tendencia desde la sección **Explore (Explorar)**. + +### Registro de auditoría + +{% data variables.product.prodname_enterprise %} mantiene un registro continuo de las acciones auditadas que puedes consultar. + +Por defecto, el registro de auditoría te muestra una lista de todas las acciones auditadas en orden cronológico reverso. Puedes filtrar esta lista al ingresar pares de valores clave en el casillero de texto de **Query (Consulta)** y después hacer clic en **Search (Buscar)**, como se explicó en "[Buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)." + +Para obtener más información acerca de las bitácoras de auditoria en general, consulta "[Bitácoras de Auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". Para encontrar una lista completa de las acciones auditadas, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". + +### Informes + +Si necesitas obtener información sobre los usuarios, organizaciones y repositorios en {% data variables.product.product_location %}, comúnmente extraerías datos JSON a través de la [API de GitHub](/rest). Lamentablemente, es posible que la API no proporcione todos los datos que deseas y se requiera algo de conocimiento técnico para usarla. Este tablero de administración del sitio ofrece una sección de **Reports (Informes)** como una alternativa, haciendo que sea fácil descargar informes CSV con la mayoría de la información que probablemente necesites para los usuarios, las organizaciones y los repositorios. + +Específicamente, puedes descargar informes CSV que enumeren a + +- todos los usuarios +- todos los usuarios que han estado activos dentro del último mes +- todos los usuarios que han estado inactivos durante un mes o más +- todos los usuarios que han sido suspendidos +- todas las organizaciones +- todos los repositorios + +También puedes acceder a estos informes mediante programación a través de una autenticación estándar de HTTP con una cuenta de administrador del sitio. Debes utilizar un token de acceso personal con alcance de `site_admin`. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +Por ejemplo, así es como descargarías el informe "todos los usuarios" utilizando cURL: + +```shell +curl -L -u username:token http(s)://hostname/stafftools/reports/all_users.csv +``` + +Para acceder a otros informes mediante programación, reemplaza `all_users` con `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, o `all_repositories`. + +{% note %} + +**Nota:** La solicitud `curl` inicial devolverá una respuesta 202 HTTP si no hay informes en caché disponibles; se generará un informe en segundo plano. Puedes enviar una segunda solicitud para descargar el informe. Puedes utilizar una contraseña o un token de OAuth con el alcance `site_admin` en lugar de la contraseña. + +{% endnote %} + +#### Informes del usuario + +| Clave | Descripción | +| ------------------------:| --------------------------------------------------------------------------------- | +| `created_at (creado en)` | Cuándo fue creada la cuenta de usuario (como una marca de tiempo ISO 8601) | +| `id` | ID de la cuenta para el usuario o la organización | +| `login` | Nombre de inicio de sesión de la cuenta | +| `email` | Dirección principal de correo electrónico de la cuenta | +| `role` | Si la cuenta es de un usuario administrador o de un usuario común | +| `suspended?` | Si la cuenta ha sido suspendida | +| `last_logged_ip` | La dirección IP más reciente que se registró en la cuenta | +| `repos` | Cantidad de repositorios que posee la cuenta | +| `ssh_keys` | Cantidad de claves SSH registradas en la cuenta | +| `org_memberships` | Cantidad de organizaciones a las que pertenece la cuenta | +| `dormant?` | Si la cuenta está inactiva | +| `last_active` | Cuándo la cuenta estuvo activa por última vez (como una marca de tiempo ISO 8601) | +| `raw_login` | Información de inicio de sesión sin procesar (en formato JSON) | +| `2fa_enabled?` | Si el usuario ha habilitado autenticación de dos factores | + +#### Informes de la organización + +| Clave | Descripción | +| ------------------------:| ------------------------------------------------------------ | +| `id` | ID de la organización | +| `created_at (creado en)` | Cuándo se creó la organización | +| `login` | Nombre de inicio de sesión de la organización | +| `email` | Dirección principal de correo electrónico de la organización | +| `owners` | Cantidad de propietarios de la organización | +| `members` | Cantidad de miembros de la organización | +| `equipos` | Cantidad de equipos de la organización | +| `repos` | Cantidad de repositorios de la organización | +| `2fa_required?` | Si la organización requiere autenticación de dos factores | + +#### Informes del repositorio + +| Clave | Descripción | +| ------------------------:| ------------------------------------------------------------------ | +| `created_at (creado en)` | Cuándo fue creado el repositorio | +| `owner_id` | ID del propietario del repositorio | +| `owner_type` | Si el repositorio es propiedad de un usuario o de una organización | +| `owner_name` | Nombre del propietario del repositorio | +| `id` | ID del repositorio | +| `name (nombre)` | Nombre del repositorio | +| `visibility` | Si el repositorio es público o privado | +| `readable_size` | El tamaño del repositorio en un formato legible | +| `raw_size` | Tamaño del repositorio como un número | +| `collaborators` | Cantidad de colaboradores del repositorio | +| `fork?` | Si el repositorio es una bifurcación | +| `deleted?` | Si el repositorio ha sido borrado | + +### Indexar + +Las funciones de [búsqueda de código][] de GitHub son propulsadas por [ElasticSearch][]. Esta sección del tablero de administración del sitio muestra el estado actual de tu agrupación de ElasticSearch y brinda diversas herramientas para controlar el comportamiento de búsqueda e indexación. Estas herramientas están separadas en las siguientes tres categorías. + +#### Búsqueda de código + +Esto te permite habilitar o deshabilitar tanto las operaciones de búsqueda como de indexación en el código fuente. + +#### Reparación del índice de búsqueda de código + +Esto controla cómo se repara el índice de búsqueda de código. Puedes + +- habilitar o inhabilitar tareas de reparación de índices +- comenzar una nueva tarea de reparación de índice +- restablecer todos los estados de reparación de índices + +{% data variables.product.prodname_enterprise %} utiliza tareas de reparación para compaginar el estado del índice de búsqueda con los datos almacenados en una base de datos (propuestas, solicitudes de extracción, repositorios y usuarios) y los datos almacenados en los repositorios de Git (código fuente). Esto sucede cuando + +- se crea un nuevo índice de búsqueda; +- faltan datos que se deben reponer; o +- los datos de búsqueda antiguos deben ser actualizados. + +En otras palabras, las tareas de reparación se inician según se necesiten y se ejecutan en segundo plano, no están programados por los administradores del sitio de ningún modo. + +Además, las tareas de reparación utilizan una "compensación de reparación" para la paralelización. Esto es una compensación dentro de la tabla de base de datos para el registro que se está compaginando. Múltiples tareas en segundo plano pueden sincronizar el trabajo en base a esta compensación. + +Una barra de progreso muestra el estado actual de la tarea de reparación a través de todos sus trabajadores en segundo plano. Es la diferencia de porcentaje de la compensación de reparación con el ID de registro más alto en la base de datos. No te preocupes sobre el valor que se muestra en la barra de progreso después de que una tarea de reparación se haya completado: ya que muestra la diferencia entre la compensación de reparación y el ID del registro más alto en la base de datos, disminuirá a medida que se agreguen más repositorios a {% data variables.product.product_location %} incluso aquellos repositorios que están de hecho indexados. + +Puedes comenzar una nueva tarea de reparación de índice de búsqueda de código en cualquier momento. Utilizará una CPU única ya que compagina el índice de búsqueda con la base de datos y los datos del repositorio de Git. Para minimizar los efectos que esto tendrá en el desempeño de I/O y reducir las posibilidades de que las operaciones queden inactivas, trata de ejecutar una tarea de reparación durante las horas valle en primer lugar. Controla las cargas promedio de tu sistema y el uso de tu CPU con una herramienta como `top`; si no notas cambios significativos, debería ser seguro ejecutar una tarea de reparación de índice también durante las horas pico. + +#### Reparación de índice de propuestas + +Esto controla de qué manera se repara el [índice de propuestas][]. Puedes + +- habilitar o inhabilitar tareas de reparación de índices +- comenzar una nueva tarea de reparación de índice +- restablecer todos los estados de reparación de índices + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +### Todos los usuarios + +Aquí puedes ver todos los usuarios que han sido suspendidos en {{ site.data.variables.product.product_location_enterprise }}, e [iniciar una auditoría clave de SSH](/enterprise/{{ page.version }}/admin/guides/user-management/auditing-ssh-keys). + +{% endif %} + +### Repositorios + +Es una lista de los repositorios en {% data variables.product.product_location %}. Puedes hacer clic en un nombre de repositorio y acceder a las funciones para administrar el repositorio. + +- [Bloquear empujes forzados en un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) +- [Configurar {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) +- [Archivar y desarchivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) + +### Todos los usuarios + +Aquí puedes ver todos los usuarios en {% data variables.product.product_location %}—, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). + +### Administrador del sitio + +Aquí puedes ver todos los administradores en {% data variables.product.product_location %}, e [iniciar una auditoría clave en SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). + +### Usuarios inactivos + +Aquí puedes ver y [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos los usuarios inactivos en {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: + +- Ha existido durante más tiempo del umbral de inactividad que está establecido para {% data variables.product.product_location %}. +- No ha generado ninguna actividad dentro de ese período. +- No es un administrador del sitio. + +{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} Para obtener más información, consulta "[Administrar usuarios inactivos](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." + +### Usuarios suspendidos + +Aquí puedes ver todos los usuarios que han sido suspendidos en {% data variables.product.product_location %}, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). + + [página de tendencia]: https://github.com/blog/1585-explore-what-is-trending-on-github + + [búsqueda de código]: https://github.com/blog/1381-a-whole-new-code-search + [ElasticSearch]: http://www.elasticsearch.org/ + + [índice de propuestas]: https://github.com/blog/831-issues-2-0-the-next-generation diff --git a/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md new file mode 100644 index 0000000000000..6afc85f200813 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md @@ -0,0 +1,72 @@ +--- +title: Errores de solución de problemas de SSL +intro: 'Si te encuentras con problemas de SSL en tu aparato, puedes tomar medidas para resolverlos.' +redirect_from: + - /enterprise/admin/articles/troubleshooting-ssl-errors/ + - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration/ + - /enterprise/admin/installation/troubleshooting-ssl-errors + - /enterprise/admin/configuration/troubleshooting-ssl-errors +versions: + enterprise-server: '*' +--- + +### Eliminar la contraseña de un archivo clave + +Si tienes una máquina linux con OpenSSL instalado, puedes eliminar tu contraseña. + +1. Renombrar tu archivo clave original. + ```shell + $ mv yourdomain.key yourdomain.key.orig + ``` +2. Generar una nueva clave sin una contraseña. + ```shell + $ openssl rsa -in yourdomain.key.orig -out yourdomain.key + ``` + +Se te pedirá la contraseña de la clave cuando ejecutes este comando. + +Para más información sobre OpenSSL, consulta la documentación de OpenSSL [](https://www.openssl.org/docs/). + +### Convertir tu certificado SSL o tu clave a un formato PEM + +Si tienes instalado OpenSSL, puedes convertir tu clave en formato PEM usando el comando `openssl`. Por ejemplo, puedes convertir una clave de formato DER a formato PEM. + +```shell +$ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM +``` + +De lo contrario, puedes utilizar la herramienta SSL Converter para convertir tu certificado a formato PEM. Para obtener más información, consulta la [Documentación de la herramienta SSL Converter](https://www.sslshopper.com/ssl-converter.html). + +### Instalación sin respuesta después de cargar una clave + +Si {% data variables.product.product_location %} no tiene respuesta después de cargar una clave SSL, contacta [al {% data variables.product.prodname_enterprise %} Soporte](https://enterprise.github.com/support) con detalles específicos, incluida una copia de tu certificado SSL. + +### Errores de validez de certificado + +Los clientes como navegadores web y líneas de comando Git mostrarán un mensaje de error si no pueden verificar la validez de un certificado SSL. Esto sucede con frecuencia con los certificados autofirmados y los certificados de "raíz encadenada" emitidos por un certificado raíz intermedio que no es reconocido por el cliente. + +Si estás usando un certificado firmado por una autoridad de certificación (CA), el archivo del certificado que cargaste a {% data variables.product.prodname_ghe_server %} debe incluir una cadena de certificado con ese certificado raíz de CA. Para crear dicho archivo, concatena tu cadena de certificado entera (o "paquete de certificado") al final de tu certificado, garantizando que el certificado principal con tu nombre del host aparezca primero. En la mayoría de los sistemas puedes hacer esto con un comando similar a: + +```shell +$ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt +``` + +Deberías poder descargar un paquete de certificado (por ejemplo, `bundle-certificates.crt`) desde tu proveedor de SSL o de la autoridad de certificación. + +### Instalar certificados raíz de autoridad de certificación (CA) autofirmados o que no son de confianza + +Si tu aparato {% data variables.product.prodname_ghe_server %} interactúa con otras máquinas en tu red que utilizan un certificado autofirmado o que no es de confianza, deberás importar el certificado raíz de la CA firmante en el almacenamiento de certificado de todo el sistema para poder acceder a estos sistemas por HTTPS. + +1. Obtén el certificado raíz de la CA de tu autoridad de certificación local y asegúrate que esté en formato PEM. +2. Copia el archivo a tu aparato {% data variables.product.prodname_ghe_server %} por SSH como el usuario "administrador" en el puerto 122. + ```shell + $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin + ``` +3. Conecta a la shell administrativa {% data variables.product.prodname_ghe_server %} por SSH como el usuario "administrador" en el puerto 122. + ```shell + $ ssh -p 122 admin@HOSTNAME + ``` +4. Importa el certificado al almacenamiento de certificado de todo el sistema. + ```shell + $ ghe-ssl-ca-certificate-install -c rootCA.crt + ``` diff --git a/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md new file mode 100644 index 0000000000000..74a7d78a7bbd6 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md @@ -0,0 +1,55 @@ +--- +title: Utilizar el servidor de GitHub Enterprise con un balanceador de carga +intro: 'Utiliza un balanceador de carga frente a un aparato único del {% data variables.product.prodname_ghe_server %} o un par de aparatos en una configuración de alta disponibilidad.' +redirect_from: + - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/ + - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer + - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_clustering.load_balancer_intro %} + +{% data reusables.enterprise_clustering.load_balancer_dns %} + +### Manejar información de conexión de clientes + +Debido a que las conexiones de cliente al {% data variables.product.prodname_ghe_server %} provienen del balanceador de carga, se puede perder la dirección IP del cliente. + +{% data reusables.enterprise_clustering.proxy_preference %} + +{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %} + +#### Habilitar soporte para protocolo de PROXY en {% data variables.product.product_location %} + +Recomendamos firmemente habilitar el soporte para protocolo de PROXY para tu aparato y el balanceador de carga. Utiliza las instrucciones provistas por tu proveedor para habilitar el protocolo PROXY en tu balanceador de carga. Para obtener más información, consulta [la documentación de protocolo PROXY](http://www.haproxy.org/download/1.6/doc/proxy-protocol.txt). + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Enable support for PROXY protocol (Habilitar soporte para el protocolo de PROXY)**. ![Casilla de verificación para habilitar el soporte para el protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.enterprise_clustering.proxy_protocol_ports %} + +#### Habilitar soporte para X-Forwarded-For en {% data variables.product.product_location %} + +{% data reusables.enterprise_clustering.x-forwarded-for %} + +{% data reusables.enterprise_installation.terminating-tls %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Allow HTTP X-Forwarded-For header (Permitir encabezados HTTP X-Forwarded-For)**. ![Casilla de verificación para permitir el encabezado de HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.enterprise_clustering.without_proxy_protocol_ports %} + +### Configurar la revisión de estado + +Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si el aparato está fuera de línea debido a un mantenimiento o una falla inesperada, el balanceador de carga puede mostrar una página de estado. En una configuración de alta disponibilidad (HA), un balanceador de carga puede usarse como parte de una estrategia de conmutación por error. Sin embargo, no está admitida la conmutación por error automática de los pares de HA. Debes impulsar de forma manual el aparato réplica antes de que comience con las consultas activas. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." + +{% data reusables.enterprise_clustering.health_checks %} +{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} diff --git a/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md b/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md new file mode 100644 index 0000000000000..0e840b54945d9 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md @@ -0,0 +1,16 @@ +--- +title: Validar tus parámetros de dominio +intro: 'Asegúrate de que tus parámetros de dominio estén configurados adecuadamente antes de arrancar {% data variables.product.product_location %} por primera vez.' +redirect_from: + - /enterprise/admin/installation/validating-your-domain-settings + - /enterprise/admin/configuration/validating-your-domain-settings +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Para probar los parámetros DNS y SSL de tu aparato, haz clic en **Test domain settings (Pruebar parámetros de dominio)**. ![Botón Test domain settings (Probar configuraciones del dominio)](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md b/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md new file mode 100644 index 0000000000000..797eee1d46b41 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md @@ -0,0 +1,70 @@ +--- +title: Acerca de los nodos de agrupación +intro: 'Los "nodos" son instancias de {% data variables.product.prodname_ghe_server %} que operan en una agrupación. Cada nodo ejecuta un conjunto de servicios que se suministra a la agrupación y; por último, a los usuarios.' +redirect_from: + - /enterprise/admin/clustering/about-cluster-nodes + - /enterprise/admin/enterprise-management/about-cluster-nodes +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_clustering.clustering-requires-https %} + +### Recomendaciones mínimas de hardware +Cada nodo debe tener un volumen raíz, así como un volumen de datos separado. Estas son las recomendaciones mínimas. Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas. + +| Servicios | Mínimo de memoria requerida | Mínimo de espacio libre de volumen de datos requerido | +|:----------------------------------------------------------------------------------------------:|:---------------------------:|:-----------------------------------------------------:| +| `job-server`,
    `memcache-server`,
    `web-server` | 14 GB | 1 GB | +| `consul-server`,
    `mysql-server`,
    `redis-server` | 14 GB | 10 GB | +| `git-server`,
    `metrics-server`,
    `pages-server`,
    `storage-server` | 7 GB | 10 GB | +| `elasticsearch-server` | 14 GB | 10 GB | + +### Servicios requeridos para agrupamiento +Para una redundancia adecuada, usa estos nodos mínimos para poner en funcionamiento cada servicio. + +{% tip %} + +**Nota:** Las necesidades de escalabilidad de tu organización dependerán de muchos factores, entre los que se incluyen el tamaño y la cantidad de repositorios, la cantidad de usuarios y la utilización general. + +{% endtip %} + +| Servicios | Mínimo de nodos requeridos | +|:---------------------------------------------------------------------------------------------:|:--------------------------:| +| `job-server`,
    `memcache-server`,
    `metrics-server`,
    `web-server` | 2 | +| `mysql-server`,
    `redis-server` | 2 | +| `consul-server` | 3 | +| `git-server`,
    `pages-server`,
    `storage-server` | 3 | +| `elasticsearch-server` | 3 | + +### Recomendaciones de diseño de agrupación + +La agrupación permite que los servicios que constituyen {% data variables.product.prodname_ghe_server %} experimenten un aumento gradual independientemente de los demás. Esta flexibilidad puede usarse para diseñar e implementar una agrupación que se adapta a las organizaciones con diferentes requisitos de escalabilidad. Por ejemplo, es posible que algunas organizaciones necesiten una mayor capacidad de almacenamiento para extracciones frecuentes o de gran tamaño, pero el uso del servidor web puede ser relativamente bajo. Otra organización puede tener un buen rendimiento con menos recursos de almacenamiento, pero se necesitan más nodos que ejecuten `pages-server` or `elasticsearch-server`. Hay muchas combinaciones diferentes posibles. Trabaja con tu representante de cuenta para determinar la mejor configuración de agrupación para tus necesidades específicas. + +- Esparcir nodos redundantes por todo el hardware independiente. Si compartes su CPU, memoria o dispositivos de almacenamiento, reducirás el rendimiento e introducirás puntos de falla únicos. Los componentes de trabajo en red compartidos también pueden reducir la capacidad y aumentar el riesgo de pérdida de conectividad en caso de una interrupción. +- Uso de almacenamiento rápido. Por lo general, las redes del área de almacenamiento (SAN, por sus siglas en inglés) se optimizan para obtener una máxima utilización de espacio, disponibilidad y tolerancia a fallas, y no un rendimiento absoluto. La agrupación de {% data variables.product.prodname_ghe_server %} brinda redundancia y disponibilidad, y ofrecerá un mejor rendimiento en el almacenamiento más rápido disponible. Se recomienda el almacenamiento SSD local. +- Establecer niveles de nodos que tengan sentido para tu organización. Un ejemplo de configuración: + - Nivel de cara al usuario con dos nodos y los siguientes servicios: + - `web-server` + - `jobs-server` + - `memcache-server` + - Nivel de base de datos con tres nodos y los siguientes servicios: + - `consul-server` + - `mysql-server` + - `redis-server` + - Nivel de búsqueda con tres nodos y el siguiente servicio: + - `elasticsearch-server` + - Nivel de almacenamiento con tres nodos y los siguientes servicios: + - `git-server` + - `pages-server` + - `storage-server` + - `metrics-server` + +#### Ejemplo del diagrama de agrupación +{% note %} + +**Nota: Este es solo un ejemplo.** El diseño de agrupamiento óptimo de tu organización dependerá de tus necesidades exclusivas. Habla con tu representante dedicado o con {% data variables.contact.contact_enterprise_sales %} para que te podamos ayudar a determinar la mejor configuración del clúster. + +{% endnote %} + +Ejemplo de agrupamiento diff --git a/translations/es-ES/content/admin/enterprise-management/about-clustering.md b/translations/es-ES/content/admin/enterprise-management/about-clustering.md new file mode 100644 index 0000000000000..fd40ae65d2555 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/about-clustering.md @@ -0,0 +1,31 @@ +--- +title: Acerca de las agrupaciones +intro: 'La agrupación {% data variables.product.prodname_ghe_server %} permite que los servicios que la componen {% data variables.product.prodname_ghe_server %} sean escalados a múltiples nodos.' +redirect_from: + - /enterprise/admin/clustering/overview + - /enterprise/admin/clustering/about-clustering + - /enterprise/admin/clustering/clustering-overview/ + - /enterprise/admin/enterprise-management/about-clustering +versions: + enterprise-server: '*' +--- + +### Arquitectura de agrupación + +{% data variables.product.prodname_ghe_server %} está compuesto por un conjunto de servicios. En una agrupación, estos servicios se ejecutan en múltiples nodos y las solicitudes son un balanceador de carga entre ellos. Los cambios se almacenan automáticamente con copias redundantes en nodos separados. La mayoría de los servicios son pares iguales con otras instancias del mismo servicio. Las excepciones a esto son los servicios `mysql-server` and `redis-server`. Estos operan con un solo nodo _principal_ o más nodos _réplica_. + +Aprende más sobre los [servicios requeridos para los agrupamientos](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering). + +### ¿Es adecuada la agrupación para mi organización? + +{% data reusables.enterprise_clustering.clustering-scalability %} Sin embargo, la configuración de un agrupación redundante y escalable puede ser compleja y requiere de una planificación cuidadosa. Se deberá planificar esta complejidad adicional para situaciones durante la instalación, situaciones de recuperación ante desastre y actualizaciones. + +{% data variables.product.prodname_ghe_server %} requiere una baja latencia entre los nodos y no está hecho para redundancia en todas las ubicaciones geográficas. + +La agrupación brinda redundancia, pero no pretende reemplazar una configuración de Alta disponibilidad. Para obtener más información, consulta [Configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). Una configuración de conmutación primaria/secundaria es mucho más simple que la agrupación y permitirá satisfacer las necesidades de muchas organizaciones. Para obtener más información, consulta [Diferencias entre agrupación y alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). + +{% data reusables.package_registry.packages-cluster-support %} + +### ¿Cómo obtengo acceso a la agrupación? + +La agrupación está diseñada para situaciones de escalada específica y no pretende ser usada para cada organización. Si te gustaría considerar la agrupación, por favor contacta a tu representante dedicado o a {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md new file mode 100644 index 0000000000000..d2932b5ab43bd --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md @@ -0,0 +1,28 @@ +--- +title: Acerca de la Replicación geográfica +intro: 'La Replicación geográfica en {% data variables.product.prodname_ghe_server %} utiliza múltiples réplicas activas para responder las solicitudes de los centros de datos distribuidos geográficamente.' +redirect_from: + - /enterprise/admin/installation/about-geo-replication + - /enterprise/admin/enterprise-management/about-geo-replication +versions: + enterprise-server: '*' +--- + +Contar con múltiples réplicas puede permitir una menor distancia a la réplica más cercana. Por ejemplo, una organización con oficinas en San Francisco, Nueva York y Londres podrían ejecutar el aparato principal en un centro de datos cercano a Nueva York y dos réplicas en centros de datos cercanos a San Francisco y Londres. Al usar DNS con información de geolocalización, se puede dirigir a los usuarios al servidor disponible más cercano para que accedan a los datos más rápido. Designar como principal el aparato cercano a Nueva York ayuda a reducir la latencia entre los hosts, a diferencia de si se designa como principal el aparato cercano a San Francisco, que tiene mayor latencia con Londres. + +Los proxies de la réplica activa solicitan que no se pueda procesar esta misma para la instancia principal. Las réplicas funcionan como un punto de presencia al terminar todas las conexiones SSL. El tráfico entre los servidores se envía a través de una conexión VPN encriptada, similar a una configuración de dos nodos de alta disponibilidad sin replicación geográfica. + +Las solicitudes de Git y las solicitudes del servidor de archivo, como LFS y las cargas de archivos, se pueden atender directamente desde la réplica sin cargar ningún dato desde el principal. Las solicitudes web siempre se enrutan hacia el principal, pero si la réplica está más cerca del usuario, las solicitudes son más rápidas porque la terminación SSL está más cerca. + +Se solicita un DNS geográfico, como [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), para que la replicación geográfica funcione sin problemas. El nombre del host para la instancia se debe resolver con la réplica más cercana a la ubicación del usuario. + +### Limitaciones + +Escribir solicitudes para la réplica exige que se envíen los datos al principal y a todas las réplicas. Esto significa que el rendimiento de todos los escritos se limita de acuerdo con la replica más lenta, aunque las geo-replicas nuevas pueden poblar la mayoría de sus datos desde geo-replicas existentes co-ubicadas, en vez de desde el primario. La replicación geográfica no le agregará capacidad a una instancia de {% data variables.product.prodname_ghe_server %} ni resolverá problemas de rendimiento relacionados con recursos de CPU o de memoria insuficientes. Si el aparato principal está fuera de línea, las réplicas activas no podrán atender ninguna solicitud de lectura o escritura. + +### Monitorear la configuración de una replicación geográfica + +{% data reusables.enterprise_installation.monitoring-replicas %} + +### Further reading +- "[Crear réplicas de replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" diff --git a/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md new file mode 100644 index 0000000000000..2fcb79cdbe73f --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md @@ -0,0 +1,179 @@ +--- +title: Acerca de la configuración de alta disponibilidad +intro: 'En una configuración de alta disponibilidad, un aparato secundario {% data variables.product.prodname_ghe_server %} totalmente redundante se mantiene en sincronización con el aparato principal mediante la replicación de todos los almacenes de datos importantes.' +redirect_from: + - /enterprise/admin/installation/about-high-availability-configuration + - /enterprise/admin/enterprise-management/about-high-availability-configuration +versions: + enterprise-server: '*' +--- + +Cuando configuras la alta disponibilidad, hay una configuración automática unidireccional, una replicación asincrónica de todos los almacenes de datos (repositorios de Git, MySQL, Redis y Elasticsearch) desde el aparato principal hacia la réplica. + +{% data variables.product.prodname_ghe_server %} admite una configuración activa/pasiva, en la que el aparato réplica se ejecuta como en un modo de espera con los servicios de base de datos ejecutándose en modo de replicación, pero con los servicios de aplicación detenidos. + +### Escenarios de fallas específicas + +Utiliza la configuración de alta disponibilidad para la protección contra lo siguiente: + +{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %} + +Una configuración de alta disponibilidad no es una buena solución para lo siguiente: + + - **Escalar**. Mientras que puede distribuir el tráfico geográficamente utilizando la replicación geográfica, el rendimiento de las escrituras queda limitado a la velocidad y la disponibilidad del aparato principal. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." + - **Generar copias de seguridad de tu aparato principal**. Una réplica de alta disponibilidad no reemplaza las copias de seguridad externas en tu plan de recuperación ante desastres. Algunas formas de corrupción o pérdida de datos se pueden replicar de inmediato desde el aparato principal hacia la réplica. Para asegurar una reversión segura a un estado antiguo estable, debes realizar copias de seguridad de rutina con instantáneas históricas. + - **Actualizaciones del tiempo de inactividad en cero**. Para evitar la pérdida de datos y las situaciones de cerebro dividido en escenarios de promoción controlados, coloca el aparato principal en el modo de mantenimiento y espera a que se completen todas las escrituras entes de promover la réplica. + +### Estrategias de conmutación por error del tráfico de red + +Durante la conmutación por error, debes configurar por separado y administrar el tráfico de red de redireccionamiento desde el aparato principal hacia la réplica. + +#### Conmutación por error de DNS + +Con la conmutación por error de DNS, utiliza valores TTL cortos en los registros DNS que se dirijan al aparato principal {% data variables.product.prodname_ghe_server %}. Recomendamos un TTL de entre 60 segundos y cinco minutos. + +Durante la conmutación por error, debes colocar el aparato principal en modo de mantenimiento y redirigir sus registros DNS hacia la dirección IP del aparato réplica. El tiempo necesario para redirigir el tráfico desde el aparato principal hacia la réplica dependerá de la configuración TTL y del tiempo necesario para actualizar los registros DNS. + +Si estás utilizando la replicación geográfica, debes configurar Geo DNS en tráfico directo hacia la réplica más cercana. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." + +#### Balanceador de carga + +{% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} + +Durante la conmutación por error, debes colocar el aparato principal en el modo de mantenimiento. Puedes configurar el balanceador de carga para que detecte automáticamente cuando la réplica se haya promovido a principal, o puede que se requiera un cambio de configuración manual. Debes promover manualmente la réplica a principal antes de que responda al tráfico de usuarios. Para obtener más información, consulta "[Utilizar {% data variables.product.prodname_ghe_server %} con un balanceador de carga](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." + +{% data reusables.enterprise_installation.monitoring-replicas %} + +### Utilidades para la administración de la replicación + +Para administrar la replicación en {% data variables.product.prodname_ghe_server %}, haz uso de estas utilidades de la línea de comando conectándote al aparato réplica con SSH. + +#### ghe-repl-setup + +El comando `ghe-repl-setup` coloca un aparato {% data variables.product.prodname_ghe_server %} en modo de espera de réplica. + + - Un tunel de VPN de WireGuard cifrado se configura para establecer la comunicación entre los dos aplicativos. + - Se configuran los servicios de bases de datos para la replicación y se inician. + - Se inhabilitan los servicios de aplicaciones. Los intentos de acceder al aparato réplica por HTTP, Git u otros protocolos compatibles generarán una página de mantenimiento o un mensaje de error de "aparato en modo réplica". + +```shell +admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1 +Verificar la conectividad ssh con 169.254.1.1 ... +Comprobación de conexión exitosa. +Configurando la replicación de base de datos en oposición al principal... +Success: Replica mode is configured against 169.254.1.1. +To disable replica mode and undo these changes, run `ghe-repl-teardown'. +Ejecuta `ghe-repl-start' para comenzar la replicación en oposición al principal recientemente configurado. +``` + +#### ghe-repl-start + +El comando `ghe-repl-start` inicia la replicación activa de todos los almacenes de datos. + +```shell +admin@169-254-1-2:~$ ghe-repl-start +Starting MySQL replication ... +Iniciando la replicación de Redis... +Iniciando la replicación de ElasticSearch... +Iniciando la replicación de Páginas... +Iniciando la replicación de Git... +Exitoso: La replicación se está ejecutando para todos los servicios. +Utiliza `ghe-repl-status' para monitorear el estado y el progreso de la replicación. +``` + +#### ghe-repl-status + +El comando `ghe-repl-status` muestra un estado de `OK`, `ADVERTENCIA` o `CRÍTICO` para cada corriente de replicación de almacén de datos. Cuando cualquiera de los canales de replicación está en estado `ADVERTENCIA`, el comando se cerrará con el código `1`. Del mismo modo, cuando cualquiera de los canales esté en un estado `CRÍTICO`, el comando se cerrará con el código `2`. + +```shell +admin@169-254-1-2:~$ ghe-repl-status +OK: replicación de mysql en sinc +OK: la replicación de redis está en sinc +OK: la agrupación de elasticsearch está en sinc +OK: los datos de git están en sinc (10 repos, 2 wikis, 5 gists) +OK: los datos de páginas están en sinc +``` + +Las opciones `-v` y `-vv` dan detalles sobre cada uno de los estados de replicación de almacén de datos: + +```shell +$ ghe-repl-status -v +OK: replicación de mysql en sinc + | IO en ejecución: Sí, SQL en ejecución: Sí, Demora: 0 + +OK: la replicación de redis está en sinc + | master_host:169.254.1.1 + | master_port:6379 + | master_link_status:up + | master_last_io_seconds_ago:3 + | master_sync_in_progress:0 + +OK: la agrupación de elasticsearch está en sinc + | { + | "cluster_name" : "github-enterprise", + | "status" : "green", + | "timed_out" : falso, + | "number_of_nodes" : 2, + | "number_of_data_nodes" : 2, + | "active_primary_shards" : 12, + | "active_shards" : 24, + | "relocating_shards" : 0, + | "initializing_shards" : 0, + | "unassigned_shards" : 0 + | } + +OK: los datos de git están en sinc (366 repos, 31 wikis, 851 gists) + | TOTAL OK FALLA PENDIENTE CON DEMORA + | repositorios 366 366 0 0 0.0 + | wikis 31 31 0 0 0.0 + | gists 851 851 0 0 0.0 + | total 1248 1248 0 0 0.0 + +OK: los datos de páginas están en sinc + | Las páginas están en sinc +``` + +#### ghe-repl-stop + +El comando `ghe-repl-stop` inhabilita temporalmente la replicación de todos los almacenes de datos y detiene los servicios de replicación. Para reanudar la replicación, utiliza el comando [ghe-repl-start](#ghe-repl-start). + +```shell +admin@168-254-1-2:~$ ghe-repl-stop +Deteniendo la replicación de Páginas... +Deteniendo la replicación de Git... +Deteniendo la replicación de MySQL... +Deteniendo la replicación de Redis... +Deteniendo la replicación de ElasticSearch... +Exitoso: la replicación se detuvo para todos los servicios. +``` + +#### ghe-repl-promote + +El comando `ghe-repl-promote` inhabilita la replicación y convierte el aparato réplica en principal. El aparato se configura con los mismos ajustes que el principal original y se habilitan todos los servicios. + +{% data reusables.enterprise_installation.promoting-a-replica %} + +```shell +admin@168-254-1-2:~$ ghe-repl-promote +Habilitando el modo de mantenimiento en el aparato principal para evitar escrituras... +Deteniendo la replicación... + | Deteniendo la replicación de Páginas... + | Deteniendo la replicación de Git... + | Deteniendo la replicación de MySQL... + | Deteniendo la replicación de Redis... + | Deteniendo la replicación de ElasticSearch... + | Exitoso: la replicación se detuvo para todos los servicios. +Cambiando del modo réplica... + | Exitoso: se eliminó la configuración de la replicación. + | Ejecuta `ghe-repl-setup' para volver a habilitar el modo réplica. +Aplicando la configuración e iniciando los servicios... +Exitoso: la réplica se promovió a principal y ahora está aceptando solicitudes. +``` + +#### ghe-repl-teardown + +El comando `ghe-repl-teardown` inhabilita el modo de replicación por completo, eliminando la configuración de la réplica. + +### Further reading + +- "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" diff --git a/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md new file mode 100644 index 0000000000000..883537014853c --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md @@ -0,0 +1,33 @@ +--- +title: Acceder al tablero del monitor +intro: '{% data variables.product.prodname_ghe_server %} incluye un tablero de monitoreo en la web que muestra los datos históricos sobre tu aparato {% data variables.product.prodname_ghe_server %}, como la CPU y el uso del almacenamiento, los tiempos de respuesta de la aplicación y de la autenticación y la salud general del sistema.' +redirect_from: + - /enterprise/admin/installation/accessing-the-monitor-dashboard + - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard +versions: + enterprise-server: '*' +--- + +### Acceder al tablero del monitor + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. En la parte superior de la página, haga clic en **Monitor**. ![Enlace al Tablero del monitor](/assets/images/enterprise/management-console/monitor-dash-link.png) + +### Solucionar problemas de la asignación de los recursos comunes en su aparato + +{% note %} + +**Nota**: Porque el sondeo regular de {% data variables.product.product_location %} con integración continua (CI) o la construcción de servidores puede causar efectivamente un rechazo del ataque al servicio que genera problemas, te recomendamos que utilice webhooks para subir las actualizaciones. Para obtener más información, consulte "[Acerca de webhooks](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)". + +{% endnote %} + +Utiliza el tablero del monitor para mantenerse informado sobre la salud del recurso de su aparato y tomar decisiones sobre cómo corregir los problemas de alto uso. + +| Problema | Posible(s) causa(s) | Recomendaciones | +| ------------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Alto uso de la CPU | Conexión a la VM desde otros servicios o programas que se ejecutan en el mismo host | De ser posible, vuelve a configurar los otros servicios o programas para utilizar menos recursos de la CPU. Para aumentar los recursos totales de la CPU para la VM, consulte "[Aumentar los recursos de CPU o de memoria](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| Alto uso de la memoria | Conexión a la VM desde otros servicios o programas que se ejecutan en el mismo host | De ser posible, vuelve a configurar otros servicios o programas para utilizar menos memoria. Para aumentar la memoria total disponible en la VM, consulta "[Aumentar los recursos de CPU o de memoria](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| Baja disponibilidad de espacio en el disco | Binarios grandes o archivos de registro que consumen espacio del disco | De ser posible, aloje los binarios grandes en un servidor separado y comprima o archive los archivos de registro. De ser necesario, aumenta el espacio del disco en la VM siguiendo los pasos de tu plataforma en "[Aumentar la capacidad de almacenamiento](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity/)." | +| Tiempos de respuesta más altos que lo común | Los suelen causar alguna de las propuestas anteriores | Identifica y corrige las propuestas subyacentes. Si los tiempos de respuesta siguen altos, contáctate con {% data variables.contact.contact_ent_support %}. | +| Índices de error elevados | Propuestas de software | Contáctate con {% data variables.contact.contact_ent_support %} e incluye tu paquete de soporte. Para obtener más información, consulta "[Proporcionar datos para {% data variables.product.prodname_enterprise %} Asistencia](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." | diff --git a/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md b/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md new file mode 100644 index 0000000000000..f8a28f5cf91d3 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md @@ -0,0 +1,123 @@ +--- +title: Configuración de la red de agrupaciones +intro: 'La agrupación de {% data variables.product.prodname_ghe_server %} se basa en la resolución de nombre de DNS pertinente, balanceo de carga y comunicación entre los nodos para operar de manera adecuada.' +redirect_from: + - /enterprise/admin/clustering/cluster-network-configuration + - /enterprise/admin/enterprise-management/cluster-network-configuration +versions: + enterprise-server: '*' +--- + +### Consideraciones de red + +El diseño de red más simple para una agrupación es colocar los nodos en una LAN única. Si un clúster debe abarcar subredes, no te recomendamos configurar ninguna regla de firewall entre ellas. La latencia entre nodos debe ser de menos de 1 milisegundo. + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Para establecer la disponibilidad alta, la latencia entre la red con los nodos activos y aquella con los pasivos debe ser de menos de 70 milisegundos. No te recomendamos configurar una firewall entre las dos redes.{% endif %} + +#### Puertos de la aplicación para usuarios finales + +Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a las aplicaciones web. + +| Port (Puerto) | Descripción | Cifrado | +|:------------- |:------------------------------------------------------------------------- |:---------------------------------------------------------------------- | +| 22/TCP | Git sobre SSH | Sí | +| 25/TCP | SMTP | Requiere STARTTLS | +| 80/TCP | HTTP | No
    (Cuando SSL está habilitado, este puerto redirige a HTTPS) | +| 443/TCP | HTTPS | Sí | +| 9418/TCP | Puerto de protocolo de Git simple
    (Inhabilitado en modo privado) | No | + +#### Puertos administrativos + +No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales. + +| Port (Puerto) | Descripción | Cifrado | +|:------------- |:--------------------------- |:---------------------------------------------------------------------- | +| ICMP | Ping de ICMP | No | +| 122/TCP | SSH administrativo | Sí | +| 161/UDP | SNMP | No | +| 8080/TCP | Consola de gestión HTTP | No
    (Cuando SSL está habilitado, este puerto redirige a HTTPS) | +| 8443/TCP | Consola de gestión de HTTPS | Sí | + +#### Puertos de comunicación de agrupación + +Si un cortafuego de nivel de red se coloca entre los nodos estos puertos deberán estar accesibles. La comunicación entre los nodos no está cifrada. Estos puertos no deberían estar accesibles externamente. + +| Port (Puerto) | Descripción | +|:------------- |:------------------------------------- | +| 1336/TCP | API interna | +| 3033/TCP | Acceso SVN interno | +| 3037/TCP | Acceso SVN interno | +| 3306/TCP | MySQL | +| 4486/TCP | Acceso del gobernador | +| 5115/TCP | Respaldo de almacenamiento | +| 5208/TCP | Acceso SVN interno | +| 6379/TCP | Redis | +| 8001/TCP | Grafana | +| 8090/TCP | Acceso a GPG interno | +| 8149/TCP | Acceso al servidor de archivos GitRPC | +| 8300/TCP | Consul | +| 8301/TCP | Consul | +| 8302/TCP | Consul | +| 9000/TCP | Git Daemon | +| 9102/TCP | Servidor de archivos de páginas | +| 9105/TCP | Servidor LFS | +| 9200/TCP | ElasticSearch | +| 9203/TCP | Servicio de código semántico | +| 9300/TCP | ElasticSearch | +| 11211/TCP | Memcache | +| 161/UDP | SNMP | +| 8125/UDP | Statsd | +| 8301/UDP | Consul | +| 8302/UDP | Consul | +| 25827/UDP | Collectd | + +### Configurar un balanceador de carga + + Recomendamos un balanceador de carga externo basado en TCP que respalde el protocolo PROXY para distribuir el tráfico a través de los nodos. Considera estas configuraciones del balanceador de carga: + + - Los puertos TCP (que se muestra a continuación) deberán ser reenviados a los nodos que ejecutan el servicio `web-server`. Estos son los únicos nodos que sirven a las solicitudes de clientes externos. + - Las sesiones pegajosas no deberían habilitarse. + +{% data reusables.enterprise_installation.terminating-tls %} + +### Manejar información de conexión de clientes + +Dado que las conexiones de clientes con el agrupamiento provienen del balanceador de carga, no se puede perder la dirección IP de cliente. Para capturar adecuadamente la información de la conexión de clientes, se requiere una consideración adicional. + +{% data reusables.enterprise_clustering.proxy_preference %} + +{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %} + +#### Habilitar el soporte PROXY en {% data variables.product.prodname_ghe_server %} + +Recomendamos firmemente habilitar el soporte PROXY para tu instancia y el balanceador de carga. + + - Para tu instancia, usa este comando: + ```shell + $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply + ``` + - Para el balanceador de carga, usa las instrucciones proporcionadas por tu proveedor. + + {% data reusables.enterprise_clustering.proxy_protocol_ports %} + +#### Habilitar el soporte X-Forwarded-For en {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_clustering.x-forwarded-for %} + +Para habilitar el encabezado `X-Fowarded-For`, usa este comando: + +```shell +$ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply +``` + +{% data reusables.enterprise_clustering.without_proxy_protocol_ports %} + +#### Configurar revisiones de estado +Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si un nodo de agrupación falla, las revisiones de estado emparejadas con nodos redundantes brindan alta disponibilidad. + +{% data reusables.enterprise_clustering.health_checks %} +{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} + +### Requisitos de DNS + +{% data reusables.enterprise_clustering.load_balancer_dns %} diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md new file mode 100644 index 0000000000000..045565d9330cc --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md @@ -0,0 +1,13 @@ +--- +title: Configurar el agrupamiento +intro: Aprende sobre agrupaciones y diferencias con alta disponibilidad. +redirect_from: + - /enterprise/admin/clustering/setting-up-the-cluster-instances + - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster + - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/ + - /enterprise/admin/enterprise-management/configuring-clustering +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md b/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md new file mode 100644 index 0000000000000..c3ab9d1586495 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md @@ -0,0 +1,58 @@ +--- +title: Configurar collectd +intro: '{% data variables.product.prodname_enterprise %} puede reunir datos con `collectd` y enviarlos a un servidor `collectd` externo. Entre otras métricas, reunimos un conjunto estándar de datos, como la utilización de la CPU, el consumo de memoria y de disco, el tráfico y los errores de la interfaz de red y la carga general de la VM.' +redirect_from: + - /enterprise/admin/installation/configuring-collectd + - /enterprise/admin/articles/configuring-collectd/ + - /enterprise/admin/enterprise-management/configuring-collectd +versions: + enterprise-server: '*' +--- + +### Configura un servidor `collectd` externo + +Si aún no has configurado un servidor `collectd` externo, tendrás que hacerlo antes de habilitar el redireccionamiento `collectd` en {% data variables.product.product_location %}. Tu servidor `collectd` debe ejecutar la versión 5.x o superior de `collectd`. + +1. Inicia sesión en tu servidor `collectd`. +2. Crea o edita el archivo de configuración `collectd` para cargar el plugin de red y completar las directivas del servidor y del puerto con los valores adecuados. En la mayoría de las distribuciones, este se ubica en `/etc/collectd/collectd.conf` + +Un ejemplo *collectd.conf* para ejecutar un servidor `collectd`: + + Red LoadPlugin + ... + ... + + Escucha "0.0.0.0" "25826" + + +### Habilita el redireccionamiento collectd en {% data variables.product.prodname_enterprise %} + +Por defecto, el redireccionamiento `collectd` está inhabilitado en {% data variables.product.prodname_enterprise %}. Sigue los pasos que aparecen a continuación para habilitar y configurar el redireccionamiento `collectd`: + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. A continuación aparecen los ajustes de redireccionamiento, selecciona **Enable collectd forwarding** (Habilitar el redireccionamiento collectd). +1. En el campo **Server addres** (Dirección del servidor), escribe la dirección del servidor `collectd` al cual quisieras redirreccionar las estadísticas del aparato {% data variables.product.prodname_enterprise %}. +1. En el campo **Port** (Puerto), escribe el puerto utilizado para canectarse al servidor `collectd`. (Predeterminados en 25826) +1. En el menú desplegable **Cryptographic setup** (Configuración criptográfica), selecciona el nivel de seguridad de las comunicaciones con el servidor `collectd`. (Ninguno, paquetes firmados o paquetes encriptados). +{% data reusables.enterprise_management_console.save-settings %} + +### Exportar los datos collectd con `ghe-export-graphs` + +La herramienta de la línea de comando `ghe-export-graphs` exportará los datos que `collectd` almacene en las bases de datos RRD. Este comando convierte los datos a XML y los exporta a un tarball único (.tgz). + +Su uso principal es proporcionarle al equipo de {% data variables.contact.contact_ent_support %} los datos sobre el desempeño de una VM, sin la necesidad de descargar un paquete de soporte completo. No se debe incluir en tus exportaciones de copias de seguridad regulares y no existe una contraparte de importación. Si te contactas con {% data variables.contact.contact_ent_support %}, puede que te solicitemos estos datos para ayudarte a solucionar los problemas. + +#### Uso + +```shell +ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz . +``` + +### Solución de problemas + +#### El servidor collectd central no recibe datos + +{% data variables.product.prodname_enterprise %} viene con la versión 5.x de `collectd`. `collectd` 5.x no es retrocompatible con la serie de lanzamientos 4.x. Tu servidor `collectd` central debe tener al menos la versión 5.x para aceptar los datos que se envían desde {% data variables.product.product_location %}. + +Para obtener ayuda con más preguntas o problemas, contacta a {% data variables.contact.contact_ent_support %}. diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md new file mode 100644 index 0000000000000..1868471de9a2d --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -0,0 +1,362 @@ +--- +title: Configurar la replicación con disponibilidad alta para un clúster +intro: 'Puedes configurar una réplica pasiva de todo tu clúster de {% data variables.product.prodname_ghe_server %} en una ubicación diferentes, lo cual le permitirá tolerar fallos en nodos redundantes.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster +versions: + enterprise-server: '>2.21' +--- + +### Acerca de la replicación de disponibilidad alta para clústers + +Puedes configurar el despliegue de un clúster de {% data variables.product.prodname_ghe_server %} para que tenga disponibilidad alta, mientras que un conjunto idéntico de nodos pasivos se sincroniza con los nodos en tu clúster activo. Si los fallos de hardware o de software afectan el datacenter que tiene tu clúster activo, puedes conmutar por error a los nódos de réplica y continuar procesando las solicitudes de los usuarios sin perder datos. + +En el modo de alta disponibilidad, cada nodo activo se sincroniza regularmente con un nodo pasivo correspondiente. El nodo pasivo se ejecuta en espera y no sirve a las aplicaciones ni procesa solicitudes de usuarios. + +Te recomendamos configurar la disponibilidad alta como parte de un plan integral de recuperación de desastres para {% data variables.product.prodname_ghe_server %}. También te recomendamos realizar respaldos constantemente. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/configuration/configuring-backups-on-your-appliance)" + +### Prerrequisitos + +#### Hardware y software + +Para cada nodo existente en tu clúster activo, necesitarás aprovisionar una segunda máquina virtual con recursos de hardware idénticos. Por ejemplo, si tu clúster tiene 11 nodos y cada nodo tiene 12 vCPUs, 96 GB de RAM, y 750 GB de almacenamiento adjunto, deberás aprovisionar 11 máquinas virtuales en donde cada una tenga 12 vCPUs, 64 GB de RAM, y 750GB de almacenamiento adjunto. + +En cada máquina virtual, instala la misma versión de {% data variables.product.prodname_ghe_server %} que se ejecuta en los nodos en tu clúster activo. No necesitas cargar una licencia ni realizar alguna configuración adicional. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)." + +{% note %} + +**Nota**: Los nodos que pretendes utilizar para la replicación de disponibilidad alta deben ser instancias independientes de {% data variables.product.prodname_ghe_server %}. No inicialices los nodos pasivos como un segundo clúster. + +{% endnote %} + +#### Red + +Debes asignar una dirección IP estática a cada nodo nuevo que aprovisiones, y debes configurar un balanceador de carga para aceptar las conecciones y dirigirlas a los nodos que están a nivel del front-end de tu clúster. + +No te recomendamos configurar un firewall entre la red con con tu clúster activo y aquella con tu clúster pasivo. Lalatencia entre las redes con nodos activos y aquellas con nodos pasivos debe ser de menos de 70 milisegundos. Para obtener más información acerca de la conectividad de red entre nodos en el clúster pasivo, consulta la sección "[Configuración de clúster de red](/enterprise/admin/enterprise-management/cluster-network-configuration)". + +### Crear una réplica de disponibilidad alta para un clúster + +- [Asignar nodos activos al datacenter primario](#assigning-active-nodes-to-the-primary-datacenter) +- [Agregar nodos pasivos al archivo de configuración de clúster](#adding-passive-nodes-to-the-cluster-configuration-file) +- [Ejemplo de configuración](#example-configuration) + +#### Asignar nodos activos al datacenter primario + +Antes de que definas un datacenter secundario para tus nodos pasivos, asegúrate de que has asignado tus nodos activos al datacenter primario. + +{% data reusables.enterprise_clustering.ssh-to-a-node %} + +{% data reusables.enterprise_clustering.open-configuration-file %} + +3. Observa el nombre del datacenter primario de tus clústers. La sección de `[cluster]` en la parte superior del archivo de configuración del clúster define el nombre del datacenter primario, utilizando el par de clave-valor `primary-datacenter`. Predeterminadamente, el datacenter primario para tu clúster se llama `default`. + + ```shell + [cluster] + mysql-master = HOSTNAME + redis-master = HOSTNAME + primary-datacenter = default + ``` + + - Opcionalmente, cambia el nombre del datacenter primario a uno más descriptivo o preciso editando el valor de `primary-datacenter`. + +4. {% data reusables.enterprise_clustering.configuration-file-heading %} Debajo del encabezado de cada nodo, agrega un par de clave-valor para asignar el nodo a un datacenter. Utiliza el mismo valor que `primary-datacenter` desde el paso 3 en adelante. Por ejemplo, si quieres utilizar el nombre predeterminado (`default`), agrega el siguiente par de clave-valor a la sección para cada nodo. + + ``` + datacenter = default + ``` + + Cuando hayas terminado, la sección para cada nodo en el archivo de configuración del clúster se debería ver como en el siguiente ejemplo. {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %} + + ```shell + [cluster "HOSTNAME"] + datacenter = default + hostname = HOSTNAME + ipv4 = IP ADDRESS + ... + ... + ``` + + {% note %} + + **Nota**: Si cambiaste el nombre del datacenter primario en el paso 3, encuentra el par de clave-valor para `consul-datacenter` en la sección para cada nodo y cambia el valor al datacenter primario que renombraste. Por ejemplo, si nombraste al datacenter primario como `primary`, utiliza el siguiente par de clave-valor para cada nodo. + + ``` + consul-datacenter = primary + ``` + + {% endnote %} + +{% data reusables.enterprise_clustering.apply-configuration %} + +{% data reusables.enterprise_clustering.configuration-finished %} + +Después de que {% data variables.product.prodname_ghe_server %} te regrese al prompt, habrás terminado de asignar tus nodos al datacenter primario del clúster. + +#### Agregar nodos pasivos al archivo de configuración de clúster + +Para configurar la disponibilidad alta, debes definir un nodo pasivo correspondiente para cada nodo activo en tu clúster. Con las siguientes instrucciones se crea una configuración de clúster nueva que define tanto los nodos activos como los pasivos. Lo que harás: + +- Crear una copia del archivo de configuración del clúster activo. +- Editar la copia para definir los nodos pasivos que corresponden a los nodos activos, agregando las direcciones IP de las máquinas virtuales nuevas que aprovisionaste. +- Fusionar la copia modificada de la configuración del clúster con tu configuración activa. +- Aplicar la configuración nueva para comenzar la replicación. + +Para ver un ejemplo de configuración, consulta la sección "[Ejemplo de configuración](#example-configuration)". + +1. Para cada nodo en tu clúster, aprovisiona una máquina virtual coincidente con especificaciones idénticas que ejecute la misma versión de {% data variables.product.prodname_ghe_server %}. Anota la dirección IPv4 y el nombre de host para cada nodo de clúster nuevo. Para obtener más información, consulta la sección "[Prerrequisitos](#prerequisites)". + + {% note %} + + **Nota**: Si estás reconfigurando la disponibilidad alta después de una recuperación de un fallo, puedes utilizar los nodos viejos del datacenter primario en su lugar. + + {% endnote %} + +{% data reusables.enterprise_clustering.ssh-to-a-node %} + +3. Respalda tu configuración de clúster existente. + + ``` + cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup + ``` + +4. Crea una copia de tu archivo de configuración de clúster en una ubicación temporal, como _/home/admin/cluster-passive.conf_. Borra los pares únicos de clave-valor para las direcciones IP (`ipv*`), las UUID (`uuid`), y las llaves públicas para WireGuard (`wireguard-pubkey`). + + ``` + grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf + ``` + +5. Elimina la sección de `[cluster]` del archivo temporal de configuración de clúster que copiaste en el paso anterior. + + ``` + git config -f ~/cluster-passive.conf --remove-section cluster + ``` + +6. Asigna un nombre para el datacenter secundario en donde aprovisionaste tus nodos pasivos, luego actualiza el archivo temporal de configuración de clúster con el nombre nuevo del datacenter. Reemplaza `SECONDARY` con el nombre que elegiste. + + ```shell + sed -i 's/datacenter = default/datacenter = SECONDARY/g' ~/cluster-passive.conf + ``` + +7. Asigna un patrón para los nombres de host del nodo pasivo. + + {% warning %} + + **Advertencia**: Los nombres de host para los nodos pasivos deben ser únicos y diferir del nombre de host para el nodo activo correspondiente. + + {% endwarning %} + +8. Abre el archivo temporal de configuración de clúster del paso 3 en un editor de texto. Por ejemplo, puedes utilizar Vim. + + ```shell + sudo vim ~/cluster-passive.conf + ``` + +9. En cada sección dentro del archivo temporal de configuración del clúster, actualiza la configuración del nodo. {% data reusables.enterprise_clustering.configuration-file-heading %} + + - Cambia el nombre de host citado en el encabezado de la sección y el valor de `hostname` dentro de la sección al nombre de host del nodo pasivo, de acuerdo con el patrón que elegiste en el paso 7 antes mencionado. + - Agrega una nueva clave llamada `ipv4`, y configura el valor como la dirección IPv4 estática del nodo pasivo. + - Agrega un par de clave-valor nuevo, `replica = enabled`. + + ```shell + [cluster "NEW PASSIVE NODE HOSTNAME"] + ... + hostname = NEW PASSIVE NODE HOSTNAME + ipv4 = NEW PASSIVE NODE IPV4 ADDRESS + replica = enabled + ... + ... + ``` + +10. Anexa el contenido del archivo temporal de configuración del clúster que creaste en el paso 4 al archivo de configuración activo. + + ```shell + cat ~/cluster-passive.conf >> /data/user/common/cluster.conf + ``` + +11. Designa los nodos de Redis y de MySQL en el datacenter secundario. Reemplaza `REPLICA MYSQL PRIMARY HOSTNAME` y `REPLICA REDIS PRIMARY HOSTNAME` con los nombres de host de los nodos pasivos que aprovisionaste para que empaten con tus primarios existentes de MySQL y de Redis. + + ```shell + git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA MYSQL PRIMARY HOSTNAME + git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA REDIS PRIMARY HOSTNAME + ``` + +12. Habilita MySQL para conmutar por error automáticamente cuando hagas una recuperación de errores hacia los nodos pasivos de réplica. + + ```shell + git config -f /data/user/common/cluster.conf cluster.mysql-auto-failover true + ``` + + {% warning %} + + **Advertencia**: Revisa tu archivo de configuración de clúster antes de proceder. + + - En la sección de `[cluster]` de nivel superior, asegúrate de que los valores para `mysql-master-replica` y para `redis-master-replica` sean los nombres de host correctos para los nodos pasivos en el datacenter secundario que servirán como los primarios de MySQL y de Redis después de una conmutación por error. + - En cada sección para un nodo activo que se llame `[cluster "ACTIVE NODE HOSTNAME"]`, vuelve a revisar los siguientes pares de clave-valor. + - `datacenter` debería coincidir con el valor de `primary-datacenter` en la sección de `[cluster]` de nivel superior. + - `consul-datacenter` debería coincidir con el valor de `datacenter`, cl cual debería ser el mismo valor para `primary-datacenter` en la sección de `[cluster]` de nivel superior. + - Asegúrate de que, para cada nodo activo, la configuración tenga **una** sección correspondiente para **un** nodo pasivo con los mismos roles. En cada sección para un nodo pasivo, verifica nuevamente cada par de clave-valor. + - `datacenter` debería coincidir con todo el resto de los nodos pasivos. + - `consul-datacenter` debería coincidir con todo el resto de los nodos pasivos. + - `hostname` debería coincidir con el nombre de host en el encabezado de la sección. + - `ipv4` debería coincidir con la dirección IPv4 estática única del nodo. + - `replica` debería estar configurado como `enabled`. + - Aprovecha la oportunidad para eliminar las secciones para los nodos sin conexión que ya no se utilicen. + + Para revisar un ejemplo de configuración, consulta la sección "[Ejemplo de configuración](#example-configuration)". + + {% endwarning %} + +13. Inicializa la configuración del clúster nuevo. {% data reusables.enterprise.use-a-multiplexer %} + + ```shell + ghe-cluster-config-init + ``` + +14. Después de que ésta termine, {% data variables.product.prodname_ghe_server %} mostrará el siguiente mensaje. + + ```shell + Finished cluster initialization + ``` + +{% data reusables.enterprise_clustering.apply-configuration %} + +{% data reusables.enterprise_clustering.configuration-finished %} + +17. Configura un balanceador de carga que aceptará las conexiones de los usuarios si conmutas por error a los nodos pasivos. Para obtener más información, consulta la sección "[Configuración de red de clúster](/enterprise/admin/enterprise-management/cluster-network-configuration#configuring-a-load-balancer)". + +Has terminado de configurar la replicación de disponibilidad alta para los nodos en tu clúster. Cada nodo activo comienza a replicar la configuración y los datos a su nodo pasivo correspondiente, y puedes dirigir el tráfico al balanceador de carga para el datacenter secundario en caso de que exista un fallo. Para obtener más información sobre la conmutación por error, consulta la sección "[Iniciar una conmutación por error a tu clúster de réplica](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)". + +#### Ejemplo de configuración + +La configuración de `[cluster]` de nivel superior se debería ver como en el ejemplo siguiente. + +```shell +[cluster] + mysql-master = HOSTNAME OF ACTIVE MYSQL MASTER + redis-master = HOSTNAME OF ACTIVE REDIS MASTER + primary-datacenter = PRIMARY DATACENTER NAME + mysql-master-replica = HOSTNAME OF PASSIVE MYSQL MASTER + redis-master-replica = HOSTNAME OF PASSIVE REDIS MASTER + mysql-auto-failover = true +... +``` + +La configuración para un nodo activo en el nivel de almacenamiento de tu clúster se debería ver como en el ejemplo siguiente. + +```shell +... +[cluster "UNIQUE ACTIVE NODE HOSTNAME"] + datacenter = default + hostname = UNIQUE ACTIVE NODE HOSTNAME + ipv4 = IPV4 ADDRESS + consul-datacenter = default + consul-server = true + git-server = true + pages-server = true + mysql-server = true + elasticsearch-server = true + redis-server = true + memcache-server = true + metrics-server = true + storage-server = true + vpn = IPV4 ADDRESS SET AUTOMATICALLY + uuid = UUID SET AUTOMATICALLY + wireguard-pubkey = PUBLIC KEY SET AUTOMATICALLY +... +``` + +La configuración para el nodo pasivo correspondiente en el nivel de almacenamiento se debería ver como en el ejemplo siguiente. + +- Las diferencias importantes con nodo activo correspondiente estarán **restaltadas**. +- {% data variables.product.prodname_ghe_server %} asigna valores para `vpn`, `uuid`, y `wireguard-pubkey` automáticamente, así que no deberías definir los valores para los nodos pasivos que vayas a inicializar. +- Los roles del servidor, como se definen en las claves de `*-server`, coinciden con el nodo activo correspondiente. + +```shell +... +[cluster "UNIQUE PASSIVE NODE HOSTNAME"] + replica = enabled + ipv4 = IPV4 ADDRESS OF NEW VM WITH IDENTICAL RESOURCES + datacenter = SECONDARY DATACENTER NAME + hostname = UNIQUE PASSIVE NODE HOSTNAME + consul-datacenter = SECONDARY DATACENTER NAME + consul-server = true + git-server = true + pages-server = true + mysql-server = true + elasticsearch-server = true + redis-server = true + memcache-server = true + metrics-server = true + storage-server = true + vpn = DO NOT DEFINE + uuid = DO NOT DEFINE + wireguard-pubkey = DO NOT DEFINE +... +``` + +### Monitorear la replicación entre los nodos de clúster pasivos y activos + +La replicación inicial entre los nodos activos y pasivos en tu clúster toma su tiempo. La cantidad de tiempo dependerá de la cantidad de datos a replicar y de los niveles de actividad de {% data variables.product.prodname_ghe_server %}. + +Puedes monitorear el progreso de cualquier nodo en el clúster, utilizando las herramientas de línea de comandos que se encuentran disponibles a través del shell administrativo de {% data variables.product.prodname_ghe_server %}. Para obtener más información acerca del shell administrativo, consulta la sección "[Acceder al shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)". + +- Monitorear la replicación de bases de datos: + + ``` + /usr/local/share/enterprise/ghe-cluster-status-mysql + ``` + +- Monitorear la replicación de los datos de los repositorios y los Gists: + + ``` + estado ghe-spokes + ``` + +- Monitorear la replicación de los adjuntos y los datos de LFS: + + ``` + ghe-storage replication-status + ``` + +- Monitorear la replicación de los datos de las páginas: + + ``` + ghe-dpages replication-status + ``` + +Puedes utilizar `ghe-cluster-status` para revisar la salud general de tu clúster. Para obtener más información, consulta la sección "[Utilidades de la línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)". + +### Reconfigurar la replilcación de disponibilidad alta después de un fallo + +Después de que te recuperes de un fallo de los nodos activos del clúster hacia los nodos pasivos, puedes reconfigurar la replicación de disponibilidad alta en dos formas. + +#### Aprovisionar y configurar los nodos pasivos nuevos + +Después de recuperarte de un fallo, puedes reconfigurar la disponibilidad alta en dos formas. El método que elijas dependerá de la razón por la cual ocurrió el fallo y del estado de los nodos activos originales. + +1. Aprovisiona y configura un conjunto nuevo de nodos pasivos para cada uno de los nodos activos en tu datacenter secundario. + +2. Utiliza los nodos activos antiguos como los nodos pasivos nuevos. + +El proceso para reconfigurar la disponibilidad alta es idéntico a la configuración inicial de la misma. Para obtener más información, consulta la sección "[Crear una réplica de disponibilidad alta para un clúster](#creating-a-high-availability-replica-for-a-cluster)". + + +### Inhabilitar la replicación de disponibilidad alta para un clúster + +Pudes parar la replicación hacia los nodos pasivos para el despliegue de {% data variables.product.prodname_ghe_server %} de tu clúster. + +{% data reusables.enterprise_clustering.ssh-to-a-node %} + +{% data reusables.enterprise_clustering.open-configuration-file %} + +3. En la sección de `[cluster]` de nivel superior, borra los pares de clave-valor de `mysql-auto-failover`, `redis-master-replica`, y `mysql-master-replica`. + +4. Borra cada sección para un nodo pasivo. Para los nodos pasivos, `replica` se configura como `enabled`. + +{% data reusables.enterprise_clustering.apply-configuration %} + +{% data reusables.enterprise_clustering.configuration-finished %} + +Después de que {% data variables.product.prodname_ghe_server %} te regrese al prompt, habrás terminado de inhabilitar la replicación de disponibilidad alta. diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md new file mode 100644 index 0000000000000..be0ff7a756307 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md @@ -0,0 +1,14 @@ +--- +title: Configurar la disponibilidad alta +redirect_from: + - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability + - /enterprise/admin/guides/installation/high-availability-cluster-configuration/ + - /enterprise/admin/guides/installation/high-availability-configuration/ + - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/ + - /enterprise/admin/enterprise-management/configuring-high-availability +intro: '{% data variables.product.prodname_ghe_server %} admite un modo de alta disponibilidad de funcionamiento diseñado para minimizar la interrupción del servicio en caso que ocurra una falla de hardware o una interrupción de red importante que afecte al aparato principal.' +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md new file mode 100644 index 0000000000000..af6b994e19460 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md @@ -0,0 +1,102 @@ +--- +title: Crear una réplica de alta disponibilidad +intro: 'En una configuración activa/pasiva, el aparato réplica es una copia redundante del aparato principal. Si el aparato principal falla, el modo de alta disponibilidad permite que la réplica actúe como aparato principal, lo que posibilita que la interrupción del servicio sea mínima.' +redirect_from: + - /enterprise/admin/installation/creating-a-high-availability-replica + - /enterprise/admin/enterprise-management/creating-a-high-availability-replica +versions: + enterprise-server: '*' +--- + +### Crear una réplica de alta disponibilidad + +1. Configurar un aparato {% data variables.product.prodname_ghe_server %} nuevo en la plataforma que desees. El aparato réplica debe espejar la CPU, la RAM y los ajustes de almacenamiento del aparato principal. Recomendamos que instales el aparato réplica en un entorno separado. El hardward subyacente, el software y los componentes de red deben estar aislados de los del aparato principal. Si estás usando un proveedor de nube, utiliza una región o zona separada. Para obtener más información, consulta ["Configurar una instancia {% data variables.product.prodname_ghe_server %}"](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance). +2. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia de {% data variables.product.prodname_enterprise %}. +3. Establece una contraseña de administrador que coincida con la contraseña del aparato principal y continúa. +4. Haz clic en **Configure as Replica** (Configurar como réplica). ![Opciones de instalación con enlace para configurar tu nueva instancia como una réplica](/assets/images/enterprise/management-console/configure-as-replica.png) +5. En "Agregar nueva clave SSH", escribe tu clave SSH. ![Agrega la clave SSH](/assets/images/enterprise/management-console/add-ssh-key.png) +6. Haz clic en **Add key** (Agregar clave), luego haz clic en **Continue** (Continuar). +6. Conectarse a la dirección IP del aparato réplica usando SSH. + ```shell + $ ssh -p 122 admin@REPLICA IP + ``` +7. Para generar un par de claves para la replicación, usa el comando `ghe-repl-setup` con la dirección IP del aparato principal y copia la clave pública que este devuelve. + ```shell + $ ghe-repl-setup PRIMARY IP + ``` +{% data reusables.enterprise_installation.add-ssh-key-to-primary %} +9. Para verificar la conexión con la primaria y habilitar el modo de réplica para una nueva réplica, ejecuta nuevamente `ghe-repl-setup`. + ```shell + $ ghe-repl-setup PRIMARY IP + ``` +{% data reusables.enterprise_installation.replication-command %} +11. Para verificar el estado de cada canal de replicación del almacén de datos, utiliza el comando `ghe-repl-status`. + ```shell + $ ghe-repl-status + ``` + +### Crear réplicas de replicación geográfica + +Esta configuración de ejemplo utiliza una réplica primaria y dos réplicas, que se encuentran en tres regiones geográficas diferentes. Aunque los tres nodos pueden estar en redes diferentes, se necesitan todos los nodos para que sean accesibles desde todos los demás nodos. Como mínimo, los puertos administrativos requeridos deben estar abiertos para todos los demás nodos. Para obtener más información acerca de los requisitos de puerto, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)." + +1. Crea la primera réplica de la misma manera en que lo harías para una configuración de dos nodos estándar ejecutando `ghe-repl-setup` en la primera réplica. + ```shell + (replica1)$ ghe-repl-setup PRIMARY IP + (replica1)$ ghe-repl-start + ``` +2. Crea una segunda réplica y utiliza el comando `ghe-repl-setup --add`. La marca `--add` evita que sobrescriba la configuración de la replicación existente y agrega la nueva réplica a la configuración. + ```shell + (replica2)$ ghe-repl-setup --add PRIMARY IP + (replica2)$ ghe-repl-start + ``` +3. Predeterminadamente, las replicas se configuran en el mismo centro de datos, y ahora intentarán poblar los datos desde un nodo existente en el mismo centro de datos. Configura las réplicas para diferentes centros de datos estableciendo un valor diferente para la opción de centro de datos. Los valores específicos pueden ser los que tú quieras, siempre que sean diferentes entre sí. Ejecuta el comando `ghe-repl-node` en cada nodo y especifica el centro de datos. + + En la primaria: + ```shell + (primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME] + ``` + En la primera réplica: + ```shell + (replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME] + ``` + En la segunda réplica: + ```shell + (replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME] + ``` + {% tip %} + + **Consejo:** puedes establecer las opciones `--datacenter` y `--active` al mismo tiempo. + + {% endtip %} +4. Un nodo de réplica activo almacenará copias de los datos del aparato y responderá las solicitudes de usuario final. Un nodo inactivo almacenará copias de los datos del aparato, pero no podrá atender las solicitudes de usuario final. Habilita el modo activo usando la marca `--active` o el modo inactivo usando la marca `--inactive`. + + En la primera réplica: + ```shell + (replica1)$ ghe-repl-node --active + ``` + En la segunda réplica: + ```shell + (replica2)$ ghe-repl-node --active + ``` +5. Para aplicar la configuración, usa el comando `ghe-config-apply` en el principal. + ```shell + (primary)$ ghe-config-apply + ``` + +### Configurar el DNS para replicación geográfica + +Configurar Geo DNS usando las direcciones IP de los nodos primarios y réplica. También puedes crear un DNS CNAME para el nodo principal (p. ej., `primary.github.example.com`) para acceder al nodo principal a través de SSH o hacerle una copia de seguridad a través de `backup-utils`. + +Para probarlo, puedes agregar entradas al archivo de `hosts` de la estación de trabajo local (por ejemplo, `/etc/hosts`). Estas entradas de ejemplo resolverán las solicitudes de `HOSTNAME` para `replica2`. Puedes apuntar a hosts específicos comentando en diferentes líneas. + +``` +# HOSTNAME +# HOSTNAME + HOSTNAME +``` + +### Further reading + +- "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)" +- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" +- "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)" diff --git a/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md new file mode 100644 index 0000000000000..2e05609563ff4 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md @@ -0,0 +1,42 @@ +--- +title: Diferencias entre los agrupamientos y la disponibilidad alta (HA) +intro: '{% data variables.product.prodname_ghe_server %} La configuración de alta disponibilidad es una configuración de conmutación primaria/secundaria que brinda redundancia mientras que el agrupamiento brinda redundancia y escalabilidad al distribuir cargas de lectura y escritura entre múltiples nodos.' +redirect_from: + - /enterprise/admin/clustering/differences-between-clustering-and-high-availability-ha + - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha +versions: + enterprise-server: '*' +--- + +### Escenarios de fallas + +Tanto la alta disponibilidad (HA, por sus siglas en inglés) como el agrupamiento brindan redundancia al eliminar el nodo único como punto de falla. Pueden brindar disponibilidad en estos escenarios: + +{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %} + +### Escalabilidad + +{% data reusables.enterprise_clustering.clustering-scalability %} En HA, la escala de este aparato depende exclusivamente del nodo principal y la cara no se distribuye al servidor de réplica. + +### Diferencias en el método de conmutación y configuración + +| Característica | Configuración de conmutación | Método de conmutación | +|:------------------------------------ |:--------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------- | +| Configuración de alta disponibilidad | Registro de DNS con un TTL bajo que apunta al aparato principal o balanceador de carga. | Debes impulsar manualmente el aparato de réplica en las configuraciones de conmutación DNS y balanceador de carga. | +| Agrupación | El registro DNS debe apuntar a un balanceador de carga. | Si falla un nodo detrás de un balanceador de carga, el tráfico se envía automáticamente a los otros nodos de funcionamiento. | + +### Copias de seguridad y recuperación ante desastres + +HA y Clustering no deben ser considerados como un reemplazo para copias de seguridad regulares. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)" + +### Supervisar + +Las características de disponibilidad, especialmente las que tienen conmutación automática como Agrupación, pueden enmascarar una falla dado que el servicio generalmente no se ve interrumpido cuando algo falla. Ya sea que esté usando HA o Agrupación, supervisar el estado de cada instancia es importante para que puedas estar al tanto cuando se produce una falla. Para obtener más información sobre la supervisión, consulta " +[Umbrales de alerta recomendados](/enterprise/{{ page.version }}/admin/guides/installation/recommended-alert-thresholds/)" y [Supervisar nodos de agrupación](/enterprise/{{ page.version}}/admin/guides/clustering/monitoring-cluster-nodes/)".

    + + + +### Further reading + +- Para obtener más información acerca del {% data variables.product.prodname_ghe_server %} Agrupamiento, visite la sección de "[Acerca del agrupamiento](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/)." +- Para obtener más información sobre HA, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)". diff --git a/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md new file mode 100644 index 0000000000000..98476d20eb40d --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md @@ -0,0 +1,33 @@ +--- +title: Habilitar comprobaciones de actualización automáticas +intro: 'Puedes habilitar comprobaciones de actualización automáticas para que {% data variables.product.product_location %} busque y descargue el último lanzamiento del {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-update-checks + - /enterprise/admin/enterprise-management/enabling-automatic-update-checks +versions: + enterprise-server: '*' +--- + +Cuando un paquete de actualizaciones se descarga automáticamente para {% data variables.product.product_location %}, recibirás un mensaje informándote que puedes actualizar el {% data variables.product.prodname_ghe_server %}. Descarga de paquetes para el directorio `/var/lib/ghe-updates` en {% data variables.product.product_location %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)." + +Si está disponible un hotpatch para una actualización, el `.hpkg` se descargará automáticamente. En la consola de administración puedes elegir instalar el hotpatch de inmediato o programar la instalación para otro momento. Para obtener más información, consulta "[Actualizar con un hotpatch](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." + +{% tip %} + +**Consejo:** Para habilitar comprobaciones de actualización automáticas, {% data variables.product.product_location %} se debe poder conectar a `https://github-enterprise.s3.amazonaws.com`. + +{% endtip %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.updates-tab %} +4. Haz clic en **Yes, automatically check for updates** (Sí, buscar actualizaciones automáticamente). ![Botón para habilitar actualizaciones automáticas](/assets/images/enterprise/management-console/enable_updates_button.png) +{% data reusables.enterprise_management_console.save-settings %} + +Para saber si tu instancia está actualizada, busca el mensaje emergente en la pestaña de actualizaciones. + +![Mensaje emergente que indica tu lanzamiento del servidor de GitHub Enterprise](/assets/images/enterprise/management-console/up-to-date-banner.png) + +En **Logs** (Registros), puedes ver el estado de la búsqueda de actualizaciones más reciente. + +![Registros para actualización](/assets/images/enterprise/management-console/update-log.png) diff --git a/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md new file mode 100644 index 0000000000000..abf38729ecfe8 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -0,0 +1,53 @@ +--- +title: Evacuar un nodo de agrupación +intro: Puedes evacuar los servicios de datos en un nodo de agrupación. +redirect_from: + - /enterprise/admin/clustering/evacuating-a-cluster-node + - /enterprise/admin/enterprise-management/evacuating-a-cluster-node +versions: + enterprise-server: '*' +--- + +Si solo tienes tres nodos en tu agrupación de servicios de datos, no puedes evacuar los nodos, porque `ghe-spokes` no tiene otro lugar para realizar una copia. Si tienes cuatro o más, `ghe-spokes` moverá todos los repositorios del nodo evacuado. + +Si colocas fuera de línea un nodo que tiene otros servicios de datos (como git, páginas o almacenamiento), debes evacuar cada nodo antes de ponerlo fuera de línea. + +1. Encuentra la `uuid` del nodo con el comando `ghe-config`. + + ``` + $ ghe-config cluster._hostname_.uuid + ``` + +2. Deberás supervisar el estado de tu nodo mientras se copian los datos. Idealmente, el nodo no debería estar fuera de línea hasta que se complete la copia. Para supervisar el estado de tu nodo, ejecuta alguno de los siguientes comandos: + + Para Git + ``` + ghe-spokes evac-status + ``` + Para {% data variables.product.prodname_pages %} + ``` + echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y + ``` + Para almacenamiento + ``` + ghe-storage evacuation-status + ``` + +3. Una vez que la copia esté completa, puedes evacuar el servicio de almacenamiento. Ejecuta alguno de los siguientes comandos: + + Para Git + ``` + ghe-spokes server evacuate git-server- + ``` + Para {% data variables.product.prodname_pages %} + ``` + ghe-dpages evacuate pages-server- + ``` + Para almacenamiento, coloca el nodo fuera de línea + ``` + ghe-storage offline storage-server- + ``` + luego evacúa + ``` + ghe-storage evacuate storage-server- + ``` diff --git a/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md new file mode 100644 index 0000000000000..2ab214b1e35bc --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md @@ -0,0 +1,71 @@ +--- +title: Aumentar el CPU o los recursos de memoria +intro: 'Si las operaciones en {% data variables.product.product_location_enterprise %} son lentas, es posible que necesites agregar CPU o recursos de memoria.' +redirect_from: + - /enterprise/admin/installation/increasing-cpu-or-memory-resources + - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} + +### Agregar CPU o recursos de memoria para AWS + +{% note %} + +**Nota:** Para agregar CPU o recursos de memoria para AWS, debes estar familiarizado con el uso de la consola de administración de AWS o la interfaz de la línea de comando `aws ec2` para administrar instancias EC2. Para obtener antecedentes y detalles sobre el uso de herramientas de AWS de tu elección para realizar el ajuste de tamaño, consulta la documentación de AWS en [ajustar el tamaño de una instancia respaldada por Amazon EBS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). + +{% endnote %} + +#### Consideraciones relativas al ajuste de tamaño + +Antes de aumentar la CPU o los recursos de memoria para {% data variables.product.product_location %}: + +- **Escala tu memoria con los CPU**. {% data reusables.enterprise_installation.increasing-cpus-req %} +- **Asigna una dirección IP elástica a la instancia**. Si no se asigna una IP elástica, deberás ajustar los registros DNS A para tu servidor {% data variables.product.prodname_ghe_server %} después de volver a iniciar para considerar el cambio de la dirección de IP pública. Una vez que tu instancia se reinicia, la IP elástica (EIP) se mantiene automáticamente si la instancia se inicia en una VPC. Si la instancia se inicia en una EC2-Classic, la IP elástica debe asociarse nuevamente de forma manual. + +#### Tipos de instancias AWS admitidos + +Debes determinar el tipo de instancia que te gustaría actualizar en base a especificaciones de CPU/memoria. +{% data reusables.enterprise_installation.aws-supported-instance-types %} + +#### Tipos de instancias AWS recomendadas + +{% data reusables.enterprise_installation.aws-recommended-instance-types %} + +{% data reusables.enterprise_installation.warning-on-scaling %} + +#### Volver a ajustar el tamaño para AWS + +{% note %} + +**Nota:** Para instancias iniciadas en EC2-Classic, escribe la dirección de IP elástica asociada con la instancia y las ID de las instancias. Una vez que reiniciaste la instancia, vuelve a asociar la dirección de IP elástica. + +{% endnote %} + +Si no es posible agregar un CPU o recursos de memoria a una instancia AWS/EC2 existente. En su lugar, debes: + +1. Frenar la instancia. +2. Cambiar el tipo de instancia. +3. Iniciar la instancia. +{% data reusables.enterprise_installation.configuration-recognized %} + +### Agregar CPU o recursos de memoria para OpenStack KVM + +No es posible agregar CPU o recursos de memoria para una instancia OpenStack KVM existente. En su lugar, debes: + +1. Tomar una instantánea para la instancia actual. +2. Frenar la instancia. +3. Seleccionar un nuevo formato de la instancia que tenga el CPU o los recursos de memoria deseados. + +### Agregar recursos de memoria o de CPU para VMware + +{% data reusables.enterprise_installation.increasing-cpus-req %} + +1. Utiliza vSphere Client para conectar al servidor de VMware ESXi. +2. Cierra {% data variables.product.product_location %}. +3. Selecciona la máquina virtual y haz clic en **Edit Settings (Editar parámetros)**. +4. En "Hardware", ajusta el CPU o los recursos de memoria asignados a la máquina virtual según se necesite: ![Recursos de configuración de WMware](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) +5. Para iniciar la máquina virtual, haz clic en **OK**. +{% data reusables.enterprise_installation.configuration-recognized %} diff --git a/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md new file mode 100644 index 0000000000000..e30ef22490c77 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md @@ -0,0 +1,60 @@ +--- +title: Aumentar la capacidad de almacenamiento +intro: 'Puedes aumentar o cambiar la cantidad de almacenamiento disponible para los repositorios de Git, las bases de datos, los índices de búsqueda y otros datos de aplicaciones persistentes.' +redirect_from: + - /enterprise/admin/installation/increasing-storage-capacity + - /enterprise/admin/enterprise-management/increasing-storage-capacity +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} + +A medida que se suman usuarios {% data variables.product.product_location %}, es posible que necesites ajustar el tamaño de tu volumen de almacenamiento. Consulta la documentación de tu plataforma de virtualización para obtener más información sobre ajuste de tamaño de almacenamiento. + +### Requisitos y recomendaciones + +{% note %} + +**Nota:** Antes de ajustar el tamaño del volumen de almacenamiento del usuario, pon tu instancia en modo mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + +{% endnote %} + +#### Requisitos mínimos + +{% data reusables.enterprise_installation.hardware-rec-table %} + +### Aumentar el tamaño de partición de datos + +1. Ajusta el disco de volumen existente del usuario utilizando las herramientas de tu plataforma de virtualización. +{% data reusables.enterprise_installation.ssh-into-instance %} +3. Pon el aparato en modo mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +4. Reinicia el aparato para detectar la nueva asignación de almacenamiento. +5. Ejecuta el comando `ghe-storage-extend` para expandir el sistema de archivos `/data`: + ```shell + $ ghe-storage-extend + ``` + +### Aumentar el tamaño de partición raíz utilizando un nuevo aparato + +1. Configura una nueva instancia {% data variables.product.prodname_ghe_server %} con un disco raíz más grande utilizando la misma versión que tu aparato actual. Para obtener más información, consulta "[Configurar una instancia {% data variables.product.prodname_ghe_server %} ](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +2. Cierra el aparato actual. +3. Desconecta el disco de datos de tu aparato actual utilizando las herramientas de tu plataforma de virtualización. +4. Conecta el disco de datos al nuevo aparato con un disco raíz más grande. + +### Aumentar el tamaño de partición raíz utilizando un aparato existente + +1. Conecta un nuevo disco a tu aparato {% data variables.product.prodname_ghe_server %}. +2. Ejecuta el comando `parted` para formatear el disco: + ```shell + $ sudo parted /dev/xvdg mklabel msdos + $ sudo parted /dev/xvdg mkpart primary ext4 0% 50% + $ sudo parted /dev/xvdg mkpart primary ext4 50% 100% + ``` +3. Ejecuta el comando `ghe-upgrade` para instalar un paquete específico de plataforma completo al disco recientemente particionado. Un paquete de actualización de hotpatch universal, como `github-enterprise-2.11.9.hpkg` no funcionará como se espera. + ```shell + $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1 + ``` +4. Cierra el aparato. +5. En el hipervisor, quita el disco raíz anterior y agrega el nuevo disco raíz en la misma ubicación del disco raíz anterior. +6. Inicia el aparato. diff --git a/translations/es-ES/content/admin/enterprise-management/index.md b/translations/es-ES/content/admin/enterprise-management/index.md new file mode 100644 index 0000000000000..ac2b47d11211a --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/index.md @@ -0,0 +1,44 @@ +--- +title: 'Monitorear, administrar y actualizar tu empresa' +intro: 'Puedes monitorear tu aplicativo, mejorar a una versión nueva y configurar el agrupamiento o la disponibilidad alta' +redirect_from: + - /enterprise/admin/enterprise-management +versions: + enterprise-server: '*' +--- + + +### Índice + +{% topic_link_in_list /monitoring-your-appliance %} + {% link_in_list /accessing-the-monitor-dashboard %} + {% link_in_list /recommended-alert-thresholds %} + {% link_in_list /setting-up-external-monitoring %} + {% link_in_list /configuring-collectd %} + {% link_in_list /monitoring-using-snmp %} +{% topic_link_in_list /updating-the-virtual-machine-and-physical-resources %} + {% link_in_list /upgrade-requirements %} + {% link_in_list /upgrading-github-enterprise-server %} + {% link_in_list /enabling-automatic-update-checks %} + {% link_in_list /increasing-storage-capacity %} + {% link_in_list /increasing-cpu-or-memory-resources %} + {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} +{% topic_link_in_list /configuring-clustering %} + {% link_in_list /about-clustering %} + {% link_in_list /differences-between-clustering-and-high-availability-ha %} + {% link_in_list /about-cluster-nodes %} + {% link_in_list /cluster-network-configuration %} + {% link_in_list /initializing-the-cluster %} + {% link_in_list /upgrading-a-cluster %} + {% link_in_list /monitoring-cluster-nodes %} + {% link_in_list /replacing-a-cluster-node %} + {% link_in_list /evacuating-a-cluster-node %} + {% link_in_list /configuring-high-availability-replication-for-a-cluster %} + {% link_in_list /initiating-a-failover-to-your-replica-cluster %} +{% topic_link_in_list /configuring-high-availability %} + {% link_in_list /about-high-availability-configuration %} + {% link_in_list /creating-a-high-availability-replica %} + {% link_in_list /initiating-a-failover-to-your-replica-appliance %} + {% link_in_list /recovering-a-high-availability-configuration %} + {% link_in_list /removing-a-high-availability-replica %} + {% link_in_list /about-geo-replication %} diff --git a/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md new file mode 100644 index 0000000000000..03bbe6e78e087 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md @@ -0,0 +1,114 @@ +--- +title: Inicializar la agrupación +intro: 'Una agrupación de {% data variables.product.prodname_ghe_server %} se debe configurar con una licencia y se debe inicializar mediante un shell administrativo (SSH).' +redirect_from: + - /enterprise/admin/clustering/initializing-the-cluster + - /enterprise/admin/enterprise-management/initializing-the-cluster +versions: + enterprise-server: '*' +--- + +{% data reusables.enterprise_clustering.clustering-requires-https %} + +### Instalar {% data variables.product.prodname_ghe_server %} + +1. En cada nodo de agrupación, suministra e instala {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar una instancia {% data variables.product.prodname_ghe_server %} ](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +2. Mediante el shell administrativo o DHCP, configura **solo** la dirección IP de cada nodo. No configures los otros parámetros. + +### Configurar el primer nodo + +1. Conèctate al nodo que se designarà como el primario de MySQL en la `cluster.conf`. Para obtener màs informaciòn, consulta la secciòn "[Acerca del archivo de configuraciòn de clùster](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)". +2. En tu navegador web, visita `https://:8443/setup/`. +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} +{% data reusables.enterprise_installation.instance-will-restart-automatically %} + +### Inicializar la agrupación + +Para inicializar la agrupación, necesitas un archivo de configuración de agrupación (`cluster.conf`). Para obtener más información, consulta "[Acerca del archivo de configuración de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)". + +1. Desde el primer nodo que se configuró, ejecuta `ghe-cluster-config. init`. De esta manera, se inicializará la agrupación si existen nodos en el archivo de configuración de la agrupación que no están configurados. +2. Ejecuta `ghe-cluster-config-apply`. Esto validará el archivo `cluster.conf`, aplicará la configuración a cada archivo del nodo y traerá los servicios configurados en cada nodo. + +Para comprobar el estado de una agrupación en funcionamiento, usa el comando `ghe-cluster-status`. + +### Acerca del archivo de configuración de la agrupación + +El archivo de configuración de la agrupación (`cluster.conf`) define los nodos en la agrupación, y los servicios que ejecutan. Para obtener más información, consulta "[Acerca de los nodos de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)". + +Este ejemplo `cluster.conf` define una agrupación con cinco nodos. + + - Dos nodos (llamados `ghe-app-node-\*`) ejecutan los servicios `web-server` y `job-server` responsables de atender las solicitudes de los clientes. + - Tres nodos (llamados `ghe-data-node-\*`) ejecutan los servicios responsables del almacenamiento y la recuperación de los datos de {% data variables.product.prodname_ghe_server %}. + +Los nombres de los nodos pueden ser cualquier nombre de host válido que elijas. Los nombres son conjuntos de nombres de host de cada nodo y también se agregarán a `/etc/hosts` en cada nodo, de manera que los nodos puedan ser resolubles localmente entre sí. + +Especifica el primer nodo de clùster que configuraste como el primario de MySQL a travès de `mysql-server` y de `mysql-master`. + +``` +[cluster] + mysql-master = ghe-data-node-1 + redis-master = ghe-data-node-1 + primary-datacenter = default +[cluster "ghe-app-node-1"] + hostname = ghe-app-node-1 + ipv4 = 192.168.0.2 + # ipv6 = fd12:3456:789a:1::2 + web-server = true + job-server = true +[cluster "ghe-app-node-2"] + hostname = ghe-app-node-2 + ipv4 = 192.168.0.3 + # ipv6 = fd12:3456:789a:1::3 + web-server = true + job-server = true +[cluster "ghe-data-node-1"] + hostname = ghe-data-node-1 + ipv4 = 192.168.0.4 + # ipv6 = fd12:3456:789a:1::4 + consul-server = true + consul-datacenter = default + git-server = true + pages-server = true + mysql-server = true + elasticsearch-server = true + redis-server = true + memcache-server = true + metrics-server = true + storage-server = true +[cluster "ghe-data-node-2"] + hostname = ghe-data-node-2 + ipv4 = 192.168.0.5 + # ipv6 = fd12:3456:789a:1::5 + consul-server = true + consul-datacenter = default + git-server = true + pages-server = true + mysql-server = true + elasticsearch-server = true + redis-server = true + memcache-server = true + metrics-server = true + storage-server = true +[cluster "ghe-data-node-3"] + hostname = ghe-data-node-3 + ipv4 = 192.168.0.6 + # ipv6 = fd12:3456:789a:1::6 + consul-server = true + consul-datacenter = default + git-server = true + pages-server = true + mysql-server = true + elasticsearch-server = true + redis-server = true + memcache-server = true + metrics-server = true + storage-server = true +``` + +Crea el archivo `/data/user/common/cluster.conf` en el primer nodo configurado. Por ejemplo, usando `vim`: + + ```shell + ghe-data-node-1:~$ sudo vim /data/user/common/cluster.conf + ``` + diff --git a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md new file mode 100644 index 0000000000000..e50b583189d84 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -0,0 +1,45 @@ +--- +title: Iniciar una tolerancia de fallos a tu aparato de réplica +intro: 'Puedes tener tolerancia de fallos en un aparato de réplica {% data variables.product.prodname_ghe_server %} por medio de la línea de comando para mantenimiento y pruebas, o si falla el aparato principal.' +redirect_from: + - /enterprise/admin/installation/initiating-a-failover-to-your-replica-appliance + - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance +versions: + enterprise-server: '*' +--- + +El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para impulsar la réplica y redireccionar el tráfico de forma manual. El tiempo promedio varía entre 2 y 10 minutos. + +{% data reusables.enterprise_installation.promoting-a-replica %} + +1. Para permitir que la replicación finalice antes de cambiar aparatos, pon el aparato principal en modo mantenimiento: + - Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)" + - También puedes usar el comando `ghe-maintenance -s`. + ```shell + $ ghe-maintenance -s + ``` +2. Cuando el número de operaciones Git activas llega a cero, espera 30 segundos. +3. Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`. + ```shell + $ ghe-repl-status -vv + ``` +4. Para frenar la replicación e impulsar el aparato de réplica a un estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible. + ```shell + $ ghe-repl-promote + ``` +5. Actualiza el registro de DNS para que apunte a la dirección IP de la réplica. El tráfico es direccionado a la réplica después de que transcurra el período TTL. Si estás utilizando un balanceador de carga, asegúrate de que esté configurado para enviar el tráfico a la réplica. +6. Notifica a los usuarios que pueden retomar las operaciones normales. +7. Si se desea, configura una replicación desde el aparato principal nuevo al aparato existente y el principal anterior. Para obtener más información, consulta "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)." +8. Los aplicativos en los que no pretendas configurar la replicación que eran parte de la configuración de disponibilidad alta antes de la recuperación del fallo deberán eliminarse de dicha configuración de disponibilidad alta a través de UUID. + - Para los aplicativos anteriores, obtén su UUID a través de `cat /data/user/common/uuid`. + ```shell + $ cat /data/user/common/uuid + ``` + - En el primario nuevo, elimina las UUID utilizando `ghe-repl-teardown`. Por favor, reemplaza *`UUID`* con aquella UUID que recuperaste en el paso anterior. + ```shell + $ ghe-repl-teardown -u UUID + ``` + +### Further reading + +- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" diff --git a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md new file mode 100644 index 0000000000000..9da99a81fd1fe --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md @@ -0,0 +1,36 @@ +--- +title: Iniciar una conmutación por error a tu clúster de réplica +intro: 'Si tu clúster de {% data variables.product.prodname_ghe_server %} falla, puedes recuperarte del fallo a la réplica pasiva.' +redirect_from: + - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster +versions: + enterprise-server: '>2.21' +--- + +### Acerca de la conmutación por error a tu clúster de réplica + +En caso de que haya una falla en tu datacenter primario, puedes recuperarte de dicho fallo hacia los nodos de réplica en el datacenter secundario si configuras un nodo de réplica pasivo para cada nodo en tu clúster activo. + +El tiempo que se requiere para recuperarse del fallo dependerá de qué tanto tiempo se necesite para promover el clúster de réplica manualmente y redirigir así el tráfico. + +El promover un clúster de réplica no configura automáticamente la replicación al clúster existente. Después de promover un clúster de réplica, puedes reconfigurar la replicación desde el clúster activo nuevo. Para obtener más información, consulta la sección "[Configurar la disponibilidad alta para un clúster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster#reconfiguring-high-availability-replication-after-a-failover)". + +### Prerrequisitos + +Para recuperarse de un fallo hacia los nodos de réplica pasivos, debes haber configurado la disponibilidad alta para tu clúster. Para obtener más información, consulta la sección "[Configurar la disponibilidad alta para un clúster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster)". + +### Iniciar una conmutación por error a tu clúster de réplica + +1. Ingresa por SSH en cualquier nodo pasivo en el datacenter secundario para tu clúster. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)." + +2. Inicializa la conmutación por error al clúster secundario y configúrala para que se comporte como los nodos activos. + + ```shell + ghe-cluster-failover + ``` + +{% data reusables.enterprise_clustering.configuration-finished %} + +3. Actualiza elregistro de DNS para que apunte a las direcciones IP del balanceador de carga para tu clúster pasivo. El tráfico es direccionado a la réplica después de que transcurra el período TTL. + +Después de que {% data variables.product.prodname_ghe_server %} te regrese al prompt y de que se hayan propagado las actualizaciones de tu DNS, habrás terminado de recuperarte del fallo. Los usuarios pueden acceder a {% data variables.product.prodname_ghe_server %} utilizando el nombre de host habitual para tu clúster. diff --git a/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md new file mode 100644 index 0000000000000..858367c5a1d65 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md @@ -0,0 +1,91 @@ +--- +title: Migrar desde GitHub Enterprise 11.10.x a 2.1.23 +redirect_from: + - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123 + - /enterprise/admin-guide/migrating/ + - /enterprise/admin/articles/migrating-github-enterprise/ + - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x/ + - /enterprise/admin/articles/upgrading-to-a-newer-release/ + - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/ + - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23 + - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123 +intro: 'Para migrar desde {% data variables.product.prodname_enterprise %} 11.10.x a 2.1.23, deberás configurar una nueva instancia de aparato y migrar los datos de la instancia anterior.' +versions: + enterprise-server: '*' +--- + +Se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 y superior. No se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 o inferior. Primero debes actualizar a 11.10.348 en varias actualizaciones. Para obtener más información, consulta el procedimiento de actualización 11.10.348, "[Actualizar al lanzamiento más reciente](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)." + +Para actualizar a la versión más reciente {% data variables.product.prodname_enterprise %}, primero debes migrar a {% data variables.product.prodname_ghe_server %} 2.1, entonces puedes aplicar el proceso normal de actualización. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". + +### Prepárate para la migración + +1. Revisa la guía de Abastecimiento e instalación y controla que se cumplan todos los requisitos previos necesarios para abastecer y configurar {% data variables.product.prodname_enterprise %} 2.1.23 en tu entorno. Para obtener más información, consulta "[Abastecimiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)." +2. Verifica que la instancia actual esté ejecutando una versión actualizada compatible. +3. Configura la versión más reciente de {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). + - Si ya has configurado copias de seguridad programadas utilizando {% data variables.product.prodname_enterprise_backup_utilities %}, asegúrate de que hayas actualizado a la versión más reciente. + - Si no estás ejecutando actualmente copias de seguridad programadas, configura {% data variables.product.prodname_enterprise_backup_utilities %}. +4. Toma una instantánea de copia de respaldo completa inicial de la instancia actual utilizando el comando `ghe-backup`. Si ya configuraste copias de seguridad programadas para tu instancia actual, no debes tomar una instantánea de tu instancia. + + {% tip %} + + **Sugerencia:** puedes dejar la instancia en línea y en uso activo durante la instantánea. Tomarás otras instantánea durante la parte de mantenimiento de la migración. Ya que las copias de seguridad son incrementales, esta instantánea inicial reduce la cantidad de datos transferidos en la instantánea final, que pueden acortar la ventana de mantenimiento. + + {% endtip %} + +5. Determina el método para cambiar el tráfico de red de usuario a la nueva instancia. Después de la migración, todo el tráfico de red de HTTP y Git se dirige a la nueva instancia. + - **DNS** - Recomendamos este método para todos los entornos, ya que es simple y funciona bien incluso cuando se migra desde una base de datos a otra. Antes de comenzar la migración, reduce los TTL de los registros DNS existentes a cinco minutos o menos y permite el cambio a propagar. Una vez que la migración se completa, actualiza los registros DNS para que apunten a la dirección IP de la nueva instancia. + - **Asignación de dirección IP** - Este método está únicamente disponible en VMware para la migración VMware y no se recomienda excepto que el método DNS no esté disponible. Antes de comenzar la migración, deberás cerrar la instancia anterior y asignar tu dirección IP a la nueva instancia. +6. Programa una ventana de mantenimiento. La ventana de mantenimiento debe incluir tiempo suficiente para transferir datos desde el servidor de seguridad a la nueva instancia y variará en base al tamaño de la instantánea de respaldo y el ancho de banda de la red disponible. Durante este tiempo tu instancia actual no estará disponible y estará en modo mantenimiento mientras migras a la nueva instancia. + +### Realiza la migración + +1. Aprovisiona una nueva instancia {% data variables.product.prodname_enterprise %} 2.1. Para obtener más información, consulta la "[Guía de aprovisionamiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" para tu plataforma destino. +2. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia de {% data variables.product.prodname_enterprise %}. +3. Configura una contraseña de administrador. +5. Haz clic en **Migrate (Migrar)**. ![Elegir el tipo de instalación](/assets/images/enterprise/migration/migration-choose-install-type.png) +6. Pega tu clave SSH de acceso al servidor de respaldo en "Add new SSH key (Agregar nueva clave SSH)". ![Autorizar la copia de seguridad](/assets/images/enterprise/migration/migration-authorize-backup-host.png) +7. Da clic en **Agregar llave** y luego en **Continuar**. +8. Copia el comando `ghe-restore` que ejecutarás en el servidor de respaldo para migrar datos a la nueva instancia. ![Iniciar la migración](/assets/images/enterprise/migration/migration-restore-start.png) +9. Habilita el modo mantenimiento en la instancia anterior y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + + {% note %} + + **Nota:** la instancia no estará disponible para el uso normal desde este punto en adelante. + + {% endnote %} + +10. En el servidor de respaldo, ejecuta el comando `ghe-backup` para tomar una instantánea de respaldo final. Esto asegura que se capturen todos los datos de la instancia anterior. +11. En el servidor de respaldo, ejecuta el comando `ghe-restore` que copiaste en la pantalla de estado de restauración de la nueva instancia para restaurar la instantánea más reciente. + ```shell + $ ghe-restore 169.254.1.1 + The authenticity of host '169.254.1.1:122' can't be established. + La clave de huella digital RSA es fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1. + ¿Estás seguro que deseas continuar conectado (sí/no)? yes + Connect 169.254.1.1:122 OK (v2.0.0) + Starting restore of 169.254.1.1:122 from snapshot 20141014T141425 + Restoring Git repositories ... + Restaurando las páginas GitHub ... + Restaurando los adjuntos de activo ... + Restaurando las entregas de enlace ... + Restaurando la base de datos MySQL ... + Restaurando la base de datos Redis ... + Restaurando las claves autorizadas de SSH ... + Restaurando los índice de ElasticSearch... + Restaurando las claves del servidor SSH ... + Completed restore of 169.254.1.1:122 from snapshot 20141014T141425 + Visit https://169.254.1.1/setup/settings to review appliance configuration. + ``` + +12. Regresa a la pantalla de estado de restauración de la nueva instancia para ver que la restauración está completa. ![Restaurar la pantalla completa](/assets/images/enterprise/migration/restore-complete-screen.png) +13. Haz clic en **Continue to settings (Continuar a configuraciones)** para revisar y ajustar la información de configuración y los parámetros que se importaron de la instancia anterior. ![Revisar los parámetros importados](/assets/images/enterprise/migration/migration-status-complete.png) +14. Haz clic en **Guardar parámetros**. + + {% note %} + + **Nota:** puedes usar la nueva instancia después de haber aplicado los parámetros de configuración y restaurar el servidor. + + {% endnote %} + +15. Cambia el tráfico de red de usuario desde la instancia anterior a la nueva instancia utilizando la asignación de DNS o la dirección IP. +16. Actualiza a la versión más reciente del lanzamiento del patch de {{ currentVersion }}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md new file mode 100644 index 0000000000000..9e215dfc2b2ab --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md @@ -0,0 +1,114 @@ +--- +title: Supervisar los nodos de agrupación +intro: 'Una agrupación de {% data variables.product.prodname_ghe_server %} está compuesta por servicios redundantes que se distribuyen entre dos o más nodos. Si un servicio individual o un nodo completo falla, los usuarios de la agrupación no deberían percibirlo inmediatamente. Sin embargo, si el rendimiento y la redundancia se ven afectados, es importante supervisar el estado de una agrupación de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/clustering/monitoring-cluster-nodes + - /enterprise/admin/enterprise-management/monitoring-cluster-nodes +versions: + enterprise-server: '*' +--- + +### Comprobación manual del estado de la agrupación + +{% data variables.product.prodname_ghe_server %} tiene una utilidad de línea de comando incorporada para supervisar el estado de la agrupación. Desde el shell administrativo, la puesta en funcionamiento de un comando `ghe-cluster-status` ejecuta una serie de revisiones de estado en cada nodo, incluida la verificación de la conectividad y el estado del servicio. La salida muestra todos los resultados de la prueba incluido el texto `ok` o `error`. Por ejemplo, para mostrar solamente las pruebas fallidas, ejecuta: + +```shell +admin@ghe-data-node-0:~$ ghe-cluster-status | grep error +> mysql-replication ghe-data-node-0: error Stopped +> mysql cluster: error +``` +{% note %} + +**Nota:** Si no hay pruebas fallidas, este comando no produce salidas. Esto indica que la agrupación está en buen estado. + +{% endnote %} + +### Supervisar el estado de la agrupación con Natgios + +Puedes configurar [Nagios](https://www.nagios.org/) para supervisar {% data variables.product.prodname_ghe_server %}. Además de supervisar la conectividad básica para cada uno de los nodos de la agrupación, puedes comprobar el estado de la agrupación al configurar Nagios para que use el comando `ghe-cluster-status -n`. Esto devuelve salidas en un formato que Nagios comprende. + +#### Prerrequisitos +* Host Linux que ejecuta Nagios. +* Acceso de red para la agrupación {% data variables.product.prodname_ghe_server %}. + +#### Configurar el host de Nagios +1. Genera una clave SSH con una contraseña en blanco. Nagios usa esto para autenticar la agrupación de {% data variables.product.prodname_ghe_server %}. + ```shell + nagiosuser@nagios:~$ ssh-keygen -t ed25519 + > Generating public/private ed25519 key pair. + > Enter file in which to save the key (/home/nagiosuser/.ssh/id_ed25519): + > Enter passphrase (empty for no passphrase): leave blank by pressing enter + > Enter same passphrase again: press enter again + > Your identification has been saved in /home/nagiosuser/.ssh/id_ed25519. + > Your public key has been saved in /home/nagiosuser/.ssh/id_ed25519.pub. + ``` + {% danger %} + + **Advertencia de seguridad** Una clave SSH sin una contraseña puede plantear un riesgo de seguridad en caso de que un host tenga autorización de acceso completo. Limita la autorización de esa clave a un comando único de solo lectura. + + {% enddanger %} + {% note %} + + **Nota:** Si estás utilizando una distribución de Linux que no sea compatible con el algoritmo Ed25519, utiliza el comando: + ```shell + nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096 + ``` + + {% endnote %} +2. Copia la llave privada (`id_ed25519`) a la carpeta principal `nagios` y configura la propiedad adecuada. + ```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 una clave pública a fin de que ejecute el comando *only* the `ghe-cluster-status -n`, usa un prefijo `command=` en el archivo `/data/user/common/authorized_keys`. Desde el shell administrativo en cualquier nodo, modifica este archivo para agregar la clave pública generada en el paso 1. Por ejemplo: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....` + +4. Valida y copia la configuración e cualquier nodo en la agrupación al ejecutar `ghe-cluster-config-apply` en el nodo donde modificase el archivo `/data/user/common/authorized_keys`. + + ```shell + admin@ghe-data-node-0:~$ ghe-cluster-config-apply + > Validating configuration + > ... + > Configuración de agrupación finalizada + ``` + +5. Para probar que el plugin de Nagios puede ejecutar el comando exitosamente, ejecútalo interactivamente desde el host de Nagios. + ```shell + nagiosuser@nagios:~$ /usr/lib/nagios/plugins/check_by_ssh -l admin -p 122 -H hostname -C "ghe-cluster-status -n" -t 30 + > OK - No errors detected + ``` + +6. Crea una definición de comando en tu configuración Nagios. + + ###### Definición de ejemplo + + ``` + definir comando { + command_name check_ssh_ghe_cluster + command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -C "ghe-cluster-status -n" -l admin -p 122 -t 30 + } + ``` +7. Agrega este comando a una definición de servicio para un nodo en la agrupación de {% data variables.product.prodname_ghe_server %}. + + + ###### Definición de ejemplo + + ``` + define host{ + use generic-host + host_name ghe-data-node-0 + alias ghe-data-node-0 + address 10.11.17.180 + } + + define service{ + use generic-service + host_name ghe-data-node-0 + service_description GitHub Cluster Status + check_command check_ssh_ghe_cluster + } + ``` + +En cuanto agregues la definición a Nagios, se ejecutará la comprobación del servicio de acuerdo con tu configuración. Deberías poder ver el servicio configurado recientemente en la interfaz web de Nagios. + +![Ejemplo de Nagios](/assets/images/enterprise/cluster/nagios-example.png) diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md new file mode 100644 index 0000000000000..7bdf58ff4da0b --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md @@ -0,0 +1,108 @@ +--- +title: Supervisar por medio de SNMP +intro: '{% data variables.product.prodname_enterprise %} proporciona datos sobre el uso del disco, la utilización del CPU, el uso de la memoria y más sobre SNMP.' +redirect_from: + - /enterprise/admin/installation/monitoring-using-snmp + - /enterprise/admin/articles/monitoring-using-snmp/ + - /enterprise/admin/enterprise-management/monitoring-using-snmp +versions: + enterprise-server: '*' +--- + +SNMP es una norma común para controlar dispositivos en una red. Recomendamos firmemente habilitar SNMP para que puedas controlar la salud de {% data variables.product.product_location %} y saber cuándo agregar más memoria, almacenamiento, o rendimiento del procesador a la máquina del servidor. + +{% data variables.product.prodname_enterprise %} tiene una instalación SNMP estándar, para poder aprovechar los [diversos plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) disponibles para Nagios o para cualquier otro sistema de control. + +### Configurar SNMP v2c + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. En el campo **Community string (Cadena de la comunidad)**, ingresa una nueva cadena de comunidad. Si se deja en blanco, queda predeterminado como `públicp`. ![Campo para añadir la cadena de comunidad](/assets/images/enterprise/management-console/community-string.png) +{% data reusables.enterprise_management_console.save-settings %} +5. Prueba tu configuración SNMP al ejecutar el siguiente comando en una estación de trabajo por separado con soporte de SNMP en tu red: + ```shell + # community-string is your community string + # hostname is the IP or domain of your Enterprise instance + $ snmpget -v 2c -c community-string -O e hostname hrSystemDate.0 + ``` + +Debería devolver la hora del sistema en el host {% data variables.product.product_location %}. + +### Seguridad basada en el usuario + +Si habilitas el SNMP v3, puedes aprovechar la seguridad en base al usuario aumentada a través de User Security Model (USM). Para cada usuario único, puedes especificar un nivel de seguridad: +- `noAuthNoPriv`: este nivel de seguridad no brinda autenticación ni privacidad. +- `authNoPriv`: este nivel de seguridad brinda autenticación pero no privacidad. Para consultar al aparato deberás usar un nombre de usuario y una contraseña (que debe tener como mínimo ocho caracteres). La información se envía sin encriptación, similar a SNMPv2. El protocolo de autenticación puede ser MD5 o SHA o SHA como predeterminado. +- `authPriv`: este nivel de seguridad brinda autenticación con privacidad. Se requiere autenticación, incluida una contraseña de autenticación de ocho caracteres como mínimo, y las respuestas están encriptadas. No se requiere una contraseña de privacidad, pero si se proporciona debe tener como mínimo ocho caracteres. Si no se proporciona una contraseña de privacidad, se usa la contraseña de autenticación. El protocolo de privacidad puede ser DES o AES y queda AES como predeterminado. + +### Configurando usuarios para SNMP v3 + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. Selecciona **SNMP v3**. ![Botón para habilitar SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png) +5. En "Username (Nombre de usuario)", escribe el nombre de usuario único de tu usuario SNMP v3.![Campo para escribir el nombre de usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-username.png) +6. En el menú desplegable **Security Level (Nivel de seguridad)**, haz clic en el nivel de seguridad para tu usuario SNMP v3. ![Menú desplegable para el nivel de seguridad del usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) +7. Para usuarios SNMP v3 con el nivel de seguridad `authnopriv`: ![Configuración para el nivel de seguridad authnopriv](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) + - {% data reusables.enterprise_management_console.authentication-password %} + - {% data reusables.enterprise_management_console.authentication-protocol %} +8. Para usuarios SNMP v3 con el nivel de seguridad `authpriv`: ![Configuración para el nivel de seguridad authpriv](/assets/images/enterprise/management-console/snmpv3-authpriv.png) + - {% data reusables.enterprise_management_console.authentication-password %} + - {% data reusables.enterprise_management_console.authentication-protocol %} + - De forma opcional, en "Privacy password" (Contraseña de privacidad), escribe la contraseña de privacidad. + - Hacia la derecha de "Privacy password" (Contraseña de privacidad), en el menú desplegable **Protocol (Protocolo)**, haz clic en el método de protocolo de privacidad que deseas usar. +9. Haz clic en **Add secret (Agregar secreto)**. ![Botón para añadir usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-adduser.png) +{% data reusables.enterprise_management_console.save-settings %} + +##### Consultar datos de SNMP + +Tanto la información del nivel de software como de hardware sobre tu aparato está disponible con SNMP v3. Debido a la falta de encriptación y privacidad para los niveles de seguridad `noAuthNoPriv` y `authNoPriv`, excluimos la tabla `hrSWRun` (1.1.3.6.1.2.1.25.41) de los informes SNMP resultantes. Incluimos esta tabla si estás usando el nivel de seguridad `authPriv`. + +Con SNMP v2c, solo está disponible la información del nivel de hardware de tu aparato. Estas aplicaciones y servicios dentro de {% data variables.product.prodname_enterprise %} no tienen configurado OID para informar métricas. Hay varios MIB disponibles, que puedes ver ejecutando `snmpwalk` en una estación de trabajo separada con soporte SNMP en tu red: + +```shell +# community-string es tu cadena de comunidad +# hostname es la IP o dominio de tu instancia de empresa +$ snmpwalk -v 2c -c community-string -O e hostname +``` + +De los MIB disponibles para SNMP, el más útil es `HOST-RESOURCES-MIB` (.1.3.6.1.2.1.25). Consulta la tabla de abajo para ver algunos objetos importantes en este MIB: + +| Nombre | OID | Descripción | +| -------------------------- | ------------------------- | ----------------------------------------------------------------------------------------------- | +| hrSystemDate.2 | .1.3.6.1.2.1.25.1.2 | La noción de servidores de los datos locales y de la hora del día. | +| hrSystemUptime.0 | .1.3.6.1.2.1.25.1.1.0 | Cuánto tiempo ha pasado desde que el servidor se inició por última vez. | +| hrMemorySize.0 | .1.3.6.1.2.1.25.2.2.0 | La cantidad de RAM en el servidor. | +| hrSystemProcesses.0 | .1.3.6.1.2.1.25.1.6.0 | La cantidad de contextos de proceso actualmente cargados o ejecutándose en el servidor. | +| hrStorageUsed.1 | .1.3.6.1.2.1.25.2.3.1.6.1 | La cantidad de espacio de almacenamiento consumido en el servidor, en hrStorageAllocationUnits. | +| hrStorageAllocationUnits.1 | .1.3.6.1.2.1.25.2.3.1.4.1 | El tamaño, en bytes, de una hrStorageAllocationUnit | + +Por ejemplo, para consultar `hrMemorySize` con SNMP v3, ejecuta el siguiente comando en una estación de trabajo separada con apoyo de SNMP en tu red: +```shell +# username es el nombre de usuario único de tu usuario SNMP v3 +# auth password es la contraseña de autenticación +# privacy password es la contraseña de privacidad +# hostname es la IP o el dominio de tu instancia de empresa +$ snmpget -v 3 -u username -l authPriv \ + -A "auth password" -a SHA \ + -X "privacy password" -x AES \ + -O e hostname HOST-RESOURCES-MIB::hrMemorySize.0 +``` + +Con SNMP v2c, para consultar `hrMemorySize`, ejecuta el siguiente comando en una estación de trabajo separada con apoyo de SNMP en tu red: +```shell +# community-string es tu cadena de comunidad +# hostname es la IP o el dominio de tu instancia de empresa +snmpget -v 2c -c community-string hostname HOST-RESOURCES-MIB::hrMemorySize.0 +``` + +{% tip %} + +**Nota:** para evitar que se filtre información sobre los servicios que se están ejecutando en tu aparato, excluimos la tabla `hrSWRun` (1.1.3.6.1.2.1.25.41) de los informes SNMP resultantes excepto que estés usando el nivel de seguridad `authPriv` con SNMP v3. Si estás utilizando el nivel de seguridad `authPriv`, incluimos la tabla `hrSWRun`. + +{% endtip %} + +Para obtener más información sobre los mapeos OID para los atributos de sistema comunes en SNMP, consulta "[OID SNMP de Linux para CPU, memoria y estadísticas de disco](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)". diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md new file mode 100644 index 0000000000000..d5445dccb9879 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md @@ -0,0 +1,13 @@ +--- +title: Monitorear tu aplicativo +intro: 'Debido a que el uso {% data variables.product.product_location %} aumenta con el tiempo, se incrementará la utilización de recursos del sistema, como el CPU, la memoria, y el almacenamiento. Puedes configurar una revisión y alertas para que estar al tanto de problemas potenciales antes de que se vuelvan lo suficientemente críticos para impactar de forma negativa en el desempeño de la aplicación o su disponibilidad.' +redirect_from: + - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting/ + - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/ + - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance + - /enterprise/admin/enterprise-management/monitoring-your-appliance +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md new file mode 100644 index 0000000000000..4059761f9b106 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md @@ -0,0 +1,44 @@ +--- +title: Límites de alerta recomendados +intro: 'Puedes configurar una alerta para notificar los problemas de tus recursos de sistema antes de que afecten el desempeño de tu aparato {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/guides/installation/about-recommended-alert-thresholds/ + - /enterprise/admin/installation/about-recommended-alert-thresholds + - /enterprise/admin/installation/recommended-alert-thresholds + - /enterprise/admin/enterprise-management/recommended-alert-thresholds +versions: + enterprise-server: '*' +--- + +### Controlar el almacenamiento + +Recomendamos que controles los dispositivos de almacenamiento de usuario y raíz y configures una alerta con valores que permitan un gran tiempo de respuesta cuando el espacio de disco disponible sea bajo. + +| Severity | Límite | +| ----------- | ---------------------------------------------------- | +| **Warning** | El disco excede el 70 % del total disponible | +| **Crítico** | El uso del disco excede el 85 % del total disponible | + +Puedes ajustar estos valores en base a la cantidad total de almacenamiento asignado, los patrones de crecimiento histórico y el tiempo esperado de respuesta. Recomendamos asignar en exceso recursos de almacenamiento para permitir el crecimiento y evitar el tiempo de inactividad requerido para asignar almacenamiento adicional. + +### Controlar el uso del CPU y de la carga promedio + +A pesar de que es normal que el uso de CPU fluctúe en base a las operaciones Git que utilizan muchos recursos, recomendamos configurar una alerta para la utilización del CPU anormalmente alta, ya que spikes prolongados puede significar que tu instancia tiene un aprovisionamiento insuficiente. Recomendamos controlar la carga promedio del sistema de quince minutos para los valores que se acerquen o excedan la cantidad de núcleos de CPU asignados en la máquina virtual. + +| Severity | Límite | +| ----------- | --------------------------------------------------------------- | +| **Warning** | La carga promedio de quince minutos excede 1x de núcleos de CPU | +| **Crítico** | La carga promedio de quince minutos excede 2x de núcleos de CPU | + +También recomendamos que controles el tiempo de "robo" de virtualización para asegurar que otras máquinas virtuales ejecutándose en el mismo sistema de servidor no estén usando todos los recursos de la instancia. + +### Controla el uso de la memoria + +La cantidad de memoria física asignada a {% data variables.product.product_location %} puede tener un gran impacto sobre el desempeño general y la capacidad de respuesta de la aplicación. El sistema está designado para realizar un uso intenso del caché del disco kernel para acelerar las operaciones Git. Recomendamos que el conjunto en funcionamiento de RSS normal se acomode dentro del 50 % del total de RAM disponible para un uso máximo. + +| Severity | Límite | +| ----------- | ---------------------------------------------------------------------- | +| **Warning** | El uso sostenido de RSS excede el 50 % del total de memoria disponible | +| **Crítico** | El uso sostenido de RSS excede el 70 % del total de memoria disponible | + +Si se acaba la memoria, el killer de OOM kernel intentará liberar recursos de memoria al sacrificar de manera forzosa procesos de aplicación con mucho uso de RAM, lo que puede dar como resultado una interrupción del servicio. Recomendamos asignar más memoria a la máquina virtual de la requerida en el curso normal de las operaciones. diff --git a/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md new file mode 100644 index 0000000000000..0daca35194fd8 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md @@ -0,0 +1,28 @@ +--- +title: Recuperar una configuración de disponibilidad alta +intro: 'Después de la conmutación por error de un aparato {% data variables.product.prodname_ghe_server %}, debes recuperar redundancia tan pronto como sea posible en lugar de depender de un aparato único.' +redirect_from: + - /enterprise/admin/installation/recovering-a-high-availability-configuration + - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration +versions: + enterprise-server: '*' +--- + +Puedes utilizar el aparato principal antiguo como el nuevo aparato de réplica si la conmutación por error fue planeada o no estaba relacionada con la salud del aparato. Si la conmutación por error estaba relacionado con un problema con el aparato primario, es posible que prefieras crear un nuevo aparato de réplica. Para obtener más información, consulta "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)." + +### Configurar un aparato principal antiguo como una nueva réplica + +1. Conéctate a la dirección IP del aparato principal antiguo utilizando SSH. + ```shell + $ ssh -p 122 admin@FORMER PRIMARY IP + ``` +2. En el aparato principal antiguo, ejecuta el comando `ghe-repl-setup` con la dirección IP de la réplica antigua. + ```shell + $ ghe-repl-setup FORMER REPLICA IP + ``` +{% data reusables.enterprise_installation.add-ssh-key-to-primary %} +4. Para verificar la conexión con el aparato principal nuevo y habilitar el modo réplica para la nueva réplica, ejecuta nuevamente `ghe-repl-setup`. + ```shell + $ ghe-repl-setup FORMER REPLICA IP + ``` +{% data reusables.enterprise_installation.replication-command %} diff --git a/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md new file mode 100644 index 0000000000000..bb8e428ff2b47 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -0,0 +1,41 @@ +--- +title: Quitar una réplica de disponibilidad alta +intro: 'Puedes detener una replicación a una réplica {% data variables.product.prodname_ghe_server %} de forma temporal, o quitar la replicación de forma permanente.' +redirect_from: + - /enterprise/admin/installation/removing-a-high-availability-replica + - /enterprise/admin/enterprise-management/removing-a-high-availability-replica +versions: + enterprise-server: '*' +--- + +### Detener una replicación de forma temporal + +1. Si es necesario, puedes detener una replicación geográfica del tráfico de usuario activo al quitar las entradas Geo DNS para la réplica. +2. En la réplica donde deseas detener la replicación de forma temporal, ejecuta ghe-repl-stop. + ```shell + $ ghe-repl-stop + ``` +3. Para comenzar la replicación nuevamente, ejecuta `ghe-repl-start`. + ```shell + $ ghe-repl-start + ``` + +### Quitar la replicación de forma permanente + +1. Si es necesario, puedes detener una replicación geográfica del tráfico de usuario activo al quitar las entradas Geo DNS para la réplica. +2. En la réplica donde deseas quitar la replicación, ejecuta `ghe-repl-stop`. + ```shell + $ ghe-repl-stop + ``` +3. En la réplica, para acabar con el estado de replicación, ejecuta `ghe-repl-teardown`. + ```shell + $ ghe-repl-teardown + ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Nota:** Si tienes habilitadas las {% data variables.product.prodname_actions %}, deberás decomisionar el servidor de réplica anterior o actualizar su configuración de {% data variables.product.prodname_actions %} para que utilice un almacenamiento externo diferente. Para obtener más información, consulta la sección "[Disponibilidad alta para {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)". + + {% endnote %} + {% endif %} diff --git a/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md new file mode 100644 index 0000000000000..e24b06cf4d50c --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md @@ -0,0 +1,37 @@ +--- +title: Reemplazar un nodo de agrupación +intro: 'Para reemplazar un nodo {% data variables.product.prodname_ghe_server %}, debes marcar los nodos fuera de línea afectados en el archivo de configuración de la agrupación (`cluster.conf`) y agregar los nodos de reemplazo. Esto puede ser necesario en caso de que un nodo falle, o para agregar un nodo con más recursos a fin de aumentar el rendimiento.' +redirect_from: + - /enterprise/admin/clustering/replacing-a-cluster-node + - /enterprise/admin/enterprise-management/replacing-a-cluster-node +versions: + enterprise-server: '*' +--- + +{% warning %} + +**Advertencia** El nodo de reemplazo debe usar un nodo de nombre de host que no haya sido usado anteriormente en la agrupación para evitar conflictos. + +{% endwarning %} + +### Reemplazar un nodo funcional +{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %} + +### Reemplazar un nodo en una emergencia +{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} +{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %} diff --git a/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md new file mode 100644 index 0000000000000..588e16c16b0fc --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md @@ -0,0 +1,19 @@ +--- +title: Configurar la revisión externa +intro: 'Puedes revisar los recursos de sistema básicos en tu aparato {% data variables.product.prodname_ghe_server %} utilizando el SNMP o los protocolos de recopilación de estadísticas collectd.' +redirect_from: + - /enterprise/admin/installation/setting-up-external-monitoring + - /enterprise/admin/enterprise-management/setting-up-external-monitoring +versions: + enterprise-server: '*' +--- + +### Acerca de SNMP + +El Protocolo de Administración de Red Simple (SNMP) es un método muy compatible para revisar los dispositivos y los servidores de red. El SNMP está inhabilitado por defecto pero puede ser configurado a través del tablero de revisión {% data variables.product.prodname_enterprise %}. El puerto UDP 161 debe abrirse y ser accesible desde tu estación de administración de red. Para obtener más información, consulta "[Revisión utilizando el SNMP](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-using-snmp/)." + +### Acerca de collectd + +collectd es una recopilación de estadísticas de código abierto y daemon de información con apoyo integrado para escribir en archivos RRD. Las estadísticas sobre utilización de CPU, memoria y uso de disco, errores y tráfico de interfaz de red y carga de sistema pueden redireccionarse a un servidor externo collectd donde se pueden configurar los gráficos, los análisis y las alertas utilizando un amplia gama de herramientas y plugins disponibles. Para configurar el redireccionamiento de `collectd`, consulta "[Configurar collectd](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-collectd/)". + +Además, las herramientas de supervisión dentro de las plataformas de virtualización subyacentes pueden también usarse para supervisar y alertar sobre los recursos de sistema. Para obtener más información, consulta la documentación [Amazon CloudWatch](http://aws.amazon.com/cloudwatch/) y [Supervisión de VMware vSphere ](http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf). diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md new file mode 100644 index 0000000000000..45c6093fcea87 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md @@ -0,0 +1,13 @@ +--- +title: Actualizar la máquina virtual y los recursos físicos +intro: 'La actualización del software virtual y del hardware virtual requiere algo de tiempo de inactividad para tu instancia, por ello asegúrate de planear tu actualización de antemano.' +redirect_from: + - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm/' + - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/' + - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources + - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md b/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md new file mode 100644 index 0000000000000..ba46bb51c38b8 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md @@ -0,0 +1,42 @@ +--- +title: Requisitos de actualización +intro: 'Antes de actualizar el {% data variables.product.prodname_ghe_server %}, revisa estas recomendaciones y requisitos para planificar tu estrategia de actualización.' +redirect_from: + - /enterprise/admin/installation/upgrade-requirements + - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/ + - /enterprise/admin/enterprise-management/upgrade-requirements +versions: + enterprise-server: '*' +--- + +{% note %} + +**Notas:** +- Para actualizar desde {% data variables.product.prodname_enterprise %} 11.10.348 a {% data variables.product.current-340-version %}, debes primero migrar a {% data variables.product.prodname_enterprise %} 2.1.23. Para obtener más información, consulta "[Migrar desde {% data variables.product.prodname_enterprise %} 11.10.x a 2.1.23](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23)." +- Los paquetes de actualización están disponibles en [enterprise.github.com](https://enterprise.github.com/releases) para las versiones admitidas. Verifica la disponibilidad de los paquetes de actualización, deberás completar la actualización. Si un paquete no está disponible, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda. +- Si estás usando una Agrupación del {% data variables.product.prodname_ghe_server %}, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" en la Guía de Agrupación del {% data variables.product.prodname_ghe_server %} para obtener instrucciones específicas únicas para agrupaciones. +- Estas notas de lanzamiento para el {% data variables.product.prodname_ghe_server %} brindan una lista detallada de las nuevas características de cada versión del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta las [páginas de lanzamiento](https://enterprise.github.com/releases). + +{% endnote %} + +### Recomendaciones + +- Incluye tantas nuevas actualizaciones como sea posible en tu proceso de actualización. Por ejemplo, en lugar de actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.supported[1] }} a {{ enterpriseServerReleases.latest }}, podrías actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.latest }}. +- Si estás varias versiones desactualizado, actualiza {% data variables.product.product_location %} tanto como sea posible con cada paso de tu proceso de actualización. Utilizar la versión más reciente posible en cada actualización te permite aprovechar las mejoras de desempeño y las correcciones de errores. Por ejemplo, podrías actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.8 a 2.10, pero actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.9 a 2.10 utiliza una versión posterior en el segundo paso. +- Utiliza el lanzamiento de patch más reciente cuando actualices. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} +- Utiliza una instancia de preparación para probar los pasos de actualización. Para obtener más información, consulta "[Configurar una instancia de preparación](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)." +- Cuando ejecutes múltiples actualizaciones, espera por lo menos 24 horas entre las actualizaciones de características para permitir que las tareas de actualización de migraciones de datos y de datos en copias de seguridad se completen en su totalidad. + +### Requisitos + +- Debes actualizar desde una característica de lanzamiento que sea **como máximo** dos lanzamientos anteriores. Por ejemplo, para actualizar a {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, debes estar en {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} o {{ enterpriseServerReleases.supported[2] }}. +- {% data reusables.enterprise_installation.hotpatching-explanation %} +- Es posible que un hotpatch requiera tiempo de inactividad si los servicios afectados (como kernel, MySQL, o Elasticsearch) requieren un reinicio de VM o un reinicio del servicio. Se te notificará cuando se necesite reiniciar. Puedes completar el reinicio más tarde. +- Es necesario que haya un almacenamiento raíz adicional disponible cuando se actualiza a través de un hotpatch, ya que instala múltiples versiones de determinados servicios hasta que se completa la actualización. El control de prevuelo te notificará si no tienes suficiente almacenamiento de disco raíz. +- Cuando se actualiza a través de un hotpatch, tu instancia no puede estar muy cargada, ya que puede impactar el proceso del hotpatch. Los controles de pre-vuelo considerarán la carga promedio y, posteriormente, la mejora fallará si dicha carga promedio es demasiado alta. - Mejorar a {% data variables.product.prodname_ghe_server %} 2.17 migrará sus registros de auditoría de Elasicsearch a MySQL. Esta migración también incrementa la cantidad de tiempo y el espacio en disco que lleva restaurar una instantánea. Antes de migrar, controla el número de bytes en tus índices de registro de auditoría de ElasticSearch con este comando: +``` shell +curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes +``` +Utiliza el número para estimar la cantidad de espacio de disco que los registros de auditoría de MySQL necesitarán. El script también controla tu espacio libre en disco mientras la importación está en progreso. Controlar este número es especialmente útil si tu espacio libre en disco está cerca de la cantidad de espacio en disco necesaria para la migración. + +Después de revisar estas recomendaciones y requisitos, puedes actualizar el {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md new file mode 100644 index 0000000000000..84014abd128c4 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md @@ -0,0 +1,77 @@ +--- +title: Actualizar una agrupación +intro: 'Usa el shell administrativo (SSH) para actualizar una agrupación de {% data variables.product.prodname_ghe_server %} a la última versión.' +redirect_from: + - /enterprise/admin/clustering/upgrading-a-cluster + - /enterprise/admin/enterprise-management/upgrading-a-cluster +versions: + enterprise-server: '*' +--- + +### Actualizar con un hotpatch +{% data reusables.enterprise_installation.hotpatching-explanation %}El script de instalación de hotpatch instala el hotpatch en cada nodo de la agrupación y reinicia los servicios en su secuencia adecuada para evitar el tiempo de inactividad. + +1. Realiza una copia de seguridad de tus datos con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). +2. Desde el shell administrativo de cualquier nodo, usa el comando ` ghe-cluster-hotpatch` para instalar el último hotpatch. Puedes proporcionar una URL para un hotpatch, o descargar manualmente el hotpatch y especificar un nombre de archivo local. + ```shell + $ ghe-cluster-hotpatch https://HOTPATCH-URL/FILENAME.hpkg + ``` + +### Actualizar con un paquete de actualización +Usa un paquete de actualización para actualizar una agrupación de {% data variables.product.prodname_ghe_server %} a la última característica de lanzamiento. Por ejemplo, puedes actualizar desde `2.11` hasta `2.13`. + +#### Preparar para una actualización + +1. Revisa la [Configuración de red de la agrupación](/enterprise/admin/guides/clustering/cluster-network-configuration) para la versión a la que deseas avanzar y realiza las actualizaciones conforme sea necesario. +2. Realiza una copia de seguridad de tus datos con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). +3. Planifica una ventana de mantenimiento para los usuarios finales de tu agrupación de {% data variables.product.prodname_ghe_server %}, dado que no estará disponible para usar normalmente durante la actualización. El modo de mantenimiento bloquea el acceso de los usuarios e impide que se realicen cambios en los datos mientras la actualización de la agrupación está en curso. +4. En [{% data variables.product.prodname_ghe_server %} Descargar página](https://enterprise.github.com/download), copia la URL para el archivo de actualización *.pkg* en el portapapeles. +5. Desde el shell administrativo de cualquier nodo, usa el comando `ghe-cluster-each` combinado con `curl` para descargar el paquete de lanzamiento para cada nodo en un solo paso. Usa la URL que copiaste en el paso anterior como argumento. + ```shell + $ ghe-cluster-each -- "cd /home/admin && curl -L -O https://PACKAGE-URL.pkg" + > ghe-app-node-1: % Total % Received % Xferd Average Speed Time Time Time Current + > ghe-app-node-1: Dload Upload Total Spent Left Speed + > 100 496M 100 496M 0 0 24.2M 0 0:00:20 0:00:20 --:--:-- 27.4M + > ghe-data-node-2: % Total % Received % Xferd Average Speed Time Time Time Current + > ghe-data-node-2: Dload Upload Total Spent Left Speed + > 100 496M 100 496M 0 0 21.3M 0 0:00:23 0:00:23 --:--:-- 25.8M + > ghe-data-node-1: % Total % Received % Xferd Average Speed Time Time Time Current + > ghe-data-node-1: Dload Upload Total Spent Left Speed + > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.6M + > ghe-app-node-2: % Total % Received % Xferd Average Speed Time Time Time Current + > ghe-app-node-2: Dload Upload Total Spent Left Speed + > 100 496M 100 496M 0 0 19.8M 0 0:00:25 0:00:25 --:--:-- 17.6M + > ghe-data-node-3: % Total % Received % Xferd Average Speed Time Time Time Current + > ghe-data-node-3: Dload Upload Total Spent Left Speed + > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.5M + ``` +6. Identifica el nodo MySQL principal, que se definió como `mysql-master = ` en `cluster.conf`. Este será el último nodo que se actualizará. + +#### Actualizar los nodos de la agrupación + +1. Habilita el modo de mantenimiento de acuerdo con tu ventana planificada conectando el shell administrativo de cualquier nodo de agrupación y ejecutando `ghe-cluster-maintenance -s`. +2. **Con la excepción del nodo primario de MySQL**, conéctate al shell administrativo de cada uno de los nodos de {% data variables.product.prodname_ghe_server %}. Ejecuta el comando `ghe-upgrade`, suministrando el nombre del archivo del paquete que descargaste en el Paso 4 de [Preparar una actualización](#preparing-to-upgrade): + ```shell + $ ghe-upgrade PACKAGE-FILENAME.pkg + > *** verifying upgrade package signature... + > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100% + > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A + > gpg: checking the trustdb + > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model + > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u + > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " + ``` +3. El proceso de actualización reiniciará el nodo MySQL principal una vez que esté completo. Verifica que puedes `hacer ping` en cada nodo luego del reinicio. +4. Conecta con el shell administrativo del nodo MySQL principal. Ejecuta el comando `ghe-upgrade`, suministrando el nombre del archivo del paquete que descargaste en el Paso 4 de [Preparar una actualización](#preparing-to-upgrade): + ```shell + $ ghe-upgrade PACKAGE-FILENAME.pkg + > *** verifying upgrade package signature... + > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100% + > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A + > gpg: checking the trustdb + > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model + > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u + > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " + ``` +5. El proceso de actualización reiniciará el nodo MySQL principal una vez que esté completo. Verifica que puedes `hacer ping` en cada nodo luego del reinicio. +6. Cierra el modo de mantenimiento desde el shell administativo de cualquier nodo al ejecutar `ghe-cluster-maintenance -u`. diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md new file mode 100644 index 0000000000000..c82513074217e --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -0,0 +1,226 @@ +--- +title: Actualizar el servidor de GitHub Enterprise +intro: 'Actualizar el {% data variables.product.prodname_ghe_server %} para obtener las funciones y las actualizaciones de seguridad más recientes.' +redirect_from: + - /enterprise/admin/installation/upgrading-github-enterprise-server + - /enterprise/admin/articles/upgrading-to-the-latest-release/ + - /enterprise/admin/articles/migrations-and-upgrades/ + - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine/ + - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases/ + - /enterprise/admin/articles/upgrading-older-installations/ + - /enterprise/admin/hidden/upgrading-older-installations/ + - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program/ + - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch/ + - /enterprise/admin/guides/installation/upgrading-github-enterprise/ + - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server +versions: + enterprise-server: '*' +--- + +### Preparar para una actualización + +1. Determina una estrategia de actualización y elige una versión a la que actualizar. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +3. Crea una copia de seguridad nueva de tu instancia principal con las {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta el archivo README.md en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). +4. Si estás actualizando con un paquete de actualización, programa una ventana de mantenimiento para los usuarios finales del {% data variables.product.prodname_ghe_server %}. Si estás usando un hotpatch, no se necesita el modo mantenimiento. + + {% note %} + + **Nota:** la ventana de mantenimiento depende del tipo de actualización que realices. Las actualizaciones que utilizan un hotpatch por lo general no necesitan una ventana de mantenimiento. A veces se necesita reiniciar; puedes hacerlo más tarde. Siguiendo el esquema de control de versiones de MAJOR.FEATURE.PATCH, los lanzamientos de patch que utilizan un paquete de actualización normalmente necesitan menos de cinco minutos de tiempo de inactividad. Los lanzamientos de funciones que incluyen migraciones de datos toman más tiempo dependiendo del desempeño del almacenamiento y de la cantidad de datos que se migran. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + + {% endnote %} + +### Tomar una instantánea + +Una instantánea es un punto de verificación de una máquina virtual (VM) en un momento en el tiempo. Recomendamos firmemente tomar una instantánea antes de actualizar tu máquina virtual para que si falla una actualización, puedas revertir tu VM nuevamente a la instantánea. Si no estás actualizando a un nuevo lanzamiento de característica, debes tomar una instantánea de VM. Si estás actualizando a un nuevo lanzamiento de patch, puedes adjuntar el disco de datos existente. + +Hay dos tipos de instantáneas: + +- **Las instantáneas de VM** guardan el estado completo de tu VM, incluidos los datos del usuario y los datos de configuración. Este método de instantáneas requiere una gran cantidad de espacio de disco e insume mucho tiempo. +- **Las instantáneas de disco de datos** únicamente guardan tus datos de usuario. + + {% note %} + + **Notas:** + - Algunas plataformas no permiten que tomes una instantánea solo de tu disco de datos. Para estas plataformas, necesitarás tomar una instantánea de tu VM completa. + - Si tu hipervisor no admite instantáneas de VM completas, debes tomar una instantánea de tu disco raíz y de tu disco de datos en rápida sucesión. + + {% endnote %} + +| Plataforma | Método de instantánea | URL de documentación de instantánea | +| --------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Amazon AWS | Disco | | +| Azure | VM | | +| Hyper-V | VM | | +| Google Compute Engine | Disco | | +| VMware | VM | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) | +| XenServer | VM | | + +### Actualizar con un hotpatch + +{% data reusables.enterprise_installation.hotpatching-explanation %} Utilizando la {% data variables.enterprise.management_console %}, puedes instalar un hotpatch de forma inmediata o programar la instalación para más tarde. Puedes utilizar el shell administrativo para instalar un hotpatch con la herramienta `ghe-upgrade`. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." + +{% note %} + +**Note**: instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} no está disponible en los entornos de agrupación. Para instalar un parche en un entorno de agrupación, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." + +{% endnote %} + +#### Actualizar un aparato único con un hotpatch + +##### Instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} + +1. Habilitar actualizaciones automáticas. Para obtener más información, consulta "[Habilitar actualizaciones automáticas](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.updates-tab %} +4. Cuando se ha descargado un nuevo hotpatch, utiliza el menú desplegable del paquete de instalación: + - Para instalar de forma inmediata, selecciona **Now (Ahora)**: + - Para instalarlo más tarde, selecciona una fecha posterior. ![Menú desplegable de fecha de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png) +5. Da clic en **Instalar**. ![Botón de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png) + +##### Instalar un hotpatch utilizando un shell administrativo + +{% data reusables.enterprise_installation.download-note %} + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copia el URL para obtener el paquete de actualización (*.hpkg* file). +{% data reusables.enterprise_installation.download-package %} +4. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: + ```shell + admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg + *** verifying upgrade package signature... + ``` +5. Si se requiere un reinicio para las actualizaciones de kernel, MySQL, Elasticsearch u otros programas, el script de actualización de hotpatch te avisa. + +#### Actualizar un aparato que tiene instancias de réplica utilizando un hotpatch + +{% note %} + +**Nota**: si estás instalando un hotpatch, no necesitas entrar en modo de mantenimiento o detener la replicación. + +{% endnote %} + +Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. + +##### Actualizar la instancia principal + +1. Actualiza la instancia principal siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)." + +##### Actualizar una instancia de réplica + +{% note %} + +**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. + +{% endnote %} + +1. Mejora la instancia de répica siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. +{% data reusables.enterprise_installation.replica-ssh %} +{% data reusables.enterprise_installation.replica-verify %} + +### Actualizar con un paquete de actualización + +Al mismo tiempo que puedes utilizar un hotpatch para actualizar al lanzamiento de patch más reciente dentro de una serie de características, debes utilizar un paquete de actualización para actualizar a un lanzamiento de característica más nuevo. Por ejemplo para actualizar de `2.11.10` a `2.12.4` debes utilizar un paquete de actualización ya que están en series de características diferentes. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." + +#### Actualizar un aparato único con un paquete de actualización + +{% data reusables.enterprise_installation.download-note %} + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Selecciona la plataforma adecuada y copia el URL para obtener el paquete de actualización (*.pkg* file). +{% data reusables.enterprise_installation.download-package %} +4. Habilita el modo mantenimiento y espera que se completen todos los procesos activos en la instancia del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + + {% note %} + + **Nota**: cuando se actualiza el aparato primario en una configuración de alta disponibilidad, el aparato debería estar ya en modo mantenimiento si estás siguiendo las instrucciones en "[Actualizar la instancia primaria](#upgrading-the-primary-instance)." + + {% endnote %} + +5. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: + ```shell + admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg + *** verifying upgrade package signature... + ``` +6. Confirma que te gustaría continuar con la actualización y reinicia después de que se verifique la firma del paquete. El nuevo sistema de archivos raíz escribe en la segunda partición y la instancia de forma automática se reinicia en modo mantenimiento: + ```shell + *** aplicando actualización... + This package will upgrade your installation to version version-number + Current root partition: /dev/xvda1 [version-number] + Target root partition: /dev/xvda2 + Proceed with installation? [s/N] + ``` +7. Para las actualizaciones de aparato único, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location %}. + + {% note %} + + **Nota**: cuando se actualizan aparatos en configuración de alta disponibilidad, deberías mantener el modo mantenimiento hasta que hayas actualizado todas las réplicas y la replicación esté en curso. Para obtener más información, consulta "[Actualizar una instancia de réplica](#upgrading-a-replica-instance)." + + {% endnote %} + +#### Actualizar un aparato que tiene instancias de réplica utilizando un paquete de actualización + +Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. + +##### Actualizar la instancia principal + +{% warning %} + +**Advertencia:** Cuando se detiene una replicación, si falla la primaria, se perderá cualquier trabajo que se realice antes de que la réplica esté actualizada y comience nuevamente la replicación. + +{% endwarning %} + +1. En la instancia primaria, habilita el modo mantenimiento y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." +{% data reusables.enterprise_installation.replica-ssh %} +3. En la instancia de réplica, o en todas las instancias de réplica si estás ejecutando múltiples instancias de réplica como parte de una replicación geográfica, ejecuta `ghe-repl-stop` para detener la replicación. +4. Actualiza la instancia primaria siguiendo las instrucciones en "[Actualizar un aparato único con un paquete de actualización](#upgrading-a-single-appliance-with-an-upgrade-package)." + +##### Actualizar una instancia de réplica + +{% note %} + +**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. + +{% endnote %} + +1. Actualiza la instancia de la réplica siguiendo las instrucciones en la sección "[Mejorar un solo aplicativo con un paquete de mejora](#upgrading-a-single-appliance-with-an-upgrade-package)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. +{% data reusables.enterprise_installation.replica-ssh %} +{% data reusables.enterprise_installation.replica-verify %} + +{% data reusables.enterprise_installation.start-replication %} + +{% data reusables.enterprise_installation.replication-status %} Si el comando devuelve `La replicación no se está ejecutando`, la replicación puede estar comenzando. Espera alrededor de un minuto antes de volver a ejecutar `ghe-repl-status`. + + {% note %} + + **Nota:** mientras la resincronización está en progreso, `ghe-repl-status` puede devolver mensajes esperados que indiquen que la replicación está de forma subyacente. + Por ejemplo: `CRITICO: la replicación de git está de forma subyacente de la primaria por más de 1007 repositorios o gists` + + {% endnote %} + + Si `ghe-repl-status` no devuelve `OK`, sigue los pasos de abajo para iniciar la replicación de forma manual. + + 1. En la instancia de réplica, ejecuta nuevamente `ghe-repl-setup `. + {% data reusables.enterprise_installation.start-replication %} + {% data reusables.enterprise_installation.replication-status %} +6. Cuando hayas completado la actualización de la última réplica, y se haya completado la resincronización, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location %}. + +### Restaurar desde una actualización fallida + +Si una actualización falla o se interrumpe, deberías revertir tu instancia a su estado anterior. El proceso para completar esto depende del tipo de actualización. + +#### Revertir un lanzamiento de patch + +Para volver a lanzar una versión de parche, usa el comando `ghe-upgrade` con el comando `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} + +Para obtener más información, consulta "[Herramientas de línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." + +#### Revertir un lanzamiento de característica + +Para revertir un lanzamiento de característica, restaura desde una instantánea de VM para garantizar que las particiones raíz y de datos estén en un estado consistente. Para obtener más información, consulta "[Tomar una instantánea](#taking-a-snapshot)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Further reading + +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md new file mode 100644 index 0000000000000..c4186a5ba38c7 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md @@ -0,0 +1,130 @@ +--- +title: Acerca del soporte de GitHub Enterprise +intro: '{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas que se presenten en {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/enterprise-support/about-github-enterprise-support +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota**: {% data reusables.support.data-protection-and-privacy %} + +{% endnote %} + +### Acerca de {% data variables.contact.enterprise_support %} + +{% data variables.product.product_name %} incluye el {% data variables.contact.enterprise_support %} en inglés{% if enterpriseServerVersions contains currentVersion %} y japonés{% endif %}. + +{% if enterpriseServerVersions contains currentVersion %} +Puedes contactar a +{% data variables.contact.enterprise_support %} a través de {% data variables.contact.contact_enterprise_portal %} para obtener ayuda sobre: + - Instalar y usar {% data variables.product.product_name %} + - Inspeccionar y verificar las causas de errores sospechados +{% endif %} + +Adicionalmente a todos los beneficios de {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}el {% data variables.contact.premium_support %}{% else %} el soporte para {% data variables.product.product_name %}{% endif %} ofrece: + - Soporte técnico por escrito a través del portal de soporte de 24 horas por día, los 7 días de la semana + - Soporte técnico telefónico las 24 horas del día, los 7 días de la semana + - Un{% if currentVersion == "github-ae@latest" %}n enhanced{% endif %} Acuerdo de Nivel de Servicio (SLA) {% if enterpriseServerVersions contains currentVersion %}con tiempos de respuesta inicial garantizados{% endif %} +{% if currentVersion == "github-ae@latest" %} + - Un Administrador Técnico de la Cuenta de Servicio + - Revisiones trimestrales de soporte + - Servicios administrativos administrados +{% else if enterpriseServerVersions contains currentVersion %} + - Administradores técnicos de cuenta + - Acceso a contenido prémium. + - Revisiones de estado programadas. + - Horas administrativas administradas +{% endif %} + +{% data reusables.support.government-response-times-may-vary %} + +{% if enterpriseServerVersions contains currentVersion %} +Para obtener más información, consulta "[Acerca de{% 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 %} + +{% data reusables.support.scope-of-support %} + +### Ponerte en contacto con {% data variables.contact.enterprise_support %} + +Puedes contactar a {% data variables.contact.enterprise_support %} a través del {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} del {% data variables.contact.ae_azure_portal %}{% endif %} para reportar los problemas por escrito. Para obtener más información, consulta la sección "[Recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". + +### Horas de operación + +{% if enterpriseServerVersions contains currentVersion %} +#### Soporte en inglés +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +Para cuestiones estándar no urgentes, ofrecemos soporte en inglés las 24 horas del día, 5 días a la semana, excepto fines de semana y feriados nacionales en EE.UU. El tiempo de respuesta estándar es 24 horas. + +Para los asuntos urgentes, estamos {% else %}Estamos{% endif %} disponibles las 24 horas del día, los 7 días de la semana, incluso durante los días festivos de EE.UU. + +{% data reusables.support.government-response-times-may-vary %} + +{% if enterpriseServerVersions contains currentVersion %} +#### Soporte en japonés + +Para cuestiones no urgentes, el soporte en japonés se encuentra disponible de lunes a viernes, de 9:00 a.m. a 5:00 p.m. (hora estándar en Japón), excepto los feriados nacionales en Japón. Para cuestiones urgentes, ofrecemos apoyo en inglés 24 horas al día, 7 días por semana, incluso durante las vacaciones nacionales de los Estados Unidos. + +Para encontrar una lista completa de días festivos de EE.UU. y japoneses que se celebran en {% data variables.contact.enterprise_support %}, consulta la "[Programación de días festivos](#holiday-schedules)".{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +### Cronograma de feriados + +Para asuntos urgentes, podemos ofrecerte ayudaeninglés 24 horas al día, 7 días por semana, incluyendo los días feriados de EE.UU. {% if enterpriseServerVersions contains currentVersion %}y Japón{% endif %}. + +#### Feriados en los Estados Unidos + +{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. {% if enterpriseServerVersions contains currentVersion %}, aunque nuestro equipo de soporte global se encuentra disponible para responder a los tickets urgentes{% endif %}. + +| Feriados en EE.UU. | Fecha en la que se celebra | +| --------------------------------- | --------------------------- | +| Año Nuevo | 1 de enero | +| Día de Martin Luther King, Jr. | Tercer lunes de enero | +| Día de los Presidentes | Tercer lunes de febrero | +| Día de los Caídos | Último lunes de mayo | +| Día de la Independencia | 4 de julio | +| Día del Trabajo | Primer lunes de septiembre | +| Día de los Veteranos | 12 de noviembre | +| Día de Acción de Gracias | Cuarto jueves de noviembre | +| Día posterior a Acción de Gracias | Cuarto viernes de noviembre | +| Nochebuena | 24 de diciembre | +| Día de Navidad | 25 de diciembre | +| Día posterior a Navidad | 28 de diciembre | +| Víspera de Año Nuevo | 31 de diciembre | + +#### Feriados en Japón + +{% data variables.contact.enterprise_support %} no proporciona soporte en idioma japonés desde el 28 de diciembre hasta el 3 de enero, así como en los días feriados listados en [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html). + +{% data reusables.enterprise_enterprise_support.installing-releases %} +{% endif %} + +### Asignar una prioridad a un ticket de soporte + +Cuando contactas a {% data variables.contact.enterprise_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. + +{% data reusables.support.github-can-modify-ticket-priority %} + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.support.ghes-priorities %} +{% elsif currentVersion == "github-ae@latest" %} +{% data reusables.support.ghae-priorities %} +{% endif %} + +### Resolver y cerrar tickets de soporte + +{% data reusables.support.enterprise-resolving-and-closing-tickets %} + +### Leer más + +{% if enterpriseServerVersions contains currentVersion %} +- [Preguntas frecuentes sobre {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) +- Sección 10 sobre soporte en el "[Acuerdo de licencia de {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license)"{% endif %} +- "[recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} +- "[Prepararse para emitir un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} +- [Enviar un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)" diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md new file mode 100644 index 0000000000000..ff1b6d863a1e2 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -0,0 +1,66 @@ +--- +title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Server +intro: '{% data variables.contact.premium_support %} es una oferta de soporte remunerado, adicional para clientes de {% data variables.product.prodname_enterprise %}.' +redirect_from: + - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise/ + - /enterprise/admin/guides/enterprise-support/about-premium-support/ + - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server +versions: + enterprise-server: '*' +--- + +{% note %} + +**Notas:** + +- Los términos del {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y entraron en vigencia a partir de septiembre de 2018. Si compraste {% data variables.contact.premium_support %} antes del 17 de septiembre de 2018, tu plan puede ser diferente. Comunícate con {% data variables.contact.premium_support %} para conocer más detalles. + +- {% data reusables.support.data-protection-and-privacy %} + +- Este artículo contiene los términos del {% data variables.contact.premium_support %} para clientes del {% data variables.product.prodname_ghe_server %}. Es posible que los términos sean diferentes para los clientes de {% data variables.product.prodname_ghe_cloud %} o los clientes de {% data variables.product.prodname_enterprise %} que compran {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Para más información, vea "Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}" y "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)." + +{% endnote %} + +### Acerca de {% data variables.contact.premium_support %} + +Además de todos los beneficios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} ofrece: + - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. + - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. + - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados. + - Acceso a contenido prémium. + - Revisiones de estado programadas. + - Servicios administrados. + +{% data reusables.support.about-premium-plans %} + +{% data reusables.support.signing-up-for-premium-support %} + +{% data reusables.support.scope-of-support %} Para obtener más información, consulta el "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)" (Obtener soporte del {% data variables.product.prodname_ghe_server %}). + +{% data reusables.support.contacting-premium-support %} + +### Horas de operación + +{% data variables.contact.premium_support %} está disponible 24 horas al día, 7 días a la semana. Si compraste {% data variables.contact.premium_support %} antes del 17 de septiembre de 2018, el soporte está limitado durante las vacaciones. Para más información sobre los días festivos que respeta el {% data variables.contact.premium_support %}, consulta la lista de feriados en "[Acerca del {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)". + +{% data reusables.support.service-level-agreement-response-times %} + +{% data reusables.enterprise_enterprise_support.installing-releases %} + +Debes instalar la versión mínima compatible del {% data variables.product.prodname_ghe_server %}, conforme a la sección Versiones compatibles del acuerdo de licencia aplicable, dentro de los 90 días posteriores a realizar el pedido del {% data variables.contact.premium_support %}. + +### Asignar una prioridad a un ticket de soporte + +Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. + +{% data reusables.support.github-can-modify-ticket-priority %} + +{% data reusables.support.ghes-priorities %} + +### Resolver y cerrar tickets de soporte + +{% data reusables.support.premium-resolving-and-closing-tickets %} + +{% data reusables.support.receiving-credits %} + +{% data reusables.support.accessing-premium-content %} diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md new file mode 100644 index 0000000000000..edc53580d2ca6 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -0,0 +1,71 @@ +--- +title: Acerca del soporte prémium de GitHub para GitHub Enterprise +intro: '{% data variables.contact.premium_support %} es una oferta de soporte remunerado, adicional para clientes de {% data variables.product.prodname_enterprise %}.' +redirect_from: + - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise +versions: + enterprise-server: '*' +--- + +{% note %} + +**Notas:** + +- Los términos de {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y están vigentes a partir de julio de 2019. + +- {% data reusables.support.data-protection-and-privacy %} + +- Este artículo contiene los términos de {% data variables.contact.premium_support %} para clientes de {% data variables.product.prodname_enterprise %} que compran {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Los términos de {% data variables.contact.premium_support %} pueden ser diferentes para los clientes que compran cada producto por separado. Para más información, vea "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)" y "Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}." + +{% endnote %} + +### Acerca de {% data variables.contact.premium_support %} + +Además de todos los beneficios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} ofrece: + - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. + - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. + - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados. + - Acceso a contenido prémium. + - Revisiones de estado programadas. + - Servicios administrados. + +{% data reusables.support.about-premium-plans %} + +{% data reusables.support.signing-up-for-premium-support %} + +{% data reusables.support.scope-of-support %} Para obtener más información, consulta el "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)" (Obtener soporte del {% data variables.product.prodname_ghe_server %}). + +{% data reusables.support.contacting-premium-support %} + +### Horas de operación + +{% data variables.contact.premium_support %} está disponible 24 horas al día, 7 días a la semana. + +{% data reusables.support.service-level-agreement-response-times %} + +{% data reusables.enterprise_enterprise_support.installing-releases %} + +Debes instalar la versión mínima compatible del {% data variables.product.prodname_ghe_server %}, conforme a la sección Versiones compatibles del acuerdo de licencia aplicable, dentro de los 90 días posteriores a realizar el pedido del {% data variables.contact.premium_support %}. + +### Asignar una prioridad a un ticket de soporte + +Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. + +- [Prioridades de tickets para {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud) +- [Prioridades de tickets para {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server) + +#### Prioridades de tickets para {% data variables.product.prodname_ghe_cloud %} + +{% data reusables.support.ghec-premium-priorities %} + +#### Prioridades de tickets para {% data variables.product.prodname_ghe_server %} + +{% data reusables.support.ghes-priorities %} + +### Resolver y cerrar tickets de soporte + +{% data reusables.support.premium-resolving-and-closing-tickets %} + +{% data reusables.support.receiving-credits %} + +{% data reusables.support.accessing-premium-content %} diff --git a/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md new file mode 100644 index 0000000000000..75b5448dd7c17 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md @@ -0,0 +1,81 @@ +--- +title: Acerca del soporte para Advanced Security +intro: '{% data variables.contact.enterprise_support %} puede ayudarte a solucionar problemas que encuentras mientras usas {% data variables.product.prodname_advanced_security %}.' +redirect_from: + - /enterprise/admin/enterprise-support/about-support-for-advanced-security +versions: + enterprise-server: '*' +--- + +{% note %} + +**Nota**: {% data reusables.support.data-protection-and-privacy %} + +{% endnote %} + +### Acerca del soporte para {% data variables.product.prodname_advanced_security %} + +{% data variables.product.prodname_advanced_security %} incluye {% data variables.contact.enterprise_support %} en inglés, por correo electrónico. + +### Alcance del soporte técnico + +Si tu solicitud de soporte técnico está fuera del alcance de lo que puede hacer nuestro equipo para ayudarte, podemos recomendarte los siguientes pasos para resolver el problema por fuera del {% data variables.contact.enterprise_support %}. Es probable que tu solicitud de soporte técnico esté fuera del alcance del {% data variables.contact.enterprise_support %} si se trata principalmente de lo siguiente: +- Integraciones de terceros +- Configuración del hardware +- Configuración de sistemas externos +- Proyectos de código abierto +- Creando proyectos o repositorios +- Diseño de cluster LGTM +- Crear o depurar el código de nuevas consultas para {% data variables.product.prodname_codeql %} + +Si no estás seguro de si el problema está fuera de nuestro alcance, abre un ticket y nos complacerá ayudarte a determinar la mejor manera de continuar. + +### Ponerte en contacto con {% data variables.contact.enterprise_support %} + +Puedes ponerte en contacto con {% data variables.contact.enterprise_support %} a través de {% data variables.contact.contact_enterprise_portal %} para obtener ayuda: +- Instalar y usar {% data variables.product.prodname_advanced_security %} +- Identificar y verificar las causas de los errores soportados + +### Horas de operación + +Ofrecemos soporte para {% data variables.product.prodname_advanced_security %} en Inglés 24 horas al día, 5 días a la semana, excluyendo fines de semana y días festivos en Estados Unidos. holidays. El tiempo de respuesta estándar es de 1 día hábil. + +### Cronograma de feriados + +{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. holidays. + +| Feriado en EE.UU. holiday | Fecha en la que se celebra | +| --------------------------------- | --------------------------- | +| Año Nuevo | 1 de enero | +| Día de Martin Luther King, Jr. | Tercer lunes de enero | +| Día de los Presidentes | Tercer lunes de febrero | +| Día de los Caídos | Último lunes de mayo | +| Día de la Independencia | 4 de julio | +| Día del Trabajo | Primer lunes de septiembre | +| Día de los Veteranos | 12 de noviembre | +| Día de Acción de Gracias | Cuarto jueves de noviembre | +| Día posterior a Acción de Gracias | Cuarto viernes de noviembre | +| Nochebuena | 24 de diciembre | +| Día de Navidad | 25 de diciembre | +| Día posterior a Navidad | 28 de diciembre | +| Víspera de Año Nuevo | 31 de diciembre | + +### Instalando actualizaciones de {% data variables.product.prodname_advanced_security %} + +Para asegurarse de que su instancia {% data variables.product.prodname_advanced_security %} es estable, debe instalar e implementar nuevas versiones cuando estén disponibles. Esto asegura que tengas las últimas características, modificaciones y mejoras así como cualquier actualización de las características, correcciones de código, parches u otras actualizaciones generales y correcciones para {% data variables.product.prodname_advanced_security %}. + +### Asignar una prioridad a un ticket de soporte + +Cuando contactas a {% data variables.contact.enterprise_support %} para obtener ayuda con {% data variables.product.prodname_advanced_security %}, puedes escoger una de tres prioridades para el ticket: {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. + +{% data reusables.support.github-can-modify-ticket-priority %} + +| Prioridad | Descripción | +|:-------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_advanced_security %} no funciona o se detiene o se ve gravemente afectado de tal manera que el usuario final no puede seguir utilizando el software razonablemente y no hay solución disponible para solucionar el problema. | +| {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} está funcionando de forma inconsistente, lo que provoca un deterioro de la productividad y el uso del usuario final. | +| {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} funciona consistentemente, pero el usuario final solicita cambios menores en el software, tales como actualizaciones de documentación, defectos cosméticos o mejoras. | + +### Resolver y cerrar tickets de soporte + +{% data reusables.support.enterprise-resolving-and-closing-tickets %} diff --git a/translations/es-ES/content/admin/enterprise-support/index.md b/translations/es-ES/content/admin/enterprise-support/index.md new file mode 100644 index 0000000000000..521fa3f590950 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/index.md @@ -0,0 +1,22 @@ +--- +title: 'Trabajar con {% data variables.contact.github_support %}' +intro: 'Aprende a abrir un ticket y proporciona al equipo de {% data variables.contact.enterprise_support %} la información que necesitan para resolver tus problemas.' +redirect_from: + - /enterprise/admin/enterprise-support +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Índice + +{% topic_link_in_list /overview %} + {% link_in_list /about-github-enterprise-support %} + {% link_in_list /about-github-premium-support-for-github-enterprise-server %} + {% link_in_list /about-github-premium-support-for-github-enterprise %} + {% link_in_list /about-support-for-advanced-security %} +{% topic_link_in_list /receiving-help-from-github-support %} + {% link_in_list /reaching-github-support %} + {% link_in_list /preparing-to-submit-a-ticket %} + {% link_in_list /submitting-a-ticket %} + {% link_in_list /providing-data-to-github-support %} diff --git a/translations/es-ES/content/admin/enterprise-support/overview.md b/translations/es-ES/content/admin/enterprise-support/overview.md new file mode 100644 index 0000000000000..c7a152e50eaac --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/overview.md @@ -0,0 +1,11 @@ +--- +title: Resumen +intro: 'Conoce las opciones de soporte disponibles para {% data variables.product.product_name %}.' +mapTopic: verdadero +redirect_from: + - /enterprise/admin/enterprise-support/overview +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md new file mode 100644 index 0000000000000..468c459afc07c --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md @@ -0,0 +1,27 @@ +--- +title: Prepararse para enviar un ticket +intro: 'Puedes agilizar tu problema con {% data variables.contact.enterprise_support %} siguiendo estas sugerencias antes de que abras un ticket con ellos.' +redirect_from: + - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Antes de enviar un ticket, deberías: + +- Obtener información que pueda ayudar a que {% data variables.contact.github_support %} rastree, priorice, reproduzca o investigue el problema. +- Reproducir el problema, en caso de que sea posible, y prepararte para compartir los pasos. +- Estar preparado para brindar una descripción completa de la propuesta y los resultados esperados. +- Copiar de manera exacta, palabra por palabra, todos los mensajes del error relacionados con tu problema. +- Determinar si existe un número de ticket en cualquier comunicación con {% data variables.contact.github_support %} que se encuentre en curso. +- Determinar la mejor persona para ponerse en contacto {% data variables.contact.github_support %}. + +### Elegir una persona de contacto + +Especialmente para los tickets con prioridad {% data variables.product.support_ticket_priority_urgent %}, la persona que contacte a {% data variables.contact.github_support %} deberá: + + - Tener conocimiento de tus sistemas internos, herramientas, políticas y prácticas. + - Ser un usuario experto de {% data variables.product.product_name %}. + - Tener acceso y permisos completos a cualquier servicio que se requiera para solucionar los problemas en cuestión. + - Estar autorizado para realizar los cambios recomendados a tu red y a todos los productos aplicables. \ No newline at end of file diff --git a/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md new file mode 100644 index 0000000000000..b9c94d00b32b7 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md @@ -0,0 +1,154 @@ +--- +title: Proporcionar datos al soporte de GitHub +intro: 'Dado que {% data variables.contact.github_support %} no tiene acceso a tu entorno, te solicitaremos información adicional.' +redirect_from: + - /enterprise/admin/guides/installation/troubleshooting/ + - /enterprise/admin/articles/support-bundles/ + - /enterprise/admin/guides/enterprise-support/providing-data-to-github-enterprise-support/ + - /enterprise/admin/enterprise-support/providing-data-to-github-support +versions: + enterprise-server: '*' +--- + +### Crear y compartir archivos de diagnóstico + +Los diagnósticos son una descripción general de los parámetros de una instancia de {% data variables.product.prodname_ghe_server %} y del entorno que contiene: + +- Información de licencia de cliente, incluido el nombre de la empresa, fecha de validez y cantidad de licencias de usuario +- Números de versión y SHAs +- Arquitectura VM +- Nombre de host, modo privado, entorno de SSL +- Cargar y procesar listas +- Parámetros de red +- Método y detalles de autenticación +- Número de repositorios, usuarios y otros datos de instalación + +Puedes descargar el diagnóstico para tu instancia desde la {% data variables.enterprise.management_console %} o al ejecutar la utilidad de la línea de comando `ghe-diagnostics`. + +#### Crear un archivo de diagnóstico desde {% data variables.enterprise.management_console %} + +Puedes usar este método si no tienes tu clave SSH fácilmente disponible. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Haz clic en **Download diagnostics info** (Descargar información de diagnóstico). + +#### Crear un archivo de diagnóstico mediante SSH + +Puedes usar este método sin iniciar sesión en {% data variables.enterprise.management_console %}. + +Usa la utilidad de la línea de comando [ghe-diagnostics](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-diagnostics) para recuperar el diagnóstico para tu instancia. + +```shell +$ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt +``` + +### Crear y compartir paquetes de soporte + +Después de que emites tu solicitud de soporte, podríamos pedirte que compartas un paquete de soporte con nuestro equipo. El paquete de soporte es un archivo tar comprimido en gzip que incluye diagnósticos y registros importantes desde tu instancia, como: + +- Registros relacionados con la autenticación que pueden resultar útiles al solucionar problemas de errores de autenticación, o configurar LDAP, CAS o SAML +- Registro {% data variables.enterprise.management_console %} +- `github-logs/exceptions.log`: Información sobre 500 errores encontrados en el sitio +- `github-logs/audit.log`: registros de auditoría {% data variables.product.prodname_ghe_server %} +- `babeld-logs/babeld.log`: registros proxy Git +- `system-logs/haproxy.log`: registros HAProxy +- `elasticsearch-logs/github-enterprise.log`: registros Elasticsearch +- `configuration-logs/ghe-config.log`: registros de configuración {% data variables.product.prodname_ghe_server %} +- `collectd/logs/collectd.log`: registros Collectd +- `mail-logs/mail.log`: registros de entrega por correo electrónico SMTP +{% if currentVersion ver_lt "enterprise-server@3.0" %} +- `hookshot-logs/exceptions.log`: errores de entrea de Webhook +{% endif %} + +Para obtener más información, consulta "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging) (Registro de auditoría". + +Los paquetes de soporte incluyen registros de los dos últimos días. Para obtener registros de los últimos siete días, puedes descargar un paquete de soporte extendido. Para obtener más información, consulta "[Crear y compartir paquete de soporte extendido](#creating-and-sharing-extended-support-bundles)". + +{% tip %} + +**Sugerencias:** Cuando te comuniques con {% data variables.contact.github_support %}, recibirás un correo electrónico de confirmación con un enlace de referencia del ticket. Si {% data variables.contact.github_support %} te pide que cargues un paquete de soporte, puedes usar el enlace de referencia del ticket para cargar el paquete de soporte. + +{% endtip %} + +#### Crear un paquete de soporte desde la {% data variables.enterprise.management_console %} + +Puedes usar estos pasos para crear y compartir un paquete de soporte si puedes acceder a la {% data variables.enterprise.management_console %} basada en la web y tienes acceso a internet de salida. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Haz clic en **Download support bundle** (Descargar paquete de soporte). +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} + +#### Crear un paquete de soporte mediante SSH + +Puedes utilizar estos pasos para crear y compartir un paquete de soporte si tienes acceso por SSH a {% data variables.product.product_location %} y cuentas con acceso externo a internet. + +{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} + +1. Descargar el paquete de soporte mediante SSH: + ```shell + $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz + ``` + Para obtener más información acerca del comando `ghe-support-bundle`, consulta "[Utilidades de la línea de comandos](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)". +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} + +#### Cargar un paquete de soporte utilizando tu cuenta empresarial + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Debajo de "Ayuda de {% data variables.product.prodname_enterprise %}", da clic en **Cargar un paquete de soporte**. ![Carga un enlace al paquete de soporte](/assets/images/enterprise/support/upload-support-bundle.png) +5. Debajo de "Selecciona una cuenta empresarial", selecciona la cuenta asociada al paquete de soporte del menú desplegable. ![Elige la cuenta empresarial del paquete de soporte](/assets/images/enterprise/support/support-bundle-account.png) +6. Debajo de "Cargar un paquete de soporte para {% data variables.contact.enterprise_support %}", para seleccionar tu paquete de soporte, da clic en **Elegir archivo**, o arrastra tu archivo de paquete de soporte hacia **Escoger archivo**. ![Cargar archivo de paquete de soporte](/assets/images/enterprise/support/choose-support-bundle-file.png) +7. Da clic en **Cargar**. + +#### Cargar paquete de soporte mediante SSH + +Puedes cargar directamente un paquete de soporte a nuestro servidor si: +- Tienes acceso de SSH a {% data variables.product.product_location %}. +- Las conexiones salientes de HTTPS sobre TCP puerto 443 se permiten desde {% data variables.product.product_location %}. + +1. Cargar el paquete a nuestro servidor de paquete de soporte: + ```shell + $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u' + ``` + +### Crear y compartir paquetes de soporte extendido + +Los paquetes de soporte incluyen registros de los últimos dos días, mientras que los paquetes de soporte _extendidos_ incluyen registros de los últimos siete días. Si los eventos que {% data variables.contact.github_support %} está investigando se produjeron hace más de dos días, es posible que te pidamos que compartas un paquete de soporte extendido. Deberás tener acceso a SSH para descargar un paquete extendido, no puedes descargar un paquete extendido desde {% data variables.enterprise.management_console %}. + +Para evitar que los paquetes sean demasiado grandes, solo pueden contener registros que no hayan sido rotados y comprimidos. La rotación de los registros en {% data variables.product.prodname_ghe_server %} se produce en diferentes frecuencias (diarias o semanales) para los diferentes archivos de registro, según el tamaño que pretendamos que tengan los registros. + +#### Crear un paquete de soporte extendido mediante SSH + +Puedes utilizar estos pasos para crear y compartir un paquete de soporte extendido si tienes acceso de SSH a {% data variables.product.product_location %} y si tienes acceso externo a internet. + +1. Descarga el paquete de soporte extendido mediante SSH al agregar el marcador `-x` al comando `ghe-support-bundle`: + ```shell + $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o -x' > support-bundle.tgz + ``` +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} + +#### Cargar un paquete de soporte extendido directamente usando SSH + +Puedes cargar directamente un paquete de soporte a nuestro servidor si: +- Tienes acceso de SSH a {% data variables.product.product_location %}. +- Las conexiones salientes de HTTPS sobre TCP puerto 443 se permiten desde {% data variables.product.product_location %}. + +1. Cargar el paquete a nuestro servidor de paquete de soporte: + ```shell + $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x' + ``` + +### Further reading + +- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" +- "[Acerca de {% 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)". diff --git a/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md new file mode 100644 index 0000000000000..4b3ea8f0795e7 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md @@ -0,0 +1,53 @@ +--- +title: Obtener soporte de GitHub +intro: 'Contacta a {% data variables.contact.enterprise_support %} utilizando la {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} o {% endif %} el portal de soporte.' +redirect_from: + - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ + - /enterprise/admin/enterprise-support/reaching-github-support +versions: + enterprise-server: '*' +--- + +### Usar sistemas de tickets automatizado + +Si bien haremos todo lo mejor por responder a solicitudes de soporte automatizado, habitualmente necesitamos más información que un sistema de tickets automatizado que nos permita resolver tu problema. Siempre que sea posible, inicia las solicitudes de soporte de una persona o una máquina con la que {% data variables.contact.enterprise_support %} pueda interactuar. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". + +### Ponerte en contacto con {% data variables.contact.enterprise_support %} + +Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte utilizando la {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} o el {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} el {% data variables.contact.contact_ae_portal %}{% endif %}. Marca la prioridad del ticket como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". + +### Ponerte en contacto con {% data variables.contact.enterprise_support %} + +{% if enterpriseServerVersions contains currentVersion %} +#### Ver tickets de soporte anteriores + +Puedes usar el {% data variables.contact.enterprise_portal %} para ver tickets de soporte anteriores. + +1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. +2. Da clic en **Mist tickets**. ![Ver los tickets emitidos anteriormente](/assets/images/enterprise/support/view-past-tickets.png) + +### Comunicarse con {% data variables.contact.premium_support %} + +Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte mediante {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o {% data variables.contact.contact_enterprise_portal %}. Marca su prioridad como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". + +{% endif %} +### Contacting sales + +Para las preguntas relacionadas con precios, licenciamiento, renovaciones, cotizaciones, pagos y otras relacionadas, contacta a {% data variables.contact.contact_enterprise_sales %} o llama al [+1 (877) 448-4820](tel:+1-877-448-4820). + +{% if enterpriseServerVersions contains currentVersion %} +### Contacting training + +Para conocer más sobre las opciones de capacitación, incluida la capacitación personalizada, consulta el sitio de capacitación de [{% data variables.product.company_short %}](https://services.github.com/). + +{% note %} + +**Nota:** La capacitación está incluida en el {% data variables.product.premium_plus_support_plan %}. Para obtener más información, consulta "[Acerca de{% 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)". + +{% endnote %} +{% endif %} + +### Further reading + +- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" +- "[Acerca de {% 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)". diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md new file mode 100644 index 0000000000000..3d25b2563c97f --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md @@ -0,0 +1,12 @@ +--- +title: Recibir ayuda desde Soporte de GitHub +intro: 'Puedes contactar a {% data variables.contact.enterprise_support %} para reportar varios problemas de tu empresa.' +redirect_from: + - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ + - /enterprise/admin/enterprise-support/receiving-help-from-github-support +mapTopic: verdadero +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md new file mode 100644 index 0000000000000..2b790cd0af6c4 --- /dev/null +++ b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md @@ -0,0 +1,63 @@ +--- +title: Envío de ticket +intro: 'Puedes emitir un ticket de soporte utilizando la {% if enterpriseServerVersions contains currentVersion %}{% data variables.enterprise.management_console %} de {% data variables.product.prodname_ghe_server %} o {% endif %} el portal de soporte.' +redirect_from: + - /enterprise/admin/enterprise-support/submitting-a-ticket +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca del envío de tickets + +Antes de enviar un ticket, deberías recopilar información útil para {% data variables.contact.github_support %} y elegir una persona de contacto. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". + +{% if enterpriseServerVersions contains currentVersion %} +Después de emitir tu solicitud de soporte y la información de diagnóstico opcional, +{% data variables.contact.github_support %} podría pedirte que descargues y compartas un paquete de soporte con nosotros. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)". + +### Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} + +1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. +5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) +{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} +{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} + +### Emitir un ticket utilizando tu cuenta empresarial + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Debajo de "Ayuda de {% data variables.product.prodname_enterprise %}", da clic en **Portal de {% data variables.contact.enterprise_support %}**. ![Enlace para navegar al sitio de soporte empresarial](/assets/images/enterprise/support/enterprise-support-link.png) +5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) +{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} +{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} + +### Enviar un ticket mediante el {% data variables.product.product_name %} {% data variables.enterprise.management_console %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Si deseas incluir los diagnósticos con tu ticket de soporte, en "Diagnostics" (Diagnóstico), haz clic en **Download diagnostic info** (Descargar información de diagnóstico) y guarda el archivo localmente. Adjuntarás este archivo a tu ticket de soporte posteriormente. ![Botón para descargar información de diagnóstico](/assets/images/enterprise/support/download-diagnostics-info-button.png) +6. En "Open Support Request" (Abrir solicitud de soporte", haz clic en **New support request** (Nueva solicitud de soporte). ![Botón para abrir una solicitud de soporte](/assets/images/enterprise/management-console/open-support-request.png) +5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) +{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} +14. Para incluir los diagnósticos con tu ticket de soporte, haz clic en **Add file** (Agregar archivo), luego adjunta el archivo de diagnóstico que descargaste. ![Añadir botón de archivo](/assets/images/enterprise/support/support-ticket-add-file.png) +{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} +7. Haz clic en **Submit** (enviar). + +{% endif %} +{% if currentVersion == "github-ae@latest" %} +### Enviar un ticket mediante el {% data variables.contact.ae_azure_portal %} + +Los clientes comerciales pueden emitir una solicitud de soporte en el {% data variables.contact.contact_ae_portal %}. Los clientes de gobierno deben utilizar el [portal de Azure para clientes de gobierno](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade). Para obtener más información, consulta la sección [Crear una solicitud de soporte de Azure](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) enla documentación de Microsoft. + +Para problemas urgentes, para asegurar una respuesta rápida, después de emitir un ticket, por favor llama a la línea directa de soporte inmediatamente. Tu Administrador de Cuenta de Soporte Técnico (TSAM) te proporcionará el número que debes utilizar en tu sesión de incorporación. + +{% endif %} + +### Further reading + +- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} +- "[Acerca de {% 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/es-ES/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..cb6af070d12af --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: Acerca de utilizar las acciones en GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} incluye la mayoría de las acciones de autoría de {% data variables.product.prodname_dotcom %}, y tiene opciones para habilitar el acceso a otras acciones de {% data variables.product.prodname_dotcom_the_website %} y de {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Los flujos de trabajo de {% data variables.product.prodname_actions %} pueden utilizar _acciones_, las cuales son tareas individuales que puedes combinar para crear jobs y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}. + +{% data reusables.actions.enterprise-no-internet-actions %} + +### Las acciones oficiales en conjunto con {% data variables.product.prodname_ghe_server %} + +La mayoría de las acciones oficiales de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.prodname_ghe_server %} y se capturan en un punto en el tiempo desde {% data variables.product.prodname_marketplace %}. Cuando tu instancia de {% data variables.product.prodname_ghe_server %} se actualiza, las acciones oficiales conjuntas también lo hacen. + +Las acciones agrupadas oficiales incluyen a `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, y varias acciones de `actions/setup-`, entre otras. Para ver todas las acciones oficiales que se incluyen en tu instancia empresarial, navega hasta la organización `actions` en tu instancia: https://HOSTNAME/actions. + +Cada acción es un repositorio en la organización `actions` y cada repositorio de acción incluye las etiquetas, ramas y SHA de confirmación necesarios que tu flujo de trabajo puede utilizar para referenciar la acción. + +{% note %} + +**Nota:** Cuando utilices acciones de configuración (tales como `actions/setup-LANGUAGE`) en {% data variables.product.prodname_ghe_server %} con ejecutores auto-hospedados, podrías necesitar configurar el caché de las herramientas en los ejecutores que no tengan acceso a internet. Para obtener más información, consulta la sección "[ Configurar el caché de herramientas en ejecutores auto-hospedados sin acceso a internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". + +{% endnote %} + +### Configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %} + +Si los usuarios en tu instancia empresarial necesitan acceso a otras acciones de {% data variables.product.prodname_dotcom_the_website %} o de {% data variables.product.prodname_marketplace %}, hay algunas opciones de configuración que puedes utilizar. + +El acercamiento recomendado es habilitar el acceso automático a todas las acciones desde {% data variables.product.prodname_dotcom_the_website %}. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} + +Como alternativa, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes descargar y sincronizar las acciones manualmente en tu instancia empresarial utilizando la herramienta `actions-sync`. Para obtener más información, consulta la sección "[Sincronizar acciones manualmente desde {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". diff --git a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..9a4a080bfea9f --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Configuración avanzada y solución de problemas +intro: 'Configura la disponibilidad alta para {% data variables.product.prodname_actions %} y soluciona los problemas de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' +mapTopic: verdadero +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..753150973623c --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Respaldar y restablecer GitHub Enterprise Server con GitHub Actions habilitadas +shortTitle: Respaldar y restablecer +intro: 'Los datos de {% data variables.product.prodname_actions %} en tu proveedor de almacenamiento externo no se incluyen en los respaldos normales de {% data variables.product.prodname_ghe_server %} y deben respaldarse por separado.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +Si utilizas {% data variables.product.prodname_enterprise_backup_utilities %} para respaldar {% data variables.product.product_location %}, es importante que tomes en cuenta que los datos de las {% data variables.product.prodname_actions %} que se almacenan en tu proveedor de almacenamiento externo no se incluyen en el respaldo. + +Esta es una vista general de los pasos que se requieren para restablecer {% data variables.product.product_location %} con {% data variables.product.prodname_actions %} para un aplicativo nuevo: + +1. Confirmar que el aplicativo original esté fuera de línea. +1. Configurar manualmente los ajustes de red en el aplicativo de reemplazo de {% data variables.product.prodname_ghe_server %}. La configuración de red se excluye de la captura del respaldo y no los sobrescribe el `ghe-restore`. +1. Configura el aplicativo de reemplazo para utilizar la misma configuración de almacenamiento externo de {% data variables.product.prodname_actions %} que el aplicativo original. +1. Habilita {% data variables.product.prodname_actions %} en el aplicativo de reemplazo. Esto conectará el aplicativo de reemplazo al mismo almacenamiento externo de {% data variables.product.prodname_actions %}. +1. Después de que se configure {% data variables.product.prodname_actions %} con el proveedor de almacenamiento externo, utiliza el comando `ghe-restore` para restablecer el resto de los datos del respaldo. Para obtener más información, consulta la sección "[Restablecer un respaldo](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)". +1. Vuelve a registrar tus ejecutores auto-hospedados en el aplicativo de reemplazo. Para obtener más información, consulta la sección de [Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +Para obtener más información sobre respaldar y restablecer {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar los respaldos en tu aplicativo](/admin/configuration/configuring-backups-on-your-appliance)". diff --git a/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md new file mode 100644 index 0000000000000..2a22a33d6276e --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -0,0 +1,26 @@ +--- +title: Habilitar el acceso automático a las acciones de GitHub.com utilizando GitHub Connect +intro: 'Para permitir que {% data variables.product.prodname_actions %} utilice acciones de {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, puedes conectar a{% data variables.product.product_location_enterprise %} con {% data variables.product.prodname_ghe_cloud %}.' +permissions: 'Los administradores de sitio para {% data variables.product.prodname_ghe_server %} que sean también propietarios de la cuenta organizacional o empresarial de {% data variables.product.prodname_ghe_cloud %} conectada pueden habilitar el acceso a todas las acciones de {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Predeterminadamente, los flujos de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} no pueden utilizar las acciones directamente desde {% data variables.product.prodname_dotcom_the_website %} o desde [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). + +Para que todas las acciones de {% data variables.product.prodname_dotcom_the_website %} se hagan disponibles para tu instancia empresarial, puedes utilizar {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_ghe_cloud %}. Para encontrar otras formas de acceder a las acciones desde {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Acerca de utilizar las acciones en {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)". + +### Habilitar el acceso automático a todas las acciones de {% data variables.product.prodname_dotcom_the_website %} + +Antes de habilitar el acceso a todas las acciones de {% data variables.product.prodname_dotcom_the_website %} en {% data variables.product.product_location_enterprise %}, debes conectar a {% data variables.product.product_location_enterprise %} con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Debajo de "El servidor puede utilizar acciones de GitHub.com en las ejecuciones de flujo de trabajo", utiliza el menú desplegable y selecciona **Habilitado**. ![Menú desplegable a las acciones de GitHub.com en las ejecuciones de flujo de trabajo](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..217962daac02f --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Habilitar GitHub Actions para GitHub Enterprise Server +intro: 'Aprende cómo configurar el almacenamiento y habilita las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' +mapTopic: verdadero +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..dcca86b930f7e --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Habilitar las GitHub Actions con el almacenamiento de Amazon S3 +intro: 'Puedes habilitar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de Amazon S3 para almacenar artefactos qeu generan las ejecuciones de flujos de trabajo.' +permissions: 'Los administradoresde sitio pueden habilitar {% data variables.product.prodname_actions %} y configurar los ajustes empresariales.' +versions: + enterprise-server: '>=3.0' +--- + +### Prerrequisitos + +{% data reusables.actions.enterprise-s3-support-warning %} + +Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos: + +* Crea tu bucket de Amazon S3 para almacenar artefactos que generan las ejecuciones de flujo de trabajo. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar {% data variables.product.prodname_actions %} con almacenamiento de Amazon S3 + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Debajo de "Almacenamiento de artefactos & bitácoras", selecciona **Amazon S3**, e ingresa los detalles de tu bucket de almacenamiento: + + * **URL de servicio de AWS**: La URL de servicio de tu bucket. Por ejemplo, si tu bucket de S3 se creó en la región `us-west-2`, este valor deberá ser `https://s3.us-west-2.amazonaws.com`. + + Para obtener más información, consulta la sección "[terminales de servicio de AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" en la documentación de AWS. + * **AWS S3 Bucket**: El nombre de tu bucket de S3. + * **Clave de acceso de AWS S3** y **Clave secreta de AWS S3**: La ID de clave de acceso y clave secreta para tu bucket. Para obtener más información sobre cómo administrar las claves de acceso de AWS, consulta la "[Documentación para la Administración de Accesos e Identidad de AWS](https://docs.aws.amazon.com/iam/index.html)". + + ![Botón radial para seleccionar el almacenamiento de Amazon S3 y los campos para la configuración de S3](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..4a0ace946f8c9 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Habilitar las GitHub Actions con el almacenamiento de Azure Blob +intro: 'Puedes habilitar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de Azure Blob para almacenar los artefactos que generen las ejecuciones de flujo de trabjo.' +permissions: 'Los administradoresde sitio pueden habilitar {% data variables.product.prodname_actions %} y configurar los ajustes empresariales.' +versions: + enterprise-server: '>=3.0' +--- + +### Prerrequisitos + +Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos: + +* Crea tu cuenta de almacenamiento para almacenar artefactos del flujo de trabajo. {% data variables.product.prodname_actions %} almacena sus datos como blobs de bloque y son compatibles dos tipos de cuenta de almacenamiento: + * Una cuenta de almacenamiento para ** propósitos generales** (también conocida como `general-purpose v1` o `general-purpose v2`) que utiliza el nivel de rendimiento **estándar**. + + {% warning %} + + **Advertencia:** No se puede utilizar el nivel de rendimiento **premium** con una cuenta de almacenamiento de propósitos generales. El nivel de rendimiento **estándar** debe seleccionarse cuando se crea la cuenta de almacenamiento y no puede cambiarse después. + + {% endwarning %} + * Una cuenta de almacenamiento de **BlockBlobStorage** que utiliza el nivel de rendimiento **premium**. + + Para obtener más información sobre los tipos de cuenta de almacenamiento de Azure y de los niveles de rendimiento, consulta la [Documentación de Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar las {% data variables.product.prodname_actions %} con el almacenamiento de Blobs de Azure + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Debajo de "Almacenamiento de artefactos & bitácoras", selecciona **Azure Blob Storage**, e ingresa tu secuencia de conexión de cuenta para el almacenamiento de Azure. Para obtener más información sobre cómo obtener la secuencia de conexión para tu cuenta de almacenamiento, consulta la [Documentación de Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Botón radial para seleccionar Azure Blob Storage y el campo de secuencia de conexión](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..138e89bf3c570 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS +intro: 'Puedes habilitar a las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar la puerta de enlace de MinIO para el almacenamiento en NAS para almacenar artefactos que generan las ejecuciones del flujo de trabajo.' +permissions: 'Los administradoresde sitio pueden habilitar {% data variables.product.prodname_actions %} y configurar los ajustes empresariales.' +versions: + enterprise-server: '>=3.0' +--- + +### Prerrequisitos + +{% data reusables.actions.enterprise-s3-support-warning %} + +Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos: + +* Para evitar la contención de recursos en el aplicativo, te recomendamos que hospedes a MinIO separado de {% data variables.product.product_location %}. +* Crea tu bucket para almacenar los artefactos del flujo de trabajo. Para configurar tu bucket y clave de acceso, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar las {% data variables.product.prodname_actions %} con la puerta de enlace de MinIO para almacenamiento en NAS + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Debajo de "Almacenamiento de artefactos & bitácoras", selecciona **Amazon S3**, e ingresa los detalles de tu bucket de almacenamiento: + + * **URL de servicio de AWS**: La URL para tu servicio de MinIO. Por ejemplo, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: El nombre de tu bucket de S3. + * **Clave de AWS S3 Access** y **Clave de AWS S3 Secret**: La `MINIO_ACCESS_KEY` y `MINIO_SECRET_KEY` que se utiliza para tu instancia de MinIO. Para obtener más información, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Botón radial para seleccionar el almacenamiento de Amazon S3 y los campos para la configuración de MinIO](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Debajo de "Almacenamiento de artefactos & bitácoras", selecciona **Forzar el estilo de la ruta**. ![Casilla de verificación para forzar el estilo de ruta](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000000..fa51460943663 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,34 @@ +--- +title: Requerir las políticas de GitHub Actions para tu empresa +intro: 'Los administradores empresariales pueden gestionar el acceso a {% data variables.product.prodname_actions %} en una empresa.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} + +### Acerca de los permisos de {% data variables.product.prodname_actions %} para tu empresa + +Cuando habilitas {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, estas se habilitan para todas las organizaciones en tu empresa. Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para todas las organizaciones en tu empresa, o puedes permitir solo organizaciones específicas. También puedes limitar el uso de acciones públicas para que las personas solo puedan utilizar las acciones locales que existen en tu empresa. + +### Administrar los permisos de {% data variables.product.prodname_actions %} para tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configurar la política de bifurcación privada para tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..b20460185266a --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Iniciar con GitHub Actions para GitHub Enterprise Server +intro: 'Aprende cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} por primera vez.' +permissions: 'Los administradoresde sitio pueden habilitar {% data variables.product.prodname_actions %} y configurar los ajustes empresariales.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Nota:** El soporte para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 es un beta público limitado. Revisa los requisitos de almacenamiento externo mencionados a continuación y [regístrate para el beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}. Esto cubre los requisitos de hardware y software, presenta las opciones de almacenamiento y describe las políticas de administración de seguridad. + +### Revisar las consideraciones de hardware + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### Requisitos de almacenamiento externo + +Para habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, debes tener acceso al almacenamiento externo de blobs. + +{% data variables.product.prodname_actions %} utiliza el almacenamiento de blobs para almacenar artefactos que se generan con las ejecuciones de flujo de trabajo, tales como las bitácoras de flujo de trabajo y los artefactos de compilaciones que sube el usuario. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo. + +{% data variables.product.prodname_actions %} es compatible con estos proveedores de almacenamiento: + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway para NAS + +{% note %} + +**Nota:** Estos son los únicos proveedores de almacenamiento compatibles con {% data variables.product.company_short %} y sobre los que éste puede proporcionar asistencia. Es muy poco probable que otros proveedores de almacenamiento de S3 compatibles con la API funcionen, debido a las diferencias de la API de S3. [Contáctanos](https://support.github.com/contact) para solicitar soporte para proveedores de almacenamiento adicionales. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Permisos para Amazon S3 + +{% data reusables.actions.enterprise-s3-permission %} + +### Habilitar {% data variables.product.prodname_actions %} + +El soporte de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 se ecuentra en un beta público limitado. [Regístrate para el beta](https://resources.github.com/beta-signup/). + +### Leer más + +- "Consideraciones de hardware" para tu plataforma en "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Habilitar las {% data variables.product.prodname_actions %} con tu proveedor de almacenamiento + +Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección: + +* [Habilitar las GitHub Actions con Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa + +Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". + +### Agregar ejecutores autoalojados + +{% data reusables.actions.enterprise-github-hosted-runners %} + +Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". + +### Administrar qué acciones pueden utilizarse en tu empresa + +Puedes controlar las acciones que pueden utilizar tus usuarios en tu empresa. Esto incluye el configurar {% data variables.product.prodname_github_connect %} para el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %}, o sincronizar las acciones de {% data variables.product.prodname_dotcom_the_website %} manualmente. + +Para obtener más información, consulta la sección "[Acerca de las acciones en {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)". + +### Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %} + +Si quieres aprender más acerca de las prácticas de seguridad para {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". + +{% endif %} diff --git a/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md b/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..dd00e8e1a52b7 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: Disponibilidad alta para las GitHub Actions +intro: 'Existen algunas especificaciones especiales para administrar las {% data variables.product.prodname_actions %} en una configuración de disponibilidad alta.' +versions: + enterprise-server: '>=3.0' +--- + +### Replicación o redundancia de tus datos de {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-storage-ha-backups %} + +Te recomendamos fuertemente que configures el almacenamiento externo de tus {% data variables.product.prodname_actions %} para que utilicen redundancia o replicación. Para obtener más información, refiérete a la documentación de tu proveedor de alamacenamiento: + +* [Documentación sobre la redundancia del almacenamiento de Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Documentación sobre la replicación de Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### Réplicas de disponibilidad alta + +#### Promover una réplica + +Cuando habilitas la configuración de disponibilidad alta, cualquier réplica se configura automáticamente para utilizar la configuración de almacenamiento externo de {% data variables.product.prodname_actions %}. Si necesitas iniciar una recuperación de fallos para promover una réplica, no se requiere ningún cambio adicional en la configuración para las {% data variables.product.prodname_actions %}. + +Para obtener más información, consulta la sección "[Iniciar una respuesta ante los fallos para aplicativo de réplica](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)". + +#### Quitar una réplica de disponibilidad alta + +Evita dejar que varias instancias escriban en el mismo almacenamiento externo de {% data variables.product.prodname_actions %}. Esto podría ocurrir cuando utilizas el comando `ghe-repl-teardown` para parar y eliminar permanentemente una réplica habilitada para {% data variables.product.prodname_actions %}. Esto se da porque la réplica se convertirá a una versión autónoma de {% data variables.product.prodname_ghe_server %} y, despues de su destrucción, seguirá utilizando el mismo almacenamiento externo. + +Para ayudarte a evitar este problema, te recomendamos ya sea que decomisiones el servidor de la réplica o actualices su configuración de {% data variables.product.prodname_actions %} con un almacenamiento externo diferente. diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md new file mode 100644 index 0000000000000..22b4cb1ae670a --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/index.md @@ -0,0 +1,33 @@ +--- +title: Administrar GitHub Actions para tu empresa +intro: 'Habilita {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y administra las políticas y configuraciones de{% data variables.product.prodname_actions %}.' +redirect_from: + - /enterprise/admin/github-actions +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Índice + +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + +{% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} + +{% topic_link_in_list /managing-access-to-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} + {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md new file mode 100644 index 0000000000000..1d4955b5aff1a --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md @@ -0,0 +1,10 @@ +--- +title: Administrar el acceso a las acciones desde GitHub.com +intro: 'En tu empresa, puedes controlar qué acciones de {% data variables.product.prodname_dotcom_the_website %} y de {% data variables.product.prodname_marketplace %} se pueden utilizar.' +mapTopic: verdadero +redirect_from: + - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md new file mode 100644 index 0000000000000..80e9f3c337302 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -0,0 +1,70 @@ +--- +title: Sincronizar manualmente las acciones de GitHub.com +intro: 'Para los usuarios que necesiten acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar las acciones específicas a tu instancia de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.actions.enterprise-no-internet-actions %} + +El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacerlo utilizando {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes seguir esta guía para utilizar la herramienta de código abierto [`actions-sync`](https://github.com/actions/actions-sync) de {% data variables.product.company_short %} para sincronizar los repositorios de acción individual desde {% data variables.product.prodname_dotcom_the_website %} hacia tu instancia empresarial. + +### Acerca de la herramienta `actions-sync` + +La herramienta `actions-sync` debe ejecutarse en una máquina que pueda acceder a la API de {% data variables.product.prodname_dotcom_the_website %} y a la API de tu instancia de {% data variables.product.prodname_ghe_server %}. La máquina no necesita estar conectada a ambas al mismo tiempo. + +Si tu máquina tiene acceso a ambos sistemas al mismo tiempo, puedes hacer la sincronización con un simple comando de `actions-sync sync`. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. + +La herramienta `actions-sync` solo puede descargar acciones de {% data variables.product.prodname_dotcom_the_website %} que estén almacenadas en repositorios públicos. + +### Prerrequisitos + +* Antes de utilizar la herramienta `actions-sync`, debes asegurarte de que todas las organizaciones de destino ya existan en tu instancia empresarial. El siguiente ejemplo demuestra cómo sincronizar acciones a una organización que se llama `synced-actions` en una instancia empresarial. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". +* Debes crear un token de acceso personal (PAT) en tu instancia empresarial que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +### Ejemplo: Utilizar la herramienta `actions-sync` + +Este ejemplo demuestra el uso de la herramienta `actions-sync` para sincronizar una acción individual de {% data variables.product.prodname_dotcom_the_website %} con una instancia empresarial. + +{% note %} + +**Nota:** Este ejemplo utiliza el comando `actions-sync sync`, el cual requiere tener acceso concurrente tanto a la API de {% data variables.product.prodname_dotcom_the_website %} como a la API de tu instancia de {% data variables.product.prodname_ghe_server %} desde tu máquina. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances). + +{% endnote %} + +1. Descarga y extrae el [lanzamiento más reciente de `actions-sync`](https://github.com/actions/actions-sync/releases) para el sistema operativo de tu máquina. +1. Crea un directorio para almacenar los archivos de caché para la herramienta. +1. Ejecuta el comando `actions-sync sync`: + + ```shell + ./actions-sync sync \ + --cache-dir "cache" \ + --destination-token "aabbccddeeffgg" \ + --destination-url "https://my-ghes-instance" \ + --repo-name "docker/build-push-action:synced-actions/docker-build-push-action" + ``` + + El comando anterior utiliza los siguientes argumentos: + + * `--cache-dir`: El directorio del caché en la máquina que ejecuta el comando. + * `--destination-token`: Un token de acceso personal para la instancia empresarial de destino. + * `--destination-url`: La URL de la instancia empresarial de destino. + * `--repo-name`: El repositorio de acción a sincronizar. Esto adopta el formato de `owner/repository:destination_owner/destination_repository`. + + * El ejemplo anterior sincroniza el repositorio [`docker/build-push-action`](https://github.com/docker/build-push-action) con el repositorio `synced-actions/docker-build-push-action` en la instancia de {% data variables.product.prodname_ghe_server %} de destino. Debes crear la organización llamada `synced-actions` en tu instancia empresarial antes de ejecutar el comando anterior. + * Si omites el `:destination_owner/destination_repository`, la herramienta utilizará el nombre de propietario y de repositorio originales para tu instancia empresarial. Antes de ejecutar el comando, debes crear una organización nueva en tu instancia, la cual empate con el nombre de propietario de la acción. Considera utilizar una organización central para almacenar las acciones sincronizadas en tu instancia, ya que esto significa que no necesitarás crear varias organizaciones nuevas si sincronizas las acciones de propietarios diferentes. + * Puedes sincronizar varias acciones si reemplazas el parámetro `--repo-name` con `--repo-name-list` o con `--repo-name-list-file`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#actions-sync). +1. Después de que se haya creado el repositorio de acción en tu instancia empresarial, las personas en tu empresa pueden utilizar el repositorio de destino para referenciar la acción en sus flujos de trabajo. Para la acción de ejemplo que se muestra a continuación: + + ``` + uses: synced-actions/docker-build-push-action@v1 + ``` + + Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)". diff --git a/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md new file mode 100644 index 0000000000000..280afb38e07f0 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -0,0 +1,90 @@ +--- +title: Configurar el caché de la herramienta en ejecutores auto-hospedados sin acceso a internet +intro: 'Para utilizar las acciones de `actions/setup` que se incluyen en los ejecutores auto-hospedados sin acceso a internet, primero debes poblar el caché de la herramienta del ejecutor para tus flujos de trabajo.' +redirect_from: + - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de las acciones de configuración incluídas y el caché de la herramienta del ejecutor + +{% data reusables.actions.enterprise-no-internet-actions %} + +La mayoría de las acciones de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.prodname_ghe_server %}. Sin embargo, los ejecutores auto-hospedados sin acceso a internet requerirán que se les configure un poco antes de que puedan utilizar las acciones de `actions/setup-LANGUAGE` incluídas, tal como `setup-node`. + +Las acciones de `actions/setup-LANGUAGE` habitualmente necesitan acceso a internet para descargar los binarios de ambiente requeridos en el caché de la herramienta del ejecutor. Los ejecutores auto-hospedados sin acceso a internet no pueden descargar los binarios, así que debes poblar el caché de la herramienta manualmente en el ejecutor. + +Puedes poblar el caché de la herramienta del ejecutor si ejecutas un flujo de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_dotcom_the_website %} que cargue un caché de la herramienta del ejecutor hospedada en {% data variables.product.prodname_dotcom %}, la cual puedes transferir y extraer posteriormente en tu ejecutor auto-hospedado sin acceso a internet. + +{% note %} + +**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-18.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 18.04 de 64 bits. Para obtener más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "Ambientes virtuales para los ejecutores hospedados en GitHub". + +{% endnote %} + +### Prerrequisitos + +* Determina qué ambientes de desarrollo necesitarán tus ejecutores auto-hospedados. El siguiente ejemplo demuestra cómo poblar el caché de la herramienta para la acción `setup-node`, utilizando las versiones 10 y 12 de Node.js. +* Accede a un repositorio en {% data variables.product.prodname_dotcom_the_website %} que puedas utilizar para ejecutar un flujo de trabajo. +* Accede al sistema de archivos de tu ejecutor auto-hospedado para poblar la carpeta del caché de la herramienta. + +### Poblar el caché de la herramienta para un ejecutor auto-hospedado + +1. En {% data variables.product.prodname_dotcom_the_website %}, navega a un repositorio que puedas utilizar para ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}. +1. Crea un archivo de flujo de trabajo nuevo en la carpeta `.github/workflows` del repositorio, el cual cargue un artefacto que contenga el caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %}. + + El siguiente ejemplo muestra un flujo de trabajo que carga el caché de la herramienta para un ambiente de Ubuntu 18.04 utilizando la acción `setup-node` con las versiones 10 y 12 de Node.js. + + {% raw %} + ```yaml + name: Upload Node.js 10 and 12 tool cache + on: push + jobs: + upload_tool_cache: + runs-on: ubuntu-18.04 + steps: + - name: Clear any existing tool cache + run: | + mv "${{ runner.tool_cache }}" "${{ runner.tool_cache }}.old" + mkdir -p "${{ runner.tool_cache }}" + - name: Setup Node 10 + uses: actions/setup-node@v1 + with: + node-version: 10.x + - name: Setup Node 12 + uses: actions/setup-node@v1 + with: + node-version: 12.x + - name: Archive tool cache + run: | + cd "${{ runner.tool_cache }}" + tar -czf tool_cache.tar.gz * + - name: Upload tool cache artifact + uses: actions/upload-artifact@v2 + with: + path: ${{runner.tool_cache}}/tool_cache.tar.gz + ``` + {% endraw %} +1. Descarga el artefacto del caché de la herramienta desde la ejecución del flujo de trabajo. Para obtener instrucciones sobre còmo descargar artefactos, consulta la secciòn "[Descargar artefactos de los flujos de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +1. Transfiere el artefacto del caché de la herramienta a tu ejecutor auto-hospedado y extráelo al directorio local del caché de la herramienta. El directorio predeterminado del caché de la herramienta es `RUNNER_DIR/_work/_tool`. Si el ejecutor no ha procesado ningún job aún, podrías necesitar crear los directorios `_work/_tool`. + + Después de extraer el artefacto del caché de la herramienta que se cargó en el ejemplo anterior, deberás tener una estructura de directorio en tu ejecutor auto-hospedado que sea similar al siguiente ejemplo: + + ``` + RUNNER_DIR + ├── ... + └── _work + ├── ... + └── _tool + └── node + ├── 10.22.0 + │   └── ... + └── 12.18.3 + └── ... + ``` + +Tu ejecutor auto-hospedado sin acceso a internet debería ahora poder utilizar la acción `setup-node`. Si experimentas algún problema, asegúrate de que hayas poblado el caché de la herramienta correcta para tus flujos de trabajo. Por ejemplo, si necesitas utilizar la acción `setup-python`, necesitarás poblar el caché de la herramienta con el ambiente de Python que quieras utilizar. diff --git a/translations/es-ES/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..c47de63b4194c --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Solucionar problemas en las GitHub Actions de tu empresa +intro: 'Solucionar problemas comunes que ocurren cuando se utilizan {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' +permissions: 'Los administradores de sitio pueden solucionar problemas de {% data variables.product.prodname_actions %} y modificar las configuraciones de {% data variables.product.prodname_ghe_server %}.' +versions: + enterprise-server: '>=3.0' +--- + +### Configurar los ejecutores auto-hospedados cuando utilizas un certificado auto-firmado para {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} Para obtener más información, consulta la sección "[Configurar TLS](/admin/configuration/configuring-tls)". + +#### Instalar el certificado en la máquina ejecutora + +Para que un ejecutor auto-hospedado se conecte a {% data variables.product.prodname_ghe_server %} utilizando un certificado auto-firmado, debes instalarlo en la máquina ejecutora para que la seguridad de la conexión se fortalezca. + +Para encontrar los pasos necesarios para instalar un certificado, refiérete a la documentación del sistema operativo de tu ejecutor. + +#### Configurar Node.JS para utilizar el certificado + +La mayoría de las acciones se escriben en JavaScript y se ejecutan utilizando Node.js, lo cual no utiliza el almacenamiento del certificado del sistema operativo. Para que la aplicación ejecutora auto-hospedada utilice el certificado, debes configurar la variable de ambiente `NODE_EXTRA_CA_CERTS` en la máquina ejecutora. + +Puedes configurar la variable de ambiente como una variable de ambiente de sistema, o declararla en un archivo que se llame _.env_ en el directorio de aplicaciones del ejecutor auto-hospedado. + +Por ejemplo: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Las variables de ambiente se leen cuando la aplicación ejecutora auto-hospedada inicia, así que debes configurar la variable de ambiente antes de configurar o iniciar la aplicación ejecutora auto-hospedada. Si cambia la configuración de tu certificado, debes reiniciar la aplicación ejecutora auto-hospedada. + +#### Configurar los contenedores de Docker para que utilicen el certificado + +Si utilizas las acciones de contenedor de Docker o los contenedores de servicio en tus flujos de trabajo, puede que también necesites instalar el certificado en tu imagen de Docker adicionalmente a configurar la variable de ambiente anterior. + +### Configurar los ajustes de proxy HTTP para {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +Si estos ajustes no se configuran adecuadamente, podrías recibir errores tales como `Resource unexpectedly moved to https://` cuando ajustes o cambies tu configuración de {% data variables.product.prodname_actions %}. + +### Los ejecutores no se conectan a {% data variables.product.prodname_ghe_server %} después de cambiar el nombre de host + +Si cambias el nombre de host de {% data variables.product.product_location %}, los ejecutores auto-hospedados no podrán conectarse al nombre de host antiguo y no podrán ejecutar ningún job. + +Necesitarás actualizar la configuración de tus ejecutores auto-hospedados para utilizar el nuevo nombre de host para {% data variables.product.product_location %}. Cada ejecutor auto-hospedado necesitará alguno de los siguientes procedimientos: + +* En el directorio de la aplicación ejecutora auto-hospedada, edita los archivos `.runner` y `.credentials` para reemplazar todas las menciones del nombre de host antiguo con el nuevo, posteriormente, reinicia la aplicación ejecutora auto-hospedada. +* Elimina al ejecutor de {% data variables.product.prodname_ghe_server %} utilizando la IU, y vuelve a agregarlo. Para obtener más información, consulta "[Eliminar ejecutores autoalojados](/actions/hosting-your-own-runners/removing-self-hosted-runners) y [Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Jobs atorados y límites de CPU y de memoria de las {% data variables.product.prodname_actions %} + +{% data variables.product.prodname_actions %} se compone de varios servicios que se ejecutan en {% data variables.product.product_location %}. Predeterminadamente, estos servicios se configuran con límites predeterminados de CPU y de memoria que deberían funcionar con la mayoría de las instancias. Sin embargo, los usuarios asiduos de {% data variables.product.prodname_actions %} podrían encesitar ajustar esta configuración. + +Puede que estés llegando a los límites de CPU o de memoria si notas que los jobs no están iniciando (aún si hay ejecutores inactivos), o si el progreso del job no se actualiza o cambia en la IU. + +#### 1. Verifica el uso total de memoria y CPU en la consola de administración + +Accede a la consola de administración y utiliza el tablero de monitoreo para inspeccionar las gráficas del total de memoria y de CPU debajo de "Salud del Sistema". Para obtener más información, consulta la sección "[Acceder al tablero de monitoreo](/admin/enterprise-management/accessing-the-monitor-dashboard)". + +Si la "Salud del sistema" para el uso total de CPU es cercano a 100%, o si ya no hay memoria disponible restante, entonces {% data variables.product.product_location %} se está ejecutando al total de su capacidad y necesita escalarse. Para obtener más información, consulta "[Aumentar los recursos de memoria o la CPU](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Verifica el uso de CPU y memoria de los jobs nómadas en la consola de administración + +Si la "Salud del sistema" para el uso total de CPU y memoria están bien, desplázate a la parte inferior de la página, hacia la sección de "Jobs nómadas", y revisa las g´raficas de "Valor porcentual de CPU" y de "Uso de memoria". + +Cada sección en estas gráficas corresponde a un servicio. Para los servicios de {% data variables.product.prodname_actions %}, busca: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +Si cualquiera de estos servicios estan cerca de o en 100% de uso de CPU, o si la memoria está cerca de su límite (2 GB, predeterminadamente), entonces el recurso de asignación para estos servicios podría necesitar un aumento. Toma nota de cuáles de los servicios antes descritos están cerca de o en su límite. + +#### 3. Incrementa la asignación de recursos para los servicios en su límite + +1. Ingresa en el shell administrativo utilizando SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Ejecuta el siguiente comando para ver qué recursos se encuentran disponibles para su asignación: + + ```shell + nomad node status -self + ``` + + En la salida, encuentra la sección de "Recursos asignados". Se debe ver similar al siguiente ejemplo: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + Para la memoria y el CPU, esta muestra cuánto se asigna al **total** de **todos** los servicios (el valor de la izquierda) y cuánto queda disponible (el valor de la derecha). En el ejemplo anterior, hay 23 GiB de memoria asignada de los 32 GiB totales. Esto significa que hay 9 GiB de memoria disponibles para asignar. + + {% warning %} + + **Advertencia:** Ten cuidado de no asignar más del total de los recursos disponibles o los servicios no podrán iniciar. + + {% endwarning %} +1. Cambia el directorio a `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + En este directorio hay tres archivos que corresponden a los servicios de {% data variables.product.prodname_actions %} descritos anteriormente: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. Para los servicios en los que identificaste una necesidad de ajuste, abre el archivo correspondiente y ubica el grupo `resources` que se ve como el siguiente ejemplo: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + Los valores están en MHz para los recursos de CPU y en MB para los recursos de memoria. + + Por ejemplo, para incrementar los límites de recursos en el ejemplo anterior a 1 GHz para el CPU y 4 GB de memoria, cámbialos a: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Guarda el cambio y sal del archivo. +1. Ejecuta `ghe-config-apply` para aplicar los cambios. + + Cuando ejecutes `ghe-config-apply`, si ves una salida como `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, entonces el cambio seguramente sobreasignó recursos de CPU o de memoria. Si esto sucede, edita los archivos de configuración nuevamente y baja los recursos de CPU o de memoria y luego vuelve a ejecutar `ghe-config-apply`. +1. Después de aplicar la configuración, ejecuta `ghe-actions-check` para verificar que los servicios de {% data variables.product.prodname_actions %} estén operando. diff --git a/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md b/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..a98afa99e638a --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Utilizar un ambiente de montaje +intro: 'Aprende sobre cómo utilizar {% data variables.product.prodname_actions %} con los ambientes de montaje de {% data variables.product.prodname_ghe_server %}.' +versions: + enterprise-server: '>=3.0' +--- + +Puede ser útil tener un ambiente de montaje o de pruebas para {% data variables.product.product_location %}, para que así puedas probar las actualizaciones o características nuevas antes de implementarlas en tu ambiente productivo. + +Una forma común para crear el ambiente de montaje es utilizar un respaldo de tu instancia productiva y restablecerlo al ambiente de montaje. + +Cuando configures un ambiente de montaje de {% data variables.product.prodname_ghe_server %} que cuente con {% data variables.product.prodname_actions %} habilitadas, debes utilizar una configuración de almacenamiento externo diferente al de tu ambiente productivo para almacenar las {% data variables.product.prodname_actions %}. De lo contrario, tu ambiente de montaje escribirá en el mismo almacenamiento externo que utiliza tu ambiente productivo. + +Espera ver errores de tipo `404` en tu ambiente de montaje cuando trates de ver las bitácoras o artefactos para las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}, ya que estos datos estarán ausentes de tu ubicación de almacenamiento de montaje. + +Aunque no es necesario que las {% data variables.product.prodname_actions %} sean funcionales en tu ambiente de montaje, opcionalmente, puedes copiar los archivos del la ubicación de almacenamiento productivo hacia la ubicación de almacenamiento de montaje. + +* Para una cuenta de almacenamiento de Azure, puedes utilizar [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Por ejemplo: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* Para los buckets de Amazon S3, puedes usar [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Por ejemplo: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md new file mode 100644 index 0000000000000..77add16150446 --- /dev/null +++ b/translations/es-ES/content/admin/index.md @@ -0,0 +1,32 @@ +--- +title: Administradores de empresa +redirect_from: + - /enterprise/admin/hidden/migrating-from-github-fi/ + - /enterprise/admin +intro: La documentación y las guías para los administradores empresariales, administradores de sistema y especialistas de seguridad quienes {% if enterpriseServerVersions contains currentVersion %}despliegan, {% endif %}configuran{% if enterpriseServerVersions contains currentVersion %},{% endif %} y administran {% data variables.product.product_name %}. +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% link_with_intro /overview %} + +{% link_with_intro /installation %} + +{% link_with_intro /configuration %} + +{% link_with_intro /authentication %} + +{% link_with_intro /user-management %} + +{% link_with_intro /policies %} + +{% link_with_intro /enterprise-management %} + +{% link_with_intro /github-actions %} + +{% link_with_intro /packages %} + +{% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/es-ES/content/admin/installation/index.md b/translations/es-ES/content/admin/installation/index.md new file mode 100644 index 0000000000000..e49383211bb5d --- /dev/null +++ b/translations/es-ES/content/admin/installation/index.md @@ -0,0 +1,33 @@ +--- +title: 'Instalar {% data variables.product.prodname_enterprise %}' +shortTitle: Instalar +intro: 'Los administradores de sistema y los especialistas de seguridad y de operaciones pueden instalar {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin-guide/ + - /enterprise/admin/guides/installation/ + - /enterprise/admin/categories/customization/ + - /enterprise/admin/categories/general/ + - /enterprise/admin/categories/logging-and-monitoring/ + - /enterprise/admin/installation +versions: + enterprise-server: '*' +--- + +Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). + +{% data reusables.enterprise_installation.request-a-trial %} + +Si tienes preguntas sobre el proceso de instalación, consulta "[Trabajar con el soporte {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/)." + +### Índice + + +{% topic_link_in_list /setting-up-a-github-enterprise-server-instance %} + {% link_in_list /installing-github-enterprise-server-on-aws %} + {% link_in_list /installing-github-enterprise-server-on-azure %} + {% link_in_list /installing-github-enterprise-server-on-google-cloud-platform %} + {% link_in_list /installing-github-enterprise-server-on-hyper-v %} + {% link_in_list /installing-github-enterprise-server-on-openstack-kvm %} + {% link_in_list /installing-github-enterprise-server-on-vmware %} + {% link_in_list /installing-github-enterprise-server-on-xenserver %} + {% link_in_list /setting-up-a-staging-instance %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md new file mode 100644 index 0000000000000..af4485bf23e4a --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -0,0 +1,134 @@ +--- +title: Instalar el servidor de GitHub Enterprise en AWS +intro: 'Para instalar el {% data variables.product.prodname_ghe_server %} en Amazon Web Services (AWS), debes iniciar una instancia de Amazon Elastic Compute Cloud (EC2) y crear y adjuntar un volumen de datos separado de Amazon Elastic Block Store (EBS).' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-aws +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener una cuenta AWS capaz de iniciar instancias EC2 y crear volúmenes EBS. Para obtener más información, consulta el [Sitio web de Amazon Web Services](https://aws.amazon.com/). +- La mayoría de las acciones necesarias para iniciar {% data variables.product.product_location %} también pueden realizarse por medio de la consola de administración de AWS. Sin embargo, recomendamos instalar la interfaz de línea de comando de AWS (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan AWS CLI. Para obtener más información, consulta las guías de Amazon "[Trabajar con la consola de administración de AWS](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" y "[Qué es la interfaz de línea de comando de AWS](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)." + +Esta guía supone que estás familiarizado con los siguientes conceptos de AWS: + + - [Iniciar instancias de EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) + - [Administrar volúmenes de EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) + - [Utilizar grupos de seguridad](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (para administrar el acceso de red a tu instancia) + - [Direcciones IP elásticas (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (altamente recomendadas para los entornos de producción) + - [EC2 y Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (si planeas iniciar dentro de Virtual Private Cloud) + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Determinar el tipo de instancia + +Antes de iniciar {% data variables.product.product_location %} en AWS, deberás determinar el tipo de máquina virtual que mejor se adapte a las necesidades de tu organización. + +#### Tipos de instancias admitidas + +{% data reusables.enterprise_installation.aws-supported-instance-types %} + +#### Tipos de instancias recomendadas + +{% data reusables.enterprise_installation.aws-recommended-instance-types %} + +{% data reusables.enterprise_installation.warning-on-scaling %} + +### Seleccionar la AMI del {% data variables.product.prodname_ghe_server %} + +Puedes seleccionar una Amazon Machine Image (AMI) para el {% data variables.product.prodname_ghe_server %} utilizando el portal del {% data variables.product.prodname_ghe_server %} o la CLI de AWS. + +Las AMIs para {% data variables.product.prodname_ghe_server %} se encuentran disponibles en la región de AWS GovCloud (EE.UU. Este y EE.UU. Oeste). Esto permite que los clientes de EE. UU. con requisitos reglamentarios específicos ejecuten el {% data variables.product.prodname_ghe_server %} en un entorno de nube que cumpla con los requisitos a nivel federal. Para obtener más información sobre el cumplimiento de AWS de las normas federales y otras normas, consulta la [Página de GovCloud (EE. UU.) de AWS](http://aws.amazon.com/govcloud-us/) y la [Página de cumplimiento de AWS](https://aws.amazon.com/compliance/). + +#### Utilizar el portal {% data variables.product.prodname_ghe_server %} para seleccionar una AMI + +{% data reusables.enterprise_installation.enterprise-download-procedural %} +{% data reusables.enterprise_installation.download-appliance %} +3. En el menú desplegable Select your platform (Selecciona tu plataforma), haz clic en **Amazon Web Services**. +4. En el menú desplegable Select your AWS region (Selecciona tu región AWS), elige tu región deseada. +5. Toma nota de la ID de AMI que se muestra. + +#### Utilizar la CLI de AWS para seleccionar una AMI + +1. Utilizando una CLI de AWS, obtén una lista de imágenes publicadas del {% data variables.product.prodname_ghe_server %} por ID de propietarios de AWS de {% data variables.product.prodname_dotcom %} (`025577942450` para GovCloud, y `895557238572` para otras regiones). Para obtener más información, consulta "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" en los documentos de AWS. + ```shell + aws ec2 describe-images \ + --owners OWNER ID \ + --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \ + --output=text + ``` +2. Toma nota del ID de AMI de la última imagen del {% data variables.product.prodname_ghe_server %}. + +### Crear un grupo de seguridad + +Si estás configurando tu AMI por primera vez, deberás crear un grupo de seguridad y agregar una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para más información, consulta la guía AWS "[Usar grupos de seguridad](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)." + +1. Crea un nuevo grupo de seguridad utilizando la CLI de AWS. Para obtener más información, consulta "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" en los documentos de AWS. + ```shell + $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" + ``` + +2. Toma nota del ID del grupo de seguridad (`sg-xxxxxxxx`) de tu grupo de seguridad recientemente creado. + +3. Crea una regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener más información, consulta "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" en los documentos de AWS. + ```shell + $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE + ``` + Esta tabla identifica para qué se utiliza cada puerto. + + {% data reusables.enterprise_installation.necessary_ports %} + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +Para crear la instancia, deberás lanzar una instancia de EC2 con tu AMI {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." + +{% note %} + +**Nota:** puedes cifrar el disco de datos para obtener un nivel adicional de seguridad y estar seguro de que los datos que escribas en tu instancia están protegidos. Hay un leve impacto de desempeño cuando usas discos encriptados. Si decides cifrar tu volumen, recomendamos firmemente hacerlo **antes** de comenzar tu instancia por primera vez. Para más información, consulta la guía de Amazon [sobre el cifrado EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). + +{% endnote %} + +{% warning %} + +**Advertencia:** si decides habilitar la encriptación después de configurar tu instancia, deberás migrar tus datos al volumen encriptado, que producirá tiempo de inactividad para tus usuarios. + +{% endwarning %} + +#### Lanzar una instancia de EC2 + +En la CLI de AWS, inicia una instancia de EC2 utilizando tu AMI y el grupo de seguridad que has creado. Adjunta un nuevo dispositivo de bloque para utilizarlo como volumen de almacenamiento para tus datos de la instancia y configura el tamaño de acuerdo con la cantidad de licencias de usuario que tengas. Para obtener más información, consulta "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" en los documentos de AWS. + +```shell +aws ec2 run-instances \ + --security-group-ids SECURITY_GROUP_ID \ + --instance-type INSTANCE_TYPE \ + --image-id AMI_ID \ + --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ + --region REGION \ + --ebs-optimized +``` + +#### Asignar una IP elástica y asociarla con la instancia + +Si esta es una instancia de producción, recomendamos firmemente asignar una IP elástica (EIP) y asociarla con la instancia antes de continuar con la configuración del {% data variables.product.prodname_ghe_server %}. De lo contrario, la dirección IP pública de la instancia no se conservará después de que se reinicie la instancia. Para obtener más información, consulta "[Asignar una dirección IP elástica](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" y "[Asociar una dirección IP elástica con una instancia en ejecución](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" en la documentación de Amazon. + +Tanto en la instancia principal y en la de réplica deberían asignarse EIP separadas en las configuraciones de alta disponibilidad de producción. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." + +### Configurar la instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md new file mode 100644 index 0000000000000..95fe583b17530 --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -0,0 +1,113 @@ +--- +title: Instalar el servidor de GitHub Enterprise en Azure +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Azure, debes implementar en una instancia de serie DS y usar almacenamiento Premium-LRS.' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-azure +versions: + enterprise-server: '*' +--- + +Puedes implementar {% data variables.product.prodname_ghe_server %} en Azure mundial o Azure Government. + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener una cuenta Azure capaz de abastecer nuevas máquinas. Para obtener más información, consulta el [sitio web de Microsoft Azure](https://azure.microsoft.com). +- La mayoría de las acciones necesarias para lanzar tu máquina virtual (VM) también se podrían realizar por medio del Portal Azure. Sin embargo, recomendamos instalar la interfaz de la línea de comando de Azure (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan Azure CLI 2.0. Para obtener más información, consulta la guía de Azure "[Instalar Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)." + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Determinar el tipo de máquina virtual + +Antes de iniciar {% data variables.product.product_location %} en Azure, deberás determinar el tipo de máquina virtual que mejor se adapte a las necesidades de tu organización. + +#### Tipos y regiones de VM admitidas + +El aparato {% data variables.product.prodname_ghe_server %} requiere un disco de datos de almacenamiento prémium, y es compatible con cualquier Azure VM que admita almacenamiento prémium. Para obtener más información, consulta "[VM admitidos](https://docs.microsoft.com/azure/storage/common/storage-premium-storage#supported-vms)" en la documentación de Azure. Para obtener información general sobre los VM disponibles, consulta [la página de descripción de máquinas virtuales de Azure](https://azure.microsoft.com/pricing/details/virtual-machines/#Linux). + +{% data variables.product.prodname_ghe_server %} admite cualquier región que sea compatible con tu tipo de VM. Para obtener más información sobre las regiones admitidas para cada VM, consulte los productos de Azure "[disponibles por región](https://azure.microsoft.com/regions/services/)." + +#### Tipos de VM recomendados + +Te recomendamos que uses un tipo de instancia DS v2 con 14 GB de RAM como mínimo. Puedes usar cualquier tipo de VM admitido. Recomendamos los siguientes tipos de instancia con base en la cantidad de licencias que tengas. + +| Asientos | Tipo recomendado | +|:----------------------------------------:|:------------------:| +| Prueba, Demo o 10 usuarios no frecuentes | Standard_DS11_v2 | +| 10 - 3000 | Standard_DS12_v2 | +| 3000 - 8000 | Standard_DS14_v2 | +| 8000 - 10000+ | Standard_DS15_v2 | + +{% data reusables.enterprise_installation.warning-on-scaling %} + +### Crear la máquina virtual{% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.create-ghe-instance %} + +1. Encuentra la imagen de aparato más reciente {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre el comando `vm image list`, consulta "[lista de imagen vm de az](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" en la documentación de Microsoft. + ```shell + $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V + ``` + +2. Crea una nueva VM utilizando la imagen de aparato que encontraste. Para obtener más información, consulta "[crear vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" en la documentación de Microsoft. + + Aprueba opciones para el nombre de tu VM, el grupo de recurso, el tamaño de tu VM, el nombre de tu región Azure preferida, el nombre de la imagen de tu aparato VM que enumeraste en el paso anterior y el almacenamiento SKU para un almacenamiento prémium. Para obtener más información sobre grupos de recursos, consulta "[Grupos de recursos](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" en la documentación de Microsoft. + + ```shell + $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS + ``` + +3. Configura los parámetros de seguridad en tu VM para abrir los puertos requeridos. Para obtener más información, consulta "[abrir puerto de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" en la documentación de Microsoft. Consulta la tabla de abajo para obtener una descripción de cada puerto para determinar qué puertos debes abrir. + + ```shell + $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER + ``` + + Esta tabla identifica para qué se utiliza cada puerto. + + {% data reusables.enterprise_installation.necessary_ports %} + +4. Crea y adjunta a la VM un nuevo disco de datos descifrado y configura su tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[adjuntar un disco de vm de az](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" en la documentación de Microsoft. + + Aprueba opciones para el nombre de tu VM (por ejemplo, `ghe-acme-corp`), el grupo de recurso, el almacenamiento prémium de SKU, el tamaño del disco (por ejemplo, `100`) y un nombre para el VHD resultante. + + ```shell + $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite + ``` + + {% note %} + + **Nota:** para instancias no productivas que tengan suficiente rendimiento de E/S, el tamaño mínimo recomendado es de 40 GiB con caché de lectura/escritura activado (`--caching ReadWrite`). + + {% endnote %} + +### Configurara la máquina virtual {% data variables.product.prodname_ghe_server %} + +1. Antes de configurar el VM, debes esperar que pase al estado ReadyRole. Controla el estado del VM con el comando `vm list`. Para obtener más información, consulta "[lista de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" en la documentación de Microsoft. + ```shell + $ az vm list -d -g RESOURCE_GROUP -o table + > Name ResourceGroup PowerState PublicIps Fqdns Location Zones + > ------ --------------- ------------ ------------ ------- ---------- ------- + > VM_NAME RESOURCE_GROUP VM running 40.76.79.202 eastus + + ``` + {% note %} + + **Nota:** Azure no crea automáticamente una entrada FQDNS para el VM. Para obtener más información, consulta la guía de Azure sobre cómo "[Crear un nombre de dominio certificado completo en el portal de Azure para una VM de Linux](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)." + + {% endnote %} + + {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} + {% data reusables.enterprise_installation.upload-a-license-file %} + {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." + {% data reusables.enterprise_installation.instance-will-restart-automatically %} + {% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} + diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md new file mode 100644 index 0000000000000..50cf7f88ab7aa --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -0,0 +1,117 @@ +--- +title: Instalar el servidor de GitHub Enterprise en Google Cloud Platform +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Google Cloud Platform, debes implementar un tipo de máquina soportado y utilizar un disco estándar persistente o un SSD persistente.' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener una cuenta de Google Cloud Platform capaz de iniciar instancias de la máquina virtual (VM) de Google Compute Engine (GCE). Para obtener más información, consulta el [Sitio web de Google Cloud Platform](https://cloud.google.com/) y la [Documentación de Google Cloud Platform](https://cloud.google.com/docs/). +- La mayoría de las acciones necesarias para iniciar tu instancia pueden también realizarse utilizando la [Consola de Google Cloud Platform](https://cloud.google.com/compute/docs/console). Sin embargo, recomendamos instalar la herramienta de línea de comando de gcloud compute para la configuración inicial. Se incluyen abajo ejemplos que utilizan la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta la guía de instalación y configuración en la documentación de Google de "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)". + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Determinar el tipo de máquina + +Antes de iniciar {% data variables.product.product_location %} en Google Cloud Platform, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. + +#### Tipos de máquinas admitidas + +{% data variables.product.prodname_ghe_server %} es compatible en los siguientes tipo de máquinas de Google Compute Engine (GCE). Para obtener más información, consulta el [artículo sobre tipos de máquinas de Google Cloud Platform](https://cloud.google.com/compute/docs/machine-types). + +| Memoria alta | +| ------------- | +| n1-highmem-4 | +| n1-highmem-8 | +| n1-highmem-16 | +| n1-highmem-32 | +| n1-highmem-64 | +| n1-highmem-96 | + +#### Tipos recomendados de máquina + +Recomendamos estos tipos de máquina con base en la cantidad de licencias que tengas. + +| Asientos | Tipo recomendado | +|:----------------------------------------:|:----------------:| +| Prueba, Demo o 10 usuarios no frecuentes | n1-standard-4 | +| 10 - 3000 | n1-standard-8 | +| 3000 - 5000 | n1-highmem-8 | +| 5000 - 8000 | n1-highmem-16 | +| 8000 - 10000+ | n1-highmem-32 | + +{% data reusables.enterprise_installation.warning-on-scaling %} + +### Seleccionar la imagen {% data variables.product.prodname_ghe_server %} + +1. Utilizando la herramienta de línea de comando de [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), enumera las imágenes públicas{% data variables.product.prodname_ghe_server %}: + ```shell + $ gcloud compute images list --project github-enterprise-public --no-standard-images + ``` + +2. Toma nota del nombre de la imagen para la última imagen de GCE de {% data variables.product.prodname_ghe_server %}. + +### Configurar el firewall + +Las máquinas virtuales de GCE se crean como un miembro de la red, que tiene un firewall. Para la red asociada con la VM {% data variables.product.prodname_ghe_server %}, deberás configurar el firewall para permitir los puertos requeridos en la tabla de abajo. Para obtener más información sobre las reglas de firewall en Google Cloud Platform, consulta la guía de Google "[Descripción de las reglas de firewall](https://cloud.google.com/vpc/docs/firewalls)." + +1. Crea la red utilizando la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta "[crea redes de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" en la documentación de Google. + ```shell + $ gcloud compute networks create NETWORK-NAME --subnet-mode auto + ``` +2. Crea una regla de firewall para cada uno de los puertos en la tabla de abajo. Para obtener más información, consulta las "[reglas de firewall de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" en la documentación de Google. + ```shell + $ gcloud compute firewall-rules create RULE-NAME \ + --network NETWORK-NAME \ + --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp + ``` + Esta tabla identifica los puertos requeridos y para qué se usa cada puerto. + + {% data reusables.enterprise_installation.necessary_ports %} + +### Asignar una IP estática y atribuirla a una VM + +Si es un aparato de producción, recomendamos firmemente reservar una dirección de IP estática externa y asignarla a la VM {% data variables.product.prodname_ghe_server %}. En caso contrario, la dirección de IP pública de la VM no se mantendrá después de que se reinicie. Para obtener más información, consulta la guía de Google "[Reservar una dirección estática de IP externa](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)." + +En las configuraciones de alta disponibilidad de producción, tantos en el aparato principal como en la réplica deberían asignarse direcciones estáticas de IP separadas. + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +Para crear la instancia {% data variables.product.prodname_ghe_server %}, deberás crear una instancia de GCE con tu imagen {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." + +1. Crea un disco de datos para utilizar como un volumen de almacenamiento adjunto para tu instancia de datos utilizando la herramienta de línea de comandos para cálculo gcloud y configura el tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[crea discos de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" en la documentación de Google. + ```shell + $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE + ``` + +2. Después crea una instancia utilizando el nombre de la imagen {% data variables.product.prodname_ghe_server %} que seleccionaste, y adjunta el disco de datos. Para obtener más información, consulta "[crea instancias de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" en la documentación de Google. + ```shell + $ gcloud compute instances create INSTANCE-NAME \ + --machine-type n1-standard-8 \ + --image GITHUB-ENTERPRISE-IMAGE-NAME \ + --disk name=DATA-DISK-NAME \ + --metadata serial-port-enable=1 \ + --zone ZONE \ + --network NETWORK-NAME \ + --image-project github-enterprise-public + ``` + +### Configurar la instancia + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md new file mode 100644 index 0000000000000..4aca6f18312e5 --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -0,0 +1,66 @@ +--- +title: Instalar el servidor de GitHub Enterprise en Hyper-V +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Hyper-V, debes implementarlo en una máquina ejecutando Windows Server 2008 a través de Windows Server 2016.' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener Windows Server 2008 a través de Windows Server 2016, que admita Hyper-V. +- La mayoría de las acciones necesarias para crear tu máquina virtual (VM) también se pueden realizar utilizando el [Administrador de Hyper-V](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). Sin embargo, recomendamos utilizar la shell de la línea de comando de Windows PowerShell para la configuración inicial. Abajo se incluyen ejemplos que utilizan PowerShell. Para obtener más información, consulta la guía de Microsoft "[Instrucciones para Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Descargar la imagen {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.enterprise-download-procedural %} +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **Hyper-V (VHD)**. +5. Haz clic en **Download for Hyper-V (VHD) (Descarga para Hyper-V (VHD))**. + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.create-ghe-instance %} + +1. Crea una nueva máquina virtual de Generación 1 en PowerShell, configura el tamaño de acuerdo con la cantidad de licencias que tengas, y adjunta la imagen de {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener más información, consulta "[VM nuevo](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" en la documentación de Microsoft. + ```shell + PS C:\> New-VM -Generation 1 -Name VM_NAME -MemoryStartupBytes MEMORY_SIZE -BootDevice VHD -VHDPath PATH_TO_VHD + ``` +{% data reusables.enterprise_installation.create-attached-storage-volume %} Reemplaza la `PATH_TO_DATA_DISK` con la ruta a la ubicación donde creas el disco. Para obtener más información, consulta "[VHD nuevo](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" en la documentación de Microsoft. + ```shell + PS C:\> New-VHD -Path PATH_TO_DATA_DISK -SizeBytes DISK_SIZE + ``` +3. Adjunta el disco de datos a tu instancia. Para obtener más información, consulta "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" en la documentación de Microsoft. + ```shell + PS C:\> Add-VMHardDiskDrive -VMName VM_NAME -Path PATH_TO_DATA_DISK + ``` +4. Inicia la VM. Para obtener más información, consulta "[Iniciar la VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" en la documentación de Microsoft. + ```shell + PS C:\> Start-VM -Name VM_NAME + ``` +5. Obtén la dirección de IP de tu VM. Para obtener más información, consulta "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" en la documentación de Microsoft. + ```shell + PS C:\> (Get-VMNetworkAdapter -VMName VM_NAME).IpAddresses + ``` +6. Copia la dirección de IP de la VM y pégala en el explorador web. + +### Configurar la instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Leer más + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md new file mode 100644 index 0000000000000..7e401d1931163 --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -0,0 +1,53 @@ +--- +title: Instalar el servidor de GitHub Enterprise en OpenStack KVM +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en OpenStack KVM, debes tener acceso a OpenStack y descargar la imagen QCOW2 {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener acceso a una instalación de OpenStack Horizon, la interfaz de usuario con base en la web para los servicios de OpenStack. Para obtener más información, consulta la [Documentación de Horizon](https://docs.openstack.org/horizon/latest/). + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Descargar la imagen {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.enterprise-download-procedural %} +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **OpenStack KVM (QCOW2) (Abrir Stack KVM (QCOW2))**. +5. Haz clic en **Download for OpenStack KVM (QCOW2) (Descargar para OpenStack KVM (QCOW2))**. + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.create-ghe-instance %} + +1. En OpenStack Horizon, carga la + +imagen de {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, dirígete a la sección "Cargar una imagen" en la guía de OpenStack "[Cargar y administrar imágenes](https://docs.openstack.org/horizon/latest/user/manage-images.html)". +{% data reusables.enterprise_installation.create-attached-storage-volume %} Para encontrar instrucciones, consulta la guía de OpenStack "[Crear y administrar volúmenes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)". +3. Crea un grupo de seguridad, y agrega una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener instrucciones, consulta la guía de OpenStack "[Configurar acceso y seguridad para instancias](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)." + + {% data reusables.enterprise_installation.necessary_ports %} +4. De forma opcional, asocia una IP flotante a la instancia. Según tu configuración de OpenStack, es posible que necesites asignar una IP flotante al proyecto y asociarla a la instancia. Contacta a tu administrador de sistema para determinar si este es tu caso. Para obtener más información, consulta "[Asignar una dirección de IP flotante a una instancia](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" en la documentación de OpenStack. +5. Inicia {% data variables.product.product_location %} utilizando la imagen, el volumen de datos y el grupo de seguridad creado en los pasos previos. Para obtener instrucciones, consulta la guía OpenStack "[Iniciar y administrar instancias](https://docs.openstack.org/horizon/latest/user/launch-instances.html)." + +### Configurar la instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md new file mode 100644 index 0000000000000..48bfea3eac6ee --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -0,0 +1,52 @@ +--- +title: Instalar el servidor de GitHub Enterprise en VMare +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en VMware, debes descargar el cliente vSphere de VMware, y después descargar y desplegar el software de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/articles/getting-started-with-vmware/ + - /enterprise/admin/articles/installing-vmware-tools/ + - /enterprise/admin/articles/vmware-esxi-virtual-machine-maximums/ + - /enterprise/admin/guides/installation/installing-github-enterprise-on-vmware/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-vmware +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes tener un VMware vSphere ESXi Hypervisor, aplicado a una máquina de metal expuesto que ejecutará {% data variables.product.product_location %}. Admitimos versiones 5.5 a 6.7. El Hipervisor de ESXi es gratuito y no incluye el vCenter Server (opcional). Para obtener más información, consulta la [Documentación de VMware ESXi](https://www.vmware.com/products/esxi-and-esx.html). +- Deberás acceder a vSphere Client. Si tienes vCenter Server puedes usar vSphere Web Client. Para obtener más información, consulta la guía de VMware "[Registrarse en vCenter Server al utilizar vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)." + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Descargar la imagen {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.enterprise-download-procedural %} +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **VMware ESXi/vSphere (OVA)**. +5. Haz clic en **Download for VMware ESXi/vSphere (OVA) (Descargar para VMware ESXi/vSphere (OVA))**. + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.create-ghe-instance %} + +1. Por medio de vSphere Windows Client o vCenter Web Client, importa la imagen del {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de VMware "[Implementar una plantilla OVF u OVA](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)." + - Cuando seleccionas un almacén de datos, elige uno con suficiente espacio para alojar los discos de la VM. Para encontrar las especificaciones mínimas recomendadas de hardware para tu instancia, consulta las "[Consideraciones de hardware](#hardware-considerations)". Te recomendamos un aprovisionamiento robusto con lazy zeroing. + - Deja el casillero **Power on after deployment (Encender después de la implementación)** sin marcar, ya que necesitarás agregar un volumen de almacenamiento adjunto para tus datos del repositorio después de aprovisionar la VM. +{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de VMware "[Agregar un nuevo disco duro a una máquina virtual](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)." + +### Configurar la instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md new file mode 100644 index 0000000000000..59f88e7e0f671 --- /dev/null +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -0,0 +1,49 @@ +--- +title: Instalar el servidor de GitHub Enterprise en XenServer +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en XenServer, debes implementar la imagen de disco {% data variables.product.prodname_ghe_server %} a un servidor XenServer.' +redirect_from: + - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver/ + - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- {% data reusables.enterprise_installation.software-license %} +- Debes instalar el XenServer Hypervisor en la máquina que ejecutará tu máquina virtual (VM) {% data variables.product.prodname_ghe_server %}. Admitimos versiones 6.0 a 7.0. +- Recomendamos utilizar XenCenter Windows Management Console para la configuración inicial. Abajo se incluyen instrucciones utilizando XenCenter Windows Management Console. Para obtener más información, consulta la guía de Citrix "[Cómo descargar e instalar una nueva versión de XenCenter](https://support.citrix.com/article/CTX118531)." + +### Consideraciones relativas al hardware + +{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} + +### Descargar la imagen {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.enterprise-download-procedural %} +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **XenServer (VHD)**. +5. Para descargar tu archivo de licencia, haz clic en **Download license (Descargar licencia)**. + +### Crear la instancia {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.create-ghe-instance %} + +1. En XenCenter, importa la imagen {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de XenCenter "[Importar imágenes de disco](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)." + - Para el paso "Enable Operating System Fixup (Habilitar Ajuste del sistema en funcionamiento)", selecciona **Don't use Operating System Fixup (No usar Ajuste del sistema en funcionamiento)**. + - Deja la VM apagada cuando hayas finalizado. +{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de XenCenter "[Agregar discos virtuales](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)." + +### Configurar la instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} + +### Further reading + +- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md new file mode 100644 index 0000000000000..39815e65c21e5 --- /dev/null +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md @@ -0,0 +1,14 @@ +--- +title: Configurar una instancia del servidor de GitHub Enterprise +intro: 'Puede instalar {% data variables.product.prodname_ghe_server %} en la plataforma de virtualización soportada de tu elección.' +redirect_from: + - /enterprise/admin/installation/getting-started-with-github-enterprise-server + - /enterprise/admin/guides/installation/supported-platforms/ + - /enterprise/admin/guides/installation/provisioning-and-installation/ + - /enterprise/admin/guides/installation/setting-up-a-github-enterprise-instance/ + - /enterprise/admin/installation/setting-up-a-github-enterprise-server-instance +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md b/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md new file mode 100644 index 0000000000000..4014ff155d33e --- /dev/null +++ b/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md @@ -0,0 +1,32 @@ +--- +title: Configurar una instancia de preparación +intro: 'Puedes utilizar una *instancia de preparación* para probar las modificaciones antes de que se apliquen a {% data variables.product.product_location %}. Por ejemplo, podrías utilizar una instancia de preparación para probar nuevas actualizaciones del {% data variables.product.prodname_ghe_server %} o para practicar importar datos de migración.' +redirect_from: + - /enterprise/admin/installation/setting-up-a-staging-instance +versions: + enterprise-server: '*' +--- + +{% tip %} + +**Sugerencia:** puedes volver a usar tu archivo de licencia existente de {% data variables.product.prodname_enterprise %} siempre que la instancia de preparación no se use para producción. + +{% endtip %} + +Para probar en profundidad un aparato del {% data variables.product.prodname_ghe_server %} deberás considerar los sistemas externos que interactúan con este. Algunos factores que considerar probar son: + + - La autenticación, en especial si se está usando un proveedor externo de autenticación + - La integración con un sistema externo de vales + - La integración con un servidor de integración continua + - Los scripts externos o el software que usan {% data variables.product.prodname_enterprise_api %} + - El servidor externo SMTP para notificaciones por correo electrónico + +1. Realiza una copia de seguridad de tu instancia de producción utilizando {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta la sección "Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}" en "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)." +2. Configura una nueva instancia para que actúe como tu entorno de preparación. Puedes utilizar las mismas guías para aprovisionar e instalar tu instancia de preparación como hiciste para tu instancia de producción. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." +3. Restaura tu copia de seguridad a tu instancia de preparación. Para obtener más información, consulta la sección "Restaurar una copia de seguridad" en "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Leer más + +- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md new file mode 100644 index 0000000000000..33dd4981a84d8 --- /dev/null +++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md @@ -0,0 +1,35 @@ +--- +title: Acerca de las cuentas de empresa +intro: 'Con {% data variables.product.product_name %}, puedes utilizar una cuenta empresarial para proporcionar a los administradores una visibilidad centralizada y la administración{% if enterpriseServerVersions contains currentVersion %} del uso de licencia y su facturación{% endif %}.' +redirect_from: + - /enterprise/admin/installation/about-enterprise-accounts + - /enterprise/admin/overview/about-enterprise-accounts +versions: + enterprise-server: '>=2.20' + github-ae: '*' +--- + +### Acerca de las cuentas empresariales en {% data variables.product.product_name %} + +Una cuenta empresarial te permite administrar varias organizaciones{% if enterpriseServerVersions contains currentVersion %} e instancias de {% data variables.product.prodname_ghe_server %}{% else %} eb {% data variables.product.product_name %}{% endif %}. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. Los administradores de empresas pueden administrar los parámetros y las referencias, como: + +- El acceso y administración de miembros (miembros de la organización, colaboradores externos){% if enterpriseServerVersions contains currentVersion %} +- La facturación y uso (instancias de {% data variables.product.prodname_ghe_server %}, licencias de usuario, paquetes de {% data variables.large_files.product_name_short %}){% endif %} +- La seguridad {% if enterpriseServerVersions contains currentVersion %}(inicio de sesión único, autenticación bifactorial) +- El compartir los paquetes de solicitudes y {% if enterpriseServerVersions contains currentVersion %}soporte {% endif %} con {% data variables.contact.enterprise_support %}{% endif %} + +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} Para obtener más información sobre la administración de tu suscripción a {% data variables.product.prodname_ghe_cloud %}, consulta la sección "[Visualizar la suscripción y el uso de tu cuenta empresarial](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)". {% endif %}Para obtener más información acerca de cómo administrar tu {% data variables.product.product_name %} configuración de facturación, consulta la sección "[Administrar la facturación de tu empresa](/admin/overview/managing-billing-for-your-enterprise)". + +Para obtener más información acerca de la administración de usuarios, organizaciones, datos y políticas para {% data variables.product.product_location %}, consulta las secciones "[Administrar usuarios, organizaciones y repositorios](/admin/user-management)" y "[Configurar políticas para tu empresa](/admin/policies)". + +Para obtener más información acerca de la administración para cuentas empresariales utilizando la API de GraphQL, consulta la sección "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)". + +{% if enterpriseServerVersions contains currentVersion %} + +Para obtener más información acerca de las diferencias entre {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}, consulta la sección "[ productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". Para mejorar tu cuenta a {% data variables.product.prodname_enterprise %} o para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}. + +### Administrar las licencias de {% data variables.product.prodname_ghe_server %} enlazadas con tu cuenta empresarial + +{% data reusables.enterprise-accounts.admin-managing-licenses %} + +{% endif %} diff --git a/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md b/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md new file mode 100644 index 0000000000000..5bb6254bfc3e5 --- /dev/null +++ b/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md @@ -0,0 +1,24 @@ +--- +title: Acerca de la API de GitHub Enterprise +intro: '{% data variables.product.product_name %} es compatible con las API de REST y de GraphQL.' +redirect_from: + - /enterprise/admin/installation/about-the-github-enterprise-server-api + - /enterprise/admin/articles/about-the-enterprise-api/ + - /enterprise/admin/articles/using-the-api/ + - /enterprise/admin/categories/api/ + - /enterprise/admin/overview/about-the-github-enterprise-server-api + - /admin/overview/about-the-github-enterprise-server-api +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Con las API, puedes automatizar muchas tareas administrativas. Algunos ejemplos incluyen los siguientes: + +{% if enterpriseServerVersions contains currentVersion %} +- Realizar cambios en {% data variables.enterprise.management_console %}. Para obtener más información, consulta la secicón "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)". +- Configura la sincronización de LDAP. Para obtener más información, consulta la sección "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %} +- Recolectar estadísticas sobre tu empresa. Para obtener más información, consulta la sección "[Estadísticas administrativas](/rest/reference/enterprise-admin#admin-stats)". +- Administra tu cuenta Enterprise. Para obtener más información, consulta "[Cuentas Enterprise](/graphql/guides/managing-enterprise-accounts)" + +Para conocer la documentación íntegra de la {% data variables.product.prodname_enterprise_api %}, consulta la [API de REST de {% data variables.product.prodname_dotcom %}](/rest) y la [API de GraphQL de {% data variables.product.prodname_dotcom%}](/graphql). diff --git a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..76a55c1e1dee5 --- /dev/null +++ b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: Acerca de las mejoras a los nuevos lanzamientos +shortTitle: Acerca de las mejoras +intro: 'Puedes beneficiarte de características nuevas y correcciones de errores para {% data variables.product.product_name %} si mejoras tu empresa a una versión más nueva.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} está en mejora contínua, con una funcionalidad nueva y correcciones de errores que se presentan mediante lanzamientos mayores y menores. + +Los lanzamientos principales incluyen funcionalidades nuevas y mejoras de características y habitualmente se presentan cada trimestre. + +Iniciando con {% data variables.product.prodname_ghe_server %} 3.0, todos los lanzamientos principales comenzarán con por lo menos un candidato de lanzamiento. Los candidatos de lanzamiento son lanzamientos principales propuestos con un conjunto completo de características. Puede que haya errores o problemas en un lanzamiento candidato que solo pueden encontrarse mediante la retroalimentación de los clientes que actualmente utilizan {% data variables.product.product_name %}. + +Puedes obtener acceso a las últimas características si pruebas un candidato de lanzamiento tan pronto como esté disponible. Puedes actualizarte a un candidato de lanzamiento desde una versión compatible y puedes actualizar desde el candidato de lanzamiento a versiones posteriores cuando éstas se lancen. Deberías actualizar cualquier ambiente que ejecute un lanzamiento candidato tan pronto como dicho lanzamiento esté disponible en general. Para obtener más información, consulta la sección "[requisitos de actualización](/admin/enterprise-management/upgrade-requirements)". + +Los candidatos de lanzamiento deben desplegarse en ambientes de montaje o de pruebas. Conforme pruebes un candidato de lanzamiento, por favor, proporciona retroalimentación contactando a soporte. Para obtener más información, consulta la sección "[Trabajar con {% data variables.contact.github_support %}](/admin/enterprise-support)". + +Utilizaremos tu retroalimentación para aplicar las correcciones de errores y cualquier otro cambio necesario para crear un lanzamiento productivo estable. Cada lanzamiento nuevo agrega correcciones de errores para los problemas de las versiones previas. Cuando el lanzamiento se encuentra listo para que se utilice en general, {% data variables.product.company_short %} publica un lanzamiento productivo estable. + +{% warning %} + +**Advertencia**: La actualización a un lanzamiento principal causará algunas horas de inactividad, durante las cuales ningún usuario podrá utilizar la empresa. Puedes informar a tus usuarios sobre dicha inactividad si publicas una notificación de anuncio global utilizando la configuración de tu empresa o la API de REST. Para obtener más información, consulta las secciones "[Personalizar los mensajes de usuario en tu instancia](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" y "[administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". + +{% endwarning %} + +Los lanzamientos menores, los cuales consisten únicamente de parches y correcciones de errores, ocurren con mayor frecuencia. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### Further reading + +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-ES/content/admin/overview/index.md b/translations/es-ES/content/admin/overview/index.md new file mode 100644 index 0000000000000..28769913e0313 --- /dev/null +++ b/translations/es-ES/content/admin/overview/index.md @@ -0,0 +1,20 @@ +--- +title: Resumen +intro: 'Puedes aprender sobre {% data variables.product.product_name %} y administrar cuentas de{% if enterpriseServerVersions contains currentVersion %} y accesos, licencias, y{% endif %} facturación.' +redirect_from: + - /enterprise/admin/overview +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). + +### Índice + +{% link_in_list /about-enterprise-accounts %} +{% link_in_list /managing-your-github-enterprise-license %} +{% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} +{% link_in_list /system-overview %} +{% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md new file mode 100644 index 0000000000000..b6b7287e987a4 --- /dev/null +++ b/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md @@ -0,0 +1,74 @@ +--- +title: Administrar la facturación para tu empresa +intro: 'Puedes visualizar la información de facturación para tu empresa.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /enterprise/admin/installation/managing-billing-for-github-enterprise + - /enterprise/admin/overview/managing-billing-for-github-enterprise + - /admin/overview/managing-billing-for-github-enterprise +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-ae.about-billing %} Una vez por día, {% data variables.product.prodname_dotcom %} contará la cantidad de usuarios en tu empresa que tengan una licencia. {% data variables.product.company_short %} te cobra por cada usuario con una licencia sin importar si éstos han ingresado en {% data variables.product.prodname_ghe_managed %} ese día. + +Para las regiones comerciales, el precio por usuario por día es de $1.2580645161. Para los meses de 31 días, el costo mensual de cada usuario es de $39. Para los meses que tienen menos días, el costo mensual es menor. Cada mes de facturación comienza en una hora fija del primer día calendario de cada mes. + +Si agregas un usuario licenciado a mitad de mes, éste solo se incluirá en el conteo de los días en los que haya tenido una licencia. Cuando elimines a un usuario con licencia, éste permanecerá en el conteo hasta el final de dicho mes. Por lo tanto, si agregas a un usuario a mitad de mes y después lo eliminas en el mismo mes, el usuario se incluirá en la cuenta desde el día que el usuario se agregó hasta el final del mes. No existe costo adicional si vuelves a agregar a un usuario durante el mismo mes en el que se eliminó. + +Por ejemplo, aquí mostramos los costos para los usuarios con licencias en fechas diferentes. + +| Usuario | Fechas de licencia | Días contados | Costo | +| --------- | ----------------------------------------------- | ------------- | ------ | +| @octocat | Enero 1 - Enero 31 | 31 | $39 | +| @robocat | Febrero 1 - Febrero 28 | 29 | $35.23 | +| @devtocat | Enero 15 - Enero 31 | 17 | $21.39 | +| @doctocat | Enero 1 - Enero 15 | 31 | $39 | +| @prodocat | Enero 7 - Enero 15 | 25 | $31.45 | +| @monalisa | Enero 1 - Enero 7,
    Enero 15 - Enero 31 | 31 | $39 | + +Tu empresa puede incluir una o más instancias. {% data variables.product.prodname_ghe_managed %} tiene un mínimo de 500 usuarios por instancia. {% data variables.product.company_short %} te cobra por un mínimo de 500 usuarios por instancia, aún si hay menos de 500 usuarios con una licencia en ese día. + +Puedes ver tu uso actual en tu [Portal de cuenta de Azure](https://portal.azure.com). + +{% else %} + +### Acerca de la facturación para las cuentas de empresa + +Las cuentas empresariales actualmente están disponibles para los clientes de {% data variables.product.prodname_enterprise %} que pagan por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas con tu cuenta empresarial se conjunta en un solo cargo por factura para todos tus servicios pagados de {% data variables.product.prodname_dotcom_the_website %} (incluyendo las licencias pagadas en organizaciones, paquetes de datos de {% data variables.large_files.product_name_long %}, y suscripciones a las apps de {% data variables.product.prodname_marketplace %}). + +Los propietarios de la empresa y los gerente de facturación pueden acceder y administrar todas las configuraciones de facturación para las cuentas de empresa. Para obtener más información sobre las cuentas empresariales, {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" y {% endif %}"[niveles de permiso en los repositorios para una organización](/articles/repository-permission-levels-for-an-organization)". Para obtener más información acerca de administrar a los gerentes de facturación, consulta la sección "[Invitar a las personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +### Visualizar tu factura actual + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +4. Dabajo de "Acciones Rápidas", da clic en **Ver factura**. ![Enlace para ver factura](/assets/images/help/business-accounts/view-invoice-link.png) + +### Pagar tu factura actual + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +4. Dabajo de "Acciones Rápidas", da clic en **Pagar factura**. ![Enlace para pagar factura](/assets/images/help/business-accounts/pay-invoice-link.png) +5. Debajo de "Pagar factura", teclea tu información de tarjeta de crédito en la forma segura, posteriormente, da clic en **Pagar factura**. ![Confirmar y pagar la factura](/assets/images/help/business-accounts/pay-invoice.png) + +### Descargar tu factura actual + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +4. Dabajo de "Acciones Rápidas", da clic en **Descargar factura actual**. ![Enlace de descarga de factura actual](/assets/images/help/business-accounts/download-current-invoice.png) + +### Ver tu historial de pagos + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +4. Debajo de "Facturación", da clic en **Facturas pasadas** para ver un resumen de tu actividad de facturación pasada. ![Pestaña de ver historial de pago](/assets/images/help/business-accounts/view-payment-history.png) + +{% endif %} diff --git a/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md new file mode 100644 index 0000000000000..7983692501029 --- /dev/null +++ b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md @@ -0,0 +1,72 @@ +--- +title: Administrar tu licencia de GitHub Enterprise +intro: 'Puedes ver, gestionar y actualizar tu licencia de {% data variables.product.prodname_enterprise %}.' +redirect_from: + - /enterprise/admin/installation/managing-your-github-enterprise-license + - /enterprise/admin/categories/licenses/ + - /enterprise/admin/articles/license-files/ + - /enterprise/admin/installation/about-license-files/ + - /enterprise/admin/articles/downloading-your-license/ + - /enterprise/admin/installation/downloading-your-license/ + - /enterprise/admin/articles/upgrading-your-license/ + - /enterprise/admin/installation/updating-your-license/ + - /enterprise/admin/installation/managing-your-github-enterprise-server-license + - /enterprise/admin/overview/managing-your-github-enterprise-license +versions: + enterprise-server: '*' +--- + +### Acerca de las licencias {% data variables.product.prodname_enterprise %} + +Cuando compras o renuevas {% data variables.product.prodname_enterprise %}, recibes un archivo de licencia para validar tu aplicación. Un archivo de licencia tiene una fecha de caducidad y controla la cantidad de licencias de usuario que puedes agregar a {% data variables.product.prodname_enterprise %}. Después de que hayas descargado e instalado {% data variables.product.prodname_enterprise %}, subir el archivo de licencia desbloquea la aplicación para que la puedas usar. + +Puedes asignar las licencias de usuario incluidas en tu licencia de {% data variables.product.prodname_enterprise %} a los usuarios en {% data variables.product.product_location_enterprise %} y en una cuenta empresarial de {% data variables.product.prodname_ghe_cloud %}. Cuando agregas un usuario a algún entorno, se consumirá una licencia. Si un usuario tiene cuentas en ambos ambientes, para consumir únicamente una licencia, su dirección de correo primaria de {% data variables.product.prodname_enterprise %} debe ser la misma que su dirección de correo verificada de {% data variables.product.prodname_ghe_cloud %}. Puedes sincronizar la cantidad de licencias y el uso entre los ambientes. + +Si tu licencia vence {% data variables.product.prodname_ghe_server %}, no podrás acceder a {% data variables.product.product_location_enterprise %} por medio de un navegador web o Git. Si es necesario, podrás usar herramientas de línea de comando para hacer un respaldo de seguridad de todos tus datos. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)" Si tienes cualquier duda sobre el renovamiento de tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}. + +### Subir una nueva licencia a {% data variables.product.prodname_ghe_server %} + +Después de que compras una nueva licencia o actualizas una licencia existente de {% data variables.contact.contact_enterprise_sales %}, debes descargar tu nuevo archivo de licencia. Posteriormente, carga el archivo a {% data variables.product.prodname_ghe_server %} para desbloquear tu nueva licencia de usuario. + +Si quisieras renovar o agregar licencias de usuario a {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.contact_enterprise_sales %}. El archivo de tu licencia nueva estará disponible para la descarga de forma inmediata después de que hayas completado tu orden. + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Debajo de "instancias de Enterprise Server", da clic en {% octicon "download" aria-label="The download icon" %} para descargar tu archivo de licencia. ![Descargar la licencia de GitHub Enterprise Server](/assets/images/help/business-accounts/download-ghes-license.png) +5. Ingresa en tu +instancia de {% data variables.product.prodname_ghe_server %} como administrador de sitio. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +12. Dentro de "Quick links (Vínculos rápidos)", haz clic en **Update license (Actualizar licencia)**. ![Actualizar enlace de la licencia](/assets/images/enterprise/business-accounts/update-license-link.png) +13. Para seleccionar tu licencia, da clic en **Archivo de licencia**, o arrastra tu archivo de licencia a **Archivo de licencia**. ![Sube el archivo de licencia](/assets/images/enterprise/management-console/upload-license.png) +14. Da clic en **Cargar**. ![Comienza la actualización](/assets/images/enterprise/management-console/begin-upload.png) + +### Ver el uso de la licencia + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Revisa tu licencia actual de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario utilizadas y disponibles. + +### Sincronizar de forma automática el uso de la licencia de usuario con {% data variables.product.prodname_ghe_cloud %} + +Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de las licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar la sincronización de licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)". + +### Sincronizar el uso de licencias de usuario manualmente entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} + +Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar el uso de la licencia de usuario entre dos implementaciones de forma manual. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +5. Debajo de "Enlaces rápidos", para descargar un archivo que contiene tu uso de licencia actual en +{% data variables.product.prodname_ghe_server %}, da clic en **Exportar uso de licencia**. + ![Exporta el vínculo de uso de la licencia](/assets/images/enterprise/business-accounts/export-license-usage-link.png) +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +8. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) +{% data reusables.enterprise-accounts.license-tab %} +10. Debajo de "Instancias de Enterprise Server", da clic en **Agregar uso del servidor**. ![Sube el vínculo de uso de los servidores de GitHub Enterprise](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) +11. Sube el archivo JSON que descargaste de {% data variables.product.prodname_ghe_server %}. ![Arrastra y suelta o selecciona un archivo para cargar](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) diff --git a/translations/es-ES/content/admin/overview/system-overview.md b/translations/es-ES/content/admin/overview/system-overview.md new file mode 100644 index 0000000000000..9b3328f4cfbed --- /dev/null +++ b/translations/es-ES/content/admin/overview/system-overview.md @@ -0,0 +1,142 @@ +--- +title: Descripción del sistema +intro: 'El {% data variables.product.prodname_ghe_server %} es la copia privada de tu organización de {% data variables.product.prodname_dotcom %} contenida dentro de un aparato virtual, alojada localmente o en la nube, que configuras y controlas.' +redirect_from: + - /enterprise/admin/installation/system-overview + - /enterprise/admin/overview/system-overview +versions: + enterprise-server: '*' +--- + +### Arquitectura de almacenamiento + +El {% data variables.product.prodname_ghe_server %} requiere dos volúmenes de almacenamiento, uno instalado en la ruta del *sistema de archivos raíz* (`/`) y otro en la ruta del *sistema de archivos del usuario* (`/data/user`). Esta arquitectura simplifica los procedimientos de actualización, reversión y recuperación al separar el entorno del software que se ejecuta de los datos de aplicación persistentes. + +El sistema de archivos raíz está incluido en la imagen de máquina distribuida. Contiene el sistema operativo base y el entorno de aplicación {% data variables.product.prodname_ghe_server %}. El sistema de archivos raíz debería tratarse como efímero. Cualquier dato en el sistema de archivos raíz será reemplazado cuando se actualice con futuros lanzamientos del {% data variables.product.prodname_ghe_server %}. + +El sistema de archivos raíz contiene: + - Los certificados de autoridad de certificación personalizados (CA) (en */usr/local/share/ca-certificates*) + - Las configuraciones de red personalizadas + - Las configuraciones de firewall personalizadas + - El estado de replicación + +El sistema de archivos del usuario contiene la configuración y los datos del usuario, tales como: + - Repositorios Git + - Bases de datos + - Índices de búsqueda + - Contenido publicado en los sitios {% data variables.product.prodname_pages %} + - Archivos grandes de {% data variables.large_files.product_name_long %} + - Entornos de enlaces de pre-recepción + +### Opciones de implementación + +Puedes implementar {% data variables.product.prodname_ghe_server %} como un aparato virtual único, o en una configuración de alta disponibilidad. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." + +Algunas organizaciones con decenas de miles de programadores podrían también beneficiarse de una Agrupación {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acerca de las agrupaciones](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)." + +### Retención de datos y redundancia de centro de datos + +{% danger %} + +Antes de usar {% data variables.product.prodname_ghe_server %} en un entorno de producción, recomendamos firmemente que configures copias de seguridad y un plan de recuperación ante desastres. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)". + +{% enddanger %} + +{% data variables.product.prodname_ghe_server %} incluye soporte para copias de seguridad en línea e incrementales con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). Puedes tomar instantáneas incrementales sobre un enlace de red seguro (el puerto administrativo SSH) sobre grandes distancias para el almacenamiento externo o geográficamente disperso. Puedes restaurar instantáneas a través de la red en un nuevo aparato virtual recientemente aprovisionado al momento de la recuperación en el caso de un desastre en el centro de datos principal. + +Además se admiten las copias de seguridad de red, las instantáneas de disco AWS (EBS) y VMware de los volúmenes de almacenamiento del usuario mientras que el aparato está fuera de línea o en modo mantenimiento. Las instantáneas de volumen regulares pueden usarse como una alternativa de bajo costo y baja complejidad para las copias de seguridad de red con {% data variables.product.prodname_enterprise_backup_utilities %} si tus requisitos de nivel de servicio permiten un mantenimiento fuera de línea regular. + +Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)". + +### Seguridad + +El {% data variables.product.prodname_ghe_server %} es un aparato virtual que se ejecuta en tu infraestructura y está gobernado por tus controles de seguridad de información existentes, como cortafuegos, IAM, monitoreo y VPN. Usar el {% data variables.product.prodname_ghe_server %} puede ayudarte a evitar problemas de cumplimiento regulatorio que surgen de las soluciones basadas en la nube. + +El {% data variables.product.prodname_ghe_server %} también incluye características de seguridad adicionales. + +- [Sistema operativo, software y parches](#operating-system-software-and-patches) +- [Seguridad de la red](#network-security) +- [Seguridad de la aplicación](#application-security) +- [Servicios externos y acceso de soporte](#external-services-and-support-access) +- [Comunicación encriptada](#encrypted-communication) +- [Usuarios y permisos de acceso](#users-and-access-permissions) +- [Autenticación](#authentication) +- [Auditoría y registro de acceso](#audit-and-access-logging) + +#### Sistema operativo, software y parches + +El {% data variables.product.prodname_ghe_server %} ejecuta un sistema operativo Linux personalizado con las aplicaciones y los servicios necesarios únicamente. El {% data variables.product.prodname_dotcom %} gestiona el parche del sistema operativo central del aparato como parte de su ciclo estándar de lanzamiento de productos. Los parches abordan problemas de funcionalidad, de estabilidad y de seguridad no críticos para las aplicaciones de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} también proporciona parches de seguridad críticos según se necesita fuera del ciclo de lanzamiento regular. + +#### Seguridad de la red + +El cortafuegos interno del {% data variables.product.prodname_ghe_server %} restringe el acceso de la red a los servicios del aparato. Están disponibles en la red únicamente los servicios necesarios para que el aparato funcione. Para obtener más información, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)." + +#### Seguridad de la aplicación + +El equipo de seguridad de la aplicación de {% data variables.product.prodname_dotcom %} se centra en la evaluación de vulnerabilidad, la prueba de penetración y la revisión del código para los productos de {% data variables.product.prodname_dotcom %} , incluido el {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} también contrata firmas de seguridad externas para proporcionar evaluaciones de seguridad puntuales de los productos de {% data variables.product.prodname_dotcom %}. + +#### Servicios externos y acceso de soporte + +El {% data variables.product.prodname_ghe_server %} puede funcionar sin ningún acceso de salida de tu red a servicios externos. De forma opcional, puedes habilitar la integración con servicios externos para la entrega de correo electrónico, el monitoreo externo y el reenvío de bitácoras. Para obtener más información, consulta las secciones "[Configurar las notificaciones por correo electrónico](/admin/configuration/configuring-email-for-notifications)", "[Configurar el monitoreo externo](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)", y "[Reenvío de bitácoras](/admin/user-management/log-forwarding)". + +Puedes recopilar y enviar manualmente datos de resolución de problemas a {% data variables.contact.github_support %}. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)." + +#### Comunicación encriptada + +{% data variables.product.prodname_dotcom %} diseña {% data variables.product.prodname_ghe_server %} para ejecutar detrás de tu cortafuegos corporativo. Para asegurar la comunicación a través del cable, te alentamos a habilitar la seguridad de la capa de transporte (TLS). El {% data variables.product.prodname_ghe_server %} admite certificados TLS comerciales de 2048 bits y superiores para el tráfico HTTPS. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)." + +Por defecto, el aparato también ofrece acceso a Secure Shell (SSH) para el acceso al repositorio utilizando Git y con fines administrativos. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." + +#### Usuarios y permisos de acceso + +El {% data variables.product.prodname_ghe_server %} proporciona tres tipos de cuentas. + +- La cuenta de usuario de Linux del `administrador` ha controlado el acceso al sistema operativo subyacente, incluido el sistema de archivos directo y el acceso a la base de datos. Un pequeño conjunto de administradores de confianza debería tener acceso a esta cuenta, a la que pueden acceder por medio de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." +- Las cuentas de usuario en la aplicación web del aparato tienen acceso completo a sus propios datos y a cualquier dato que otros usuarios u organizaciones concedan de manera explícita. +- Los administradores del sitio en la aplicación web del aparato son cuentas de usuario que pueden administrar los ajustes de aplicaciones web y de aparatos de alto nivel, la configuración de cuenta de usuario y de organización y los datos del repositorio. + +Para más información sobre los permisos de usuario del {% data variables.product.prodname_ghe_server %}, consulta "[Permisos de acceso en GitHub](/enterprise/user/articles/access-permissions-on-github)." + +#### Autenticación + +El {% data variables.product.prodname_ghe_server %} proporciona cuatro métodos de autenticación. + +- La autenticación de claves públicas SSH proporciona acceso del repositorio usando Git y el shell administrativo. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." +- El nombre de usuario y la autenticación de contraseña con cookies HTTP proporciona acceso a la aplicación web y la gestión de sesiones, con autenticación opcional de dos factores (2FA). Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)." +- La autenticación externa LDAP, SAML o CAS mediante un servicio LDAP, SAML Identity Provider (IdP) u otro servicio compatible proporciona acceso a la aplicación web. Para más información, consulta "[Autenticar usuarios para tu instancia de servidor de GitHub Enterprise](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)." +- OAuth y los token de acceso personal proporcionan acceso a los datos del repositorio de Git y a API para clientes externos y servicios. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +#### Auditoría y registro de acceso + +El {% data variables.product.prodname_ghe_server %} almacena tanto registros tradicionales de sistema operativo como de aplicación. La aplicación también escribe registros de auditoría y de seguridad detallados, que el {% data variables.product.prodname_ghe_server %} almacena de forma permanente. Puedes reenviar ambos tipos de registros en tiempo real a múltiples destinos a través del protocolo `syslog-ng`. Para obtener más información, consulta la sección "[Reenvío de bitácoras](/admin/user-management/log-forwarding)". + +Los registros de acceso y de auditoría incluyen información como la siguiente. + +##### Registros de acceso + +- Registros completos de servidor web tanto para el navegador como para el acceso a la API +- Registros completos para acceder a los datos del repositorio por medio de protocolos Git, HTTPS y SSH +- Registros de acceso administrativo por medio de HTTPS y SSH + +##### Registros de auditoría + +- Inicios de sesión del usuario, restablecimientos de contraseña, solicitudes 2FA, cambios en la configuración del correo electrónico y cambios en aplicaciones autorizadas y API +- Acciones de administrador del sitio, como desbloquear cuentas de usuario y repositorios +- Eventos push de repositorio, permisos de acceso, transferencias y renombres +- Cambios de membresía de la organización, incluida la creación y la destrucción de equipo + +### Dependencias de código abierto para {% data variables.product.prodname_ghe_server %} + +Puedes consultar una lista completa de dependencias en la versión de tu aparato de {% data variables.product.prodname_ghe_server %}, y la licencia de cada proyecto, en `http(s)://HOSTNAME/site/credits`. + +Están disponibles en tu aparato los tarballes con una lista completa de dependencias y metadatos asociados: +- Para conocer las dependencias comunes a todas las plataformas, ingresa en `/usr/local/share/enterprise/dependencies--base.tar.gz`. +- Para conocer las dependencias específicas de una plataforma, ingresa en `/usr/local/share/enterprise/dependencies--.tar.gz`. + +También están disponibles los tarballes, con una lista completa de las dependencias y los metadatos, en `https://enterprise.github.com/releases//download.html`. + +### Further reading + +- "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" +- "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)" +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..5b1289d0a515f --- /dev/null +++ b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. Para obtener más información, consulta la sección "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)". +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. Debajo de "Alternación de ecosistema", para cada tipo de paquete, selecciona **Enabled**, **Read-Only**, o **Disabled**. ![Alternación de ecosistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| Source | Destination | Port (Puerto) | Type | +| -------------------------------------------------- | -------------------- | ------------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### Pasos siguientes + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..b4416b0b2c69d --- /dev/null +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Advertencias:** +- It is critical that you configure any restrictive access policies you need 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 to 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. +- Te recomendamos utilizar un bucket dedicado para {% data variables.product.prodname_registry %}, separado de aquél que utilices para almacenar {% data variables.product.prodname_actions %}. +- Asegúrate de configurar el bucket que quieres utilizar en el futuro. No te recomendamos cambiar tu almacenamiento después de que comienzas a utilizar {% data variables.product.prodname_registry %}. + +{% endwarning %} + +### Prerrequisitos + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Debajo de "AWS Service URL", teclea la URL de la terminal de S3 para la región de tu espacio. ![Campo de URL de servicio de AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Debajo de "AWS S3 Bucket", teclea el nombre del espacio de S3 que quieras utilizar para almacenar artefactos de los paquetes. ![Campo de espacio de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Debajo de "AWS S3 Access Key", teclea tu clave de acceso para S3. ![Campo de clave de acceso de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Debajo de "AWS S3 Secret Key", teclea tu clave secreta para S3. ![Campo de clave secreta de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Debajo de "AWS S3 Region", teclea tu región para S3. ![Campo de región de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Pasos siguientes + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..5fc2045680c20 --- /dev/null +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**Advertencias:** +- It is critical that you set the restrictive access policies you need 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. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos. +- Te recomendamos utilizar un bucket dedicado para {% data variables.product.prodname_registry %}, separado de aquél que utilices para almacenar {% data variables.product.prodname_actions %}. +- Asegúrate de configurar el bucket que quieres utilizar en el futuro. No te recomendamos cambiar tu almacenamiento después de que comienzas a utilizar {% data variables.product.prodname_registry %}. + +{% endwarning %} + +### Prerrequisitos + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### Pasos siguientes + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..4f46c8542b644 --- /dev/null +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Advertencias:** +- It is critical that you set the restrictive access policies you need 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. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos. +- Te recomendamos utilizar un bucket dedicado para {% data variables.product.prodname_registry %}, separado de aquél que utilices para almacenar {% data variables.product.prodname_actions %}. +- Asegúrate de configurar el bucket que quieres utilizar en el futuro. No te recomendamos cambiar tu almacenamiento después de que comienzas a utilizar {% data variables.product.prodname_registry %}. + +{% endwarning %} +### Prerrequisitos +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![Campo de URL de servicio de AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![Campo de espacio de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![Campo de clave de acceso de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![Campo de clave secreta de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![Campo de región de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Pasos siguientes + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..58ad9273f1efe --- /dev/null +++ b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_registry %} en {% data variables.product.prodname_ghe_server %} utiliza almacenamiento externo de blobs para almacenar tus paquetes. + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Asegúrate de que cada URL de host de paquete incluya `https://`. + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. Para obtener más información acerca de las URL del host de los paquetes, consulta "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obtener más información sobre cómo cargar certificados TLS a {% data variables.product.product_name %}, consulta la sección "[Configurar el TLS](/enterprise/admin/configuration/configuring-tls)". diff --git a/translations/es-ES/content/admin/packages/index.md b/translations/es-ES/content/admin/packages/index.md new file mode 100644 index 0000000000000..d91a3b3d5932c --- /dev/null +++ b/translations/es-ES/content/admin/packages/index.md @@ -0,0 +1,19 @@ +--- +title: Administrar GitHub Packages para tu empresa +intro: 'Puedes habilitar {% data variables.product.prodname_registry %} para tu empresa y administrar la configuración y los tipos de paquetes permitidos de {% data variables.product.prodname_registry %}.' +redirect_from: + - /enterprise/admin/packages +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..1c7bdd3f85319 --- /dev/null +++ b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Antes de que puedas habilitar y configurar el {% data variables.product.prodname_registry %} en {% data variables.product.product_location_enterprise %}, deberás preparar tu solución de almacenamiento externo. + +MinIO ofrece almacenamiento de objetos con soporte para la API de S3 y para {% data variables.product.prodname_registry %} en tu empresa. + +Esta guía de inicio rápido te muestra cómo configurar MinIO utilizando Docker para usarlo con el {% data variables.product.prodname_registry %}, peto tienes otras opciones para administrar MinIO aparte de Docker. Para obtener más información acerca de MinIO, consulta los [documentos oficiales de MinIO](https://docs.min.io/). + +### 1. Elige un modo de MinIO de acuerdo con tus necesidades + +| Modo de MinIO | Optimizado para | Infraestructura de almacenamiento requerida | +| -------------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------- | +| MinIO Autónomo (en un solo host) | Configuración rápida | N/A | +| MinIO como una puerta de enlace de NAS | NAS (Almacenamiento adjunto a la red, por sus siglas en inglés) | Dispositivos NAS | +| MinIO Agrupado (también conocido como MinIO distribuído) | Seguridad de datos | Servidores de almacenamiento que se ejecutan en un agrupamiento | + +Para obtener más información acerca las opciones que tienes, consulta los [documentos oficiales de MinIO](https://docs.min.io/). + +### 2. Instala, ejecuta e inicia sesión en MinIO + +1. Configura tus variables de ambiente preferidas para MinIO. + + Estos ejemplos utilizan `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Instala MinIO. + + ```shell + $ docker pull minio/minio + ``` + Para obtener más información, consulta la [Guía de inicio rápido oficial de MinIO](https://docs.min.io/docs/minio-quickstart-guide)". + +3. Inicia sesión en MinIO utilizando tu llave de acceso y secreto de MinIO. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + Puedes acceder a tus llaves de MinIO utilizando las variables de ambiente: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Ejecuta MinIO en el modo que hayas elegido. + + * Ejecuta MinIO utilizando Docker en un host único: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + Para obtener más información, consulta la "[Guía de inicio rápido de Docker para MinIO](https://docs.min.io/docs/minio-docker-quickstart-guide.html)". + + * Ejecuta MinIO utilizando Docker como una puerta de enlace de NAS: + + Esta configuración es útil para los despliegues en donde ya exista una NAS que quieras utilizar como respaldo de almacenamiento para el {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + Para obtener más información, consulta la sección "[Puerta de enlace de MinIO para NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)". + + * Ejecuta MinIO utilizando Docker como un agrupamiento. Este despliegue de MinIO utiliza diversos hosts y el código de borrado de MinIO para tener la mayor protección de los datos. Para ejecutar MinIO en modo de agrupamiento, consulta la "[Guía Rápida para MinIO Distribuído](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Crea tu bucket de MinIO para {% data variables.product.prodname_registry %} + +1. Instala el cliente de MinIO. + + ```shell + $ docker pull minio/mc + ``` + +2. Crea un bucket con una URL de host a la que {% data variables.product.prodname_ghe_server %} pueda acceder. + + * Ejemplos de despliegues locales: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + Este ejemplo puede utilizarse para la versión autónoma de MinIO o para MinIO como puerta de enlace de NAS. + + * Ejemplo de despliegues en agrupamiento: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### Pasos siguientes + +Para terminar de configurar el almacenamiento para el {% data variables.product.prodname_registry %}, necesitarás copiar la URL de almacenamiento de MinIO: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md b/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md new file mode 100644 index 0000000000000..8ffd1a17bee23 --- /dev/null +++ b/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md @@ -0,0 +1,26 @@ +--- +title: Acerca de ganchos de pre-recepción +intro: 'Los *ganchos de pre-recepción* son scripts que se ejecutan en el aparato {% data variables.product.prodname_ghe_server %} que puedes usar para implementar controles de calidad.' +redirect_from: + - /enterprise/admin/developer-workflow/about-pre-receive-hooks + - /enterprise/admin/policies/about-pre-receive-hooks +versions: + enterprise-server: '*' +--- + +Cuando se produce una subida, cada script se ejecuta en un entorno aislado y puede realizar verificaciones en el contenido que se subió. Los scripts provocarán la aceptación de la subida si el estado de salida es 0, o rechazado si el estado de salida no es cero. + +### Escenarios de uso +Usa los ganchos de pre-recepción para satisfacer las reglas comerciales, implementar el cumplimiento regulatorio y prevenir determinados errores comunes. + +Ejemplos de cómo usar los ganchos de pre-recepción: + +- Requerir mensajes de confirmación para seguir un patrón o formato específico, como incluir un número de ticket válido o finalizar luego de una determinada duración. +- Buscar una rama o repositorio al rechazar todas las subidas. +- Impedir que se agreguen datos sensibles al repositorio al bloquear palabras clave, patrones o tipos de archivo. +- Impedir que un autor PR se fusione con sus propios cambios. + +### Impactar en el rendimiento y los flujos de trabajo flujo de trabajo +El impacto que causa en los programadores y sus flujos de trabajo puede ser significativo y debe considerarse cuidadosamente. Los ganchos de pre-recepción que se basan en necesidades comerciales y se implementan cuidadosamente brindarán la mayor cantidad de beneficios a la organización en conjunto. + +Los ganchos de pre-recepción pueden tener efectos no deseados sobre el rendimiento de {% data variables.product.product_location %} y deberían implementarse y revisarse cuidadosamente. diff --git a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md new file mode 100644 index 0000000000000..16ea1e557a27d --- /dev/null +++ b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md @@ -0,0 +1,92 @@ +--- +title: Crear un entorno de gancho de pre-recepción +intro: 'Para ejecutar los ganchos de pre-recepción, usa el entorno de pre-recepción predeterminado o crea un entorno personalizado.' +redirect_from: + - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-environment + - /enterprise/admin/policies/creating-a-pre-receive-hook-environment +versions: + enterprise-server: '*' +--- + +Un entorno de pre-recepción para {% data variables.product.prodname_ghe_server %} es un entorno Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot). Dado que los ganchos de pre-recepción se ejecutan en todos los eventos de extracción, deberían ser rápidos y livianos. Normalmente, el entorno necesario para tales verificaciones será mínimo. + +{% data variables.product.prodname_ghe_server %} brinda un entorno predeterminado que incluye estos paquetes: `awk`, `bash`, `coreutils`, `curl`, `find`, `gnupg`, `grep`, `jq`, `sed`. + +Si tu entorno no cumple con uno de los requisitos específicos, como respaldo para un idioma en particular, puedes crear y cargar tu propio entorno `chroot` en Linux de 64 bits. + +### Crear un entorno de gancho de pre-recepción mediante Docker + +Puedes usar una herramienta de administración de contenedores de Linux para crear un entorno de gancho de pre-recepción. Este ejemplo usa [Alpine Linux](http://www.alpinelinux.org/) y [Docker](https://www.docker.com/). + +{% data reusables.linux.ensure-docker %} +2. Crea el archivo `Dockerfile.alpine-3.3` que contiene esta información: + + ``` + FROM gliderlabs/alpine:3.3 + RUN apk add --no-cache git bash + ``` +3. Desde el directorio de trabajo que contiene `Dockerfile.dev`, crea una imagen: + + ```shell + $ docker build -f Dockerfile.alpine-3.3 -t pre-receive.alpine-3.3 . + > Sending build context to Docker daemon 12.29 kB + > Step 1 : FROM gliderlabs/alpine:3.3 + > ---> 8944964f99f4 + > Step 2 : RUN apk add --no-cache git bash + > ---> Using cache + > ---> 0250ab3be9c5 + > Successfully built 0250ab3be9c5 + ``` +4. Crea un contenedor: + + ```shell + $ docker create --name pre-receive.alpine-3.3 pre-receive.alpine-3.3 /bin/true + ``` +5. Exporta el contenedor Docker a un archivo `tar` comprimido como `gzip`: + + ```shell + $ docker export pre-receive.alpine-3.3 | gzip > alpine-3.3.tar.gz + ``` + + Este archivo `alpine-3.3.tar.gz` está listo para subirse al aparato {% data variables.product.prodname_ghe_server %}. + +### Crear un entorno de gancho de pre-recepción mediante chroot + +1. Crea un entorno `chroot` en Linux. +2. Crea un archivo `tar` comprimido como `gzip` del directorio `chroot`. + ```shell + $ cd /path/to/chroot + $ tar -czf /path/to/pre-receive-environment.tar.gz . + ``` + + {% note %} + + **Notas:** + - No incluyas las rutas iniciales del directorio en los archivos dentro del tar, tales como `/path/to/chroot`. + - La ruta `/bin/sh` debe existir y ser ejecutable como punto de entrada al ambiente chroot. + - A diferencia de los chroots tradicionales, el ambiente de chroot para ganchos de pre-recepción no requiere el directorio `dev`. + + {% endnote %} + +Para obtener más información acerca de la creación de un entorno chroot, consulta "[Chroot](https://wiki.debian.org/chroot)" desde *Debian Wiki*, "[BasicChroot](https://help.ubuntu.com/community/BasicChroot)" desde *Ubuntu Community Help Wiki* o "[Instalar Alpine Linux en un chroot](http://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot)" desde *Alpine Linux Wiki*. + +### Cargar un entorno de pre-recepción en {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Haz clic en **Manage environments** (Administrar entornos). ![Administrar entornos](/assets/images/enterprise/site-admin-settings/manage-pre-receive-environments.png) +6. Haz clic en **Add environment** (Agregar entorno). ![Agregar entorno](/assets/images/enterprise/site-admin-settings/add-pre-receive-environment.png) +7. Escribe el nombre que desees en el campo **Environment name** (Nombre del entorno). ![Nombre del entorno](/assets/images/enterprise/site-admin-settings/pre-receive-environment-name.png) +8. Escribe la URL del archivo `*.tar.gz` que contiene tu entorno. ![Cargar un entorno desde una URL](/assets/images/enterprise/site-admin-settings/upload-environment-from-url.png) +9. Haz clic en **Add environment** (Agregar entorno). ![Agregar el botón de entorno](/assets/images/enterprise/site-admin-settings/add-environment-button.png) + +### Cargar un entorno de pre-recepción mediante el shell administrativo +1. Carga un archivo `*.tar.gz` legible que contenga tu entorno a un host web y copia la URL o transfiere el archivo al aparato del {% data variables.product.prodname_ghe_server %} mediante `scp`. Al usar `scp`, es posible que necesites ajustar los permisos del archivo `*.tar.gz` para que todos puedan leerlo. +1. Conecta con el shell administrativo. +2. Usa el comando `ghe-hook-env-create` y escribe el nombre que desees para el entorno como primer argumento y la ruta local completa o la dirección URL de un archivo `*.tar.gz` que contenga tu entorno como segundo argumento. + + ```shell + admin@ghe-host:~$ ghe-hook-env-create AlpineTestEnv /home/admin/alpine-3.3.tar.gz + > Pre-receive hook environment 'AlpineTestEnv' (2) has been created. + ``` diff --git a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md new file mode 100644 index 0000000000000..79afed7e7f946 --- /dev/null +++ b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -0,0 +1,201 @@ +--- +title: Crear un script de ganchos de pre-recepción +intro: Usa los scripts de los ganchos de pre-recepción para crear requisitos para aceptar o rechazar una subida en función de los contenidos. +redirect_from: + - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script + - /enterprise/admin/policies/creating-a-pre-receive-hook-script +versions: + enterprise-server: '*' +--- + +Puedes ver los ejemplos de los ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} en el repositorio [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). + +### Escribir un script de ganchos de pre-recepción +Un script de gancho de pre-recepción se ejecuta en un entorno de gancho de pre-recepcion en el aparato {% data variables.product.prodname_ghe_server %}. Cuando crees un script de gancho de pre-recepción, considera la entrada, salida, el estado de salida y las variables de entorno. + +#### Entrada (stdin) +Después de que se produce la subida y antes de que las ref se actualicen en el repositorio remoto, el proceso `git-receive-pack` invoca el script del gancho de pre-recepción con la entrada estándar de una línea por ref que se actualizará: + +` SP SP LF` + +Esta cadena representa estos argumentos: + +| Argumento | Descripción | +|:------------------- |:-------------------------------------------------------------------------------------------------------------------- | +| `` | Nombre del objeto antiguo almacenado en la `ref`.
    Cuando *creas* una nueva`ref`, esto equivale a 40 ceros. | +| `` | El nombre del objeto nuevo se almacenará en la `ref`.
    Cuando *eliminas* una `ref`, equivale a 40 ceros. | +| `` | El nombre completo de la `ref`. | + +Para obtener más información sobre `git-receive-pack`, consulta "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" en la documentación de Git. Para obtener más información sobre `refs`, consulta "[Referencias de Git](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" en *Pro Git*. + +#### Salida (stdout) + +La salida del script (`stdout`) se vuelve a pasar al cliente, de manera que los enunciados `eco` estén visibles para el usuario en la línea de comando o en la interfaz del usuario. + +#### Estado de salida + +El `estado de salida` de un script de pre-recepción determina si la subida se aceptará. + +| Valor del estado de salida | Acción | +|:--------------------------:|:-------------------------:| +| 0 | La subida será aceptada. | +| no cero | La subida será rechazada. | + +#### Variables del entorno +Fuera de los valores que se brindan a `stdin`, existen variables adicionales que están disponibles para un script de gancho de pre-recepción en {% data variables.product.prodname_ghe_server %}. + +| Variable | Descripción | +|:------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| $GITHUB_USER_LOGIN | El id de usuario que creó el `ref`. | +| $GIT_DIR | La ruta del repositorio remoto en el aparato. | +| $GITHUB_USER_IP | La dirección IP del usuario que realiza la subida. | +| $GITHUB_REPO_NAME | El nombre en el formato `owner`/`repo` del repositorio que se actualiza. | +| $GITHUB_PULL_REQUEST_AUTHOR_LOGIN | El ID de usuario para el autor de una solicitud de extracción en tu instancia. | +| $GITHUB_REPO_PUBLIC | Un valor booleano que cuando `true` representa un repositorio público, y cuando `false` representa un repositorio privado. | +| $GITHUB_PUBLIC_KEY_FINGERPRINT | La huella digital de clave pública del usuario. | +| $GITHUB_PULL_REQUEST_HEAD | Una cadena en el formato: `user:branch` para el HEAD del PR.
    Ejemplo: `octocat:fix-bug` | +| $GITHUB_PULL_REQUEST_BASE | Una secuencia en el formato: `user:branch` para la BASE de la Solicitud de Extracción.
    Ejemplo: `octocat:main` | +| $GITHUB_VIA | Método usado para crear la ref.
    **Valores posibles:**
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | +| $GIT_PUSH_OPTION_COUNT | El número de opciones de extracción que envió el cliente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. | +| $GIT_PUSH_OPTION_N | Where N is an integer starting at 0, this variable contains the push option string that was sent by the client. La primera opción que se envió se almacenó en GIT_PUSH_OPTION_0, la segunda opción que se envió se almacenó en GIT_PUSH_OPTION_1, y así sucesivamente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. |{% if currentVersion ver_gt "enterprise-server@2.21" %} +| $GIT_USER_AGENT | La secuencia de usuario-agente que envió el cliente que subió los cambios. |{% endif %} + +### Establecer permisos y subidas a un ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} + +Un script de gancho de pre-recepción se encuentra en un repositorio en el aparato {% data variables.product.prodname_ghe_server %}. Un administrador del sitio debe tener en cuenta los permisos del repositorio y garantizar que solo los usuarios correspondientes tengan acceso. + +Recomendamos los ganchos de consolidación a un solo repositorio. Si el repositorio de gancho consolidado es público, `README.md` puede usarse para explicar los cumplimientos de la política. Además, las contribuciones pueden aceptarse mediante solicitudes de extracción. Sin embargo, los ganchos de pre-recepción solo pueden agregarse desde la rama por defecto. Para un flujo de trabajo de prueba, se deben usar las bifurcaciones del repositorio con la configuración. + +1. Para usuarios de Mac, asegúrate de que los scripts tengan permisos de ejecución: + + ```shell + $ sudo chmod +x SCRIPT_FILE.sh + ``` + Para usuarios de Windows, asegúrate de que los scripts tengan permisos de ejecución: + + ```shell + git update-index --chmod=+x SCRIPT_FILE.sh + ``` + +2. Confirmar y subir a tus repositorio de ganchos pre-recibidos en la instancia {% data variables.product.prodname_ghe_server %}. + + ```shell + $ git commit -m "YOUR COMMIT MESSAGE" + $ git push + ``` + +3. [Crear la instancia de ganchos de pre-recepción](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %}. + +### Probar scripts de pre-recepción localmente +Puedes probar un script de gancho de pre-recepción localmente antes de crear o actualizar en tu aparato {% data variables.product.prodname_ghe_server %}. Un método es crear un entorno de Docker local para que actúe como un repositorio remoto que pueda ejecutar el gancho de pre-recepción. + +{% data reusables.linux.ensure-docker %} + +2. Crear un archivo denominado `Dockerfile.dev` que contenga: + + ``` + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" + + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git + + CMD ["/usr/sbin/sshd", "-D"] + ``` + +3. Crear un script de pre-recepción de prueba denominado `always_reject.sh`. Este script del ejemplo rechazará todas las subidas, lo cual es útil para bloquear un repositorio: + + ``` + #!/usr/bin/env bash + + echo "error: rejecting all pushes" + exit 1 + ``` + +4. Asegúrate de que los scripts `always_reject.sh` tengan permisos de ejecución: + + ```shell + $ chmod +x always_reject.sh + ``` + +5. Desde el directorio que contiene `Dockerfile.dev`, crea una imagen: + + ```shell + $ docker build -f Dockerfile.dev -t pre-receive.dev . + > Sending build context to Docker daemon 3.584 kB + > Step 1 : FROM gliderlabs/alpine:3.3 + > ---> 8944964f99f4 + > Step 2 : RUN apk add --no-cache git openssh bash && ssh-keygen -A && sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && adduser git -D -G root -h /home/git -s /bin/bash && passwd -d git && su git -c "mkdir /home/git/.ssh && ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P ' && mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && mkdir /home/git/test.git && git --bare init /home/git/test.git" + > ---> Running in e9d79ab3b92c + > fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz + > fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz + ....truncated output.... + > OK: 34 MiB in 26 packages + > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 + > Password for git changed by root + > Generating public/private ed25519 key pair. + > Your identification has been saved in /home/git/.ssh/id_ed25519. + > Your public key has been saved in /home/git/.ssh/id_ed25519.pub. + ....truncated output.... + > Initialized empty Git repository in /home/git/test.git/ + > Successfully built dd8610c24f82 + ``` + +6. Ejecutar un contenedor de datos que contiene una clave SSH generada: + + ```shell + $ docker run --name data pre-receive.dev /bin/true + ``` + +7. Copiar el ganchos de pre-recepción de prueba `always_reject.sh` en el contenedor de datos: + + ```shell + $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive + ``` + +8. Poner en marcha un contenedor de la aplicación que corre `sshd` y ejecuta el gancho. Toma nota del id del contenedor que se devolvió: + + ```shell + $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev + > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58 + ``` + +9. Copilar la clave SSH generada desde el contenedor de datos hasta la máquina local: + + ```shell + $ docker cp data:/home/git/.ssh/id_ed25519 . + ``` + +10. Modificar el remoto de un repositorio de prueba y subirlo al repositorio `test.git` dentro del contenedor Docker. Este ejemplo usa `git@github.com:octocat/Hello-World.git` pero puedes usar cualquier repositorio que desees. Este ejemplo asume que tu máquina local (127.0.01) es el puerto vinculante 52311, pero puedes usar una dirección IP diferente si el docker está ejecutándose en una máquina remota. + + ```shell + $ git clone git@github.com:octocat/Hello-World.git + $ cd Hello-World + $ git remote add test git@127.0.0.1:test.git + $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_ed25519" git push -u test main + > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts. + > Counting objects: 7, done. + > Delta compression using up to 4 threads. + > Compressing objects: 100% (3/3), done. + > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done. + > Total 7 (delta 0), reused 7 (delta 0) + > remote: error: rejecting all pushes + > To git@192.168.99.100:test.git + > ! [remote rejected] main -> main (pre-receive hook declined) + > error: failed to push some refs to 'git@192.168.99.100:test.git' + ``` + + Observa que la subida fue rechazada después de ejecutar el ganchos de pre-recepción y de hace eco la salida del script. + +### Further reading + - "[Personalizar Git - Un ejemplo de la política activa de Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" desde el *sitio web de Pro Git* diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md new file mode 100644 index 0000000000000..f2439cea28cd9 --- /dev/null +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md @@ -0,0 +1,10 @@ +--- +title: Requerir políticas para tu empresa +mapTopic: verdadero +redirect_from: + - /enterprise/admin/policies/enforcing-policies-for-your-enterprise +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md new file mode 100644 index 0000000000000..5d1237c55c427 --- /dev/null +++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md @@ -0,0 +1,11 @@ +--- +title: Requerir políticas para los ganchos de pre-recepción +intro: Usar ganchos de pre-recepción para implementar estándares de flujo de trabajo dentro de tu organización. Los ganchos de pre-recepción requieren un código para aprobar un conjunto de verificaciones de calidad predefinido antes de que la extracción sea aceptada en el repositorio. +mapTopic: verdadero +redirect_from: + - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy + - /enterprise/admin/policies/enforcing-policy-with-pre-receive-hooks +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md new file mode 100644 index 0000000000000..51cf021384fe9 --- /dev/null +++ b/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md @@ -0,0 +1,227 @@ +--- +title: Requerir políticas de administración de repositorios en tu empresa +intro: 'Los propietarios de empresas pueden hacer cumplir determinadas políticas de administración de repositorios para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que las políticas se establezcan en cada organización.' +redirect_from: + - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance + - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility + - /enterprise/admin/user-management/preventing-users-from-changing-a-repositorys-visibility + - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance + - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories + - /enterprise/admin/installation/setting-git-push-limits + - /enterprise/admin/guides/installation/git-server-settings/ + - /enterprise/admin/articles/setting-git-push-limits/ + - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories + - /enterprise/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories + - /enterprise/admin/developer-workflow/blocking-force-pushes-on-your-appliance + - /enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization + - /enterprise/admin/developer-workflow/blocking-force-pushes-to-a-repository + - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance/ + - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository/ + - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access + - /enterprise/admin/articles/blocking-force-pushes-to-a-repository/ + - /enterprise/admin/articles/block-force-pushes/ + - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account/ + - /enterprise/admin/articles/blocking-force-pushes-for-an-organization/ + - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization/ + - /enterprise/admin/developer-workflow/blocking-force-pushes + - /enterprise/admin/policies/enforcing-repository-management-policies-in-your-enterprise +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Configurar la visibilidad predeterminada para los repositorios nuevos en tu empresa + +Cada vez que alguien crea un repositorio nuevo en tu empresa, esta persona debe elegir una visibilidad para el mismo. Cuando configuras una visibilidad predeterminada para la empresa, eliges qué vsibilidad se seleccina predeterminadamente. Para obtener más información sobre los tipos de visibilidad para los repositorios, visita "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +Si un propietario de empresa deja de permitir que los miembros de ésta creen ciertos tipos de repositorios, estos no podrán crear este tipo de repositorio aún si la configuración de visibilidad lo tiene como predeterminado. Para obtener más información, consulta la sección "[Configurar una política para la creación de repositorios](#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" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +1. Debajo de "Default repository visibility" (visibilidad predeterminada del repositorio), utiliza el menú desplegable y selecciona un tipo de visibilidad predeterminado. ![Menú desplegable para elegir la visibilidad predeterminada de los repositorios para tu empresa](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) + +{% data reusables.enterprise_installation.image-urls-viewable-warning %} + +### Configurar una política para cambiar la visibilidad de un repositorio + +Cuando no permites que los miembros cambien la visibilidad del repositroio, únicamente los propietarios de la empresa podrán hacerlo. + +Si un propietario de empresa restringió la creación de repositorios en la misma para que solo los propietarios puedan realizar esta operación, entonces los miembros no podrán cambiar la visibilidad de los repositorios. Si un propietario de una empresa restringe la creación de repositorios para que los miembros solo puedan crear repositorios privados, entonces éstos solo podrán cambiar la visibilidad de un repositorio a privada. Para obtener más información, consulta la sección "[Configurar una política para la creación de repositorios](#setting-a-policy-for-repository-creation)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.repositories-tab %} +5. En "Modificar visibilidad del repositorio", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} + +{% data reusables.enterprise-accounts.repository-visibility-policy %} + +### Configurar una política para la creación de repositorios + +{% data reusables.organizations.repo-creation-constants %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.repositories-tab %} +5. En "Creación de repositorio", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.repo-creation-policy %} +{% data reusables.enterprise-accounts.repo-creation-types %} +{% else %} +6. En "Creación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con políticas para creación de repositorio](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png) +{% endif %} + +### Requerir una política para bifurcar repositorios privados o internos + +En todas las organizaciones que pertenezcan a tu empresa, puedes permitir o prohibir la bifurcación de un repositorio privado o interno o permitir a los propietarios administrar la configuración a nivel organizacional para todos los que tengan acceso a éstos. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Bifurcación de repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +4. En "Bifurcación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de bifurcación de repositorios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png) + +### Configurar una política para el borrado y transferencia de repositorios + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.repositories-tab %} +5. En "Transferencia y eliminación de repositorios", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} + +{% data reusables.enterprise-accounts.repository-deletion-policy %} + +### Configurar una política para los límites de subida de Git + +Para que el tamaño de tu repositorio se mantenga en una cantidad administrable y puedas prevenir los problemas de rendimiento, puedes configurar un límite de tamaño de archivo para los repositorios de tu empresa. + +Cuando impones límites de carga a los repositorios, la configuración predeterminada no permite a los usuarios añadir o actualizar archivos mayores a 100 MB. + +{% if currentVersion ver_lt "enterprise-server@2.20" %} +{% tip %} + +**Nota:** únicamente los archivos mayores a {% data variables.large_files.warning_size %} se revisarán frente al límite de subida de Git. Si debes establecer un límite de subida menor, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda. + +{% endtip %} +{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. Dentro de "Repository upload limit (Límite de subida del repositorio)", utiliza el menú desplegable y haz clic en un tamaño máximo de objeto. ![Menú desplegable con opciones de tamaño máximo de objeto](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png) +5. Opcionalmente, para requerir un límite de carga máximo para todos los repositorios en tu empresa, selecciona **Requerir en todos los repositorios** ![Opción para imponer tamaño máximo de objetos en todos los repositorios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) + +### Configurar el editor de fusión de conflictos para solicitudes de extracción entre repositorios + +Solicitarles a los usuarios que resuelvan los conflictos de fusión en forma local desde sus computadoras puede evitar que las personas escriban inadvertidamente un repositorio ascendente desde una bifurcación. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +1. En "Editor de conflicto para las solicitudes de extracción entre repositorios", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). ![Menú desplegable con opción para inhabilitar el editor de conflicto de fusión](/assets/images/enterprise/settings/conflict-editor-settings.png) + +### Configurar las cargas forzadas + +Cada repositorio hereda una configuración de empuje forzado por defecto desde la configuración de la cuenta del usuario o la organización a la que pertenece. De la misma forma, cada cuenta de organización y de usuario hereda una configuración de subidas forzadas de aquella de la empresa. Si cambias esta configuración para la empresa, se cambiará en todos los repositorios que le pertenezcan a cualquier usuario u organización dentro de ella. + +#### Bloquear las cargas forzadas en tu aplicativo + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. Debajo de "Force pushes" (Empujes forzados), usa el menú desplegable y haz clic en **Allow** (Permitir), **Block** (Bloquear) o **Block to the default branch** (Bloquear en la rama predeterminada). ![Forzar empujes desplegables](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png) +5. Opcionalmente, selecciona **Enforce on all repositories** (Implementar en todos los repositorios) que sobrescribirán las configuraciones a nivel de la organización y del repositorio para los empujes forzados. + +#### Bloquear las cargas forzadas para un repositorio específico + +{% data reusables.enterprise_site_admin_settings.override-policy %} + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +4. Selecciona **Block** (Bloquear) o **Block to the default branch** (Bloquear en la rama predeterminada) debajo de **Push and Pull** (Subir y extraer). ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png) + +#### Bloquear empujes forzados a los repositorios que posee una cuenta de usuario u organización + +Los repositorios heredan los parámetros de los empujes forzados de la cuenta de usuario u organización a la que pertenecen. Las cuentas de usuario y las organizaciones a su vez heredan su configuración de subidas forzadas de aquella de la empresa. + +Puedes sustituir los parámetros predeterminados heredados al configurar los parámetros para una cuenta de usuario u organización. + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. En "Parámetros predeterminados del repositorio" en la sección "Empujes forzados", selecciona + - **Block** (Bloquear) para bloquear los empujes forzados en todas las ramas. + - **Block to the default branch** (Bloquear en la rama por defecto) para bloquear solo los empujes forzados en la rama por defecto. ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png) +6. Opcionalmente, selecciona **Enforce on all repositories** (Implementar en todos los repositorios) para sustituir los parámetros específicos del repositorio. Nota que esto **no** anulará alguna política válida en toda la empresa. ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) + +{% if enterpriseServerVersions contains currentVersion %} + +### Configurar el acceso de lectura anónimo de Git + +{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} + +{% if enterpriseServerVersions contains currentVersion %}Si [habilitaste el modo privado](/enterprise/admin/configuration/enabling-private-mode) en tu empresa, puedes {% else %}Puedes {% endif %}permitir a los administradores de repositorio habilitar el acceso de lectura de Git a los repositorios públicos. + +Habilitar el acceso anónimo de lectura de Git permite a los usuarios saltar la autenticación para las herramientas personalizadas en tu empresa. Cuando tú o un administrador de repositorio activan esta configuración de acceso a un repositorio, las operaciones Git no autenticadas (y cualquiera con acceso de red a {% data variables.product.product_name %}) tendrán acceso de lectura al repositorio sin autenticación. + +De ser necesario, puedes prevenir que los administradores de repositorio cambien la configuración de acceso anónimo de Git para los repositorios de tu empresa si bloqueas la configuración de acceso de los mismos. Una vez que bloqueas los parámetros de acceso de lectura Git de un repositorio, solo un administrador del sitio puede modificar los parámetros. + +{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} + +{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} + +#### Configurar el acceso de lectura anónimo de Git para todos los repositorios + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. En "Acceso de lectura Git anónimo", usa el menú desplegable y haz clic en **Activado**. ![Menú desplegable de acceso de lectura Git anónimo que muestra las opciones de menú "Habilitado" e "Inhabilitado"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png) +3. Opcionalmente, para prevenir que los administradores de repositorio cambien la configuración del acceso de lectura anónimo de Git en todos los repositorios de tu empresa, selecciona **Prevenir que los administradores de los repositorios cambien el acceso de lectura anónimo de Git**. ![Casilla de verificación seleccionada para prevenir que los administradores de los repositorios cambien la configuración de acceso de lectura anónimo de Git para todos los repositorios de tu empresa](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) + +#### Configurar el acceso de lectura anónimo de Git para un repositorio específico + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +6. En "Zona de peligro", al lado de "Activar el acceso de lectura Git anónimo", haz clic en **Activar**. ![Botón "Activado" en "Activar el acceso de lectura Git anónimo" en la zona de peligro de los parámetros de administración del sitio de un repositorio ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png) +7. Revisa los cambios. Para confirmar, haz clic en **Sí, habilitar el acceso de lectura Git anónimo.** ![Confirma la configuración de acceso de lectura Git anónimo en la ventana emergente](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png) +8. Opcionalmente, para impedir que los administradores de repositorio modifiquen estos parámetros para este repositorio, selecciona **Impedir que los administradores de repositorio modifiquen el acceso de lectura Git anónimo**. ![Selecciona la casilla de verificación para evitar que los administradores del repositorio cambien el acceso de lectura Git anónimo para este repositorio](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png) + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Requerir una política para el nombre de la rama predeterminada + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña de **Políticas de los repositorios**, debajo de "Nombre de la rama predeterminada", ingresa el nombre de rama predeterminada que deberán utilizar los repositorios nuevos. ![Caja de texto para ingresar un nombre de rama predeterminado](/assets/images/help/business-accounts/default-branch-name-text.png) +4. Opcionalmente, para requerir el nombre de rama predeterminado para todas las organizaciones en la empresa, selecciona **Requerir en toda la empresa**. ![Casilla de requerir](/assets/images/help/business-accounts/default-branch-name-enforce.png) +5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/business-accounts/default-branch-name-update.png) +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/policies/index.md b/translations/es-ES/content/admin/policies/index.md new file mode 100644 index 0000000000000..e48cae9ace9e9 --- /dev/null +++ b/translations/es-ES/content/admin/policies/index.md @@ -0,0 +1,21 @@ +--- +title: Configurar las políticas para tu empresa +intro: 'Puedes configurar políticas en {% data variables.product.product_name %} para reducir el riesgo e incrementar la calidad.' +redirect_from: + - /enterprise/admin/developer-workflow + - /enterprise/admin/policies +versions: + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /enforcing-policies-for-your-enterprise %} + {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %} +{% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %} + {% link_in_list /about-pre-receive-hooks %} + {% link_in_list /creating-a-pre-receive-hook-environment %} + {% link_in_list /creating-a-pre-receive-hook-script %} + {% link_in_list /managing-pre-receive-hooks-on-the-github-enterprise-server-appliance %} diff --git a/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md new file mode 100644 index 0000000000000..638e97e5b2806 --- /dev/null +++ b/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md @@ -0,0 +1,57 @@ +--- +title: Administrar ganchos de pre-recepción en el aparato del Servidor de GitHub Enterprise +intro: 'Configurar cómo las personas usarán sus ganchos de pre-recepción dentro de su aparato de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance + - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance/ + - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance +versions: + enterprise-server: '*' +--- + +### Crear ganchos de pre-recepción + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +4. Haz clic en **Add pre-receive hook** (Agregar gancho de pre-recepción). ![Agregar un gancho de pre-recepción](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png) +5. En el campo **Hook name** (Nombre de gancho), escribe el nombre del gancho que deseas crear. ![Nombrar los ganchos de pre-recepción](/assets/images/enterprise/site-admin-settings/hook-name.png) +6. En el menú desplegable **Environment** (Entorno), selecciona el entorno en el que deseas ejecutar el gancho. ![Entornos para ganchos](/assets/images/enterprise/site-admin-settings/environment.png) +7. Debajo de **Script**, desde el menú desplegable **Select hook repository** (Seleccionar repositorio de gancho), selecciona el repositorio que contiene tu script de gancho de pre-recepción. Desde el menú desplegable **Select file** (Seleccionar archivo), selecciona el nombre de archivo o el script del gancho de pre-recepción. ![Script para ganchos](/assets/images/enterprise/site-admin-settings/hook-script.png) +8. Selecciona **Use the exit-status to accept or reject pushes** (Usar el estado de salida para aceptar o rechazar subidas) para imponer tu script. Al quitar la marca de selección de esta opción podrás probar el script mientras se ignora el valor del estado de salida. En este modo, el resultado del script estará visible para el usuario en la línea de comandos pero no en la interfaz web. ![Usar el estado de salida](/assets/images/enterprise/site-admin-settings/use-exit-status.png) +9. Selecciona **Enable this pre-receive hook on all repositories by default ** (Habilitar este gancho de pre-recepción en todos los repositorios por defecto) si quieres que el gancho de pre-recepción se ejecute en todos los repositorios. ![Habilitar gachos para todos los repositorios](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png) +10. Selecciona **Administrators can enable and disable this hook** (Los administradores pueden habilitar e inhabilitar este gancho) para permitir que los miembros de la organización con permisos de administración o propietario seleccionen si desean habilitar o inhabilitar este gancho de pre-recepción. ![Los administradores habilitan o inhabilitan los ganchos](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png) + +### Editar ganchos de pre-recepción + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +1. Junto al gancho de pre-recepción que deseas editar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Editar pre-recepción](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png) + +### Eliminar ganchos de pre-recepción + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +2. Junto al gancho de pre-recepción que deseas eliminar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Editar pre-recepción](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png) + +### Configurar ganchos de pre-recepción para una organización + +Un administrador de la organización solo puede configurar permisos de gancho para una organización si el administrador del sitio seleccionó la opción **Administrators can enable o disable this hook** (Los administradores pueden habilitar o inhabilitar este gancho) al crear el gancho de pre-recepción. Para configurar los ganchos de pre-recepción para un repositorio, debes ser el administrador o el propietario de una organización. + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. En la barra lateral izquierda, haz clic en **Hooks** (Ganchos). ![Barra lateral de ganchos](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png) +5. Junto al gancho de pre-recepción que deseas configurar, haz clic en el menú desplegable **Hook permissions** (Permisos del gancho). Selecciona si deseas habilitar o inhabilitar el gancho de pre-recepción o permite que lo configuren los administradores del repositorio. ![Permisos para ganchos](/assets/images/enterprise/orgs-and-teams/hook-permissions.png) + +### Configurar ganchos de pre-recepción para un repositorio + +Un propietario de repositorio solo puede configurar un gancho si el administrador del sitio seleccionó la opción **Administrators can enable or disable this hook** (Los administradores pueden habilitar o inhabilitar este gancho) al crear el gancho de pre-recepción. En una organización, el propietario de la organización también debe haber seleccionado el permiso de gancho **Configurable**. Para configurar los ganchos de pre-recepción para un repositorio, debes ser un propietario de repositorio. + +{% data reusables.profile.enterprise_access_profile %} +2. Haz clic en **Repositories** (Repositorios) y selecciona el repositorio para el que deseas configurar los ganchos de pre-recepción. ![Repositorios](/assets/images/enterprise/repos/repositories.png) +{% data reusables.repositories.sidebar-settings %} +4. En la barra lateral izquierda, haz clic en **Hooks & Services** (Ganchos y Servicios). ![Ganchos y servicios](/assets/images/enterprise/repos/hooks-services.png) +5. Junto al gancho de pre-recepción que deseas configurar, haz clic en el menú desplegable **Hook permissions** (Permisos del gancho). Selecciona si deseas habilitar o inhabilitar el gancho de pre-recepción. ![Permisos para ganchos de repositorios](/assets/images/enterprise/repos/repo-hook-permissions.png) diff --git a/translations/es-ES/content/admin/release-notes.md b/translations/es-ES/content/admin/release-notes.md new file mode 100644 index 0000000000000..7f4e202b7ffe3 --- /dev/null +++ b/translations/es-ES/content/admin/release-notes.md @@ -0,0 +1,8 @@ +--- +title: Notas de lanzamiento +intro: Las notas de lanzamiento para {{ allVersions[currentVersion].versionTitle }}. +layout: notas de lanzamiento +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/about-migrations.md b/translations/es-ES/content/admin/user-management/about-migrations.md new file mode 100644 index 0000000000000..02ce80f4eed31 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/about-migrations.md @@ -0,0 +1,47 @@ +--- +title: Acerca de las migraciones +intro: 'Una migración es un proceso de transferencia de datos desde una ubicación *origen* (ya sea una organización {% data variables.product.prodname_dotcom_the_website %} o una instancia {% data variables.product.prodname_ghe_server %}) a una instancia *objetivo* {% data variables.product.prodname_ghe_server %}. Las migraciones se pueden utilizar para la transferencia de datos al cambiar de plataforma o actualizar el hardware en la instancia.' +redirect_from: + - /enterprise/admin/migrations/about-migrations + - /enterprise/admin/user-management/about-migrations +versions: + enterprise-server: '*' +--- + +### Tipos de migraciones + +Existen tres tipos de migraciones que se pueden realizar: + +- Una migración de una instancia {% data variables.product.prodname_ghe_server %} a otra instancia {% data variables.product.prodname_ghe_server %}. Puedes migrar la cantidad de repositorios que desees de cualquier usuario u organización en la instancia. Antes de hacer una migración, debes tener acceso de administrador del sitio en ambas instancias. +- Una migración de una organización {% data variables.product.prodname_dotcom_the_website %} a una instancia {% data variables.product.prodname_ghe_server %}. Puedes migrar la cantidad de repositorios de la organización que desees. Antes de efectuar una migración, debes tener [ acceso administrativo ](/enterprise/user/articles/permission-levels-for-an-organization/) a la organización {% data variables.product.prodname_dotcom_the_website %}, así como acceso de administrador del sitio a la instancia de destino. +- *Las ejecuciones de prueba *son migraciones que importan datos a una [instancia de preparación](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). Estas pueden ser útiles para ver qué *sucedería* si se aplicara una migración {% data variables.product.product_location %}. **Se recomienda encarecidamente que se lleve a cabo una ejecución de prueba en una instancia de preparación antes de importar datos a la instancia de producción.** + +### Datos migrados + +En una migración, todo gira en torno a un repositorio. La mayoría de los datos asociados con un repositorio se pueden migrar. Por ejemplo, un repositorio dentro de una organización migrará el repositorio *y* la organización, así como los usuarios, equipos, propuestas y solicitudes de extracción asociados con el repositorio. + +Los elementos de la tabla a continuación se pueden migrar con un repositorio. Los elementos que no se muestren en la lista de datos migrados no se pueden migrar. + +{% data reusables.enterprise_migrations.fork-persistence %} + +| Datos asociados con un repositorio migrado | Notas | +| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Usuarios | Las **@menciones** de los usuarios se reescriben para coincidir con el objetivo. | +| Organizaciones | El nombre y los datos de una organización se migran. | +| Repositorios | Los enlaces a árboles Git, blobs, confirmaciones de cambios y líneas se reescriben para coincidir con el objetivo. El migrador sigue un máximo de tres redirecciones de repositorio. | +| Wikis | Todos los datos de la wiki se migran. | +| Equipos | Las **@menciones** de los equipos se reescriben para coincidir con el objetivo. | +| Hitos | Los registros horarios se conservan. | +| Tableros de proyecto | Los tableros de proyectos asociados con el repositorio y con la organización que posee el repositorio se migran. | +| Problemas | Las referencias de propuestas y los registros horarios se conservan. | +| Comentarios de propuestas | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. | +| Solicitudes de cambios | Las referencias cruzadas a las solicitudes de extracción se reescriben para coincidir con el objetivo. Los registros horarios se conservan. | +| Revisiones de solicitudes de extracción | Las revisiones de solicitudes de extracción y los datos asociados se migran. | +| Comentarios sobre revisiones de solicitudes de extracción | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | +| Comentarios sobre confirmación de cambios | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | +| Lanzamientos | Todos los datos de las versiones se migran. | +| Medidas adoptadas en las solicitudes de extracción o propuestas | Todas las modificaciones a las solicitudes de extracción o propuestas, como la asignación de usuarios, el cambio de nombre de título y la modificación de etiquetas se conservan, junto con los registros horarios de cada acción. | +| Archivos adjuntos | [Los archivos adjuntos a las propuestas y las solicitudes de extracción](/articles/file-attachments-on-issues-and-pull-requests) se migran. Puedes elegir inhabilitar esta opción como parte de la migración. | +| Webhooks | Solo se migran los webhooks activos. | +| Llaves de implementación de repositorios | Las llaves de implementación de repositorios se migran. | +| Ramas protegidas | La configuración de las ramas protegidas y los datos asociados se migran. | diff --git a/translations/es-ES/content/admin/user-management/activity-dashboard.md b/translations/es-ES/content/admin/user-management/activity-dashboard.md new file mode 100644 index 0000000000000..f884c378ec71a --- /dev/null +++ b/translations/es-ES/content/admin/user-management/activity-dashboard.md @@ -0,0 +1,34 @@ +--- +title: Tablero de actividades +intro: 'El tablero de actividades te proporciona un resumen de toda la actividad en tu empresa.' +redirect_from: + - /enterprise/admin/articles/activity-dashboard/ + - /enterprise/admin/installation/activity-dashboard + - /enterprise/admin/user-management/activity-dashboard +versions: + enterprise-server: '*' + github-ae: '*' +--- + +El Tablero de actividades te proporciona gráficos semanales, mensuales y anuales de la cantidad de: +- Solicitudes de extracción nuevas +- Solicitudes de extracción fusionadas +- Problemas nuevos +- Problemas resueltos +- Comentarios de problemas nuevos +- Repositorios nuevos +- Cuentas de usuario nuevas +- Organizaciones nuevas +- Equipos nuevos + +![Tablero de actividades](/assets/images/enterprise/activity/activity-dashboard-yearly.png) + +{% if enterpriseServerVersions contains currentVersion %} +Para encontrar más analítica basada en datos de +{% data variables.product.product_name %}, puedes comprar {% data variables.product.prodname_insights %}. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)." +{% endif %} + +### Acceder al Tablero de actividades + +1. En la parte superior de cualquier página, haz clic en **Explore** (Explorar). ![Explorar la etiqueta](/assets/images/enterprise/settings/ent-new-explore.png) +2. En el margen izquierdo superior, haz clic en **Activity** (Actividad). ![Botón de actividades](/assets/images/enterprise/activity/activity-button.png) diff --git a/translations/es-ES/content/admin/user-management/adding-people-to-teams.md b/translations/es-ES/content/admin/user-management/adding-people-to-teams.md new file mode 100644 index 0000000000000..d3a8814a1b507 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/adding-people-to-teams.md @@ -0,0 +1,30 @@ +--- +title: Agregar personas a los equipos +redirect_from: + - /enterprise/admin/articles/adding-teams/ + - /enterprise/admin/articles/adding-or-inviting-people-to-teams/ + - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams/ + - /enterprise/admin/user-management/adding-people-to-teams +intro: 'Una vez que se ha creado un equipo, los administradores de la organización pueden agregar usuarios desde {% data variables.product.product_location %} al equipo y determinar a qué repositorios tienen acceso.' +versions: + enterprise-server: '*' +--- + +Cada equipo tiene sus propios premisos de acceso definidos de manera individual [ para repositorios que le pertenecen a tu organización](/articles/permission-levels-for-an-organization). + +- Los miembros con el rol de propietario pueden agregar o eliminar miembros existentes de la organización de todos los equipos. +- Los miembros de equipos que dan permisos de administración solo pueden modificar los repositorios y las membresías de equipos para ese equipo. + +### Configurar un equipo + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.invite_to_team %} +{% data reusables.organizations.review-team-repository-access %} + +### Asignar equipos a los grupos LDAP (para instancias que usan la sincronización LDAP para la autenticación de usuario) + +{% data reusables.enterprise_management_console.badge_indicator %} + +Para agregar un nuevo miembro a un equipo sincronizado con un grupo LDAP, agrega el usuario como un miembro del grupo LDAP o comunícate con el administrador LDAP. diff --git a/translations/es-ES/content/admin/user-management/audit-logging.md b/translations/es-ES/content/admin/user-management/audit-logging.md new file mode 100644 index 0000000000000..d7d7453c58b46 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/audit-logging.md @@ -0,0 +1,41 @@ +--- +title: Registro de auditoría +intro: '{% data variables.product.product_name %} mantiene las bitácoras de los eventos auditados de{% if enterpriseServerVersions contains currentVersion %} sistemas,{% endif %} usuarios, organizaciones, y repositorios. Los registros son útiles para la depuración y el cumplimiento interno y externo.' +redirect_from: + - /enterprise/admin/articles/audit-logging/ + - /enterprise/admin/installation/audit-logging + - /enterprise/admin/user-management/audit-logging +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Para encontrar una lista completa, consulta "[Acciones auditadas](/admin/user-management/audited-actions)". Para obtener más información sobre cómo encontrar una acción en particular, consulta la sección "[Buscar la bitácora de auditoría](/admin/user-management/searching-the-audit-log)". + +### Subir registros + +Se registra cada operación de inserción de Git. Para obtener más información, consulta la sección "[Ver las bitácoras de subida](/admin/user-management/viewing-push-logs)". + +{% if enterpriseServerVersions contains currentVersion %} +### Eventos del sistema + +Todos los eventos del sistema auditados, incluidas las inserciones y las extracciones, se registran en `/var/log/github/audit.log`. Los registros se rotan automáticamente cada 24 horas y se mantienen durante siete días. + +El paquete de soporte incluye registros del sistema. Para obtener más información, consulta la sección "[Proporcionar datos al soporte de {% data variables.product.prodname_dotcom %}](/admin/enterprise-support/providing-data-to-github-support)". + +### Paquete de soporte + +Toda la información de auditoría se registra en el archivo `audit.log` del directorio de `github-logs` de cualquier paquete de soporte. Si está habilitado el redireccionamiento de registro, puedes transmitirle estos datos a un consumidor de flujo syslog externo como [Splunk](http://www.splunk.com/) o [Logstash](http://logstash.net/). Todas las entradas de este registro utilizan la palabra clave `github_audit` y se pueden filtrar con ella. Para obtener más información, consulta la sección "[Reenvío de bitácoras](/admin/user-management/log-forwarding)". + +Por ejemplo, esta entrada muestra que se creó un repositorio nuevo. + +``` +Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"} +``` + +Este ejemplo muestra que las confirmaciones se subieron a un repositorio. + +``` +Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" } +``` +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/user-management/audited-actions.md b/translations/es-ES/content/admin/user-management/audited-actions.md new file mode 100644 index 0000000000000..44246bd880481 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/audited-actions.md @@ -0,0 +1,150 @@ +--- +title: Acciones auditadas +intro: Puedes buscar el registro de auditoría para una gran variedad de acciones. +redirect_from: + - /enterprise/admin/articles/audited-actions/ + - /enterprise/admin/installation/audited-actions + - /enterprise/admin/user-management/audited-actions +versions: + enterprise-server: '*' + github-ae: '*' +--- + +#### Autenticación + +| Nombre | Descripción | +| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `oauth_access.create` | Un [Token de acceso de OAuth][] fue [generado][generate token] para la cuenta de un usuario. | +| `oauth_access.destroy` | Un [Token de acceso de OAuth][] se eliminó de la cuenta de un usuario. | +| `oauth_application.destroy` | Una [Aplicación de OAuth][] se eliminó de la cuenta de un usuario o de una organización. | +| `oauth_application.reset_secret` | Se restableció una [clave secreta de una aplicación de OAuth][]. | +| `oauth_application.transfer` | Una [aplicación de OAuth][] se transfirió de una cuenta de usuario o de organización a otra. | +| `public_key.create` | Una clave SSH se [agregó][add key] a una cuenta de usuario o una [llave de implementación][] se agregó a un repositorio. | +| `public_key.delete` | Una clave SSH se eliminó de una cuenta de usuario o una [llave de implementación][] se eliminó de un repositorio. | +| `public_key.update` | Se actualizó una llave SSH de una cuenta de usuario o una [llave de despliegue][] de un repositorio.{% if enterpriseServerVersions contains currentVersion %} +| `two_factor_authentication.enabled` | [Se habilitó la autenticación de dos factores][2fa] para una cuenta de usuario. | +| `two_factor_authentication.disabled` | Se inhabilitó la [Autenticación bifactorial][2fa] para una cuenta de usuario.{% endif %} + +#### Ganchos + +| Nombre | Descripción | +| ---------------------:| --------------------------------------------------- | +| `hook.create` | Se agregó un enlace nuevo a un repositorio. | +| `hook.config_changed` | Se cambió la configuración de un enlace. | +| `hook.destroy` | Se eliminó un enlace. | +| `hook.events_changed` | Se cambiaron los eventos configurados de un enlace. | + +#### Configuración de ajustes de empresa + +| Nombre | Descripción | +| -------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `business.update_member_repository_creation_permission` | Un administrador de sitio restringe la creación de repositorios en las organizaciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | +| `business.clear_members_can_create_repos` | Un administrador de sitio elimina una restricción para la creación de repositorios en las organizciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% if enterpriseServerVersions contains currentVersion %} +| `enterprise.config.lock_anonymous_git_access` | Un administrador de sitio bloquea el acceso de lectura anónima a Git para prevenir que los administradores de repositorio cambien dicha configuración para los repositorios de la empresa. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | +| `enterprise.config.unlock_anonymous_git_access` | Un administrador de sitio desbloquea el acceso de lectura anónima a Git para permitir que los administradores de repositorio cambien dicha configuración en los repositorios de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %} + +#### Propuestas y solicitudes de extracción + +| Nombre | Descripción | +| ------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `issue.update` | Cambió el texto del cuerpo de un problema (comentario inicial). | +| `issue_comment.update` | Cambió un comentario sobre un problema (diferente al inicial). | +| `pull_request_review_comment.delete` | Se detectó un comentario en una solicitud de extracción. | +| `issue.destroy` | Se eliminó un problema del repositorio. Para obtener más información, consulta la sección "[Borrar una propuesta](/github/managing-your-work-on-github/deleting-an-issue)". | + +#### Organizaciones + +| Nombre | Descripción | +| ------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.async_delete` | Un usuario inició una tarea en segundo plano para eliminar una organización. | +| `org.delete` | Un job en segundo plano que inició un usuario ocasionó que una organización se borrara.{% if currentVersion != "github-ae@latest" %} +| `org.transform` | Una cuenta de usuario se convirtió en una organización. Para obtener más información, consulta la sección "[Convertir a un usuario en una organización](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)".{% endif %} + +#### Ramas protegidas + +| Nombre | Descripción | +| ------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------ | +| `protected_branch.create` | La protección de rama está habilitada para una rama. | +| `protected_branch.destroy` | La protección de rama está inhabilitada para una rama. | +| `protected_branch.update_admin_enforced` | La protección de rama es obligatoria para los administradores de repositorios. | +| `protected_branch.update_require_code_owner_review` | Se atualiza la imposición de las revisiones requeridas de los propietarios del código en una rama. | +| `protected_branch.dismiss_stale_reviews` | El cumplimiento de las solicitudes de extracción en espera descartadas está actualizado para una rama. | +| `protected_branch.update_signature_requirement_enforcement_level` | El cumplimiento de la firma de confirmación obligatoria está actualizado para una rama. | +| `protected_branch.update_pull_request_reviews_enforcement_level` | El cumplimiento de la revisión obligatoria de solicitud de extracción está actualizado para una rama. | +| `protected_branch.update_required_status_checks_enforcement_level` | El cumplimiento de las verificaciones de estado obligatorias está actualizado para una rama. | +| `protected_branch.rejected_ref_update` | Se rechaza el intento de actualización de una rama. | +| `protected_branch.policy_override` | Un administrador de repositorios anula el requisito de protección de una rama. | + +#### Repositorios + +| Nombre | Descripción | +| ------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.access` | La visbilidad de un repositorio cambió a privado{% if enterpriseServerVersions contains currentVersion %}, público,{% endif %} o interno. | +| `repo.archive` | Se archivó un repositorio. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | +| `repo.add_member` | Se agregó un colaborador a un repositorio. | +| `repo.config` | Un administrador de sitio bloqueó los empujes forzados. Para obtener más información, consulta [Bloquear los empujes forzados para un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) para un repositorio. | +| `repo.create` | Se creó un repositorio. | +| `repo.destroy` | Se eliminó un repositorio. | +| `repo.remove_member` | Se eliminó un colaborador de un repositorio. | +| `repo.rename` | Se renombró un repositorio. | +| `repo.transfer` | Un usuario aceptó una solicitud para recibir un repositorio transferido. | +| `repo.transfer_start` | Un usuario envió una solicitud para transferir un repositorio a otro usuario u organización. | +| `repo.unarchive` | Un repositorio dejó de estar archivado. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% if enterpriseServerVersions contains currentVersion %} +| `repo.config.disable_anonymous_git_access` | El acceso de lectura anónima de Git se encuentra inhabilitado para un repositorio. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.enable_anonymous_git_access` | El acceso de lectura anónima de Git se encuentra habilitado para un repositorio. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.lock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está bloqueada, lo cual evita que los administradores de repositorios cambien (habiliten o deshabiliten) esta configuración. Para obtener más información, consulta la sección "[Prevenir que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | +| `repo.config.unlock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está desbloqueada, lo cual permite que los administradores del repositorio cambien (habiliten o inhabiliten) esta configuración. Para obtener más información, consulta la sección "[Prevenir que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)".{% endif %} + +#### Herramientas del admin del sitio + +| Nombre | Descripción | +| --------------------:| ------------------------------------------------------------------------------------------------------------------------------- | +| `staff.disable_repo` | Un administrador del sitio inhabilitó el acceso a un repositorio y a todas sus bifurcaciones. | +| `staff.enable_repo` | Un administrador del sitio volvió a habilitar el acceso a un repositorio y a todas sus bifurcaciones. | +| `staff.fake_login` | Un administrador del sitio inició sesión en {% data variables.product.product_name %} como otro usuario. | +| `staff.repo_unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) uno de los repositorios privados del usuario. | +| `staff.unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) todos los repositorios privados de un usuario. | + +#### Equipos + +| Nombre | Descripción | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + + +#### Usuarios + +| Nombre | Descripción | +| -------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | Se agregó una dirección de correo electrónico a una cuenta de usuario. | +| `user.async_delete` | Se inició un job asincrónico para destruir una cuenta de usuario, lo cual finalmente activó a `user.delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.change_password` | Un usuario cambió su contraseña.{% endif %} +| `user.create` | Se creó una cuenta de usuario nueva. | +| `user.delete` | Se destruyó una cuenta de usuario mediante una tarea asincrónica. | +| `user.demote` | Se disminuyó el nivel de un administrador del sitio a cuenta de usuario común. | +| `user.destroy` | Un usuario borró su cuenta, lo cual activó a `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | Un usuario intentó registrarse con un nombre de usuario, contraseña o código de autenticación de dos factores incorrecto. | +| `user.forgot_password` | Un usuario solicitó el restablecimiento de una contraseña a través de la página de inicio de sesión.{% endif %} +| `user.login` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `user.promote` | Se ascendió una cuenta de usuario común a administrador del sitio. | +| `user.remove_email` | Se eliminó una dirección de correo electrónico de una cuenta de usuario. | +| `user.rename` | Se cambió un nombre de usuario. | +| `user.suspend` | Un administrador de sitio suspendió una cuenta de usuario.{% if enterpriseServerVersions contains currentVersion %} +| `user.two_factor_requested` | Se solicitó a un usuario ingresar un código de autenticación bifactorial.{% endif %} +| `user.unsuspend` | Un administrador del sitió dejó de suspender una cuenta de usuario. | + + [add key]: /articles/adding-a-new-ssh-key-to-your-github-account + [llave de implementación]: /guides/managing-deploy-keys/#deploy-keys + [llave de despliegue]: /guides/managing-deploy-keys/#deploy-keys + [generate token]: /articles/creating-an-access-token-for-command-line-use + [Token de acceso de OAuth]: /developers/apps/authorizing-oauth-apps + [Aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app + [clave secreta de una aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app + [aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app + [2fa]: /articles/about-two-factor-authentication + [2fa]: /articles/about-two-factor-authentication diff --git a/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md b/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md new file mode 100644 index 0000000000000..892d4e0d2c73d --- /dev/null +++ b/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md @@ -0,0 +1,59 @@ +--- +title: Auditar claves SSH +intro: Los administradores del sitio pueden iniciar una auditoría en todas las instancias de las claves SSH. +redirect_from: + - /enterprise/admin/articles/auditing-ssh-keys/ + - /enterprise/admin/user-management/auditing-ssh-keys +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Una vez iniciada, la auditoría desactiva todas las claves SSH existentes y obliga a los usuarios a aprobarlas o rechazarlas antes de que sea posible clonarlas, extraerlas o subirlas a cualquier repositorio. Una auditoría es útil cuando un empleado o contratista se va de la empresa y necesitas asegurarte de que todas las claves estén verificadas. + +### Iniciar una auditoría + +Puedes iniciar una auditoría de claves SSH desde la pestaña "Todos los usuarios" del tablero de administrador del sitio: + +![Iniciar una auditoría de clave pública](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png) + +Una vez que haces clic en el botón "Iniciar auditoría de clave pública", serás redirigido a la pantalla de confirmación que explica lo que sucederá a continuación: + +![Confirmación de la auditoría](/assets/images/enterprise/security/Enterprise-Begin-Audit.png) + +Una vez que haces clic en el botón "Comenzar auditoría", todas las claves SSH son invalidadas y se necesitará aprobación. Verás una notificación que indica que la auditoría ha comenzado. + +### Lo que los usuarios ven + +Si un usuario intenta realizar cualquier operación Git a través de SSH, fallará y se indicará el siguiente mensaje: + +```shell +ERROR: Hola nombre de usuario. Estamos realizando una auditoría de clave SSH. +Visita http(s)://hostname/settings/ssh/audit/2 +para aprobar esta clave y saber que es segura. +Huella digital: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 +fatal: El final remoto ha colgado inesperadamente. +``` + +Cuando el usuario sigue el enlace, se le solicita aprobar las claves en su cuenta: + +![Auditoría de claves](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg) + +Una vez que se aprueban o se rechazan sus claves, podrá interactuar con los repositorios como siempre. + +### Agregar una clave SSH + +Cuando los usuarios nuevos agreguen una clave SSH, se les solicitará su contraseña: + +![Confirmación de contraseña](/assets/images/help/settings/sudo_mode_popup.png) + +Cuando un usuario agrega una clave, recibirá un correo electrónico de notificación que se verá como esto: + + Se agregó la siguiente clave SSH a tu cuenta: + + [title] + ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 + + Si crees que esta clave se agregó por error, puedes eliminar la clave y desactivar el acceso a la siguiente ubicación: + + http(s)://HOSTNAME/settings/ssh diff --git a/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md new file mode 100644 index 0000000000000..e2c561804ac18 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md @@ -0,0 +1,111 @@ +--- +title: Auditar a los usuarios a lo largo de tu empresa +intro: 'El tablero de bitácoras de auditoría muestra a los administradores de sitio las acciones que realizan todos los usuarios y organizaciones en toda la empresa durante los últimos 90 días, incluyendo detalles tales como quién realizó la acción, de qué acción se trata, y cuándo se llevó a cabo.' +redirect_from: + - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ + - /enterprise/admin/user-management/auditing-users-across-your-instance + - /admin/user-management/auditing-users-across-your-instance +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Acceder al registro de auditoría + +El tablero de bitácoras de auditoría te proporciona una presentación visual de los datos de auditoría a lo largo de tu empresa. + +![Tablero de registro de auditoría en toda la instancia](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} + +Dentro del mapa, puedes usar panorámica y zoom para ver eventos en todo el mundo. Mantén el puntero sobre un país para ver un recuento rápido de los eventos de ese país. + +### Buscar eventos a través de tu empresa + +La bitácora de auditoría lista la siguiente información sobre las acciones que se llevan a cabo dentro de tu empresa: + +* [El repositorio](#search-based-on-the-repository) en el cual una acción fue realizada. +* [El usuario](#search-based-on-the-user) que realizó la acción. +* [La organización](#search-based-on-the-organization) a la cual pertenece la acción. +* [La acción](#search-based-on-the-action-performed) que fue realizada. +* [El país](#search-based-on-the-location) en el que la acción fue realizada. +* [La fecha y la hora](#search-based-on-the-time-of-action) en que ocurrió la acción. + +{% warning %} + +**Notas:** + +- Si bien no puedes utilizar texto para buscar entradas de auditoría, puedes crear consultas de búsqueda usando una variedad de filtros. {% data variables.product.product_name %} es compatible con muchos operadores para hacer búsquedas a través de {% data variables.product.product_name %}. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". +- Para buscar eventos de más de 90 días, usa el calificador `created`. + +{% endwarning %} + +#### Búsqueda basada en el repositorio + +El calificador `repo` limita las acciones a un repositorio específico que le pertenece a tu organización. Por ejemplo: + +* `repo:my-org/our-repo` encuentra todos los eventos que ocurrieron para el repositorio `our-repo` en la organización `my-org`. +* `repo:my-org/our-repo repo:my-org/another-repo` encuentra todos los eventos que ocurrieron tanto para los repositorios `our-repo` como `another-repo` en la organización `my-org`. +* `-repo:my-org/not-this-repo` excluye todos los eventos que ocurrieron para el repositorio `not-this-repo` en la organización `my-org`. + +Debes incluir el nombre de tu organización dentro del calificador `repo`; si buscas solo `repo:our-repo` no funcionará. + +#### Búsqueda basada en el usuario + +El calificador `actor` examina eventos basados en el miembro de tu organización que realizó la acción. Por ejemplo: + +* `actor:octocat` encuentra todos los eventos realizados por `octocat`. +* `actor:octocat actor:hubot` encuentra todos los eventos realizados tanto por `octocat` como por `hubot`. +* `-actor:hubot` excluye todos los eventos realizados por `hubot`. + +Solo puedes usar un nombre de usuario {% data variables.product.product_name %}, no el nombre real de un individuo. + +#### Búsqueda basada en la organización + +El calificador `org` limita las acciones a una organización específica. Por ejemplo: + +* `org:my-org` encuentra todos los eventos que ocurrieron para la organización `my-org`. +* `org:my-org action:team` encuentra todos los eventos del equipo realizados dentro de la organización `my-org`. +* `-org:my-org` excluye todos los eventos que ocurrieron para la organización `my-org`. + +#### Búsqueda basada en la acción realizada + +El calificador `action` busca los eventos específicos, agrupados dentro de categorías. Para obtener más información sobre los eventos asociados con estas categorías, consulta la sección "[Acciones auditadas](/admin/user-management/audited-actions)". + +| Nombre de la categoría | Descripción | +| ---------------------- | ----------------------------------------------------------------------------------------------------- | +| `hook` | Contiene todas las actividades relacionadas con los webhooks. | +| `org` | Contiene todas las actividades relacionadas con los miembros de la organización. | +| `repo` | Contiene todas las actividades relacionadas con los repositorios que le pertenecen a tu organización. | +| `team` | Contiene todas las actividades relacionadas con los equipos en tu organización. | + +Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: + +* `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo. +* `-action:billing` excluye todos los eventos en la categoría de facturación. + +Cada categoría tiene un conjunto de eventos asociados con los que puedes filtrar. Por ejemplo: + +* `action:team.create` encuentra todos los eventos donde se creó un equipo. +* `-action:billing.change_email` excluye todos los eventos donde se modificó el correo electrónico de facturación. + +#### Búsqueda basada en la ubicación + +El calificador `country` filtra las acciones por el país de origen. +- Puedes utilizar un código corto de dos letras del país o el nombre completo. +- Los países con espacios en sus nombres deben encerrarse entre comillas. Por ejemplo: + * `country:de` encuentra todos los eventos ocurridos en Alemania. + * `country:Mexico` encuentra todos los eventos ocurridos en México. + * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos. + +#### Búsqueda basada en la fecha de acción + +El calificador `created` filtra las acciones por la fecha en la que ocurrieron. +- Define fechas usando el formato `YYYY-MM-DD`-- es decir, año, seguido del mes, seguido del día. +- Las fechas admiten [ calificadores mayor que, menor que y rango](/enterprise/{{ currentVersion }}/user/articles/search-syntax). Por ejemplo: + * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014. + * `created:>=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o posteriormente. + * `created:<=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o anteriormente. + * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014. diff --git a/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md b/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md new file mode 100644 index 0000000000000..367abc442ff75 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md @@ -0,0 +1,27 @@ +--- +title: Las mejores prácticas para la seguridad del usuario +intro: '{% if enterpriseServerVersions contains currentVersion %}Fuera de las medidas de seguridad a nivel de la instancia (SSL, aislamiento de subdominios, configurar un cortafuegos) que puede implementar un administrador de sitio, hay {% else %}Hay {% endif %}pasos que tus usuarios pueden llevar a cabo para ayudarte a proteger tu empresa.' +redirect_from: + - /enterprise/admin/user-management/best-practices-for-user-security +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +### Activar autenticación de dos factores + +La autenticación de dos factores (2FA) es una manera de iniciar sesión en sitios web y servicios que requieren de un segundo factor además de una contraseña para la autenticación. En el caso de {% data variables.product.prodname_ghe_server %}, este segundo factor es un código de autenticación de un solo uso generado por una aplicación en el smartphone de un usuario. Te recomendamos que le solicites a tus usuarios activar la autenticación de dos factores en sus cuentas. Con la autenticación de dos factores, tanto la contraseña del usuario como su smartphone deben verse comprometidos para permitir que la propia cuenta se vea comprometida. + +Para obtener más información sobre cómo configurar la autenticación de dos factores, consulta "[Acerca de la autenticación de dos factores](/enterprise/{{ currentVersion }}/user/articles/about-two-factor-authentication)". +{% endif %} + +### Solicitar un administrador de contraseñas + +Te recomendamos ampliamente que solicites que tus usuarios instalen y utilicen un administrador de contraseñas; tal como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/); en cualquier computadora que utilicen para conectarse a tu empresa. Esto garantiza que las contraseñas sean más seguras y que sea menos probable que se vean comprometidas o sean robadas. + +### Restringir el acceso a equipos y repositorios + +Para limitar la posible superficie expuesta a ataques en el caso de una vulneración de la seguridad, te recomendamos que se le de a los usuarios acceso solo a los equipos y los repositorios que realmente necesiten para realizar su trabajo. Ya que los miembros con rol de propietario pueden acceder a todos los equipos y los repositorios en la organización, te recomendamos que este equipo sea lo más pequeño posible. + +Para obtener más información sobre la configuración de los equipos y de los permisos del equipo, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)". diff --git a/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md new file mode 100644 index 0000000000000..7f9eaf22acb45 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md @@ -0,0 +1,137 @@ +--- +title: Configurar el almacenamiento de archivos grandes de Git para tu empresa +intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' +redirect_from: + - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/ + - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server + - /enterprise/admin/installation/configuring-git-large-file-storage + - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server + - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server + - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/ + - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/ + - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/ + - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/ + - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de {% data variables.large_files.product_name_long %} + +{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} Puedes utilizar {% data variables.large_files.product_name_long %} con un solo repositorio, con todos tus repositorios personales o de organización, o con todos los repositorios de tu empresa. Antes de que puedas habilitar a {% data variables.large_files.product_name_short %} para repositorios u organizaciones específicos, necesitas habilitar a {% data variables.large_files.product_name_short %} en tu empresa. + +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} + +Para obtener más información, consulta "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Control de versiones de archivos grandes](/enterprise/user/articles/versioning-large-files/)," y el sitio del proyecto [{% data variables.large_files.product_name_long %} ](https://git-lfs.github.com/). + +{% data reusables.large_files.can-include-lfs-objects-archives %} + +### Configurar a {% data variables.large_files.product_name_long %} para tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. Dentro del "acceso de {% data variables.large_files.product_name_short %}", usa el menú desplegable y haz clic en **Enabled (Habilitado)** o **Disabled (Inhabilitado)**. ![Acceso a LFS de Git](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) + +### Configurar {% data variables.large_files.product_name_long %} para un repositorio individual + +{% data reusables.enterprise_site_admin_settings.override-policy %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} + +### Configurar {% data variables.large_files.product_name_long %} para cada repositorio que pertenezca a una cuenta de usuario u organización + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} + +{% if enterpriseServerVersions contains currentVersion %} +### Configurar Almacenamiento de archivos de gran tamaño Git para usar un servidor de terceros + +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} + +1. Inhabilita a {% data variables.large_files.product_name_short %} en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Configurar a {% data variables.large_files.product_name_long %} para tu empresa](#configuring-git-large-file-storage-for-your-enterprise)". + +2. Crea un archivo de configuración {% data variables.large_files.product_name_short %} que apunte al servidor de terceros. + ```shell + # Show default configuration + $ git lfs env + > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) + > git version 2.7.4 (Apple Git-66) +   + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) +   + # Create .lfsconfig that points to third party server. + $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo + $ git lfs env + > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) + > git version 2.7.4 (Apple Git-66) +   + > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none) +   + # Show the contents of .lfsconfig + $ cat .lfsconfig + [remote "origin"] + lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo + ``` + +3. Para mantener la misma configuración {% data variables.large_files.product_name_short %} para cada usuario, confirma un archivo `.lfsconfig` personalizado para el repositorio. + ```shell + $ git add .lfsconfig + $ git commit -m "Adding LFS config file" + ``` +3. Migra cualquier activo {% data variables.large_files.product_name_short %} existente. Para obtener más información, consulta la sección "[Migrarse a un servidor diferente de {% data variables.large_files.product_name_long %}](#migrating-to-a-different-git-large-file-storage-server)". + +### Migrar a un servidor de Git Large File Storage diferente + +Antes de migrarte a un servidor de {% data variables.large_files.product_name_long %} diferente, debes configurar a {% data variables.large_files.product_name_short %} para que utilice un servidor de terceros. Para obtener más información, consulta la sección "[Configurar a {% data variables.large_files.product_name_long %} para utilizar un servidor de terceros](#configuring-git-large-file-storage-to-use-a-third-party-server)". + +1. Configura un repositorio con un segundo remoto. + ```shell + $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo +   + $ git lfs env + > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) + > git version 2.7.4 (Apple Git-66) +   + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) + > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) + ``` + +2. Extrae todos los objetos del remoto anterior. + ```shell + $ git lfs fetch origin --all + > Scanning for all objects ever referenced... + > ✔ 16 objects found + > Fetching objects... + > Git LFS: (16 de 16 archivos) 48.71 MB / 48.85 MB + ``` + +3. Extrae todos los objetos a un nuevo remoto. + ```shell + $ git lfs push NEW-REMOTE --all + > Scanning for all objects ever referenced... + > ✔ 16 objects found + > Pushing objects... + > Git LFS: (16 de 16 archivos) 48.00 MB / 48.85 MB, 879.10 KB pasados por alto + ``` +{% endif %} + +### Further reading + +- [Sitio del proyecto {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/) diff --git a/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md new file mode 100644 index 0000000000000..31a8bc656d71d --- /dev/null +++ b/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md @@ -0,0 +1,24 @@ +--- +title: Configurar visibilidad para los miembros de la organización +intro: Puedes configurar la visibilidad para los miembros nuevos de la organización a lo largo de tu empresa como pública o privada. También puedes hacer que los miembros no puedan modificar su visibilidad de la establecida por defecto. +redirect_from: + - /enterprise/admin/user-management/configuring-visibility-for-organization-membership +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +También puedes implementar tu configuración por defecto en todos los miembros actuales de la organización en tu instancia usando una utilidad de línea de comandos. Por ejemplo, si quieres solicitar que la visibilidad de cada miembro de la organización sea pública, puedes establecer la configuración predeterminada como pública e implementar la predeterminada para todos los nuevos miembros en los parámetros de administración, y luego usar la utilidad de línea de comandos para implementar la configuración pública en los miembros existentes. +{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +3. En "Visibilidad predeterminada de los miembros de la organización", usa el menú desplegable y haz clic en **Private (Privada)** o **Public (Pública)**. ![Menú desplegable con opción para configurar la visibilidad predeterminada de los miembros de la organización como pública o privada](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) +4. Opcionalmente, para evitar que los miembros modifiquen la visibilidad de su membresía respecto de la predeterminada, selecciona **Implementar en los miembros de la organización**. ![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. Si quieres implementar tu nueva configuración de visibilidad en todos los miembros existentes, usa la utilidad de línea de comandos `ghe-org-membership-update`. Para obtener más información, consulta la sección "[Utilidades de la línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)".{% endif %} diff --git a/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md new file mode 100644 index 0000000000000..93d85e90fc9ab --- /dev/null +++ b/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md @@ -0,0 +1,13 @@ +--- +title: Integración continua mediante Jenkins +intro: 'Puedes activar automáticamente la creación de trabajos en un servidor Jenkins cuando las extracciones se realizan a un repositorio en {% data variables.product.product_location %}.' +redirect_from: + - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins + - /enterprise/admin/user-management/continuous-integration-using-jenkins +versions: + enterprise-server: '*' +--- + +### Requisitos + +- Sigue nuestra documentación técnica "[Guía práctica para CI con Jenkins y GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" para conocer las instrucciones detalladas sobre cómo puedes activar automáticamente la creación de trabajos en un servidor Jenkins cuando las extracciones de realizan en un repositorio en {% data variables.product.product_location %}. diff --git a/translations/es-ES/content/admin/user-management/creating-teams.md b/translations/es-ES/content/admin/user-management/creating-teams.md new file mode 100644 index 0000000000000..64b08ef31f07b --- /dev/null +++ b/translations/es-ES/content/admin/user-management/creating-teams.md @@ -0,0 +1,55 @@ +--- +title: Crear equipos +intro: 'Los equipos les permiten a las organizaciones crear grupos de miembros y controlar el acceso a los repositorios. A los miembros del equipo se les pueden otorgar permisos de lectura, escritura o administración para repositorios específicos.' +redirect_from: + - /enterprise/admin/user-management/creating-teams +versions: + enterprise-server: '*' +--- + +Los equipos son centrales para muchas de las características colaborativas de {% data variables.product.prodname_dotcom %}, como las @menciones del equipo para notificar a las partes correspondientes que les quieres solicitar su colaboración o atención. Para obtener más información, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)". + +Un equipo puede representar a un grupo dentro de tu empresa o incluir personas con ciertos intereses o experiencia. Por ejemplo, un equipo de expertos en accesibilidad en {% data variables.product.product_location %} podría estar compuesto por personas de diferentes departamentos. Los equipos pueden representar inquietudes de carácter funcional que complementan la jerarquía divisional existente de una empresa. + +Las organizaciones pueden crear varios niveles de equipos anidados para reflejar la estructura de jerarquía de una empresa o grupo. Para obtener más información, consulta "[Acerca de los equipos](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)". + +### Crear un equipo + +Una combinación prudente de equipos es una manera eficaz de controlar el acceso a los repositorios. Por ejemplo, si tu organización solo permite que tu equipo de ingeniería en lanzamientos suba código a la rama predeterminada de cualquier repositorio, puedes otorgar únicamente a este equipo el permiso de **administrador** para los repositorios de tu organización y darle al resto de los equipos permisos de **lectura**. + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} + +### Crear equipos con la sincronización LDAP activada + +Las instancias que usan LDAP para la autenticación de usuarios pueden usar la sincronización LDAP para administrar los miembros de un equipo. Al poner el **Nombre Distintivo** (DN) del grupo en el campo **LDAP group** (Grupo LDAP), se le asignará un equipo a un grupo LDAP en tu servidor LDAP. Si usas la sincronización LDAP para administrar los miembros de un equipo, no podrás administrar tu equipo dentro de {% data variables.product.product_location %}. Cuando la sincronización LDAP está activada, el equipo asignado sincroniza sus miembros en segundo plano de manera periódica con el intervalo configurado. Para obtener más información, consulta "[Activar sincronización LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +{% warning %} + +**Notas:** +- La sincronización LDAP solo administra la lista de miembros del equipo. Debes administrar los permisos y repositorios del equipo desde dentro del {% data variables.product.prodname_ghe_server %}. +- Si se elimina un grupo LDAP asignado a un DN, o si se borra un grupo LDAP, todos los miembros se eliminan del equipo sincronizado del {% data variables.product.prodname_ghe_server %}. Para solucionar esto, asigna el equipo a un nuevo DN, vuelve a agregar a los miembros del equipo y [sincroniza de forma manual la asignación](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#manually-syncing-ldap-accounts). +- Si se elimina a una persona de un repositorio cuando la sincronización LDAP está activada, perderá el acceso, pero sus bifurcaciones no se borrarán. Si se agrega a esa persona a un equipo con acceso al repositorio original de la organización dentro de los tres meses posteriores, en la siguiente sincronización, se reestablecerá automáticamente su acceso a las bifurcaciones. + +{% endwarning %} + +1. Asegúrate de que [La sincronización LDAP esté activada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync). +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +6. Busca el DN de un grupo LDAP al que asignar el equipo. Si no conoces el DN, escribe el nombre del grupo LDAP. +El {% data variables.product.prodname_ghe_server %} buscará y completará automáticamente cualquier coincidencia. +![Asignar al DN del grupo LDAP](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} diff --git a/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md new file mode 100644 index 0000000000000..06def39d2c8b4 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -0,0 +1,99 @@ +--- +title: Personalizar los mensajes de usuario para tu 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 {% data variables.product.product_location %}.' +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% note %} + +**Nota:** Si usas SAML para la autenticación, tu proveedor de identidad presenta la página de inicio de sesión y no es personalizable a través de {% data variables.product.prodname_ghe_server %}. + +{% endnote %} + +Puedes usar Markdown para dar formato al mensaje. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." + +### Crear un mensaje de inicio de sesión personalizado + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. En **Mensaje de inicio de sesión**, escribe el mensaje que quisieras que vean los usuarios. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Revisar el mensaje presentado. ![Mensaje de inicio presentado](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} +{% endif %} + +### Crear un mensaje de cierre de sesión personalizado + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. En **Mensaje de cierre de sesión**, escribe el mensaje que quieras que vean los usuarios. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Revisar el mensaje presentado. ![Mensaje de salida presentado](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +### Crear un letrero de anuncio global + +Puedes configurar un letrero de anuncio global para que se muestre a todos los usuarios en la parte superior de cada página. + +{% 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. Para obtener más información, consulta las secciones {% if enterpriseServerVersions contains currentVersion %}"[Utilidades de la línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" y {% endif %}"[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". +{% else %} + +También puedes configurar un letrero de anuncio en el shell administrativo utilizando una utilidad de línea de comandos. Para obtener más información, consulta la sección "[Utilidades de línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)". + +{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Debajo de "Anuncio", en el campo de texto, teclea el anuncio que quieras mostrar en un letrero. ![Campo de texto para ingresar el anuncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Menú desplegable de calendario para elegir una fecha de vencimiento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} +{% endif %} diff --git a/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md new file mode 100644 index 0000000000000..681dbcb1a42f0 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md @@ -0,0 +1,53 @@ +--- +title: Inhabilitar el acceso por SSH a git en tu empresa +redirect_from: + - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/ + - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/ + - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance/ + - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance/ + - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization/ + - /enterprise/admin/articles/disabling-ssh-access-for-an-organization/ + - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository/ + - /enterprise/admin/articles/disabling-ssh-access-to-a-repository/ + - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise/ + - /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: 'Puedes prevenir que las personas utilicen git a través de SSH para ciertos repositorios o para todos ellos en tu empresa.' +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Inhabilitar el acceso SSH de Git para un repositorio específico + +{% data reusables.enterprise_site_admin_settings.override-policy %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +1. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png) + +### Inhabilitar el acceso SSH de Git para todos los repositorios que le pertenecen a un usuario o a una organización + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +7. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). Luego selecciona **Enforce on all repositories** (Aplicar en todos los repositorios). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) + +### Inhabilitar el acceso a Git por SSH para todos los repositorios de tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +7. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). Luego selecciona **Enforce on all repositories** (Aplicar en todos los repositorios). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png) diff --git a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md new file mode 100644 index 0000000000000..9704cff37a51f --- /dev/null +++ b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md @@ -0,0 +1,85 @@ +--- +title: Exportar datos de migración desde GitHub.com +intro: 'Puedes exportar los dtos de migración desde una organización en {% data variables.product.prodname_dotcom_the_website %} si utilizas la API para seleccionar los repositorios que deseas migrar y luego generas un archivo de migración que puedas importar en una instancia de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com + - /enterprise/admin/migrations/exporting-migration-data-from-githubcom + - /enterprise/admin/migrations/preparing-the-githubcom-source-organization + - /enterprise/admin/migrations/exporting-the-githubcom-organizations-repositories + - /enterprise/admin/guides/migrations/preparing-the-github-com-source-organization + - /enterprise/admin/guides/migrations/exporting-the-github-com-organization-s-repositories + - /enterprise/admin/user-management/exporting-migration-data-from-githubcom +versions: + enterprise-server: '*' +--- + +### Preparar la orgnanización origen en {% data variables.product.prodname_dotcom %} + +1. Asegúrate de tener [permisos de propietario](/articles/permission-levels-for-an-organization/) en los repositorios de la organización de origen. + +2. {% data reusables.enterprise_migrations.token-generation %} en {% data variables.product.prodname_dotcom_the_website %}. + +{% data reusables.enterprise_migrations.make-a-list %} + +### Exportar los repositorios de la organización + +{% data reusables.enterprise_migrations.fork-persistence %} + +Para exportar datos del repositorio desde {% data variables.product.prodname_dotcom_the_website %}, usa la API de Migraciones. + +La API de Migraciones se encuentra actualmente en un período de previsualización, lo que significa que los puntos finales y los parámetros pueden cambiar en el futuro. Para acceder a la API de Migraciones, debes proporcionar un [tipo de medio](/rest/overview/media-types) personalizado en el encabezado `Accept` (Aceptar): `application/vnd.github.wyandotte-preview+json`. Los ejemplos a continuación incluyen el tipo de medio personalizado. + +### Generar un archivo de migración + +{% data reusables.enterprise_migrations.locking-repositories %} + +1. Notifica a los miembros de tu organización que harás una migración. La exportación puede durar varios minutos, en función de la cantidad de repositorios que se exporten. La migración completa, incluida la importación, puede durar varias horas. Por lo tanto, te recomendamos que hagas una prueba para determinar cuánto tiempo tomará el proceso completo. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)". + +2. Inicia una migración mediante `POST` al punto final de migración. Necesitarás: + * Tu token de acceso para autenticación. + * Una [lista de los repositorios](/rest/reference/repos#list-organization-repositories) que deseas migrar: + ```shell + curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X POST \ + -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \ + https://api.github.com/orgs/orgname/migrations + ``` + * Si deseas bloquear los repositorios antes de migrarlos, asegúrate de que `lock_repositories`esté establecido en `true` (true). Esto es altamente recomendable. + * Puedes excluir archivos adjuntos pasando `exclude_attachments: true` al punto final. {% data reusables.enterprise_migrations.exclude-file-attachments %} El tamaño final del archivo debe ser inferior a 20 GB. + + Esta solicitud devuelve un `id` único que representa tu migración. Lo necesitarás para solicitudes posteriores a la API de Migraciones. + +3. Envía una solicitud de `GET` al punto final del estado de la migración para extraer el estado de una migración. Necesitarás: + * Tu token de acceso para autenticación. + * El `id` único de la migración: + ```shell + curl -H "Autorización: token GITHUB_ACCESS_TOKEN" \ + -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + https://api.github.com/orgs/orgname/migrations/id + ``` + + Una migración puede estar en uno de los siguientes estados: + * `pending` (pendiente), lo que significa que la migración aún no se ha iniciado. + * `exporting` (exportando), lo que significa que la migración está en curso. + * `exported` (exportada), lo que significa que la migración finalizó correctamente. + * `failed` (fallida), lo que significa que la migración falló. + +4. Una vez que se haya exportado tu migración, descarga el archivo de migración enviando una solicitud de `GET` al punto final de descarga de migración. Necesitarás: + * Tu token de acceso para autenticación. + * El `id` único de la migración: + ```shell + curl -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + -u GITHUB_USERNAME:GITHUB_ACCESS_TOKEN \ + -L -o migration_archive.tar.gz \ + https://api.github.com/orgs/orgname/migrations/id/archive + ``` + +5. El archivo de migración se elimina automáticamente después de siete días. Si prefieres eliminarlo antes, puedes enviar una solicitud `DELETE` al punto final de eliminación del archivo de migración. Necesitarás: + * Tu token de acceso para autenticación. + * El `id` único de la migración: + ```shell + curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X DELETE \ + -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ + https://api.github.com/orgs/orgname/migrations/id/archive + ``` +{% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md new file mode 100644 index 0000000000000..18308c936d755 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md @@ -0,0 +1,99 @@ +--- +title: Exportar los datos de migración de tu empresa +intro: 'Para cambiar las plataformas o migrarse de una instancia de pruebas a una productiva, puedes exportar los datos de migración de una instancia de {% data variables.product.prodname_ghe_server %} si preparas la instancia, bloqueas los repositorios, y generas un archivo de migración.' +redirect_from: + - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise/ + - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server + - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance + - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories + - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance/ + - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/ + - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise +versions: + enterprise-server: '*' +--- + +### Preparar la instancia origen de {% data variables.product.prodname_ghe_server %} + +1. Verifica que eres un administrador del sitio en el origen {% data variables.product.prodname_ghe_server %}. La mejor manera de hacerlo es verificar que puedes usar [SSH en la instancia](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). + +2. {% data reusables.enterprise_migrations.token-generation %} en la instancia de origen {% data variables.product.prodname_ghe_server %}. + +{% data reusables.enterprise_migrations.make-a-list %} + +### Exportar los repositorios origen de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_migrations.locking-repositories %} + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Para preparar un repositorio para la exportación, usa el comando `ghe-migrator add` con la URL del repositorio: + * Si estás bloqueando el repositorio, agrega el comando `--lock`. Si estás efectuando una ejecución de prueba, el comando `--lock` no es necesario. + ```shell + $ ghe-migrator add https://hostname/username/reponame --lock + ``` + * Puedes excluir archivos adjuntos agregando ` --exclude_attachments ` al comando. {% data reusables.enterprise_migrations.exclude-file-attachments %} + * Para preparar varios repositorios al mismo tiempo para exportación, crea un archivo de texto que incluya las URL del repositorio en una línea separada, y ejecuta el comando `ghe-migrator add` con el indicador `-i` y la ruta a tu archivo de texto. + ```shell + $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt + ``` + +3. Cuando se te indique, ingresa tu nombre de usuario {% data variables.product.prodname_ghe_server %}: + ```shell + Ingresa el nombre de usuario autorizado para la migración: admin + ``` +4. Cuando se te pida un token de acceso personal, ingresa el token de acceso que creaste en"[Preparación de {% data variables.product.prodname_ghe_server %} la instancia de origen](#preparing-the-github-enterprise-server-source-instance)": + ```shell + Ingresa el token de acceso personal: ************** + ``` +5. Cuando `ghe-migrator add` haya terminado, imprimirá el "GUID de migración" único que generó para identificar esta exportación, así como una lista de los recursos que se agregaron a la exportación. Utilizarás el GUID de migración que generaste en los pasos posteriores `ghe-migrator add` y`ghe-migrator export` para indicar a `ghe-migrator` que continúe operando en la misma exportación. + ```shell + > 101 models added to export + > Migration GUID: example-migration-guid + > Number of records in this migration: + > users | 5 + > organizations | 1 + > repositories | 1 + > teams | 3 + > protected_branches | 1 + > pull_request_reviews | 1 + > milestones | 1 + > issues | 3 + > pull_requests | 5 + > pull_request_review_comments | 4 + > commit_comments | 2 + > issue_comments | 10 + > issue_events | 63 + > releases | 3 + > attachments | 4 + > projects | 2 + ``` + Cada vez que agregues un repositorio nuevo con un GUID de migración existente, se actualizará la exportación existente. Si ejecutas `ghe-migrator add` nuevamente sin un GUID de migración, comenzará una nueva exportación y generará un nuevo GUID de migración. **No vuelvas a utilizar el GUID de migración generado durante una exportación cuando comiences a preparar tu migración para importar**. + +3. Si bloqueaste el repositorio de origen, puedes usar el comando `ghe-migrator target_url` para configurar un mensaje de bloqueo personalizado en la página del repositorio que vincula con la nueva ubicación del repositorio. Pasa la URL del repositorio de origen, la URL del repositorio de destino y el GUID de migración del Paso 5: + + ```shell + $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID + ``` + +6. Usa el comando `ghe-migrator add` con el indicador `-g` para agregar más repositorios a la misma exportación. Pasarás la nueva URL del repositorio y el GUID de migración del Paso 5: + ```shell + $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock + ``` +7. Cuando hayas terminado de agregar repositorios, genera el archivo de migración con el comando `ghe-migrator export` con el indicador `-g` y el GUID de migración del Paso 5: + ```shell + $ ghe-migrator export -g MIGRATION_GUID + > Archivo guardado en: /data/github/current/tmp/MIGRATION_GUID.tar.gz + ``` + * {% data reusables.enterprise_migrations.specify-staging-path %} + +8. Cierra la conexión a {% data variables.product.product_location %}: + ```shell + $ exit + > logout + > Connection to hostname closed. + ``` +9. Copia el archivo de migración a tu computadora con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). Se te asignará al archivo de almacenamiento un nombre con el GUID de migración: + ```shell + $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop + ``` +{% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md new file mode 100644 index 0000000000000..0f7f751d87cdc --- /dev/null +++ b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md @@ -0,0 +1,73 @@ +--- +title: Importar datos desde sistemas de control de versiones de terceros +intro: 'Usando el conjunto de herramientas git-import, puedes importar desde Subversion, Mercurial y Team Foundation Version Control a los repositorios Git en {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /enterprise/admin/migrations/importing-data-from-third-party-version-control-systems + - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems +versions: + enterprise-server: '*' +--- + +### Importar proyectos de Mercurial + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: + ```shell + $ git-import-hg-raw HG-CLONE-URL /PATH/REPO-NAME.git + # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. + ``` +{% data reusables.enterprise_migrations.review-the-import-csv %} +4. Reescribe los autores y las ramas utilizando el archivo CSV: + ```shell + $ git-import-rewrite --flavor hg --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git + ``` +5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +{% data reusables.command_line.switching_directories_procedural %} +7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: + ```shell + $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE + ``` + +### Importar proyectos de Subversion + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: + ```shell + $ git-import-svn-raw SVN-CLONE-URL /PATH/REPO-NAME.git + # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. + ``` +{% data reusables.enterprise_migrations.review-the-import-csv %} +4. Reescribe los autores y las ramas utilizando el archivo CSV: + ```shell + $ git-import-rewrite --flavor svn --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git + ``` +5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +{% data reusables.command_line.switching_directories_procedural %} +7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: + ```shell + $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE + ``` + +### Importar proyectos de Team Foundation Version Control + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: + ```shell + $ git-import-tfs-raw TEAM-FOUNDATION-CLONE-URL /PATH/REPO-NAME.git + # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. + ``` +{% data reusables.enterprise_migrations.review-the-import-csv %} +4. Reescribe los autores y las ramas utilizando el archivo CSV: + ```shell + $ git-import-rewrite --flavor tfs --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git + ``` +5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +{% data reusables.command_line.switching_directories_procedural %} +7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: + ```shell + $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE + ``` + +### Further reading + +- "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)" diff --git a/translations/es-ES/content/admin/user-management/index.md b/translations/es-ES/content/admin/user-management/index.md new file mode 100644 index 0000000000000..40678b304dbb2 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/index.md @@ -0,0 +1,57 @@ +--- +title: 'Administrar usuarios, organizaciones y repositorios' +shortTitle: 'Administrar usuarios, organizaciones y repositorios' +intro: 'Esta guía describe los métodos de autenticación para los usuarios que inician sesión en tu empresa, cómo crear organizaciones y equipos para acceso a repositorios y colaboraciones, y las mejores prácticas que se sugieren para la seguridad de los usuarios.' +redirect_from: + - /enterprise/admin/categories/user-management/ + - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration + - /enterprise/admin/migrations + - /enterprise/admin/clustering + - /enterprise/admin/user-management +versions: + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-users-in-your-enterprise %} + {% link_in_list /promoting-or-demoting-a-site-administrator %} + {% link_in_list /best-practices-for-user-security %} + {% link_in_list /auditing-users-across-your-enterprise %} + {% link_in_list /managing-dormant-users %} + {% link_in_list /suspending-and-unsuspending-users %} + {% link_in_list /placing-a-legal-hold-on-a-user-or-organization %} + {% link_in_list /auditing-ssh-keys %} + {% link_in_list /customizing-user-messages-for-your-enterprise %} + {% link_in_list /rebuilding-contributions-data %} + {% link_in_list /managing-global-webhooks %} +{% topic_link_in_list /managing-organizations-in-your-enterprise %} + {% link_in_list /configuring-visibility-for-organization-membership %} + {% link_in_list /preventing-users-from-creating-organizations %} + {% link_in_list /requiring-two-factor-authentication-for-an-organization %} + {% link_in_list /creating-teams %} + {% link_in_list /adding-people-to-teams %} + {% link_in_list /removing-users-from-teams-and-organizations %} + {% link_in_list /managing-projects-using-jira %} + {% link_in_list /continuous-integration-using-jenkins %} +{% topic_link_in_list /managing-repositories-in-your-enterprise %} + {% link_in_list /configuring-git-large-file-storage-for-your-enterprise %} + {% link_in_list /migrating-to-internal-repositories %} + {% link_in_list /disabling-git-ssh-access-on-your-enterprise %} + {% link_in_list /troubleshooting-service-hooks %} +{% topic_link_in_list /monitoring-activity-in-your-enterprise %} + {% link_in_list /activity-dashboard %} + {% link_in_list /audit-logging %} + {% link_in_list /searching-the-audit-log %} + {% link_in_list /audited-actions %} + {% link_in_list /viewing-push-logs %} + {% link_in_list /log-forwarding %} +{% topic_link_in_list /migrating-data-to-and-from-your-enterprise %} + {% link_in_list /about-migrations %} + {% link_in_list /exporting-migration-data-from-your-enterprise %} + {% link_in_list /exporting-migration-data-from-githubcom %} + {% link_in_list /preparing-to-migrate-data-to-your-enterprise %} + {% link_in_list /migrating-data-to-your-enterprise %} + {% link_in_list /importing-data-from-third-party-version-control-systems %} diff --git a/translations/es-ES/content/admin/user-management/log-forwarding.md b/translations/es-ES/content/admin/user-management/log-forwarding.md new file mode 100644 index 0000000000000..30bfb05d38aa6 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/log-forwarding.md @@ -0,0 +1,42 @@ +--- +title: Redireccionamiento de registro +intro: '{% data variables.product.product_name %} utiliza `syslog-ng` para reenviar bitácoras de {% if enterpriseServerVersions contains currentVersion %}sistema{% elsif currentVersion == "github-ae@latest" %}Git{% endif %} y de aplicaciones al servidor que especifiques.' +redirect_from: + - /enterprise/admin/articles/log-forwarding/ + - /enterprise/admin/installation/log-forwarding + - /enterprise/admin/enterprise-management/log-forwarding + - /admin/enterprise-management/log-forwarding +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Es compatible cualquier sistema de recopilación de registro que admita los flujos de registro syslog-style (p. ej., [Logstash](http://logstash.net/) y [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)). + +### Habilitar redireccionamiento de registro + +{% if enterpriseServerVersions contains currentVersion %} +1. En la página de parámetros {% data variables.enterprise.management_console %}, en la barra lateral izquierda, haz clic en **(Monitoring) Revisar**. +1. Selecciona **Enable log forwarding (Habilitar redireccionamiento de registro)**. +1. En el campo **Server address (Dirección del servidor)**, escribe la dirección del servidor al que desees redireccionar los registros. Puedes especificar varias direcciones en una lista de separación por coma. +1. En el menú desplegable de Protocolo, selecciona el protocolo a utilizar para que se comunique con el servidor de registro. El protocolo se aplicará a todos los destinos de registro especificados. +1. Selecciona **Enable TLS (Habilitar TLS)**. +1. Haz clic en **Choose File (Elegir el archivo)** y elige un certificado CA para encriptar la comunicación entre puntos de conexión syslog. Se validará la cadena de certificado completa, y debe terminar en un certificado raíz. Para obtener más información, consulta [Opciones TLS en la documentación de syslog-ng](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599). +{% elsif currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. Debajo de {% octicon "gear" aria-label="The Settings gear" %} **Configuración**, da clic en **Reenvío de bitácoras**. ![Pestaña de reenvío de bitácoras](/assets/images/enterprise/business-accounts/log-forwarding-tab.png) +1. Debajo de "Reenvío de bitácoras", selecciona **Habilitar el reenvío de bitácoras**. ![Casilla de verificación para habilitar el reenvío de bitácoras](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png) +1. Debajo de "Dirección del servidor", ingresa la dirección del servidor al cual quieras reenviar las bitácoras. ![Campo de dirección del servidor](/assets/images/enterprise/business-accounts/server-address-field.png) +1. Utiliza el menú desplegable de "Protocolo", y selecciona un protocolo. ![Menú desplegable del protocolo](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png) +1. Opcionalmente, para habilitar la comunicación cifrada con TLS entre las terminales de syslog, selecciona **Habilitar TLS**. ![Casilla de verificación para habilitar TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png) +1. Debajo de "Certificado público", pega tu certificado x509. ![Caja de texto para el certificado público](/assets/images/enterprise/business-accounts/public-certificate-text-box.png) +1. Haz clic en **Save ** (guardar). ![Botón de guardar para el reenvío de bitácoras](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +### Solución de problemas +Si te encuentras con algún problema para reenviar las bitácoras, contacta a + +{% data variables.contact.contact_ent_support %} y adjunta el archivo de salida de `http(s)://[hostname]/setup/diagnostics` a tu mensaje de correo electrónico. +{% endif %} diff --git a/translations/es-ES/content/admin/user-management/managing-dormant-users.md b/translations/es-ES/content/admin/user-management/managing-dormant-users.md new file mode 100644 index 0000000000000..1856570543d00 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-dormant-users.md @@ -0,0 +1,47 @@ +--- +title: Administrar usuarios inactivos +redirect_from: + - /enterprise/admin/articles/dormant-users/ + - /enterprise/admin/articles/viewing-dormant-users/ + - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ + - /enterprise/admin/user-management/managing-dormant-users +intro: Se considera una cuenta de usuario como durmiente si no ha tenido actividad por lo menos en todo un mes.{% if enterpriseServerVersions contains currentVersion %} Puedes elegir suspender a los usuarios durmientes para liberar licencias de usuario.{% endif %} +versions: + enterprise-server: '*' + github-ae: '*' +--- + +"Actividad" incluye, entre otros: +- Iniciar sesión en {% data variables.product.product_name %}. +- Comentar en propuestas y en solicitudes de extracción. +- Crear, eliminar, observar y destacar repositorios. +- Subida de confirmaciones.{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Acceder a los recursos utilizando un token de acceso personal o llave de SSH.{% endif %} + +### Visualizar usuarios inactivos + +Puedes ver una lista de todos los usuarios inactivos que no han sido suspendidos y que no son administradores del sitio. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. En la barra lateral de la izquierda, haz clic en **Usuarios inactivos**. ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% if enterpriseServerVersions contains currentVersion %} +4. Para suspender todos los usuarios inactivos de esta lista, haz clic en **Suspender todos**, en la parte superior de la página. ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %} + +### Determinar si un usuario está inactivo + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +5. En la sección **Información del usuario**, un punto rojo con la palabra "Inactiva" indica que la cuenta del usuario está inactiva, y un punto verde con la palabra "Activa" indica que la cuenta del usuario está activa. ![Cuenta de usuario inactiva](/assets/images/enterprise/stafftools/dormant-user.png) ![Cuenta de usuario activa](/assets/images/enterprise/stafftools/active-user.png) + +### Configurar el umbral de inactividad + +{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. En "Umbral de inactividad", usa el menú desplegable y haz clic en el umbral de inactividad deseado. ![Menú desplegable Umbral de inactividad](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) diff --git a/translations/es-ES/content/admin/user-management/managing-global-webhooks.md b/translations/es-ES/content/admin/user-management/managing-global-webhooks.md new file mode 100644 index 0000000000000..5a1e50190de16 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-global-webhooks.md @@ -0,0 +1,70 @@ +--- +title: Administrar webhooks globales +intro: 'Los administradores de sitio pueden ver, agregar, editar y borrar los webhooks globales para rastrear los eventos de la empresa.' +redirect_from: + - /enterprise/admin/user-management/about-global-webhooks + - /enterprise/admin/user-management/managing-global-webhooks +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los webhooks locales + +Puedes utilizar webhooks globales para monitorear, responder, o requerir reglas automáticamente para la administración de usuarios y organizaciones de tu empresa. Por ejemplo, puedes configurar tus webhooks para ejecutar lo siguiente: +- Se crea o se elimina una cuenta de usuario. +- Se crea o se borra una organización +- Se agrega o se elimina un colaborador desde un repositorio. +- Se bifurca un repositorio + +![Listado de webhooks globales](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) + +{% data reusables.enterprise_user_management.manage-global-webhooks-api %} + +### Agregar un webhook local + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Haz clic en **Add webhook** (Agregar webhook). ![Botón Agregar webhook en la página webhooks en el centro de administración](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) +6. Escribe la URL donde quisieras recibir las cargas. ![Campo para escribir una URL de carga](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) +7. Opcionalmente, usa el menú desplegable **Tipo de contenido** y haz clic en un formato de carga. ![Menú desplegable que detalla las opciones de tipo de contenido](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) +8. Opcionalmente, en el campo **Secreto**, escribe una cadena para usar como una clave `secret`. ![Campo para escribir una cadena para usar como clave secreta](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) +9. Opcionalmente, si no quieres que {% data variables.product.prodname_ghe_server %} verifique los certificados SSL cuando se entregan las cargas, haz clic en **Desactivar la verificación SSL**. Lee la información sobre verificación SSL, luego haz clic en **Entiendo que mis webhooks pueden no ser seguros**. ![Botón para desactivar la verificación SSL](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) + + {% warning %} + + **Advertencia:** La verificación SSL ayuda a garantizar que las cargas de enganche se entreguen de forma segura. No es recomendable desactivar la verificación SSL. + + {% endwarning %} +10. Decide si quieres que esta webhook se dispare para cada evento o para eventos seleccionados: ![Botones de selección con opciones para recibir cargas para cada evento o eventos seleccionados](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) + - Para cada evento, selecciona **Enviarme todo**. + - Para elegir eventos específicos, selecciona **Dejarme seleccionar eventos individuales**. +11. Si eliges seleccionar eventos individuales, selecciona si se disparará este webhook para una actividad de usuario o de organización. ![Casillas de verificación para eventos de usuario y de organización](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) +12. Confirma que la casilla de verificación **Activo** esté seleccionada (se selecciona por defecto). ![Casilla de verificación Activo seleccionada](/assets/images/enterprise/site-admin-settings/add-global-webhook-active-checkbox.png) +13. Haz clic en **Add webhook** (Agregar webhook). + +### Editar un webhook global + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Al lado del webhook que quieres editar, haz clic en **Editar**. ![Botón Editar al lado de una webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) +6. Actualiza los parámetros del webhook. +7. Haz clic en **Actualizar webhook**. + +### Eliminar un webhook global + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Al lado del webhook que quieres eliminar, haz clic en **Eliminar**. ![Botón Eliminar al lado de una webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) +6. Lee la información sobre cómo eliminar un webhook, luego haz clic en **Sí, eliminar webhook**. ![Casilla emergente con información de advertencia y botón para confirmar la eliminación del webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) + +### Visualizar respuestas y entregas recientes + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. En la lista de webhooks, haz clic en el webhook del que quieres ver las entregas. ![Lista de webhooks con los enlaces para visualizar cada webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) +6. En "Entregas recientes", haz clic en una entrega para ver los detalles. ![Lista de entregas recientes de webhooks con los enlaces para visualizar los detalles](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md new file mode 100644 index 0000000000000..9a2c87dbf58d6 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md @@ -0,0 +1,14 @@ +--- +title: Administrar las organizaciones en tu empresa +redirect_from: + - /enterprise/admin/articles/adding-users-and-teams/ + - /enterprise/admin/categories/admin-bootcamp/ + - /enterprise/admin/user-management/organizations-and-teams + - /enterprise/admin/user-management/managing-organizations-in-your-enterprise +intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares. {% if currentVersion == "github-ae@latest" %}Los usuarios de otras organizaciones pueden acceder a los repositorios internos{% else %}públicos e internos{% endif %} que pertenezcan a una organización diferente, pero solo los miembros de la organización que hayan recibido acceso a los repositorios privados podrán acceder a ellos.' +mapTopic: verdadero +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md b/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md new file mode 100644 index 0000000000000..0ca0c22e73589 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md @@ -0,0 +1,44 @@ +--- +title: Administrar proyectos mediante JIRA +intro: 'Puedes integrar JIRA con {% data variables.product.prodname_enterprise %} para la administración de proyectos.' +redirect_from: + - /enterprise/admin/guides/installation/project-management-using-jira/ + - /enterprise/admin/articles/project-management-using-jira/ + - /enterprise/admin/developer-workflow/managing-projects-using-jira + - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations + - /enterprise/admin/user-management/managing-projects-using-jira +versions: + enterprise-server: '*' +--- + +### Conectar JIRA a una organización {% data variables.product.prodname_enterprise %} + +1. Inicia sesión en tu cuenta de {% data variables.product.prodname_enterprise %} en http[s]://[hostname]/login. +1. En el ángulo superior derecho de cualquier página, haz clic en el icono de ajustes (engranaje) de la cuenta. +1. En la barra lateral izquierda, haz clic en el nombre de tu organización. +1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). +1. En el ángulo superior derecho del cuadro **Organization applications** (Aplicaciones de la organización), haz clic en **Register new application** (Registrar aplicación nueva). +1. Completa los parámetros de la aplicación: + - En el campo **Application name** (Nombre de la aplicación), escribe "JIRA". + - En el campo **Homepage URL** (URL de inicio de sesión), escribe la URL completa de tu instancia JIRA. + - En el campo **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa de tu instancia JIRA. +1. Haz clic en **Register application** (Registrar aplicación). +1. En la parte inferior de la página, observa el **Client ID** (ID de cliente) y **Client Secret** (Secreto de cliente). Necesitarás estos datos para configurar tu instancia JIRA. + +### Configuración de instancia de JIRA + +1. En tu instancia de JIRA, inicia sesión en una cuenta con acceso administrativo. +1. En la parte superior de la página, haz clic en el icono de ajustes (engranaje). +1. En el desplegable de los parámetros, elige **Add-ons** (Adicionales). +1. En la barra lateral izquierda, debajo de **Source control** (Control de origen), haz clic en **DVCS accounts** (Cuentas de DVCS). +1. Haz clic en **Link Bitbucket or GitHub account** (Enlazar cuenta de Bitbucket o GitHub). +1. En el modal **Add New Account** (Agregar nueva cuenta), completa tus parámetros de {% data variables.product.prodname_enterprise %}: + - En el menú desplegable **Host**, elige **GitHub Enterprise**. + - En el campo **Team or User Account** (Cuenta de equipo o usuario), escribe el nombre de tu organización {% data variables.product.prodname_enterprise %} o cuenta personal. + - En el campo **OAuth Key** (Clave OAuth), escribe el ID de cliente de tu aplicación de programador de {% data variables.product.prodname_enterprise %}. + - En el campo **OAuth Secret** (OAuth secreto), escribe el secreto de cliente para tu aplicación de programador de {% data variables.product.prodname_enterprise %}. + - Si no quieres vincular los repositorios nuevos que pertenecen a tu organización o cuenta personal de {% data variables.product.prodname_enterprise %}, quita la marca de selección de **Auto Link New Repositories** (Vincular automáticamente repositorios nuevos). + - Si no quieres habilitar las confirmaciones inteligentes, quita la marca de selección **Enable Smart Commits** (Habilitar confirmaciones inteligentes). + - Da clic en **Agregar**. +1. Revisa los permisos que concedes a tu cuenta de {% data variables.product.prodname_enterprise %} y haz clic en **Authorize application** (Autorizar aplicación). +1. Si es necesario, escribe tu contraseña para continuar. diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md new file mode 100644 index 0000000000000..f27afa34ea40b --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md @@ -0,0 +1,12 @@ +--- +title: Administrar repositorios en tu empresa +intro: 'Puedes administrar la configuración disponible para los administradores de repositorios en tu empresa.' +redirect_from: + - /enterprise/admin/user-management/repositories + - /enterprise/admin/user-management/managing-repositories-in-your-enterprise +mapTopic: verdadero +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md new file mode 100644 index 0000000000000..096ca667ce602 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md @@ -0,0 +1,14 @@ +--- +title: Administrar los usuarios en tu empresa +intro: 'Puedes auditar la actividad de los usuarios y administrar sus configuraciones de usuario.' +redirect_from: + - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ + - /enterprise/admin/user-management/basic-account-settings + - /enterprise/admin/user-management/user-security + - /enterprise/admin/user-management/managing-users-in-your-enterprise +mapTopic: verdadero +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md new file mode 100644 index 0000000000000..41947e2981995 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md @@ -0,0 +1,13 @@ +--- +title: Migrar los datos desde y hacia tu empresa +intro: 'Puedes exportar datos de usuario, organización y repositorio desde {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_dotcom_the_website %}, y posteriormente importar los datos en {% data variables.product.product_location %}.' +mapTopic: verdadero +redirect_from: + - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/ + - /enterprise/admin/categories/migrations-and-upgrades/ + - /enterprise/admin/migrations/overview + - /enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md new file mode 100644 index 0000000000000..e568daed8c247 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Migrar datos a tu empresa +intro: 'Después de generar un archivo de migración, puedes importar los datos a tu instancia de destino del {% data variables.product.prodname_ghe_server %}. Podrás revisar los cambios para detectar posibles conflictos antes de aplicar de manera permanente los cambios a tu instancia de destino.' +redirect_from: + - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise/ + - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server + - /enterprise/admin/migrations/reviewing-migration-data + - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server + - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise/ + - /enterprise/admin/guides/migrations/reviewing-the-imported-data/ + - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise/ + - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/ + - /enterprise/admin/user-management/migrating-data-to-your-enterprise +versions: + enterprise-server: '*' +--- + +### Aplicar los datos importados en {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.ssh-into-target-instance %} + +2. Con el comando `ghe-migrator import`, inicia el proceso de importación. Necesitarás: + * Tu GUID de migración. + * Tu token de acceso personal para autenticación. El token de acceso personal que utilices es solo para autenticación como administrador de sitio, y no requiere ningún alcance específico. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + + ```shell + $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN + + > Comenzando con GitHub::Migrador + > Importación 100 % completa / + ``` + + * {% data reusables.enterprise_migrations.specify-staging-path %} + +### Revisar datos de migración + +De forma predeterminada, `ghe-migrator audit` devuelve todos los registros. También te permite filtrar los registros por: + + * Los tipos de registros. + * El estado de los registros. + +Los tipos de registro coinciden con los encontrados en los [datos migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data). + +### Filtros de tipo de registro + +| Tipo de registro | Nombre del filtro | +| --------------------------------------------------------------- | --------------------------------------------------- | +| Usuarios | `user` | +| Organizaciones | `organization` | +| Repositorios | `repositorio` | +| Equipos | `team` | +| Hitos | `milestone` | +| Tableros de proyecto | `project` | +| Problemas | `issue` | +| Comentarios de propuestas | `comentario_propuesta` | +| Solicitudes de cambios | `solicitud_extracción` | +| Revisiones de solicitudes de extracción | `revisión_solicitud de extracción` | +| Comentarios sobre confirmación de cambios | `comentario_confirmación de cambios` | +| Comentarios sobre revisiones de solicitudes de extracción | `comentarios _revisiones_solicitudes de extracción` | +| Lanzamientos | `release` | +| Medidas adoptadas en las solicitudes de extracción o propuestas | `evento_propuesta` | +| Ramas protegidas | `rama_protegida` | + +### Filtros de estado de registro + +| Estado de registro | Descripción | +| --------------------- | ---------------------------------- | +| `exportar` | El registro se exportará. | +| `importar` | El registro se importará. | +| `asignar` | El registro se asignará. | +| `rename (renombrar)` | El registro se renombrará. | +| `merge` | El registro se fusionará. | +| `exportado` | El registro se exportó con éxito. | +| `importado` | El registro se importó con éxito. | +| `asignado` | El registro se asignó con éxito. | +| `renombrado` | El registro se renombró con éxito. | +| `fusionado` | El registro se fusionó con éxito. | +| `exportación_fallida` | El registro no se pudo exportar. | +| `importación_fallida` | El registro no se pudo importar. | +| `asignación_fallida` | El registro no se pudo asignar. | +| `renombrar_fallido` | El registro no se pudo renombrar. | +| `fusión_fallida` | El registro no se pudo fusionar. | + +### Filtrar registros auditados + +Con el comando de auditoría `ghe-migrator audit` puedes filtrar en función del tipo de registro mediante el indicador `-m`. Del mismo modo, puedes filtrar en el estado de importación mediante el indicador `-s`. El comando se ve de la siguiente manera: + +```shell +$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID +``` + +Por ejemplo, para ver cada organización y equipo importados con éxito, debes ingresar: +```shell +$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID +> model_name,source_url,target_url,state +> organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed +``` + +**Te recomendamos encarecidamente que hagas una auditoría de todas las importaciones que fallaron.** Para ello, ingresa en: +```shell +$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID +> model_name,source_url,target_url,state +> user,https://gh.source/octocat,https://gh.target/octocat,failed +> repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed +``` + +Si tienes alguna duda sobre las importaciones fallidas, comunícate con {% data variables.contact.contact_ent_support %}. + +### Completar la importación en {% data variables.product.prodname_ghe_server %} + +Después de que se aplique tu migración a tu instancia destino y la hayas revisado, desbloquearás los repositorios y los borrarás del origen. Antes de eliminar los datos de origen, se recomienda esperar alrededor de dos semanas para asegurarse de que todo funciona de acuerdo con lo esperado. + +### Desbloquear repositorios en la instancia de destino + +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} + +### Desbloquear repositorios en el origen + +#### Desbloquear los repositorios de una organización en {% data variables.product.prodname_dotcom_the_website %} + +Para desbloquear los repositorios en una organización{% data variables.product.prodname_dotcom_the_website %}, debes enviar una solicitud de `DELETE` al punto final de desbloqueo de migración. Necesitarás: + * Tu token de acceso para autenticación + * El `id` único de la migración + * El nombre del repositorio a desbloquear +```shell +curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ + -H "Accept: application/vnd.github.wyandotte-preview+json" \ + https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock +``` + +#### Borrar los repositorios de una organización en {% data variables.product.prodname_dotcom_the_website %} + +Después de desbloquear los repositorios de organización de {% data variables.product.prodname_dotcom_the_website %} deberás borrar todos los repositorios que migraste previamente utilizando [la terminal de borrado de repositorios](/rest/reference/repos/#delete-a-repository). Necesitarás tu token de acceso para la autenticación: +```shell +curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ + https://api.github.com/repos/orgname/repo_name +``` + +#### Desbloquear repositorios desde una instancia de {% data variables.product.prodname_ghe_server %} + +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} diff --git a/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md new file mode 100644 index 0000000000000..2abc0ae1409d5 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md @@ -0,0 +1,48 @@ +--- +title: Migrar hacia repositorios internos +intro: 'Puedes migrar hacia repositorios internos para unificar la experiencia de innersource para los desarolladores que utilicen tanto {% data variables.product.prodname_ghe_server %} como {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/installation/migrating-to-internal-repositories + - /enterprise/admin/user-management/migrating-to-internal-repositories +permissions: Los administradores de sitio pueden migrar hacia repositorios internos. +versions: + enterprise-server: '>=2.20' +--- + +### Acerca de los repositorios internos + +Los repositorios internos están disponibles desde {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} para obtener más información, consulta "[Acerca de la visibilidad en los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)." + +En lanzamientos futuros de {% data variables.product.prodname_ghe_server %}, ajustaremos la manera en la que funciona la visibilidad de los repositorios para que los conceptos público, interno y privado tengan un significado uniforme para los desarrolladores de {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. + +Para prepararse para estos cambios, si has habilitado el modo privado, puedes ejecutar una migración en tu instancia para convertir los repositorios públicos en internos. Esta migración es opcional actualmente. Esto sirve para permitirte probar los cambios en una instancia no productiva. La migración será obligatoria en el futuro. + +Cuando ejecutas la migración, todos los repositorios públicos propiedad de las organizaciones en tu instancia se convertirán en repositorios internos. En caso de que cualquiera de estos repositorios tenga ramificaciones, estas se convertirán en privadas. Los repositorios privados permanecerán como privados. + +Todos los repositorios públicos propiedad de cuentas de usuario en tu instancia se convertirán en repositorios privados. Si cualquiera de estos repositorios tienen ramificaciones, éstas también se convertirán en privadas. A cada dueño de una ramificación se le otorgarán permisos de lectura para el directorio padre de la misma. + +Se inhabilitará el acceso de lectura anónimo para Git en cada repositorio público que se convierta en interno o privado. + +Si tu visibilidad predeterminada actual para los repositorios es pública, ahora se convertirá en interna. Si la predeterminada es privada, entonces no cambiará. Puedes cambiar esta configuración predeterminada en cualquier momento. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-the-default-visibility-of-new-repositories-in-your-enterprise)". + +La política de creación de repositorios para la instancia cambiará para inhabilitar los repositorios públicos y permitir los privados e internos. Puedes actualizar la política en cualquier momento. Para obtener más información, consulta "[Restringir la creación de repositorios en tu instancia](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance)." + +El script de migración no tendrá efecto si no tienes el modo privado habilitado. + +### Ejecutar la migración + +1. Conecta con el shell administrativo. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." +2. Navega hacia el directorio `/data/github/current`. + ``` + cd /data/github/current + ``` +3. Ejecuta el comando de migración. + ``` + sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log + ``` + +Se mostrará el registro de salida en la terminal y quedará en `/tmp/convert_public_ghes_repos_to_internal.log`. + +### Further reading + +- "[Habilitar el modo privado](/enterprise/admin/installation/enabling-private-mode)" diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md new file mode 100644 index 0000000000000..c7055bfebf0cc --- /dev/null +++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md @@ -0,0 +1,11 @@ +--- +title: Monitorear la actividad en tu empresa +mapTopic: verdadero +redirect_from: + - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance + - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise +versions: + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md new file mode 100644 index 0000000000000..52b47aa42ea9b --- /dev/null +++ b/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md @@ -0,0 +1,19 @@ +--- +title: Asignar un titular legal a un usuario o una organización +intro: 'Puedes asignar un titular legal a un usuario o una organización para garantizar que los repositorios que les pertenezcan no se puedan eliminar de forma permanente desde tu empresa.' +redirect_from: + - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Generalmente, si alguien elimina un repositorio, estará disponible en el disco por 90 días y se puede restablecer mediante el tablero de administración del sitio. Después de los 90 días, el repositorio se purga y se elimina para siempre. Si asignas un titular legal a un usuario o una organización, los repositorios que ellos poseen se pueden restablecer indefinidamente. + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. Haz clic en **Asignar titular legal**. ![Botón Asignar titular legal](/assets/images/enterprise/site-admin-settings/place-legal-hold-button.png) diff --git a/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md new file mode 100644 index 0000000000000..1a4c3fb9cf8a7 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Prepararse para migrar los datos a tu empresa +intro: 'Después de generar un archivo de migración, puedes importar los datos a tu instancia de destino del {% data variables.product.prodname_ghe_server %}. Podrás revisar los cambios para detectar posibles conflictos antes de aplicar de manera permanente los cambios a tu instancia de destino.' +redirect_from: + - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server + - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts + - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts + - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings + - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise/ + - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise +versions: + enterprise-server: '*' +--- + +### Preparar los datos migrados para importarlos a {% data variables.product.prodname_ghe_server %} + +1. Con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copia el archivo de migración generado desde tu instancia u organización de origen a tu {% data variables.product.prodname_ghe_server %} destino: + + ```shell + $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/ + ``` + +{% data reusables.enterprise_installation.ssh-into-target-instance %} + +3. Usa el comando `ghe-migrator prepare` para preparar el archivo para importar en la instancia de destino y generar un nuevo GUID de Migración para que uses en los pasos subsiguientes: + + ```shell + ghe-migrator prepare /home/admin/MIGRATION_GUID.tar.gz + ``` + + * Para comenzar un nuevo intento de importación, ejecuta `ghe-migrator prepare` nuevamente y obtén un nuevo GUID de migración. + * {% data reusables.enterprise_migrations.specify-staging-path %} + +### Generar una lista de conflictos de migración + +1. Con el comando `ghe-migrator conflicts` con el GUID de migración, genera un archivo *conflicts.csv*: + ```shell + $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv + ``` + - Si no se reporta conflicto alguno, puedes importar los datos de forma segura siguiendo los pasos en la sección "[Migrar datos a tu empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)". +2. Si hay conflictos, con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copia *conflicts.csv* a tu computadora local: + ```shell + $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop + ``` +3. Continúa con "[Resolver conflictos de migración o crear asignaciones personalizadas](#resolving-migration-conflicts-or-setting-up-custom-mappings)". + +### Revisar conflictos de migración + +1. Con un editor de texto o [ un software de hoja de cálculo compatible con CSV](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), abre *conflicts.csv*. +2. Con la guía de los ejemplos y las tablas de referencia a continuación, revisa el archivo *conflicts.csv* para asegurarte de que se tomarán las medidas adecuadas al importar. + +El archivo *conflicts.csv* contiene un *mapa de migración* de conflictos y acciones recomendadas. Un mapa de migración enumera tanto los datos que se migran desde el origen como la forma en que los datos se aplicarán al destino. + +| `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | +| --------------- | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- | +| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | +| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `asignar` | +| `repositorio` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename (renombrar)` | +| `team` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` | + +Cada fila de *conflicts.csv* proporciona la siguiente información: + +| Nombre | Descripción | +| -------------------- | -------------------------------------------------------------------- | +| `nombre_modelo` | El tipo de datos que se están cambiando. | +| `url_origen` | La URL fuente de los datos. | +| `url_destino` | La URL de destino esperada de los datos. | +| `recommended_action` | La acción preferida que tomará `ghe-migrator` al importar los datos. | + +#### Asignaciones posibles para cada tipo de registro + +Hay varias acciones de asignación diferentes que `ghe-migrator` puede realizar al transferir datos: + +| `Acción` | Descripción | Modelos aplicables | +| --------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------- | +| `importar` | (predeterminado) Los datos del origen se importan al destino. | Todos los tipos de registro | +| `asignar` | Los datos del origen se reemplazan por los datos existentes en el destino. | Usuarios, organizaciones, repositorios | +| `rename (renombrar)` | Los datos del origen se renombran y luego se copian en el destino. | Usuarios, organizaciones, repositorios | +| `asignar_o_renombrar` | Si el destino existe, asignar a ese destino. De lo contrario, renombrar el modelo importado. | Usuarios | +| `merge` | Los datos del origen se combinan con los datos existentes en el destino. | Equipos | + +**Te recomendamos ampliamente que revises el archivo *conflicts.csv* y que utilices [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) para garantizar que se estén tomando las acciones adecuadas.** Si todo se ve bien, puedes continuar con las acciones para "[Migrar los datos a tu empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)". + + +### Resolver conflictos de migración o crear asignaciones personalizadas + +Si crees que `ghe-migrator` realizará un cambio incorrecto, puedes hacer correcciones cambiando los datos en *conflicts.csv*. Puedes hacer cambios en cualquiera de las filas en *conflicts.csv*. + +Por ejemplo, supongamos que observas que el usuario `octocat` del origen se está asignando a `octocat` en el destino: + +| `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | +| --------------- | ------------------------------------ | ----------------------------------- | -------------------- | +| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | + +Puedes optar por asignar el usuario a un usuario diferente en el destino. Supongamos que sabes que `octocat` en realidad debe ser `monalisa` en el destino. Puedes cambiar la columna `target_url` en *conflicts.csv* a `monalisa`: + +| `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | +| --------------- | ------------------------------------ | ------------------------------------ | -------------------- | +| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `asignar` | + +Como otro ejemplo, si deseas cambiar el nombre del repositorio `octo-org/widgets` a `octo-org/amazing-widgets` en la instancia de destino, cambia la `target_url` a `octo-org/amazing-widgets` y la `recommended_action` a `rename`: + +| `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | +| --------------- | -------------------------------------------- | ---------------------------------------------------- | -------------------- | +| `repositorio` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename (renombrar)` | + +#### Agregar asignaciones personalizadas + +Una situación común durante una migración es que los usuarios migrados tengan diferentes nombres de usuario en el destino que los que tienen en el origen. + +Dada una lista de nombres de usuario en el origen y una lista de nombres de usuario en el destino, puedes crear un archivo CSV con asignaciones personalizadas y luego aplicarlo para garantizar que el nombre de usuario y el contenido de cada usuario se atribuyan correctamente al final de la migración. + +Puedes generar rápidamente un CSV de usuarios que se migran en el formato CSV necesario para aplicar asignaciones personalizadas mediante el comando [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data): + +```shell +$ ghe-migrator audit -m user -g MIGRATION_GUID > users.csv +``` + +Ahora, puedes editar ese CSV e ingresar la nueva URL para cada usuario que quieras asignar o renombrar, y luego actualizar la cuarta columna para `asignar` o `renombrar` según corresponda. + +Por ejemplo, para cambiar el nombre del usuario `octocat` a `monalisa` en el `https://example-gh.target` de destino, debes crear una fila con el siguiente contenido: + +| `nombre_modelo` | `url_origen` | `url_destino` | `state` | +| --------------- | ------------------------------------ | ------------------------------------ | -------------------- | +| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `rename (renombrar)` | + +Se puede usar el mismo proceso para crear asignaciones para cada registro que admita asignaciones personalizadas. Para obtener más información, consulta [nuestra tabla sobre las posibles asignaciones de registro](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type). + +#### Aplicar datos de migración modificados + +1. Después de hacer cambios, usa el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar el *conflicts.csv* modificado (o cualquier otro csv de asignación en el formato correcto) a la instancia de destino: + + ```shell + $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/ + ``` + +2. Vuelve a asignar los datos de migración con el comando `ghe-migrator map`, pasando la ruta al archivo csv modificado y al GUID de migración: + + ```shell + $ ghe-migrator map -i conflicts.csv -g MIGRATION_GUID + ``` + +3. Si el comando `ghe-migrator map -i conflicts.csv -g MIGRATION_GUID` informa que aún existen conflictos, ejecuta nuevamente el proceso de resolución de conflictos de migración. diff --git a/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md new file mode 100644 index 0000000000000..0a2d2c99a85ee --- /dev/null +++ b/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md @@ -0,0 +1,20 @@ +--- +title: Impedir que los usuarios creen organizaciones +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: 'Puedes prevenir que los usuarios creen organizaciones en tu empresa.' +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.enterprise-accounts.access-enterprise %} +{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. En "Los usuarios pueden crear organizaciones", usa el menú desplegable y haz clic en **Activado** o **Desactivado**. ![Desplegable Los usuarios pueden crear organizaciones](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png) diff --git a/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md new file mode 100644 index 0000000000000..8fb320fed2067 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md @@ -0,0 +1,51 @@ +--- +title: Promover o degradar a un administrador del sitio +redirect_from: + - /enterprise/admin/articles/promoting-a-site-administrator/ + - /enterprise/admin/articles/demoting-a-site-administrator/ + - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator +intro: 'Los administradores del sitio pueden promover cualquier cuenta de usuarios normales a un administrador del sitio, así como degradar a otros administradores del sitio a usuarios normales.' +versions: + enterprise-server: '*' +--- + +{% tip %} + +**Nota:** Si [ la sincronización LDAP está activada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) y se establece el atributo `Administrators group` cuando [se configura el acceso LDAP para usuarios](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance), estos usuarios tendrán automáticamente acceso de administrador del sitio para tu instancia. En este caso, no puedes promover usuarios manualmente con los siguientes pasos, debes agregarlos al grupo de administradores LDAP. + +{% endtip %} + +Para obtener información sobre cómo promover un usuario a un propietario de la organización, consulta la sección `ghe-org-admin-promote` de "[Utilidades de línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-admin-promote)". + +### Promover un usuario desde los parámetros de empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.enterprise-accounts.administrators-tab %} +5. En la esquina superior derecha de la página, haz clic en **Agregar propietario**. ![Botón para agregar un administrador](/assets/images/help/business-accounts/business-account-add-admin-button.png) +6. En el campo Buscar, escribe el nombre del usuario y haz clic en **Agregar**. ![Campo de búsqueda para agregar un administrador](/assets/images/help/business-accounts/business-account-search-to-add-admin.png) + +### Degradar un administrador del sitio desde los parámetros de empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.enterprise-accounts.administrators-tab %} +1. En la esquina superior izquierda de la página, en el campo de búsqueda "Find an administrator" (Encontrar un administrador), escribe el nombre de usuario de la persona que deseas degradar. ![Campo de búsqueda para encontrar un administrador](/assets/images/help/business-accounts/business-account-search-for-admin.png) + +1. En los resultados de búsqueda, encuentra el nombre de usuario de la persona que quieres bajar de rango y luego utiliza el menú desplegable de {% octicon "gear" %} y selecciona **Eliminar propietario**. ![Eliminar de la opción de empresa](/assets/images/help/business-accounts/demote-admin-button.png) + +### Promover un usuario desde la línea de comandos + +1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) en tu aparato. +2. Ejecuta [ghe-user-promote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-promote) con el nombre de usuario a promover. + ```shell + $ ghe-user-promote username + ``` + +### Degradar un administrador del sitio desde la línea de comandos + +1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) en tu aparato. +2. Ejecuta [ghe-user-demote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-demote) con el nombre de usuario a degradar. + ```shell + $ ghe-user-demote username + ``` \ No newline at end of file diff --git a/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md b/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md new file mode 100644 index 0000000000000..72ce162f4a421 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md @@ -0,0 +1,19 @@ +--- +title: Reconstruir datos de contribuciones +intro: Es posible que necesites reconstruir los datos de contribuciones para vincular las confirmaciones de cambios a una cuenta de usuario. +redirect_from: + - /enterprise/admin/articles/rebuilding-contributions-data/ + - /enterprise/admin/user-management/rebuilding-contributions-data +versions: + enterprise-server: '*' +--- + +Siempre que se sube una confirmación de cambios a {% data variables.product.prodname_enterprise %}, se vincula a una cuenta de usuario, si ambas están asociadas con la misma dirección de correo electrónico. Sin embargo, las confirmaciones de cambio existentes *no* se vinculan de forma retroactiva cuando un usuario registra una dirección de correo electrónico nueva o crea una cuenta nueva. + +1. Visita la página de perfil de usuario. +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. En el lado izquierdo de la página, haz clic en **Administrar**. ![Pestaña Administrar](/assets/images/enterprise/site-admin-settings/admin-tab.png) +4. En **Datos de contribuciones**, haz clic en **Reconstruir**. ![Botón Reconstruir](/assets/images/enterprise/site-admin-settings/rebuild-button.png) + +{% data variables.product.prodname_enterprise %} ahora comenzará jobs en segundo plano para volver a enlazar las confirmaciones con esa cuenta de usuario. + ![Trabajos de reconstrucción en cola](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png) diff --git a/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md new file mode 100644 index 0000000000000..41f79d013ba7a --- /dev/null +++ b/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md @@ -0,0 +1,42 @@ +--- +title: Eliminar usuarios de equipos y organizaciones +intro: 'Si un miembro de tu organización ya no necesita acceso a ciertos repositorios, puedes eliminarlo del equipo que permite ese acceso. Si un miembro de tu organización ya no necesita acceso a ningún repositorio que le pertenezca a tu organización, puedes eliminarlo de la organización.' +redirect_from: + - /enterprise/admin/user-management/removing-users-from-teams-and-organizations +versions: + enterprise-server: '*' +--- + +Solo los propietarios o los administradores del equipo pueden eliminar miembros de la organización. Cuando se elimina un usuario de un equipo o una organización, sus propuestas, solicitudes de extracción y comentarios en los repositorios de la organización permanecen intactos y siguen siendo atribuidos al usuario. + +{% warning %} + +**Advertencia**: cuando eliminas un usuario de una organización, perderán el acceso a cualquier bifurcación privada que tengan en los **repositorios privados** de tu organización. Puede seguir teniendo copias locales de esas bifurcaciones. Sin embargo, no podrá sincronizarlas con los repositorios de tu organización. Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. Si el usuario eliminado de tu organización era un miembro de la organización, su acceso a las bifurcaciones privadas de los repositorios de la organización se pueden restablecer si el usuario es [reinstalado como un miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses de haber sido eliminado de una organización. + +{% endwarning %} + +### Eliminar un miembro del equipo + +{% warning %} + +**Nota:** {% data reusables.enterprise_management_console.badge_indicator %} + +Para eliminar un miembro existente de un equipo sincronizado a un grupo LDAP, comunícate con tu administrador LDAP. + +{% endwarning %} + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Selecciona la persona o las personas que quieres eliminar. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) +5. Arriba de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Remove from team** (Eliminar del equipo). ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) + +### Eliminar un usuario de una organización + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Al lado del nombre de los usuarios que quieras eliminar de la organización, haz clic en la casilla de verificación. ![Casilla de verificación Eliminar usuario](/assets/images/help/organizations/Organization-remove-user.png) +5. En la parte superior de la página, debajo del nombre de la organización, haz clic en **Eliminar de la organización**. ![Botón para eliminar de la organización ](/assets/images/help/organizations/Organization-remove-from-organization-button.png) + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} diff --git a/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md new file mode 100644 index 0000000000000..33604f49286d6 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md @@ -0,0 +1,63 @@ +--- +title: Solicitar autenticación de dos factores para una organización +intro: 'Le puedes solicitar a los miembros de la organización y a los colaboradores externos que activen la autenticación de dos factores para sus cuentas personales en una organización, para que sea más difícil para los actores maliciosos acceder a los parámetros y los repositorios de una organización.' +redirect_from: + - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization +versions: + enterprise-server: '*' +--- + +Cuando utilizas LDAP o la autenticación integrada, la autenticación bifactorial será compatible en {% data variables.product.product_location %}. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada. + +{% data reusables.enterprise_user_management.external_auth_disables_2fa %} + +Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/github/authenticating-to-github/about-two-factor-authentication)". + +### Requisitos para aplicar la autenticación de dos factores + +Antes de poder solicitarle a los miembros de la organización y a los colaboradores externos que usen 2FA, debes [activar la autenticación de dos factores](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa/) para tu cuenta personal propia. + +{% warning %} + +**Advertencias:** + +- Cuando solicitas la autenticación de dos factores, los miembros y los colaboradores externos (incluidas cuentas bot) que no usan la 2FA serán eliminados de la organización y perderán acceso a sus repositorios, incluidas sus bifurcaciones de los repositorios privados. Si activan la 2FA para su cuenta personal dentro de los tres meses de haber sido eliminados de la organización, puedes [reinstalar sus parámetros y sus privilegios de acceso](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization). +- Cuando se solicita la 2FA, los miembros de la organización o los colaboradores externos que desactiven la 2FA se eliminarán automáticamente de la organización. +- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización. + +{% endwarning %} + +Antes de solicitar el uso de la autenticación de dos factores, te recomendamos notificar a los miembros de la organización y a los colaboradores externos y pedirles que configuren la 2FA para sus cuentas. Puedes [ ver si los miembros y los colaboradores externos ya usan 2FA](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) en la pestaña Personas de una organización. + +{% data reusables.profile.enterprise_access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.require_two_factor_authentication %} +{% data reusables.organizations.removed_outside_collaborators %} + +### Ver las personas que se eliminaron de tu organización + +Para ver las personas que fueron automáticamente eliminadas de tu organización por no cumplir cuando solicitaste la autenticación de dos factores, puedes [buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log/) usando el campo de búsqueda `reason:two_factor_requirement_non_compliance`. + +{% data reusables.audit_log.octicon_icon %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.audit_log.audit_log_sidebar_for_site_admins %} +4. Ingresa tu consulta de búsqueda usando `reason:two_factor_requirement_non_compliance`. ![Evento de registro de auditoría de herramientas de plantilla que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) Para limitar tu búsqueda para: + - Miembros de organizaciones eliminados, ingresa `action:org.remove_member AND reason:two_factor_requirement_non_compliance` + - Colaboradores externos eliminados, ingresa `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` + + También puedes ver las personas eliminadas de una organización en particular usando el nombre de la organización en tu búsqueda: + - `org:octo-org AND reason:two_factor_requirement_non_compliance` +5. Da clic en **Buscar**. + +### Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización + +Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. + +### Further reading + +- "[Ver si los usuarios de tu organización tienen la 2FA activada](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Asegurar tu cuenta con autenticación de dos factores (2FA)](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstalar el acceso a tu organización para un colaborador externo antiguo](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/es-ES/content/admin/user-management/searching-the-audit-log.md b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md new file mode 100644 index 0000000000000..361651f5386f5 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md @@ -0,0 +1,45 @@ +--- +title: Buscar el registro de auditoría +intro: 'Los administradores de sitio pueden buscar en una lista extensa de acciones auditadas en la empresa.' +redirect_from: + - /enterprise/admin/articles/searching-the-audit-log/ + - /enterprise/admin/installation/searching-the-audit-log + - /enterprise/admin/user-management/searching-the-audit-log +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Buscar sintaxis de consultas + +Redacta una consulta de búsqueda de uno o más pares de clave-valor separados por operadores lógicos y/o. + +| Clave | Valor | +| ------------------------:| ---------------------------------------------------------------------------- | +| `actor_id` | ID de la cuenta de usuario que inició la acción | +| `actor (actor)` | Nombre de la cuenta de usuario que inició la acción | +| `oauth_app_id` | ID de la aplicación OAuth asociada con la acción | +| `Acción` | Nombre de la acción auditada | +| `user_id` | ID del usuario afectado por la acción | +| `user` | Nombre del usuario afectado por la acción | +| `repo_id` | ID del repositorio afectado por la acción (si corresponde) | +| `repo` | Nombre del repositorio afectado por la acción (si corresponde) | +| `actor_ip` | Dirección IP desde donde se inició la acción | +| `created_at (creado en)` | Momento en el cual ocurrió la acción | +| `from` | Vista desde donde se inició la acción | +| `note` | Información variada de evento específico (en texto simple o en formato JSON) | +| `org` | Nombre de la organización afectada por la acción (si corresponde) | +| `org_id` | ID de la organización afectada por la acción (si corresponde) | + +Por ejemplo, para ver todas las acciones que afectaron el repositorio `octocat/Spoon-Knife` desde el inicio de 2017: + + `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` + +Para encontrar una lista completa de acciones, consulta la sección "[Acciones auditadas](/admin/user-management/audited-actions)". + +### Buscar el registro de auditoría + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +4. Escribe una consulta de búsqueda. ![Consulta de búsqueda](/assets/images/enterprise/site-admin-settings/search-query.png) diff --git a/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md new file mode 100644 index 0000000000000..dc918269e9fcb --- /dev/null +++ b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md @@ -0,0 +1,86 @@ +--- +title: Suspender y anular suspensión de usuarios +redirect_from: + - /enterprise/admin/articles/suspending-a-user/ + - /enterprise/admin/articles/unsuspending-a-user/ + - /enterprise/admin/articles/viewing-suspended-users/ + - /enterprise/admin/articles/suspended-users/ + - /enterprise/admin/articles/suspending-and-unsuspending-users/ + - /enterprise/admin/user-management/suspending-and-unsuspending-users +intro: 'Si un usuario se va o se traslada a un lugar diferente de la empresa, deberías eliminar o modificar su posibilidad de acceder a {% data variables.product.product_location %}.' +versions: + enterprise-server: '*' +--- + +Puedes suspender las cuentas de usuario de {% data variables.product.prodname_ghe_server %} de aquellos que abandonen la compañía para abrir licencias de usuario en tu licencia de {% data variables.product.prodname_enterprise %} preservando las propuestas, comentarios, repositorios, gists y otros datos que hayan creado. Los usuarios suspendidos no pueden iniciar sesión en tu instancia, y no pueden subir ni extraer un código. + +Cuando suspendes un usuario, la modificación entra en efecto de inmediato sin notificar al usuario. Si el usuario intenta extraer o subir un repositorio, recibirá el siguiente error: + +```shell +$ git clone git@[hostname]:john-doe/test-repo.git +Cloning into 'test-repo'... +ERROR: Tu cuenta está suspendida. Consulta a tu administrador de instalación. +fatal: El extremo remoto colgó inesperadamente +``` + +Antes de suspender administradores del sitio, debes degradarlos a usuarios normales. Para obtener más información, consulta "[Promover o degradar a un administrador del sitio](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)." + +{% tip %} + +**Nota:** Si [la sincronización LDAP está activada](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) para {% data variables.product.product_location %}, los usuarios son suspendidos automáticamente cuando son eliminados del servidor de directorios LDAP. Cuando la sincronización LDAP está activada para tu instancia, los métodos de suspensión de usuario normal están desactivados. + +{% endtip %} + +### Suspender un usuario desde el tablero de administrador de usuarios + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. En "Suspensión de cuenta", en el cuadro rojo de Zona de peligro, haz clic en **Suspender**. ![Botón Suspender](/assets/images/enterprise/site-admin-settings/suspend.png) +6. Indica un motivo para suspender al usuario. ![Motivo de suspensión](/assets/images/enterprise/site-admin-settings/suspend-reason.png) + +### Anular la suspensión de un usuario desde el tablero de administrador de usuarios + +Como cuando se suspende un usuario, anular la suspensión entra en efecto de inmediato. El usuario no será notificado. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. En la barra lateral de la izquierda, haz clic en **Usuarios suspendidos**. ![Pestaña Usuarios suspendidos](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) +2. Haz clic en el nombre de la cuenta de usuario de la que quieres anular la suspensión. ![Usuario suspendido](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +4. En "Suspensión de cuenta", en el cuadro rojo de Zona de peligro, haz clic en **Anular suspensión**. ![Botón Anular suspensión](/assets/images/enterprise/site-admin-settings/unsuspend.png) +5. Indica un motivo para anular la suspensión del usuario. ![Motivo de anulación de suspensión](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) + +### Suspender un usuario desde la línea de comandos + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Ejecuta [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) con el nombre de usuario a suspender. + ```shell + $ ghe-user-suspend username + ``` + +### Crear un mensaje personalizado para usuarios suspendidos + +Puedes crear un mensaje personalizado que los usuarios suspendidos verán cuando intenten iniciar sesión. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. Haz clic en **Agregar mensaje**. ![Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-message.png) +6. Escribe tu mensaje en el cuadro **Mensaje para usuario suspendido**. Puedes escribir Markdown o usar la barra de herramientas Markdown para diseñar tu mensaje. ![Mensaje para usuario suspendido](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) +7. Haz clic en el botón **Vista previa** en el campo **Mensaje para usuario suspendido** para ver el mensaje representado. ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) +8. Revisar el mensaje presentado. ![Mensaje presentado de usuario suspendido](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %} + +### Anular la suspensión de un usuario desde la línea de comandos + +{% data reusables.enterprise_installation.ssh-into-instance %} +2. Ejecuta [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) con el nombre de usuario a anular la suspensión. + ```shell + $ ghe-user-unsuspend username + ``` + +### Further reading +- "[Suspender a un usuario](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/es-ES/content/admin/user-management/troubleshooting-service-hooks.md b/translations/es-ES/content/admin/user-management/troubleshooting-service-hooks.md new file mode 100644 index 0000000000000..0518d690b78e9 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/troubleshooting-service-hooks.md @@ -0,0 +1,39 @@ +--- +title: Solución de problemas con ganchos de servicio +intro: 'Si las cargar no se están entregando, comprueba estos problemas comunes.' +redirect_from: + - /enterprise/admin/articles/troubleshooting-service-hooks/ + - /enterprise/admin/developer-workflow/troubleshooting-service-hooks + - /enterprise/admin/user-management/troubleshooting-service-hooks +versions: + enterprise-server: '*' + github-ae: '*' +--- + +### Obtener información sobre las entregas + +Puedes buscar información para la última respuesta de todas las entregas de ganchos de servicio en cualquier repositorio. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Explorar en el repositorio que estás investigando. +3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. ![Detalles de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png) +5. En **Remote Calls** (Llamadas remotas), verás los encabezados que se usaron al publicar en el servidor remoto junto con la respuesta que el servidor remoto volvió a enviar a tu instalación. + +### Ver la carga + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Explorar en el repositorio que estás investigando. +3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. +5. Da clic en **Entrega**. ![Ver la carga](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png) + +### Ver entregas anteriores + +Las entregas se almacenan durante 15 días. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Explorar en el repositorio que estás investigando. +3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. +5. Para ver otras entregas para ese gancho específico, haz clic en **More for this Hook ID** (Más para este ID de gancho): ![Ver más entregas](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png) diff --git a/translations/es-ES/content/admin/user-management/viewing-push-logs.md b/translations/es-ES/content/admin/user-management/viewing-push-logs.md new file mode 100644 index 0000000000000..d2cb7abd707a7 --- /dev/null +++ b/translations/es-ES/content/admin/user-management/viewing-push-logs.md @@ -0,0 +1,38 @@ +--- +title: Ver registros de subidas +intro: 'Los administradores de sitio pueden ver una lista de operaciones de subida de git para cualquier repositorio en la empresa.' +redirect_from: + - /enterprise/admin/articles/viewing-push-logs/ + - /enterprise/admin/installation/viewing-push-logs + - /enterprise/admin/user-management/viewing-push-logs +versions: + enterprise-server: '*' + github-ae: '*' +--- + +Las entradas de registro de subida muestran: + +- Quién inició la subida +- Si fue un empuje forzado o no +- La rama a la que alguien subió +- El protocolo utilizado para subir +- La dirección IP inicial +- El cliente Git utilizado para subir +- Los hashes SHA de antes y después de la operación + +### Ver registros de subida de un repositorio + +1. Navegar a un repositorio. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.security-tab %} +4. En la barra lateral izquierda, haz clic en **Push Log (Registro de subida)**. ![Pestaña de registro de subida](/assets/images/enterprise/site-admin-settings/push-log-tab.png) + +{% if enterpriseServerVersions contains currentVersion %} +### Ver registros de subida de un repositorio en la línea de comando + +1. SSH en tu aparato. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." +2. En el repositorio Git adecuado, abre el archivo de registro de auditoría: + ```shell + ghe-repo owner/repository -c "less audit_log" + ``` +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop.md new file mode 100644 index 0000000000000..a9396563353f8 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop.md @@ -0,0 +1,30 @@ +--- +title: Agregar un repositorio desde tu equipo local a GitHub Desktop +intro: 'Puedes agregar cualquier repositorio Git a {% data variables.product.prodname_desktop %}, incluso si no es un repositorio {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** Puedes agregar un repositorio Git desde tu equipo local hasta GitHub Destktop arrastrando la carpeta a la ventana {% data variables.product.prodname_desktop %}. Si arrastras múltiples carpetas Git a {% data variables.product.prodname_desktop %} al mismo tiempo, cada carpeta se agregará como un repositorio Git individual. + +{% endtip %} + +{% mac %} + +1. En el menú **File** (Archivo), haz clic en **Add Local Repository** (Agregar repositorio local). ![Agrega la opción de menú Local Repository (Repositorio local)](/assets/images/help/desktop/add-local-repository-mac.png) +2. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta el repositorio local que deseas agregar. ![El campo Local Path en la app Mac](/assets/images/help/desktop/add-repo-choose-button-mac.png) +4. Haz clic en **Add Repository** (Agregar repositorio). ![El botón Add repository (Agregar repositorio) en la app Mac](/assets/images/help/desktop/add-repository-button-mac.png) + +{% endmac %} + +{% windows %} + +1. En el menú **File** (Archivo) haz clic en **Add Local Repository** (Agregar repositorio local). ![Agrega la opción de menú Local Repository (Repositorio local)](/assets/images/help/desktop/add-local-repository-windows.png) +2. Haz clic en **Choose...** (Elegir) y, a través de Windows Explorer, desplázate hasta el repositorio local que deseas agregar. ![El campo Local Path (Ruta local) en la app Windows](/assets/images/help/desktop/add-repo-choose-button-win.png) +4. Haz clic en **Add repository** (Agregar repositorio). ![El botón Add repository (Agregar repositorio) en la app Windows](/assets/images/help/desktop/add-repository-button-windows.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-an-existing-project-to-github-using-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-an-existing-project-to-github-using-github-desktop.md new file mode 100644 index 0000000000000..1a7aeffcbaa5f --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-an-existing-project-to-github-using-github-desktop.md @@ -0,0 +1,32 @@ +--- +title: Agregar un proyecto existente a GitHub usando el GitHub Desktop +intro: 'Puedes agregar un repositorio Git existente a {% data variables.product.prodname_dotcom %} usando {% data variables.product.prodname_desktop %}.' +redirect_from: + - /desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop +versions: + free-pro-team: '*' +--- + +{% mac %} + +{% data reusables.git.remove-git-remote %} +2. [Agrega el repositorio al GitHub Desktop Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/). +{% data reusables.desktop.publish-repository %} +4. Escribe el nombre deseado del repositorio en el campo **Name** (Name) o usa el nombre de repositorio local actual predeterminado. ![El campo Name (Nombre)](/assets/images/help/desktop/publish-repository-name-mac.png) +5. Para publicar un repositorio público, quita la marca de selección de **Keep this code private**. ![Marca la casilla de verificación privada de este código](/assets/images/help/desktop/publish-repository-private-checkbox-mac.png) +6. Escoge la organización en el **Organization** (Organización) desplegable donde deseas publicar el repositorio, o selecciona **None** (Ninguno) para publicar el repositorio en tu cuenta personal. ![Desplegable de la organización](/assets/images/help/desktop/publish-repository-org-dropdown-mac.png) +7. Haz clic en el botón **Publish Repository** (Publicar repositorio). ![El botón Publish repository (Publicar repositorio) en el cuadro de diálogo Publish Repository (Publicar repositorio)](/assets/images/help/desktop/publish-repository-dialog-button-mac.png) + +{% endmac %} + +{% windows %} + +{% data reusables.git.remove-git-remote %} +2. [Agrega el repositorio al GitHub Desktop Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/). +{% data reusables.desktop.publish-repository %} +4. Escribe el nombre deseado del repositorio en el campo **Name** (Name) o usa el nombre de repositorio local actual predeterminado. ![El campo Name (Nombre)](/assets/images/help/desktop/publish-repository-name-win.png) +5. Para publicar un repositorio público, quita la marca de selección de **Keep this code private**. ![Marca la casilla de verificación privada de este código](/assets/images/help/desktop/publish-repository-private-checkbox-win.png) +6. Escoge la organización en el **Organization** (Organización) desplegable donde deseas publicar el repositorio, o selecciona **None** (Ninguno) para publicar el repositorio en tu cuenta personal. ![Desplegable de la organización](/assets/images/help/desktop/publish-repository-org-dropdown-win.png) +7. Haz clic en el botón **Publish Repository** (Publicar repositorio). ![El botón Publish repository (Publicar repositorio) en el cuadro de diálogo Publish repository (Publicar repositorio)](/assets/images/help/desktop/publish-repository-dialog-button-win.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md new file mode 100644 index 0000000000000..ff8247faf36d8 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md @@ -0,0 +1,10 @@ +--- +title: Agregar y clonar repositorios +intro: 'Añadir repositorios existentes desde su equipo local a {% data variables.product.prodname_desktop %}o clonar repositorios desde {% data variables.product.product_name %}.' +mapTopic: verdadero +redirect_from: + - /desktop/contributing-to-projects/adding-and-cloning-repositories +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md new file mode 100644 index 0000000000000..937a43c59ca4c --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md @@ -0,0 +1,25 @@ +--- +title: Cambiar una URL remota desde el GitHub Desktop +intro: 'Puedes cambiar la URL remota para un repositorio en el que estés trabajando {% data variables.product.prodname_desktop %}. Es posible que puedas hacerlo si se ha cambiado el nombre, o si el nombre de usuario o la organización que posee el repositorio ha cambiado.' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop +versions: + free-pro-team: '*' +--- + +{% mac %} + +1. In the **Repository** menu, click **Repository Settings...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-mac.png) +2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-mac.png) +3. Haz clic en **Save ** (guardar). ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-mac.png) + +{% endmac %} + +{% windows %} + +1. In the **Repository** menu, click **Repository settings...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-win.png) +2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-win.png) +3. Haz clic en **Save ** (guardar). ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-win.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md new file mode 100644 index 0000000000000..22ddc52e58c1f --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop.md @@ -0,0 +1,52 @@ +--- +title: Cómo clonar un repositorio desde GitHub hasta GitHub Desktop +intro: 'Puedes usar {% data variables.product.prodname_dotcom %} para clonar repositorios remotos a {% data variables.product.prodname_desktop %}.' +redirect_from: + - /desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** También puede usar {% data variables.product.prodname_desktop %} para clonar repositorios que existen en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Cómo clonar un repositorio desde {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)." + +{% endtip %} + +{% mac %} + +1. Ingresa en + +{% data variables.product.product_location %} y {% data variables.product.prodname_desktop %} antes de que comiences a clonar. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir) en la pestaña URL](/assets/images/help/desktop/clone-choose-button-url-mac.png) + + {% note %} + + **Nota:** Si el repositorio está configurado para usar LFS, se te pedirá que inicies {% data variables.large_files.product_name_short %}. + + {% endnote %} + +5. Haz clic en **Clone**. ![El botón para clonar en la pestaña URL](/assets/images/help/desktop/clone-button-url-mac.png) + +{% endmac %} + +{% windows %} + +1. Ingresa en + +{% data variables.product.product_location %} y {% data variables.product.prodname_desktop %} antes de que comiences a clonar. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. Haz clic en **Choose...** (Elegir...) y, a través de Windows Explorer, desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-url-win.png) + + {% note %} + + **Nota:** Si el repositorio está configurado para usar LFS, se te pedirá que inicies {% data variables.large_files.product_name_short %}. + + {% endnote %} + +5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-url-win.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md new file mode 100644 index 0000000000000..24f7b6ce8eeba --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -0,0 +1,47 @@ +--- +title: Cómo clonar y bifurcar repositorios desde GitHub Desktop +intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para clonar y ramificar los repositorios que están en {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop + - /desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop +versions: + free-pro-team: '*' +--- + +### Clonar repositorios +Los repositorios en {% data variables.product.prodname_dotcom %} son remotos. Puedes clonar repositorios públicos de otros dueños. Puedes clonar tu propio repositorio para crear una copia local en tu computadora y sincronizarla entre las dos ubicaciones. + +También puedes clonar un repositorio directamente desde {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. Para obtener más información, visita "[Cómo clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". + +{% mac %} + +{% data reusables.desktop.choose-clone-repository %} + ![Clonar opción de menú en la aplicación Mac](/assets/images/help/desktop/clone-file-menu-mac.png) +{% data reusables.desktop.cloning-location-tab %} + ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-mac.png) +{% data reusables.desktop.cloning-repository-list %} + ![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-mac.png) +4. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-mac.png) +5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.choose-clone-repository %} + ![Opción Clone menu (Clonar menú) en la app de Windows](/assets/images/help/desktop/clone-file-menu-windows.png) +{% data reusables.desktop.cloning-location-tab %} + ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-win.png) +{% data reusables.desktop.cloning-repository-list %} + ![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-win.png) +4. Haz clic en **Choose...** (Elegir...) y, a través de Windows Explorer, desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-win.png) +5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png) + +{% endwindows %} + +### Ramificar repositorios +Puedes utilizar {% data variables.product.prodname_desktop %} para crear una ramificación del repositorio y contribuir con un proyecto en donde no tengas privilegios de escritura. Los cambios en tu ramificación no afectarán al repositorio original. Puedes confirmar los cambios en tu ramificación y generar una solicitud de extracción del repositorio original con los cambios que propones. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)." + +1. Si clonaste un repositorio en donde no tienes privilegios de escritura, intenta confirmar los cambios, {% data variables.product.prodname_desktop %} enviará una alerta de que "No cuentas con privilegios de escritura para el **REPOSITORIO**". Da clic en **crear una ramificación**. ![Crear un enlace para la ramificación](/assets/images/help/desktop/create-a-fork.png) +3. Da clic en **Ramificar este repositorio**. ![Botón para ramificar este repositorio](/assets/images/help/desktop/fork-this-repo-button.png) +4. Para ver tu ramificación en {% data variables.product.prodname_dotcom %}, da clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom %} y posteriormente en **Tus repositorios**. ![Enlace a tus repositorios](/assets/images/help/profile/your-repositories.png) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md new file mode 100644 index 0000000000000..ea05193135399 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -0,0 +1,99 @@ +--- +title: Confirmar y revisar cambios en su proyecto +intro: '{% data variables.product.prodname_desktop %} registra todos los cambios a medida que los editas. Puedes decidir cómo agrupar los cambios para crear confirmaciones significativas.' +redirect_from: + - /desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project +versions: + free-pro-team: '*' +--- + +### Acerca de las confirmaciones + +{% data reusables.commits.about-commits %} También puedes agregar un coautor en cualquier confirmación en la que colabores. + +{% data reusables.desktop.update-email-address %} Para obtener más información, consulta la sección ["Configurar Git para GitHub Desktop](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop)". + +### 1. Elegir una rama y realizar cambios + +1. [Crea una rama nueva](/desktop/guides/contributing-to-projects/managing-branches), o selecciona una rama existente dando clic + +{% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** en la barra de herramientas y seleccionando la rama de la lista. + ![Despliega el menú para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down.png) +{% data reusables.desktop.make-changes %} + +### 2. Seleccionar cambios para incluirlos en una confirmación + +A medida que realizas cambios en los archivos en tu editor de texto y que los guardas localmente, también verás los cambios en {% data variables.product.prodname_desktop %}. + +* El icono rojo {% octicon "diff-removed" aria-label="The diff removed icon color-red" %} hace referencia a los archivos eliminados. +* El icono amarillo {% octicon "diff-modified" aria-label="The diff modified icon color-yellow" %} hace referencia a los archivos modificados. +* El icono verde {% octicon "diff-added" aria-label="The diff added icon color-green" %} hace referencia a los archivos agregados. +* Para acceder a los cambios acumulados, haz clic en **Stashed Changes** (Cambios acumulados). ![Opción de cambios acumulados](/assets/images/help/desktop/stashed-changes.png) +* {% data reusables.desktop.commit-all-desc %}![Selecciona la casilla de verificación para confirmar todos los archivos cambiados](/assets/images/help/desktop/commit-all.png) +* {% data reusables.desktop.commit-some-desc %}![Selecciona las casillas de verificación junto a los archivos que deseas confirmar](/assets/images/help/desktop/commit-some.png) + +#### Crear una confirmación parcial + +Si un archivo contiene varios cambios pero solo quieres que algunos de ellos se incluyan en una confirmación, puedes crear una confirmación parcial. El resto de los cambios permanecerán intactos, por lo que puedes realizar confirmaciones y modificaciones adicionales. Esto permite realizar confirmaciones separadas, significativas, como mantener cambios de interrupción de línea en una confirmación separada desde cambios en el código o la prosa. + +{% note %} + +**Nota:** Las muestras de diffs separadas se encuentran actualmente en beta y están sujetas a cambios. + +{% endnote %} + +1. Para elegir cómo se muestran tus cambios, en la esquina superior derecha del archivo que presenta estos cambios, utiliza el {% octicon "gear" aria-label="The Gear icon" %} para seleccionar **Unificada** o **Dividida**. ![Icono de engrane con diffs unificados y divididos](/assets/images/help/desktop/gear-diff-select.png) +2. Para excluir de tu confirmación las líneas que cambiaron, da clic en una o más de ellas para que las azules desaparezcan. Las líneas que aún se resalten en azul se incluirán en la confirmación. ![Líneas no seleccionadas en un archivo](/assets/images/help/desktop/partial-commit.png) + +### 3. Descartar cambios +Si retiraste la confirmación de los cambios que no quieres mantener, puedes descartarlos. Esto eliminará los cambios de los archivos en tu computadora. Puedes descartar todos los cambios que dejaste de confirmar en uno o más archivos, o puedes descartar las líneas específicas que agregaste. + +Los cambios que descartas se guardan en un archivo con fecha en la sección de basura. Puedes recuperar los cambios que descartaste antes de que se vacíe la basura. + +#### Descartar cambios en uno o más archivos + +{% data reusables.desktop.select-discard-files %} +{% data reusables.desktop.click-discard-files %} + ![Opción Discard Changes (Descartar cambios) en el menú contextual](/assets/images/help/desktop/discard-changes-mac.png) +{% data reusables.desktop.confirm-discard-files %} + ![Botón Discard Changes (Descartar cambios) en el cuadro de diálogo de confirmación](/assets/images/help/desktop/discard-changes-confirm-mac.png) + +#### Descartar los cambios en una o más líneas +Puedes descartar una o más líneas que hayan cambiado y que se hayan dejado de confirmar. + +{% note %} + +**Nota:** Se inhabilita la capacidad para descartar líneas sencillas en los grupos de cmabios que agreguen y eliminen líneas. + +{% endnote %} + +Para descartar una línea que se haya agregado, en la lista de líneas que cambiaron, da clic derecho sobre aquella que quieras descartar y selecciona **Descargar línea agregada**. + + ![Descartar una línea sencilla en el diálogo de confirmación](/assets/images/help/desktop/discard-single-line.png) + +Para descartar un grupo de líneas que cambiaron, da clic derecho en la barra vertical a la derecha de los números de línea para aquellas líneas que quieras descartar y luego selecciona **Descartar líneas agregadas**. + + ![Descartar un grupo de líneas agregadas en el diálogo de confirmación](/assets/images/help/desktop/discard-multiple-lines.png) + + +### 4. Escribir un mensaje de confirmación y subir los cambios + +Una vez que estés satisfecho con los cambios que elegiste incluir en tu confirmación, escribe tu mensaje de confirmación y sube los cambios. Si has colaborado en una confirmación, también puedes contribuir en una confirmación de más de un autor. + +{% note %} + +**Nota**: {% data reusables.desktop.tags-push-with-commits %} Para obtener más información, consulta la sección "[Administrar las etiquetas](/desktop/contributing-to-projects/managing-tags)". + +{% endnote %} + +{% data reusables.desktop.commit-message %} + ![Campo para mensaje de confirmación](/assets/images/help/desktop/commit-message.png) +2. De manera opcional, para atribuir una confirmación a otro autor, haz clic en el icono de coautores y escribe el nombre de usuario que deseas incluir. ![Agregar un coautor al mensaje de confirmación](/assets/images/help/desktop/add-co-author-commit.png) +{% data reusables.desktop.commit-button %} + ![Botón Commit (Confirmar)](/assets/images/help/desktop/commit-button.png) +4. Si la rama a la que intentas comprometerte está protegida, Desktop te avisará. + - Para mover tus cambios, haz clic en **switch btanches (cambiar ramas)**. + - Para confirmar tus cambios en la rama protegida, haz clic en **Commit to _BRANCH_****(Enviar a _RAMA)_**. + + Para más información sobre ramas protegidas, ve "[Acerca de ramas protegidas](/github/administering-a-repository/about-protected-branches)". ![Advertencia de rama protegida](/assets/images/help/desktop/protected-branch-warning.png) +{% data reusables.desktop.push-origin %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md new file mode 100644 index 0000000000000..aa5e79ff74827 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md @@ -0,0 +1,77 @@ +--- +title: Crear un nuevo informe de problemas o solicitud de extracción +intro: Puedes crear una propuesta o solicitud de extracción para proponer y colaborar en los cambios en un repositorio. +permissions: 'Cualquiera puede crear un informe de problemas en un repositorio público que los haya habilitado. Todo usuario que tenga permisos de lectura para un repositorio puede crear una solicitud de extracción, pero tú debes tener permisos de escritura para poder crear una rama.' +redirect_from: + - /desktop/contributing-to-projects/creating-an-issue-or-pull-request + - /desktop/contributing-to-projects/creating-a-pull-request +versions: + free-pro-team: '*' +--- + +### Acerca de los informes de problemas y solicitudes de extracción + +Puedes utilizar los informes de problemas para rastrear ideas, errores, tareas, y otros tipos de información que sean importantes para tu proyecto. Puedes crear un informe de problemas en el repositorio de tu proyecto con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de los informes de problemas, consulta la sección "[Acerca de los informes de problemas](/github/managing-your-work-on-github/about-issues)". + +Después de que crees una rama y hagas cambios a los archivos en un proyecto, puedes crear una solicitud de extracción. Con una solicitud de extracción, puedes proponer, debatir e iterar entre los cambios antes de fusionarlos en el proyecto. Puedes crear una solicitud de extracción en el repositorio de tu proyecto con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de las solicitudes de extracción, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". + +### Prerrequisitos + +Amtes de crear una solicitud de extracción, necesitarás subir los cambios a una rama en {% data variables.product.prodname_dotcom %}. +- Guardar y confirmar cualquier cambio en tu rama local. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)". +- Cambiar tus confirmaciones locales en el repositorio remoto. Para obtener más información, consulta la sección"[Subir cambios a GitHub](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)". +- Publicar tu rama actual en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)". + +### Crear una propuesta + +{% mac %} + +1. En la barra de menú, utiliza el menú desplegable de **Repositorio** y luego da clic en **Crear informe de problemas en {% data variables.product.prodname_dotcom %}**. ![Valor del repositorio en el menú de la rama](/assets/images/help/desktop/create-issue-mac.png) +2. En {% data variables.product.prodname_dotcom %}, da clic en **Empezar** para abrir una plantilla de informe de problemas o da clic en **Abrir un informe de problemas en blanco**. ![Opciones para crear nuevo informe de problemas](/assets/images/help/desktop/create-new-issue.png) + +{% endmac %} + +{% windows %} + +1. En la barra de menú, utiliza el menú desplegable de **Repositorio** y luego da clic en **Crear usuario en {% data variables.product.prodname_dotcom %}**. ![El valor del repositorio en el menú de la rama](/assets/images/help/desktop/create-issue-windows.png) +2. En {% data variables.product.prodname_dotcom %}, da clic en **Empezar** para abrir una plantilla de informe de problemas o da clic en **Abrir un informe de problemas en blanco**. ![Opciones para crear nuevo informe de problemas](/assets/images/help/desktop/create-new-issue.png) + +{% endwindows %} + +{% note %} + +**Nota**: Si no están habilitadas las plantillas de informe de problemas en tu repositorio actual, {% data variables.product.prodname_desktop %}te direccionará a un informe de problemas en blanco en {% data variables.product.prodname_dotcom %}. + +{% endnote %} + +### Crear una solicitud de extracción + +{% mac %} + +1. Cambia a la rama para la cual quieras crear una solicitud de extracción. Para obtener más información, consulta la sección "[Cambiar entre ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)". +2. Haz clic en **Create Pull Request** (Crear solicitud de extracción). {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado para llevarte a {% data variables.product.prodname_dotcom %}. ![El botón de crear solicitud de extracción](/assets/images/help/desktop/mac-create-pull-request.png) +4. Activado +{% data variables.product.prodname_dotcom %}, confirma que la rama en el menú desplegable de **base:** es aquella en donde quieres fusionar tus cambios. Confirma que la rama en el menú desplegable de **comparar:** es la rama de tema en donde realizaste tus cambios. + ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/desktop/mac-create-pull-request.png) +{% data reusables.repositories.pr-title-description %} +{% data reusables.repositories.create-pull-request %} + +{% endmac %} + +{% windows %} + +1. Cambia a la rama para la cual quieras crear una solicitud de extracción. Para obtener más información, consulta la sección "[Cambiar entre ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)". +2. Haz clic en **Create Pull Request** (Crear solicitud de extracción). {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado para llevarte a {% data variables.product.prodname_dotcom %}. ![El botón de crear solicitud de extracción](/assets/images/help/desktop/windows-create-pull-request.png) +3. Activado +{% data variables.product.prodname_dotcom %}, confirma que la rama en el menú desplegable de **base:** es aquella en donde quieres fusionar tus cambios. Confirma que la rama en el menú desplegable de **comparar:** es la rama de tema en donde realizaste tus cambios. + ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/desktop/base-and-compare-branches.png) +{% data reusables.repositories.pr-title-description %} +{% data reusables.repositories.create-pull-request %} + +{% endwindows %} + +### Further reading +- "[Informe de problemas](/github/getting-started-with-github/github-glossary#issue)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Solicitud de extracción](/github/getting-started-with-github/github-glossary#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Rama base](/github/getting-started-with-github/github-glossary#base-branch)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Rama de tema](/github/getting-started-with-github/github-glossary#topic-branch)" en el glosario de {% data variables.product.prodname_dotcom %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/index.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/index.md new file mode 100644 index 0000000000000..b6133eebb09bd --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/index.md @@ -0,0 +1,31 @@ +--- +title: Contribuir y colaborar utilizando GitHub Desktop +shortTitle: Contribuir y colaborar +intro: 'Usa GitHub Desktop para administrar tus proyectos, crear confirmaciones significativas y realizar un seguimiento del historial del proyecto en una app en lugar de en la línea de comando.' +redirect_from: + - /desktop/contributing-to-projects +versions: + free-pro-team: '*' +--- + + +### Índice + +{% topic_link_in_list /adding-and-cloning-repositories %} + {% link_in_list /adding-a-repository-from-your-local-computer-to-github-desktop %} + {% link_in_list /adding-an-existing-project-to-github-using-github-desktop %} + {% link_in_list /cloning-and-forking-repositories-from-github-desktop %} + {% link_in_list /cloning-a-repository-from-github-to-github-desktop %} +{% topic_link_in_list /making-changes-in-a-branch %} + {% link_in_list /managing-branches %} + {% link_in_list /committing-and-reviewing-changes-to-your-project %} + {% link_in_list /pushing-changes-to-github %} + {% link_in_list /reverting-a-commit %} + {% link_in_list /managing-tags %} + {% link_in_list /viewing-the-branch-history %} +{% topic_link_in_list /working-with-your-remote-repository-on-github-or-github-enterprise %} + {% link_in_list /creating-an-issue-or-pull-request %} + {% link_in_list /viewing-a-pull-request-in-github-desktop %} + {% link_in_list /changing-a-remotes-url-from-github-desktop %} +{% topic_link_in_list /keeping-your-local-repository-in-sync-with-github %} + {% link_in_list /syncing-your-branch %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md new file mode 100644 index 0000000000000..1430d50319828 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md @@ -0,0 +1,8 @@ +--- +title: Mantener tu repositorio local sincronizado con GitHub +intro: 'Puedes mantener tu repositorio local sincronizado con tu repositorio remoto mientras actualizas cualquiera de estos. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md new file mode 100644 index 0000000000000..abce8123be537 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md @@ -0,0 +1,10 @@ +--- +title: Realizar cambios en una rama +intro: 'Usa tu editor de texto favorito, como [Atom](https://atom.io/), para realizar cambios en el proyecto y, a continuación, utiliza {% data variables.product.prodname_desktop %} para visualizar confirmaciones útiles.' +mapTopic: verdadero +redirect_from: + - /desktop/contributing-to-projects/making-changes-in-a-branch +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md new file mode 100644 index 0000000000000..8a048e8f98312 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md @@ -0,0 +1,118 @@ +--- +title: Administrar ramas +intro: Puedes crear una rama nueva desde la rama predeterminada de un repositorio para que puedas experimentar con los cambios de forma segura. +redirect_from: + - /desktop/contributing-to-projects/creating-a-branch-for-your-work + - /desktop/contributing-to-projects/switching-between-branches + - /desktop/contributing-to-projects/managing-branches +versions: + free-pro-team: '*' +--- + +### Acerca de administrar ramas +Puedes utilizar las ramas para experimentar de forma segura con los cambios de tu proyecto. Las ramas aislan tu trabajo de desarrollo de otras ramas en el repositorio. Por ejemplo, puedes utilizar una rama para desarrollar una nueva característica o para corregir un error. + +Siempre puedes crear una rama a partir de otra rama existente. Habitualmente, puedes crear una rama desde la rama predeterminada de tu repositorio. Podrás entonces trabajar en esta rama nueva aislado de los cambios que otras personas hacen al repositorio. + +Una vez que estás satisfecho con to trabajo puedes crear una solicitud de extracción para fusionar tus cambios en la rama actual en alguna otra rama. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" y "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". + +Siempre podrás crear una rama en {% data variables.product.prodname_desktop %} si tienes acceso de lectura en un repositorio, pero solo podrás cargar la rama a {% data variables.product.prodname_dotcom %} si tienes acceso de escritura en el repositorio en cuestión. + +{% data reusables.desktop.protected-branches %} + +### Cómo crear una rama + +{% tip %} + +**Tip:** La primera rama nueva que creas se basará en la rama predeterminada. Si tienes más de una rama, puedes elegir basar la nueva rama en aquella que has revisado actualmente o en la rama predeterminada. + +{% endtip %} + +{% mac %} + +{% data reusables.desktop.click-base-branch-in-drop-down %} + ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) +{% data reusables.desktop.create-new-branch %} + ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-mac.png) +{% data reusables.desktop.name-branch %} + ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-mac.png) +{% data reusables.desktop.select-base-branch %} + ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-mac.png) +{% data reusables.desktop.confirm-new-branch-button %} + ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-mac.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.click-base-branch-in-drop-down %} + ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down-win.png) +{% data reusables.desktop.create-new-branch %} + ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-win.png) +{% data reusables.desktop.name-branch %} + ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-win.png) +{% data reusables.desktop.select-base-branch %} + ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-win.png) +{% data reusables.desktop.confirm-new-branch-button %} + ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-win.png) + +{% endwindows %} + +### Publicar una rama + +Si creas una rama en {% data variables.product.product_name %}, necesitarás publicarla para que se muestre disponible para colaboración en {% data variables.product.prodname_dotcom %}. + +1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego en la rama que quieres publicar. ![Menú desplegable para seleccionar qué rama publicar](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) +2. Da clic en **Publicar rama**. ![El botón de publicar rama](/assets/images/help/desktop/publish-branch-button.png) + +### Alternar entre ramas +Puedes ver y realizar confirmaciones en cualquiera de las ramas de tu repositorio. Si tienes cambios guardados, no confirmados, deberás decidir qué hacer con tus cambios antes de alternar las ramas. Puedes confirmar tus cambios en la rama actual, acumula tus cambios en la rama actual, o lleva los cambios a tu nueva rama. Si quieres confirmar tus cambios en la rama actual, sigue los pasos en [Confirmar y revisar cambios en tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project) antes de alternar entre ramas. + +{% tip %} + +**Consejo**: Puedes configurar un comportamiento predeterminado para alternar entre ramas en la configuración **Avanzada**. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". + +{% endtip %} + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.switching-between-branches %} + ![Lista de ramas en el repositorio](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) +3. Si tienes cambios guardados, sin confirmar, elige **Leave my changes** (Dejar mis cambios) o **Bring my changes** (Traer mis cambios) y luego haz clic en **Switch Branch** (Cambiar rama). ![Alternar ramas con opciones de cambios](/assets/images/help/desktop/stash-changes-options.png) + +### Recuperar cambios acumulados +Para acceder a los cambios que has acumulado en otra rama, vuelve a cambiar a la rama en la que acumulaste los cambios. + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.switching-between-branches %} + ![Lista de ramas en el repositorio](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) +3. En la barra lateral a la izquierda, haz clic en **Stashed Changes** (Cambios acumulados). ![Opción de cambios acumulados](/assets/images/help/desktop/stashed-changes.png) +4. Para eliminar tus cambios acumulados, haz clic en **Discard **, o bien, para usar tus cambios acumulados, haz clic en **Restore**. ![Descartar o restaurar cambios acumulados](/assets/images/help/desktop/discard-restore-stash-buttons.png) + +### Cómo eliminar una rama + +No puedes borrar una rama que esté actualmente asociada con una solicitud de extracción abierta. No puedes revertir el haber borrado una rama. + +{% mac %} + +{% data reusables.desktop.select-branch-to-delete %} + ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-to-delete.png) +{% data reusables.desktop.delete-branch-mac %} + ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-mac.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.select-branch-to-delete %} + ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-to-delete.png) +{% data reusables.desktop.delete-branch-win %} + ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-win.png) + +{% endwindows %} + +### Further reading + +- [Clonar un repositorio de {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop) +- "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} +- "[Acerca de las ramas](/articles/about-branches)" +- "[Ramas en resumen](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" en la documentación de Git diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md new file mode 100644 index 0000000000000..a9b79d1937934 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -0,0 +1,35 @@ +--- +title: Administrar etiquetas +intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para crear, cargar y visualizar etiquetas.' +redirect_from: + - /desktop/contributing-to-projects/managing-tags +versions: + free-pro-team: '*' +--- + +### Acerca de las etiquetas en {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} te permite crear etiquetas anotadas. Puedes utilizar una etiqueta para marcar un punto individual en el historial de tu repositorio, incluyendo un número de versión para un lanzamiento. Para obtener más información acerca de las etiquetas de lanzamiento, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)". + +{% data reusables.desktop.tags-push-with-commits %} + +### Crear una etiqueta + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.create-tag %} +{% data reusables.desktop.name-tag %} +{% data reusables.desktop.confirm-tag %} + +### Visualizar etiquetas + +{% data reusables.desktop.history-tab %} +2. Da clic en la confirmación. + {% note %} + + **Nota**: {% data variables.product.prodname_desktop %} muestra una flecha {% octicon "arrow-up" aria-label="The up arrow icon" %} si la etiqueta no se ha subido al repositorio remoto. + + {% endnote %} + + ![Visualizar una etiqueta en el historial](/assets/images/help/desktop/viewing-tags-in-history.png) + +3. Todas las etiquetas asociadas con la confirmación se pueden ver en los metadatos de dicha confirmación. ![Visualizar una etiqueta en la confirmación](/assets/images/help/desktop/viewing-tags-in-commit.png) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md new file mode 100644 index 0000000000000..3923e4c7399c3 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md @@ -0,0 +1,39 @@ +--- +title: Cargar cambios en GitHub +shortTitle: Cargar cambios +intro: 'De manera que confirmes cambios localmente en tu proyecto, puedes cargarlos a {% data variables.product.prodname_dotcom %} para que otros puedan acceder a ellos desde el repositorio remoto.' +permissions: Las personas con permisos de escritura pueden cargar cambios a un repositorio. +redirect_from: + - /desktop/contributing-to-projects/pushing-changes-to-github +versions: + free-pro-team: '*' +--- + +### Acerca de cargar cambios a {% data variables.product.prodname_dotcom %} + +Cuando cargas cambios, envías los cambios confirmados en tu repositorio local al repositorio remoto en {% data variables.product.prodname_dotcom %}. Si cambias tu proyecto localmente y quieres que otros tengan acceso a los cambios, deberás cargar los cambios a {% data variables.product.prodname_dotcom %}. + +Antes de cargar los cambios, debes actualizar tu rama local para que incluya cualquier confirmación que se haya agregado al repositorio remoto. Si alguien hizo confirmaciones en la rama remota, las cuales no están en tu rama local, {% data variables.product.prodname_desktop %} te solicitará conseguir las confirmaciones nuevas antes de cargar tus cambios para evitar conflictos de fusión. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-to-projects/syncing-your-branch)". + +{% data reusables.desktop.protected-branches %} + +### Cargar cambios a {% data variables.product.prodname_dotcom %} + +{% note %} + +**Nota:** {% data variables.product.prodname_desktop %} rechazará una carga si excede ciertos límites. + +- Una subida contiene un archivo grande de más de {% data variables.large_files.max_github_size %}. +- Una subida es de más de {% data variables.large_files.max_file_size %} en total. + +Si configuras a {% data variables.large_files.product_name_long %} para rastrear tus archivos grandes, puedes subir aquellos que normalmente se rechazarían. Para obtener más información, consulta la sección "[Acerca de {% data variables.large_files.product_name_long %} y {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)". + +{% endnote %} + +{% data reusables.desktop.push-origin %} +2. Si {% data variables.product.prodname_desktop %} te pide traer las confirmaciones nuevas de la rama remota, da clic en **Recuperar**. ![El botón de recuperar](/assets/images/help/desktop/fetch-newer-commits.png) +3. Opcionalmente, da clic en **Crear Solicitud de Extracción** para abrir una solicitud de extracción y colaborar en tus cambios. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" ![El botón de crear solicitud de extracción](/assets/images/help/desktop/create-pull-request.png) + +### Further reading +- "[Cargar](/github/getting-started-with-github/github-glossary/#push)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Confirmar y revisar los cambios hechos a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)" diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/reverting-a-commit.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/reverting-a-commit.md new file mode 100644 index 0000000000000..85cd6df3e3daf --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/reverting-a-commit.md @@ -0,0 +1,32 @@ +--- +title: Revertir una confirmación +intro: Puedes revertir una confirmación específica para eliminar los cambios de tu rama. +redirect_from: + - /desktop/contributing-to-projects/reverting-a-commit +versions: + free-pro-team: '*' +--- + +Cuando reviertes la confirmación anterior, la reversión también es una confirmación. La confirmación original también permanece en el historial del repositorio. + +{% tip %} + +**Sugerencia:** Cuando reviertes múltiples confirmaciones, es mejor revertirlas desde la más nueva hasta la más antigua. Si reviertes confirmaciones en un orden diferente, es posible que se produzcan conflictos de fusión. + +{% endtip %} + +{% mac %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.revert-commit %} + ![La opción Revert (Revertir) sobre la vista diferente](/assets/images/help/desktop/commit-revert-mac.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.revert-commit %} + ![La opción Revert (Revertir) sobre la vista diferente](/assets/images/help/desktop/commit-revert-win.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch.md new file mode 100644 index 0000000000000..72dcf7cf9a24a --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch.md @@ -0,0 +1,94 @@ +--- +title: Sincronizar tu rama +intro: 'Conforme se suban las confirmaciones a tu proyecto en {% data variables.product.prodname_dotcom %}, podrás mantener una copia local de éste en sincornización si lo extraes del repositorio remoto.' +redirect_from: + - /desktop/contributing-to-projects/syncing-your-branch +versions: + free-pro-team: '*' +--- + +### Acerca de la sincronización de ramas + +Puedes sincronizar tu rama local con el repositorio remoto si extraes cualquier confirmación que se haya agregado a la rama en {% data variables.product.product_name %} desde la última vez que lo sincronizaste. Si realizas confirmaciones desde otro dispositivo o si muchas personas colaboran con el proyecto, necesitarás sincronizar tu rama local para mantenerla actualizada. + +Cuando extraes información a tu rama local, únicamente estás actualizando la copia local del repositorio. Para actualziar tu rama en {% data variables.product.prodname_dotcom %}, deberás subir tus cambios. Para obtener más información, consulta la sección "[Subir los cambios a {% data variables.product.prodname_dotcom %}](/desktop/contributing-to-projects/pushing-changes-to-github)". + +Para agregar cambios de una rama en otra, puedes fusionar estas ramas. Para aplicar los cambios a tu rama desde otra rama en el mismo repositorio, puedes fusionar esta otra rama con la tuya en {% data variables.product.prodname_desktop %}. Para solicitar que se fusionen los cambios de tu rama en otra rama que se encuentre en el mismo repositorio o en otro repositorio dentro de la red, puedes crear una solicitud de extracción en {% data variables.product.prodname_desktop %}. Para obtener más información, consulta las secciones "[Fusionar otra rama en tu rama de proyecto](#merging-another-branch-into-your-project-branch)" y " +Acerca de las solicitudes de extracción".

    + +Algunos flujos de trabajo requieren o se benefician con el rebase en vez de con la fusión. Al rebasar podemos reordenar, editar o combinar confirmaciones. Para obtener más información, consulta las secciones "[Acerca del rebase de Git](/articles/about-git-rebase)" y "[rebasar tu rama de proyecto en otra rama](#rebasing-your-project-branch-onto-another-branch)". + + + +### Extraer tu rama local de la rama remota + +1. En {% data variables.product.prodname_desktop %}, utiliza el menú desplegable de {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y selecciona la rama local que quieres actualizar. +2. Para verificar las confirmaciones en la rama remota, da clic en **Obtener origen** ![El botón Fetch origin (Buscar origen)](/assets/images/help/desktop/fetch-button.png) + +3. Para extraer cualquier confirmación de la rama remota, da clic en **Extraer origen** o en **Extraer origen con rebase**. ![El botón Pull origin (Extraer origen)](/assets/images/help/desktop/pull-button.png) + + {% data reusables.desktop.resolve-merge-conflicts %} + + + +### Fusionar otra rama en tu rama de proyecto + +{% data reusables.desktop.current-branch-menu %} + + + +{% data reusables.desktop.choose-a-branch-to-merge %} + + + +{% data reusables.desktop.confirm-merging-branch %} + +{% note %} + +**Nota:** Si hay conflictos de fusión, {% data variables.product.prodname_desktop %} te advertiremos sobre **Merge BRANCH (Fusionar RAMA) en el botón BRANCH** (RAMA). No podrás fusionar las ramas hasta que hayas resuelto todos los conflictos. + +{% endnote %} + +![El botón Merge (Fusionar)](/assets/images/help/desktop/merge-branch-button.png) + +{% data reusables.desktop.push-origin %} + + + +### Rebasar tu rama de proyecto en otra rama + +{% mac %} + +1. En la barra de menú, utiliza el menú desplegable de **Rama** y da clic en **Rebasar la rama actual**. ![Rebase Current Branch (Rebasar rama actual) en el desplegable de rama](/assets/images/help/desktop/mac-rebase-current-branch.png) + +2. Haz clic en la rama que deseas rebasar en la rama actual, luego haz clic en **Start rebase**. ![Botón Start rebase (Iniciar rebase)](/assets/images/help/desktop/start-rebase-button.png) + +3. Si estás seguro de que deseas rebasar, haz clic en **Begin rebase** (Comenzar rebase). ![Botón Begin rebase (Comenzar rebase)](/assets/images/help/desktop/begin-rebase-button.png) + + {% data reusables.desktop.resolve-merge-conflicts %} + +4. Para subir tus cambios locales, da clic en **Subir el origen forzadamente**. ![Origen de empuje forzado](/assets/images/help/desktop/force-push-origin.png) + +{% endmac %} + +{% windows %} + +1. Usa el desplegable ** Branch** y haz clic en **Rebase Current Branch**. ![Rebase Current Branch (Rebasar rama actual) en el desplegable de rama](/assets/images/help/desktop/windows-rebase-current-branch.png) + +2. Haz clic en la rama que deseas rebasar en la rama actual, luego haz clic en **Start rebase**. ![Botón Start rebase (Iniciar rebase)](/assets/images/help/desktop/start-rebase-button.png) + +3. Si estás seguro de que deseas rebasar, haz clic en **Begin rebase** (Comenzar rebase). ![Botón Begin rebase (Comenzar rebase)](/assets/images/help/desktop/begin-rebase-button.png) + + {% data reusables.desktop.resolve-merge-conflicts %} + +4. Para extraer tus cambios locales, haz clic en **Force push origin** (Origen de empuje forzado). ![Origen de empuje forzado](/assets/images/help/desktop/force-push-origin.png) + +{% endwindows %} + + + +### Leer más + +- "[Extraer](/github/getting-started-with-github/github-glossary#pull)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Fusionar](/github/getting-started-with-github/github-glossary#merge)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Rebasar](/github/getting-started-with-github/github-glossary#rebase)" en el glosario de {% data variables.product.prodname_dotcom %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop.md new file mode 100644 index 0000000000000..b96cf4d5792df --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop.md @@ -0,0 +1,28 @@ +--- +title: Visualizar una solicitud de extracción en GitHub Desktop +shortTitle: Visualizar una solicitud de extracción +intro: 'Puedes ver los cambios propuestos en las solicitudes de extracción abiertas en {% data variables.product.prodname_desktop %}.' +redirect_from: + - /desktop/contributing-to-projects/accessing-a-pull-request-locally + - /desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally +versions: + free-pro-team: '*' +--- + +### Acerca de las solicitudes de extracción en {% data variables.product.prodname_desktop %} +Puedes ver las solicitudes de extracción que tú o tus colaboradores hayan propuesto en {% data variables.product.prodname_desktop %}. Las solicitude de extracción te permiten proponer cambios a los proyectos, proporcionar retroalimentación y revisiones, y fusionar cambios en los proyectos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." + +Cuando visualizas una solicitud de extracción en {% data variables.product.prodname_desktop %}, puedes ver un historial de confirmaciones que han hecho los colaboradores. También puedes ver qué archivos modificaron, agregaron o borraron estas confirmaciones. Desde {% data variables.product.prodname_desktop %}, puedes abrir los repositorios en tu editor de texto preferido para ver cualquier cambio o para hacer cambios adicionales. Después de recibir los cambios en una solicitud de extracción, puedes dar retroalimentación en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)". + +### Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %} +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![Pestaña Pull Requests en el menú desplegable de la rama actual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![Lista de las solicitudes de extracción abiertas en el repositorio](/assets/images/help/desktop/click-pull-request.png) +4. Opcionalmente, para actualizar la lista de solicitudes de extracción, haz clic en {% octicon "sync" aria-label="The sync icon" %}. ![Botón Sync (Sincronizar) para actualizar](/assets/images/help/desktop/pull-request-list-sync.png) + +### Abrir una solicitud de extracción en {% data variables.product.prodname_desktop %} desde {% data variables.product.prodname_dotcom %} +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, da clic en la solicitud de extracción que te gustaría abrir en {% data variables.product.prodname_desktop %}. +3. A la derecha del título de la solicitud de extracción, da clic en el menú desplegable de **Abrir con** y después da clic en el botón de **Abrir en Desktop**. ![El botón de Abrir en Desktop](/assets/images/help/desktop/open-pr-in-desktop-button.png) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md new file mode 100644 index 0000000000000..706ce8c4bd70f --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md @@ -0,0 +1,23 @@ +--- +title: Visualizar el historial de ramas +intro: 'Puedes ver los detalles de cualquier confirmación en {% data variables.product.prodname_desktop %}, incluyendo una diferencia de los cambios introducidos por la confirmación.' +redirect_from: + - /desktop/contributing-to-projects/viewing-the-branch-history +versions: + free-pro-team: '*' +--- + +Cada confirmación muestra: + + - El mensaje de confirmación + - La hora en que se creó la confirmación + - El nombre de usuario y la foto de perfil (si está disponible) de la persona que confirma el cambio + - El hash SHA-1 de la confirmación (el ID exclusivo) + +{% data reusables.desktop.history-tab %} +2. En la pestaña **History** (Historial), haz clic en la confirmación que deseas revisar. ![Una confirmación en la pestaña History (Historial)](/assets/images/help/desktop/branch-history-commit.png) +3. Si existen múltiples archivos en la confirmación, haz clic en un archivo individual para ver los cambios que se realizan a ese archivo en esa confirmación. ![Un archivo en la confirmación](/assets/images/help/desktop/branch-history-file.png) + +### Further reading + +- [Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md new file mode 100644 index 0000000000000..068be04af04d7 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md @@ -0,0 +1,10 @@ +--- +title: Trabajar con tu repositorio remoto en GitHub o GitHub Enterprise +intro: 'A medida que realizas cambios a tu proyecto localmente, puedes mantenerlos actualizados con tu repositorio remoto. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' +mapTopic: verdadero +redirect_from: + - /desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/index.md b/translations/es-ES/content/desktop/index.md new file mode 100644 index 0000000000000..55705b95719ae --- /dev/null +++ b/translations/es-ES/content/desktop/index.md @@ -0,0 +1,11 @@ +--- +title: Documentación del Escritorio de GitHub +shortTitle: GitHub Desktop +intro: Guías paso a paso para configurar y usar GitHub Desktop a fin de administrar tu trabajo de proyecto. +versions: + free-pro-team: '*' +--- + +{% link_with_intro /installing-and-configuring-github-desktop %} + +{% link_with_intro /contributing-and-collaborating-using-github-desktop %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md new file mode 100644 index 0000000000000..db2f0ede51f95 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md @@ -0,0 +1,17 @@ +--- +title: Acerca de las conexiones a GitHub +intro: '{% data variables.product.prodname_desktop %} utiliza HTTPS para intercambiar datos de forma segura con {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /desktop/getting-started-with-github-desktop/about-connections-to-github +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_desktop %} se conecta a {% data variables.product.prodname_dotcom %} cuando extraes, subes, clonas y bifurcas repositorios remotos. Para conectarse a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_desktop %}, debes autenticar tu cuenta. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." + +Después de que te autentiques en {% data variables.product.prodname_dotcom %}, puedes conectarte a los repositorios remotos con {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} guarda tus credenciales en caché (nombre de usuario y contraseña o token de acceso personal) y las utiliza para autenticarse en cada conexión hacia el destino remoto. + +{% data variables.product.prodname_desktop %} se conecta con {% data variables.product.prodname_dotcom %} utilizando HTTPS. Si utilizas {% data variables.product.prodname_desktop %} para acceder a los repositorios que se clonaron utilizando SSH, podrías encontrar errores. Para conectarte a un repositorio que se clonó utilizando SSH, cambia las URL del destino remoto. Para obtener más información, consulta "[Changing a remote's URL](/github/using-git/changing-a-remotes-url) (Cambiar la URL de un remoto). + +### Further reading +- "[Clonar y bifurcar repositorios desde GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md new file mode 100644 index 0000000000000..69ca9f3449edc --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md @@ -0,0 +1,19 @@ +--- +title: Acerca de GitHub Desktop y del Almacenamiento de Archivos Grandes de Git +shortTitle: Acerca de Git LFS +intro: '{% data variables.product.prodname_desktop %} incluye a {% data variables.large_files.product_name_long %} para administrar los archivos grandes.' +redirect_from: + - /desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop +versions: + free-pro-team: '*' +--- + +Cuando instalas {% data variables.product.prodname_desktop %}, también se instala {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). {% data variables.large_files.product_name_short %} te permite subir archivos a {% data variables.product.prodname_dotcom %} que excedan el límite normal de {% data variables.large_files.max_github_size %}. Para obtener más información acerca de las {% data variables.large_files.product_name_short %}, consulta la sección "[Acerca del {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage)". + +Para utilizar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}, debes configurar a {% data variables.large_files.product_name_short %} utilizando la línea de comandos. Para obtener más información, consulta la sección "[Configurar las {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". + +Después de que configuras a {% data variables.large_files.product_name_short %} para rastrear los archivos en un repositorio, puedes acceder sin problema y administrar archivos grandes con {% data variables.product.prodname_desktop %} como lo harías con cualquier otro archivo en el repositorio. + +### Further reading +- "[Trabajar con archivos grandes](/github/managing-large-files/working-with-large-files)" +- "[Control de versiones de archivos grandes](/github/managing-large-files/versioning-large-files)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md new file mode 100644 index 0000000000000..378c40d2ab0b7 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md @@ -0,0 +1,186 @@ +--- +title: Autenticar a GitHub +shortTitle: Autenticación +intro: 'Puedes acceder de forma segura a los recursos de tu cuenta en {% data variables.product.prodname_desktop %} si te autenticas con {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser + - /desktop/getting-started-with-github-desktop/authenticating-to-github +versions: + free-pro-team: '*' +--- + +### Acerca de la autenticación + +Para mantener la seguridad de tu cuenta, debes autenticarte antes de que puedas utilizar {% data variables.product.prodname_desktop %} para acceder a los recursos en {% data variables.product.prodname_dotcom %}. + +Antes de realizar la autenticación, {% data reusables.desktop.get-an-account %} + +{% mac %} + +### Autenticar una cuenta en {% data variables.product.prodname_dotcom %} + +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +3. A la derecha de "{% data variables.product.prodname_dotcom_the_website %}", da clic en **Iniciar sesión**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-github.png) +4. En el recuadro de "Iniciar sesión", da clic en **Iniciar sesión utilizando tu buscador**. {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado. ![Inicio de sesión mediante el enlace de su navegador](/assets/images/help/desktop/mac-sign-in-browser.png) + + {% data reusables.user_settings.password-authentication-deprecation-desktop %} + +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. Después de que {% data variables.product.prodname_dotcom %} autentique tu cuenta, sigue las indicaciones para regresar a {% data variables.product.prodname_desktop %}. + +### Autenticar una cuenta en {% data variables.product.prodname_enterprise %} + +{% data reusables.user_settings.password-authentication-deprecation-desktop %} + +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. Para agregar una +cuenta de {% data variables.product.prodname_enterprise %}, teclea tus credenciales debajo de "Enterprise server address", y luego da clic en **Continuar**. + ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) +{% data reusables.desktop.retrieve-2fa %} + +{% endmac %} + +{% windows %} + +### Autenticar una cuenta en {% data variables.product.prodname_dotcom %} + +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +3. A la derecha de "GitHub.com", da clic en **Iniciar sesión**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-github.png) +4. En el panel de inicio de sesión, haz clic en **Sign in using your browser** (Iniciar sesión usando el navegador). ![Inicio de sesión mediante el enlace de su navegador](/assets/images/help/desktop/windows-sign-in-browser.png) + + {% data reusables.user_settings.password-authentication-deprecation-desktop %} + +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. Después de que {% data variables.product.prodname_dotcom %} autentique tu cuenta, sigue las indicaciones para regresar a {% data variables.product.prodname_desktop %}. + +### Autenticar una cuenta en {% data variables.product.prodname_enterprise %} + + +{% data reusables.user_settings.password-authentication-deprecation-desktop %} + +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. Para agregar una +cuenta de {% data variables.product.prodname_enterprise %}, teclea tus credenciales debajo de "Enterprise server address", y luego da clic en **Continuar**. + ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) +{% data reusables.desktop.retrieve-2fa %} + +{% endwindows %} + +### Solucionar problemas de autenticación + +Si {% data variables.product.prodname_desktop %} encuentra un error de autenticación, puedes utilizar los mensajes de error para solucionar los problemas. + +Si te encuentras con un error de autenticación, primero intenta salir y entrar nuevamente a tu cuenta en {% data variables.product.prodname_desktop %}. + +En el caso de algunos errores, {% data variables.product.prodname_desktop %} te solicitará que indiques el mensaje de error. Si no se te solicita esto, o si quieres encontrar información adicional sobre cualquier error, consulta los archivos de bitácora de {% data variables.product.prodname_desktop %} siguiendo estos pasos. + +{% mac %} + +1. Utiliza el menú desplegable de **Ayuda** y da clic en **Mostrar bitácoras en el buscador**. ![El botón de Mostrar Bitácoras en el Buscador](/assets/images/help/desktop/mac-show-logs.png) +2. Selecciona el archivo de bitácora desde la fecha en donde encontraste el error de autenticación. + +{% endmac %} + +{% windows %} + +1. Utiliza el menú desplegable de **Ayuda** y da clic en **Mostrar las bitácoras en el explorador**. ![El botón de Mostrar Bitácoras en el Buscador](/assets/images/help/desktop/windows-show-logs.png) +2. Selecciona el archivo de bitácora desde la fecha en donde encontraste el error de autenticación. + +{% endwindows %} + +Revisa la información de solución de problemas que se muestra a continuación dependiendo del error con el que te hayas encontrado. + +#### Credenciales incorrectas + +```shell +Error: Bad credentials +``` + +Este error significa que hay un problema con las credenciales almacenadas de tu cuenta. + +Para solucionar este problema, sal de tu cuenta en {% data variables.product.prodname_desktop %} y vuelve a firmarte. + +#### Token vacío + +```shell +info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - (empty token) +``` + +Este error significa que {% data variables.product.prodname_desktop %} no puede encontrar el token de acceso que creó en la cadena de llaves del sistema. + +Para solucionar este problema, sal de tu cuenta en {% data variables.product.prodname_desktop %} y vuelve a firmarte. + +#### No se encuentra el repositorio + +```shell +fatal: repository 'https://github.com//.git' not found + +(The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.) +``` + +Este error significa que no tienes permiso para acceder al repositorio que estás intentando clonar. + +Para solucionar los problemas, contacta a la persona que administre los permisos en tu organización. + +#### No se pudo leer del repositorio remoto + +```shell +git@github.com: Permission denied (publickey). +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights and the repository exists. +``` + +Este error significa que no tienes una llave SSH válida configurada. + +Para solucionarlo, consulta la sección "[Generar una llave SSH nueva y agregarla al agente de SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + +#### No se pudo clonar + +```shell +fatal: clone of 'git@github.com:/' into submodule path '' failed +Failed to clone 'src/github.com//'. Retry scheduled +Cloning into ''... +git@github.com: Permission denied (publickey). +fatal: Could not read from remote repository. +Please make sure you have the correct access rights +and the repository exists. +``` + +Este error significa ya sea que el repositorio que intentas clonar tiene submódulos a los cuales no tienes acceso o que no tienes una llave SSH válida configurada. + +Si no tienes acceso a los submódulos, soluciona este problema contactando a la persona que administre los permisos para este repositorio. + +Si no tienes una llave SSH válida configurada, consulta la sección "[Generar una llave SSH nueva y agregarla al agente de SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + +{% windows %} + +#### No se pudo leer la respuesta de AskPass + +```shell +error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh' +fatal: could not read Username for 'https://github.com': terminal prompts disabled +``` + +Este error se puede presentar a causa de varios eventos. + +Si se modifican las entradas del registro de `Command Processor`, {% data variables.product.prodname_desktop %} responderá con un error de `Authentication failed`. Para verificar si estas entradas de registro se modifcaron, sigue estos pasos. + +1. Abre el editor de registro (`regedit.exe`) y navega hasta las siguientes ubicaciones. `` HKEY_CURRENT_USER\Software\Microsoft\Command Processor\` ``HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\` +2. Revisa para ver si hay un valor de `Autorun` en cualquiera de las ubicaciones. +3. Si hay un valor de `Autorun`, bórralo. + +Si tu nombre de usuario de Windows tiene caracteres extendidos de Unicode, esto podría causar un error de respuesta de AskPass. Para solucionar los problemas, crea una cuenta nueva de usuario de Windows y migra tus archivos a dicha cuenta. Para obtener más información, consulta la sección "[Crear una cuenta de usuario en Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" en la documentación de Microsoft. + +{% endwindows %} + +### Further reading +- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-a-default-editor.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-a-default-editor.md new file mode 100644 index 0000000000000..7faaf4382669f --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-a-default-editor.md @@ -0,0 +1,74 @@ +--- +title: Configurar un editor predeterminado +intro: Puedes configurar GitHub Desktop para abrir archivos en tu proyecto con tu editor de texto o ambiente de desarrollo integrado (IDE) preferidos. +redirect_from: + - /desktop/getting-started-with-github-desktop/configuring-a-default-editor +versions: + free-pro-team: '*' +--- + +### Editores compatibles + +{% data variables.product.prodname_desktop %} es compatible con los siguientes editores. + +{% mac %} + +- [Atom](https://atom.io/) +- [MacVim](https://macvim-dev.github.io/macvim/) +- [Visual Studio Code](https://code.visualstudio.com/) +- [Visual Studio Codium](https://vscodium.com/) +- [Sublime Text](https://www.sublimetext.com/) +- [BBEdit](http://www.barebones.com/products/bbedit/) +- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) +- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) +- [JetBrains Rider](https://www.jetbrains.com/rider/) +- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/) +- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/) +- [JetBrains IntelliJ IDEA](https://www.jetbrains.com/idea/) +- [JetBrains GoLand](https://www.jetbrains.com/go/) +- [TextMate](https://macromates.com/) +- [Brackets](http://brackets.io/) + - Para utilizar Brackets con {% data variables.product.prodname_desktop %}, debes instalar el atajo de la línea de comandos. Para instalar el atajo, abre Brackets, da clic en **Archivo** en la barra de menú y luego da clic en **Instalar Atajo para la Línea de Comandos**. +- [Typora](https://typora.io/) +- [CodeRunner](https://coderunnerapp.com/) +- [SlickEdit](https://www.slickedit.com/) +- [Xcode](https://developer.apple.com/xcode/) +- [Android Studio](https://developer.android.com/studio) + +{% endmac %} + +{% windows %} + +- [Atom](https://atom.io/) +- [Visual Studio Code](https://code.visualstudio.com/) +- [Visual Studio Codium](https://vscodium.com/) +- [Sublime Text](https://www.sublimetext.com/) +- [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) +- [Typora](https://typora.io/) +- [SlickEdit](https://www.slickedit.com/) +- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) +- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) +- [JetBrains Rider](https://www.jetbrains.com/rider/) +- [Notepad++](https://notepad-plus-plus.org/) + +{% endwindows %} + +### Configurar un editor predeterminado + +{% mac %} + +{% data reusables.desktop.mac-select-desktop-menu %} +3. En la ventana de preferencias, selecciona **Integrations** (integraciones). ![El panel de Integraciones en la ventana de Preferencias](/assets/images/help/desktop/mac-select-integrations-pane.png) +4. Utiliza el menú desplegable de "Editor Externo" y elige el editor que quieras configurar como predeterminado. ![El menú External editor (Editor externo) en la barra del menú Preferences (Preferencias)](/assets/images/help/desktop/mac-editor-menu.png) +5. Haz clic en **Save ** (guardar). + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-choose-options %} +3. En la ventana de Opciones, seleccione **Integrations** (integraciones). ![El panel de Integraciones en la ventana de Opciones](/assets/images/help/desktop/windows-select-integrations-pane.png) +4. Utiliza el menú desplegable de "Editor Externo" y elige el editor que quieras configurar como predeterminado. ![El menú External editor (Editor externo) en la barra del menú Options (Opciones)](/assets/images/help/desktop/windows-editor-menu.png) +5. Haz clic en **Save ** (guardar). + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md new file mode 100644 index 0000000000000..98483f273f8aa --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md @@ -0,0 +1,10 @@ +--- +title: Configurar y personalizar GitHub Desktop +intro: 'Cómo configurar Git, conectar tu editor predeterminado y personalizar las opciones para alinear GitHub Desktop con tu flujo de trabajo.' +mapTopic: verdadero +redirect_from: + - /desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md new file mode 100644 index 0000000000000..32d7544d1fe2b --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md @@ -0,0 +1,28 @@ +--- +title: Configurar parámetros básicos +intro: 'Puedes acceder a la configuración para proteger tu privacidad, conectar cuentas a GitHub Desktop, y configurar Git.' +redirect_from: + - /desktop/getting-started-with-github-desktop/configuring-basic-settings +versions: + free-pro-team: '*' +--- + +{% mac %} + +{% data reusables.desktop.mac-select-desktop-menu %} +3. Para ver o cambiar tu configuración, alterna entre estos paneles:![La navegación por el menú Preferences (Preferencias)](/assets/images/help/desktop/mac-select-accounts-pane.png) +{% data reusables.desktop.preferences-options-tabs %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-choose-options %} +2. Para ver o cambiar tu configuración, alterna entre estos paneles:![La navegación por el menú Options (Opciones)](/assets/images/help/desktop/windows-select-accounts-pane.png) +{% data reusables.desktop.preferences-options-tabs %} + +{% endwindows %} + +### Further reading + +- "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md new file mode 100644 index 0000000000000..e87dc1321d634 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md @@ -0,0 +1,60 @@ +--- +title: Configurar Git para GitHub Desktop +shortTitle: Configurar Git +intro: 'Si todavía no tienes Git instalado, debes configurarlo antes de usar GitHub Desktop.' +redirect_from: + - /desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_desktop %} utiliza la dirección de correo electrónico que configuraste en tus ajustes locales de Git para conectar las confirmaciones con tu cuenta en {% data variables.product.product_name %}. + +{% data reusables.desktop.update-email-address %} + +{% tip %} + +**Tip**: Cualquiera podrá ver la dirección de correo electrónico en tu configuración de Git si haces confirmaciones públicas. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)." + +{% endtip %} + +{% mac %} + +{% data reusables.desktop.sign-in-choose-product %} +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +{% data reusables.desktop.copy-email-git-config %} +{% data reusables.desktop.return-to-desktop %} +{% data reusables.desktop.mac-select-desktop-menu %} +7. En la ventana de preferencias, da clic en **Git**. ![El panel de Git en el menú Preferences (Preferencias)](/assets/images/help/desktop/mac-select-git-pane.png) +{% data reusables.desktop.name-field-git-config %} + ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/mac-name-git-config.png) +{% data reusables.desktop.paste-email-git-config %} + ![La dirección de correo electrónico copiada en el campo de configuración de Git](/assets/images/help/desktop/mac-email-git-config.png) +{% data reusables.desktop.click-save-git-config %} + ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/mac-save-git-config.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.sign-in-choose-product %} +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +{% data reusables.desktop.copy-email-git-config %} +{% data reusables.desktop.return-to-desktop %} +{% data reusables.desktop.windows-choose-options %} +8. En la ventana de Opciones, da clic en **Git**. ![El panel de Git en el menú Options (Opciones)](/assets/images/help/desktop/windows-select-git-pane.png) +{% data reusables.desktop.name-field-git-config %} + ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/windows-name-git-config.png) +{% data reusables.desktop.paste-email-git-config %} + ![La dirección de correo electrónico copiada en el campo de configuración de Git](/assets/images/help/desktop/windows-email-git-config.png) +{% data reusables.desktop.click-save-git-config %} + ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/windows-save-git-config.png) + +{% endwindows %} + +### Further reading + +- [Agregar una dirección de correo electrónico a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account/)" +- "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)." diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md new file mode 100644 index 0000000000000..ddd3c4dcd430c --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md @@ -0,0 +1,97 @@ +--- +title: Crear el primer repositorio mediante GitHub Desktop +shortTitle: Crear tu primer repositorio +intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para crear y administrar un repositorio de Git sin utilizar la línea de comandos.' +redirect_from: + - /desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop +versions: + free-pro-team: '*' +--- + +### Introducción +{% data variables.product.prodname_desktop %} se extiende y simplifica tu flujo de trabajo {% data variables.product.prodname_dotcom_the_website %}, usando una interfaz visual en lugar de comandos de texto en la línea de comandos. Al final de esta guía, habrás utilizado {% data variables.product.prodname_desktop %} para crear un repositorio, hacer cambios en éste y publicarlos en {% data variables.product.product_name %}. + +Después de instalar {% data variables.product.prodname_desktop %} y de iniciar sesión en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, deberás crear y clonar un repositorio de tutorial. El tutorial te presentará lo básico de trabajar con Git y con {% data variables.product.prodname_dotcom %}, incluyendo el instalar un editor de texto, crear una rama, hacer una confirmación, cargarla a {% data variables.product.prodname_dotcom_the_website %} y abrir una solicitud de extracción. El tutorial está disponible si aún no tienes ningún repositorio en {% data variables.product.prodname_desktop %}. + +Te recomendamos completar el tutorial, pero si quieres explorar {% data variables.product.prodname_desktop %} creando un nuevo repositorio, esta guía te describirá cómo utilizar {% data variables.product.prodname_desktop %} para trabajar en un repositorio de Git. + +### Parte 1: Instalar {% data variables.product.prodname_desktop %} y autenticar tu cuenta +Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Después de instalar la app, necesitarás iniciar sesión y autenticarte en tu cuenta de {% data variables.product.prodname_dotcom %} o de {% data variables.product.prodname_enterprise %} antes de que puedas crear y clonar un repositorio de tutorial. + +Para obtener más información sobre la instalación y autenticación, consulta la sección "[Configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)". + +### Parte 2: Crear un repositorio nuevo +Si no tienes ningún repositorio asociado con {% data variables.product.prodname_desktop %}, tendrás una vista de "Let's get started!", en donde podrás elegir crear y clonar un repositorio de tutorial, clonar un repositorio existente desde internet, crear un repositorio nuevo, o agregar un repositorio existente desde tu disco duro. ![¡Comencemos! Pantalla](/assets/images/help/desktop/lets-get-started.png) + +#### Crear y clonar un repositorio de tutorial +Te recomendamos que tu primer poyecto sea crear y clonar un repositorio de tutorial para practicar cómo utilizar {% data variables.product.prodname_desktop %}. + +1. Haz clic en **Create a tutorial repository and clone it** (Crear un repositorio de tutorial y clonarlo). ![Crear y clonar un botón de repositorio de tutorial](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png) +2. Sigue las instrucciones en el tutorial para instalar un editor de texto, crear una rama, editar un archivo, hacer una confirmación, publicar en {% data variables.product.prodname_dotcom %} y abrir una solicitud de extracción. + +#### Crear un repositorio nuevo +Si no quieres crear y clonar un repositorio de tutorial, puedes crear un repositorio nuevo. + +1. Haz clic en **Crear un nuevo repositorio en tu disco duro...** ![Crear un repositorio nuevo](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png) +2. Llena los campos y selecciona tus opciones preferidas. ![Crear un repositorio de opciones](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png) + - "Name" (Nombre) define el nombre de tu repositorio a nivel local y en {% data variables.product.product_name %}. + - "Description" (Descripción) es un campo opcional que puedes usar para brindar más información sobre el objetivo de tu repositorio. + - "Local path" (Ruta local) establece la ubicación de tu repositorio en tu computadora. De manera predeterminada, {% data variables.product.prodname_desktop %} crea una carpeta _GitHub_ en tu carpeta _Documents_ (Documentos) para almacenar tus repositorios, pero puedes elegir cualquier ubicación en tu computadora. Tu nuevo repositorio será una carpeta dentro de la ubicación elegida. Por ejemplo, si colocas el nombre `Tutorial` a tu repositorio, se creará la carpeta _Tutorial_ dentro de la carpeta que seleccionaste en tu ruta local. {% data variables.product.prodname_desktop %} recuerda tu ubicación elegida la próxima vez que crees o clones un repositorio nuevo. + - **Si inicializas este repositorio con un README** (Léeme), se crea una confirmación inicial con un archivo _README.md_. README ayuda a las personas a comprender el objetivo de tu proyecto, por lo que recomendamos seleccionarlo y completarlo con información útil. Cuando alguien visita tu repositorio en {% data variables.product.product_name %}, el archivo README es lo primero que verán a medida que aprenden sobre tu proyecto. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". + - El menú desplegable **Git ignore** (Ignorar Git) te permite agregar un archivo personalizado para ignorar los archivos específicos en tu repositorio local que no deseas almacenar en el control de la versión. Si hay un lenguaje o marco de trabajo que estarás utilizando, puedes seleccionar una opción de la lista disponible. Si recién estás comenzando, puedes omitir esta selección. Para obtener más información, consulta "[Ignorar archivos](/articles/ignoring-files)". + - El menú desplegable **License** (Licencia) te permite agregar una licencia de código abierto para un archivo _LICENSE_ (Licencia) en tu repositorio. No tienes que preocuparte por aprender cómo agregar una licencia inmediatamente. Para obtener más información sobre las licencias de código abierto disponibles y cómo agregarlas a tu repositorio, consulta "[Licenciar un repositorio](/articles/licensing-a-repository)". +3. Haz clic en **Crear repositorio**. + +### Parte 3: Explorar {% data variables.product.prodname_desktop %} +En el menú del archivo en la parte superior de la pantalla, puedes acceder a la configuración y a las acciones que puedes realizar en {% data variables.product.prodname_desktop %}. La mayoría de las acciones tienen atajos del teclado para ayudarte a trabajar con más eficacia. Para encontrar un listado completo de atajos de teclado, consulta la sección "[Atajos de teclado](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)". + +#### La barra de menú de {% data variables.product.prodname_desktop %} +En la parte superior de la app de {% data variables.product.prodname_desktop %}, verás una barra que muestra el estado actual de tu repositorio. + - **Current repository** (Repositorio actual) muestra el nombre del repositorio en el que estás trabajando. Puedes hacer clic en **Current repository** (Repositorio actual) para alternar a un repositorio diferente en {% data variables.product.prodname_desktop %}. + - **Current branch** (Rama actual) muestra el nombre de la rama en la que estás trabajando. Puedes hacer clic en **Current branch** (Rama actual) para ver todas las ramas en tu repositorio, alternar a una rama diferente o crear una rama nueva. Una vez que creaste solicitud de extracción en tu repositorio, también puedes verlas haciendo clic en **Current branch** (Rama actual). + - **Publish repository** (Publicar repositorio) aparece porque todavía no has publicado tu repositorio en {% data variables.product.product_name %}. que harás a continuación en el próximo paso. Esta sección de la barra cambiará con base en el estado de tu repositorio y rama actuales. Varias acciones dependientes del contexto estarán disponibles, las cuales te permitirán intercambiar datos entre tus repositorios locales y remotos. + + ![Explorar el escritorio de GitHub](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png) + +#### Cambios e Historial +En la barra lateral a la izquierda, encontrarás la vista **Changes** (Cambios) y la vista**History** (Historial). ![Las pestañas de cambios y de historial](/assets/images/help/desktop/changes-and-history.png) + + - La vista **Changes** (Cambios) muestra los cambios que realizaste a los archivos en tu rama actual pero aún no confirmaste en tu repositorio local. En la parte inferior, encontrarás un recuadro con cajas de texto para "Resumen" y "Descripción", y un botón de **Confirmar a RAMA**. Aquí es donde confirmarás los campos nuevos. El botón de **Confirmar a RAMA** es dinámico y mostrará a qué rama estás confirmando tus cambios. ![Área de confirmación de cambios](/assets/images/help/desktop/getting-started-guide/commit-area.png) + + - La vista **History** (Historial) muestra las confirmaciones previas en la rama actual de tu repositorio. Deberías ver una "Initial commit" (Confirmación inicial) que fue creada por {% data variables.product.prodname_desktop %} cuando creaste tu repositorio. A la derecha de la confirmación, según las opciones que seleccionaste al crear tu repositorio, es posible que veas los archivos _.gitattributes_, _.gitignore_, _LICENSE_, o _README_. Puedes hacer clic en cada archivo para ver una diferencia para ese archivo, que son los cambios realizados en el archivo en esa confirmación. La diferencia solo muestra las partes del archivo que han cambiado, no slo los contenidos completos del archivo. ![Vista de historial](/assets/images/help/desktop/getting-started-guide/history-view.png) + +### Parte 4: Publicar tu repositorio en {% data variables.product.product_name %} +Cuando creas un repositorio nuevo, éste solo existirá en tu computadora y serás el único que pueda acceder a él. Puedes publicar tu repositorio en {% data variables.product.product_name %} para mantenerlo sincronizado a través de varias computadoras y permitir que otras personas accedan a él. Para publicar tu repositorio, sube tus cambios locales a {% data variables.product.product_name %}. + +1. Da clic en **Publicar repositorio** en la barra de menú. ![Publicar repositorio](/assets/images/help/desktop/getting-started-guide/publish-repository.png) + - {% data variables.product.prodname_desktop %} llenará los campos de "Nombre" y "Descripción" automáticamente con la información que ingresaste cuando creaste el repositorio. + - La opción de **Mantener este código como privado** te permite controlar quién puede ver tu proyecto. Si no seleccionas esta opción, otros usuarios en {% data variables.product.product_name %} podrán ver tu código. Si seleccionas esta opción, tu código no estará disponible al público en general. + - El menú desplegable de **Organización**, si es que lo hay, te permite publicar tu repositorio en una organización específica en {% data variables.product.product_name %} a la cual pertenezcas. + + ![Publicar pasos del repositorio](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png) + 2. Haz clic en el botón **Publish Repository** (Publicar repositorio). + 3. Puedes acceder al repositorio en {% data variables.product.prodname_dotcom_the_website %} desde el interior de {% data variables.product.prodname_desktop %}. En el menú del archivo, haz clic en **Repository** (Repositorio), luego haz clic en **View on GitHub** (Ver en GitHub). Esto te llevará directamente hasta el repositorio en tu navegador predeterminado. + +### Parte 5: Hacer, confirmar y subir cambios +Ahora que creaste y publicaste tu repositorio, estás listo para hacer cambios en tu proyecto y comenzar a crear tu primera confirmación para este repositorio. + +1. Para lanzar tu editor externo desde dentro de {% data variables.product.prodname_desktop %}, da clic en **Repositorio**, luego da clic en **Abrir en EDITOR**. Para obtener más información, consulta la sección "[Configurar un editor predeterminado](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)". ![Abrir en editor](/assets/images/help/desktop/getting-started-guide/open-in-editor.png) + +2. Haz algunos cambios al archivo _README.md_ que hayas creado previamente. Puedes agregar información que describa tu proyecto, como por ejemplo, que es lo que hace y por qué es útil. Cuando estés satisfecho con los cambios, guárdalos en tu editor de texto. +3. En {% data variables.product.prodname_desktop %}, navega a la vista de **Cambios**. En la lista de archivos, deberías ver tu _README.md_. La marca de verificación a la izquierda del archivo _README.md_ indica que los cambios que has hecho al archivo serán parte de la confirmación que haces. En el futuro, es posible que realices cambios a múltiples archivos pero solo quieras confirmar los cambios que realizaste en alguno de los archivos. Si das clic en la marca de verificación contigua a un archivo, este archivo no se incluirá en la confirmación. ![Ver cambios](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) + +4. En la parte inferior de la lista **Changes** (Cambios), escribe un mensaje de confirmación. A la derecha de tu imagen de perfil, escribe una descripción breve de la confirmación. Dado que estamos cambiando el archivo _README.md_, "Agregar información sobre el objetivo del proyecto" sería un buen resumen de la confirmación. Debajo del resumen, verás un campo de texto de "Descripción" en donde podrás teclear una descripción más amplia de los cambios en la confirmación, lo cual es de gran ayuda cuando regresas a ver el historial de un proyecto y entiendes por qué se realizaron los cambios. Dado que estás realizando una actualización básica de un archivo _README.md_, puedes omitir la descripción. ![Mensaje de confirmación](/assets/images/help/desktop/getting-started-guide/commit-message.png) +5. Da clic en **Confirmar al NOMBRE DE RAMA**. El botón de confirmación muestra tu rama actual, así que puedes estar seguro de confirmar a la rama que quieras. ![Confirmar a una rama](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) +6. Para subir los cambios al repositorio remoto en {% data variables.product.product_name %}, haz clic en **Push origin** (Subir origen). ![Subir origen](/assets/images/help/desktop/getting-started-guide/push-to-origin.png) + - El botón de **Subir el origen** es el mismo en el que diste clic para publicar tu repositorio en {% data variables.product.product_name %}. Este botón cambia contextualmente con base en el punto en el que estés en el flujo de trabajo de Git. Ahora debería decir `Subir el origen` con un `1` en un costado, indicando que hay una confirmación que no se ha subido a {% data variables.product.product_name %}. + - El "origen" en **Subir el origen** significa que estás subiendo los cambios al repositorio remoto llamado `origin`, que en este caso es el repositorio de tu proyecto en {% data variables.product.prodname_dotcom_the_website %}. Hasta que hayas subido alguna de las nuevas confirmaciones {% data variables.product.product_name %}, habrá diferencias entre el repositorio de tu proyecto en tu computadora y el repositorio del proyecto en {% data variables.product.prodname_dotcom_the_website %}. Esto te permite trabajar localmente y solo subir tus cambios a {% data variables.product.prodname_dotcom_the_website %} cuando estés listo. +7. En la ventana, a la derecha de la vista de **Cambios**, verás las sugerencias para las acciones que puedes hacer después. Para abrir el repositorio en {% data variables.product.product_name %} en tu buscador, da clic en **Ver en {% data variables.product.product_name %}**. ![Acciones disponibles](/assets/images/help/desktop/available-actions.png) +8. En tu navegador, haz clic en **2 commits** (2 confirmaciones). Verás una lista de las confirmaciones en este repositorio en {% data variables.product.product_name %}. La primera confirmación deberá ser aquella que acabas de realizar en {% data variables.product.prodname_desktop %}. ![Hacer clic en dos confirmaciones](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) + +### Conclusión +Ya creaste un repositorio, lo publicaste en {% data variables.product.product_name %}, hiciste una confirmación y subiste tus cambios a {% data variables.product.product_name %}. Puedes seguir este flujo de trabajo cuando colabores con otros proyectos que crees o en los cuales colabores. + +### Further reading +- "[Aprender más sobre Git](/github/using-git/learning-about-git)" +- "[Aprender más sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" +- "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md new file mode 100644 index 0000000000000..91f180beb2416 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md @@ -0,0 +1,107 @@ +--- +title: Comenzar con GitHub Desktop +intro: 'Aprende cómo ajustar, autenticar y configurar {% data variables.product.prodname_desktop %} para permitirte contribuir en proyectos directamente desde tu máquina.' +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +--- + +### Introducción +{% data variables.product.prodname_desktop %} es una aplicación que te habilita para interactuar con {% data variables.product.prodname_dotcom %} utilizando una GUI en vez de la línea de comandos o de un buscador web. {% data variables.product.prodname_desktop %} fomenta que tú y tu equipo colaboren utilizando las mejoras prácticas con Git y {% data variables.product.prodname_dotcom %}. Puedes utilizar {% data variables.product.prodname_desktop %} para completar la mayoría de los comandos de Git desde tu computadora de escritorio con confirmaciones visuales para los cambios. Puedes subir, extraer y clonar repositorios remotos con {% data variables.product.prodname_desktop %} y utilizar herramientas colaborativas tales como atribuir confirmaciones y crear solicitudes de extracción. + +Esta guía te ayudará a iniciar con {% data variables.product.prodname_desktop %} mediante la configuración de la aplicación, la autenticación en tu cuenta, la configuración de ajustes básicos y la introducción de las bases fundamentales para administrar los proyectos con {% data variables.product.prodname_desktop %}. Podrás utilizar {% data variables.product.prodname_desktop %} para colaborar en proyectos y conectarte a repositorios remotos después de seguir esta guía. + +Puede que te sea útil el entender los conceptos básicos de Git y de {% data variables.product.prodname_dotcom %} antes de comenzar a utilizar {% data variables.product.prodname_desktop %}. Para obtener más información, consulta los siguientes artículos. + +- "[Aprender más sobre Git](/github/using-git/learning-about-git)" +- "[Aprender más sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" +- "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" + +{% data variables.product.prodname_desktop %} es un proyecto de código abierto. Puedes ver el itinerario, contribuir con el proyecto, o abrir un informe de problemas para proporcionar retroalimentación o solicitudes de características. Para obtener más información, consulta el repositorio [`desktop/desktop`](https://github.com/desktop/desktop). + +### Parte 1: Instalación y autenticación +Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Para obtener más información, consulta la sección "[Sistemas operativos compatibles](/desktop/getting-started-with-github-desktop/supported-operating-systems)". + +Para instalar {% data variables.product.prodname_desktop %}, visita la página de descargas para [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). Para obtener más información, consulta la sección "[Instalar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/installing-github-desktop)". + +Después de que hayas instalado {% data variables.product.prodname_desktop %}, puedes autenticar la aplicación con tu cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. Esta autenticación te permite conectarte remotamente a los repositorios en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. + +{% mac %} + +1. Antes de que te puedas autenticar en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, necesitarás una cuenta. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/github/getting-started-with-github/signing-up-for-a-new-github-account)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. + +2. En el menú desplegable de {% data variables.product.prodname_desktop %}, da clic en **Preferencias**. En la ventana de preferencias, da clic en **Cuentas** y sigue los pasos para iniciar sesión. Para obtener más información sobre la autenticación, consulta la sección "[Autenticarte en {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-github.png) + +{% endmac %} + +{% windows %} + +1. Antes de que te puedas autenticar en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, necesitarás una cuenta. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/github/getting-started-with-github/signing-up-for-a-new-github-account)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. + +2. En el menú desplegable de archivo, da clic en **Opciones**. En la ventana de opciones, da clic en **Cuentas** y sigue los pasos para iniciar sesión. Para obtener más información sobre la autenticación, consulta la sección "[Autenticarte en {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-github.png) + +{% endwindows %} + +### Parte 2: Configurar y personalizar {% data variables.product.prodname_desktop %} +Después de que instales {% data variables.product.prodname_desktop %}, puedes configurar y personalizar la app para que se adapte mejor a tus necesidades. + +{% mac %} + +Puedes conectar o eliminar cuentas en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, elegir un editor de texto o shell predeterminado, editar tu configuración de Git, cambiar la apariencia de {% data variables.product.prodname_desktop %}, personalizar los diálogos de sistema y configurar las preferencias de privacidad en la ventana de Preferencias de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". + + ![Los ajustes básicos en la ventana de Preferencias](/assets/images/help/desktop/mac-appearance-tab-themes.png) + +{% endmac %} + +{% windows %} + +Puedes conectar o eliminar cuentas en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, elegir un editor de texto o shell predeterminado, editar tu configuración de Git, cambiar la apariencia de {% data variables.product.prodname_desktop %}, personalizar los diálogos de sistema y configurar las preferencias de privacidad en la ventana de Opciones de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". + + ![Los ajustes básicos en la ventana de Opciones](/assets/images/help/desktop/windows-appearance-tab-themes.png) + +{% endwindows %} + +### Parte 3: Colaborar en proyectos con {% data variables.product.prodname_desktop %} +Después deinstalar, autenticarte y configurar la app, estás listo para comenzar a utilizar {% data variables.product.prodname_desktop %}. Puedes crear, agregar, o clonar los repositorios y utilizar {% data variables.product.prodname_desktop %} para administrar las contribuciones a tus repositorios. + +#### Crear, agregar y clonar repositorios +Puedes crear un repositorio nuevo si seleccionas el menú de archivo y das clic en **Repositorio nuevo...**. Para obtener más información, consulta la sección "[Crear tu primer repositorio utilizando {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop)". + +Puedes agregar un repositorio desde tu computadora local si seleccionas el menú de Archivo y das clic en **Agregar Repositorio Local...**. Para obtener más información, consulta la sección [Agregar un repositorio a {% data variables.product.prodname_desktop %} desde tu computadora local](/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop)". + +Puedes clonar un repositorio desde {% data variables.product.prodname_dotcom %} si seleccionas el menú de Archivo y das clic en **Clonar Repositorio...**. Para obtener más información, consulta la sección "[Clonar y Bifurcar Repositorios desde {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)". + +{% mac %} + + ![Las opciones del menú de Archivo para crear, agregar, y clonar repositorios](/assets/images/help/desktop/mac-file-menu.png) + +{% endmac %} + +{% windows %} + + ![Las opciones del menú de Archivo para crear, agregar, y clonar repositorios](/assets/images/help/desktop/windows-file-menu.png) + +{% endwindows %} + +#### Realizar cambios en una rama +Puedes utilizar {% data variables.product.prodname_desktop %} para crearuna rama de un proyecto. Las ramas aislan tu trabajo de desarrollo de otras ramas en el repositorio para que puedas experimentar con varios cambios de manera segura. Para obtener más información, consulta la sección "[Administrar ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)". + + ![El botón de Rama Nueva](/assets/images/help/desktop/new-branch-button-mac.png) + +Después de que hagas cambios a una rama, puedes revisarlos en {% data variables.product.prodname_desktop %} y hacer una confirmación para controlar dichos cambios. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)". + + ![Viualizar y hacer confirmaciones](/assets/images/help/desktop/commit-button.png) + +Si quieres acceder a tus cambios de manera remota o si quieres compartirlos con otras personas, puedes cargar tus confirmaciones en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Subir los cambios a {% data variables.product.prodname_dotcom %}](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)". + +#### Colaborar con {% data variables.product.prodname_desktop %} +Puedes utilizar {% data variables.product.prodname_desktop %} para crear informes de problemas o solicitudes de extracción para colaborar en proyectos con otras personas. Los informes de problemas te ayudan a llevar un seguimiento de las ideas y debatir los posibles cambios a los proyectos. Las solicitudes de extracción te permiten compartir tus cambios propuestos con los demás, recibir retroalimentación y fusionar los cambios en un proyecto. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request)."'' + +Puedes ver tus propias solicitudes de extracción o las de tus colaboradores en {% data variables.product.prodname_desktop %}. El visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %} te permite ver cualquier cambio propuesto y hacer cambios adicionales si abres los repositorios y archivos del proyecto en tu editor de texto predeterminado. Para obtener más información, consulta la sección "[Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop)". + +#### Mantener tu repositorio local sincronizado +Cuando haces cambios a tus repositorios locales o cuando otros hacen cambios a los repositorios remotos, necesitarás sincronizar tu copia local del proyecto con el repositorio remoto. {% data variables.product.prodname_desktop %} puede mantener sincronizada tu copia local de un proyecto con la versión remota al subir y extraer las confirmaciones. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". + +### Further reading +- "[Instalar y autenticarse en {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)" +- "[Colaborar y contribuir utilizando {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/index.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/index.md new file mode 100644 index 0000000000000..713f079c4a85f --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/index.md @@ -0,0 +1,32 @@ +--- +title: Instalar y configurar GitHub Desktop +shortTitle: Instalar y configurar +intro: 'Configura a {% data variables.product.prodname_desktop %} para que administre el trabajo de tu proyecto. Autentícate en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_enterprise %}, mantén la app actualizada y revisa tu configuración preferida.' +redirect_from: + - /desktop/getting-started-with-github-desktop +versions: + free-pro-team: '*' +--- + + +### Índice + +{% topic_link_in_list /overview %} + {% link_in_list /getting-started-with-github-desktop %} + {% link_in_list /creating-your-first-repository-using-github-desktop %} + {% link_in_list /supported-operating-systems %} + {% link_in_list /keyboard-shortcuts %} + {% link_in_list /launching-github-desktop-from-the-command-line %} +{% topic_link_in_list /installing-and-authenticating-to-github-desktop %} + {% link_in_list /setting-up-github-desktop %} + {% link_in_list /installing-github-desktop %} + {% link_in_list /authenticating-to-github %} + {% link_in_list /about-connections-to-github %} + {% link_in_list /updating-github-desktop %} + {% link_in_list /uninstalling-github-desktop %} +{% topic_link_in_list /configuring-and-customizing-github-desktop %} + {% link_in_list /configuring-git-for-github-desktop %} + {% link_in_list /configuring-basic-settings %} + {% link_in_list /configuring-a-default-editor %} + {% link_in_list /setting-a-theme-for-github-desktop %} + {% link_in_list /about-git-large-file-storage-and-github-desktop %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md new file mode 100644 index 0000000000000..71b7006814131 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md @@ -0,0 +1,10 @@ +--- +title: Cómo instalar y autenticarse en GitHub Desktop +intro: Instalar GitHub Desktop y conectar tus cuentas de GitHub y GitHub Enterprise. +mapTopic: verdadero +redirect_from: + - /desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md new file mode 100644 index 0000000000000..3d4b4865f481e --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-github-desktop.md @@ -0,0 +1,54 @@ +--- +title: Instalar GitHub Desktop +shortTitle: Instalación +intro: Puedes instalar GitHub Desktop en sistemas operativos Windows o macOS compatibles. +redirect_from: + - /desktop/getting-started-with-github-desktop/installing-github-desktop +versions: + free-pro-team: '*' +--- + +### Acerca de la instalación de {% data variables.product.prodname_desktop %} + +Puedes instalar {% data variables.product.prodname_desktop %} en los sistemas operativos compatibles. Si tienes una cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, puedes conectarla a {% data variables.product.prodname_desktop %}. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account/)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. + +{% windows %} + +Si eres un administrador de red, puedes desplegar {% data variables.product.prodname_desktop %} en las computadoras con Windows en una red que se administre con Active Directory si utilizas el archivo de paquete de instalador para Windows (`.msi`) con la Política de grupo o con otro sistema de instalación remoto. + +El paquete de instalación de Windows extrae el instalador independiente (`.exe`) y configura a Windows para instalar {% data variables.product.prodname_desktop %} en la siguiente ocasión que el usuario ingrese a su estación de trabajo. Los usuarios deben tener permisos para instalar {% data variables.product.prodname_desktop %} en su directorio de usuario. + +Si un usuario ejecuta el paquete de instalación en Windows de {% data variables.product.prodname_desktop %} directamente, para completar la instalación, el usuario debe salir de su sesión en su estación de trabajo y volverse a firmar. + +{% endwindows %} + +### Descargar e instalar {% data variables.product.prodname_desktop %} + +{% mac %} + +Puedes instalar {% data variables.product.prodname_desktop %} en {% data variables.desktop.mac-osx-versions %}. + +{% data reusables.desktop.download-desktop-page %} +2. Da clic en **Descargar para macOS**. ![El botón de Descargar para MacOS](/assets/images/help/desktop/download-for-mac.png) +3. En la carpeta `Download` (Descargas) de tu computadora, haz doble clic en el archivo comprimido **{% data variables.product.prodname_desktop %}**. ![El archivo de GitHubDesktop.zip](/assets/images/help/desktop/mac-zipfile.png) +4. Una vez que se descomprima el archivo, haz doble clic en **{% data variables.product.prodname_desktop %}**. +5. {% data variables.product.prodname_desktop %} se lanzará después de que se complete la instalación. + +{% endmac %} + +{% windows %} + +Puedes instalar {% data variables.product.prodname_desktop %} en {% data variables.desktop.windows-versions %}. + +{% warning %} + +**Advertencia**: Debes tener un sistema operativo de 64 bits para ejecutar {% data variables.product.prodname_desktop %}. + +{% endwarning %} + +{% data reusables.desktop.download-desktop-page %} +2. Da clic en **Descargar para Windows**. ![El botón de Descargar para Windows](/assets/images/help/desktop/download-for-windows.png) +3. En la carpeta `Download` de tu computadora, da doble clic en el archivo de configuración de **{% data variables.product.prodname_desktop %}**. ![El archivo de GitHubDesktopSetup](/assets/images/help/desktop/windows-githubdesktopsetup.png) +4. {% data variables.product.prodname_desktop %} se lanzará después de que se complete la instalación. + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/keyboard-shortcuts.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/keyboard-shortcuts.md new file mode 100644 index 0000000000000..07c4d762918c0 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/keyboard-shortcuts.md @@ -0,0 +1,120 @@ +--- +title: Atajos del teclado +intro: 'Puedes usar los atajos de teclado en {% data variables.product.prodname_desktop %}.' +redirect_from: + - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop/ + - /desktop/getting-started-with-github-desktop/keyboard-shortcuts +versions: + free-pro-team: '*' +--- + +{% mac %} + +Atajos de teclado de GitHyb Desktop en macOS + +### Atajos en todo el sitio + +| Atajo del teclado | Descripción | +| ------------------------------------ | ------------------------------------------------------------------- | +| ⌘, | Ir a Preferences (Preferencias) | +| ⌘H | Ocultar la aplicación {% data variables.product.prodname_desktop %} +| ⌥⌘H | Ocultar todas las otras aplicaciones | +| ⌘Q | Dejar {% data variables.product.prodname_desktop %} +| ⌃⌘F | Alternar vista de pantalla completa | +| ⌘0 | Restablecer zoom al tamaño de texto predeterminado | +| ⌘= | Acercar para textos y gráficos más grandes | +| ⌘- | Alejar para textos y gráficos más pequeños | +| ⌥⌘I | Alternar herramientas del desarrollador | + +### Repositorios + +| Atajo del teclado | Descripción | +| ------------------------------------ | ------------------------------------------------------------------------------- | +| ⌘N | Agregar un repositorio nuevo | +| ⌘O | Agregar un repositorio local | +| ⇧⌘O | Clonar un repositorio desde {% data variables.product.prodname_dotcom %} +| ⌘T | Mostrar una lista de tus repositorios | +| ⌘P | Subir las últimas confirmaciones a {% data variables.product.prodname_dotcom %} +| ⇧⌘P | Bajar los últimos cambios de {% data variables.product.prodname_dotcom %} +| ⌘⌫ | Eliminar un repositorio existente | +| ⇧⌘G | Ver el repositorio en {% data variables.product.prodname_dotcom %} +| ⌃` | Abrir el repositorio en tu herramienta de terminal preferida | +| ⇧⌘F | Mostrar el repositorio en Finder | +| ⇧⌘A | Abrir el repositorio en tu herramienta de editor preferida | +| ⌘I | Crear un informe de problemas en {% data variables.product.prodname_dotcom %} + +### Ramas + +| Atajo del teclado | Descripción | +| ------------------------------------ | ----------------------------------------------------------------------------------------- | +| ⌘1 | Mostrar todos los cambios antes de confirmar | +| ⌘2 | Mostrar tu historial de confirmaciones | +| ⌘B | Mostrar todas tus ramas | +| ⌘G | Ir al campo de resumen de confirmaciones | +| ⌘Enter | Confirma los cambios cuando el campo de resumen o de descripción está activo | +| espacio | Selecciona o deselecciona todos los archivos resaltados | +| ⇧⌘N | Crear una rama nueva | +| ⇧⌘R | Renombrar la rama actual | +| ⇧⌘D | Eliminar la rama actual | +| ⇧⌘U | Actualizar desde la rama predeterminada | +| ⇧⌘B | Comparar con una rama existente | +| ⇧⌘M | Fusionar en una rama actual | +| ⌃H | Mostrar u ocultar cambios acumulados | +| ⇧⌘C | Comparar ramas en {% data variables.product.prodname_dotcom %} +| ⌘R | Mostrar la solicitud de extracción actual en {% data variables.product.prodname_dotcom %} + +{% endmac %} + +{% windows %} + +Atajos de teclado de GitHub Desktop en Windows + +### Atajos en todo el sitio + +| Atajo del teclado | Descripción | +| ------------------------------------------- | -------------------------------------------------- | +| Ctrl, | Ir a Options (Opciones) | +| F11 | Alternar vista de pantalla completa | +| Ctrl0 | Restablecer zoom al tamaño de texto predeterminado | +| Ctrl= | Acercar para textos y gráficos más grandes | +| Ctrl- | Alejar para textos y gráficos más pequeños | +| CtrlShiftI | Alternar herramientas del desarrollador | + +### Repositorios + +| Atajo del teclado | Descripción | +| ------------------------------------------- | ------------------------------------------------------------------------------- | +| CtrlN | Agregar un repositorio nuevo | +| CtrlO | Agregar un repositorio local | +| CtrlShiftO | Clonar un repositorio desde {% data variables.product.prodname_dotcom %} +| CtrlT | Mostrar una lista de tus repositorios | +| CtrlP | Subir las últimas confirmaciones a {% data variables.product.prodname_dotcom %} +| CtrlShiftP | Bajar los últimos cambios de {% data variables.product.prodname_dotcom %} +| CtrlDelete | Eliminar un repositorio existente | +| CtrlShiftG | Ver el repositorio en {% data variables.product.prodname_dotcom %} +| Ctrl` | Abrir el repositorio en tu herramienta de línea de comando preferida | +| CtrlShiftF | Mostrar el repositorio en Explorador | +| CtrlShiftA | Abrir el repositorio en tu herramienta de editor preferida | +| CtrlI | Crear un informe de problemas en {% data variables.product.prodname_dotcom %} + +### Ramas + +| Atajo del teclado | Descripción | +| ------------------------------------------- | ----------------------------------------------------------------------------------------- | +| Ctrl1 | Mostrar todos los cambios antes de confirmar | +| Ctrl2 | Mostrar tu historial de confirmaciones | +| CtrlB | Mostrar todas tus ramas | +| CtrlG | Ir al campo de resumen de confirmaciones | +| CtrlEnter | Confirma los cambios cuando el campo de resumen o de descripción está activo | +| espacio | Selecciona o deselecciona todos los archivos resaltados | +| CtrlShiftN | Crear una rama nueva | +| CtrlShiftR | Renombrar la rama actual | +| CtrlShiftD | Eliminar la rama actual | +| CtrlShiftU | Actualizar desde la rama predeterminada | +| CtrlShiftB | Comparar con una rama existente | +| CtrlShiftM | Fusionar en una rama actual | +| CtrlH | Mostrar u ocultar cambios acumulados | +| CtrlShiftC | Comparar ramas en {% data variables.product.prodname_dotcom %} +| CtrlR | Mostrar la solicitud de extracción actual en {% data variables.product.prodname_dotcom %} + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/launching-github-desktop-from-the-command-line.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/launching-github-desktop-from-the-command-line.md new file mode 100644 index 0000000000000..12bf987743553 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/launching-github-desktop-from-the-command-line.md @@ -0,0 +1,46 @@ +--- +title: Lanzar GitHub Desktop desde la línea de comando +shortTitle: Lanzar desde la línea de comandos +intro: Puedes lanzar GitHub Desktop desde la línea de comando. +redirect_from: + - /desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line +versions: + free-pro-team: '*' +--- + +{% mac %} + +1. En la barra de menú, selecciona el menú de **{% data variables.product.prodname_desktop %}** y luego da clic en **Instalar la Herramienta de Línea de Comandos**. ![Opción para Instalar la Herramienta de Línea de Comandos en el menú desplegable de {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-install-command-line-tool.png) +2. Abre Terminal. +3. {% data reusables.desktop.launch-desktop-from-command-line %} + + ```shell + $ github /path/to/repo + ``` + + También puedes cambiar tu ruta de repositorio y luego teclear `github .` para abrir ese repositorio. + + ```shell + $ cd /path/to/repo + [repo]$ github . + ``` + +{% endmac %} + +{% windows %} + +1. Abre un símbolo del sistema. +2. {% data reusables.desktop.launch-desktop-from-command-line %} + + ```shell + C:\Users\octocat> github path\to\repo + ``` + + También puedes cambiar tu ruta de repositorio y luego teclear `github .` para abrir ese repositorio. + + ```shell + C:\Users\octocat> cd repo\myrepo + C:\Users\octocat\repo\myrepo> github . + ``` + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md new file mode 100644 index 0000000000000..a309a06077e2e --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md @@ -0,0 +1,10 @@ +--- +title: Resumen +intro: Conozca GitHub Desktop y cree rápidamente su primer repositorio. +mapTopic: verdadero +redirect_from: + - /desktop/getting-started-with-github-desktop/overview +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop.md new file mode 100644 index 0000000000000..b3ec93392e30f --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop.md @@ -0,0 +1,24 @@ +--- +title: Establecer un tema para GitHub Desktop +intro: Puedes establecer un tema para personalizar el aspecto de GitHub Desktop. +redirect_from: + - /desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop +versions: + free-pro-team: '*' +--- + +{% mac %} + +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.choose-a-theme %} + ![Las opciones de temas para la pestaña de Apariencia para Mac](/assets/images/help/desktop/mac-appearance-tab-themes.png) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.choose-a-theme %} + ![Las opciones de temas para la pestaña de Apariencia para Windows](/assets/images/help/desktop/windows-appearance-tab-themes.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md new file mode 100644 index 0000000000000..abf0d4fed6dda --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop.md @@ -0,0 +1,43 @@ +--- +title: Configurar GitHub Desktop +shortTitle: Configuración +intro: 'Puedes configurar a {% data variables.product.prodname_desktop %} para que se ajuste a tus necesidades y así contribuir con proyectos.' +redirect_from: + - /desktop/getting-started-with-github-desktop/setting-up-github-desktop +versions: + free-pro-team: '*' +--- + +### Parte 1: Instalar {% data variables.product.prodname_desktop %} + +Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Para obtener más información, consulta la sección "[Sistemas Operativos Compatibles](/desktop/getting-started-with-github-desktop/supported-operating-systems)". + +Para instalar {% data variables.product.prodname_desktop %}, navega a [https://desktop.github.com/](https://desktop.github.com/) y descarga la versión adecuada de {% data variables.product.prodname_desktop %} para tu sistema operativo. Sigue las instrucciones para completar la instalación. Para obtener más información, consulta la sección "[Instalar {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-github-desktop)". + +### Parte 2: Configurar tu cuenta + +Si tienes una cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, puedes utilizar {% data variables.product.prodname_desktop %} para intercambiar datos entre tus repositorios locales y remotos. + +#### Crear una cuenta +Si no tienes una cuenta de {% data variables.product.prodname_dotcom %} aún, consulta la sección "[Registrarte para obtener una cuenta nueva de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account/)". + +Si eres parte de una organización que utiliza {% data variables.product.prodname_enterprise %} y no tienes una cuenta, contacta a tu administrador de sitio de {% data variables.product.prodname_enterprise %}. + +#### Autenticarse en {% data variables.product.prodname_dotcom %} +Para conectase a {% data variables.product.prodname_desktop %} con {% data variables.product.prodname_dotcom %}, necesitarás autenticar tu cuenta. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." + +Después de autenticar tu cuenta, estarás listo para contribuir con y administrar proyectos con {% data variables.product.prodname_desktop %}. + +### Parte 3: Configurar Git +Debes tener instalado Git antes de utilizar {% data variables.product.prodname_desktop %}. Si aún no tienes Git instalado, puedes descargar e instalar la última versión de Git desde [https://git-scm.com/downloads](https://git-scm.com/downloads). + +Después de que instales Git, necesitarás configurarlo para {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar a Git para {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop)". + +### Parte 4: Personalizar {% data variables.product.prodname_desktop %} +Puedes ajustar las características predeterminadas y las configuraciones para ajustar a {% data variables.product.prodname_desktop %} según tus necesidades. + +#### Elegir un editor de texto predeterminado +Puedes abrir un editor de texto desde {% data variables.product.prodname_desktop %} para manipular los archivos y repositorios. {% data variables.product.prodname_desktop %} es compatible con varios editores de textos y ambientes de desarrollo integrados (IDE) para Windows y macOS. Puedes elegir un editor predeterminado en la configuración de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar un editor predeterminado](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)". + +#### Elegir un tema +{% data variables.product.prodname_desktop %} cuenta con varios temas disponibles para personalizar el aspecto y el estilo de la app. Puedes elegir un tema en la configuración de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)". diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/supported-operating-systems.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/supported-operating-systems.md new file mode 100644 index 0000000000000..ff9c6a36ef78c --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/supported-operating-systems.md @@ -0,0 +1,61 @@ +--- +title: Sistemas operativos compatibles +intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} en cualquier sistema operativo compatible.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /desktop/getting-started-with-github-desktop/supported-operating-systems +versions: + free-pro-team: '*' +--- + +### Acerca de los sistemas operativos compatibles + +Estos son los sistemas operativos compatibles para {% data variables.product.prodname_desktop %}. +- {% data variables.desktop.mac-osx-versions %} +- {% data variables.desktop.windows-versions %}. Debes tener un sistema operativo de 64 bits para ejecutar {% data variables.product.prodname_desktop %}. + +### Solución de problemas en macOS +Si te encuentras con algún problema al utilizar {% data variables.product.prodname_desktop %} en macOS, aquí tienes algunas resoluciones que puedes intentar. Para obtener más información, consulta la sección [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md). + +#### El error `The username or passphrase you entered is not correct` se muestra después de iniciar sesión en tu cuenta + +Este error puede ocurrir cuando {% data variables.product.prodname_desktop %} no puede acceder a tus credenciales almacenadas en la cadena de llaves. + +Para solucionar este error, sigue estos pasos. + +1. Abre la app de "Acceso a la cadena de llaves". +2. Da clic derecho en **inicio de sesión** y luego da clic en **Bloquear el "inicio de sesión" de la cadena de llaves**. ![La opción de "Bloquear el "inicio de sesión" en la cadena de llaves](/assets/images/help/desktop/mac-lock-keychain.png) +3. Da clic derecho en **inicio de sesión** y luego da clic en **Desbloquear el "inicio de sesión" de la cadena de llaves**. Sigue las instrucciones en la pantalla para terminar de desbloquear el "inicio de sesión" de la cadena de llaves ![La opción de "Desbloquear el inicio de sesión en la "cadena de llaves"](/assets/images/help/desktop/mac-unlock-keychain.png) +4. Vuelve a autenticarte en tu cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. + +#### El error de `Could not create temporary directory: Permission denied` se muestra después de verificar si hay actualizaciones + +Este error puede estarse causando debido a que no existen los permisos para el directorio `~/Library/Caches/com.github.GitHubClient.ShipIt`. {% data variables.product.prodname_desktop %} utiliza este directorio para crear y desempacar archivos temporales como parte de la actualización de la aplicación. + +Para solucionar este error, sigue estos pasos. + +1. Cierra {% data variables.product.prodname_desktop %}. +2. Abre el "Buscador" y navega hasta `~/Library/Caches/`. +3. Da clic derecho en `com.github.GitHubClient.ShipIt` y luego da clic en **Obtener Información**. +4. Da clic en la flecha a la izquierda de "Compartir & Permisos." +5. Si el privilegio a la derecha de tu cuenta de usuario no dice "Lectura & Escritura", da clic en el texto y luego en **Lectura & Escritura**. ![Las opciones de "Compartir & Permisos"](/assets/images/help/desktop/mac-adjust-permissions.png) +6. Abre {% data variables.product.prodname_desktop %} y verifica si hay actualizaciones. + +### Solución de problemas en Windows +Si te encuentras con algún problema al utilizar {% data variables.product.prodname_desktop %} en Windows, aquí tienes algunas resoluciones que puedes intentar. Para obtener más información, consulta la sección [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md). + +#### Error de `The revocation function was unable to check revocation for the certificate.` + +Este error puede suscitarse si estás utilizando {% data variables.product.prodname_desktop %} en una red corporativa que blqouea a Windows para verificar el estado de revocación de un certificado. + +Para solucionar este problema, contacta al administrador de tu sistema. + +#### Error de `git clone failed` al clonar un repositorio configurado con Redirección de Carpetas + +{% data variables.product.prodname_desktop %} no es compatible con repositorios que se hayan configurado con la Redirección de Carpetas. + +#### Error de `cygheap base mismatch detected` + +Este error se suscita cuando se habilita el ASLR mandatorio. Habilitar el ASLR Mandatorio afecta la librería central de MSYS2, de la cual depende {% data variables.product.prodname_desktop %} para emular la bifurcación de procesos. + +Para solucionar este error, puedes ya sea inhabilitar el ASLR Mandatorio o permitir explícitamente todos los ejecutables bajo `\usr\bin` los cuales dependen en MSYS2. diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/uninstalling-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/uninstalling-github-desktop.md new file mode 100644 index 0000000000000..69982c0ba9e78 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/uninstalling-github-desktop.md @@ -0,0 +1,26 @@ +--- +title: Desinstalar GitHub Desktop +intro: Puedes desinstalar GitHub Desktop de tu computadora en cualquier momento. +redirect_from: + - /desktop/getting-started-with-github-desktop/uninstalling-github-desktop +versions: + free-pro-team: '*' +--- + +{% mac %} + +1. En una ventana de búsqueda, desplázate hasta la carpeta de Aplicaciones. ![Carpeta de aplicaciones en la ventana del Buscador](/assets/images/help/desktop/applications-folder.png) +2. Mientras presionas el botón de **Control** en tu teclado, da clic en **{% data variables.product.prodname_desktop %}**. +3. Elige **Move to Trash** (Mover a Papelera). ![La opción de mover a la papelera](/assets/images/help/desktop/mac-move-to-trash.png) +4. En la barra de menú, utiliza el menú desplegable de **Buscador** y luego da clic en **Vaciar la papelera**. ![La opción de vaciar la papelera en la barra de menú](/assets/images/help/desktop/mac-empty-trash-menu.png) +5. Lee la advertencia en el cuadro emergente y haz clic en **Empty Trash** (Vaciar Papelera). ![El botón de vaciar la papelera](/assets/images/help/desktop/mac-empty-trash-button.png) + +{% endmac %} + +{% windows %} + +1. Aber el panel de control. Para obtener más información, consulta la sección [¿Dónde está el Panel de Control?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) en la ayuda de Windows. +2. Debajo de "Programas", da clic en **Desinstalar un programa**. ![La opción de desinstalar programa en el panel de control](/assets/images/help/desktop/windows-uninstall-a-program.png) +3. Da clic derecho en la entrada que se llama **{% data variables.product.prodname_desktop %}**, y luego da clic en **Desinstalar**. ![La opción de desinstalar](/assets/images/help/desktop/windows-click-uninstall.png) + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/updating-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/updating-github-desktop.md new file mode 100644 index 0000000000000..04ff291397f19 --- /dev/null +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/updating-github-desktop.md @@ -0,0 +1,24 @@ +--- +title: Actualizar GitHub Desktop +intro: GitHub Desktop automáticamente descarga las actualizaciones y las instala al reiniciar. También puedes verificar las actualizaciones manualmente. +redirect_from: + - /desktop/getting-started-with-github-desktop/updating-github-desktop +versions: + free-pro-team: '*' +--- + +{% mac %} + +1. En el menú **GitHub Desktop**, haz clic en **Acerca de GitHub Desktop**. ![Acerca de la opción de menú de GitHub Desktop](/assets/images/help/desktop/desktop-menu-about-desktop-mac.png) +2. Haz clic en **Check for Updates** (Comprobar actualizaciones). ![Botón Check for Updates (Comprobar actualizaciones)](/assets/images/help/desktop/check-for-updates.png) +3. Si hay una actualización disponible, cierre y vuelva a abrir {% data variables.product.prodname_desktop %} para instalar la actualización. + +{% endmac %} + +{% windows %} + +1. En el menú **Help** (Ayuda), haz clic en **Acerca de GitHub Desktop**. ![Acerca de la opción de menú de GitHub Desktop](/assets/images/help/desktop/help-about-desktop-win.png) +2. Haz clic en **Check for Updates** (Comprobar actualizaciones). ![Botón Check for Updates (Comprobar actualizaciones)](/assets/images/help/desktop/check-for-updates.png) +3. Si hay una actualización disponible, cierre y vuelva a abrir {% data variables.product.prodname_desktop %} para instalar la actualización. + +{% endwindows %} diff --git a/translations/es-ES/content/developers/apps/about-apps.md b/translations/es-ES/content/developers/apps/about-apps.md new file mode 100644 index 0000000000000..40c701b9b3a9b --- /dev/null +++ b/translations/es-ES/content/developers/apps/about-apps.md @@ -0,0 +1,101 @@ +--- +title: Acerca de las apps +intro: 'Puedes crear integraciones con las API de {% data variables.product.prodname_dotcom %} para agregar flexibilidad y reducir la fricción en tu propio flujo de trabajo.{% if currentVersion == "free-pro-team@latest" %} También puedes compartir las integraciones con otros en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' +redirect_from: + - /apps/building-integrations/setting-up-a-new-integration/ + - /apps/building-integrations/ + - /apps/getting-started-with-building-apps/ + - /apps/about-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las apps en {% data variables.product.prodname_dotcom %} te permiten automatizar y mejorar tu flujo de trabajo. Puedes crear apps para mejorar tu flujo de trabajo.{% if currentVersion == "free-pro-team@latest" %} También puedes compartir o vender apps en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender sobre cómo listar una app en {% data variables.product.prodname_marketplace %}, consulta la sección "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)".{% endif %} + +{% data reusables.marketplace.github_apps_preferred %}, Pero GitHub es compatible tanto con las {% data variables.product.prodname_oauth_app %} y con {% data variables.product.prodname_github_apps %}. Para obtener más información sobre cómo escoger un tipo de app, consulta las secciónes "[Acerca de las apps](/apps/about-apps/)" y "[Diferencias entre apps](/apps/differences-between-apps/)". + +{% data reusables.apps.general-apps-restrictions %} + +Para obtener una guía detallada del proceso de creación de una {% data variables.product.prodname_github_app %}, consulta la sección "[Crea tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". + +### Acerca de {% data variables.product.prodname_github_apps %} + +Las {% data variables.product.prodname_github_apps %} son actores de primera clase dentro de GitHub. Una {% data variables.product.prodname_github_app %} actúa por si misma, tomando las acciones a través de la API y utilizando directamente su propia identidad, lo que significa que no necesitas mantener un bot o cuenta de servicio como un usuario separado. + +Las {% data variables.product.prodname_github_apps %} se pueden instalar directamente en las cuentas de organización y de usuario, y se les puede dar acceso a repositorios diferentes. Vienen con webhooks integrados y con permisos específicos y delimitados. Cuando configuras tu {% data variables.product.prodname_github_app %}, puedes seleccionar los repositorios a los cuales quieres acceder. Por ejemplo, puedes configurar una app llamada `MyGitHub` que escribe informes de problemas en el repositorio `octocat` y _únicamente_ en dicho repositorio. Para instalar una {% data variables.product.prodname_github_app %}, necesitas ser propietario de la organización o tener permisos administrativos en el repositorio. + +{% data reusables.apps.app_manager_role %} + +Las {% data variables.product.prodname_github_apps %} son aplicaciones que necesitan hospedarse en algún lugar. Para obtener instruciones paso a paso que cubran los temas de servidores y hospedaje, consulta la sección "[Crear tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". + +Para mejorar tu flujo de trabajo, puedes crear una {% data variables.product.prodname_github_app %} que contenga varios scripts, o bien, una aplicación completa, y después conectarla a muchas otras herramientas. Por ejemplo, puedes conectar las {% data variables.product.prodname_github_apps %} a GitHub, Slack, a otras apps locales que tuvieras, programas de correo electrónico, o incluso a otras API. + +Toma estas ideas en consideración cuando crees {% data variables.product.prodname_github_apps %}: + +{% if currentVersion == "free-pro-team@latest" %} +* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %} +* Una {% data variables.product.prodname_github_app %} debe tomar acciones independientemente del usuario (a menos de que dicha app utilice un token de [usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %} + +* Asegúrate de que la {% data variables.product.prodname_github_app %} se integre con repositorios específicos. +* La {% data variables.product.prodname_github_app %} deberá conectarse a una cuenta personal o a una organización. +* No esperes que la {% data variables.product.prodname_github_app %} sepa y haga todo lo que puede hacer un usuario. +* No utilices a la {% data variables.product.prodname_github_app %} si solo necesitas el servicio de "Iniciar sesión en GitHub". Sin embargo, una {% data variables.product.prodname_github_app %} puede utilizar un [flujo de identificación de usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para registrar a los usuarios _y_ para hacer otras cosas. +* No crees una {% data variables.product.prodname_github_app %} si _solo_ quieres fungir como un usuario de GitHub y hacer todo lo que un usuario puede hacer.{% if currentVersion == "free-pro-team@latest" %} +* {% data reusables.apps.general-apps-restrictions %}{% endif %} + +Para comenzar a desarrollar {% data variables.product.prodname_github_apps %}, comienza con la sección "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% if currentVersion == "free-pro-team@latest" %} Para aprender cómo utilizar los manifiestos de las {% data variables.product.prodname_github_app %}, los cuales permiten a las personas crear {% data variables.product.prodname_github_apps %} preconfiguradas, consulta la sección "[Crear una {% data variables.product.prodname_github_apps %} desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %} + +### Acerca de las {% data variables.product.prodname_oauth_app %} + +OAuth2 es un protocolo que permite a las aplicaciones externas el solicitar autorización para usar detalles privados en una cuenta de {% data variables.product.prodname_dotcom %} del usuario sin acceder a su contraseña. Estas son preferentes sobre la Autenticación Básica, ya que los tokens pueden limitarse a ciertos tipos de datos y los usuarios pueden revocarlos en cualquier momento. + +{% data reusables.apps.deletes_ssh_keys %} + +Una {% data variables.product.prodname_oauth_app %} utiliza a {% data variables.product.prodname_dotcom %} como proveedor de identidad para autenticarse como el usuario que otorga el acceso a la app. Esto significa que, cuando un usuario otorga acceso a una {% data variables.product.prodname_oauth_app %}, también otorga permisos a _todos_ los repositorios a los cuales tienen acceso en su cuenta, y también a cualquier organización a la que pertenezcan que no haya bloqueado el acceso de terceros. + +Crear una {% data variables.product.prodname_oauth_app %} es una buena opción si estás creando procesos más complejos de lo que puede manejar un script sencillo. Nota que las {% data variables.product.prodname_oauth_app %} son aplicaciones que necesitan hospedarse en algún lugar. + +Considera estas ideas cuando crees {% data variables.product.prodname_oauth_app %}: + +{% if currentVersion == "free-pro-team@latest" %} +* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} +* Una {% data variables.product.prodname_oauth_app %} siempre debe actuar como el usuario autenticado de {% data variables.product.prodname_dotcom %} a través de todo {% data variables.product.prodname_dotcom %} (por ejemplo, cuando proporciona notificaciones de usuario). +* Una {% data variables.product.prodname_oauth_app %} puede utilizarse como un proveedor de identidad si el usuario autenticado habilita la opción de "Ingresar con {% data variables.product.prodname_dotcom %}". +* No crees una {% data variables.product.prodname_oauth_app %} si quieres que tu aplicación actúe en un solo repositorio. Con el alcance de `repo` de OAuth, Las {% data variables.product.prodname_oauth_app %} podrán actuar en _todos_ los repositorios del usuario autenticado. +* No crees una {% data variables.product.prodname_oauth_app %} para que actúe como una aplicación para tu equipo o compañía. Las {% data variables.product.prodname_oauth_app %}s se autentican como un solo usuario, así que, si una persona crea una {% data variables.product.prodname_oauth_app %} para que la utilice una compañía y luego salen de la compañía, nadie más tendrá acceso a ella.{% if currentVersion == "free-pro-team@latest" %} +* {% data reusables.apps.oauth-apps-restrictions %}{% endif %} + +Para conocer más sobre las {% data variables.product.prodname_oauth_app %}s, consulta las secciones "[Crear una {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" y "[Registrar tu app](/rest/guides/basics-of-authentication#registering-your-app)". + +### Tokens de acceso personal + +Un [token de acceso personal](/articles/creating-a-personal-access-token-for-the-command-line/) es una secuencia de caracteres que funciona de forma similar a un [Token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) en el aspecto de que puedes especificar sus permisos a través de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Un token de acceso personal también es similar a una contraseña, pero puedes tener varios de ellos y puedes revocar el acceso de cada uno en cualquier momento. + +Com ejemplo, puedes habilitar un token de acceso personal para tener acceso de escritura en tus repositorios. Si posteriormente ejecutas un comando de cURL o escribes un script que [cree una propuesta](/rest/reference/issues#create-an-issue) en tu repositorio, tendrías que pasar el token de acceso personal para autenticarte. Puedes almacenar el token de acceso personal como una variable de ambiente para evitar el tener que teclearlo cada vez que lo utilices. + +Considera estas ideas cuando utilices tokens de acceso personal: + +* Recuerda utilizar este token para que te represente únicamente a ti. +* Puedes realizar solicitudes cURL de una sola ocasión. +* Puedes ejecutar scripts personales. +* No configures un script para que lo utilice todo tu equipo o compañía. +* No configures una cuenta de usuario compartida para que actúe como un usuario bot. + +### Determinar qué integración debes crear + +Antes de que comiences a crear integraciones, necesitas determinar la mejor forma de acceder, autenticar, e interactuar con las API de {% data variables.product.prodname_dotcom %}. La siguiente imagen te da algunas pregutnas para hacerte a ti mismo cuando decidas si vas a utilizar tokens de acceso personal, {% data variables.product.prodname_github_apps %}, o {% data variables.product.prodname_oauth_app %} para tu integración. + +![Introducción al flujo de preguntas de apps](/assets/images/intro-to-apps-flow.png) + +Considera estas preguntas acerca de cómo necesita comportarse tu integración y a qué necesita acceder: + +* ¿Mi integración actuará únicamente como yo, o actuará más como una aplicación? +* ¿Quiero que actúe independientemente de mí como su propia entidad? +* ¿Accederá a todo lo que yo puedo acceder, o quiero limitar su acceso? +* ¿Es simple o compleja? Por ejemplo, los tokens de acceso personal sirven bien para scripts simples y cURLs, mientras que una {% data variables.product.prodname_oauth_app %} puede manejar scripts más complejos. + +### Solicitar soporte + +{% data reusables.support.help_resources %} diff --git a/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md b/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md new file mode 100644 index 0000000000000..ba096f63aa7ff --- /dev/null +++ b/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md @@ -0,0 +1,27 @@ +--- +title: Activar las características beta para las apps +intro: 'Puedes probar nuevas características que se lanzan para el beta público para tus {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_app %}s.' +versions: + free-pro-team: '*' +--- + +{% warning %} + +**Advertencia:** Las características disponibles en el beta público están sujetas a cambios. + +{% endwarning %} + +### Activar las características beta para las {% data variables.product.prodname_github_apps %} + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +3. Selecciona la +{% data variables.product.prodname_github_app %} para la cual quieres habilitar la característica beta. +{% data reusables.apps.beta_feature_activation %} + +### Activar las características beta para las {% data variables.product.prodname_oauth_app %}s + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +{% data reusables.apps.beta_feature_activation %} diff --git a/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md b/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md new file mode 100644 index 0000000000000..421d10df69187 --- /dev/null +++ b/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md @@ -0,0 +1,181 @@ +--- +title: Autenticarse con GitHub Apps +intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}' +redirect_from: + - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/ + - /apps/building-github-apps/authentication-options-for-github-apps/ + - /apps/building-github-apps/authenticating-with-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% data reusables.pre-release-program.machine-man-preview %} +{% data reusables.pre-release-program.api-preview-warning %} +{% endif %} + +### Generar una llave privada + +Después de que creas una GitHub App, necesitarás generar una o más llaves privadas. Utilizarás la llave privada para firmar las solicitudes de token de acceso. + +Puedes crear varias llaves privadas y rotarlas para prevenir el tiempo de inactividad si alguna llave se pone en riesgo o se pierde. Para verificar que una llave privada empata con una llave pública, consulta la sección [Verificar llaves privadas](#verifying-private-keys). + +Para generar una llave privada: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +{% data reusables.user-settings.modify_github_app %} +5. En "Llaves privadas", da clic en **Generar una llave privada**. ![Generar llave privada](/assets/images/github-apps/github_apps_generate_private_keys.png) +6. Verás una llave privada en formato PEM que se descarga en tu ordenador. Asegúrate de almacenar este archivo, ya que GitHub solo almacena la porción pública de la llave. + +{% note %} + +**Nota:** Si estás utilizando una biblioteca que requiere de un formato de archivo específico, el archivo PEM que descargues se encontrará en formato `PKCS#1 RSAPrivateKey`. + +{% endnote %} + +### Verificar las llaves privadas +{% data variables.product.product_name %} genera una huella digital para cada par de llaves pública y privada utilizando la función de hash {% if currentVersion ver_lt "enterprise-server@2.23" %}SHA-1{% else %}SHA-256{% endif %}. Puedes verificar que tu llave privada empate con la llave pública almacenada en {% data variables.product.product_name %} generando la huella digital de tu llave privada y comparándola con la huella digital que se muestra en {% data variables.product.product_name %}. + +Para verificar una llave privada: + +1. Encuentra la huella digital del par de llaves pública y privada que quieras verificar en la sección "Llaves privadas" de tu página de configuración de desarrollador de {% data variables.product.prodname_github_app %}. Para obtener más información, consulta la sección [Generar una llave privada](#generating-a-private-key). ![Huella digital de llave privada](/assets/images/github-apps/github_apps_private_key_fingerprint.png) +2. Genera la huella digital de tu llave privada (PEM) localmente utilizando el siguiente comando: + ```shell + $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl {% if currentVersion ver_lt "enterprise-server@2.23" %}sha1 -c{% else %}sha256 -binary | openssl base64{% endif %} + ``` +3. Compara los resultados de la huella digital generada localmente con aquella que ves en {% data variables.product.product_name %}. + +### Borra las llaves privadas +Puedes eliminar una llave privada que se haya perdido o puesto en riesgo si la borras, pero debes de tener por lo menos una llave privada. Cuando solo tienes una llave, necesitas generar una nueva antes de borrar la anterior. ![Borrar la última llave privada](/assets/images/github-apps/github_apps_delete_key.png) + +### Autenticarse como una {% data variables.product.prodname_github_app %} + +El autenticarte como una {% data variables.product.prodname_github_app %} te permite hacer un par de cosas: + +* Puedes recuperar información administrativa de alto nivel acerca de tu {% data variables.product.prodname_github_app %}. +* Puedes solicitar tokens de acceso para una instalación de la app. + +Para autenticarte como una {% data variables.product.prodname_github_app %}, [genera una llave privada](#generating-a-private-key) en formato PEM y descárgala a tu máquina local. Utilizarás esta llave para firmar un [Token Web (JWT) de JSON](https://jwt.io/introduction) y cifrarlo utilizando el algoritmo `RS256`. {% data variables.product.product_name %} revisa que la solicitud se autentique verificando el token con la llave pública almacenada de la app. + +Aquí se muestra rápidamente un script de Ruby que puedes utilizar para generar un JWT. Nota que tendrás que ejecutar `gem install jwt` antes de utilizarlo. + + + +```ruby +require 'openssl' +require 'jwt' # https://rubygems.org/gems/jwt + +# Private key contents +private_pem = File.read(YOUR_PATH_TO_PEM) +private_key = OpenSSL::PKey::RSA.new(private_pem) + +# Generate the JWT +payload = { + # issued at time + iat: Time.now.to_i, + # JWT expiration time (10 minute maximum) + exp: Time.now.to_i + (10 * 60), + # {% data variables.product.prodname_github_app %}'s identifier + iss: YOUR_APP_ID +} + +jwt = JWT.encode(payload, private_key, "RS256") +puts jwt +``` + +`YOUR_PATH_TO_PEM` y `YOUR_APP_ID` son los valores que debes reemplazar. + +Utiliza tu identificador de {% data variables.product.prodname_github_app %} (`YOUR_APP_ID`) como el valor para la solicitud del [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emisor) del JWT. Puedes obtener el identificador de {% data variables.product.prodname_github_app %} a través del ping del webhook inicial después de [crear la app](/apps/building-github-apps/creating-a-github-app/), o en cualquier momento desde la página de configuración de la app en la UI de GitHub.com. + +Después de crear el JWT, configura el `Header` de la solicitud de la API: + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +```shell +$ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.machine-man-preview+json" {% data variables.product.api_url_pre %}/app +``` +{% else %} +```shell +$ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app +``` +{% endif %} + +`YOUR_JWT` es el valor que debes reemplazar. + +El ejemplo anterior utiliza el tiempo de caducidad máximo de 10 minutos, después del cual, la API comenzará a devolver el error `401`: + +```json +{ + "message": "'Expiration' claim ('exp') must be a numeric value representing the future time at which the assertion expires.", + "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +} +``` + +Necesitarás crear un nuevo JWT después de que el tiempo caduque. + +### Acceder a terminales de API como una {% data variables.product.prodname_github_app %} + +Para obtener una lista de las terminales de API de REST que puedes utilizar para obtener información de alto nivel acerca de una {% data variables.product.prodname_github_app %}, consulta la sección "[GitHub Apps](/rest/reference/apps)". + +### Autenticarse como una instalación + +El autenticarte como una instalación te permite realizar acciones en la API para dicha instalación. Antes de autenticarte como una instalación, debes crear un token de acceso a ésta. Las {% data variables.product.prodname_github_app %} utilizan estos tokes de acceso a la instalación para autenticarse. + +Predeterimenadamente, los tokens de acceso de instalación tienen un alcance de todos los repositorios a los cuales tiene acceso dicha instalación. Puedes limitar el alcance del token de acceso de la instalación a repositorios específicos si utilizas el parámetro `repository_ids`. Consulta la terminal [Crear un token de acceso de instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app) para encontrar más detalles. Los tokens de acceso de instalación cuentan con permisos configurados por la {% data variables.product.prodname_github_app %} y caducan después de una hora. + +Para crear un token de acceso de instalación, incluye el JWT [previamente generado](#jwt-payload) en el encabezado de autorización en la solicitud de la API: + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +```shell +$ curl -i -X POST \ +-H "Authorization: Bearer YOUR_JWT" \ +-H "Accept: application/vnd.github.machine-man-preview+json" \ +{% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens +``` +{% else %} +```shell +$ curl -i -X POST \ +-H "Authorization: Bearer YOUR_JWT" \ +-H "Accept: application/vnd.github.v3+json" \ +{% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens +``` +{% endif %} + +La respuesta incluirá tu token de acceso de instalación, la fecha de caducidad, los permisos del token, y los repositorios a los cuales tiene acceso. Para obtener más información acerca del formato de respuesta, consulta la terminal [Crear un token de acceso de instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app). + +Para autenticarte con un token de acceso de instalación, inclúyela en el encabezado de Autorización en la solicitud de la API: + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +```shell +$ curl -i \ +-H "Authorization: token YOUR_INSTALLATION_ACCESS_TOKEN" \ +-H "Accept: application/vnd.github.machine-man-preview+json" \ +{% data variables.product.api_url_pre %}/installation/repositories +``` +{% else %} +```shell +$ curl -i \ +-H "Authorization: token YOUR_INSTALLATION_ACCESS_TOKEN" \ +-H "Accept: application/vnd.github.v3+json" \ +{% data variables.product.api_url_pre %}/installation/repositories +``` +{% endif %} + +`YOUR_INSTALLATION_ACCESS_TOKEN` es el valor que debes reemplazar. + +### Acceder a las terminales de la API como una instalación + +Para encontrar un listado de las terminales de la API de REST disponibles para utilizarse con {% data variables.product.prodname_github_app %} utilizando un token de acceso de instalación, consulta la sección "[Terminales Disponibles](/rest/overview/endpoints-available-for-github-apps)". + +Para encontrar un listad de terminales relacionado con las instalaciones, consulta la sección "[Instalaciones](/rest/reference/apps#installations)". + +### Acceso a Git basado en HTTP mediante una instalación + +Las instalaciones con [permisos](/apps/building-github-apps/setting-permissions-for-github-apps/) en los `contents` de un repositorio pueden utilizar su token de acceso de instalación para autenticarse para acceso a Git. Utiliza el token de acceso de instalación como la contraseña HTTP: + +```shell +git clone https://x-access-token:<token>@github.com/owner/repo.git +``` diff --git a/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md new file mode 100644 index 0000000000000..01776be235930 --- /dev/null +++ b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md @@ -0,0 +1,304 @@ +--- +title: Autorizar aplicaciones OAuth +intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' +redirect_from: + - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps/ + - /v3/oauth/ + - /apps/building-oauth-apps/authorization-options-for-oauth-apps/ + - /apps/building-oauth-apps/authorizing-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La implementación de OAuth de {% data variables.product.product_name %} es compatible con el [tipo de otorgamiento de código de autorización](https://tools.ietf.org/html/rfc6749#section-4.1) estándar{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} y con el [Otorgamiento de autorización de dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0 para las aplicaciones que no tienen acceso a un buscador web{% endif %}. + +Si quieres saltar el proceso de autorización de tu app en el modo estándar, tal como sucede cuando la estás probando, puedes utilizar el [flujo no web para aplicaciones](#non-web-application-flow). + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} + +Para autorizar tu app de OAuth, considera qué flujo de autorizaciones queda mejor con ella. + +- [flujo web de aplicaciones](#web-application-flow): Se utiliza para autorizar a los usuarios para las aplicaciones de OAuth que se ejecutan en el buscador. (El [tipo de concesión implícito](https://tools.ietf.org/html/rfc6749#section-4.2) no es compatible) +- [flujo de dispositivos](#device-flow): Se utiliza para las apps sin encabezado, tales como las herramientas de CLI. + +{% else %} + +Para las apps estándar que se ejecutan en el buscador, utiliza el [flujo web de aplicaciones](#web-application-flow) para obtener un código de autorización e intercambiarlo por un token. (El [tipo de concesión implícito](https://tools.ietf.org/html/rfc6749#section-4.2) no es compatible) + +{% endif %} + +### Flujo de aplicaciones Web + +{% note %} + +**Nota:** Si estás creando una GitHub App, aún puedes utilizar el flujo de aplicaciones web de OAuth, pero la configuración tiene diferencias importantes. Consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obtener más información. + +{% endnote %} + +El flujo web de aplicaciones para autorizar a los usuarios en tu app es: + +1. Se redirecciona a los usuarios para solicitar su identidad de GitHub +2. GitHub redirecciona a los usuarios de vuelta a tu sitio +3. Tu aplicación accede a la API con el token de acceso del usuario + +#### 1. Solicita la identidad de un usuario de GitHub + + GET {% data variables.product.oauth_host_code %}/login/oauth/authorize + +Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuarios con una cuenta específica que pueden utilizar para registrarse y autorizar tu app. + +##### Parámetros + +| Nombre | Type | Descripción | +| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido**. La ID de ciente que recibiste de GitHub cuando te {% if currentVersion == "free-pro-team@latest" %}[registraste](https://github.com/settings/applications/new){% else %}registraste{% endif %}. | +| `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Consulta los siguientes detalles sobre [urls de redireccionamiento](#redirect-urls). | +| `login` | `secuencia` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app. | +| `scope` | `secuencia` | Una lista de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada en espacio. De no proporcionarse, el `scope` será, predeterminadamente, una lista vacía para los usuarios que no han autorizado ningún alcance para la aplicación. Para los usuarios que han autorizado alcances para la aplicación, el usuario no se mostrará en la página de autorización de OAuth con la lista de alcances. En vez de esto, este paso del flujo se completara automáticamente con el conjunto de alcances que el usuario haya autorizado para la aplicación. Por ejemplo, si un usuario ya realizó el flujo web dos veces y autorizó un token con alcance de `user` y otro con alcance de `repo`, un tercer flujo web que no proporcione un `scope` recibirá un token con los alcances `user` y `repo`. | +| `state` | `secuencia` | {% data reusables.apps.state_description %} +| `allow_signup` | `secuencia` | Ya sea que se ofrezca o no una opción para registrarse en GitHub a los usuarios sin autenticar durante el flujo de OAuth, la opción predeterminada es `true`. Utiliza `false` cuando una política prohíba los registros. | + +#### 2. GitHub redirecciona a los usuarios de vuelta a tu sitio + +Si el usuario acepta tu solicitud, {% data variables.product.product_name %} lo redirecciona a tu sitio con un `code` temporal en un parámetro de código así como el estado que proporcionaste en el paso previo en un parámetro de `state`. El código temporal caducará después de 10 minutos. Si los estados no empatan, entonces un tercero creó la solicitud, y debes abandonar el proceso. + +Intercambia este `code` por un token de acceso: + + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token + +##### Parámetros + +| Nombre | Type | Descripción | +| --------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | +| `code` | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1. | +| `redirect_uri` | `secuencia` | La URL en tu aplicación, hacia la cual se envía a los usuarios después de su autorización. | +| `state` | `secuencia` | La secuencia aleatoria indescifrable que proporcionaste en el Paso 1. | + +##### Respuesta + +Predeterminadamente, la respuesta toma la siguiente forma: + + access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + +También puedes recibir el contenido en diferentes formatos, dependiendo del encabezado de aceptación: + + Accept: application/json + {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + + Accept: application/xml + + bearer + repo,gist + e72e16c7e42f292c6912e7710c838347ae178b4a + + +#### 3. Utiliza el token de acceso para acceder a la API + +El token de acceso te permite hacer solicitudes a la API a nombre de un usuario. + + Authorization: token OAUTH-TOKEN + GET {% data variables.product.api_url_code %}/user + +Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera: + +```shell +curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user +``` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +### Flujo de dispositivos + +{% if currentVersion ver_lt "enterprise-server@3.1" %} +{% note %} + +**Nota:** El flujo de dispositivos se encuentra en un beta público y está sujeto a cambios. + +{% endnote %} +{% endif %} + +Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git. + +#### Resumen del flujo de dispositivos + +1. Tu app solicita el dispositivo y los códigos de verificación de usuario y obtiene una URL de autoización en donde el usuario ignresará su código de verificación de usuario. +2. La app pide al usuario ingresar un código de verificación de usuario en {% data variables.product.device_authorization_url %}. +3. La app sondea el estado de autenticación del usuario. Una vez que el usuario haya autorizado el dispositivo, la app podrá hacer llamadas a la API con un token de acceso nuevo. + +#### Paso 1: La app solicita los códigos de dispositivo y de usuario a GitHub + + POST {% data variables.product.oauth_host_code %}/login/device/code + +Tu app debe solicitar un código de verificación de usuario y una URL de verificación que la app utilizará para indicar al usuario que se autentique en el siguiente paso. Esta solicitud también devuelve un código de verificación de dispositivo que debe utilizar la app para recibir un token de acceso y verificar así el estado de la autenticación del usuario. + +##### Parámetros de entrada + +| Nombre | Type | Descripción | +| ----------- | ----------- | ------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu app. | +| `scope` | `secuencia` | El alcance al cual está solicitando acceso tu app. | + +##### Respuesta + +{% if currentVersion == "free-pro-team@latest" %} + ```JSON + { + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "https://github.com/login/device", + "expires_in": 900, + "interval": 5 + } + ``` +{% else %} + ```JSON + { + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "http(s)://[hostname]/login/device", + "expires_in": 900, + "interval": 5 + } + ``` +{% endif %} + +##### Parámetros de respuesta + +| Nombre | Type | Descripción | +| ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `device_code` | `secuencia` | El código de verificación de dispositivo es de 40 caracteres y se utiliza para verificar dicho dispositivo. | +| `user_code` | `secuencia` | El código de verificación de usuario se muestra en el dispositivo para que el usuario pueda ingresar dicho código en un buscador. El código es de 8 caracteres con un guión medio a la mitad. | +| `verification_uri` | `secuencia` | La URL de verificación en donde los usuarios necesitan ingresar el `user_code`: {% data variables.product.device_authorization_url %}. | +| `expires_in` | `número` | La cantidad de segundos antes de que caduquen tanto el `device_code` como el `user_code`. La cantidad predeterminada es de 900 segundos o 15 minutos. | +| `interval` | `número` | La cantidad mínima de segundos que deben transcurrir antes de que puedas hacer una soliciud de token de acceso nueva (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para completar la autorización del dispositivo. Por ejemplo, si el intervalo es 5, entonces no puedes hacer una solicitud nueva hasta que hayan transcurrido 5 segudos. Si haces más de una solicitud en estos 5 segundos, entonces lelgarás al límite de tasa y recibirás un error de `slow_down`. | + +#### Paso 2: Indicar al usuario ingresar el código de usuario en un buscador + +Tu dispositivo mostrará el código de verificación de usuario y pedirá al usuario ingresar el código en la {% data variables.product.device_authorization_url %}. + + ![Campo para ingresar el código de verificación de usuario nuevo en tu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png) + +#### Paso 3: La app sondea GitHub para verificar si el usuario autorizó el dispositivo + + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token + +Tu app hará solicitudes de autorización de dispositivo que sondean a `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, hasta que los códigos de dispositivo y de usuario caduquen o hasta que el usuario haya autorizado la app con éxito con un código de usuario válido. La app debe usar el `interval` de sondeo mínimo que se ha recuperado en el paso 1 para evitar los errores de límite de tasa. Para obtener más información, consulta la sección "[Límites de tasa para el flujo del dispositivo](#rate-limits-for-the-device-flow)". + +El usuario debe ingresar un código válido dentro de los 15 minutos (o 900 segundos) siguientes. Después de transcurridos estos 15 minutos, necesitarás solicitar un código de autorización de dispositivo nuevo con `POST {% data variables.product.oauth_host_code %}/login/device/code`. + +Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se puede utilizar para hacer solicitudes a la API en nombre de un usuario. + +##### Parámetros de entrada + +| Nombre | Type | Descripción | +| ------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | +| `device_code` | `secuencia` | **Requerido.** El código de verificación del dispositivo que recibiste de la solicitud de `POST {% data variables.product.oauth_host_code %}/login/device/code`. | +| `grant_type` | `secuencia` | **Requerido.** El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code`. | + +##### Respuesta + +```json +{ + "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "token_type": "bearer", + "scope": "user" +} +``` + +#### Límites de tasa para el flujo del dispositivo + +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. + +Si realizas más de una solicitud de acceso con token (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) dentro del marco de tiempo mínimo requerido entre solicitudes (o `interval`), alcanzarás el límite de tasa y recibirás una respuesta de error de `slow_down`. La respuesta de error `slow_down` agrega 5 segundos al último `interval`. Para obtener más información, consulta los [Errores para el flujo del dispositivo](#errors-for-the-device-flow). + +#### Códigos de error para el flujo del dispositivo + +| Código de error | Descripción | +| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `authorization_pending` | Este error ocurre cuando la solicitud de autorización se encuentra pendiente y el usuario no ha ingresado el código de usuario aún. Se espera que la app siga sondeando la solicitud de `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` sin exceder el [`interval`](#response-parameters), lo cual requiere una cantidad mínima de segundos entre cada solicitud. | +| `slow_down` | Cuando recibes el error de `slow_down`, se agregan 5 segundos extra al `interval` mínimo o al marco de tiempo requerido entre tus solicitudes utilizando `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. Por ejemplo, si el intervalo de inicio requirió por lo menos 5 segundos entre solicitudes y obtienes una respuesta de error de `slow_down`, ahora necesitarás esperar por lo menos 10 segundos antes de que hagas una solicitud nueva para un token de acceso de OAuth. La respuesta de error incluye el nuevo `interval` que debes utilizar. | +| `expired_token` | Si el código de dispositivo expiró, entonces verás el error `token_expired`. Debes hacer una nueva solicitud para un código de dispositivo. | +| `unsupported_grant_type` | El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code` y se debe incluir como un parámetro de entrada cuando sondeas la solicitud de token de OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. | +| `incorrect_client_credentials` | Para el flujo de dispositivos, debes pasar la ID de cliente de tu app, la cual puedes encontrar en la página de configuración de la misma. No se necesita el `client_secret` para el flujo del dispositivo. | +| `incorrect_device_code` | El device_code que se proporcionó es inválido. | +| `access_denied` | Cuando un usuario da clic en cancelar durante el proceso de autorización, recibirás un error de `access_denied` y el usuario no podrá utilizar el código de verificación nuevamente. | + +Para obtener más información, consulta la sección "[Otorgamiento de Autorización de Dispositivo de OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)". + +{% endif %} + +### Flujo de aplicaciónes no web + +La autenticación no web está disponible para situaciones limitadas, como las pruebas. Si lo necesitas, puedes utilizar la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) para crear un token de acceso personal utilizando tu [página de configuración de los tokens de acceso personal](/articles/creating-an-access-token-for-command-line-use). Esta técnica le permite al usuario revocar el acceso en cualquier momento. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +{% note %} + +**Nota:** CUando utilices el flujo de aplicaciones no web para crear un token OAuth2, asegúrate de entender cómo [trabajar con autenticaciones de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) si tú o tus usuarios han habilitado dicho tipo de autenticación. + +{% endnote %} +{% endif %} + +### URLs de Redirección + +El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionará a los usuarios a la URL de rellamado configurada en la aplicación de OAuth. De proporcionarse, el puerto y host de las URL de rellamado deberán empatar exactamente con la URL de rellamado. La ruta de las URL de redireccionamiento deberán referenciar un subdirectorio de la URL de rellamado. + + CALLBACK: http://example.com/path + + GOOD: http://example.com/path + GOOD: http://example.com/path/subdir/other + BAD: http://example.com/bar + BAD: http://example.com/ + BAD: http://example.com:8080/path + BAD: http://oauth.example.com:8080/path + BAD: http://example.org + +#### URLs de redirección de Localhost + +El parámetro opcional `redirect_uri` también puede utilizarse para las URL de localhost. Si la aplicación especifica una URL y puerto de localhost, entonces, después de autorizar la aplicación, los usuarios se redireccionarán al puerto y URL proporcionados. La `redirect_uri` no necesita empatar con el puerto especificado en la url de rellamado para la app. + +Para la URL de rellamado de `http://localhost/path`, puedes utilizar esta `redirect_uri`: + +``` +http://localhost:1234/path +``` + +### Crear tokens múltiples para Apps de OAuth + +Puedes crear tokens múltiples para una combinación de usuario/aplicación/alcance para crear tokens para casos de uso específicos. + +Esto es útil si tu Aplicación de OAuth es compatible con un flujo de trabajo que utilice GitHub para registrarse y requiera solo información básica del usuario. Otro flujo de trabajo podría requerir acceso a los repositorios privados del usuario. Al utilizar tokens múltiples, tu App de OAuth podrá llevar a cabo el flujo web para cada caso de uso, solicitando únicamente los alcances que necesite. Si un usuario utiliza tu aplicación únicamente para registrarse, nunca se les solicitará otorgar acceso a tu App de OAuth para sus repositorios privados. + +Hay un límite en la cantidad de tokens que se emiten por combinación de usuario/aplicación/alcance. Si tu aplicación solicita suficientes tokens para sobrepasar uno de los límites, los tokens anteriores _con el mismo alcance que se está solicitando_ dejarán de funcionar. + +{% data reusables.apps.deletes_ssh_keys %} + +### Dirigir a los usuarios para revisar su acceso + +Puedes vincular a la información de autorización para una App de OAuth para que los usuarios puedan revisar y revocar sus autorizaciones de la aplicación. + +Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el cual recibiste de GitHub cuando registraste la aplicación. + +``` +{% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id +``` + +{% tip %} + +**Tip:** Para aprender más acerca de los recursos a los cuales puede acceder tu App de OAuth para un usuario, consulta la sección "[Descubrir recursos para un usuario](/rest/guides/discovering-resources-for-a-user)". + +{% endtip %} + +### Solución de problemas + +* "[Solución de problemas para errores de solicitud de autorización](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Solución de problemas para errores de solicitud de tokens de acceso para Apps de OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +* "[Errores de flujo de dispositivo](#errors-for-the-device-flow)" +{% endif %} diff --git a/translations/es-ES/content/developers/apps/building-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps.md new file mode 100644 index 0000000000000..cdbbc6cc28ea3 --- /dev/null +++ b/translations/es-ES/content/developers/apps/building-github-apps.md @@ -0,0 +1,13 @@ +--- +title: Crear GitHub Apps +intro: Puedes crear GitHub Apps para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para GitHub Apps. +mapTopic: verdadero +redirect_from: + - /apps/building-integrations/setting-up-and-registering-github-apps/ + - /apps/building-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps.md new file mode 100644 index 0000000000000..a76fe5f07b6bc --- /dev/null +++ b/translations/es-ES/content/developers/apps/building-oauth-apps.md @@ -0,0 +1,13 @@ +--- +title: Crear Apps de OAuth +intro: Puedes crear Apps de OAuth para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para Apps de OAuth. +mapTopic: verdadero +redirect_from: + - /apps/building-integrations/setting-up-and-registering-oauth-apps/ + - /apps/building-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-github-app.md b/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-github-app.md new file mode 100644 index 0000000000000..87ccf41f4f20d --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-github-app.md @@ -0,0 +1,42 @@ +--- +title: Crear una insignia personalizada para tu GitHub App +intro: '{% data reusables.shortdesc.creating_custom_badges_github_apps %}' +redirect_from: + - /apps/building-github-apps/creating-custom-badges-for-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Predeterminadamente, una GitHUb App tendrá un [identicon](https://github.com/blog/1586-identicons) generado automáticamente. Una insignia de identicon se ve más o menos así: + +![Identicon](/assets/images/identicon.png) + +Después de crear una GitHub App, puedes personalizar la insignia de tu app si subes un logo y seleccionas un color de fondo. Una insignia es una imagen de logo cuadrado dentro de una insignia circular. Puedes escoger un color de fondo para la insignia, el cual puede distinguir visualmente a tu app. + +Tu logo debe ser un archivo en PNG, JPG, o GIF de menos de 1 MB de tamaño. Para obtener la mejor calidad, te recomendamos un tamaño de por lo menos 200px x 200px. {% if currentVersion == "free-pro-team@latest" %}Consulta la sección "[Tips para las imagenes de logo y de insignia](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" para obtener más orientación sobre la personalización de insignias.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Puedes cambiar una insignia personalizada para una GitHub App que ya tenga una lista de Marketplace aprobada si navegas a https://github.com/marketplace/manage. + +{% endif %} + +Para crear una insignia personalizada: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +{% data reusables.user-settings.modify_github_app %} +5. En "Mostrar información", arrastra y suelta una imagen de una carpeta local, o da clic en **Cargar un logo** para seleccionar una imagen de tu ordenador. ![Cargar un logo](/assets/images/github-apps/github_apps_upload_logo.png) +6. Recorta tu imagen. Cuando termines, da clic en **Confirmar avatar nuevo**. ![Cortar y confirmar logo ](/assets/images/github-apps/github_apps_crop_and_set_avatar.png) +7. En "Color de fondo de la insignia", teclea el [código hexadecimal de color](http://www.color-hex.com/) para el color de fondo de tu insignia. {% if currentVersion == "free-pro-team@latest" %}**Nota:** El campo de entrada de "Color de fondo de la Insignia" solo aparecerá después de que cargues un logo de la aplicación.{% endif %} ![Color de fondo de la insignia](/assets/images/github-apps/github_apps_badge_background_color.png) + +{% if currentVersion == "free-pro-team@latest" %} + +### Pasos siguientes + +Para obtener más información acerca de cómo crear un listado de Marketplace para esta app, consulta la sección "[Listados en GitHub Marketplace](/marketplace/listing-on-github-marketplace/)". + +{% endif %} diff --git a/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md b/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md new file mode 100644 index 0000000000000..faf9558bfcdb3 --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-a-custom-badge-for-your-oauth-app.md @@ -0,0 +1,45 @@ +--- +title: Crear una insignia personalizada para tu App de OAuth +intro: '{% data reusables.shortdesc.creating_custom_badges_oauth_apps %}' +redirect_from: + - /apps/building-oauth-apps/creating-custom-badges-for-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Predeterminadamente, una App de OAuth nueva tendrá un [identicon](https://github.com/blog/1586-identicons) que se genera automáticamente. Una insignia de identicon se ve más o menos así: + +![Identicon](/assets/images/identicon.png) + +Después de que crees una App de OAuth, podrás personalizar la insignia de la misma si cargas un logo y seleccionas un color de fondo. Una insignia es una imagen de logo cuadrado dentro de una insignia circular. Puedes elegir un color de fondo para la insignia, la cual puede utilizarse para distinguir a tu app visualmente. + +Tu logo debe ser un archivo en PNG, JPG, o GIF de menos de 1 MB de tamaño. Para obtener la mejor calidad, te recomendamos un tamaño de por lo menos 200px x 200px. {% if currentVersion == "free-pro-team@latest" %}Consulta la sección "[Tips para las imagenes de logo y de insignia](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" para obtener más orientación sobre la personalización de insignias.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Puedes cambiar una insignia personalizada para una GitHub App que ya tenga una lista de Marketplace aprobada si navegas a https://github.com/marketplace/manage. + +{% endif %} + +Para crear una insignia personalizada: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +{% data reusables.user-settings.modify_oauth_app %} +1. En la zona de "Logo de la aplicación", arrastra y suelta una imagen de alguna carpeta local, o da clic en **Cargar logo nuevo** para seleccionar una imagen de tu ordenador. ![Cargar un logo](/assets/images/oauth-apps/oauth_apps_upload_logo.png) +6. Recorta tu imagen. Cuando hayas terminado, da clic en **Configurar nuevo logo de la aplicación**. ![Cortar y confirmar logo](/assets/images/oauth-apps/oauth_apps_crop_and_set_logo.png) +7. En "Color de fondo de la insignia", teclea el [código hexadecimal de color](http://www.color-hex.com/) para el color de fondo de tu insignia. +{% if currentVersion == "free-pro-team@latest" %}**Nota:** El campo de entrada de "Color de fondo de la Insignia" estará visible después de que el logo de una aplicación se actualice.{% endif %} +![Color de fondo de la insignia](/assets/images/oauth-apps/oauth_apps_badge_background_color.png) +{% data reusables.user-settings.update_oauth_app %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Pasos siguientes + +Para obtener más información acerca de cómo crear un listado de Marketplace para esta app, consulta la sección "[Listados en GitHub Marketplace](/marketplace/listing-on-github-marketplace/)". + +{% endif %} diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md new file mode 100644 index 0000000000000..153ab8defd741 --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -0,0 +1,194 @@ +--- +title: Crear una GitHub App a partir de un manifiesto +intro: 'Un Manifiesto de una GitHub App es una GitHub App preconfigurada que puedes compartir con cualquiera que desée utilizar tu app en sus repositorios personales. El flujo del manifiesto les permite a los usuarios crear, instalar y comenzar a extender una GitHub App rápidamente sin necesidad de registrarla o de conectar el registro al código hospedado de la app.' +redirect_from: + - /apps/building-github-apps/creating-github-apps-from-a-manifest +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Acerca de los Manifiestos de las GitHub Apps + +Cuando alguien crea una GitHub App desde un manifiesto, únicamente necesitan seguir una URL y nombrar a la app. El manifiesto incluye los permisos, eventos, y URL de los webhooks que se necesiten para registrar la app automáticamente. El flujo del manifiesto crea el registro de la GitHub App y recupera el secreto del webhook, llave privada (archivo PEM), e ID de la GitHub App. Quien sea que cree la app desde el manifiesto será el propietario de la misma y podrá elegir [editar los ajustes de la configuración de seguridad de la app](/apps/managing-github-apps/modifying-a-github-app/), eliminarlos, o transferirlos a otra persona en GitHub. + +Puedes utilizar al [Probot](https://probot.github.io/) para comenzar a utilizar los Manifiestos de las GitHub Apps o ver un ejemplo de implementación. Consulta la sección "[Utilizar al Probot para implementar el flujo del Manifiesto de las GitHub Apps](#using-probot-to-implement-the-github-app-manifest-flow)" para obtener más información. + +Aquí te mostramos algunos escenarios en donde podrías utilizar los Manifiestos de las GitHub Apps para crear apps preconfiguradas: + +* Para ayudar a los miembros nuevos del equipo a que se familiaricen rápidamente con el desarrollo de las GitHub Apps. +* Para permitir que otros extiendan una GitHub App utilizando las API de GitHub sin que necesiten configurar dicha app. +* Para crear diseños de referencia de GitHub Apps y compartirlos con la comunidad de GitHub. +* Para garantizar que despliegas GitHub Apps en los ambientes de desarrollo y de producción utilizando la misma configuración. +* Para rastrear las revisiones hechas en la configuración de una GitHub App. + +### Implementar el flujo del Manifiesto de una GitHub App + +El flujo del Manifiesto de una GitHub App utiliza un proceso de intercambio similar al del [flujo de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). El flujo utiliza un manifiesto para [registrar una GitHub App](/apps/building-github-apps/creating-a-github-app/) y recibe un `code` temporal que se utiliza para recuperar la llave privada, webhoo, secreto, e ID de la misma. + +{% note %} + +**Nota:** Tienes solo una hora para completar los tres pasos del flujo del Manifiesto de la GitHub App. + +{% endnote %} + +Sigue estos pasos par aimplementar el flujo del Manifiesto de la GitHub App: + +1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva. +1. GitHub redirige a las personas de vuelta a tu sitio. +1. Intercambias el código temporal para recuperar la configuración de la app. + +#### 1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva + +Para redireccionar a las personas a crear una GitHub App nueva, [proporciona un enlace](#examples) para que ellos den clic y envíen una solicitud de `POST` a `https://github.com/settings/apps/new` para una cuenta de usuario o a `https://github.com/organizations/ORGANIZATION/settings/apps/new` para una cuenta de organización, reemplazando `ORGANIZATION` con el nombre de la cuenta de organización en donde se creará la app. + +Debes incluir los [Parámetros del Manifiesto de la GitHub App](#github-app-manifest-parameters) como una secuencia cifrada con JSON en un parámetro que se llame `manifest`. También puedes incluir un [parámetro](#parameters) de `state` para agregar seguridad adicional. + +Se redirigirá al creador de la app a una página de GitHub en donde encontrará un campo de entrada y ahí podrá editar el nombre de la app que incluiste en el parámetro de `manifest`. Si no incluyes un `name` en el `manifest`, podrán configurar un nombre de su elección para la app en este campo. + +![Crear un Manifiesto de una GitHub App](/assets/images/github-apps/create-github-app-manifest.png) + +##### Parámetros del Manifiesto de la GitHub App + + | Nombre | Type | Descripción | + | --------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name (nombre)` | `secuencia` | El nombre dela GitHub App. | + | `url` | `secuencia` | **Requerido.** La página principal de tu GitHub App. | + | `hook_attributes` | `object` | La configuración del webhook de la GitHub App. | + | `redirect_url` | `secuencia` | La URL completa a la cual se redireccionará a la persona después de que instale la GitHub App. | + | `description` | `secuencia` | Una descripción de la GitHub App. | + | `public` | `boolean` | Configúralo como `true` cuando tu GitHub App esté disponible al público o como `false` si solo puede acceder el propietario de la misma. | + | `default_events` | `arreglo` | La lista de [eventos](/webhooks/event-payloads) a la cual se suscribe la GitHub App. | + | `default_permissions` | `object` | El conjunto de [permisos](/rest/reference/permissions-required-for-github-apps) que requiere la GitHub App. El formato del objeto utiliza el nombre del permiso para la clave (por ejemplo, `issues`) y el tipo de acceso para el valor (por ejemplo, `write`). | + +El objeto `hook_attributes` tiene la siguiente clave: + +| Nombre | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------------------------------------- | +| `url` | `secuencia` | **Requerido.** La URL del servidor que recibirá las solicitudes de `POST` del webhook. | +| `active` | `boolean` | Entrega detalles del evento cuando se activa este gancho y su valor predeterminado es "true". | + +##### Parámetros + + | Nombre | Type | Descripción | + | ------- | ----------- | ------------------------------------------- | + | `state` | `secuencia` | {% data reusables.apps.state_description %} + +##### Ejemplos + +Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de usuario: + +``` +
    + Create a GitHub App Manifest:
    + +
    + + +``` +Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de organización. Reemplaza a `ORGANIZATION` con el nombre de la cuenta de organización en donde quieras crear la app. + +``` +
    + Create a GitHub App Manifest:
    + +
    + + +``` + +#### 2. GitHub redirige a las personas de vuelta a tu sitio + +Cuando la persona dé clic en **Crear GitHub App**, Github lo redirigirá a la `redirect_url` con un `code` temporal en un parámetro de código. Por ejemplo: + + https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + +Si proporcionaste un parámetro de `state`, también verás este parámetro en la `redirect_url`. Por ejemplo: + + https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + +#### 3. Intercambias el código temporal para recuperar la configuración de la app + +Para completar el intercambio, envía el `code` temporal en una solicitud de tipo `POST` a la terminal [Crear una Github App a partir de un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest). La respuesta incluirá la `id` (GitHub App ID), la `pem` (llave privada), y el `webhook_secret`. GitHub crea un secreto de webhook para la app de forma automática. Puedes almacenar estos valores en variables de ambiente dentro del servidor de la app. Por ejemplo, si tu app utiliza [dotenv](https://github.com/bkeepers/dotenv) para almacenar las variables de ambiente, almacenarías las variables en el archivo `.env` de tu app. + +Tienes solo una hora para completar este paso en el flujo del Manifiesto de la GitHub App. + +{% note %} + +**Nota:** Esta terminal tiene un límite de tasa. Consulta la sección [Límites de tasa](/rest/reference/rate-limit) para aprender cómo obtener tu estado actual de límite de tasa. + +{% endnote %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +{% data reusables.pre-release-program.fury-pre-release %} +{% data reusables.pre-release-program.api-preview-warning %} +{% endif %} + + POST /app-manifests/:code/conversions + +Para obtener más información acerca de la respuesta de la terminal, consulta la sección [Crear una GitHub App desde un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest). + +Cuando se complete el último paso del flujo del manifiesto, la persona que cree la app desde el flujo será el propietario de una GitHub App registrada que podrá instalar en cualquiera de sus repositorios personales. En cualquier momento podrán elegir extender la app utilizando las API de GitHub, transferir la propiedad a alguien más, o borrarla. + +### Utilizar el Probot par aimplementar el flujo del Manifiesto de la GitHub App + +El [Probot](https://probot.github.io/) es un marco de trabajo que se creó con [Node.js](https://nodejs.org/) y que realiza muchas de las tareas que todas las GitHub Apps requieren, como el validar webhooks y llevar a cabo la autenticación. El Probot implementa el [flujo del manifiesto de las GitHub Apps](#implementing-the-github-app-manifest-flow), lo cual facilita el crear y compartir los diseños de referencia de las GitHub Apps con la comunidad de GtiHub. + +Para crear una App de Probot que puedas compartir, sigue estos pasos: + +1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app). +1. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. El Probot utiliza la configuración en `app.yml` como los [parámetros del manifiesto dela GitHub App](#github-app-manifest-parameters). +1. Agrega el código personalizado de tu aplicación. +1. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally) u [hospédala en donde quieras](#hosting-your-app-with-glitch). Cuando navegues a la URL de la app hospedada, encontrarás una página web con un botón de **Registrar GitHub App** en el que as personas podrán dar clic para crear una app preconfigurada. La siguiente página web es la implementación del Probot para el [paso 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) en el flujo del Manifiesto de la GitHub App: + +![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png) + +Al utilizar [dotenv](https://github.com/bkeepers/dotenv), el Probot crea un archivo de tipo `.env` y configura las variables de ambiente para la `APP_ID`, `PRIVATE_KEY`, y el `WEBHOOK_SECRET` con los valores que [recupera de la configuración de la app](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). + +#### Hospedar tu app con Glitch + +Puedes ver un ejemplo de una [App de Probot de muestra](https://glitch.com/~auspicious-aardwolf) que utiliza [Glitch](https://glitch.com/) para hospedar y compartir la app. El ejemplo utiliza la [API de verificaciones](/rest/reference/checks) y selecciona los eventos necesarios de la misma y los permisos en el archivo `app.yml`. Glitch es una herramienta que te permite "Remezclar tus propias apps". El remezclar una app crea una copia de la app que Glitch hospeda y despliega. Consulta la sección "[Acerca de Glitch](https://glitch.com/about/)" para aprender sobre cómo remezclar las apps de Glitch. diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md new file mode 100644 index 0000000000000..6a3b153054ef3 --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -0,0 +1,123 @@ +--- +title: Crear una GitHub App utilizando parámetros de URL +intro: 'Puedes preseleccionar los ajustes de una nueva {% data variables.product.prodname_github_app %} utilizando [parámetros de consulta] de una URL (https://en.wikipedia.org/wiki/Query_string) para configurar rápidamente los nuevos ajustes de la {% data variables.product.prodname_github_app %}.' +redirect_from: + - /apps/building-github-apps/creating-github-apps-using-url-parameters +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Acerca de los parámetros de URL de las {% data variables.product.prodname_github_app %} + +Puedes agregar parámetros de consulta a estas URL para preseleccionar la configuración de una {% data variables.product.prodname_github_app %} en una cuenta organizacional o personal: +* **Cuenta de usuario:** `{% data variables.product.oauth_host_code %}/settings/apps/new` +* **Cuenta de organización:** `{% data variables.product.oauth_host_code %}/:org/settings/apps/new` + +El creador de la app puede editar los valores preseleccionados desde la página de registro de la {% data variables.product.prodname_github_app %} antes de emitirla. Si no incluyes los parámetros requeridos en la secuencia de consulta de la URL, como el `name`, el creador de la app necesitará ingresar un valor antes de emitirla. + +La siguiente URL crea una app pública nueva que se llama `octocat-github-app` con una descripción preconfigurada y una URL de rellamado. Esta URL también selecciona los permisos de lectura y escritura para las `checks`, se suscribe a los eventos de webhook de `check_run` y `check_suite`, y selecciona la opción para solicitar la autorización del usuario (OAuth) durante la instalación: + + ``` + {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite + ``` + +La lista completa de parámetros de consulta, permisos y eventos disponibles se lista en las secciones siguientes. + +### Parámetros de configuración de una {% data variables.product.prodname_github_app %} + + | Nombre | Type | Descripción | + | -------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name (nombre)` | `secuencia` | El nombre de la {% data variables.product.prodname_github_app %}. Pónle un nombre claro y breve a tu app. Tu app no puede tener el mismo nombre que un usuario de GitHub, a menos de que sea tu propio nombre de usuario u organización. Una versión simplificada del nombre de tu aplicación se mostrará en la interface de usuario cuando tu integración tome alguna acción. | + | `description` | `secuencia` | Una descripción de la {% data variables.product.prodname_github_app %}. | + | `url` | `secuencia` | La URL complea de la página principal del sitio web de tu {% data variables.product.prodname_github_app %}. | + | `callback_url` | `secuencia` | La URL completa a la cual se redirigirá después de que alguien autorice la instalación. Esta URL se utiliza si tu app necesita identificar y autorizar las solicitudes de usuario a servidor. | + | `request_oauth_on_install` | `boolean` | Si tu app autoriza a los usuarios mediante el flujo de OAuth, puedes configurar esta opción como `true` para permitir que las personas autoricen la app cuando la instalen, lo cual te ahorra un paso. Si seleccionas esta opción, la `setup_url` deja de estar disponible y se redirigirá a los usuarios a tu `callback_url` después de que instalen la app. | + | `setup_url` | `secuencia` | La URL completa a la cual se redirigirá después de que instalen la {% data variables.product.prodname_github_app %} si ésta requiere de alguna configuración adicional después de su instalación. | + | `setup_on_update` | `boolean` | Configúralo como `true` para redireccionar a las personas a la URL de ajustes cuando las instalaciones se actualicen, por ejemplo, después de que se agreguen o eliminen repositorios. | + | `public` | `boolean` | Configúralo como `true` cuando tu {% data variables.product.prodname_github_app %} se encuentre disponible al público, o como `false` cuando solo el propietario de la misma tenga acceso a ella. | + | `webhook_url` | `secuencia` | La URL completa a la cual quisieras enviar cargas útiles de eventos de webhook. | + | `webhook_secret` | `secuencia` | Puedes especificar un secreto para asegurar tus webhooks. Consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)" para obtener más detalles. | + | `events` | `conjunto de secuencias` | Eventos de webhook. Algunos eventos de webhook requieren asignar permisos de `read` o de `write` a un recurso antes de que puedas seleccionar el evento cuando registras una {% data variables.product.prodname_github_app %} nueva. Consulta la sección "[Eventos de webhook de las {% data variables.product.prodname_github_app %}](#github-app-webhook-events)" para encontrar los eventos disponibles y sus permisos requeridos. Puedes seleccionar eventos múltiples en una secuencia de consulta. Por ejemplo, `events[]=public&events[]=label`. | + | `domain` | `secuencia` | La URL de una referencia de contenido. | + | `single_file_name` | `secuencia` | Este es un permiso con alcance corto que permite a la app acceder a un solo archivo en cualquier repositorio. Cuando configuras el permiso de `single_file` en `read` o `write`, este campo proporciona la ruta al archivo único que administrará tu {% data variables.product.prodname_github_app %}. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Si necesitas administrar varios archivos, consulta la opción `single_file_paths` a continuación. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + | `single_file_paths` | `conjunto de secuencias` | Esto permite a la app acceder hasta a 10 archivos especificos en un repositorio. Cuando configuras el permiso `single_file` en `read` o `write`, este arreglo puede almacenar las rutas de hasta diez archivos que administrará tu {% data variables.product.prodname_github_app %}. Estos archivos reciben el mismo permiso que se configuró para `single_file`, y no tienen permisos individuales por separado. Cuando dos o mas archivos se configuran, la API devuelve `multiple_single_files=true`, de lo contrario, devuelve `multiple_single_files=false`.{% endif %} + +### Permisos de la {% data variables.product.prodname_github_app %} + +Puedes seleccionar los permisos en una secuencia de consulta utilizando los nombres de permiso conforme en la siguiente tabla a manera de nombres de parámetro de consulta y usando el tipo de permiso como el valor de la consulta. Por ejemplo, para seleccionar los permisos de `Read & write` en la interface de usuario para `contents`, tu secuencia de consulta incluiría `&contents=write`. Para seleccionar los permisos de `Read-only` en la interface de usuario para `blocking`, tu secuencia de consulta incluiría `&blocking=read`. Para seleccionar `no-access` en la interface de usuario para las `checks`, tu secuencia de consulta no incluiría el permiso `checks`. + +| Permiso | Descripción | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Otorga acceso a diversas terminales para la administración de organizaciones y repositorios. Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" %} +| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Otorga acceso a la [API de Bloqueo de Usuarios](/rest/reference/users#blocking). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} +| [`verificaciones`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Otorga acceso a la [API de verificaciones](/rest/reference/checks). Puede ser uno de entre `none`, `read`, o `write`. | +| `content_references` | Otorga acceso a la terminal "[Crear un adjunto de contenido](/rest/reference/apps#create-a-content-attachment)". Puede ser uno de entre `none`, `read`, o `write`. | +| [`contenidos`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Otorga acceso a diversas terminales que te permiten modificar el contenido de los repositorios. Puede ser uno de entre `none`, `read`, o `write`. | +| [`implementaciones`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Otorga acceso a la [API de despliegues](/rest/reference/repos#deployments). Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Otorga acceso a la [API de Correos electrónicos](/rest/reference/users#emails). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} +| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Otorga acceso a la [API de Seguidores](/rest/reference/users#followers). Puede ser uno de entre `none`, `read`, o `write`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Otorga acceso a la [API de Llaves GPG](/rest/reference/users#gpg-keys). Puede ser uno de entre `none`, `read`, o `write`. | +| [`propuestas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Otorga acceso a la [API de Informe de problemas](/rest/reference/issues). Puede ser uno de entre `none`, `read`, o `write`. | +| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Otorga acceso a la [API de Llaves Públicas](/rest/reference/users#keys). Puede ser uno de entre `none`, `read`, o `write`. | +| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Otorga acceso para administrar los miembros de una organización. Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" %} +| [`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Otorga acceso a las terminales de solo lectura que no filtran datos sensibles. Puede ser `read` o `none`. Su valor predeterminado es `read` cuando configuras cualquier permiso, o bien, `none` cuando no especificas ningún permiso para la {% data variables.product.prodname_github_app %}. | +| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Otorga acceso a la terminal "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" y a la [API de Restricciones de Interacción en la Organización](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Otorga acceso a la [API de Webhooks de la Organización](/rest/reference/orgs#webhooks/). Puede ser uno de entre `none`, `read`, o `write`. | +| `organization_plan` | Otorga acceso para obtener información acerca del plan de una organización que utilice la terminal "[Obtener una organización](/rest/reference/orgs#get-an-organization)". Puede ser uno de entre `none` o `read`. | +| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Otorga acceso a la [API de Proyectos](/rest/reference/projects). Puede ser uno de entre: `none`, `read`, `write`, o `admin`.{% if currentVersion == "free-pro-team@latest" %} +| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Otorga acceso a la [API de Bloqueo de Usuarios de la Organización](/rest/reference/orgs#blocking). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} +| [`páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Otorga acceso a la [API de páginas](/rest/reference/repos#pages). Puede ser uno de entre `none`, `read`, o `write`. | +| `plan` | Otorga acceso para obtener información acerca del plan de GitHub de un usuario que utilice la terminal "[Obtener un usuario](/rest/reference/users#get-a-user)". Puede ser uno de entre `none` o `read`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Otorga acceso a varias terminales de solicitud de extracción. Puede ser uno de entre `none`, `read`, o `write`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Otorga acceso a la [API de Webhooks del Repositorio](/rest/reference/repos#hooks). Puede ser uno de entre `none`, `read`, o `write`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Otorga acceso a la [API de Proyectos](/rest/reference/projects). Puede ser uno de entre: `none`, `read`, `write`, o `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Otorga acceso a la [API de escaneo de secretos](/rest/reference/secret-scanning). Puede ser uno de entre: `none`, `read`, o `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Otorga acceso a la [API de escaneo de código](/rest/reference/code-scanning/). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Otorga acceso a la [API de Contenidos](/rest/reference/repos#contents). Puede ser uno de entre `none`, `read`, o `write`. | +| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Otorga acceso a la [API de marcar con estrella](/rest/reference/activity#starring). Puede ser uno de entre `none`, `read`, o `write`. | +| [`estados`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Otorga acceso a la [API de Estados](/rest/reference/repos#statuses). Puede ser uno de entre `none`, `read`, o `write`. | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Otorga acceso a la [API de debates de equipo](/rest/reference/teams#discussions) y a la [API de comentarios en debates de equipo](/rest/reference/teams#discussion-comments). Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} +| `vulnerability_alerts` | Otorga acceso para recibir alertas de seguridad para las dependencias vulnerables en un repositorio. Consulta la sección "[Acerca de las alertas de seguridad para las dependencias vulnerables](/articles/about-security-alerts-for-vulnerable-dependencies)" para aprender más. Puede ser uno de entre: `none` o `read`.{% endif %} +| `watching` | Otorga acceso a la lista y cambia los repositorios a los que un usuario está suscrito. Puede ser uno de entre `none`, `read`, o `write`. | + +### Eventos de webhook de {% data variables.product.prodname_github_app %} + +| Nombre del evento de webhook | Permiso requerido | Descripción | +| ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------- | +| [`check_run`](/webhooks/event-payloads/#check_run) | `verificaciones` | {% data reusables.webhooks.check_run_short_desc %} +| [`check_suite`](/webhooks/event-payloads/#check_suite) | `verificaciones` | {% data reusables.webhooks.check_suite_short_desc %} +| [`comentario_confirmación de cambios`](/webhooks/event-payloads/#commit_comment) | `contenidos` | {% data reusables.webhooks.commit_comment_short_desc %} +| [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} +| [`create (crear)`](/webhooks/event-payloads/#create) | `contenidos` | {% data reusables.webhooks.create_short_desc %} +| [`eliminar`](/webhooks/event-payloads/#delete) | `contenidos` | {% data reusables.webhooks.delete_short_desc %} +| [`deployment`](/webhooks/event-payloads/#deployment) | `implementaciones` | {% data reusables.webhooks.deployment_short_desc %} +| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `implementaciones` | {% data reusables.webhooks.deployment_status_short_desc %} +| [`fork`](/webhooks/event-payloads/#fork) | `contenidos` | {% data reusables.webhooks.fork_short_desc %} +| [`gollum`](/webhooks/event-payloads/#gollum) | `contenidos` | {% data reusables.webhooks.gollum_short_desc %} +| [`propuestas`](/webhooks/event-payloads/#issues) | `propuestas` | {% data reusables.webhooks.issues_short_desc %} +| [`comentario_propuesta`](/webhooks/event-payloads/#issue_comment) | `propuestas` | {% data reusables.webhooks.issue_comment_short_desc %} +| [`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %} +| [`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} +| [`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} +| [`milestone`](/webhooks/event-payloads/#milestone) | `solicitud_extracción` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} +| [`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} +| [`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} +| [`page_build`](/webhooks/event-payloads/#page_build) | `páginas` | {% data reusables.webhooks.page_build_short_desc %} +| [`project`](/webhooks/event-payloads/#project) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_short_desc %} +| [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} +| [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} +| [`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %} +| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} +| [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review) | `solicitud_extracción` | {% data reusables.webhooks.pull_request_review_short_desc %} +| [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | `solicitud_extracción` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} +| [`push`](/webhooks/event-payloads/#push) | `contenidos` | {% data reusables.webhooks.push_short_desc %} +| [`release`](/webhooks/event-payloads/#release) | `contenidos` | {% data reusables.webhooks.release_short_desc %} +| [`repositorio`](/webhooks/event-payloads/#repository) | `metadata` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} +| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contenidos` | Permite que los integradores que utilizan GitHub Actions activen eventos personalizados.{% endif %} +| [`status`](/webhooks/event-payloads/#status) | `estados` | {% data reusables.webhooks.status_short_desc %} +| [`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} +| [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} +| [`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app.md b/translations/es-ES/content/developers/apps/creating-a-github-app.md new file mode 100644 index 0000000000000..ca92c5d6b363d --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-a-github-app.md @@ -0,0 +1,69 @@ +--- +title: Crear una GitHub App +intro: '{% data reusables.shortdesc.creating_github_apps %}' +redirect_from: + - /early-access/integrations/creating-an-integration/ + - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps/ + - /apps/building-github-apps/creating-a-github-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %}Para aprender cómo utilizar los manifiestos de las GitHub Apps, los cuales le permiten a las personas crear GitHub Apps preconfiguradas, consulta la sección "[Crear GitHub Apps desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + + **Nota:** {% data reusables.apps.maximum-github-apps-allowed %} + +{% endnote %} +{% endif %} + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Da clic en **GitHub App Nueva**. ![Botón para crear una GitHub App nueva](/assets/images/github-apps/github_apps_new.png) +5. E "Nombre dela GitHub App", teclea el nombre de tu app. ![Campo para nombrar tu GitHub App](/assets/images/github-apps/github_apps_app_name.png) + + Pónle un nombre claro y breve a tu app. Tu app no puede tener el mismo nombre que un usuario de GitHub, a menos de que sea tu propio nombre de usuario u organización. Una versión simplificada del nombre de tu aplicación se mostrará en la interface de usuario cuando tu integración tome alguna acción. + +6. Opcionalmente, en "Descripción", teclea la descripción de tu app que verán los usuarios. ![Campo para agregar una descripción de tu GitHub App](/assets/images/github-apps/github_apps_description.png) +7. En "URL de la página principal", teclea la URL completa del sitio web de tu app. ![Campo para la URL de la página de inicio de tu GitHub App](/assets/images/github-apps/github_apps_homepage_url.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +8. En "URL de rellamado", teclea la URL completa a la cual se redirigirá a los usuarios después de que autoricen la instalación. Esta URL se utiliza si tu app necesita identificar y autorizar las solicitudes de usuario a servidor. + + Puedes utilizar la opción de **Agregar una URL de rellamado** para proporcionar las URL de rellamado adicionales, con un máximo de 10 de ellas. + + ![Botón para 'Agregar una URL de rellamado' y campo para ingresar la URL de rellamado](/assets/images/github-apps/github_apps_callback_url_multiple.png) +{% else %} +8. En "URL de rellamado para la autorización del usuario", teclea la URL completa a la cual se redireccionará después de que un usuario autorice una instalación. Esta URL se utiliza si tu app necesita identificar y autorizar las solicitudes de usuario a servidor. ![Campo para la URL de rellamado para la autorización del usuario de tu GitHub App](/assets/images/github-apps/github_apps_user_authorization.png) + +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +9. Predeterminadamente, para mejorar la seguridad de tu app, ésta utilizará un token de autorización de usuario con una vida útil limitada. Para elegir no utilizar estos tokens de usuario, debes deseleccionar la opción "Limitar la vida útil de los tokens de autorización de usuario". Para conocer más acerca de configurar un flujo de rehabilitación de tokens y acerca de los beeficios de que éstos tenga una vida útil limitada, consulta la sección "[Rehabilitar los tokens de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)". ![Opción para unirse a los tokens de usuario con caducidad durante la configuración de las GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) +{% endif %} +9. Si tu app autoriza a los usuarios que utilizan el flujo de OAuth, puedes seleccionar la opción **Solicitar la autorización del usuario (OAuth) durante la instalación** para permitir que las personas den autorización a la app cuando la instalen, lo cual te ahorra un paso. Si seleccionas esta opción, la "URL de configuración" dejará de estar disponible y se redirigirá a los usuarios a tu "URL de rellamado para autorización del usuario" después de que instalen la app. Consulta la sección "[Autorizar a los usuarios durante la instalación](/apps/installing-github-apps/#authorizing-users-during-installation)" para obtener más información. ![Solicitar una autorización de usuario durante la instalación](/assets/images/github-apps/github_apps_request_auth_upon_install.png) +10. Si se requiere hacer ajustes adicionales después de la instalación, agrega una "URL de configuración" para redireccionar a los usuarios después de que instalen tu app. ![Campo para configurar la URL de tu GitHub App ](/assets/images/github-apps/github_apps_setup_url.png) + + {% note %} + + **Nota:** Cuando seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación** en el paso anterior, este campo dejará de estar disponible y se redirigirá a los usuarios a tu "URL de rellamado para autorización del usuario" después de que instalen la app. + + {% endnote %} + +11. En "URL del Webhook", teclea la URL a la cual los eventos harán POST. Cada app recibe su propio webhook, el cual te notificará cada que se instale o modifique dicha app, así como sobre cualquier otor evento al cual se suscriba. ![Campo para la URL del webhook de tu GitHub App](/assets/images/github-apps/github_apps_webhook_url.png) + +12. Opcionalmente, en "Secreto del Webhook", teclea un token secreto opcional que se utilizará para asegurar tus webhooks. ![Campo para agregar un token secreto para tu Webhook](/assets/images/github-apps/github_apps_webhook_secret.png) + + {% note %} + + **Nota:** Te recomendamos ampliamente que configures un token secreto. Para obtener más información, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". + + {% endnote %} + +13. En "Permisos", elige aquellos permisos que solicitará tu app. Para cada tipo de permiso, utiliza el menú desplegable, y da clic en **Solo lectura**, **Lectura& escritura**, o **Sin acceso**. ![Varios permisos para tu GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) +14. En "Suscribirse a los eventos", elige si quieres suscribir a tu app a los eventos de **Etiquetas**, **Públicos**, **Repositorios**, o **Observar**. ![Opciones de suscripción a los eventos para tu GitHub App](/assets/images/github-apps/github_apps_subscribe_to_events.png) +15. Para elegir si la app se podrá instalar, selecciona ya sea **Únicamente en esta cuenta** o **Cualquier cuenta**. Para obtener más información sobre las opciones de instalación, selecciona "[Convertir una GitHub App en pública o privada](/apps/managing-github-apps/making-a-github-app-public-or-private/)". ![Opciones de instalación para tu GitHub App](/assets/images/github-apps/github_apps_installation_options.png) +16. Da clic en **Crear GitHub App**. ![Botón para crear tu GitHub App](/assets/images/github-apps/github_apps_create_github_app.png) diff --git a/translations/es-ES/content/developers/apps/creating-an-oauth-app.md b/translations/es-ES/content/developers/apps/creating-an-oauth-app.md new file mode 100644 index 0000000000000..14e4f69eb4186 --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-an-oauth-app.md @@ -0,0 +1,49 @@ +--- +title: Crear una App de OAuth +intro: '{% data reusables.shortdesc.creating_oauth_apps %}' +redirect_from: + - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps/ + - /apps/building-oauth-apps/creating-an-oauth-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + + **Nota:** {% data reusables.apps.maximum-oauth-apps-allowed %} + +{% endnote %} +{% endif %} + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +4. Da clic en **Nueva App de OAuth**. ![Botón para crear una app de OAuth nueva](/assets/images/oauth-apps/oauth_apps_new_app.png) + + {% note %} + + **Nota:** si es la primera vez que creas una app, este botón dirá **Registrar una aplicación nueva**. + + {% endnote %} +6. Teclea el nombre de tu app en "Nombre de la aplicación". ![Campo para el nombre de tu app](/assets/images/oauth-apps/oauth_apps_application_name.png) + + {% warning %} + + **Advertencia** Utiliza solo la información que consideres pública en tu App de OAuth. Evita utilizar datos sensibles, tales como URL internas, cuando crees una App de OAuth. + + {% endwarning %} + +7. En "URL de la página principal", teclea la URL completa del sitio web de tu app. ![Campo para la URL de la página principal de tu app](/assets/images/oauth-apps/oauth_apps_homepage_url.png) +8. Opcionalmente, en "Descripción de la aplicación", teclea una descripción de tu app para que los usuarios la vean. ![Campo para la descripción de tu app](/assets/images/oauth-apps/oauth_apps_application_description.png) +9. Teclea la URL de rellamado de tu app en "URL de rellamado para autorización". ![Campo para la URL de rellamado de autorización de tu app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + {% note %} + + **Nota:** Las apps de OAuth no puede tener URL de rellamado múltiples, a diferencia de las {% data variables.product.prodname_github_apps %}. + + {% endnote %} +{% endif %} +10. Haz clic en **Register application** (Registrar aplicación). ![Botón para registrar una aplicación](/assets/images/oauth-apps/oauth_apps_register_application.png) diff --git a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md new file mode 100644 index 0000000000000..191979d297b9b --- /dev/null +++ b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -0,0 +1,872 @@ +--- +title: Crear pruebas de IC con la API de Verificaciones +intro: 'Crea un servidor de integración continua para ejecutar pruebas utilizando una {% data variables.product.prodname_github_app %} y la API de Verificaciones.' +redirect_from: + - /apps/quickstart-guides/creating-ci-tests-with-the-checks-api +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Introducción + +Esta guía te dará una introducción a las [GitHub Apps](/apps/) y a la [API de verificaciones](/rest/reference/checks), las cuales utilizarás para crear un servidor de Integración contínua (CI) que ejecute pruebas. + +La IC es una práctica de software que requiere código confirmado frecuente en un repositorio compartido. El código de confirmación generar errores de manera temprana frecuentemente, así como reduce la cantidad de código que necesita un desarrollador para hacer depuraciones cuando encuentra la fuente de un error. Las actualizaciones frecuentes de código facilitan también la fusión de cambios de diferentes miembros de un equipo de desarrollo de software. Esto es excelente para los desarrolladores, que pueden dedicar más tiempo a escribir código y menos tiempo a depurar errores o resolver conflictos de fusión. 🙌 + +Un servidor de IC hospeda código que ejecuta pruebas de IC, tal como los limpíadores de código (que revisan el formato del estilo), revisiones de seguridad, cobertura de código, y otras verificaciones contra las confirmaciones de código nuevas que hay en un repositorio. Los servidores de IC incluso pueden crear y desplegar código en los servidores de pruebas y en los productivos. Para encontrar algunas ejemplos de los tipos de pruebas de IC que puedes crear con una GitHub App, revisa las [apps de integración continua](https://github.com/marketplace/category/continuous-integration) que se encuentran disponibles en GitHub Marketplace. + +{% data reusables.apps.app-ruby-guides %} + +#### Resumen de la API de Verificaciones + +La [API de Verificaciones](/rest/reference/checks) te permite configurar las pruebas de IC que se ejecutan automáticamente contra cada confirmación de código en un repositorio. La API de Verificaciones reporta información detallada acerca de cada verificación en GitHub dentro de la pestaña de **Verificaciones** de las solicitudes de extracción. Con la API de verificaciones, puedes crear anotaciones con detalles adicionales para líneas específicas de código. Las anotaciones se encuentran visibles en la pestaña de **Verificaciones**. Cuando creas una anotación para un archivo que es parte de la solicitud de extracción, estas también se muestran en la pestaña **Archivos cambiados**. + +Un _conjunto de verificaciones_ es un grupo de _ejecuciones de verificación_ (pruebas de IC individuales). Tanto estos conjuntos como las ejecuciones contienen _estados_ que pueden visualizarse en la solicitud de extracción en GitHub. Puedes utilizar estados para determinar cuando una confirmación de código introduce errores. El utilizar estos estados con [ramas protegidas](/rest/reference/repos#branches) puede prevenir que las personas fusionen solicitudes de extracción prematuramente. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. + +La API de Verificaciones envía el [evento de webhook `check_suite`](/webhooks/event-payloads/#check_suite) a todas las GitHub Apps que se instalan en un repositorio cada vez que se carga código nuevo a éste. Para recibir todas las acciones de los eventos de la API de Verificaciones, la app debe contar con el permiso `checks:write`. GitHub crea los eventos de `check_suite` automáticamente para las nuevas confirmaciones de código en un repositorio utilizando el flujo predeterminado, aunque puedes [Actualizar las preferencias del repositorio para los conjuntos de verificaciones](/rest/reference/checks#update-repository-preferences-for-check-suites) si así lo quieres. Aquí te mostramos cómo funciona el flujo predeterminado: + +1. Cada que alguien carga código en el repositorio, GitHub envía el evento de `check_suite` con una acción de `requested` a todas las GitHub Apps que estén instaladas en el repositorio que tiene el permiso de `checks:write`. Este evento permite a las apps saber que se cargó código y que GitHub creó un nuevo conjunto de verificaciones automáticamente. +1. Cuando tu app recibe este evento, puede [agregar ejecuciones de verificacion](/rest/reference/checks#create-a-check-run) a ese conjunto. +1. Tus ejecuciones de verificacion pueden incluir [anotaciones](/rest/reference/checks#annotations-object) que se muestran en líneas de código específicas. + +**En esta guía, aprenderás cómo:** + +* Parte 1: Configurar el marco de trabajo para un servidor de IC utilizando la API de Verificaciones. + * Configurar una GitHub App como un servidor que recibe los eventos de la API de Verificaciones. + * Crear ejecuciones de verificacion nuevas para las pruebas de IC cuando un repositorio recibe cargas nuevas de confirmaciones. + * Re-ejecutar ejecuciones de verificación cuando un usuario solicita esta acción en GitHub. +* Parte 2: Compilar en el marco de trabajo del servidor de IC que creaste agregando una prueba de limpieza de IC. + * Actualizar una ejecución de verificación con un `status`, `conclusion`, y `output` details. + * Crear anotaciones en las líneas de código que muestra GitHub en las pestañas de **Verificaciones** y **Archivos Cambiados** de una solicitud de extracción. + * Arreglar automáticamente las recomendaciones del limpiador al exponer el botón "Arreglar esto" en la pestaña de **Verificaciones** de la solicitud de extracción. + +Para obtener una idea de lo que hará tu servidor de IC para la API de Verificaciones cuando completes este inicio rápido, revisa el siguiente demo: + +![Demostración de la guía de inicio rápido para el servidor de IC de la API de Verificaciones](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) + +### Prerrequisitos + +Antes de que inicies, tal vez quieras familiarizarte con las [GitHub Apps](/apps/), los [Webhooks](/webhooks), y con la [API de Verificaciones](/rest/reference/checks), si aún no lo has hecho. Encontrarás más API en los [documentos de la API de REST](/rest). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/graphql), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/graphql/reference/objects#checksuite) y [Ejecución de Verificación](/graphql/reference/objects#checkrun) de GraphQL para obtener más detalles. + +Utilizarás el [Lenguaje de Programación Ruby](https://www.ruby-lang.org/en/), el servicio de entrega de carga útil para el webhook de [Smee](https://smee.io/), la [biblioteca de Ruby Ocktokit.rb](http://octokit.github.io/octokit.rb/) para la API de REST de GitHub, y el [marco de trabajo web Sinatra](http://sinatrarb.com/) para crear tu aplicación de servidor de IC para la API de Verificaciones. + +No necesitas ser un experto en ninguna de estas herramientas o conceptos para completar este proyecto. Esta guía te mostrará todos los pasos requeridos a detalle. Antes de que comiences a crear pruebas de IC con la API de Verificaciones, necesitarás hacer lo siguiente: + +1. Clona el repositorio [Crear pruebas de IC con la API de Verificaciones](https://github.com/github-developer/creating-ci-tests-with-the-checks-api). + ```shell + $ git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git + ``` + + Dentro del directorio, encontrarás un archivo de nombre `template_server.rb` con el código de plantilla que utilizarás en este inicio rápido, y un archivo llamado `server.rb` con el código del proyecto completo. + +1. Sigue los pasos en la guía de inicio rápido "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)" para configurar y ejecutar el servidor de la app. **Nota:** en vez de [clonar el repositorio de plantilla de GitHub App](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites), utiliza el archivo `template_server.rb` en el repositorio que clonaste en el paso anterior de esta guía de inicio rápido. + + Si ya has completado una guía de inicio rápido de GitHub App anteriormente, asegúrate de registrar una GitHub App _nueva_ y levanta un canal de Smee nuevo para utilizarlo con esta guía de inicio rápido. + + Consulta la sección [solución de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) si te encuentras con algún problema al configurar tu GitHub App de plantilla. + +### Parte 1. Crear la interface de la API de Verificaciones + +En esta parte, agregarás el código necesario para recibir eventos del webhook de `check_suite` y para las ejecuciones de verificación de creación y actualización. También aprenderás cómo crear ejecuciones de verificación cuando se re-solicite una verificación en GitHub. Al final de esta sección, podrás ver la ejecución de verificación que creaste en una solicitud de extracción de GitHub. + +En esta sección, tu ejecución de verificación no realizará ninguna verificación de código. Agregarás esa funcionalidad en la [Parte 2: Crear la prueba de IC de Octo RuboCop](#part-2-creating-the-octo-rubocop-ci-test). + +Ya deberías haber configurado el canal de Smee que reenviará las cargas útiles del webhook a tu servidor local. Tu servidor deberá estar funcionando y también estar conectado con la GitHub App que registraste e instalaste ene un repositorio de prueba. Si no has completado los pasos de "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)", necesitarás hacerlo antes de que puedas continuar. + +¡Comencemos! Estos son los pasos que completarás en la Parte 1: + +1. [Actualizar los permisos de la app](#step-11-updating-app-permissions) +1. [Agregar la gestión de eventos](#step-12-adding-event-handling) +1. [Crear una ejecución de verificación](#step-13-creating-a-check-run) +1. [Actualizar una ejecución de verificación](#step-14-updating-a-check-run) + +### Paso 1.1. Actualizar los permisos de la app + +Cuando [registraste tu app por primera vez](#prerequisites), aceptaste los permisos predeterminados, lo que significa que tu app no tiene acceso a la mayoría de los recursos. Para este ejemplo, tu app necesitará el permiso de leer y escribir verificaciones. + +Para actualizar los permisos de tu app: + +1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. +1. En la sección de "Permisos", encuentra "Verificaciones"; y selecciona **Lectura & escritura** en el menú desplegable de acceso que está a un costado. +1. En la sección "Sucribirse a los eventos", selecciona **conjuntos de verificación** y **ejecución de verificación** para suscribirte a estos eventos. +{% data reusables.apps.accept_new_permissions_steps %} + +¡Genial! Tu app tiene permiso para realizar las tareas que quieres que haga. Ahora puedes agregar el código para que gestione los eventos. + +### Paso 1.2. Agregar la gestión de eventos + +Ahora que tu app está suscrita a los eventos de **conjuntos de verificaciones** y **ejecución de verificación**, comenzará a recibir los webhooks [`check_suite`](/webhooks/event-payloads/#check_suite) y [`check_run`](/webhooks/event-payloads/#check_run). GitHub envía las cargas útiles de los webhooks como solicitudes de tipo `POST`. Ya que reenviaste las cargas útiles del webhook de Smee a `http://localhost/event_handler:3000`, tu servidor recibirá las cargas útiles de la solicitud de `POST` en la ruta `post '/event_handler'`. + +Ya se incluye una ruta de `post '/event_handler'` vacía en el archivo `template_server.rb`, el cual descargaste en la sección de [prerrequisitos](#prerequisites). La ruta vacía se ve así: + +``` ruby + post '/event_handler' do + + # # # # # # # # # # # # + # ADD YOUR CODE HERE # + # # # # # # # # # # # # + + 200 # success status + end +``` + +Utiliza esta ruta para gestionar el evento `check_suite` agregando el siguiente código: + +``` ruby +# Get the event type from the HTTP_X_GITHUB_EVENT header +case request.env['HTTP_X_GITHUB_EVENT'] +when 'check_suite' + # A new check_suite has been created. Create a new check run with status queued + if @payload['action'] == 'requested' || @payload['action'] == 'rerequested' + create_check_run + end +end +``` + +Cada vento que envíe GitHub incluye un encabezado de solicitud que se llama `HTTP_X_GITHUB_EVENT`, el cual indica el tipo de evento en la solicitud de `POST`. Ahora mismo solo te interesan los eventos de tipo `check_suite`, los cuales se emiten cuando se crea un nuevo conjunto de verificaciones. Cada evento tiene un campo adicional de `action` que indica el tipo de acción que activó los eventos. Para`check_suite`, el campo `action` puede ser `requested`, `rerequested`, o `completed`. + +La acción `requested` solicita una ejecución de verificación cada vez que se carga el código al repositorio, mientras que la acción `rerequested` solicita que re-ejecutes una verificación para el código que ya existe en el repositorio. Ya que ambas acciones, `requested` y `rerequested` requieren crear una ejecución de verificación, llamarás a un ayudante llamado `create_check_run`. Vamos a escribir ese método ahora. + +### Paso 1.3. Crear una ejecución de verificación + +Agregarás este método nuevo como un [Ayudante de Sinatra](https://github.com/sinatra/sinatra#helpers) en caso de que quieras que otras rutas lo utilicen también. Debajo de `helpers do`, agrega este método de `create_check_run`: + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +``` ruby +# Create a new check run with the status queued +def create_check_run + # # At the time of writing, Octokit does not support the Checks API yet, but + # it does provide generic HTTP methods you can use: + # /rest/reference/checks#create-a-check-run + check_run = @installation_client.post( + "repos/#{@payload['repository']['full_name']}/check-runs", + { + accept: 'application/vnd.github.v3+json', + # The name of your check run. + name: 'Octo RuboCop', + # The payload structure differs depending on whether a check run or a check suite event occurred. + head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'] + } + ) +end +``` +{% else %} +``` ruby +# Create a new check run with the status queued +def create_check_run + # # At the time of writing, Octokit does not support the Checks API yet, but + # it does provide generic HTTP methods you can use: + # /rest/reference/checks#create-a-check-run + check_run = @installation_client.post( + "repos/#{@payload['repository']['full_name']}/check-runs", + { + # This header allows for beta access to Checks API + accept: 'application/vnd.github.antiope-preview+json', + # The name of your check run. + name: 'Octo RuboCop', + # The payload structure differs depending on whether a check run or a check suite event occurred. + head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'] + } + ) +end +``` +{% endif %} + +Este código llama a la terminal "[Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run)" utilizando el [Método HTTP de `publicación`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method) genérico. Este método toma dos parámetros: la URL de la terminal y los parámetros de entrada del método. + +Solo se requieren dos parámetros de entrada para crear una ejecución de flujo de trabajo: `name` y `head_sha`. Utilizaremos a [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar la prueba de IC más adelante en esta guía de inicio rápido, y esto es por lo que se utiliza el nombre "Octo Rubocop" aquí, pero puedes elegir cualquier nombre que quieras para la ejecución de verificación. + +Ahora mismo, solo estás proporcionando los parámetros requeridos para echar a andar la funcionalidad básica, pero actualizarás la ejecución de verificación más adelante mientras recolectes más información acerca de la ejecución de verificación. Predeterminadamente, GitHub configura el `Estado` como `queued`. + +GitHub Crea una ejecución de flujo de trabajo para un SHA de confirmación específico, y es por esto que el `head_sha` es un parámetro requerido. Puedes encontrar el SHA de la confirmación en la carga útil del webhook. Aunque ahora mismo solo estás creando una ejecución de verificación para el evento `check_suite`, es bueno saber que el `head_sha` se incluye tanto en el objeto de `check_suite` como en el de `check_run` dentro de las cargas útiles del evento. + +En el código anterior, estás utilizando el [operador ternario](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if), el cual funciona como una declaración `if/else`, para verificar si la carga útil contiene un objeto `check_run`. Si lo tiene, lees el `head_sha` desde el objeto `check_run`, de lo contrario lo leerías desde el objeto de `check_suite`. + +Para probar este código, reinicia el servidor desde tu terminal: + +```shell +$ ruby template_server.rb +``` + +{% data reusables.apps.sinatra_restart_instructions %} + +Ahora abre una solicitud de extracción en el repositorio en donde instalaste tu app. Tu app deberá responder creando una ejecución de verificación en tu solicitud de cambios. Da clic en la pestaña de **Verificaciones** y deberías ver algo como esto: + +![Ejecución de verificación en cola](/assets/images/github-apps/github_apps_queued_check_run.png) + +Si ves otras apps en la pestaña de verificaciones, significa que tienes otras apps instaladas en tu repositorio las cuales cuentan con acceso de **Lectura & escritura** en las verificaciones y que están suscritas a los eventos de **conjuntos de verificaciones** y de **ejecución de verificación**. + +¡Genial! Le has dicho a GitHub que cree una ejecución de verificación. Puedes ver junto al icono amarillo que el estado de esta ejecución de verificación se configuró como `queued`. A continuación, deberás esperar a que GitHub cree la ejecución de verificación y actualice su estado. + +### Paso 1.4. Actualizar una ejecución de verificación + +Cuando tu método de `create_check_run` se ejecuta, éste solicita a GitHub crear una ejecución de verificación nueva. Cuando GitHub termine de crear la ejecución de verificación, recibirás un evento de webhook de `check_run` con la acción como `created`. Este evento es tu señal para comenzar a ejecutar la verificación. + +Necesitas actualizar tu gestor de eventos para buscar la acción que se encuentra como `created`. Mientras actualizas el gestor de eventos, puedes agregar una condicional para la acción que se encuentra como `rerequested`. Cuando alguien re-ejecuta una sola prueba en GitHub, al dar clic en el botón de "Re-ejecutar", GitHub envía a tu app el evento de ejecución de verificación que está como `rerequested`. Cuando una ejecución de verificación se pone como `rerequested`, necesitarás iniciar el proceso desde cero y crear una ejecución de verificación nueva. + +Para incluir una condición para el evento de `check_run` en la ruta de `post '/event_handler'`, agrega el siguiente código debajo de `case request.env['HTTP_X_GITHUB_EVENT']`: + +``` ruby +when 'check_run' + # Check that the event is being sent to this app + if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER + case @payload['action'] + when 'created' + initiate_check_run + when 'rerequested' + create_check_run + end + end +``` + +GitHub envía todos los eventos de las ejecuciones de verificación que se encuentran como `created` a cada app instalada en un repositorio, la cual tenga los permisos de verificación necesarios. Esto significa que tu app recibirá las ejecuciones de verificación que creen otras apps. Una ejecución de verificación que se encuentre como `created` es un poco diferente de un conjunto de verificaciones que estén como `requested` o `rerequested` y que GitHub envía únicamente a las aplicaciones a las cuales se solicita que ejecuten una verificación. El código anterior busca la ID de aplicación de la ejecución de verificación. Esto filtra todas las ejecuciones de verificación para otras apps en el repositorio. + +A continuación, escribirás el método de `initiate_check_run`, que es donde actualizarás el estado de la ejecución de verificación y donde te prepararás para lanzar tu prueba de IC. + +En esta sección no vas a lanzar la prueba de IC aún, pero te mostraremos cómo actualizar el estado de la ejecución de verificación de `queued` a `pending` y después de `pending` a `completed` para ver el flujo general de una ejecución de verificación. En la "[Parte 2: Crear la prueba de IC de Octo RuboCop](#part-2-creating-the-octo-rubocop-ci-test)", agregarás el código responsable de llevar a cabo la prueba de IC. + +Vamos a crear el método `initiate_check_run` y a actualizar el estado de la ejecución de verificación. Agrega el siguiente código a la sección de ayudantes: + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +``` ruby +# Start the CI process +def initiate_check_run + # Once the check run is created, you'll update the status of the check run + # to 'in_progress' and run the CI process. When the CI finishes, you'll + # update the check run status to 'completed' and add the CI results. + + # Octokit doesn't yet support the Checks API, but it does provide generic + # HTTP methods you can use: + # /rest/reference/checks#update-a-check-run + updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.v3+json', + name: 'Octo RuboCop', + status: 'in_progress', + started_at: Time.now.utc.iso8601 + } + ) + + # ***** RUN A CI TEST ***** + + # Mark the check run as complete! + updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.v3+json', + name: 'Octo RuboCop', + status: 'completed', + conclusion: 'success', + completed_at: Time.now.utc.iso8601 + } + ) +end +``` +{% else %} +``` ruby +# Start the CI process +def initiate_check_run + # Once the check run is created, you'll update the status of the check run + # to 'in_progress' and run the CI process. When the CI finishes, you'll + # update the check run status to 'completed' and add the CI results. + + # Octokit doesn't yet support the Checks API, but it does provide generic + # HTTP methods you can use: + # /rest/reference/checks#update-a-check-run + updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API + name: 'Octo RuboCop', + status: 'in_progress', + started_at: Time.now.utc.iso8601 + } + ) + + # ***** RUN A CI TEST ***** + + # Mark the check run as complete! + updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + # This header is necessary for beta access to Checks API + accept: 'application/vnd.github.antiope-preview+json', + name: 'Octo RuboCop', + status: 'completed', + conclusion: 'success', + completed_at: Time.now.utc.iso8601 + } + ) +end +``` +{% endif %} + +El código anterior llama a la terminal "[Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)" de la API utilizando el [Método HTTP`patch`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para actualizar la ejecución de verificación que ya creaste. + +Te explicamos lo que hace este código. Primero, actualiza el estado de la ejecución de verificación a `in_progress` y configura la hora `started_at` de acuerdo con la hora actual. En la [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) de esta guía de inicio rápido, agregarás el código que lanza una prueba de IC real bajo `***** RUN A CI TEST *****`. Por el momento, dejarás esta sección como un marcador de posición para que el código subsecuente simplemente estimule el éxito del proceso de IC y que todas las pruebas pasen. Por último, el código actualiza el estado de la ejecución de verificación nuevamente como `completed`. + +Notarás en los documentos de "[Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)" que, cuando proporcionas un estado de `completed`, se requieren los parámetros de `conclusion` y `completed_at`. La `conclusion` resume el resultado de una ejecución de verificación, la cual se puede mostrar como `success`, `failure`, `neutral`, `cancelled`, `timed_out`, o `action_required`. Vas a configurar la conclusión como `success`, la hora de `completed_at` según la hora actual, y el estado como `completed`. + +También puedes proporcionar más detalles sobre lo que está haciendo tu verificación, pero eso lo abordaremos en la siguiente sección. Vamos a probar este código nuevamente volviendo a ejecutar `template_server.rb`: + +```shell +$ ruby template_server.rb +``` + +Diríjete a tu solicitud de extracción abierta y da clic en la pestaña **Verificaciones**. Da clic en el botón "Re-ejecutar todo" en la esquina superior derecha. Deberías ver que la ejecución de verificación cambia de `pending` a `in_progress` y termina en `success`: + +![Ejecución de verificación completada](/assets/images/github-apps/github_apps_complete_check_run.png) + +### Parte 2. Crear la prueba de IC de Octo RuboCop + +[RuboCop](https://rubocop.readthedocs.io/en/latest/) es un formateador y limpiador de código para Ruby. Revisa el código de Ruby para garantizar que se apegue a la "[Guía de Estilo de Ruby](https://github.com/rubocop-hq/ruby-style-guide)". RuboCop tiene tres funciones prncipales: + +* Limpiar para revisar el estilo del código +* Formatear el código +* Reemplazar las capacidades de limpieza nativas de Ruby utilizando `ruby -w` + +Ahora que tienes la interface que se ha creado para recibir eventos de la API de verificaciones y para crear ejecuciones de verificción, puedes crear una ejecución de verificación que implemente una prueba de IC. + +Tu app ejecutará RuboCop en el servidor de IC y creará ejecuciones de verificación (en este caso, pruebas de IC) que reporten los resultados que RuboCop reporta a GitHub. + +La API de Verificaciones te permite reportar detalles enriquecidos acerca de cada ejecución de verificación, incluyendo los estados, imágenes, resúmenes, y las acciones solicitadas. + +Las anotaciones son información acerca de líneas de código específicas en un repositorio. Una anotación te permite identificar y visualizar las partes exactas del código para las cuales quieres mostrar información adicional. Esa puede ser cualquier información: por ejemplo, un comentario, un error, o una advertencia. Esta guía rápida utiliza anotaciones para visualizar los errores de RuboCop. + +Para tomar ventaja de las acciones solicitadas, los desarrolladores de apps pueden crear botones en la pestaña de **Verificaciones** de las solicitudes de extracción. Cuando alguien da clic en alguno de estos botones, dicho clic envía un evento de `requested_action` `check_run` a la GitHub App. El desarrollador de la app puede configurar íntegramente la acción que ésta toma. Esta guía de inicio rápido te mostrará cómo agregar un botón que permitirá a los usuarios solicitar que RuboCop corrija los errores que encuentre. RuboCop es compatible con la corrección automática de errores utilizando una opción en la línea de comandos, y configurarás la `requested_action` para aprovechar esta opción. + +¡Comencemos! Estos son los pasos que tendrás que completar en esta sección: + +1. [Agregar un archivo de Ruby](#step-21-adding-a-ruby-file) +1. [Clonar el repositorio](#step-22-cloning-the-repository) +1. [Ejecutar RuboCop](#step-23-running-rubocop) +1. [Recolectar los errores de RuboCop](#step-24-collecting-rubocop-errors) +1. [Actualizar la ejecución de verificación con los resultados de la prueba de IC](#step-25-updating-the-check-run-with-ci-test-results) +1. [Corregir automáticamente los errores de RuboCop](#step-26-automatically-fixing-rubocop-errors) +1. [Tips de seguridad](#step-27-security-tips) + +### Paso 2.1. Agregar un archivo de Ruby + +Puedes pasar archivos específicos o directorios completos para que los revise RuboCop. En esta guía de inicio rápido, ejecutarás a RuboCop en un directorio completo. Ya que RuboCop únicamente revisa el código de Ruby, querrás que por lo menos un archivo de Ruby en tu repositorio contenga errores. El archivo de ejemplo que te proporcionamos a continuación contiene unos cuantos errores. Agrega este ejemplo de archivo de Ruby al repositorio en donde se instaló tu app (asegúrate de nombrar este archivo con una extensión `.rb`, como `myfile.rb`, por ejemplo.): + +```ruby +# The Octocat class tells you about different breeds of Octocat +class Octocat + def initialize(name, *breeds) + # Instance variables + @name = name + @breeds = breeds + end + + def display + breed = @breeds.join("-") + + puts "I am of #{breed} breed, and my name is #{@name}." + end +end + +m = Octocat.new("Mona", "cat", "octopus") +m.display +``` + +### Paso 2.2. Clonar el repositorio + +RuboCop se encuentra disponible como una utilidad de línea de comandos. Eso significa que tu GitHub App necesitará clonar una copia local del repositorio en el servidor de IC para que RuboCop analice los archivos. Para ejecutar las operaciones de Git en tu app de Ruby, puedes usar la gema [ruby-git](https://github.com/ruby-git/ruby-git). + +El `Gemfile` en el repositorio `building-a-checks-api-ci-server` ya incluye la gema ruby-git, y lo instalaste cuando ejecutaste `bundle install` en los [pasos de pre-requisitos](#prerequisites). Para utilizar la gema, agrega este código a la parte superior de tu archivo `template_server.rb`: + +``` ruby +require 'git' +``` + +Tu app necesita el permiso de lectura para "contenido de repositorio" si quieres que clone un repositorio. Más adelante en esta guía de inicio rápido, necesitarás cargar contenido a GitHub, lo cual requiere el permiso de escritura. Continúa y configura el permiso de "contenido de repositorio" de tu app como **Lectura & escritura** ahora mismo para que no tengas que actualizarlo nuevamente más adelante. Para actualizar los permisos de tu app: + +1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. +1. En la sección de "Permisos", encuentra el "contenido del repositorio", y selecciona **Lectura & escritura** en el menú desplegable de "Acceso" que está a un costado. +{% data reusables.apps.accept_new_permissions_steps %} + +Para clonar un repositorio utilizando los permisos de tu GitHub App, puedes utilizar el token de instalación de la misma (`x-access-token:`), el cual se muestra en el siguiente ejemplo: + +```shell +git clone https://x-access-token:@github.com//.git +``` + +El código anterior clona un repositorio a través de HTTP. Éste necesita el nombre íntegro del repositorio, lo cual incluye al propietario del mismo (usuario u organización) y el nombre de éste. Por ejemplo, el repositorio [octocat Hello-World](https://github.com/octocat/Hello-World) tiene un nombre completo que se ve así: `octocat/hello-world`. + +Después de que tu app clone el repositorio, necesita extraer los últimos cambios al código y verificar una ref específica de Git. El código que hará todo esto encajará perfectamente en su propio método. Para llevar a cabo estas operaciones, el método necesita el nombre y nombre completo del repositorio y la ref de salida. La ref puede ser el SHA de una confirmación, una rama, o una etiqueta. Agrega el siguiente método a la sección del método del ayudante en `template_server.rb`: + +``` ruby +# Clones the repository to the current working directory, updates the +# contents using Git pull, and checks out the ref. +# +# full_repo_name - The owner and repo. Ex: octocat/hello-world +# repository - The repository name +# ref - The branch, commit SHA, or tag to check out +def clone_repository(full_repo_name, repository, ref) + @git = Git.clone("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", repository) + pwd = Dir.getwd() + Dir.chdir(repository) + @git.pull + @git.checkout(ref) + Dir.chdir(pwd) +end +``` + +El código anterior utiliza la gema `ruby-git` para clonar el repositorio utilizando el token de instalación de la app. Este código clona el código en el mismo directorio en el que esté `template_server.rb`. Para ejecutar los comandos de Git en el repositorio, el código necesita cambiar el directorio del repositorio. Antes de cambiar de directorio, el código almacena el directorio de trabajo actual en una variable (`pwd`) para recordar a dónde regresar antes de salir del método de `clone_repository`. + +Desde el directorio del repositorio, este código obtiene y fusiona los últimos cambios (`@git.pull`), revisa la ref (`@git.checkout(ref)`), y luego cambia el directorio de vuelta al directorio de trabajo original (`pwd`). + +Ahora tienes un método que clona un repositorio y revisa una ref. A continuación, necesitarás agregar código para obtener los parámetros de entrada requeridos y llamar al nuevo método de `clone_repository`. Agrega el siguiente código debajo del comentario `***** RUN A CI TEST *****` en tu método `initiate_check_run` del ayudante: + +``` ruby +# ***** RUN A CI TEST ***** +full_repo_name = @payload['repository']['full_name'] +repository = @payload['repository']['name'] +head_sha = @payload['check_run']['head_sha'] + +clone_repository(full_repo_name, repository, head_sha) +``` + +El código anterior obtiene el nombre completo del repositorio y el SHA de encabezado de la confirmación desde la carga útil del webhook de `check_run`. + +### Paso 2.3. Ejecutar RuboCop + +¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Ahora te meterás en los detalles más minusciosos del [Limpiador de RuboCop](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) y de las [Anotaciones de la API de Verificaciones](/rest/reference/checks#create-a-check-run). + +El siguiente código ejecuta RuboCop y guarda los errores de estilo en el código con un formato JSON. Agrega el código siguiente debajo de la llamada a `clone_repository` que agregaste en el [paso anterior](#step-22-cloning-the-repository) y sobre el código que actualiza la ejecución de verificación para completarse. + +``` ruby +# Run RuboCop on all files in the repository +@report = `rubocop '#{repository}' --format json` +logger.debug @report +`rm -rf #{repository}` +@output = JSON.parse @report +``` + +Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. Consulta los [Documentos de RuboCop](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) para obtener más detalles y un ejemplo del formato en JSON. + +Ya que este código almacena los resultados de RuboCop en una variable de `@report`, puede eliminar la salida del repositorio con seguridad. Este código también analiza el JSON para que puedas acceder fácilmente a las claves y valores en tu GitHub App utilizando la variable `@output`. + +{% note %} + +**Nota:** El comando que se utiliza para eliminar el repositorio (`rm -rf`) no puede deshacerse. Consulta el [Paso 2.7. Tips de seguridad](#step-27-security-tips) para aprender cómo verificar los webhooks para que no inyecten comandos maliciosos que puedan utilizarse para eliminar un directorio diferente de aquél que tu app busca eliminar. Por ejemplo, si un mal actor envía un webhook con el nombre de repositorio `./`, tu app eliminaría el directorio raíz. 😱 si por alguna razón _no_ estás utilizando el método `verify_webhook_signature` (el cual se incluye en `template_server.rb`) para validar al emisor del webhook, asegúrate de revisar que el nombre del repositorio es válido. + +{% endnote %} + +Puedes probar que este código funcione y ver los errores que reporta RuboCop en la salida de depuración de tu servidor. Inicia el servidor `template_server.rb` nuevamente y crea una solicitud de extracción nueva en el repositorio en donde estás probando tu app: + +```shell +$ ruby template_server.rb +``` + +Deberías ver los errores de limpieza en la salida de depuración, aunque no se imprimen con formato. Puedes utilizar una herramienta web como [JSON formatter](https://jsonformatter.org/) para dar formato a tu salida de JSON como en esta salida de errores de limpieza formateada que tenemos de ejemplo: + +```json +{ + "metadata": { + "rubocop_version": "0.60.0", + "ruby_engine": "ruby", + "ruby_version": "2.3.7", + "ruby_patchlevel": "456", + "ruby_platform": "universal.x86_64-darwin18" + }, + "files": [ + { + "path": "Octocat-breeds/octocat.rb", + "offenses": [ + { + "severity": "convention", + "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.", + "cop_name": "Style/StringLiterals", + "corrected": false, + "location": { + "start_line": 17, + "start_column": 17, + "last_line": 17, + "last_column": 22, + "length": 6, + "line": 17, + "column": 17 + } + }, + { + "severity": "convention", + "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.", + "cop_name": "Style/StringLiterals", + "corrected": false, + "location": { + "start_line": 17, + "start_column": 25, + "last_line": 17, + "last_column": 29, + "length": 5, + "line": 17, + "column": 25 + } + } + ] + } + ], + "summary": { + "offense_count": 2, + "target_file_count": 1, + "inspected_file_count": 1 + } +} +``` + +### Paso 2.4. Recolectar los errores de RuboCop + +La variable `@output` contiene los resultados analizados de JSON para el reporte de RuboCop. Tal como se muestra anteriormente, los resultados contienen una sección de `summary` que tu código puede ut utilizar rápidamente para determinar si hay algún error. El siguiente código configurará la ejecución de verificación en `success` cuando no se reporten errores. RuboCop reporta errores para cada archivo en la matriz de `files`, así que, si hay errores, necesitarás extraer algunos datos del objeto del archivo. + +La API de Verificaciones te permite crear anotaciones para líneas de código específicas. Cuando creas o actualizas una ejecución de verificación, puedes agregar anotaciones. En esta guía de inicio rápido estás [actualizando la ejecución de verificación](/rest/reference/checks#update-a-check-run) con anotaciones. + +La API de Verificaciones limita la cantidad de anotaciones a un máximo de 50 por solilcitud de API. Para crear más de 50 anotaciones, tienes que hacer solicitudes múltiples a la terminal [Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run). Por ejemplo, para crear 105 anotaciones necesitarías llamar a la terminal [Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run) tres veces. Las primeras dos contarían por 50 anotaciones cada una, y la tercera incluiría las cinco restantes. Cada vez que actualices la ejecución de verificación, se adjuntan las anotaciones a la lista de anotaciones existente para la ejecución de verificación. + +Una ejecución de verificación espera encontrar las anotaciones en una matriz de objetos. Cada objeto de anotación debe incluir `path`, `start_line`, `end_line`, `annotation_level`, y `message`. RuboCop también proporciona la `start_column` y `end_column`, para que puedas incluir estos parámetros opcionales en la anotación. Las anotaciones únicamente son compatibles con `start_column` y `end_column` en la misma línea. Consulta la documentación de referencia del [objeto de `anotaciones`](/rest/reference/checks#annotations-object-1) para obtener más detalles. + +Extraerás la información requerida de RuboCop que necesites para crear cada anotación. Adjunta el siguiente código a aquél que agregaste en la [sección anterior](#step-23-running-rubocop): + +``` ruby +annotations = [] +# You can create a maximum of 50 annotations per request to the Checks +# API. To add more than 50 annotations, use the "Update a check run" API +# endpoint. This example code limits the number of annotations to 50. +# See /rest/reference/checks#update-a-check-run +# for details. +max_annotations = 50 + +# RuboCop reports the number of errors found in "offense_count" +if @output['summary']['offense_count'] == 0 + conclusion = 'success' +else + conclusion = 'neutral' + @output['files'].each do |file| + + # Only parse offenses for files in this app's repository + file_path = file['path'].gsub(/#{repository}\//,'') + annotation_level = 'notice' + + # Parse each offense to get details and location + file['offenses'].each do |offense| + # Limit the number of annotations to 50 + next if max_annotations == 0 + max_annotations -= 1 + + start_line = offense['location']['start_line'] + end_line = offense['location']['last_line'] + start_column = offense['location']['start_column'] + end_column = offense['location']['last_column'] + message = offense['message'] + + # Create a new annotation for each error + annotation = { + path: file_path, + start_line: start_line, + end_line: end_line, + start_column: start_column, + end_column: end_column, + annotation_level: annotation_level, + message: message + } + # Annotations only support start and end columns on the same line + if start_line == end_line + annotation.merge({start_column: start_column, end_column: end_column}) + end + + annotations.push(annotation) + end + end +end +``` + +Este código limita la cantidad total de anotaciones a 50. Pero puedes modificarlo para actualizar la ejecución de verificación para cada lote de 50 anotaciones. El código anterior incluye la variable `max_annotations` que configura el límite a 50, el cual se utiliza en el bucle que itera a través de las faltas. + +Cuando la `offense_count` es de cero, la prueba de IC se muestra como `success`. Si hay errores, este código configura la conclusión como `neutral` para prevenir los errores estrictamente implementados desde los limpiadores de código. Pero puedes cambiar la conclusión a `failure` si quisieras garantizar que el conjunto de verificaciones falle cuando existan errores de limpieza. + +Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. Puedes incluso ir más allá y especificar ls niveles de advertencia para cada tipo de [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), pero para simplificar todo aún más en esta guía rápida, todos los errores se configurarán en un nivel de `notice`. + +Este código también itera a través de cada error en la matriz de `offenses` y recolecta la ubicación de la falta y el mensaje de error. Después de extraer la información requerida, el código crea una anotación para cada error y lo almacena en la matriz de `annotations`. Ya que las anotaciones solo son compatibles con las columnas de inicio y fin en la misma línea, `start_column` y `end_column` se agregarán únicamente al objeto `annotation` si los valores iniciales y finales de la línea son los mismos. + +Este código aún no crea una anotación para la ejecución de verificación. Agregarás dicho código en la siguiente sección. + +### Paso 2.5. Actualizar la ejecución de verificación con los resultados de la prueba de IC + +Cada ejecución de verificación de GitHub contiene un objeto de `output` que incluye un `title`, `summary`, `text`, `annotations`, y `images`. El `summary` y `title` son los únicos parámetros requeridos para la `output`, pero no ofrecen muchos detalles por sí mismos, así que esta guía de inicio rápido agrega `text` y `annotations` también. Este código no agrega una imagen, pero ¡no dudes en agregarla si así lo deseas! + +Para el `summary`, este ejemplo utiliza la información de resumen de RuboCop y agrega algunas líneas nuevas (`\n`) para formatear la salida. Puedes personalizar lo que agregas en el parámetro de `text`, pero este ejemplo configura el parámetro `text` en la versión de RuboCop. Para configurar tanto `summary` como `text`, adjunta este código a aquél que agregaste en la [sección anterior](#step-24-collecting-rubocop-errors): + +``` ruby +# Updated check run summary and text parameters +summary = "Octo RuboCop summary\n-Offense count: #{@output['summary']['offense_count']}\n-File count: #{@output['summary']['target_file_count']}\n-Target file count: #{@output['summary']['inspected_file_count']}" +text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}" +``` + +Ahora tienes toda la información que necesitas para actualizar tu ejecución de verificación. En la [primera parte de esta guía de inicio rápido](#step-14-updating-a-check-run), agregaste este código para configurar el estado de la ejecución de verificación como `success`: + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +``` ruby +# Mark the check run as complete! +updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.v3+json', + name: 'Octo RuboCop', + status: 'completed', + conclusion: 'success', + completed_at: Time.now.utc.iso8601 + } +) +``` +{% else %} +``` ruby +# Mark the check run as complete! +updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API + name: 'Octo RuboCop', + status: 'completed', + conclusion: 'success', + completed_at: Time.now.utc.iso8601 + } +) +``` +{% endif %} + +Necesitarás actualizar este código para utilizar la variable `conclusion` que configures con base en los resultados de RuboCop (ya sea como `success` o como `neutral`). Puedes actualizar el código con lo siguiente: + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +``` ruby +# Mark the check run as complete! And if there are warnings, share them. +updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.v3+json', + name: 'Octo RuboCop', + status: 'completed', + conclusion: conclusion, + completed_at: Time.now.utc.iso8601, + output: { + title: 'Octo RuboCop', + summary: summary, + text: text, + annotations: annotations + }, + actions: [{ + label: 'Fix this', + description: 'Automatically fix all linter notices.', + identifier: 'fix_rubocop_notices' + }] + } +) +``` +{% else %} +``` ruby +# Mark the check run as complete! And if there are warnings, share them. +updated_check_run = @installation_client.patch( + "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", + { + accept: 'application/vnd.github.antiope-preview+json', + name: 'Octo RuboCop', + status: 'completed', + conclusion: conclusion, + completed_at: Time.now.utc.iso8601, + output: { + title: 'Octo RuboCop', + summary: summary, + text: text, + annotations: annotations + }, + actions: [{ + label: 'Fix this', + description: 'Automatically fix all linter notices.', + identifier: 'fix_rubocop_notices' + }] + } +) +``` +{% endif %} + +Ahora que estás configurando una conclusión con base en el estado de la prueba de IC y has agregado la salida de los resultados de RuboCop, ¡has creado una prueba de IC! Felicidades. 🙌 + +El código anterior también agrega una característica a tu servidor de IC, la cual se llama [acciones solicitadas](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) a través del objeto `actions`. {% if currentVersion == "free-pro-team@latest" %}(Nota que esto no está relacionado con las [GitHub Actions](/actions).) {% endif %}Las acciones que se solicitan agregan un botón en la pestaña **Verificaciones** en GitHub que permite a las personas solicitar que la ejecución de verificación tome acciones adicionales. Tu app puede configurar la acción adicional en su totalidd. Por ejemplo, ya que RuboCop tiene una característica para corregir automáticamente los errores que encuentre en el código de Ruby, tu servidor de IC puede utilizar un botón de acciones solicitadas para ayudar a que las personas soliciten correcciónes de errores automáticas. Cuando alguien da clic en el botón, la app recibe el evento de `check_run` con una acción de `requested_action`. Cada acción solicitada tiene un `identifier` que la app utiliza para determinar en qué botón se dio clic. + +El código anterior aún no hace que RuboCop corrija los errores automáticamente. Eso lo agregarás en la siguiente sección. Pero primero, observa la prueba de IC que acabas de crear iniciando nuevamente el servidor `template_server.rb` y creando una nueva solicitud de extracción: + +```shell +$ ruby template_server.rb +``` + +Las anotaciones se mostrarán en la pestaña de **Verificaciones**. + +![Anotaciones de la ejecución de verificación en la pestaña de verificaciones](/assets/images/github-apps/github_apps_checks_annotations.png) + +Nota el botón de "Arreglar esto" que creaste al agregar la acción solicitada. + +![Botón de acción solicitada para la ejecución de verificación](/assets/images/github-apps/github_apps_checks_fix_this_button.png) + +Si las anotaciones se relacionan con un archivo que ya se incluya en la solicitud de extracción, estas también se mostrarán en la pestaña de **Archivos cambiados**. + +![Anotaciones de la ejecución de verificación en la pestaña de archivos cambiados](/assets/images/github-apps/github_apps_checks_annotation_diff.png) + +### Paso 2.6. Corregir automáticamente los errores de RuboCop + +Si has llegado hasta aquí, ¡excelente! 👏 Ya creaste una prueba de IC. En esta sección vas a agregar una característica más que utiliza a RuboCop para corregir automáticamente los errores que encuentre. Ya agregaste el botón de "Corregir esto" en la [sección anterior](#step-25-updating-the-check-run-with-ci-test-results). Ahora agregarás el código para gestionar el evento de ejecución de verificación `requested_action` que se activa cuando alguien da clic en dicho botón. + +La herramienta de RuboCop [ofrece](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) la opción de línea de comandos `--auto-correct` para corregir automáticamente los errores que encuentre. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia. + +Para cargar un repositorio, tu app debe tener permisos de escritura para "contenido de repositorio". Estos permisos los configuraste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) como **Lectura & escritura**, así que estás listo. + +Para confirmar los archivos, Git debe saber qué [nombre de usuario](/articles/setting-your-username-in-git/) y [correo electrónico](/articles/setting-your-commit-email-address-in-git/) asociará con la confirmación. Agrega dos variables de ambiente adicionales en tu archivo `.env` para almacenar las configuraciones de nombre(`GITHUB_APP_USER_NAME`) y de correo electrónico (`GITHUB_APP_USER_EMAIL`). Tu nombre puede ser aquél de tu app y la dirección de correo electrónico puede ser cualquiera para este ejemplo. Por ejemplo: + +``` +GITHUB_APP_USER_NAME=Octoapp +GITHUB_APP_USER_EMAIL=octoapp@octo-org.com +``` + +Ya que hayas actualizado tu archivo `.env` con el nombre y correo electrónico del autor y del confirmante, estarás listo para agregar código para que lea las variables de ambiente y configur los ajustes de Git. Pronto agregarás este código. + +Cuando alguien da clic en el botón "Arreglar esto", tu app recibe el [webhook de ejecución de verificación](/webhooks/event-payloads/#check_run) con el tipo de acción `requested_action`. + +En el [Paso 1.4. Actualizar una ejecución de verificación](#step-14-updating-a-check-run) actualizaste tu `event_handler` para que gestionara la búsqueda de acciones en el evento `check_run`. Ya tienes una declaración de caso para gestionar los tipos de acción `created` y `rerequested`: + +``` ruby +when 'check_run' + # Check that the event is being sent to this app + if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER + case @payload['action'] + when 'created' + initiate_check_run + when 'rerequested' + create_check_run + end +end +``` + +Agrega otra declaración de `when` después del caso `rerequested` para gestionar el evento `rerequested_action`: + +``` ruby +when 'requested_action' + take_requested_action +``` + +Este código llamará aun método nuevo que gestionará todos los eventos `requested_action` para tu app. Agrega el siguiente método a la sección de métodos del ayudante para tu código: + +``` ruby +# Handles the check run `requested_action` event +# See /webhooks/event-payloads/#check_run +def take_requested_action + full_repo_name = @payload['repository']['full_name'] + repository = @payload['repository']['name'] + head_branch = @payload['check_run']['check_suite']['head_branch'] + + if (@payload['requested_action']['identifier'] == 'fix_rubocop_notices') + clone_repository(full_repo_name, repository, head_branch) + + # Sets your commit username and email address + @git.config('user.name', ENV['GITHUB_APP_USER_NAME']) + @git.config('user.email', ENV['GITHUB_APP_USER_EMAIL']) + + # Automatically correct RuboCop style errors + @report = `rubocop '#{repository}/*' --format json --auto-correct` + + pwd = Dir.getwd() + Dir.chdir(repository) + begin + @git.commit_all('Automatically fix Octo RuboCop notices.') + @git.push("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", head_branch) + rescue + # Nothing to commit! + puts 'Nothing to commit' + end + Dir.chdir(pwd) + `rm -rf '#{repository}'` + end +end +``` + +El código anterior clona un repositorio tal como aquél que agregaste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository). Una declaración de tipo `if` revisará que el identificación de la acción solicitada empate con el identificador del botón de RuboCop (`fix_rubocop_notices`). Cuando empaten, el código clonará el repositorio, configurará el correo electrónico y nombre de usuario de Git, y ejecutará RuboCop con la opción `--auto-correct`. La opción `--auto-correct` aplica los cambios a los archivos locales del servidor de IC automáticamente. + +Los archivos se cambian de manera local, pero aún necesitarás cargarlos a GitHub. Utilizarás la gema útil `ruby-git` nuevamente para confirmar todos los archivos. Git tiene un comando único que organiza todos los archivos que se han modificado o borrado y los confirma: `git commit -a`. Para hacerlo lo mismo utilizando `ruby-git`, el código anterior utiliza el método `commit_all`. Después, el código carga los archivos confirmados a GitHub utilizando el token de instalación y utilizando el mismo método de autenticación que el comando `clone` de Git. Por último, elimina el directorio del repositorio para garantizar que el directorio de trabajo está preparado para el siguiente evento. + +¡Listo! El código que escribiste ahora completa tu servidor de IC para la API de Verificaciones. 💪 Reinicia nuevamente tu servidor de `template_server.rb` y crea una solicitud de extracción nueva: + +```shell +$ ruby template_server.rb +``` + +{% data reusables.apps.sinatra_restart_instructions %} + +Esta vez, da clic en el botón "Arreglar esto" para corregir automáticamente los errores que RuboCop encontró desde la pestaña de **Verificaciones**. + +En la pestaña de **Confirmaciones** encontrarás una confirmación nueva con el nombre de usuario que configuraste en los ajustes de Git. Puede que necesites actualizar tu buscador para ver esto. + +![Una confirmación nueva para corregir los avisos de Octo RuboCop automáticamente](/assets/images/github-apps/github_apps_new_requested_action_commit.png) + +Ya que se cargó una confirmación nueva al repositorio, verás un conjunto de verificaciones nuevo para Octo RuboCop en la pestaña de **Verificaciones**. Pero esta vez no habrá errores, ya que RuboCop los arregló todos. 🎉 + +![Sin errores en los conjuntos de verificaciones o en la ejecución de verificación](/assets/images/github-apps/github_apps_checks_api_success.png) + +Puedes encontrar todo el código de la app que acabas de crear en el archivo `server.rb` dentro del repositorio [Crear pruebas de IC con la API de Verificaciones](https://github.com/github-developer/creating-ci-tests-with-the-checks-api). + +### Paso 2.7. Tips de seguridad + +El código de la plantilla de la GitHub App ya tiene un método para verificar las cargas útiles de webhook entrantes para garantizar que vengan de una fuente confiable. Si no estás validando las cargas útiles de los webhooks, necesitarás garantizar que, cuando los nombres de repositorio se incluyan en éstas, el webhook no contenga comandos arbitrarios que puedan usarse con malas intenciones. El siguiente código valida que el nombre del repositorio solo contenga caracteres alfabeticos latinos, guiones y guiones bajos. Para proporcionarte un ejemplo completo, el código integral de `server.rb` que encuentras disponible en el [repositorio acompañante](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) para esta guía de inicio rápido incluye tanto el método para validar las cargas útiles de webhooks entrantes como esta verificación que revisa el nombre del repositorio. + +``` ruby +# This quickstart example uses the repository name in the webhook with +# command-line utilities. For security reasons, you should validate the +# repository name to ensure that a bad actor isn't attempting to execute +# arbitrary commands or inject false repository names. If a repository name +# is provided in the webhook, validate that it consists only of latin +# alphabetic characters, `-`, and `_`. +unless @payload['repository'].nil? + halt 400 if (@payload['repository']['name'] =~ /[0-9A-Za-z\-\_]+/).nil? +end +``` + +### Solución de problemas + +Aquí te presentamos algunos problemas comunes y sus soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejos en el {% data variables.product.prodname_support_forum_with_url %}. + +* **P:** Mi app no está cargando código a GitHub. !No veo las correcciones que RuboCop hace automáticamente! + + **A:** Asegúrate de tener permisos de **Lectura & escritura** para el "contenido del repositorio", y que estés clonando el repositorio con tu token de instalación. Consulta el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) para encontrar más detalles. + +* **P:** Veo un error en la salida de depuración `template_server.rb` relacionada con el clonado de mi repositorio. + + **R:** Si ves el siguiente error, no has borrado la salida del repositorio en uno o ambos de los métodos de `initiate_check_run` o `take_requested_action`: + + ```shell + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:v1.9b2080277016f797074c4debd350745f4257f8dd@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: + ``` + + Compara tu código con el archivo `server.rb` para garantizar que tienes el mismo código en tus métodos de `initiate_check_run` y de `take_requested_action`. + +* **P:** Las ejecuciones de verificación no se están mostrando en la pestaña de "Verificaciones" en GitHub. + + **R:** Reinicia Smee y vuelve a ejecutar tu servidor de `template_server.rb`. + +* **P:** No veo el botón de "Re-ejecutar todo" en la pestaña de "Verificaciones" de GitHub. + + **R:** Reinicia Smee y vuelve a ejecutar tu servidor de `template_server.rb`. + +### Conclusión + +Después de seguir esta guía, ¡aprendiste los puntos básicos de utilizar la API de Verificaciones para crear un servidor de IC! Para revisar todo, debes: + +* Configuraste tu servidor para recibir eventos de la API de Verificaciones y creaste ejecuciones de verificación. +* Utilizaste RuboCop para verificar el código en los repositorios y creaste anotaciones para los errores. +* Iplementaste una accion solicitada que corrijió automáticamente los errores de limpieza. + +### Pasos siguientes + +Aquí tienes algunas ideas para lo que puedes hacer después: + +* Actualmente, el botón "Arreglar esto" siempre se muestra. Actualiza el código que escribiste para que muestre el botón de "Arreglar esto" únicamente cuando RuboCop encuentre errores. +* Si prefieres que RuboCop no confirme archivos directamente en la rama principal, puedes actualizar el código a [crear una solicitud de extracción](/rest/reference/pulls#create-a-pull-request) con una rama nueva basada en la rama principal. diff --git a/translations/es-ES/content/developers/apps/deleting-a-github-app.md b/translations/es-ES/content/developers/apps/deleting-a-github-app.md new file mode 100644 index 0000000000000..e60860c3043bb --- /dev/null +++ b/translations/es-ES/content/developers/apps/deleting-a-github-app.md @@ -0,0 +1,20 @@ +--- +title: Borrar una GitHub App +intro: '{% data reusables.shortdesc.deleting_github_apps %}' +redirect_from: + - /apps/building-integrations/managing-github-apps/deleting-a-github-app/ + - /apps/managing-github-apps/deleting-a-github-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Selecciona la GitHub App que quieres borrar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +{% data reusables.user-settings.github_apps_advanced %} +6. Da clic en **Borrar GitHub App**. ![Botón para borrar una GitHub App](/assets/images/github-apps/github_apps_delete.png) +7. Teclea e nombre de la GitHub App para confirmar que la quieres borrar. ![Campo para confirmar el nombre de la GitHub App que quieres borrar](/assets/images/github-apps/github_apps_delete_integration_name.png) +8. Da clic en **Entiendo las consecuencias, borrar esta GitHub App**. ![Botón para confirmar el borrado de tu GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png) diff --git a/translations/es-ES/content/developers/apps/deleting-an-oauth-app.md b/translations/es-ES/content/developers/apps/deleting-an-oauth-app.md new file mode 100644 index 0000000000000..2a14be6430024 --- /dev/null +++ b/translations/es-ES/content/developers/apps/deleting-an-oauth-app.md @@ -0,0 +1,18 @@ +--- +title: Borrar una App de OAuth +intro: '{% data reusables.shortdesc.deleting_oauth_apps %}' +redirect_from: + - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app/ + - /apps/managing-oauth-apps/deleting-an-oauth-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +4. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) +5. Da clic en **Borrar aplicación**. ![Botón para borrar la aplicación](/assets/images/oauth-apps/oauth_apps_delete_application.png) +6. Da clic en **Borrar esta aplicación de OAuth**. ![Botón para confirmar el borrado](/assets/images/oauth-apps/oauth_apps_delete_confirm.png) diff --git a/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md new file mode 100644 index 0000000000000..19f1ebd1512fd --- /dev/null +++ b/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -0,0 +1,107 @@ +--- +title: Diferencias entre GitHub Apps y Apps de OAuth +intro: 'El entender las diferencias entre {% data variables.product.prodname_github_app %} y {% data variables.product.prodname_oauth_app %} te ayudará a decidir qué app quieres crear. Una {% data variables.product.prodname_oauth_app %} actúa como un usuario de Github, mientras que una {% data variables.product.prodname_github_app %} utiliza su propia identidad cuando se instala en una organización o en repositorios dentro de una organización.' +redirect_from: + - /early-access/integrations/integrations-vs-oauth-applications/ + - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ + - /apps/differences-between-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### ¿Quién puede instalar GitHub Apps y autorizar Apps de OAuth? + +Puedes instalar GitHub Apps en tu cuenta personal o en las organizaciones que te pertenezcan. Si tienes permisos administrativos en un repositorio, puedes instalar GitHub Apps en las cuentas de la organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. + +{% data reusables.apps.app_manager_role %} + +Por el contrario, los usuarios _autorizan_ las Apps de OAuth, lo cual otorga a estas apps la capacidad de actuar como un usuario autenticado. Por ejemplo, puedes autorizar una App de OAuth que encuentre todas las notificaciones para el usuario autenticado. Siempre puedes retirar los permisos de las Apps de OAuth. + +{% data reusables.apps.deletes_ssh_keys %} + +| GitHub Apps | OAuth Apps | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para instalar una GitHub App en una organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos. | +| Puedes instalar una GitHu App en tu repositorio personal. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos. | +| Debes ser un propietario de la organización, propietario del repositorio personal, o tener permisos administrativos en un repositorio para desinstalar una GitHub App y eliminar su acceso. | Puedes borrar un token de acceso de OAuth para eliminar el acceso. | +| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para solicitar la instalación de una GitHub App. | Si está activa una política de aplicación organizacional, cualquier miembro de la organización puede solicitar la instalación de una App de OAuth en dicha organización. Un propietario de la organización deberá aprobar o negar la solicitud. | + +### ¿A qué recursos pueden acceder las GitHub Apps y las Apps de OAuth? + +Los propietarios de las cuentas pueden utilizar una {% data variables.product.prodname_github_app %} en una cuenta sin otorgarle acceso a otra cuenta. Por ejemplo, puedes instalar un servicio de compilación de terceros en la organización de tu patrón laboral, pero puedes decidir no otorgar a esa compilación acceso de servicio a los repositorios en tu cuenta personal. Una GitHub App permanece instalada si la persona que la configuró deja a la organización. + +Una App de OAuth _autorizada_ tiene acceso a todos los recursos que son accesibles para el usuario o el propietario de la organización. + +| GitHub Apps | OAuth Apps | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Instalar la GitHub App le otorga acceso a la misma en los repositorios elegidos de la cuenta de usuario o de organización. | Autorizar una App de OAuth otorga a dicha app acceso a los recursos que puede acceder el usuario. Por ejemplo, a los repositorios que puede acceder. | +| El token de instalación de una GitHub App pierde acceso a los recursos si un administrador elimina los repositorios de la instalación. | Un token de acceso de OAuth pierde acceso a los recursos cuando el usuario mismo pierde acceso a ellos, como cuando pierden el acceso de escritura a un repositorio. | +| Los tokens de acceso de la instalación se limitan a los repositorios especificados con los permisos que escogió el creador de la app. | Un token de acceso de OAuth se limita por alcances. | +| Las GitHub Apps pueden solicitar acceso por separado a los informes de problemas y a las solicitudes de extracción sin acceder al contenido real del repositorio. | Las Apps de OAuth necesitan solicitar el alcance de `repo` para obtener acceso a los informes de problemas, solicitudes de extracción, o a cualquier recurso que pertenezca al repositorio. | +| Las GitHub Apps no están sujetas a las políticas de aplicación de la organización. Una GitHub app solo tendrá acceso a los repositorios que haya otorgado el propietario de una organización. | Si una política de aplicación de la organización se encuentra activa, únicamente el propietario de la organización podrá autorizar la instalación de una App de OAuth. Si se instala, la App de OAuth obtiene acceso a todo lo que esté visible para el token que tiene el propietario de la organización dentro de la organización aprobada. | +| Las GitHub Apps reciben un evento de webhook cuando se cambia o elimina una instalación. Esto indica al creador de la app cuando han recibido más o menos accesos a los recursos organizacionales. | Las Apps de OAuth pueden perder el acceso a una organización o a un repositorio en cualquier momento con base en acceso cambiante del usuario que otorga los permisos. La App de OAuth no te informará cuando pierde el acceso a un recurso. | + +### Identificación basada en tokens + +{% note %} + +**Nota:** Las GitHub Apps también pueden utilizar un token basado en un usuario. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". + +{% endnote %} + +| GitHub Apps | OAuth Apps | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Una GitHub App puede solicitar un token de acceso de la instalación si utiilza una llave privada con un formato de token web de JSON fuera de banda. | Una App de OAuth puede intercambiar un token de solicitud por un token de acceso después de una redirección a través de una solicitud web. | +| Un token de instalación identifica a la app como el bot de las GitHub Apps, tal como el @jenkins-bot. | Un token de acceso identifica a la app como el usuario que otorgó el token para la app, tal como el @octocat. | +| Los tokens de instalación caducan después de un tiempo predefinido (actualmente, 1 hora). | Los tokens de OAuth permanecen activos hasta que el cliente los revoque. | +| {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Aplicarán límites de tasa más altos para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Límites de tasa para las GitHub Apps](/developers/apps/rate-limits-for-github-apps)".{% endif %} | Los tokens de OAuth utilizan el límite de tasa del usuario de 5,000 solicitudes por hora. | +| Pueden otorgarse incrementos en el límite de tasa tanto a nivel de las GitHub Apps (lo cual afecta a todas las instalaciones) como a nivel de la instalación individual. | Los incrementos en el límite de tasa se otorgan por cada App de OAuth. Cada token que se otorgue a esa App de OAuth obtiene el límite incrementado. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| Las {% data variables.product.prodname_github_app %} pueden autenticarse a nombre del usuario y a esto se le llama solicitudes de usuario a servidor. El flujo para autorizaciones es el mismo que aquél de las autorizaciones para las apps de OAuth. Los tokens de usuario a servidor pueden caducar y renovarse con un token de actualización. Para obtener más información, consulta las secciones "[Actualizar un token de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" y "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | El flujo de OAuth que utilizan las {% data variables.product.prodname_oauth_app %} autoriza a una {% data variables.product.prodname_oauth_app %} a nombre del usuario. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. |{% endif %} + +### Solicitar niveles de permiso para recursos + +A diferencia de las apps de OAuth, las GitHub Apps tiene permisos específicos que les permiten solicitar acceso únicamente a lo que necesitan. Por ejemplo, una GitHub App de Integración Continua (IC) puede solicitar acceso de lectura al contenido del repositorio y acceso de escritura la API de estado. Puede que alguna otra GitHub App no tenga acceso de escritura o lectura al código, pero aún podrá administrar propuestas, etiquetas e hitos. Las Apps de OAuth no pueden utilizar permisos granulares. + +| Acceso | GitHub Apps (permisos de `read` o `write`) | OAuth Apps | +| --------------------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------- | +| **Para acceder a los repositorios públicos** | El repositorio público necesita elegirse durante la instalación. | alcance `public_repo`. | +| **Para acceder al código/contenido del repositorio** | Contenidos del repositorio | alcance `repo`. | +| **Para acceder a propuestas, etiquetas e hitos** | Problemas | alcance `repo`. | +| **Para acceder a solicitudes de extracción, etiquetas e hitos** | Solicitudes de cambios | alcance `repo`. | +| **Para acceder a estados de confirmación (para compilaciones de IC)** | Estados de confirmación | alcance `repo:status`. | +| **Para acceder a los despliegues y estados de despliegue** | Implementaciones | alcance `repo_deployment`. | +| **Para recibir eventos a través de un webhook** | Las GitHub Apps incluyen un webhook predeterminadamente. | alcance `write:repo_hook` o `write:org_hook`. | + +### Descubrimiento de repositorios + +| GitHub Apps | OAuth Apps | +| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Las GitHub Apps pueden ver a `/installation/repositories` para encontrar repositorios a los que puede acceder la instalación. | Las Apps de OAuth pueden ver a `/user/repos` para tener una vista de tipo usuario o a `/orgs/:org/repos` para tener una de tipo organización para los repositorios accesibles. | +| Las Github Apps reciben webhooks cuando los repositorios se agregan o eliminan de la instalación. | Las Apps de OAuth crean webhooks de organización para las notificaciones cuando se crea un repositorio nuevo dentro de una organización. | + +### Webhooks + +| GitHub Apps | OAuth Apps | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Predeterminadamente, las GitHub Apps tienen un solo webhook que recibe los eventos que se les ha configurado para recibir para cada repositorio al que tengan acceso. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. | +| Las GitHub Apps reciben algunos eventos a nivel organizacional con el permiso del miembro de la organización. | Las Apps de OAuth solicitan el alcance de webhook de la organización para crear un webhook de organización para cada organización de la cual necesiten recibir eventos de nivel organizacional. | + +### Acceso a Git + +| GitHub Apps | OAuth Apps | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Las GitHub Apps solicitan permiso a los contenidos del repositorio y utilizan tu token de instalación para autenticarte a través de [Git basado en HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Las Apps de OAuth piden el alcance `write:public_key` y [Crean una llave de despliegue](/rest/reference/repos#create-a-deploy-key) a través de la API. Entonces puedes utilizar esa llave para ejecutar comandos de Git. | +| El token se utiliza como la contraseña HTTP. | El token se utiliza como el nombre de usuario HTTP. | + +### Cuentas de máquina vs cuentas de bot + +Las cuentas de usuario de máquina son cuentas de usuario basadas en OAuth que segregan sistemas automatizados utilizando el sistema de usuarios de GitHub. + +Las cuentas de bot son específicas para las GitHub Apps y se crean en cada GitHub App. + +| GitHub Apps | OAuth Apps | +| ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | +| Los bots de las GitHub Apps no consumen una plaza de {% data variables.product.prodname_enterprise %}. | Una cuenta de usuario de máquina consume una plaza de {% data variables.product.prodname_enterprise %}. | +| Ya que jamás se otorga una contraseña a un bot de una GitHub App, un cliente no podrá iniciar sesión directamente en él. | Una cuenta de usuario de máquina obtiene un nombre de usuario y contraseña para que el cliente lo administre y asegure. | diff --git a/translations/es-ES/content/developers/apps/editing-a-github-apps-permissions.md b/translations/es-ES/content/developers/apps/editing-a-github-apps-permissions.md new file mode 100644 index 0000000000000..eb195652864fa --- /dev/null +++ b/translations/es-ES/content/developers/apps/editing-a-github-apps-permissions.md @@ -0,0 +1,27 @@ +--- +title: Editar los permisos de una GitHub App +intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}' +redirect_from: + - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions/ + - /apps/managing-github-apps/editing-a-github-app-s-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Los permisos actualizados no tendrán efecto en una instalación hasta que el propietario de la cuenta o de la organización apruebe los cambios. Puedes utilizar el [Webhook de eventos de la instalación](/webhooks/event-payloads/#installation) para saber cuando las personas acepten nuevos permisos para tu app. Una excepción son los [permisos a nivel de usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), los cuales no requieren que un propietario de la cuenta apruebe los cambios a los permisos. + +{% endnote %} + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Selecciona la GitHub App de la cual quieras cambiar los permisos. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +5. En la barra lateral izquierda, haz clic en **Permissions & webhooks** (Permisos y webhooks). ![Permisos y webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png) +6. Modifica los permisos que te gustaría cambiar. Para cada tipo de permisos, selecciona ya sea "únicamente lectura", "Lectura & escritura", o "Sin acceso" del menú desplegable. ![Selecciones de permisos para tu GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png) +7. En "suscribirse a los eventos", selecciona cualquier evento al que quieras suscribir a tu app. ![Selecciones de permisos para suscribir tu GitHub App a los eventos](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png) +8. Opcionalmente, en "agregar una nota para los usuarios", agrega una nota que indique a tus usuarios el por qué estás cambiando los permisos que solicita tu GitHub App. ![Caja de entrada para agregar una nota para los usuarios, la cual explique por qué cambiaron los permisos de tu GitHub App](/assets/images/github-apps/github_apps_permissions_note_to_users.png) +9. Haz clic en **Guardar cambios**. ![Botón para guardar los cambios en los permisos](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps.md new file mode 100644 index 0000000000000..ccf0d4055dd33 --- /dev/null +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps.md @@ -0,0 +1,10 @@ +--- +title: Comenzar con las apps +intro: Aprende cómo crear apps y como configurar tu ambiente de desarrollo. +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/guides.md b/translations/es-ES/content/developers/apps/guides.md new file mode 100644 index 0000000000000..04399979ee33b --- /dev/null +++ b/translations/es-ES/content/developers/apps/guides.md @@ -0,0 +1,12 @@ +--- +title: Guías +intro: 'Aprende cómo utilizar la API de {% data variables.product.prodname_dotcom %} con tu app, integración continua, y cómo compilar con las apps.' +mapTopic: verdadero +redirect_from: + - /apps/quickstart-guides +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md new file mode 100644 index 0000000000000..bd59f982c9644 --- /dev/null +++ b/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -0,0 +1,933 @@ +--- +title: Identificar y autorizar usuarios para las GitHub Apps +intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' +redirect_from: + - /early-access/integrations/user-identification-authorization/ + - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps/ + - /apps/building-github-apps/identifying-and-authorizing-users-for-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +{% data reusables.pre-release-program.expiring-user-access-tokens-beta %} + +Cuando tu GitHub App actúe en nombre de un usuario, ésta realiza solicitudes de usuario a servidor. Estas solicitudes deben autorizarse con un token de acceso de usuario. Las solicitudes de usuario a servidor incluyen el solicitar datos para un usuario, como el determinar qué repositorios mostrar a un usuario en particular. Estas solicitudes también incluyen las acciones que activa un usuario, como ejecutar una compilación. + +{% data reusables.apps.expiring_user_authorization_tokens %} + +### Identificar usuarios en tu sitio + +Para autorizar a los usuarios para las apps estándar que se ejecutan en el buscador, utiliza el [flujo de aplicaciones web](#web-application-flow). + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +Para autorizar a los usuarios para apps sin interfaz gráfica sin acceso directo al buscador, tales como las herramientas de CLI o administradores de credenciales de Git, utiliza el [flujo del dispositivo](#device-flow). El flujo de dispositivos utiliza el [Otorgamiento de Autorizción de Dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0. +{% endif %} + +### Flujo de aplicaciones Web + +Al utilizar el flujo de aplicaciones web, el proceso para identificar a los usuarios en tu sitio es: + +1. Se redirecciona a los usuarios para solicitar su identidad de GitHub +2. GitHub redirecciona a los usuarios de vuelta a tu sitio +3. Tu GitHub App accede a la API con el token de acceso del usuario + +Si seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación** cuando crees o modifiques tu app, el paso 1 se completará durante la instalación de la misma. Para obtener más información, consulta la sección "[Autorizar usuarios durante la instalación](/apps/installing-github-apps/#authorizing-users-during-installation)". + +#### 1. Solicita la identidad de un usuario de GitHub + + GET {% data variables.product.oauth_host_code %}/login/oauth/authorize + +Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuarios con una cuenta específica que pueden utilizar para registrarse y autorizar tu app. + +##### Parámetros + +| Nombre | Type | Descripción | +| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu GitHub App. Puedes encontrarla en los [Ajustes de tu GitHub App](https://github.com/settings/apps) cuando selecciones tu app. | +| `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esta debe ser una copia exacta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} una de las URL que proporcionaste como **URL de rellamado** {% else %} la URL que proporcionaste en el campo **URL de rellamado de autorización de usuario** {% endif %} cuando configuraste tu GitHub App y no puede contener ningún parámetro adicional. | +| `state` | `secuencia` | Este deberá contener una secuencia aleatoria para dar protección contra los ataques de falsificación y podría contener cualquier otros datos arbitrarios. | +| `login` | `secuencia` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app. | + +{% note %} + +**Nota:** No necesitas proporcionar alcances en tu solicitud de autorización. A diferencia de la OAuth trandicional, el token de autorizción se limita a los permisos asociados con tu GitHub App y a aquellos del usuario. + +{% endnote %} + +#### 2. GitHub redirecciona a los usuarios de vuelta a tu sitio + +Si el usuario acepta tu solicitud, GitHub te redirecciona de regreso a tu sitio con un `code` temporal en un parámetro de código así como con el estado que proporcionaste en el paso anterior en el parámetro `state`. Si los estados no coinciden significa que un tercero creó la solicitud y que se debe anular el proceso. + +{% note %} + +**Nota:** Si seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación ** cuando creas o modificas tu app, GitHub regreará un `code` temporal que necesitarás intercambiar por un token de acceso. El parámetro `state` no se regresa cuando GitHub inicia el flujo de OAuth durante la instalación de la app. + +{% endnote %} + +Intercambia este `code` por un token de acceso. {% if currentVersion == "free-pro-team@latest" %} Cuando se habilita el vencimiento de tokens, el token de acceso vence en 8 horas yel token de actualización en 6 meses. Cada que actualizas el token, obtienes un nuevo token de actualización. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)". + +Los tokens de usuario con caducidad son parte del beta de caducidad de tokens de usuario a servidor actualmente y están sujetos a cambios. Para participar en la característica beta de tokens de usuario a servidor con caducidad, consulta la sección "[Activar las características beta para las aplicaciones](/developers/apps/activating-beta-features-for-apps)".{% endif %} + + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token + +##### Parámetros + +| Nombre | Type | Descripción | +| --------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu GitHub App. | +| `client_secret` | `secuencia` | **Requerido.** El secreto de cliente para tu GitHub App. | +| `code` | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1. | +| `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esta debe ser una copia exacta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} una de las URL que proporcionaste como **URL de rellamado** {% else %} la URL que proporcionaste en el campo **URL de rellamado de autorización de usuario** {% endif %} cuando configuraste tu GitHub App y no puede contener ningún parámetro adicional. | +| `state` | `secuencia` | La secuencia aleatoria indescifrable que proporcionaste en el Paso 1. | + +##### Respuesta + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} + +Predeterminadamente, la respuesta toma la siguiente forma. Los parámetros de respuesta `expires_in`, `refresh_token`, y `refresh_token_expires_in` solo se devuelven cuando habilitas el beta para la caducidad de los tokens de acceso de usuario a servidor. + +``` +{ + "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "expires_in": "28800", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token_expires_in": "15811200", + "scope": "", + "token_type": "bearer" +} +``` +{% else %} + +Predeterminadamente, la respuesta toma la siguiente forma: + + access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + +{% endif %} + +#### 3. Tu GitHub App accede a la API con el token de acceso del usuario + +El token de acceso del usuario permite que la GitHub App haga solicitudes a la API a nombre del usuario. + + Authorization: token OAUTH-TOKEN + GET {% data variables.product.api_url_code %}/user + +Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera: + +```shell +curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user +``` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +### Flujo de dispositivos + +{% if currentVersion ver_lt "enterprise-server@3.1" %} +{% note %} + +**Nota:** El flujo de dispositivos se encuentra en un beta público y está sujeto a cambios. + +{% endnote %} +{% endif %} + +Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git. + +Para obtener más información acerca de autorizar a usuarios utilizando el flujo de dispositivos, consulta la sección "[Autorizar Apps de OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". + +{% endif %} + +### Revisar a qué recursos de instalación puede acceder un usuario + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% data reusables.pre-release-program.machine-man-preview %} +{% data reusables.pre-release-program.api-preview-warning %} +{% endif %} + +Ya que tengas un token de OAuth para un usuario, puedes revisar a qué instalaciones puede acceder. + + Authorization: token OAUTH-TOKEN + GET /user/installations + +También puedes verificar qué repositorios se encuentran accesibles para un usuario para una instalación. + + Authorization: token OAUTH-TOKEN + GET /user/installations/:installation_id/repositories + +Puedes encontrar más detalles en: [Listar instalaciones de app accesibles para el token de acceso del usuario](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) y [Listar repositorios accesibles para el token de acceso del usuario](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token). + +### Gestionar una autorización revocada a una GitHub App + +Si un usuario revoca su autorización de una GitHub App, dicha app recibirá el webhook [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) predeterminadamente. Las GitHub Apps no pueden desuscribirse de este evento. {% data reusables.webhooks.authorization_event %} + +### Permisos a nivel de usuario + +Puedes agregar permisos a nivel de usuario a tu GitHub App para acceder a los recursos del usuario, tales como correos electrónicos del usuario, los cuales otorgan los usuarios independientes como parte del [flujo de autorización del usuario](#identifying-users-on-your-site). Los permisos a nivel de usuario difieren de los [permisos a nivel de organización y de repositorio](/rest/reference/permissions-required-for-github-apps), los cuales se otorgan en el momento de la instalación en una cuenta de usuario o de organización. + +Puedes seleccionar los permisos a nivel de usuario desde dentro de la configuración de tu GitHub App en la sección de **Permisos de usuario** de la página de **Permisos & webhooks**. Para obtener más información sobre seleccionar permisos, consulta la sección [Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". + +Cuando un usuario instala tu app en su cuenta, el aviso de instalación listará los permisos a nivel de usuario que tu app está solicitando y explicará que la app puede pedir estos permisos a los usuarios independientes. + +Ya que los permisos a nivel de usuario se otorgan individualmente, puedes agregarlos a tu app existente sin solicitar que los usuarios los mejoren. Sin embargo, necesitarás enviar usuarios existentes a través del flujo de autorización de usuarios para autorizar los permisos nuevos y obtener un token nuevo de usuario a servidor para estas solicitudes. + +### Solicitudes de usuario a servidor + +Mientras que la mayoría de tu interacción con la API deberá darse utilizando tus tokens de acceso a la instalación de servidor a servidor, ciertas terminales te permiten llevar a cabo acciones a través de la API utilizando un token de acceso. Tu app puede hacer las siguientes solicitudes utilizando las terminales de [GraphQL v4](/graphql) o de [REST v3](/rest). + +#### Terminales compatibles + +{% if currentVersion == "free-pro-team@latest" %} +##### Ejecutores de Acciones + +* [Listar aplicaciones de ejecutores para un repositorio](/rest/reference/actions#list-runner-applications-for-a-repository) +* [Listar ejecutores auto-hospedados para un repositorio](/rest/reference/actions#list-self-hosted-runners-for-a-repository) +* [Obtener un ejecutor auto-hospedado para un repositorio](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) +* [Borrar un ejecutor auto-hospedado de un repositorio](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) +* [Crear un token de registro para un repositorio](/rest/reference/actions#create-a-registration-token-for-a-repository) +* [Crear un token de eliminación para un repositorio](/rest/reference/actions#create-a-remove-token-for-a-repository) +* [Listar aplicaciones de ejecutores para una organización](/rest/reference/actions#list-runner-applications-for-an-organization) +* [Listar ejecutores auto-hospedados para una organización](/rest/reference/actions#list-self-hosted-runners-for-an-organization) +* [Obtener ejecutores auto-hospedados para una organización](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) +* [Borrar un ejecutor auto-hospedado de una organización](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) +* [Crear un token de registro para una organización](/rest/reference/actions#create-a-registration-token-for-an-organization) +* [Crear un token de eliminación para una organización](/rest/reference/actions#create-a-remove-token-for-an-organization) + +##### Secretos de las Acciones + +* [Obtener la llave pública de un repositorio](/rest/reference/actions#get-a-repository-public-key) +* [Listar los secretos del repositorio](/rest/reference/actions#list-repository-secrets) +* [Obtener el secreto de un repositorio](/rest/reference/actions#get-a-repository-secret) +* [Crear o actualizar el secreto de un repositorio](/rest/reference/actions#create-or-update-a-repository-secret) +* [Borrar el secreto de un repositorio](/rest/reference/actions#delete-a-repository-secret) +* [Obtener la llave pública de una organización](/rest/reference/actions#get-an-organization-public-key) +* [Listar los secretos de la organización](/rest/reference/actions#list-organization-secrets) +* [Obtener el secreto de una organización](/rest/reference/actions#get-an-organization-secret) +* [Crear o actualizar el secreto de una organización](/rest/reference/actions#create-or-update-an-organization-secret) +* [Listar los repositorios seleccionados para el secreto de una organización](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) +* [Configurar los repositorios seleccionados para el secreto de una organización](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) +* [Agregar el repositorio seleccionado al secreto de una organización](/rest/reference/actions#add-selected-repository-to-an-organization-secret) +* [Eliminar el repositorio seleccionado del secreto de una organización](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) +* [Borrar el secreto de una organización](/rest/reference/actions#delete-an-organization-secret) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +##### Artefactos + +* [Listar artefactos para un repositorio](/rest/reference/actions#list-artifacts-for-a-repository) +* [Listar artefactos de ejecución de flujo de trabajo](/rest/reference/actions#list-workflow-run-artifacts) +* [Obtener un artefacto](/rest/reference/actions#get-an-artifact) +* [Borrar un artefacto](/rest/reference/actions#delete-an-artifact) +* [Descargar un artefacto](/rest/reference/actions#download-an-artifact) +{% endif %} + +##### Ejecuciones de Verificación + +* [Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run) +* [Obtener una ejecución de verificación](/rest/reference/checks#get-a-check-run) +* [Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run) +* [Listar las anotaciones de una ejecución de verificación](/rest/reference/checks#list-check-run-annotations) +* [Listar las ejecuciones de verificación en un conjunto de verificaciones](/rest/reference/checks#list-check-runs-in-a-check-suite) +* [Listar las ejecuciones de verificación para una referencia de Git](/rest/reference/checks#list-check-runs-for-a-git-reference) + +##### Check Suites + +* [Crear un conjunto de verificaciones](/rest/reference/checks#create-a-check-suite) +* [Obtener un conjunto de verificaciones](/rest/reference/checks#get-a-check-suite) +* [Solicitar un conjunto de verificaciones](/rest/reference/checks#rerequest-a-check-suite) +* [Actualizar las preferencias del repositorio para los conjuntos de verificaciones](/rest/reference/checks#update-repository-preferences-for-check-suites) +* [Listar conjuntos de verificaciones para una referencia de Git](/rest/reference/checks#list-check-suites-for-a-git-reference) + +##### Códigos de Conducta + +* [Obtener todos los códigos de conducta](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +* [Obtener un código de conducta específico](/rest/reference/codes-of-conduct#get-a-code-of-conduct) + +##### Estados de Despliegue + +* [Listar los estados de despliegue](/rest/reference/repos#list-deployment-statuses) +* [Crear los estados de despliegue](/rest/reference/repos#create-a-deployment-status) +* [Obtener un estado de despliegue](/rest/reference/repos#get-a-deployment-status) + +##### Implementaciones + +* [Listar los despliegues](/rest/reference/repos#list-deployments) +* [Crear un despliegue](/rest/reference/repos#create-a-deployment) +* [Obtén un despliegue](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Borrar un despliegue](/rest/reference/repos#delete-a-deployment){% endif %} + +##### Eventos + +* [Listar eventos públicos para una red de repositorios](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +* [Listar eventos de organizaciones públicas](/rest/reference/activity#list-public-organization-events) + +##### Fuentes + +* [Obtener fuentes](/rest/reference/activity#get-feeds) + +##### Blobs de Git + +* [Crear un blob](/rest/reference/git#create-a-blob) +* [Obtener un blob](/rest/reference/git#get-a-blob) + +##### Confirmaciones de Git + +* [Crear una confirmación](/rest/reference/git#create-a-commit) +* [Obtener una confirmación](/rest/reference/git#get-a-commit) + +##### Referencias de Git + +* [Crea una referencia](/rest/reference/git#create-a-reference)* [Obtén una referencia](/rest/reference/git#get-a-reference) +* [Lista las referencias coincidentes](/rest/reference/git#list-matching-references) +* [Actualizar una referencia](/rest/reference/git#update-a-reference) +* [Borrar una referencia](/rest/reference/git#delete-a-reference) + +##### Matrículas de Git + +* [Crear un objeto de matrícula](/rest/reference/git#create-a-tag-object) +* [Obtener una matrícula](/rest/reference/git#get-a-tag) + +##### Árboles de Git + +* [Crear un árbol](/rest/reference/git#create-a-tree) +* [Obtener un árbol](/rest/reference/git#get-a-tree) + +##### Plantillas de Gitignore + +* [Obtener todas las plantillas de gitignore](/rest/reference/gitignore#get-all-gitignore-templates) +* [Obtener una plantilla específica de gitignore](/rest/reference/gitignore#get-a-gitignore-template) + +##### Instalaciones + +* [Listar repositorios accesibles para el token de acceso del usuario](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token) + +{% if currentVersion == "free-pro-team@latest" %} +##### Límites de interacción + +* [Obtener restricciones de interacción para una organización](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) +* [Configurar restricciones de interacción para una organización](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) +* [Eliminar restricciones de interacción para una organización](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) +* [Obtener restricciones de interacción para un repositorio](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) +* [Configurar restricciones de interacción para un repositorio](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) +* [Eliminar restricciones de interacción para un repositorio](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) +{% endif %} + +##### Asignados de Informes de Problemas + +* [Agregar asignados a un informe de problemas](/rest/reference/issues#add-assignees-to-an-issue) +* [Eliminar asignados de un informe de problemas](/rest/reference/issues#remove-assignees-from-an-issue) + +##### Comentarios de Informes de Problemas + +* [Listar comentarios del informe de problemas](/rest/reference/issues#list-issue-comments) +* [Crear un comentario del informe de problemas](/rest/reference/issues#create-an-issue-comment) +* [Listar cometnarios del informe de problemas para un repositorio](/rest/reference/issues#list-issue-comments-for-a-repository) +* [Obtener un comentario de un informe de problemas](/rest/reference/issues#get-an-issue-comment) +* [Actualizar un comentario de un informe de problemas](/rest/reference/issues#update-an-issue-comment) +* [Borrar un comentario de un informe de problemas](/rest/reference/issues#delete-an-issue-comment) + +##### Eventos de Informe de Problemas + +* [Listar eventos del informe de problemas](/rest/reference/issues#list-issue-events) + +##### Línea de tiempo del Informe de Problemas + +* [Listar eventos de la línea de tiempo para un informe de problemas](/rest/reference/issues#list-timeline-events-for-an-issue) + +##### Problemas + +* [Listar informes de problemas asignados al usuario autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user) +* [Listar asignados](/rest/reference/issues#list-assignees) +* [Revisar si se puede asignar un usuario](/rest/reference/issues#check-if-a-user-can-be-assigned) +* [Listar informes de problemas del repositorio](/rest/reference/issues#list-repository-issues) +* [Crear un informe de problemas](/rest/reference/issues#create-an-issue) +* [Obtener un informe de problemas](/rest/reference/issues#get-an-issue) +* [Actualizar un informe de problemas](/rest/reference/issues#update-an-issue) +* [Bloquear un informe de problemas](/rest/reference/issues#lock-an-issue) +* [Desbloquear un informe de problemas](/rest/reference/issues#unlock-an-issue) + +{% if currentVersion == "free-pro-team@latest" %} +##### Jobs + +* [Obener un job para una ejecución de flujo de trabajo](/rest/reference/actions#get-a-job-for-a-workflow-run) +* [Descargar bitácoras del job para una ejecución de flujode trabajo](/rest/reference/actions#download-job-logs-for-a-workflow-run) +* [Listar jobs para una ejecución de flujo de trabajo](/rest/reference/actions#list-jobs-for-a-workflow-run) +{% endif %} + +##### Etiquetas + +* [Listar las etiquetas para un informe de problemas](/rest/reference/issues#list-labels-for-an-issue) +* [Agregar etiquetas a un informe de problemas](/rest/reference/issues#add-labels-to-an-issue) +* [Configurar eitquetas para un informe de problemas](/rest/reference/issues#set-labels-for-an-issue) +* [Eliminar todas las etiquetas de un informe de problemas](/rest/reference/issues#remove-all-labels-from-an-issue) +* [Eliminar una etiqueta de un informe de problemas](/rest/reference/issues#remove-a-label-from-an-issue) +* [Listar etiquetas para un repositorio](/rest/reference/issues#list-labels-for-a-repository) +* [Crear una etiqueta](/rest/reference/issues#create-a-label) +* [Obtener una etiqueta](/rest/reference/issues#get-a-label) +* [Actualizar una etiqueta](/rest/reference/issues#update-a-label) +* [Borrar una etiqueta](/rest/reference/issues#delete-a-label) +* [Obtener etiquetas para cada informe de problemas en un hito](/rest/reference/issues#list-labels-for-issues-in-a-milestone) + +##### Licencias + +* [Obtener todas las licencias que se utilizan habitualmente](/rest/reference/licenses#get-all-commonly-used-licenses) +* [Obtener una licencia](/rest/reference/licenses#get-a-license) + +##### Markdown + +* [Generar un documento de Markdown](/rest/reference/markdown#render-a-markdown-document) +* [Generar un documento de markdwon en modo raw](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) + +##### Meta + +* [Meta](/rest/reference/meta#meta) + +##### Hitos + +* [Listar hitos](/rest/reference/issues#list-milestones) +* [Crear un hito](/rest/reference/issues#create-a-milestone) +* [Obtener un hito](/rest/reference/issues#get-a-milestone) +* [Actualizar un hito](/rest/reference/issues#update-a-milestone) +* [Borrar un hito](/rest/reference/issues#delete-a-milestone) + +##### Ganchos de organización + +* [Listar los webhooks de la organización](/rest/reference/orgs#webhooks/#list-organization-webhooks) +* [Crear un webhook para una organización](/rest/reference/orgs#webhooks/#create-an-organization-webhook) +* [Obtener un webhook de una organización](/rest/reference/orgs#webhooks/#get-an-organization-webhook) +* [Actualizar el webhook de una organización](/rest/reference/orgs#webhooks/#update-an-organization-webhook) +* [Borrar el webhook de una organización](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) +* [Hacer ping al webhook de una organización](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) + +{% if currentVersion == "free-pro-team@latest" %} +##### Invitaciones a las Organizaciones + +* [Listar las invitaciones pendientes a una organización](/rest/reference/orgs#list-pending-organization-invitations) +* [Crear una invitación a una organización](/rest/reference/orgs#create-an-organization-invitation) +* [Listar los equipos de invitación a una organización](/rest/reference/orgs#list-organization-invitation-teams) +{% endif %} + +##### Miembros de la Organización + +* [Listar a los miembros de la organización](/rest/reference/orgs#list-organization-members) +* [Verificar la membrecía de organización de un usuario](/rest/reference/orgs#check-organization-membership-for-a-user) +* [Eliminar a un miembro de una organización](/rest/reference/orgs#remove-an-organization-member) +* [Obtener la membrecía de organización para un usuario](/rest/reference/orgs#get-organization-membership-for-a-user) +* [Configurar una mebrecía de organización para un usuario](/rest/reference/orgs#set-organization-membership-for-a-user) +* [Eliminar la membrecía de organización de un usuario](/rest/reference/orgs#remove-organization-membership-for-a-user) +* [Listar los miembros de una organización pública](/rest/reference/orgs#list-public-organization-members) +* [Verificar la membrecía de una organización pública de un usuario](/rest/reference/orgs#check-public-organization-membership-for-a-user) +* [Configurar la membrecía de una organización pública para el usuario autenticado](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) +* [Eliminar la membrecía de una organizción pública del usuario autenticado](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) + +##### Colaboradores Externos de una Organización + +* [Listar los colaboradores externos de una organización](/rest/reference/orgs#list-outside-collaborators-for-an-organization) +* [Convertir a un miembro de la organización en colaborador externo](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) +* [Eliminar a un colaborador externo de la organización](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) + +{% if enterpriseServerVersions contains currentVersion %} +##### Ganchos de Pre-recepción de la Organización + +* [Listar los ganchos de pre-recepción de una organización](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) +* [Obtener los ganchos de pre-recepción de una organización](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) +* [Actualizar el requerir los ganchos de pre-recepción para una organización](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) +* [Eliminar el requerir los ganchos de pre-recepción para una organización](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +##### Poyectos de Equipo de una Organización + +* [Listar los proyectos de equipo](/rest/reference/teams#list-team-projects) +* [Verificar los permisos del equipo para un proyecto](/rest/reference/teams#check-team-permissions-for-a-project) +* [Agregar o actualizar los permisos de un proyecto de equipo](/rest/reference/teams#add-or-update-team-project-permissions) +* [Eliminar a un proyecto de un equipo](/rest/reference/teams#remove-a-project-from-a-team) +{% endif %} + +##### Repositorios de Equipo de la Organización + +* [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories) +* [Verificar los permisos de un equipo para un repositorio](/rest/reference/teams#check-team-permissions-for-a-repository) +* [Agregar o actualizar los permisos de un repositorio de equipo](/rest/reference/teams#add-or-update-team-repository-permissions) +* [Eliminar a un repositorio de un equipo](/rest/reference/teams#remove-a-repository-from-a-team) + +{% if currentVersion == "free-pro-team@latest" %} +##### Sincronización de Equipos de la Organización + +* [Listar los grupos de IdP de un equipo](/rest/reference/teams#list-idp-groups-for-a-team) +* [Crear o actualizar las conexiones de un grupo de IdP](/rest/reference/teams#create-or-update-idp-group-connections) +* [Listar grupos de IdP para una organización](/rest/reference/teams#list-idp-groups-for-an-organization) +{% endif %} + +##### Equipos de la Organización + +* [Listar equipos](/rest/reference/teams#list-teams) +* [Crear un equipo](/rest/reference/teams#create-a-team) +* [Obtener un equipo por su nombre](/rest/reference/teams#get-a-team-by-name) +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +* [Obtener un equipo](/rest/reference/teams#get-a-team) +{% endif %} +* [Actualizar un equipo](/rest/reference/teams#update-a-team) +* [Borrar un equipo](/rest/reference/teams#delete-a-team) +{% if currentVersion == "free-pro-team@latest" %} +* [Listar invitaciones pendientes al equipo](/rest/reference/teams#list-pending-team-invitations) +{% endif %} +* [Listar miembros del equipo](/rest/reference/teams#list-team-members) +* [Obtener la membresía de equipo de un usuario](/rest/reference/teams#get-team-membership-for-a-user) +* [Agregar o actualizar la membrecía de equipo de un usuario](/rest/reference/teams#add-or-update-team-membership-for-a-user) +* [Eliminar la membrecía de equipo para un usuario](/rest/reference/teams#remove-team-membership-for-a-user) +* [Listar los equipos hijos](/rest/reference/teams#list-child-teams) +* [Listar los equipos para el usuario autenticado](/rest/reference/teams#list-teams-for-the-authenticated-user) + +##### Organizaciones + +* [Listar organizaciones](/rest/reference/orgs#list-organizations) +* [Obtener una organización](/rest/reference/orgs#get-an-organization) +* [Actualizar una organización](/rest/reference/orgs#update-an-organization) +* [Listar membrecías de organización para el usuario autenticado](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) +* [Obtener la membrecía de organización para el usuario autenticado](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) +* [Actualizar la membrecía de una organización para el usuario autenticado](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) +* [Listar las organizaciones para el usuario autenticado](/rest/reference/orgs#list-organizations-for-the-authenticated-user) +* [Listar las organizaciones de un usuario](/rest/reference/orgs#list-organizations-for-a-user) + +{% if currentVersion == "free-pro-team@latest" %} +##### Autorizaciones de Credencial para las Organizaciones + +* [Listar las autorizaciones del SSO de SAML para una organización](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization) +* [Eliminar las autorizaciones del SSO de SAML de una organización](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +##### Scim de las Organizaciones + +* [Listar las identidades aprovisionadas de SCIM](/rest/reference/scim#list-scim-provisioned-identities) +* [Aprovisionar e invitar a un usuario de SCIM](/rest/reference/scim#provision-and-invite-a-scim-user) +* [Obtener la información de aprovisionamiento de SCIM para un usuario](/rest/reference/scim#get-scim-provisioning-information-for-a-user) +* [Configurar la información de SCIM para un usuario aprovisionado](/rest/reference/scim#set-scim-information-for-a-provisioned-user) +* [Actualizar un atributo para un usuario de SCIM](/rest/reference/scim#update-an-attribute-for-a-scim-user) +* [Borrar a un usuario de SCIM de una organización](/rest/reference/scim#delete-a-scim-user-from-an-organization) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +##### Importaciones de Código Fuente + +* [Obtener el estado de una importación](/rest/reference/migrations#get-an-import-status) +* [Iniciar una importación](/rest/reference/migrations#start-an-import) +* [Actualizar una importación](/rest/reference/migrations#update-an-import) +* [Cancelar una importación](/rest/reference/migrations#cancel-an-import) +* [Obtener los autores de una confirmación](/rest/reference/migrations#get-commit-authors) +* [Mapear al autor de una confirmación](/rest/reference/migrations#map-a-commit-author) +* [Obtener archivos grandes](/rest/reference/migrations#get-large-files) +* [Actualizar la preferencia de LFS de Git](/rest/reference/migrations#update-git-lfs-preference) +{% endif %} + +##### Colaboradores de Proyecto + +* [Listar colaboradores del proyecto](/rest/reference/projects#list-project-collaborators) +* [Agregar a un colaborador del proyecto](/rest/reference/projects#add-project-collaborator) +* [Eliminar a un colaborador del proyecto](/rest/reference/projects#remove-project-collaborator) +* [Obtener permisos del proyecto para un usuario](/rest/reference/projects#get-project-permission-for-a-user) + +##### Proyectos + +* [Listar los proyectos de la organización](/rest/reference/projects#list-organization-projects) +* [Crear un proyecto en la organización](/rest/reference/projects#create-an-organization-project) +* [Obtener un proyecto](/rest/reference/projects#get-a-project) +* [Actualizar un proyecto](/rest/reference/projects#update-a-project) +* [Borrar un proyecto](/rest/reference/projects#delete-a-project) +* [Listar las columnas del proyecto](/rest/reference/projects#list-project-columns) +* [Crear una columna de proyecto](/rest/reference/projects#create-a-project-column) +* [Obtener una columna de proyecto](/rest/reference/projects#get-a-project-column) +* [Actualizar una column de proyecto](/rest/reference/projects#update-a-project-column) +* [Borrar una columna de proyecto](/rest/reference/projects#delete-a-project-column) +* [Listar las tarjetas del proyecto](/rest/reference/projects#list-project-cards) +* [Crear una tarjeta de proyecto](/rest/reference/projects#create-a-project-card) +* [Mover una columna de proyecto](/rest/reference/projects#move-a-project-column) +* [Obtener una tarjeta de proyecto](/rest/reference/projects#get-a-project-card) +* [Actualizar una tarjeta de proyecto](/rest/reference/projects#update-a-project-card) +* [Borrar una tarjeta de proyecto](/rest/reference/projects#delete-a-project-card) +* [Mover una tarjeta de proyecto](/rest/reference/projects#move-a-project-card) +* [Listar los proyectos de un repositorio](/rest/reference/projects#list-repository-projects) +* [Crear un proyecto en un repositorio](/rest/reference/projects#create-a-repository-project) + +##### Comentarios de Extracción + +* [Listar comentarios de revisión en una solicitud de extracción](/rest/reference/pulls#list-review-comments-on-a-pull-request) +* [Crear un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) +* [Listar comentarios de revisión en un repositorio](/rest/reference/pulls#list-review-comments-in-a-repository) +* [Obtener un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) +* [Actualizar un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) +* [Borrar un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) + +##### Eventos de Revisión en Solciitudes de Extracción + +* [Descartar una revisión para una solicitud de extracción](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) +* [Emitir una revisión para una solicitud de extracción](/rest/reference/pulls#submit-a-review-for-a-pull-request) + +##### Solicitudes de Revisión para Solicitudes de Extracción + +* [Listar a los revisores requeridos para una solicitud de extracción](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) +* [Solicitar a los revisores para una solicitud de extracción](/rest/reference/pulls#request-reviewers-for-a-pull-request) +* [Eliminar a los revisores solicitados para una solicitud de extracción](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) + +##### Revisiones de Solicitudes de Extracción + +* [Listar revisores para una solicitud de extracción](/rest/reference/pulls#list-reviews-for-a-pull-request) +* [Crear revisión para una solicitud de extracción](/rest/reference/pulls#create-a-review-for-a-pull-request) +* [Obtener una revisión para una solicitud de extracción](/rest/reference/pulls#get-a-review-for-a-pull-request) +* [Actualizar una revisión para una solicitud de extracción](/rest/reference/pulls#update-a-review-for-a-pull-request) +* [Listar los comentarios para una revisión de una solicitud de extracción](/rest/reference/pulls#list-comments-for-a-pull-request-review) + +##### Extracciones + +* [Listar solicitudes extracción](/rest/reference/pulls#list-pull-requests) +* [Crear una solicitud de extracción](/rest/reference/pulls#create-a-pull-request) +* [Obtener una solicitud de extracción](/rest/reference/pulls#get-a-pull-request) +* [Actualizar una solicitud de extracción](/rest/reference/pulls#update-a-pull-request) +* [Listar las confirmaciones en una solicitud de extracción](/rest/reference/pulls#list-commits-on-a-pull-request) +* [Listar los archivos en una solicitud de extracción](/rest/reference/pulls#list-pull-requests-files) +* [Revisar si se ha fusionado una solicitud de extracción](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) +* [Fusionar una solicitud de extracción (Botón de Fusionar)](/rest/reference/pulls#merge-a-pull-request) + +##### Reacciones + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}* [Borrar una reacción](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Borrar una reacción](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Listar las reacciones a un comentario de una confirmación](/rest/reference/reactions#list-reactions-for-a-commit-comment) +* [Crear una reacción para el comentario de una confirmación](/rest/reference/reactions#create-reaction-for-a-commit-comment) +* [Listar las reacciones de un informe de problemas](/rest/reference/reactions#list-reactions-for-an-issue) +* [Crear una reacción para un informe de problemas](/rest/reference/reactions#create-reaction-for-an-issue) +* [Listar las reacciones para el comentario de un informe de problemas](/rest/reference/reactions#list-reactions-for-an-issue-comment) +* [Crear una reacción para el comentario de informe de problemas](/rest/reference/reactions#create-reaction-for-an-issue-comment) +* [Listar las reacciones para el comentario de revisión de una solicitud de extracción](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) +* [Crear una reacción para un comentario de revisión de una solicitud de extracción](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) +* [Listar las reacciones para un comentario de debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) +* [Crear una reacción para un comentario de debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) +* [Listar las reaciones a un debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion) +* [Crear una reacción para un debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +* [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-a-commit-comment-reaction) +* [Borrar la reacción a un comentario](/rest/reference/reactions#delete-an-issue-reaction) +* [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-an-issue-comment-reaction) +* [Borrar la reacción a un comentario de una solicitud de extracción](/rest/reference/reactions#delete-a-pull-request-comment-reaction) +* [Borrar la reacción a un debate de equipo](/rest/reference/reactions#delete-team-discussion-reaction) +* [Borrar la reacción a un comentario de un debate de equipo](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} + +##### Repositorios + +* [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories) +* [Crear un repositorio para el usuario autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) +* [Obtener un repositorio](/rest/reference/repos#get-a-repository) +* [Actualizar un repositorio](/rest/reference/repos#update-a-repository) +* [Borrar un repositorio](/rest/reference/repos#delete-a-repository) +* [Comparar dos confirmaciones](/rest/reference/repos#compare-two-commits) +* [Listar los colaboradores del repositorio](/rest/reference/repos#list-repository-contributors) +* [Listar las bifurcaciones](/rest/reference/repos#list-forks) +* [Crear una bifuración](/rest/reference/repos#create-a-fork) +* [Listar los lenguajes de un repositorio](/rest/reference/repos#list-repository-languages) +* [Listar las matrículas de un repositorio](/rest/reference/repos#list-repository-tags) +* [Listar los equipos de un repositorio](/rest/reference/repos#list-repository-teams) +* [Transferir un repositorio](/rest/reference/repos#transfer-a-repository) +* [Listar los repositorios públicos](/rest/reference/repos#list-public-repositories) +* [Listar los repositorios para el usuario autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) +* [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user) +* [Crear un repositorio utilizando una plantilla de repositorio](/rest/reference/repos#create-repository-using-a-repository-template) + +##### Actividad del Repositorio + +* [Listar Stargazers](/rest/reference/activity#list-stargazers) +* [Listar observadores](/rest/reference/activity#list-watchers) +* [Listar los repositorios que el usuario ha marcado con una estrella](/rest/reference/activity#list-repositories-starred-by-a-user) +* [Verificar si el usuario autenticado ha marcado al repositorio con una estrella](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) +* [Marcar un repositorio con una estrella para el usuario autenticado](/rest/reference/activity#star-a-repository-for-the-authenticated-user) +* [Quitar la estrella de un repositorio para el usuario autenticado](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) +* [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user) + +{% if currentVersion == "free-pro-team@latest" %} +##### Correcciones de Seguridad Automatizadas de un Repositorio + +* [Habilitar las correcciones de seguridad automatizadas](/rest/reference/repos#enable-automated-security-fixes) +* [Inhabilitar las correcciones de seguridad automatizadas](/rest/reference/repos#disable-automated-security-fixes) +{% endif %} + +##### Ramas de los Repositorios + +* [Listar ramas](/rest/reference/repos#list-branches) +* [Obtener una rama](/rest/reference/repos#get-a-branch) +* [Obtener la protección de una rama](/rest/reference/repos#get-branch-protection) +* [Actualizar la protección de una rama](/rest/reference/repos#update-branch-protection) +* [Borrar la protección de una rama](/rest/reference/repos#delete-branch-protection) +* [Obtener la protección administrativa de una rama](/rest/reference/repos#get-admin-branch-protection) +* [Configurar la protección administrativa de una rama](/rest/reference/repos#set-admin-branch-protection) +* [Borrar la protección administrativa de una rama](/rest/reference/repos#delete-admin-branch-protection) +* [Obtener la protección de la revisión de una solicitud de extracción](/rest/reference/repos#get-pull-request-review-protection) +* [Actualizar la protección de la revisión de una solicitud de extracción](/rest/reference/repos#update-pull-request-review-protection) +* [Borrar la protección de la revisión de una solicitud de extracción](/rest/reference/repos#delete-pull-request-review-protection) +* [Obtener la protección de firma de una confirmación](/rest/reference/repos#get-commit-signature-protection) +* [Crear la protección de firma de una confirmación](/rest/reference/repos#create-commit-signature-protection) +* [Borrar la protección de firma de una confirmación](/rest/reference/repos#delete-commit-signature-protection) +* [Obtener la protección de las verificaciones de estado](/rest/reference/repos#get-status-checks-protection) +* [Actualizar la protección para la verificación de estados](/rest/reference/repos#update-status-check-protection) +* [Eliminar la protección de las verificaciones de estado](/rest/reference/repos#remove-status-check-protection) +* [Obtener todos los contextos de verificaciones de estado](/rest/reference/repos#get-all-status-check-contexts) +* [Agregar un contexto de verificación de estado](/rest/reference/repos#add-status-check-contexts) +* [Obtener un contexto de verificación de estado](/rest/reference/repos#set-status-check-contexts) +* [Eliminar los contextos de verificación de estado](/rest/reference/repos#remove-status-check-contexts) +* [Obtener restricciones de acceso](/rest/reference/repos#get-access-restrictions) +* [Borrar restricciones de acceso](/rest/reference/repos#delete-access-restrictions) +* [Listar a los equipos con acceso a la rama protegida](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) +* [Agregar restricciones de acceso a equipos](/rest/reference/repos#add-team-access-restrictions) +* [Obtener restricciones de acceso a equipos](/rest/reference/repos#set-team-access-restrictions) +* [Eliminar restricciones de acceso a equipos](/rest/reference/repos#remove-team-access-restrictions) +* [Listar las restricciones de usuario para la rama protegida](/rest/reference/repos#list-users-with-access-to-the-protected-branch) +* [Agregar las restricciones de acceso para los usuarios](/rest/reference/repos#add-user-access-restrictions) +* [Configurar las restricciones de acceso para los usuarios](/rest/reference/repos#set-user-access-restrictions) +* [Eliminar las restricciones de acceso para los usuarios](/rest/reference/repos#remove-user-access-restrictions) +* [Fusionar una rama](/rest/reference/repos#merge-a-branch) + +##### Colaboradores del Repositorio + +* [Listar los colaboradores del repositorio](/rest/reference/repos#list-repository-collaborators) +* [Verificar si un usuario es colaborador de un repositorio](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) +* [Agregar un colaborador de repositorio](/rest/reference/repos#add-a-repository-collaborator) +* [Eliminar a un colaborador del repositorio](/rest/reference/repos#remove-a-repository-collaborator) +* [Obtener permisos del repositorio para un usuario](/rest/reference/repos#get-repository-permissions-for-a-user) + +##### Comentarios de Confirmaciones de un Repositorio + +* [Listar los comentarios de confirmaciones en un repositorio](/rest/reference/repos#list-commit-comments-for-a-repository) +* [Obtener un comentario de una confirmación](/rest/reference/repos#get-a-commit-comment) +* [Actualizar un comentario de una confirmación](/rest/reference/repos#update-a-commit-comment) +* [Borrar un comentario de una confirmación](/rest/reference/repos#delete-a-commit-comment) +* [Listar los comentarios de una confirmación](/rest/reference/repos#list-commit-comments) +* [Crear un comentario de una confirmación](/rest/reference/repos#create-a-commit-comment) + +##### Confirmaciones de Repositorio + +* [Listar confirmaciones](/rest/reference/repos#list-commits) +* [Obtener una confirmación](/rest/reference/repos#get-a-commit) +* [Listar ramas para la confirmación principal](/rest/reference/repos#list-branches-for-head-commit) +* [Listar solicitudes de extracción asociadas con una confirmación](/rest/reference/repos#list-pull-requests-associated-with-commit) + +##### Comunidad del Repositorio + +* [Obtener el código de conducta de un repositorio](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) +{% if currentVersion == "free-pro-team@latest" %} +* [Obtener las métricas de perfil de la comunidad](/rest/reference/repos#get-community-profile-metrics) +{% endif %} + +##### Contenido de los Repositorios + +* [Descargar un archivo de un repositorio](/rest/reference/repos#download-a-repository-archive) +* [Obtener el contenido de un repositorio](/rest/reference/repos#get-repository-content) +* [Crear o actualizar los contenidos de archivo](/rest/reference/repos#create-or-update-file-contents) +* [Borrar un archivo](/rest/reference/repos#delete-a-file) +* [Obtener el README de un repositorio](/rest/reference/repos#get-a-repository-readme) +* [Obtener la licencia para un repositorio](/rest/reference/licenses#get-the-license-for-a-repository) + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +##### Envíos de Evento de un Repositorio + +* [Crear un evento de envío de un repositorio](/rest/reference/repos#create-a-repository-dispatch-event) +{% endif %} + +##### Ganchos de Repositorio + +* [Listar los webhooks de un repositorio](/rest/reference/repos#list-repository-webhooks) +* [Crear un webhook para un repositorio](/rest/reference/repos#create-a-repository-webhook) +* [Obtener un webhook para un repositorio](/rest/reference/repos#get-a-repository-webhook) +* [Actualizar el webhook de un repositorio](/rest/reference/repos#update-a-repository-webhook) +* [Borrar el webhook de un repositorio](/rest/reference/repos#delete-a-repository-webhook) +* [Hacer ping al webhook de un repositorio](/rest/reference/repos#ping-a-repository-webhook) +* [Probar el webhook de carga a un repositorio](/rest/reference/repos#test-the-push-repository-webhook) + +##### Invitaciones a un repositorio + +* [Listar las invitaciones a un repositorio](/rest/reference/repos#list-repository-invitations) +* [Actualizar la invitación a un repositorio](/rest/reference/repos#update-a-repository-invitation) +* [Borrar la invitación a un repositorio](/rest/reference/repos#delete-a-repository-invitation) +* [Listar las invitaciones a un repositorio para el usuario autenticado](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user) +* [Aceptar la invitación a un repositorio](/rest/reference/repos#accept-a-repository-invitation) +* [Rechazar la invitación a un repositorio](/rest/reference/repos#decline-a-repository-invitation) + +##### Claves de Repositorio + +* [Listar claves de despliegue](/rest/reference/repos#list-deploy-keys) +* [Crear una clave de despliegue](/rest/reference/repos#create-a-deploy-key) +* [Obtener una clave de despliegue](/rest/reference/repos#get-a-deploy-key) +* [Borrar una clave de despiegue](/rest/reference/repos#delete-a-deploy-key) + +##### Páginas de Repositorio + +* [Obtener un sitio de GitHub Pages](/rest/reference/repos#get-a-github-pages-site) +* [Crear un sitio de GitHub Pages](/rest/reference/repos#create-a-github-pages-site) +* [Actualizar la información acerca de un sitio de GitHub Pages](/rest/reference/repos#update-information-about-a-github-pages-site) +* [Borrar un sitio de GitHub Pages](/rest/reference/repos#delete-a-github-pages-site) +* [Listar las compilaciones de GitHub Pages](/rest/reference/repos#list-github-pages-builds) +* [Solicitar una compilación de GitHub Pages](/rest/reference/repos#request-a-github-pages-build) +* [Obtener una compilación de GitHub Pages](/rest/reference/repos#get-github-pages-build) +* [Obtener la última compilación de pages](/rest/reference/repos#get-latest-pages-build) + +{% if enterpriseServerVersions contains currentVersion %} +##### Ganchos de Pre-recepción de un Repositorio + +* [Listar los ganchos de pre-recepción para un repositorio](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) +* [Obtener un gancho de pre-recepción de un repositorio](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) +* [Actualizar el requerir ganchos de pre-recepción en un repositorio](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) +* [Eliminar el requerir ganchos de pre-recepción para un repositorio](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) +{% endif %} + +##### Lanzamientos de repositorio + +* [Listar los lanzamientos](/rest/reference/repos/#list-releases) +* [Crear un lanzamiento](/rest/reference/repos/#create-a-release) +* [Obtener un lanzamiento](/rest/reference/repos/#get-a-release) +* [Actualizar un lanzamiento](/rest/reference/repos/#update-a-release) +* [Borrar un lanzamiento](/rest/reference/repos/#delete-a-release) +* [Listar activos de lanzamiento](/rest/reference/repos/#list-release-assets) +* [Obtener un activo de lanzamiento](/rest/reference/repos/#get-a-release-asset) +* [Actualizar un activo de lanzamiento](/rest/reference/repos/#update-a-release-asset) +* [Borrar un activo de lanzamiento](/rest/reference/repos/#delete-a-release-asset) +* [Obtener el lanzamiento más reciente](/rest/reference/repos/#get-the-latest-release) +* [Obtener un lanzamiento por nombre de matrícula](/rest/reference/repos/#get-a-release-by-tag-name) + +##### Estadísticas de Repositorio + +* [Obtener la actividad de confirmaciones semanal](/rest/reference/repos#get-the-weekly-commit-activity) +* [Obtener la actividad de confirmaciones del año pasado](/rest/reference/repos#get-the-last-year-of-commit-activity) +* [Obtener la actividad de confirmaciones de todos los colaboradores](/rest/reference/repos#get-all-contributor-commit-activity) +* [Obtener la cuenta semanal de confirmaciones](/rest/reference/repos#get-the-weekly-commit-count) +* [Obtener la cuenta de confirmaciones por hora para cada día](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) + +{% if currentVersion == "free-pro-team@latest" %} +##### Alertas de Vulnerabilidad en Repositorios + +* [Habilitar las alertas de vulnerabilidades](/rest/reference/repos#enable-vulnerability-alerts) +* [Inhabilitar las alertas de vulnerabilidades](/rest/reference/repos#disable-vulnerability-alerts) +{% endif %} + +##### Raíz + +* [Terminal raíz](/rest#root-endpoint) +* [Emojis](/rest/reference/emojis#emojis) +* [Obtener un estado de límite de tasa para el usuario autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) + +##### Search + +* [Buscar código](/rest/reference/search#search-code) +* [Buscar confirmaciones](/rest/reference/search#search-commits) +* [Buscar etiquetas](/rest/reference/search#search-labels) +* [Buscar repositorios](/rest/reference/search#search-repositories) +* [Buscar temas](/rest/reference/search#search-topics) +* [Buscar usuarios](/rest/reference/search#search-users) + +##### Estados + +* [Obtener el estado combinado para una referencia específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) +* [Listar los estados de confirmación para una referencia](/rest/reference/repos#list-commit-statuses-for-a-reference) +* [Crear un estado de confirmación](/rest/reference/repos#create-a-commit-status) + +##### Debates de Equipo + +* [Listar debates](/rest/reference/teams#list-discussions) +* [Crear un debate](/rest/reference/teams#create-a-discussion) +* [Obtener un debate](/rest/reference/teams#get-a-discussion) +* [Actualizar un debate](/rest/reference/teams#update-a-discussion) +* [Borrar un debate](/rest/reference/teams#delete-a-discussion) +* [Listar los comentarios del debate](/rest/reference/teams#list-discussion-comments) +* [Crear un comentario sobre un debate](/rest/reference/teams#create-a-discussion-comment) +* [Obtener un comentario de un debate](/rest/reference/teams#get-a-discussion-comment) +* [Actualizar un comentario en un debate](/rest/reference/teams#update-a-discussion-comment) +* [Borrar un comentario de un debate](/rest/reference/teams#delete-a-discussion-comment) + +##### Temas + +* [Obtener todos los temas de un repositorio](/rest/reference/repos#get-all-repository-topics) +* [Reemplazar todos los temas de un repositorio](/rest/reference/repos#replace-all-repository-topics) + +{% if currentVersion == "free-pro-team@latest" %} +##### Tráfico + +* [Obtener los clones de un repositorio](/rest/reference/repos#get-repository-clones) +* [Obtener las rutas de referencia superior](/rest/reference/repos#get-top-referral-paths) +* [Obtener las fuentes de referencia superior](/rest/reference/repos#get-top-referral-sources) +* [Obtener las visualizaciones de página](/rest/reference/repos#get-page-views) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +##### Bloquear Usuarios + +* [Listar a los usuarios que ha bloqueado el usuario autenticado](/rest/reference/users#list-users-blocked-by-the-authenticated-user) +* [Verificar si el usuario autenticado bloqueó a un usuario](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) +* [Listar a los usuarios que habloqueado la organización](/rest/reference/orgs#list-users-blocked-by-an-organization) +* [Verificar si una organización bloqueó a un usuario](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) +* [Bloquear a un usuario de una organización](/rest/reference/orgs#block-a-user-from-an-organization) +* [Desbloquear a un usuario de una organización](/rest/reference/orgs#unblock-a-user-from-an-organization) +* [Bloquear a un usuario](/rest/reference/users#block-a-user) +* [Desbloquear a un usuario](/rest/reference/users#unblock-a-user) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +##### Correo Electrónico de Usuario + +{% if currentVersion == "free-pro-team@latest" %} +* [Configurar la visibilidad del correo electrónico principal para el usuario autenticado](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) +{% endif %} +* [Listar las direcciones de correo electrónico para el usuario autenticado](/rest/reference/users#list-email-addresses-for-the-authenticated-user) +* [Agregar la(s) dirección(es) de correo electrónico](/rest/reference/users#add-an-email-address-for-the-authenticated-user) +* [Borrar la(s) direccion(es) de correo electrónico](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) +* [Listar las direcciones de correo electrónico del usuario autenticado](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) +{% endif %} + +##### Seguidores del Usuario + +* [Listar los seguidores de un usuario](/rest/reference/users#list-followers-of-a-user) +* [Listar a las personas que sigue un usuario](/rest/reference/users#list-the-people-a-user-follows) +* [Revisar si el usuario autenticado sigue a una persona](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) +* [Seguir a un usuario](/rest/reference/users#follow-a-user) +* [Dejar de seguri a un usuario](/rest/reference/users#unfollow-a-user) +* [Verificar si el usuario sigue a otro usuario](/rest/reference/users#check-if-a-user-follows-another-user) + +##### Utilizar Llaves Gpg + +* [Listar las llaves GPG para el usuario autenticado](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) +* [Crear una llave GPG para el usuario autenticado](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) +* [Obtener una llave GPG para el usuario autenticado](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) +* [Borrar una llave GPG para el usuario autenticado](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) +* [Listar las llaves GPG de un usuario](/rest/reference/users#list-gpg-keys-for-a-user) + +##### Llaves Públicas de Usuario + +* [Listar las llaves SSH para el usuario autenticado](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) +* [Crear una llave SSH para el usuario autenticado](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) +* [Obtener una llave SSH pública para el usuario autenticado](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) +* [Borrar una llave pública de SSH para el usuario autenticado](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) +* [Listar las llaves públicas de un usuario](/rest/reference/users#list-public-keys-for-a-user) + +##### Usuarios + +* [Obtener al usuario autenticado](/rest/reference/users#get-the-authenticated-user) +* [Listar las instalaciones de apps accesibles para el token de acceso del usuario](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) +{% if currentVersion == "free-pro-team@latest" %} +* [Listar las suscripciones del usuario autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) +{% endif %} +* [Listar usuarios](/rest/reference/users#list-users) +* [Obtener un usuario](/rest/reference/users#get-a-user) + +{% if currentVersion == "free-pro-team@latest" %} +##### Ejecuciones de Flujo de Trabajo + +* [Listar las ejecuciones de flujode trabajo de un repositorio](/rest/reference/actions#list-workflow-runs-for-a-repository) +* [Obtener una ejecución de flujo de trabajo](/rest/reference/actions#get-a-workflow-run) +* [Cancelar una ejecución de flujo de trabajo](/rest/reference/actions#cancel-a-workflow-run) +* [Descargar las bitácoras de ejecución de flujo de trabajo](/rest/reference/actions#download-workflow-run-logs) +* [Borrar las bitácoras de ejecución de flujo de trabajo](/rest/reference/actions#delete-workflow-run-logs) +* [Re-ejecutar un flujo de trabajo](/rest/reference/actions#re-run-a-workflow) +* [Listar las ejecuciones de flujo de trabajo](/rest/reference/actions#list-workflow-runs) +* [Obtener las estadísticas de uso de las ejecuciones de flujo de trabajo](/rest/reference/actions#get-workflow-run-usage) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +##### Flujos de trabajo + +* [Listar los flujos de trabajo del repositorio](/rest/reference/actions#list-repository-workflows) +* [Obtener un flujo de trabajo](/rest/reference/actions#get-a-workflow) +* [Obtener el uso de un flujo de trabajo](/rest/reference/actions#get-workflow-usage) +{% endif %} diff --git a/translations/es-ES/content/developers/apps/index.md b/translations/es-ES/content/developers/apps/index.md new file mode 100644 index 0000000000000..c9f3e87bc1835 --- /dev/null +++ b/translations/es-ES/content/developers/apps/index.md @@ -0,0 +1,56 @@ +--- +title: Aplicaciones +intro: Puedes automatizar y transmitir tu flujo de trabajo si creas tus propias apps. +redirect_from: + - /early-access/integrations/ + - /early-access/integrations/authentication/ + - /early-access/integrations/install-an-integration/ + - /apps/adding-integrations/ + - /apps/building-integrations/setting-up-a-new-integration/about-integrations/ + - /aplicaciones + - /v3/integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% topic_link_in_list /getting-started-with-apps %} + {% link_in_list /about-apps %} + {% link_in_list /activating-beta-features-for-apps %} + {% link_in_list /differences-between-github-apps-and-oauth-apps %} + {% link_in_list /migrating-oauth-apps-to-github-apps %} + {% link_in_list /setting-up-your-development-environment-to-create-a-github-app %} +{% topic_link_in_list /building-github-apps %} + {% link_in_list /creating-a-github-app %} + {% link_in_list /setting-permissions-for-github-apps %} + {% link_in_list /authenticating-with-github-apps %} + {% link_in_list /identifying-and-authorizing-users-for-github-apps %} + {% link_in_list /rate-limits-for-github-apps %} + {% link_in_list /refreshing-user-to-server-access-tokens %} + {% link_in_list /creating-a-github-app-from-a-manifest %} + {% link_in_list /creating-a-github-app-using-url-parameters %} + {% link_in_list /creating-a-custom-badge-for-your-github-app %} +{% topic_link_in_list /managing-github-apps %} + {% link_in_list /installing-github-apps %} + {% link_in_list /modifying-a-github-app %} + {% link_in_list /editing-a-github-apps-permissions %} + {% link_in_list /making-a-github-app-public-or-private %} + {% link_in_list /suspending-a-github-app-installation %} + {% link_in_list /transferring-ownership-of-a-github-app %} + {% link_in_list /deleting-a-github-app %} +{% link_in_list /deleting-a-github-app %} + {% link_in_list /creating-an-oauth-app %} + {% link_in_list /authorizing-oauth-apps %} + {% link_in_list /scopes-for-oauth-apps %} + {% link_in_list /creating-a-custom-badge-for-your-oauth-app %} +{% topic_link_in_list /managing-oauth-apps %} + {% link_in_list /modifying-an-oauth-app %} + {% link_in_list /transferring-ownership-of-an-oauth-app %} + {% link_in_list /troubleshooting-authorization-request-errors %} + {% link_in_list /troubleshooting-oauth-app-access-token-request-errors %} + {% link_in_list /deleting-an-oauth-app %} +{% topic_link_in_list /guides %} + {% link_in_list /using-the-github-api-in-your-app %} + {% link_in_list /using-content-attachments %} + {% link_in_list /creating-ci-tests-with-the-checks-api %} diff --git a/translations/es-ES/content/developers/apps/installing-github-apps.md b/translations/es-ES/content/developers/apps/installing-github-apps.md new file mode 100644 index 0000000000000..fb736c2d285d7 --- /dev/null +++ b/translations/es-ES/content/developers/apps/installing-github-apps.md @@ -0,0 +1,63 @@ +--- +title: Instalar GitHub Apps +intro: 'Cuando tu app es pública, cualquiera puede instalarla en su repositorio a través de {% if currentVersion == "free-pro-team@latest" %} the {% data variables.product.prodname_marketplace %} o {% endif %}de una URL de instalación. Cuando tu app es privada, solo puedes instalarla en los repositorios que te pertenezcan.' +redirect_from: + - /apps/installing-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Tu {% data variables.product.prodname_github_app %} tendra acceso a cualquier repositorio que ella misma cree, aún si alguien la instala únicamente en repositorios selectos. + +{% endnote %} + +### Instalar tu GitHub App privada en tu repositorio + +Una vez que creas una GitHub App privada, puedes instalarla en uno de tuos repositorios de usuario o de organización. Para obtener más información, consulta la sección "[Flujo de instalación privada](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)". + +1. Selecciona tu app desde la [página de configuración de GitHub Apps](https://github.com/settings/apps). +2. En la barra lateral izquierda, da clic en **Instalar App**. +3. Da clic en **Instalar** junto a la cuenta de usuario o de organización que contiene el repositorio correcto. +4. Instala al app en todos los repositorios o selecciona los repositorios por separado. ![Permisos de instalación de la aplicación](/assets/images/install_permissions.png) +5. Una vez instalada, verás las opciones de configuración para la app en tu cuenta seleccionada. Puedes hacer cambios aquí, o repetir los pasos anteriores para instalar la app en otra cuenta. + +{% if currentVersion == "free-pro-team@latest" %} +### Ofrecer tu app en GitHub Marketplace + +Puedes ofrecer una versión gratuita o pagada de tu app en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), en donde las personas pueden uscar y ver los detalles de la misma. {% data variables.product.prodname_marketplace %} instala automáticamente una GitHub App cuando se completa una orden. + +Consulta la sección "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)" para aprender más acerca de listar tu app en {% data variables.product.prodname_marketplace %}. + +Para aprender más acerca de cómo los usuarios pueden instalar tu app desde {% data variables.product.prodname_marketplace %}, consulta la sección "[Comprar e instalar apps en GitHub Marketplace](/articles/purchasing-and-installing-apps-in-github-marketplace)". + +{% endif %} + +### Permitir que las personas instalen tu app pública en su repositorio + +Puedes habilitar a otras personas para que instalen tu app pública si les proporcionas la URL de instalación en lugares como la página principal de tu app. Entonces puedes dirigirlos a la página principal de tu app desde la página de llegada en GitHub. + + Si estás migrándote desde una App de OAuth hacia una GitHub App, puedes utilizar los parámetros de consulta para preseleccionar los repositorios y la cuenta cuando instalen esta GitHub App. Consulta la secicón "[Migrar de Apps de OAuth a GitHub Apps](/apps/migrating-oauth-apps-to-github-apps/)" para aprender más. + +Estos pasos asumen que has [creado una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/): + +1. Desde la [Página de configuración de GitHub Apps](https://github.com/settings/apps), selecciona la app pública que quieres configurar para que los demás la instalen. +2. En "URL de la Página Principal", teclea la URL de la página principal de tu app y da clic en **Guardar cambios**. ![URL de la página de inicio](/assets/images/github-apps/github_apps_homepageURL.png) +3. GitHub proporciona una página de llegada para tu app, la cual incluye un enlace a la "URL de la Página Principal" de la misma. Para visitar la página de llegada en GitHub, copia la URL de "Enlace público" y pégala en un buscador. ![Enlace público](/assets/images/github-apps/github_apps_public_link.png) +4. Crear una página principal para tu app que incluya la URL de instalación de la misma: `{% data variables.product.oauth_host_code %}/apps//installations/new`. + +### Autorizar a los usuarios durante la instalación + +Puedes simplificar el proceso de autorización si lo completas durante la instalación de la app. Para hacerlo, sleecciona **Solicitar la autorización del usuario (OAuth) durante la instalación** al crear o modificar tu app en GitHub. Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" para aprender más al respecto. + +Una vez que alguien instale tu app, necesitarás obtener un token de acceso para el usuario. Consulta los pasos 2 y 3 en la sección "[Indentificar a los usuarios en tu sitio](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" para aprender más al respecto. +### Preservar el estado de una aplicación durante su instalación + +Puedes proporcionar un parámetro de `state` en la URL de instalación de una app para preservar el estado de la página de la aplicación y regresar a las personas a ese estado después de que instalen, se autentiquen, o acepten actualizaciones de tu GitHub App. Por ejemplo, puedes utilizar el `state` para correlacionar una instalación para el usuario o cuenta. + +Para preservar el estado, agrégalo a la URL de instalación: + +`{% data variables.product.oauth_host_code %}/apps//installations/new?state=AB12t` diff --git a/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md b/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md new file mode 100644 index 0000000000000..c077e1fa1ed55 --- /dev/null +++ b/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md @@ -0,0 +1,36 @@ +--- +title: Hacer pública o privada a una GitHub App +intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}' +redirect_from: + - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/ + - /apps/building-github-apps/installation-options-for-github-apps/ + - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option/ + - /apps/managing-github-apps/changing-a-github-app-s-installation-option/ + - /apps/managing-github-apps/making-a-github-app-public-or-private +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para obtener información sobre la autenticación, consulta la sección "[Autenticarse con las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". + +### Flujo de instalación pública + +Los flujos de instalación pública tienen una página de llegada en donde los usuarios comenzarán el flujo de instalación. Este enlace se proprociona en el campo "enlace público" cuando configuras tu GitHub App. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/apps/installing-github-apps/)". + +### Flujo de instalación privada + +Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Las GitHub Apps privadas o internas solo se pueden instalar en la cuenta de usuario o de organización del propietario. + +### Cambiar el quién puede instalar tu GitHub App + +Para cambiar quién puede instalar una GitHub App: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +3. Selecciona la GitHub App cuya opción de instalación quieras cambiar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +{% data reusables.user-settings.github_apps_advanced %} +5. Dependiendo de la opción deinstalación de tu GitHub App, da clic ya sea en **Convertir en pública** o en **Convertir en interna**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Dependiendo de la opción de instalación de tu GitHub App, da clic ya sea en **Sí, convertir esta GitHub App en pública** o en **Sí, convertir esta GitHub App en interna**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/es-ES/content/developers/apps/managing-github-apps.md b/translations/es-ES/content/developers/apps/managing-github-apps.md new file mode 100644 index 0000000000000..a31b60d5d4f6a --- /dev/null +++ b/translations/es-ES/content/developers/apps/managing-github-apps.md @@ -0,0 +1,13 @@ +--- +title: Adminsitrar las GitHub Apps +intro: 'Después de que creas y registras una GitHub App, puedes hacer modificaciones a la misma, cambiar sus permisos, transferir la propiedad, y borrarla.' +mapTopic: verdadero +redirect_from: + - /apps/building-integrations/managing-github-apps/ + - /apps/managing-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps.md b/translations/es-ES/content/developers/apps/managing-oauth-apps.md new file mode 100644 index 0000000000000..f2fc4b0b993ad --- /dev/null +++ b/translations/es-ES/content/developers/apps/managing-oauth-apps.md @@ -0,0 +1,13 @@ +--- +title: Adminsitrar las Apps de OAuth +intro: 'Después de que creas y registras una App de OAuth, puedes hacerle modificaciones, cambiar sus permisos, transferir su propiedad y borrarla.' +mapTopic: verdadero +redirect_from: + - /apps/building-integrations/managing-oauth-apps/ + - /apps/managing-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md new file mode 100644 index 0000000000000..fe64cdbe2ec08 --- /dev/null +++ b/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -0,0 +1,101 @@ +--- +title: Migrar de Apps de OAuth a GitHub Apps +intro: 'Aprende sobre las ventajas de migrarte de tu {% data variables.product.prodname_oauth_app %} a una {% data variables.product.prodname_github_app %} y sobre como migrar una {% data variables.product.prodname_oauth_app %} que no se encuentre listada en {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/migrating-oauth-apps-to-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Este artículo proporciona los lineamientos para los integradores existentes que están considerando migrarse de una App de OAuth a una GitHub App. + +### Razones para cambiar a GitHub Apps + +Las [GitHub Apps](/apps/) son la forma recomendada de integrarse con GitHub, ya que ofrecen muchas ventajas sobre una integración puramente basada en OAuth: + +- [Permisos detallados](/apps/differences-between-apps/#requesting-permission-levels-for-resources) que se enfocan en la información específica a la que puede acceder una GitHub App, lo cual permite que las personas y organizaciones la utilicen más ampliamente con políticas de seguridad a diferencia de las Apps de OAuth, las cuales no se pueden limitar con permisos. +- [Tokens de vida corta](/apps/differences-between-apps/#token-based-identification) que proporcionan un método de autenticación más segura qu la de los tokens de OAuth. Un token de OAuth no caduca hasta que la persona que autorizó la App de OAuth revoque el token. Las GitHub Apps utilizan tokens que caducan rápidamente, lo cual permite tener una ventana de tiempo mucho menor para que se utilicen los tokens que se hayan puesto en riesgo, en caso de existir. +- [Webhooks integrados y centralizados](/apps/differences-between-apps/#webhooks) que reciben eventos para todos los repositorios y organizaciones a los cuales puede acceder la app. Por el contrario, las Apps de OAuth requieren configurar un webhook para cada repositorio y organización que sea accesible para el usuario. +- [Cuentas Bot](/apps/differences-between-apps/#machine-vs-bot-accounts) que no consument una plaza de {% data variables.product.product_name %} y permanecen instaladas aún cuando la persona que las instaló inicialmente deja la organización. +- El soporte integrado para OAuth aún estará disponible para las GitHub Apps que utilicen [terminales de usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). +- Los [límites de tasa de la API](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) dedicados para cuentas bot se escalarán con tu integración. +- Los propietarios de los repositorios pueden [Instalar GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) en repositorios de organización. Si la configuración de una GitHub App tiene permisos que solicitan los recursos de una organización, el propietario de dicha organización debe aprobar la instalación. +- El apoyo de la comunidad de código abierto se encuentra disponible mediante las [bibliotecas Octokit](/rest/overview/libraries) y mediante otros marcos de trabajo, tales como el [Probot](https://probot.github.io/). +- Los integradores que crean GitHub Apps tienen la oportunidad para adoptar un acceso temprano a las API. + +### Convertir una App de OAuth en una GitHub App + +Estos lineamientos asumen que registraste una App de OAuth{% if currentVersion == "free-pro-team@latest" %} que puede estar o no listada en GitHub Marketplace{% endif %}. A nivel superior, necesitarás llevar a cabo los siguientes pasos: + +1. [Revisar las terminales de la API disponibles para las Github Apps](#review-the-available-api-endpoints-for-github-apps) +1. [Diseñar con apego a los límites de tasa de la API](#design-to-stay-within-api-rate-limits) +1. [Registrar una GitHub App nueva](#register-a-new-github-app) +1. [Determinar los permisos que necesitará tu app](#determine-the-permissions-your-app-requires) +1. [Suscribirte a los webhooks](#subscribe-to-webhooks) +1. [Entender los diferentes métodos de autenticación](#understand-the-different-methods-of-authentication) +1. [Dirigir a los usuarios a instalar tu GitHub App en los repositorios](#direct-users-to-install-your-github-app-on-repositories) +1. [Eliminar cualquier gancho innecesario en los repositorios](#remove-any-unnecessary-repository-hooks) +1. [Animar a los usuarios a que revoquen el acceso a tu App de OAuth](#encourage-users-to-revoke-access-to-your-oauth-app) + +#### Revisar las terminales de la API disponibles para las Github Apps + +Mientras que la mayoría de las terminales de la [API de REST](/rest) y de las consultas de [GraphQL](/graphql) están disponibles hoy en día para las GitHub Apps, aún estamos en el proceso de habilitar algunas de ellas. Revisa las [terminales disponibles de REST](/rest/overview/endpoints-available-for-github-apps) para garantizar que las terminales que necesitas sean compatibles con las GitHub Apps. Nota que algunas de las terminales de la API que están habilitadas para las GtiHub Apps permiten que éstas interactúen en nombre del usuario. Consulta la sección "[Solicitudes de usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para encontrar una lista de terminales disponibles para que una GitHub App se autentique como un usuario. + +Te recomendamos revisar la lista de terminales de la API que necesitas tan pronto como te sea posible. Por favor, comunícale a soporte si hay alguna terminal que requieras y que no esté habilitada aún para las {% data variables.product.prodname_github_app %}. + +#### Diseñar con apego a los límites de tasa de la API + +Las GitHub Apps utilizan [reglas móviles para los límites de tasa](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), las cuales pueden incrementar con base en la cantidad de repositorios y usuarios de la organización. Una GitHub App también puede hacer uso de [solicitudes condicionales](/rest#conditional-requests) o de solicitudes consolidadas si utiliza la [API de GraphQL V4](/graphql). + +#### Registrar una GitHub App nueva + +Una vez que hayas decidido hacer el cambio hacia GitHub Apps, necesitarás [crear una GitHub App nueva](/apps/building-github-apps/). + +#### Determinar los permisos que necesitará tu app + +Cuando registras tu GitHub App, necesitarás seleccionar los permisos que requiere cada terminal que se utilice en el código de tu app. Consulta la sección "[Permisos de la GitHub App](/rest/reference/permissions-required-for-github-apps)" para encontrar un listado de permisos que necesita cada terminal disponible para las GitHub Apps. + +En la configuración de tu GitHub App, puedes especificar si tu app necesita acceso de tipo `No Access`, `Read-only`, o `Read & Write` para cada tipo de permiso. Los permisos detallados le permiten a tu app obtener acceso específico a el subconjunto de datos que necesites. Te recomendamos especifcar el conjunto de datos más definido que sea posible, el cual proporcione la funcionalidad deseada. + +#### Suscribirte a los webhooks + +Después de que creaste una GitHub App nueva y seleccionaste sus permisos, puedes seleccionar los eventos de webhook a los cuales deseas suscribirte. Consulta la sección "[Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para aprender sobre cómo suscribirte a los webhooks. + +#### Entender los diferentes métodos de autenticación + +Las GitHub Apps utilizan principalmente una autenticación basada en tokens que caducan después de un periodo de tiempo corto, lo cual proporciona más seguirdad que un token de OAuth que no caduca. Es importante entender los diferentes métodos de autenticación que tienes disponibles cuando necesitas utilizarlos: + +* Un **Token Web de JSON (JWT)** [ se autentica como la GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). Por ejemplo, puedes autenticarte con un **JWT** para obtener los detalles de instalación de la aplicación o para intercambiar dicho **JWT** por un **token de acceso a la instalación**. +* Un **token de acceso de la instalación** [se autentica como una instalación específica de tu GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (también se les conoce como solicitudes de servidor a servidor). Por ejemplo, puedes autenticarte con un **token de acceso de la instalación** para abrir un informe de problemas o para proporcionar retroalimentación en una solicitud de extracción. +* Un **Token de acceso de OAuth** puede [autenticarse como un usuario de tu GitHub App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (también se les conoce como solicitudes de usuario a servidor). Por ejemplo, puedes utilizar un token de acceso de OAuth para autenticarte como un usuario cuando una GitHub App necesite verificar la identidad del usuario o actuar en nombre de un usuario. + +El escenario más común es autenticarse como una instalación específica utilizando un **token de acceso de la instalación**. + +#### Dirigir a los usuarios a instalar tu GitHub App en los repositorios + +Una vez que hiciste la transición de una App de OAuth a una GitHub App, necesitarás informar a los usuarios que esta GitHub App se encuentra disponible para su instalación. Por ejemplo, puedes incluir un enlace de instalación para la GitHub App en un letrero de llamada a la acción dentro de tu aplicación. Para facilitar la transición, puedes utilizar parámetros de consulta para identificar a la cuenta de usuario o de organización que esté pasando por el flujo de instalación para tu GitHub App y pre-seleccionar cualquier repositorio al que tuviera acceso tu App de OAuth. Esto les permite a los usuarios instalar tu GitHub App en los repositorios a los que ya tengas acceso. + +##### Parámetros de consulta + +| Nombre | Descripción | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `suggested_target_id` | **Requerido**: La ID del usuario u organización que está instalando tu GitHub App. | +| `repository_ids[]` | Matriz de las ID de repositorio. Si se omite, seleccionaremos todos los repositorios. La cantidad máxima de repositorios que se pueden pre-seleccionar es de 100. | + +##### URL de Ejemplo +``` +https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID +``` + +Necesitarás reemplazar a `YOUR_APP_NAME` con el nombre de tu GitHub App, a `ID_OF_USER_OR_ORG` con la ID de tu usuario u organización destino, e incluir hasta 100 ID de repositorio (`REPO_A_ID` y `REPO_B_ID`). Para obtener una lista de repositorios a los cuales tiene acceso tu aplicación de OAuth, utiliza las terminales [Listar repositorios para el usuario autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) y [Listar repositorios de la organización](/rest/reference/repos#list-organization-repositories). + +#### Eliminar cualquier gancho innecesario en los repositorios + +Una vez que ti GitHub App se haya instalado en un repositorio, deberías eliminar cualquier webhook innecesario que haya creado tu App tradicional de OAuth. Si ambas apps están instaladas en un repositorio, puede que se duplique la funcionalidad para el usuario. Para eliminar los webhooks, puedes escuchar al [webhook de `installation_repositories`](/webhooks/event-payloads/#installation_repositories) con la acción `repositories_added` y al [webhook para borrar un repositorio](/rest/reference/repos#delete-a-repository-webhook) en los repositorios que creó tu App de OAuth. + +#### Animar a los usuarios a que revoquen el acceso a tu App de OAuth + +En medida en que vaya creciendo tu base de instalación de la GitHub App, considera exhortar a tus usuarios para [revocar el acceso](/articles/authorizing-oauth-apps/) a la integración tradicional de OAuth. diff --git a/translations/es-ES/content/developers/apps/modifying-a-github-app.md b/translations/es-ES/content/developers/apps/modifying-a-github-app.md new file mode 100644 index 0000000000000..b7931fd7262c9 --- /dev/null +++ b/translations/es-ES/content/developers/apps/modifying-a-github-app.md @@ -0,0 +1,18 @@ +--- +title: Modificar una GitHub App +intro: '{% data reusables.shortdesc.modifying_github_apps %}' +redirect_from: + - /apps/building-integrations/managing-github-apps/modifying-a-github-app/ + - /apps/managing-github-apps/modifying-a-github-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +{% data reusables.user-settings.modify_github_app %} +5. En "Información básica", modifica la información que quieras cambiar para la GitHub App. ![Sección de información básica para tu GitHub App](/assets/images/github-apps/github_apps_basic_information.png) +6. Haz clic en **Guardar cambios**. ![Botón para guardar los cambios en tu GitHub App](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/es-ES/content/developers/apps/modifying-an-oauth-app.md b/translations/es-ES/content/developers/apps/modifying-an-oauth-app.md new file mode 100644 index 0000000000000..b0f8d461a1107 --- /dev/null +++ b/translations/es-ES/content/developers/apps/modifying-an-oauth-app.md @@ -0,0 +1,19 @@ +--- +title: Modificar una App de OAuth +intro: '{% data reusables.shortdesc.modifying_oauth_apps %}' +redirect_from: + - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app/ + - /apps/managing-oauth-apps/modifying-an-oauth-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +{% data reusables.user-settings.modify_oauth_app %} +1. Modifica la +información de {% data variables.product.prodname_oauth_app %} que quieres cambiar. +{% data reusables.user-settings.update_oauth_app %} diff --git a/translations/es-ES/content/developers/apps/rate-limits-for-github-apps.md b/translations/es-ES/content/developers/apps/rate-limits-for-github-apps.md new file mode 100644 index 0000000000000..228ec4930911f --- /dev/null +++ b/translations/es-ES/content/developers/apps/rate-limits-for-github-apps.md @@ -0,0 +1,57 @@ +--- +title: Límites de tasa para las GitHub Apps +intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' +redirect_from: + - /early-access/integrations/rate-limits/ + - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps/ + - /apps/building-github-apps/rate-limits-for-github-apps/ + - /apps/building-github-apps/understanding-rate-limits-for-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Solicitudes de servidor a servidor + +{% if currentVersion == "free-pro-team@latest" %} + +Se aplicarán límites de tasa diferentes para las solicitudes de servidor a servidor en las {% data variables.product.prodname_github_app %}s si la app se encuentra instalada en organizaciones o repositorios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}. + +#### Límites de tasa normales de servidor a servidor + +{% endif %} + +{% data reusables.apps.api-rate-limits-non-ghec %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Límites de tasa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %} + +Las {% data variables.product.prodname_github_app %}s que se instalen en un repositorio de organización que pertenezca a una cuenta de {% data variables.product.prodname_ghe_cloud %} y haga solicitudes de servidor a servidor tiene un límite de tasa de 15,000 solicitudes por hora. + +{% endif %} + +### Solicitudes de usuario a servidor + +Las {% data variables.product.prodname_github_app %} también pueden actuar [en nombre de un usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps) al hacer solicitudes de usuario a servidor. + +{% if currentVersion == "free-pro-team@latest" %} + +Se aplicarán límites de tasa diferentes para las solicitudes de usuario a servidor en las {% data variables.product.prodname_github_app %}s si la app se encuentra instalada en organizaciones o repositorios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %} y el usuario autenticado también pertenece a dicha cuenta de {% data variables.product.prodname_ghe_cloud %}. + +#### Límites de tasa normales de usuario a servidor + +{% endif %} + +Las solicitudes de usuario a servidor tienen un límite de tasa de 5,000 solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorizó éste usuario, los tokens de acceso personal que le pertenecen, y las solicitudes que se autenticaron con su{% if currentVersion == "github-ae@latest" %} token{% else %} nombre de usuario y contraseña{% endif %} comparten la misma cuota de 5,000 solicitudes por hora para dicho usuario. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Límites de tasa de usuario a servidor de {% data variables.product.prodname_ghe_cloud %} + +Cuando un usuario pertenece a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes de usuario a servidor para los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite de tasa de 15,000 solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorizó este usuario, los tokens de acceso personal que le pertenezcan, y las solicitudes de {% data variables.product.prodname_ghe_cloud %} que se autenticaron con el nombre de usuario y contraseña del mismo, comparten la misma cuota de 5,000 solicitudes por hora para dicho usuario. + +{% endif %} + +Para obtener información más detallada acerca de los límites de tasa, consulta la sección "[Limitaciones a las tasas](/rest/overview/resources-in-the-rest-api#rate-limiting)" para la API de REST y "[Limitaciones a los recursos](/graphql/overview/resource-limitations)" para la API de GraphQL. diff --git a/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md new file mode 100644 index 0000000000000..7a9ad0b1f3b4c --- /dev/null +++ b/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -0,0 +1,72 @@ +--- +title: Actualizar los tokens de acceso de usuario a servidor +intro: 'Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad.' +redirect_from: + - /apps/building-github-apps/refreshing-user-to-server-access-tokens +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +--- + + +{% data reusables.pre-release-program.expiring-user-access-tokens-beta %} + + +### Acerca de los tokens de acceso de usuario con caducidad + +Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad. Para obtener más información sobre cómo crear solicitudes de usuario a servidor, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". + +La caducidad de los tokens se alcanza después de 8 horas. Cuando recibes un token nuevo para el acceso de usuario a servidor, la respuesta también contendrá un token de actualización, el cual se puede intercambiar por un token de usuario nuevo y un token de actualización. Los tokens de actualización son válidos por 6 meses. + +### Renovar un token de usuario con un token de actualización + +Para renovar un token de acceso de usuario a servidor que esté por caducar, puedes intercambiar el `refresh_token` por un token de acceso nuevo y un `refresh_token`. + + `POST https://github.com/login/oauth/access_token` + +Esta solicitud de rellamada te enviará un token de acceso y un token de actualización nuevos. Esta solicitud de rellamada es similar a la solicitud de OAuth que utilizarías para intercambiar un `code` temporal para un token de acceso. Para obtener más información, consulta las secciones "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" y "[Información básica sobre la autenticación](/rest/guides/basics-of-authentication#providing-a-callback)". + +#### Parámetros + +| Nombre | Type | Descripción | +| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `refresh_token` | `secuencia` | **Requerido.** El token que se genera cuando el dueño de la {% data variables.product.prodname_github_app %} habilita los tokens con caducidad y emite un token de acceso de usuario nuevo. | +| `grant_type` | `secuencia` | **Requerido.** El valor debe ser `refresh_token` (se requiere en la especificación de OAuth). | +| `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu {% data variables.product.prodname_github_app %}. | +| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente para tu {% data variables.product.prodname_github_app %}. | + +#### Respuesta + +```json +{ + "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "expires_in": "28800", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token_expires_in": "15811200", + "scope": "", + "token_type": "bearer" +} +``` +### Configurar los tokens de usuario con caducidad para una GitHub App existente + +Puedes habilitar o inhabilitar los tokens de autorización de usuario a servidor desde los ajustes de tu {% data variables.product.prodname_github_app %}. + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Da clic en la opción**Editar** junto a la {% data variables.product.prodname_github_app %} que escogiste. ![Configuración para editar una GitHub App](/assets/images/github-apps/edit-test-app.png) +5. En la barra lateral izquierda, da clic en **Características del Beta**. ![Opción de menú de Características del Beta](/assets/images/github-apps/beta-features-option.png) +6. Junto a "caducidad de token de usuario a servidor", da clic en **Unirse** o en **No unirse**. Esta característica podría tardar un par de segundos para su aplicación. + +### Decidir no unirse a los tokens con caducidad para las GitHub Apps nuevas + +Cuando creas una {% data variables.product.prodname_github_app %}, ésta utilizará predeterminadamente los tokens de acceso de usuario a servidor con caducidad. + +Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducidad, puedes deseleccionar la opción "Poner caducidad en los tokens de autorización de usuario" en la página de ajustes de la app. + +![Opción para unirse a los tokens de usuario con caducidad durante la configuración de las GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) + +Las {% data variables.product.prodname_github_app %} existentes que utilicen tokens de autorización de usuario a servidor solo se verán afectadas por este flujo nuevo cuando el propietario de la app habililte la caducidad de los tokens para la app en cuestión. + +Habilitar los tokens de usuario con caducidad para las {% data variables.product.prodname_github_app %} existentes requiere de enviar a los usuarios a través del flujo de OAuth para re-emitir tokens de usuario nuevos que caducarán en 8 horas y que harán una solicitud con el token de actualización para obtener un token de acceso y un token de actualización nuevos. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". diff --git a/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md new file mode 100644 index 0000000000000..2c32a0de01840 --- /dev/null +++ b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md @@ -0,0 +1,101 @@ +--- +title: Alcances para las Apps de 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/ + - /apps/building-oauth-apps/scopes-for-oauth-apps/ + - /apps/building-oauth-apps/understanding-scopes-for-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando estás configurando una App de OAuth en GitHub, los alcances solicitados se muestran al usuario en el formato de autorización. + +{% note %} + +**Nota:** Si estás creando una GitHub App, no necesitas proporcionar alcances en tu solicitud de autorización. Para obtener más información sobre esto, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/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" %} +Si tu +{% data variables.product.prodname_oauth_app %} no tiene acceso a un buscador, tal como una herramienta de CLI, entonces no necesitas especificar un alcance para que los usuarios se autentiquen en tu app. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". +{% endif %} + +Verifica los encabezados para ver qué alcances de OAuth tienes, y cuáles acepta la acción de la API: + +```shell +$ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I +HTTP/1.1 200 OK +X-OAuth-Scopes: repo, user +X-Accepted-OAuth-Scopes: user +``` + +* `X-OAuth-Scopes` lista los alcances que tu token tiene autorizados. +* `X-Accepted-OAuth-Scopes` lista los alcances que revisrá la acción. + +### Alcances disponibles + +| Nombre | Descripción | +| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **`(no scope)`** | Otorga acceso de solo lectura a la información pública (incluyendo la información del perfil de usuario público, información de repositorio público, y gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| **`site_admin`** | Otorga a los administradores de sitio acceso a las [Terminales de la API para la Administración de {% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} +| **`repo`** | Otorga acceso completo a los repositorios públicos y privados. Esto incluye acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio y de organización, invitaciones, colaboradores, agregar membrecías de equipo, estados de despliegue, y webhooks de repositorio para aquellos repositorios privados y públicos y para las organizaciones. También otorga la capacidad de administrar proyectos de usuario. | +|  `repo:status` | Otorga acceso de lectura/escritura en los estados de confirmación de los repositorios privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de las confirmaciones en repositorios privados *sin* otorgarles acceso al código. | +|  `repo_deployment` | Otorga acceso a los [estados de despliegue](/rest/reference/repos#deployments) para los repositorios públicos y privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de despliegue *sin* otorgarles acceso al código. | +|  `public_repo` | Limita el acceso a los repositorios públicos. Esto incluye el acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio, colaboradores y estados de despliegue para los repositorios públicos y para las organizaciones. También se requiere para marcar a los repositorios públicos con una estrella. | +|  `repo:invite` | Otorga capacidades de aceptar/rechazar las invitaciones para colaborar con un repositorio. Este alcance solo es necesario para otorgar a otros usuarios o servicios acceso a las invitaciones *sin* otorgar acceso al código.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | Grants:
    read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
    This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +| **`admin:repo_hook`** | Otorga acceso de lectura, escritura, ping y borrado a los ganchos de los repositorios privados y públicos. Los alcances `repo` y `public_repo` otorgan acceso completo a los repositorios, incluyendo a los ganchos de éstos. Utiliza el alcance `admin:repo_hook` para limitar el acceso únicamente a los ganchos de los repositorios. | +|  `write:repo_hook` | Otorga acceso de lectura, escritura y ping a los ganchos en los repositorios públicos o privados. | +|  `read:repo_hook` | Otorga acceso de lectura y de ping a los ganchos en los repositorios privados o públicos. | +| **`admin:org`** | Para administrar totalmente la organización y sus equipos, proyectos y membrecías. | +|  `write:org` | Acceso de lectura y escritura para la membrecía de organización y de los equipos y para los proyectos de la organización. | +|  `read:org` | Acceso de solo lectura para la membrecía de organización y de los equipos y para los proyectos de la organización. | +| **`admin:public_key`** | Administrar totalmente las llaves públicas. | +|  `write:public_key` | Crear, listar y ver los detalles de las llaves públicas. | +|  `read:public_key` | Listar y ver los detalles para las llaves públicas. | +| **`admin:org_hook`** | Otorga acceso de lectura, escritura, ping y borrado para los ganchos de la organización. **Nota:** Los tokens de OAuth solo podrán realizar estas acciones en los ganchos de la organización los cuales haya creado la App de OAuth. Los tokens de acceso personal solo podrán llevar a cabo estas acciones en los ganchos de la organización que cree un usuario. | +| **`gist`** | Otorga acceso de escritura a los gists. | +| **`notificaciones`** | Otorga:
    * acceso de lectura a las notificaciones de un usuario
    * acceso de marcar como leído en los hilos
    * acceso de observar y dejar de observar en un repositorio, y
    * acceso de lectura, escritura y borrado para las suscripciones a los hilos. | +| **`user`** | Otorga acceso de lectura/escritura únicamente para la información de perfil. Este alcance incluye a `user:email` y `user:follow`. | +|  `read:user` | Otorga acceso para leer los datos de perfil de un usuario. | +|  `user:email` | Otorga acceso de lectura para las direcciones de correo electrónico de un usuario. | +|  `user:follow` | Otorga acceso para seguir o dejar de seguir a otros usuarios. | +| **`delete_repo`** | Otorga acceso para borrar los repositorios administrables. | +| **`write:discussion`** | Permite el acceso de lectura y escritura para los debates de equipo. | +|  `read:discussion` | Permite el acceso de lectura para los debates de equipo.{% if currentVersion == "free-pro-team@latest" %} +| **`write:packages`** | Otorga acceso para cargar o publicar un paquete en el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Publicar un paquete](/github/managing-packages-with-github-packages/publishing-a-package)". | +| **`read:packages`** | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Instalar un paquete](/github/managing-packages-with-github-packages/installing-a-package)". | +| **`delete:packages`** | Otorga acceso para borrar paquetes del {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Borrar paquetes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} +| **`admin:gpg_key`** | Administra las llaves GPG totalmente. | +|  `write:gpg_key` | Crea, lista, y visualiza los detalles de las llaves GPG. | +|  `read:gpg_key` | Listar y visualizar los detalles para las llaves GPG.{% if currentVersion == "free-pro-team@latest" %} +| **`workflow`** | Otorga la capacidad de agregar y actualizar archivos del flujo de trabajo de las {% data variables.product.prodname_actions %}. Los archivos de flujo de trabajo pueden confirmarse sin este alcance en caso de que el mismo archivo (con la misma ruta y el mismo contenido) exista en otra rama en el mismo repositorio. Los archivos de flujo de trabajo pueden exponer `GITHUB_TOKEN` que pueden tener un conjunto diferente de alcances, consulta https://docs.github.com/en/free-pro-team@latest/actions/reference/autentication-in-a-workflow#permissions-for-the-github_token para obtener más detalles.{% endif %} + +{% note %} + +**Nota:** Tu App de OAuth puede solicitar los alcances en la redirección inicial. Puedes especificar varios alcances si los separas con un espacio: + + https://github.com/login/oauth/authorize? + client_id=...& + scope=user%20public_repo + +{% endnote %} + +### Alcances solicitados y otorgados + +El atributo `scope` lista los alcances adjuntos al token que otorgó el usuario. Normalmente, estos alcances serán idénticos a lo que solicitaste. Sin embargo, los usuarios pueden editar sus alcances, lo cual es efectivo para otorgar a tu organización menos accesos de lo que solicitaste originalmente. También, los usuarios puede editar los alcances de los tokens después de completar un flujo de OAuth. Debes estar consciente de esta posibilidad y ajustar el comportamiento de tu aplicación de acuerdo con esto. + +Es importante gestionar los casos de error en donde un usuario elige otorgarte menos acceso de lo que solicitaste originalmente. Por ejemplo, las aplicaciones pueden advertir o comunicar de cualquier otra forma a sus usuarios si experimentarán funcionalidad reducida o si serán incapaces de realizar alguna acción. + +También, las aplicaciones siempre pueden enviar nuevamente de regreso a los usuarios a través del flujo para obtener permisos adicionales, pero no olvides que dichos usuarios siempre pueden rehusarse a hacerlo. + +Revisa la sección [Guía de aspectos básicos de la autenticación](/guides/basics-of-authentication/), la cual proporciona consejos sobre la gestión de alcances modificables de los tokens. + +### Alcances normalizados + +Cuando solicites alcances múltiples, el token se guarda con una lista de alcances normalizada y descarta aquellos que se otro alcance solicitado incluya implícitamente. Por ejemplo, el solicitar `user,gist,user:email` dará como resultado un token con alcances de `user` y de `gist` únicamente, ya que el acceso que se otorga con el alcance `user:email` se incluye en el alcance `user`. diff --git a/translations/es-ES/content/developers/apps/setting-permissions-for-github-apps.md b/translations/es-ES/content/developers/apps/setting-permissions-for-github-apps.md new file mode 100644 index 0000000000000..4a38e489cd3c3 --- /dev/null +++ b/translations/es-ES/content/developers/apps/setting-permissions-for-github-apps.md @@ -0,0 +1,20 @@ +--- +title: Configurar los permisos para las GitHub Apps +intro: '{% data reusables.shortdesc.permissions_github_apps %}' +redirect_from: + - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps/ + - /apps/building-github-apps/permissions-for-github-apps/ + - /apps/building-github-apps/setting-permissions-for-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando creas una GitHub App, puedes seleccionar los permisos a los que necesita para acceder a los datos del usuario final. Los permisos también se pueden agregar y eliminar. Para obtener más información, consulta la sección "[Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". + +### Permisos de metadatos + +Predeterminadamente, las GitHub Apps tienen acceso de `Read-only` a las terminales de metadatos. Los metadatos son un conjunto de terminales de solo lectura que proporcionan información general acerca de los recursos a los que puede acceder la instalación autorizada. + +{% data reusables.apps.metadata-permissions %}Para encontrar una lista de terminales de metadatos, consulta la sección "[Permisos de metadatos](/rest/reference/permissions-required-for-github-apps#metadata-permissions)". diff --git a/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md new file mode 100644 index 0000000000000..3719cb937763b --- /dev/null +++ b/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -0,0 +1,449 @@ +--- +title: Configurar tu ambiente de desarrollo para crear una GitHub App +intro: 'Aprende los fundamentos para extender y crear {% data variables.product.prodname_github_apps %} nuevas.' +redirect_from: + - /apps/quickstart-guides/setting-up-your-development-environment +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Introducción + +Esta guía te mostrará los pasos necesarios para configurar una GitHub App y para ejecutarla en un servidor. Las GitHub Apps necesitan algunos pasos de configuración para administrar eventos de webhook y así conectar el registro de la App en GitHub hacia tu código. La app en esta guía sirve como una base que puedes utilizar para extender y crear GitHub Apps nuevas. + +Al finalizar esta guía habrás registrado una GitHub App y habrás configurado un servidor web para recibir eventos de webhook. Aprenderás como utilizar una herramienta llamada Smee para capturar las cargas útiles de los webhooks y reenviarlas a tu ambiente de desarrollo local. La app de plantilla que configurarás en esta sección no hará nada especial aún, pero funcionará como un marco de trabajo que puedes utilizar para comenzar a escribir tu código de aplicaciones utilizando la API o para completar otras [guías de inicio rápido](/apps/quickstart-guides/). {% if currentVersion == "free-pro-team@latest" %}Puedes revisar los ejemplos exitosos de las apps en [GitHub Marketplace](https://github.com/marketplace) y en [Funciona con GitHub](https://github.com/works-with).{% endif %} + +Después de completar este proyecto entenderás cómo autenticarte como una GitHub App y como una instalación, así como la forma en que difieren estos métodos de autenticación. + +Aquí están los pasos que tomarás para configurar la plantilla de la GitHub App: + +1. [Inicia un canal nuevo de Smee](#step-1-start-a-new-smee-channel) +1. [Registrar una GitHub App nueva](#step-2-register-a-new-github-app) +1. [Guarda tu llave privada e ID de tu App](#step-3-save-your-private-key-and-app-id) +1. [Prepara el ambiente de ejecución](#step-4-prepare-the-runtime-environment) +1. [Revisar el código de la plantilla de la GitHub App](#step-5-review-the-github-app-template-code) +1. [Inicia el servidor](#step-6-start-the-server) +1. [Instala la app en tu cuenta](#step-7-install-the-app-on-your-account) + +{% data reusables.apps.app-ruby-guides %} + +### Prerrequisitos + +Puede que te sea útil tener un entendimiento básico de lo siguiente: + +* [GitHub Apps](/apps/about-apps) +* [Webhooks](/webhooks) +* [El lenguaje de programación Ruby](https://www.ruby-lang.org/en/) +* [Las API de REST](/rest) +* [Sinatra](http://sinatrarb.com/) + +Pero puedes seguir esta guía sin importar tu nivel de experiencia. ¡Colocaremos enlaces para la información que requieras en cada fase! + +Antes de comenzar, necesitarás clonar el repositorio con el código de la plantilla que se utiliza en esta guía de inicio rápido. Abre tu app de terminal y encuentra el directorio en donde quieras almacenar el código. Ejecuta este comando para clonar el repositorio [Plantilla de GitHub App](https://github.com/github-developer/github-app-template): + +```shell +$ git clone https://github.com/github-developer/github-app-template.git +``` + +### Paso 1. Inicia un canal nuevo de Smee + +Para ayudar a que GitHub envíe webhooks a tu máquina local sin exponerla al internet, puedes utilizar una herramienta llamada Smee. Primero, dirígete a https://smee.io y da clic en **Iniciar un canal nuevo**. Si ya estás a gusto con otras herramientas que exponen tu máquina local al internet como [ngrok](https://dashboard.ngrok.com/get-started) o [localtunnel](https://localtunnel.github.io/www/), siéntete libre para utilizarlas. + +![El botón de nuevo canal de Smee](/assets/images/smee-new-channel.png) + +El iniciar un canal de Smee nuevo crea un dominio único en donde GitHub puede enviar cargas útiles de webhooks. Necesitas saber cuál es este dominio para continuar con el siguiente paso. Aquí hay un ejemplo de un dominio único en `https://smee.io/qrfeVRbFbffd6vD`: + +![Un canal de Smee único](/assets/images/smee-unique-domain.png) + +Posteriormente, regresa a la terminal y sigue estos pasos para ejecutar el cliente de la interface de línea de comandos (CLI) de Smee: + +{% note %} + +**Nota:** Los siguientes pasos son ligeramente diferentes que las instrucciones de "Utilizar la CLI" que encuentras en la página de tu canal de Smee. **No** necesitas seguir las instrucciones de las secciones "Utilizar el cliente de Node.js" o de "Utilizar el soporte integrado de Probot". + +{% endnote %} + +1. Instalar el cliente: + + ```shell + $ npm install --global smee-client + ``` + +2. Ejecuta el cliente (reemplazando a `https://smee.io/qrfeVRbFbffd6vD` con tu propio dominio): + + ```shell + $ smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000 + ``` + + Deberías ver una salida como ésta: + + ```shell + Forwarding https://smee.io/qrfeVRbFbffd6vD to http://127.0.0.1:3000/event_handler + Connected https://smee.io/qrfeVRbFbffd6vD + ``` + +El comando `smee --url ` le dice a Smee que reenvíe todos los eventos de webhook que reciba el canal de Smee al cliente de Smee que se ejecuta en tu computadora. La opción `--path /event_handler` reenvía los eventos a la ruta `/event_handler`, lo cual cubriremos en una [sección subsecuente](#step-5-review-the-github-app-template-code). La opción `--port 3000` especifica al puerto 3000, el cual es aquél que escuchará tu servidor. Si utilizas Smee, tu máquina no necesita estar abierta al internet público para recibir webhooks de GitHub. También puedes abrir la URL de Smee en tu buscador para inspeccionar las cargas útiles de los webhooks como vayan llegando. + +Te recomendamos dejar abierta esta ventana de terminal y mantener a Smee conectado mientras completas el resto de los pasos de esta guía. Aunque _puedes_ desconectar y reconectar el cliente de Smee sin perder tu dominio único (a diferencia de con ngrok), puede que te sea más fácil dejarlo conectado y llevar a cabo otras tareas en la línea de comandos en una ventana diferente de la terminal. + +### Paso 2. Registrar una GitHub App nueva + +Si aún no tienes una cuenta de GitHub, ahora es un [buen momento para unirte](https://github.com/join). ¡No te olvides de verificar tu dirección de correo electrónico antes de continuar! Para registrar una app nueva, visita la [página de configuración de la app](https://github.com/settings/apps) en tu perfil de GitHub, y da clic en **GitHub App nueva**. + +![El sitio web de Github, mostrando la **App Nueva**](/assets/images/new-app.png) + +Verás un formato en el cual puedes ingresar detalles sobre tu app. Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" para obtener información general acerca de los campos de esta página. Para los fines de esta guía, necesitaras ingresar datos específicos en unos cuantos campos: + +{% note %} + +**Nota:** Siempre puedes actualizar esta configuración más adelante para apuntar a un servidor hospedado. + +{% endnote %} + +* En "URL de la página principal", utiliza el dominio que emitió Smee. Por ejemplo: + + ![Formato completado con el dominio de Smee para la URL de una página principal](/assets/images/homepage-url.png) + +* Para la "URL del webhook", utiliza nuevamente el dominio que emitió Smee. Por ejemplo: + + ![Formato completado con el dominio de Smee para la URl de un webhook](/assets/images/webhook-url.png) + +* Para el "Secreto del webhook", crea una contraseña para asegurar las terminales de tu webhook. Este debería ser algo que solo tú (y GitHub, a través de este formulario) sepas. El secreto es importante, ya que estarás recibiendo cargas útiles desde el internet público, y utilizarás este secreto para verificar el remitente del webhook. Nota que la configuración de la GitHub App dice que el secreto de webhook es opcional, lo cual es verdad en la mayoría de los casos, pero para que funcione el código de la plantilla de la app, debes configurar un secreto de webhook. + + ![Formato completado con el secreto de un webhook](/assets/images/webhook-secret.png) + +* En la página de permisos & webhooks, puedes especificar un conjunto de permisos para tu app, los cuales determinan la cantidad de datos a los cuales tiene acceso la misma. Deja esta página con sus valores predeterminados. Si decides extender esta app de plantilla, puedes actualizar estos permisos más adelante. + +* En la parte inferior de la página de permisos & webhooks, especifica si es una app privada o pública. Esto se refiere a quién puede instalarla: ¿solo tú, o alguien más en general? Por el momento, deja la app como privada seleccionando **Solo en esta cuenta**. + + ![Privacidad de GitHub App](/assets/images/create_app.png) + +¡Da clic en **Crear GitHub App** para crear tu app! + +### Paso 3. Guarda tu llave privada e ID de tu App + +Después de que creas tu app, se te llevará de regreso a la [página de configuración de la app](https://github.com/settings/apps). Tienes dos cosas más para hacer aquí: + +* **Generar una llave privada para tu app.** Esto es necesario para autenticar tu app más adelante. Baja en la página y da clic en **Generar una llave privada**. Guarda el archivo PEM resultante (que tiene un nombre algo similar a _`app-name`_-_`date`_-private-key.pem) en un directorio en donde lo puedas volver a encontrar después. + + ![El diálogo de generación de la llave privada](/assets/images/private_key.png) + +* **Guardar la ID de app que GitHub le asignó a ésta.** Esto se necesita para preparar tu ambiente de ejecución. + + Tu número de ID para la app + +### Paso 4. Prepara el ambiente de ejecución + +Para mantener tu información segura, te recomendamos poner todos los secretos relacionados con tu app en la memoria de tu ordenador en donde tu app pueda encontrarlos, en vez de ponerlos directamente en tu código. Esta útil herramienta de desarrollo llamada [dotenv](https://github.com/bkeepers/dotenv) carga las variables de ambiente específicas del proyecto desde un archivo `.env` hacia `ENV`. Jamás ingreses tu archivo `.env` en GitHub. Este es un archivo local que almacena la información sensible que no quieres sacar al internet público. El archivo `.env` ya se incluye en el archivo [`.gitignore`](/articles/ignoring-files/) del repositorio para prevenir esto. + +El código de la plantilla que descargaste en la [Sección de pre-requisitos](#prerequisites) ya tiene un archivo de ejemplo llamado `.env-example`. Renombra el archivo de ejemplo de `.env-example` a `.env` o crea una copia del archivo `.env-example` llamada `.env`. No has instalado dotenv aún, pero lo instalarás más adelante en esta guía de inicio rápido cuando ejecutes `bundle install`. **Nota:** Las guías de inicio rápido que hagan referencia a los pasos en ésta guía podrían incluir variables de ambiente adicionales en el archivo `.env-example`. Referencia la guía de inicio rápido para el proyecto que clonaste en GitHub para obtener orientación para configurar estas variables de ambiente adicionales. + +Necesitas agregar estas variables al archivo `.env`: + +* _`GITHUB_PRIVATE_KEY`_: Agerga la llave privada que [generaste y guardaste anteriormente](#step-3-save-your-private-key-and-app-id). Abre el archivo `.pem` con un editor de texto o utiliza la línea de comandos para mostrar el contenido del archivo: `cat path/to/your/private-key.pem`. Copia todo el contenido del archivo como el valor de `GITHUB_PRIVATE_KEY` en tu archivo `.env`. **Nota:** Ya que el archivo PEM tiene más de una línea de código, necesitarás encerrar el valor entre comillas como en el siguiente ejemplo. +* _`GITHUB_APP_IDENTIFIER`_: Utiliza la ID de app que anotaste en la sección anterior. +* _`GITHUB_WEBHOOK_SECRET`_: Agrega tu secreto de webhook. + +Aquí se muestra un ejemplo de archivo `.env`: + +``` +PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- +... +HkVN9... +... +-----END DSA PRIVATE KEY-----" +GITHUB_APP_IDENTIFIER=12345 +GITHUB_WEBHOOK_SECRET=your webhook secret +``` + +### Paso 5. Revisar el código de la plantilla de la GitHub App + +Éste contiene código que todas las GitHub Apps necesitarán. Esta sección te muestra el código que ya existe en la plantilla de la GitHub App. No hay algún paso que necesites completar en esta sección. Si ya estás familiarizado con el código de la plantilla, puedes adelantarte al "[Paso 6. Iniciar el servidor](#step-6-start-the-server)". + +Abre el archivo `template_server.rb` en tu editor de texto favorito. Verás los comentarios a lo largo de este archivo, los cuales proporcionan contexto adicional para el código de la plantilla. Te recomendamos leer estos comentarios cuidadosamente, e incluso, agregar tus propios comentarios para complementar el código que escribas. + +En la parte superior del archivo verás `set :port 3000`, lo cual configura el puerto que se utiliza cuando inicias el servidor web para empatar con el puerto al cual redirigiste tus cargas útiles de webhook en el "[Paso 1. Iniciar un canal nuevo de Smee](#step-1-start-a-new-smee-channel)". + +El siguiente código que verás es la declaración `class GHApp < Sintra::Application`. Escribirás todo el código de tu GitHub App dentro de esta clase. + +Fuera de esta caja, la clase en la plantilla realiza lo siguiente: +* [Lee las variables de ambiente](#read-the-environment-variables) +* [Activa el inicio de sesión](#turn-on-logging) +* [Define un filtro del antes](#define-a-before-filter) +* [Define el gestor de ruta](#define-a-route-handler) +* [Define los métodos auxiliares](#define-the-helper-methods) + +#### Lee las variables de ambiente + +Lo primero que hace esta clase es leer las tres variables de ambiente que configuraste en el [Paso 4. Preparar el ambiente de ejecución](#step-4-prepare-the-runtime-environment)" y almacenarlas en variables para utilizarlas más adelante: + +``` ruby +# Expects that the private key in PEM format. Converts the newlines +PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) + +# Your registered app must have a secret set. The secret is used to verify +# that webhooks are sent by GitHub. +WEBHOOK_SECRET = ENV['GITHUB_WEBHOOK_SECRET'] + +# The GitHub App's identifier (type integer) set when registering an app. +APP_IDENTIFIER = ENV['GITHUB_APP_IDENTIFIER'] +``` + +#### Activa el inicio de sesión + +Posteriormente, hay un bloqueo de código que habilita el inicio de sesión durante el desarrollo, el cual es el ambiente predeterminado en Sinatra. Este código activa el inicio de sesión a nivel de `DEBUG` para mostrar una salida útil en la terminal mientras desarrollas la app: + +``` ruby +# Turn on Sinatra's verbose logging during development +configure :development do + set :logging, Logger::DEBUG +end +``` + +#### Define un filtro del antes + +Sintatra utiliza [filtros de anterioridad](https://github.com/sinatra/sinatra#filters) que te permiten ejecutar el código antes del gestor de la ruta. El bloque `before` en la plantilla llama a cuatro [métodos auxiliares](https://github.com/sinatra/sinatra#helpers). La app de plantilla define estos métodos auxiliares en una [sección posterior](#define-the-helper-methods). + +``` ruby +# Before each request to the `/event_handler` route +before '/event_handler' do + get_payload_request(request) + verify_webhook_signature + authenticate_app + # Authenticate the app installation in order to run API operations + authenticate_installation(@payload) +end +``` + +#### Define el gestor de la ruta + +Se incluye una ruta vacía en el código de la plantilla. Este código gestiona las solicitudes de tipo `POST` hacia la ruta `/event_handler`. No escribirás este gestor de evento en esta guía de inicio rápido, sino que verás las otras [guías de inicio rápido](/apps/quickstart-guides/) para encontrar ejemplos de como extender esta app de planitlla. + +``` ruby +post '/event_handler' do + +end +``` + +#### Define los métodos auxiliares + +Los métodos auxiliares en esta plantilla hacen la mayoria del trabajo pesado. Se definen cuatro métodos auxiliares en esta sección del código. + +##### Gestionar la carga útil del webhok + +El primer método `get_payload_request` captura la carga útil del webhook y la convierte en formato JSON, lo cual hace mucho más fácil el acceder a los datos de la misma. + +##### Verificar la firma del webhook + +El segundo método `verify_webhook_signature` lleva a cabo la verificación de la firma del webhook para garantizar que GitHub generó el evento. Para aprender más acerca del código en el método auxiliar `verify_webhook_signature`, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". Si los webhooks son seguros, este método registrará todas las cárgas útiles en tu terminal. El código de registro es útil para verificar que tu servidor web esté trabajando, pero siempre lo puedes eliminar más adelante. + +##### Autenticarse como una GitHub App + +Para hacer llamadas a la API, estarás utilizando la [Biblioteca Octokit](http://octokit.github.io/octokit.rb/). Para que puedas hacer algo interesante con esta biblioteca necesitarás, o más bien, tu app necesitará autenticarse. GitHub Apps tiene dos métodos de autenticación: + +- Autenticación como una GitHub App utilizando un [Token Web de JSON (JWT)](https://jwt.io/introduction). +- Autenticación como una instalación específica de una GitHub App utilizando un token de acceso de instalación. + +Aprenderás cómo autenticarte como una instalación en la [siguiente sección](#authenticating-as-an-installation). + +El [autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) te permite hacer un par de cosas: + + * Puedes recuperar información administrativa de alto nivel sobre tu GitHub App. + * Puedes solicitar tokens de acceso para una instalación de la app. + +Por ejemplo, te podrías autenticar como una GitHub App para solicitar una lista de las cuentas (de organización y de persona) que han instalado tu app. Pero este método de autenticación no te permite hacer mucho con la API. Para acceder a los datos del repositorio y realizar operaciones en nombre de la instalación, necesitas autenticarte como una instalación. Para hacerlo, primero necesitarás autenticarte como una GitHub App para solicitar un token de acceso a la instalación. + +Antes de que puedas utilizar la biblioteca Octokit.rb para hacer llamados a la API, necesitarás inicializar un [cliente de Octokit](http://octokit.github.io/octokit.rb/Octokit/Client.html) autenticado como una GitHub App. ¡El método auxiliar `authenticate_app` hace exactamente eso! + +``` ruby +# Instantiate an Octokit client authenticated as a GitHub App. +# GitHub App authentication requires that you construct a +# JWT (https://jwt.io/introduction/) signed with the app's private key, +# so GitHub can be sure that it came from the app an not altered by +# a malicious third party. +def authenticate_app + payload = { + # The time that this JWT was issued, _i.e._ now. + iat: Time.now.to_i, + + # JWT expiration time (10 minute maximum) + exp: Time.now.to_i + (10 * 60), + + # Your GitHub App's identifier number + iss: APP_IDENTIFIER + } + + # Cryptographically sign the JWT + jwt = JWT.encode(payload, PRIVATE_KEY, 'RS256') + + # Create the Octokit client, using the JWT as the auth token. + @app_client ||= Octokit::Client.new(bearer_token: jwt) +end +``` + +El código anterior genera un [Token Web de JSON (JWT)](https://jwt.io/introduction) y lo utiliza (junto con la llave privada de tu app) para inicializar el cliente de Octokit. GitHub revisa la autenticación de una solicitud verificando el token con la llave pública almacenada en la app. Para aprender más acerca de cómo funciona este código, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)". + +##### Autenticarse como una instalación + +Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Aún si alguien instala la app en más de un repositorio, esto únicamente cuenta como una instalación, ya que toma lugar en la misma cuenta. El último método auxiliar `authenticate_installation` inicializa un [cliente de Octokit](http://octokit.github.io/octokit.rb/Octokit/Client.html) autenticado como una instalación. Este cliente de Octokit es lo que utilizarás para hacer llamadas autenticadas a la API. + +``` ruby +# Instantiate an Octokit client authenticated as an installation of a +# GitHub App to run API operations. +def authenticate_installation(payload) + installation_id = payload['installation']['id'] + installation_token = @app_client.create_app_installation_access_token(installation_id)[:token] + @installation_client = Octokit::Client.new(bearer_token: installation_token) +end +``` + +El método de Octokit [`create_app_installation_access_token`](http://octokit.github.io/octokit.rb/Octokit/Client/Apps.html#create_app_installation_access_token-instance_method) crea un token de instalación. Este método acepta dos argumentos: + +* Instalación (número entero): la ID de la instalación de una GitHub App +* Opciones (un hash, predeterminadamente es `{}`): un conjunto de opciones personalizables + +En cualquier momento en el que una GitHub App reciba un webhook, este incluirá un objeto de `installation` con una `id`. Utilizando el cliente autenticado como una GitHub App, pasarás la ID del método `create_app_installation_access_token` para generar un token de acceso para cada instalación. Ya que no estás pasando ninguna opción al método, ésta será un hash vacío predeterminadamente. Si te refieres a [los documentos](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation), podrás ver que la respuesta de `create_app_installation_access_token` incluye dos campos: `token` y `expired_at`. El código de la plantilla selecciona al token en la respuesta e inicializa un cliente de instalación. + +Una vez teniendo listo este métido, cada vez que tu app reciba una nueva carga útil de un webhook, este creará un cliente para la instalación que activó dicho evento. Este proceso de autenticación habilita a tu GitHub App para que trabaje para todas las instalaciones en cualquier cuenta. + +¡Ahora estás listo para comenzar a hacer llamadas a la API! + +### Paso 6. Inicia el servidor + +Tu app no _hace_ nada aún, pero en este punto, puedes ponerla a ejecutarse en el servidor. + +Mantén a Smee ejecutándose en la pestaña actual dentro de tu terminal. Abre una nueva pestaña y muévete al directorio en donde [clonaste el código de la plantilla de la app](#prerequisites) con el comando `cd`. El código de Ruby en este repositorio iniciará un servidor web de [Sinatra](http://sinatrarb.com/). Este código tiene algunas cuantas dependencias. Puedes instalarlas si ejecutas: + +```shell +$ gem install bundler +``` + +Seguido de: + +```shell +$ bundle install +``` + +Con las dependencias instaladas, puedes iniciar el servidor: + +```shell +$ ruby template_server.rb +``` + +Deberás ver una respuesta como: + +```shell +> == Sinatra (v2.0.3) has taken the stage on 3000 for development with backup from Puma +> Puma starting in single mode... +> * Version 3.11.2 (ruby 2.4.0-p0), codename: Love Song +> * Min threads: 0, max threads: 16 +> * Environment: development +> * Listening on tcp://localhost:3000 +> Use Ctrl-C to stop +``` + +Si ves un error, asegúrate de haber creado el archivo `.env` en el directorio que contiene a `template_server.rb`. + +Una vez que esté ejecutándose el servidor, puedes probarlo si vas a `http://localhost:3000` en tu buscador. Si la app funciona como se espera, verás una página de error útil: + +Página de error 404 de Sinatra + +¡Esto es bueno! Aunque es una página de error, es una página de error de _Sinatra_, lo cual significa que tu app está conectada con el servidor como lo esperabas. Estás viendo este mensaje porque no le has dado nada más que mostrar a la app. + +### Paso 7. Instala la app en tu cuenta + +Puedes probar que el servidor está escuchando a tu app si activas un evento para que lo reciba. Un evento simple con el que puedes hacer la prueba es instalar la app en tu cuenta de GitHub, la cual deberá enviar el evento [`installation`](/webhooks/event-payloads/#installation). Si la app lo recibe, deberás ver alguna salida en la pestaña de la terminal en donde iniciaste el `template_server.rb`. + +Para instalar la app, visita la [página de configuración de la app](https://github.com/settings/apps), elige tu app, y da clic en **Instalar App** en la barra lateral. Junto a tu nombre de usuario, da clic en **Instalar**. + +Se te solicitará si quieres instalar la app en todos los repositorios o solo en los seleccionados. Si no quieres instalar la app en _todos_ tus repositorios, ¡no pasa nada! Tal vez quieras crear un repositorio de entorno de pruebas para e instalar tu app ahí. + +Permisos de instalación de la aplicación + +Después de que des clic en **Instalar**, revisa la salida en tu terminal. Deberías encontrar algo como esto: + +```shell +> D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation +> D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ---- action created +> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067 +> D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation +> D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ---- action created +> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019 +``` + +¡Estas son buenas noticias! Esto significa que tu app recibió una notificación de que se instaló en tu cuenta de GitHub. Si ves algo como esto, tu app está ejecutándose en el servidor como lo esperabas. 🙌 + +Si no ves la salida, asegúrate de que Smee se esté ejecutando correctamente en otra pestaña de la terminal. Si necesitas reiniciar Smee, nota que también necesitarás _desinstalar_ y _reinstalar_ la app para enviar el evento de `installation` a tu app nuevamente y así ver la salida en la terminal. Si el problema no es con Smee, consulta la sección de "[Solución de problemas](#troubleshooting)" para darte otras ideas al respecto. + +Si te estás preguntando de dónde viene la salida de la terminal que ya mostramos, esto se encuentra escrito en el [código de la plantilla de la app](#prerequisites) dentro de `template_server.rb`. + +### Solución de problemas + +Aquí te presentamos algunos problemas comunes y sus soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejos en el {% data variables.product.prodname_support_forum_with_url %}. + +* **P:** Cuando trato de instalar el cliente de línea de comandos de Smee, me encuentro con el siguiente error: + + ```shell + > npm: command not found + ``` + + **R:** Parece que no instalaste npm. La mejor forma de isntalarlo es descargar el paquete de Node.js en https://nodejs.org y seguir las instrucciones de instalación para tu sistema. Se instalará npm junto con Node.js. + +* **P:** Cuando ejecuto el servidor me aparece el siguiente error: + + ```shell + > server.rb:38:in `initialize': Neither PUB key nor PRIV key: header too long (OpenSSL::PKey::RSAError) + ``` + + **R:** Probablemente no configuraste bien la variable de ambiente de tu llave privada. Tu variable de `GITHUB_PRIVATE_KEY` se debe ver así: + + ``` + PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- + ... + HkVN9... + ... + -----END RSA PRIVATE KEY-----" + ``` + + Revisa otra vez si copiaste la llave pública correcta en tu archivo `.env`. + +* **P:** Cuando ejecuto el servidor, produce un fallo con este error: + + ```shell + > Octokit::Unauthorized ... 401 - Bad credentials` + ``` + + **R:** Tal vez estés autenticado como una GitHub App pero no como una instalación. Asegúrate de seguir todos los pasos de la sección "[Autenticarte como una instalación](#authenticating-as-an-installation)", y utilizar la variable de instancia `@installation_client` (autenticado con un token de acceso de instalación) para las operaciones de tu API, y no así la variable de instancia `@app_client` (autenticado con un JWT). El `@app_client` solopuede recuperar información de alto nivel acerca de tu app y obtener tokens de acceso a la instalación. No puede más que esto en la API. + +* **P:** ¡Mi servidor no está escuchando los eventos! El cliente de Smee está ejecutándose en una ventana de la terminal, y estoy instalando la app en un repositorio con GitHub, pero no veo ninguna salida en la ventana de la terminal en donde estoy ejecutando el servidor. + + **R:** Tal vez no estés ejecutando el cliente de Smee, o tal vez no tengas el dominio correcto de Smee en la configuración de tu GitHub App. Primero revisa para asegurarte de que se esté ejecutando el cliente de Smee en la pestaña de la terminal. Si ese no es el problema, visita tu [página de configuración de la app](https://github.com/settings/apps) y revisa los campos que se muestran en el "[Paso 2. Registra una GitHub App nueva](#step-2-register-a-new-github-app)". Asegúrate que el dominio en esos campos empata con aquél que utilizaste en tu comando de `smee -u ` en el "[Paso 1. Iniciar un canal nuevo de Smee](#step-1-start-a-new-smee-channel)". + +* **P:** Se me está mostrando un error 404 de `Octokit::NotFound` en mi salida de depuración: + ``` + 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: + ``` + + **R:** Asegúrate que las variables en tu archivo `.env` son correctas. Asegúrate de que no has configurado variables idénticas en otros archivos de variable del ambiente como `bash_profile`. Puedes revisar las variables de ambiente que utiliza tu app si agregas una declaración de `puts` en el código de tu app y vuelves a ejecutar el código. Por ejemplo, para garantizar que tienes el conjunto de llaves correcto, podrías agregar `puts PRIVATE_KEY` al código de tu app: + + ``` + PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) + puts PRIVATE_KEY + ``` + +### Conclusión + +Después de seguir esta guía, ¡habrás aprendido los fundamentos básicos para desarrollar GitHub Apps! Para revisar todo, debes: + +* Registrar una GitHub App nueva +* Utilizar Smee para recibir cargas útiles de los webhooks +* Ejecutar un servidor web simple a través de Sinatra +* Autenticarte como una GitHub App +* Autenticarte como una instalación + +### Pasos siguientes + +Ahora tienes una GitHub App ejecutándose en un servidor. Aún no hace nada especial, pero revisa en las otras [Guías de inicio rápido](/apps/quickstart-guides/) las formas en las que puedes personalizar la plantilla de GitHub App. diff --git a/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md b/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md new file mode 100644 index 0000000000000..2a273623a18b0 --- /dev/null +++ b/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md @@ -0,0 +1,29 @@ +--- +title: Suspender la instalación de una GitHub App +intro: '{% data reusables.shortdesc.suspending_a_github_app %}' +redirect_from: + - /apps/managing-github-apps/suspending-a-github-app-installation +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:**{% data reusables.pre-release-program.suspend-installation-beta %} + +{% endnote %} + +### Suspender una GitHub App + +El integrador que mantiene y al que le pertenece la GitHub app, también llamado propietario de la GitHub App, puede suspender o dejar de suspender una instalación de la GitHub App utilizando las terminales de la API de REST con JWT. Para obtener más información, consulta la [API de REST para las GitHub Apps](/rest/reference/apps). + +Las personas que han instalado una GitHub App, también llamadas propietarias de la instalación, solo podrán suspender o dejar de suspendar una GitHub App a través de la configuración de instalación de la app. Los propietarios de la instalación no pueden usar la API para suspender o dejar de suspender su instalación de la app. Antes de que las personas puedan suspender la instalación de una GitHub app, el propietario de la misma debe participar en el lanzamiento del beta. Para obtener más información, consulta la sección "[Suspender la instalación de una GitHub App](/apps/managing-github-apps/suspending-a-github-app-installation/)". + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Selecciona la +La {% data variables.product.prodname_github_app %} que quieres suspender. +![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +{% data reusables.user-settings.github_apps_advanced %} +6. Junto a la configuración de suspensión para la instalación, da clic en **Suspender** o en **Dejar de suspender**. ![Suspender una GitHub App](/assets/images/github-apps/suspend-a-github-app.png) diff --git a/translations/es-ES/content/developers/apps/transferring-ownership-of-a-github-app.md b/translations/es-ES/content/developers/apps/transferring-ownership-of-a-github-app.md new file mode 100644 index 0000000000000..70faddeba7f51 --- /dev/null +++ b/translations/es-ES/content/developers/apps/transferring-ownership-of-a-github-app.md @@ -0,0 +1,21 @@ +--- +title: Transferir la propiedad de una GitHub App +intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}' +redirect_from: + - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app/ + - /apps/managing-github-apps/transferring-ownership-of-a-github-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.github_apps %} +4. Selecciona la GitHub App cuya propiedad quieras transferir. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +{% data reusables.user-settings.github_apps_advanced %} +6. Da clic en **Transferir propiedad**. ![Botón para transferir la propiedad](/assets/images/github-apps/github_apps_transfer_ownership.png) +7. Teclea el nombre de la GitHub App que quieres transferir. ![Campo para ingresar el nombre de la app a transferir](/assets/images/github-apps/github_apps_transfer_app_name.png) +8. Teclea el nombre del usuario u organización al cual quieres transferir la GitHub App. ![Campo para ingresar el usuario u organización al cual se transferirá la app](/assets/images/github-apps/github_apps_transfer_new_owner.png) +9. Da clic en **Transferir esta GitHub App**. ![Botón para confirmar la transferencia de una GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png) diff --git a/translations/es-ES/content/developers/apps/transferring-ownership-of-an-oauth-app.md b/translations/es-ES/content/developers/apps/transferring-ownership-of-an-oauth-app.md new file mode 100644 index 0000000000000..dd32a803b5955 --- /dev/null +++ b/translations/es-ES/content/developers/apps/transferring-ownership-of-an-oauth-app.md @@ -0,0 +1,20 @@ +--- +title: Transferir la propiedad de una App de OAuth +intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}' +redirect_from: + - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app/ + - /apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +4. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) +5. Da clic en **Transferir propiedad**. ![Botón para transferir la propiedad](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png) +6. Teclea el nombre de la {% data variables.product.prodname_oauth_app %} que quieres transferir. ![Campo para ingresar el nombre de la app a transferir](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png) +7. Teclea el nombre del usuario u organización al cual quieres transferir la {% data variables.product.prodname_oauth_app %}. ![Campo para ingresar el usuario u organización al cual se transferirá la app](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png) +8. Da clic en **Transferir esta aplicación**. ![Botón para transferir la aplicación](/assets/images/oauth-apps/oauth_apps_transfer_application.png) diff --git a/translations/es-ES/content/developers/apps/troubleshooting-authorization-request-errors.md b/translations/es-ES/content/developers/apps/troubleshooting-authorization-request-errors.md new file mode 100644 index 0000000000000..8baab859520bd --- /dev/null +++ b/translations/es-ES/content/developers/apps/troubleshooting-authorization-request-errors.md @@ -0,0 +1,44 @@ +--- +title: Solución de problemas para los errores de solicitud de autorización +intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}' +redirect_from: + - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors/ + - /apps/managing-oauth-apps/troubleshooting-authorization-request-errors +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Aplicación suspendida + +Si la App de OAuth que configuraste se suspendió (debido a que reportaron abuso, spam, o mal uso de la API), GitHub te redirigirá a la URL de rellamado registrada utilizando los siguientes parámetros para resumir el error: + + http://your-application.com/callback?error=application_suspended + &error_description=Your+application+has+been+suspended.+Contact+support@github.com. + &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended + &state=xyz + +Para resolver los problemas de suspensión de aplicaciones, por favor contacta a {% data variables.contact.contact_support %}. + +### Redirigir una discordancia de URI + +Si proporcionas una `redirect_uri` que no concuerde con lo que has registrado con tu aplicación, GitHub te redirigirá a la URL de rellamado registrada con los siguientes parámetros que resumirán el error: + + http://your-application.com/callback?error=redirect_uri_mismatch + &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application. + &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch + &state=xyz + +Para corregir este error, puedes ya sea proporcionar una `redirect_uri` que coincida con lo que registraste o dejar este parámetro para utilizar aquél predeterminado que se registró con tu aplicación. + +#### Acceso denegado + +Si el usuario rechaza el acceso a tu aplicación, GitHub te redirigirá a la URL de rellamado registrada con los siguientes parámetros para resumir el error: + + http://your-application.com/callback?error=access_denied + &error_description=The+user+has+denied+your+application+access. + &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied + &state=xyz + +No puedes hacer nada al respecto, ya que los usuarios tiene la libertad de elegir si no quieren utilizar tu aplicación. Lo más común es que los usuarios simplemente cierren la ventana o presionen "atrás" en su buscador, así que es probable que nunca veas este error. diff --git a/translations/es-ES/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/es-ES/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md new file mode 100644 index 0000000000000..b09783704f30c --- /dev/null +++ b/translations/es-ES/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md @@ -0,0 +1,68 @@ +--- +title: Solucionar problemas para los errores de solicitud en los tokens de acceso a Apps de OAuth +intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}' +redirect_from: + - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/ + - /apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Estos ejemplos solo muestran respuestas de JSON. + +{% endnote %} + +### Credenciales de cliente incorrectas + +Si la client\_id y/o el client\_secret que pasas son incorrectos, recibirás este error como respuesta. + +```json +{ + "error": "incorrect_client_credentials", + "error_description": "The client_id and/or client_secret passed are incorrect.", + "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#incorrect-client-credentials" +} +``` + +Para resolver este error, asegúrate de que tienes las credenciales correctas para tu {% data variables.product.prodname_oauth_app %}. Revisa dos veces la `client_id` y el `client_secret` para asegurarte de que sean correctos y de que se pasen correctamente en {% data variables.product.product_name %}. + +### Redirigir una discordancia de URI + +Si proporcionas una `redirect_uri` que no empate con lo que registraste con tu {% data variables.product.prodname_oauth_app %}, recibirás este mensaje de error: + +```json +{ + "error": "redirect_uri_mismatch", + "error_description": "The redirect_uri MUST match the registered callback URL for this application.", + "error_uri": "/apps/managing-oauth-apps/troubleshooting-authorization-request-errors/#redirect-uri-mismatch2" +} +``` + +Para corregir este error, puedes ya sea proporcionar una `redirect_uri` que coincida con lo que registraste o dejar este parámetro para utilizar aquél predeterminado que se registró con tu aplicación. + +### Código de verificación incorrecto + +```json +{ + "add_scopes": [ + "repo" + ], + "note": "admin script" +} +``` + +Si el código de verificación que pasaste es incorrecto, está caduco, o no coincide con lo que recibiste en la primera solicitud de autorización, recibirás este error. + +```json +{ + "error": "bad_verification_code", + "error_description": "The code passed is incorrect or expired.", + "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#bad-verification-code" +} +``` + +Para resolver este error, inicia el [proceso de autorización de OAuth nuevamente](/apps/building-oauth-apps/authorizing-oauth-apps/) y obtén un código nuevo. diff --git a/translations/es-ES/content/developers/apps/using-content-attachments.md b/translations/es-ES/content/developers/apps/using-content-attachments.md new file mode 100644 index 0000000000000..6f4c145ebddb7 --- /dev/null +++ b/translations/es-ES/content/developers/apps/using-content-attachments.md @@ -0,0 +1,178 @@ +--- +title: Utilizar adjuntos de contenido +intro: Los adjuntos de contenido permiten que una GitHub App proporcione más información en GitHub para las URL que vinculan a los dominios registrados. GitHub interpreta la información que proporciona la app bajo la URL en el cuerpo o el comentario de un informe de problemas o de una solicitud de extracción. +redirect_from: + - /apps/using-content-attachments +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pre-release-program.content-attachments-public-beta %} + +### Acerca de los adjuntos de contenido + +Una GitHub App puede registrar dominios que activarán los eventos de `content_reference`. Cuando alguien incluye una URL que vincule a un dominio registrado en el cuerpo o en el comentario de un informe de problemas o de una solicitud de extracción, la app recibe el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference). Puedes utilizar los adjuntos de contenido para proporcionar visualmente más contenido o datos para la URL que se agregó a un informe de problemas o a una solicitud de extracción. La URL debe estar completamente calificada, comenzando ya sea con `http://` o con `https://`. Las URL que sean parte de un enlace de markdown se ignorarán y no activarán el evento de `content_reference`. + +Antes de que puedas utilizar la API de {% data variables.product.prodname_unfurls %}, necesitarás configurar las referencias de contenido para tu GitHub App: +* Concede los permisos de `Read & write` a tu app para "Referencias de contenido". +* Registra hasta 5 dominios válidos y accesibles al público cuando configures el permiso de "Referencias de contenido". No utilices direcciones IP cuando configures dominios con referencias de contenido. Puedes registrar un nombre de dominio (ejemplo.com) o un subdominio (subdominio.ejemplo.com). +* Suscribe a tu app al evento de "Referencia de contenido". + +Una vez que tu app se instale en un repositorio, los comentarios de solicitudes de extracción o de informes de problemas en éste, los cuales contengan URL para tus dominios registrados, generarán un evento de referencia de contenido. La app debe crear un adjunto de contenido en las seis horas siguientes a la publicación de la URL de referencia de contenido. + +Los adjuntos de contenido no actualizarán las URL retroactivamente. Esto solo funciona para aquellas URL que se agerguen a las solicitudes de extracción o informes de problemas después de que configuras la app utilizando los requisitos descritos anteriormente y que después alguien instale la app en su repositorio. + +Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" o "[Editar los permisos de las GitHub Apps](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para encontrar los pasos necesarios para configurar los permisos de las GitHub Apps y las suscripciones a eventos. + +### Implementar el flujo de los adjuntos de contenido + +El flujo de los adjuntos de contenido te muestra la relación entre la URL en el informe de problemas o en la solicitud de extracción, el evento de webhook de `content_reference`, y la terminal de la API de REST que necesitas para llamar o actualizar dicho informe de problemas o solicitud de extracción con información adicional: + +**Paso 1.** Configura tu app utilizando los lineamientos descritos en la sección [Acerca de los adjuntos de contenido](#about-content-attachments). También puedes utilizar el [ejemplo de la App de Probot](#example-using-probot-and-github-app-manifests) para iniciar con los adjuntos de contenido. + +**Paso 2.** Agrega la URL para el dominio que registraste a un informe de problemas o solicitud de extracción. Debes utilizar una URL totalmente calificada que comience con `http://` o con `https://`. + +![URL que se agregó a un informe de problemas](/assets/images/github-apps/github_apps_content_reference.png) + +**Paso 3.** Tu app recibirá el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference) con la acción `created`. + +``` json +{ + "action": "created", + "content_reference": { + "id": 17, + "node_id": "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA5", + "reference": "errors.ai" + }, + "repository": {...}, + "sender": {...}, + "installation": { + "id": 371641, + "node_id": "MDIzOkludGVncmF0aW9uSW5zdGFsbGF0aW9uMzcxNjQx" + } +} +``` + +**Paso 4.** La app utiliza la `id` de `content_reference`, para [Crear un adjunto de contenido](/rest/reference/apps#create-a-content-attachment) utilizando la API de REST. También necesitas la `id` de la `installation` para autenticarte como una [Instalación de una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +{% data reusables.pre-release-program.corsair-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +El parámetro `body` puede contener lenguaje de markdown: + + ```shell + curl -X POST \ + https://api.github.com/content_references/1512/attachments \ + -H 'Accept: application/vnd.github.corsair-preview+json' \ + -H 'Authorization: Bearer $INSTALLATION_TOKEN' \ + -d '{ + "title": "[A-1234] Error found in core/models.py file", + "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" + }' + ``` + +Para obtener más información acerca de crear un token de instalación, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". + +**Paso 5.** Verás como el nuevo adjunto de contenido aparece bajo el enlace en un comentario de una solicitud de extracción o informe de problemas: + +![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/github_apps_content_reference_attachment.png) + +### Utilizar adjuntos de contenido en GraphQL +Proporcionamos la `node_id` en el evento de [Webhook de `content_reference` ](/webhooks/event-payloads/#content_reference) para que puedas referirte a la mutación `createContentAttachment` en la API de GraphQL. + +{% data reusables.pre-release-program.corsair-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +Por ejemplo: + +``` graphql +mutation { + createContentAttachment(input: { + contentReferenceId: "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1", + title: "[A-1234] Error found in core/models.py file", + body:"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" + }) { + contentAttachment { + ... on ContentAttachment { + id + title + body + } + } + } +} +``` +cURL de ejemplo: + +```shell +curl -X "POST" "https://api.github.com/graphql" \ + -H 'Authorization: Bearer $INSTALLATION_TOKEN' \ + -H 'Accept: application/vnd.github.corsair-preview+json' \ + -H 'Content-Type: application/json; charset=utf-8' \ + -d $'{ + "query": "mutation {\\n createContentAttachment(input:{contentReferenceId: \\"MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1\\", title:\\"[A-1234] Error found in core/models.py file\\", body:\\"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n\self.save()\\"}) {\\n contentAttachment {\\n id,\\n title,\\n body\\n }\\n }\\n}" +}' +``` + +Para obtener más información aacerca de `node_id`, consulta la sección "[Utilizar las Node ID Globales](/graphql/guides/using-global-node-ids)". + +### Ejemplo de uso con Probot y Manifiestos de GitHub Apps + +Para configurar rápidamente una GitHub App que pueda utilizar la API de {% data variables.product.prodname_unfurls %}, puedes utilizar el [Probot](https://probot.github.io/). Consulta la sección "[Crear Github Apps a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para aprender cómo el Probot utiliza los Manifiestos de las GitHub Apps. + +Para crear una App de Probot, sigue estos pasos: + +1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app). +2. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. Suscríbete al evento `content_reference` y habilita los permisos de escritura de `content_references`: + + ``` yml + + default_events: + - content_reference + # The set of permissions needed by the GitHub App. The format of the object uses + # the permission name for the key (for example, issues) and the access type for + # the value (for example, write). + # Valid values are `read`, `write`, and `none` + default_permissions: + content_references: write + + content_references: + - type: domain + value: errors.ai + - type: domain + value: example.org + ``` + +3. Agrega este código al archivo `index.js` para gestionar los eventos de `content_reference` y llamar a la API de REST: + + ``` javascript + module.exports = app => { + // Your code here + app.log('Yay, the app was loaded!') + app.on('content_reference.created', async context => { + console.log('Content reference created!', context.payload) + // Call the "Create a content reference" REST endpoint + await context.github.request({ + method: 'POST', + headers: { accept: 'application/vnd.github.corsair-preview+json' }, + url: `/content_references/${context.payload.content_reference.id}/attachments`, + // Parameters + title: '[A-1234] Error found in core/models.py file', + body: 'You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\nself.save()' + }) + }) + } + ``` + +4. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally). Navega hasta `http://localhost:3000`, y da clic en el botón **Registrar GitHub App**: + + ![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png) + +5. Instala la app en un repositorio de prueba. +6. Crea un informe de problemas en tu repositorio de prueba. +7. Agrega un comentario en el informe de problemas que abriste, el cual incluya la URL que configuraste en el archivo `app.yml`. +8. Revisa el comentario del informe de problemas y verás una actualización que se ve así: + + ![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/github_apps_content_reference_attachment.png) diff --git a/translations/es-ES/content/developers/apps/using-the-github-api-in-your-app.md b/translations/es-ES/content/developers/apps/using-the-github-api-in-your-app.md new file mode 100644 index 0000000000000..b4222b87a3bc0 --- /dev/null +++ b/translations/es-ES/content/developers/apps/using-the-github-api-in-your-app.md @@ -0,0 +1,235 @@ +--- +title: Utilizar la API de GitHub en tu app +intro: Aprende cómo configurar tu app para que escuche los eventos y utilice la biblioteca de Octokit para hacer operaciones de la API de REST. +redirect_from: + - /apps/building-your-first-github-app/ + - /apps/quickstart-guides/using-the-github-api-in-your-app +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Introducción + +Esta guía te ayudará a crear una GitHub App y a ejecutarla en un servidor. La app que crees agregará una etiqueta a todos los informes de problemas nuevos que estén abiertos en el repositorio en donde ésta se instale. + +Este proyecto te mostrará cómo hacer lo siguiente: + +* Programar tu app para escuchar eventos +* Utilizar la biblioteca de Octokit para hacer operaciones de la API de REST + +{% data reusables.apps.app-ruby-guides %} + +Una vez que hayas seguido estos pasos, estarás listo para desarrollar otros tipos de integraciones utilizando la suite completa de las API de GItHub. {% if currentVersion == "free-pro-team@latest" %}Puedes revisar los ejemplos exitosos de las apps en [GitHub Marketplace](https://github.com/marketplace) y en [Funciona con GitHub](https://github.com/works-with).{% endif %} + +### Prerrequisitos + +Puede que te sea útil tener un entendimiento básico de lo siguiente: + +* [GitHub Apps](/apps/about-apps) +* [Webhooks](/webhooks) +* [El lenguaje de programación Ruby](https://www.ruby-lang.org/en/) +* [Las API de REST](/rest) +* [Sinatra](http://sinatrarb.com/) + +Pero puedes seguir esta guía sin importar tu nivel de experiencia. ¡Colocaremos enlaces para la información que requieras en cada fase! + +Antes de que comiences, necesitas hacer lo siguiente: + +1. Clona el repositorio [Utilizar la API de GitHub en tu app](https://github.com/github-developer/using-the-github-api-in-your-app). + ```shell + $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git + ``` + + Dentro del directorio, encontrarás un archivo de nombre `template_server.rb` con el código de plantilla que utilizarás en este inicio rápido, y un archivo llamado `server.rb` con el código del proyecto completo. + +1. Sigue los pasos en la guía de inicio rápido "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)" para configurar y ejecutar el servidor `template_server.rb` de la app. Si ya habías completado alguna guía de inicio rápido para las GitHub Apps diferente a aquella de [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/), deberás registrar una GitHub App _nueva_ e iniciar un canal de Smee nuevo para utilizarlo con esta guía. + + Esta guía de inicio rápido incluye el mismo código de `template_server.rb` que aquella llamada [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/). **Nota:** Mientras sigues la guía de inicio rápido de [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/) asegúrate de utilizar los archivos de proyecto que se incluyen en el repositorio [Utilizar la API de GitHub para tu app](https://github.com/github-developer/using-the-github-api-in-your-app). + + Consulta la sección [Solución de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) si te encuentras con algún problema al configurar tu GitHub App de plantilla. + +### Crear la app + +Ahora que estás familiarizado con el código de `template_server.rb`, vas a crear el código que agregará la etiqueta `needs-response` automáticamente a todos los informes de problemas que estén abiertos en el repositorio en donde se instale la app. + +El archivo `template_server.rb` contiene el código de la plantilla de la app que no se ha personalizado aún. En este archivo, verás código de marcador de posición para gestionar eventos de webhook y algún otro tipo de código para inicializar el cliente de Octokit.rb. + +{% note %} + +**Nota:** El `template_server.rb` contiene muchos comentarios de código que complementan esta guía y explican detalles técnicos adicionales. Es posible que le resulte útil leer los comentarios de ese archivo ahora, antes de continuar con esta sección, para obtener resumen de cómo funciona el código. + +El código personalizado final que crees al terminar esta guía se proporciona en el archivo [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Pero, ¡intenta esperar hasta que termines para darle un vistazo! + +{% endnote %} + +Estos son los pasos que tendrás que completar para crear tu primer GitHub App: + +1. [Actualizar los permisos de la app](#step-1-update-app-permissions) +2. [Agregar la gestión de eventos](#step-2-add-event-handling) +3. [Crear una etiqueta nueva](#step-3-create-a-new-label) +4. [Agregar la gestión de etiquetas](#step-4-add-label-handling) + +### Paso 1. Actualizar los permisos de la app + +Cuando [registraste tu app por primera vez](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), aceptaste los permisos predeterminados, lo que significa que tu app no tiene acceso a la mayoría de los recursos. Para este ejemplo, tu app necesitará el permiso para leer los informes de problemas y escribir etiquetas. + +Para actualizar los permisos de tu app: + +1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. +1. En la sección de "Permisos", encuentra "Informes de problemas"; y selecciona **Lectura & Escritura** en el menú desplegable de "Acceso" que está a un costado. La descripción dice que esta opción otorga acceso tanto a informes de problemas como a etiquetas, que es exactamente lo que buscas. +1. En la sección "Suscribirse a los eventos", selecciona **Informes de problemas** para suscribirte a este evento. +{% data reusables.apps.accept_new_permissions_steps %} + +¡Genial! Tu app tiene permiso para realizar las tareas que quieres que haga. Ahora puedes agregar el código para que funcione. + +### Paso 2. Agregar la gestión de eventos + +Lo primero que tiene que hacer tu app es escuchar si se han abierto informes de problemas nuevos. Ahora que te has suscrito alevento de **Informes de problemas**, comenzarás a recibir el webhook [`issues`](/webhooks/event-payloads/#issues), el cual se activa cuando ocurren algunas acciones relacionadas con los informes de problemas. Puedes filtrar este tipo de evento para la acción específica que quieres en tu código. + +GitHub envía las cargas útiles de los webhooks como solicitudes de tipo `POST`. Ya que reenviaste las cargas útiles del webhook de Smee a `http://localhost/event_handler:3000`, tu servidor recibirá las cargas útiles de la solicitud de `POST` en la ruta `post '/event_handler'`. + +Ya se incluye una ruta de `post '/event_handler'` vacía en el archivo `template_server.rb`, el cual descargaste en la sección de [prerrequisitos](#prerequisites). La ruta vacía se ve así: + +``` ruby + post '/event_handler' do + + # # # # # # # # # # # # + # ADD YOUR CODE HERE # + # # # # # # # # # # # # + + 200 # success status + end +``` + +Utiliza esta ruta para gestionar el evento `issues` agregando el siguiente código: + +``` ruby +case request.env['HTTP_X_GITHUB_EVENT'] +when 'issues' + if @payload['action'] === 'opened' + handle_issue_opened_event(@payload) + end +end +``` + +Cada vento que envíe GitHub incluye un encabezado de solicitud que se llama `HTTP_X_GITHUB_EVENT`, el cual indica el tipo de evento en la solicitud de `POST`. Ahora mismo solo te interesan los tipos de evento `issues`. Cada evento tiene un campo adicional de `action` que indica el tipo de acción que activó los eventos. Para los `issues`, el campo de `action` puede estar como `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, o `reopened`. + +Para probar tu gestor de eventos, intenta agregar un método auxiliar temporal. Lo actualizarás más adelante cuando [Agregues la gestión de etiquetas](#step-4-add-label-handling). Por ahora, agrega el siguiente código dentro de la sección `helpers do` del mismo. Puedes poner el método nuevo arriba o abajo de cualquiera de los métodos auxiliares. El orden no importa. + +``` ruby +def handle_issue_opened_event(payload) + logger.debug 'An issue was opened!' +end +``` + +Este método recibe una carga útil de evento formateada con JSON a manera de argumento. Esto significa que puedes analizar la carga útil en el método y profundizar hacia cualquier tipo de datos específico que necesites. Podría parecerte útil el inspeccionar totalmente la carga útil en algún memoento: intenta cambiar el mensaje `logger.debug 'An issue was opened!` a `logger.debug payload`. La estructura de la carga útil que ves deberá coincidir con lo que [se muestra en los documentos del evento de webhook `issues`](/webhooks/event-payloads/#issues). + +¡Genial! Es momento de probar los cambios. + +{% data reusables.apps.sinatra_restart_instructions %} + +En tu buscador, visita el repositorio en donde instalaste tu app. Abre un informe de problemas nuevo en este repositorio. El informe de problemas puede decir lo que gustes. Esto es solo para hacer la prueba. + +Cuando regreses a ver tu terminal, deberás ver un mensaje en la salida, el cual diga, `An issue was opened!` ¡Felicidades! Acabas de agregar un gestor de eventos a tu app. 💪 + +### Paso 3. Crear una etiqueta nueva + +Bien, tu app puede decirte qué informes de problemas están abiertos. Ahora querrás que agregue la etiqueta `needs-response` a cualquier informe de problemas nuevo que esté abierto en el repositorio en donde se instale. + +Antes de que puedas _agregar_ la etiqueta a alguna parte, necesitarás _crear_ la etiqueta personalizada en tu repositorio. Solo necesitas hacer esto una vez. Para fines de esta guía, crea la etiqueta manualmente en GitHub. En tu repositorio, da clic en **Informes de problemas**, luego en **Etiquetas**, y después da clic en **Etiqueta nueva**. Nombra la nueva etiqueta como `needs-response`. + +{% tip %} + +**Tip**: ¿No sería genial si tu app pudiera crear la etiqueta mediante programación? Pues ¡[Puede hacerlo](/rest/reference/issues#create-a-label)! Intenta agregar tú mismo el código para que lo haga después de que completes los pasos en esta guía. + +{% endtip %} + +Ahora que existe la etiqueta, puedes programar tu app para que utilice la API de REST para [agregar la etiqueta a cualquier informe de problemas recién abierto](/rest/reference/issues#add-labels-to-an-issue). + +### Paso 4. Agregar la gestión de etiquetas + +Felicidades—llegste al último paso: agregar la gestión de etiquetas a tu app. Para esta tarea, querrás utilizar la [Biblioteca Ocktokit.rb de Ruby](http://octokit.github.io/octokit.rb/). + +En los documentos de Octokit, encuentra una lista de los [métodos de las etiquetas](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). El método que necesitarás usar es [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method). + +Una vez de regreso en el `template_server.rb`, encuentra el método que definiste previamente: + +``` ruby +def handle_issue_opened_event(payload) + logger.debug 'An issue was opened!' +end +``` + +Los documentos de [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) te muestran que necesitarás pasar tres argumentos en este método: + +* Repo (secuencia en formato `"owner/name"`) +* Número de informe de problemas (número entero) +* Etiquetas (matriz) + +Puedes analizar la carga útil para obtener tanto el repo y el número de informe de problemas. Ya que el nombre de la etiqueta siempre será el mismo (`needs-response`), podrás pasarlo como una secuencia fijada en la matriz de etiquetas. Al juntar estas piezas, tu método actualizado se podría ver más o menos así: + +``` ruby +# When an issue is opened, add a label +def handle_issue_opened_event(payload) + repo = payload['repository']['full_name'] + issue_number = payload['issue']['number'] + @installation_client.add_labels_to_an_issue(repo, issue_number, ['needs-response']) +end +``` + +¡Intenta abrir un informe de problemas nuevo en tu repositorio de prueba y ver lo que pasa! Si no pasa nada de inmediato, intenta actualizarlo. + +No verás mucho en la terminal, _pero_ deberías ver que el usuario bot agregó la etiqueta al informe de problemas. + +{% note %} + +**Nota:** Cuando las GitHub Apps toman acciones a través de la API, tales como agregar etiquetas, GitHub muestra estas acciones como si las cuentas _bot_ las realizaran. Para obtener más información, consulta la sección "[Cuentas de máquina vs cuentas de bot](/apps/differences-between-apps/#machine-vs-bot-accounts)". + +{% endnote %} + +Si es así, ¡felicidades! ¡Has creado una app funcional exitosamente! 🎉 + +Puedes ver el código final en el `server.rb` dentro del [repositorio de plantilla de app](https://github.com/github-developer/using-the-github-api-in-your-app). + +Consulta la sección "[Pasos siguientes](#next-steps)" para obtener ideas de qué puedes hacer después. + +### Solución de problemas + +Aquí te presentamos algunos problemas comunes y sus soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejos en el {% data variables.product.prodname_support_forum_with_url %}. + +* **P:** ¡Mi servidor no está escuchando los eventos! El cliente de Smee está ejecutándose en una ventana de la terminal, y estoy enviando eventos en GitHub.com mediante la apertura de informes de problemas nuevos, pero no veo ninguna salida en la ventana de la terminal en donde estoy ejecutando el servidor. + + **R:** Tal vez no tengas el dominio correcto de Smee en la configuración de tu app. Visita tu [página de configuración de la app](https://github.com/settings/apps) y vuelve a revisar los campos que se muestran en "[Registrar una app nueva con GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)". Asegúrate que el dominio en estos campos empate con el dominio que utilizaste en tu comando de `smee -u ` en "[Iniciar un canal de Smee nuevo](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)". + +* **P:** ¡Mi app no funciona! Abrí un nuevo informe de problemas, pero aún después de actualizar, no se le ha agregado ninguna etiqueta. + + **R:** Asegúrate de que hayas hecho todo lo siguiente: + + * [Instalaste la app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) en el repositorio en donde estás abriendo el informe de problemas. + * Tu [cliente de Smee se está ejecutando](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) en una ventana de la terminal. + * Tu [servidor web se está ejecutando](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) sin errores en otra ventana de la terminal. + * Tu app tiene permisos de [lectura & escritura en los informes de problemas y está suscrita a los eventos de los mismos](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel). + * [Revisaste tu cuenta de correo electrónico](#step-1-update-app-permissions) después de actualizar los permisos y aceptaste los permisos nuevos. + +### Conclusión + +Después de seguir esta guía, ¡habrás aprendido los fundamentos básicos para desarrollar GitHub Apps! Para revisar todo, debes: + +* Programaste tu app para escuchar eventos +* Utilizaste la biblioteca de Octokit para hacer operaciones de la API de REST + +### Pasos siguientes + +Aquí tienes algunas ideas para lo que puedes hacer después: + +* ¡[Vuelve a escribir tu app utilizando GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)! +* ¡Vuelve a escribir tu app en Node.js utilizando al [Probot](https://github.com/probot/probot)! +* Haz que la app revise si la etiqueta `needs-response` ya existe en el informe de problemas, y si no, agrégala. +* Cuando el bot agregue la etiqueta exitosamente, muestra un mensaje en la terminal. (Pista: compara la ID de la etiqueta `needs-response` con la ID de la etiqueta en la carga útil como una condición para tu mensaje, para que así, el mensaje solo muestre cuando la etiqueta relevante se agregue y no lo haga con otra etiqueta). +* Agrega una página de llegada para tu app y conéctale una [Ruta de Sinatra](https://github.com/sinatra/sinatra#routes). +* Migra tu código a un servidor hospedado (como Heroku). No olvides actualizar la configuración de tu app con el dominio nuevo. +* Comparte tu proyecto u obtén consejos en el {% data variables.product.prodname_support_forum_with_url %}{% if currentVersion == "free-pro-team@latest" %} +* ¿Has creado una nueva y reluciente app que crees que pueda ser útil para otros? ¡[Agrégala a GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %} diff --git a/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md new file mode 100644 index 0000000000000..6e2f81f50ae54 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md @@ -0,0 +1,54 @@ +--- +title: Acerca de Mercado GitHub +intro: 'Aprende más sobre {% data variables.product.prodname_marketplace %}, en donde puedes compartir tus apps y acciones públicamente con todos los usuarios de {% data variables.product.product_name %}.' +redirect_from: + - /apps/marketplace/getting-started/ + - /marketplace/getting-started +versions: + free-pro-team: '*' +--- + +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) te conecta a los desarrolladores que quieren extender y mejorar sus flujos de trabajo de {% data variables.product.prodname_dotcom %}. Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} ofrece dos tipos de herramientas para los desarrolladores: {% data variables.product.prodname_actions %} y Apps, y cada herramienta requiere pasos diferentes para agregarla a {% data variables.product.prodname_marketplace %}. + +### GitHub Actions + +{% data reusables.actions.actions-not-verified %} + +Para aprender sobre cómo publicar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_marketplace %}, consulta la sección "[Publicar acciones en GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)". + +### Aplicaciones + +Cualquiera puede compartir sus apps con otros usuarios en {% data variables.product.prodname_marketplace %}, pero solo las listas que verifique {% data variables.product.company_short %} podrán incluir planes pagados. Para obtener más información, consulta la sección "[Acerca de los creadores verificados](/developers/github-marketplace/about-verified-creators)". + +Si te interesa crear una app para {% data variables.product.prodname_marketplace %} pero eres nuevo en las {% data variables.product.prodname_github_apps %} o en las {% data variables.product.prodname_oauth_app %}s, consulta la sección "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" o "[Crear {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)". + +{% data reusables.marketplace.github_apps_preferred %}, aunque puedes listar tanto las Apps de OAuth como las {% data variables.product.prodname_github_app %} en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta las secciones "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" y "[Migrarse de las {% data variables.product.prodname_oauth_app %}s a las {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)". + +Si tienes preguntas acerca de {% data variables.product.prodname_marketplace %}, por favor contacta directamente a {% data variables.contact.contact_support %}. + +### Publicar una app en {% data variables.product.prodname_marketplace %} + +Cuando termines de crear tu app, puedes compartirla con otros usuarios si la publicas en {% data variables.product.prodname_marketplace %}. En resúmen, el proceso es: + +1. Revisa tu app cuidadosamente para garantizar que se comporte en otros repositorios como se espera y que cumpla con los lineamientos de mejores prácticas. Para obtener más información, consulta las secciones "[Mejores prácticas de seguridad para las apps](/developers/github-marketplace/security-best-practices-for-apps)" y "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)". + +1. Agrega eventos de webhook a la app para rastrear las solicitudes de facturación de los usuarios. Para obtener más información acerca de la API de {% data variables.product.prodname_marketplace %}, los eventos de webhook y las solicitudes de facturación, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +1. Crea un borrador de lista de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Hacer un borrador de lista para tu app](/developers/github-marketplace/drafting-a-listing-for-your-app)". + +1. Agrega un plan de precios. Para obtener más información, consulta la sección "[Configurar planes de precios para tu listado](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". + +1. Verifica si tu app cumple con los requisitos para los listados en {% data variables.product.prodname_marketplace %} como una app gratuita o pagada. Para obtener más información, consulta la sección "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". + +1. Lee y acepta las condiciones del "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". + +1. Emite tu lista para publicarla en {% data variables.product.prodname_marketplace %} y solicita su verificación si quieres vender la app. Para obtener más información, consulta la sección "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication)". + +Un experto en incorporaciones te contactará para hacerte cualquier pregunta o para indicarte los pasos siguietnes. Por ejemplo, si agregaste un plan de pago, necesitarás completar el proceso de verificación y completar una incorporación financiera. La app se publicará en {% data variables.product.prodname_marketplace %} tan pronto como se apruebe tu lista. + +### Ver el desempeño de tu app + +Puedes acceder a las métricas y transacciones de tu lista. Para obtener más información, consulta: + +- "[Visualizar las métricas de tu lista](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Visualizar las transacciones de tu lista](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/es-ES/content/developers/github-marketplace/about-verified-creators.md b/translations/es-ES/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000000..0029c4d473238 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: Acerca de los creadores verificados +intro: 'Cada organización que quiera vender apps en {% data variables.product.prodname_marketplace %} debe seguir un proceso de verificación. Se verifica su identidad y se revisa su proceso de facturación.' +versions: + free-pro-team: '*' +--- + +### Acerca de los creadores verificados + +Un creador verificado es una organización que ya ha verificado {% data variables.product.company_short %}. Cualquiera puede compartir sus apps con otros usuarios en {% data variables.product.prodname_marketplace %}, pero solo las organizaciones que haya verificado {% data variables.product.company_short %} pueden venderlas. Para obtener más información sobre las organizaciones, consulta la sección "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)". + +El proceso de verificación existe para proteger a los usuarios. Por ejemplo, verifica la identidad del vendedor, verifica que su organización de {% data variables.product.product_name %} se encuentre configurada de forma segura y que se le pueda contactar para recibir soporte. + +Después de pasar las revisiones de verificación cualquier app que la organización liste en {% data variables.product.prodname_marketplace %} se mostrará con una insignia de creador verificado {% octicon "verified" aria-label="Verified creator badge" %}. Ahora, la organización podrá agregar planes de pago a cualquiera de sus apps. Cada app con un plan de pago también pasará por un proceso de incorporación financiera para verificar que se encuentre configurada para gestionar la facturación de forma adecuada. + +![insignias de creador verificado](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +Adicionalmente a la insignia de creador verificado, también podrás ver insignias para las apps que estén verificadas, y para las que no lo estén. Estas apps se publicaron utilizando el método anterior para verificar las apps individuales. + +![Insignias verde para verificado y gris para no verificado](/assets/images/marketplace/marketplace_verified_badges.png) + +Para obtener información sobre cómo encontrar apps que puedas utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". + +### Acerca del proceso de verificación + +La primera vez que solicitas una verificación para una lista de alguna de tus apps, ingresarás al proceso de verificación. Un experto en integración te guiará a lo largo del proceso. Esto incluye la verificación de: + +- La información del perfil - Se llena la información básica del perfil de forma precisa y adecuada. +- La seguridad - La organización habilitó la autenticación bifactorial. +- El dominio verificado - La organización verificó el dominio de la URL del sitio. +- El evento de webhook de compra - La app gestiona correctamente el evento. + +Cuando tu organización se encuentre verificada, todas tus apps se mostrarán con una insignia de creador verificado. Ahora podrás ofrecer planes de pago para cualquiera de tus apps. + +Para obtener más información sobre los requisitos para listar una app en {% data variables.product.prodname_marketplace %}, consulta los "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección: "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% note %} + +**Nota:** Este proceso de verificación para las apps reemplaza el proceso anterior en donde se verificaba a las apps individuales. El proceso actual es similar al proceso de verificación de las acciones. Si tienes apps que se verificaron con el proceso anterior, estas no se verán afectadas por estos cambios. El equipo de {% data variables.product.prodname_marketplace %} te contactará con los detalles de cómo migrarte a una verificación basada en la organización. + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/billing-customers.md b/translations/es-ES/content/developers/github-marketplace/billing-customers.md new file mode 100644 index 0000000000000..e681d7099e386 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/billing-customers.md @@ -0,0 +1,48 @@ +--- +title: Facturar a los clientes +intro: 'Las apps en {% data variables.product.prodname_marketplace %} deben apegarse a los lineamientos de facturación de GitHub y apoyar a los servicios recomendados. El seguir nuestros lineamientos ayuda a los clientes a navegar en el proceso de facturación sin ninguna sorpresa.' +redirect_from: + - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace/ + - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace/ + - /marketplace/selling-your-app/billing-customers-in-github-marketplace +versions: + free-pro-team: '*' +--- + + + +### Entender el ciclo de facturación + +Los clientes pueden escoger un ciclo mensual o anual cuando compran tu app. Todos los cambios que los clientes hagan a los ciclos de facturación y a la selección de plan activaran un evento de `marketplace_purchase`. Puedes referirte a la carga útil del webhook de `marketplace_purchase` para ver qué ciclo de facturación selecciona un usuario y cuándo comienza la siguiente fecha de facturación (`effective_date`). Para obtener más información sobre las cargas útiles de los webhooks, consulta la sección "[Eventos de webhook para la API de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)". + +### Proporcionar servicios de facturación en la IU de tu app + +Los clientes deberán ser capaces de realizar las siguientes acciones desde el sitio web de tu app: +- Los clientes podrán modificar o cancelar sus planes de {% data variables.product.prodname_marketplace %} para sus cuentas de organización y personales por separado. +{% data reusables.marketplace.marketplace-billing-ui-requirements %} + +### Servicios de facturación para mejoras, decrementos y cancelaciones + +Sigue estos lineamientos para las mejoras, decrementos y cancelaciones para mantener un proceso de facturación limpio y consistente. Para obtener instrucciones más detalladas sobre los eventos de compra de {% data variables.product.prodname_marketplace %}, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Puedes utilizar la llave de `effective_date` del webhook de `marketplace_purchase` para determinar cuando ocurrirá un cambio de plan y sincronizar la [Lista de cuentas para un plan](/rest/reference/apps#list-accounts-for-a-plan) de vez en cuando. + +#### Actualizaciones + +Cuando un cliente mejora su plan de precios o cambia su ciclo de facturación de mensual a anual, deberás hacerles el cambio efectivo inmediatamente. Tienes que aplicar un descuento prorrateado para el plan nuevo y cambiar el ciclo de facturación. + +{% data reusables.marketplace.marketplace-failed-purchase-event %} + +Para obtener más información sobre cómo crear flujos de trabajo para mejoras y retrocesos en tu app, consulta la sección "[Administrar los cambios de planes](/developers/github-marketplace/handling-plan-changes)". + +#### Decrementos y cancelaciones + +Los decrementos ocurren cuando un cliente se cambia de un plan pagado a uno gratuito, selecciona un plan con un costo menor al actual, o cambia su ciclo de facturación de anual a mensual. Cuando suceden los decrementos o cancelaciones, no necesitas proporcionar un reembolso. En vez de esto, el plan actual se mantendrá activo hasta el último día del ciclo de facturación actual. El evento `marketplace_purchase` se enviará cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación del cliente. + +Cuando un cliente cancela un plan, debes: +- Degradarlos automáticamente al plan gratuito, si es que existe. + + {% data reusables.marketplace.cancellation-clarification %} +- Habilitarlos para mejorar el plan a través de GitHub si es que quisieran continuar con él más adelante. + +Para obtener más información sobre cómo crear flujos de trabajo de cancelaciones en tu app, consulta la sección "[Administrar cancelaciones de planes](/developers/github-marketplace/handling-plan-cancellations)". diff --git a/translations/es-ES/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/es-ES/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md new file mode 100644 index 0000000000000..45e89864efd4b --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md @@ -0,0 +1,42 @@ +--- +title: Configurar un webhook para que te notifique sobre los cambios de plan +intro: 'Después de [crear un listado de {% data variables.product.prodname_marketplace %} en borrador] (/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), puedes configurar un webhook que te notifique cuando sucedan cambios en los planes de la cuenta de los clientes. Después de que configures el webhook, puedes [gestionar los tipos de evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) en tu app.' +redirect_from: + - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing/ + - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing/ + - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing/ + - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/ + - /marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook +versions: + free-pro-team: '*' +--- + + + +El webhook de evento de {% data variables.product.prodname_marketplace %} solo puede configurarse desde la página de listado de {% data variables.product.prodname_marketplace %} de tu aplicación. Puedes configurar el resto de los eventos desde la [página de configuración del desarrollador de la aplicación](https://github.com/settings/developers). Si no has creado un listado de {% data variables.product.prodname_marketplace %}, lee la sección "[Crear un borrador de listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender cómo hacerlo. + +### Crear un webhook + +Para crear un webhook para tu listado de {% data variables.product.prodname_marketplace %}, da clic en **Webhooks** en la barra lateral de tu [página de listado de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Verás las siguientes opciones que se necesitan para configurar tu webhook: + +#### URL de la carga útil + +{% data reusables.webhooks.payload_url %} + +#### Tipo de contenido + +{% data reusables.webhooks.content_type %} GitHub te recomienda utilizar el tipo de contenido `application/json`. + +#### Secreto + +{% data reusables.webhooks.secret %} + +#### Activo + +Predeterminadamente, las entregas de webhook están "Activas". También puedes elegir inhabilitar la entrega de cargas útiles de webhooks durante el desarrollo si deseleccionas "Activo". Si inhabilitaste las entregas de los webhooks, necesitarás seleccionar "Activo" antes de que emitas tu app para su revisión. + +### Visualizar las entregas de los webhooks + +Una vez que hayas configurado tu webhook de {% data variables.product.prodname_marketplace %}, podrás inspecionar las cargas útiles de las solicitudes de tipo `POST` desde la página del **Webhooks** del [listado de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage) de tu aplicación. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub. + +![Inspeccionar las entregas de webhooks de {% data variables.product.prodname_marketplace %} recientes](/assets/images/marketplace/marketplace_webhook_deliveries.png) diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md new file mode 100644 index 0000000000000..dd169c4654839 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md @@ -0,0 +1,8 @@ +--- +title: Crear apps para GitHub Marketplace +intro: 'Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/es-ES/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000000..98fbb186b7098 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Mejores prácticas para la experiencia de los clientes con las apps +intro: 'Lineamientos para crear una app que sea fácil de utilizar y entender.' +shortTitle: Mejores prácticas para la experiencia de los clientes +versions: + free-pro-team: '*' +--- + +El seguir estas mejores prácticas te ayudará a proporcionar una buena experiencia del cliente. + +### Comunicación con el cliente + +- Los materiales de marketing para la app deberán representar adecuadamente le comportamiento de la misma. +- Las apps deberán incluir enlaces a los documentos de cara al cliente que describan cómo configurarla y utilizarla. +- Los clientes deberán poder ver qué tipo de plan tienen en la sección de facturación, perfil, o configuración de cuenta de la app. +- Los clientes deberán poder instalar y utilizar tu app tanto en una cuenta personal como en una cuenta de organización. Deberán poder ver y administrar la app en estas cuentas por separado. + +### Administración de planes + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md new file mode 100644 index 0000000000000..72455c12c587f --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -0,0 +1,67 @@ +--- +title: Hacer un borrador de un listado para tu app +intro: 'Cuando creas un listado de {% data variables.product.prodname_marketplace %}, GitHub lo guarda en modo borrador hasta que emitas la app para su aprobación. Tu listado muestra a los clientes cómo pueden utilizar tu app.' +redirect_from: + - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ + - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ + - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace/ + - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace/ + - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace/ + - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace/ + - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing/ + - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing/ + - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/ + - /marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing +versions: + free-pro-team: '*' +--- + + + +### Crear un borrador nuevo de un listado de {% data variables.product.prodname_marketplace %} + +Solo puedes crear borradores de listados para las apps que sean públicas. Antes de crear tu borrador de listado puedes leer los siguientes lineamientos para escribir y configurar los ajustes en tu listado de {% data variables.product.prodname_marketplace %}: + +* [Escribir descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) +* [Configurar un plan de precios para el listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) +* [Configurar el Webhook de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) + +Para crear un listado de {% data variables.product.prodname_marketplace %}: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +3. En la barra lateral izquierda, da clic ya sea en **Apps de OAuth** o **GitHub Apps** dependiendo del tipo de app que estés agregando a {% data variables.product.prodname_marketplace %}. + + {% note %} + + **Nota**: También puedes agregar un listado si navegas a https://github.com/marketplace/new, ves tus apps disponibles, y das clic en **Crear un borrador de un lsitado**. + + {% endnote %} + + ![Selección del tipo de app](/assets/images/settings/apps_choose_app.png) + +4. Selecciona la app que te gustaría agregar a + +{% data variables.product.prodname_marketplace %}. +![Selección de aplicaciones para el listado de {% data variables.product.prodname_marketplace %}](/assets/images/github-apps/github_apps_select-app.png) +{% data reusables.user-settings.edit_marketplace_listing %} +5. Una vez que hayas creado un borrador nuevo de un listado, verás un resumen de las secciones que necesitas visitar antes de que tu listado de {% data variables.product.prodname_marketplace %} esté completo. ![Listado de GitHub Marketplace](/assets/images/marketplace/marketplace_listing_overview.png) + + +{% note %} + +**Nota:** En la sección de "información de contacto" de tu listado, te recomendamos utilizar direcciones de correo electrónico individuales en vez de direcciones grupales como support@domain.com. GitHub utilizará estas direcciones de correo electrónico para contactarte con respecto a las actualizaciones a {% data variables.product.prodname_marketplace %} que pudieran afectar tu listado, a los lanzamientos de nuevas características, a las oportunidades de marketing, a los pagos, y a la información sobre conferencias y patrocinios. + +{% endnote %} + +### Editar tu listado + +Ya que hayas creado un borrador de listado de {% data variables.product.prodname_marketplace %}, puedes regresar a modificar la información de éste en cualquier momento. Si tu app ya se aprobó y está en {% data variables.product.prodname_marketplace %}, puedes editar la información e imágenes en tu listado, pero no podrás cambiar los planes de precios que ya estén publicados. Consulta la sección "[Configurar el plan de pagos de un listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". + +### Emitir tu app + +Ya que hayas completado tu listado de {% data variables.product.prodname_marketplace %}, puedes emitirlo para su revisión a través de la página **Resumen**. Necesitas leer y aceptar el "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)", y luego puedes dar clic en **Emitir para revisión**. Después de emitir tu app para su revisión te contactará un experto en integraciones con cualquier tipo de información adicional que se requiera para el proceso de integración. Puedes aprender más acerca del proceso de integración y revisión de seguridad en la sección "[Comenzar con {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". + +### Eliminar un listado de {% data variables.product.prodname_marketplace %} + +Si ya no quieres listar tu app en {% data variables.product.prodname_marketplace %}, contacta a {% data variables.contact.contact_support %} para eliminar tu lista. diff --git a/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md new file mode 100644 index 0000000000000..20bf68d1ee3ba --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -0,0 +1,81 @@ +--- +title: Gestionar las compras nuevas y las pruebas gratuitas +intro: 'Cuando un cliente compra un plan de pago, una prueba gratuita, o la versión gratuita de tu app de {% data variables.product.prodname_marketplace %}, recibirás el webhook de [evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `comprado`, lo cual inicia el flujo de compra.' +redirect_from: + - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps/ + - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/ + - /marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials +versions: + free-pro-team: '*' +--- + + + +{% warning %} + +Si ofreces una GitHub App en {% data variables.product.prodname_marketplace %}, ésta debe identificar a los usuarios utilizando el flujo de autorización de OAuth. No necesitas configurar un a App de OAuth por separado para apoyar a este flujo. Consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obtener más información. + +{% endwarning %} + +### Paso 1. Compra inicial y evento de webhook + +Antes de qeu un cliente compre tu app de {% data variables.product.prodname_marketplace %}, ellos elligen un [plan del listado](/marketplace/selling-your-app/github-marketplace-pricing-plans/). También eligen si quieren comprar la app desde su cuenta personal o su cuenta de organización. + +El cliente completa la compra dando clic en **Completar orden y comenzar con la instalación**. + +Entonces GitHub envía a tu app el webhook de la [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) con la acción `purchased`. + +Lee el objeto `effective_date` y `marketplace_purchase` del webhook de `marketplace_purchase` para determinar qué plan compró el cliente, cuándo inicia el ciclo de facturación, y cuándo comienza el siguiente ciclo de facturación. + +Si tu app ofrece una prueba gratuita, lee el atributo `marketplace_purchase[on_free_trial]` del webhook. Si el valor es `true`, tu app necesitará rastrear la fecha de inicio de la prueba gratuita (`effective_date`) y la fecha en la cual termina éste (`free_trial_ends_on`). Utiliza la fecha `free_trial_ends_on` para mostrar los días restantes en una prueba gratuita en la IU de tu app. Puedes hacerlo ya sea en un letrero o en tu [IU de facturación](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para saber cómo administrar las cancelaciones antes de que termine un periodo de prueba gratuita, consulta la sección "[Administrar las cancelaciones de planes](/developers/github-marketplace/handling-plan-cancellations)". Consulta la sección "[Administrar los cambios de planes](/developers/github-marketplace/handling-plan-changes)" para encontrar más información sobre cómo hacer la transición de un plan de prueba gratuito a un plan de pago cuando el primero venza. + +Consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" para encontrar un ejemplo de la carga últil del evento `marketplace_purchase`. + +### Paso 2. Instalación + +Si tu app es una GitHub App, GitHub pide al cliente que seleccione a qué repositorios puede acceder la app cuando la compran. Entonces, GitHub instala la app en la cuenta que escogió el cliente y le otorga acceso a los repositorios seleccionados. + +En este punto, si especificaste una **URL de configuración** en los ajustes de tu GitHub App, GitHub redirigirá al cliente hacia esa URL. Si no especificas una URL de configuración, no podrás gestionar las compras de tu GitHub App. + +{% note %} + +**Nota** La **URL de configuración** se describe como opcional en los ajustes de la GitHub App, pero es un campo requerido si quieres ofrecer tu app en {% data variables.product.prodname_marketplace %}. + +{% endnote %} + +Si tu app es una App de OAuth, GitHub no la instala en ningún lugar. En vez de esto, GitHub redirige al usuario a la **URL de instalación** que especificaste en tu [listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). + +Cuando un cliente compra una App de OAuth, GitHub lo redirige a la URL que escoges (ya sea de configuración o de instalación) y ésta nicluye el plan de precios que eligió el cliente como un parámetro de consulta: `marketplace_listing_plan_id`. + +### Paso 3. Autorización + +Cuando un cliente compra tu app, debes enviar a dicho cliente a través del flujo de autorización de OAuth: + +* Si tu app es una GitHub App, inicia el flujo tan pronto GitHub redireccione al cliente a la **URL de configuración**. Sigue los pasos en la sección "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". + +* Si tu app es una App de OAuth, inicia el flujo de autorización tan pronto como GitHub redirija al usuario a la **URL de instalación**. Sigue los pasos de la sección "[Autorizar las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/)". + +Para cualquier tipo de app, el primer paso es redirigir al cliente a https://github.com/login/oauth/authorize. + +Después de que el ciente complete la autorización, tu app recibirá un token de acceso de OAuth para el cliente. Necesitas este token para el siguiente paso. + +{% note %} + +**Nota:** Cuando autorices a un cliente para una prueba gratuita, otórgales el mismo acceso que tendrían en el plan de pago. Los migrarás al plan pagado después de que termine el periodo de pruebas. + +{% endnote %} + +### Paso 4. Aprovisionar las cuentas de los clientes + +Tu app debe aprovisionar una cuenta de cliente para cada compra nueva. Mediante el uso del token de acceso que recibiste para el cliente en el [Paso 3. Autorización](#step-3-authorization), llama a la terminal "[Listar suscripciones para el usuario autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)". La respuesta incluirá la información de `account` del cliente y mostrará si están en una prueba gratuita (`on_free_trial`). Utiliza esta información para completar el aprovisionamiento y la configuración. + +{% data reusables.marketplace.marketplace-double-purchases %} + +Si la compra es para una organización y es por usuario, puedes solicitar al cliente que escoja qué miembros de la organización tendrán acceso a la app que se compró. + +Puedes personalizar la forma en la que los miembros de la organización reciben acceso a tu app. Aquí hay algunas sugerencias: + +**Precios con tasa fija:** Si la compra se hace para una organización que utiliza precios de tasa fija, tu app puede [obtener todos los miembros de la organización](/rest/reference/orgs#list-organization-members) a través de la API y solicitar al administrador de la organización que elija qué miembros tendrán usuarios en plan de pago de lado del integrador. + +**Precios por unidad:** Un método para aprovisionar plazas por unidad es permitir a los usuarios que ocupen una plaza conforme inicien sesión en la app. Una vez que el cliente llegue al umbral de conteo de plazas, tu app puede notificarle que necesita mejorar el plan a través de {% data variables.product.prodname_marketplace %}. diff --git a/translations/es-ES/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/es-ES/content/developers/github-marketplace/handling-plan-cancellations.md new file mode 100644 index 0000000000000..3eaccf930d7bf --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/handling-plan-cancellations.md @@ -0,0 +1,33 @@ +--- +title: Gestionar las cancelaciones de plan +intro: 'El cancelar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `cancelada`, lo cual inicia el flujo de cancelación.' +redirect_from: + - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/ + - /marketplace/integrating-with-the-github-marketplace-api/cancelling-plans +versions: + free-pro-team: '*' +--- + + + +Para obtener más información acerca de las cancelaciones de acuerdo a como se relaciona con la facturación, consulta la sección "[Cobrar a los usuarios en {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)". + +### Paso 1. Evento de cancelación + +Si un cliente decide cancelar una orden de {% data variables.product.prodname_marketplace %}, GitHub envía un webhook de [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) conla acción `cancelled` a tu app cuando tome efecto dicha cancelación. Si el cliente cancela durante un periodo de prueba gratuito, tu app recibirá el vento de inmediato. Cuando un cliente cancela un plan pagado, la cancelación tomará lugar al final del ciclo de facturación del cliente. + +### Paso 2. Desactivar las cuentas de usuario + +Cuando un cliente cancela un plan pagado o gratuito, tu app debe llevar a cabo estos pasos para completar la cancelación: + +1. Desactivar la cuenta del cliente que canceló su plan. +1. Revocar el token de OAuth que recibió tu app para el cliente. +1. Si tu app es una App de OAuth, eliminar todos los webhooks que creó tu app para los repositorios. +1. Eliminar todos los datos del cliente en los primeros 30 días de que se recibió el evento `cancelled`. + +{% note %} + +**Nota:** Te recomendamos utilizar la `effective_date` del webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar cuándo ocurrirá un cambio de plan y así sincronizar a menudo el [Listar las cuentas para un plan](/rest/reference/apps#list-accounts-for-a-plan). Para obtener más informació sobre los webhooks, consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/handling-plan-changes.md b/translations/es-ES/content/developers/github-marketplace/handling-plan-changes.md new file mode 100644 index 0000000000000..c7428cd38e739 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/handling-plan-changes.md @@ -0,0 +1,64 @@ +--- +title: Gestionar cambios de plan +intro: 'El mejorar y degradar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) con la acción `cambiada`, lo cual inicia el flujo de mejora o degradación.' +redirect_from: + - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/ + - /marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans +versions: + free-pro-team: '*' +--- + + + +Para obtener más información acerca de mejorar y degradar los planes de acuerdo a como se relaciona con la facturación, consulta la sección "[Integrarse con la API de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/)". + +### Paso 1. Evento de cambio en el plan de precios + +GitHub envía el webhook `marketplace_purchase` con la acción `changed` a tu app cuando el cliente hace cualquiera de estos cambios a su orden de {% data variables.product.prodname_marketplace %}: +* Mejorar a un plan de precios más caro o degradarlo a uno más barato. +* Agregar o eliminar plazas a su plan existente. +* Cambiar el ciclo de facturación. + +GitHub enviará el webhook cuando el cambio entre en vigor. Por ejemplo, cuando un cliente degrada un plan, GitHub envía el webhook al final del ciclo de facturación del cliente. GitHub envía un webhook a tu app inmediatamente cuando un cliente mejora su plan para permitirle el acceso al servicio nuevo de inmediato. Si un cliente cambia de un ciclo mensual a uno anual, esto se considera como una mejora. Consulta la sección "[Cobrar a los clientes en {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" para aprender más acerca de las acciones que se consideran una mejora o una degradación. + +Lee `effective_date`, `marketplace_purchase`, y `previous_marketplace_purchase` del webhook de `marketplace_purchase` para actualizar la fecha de inicio del plan y hacer cambios al ciclo de facturació y plan de precios del cliente. Consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" para encontrar un ejemplo de la carga últil del evento `marketplace_purchase`. + +Si tu app ofrece periodos de prueba gratuitos, recibirás el webhook de `marketplace_purchase` con la acción `changed` cuando caduque este periodo de prueba. Si el periodo de prueba gratuito del cliente caduca, mejora al cliente a la versión pagada del plan de prueba gratuito. + +### Paso 2. Actualizar las cuentas de usuario + +Necesitarás actualizar la información de las cuentas de usuario para que se reflejen los cambios en el ciclo de facturación y en el plan de precios que el cliente hizo en su orden de {% data variables.product.prodname_marketplace %}. Muestra las mejoras al plan de precios, `seat_count` (para planes de precios por unidad), y ciclo de facturación en el sitio web de tu app de Marketplace en la IU de la misma cuando recibas el webhook de la acción `changed`. + +Cuando un cliente degrada un plan, se recomienda revisar si éste excedió los límites del mismo y contactarlos directamente en tu IU o por teléfono o correo electrónico. + +Para motivar a las personas a mejorar el plan, puedes mostrar una URL de mejora en la IU de tu app. Consulta la sección "[Acerca de las URL de mejora](#about-upgrade-urls)" para obtener más detalles. + +{% note %} + +**Nota:** Te recomendamos llevar a cabo una sincronización frecuente utilizando `GET /marketplace_listing/plans/:id/accounts` para asegurarte de que tu app tiene el plan, información de ciclo de facturación y conteo de unidades (para los precios por unidad) correctos para cada cuenta. + +{% endnote %} + +### Pagos de mejora fallidos + +{% data reusables.marketplace.marketplace-failed-purchase-event %} + +### Acerca de las URL de mejora + +Puedes redirigir a los usuarios desde la IU de tu app para que mejoren su plan en GitHub a través de una URL de mejora: + +``` +https://www.github.com/marketplace//upgrade// +``` + +Por ejemplo, si notas que el cliente tiene un plan de 5 personas y necesita cambiar a uno de 10, puedes mostrar un boton en la IU de tu app, el cual diga "Te mostramos como mejorar tu plan", o bien, mostrar un letrero con un enlace a la URL de mejora. La URL de mejora llevará al cliente a la página de confirmación de mejora para el plan de tu listado. + +Utiliza el `LISTING_PLAN_NUMBER` para el plan que el cliente quisiera comprar. Cuando creas planes de precios nuevos, estos reciben un `LISTING_PLAN_NUMBER`, lo cual es específico para cada plan en tu listado, y también reciben una `LISTING_PLAN_ID`, que es específica para cada plan en {% data variables.product.prodname_marketplace %}. Puedes encontrar estos números cuando [Listas los planes](/rest/reference/apps#list-plans), los cuales identifican a los planes de precios en tus listados. Utiliza la `LISTING_PLAN_ID` y la terminal "[Listar cuentas para un plan](/rest/reference/apps#list-accounts-for-a-plan)" para obtener la `CUSTOMER_ACCOUNT_ID`. + + +{% note %} + +**Nota:** Si un cliente mejora su cantidad adicional de unidades (como las plazas), aún puedes enviarlos al plan adecuado para su compra, pero no podemos dar soporte para los parámetros de `unit_count` en este momento. + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/index.md b/translations/es-ES/content/developers/github-marketplace/index.md new file mode 100644 index 0000000000000..ce31b9b8167c7 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/index.md @@ -0,0 +1,36 @@ +--- +title: GitHub Marketplace +intro: 'Lista tus herramientas en {% data variables.product.prodname_dotcom %} Marketplace para que los desarrolladores las utilicen o las compren.' +redirect_from: + - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace/ + - /apps/marketplace/ + - /marketplace +versions: + free-pro-team: '*' +--- + +{% topic_link_in_list /creating-apps-for-github-marketplace %} + {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} + {% link_in_list /requirements-for-listing-an-app %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} + {% link_in_list /viewing-metrics-for-your-listing %} + {% link_in_list /viewing-transactions-for-your-listing %} +{% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} + {% link_in_list /rest-endpoints-for-the-github-marketplace-api %} + {% link_in_list /webhook-events-for-the-github-marketplace-api %} + {% link_in_list /testing-your-app %} + {% link_in_list /handling-new-purchases-and-free-trials %} + {% link_in_list /handling-plan-changes %} + {% link_in_list /handling-plan-cancellations %} +{% topic_link_in_list /listing-an-app-on-github-marketplace %} + {% link_in_list /drafting-a-listing-for-your-app %} + {% link_in_list /writing-a-listing-description-for-your-app %} + {% link_in_list /setting-pricing-plans-for-your-listing %} + {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} + {% link_in_list /submitting-your-listing-for-publication %} +{% topic_link_in_list /selling-your-app-on-github-marketplace %} + {% link_in_list /pricing-plans-for-github-marketplace-apps %} + {% link_in_list /billing-customers %} + {% link_in_list /receiving-payment-for-app-purchases %} diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md new file mode 100644 index 0000000000000..6c03762016c52 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md @@ -0,0 +1,17 @@ +--- +title: Listar una app en GitHub Marketplace +intro: 'Aprende sobre los requisitos y mejores prácticas para listar tu app en {% data variables.product.prodname_marketplace %}.' +mapTopic: verdadero +redirect_from: + - /apps/adding-integrations/listing-apps-on-github-marketplace/ + - /apps/marketplace/listing-apps-on-github-marketplace/ + - /apps/marketplace/getting-started-with-github-marketplace-listings/ + - /apps/marketplace/creating-and-submitting-your-app-for-approval/ + - /apps/adding-integrations/managing-listings-on-github-marketplace/ + - /apps/marketplace/managing-github-marketplace-listings/ + - /apps/marketplace/listing-on-github-marketplace/ + - /marketplace/listing-on-github-marketplace +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/es-ES/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md new file mode 100644 index 0000000000000..2523f8013cb71 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -0,0 +1,57 @@ +--- +title: Planes de precios para las apps de GitHub Marketplace +intro: 'Los planes de precios te permiten darle a tu app diferentes recursos o niveles de servicio. Puedes ofrecer hasta 10 planes de precios en tu listado de {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ + - /marketplace/selling-your-app/github-marketplace-pricing-plans +versions: + free-pro-team: '*' +--- + + + +Los planes de precios de {% data variables.product.prodname_marketplace %} pueden ser gratuitos, de tasa fija, o por unidad. Los precios se configuran, muestran y procesan en dólares estadounidenses. Los planes de pago se restringen a las listas verificadas. + +Los clientes compran tu app utilizando un método de pago adjunto a su cuenta de {% data variables.product.product_name %}, sin tener que salir del {% data variables.product.prodname_dotcom_the_website %}. No tienes que escribir código para realizar las transacciones de facturación, pero tendrás que administrar los eventos desde la API de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Si la app que estás listando en {% data variables.product.prodname_marketplace %} tiene opciones de plan múltiples, puedes configurar los planes de precios correspondientes. Por ejemplo, si tu app tiene dos opciones de plan, u plan de código abierto y un plan profesional, puedes configurar un plan de precios gratuito para tu plan de código abierto y un plan de tasa fija para tu plan profesional. Cada listado de {% data variables.product.prodname_marketplace %} debe tener un precio mensual y anual para cada plan que se liste. + +Para obtener más información sobre cómo crear un plan de precios, consulta la sección "[Configurar un plan de precios del listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". + +{% data reusables.marketplace.free-plan-note %} + +### Tipos de planes de precios + +#### Planes gratuitos + +{% data reusables.marketplace.free-apps-encouraged %} + +Los planes gratuitos no tienen costo alguno para los usuarios. Si configuras un plan de precios gratuito, no puedes cobrar a los usuarios que elijan dicho plan por utilizar tu app. Puedes crear planes tanto de pago como gratuitos para tu listado. + +Todas las apps necesitan administrar los eventos de las compras nuevas y de las cancelaciones. Aquellas apps que solo tengan planes gratuitos no necesitan administrar los eventos de las pruebas gratuitas, mejoras y retrocesos. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Si agregas un plan de pago a una app que ya esté listada en {% data variables.product.prodname_marketplace %} como un servicio gratuito, necesitarás solicitar una verificación para dicha app y pasar por un proceso de integración financiera. + +#### Planes de pago + +Hay dos tipos de planes de pago: + +- Los planes de pago de tasa fija cobran una cantidad fija mensual o anualmente. + +- Los planes de pago por unidad cobran una cantidad fija ya sea mensual o anual por el tipo de unidad que especifiques. Una "unidad" puede ser lo que tu escojas (por ejemplo, un usuario, una plaza, una persona). + +Puede que también quieras ofrecer pruebas gratuitas. Estas proporcionan periodos de prueba gratuitos de 14 días en aplicaciones de GitHub y de OAuth. Cuandoconfiguras un plan de precios en Marketplace, puedes seleccionar la opción de proporcionar un plan gratuito para los planes de tasa fija o o de costo por unidad. + +### Periodos de prueba gratuitos + +Los clientes pueden iniciar un periodo de prueba gratuto para cualquier plan de pago en una lista de Marketplace que incluya pruebas gratuitas. Sin embargo, los clientes no pueden crear más de una prueba gratuita por producto de marketplace. + +Los periodos de prueba gratuitos tienen una longitud fija de 14 días. Se les notifica a los clientes 4 días antes del fin de su periodo de pruebas gratuito (en el día 11 del este periodo) sobre la mejora que se hará a su plan. Al final del periodo de pruebas gratuito, los clientes se matricularán automáticamente en el plan desde el cual estaban generando el periodo gratuito en caso de que no lo cancelen. + +Para obtener más información, consulta la sección "[Administrar las compras nuevas y las pruebas gratuitas](/developers/github-marketplace/handling-new-purchases-and-free-trials/)". + +{% note %} + +**Nota:** GitHub espera que borres cualquier dato privado del cliente dentro de los primeros 30 días después de que se cancela una prueba, iniciando con la recepción del evento de cancelación. + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md b/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md new file mode 100644 index 0000000000000..aa81aa8421863 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md @@ -0,0 +1,26 @@ +--- +title: Recibir pagos por las compras de las apps +intro: 'Al final de cada mes, recibiras los pagos de tus listados de {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/ + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/ + - /apps/marketplace/pricing-payments-and-free-trials/receiving-payment-for-a-github-marketplace-listing/ + - /apps/marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings/ + - /marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings +versions: + free-pro-team: '*' +--- + + + +After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process. + +Once your revenue reaches a minimum of $500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs. + +For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward. + +{% note %} + +**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/github/site-policy/github-marketplace-developer-agreement)." + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md new file mode 100644 index 0000000000000..907cc8964916d --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -0,0 +1,73 @@ +--- +title: Requisitos para listar una app +intro: 'Las apps que se encuentren en {% data variables.product.prodname_marketplace %} deben cumplir con los requisitos que se detallan en esta página antes de que se pueda publicar la lista.' +redirect_from: + - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ + - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ + - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace/ + - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/ + - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/ + - /marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace +versions: + free-pro-team: '*' +--- + + + +Los requisitos para listar una app en {% data variables.product.prodname_marketplace %} varían de acuerdo con si quieres ofrecer una app gratuita o de pago. + +### Requisitos para todas las listas de {% data variables.product.prodname_marketplace %} + +Todas las listas de {% data variables.product.prodname_marketplace %} deben ser para las herramientas que proporcionen valor a la comunidad de {% data variables.product.product_name %}. Cuando emites tu lista para que se publique debes leer y aceptar las condiciones del [Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". + +#### Requisitos de la experiencia del usuario para todas las apps + +Todas las listas deben cumplir con los siguientes requisitos, sin importar si son para una app gratuita o de pago. + +- Las listas no deben persuadir activamente a los usuarios de que salgan de {% data variables.product.product_name %}. +- Las listas deben incluir la información de contacto válida del publicador. +- Las listas deben tener una descripción relevante de la aplicación. +- Las listas deben especificar un plan de precios. +- Las apps deben proporcionar valor a los clientes e integrarse con la plataforma de alguna forma más allá de la autenticación. +- Las apps deben estar disponibles al público en {% data variables.product.prodname_marketplace %} y no pueden estar en fase beta o únicamente disponibles con invitación. +- Las apps deben contar con eventos de webhook configurados para notificar al publicador sobre cualquier cancelación o cambio en el plan utilizando la API de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Para obtener más información sobre cómo proporcionar una buena experiencia al cliente, consulta la sección "[Mejores prácticas para la experiencia del cliente en las apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)". + +#### Requisitos de marca y de listado para todas las apps + +- Las apps que utilizan los logos de GitHub deben seguir los lineamientos de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Logos de {% data variables.product.company_short %} y su uso](https://github.com/logos)". +- Las apps deben tener un logo, tarjeta de características, e imágenes de impresión de pantalla que cumplan con las recomendaciones que se proporcionan en "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". +- Los listados deben incluir descripciones que estén bien escritas y no tengan errores gramaticales. Para obtener orientación sobre cómo escribir tu listado, consulta la sección "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". + +Para proteger a tus clientes, te recomendamos que también sigas las mejores prácticas de seguridad. Para obtener más información, consulta la sección "[Mejores prácticas de seguridad para las apps](/developers/github-marketplace/security-best-practices-for-apps)". + +### Consideraciones para las apps gratuitas + +{% data reusables.marketplace.free-apps-encouraged %} + +### Requisitos para las apps de pago + +Adicionalmente a los requisitos para todas las apps que se mencionaron anteriormente, cada app que ofrezcas en {% data variables.product.prodname_marketplace %} como un servicio pagado deberá cumplir con los siguientes requisitos: + +- Las {% data variables.product.prodname_github_app %} deben contar con un mínimo de 100 instalaciones. +- Las {% data variables.product.prodname_oauth_app %} deben tener un mínimo de 200 usuarios. +- Todas las apps de pago deben gestinar los eventos de compra de {% data variables.product.prodname_marketplace %} para las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información, consulta la sección "[Requisitos de facturación para las apps de pago](#billing-requirements-for-paid-apps)" que se encuentra más adelante. +- Las organizaciones publicadoras deben tener un dominio verificado y deben habilitar la autenticación bifactorial. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en tu organización](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + +Cuando estés listo para publicar la app en {% data variables.product.prodname_marketplace %}, deberás solicitar la verificación de la lista. + +{% note %} + +El proceso de verificación está disponible para las organizaciones. {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección: "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% endnote %} + +### Requisitos de facturación para las apps de pago + +Tu app no necesita administrar pagos, pero sí necesita utilizar los eventos de compra de {% data variables.product.prodname_marketplace %} para administrar las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información sobre cómo integrar estos eventos en tu app, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +El utilizar la API de facturación de GitHub permite a los clientes comprar una app sin salir de GitHub y pagar por el servicio con el método de pago que ya está adjunto a su cuenta de {% data variables.product.product_name %}. + +- Las apps deben permitir facturación mensual y anual para las compras de sus sucripciones de pago. +- Los listados pueden ofrecer cualquier combienación de planes gratuitos y de pago. Los planes gratuitos son opcionales, pero se les fomenta. Para obtener más información, consulta la sección "[Configurar un plan de precios para los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". diff --git a/translations/es-ES/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md new file mode 100644 index 0000000000000..183edc83ada32 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api.md @@ -0,0 +1,30 @@ +--- +title: Terminales de REST para la API de GitHub Marketplace +intro: 'Para ayudarte a adminsitrar tu app en {% data variables.product.prodname_marketplace %}, utiliza estas terminales de la 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/ + - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints +versions: + free-pro-team: '*' +--- + + + +Aquí te mostramos algunas terminales útiles que están disponibles para los listados de Marketplace: + +* [Listar planes](/rest/reference/apps#list-plans) +* [Listar cuentas para un plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Obtener un plan de suscripción para una cuenta](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [Listar las suscripciones del usuario autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) + +Consulta estas páginas para encontrar más detalles sobre cómo autenticarte cuando utilices la API de {% data variables.product.prodname_marketplace %}: + +* [Opciones de autorización para las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) +* [Opciones de autenticación para las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/) + +{% note %} + +**Nota:** [Los límites de tasa para la API de REST](/rest#rate-limiting) aplican para todas las terminales de la API de {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/es-ES/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000000..cd1a62c35318b --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Mejores prácticas de seguridad para las apps +intro: 'Lineamientos para preparar una app segura para que se comparta en {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Mejores prácticas de seguridad +versions: + free-pro-team: '*' +--- + +El seguir estas mejores prácticas te ayudará a proporcionar una experiencia de usuario segura. + +### Autorización, autenticación, y control de accesos + +Te recomendamos crear una GitHub App en vez de una OAuth App. {% data reusables.marketplace.github_apps_preferred %}. Consulta la sección "[Diferencias entre las GitHub Apps y las Apps de OAuth](/apps/differences-between-apps/)" para encontrar más detalles. +- Las apps deben utilizar el principio del menor privilegio necesario y solo deberán solicitar los alcances de OAuth y permisos de GitHub Apps que dicha app necesite para llevar a cabo su funcionalidad prevista. Para obtener más información, consulta la sección [Principio del menor privilegio necesario](https://en.wikipedia.org/wiki/Principle_of_least_privilege) en Wikipedia. +- Las apps deben proporcionar a los clientes una forma de borrar su cuenta, sin tener que enviar un correo electrónico o llamar a una persona de soporte. +- Las apps no deben compartir tokens entre las diferentes implementaciones de la misma. Por ejemplo, una app de escritorio debe tener un token separado de aquella que es basada en web. Los tokens individuales permiten a cada app solicitar el acceso necesario a los recursos de GitHub por separado. +- Diseña tu app con diferentes roles de usuario, dependiendo de la funcionalidad que necesita cada tipo de usuario. Por ejemplo, un usuario estándar no debe tener acceso a la funcionalidad de administrador, y los gerentes de facturación podrían no requerir acceso de carga al código de un repositorio. +- Las apps no deben compartir cuentas de servicio tales como servicios de correo electrónico o de bases de datos para administrar tu servicio SaaS. +- Todos los servicios que se utilicen en tu app deben contar con credenciales únicas de nombre de inicio de sesión y contraseña. +- El acceso privilegiado de administrador para la infraestructura de alojamiento productiva solo se deberá otorgar a los ingenieros y empleados con obligaciones administrativas. +- Las apps no deben utilizar tokens de acceso personal para autenticarse en ellas y deberán autenticarse como una [App de OAuth](/apps/about-apps/#about-oauth-apps) o una [GitHub App](/apps/about-apps/#about-github-apps): + - Las apps de OAuth deben autenticarse utilizando un [Token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). + - Las GitHub Apps deben autenticarse utilizando ya sea un [Token Web de JSON (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), un [token de OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), o un [token de acceso a la instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### Protección de datos + +- Las apps deben cifrar los datos que se transfieren a través del internet público utilizando HTTPS con un certificado TLS válido o con SSH para Git. +- Las apps deben almacenar las llaves secretas y las ID de los clientes de forma segura. Te recomendamos almacenarlas como [variables de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Las apps deben borrar todos los datos de usuario de GitHub dentro de los 30 días posteriores de recibir una solicitud del usuario para hacerlo, o dentro de 30 días posteriores al final de la relación legal del usuario con GitHub. +- Las apps no deben requerir que el usuario proporcione su contraseña de GitHub. +- Las apps deben cifrar los tokens, ID de cliente y secretos de cliente. + +### Registro y monitoreo + +Las apps deben tener capacidad de monitoreo y de ingreso de usuarios. Las bitácoras de las apps deben retenerse por lo menos por 30 días y archivarse por un mínimo de un año. Un log de seguirdad debería incluir: + +- Eventos de autenticación y autorización +- Cambios a la configuración del servicio +- Escritura y lectura de objetos +- Todos los cambios de permisos de usuarios y grupos +- Elevación de rol a aquel de administrador +- Marca de tiempo consistente para cada evento +- Usuarios orgien, direcciones IP, y/o nombres de host para todas las acciones registradas + +### Flujo de trabajo de respuesta a incidentes + +Para proporcionar una experiencia segura a los usuarios, debes tener un plan claro de respuesta a incidentes antes de listar tu app. Te recomendamos tener un equipo de respuesta a incidentes para operaciones y de seguridad en tu compañía en vez de utilizar un proveedor tercero. Debes poder notificar a {% data variables.product.product_name %} dentro de las primeras 24 horas de que se confirme un incidente. + +Para obtener un ejemplo de un flujo de trabajo de respuesta a incidentes, consulta la "Política de Respuesta a Fuga de Datos" en el [Sitio web del insitituto SANS](https://www.sans.org/information-security-policy/). Un documento corto con pasos claros a tomar en caso de un incidente es más valioso que una plantilla larga de una política. + +### Administración de vulnerabilidades y flujo de trabajo de parchado + +Debes llevar a cabo escaneos de vulnerabilidades frecuentes para la infraestructura productiva. Debes clasificar los resultados de los escaneos de vulnerabilidades y definir un tiempo en el que acuerdes remediar dichas vulnerabilidades. + +Si no estás listo para configurar un programa completo de administración de vulnerabilidades, es útil comenzar creando un proceso de parchado. Para obtener orientación sobre la creación de una política de administración de parches, consulta este artículo de TechRepublic: "[Establecer una política de administración de parches](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)". diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md new file mode 100644 index 0000000000000..45ea865274cab --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md @@ -0,0 +1,15 @@ +--- +title: Vender tu app en GitHub Marketplace +intro: 'Aprende sobre los requisitos y mejores prácticas para vender tu app en {% data variables.product.prodname_marketplace %}.' +mapTopic: verdadero +redirect_from: + - /apps/marketplace/administering-listing-plans-and-user-accounts/ + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/ + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/ + - /apps/marketplace/pricing-payments-and-free-trials/ + - /apps/marketplace/selling-your-app/ + - /marketplace/selling-your-app +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md new file mode 100644 index 0000000000000..ba13e1e6ce23b --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -0,0 +1,77 @@ +--- +title: Configurar planes de precios para tu listado +intro: 'Cuando listas tu app en {% data variables.product.prodname_marketplace %}, puedes elegir proporcionarla como un servicio gratuito o venderla. Si planeas vender tu app, puedes crear planes de precio diferentes para los diferentes escalones de características.' +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/ + - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan/ + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ + - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans/ + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ + - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan/ + - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/ + - /marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan +versions: + free-pro-team: '*' +--- + +### Acerca de configurar planes de precios + +Si quieres vender una app en {% data variables.product.prodname_marketplace %}, necesitas solicitar una verificación cuando publicas la lista para tu app. Durante el proceso de verificación, un experto en integración revisará la identidad de la organización y su configuración de seguridad. El experto en integración también llevará a la organización a través de una integración financiera. Para obtener más información, consulta la sección "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección: "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% data variables.product.prodname_marketplace %} ofrece varios tipos diferentes de planes de precios. Para obener información detallada, consulta la sección "[Planes de precios para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". + +### Acerca de guardar los planes de precios + +Puedes guardar los planes de precios con los estados de "borrador" o de "publicado". Si aún no emites tu listado de {% data variables.product.prodname_marketplace %} para su aprobación, los planes publicados funcionarán de la misma forma que los planes en borrador hasta que se apruebe tu listado y se muestre en {% data variables.product.prodname_marketplace %}. Los planes en borrador te permiten crear y guardar nuevos planes de precios sin hacerlos disponibles en tu página de listado de {% data variables.product.prodname_marketplace %}. Una vez que publicas un plan de precios en un listado publicado, éste estará disponible para que los clientes lo compren de inmediato. Puedes publicar hasta 10 planes de precios. + +Para obtener lineamientos sobre la facturación a clientes, consulta la sección "[Facturar a clientes](/developers/github-marketplace/billing-customers)". + +### Crear planes de precios + +Para crear un plan de precios para tu listado de {% data variables.product.prodname_marketplace %}, da clic en **Planes y precios** en la barra lateral izquierda de tu [página de listado de{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Para obtener más información, consulta la sección "[Crear un borrador de listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)". + +Cuando das clic en **Nuevo borrador de plan**, verás un formato que te permite personalizar tu plan de precios. Necesitarás configurar los siguientes cambios para crear un plan de precios: + +- **Nombre del plan** - El nombre de tu plan de precios aparecerá en la página de llegada de tu app de {% data variables.product.prodname_marketplace %}. Puedes personalizar el nombre de tu plan de precios para que se ajuste con los recursos del plan, el tamaño de la compañía que lo utilizará, o con lo que gustes. + +- **Modelos de precios** - Hay tres tipos de planes de precios: grtuito, tasa fija, y por unidad. Todos los planes requieren que proceses eventos de compras nuevas y de cancelaciones desde la API de marketplace. Adicionalmente, para los planes pagados: + + - Debes configurar un precio para las suscripciones tanto anuales como mensuales en dólares estadounidenses. + - Tu app debe procesar los eventos de cambio de planes. + - Debes solicitar la verificación para publicar un listado con un plan de pago. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} + + Para obtener información detallada, consulta las secciones "[Planes de precios para las apps de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" y "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +- **Disponible para** - Los planes de precios de {% data variables.product.prodname_marketplace %} pueden aplicar para las **cuentas personales y de organización**, **Cuentas personales únicamente**, o **Cuentas de organización únicamente**. Por ejemplo, si tu plan de precios es por unidad y proporciona plazas múltioples, seleccionarías **únicamente para cuentas de organización**, ya que no hay manera de asignar plazas a las personas de la organización desde una cuenta personal. + +- **Descripción corta** - Escribe un resumen breve de los detalles del plan de precios. La descripción puede incluir el tipo de cliente para el cual se creó el plan o los recursos que dicho plan incluye. + +- **Viñetas** - Puedes escribir hasta cuatro viñetas que incluyan más detalles sobre tu plan de precios. Estas viñetas pueden incluir los casos de uso de tu app o listar información más detallada acerca de los recursos o de las características que incluye el plan. + +{% data reusables.marketplace.free-plan-note %} + +### Cambiar un plan de precios del listado de {% data variables.product.prodname_marketplace %}. + +Si ya no se requiere algún plan de precios para tu listado de {% data variables.product.prodname_marketplace %}, o si necesitas ajustar los detalles de los precios, puedes eliminarlo. + +![Botón para eliminar tu plan de precios](/assets/images/marketplace/marketplace_remove_this_plan.png) + +No podrás hacer cambios a un plan de precios para una app que ya está listada en {% data variables.product.prodname_marketplace %} una vez que lo publiques. En su lugar, necesitarás eliminar el plan de precios y crear un plan nuevo. Los clientes que ya compraron el plan de precios que se eliminó seguirán utilizándolo hasta que decidan abandonarlo y migrarse a un plan de precios nuevo. Para encontrar más información acerca de los planes de precios, consulta la sección "[planes de precios en {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". + +Una vez que elimines el plan de precios, los usuarios ya no podrán comprar tu app utilizando dicho plan. Los usuarios existentes del plan que eliminaste seguirán en ese plan hasta que cancelen su suscripción. + +{% note %} + +**Nota:** {% data variables.product.product_name %} no puede eliminar a los usuarios de un plan de precios que ya no existe. Puedes lanzar una campaña para exhortar a los usuarios a mejorar o degradar su suscripción para el plan de precios que eliminaste hacia un plan nuevo. + +{% endnote %} + +Puedes inhabilitar los periodos de prueba gratuitos en GitHub Marketplace sin retirar el plan de precios, pero esto te impide inciar periodos de prueba gratuitos en el futuro para este plan. Si eliges inhabilitar los periodos de prueba gratuitos para un plan de precios, los usuarios que ya se hayan registrado pueden completar su periodo de prueba gratuito. + +Después de dar de baja un plan de precios, puedes crear uno nuevo con el mismo nombre que aquél que eliminaste. Por ejemplo, si tienes un plan de precios "Pro" pero necesitas cambiar el precio de tasa fija, puedes eliminar el plan "Pro" y crear uno nuevo, que también sea "Pro" con un precio actualizado. Los usuarios podrán comprar el nuevo plan de precios inmediatamente. diff --git a/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000000..f6163f3b39c1b --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Emitir tu listado para que se publique +intro: 'Puedes emitir tu listado para que lo utilice la comunidad de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Una vez que hayas completado el listado para tu app, verás dos botones que te permiten solicitar la publicación del mismo con o sin verificación. El botón **Solicitar** para "Publicar sin verificación" estará inhabilitado si publicaste cualquier plan de precios en el listado. + +![Botón para solicitudes verificadas y sin verificar](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +Un experto en incorporación te contactará con información adicional después de que emitas tu listado para su revisión. + +Para encontrar un resumen del proceso para crear y emitir un listado, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)". + +### Prerequisitos para publicar con verificación + +Antes de que solicites una verificación para tu listado, necesitarás integrar los flujos de facturación y webhook de {% data variables.product.prodname_marketplace %} en tu app. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Si cumpliste con los requisitos de los listados y te integraste con la API de {% data variables.product.prodname_marketplace %}, puedes seguir con la emisión de tu listado. Para obtener más información, consulta la sección "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección "[Transferir una app a una organización antes de emitirla](#transferring-an-app-to-an-organization-before-you-submit)" que se encuentra más adelante. + +### Transferir una app a una organización antes de emitirla + +No puedes vender una app que pertenezca a una cuenta de usuario. Necesitas transferir la app a una organización que ya constituya un creador verificado, o que pueda solicitar la verificación de un listado para la app. Para obtener más detalles, consulta: + +1. "[Crear una organización desde cero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferir la propiedad de una GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" o "[Transferir la propiedad de una OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/es-ES/content/developers/github-marketplace/testing-your-app.md b/translations/es-ES/content/developers/github-marketplace/testing-your-app.md new file mode 100644 index 0000000000000..c5049fa5fdd53 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/testing-your-app.md @@ -0,0 +1,44 @@ +--- +title: Probar tu app +intro: 'GitHub te recomienda probar tu app con las API y los webhooks antes de emitir tu listado a {% data variables.product.prodname_marketplace %} para que puedas proporcionar una experiencia ideal para los clientes. Antes de que un experto de incorporación apruebe tu app, ésta deberá administrar los flujos de facturación adecuadamente.' +redirect_from: + - /apps/marketplace/testing-apps-apis-and-webhooks/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ + - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps +versions: + free-pro-team: '*' +--- + + + +### Probar las apps + +Puedes utilizar un borrador de listado de {% data variables.product.prodname_marketplace %} para simular cada uno de los flujos de facturación. Un listado en estado de borrador significa que no se ha emitido para aprobación. Cualquier compra que hagas utilizando un borrador de listado de {% data variables.product.prodname_marketplace %} _no_ creará transacciones reales, y GitHub no hará cargos a tu tarjeta de crédito. Para obtener más información, consulta las secciones "[Hacer un borrador de listado para tu app](/developers/github-marketplace/drafting-a-listing-for-your-app)" y "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +#### Utilizar una app de desarrollo con un borrador de listado para probar los cambios + +Un listado de {% data variables.product.prodname_marketplace %} únicamente puede asociarse con un solo registro de app, y cada app puede acceder únicamente a su propio listado de {% data variables.product.prodname_marketplace %}. Es por esto que te recomendamos configurar una app de desarrollo por separado con la misma configuración que la productiva, y que crees un _borrador_ de listado de {% data variables.product.prodname_marketplace %} que puedas utilizar para las pruebas. El borrador del listado de {% data variables.product.prodname_marketplace %} te permite probar los cambios sin afectar a los usuarios activos de tu app productiva. Nunca tendrás que emitir tu listado de desarrollo de {% data variables.product.prodname_marketplace %}, ya que solo lo utilizarás para las pruebas. + +Ya que solo puedes crear un borrador de listado de {% data variables.product.prodname_marketplace %} para las apps públicas, debes poner tu app de desarrollo como pública. Las apps públicas no pueden descubrirse fuera de los listados publicados de {% data variables.product.prodname_marketplace %} mientras no compartas la URL de éstas. Solo el dueño de la aplicación podrá ver el lsitado de Marketplace en su estado de borrador. + +Una vez que cuentes con una app de desarrollo con un listado en estado de borrador, puedes utilizarla para probar los cambios que hagas a dicha app mientras que lo integras con la API y los webhooks de {% data variables.product.prodname_marketplace %}. + +{% warning %} + +No hagas compras de prueba con las apps que están activas en {% data variables.product.prodname_marketplace %}. + +{% endwarning %} + +#### Simular eventos de compra en Marketplace + +Tus escenarios de prueba podrían requerir que configures los planes de los listados que ofrecen periodos de prueba gratuitos y que cambies entre las suscripciones de pago y gratuitas. Ya que los decrementos y las cancelaciones no toman efecto sino hasta el siguiente ciclo de facturación, GitHub proporciona una característica exclusiva para desarrolladores para "Aplicar el Cambio Pendiente", la cual fuerza las acciones de `changed` y `cancelled` para que tomen efecto inmediatamente. Puedes acceder a la opción de **Aplicar Cambios Pendientes** para las apps con listados de Marketplace en estado de _borrador_ en https://github.com/settings/billing#pending-cycle: + +![Aplicar el cambio pendiente](/assets/images/github-apps/github-apps-apply-pending-changes.png) + +### Probar las API + +También proporcionamos terminales de prueba para muchas de las terminales de las API de {% data variables.product.prodname_marketplace %}, las cuales devuelven datos falsos de código predefinido que puedes utilizar para hacer pruebas. Para recibir datos de prueba, debes especificar las URL de prueba que incluyan `/stubbed` en la ruta (por ejemplo, `/user/marketplace_purchases/stubbed`). Para obtener una lista de terminales que son compatibles con este acercamiento de datos de prueba, consulta la sección de [terminales de {% data variables.product.prodname_marketplace %}](/rest/reference/apps#github-marketplace). + +### Probar los webhooks + +GitHub proporciona herramientas para probar tus cárgas útiles desplegadas. Para obtener más información, consulta la sección "[Probar los webhooks](/webhooks/testing/)". diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md new file mode 100644 index 0000000000000..6f5b4e681da05 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md @@ -0,0 +1,12 @@ +--- +title: Utilizar la API de GitHub Marketplace en tu app +intro: 'Aprende cómo integrar la API y eventos de webhook de {% data variables.product.prodname_marketplace %} en tu app para {% data variables.product.prodname_marketplace %}.' +mapTopic: verdadero +redirect_from: + - /apps/marketplace/setting-up-github-marketplace-webhooks/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/ + - /marketplace/integrating-with-the-github-marketplace-api +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/developers/github-marketplace/viewing-metrics-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/viewing-metrics-for-your-listing.md new file mode 100644 index 0000000000000..cb685cb99d2eb --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/viewing-metrics-for-your-listing.md @@ -0,0 +1,54 @@ +--- +title: Visualizar las métricas para tu listado +intro: 'La página de perspectivas de {% data variables.product.prodname_marketplace %} muestra métricas para tu {% data variables.product.prodname_github_app %}. Puedes utilizar las métricas para rastrear el desempeño de tu {% data variables.product.prodname_github_app %} y tomar decisiones informadas acerca de los precios, planes, periodos de prueba gratuitos, y de cómo visualizar los efectos de las campañas de marketing.' +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/ + - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/ + - /marketplace/github-marketplace-insights +versions: + free-pro-team: '*' +--- + + + +Puedes ver las métricas del día anterior (24 horas), de la semana, el mes, o de la duración total de tiempo que ha estado listada tu {% data variables.product.prodname_github_app %}. + +{% note %} + +**Nota:** Ya que el agregar datos es tardado, notarás un atraso ligero en las fechas que se muestran. Cuando seleccionas un periodo de tiempo, puedes ver las fechas exactas para las métricas en la parte superior de la página. + +{% endnote %} + +### Métricas de rendimiento + +La página de perspectivas muestra estas métricas de rendimiento para el periodo de tiempo que selecciones: + +* **Valor de la suscripción:** La ganancia total posible (en dólares estadounidenses) de las suscripciones. Este valor representa la ganancia posible si no se cancela ningún plan o periodo de prueba gratuito para que todas las transacciones de tarjetas bancarias tengan éxito. El valor de la suscripción incluye el valor total de los planes que comeinzan con un periodo de prueba gratuito en el periodo de tiempo seleccionado, aún cuando no hay transacciones financieras en dicho periodo de tiempo. El valor de la suscripción también incluye un valor completo de los planes actualizados en el periodo de tiempo seleccionado pero no incluye la cantidad prorrateada. Para ver y descargar las transacciones individuales, consulta la sección "[transacciones de GitHub Marketplace](/marketplace/github-marketplace-transactions/)". +* **Visitantes:** Cantidad de personas que han visto una página en tu listado de GitHub Apps. Esta cantidad incluye tanto a los visitantes que han iniciado sesión como a los que salen de sesión. +* **Visualizaciones de página:** Cantidad de visualizaciones que han recibido las páginas en tu listado de GitHub Apps. Un solo visitante puede generar más de una visualización de página. + +{% note %} + +**Nota:** El valor estimado de tu suscripción podría ser mucho mayor que el de las transacciones procesadas durante este periodo de tiempo. + +{% endnote %} + +#### Rendimiento de conversión + +* **Visitantes únicos en la página de llegada:** Cantidad de personas que vieron la página de llegada de tu GitHub App. +* **Visitantes únicos de la página pago:** Cantidad de personas que vieron una de tus páginas de pago para tu GitHub App. +* **Página de pago para suscripciones nuevas:** La cantidad total de suscripciones pagadas, periodos de prueb gratuitos, y suscripciones gratuitas. Consulta la sección "Desglose del total de las suscripciones" para encontrar la cantidad específcia de cada tipo de suscripción. + +![Perspectivas de Marketplace](/assets/images/marketplace/marketplace_insights.png) + +Para acceder a las perspectivas de {% data variables.product.prodname_marketplace %}: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.marketplace_apps %} +4. Selecciona la +la {% data variables.product.prodname_github_app %} para la cual te gustaría ver las perspectivas. +{% data reusables.user-settings.edit_marketplace_listing %} +6. Da clic en la pestaña **Perspectivas**. +7. Opcionalmente, selecciona cualquier periodo de tiempo diferente dando clic en el menú desplegable de dicho periodo en la esquina superior derecha de la página de perspectivas. ![Periodo de tiempo de Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md new file mode 100644 index 0000000000000..0b8ee7a3896e4 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -0,0 +1,46 @@ +--- +title: Visualizar las transacciones para tu listado +intro: 'La página de transacciones de {% data variables.product.prodname_marketplace %} te permite descargar y visualizar todas las transacciones de tu listado de {% data variables.product.prodname_marketplace %}. You can view transactions 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.' +redirect_from: + - /marketplace/github-marketplace-transactions +versions: + free-pro-team: '*' +--- + + + +{% note %} + +**Nota:** Ya que el agregar datos es tardado, notarás un atraso ligero en las fechas que se muestran. Cuando seleccionas un periodo de tiempo, puedes ver las fechas exactas para las métricas en la parte superior de la página. + +{% endnote %} + + +Puedes visualizar o descargar los datos de las transacciones para dar seguimiento a la actividad de tus suscripciones. Da clic en el botón de **Exportar CSV** para descargar un archivo de tipo `.csv`. También puedes seleccionar un periodo de tiempo que quieras ver en la página de transacciones para hacer búsquedas dentro de éste. + +### Campos de datos de las transacciones + +* **date:** La fecha de la transacción en formato `aaa-mm-dd`. +* **app_name:** El nombre de la app. +* **user_login:** La información de inicio de sesión del usuario con la suscripción. +* **user_id:** La id del usuario con la suscripción. +* **user_type:** El tipo de cuenta de GitHub, ya sea `User` o `Organization`. +* **country:** El código de tres letras del país. +* **amount_in_cents:** La cantidad de la transacción en centavos. Cuando un valor es menor a la cantidad del plan, el usuario que hizo la mejora y el plan nuevo se prorratean. Un valor de cero indica que el usuario canceló el plan. +* **renewal_frequency:** La frecuencia de renovación de la suscripción, ya sea `Monthly` o `Yearly`. +* **marketplace_listing_plan_id:** La `id` del plan de suscripción. + +![Perspectivas de Marketplace](/assets/images/marketplace/marketplace_transactions.png) + +### Acceder a las transacciones de {% data variables.product.prodname_marketplace %} + +Para acceder a las transacciones de {% data variables.product.prodname_marketplace %}: + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.marketplace_apps %} +4. Selecciona la +la {% data variables.product.prodname_github_app %} de la cual quisieras ver las transacciones. +{% data reusables.user-settings.edit_marketplace_listing %} +6. Da clic en la pestaña de **Transacciones**. +7. Opcionalmente, selecciona un periodo de tiempo diferente dando clic en el menú desplegable de "Periodo" en la esquina superior derecha de la página de Transacciones. ![Periodo de tiempo de Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md new file mode 100644 index 0000000000000..e6723353e5df9 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -0,0 +1,73 @@ +--- +title: Eventos de webhook para la API de GitHub Marketplace +intro: 'Una app de {% data variables.product.prodname_marketplace %} recibe información acerca de los cambios en el plan de un usuario desde el webhook del evento de compra en Marketplace. Un evento de compra de marketplace se activa cuando un usuario compra, cancela o cambia su plan de pago.' +redirect_from: + - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ + - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ + - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events +versions: + free-pro-team: '*' +--- + + + +### Carga útil del webhook de compras en {% data variables.product.prodname_marketplace %} + +Las solicitudes de `POST` de los webhooks tienen encabezados especiales. Consulta la sección "[Encabezados de entrega de Webhooks](/webhooks/event-payloads/#delivery-headers)" para encontrar más detalles. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub. + +Las cancelaciones y disminuciones de categoría toman efecto el primer día del siguiente ciclo de facturación. Los eventos para las cancelaciones y disminuciones de categoría se envían cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación. Los eventos para las nuevas compras y mejoras de categoría comienzan inmediatamente. Utiliza `effective_date` en la carga útil del webhook para determinar cuándo comenzará un cambio. + +{% data reusables.marketplace.marketplace-malicious-behavior %} + +Cada carga útil de webhook de una `marketplace_purchase` tendrá la siguiente información: + + +| Clave | Type | Descripción | +| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada para generar el webhook. Puede ser `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, o `changed`. Para obtener más información, consulta los ejemplos de cargas útiles de webhook a continuación. **Nota:** las cargas útiles de `pending_change` y `pending_change_cancelled` contienen las mismas claves que se muestra en el [ejemplo de carga útil de `changed`](#example-webhook-payload-for-a-changed-event). | +| `effective_date` | `secuencia` | La fecha en la que la `action` se hace efectiva. | +| `sender` | `object` | La persona que tomó la `action` que activó el webhook. | +| `marketplace_purchase` | `object` | La información de compra de {% data variables.product.prodname_marketplace %}. | + +El objeto `marketplace_purchase` tiene las siguientes claves: + +| Clave | Type | Descripción | +| -------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `account` | `object` | La cuenta de `organización` o `usuario` asociada con la suscripción. Las cuentas de organización incluirán `organization_billing_email`, que es la dirección de correo electrónico administrativa de la misma. Para encontrar direcciones de correo electrónico para cuentas personales, puedes utilizar la terminal [Obtener el usuario autenticado](/rest/reference/users#get-the-authenticated-user). | +| `billing_cycle` | `secuencia` | Puede ser `yearly` o `monthly`. Cuando el dueño de la `account` tiene un plan gratuito de GitHub y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `billing_cycle` será `nil`. | +| `unit_count` | `número` | Cantidad de unidades compradas. | +| `on_free_trial` | `boolean` | Es `true` cuando la `account` está en un periodo de prueba gratuito. | +| `free_trial_ends_on` | `secuencia` | La fecha en la que caduca el periodo de prueba gratuito. | +| `next_billing_date` | `secuencia` | La fecha en la que comenzará el siguiente ciclo de facturación. Cuando el dueño de la `account` tiene un plan gratuito de GitHub.com y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `next_billing_date` será `nil`. | +| `plan` | `object` | El plan que compra el `user` u `organization`. | + +El objeto `plan` tiene las siguientes claves: + +| Clave | Type | Descripción | +| ------------------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | `número` | El identificador único para este plan. | +| `name (nombre)` | `secuencia` | El nombre del plan. | +| `description` | `secuencia` | La descripción de este plan. | +| `monthly_price_in_cents` | `número` | El precio mensual de este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 10 dólares de EEUU por mes sería de 1000 centavos. | +| `yearly_price_in_cents` | `número` | El precio anual para este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 100 dólares de EEUU por mes sería de 10000 centavos. | +| `price_model` | `secuencia` | El modelo de precios para este listado. Puede ser alguno de entre `flat-rate`, `per-unit`, o `free`. | +| `has_free_trial` | `boolean` | es `true` cuando este listado ofrece un periodo de prueba gratuito. | +| `unit_name` | `secuencia` | El nombre de la unidad. Si el modelo de precios no es `per-unit`, éste será `nil`. | +| `bullet` | `conjunto de secuencias` | Los nombres de los puntos configurados en el plan de precios. | + +
    + +#### Ejemplo de la carga útil de un webhook para un evento de `purchased` +Este ejemplo proporciona la carga útil del evento `purchased`. + +{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} + +#### Ejemplo de la carga útil de un webhook para un evento de `changed` + +Los cambios en un plan incluyen mejoras y degradaciones. Este ejemplo representa las cargas útiles de los eventos `changed`,`pending_change`, y `pending_change_cancelled`. La acción identifica cuál de estos tres eventos ha ocurrido. + +{{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }} + +#### Ejemplo de carga útil del webhook para un evento de `cancelled` + +{{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }} diff --git a/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md new file mode 100644 index 0000000000000..0d4aaf6d7dc71 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md @@ -0,0 +1,195 @@ +--- +title: Escribir la descripción de un listado para tu app +intro: 'Para [Listar tu app](/marketplace/listing-on-github-marketplace/) en {% data variables.product.prodname_marketplace %}, necesitarás escribir una descripción de ésta y proporcionar imágenes que se apeguen a los lineamientos de GitHub.' +redirect_from: + - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ + - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ + - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing/ + - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing/ + - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images/ + - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images/ + - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/ + - /marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions +versions: + free-pro-team: '*' +--- + + + +Aquí te mostramos los lineamientos de los campos que necesitas llenar en la sección **Listar descripción** del borrador de tu listado. + +### Nomencltura y enlaces + +#### Nombre del listado + +El nombre de tu app se mostrará en la [página de inicio de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). El nombre se limita a 255 caracteres. + +#### Descripción muy corta + +La comunidad verá la descripción "muy corta" debajo del nombre de tu app en la [página principal de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). + +![Descripción corta de la app en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png) + +##### Longitud + +Te remcomendamos mantener un largo de 40 a 80 caracteres para las descripciones cortas. Aunque se te permite utilizar más caracteres, las descripciones concisas son más fáciles de leer y más rápidas de entender para los clientes. + +##### Contenido + +- Describe la funcionalidad de la app. No utilices este espaccio para un llamado a la acción. Por ejemplo: + + **RECOMENDADO:** Una administración de proyectos ligera para los informes de problemas de GitHub + + **NO RECOMENDADO:** Administración de proyectos e informes de problemas en GitHub + + **Tip:** Pon los verbos en tercera persona del singular en las llamadas a la acción para convertirlas en una descripción aceptable: _Administra tus proyectos e informes de problemas en GitHub_ + +- No repitas el nombre de la app en la descripción. + + **RECOMENDADO:** Una herramienta de integración contínua nativa para el contenedor + + **NO RECOMENDADO:** Skycap es una herramienta de integración contínua nativa para el contenedor + +##### Formato + +- Apégate siempre al uso de mayúsculas correcto en las oraciones. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. + +- No uses puntuación al final de tu descripción corta. Las descripciones cortas no deben incluir oraciones completas, y en definitiva, no deben incluir más de una oración. + +- Usa mayúscula inicial únicamente en nombres propios. Por ejemplo: + + **RECOMENDADO:** Automatización de entrega en un solo click para desarrolladores web + + **NO RECOMENDADO:** Automatización de entrega en un solo click para Desarrolladores Web + +- Utiliza siempre una [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. + +- Evita referirte a la comunidad de GitHub como "usuarios". + + **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización + + **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización + +- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). Por ejemplo: + + **RECOMENDADO:** Tableros de tareas ágiles, estimados y reportes sin salir de GitHub + + **NO RECOMENDADO:** Tableros de tareas ágiles, estimados, y reportes sin dejar la IU de GitHub + +#### Categorías + +Las apps en {% data variables.product.prodname_marketplace %} se pueden mostrar por categoría. Selecciona la categoría que describa mejor la funcionalidad principal de tu app en el menú desplegable de **Categoría principal** y, opcionalmente, selecciona una **Categoría secundaria** si es que describe mejor a tu app. + +#### Lenguajes compatibles + +Si tu app funciona únicamente con lenguajes específicos, selecciona hasta 10 lenguajes de programación que sean compatibles con ella. Estos lenguajes se muestran en la página del listado de {% data variables.product.prodname_marketplace %} de tu app. Este campo es opcional. + +#### Listar las URL + +**URL Requeridas** +* **URL de servicio al cliente:** La URL de una página web a la que llegarán tus clientes cuando tienen preguntas de la cuenta, producto o soporte técnico. +* **URL de la política de privacidad:** La página web que muestra la política de privacidad de tu app. +* **URL de la instalación:** Este campo se muestra únicamente para las apps de OAuth. (Las GitHub Apps no utilizan esta URL porque utilizan la URL de configuración opcional de la página de su página de configuración). Cuando un cliente compra tu App de OAuth, GitHub redireccionará a los clientes a la URL de la instalación después de que la instalen. Necesitarás redirigir a los clientes a `https://github.com/login/oauth/authorize` para comenzar el flujo de autorizaciones de OAuth. Consulta la sección "[Compras nuevas de Apps de OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para recibir más detalles al respecto. Omite este campo si estás listando una GitHub App. + +**URL opcionales** +* **URL de la empresa:** Un enlace al sitio web de tu empresa. +* **URL de estado:** Un enlace a la página web que muestra el estado de tu app. Las páginas de estado incluyen reportes de incidentes actuales y en forma de historial, el estado de tiempo activo de la aplicación web, y los periodos programados de mantenimiento. +* **URL de Documentación:** Un enlace a la documentación que muestra a los clientes cómo utilizar tu app. + +### Logo y tarjeta de características + +{% data variables.product.prodname_marketplace %} muestra todos los listados con un logo de imagen cuadrada dentro de una insignia circular para distinguir a las apps visualmente. + +![Imágenes de logo e insignia en GitHub marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png) + +Una tarjeta de características consiste en el logo, nombre e imagen personalizada de fondo para tu app, la cual captura la personalidad de ésta. {% data variables.product.prodname_marketplace %} muestra esta tarjeta si tu app es una de las cuatro apps que se presentan aleatoriamente en la parte superior de la [página principal](https://github.com/marketplace). Cada descripción muy corta de las apps se muestra debajo de su tarjeta de características. + +![Tarjeta de características](/assets/images/marketplace/marketplace_feature_card.png) + +En medidad que subas imágenes y selecciones los colores, tu borrador de listado de {% data variables.product.prodname_marketplace %} mostrará una vista previa de tu logo y de tu tarjeta de características. + +##### Lineamientos para los logos + +Debes cargar una imagen personalizada para el logo. Para el caso de la insignia, elige un color de fondo. + +- Carga una imagen de logo que tenga por lo menos 200 pixeles por 200 pixeles para que éste no tenga que escalarse ascendentemente cuando se publique tu listado. +- Los logos se cortarán en forma de cuadrado. Te recomendamos cargar un archivo de imagen cuadrado con tu logo en el centro. +- Para obtener los mejores resultados, carga una imagen de logo con un fondo transparente. +- Para darle la apariencia contínua a la insignia, elige un color de fondo que empate con el color (o con la transparencia) de tu imagen de logo. +- Evita utilizar las imágenes de logo que tienen texto o palabras. Los logos con texto no se escalan bien en pantallas pequeñas. + +##### Lineamientos para las tarjetas de características + +Debes cargar una imagen personalizada de fondo para la tarjeta de características. Elige el color del texto para el nombre de la app. + +- Utiliza un patrón o textura en la imagen de fondo para dar a tu tarjeta una identidad visual específica y ayudar a que resalten contra el fondo oscuro de la página de inicio de {% data variables.product.prodname_marketplace %}. Las tarjetas de caracetrísticas capturan la personalidad de la marca de tu app. +- La imagen de fondo mide 065 pixeles x 482 pixeles (ancho x alto). +- Elige un color de texto para el nombre de tu app, el cual se muestre claramente sobre la imagen de fondo. + +### Detalles del listado + +Para obtener la página de llegada de tu app, da clic en su nombre desde la página principal de {% data variables.product.prodname_marketplace %} o desde su página de categoría. La página de llegada muestra una descripción más larga de tu app, la cual incluye dos partes: una "Descripción de introducción" y una "Descripción detallada". + +Tu "Descripción de introducción" se muestra en la parte superior de la página de llegada de {% data variables.product.prodname_marketplace %} para tu app. + +![Descripción de introducción en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png) + +El dar clic en **Leer más...** mostrará la "Descripción detallada". + +![Descripción detallada en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png) + +Sigue estos lineamientos para escribir estas descripciones. + +#### Longitud + +Te recomendamos escribir un resumen de alto nivel que se componga de una o dos oraciones de entre 150 y 250 caracteres en el campo "Descripción de introducción" cuando [listes tu aplicación](/marketplace/listing-on-github-marketplace/). Aunque se te permite utilizar más caracteres, los resúmenes concisos son más fáciles de leer y más rápidas de entender para los clientes. + +Puedes agregar más información en el campo opcional "Descripción detallada". Encuentras esta descripción al dar clic en **Leer más...** debajo de la descripción de introducción en la página de llegada de tu app. Una descripción detallada consiste en 3-5 [propuestas de valor](https://en.wikipedia.org/wiki/Value_proposition) con 1-2 oraciones que se describen una a la otra. Puedes utilizar hasta 1,000 caracteres para esta descripción. + +#### Contenido + +- Inicia siempre con el nombre de tu aplicación en las descripciones de introducción. + +- Escribe siempre las descripciones y propuestas de valor utilizando la voz activa. + +#### Formato + +- Utiliza siempre las mayúsculas adecuadamente en las oraciones de los títulos para las propuestas de valor. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. + +- Utiliza puntos en tus descripciones. Evita los signos de admiración. + +- No utilices signos de puntuación al final de tus títulos para las propuestas de valor. Los títulos de propuestas de valor no deben incluir oraciones completas ni más de una oración. + +- Para cada propuesta de valor, incluye un título seguido de un párrafo de descripción. Da formato al título como un [encabezado nivel tres](/articles/basic-writing-and-formatting-syntax/#headings) utilizando lenguaje de marcado (Markdown). Por ejemplo: + + + ### Adquiere las habilidades que necesitas + + GitHub Learning Lab te puede ayudar a aprender cómo utilizar GitHub, a comunicarte de forma más efectiva con el lenguaje de Markdown, a gestionar conflictos de fusión, y más. + +- Usa mayúscula inicial únicamente en nombres propios. + +- Utiliza siempre la [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. + +- Evita referirte a la comunidad de GitHub como "usuarios". + + **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización + + **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización + +- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). + +### Impresiones de pantalla de los productos + +Puedes cargar hasta cinco impresiones de pantalla para tu app para que se muestren en su página de llegada. Agrega una captura opcional a cada impresión de pantalla para proporcionar contexto. Después de cargar tus impresiones de pantalla, puedes arrastrarlas para que tomen el órden en el que quieras que se muestren dentro de la página de llegada. + +#### Lineamientos para las impresiones de pantalla + +- Las imágenes deben tener resolución alta (por lo menos 1200px de ancho). +- Todas las imágenes deben tener la misma altura y ancho (proporción de aspecto) para evitar los saltos de página cuando las personas den clic de una imagen a otra. +- Muestra tanto de la interface de usuario como sea posible para que las personas pueden ver lo que hace tu app. +- Cuando tomes una impresión de pantalla de tu app en un buscador, incluye solamente el contenido en la ventana a mostrar. Evita incluir la barra de dirección, la barra de título o los iconos de la barra de herramientas, ya que estos no se escalan bien cuando se miran desde pantallas más pequeñas. +- GitHub muestra las impresiones de pantalla que cargues en una caja dentro de la página de llegada de tu app, así que no necesitas agregar cajas o márgenes al rededor de tus impresiones de pantalla. +- Las capturas son más efectivas cuando son cortas y concisas. + +![Imagen de impresión de pantalla en GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/es-ES/content/developers/index.md b/translations/es-ES/content/developers/index.md new file mode 100644 index 0000000000000..9a6350fcafcca --- /dev/null +++ b/translations/es-ES/content/developers/index.md @@ -0,0 +1,13 @@ +--- +title: Desarrolladores +intro: 'Saca más provecho de {% data variables.product.prodname_dotcom %} integrándote con nuestras API, personalizando tu flujo de trabajo de {% data variables.product.prodname_dotcom %}, y creando y compartiendo apps con la comunidad.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_with_intro /overview %} +{% link_with_intro /webhooks-and-events %} +{% link_with_intro /apps %} +{% link_with_intro /github-marketplace %} diff --git a/translations/es-ES/content/developers/overview/about-githubs-apis.md b/translations/es-ES/content/developers/overview/about-githubs-apis.md new file mode 100644 index 0000000000000..bff77a813323d --- /dev/null +++ b/translations/es-ES/content/developers/overview/about-githubs-apis.md @@ -0,0 +1,26 @@ +--- +title: Acerca de las API de GitHub +intro: 'Aprende sobre las API de {% data variables.product.prodname_dotcom %} para extender y personalizar tu experiencia en {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v3/versions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Hay dos versiones estables de la API de GitHub: la [API de REST](/rest) y la [API de GraphQL](/graphql). Cuando utilizas la API de REST, te exhortamos a que [solicites la v3 a través del encabezado de `Accept`](/v3/media/#request-specific-version). Para obtener más información sobre cómo utilizar la API de GraphQL, consulta los [documentos de la v4](/graphql). + +## Versiones obsoletas + +### beta + +Se hizo obsoleta la API beta el 22 de abril de 2014. + +### v2 + +Eliminamos el soporte para la API v2 en el 12 de junio de 2012. + +### v1 + +Eliminamos el soporte para la API v1 en el 12 de junio de 2012. diff --git a/translations/es-ES/content/developers/overview/github-developer-program.md b/translations/es-ES/content/developers/overview/github-developer-program.md new file mode 100644 index 0000000000000..944949906f4de --- /dev/null +++ b/translations/es-ES/content/developers/overview/github-developer-program.md @@ -0,0 +1,37 @@ +--- +title: Programa de Desarrollador de GitHub +intro: 'Si creas herramientas que se integren con {% data variables.product.prodname_dotcom %}, puedes unirte al Programa de Desarrollador de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /program +versions: + free-pro-team: '*' +--- + +¿Estás creando una aplicación que se integra con GitHub? ¡Regístrate para nuestro Programa de Desarrollador! Las posibilidades son infinitas, y disfrutarás del reconocimiento de la comunidad. [Regístrate ahora](https://github.com/developer/register) + +## Permanece informado + +Sé el primero en saber acerca de los cambios a la API y prueba características nuevas antes de que se lanzen en el [Blod del desarrollador](https://developer.github.com/changes/). + +## Quítate la tentación + +Crea tus propias herramientas que se integren de manera continua con el lugar en donde cargas código todos los días. + +## Házte cargo de la empresa + +[Obtén licencias de desarrollador](http://github.com/contact?form%5Bsubject%5D=Development+licenses) para crear y probar tu aplicación contra {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_ghe_managed %}. + + +## ¿Tienes una integración que opera con GitHub? + +¡Genial! Nos gustaría que fueras parte del programa. Aquí te mostramos como puedes correr la voz:

    +* [Infórmanos sobre tu integración](https://github.com/contact?form[subject]=New+GitHub+Integration) +* Utiliza el [Logo de Octocat o de GitHub](https://github.com/logos) para denotar que tu producto se integra con GitHub +* Publica un video o un blog en tu sitio web que explique esta integración + +## ¿Estás listo para unirte al Programa de Desarrollador de GitHub? + +La membrecía está disponible para los desarrolladores individuales y para las comañías que tienen: + +* Una integración en producción o desarrollo que utilice la API de GitHub. +* Una dirección de correo electrónico en donde los usuarios de GitHub puedan contactarte para soporte. diff --git a/translations/es-ES/content/developers/overview/index.md b/translations/es-ES/content/developers/overview/index.md new file mode 100644 index 0000000000000..7d0f61d0e311d --- /dev/null +++ b/translations/es-ES/content/developers/overview/index.md @@ -0,0 +1,18 @@ +--- +title: Resumen +intro: 'Aprende sobre las API de {% data variables.product.prodname_dotcom %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} y asegura tus despliegues.{% else %}, asegura tus despliegues y únete al Programa de Desarrolladores de {% data variables.product.prodname_dotcom %}.{% endif %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Índice + +{% link_in_list /about-githubs-apis %} +{% link_in_list /managing-deploy-keys %} +{% link_in_list /viewing-deployment-history %} +{% link_in_list /using-ssh-agent-forwarding %} +{% link_in_list /secret-scanning %} +{% link_in_list /replacing-github-services %} +{% link_in_list /github-developer-program %} diff --git a/translations/es-ES/content/developers/overview/managing-deploy-keys.md b/translations/es-ES/content/developers/overview/managing-deploy-keys.md new file mode 100644 index 0000000000000..8391900e501d1 --- /dev/null +++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md @@ -0,0 +1,154 @@ +--- +title: Administrar las llaves de despliegue +intro: Aprende las diversas formas de administrar llaves SSH en tus servidores cuando automatizas los scripts de desplegue y averigua qué es lo mejor para ti. +redirect_from: + - /guides/managing-deploy-keys/ + - /v3/guides/managing-deploy-keys +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Puedes administrar llaves SSH en tus servidores cuando automatices tus scripts de despliegue utilizando el reenvío del agente de SSH, HTTPS con tokens de OAuth, o usuarios máquina. + +### Reenvío del agente SSH + +En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente SSH es el método más fácil y rápido a utilizar. El reenvío de agentes utiliza las mismas llaves SSH que utiliza tu ordenador de desarrollo local. + +##### Pros + +* No tienes que generar o llevar registros de las llaves nuevas. +* No hay administración de llaves; los usuarios tienen los mismos permisos en el servidor y localmente. +* No se almacenan las llaves en el servidor, así que, en caso de que el servidor se ponga en riesgo, no necesitas buscar y eliminar las llaves con este problema. + +##### Contras + +* Los usuarios **deben** ingresar cno SSH para hacer los despliegues; no pueden utilizarse los procesos de despliegue automatizados. +* El reenvío del agente SSH puede ser difícil de ejecutar para usuarios de Windows. + +##### Configuración + +1. Habilita el reenvío de agente localmente. Consulta [nuestra guía sobre el redireccionamiento del agente SSH][ssh-agent-forwarding] para obtener más información. +2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, el habilitar el reenvío de agentes en un script de bash se vería más o menos así: `ssh -A serverA 'bash -s' < deploy.sh` + +### Clonado de HTTPS con tokens de OAuth + +Si no quieres utilizar llaves SSH, puedes utilizar [HTTPS con tokens de OAuth][git-automation]. + +##### Pros + +* Cualquiera que tenga acceso al servidor puede desplegar el repositorio. +* Los usuarios no tienen que cambiar su configuración local de SSH. +* No se necesitan tokens múltiples (uno por usuario); un token por servidor es suficiente. +* Los tokens se pueden revocar en cualquier momento, convirtiéndolos esencialmente en una contraseña de un solo uso. +{% if enterpriseServerVersions contains currentVersion %} +* Se puede generar nuevos tokens con scripts si se utiliza [la API de OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization). +{% endif %} + +##### Contras + +* Debes asegurarte de que configuras tu token con los alcances de acceso correctos. +* Los tokens son prácticamente contraseñas, y deben protegerse de la misma manera. + +##### Configuración + +Consulta [nuestra guía sobre la automatización de tokens en Git][git-automation]. + +### Llaves de implementación + +{% data reusables.repositories.deploy-keys %} + +{% data reusables.repositories.deploy-keys-write-access %} + +##### Pros + +* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto. +* Los usuarios no tienen que cambiar su configuración local de SSH. +* Las llaves de despliegue son de solo lectura predeterminadamente, pero les puedes otorgar acceso de escritura cuando las agregas a un repositorio. + +##### Contras + +* Las llaves de despliegue solo otorgan acceso a un solo repositorio. Los proyectos más complejos pueden tener muchos repositorios que extraer del mismo servidor. +* Las llaves de lanzamiento habitualmente no están protegidas con una frase de acceso, lo cual hace que se pueda acceder fácilmente a ellas si el servidor estuvo en riesgo. + +##### Configuración + +1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor, y recuerda en donde guardaste el par de llaves pública/privada de rsa. +2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego da clic en **Tu perfil**. ![Navegación al perfil](/assets/images/profile-page.png) +3. En tu página de perfil, da clic en **Repositorios** y luego en el nombre de tu repositorio. ![Enlace de los repositorios](/assets/images/repos.png) +4. Desde tu repositorio, da clic en **Configuración**. ![Configuración del repositorio](/assets/images/repo-settings.png) +5. En la barra lateral, da clic en **Desplegar llaves** y luego en **Agregar llave de despliegue**. ![Enlace para agregar llaves de despliegue](/assets/images/add-deploy-key.png) +6. Proporciona un título, pégalo en tu llave pública. ![Página de la llave de despliegue](/assets/images/deploy-key.png) +7. Selecciona **Permitir acceso de escritura** si quieres que esta llave tenga acceso de escritura en el repositorio. Una llave de despliegue con acceso de escritura permite que un despliegue cargue información al repositorio. +8. Da clic en **Agregar llave**. + +##### Utilizar repositorios múltiples en un servidor + +Si utilizas repositorios múltiples en un servidor, necesitarás generar un par de llaves dedicados para cada uno. No puedes reutilizar una llave de despliegue para repositorios múltiples. + +En el archivo de configuración SSH del servidor (habitualmente `~/.ssh/config`), agrega una entrada de alias para cada repositorio. Por ejemplo: + +```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` - El alias del repositorio. +* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configura el nombre de host para utilizarlo con el alias. +* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Asigna una llave privada al alias. + +Entonces podrás utilizar el alias del nombre de host para que interactúe con el repositorio utilizando SSH, lo cual utilizará la llave de despliegue única que se asignó a dicho alias. Por ejemplo: + +```bash +$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git +``` + +### Usuarios máquina + +Si tu servidor necesita acceder a repositorios múltiples, puedes crear una nueva cuenta de {% data variables.product.product_name %} y adjuntar una llave SSH que se utilizará exclusivamente para fines de automatización. Ya que ninguna persona utilizará esta cuenta de {% data variables.product.product_name %}, se le llama _usuario máquina_. Puedes agregar el usuario máquina como [colaborador][collaborator] en un repositorio personal (otorgándole acceso de lectura y escritura), como un [colaborador externo][outside-collaborator] en el repositorio de una organización (otorgándole acceso de lectura, escritura y administrador), o a un [equipo][team] con acceso a los repositorios que necesite para la automatización (otorgándole los permisos del equipo). + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Tip:** En nuestras [condiciones de servicio][tos] se declara que: + +> *No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados.* + +Esto significa que no puedes automatizar la creación de las cuentas. Pero si quieres crear un solo usuario máquina para automatizar las tareas como el despliegue de scripts en tu proyecto u organización, eso está perfecto. + +{% endtip %} + +{% endif %} + +##### Pros + +* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto. +* No se necesitan usuarios (humanos) para cambiar su configuración local de SSH. +* No se necesitan llaves múltiples; una por servidor está bien. + +##### Contras + +* Únicamente las organizaciones pueden restringir a los usuarios máquina para que tengan acceso de solo lectura. Los repositorios personales siempre otorgan a los colaboradores acceso de lectura/escritura. +* Las llaves de los usuarios máquina, tal como las llaves de despliegue, a menudo no se encuentran protegidas con una frase de acceso. + +##### Configuración + +1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor y adjunta la llave pública a la cuenta del usuario máquina. +2. Otorga a la cuenta del usuario máquina el acceso a los repositorios que quieras automatizar. Puedes hacer esto si agregas la cuenta como un [colaborador][collaborator], como un [colaborador externo][outside-collaborator], o a un [equipo][team] en una organización. + +[ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/ +[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key +[tos]: /articles/github-terms-of-service/ +[git-automation]: /articles/git-automation-with-oauth-tokens +[git-automation]: /articles/git-automation-with-oauth-tokens +[collaborator]: /articles/inviting-collaborators-to-a-personal-repository +[outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization +[team]: /articles/adding-organization-members-to-a-team diff --git a/translations/es-ES/content/developers/overview/replacing-github-services.md b/translations/es-ES/content/developers/overview/replacing-github-services.md new file mode 100644 index 0000000000000..31129402485c9 --- /dev/null +++ b/translations/es-ES/content/developers/overview/replacing-github-services.md @@ -0,0 +1,71 @@ +--- +title: Reemplazar los GitHub Services +intro: 'Si aún estás dependiendo de los {% data variables.product.prodname_dotcom %} Services obsoletizados, aprende cómomigrar los ganchos de tu servicio a webhooks.' +redirect_from: + - /guides/replacing-github-services/ + - /v3/guides/automating-deployments-to-integrators/ + - /v3/guides/replacing-github-services +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + + +Hemos obsoletizado los GitHub Services para favorecer la integración con los webhooks. Esta guía te ayuda a hacer la transición hacia los webhooks de GitHub Services. Para obtener más información acerca de este anuncio, consulta la [Publicación del blog](https://developer.github.com/changes/2018-10-01-denying-new-github-services). + +{% note %} + +Como una alternativa al servicio de correo electrónico, ahora puedes comenzar a utilizar las notificaciones para las cargas de información a tu repositorio. Consulta la sección "[Acerca de las notificaciones de correo electrónico para las cargas a tu repositorio](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" para aprender cómo configurar las notificaciones por correo electrónico de las confirmaciones. + +{% endnote %} + +### Línea del tiempo de la obsoletización + +- **1 de octubre de 2018**: GitHub descontinuó el permitir que los usuarios instalen servicios. Eliminamos los GitHub Services de la interface de usuario de GitHub.com. +- **29 de enero de 2019**: Como alternativa al servicio de correo electrónico, ahora puedes comenzar a utilizar las notificaciones por correo electrónico para las cargas a tu repositorio. Consulta la sección "[Acerca de las notificaciones de correo electrónico para las cargas a tu repositorio](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" para aprender cómo configurar las notificaciones por correo electrónico de las confirmaciones. +- **31 de enero de 2019**: GitHub dejará de entregar los eventos de los servicios instalados en GitHub.com. + +### Antecedentes de GitHub Services + +GitHub Services (a veces conocido como Ganchos de Servicio) es el método tradicional de integración en donde GitHub hospedó una porción de los servicios de nuestros integradores a través [del repositorio`github-services`](https://github.com/github/github-services). Las acciones que se realizan en GitHub activan estos servicios, y puedes utilizarlos a su vez para activar acciones fuera de GitHub. + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +### Encontrar los repositorios que utilizan GitHub Services +Proporcionamos un script de línea de comandos que te ayuda a identificar los repositorios de tu aplicativo que utilizan GitHub Services. Para obtener más información, consulta [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %} + +### GitHub Services vs webhooks + +Las diferencias clave entre GitHub Services y los webhooks son: +- **Configuración**: Los GitHub Services tienen opciones de configuración específicas para los servicioes, mientras que los webhooks se configuran simplemente especificando una URL y un conjunto de eventos. +- **Lógica personalizada**: Los GitHub Services pueden tener una lógica personalizada para responder con acciones múltiples como parte de procesar solo un evento, mientras que los webhooks no tienen lógica personalizada. +- **Tipos de solicitudes**: Los GitHub Services pueden hacer solicitudes tanto de HTTP como no-HTTP, mientras que los webhooks solo hacen solicitudes HTTP. + +### Reemplazar los Servicios con webhooks + +Para reemplazar los GitHub Services con Webhooks: + +1. Identifica los eventos de webhook relevantes a los que necesitas suscribirte desde [esta lista](/webhooks/#events). + +2. Cambia tu configuración dependiendo de cómo utilizas los GitHub Services actualmente: + + - Para las **GitHub Apps**: Actualiza los permisos y eventos suscritos de tu app para configurarla para recibir los eventos de webhook reelevantes. + - Para las **Apps de OAuth**: Solicita ya sea el(los) alcance(s) `repo_hook` y/o `org_hook` para administrar los eventos relevantes a nombre de los usuarios. + - Para los **proveedores de GitHub Services**: solicita que los usuarios configuren manualmente un webhook con los eventos relevantes que se te envían, o aprovecha esta oportunidad para crear una app para administrar esta funcionalidad. Para obtener más información, consulta "[Acerca de las apps](/apps/about-apps/)." + +3. Migra las configuraciones adicionales desde fuera de GitHub. Algunos GitHub Services necesitan configuraciones personalizadas adicionales en la página de configuración dentro de GitHub. Si tu servicio hace esto, necesitarás migrar esta funcionalidad en tu aplicación o depender de GitHub o de las Apps de OAuth conforme esto aplique. + +### Compatibilidad con {% data variables.product.prodname_ghe_server %} + +- **{% data variables.product.prodname_ghe_server %} 2.17**: El {% data variables.product.prodname_ghe_server %} con lanzamiento 2.17 y superior descontinuará el permitir que los administradores instalen servicios. Los aministradores podrán seguir modificando los ganchos de servicio existentes y recibiendo ganchos en el {% data variables.product.prodname_ghe_server %} con lanzamiento 2.17 hasta el 2.19. Como una alternativa al servicio de correo electrónico, podrás utilizar las notificaciones de correo electrónico para las cargas de información a tu repositorio en el {% data variables.product.prodname_ghe_server %} 2.17 y superior. Consulta [esta publicación del blog](https://developer.github.com/changes/2019-01-29-life-after-github-services) para conocer más al respecto. +- **{% data variables.product.prodname_ghe_server %} 2.20**: El {% data variables.product.prodname_ghe_server %} con lanzamiento 2.20 y superior dejará de entregar cualquier evento de los servicios instalados. + +El lanzamiento 2.17 de {% data variables.product.prodname_ghe_server %} será el primer lanzamiento que no permite a los administradores instalar GitHub Services. Únicamente admitiremos los GitHub Services existentes hasta el lanzamiento 2.20 de {% data variables.product.prodname_ghe_server %}. También aceptaremos cualquier parche crítico para tu Github Service que se ejecute en el {% data variables.product.prodname_ghe_server %} hasta el 1 de octubre de 2019. + +### Migrarte con nuestra ayuda + +Por favor [contáctanos](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) si tienes cualquier pregunta. + +Como un resumen de alto nivel, el proceso de migración involucra habitualmente: + - Identificar cómo y dónde tu producto está utilizando los GitHub Services. + - Identificar los eventos de webhook correspondientes que necesites configurar para poder migrarlos a webhooks sencillos. + - Implementar el diseño utilizando ya sea [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/) o [{% data variables.product.prodname_github_app %}. Se prefieren las {% data variables.product.prodname_github_app %}](/apps/building-github-apps/). Para aprender más acerca del porqué se prefieren las {% data variables.product.prodname_github_app %}, consulta la sección "[Razones para cambiar a {% data variables.product.prodname_github_app %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)". diff --git a/translations/es-ES/content/developers/overview/secret-scanning.md b/translations/es-ES/content/developers/overview/secret-scanning.md new file mode 100644 index 0000000000000..3ab1485aec9bb --- /dev/null +++ b/translations/es-ES/content/developers/overview/secret-scanning.md @@ -0,0 +1,280 @@ +--- +title: Escaneo de secretos +intro: 'Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que se aseguren nuestros formatos de token secretos a través de un escaneo de secretos, el cual busca las confirmaciones accidentales de tus formatos secretos y puede enviarse a la terminal de verificación de un proveedor de servicios.' +redirect_from: + - /partnerships/token-scanning/ + - /partnerships/secret-scanning +versions: + free-pro-team: '*' +--- + + +{% data variables.product.prodname_dotcom %} escanea los repositorios en busca de formatos secretos para prevenir el uso fraudulento de las credenciales que se confirmaron por accidente. El escaneo de secretos ocurre predeterminadamente en los repositorios públicos, y se puede habilitar en los privados por parte de los administradores de dicho repositorio o de los propietarios de la organización. Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que tus formatos secretos se incluyan en nuestro escaneo de secretos. + +Cuando se encuentra una coincidencia de tu formato secreto en un repositorio público, se envía una carga útil a una terminal HTTP de tu elección. + +Cuando se encuentra una coincidencia de tu formato secreto en un repositorio privado configurado para el escaneo de secretos, entonces se les alerta a los administradores del repositorio y estos pueden ver y administrar los resultados del escaneo de secretos en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas del escaneo de secretos](/github/administering-a-repository/managing-alerts-from-secret-scanning)". + +{% note %} + +**Nota:** El escaneo de secretos para repositorios privados se encuentra actualmente en beta. + +{% endnote %} + +Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa de escaneo de secretos. + +### El proceso de escaneo de secretos + +##### Cómo funciona el escaneo de secretos en un repositorio público + +El siguiente diagrama resume el proceso de escaneo de secretos para los repositorios públicos y cualquier coincidencia se envía a una terminal de verificación de un proveedor de servicios. + +![Diagrama de flujo que muestra el proceso de escaneo para un secreto y el envío de coincidencias a una terminal de verificación del proveedor de servicios](/assets/images/secret-scanning-flow.png "Flujo de escaneo de secretos") + +### Unirse al programa de escaneo de secretos en {% data variables.product.prodname_dotcom %} + +1. Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso. +1. Identifica los secretos relevantes que quieres escanear y crea expresiones regulares para capturarlos. +1. Para las coincidencias de secretos que estén en repositorios públicos, crea un servicio de alerta de secretos que acepte webhooks de {% data variables.product.prodname_dotcom %} que contengan la carga útil del mensaje del escaneo de secretos. +1. Implementa la verificación de firmas en tu servicio de alerta secreto. +1. Implementa la revocación de secretos y las notificaciones al usuario en tu servicio de alerta de secretos. + +#### Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso + +Para iniciar con el proceso de inscripción, manda un mensaje de correo electrónico a secret-scanning@github.com. + +Recibirás los detalles del programa de escane de secretos, y necesitarás aceptar las condiciones de participación de {% data variables.product.prodname_dotcom %} antes de seguir con el proceso. + +#### Identifica tus secretos y crea expresiones regulares + +Para escanear en busca de tus secretos, {% data variables.product.prodname_dotcom %} necesita saber los siguientes detalles de cada secreto que quieras incluir en el programa de escaneo de secretos: + +* Un nombre único y legible para las personas para el tipo de secreto. Lo utilizaremos para generar el valor `Type` en la carga útil del mensaje más adelante. +* Una expresión regular que encuentre el tipo de secreto. Sé tan preciso como sea posible, ya que esto reducirá la cantidad de falsos positivos. +* La URL de la terminal que recibe mensajes de {% data variables.product.prodname_dotcom %}. Esto no tiene que ser único para cada tipo de secreto. + +Envía esta información a secret-scanning@github.com. + +#### Crea un servicio de alerta de secretos + +Crea una terminal HTTP pública y accesible desde la internet en la URL que nos proporcionaste. Cuando se encuentre una coincidencia de tu expresión regular en un repositorio público, {% data variables.product.prodname_dotcom %} enviará un mensaje HTTP de tipo `POST` a tu terminal. + +##### Ejemplo del POST que se envía a tu terminal + +``` +POST / HTTP/1.1 +Host: HOST +Accept: */* +Content-Type: application/json +GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a +GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek= +Content-Length: 0123 + +[ + { + "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a", + "type": "ACompany_API_token", + "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123" + } +] +``` + +El cuerpo del mensaje es una matriz de JSON que contiene uno o más objetos con el siguiente contenido. Cuando se encuentran coincidencias múltiples, {% data variables.product.prodname_dotcom %} podría enviar un solo mensaje con más de una coincidencia del secreto. Tu terminal deberá poder gestionar las solicitudes con una gran cantidad de coincidencias sin exceder el tiempo. + +* **Token**: El valor de la coincidencia del secreto. +* **Tipo**: El nombre único que proporcionaste para identificar tu expresión regular. +* **URL**: La URL de la confirmación pública en donde se encontró la coincidencia. + +#### Implementa la verificación de firmas en tu servicio de alerta de secretos + +Te recomendamos que implementes la validación de firmas en tu servicio de alerta de secretos para garantizar que los mensajes que recibes son auténticamente de {% data variables.product.prodname_dotcom %} y no son malintencionados. + +Puedes recuperar la llave pública del escaneo de secretos de {% data variables.product.prodname_dotcom %} desde https://api.github.com/meta/public_keys/secret_scanning y validar el mensaje utilizando el algoritmo `ECDSA-NIST-P256V1-SHA256`. + +Asumiendo que recibes el siguiente mensaje, los extractos de código que presentamos a continuación demuestran cómo pudiste realizar la validación de firmas. El código también asume que configuraste una variable de ambiente llamada `GITHUB_PRODUCTION_TOKEN` con un PAT generado (https://github.com/settings/tokens). El token no necesita que se configure ningún permiso. + +**Mensaje de ejemplo que se envía a tu terminal de verificación** +``` +POST / HTTP/1.1 +Host: HOST +Accept: */* +content-type: application/json +GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a +GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc= +Content-Length: 0000 + +[{"token": "some_token", "type": "some_type", "url": "some_url"}] +``` + +**Ejemplo de validación en Go** +```golang +package main + +import ( + "crypto/ecdsa" + "crypto/sha256" + "crypto/x509" + "encoding/asn1" + "encoding/base64" + "encoding/json" + "encoding/pem" + "errors" + "fmt" + "math/big" + "net/http" + "os" +) + +func main() { + payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]` + + kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a" + + kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=" + + // Fetch the list of GitHub Public Keys + req, err := http. NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil) + if err != nil { + fmt. Printf("Error preparing request: %s\n", err) + os. Exit(1) + } + + if len(os.Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 { + fmt. Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN") + os. Exit(1) + } + + req. Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN")) + + resp, err := http. DefaultClient.Do(req) + if err != nil { + fmt. Printf("Error requesting GitHub signing keys: %s\n", err) + os. Exit(2) + } + + decoder := json. NewDecoder(resp.Body) + var keys GitHubSigningKeys + if err := decoder. Decode(&keys); err != nil { + fmt. Printf("Error decoding GitHub signing key request: %s\n", err) + os. Exit(3) + } + + // Find the Key used to sign our webhook + pubKey, err := func() (string, error) { + for _, v := range keys. PublicKeys { + if v. KeyIdentifier == kID { + return v. Key, nil + + } + } + return "", errors. New("specified key was not found in GitHub key list") + }() + + if err != nil { + fmt. Printf("Error finding GitHub signing key: %s\n", err) + os. Exit(4) + } + + // Decode the Public Key + block, _ := pem.Decode([]byte(pubKey)) + if block == nil { + fmt. Println("Error parsing PEM block with GitHub public key") + os. Exit(5) + } + + // Create our ECDSA Public Key + key, err := x509.ParsePKIXPublicKey(block.Bytes) + if err != nil { + fmt. Printf("Error parsing DER encoded public key: %s\n", err) + os. Exit(6) + } + + // Because of documentation, we know it's a *ecdsa.PublicKey + ecdsaKey, ok := key.(*ecdsa.PublicKey) + if !ok { + fmt. + Exit(7) + } + + // Parse the Webhook Signature + parsedSig := asn1Signature{} + asnSig, err := base64.StdEncoding.DecodeString(kSig) + if err != nil { + fmt. Printf("unable to base64 decode signature: %s\n", err) + os. Exit(8) + } + rest, err := asn1.Unmarshal(asnSig, &parsedSig) + if err != nil || len(rest) != 0 { + fmt. Printf("Error unmarshalling asn.1 signature: %s\n", err) + os. Exit(9) + } + + // Verify the SHA256 encoded payload against the signature with GitHub's Key + digest := sha256.Sum256([]byte(payload)) + keyOk := ecdsa. Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S) + + if keyOk { + fmt. + Println("the payload is invalid :(") + os. Exit(10) + } +} + +type GitHubSigningKeys struct { + PublicKeys []struct { + KeyIdentifier string `json:"key_identifier"` + Key string `json:"key"` + IsCurrent bool `json:"is_current"` + } `json:"public_keys"` +} + +// asn1Signature is a struct for ASN.1 serializing/parsing signatures. +type asn1Signature struct { + R *big.Int + S *big.Int +} +``` + +**Ejemplo de validación en Ruby** +```ruby +require 'openssl' +require 'net/http' +require 'uri' +require 'json' +require 'base64' + +payload = <<-EOL +[{"token": "some_token", "type": "some_type", "url": "some_url"}] +EOL + +payload = payload + +signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=" + +key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a" + +url = URI.parse('https://api.github.com/meta/public_keys/token_scanning') + +raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN'] +request = Net::HTTP::Get.new(url.path) +request['Authorization'] = "Bearer #{ENV['GITHUB_PRODUCTION_TOKEN']}" + +http = Net::HTTP.new(url.host, url.port) +http.use_ssl = (url.scheme == "https") + +response = http.request(request) + +parsed_response = JSON.parse(response.body) + +current_key_object = parsed_response["public_keys"].find { |key| key["key_identifier"] == key_id } + +current_key = current_key_object["key"] + +openssl_key = OpenSSL::PKey::EC.new(current_key) + +puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp) +``` + +#### Implementa la revocación de secretos y la notificación a usuarios en tu servicio de alerta de secretos + +Para escanear secretos en los repositorios públicos, puedes ampliar tu servicio de alerta de secretos para revocar los secretos expuestos y notificar a los usuarios afectados. Depende de ti el cómo implementas esto en tu servicio de alerta de secretos, pero te recomendamos considerar cualquier secreto del cual {% data variables.product.prodname_dotcom %} te envíe mensajes de que es público y está puesto en riesgo. diff --git a/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md b/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md new file mode 100644 index 0000000000000..2a0efaa9dcc3d --- /dev/null +++ b/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md @@ -0,0 +1,161 @@ +--- +title: Utilizar el reenvío del agente SSH +intro: 'Para simplificar los despliegues en un servidor, puedes configurar el reenvío del agente SSH para utilizar las llaves SSH locales de forma segura.' +redirect_from: + - /guides/using-ssh-agent-forwarding/ + - /v3/guides/using-ssh-agent-forwarding +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +El reenvío del agente de SSH puede utilizarse para hacer despliegues a un servidor simple. Te permite utilizar llaves SSH locales en vez de dejar las llaves (¡sin frases de acceso!) en tu servidor. + +Si ya configuraste una llave SSH para que interactúe con {% data variables.product.product_name %}, probablemente estás familiarizado con el `ssh-agent`. Es un programa que se ejecuta en segundo plano y que mantiene tu llave cargada en la memoria para que no tengas que ingresar tu frase deacceso cada que quieres utilizar esta llave. Lo ingenioso de esto es que puedes elegir dejar que los servidores accedan a tu `ssh-agent` local como si ya se estuvieran ejecutando en el servidor. Esto es como pedirle a un amigo que ingrese su contraseña para que puedas utilizar su computadora. + +Revisa la sección [Guía de Tips Técnicos de Steve Friedl][tech-tips] para obtener una explicación más exacta del reenvío del agente SSH. + +### Configurar el reenvío del agente SSH + +Asegúrate de que tu propia llave SSH está configurada y funciona. Puedes utilizar [nuestra guía para generar llaves SSH][generating-keys] si aún no lo has hecho. + +Puedes probar si tu llave local funciona ingresando `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` en la terminal: + +```shell +$ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} +# Attempt to SSH in to github +> Hi username! You've successfully authenticated, but GitHub does not provide +> shell access. +``` + +Estamos empezando muy bien. Vamso a configurar SSH para permitir el reenvío del agente en tu servidor. + +1. Utilizando tu editor de texto preferido, abre el archivo en `~/.ssh/config`. Si este archivo no existe, puedes crearlo si ingresas `touch ~/.ssh/config` en la terminal. + +2. Ingresa el siguiente texto en el archivo, reemplazando `example.com` con el nombre de dominio o la IP de tu servidor: + + Host example.com + ForwardAgent yes + +{% warning %} + +**Advertencia:** Podrías estar tentado a utilizar un comodín como `Host *` para aplicar esta configuración únicamente a todas las conexiones SSH. No es realmente una buena idea, ya que compartirías tus llaves SSH locales con *todos* los servidores en los que ingreses con SSH. No tendrán acceso directo a las llaves, pero podrán utilizarlas *como si fueran tú* mientras que se establece la conexión. **Deberías agregar únicamente los servidores en los que confías y que pretendes usar con el reenvío del agente.** + +{% endwarning %} + +### Probar el reenvío del agente SSH + +Para probar que el reenvío de agentes funcione con tu servidor, puedes ingresar por SSH en éste y ejecutar `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` nuevamente. Si todo sale bien, te regresará el mismo mensaje que salió cuando lo hiciste localmente. + +Si no estás seguro de que se esté utilizando tu llave local, también puedes inspeccionar la variable `SSH_AUTH_SOCK` en tu servidor: + +```shell +$ echo "$SSH_AUTH_SOCK" +# Print out the SSH_AUTH_SOCK variable +> /tmp/ssh-4hNGMk8AZX/agent.79453 +``` + +Si no se ha configurado la variable, esto significa que el reenvío del agente no funciona: + +```shell +$ echo "$SSH_AUTH_SOCK" +# Print out the SSH_AUTH_SOCK variable +> [No output] +$ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} +# Try to SSH to github +> Permission denied (publickey). +``` + +### Solucionar problemas del reenvío del agente SSH + +Aquí te mostramos algunos puntos en los cuales tener cuidado cuando intentes solucionar problemas relacionados con el reenvío del agente SSH. + +#### Debes utilizar una URL con SSH para revisar el código + +El reenvío SSH funciona únicamente con URL con SSH, no con aquellas de HTTP(s). Revisa el archivo *.git/config* en tu servidor y asegúrate de que la URL es de estilo SSH como se muestra a continuación: + +```shell +[remote "origin"] + url = git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}:yourAccount/yourProject.git + fetch = +refs/heads/*:refs/remotes/origin/* +``` + +#### Tus llaves SSH deben funcionar localmente + +Antes de que hagas que tus llaves funcionen a través del reenvío del agente, primero deben funcionar localmente. [Nuestra guía para generar llaves SSH][generating-keys] puede ayudarte a configurar tus llaves SSH localmente. + +#### Tu sistema debe permitir el reenvío del agente SSH + +Algunas veces, la configuración del sistema deja de permitir el reenvío del agente SSH. Puedes verificar si se está utilizando un archivo de configuración del sistema ingresando el siguiente comando en la terminal: + +```shell +$ ssh -v example.com +# Connect to example.com with verbose debug output +> OpenSSH_8.1p1, LibreSSL 2.7.3 +> debug1: Reading configuration data /Users/you/.ssh/config +> debug1: Applying options for example.com +> debug1: Reading configuration data /etc/ssh_config +> debug1: Applying options for * +$ exit +# Returns to your local command prompt +``` + +En este ejemplo, el archivo *~/.ssh/config* se carga primero, luego se lee el */etc/ssh_config*. Podemos inspeccionar ese archivo para ver si está anulando nuestras opciones si ejecutamos los siguientes comandos: + +```shell +$ cat /etc/ssh_config +# Print out the /etc/ssh_config file +> Host * +> SendEnv LANG LC_* +> ForwardAgent no +``` + +En este ejemplo, nuestro archivo */etc/ssh_config* dice específicamente `ForwardAgent no`, lo cual es una manera de bloquear el reenvío del agente. Si borramos esta línea del archivo deberíamos poder hacer funcionar el reenvío del agente nuevamente. + +#### Tu servidor debe permitir el reenvío del agente SSH en las conexiones entrantes + +El reenvío del agente también puede bloquearse en tu servidor. Puedes verificar que se permita este reenvío si entras al servidor mediante SSH y ejecutas `sshd_config`. La salida de este comando deberá indicar que se configuró `AllowAgentForwarding`. + +#### Tu `ssh-agent` local debe estar ejecutándose + +En la mayoría de las computadoras, el sistema operativo lanza el `ssh-agent` automáticamente. Sin embargo, en Windows, tienes que hacerlo manualmente. Tenemos [una guía de cómo empezar con el `ssh-agent` cuando abres Git Bash][autolaunch-ssh-agent]. + +Para verificar que el `ssh-agent` se está ejecutando en tu computadora, teclea el siguiente comando en la terminal: + +```shell +$ echo "$SSH_AUTH_SOCK" +# Print out the SSH_AUTH_SOCK variable +> /tmp/launch-kNSlgU/Listeners +``` + +#### Tu llave debe estar disponible para el `ssh-agent` + +Puedes verificar que tu llave esté visible para el `ssh-agent` si ejecutas el siguiente comando: + +```shell +ssh-add -L +``` + +Si el comando dice que no hay identidad disponible, necesitarás agregar tu llave: + +```shell +$ ssh-add yourkey +``` + +{% tip %} + +En Mac OS X, `ssh-agent` "olvidará" esta llave una vez que se reinicie. Pero puedes importar tus llaves SSH en Keychain si utilizas este comando: + +```shell +$ ssh-add -K yourkey +``` + +{% endtip %} + +[tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html +[generating-keys]: /articles/generating-ssh-keys +[generating-keys]: /articles/generating-ssh-keys +[autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows diff --git a/translations/es-ES/content/developers/overview/viewing-deployment-history.md b/translations/es-ES/content/developers/overview/viewing-deployment-history.md new file mode 100644 index 0000000000000..a1cbe9b2a2bbc --- /dev/null +++ b/translations/es-ES/content/developers/overview/viewing-deployment-history.md @@ -0,0 +1,20 @@ +--- +title: Visualizar el historial de despliegues +intro: Ver los despliegues actuales y previos de tu repositorio. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.actions.environments-beta %} + +Puedes entregar despliegues a través de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_actions %} y de ambientes o con {% endif %}la API de REST y apps de terceros. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[{% data variables.product.prodname_actions %}](/actions)". {% endif %}Para obtener más información acerca de los despliegues con la API de REST, consulta la sección "[Repositorios](/rest/reference/repos#deployments)". + +Para ver los despliegues actuales y pasados, da clic en **Ambientes** en la página principal de tu repositorio. ![Ambientes](/assets/images/environments-sidebar.png) + +La página de despliegues muestra el último despliegue activo de cada ambiente para tu repositorio. Si el despliegue incluye una URL de ambiente, un botón de "Ver despliegue" que enlaza a la URL se mostrará junto a dicho despliegue. + +La bitácora de actividad muestra el historial de despliegues para tus ambientes. Predeterminadamente, solo el despliegue más reciente de un ambiente tiene un estado de `Active`; todos los despliegues previos tendrán un estado de `Inactive`. Para obtener más información sobre la inactivación automática de despliegues, consulta la sección "[Despliegues inactivos](/rest/reference/repos#inactive-deployments)". + +También puedes utilizar la API de REST para obtener información sobre los despliegues. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#deployments)". diff --git a/translations/es-ES/content/developers/webhooks-and-events/about-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/about-webhooks.md new file mode 100644 index 0000000000000..8f6ea5dedb75f --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/about-webhooks.md @@ -0,0 +1,34 @@ +--- +title: Acerca de webhooks +intro: Aprende lo básico sobre cómo funcionan los webhooks para ayudarte a ccrear y configurar integraciones. +redirect_from: + - /webhooks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Los Webhooks te permiten crear y configurar integraciones, tales como [{% data variables.product.prodname_github_app %}](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/), las cuales se suscriben a ciertos eventos en GitHub.com. Cuando se activa alguno de esos eventos, enviamos una carga útil de POST por HTTP a la URL que el webhook tiene configurada. Los webhooks pueden utilizarse para actualizar un rastreador de problemas externo, activar compilaciones de IC, actualizar un espejo de respaldo, o incluso para desplegar en tu servidor productivo. Solo te limita tu imaginación. + +Los webhooks pueden instalarse en{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} una [organización][org-hooks], un [repositorio][repo-hooks] específico, o una {% data variables.product.prodname_github_app %}. Una vez que se instalan, el webhook se enviará cada vez que ocurra uno o más eventos suscritos. + +Puedes crear hasta {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks para cada evento en cada destino de instalación {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} (instancia de {% data variables.product.prodname_ghe_server %}, organización específica, o repositorio específico).{% else %} (organización específica o repositorio específico).{% endif %} + +### Eventos + +{% data reusables.webhooks.webhooks_intro %} + +Cada evento corresponde a conjuntos de acciones específicos que pueden suceder en tu organización y/o repositorio. Por ejemplo, si te suscribes al evento `issues`, recibirás cargas útiles detalladas cada vez que un informe de problemas se abra, cierre, etiquete, etc. + +Consulta la sección "[Cargas útiles de los eventos de webhook](/webhooks/event-payloads)" para encontrar una lista de los eventos de webhook disponibles y de sus cargas útiles. + +### Evento de Ping + +{% data reusables.webhooks.ping_short_desc %} + +Para obtener más información acerca de la carga útil del webhook del evento `ping`, consulta el evento [`ping`](/webhooks/event-payloads/#ping). + +[org-hooks]: /rest/reference/orgs#webhooks/ +[repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/es-ES/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md new file mode 100644 index 0000000000000..85c3f3ab2988d --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md @@ -0,0 +1,70 @@ +--- +title: Configurar tu servidor para recibir cargas útiles +intro: Aprende a conigurar un servidor para administrar las cargas útiles de webhook entrantes. +redirect_from: + - /webhooks/configuring +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Ahora que tu webhook está listo para entregar mensajes, configuraremos un servidor básico de Sinatra para gestionar las cargas útiles entrantes. + +Recuerda que configuramos nuestra URL del webhook específicamente como `http://localhost:4567/payload`. Ya que estamos desarrollando localmente, necesitaremos exponer nuestro ambiente de desarrollo local a la internet para que GitHub pueda enviar mensajes y para que nuestro servidor local los pueda procesar. + +Nota: puedes descargar el código fuente completo para este proyecto [del repositorio de ejemplos de plataforma][platform samples]. + +### Utilizando ngrok + +Primero, instalaremos un programa para exponer nuestro host local a la internet. Utilizaremos ngrok para hacerlo. [ngrok es una descarga gratuita](https://ngrok.com/download) disponible para todos los sistemas operativos principales. + +Cuando termines de hacerlo, puedes exponer tu localhost si ejecutas `./ngrok http 4567` en la línea de comandos. Deberías ver una línea que se ve más o menos así: + +```shell +$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567 +``` + +¡Copia esa URL rara de `*.ngrok.io`! Ahora vamos a *regresar* a la URL de la carga útil y vamos a pegar este servidor en ese campo. Se vería ver más o menos como `http://7e9ea9dc.ngrok.io/payload`. + +Cuando lo hacemos, nos hemos preparado para exponer nuestro localhost a la internet en la ruta `/payload`. + +### Escribir el servidor + +¡Ahora viene lo divertido! Queremos que nuestro servidor escuche a las solicitudes de `POST`, en `/payload`, porque es donde le dijimos a GitHub que estaba nuestra URL. Ya que ngrok expone nuestro ambiente local, no necesitamos configurar un servidor real en línea, y podemos probar nuestro código felizmente de manera local. + +Vamos a configurar una pequeña app de Sinatra para que haga algo con la información. Nuestra configuración inicial se verá más o menos así: + +``` ruby +require 'sinatra' +require 'json' + +post '/payload' do + push = JSON.parse(request.body.read) + puts "I got some JSON: #{push.inspect}" +end +``` + +(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) + +Inicia este servidor. + +Ya que configuramos nuestros webhooks para escuchar a los eventos que tengan que ver con `Issues`, continúa y crea un informe de problemas nuevo en el repositorio en el cual estés haciendo las pruebas. Una vez que lo hayas creado, regresa a tu terminal. Deberías ver algo más o menos como esto en tu salida: + +```shell +$ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb +> == Sinatra/1.4.4 has taken the stage on 4567 for development with backup from Thin +> >> Thin web server (v1.5.1 codename Straight Razor) +> >> Maximum connections set to 1024 +> >> Listening on localhost:4567, CTRL+C to stop +> I got some JSON: {"action"=>"opened", "issue"=>{"url"=>"... +``` + +¡Exito! Configuraste exitosamente tu servidor para que escuche a los webhooks. Ahora tu servidor puede procesar esta información en cualquier manera que te parezca pertinente. Por ejemplo, si estuvieras configurando una aplicación web "real", tal vez quisieras registrar algo de la salida de JSON en una base de datos. + +Para obtener información adicional sobre cómo trabajar con los webhooks por diverción y por ganancias, dirígete a la guía de cómo [Probar los Webhooks](/webhooks/testing). + +[platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server +[Sinatra]: http://www.sinatrarb.com/ diff --git a/translations/es-ES/content/developers/webhooks-and-events/creating-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/creating-webhooks.md new file mode 100644 index 0000000000000..ee94c05f7352b --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/creating-webhooks.md @@ -0,0 +1,69 @@ +--- +title: Crear webhooks +intro: 'Aprende a crear un webhook, escoger los eventos a los cuales escuchará en {% data variables.product.prodname_dotcom %} y cómo configurar un servidor para recibir y administrar su carga útil.' +redirect_from: + - /webhooks/creating +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Ahora que entendemos [lo básico de los webhooks][webhooks-overview], vamos a revisar el proceso de creación de nuestra propia integración impulsada por webhooks. En este tutorial, crearemos un webhook de repositorio que será responsable de listar qué tan popular es nuestro repositorio con base en la cantidad de informes de problemas que recibe diariamente. + +Crear un webhook es un proceso de dos pasos. Primero necesitas configurar la forma en la que quieres que se comporte tu webhook a través de {% data variables.product.product_name %}, es decir: a qué eventos quieres que escuche. Después, configurarás tu servidor para recibir y administrar la carga útil. + + +{% data reusables.webhooks.webhooks-rest-api-links %} + +### Configurar un Webhook + +Puedes instalar webhooks en una organización o en un repositorio específico. + +Para configurar un webhook, ve a la página de configuración de tu repositorio u organización. Desde ahí, da clic en **Webhooks**, y luego en **Agregar webhook**. + +Como alternativa, puedes elegir el crear y administrar un webhook [através de la API de Webhooks][webhook-api]. + +Los Webhooks necesitan configurar algunas de sus opciones antes de que los puedas utilizar. Vamos a ver cada una de éstas opciones a continuación. + +### URL de la carga útil + +{% data reusables.webhooks.payload_url %} + +Ya que estamos desarrollando todo localmente para nuestro tutorial, configurémosla como `http://localhost:4567/payload`. Te explicaremos por qué en los documentos de [Configurar tu Servidor](/webhooks/configuring/). + +### Tipo de Contenido + +{% data reusables.webhooks.content_type %} Para efecto de este tutorial, está bien si usas el tipo de contenido predeterminado de `application/json`. + +### Secreto + +{% data reusables.webhooks.secret %} + +### Verificación de SSL + +{% data reusables.webhooks.webhooks_ssl %} + +### Activo + +Predeterminadamente, las entregas de webhook están "Activas". También puedes elegir inhabilitar la entrega de cargas útiles de webhooks si deseleccionas "Activo". + +### Eventos + +Los eventos son el núcleo de los webhooks. Estos webhooks se disparan cuando se toma alguna acción específica en el repositorio, la cual intercepta tu URL de carga útil de l servidor para actuar sobre ella. + +Puedes encontrar un listado completo de eventos de webhook y del cuándo se ejecutan en la referencia de [la API de webhooks][hooks-api]. + +Ya que nuestro webhook trata con informes de problemas en un repositorio, vamos a dar clic en **Permíteme seleccionar eventos individuales** y, posteriormente, en **Informes de problemas**. Asegúrate de seleccionar **Activo** para recibir eventos de los informes de problemas para los webhooks que se activen. También puedes seleccionar todos los eventos utilizando la opción predeterminada. + +Cuando hayas terminado, da clic en **Agregar webhook**. ¡Uf! Ahora que creaste el webhook, es momento de configurar nuestro servidor local para probarlo. Dirígete a [Configurar tu Servidor](/webhooks/configuring/) para aprender cómo hacerlo. + +#### Evento de Comodín + +Para configurar un webhook para todos los eventos, utiliza el caracter de comodín (`*`) para especificar dichos eventos. Cuando agregas el evento de comodín, reemplazaremos cualquier evento existente que hayas configurado con el evento de comodín se te enviarán las cargas útiles para todos los eventos compatibles. También obtendrás automáticamente cualquier evento nuevo que pudiéramos agregar posteriormente. + +[webhooks-overview]: /webhooks/ +[webhook-api]: /rest/reference/repos#hooks +[hooks-api]: /webhooks/#events diff --git a/translations/es-ES/content/developers/webhooks-and-events/events.md b/translations/es-ES/content/developers/webhooks-and-events/events.md new file mode 100644 index 0000000000000..43d087fec0f82 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/events.md @@ -0,0 +1,10 @@ +--- +title: Eventos +intro: 'Tus integraciones pueden suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md new file mode 100644 index 0000000000000..2fd0ad3707806 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md @@ -0,0 +1,248 @@ +--- +title: Tipos de evento de GitHub +intro: 'Para la API de Eventos de {% data variables.product.prodname_dotcom %}, aprende acerca de cada tipo de evento, la acción que los desencadena en {% data variables.product.prodname_dotcom %}, y las propiedades exclusivas de cada evento.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /v3/activity/event_types +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +La API de eventos puede devolver diferentes tipos de ventos que se activan de acuerdo a la actividad en GitHub. Cada respuesta de evento contiene propiedades compartidas, pero tiene un objeto único de `payload` que se determina por su tipo de evento. Las [propiedades comunes del objeto de los eventos](#event-object-common-properties) describen aquellas propiedades que comparten todos los eventos, y cada tipo de evento describe las propiedades de la `payload` que son exclusivas para éste. + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +### Propiedades comunes del objeto de los eventos + +Los objetos de los eventos que se devuelven de las terminales de la API de Eventos tienen la misma estructura. + +| Nombre del atributo de la API del Evento | Descripción | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | Identificador único para el evento. | +| `type` | El tipo de evento. Los eventos utilizan PascalCase para el nombre. | +| `actor (actor)` | El usuario que activó el evento. | +| `actor.id` | El identificador único para el actor. | +| `actor.login` | El nombre de usuario para el actor. | +| `actor.display_login` | El formato de visualización específico para el nombre de usuario. | +| `actor.gravatar_id` | El identificador único del perfil de Gravatar para el actor. | +| `actor.url` | La URL de la API de REST que se utiliza para recuperar el objeto del usuario, el cual incluye información adicional del usuario. | +| `actor.avatar_url` | La URL de la imagen de perfil del actor. | +| `repo` | El objeto del repositorio en donde ocurrió el evento. | +| `repo.id` | El identificador único del repositorio. | +| `repo.name` | El nombre del repositorio, el cual incluye también al nombre del propietario. Por ejemplo, el nombre del repositorio `hello-world`, cuyo propietario es la cuenta de usuario `octocat`, es `octocat/hello-world`. | +| `repo.url` | La URL de la API de REST que se utiliza para recuperar el objeto del repositorio, el cual incluye información adicional sobre dicho repositorio. | +| `payload` | El objeto de la carga útil del evento que es exclusivo para el tipo de evento. En el siguiente ejemplo puedes ver el tipo de evento para el objeto de `payload` de la API de eventos. | + +#### Ejemplo con el objeto de evento WatchEvent + +Este ejemplo te muestra el formato de la respuesta de [WatchEvent](#watchevent) cuando utilizas la [API de Eventos](/rest/reference/activity#events). + +``` +Status: 200 OK +Link: ; rel="next", + ; rel="last" +``` +```json +[ + { + "type": "WatchEvent", + "public": true, + "payload": { + }, + "repo": { + "id": 3, + "name": "octocat/Hello-World", + "url": "https://api.github.com/repos/octocat/Hello-World" + }, + "actor": { + "id": 1, + "login": "octocat", + "gravatar_id": "", + "avatar_url": "https://github.com/images/error/octocat_happy.gif", + "url": "https://api.github.com/users/octocat" + }, + "org": { + "id": 1, + "login": "github", + "gravatar_id": "", + "url": "https://api.github.com/orgs/github", + "avatar_url": "https://github.com/images/error/octocat_happy.gif" + }, + "created_at": "2011-09-06T17:26:27Z", + "id": "12345" + } +] +``` + +### CommitCommentEvent + +{% data reusables.webhooks.commit_comment_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.commit_comment_properties %} + +### CreateEvent + +{% data reusables.webhooks.create_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.create_properties %} + +### DeleteEvent + +{% data reusables.webhooks.delete_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.delete_properties %} + +### ForkEvent + +{% data reusables.webhooks.fork_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.fork_properties %} + +### GollumEvent + +{% data reusables.webhooks.gollum_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.gollum_properties %} + +### IssueCommentEvent + +{% data reusables.webhooks.issue_comment_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.issue_comment_webhook_properties %} +{% data reusables.webhooks.issue_comment_properties %} + +### IssuesEvent + +{% data reusables.webhooks.issues_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.issue_event_api_properties %} +{% data reusables.webhooks.issue_properties %} + +### MemberEvent + +{% data reusables.webhooks.member_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.member_event_api_properties %} +{% data reusables.webhooks.member_properties %} + +### PublicEvent + +{% data reusables.webhooks.public_short_desc %} + +#### Objeto de `payload` del evento + +Este evento devuelve un objeto de `payload` vacío. + +### PullRequestEvent + +{% data reusables.webhooks.pull_request_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.pull_request_event_api_properties %} +{% data reusables.webhooks.pull_request_properties %} + +### PullRequestReviewCommentEvent + +{% data reusables.webhooks.pull_request_review_comment_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.pull_request_review_comment_event_api_properties %} +{% data reusables.webhooks.pull_request_review_comment_properties %} + +### PushEvent + +{% data reusables.webhooks.push_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +| Clave | Type | Descripción | +| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `push_id` | `número` | Identificador único para la carga. | +| `size` | `número` | La cantidad de confirmaciones de la carga. | +| `distinct_size` | `número` | La cantidad de confimraciones distintas para la carga. | +| `ref` | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main`. | +| `head` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | +| `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | +| `commits` | `arreglo` | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (El conjunto incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks). | +| `commits[][sha]` | `secuencia` | El SHA de la confirmación. | +| `commits[][message]` | `secuencia` | El mensaje de la confirmación. | +| `commits[][author]` | `object` | El autor de git de la confirmación. | +| `commits[][author][name]` | `secuencia` | El nombre del autor de git. | +| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | +| `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | +| `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | + +### ReleaseEvent + +{% data reusables.webhooks.release_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.release_event_api_properties %} +{% data reusables.webhooks.release_properties %} + +{% if currentVersion == "free-pro-team@latest" %} +### SponsorshipEvent + +{% data reusables.webhooks.sponsorship_short_desc %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.sponsorship_event_api_properties %} +{% data reusables.webhooks.sponsorship_properties %} +{% endif %} + +### WatchEvent + +{% data reusables.webhooks.watch_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +{% data reusables.webhooks.watch_properties %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/index.md b/translations/es-ES/content/developers/webhooks-and-events/index.md new file mode 100644 index 0000000000000..d7a00651c8390 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/index.md @@ -0,0 +1,21 @@ +--- +title: Webhooks y eventos +intro: 'Puedes configurar, probar y asegurar los webhooks para que tus integraciones puedan suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Índice + +{% topic_link_in_list /webhooks %} + {% link_in_list /about-webhooks %} + {% link_in_list /creating-webhooks %} + {% link_in_list /configuring-your-server-to-receive-payloads %} + {% link_in_list /testing-webhooks %} + {% link_in_list /securing-your-webhooks %} + {% link_in_list /webhook-events-and-payloads %} +{% topic_link_in_list /events %} + {% link_in_list /github-event-types %} + {% link_in_list /issue-event-types %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md new file mode 100644 index 0000000000000..616999551597b --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md @@ -0,0 +1,733 @@ +--- +title: Tipos de eventos de los informes de problemas +intro: 'Para la API de Eventos de Informes de Problemas y la API de Línea de Tiempo, aprende sobre cada tipo de evento, la acción que los activa en {% data variables.product.prodname_dotcom %} y las propiedades exclusivas de cada uno de ellos.' +redirect_from: + - /v3/issues/issue-event-types +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Los eventos de informes de problemas se activan dependiendo de la actividad en las solicitudes de extracción e informes de problemas y se encuentran disponibles en la [API de eventos de informes de problemas](/rest/reference/issues#events) y en la [API de Eventos de la Línea de Tiempo](/rest/reference/issues#timeline). Cada tipo de evento especifica si éste está disponible en la API de Eventos de los Informes de Problemas o en la de Eventos de la Línea de tiempo. + +La API de REST de GitHub considera a cada solicitud de extracción como un informe de problemas, pero no todos los informes de problemas consitutyen una solicitud de extracción. Por esta razón, las terminales de los Eventos de Informes de Problemas y las de Eventos de la Línea de Tiempo podrían devolver tanto informes de problemas como solicitudes de extracción en su respuesta. Las solicitudes de extracción tienen una propiedad de `pull_request` en el objeto del `issue`. Ya que todas las solicitudes de extracción son informes de problemas, las cantidades de unas y de otras no se duplican en un repositorio. Por ejemplo, si abres tu primer informe de problemas en un repositorio, la cantidad será de 1. Si después abres una solicitud de extracción, a cantidad será de 2. Cada tipo de evento especifica si éste ocurre en solicitudes de extracción, informes de problemas, o en ambos. + +### Propiedades comunes del objeto del evento de los informes de problemas + +Los eventos de los informes de problemas tienen la misma estructura de objeto, excepto aquellos eventos que solo se encuentran disponibles en la API de Eventos de la Línea de Tiempo. Algunos eventos también incluyen propiedades adicionales que proporcionan más contexto acerca de los recursos de éstos. Consulta el evento específico para encontrar más detalles sobre cualquier propiedad que difiera de este formato de objeto. + +{% data reusables.issue-events.issue-event-common-properties %} + +### added_to_project + +El informe de problemas o solicitud de extracción se agregó a un tablero de proyecto. {% data reusables.projects.disabled-projects %} + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitud de extracción
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.pre-release-program.starfox-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.project-card-properties %} + +### assigned + +El informe de problemas o solicitud de extracción se asignó al usuario. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.assignee-properties %} + +### automatic_base_change_failed + +GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente y sin éxito. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### automatic_base_change_succeeded + +GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente con éxito. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### base_ref_changed + +La rama base de referencia de la solicitud de extracción cambió. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### closed + +Se cerró el informe de problemas o la solicitud de extracción. Cuando está presente la `commit_id`, esta identifica a la confirmación que cerró el informe de problemas utilizando la sintaxis de "cerrados/arreglados". Para obtener más información acerca de la sintaxis, consulta la sección "[Enlazar una solicitud de extracción con un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### commented + +Un comentario se agregó al informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.timeline_events_object_properties %} + +| Nombre | Type | Descripción | +| ------------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `url` | `secuencia` | La URL de la API de REST que recuperará el comentario del informe de problemas. | +| `html_url` | `secuencia` | La URL de HTML para el comentario del informe de problemas. | +| `issue_url` | `secuencia` | La URL de HTML para el informe de problemas. | +| `id` | `número` | El identificador único del evento. | +| `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | +| `user` | `object` | La persona que comentó en el informe de problemas. | +| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó el comentario. | +| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó el comentario en caso de que éste jamás se haya actualizado. | +| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | +| `body` | `secuencia` | El cuerpo de texto del comentario. | +| `event` | `secuencia` | El valor del evento es `"commented"`. | +| `actor (actor)` | `object` | La persona que generó el evento. | + +### committed + +Una confirmación se agregó a la rama `HEAD` de la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.timeline_events_object_properties %} + +| Nombre | Type | Descripción | +| ------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sha` | `secuencia` | El SHA de la confirmación en la solicitud de extracción. | +| `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | +| `url` | `secuencia` | La URL de la API de REST que recuperará la confirmación. | +| `html_url` | `secuencia` | La URL de HTML de la confirmación. | +| `author` | `object` | La persona que autorizó la confirmación. | +| `committer` | `object` | La persona que confirmó la confirmación en nombre del autor. | +| `tree` | `object` | El árbol de Git de la confirmación. | +| `message` | `secuencia` | El mensaje de la confirmación. | +| `parents` | `matriz de objetos` | Una lista de confirmaciones padre. | +| `verfication` | `object` | El resultado de verificar la firma de la confirmación. Para obtener más información, consulta la sección "[Objeto de verificación de firmas](/rest/reference/git#signature-verification-object)". | +| `event` | `secuencia` | El valor del evento es `"committed"`. | + +### connected + +El informe de problemas o solicitud de extracción se vinculó a otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### convert_to_draft + +La solicitud de extracción se convirtió a modo borrador. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### converted_note_to_issue + +El informe de problemas se creó convirtiendo una nota en un tablero de proyecto para un informe de problemas. {% data reusables.projects.disabled-projects %} + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.pre-release-program.starfox-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.project-card-properties %} + +### cross-referenced + +El informe de problemas o solicitud de extración se referenció desde otro informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.timeline_events_object_properties %} + +| Nombre | Type | Descripción | +| ------------------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `actor (actor)` | `object` | La persona que generó el evento. | +| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó la referencia cruzada. | +| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó la referencia cruzada en caso de que ésta jamás se haya actualizado. | +| `source` | `object` | La solicitud de extracción o informe de problemas que agregó la referencia cruzada. | +| `source[type]` | `secuencia` | Este valor siempre será `"issue"` ya que las solicitudes de extracción son un tipo de informe de rpoblemas. En la API de Eventos de la Línea de Tiempo solo se devolverán los eventos de referencia cruzada que se activen con informes de problemas o solicitudes de extracción. Puedes verificar si existe el objeto `source[issue][pull_request` para determinar si el informe de problemas que activó el evento es una solicitud de extracción. | +| `source[issue]` | `object` | El objeto del `issue` que agregó la referencia cruzada. | +| `event` | `secuencia` | El valor del evento es `"cross-referenced"`. | + +### demilestoned + +El informe de problemas o solicitud de extracción se elimnó de un hito. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. + +### deployed + +Se desplegó la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### deployment_environment_changed + +El ambiente de despliegue de la solicitud de extracción cambió. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### disconnected + +El informe de problemas o solicitud de extracción se desvinculó de otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### head_ref_deleted + +Se eliminó la rama `HEAD` de la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### head_ref_restored + +Se restauró la rama `HEAD` de la solicitud de extracción a su última confirmación conocida. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### labeled + +Se agregó una etiqueta al informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.label-properties %} + +### locked + +Se bloqueó el informe de problemas o la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% data reusables.pre-release-program.sailor-v-preview %} +{% data reusables.pre-release-program.api-preview-warning %} +{% endif %} + +{% data reusables.issue-events.issue-event-common-properties %} +`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. + +### mentioned + +Se `@mentioned` al `actor` en el cuerpo de un informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### marked_as_duplicate + +Un usuario con permisos de escritura marcó un informe de problemas como el duplicado de otro, o el mismo caso con alguna solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### fusionado + +Se fusionó la solicitud de extracción. El atributo de `commit_id` es el SHA1 de la confirmación `HEAD` que se fusionó. El `commit_repository` siempre es el mismo que el repositorio principal. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### milestoned + +El informe de problemas o solicitud de extracción se agregó a un hito. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. + +### moved_columns_in_project + +El informe de problemas o solicitud de extracción se movió entre columnas en un tablero de proyecto. {% data reusables.projects.disabled-projects %} + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.pre-release-program.starfox-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.project-card-properties %} +`previous_column_name` | `string` | El nombre de la columna desde la cual se movió el informe de problemas. + +### pinned + +Se fijó el informe de problemas. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### ready_for_review + +Se creó una solicitud de extracción que no está en modo borrador. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### referenced + +Se referenció al informe de problemas desde un mensaje de confirmación. El atributo `commit_id` es la confirmación de tipo SHA1 de donde eso sucedió y el commit_repository es el lugar donde se cargó esa confirmación. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### removed_from_project + +El informe de problemas o solicitud de extracción se eliminó de un tablero de proyecto. {% data reusables.projects.disabled-projects %} + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.pre-release-program.starfox-preview %} +{% data reusables.pre-release-program.api-preview-warning %} + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.project-card-properties %} + +### renombrado + +Se cambió el informe de problemas o la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +`rename` | `object` | Los detalles del nombre. `rename[from]` | `string` | El nombre anterior. `rename[to]` | `string` | El nombre nuevo. + +### reopened + +El informe de problemas o solicitud de extracción se reabrió. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### review_dismissed + +Se destituyó la revisión de la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.review-dismissed-properties %} + +### review_requested + +Se solicitó una revisión de una solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.review-request-properties %} + +### review_request_removed + +Se eliminó una solicitud de revisión para una solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.review-request-properties %} + +### reviewed + +Se revisió la solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Solicitudes de cambios
    | | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.timeline_events_object_properties %} + +| Nombre | Type | Descripción | +| -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | `número` | El identificador único del evento. | +| `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | +| `user` | `object` | La persona que comentó en el informe de problemas. | +| `body` | `secuencia` | El texto de resúmen de la revisión. | +| `commit_id` | `secuencia` | El SHA de la última confirmación en la soicitud de extracción al momento de la revisión. | +| `submitted_at` | `secuencia` | La marca de tiempo que indica cuándo se emitió la revisión. | +| `state` | `secuencia` | El estado de la revisión emitida. Puede ser uno de entre: `commented`, `changes_requested`, o `approved`. | +| `html_url` | `secuencia` | La URL de HTML para la revisión. | +| `pull_request_url` | `secuencia` | La URL de la API de REST que recuperará la solicitud de extracción. | +| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | +| `_links` | `object` | El `html_url` y `pull_request_url`. | +| `event` | `secuencia` | El valor del evento es `"reviewed"`. | + +### subscribed + +Alguien se suscribió para recibir notificaciones para un informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### transferred + +El informe de problemas se transfirió a otro repositorio. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### unassigned + +De desasignó a un usuario del informe de problemas. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.assignee-properties %} + +### unlabeled + +La etiqueta se eliminó del informe de problemas. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} +{% data reusables.issue-events.label-properties %} + +### unlocked + +Se desbloqueó el informe de problemas. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% data reusables.pre-release-program.sailor-v-preview %} +{% data reusables.pre-release-program.api-preview-warning %} +{% endif %} + +{% data reusables.issue-events.issue-event-common-properties %} +`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. + +### unmarked_as_duplicate + +Un informe de problemas que algún usuario había marcado previamente como duplicado de otro informe de problemas ya no se considera como duplicado, o el mismo caso con solicitudes de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### unpinned + +El informe de problemas dejó de fijarse. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +### unsubscribed + +Alguien se desuscribió de recibir notificaciones para un informe de problemas o solicitud de extracción. + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +{% if currentVersion == "free-pro-team@latest" %} +### user_blocked + +El propietario de una organización bloqueó a un usuario de la misma. Esto se hizo [a través de uno de los comentarios del usuario bloqueado sobre el informe de problemas](/articles/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). + +#### Disponibilidad + +| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | +|:---------------------------- |:---------------------------------------:|:------------------------------------:| +|
    • Problemas
    • Solicitudes de cambios
    | **X** | **X** | + +#### Propiedades del objeto del evento + +{% data reusables.issue-events.issue-event-common-properties %} + +{% endif %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md new file mode 100644 index 0000000000000..dc7e3d35b63bf --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -0,0 +1,88 @@ +--- +title: Asegurar tus webhooks +intro: 'Asegúrate de que tu servidor está recibiendo únicamente las solicitudes de {% data variables.product.prodname_dotcom %} esperadas por razones de seguridad.' +redirect_from: + - /webhooks/securing +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Una vez que tu servidor se configure para recibir cargas útiles, éste escuchará a cualquiera de ellas que se envíe a la terminal que configuraste. Por razones de seguridad, probablemente quieras limitar las solicitudes a aquellas que vengan de GitHub. Hay algunas formas de solucionar esto, por ejemplo, podrías decidir el permitir las solicitudes que vengan de la dirección IP de GitHub, pero una manera mucho más fácil es configurar un token secreto y validar la información. + +{% data reusables.webhooks.webhooks-rest-api-links %} + +### Configurar tu token secreto + +Necesitarás configurar tu token secreto en dos lugares: GitHub y tu servidor. + +Para configurar tu token en GitHub: + +1. Navega al repositorio en donde configuraste tu webhook. +2. Llena la caja de texto del secreto. Utiliza una secuencia aleatoria con entropía alta (por ejemplo, tomando la salida de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` en la terminal). ![Campo de webhook y de token secreto](/assets/images/webhook_secret_token.png) +3. Da clic en **Actualizar Webhook**. + +Después, configura una variable de ambiente en tu servidor, la cual almacene este token. Por lo general, esto es tan simple como el ejecutar: + +```shell +$ export SECRET_TOKEN=your_token +``` + +¡**Jamás** preprogrames el token en tu app! + +### Validar cargas útiles de GitHub + +Cuando se configura tu token secreto, {% data variables.product.product_name %} lo utiliza para crear una firma de hash con cada carga útil. Esta firma de hash se incluye con los encabezados de cada solicitud como una {% 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 %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% note %} + +**Nota:** Para tener compatibilidad en versiones anteriores, también incluimos el encabezado `X-Hub-Signature` que se genera utilizando la función de hash SHA-1. De ser posible, te recomendamos que utilices el encabezado de `X-Hub-Signature-256` para mejorar la seguridad. El siguiente ejemplo ilustra el uso del encabezado `X-Hub-Signature-256`. + +{% endnote %} +{% endif %} + +Por ejemplo, si tienes un servidor básico que escucha a los webhooks, puede configurarse de forma similar a esto: + +``` ruby +require 'sinatra' +require 'json' + +post '/payload' do + push = JSON.parse(params[:payload]) + "I got some JSON: #{push.inspect}" +end +``` + +La intención es calcular un hash utilizando tu `SECRET_TOKEN`, y asegurarse de que el resultado empate con el hash de {% data variables.product.product_name %}. {% data variables.product.product_name %} utiliza un resumen hexadecimal de HMAC para calcular el hash, así que podrías reconfigurar tu servidor para que se viera así: + +``` ruby +post '/payload' do + request.body.rewind + payload_body = request.body.read + verify_signature(payload_body) + push = JSON.parse(params[:payload]) + "I got some JSON: #{push.inspect}" +end + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +def verify_signature(payload_body) + signature = 'sha256=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha256'), ENV['SECRET_TOKEN'], payload_body) + return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE_256']) +end{% elsif currentVersion ver_lt "enterprise-server@2.23" %} +def verify_signature(payload_body) + signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body) + return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE']) +end{% endif %} +``` + +Tus implementaciones de lenguaje y de servidor pueden diferir de esta muestra de código. Sin embargo, hay varias cosas muy importantes que destacar: + +* Sin importar qué implementación utilices, la firma de hash comienza con {% 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 %}, utilizando la llave de tu token secreto y el cuerpo de tu carga útil. + +* **No se recomienda** utilizar un simple operador de `==`. Un método como el de [`secure_compare`][secure_compare] lleva a cabo una secuencia de comparación de "tiempo constante" que ayuda a mitigar algunos ataques de temporalidad en contra de las operaciones de igualdad habituales. + +[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare diff --git a/translations/es-ES/content/developers/webhooks-and-events/testing-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/testing-webhooks.md new file mode 100644 index 0000000000000..1e5f079cfe133 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/testing-webhooks.md @@ -0,0 +1,37 @@ +--- +title: Probar los webhooks +intro: 'Revisa tus entregas de webhook en {% data variables.product.prodname_dotcom %}, incluyendo la solicitud HTTP y la carga útil, así como la respuesta.' +redirect_from: + - /webhooks/testing +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Ahor que [configuraste tu servidor local](/webhooks/configuring/), podrías estar interesado en llevar tu código a sus límites. Para ello, la vista de webhooks de GitHub te proporciona herramientas para probar tus cargas útiles desplegadas. + +### Listar las entregas recientes + +Cada webhook tiene su propia sección de "Entregas Recientes", la cual lista rápidamente si una entrega fue exitosa (paloma verde) o fallida (x roja). También puedes identificar cuando se intentó cada entrega. + +{% data variables.product.product_name %} mantiene un log de cada entrega de webhook durante {% if currentVersion == "free-pro-team@latest" %} 30 {% else %} 8 {% endif %} días. + +![Vista de entregas recientes](/assets/images/webhooks_recent_deliveries.png) + +### Profundizar en los resultados + +Si expandes una entrega individual podrás presenciar *exactamente* qué información de GitHub se está intentando enviar a tu servidor. Esto incluye tanto la solicitud de HTTP como la respuesta. + +#### Solicitud + +La vista de entregas del webhook te proporciona información sobre qué encabezados se enviaron a través de GitHub. También incluye detalles acerca de la carga útil de JSON. + +![Visualizar la solicitud de una carga útil](/assets/images/payload_request_tab.png) + +#### Respuesta + +La pestaña de respuesta lista la forma en que tu servidor respondió una vez que recibió la carga útil de GitHub. Esto incluye al código de estado, a los encabezados y a cualquier dato adicional dentro del cuerpo de la respuesta. + +![Visualizar la respuesta de una carga útil](/assets/images/payload_response_tab.png) diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md new file mode 100644 index 0000000000000..d4a4025afc612 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -0,0 +1,1353 @@ +--- +title: Eventos y cargas útiles de un Webhook +intro: 'Para cada evento de webhook, puedes revisar cuándo ocurre el evento, una carga útil de ejemplo, y las descripciones de los parámetros del objeto de dicha carga útil.' +product: '{% data reusables.gated-features.enterprise_account_webhooks %}' +redirect_from: + - /early-access/integrations/webhooks/ + - /v3/activity/events/types/ + - /webhooks/event-payloads +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +{% data reusables.webhooks.webhooks_intro %} + +Puedes crear webhooks que se suscriban a los eventos listados en esta página. Cada evento de webhook incluye una descripción de las propiedades de dicho webhook y un ejemplo de carga útil. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/)". + +### Propuiedades comunes del objeto de la carga útil del webhook + +Cada carga útil del evento del webhook contiene propiedades únicas de dicho evento. Puedes encontrar estas propiedades únicas en las secciones individuales de tipo de evento. + +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La mayoría de las cargas útiles de webhooks contienen una propiedad de `action` que contiene la actividad específica que activa el evento. | +{% data reusables.webhooks.sender_desc %} Esta propiedad se incluye en cada carga útil del webhook. +{% data reusables.webhooks.repo_desc %} Las cargas útiles del webhook contienen la propiedad `repository` cuando el evento ocurre desde una actividad en un repositorio. +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} Para obtener más información, consulta la sección "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)". + +Las propiedades únicas de un evento de webhook son las mismas que encontrarás en la propiedad `payload` cuando utilices la [API de eventos](/rest/reference/activity#events). Una excepción es el [evento `push`](#push). Las propiedades únicas de la carga útil del evento `push` del webhook y la propiedad `payload` en la API de Eventos difieren entre ellos. La carga útil del webhook contiene información más detallada. + +{% tip %} + +**Nota:** Las cargas útiles se limitan a los 25 MB. Si tu evento genera una carga útil mayor, el webhook no se lanzará. Esto puede pasar, por ejemplo, en un evento de `create` si muchas ramas o etiquetas se cargan al mismo tiempo. Te sugerimos monitorear el tamaño de tu carga útil para garantizar la entrega. + +{% endtip %} + +#### Encabezados de entrega + +Las cargas útiles de HTTP POST que se entregan a la terminal URL configurada para tu webhook contendrán varios encabezados especiales: + +| Encabezado | Descripción | +| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | Nombre del evento que desencadenó la entrega. | +| `X-GitHub-Delivery` | Una [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar la entrega.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| `X-GitHub-Enterprise-Version` | La versión de la instancia de {% data variables.product.prodname_ghe_server %} que envía la carga útil del HTTP POST. | +| `X-GitHub-Enterprise-Host` | El nombre de host de la instancia de {% data variables.product.prodname_ghe_server %} que envió la carga útil de HTTP POST.{% endif %}{% if currentVersion != "github-ae@latest" %} +| `X-Hub-Signature` | Este encabezado se envía si el webhook se configura con un [`secret`](/rest/reference/repos#create-hook-config-params). Éste es el resúmen hexadecimal de HMAC del cuerpo de la solicitud y se genera utilizando tanto la función de hash SHA-1 y el `secret` como la `key` HMAC.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} La `X-Hub-Signature` se proporciona para compatibilidad con las integraciones existentes, y te recomendamos que mejor utilices la `X-Hub-Signature-256`, que es más segura.{% 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 encabezado se envía si el webhook se configura con un [`secret`](/rest/reference/repos#create-hook-config-params). Este es el resumen hexadecimal de HMAC para el cuerpo de la solicitud y se genera utilizando la función de hash SHA-256 y el `secret` como la `key` HMAC.{% endif %} + +También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hookshot/`. + +#### Ejemplo de entrega + +```shell +> POST /payload HTTP/1.1 + +> Host: localhost:4567 +> X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +> X-GitHub-Enterprise-Version: 2.15.0 +> X-GitHub-Enterprise-Host: example.com{% endif %}{% if currentVersion != "github-ae@latest" %} +> X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +> X-Hub-Signature-256: sha256=d57c68ca6f92289e6987922ff26938930f6e66a2d161ef06abdf1859230aa23c{% endif %} +> User-Agent: GitHub-Hookshot/044aadd +> Content-Type: application/json +> Content-Length: 6615 +> X-GitHub-Event: issues + +> { +> "action": "opened", +> "issue": { +> "url": "{% data variables.product.api_url_pre %}/repos/octocat/Hello-World/issues/1347", +> "number": 1347, +> ... +> }, +> "repository" : { +> "id": 1296269, +> "full_name": "octocat/Hello-World", +> "owner": { +> "login": "octocat", +> "id": 1, +> ... +> }, +> ... +> }, +> "sender": { +> "login": "octocat", +> "id": 1, +> ... +> } +> } +``` + +### check_run + +{% data reusables.webhooks.check_run_short_desc %} + +{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} + +#### Disponibilidad + +- Los webhooks de repositorio solo reciben cargas útiles para los tipos de evento `created` y `completed` en un repositorio +- Los webhooks de organización solo reciben cargas útiles para los tipos de evento `created` y `completed` en los repositorios +- Las {% data variables.product.prodname_github_app %}s con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `rerequested` y `requested_action`. Las cargas útiles para los tipos de evento `rerequested` y `requested_action` solo se enviarán a la {% data variables.product.prodname_github_app %} que se esté solicitando. Las {% data variables.product.prodname_github_app %}s con el `checks:write` se suscriben automáticamente a este evento de webhook. + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.check_run_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.check_run.created }} + +### check_suite + +{% data reusables.webhooks.check_suite_short_desc %} + +{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} + +#### Disponibilidad + +- Los webhooks de los repositorios únicamente recibirán cargas útiles para los tipos de evento `completed` en un repositorio +- Los webhooks de organización recibirán únicamente cargas útiles para los tipos de evento `completed` en los repositorios +- Las {% data variables.product.prodname_github_app %}s con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `requested` y `rerequested`. Las cargas útiles para los tipos de evento `requested` y `rerequested` se envían únicamente a la {% data variables.product.prodname_github_app %} que se está solicitando. Las {% data variables.product.prodname_github_app %}s con el `checks:write` se suscriben automáticamente a este evento de webhook. + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.check_suite_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.check_suite.completed }} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### comentario_confirmación de cambios + +{% data reusables.webhooks.code_scanning_alert_event_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.code_scanning_alert_event_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +`sender` | `object` | Si la `action` está como `reopened_by_user` o `closed_by_user`, el objeto que sea el `sender` será el usuario que activó el evento. El objeto `sender` estará vacío en el resto de las acciones. + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} + +### comentario_confirmación de cambios + +{% data reusables.webhooks.commit_comment_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.commit_comment_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.commit_comment.created }} +{% endif %} + +### content_reference + +{% data reusables.webhooks.content_reference_short_desc %} + +Los eventos de webhook se desencadenan basándose en la especificidad del dominio que registres. Por ejemplo, si registras un subdominio (`https://subdomain.example.com`), entonces la única URL para el subdominio activarán este evento. Si registras un dominio (`https://example.com`) entonces las URL para el dominio y todos sus subdominios activarán este evento. Consulta la sección "[Crear un adjunto de contenido](/rest/reference/apps#create-a-content-attachment)" para crear un nuevo adjunto de contenido. + +Solo las {% data variables.product.prodname_github_app %}s podrán recibir este evento. Las {% data variables.product.prodname_github_app %}s deben tener el permiso `content_references` `write` para suscribirse a este evento. + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.content_reference.created }} + +### create (crear) + +{% data reusables.webhooks.create_short_desc %} + +{% note %} + +**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. + +{% endnote %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.create_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.create }} + +### eliminar + +{% data reusables.webhooks.delete_short_desc %} + +{% note %} + +**Nota:** No recibirás un webhook para este evento cuando borres más de tres etiquetas al mismo tiempo. + +{% endnote %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.delete_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.delete }} + +### deploy_key + +{% data reusables.webhooks.deploy_key_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.deploy_key_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.deploy_key.created }} + +### deployment + +{% data reusables.webhooks.deployment_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `deployments` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} +| `deployment` | `object` | El [despliegue](/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 %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.deployment }} + +### deployment_status + +{% data reusables.webhooks.deployment_status_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `deployments` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} +| `deployment_status` | `object` | El [Estado del despliegue](/rest/reference/repos#list-deployment-statuses). | +| `deployment_status["state"]` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | +| `deployment_status["target_url"]` | `secuencia` | El enlace opcional agregado al estado. | +| `deployment_status["description"]` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | +| `deployment` | `object` | El [despliegue](/rest/reference/repos#list-deployments) con el que se asocia este estado. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.deployment_status }} + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +### enterprise + +{% data reusables.webhooks.enterprise_short_desc %} + +#### Disponibilidad + +- Webhooks de GitHub Enterprise. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/)." + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------- | ----------- | ---------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `anonymous_access_enabled` o `anonymous_access_disabled`. | + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} + +{% endif %} + +### fork + +{% data reusables.webhooks.fork_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.fork_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.fork }} + +### github_app_authorization + +Este evento ocurre cuando alguien revoca su autorización de una {% data variables.product.prodname_github_app %}. Una {% data variables.product.prodname_github_app %} recibe este webhook predeterminadamente y no puede desuscribirse de este evento. + +{% data reusables.webhooks.authorization_event %} Para obtener detalles sobre las solicitudes de usuario a servidor, las cuales requieren autorización de la {% data variables.product.prodname_github_app %}, consulta la sección "[Identificar y autorizar a los usuarios para las {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". + +#### Disponibilidad + +- {% data variables.product.prodname_github_app %}s + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------- | ----------- | ----------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `revoked`. | +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} + +### gollum + +{% data reusables.webhooks.gollum_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.gollum_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.gollum }} + +### installation + +{% data reusables.webhooks.installation_short_desc %} + +{% note %} + +**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:**{% data reusables.pre-release-program.suspend-installation-beta %}Para obtener más información, consulta la sección "[Suspender la instalación de una {% data variables.product.prodname_github_app %}](/apps/managing-github-apps/suspending-a-github-app-installation/)". + +{% endnote %} +{% endif %} + +#### Disponibilidad + +- {% data variables.product.prodname_github_app %}s + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.installation_properties %} +{% data reusables.webhooks.app_always_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.installation.deleted }} + +### installation_repositories + +{% data reusables.webhooks.installation_repositories_short_desc %} + +{% note %} + +`repository` cuando el evento ocurre desde una actividad en un repositorio. + +{% endnote %} + +#### Disponibilidad + +- {% data variables.product.prodname_github_app %}s + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.installation_repositories_properties %} +{% data reusables.webhooks.app_always_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.installation_repositories.added }} + +### comentario_propuesta + +{% data reusables.webhooks.issue_comment_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `issues` + +#### Objeto de carga útil del webhook + +{% 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 %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.issue_comment.created }} + +### propuestas + +{% data reusables.webhooks.issues_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `issues` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.issue_webhook_properties %} +{% data reusables.webhooks.issue_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook cuando alguien edita un informe de problemas + +{{ webhookPayloadsForCurrentVersion.issues.edited }} + +### label + +{% data reusables.webhooks.label_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `metadata` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ---------------------- | ----------- | --------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`, `edited`, o `deleted`. | +| `label` | `object` | La etiqueta que se añadió. | +| `changes` | `object` | Los cambios a la etiqueta si la acción se `edited` (editó). | +| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | +| `changes[color][from]` | `secuencia` | La versión previa del color si la acción se `edited` (editó). | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.label.deleted }} + +{% if currentVersion == "free-pro-team@latest" %} +### marketplace_purchase + +Actividad relacionada con una compra en GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta el "[GitHub Marketplace](/marketplace/)". + +#### Disponibilidad + +- {% data variables.product.prodname_github_app %}s + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada para un plan de [GitHub Marketplace](https://github.com/marketplace). Puede ser una de las siguientes:
    • `purchased` - Alguien compró un plan de GitHub Marketplace. El cambio deberá entrar en vigor en la cuenta inmediatamente.
    • `pending_change` - Reicbirás el evento `pending_change` cuando alguien haya degradado o cancelado un plan de GitHub Marketplace para indicar que ocurrirá un cambio en la cuenta. El nuevo plan o cancelación entra en vigor al final del ciclo de facturación. El tipo de evento `cancelled` o `changed` se enviará cuando haya concluido el ciclo de facturación y la cancelación o plan nuevo deberán entrar en vigor.
    • `pending_change_cancelled` - Alguien canceló un cambio pendiente. Los cambios pendientes incluyen cancelaciones y degradaciones de planes que entrarán en vigor al final del ciclo de facturación.
    • `changed` - Alguien mejoró o degradó un plan de GitHub Marketplace y el cambio deberá entrar en vigor en la cuenta de inmediato.
    • `cancelled` - Alguien canceló un plan de GitHub marketplace y el último ciclo de facturación ya terminó. El cambio deberá entrar en vigor en la cuenta inmediatamente.
    | + +Para obtener una descripción detallada de esta carga útil y de aquella para cada tipo de `action`, consulta los [eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). + +#### Ejemplo de carga útil de webhook cuando alguien compra el plan + +{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} + +{% endif %} + +### member + +{% data reusables.webhooks.member_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `members` + +#### Objeto de carga útil del webhook + +{% 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 %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.member.added }} + +### membership + +{% data reusables.webhooks.membership_short_desc %} + +#### Disponibilidad + +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `members` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.membership_properties %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.membership.removed }} + +### meta + +Se eliminó el evento para el cual se configuró este webhook. Este evento únicamente escuchará los cambios del gancho particular en el cual se instaló. Por lo tanto, debe seleccionarse para cada gancho para el cual quieras recibir metaeventos. + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| --------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `deleted`. | +| `hook_id` | `número` | La id del webhook modificado. | +| `hook` | `object` | El webhook modificado. Este contendrá claves diferentes con base en el tipo de webhook que sea: de repositorio, organización, negocio, app, o GitHub Marketplace. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.meta.deleted }} + +### milestone + +{% data reusables.webhooks.milestone_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.milestone_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.milestone.created }} + +### organization + +{% data reusables.webhooks.organization_short_desc %} + +#### Disponibilidad + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Los webhooks de GitHub Enterprise reciben únicamente eventos de `created` y `deleted`. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} +- Los webhooks de organización únicamente reciben los eventos `deleted`, `added`, `removed`, `renamed`, y `invited` events +- {% data variables.product.prodname_github_app %}s con el permiso `members` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, o `member_invited`. | +| `invitation` | `object` | La invitación para el usuario o correo electrónico si la acción es `member_invited`. | +| `membership` | `object` | La membrecía entre el usuario y la organización. No está presente cuando la cción es `member_invited`. | +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.organization.member_added }} + +{% if currentVersion == "free-pro-team@latest" %} + +### org_block + +{% data reusables.webhooks.org_block_short_desc %} + +#### Disponibilidad + +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `organization_administration` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------------- | ----------- | ----------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `blocked` o `unblocked`. | +| `blocked_user` | `object` | Información acerca del usuario que se bloqueó o desbloqueó. | +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.org_block.blocked }} + +### package + +Actividad relacionada con el {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} para obtener más información, consulta la sección "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para aprender más sobre el {% data variables.product.prodname_registry %}. + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.package_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.package.published }} +{% endif %} + +### page_build + +{% data reusables.webhooks.page_build_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `pages` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------- | -------- | ---------------------------------------------------------------------------------------------------------------- | +| `id` | `número` | El idientificador único de la compilación de la página. | +| `build` | `object` | La misma terminal de [Listar las compilaciones de GitHub Pages](/rest/reference/repos#list-github-pages-builds). | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.page_build }} + +### ping + +{% data reusables.webhooks.ping_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s reciben un evento de ping con un `app_id` que se utiliza para registrar la app + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `zen` | `secuencia` | Secuencia aleatoria de GitHub zen. | +| `hook_id` | `número` | La ID del webhook que activó el ping. | +| `hook` | `object` | La [configuración del webhook](/rest/reference/repos#get-a-repository-webhook). | +| `hook[app_id]` | `número` | Cuando registras una {% data variables.product.prodname_github_app %} nueva, {% data variables.product.product_name %} envía un evento de ping a la **URL del webhook** que especificaste durante el registro. El evento contiene la `app_id`, la cual se requiere para [autenticar](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) una app. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.ping }} + +### project_card + +{% data reusables.webhooks.project_card_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.project_card_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.project_card.created }} + +### project_column + +{% data reusables.webhooks.project_column_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.project_column_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.project_column.created }} + +### project + +{% data reusables.webhooks.project_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.project_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.project.created }} + +### public + +{% data reusables.webhooks.public_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `metadata` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ----- | ---- | ----------- | +| | | | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.public }} + +### solicitud_extracción + +{% data reusables.webhooks.pull_request_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.pull_request_webhook_properties %} +{% data reusables.webhooks.pull_request_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +Las entregas para los eventos `review_requested` y `review_request_removed` tendrán un campo adicional llamado `requested_reviewer`. + +{{ webhookPayloadsForCurrentVersion.pull_request.opened }} + +### revisión_solicitud de extracción + +{% data reusables.webhooks.pull_request_review_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.pull_request_review_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} + +### comentarios _revisiones_solicitudes de extracción + +{% data reusables.webhooks.pull_request_review_comment_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.pull_request_review_comment_webhook_properties %} +{% data reusables.webhooks.pull_request_review_comment_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} + +### push + +{% data reusables.webhooks.push_short_desc %} + +{% note %} + +**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. + +{% endnote %} + +{% tip %} + +**Nota**: El ejemplo de la carga útil del webhook siguiendo la tabla difiere significativamente de la carga útil de la API de Eventos descrita en la misma. Entre otras diferencias, la carga útil del webhook incluye ambos objetos, `sender` y `pusher`. El remitente y cargador son el mismo usuario que inició el evento `push`, pero el objeto `sender` contiene más detalles. + +{% endtip %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main`. | +| `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | +| `after` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | +| `commits` | `arreglo` | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (El conjunto incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks). | +| `commits[][id]` | `secuencia` | El SHA de la confirmación. | +| `commits[][timestamp]` | `secuencia` | La marca de tiempo de tipo ISO 8601 de la confirmación. | +| `commits[][message]` | `secuencia` | El mensaje de la confirmación. | +| `commits[][author]` | `object` | El autor de git de la confirmación. | +| `commits[][author][name]` | `secuencia` | El nombre del autor de git. | +| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | +| `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | +| `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | +| `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. | +| `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. | +| `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. | +| `pusher` | `object` | El usuario que subió la confirmación. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.push }} + +### release + +{% data reusables.webhooks.release_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `contents` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.release_webhook_properties %} +{% data reusables.webhooks.release_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ 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 ocurre cuando una {% data variables.product.prodname_github_app %} envía una solicitud de `POST` a la terminal "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)". + +#### Disponibilidad + +- Las {% data variables.product.prodname_github_app %}s deben tener el permiso `contents` para recibir este webhook. + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.repository_dispatch }} +{% endif %} + +### repositorio + +{% data reusables.webhooks.repository_short_desc %} + +#### Disponibilidad + +- Los webhooks de repositorio reciben todos los eventos excepto los de `deleted` +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s con el permiso `metadata` reciben todos los tipos de evento menos los de `deleted` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------- | ----------- | ---------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de las siguientes:
    • `created` - Un repositorio se crea.
    • Un repositorio se borra.
    • `archived` - Un repositorio se archiva.
    • `unarchived` - Un repositorio se desarchiva.
      • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
    • `anonymous_access_enabled` - Un repositorio se [habilita para el acceso anónimo de Git](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - Un repositorio se [inhabilita para el acceso anónimo de Git](/rest/overview/api-previews#anonymous-git-access-to-repositories)
      • {% endif %}
    • `edited` - Se edita la información de un repositorio.
    • `renamed` - Un repositorio se renombra.
    • `transferred` - Un repositorio se transfiere.
    • `publicized` - Un repositorio se hace público.
    • `privatized` - Un repositorio se hace privado.
    | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.repository.publicized }} + +{% if currentVersion == "free-pro-team@latest"%} +### repository_import + +{% data reusables.webhooks.repository_import_short_desc %} Para recibir este evento para un repositorio personal, debes crear un repositorio vacío antes de la importación. Este evento puede activarse utilizando ya sea el [Importador de GitHub](/articles/importing-a-repository-with-github-importer/) o la [API de importaciones fuente](/rest/reference/migrations#source-imports). + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.repository_import_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.repository_import }} + +### repository_vulnerability_alert + +{% data reusables.webhooks.repository_vulnerability_alert_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.repository_vulnerability_alert_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- Las {% data variables.product.prodname_github_app %}s con el permiso de `secret_scanning_alerts:read` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.secret_scanning_alert_event_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +`sender` | `object` | Si la `action` se muestra como `resolved` o como `reopened`, el objeto `sender` será el usuario que activó el evento. El objeto `sender` estará vacío en el resto de las acciones. + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} +### security_advisory + +Actividad relacionada con una asesoría de seguridad. Una asesoría de seguridad proporciona información acerca de las vulnerabilidades relacionadas con la seguridad en el software dentro de GitHub. El conjunto de datos de la asesoría de seguridad también impulsa las alertas de seguridad de Github, consulta la sección "[Acerca de las alertas de seguridad para dependencias vulnerables](/articles/about-security-alerts-for-vulnerable-dependencies/)". +{% endif %} + +#### Disponibilidad + +- {% data variables.product.prodname_github_app %}s with the `security_events` permission + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. La acción puede ser una de entre `published`, `updated`, o `performed` en el caso de todos los eventos nuevos. | +| `security_advisory` | `object` | Los detalles de la asesoría de seguridad, incluyendo el resumen, descripción, y severidad. | + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.security_advisory.published }} + +{% if currentVersion == "free-pro-team@latest" %} +### sponsorship + +{% data reusables.webhooks.sponsorship_short_desc %} + +Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Configurar webhooks para eventos en tu cuenta patrocinada](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". + +#### Disponibilidad + +- Cuentas patrocinadas + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.sponsorship_webhook_properties %} +{% data reusables.webhooks.sponsorship_properties %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil de un webhook cuando alguien crea un patrocinio + +{{ webhookPayloadsForCurrentVersion.sponsorship.created }} + +#### Ejemplo de carga útil de un webhook cuando alguien degrada un patrocinio + +{{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} + +{% endif %} + +### star + +{% data reusables.webhooks.star_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.star_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.star.created }} + +### status + +{% data reusables.webhooks.status_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `statuses` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | `número` | El identificador único del estado. | +| `sha` | `secuencia` | El SHA de la confirmación. | +| `state` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | +| `description` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | +| `url_destino` | `secuencia` | El enlace opcional agregado al estado. | +| `branches` | `arreglo` | Un conjunto de objetos de la rama que contiene el SHA del estado. Cada rama contiene el SHA proporcionado, pero éste puede ser o no el encabezado de la rama. El conjunto incluye un máximo de 10 ramas. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.status }} + +### team + +{% data reusables.webhooks.team_short_desc %} + +#### Disponibilidad + +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `members` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ----------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `created`, `deleted`, `edited`, `added_to_repository`, o `removed_from_repository`. | +| `team` | `object` | El equipo mismo. | +| `changes` | `object` | Los cambios al equipo si la acción está como `edited`. | +| `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | +| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | +| `changes[privacy][from]` | `secuencia` | La versión previa de la privacidad del equipo si ésta se encuentra como `edited`. | +| `changes[repository][permissions][from][admin]` | `boolean` | La versión previa de los permisos de `admin` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | +| `changes[repository][permissions][from][pull]` | `boolean` | La versión previa de los permisos de `pull` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | +| `changes[repository][permissions][from][push]` | `boolean` | La versión previa de los permisos de `push` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | +| `repositorio` | `object` | El repositorio que se agregó o eliminó del alcance del equipo si la acción se encuentra como `added_to_repository`, `removed_from_repository`, o `edited`. Para las acciones que estén como `edited`, el `repository` también contendrá los nuevos niveles de permiso del equipo para dicho repositorio. | +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.team.added_to_repository }} + +### team_add + +{% data reusables.webhooks.team_add_short_desc %} + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `members` + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------- | +| `team` | `object` | El [equipo](/rest/reference/teams) que se modificó. **Nota:** Los eventos anteriores podrían no incluir esto en la carga útil. | +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.team_add }} + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +### user + +Cuando se aplica `created` o `deleted` a un usuario. + +#### Disponibilidad +- Webhooks de GitHub Enterprise. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/)." + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.user.created }} + +{% endif %} + +### watch + +{% data reusables.webhooks.watch_short_desc %} + +El actor del evento es el [usuario](/rest/reference/users) que marcó el repositorio con una estrella, y el repositorio del evento es el [repositorio](/rest/reference/repos) que se marcó con una estrella. + +#### Disponibilidad + +- Webhooks de repositorio +- Webhooks de organización +- {% data variables.product.prodname_github_app %}s con el permiso `metadata` + +#### Objeto de carga útil del webhook + +{% data reusables.webhooks.watch_properties %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.watch.started }} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### workflow_dispatch + +Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en GitHub o cuando envía una solicitud de tipo `POST` a la terminal [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obtener más información, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". + +#### Disponibilidad + +- Las {% data variables.product.prodname_github_app %}s deben tener el permiso `contents` para recibir este webhook. + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.workflow_dispatch }} +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### workflow_run + +Cuando una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %} se solicita o se completa. Para obtener más información, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_run)". + +#### Disponibilidad + +- En {% data variables.product.prodname_github_app %}s con los permisos de `actions` o de `contents`. + +#### Objeto de carga útil del webhook + +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La mayoría de las cargas útiles de webhooks contienen una propiedad de `action` que contiene la actividad específica que activa el evento. | +{% data reusables.webhooks.org_desc %} +{% data reusables.webhooks.repo_desc %} +{% data reusables.webhooks.sender_desc %} + +#### Ejemplo de carga útil del webhook + +{{ webhookPayloadsForCurrentVersion.workflow_run }} +{% endif %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md new file mode 100644 index 0000000000000..228bb709a19c0 --- /dev/null +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md @@ -0,0 +1,10 @@ +--- +title: Webhooks +intro: 'Aprende a configurar, probar y asegurar los webhooks para integrarte con {% data variables.product.prodname_dotcom %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md new file mode 100644 index 0000000000000..6fd5ec9c1f1c4 --- /dev/null +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: Acerca de los debates +intro: Utiliza los debates para preguntar y responder preguntas, compartir información, hacer anuncios y moderar o participar en una conversación sobre un proyecto en {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de los debates + +Con los {% data variables.product.prodname_discussions %}, la comunidad de tu proyecto puede crear y participar en conversaciones dentro del repositorio del proyecto. Los debates fotalecen a los mantenedores del proyecto, contribuyentes y visitantes para que se reunan y logren sus metas en una ubicación centralizada, sin herramientas de terceros. + +- Comparte anuncios e información, recolecta comentarios, planea y toma decisiones +- Haz preguntas, debate y respóndelas, y marca los debates como respondidos +- Fomenta un ambiente amigable para los visitantes y contribuyentes para que se debatan las metas, el desarrollo, la administración y los flujos de trabajo + +![Pestaña de debates en un repositorio](/assets/images/help/discussions/hero.png) + +No necesitas cerrar un debate de la misma forma en que cierras una propuesta o una solicitud de cambios. + +Si un administrador de repositorio o mantenedor de proyecto habilita los debates en un repositorio, cualquiera que lo visite puede crear y participar en ellas. Los administradores del repositorio y los mantenedores del proyecto pueden administrar los debates y las categorías de los mismos en un repositorio y fijarlos para incrementar la visibilidad de éstos. Los moderadores y colaboradores pueden marcar los comentarios como respuestas, fijar debates, y convertir las propuestas en debates. Para obtener más información, consulta la sección "[Niveles de permiso en un repositorio para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". + +Para obtener más información sobre la adminsitración de debates para tu repositorio, consulta la sección "[Administrar debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". + +### Acerca de las categorías y formatos para los debates + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +Para los debates con un formato de pregunta/respuesta, un comentario individual dentro del debate puede marcarse como la respuesta a éste. {% data reusables.discussions.github-recognizes-members %} + +Para obtener más información, consulta la sección "[Administrar las categorías para los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)". + +### Mejores prácticas para las discusiones + +Como mantenedor o miembro de la comunidad, inicia un debate para hacer una pregunta o debatir información que les afecte. Para obtener más información, consulta la sección "[Colaborar con los mantenedores a través de los debates](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)". + +Participa en un debate para hacer y responder preguntas, proporcionar retroalimentación e interactuar con la comunidad del proyecto. Para obtener más información, consulta la sección "[Participar en un debate](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)". + +Puedes destacar los debates que contengan conversaciones importantes, útiles o ejemplares entre los miembros de la comunidad. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". + +{% data reusables.discussions.you-can-convert-an-issue %} Para obtener más información, consulta la sección "[Moderar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)". + +### Compartir retroalimentación + +Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_discussions %} con {% data variables.product.company_short %}. Para unirte a la conversación, consulta la sección [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### Further reading + +- "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" +- "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[Moderar comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" +- "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000000..a2130dd1cee03 --- /dev/null +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Colaborar con los mantenedores utilizando debates +shortTitle: Colaborar con los mantenedores +intro: Puedes contribuir a las metas, planes, salud y comunidad de un proyecto en {% data variables.product.product_name %} si te comunicas con los mantenedores del proyecto en un debate. +permissions: Las personas con permisos de lectura en un repositorio pueden iniciar y participar en debates dentro del mismo. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de la colaboración con los mantenedores utilizando debates + +{% data reusables.discussions.about-discussions %} Si utilizas o contribuyes con un proyecto, puedes iniciar un debate para hacer sugerencias e interactuar con los manenedores y miembros de la comunidad con respecto a tus planes, preguntas, ideas y retroalimentación. Para obtener más información, consulta la sección "[‎Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". + +{% data reusables.discussions.about-categories-and-formats %} Los administradores de repositorio y mantenedores de proyecto pueden borrar un debate. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)". + +{% data reusables.discussions.github-recognizes-members %} Estos miembros aparecen en una lista de los contribuyentes más útiles en los debates del proyecto. Conforme crezca tu proyecto, podrás otorgar permisos de acceso superiores a los miembros activos de tu comunidad. Para obtener más información, consulta la sección "[Otorgar permisos superiores a los colaboradores principales](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Contribuyentes más útiles para los debates de un proyecto](/assets/images/help/discussions/most-helpful.png) + +Para obtener más información acerca de la participación en los debates, consulta la sección "[Participar en un debate](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)". + +### Prerrequisitos + +Para colaborar con los mantenedores utilizando debates, un administrador de repositorio o mantenedor de proyecto debe habilitar los debates para el repositorio. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los debates para el repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". + +### Iniciar un debate + +{% data reusables.discussions.starting-a-discussion %} + +### Filtrar la lista de debates + +Puedes buscar debates y filtrar la lista de éstos en un repositorio. Para obtener más información, consulta la sección "[Buscar buscar debates](/github/searching-for-information-on-github/searching-discussions)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. En el campo de **Buscar todos los debates**, teclea una consulta de búsqueda. Opcionalmente, a la derecha del campo de búsqueda, da clic en un botón para filtrar aún más los resultados. ![Barra de búsqueda y botones para filtrar los debates](/assets/images/help/discussions/search-and-filter-controls.png) +1. En la lista de debates, da clic en el debate que quieras ver. ![Resultados de búsqueda para debates](/assets/images/help/discussions/search-result.png) + +### Convertir una propuesta en un debate + +{% data reusables.discussions.you-can-convert-an-issue %} Para obtener más información, consulta la sección "[Moderar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)". + +### Further reading + +- "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000000..e4fbe6b09a0db --- /dev/null +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Colaborar con tu comunidad utilizando los debates +shortTitle: Colaborar utilizando debates +intro: Recopila y debate tu proyecto con los miembros de la comunidad y con otros mantenedores. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000000..07d1a5021677d --- /dev/null +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participar en un debate +intro: Puedes conversar con la comunidad y con los mantenedores en un foro dentro del repositorio de un proyecto en {% data variables.product.product_name %}. +permissions: Las personas con permisos de lectura en un repositorio pueden participar en debates dentro del mismo. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de la perticipación en un debate + +{% data reusables.discussions.about-discussions %} Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". + +Adicionalmente a iniciar o visualizar un debate, puedes comentar como respuesta al comentario original del autor del mismo. También puedes crear un hilo de comentarios si respondes a un comentario individual que otro miembro de la comunidad haya hecho dentro del debate, y reaccionar a los comentarios con emojis. Para obtener más información acerca de las reacciones, consulta la sección "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)". + +Puedes bloquear usuarios y reportar el contenido perjudicial para mantener un ambiente placentero y seguro en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)". + +### Prerrequisitos + +Para que puedas participar en un debate, estos deben habilitarse en el repositorio. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los debates para el repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". + +### Crear un debate + +{% data reusables.discussions.starting-a-discussion %} + +### Marcar un comentario como una respuesta + +Los autores de los debates y los usuarios con el rol de clasificación o superior dentro del repositorio pueden marcar un comentario como la respuesta a un debate dentro de dicho repositorio. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} diff --git a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md new file mode 100644 index 0000000000000..d42b85c6756b0 --- /dev/null +++ b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Mejores prácticas para las conversaciones comunitarias en GitHub +shortTitle: Mejores prácticas para las conversaciones comunitarias +intro: 'Puedes utilizar los debates para hacer una lluvia de ideas con tu equipo y, en algún momento, migrar la conversación a un debate cuando estés listo para aumentar el alcance del trabajo.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Conversaciones comunitarias en {% data variables.product.prodname_discussions %} + +Ya que {% data variables.product.prodname_discussions %} constituye un foro abierto, existe la oportunidad de incorporar colaboraciones diferentes a aquellas de código en el repositorio de un proyecto y recabar retroalimentación e ideas distintas más rápidamente. Puedes ayudar llevar una conversación productiva si: + +- Haces preguntas puntuales y preguntas de seguimiento para recabar comentarios específicos +- Capturas experiencias distintas y las simplificas en puntos principales +- Abres una propuesta para que se tome una acción con base en la conversación, si es que aplica + +Para obtener más información acerca de abrir propuestas y hacer referencias cruzadas en un debate, consulta la sección [Abrir una propuesta desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". + +### Aprender más sobre las conversaciones en GitHub + +Puedes crear y participar en los debates, propuestas y solicitudes de cambio dependiendo del tipo de conversación que desees tener. + +Puedes utilizar lps {% data variables.product.prodname_discussions %} para debatir las ideas más amplias, hacer lluvias de ideas y resaltar los detalles específicos de un proyecto antes de hacer cualquier confirmación en una propuesta, la cual puede aumetar su alcance posteriormente. Los debates son útiles para los equipos si: +- Estás en la fase de descubrimiento de un proyecto y aún estás aprendiendo en qué dirección quiere ir tu equipo. +- Quieres recolectar los comentarios de una comunidad más amplia sobre un proyecto +- Quieres mantener la separación entre las correcciones de errores y las conversaciones generales + +Las propuestas son útiles para debatir detalles específicos de un proyecto como registros de errores y mejoras planificadas. Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". Las solicitudes de extracción te permiten comentar directamente en los cambios propuestos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" y "[Comentar en una solicitud de extracción](/articles/commenting-on-a-pull-request)". + +{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)". + +### Seguir los lineamientos de contribución + +Antes de que abras un debate, verifica si el repositorio tiene lineamientos de contribución. El archivo de CONTRIBUCIÓN incluye información sobre cómo el gustaría al mantenedor del repositorio que colabores con ideas para el proyecto. + +Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Pasos siguientes + +Para seguir aprendiendo sobre los {% data variables.product.prodname_discussions %} y crear uno rápidamente para tu comunidad, consulta la sección "[Guía de inicio rápido para los {% data variables.product.prodname_discussions %}](/discussions/quickstart)". + +### Further reading + +- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" +- [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderar comentarios y conversaciones](/articles/moderating-comments-and-conversations)" +- "[Escribir en {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000000..f3c14d80507fa --- /dev/null +++ b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Encontrar debates a lo largo de varios repositorios +intro: 'Puedes acceder fácilmente a todos los debates que hayas creado, o en los que hayas participado, a lo largo de varios repositorios.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Encontrar debates + +1. Ve a {% data variables.product.prodname_dotcom_the_website %}. +1. En la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %}, da clic en tu foto de perfil y luego en **Tus debates**. !["Tus debates" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Alterna entre **Creados** y **Comentados** para ver los debates que creaste o en los que has participado. + +### Further reading + +- "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" +- "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md new file mode 100644 index 0000000000000..f1e00f8c332a4 --- /dev/null +++ b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Otorgar permisos superiores a los contribuyentes principales +intro: 'Los administradores de repositorio pueden promover a cualquier miembro de la comunidad para que sea un moderador o un mantenedor.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introducción + +Los colaboradores más útiles en los últimos 30 días se resaltarán en el tablero de {% data variables.product.prodname_discussions %} con base en cuántos comentarios marcaron otros miembros de la comunidad como respuestas. Los colaboradores útiles pueden ayudar a mantener una comunidad saludable y a moderar y guiar el espacio comunitario adicionalmente al trabajo que hacen los mantenedores. + +### Paso 1: Audita los contribuyentes principales de tus debates + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compara la lista de contribuyentes con sus permisos de acceso para ver quién califica para moderar el debate. + +### Paso 2: Revisa los niveles de permiso para los debates + +Las personas con permisos de clasificación en un repositorio pueden ayudar a moderar los debates de un proyecto si marcan los comentarios como respuestas, fijar los debates que ya no son útiles o que están haciendo daño a la comunidad, y convertir las propuestas en debates cuando una idea aún se encuentra en una etapa temprana de desarrollo. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)". + +Para obtener más información sobre los niveles de permiso y los {% data variables.product.prodname_discussions %} de un repositorio, consulta la sección "[Niveles de permiso de un repositorio en una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". + +### Paso 3: Cambia los niveles de permiso para los contribuyentes principales + +Puedes cambiar los niveles de permiso de un contribuyente para darles más acceso a las herramientas que necesitan para moderar los debates de GitHub. Para cambiar los niveles de permiso de una persona o de un equipo, consulta la sección "[Administrar equipos y personas con acceso a tu repositorio](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)". + +### Paso 4: Notifica a los miembros de la comunidad sobre el acceso superior + +Cuando cambias el nivel de permiso de un colaborador, estos recibirán una notificación del cambio. diff --git a/translations/es-ES/content/discussions/guides/index.md b/translations/es-ES/content/discussions/guides/index.md new file mode 100644 index 0000000000000..fec8e05d5e5e6 --- /dev/null +++ b/translations/es-ES/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Guías de los debates +shortTitle: Guías +intro: 'Descubre las trayectorias para iniciar o aprende las mejores prácticas para participar o monitorear los debates de tu comunidad.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Iniciar con los debates + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administrar los debates + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md new file mode 100644 index 0000000000000..73218713cebd7 --- /dev/null +++ b/translations/es-ES/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: Documentación sobre los debates de GitHub +beta_product: verdadero +shortTitle: GitHub Discussions +intro: '{% data variables.product.prodname_discussions %} es un foro de comunicación colaborativa para la comunidad que circunda un proyecto de código abierto. Los miembros de la comunidad pueden hacer preguntas y proporcionar respuestas, compartir actualizaciones, tener conversaciones abiertas y dar seguimiento a las decisiones que afectan la forma de trabajar de la misma.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
    +

    Comunidades que utilizan debates

    + +
    + {% render 'discussions-community-card' for discussionsCommunityExamples as example %} +
    + {% if discussionsCommunityExamples.length > 6 %} + + {% endif %} +
    +
    {% octicon "search" width="24" %}
    +

    Lo sentimos, no hay respultados para

    +

    Parece que no tenemos un ejemplo que se adapte a tu filtro.
    Intenta con otro filtro o agrega tu ejemplo de código

    + Agrega tu comunidad {% octicon "arrow-right" %} +
    +
    +{% endif %} diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000000..447a493f200c1 --- /dev/null +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Administrar los debates para tu comunidad +shortTitle: Administrar los debates +intro: 'Puedes habilitar y configurar los debates en tu repositorio, y puedes utilizar herramientas en {% data variables.product.product_name %} para moderar las conversaciones entre los miembros de la comunidad.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000000..7dff51deefd56 --- /dev/null +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Administrar las categorías de los debates en tu repositorio +intro: Puedes categorizar los debates en tu repositorio para organizar las conversaciones para los miembros de tu comunidad, y puedes elegir un formato para cada categoría. +permissions: Los administradores de repositorio y las personas con acceso de escritura o superior en el mismo pueden habilitar los debates para éste. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de las categorías para los debates + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Cada categoría debe tener un nombre único y un emoji distintivo, y se le puede acompañar con una descripción detallada que describa su propósito. Las categorías ayudan a los mantenedores a organizar la forma en las que se archivan las conversaciones, y estas se pueden personalizar para ayudar a distinguir las categorías que son de Q&A (preguntas y respuestas) o que son conversaciones más abiertas.{% data reusables.discussions.repository-category-limit %} + +Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". + +### Categorías predeterminadas + +| Categoría | Propósito | Type | +|:------------------ |:------------------------------------------------------------------------------ |:-------------------- | +| #️⃣ General | Cualquier cosa que sea relevante para el proyecto | Debates abiertos | +| 💡Ideas | Ideas para cambiar o mejorar el proyecto | Debates abiertos | +| 🙏 Q&A | Preguntas para que responda la comunidad, con un formato de pregunta/respuesta | Pregunta y respuesta | +| 🙌 Mostrar y contar | Creaciones, experimentos, o pruebas relevantes para el proyecto | Debates abiertos | + +### Crear una categoría + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Da clic en **Categoría nueva**. ![Botón de "Categoría nueva" sobre la lista de categorías de debate para un repositorio](/assets/images/help/discussions/click-new-category-button.png) +1. Edita el emoji, título, descripción y formato del debate para la categoría. Para obtener más información sobre los formatos de debate, consulta la sección [Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". ![Emoji, título, descripción y formato de debate para la categoría nueva](/assets/images/help/discussions/edit-category-details.png) +1. Da clic en **Crear**. ![Botón de "Crear" para la categoría nueva](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editar una categoría + +Puedes editar una categoría para cambiar el emoji, título, descripción y formato de debate de la misma. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. A la derecha de la categoría en la lista, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Botón de editar a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editar el emoji, título, descripción y formato del debate para la categoría existente](/assets/images/help/discussions/edit-existing-category-details.png) +1. Haz clic en **Guardar cambios**. ![Botón de "Guardar cambios" para la categoría existente](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Borrar una categoría + +Cuando borras una categoría, {% data variables.product.product_name %} enviará todos los debates en la categoría que se borró a una categoría existente que elijas. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. A la derecha de la categoría en la lista, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Botón de cesto de basura a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-delete-for-category.png) +1. Utiliza el menú desplegable y elige una categoría nueva para cualquier debate en la categoría que estás eliminando. ![Menú desplegable para elegir una categoría nueva cuando se borra una categoría existente](/assets/images/help/discussions/choose-new-category.png) +1. Da clic en **Borrar & Mover**. ![Menú desplegable para elegir una categoría nueva cuando se borra una categoría existente](/assets/images/help/discussions/click-delete-and-move-button.png) diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md new file mode 100644 index 0000000000000..e47d4b40356d5 --- /dev/null +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Adminsitrar los debates en tu repositorio +intro: Puedes categorizar, resaltar, transferir o borrar los debates en un repositorio. +permissions: Los administradores de repositorio y las personas con acceso de escritura o superior en un repositorio pueden administrar los debates del mismo. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de la administración de los debates + +{% data reusables.discussions.about-discussions %} Para obtener más información sobre los debates, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". + +Los propietarios de la organización pueden elegir los permisos que se requieren para crear un debate en los repositorios que pertenezcan a la organización. Para obtener más información, consulta la sección "[Administrar la creación de debates para los repositorios de tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)". + +Como mantenedor de debates, puedes crear recursos comunitarios para impulsar los debates que se alinien con la meta general del proyecto y mantener así un foro abierto y amistoso para los colaboradores. El crear un código de conducta o lineamientos de contribución para que los colaboradores los sigan te ayudará a proporcionar un foro colaborativo y productivo. Para obtener más información sobre cómo crear recursos comunitarios, consulta las secciones "[Agregar un código de conducta a tu proyecto](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" y "[Configurar los lineamientos para los contribuyentes de un repositorio](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)". + +Para obtener más información sobre cómo proporcionar un debate sano, consulta la sección "[Moderar los comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)". + +### Prerrequisitos + +Para administrar los debates de un repositorio, éste deberá habilitar dicha función. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los debates para el repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". + +### Cambiar la categoría de un debate + +Puedes categorizar los debates para ayudar a que los miembros de la comunidad encuentren aquellos que tengan alguna relación. Para obtener más información, consulta el artículo "[Administrar las categorías para los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)". + +También puedes migrar un debate a una categoría diferente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra lateral derecha, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar debate fijado**. !["Fijar debate" en la barra lateral derecha del debate](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Fijar un debate + +Puedes fijar hasta cuatro debates importantes sobre la lista de debates del repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra lateral derecha, da clic en {% octicon "pin" aria-label="The pin icon" %} **Fijar debate**. !["Fijar debate" en la barra lateral derecha del debate](/assets/images/help/discussions/click-pin-discussion.png) +1. Opcionalmente, personaliza la apariencia del debate que fijaste. ![Opciones de personalización para un debate que se fijó](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Da clic en **Fijar debate**. ![Botón de "Fijar debate" debajo de las opciones de personalización para un debate fijado](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editar un debate que se fijó + +Editar un debate que se ha fijado no cambiará la categoría del mismo. Para obtener más información, consulta la sección "[Administrar las categorías para los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra lateral derecha, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar debate fijado**. !["Fijar debate" en la barra lateral derecha del debate](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Personaliza la apariencia del debate que fijaste. ![Opciones de personalización para un debate que se fijó](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Da clic en **Fijar debate**. ![Botón de "Fijar debate" debajo de las opciones de personalización para un debate fijado](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Dejar de fijar un debate + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra lateral derecha, da clic en {% octicon "pin" aria-label="The pin icon" %} **Dejar de fijar debate**. !["Dejar de fijar debate" en la barra lateral derecha del debate](/assets/images/help/discussions/click-unpin-discussion.png) +1. Lee la advertencia y luego da clic en **Dejar de fijar debate**. ![Botón de "Dejar de fijar debate" bajo advertencia en el modo](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferir un debate + +Para transferir un debate, debes tener permisos para crear debates en el repositorio a donde quieras trasnferirlo. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra laeral derecha, da clic en {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transferir debate**. !["transferir debate" en la barra lateral derecha del mismo](/assets/images/help/discussions/click-transfer-discussion.png) +1. Selecciona el menú desplegable de **Elige un repositorio** y da clic en aquél al que quieras transferir el debate. ![Menú desplegable de "Elige un repositorio", campo de búsqueda de "Encuentra un repositorio", y repositorio en la lista](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Da clic en **Transferir debate**. ![Botón de "Transferir debate"](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Borrar un debate + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. En la barra lateral, da clic en {% octicon "trash" aria-label="The trash arrow icon" %} **Borrar debate**. !["Borrar debate" en la barra lateral derecha del mismo](/assets/images/help/discussions/click-delete-discussion.png) +1. Lee la advertencia y luego da clic en **Borrar este debate**. ![Botón de "Borrar este debate" bajo advertencia en el modo](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Convertir propuestas con base en las etiquetas + +Puedes convertir todas las propuestas con la misma etiqueta en debates, por lote. Las propuestas subsecuentes que tengan esta etiqueta también se convertirán automáticamente en el debate y categoría que configures. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Junto a la etiqueta que quieras convertir en una propuesta, da clic en **Convertir propuestas**. +1. Selecciona el menú desplegable de **Elige una categoría** y da clic en aquella que quieras para tu debate. +1. Da clic en **Entiendo, convertir esta propuesta en debate**. diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000000..e5d277a3e7b47 --- /dev/null +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderar los debates +intro: 'Puedes promover una colaboración sana si marcas los comentarios como respuestas, bloqueas o desbloqueas debates, y conviertes propuestas en debates. y editar o borrar comentarios, debates y categorías que no concuerden con el código de conducta de tu comunidad para los debates.' +permissions: Las personas con acceso de clasificación en un repositorio pueden moderar los debates del mismo. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de moderar los debates + +{% data reusables.discussions.about-discussions %} Si tienes permisos de clasificación en un repositorio, puedes ayudar a moderar el debate de un proyecto si marcas los comentarios como respuestas, bloqueas debates que ya no sean útiles o que dañen a la comunidad, y conviertes propuestas en debates cuando una idea aún se encuentre en una etapa temprana de desarrollo. + +### Marcar un comentario como una respuesta + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Bloquear debates + +Es adecuado bloquear una conversación cuando ésta no sea constructiva o viole el código de conducta de tu comunidad o los [Lineamientos comunitarios](/github/site-policy/github-community-guidelines) de {% data variables.product.prodname_dotcom %}. También puedes bloquear una conversación para prevenir que se hagan comentarios en un debate que quieres utilizar como un anuncio para la comunidad. Cuando bloqueas una conversación, las personas con acceso de escritura en el repositorio aún podrán comentar sobre el debate. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. En la lista de debates, da clic en aquél que quieras bloquear. ![Bloquear debate](/assets/images/help/discussions/unanswered-discussion.png) +1. En el margen derecho de un debate, da clic en **Bloquear conversación**. +1. Lee la información sobre bloquear los debates y da clic en **Bloquear conversación en este debate**. +1. Cuando estés listo para desbloquear la conversación, da clic en **Desbloquear conversación** y luego en **Desbloquear conversación en este debate**. + +### Convertir una propuesta en un debate + +Cuando conviertes una propuesta en un debate, ésta se creará automáticamente utilizando el contenido de la propuesta. Las personas con acceso de escritura en un repositorio pueden convertir propeustas por lote con base en las etiquetas. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. En la lista de propuestas, da clic en aquella que quieras convertir. +1. En el margen derecho de la propuesta, da clic en **Convertir en debate**. +1. Selecciona el menú desplegable de **Elige una categoría** y da clic en aquella que quieras para tu debate. +1. Da clic en **Entiendo, convertir esta propuesta en debate**. diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md new file mode 100644 index 0000000000000..d4c69465af6a3 --- /dev/null +++ b/translations/es-ES/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Guía de inicio rápido para los debates de GitHub +intro: 'Habilita los {% data variables.product.prodname_discussions %} en un repositorio existente e inicia conversaciones con tu comunidad.' +allowTitleToDifferFromFilename: verdadero +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introducción + +{% data variables.product.prodname_discussions %} es un foro de comunicación colaborativa para la comunidad que circunda un proyecto de código abierto. Se pretende que los debates se lleven a cabo para las conversaciones que necesitan ser transparentes y de fácil acceso pero que no necesitan rastrearse en un tablero de proyecto y que no estén relacionadas con el código, a diferencia de las propuestas. Los debates habilitan las conversaciones abiertas y fluídas en un foro público. + +Los debates proporcionan un espacio para que existan conversaciones colaborativas al conectar y asignar un área más centralizada para conectarse y encontrar información. + +### Habilitar los {% data variables.product.prodname_discussions %} en tu repositorio + +Los propietarios de los repositoriso con acceso de escritura pueden habilitar los {% data variables.product.prodname_discussions %} para una comunidad en sus repositorios públicos. + +Cuando habilitas un {% data variables.product.prodname_discussions %} por primera vez, se te invitará a configurar una publicación de bienvenida. + +{% data reusables.repositories.navigate-to-repo %} +1. Debajo de tu nombre de repositorio, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Botón de configuración pública](/assets/images/help/discussions/public-repo-settings.png) +1. Debajo de "Características", da clic en **Configurar debates**. ![Botón de configurar un debate debajo de "Características" para habilitar o inhabilitar los debates para un repositorio](/assets/images/help/discussions/setup-discussions-button.png) +1. Debajo de "Iniciar un debate nuevo" edita la plantilla para que se apegue con los recursos y el tono que quieras configurar para tu comunidad. +1. Da clic en **Iniciar debate**. ![Botón de "Iniciar debate"](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Aceptar contribuyentes en tus debates + +Puedes invitar a tu comunidad y presentarles una forma nueva de comunicarse en un repositorio si creas una publicación de bienvenida y la fijas en tu página de {% data variables.product.prodname_discussions %}. El fijar y bloquear los debates ayuda a que las personas sepan si una publicación se hizo a manera de anuncio. Puedes utilizar los anuncios como una forma de vincular a las personas con más recursos y ofrecerles orientación para abrir debates en tu comunidad. Para obtener más información sobre cómo fijar un debate, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". + + +### Configurar los lineamientos comunitarios para los contribuyentes + +Puedes configurar lineamientos de contribución para motivar a los colaboradores para que tengan conversaciones significativas y útiles que sean relevantes para el repositorio. También puedes actualizar el archivo de README del repositorio para comunicar tus expectativas de cuándo deberían los colaboradores abrir una propuesta o un debate. + +Para obtener más información sobre proporcionar lineamientos para tu proyecto, consulta las secciones "[Agregar un código de conducta a tu proyecto](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" y "[Configurar tu proyecto para que tegan contribuciones sanas](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)". + +### Crear un debate nuevo + +Cualquiera con acceso a un repositorio puede crear un debate. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizar los debates en tus categorías relevantes + +Los propietarios de los repositorios y las personas con acceso de escritura pueden crear categorías nuevas para mantener los debates organizados. Los colaboradores que participen y creen debates nuevos pueden agruparlos en las categorías existentes más relevantes. Los debates también pueden volver a categorizarse después de su creación. Para obtener más información, consulta la sección "[Administrar las categorías para los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promover las conversaciones sanas + +Las personas con permisos de escritura en un repositorio pueden ayudar a que las conversaciones importantes emerjan fijando los debates, borrando aquellos que ya no sean útiles o que dañen a la comunidad, y transfiriendo aquellos a repositorios más relevantes que pertenezcan a la organización. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". + +Las personas con permisos de clasificación en un repositorio pueden ayudar a moderar los debates de un proyecto si marcan los comentarios como respuestas, fijar los debates que ya no son útiles o que están haciendo daño a la comunidad, y convertir las propuestas en debates cuando una idea aún se encuentra en una etapa temprana de desarrollo. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)". + +### Pasos siguientes + +Una vez que exista una ruta clara para ampliar el alcance del trabajo y migrar una idea desde un concepto hacia la realidad, puedes crear una propuesta y comenzar a rastrear tu progreso. Para obtener más información sobre cómo crear una propuesta a partir de un debate, consulta la sección "[Moderar debates](/discussions/managing-discussions-for-your-community/moderating-discussions)". diff --git a/translations/es-ES/content/education/guides.md b/translations/es-ES/content/education/guides.md new file mode 100644 index 0000000000000..683d83afc241e --- /dev/null +++ b/translations/es-ES/content/education/guides.md @@ -0,0 +1,45 @@ +--- +title: Guías de GitHub Education +intro: 'Estas guías de {% data variables.product.prodname_education %} te ayudan a enseñar y aprender tanto {% data variables.product.product_name %} como desarrollo de software.' +allowTitleToDifferFromFilename: verdadero +versions: + free-pro-team: '*' +--- + +### Inicia con {% data variables.product.product_name %} + +Los maestros, alumnos e investigadores pueden utilizar herramientas de {% data variables.product.product_name %} para enriquecer un currículum de desarrollo de software y desarrollar habilidades colaborativas para el mundo real. + +- [Regístrate para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account) +- [Guía de inicio rápido de Git y {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/quickstart) +- [Postularse para un descuento de investigador o educador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Aplicar un paquete de desarrollo para alumnos](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Ejecuta un curso de desarrollo de software con {% data variables.product.company_short %} + +Administra un aula, asigna y revisa el trabajo de tus alumnos y enseña a la nueva generación de desarrolladores de software con {% data variables.product.prodname_classroom %}. + +- [Puntos básicos para configurar {% data variables.product.prodname_classroom %} ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) +- [Administrar aulas](/education/manage-coursework-with-github-classroom/manage-classrooms) +- [Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) +- [Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment) +- [Crear una tarea desde un repositorio de plantilla](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository) +- [Deja retroalimentación con solicitudes de cambios](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests) +- [Utiliza las calificaciones automáticas](/education/manage-coursework-with-github-classroom/use-autograding) + +### Aprende a desarrollar software + +Incorpora a {% data variables.product.prodname_dotcom %} en tu educación y utiliza las mismas herramientas que los profesionales. + +- [Recursos de aprendizaje para Git y {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/git-and-github-learning-resources) +- [Utiliza {% data variables.product.prodname_dotcom %} para tu trabajo escolar](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [Prueba {% data variables.product.prodname_desktop %}](/desktop) +- [Prueba {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) + +### Contribuye con la comunidad + +Participa en la comunidad, obtén capacitación de {% data variables.product.company_short %} y aprende o enseña nuevas habilidades. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [Acerca de Expertos en campus](/education/teach-and-learn-with-github-education/about-campus-experts) +- [Acerca de Asesores de campus](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/es-ES/content/education/index.md b/translations/es-ES/content/education/index.md new file mode 100644 index 0000000000000..88b8be6bac98b --- /dev/null +++ b/translations/es-ES/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: Documentación de GitHub Education +shortTitle: Educación +intro: "{% data variables.product.prodname_education %} te permite enseñar o aprender sobre desarrollo de software con las herramientas y el apoyo de la plataforma y la comunidad de {% data variables.product.company_short %}." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Intenta hacer algo nuevo en el día local del Hack: Aprende' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Educación remota: Crear una comunidad mediante las experiencias compartidas' + date: '24-09-2020' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Educación remota: Una serie de mejores prácticas para las comunidades de campus en línea' + date: '10-09-2020' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Bienvenido a la clase de inauguración de MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000000..f69f99798475a --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: Acerca de utilizar MakeCode Arcade con GitHub Classroom +shortTitle: Acerca de utilizar MakeCode Arcade +intro: Puedes configurar a MakeCode Arcade como el IDE en línea para las tareas en {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### Acerca de MakeCode Arcade + +MakeCode Arcade es un ambiente de desarrollo integrado (IDE, por sus siglas en inglés) para desarrollar juegos retro de arcade utilizando una programación de arrastre de bloques y JavaScript. Con MakeCode Arcade, los alumnos pueden escribir, editar, ejecutar, probar y depurar código desde un buscador. Para obtener más información sobre los IDE en línea y sobre {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE en línea](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)". + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +La primera vez que el alumno da clic en el botón para visitar a MakeCode Arcade, éste deberá ingresar en MakeCode Arcade con sus credenciales de {% data variables.product.product_name %}. Después de ingresar, el alumno tendrá acceso a un ambiente de desarrollo que contenga el código de un repositorio de tareas, completamente configurado en makeCode Arcade. + +Para obtener más información sobre cómo trabajar en MakeCode Arcade, consulta el [Recorrido de MakeCode Arcade](https://arcade.makecode.com/ide-tour) y la [documentación](https://arcade.makecode.com/docs) en el sitio web de MakeCode Arcade. + +MakeCode Arcade no escompatible con edición de multijugadores para las tareas grupales. En vez de esto, los alumnos pueden colaborar con las características de Git y de {% data variables.product.product_name %} como las ramas y las solicitudes de cambios. + +### Acerca de la emissión de tareas con MakeCode Arcade + +Predeterminadamente, MakeCode Arcade se encuentra configurado para subir las tareas al repositorio designado para ellas en {% data variables.product.product_location %}. Después de que se haya progresado en una tarea de MakeCode Arcade, los alumnos deberán subir los cambios a {% data variables.product.product_location %} utilizando el {% octicon "arrow-up" aria-label="The up arrow icon" %} de la {% octicon "mark-github" aria-label="The GitHub mark" %} al final de la pantalla. + +![Funcionalidad de control de versiones de MakeCode Arcade](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### Further reading + +- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000000..7b64e53af7494 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Acerca de utilizar Repl.it con GitHub Clasroom +shortTitle: Acerca de utilizar Repl.it +intro: Puedes configurar a Repl.it como el ambiente de desarrollo integrado (IDE, por sus siglas en inglés) en línea para las tareas de {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### Acerca de Repl.it + +Repl.it es un ambiente de desarrollo integrado (IDE) compatible con diversos lenguajes de programación. Con Repl.it, los alumnos pueden escribir, editar, ejecutar, probar y depurar el código en un buscador. Para obtener más información sobre los IDE en línea y sobre {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE en línea](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)". + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +La primera vez que el alumno d aclic en el botón para visitar Repl.it, deberá ingresar con sus credenciales de {% data variables.product.product_name %}. Después de ingresar, el alumno deberá acceder al ambiente de desarrollo que contiene el código del repositorio de tareas, completamente configurado en Repl.it. + +Para obtener más información sobre cómo trabajar con Repl.it, consulta la [Guía de acceso rápido de Repl.it](https://docs.repl.it/misc/quick-start#the-repl-environment). + +Para las tareas grupales, los alumnos pueden utilizar Repl.it Multiplayer para trabajar en colaboración. Para obtener más información, consulta el sitio web de [Repl.it Multiplayer](https://repl.it/site/multiplayer). + +### Acerca de emitir tareas con Repl.it + +Predeterminadamente, Repl.it se configura para subir información al repositorio de tareas en {% data variables.product.product_location %}. Después de progresar en una tarea con Repl.it, los alumnos deberán subir los cambios a {% data variables.product.product_location %} utilizando la funcionalidad de control de versiones en la barra lateral izquierda. + +![Funcionalidad de control de versiones de Repl.it](/assets/images/help/classroom/ide-replit-version-control-button.png) + +Para obtener más información sobre cómo utilizar Git en Repl.it, consulta el [Tutorial de Repl.it + Git](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) en el sitio web de Repl.it. + +### Further reading + +- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000000..19a519d3fcfaa --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Conceptos básicos para configurar GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Aprende a configurar tu aula, administrar las tareas y configurar la automatización para eficientizar el tiempo. +versions: + free-pro-team: '*' +--- + +### Videos sobre {% data variables.product.prodname_classroom %} + +Puedes ver varios videotutoriales sobre cómo configurar y utilizar {% data variables.product.prodname_classroom %}. Para ver todos los videos como parte de una lista de reproducción contínua, consulta la [Guía de inicio de {% data variables.product.prodname_classroom %}](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) en YouTube. + +Para obtener más información sobre la terminología de {% data variables.product.prodname_classroom %}, consulta el [Golsario](/education/manage-coursework-with-github-classroom/glossary)". + +1. Iniciar{% octicon "link-external" aria-label="The external link icon" %} +2. Agregar tu registro de alumno{% octicon "link-external" aria-label="The external link icon" %} +3. Crear tareas + - Crear una tarea utilizando un repositorio de {% data variables.product.prodname_dotcom %} {% octicon "link-external" aria-label="The external link icon" %} + - Crear una tarea utilizando Microsoft MakeCode como tu IDE en línea {% octicon "link-external" aria-label="The external link icon" %} + - Crear una tarea utilizando Repl.it como tu IDE en línea {% octicon "link-external" aria-label="The external link icon" %} +4. Cómo completan las tareas los alumnos {% octicon "link-external" aria-label="The external link icon" %} +5. Cómo revisan las tareas los maestros {% octicon "link-external" aria-label="The external link icon" %} +6. Crear tareas grupales {% octicon "link-external" aria-label="The external link icon" %} +7. Pasos siguientes para iniciar {% octicon "link-external" aria-label="The external link icon" %} +8. Herramientas de {% data variables.product.prodname_dotcom %} para los maestros {% octicon "link-external" aria-label="The external link icon" %} + +### Pasos siguientes + +Para obtener más información sobre cómo dar clases con {% data variables.product.prodname_classroom %}, consulta la sección "[Dar clases con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)". + +### Further reading + +- "[Aprende y da clases con {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000000..78f513ff3a8c2 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configura los ajustes predeterminados para los repositorios de tareas +shortTitle: Configuración predeterminada para repositorios de tareas +intro: Puedes utilizar la app de configuración de Probot para configurar los ajustes predeterminados de los repositorios que cree {% data variables.product.prodname_classroom %} para una tarea. +permissions: Los propietarios de organizaciones pueden configurar los ajustes predeterminados para los repositorios de tareas si instalan una {% data variables.product.prodname_github_app %} para la organización. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### Acerca de la configuración de ajustes predeterminados para los repositorios de tareas + +{% data variables.product.prodname_classroom %} crea un repositorio que pertenece a cada alumno o equipo que acepte una tarea. El repositorio pertenecerá a la organización que utilizas con {% data variables.product.prodname_classroom %}. Los repositorios de tareas pueden estar vacíos, o puedes utilizar un repositorio de plantilla. Para obtener más información, consulta la sección "[Crear una tarea desde un repositorio de plantilla](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)". + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +Con la app de ajustes de Probot, puedes crear un archivo que se llame _.github/settings.yml_ en un repositorio que contenga una lista de ajustes para el mismo, y luego instalar una {% data variables.product.prodname_github_app %} para tu organización, la cual aplique automáticamente los ajustes al repositorio. + +Puedes incluir un _.github/settings.yml_ en un repositorio de plantilla, el cual utilices para una tarea en {% data variables.product.prodname_classroom %}. Cuando una persona o un equipo acepta la tarea, {% data variables.product.prodname_classroom %} creará el repositorio para ésta, y la app de ajustes aplicará automáticamente esta configuración desde _.github/settings.yml_. + +Probot es un proyecto, marco de trabajo y colección de apps gratuitas para automatizar a {% data variables.product.product_name %}. Una app de Probot puede escuchar los eventos de los repositorios, como la creación de confirmaciones, comentarios y propuestas nuevos, así como responder automáticamente al evento. + +Para obtener más información, consulta el "[Sitio web de Probot](https://probot.github.io) y el [Sitio web de la app de ajustes](https://probot.github.io/apps/settings/). Para obtener más información acerca de las {% data variables.product.prodname_github_apps %}, consulta la sección "[Acerca de las apps](/developers/apps/about-apps)". + +### Agregar la app de ajustes a tu organización + +Después de que instalas la app de ajustes de Probot para tu organización, ésta aplicará la configuración que definiste en el _.github/settings.yml_ en cualquier repositorio de tu organización, incluyendo los repositorios de tareas nuevos que cree {% data variables.product.prodname_classroom %}. + +1. Navega a la [página de la app de ajustes](https://github.com/apps/settings). +1. Da clic en **Instalar** y luego en la organización que utilizas para {% data variables.product.prodname_classroom %}. Proporciona acceso total a la app para todos los repositorios que pertenezcan a la organización. ![Instalar la app de ajustes de Probot](/assets/images/help/classroom/probot-settings.gif) + +### Configurar los ajustes predeterminados para un repositorio de tareas + +1. Crea un repositorio de plantilla que contenga un archivo _.github/settings.yml_. Para obtener una lista completa de ajustes, consulta el [README](https://github.com/probot/settings#github-settings) del reposiotorio `probot/settings`. Para obtener más información sobre cómo utilizar un repositorio de plantilla para el código inicial en {% data variables.product.prodname_classroom %}, consulta la sección "[Crear una tarea desde un repositorio de plantilla](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)". + + {% warning %} + + **Advertencia:** No definas `collaborators` en el archivo _.github/settings.yml_ de tu repositorio de tareas. {% data variables.product.prodname_classroom %} otorgará automáticamente a los maestros y asistentes de éstos el acceso a los repositorios de tareas. + + {% endwarning %} + +1. Crea una tarea utilizando el repositorio de plantilla que contiene el _.github/settings.yml_ como código inicial. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +La app de ajustes de Probot para tu organización aplicará ahora los ajustes que definas en _.github/settings.yml_ dentro del repositorio de plantilla para todos los repositorios de tareas que cree {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} para un alumno o equipo. + +### Further reading + +- [Apps de Probot](https://probot.github.io/apps/) +- [Documentación de Probot](https://probot.github.io/docs/) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000000..e3051c6a9b391 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Conectar un sistema de administración de aprendizaje a GitHub Classroom +intro: Puedes configurar un sistema de administración de aprendizaje (LMS) que cumpla con LTI para conectarte a {% data variables.product.prodname_classroom %} y que puedas importar un registro de alumno para tu aula. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### Acerca de la configuración de tu LMS + +Puedes conectar un sistema de administración de aprendizaje (LMS) a {% data variables.product.prodname_classroom %} y {% data variables.product.prodname_classroom %} puede importar los identificadores de un registro de alumno desde éste. Para conectar tu LMS a {% data variables.product.prodname_classroom %}, debes ingresar sus credenciales de configuración en éste. + +### Prerrequisitos + +Para configurar un LMS para que se conecte con {% data variables.product.prodname_classroom %}, primero debes crear un aula. Para obtener más información, consulta la sección "[Administrar las aulas](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)". + +### LMS compatibles + +{% data variables.product.prodname_classroom %} es compatible conla importación de datos de registros de alumnos desde los LMS que implementen estándares de Interoperabilidad de Herramientas de Aprendizaje (LTI). + +- LTI versión 1.0 o 1.1 +- Aprovisionamiento de Roles y Nombres de LTI 1.X + +Utilizar LTI ayuda a mantener tu información segura y protegida. LTI es un protocolo estándar de la industria y GitHub Classroom lo utiliza con una certificación del Consorcio de Aprendizaje Global para el Sistema de Gestión Instruccional (IMS). Para obtener más información, consulta la [interoperabilidad de herramientas para el aprendizaje](https://www.imsglobal.org/activity/learning-tools-interoperability) y la sección [Acerca del Consorcio de Aprendizaje Global del IMS](http://www.imsglobal.org/aboutims.html) en el sitio web del Consorcio de Aprendizaje Global del IMS. + +{% data variables.product.company_short %} ha probado la importación de datos de registro de alumnos desde los siguientes LMS hacia {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Actualmente, {% data variables.product.prodname_classroom %} no es compatible para importar datos de registro de alumnos desde Blackboard o Brightspace + +### Generar credenciales de configuración para tu aula + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Si tu aula ya tiene un registro de alumnos, puedes ya sea actualizarlo o borrarlo y crear uno nuevo. + - Para obtener más información sobre borrar y crear un registro de alumnos, consulta las secciones "[Borrar un registro de alumnos para un aula](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" y "[Crear un registro de alumnos para tu aula](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)". + - Para obtener más información acerca de cómo actualizar un registro de alumnos, consulta la sección "[Agregar alumnos al registro de alumnos de tu aula](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)". +1. En la lista de LMS, da clic en el tuyo. Si tu LMS no es compatible, da clic en **Otro LMS**. ![Lista de LMS](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Lee sobre cómo conectar tu LMS y luego da clic en **Conectar al _LMS_**. +1. Copia la "Llave de consumidor", "Secreto compartido", y "URL de lanzamiento" para la conexión al aula. ![Copiar credenciales](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configurar un LMS genérico + +Debes configurar los ajustes de privacidad para que tu LMS permita que las herramientas externas reciban información del registro de alumnos. + +1. Navega a tu LMS. +1. Configura una herramienta externa. +1. Proporciona las credenciales de configuración que generaste en {% data variables.product.prodname_classroom %}. + - Llave de consumidor + - Secreto compartido + - URL de lanzamiento (a menudo se le llama "URL de herramienta" o similar) + +### Configurar Canvas + +Puedes configurar {% data variables.product.prodname_classroom %} como una app externa para que Canvas importe los datos de la lista de alumnos a tu aula. Para obtener más información acerca de Canvas, consulta el [Sitio web de Canvas](https://www.instructure.com/canvas/). + +1. Ingresa en [Canvas](https://www.instructure.com/canvas/#login). +1. Selecciona el curso de Canvas que quieras integrar con {% data variables.product.prodname_classroom %}. +1. En la barra lateral izquierda, da clic en **Configuración**. +1. Da clic en la pestaña **Apps**. +1. Da clic en **Ver configuraciones de la app**. +1. Da clic en **+App**. +1. Selecciona el menú desplegable de **Tipo de configuración** y daclic en **Por URL**. +1. Pega las credenciales deconfiguración desde {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Generar credenciales de configuración para tu aula](#generating-configuration-credentials-for-your-classroom)". + + | Campo en la configuración de la app de Canvas | Valor o ajuste | + |:--------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------- | + | **Llave de consumidor** | Llave de consumidor de {% data variables.product.prodname_classroom %} + | **Secreto compartido** | Secreto compartido de {% data variables.product.prodname_classroom %} + | **Permitir que esta herramienta acceda a los nombres de IMS y al servicio de aprovisionamiento de roles** | Habilitado | + | **URL de configuración** | URL de lanzamiento de {% data variables.product.prodname_classroom %} + + {% note %} + + **Nota**: Si no ves una casilla de verificación en Canvas que lleve la etiqueta "Permitir que esta herramienta acceda a los nombres de IMS y al servicio de aprovisionamiento de roles", entonces tu administrador de Canvas debe contactar a soporte de Canvas para habilitar la configuración de servicios de membrecía para tu cuenta de Canvas. Si no se habilita esta característica, no podrás sincronizar el registro de alumnos desde Canvas. Para obtener más información, consulta la sección [¿Cómo contacto al soporte de Canvas?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) en el sitio web de Canvas. + + {% endnote %} + +1. Haz clic en **Submit** (enviar). +1. En la barra lateral izquierda, da clic en **Principal**. +1. Para solicitar a Canvas que envíe un correo electrónico de confirmación, en la barra lateral izquierda, da clic en **GitHub Classroom**. Sigue las instrucciones en el correo electrónico para concluir la vinculación de {% data variables.product.prodname_classroom %}. + +### Configurar Moodle + +Puedes configurar a {% data variables.product.prodname_classroom %} como una actividad para Moodle para importar datos del registro de alumnos a tu aula. Para obtener más información acerca de Moodle, consulta el [Sitio web de Moodle](https://moodle.org). + +Debes utilizar Moodle versión 3.0 o superior. + +1. Inicia sesión en [Moodle](https://moodle.org/login/index.php). +1. Selecciona el curso de Moodle que quieres integrar con {% data variables.product.prodname_classroom %}. +1. Da clic en **Activar la edición**. +1. Da clic en **Agregar una actividad o recurso** en donde quieras que esté disponible {% data variables.product.prodname_classroom %} en Moodle. +1. Elige **Herramienta externa** y da clic en **Agregar**. +1. En el campo de "Nombre de actividad", teclea "GitHub Classroom". +1. En el campo de **Herramienta preconfigurada**, a la derecha del menú desplegable, da clic en **+**. +1. Debajo de "Configuración de herramienta externa", pega las credenciales de configuración de {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Generar credenciales de configuración para tu aula](#generating-configuration-credentials-for-your-classroom)". + + | Campo en la configuración de la app de Moodle | Valor o ajuste | + |:--------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Nombre de la herramienta** | {% data variables.product.prodname_classroom %} - _TU NOMBRE DE AULA_

    **Nota**: Puedes utilizar cualquier nombre, pero te sugerimos este valor para tener más claridad. | + | **URL de la herramienta** | URL de lanzamiento de {% data variables.product.prodname_classroom %} + | **Versión de LTI** | LTI 1.0/1.1 | + | **Contenedor de lanzamiento predeterminado** | Ventana nueva | + | **Llave de consumidor** | Llave de consumidor de {% data variables.product.prodname_classroom %} + | **Secreto compartido** | Secreto compartido de {% data variables.product.prodname_classroom %} + +1. Desplázate y da clic en **Servicios**. +1. A la derecha de "Nombres de LTI de IMS y Aprovisionamiento de Roles", selecciona el menú desplegable y da clic en **Utilizar este servicio para recuperar la información de los miembros de acuerdo con la configuración de seguridad**. +1. Desplázate y da clic en **Privacidad**. +1. A la derecha de **Compartir el nombre del lanzador con la herramienta** y **Compartir el correo electrónico del lanzador con la herramienta**, selecciona los menús desplegables para dar clic en **Siempre**. +1. En la parte inferior de la página, da clic en **Guardar cambios**. +1. En el menú de **Preconfigurar herramienta** da clic en **GitHub Classroom - _TU NOMBRE DE AULA_**. +1. Debajo de "Configuración común de módulo", a la derecha de "Disponibilidad", selecciona el menú desplegable y da clic en **Ocultar para los alumnos**. +1. En la parte inferior de la página, da clic en **Guardar y regresar al curso**. +1. Navega a donde sea que elijas mostrar tu {% data variables.product.prodname_classroom %} y da dlic en la actividad {% data variables.product.prodname_classroom %}. + +### Importar un registro de alumnos desde tu LMS + +Para obtener más información acerca de importar el registro de alumnos de tu LMS en {% data variables.product.prodname_classroom %}, consulta la sección "[Administrar aulas](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)". + +### Desconectar tu LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Debajo de "Conectar a un sistema de administración de aprendizaje (LMS)", da clic en **Configuración de conexión**. ![Enlace de "Configuración de conexión " en los ajustes de aula](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Debajo de "Borrar la conexión con tu sistema de administración de aprendizaje", da clic en **Desconectarse de tu sistema de administración de aprendizaje**. ![Botón de "Desconectarse de tu sistema de administración de aprendizaje" en los ajustes de conexión para el aula](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md new file mode 100644 index 0000000000000..b19eccf512d24 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Crear una tarea de grupo +intro: 'Puedes crear una tarea colaborativa para que los equipos de alumnos participen en tu curso.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### Acerca de las tareas de grupo + +{% data reusables.classroom.assignments-group-definition %} Los alumnos pueden trabajar en conjunto en las tareas de grupo dentro de un repositorio compartido, como un equipo de desarrolladores profesionales. + +Cuando un alumno acepta una tarea grupal, los alumnos pueden crear un equipo nuevo o unirse a uno existente. {% data variables.product.prodname_classroom %} guarda los equipos para una tarea como un conjunto. Puedes nombrar el conjunto de equipos para una tarea específica cuando creas dicha tarea y puedes reutilizar ese conjunto de equipos para una tarea más grande. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +Puedes decidir cuántos equipos puede tener una tarea y cuántos miembros puede tener cada equipo. Cada equipo que crea un alumno para una tarea constituye un equipo dentro de tu organización en {% data variables.product.product_name %}. La visibilidad del equipo es secreta. Los equipos que crees en {% data variables.product.product_name %} no aparecerán en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta "[Acerca de equipos](/github/setting-up-and-managing-organizations-and-teams/about-teams)." + +Para ver un video demostrativo de la creación de una tarea de grupo, consulta la sección "[Conceptos básicos para configurar un {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". + +### Prerrequisitos + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Crear una tarea + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Configurar lo básico para una tarea + +Nombra tu tarea, decide si quires asignarle una fecha límite, definir equipos o elegir la visibilidad de los repositorios de la misma. + +- [Nombrar una tarea](#naming-an-assignment) +- [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment) +- [Elegir un tipo de tarea](#choosing-an-assignment-type) +- [Definir los equipos para una tarea](#defining-teams-for-an-assignment) +- [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories) + +#### Nombrar una tarea + +En las tareas grupales, {% data variables.product.prodname_classroom %} nombra a los repositorios de acuerdo con el prefijo de los mismos y el nombre del equipo. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras la tarea "assignment-1" y el nombre del equipo en {% data variables.product.product_name %} es "student-team", el nombre del repositorio de la tarea para los miembros del equipo será `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Asignar una fecha límita para una tarea + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Elegir un tipo de tarea + +Debajo de "Tarea individual o grupal", selecciona el menú desplegable y daclic en **Tarea grupal**. No puedes cambiar el tipo de tarea después de crearla. Si prefieres crear una tarea individual, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)". + +#### Definir los equipos para una tarea + +Si ya creaste una tarea grupal para el aula, puedes reutilizar un conjunto de equipos para la tarea nueva. Para crear un conjunto nuevo con los equipos que crean tus alumnos para la tarea, teclea el nombre de dicho conjunto. Opcionalmente, teclea la cantidad máxima de miembros de los equipos y el total de los equipos. + +{% tip %} + +**Tips**: + +- Te recomendamos incluir detalles sobre el conjunto de equipos en el nombre de dicho conjunto. Por ejemplo, si quieres utilizar un conjunto de equipos en un segmente, nómbralo como la tarea. Si quieres reutilizar el conjunto a lo largo de un semesre o curso, nombra el conjunto como el semestre o curso. + +- Si te gustaría asignar alumnos a un equipo específico, proporciónales un nombre de equipo y una lista de mimebros. + +{% endtip %} + +![Parámetros para los equipos que participan en una tarea grupal](/assets/images/help/classroom/assignments-define-teams.png) + +#### Elegir un tipo de visibilidad para los repositorios de la tarea + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Agergar un código de inicio y configurar un ambiente de desarrollo + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Elegir un repositorio de plantilla](#choosing-a-template-repository) +- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Elegir un repositorio de plantilla + +Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada equipo que cree el alumno. {% data reusables.classroom.you-can-choose-a-template-repository %} Para obener más información sobre los repositorios de plantilla, consulta la sección "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)". + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Elegir un ambiente de desarrollo integrado (IDE) + +{% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Proporcionar retroalimentación + +Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el equipo. + +- [Probar las tareas automáticamente](#testing-assignments-automatically) +- [Prevenir que se hagan cambios en los archivos importantes](#preventing-changes-to-important-files) +- [Crear una solicitud de cambios para retroalimentación](#creating-a-pull-request-for-feedback) + +#### Probar las tareas automáticamente + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Prevenir que se hagan cambios en los archivos importantes + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Crear una solicitud de cambios para retroalimentación + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Invitar a los alumnos a una tarea + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +Puedes ver los equipos que están trabajando o que han emitido una tarea en la pestaña de **Equipos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %} + +
    + Tarea grupal +
    + +### Pasos siguientes + +- Después de que creas una tarea y de que tus alumnos forme equipos, los miembros de dichos equipos pueden comenzar a trabajar en la tarea utilizando las características de Git y de {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el equipo pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Crear, clonar y archivar repositorios](/github/creating-cloning-and-archiving-repositories)", "[Utilizar Git](/github/using-git)", y "[Colaborar con las propeustas y solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests)", así como el curso gratuito sobre [administrar conflictos de fusión](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}. + +- Cuando un equipo termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y visualizaciones del mismo para entender mejor cómo colaboró el equipo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". + +- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para obtener más información, consulta la sección "[Comentar en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Abrir una propuesta desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obtener más información sobre cómo crear respuestas guardadas para proporcionar retroalimentación a los errores comunes, consulta la sección "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)". + +### Further reading + +- "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Utilizar equipos existentes en tareas grupales](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) en la comunidad de {% data variables.product.prodname_education %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000000..bc675f17182b7 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Crear una tarea desde un repositorio de plantilla +intro: Puedes crear una tarea desde un repositorio de plantilla para proporcionar a tus alumnos código inicial, documentación y otros recursos. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +Puedes utilizar un repositorio de plantilla en {% data variables.product.product_name %} como el código inicial de una tarea en {% data variables.product.prodname_classroom %}. Tu repositorio de plantilla puede contener código modelo, documentación y otros recursos para tus alumnos. Para obtener más información, consulta "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)". + +Para utilizar el repositorio de plantilla para tu tarea, éste debe pertenecer a tu organización, o su visibilidad debe ser pública. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} Para obtener más información, consulta la sección "[Configurar los ajustes predeterminados para los repositorios de las tareas](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)". + +### Further reading + +- "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" +- "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000000..8880a786501ed --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Crear una tarea individual +intro: Puedes crear una tarea individual para que los alumnos de tu curso la completen individualmente. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### Acerca de las tareas individuales + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +Para ver un video demostrativo de la creación de una tarea individual, consulta la sección "[Conceptos básicos para configurar un {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". + +### Prerrequisitos + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Crear una tarea + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Configurar lo básico para una tarea + +Nombra tu tarea, decide si quieres asignar una fecha límite y elige la visibilidad de los repositorios de la misma. + +- [Nombrar una tarea](#naming-an-assignment) +- [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment) +- [Elegir un tipo de tarea](#choosing-an-assignment-type) +- [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories) + +#### Nombrar una tarea + +Para una tarea individual, {% data variables.product.prodname_classroom %} nombra los repositorios de acuerdo con su prefijo y con el nombre de usuario de {% data variables.product.product_name %} del alumno. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras a una tarea "assingment-1" y el nombre de usuario del alumno en {% data variables.product.product_name %} es @octocat, entonces el nombre del repositorio de la tarea para @octocat será `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Asignar una fecha límita para una tarea + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Elegir un tipo de tarea + +Debajo de "Tarea individual o grupal", selecciona el menú desplegable y da clic en **Tarea individual**. No puedes cambiar el tipo de tarea después de crearla. Si prefieres crear una tarea de grupo, consulta la sección "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". + +#### Elegir un tipo de visibilidad para los repositorios de la tarea + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Agergar un código de inicio y configurar un ambiente de desarrollo + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Elegir un repositorio de plantilla](#choosing-a-template-repository) +- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Elegir un repositorio de plantilla + +Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada alumno del registro de alumnos del aula. {% data reusables.classroom.you-can-choose-a-template-repository %} Para obener más información sobre los repositorios de plantilla, consulta la sección "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)". + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Elegir un ambiente de desarrollo integrado (IDE) + +{% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Proporcionar retroalimentación para una tarea + +Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el alumno. + +- [Probar las tareas automáticamente](#testing-assignments-automatically) +- [Prevenir que se hagan cambios en los archivos importantes](#preventing-changes-to-important-files) +- [Crear una solicitud de cambios para retroalimentación](#creating-a-pull-request-for-feedback) + +#### Probar las tareas automáticamente + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Prevenir que se hagan cambios en los archivos importantes + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Crear una solicitud de cambios para retroalimentación + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Invitar a los alumnos a una tarea + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pestaña de **Todos los alumnos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %} + +
    + Tarea individual +
    + +### Pasos siguientes + +- Después de que creas la tarea, los alumnos pueden comenzar a trabajar en ella utilizando las características de Git y {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el alumno pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Crear, clonar y archivar repositorios](/github/creating-cloning-and-archiving-repositories)", "[Utilizar Git](/github/using-git)", y "[Colaborar con las propuestas y solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests)". + +- Cuando un alumno termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y las visualizaciones del repositorio para entender mejor su trabajo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". + +- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para obtener más información, consulta la sección "[Comentar en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Abrir una propuesta desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obtener más información sobre cómo crear respuestas guardadas para proporcionar retroalimentación a los errores comunes, consulta la sección "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)". + +### Further reading + +- "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000000..b7e711bbed826 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Inicia con GitHub Classroom +shortTitle: Empezar +intro: Aprende cómo configurar y utilizar {% data variables.product.prodname_classroom %} para administrar tu curso. +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000000..bee1dc7f7e975 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: Glosario +intro: Puedes revisar las explicaciones de la terminología de {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### tarea + +Una tarea es el trabajo del curso de {% data variables.product.prodname_classroom %}. Un maestropuede asignar una tarea a un alumno individual o a un grupo de alumnos. Los alumnos pueden importar código inicial para la tarea, asignar alumnos, y crear una fecha límite para cada tarea. Para obtener más información, consulta las definiciones de una "[tarea individual](#individual-assignment)" y de una "[tarea grupal](#group-assignment)". + +--- + +### aula + +Un aula es la unidad básica de {% data variables.product.prodname_classroom %}. Los maestros pueden utilizar un aula para organizar y adminisrar a los alumnos, enseñar a los asistentes y crear tareas para un curso. Las aulas pertenecne a una organización de {% data variables.product.prodname_dotcom_the_website %}. Para administrar un aula, debes ser el propietario de la organización de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar las aulas](/education/manage-coursework-with-github-classroom/manage-classrooms)". + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} es una aplicación web para los docentes que proporciona herramientas de administración de cursos integradas con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta el sitio web de [{% data variables.product.prodname_classroom %}](https://classroom.github.com/). + +--- + +### tarea grupal + +{% data reusables.classroom.assignments-group-definition %} Para obtener más información, consulta la sección "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". + +--- + +### identificador + +Un identificador en {% data variables.product.prodname_classroom %} es una ID única para un alumno que participa en un curso. Por ejemplo, un identificador puede ser el nombre del alumno, una ID alfanumérica o su dirección de correo electrónico. + +--- + +### tarea individual + +{% data reusables.classroom.assignments-individual-definition %} Para obtener más información, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)". + +--- + +### registro de alumnos + +Un registro de alumnos permite a los maestros administrar a los alumnos y emitir tareas en un aula de {% data variables.product.prodname_classroom %}. Los maestros pueden crear un registro de alumnos si ingresan una lista de identificadores de los mismos, o si conectan a {% data variables.product.prodname_classroom %} con un sistema de administración de aprendizaje (LMS). Para obtener más información sobre los identificadores, consulta la definición de [identificador](#identifier)". Para obtener más información sobre cómo conectar {% data variables.product.prodname_classroom %} con un LMS, consulta la sección "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". + +--- + +### Further reading + +- "[Glosario de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-glossary)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000000..4b4b6a4f31ca4 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Administrar el trabajo del curso con GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: Con {% data variables.product.prodname_classroom %}, puedes utilizar {% data variables.product.product_name %} para administrar o participar en un curso sobre el desarrollo de software. +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000000..e0ece3f059317 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrar a GitHub Classroom con un IDE +shortTitle: Integrar con un IDE +intro: Puedes ayudar a que tus alumnos escriban, prueben y depuren código si preconfiguras un ambiente de desarrollo para los repositorios de tareas en {% data variables.product.prodname_classroom %}. +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000000..f0a0050488cda --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integra a GitHub Classroom con un IDE en línea +shortTitle: Integrar con un IDE en línea +intro: Puedes preconfigurar un ambiente de desarrollo integrado (IDE) en línea para las tareas que crees en {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### Acerca de la integración con un IDE en línea + +{% data reusables.classroom.about-online-ides %} + +Después de que un alumno acepta una tarea con un IDE en línea, el archivo README en su repositorio de tareas contendrá un botón para abrir dicha tarea en el IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional. + +![Botón para un IDE en línea en el README.md de un repositorio de tarea](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### IDE en línea compatibles + +{% data variables.product.prodname_classroom %} es compatible con los siguientes IDE en línea. Puedes aprender más sobre la experiencia del alumno para cada IDE. + +| IDE | Más información | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[Acerca de utilizar MakeCode Arcade con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[Acerca de utilizar Repl.it con GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configurr un IDE en línea para una tarea + +Puedes elegir el IDE en línea que te gustaría utilizar para una tarea cuando la crees. Para aprender cómo crear una tarea nueva que utilice un IDE en línea, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". + +### Autorizar la app de OAuth para un IDE en línea + +La primera vez que configuras una tarea con un IDE en elínea, debes autorizar la app de OAuth para el IDE en línea de tu organización. + +![botón de "Otorgar acceso" en la ventana emergente para autorizar una app de OAuth en el IDE en línea](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +En todos tus repositorios, otorga acceso de **lectura** a la app para metadatos, administración y código, y acceso de **escritura** para administración y código. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". + +### Further reading + +- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000000..11ad0e7cfae77 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Aprende con GitHub Classroom +intro: Puedes participar en el trabajo del curso en {% data variables.product.prodname_classroom %} y ver los resultados de tu maestro. +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000000..45b9f657ad0b2 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Deja retroalimentación con solicitudes de cambios +intro: Puedes dejar retroalimentación para tus alumnos en una solicitud de cambio especial dentro del repositorio de cada tarea. +permissions: Las personas con permisos de lectura en un repositorio pueden dejar retroalimentación en una solicitud de cambios del repositorio. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### Acerca de las solicitudes de cambio de retroalimentación de las tareas + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +Cuando habilitas las solicitudes de cambio para retroalimentación de una tarea, {% data variables.product.prodname_classroom %} crerá una soicitud de cambios especial que se llama **Retroalimentación** en el repositorio de la tarea para cada alumno o equipo. La solicitud de cambios mostrará automáticamente todas las confirmaciones que subió el alumno a la rama predeterminada del repositorio de la tarea. + +### Prerrequisitos + +Para crear y acceder a la solicitud de cambios de retroalimentación, debes habilitarla cuando creas la tarea. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Dejar retroalimentación en una solicitud de cambios para una tarea + +{% data reusables.classroom.sign-into-github-classroom %} +1. En la lista de aulas, da clic en aquella con la tarea que quieres revisar. ![Aula en la lista de aulas de una organización](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. A la derecha de la emisión, da clic en **Revisar**. ![Botón de revisar para la tarea en una lista de emisiones de una tarea](/assets/images/help/classroom/assignments-click-review-button.png) +1. Revisar la solicitud de cambios. Para obtener más información, consulta "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### Further reading + +- "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md new file mode 100644 index 0000000000000..f5deeeb19f069 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Administrar aulas +intro: Puedes crear y administrar un aula para cada curso que impartes utilizando {% data variables.product.prodname_classroom %}. +permissions: Los propietarios de las organizaciones pueden administrar las aulas de éstas. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### Acerca de las aulas + +{% data reusables.classroom.about-classrooms %} + +![Aula](/assets/images/help/classroom/classroom-hero.png) + +### Acerca de la administración de aulas + +{% data variables.product.prodname_classroom %} utiliza cuentas de organización en {% data variables.product.product_name %} para administrar los permisos, la administración y la seguridad de cada aula que crees. Cada organización puede tener varias aulas. + +Después de crear un aula, {% data variables.product.prodname_classroom %} te pedirá que invites a los asistentes del maestro (TA) y a los administradores a formar parte de ella. Cada aula puede tener uno o más administradores. Los administradores pueden ser maestros, TA o cualquier otro administrador de curso que quieras tenga control sobre las aulas de {% data variables.product.prodname_classroom %}. + +Invita a los TA y administradores a tu aula invitando a sus cuentas de usuario en {% data variables.product.product_name %} para que formen parte de tu organización como propietarios de la misma y compartiendo la URL de tu aula. Los propietarios de la organización pueden administrar cualquier aula en ésta. Para obtener más información, consulta la sección "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)" y "[Invitar a los usuarios a unirse a tu organización](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)". + +Cuando termines de utilizar un aula, puedes archivarla y referirte a ella, a su registro de alumnos o a sus tareas posteriormente, o puedes borrarla si ya no la necesitas. + +### Acerca de los registros de alumnos de las aulas + +Cada aula tiene un registro de alumnos. Un registro de alumnos es una lista de identificadores para los alumnos que participan en tu curso. + +Cuando compartes la URL de una tarea con un alumno por primera vez, dicho alumno debe ingresar en {% data variables.product.product_name %} con una cuenta de usuario para vincularla con un identificador para el aula. Después de que el alumno vinculasu cuenta de usuario, puedes ver la cuenta de usuario asociada en el registro dealumnos. También puedes ver cuando el alumno acepta o emite una tarea. + +![Registro de alumnos de un aula](/assets/images/help/classroom/roster-hero.png) + +### Prerrequisitos + +Debes tener una cuenta de organización en {% data variables.product.product_name %} para administrar las aulas en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta las secciones "[Tipos de cuentas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" y "[Crear una organización nueva desde cero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". + +Debes autorizar a la app de OAuth de {% data variables.product.prodname_classroom %} para que tu organización administre aulas para tu cuenta organizacional. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". + +### Crear un aula + +{% data reusables.classroom.sign-into-github-classroom %} +1. Da clic en **Aula nueva**. ![Botón de "Aula nueva"](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +Después de que crees un aula, puedes comenzar a crear tareas para los alumnos. Para obtener más información, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". + +### Crear un registro de alumnos para tu aula + +Puedes crear un registro de alumnos de aquellos que participen en tu curso. + +Si tu curso ya tiene un registro de alumnos, puedes actualizar a los alumnos en el registro o borrarlos de éste. Para obtener más información, consulta la sección "[Agregar a un alumno al registro de alumnos de tu aula](#adding-students-to-the-roster-for-your-classroom)" o "[Borrar un registro de alumnos de un aula](#deleting-a-roster-for-a-classroom)". + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Para conectar a {% data variables.product.prodname_classroom %} a tu LMS e importar un registro de alumnos, da clic en {% octicon "mortar-board" aria-label="The mortar board icon" %} **importar desde un sistema de administración de aprendizaje** y sigue las instrucciones. Para obtener más información, consulta la sección "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". ![Botón de "Importar desde un sistema de administración de aprendizaje"](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. Para crear un registro de alumnos manualmente, teclea tus identificadores de alumno. Opcionalmente, da clic en **Cargar un CSV o archivo de texto**para cargar un archivo que contenga los identificadores. ![Campo de texto para teclear los identificadores de alumno y botón de "Cargar un CSV o archivo de texto"](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Da clic en **Crear registro de alumnos**. ![Botón de "Crear registro de alumnos"](/assets/images/help/classroom/click-create-roster-button.png) + +### Agregar a los alumnos al registro de alumnos de tu aula + +Tu aula debe tener un registro de alumnos existente para agregar alumnos a éste. Para obtener más información sobre crear un registro de alumnos, consulta la sección "[Crear un registro de alumnos para tu aula](#creating-a-roster-for-your-classroom)". + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. A la derecha de "Registro de alumnos del aula", da clic en **Actualizar alumnos**. ![Botón de "Actualizar alumnos" a la derecha del encabezado "Registro de alumnos" sobre la lista de alumnos](/assets/images/help/classroom/click-update-students-button.png) +1. Sigue las instrucciones para agregar a los alumnos al registro de alumnos. + - Para importar a los alumnos desde un LMS, da clic en **Sincronizar desde un sistema de administración de aprendizaje**. Para obtener más información sobre cómo importar un registro dealumnos desde un LMS, consulta la sección "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". + - Para agregar manualmente a los alumnos, debajo de "Agregar manualmente a los alumnos", da clic en **Cargar un CSV o archivo de texto** o teclea los identificadores de los alumnos y luego da clic en **Agregar entradas al registro de alumnos**. ![Modo para elegir un método para agregar alumnos al aula](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renombrar un aula + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Debajo de "nombre del aula", teclea un nombre nuevo para ésta. ![Campo de texto debajo de "Nombre de aula" para teclear el nombre de un aula](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Da clic en **Renombrar aula**. ![Botón "Renombrar aula"](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archivar o dejar de archivar un aula + +Puedes archuivar un aula que ya no utilices en {% data variables.product.prodname_classroom %}. Cuando archivas un aula, no puedes crear tareas nuevas ni editar aquellas existentes en ella. Los alumnos no pueden aceptar invitaciones a las tareas de las aulas archivadas. + +{% data reusables.classroom.sign-into-github-classroom %} +1. A la derecha del nombre del aula, selecciona el menú desplegable {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y da clic en **Archivar**. ![Menú desplegable del icono de kebab horizontal y elemento "Archive" del menú](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. Para dejar de archivar un aula, a la derecha de su nombre, selecciona el menú desplegable {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y da clic en **Dejar de archivar**. ![Menú desplegable desde el icono de kebab horizontal y elemento "Dejar de archivar" del menú](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Borrar el registro de alumnos de un aula + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Debajo de "Borrar este registro de alumnos", da clic en **Borrar registro de alumnos**. ![Botón "Borrar registro de alumnos" debajo de "Borrar este registro de alumnos" en la pestaña "Alumnos" de un aula](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Lee las advertencias y luego da clic en **Borrar registro de alumnos**. ![Botón "Borrar registro de alumnos" debajo de "Borrar este registro de alumnos" en la pestaña "Alumnos" de un aula](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Borrar un aula + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. A la derecha de "Borrar esta aula", da clic en **Borrar aula**. ![Botón de "Borrar un repositorio"](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Lee las advertencias**. +1. Para verificar que estás borrando el aula correcta, teclea el nombre del aula que quieres borrar. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Da clic en **Borrar aula**. ![Botón de "Borrar aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000000..29ee125f4b0e7 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Ejecuta el código de los alumnos en un IDE en línea +intro: Puedes ejecutar el código desde una tarea de un alumno dentro del ambiente de desarrollo integrado (IDE) en línea que configuraste para la tarea. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### Acerca de el código de los alumnos y los IDE en línea + +Si configuras un ambiente de desarrollo integrado (IDE) en línea para una tarea, puedes ejecutar el código dentro de éste. No necesitas clonar el repositorio de la tarea en tu computadora. + +Para obtener más información sobre los IDE en línea, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE en línea](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)". + +### Ejecutar el código de los alumnos en el IDE en línea + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. A la derecha de la emisión, da clic en **Ver IDE**. ![Botón de "Ver IDE" en una emisión que utiliza un IDE en línea](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000000..7bb46bc4523b3 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Enseña con GitHub Classroom +intro: Aprende cómo configurar tu aula y tus tareas. +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000000..3b37273b15003 --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Utiliza las calificaciones automáticas +intro: Puedes proporcionar retroalimentación automáticamente en las emisiones de código de tus alumnos si configuras las pruebas para que se ejecuten en el repositorio de tareas. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### Acerca de las calificaciones automáticas + +{% data reusables.classroom.about-autograding %} + +Después de que un alumno acepte una tarea, en cada subida al repositorio de la misma, {% data variables.product.prodname_actions %} ejecuta comandos para tu prueba de calificaciones automáticas en un ambiente Linux que contiene el código más nuevo del alumno. {% data variables.product.prodname_classroom %} crea los flujos de trabajo necesarios para {% data variables.product.prodname_actions %}. No necesitas tener experiencia con las {% data variables.product.prodname_actions %} para utilizar las calificaciones automáticas. + +Puedes utiizar un marco de trabajo de prueba, ejecutar un comando personalizado, escribir pruebas de entrada/salida, o combinar varios métodos de pruebas. El ambiente de Linux para las calificaciones automáticas contienen muchas herramientas de software populares. Para obtener más información, consulta los detalles de la última versión de Ubuntu en "[Especificaciones para los ejecutores hospedados en {% data variables.product.company_short %}](/actions/reference/specifications-for-github-hosted-runners#supported-software)". + +Puedes ver un resumen de qué estudiantes están pasando las pruebas con calificación automática si navegas a la tarea en {% data variables.product.prodname_classroom %}. Una marca verde significa que el alumno está pasando todas las pruebas, la X roja significa que el alumno falló en algunas o todas las pruebas. Si otorgas puntos para una o más pruebas, entonces una burbuja mostrará la puntuación de éstas con base en la puntuación máxima posible para la tarea. + +![Resumen de una tarea con resultados de calificación automática](/assets/images/help/classroom/autograding-hero.png) + +### Métodos para calificar + +Hay dos métodos para calificar: pruebas de entrada/salida y pruebas de ejecución de comandos. + +#### Prueba de entrada/salida + +Una prueba de entrada/salida ejecuta un comando de configuración opcionalmente y proporciona una entrada estándar de un comando de prueba. {% data variables.product.prodname_classroom %} evalúa la salida del comando de prueba contra un resultado esperado. + +| Parámetro | Descripción | +|:---------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- | +| **Nombre de la prueba** | El nombre de la prueba para identificarla en las bitácoras | +| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación | +| **Comando de ejecución** | El comando para ejecutar la prueba y generar una salida estándar para su evaluación | +| **Inputs** | Entrada estándar para el comando de ejecución | +| **Salida esperada** | La salida que quieres ver como estándar para el comando de ejecución | +| **Comparación** | El tipo de comparación entre el la salida del comando de ejecución y la salida esperada

    • **Included**: Pasa cuando la salida esperada aparece
      en cualquier parte dentro de la salida estándar del comando de ejecución
    • **Exact**: Pasa cuando la salida esperada es completamente idéntica
      a la salida estándar del comando de ejecución
    • **Regex**: Pasa si la expresión regular en la salida
      esperada coincide con la salida estándar del comando de ejecución
    | +| **Tiempo excedido** | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo | +| **Puntos** | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total | + +#### Prueba de comando de ejecución + +Una prueba de comando de ejecución ejecuta un comando de configuración y luego un comando de prueba. {% data variables.product.prodname_classroom %} verifica el estado de salida del comando de prueba. Un código de salida de `0` resultará en éxito y cualquier otro código de salida resultara en un fallo. + +{% data variables.product.prodname_classroom %} proporciona preajustes para un las pruebas de comandos de ejecución específicas de lenguaje para varios lenguajes de programación. Por ejemplo, la prueba de **ejecutar nodo** llena previamente el comando de configuración con `npm install` y el comando de prueba con `npm test`. + +| Parámetro | Descripción | +|:---------------------------- |:---------------------------------------------------------------------------------------------- | +| **Nombre de la prueba** | El nombre de la prueba para identificarla en las bitácoras | +| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación | +| **Comando de ejecución** | El comando para ejecutar la prueba y generar un código de salida para evaluación | +| **Tiempo excedido** | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo | +| **Puntos** | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total | + +### Configurar las pruebas de calificación automática para una tarea + +Puedes agregar pruebas de calificación automática durante la creación de una tarea nueva. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +Puedes agregar, editar o borrar las pruebas de calificación automática para una tarea existente. Si cambias las pruebas de calificación automática para una tarea existente, los repositorios de tareas existentes no se verán afectados. Un alumno o equipo debe aceptar la tarea y crear un repositorio de tareas nuevo para utilizar las pruebas nuevas. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. En la barra lateral, da clic en **Calificaciones y retroalimentación**. !["Calificaciones y retroalimentación" a la izquierda de los puntos básicos de la tarea](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Agrega, edita o borra una prueba de calificación automática. + - Para agregar una prueba, debajo de "Agregar pruebas de calificación automática", selecciona el menú desplegable **Agregar prueba** y luego da clic en el método de calificación que quieras utilizar. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - Para editar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - Para borrar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Icono de cesta de basura para borrar una prueba de calificación automática](/assets/images/help/classroom/autograding-click-trash.png) +1. En la parte inferior de la página, da clic en **Actualizar tarea**. ![Botón de "Actualizar tarea" en la parte inferior de la página](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Visualizar las bitácoras desde las pruebas de calificación automática + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. A la derecha de una emisión, da clic en **Ver prueba**. ![Botón de "Ver tarea" para una emisión de una tarea](/assets/images/help/classroom/assignments-click-view-test.png) +1. Revisa la salida de la prueba. Para obtener más información, consulta la sección "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/managing-workflow-runs/using-workflow-run-logs)". + +### Further reading + +- [Documentación de {% data variables.product.prodname_actions %}](/actions) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000000..a976a29e0468e --- /dev/null +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: Ver los resultados de calificaciones automáticas +intro: Puedes ver los resultados de las calificaciones automáticas dentro del repositorio de tu tarea. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### Acerca de las calificaciones automáticas + +Tu maestro puede configurar las pruebas que verifican tu trabajo automáticamente cuando subres información a un repositorio de tarea en {% data variables.product.product_location %}. + +Si eres un alumno y tu instructor configuró las calificaciones automáticas para tu tarea en {% data variables.product.prodname_classroom %}, encontrarás los resultados de las pruebas de calificación automática a lo largo de tu repositorio de tareas. Si todas las pruebas de una confirmación son exitosas, verás una marca verde. Si cualquiera de las pruebas de una confirmación falla, verás una X roja. Puedes ver las bitácoras detalladas si das clic en la marca verde o en la X roja. + +### Visualizr los resultados de calificaciones automáticas para un repositorio de tarea + +{% data variables.product.prodname_classroom %} utiliza {% data variables.product.prodname_actions %} para ejecutar las pruebas de calificación automática. Para obtener más información sobre cómo ver las bitácoras para una prueba de calificación automática, consulta la sección "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)". + +La pestaña de **Acciones** muestra el historial completo de las ejecuciones de las pruebas. + +![Pestaña de "Acciones" que tiene seleccionado "Todos los flujos de trabajo"](/assets/images/help/classroom/autograding-actions-tab.png) + +Puedes dar clic en una ejecución de prueba específica para revisar la bitácora de salida, como en los errores de compilación y fallos de pruebas. + +![Las bitácoras de resultados de las pruebas de un "flujo de trabajo de calificación automática de {% data variables.product.prodname_classroom %}" en {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### Further reading + +- "[Acerca de las verificaciones de estado](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/es-ES/content/education/quickstart.md b/translations/es-ES/content/education/quickstart.md new file mode 100644 index 0000000000000..4a185f18e657e --- /dev/null +++ b/translations/es-ES/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Inicio rápido para GitHub Educators +intro: En cerca de 15 minutos, los maestros pueden iniciar con descuentos, capacitación y herramientas para {% data variables.product.company_short %}, posteriormente, pueden crear un aula para los alumnos en un curso de desarrollo de software utilizando {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: verdadero +versions: + free-pro-team: '*' +--- + +### Introducción + +Los docentes que enseñan un curso de desarrollo de software pueden utilizar descuentos, alianzas, capacitación y herramientas de {% data variables.product.prodname_education %} para enseñar de forma efectiva las habilidades relevantes a los alumnos. + +En esta guía, iniciarás con {% data variables.product.product_name %}, regístrate para las cuentas y servicios con descuento a través de {% data variables.product.prodname_education %} y crea un espacio para tu curso y tareas en {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: Si eres un alumno y te gustaría sacar partido de un descuento académico, consulta la sección "[Postularse para un paquete de desarrollo para alumnos](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)". + +{% endtip %} + +### Crear cuentas en {% data variables.product.product_name %} + +Primero, necesitas crear una cuenta de usuario gratuita en {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Sigue las indicaciones para crear tu cuenta de usuario gratuita. + +Después de que crees tu cuenta de usuario, crea una cuenta de organización gratuita. Utilizarás esta cuenta de organización para crear y administrar las aulas {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Sigue las indicaciones para crear una organización gratuita. + +Para obtener más información, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". + +### Postularse para un descuento de docente + +A continuación, te registrarás para obtener descuentos en los servicios de {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** Adicionalmente a los descuentos adicionales, {% data variables.product.company_short %} ofrece alianzas con las instituciones educativas mediante el {% data variables.product.prodname_campus_program %}. Para obtener más información, consulta el sitio web de [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Configura {% data variables.product.prodname_classroom %} + +Con tu cuenta de usuario y cuenta de organización, ya estás listo para iniciar con {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} es de uso gratuito. Puedes rastrear y administrar las tareas, calificar los trabajos automáticamente y proporcionar retroalimentación a tus alumnos. + +{% data reusables.classroom.sign-into-github-classroom %} +1. Para autorizar a {% data variables.product.prodname_classroom %} para que acceda a tu cuenta de usuario en {% data variables.product.prodname_dotcom %}, revisa la información y luego da clic en **Autorizar a {% data variables.product.prodname_classroom %}**. ![Botón de "Autorizar {% data variables.product.prodname_classroom %}" para una cuenta de usuario](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Revisa la información. Para autorizar a {% data variables.product.prodname_classroom %} para que acceda a tu cuenta de organización en {% data variables.product.prodname_dotcom %}, da clic en **Otorgar**. ![Botón de "Otorgar" para una organización](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: si ves un botón de **Solicitar** en vez de uno de **Otorgar**, significa que eres un miembro de la organización y no un propietario. Un propietario deberá aprobar tu solicitud para {% data variables.product.prodname_classroom %}. Debes ser un propietario de la organización para crear y administrar las aulas y las tareas en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)". + + {% endtip %} + +1. Da clic en **Autorizar github**. ![Clic en el botón "Autorizar" para una organización](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Crea tu aula + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Da clic en **Crear tu primer aula** o en **Aula nueva**. +{% data reusables.classroom.guide-create-new-classroom %} + +### Pasos siguientes + +¡Creaste un aula y estás listo para enriquecer tu curso con {% data variables.product.product_name %} y {% data variables.product.prodname_classroom %}! 🎉 + +- Mira algunos videos acerca de {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Puntos básicos para configurar {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". +- Administra tus aulas y administradores de aula y crea un registro de alumnos para aquellos que conforman tu aula. Para obtener más información, consulta la sección "[Administrar las aulas](/education/manage-coursework-with-github-classroom/manage-classrooms)". +- Crea una tarea para alumnos individuales o equipos. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Escribe e implementa pruebas automatizadas para proporcionar retroalimentación inmediata a los alumnos directamente en los repositorios de tareas. Para obtener más información, consulta la sección "[Utilizar calificaciones automáticas](/education/manage-coursework-with-github-classroom/use-autograding)". +- Participa en {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000000..e800c9db1e349 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: Acerca de Asesores de campus +intro: 'Como instructor o mentor, aprende a usar {% data variables.product.prodname_dotcom %} en tu escuela con el soporte técnico y la capacitación de Asesores de campus.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Profesores, maestros y mentores pueden usar la capacitación en línea de Asesores de campus para ser expertos en Git y {% data variables.product.prodname_dotcom %} y aprender las mejores prácticas para enseñarles a los alumnos con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Asesores de campus](https://education.github.com/teachers/advisors)". + +{% note %} + +**Nota:** Como instructor, no puedes crear cuentas de {% data variables.product.prodname_dotcom %} para tus alumnos. Los alumnos deben crear sus propias cuentas de {% data variables.product.prodname_dotcom %}. + +{% endnote %} diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000000..c4d93261979c0 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: Acerca de Expertos en campus +intro: 'Como estudiante, aprende las habilidades que necesitas para crear un portfolio real y una comunidad tecnológica de tu escuela, con la capacitación de Expertos en campus de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Aprende habilidades comunicativas en público, escritura técnica, liderazgo comunitario y habilidades de desarrollo de software como un Experto en campus de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Expertos en campus](https://education.github.com/students/experts)". diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000000..0328e4bc987e4 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: Acerca de Educación GitHub para educadores e investigadores +intro: '{% data variables.product.prodname_education %} ofrece una variedad de herramientas para ayudar a los educadores y los investigadores a trabajar de manera más eficaz dentro y fuera del aula.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} para educadores + +Con los servicios y las herramientas de {% data variables.product.prodname_education %} para educadores de todos los niveles, puedes: + - Usar [{% data variables.product.prodname_classroom %}](https://classroom.github.com) para distribuir el código, hacerles comentarios a los estudiantes y recolectar las tareas en {% data variables.product.prodname_dotcom %}. + - Unirte a nuestra [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) para debatir tendencias actuales sobre educación tecnológica con tus pares de todo el mundo. + - Acceder y adaptar nuestros [planes de lecciones de código abierto](https://education.github.community/t/open-source-lesson-plans/1591) para enseñar Git y {% data variables.product.prodname_dotcom %}. + - [Solicitar un botín {% data variables.product.prodname_dotcom %}](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) con beneficios y materiales educativos para tus estudiantes. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} para investigadores + +Con los servicios y las herramientas de {% data variables.product.prodname_education %} para investigadores, puedes: + - Colaborar con otros en tu trabajo de investigación en todo el mundo en {% data variables.product.prodname_dotcom %}. + - [Aprender](https://education.github.com/stories) cómo usan {% data variables.product.prodname_dotcom %} las instituciones académicas en todo el mundo para su investigación. + {% data reusables.education.apply-for-team %} + +### Further reading + +- "[Acerca de {% data variables.product.prodname_education %} para estudiantes](/articles/about-github-education-for-students)" diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000000..062224fcf0305 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: Acerca de Educación GitHub para estudiantes +intro: '{% data variables.product.prodname_education %} le ofrece a los estudiantes experiencia práctica con acceso gratuito a diversas herramientas de programadores de los socios de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Usar {% data variables.product.prodname_dotcom %} para tus proyectos escolares es un modo práctico de colaborar con otros y crear un portfolio que exhiba experiencia práctica. + +{% data reusables.education.about-github-education-link %} + +Cualquiera con una cuenta de {% data variables.product.prodname_dotcom %} puede colaborar en repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %}. Como estudiante, también puedes solicitar el {% data variables.product.prodname_student_pack %}, que ofrece acceso gratuito a herramientas y servicios usados por programadores profesionales. Para obtener más información, consulta las secciones "[Postularse para un paquete de desarrollo para alumnos](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" y [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Si eres un miembro de un club de robótica FIRST, tu mentor puede solicitar un descuento de educador para que tu equipo pueda colaborar usando {% data variables.product.prodname_team %}, lo que permite repositorios privados y usuarios ilimitados, de forma gratuita. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)". + +### Further reading + +- "[Acerca de {% data variables.product.prodname_education %} para educadores e investigadores](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000000..35d1ee04244f7 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: Acerca de Educación GitHub +intro: '{% data variables.product.prodname_education %} ofrece un producto gratuito especial para las escuelas que quieren aprovechar al máximo {% data variables.product.prodname_dotcom %} para su comunidad y que aceptan los requisitos específicos del programa.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Si tu escuela acepta cumplir con ciertos requisitos, tu escuela secundaria, universidad o seminario intensivo profesional puede obtener {% data variables.product.prodname_education %}, que ofrece lo mejor de {% data variables.product.prodname_dotcom %} gratis, e incluye: +- {% data variables.product.prodname_ghe_cloud %} y/o {% data variables.product.prodname_ghe_server %} +- Capacitación para docentes para el Git principal y {% data variables.product.prodname_dotcom %} con nuestro programa Asesores de campus +- Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %} +- Desarrollo de liderazgo y capacitación técnica para estudiantes con el programa Expertos en campus + +Para obtener más información, consulta la página [oficial {% data variables.product.prodname_education %}](https://education.github.com/partners/schools). + +Los maestros pueden administrar un curso sobre desarrollo de software con {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} te ayuda a distribuir código, proporcionar retroalimentación y administrar el trabajo del curso utilizando {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Administrar el trabajo del curso con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)". + +Para conocer más acerca de los programas de capacitación para líderes estudiantiles y docentes, consulta "[{% data variables.product.prodname_dotcom %} Expertos en campus](https://education.github.com/students/experts)" y "[Asesores de campus](https://education.github.com/teachers/advisors)". + +Si eres un estudiante validado o académico y tu escuela no está asociada con {% data variables.product.prodname_dotcom %} como una escuela {% data variables.product.prodname_education %}, aún puedes solicitar descuentos de forma individual para usar {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Usar {% data variables.product.prodname_dotcom %} para tu trabajo escolar](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" o "[Usar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)". diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000000..693201df2b48f --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Aplicar un paquete de desarrollo para alumnos +intro: 'Como estudiante, puedes aplicar para el {% data variables.product.prodname_student_pack %}, que incluye ofertas y beneficios de los socios de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Requisitos + +Para ser elegible para el {% data variables.product.prodname_student_pack %}, debes: +- Estar inscrito actualmente en un curso que otorgue un título o diploma que garantice un curso de estudio como colegio, escuela secundaria, facultad, universidad, escolarización en casa o institución educativa similar +- Tener una dirección de correo electrónico verificable suministrada por la escuela o cargar documentos que demuestren tu situación de estudiante actual +- Tener una cuenta de usuario de [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) +- Tener al menos 13 años + +Entre los documentos que comprueban tu estado actual de alumno se incluye una foto de la ID de tu escuela con la fecha de inscripción actual, horario de clases, transcripción y carta de verificación de inscripción o de afiliación. + +Es posible que se te pida periódicamente que vuelvas a verificar tu estado académico actual para confirmar que eres estudiante. + +{% note %} + +**Nota:** No puedes transferir tus descuentos académicos de una cuenta a otra. Si tienes más de una cuenta a la que deseas aplicarle el descuenta, considera [fusionar](/articles/merging-multiple-user-accounts) tus cuentas de usuario y [cambiar el nombre](/articles/changing-your-github-username) a la cuenta retenida si así lo deseas. + +{% endnote %} + +Para obtener información sobre cómo renovar tu {% data variables.product.prodname_student_pack %}, consulta "[Caducidad y renovaciones](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)". + +### Aplicar para un {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. En "¿Qué es lo que mejor describe tu estado académico?", selecciona **Student** (Estudiante). ![Selecciona el estado académico](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Caducidad y renovaciones + +Una vez que caduca tu acceso a {% data variables.product.prodname_student_pack %}, puedes volver a aplicar si sigues siendo elegible, aunque es posible que las ofertas de algunos socios no puedan renovarse. La mayoría de las ofertas regulares de nuestros socios comiencen una vez que las configuraste. Para obtener más información, consulta la página [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). + +Para ver cuándo caduca tu acceso gratis al {% data variables.product.prodname_student_pack %}, visita los [ajustes de facturación](https://github.com/settings/billing). + +### Further reading + +- "[¿Por qué no aprobaron mi aplicación para un {% data variables.product.prodname_student_pack %}?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000000..ac0d79bfb5d05 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Postularse para un descuento de investigador o educador +intro: 'Si eres educador o investigador, puedes aplicar para recibir {% data variables.product.prodname_team %} para la cuenta de tu organización de manera gratuita.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Acerca de descuentos para educadores e investigadores + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +Para obtener más información acerca de las cuentas de usuario en {% data variables.product.product_name %}, consulta la sección "[Registrarse para una cuenta nueva de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account)". + +### Aplicar para un descuento de educador o investigador + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Actualizar tu organización + +Después de que se apruebe tu solicitud para un descuento de investigador o de maestro, puedes mejorar las organizaciones que utilizas con tu comunidad educativa a {% data variables.product.prodname_team %}, lo cual permitirá que tengas usuarios y repositorios privados ilimitados con todas las características gratuitamente. Puedes actualizar una organización existente o crear una organización nueva para actualizarla. + +#### Actualizar una organización existente + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Actualizar una organización nueva + +{% data reusables.education.upgrade-page %} +1. Da clic en {% octicon "plus" aria-label="The plus symbol" %}**Crear una organización**. ![Botón para crear una organizacion](/assets/images/help/education/create-org-button.png) +3. Lee la información, posteriormente da clic en **Crear organización**. ![Botón Create organization (Crear organización)](/assets/images/help/education/create-organization-button.png) +4. Debajo de "Elige tu plan", da clic en **Elegir {% data variables.product.prodname_free_team %}**. +5. Sigue las propuestas para crear tu organización. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Further reading + +- "[¿Por que no ha sido aprobada mi aplicación para recibir un descuento como educador o investigador?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [Videos de {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/index.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000000..4222653b94633 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explora los beneficios de enseñar y aprender con GitHub Education +shortTitle: Enseña y aprende +intro: Aprende cómo {% data variables.product.prodname_education %} puede beneificiar a tu aula, trabajo escolar o investigación y cómo postularse para obtener acceso gratuito a varias herramientas de desarrollo de los socios de {% data variables.product.company_short %}. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000000..76af908244221 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +title: Utiliza GitHub en tu institución educativa +intro: 'Aumenta los beneficios de utilizar {% data variables.product.prodname_dotcom %} en tu institución para los estudiantes, instructores y el personal de TI con {% data variables.product.prodname_education %} y nuestros múltiples programas de capacitación para estudiantes e instructores.' +mapTopic: verdadero +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000000..1ad86b48b8bb2 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +title: Utiliza GitHub para tu trabajo escolar +intro: 'Como estudiante, utiliza {% data variables.product.prodname_dotcom %} para colaborar en tus proyectos escolares y crear experiencias de la vida real.' +mapTopic: verdadero +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000000..d42a1a1b5e6bc --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +title: Utiliza GitHub en tu aula y en tu investigación +intro: 'Como educador o investigador, utiliza {% data variables.product.prodname_dotcom %} para colaborar con el trabajo en clase, con el grupo de estudiantes o de investigación, y mucho más.' +mapTopic: verdadero +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000000..bad58adeddf3c --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: '¿Por qué no se aprobó mi solicitud para un paquete de desarrollo para estudiantes?' +intro: 'Revisa las razones comunes por las que las solicitudes para el {% data variables.product.prodname_student_pack %} no se aprueban y lee las sugerencias para volver a solicitarlo con éxito.' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Documentos de afiliación académica poco claros + +Si la imagen que cargaste no identifica claramente tu situación académica actual, solicitamos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico con un dominio no verificado + +Si tu dirección de correo electrónico académica tiene un dominio no verificado, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas + +Si tu escuela expide direcciones de correo electrónico antes del pago de la inscripción, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +Si tienes otras preguntas o inquietudes acerca del dominio de la escuela solicita al personal de informática de tu escuela que nos contacte. + +### Dirección de correo electrónico académica que ya se usó + +Si tu dirección de correo electrónico académica ya se usó para solicitar un {% data variables.product.prodname_student_pack %} para una cuenta {% data variables.product.prodname_dotcom %} diferente, no puedes volver a usar la dirección de correo electrónico académica para solicitar con éxito otro {% data variables.product.prodname_student_pack %} hasta que ese descuento haya vencido. + +{% note %} + +**Nota:** mantener más de una cuenta individual no respeta los {% data variables.product.prodname_dotcom %} [Términos del servicio](/articles/github-terms-of-service/#3-account-requirements). + +{% endnote %} + +Si tienes más de una cuenta de usuario, debes fusionar tus cuentas. Para conservar el descuento, debes mantener la cuenta a la que se le otorgó el descuento. Puedes renombrar la cuenta retenida y conservar tu historial de contribuciones agregando todas las direcciones de correo electrónico a la cuenta retenida. + +Para obtener más información, consulta: +- "[Fusionar cuentas de usuario múltiples](/articles/merging-multiple-user-accounts)" +- "[Cambiar tu nombre de usuario {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)" +- "[Agregar una dirección de correo electrónico a tu cuenta {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account)" + +### Situación de estudiante inadmisible + +No eres apto para un {% data variables.product.prodname_student_pack %} si: +- Estás inscrito en un programa de aprendizaje informal que no forma parte del [Programa del Campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools) y no estás inscrito en un diploma o título que otorgue un reconocimiento de estudios. +- Tienes menos de 13 años. + +Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. Si estás estudiando en una escuela o programa intensivo de codificación, podrás inscribirte en {% data variables.product.prodname_student_pack %} si tu escuela se une al [Programa del campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools). + +### Further reading + +- "[Solicitar un paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)" +- "[Postularse para un paquete de desarrollo para alumnos](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000000..b0f4f28af0343 --- /dev/null +++ b/translations/es-ES/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: '¿Por qué mi solicitud para un descuento de educador o de investigador no se aprobó?' +intro: Revisa las razones comunes por las que las solicitudes para un descuento de educador o de investigador no se aprueban y lee las sugerencias para volver a solicitarlo con éxito. +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Documentos poco claros de la prueba de afiliación + +Si la imagen que cargaste no identifica claramente tu empleo actual con una escuela o una universidad, debes volver a presentar la solicitud y cargar otra imagen de la identificación de tu facultad o carta de verificación de empleo con información clara. + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico con un dominio no verificado + +Si tu dirección de correo electrónico académica tiene un dominio no verificado, podemos solicitar más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas + +Si los ex alumnos y los profesores retirados de tu escuela tienen acceso vitalicio a las direcciones de correo electrónico suministradas por la escuela, podemos requerir más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +Si tienes otras preguntas o inquietudes acerca del dominio de la escuela, solicita al personal de informática de tu escuela que nos contacte. + +### Personas que no son estudiantes solicitan un paquete de desarrollo para estudiantes + +Los educadores y los investigadores no son elegibles para las ofertas de los socios que vienen con el [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Cuando vuelves a presentar una solicitud, asegúrate de elegir **Profesor** para describir tu situación académica. + +### Further reading + +- "[Solicitar un descuento de educador o de investigador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md new file mode 100644 index 0000000000000..c0ebd2c0c2e28 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -0,0 +1,49 @@ +--- +title: Acerca de las actualizaciones a la versión del Dependabot +intro: 'Puede utilizar el {% data variables.product.prodname_dependabot %} para mantener los paquetes que utilizas actualizados a su versión más reciente.' +redirect_from: + - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot-version-updates +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca de {% data variables.product.prodname_dependabot_version_updates %} + +El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende. + +Puedes habilitar {% data variables.product.prodname_dependabot_version_updates %} si seleccionas el archivo de configuración en tu repositorio. El archivo de configuración especifica la ubicación del manifiesto, u otros archivos de definición de paquetes, almacenado en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas a proveedores (o almacenadas en caché) son dependencias que se verifican en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. + +Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Para las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta solicitudes de cambios para reemplazar directamente la dependencia desactualizada con una versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". + +Si habilitas las actualizaciones de seguridad, el {% data variables.product.prodname_dependabot %} también levantará las solicitudes de extracción para actualizar las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + +{% data reusables.dependabot.dependabot-tos %} + +### Frecuencia de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} + +Tú eres quien especifica qué tan a menudo se revisa cada ecosistema para encontrar nuevas versiones en el archivo de configuración: diario, semanalmente, o mensualmente. + +{% data reusables.dependabot.initial-updates %} + +Si habilitaste las actualizaciones de seguridad, algunas veces verás solicitudes de extracción adicionales para actualizaciones de seguridad. Esto se activa con una alerta del {% data variables.product.prodname_dependabot %} para una dependencia en tu rama predeterminada. El {% data variables.product.prodname_dependabot %} levanta automáticamente una solicitud de extracción para actualizar la dependencia vulnerable. + +### Repositorios y ecosistemas compatibles + +Puedes configurar las actualizaciones de versión para los repositorios que contengan un manifiesto de dependencias o un archivo fijado para alguno de los administradores de paquetes compatibles. Para algunos administradores de paquetes, también puedes configurar la delegación a proveedores para las dependencias. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)". + +{% note %} + +{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, el {% data variables.product.prodname_dependabot %} no es compatible con dependencias privadas de {% data variables.product.prodname_dotcom %} para todos los administradores de paquetes. Consulta los detalles en la tabla a continuación. + +{% endnote %} + +{% data reusables.dependabot.supported-package-managers %} + +Si tu repositorio ya utiliza una integración para la administración de dependencias, necesitarás inhabilitarlo antes de habilitar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)". + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". diff --git a/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md new file mode 100644 index 0000000000000..c79561d405fd7 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -0,0 +1,46 @@ +--- +title: Acerca de las notificaciones por correo electrónico para las inserciones en tu repositorio +intro: Puedes elegir enviar notificaciones por correo electrónico automáticamente a una dirección en específico cuando alguien suba información a tu repositorio. +permissions: Las personas con permisos administrativos en un repositorio pueden habilitar notificaciones de correo electrónico para las cargas a tu repositorio. +redirect_from: + - /articles/managing-notifications-for-pushes-to-a-repository/ + - /articles/receiving-email-notifications-for-pushes-to-a-repository/ + - /articles/about-email-notifications-for-pushes-to-your-repository/ + - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.notifications.outbound_email_tip %} + +Cada notificación por correo electrónico para una subida a un repositorio enumera las confirmaciones nuevas y las vincula a una diferencia que solo contenga esas confirmaciones. En la notificación por correo electrónico verás: + +- El nombre del repositorio donde se realizó la confirmación. +- La rama en la que se realizó la confirmación. +- El SHA1 de la confirmación, incluido un enlace a la diferencia en {% data variables.product.product_name %}. +- El autor de la confirmación. +- La fecha en que se realizó la confirmación. +- Los archivos que fueron modificados como parte de la confirmación. +- El mensaje de confirmación + +Puedes filtrar las notificaciones por correo electrónico que recibes para las inserciones en un repositorio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de los correos electrónicos de notificación](/github/receiving-notifications-about-activity-on-github/about-email-notifications)". También puedes apagar las notificaciones por correo electrónico para las cargas de información. Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}". + +### Habilitar las notificaciones por correo electrónico para las subidas de información en tu repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.sidebar-notifications %} +5. Escribe hasta dos direcciones de correo electrónico, separadas por espacio en blanco, donde quieras que se envíen las notificaciones. Si quieres enviar los correos electrónicos a más de dos cuentas, configura una de las direcciones de correo electrónico a una dirección de correo electrónico del grupo. ![Cuadro de texto dirección de correo electrónico](/assets/images/help/settings/email_services_addresses.png) +6. Si operas tu propio servidor, puedes verificar la integridad de los correos electrónicos mediante el token **Secreto**. Este token se envía con el correo electrónico como el encabezado `Aprobado`. Si el encabezado `Aprobado` coincide con el token que enviaste, puedes confiar en que el correo electrónico es de {% data variables.product.product_name %}. ![Cuadro de texto correo electrónico secreto](/assets/images/help/settings/email_services_token.png) +7. Haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/help/settings/save_notification_settings.png) + +### Further reading +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +- "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +{% else %} +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" +- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" +- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md new file mode 100644 index 0000000000000..b7ccd20dbb71b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -0,0 +1,37 @@ +--- +title: Acerca de los métodos de fusión en GitHub +intro: 'Puedes permitirle a los colaboradores con acceso de escritura a tu repositorio fusionar sus solicitudes de extracción en {% data variables.product.product_location %} con diferentes opciones de fusión o implementar un método de fusión específico para todas las solicitudes de extracción de tu repositorio.' +redirect_from: + - /articles/about-merge-methods-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pull_requests.configure_pull_request_merges_intro %} Puedes implementar un tipo de método de fusión, como el cambio de base o la combinación de confirmaciones, con solo activar el método deseado para tu repositorio. + +{% data reusables.pull_requests.default_merge_option %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} + +### Combinar tus confirmaciones de fusión + +{% data reusables.pull_requests.squash_and_merge_summary %} + +Antes de activar combinar confirmaciones, considera estas desventajas: +- Se pierde información acerca de cuándo se hicieron originalmente los cambios específicos y quién es el autor de las confirmaciones combinadas. +- Si sigues trabajando en la rama principal de una solicitud de extracción después de combinar y fusionar, y luego creas una solicitud de extracción nueva entre las mismas ramas, las confirmaciones que ya hayas combinado y fusionado se listarán en la solicitud de extracción nueva. También podrías tener conflictos que tienes que resolver constantemente en cada solicitud de extracción sucesiva. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)". +- Es posible que sea más difícil usar algunos comandos de Git que usan el ID "SHA" o "hash", ya que se pierde el ID SHA para las confirmaciones originales. Por ejemplo, es posible que no sea tan efectivo usar [`git rerere`](https://git-scm.com/docs/git-rerere). + +Para obtener más información, consulta "[Configurar la combinación de confirmaciones para las solicitudes de extracción](/articles/configuring-commit-squashing-for-pull-requests)". + +### Cambiar de base y fusionar tus confirmaciones + +{% data reusables.pull_requests.rebase_and_merge_summary %} + +Antes de activar cambiar de base las confirmaciones, considera estas desventajas: +- Es posible que los colaboradores del repositorio tengan que cambiar de base en la línea de comandos, resolver cualquier conflicto y realizar un empuje forzado de sus cambios a la rama de tema de la solicitud de extracción (o rama de encabezado remota) antes de poder usar la opción **cambiar de base y fusionar** en {% data variables.product.product_location %}. El empuje forzado se debe realizar cuidadosamente para que los colaboradores no sobreescriban un trabajo en el que otros se hayan basado. Para conocer más sobre cuando la opción **Cambiar de base y fusionar** está desactivada en {% data variables.product.product_location %} y el flujo de trabajo para volver a activarlo, consulta "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)". + +Para obtener más información, consulta [Configurar el cambio de base de las solicitudes de extracción](/articles/configuring-commit-rebasing-for-pull-requests)". diff --git a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md new file mode 100644 index 0000000000000..59a03b1954e3c --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md @@ -0,0 +1,142 @@ +--- +title: Acerca de las ramas protegidas +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/about-protected-branches + - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### About branch protection rules + +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. + +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. + +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." + +{% data reusables.pull_requests.you-can-auto-merge %} + +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [Requerir confirmaciones firmadas](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. Para obtener información acerca de las ramas base, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +Las verificaciones de estado requeridas garantizan que todas las pruebas de integración continua (CI) requeridas sean aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. Para obtener más información, consulta "[Configurar ramas protegidas](/articles/configuring-protected-branches/)" y "[Activar verificaciones de estado requeridas](/articles/enabling-required-status-checks)". Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/github/collaborating-with-issues-and-pull-requests/about-status-checks)". + +Antes de que puedas habilitar las verificaciones de estado requeridas, debes configurar el repositorio para utilizar la API de estado. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. Una vez que hayan pasado todas las verificaciones de estado requeridas, cualquier confirmación deberá ya sea subirse en otra rama y después fusionarse, o subirse directo a la rama protegida. + +{% note %} + +**Nota:** Cualquier persona o integración con permisos de escritura en un repositorio puede establecer el estado de cualquier comprobación de estado en el repositorio. {% data variables.product.company_short %} no verifica que el autor de una comprobación está autorizado para crear un determinado nombre o modificar un estado existente. Antes de fusionar una solicitud de extracción, deberás verificar que se esté esperando al autor de cada estado, los cuales se encuentran listados en la caja de fusión. + +{% endnote %} + +Puedes configurar las verificaciones de estado requeridas para que sean "laxas" o "estrictas". The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| Tipo de verificación de estado requerida | Parámetro | Requisitos de fusión | Consideraciones | +| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Estricta** | La casilla **Require branches to be up-to-date before merging** (Las ramas deben estar actualizadas antes de la fusión) está marcada. | La rama **debe** estar actualizada con la rama de base antes de la fusión. | Este es el comportamiento predeterminado para las verificaciones de estado requeridas. Se pueden requerir más construcciones, ya que deberás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción con la rama de base protegida. | +| **Flexible** | La casilla **Require branches to be up-to-date before merging** (Las ramas deben estar actualizadas antes de la fusión) **no** está marcada. | La rama **no debe** estar actualizada con la rama de base antes de la fusión. | Tendrás menos construcciones requeridas, ya que no necesitarás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción. Las verificaciones de estado pueden fallar después de que fusiones tu rama si hay cambios incompatibles con la rama de base. | +| **Inhabilitada** | La casilla **Require status checks to pass before merging** (Se deben superar las verificaciones de estado antes de la fusión) **no** está marcada. | La rama no tiene restricciones de fusión. | Si las verificaciones de estado requeridas no están habilitadas, los colaboradores pueden fusionar la rama en cualquier momento, independientemente de si está actualizada con la rama de base. Esto aumenta la posibilidad de cambios incompatibles. | + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### Requerir confirmaciones firmadas + +Cuando habilitas el requerir el firmado de confirmaciones en una rama, los colaboradores {% if currentVersion == "free-pro-team@latest" %}y bots{% endif %} solo podrán subir a la rama aquellas confirmaciones que se hayan firmado y verificado. Para obtener más información, consulta "[Acerca de la verificación de firmas en las confirmaciones](/articles/about-commit-signature-verification)." + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +Siempre puedes subir confirmaciones locales a la rama si estas se firmaron y verificaron. {% if currentVersion == "free-pro-team@latest" %}También puedes fusionar las confirmaciones firmadas y verificadas en la rama si utilizas una solicitud de cambios en {% data variables.product.product_name %}. Sin embargo, no puedes combinar y fusionar una solicitud de cambios en la rama en {% data variables.product.product_name %} a menos de que seas el autor de la misma.{% else %} Sin embargo, no puedes fusionar una solicitud de cambios en la rama en {% data variables.product.product_name %}.{% endif %} Puedes {% if currentVersion == "free-pro-team@latest" %}combinar y {% endif %} fusionar solicitudes de cambios localmente. Para obtener más información, consulta la sección "[Revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. Esto significa que cualquier solicitud de extracción fusionada con la rama protegida deberá utilizar una fusión combinada o una fusión de rebase. A strictly linear commit history can help teams reverse changes more easily. Para obtener más información acerca de los métodos de fusión, consulta "[Acerca de la fusión de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + +Antes de poder requerir un historial de confirmaciones linear, tu repositorio deberá permitir fusiones combinadas o fusiones de rebase. Para obtener más información, consulta "[Configurar las fusiones de solicitud de extracción](/github/administering-a-repository/configuring-pull-request-merges)." + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using +{% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +Cuando habilitas las restricciones de rama, solo los usuarios, equipos o apps a los que se les haya dado permisos pueden subir información a la rama protegida. Puedes ver y editar los usuarios, equipos o apps con acceso de escritura a una rama protegida en la configuración de la misma. + +Solo puedes dar acceso de escritura a una rama protegida para usuarios, equipos o {% data variables.product.prodname_github_apps %} instaladas con acceso de tipo write a un repositorio. Las personas y apps con permisos administrativos en un repositorio siempre pueden subir información a una rama protegida. + +#### Allow force pushes + +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. Cuando habilitas estas subidas forzadas en una rama protegida, cualquiera que tenga privilegios por lo menos de escritura en ese repositorio puede forzar la subida de información a la rama, incluyendo aquellos con permisos de administrador. + +Habilitar las subidas forzadas no invalidará ninguna otra regla de protección a la rama. Por ejemplo, si una rama requiere un historial de confirmaciones linear, no puedes forzar la subida de fusión de confirmaciones en esa rama. + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}No puedes habilitar las subidas forzadas para una rama protegida si un administrador de sitio las bloqueó en todas las ramas de tu repositorio. Para obtener más información, consulta "[Bloquear las subidas de información forzadas en los repositorios que sean propiedad de una organización o cuenta de usuario](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." + +Si un administrador de sitio ha bloqueado las subidas de información forzadas en la rama predeterminada únicamente, entonces aún puedes habilitarlas en cualquier otra rama protegida.{% endif %} + +#### Allow deletions + +Por defecto, no puedes eliminar una rama protegida. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/es-ES/content/github/administering-a-repository/about-releases.md b/translations/es-ES/content/github/administering-a-repository/about-releases.md new file mode 100644 index 0000000000000..baa2fe5efc1aa --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-releases.md @@ -0,0 +1,47 @@ +--- +title: Acerca de los lanzamientos +intro: 'Puedes crear un lanzamiento para empaquetar software, junto con notas de lanzamiento y enlaces a archivos binarios, para que los usen otras personas.' +redirect_from: + - /articles/downloading-files-from-the-command-line/ + - /articles/downloading-files-with-curl/ + - /articles/about-releases + - /articles/getting-the-download-count-for-your-releases + - /github/administering-a-repository/getting-the-download-count-for-your-releases +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los lanzamientos + +![Un resumen de los lanzamientos](/assets/images/help/releases/releases-overview.png) + +Los lanzamientos son iteraciones de software desplegable que puedes empaquetar y poner a disposición de una audiencia más amplia para su descarga y uso. + +Los lanzamientos se basan en las [etiquetas Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcan un punto específico en el historial de tu repositorio. Una fecha de etiqueta puede ser diferente a una fecha de lanzamiento ya que ambas pueden crearse en momentos diferentes. Para obtener más información sobre cómo visualizar tus etiquetas existentes, consulta "[Ver las etiquetas y lanzamientos de tu repositorio](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." + +Puedes recibir notificaciones cuando se publican nuevos lanzamientos en un repositorio sin recibir notificaciones sobre otras actualizaciones del repositorio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Ver tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Observar y dejar de observar los lanzamientos de un repositorio](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}". + +Cualquiera que tenga acceso de lectura a un repositorio podrá ver y comparar los lanzamientos, pero únicamente aquellos con permisos de escritura en éste podrán administrarlos. Para obtener más información, consulta "[Administrar lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +Las personas con permisos administrativos en un repositorio pueden elegir si +los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos ZIP y TAR que {% data variables.product.product_name %} crea para cada lanzamiento. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Si un lanzamiento arregla una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio. +{% data variables.product.prodname_dotcom %} revisa cada asesoría de seguridad que se publica y podría utilizarla para enviar {% data variables.product.prodname_dependabot_alerts %} a los repositorios afectados. Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". + +Puedes ver la pestaña de **Dependientes** de la gráfica de dependientes para ver qué repositorios y paquetes dependen del código en tu repositorio, y podrían entonces verse afectados con un nuevo lanzamiento. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +{% endif %} + +También puedes usar la API de releases para recopilar información, como la cantidad de veces que las personas descargan un recurso de lanzamiento. Para obtener más información, consulta la sección "[Lanzamientos](/rest/reference/repos#releases)." + +{% if currentVersion == "free-pro-team@latest" %} +### Cuotas de ancho de banda y de almacenamiento + + Cada archivo incluido en un lanzamiento debe ser de menos de {% data variables.large_files.max_file_size %}. No hay un límite para el tamaño total de un lanzamiento, ni para el uso de ancho de banda. + +{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md b/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md new file mode 100644 index 0000000000000..2d18408607cd5 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md @@ -0,0 +1,74 @@ +--- +title: Acerca del escaneo de secretos +intro: '{% data variables.product.product_name %} escanea repositorios para encontrar tipos conocidos de secretos para prevenir el uso fraudulento de aquellos que se confirmaron por accidente.' +product: '{% data reusables.gated-features.secret-scanning %}' +redirect_from: + - /github/administering-a-repository/about-token-scanning + - /articles/about-token-scanning + - /articles/about-token-scanning-for-private-repositories +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +Si tu proyecto se comunica con un servicio externo, puedes utilizar un token o llave privada para autenticación. Los tokens y llaves privadas son ejemplos de secretos que puede emitir un proveedor de servicios. Si registras un secreto en un repositorio, cualquiera que tenga acceso de lectura al mismo puede utilizarlo para acceder al servicio externo con tus privilegios. Te recomendamos que almacenes los secretos en una ubicación dedicada y segura fuera del repositorio de tu proyecto. +Service providers can partner with + +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} + +{% data reusables.secret-scanning.about-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +### Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios públicos + +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. Cuando subes información a un repositorio público, {% data variables.product.product_name %} escanea el contenido de las confirmaciones para los secretos. Si cambias un repositorio de privado a público, {% data variables.product.product_name %} escanea todo el repositorio en busca de secretos. + +Cuando {% data variables.product.prodname_secret_scanning %} detecta un conjunto de credenciales, notificamos al proveedor del servicio que emitió el secreto. El proveedor del servicio valida la credencial y luego decide si debería retirar el secreto, emitir uno nuevo, o contactarte directamente, lo cual dependerá de los riesgos asociados a ti o a dicho proveedor. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." + +Actualmente, {% data variables.product.product_name %} escanea los repositorios públicos en busca de secretos emitidos por los siguientes proveedores de servicios. + +{% data reusables.secret-scanning.partner-secret-list-public-repo %} + +### Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios privados +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} + +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} + +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." + +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. + +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. + +- {% data variables.product.prodname_dotcom %} envía una alerta por correo electrónico a los administradores del repositorio y a los propietarios de la organización. + +- {% data variables.product.prodname_dotcom %} muestra una alerta en el repositorio. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)". + +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} + +{% note %} + +**Nota:**{% data variables.product.prodname_secret_scanning_caps %} no permite actualmente que definas tus propios parámetros para detectar secretos. + +{% endnote %} + +### Further reading + +- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md new file mode 100644 index 0000000000000..437f1b576dbe5 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md @@ -0,0 +1,64 @@ +--- +title: Acerca de asegurar tu repositorio +intro: '{% data variables.product.product_name %} proporciona varias formas para que puedas mantener tu repositorio seguro.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### Configurar tu repositorio de forma segura + +El primer paso para asegurar un repositorio es configurar quién puede ver y modificar tu código. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)". + +### Asegurar tu repositorio + +{% data variables.product.prodname_dotcom %} cuenta con un conjunto de características cada vez mayor que te ayuda a mantener tu código seguro. Puedes encontrarlas en la pestaña de **Seguridad** de tu repositorio. + +{% if currentVersion == "free-pro-team@latest" %} +- **Política de seguridad** + + Facilítale a las personas el poder reportar de forma confidencial las vulnerabilidades de seguridad que hayan encontrado en tu repositorio. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)". + +- **Asesorías de seguridad** + + Debate en privado y arregla las vulnerabilidades de seguridad en el código de tu repositorio. Puedes entonces publicar la asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad en cuestión y alentarlos a mejorar la versión que tienen actualmente. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". + +- **{% data variables.product.prodname_dependabot_alerts %} y actualizaciones de seguridad** + + Ver alertas acerca de las dependencias de las cuales se sabe contienen vulnerabilidades de seguridad y elige si se generarán automáticamente las solicitudes de extracción para actualizar dichas dependencias. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + {% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **Las actualizaciones de versión del {% data variables.product.prodname_dependabot %}** +Use + + {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. Esto te ayuda a reducir tu exposición a las versiones anteriores de las dependencias. El utilizar versiones más nuevas facilita aún más la aplicación de parches si se descubren las vulnerabilidades de seguridad, y también facilita que las {% data variables.product.prodname_dependabot_security_updates %} levante las solicitudes de cambios exitosamente para mejorar las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". + {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +- **Alertas de {% data variables.product.prodname_code_scanning_capc %}** + + Detecta automáticamente las vulnerabilidades de seguridad y los errores de código en el código nuevo o modificado. Se resaltan los problemas potenciales, con información detallada, lo cual te permite arreglar el código antes de que se fusione en tu rama predeterminada. Para obtener más información, consulta la sección "[Acerca del escaneo de código"](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning). + +- **Secretos detectados** +View any secrets that + + {% data variables.product.prodname_dotcom %} has found in your code. Deberías tratar a los tokens o las credenciales que se hayan registrado en tu repositorio como puestos en riesgo. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). + {% endif %} + +### Explorar las dependencias +La gráfica de dependencias de {% data variables.product.prodname_dotcom %} te permite explorar: + +* Ecosistemas y paquetes de los cuales depende tu repositorio +* Repositorios y paquetes que dependen de tu repositorio + +Debes habilitar la gráfica de dependencias antes de que {% data variables.product.prodname_dotcom %} pueda generar {% data variables.product.prodname_dependabot_alerts %} para las dependencias con vulnerabilidades de seguridad. + +Puedes encontrar la gráfica de dependencias en lapestaña de **Perspectivas** para tu repositorio. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". diff --git a/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md b/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md new file mode 100644 index 0000000000000..1607b01f85b6a --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md @@ -0,0 +1,30 @@ +--- +title: Automatización de los formularios de lanzamiento con parámetros de consulta +intro: 'Para crear lanzamientos al completar automáticamente el nuevo formulario de lanzamiento con información personalizada, puedes agregar los parámetros de consulta a la URL para la página del formulario de lanzamiento.' +redirect_from: + - /articles/automation-for-release-forms-with-query-parameters +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los parámetros de consulta son partes opcionales de una URL que puedes personalizar para compartir una vista de página web específica, como los resultados de filtro de búsqueda, una plantilla de propuestas o la página del formulario de lanzamiento en {% data variables.product.prodname_dotcom %}. Para crear tus propios parámetros de consulta, debes hacer coincidir el par de clave y valor. + +Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para crear lanzamientos para completar previamente los formularios de lanzamiento. Para obtener más información, consulta "[Administrar lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)." + +Si creas una URL no válida usando los parámetros de consulta o si no tienen los permisos adecuados, la URL devolverá una página de error 404. + +### Parámetros de consulta admitidos + +| Parámetro de consulta | Ejemplo | +| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `tag` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1` create un lanzamiento en función de la etiqueta denominada "v1.0.1". | +| `destino` | `https://github.com/octo-org/octo-repo/releases/new?target=release-1.0.1` create un lanzamiento en función de la última confirmación a la rama "release-1.0.1". | +| `título` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1&title=octo-1.0.1` crea un lanzamiento denominado "octo-1.0.1" basado en una etiqueta denominada "v1.0.1". | +| `body` | `https://github.com/octo-org/octo-repo/releases/new?body=Adds+widgets+support` crea un lanzamiento con la descripción "Adds widget support" (Agrega soporte de widget) en el cuerpo del lanzamiento. | +| `lanzamiento previo` | `https://github.com/octo-org/octo-repo/releases/new?prerelease=1` crea un lanzamiento que será identificado como listo para no producción. | + +### Further reading + +- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" diff --git a/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md new file mode 100644 index 0000000000000..486536ab1fd0b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md @@ -0,0 +1,62 @@ +--- +title: Cambiar la rama predeterminada +intro: 'Si tienes màs de una rama en tu repositorio, puedes configurar cualquiera de ellas como la predeterminada.' +permissions: Las personas con permisos administrativos en un repositorio pueden cambiar la rama predeterminada para el mismo. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /github/administering-a-repository/setting-the-default-branch + - /articles/setting-the-default-branch +--- + +### Acerca de cambiar la rama predeterminada + +Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base para las solicitudes de cambios y confirmaciones de còdigo. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". + +{% if currentVersion != "github-ae@latest" %} +{% note %} + +**Nota**: Si utilizas el puente de Git-Subversion, el cambiar la rama predeterminada afectarà al contenido de tu rama `trunk` y al `HEAD` que ves cuando listas las referencias para el repositorio remoto. Para obtener màs informaciòn, consulta la secciòn "[Soporte para los clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)" y a [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) en la documentaciòn de Git. + +{% endnote %} +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +{% data reusables.branches.set-default-branch %} + +{% endif %} + +### Prerrequisitos + +Para cambiar la rama predeterminada, tu repositorio debe tener màs de una rama. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)". + +### Cambiar la rama predeterminada + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. Debajo de "Rama predeterminada", a la derecha del nombre de rama predeterminado, da clic en el {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Cambiar el icono con dos flechas hacia la derecha del nombre de la rama predeterminada actual](/assets/images/help/repository/repository-options-defaultbranch-change.png) +1. Utiliza el menù desplegable y luego da clic en el nombre de una rama. ![Menù desplegable para elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) +1. Da clic en **Actualizar**. ![Botòn de "Update" despuès de elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-update.png) +1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** ![Botòn de "Update" despuès de elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) + +{% else %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. En el menú desplegable de la rama predeterminada, elige la rama predeterminada nueva. ![Selector desplegable de la rama por defecto](/assets/images/help/repository/repository-options-defaultbranch.png) +1. Da clic en **Actualizar**. + +{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/es-ES/content/github/administering-a-repository/classifying-your-repository-with-topics.md new file mode 100644 index 0000000000000..602d7bc73d64b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/classifying-your-repository-with-topics.md @@ -0,0 +1,39 @@ +--- +title: Clasificar tu repositorio con temas +intro: 'Para ayudar a otras personas a buscar y contribuir en tu proyecto, puedes agregar temas a tu repositorio relacionados con el fin previsto de tu proyecto, área temática, grupos de afinidad u otras cualidades importantes.' +redirect_from: + - /articles/about-topics/ + - /articles/classifying-your-repository-with-topics +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los temas + +En el caso de los temas, puedes explorar repositorios en un área temática particular, buscar proyectos a los cuales contribuir y descubrir nuevas soluciones para un problema específico. Los temas aparecen en la página principal de un repositorio. Puedes dar clic en el nombre de un tema para {% if currentVersion == "free-pro-team@latest" %}ver los temas relacionados y una lista de otros repositorios clasificados con ese tema{% else %}buscar otros repositorios con ese tema{% endif %}. + +![Página principal del repositorio de prueba que muestra temas](/assets/images/help/repository/os-repo-with-topics.png) + +Para explorar los temas más usados, visita https://github.com/topics/. + +{% if currentVersion == "free-pro-team@latest" %}Puedes colaborar con el set de temas destacados de {% data variables.product.product_name %} en el repositorio [github/explore](https://github.com/github/explore). {% endif %} + +Los administradores del repositorio pueden agregar los temas que deseen a un repositorio. Entre los temas útiles para clasificar un repositorio se incluyen la función prevista del mismo, su área temática, comunidad o idioma.{% if currentVersion == "free-pro-team@latest" %} Adicionalmente, {% data variables.product.product_name %} analiza el contenido de los repositorios públicos y genera temas sugeridos que los administradores de éstos pueden aceptar o rechazar. El contenido del repositorio privado no se analiza y no recibe sugerencias de tema.{% endif %} + +{% if currentVersion == "github-ae@latest" %}Los repositorios internos {% else %}Públicos, internos, {% endif %}y privados pueden tener temas, aunque solo verás los repositorios privados a los cuales tengas acceso en los resultados de búsqueda por tema. + +Puedes buscar los repositorios que están asociados con un tema en particular. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)". También puedes buscar un listado de temas en {% data variables.product.product_name %}. Para obtener más información, consulta "[Buscar temas](/articles/searching-topics)". + +### Agregar temas a tu repositorio + +{% data reusables.repositories.navigate-to-repo %}{% if currentVersion ver_lt "enterprise-server@2.22" %} +2. En la descripción de tu repositorio, haz clic en **Add topics** (Agregar temas). ![Enlace para agregar temas en la página principal de un repositorio](/assets/images/help/repository/add-topics-link.png) +3. Escribe el tema que deseas agregar a tu repositorio, luego escribe un espacio. ![Formulario para ingresar temas](/assets/images/help/repository/add-topic-form.png) +4. Cuando hayas finalizado de agregar temas, haz clic en **Done** (Listo). ![Formulario con una lista de temas y botón Done (Listo)](/assets/images/help/repository/add-topics-done-button.png) +{% else %} +2. A la derecha de "Acerca de", da clic en el {% octicon "gear" aria-label="The Gear icon" %}. ![Icono de engrane en la página principal del repositorio](/assets/images/help/repository/edit-repository-details-gear.png) +3. Debajo de "Temas", teclea el tema que quieras agregar a tu repositorio y después teclea un espacio. ![Formulario para ingresar temas](/assets/images/help/repository/add-topic-form.png) +4. Después de que termines de agregar los temas, da clic en **Guardar cambios**. ![Botón de "Guardar cambios" en "Editar los detalles del repositorio"](/assets/images/help/repository/edit-repository-details-save-changes-button.png) +{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/comparing-releases.md b/translations/es-ES/content/github/administering-a-repository/comparing-releases.md new file mode 100644 index 0000000000000..e2308daa83c2b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/comparing-releases.md @@ -0,0 +1,14 @@ +--- +title: Comparar lanzamientos +intro: Puedes comparar etiquetas de lanzamiento para ver los cambios en tu repositorio entre diferentes lanzamientos. +permissions: Las personas con acceso de lectura a un repositorio podrán ver y comparar los lanzamientos. +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Da clic en **Comparar** a un costado del lanzamiento que deseas utilizar como tu base. ![Menú de comparación de etiquetas de lanzamiento](/assets/images/help/releases/compare-tags-menu.png) +4. Utiliza el menú desplegable "Comparar" y selecciona las etiquetas que quieras comparar. ![Opciones del menú de comparación de etiquetas de lanzamiento](/assets/images/help/releases/compare-tags-menu-options.png) diff --git a/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md new file mode 100644 index 0000000000000..ab50a586b9ecb --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -0,0 +1,619 @@ +--- +title: Opciones de configuración para actualizaciones de dependencias +intro: 'La información detallada para todas las opciones que puedes utilizar para personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus repositorios.' +permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar el {% data variables.product.prodname_dependabot %} para el mismo.' +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca del archivo *dependabot.yml* + +El archivo de configuración del {% data variables.product.prodname_dependabot %}, *dependabot.yml*, utiliza la sintaxis YAML. Si eres nuevo en YAML y deseas conocer más, consulta "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". + +Debes almacenar este archivo en el directorio `.github` de tu repositorio. Cuando agregas o actualizas el archivo *dependabot.yml*, esto activa una revisión inmediata de las actualizaciones de la versión. Cualquier opción que también afecte las actualizaciones de seguridad se utiliza en la siguiente ocasión en que una alerta de seguridad active una solicitud de cambios para una actualización de seguridad. Para obtener más información, consulta las secciónes "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". + +### Opciones de configuración para *dependabot.yml* + +El archivo *dependabot.yml* debe comenzar con `version: 2`, seguido de un conjunto de `updates`. + +| Opción | Requerido | Descripción | +|:-------------------------------------------------------------------------- |:---------:|:--------------------------------------------------------------------------------------------- | +| [`package-ecosystem`](#package-ecosystem) | **X** | Administrador de paquetes a utilizar | +| [`directory`](#directory) | **X** | Ubicación de los manifiestos del paquete | +| [`schedule.interval`](#scheduleinterval) | **X** | Qué tan a menudo se revisará si hay actualizaciones | +| [`allow`](#allow) | | Personalizar qué actualizaciones se permitirán | +| [`asignatarios`](#assignees) | | Los asignados a configurar en las solicitudes de extracción | +| [`commit-message`](#commit-message) | | Preferencias de mensaje de confirmación | +| [`ignore`](#ignore) | | Ignorar ciertas dependencias o versiones | +| [`etiquetas`](#labels) | | Las etiquetas a configurar en las solicitudes de extracción | +| [`milestone`](#milestone) | | Hito a configurar en las solicitudes de extracción | +| [`open-pull-requests-limit`](#open-pull-requests-limit) | | Limitar la cantidad de solicitudes de extracción abiertas para las actualizaciones de versión | +| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | Cambiar el separador para los nombres de rama de la solicitud de extracción | +| [`rebase-strategy`](#rebase-strategy) | | Inhabilitar el rebase automático | +| [`reviewers`](#reviewers) | | Los revisores a configurar en las solicitudes de extracción | +| [`schedule.day`](#scheduleday) | | Día de la semana para revisar si hay actualizaciones | +| [`schedule.time`](#scheduletime) | | Hora del día para revisar si hay actualizaciones (hh:mm) | +| [`schedule.timezone`](#scheduletimezone) | | Huso horario para la hora del día (identificador de zona) | +| [`target-branch`](#target-branch) | | Rama contra la cual se creará la solicitud de extracción | +| [`vendor`](#vendor) | | Actualiza las dependencias delegadas a proveedores o almacenadas en caché | +| [`versioning-strategy`](#versioning-strategy) | | Cómo actualizar los requisitos de la versión del manifiesto | + +Estas opciones caen a groso modo en las siguientes categorías. + +- Opciones de configuración esenciales que debes incluir en todas las configuraciones: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval). +- Opciones para personalizar el calendario de actualización: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday). +- Las opciones para controlar qué dependencias se actualizarán: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor). +- Opciones para agregar metadatos a las solicitudes de extracción: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone). +- Opciones para cambiar el comportamiento de las solicitudes de extracción: [`target-branch`](#target-branch), [`versioning-strategy`](#versioning-strategy), [`commit-message`](#commit-message), [`rebase-strategy`](#rebase-strategy), [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator). + +Adicionalmente, la opción [`open-pull-requests-limit`](#open-pull-requests-limit) cambia la cantidad máxima de solicitudes de extracción para las actualizaciones de versión que puede abrir el {% data variables.product.prodname_dependabot %}. + +{% note %} + +**Nota:** Algunas de estas opciones de configuración también pueden afectar a las solicitudes de extracción que se levantan para las actualizaciones de seguridad de los manifiestos delos paquetes vulnerables. + +Las actualizaciones de seguridad se levantan para los manifiestos de paquetes vulnerables únicamente en la rama predeterminada. Cuando se establecen las opciones de configuración para la misma rama (como "true" a menos de que utilices `target-branch`), y se especifica un `package-ecosystem` y `directory` para el manifiesto vulnerable, entonces las solicitudes de extracción para las actualizaciones de seguridad utilizan las opciones relevantes. + +En general, las actualizaciones de seguridad utilizan cualquier opción de configuración que afecte las solicitudes de extracción, por ejemplo, agregar metadatos o cambiar su comportamiento. Para obtener más información acerca de las actualizaciones de seguridad, consulta la sección "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". + +{% endnote %} + +### `package-ecosystem` + +**Requerido** Agregas un elemento de `package-ecosystem` para cada administrador de paquetes que quieras que el {% data variables.product.prodname_dependabot %} monitoree para revisar si hay nuevas versiones. El repositorio también debe contener un archivo bloqueado o de manifiesto de dependencias para cada uno de estos administradores de paquetes. Si quieres habilitar la delegación a proveedores para un administrador de paquetes que sea compatible con ella, las dependencias delegadas a proveedores deben ubicarse en el directorio requerido. Para obtener más información, consulta la sección [`vendor`](#vendor) a continuación. + +{% data reusables.dependabot.supported-package-managers %} + +```yaml +# Basic set up for three package managers + +version: 2 +updates: + + # Maintain dependencies for GitHub Actions + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "daily" + + # Maintain dependencies for npm + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + + # Maintain dependencies for Composer + - package-ecosystem: "composer" + directory: "/" + schedule: + interval: "daily" +``` + +### `directory` + +**Requerido** Debes definir la ubicación de los manifiestos de paquete para cada administrador de paquete (por ejemplo, el *package.json* o *Gemfile*). Tú definierás el directorio relativo a la raíz del repositorio para todos los ecosistemas, menos para GitHub Actions. Para GitHub Actions, configura el directorio para que sea `/` y así revisar los archivos de flujo de trabajo en `.github/workflows`. + +```yaml +# Specify location of manifest files for each package manager + +version: 2 +updates: + - package-ecosystem: "composer" + # Files stored in repository root + directory: "/" + schedule: + interval: "daily" + + - package-ecosystem: "npm" + # Files stored in `app` directory + directory: "/app" + schedule: + interval: "daily" + + - package-ecosystem: "github-actions" + # Workflow files stored in the + # default location of `.github/workflows` + directory: "/" + schedule: + interval: "daily" +``` + +### `schedule.interval` + +**Requerido** Debes definir qué tan a menudo se debe revisar si hay nuevas versiones y levantar solicitudes de extracción para las actualizaciones de versión en cada administrador de paquetes. Predeterminadamente, esto ocurre a las 5am UTC. Para modificar esto, utiliza [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone). + +- `daily`—se ejecuta en cada día de la semana, de Lunes a Viernes. +- `weekly`—se ejecuta una vez cada semana. Predeterminadamente, esto ocurre los lunes. Para modificar esto, utiliza [`schedule.day`](#scheduleday). +- `monthly`—se ejecuta una vez al mes. Esto ocurre en el primer día de cada mes. + +```yaml +# Set update schedule for each package manager + +version: 2 +updates: + + - package-ecosystem: "github-actions" + directory: "/" + schedule: + # Check for updates to GitHub Actions every weekday + interval: "daily" + + - package-ecosystem: "composer" + directory: "/" + schedule: + # Check for updates managed by Composer once a week + interval: "weekly" +``` + +### `allow` + +{% data reusables.dependabot.default-dependencies-allow-ignore %} + +Utiliza la opción `allow` para personalizar qué dependencias se actualizan. Esto no impacta en las actualizaciones de seguridad para las dependencias vulnerables. Puedes utilizar las siguientes opciones: + +- `dependency-name`—se utiliza para permitir actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`. +- `dependency-type`—utilízalo para permitir actualizaciones para dependencias de tipos específicos. + + | Tipos de dependencia | Administradores de paquete compatibles | Permitir actualizaciones | + | -------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | + | `direct` | Todas | Todas las dependencias definidas explícitamente. | + | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Las dependencias de las dependencias directas (también conocidas como sub-dependencias, o dependencias transitorias). | + | `all` | Todas | Todas las dependencias definidas explícitamente. Para `bundler`, `pip`, `composer`, `cargo`, también las dependencias de las dependencias directas. | + | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Únicamente las dependencias en el "Grupo de dependencias del producto". | + | `development` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Únicamente las dependencias en el "Grupo de dependencias de desarrollo". | + +```yaml +# Customizing the dependencies to maintain with `allow` + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + allow: + # Allow updates for Lodash + - dependency-name: "lodash" + # Allow updates for React and any packages starting "react" + - dependency-name: "react*" + + - package-ecosystem: "composer" + directory: "/" + schedule: + interval: "daily" + allow: + # Allow both direct and indirect updates for all packages + - dependency-type: "all" + + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + allow: + # Allow only direct updates for + # Django and any packages starting "django" + - dependency-name: "django*" + dependency-type: "direct" + # Allow only production updates for Sphinx + - dependency-name: "sphinx" + dependency-type: "production" +``` + +### `asignatarios` + +Utiliza `assignees` para especificar a los asignados individuales para todas las solicitudes de extracción levantadas para un administrador de paquete. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Specify assignees for pull requests + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Add assignees + assignees: + - "octocat" +``` + +### `commit-message` + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} intenta detectar tus preferencias de mensajes de confirmación y utiliza patrones similares. Utiliza la opción`commit-message` para especificar tus preferencias explícitamente. + +Opciones compatibles + +- `prefix` especifica un prefijo para todos los mensajes de confirmación. +- `prefix-development` especifica un prefijo separado para todos los mensajes de confirmación que actualizan dependencias en el grupo de dependencias de desarrollo. Cuando especificas un valor para esta opción, `prefix` se utiliza únicamente para las actualizaciones a las dependencias en el grupo de dependencias de producción. Esto es compatible con: `bundler`, `composer`, `mix`, `maven`, `npm`, y `pip`. +- `include: "scope"` especifica que cualquier prefijo es sucedido por una lista de dependencias actualizadas en la confirmación. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Customizing commit messages + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + commit-message: + # Prefix all commit messages with "npm" + prefix: "npm" + + - package-ecosystem: "composer" + directory: "/" + schedule: + interval: "daily" + # Prefix all commit messages with "Composer" + # include a list of updated dependencies + commit-message: + prefix: "Composer" + include: "scope" + + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + # Include a list of updated dependencies + # with a prefix determined by the dependency group + commit-message: + prefix: "pip prod" + prefix-development: "pip dev" + include: "scope" +``` + +### `ignore` + +{% data reusables.dependabot.warning-ignore-option %} + +#### Revisar por preferencias ignoradas existentes + +Antes de que agreges una opción de `ignore` al archivo de configuración, revisa si has utilizado previamente cualquiera de los comandos de `@dependabot ignore` en una solicitud de extracción de actualizaciones de seguridad o de versión. El {% data variables.product.prodname_dependabot %} almacena estas preferencias para cada administrador de paquetes centralmente, y esta información se sobreescribe mediante la opción `ignore`. Para obtener más información acerca de los comandos de `@dependabot ignore`, consulta la sección "[Administrar las solicitudes de extracción para las actualizaciones de dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)". + +Puedes revisar si un repositorio ha almacenado las preferencias si buscas dicho repositorio con `"@dependabot ignore" in:comments`. Si revias alguna solicitud de extracción en los resultados, puedes decidir si quieres o no especificar esas dependencias o versiones ignoradas en el archivo de configuración. + +#### Especificar dependencias y versiones para ignorar + +{% data reusables.dependabot.default-dependencies-allow-ignore %} + +Puedes utilizar la opción `ignore` para personalizar qué dependencias se actualizarán. La opción `ignore` es compatible con las siguientes opciones. + +- `dependency-name`—se utiliza para ignorar actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`. +- `versions`—se utiliza para ignorar versiones o rangos específicos de las versiones. Si quieres definir un rango, utiliza el patrón estándar del administrador de paquetes (por ejemplo: `^1.0.0` para npm, o `~> 2.0` para Bundler). + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Customizing the dependencies to maintain with `ignore` + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + ignore: + - dependency-name: "express" + # For Express, ignore all updates for version 4 and 5 + versions: ["4.x", "5.x"] + # For Lodash, ignore all updates + - dependency-name: "lodash" +``` + +{% note %} + +**Nota**: El {% data variables.product.prodname_dependabot %} solo puede ejecutar actualizaciones de versión en los archivos de bloqueo o de manifiesto si puede acceder a todas las dependencias en estos archivos, aún si agregas dependencias inaccesibles a la opción `ignore` de tu archivo de configuración. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y deanálisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)" y "[Solucionar los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". + + +{% endnote %} + +### `etiquetas` + +{% data reusables.dependabot.default-labels %} + +Utiliza `labels` para anular las etiquetas predeterminadas y especificar las etiquetas alternas para todas las solicitudes de extracción que se levante para un administrador de paquete. Si ninguna de estas etiquetas se define en el repositorio, entonces se ha ignorado. Para inhabilitar todas las etiquetas, incluyendo aquellas predeterminadas, utiliza `labels: [ ]`. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Specify labels for pull requests + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Specify labels for npm pull requests + labels: + - "npm" + - "dependencies" +``` + +### `milestone` + +Utiliza `milestone` para asociar todas las solicitudes de extracción que se han levantado para un administrador de paquete con un hito. Necesitas especificar el identificador numérico del hito y, no así, su etiqueta. Si ves un hito, la parte final de la URL de la página, después de `milestone`, es el identificador. Por ejemplo: `https://github.com///milestone/3`. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Specify a milestone for pull requests + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Associate pull requests with milestone "4" + milestone: 4 +``` + +### `open-pull-requests-limit` + +Predeterminadamente, {% data variables.product.prodname_dependabot %} abre un máximo de cinco solicitudes de extracción para las actualizaciones de versión. Una vez que haya cinco solicitudes de extracción abiertas, las nuevas solicitudes se bloquearán hasta que fusiones o cierres alguna de las que están abiertas. Utiliza `open-pull-requests-limit` para cambiar este límite. Esto también proporciona una forma simple de inhabilitar temporalmente las actualizaciones de versión para un administrador de paquete. + +Esta opción no tiene impacto en las actualizaciones de seguridad que tienen un límite separado e interno de diez solicitudes de extracción abiertas. + +```yaml +# Changing the number of open pull requests allowed + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Disable version updates for npm dependencies + open-pull-requests-limit: 0 + + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + # Allow up to 10 open pull requests for pip dependencies + open-pull-requests-limit: 10 +``` + +### `pull-request-branch-name.separator` + +El {% data variables.product.prodname_dependabot %} genera una rama para cada solicitud de extracción. Cada nombre de rama incluye `dependabot`, y el administrador de paquete y la dependencia que se actualizaron. Predeterminadamente, estas partes están separadas por un símbolo de `/`, por ejemplo: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`. + +Utiliza `pull-request-branch-name.separator` para especificar un separador diferente. Este puede ser alguno de entre: `"-"`, `_` o `/`. El símbolo de guión debe estar entre comillas porque, de lo contrario, se interpretará como que está declarando una lista YAML vacía. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Specifying a different separator for branch names + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + pull-request-branch-name: + # Separate sections of the branch name with a hyphen + # for example, `dependabot-npm_and_yarn-next_js-acorn-6.4.1` + separator: "-" +``` + +### `rebase-strategy` + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción abiertas cuando detecta conflictos. Utiliza `rebase-strategy` para inhabilitar este comportamiento. + +Estrategias de rebase disponibles + +- `disabled` para inhabilitar el rebase automático. +- `auto` para utilizar el comportamiento predeterminado y rebasar las solicitudes de extracción abiertas cuando se detecten conflictos. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Disabling automatic rebasing + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Disable rebasing for npm pull requests + rebase-strategy: "disabled" +``` + +### `reviewers` + +Utiliza `reviewers` para especificar los revisores o equipos individuales de revisores para las solicitudes de extracción que se levantaron para un administrador de paquete. Debes utilizar el nombre completo del equipo, incluyendo la organización, como si lo estuvieras @mencionando. + +{% data reusables.dependabot.option-affects-security-updates %} + +```yaml +# Specify reviewers for pull requests + +version: 2 +updates: + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + # Add reviewers + reviewers: + - "octocat" + - "my-username" + - "my-org/python-team" +``` + +### `schedule.day` + +Cuando configuras un calendario de actualización en `weekly`, predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa las nuevas versiones los lunes a las 05:00 UTC. Utiliza `schedule.day` para especificar un día alterno para revisar si hay actualizaciones. + +Valores compatibles + +- `monday` +- `tuesday` +- `wednesday` +- `thursday` +- `friday` +- `saturday` +- `sunday` + +```yaml +# Specify the day for weekly checks + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "weekly" + # Check for npm updates on Sundays + day: "sunday" +``` + +### `schedule.time` + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Utiliza `schedule.time` para especificar una hora alterna para revisar si hay actualizaciones (formato: `hh:mm`). + +```yaml +# Set a time for checks +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Check for npm updates at 9am UTC + time: "09:00" +``` + +### `schedule.timezone` + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Utiliza `schedule.timezone` para especificar un huso horario alternativo. El identificador de zona debe ser tomado de la base de datos de Husos Horarios que mantiene [iana](https://www.iana.org/time-zones). Para obtener más información, consulta la [Lista de bases de datos tz para husos horarios](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). + +```yaml +# Specify the timezone for checks + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + time: "09:00" + # Use Japan Standard Time (UTC +09:00) + timezone: "Asia/Tokyo" +``` + +### `target-branch` + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay archivos de manifiesto en las ramas predeterminadas y levanta solicitudes de extracción para las actualizaciones de versión contra dicha rama. Utiliza `target-branch` para especificar una rama diferente para los archivos de manifiesto y para las solicitudes de extracción. Cuando utilizas esta opción, la configuración para este administrador de paquete ya no afectará ninguna solicitud de extracción que se haya levantado para las actualizaciones de seguridad. + +```yaml +# Specify a non-default branch for pull requests for pip + +version: 2 +updates: + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + # Raise pull requests for version updates + # to pip against the `develop` branch + target-branch: "develop" + # Labels on pull requests for version updates only + labels: + - "pip dependencies" + + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "weekly" + # Check for npm updates on Sundays + day: "sunday" + # Labels on pull requests for security and version updates + labels: + - "npm dependencies" +``` + +### `vendor` + +Utiliza la opción `vendor` para indicar al {% data variables.product.prodname_dependabot %} delegar las dependencias a los proveedores cuando se actualicen. + +```yaml +# Configure version updates for both dependencies defined in manifests and vendored dependencies + +version: 2 +updates: + - package-ecosystem: "bundler" + # Raise pull requests to update vendored dependencies that are checked in to the repository + vendor: true + directory: "/" + schedule: + interval: "weekly" +``` + +El {% data variables.product.prodname_dependabot %} solo actualiza las dependencias delegadas a proveedores que se ubiquen en directorios específicos en un repositorio. + +| Administración de paquetes | Ruta de archivo requerida para las dependencias delegadas | Más información | +| -------------------------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- | +| `bundler` | Las dependencias deben estar en el directorio _vendor/cache_.
    Otras rutas de archivo no son compatibles. | [documentación de `bundle cache`](https://bundler.io/man/bundle-cache.1.html) | +| `gomod` | No hay requisitos de ruta (las dependencias se ubican habitualmente en el directorio _vendor_) | [documentación de `go mod vendor`](https://golang.org/ref/mod#go-mod-vendor) | + + +### `versioning-strategy` + +Cuando el {% data variables.product.prodname_dependabot %} edita un archivo de manifiesto para actualizar una versión, utiliza las siguientes estrategias generales: + +- Para las apps, los requisitos de versión se incrementan, por ejemplo: npm, pip y Composer. +- Para las bibliotecas, el rango de versiones se amplía, por ejemplo: Bundler y Cargo. + +Utiliza la opción `versioning-strategy` para cambiar este comportamiento para los administradores de paquete compatibles. + +{% data reusables.dependabot.option-affects-security-updates %} + +Estrategias de actualización disponibles + +| Opción | Compatible con | Acción | +| ----------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Crear únicamente solicitudes de extracción para actualizar los archivos fijados. Ignorar cualquier versión nueva que pudiera requerir cambios en el paquete del manifiesto. | +| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Seguir la estrategia predeterminada descrita anteriormente. | +| `widen` | `composer`, `npm` | Relajar el requisito de versión para que incluya tanto la versión nueva como la anterior, cuando sea posible. | +| `increase` | `bundler`, `composer`, `npm` | Siempre incrementar el requisito de versión para que empate con la versión nueva. | +| `increase-if-necessary` | `bundler`, `composer`, `npm` | Incrementar el requisito de versión únicamente cuando lo requiera la versión nueva. | + +```yaml +# Customizing the manifest version strategy + +version: 2 +updates: + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Update the npm manifest file to relax + # the version requirements + versioning-strategy: widen + + - package-ecosystem: "composer" + directory: "/" + schedule: + interval: "daily" + # Increase the version requirements for Composer + # only when required + versioning-strategy: increase-if-necessary + + - package-ecosystem: "pip" + directory: "/" + schedule: + interval: "daily" + # Only allow updates to the lockfile for pip and + # ignore any version updates that affect the manifest + versioning-strategy: lockfile-only +``` diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md b/translations/es-ES/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md new file mode 100644 index 0000000000000..705e69280d164 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md @@ -0,0 +1,23 @@ +--- +title: Configurar enlaces automáticos para referenciar recursos externos +intro: Puedes agregar enlaces automáticos a recursos externos, como propuestas de JIRA y tickets de Zendesk, para ayudar a optimizar tu flujo de trabajo. +product: '{% data reusables.gated-features.autolinks %}' +redirect_from: + - /articles/configuring-autolinks-to-reference-external-resources +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cualquiera con permisos administrativos en un repositorio puede configurar las referencias autovinculadas para vincular propuestas, solicitudes de cambios,{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} mensajes de confirmación, y descripciones de lanzamientos{% else %} y mensajes de confirmación{% endif %} a los servicios externos de terceros. + +Si usas Zendesk para hacer el seguimiento de los tickets informados por el usuario, por ejemplo, puedes referenciar un número de ticket en la solicitud de extracción que abres para corregir el problema. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). ![Pestaña Autolink references (Referencias de enlace automático) en la barra lateral izquierda](/assets/images/help/repository/autolink-references-tab.png) +4. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). ![Botón para completar con información de la referencia de enlace automático](/assets/images/help/repository/add-autolink-reference-details.png) +5. Debajo de "Reference prefix" (Prefijo de referencia), escribe un prefijo corto y significativo que quieras que los colaboradores utilicen para generar enlaces automáticos para el recurso externo. ![Campo para escribir la abreviación para el sistema externo](/assets/images/help/repository/add-reference-prefix-field.png) +6. Debajo de "Target URL" (URL de destino), escribe el enlace al sistema externo al que te quieras vinculr. Asegúrate de conservar `` como variable para el número de referencia. ![Campo para escribir la URL al sistema externo](/assets/images/help/repository/add-target-url-field.png) +7. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). ![Botón para agregar referencia de enlace automático](/assets/images/help/repository/add-autolink-reference.png) diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md b/translations/es-ES/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md new file mode 100644 index 0000000000000..77676cb679eff --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md @@ -0,0 +1,16 @@ +--- +title: Configurar rebase de confirmación para las solicitudes de extracción +intro: 'Puedes hacer cumplir, permitir o inhabilitar rebases de confirmación para todas las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} en tu repositorio.' +redirect_from: + - /articles/configuring-commit-rebasing-for-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pull_requests.configure_pull_request_merges_intro %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de rebase). Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base. Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png) diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md b/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md new file mode 100644 index 0000000000000..55ef3782e1389 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md @@ -0,0 +1,24 @@ +--- +title: Configurar combinación de confirmaciones para las solicitudes de extracción +intro: 'Puedes hacer cumplir, permitir o inhabilitar combinaciones de confirmación para todas las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} en tu repositorio.' +redirect_from: + - /articles/configuring-commit-squashing-for-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pull_requests.configure_pull_request_merges_intro %} + +{% data reusables.pull_requests.default-commit-message-squash-merge %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Merge button" (Fusionar botón), selecciona **Allow merge commits** (Permitir fusión de confirmaciones). Esto permite que los colaboradores fusionen una solicitud de extracción con un historial completo de confirmaciones. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png) +4. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de combinación). Esto permite que los colaboradores fusionen una solicitud de extracción al combinar todas las confirmaciones en una confirmación única. Si seleccionas otro método de fusión además de **Allow squash merging** (Permitir combinación de fusiones), los colaboradores podrán elegir el tipo de confirmación de fusiones al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones combinadas de solicitudes de extracción](/assets/images/help/repository/pr-merge-squash.png) + +### Further reading + +- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" +- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md b/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md new file mode 100644 index 0000000000000..e5c512b416eb7 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md @@ -0,0 +1,12 @@ +--- +title: Configurar fusiones de solicitudes de extracción +intro: 'Puedes configurar las fusiones de solicitudes de cambio en {% data variables.product.product_location %} para que coincidan con tu flujo de trabajo y con tus preferencias para administrar el historial de Git.' +mapTopic: verdadero +redirect_from: + - /articles/configuring-pull-request-merges +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..77f705197e446 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de {% data variables.product.prodname_secret_scanning %}. Por ejemplo, puedes excluir directorios que contengan pruebas o contenido generado aleatoriamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo de nombre del archivo, teclea *.github/secret_scanning.yml*. +4. Debajo de **Editar nuevo archivo**, teclea `paths-ignore:` seguido por las rutas que quieras excluir de {% data variables.product.prodname_secret_scanning %}. + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + Puedes utilizar caracteres especiales, tales como `*` para filtrar las rutas. Para obtener más información acerca de filtrar las rutas, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)". + + {% note %} + + **Notas:** + - Si hay más de 1,000 entradas en `paths-ignore`, {% data variables.product.prodname_secret_scanning %} solo excluirá de los escaneos a los primeros 1,000 directorios. + - Si *secret_scanning.yml* es mayor a 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo el archivo. + + {% endnote %} + +También puedes ignorar alertas individuales de {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)". + +### Further reading + +- "[Administrar la seguridad y la configuración de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md new file mode 100644 index 0000000000000..165327ca866ef --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md @@ -0,0 +1,18 @@ +--- +title: Configurar el periodo de retenciòn para los artefactos de GitHub Actions y las bitàcoras en tu repositorio +intro: 'Puedes configurar el periodo de retenciòn para los artefactos de las {% data variables.product.prodname_actions %} y las bitàcoras en tu repositorio.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' +--- + +{% data reusables.actions.about-artifact-log-retention %} + +Tambièn puedes definir un periodo de retenciòn personalizado para un artefacto especìfico que haya creado un flujo de trabajo. Para obtener màs informaciòn consulta la secciòn "[Configurar el periodo de retenciòn para un artefacto](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)". + +## Configurar el periodo de retenciòn para un repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/es-ES/content/github/administering-a-repository/customizing-dependency-updates.md b/translations/es-ES/content/github/administering-a-repository/customizing-dependency-updates.md new file mode 100644 index 0000000000000..3fa6039a97f16 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/customizing-dependency-updates.md @@ -0,0 +1,127 @@ +--- +title: Personalizar las actualizaciones de las dependencias +intro: 'Puedes personalizar cómo el {% data variables.product.prodname_dependabot %} mantiene tus dependencias.' +permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar el {% data variables.product.prodname_dependabot %} para el mismo.' +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca de personalizar las actualizaciones de las dependencias + +Después de que hayas habilitado la actualización de versiones, puedes personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus dependencias si agregas más opciones al archivo *dependabot.yml*. Por ejemplo, podrías: + +- Especifica en qué día de la semana se abrirán las solicitudes de extracción para la actualización de versiones: `schedule.day` +- Establece revisores, asignados y etiquetas para cada administrador de paquete: `reviewers`, `assignees`, y `labels` +- Define una estrategia de versionamiento para los cambios que se realicen en cada archivo de manifiesto: `versioning-strategy` +- Cambia la cantidad máxima de solicitudes de extracción abiertas para actualizaciones de versión del valor predeterminado que es 5: `open-pull-requests-limit` +- Abre solicitudes de extracción para actualizaciones de versión para seleccionar una rama específica en vez de la rama predeterminada: `target-branch` + +Para obtener más información acerca de las opciones de configuración, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". + +Cuando actualizas el archivo *dependabot.yml* en tu repositorio, el {% data variables.product.prodname_dependabot %} ejecuta una revisión inmediata con la nueva configuración. Verás una lista de dependencias actualizada en cuestión de minutos en la pestaña de **{% data variables.product.prodname_dependabot %}**, esto podría tomar más tiempo si el reposiorio tiene muchas dependencias. También puedes ver las solicitudes de extracción nuevas para las actualizaciones de versión. Para obtener más información, consulta la sección "[Listar dependencias configuradas para actualizaciones de versión](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". + +### Impacto de los cambios de configuración en las actualizaciones de seguridad + +Si personalizas el archivo *dependabot.yml*, podrías notar algunos cambios en las solicitudes de extracción que se levantan para las actualizaciones de seguridad. Estas solicitudes de extracción siempre se activan mediante una asesoría de seguridad para una dependencia en vez de mediante un calendario de programación del {% data variables.product.prodname_dependabot %}. Sin embargo, estas heredan la configuración de ajustes relevante del archivo *dependabot.yml* a menos de que especifiques una rama destino diferente para las actualizaciones de versión. + +Por ejemplo, consulta la sección "[Configurar etiquetas personalizadas](#setting-custom-labels)" a más adelante. + +### Modificar la programación + +Cuando configuras una actualización de tipo `daily`, predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Puedes utilizar `schedule.time` para especificar una hora alterna para que revise actualizaciones (en formato: `hh:mm`). + +El archivo *dependabot.yml* de ejemplo a continuación expande la configuración de npm para especificar cuándo el {% data variables.product.prodname_dependabot %} debería revisar si hay actualizaciones de versión para las dependencias. + +```yaml +# dependabot.yml file with +# customized schedule for version updates + +version: 2 +updates: + # Keep npm dependencies up to date + - package-ecosystem: "npm" + directory: "/" + # Check the npm registry for updates at 2am UTC + schedule: + interval: "daily" + time: "02:00" +``` + +### Configurar los revisores y asignados + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} levanta solicitudes de extracción sin ningún revisor o asignado. + +Puedes utilizar `reviewers` y `assignees` para especificar los revisores y asignados para todas las solicitudes de extracción que se levanten para un administrador de paquete. Cuando especificas un equipo, debes utilizar el nombre completo de éste, como si estuvieras @mencionándolo (incluyendo la organización). + +El ejemplo de archivo *dependabot.yml* mostrado a continuación cambia las configuraciones npm para que todas las solicitudes de extracción que se hayan abierto con actualizaciones de versión y de seguridad para npm tengan dos revisores y un asignado. + +```yaml +# dependabot.yml file with +# reviews and an assignee for all npm pull requests + +version: 2 +updates: + # Keep npm dependencies up to date + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Raise all npm pull requests with reviewers + reviewers: + - "my-org/team-name" + - "octocat" + # Raise all npm pull requests with an assignee + assignees: + - "user-name" +``` + +### Configurar las etiquetas personalizadas + +{% data reusables.dependabot.default-labels %} + +Puedes utilizar `labels` para anular las etiquetas predeterminadas y especificar etiquetas alternas para todas las solicitudes de extracción que se han levantado para un administrador de paquete. No puedes crear etiquetas nuevas en el archivo *dependabot.yml*, así que las etiquetas alternas ya deben existir en el repositorio. + +El siguiente ejemplo de archivo *dependabot.yml* cambia la configuración de npm para que las solicitudes de extracción abiertas con actualizaciones de versión y de seguridad para npm tengan etiquetas personalizadas. También cambia la configuración de Docker para revisar las actualizaciones de versión contra una rama personalizada y para levantar solicitudes de extracción con etiquetas personalizadas contra dicha rama personalizada. Los cambios en Docker no afectarán las solicitudes de extracción para actualizaciones de seguridad, ya que dichas actualizaciones de seguridad siempre se hacen contra la rama predeterminada. + +{% note %} + +**Nota:** La nueva `target-branch` deberá contener un Dockerfile para actualizar, de lo contrario, este cambio tendrá el efecto de inhabilitar las actualizaciones de versión para Docker. + +{% endnote %} + +```yaml +# dependabot.yml file with +# customized npm configuration + +version: 2 +updates: + # Keep npm dependencies up to date + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Raise all npm pull requests with custom labels + labels: + - "npm dependencies" + - "triage-board" + + # Keep Docker dependencies up to date + - package-ecosystem: "docker" + directory: "/" + schedule: + interval: "daily" + # Raise pull requests for Docker version updates + # against the "develop" branch. The Docker configuration + # no longer affects security update pull requests. + target-branch: "develop" + # Use custom labels on pull requests for Docker version updates + labels: + - "Docker dependencies" + - "triage-board" +``` + +### Más ejemplos + +Para obtener más ejemplos, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". diff --git a/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md b/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md new file mode 100644 index 0000000000000..39410f1f99896 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md @@ -0,0 +1,25 @@ +--- +title: Personalizar cómo aparecen los archivos cambiados en GitHub +intro: 'Para evitar que determinados archivos se muestren en diferencias de manera predeterminada, o que contribuyan al lenguaje del repositorio, puedes marcarlos con el atributo `linguist-generated` en un archivo *.gitattributes*.' +redirect_from: + - /articles/customizing-how-changed-files-appear-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Usa un archivo *.gitattributes* para marcar los archivos que coincidan con un "patrón" determinado con los atributos específicos. Un archivo *.gitattributes* usa las mismas reglas para coincidir como archivo _.gitignore_. Para obtener más información, consulta [FORMATO DE PATRONES](https://www.git-scm.com/docs/gitignore#_pattern_format) en la documentación de Git. + +1. A menos de que ya exista el archivo *.gitattributes* créalo en la raíz del repositorio. +2. Usa el atributo `linguist-generated` para marcar o desmarcar las rutas que deseas que se ignoren para las estadísticas de lenguaje del repositorio y las que deseas que se oculten de manera predeterminada en las diferencias. + + Por ejemplo, para marcar `search/index.json` como archivo generado, agrega esta línea a *.gitattributes*: + + ``` +search/index.json linguist-generated=true + ``` + +### Further reading +- "[Código generado](https://github.com/github/linguist/#generated-code)" en la documentación del lingüista +- "[Crear archivos nuevos](/articles/creating-new-files/)" diff --git a/translations/es-ES/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md b/translations/es-ES/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md new file mode 100644 index 0000000000000..6f7926a2c1fd5 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md @@ -0,0 +1,26 @@ +--- +title: Personalizar la vista previa de las redes sociales de tu repositorio +intro: Puedes personalizar la imagen que se muestra en las plataformas de las redes sociales cuando alguien usa un enlace a tu repositorio. +redirect_from: + - /articles/customizing-your-repositorys-social-media-preview +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Hasta que agregues una imagen, los enlaces al repositorio se expanden para mostrar información básica acerca del repositorio y del avatar del propietario. Agregar una imagen a tu repositorio puede ayudar a identificar tu proyecto entre distintas plataformas de redes sociales. + +{% if currentVersion != "github-ae@latest" %}Puedes cargar una imagen a un repositorio privado, pero tu imagen solo se puede compartir desde un repositorio público.{% endif %} + +{% tip %} +Tip: Tu imagen debe ser un archivo PNG, JPG o GIF de menos de 1 MB de tamaño. Para presentar la mejor calidad, recomendamos mantener la imagen alrededor de 640 por 320 píxeles. +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Vista previa de las redes sociales", haz clic en **Editar**. + - Para agregar una nueva imagen, haz clic en **Cargar imagen...**. + - Para eliminar un imagen, haz clic en **Eliminar imagen**. + + ![Menú desplegable de vista previa de redes sociales](/assets/images/help/repository/social-preview.png) diff --git a/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md b/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md new file mode 100644 index 0000000000000..576f79cdbe9f6 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md @@ -0,0 +1,15 @@ +--- +title: Definir la capacidad de fusión de las solicitudes de extracción +intro: 'Puedes requerir que las solicitudes de extracción superen un conjunto de verificaciones antes de que se las pueda fusionar. Por ejemplo, puedes bloquear las solicitudes de extracción que no superan las verificaciones de estado o puedes requerir que las solicitudes de extracción tengan un número específico de revisiones aprobadas antes de que las pueda fusionar.' +redirect_from: + - /articles/defining-the-mergeability-of-a-pull-request/ + - /articles/defining-the-mergeability-of-pull-requests + - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions +product: '{% data reusables.gated-features.protected-branches %}' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/deleting-a-repository.md b/translations/es-ES/content/github/administering-a-repository/deleting-a-repository.md new file mode 100644 index 0000000000000..a5247a7ab4e24 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/deleting-a-repository.md @@ -0,0 +1,36 @@ +--- +title: Eliminar un repositorio +intro: Puedes eliminar cualquier repositorio o bifurcación si eres un propietario de la organización o si tienes permisos de administración para el repositorio o la bifurcación. Eliminar un repositorio bifurcado no elimina el repositorio ascendente. +redirect_from: + - /delete-a-repo/ + - /deleting-a-repo/ + - /articles/deleting-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.owners-and-admins-can %} elimina un repositorio de la organización. Si se ha deshabilitado **Permitir que los miembros eliminen o transfieran repositorios para esta organización**, solo los propietarios de la organización pueden eliminar los repositorios de la organización. {% data reusables.organizations.new-repo-permissions-more-info %} + +{% if currentVersion != "github-ae@latest" %}El borrar un repositorio público no borrará ninguna bifurcación del mismo.{% endif %} + +{% warning %} + +**Advertencias**: + +- El borrar un repositorio borrará los adjuntos del lanzamiento y los permisos de equpo **permanentemente**. Esta acción **no** se puede deshacer. +- El borrar un repositorio privado {% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}o interno{% endif %} borrará todas sus bifurcaciones. + +{% endwarning %} + +{% if currentVersion == "free-pro-team@latest" %} +Puede restaurar algunos de los repositorios eliminados en un plazo de 90 días. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)". +{% endif %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +2. En la Zona de peligro, haz clic en **Eliminar este repositorio**. ![Botón Eliminar repositorio](/assets/images/help/repository/repo-delete.png) +3. **Lee las advertencias**. +4. Para verificar que está eliminando el repositorio correcto, escribe el nombre del repositorio que deseas eliminar. ![Etiqueta de eliminación](/assets/images/help/repository/repo-delete-confirmation.png) +5. Haga clic en **Comprendo las consecuencias. Eliminar este repositorio**. diff --git a/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md new file mode 100644 index 0000000000000..1c448fafbe6d6 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md @@ -0,0 +1,40 @@ +--- +title: Eliminar y restaurar ramas en una solicitud de extracción +intro: 'Si tienes acceso de escritura en un repositorio, puedes eliminar las ramas asociadas con solicitudes de extracción cerradas o fusionadas. No puedes eliminar las ramas asociadas con solicitudes de extracción abiertas.' +redirect_from: + - /articles/tidying-up-pull-requests/ + - /articles/restoring-branches-in-a-pull-request/ + - /articles/deleting-unused-branches/ + - /articles/deleting-and-restoring-branches-in-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Borrar la rama utilizada para una solicitud de extracción + +Puedes borrar la rama que se asocia con una solicitud de extracción si la han fusionado o cerrado y no hay ninguna otra solicitud de extracción abierta que haga referencia a dicha rama. Para obtener información sobre cerrar ramas que no están asociadas con solicitudes de extracción, consulta la sección "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.list-closed-pull-requests %} +4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas eliminar. +5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Eliminar rama**. ![Botón Eliminar rama](/assets/images/help/pull_requests/delete_branch_button.png) + + Este botón no se muestra si hay alguna solicitud de extracción abierta para esta rama actualmente. + +### Restaurar una rama eliminada + +Puedes restaurar la rama de encabezado de una solicitud de extracción cerrada. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.list-closed-pull-requests %} +4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas restaurar. +5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Restaurar rama**. ![Botón Restaurar rama eliminada](/assets/images/help/branches/branches-restore-deleted.png) + +### Further reading + +- "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)" +- "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)" diff --git a/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md new file mode 100644 index 0000000000000..7e077faeb729c --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -0,0 +1,81 @@ +--- +title: Inhabilitar o limitar las acciones de GitHub para un repositorio +intro: 'Los dueños de repositorios pueden inhabilitar, habilitar y limitar {% data variables.product.prodname_actions %} para un repositorio específico.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los permisos de {% data variables.product.prodname_actions %} para tu repositorio + +{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". + +Puedes habilitar {% data variables.product.prodname_actions %} para tu repositorio. {% data reusables.github-actions.enabled-actions-description %} Puedes inhabilitar {% data variables.product.prodname_actions %} totalmente para tu repositorio. {% data reusables.github-actions.disabled-actions-description %} + +De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} en tu repositorio, pero limitar las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio + +{% note %} + +**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta la sección "[Inhabilitar o limitar a las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" o {% if currentVersion == "free-pro-team@latest" %}"[Requerir las políticas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)".{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Requerir las políticas de las {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".{% endif %} + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +4. Selecciona una opción debajo de "Permisos de las acciones". ![Habilita, inhabilita o limita las acciones para este repositorio](/assets/images/help/repository/enable-repo-actions.png) + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio + +Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar una política que configure qué acciones pueden utilzarse en éste. + +{% data reusables.actions.actions-use-policy-settings %} + +{% note %} + +**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta la sección "[Inhabilitar o limitar a las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" o {% if currentVersion == "free-pro-team@latest" %}"[Requerir las políticas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)".{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Requerir las políticas de las {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". + +{% endif %} + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +1. Debajo de **Permisos de las acciones**, selecciona una opción. ![Configurar la política de acciones para esta organización](/assets/images/help/repository/actions-policy.png) +1. Haz clic en **Save ** (guardar). + +### Permitir que se ejecuten acciones específicas + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +1. Debajo de **Permisos de las acciones**, selecciona **Permitir acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/repository/actions-policy-allow-list.png) +2. Haz clic en **Save ** (guardar). +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configurar la política de bifurcaciones privadas para un repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.settings-sidebar-actions %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md new file mode 100644 index 0000000000000..29b2c72d56f31 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md @@ -0,0 +1,78 @@ +--- +title: Botón para mostrar un patrocinador en tu repositorio +intro: Puedes agregar un botón de patrocinador en tu repositorio para aumentar la visibilidad de las opciones de financiación para tu proyecto de código abierto. +redirect_from: + - /github/building-a-strong-community/displaying-a-sponsor-button-in-your-repository + - /articles/displaying-a-sponsor-button-in-your-repository +versions: + free-pro-team: '*' +--- + +### Acerca de los archivos FUNDING + +Puedes configurar tu botón de patrocinador editando un archivo _FUNDING.yml_ en la carpeta `.github` de tu repositorio, o bien en la rama predeterminada. Puedes configurar el botón para que incluya programadores patrocinados en {% data variables.product.prodname_sponsors %}, plataformas de financiamiento externo o URL de financiamiento personalizadas. Para obtener mas información acerca de {% data variables.product.prodname_sponsors %}, consulta "[Acerca de los patrocinadores de GitHub](/articles/about-github-sponsors)". + +Puedes agregar un nombre de usuario, un nombre de paquete o un nombre de proyecto por plataforma de financiamiento externo y hasta cuatro URL personalizadas. Puedes añadir hasta cuatro organizaciones o desarrolladores patrocinadores en {% data variables.product.prodname_sponsors %}. Agrega cada plataforma en una línea nueva, usando la siguiente sintaxis: + +| Plataforma | Sintaxis | +| ----------------------------------------------------------------------------- | ----------------------------------------------------------------------- | +| [CommunityBridge](https://communitybridge.org) | `community_bridge: PROJECT-NAME` | +| [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors) | `github: USERNAME` o `github: [USERNAME, USERNAME, USERNAME, USERNAME]` | +| [IssueHunt](https://issuehunt.io/) | `issuehunt: USERNAME` | +| [Ko-fi](https://ko-fi.com/) | `ko_fi: USERNAME` | +| [Liberapay](https://en.liberapay.com/) | `liberapay: USERNAME` | +| [Open Collective](https://opencollective.com/) | `open_collective: USERNAME` | +| [Otechie](https://otechie.com/) | `otechie: USERNAME` | +| [Patreon](https://www.patreon.com/) | `patreon: USERNAME` | +| [Tidelift](https://tidelift.com/) | `tidelift: PLATFORM-NAME/PACKAGE-NAME` | +| URL personalizada | `custom: LINK1` or `custom: [LINK1, LINK2, LINK3, LINK4]` | + +Para Tidelift, usa la sintaxis `platform-name/package-name` con los siguientes nombres de plataforma: + +| Lenguaje | Nombre de la plataforma | +| ---------- | ----------------------- | +| JavaScript | `npm` | +| Python | `pypi` | +| Ruby | `rubygems` | +| Java | `maven` | +| PHP | `packagist` | +| C# | `nuget` | + +A continuación, un ejemplo de un archivo _FUNDING.yml_: +``` +github: [octocat, surftocat] +patreon: octocat +tidelift: npm/octo-package +custom: ["https://www.paypal.me/octocat", octocat.com] +``` + +{% note %} + +**Nota:** Si una URL personalizada en una matriz incluye `:`, debes encerrar la URL entre comillas. Por ejemplo, `"https://www.paypal.me/octocat"`. + +{% endnote %} + +Puedes crear un botón patrocinador predeterminado para tu organización o cuenta de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% note %} + +Los enlaces de financiamiento permiten que los proyectos de código abierto reciban apoyo financiero directo de su comunidad. El uso de enlaces de financiamiento para otros fines, como la publicidad o el apoyo a grupos solidarios, comunitarios o políticos no está admitido. Si tienes consultas acerca de si los fines con que deseas usar estos enlaces está admitido, comunícate con {% data variables.contact.contact_support %}. + +{% endnote %} + +### Botón para mostrar un patrocinador en tu repositorio + +Cualquier usuario que cuente con permisos de administración puede habilitar un botón de patrocinador en un repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En Características, selecciona **Patrocinios**. ![Casilla de verificación para habilitar Patrocinios](/assets/images/help/sponsors/sponsorships-checkbox.png) +4. Da clic en **Configurar botón de patrocinador** o **Invalidad enlaces de financiamiento** debajo de la opción "Patrocionios". ![Botón para configurar el botón del patrocinador](/assets/images/help/sponsors/sponsor-set-up-button.png) +5. En el editor de archivos, sigue la instrucciones en el archivo _FUNDING.yml_ para agregar enlaces a las ubicaciones de tus fuentes de financiamiento. ![Edita el archivo FUNDING para añadir enlaces a ubicaciones de fondeo](/assets/images/help/sponsors/funding-yml-file.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Further reading +- "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" +- "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/es-ES/content/github/administering-a-repository/enabling-and-disabling-version-updates.md new file mode 100644 index 0000000000000..cfa29da797b5c --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -0,0 +1,122 @@ +--- +title: Habilitar e inhabilitar las actualizaciones de versión +intro: 'Puedes configurar tu repositorio para que el {% data variables.product.prodname_dependabot %} actualice automáticamente los paquetes que utilizas.' +permissions: 'Las personas con permisos de escritura en un repositorio pueden habilitar o inhabilitar las {% data variables.product.prodname_dependabot_version_updates %} para el mismo.' +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note-no-link %} + +### Acerca de las actualizaciones de versión para las dependencias + +Habilitarás {% data variables.product.prodname_dependabot_version_updates %} mediante la selección de un archivo de configuración de *dependabot.yml* en el directorio `.github` dentro de tu repositorio. El {% data variables.product.prodname_dependabot %} levanta entonces las solicitudes de extracción para mantener actualizadas las dependencias que configures. Para cada dependencia del administrador de paquete que quieras actualizar, debes especificar la ubicación de los archivos de manifiesto de dicho paquete, así como la periodicidad en la que quieres buscar actualizaciones para las dependencias listadas en esos archivos. Para obtener más información sobre habilitar las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". + +{% data reusables.dependabot.initial-updates %} Para obtener más información, consulta la sección "[Personalizar las actualizaciones de las dependencias](/github/administering-a-repository/customizing-dependency-updates)". + +{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, el {% data variables.product.prodname_dependabot %} no es compatible con dependencias privadas de {% data variables.product.prodname_dotcom %} para todos los administradores de paquetes. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". + +### Habilitar las {% data variables.product.prodname_dependabot_version_updates %} + +{% data reusables.dependabot.create-dependabot-yml %} +1. Utiliza `package-ecosystem` para especificar los administradores de paquete que se deben monitorear. +1. Para cada administrador de paquete, utiliza: + - `directory` para especificar la ubicación del manifiesto u otros archivos de definición. + - `schedule.interval` para especificar qué tan a menudo se debe revisar si hay nuevas versiones. +{% data reusables.dependabot.check-in-dependabot-yml %} + +#### Archivo *dependabot.yml* de ejemplo + +El archivo de ejemplo *dependabot.yml* que se muestra a continuación configura las actualizaciones de versión para dos administradores de paquete: npm y Docker. Cuando se registra este archivo, el {% data variables.product.prodname_dependabot %} revisa los archivos de manifiesto en la rama predeterminada par ver si hay dependencias desactualizadas. Si encuentra dependencias desactualizadas, levantará solicitudes de extracción contra la rama predeterminada para actualizar estas dependencias. + +```yaml +# Basic dependabot.yml file with +# minimum configuration for two package managers + +version: 2 +updates: + # Enable version updates for npm + - package-ecosystem: "npm" + # Look for `package.json` and `lock` files in the `root` directory + directory: "/" + # Check the npm registry for updates every day (weekdays) + schedule: + interval: "daily" + + # Enable version updates for Docker + - package-ecosystem: "docker" + # Look for a `Dockerfile` in the `root` directory + directory: "/" + # Check for updates once a week + schedule: + interval: "weekly" +``` + +En el ejemplo anterior, si las dependencias de Docker estuvieran muy desactualizadas, tal vez quisieras comenzar con una programación de tipo `daily` hasta que las dependencias estén bien actualizadas y, posteriormente, tomar una programación semanal. + +#### Habilitar las actualizaciones de versión en las bifurcaciones + +Si quieres habilitar las actualizaciones de versión en las bifurcaciones, hay un paso extra que debes tomar. Las actualizaciones de versión no se habilitan automáticamente en las bifurcaciones cuando existe un archivo de configuración *dependabot.yml*. Esto garantiza que los dueños de la bifurcación no habiliten las actualizaciones de versión accidentalmente cuando suben cambios, incluyendo el archivo de configuración *dependabot.yml* del repositorio original. + +En una bifurcación, también necesitas habilitar explícitamente el {% data variables.product.prodname_dependabot %}. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.click-dependency-graph %} +{% data reusables.dependabot.click-dependabot-tab %} +5. Debajo de "Habilitar el Dependabot", da clic en **Enable Dependabot**. + +### Revisar el estado de las actualizaciones de versión + +Después de que habilitas las actualizaciones de versión, verás una nueva pestaña de **Dependabot** en la gráfica de dependencias del repositorio. Esta pestaña muestra los administradores de paquetes para los cuales se configuró el monitoreo del {% data variables.product.prodname_dependabot %} y cuándo éste revisó las últimas versiones. + +![Pestaña de perspectivas de repositorio, gráfica de dependencias, pestaña de dependabot](/assets/images/help/dependabot/dependabot-tab-view-beta.png) + +Para obtener más información, consulta la sección "[Listar las dependencias configuradas para las actualizaciones de versión](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". + +### Inhabilitar las {% data variables.product.prodname_dependabot_version_updates %} + +Puedes inhabilitar las actualizaciones de versión completamente si eliminas el archivo *dependabot.yml* de tu repositorio. Normalmente, tal vez quieras inhabilitar las actualizaciones temporalmente para una o más dependencias o administradores de paquete. + +- Administradores de paquete: inhabilítalas configurando `open-pull-requests-limit: 0` o dejando de comentar el `package-ecosystem` relevante en el archivo de configuración. +- Dependencias específicas: inhabilítalas agregando los atributos de `ignore` para los paquetes o aplicaciones que quieras excluir de las actualizaciones. + +Cuando inhabilitas las dependencias, puedes utilizar comodines para empatar con un conjunto de bibliotecas relacionadas. También puedes especificar qué versiones excluir. Esto es particularmente útil si necesitas bloquear actualizaciones en una biblioteca, el trabajo pendiente para apoyar un cambio sustancial en su API, pero quieres quieres obtener cualquier arreglo de seguridad para la versión que utilices. + +#### Ejemplo de inhabilitar las actualizaciones de versión para algunas dependencias + +En este archivo de *dependabot.yml* de ejemplo se incluyen ejemplos de las formas diferentes para inhabilitar las actualizaciones en algunas dependencias, mientras que se permite que otras actualizaciones continuen. + +```yaml +# dependabot.yml file with updates +# disabled for Docker and limited for npm + +version: 2 +updates: + # Configuration for Dockerfile + - package-ecosystem: "docker" + directory: "/" + schedule: + interval: "weekly" + # Disable all pull requests for Docker dependencies + open-pull-requests-limit: 0 + + # Configuration for npm + - package-ecosystem: "npm" + directory: "/" + schedule: + interval: "daily" + # Overwrite any ignores created using `@dependabot ignore` commands + ignore: + # Ignore updates to packages that start 'aws' + # Wildcards match zero or more arbitrary characters + - dependency-name: "aws*" + # Ignore some updates to the 'express' package + - dependency-name: "express" + # Ignore only new versions for 4.x and 5.x + versions: ["4.x", "5.x"] +``` + +{% data reusables.dependabot.warning-ignore-option %} + +Para obtener más información acerca de revisar si existen preferencias para ignorar, consulta la sección "[Opciones de configuración para las actualizaciones de depdendencias](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/es-ES/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md b/translations/es-ES/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md new file mode 100644 index 0000000000000..a290c196156ba --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Activar el acceso de lectura Git anónimo para un repositorio +intro: 'Como administrador de un repositorio, puedes habilitar o inhabilitar el acceso de lectura Git anónimo para repositorios públicos que cumplen con determinados requisitos.' +redirect_from: + - /articles/enabling-anonymous-git-read-access-for-a-repository +versions: + enterprise-server: '*' +--- + +Los administradores de repositorios pueden cambiar el acceso de lectura Git anónimo y establecer un repositorio específico en los siguientes casos: +- Si un administrador del sitio ha habilitado el modo privado y el acceso de lectura Git anónimo. +- Si el repositorio es público en la empresa y si no es una bifurcación. +- Si un administrador del sitio no ha inhabilitado el acceso de lectura Git anónimo para el repositorio. + +{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Junto a "Habilitar el acceso de lectura Git anónimo", haz clic en **Habilitar**. ![Botón "Habilitado" en "Acceso de lectura Git anónimo"](/assets/images/help/repository/enable-git-read-access-for-a-repo.png) +4. Revisa los cambios. Para confirmar, escribe el nombre del repositorio y haz clic en **Comprendo. Habilitar el acceso de lectura Git.** diff --git a/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000000..ecdc7e280040c --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Habilita o inhabilita los debates de GitHub para un repositorio +intro: 'Puedes utilizar debates en un repositorio como un lugar para que tu comunidad sostenga conversaciones, haga preguntas y publique respuestas sin dimensionar el trabajo en una propuesta.' +product: '{% data reusables.gated-features.discussions %}' +permissions: Las personas con permisos administrativos en un repositorio pueden habilitar los debates en éste. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Habilitar o inhabilitar los debates en tu repositorio + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. Para inhabilitar los debates, debajo de "Características", deselecciona **Debates**. + +### Further reading + +- "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/github/administering-a-repository/index.md b/translations/es-ES/content/github/administering-a-repository/index.md new file mode 100644 index 0000000000000..554f1ed9393ca --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/index.md @@ -0,0 +1,69 @@ +--- +title: Administrar un repositorio +redirect_from: + - /categories/administering-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-repository-settings %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} + {% link_in_list /classifying-your-repository-with-topics %} + {% link_in_list /customizing-how-changed-files-appear-on-github %} + {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} + {% link_in_list /displaying-a-sponsor-button-in-your-repository %} + {% link_in_list /customizing-your-repositorys-social-media-preview %} + {% link_in_list /viewing-deployment-activity-for-your-repository %} + {% link_in_list /managing-the-forking-policy-for-your-repository %} + {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} + {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} + {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} + {% link_in_list /configuring-autolinks-to-reference-external-resources %} + {% link_in_list /renaming-a-repository %} + {% link_in_list /transferring-a-repository %} + {% link_in_list /deleting-a-repository %} + {% link_in_list /restoring-a-deleted-repository %} +{% topic_link_in_list /managing-branches-in-your-repository %} + {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} + {% link_in_list /changing-the-default-branch %} + {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} +{% topic_link_in_list /configuring-pull-request-merges %} + {% link_in_list /about-merge-methods-on-github %} + {% link_in_list /configuring-commit-squashing-for-pull-requests %} + {% link_in_list /configuring-commit-rebasing-for-pull-requests %} + {% link_in_list /managing-auto-merge-for-pull-requests-in-your-repository %} + {% link_in_list /managing-the-automatic-deletion-of-branches %} +{% topic_link_in_list /defining-the-mergeability-of-pull-requests %} + {% link_in_list /about-protected-branches %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} +{% topic_link_in_list /releasing-projects-on-github %} + {% link_in_list /about-releases %} + {% link_in_list /managing-releases-in-a-repository %} + {% link_in_list /viewing-your-repositorys-releases-and-tags %} + {% link_in_list /linking-to-releases %} + {% link_in_list /comparing-releases %} + {% link_in_list /automation-for-release-forms-with-query-parameters %} +{% topic_link_in_list /securing-your-repository %} + {% link_in_list /about-securing-your-repository %} + {% link_in_list /about-secret-scanning %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} + {% link_in_list /managing-alerts-from-secret-scanning %} + {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} +{% topic_link_in_list /keeping-your-dependencies-updated-automatically %} + {% link_in_list /about-dependabot-version-updates %} + {% link_in_list /enabling-and-disabling-version-updates %} + {% link_in_list /listing-dependencies-configured-for-version-updates %} + {% link_in_list /managing-pull-requests-for-dependency-updates %} + {% link_in_list /customizing-dependency-updates %} + {% link_in_list /configuration-options-for-dependency-updates %} + {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} diff --git a/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md b/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md new file mode 100644 index 0000000000000..52808817e03cd --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md @@ -0,0 +1,49 @@ +--- +title: Mantener tus acciones actualizadas con el Dependabot +intro: 'Puedes utilizar el {% data variables.product.prodname_dependabot %} para mantener las acciones que utilizas actualizadas en sus versiones más recientes.' +redirect_from: + - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca de {% data variables.product.prodname_dependabot_version_updates %} para las acciones + +Las acciones a menudo se actualizan con correcciones de errores y con nuevas características para que los procesos automatizados sean más confiables, rápidos y seguros. Cundo habilitas las {% data variables.product.prodname_dependabot_version_updates %} para {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} te ayudará a asegurarte de que las referencias para las acciones en el archivo *workflow.yml* de un repositorio se mantengan actualizadas. El {% data variables.product.prodname_dependabot %} verifica la referencia de la acción para cada una de ellas en el archivo (habitualmente un número de versión o identificador de confirmación que se asocie con la acción) contra la última versión. Si alguna versión más reciente de la acción está disponible, el {% data variables.product.prodname_dependabot %} te enviará una solicitud de extracción que actualice la referencia en el archivo de flujo de trabajo a su última versión. Para obtener más información acerca de las {% data variables.product.prodname_dependabot_version_updates %}, consulta la sección "[Acerca del {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". Para obtener más información acerca de configurar flujos de trabajo para las {% data variables.product.prodname_actions %}, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +### Habilitar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones + +{% data reusables.dependabot.create-dependabot-yml %}Si ya habilitaste las {% data variables.product.prodname_dependabot_version_updates %} para otros ecosistemas o administradores de paquetes, simplemente abre el archivo *dependabot.yml* existente. +1. Especifica `"github-actions"` como el `package-ecosystem` a monitorear. +1. Configura el `directory` como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. +1. Configura un `schedule.interval` para especificar la frecuencia en la que se revisará si hay versiones nuevas. +{% data reusables.dependabot.check-in-dependabot-yml %}Si editaste un archivo existente, guarda tus cambios. + +También puedes habilitar las {% data variables.product.prodname_dependabot_version_updates %} en las bifurcaciones. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates#enabling-version-updates-on-forks)". + +#### Archivo de ejemplo de *dependabot.yml* para {% data variables.product.prodname_actions %} + +El siguiente ejemplo de archivo de *dependabot.yml* configura las actualizaciones de versión para {% data variables.product.prodname_actions %}. El `directory` debe configurarse como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. El `schedule.interval` se configura en `"daily"`. Después de que se verifique o actualice este archivo, el {% data variables.product.prodname_dependabot %} revisará si hay versiones nuevas de tus acciones. El {% data variables.product.prodname_dependabot %} levantará solicitudes de extracción para las actualizaciones de versión de cualquier acción desactualizada que encuentre. Después de las actualizaciones de versión iniciales, el {% data variables.product.prodname_dependabot %} seguirá buscando versiones desactualizadas para las acciones una vez por día. + +```yaml +# Set update schedule for GitHub Actions + +version: 2 +updates: + + - package-ecosystem: "github-actions" + directory: "/" + schedule: + # Check for updates to GitHub Actions every weekday + interval: "daily" +``` + +### Configurar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones + +Cuando habilitas las {% data variables.product.prodname_dependabot_version_updates %} para las acciones, debes especificar los valores de `package-ecosystem`, `directory`, y `schedule.interval`. Hay muchas más propiedades opcionales que puedes configurar para personalizar tus actualizaciones de versión aún más. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". + +### Further reading + +- "[Acerca de GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" diff --git a/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md b/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md new file mode 100644 index 0000000000000..095b276bd4ee9 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md @@ -0,0 +1,8 @@ +--- +title: Mantener tus dependencias actualizadas automáticamente +intro: 'El {% data variables.product.prodname_dependabot %} puede mantener tus dependencias de repositorio automáticamente.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/linking-to-releases.md b/translations/es-ES/content/github/administering-a-repository/linking-to-releases.md new file mode 100644 index 0000000000000..959255c1a463a --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/linking-to-releases.md @@ -0,0 +1,17 @@ +--- +title: Vincular a lanzamientos +intro: Puedes compartir cada lanzamiento que crees en GitHub con una URL única. +redirect_from: + - /articles/linking-to-releases +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Encuentra el lanzamiento al que quieres enlazar y da clic en el número de versión. ![Información de la etiqueta de lanzamientos](/assets/images/help/releases/release_tag_name.png) +3. Como alternativa, da clic derecho en **Lanzamiento más Reciente** y copia la URL para compartirlo. El sufijo de esta URL siempre es `/releases/latest`. ![Etiqueta del último lanzamiento](/assets/images/help/releases/release_latest_release_tag.png) + +Para enlazarlo directamente con una descarga de tu último activo de lanzamiento, enlaza a `/owner/name/releases/latest/download/nombre-de-activo.zip`. diff --git a/translations/es-ES/content/github/administering-a-repository/listing-dependencies-configured-for-version-updates.md b/translations/es-ES/content/github/administering-a-repository/listing-dependencies-configured-for-version-updates.md new file mode 100644 index 0000000000000..3ce364c49c2ef --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/listing-dependencies-configured-for-version-updates.md @@ -0,0 +1,25 @@ +--- +title: Listar dependencias configuradas para las actualizaciones de versión +intro: 'Puedes ver las dependencias que monitorea el {% data variables.product.prodname_dependabot %} pára encontrar actualizaciones.' +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Visualizar dependencias que monitorea el {% data variables.product.prodname_dependabot %} + +Después de que habilites las actualizaciones de versión, puedes confirmar que tu configuración es la correcta si utilizas la pestaña de **{% data variables.product.prodname_dependabot %}** en la gráfica de dependencias para el repositorio. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.click-dependency-graph %} +{% data reusables.dependabot.click-dependabot-tab %} +5. Opcionalmente, para ver los archivos que se monitorean para un administrador de paquete, da clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} asociado. ![Archivos de dependencia monitoreados](/assets/images/help/dependabot/monitored-dependency-files.png) + +Si no encuentras alguna dependencia, revisa los archivos de bitácora para ver los errores. En caso de que no encuentres algún administrador de paquete, revisa el archivo de configuración. + +### Visualizar los archivos de bitácora del {% data variables.product.prodname_dependabot %} + +1. En la **pestaña de {% data variables.product.prodname_dependabot %}**, da clic en **Revisado por última vez hace *TIME*** para ver el archivo de bitácora que generó el {% data variables.product.prodname_dependabot %} durante su última verificación de actualizaciones de versión. ![Ver el archivo de bitácora](/assets/images/help/dependabot/last-checked-link.png) +2. Opcionalmente, para volver a ejecutar la revisión de versión, da clic en **Revisar si hay actualizaciones**. ![Revisar si hay actualizaciones](/assets/images/help/dependabot/check-for-updates.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..878036391585b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Ya que {% data variables.product.company_short %} utiliza el indicador `File::FNM_PATHNAME` para la sintaxis `File.fnmatch` el comodín no empata con los separadores de directorio (`/`). Por ejemplo, `qa/*` empatará con todas las ramas que comiencen con `qa/` y contengan una sola diagonal. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. Para más información sobre las opciones de sintaxis para las reglas de la rama, consulta la [documentación fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). + +Si un repositorio tiene varias reglas de rama protegida que afectan las mismas ramas, las reglas que incluyen el nombre de una rama específica tienen la mayor prioridad. Si hay más de una regla de rama protegida que hace referencia al mismo nombre de rama específico, entonces la regla de rama creada primera tendrá la prioridad más alta. + +Las reglas de rama protegida que mencionen un caracter especial, como `*`, `?` o `]`, se aplican en el orden que fueron creadas, así que las reglas más antiguas con estos caracteres tienen la prioridad más alta. + +Para crear una excepción a una regla de rama existente, puedes crear una nueva regla de protección de rama que sea una prioridad superior, como una regla de rama para un nombre de rama específico. + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Casilla de verificación Restricción de revisión de solicitud de extracción](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Menú desplegable para seleccionar el número de aprobaciones de revisión requeridas](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![Casilla de verificación Descartar aprobaciones de solicitudes de extracción en espera cuando se suben nuevas confirmaciones](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Requerir revisión de los propietarios del código](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)". ![Restringir quién puede descartar la casilla de verificación de revisiones de solicitudes de extracción](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. + - Selecciona **Requerir verificaciones de estado requeridas antes de la fusión**. ![Opción Verificaciones de estado requeridas](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![Casilla de verificación de estado estricta o poco estricta](/assets/images/help/repository/protecting-branch-loose-status.png) + - Selecciona las verificaciones que quieres requerir de la lista de verificaciones de estado disponibles. ![Lista de verificaciones de estado disponibles](/assets/images/help/repository/required-statuses-list.png) +1. Optionally, select **Require signed commits**. ![Opción Requerir confirmaciones firmadas](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. ![Opción para requerir historial linear](/assets/images/help/repository/required-linear-history.png) +1. También puedes seleccionar **Incluir administradores**. ![Casilla de verificación Incluir administradores](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. ![Casilla de verificación para restricción de rama](/assets/images/help/repository/restrict-branch.png) + - Busca y selecciona las personas, equipos, o apps que tendrán permiso para subir información a la rama protegida. ![Búsqueda de restricciones de rama](/assets/images/help/repository/restrict-branch-search.png) +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Permitir la opción de subida de información forzada](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. ![Opción para habilitar las eliminaciones de ramas](/assets/images/help/repository/allow-branch-deletions.png) +1. Da clic en **Crear**. + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to edit, click **Edit**. ![Botón editar](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Haz clic en **Guardar cambios**. ![Botón Editar mensaje](/assets/images/help/repository/save-branch-protection-rule.png) + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to delete, click **Delete**. ![Botón de borrar](/assets/images/help/repository/delete-branch-protection-rule.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md new file mode 100644 index 0000000000000..8c7065f9fcc11 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -0,0 +1,37 @@ +--- +title: Administrar las alertas del escaneo de secretos +intro: Puedes ver y cerrar las alertas para los secretos que se hayan revisado en tu repositorio. +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### Administrar alertas + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +3. En la barra lateral izquierda, da clic en **Secretos detectados**. ![pestaña "Secretos detectados"](/assets/images/help/repository/sidebar-secrets.png) +4. Debajo de "Escaneo de secretos" da clic en la alerta que quieras ver. + {% if currentVersion == "free-pro-team@latest" %} + ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} + +### Asegurar los secretos en riesgo + +Cuando un secreto se haya confirmado en un repositorio, deberás considerarlo en riesgo. {% data variables.product.prodname_dotcom %} recomienda tomar las siguientes acciones para los secretos puestos en riesgo: + +- Para un token de acceso personal de {% data variables.product.prodname_dotcom %} comprometido, elimina el token comprometido, crea un nuevo token y actualiza todo servicio que use el token antiguo. Para obtener más información, consulta la sección "[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". +- Para todos los demás secretos, verifica primero que aquellos que se hayan confirmado en {% data variables.product.product_name %} sean válidos. De ser así, crea un secreto nuevo, actualiza cualquier servicio que utilice el secreto anterior, y luego bórralo. diff --git a/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md new file mode 100644 index 0000000000000..de0a3bb3c7964 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -0,0 +1,16 @@ +--- +title: Administrar la fusión automática para las solicitudes de cambios en tu repositorio +intro: "Puedes permitir o dejar de permitir la fusión automática de solicitudes de cambio en tu repositorio." +product: '{% data reusables.gated-features.auto-merge %}' +versions: + free-pro-team: '*' +permissions: Las personas con permisos de mantenedor pueden administrar las fusiones automáticas de solicitudes de cambios en un repositorio. +--- + +{% data reusables.pull_requests.auto-merge-release-phase %} + +Si permites la fusión automática de solciitudes de cambios en tu repositorio, las personas pueden configurar que solicitudes de cambio individuales en éste se fusionen automáticamente cuando todos los requisitos de fusión se cumplan. Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. Debajo de "Botón para fusionar", selecciona o deselecciona **Permitir la fusión automática**. ![Casilla de verificación para permitir o dejar de permitir la fusión automática](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md new file mode 100644 index 0000000000000..43f979a206cd8 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md @@ -0,0 +1,12 @@ +--- +title: Administrar ramas en tu repositorio +intro: 'Cada vez que propones un cambio en Git, [creas una nueva rama](/articles/creating-and-deleting-branches-within-your-repository/). La administración de ramas es una parte importante del flujo de trabajo de Git. Después de algún tiempo, tu lista de ramas puede crecer, por lo que es una buena idea eliminar las ramas fusionadas o antiguas.' +mapTopic: verdadero +redirect_from: + - /articles/managing-branches-in-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md new file mode 100644 index 0000000000000..68d69c4db42e4 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -0,0 +1,25 @@ +--- +title: Administrar los objetos de LFS de Git en los archivos de tu repositorio +shortTitle: 'Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos' +intro: 'Puedes elegir si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos de código fuente, tales como los archivos ZIP y .tar, que {% data variables.product.product_name %} crea para tu repositorio.' +permissions: 'Las personas con permisos administrativos en un repositorio pueden administrar si los objetos de {% data variables.large_files.product_name_short %} se incluirán en los archivos de dicho repositorio.' +versions: + free-pro-team: '*' + enterprise-server: '>3.0' + github-ae: '*' +--- + +### Acerca de los objetos de {% data variables.large_files.product_name_short %} en los archivos + +{% data variables.product.product_name %} crea archivos de código fuente para tu repositorio en forma de archivos ZIP y .tar. Las personas pueden descargar estos archivos en la página principal de tu repositorio o en forma de activos del lanzamiento. Predeterminadamente, los objetos de {% data variables.large_files.product_name_short %} no se incluyen en estos archivos, únicamente los archivos de puntero a estos objetos. Para mejorar la usabilidad de los archivos para tu repositorio, puedes elegir incluir los objetos de {% data variables.large_files.product_name_short %} en su lugar. + +{% if currentVersion == "free-pro-team@latest" %} +Si eliges incluir +objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio, cada descarga de dichos archivos contrará contra el uso de ancho de banda de tu cuenta. Cada cuenta recibirá una {% data variables.large_files.initial_bandwidth_quota %} mensual de ancho de banda gratuito, y podrás pagar por cualquier uso adicional. Para obtener más información, consulta las secciones "[Acerca del uso del ancho de banda y del almacenamiento](/github/managing-large-files/about-storage-and-bandwidth-usage)" y "[Administrar la facturación 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 %} + +### Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Archivos", sleecciona o deselecciona **Incluir los objetos de {% data variables.large_files.product_name_short %} en los archivos**. ![Casilla para incluir los objetos de {% data variables.large_files.product_name_short %} en los archivos](/assets/images/help/repository/include-git-lfs-objects-checkbox.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md b/translations/es-ES/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md new file mode 100644 index 0000000000000..608cdf8ae2382 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-pull-requests-for-dependency-updates.md @@ -0,0 +1,34 @@ +--- +title: Administrar las solicitudes de extracción para las actualizaciones de dependencia +intro: 'Administrarás las solicitudes de extracción que levante el {% data variables.product.prodname_dependabot %} de casi la misma forma que cualquier otra solicitud de extracción, pero hay algunas opciones adicionales.' +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} + +{% data reusables.dependabot.pull-request-introduction %} + +Cuando el {% data variables.product.prodname_dependabot %} levanta una solicitud de extracción, se te notificará con el método que hayas escogido para el repositorio. Cada solicitud de cambios contiene información detallada sobre el cambio propusto, que se toma del administrador de paquetes. Estas solicitudes de extracción siguen las revisiones y pruebas normales que se definieron en tu repositorio. Adicionalmente, si hay información suficiente disponible, verás una puntuación de compatibilidad. Esto también podría ayudarte a decidir si quieres fusionar el cambio o no. Para obtener información sobre esta puntuación, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + +Si tienes muchas dependencias para administrar, tal vez quieras personalizar la configuración para cada administrador de paquete y que así, las solicitudes de extracción tengan revisores, asignados, y etiquetas específicos. Para obtener más información, consulta la sección "[Personalizar actualizaciones de dependencias](/github/administering-a-repository/customizing-dependency-updates)". + +### Visualizar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +1. Cualquier solicitud de extracción para actualizaciones de versión o de seguridad se puede identificar fácilmente. + - El autor es [dependabot](https://github.com/dependabot), la cuenta bot que utiliza la app del {% data variables.product.prodname_dependabot %}. + - Predeterminadamente, tienen la etiqueta `dependencies`. + +### Cambiar la estrategia de rebase para las solicitudes de extracción del {% data variables.product.prodname_dependabot %} + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción para resolver cualquier conflicto. Si prefieres manejar los conflictos de fusión manualmente, puedes inhabilitar esta opción utilizando la opción de `rebase-strategy`. Para obtener más detalles, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)". + +### Administrar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} con comandos de comentario + +El {% data variables.product.prodname_dependabot %} responde a comandos simples en los comentarios. Cada solicitud de extracción contiene detalles de los comandos que puedes utilizar para procesarla, por ejemplo: fusionar, combinar, reabrir, cerrar o rebasar dicha solicitud. El objetivo es facilitar tanto como sea posible el que se pueda clasificar automáticamente las solicitudes de extracción generadas. + +Si ejecutas cualquiera de los comandos para ignorar las dependencias o las versiones, el {% data variables.product.prodname_dependabot %} almacena las preferencias para el repositorio centralmente. Si bien esta es una solución rápida, para aquellos repositorios con más de un colaborador, es mejor definir explícitamente las dependencias y versiones a ignorar en el archivo de configuración. Esto hace que todos los colaboradores puedan ver más fácilmente por qué una dependencia en particular no se está actualizando automáticamente. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md new file mode 100644 index 0000000000000..9250dccde9874 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -0,0 +1,67 @@ +--- +title: Administrar lanzamientos en un repositorio +intro: Puedes crear lanzamientos que desees poner en conjunto y entregar iteraciones de un proyecto a los usuarios. +redirect_from: + - /articles/creating-releases + - /articles/listing-and-editing-releases/ + - /articles/editing-and-deleting-releases + - /articles/managing-releases-in-a-repository + - /github/administering-a-repository/creating-releases + - /github/administering-a-repository/editing-and-deleting-releases +permissions: 'Los colaboradores del repositorio y las personas con acceso de escritura en el mismo pueden crear, editar y eliminar un lanzamiento.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} + +### Acerca de la administración de lanzamientos + +{% if currentVersion == "free-pro-team@latest" %} +También puedes publicar una acción desde un lanzamiento específico en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "Publicar una acción en {% data variables.product.prodname_marketplace %}". +{% endif %} +Puedes elegir si + +los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos ZIP y TAR que {% data variables.product.product_name %} crea para cada lanzamiento. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% tip %} + +**Tip**: También puedes administrar los lanzamientos utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta la sección "[`gh release`](https://cli.github.com/manual/gh_release)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +### Crear un lanzamiento + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Haz clic en **Borrador de un nuevo lanzamiento**. ![Botón Borrador de lanzamientos](/assets/images/help/releases/draft_release_button.png) +4. Escribe un número de versión para tu lanzamiento. Las versiones se basan en [etiquetas Git](https://git-scm.com/book/en/Git-Basics-Tagging). Te recomendamos darles a las etiquetas nombres que se adapten al [control semántico de versiones](http://semver.org/). ![Versión de lanzamientos con etiquetas](/assets/images/help/releases/releases-tag-version.png) +5. Utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. ![Rama de lanzamientos con etiquetas](/assets/images/help/releases/releases-tag-branch.png) +6. Escribe un título y una descripción para tu lanzamiento. ![Descripción de lanzamientos](/assets/images/help/releases/releases_description.png) +7. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios. ![Proporcionar un DMG con el lanzamiento](/assets/images/help/releases/releases_adding_binary.gif) +8. Para notificar a los usuarios que el lanzamiento no está listo para producción y puede ser inestable, selecciona **Esto es un pre-lanzamiento**. ![Casilla de verificación para marcar un lanzamiento como prelanzamiento](/assets/images/help/releases/prerelease_checkbox.png) +9. Si estás listo para publicitar tu lanzamiento, haz clic en **Publicar lanzamiento**. Para seguir trabajando luego en el lanzamiento, haz clic en **Guardar borrador**. ![Botones Publicar lanzamiento y Borrador de lanzamiento](/assets/images/help/releases/release_buttons.png) + +También puedes crear un lanzamiento automáticamente desde la línea de comandos o en un script. Para obtener más información, consulta la sección "[Lanzamientos](/rest/reference/repos/#create-a-release)." + +### Editar un lanzamiento + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. En la parte derecha de la página, junto al lanzamiento que quieres editar, da clic en **Editar lanzamiento**. ![Editar un lanzamiento](/assets/images/help/releases/edit-release.png) +4. Edita los detalles del lanzamiento en el formato, después, da clic en **Actualizar lanzamiento**. ![Actualizar un lanzamiento](/assets/images/help/releases/update-release.png) + +### Eliminar un lanzamiento + +Debes eliminar todos los archivos binarios adjuntos a un lanzamiento antes de poder eliminarlo. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Da clic en el nombre del lanzamiento que quieres eliminar. ![Enlace para ver el lanzamiento](/assets/images/help/releases/release-name-link.png) +4. En la esquina superior derecha de la página, haz clic en **Eliminar**. ![Botón para eliminar lanzamiento](/assets/images/help/releases/delete-release.png) +5. Da clic en **Eliminar este lanzamiento**. ![Confirmar la eliminación del lanzamiento](/assets/images/help/releases/confirm-delete-release.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md b/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md new file mode 100644 index 0000000000000..1354462222e19 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md @@ -0,0 +1,12 @@ +--- +title: Administrar configuraciones de repositorios +intro: 'Los administradores de repositorio y propietarios de organización pueden cambiar la configuración de un repositorio, como el nombre, propietario y visibilidad, o bien, borrar el repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/managing-repository-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md new file mode 100644 index 0000000000000..39ac74627217b --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -0,0 +1,82 @@ +--- +title: Administrar la configuración de seguridad y análisis para tu repositorio +intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tu proyecto dentro de {% data variables.product.prodname_dotcom %}.' +permissions: Las personas con permisos administrativos en un repositorio pueden gestionar la configuración de análisis y seguridad del mismo. +redirect_from: + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/ + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/ + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization + - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories + +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} + +{% data reusables.security.security-and-analysis-features-enable-read-only %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} + +### Otorgar acceso a las alertas de seguridad + +Después de que habilitas las alertas del {% data variables.product.prodname_dependabot %} o del {% data variables.product.prodname_secret_scanning %} para un repositorio en una organización, los propietarios y administradores de repositorio de ésta podrán ver las alertas predeterminadamente. Puedes dar acceso a equipos y personas adicionales para las alertas de un repositorio. + +{% note %} + +Los propietarios de organización y administradores de repositorio solo pueden otorgar acceso para ver alertas de seguridad, tales como aquellas del {% data variables.product.prodname_dependabot %} y del {% data variables.product.prodname_secret_scanning %}, a las personas o equipos que tengan acceso de escritura en el repositorio. + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Debajo de "Acceso a las alertas", en el campo de búsqueda, comienza a teclear el nombre de la persona o equipo que quieres encontrar y luego da clic en su nombre dentro de la lista de coincidencias. + {% if currentVersion == "free-pro-team@latest" %} + ![Campo de búsqueda para otorgar acceso a las alertas de seguridad a personas y equipos](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Campo de búsqueda para otorgar acceso a las alertas de seguridad a personas y equipos](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} +5. Haz clic en **Guardar cambios**. ![Botón de "Guardar cambios" para los cambios realizados a la configuración de alertas de seguridad](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) + +### Eliminar el acceso a las alertas de seguridad + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + ![Botón "x" para eliminar el acceso de alguien a las alertas de seguridad para tu repositorio](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botón "x" para eliminar el acceso de alguien a las alertas de seguridad para tu repositorio](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} + +### Further reading + +- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" +- "[Administrar la seguridad y la configuración de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md new file mode 100644 index 0000000000000..8064a2d22dd03 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -0,0 +1,54 @@ +--- +title: Gestionar equipos y personas con acceso a tu repositorio +intro: Puedes ver a todo aquél que ha accedido a tu repositorio y ajustar los permisos. +permissions: Los administradores de repositorio pueden administrar equipos y personas con acceso a ellos. +redirect_from: + - /github/administering-a-repository/managing-people-and-teams-with-access-to-your-repository +versions: + free-pro-team: '*' +--- + +### Acerca de gestionar el acceso a tu repositorio + +Puedes ver un resumen de cada equipo o persona con acceso a tu repositorio para todo aquél que administres en {% data variables.product.prodname_dotcom %}. Desde este resumen, también puedes invitar a nuevos equipos o personas, cambiar los permisos de ellos, o eliminar su acceso al repositorio. + +Este resumen puede ayudarte a auditar el acceso a tu repositorio, incorporar o retirar personal externo o empleados, y responder con efectividad a los incidentes de seguridad. + +Para obtener más información acerca de los niveles de permiso en los repositorios, consulta "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y"[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." + +![Resumen de gestión de accesos](/assets/images/help/repository/manage-access-overview.png) + +### Filtrar la lista de equipos y personas + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-manage-access %} +4. Debajo de "Administrar acceso" en el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres encontrar. ![Campo de búsqueda para filtrar la lista de equipos o personas con acceso](/assets/images/help/repository/manage-access-filter.png) + +### Cambiar permisos para un equipo o persona + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-manage-access %} +4. Encuentra el equipo o persona cuyos permisos quieres cambiar debajo de "Administrar acceso", posteriormente, utiliza el menú desplegable de **Rol** para seleccionar nuevos permisos. ![Utilizar el menú desplegable de "Rol" para seleccionar nuevos permisos para un equipo o persona](/assets/images/help/repository/manage-access-role-drop-down.png) + +### Invitar a un equipo o persona + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-manage-access %} +{% data reusables.organizations.invite-teams-or-people %} +5. En el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres invitar y da clic en el mismo dentro de la lista de coincidencias. ![Campo de búsqueda para teclear el nombre del equipo o persona que deseas invitar al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Debajo de "Escoje un rol", selecciona los permisos que quieres otorgar al equipo o persona, posteriormente, da clic en **Añadir NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para el equipo o persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png) + +### Eliminar el acceso de un equipo o persona + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-manage-access %} +4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trashcan" aria-label="The trashcan icon" %}. ![Icono de papelera para eliminar el acceso](/assets/images/help/repository/manage-access-remove.png) + +### Further reading + +- "[Configurar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)" +- "[Configurar los permisos básicos para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md b/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md new file mode 100644 index 0000000000000..8d9b5866814cd --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md @@ -0,0 +1,20 @@ +--- +title: Administrar la eliminación automática de ramas +intro: Puedes hacer que se eliminen automáticamente ramas centrales después de que se fusionen solicitudes de extracción en tu repositorio. +redirect_from: + - /articles/managing-the-automatic-deletion-of-branches +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cualquier persona con permisos de administrador a un repositorio puede habilitar e inhabilitar la eliminación automática de ramas. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Dentro de "Merge button" (Botón fusionar), selecciona o deselecciona **Automatically delete head branches (Eliminar automáticamente ramas centrales)**. ![Casilla de verificación para habilitar o inhabilitar la eliminación automática de ramas](/assets/images/help/repository/automatically-delete-branches.png) + +### Further reading +- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" +- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md new file mode 100644 index 0000000000000..c33ec496c31a0 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -0,0 +1,25 @@ +--- +title: Administrar la política de ramificación para tu repositorio +intro: 'Puedes permitir o prevenir la bifurcación de un repositorio específico privado {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o interno{% endif %} que pertenezca a una organización.' +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 +permissions: Las personas con permisos de administrador en un repositorio pueden administrar la política de ramificación del mismo. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Un propietario de la organización debe permitir las bifurcaciones de repositorios privados{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e internos{% endif %} a nivel organizacional antes de que puedas permitir o dejr de permitir las bifurcaciones en un repositorio específico. Para obtener más información, consulta "[Administrar la política de ramificación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)." + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Features" (Características), selecciona **Allow forking** (Permitir bifurcación). ![Casilla de verificación para permitir o prohibir la bifurcación de un repositorio privado](/assets/images/help/repository/allow-forking-specific-org-repo.png) + +### Further reading + +- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md b/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md new file mode 100644 index 0000000000000..7f32b5541bfb3 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md @@ -0,0 +1,13 @@ +--- +title: Lanzar proyectos en GitHub +intro: 'Puedes crear un lanzamiento para consolidad software, notas de lanzamiento y archivos binarios para que los demás lo descarguen.' +mapTopic: verdadero +redirect_from: + - /categories/85/articles/ + - /categories/releases/ +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) diff --git a/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md b/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md new file mode 100644 index 0000000000000..f5d118a23ab23 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md @@ -0,0 +1,50 @@ +--- +title: Renombrar un repositorio +intro: Puedes renombrar un repositorio si eres propietario de la organización o tienes permisos de administrador para el repositorio. +redirect_from: + - /articles/renaming-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando cambias el nombre de un repositorio, toda la información existente, a excepción de las URL del sitio del proyecto, se redirige automáticamente al nuevo nombre, incluyendo: + +* Problemas +* Wikis +* Estrellas +* Seguidores + +Para obtener más información sobre los sitios del proyecto, consulta "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)" + +Adicionalmente a redirigir el tráfico web, todas las operaciones de `git clone`, `git fetch`, o`git push` que apunten a la ubicación anterior seguirán funcionando como si se hubieran hecho en la nueva. Sin embargo, para evitar la confusión, recomendamos ampliamente actualizar cualquier clon local para que lleve a la URL del nuevo repositorio. Puedes hacer esto utilizando `git remote` en la línea de comandos: + +```shell +$ git remote set-url origin new_url +``` + +Para obtener más información, consulta "[Cambiar la URL de un remoto](/github/using-git/changing-a-remotes-url)." + +{% if currentVersion == "free-pro-team@latest" %} + +Si planeas renombrar un repositorio que tenga un sitio {% data variables.product.prodname_pages %}, recomendamos utilizar un dominio personalizado para el mismo. Esto garantiza que la URL del sitio no se vea impactada cuando se renombre el repositorio. Para obtener más información, consulta "[Acerca de los dominios personalizados y sitio de {% data variables.product.prodname_pages %} ](/github/working-with-github-pages/about-custom-domains-and-github-pages)." + +{% endif %} + +{% tip %} + +**Sugerencia:** {% data reusables.organizations.owners-and-admins-can %} renombra un repositorio. {% data reusables.organizations.new-repo-permissions-more-info %} + +{% endtip %} + +{% warning %} + +**Advertencia**: Si en el futuro creas un nuevo repositorio bajo tu cuenta, no reutilices el nombre original del repositorio renombrado. Si lo haces, los redireccionamientos al repositorio renombrado fallarán. + +{% endwarning %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En **Repository Name** (Nombre del repositorio), escribe el nombre nuevo de tu repositorio. ![Renombrar repositorio](/assets/images/help/repository/repository-name-change.png) +4. Haz clic en **Rename** (Renombrar). ¡Lo has hecho! diff --git a/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md new file mode 100644 index 0000000000000..3e3be4f41c1ec --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md @@ -0,0 +1,41 @@ +--- +title: Restaurando un repositorio eliminado +intro: Puede restaurar algunos de los repositorios eliminados para recuperar su contenido. +redirect_from: + - /articles/restoring-a-deleted-repository +versions: + free-pro-team: '*' +--- + +Cualquier usuario puede restaurar repositorios eliminados que le pertenecieron a su propia cuenta de usuario. Los propietarios de la organización pueden restaurar repositorios eliminados que le pertenecieron a la organización. + +### Acerca de la restauración de repositorios + +Un repositorio eliminado se puede restaurar en un plazo de 90 días, a menos que el repositorio haya sido parte de una red de bifurcaciones que actualmente no está vacía. Una red de bifurcaciones consiste en un repositorio padre, las bifurcaciones del repositorio y las bifurcaciones de las bifurcaciones del repositorio. Si tu repositorio forma parte de una red de bifurcaciones, no se puede restaurar a menos que se elimine cualquier otro repositorio de la red o que se haya separado de la red. Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". + +Si quieres restaurar un repositorio que era parte de una red de bifurcaciones que actualmente no está vacía, te puedes contactar con {% data variables.contact.contact_support %}. + +Puede tardar hasta una hora después de que se elimine un repositorio antes de que ese repositorio esté disponible para la restauración. + +Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o los permisos de equipo. Las propuestas que se restablezcan no se etiquetarán. + +### Restaurar un repositorio eliminado que le pertenecía a una cuenta de usuario + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.repo-tab %} +{% data reusables.user_settings.deleted-repos %} +{% data reusables.user_settings.restore-repo %} +{% data reusables.user_settings.restore-confirmation %} + +### Restaurar un repositorio eliminado que le pertenecía a una organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.deleted-repos %} +{% data reusables.user_settings.restore-repo %} +{% data reusables.user_settings.restore-confirmation %} + +### Further reading + +- "[Borrar un repositorio](/articles/deleting-a-repository)" diff --git a/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md new file mode 100644 index 0000000000000..cf73992a8313e --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md @@ -0,0 +1,10 @@ +--- +title: Asegurar tu repositorio +intro: 'Asegurar las funciones como {% data variables.product.prodname_secret_scanning %} protegen los datos de tu repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/securing-your-repository +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md new file mode 100644 index 0000000000000..a45e4b87b1f21 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md @@ -0,0 +1,106 @@ +--- +title: Configurar la visibilidad de un repositorio +intro: Puedes elegir quién puede ver tu repositorio. +redirect_from: + - /articles/making-a-private-repository-public/ + - /articles/making-a-public-repository-private/ + - /articles/converting-a-public-repo-to-a-private-repo/ + - /articles/setting-repository-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los cambios a la visibilidad de un repositorio + +Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. Para obtener más información, consulta "[Restringir los cambios a la visibilidad del repositorio en tu organización](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." + +Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio. + +#### Convertir un repositorio en privado +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +* {% data variables.product.product_name %} separará las bifurcaciones públicas del repositorio público y las pondrá en una red nueva. Las bifurcaciones públicas no se hacen privadas.{% endif %} +* Si cambias la visibilidad de un repositorio de interna a privada, {% data variables.product.prodname_dotcom %} eliminará las bifurcaciones que pertenezcan a cualquiera de los usuarios sin acceso al repositorio que recientemente se hizo privado. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}La visibilidad de cualquier bifurcación también cambiará a privada.{% elsif currentVersion == "github-ae@latest" %}Si el repositorio interno tiene cualquier bifurcación, la visibilidad de éstas ya será privada.{% endif %} Para obtener más información, consulta la sección "[¿Qué pasa con las bifurcaciones cuando un repositorio se borra o cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} +* Si utilizas {% data variables.product.prodname_free_user %} para cuentas de usuario o de organización, algunas características no estarán disponibles en el repositorio después de que cambies la visibilidad a privada. {% data reusables.gated-features.more-info %}{% endif %} +* Cualquier sitio de {% data variables.product.prodname_pages %} publicado se dejará de publicar automáticamente.{% if currentVersion == "free-pro-team@latest" %} Si agregaste un dominio personalizado al sitio de {% data variables.product.prodname_pages %}, deberás eliminar o actualizar tus registros de DNS antes de que hagas al repositorio privado para evitar el riesgo de que alguien más tome el dominio. Para obtener más información, consulta la sección "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %}{% if currentVersion == "free-pro-team@latest" %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* El acceso anónimo de Git ya no está disponible. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + +#### Convertir un repositorio en interno + +{% note %} + +**Nota:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +* Cualquier bifurcación del repositorio se mantendrá en la red del mismo y {% data variables.product.product_name %} mantendrá la relación entre el repositorio raíz y la bifurcación. Para obtener más información, consulta la sección "[¿Qué le sucede a las bifurcaciones cuando se elimina un repositorio o cuando cambia la visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +#### Convertir un repositorio en público + +* {% data variables.product.product_name %} se deslindará de las bifurcaciones privadas y lasconvertirá en repositorios privados independientes. Para obtener más información, consulta la sección "[¿Qué sucede con las bifurcaciones cuando se borra un repositorio o cuando cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} +* Si vas a convertir tu repositorio privado en uno público como parte de un movimiento hacia la creación de un proyecto de código abierto, consulta las [Guías de Código Abierto](http://opensource.guide) para encontrar tips ylineamientos útiles. También puedes tomar un curso gratuito sobre cómo administrar un proyecto de código abierto con [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Una vez que tu repositorio es público, también puedes ver el perfil de la comunidad de tu repositorio para ver si tu proyecto cumple con las mejoras prácticas para los colaboradores de apoyo. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + +### Cambiar la visibilidad de un repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Zona de Peligro", a la derecha de "Cambiar la visibilidad del repositorio", da clic en **Cambiar la visibilidad**. ![Botón de cambiar la visibilidad](/assets/images/help/repository/repo-change-vis.png) +4. Selecciona una visibilidad. ![Diálogo de opciones para la visbilidad del repositorio](/assets/images/help/repository/repo-change-select.png) +5. Para verificar que estás cambiando la visibilidad del repositorio correcto, teclea el nombre del repositorio para el cual quieres cambiar la visibilidad. +6. Da clic en **Entiendo, cambiar la visibilidad del repositorio**. ![Botón de confirmar cambio para la visibilidad de un repositorio](/assets/images/help/repository/repo-change-confirm.png) + +{% endif %} + +{% if currentVersion ver_lt "enterprise-server@2.22" %} + +### Convertir un repositorio en privado + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Zona de Peligro", junto a "Convertir este repositorio en privado", da clic en **Convertir en privado**. ![Botón para convertir en privado](/assets/images/help/repository/repo-makeprivate.png) +4. Lee las advertencias acerca de convertir un repositorio en privado. ![Ventana emergente de advertencias](/assets/images/help/repository/repo-privateconfirm.png) +5. Escribe el nombre del repositorio que deseas convertir en privado, por ejemplo `accountname/reponame`. +6. Da clic en **Entiendo, convertir este repositorio en privado**. + +### Convertir un repositorio en público + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Zona de Peligro", junto a "Convertir este repositorio en público", da clic en **Convertir en público**. ![Botón para convertir en público](/assets/images/help/repository/repo-makepublic.png) +4. Lee las advertencias acerca de convertir un repositorio en público. ![Ventana emergente con información sobre convertir un repositorio privado en público](/assets/images/help/repository/repo-publicconfirm.png) +5. Escribe el nombre del repositorio que deseas convertir en público, por ejemplo `accountname/reponame`. +6. Da clic en **Entiendo, convertir este repositorio en público**. + +{% if currentVersion ver_gt "enterprise-server@2.19" %} +### Convertir un repositorio en interno + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Zona de Peligro", junto a "Convertir este repositorio en interno", da clic en **Convertir en interno**. ![Botón para convertir en interno](/assets/images/help/repository/repo-makeinternal.png) +4. Lee las advertencias acerca de convertir un repositorio en interno. ![Ventana emergente de advertencias](/assets/images/help/repository/repo-internalconfirm.png) +5. Escribe el nombre del repositorio que deseas convertir en interno, por ejemplo `accountname/reponame`. +6. Da clic en **Entiendo, convertir este repositorio en interno**. +{% endif %} + +{% endif %} + +### Further reading +- "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-ES/content/github/administering-a-repository/transferring-a-repository.md b/translations/es-ES/content/github/administering-a-repository/transferring-a-repository.md new file mode 100644 index 0000000000000..b12cf1a81ea5e --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/transferring-a-repository.md @@ -0,0 +1,74 @@ +--- +title: Transferir un repositorio +intro: Puedes transferir repositorios a otros usuarios o cuentas de organización. +redirect_from: + - /articles/about-repository-transfers/ + - /move-a-repo/ + - /moving-a-repo/ + - /articles/what-is-transferred-with-a-repository/ + - /articles/what-is-transferred-with-a-repo/ + - /articles/how-to-transfer-a-repo/ + - /articles/how-to-transfer-a-repository/ + - /articles/transferring-a-repository-owned-by-your-personal-account/ + - /articles/transferring-a-repository-owned-by-your-organization/ + - /articles/transferring-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las transferencias de repositorios + +Cuando transfieres un repositorio a un propietario nuevo, puede administrar de inmediato los contenidos, propuestas, solicitudes de extracción, lanzamientos, tableros de proyecto y parámetros del repositorio. + +Prerrequisitos para las transferencias de repositorio: {% if currentVersion == "free-pro-team@latest" %} +- Cuando le transfieras un repositorio que te pertenece a otra cuenta de usuario, el propietario recibirá un correo electrónico de confirmación. El correo electrónico de confirmación incluye instrucciones para aceptar la transferencia. Si el propietario nuevo no acepta la transferencia en el transcurso de un día, la invitación se vencerá.{% endif %} +- Para transferirle un repositorio que te pertenece a una organización, debes tener permiso para crear un repositorio en la organización de destino. +- La cuenta objetivo no debe tener un repositorio con el mismo nombre o una bifurcación en la misma red. +- El propietario original del repositorio se agrega como colaborador en el repositorio transferido. Los demás colaboradores del repositorio transferido permanecen intactos. +- Las bifurcaciones privadas no se pueden transferir. + +{% if currentVersion == "free-pro-team@latest" %}Si transfieres un repositorio privado a una cuenta de usuario {% data variables.product.prodname_free_user %} o de organización, el repositorio perderá acceso a características como ramas protegidas y {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} + +#### ¿Qué se transfiere con un repositorio? + +Cuando transfieres un repositorio, también se transfieren sus propuestas, solicitudes de extracción, wiki, estrellas y observadores. Si el repositorio transferido contiene webhooks, servicios, secretos, o llaves de implementación, estos permanecerán asociados después de que se complete la transferencia. Se preserva la información de Git acerca de las confirmaciones, incluidas las contribuciones. Asimismo: + +- Si el repositorio transferido es una bifurcación, sigue asociado con el repositorio ascendente. +- Si el repositorio transferido tiene alguna bifurcación, esas bifurcaciones seguirán asociadas al repositorio después de que se complete la transferencia. +- Si el repositorio transferido utiliza {% data variables.large_files.product_name_long %}, todos {% data variables.large_files.product_name_short %} los objetos se mueven automáticamente. Esta transferencia ocurre en segundo plano, así que, si tienes muchos objetos de {% data variables.large_files.product_name_short %} o si los objetos de {% data variables.large_files.product_name_short %} son muy grandes, podría tomar algo de tiempo para que se lleve a cabo la transferencia.{% if currentVersion == "free-pro-team@latest" %} Antes de que transfieras un repositorio que utilice {% data variables.large_files.product_name_short %}, asegúrate de que la cuenta receptora tenga suficientes paquetes de datos para almacenar los objetos de {% data variables.large_files.product_name_short %} que vayas a mover. Para obtener más información acerca de agregar almacenamiento para las cuentas de usuario, consulta "[Subir de categoría {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %} +- Cuando se transfiere un repositorio entre dos cuentas de usuario, las asignaciones de propuestas se dejan intactas. Cuando transfieres un repositorio desde una cuenta de usuario a una organización, las propuestas asignadas a los miembros de la organización permanecen intactas, y todos los demás asignatarios de propuestas se eliminan. Solo los propietarios de la organización están autorizados a crear asignaciones de propuestas nuevas. Cuando transfieres un repositorio desde una organización a una cuenta de usuario, solo se mantienen las propuestas asignadas al propietario del repositorio, y se eliminan todos los demás asignatarios de propuestas. +- Si el repositorio transferido contiene un {% data variables.product.prodname_pages %} sitio, se redirigen los enlaces al repositorio de Git en la web y a través de la actividad de Git. Sin embargo, no redirigimos {% data variables.product.prodname_pages %} asociadas al repositorio. +- Todos los enlaces a la ubicación anterior del repositorio se redirigen de manera automática hacia la ubicación nueva. Cuando utilices `git clone`, `git fetch` o `git push` en un repositorio transferido, estos comando redirigirán a la ubicación del repositorio o URL nueva. Sin embargo, para evitar confusiones, es altamente recomendable actualizar cualquier clon local existente para que apunte a la nueva URL del repositorio. Puedes hacerlo utilizando `git remote` en la línea de comando: + + ```shell + $ git remote set-url origin new_url + ``` + +Para obtener más información, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". + +#### Transferencias de repositorios y organizaciones + +Para transferir repositorios a una organización, debes tener permisos de creación de repositorios en la organización receptora. Si los propietarios de la organización inhabilitaron la creación de repositorios para los miembros de la organización, solo los propietarios de la organización pueden transferir repositorios hacia fuera o dentro de la organización. + +Una vez que se transfiere un repositorio a una organización, los parámetros de permiso del repositorio de la organización predeterminados y los privilegios de membresía predeterminados se aplicarán al repositorio transferido. + +### Transferir un repositorio que le pertenece a tu cuenta de usuario + +Puedes transferir tu repositorio a cualquier cuenta de usuario que acepte la transferencia de tu repositorio. Cuando se transfiere un repositorio entre dos cuentas de usuario, el propietario del repositorio original y los colaboradores se agregan automáticamente como colaboradores al repositorio nuevo. + +{% if currentVersion == "free-pro-team@latest" %}Si publicaste un sitio de {% data variables.product.prodname_pages %} en un repositorio privado y agregaste un dominio personalizado, antes de transferir el repositorio, deberás eliminar o actualizar tus registros de DNS para evitar el riesgo de que alguien más tome el dominio. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.transfer-repository-steps %} + +### Transferir un repositorio que le pertenece a tu organización + +Si tienes permisos de propietario en una organización o permisos de administración para uno de sus repositorios, puedes transferir un repositorio que le pertenece a tu organización a tu cuenta de usuario o a otra organización. + +1. Inicia sesión en tu cuenta de usuario que tiene permisos de administración o de propietario en la organización a la que le pertenece el repositorio. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.transfer-repository-steps %} diff --git a/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..5ad3fe0d23ace --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: Solución de problemas para verificaciones de estado requeridas +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. Para obtener más información, consulta las "[Verificaciones](/rest/reference/checks)". + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. Esto garantiza que tu rama ha sido probada con el último código desde la rama base. Si tu rama no está actualizada, necesitarás fusionar la rama base en tu rama. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". + +{% note %} + +**Nota:** También puedes actualizar tu rama con la rama base utilizando Git rebase. Para obtener más información, consulta [Accerca del rebase de Git](/github/using-git/about-git-rebase)." + +{% endnote %} + +No podrás subir cambios locales a una rama protegida hasta que se hayan aprobado todas las verificaciones de estado requeridas. En su lugar, recibirás un mensaje de error similar al siguiente. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. Esto se puede hacer sin las verificaciones de estado ejecutándose en la propia confirmación de fusión. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. If the test merge commit has a status, the test merge commit must pass. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![Ramas con conflictos en las confirmaciones de fusión](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md new file mode 100644 index 0000000000000..5d03aa7724087 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md @@ -0,0 +1,25 @@ +--- +title: Ver las ramas en tu repositorio +intro: 'Las ramas son centrales para la colaboración en {% data variables.product.product_name %}, y la mejor manera de verlas es en la pagina de ramas.' +redirect_from: + - /articles/viewing-branches-in-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +3. Utiliza la navegación en la parte superior de la página para ver las listas de ramas específicas: + - **Tus ramas**: en los repositorios a los que puedes tener acceso de escritura, la vista **Yours** (Tuyas) muestra todas las ramas a las que has subido contenido, y las más recientes se muestran primero. + - **Ramas activas**: la vista **Active** (Activas) muestra todas las ramas a las que alguien ha confirmado dentro de los últimos tres meses, ordenadas de forma descendente desde las ramas con las confirmaciones más recientes. + - **Ramas en espera**: la vista **Stale** (En espera) muestra todas las ramas en las que nadie ha confirmado durante los últimos tres meses, ordenadas de forma descendente desde las confirmaciones más antiguas. Utiliza esta lista para determinar [qué ramas eliminar](/articles/creating-and-deleting-branches-within-your-repository). + - **Todas las ramas**: la vista **All** (Todas) muestra la rama por defecto, seguida por todas las otras ramas ordenadas de forma descendente desde las ramas con las confirmaciones más recientes. + +![La página de ramas para el repositorio Atom](/assets/images/help/branches/branches-overview-atom.png) + +### Further reading + +- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" +- "[Eliminar ramas no utilizadas](/articles/deleting-unused-branches)" diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md new file mode 100644 index 0000000000000..55014b4023750 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md @@ -0,0 +1,28 @@ +--- +title: Ver la actividad de implementación de tu repositorio +intro: Puedes ver la información acerca de las implementaciones de tu repositorio completo o de una solicitud de extracción específica. +redirect_from: + - /articles/viewing-deployment-activity-for-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** el tablero de implementaciones está actualmente en beta y es susceptible a cambios. + +{% endnote %} + +Las personas con acceso de lectura a un repositorio pueden ver un resumen de todas las implementaciones actuales y un registro de la actividad de implementación pasada, si el flujo de trabajo de implementación del repositorio está integrado con {% data variables.product.product_name %} a través de las implementaciones API o una app de [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). Para obtener más información, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". + +También puedes ver información de implementación en la pestaña "Conversation" (Conversación) de una solicitud de extracción. + +### Ver el tablero de implementaciones + +{% data reusables.repositories.navigate-to-repo %} +2. Arriba de la lista de archivos, haz clic en **Environments (Entornos)**. ![Entornos por encima de la página del repositorio](/assets/images/help/repository/environments.png) + +### Further reading + - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md b/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md new file mode 100644 index 0000000000000..eb0ac18fd59d9 --- /dev/null +++ b/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md @@ -0,0 +1,36 @@ +--- +title: Visualizar los lanzamientos y etiquetas de tu repositorio +intro: Puedes ver el historial cronológico de tu repositorio por lanzamiento, nombre o número de versión de la etiqueta. +redirect_from: + - /articles/working-with-tags/ + - /articles/viewing-your-repositorys-tags + - /github/administering-a-repository/viewing-your-repositorys-tags +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% tip %} + +**Tip**: También puedes ver un lanzamientos utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta la sección "[`gh release view`](https://cli.github.com/manual/gh_release_view)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +### Visualizar lanzamientos + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +2. En la parte superior de la página de lanzamientos, da clic en **Lanzamientos**. + +### Visualizar etiquetas + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png) + +### Further reading + +- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md new file mode 100644 index 0000000000000..fd4cd3b4ce0e5 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md @@ -0,0 +1,92 @@ +--- +title: Acerca de las URL de imágenes anonimizadas +intro: 'Si cargas una imagen a {% data variables.product.product_name %}, la URL de la imagen será modificada para que tu información no se pueda seguir.' +redirect_from: + - /articles/why-do-my-images-have-strange-urls/ + - /articles/about-anonymized-image-urls +versions: + free-pro-team: '*' +--- + +Para alojar tus imágenes, {% data variables.product.product_name %} usa el [Camo del proyecto de código abierto](https://github.com/atmos/camo). Camo genera un proxy de URL anónimo para cada imagen que oculta los detalles de tu buscador y la información relacionada de otros usuarios. La URL inicia a `https://.githubusercontent.com/`, con subdominios diferentes dependiendo de cómo la cargues. + +Cualquiera que reciba tu URL de imagen anonimizada, directa o indirectamente, puede ver tu imagen. Para mantener las imágenes confidenciales en privado, limítalas a una red privada o a un servidor que requiera de autenticación en lugar de usar Camo. + +### Solución de problemas con Camo + +En circunstancias excepcionales, las imágenes procesadas mediante Camo podrían no aparecer en {% data variables.product.prodname_dotcom %}. Aquí presentamos algunos pasos que puedes tomar para determinar dónde está el problema. + +{% windows %} + +{% tip %} + +Los usuarios de Windows necesitarán usar PowerShell de Git (que está instalado junto a [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) o descargar [curl para Windows](http://curl.haxx.se/download.html). + +{% endtip %} + +{% endwindows %} + +#### Una imagen no aparece + +Si una imagen aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar solicitar la imagen localmente. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Solicita los encabezados de la imagen usando `curl`. + ```shell + $ curl -I https://www.my-server.com/images/some-image.png + > HTTP/1.1 200 OK + > Date: Fri, 06 Jun 2014 07:27:43 GMT + > Expires: Sun, 06 Jul 2014 07:27:43 GMT + > Content-Type: image/x-png + > Server: Google Frontend + > Content-Length: 6507 + ``` +3. Verifica el valor de `Content-Type`. En este caso, es `image/x-png`. +4. Verifica ese tipo de contenido con [la lista de tipos admitidos por Camo](https://github.com/atmos/camo/blob/master/mime-types.json). + +Si Camo no admite tu tipo de contenido, puedes probar varias acciones: + * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un tipo de contenido correcto para las imágenes. + * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. + * Realiza una solicitud de extracción para que Camo agregue tu tipo de contenido a la lista. + +#### Una imagen que cambió recientemente no se está actualizando + +Si recientemente modificaste una imagen y aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar restablecer la caché de la imagen. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Solicita los encabezados de la imagen usando `curl`. + ```shell + $ curl -I https://www.my-server.com/images/some-image.png + > HTTP/1.1 200 OK + > Expires: Fri, 01 Jan 1984 00:00:00 GMT + > Content-Type: image/png + > Content-Length: 2339 + > Server: Jetty(8.y.z-SNAPSHOT) + ``` + +Verifica el valor de `Cache-Control`. En este ejemplo, no hay `Cache-Control`. En ese caso: + * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un `Cache-Control` de `no-cache` para las imágenes. + * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. + + Si `Cache-Control` se *configura* como `no-cache`, contacta a {% data variables.contact.contact_support %} o busca ayuda en el {% data variables.contact.community_support_forum %}. + +#### Eliminar una imagen desde la caché de Camo + +Purgar la caché fuerza a cada usuario de {% data variables.product.prodname_dotcom %} a volver a solicitar la imagen, por lo que deberías usarla con mucha prudencia y solo en el caso de que los pasos anteriores no hayan funcionado. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Purga la imagen usando `curl -X PURGE` en la URL de Camo. + ```shell + $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223.... + > {"status": "ok", "id": "216-8675309-1008701"} + ``` + +#### Visualizar imágenes en redes privadas + +Si una imagen está siendo proporcionada desde una red privada o desde un servidor que requiere de autenticación, se puede ver mediante {% data variables.product.prodname_dotcom %}. De hecho, no puede ser vista por ningún usuario sin pedirle que se registre en el servidor. + +Para solucionar esto, mueva la imagen a un servicio que esté disponible públicamente. + +### Further reading + +- "[Imágenes de usuarios de conexiones proxy](https://github.com/blog/1766-proxying-user-images)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md new file mode 100644 index 0000000000000..cd7323b1d31bb --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md @@ -0,0 +1,54 @@ +--- +title: Acerca de la autenticación en GitHub +intro: 'Puedes acceder de manera segura a los recursos de tu cuenta si te atutenticas en {% data variables.product.product_name %}, utilizando diferentes credenciales dependiendo de en donde te autenticas.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de la autenticación en {% data variables.product.prodname_dotcom %} + +Para mantener tu cuenta segura, debes atutenticarte antes de poder acceder a{% if currentVersion != "github-ae@latest" %} algunos{% endif %} recursos en {% data variables.product.product_name %}. Cuando te autenticas en {% data variables.product.product_name %}, proporcionas o confirmas las credenciales que son específicas para ti y así compruebas de que eres exactamente quien estás declarando ser. + +Puedes acceder a tus recursos en {% data variables.product.product_name %} de muchas maneras: en el buscador, a través de {% data variables.product.prodname_desktop %} o de alguna otra aplicación de escritorio, con la API o a través de la línea de comandos. Cada forma de acceder a {% data variables.product.product_name %} es compatible con diferentes modalidades de autenticación. + +- {% if currentVersion == "github-ae@latest" %}Tu proveedor de identidad (IdP){% else %}Nombre de usuario y contraseña con autenticación bifactorial{% endif %} +- Token de acceso personal +- Llave SSH + +### Autenticarte en tu buscador + +Puedes autenticarte en {% data variables.product.product_name %} en tu buscador {% if currentVersion == "github-ae@latest" %} utilizando tu IdP. Para obtener más información, consulta la sección "[Acera de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".{% else %} de varias formas. + +- **Nombre de usuario y contraseña únicamente** + - Crearás una contraseña cuando crees tu cuenta de usuario en {% data variables.product.product_name %}. Te recomendamos que utilices un administrador de contraseñas para generar una contraseña aleatoria y única. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/creating-a-strong-password)". +- **Autenticación de dos factores (2FA)** (recomendada) + - Si habilitas la 2FA, también te pediremos que proporciones un código que genera una aplicación en tu dispositivo móvil o que mandes un mensaje de texto (SMS) después de que ingreses tu usuario y contraseña con éxito. Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". + - Adicionalmente a la autenticación con una aplicación móvil o con un mensaje de texto, puedes agregar opcionalmente un método secundario de autenticación con una llave de seguridad utilizando WebAuthn. Para obtener más información, consulta la sección "[Configurar la autenticación de dos factores utilizando una llave de seguridad](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +{% endif %} + +### Autenticarte con {% data variables.product.prodname_desktop %} + +Puedes autenticarte con {% data variables.product.prodname_desktop %} utilizando tu buscador. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." + +### Autenticarte con la API + +Puedes autenticarte con la API de varias formas. + +- **Tokens de acceso personal** + - En situaciones limitadas, tales como cuando se hacen pruebas, puedes utilizar un token de acceso personal para acceder a la API. El utilizar un token de acceso personal te habilita para revocarle el acceso en cualquier momento. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +- **Flujo de aplicaciones Web** + - Para las Apps de OAuth productivas, debes autenticarte utilizando el flujo de las aplicaciones web. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)". +- **GitHub Apps** + - Para las Github Apps productivas, debes autenticarte en nombre de la instalación de la app. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)". + +### Autenticarte con la línea de comandos + +Puedes acceder a los repositorios en {% data variables.product.product_name %} desde la línea de comandos en dos formas, HTTPS y SSH, y ambas tienen una forma diferente para autenticarte. El método para autenticarte se determina con base en si escoges una URL remota de HTTPS o SSH cuando clonas el repositorio. Para obtener más información acerca de en qué forma acceder, consulta la sección "[¿Qué URL remota debería usar?](/github/using-git/which-remote-url-should-i-use)" + +* Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de HTTPS, aún si estás detrás de un cortafuegos o de un proxy. Cada vez que utilizas Git para autenticarte con {% data variables.product.product_name %}, se te pedirá que ingreses tus credenciales para autenticarte con {% data variables.product.product_name %} a menos de que las guardes en caché con un [asistente de credenciales](/github/using-git/caching-your-github-credentials-in-git). {% data reusables.user_settings.password-authentication-deprecation %} + +* Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de SSH, aunque los cortafuegos y los proxys podrían rehusarse a permitir las conexiones de SSH. Para utilizar SSH necesitas generar un par de llaves pública/privada de SSH en tu máquina local y agregar la llave pública a tu cuenta de {% data variables.product.product_name %}. Cada que utilizas Git para autenticarte con {% data variables.product.product_name %}, se te solicitará que ingreses tu frase de ingreso de la llave SSH, a menos de que hayas [almacenado la llave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." + +{% if currentVersion == "free-pro-team@latest" %}Para utilizar un token de acceso personal o llave SSH para acceder a los recursos que pertenecen a una organización que utilice el inicio de sesión único de SAML, también debes autorizar el token personal o llave SSH. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o la sección "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..65cf92b98ff6b --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -0,0 +1,47 @@ +--- +title: Acerca de la autenticación con el inicio de sesión único de SAML +intro: 'Puedes acceder a {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}una organización que utilice el inicio de sesión único (SSO) de SAML{% endif %} si te autenticas {% if currentVersion == "github-ae@latest" %}con el inicio de sesión único (SSO) de SAML {% endif %}a través de un proveedor de identidad (IdP).{% if currentVersion == "free-pro-team@latest" %}Para autenticarte con la API o con Git en la línea de comandos cuando una organización requiera el SSO de SAML, debes autorizar tu token de acceso personal o llave de SSH.{% endif %}' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-authentication-with-saml-single-sign-on +versions: + free-pro-team: '*' + github-ae: '*' +--- + +{% if currentVersion == "github-ae@latest" %} + +El SSO de SAML permite que un propietario de empresa controle centralmente y asegure el acceso a {% data variables.product.product_name %} desde un IdP de SAML. Cuando visitas {% data variables.product.product_location %} en un buscador, {% data variables.product.product_name %} te redireccionará a tu IdP para autenticarte. Después de que te autenticas exitosamente con una cuenta en el IdP, éste te redirigirá de vuelta a {% data variables.product.product_location %}. {% data variables.product.product_name %} valida la respuesta de tu IdP y luego te otorga el acceso. + +{% data reusables.saml.you-must-periodically-authenticate %} + +Si nopuedes acceder a {% data variables.product.product_name %}, contacta al propietario o al administrador local de tu empresa para {% data variables.product.product_name %}. Puede que seas capaz de ubicar la información de contacto para tu empresa dando clic en **Soporte** en la parte inferior de cualquier página en {% data variables.product.product_name %}. {% data variables.product.company_short %} y {% data variables.contact.github_support %} carecen de acceso a tu IdP y no pueden solucionar problemas de autenticación. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% data reusables.saml.dotcom-saml-explanation %} Los propietarios de la organización pueden invitar a tu cuenta de usuario en {% data variables.product.prodname_dotcom %} para unirse a la organización que utiliza SAML SSO, lo cual te permite contribuir con ella y mantener tu identidad actual y las contribuciones con {% data variables.product.prodname_dotcom %}. + +Cuando accedes a recurso dentro de la organización que utiliza SAML SSO, , {% data variables.product.prodname_dotcom %} te redirigirá a el SAML IdP de la organización para autenticarte. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización. + +{% data reusables.saml.outside-collaborators-exemption %} + +Si te has autenticado recientemente con tu SAML IdP de la organización en tu navegador, estás autorizado automáticamente cuando accedas a la {% data variables.product.prodname_dotcom %} organización que utiliza SAML SSO. Si no te has autenticado recientemente con el SAML IdP de tu organización en tu navegador, debes hacerlo en el SAML IdP antes de acceder a la organización. + +{% data reusables.saml.you-must-periodically-authenticate %} + +Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada. Los tokens de acceso {% data variables.product.prodname_oauth_app %} están autorizados por defecto. + +Si no tienes un token de acceso personal ni una clave SSH, puedes crear un token de acceso personal para la línea de comandos o generar una clave SSH nueva. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" o "[Generar una nueva llave SSH y añadirla al agente de ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + +Para usar un token de acceso personal o una clave SSH nuevos o existentes con una organización que implementa SAML SSO, necesitarás autorizar el token o autorizar la clave SSH para usar con una organización de SAML SSO. Para obtener más información, consulta "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + +Debes tener una sesión activa de SAML cada que autorices un {% data variables.product.prodname_oauth_app %}. + +{% endif %} + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %}- "[Acerca de la administración de identidad y de acceso con el inicio de sesión único de 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" %}- "[Acerca de la administración de identidad y de acceso para tu empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md new file mode 100644 index 0000000000000..d997b1985e208 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -0,0 +1,74 @@ +--- +title: Acerca de la verificación de firma de confirmación +intro: 'Puedes firmar etiquetas y confirmaciones localmente utilizando GPG o S/MIME. Estas etiquetas o confirmaciones se marcan como verificadas en {% data variables.product.product_name %}, para que otras personas puedan confiar en que los cambios vienen de una fuente confiable.' +redirect_from: + - /articles/about-gpg-commit-and-tag-signatures/ + - /articles/about-gpg/ + - /articles/about-commit-signature-verification +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de la verificación de firma de confirmación + +Puedes firmar confirmaciones y etiquetas localmente, para que otras personas puedan verificar que tu trabajo viene de una fuente confiable. Si una confirmación o etiqueta tienen una firma GPG o S/MINE que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. + +![Confirmación verificada](/assets/images/help/commits/verified-commit.png) + +Si una confirmación o etiqueta tiene una firma que no puede ser comprobada, {% data variables.product.product_name %} marca la confirmación o la etiqueta como no verificada. + +Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-signed-commits)". + +Puedes comprobar el estado de verificación de tus confirmaciones o etiquetas firmadas en {% data variables.product.product_name %} y ver por qué las firmas de tu confirmación podrían no ser verificadas. Para obtener más información, consulta "[Comprobar la confirmación y el estado de verificación de firma de la etiqueta](/articles/checking-your-commit-and-tag-signature-verification-status)". + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Las confirmaciones que firme {% data variables.product.product_name %} tendrán un estado verificado en {% data variables.product.product_name %}. Puedes verificar la firma localmente usando la clave pública disponible en https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} + +### Verificación de firma de confirmación GPG + +Puedes usar GPG para firmar confirmaciones con una clave GPG que generas tu mismo. + +{% data variables.product.product_name %} usa las bibliotecas OpenPGP para confirmar que tus confirmaciones y etiquetas firmadas localmente son criptográficamente comprobables con una clave pública que has agregado a tu cuenta de {% data variables.product.product_name %}. + +Para firmar confirmaciones usando GPG y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: + +1. [Comprobar las claves GPG existentes](/articles/checking-for-existing-gpg-keys) +2. [Generar una clave GPG nueva](/articles/generating-a-new-gpg-key) +3. [Agregar una clave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account) +4. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) +5. [Firmar confirmaciones](/articles/signing-commits) +6. [Firmar etiquetas](/articles/signing-tags) + +### Verificación de firma de confirmación S/MIME + +Puedes usar S/MIME para firmar confirmaciones con una clave X.509 emitida por tu organización. + +{% data variables.product.product_name %} usa [el paquete de certificados CA Debian](https://packages.debian.org/hu/jessie/ca-certificates), el mismo almacenamiento de confianza usado por los navegadores Mozilla, para confirmar que tus confirmaciones y etiquetas firmadas localmente son criptográficamente comprobables con una clave pública en un certificado raíz de confianza. + +{% data reusables.gpg.smime-git-version %} + +Para firmar confirmaciones usando S/MIME y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: + +1. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) +2. [Firmar confirmaciones](/articles/signing-commits) +3. [Firmar etiquetas](/articles/signing-tags) + +No es necesario cargar tu clave pública a {% data variables.product.product_name %}. + +{% if currentVersion == "free-pro-team@latest" %} +### Verificación de firma para bots + +Las organizaciones y {% data variables.product.prodname_github_app %}s que requieren de la firma de confirmación pueden usar bots para firmar las confirmaciones. Si una confirmación o etiqueta tienen una firma de bot que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. +La verificación de firmas para los bots solo funcionará si la solicitud se verifica y autentica como la + +{% data variables.product.prodname_github_app %} o bot y no contiene información personalizada del autor, del confirmante, ni de la firma, tal como la API de confirmaciones. +{% endif %} + +### Further reading + +- "[Firmar confirmaciones](/articles/signing-commits)" +- "[Firmar etiquetas](/articles/signing-tags)" +- "[Solucionar problemas de la verificación de firma de confirmación](/articles/troubleshooting-commit-signature-verification)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md new file mode 100644 index 0000000000000..85a4c32a88032 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -0,0 +1,25 @@ +--- +title: Acerca de las direcciones de IP de GitHub +intro: '{% data variables.product.product_name %} proporciona aplicaciones desde varios rangos de dirección IP, que están disponibles usando la API.' +redirect_from: + - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/ + - /categories/73/articles/ + - /categories/administration/ + - /articles/github-s-ip-addresses/ + - /articles/about-github-s-ip-addresses + - /articles/about-githubs-ip-addresses +versions: + free-pro-team: '*' +--- + +Puedes recuperar una lista de direcciones IP de {% data variables.product.prodname_dotcom %} desde el punto de conexión de API [meta](https://api.github.com/meta). Para obtener más información, consulta la sección "[Meta](/rest/reference/meta)". + +Estos rangos están en [notación CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). Puedes usar una herramienta de conversión en línea como esta [Calculadora Supernet CIDR / VLSM](http://www.subnet-calculator.com/cidr.php) para convertir de una notación CIDR a rangos de dirección IP. + +De vez en cuando hacemos cambios en nuestras direcciones IP, y mantendremos esta API actualizada. No te recomendamos hacer una lista blanca por dirección de IP, sin embargo, si utilizas estos rangos de IP te exhortamos enfáticamente a monitorear nuestra API con frecuencia. + +Para que las aplicaciones funcionen, debes habilitar los puertos TCP 22, 80, 443 y 9418 mediante nuestros rangos de IP para `github.com`. + +### Further reading + +- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-ssh.md b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md new file mode 100644 index 0000000000000..4b1df462142e3 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md @@ -0,0 +1,33 @@ +--- +title: Acerca de SSH +intro: 'Usando el protocolo SSH, te puedes conectar y autenticar con servicios y servidores remotos. Con las llaves SSH puedes conectarte a {% data variables.product.product_name %} sin proporcionar tu nombre de usuario y token de acceso personal en cada visita.' +redirect_from: + - /articles/about-ssh +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando configuras SSH, [generarás una clave SSH y la agregarás al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) y luego [agregarás la clave a tu cuenta de {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account). Al agregar la clave SSH al ssh-agent te aseguras de que tu clave SSH tiene una capa extra de seguridad mediante el uso de una frase de contraseña. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)". + +{% if currentVersion == "free-pro-team@latest" %}Para utilizar tu llave SSH con un repositorio que pertenezca a una organización que utiliza el inicio de sesión único de SAML, necesitarás autorizarla primero. Para obtener más información, consulta "[Autorizar una clave SSH para usar con una clave de organización único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} + +Te recomendamos que regularmente [revises tu listado de claves SSH](/articles/reviewing-your-ssh-keys) y revoques cualquiera que no sea válida o que se haya visto comprometida. + +{% if currentVersion == "free-pro-team@latest" %} +Si no has utilizado tu llave SSH por un año, entonces +{% data variables.product.prodname_dotcom %} borrará automáticamente tu llave de SSH inactiva como precaución de seguridad. Para obtener más información, consulta "[Claves SSH eliminadas o faltantes](/articles/deleted-or-missing-ssh-keys)". +{% endif %} + +Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)". + +### Further reading + +- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" +- "[Probar tu conexión SSH](/articles/testing-your-ssh-connection)" +- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)" +- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)" +{%- if currentVersion == "free-pro-team@latest" %} +- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +{%- endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-two-factor-authentication.md b/translations/es-ES/content/github/authenticating-to-github/about-two-factor-authentication.md new file mode 100644 index 0000000000000..105bf5bfa7735 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/about-two-factor-authentication.md @@ -0,0 +1,39 @@ +--- +title: Acerca de la autenticación de dos factores +intro: '{% data reusables.two_fa.about-2fa %} Con la 2FA, tendrás que ingresar con tu nombre de usuario y contraseña y proporcionar otra forma de autenticación que solo tú sepas o a la que solo tú tengas acceso.' +redirect_from: + - /articles/about-two-factor-authentication +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Para {% data variables.product.product_name %}, la segunda forma de autenticación es un código que se genera con una aplicación en tu dispositivo móvil{% if currentVersion == "free-pro-team@latest" %} o que se envía como un mensaje de texto (SMS){% endif %}. Una vez que activas la 2FA, {% data variables.product.product_name %} genera un código de autenticación cada vez que alguien intenta iniciar sesión en tu cuenta de {% data variables.product.product_name %}. El único modo en que alguien puede iniciar sesión en tu cuenta es si conoce la contraseña y si tiene acceso al código de autenticación de tu teléfono. + +{% data reusables.two_fa.after-2fa-add-security-key %} + +También puedes configurar métodos de recuperación adicionales en caso de que pierdas el acceso a tus credenciales de autenticación de dos factores. Para obtener más información acerca de la configuración de la 2FA, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" y "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)". + +Te recomendamos **enfáticamente** que habilites la 2FA para mantener la seguridad de tu cuenta, no solo en {% data variables.product.product_name %}, sino en otros sitios web y aplicaciones que la admitan. Puedes habilitar la 2FA para acceder a {% data variables.product.product_name %} y a {% data variables.product.prodname_desktop %}. + +Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)". + +### Códigos de recuperación de autenticación de dos factores + +{% data reusables.two_fa.about-recovery-codes %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Advertencia**: {% data reusables.two_fa.support-may-not-help %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". + +{% endwarning %} + +{% endif %} + +### Solicitar autenticación de dos factores en tu organización + +Los propietarios de las organizaciones requieren que los miembros de las organizaciones{% if currentVersion == "free-pro-team@latest" %}, gerentes de facturación,{% endif %} y colaboradores externos utilicen autenticación bifactorial para asegurar sus cuentas personales. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)". + +{% data reusables.two_fa.auth_methods_2fa %} diff --git a/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md b/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md new file mode 100644 index 0000000000000..36dfb30de7e63 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md @@ -0,0 +1,67 @@ +--- +title: Acceder a GitHub utilizando la autenticación de dos factores +intro: 'Cuando habilitas la 2FA, se te pedirá que proporciones tu código de 2FA así como tu contraseña al momento de iniciar sesión en {% data variables.product.product_name %}.' +redirect_from: + - /articles/providing-your-2fa-security-code/ + - /articles/providing-your-2fa-authentication-code/ + - /articles/authenticating-to-github-using-fido-u2f-via-nfc/ + - /articles/accessing-github-using-two-factor-authentication +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Al tener la autenticación de dos factores habilitada, necesitarás proporcionar el código de autenticación cuando accedes a {% data variables.product.product_name %} a través de tu buscador. Si accedes a {% data variables.product.product_name %} utilizando otros métodos, tales como la API o la línea de comandos, necesitarás utilizar una forma alterna de autenticación. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". + +### Proporcionar un código 2FA al iniciar sesión en el sitio web + +Después de que ingresas a {% data variables.product.product_name %} utilizando tu contraseña, se te pedirá proporcionar un código de autenticación desde {% if currentVersion == "free-pro-team@latest" %}un mensaje de texto o{% endif %} desde tu app de TOTP. + +{% data variables.product.product_name %} solo te pedirá que brindes tu código de autenticación 2FA nuevamente si has cerrado sesión, estás usando un dispositivo nuevo o si caduca tu sesión. + +#### Generar un código a través de una aplicación TOTP + +Si decides configurar una autenticación de dos factores mediante una aplicación TOTP en tu smartphone, puedes generar un código de autenticación para {% data variables.product.product_name %} en cualquier momento. En la mayoría de los casos, el lanzamiento de la aplicación generará un código nuevo. Deberías consultar la documentación de la aplicación para conocer las instrucciones específicas. + +Si eliminas las aplicaciones móviles después de configurar la autenticación de dos factores, deberás proporcionar tu código de recuperación para obtener acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si perdiste las credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" + +{% if currentVersion == "free-pro-team@latest" %} + +#### Recibir un mensaje de texto + +Si configuras una autenticación de dos factores mediante mensajes de texto, {% data variables.product.product_name %} te enviará un mensaje de texto con tu código de autenticación. + +{% endif %} + +### Usar autenticación de dos factores con la línea de comando + +Después de haber habilitado 2FA, debes usar un token de acceso personal o una clave SSH en lugar de tu contraseña al acceder a {% data variables.product.product_name %} en la línea de comando. + +#### Autenticar en la línea de comando mediante HTTPS + +Después de haber habilitado 2FA, debes crear un token de acceso personal para usar una contraseña al autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL HTTPS. + +Cuando se te solicite el nombre de usuario y la contraseña en la línea de comando, usa tu nombre de usuario {% data variables.product.product_name %} y el token de acceso personal. La indicación de la línea de comando no especificará que debes ingresar tu token de acceso personal cuando se te solicite la contraseña. + +Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +#### Autenticar en la línea de comandos mediante SSH + +La habilitación de 2FA no cambia el modo de autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL SSH. Para obtener más información sobre cómo establecer y usar una clave SSH, consulta "[Conectar a {% data variables.product.prodname_dotcom %} con SSH](/articles/connecting-to-github-with-ssh/)". + +### Usar autenticación de dos factores para acceder a un repositorio mediante Subversion + +Cuando accedas a un repositorio mediante Subversion, debes proporcionar un token de acceso personal en lugar de ingresar tu contraseña. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +### Solución de problemas + +Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes usar tus códigos de recuperación u otro método de recuperación (si has configurado uno) para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". + +Si tu autenticación falla varias veces, es posible que desees sincronizar el reloj de tu teléfono con tu proveedor móvil. Frecuentemente, esto involucra la verificación de la opción "Establecer automáticamente" en el reloj de tu teléfono, en lugar de brindar tu propia zona horaria. + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" +- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" +- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md new file mode 100644 index 0000000000000..a861181de04ef --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md @@ -0,0 +1,35 @@ +--- +title: Agregar una llave GPG nueva a tu cuenta de GitHub +intro: 'Para configurar tu cuenta de {% data variables.product.product_name %} a fin de usar una llave GPG nueva (o existente), también deberás agregarla a tu cuenta de {% data variables.product.product_name %}.' +redirect_from: + - /articles/adding-a-new-gpg-key-to-your-github-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Antes de agregar una nueva llave GPG a tu cuenta de {% data variables.product.product_name %}, cerciórate de haber: +- [Comprobado tus llaves GPG existentes](/articles/checking-for-existing-gpg-keys) +- [Generado y copiado una nueva llave GPG](/articles/generating-a-new-gpg-key) + +{% data reusables.gpg.supported-gpg-key-algorithms %} + +Al verificar una firma, extraemos la firma e intentamos analizar sus id de llave. Complementamos los id de llave con las llaves cargadas a {% data variables.product.product_name %}. Hasta que cargues tu llave de GPG a {% data variables.product.product_name %}, no podemos verificar tus firmas. + +### Agregar una llave GPG + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +3. Haz clic en **New GPG key** (Nueva llave GPG). ![Botón de llave GPG](/assets/images/help/settings/gpg-add-gpg-key.png) +4. En el campo "Clave", pega la llave GPG que copiaste cuando [generó tu llave GPG](/articles/generating-a-new-gpg-key). ![Campo de llave](/assets/images/help/settings/gpg-key-paste.png) +5. Haz clic en **Add GPG key** (Agregar llave GPG). ![Botón Add key (Agregar llave)](/assets/images/help/settings/gpg-add-key.png) +6. Para confirmar la acción, escribe tu contraseña de {% data variables.product.product_name %}. + +### Further reading + +* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" +* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +* "[Firmar confirmaciones y etiquetas mediante llaves GPG](/articles/signing-commits-and-tags-using-gpg)" diff --git a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md new file mode 100644 index 0000000000000..62c60118998b2 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -0,0 +1,107 @@ +--- +title: Agregar una clave SSH nueva a tu cuenta de GitHub +intro: 'Para configurar tu cuenta de {% data variables.product.product_name %} a fin de usar tu clave SSH nueva (o existente), también deberás agregarla a tu cuenta de {% data variables.product.product_name %}.' +redirect_from: + - /articles/adding-a-new-ssh-key-to-your-github-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Antes de agregar una nueva llave GPG a tu cuenta de {% data variables.product.product_name %}, deberías haber: +* [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) +* [Generado una clave SSH nueva y haberla agregado al agente ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) + +Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product.product_name %}, puedes reconfigurar los repositorios locales para usar SSH. Para obtener más información, consulta "[Alternar URL remota de HTTPS a SSH](/articles/changing-a-remote-s-url/#switching-remote-urls-from-https-to-ssh)". + +{% data reusables.ssh.dsa-support %} + +{% mac %} + +1. Copia la llave SSH pública a tu portapapeles. + + Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + + ```shell + $ pbcopy < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard + ``` + + {% tip %} + + **Sugerencia:** Si `pbcopy` no está funcionando, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. + + {% endtip %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) +5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". +6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) +{% data reusables.user_settings.sudo-mode-popup %} + +{% endmac %} + +{% windows %} + +1. Copia la llave SSH pública a tu portapapeles. + + Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + + ```shell + $ clip < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard + ``` + + {% tip %} + + **Sugerencia:** Si `clip` no está funcionando, puedes ubicar la carpeta `.shh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. + + {% endtip %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) +5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". +6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) +8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) + +{% endwindows %} + +{% linux %} + +1. Copia la llave SSH pública a tu portapapeles. + + Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. + + ```shell + $ sudo apt-get install xclip + # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`) + + $ xclip -selection clipboard < ~/.ssh/id_ed25519.pub + # Copies the contents of the id_ed25519.pub file to your clipboard + ``` + {% tip %} + + **Sugerencia:** Si `xclip` no está funcionando, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. + + {% endtip %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) +5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". +6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) +8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) + +{% endlinux %} + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md new file mode 100644 index 0000000000000..2545f3cec4977 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -0,0 +1,52 @@ +--- +title: Asociar un correo electrónico con tu llave GPG +intro: 'Tu llave GPG debe estar asociada con un correo electrónico verificado de {% data variables.product.product_name %} que coincida con tu identidad de persona que confirma el cambio.' +redirect_from: + - /articles/associating-an-email-with-your-gpg-key +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +Si estás usando una llave GPG que coincida con la identidad de la persona que confirma el cambio y tu dirección de correo electrónico verificada con tu cuenta de {% data variables.product.product_name %}, puedes comenzar a firmar confirmaciones y firmar etiquetas. + +{% endnote %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +4. Escribe `gpg --edit-key GPG key ID`, sustituyendo la ID de la llave GPG que te gustaría usar. En el siguiente ejemplo, el ID de llave GPG es `3AA5C34371567BD2`: + ```shell + $ gpg --edit-key 3AA5C34371567BD2 + ``` +5. Escribe `gpg> adduid` para agregar los detalles de ID de usuario. + ```shell + $ gpg> adduid + ``` +6. Sigue las indicaciones para suminsitrar tu nombre real, dirección de correo electrónica o cualquier comentario. Puedes modificar tus entradas al elegir `N`, `C` o `E`. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/articles/setting-your-commit-email-address)".{% endif %} + ```shell + Real Name: Octocat + Email address: octocat@github.com + Comment: GitHub key + Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? + ``` +7. Escribe `O` para guardar tus selecciones. +8. Escribe la contraseña de tu llave. +9. Escribe `gpg --armor --export GPG key ID`, sustituyendo la ID de la llave GPG que te gustaría usar. En el siguiente ejemplo, el ID de llave GPG es `3AA5C34371567BD2`: + ```shell + $ gpg --armor --export 3AA5C34371567BD2 + # Prints the GPG key, in ASCII armor format + ``` +10. Carga la llave GPG al [agregarla a tu cuenta GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). + +### Further reading + +- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +- "[Utilizar una dirección de correo electrónico verificada en tu llave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" +- "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +- "[Firmar confirmaciones](/articles/signing-commits)" +- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..5c4dc30cd95ab --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md @@ -0,0 +1,13 @@ +--- +title: Autenticación con inicio de sesión único de SAML +intro: 'Puedes autenticarte en {% if currentVersion == "free-pro-team@latest" %} una organización de {% data variables.product.product_name %} {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}con el inicio de sesión único (SSO) de SAML{% if currentVersion == "free-pro-team@latest" %} y ver tus sesiones activas{% endif %}.' +mapTopic: verdadero +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ + - /articles/authenticating-with-saml-single-sign-on +versions: + free-pro-team: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..4ab56bd18a5a7 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -0,0 +1,23 @@ +--- +title: Autorizar un token de acceso personal para usar con un inicio de sesión único de SAML +intro: 'Para usar un token de acceso personal con una organización que usa el inicio de sesión único de SAML (SSO), primer debes autorizar el token.' +redirect_from: + - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on +versions: + free-pro-team: '*' +--- + +Puedes autorizar un token de acceso personal existente, o [crear un nuevo token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token) y luego autorizarlo. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +3. Junto al token que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/sso-allowlist-button.png) +4. Busca la organización para la que deseas autorizar el token de acceso. +4. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/token-authorize-button.png) + +### Further reading + +- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" +- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..86a578eedd694 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md @@ -0,0 +1,28 @@ +--- +title: Autorizar una clave SSH para usar con un inicio único de SAML +intro: 'Para usar una clave SSH con una organización que usa un inicio de sesión único (SSO) de SAML, primero debes autorizar la clave.' +redirect_from: + - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on +versions: + free-pro-team: '*' +--- + +Puedes autorizar una clave SSH existente, o crear una nueva clave SSH, y luego autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + +{% note %} + +**Nota:** Si tu autorización de clave SSH es revocada por una organización, no podrás volver a autorizar la misma clave. Deberás crear una nueva clave SSH y autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +3. Junto a la clave SSH que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/ssh-sso-button.png) +4. Busca la organización para la que deseas autorizar la clave SSH. +5. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/ssh-sso-authorize.png) + +### Further reading + +- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" +- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md new file mode 100644 index 0000000000000..86db9a7cadd8f --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md @@ -0,0 +1,86 @@ +--- +title: Autorizar aplicaciones OAuth +intro: 'Puedes conectar tu identidad {% data variables.product.product_name %} con aplicaciones de terceros mediante OAuth. Al autorizar un {% data variables.product.prodname_oauth_app %}, deberías asegurarte de que confías en la aplicación, revisar quién la desarrolló y revisar los tipos de información a la que desea acceder la aplicación.' +redirect_from: + - /articles/authorizing-oauth-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando una {% data variables.product.prodname_oauth_app %} quiere identificarte a través de tu cuenta de {% data variables.product.product_name %}, verás una página con la información de contacto del desarrollador de la app y una lista de los datos específicos que se han solicitado. + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Sugerencia:** Debes [verificar tu dirección de correo electrónico](/articles/verifying-your-email-address) antes de que puedas autorizar una {% data variables.product.prodname_oauth_app %}. + +{% endtip %} + +{% endif %} + +### Acceso a {% data variables.product.prodname_oauth_app %} + +Las {% data variables.product.prodname_oauth_app %} pueden tener acceso de *lectura* o *escritura* en tus datos de {% data variables.product.product_name %}. + +- El **acceso de lectura** solo permite que una app *mire* tus datos. +- El **acceso de escritura** permite que una app *cambie* tus datos. + +{% tip %} + +**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} + +{% endtip %} + +#### Acerca de los alcances de OAuth + +Los *alcances* son los grupos de permiso denominados que una {% data variables.product.prodname_oauth_app %} puede solicitar para acceder a datos públicos y no públicos. + +Cuando quieres usar una {% data variables.product.prodname_oauth_app %} que se integra con {% data variables.product.product_name %}, la app te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la app, la app podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_app %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". + +{% tip %} + +**Nota:** Actualmente, no puedes demarcar el acceso al código fuente a solo lectura. + +{% endtip %} + +#### Tipos de datos solicitados + +{% data variables.product.prodname_oauth_app %} puede solicitar diferentes tipos de datos. + +| Tipos de datos | Descripción | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Estado de confirmación | Puedes otorgar acceso para una app para que informe tu estado de confirmación. El acceso al estado de confirmación permite que las apps determinen si una construcción es exitosa frente a una confirmación específica. Las apps no tendrán acceso a tu código, pero podrán leer y escribir el estado de la información frente a una confirmación específica. | +| Implementaciones | El estado de implementación permite que las apps determinen si una implementación es exitosa frente a una confirmación específica para repositorios públicos y privados. Las apps no tendrán acceso a tu código. | +| Gists | El acceso a [Gist](https://gist.github.com) permite que las apps lean o escriban en tus Gists públicos y secretos. | +| Ganchos | El acceso a [webhooks](/webhooks) permite que las apps lean o escriban configuraciones de gancho en los repositorios que administras. | +| Notificaciones | El acceso a las notificaciones permite que las apps lean tus notificaciones de {% data variables.product.product_name %}, como comentarios sobre propuestas y solicitudes de extracción. Sin embargo, las apps permanecen inhabilitadas para acceder a tus repositorios. | +| Organizaciones y equipos | El acceso a organizaciones y equipos permite que las apps accedan y administren la membresía de la organización y del equipo. | +| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación. | +| Repositorios | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Las apps pueden solicitar acceso a repositorios públicos o privados a nivel del usuario. | +| Eliminación de repositorio | Las apps pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código. | + +### Solicitar permisos actualizados + +Cuando las {% data variables.product.prodname_oauth_app %} solicitan nuevos permisos de acceso, te notificarán sobre las diferencias entre los permisos actuales y los permisos nuevos. + +{% if currentVersion == "free-pro-team@latest" %} + +### {% data variables.product.prodname_oauth_app %} y organizaciones + +Cuando autorizas una {% data variables.product.prodname_oauth_app %} para tu cuenta de usuario personal, verás cómo la autorización afectará a cada organización de la que eres miembro. + +- **Para organizaciones *con restricciones de acceso a * {% data variables.product.prodname_oauth_app %}, puedes solicitar que los administradores de la organización aprueben la aplicación para usar en esa organización.** Si la organización no aprueba la aplicación, la aplicación solo podrá acceder a los recursos públicos de la organización. Si eres administrador de una organización, puedes [aprobar la aplicación](/articles/approving-oauth-apps-for-your-organization) por tu cuenta. + +- **Para organizaciones *sin* restricciones de acceso a {% data variables.product.prodname_oauth_app %}, la aplicación automáticamente estará autorizada para acceder a los recursos de esa organización.**Por este motivo, deberías tener cuidado con respecto a las {% data variables.product.prodname_oauth_app %} que apruebas para que tengan acceso a tus recursos de cuenta personal así como a los recursos de la organización. + +Si perteneces a cualquier organizacion que imponga el inicio de sesión único de SAML, debes tener una sesión activa de SAML para cada organización cada vez que autorices un {% data variables.product.prodname_oauth_app %}. + +### Further reading + +- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" +- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" + +{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md new file mode 100644 index 0000000000000..e8abd26dce107 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -0,0 +1,28 @@ +--- +title: Cambiar los métodos de entrega de autenticación de dos factores para tu dispositivo móvil +intro: Puedes alternar entre la recepción de código de autenticación a través de un mensaje de texto o una aplicación móvil. +redirect_from: + - /articles/changing-two-factor-authentication-delivery-methods/ + - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** El cambio de tu método de autenticación de dos factores invalida tu configuración de método de dos factores actual. Sin embargo, esto no afecta tus códigos de recuperación o configuración SMS de reserva. Puedes actualizar tus códigos de recuperación o configuración SMS de reserva o en la página de parámetros de seguridad de tu cuenta personal, si así lo deseas. + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +3. Al lado de "SMS delivery" (Entrega de SMS), haz clic en **Edit** (Editar). ![Editar opciones de entrega de SMS](/assets/images/help/2fa/edit-sms-delivery-option.png) +4. En "Delivery options" (Opciones de entrega), haz clic en **Reconfigure two-factor authentication** (Reconfirgurar autenticación de dos factores). ![Cambiar tus opciones de entrega 2FA](/assets/images/help/2fa/2fa-switching-methods.png) +5. Decide si deseas configurar la autenticación de dos factores mediante una app móvil TOTP o un mensaje de texto. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". + - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app). + - Para configurar la autenticación de dos factores mediante un mensaje de texto (SMS), haz clic en **Set up using SMS** (Configurar mediante SMS). + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md new file mode 100644 index 0000000000000..06fc006ac7e5c --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md @@ -0,0 +1,33 @@ +--- +title: Comprobar las llaves GPG existentes +intro: 'Antes de generar una llave GPG, puedes comprobar si tienes alguna clave GPG existente.' +redirect_from: + - /articles/checking-for-existing-gpg-keys +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.gpg.supported-gpg-key-algorithms %} + +{% note %} + +**Nota:** GPG no viene instalado por defecto en OS X o Windows. Para instalar las herramientas de la línea de comando, consulta [Página de descarga de GnuPG](https://www.gnupg.org/download/). + +{% endnote %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +3. Comprueba el resultado de los comandos para ver si tienes un par de llaves GPG. + * Si no hay pares de llaves GPG o no quieres usar algunas de las que están disponibles para las confirmaciones y las etiquetas firmadas, [genera una nueva llave GPG](/articles/generating-a-new-gpg-key). + * Si existe un nuevo par de llaves GPG existente y quieres usarlo para firmar confirmaciones y etiquetas, [agrega tu llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). + +### Further reading + +* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +* "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" +* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +* "[Firmar confirmaciones](/articles/signing-commits)" +* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md new file mode 100644 index 0000000000000..34bcd4e548a4d --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md @@ -0,0 +1,34 @@ +--- +title: Comprobar tus claves SSH existentes +intro: 'Antes de generar una clave SSH, puedes comprobar si tienes alguna clave SSH existente.' +redirect_from: + - /articles/checking-for-existing-ssh-keys +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.ssh.dsa-support %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Ingresa `ls -al ~/.ssh` para ver si hay claves SSH presentes: + + ```shell + $ ls -al ~/.ssh + # Lists the files in your .ssh directory, if they exist + ``` +3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Por defecto, los nombres de archivos de llave pública son uno de los siguientes: + - *id_rsa.pub* + - *id_ecdsa.pub* + - *id_ed25519.pub* + +Si no tienes un par de llaves pública y privada, o si no deseas utilizar las que están disponibles para conectarte a{% data variables.product.product_name %}, entonces [genera una llave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). + +Si ves que ya hay un par de llaves pública y privada listado (por ejemplo*id_rsa.pub* y *id_rsa*) que te gustaría utilizar para conectarte a {% data variables.product.product_name %}, entonces puedes [añadir tu llave SSH al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#adding-your-ssh-key-to-the-ssh-agent). + +{% tip %} + +**Sugerencia:** Si recibes un error que *~/.ssh* no existe, 'no te preocupes! Lo crearemos cuando [generemos una nueva clave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). + +{% endtip %} diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md new file mode 100644 index 0000000000000..e73976e3ad577 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md @@ -0,0 +1,36 @@ +--- +title: Comprobar el estado de verificación de firma de la confirmación y de la etiqueta +intro: 'Puedes comprobar el estado de verificación de las firmas de tu confirmación y de la etiqueta en {% data variables.product.product_name %}.' +redirect_from: + - /articles/checking-your-gpg-commit-and-tag-signature-verification-status/ + - /articles/checking-your-commit-and-tag-signature-verification-status +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Comprobar el estado de verificación de firma de la confirmación + +1. Activado + +{% data variables.product.product_name %}, navega a tu solicitud de cambios. +{% data reusables.repositories.review-pr-commits %} +3. Junto al hash de confirmación abreviado de la confirmación, existe un cuadro que muestra si la firma de la confirmación está verificada o no está verificada. ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) +4. Para ver información más detallada sobre la firma de confirmación, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). ![Confirmación firmada verificada](/assets/images/help/commits/gpg-signed-commit_verified_details.png) + +Si la firma de tu confirmación no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Confirmación firmada no verificada](/assets/images/help/commits/gpg-signed-commit-unverified-details.png) + +### Comprobar el estado de verificación de firma de la etiqueta + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png) +3. Junto a la descripción de tu etiqueta, hay un cuadro que muestra si la firma de la etiqueta está verificada o no está verificada. ![firma de etiqueta verificada](/assets/images/help/commits/gpg-signed-tag-verified.png) +4. Para ver información más detallada sobre la firma de la etiqueta, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). Si la firma de tu etiqueta no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png) + +### Further reading + +- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" +- "[Firmar confirmaciones](/articles/signing-commits)" +- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md new file mode 100644 index 0000000000000..90779406ffcb2 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md @@ -0,0 +1,111 @@ +--- +title: Configurar la autenticación de dos factores mediante métodos de recuperación +intro: Puedes configurar diversos métodos de recuperación para acceder a tu cuenta si pierdes tus credenciales de autenticación de dos factores. +redirect_from: + - /articles/downloading-your-two-factor-authentication-recovery-codes/ + - /articles/setting-a-fallback-authentication-number/ + - /articles/about-recover-accounts-elsewhere/ + - /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/ + - /articles/generating-and-storing-an-account-recovery-token/ + - /articles/configuring-two-factor-authentication-recovery-methods +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Además de almacenar tus códigos de recuperación de autenticación de dos factores de manera segura, recomendamos configurar uno o más métodos de recuperación adicionales. + +### Descargar tus códigos de recuperación de autenticación de dos factores + +{% data reusables.two_fa.about-recovery-codes %} También puedes descargar tus códigos de recuperación en cualquier punto luego de habilitar la autenticación de dos factores. + +Para mantener la cuenta segura, no compartas ni distribuyas tus códigos de recuperación. Recomendamos guardarlos en un administrador de contraseñas seguro, como: +- [1Password](https://1password.com/) +- [Keeper](https://keepersecurity.com/) +- [LastPass](https://lastpass.com/) + +Si generas nuevos códigos de recuperación o inhabilitas y vuelves a habilitar 2FA, los códigos de recuperación de tus parámetros de seguridad se actualizarán automáticamente. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +{% data reusables.two_fa.show-recovery-codes %} +4. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso. + - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar). + - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir). + - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) + +### Generar un nuevo conjunto de códigos de recuperación + +Una vez que usas un código de recuperación para recuperar el acceso a tu cuenta, no puedes volver a usarlo. Si has usado los 16 códigos de recuperación, puedes generar otra lista de códigos. La generación de un nuevo conjunto de códigos de recuperación invalidará todos los códigos que generaste previamente. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +{% data reusables.two_fa.show-recovery-codes %} +3. Para crear otro lote de códigos de recuperación, haz clic en **Generate new recovery codes** (Generar nuevos códigos de recuperación). ![Botón para generar nuevos códigos de recuperación](/assets/images/help/2fa/generate-new-recovery-codes.png) + +### Configurar una clave de seguridad como un método de autenticación de dos factores adicional + +Puedes configurar una clave de seguridad como un método de autenticación de dos factores secundario, y usar la clave de seguridad para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". + +{% if currentVersion == "free-pro-team@latest" %} + +### Configurar un número de autenticación de reserva + +Puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta. + +Puedes usar un número de reserva independientemente de que hayas configurado la autenticación mediante un mensaje de texto o aplicación móvil TOTP. + +{% warning %} + +**Advertencia:** Usar un número de reserva es tu último recurso. Recomendamos configurar métodos de recuperación adicionales si estableces un número de autenticación de reserva. +- Los malos actores pueden atacar a los proveedores de teléfono celular, de manera que la autenticación SMS es riesgosa. +- Los mensajes SMS solo son compatibles para determinados países fuera de los EE. UU., para conocer la lista, consulta "[Países donde la autenticación SMS es compatible](/articles/countries-where-sms-authentication-is-supported)". + +{% endwarning %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +3. Al lado de "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add** (Agregar). ![Botón para agregar número de SMS de reserva](/assets/images/help/2fa/add-fallback-sms-number-button.png) +4. En "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add fallbacck SMS number (Agregar número de SMS de reserva). ![Agregar texto al número de SMS de reserva](/assets/images/help/2fa/add_fallback_sms_number_text.png)

    +5 +Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Set fallback** (Establecer reserva). ![Establecer número de SMS de reserva](/assets/images/help/2fa/2fa-fallback-number.png) + +Después de la configuración, el dispositivo de copia de seguridad recibirá un SMS de confirmación. + +### Agregar un método de autenticación de reserva con Recuperar cuentas en otro lugar + +Puedes generar una credencial de autenticación adicional para tu cuenta y almacenarla con un proveedor de recuperación asociado. + +#### Acerca de Recuperar cuentas en otro lugar + +Con Recuperar cuentas en otro lugar, puedes agregar un factor de seguridad adicional a tu cuenta {% data variables.product.product_name %} en caso de que pierdas acceso al método de autenticación de dos factores o los códigos de recuperación. + +Recuperar cuentas en otro lugar te permite asociar tu cuenta {% data variables.product.product_name %} con tu cuenta de Facebook. Puedes almacenar una credencial de autenticación en la forma de un _token de recuperación de cuenta_ para tu cuenta {% data variables.product.product_name %} con Facebook. + +Si pierdes acceso a tu cuenta {% data variables.product.product_name %} porque ya no tienes acceso a tu método de autenticación de dos factores o códigos de recuperación, puedes recuperar tu token de recuperación de cuenta del proveedor de recuperación para demostrar que eres el propietario de tu cuenta {% data variables.product.product_name %}. + +Después de que recuperes tu token, {% data variables.contact.contact_support %} puede inhabilitar la autenticación de dos factores para tu cuenta. Luego, puedes proporcionar o restablecer tu contraseña para recuperar el acceso a tu cuenta. + +Cuando generas o recuperas un token de recuperación de cuenta, se agrega un evento a tu registro de auditoría de la cuenta. Para obtener más información, consulta "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)". + +#### Generar y almacenar un token de recuperación de cuenta + +Puedes generar un token de recuperación de cuenta y almacenarlo con un proveedor de recuperación asociado. + +1. Ingresa en tu cuenta de Facebook, luego regresa a + +{% data variables.product.product_name %}. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +4. Para generar un token nuevo, en "Recovery tokens" (Tokens de recuperación), haz clic en **Store new token** (Almacenar token nuevo). ![Botón para almacenar un nuevo token de recuperación](/assets/images/help/settings/store-new-recovery-token.png) +5. Obtén más información sobre tokens de recuperación de cuenta, luego haz clic en **Connect with https://www.facebook.com** (Conectar con https://www.facebook.com). ![Botón para conectar un token de recuperación con Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) +6. Una vez que eres redirigido a Facebook, lee la información sobre cómo activar la recuperación de cuenta con Facebook antes de hacer clic en **Save as [_YOUR NAME_]** (Guardar como [_TU NOMBRE_]. (Si guardas múltiples tokens dentro de un período breve, Facebook puede omitir este paso de confirmación después de que guardes tu primer token). ![Página de Facebook con botón para activar la recuperación de la cuenta](/assets/images/help/settings/security-turn-on-rae-facebook.png) + +{% endif %} + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" +- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" +- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md new file mode 100644 index 0000000000000..ea04a3e4718da --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md @@ -0,0 +1,103 @@ +--- +title: Configurar la autenticación de dos factores +intro: Puedes elegir entre varias opciones para añadir una segunda fuente de autenticación a tu cuenta. +redirect_from: + - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/ + - /articles/configuring-two-factor-authentication-via-text-message/ + - /articles/configuring-two-factor-authentication-via-fido-u2f/ + - /articles/configuring-two-factor-authentication +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Puedes configurar la autenticación bifactorial utilizando una app móvil{% if currentVersion == "free-pro-team@latest" %} o a través de un mensaje de texto{% endif %}. También puedes agregar una clave de seguridad. + +Te recomendamos ampliamente utilizar una aplicación generadora de contraseñas de una sola ocasión con temporización (TOTP) para configurar la 2FA.{% if currentVersion == "free-pro-team@latest" %} Las aplicaciones TOTP son más confiables que los SMS, especialmente para las ubicaciones fuera de los Estados Unidos.{% endif %} Las aplicaciones TOTP son compatibles con el respaldo seguro de tus códigos de autenticación en la nube y pueden restablecerse si pierdes el acceso a tu dispositivo. + +{% warning %} + +**Advertencia:** +- Si eres un miembro de{% if currentVersion == "free-pro-team@latest" %}, gerente de facturación,{% endif %} o colaborador externo de un repositorio privado de una organización que requiera autenticación bifactorial, debes salir de la organización antes de que puedas inhabilitar la 2FA en {% data variables.product.product_location %}. +- Si inhabilitas 2FA, automáticamente perderás acceso a la organización y a cualquier bifurcación privada que tengas de los repositorios privados de la organización. Para volver a obtener acceso a la organización y a tus bifurcaciones, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización. + +{% endwarning %} + +### Configurar la autenticación de dos factores mediante una app móvil TOTP + +Una aplicación de contraseña única basada en el tiempo (TOTP) genera automáticamente un código de autenticación que cambia después de un cierto período de tiempo. Recomendamos usar apps TOTP basadas en la nube como: +- [1Password](https://support.1password.com/one-time-passwords/) +- [Authy](https://authy.com/guides/github/) +- [LastPass Authenticator](https://lastpass.com/auth/) + +{% tip %} + +**Sugerencia**: Para configurar la autenticación mediante TOTP en múltiples dispositivos, durante la configuración, escanea el código QR usando todos los dispositivos al mismo tiempo. Si 2FA ya está habilitado y deseas agregar otro dispositivo, debes volver a configurar 2FA desde tus parámetros de seguridad. + +{% endtip %} + +1. Descargar una app TOTP. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +5. En la página de autenticación de dos factores, haz clic en **Set up using an app** (Configurar mediante una app). +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +8. En la página de autenticación de dos factores, realiza una de las siguientes opciones: + - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}. + - Si no puedes escanear el código QR, haz clic en **enter this text code** (escribir este código de texto) para ver un código que puedas copiar e ingresar manualmente en {% data variables.product.product_name %}. ![Haz clic para ingresar este código](/assets/images/help/2fa/totp-click-enter-code.png) +9. La aplicación móvil TOTP guarda tu +cuenta de {% data variables.product.product_name %} y genera un código de autenticación nuevo cada ciertos segundos. En {% data variables.product.product_name %}, en la página 2FA, escribe el código y haz clic en **Enable** (Habilitar). + ![Campo TOTP Enable (Habilitar TOTP)](/assets/images/help/2fa/totp-enter-code.png) +{% data reusables.two_fa.test_2fa_immediately %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Configurar la autenticación de dos factores mediante mensajes de texto + +Si no puedes habilitar la autenticación mediante una app móvil TOTP, puedes autenticar mediante mensajes SMS. También puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta. + +Antes de usar este método, asegúrate de que puedes recibir mensajes de texto. Es posible que se apliquen tarifas de protador. + +{% warning %} + +**Advertencia:** **Recomendamos enérgicamente** el uso de una aplicación TOTP para la autenticación de dos factores en lugar de SMS. {% data variables.product.product_name %} no admite el envío de mensajes SMS a teléfonos en todos los países. Antes de configurar la autenticación a través de mensaje de texto, revisa la lista de países donde {% data variables.product.product_name %} respalda la autenticación mediante SMS. Para obtener más información, consulta "[Países donde es compatible la autenticación SMS](/articles/countries-where-sms-authentication-is-supported)". + +{% endwarning %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +4. En la página de autenticación de dos factores, haz clic en **Set up using SMS** (Configurar mediante SMS). +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +7. Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Send authentication code** (Enviar código de autenticación). ![Pantalla 2FA SMS](/assets/images/help/2fa/2fa_sms_photo.png) +8. Recibirás un mensaje de texto con un código de seguridad. Escribe el código en la página de autenticación de dos factores, y haz clic en **Enable** (Habilitar). ![Campo 2FA SMS continue (Continuación de 2FA SMS)](/assets/images/help/2fa/2fa-sms-code-enable.png) +{% data reusables.two_fa.test_2fa_immediately %} + +{% endif %} + +### Configurar la autenticación de dos factores mediante una clave de seguridad + +{% data reusables.two_fa.after-2fa-add-security-key %} + +En muchos dispositivos y buscadores, puedes utilizar una llave de seguridad física por USB o NFC. Algunos buscadores utilizan un lector de huella digital, reconocimiento facial o contraseña/NIP en tu dispositivo a modo de llave de seguridad. + +La autenticación con una llave de seguridad es *secundaria* a la autenticación con una aplicación TOTP{% if currentVersion == "free-pro-team@latest" %} o con un mensaje de texto{% endif %}. Si pierdes tu llave de seguridad, aún podrás utilizar tu código de teléfono para ingresar. + +1. Ya debes haber configurado la 2FA a través de la app TOTP móvil{% if currentVersion == "free-pro-team@latest" %} o a través de SMS{% endif %}. +2. Asegúrate de que tengas una llave de seguridad compatible con WebAuthn insertada en tu computadora. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +5. Al lado de "Security keys" (Claves de seguridad), haz clic en **Add** (Agregar). ![Agrega la opción de las claves de seguridad](/assets/images/help/2fa/add-security-keys-option.png) +6. En "Security keys" (Claves de seguridad), haz clic en **Register new security key** (Registrar clave de seguridad nueva). ![Registrar una nueva clave de seguridad](/assets/images/help/2fa/security-key-register.png) +7. Escribe un sobrenombre para la clave de seguridad, luego haz clic en **Add** (Agregar). ![Porporcionar un sobrenombre para una clave de seguridad](/assets/images/help/2fa/security-key-nickname.png) +8. Activa tu clave de seguridad, seguida por la documentación de tu clave de seguridad.![Solicitar una clave de seguridad](/assets/images/help/2fa/security-key-prompt.png) +9. Confirma que has descargado tus códigos de recuperación y puedes acceder a ellos. Si aún no lo has hecho, o si deseas generar otro conjunto de códigos, descarga tus códigos y guárdalos en un lugar seguro. Si pierdes el acceso a tu cuenta, puedes usar tus códigos de recuperación para volver a ingresar a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". ![Botón Download recovery codes (Descargar códigos de recuperación)](/assets/images/help/2fa/2fa-recover-during-setup.png) +{% data reusables.two_fa.test_2fa_immediately %} + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" +- "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md b/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md new file mode 100644 index 0000000000000..531361da909a0 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md @@ -0,0 +1,19 @@ +--- +title: Conectar a GitHub con SSH +intro: 'Puedes conectarte con {% data variables.product.product_name %} mediante SSH.' +redirect_from: + - /key-setup-redirect/ + - /linux-key-setup/ + - /mac-key-setup/ + - /msysgit-key-setup/ + - /articles/ssh-key-setup/ + - /articles/generating-ssh-keys/ + - /articles/generating-an-ssh-key/ + - /articles/connecting-to-github-with-ssh +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/connecting-with-third-party-applications.md b/translations/es-ES/content/github/authenticating-to-github/connecting-with-third-party-applications.md new file mode 100644 index 0000000000000..b862872f8ea36 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/connecting-with-third-party-applications.md @@ -0,0 +1,71 @@ +--- +title: Conectar con aplicaciones de terceros +intro: 'Puedes conectar tu identidad {% data variables.product.product_name %} con aplicaciones de terceros mediante OAuth. Al autorizar una de estas aplicaciones, deberías asegurarte de que confías en la aplicación, revisar quién la desarrolló y revisar los tipos de información a la que desea acceder la aplicación.' +redirect_from: + - /articles/connecting-with-third-party-applications +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando una aplicación de terceros desea identificarte mediante tu inicio de sesión de {% data variables.product.product_name %}, verás una página con la información de contacto del programador y una lista de los datos específicos que se han solicitado. + +### Contactarse con el programador de la aplicación + +Dado que una aplicación está desarrollada por un tercero que no es {% data variables.product.product_name %}, no sabemos exactamente cómo una aplicación usa los datos a los que solicita acceso. Puedes usar la información del programador en la parte superior de la página para contactarte con el administrador de la aplicación si tienes preguntas o inquietudes sobre tu aplicación. + +![Información del propietario de {% data variables.product.prodname_oauth_app %}](/assets/images/help/platform/oauth_owner_bar.png) + +Si el programador ha elegido suministrarla, el lateral derecho de la página brinda una descripción detallada de la aplicación, así como su sitio web asociado. + +![Información de la aplicación OAuth y sitio web](/assets/images/help/platform/oauth_app_info.png) + +### Tipos de acceso a la aplicación y datos + +Las aplicaciones pueden tener acceso de *lectura* o *escritura* a tus datos de {% data variables.product.product_name %}. + +- El **acceso de lectura** solo permite que una aplicación *mire* tus datos. +- El **acceso de escritura** permite que una aplicación *cambie* tus datos. + +#### Acerca de los alcances de OAuth + +*Alcances* son grupos de permisos designados que una aplicación puede solicitar para acceder a los datos públicos y no públicos. + +Cuando quieres usar una aplicación de terceros que se integra con {% data variables.product.product_name %}, esa aplicación te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la aplicación, la aplicación podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_app %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". + +{% tip %} + +**Nota:** Actualmente, no puedes demarcar el acceso al código fuente a solo lectura. + +{% endtip %} + +#### Tipos de datos solicitados + +Existen varios tipos de datos que las aplicaciones pueden solicitar. + +![Detalles de acceso a OAuth](/assets/images/help/platform/oauth_access_types.png) + +{% tip %} + +**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} + +{% endtip %} + +| Tipos de datos | Descripción | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Estado de confirmación | Puedes otorgar acceso a una aplicación de terceros para que informe tu estado de confirmación. El acceso al estado de confirmación permite que las aplicaciones determinen si una construcción es exitosa frente a una confirmación específica. Las aplicaciones no tendrán acceso a tu código, pero pueden leer y escribir la información del estado frente a una confirmación específica. | +| Implementaciones | El acceso a los estados de despliegue permite a las aplicaciones determinar si un despliegue fue exitoso contra una confirmación específica para los repositorios públicos y privados. Las aplicaciones no tendrán acceso a tu código. | +| Gists | El acceso a [Gist](https://gist.github.com) permite que las aplicaciones lean o escriban en tus Gists públicos y secretos. | +| Ganchos | El acceso a [webhooks](/webhooks) permite que las aplicaciones lean o escriban configuraciones de gancho en los repositorios que administras. | +| Notificaciones | El acceso a las notificaciones permite a las aplicaciones leer tus notificaciones de {% data variables.product.product_name %}, tales como los comentarios sobre las propuestas y las solicitudes de cambios. Sin embargo, las aplicaciones permanecen inhabilitadas para acceder a tus repositorios. | +| Organizaciones y equipos | El acceso a organizaciones y equipos permite que las apps accedan y administren la membresía de la organización y del equipo. | +| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación. | +| Repositorios | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Las aplicaciones pueden solicitar acceso a repositorios públicos o privados a nivel del usuario. | +| Eliminación de repositorio | Las aplicaciones pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código. | + +### Solicitar permisos actualizados + +Las aplicaciones pueden solicitar nuevos privilegios de acceso. Al solicitar permisos actualizados, la aplicación te notificará de las diferencias. + +![Cambiar el acceso a aplicaciones de terceros](/assets/images/help/platform/oauth_existing_access_pane.png) diff --git a/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md b/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md new file mode 100644 index 0000000000000..39a5b4ed8cb25 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md @@ -0,0 +1,134 @@ +--- +title: Países donde se admite la autenticación por SMS +intro: 'Debido a las tasas de éxito de la entrega, {% data variables.product.product_name %} solo admite autenticación de dos factores mediante SMS para determinados países.' +redirect_from: + - /articles/countries-where-sms-authentication-is-supported +versions: + free-pro-team: '*' +--- + +Si no admitimos la autenticación de dos factores mediante mensaje de texto para tu país de residencia, puedes establecer la autenticación mediante una aplicación móvil TOTP. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". + +### Países admitidos para autenticación SMS + +Si tu país no está en la lista, significa que actualmente no podemos entregar mensajes de texto confiables a tu país. Actualizamos esta lista periódicamente. + +
      +
    • Islas Aland
      • +
    • Algeria
      • +
    • Angola
      • +
    • Anguilla
      • +
    • Australia
      • +
    • Austria
      • +
    • Bahamas
      • +
    • Bahrain
      • +
    • Bangladesh
      • +
    • Bielorusia
      • +
    • Bélgica
      • +
    • Benin
      • +
    • Bolivia
      • +
    • Bosnia y Herzegovina
      • +
    • Brunei
      • +
    • Bulgaria
      • +
    • Burundi
      • +
    • Camboya
      • +
    • Canadá
      • +
    • Cabo Verde
      • +
    • Islas Caimán
      • +
    • Isla de Navidad
      • +
    • Cocos
      • +
    • República Democrática del Congo
      • +
    • Croacia
      • +
    • Chipre
      • +
    • República Checa
      • +
    • Dinamarca
      • +
    • Dominica
      • +
    • República Dominicana
      • +
    • Ecuador
      • +
    • Guinea Ecuatorial
      • +
    • Estonia
      • +
    • Finlandia/Islas Aland
      • +
    • Francia
      • +
    • La Gambia
      • +
    • Georgia
      • +
    • Alemania
      • +
    • Ghana
      • +
    • Gibraltar
      • +
    • Grecia
      • +
    • Guatemala
      • +
    • Guyana
      • +
    • Hungría
      • +
    • Islandia
      • +
    • India
      • +
    • Indonesia
      • +
    • Irán
      • +
    • Irlanda
      • +
    • Israel
      • +
    • Italia
      • +
    • Costa de Marfil
      • +
    • Jamaica
      • +
    • Japón
      • +
    • Jordania
      • +
    • Kazakhstan
      • +
    • Kuwait
      • +
    • Letonia
      • +
    • Libia
      • +
    • Liechtenstein
      • +
    • Lituania
      • +
    • Luxemburgo
      • +
    • Madagascar
      • +
    • Malawi
      • +
    • Malasia
      • +
    • Maldivas
      • +
    • Mali
      • +
    • Malta
      • +
    • Isla Mauricio
      • +
    • México
      • +
    • Mónaco
      • +
    • Montenegro
      • +
    • Montserrat
      • +
    • Mozambique
      • +
    • Namibia
      • +
    • Países Bajos
      • +
    • Antillas Neerlandesas
      • +
    • Nueva Zelanda
      • +
    • Nigeria
      • +
    • Noruega
      • +
    • Filipinas
      • +
    • Polonia
      • +
    • Portugal
      • +
    • Catar
      • +
    • Rumania
      • +
    • Rusia
      • +
    • Ruanda
      • +
    • Senegal
      • +
    • Serbia
      • +
    • Islas Seychelles
      • +
    • Singapur
      • +
    • Eslovaquia
      • +
    • Eslovenia
      • +
    • Sudáfrica
      • +
    • Corea del Sur
      • +
    • España
      • +
    • Sri Lanka
      • +
    • St. Lucía
      • +
    • Sudán
      • +
    • Suecia
      • +
    • Suiza
      • +
    • Taiwán
      • +
    • Tanzania
      • +
    • Togo
      • +
    • Trinidad y Tobago
      • +
    • Turcas y Caicos
      • +
    • Uganda
      • +
    • Ucrania
      • +
    • Emiratos Árabes Unidos
      • +
    • Reino Unido
      • +
    • Estados Unidos
      • +
    • Uzbekistán
      • +
    • Venezuela
      • +
    + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md new file mode 100644 index 0000000000000..b99f7b6557406 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -0,0 +1,51 @@ +--- +title: Crear un token de acceso personal +intro: Debes crear un token de acceso personal para utilizar como contraseña con la línea de comandos o con la API. +redirect_from: + - /articles/creating-an-oauth-token-for-command-line-use/ + - /articles/creating-an-access-token-for-command-line-use/ + - /articles/creating-a-personal-access-token-for-the-command-line + - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas para la autenticación en {% data variables.product.product_name %} cuando utilizas la [API de GitHub](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) o la [línea de comandos](#using-a-token-on-the-command-line). + +{% if currentVersion == "free-pro-team@latest" %}Si quieres utilizar un PAT para acceder a los recursos que pertenecen a una organización que utiliza el SSO de SAML, debes autorizarlo. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} + +### Crear un token + +{% if currentVersion == "free-pro-team@latest" %}1. [Verifica tu dirección de correo electrónico](/articles/verifying-your-email-address), si aún no ha sido verificada.{% endif %} +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +4. Haz clic en **Generar un nuevo token**. ![Generar el botón para el nuevo token](/assets/images/help/settings/generate_new_token.png) +5. Asígnale a tu token un nombre descriptivo. ![Campo para la descripción del token](/assets/images/help/settings/token_description.png) +6. Selecciona los alcances o permisos que deseas otorgarle a este token. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona **repo**. ![Seleccionar los alcances del token](/assets/images/help/settings/token_scopes.gif) +7. Haz clic en **Generar token**. ![Generar un botón para el token](/assets/images/help/settings/generate_token.png) +8. Haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar el token en tu portapapeles. Por razones de seguridad, después de que navegas fuera de la página, no podrás ver el token nuevamente.{% if currentVersion == "free-pro-team@latest" %} ![Newly created token](/assets/images/help/settings/personal_access_tokens.png){% else %} +![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png){% endif %} + + {% warning %} + + **Advertencia:**Preserva tus tokens de la misma manera que tus contraseñas y no se las reveles a nadie. Cuando trabajes con la API, usa tokens como variables del entorno en lugar de codificarlos de forma rígida en tus programas. + + {% endwarning %} +{% if currentVersion == "free-pro-team@latest" %}9. Para usar tu token a fin de autenticar a una organización que usa SAML SSO, [autoriza el token para usarlo con una organización con inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %} + +### Usar un token en la línea de comando + +{% data reusables.command_line.providing-token-as-password %} + +Los tokens de acceso personal solo se pueden usar para operaciones HTTPS Git. Si tu repositorio usa una URL SSH remota, necesitarás [pasar de la URL SSH remota a HTTPS](/articles/changing-a-remote-s-url/#switching-remote-urls-from-ssh-to-https). + +Si no se te solicita tu nombre de usuario y contraseña, tus credenciales pueden estar almacenadas en la caché de tu computadora. Puedes [actualizar tus credenciales en la keychain](/articles/updating-credentials-from-the-osx-keychain) para reemplazar tu contraseña anterior con el token. + +### Further reading + +- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md new file mode 100644 index 0000000000000..6a7da79688e6f --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md @@ -0,0 +1,31 @@ +--- +title: Crear una contraseña segura +intro: 'Protege tu cuenta de {% data variables.product.product_name %} con una contraseña segura y única usando un administrador de contraseñas.' +redirect_from: + - /articles/what-is-a-strong-password/ + - /articles/creating-a-strong-password +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Debes elegir o generar una contraseña para tu cuenta de {% data variables.product.product_name %} que por lo menos cumpla con: +- Ocho caracteres de largo, si incluye un número o una letra minúscula, o bien +- 16 caracteres de largo con cualquier combinación de caracteres + +Para preservar la seguridad de tu cuenta, te recomendamos que sigas estas buenas prácticas: +- Utiliza un administrador de contraseñas, como [LastPass](https://lastpass.com/) o[1Password](https://1password.com/), para generar una contraseña de más de 16 caracteres. +- Genera una contraseña que sea única para {% data variables.product.product_name %}. Si usas tu contraseña de {% data variables.product.product_name %} en algún otro lugar y ese servicio se ve comprometido, los atacantes u otros actores maliciosos pueden usar esa información para acceder a tu cuenta de {% data variables.product.product_name %}. +- Configura la autenticación de dos factores para tu cuenta personal. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)". +- Nunca compartas tu contraseña con nadie, aunque se trate de un potencial colaborador. Cada persona debe usar su propia cuenta personal en {% data variables.product.product_name %}. Para obtener más información acerca de cómo colaborar, consulta: "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)," "[Acerca de los modelos de desarrollo colaborativos](/articles/about-collaborative-development-models/)," o "[Colaborar con los grupos en las organizaciones](/articles/collaborating-with-groups-in-organizations/)". + +{% data reusables.repositories.blocked-passwords %} + +Solo puedes utilizar tu contraseña para ingresar en {% data variables.product.product_name %} a través de tu buscador. Cuadno te atutenticas en {% data variables.product.product_name %} con otros medios, tales como la línea de comandos o la API, debes utilizar otras credenciales. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". + +{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %} + +### Further reading + +- [Almacenar tus credenciales de {% data variables.product.product_name %} en la caché en Git](/github/using-git/caching-your-github-credentials-in-git/)" +- "[Preservar la seguridad de tu cuenta y tus datos](/articles/keeping-your-account-and-data-secure/)" diff --git a/translations/es-ES/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md b/translations/es-ES/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md new file mode 100644 index 0000000000000..1f3ed3b830365 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md @@ -0,0 +1,14 @@ +--- +title: Claves SSH eliminadas o faltantes +intro: 'Como precaución de seguridad, {% data variables.product.prodname_dotcom %} elimina automáticamente las claves SSH que no se han usado durante un año.' +redirect_from: + - /articles/deleted-or-missing-ssh-keys +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} elimina automáticamente las claves SSH inactivas para mantener la seguridad de las cuentas, por ejemplo, cuando alguien deja el trabajo o pierde su computadora. + +Puedes verificar si has usado o no una clave SSH durante un año revisando el registro de seguridad de tu cuenta. Para obtener más información, consulta "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log/)". + +Una vez que tu clave SSh se ha eliminado, debes generar una nueva clave SSH y asociarla con tu cuenta. Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)" y "[Agregar una nueva clave SSH a tu cuenta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account/)". diff --git a/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md b/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md new file mode 100644 index 0000000000000..b86e1cd0d6f1d --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md @@ -0,0 +1,33 @@ +--- +title: Inhabilitar la autenticación de dos factores para tu cuenta personal +intro: 'Si inhabilitas la autenticación de dos factores para tu cuenta personal, puedes perder acceso a las organizaciones a las que perteneces.' +redirect_from: + - /articles/disabling-two-factor-authentication-for-your-personal-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Te recomendamos encarecidamente que uses la autenticación de dos factores para proteger tu cuenta. Si necesitas inhabilitar la autenticación de dos factores, te recomendamos habilitarla nuevamente lo antes posible. + +{% warning %} + +**Advertencia:** Si eres un miembro{% if currentVersion == "free-pro-team@latest" %}, gerente de facturación,{% endif %} o colaborador externo para un repositorio público o para una organización que requiere de autenticación bifactorial e inhabilitas la 2FA, se te eliminará automáticamente de la organización y perderás tu acceso a sus repositorios. Para volver a obtener acceso a la organización, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización. + +{% endwarning %} + +Si tu organización requiere autenticación de dos factores y eres un miembro, propietario o colaborador externo de un repositorio privado de tu organización, primero debes abandonar la organización para poder inhabilitar la autenticación de dos factores. + +Para eliminarte a ti mismo de la organización: + - Como miembro o propietario de la organización, consulta "[Eliminarte a ti mismo de una organización](/articles/removing-yourself-from-an-organization/)". + - Como colaborador externo, solicita a un propietario de la organización o administrador de un repositorio que te elimine de los repositorios de la organización. Para obtener más información, consulta "[Ver los roles de las personas en una organización](/articles/viewing-people-s-roles-in-an-organization)" y "[Eliminar un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository/)". + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +3. Da clic en **Inhabilitar**. ![Botón Inhabilitar autenticación de dos factores](/assets/images/help/2fa/disable-two-factor-authentication.png) + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" +- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-ES/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md b/translations/es-ES/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md new file mode 100644 index 0000000000000..9d9145f3d4e39 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md @@ -0,0 +1,47 @@ +--- +title: 'Error: El agente admitió una falla para registrarse' +intro: 'En circunstancias muy poco frecuentes, al conectarse con {% data variables.product.product_name %} mediante SSH en Linux produce el error "El agente admitió una falla para registrarse usando la clave". Sigue los pasos siguientes para resolver el problema.' +redirect_from: + - /articles/error-agent-admitted-failure-to-sign-using-the-key/ + - /articles/error-agent-admitted-failure-to-sign +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando intentes implementar SSH en {% data variables.product.product_location %} en una computadora con Linux, posiblemente veas el siguiente mensaje en tu terminal: + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> ... +> Agent admitted failure to sign using the key. +> debug1: No more authentication methods to try. +> Permission denied (publickey). +``` + +Para conocer más detalles, consulta este informe de propuesta. + +### Resolución + +Deberías poder solucionar este error al cargar tus claves en tu agente de SSH con `ssh-add`: + +```shell +# start the ssh-agent in the background +$ eval "$(ssh-agent -s)" +> Agent pid 59566 +$ ssh-add +> Enter passphrase for /home/you/.ssh/id_rsa: [tippy tap] +> Identity added: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) +``` + +Si tu clave no tiene el nombre de archivo predeterminado (`/.ssh/id_rsa`), deberás pasar esa ruta a `ssh-add`: + +```shell +# start the ssh-agent in the background +$ eval "$(ssh-agent -s)" +> Agent pid 59566 +$ ssh-add ~/.ssh/my_other_key +> Enter passphrase for /home/you/.ssh/my_other_key: [tappity tap tap] +> Identity added: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) +``` diff --git a/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md b/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md new file mode 100644 index 0000000000000..a04f3b1d2687a --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md @@ -0,0 +1,56 @@ +--- +title: 'Error: Número de archivo erróneo' +intro: Este error, por lo general, significa que no has podido conectarte al servidor. A menudo es causado por los firewalls y los servidores proxy. +redirect_from: + - /articles/error-bad-file-number +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando ejecutes comandos Git remotos o SSH, tu conexión puede quedar inactiva: + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> OpenSSH_8.1p1, LibreSSL 2.7.3 +> debug1: Connecting to {% data variables.command_line.codeblock %} [207.97.227.239] port 22. +> debug1: connect to address 207.97.227.239 port 22: Connection timed out +> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Connection timed out +> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Bad file number +``` + +### Resolver el problema + +#### Usa HTTPS + +A menudo la solución más sencilla es simplemente evitar por completo el SSH. La mayoría de los firewalls y los proxys permiten el tráfico de HTTPS sin problemas. Para aprovechar esto, cambia [la URL remota](/articles/which-remote-url-should-i-use) que estás usando: + +```shell +$ git clone https://{% data variables.command_line.codeblock %}/username/reponame.git +> Cloning into 'reponame'... +> remote: Counting objects: 84, done. +> remote: Compressing objects: 100% (45/45), done. +> remote: Total 84 (delta 43), reused 78 (delta 37) +> Unpacking objects: 100% (84/84), done. +``` + +#### Prueba desde una red diferente + +Si puedes conectar la computadora a otra red que no tenga un firewall, puedes tratar de probar tu conexión de SSH a {% data variables.product.product_name %}. Si todo funciona como es debido, comunícate con tu administrador de red para que te ayude a cambiar los parámetros del firewall para permitir que tu conexión de SSH a {% data variables.product.product_name %} se establezca sin problemas. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Uso de SSH a través del puerto HTTPS + +Si usar HTTPS no es una opción y tu administrador de firewall no permite las conexiones de SSH, puedes intentar usar [SSH a través del puerto HTTPS](/articles/using-ssh-over-the-https-port). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Further reading + +- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" + +{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/error-key-already-in-use.md b/translations/es-ES/content/github/authenticating-to-github/error-key-already-in-use.md new file mode 100644 index 0000000000000..33cab8089db4c --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-key-already-in-use.md @@ -0,0 +1,33 @@ +--- +title: 'Error: La clave ya está en uso' +intro: 'Este error se produce cuando intentas [agregar una clave](/articles/adding-a-new-ssh-key-to-your-github-account) que ya ha sido agregada a otra cuenta o repositorio.' +redirect_from: + - /articles/error-key-already-in-use +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Determinar dónde se ha usado la clave + +Para determinar dónde se ha usado la clave, abre una terminal y escribe el comando `ssh`. Usa la marca `-i` para obtener la ruta a la clave que deseas verificar: + +```shell +$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} +# Connect to {% data variables.product.product_location %} using a specific ssh key +> Hi username! You've successfully authenticated, but GitHub does not +> provide shell access. +``` + +El *nombre de usuario* que aparece en la respuesta es la cuenta de {% data variables.product.product_name %} a la que la clave se encuentra actualmente vinculada. Si la respuesta se parece a "username/repo", la llave se ha vinculado a un repositorio como [*llave de implementación*](/guides/managing-deploy-keys#deploy-keys). + +### Resolver el problema + +Para resolver el problema, primero elimina la clave de la otra cuenta o repositorio y luego [agrégala a tu cuenta](/articles/adding-a-new-ssh-key-to-your-github-account). + +Si no tienes permisos para transferir la clave y no puedes comunicarte con un usuario que los tenga, elimina el par de claves y [genera uno nuevo](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). + +### Llaves de implementación + +Una vez que una clave se ha vinculado a un repositorio como llave de implementación, no se la puede usar en otro repositorio. Si se te muestra este error mientras configuras las llaves de despliegue, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)". diff --git a/translations/es-ES/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/es-ES/content/github/authenticating-to-github/error-permission-denied-publickey.md new file mode 100644 index 0000000000000..e510edd05b216 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-permission-denied-publickey.md @@ -0,0 +1,278 @@ +--- +title: 'Error: Permiso denegado (publickey)' +intro: 'Un error de "Permiso denegado" significa que el servidor rechazó tu conexión. Esto puede suceder por varias razones. A continuación se explican los ejemplos más comunes.' +redirect_from: + - /articles/error-permission-denied-publickey +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### ¿El comando `sudo` se debe usar con Git? + +No deberías estar usando el comando `sudo` con Git. Si tienes una *muy buena razón* para usar `sudo`, asegúrate de estar usándolo con todos los comandos (probablemente es mejor que uses `su` para obtener un shell como raíz en este punto). Si [generas claves SSH](/articles/generating-an-ssh-key) sin `sudo` y luego intentas usar un comando como `sudo git push`, no estarás usando las mismas claves que generaste. + +### Verifica si estás conectado al servidor correcto + +Escribir no es fácil. Todos los sabemos. Escribe con cuidado; no podrás conectarte con "githib.com" ni a "guthub.com". En algunos casos, una red corporativa puede generar problemas al tratar de resolver también el registro de DNS. + +Para asegurarte de que te estás conectando al dominio correcto, puedes ingresar el siguiente comando: + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> OpenSSH_8.1p1, LibreSSL 2.7.3 +> debug1: Reading configuration data /Users/you/.ssh/config +> debug1: Reading configuration data /etc/ssh/ssh_config +> debug1: /etc/ssh/ssh_config line 47: Applying options for * +> debug1: Connecting to {% data variables.command_line.codeblock %} port 22. +``` + +La conexión debe hacerse en el puerto 22{% if currentVersion == "free-pro-team@latest" %}, a menos de que estés ignorando la configuración para utilizar [SSH sobre HTTPS](/articles/using-ssh-over-the-https-port){% endif %}. + +### Siempre usa el usuario "git" + +Todas las conexiones, incluidas las de URL remotas, deben hacerse como el usuario "git". Si intentas conectarte con tu nombre de usuario de {% data variables.product.product_name %}, la conexión fallará: + +```shell +$ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %} +> Permission denied (publickey). +``` +Si tu conexión ha fallado y estás usando una URL remota con tu nombre de usuario de {% data variables.product.product_name %}, puedes [cambiar tu URL remota para usar el usuario "git"](/articles/changing-a-remote-s-url/). + +Para verificar tu conexión, debes escribir: + +```shell +$ ssh -T git@{% data variables.command_line.codeblock %} +> Hi username! You've successfully authenticated... +``` + +### Asegúrate de tener una clave que esté en uso + +{% mac %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Verifica si tienes una llave privada generada y cargada en SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}Si estàs utilizando OpenSSH 6.7 o superior: + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows_git_bash %} + +1. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} + + {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} +2. Verifica si tienes una llave privada generada y cargada en SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +{% endwindows %} + +{% linux %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Verifica si tienes una llave privada generada y cargada en SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + + +{% endlinux %} + +The `ssh-add` command *should* print out a long string of numbers and letters. If it does not print anything, you will need to [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and associate it with {% data variables.product.product_name %}. + +{% tip %} + +**Tip**: On most systems the default private keys (`~/.ssh/id_rsa` and `~/.ssh/identity`) are automatically added to the SSH authentication agent. You shouldn't need to run `ssh-add path/to/key` unless you override the file name when you generate a key. + +{% endtip %} + +#### Getting more details + +You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`: + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> ... +> debug1: identity file /Users/you/.ssh/id_rsa type -1 +> debug1: identity file /Users/you/.ssh/id_rsa-cert type -1 +> debug1: identity file /Users/you/.ssh/id_dsa type -1 +> debug1: identity file /Users/you/.ssh/id_dsa-cert type -1 +> ... +> debug1: Authentications that can continue: publickey +> debug1: Next authentication method: publickey +> debug1: Trying private key: /Users/you/.ssh/id_rsa +> debug1: Trying private key: /Users/you/.ssh/id_dsa +> debug1: No more authentication methods to try. +> Permission denied (publickey). +``` + +En ese ejemplo, no teníamos ninguna llave para que usara SSH. El "-1" al final de las líneas que dicen "identity file" (identidad del archivo) significan que SSH no pudo encontrar un archivo para usar. Luego, en las líneas que indican "Trying private key" (Probando llave privada) también indica que no se encontró ningún archivo. Si existiera un archivo, esas líneas dirían "1" y "Ofreciendo llave privada", respectivamente: + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> ... +> debug1: identity file /Users/you/.ssh/id_rsa type 1 +> ... +> debug1: Authentications that can continue: publickey +> debug1: Next authentication method: publickey +> debug1: Offering RSA public key: /Users/you/.ssh/id_rsa +``` + +### Verifica si la llave pública está asociada a tu cuenta + +Debes indicarle tu llave privada a {% data variables.product.product_name %} para establecer una conexión segura. + +{% mac %} + +1. Abre Terminal. +2. Inicia el agente SSH en segundo plano. + ```shell + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + ``` +3. Busca tu huella digital de llave pública y anótala. {% if currentVersion ver_lt "enterprise-server@3.0" %}Si estàs utilizando OpenSSH 6.7 o superior: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +6. Compare the list of SSH keys with the output from the `ssh-add` command. +![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) + +{% endmac %} + +{% windows %} + +1. Abre la línea de comando. +2. Inicia el agente SSH en segundo plano. + ```shell + $ ssh-agent -s + > Agent pid 59566 + ``` +3. Busca tu huella digital de llave pública y anótala. {% if currentVersion ver_lt "enterprise-server@3.0" %}Si estàs utilizando OpenSSH 6.7 o superior: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +6. Compare the list of SSH keys with the output from the `ssh-add` command. +![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) + +{% endwindows %} + +{% linux %} + +1. Abre Terminal. +2. Inicia el agente SSH en segundo plano. + ```shell + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + ``` +3. Busca tu huella digital de llave pública y anótala. Si estás usando OpenSSH 6.7 o una versión anterior: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +6. Compara la lista de claves SSH con el resultado que arroja el comando `ssh-add`. ![Lista de claves SSH en {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) + +{% endlinux %} + +Si no ves tu llave pública en {% data variables.product.product_name %}, será necesario que [agregues tu clave SSH a {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) para asociarla con tu computadora. + +{% warning %} + +**Advertencia**: Si ves una clave SSH que no te resulta familiar en {% data variables.product.product_name %}, elimínala de inmediato y contáctate con {% data variables.contact.contact_support %} para recibir más ayuda. Una llave pública no identificada puede indicar un posible problema de seguridad. Para obtener más información, consulta "[Revisar tus claves SSH](/articles/reviewing-your-ssh-keys)". + +{% endwarning %} diff --git a/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md b/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md new file mode 100644 index 0000000000000..7a9fec27ec37c --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md @@ -0,0 +1,13 @@ +--- +title: 'Error: Permiso de usuario/repo denegado a otro usuario' +intro: Este error significa que la clave con la que estás subiendo está conectada con una cuenta que no tiene acceso al repositorio. +redirect_from: + - /articles/error-permission-to-user-repo-denied-to-other-user + - /articles/error-permission-to-userrepo-denied-to-other-user +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para resolverlo, el propietario del repositorio (`user`) debe agregar tu cuenta (`other-user`) como colaborador en el repositorio o en un equipo que tenga acceso de escritura al repositorio. diff --git a/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md b/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md new file mode 100644 index 0000000000000..d5289945c5b99 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md @@ -0,0 +1,15 @@ +--- +title: 'Error: Permiso de usuario/repo denegado al usuario/otro repo' +intro: 'Este error significa que la clave con la que estás subiendo se encuentra conectada con otro repositorio como llave de implementación, y no tiene acceso al repositorio al que estás intentado subir.' +redirect_from: + - /articles/error-permission-to-user-repo-denied-to-user-other-repo + - /articles/error-permission-to-userrepo-denied-to-userother-repo +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para resolverlo, elimina la llave de implementación del repositorio y [agrega la clave a tu cuenta](/articles/adding-a-new-ssh-key-to-your-github-account) en lugar de esa llave. + +Si la clave que estás usando está diseñada para funcionar como una llave de implementación, consulta [nuestra guía sobre llaves de implementación](/guides/managing-deploy-keys) para conocer más detalles. diff --git a/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md b/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md new file mode 100644 index 0000000000000..95fb2072c9058 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md @@ -0,0 +1,33 @@ +--- +title: 'Error: ssh-add: opción ilegal -- K' +intro: 'Este error significa que tu versión de `ssh-add` no es compatible con la integración keychain macOS, que te permite almacenar tu contraseña en la keychain.' +redirect_from: + - /articles/error-ssh-add-illegal-option-k + - /articles/error-ssh-add-illegal-option----k +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La opción `-K` es una versión estándar de Apple de `ssh-add`, que almacena la contraseña en tu keychain cuando agregas una clave SSH al ssh-agent. Si has instalado una versión diferente de `ssh-add`, es posible que no sea compatible para `-K`. + +### Resolver el problema + +Para agregar tu llave privada SSH al ssh-agent, puedes especificar la ruta a la versión de Apple de `ssh-add`: + +```shell + $ /usr/bin/ssh-add -K ~/.ssh/id_rsa +``` + +{% note %} + +**Nota:** {% data reusables.ssh.add-ssh-key-to-ssh-agent %} + +{% endnote %} + +### Further reading + +- "[Generar una clave SSH nueva y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" +- [Página de manual de Linux para SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html) +- Para ver la página del manual de Apple para SSH-ADD, ejecuta `man ssh-add` en Terminal. diff --git a/translations/es-ES/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md b/translations/es-ES/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md new file mode 100644 index 0000000000000..9c734395a86b5 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md @@ -0,0 +1,25 @@ +--- +title: 'Error: Problema en el certificado SSL, verificar que el certif. CA esté bien' +intro: 'Este error significa que el certificado raíz de tu CA está desactualizado. Si es necesario actualizar el certificado de raíz de tu CA, no podrás subir ni extraer desde los repositorios de {% data variables.product.product_name %}.' +redirect_from: + - /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok +versions: + free-pro-team: '*' +--- + +Probablemente recibirás el siguiente error: + +```shell +$ git push -u github.main +> fatal: 'github.main' does not appear to be a git repository +> fatal: The remote end hung up unexpectedly + +$ git pull -u github +> error: SSL certificate problem, verify that the CA cert is OK. Details: +> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing https://github.com/tqisjim/google-oauth.git/info/refs +> fatal: HTTP request failed +``` + +"CA" es la forma abreviada de "autoridad de certificado". Las autoridades de certificado son un grupo independiente responsable de manejar las conexiones seguras en la web. Estas autoridades establecen "certificados" digitales, que son una forma de asegurar que las conexiones entre dos máquinas (como tu computadora y GitHub.com) son válidas. Sin un certificado, el riesgo de seguridad entre dos máquinas es mayor. + +Cuando recibes este error, probablemente significa que tu CA está desactualizado y requiere una actualización. Por lo general, al actualizar tu sistema operativo también se actualizar tu CA y se resuelve el problema. diff --git a/translations/es-ES/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md b/translations/es-ES/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md new file mode 100644 index 0000000000000..114e81f2d2ddd --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md @@ -0,0 +1,25 @@ +--- +title: 'Error: Estamos haciendo una auditoría de clave SSH' +intro: Este error significa que la clave SSH que estás usando para realizar una operación Git no está verificada. +redirect_from: + - /articles/error-we-re-doing-an-ssh-key-audit + - /articles/error-were-doing-an-ssh-key-audit +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando uses una clave sin verificar para realizar operaciones Git, se te indicará que debes realizar una auditoría de tus claves SSH. + +```shell +ERROR: We're doing an SSH key audit. +Reason: unverified due to lack of use +Please visit https://github.com/settings/ssh +to approve this key so we know it's safe. +Fingerprint: ab:08:46:83:ff:f6:c4:f8:a9:4e:68:6b:94:17:f2:46 +fatal: could not read from remote repository +``` +### Resolver el problema + +Para resolverlo, necesitas [revisar tus claves SSH](/articles/reviewing-your-ssh-keys) y rechazar o aprobar la clave sin verificar. Al hacer clic en el mensaje de error en el enlace de la URL, irás a la página de Configuración de SSH, donde la clave SSH aparece destacada en la lista de claves SSH. diff --git a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md new file mode 100644 index 0000000000000..aacc4b1e52dd5 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md @@ -0,0 +1,63 @@ +--- +title: Generar una llave GPG nueva +intro: 'Si no tienes una llave GPG existentes, puedes generar una nueva llave GPG para usarla para firmar confirmaciones y etiquetas.' +redirect_from: + - /articles/generating-a-new-gpg-key +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.gpg.supported-gpg-key-algorithms %} + +### Generar una llave GPG + +{% note %} + +**Nota:** Antes de generar una nueva llave GPG, asegúrate de haber verificado tu dirección de correo electrónico. Si no has verificado tu dirección de correo electrónico, no podrás firmar confirmaciones y etiquetas con GPG.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".{% endif %} + +{% endnote %} + +1. Descarga e instala [las herramientas de la línea de comando GPG](https://www.gnupg.org/download/) para tu sistema operativo. Generalmente recomendamos instalar la versión más reciente para tu sistema operativo. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Genera un par de la llave GPG. Ya que existen varias versiones de GPG, puede que necesites consultar la [_página man_](https://en.wikipedia.org/wiki/Man_page) relevante para encontrar el comando adecuado para la generación de llaves. Tu llave debe utilizar RSA. + - Si estás usando una versión 2.1.17 o superior, copia el siguiente texto para generar un par de la llave GPG. + ```shell + $ gpg --full-generate-key + ``` + - Si no estás usando la versión 2.1.17 ni una superior, el comando `gpg --full-generate-key` no funciona. Copia el siguiente texto y continúa con el paso 6. + ```shell + $ gpg --default-new-key-algo rsa4096 --gen-key + ``` +4. Donde se indica, especifica la clase de llave que deseas, o presiona `Enter` para aceptar el `RSA and RSA` predeterminado. +5. Ingresa el tamaño de la llave que deseas. Tu llave debe ser de al menos `4096` bits. +6. Ingresa el periodo de validez que deberá tener la llave. Presiona `Enter` para especificar la selección predeterminada, indicando que la llave no expira. +7. Verifica que tus selecciones sean correctas. +8. Ingresa tu información de ID de usuario. + + {% note %} + + **Nota:** Cuando se te pida que ingreses tu dirección de correo electrónico, asegúrate de ingresar la dirección de correo electrónico verificada para tu cuenta Github. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)" y "[Configurar tu dirección de correo electrónico para confirmaciones](/articles/setting-your-commit-email-address)".{% endif %} + + {% endnote %} + +9. Escribe una contraseña segura. +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +10. Pega el siguiente texto sustituyendo el ID de la llave GPG que deseas usar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: + ```shell + $ gpg --armor --export 3AA5C34371567BD2 + # Prints the GPG key ID, in ASCII armor format + ``` +11. Copia tu llave GPG, comenzando con `-----BEGIN PGP PUBLIC KEY BLOCK-----` y terminando con `-----END PGP PUBLIC KEY BLOCK-----`. +12. [Agrega la llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). + +### Further reading + +* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +* "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" +* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +* "[Firmar confirmaciones](/articles/signing-commits)" +* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md new file mode 100644 index 0000000000000..fe3591f96eebf --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -0,0 +1,158 @@ +--- +title: Generar una nueva clave SSH y agregarla al ssh-agent +intro: 'Una vez que has comprobado las claves SSH existentes, puedes generar una nueva clave SSH para usarla para la autenticación y luego agregarla al ssh-agent.' +redirect_from: + - /articles/adding-a-new-ssh-key-to-the-ssh-agent/ + - /articles/generating-a-new-ssh-key/ + - /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si todavía no tienes una clave SSH, debes [generar una nueva clave SSH](#generating-a-new-ssh-key). Si no estás seguro de si ya tienes una clave SSH, comprueba las [claves existentes](/articles/checking-for-existing-ssh-keys). + +Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, puedes [agregar tu clave al SSH agent](#adding-your-ssh-key-to-the-ssh-agent), que gestiona tus claves SSH y recuerda tu contraseña. + +### Generar una nueva clave SSH + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Pega el siguiente texto, que sustituye tu dirección de correo electrónico en {% data variables.product.product_name %}. + ```shell + $ ssh-keygen -t ed25519 -C "your_email@example.com" + ``` + {% note %} + + **Nota:** Si estás utilizando un sistema tradicional que no es compatible con el algoritmo Ed25519, utiliza: + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + + {% endnote %} + Esto crea una nueva clave ssh usando el correo electrónico proporcionado como etiqueta. + ```shell + > Generating public/private ed25519 key pair. + ``` +3. Cuando se te indique "Ingresar un archivo donde guardar la clave", presiona Intro. Al hacerlo aceptas la ubicación predeterminada del archivo. + + {% mac %} + + ```shell + > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + ``` + + {% endmac %} + + {% windows %} + + ```shell + > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + ``` + + {% endwindows %} + + {% linux %} + + ```shell + > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + ``` + + {% endlinux %} + +4. Donde se indica, escribe una contraseña segura. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)". + ```shell + > Enter passphrase (empty for no passphrase): [Type a passphrase] + > Enter same passphrase again: [Type passphrase again] + ``` + +### Agregar tu clave SSH al ssh-agent + +Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, debes haber [comprobado las claves SSH existentes](/articles/checking-for-existing-ssh-keys) y [generado una nueva clave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). Cuando agregues tu clave SSH al agente, usa el comando macOS `ssh-add` y no una aplicación instalada por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) o alguna otra fuente externa. + +{% mac %} + +1. {% data reusables.command_line.start_ssh_agent %} + +2. Si estás usando macOS Sierra 10.12.2 o una versión posterior, deberás modificar tu archivo `~/.ssh/config` para cargar las claves automáticamente en el ssh-agent y almacenar las contraseñas en tu keychain. + + * Primero, revisa si tu archivo `~/.ssh/config` existe en la ubicación predeterminada. + + ```shell + $ open ~/.ssh/config + > The file /Users/you/.ssh/config does not exist. + ``` + + * Si el archivo no existe, créalo. + + ```shell + $ touch ~/.ssh/config + ``` + + * Abre tu archivo `~/.ssh/config` y luego modifícalo reemplazando `~/.ssh/id_ed25519` si no estás utilizando la ubicación y nombre predeterminados para tu llave de `id_ed25519`. + + ``` + Host * + AddKeysToAgent yes + UseKeychain yes + IdentityFile ~/.ssh/id_ed25519 + ``` + + {% note %} + + **Nota:** Si eliges no agregar una frase de acceso a tu llave, deberás omitir la línea `UseKeychain`. + + {% endnote %} + +3. Agrega tu llave privada SSH al ssh-agent y almacena tu contraseña en tu keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} + ```shell + $ ssh-add -K ~/.ssh/id_ed25519 + ``` + {% note %} + + **Nota:** La opción `-K` es una versión estándar de Apple de `ssh-add`, que almacena la contraseña en tu keychain cuando agregas una clave SSH al ssh-agent. Si eliges no agregar una frase de acceso a tu llave, ejecuta el comando sin la opción `-K`. + + Si no tienes instalada la versión estándar de Apple, puedes recibir un mensaje de error. Para obtener más información sobre cómo resolver este error, consulta "[Error: ssh-add: opción ilegal -- K](/articles/error-ssh-add-illegal-option-k)". + + {% endnote %} + +4. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows_git_bash %} + +1. Verifica que el ssh-agent se esté ejecutando. Puedes utilizar las instrucciones de "Autolanzamiento del ssh-agent" que se encuentran en [Trabajar con frases de acceso de las llaves SSH](/articles/working-with-ssh-key-passphrases)" o iniciarlo manualmente: + ```shell + # start the ssh-agent in the background + $ eval `ssh-agent -s` + > Agent pid 59566 + ``` + +2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} + {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} + +3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) + +{% endwindows %} + +{% linux %} + +1. {% data reusables.command_line.start_ssh_agent %} + +2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} + {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} + +3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) + +{% endlinux %} + +### Further reading + +- "[Acerca de SSH](/articles/about-ssh)" +- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)" +{%- if currentVersion == "free-pro-team@latest" %} +- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +{%- endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md b/translations/es-ES/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md new file mode 100644 index 0000000000000..1a393e3c92b90 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md @@ -0,0 +1,15 @@ +--- +title: Huellas digitales de la clave SSH de GitHub +intro: Se pueden utilizar las huellas digitales de clave pública para validar una conexión a un servidor remoto. +redirect_from: + - /articles/what-are-github-s-ssh-key-fingerprints/ + - /articles/github-s-ssh-key-fingerprints + - /articles/githubs-ssh-key-fingerprints +versions: + free-pro-team: '*' +--- + +Estas son las huellas dactilares de la llave pública de {% data variables.product.prodname_dotcom %}: + +- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) diff --git a/translations/es-ES/content/github/authenticating-to-github/index.md b/translations/es-ES/content/github/authenticating-to-github/index.md new file mode 100644 index 0000000000000..cfeec1a493d04 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/index.md @@ -0,0 +1,89 @@ +--- +title: Autenticar a GitHub +shortTitle: Autenticación +intro: 'Manten tu cuenta y datos seguros con características como {% if currentVersion != "github-ae@latest" %}la autenticación bifactoria, {% endif %}SSH{% if currentVersion != "github-ae@latest" %},{% endif %} y la verificación de firmas de las confirmaciones.' +redirect_from: + - /categories/56/articles/ + - /categories/ssh/ + - /mac-verify-ssh/ + - /ssh-issues/ + - /verify-ssh-redirect/ + - /win-verify-ssh/ + - /categories/92/articles/ + - /categories/gpg/ + - /categories/security/ + - /categories/authenticating-to-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /keeping-your-account-and-data-secure %} + {% link_in_list /about-authentication-to-github %} + {% link_in_list /creating-a-strong-password %} + {% link_in_list /updating-your-github-access-credentials %} + {% link_in_list /creating-a-personal-access-token %} + {% link_in_list /reviewing-your-ssh-keys %} + {% link_in_list /reviewing-your-deploy-keys %} + {% link_in_list /authorizing-oauth-apps %} + {% link_in_list /reviewing-your-authorized-integrations %} + {% link_in_list /connecting-with-third-party-applications %} + {% link_in_list /reviewing-your-authorized-applications-oauth %} + {% link_in_list /reviewing-your-security-log %} + {% link_in_list /removing-sensitive-data-from-a-repository %} + {% link_in_list /about-anonymized-image-urls %} + {% link_in_list /about-githubs-ip-addresses %} + {% link_in_list /githubs-ssh-key-fingerprints %} + {% link_in_list /sudo-mode %} + {% link_in_list /preventing-unauthorized-access %} +{% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} + {% link_in_list /about-two-factor-authentication %} + {% link_in_list /configuring-two-factor-authentication %} + {% link_in_list /configuring-two-factor-authentication-recovery-methods %} + {% link_in_list /accessing-github-using-two-factor-authentication %} + {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} + {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} + {% link_in_list /countries-where-sms-authentication-is-supported %} + {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} +{% topic_link_in_list /authenticating-with-saml-single-sign-on %} + {% link_in_list /about-authentication-with-saml-single-sign-on %} + {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} + {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} + {% link_in_list /viewing-and-managing-your-active-saml-sessions %} +{% topic_link_in_list /connecting-to-github-with-ssh %} + {% link_in_list /about-ssh %} + {% link_in_list /checking-for-existing-ssh-keys %} + {% link_in_list /generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent %} + {% link_in_list /adding-a-new-ssh-key-to-your-github-account %} + {% link_in_list /testing-your-ssh-connection %} + {% link_in_list /working-with-ssh-key-passphrases %} +{% topic_link_in_list /troubleshooting-ssh %} + {% link_in_list /using-ssh-over-the-https-port %} + {% link_in_list /recovering-your-ssh-key-passphrase %} + {% link_in_list /deleted-or-missing-ssh-keys %} + {% link_in_list /error-permission-denied-publickey %} + {% link_in_list /error-bad-file-number %} + {% link_in_list /error-key-already-in-use %} + {% link_in_list /error-permission-to-userrepo-denied-to-other-user %} + {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} + {% link_in_list /error-agent-admitted-failure-to-sign %} + {% link_in_list /error-ssh-add-illegal-option----k %} + {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} + {% link_in_list /error-were-doing-an-ssh-key-audit %} +{% topic_link_in_list /managing-commit-signature-verification %} + {% link_in_list /about-commit-signature-verification %} + {% link_in_list /checking-for-existing-gpg-keys %} + {% link_in_list /generating-a-new-gpg-key %} + {% link_in_list /adding-a-new-gpg-key-to-your-github-account %} + {% link_in_list /telling-git-about-your-signing-key %} + {% link_in_list /associating-an-email-with-your-gpg-key %} + {% link_in_list /signing-commits %} + {% link_in_list /signing-tags %} +{% topic_link_in_list /troubleshooting-commit-signature-verification %} + {% link_in_list /checking-your-commit-and-tag-signature-verification-status %} + {% link_in_list /updating-an-expired-gpg-key %} + {% link_in_list /using-a-verified-email-address-in-your-gpg-key %} diff --git a/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md b/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md new file mode 100644 index 0000000000000..89f58138f67a1 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md @@ -0,0 +1,12 @@ +--- +title: Mantener seguros tu cuenta y tus datos +intro: 'Para proteger tu información personal, debes mantener seguros tanto tu {% data variables.product.product_name %} cuenta como cualquier dato asociado.' +mapTopic: verdadero +redirect_from: + - /articles/keeping-your-account-and-data-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md new file mode 100644 index 0000000000000..fca2a0991363b --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md @@ -0,0 +1,14 @@ +--- +title: Administrar la verificación de firma de confirmación de cambios +intro: 'Puedes firmar tu trabajo localmente utilizando GPG o S/MIME. {% data variables.product.product_name %} verificará estas firmas para que otras personas sepan que tus confirmaciones vienen de una fuente confiable.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} firmará automáticamente las confirmaciones que hagas utilizando la interface web de {% data variables.product.product_name %}.{% endif %}' +redirect_from: + - /articles/generating-a-gpg-key/ + - /articles/signing-commits-with-gpg/ + - /articles/managing-commit-signature-verification +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/preventing-unauthorized-access.md b/translations/es-ES/content/github/authenticating-to-github/preventing-unauthorized-access.md new file mode 100644 index 0000000000000..03800a876e3a5 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/preventing-unauthorized-access.md @@ -0,0 +1,24 @@ +--- +title: Evitar el acceso no autorizado +intro: 'Puedes ser alertado sobre un incidente de seguridad en los medios, como el descubrimiento de [Heartbleed bug](http://heartbleed.com/), o pueden robar tu computadora mientras estás registrado en {% data variables.product.product_location %}. En dichos casos, cambiar tu contraseña previene cualquier acceso futuro no deseado a tu cuenta y a tus proyectos.' +redirect_from: + - /articles/preventing-unauthorized-access +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% data variables.product.product_name %} requiere una contraseña para realizar acciones confidenciales, como agregar nuevas claves SSH, autorizar aplicaciones , o modificar miembros del equipo. + +Después de cambiar tu contraseña, deberías realizar estas acciones para asegurarte que tu cuenta sea segura: + +- [Habilitar una autenticación de dos factores](/articles/about-two-factor-authentication) en tu cuenta para que el acceso requiera más de una contraseña. +- [Revisar tus claves SSH](/articles/reviewing-your-ssh-keys), [llaves de implementación](/articles/reviewing-your-deploy-keys), e [integraciones autorizadas](/articles/reviewing-your-authorized-integrations) y revocar el acceso no autorizado o desconocido en tus configuraciones de SSH y de Aplicaciones. +{% if currentVersion == "free-pro-team@latest" %} +- [Verificar todas tus direcciones de correo electrónico](/articles/verifying-your-email-address). Si un atacante agregó sus direcciones de correo electrónico a tu cuenta, esto puede permitirle forzar un restablecimiento de contraseña no deseado. +{% endif %} +- [Revisar el registro de seguridad de tu cuenta](/github/authenticating-to-github/reviewing-your-security-log). Esto brinda un resumen de varias configuraciones realizadas a tus repositorios. Por ejemplo, puedes asegurarte que no se convirtieron repositorios privados en públicos, o que no se transfirieron repositorios. +- [Revisa los webhooks](/articles/creating-webhooks) en tus repositorios. Los webhooks podrían permitir que un atacante intercepte cargas que hagas a tu repositorio. +- [Asegurarte que no se hayan creado nuevas llaves de implementación](/guides/managing-deploy-keys/#deploy-keys). Esto podría permitir que servidores externos accedan a tus proyectos. +- Revisar las confirmaciones de cambios recientes realizadas a tus repositorios. +- Revisar la lista de colaboradores de cada repositorio. diff --git a/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md new file mode 100644 index 0000000000000..ae459bfb7f7c4 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -0,0 +1,93 @@ +--- +title: Recuperar tu cuenta si pierdes tus credenciales 2FA +intro: 'Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes utilizar tus códigos de recuperación, o cualquier otra opción de recuperación, para recuperar el acceso a tu cuenta.' +redirect_from: + - /articles/recovering-your-account-if-you-lost-your-2fa-credentials/ + - /articles/authenticating-with-an-account-recovery-token/ + - /articles/recovering-your-account-if-you-lose-your-2fa-credentials +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Advertencia**: {% data reusables.two_fa.support-may-not-help %} + +{% endwarning %} + +{% endif %} + +### Utilizar un código de recuperación de autenticación de dos factores + +Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)." + +{% data reusables.two_fa.username-password %}{% if currentVersion == "free-pro-team@latest" %} +2. Da clic en **Ingresar un código de recuperación de dos factores** debajo de "¿Tienes Problemas?". ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} +2. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} +3. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Autenticar con un número de reserva + +Si pierdes el acceso a tu app TOTP principal o número de teléfono, puedes proporcionar un código de autenticación de dos factores enviado a tu número de reserva para recuperar automáticamente el acceso a tu cuenta. +{% endif %} + +### Autenticar con una clave de seguridad + +Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". + +{% if currentVersion == "free-pro-team@latest" %} +### Autentificarse con un dispositivo verificado, token SSH, o token de acceso personal +Si pierdes el acceso a tus credenciales de autenticación de dos factores y no tienes tus códigos de recuperación para atutenticación de dos factores, se puede enviar una contraseña de única ocasión a tu dirección de correo electrónico verificada para comenzar el proceso de verificación y recobrar el acceso a tu cuenta. + +{% note %} + +**Nota**: Por razones de seguridad, recobrar el acceso a tu cuenta autenticándose con una contraseña de una sola ocasión puede demorar de 3 a 5 días hábiles. Las solicitudes adicionales emitidas durante este periodo no se revisarán. + +{% endnote %} + +Puedes utilizar tus credenciales de autenticación de dos factores para recobrar el acceso a tu cuenta en cualquier momento durante el periodo de espera de 3 a 5 días. + +{% data reusables.two_fa.username-password %} +2. Da clic en **¿No puedes acceder a tu dispositivo de dos factores o a tus códigos de recuperación válidos?** debajo de "¿Tienes Problemas ![Enlace si no tienes tu dispositivo de 2fa o códigos de recuperación](/assets/images/help/2fa/no-access-link.png) +3. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. ![Botón de restablecimiento de configuración de autenticación](/assets/images/help/2fa/reset-auth-settings.png) +4. Da clic en **Enviar contraseña de una sola vez** para enviarla a todas las direcciones de correo electrónico asociadas con tu cuenta. ![Botón para enviar contraseña de una sola vez](/assets/images/help/2fa/send-one-time-password.png) +5. Teclea la contraseña recibida en el correo electrónico de recuperación debajo de "Contraseña de una sola vez"{% data variables.product.prodname_dotcom %}. ![Campo para contraseña de una sola vez](/assets/images/help/2fa/one-time-password-field.png) +6. Da clic en **Verificar dirección de correo electrónico**. +7. Escoge un factor de verificación alterno. + - Si has utilizado tu dispositivo actual para ingresar en esta cuenta antes y quieres utilizarlo para verificación, da clic en **Verificar este dispositivo**. + - Si has configurado una llave SSH previamente en esta cuenta y quieres utilizarla para verificación, da clic en **Llave SSH**. + - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. ![Botones de verificación alternativa](/assets/images/help/2fa/alt-verifications.png) +8. Un miembro de {% data variables.contact.github_support %} revisará tu solicitud y te enviará un mensaje de correo electrónico dentro de los siguientes 3 a 5 días. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional. + +### Autenticar con un token de recuperación de cuenta + +Si pierdes el acceso a tus métodos de autenticación de dos factores para tu cuenta {% data variables.product.product_name %}, puedes recuperar tu token de recuperación de cuenta desde un proveedor socio de recuperación y solicitarle a Soporte de {% data variables.product.prodname_dotcom %} que lo revise. + +Si no tienes acceso a tus métodos de autenticación de dos factores o a tus códigos de recuperación y has almacenado un token de recuperación de cuenta con Facebook utilizando Recuperar cuentas en otro lugar, puedes utilizar tu token para recuperar el acceso a tu cuenta. + +Si te es imposible recuperar el acceso a tu cuenta, genera una contraseña de una sola vez para recuperarlo. Para obtener más información, consulta "[Autenticarse con un dispositivo verificado, token, ssh, o token de acceso personal](#authenticating-with-a-verified-device-ssh-token-or-personal-access-token)". + +{% warning %} + +**Advertencias:** +- Antes de recuperar un token de recuperación de cuenta, deberías tratar de utilizar tus [códigos de autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication) o tus códigos de recuperación de autenticación de dos factores para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". + +{% endwarning %} + +1. En Facebook, desplázate hasta tus [Configuraciones de seguridad](https://www.facebook.com/settings?tab=security), después haz clic en **Recover Accounts Elsewhere (Recuperar cuentas en otro lugar)**. ![Página de configuraciones de seguridad de Facebook con enlace Recuperar cuentas en otro lugar](/assets/images/help/settings/security-facebook-security-settings-page.png) +2. Haz clic en el token de recuperación asociado con tu cuenta {% data variables.product.product_name %}. ![Lista de tokens de recuperación almacenados en Facebook](/assets/images/help/settings/security-github-rae-token-on-facebook.png) +3. Para rescatar tu token de recuperación de cuenta, haz clic en **Recover This Account (Recuperar esta cuenta)**. Se abrirá una nueva ventana, que te llevará de vuelta a {% data variables.product.product_name %}. ![Casilla modal con información acerca de tu token de recuperación y botón Recuperar esta cuenta](/assets/images/help/settings/security-recover-account-facebook.png) +4. Contacto +{% data variables.contact.contact_support %} para hacerles saber que tu token de recuperación de cuenta está listo para revisión. +{% endif %} + +### Further reading + +- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" +- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" +- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md new file mode 100644 index 0000000000000..733a0f3142a65 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md @@ -0,0 +1,37 @@ +--- +title: Recuperar tu contraseña de clave SSH +intro: 'Si perdiste tu contraseña de clave SSH, según el sistema operativo que utilices, puedes recuperarla o generar una nueva contraseña de clave SSH.' +redirect_from: + - /articles/how-do-i-recover-my-passphrase/ + - /articles/how-do-i-recover-my-ssh-key-passphrase/ + - /articles/recovering-your-ssh-key-passphrase +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% mac %} + +Si [configuraste tu contraseña de clave SSH con OS X Keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), quizás puedas recuperarla. + +1. En Finder (Buscador), busca la aplicación **Keychain Access** (Acceso keychain). ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png) +2. En Keychain Access (Acceso keychain), busca **SSH**. +3. Haz doble clic en la entrada de tu clave SSH para abrir un nuevo cuadro de diálogo. +4. En la esquina inferior izquierda, selecciona **Show password** (Mostrar contraseña). ![Diálogo Keychain access (Acceso keychain)](/assets/images/help/setup/keychain_show_password_dialog.png) +5. Se te solicitará tu contraseña administrativa. Escríbela en el cuadro de diálogo "Keychain Access" (Acceso keychain). +6. Se revelará tu contraseña. + +{% endmac %} + +{% windows %} + +Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/articles/changing-a-remote-s-url/#switching-remote-urls-from-ssh-to-https) para poder utilizar tu contraseña de GitHub en su lugar. + +{% endwindows %} + +{% linux %} + +Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls) para poder utilizar tu contraseña de GitHub en su lugar. + +{% endlinux %} diff --git a/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md new file mode 100644 index 0000000000000..61db8e71f4bd2 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -0,0 +1,156 @@ +--- +title: Eliminar datos confidenciales de un repositorio +intro: 'Si confirmas datos confidenciales, como una contraseña o clave SSH en un repositorio de Git, puedes eliminarlos del historial. Para eliminar por completo los archivos no deseados del historial de un repositorio, puedes utilizar el comando `git filter-branch` o la herramienta de código abierto BFG Repo-Cleaner.' +redirect_from: + - /remove-sensitive-data/ + - /removing-sensitive-data/ + - /articles/remove-sensitive-data/ + - /articles/removing-sensitive-data-from-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El comando `git filter-branch` y el BFG Repo-Cleaner reescriben el historial de tu repositorio, lo cual cambia las SHA de las confirmaciones existentes que modificas y cualquier confirmación de las dependencias. Las SHA de confirmación modificadas pueden afectar las solicitudes de extracción abiertas de tu repositorio. Recomendamos fusionar o cerrar todas las solicitudes de extracción abiertas antes de eliminar archivos de tu repositorio. + +Puedes eliminar el archivo desde la última confirmación con `git rm`. Para obtener información acerca de eliminar un archivo que se agregó con la última confirmación, consulta "[Eliminar archivos del historial de un repositorio](/articles/removing-files-from-a-repository-s-history)". + +{% warning %} + +**Advertencia: Una vez que hayas subido una confirmación en {% data variables.product.product_name %}, debes tener en cuenta cualquier dato que contenga que pueda ser riesgoso.** Si confirmaste una contraseña, ¡cámbiala! Si confirmaste una clave, genera una nueva. + +Este artículo te explica cómo hacer confirmaciones con datos confidenciales inaccesibles desde cualquier rama o etiqueta en tu {% data variables.product.product_name %} repositorio. Sin embargo, es importante tener en cuenta que esas confirmaciones pueden seguir siendo accesibles desde cualquier clon o bifurcación de tu repositorio, directamente por medio de sus hashes de SHA-1 en las visualizaciones cacheadas en {% data variables.product.product_name %} y a través de cualquier solicitud de extracción que las referencie. No puedes hacer nada con los clones o bifurcaciones existentes de tu repositorio, pero puedes eliminar de manera permanente las visualizaciones cacheadas y las referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %} contactándote con {% data variables.contact.contact_support %}. + +{% endwarning %} + +### Purgar un archivo del historial de tu repositorio + +#### Usar el BFG + +El [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) es una herramienta construida y mantenida por la comunidad de código abierto. Proporciona una alternativa más rápida y simple que `git filter-branch` para eliminar datos no deseados. Por ejemplo, para eliminar tu archivo con datos confidenciales y dejar intacta tu última confirmación, ejecuta lo siguiente: + +```shell +$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA +``` + +Para reemplazar todo el texto detallado en `passwords.txt` donde sea que se encuentre en el historial de tu repositorio, ejecuta lo siguiente: + +```shell +$ bfg --replace-text passwords.txt +``` + +Después de que se eliminan los datos sensibles, debes subir forzadamente tus cambios a {% data variables.product.product_name %}. + +```shell +$ git push --force +``` + +Consulta los documentos de [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga. + +#### Utilizar filter-branch + +{% warning %} + +**Advertencia:** Si ejecutas `git filter-branch` después de acumular cambios, no podrás recuperar tus cambios con otros comandos de acumulación. Antes de ejecutar `git filter-branch`, recomendamos anular la acumulación de cualquier cambio que hayas hecho. Para dejar de acumular el último conjunto de cambios que hayas acumulado, ejecuta `git stash show -p | git apply -R`. Para obtener más información, consulta [Herramientas de Git Acumulación](https://git-scm.com/book/en/v1/Git-Tools-Stashing). + +{% endwarning %} + +Para ilustrar cómo funciona `git filter-branch`, te mostraremos cómo eliminar tu archivo con datos confidenciales del historial de tu repositorio y agregarlo a `.gitignore` para asegurar que no se reconfirmó de manera accidental. + +1. Si aún no tienes una copia local de tu repositorio con datos confidenciales en el historial, [clona el repositorio](/articles/cloning-a-repository/) en tu computadora local. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY + > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ + > remote: Counting objects: 1301, done. + > remote: Compressing objects: 100% (769/769), done. + > remote: Total 1301 (delta 724), reused 910 (delta 522) + > Receiving objects: 100% (1301/1301), 164.39 KiB, done. + > Resolving deltas: 100% (724/724), done. + ``` +2. Navega hacia el directorio de trabajo del repositorio. + ```shell + $ cd YOUR-REPOSITORY + ``` +3. Ejecuta el siguiente comando, reemplazando `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` por la **ruta al archivo que quieres eliminar, no solo con su nombre de archivo**. Estos argumentos harán lo siguiente: + - Forzar a Git a que procese, pero no revise, todo el historial de cada rama y etiqueta + - Eliminar el archivo especificado y cualquier confirmación vacía generada como resultado + - **Sobrescribir tus etiquetas existentes** + ```shell + $ git filter-branch --force --index-filter \ + "git rm --cached --ignore-unmatch PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA" \ + --prune-empty --tag-name-filter cat -- --all + > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (266/266) + > Ref 'refs/heads/main' was rewritten + ``` + + {% note %} + + **Nota:** Si se utilizó el archivo con datos confidenciales para que existiera en cualquier otra ruta (porque se movió o se renombró), debes ejecutar este comando en esas rutas también. + + {% endnote %} + +4. Agrega tu archivo con datos confidenciales a `.gitignore` para asegurar que no lo volviste a confirmar por accidente. + + ```shell + $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore + $ git add .gitignore + $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" + > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore + > 1 files changed, 1 insertions(+), 0 deletions(-) + ``` +5. Comprueba que hayas eliminado todo lo que querías del historial de tu repositorio y que todas tus ramas estén revisadas. +6. Una vez que estés conforme con el estado de tu repositorio, realiza un empuje forzado de tus cambios locales para sobrescribir tu {% data variables.product.product_name %} repositorio y todas las ramas que hayas subido: + ```shell + $ git push origin --force --all + > Counting objects: 1074, done. + > Delta compression using 2 threads. + > Compressing objects: 100% (677/677), done. + > Writing objects: 100% (1058/1058), 148.85 KiB, done. + > Total 1058 (delta 590), reused 602 (delta 378) + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > + 48dc599...051452f main -> main (forced update) + ``` +7. Para eliminar el archivo confidencial de [tus lanzamientos etiquetados](/articles/about-releases), también deberás realizar un empuje forzado contra tus etiquetas de Git: + ```shell + $ git push origin --force --tags + > Counting objects: 321, done. + > Delta compression using up to 4 threads. + > Compressing objects: 100% (166/166), done. + > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done. + > Total 321 (delta 124), reused 269 (delta 108) + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > + 48dc599...051452f main -> main (forced update) + ``` +8. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. +9. Pídeles a tus colaboradores que [rebasen](https://git-scm.com/book/en/Git-Branching-Rebasing), *no* fusionen, cualquier rama que hayan creado fuera del historial de tu repositorio antiguo (contaminado). Una confirmación de fusión podría volver a introducir algo o todo el historial contaminado sobre el que acabas de tomarte el trabajo de purgar. +10. Después de que haya transcurrido un tiempo y estés seguro de que `git filter-branch` no tuvo efectos secundarios inesperados, puedes forzar a todos los objetos de tu repositorio local a desreferenciarse y recolectar la basura con los siguientes comandos (usando Git 1.8.5 o posterior): + ```shell + $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin + $ git reflog expire --expire=now --all + $ git gc --prune=now + > Counting objects: 2437, done. + > Delta compression using up to 4 threads. + > Compressing objects: 100% (1378/1378), done. + > Writing objects: 100% (2437/2437), done. + > Total 2437 (delta 1461), reused 1802 (delta 1048) + ``` + {% note %} + + **Nota:** También puedes lograrlo subiendo tu historial filtrado a un repositorio nuevo o vacío para después hacer un nuevo clon desde {% data variables.product.product_name %}. + + {% endnote %} + +### Evitar confirmaciones accidentales en el futuro + +Existen algunos trucos sencillos para evitar confirmar cosas que no quieres confirmar: + +- Utiliza un programa visual como [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) o [gitk](https://git-scm.com/docs/gitk) para confirmar los cambios. Los programas visuales suelen hacer que sea más sencillo ver exactamente qué archivos se agregarán, eliminarán y modificarán con cada confirmación. +- Evita los comandos para atrapar todo `git add .` y `git commit -a` de la línea de comando —en su lugar, utiliza `git add filename` y `git rm filename` para ordenar por etapas los archivos. +- Utiliza `git add --interactive` para revisar por separado y preparar los cambios de cada archivo. +- Utiliza `git diff --cached` para revisar los cambios que hayas preparado para la confirmación. Esta es la diferencia exacta que `git commit` generará siempre que no utilices la marca `-a`. + +### Further reading + +- [man page de `git filter-branch`](https://git-scm.com/docs/git-filter-branch) +- [Pro Git: Herramientas de Git - Rescribir historial](https://git-scm.com/book/en/Git-Tools-Rewriting-History) diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md new file mode 100644 index 0000000000000..bdefee6d989d3 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md @@ -0,0 +1,20 @@ +--- +title: Revisar tus aplicaciones autorizadas (OAuth) +intro: 'Debes revisar tus aplicaciones autorizadas para comprobar que no se autoricen aplicaciones nuevas con permisos expansivos, como aquellas que tienen acceso a tus repositorios privados.' +redirect_from: + - /articles/reviewing-your-authorized-applications-oauth +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.access_applications %} +{% data reusables.user_settings.access_authorized_oauth_apps %} +{% data reusables.user_settings.review-oauth-apps %} + +### Further reading +{% if currentVersion == "free-pro-team@latest" %} +- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} +- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md new file mode 100644 index 0000000000000..a0260c75dc5b4 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md @@ -0,0 +1,29 @@ +--- +title: Revisar tus integraciones autorizadas +intro: Puedes revisar tus integraciones autorizadas para auditar el acceso que cada integración tiene a tu cuenta y a tus datos. +redirect_from: + - /articles/reviewing-your-authorized-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Revisar tus {% data variables.product.prodname_oauth_app %}s autorizadas + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.access_applications %} +{% data reusables.user_settings.access_authorized_oauth_apps %} +{% data reusables.user_settings.review-oauth-apps %} + +### Revisar tus {% data variables.product.prodname_github_app %}s autorizadas + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.access_applications %} +3. Haz clic en la pestaña **Authorized {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s autorizadas). ![Pestaña de {% data variables.product.prodname_github_app %}s autorizadas](/assets/images/help/settings/settings-authorized-github-apps-tab.png) +3. Revisa las {% data variables.product.prodname_github_app %}s que tienen acceso a tu cuenta. Para las que no reconozcas o las que estén desactualizadas, haz clic en **Revoke** (Revocar). Para revocar todas las {% data variables.product.prodname_github_app %}s, haz clic en **Revoke all** (Revocar todo). ![Lista de {% data variables.product.prodname_github_app %} autorizadas](/assets/images/help/settings/revoke-github-app.png) + +### Further reading +{% if currentVersion == "free-pro-team@latest" %} +- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} +- "[Revisar tus aplicaciones autorizadas (OAuth)](/articles/reviewing-your-authorized-applications-oauth)" diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-deploy-keys.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-deploy-keys.md new file mode 100644 index 0000000000000..56a7ee2f12d41 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-deploy-keys.md @@ -0,0 +1,17 @@ +--- +title: Revisar tus llaves de implementación +intro: Debes revisar tus llaves de implementación para garantizar que no haya ninguna llave sin autorización (o posiblemente comprometida). También puedes aprobar llaves de implementación existentes que sean válidas. +redirect_from: + - /articles/reviewing-your-deploy-keys +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En la barra lateral izquierda, haz clic en **Deploy keys** (Llaves de implementación). ![Parámetro de llaves de implementación](/assets/images/help/settings/settings-sidebar-deploy-keys.png) +4. En la página de Llaves de implementación, anota las llaves de implementación asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay llaves de implementación válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de llaves de implementación](/assets/images/help/settings/settings-deploy-key-review.png) + +Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)". diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md new file mode 100644 index 0000000000000..a56bfe4dbba85 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -0,0 +1,258 @@ +--- +title: Revisar tu registro de seguridad +intro: Puedes revisar el registro de seguridad de tu cuenta de usuario para entender mejor las acciones que has realizado y las que otros han realizado, las cuales te involucran. +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-your-security-log +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acceder a tu registro de seguridad + +La bitácora de seguridad lista todas las acciones realizadas dentro de los últimos 90 días{% if currentVersion ver_lt "enterprise-server@2.20" %}, hasta 50 de ellas{% endif %}. + +{% data reusables.user_settings.access_settings %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +2. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. ![Pestaña de registro de seguridad](/assets/images/help/settings/audit-log-tab.png) +{% else %} +{% data reusables.user_settings.security %} +3. En "Security history" (Historial de seguridad) se muestra tu registro. ![Registro de seguridad](/assets/images/help/settings/user_security_log.png) +4. Haz clic en la entrada para ver más información acerca del evento. ![Registro de seguridad](/assets/images/help/settings/user_security_history_action.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +### Buscar tu registro de seguridad + +{% data reusables.audit_log.audit-log-search %} + +#### Búsqueda basada en la acción realizada +{% else %} +### Entender los eventos en tu registro de seguridad +{% endif %} + +Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las acciones se agrupan en las siguientes categorías: + +| Nombre de la categoría | Descripción | +| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`account_recovery_token`](#account_recovery_token-category-actions) | Contiene todas las actividades relacionadas con [agregar un token de recuperación](/articles/configuring-two-factor-authentication-recovery-methods). | +| [`billing`](#billing-category-actions) | Contiene todas las actividades relacionadas con tu información de facturación. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}. | +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas con el listado de aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %} +| [`oauth_access`](#oauth_access-category-actions) | Contiene todas las actividades relacionadas con las [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) que hayas conectado con.{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con el pago de tu suscripción de {% data variables.product.prodname_dotcom %}.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contiene todas las actividades relacionadas con tu foto de perfil. | +| [`project`](#project-category-actions) | Contiene todas las actividades relacionadas con los tableros de proyecto. | +| [`public_key`](#public_key-category-actions) | Contiene todas las actividades relacionadas con [tus claves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account). | +| [`repo`](#repo-category-actions) | Contiene todas las actividades relacionadas con los repositorios que te pertenecen.{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contiene todos los eventos relacionados con {% data variables.product.prodname_sponsors %} y los botones de patrocinio (consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" y "[Mostrar el botón de patrocinio en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| [`team`](#team-category-actions) | Contiene todas las actividades relacionadas con los equipos de los cuales formas parte.{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contiene todas las actividades relacionadas con la [autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} +| [`user`](#user-category-actions) | Contiene todas las actividades relacionadas con tu cuenta. | + +{% if currentVersion == "free-pro-team@latest" %} + +### Exportar tu registro de seguridad + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} + +{% endif %} + +### Acciones de la bitácora de seguridad + +Un resumen de algunas de las acciones más frecuentes que se registran como eventos en la bitácora de seguridad. + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `account_recovery_token` + +| Acción | Descripción | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `confirm (confirmar)` | Se activa cuando almacenas [con éxito un nuevo token con un proveedor de recuperación](/articles/configuring-two-factor-authentication-recovery-methods). | +| `recover (recuperar)` | Se activa cuando canjeas [con éxito un token de recuperación de cuenta](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). | +| `recover_error (error de recuperación)` | Se activa cuando se utiliza un token, pero {% data variables.product.prodname_dotcom %} no está disponible para validarlo. | + +#### acciones de la categoría `billing` + +| Acción | Descripción | +| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando [cambias la manera de pagar](/articles/adding-or-editing-a-payment-method) para {% data variables.product.prodname_dotcom %}. | +| `change_email (cambiar correo electrónico)` | Se activa cuando [cambias tu dirección de correo electrónico](/articles/changing-your-primary-email-address). | + +#### `codespaces` category actions + +| Acción | Descripción | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + +#### acciones de la categoría `marketplace_agreement_signature` + +| Acción | Descripción | +| ---------------- | ----------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. | + +#### acciones de la categoría `marketplace_listing` + +| Acción | Descripción | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | +| `approve` | Se activa cuando se aprueba tu lista para ser incluida en {% data variables.product.prodname_marketplace %}. | +| `create (crear)` | Se activa cuando creas una lista para tu app en {% data variables.product.prodname_marketplace %}. | +| `delist (quitar de la lista)` | Se activa cuando se elimina tu lista de {% data variables.product.prodname_marketplace %}. | +| `redraft` | Se activa cuando tu lista se vuelve a colocar en estado de borrador. | +| `reject (rechazar)` | Se activa cuando no se acepta la inclusión de tu lista en {% data variables.product.prodname_marketplace %}. | + +{% endif %} + +#### acciones de la categoría `oauth_access` + +| Acción | Descripción | +| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create (crear)` | Se activa cuando [otorgas acceso a una {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). | +| `destroy (destruir)` | Se activa cuando [revocas el acceso de una {% data variables.product.prodname_oauth_app %} a tu cuenta](/articles/reviewing-your-authorized-integrations). | + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `payment_method` + +| Acción | Descripción | +| ------------------ | ------------------------------------------------------------------------------------------------------------- | +| `clear (eliminar)` | Se activa cuando se elimina [un método de pago](/articles/removing-a-payment-method) archivado. | +| `create (crear)` | Se activa cuando se agrega un método de pago nuevo, como una tarjeta de crédito nueva o una cuenta de PayPal. | +| `update` | Se activa cuando se actualiza un método de pago existente. | + +{% endif %} + +#### acciones de la categoría `profile_picture` + +| Acción | Descripción | +| -------- | ------------------------------------------------------------------------------------------------------ | +| `update` | Se activa cuando [estableces o actualizas tu foto de perfil](/articles/setting-your-profile-picture/). | + +#### acciones de la categoría `project` + +| Acción | Descripción | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | +| `access (acceder)` | Se activa cuando se modifica la visibilidad de un tablero de proyecto. | +| `create (crear)` | Se activa cuando se crear un tablero de proyecto. | +| `rename (renombrar)` | Se activa cuando se renombra un tablero de proyecto. | +| `update` | Se activa cuando se actualiza un tablero de proyecto. | +| `eliminar` | Se activa cuando se elimina un tablero de proyecto. | +| `enlace` | Se activa cuando un repositorio se vincula a un tablero de proyecto. | +| `unlink (desvincular)` | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto. | +| `update_user_permission` | Se activa cuando se agrega o elimina un colaborador externo a un tablero de proyecto o cuando se cambia su nivel de permiso. | + +#### acciones de la categoría `public_key` + +| Acción | Descripción | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando [agregas una clave SSH pública a tu {% data variables.product.product_name %} cuenta](/articles/adding-a-new-ssh-key-to-your-github-account). | +| `eliminar` | Se activa cuando [eliminas una clave SSH pública para tu {% data variables.product.product_name %} cuenta](/articles/reviewing-your-ssh-keys). | + +#### acciones de la categoría `repo` + +| Acción | Descripción | +| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access (acceder)` | Se activa cuando un repositorio que te pertenece se [cambia de "privado" a "público"](/articles/making-a-private-repository-public) (o viceversa). | +| `add_member (agregar miembro)` | Se activa cuando un usuario de {% data variables.product.product_name %} recibe [una invitación para tener acceso de colaboración](/articles/inviting-collaborators-to-a-personal-repository){% else %}[un permiso de acceso para colaborar](/articles/inviting-collaborators-to-a-personal-repository){% endif %} en un repositorio. | +| `add_topic (agregar tema)` | Se activa cuando un propietario del repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio. | +| `archived (archivado)` | Se activa cuando un propietario del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)` | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)` | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)` | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create (crear)` | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository). | +| `destroy (destruir)` | Se activa cuando [se borra un repositorio](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `disable` | Se activa cuando un repositorio se inhabilita (por ejemplo, por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable` | Se activa cuando se vuelve a habilitar un repositorio.{% endif %} +| `remove_member (eliminar miembro)` | Se activa cuando se elimina {% data variables.product.product_name %} un usuario [de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | +| `remove_topic (eliminar tema)` | Se activa cuando un propietario del repositorio elimina un tema de un repositorio. | +| `rename (renombrar)` | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository). | +| `transfer` | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository). | +| `transfer_start (comienzo de transferencia)` | Se activa cuando está por ocurrir una transferencia de repositorio. | +| `unarchived (desarchivado)` | Se activa cuando un administrador del repositorio desarchiva un repositorio. | + +{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `sponsors` + +| Acción | Descripción | +| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo_funding_link_button_toggle (alternar botón de enlace al financiamiento del repositorio)` | Se activa cuando habilitas o inhabilitas un botón de patrocinador en tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)` | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)` | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)` | Se activa cuando patrocinas una cuenta (consulta "[Patrocinar a un contribuyente de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado (consulta "[Administrar tu patrocinio](/articles/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)` | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve (aprobación de programador patrocinado)` | Desencadenado cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configuración {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_create (creación de programador patrocinado)` | Desencadenado cuando se crea tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Desencadenado cuando editas el perfil de tu desarrollador patrocinado (consulta "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Desencadenado cuando emites tu aplicación para {% data variables.product.prodname_sponsors %} para su aprobación (consulta "[Configuración {% data variables.product.prodname_sponsors %} pára tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta "[Cambiar tus niveles de patrocinio](/articles/changing-your-sponsorship-tiers)") | +| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)` | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta "[Contactar a tus patrocinadores](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Desencadenado cuando se te invita a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `waitlist_join (incorporación a la lista de espera)` | Desencadenado cuando te unes a la lista de espera para convertirte en un desarrollador patrocinado (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `successor_invitation` + +| Acción | Descripción | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `accept` | Se activa cuando aceptas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `cancel` | Se activa cuando cancelas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `create (crear)` | Se activa cuando creas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `decline` | Se activa cuando rechazas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| `revoke` | Se activa cuando retiras una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/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" %} + +#### acciones de la categoría `team` + +| Acción | Descripción | +| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member (agregar miembro)` | Se activa cuando un miembro de una organización a la que perteneces te [agrega a un equipo](/articles/adding-organization-members-to-a-team). | +| `add_repository (agregar repositorio)` | Se activa cuando se le otorga el control de un repositorio a un equipo del que eres miembro. | +| `create (crear)` | Se activa cuando se crea un equipo nuevo en una organización a la que perteneces. | +| `destroy (destruir)` | Se activa cuando un equipo del que eres miembro se elimina de la organización. | +| `remove_member (eliminar miembro)` | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team) del que eres miembro. | +| `remove_repository (eliminar repositorio)` | Se activa cuando un repositorio deja de estar bajo el control de un equipo. | + +{% endif %} + +{% if currentVersion != "github-ae@latest" %} +#### acciones de la categoría `two_factor_authentication` + +| Acción | Descripción | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `enabled (habilitado)` | Se activa cuando se habilita la [autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa). | +| `disabled (inhabilitado)` | Se activa cuando se inhabilita la autenticación de dos factores. | +{% endif %} + +#### acciones de la categoría `user` + +| Acción | Descripción | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email (agregar correo electrónico)` | 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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} +| `create (crear)` | Se activa cuando creas una cuenta de usuario nueva.{% if currentVersion != "github-ae@latest" %} +| `change_password (cambiar contraseña)` | Se activa cuando cambias tu contraseña. | +| `forgot_password (olvidé la contraseña)` | Se activa cuando pides [un restablecimiento de contraseña](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count (ocultar conteo de contribuciones privadas)` | Se activa cuando [ocultas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | +| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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 %} + +#### acciones de la categoría `user_status` + +| Acción | Descripción | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `update` | Se activa cuando estableces o cambias el estado en tu perfil. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". | +| `destroy (destruir)` | Se activa cuando eliminas el estado de tu perfil. | + diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-ssh-keys.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-ssh-keys.md new file mode 100644 index 0000000000000..e4689ac3b9ac8 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-ssh-keys.md @@ -0,0 +1,133 @@ +--- +title: Revisar tus claves SSH +intro: 'Para mantener seguras tus credenciales, debes auditar de manera regular tus claves SSH, llaves de implementación y revisar las aplicaciones autorizadas que acceden a tu {% data variables.product.product_name %} cuenta.' +redirect_from: + - /articles/keeping-your-application-access-tokens-safe/ + - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/ + - /articles/reviewing-your-ssh-keys +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes eliminar las claves SSH no autorizadas (o posiblemente comprometidas) para garantizar que un atacante no tenga más acceso a tus repositorios. También puedes aprobar llaves SSH existentes que sean válidas. + +{% mac %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay claves SSH válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de claves SSH](/assets/images/help/settings/settings-ssh-key-review.png) + + {% tip %} + + **Nota:** Si estás auditando tus claves SSH por una operación de Git fallida, la clave no verificada que provocó el [error de auditoría de clave SSH](/articles/error-we-re-doing-an-ssh-key-audit) se resaltará en la lista de claves SSH. + + {% endtip %} + +4. Abre Terminal. + +5. {% data reusables.command_line.start_ssh_agent %} + +6. Busca tu huella digital de llave pública y anótala. {% if currentVersion ver_lt "enterprise-server@3.0" %}Si estàs utilizando OpenSSH 6.7 o superior: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. + +{% endmac %} + +{% windows %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) + + {% tip %} + + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. + + {% endtip %} + +4. Abre Git Bash. Si estás usando Git Shell, que se incluye en {% data variables.product.prodname_desktop %}, abre Git Shell y avanza hasta el paso 6. + +5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} + + {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} + +6. Busca tu huella digital de llave pública y anótala. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + {% else %} + ```shell + $ ssh-add -l -E sha256 + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + ```{% endif %} + +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. + +{% endwindows %} + +{% linux %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.ssh %} +3. En la página de Parámetros SSH, anota las claves SSH asociadas a tu cuenta. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) + + {% tip %} + + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. + + {% endtip %} + +4. Abre Terminal. + +5. {% data reusables.command_line.start_ssh_agent %} + +6. Busca tu huella digital de llave pública y anótala. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: + ```shell + $ ssh-add -l + > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + + Si estás usando OpenSSH 6.8 o una versión más reciente: + ```shell + $ ssh-add -l -E md5 + > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) + ``` + {% else %} +```shell $ ssh-add -l -E sha256 +> 2048 *SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ* /Users/*USERNAME*/.ssh/id_rsa (RSA) ```{% endif %} + +7. Las claves SSH en {% data variables.product.product_name %} *deben* coincidir con las mismas calves en tu computadora. + +{% endlinux %} + +{% warning %} + +**Advertencia**: Si ves una clave SSH que no te resulta familiar en {% data variables.product.product_name %}, elimínala de inmediato y contáctate con {% data variables.contact.contact_support %} para recibir más ayuda. Una llave pública no identificada puede indicar un posible problema de seguridad. + +{% endwarning %} diff --git a/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md b/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md new file mode 100644 index 0000000000000..90ba94465f064 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md @@ -0,0 +1,13 @@ +--- +title: Asegurar tu cuenta con autenticación de dos factores (2FA) +intro: 'Puedes configurar tu cuenta {% data variables.product.product_name %} para requerir un código de autenticación además de tu contraseña cuando te registras.' +redirect_from: + - /categories/84/articles/ + - /categories/two-factor-authentication-2fa/ + - /articles/securing-your-account-with-two-factor-authentication-2fa +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/signing-commits.md b/translations/es-ES/content/github/authenticating-to-github/signing-commits.md new file mode 100644 index 0000000000000..cd3cb76f53dc4 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/signing-commits.md @@ -0,0 +1,55 @@ +--- +title: Firmar confirmaciones +intro: Puedes firmar las confirmaciones localmente utilizando GPG o S/MIME. +redirect_from: + - /articles/signing-commits-and-tags-using-gpg/ + - /articles/signing-commits-using-gpg/ + - /articles/signing-commits +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.gpg.desktop-support-for-commit-signing %} + +{% tip %} + +**Tips:** + +Para configurar tu cliente Git para firmar confirmaciones por defecto de un repositorio local, en versiones Git 2.0.0 y superiores, ejecuta `git config commit.gpgsign true`. Para firmar todas las confirmaciones por defecto en cualquier repositorio local en tu computadora, ejecuta `git config --global commit.gpgsign true`. + +Para almacenar tus contraseña de llave GPG para no tener que ingresarla cada vez que firmas una confirmación, recomendamos utilizando las siguientes herramientas: + - Para los usuarios de Mac, la [GPG Suite](https://gpgtools.org/) te permite almacenar tu contraseña de llave GPG en la keychain de Mac OS. + - Para los usuarios de Windows, [Gpg4win](https://www.gpg4win.org/) se integra con otras herramientas de Windows. + +También puedes configurar de forma manual [gpg-agent](http://linux.die.net/man/1/gpg-agent) para guardar tu contraseña de llave GPG, pero esta no se integra con la keychain de Mac OS como ssh-agent y requiere mayor configuración. + +{% endtip %} + +Si tienes múltiples llaves o estás intentando firmar confirmaciones o etiquetas con una llave que no coincide con tu identidad de persona que confirma el cambio, deberías [informarle a Git acerca de tu llave de firma](/articles/telling-git-about-your-signing-key). + +1. Cuando confirmas los cambios en tu rama local, agrega la marca -S al comando de confirmación de Git: + ```shell + $ git commit -S -m your commit message + # Creates a signed commit + ``` +2. Si estás utilizando GPG, después de crear tu confirmación, proporciona la contraseña que configuraste cuando [generaste tu llave GPG](/articles/generating-a-new-gpg-key). +3. Cuando terminaste de crear confirmaciones de forma local, súbelas a tu repositorio remoto en {% data variables.product.product_name %}: + ```shell + $ git push + # Pushes your local commits to the remote repository + ``` +4. Activado +{% data variables.product.product_name %}, navega a tu solicitud de cambios. +{% data reusables.repositories.review-pr-commits %} +5. Para ver información más detallada acerca de la firma verificada, haz clic en Verified (Verificada). ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) + +### Further reading + +* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +* "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" +* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/signing-tags.md b/translations/es-ES/content/github/authenticating-to-github/signing-tags.md new file mode 100644 index 0000000000000..4095f71b1153b --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/signing-tags.md @@ -0,0 +1,34 @@ +--- +title: Firmar etiquetas +intro: Puedes firmar las etiquetas localmente utilizando GPG o S/MIME. +redirect_from: + - /articles/signing-tags-using-gpg/ + - /articles/signing-tags +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.gpg.desktop-support-for-commit-signing %} + +1. Para firmar una etiqueta, agrega `-s` a tu comando `git tag`. + ```shell + $ git tag -s mytag + # Creates a signed tag + ``` +2. Verifica tu etiqueta firmada al ejecutar `git tag -v [tag-name]`. + ```shell + $ git tag -v mytag + # Verifies the signed tag + ``` + +### Further reading + +- [Ver las etiquetas de tu repositorio](/articles/viewing-your-repositorys-tags)" +- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +- "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +- "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" +- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +- "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md b/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md new file mode 100644 index 0000000000000..d9f2bc1905d09 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md @@ -0,0 +1,17 @@ +--- +title: Modo sudo +intro: '{% data variables.product.product_name %} te solicita tu contraseña antes de poder modificar tu dirección de correo electrónico, autorizar aplicaciones de terceros, o agregar nuevas llaves públicas, o iniciar otras acciones *sudo-protected* (sudo-protegidas).' +redirect_from: + - /articles/sudo-mode +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Después de haber realizado una acción sudo-protegida, únicamente se te solicitará volver a autenticarte después de unas pocas horas de inactividad. Cada acción sudo-protegida reinicia este temporizador. + +![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) + +### Further reading + +- [Comando `sudo` Unix](http://en.wikipedia.org/wiki/Sudo) diff --git a/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md new file mode 100644 index 0000000000000..9090823edf8e3 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -0,0 +1,114 @@ +--- +title: Informarle a Git acerca de tu clave de firma +intro: "Para firmar las confirmaciones localmente, necesitas informar a Git que hay una llave de GPG o X.509 que quieres utilizar." +redirect_from: + - /articles/telling-git-about-your-gpg-key/ + - /articles/telling-git-about-your-signing-key +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% mac %} + +### Informarle a Git acerca de tu llave GPG + +Si estás usando una llave GPG que coincida con la identidad de la persona que confirma el cambio y tu dirección de correo electrónico verificada con tu cuenta de {% data variables.product.product_name %}, puedes comenzar a firmar confirmaciones y firmar etiquetas. + +{% note %} + +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". + +{% endnote %} + +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +{% data reusables.gpg.paste-gpg-key-id %} +1. Si no estás utilizando GPG Suite, pega el texto que aparece a continuación para agregar la llave GPG a tu perfil bash: + ```shell + $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile + $ echo 'export GPG_TTY=$(tty)' >> ~/.profile + ``` + {% note %} + + **Nota:** Si no tienes `.bash_profile`, este comando agrega tu llave GPG al `.profile`. + + {% endnote %} + +{% data reusables.gpg.x-509-key %} + +{% endmac %} + +{% windows %} + +### Informarle a Git acerca de tu llave GPG + +Si estás usando una llave GPG que coincida con la identidad de la persona que confirma el cambio y tu dirección de correo electrónico verificada con tu cuenta de {% data variables.product.product_name %}, puedes comenzar a firmar confirmaciones y firmar etiquetas. + +{% note %} + +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". + +{% endnote %} + +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +{% data reusables.gpg.paste-gpg-key-id %} + +{% data reusables.gpg.x-509-key %} + +{% endwindows %} + +{% linux %} + +{% note %} + +**Nota:** Linux no admite claves X.509. Puedes configurar gpgsm para proporcionar servicios de cifrado y firma. Sin embargo, actualmente no es compatible con {% data variables.product.product_name %}. Para obtener más información, consulta el tema [gpgsm](https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPGSM.html) en la documentación de GnuPG. + +{% endnote %} + +### Informarle a Git acerca de tu llave GPG + +Si estás usando una llave GPG que coincida con la identidad de la persona que confirma el cambio y tu dirección de correo electrónico verificada con tu cuenta de {% data variables.product.product_name %}, puedes comenzar a firmar confirmaciones y firmar etiquetas. + +{% note %} + +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". + +{% endnote %} + +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +{% data reusables.gpg.paste-gpg-key-id %} +1. Para agregar tu llave GPG a tu perfil bash, pega el texto que aparece a continuación: + ```shell + $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile + $ echo 'export GPG_TTY=$(tty)' >> ~/.profile + ``` + {% note %} + + **Nota:** Si no tienes `.bash_profile`, este comando agrega tu llave GPG al `.profile`. + + {% endnote %} + +{% endlinux %} + +### Further reading + +- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" +- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" +- "[Utilizar una dirección de correo electrónico verificada en tu llave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" +- "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" +- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" +- "[Firmar confirmaciones](/articles/signing-commits)" +- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md new file mode 100644 index 0000000000000..9a86c82a464d3 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md @@ -0,0 +1,54 @@ +--- +title: Probar tu conexión SSH +intro: 'Después de haber configurado tu clave SSH y haberla agregado a tu {% data variables.product.product_name %} cuenta, puedes probar tu conexión.' +redirect_from: + - /articles/testing-your-ssh-connection +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Antes de probar tu conexión SSH, debes haber hecho lo siguiente: +- [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) +- [Generado una clave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +- [Agregado una clave SSH nueva a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) + +Cuando pruebes tu conexión, tendrás que autenticar esta acción utilizando tu contraseña, que es la contraseña de clave SSH que ya creaste. Para obtener más información acerca de trabajar con contraseñas de clave SSH, consulta ["Trabajar con contraseñas de clave SSH"](/articles/working-with-ssh-key-passphrases). + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Ingresa lo siguiente: + ```shell + $ ssh -T git@{% data variables.command_line.codeblock %} + # Attempts to ssh to {% data variables.product.product_name %} + ``` + + Puedes ver una advertencia como la siguiente: + + ```shell + > La autenticidad del host '{% data variables.command_line.codeblock %} (DIRECCIÓN IP)' no se puede establecer. + > La clave de huella digital RSA es SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. + > ¿Estás seguro de que quieres continuar conectado (sí/no)? + ``` + +3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: + ```shell + > Hi username! You've successfully authenticated, but GitHub does not + > provide shell access. + ``` + + {% linux %} + + Puede que veas el siguiente mensaje de error: + ```shell + ... + El agente admitió una falla para registrarse utilizando la clave. + debug1: No hay más métodos de autenticación para probar. + Permiso denegado (publickey). + ``` + + Se trata de un problema conocido con determinadas distribuciones de Linux. Para obtener más información, consulta ["Error: El agente admitió una falla para registrarse"](/articles/error-agent-admitted-failure-to-sign). + + {% endlinux %} + +4. Comprueba que el mensaje resultante contenga tu nombre de usuario. Si recibes un mensaje de "permiso denegado", consulta ["Error: Permiso denegado (publickey)"](/articles/error-permission-denied-publickey). diff --git a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md new file mode 100644 index 0000000000000..07abe10c7f20c --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md @@ -0,0 +1,13 @@ +--- +title: Solucionar problemas de verificación de confirmación de firma +intro: 'Puede que debas solucionar problemas imprevistos que surgen cuando se firman confirmaciones de forma local para la verificación en {% data variables.product.product_name %}.' +redirect_from: + - /articles/troubleshooting-gpg/ + - /articles/troubleshooting-commit-signature-verification +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md new file mode 100644 index 0000000000000..4245d367cc988 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md @@ -0,0 +1,12 @@ +--- +title: Solucionar problemas de SSH +intro: 'Cuando utilizas SSH para conectarte y autenticarte para {% data variables.product.product_name %}, puede que debas solucionar problemas inesperados que surjan.' +mapTopic: verdadero +redirect_from: + - /articles/troubleshooting-ssh +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md new file mode 100644 index 0000000000000..4210ea0464624 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md @@ -0,0 +1,18 @@ +--- +title: Actualizar una llave GPG vencida +intro: 'Cuando verifica una firma, {% data variables.product.product_name %} comprueba que la clave no esté revocada o vencida. Si tu clave de firma está revocada o vencida, {% data variables.product.product_name %} no puede verificar tus firmas. Si tu clave está revocada, utiliza la clave principal u otra clave que no esté revocada para firmar tus confirmaciones.' +redirect_from: + - /articles/updating-an-expired-gpg-key +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si tu clave está vencida, debes [actualizar el vencimiento](https://www.gnupg.org/gph/en/manual/c235.html#AEN328), exportar la clave nueva, eliminar la clave vencida en tu cuenta de GitHub y [cargar la clave nueva para GitHub](/articles/adding-a-new-gpg-key-to-your-github-account/). Tus confirmaciones y etiquetas previas se mostrarán como verificadas, siempre que la clave reúna todos los demás requisitos de verificación. + +Si tu clave es inválida y no utilizas otra clave válida de tu conjunto de claves, pero en su lugar generas una llave GPG nueva con un conjunto nuevo de credenciales, tus confirmaciones hechas con la clave revocada o vencida se seguirán mostrando como no verificadas. Asimismo, tus credenciales nuevas no podrán volver a firmar o verificar tus confirmaciones y etiquetas antiguas. + +### Further reading + +- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-ES/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/es-ES/content/github/authenticating-to-github/updating-your-github-access-credentials.md new file mode 100644 index 0000000000000..ddd4926f2f3c9 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/updating-your-github-access-credentials.md @@ -0,0 +1,60 @@ +--- +title: Actualizar tus credenciales de acceso de GitHub +intro: 'Las credenciales de {% data variables.product.product_name %} no solo incluyen{% if currentVersion != "github-ae@latest" %} tu contraseña, sino también{% endif %} los tokens de acceso, llaves de SSH, y tokens de la API de la aplicación que utilizas para comunicarte con {% data variables.product.product_name %}. Si lo necesitas, puedes restablecer todas estas credenciales de acceso tú mismo.' +redirect_from: + - /articles/rolling-your-credentials/ + - /articles/how-can-i-reset-my-password/ + - /articles/updating-your-github-access-credentials +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion != "github-ae@latest" %} +### Solicitar una contraseña nueva + +1. Para solicitar una contraseña nueva, visita {% if currentVersion == "free-pro-team@latest" %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. +2. Ingresa la dirección de correo electrónico asociada a tu cuenta personal {% data variables.product.product_name %}, luego haz clic en **Send password reset email** (Enviar correo electrónico de restablecimiento de contraseña). El correo electrónico se enviará a la dirección de correo electrónico de respaldo si tienes configurada una. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png) +3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam. +4. Después de hacer clic en el enlace de tu correo electrónico, se te pedirá que ingreses una contraseña nueva. ![Casilla de recuperación de contraseña](/assets/images/help/settings/password_recovery_page.png) + +{% tip %} + +Para evitar que vuelvas a perder tu contraseña, sugerimos utilizar un administrador de contraseñas seguro, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/) o [Keeper](https://keepersecurity.com/). + +{% endtip %} + +### Cambiar una contraseña existente + +{% data reusables.repositories.blocked-passwords %} + +1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +4. En "Change password" (Cambiar contraseña), escribe tu contraseña antigua, una contraseña segura nueva y confirma tu contraseña nueva. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)" +5. Haz clic en **Update password** (Actualizar contraseña). + +{% tip %} + +Para mayor seguridad, habilita la autenticación de dos factores además de cambiar la contraseña. Consulta [Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication) para obtener más detalles. + +{% endtip %} +{% endif %} +### Actualizar tus tokens de acceso + +Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" para recibir indicaciones sobre revisar y eliminar tokens de acceso. Para generar tokens de acceso nuevos, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +### Actualizar tus claves SSH + +Consulta "[Revisar tus claves SSH](/articles/reviewing-your-ssh-keys)" para obtener indicaciones sobre la revisar y eliminar claves SSH. Para generar y agregar claves SSH nuevas, consulta "[Generar una clave SSH](/articles/generating-an-ssh-key)". + +### Restablecer tokens API + +Si tienes alguna aplicación registrada con {% data variables.product.product_name %}, querrás restablecer sus tokens de OAuth. Para obtener más información, consulta la terminal de "[Restablecer una autorización](/rest/reference/apps#reset-an-authorization)". + +{% if currentVersion != "github-ae@latest" %} +### Evitar el acceso no autorizado + +Para obtener más sugerencias acerca de proteger tu cuenta y evitar el acceso sin autorización, consulta "[Evitar el acceso sin autorización](/articles/preventing-unauthorized-access)". +{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md new file mode 100644 index 0000000000000..cbf04e1efce57 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md @@ -0,0 +1,22 @@ +--- +title: Utilizar una dirección de correo electrónico verificada en tu llave GPG +intro: 'Cuando verifica una firma, {% data variables.product.product_name %} comprueba que la dirección de correo electrónico de la persona que confirma el cambio o del etiquetador coincida con una dirección de correo electrónico de las identidades de llave GPG y que sea una dirección de correo electrónico verificada en la cuenta del usuario. Esto garantiza que la clave te pertenece y que tú creaste la confirmación o etiqueta.' +redirect_from: + - /articles/using-a-verified-email-address-in-your-gpg-key +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} +Si debes verificar tu dirección de correo electrónico de GitHub, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address/)". +{% endif %}Si debes actualizar o agregar una dirección de correo electrónico para tu llave GPG, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". + +Las confirmaciones y etiquetas pueden contener varias direcciones de correo electrónico. Para las confirmaciones, está el autor —la persona que escribió el código— y la persona que confirma el cambio —la persona que agregó la confirmación al árbol—. Cuando se firma una confirmación con Git, sea durante una fusión, cherry-picking o `confirmación git` normal, la dirección de correo electrónico de la persona que confirma el cambio debe ser la tuya, incluso si la dirección de correo electrónico del autor no lo es. Con las etiquetas es más simple: la dirección de correo electrónico del etiquetador es siempre la del usuario que creó la etiqueta. + +Si debes cambiar la dirección de correo electrónico de la persona que confirma el cambio o del etiquetador, consulta "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address/)". + +### Further reading + +- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md new file mode 100644 index 0000000000000..794c1e3fb13b2 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md @@ -0,0 +1,44 @@ +--- +title: Uso de SSH a través del puerto HTTPS +intro: 'Algunas veces, los firewalls se niegan a permitir conexiones SSH por completo. Si el utilizar el [clonado de HTTPS con almacenamiento de credenciales en el caché](/github/using-git/caching-your-github-credentials-in-git) no es una opción, puedes intentar clonar utilizando una conexión SSH que hayas hecho a través del puerto HTTPS. La mayoría de las reglas del firewall deberían permitir esto, pero los servidores proxy pueden interferir.' +redirect_from: + - /articles/using-ssh-over-the-https-port +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Usuarios de GitHub Enterprise**: Actualmente, no se puede acceder a GitHub Enterprise por SSH a través del puerto HTTPS. + +{% endtip %} + +Para probar si es posible el SSH a través del puerto HTTPS, ejecuta este comando SSH: + +```shell +$ ssh -T -p 443 git@ssh.github.com +> Hi username! You've successfully authenticated, but GitHub does not +> provide shell access. +``` + +Si eso funcionó, ¡fantástico! De lo contrario, puede que debas [seguir nuestra guía de solución de problemas](/articles/error-permission-denied-publickey). + +### Habilitar conexiones SSH a través de HTTPS + +Si es posible el SSH en `git@ssh.{% data variables.command_line.backticks %}` a través del puerto 443, puedes reemplazar los parámetros SSH para forzar que cualquier conexión a {% data variables.product.product_location %} se ejecute a través de ese servidor y puerto. + +Para establecer esto en tus parámetros ssh, edita el archivo en `~/.ssh/config` y agrega esta sección: + +``` +Host {% data variables.command_line.codeblock %} + Hostname ssh.{% data variables.command_line.codeblock %} + Port 443 +``` + +Puedes probar que esto funcione volviéndote a conectar a {% data variables.product.product_location %}: + +```shell +$ ssh -T git@{% data variables.command_line.codeblock %} +> Hi username! You've successfully authenticated, but GitHub does not +> provide shell access. +``` diff --git a/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md b/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md new file mode 100644 index 0000000000000..193181c338484 --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md @@ -0,0 +1,24 @@ +--- +title: Ver y administrar tus sesiones de SAML activas +intro: Puedes ver y revocar tus sesiones de SAML activas en tus parámetros de seguridad. +redirect_from: + - /articles/viewing-and-managing-your-active-saml-sessions +versions: + free-pro-team: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security %} +3. Debajo de "Sesiones" puedes ver tus sesiones activas de SAML. ![Lista de sesiones de SAML activas](/assets/images/help/settings/saml-active-sessions.png) +4. Para ver los detalles de la sesión, da clic en **Ver más**. ![Botón para abrir los detalles de la sesión de SAML](/assets/images/help/settings/saml-expand-session-details.png) +5. Para revocar una sesión, da clic en **Revocar SAML**. ![Botón para revocar una sesión de SAML](/assets/images/help/settings/saml-revoke-session.png) + + {% note %} + + **Nota:** Cuando revocas una sesión, puedes eliminar tu autenticación de SAML para esa organización. Para volver a acceder a la organización, tendrás que hacer un inicio de sesión único a través de tu proveedor de identidad. Para obtener más información, consulta "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + + {% endnote %} + +### Further reading + +- "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" \ No newline at end of file diff --git a/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md new file mode 100644 index 0000000000000..c2e0f2a3e380a --- /dev/null +++ b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -0,0 +1,112 @@ +--- +title: Trabajar con contraseñas de clave SSH +intro: Puedes asegurar tus claves SSH y configurar un agente de autenticación para no tener que volver a ingresar tu contraseña cada vez que uses tus claves SSH. +redirect_from: + - /ssh-key-passphrases/ + - /working-with-key-passphrases/ + - /articles/working-with-ssh-key-passphrases +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Con las claves SSH, si alguien obtiene acceso a tu computadora, también tiene acceso a cada sistema que usa esa clave. Para agregar una capa extra de seguridad, puedes incluir una contraseña a tu clave SSH. Puedes usar `ssh-agent` para guardar tu contraseña de forma segura y no tener que volver a ingresarla. + +### Agregar o cambiar una contraseña + +Puedes cambiar la contraseña por una llave privada existente sin volver a generar el par de claves al escribir el siguiente comando: + +```shell +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' +> Enter new passphrase (empty for no passphrase): [Type new passphrase] +> Enter same passphrase again: [Repeat the new passphrase] +> Your identification has been saved with the new passphrase. +``` + +Si tu clave ya tiene una contraseña, se te pedirá que la ingreses antes de que puedas cambiar a una nueva contraseña. + +{% windows %} + +### Auto-lanzamiento `ssh-agent` en Git para Windows + +Puedes ejecutar el `ssh-agent` automáticamente cuando abres el bash o el Git shell. Copia las siguientes líneas y pégalas en tu `~/.perfil` o archivo `~/.bashrc` en Git Shell: + +``` bash +env=~/.ssh/agent.env + +agent_load_env () { test -f "$env" && . "$env" >| /dev/null ; } + +agent_start () { + (umask 077; ssh-agent >| "$env") + . "$env" >| /dev/null ; } + +agent_load_env + +# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= agent not running +agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?) + +if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then + agent_start + ssh-add +elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then + ssh-add +fi + +unset env + +if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then + agent_start + ssh-add +elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then + ssh-add +fi + +unset env +``` + +Si tu llave privada no está almacenada en una de las ubicaciones predeterminadas (como`~/.ssh/id_rsa`), necesitarás indicar a tu agente de autenticación SSH en dónde encontrarla. Para agregar tu clave a ssh-agent, escribe `ssh-add ~/path/to/my_key`. Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)" + +{% tip %} + +**Sugerencias:** si quieres que `ssh-agent` olvide tu clave luego de un tiempo, puedes configurarlo para que lo haga ejecutando `ssh-add -t `. + +{% endtip %} + +Ahora, cuando ejecutas Git Bash por primera vez, se te pedirá tu contraseña: + +```shell +> Initializing new SSH agent... +> succeeded +> Enter passphrase for /c/Users/you/.ssh/id_rsa: +> Identity added: /c/Users/you/.ssh/id_rsa (/c/Users/you/.ssh/id_rsa) +> Welcome to Git (version 1.6.0.2-preview20080923) +> +> Run 'git help git' to display the help index. +> Run 'git help ' to display help for specific commands. +``` + +El proceso de `ssh-agent` continuará funcionando hasta que cierres sesión, apagues tu computadora o termines el proceso. + +{% endwindows %} + +{% mac %} + +### Guardar tu contraseña en keychain + +En OS X Leopard a través de OS X El Capitan, los siguientes archivos de llave privada predeterminada se manejan automáticamente: + +- *.ssh/id_rsa* +- *.ssh/identity* + +La primera vez que usas tu clave, se te pedirá que ingreses tu contraseña. Si eliges guardar la contraseña con tu keychain, no necesitarás ingresarla nuevamente. + +De lo contrario, puedes almacenar tu contraseña en la keychain cuando agregues tu clave a ssh-agent. Para obtener más información, consulta "[Agregar tu clave SSH a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)." + +{% endmac %} + +### Further reading + +- "[Acerca de SSH](/articles/about-ssh)" diff --git a/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md b/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md new file mode 100644 index 0000000000000..37c7dc72a3797 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md @@ -0,0 +1,32 @@ +--- +title: Acerca de la gestión y moderación de la comunidad +intro: '{% data variables.product.prodname_dotcom %} ofrece herramientas para que los mantenedores de repositorios puedan establecer y dar cumplimiento a los estándares de comportamiento en sus comunidades dentro de {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' +--- + +### Acerca de la gestión y moderación de la comunidad + +{% data reusables.policies.github-community-guidelines-and-terms %} + +{% data variables.product.prodname_dotcom %} también ofrece herramientas para que los mantenedores de repositorios definan y den cumplimiento a los estándares más altos de comportamiento en sus propias comunidades dentro de {% data variables.product.prodname_dotcom_the_website %}. + +Una vez definidos los estándares de comportamiento de la comunidad, puedes exhortar a que se tenga un ambiente agradable y productivo respondiendo a los comportamientos perjudiciales de manera rápida y justa. Moderar tu comunidad con efectividad generará confianza y permitirá que los colaboradores se sientan seguros y bienvenidos en ella. + +### Herramientas para moderar tu comunidad + +Las herramientas de {% data variables.product.prodname_dotcom %} optimizan la gestión y las tareas de moderación en tu comunidad sin exigir mucha experiencia previa en ello. + +Como mantenedor de repositorio, puedes crear tus propios lineamientos para contribuir con tu proyecto y compartirlos en el mismo. {% data variables.product.prodname_dotcom %} ofrece una lista de control en el perfil de la comunidad que te ayudará a crear y publicar los archivos de salud de la misma. Los colaboradores potenciales de tu proyecto pueden revisar la lista de control en el perfil de tu comunidad para conocer sus estándares y decidir si quieren contribuir. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +{% data reusables.community.tools-for-moderating %} + +Los colaboradores pueden reportar el contenido perjudicial en {% data variables.contact.github_support %} siempre que lo deseen. Si decides incluir el contenido reportado para un repositorio público en tu organización, los colaboradores también pueden reportar los comentarios que presenten comportamiento perjudicial directamente a los mantenedores del mismo. Para encontrar más información, visita la sección "[Gestionar contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)." + +### Further reading + +- "[Tu Código de Conducta](https://opensource.guide/code-of-conduct/)" de las Guías de Código Abierto +- "[Construyendo Comunidades de Bienvenida](https://opensource.guide/building-community/)" de las Guías de Código Abierto +- "[Liderazgo y Gobierno](https://opensource.guide/leadership-and-governance/)" de las Guías de Código Abierto +- "[Por qué es inadecuado el humillar a los demás](https://github.community/t5/Studies-in-Community/Shaming-and-why-it-is-inappropriate/ba-p/12728)" del Foro de la Comunidad de GitHub +- "[No es lo mismo la crítica constructiva que el ser tóxico](https://github.community/t5/Studies-in-Community/Being-toxic-is-not-constructive-criticism/ba-p/8029)" del Foro de la Comunidad de GitHub diff --git a/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md b/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md new file mode 100644 index 0000000000000..77a5a10a3f1b2 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md @@ -0,0 +1,40 @@ +--- +title: Acerca de los perfiles de comunidad para los repositorios públicos +intro: Los mantenedores del repositorio pueden revisar el perfil de comunidad de sus repositorios públicos para saber cómo pueden ayudar a hacer crecer su comunidad y dar soporte a los colaboradores. Los colaboradores pueden ver el perfil de comunidad de un repositorio público para ver si quieren contribuir con el proyecto. +redirect_from: + - /articles/viewing-your-community-profile/ + - /articles/about-community-profiles-for-public-repositories +versions: + free-pro-team: '*' +--- + +La lista de verificación del perfil de comunidad se comprueba para ver si un proyecto incluye un archivo de salud de comunidad recomendado, como README, CODE_OF_CONDUCT, LICENSE o CONTRIBUTING, en una ubicación admitida. Para obtener más información, consulta "[ una ubicación admitida](/articles/accessing-a-project-s-community-profile)". + +### Usar la lista de verificación del perfil de comunidad como mantenedor del repositorio + +Como mantenedor del repositorio, usa la lista de verificación del perfil de comunidad para ver si tu proyecto cumple con los estándares de comunidad recomendados para ayudar a las personas a usar y contribuir con tu proyecto. Para obtener más información, consulta "[Construir una comunidad](https://opensource.guide/building-community/)" en las Guías de código abierto. + +Si un proyecto no tiene un archivo recomendado, puedes hacer clic en **Agregar** para redactar y enviar un archivo. + +{% data reusables.repositories.valid-community-issues %} Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". + +![Lista de verificación del perfil de comunidad con estándares de comunidad recomendados para mantenedores](/assets/images/help/repository/add-button-community-profile.png) + +{% data reusables.repositories.security-guidelines %} + +### Usar la lista de verificación del perfil de comunidad como colaborador o miembro de la comunidad + +Como posible colaborador, usa la lista de verificación del perfil de comunidad para ver si tu proyecto cumple con los estándares de comunidad recomendados y decidir si quieres contribuir. Para obtener más información, consulta "[¿Cómo contribuir?](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" en las Guías de código abierto. + +Si un proyecto no tiene un archivo recomendado, puedes hacer clic en **Proponer** para redactar y enviar un archivo para que el mantenedor del repositorio lo apruebe. + +![Lista de verificación del perfil de comunidad con estándares de comunidad recomendados para colaboradores](/assets/images/help/repository/propose-button-community-profile.png) + +### Further reading + +- "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project)" +- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" +- "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)" +- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" +- "[Guías de código abierto](https://opensource.guide/)" +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) diff --git a/translations/es-ES/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md b/translations/es-ES/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md new file mode 100644 index 0000000000000..1c4ec9784fdb5 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md @@ -0,0 +1,46 @@ +--- +title: Acerca de las plantillas de propuestas y solicitudes de extracción +intro: 'Con las plantillas de propuestas y solicitudes de extracción, puedes personalizar y estandarizar la información que quisieras que los colaboradores incluyan cuando abren propuestas y solicitudes de extracción en tu repositorio.' +redirect_from: + - /articles/about-issue-and-pull-request-templates +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Una vez que creas las plantillas de propuestas y solicitudes de extracción en tu repositorio, los colaboradores pueden usar las plantillas para abrir propuestas o describir los cambios propuestos en sus solicitudes de extracción de acuerdo con las pautas de contribución del repositorio. Para obtener más información sobre cómo agregar pautas de contribución a un repositorio, consulta "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)". + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Puedes crear plantillas predeterminadas de propuestas y solicitudes de cambios para tu cuenta de organización o de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} + +### Plantillas de propuestas + +Cuando creas plantillas de propuestas para tu repositorio usando el creador de plantillas de propuestas, estarán disponibles para que las usen los colaboradores cuando abran nuevas propuestas en el repositorio. + +![Página de la propuesta nueva que muestra las opciones de plantilla de propuesta](/assets/images/help/issues/new-issue-page-with-multiple-templates.png) + +Al usar el creador de plantillas, puedes especificar un título y una descripción para cada plantilla, agregar el contenido de la plantilla y asignar la plantilla a la rama por defecto o bien abrir una solicitud de extracción en el repositorio. El creador de plantillas automáticamente agrega el markup del texto preliminar de YAML que se requiere para que la plantilla aparezca en la página de la propuesta nueva. Para obtener más información, consulta "[Configurar plantillas de reporte de problemas para tu repositorio](/articles/configuring-issue-templates-for-your-repository)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% data reusables.repositories.issue-template-config %} Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)". +{% endif %} + +Las plantillas de propuestas se almacenan en la rama por defecto del repositorio, en un directorio oculto `.github/ISSUE_TEMPLATE`. Si creas una plantilla en otra rama, no estará disponible para que la usen los colaboradores. Los nombres de archivo de la plantilla de propuesta no distinguen entre mayúsculas y minúsculas y necesitan una extensión *.md*. {% data reusables.repositories.valid-community-issues %} + +Es posible crear de forma manual una única plantilla de propuesta en Markdown usando el flujo de trabajo de la plantilla de propuesta heredado. Los colaboradores del proyecto automáticamente ven el contenido de la plantilla en el cuerpo de la propuesta. Si embargo, recomendamos usar el creador de varias plantillas de propuestas actualizado para crear plantillas de propuestas. Para obtener más información acerca del flujo de trabajo heredado, consulta "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". + +{% data reusables.repositories.security-guidelines %} + +### Plantillas de solicitudes de extracción + +Cuando agregas una plantilla de solicitud de extracción a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la solicitud de extracción. + +![Plantilla de solicitud de extracción de ejemplo](/assets/images/help/pull_requests/pr-template-sample.png) + +Debes crear las plantillas en la rama por defecto del repositorio. Las plantillas creadas en otras ramas no están disponibles para que las usen los colaboradores. Puedes almacenar tu plantilla de solicitud de extracción en el directorio raíz visible del repositorio, la carpeta `docs` o el directorio oculto `.github`. Los nombres de archivo de la plantilla de solicitud de extracción no distinguen entre mayúsculas y minúsculas y pueden tener una extensión como *.md* o *.txt*. + +Para obtener más información, consulta [Crear plantillas de solicitud de extracción para tu repositorio](/articles/creating-a-pull-request-template-for-your-repository)". diff --git a/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md b/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md new file mode 100644 index 0000000000000..30f52ef967acc --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md @@ -0,0 +1,45 @@ +--- +title: Acerca de los debates de equipo +intro: 'Tu equipo puede planificar de manera conjunta, actualizarse unos a otros o hablar sobre cualquier tema que quieran en las publicaciones de debates en la página de tu equipo en una organización.' +redirect_from: + - /articles/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Todo miembro de una organización puede publicar en la página de tu equipo o participar de un debate público. {% data reusables.organizations.team-discussions-permissions %} + +![Pestaña Debayes de la página del equipo con debates privados y públicos](/assets/images/help/organizations/team-page-discussions-tab.png) + +Puedes vincularte a cualquier debate de equipo para hacer referencia al mismo en otro lugar. Puedes anclar publicaciones importantes a la página de tu equipo para una referencia rápida a futuro. Para obtener más información, consulta "[Anclar un debate del equipo](/articles/pinning-a-team-discussion)". + +![Pestaña Debates anclados de la página del equipo con debate anclado](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %} Los propietarios pueden desactivar debates del equipo para toda la organización. Para obtener más información, consulta "[Desactivar los debates del equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)". + +### Notificaciones para los debates del equipo + +Cuando alguien publica o responde a un debate público en la página de un equipo, los miembros del equipo y los miembros de cualquier equipo hijo reciben un correo electrónico o notificaciones web. Cuando alguien publica o responde a un debate privado en la página de un equipo, solo los miembros del equipo reciben notificaciones. + +{% tip %} + +**Sugerencia:** Dependiendo de los parámetros de tu notificación, recibirás actualizaciones por correo electrónico, la página de notificaciones web en {% data variables.product.product_name %}, o ambas. Para obtener más información, consulta las secciones {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Acerca de las notificaciones web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}". + +{% endtip %} + +Por defecto, si se menciona tu nombre de usuario en un debate del equipo, recibirás notificaciones por la publicación que menciona tu nombre de usuario y toda respuesta a esa publicación. Además, por defecto, si respondes a una publicación, recibirás notificaciones por otras respuestas a la publicación. + +Para apagar las notificaciones para los debates del equipo, puedes cancelar la suscripción a una publicación de debate específica o cambiar tus parámetros de notificación para dejar de ver o ignorar por completo los debtaes de un equipo específico. Te puedes suscribir a las notificaciones para la publicación de un debate específico incluso si dejaste de ver los debates de ese equipo. + +Para obtener más información, consulta las secciones{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Suscribirte y desuscribirte de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" y "[Equipos anidados](/articles/about-teams/#nested-teams)". + +### Further reading + +- "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" +- [Acerca de los equipos](/articles/about-teams)" +- "[Crear un debate de equipo](/articles/creating-a-team-discussion)" +- "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/about-wikis.md b/translations/es-ES/content/github/building-a-strong-community/about-wikis.md new file mode 100644 index 0000000000000..1d4c9919c2a8c --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/about-wikis.md @@ -0,0 +1,28 @@ +--- +title: Acerca de las wikis +intro: 'Puedes alojar documentación para tu repositorio en una wiki, para que otros puedan usar y colaborar con tu proyecto.' +redirect_from: + - /articles/about-github-wikis/ + - /articles/about-wikis +product: '{% data reusables.gated-features.wikis %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cada repositorio de {% data variables.product.product_name %} viene equipado con una sección para alojar documentación, llamada una wiki. Puedes usar la wiki de tu repositorio para compartir contenido en forma completa acerca de tu proyecto, como por ejemplo cómo usarlo, cómo lo diseñaste o sus principios básicos. Un archivo README rápidamente dice lo que puede hacer tu proyecto, mientras que puedes usar una wiki para proporcionar documentación adicional. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". + +Con las wikis, puedes escribir contenido como en cualquier otro lado en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nuestra biblioteca Markup de código abierto](https://github.com/github/markup) para convertir diferentes formatos en HTML, para que puedas elegir escribir en Markdown o en cualquier otro formato admitido. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Si creas un wiki en un repositorio público, éste estará disponible para {% if enterpriseServerVersions contains currentVersion %}cualquiera con acceso a {% data variables.product.product_location %}{% else %}el público en general{% endif %}. {% endif %}Si creas un wiki en un repositorio interno o privado, {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}las personas{% elsif currentVersion == "github-ae@latest" %}los miembros de la empresa{% endif %} con acceso al repositorio también podrán acceder al wiki. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". + +Puedes editar las wikis directamente en {% data variables.product.product_name %} o puedes editar los archivos wiki localmente. Predeterminadamente, solo las personas con acceso a tu repositorio podrán hacer cambios a los wikis, aunque podrás permitir que cualquiera en {% data variables.product.product_location %} colabore con un wiki en {% if currentVersion == "github-ae@latest" %}un repositorio interno{% else %}un repositorio público{% endif %}. Para obtener más información, consulta "[Cambiar permisos de acceso para wikis](/articles/changing-access-permissions-for-wikis)". + +### Further reading + +- "[Agregar o eliminar páginas wiki](/articles/adding-or-editing-wiki-pages)" +- "[Crear un pie de página o barra lateral para tu wiki](/articles/creating-a-footer-or-sidebar-for-your-wiki)" +- "[Editar el contenido de una wiki](/articles/editing-wiki-content)" +- "[Ver el historial de cambios de una wiki](/articles/viewing-a-wiki-s-history-of-changes)" +- "[Buscar wikis](/articles/searching-wikis)" diff --git a/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md b/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md new file mode 100644 index 0000000000000..3fb12cb6ba750 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md @@ -0,0 +1,17 @@ +--- +title: Acceso a un perfil de comunidad del proyecto +intro: Ver un perfil de comunidad del repositorio público para verificar el estado de un proyecto y decidir si deseas contribuir. +redirect_from: + - /articles/accessing-a-project-s-community-profile + - /articles/accessing-a-projects-community-profile +versions: + free-pro-team: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Community** (Comunidad). ![Comunidad en la barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-community-tab.png) + +### Further reading + +- [Acerca de los perfiles de la comunidad para repositorios públicos](/articles/about-community-profiles-for-public-repositories)" diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md new file mode 100644 index 0000000000000..cd9dcc08bf23a --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -0,0 +1,50 @@ +--- +title: Agregar un código de conducta a tu proyecto +intro: 'Adoptar un código de conducta para definir los estándares de la comunidad, señalizar un proyecto cordial e inclusivo, y delinear los procedimientos para manejar los abusos.' +redirect_from: + - /articles/adding-a-code-of-conduct-to-your-project +versions: + free-pro-team: '*' +--- + +Un *código de conducta* define los estándares de cómo participar en una comunidad. Señala un entorno inclusivo que respeta todas las contribuciones. También describe los procedimientos para tratar problemas de tus proyectos entre los miembros de la comunidad. Para obtener más información acerca de por qué un código de conducta define los estándares y las expectativas sobre cómo participar en una comunidad, consulta la [Guía de Código abierto](https://opensource.guide/code-of-conduct/). + +Antes de adoptar un código de conducta para tu proyecto: + +* Investiga códigos de conducta diferentes diseñados para proyectos de código abierto. Elije uno que refleje los estándares de tu comunidad. +* Considera cuidadosamente si estás dispuesto a hacerlo cumplir y puedes hacerlo. + +Puedes agregar un código de conducta a tu proyecto si utilizas una plantilla o creando manualmente un código de conducta personalizado. Tu código de conducta estará disponible de cualquier forma, pero el "Código de conducta" solo se marcará como completo en el perfil comunitario de tu repositorio si utilizas una plantilla. Si utilizas un código de conducta que escriba otra persona u organización, asegúrate de utilizar los lineamientos de adjudicación de la fuente. Para obtener más información acerca de los perfiles comunitarios, consulta la sección "[Acerca de los perfiles comunitarios para los repositorios públicos](/github/building-a-strong-community/about-community-profiles-for-public-repositories)". + +Puedes crear un código de conducta por defecto para tu organización o cuenta de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +### Agregar un código de conducta mediante una plantilla + +{% data variables.product.product_name %} brinda plantillas para códigos de conducta comunes a fin de ayudarte a agregar rápidamente un código de conducta para tu proyecto. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo de nombre del archivo, escribe *CODE_OF_CONDUCT.md*. +4. Haz clic en **Choose a code of conduct template** (Elegir una plantilla de código de conducta). ![Botón para elegir una plantilla de código de conducta](/assets/images/help/repository/code-of-conduct-tool.png) +5. En el lateral izquierdo de la página, selecciona un código de conducta para previsualizar y agregar a tu proyecto. ![Selección de una plantilla de código de conducta](/assets/images/help/repository/code-of-conduct-tool-picker.png) +6. En el lateral derecho de la página, completa los campos para llenar el código de conducta seleccionado con la información adecuada. +7. Haz clic en **Review and submit** (Revisar y enviar). ![Revisar y enviar el código de conducta a un proyecto](/assets/images/help/repository/code-of-conduct-tool-review.png) +8. Revisa los contenidos del código de conducta que está en el área de texto. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Agregar un código de conducta manualmente + +Si el código de conducta que quieres utilizar no se encuentra disponible en las plantillas proporcionadas, puedes agregar manualmente un código de conducta. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo de nombre, teclea el nombre y la extensión del archivo. ![Nombre de archivo del código de conducta nuevo](/assets/images/help/repository/new-code-of-conduct-file-name.png) + - Para que tu código de conducta se muestre como visible en el directorio raíz del repositorio, teclea *CODE_OF_CONDUCT* en el campo de nombre de archivo. + - Para que tu código de conducta esté visible en los `docs` del repositorio, teclea *docs/CODE_OF_CONDUCT*. + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. +4. En el archivo nuevo, agrega tu código de conducta personalizado. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md b/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md new file mode 100644 index 0000000000000..3eeea5ab00c29 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md @@ -0,0 +1,50 @@ +--- +title: Agregar una licencia a un repositorio +intro: Puedes incluir una licencia de código abierto en tu repositorio para que simplifique la contribución de otras personas. +redirect_from: + - /articles/adding-a-license-to-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Si incluyes una licencia detectable en tu repositorio, las personas que visiten tu repositorio la verán en la parte superior de la página del repositorio. Para leer el archivo de licencia completa, haz clic en el nombre de la licencia. + +![Un encabezado de repositorio con una licencia MIT](/assets/images/help/repository/repo-license-indicator.png) + +Las licencias de código abierto permiten que otras personas usen, cambien y distribuyan el proyecto en tu repositorio. Para más información sobre las licencias de repositorios, consulta "[Licenciar un repositorio](/articles/licensing-a-repository)". + +### Incluir una licencia de código abierto en tu repositorio + + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo del nombre del archivo, escribe *LICENSE* o *LICENSE.md* (todo en mayúscula). +4. A la derecha del campo del nombre del archivo, haz clic en **Elegir una plantilla de licencia**. ![Elige un botón para la plantilla de licencia](/assets/images/help/repository/license-tool.png) +5. En el lateral izquierdo de la página, en "Agregar una licencia a tu proyecto", revisa las licencias disponibles, luego selecciona una licencia de la lista. ![Lista de licencias disponibles](/assets/images/help/repository/license-tool-picker.png) +6. Haz clic en **Review and submit** (Revisar y enviar). ![Botón Review and submit (Revisar y enviar)](/assets/images/help/repository/license-review-tool.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.choose-commit-email %} +10. Haz clic en **Commit new file** (Confirmar archivo nuevo). ![Confirmar licencia a la rama](/assets/images/help/repository/license-submit-tool.png) + +{% endif %} + + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo del nombre del archivo, escribe *LICENSE* o *LICENSE.md* (todo en mayúscula). +4. En la pestaña **Edit new file** (Editar archivo nuevo), pega el texto completo de la licencia que deseas usar. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +7. Debajo de los campos del mensaje de confirmación, decide si deseas agregar tu confirmación a la rama actual o a una rama nueva. Si tu rama actual es `main`, deberás elegir crear una nueva rama para tu confirmación y luego crear una solicitud de extracción. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)". ![Confirmar opciones de rama](/assets/images/help/repository/choose-commit-branch.png) +8. Haz clic en **Commit new file** (Confirmar archivo nuevo). ![Confirmar licencia a la rama](/assets/images/help/repository/license-submit-tool.png) + +{% endif %} + +### Further reading + +- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md b/translations/es-ES/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md new file mode 100644 index 0000000000000..a88af9c9e9152 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md @@ -0,0 +1,57 @@ +--- +title: Agregar o eliminar páginas wiki +intro: 'Puedes agregar y editar páginas wiki directamente en {% data variables.product.product_name %} o localmente usando la línea de comando.' +redirect_from: + - /articles/adding-wiki-pages-via-the-online-interface/ + - /articles/editing-wiki-pages-via-the-online-interface/ + - /articles/adding-and-editing-wik-pages-locally/ + - /articles/adding-and-editing-wiki-pages-locally/ + - /articles/adding-or-editing-wiki-pages +product: '{% data reusables.gated-features.wikis %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Agregar páginas wiki + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +3. En el ángulo superior derecho de la página, haz clic en **New Page** (Página nueva) ![Botón de la nueva página wiki](/assets/images/help/wiki/wiki_new_page_button.png) +4. Opcionalmente, para escribir en otro formato diferente a Markdown, usa el menú desplegable del modo Edit (Editar) y haz clic en un formato diferente.![Selección de markup de wiki](/assets/images/help/wiki/wiki_dropdown_markup.gif) +5. Usa el editor de texto para agregar el contenido de tu página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) +6. Escribe un mensaje de confirmación que describa el nuevo archivo que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) +7. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. + +### Editar páginas wiki + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +4. Desplázate hasta la página que deseas cambiar con la ayuda de la barra lateral wiki. En el ángulo superior derecho de la página, haz clic en **Edite** (Editar). ![Botón de la página para editar wikis](/assets/images/help/wiki/wiki_edit_page_button.png) +5. Usa el editor de texto para editar el contenido de la página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) +6. Escribe un mensaje de confirmación que describa tus cambios. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) +7. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. + +### Agregar o editar páginas wiki localmente + +Las wikis son parte de los repositorios Gift, de manera que puedes hacer cambios localmente y subirlos a tu repositorio mediante un flujo de trabajo de Git. + +#### Clonar wikis en tu computadora + +Cada wiki brinda una manera sencilla de clonar sus contenidos en tu computadora. Puedes clonar el repositorio a tu computadora con la URL proporcionada: + +```shell +$ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git +# Clona la wiki localmente +``` + +Una vez que has clonado la wiki, puedes agregar archivos nuevos, editar los existentes y confirmar tus cambios. Tus colaboradores y tú pueden crear ramas cuando trabajen en wikis, pero solo los cambios que se suban a la rama predeterminada estarán productivos y disponibles para tus lectores. + +### Acerca de los nombres de archivo wiki + +El nombre de archivo determina el título de tu página wiki, y la extensión del archivo determina cómo se presenta el contenido wiki. + +Las wikis usan [nuestra biblioteca Markup de código abierto](https://github.com/github/markup) para convertir el Markup, y este determina qué convertidor usar para una extensión de archivo. Por ejemplo, si denominas un archivo *foo.md* o *foo.markdown*, wiki usará el convertidor Markdown, mientras que un archivo denominado *foo.textile* usará el convertidor Textile. + +No uses los siguientes caracteres en los títulos de tu página wiki: `\ / : * ? " < > |`. Los usuarios en determinados sistemas operativos no podrán trabajar con nombres de archivos que contienen estos caracteres. Asegúrate de escribir tu contenido mediante un idioma de Markup que coincida con la extensión, o tu contenido no se presentará de manera adecuada. diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-support-resources-to-your-project.md b/translations/es-ES/content/github/building-a-strong-community/adding-support-resources-to-your-project.md new file mode 100644 index 0000000000000..619ab2cc4cdd5 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/adding-support-resources-to-your-project.md @@ -0,0 +1,38 @@ +--- +title: Agregar recursos de soporte a tu proyecto +intro: Puedes crear un archivo de SOPORTE para permitir que las personas conozcan nueva maneras de obtener ayuda con tu proyecto. +redirect_from: + - /articles/adding-support-resources-to-your-project +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para dirigir a las personas hasta recursos de soporte específicos, puedes agregar un archivo de SOPORTE a tu raíz de repositorio, `docs` (documentos), o carpeta `.github`. Cuando alguien crea una propuesta en tu repositorio, verá un enlace en el archivo de SOPORTE de tu proyecto. + +![Lineamientos de soporte](/assets/images/help/issues/support_guidelines_in_issue.png) + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Puedes crear recursos de apoyo predeterminados para tu cuenta de organización o de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} + +{% tip %} + +**Sugerencia:** Para ayudar a las personas a buscar sus lineamientos de soporte, puedes vincular tu archivo de SOPORTE desde otros lugares en tu repositorio, como tu [archivo README](/articles/about-readmes/). + +{% endtip %} + +### Agregar recursos de soporte a tu proyecto + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo de nombre del archivo, escribe *SUPPORT.md* (todo en mayúsculas. +4. En la pestaña **Edit new file** (Editar archivo nuevo), agrega la información sobre las personas que pueden obtener soporte para tu proyecto. +5. Para revisar tu archivo de SOPORTE, haz clic en **Preview** (Vista previa). +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} diff --git a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md new file mode 100644 index 0000000000000..e675069e0bfe2 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -0,0 +1,65 @@ +--- +title: Bloquear a un usuario de tu organización +intro: Los propietarios de una organización pueden bloquear a un usuario para eliminar la capacidad del usuario para colaborar en los repositorios de la organización. +redirect_from: + - /articles/blocking-a-user-from-your-organization +versions: + free-pro-team: '*' +--- + +Puedes bloquear a un usuario desde los parámetros de la organización o desde un comentario específico realizado por el usuario. Al bloquear a un usuario en un comentario, puedes elegir si deseas enviar una notificación al usuario explicando que fue bloqueado y por qué. De lo contrario, el usuario no será notificado directamente que ha sido bloqueado. Los usuarios bloqueados aún podrán borrar el contenido existente. + +Cuando bloqueas a un usuario, puedes elegir bloquearlo indefinidamente o durante un período determinado. Si bloqueas a alguien durante un tiempo determinado, estará desbloqueado automáticamente cuando caduque ese período. Si bloqueas a alguien indefinidamente, puedes desbloquearlo manualmente en cualquier momento. Para obtener más información, consulta "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)". + +{% tip %} + +**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. + +{% endtip %} + +Al momento en que bloqueas a un usuario de tu organización: +- El usuario deja de ver los repositorios de la organización +- Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios +- Se borrarán las bifurcaciones del usuario para los repositorios de tu organización +- Se borrarán los votos del usuario sobre los comentarios y debates en los repositorios de tu organización +- El usuario será eliminado como colaborador en los repositorios de tu organización +- Las contribuciones del usuario ya no contarán como tales para ellos en los repositorios de tu organización +- Cualquier repositorio o invitación de la organización pendientes para el usuario bloqueado se cancelará + +Una vez que has bloqueado a un usuario de tu organización, no podrá: +- Realizar referencias cruzadas con repositorios de la organización en comentarios +- Bifurca, observa, fija, o marca con una estrella los repositorios de tu organización + +En los repositorios de tu organización, los usuarios bloqueados tampoco podrán: +- Abrir propuestas +- Envía, cierra, o fusiona las solicitudes de extracción +- Comentar sobre las propuestas, solicitudes de extracción o confirmaciones +- Agregar o editar páginas wiki + +### Bloquear a un usuario en un comentario + +1. Desplázate hasta el comentario cuyo autor deseas bloquear. +2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} (el ícono de kebab horizontal) , después haz clic en **Block user** (Bloquear usuario). ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones de bloqueo del usuario](/assets/images/help/repository/comment-menu-block-user.png) +3. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block user (Bloquear usuario), y selecciona el período que deseas bloquear al usuario. ![Bloquear límite de tiempo en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-from-comment.png) +4. Si deseas ocultar todos los comentarios que realizó el usuario en la organización, selecciona **Hide this user's comments** (Ocultar los comentarios del usuario) y elige un motivo. ![Enviar una notificación en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png) +5. Si te gustaría notificar al usuario sobre el motivo por el que fue bloqueado, selecciona **Send a notification to this user** (Enviar una notificación a este usuario). ![Enviar una notificación en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-send-notification.png) +6. Para bloquear al usuario, haz clic en **Block user from organization** (Bloquear usuario de la organización) o **Block user from organization and send message** (Bloquear usuario de la organización y enviar mensaje). ![Botón Block user (Bloquear usuario)](/assets/images/help/organizations/org-block-user-button-in-comment.png) + +### Bloquear a un usuario en los parámetros de la organización + +1. Para bloquear a un miembro de la organización, primero [elimina al usuario](/articles/removing-a-member-from-your-organization) desde la organización. +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.block_users %} +6. En "Block a user" (Bloquear a un usuario), escribe el nombre de usuario del usuario que deseas bloquear. ![Campo Username (Nombre de usuario)](/assets/images/help/organizations/org-block-username-field.png) +7. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block options (Bloquear opciones), y selecciona el período que deseas bloquear al usuario. ![Menú desplegable con las opciones de bloqueo](/assets/images/help/organizations/org-block-options-menu.png) +8. Haz clic en **Block user** (Bloquear usuario). ![Botón Block (Bloquear)](/assets/images/help/organizations/org-block-user-button.png) + +### Further reading + +- "[Ver usuarios que están bloqueados en tu organización](/articles/viewing-users-who-are-blocked-from-your-organization)" +- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" +- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md new file mode 100644 index 0000000000000..303a6612a9955 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -0,0 +1,79 @@ +--- +title: Bloquear a un usuario de tu cuenta personal +intro: 'Puedes bloquear a un usuario para impedirle el acceso a tu actividad y repositorios y para evitar que te envíe notificaciones.' +redirect_from: + - /articles/blocking-a-user-from-your-personal-account +versions: + free-pro-team: '*' +--- + +### Acerca de bloquear usuarios + +Puedes bloquear a un usuario en los parámetros de tu cuenta o desde el perfil del usuario. {% data variables.product.prodname_dotcom %} no notificará al usuario cuando lo bloquees. Si no deseas contribuir en el mismo proyecto que alguien que has bloqueado, puedes [exhibir una advertencia](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) en cualquier repositorio con contribuciones previas de un usuario bloqueado. Puede que aún veas la actividad de los usuarios bloqueados en los espacios compartidos y los usuarios bloqueados pueden borrar su contenido existente. + +{% tip %} + +**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. + +{% endtip %} + +Cuando bloqueas a un usuario: +- El usuario deja de seguirte +- El usuario deja de observar y deja de fijar tus repositorios +- El usuario no puede unirse a ninguna organización que te pertenezca +- Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios +- Se borran las bifurcaciones del usuario para tus repositorios +- Borras cualquier bifuracación de los repositorios del usuario +- Se borran los votos del usuario en los comentarios o debates de tus repositorios +- El usuario será eliminado como colaborador en los repositorios de tu organización +- Las contribuciones del usuario ya no contarán como tales para ellos en tus repositorios +- Tus contribuciones para los repositorios del usuario bloqueado ya no contarán como tales para ti +- Se te elimina como colaborador en sus repositorios +- Ya no contarás con su patrocinio +- Cualquier invitación de sucesor de una cuenta o repositorio que se haga a o que provenga del usuario bloqueado se cancela + +Después de que hayas bloqueado a un usuario, no podrá: +- Enviarte notificaciones, incluso al [@mencionar](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) tu nombre de usuario +- Los comentarios o ediciones a los informes de problemas o solicitudes de extracción que has creado +- Reaccionar a tus comentarios en reportes de problemas, solicitudes de extracción y confirmaciones +- Seguir o ver tu contenido en el feed de sus actividades +- Se te asigna a los informes de problemas o solicitudes de extracción +- Invitarte para que seas colaborador en sus repositorios +- Invitarte como colaborador en una asesoría de seguridad +- Realizar referencias cruzadas con tus repositorios en comentarios +- Bifurcar, observar, fijar o marcar con estrella a tus repositorios +- Patrocinarte + +En los repositorios que te pertenecen, los usuarios bloqueados tampoco podrán: +- Abrir propuestas +- Envía, cierra, o fusiona las solicitudes de extracción +- Comentar sobre las propuestas, solicitudes de extracción o confirmaciones +- Agregar o editar páginas wiki + +### Bloquear a un usuario en tus parámetros de cuenta + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.blocked_users %} +3. En "Block a user" (Bloquear a un usuario), escribe el nombre de usuario del usuario que deseas bloquear, luego haz clic en **Block user** (Bloquear usuario). ![Campo Username (Nombre de usuario) y botón Block (Bloquear)](/assets/images/help/settings/user-settings-block-user.png) +4. Opcionalmente, para mostrar una advertencia al visitar un repositorio donde un usuario bloqueado es un colaborador, selecciona **Warn me when blocked user is a prior contributor to a repository** (Advertirme cuando un usuario bloqueado es un colaborador anterior del repositorio). ![Opción para advertir sobre usuarios bloqueados](/assets/images/help/settings/warn-block-user.png) + +### Bloquear a un usuario desde su página de perfil + +{% data reusables.profile.user_profile_page_navigation %} +{% data reusables.profile.user_profile_page_block_or_report %} +3. Haz clic en **Block user** (Bloquear usuario). ![Cuadro de modo con opciones para bloquear a un usuario o reportar abusos](/assets/images/help/profile/profile-blockuser.png) + +{% note %} + +Utiliza {% data variables.contact.report_abuse %} para contactarnos si te están acosando. {% data reusables.policies.abuse %} + +{% endnote %} + +### Further reading + +- "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)" +- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" +- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" +- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)" diff --git a/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md b/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md new file mode 100644 index 0000000000000..8dee388baff18 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md @@ -0,0 +1,19 @@ +--- +title: Cambiar permisos de acceso para wikis +intro: 'Solo los colaboradores de los repositorios pueden editar el wiki del mismo predeterminadamente, pero puedes permitir a cualquiera con una cuenta de {% data variables.product.product_name %} para que lo haga.' +product: '{% data reusables.gated-features.wikis %}' +redirect_from: + - /articles/changing-access-permissions-for-wikis +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En Features (Características), quita la marca de selección de **Restrict edits to collaborators only** (Restringir ediciones a colaboradores solamente). ![Edición de restricción de wikis](/assets/images/help/wiki/wiki_restrict_editing.png) + +### Further reading + +- "[Inhabilitar wikis](/articles/disabling-wikis)" diff --git a/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md b/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md new file mode 100644 index 0000000000000..aabfc939ebae1 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md @@ -0,0 +1,12 @@ +--- +title: Colaborar con tu equipo +intro: 'Dentro de una organización, tu equipo puede trabajar en varios proyectos usando los debates de equipo.' +mapTopic: verdadero +redirect_from: + - /articles/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md new file mode 100644 index 0000000000000..79a5977b8a3c5 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md @@ -0,0 +1,79 @@ +--- +title: Configurar las plantillas de reporte de problemas para tu repositorio +intro: Puedes personalizar las plantillas disponibles para los colaboradores para que las utilicen cuando abren un nuevo reporte de problema en tu repositorio. +redirect_from: + - /github/building-a-strong-community/creating-issue-templates-for-your-repository + - /articles/configuring-issue-templates-for-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +{% data reusables.repositories.default-issue-templates %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + +### Crear plantillas de reporte de problemas + +{% endif %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En la sección "Características", en "Propuestas", haz clic en **Configurar plantillas**. ![Botón Start template setup (Comenzar la configuración de plantilla)](/assets/images/help/repository/set-up-templates.png) +4. Usa el menú desplegable Agregar plantilla y haz clic en el tipo de plantilla que deseas crear. ![Menú desplegable Agregar plantilla](/assets/images/help/repository/add-template-drop-down-menu.png) +5. Para acceder a la vista previa o editar la plantilla antes de confirmarla en el repositorio, haz clic en ** Mostrar la vista previa y editar**. ![Botón para mostrar la vista previa y editar](/assets/images/help/repository/preview-and-edit-button.png) +6. Para editar la plantilla, haz clic en {% octicon "pencil" aria-label="The edit icon" %} y escribe en los campos para editar el contenido. ![Botón Issue template edit (Editar plantilla de propuesta)](/assets/images/help/repository/issue-template-edit-button.png) +7. Para establecer automáticamente un título predeterminado para la propuesta, asigna la propuesta a personas que tengan acceso de lectura al repositorio o aplica etiquetas a tu plantilla de propuesta e ingresa estos detalles en "Información adicional opcional". También puedes agregar estos detalles en la plantilla de propuesta con `título`, `etiquetas` o `asignatario` en un formato de texto preliminar en lenguaje YAML. ![Información adicional de plantilla de propuesta](/assets/images/help/repository/additional-issue-template-info.png) +8. Cuando hayas terminado de editar y visualizar la vista previa de tu plantilla, haz clic en **Proponer cambios** en el ángulo superior derecho de la página. ![Botón para proponer cambios](/assets/images/help/repository/propose-changes-button.png) +9. Escribe un mensaje de confirmación que describa los cambios que realizaste. ![Campo para el mensaje de confirmación de la plantilla de propuesta](/assets/images/help/repository/issue-template-commit-message-field.png) +10. Debajo de los campos del mensaje de confirmación, decide si deseas confirmar tu plantilla directamente en la rama predeterminada o si deseas crear una nueva rama y abrir una solicitud de extracción. Para obtener más información acerca de las solicitudes de extracción, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". ![Elecciòn de la plantilla de propuesta para mantener o abrir una solicitud de cambios](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) +11. Haz clic en **Commit changes** (Confirmar cambios). Una vez que estos cambios se fusionen en la rama predeterminada, la plantilla estará disponible para que la usen los colaboradores cuando abran nuevas propuestas en el repositorio. + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +### Configurar el selector de plantillas + +{% data reusables.repositories.issue-template-config %} + +Puedes alentar a los colaboradores para que utilicen plantillas de informe de problemas si configuras el parámetro `blank_issues_enabled` como `false`. Si configuras `blank_issues_enabled` como `true`, las personas podrán abrir un reporte de problema en blanco. + +{% note %} + +**Nota:** Si utilizaste tu flujo de trabajo tradicional para crear manualmente un archivo de `issue_template.md` fy habilitaste el reporte de problemas en blanco en tu archivo de *config.yml* se utilizará la plantilla en `issue_template.md` cuando las personas decidan abrir un reporte de problema en blanco. Si inhabilitas los reportes de problemas en blanco, la plantilla nunca se utilizará. + +{% endnote %} + +Si prefieres recibir ciertos reportes fuera de {% data variables.product.product_name %}, puedes dirigir a las personas a sitios externos con `contact_links`. + +Aquí hay un ejemplo del archivo *config.yml*. + +```shell +blank_issues_enabled: false +contact_links: + - name: {% data variables.product.prodname_gcf %} + url: https://github.community/ + about: Please ask and answer questions here. + - name: {% data variables.product.prodname_dotcom %} Security Bug Bounty + url: https://bounty.github.com/ + about: Please report security vulnerabilities here. +``` + +Tu archivo de configuración personalizará el selector de plantilla cuando el archivo se combina en la rama predeterminada del repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. Teclea `.github/ISSUE_TEMPLATE/config.yml` en el campo de nombre de archivo. ![Nombre de archivo de configuración](/assets/images/help/repository/template-config-file-name.png) +4. Teclea el contenido de tu archivo de configuración en el cuerpo del nuevo archivo. ![Contenido de archivo de configuración](/assets/images/help/repository/template-config-file-content.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} +{% endif %} + +### Further reading + +- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" +- "[Crear de forma manual una plantilla de propuesta única para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)" diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-default-community-health-file.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-default-community-health-file.md new file mode 100644 index 0000000000000..2f5a2850fd9fa --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-default-community-health-file.md @@ -0,0 +1,48 @@ +--- +title: Creando un archivo predeterminado para la salud de la comunidad +intro: 'Puedes crear archivos predeterminados para la salud de la comunidad, como CONTRIBUTING (Contribuciones) y CODE_OF_CONDUCT (Código de conducta). Los archivos predeterminados se utilizarán para cualquier repositorio público propiedad de la cuenta que no contenga su propio archivo de ese tipo.' +redirect_from: + - /articles/creating-a-default-community-health-file-for-your-organization + - /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de los archivos predeterminados del estado de la comunidad + +Puedes agregar archivos de salud de comunidad predeterminados a la raíz de un repositorio público que se llame `.github` y que pertenezca a una cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %}. + +{% data variables.product.product_name %} utilizará y mostrará los archivos predeterminados para cualquier repositorio público que sea propiedad de la cuenta que no tiene su propio archivo de ese tipo en ninguno de los siguientes lugares: +- la raíz del repositorio +- la carpeta `.github` +- la carpeta `docs` + +Por ejemplo, una persona que cree una propuesta o solicitud de extracción en un repositorio público que no tenga su propio archivo CONTRIBUTING verá un enlace al archivo CONTRIBUTING predeterminado. Si un repositorio tiene algún archivo en su propia carpeta de `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, incluyendo plantillas de propuestas o un archivo *config.yml*,{% endif %} no se utilizará nigún contenido de la carpeta predeterminada `.github/ISSUE_TEMPLATE`. + +Los archivos predeterminados no están incluidos en los clones, paquetes ni descargas de repositorios individuales porque se almacenan únicamente en el repositorio `.github`. + +### Tipos de archivos admitidos + +Puedes crear versiones predeterminadas en tu cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %} para los siguientes archivos de salud de la comunidad: + +| Archivo de salud de la comunidad | Descripción | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| *CODE_OF_CONDUCT.md* | Un archivo CODE_OF_CONDUCT define las normas para participar en una comunidad. Para obtener más información, consulta "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} +| *CONTRIBUTING.md* | Un archivo CONTRIBUTING comunica cómo pueden contribuir las personas con tu proyecto. Para obtener más información, consulta la sección "[Configurar lineamientos para los colaboradores del repositorio](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %} +| *FUNDING.yml* | Un archivo FUNDING muestra un botón de patrocinador en tu repositorio para aumentar la visibilidad de las opciones de financiación para tu proyecto de código abierto. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} +| Plantillas de propuestas y solicitudes de cambio{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y *config.yml*{% endif %} | Las plantillas de propuestas y solicitudes de extracción personalizan y estandarizan la información que quieres que incluyan los colaboradores cuando abren propuestas y solicitudes de extracción en tu repositorio. Para obtener más información, consulta la sección "[Acerca de las plantillas de propuestas y solicitudes de extración](/articles/about-issue-and-pull-request-templates/)".{% if currentVersion == "free-pro-team@latest" %} +| *SECURITY.md* | Un archivo SECURITY da indicaciones para informar responsablemente acerca de una vulnerabilidad de seguridad en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)".{% endif %} +| *SUPPORT.md* | Un archivo SOPPORT les permite a las personas conocer las formas de obtener ayuda con tu proyecto. Para obtener más información, consulta "[Agregar recursos de soporte a tu proyecto](/articles/adding-support-resources-to-your-project/)." | + +No puedes crear un archivo de licencia predeterminado. Los archivos de licencia se deben agregar a repositorios individuales, de manera que el archivo se incluirá cuando el proyecto se clone, se coloque dentro de un paquete o se descargue. + +### Crear un repositorio para archivos predeterminados + +{% data reusables.repositories.create_new %} +2. Utiliza el menú desplegable de **Propietario** y selecciona la cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %} para la cual quieras crear archivos predeterminados. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) +3. Escribe **.github** como nombre para tu repositorio y escribe una descripción opcional. ![Crear un campo de repositorio](/assets/images/help/repository/default-file-repository-name.png) +4. Asegúrate de que el estado del repositorio se encuentre configurado en **Público** (los repositorios para los archivos predeterminados no pueden ser privados). ![Botones de selección para seleccionar el estado público o privado](/assets/images/help/repository/create-repository-public-private.png) +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} +7. En el repositorio, crea uno de los archivos admitidos de estado de la comunidad. Las plantillas de propuesta{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y su archivo de configuración{% endif %}deben estar en una carpeta que se llame `.github/ISSUE_TEMPLATE`. Todos los demás archivos admitidos deben estar en la raíz del repositorio. Para obtener más información, consulta "[Crear nuevos archivos](/articles/creating-new-files/)." diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki.md new file mode 100644 index 0000000000000..9b31882292353 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki.md @@ -0,0 +1,35 @@ +--- +title: Crear un pie de página o barra lateral para tu wiki +intro: Puedes agregar una barra lateral o un pie de página personalizados a tu wiki para dar a los lectores más información contextual. +redirect_from: + - /articles/creating-a-footer/ + - /articles/creating-a-sidebar/ + - /articles/creating-a-footer-or-sidebar-for-your-wiki +product: '{% data reusables.gated-features.wikis %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Crear una carpeta + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +3. En la parte inferior de la página, haz clic en **Agregar un pie de página**. ![Sección para agregar el pie de página a la wiki](/assets/images/help/wiki/wiki_add_footer.png) +4. Usa el editor de texto para escribir el contenido que deseas que tenga tu pie de página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png) +5. Ingresa un mensaje de confirmación que describa el pie de página que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) +6. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. + +### Crear una barra lateral + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +3. Haz clic en **Agregar una barra lateral personalizada**. ![Sección para agregar la barra lateral a la wiki](/assets/images/help/wiki/wiki_add_sidebar.png) +4. Usa el editor de texto para agregar el contenido de tu página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png) +5. Ingresa un mensaje de confirmación que describa la barra lateral que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) +6. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. + +### Crear un pie de página o barra lateral de manera local + +Si creas un archivo con el nombre `_Footer.` or `_Sidebar.`, los usaremos para completar el pie de página y la barra lateral de tu wiki, respectivamente. Al igual que cualquier otra página wiki, la extensión que elijas para estos archivos determina cómo los representaremos. diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md new file mode 100644 index 0000000000000..ebe41bf8ca681 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md @@ -0,0 +1,43 @@ +--- +title: Crear una plantilla de solicitud de extracción para tu repositorio +intro: 'Cuando agregas una plantilla de solicitud de extracción a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la solicitud de extracción.' +redirect_from: + - /articles/creating-a-pull-request-template-for-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". + +Puedes crear un subdirectorio *PULL_REQUEST_TEMPLATE/* en alguna de las carpetas admitidas para incluir múltiples plantillas de solicitudes de extracción, y utilizar el parámetro de consulta `template` para especificar la plantilla que completará el cuerpo de la solicitud de extracción. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Puedes crear plantillas predeterminadas de solicitud de cambios para tu cuenta de organización {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} + +### Agregar una plantilla de solicitud de extracción + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo para el nombre del archivo: + - Para hacer que tu plantilla de solicitud de extracción se pueda ver en el directorio raíz del repositorio, nómbrala como `pull_request_template.md`. ![Nuevo nombre de plantilla de solicitud de extracción en un directorio raíz](/assets/images/help/repository/pr-template-file-name.png) + - Para hacer que tu plantilla de solicitud de extracción se pueda ver en el directorio `docs` del repositorio, nómbrala como `docs/pull_request_template.md`. ![Nueva plantilla de solicitud de extracción en un directorio de documentos](/assets/images/help/repository/pr-template-file-name-docs.png) + - Para guardar tu archivo en un directorio oculto, nombra la plantilla de solicitud de extracción `.github/pull_request_template.md`. ![Nueva plantilla de solicitud de extracción en un directorio oculto](/assets/images/help/repository/pr-template-hidden-directory.png) + - Para crear plantillas de solicitud de extracción múltiples y utilizar el parámetro de consulta `template` para especificar una plantilla para completar el cuerpo de la solicitud de extracción, escribe *.github/PULL_REQUEST_TEMPLATE/* y luego, el nombre de tu plantilla de solicitud de extracción. Por ejemplo, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. También puedes almacenar plantillas de solicitud de extracción múltiples en un subdirectorio `PULL_REQUEST_TEMPLATE` dentro de la raíz o directorios `docs/`. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" ![Nueva plantilla de solicitud de extracción múltiple en un directorio oculto](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. En el cuerpo del nuevo archivo, agrega tu plantilla de solicitud de extracción. Puede incluir: + - Una [ referencia a una propuesta relacionada](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) en tu repositorio. + - Una descripción de los cambios propuestos en la solicitud de extracción. + - [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) de la persona o del equipo responsable de revisar los cambios propuestos. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Las plantillas están disponibles para los colaboradores cuando están fusionadas dentro de la rama predeterminada del repositorio. +{% data reusables.files.propose_new_file %} + +### Further reading + +- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" +- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md new file mode 100644 index 0000000000000..4c336298b3895 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Crear un debate del equipo +intro: 'Todo miembro de la organización puede crear una publicación _public_ de un debate del equipo. Para crear una publicación de un debate del equipo _private_, debes ser un miembro del equipo o un propietario de la organización.' +redirect_from: + - /articles/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.team-discussions-permissions %}Para obtener más información, consulta "[Acerca de los debates del equipo](/articles/about-team-discussions)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Escribe un título para el debate del equipo y agrega un comentario para iniciar una conversación. ![Nuevo comentario de los debates del equipo](/assets/images/help/projects/team-discussions-comment.png) +7. También puedes seleccionar si deseas que tu publicación sea privada o pública usando el menú desplegable.![Menú de parámetros de privacidad de los debates del equipo](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. Da clic en **Comentar**. ![Botón Crear nuevo comentario de los debates del equipo](/assets/images/help/projects/team-discussions-comment-button.png) + +### Further reading + + - "[Acerca de los debates del equipo](/articles/about-team-discussions)" + - "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" + - "[Anclar un debate del equipo](/articles/pinning-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md b/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md new file mode 100644 index 0000000000000..3179a58402830 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md @@ -0,0 +1,21 @@ +--- +title: Inhabilitar las wikis +intro: Puedes inhabilitar las wikis de tu repositorio. +product: '{% data reusables.gated-features.wikis %}' +redirect_from: + - /articles/disabling-wikis +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando desactivas una wiki, su contenido se oculta pero no se borra. Si eliges habilitar nuevamente las wikis en el futuro, se restaurarán tus páginas anteriores. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En Características, quita la marca de selección de **Wiki**. ![Casilla de verificación para inhabilitar wikis](/assets/images/help/wiki/wiki_enable_disable.png) + +### Further reading + +- "[Cambiar los permisos de acceso para las wikis](/articles/changing-access-permissions-for-wikis)" diff --git a/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md b/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md new file mode 100644 index 0000000000000..726c01c0a8fde --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md @@ -0,0 +1,15 @@ +--- +title: Documentar tu proyecto con wikis +intro: 'Puedes usar una wiki para compartir información detallada en forma completa acerca de tu proyecto.' +redirect_from: + - /categories/49/articles/ + - /categories/wiki/ + - /articles/documenting-your-project-with-wikis +product: '{% data reusables.gated-features.wikis %}' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000000..0a88ab7ab42c9 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,24 @@ +--- +title: Editar o eliminar un debate de equipo +intro: 'Los miembros de la organización pueden editar o eliminar debates en la página del equipo. Si eres un miembro de la organización, puedes editar o eliminar el debate.' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Haz clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} junto al debate de equipo que deseas editar o eliminar. +7. Da clic en **Editar**. También puedes hacer clic en **Eliminar**. ![Botón Editar debate de equipo](/assets/images/help/projects/edit-team-discussions-button.png) +8. Modifica el título y el comentario del debate de equipo según sea necesario, y haz clic en **Actualizar comentario**. ![Botón Actualizar comentario](/assets/images/help/projects/update-comment-button.png) + +### Further reading + + - "[Acerca de los debates del equipo](/articles/about-team-discussions)" + - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" + - "[Anclar un debate del equipo](/articles/pinning-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/editing-wiki-content.md b/translations/es-ES/content/github/building-a-strong-community/editing-wiki-content.md new file mode 100644 index 0000000000000..a003b102c17b7 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/editing-wiki-content.md @@ -0,0 +1,55 @@ +--- +title: Editar el contenido de una wiki +intro: 'Puedes agregar imágenes y enlaces al contenido de tu wiki y usar algunos de los formatos que admite MediaWiki.' +redirect_from: + - /articles/adding-links-to-wikis/ + - /articles/how-do-i-add-links-to-my-wiki/ + - /articles/how-do-i-add-or-upload-images-to-the-wiki/ + - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki/ + - /articles/how-do-i-add-images-to-my-wiki/ + - /articles/adding-images-to-wikis/ + - /articles/supported-mediawiki-formats/ + - /articles/editing-wiki-content +product: '{% data reusables.gated-features.wikis %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Agregar enlaces + +Puedes crear enlaces en wikis usando el markup estándar admitido por tu página, o usando la sintaxis MediaWiki. Por ejemplo: + +- Si tus páginas se presentan con Markdown, la sintaxis del enlace es `[Link Text](full-URL-of-wiki-page)`. +- Con la sintaxis MediaWiki, la sintaxis del enlace es `[[Link Text|nameofwikipage]]`. + +### Agregar imágenes + +Las wikis pueden presentar imágenes PNG, JPEG y GIF. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +3. Usando la barra lateral de la wiki, dirígete a la página que deseas cambiar y luego haz clic en **Editar**. +4. En la barra de herramientas de la wiki, haz clic en **Imagen**. ![Botón de la wiki Agregar imagen](/assets/images/help/wiki/wiki_add_image.png) +5. En el cuadro de diálogo "Insertar imagen", escribe la URL de la imagen y el texto alternativo (el que usan los motores de búsqueda y los lectores de pantalla). +6. Haz clic en **OK** (aceptar). + +#### Establecer enlaces a las imágenes en un repositorio + +Puedes establecer un enlace a una imagen en un repositorio en {% data variables.product.product_name %} copiando la URL en tu navegador y usándola como la ruta que lleva a la imagen. Por ejemplo, cuando insertas una imagen en tu wiki usando Markdown, la imagen debe verse de la siguiente manera: + + [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] + +### Formatos MediaWiki admitidos + +Independientemente del lenguaje markup en que esté escrita tu página, siempre tendrás una determinada sintaxis MediaWiki disponible. +- Enlaces ([excdepto AsciiDoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)) +- Reglas horizontales mediante `---` +- Entidades simbólicas abreviadas (como `δ` o `€`) + +Por razones de seguridad y rendimiento, algunas sintaxis no son compatibles. +- [Transclusión](https://www.mediawiki.org/wiki/Transclusion) +- Listas de definiciones +- Sangría +- Índice diff --git a/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md new file mode 100644 index 0000000000000..e875b2174f986 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -0,0 +1,23 @@ +--- +title: Fomentar colaboraciones útiles a tu proyecto con etiquetas +intro: Aplica la etiqueta `good first issue` (primera buena propuesta) a las propuestas de tu repositorio para resaltar las oportunidades que las personas tienen para contribuir con tu proyecto. +redirect_from: + - /github/building-a-strong-community/helping-new-contributors-find-your-project-with-labels + - /articles/helping-new-contributors-find-your-project-with-labels +versions: + free-pro-team: '*' +--- + +Puedes aplicar la etiqueta `good first issue` (primera buena propuesta) a las propuestas de tu repositorio público para que las personas puedan encontrarlas cuando busquen por etiquetas. Para obtener más información acerca de buscar por etiquetas, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests/#search-by-label)". + +{% data variables.product.prodname_dotcom %} usa un algoritmo para determinar las propuestas más accesibles en cada repositorio y las hace aparecer en varios lugares en {% data variables.product.prodname_dotcom_the_website %}. Agregar la etiqueta `good first issue` (primera buena propuesta) puede aumentar la probabilidad de que tus propuestas salgan a la luz. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. En la esquina superior derecha, haz clic en **Label** (etiqueta), luego escribe `good first issue` (primera buena propuesta). Haz clic en el nombre de la etiqueta para asociarla con los elementos seleccionados. ![Desplegable de la asignación de los hitos de propuestas](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Further reading + +- "[Acerca de las etiquetas](/articles/about-labels)" +- "[Buscar repositorios](/articles/searching-for-repositories)" diff --git a/translations/es-ES/content/github/building-a-strong-community/index.md b/translations/es-ES/content/github/building-a-strong-community/index.md new file mode 100644 index 0000000000000..548fd88d182d3 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/index.md @@ -0,0 +1,59 @@ +--- +title: Construir una comunidad sólida +intro: 'Más allá de que tu proyecto sea de código abierto o privado, puedes generar un entorno saludable y eficaz para la colaboración.' +redirect_from: + - /categories/building-a-strong-community +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} + {% link_in_list /about-community-management-and-moderation %} + {% link_in_list /about-community-profiles-for-public-repositories %} + {% link_in_list /accessing-a-projects-community-profile %} + {% link_in_list /adding-a-code-of-conduct-to-your-project %} + {% link_in_list /setting-guidelines-for-repository-contributors %} + {% link_in_list /adding-a-license-to-a-repository %} + {% link_in_list /adding-support-resources-to-your-project %} + {% link_in_list /creating-a-default-community-health-file %} + {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} +{% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} + {% link_in_list /about-issue-and-pull-request-templates %} + {% link_in_list /configuring-issue-templates-for-your-repository %} + {% link_in_list /creating-a-pull-request-template-for-your-repository %} + {% link_in_list /manually-creating-a-single-issue-template-for-your-repository %} +{% topic_link_in_list /moderating-comments-and-conversations %} + {% link_in_list /managing-disruptive-comments %} + {% link_in_list /locking-conversations %} + {% link_in_list /limiting-interactions-in-your-repository %} + {% link_in_list /limiting-interactions-for-your-user-account %} + {% link_in_list /limiting-interactions-in-your-organization %} + {% link_in_list /tracking-changes-in-a-comment %} + {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} + {% link_in_list /managing-reported-content-in-your-organizations-repository %} +{% topic_link_in_list /maintaining-your-safety-on-github %} + {% link_in_list /blocking-a-user-from-your-personal-account %} + {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} + {% link_in_list /unblocking-a-user-from-your-personal-account %} + {% link_in_list /blocking-a-user-from-your-organization %} + {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} + {% link_in_list /unblocking-a-user-from-your-organization %} + {% link_in_list /reporting-abuse-or-spam %} +{% topic_link_in_list /documenting-your-project-with-wikis %} + {% link_in_list /about-wikis %} + {% link_in_list /adding-or-editing-wiki-pages %} + {% link_in_list /creating-a-footer-or-sidebar-for-your-wiki %} + {% link_in_list /editing-wiki-content %} + {% link_in_list /viewing-a-wikis-history-of-changes %} + {% link_in_list /changing-access-permissions-for-wikis %} + {% link_in_list /disabling-wikis %} +{% topic_link_in_list /collaborating-with-your-team %} + {% link_in_list /about-team-discussions %} + {% link_in_list /creating-a-team-discussion %} + {% link_in_list /editing-or-deleting-a-team-discussion %} + {% link_in_list /pinning-a-team-discussion %} diff --git a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md new file mode 100644 index 0000000000000..58c63d7a264da --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md @@ -0,0 +1,26 @@ +--- +title: Limitar las interacciones para tu cuenta de usuario +intro: 'Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en todos los repositorios públicos que pertenezcan a tu cuenta de usuario.' +versions: + free-pro-team: '*' +permissions: Cualquiera puede limitar las interacciones de su propia cuenta de usuario. +--- + +### Acerca de los límites de interacción temporales + +Limitar las interacciones para tu cuenta de usuario habilita límites de interacción temporales para todos los repositorios públicos que pertenezcan a tu cuenta de usuario. {% data reusables.community.interaction-limits-restrictions %} + +{% data reusables.community.interaction-limits-duration %} Después de que pase la duración de tu límite, los usuarios pueden reanudar sus actividades normales en tus repositorios públicos. + +{% data reusables.community.types-of-interaction-limits %} + +Cuando habilitas las limitaciones de actividad en toda la organización, no puedes habilitar o inhabilitar los límites de interacción en los repositorios individuales. Para obtener más información sobre limitar la actividad de un repositorio individual, consulta la sección "[Limitr las interacciones en tu repositorio](/articles/limiting-interactions-in-your-repository)". + +También puedes bloquear usuarios. Para obtener más información, consulta la sección "[Bloquear a un usuario desde tu cuenta personal](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)". + +### Limitar las interacciones para tu cuenta de usuario + +{% data reusables.user_settings.access_settings %} +1. En tu barra lateral de configuración de usuario, debajo de "Configuración de moderación", da clic en **Límites de interacción**. ![Pestaña de "límites de interacción" en la barra lateral de la configuración de usuario](/assets/images/help/settings/settings-sidebar-interaction-limits.png) +{% data reusables.community.set-interaction-limit %} + ![Opciones de límites de interacción temporarios](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md new file mode 100644 index 0000000000000..bf666fe131964 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Limitar las interacciones en tu organización +intro: 'Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en todos los repositorios públicos que pertenezcan a tu organización.' +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: Los propietarios de la organización pueden limitar las interacciones en la misma. +--- + +### Acerca de los límites de interacción temporales + +El limitar las interacciones en tu organización habilita los límites de interacción temporal para todos los repositorios públicos que pertenezcan a la organización. {% data reusables.community.interaction-limits-restrictions %} + +{% data reusables.community.interaction-limits-duration %} Después de que pase el periodo de límite, los usuarios pueden reanudar sus actividades normales en los repositorios públicos de tu organización. + +{% data reusables.community.types-of-interaction-limits %} + +Los miembros de la organización no se verán afectados por ninguno de los tipos de límites. + +Cuando habilitas limitaciones de actividad en toda la organización, no puedes habilitar o inhabilitar límites de interacción en los repositorios individuales. Para obtener más información sobre limitar la actividad de un repositorio individual, consulta la sección "[Limitr las interacciones en tu repositorio](/articles/limiting-interactions-in-your-repository)". + +Los propietarios de la organización también pueden bloquear a los usuarios por un periodo específico. Después de que expira el bloqueo, el usuario se desbloquea de manera automática. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/articles/blocking-a-user-from-your-organization)". + +### Limitar las interacciones en tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. Enla barra lateral de configuración de la organización, da clic en **Configuración de moderación**. !["Configuración de moderación" en la barra lateral de configuración de la organización](/assets/images/help/organizations/org-settings-moderation-settings.png) +1. Debajo de "Configuración de moderación", da clic en **Límites de interacción**. !["Límites de interacción" en la barra lateral de configuración de la organización](/assets/images/help/organizations/org-settings-interaction-limits.png) +{% data reusables.community.set-interaction-limit %} + ![Opciones de límites de interacción temporarios](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) + +### Further reading +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" +- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md new file mode 100644 index 0000000000000..7993af791d077 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md @@ -0,0 +1,35 @@ +--- +title: Limitar las interacciones en tu repositorio +intro: 'Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en un repositorio público.' +redirect_from: + - /articles/limiting-interactions-with-your-repository/ + - /articles/limiting-interactions-in-your-repository +versions: + free-pro-team: '*' +permissions: Las personas con permisos administrativos en un repositorio pueden limitar temporalmente las interacciones en el mismo. +--- + +### Acerca de los límites de interacción temporales + +{% data reusables.community.interaction-limits-restrictions %} + +{% data reusables.community.interaction-limits-duration %} Después de que pase el periodo de tu límite, los usuarios pueden reanudar sus actividades normales en tu repositorio. + +{% data reusables.community.types-of-interaction-limits %} + +También puedes habilitar los límites de actividad en todos los repositorios que pertenecen a tu cuenta de usuario o a una organización. Si se habilita un límite a lo largo de la organización o del usuario, no podrás limitar la actividad para los repositorios individuales que pertenezcan a la cuenta. Para obtener más información, consulta las secciones "[Limitar las interacciones para tu cuenta de usuario](/github/building-a-strong-community/limiting-interactions-for-your-user-account)" y "[Limitar las interacciones en tu organización](/github/building-a-strong-community/limiting-interactions-in-your-organization)". + +### Limitar las interacciones en tu repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. En la barra lateral izquierda, da clic en **Configuración de moderación**. !["Configuración de moderación" en la barra lateral de configuración del repositorio](/assets/images/help/repository/repo-settings-moderation-settings.png) +1. Debajo de "Configuración de moderación", da clic en **Límites de interacción**. ![Límites de interacción en los parámetros del repositorio ](/assets/images/help/repository/repo-settings-interaction-limits.png) +{% data reusables.community.set-interaction-limit %} + ![Opciones de límites de interacción temporarios](/assets/images/help/repository/temporary-interaction-limits-options.png) + +### Further reading +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" +- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md b/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md new file mode 100644 index 0000000000000..7127bf595213c --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md @@ -0,0 +1,36 @@ +--- +title: Bloquear conversaciones +intro: 'Los propietarios y colaboradores del repositorio, y las personas con acceso de escritura, pueden bloquear conversaciones sobre propuestas, solicitudes de extracción y confirmaciones de manera permanente o temporal para desactivar una interacción subida de tono.' +redirect_from: + - /articles/locking-conversations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Es adecuado fijar una conversación cuando toda ella carece de comentarios constructivos o cuando viola el código de conducta de tu comunidad{% if currentVersion == "free-pro-team@latest" %} o los [Lineamientos comunitarios](/articles/github-community-guidelines) de GitHub{% endif %}. Cuando bloqueas una conversación, también puedes especificar el motivo, que queda públicamente visible. + +Bloquear una conversación genera un evento de cronología que queda visible para cualquiera que tenga acceso de lectura al repositorio. Sin embargo, el nombre de usuario de la persona que bloqueó la conversación solo lo pueden ver las personas con acceso de escritura al repositorio. Para cualquiera que no tenga acceso de escritura, el evento de cronología es anónimo. + +![Evento de cronología anónimo de una conversación bloqueada](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png) + +Mientras una conversación está bloqueada, solo [las personas con acceso de escritura](/articles/repository-permission-levels-for-an-organization/) y [los propietarios y colaboradores del repositorio](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) pueden agregar, ocultar y eliminar comentarios. + +Para buscar conversaciones bloqueadas en un repositorio que no está archivado, puedes usar los calificadores de búsqueda `is:locked` y `archived:false`. Las conversaciones se bloquean de forma automática en los repositorios archivados. Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". + +1. De manera opcional, escribe un comentario que explique el motivo por el cual estás bloqueando la conversación. +2. En el margen derecho de la propuesta o solicitud de extracción, o por encima del cuadro de comentarios de la página de confirmaciones, haz clic en **Lock conversation** (Bloquear conversación). ![Enlace Lock conversation (Bloquear conversación)](/assets/images/help/repository/lock-conversation.png) +3. De manera opcional, elige el motivo para bloquear la conversación. ![Menú Reason for locking a conversation (Motivo para bloquear una conversación)](/assets/images/help/repository/locking-conversation-reason-menu.png) +4. Lee la información acerca de bloquear conversaciones y haz clic en **Lock conversation on this issue** (Bloquear conversación sobre esta propuesta), **Lock conversation on this pull request** (Bloquear conversación sobre esta solicitud de extracción) o **Lock conversation on this commit** (Bloquear conversación sobre esta confirmación). ![Cuadro de diálogo Confirm lock with a reason (Confirmar bloqueo con motivo)](/assets/images/help/repository/lock-conversation-confirm-with-reason.png) +5. Cuando estés listo para desbloquear la conversación, haz clic en **Unlock conversation** (Desbloquear conversación). ![Enlace Unlock conversation (Anular bloqueo de la conversación)](/assets/images/help/repository/unlock-conversation.png) + +### Further reading + +- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" +- [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} +- "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" +- "[Limitar interacciones en tu repositorio](/github/building-a-strong-community/limiting-interactions-in-your-repository)" +{% endif %} diff --git a/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md b/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md new file mode 100644 index 0000000000000..1f837e60f70dd --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md @@ -0,0 +1,13 @@ +--- +title: Mantener tu seguridad en GitHub +intro: 'Para construir un ambiente seguro y positivo para ti y para la comunidad de tu proyecto en {% data variables.product.prodname_dotcom %}, puedes bloquear y desbloquear a los usuarios y reportar el contenido ofensivo.' +mapTopic: verdadero +redirect_from: + - /articles/encouraging-positive-contributions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/encouraging-positive-contributions-in-your-organization + - /github/building-a-strong-community/encouraging-positive-contributions-to-your-project + - /articles/encouraging-positive-contributions-to-your-project +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/managing-disruptive-comments.md b/translations/es-ES/content/github/building-a-strong-community/managing-disruptive-comments.md new file mode 100644 index 0000000000000..3bf6bdc3c351c --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/managing-disruptive-comments.md @@ -0,0 +1,79 @@ +--- +title: Administrar comentarios negativos +intro: 'Puedes {% if currentVersion == "free-pro-team@latest" %}ocultar, editar, {% else %}editar{% endif %} o borrar comentarios en propuestas, solicitudes de cambios y confirmaciones.' +redirect_from: + - /articles/editing-a-comment/ + - /articles/deleting-a-comment/ + - /articles/managing-disruptive-comments +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Ocultar un comentario + +Cualquiera con acceso de escritura a un repositorio puede ocultar comentarios en reportes de problemas, solicitudes de extracción y confirmaciones. + +Si un comentario está fuera de tema, desactualizado o resuelto, es posible que desees ocultar un comentario para mantener la conversación enfocada o hacer que una solicitud de extracción sea más fácil de navegar o revisar. Los comentarios ocultos se minimizan pero las personas con acceso de lectura a un repositorio puede expandirlos. + +![Contenido minimizado](/assets/images/help/repository/hidden-comment.png) + +1. Navega hasta el comentario que deseas ocultar. +2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, después haz clic en **Hide (Ocultar)**. ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones Editar, Ocultar y Eliminar](/assets/images/help/repository/comment-menu.png) +3. Utilizando el menú desplegable "Choose a reason" (Elige una razón), haz clic en una razón para ocultar el comentario. Después haz clic en **Hide comment (Ocultar comentario)**. + {% if currentVersion == "free-pro-team@latest" %} + ![Elija la razón para ocultar el menú desplegable de comentarios](/assets/images/help/repository/choose-reason-for-hiding-comment.png) + {% else %} + ![Elija la razón para ocultar el menú desplegable de comentarios](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png) + {% endif %} + +### Desocultar un comentario + +Cualquiera con acceso de escritura a un repositorio puede volver a mostrar comentarios sobre reportes de problemas, solicitudes de extracción y confirmaciones. + +1. Navega hasta el comentario que deseas desocultar. +2. En la esquina superior derecha del comentario, haz clic en **{% octicon "fold" aria-label="The fold icon" %} Show comment (Mostrar comentario)**. ![Mostrar el texto del comentario](/assets/images/help/repository/hidden-comment-show.png) +3. En el lateral derecho del comentario expandido, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} (el ícono de kebab horizontal), después **Unhide (Desocultar)**. ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones Editar, Desocultar y Eliminar](/assets/images/help/repository/comment-menu-hidden.png) + +### Editar un comentario + +Cualquiera con acceso de escritura a un repositorio puede editar comentarios sobre reportes de problemas, solicitudes de extracción y confirmaciones. + +Es adecuado editar un comentario y eliminar el contenido que no haga ninguna colaboración con la conversación y viole el código de conducta de tu comunidad{% if currentVersion == "free-pro-team@latest" %} o los [Lineamientos comunitarios](/articles/github-community-guidelines) de GitHub{% endif %}. + +Cuando editas un comentario, toma nota de la ubicación desde la que se ha eliminado el contenido y, de manera opcional, la razón por la que se lo eliminó. + +Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. El menú desplegable **editado** en la parte superior del comentario contiene un historial de las ediciones y muestra el usuario y el registro de horario de cada edición. + +![Comentario con nota adicional que el contenido fue redactado](/assets/images/help/repository/content-redacted-comment.png) + +Los autores de los comentarios y cualquiera con acceso de escritura a un repositorio puede también eliminar información sensible de un historial de edición de los comentarios. Para obtener más información, consulta "[Rastrear los cambios en un comentario](/github/building-a-strong-community/tracking-changes-in-a-comment)". + +1. Navega hasta el comentario que deseas editar. +2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, después haz clic en **Edit (Editar)**. ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones Editar, Ocultar, Eliminar e Informar](/assets/images/help/repository/comment-menu.png) +3. En la ventana de comentario, elimina el contenido que deseas eliminar, después escribe `[REDACTED]` para reemplazarlo. ![Ventana de comentario con contenido redactado](/assets/images/help/issues/redacted-content-comment.png) +4. En la parte inferior del comentario, escribe una nota que indique que has editado el comentario, y de forma opcional, la razón por la que editaste el comentario. ![Ventana de comentario con nota adicional que indica que el contenido fue redactado](/assets/images/help/issues/note-content-redacted-comment.png) +5. Haz clic en **Update comment (Actualizar comentario)**. + +### Eliminar un comentario + +Cualquiera con acceso de escritura a un repositorio puede borrar comentarios sobre reportes de problemas, solicitudes de extracción y confirmaciones. Los propietarios de organizaciones, mantenedores de equipos, y el autor del comentario también pueden borrarlo en la página del equipo. + +Eliminar un comentario es tu último recurso como moderador. Es correcto eliminar un comentario si todo este falla en añadir contenido constructivo a una conversación y viola el código de conducta de tu comunidad{% if currentVersion == "free-pro-team@latest" %} o los [Lineamientos comunitarios](/articles/github-community-guidelines) de GitHub{% endif %}. + +Eliminar un comentario crea un evento cronológico que es visible para todos aquellos que tienen acceso de lectura al repositorio. Sin embargo, el nombre de usuario de la persona que eliminó el comentario solo es visible para personas con acceso de escritura al repositorio. Para cualquiera que no tenga acceso de escritura, el evento de cronología es anónimo. + +![Evento cronológico anónimo para un comentario eliminado](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png) + +Si un comentario contiene algún contenido constructivo que sume a la conversación en cuanto a la propuesta o a la solicitud de extracción, puedes editar el comentario. + +{% note %} + +**Nota:** el comentario inicial (o cuerpo) de una propuesta o solicitud de extracción no puede eliminarse. Por el contrario, pueden editar los cuerpos de la propuesta o de la solicitud de extracción para eliminar el contenido no deseado. + +{% endnote %} + +1. Navega hasta el comentario que deseas eliminar. +2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, después haz clic en **Delete (Eliminar)**. ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones Editar, Ocultar, Eliminar e Informar](/assets/images/help/repository/comment-menu.png) +3. De forma opcional, escribe un comentario señalando que eliminaste un comentario y el porqué. diff --git a/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md b/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md new file mode 100644 index 0000000000000..398864630f101 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md @@ -0,0 +1,21 @@ +--- +title: Administrar la forma en que los colaboradores reportan abusos en el repositorio de tu organización +intro: Puedes permitir que los colaboradores reporten el comportamiento ofensivo directamente a los mantenedores de los repositorios. +versions: + free-pro-team: '*' +--- + +Cualquiera con permisos de administrador en el repositorio puede administrar la forma en la que los colaboradores reportan los abusos en el mismo. + +Puedes habilitar o inhabilitar el contenido para los repositorios públicos que pertenezca a una organización. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.sidebar-moderation-reported-content %} +4. Selecciona o desselecciona **Aceptar reportes de contenido de los colaboradores recientes y anteriores** debajo de "Contenido reportado". ![Casilla para optar por ingresar o salir del contenido reportado en un repositorio](/assets/images/help/repository/reported-content-opt-in-checkbox.png) + +### Further reading + +- "[Administrar el contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)" +- "[Moderar comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" +- "[Acerca de la administración y moderación de la comunidad](/github/building-a-strong-community/about-community-management-and-moderation)" diff --git a/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md b/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md new file mode 100644 index 0000000000000..954ed77e8f891 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md @@ -0,0 +1,44 @@ +--- +title: Administrar el contenido reportado en el repositorio de tu organización +intro: 'Una vez que un colaborador reporta contenido ofensivo en un repositorio, los mantenedores del mismo pueden ver y administrar esta información.' +versions: + free-pro-team: '*' +--- + +Cualquiera con permisos de administrador para un repositorio puede ver y administrar el contenido reportado del mismo. + +### Acerca de la administración del contenido reportado + +Antes de ver o administrar el contenido reportado, debes habilitar esta opción para el repositorio. Para obtener más información, consulta "[Administrar la forma en la que los colaboradores reportan el abuso en el repositorio de tu organización](/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository)." + +Puedes rastrear, clasificar y responder a los reportes de contenido ofensivo. Puedes ver todos los reportes y navegar directamente a cada comentario en {% data variables.product.prodname_dotcom %} dentro del listado de "Reportes de abuso". + +{% data reusables.community.tools-for-moderating %} + +Cuando termines de moderar el contenido ofensivo, puedes marcar el reporte como resuelto. Si decides que aún no has terminado de moderarlo, también puedes marcarlo como no resuelto. + +### Ver el contenido que reportó un colaborador + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.sidebar-moderation-reported-content %} +4. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} al costado derecho del contenido reportado que quieres ver. Posteriormente, da clic en **Ver contenido**. !["Ver contenidot" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-report-view-content.png) + +### Resolver un reporte + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.sidebar-moderation-reported-content %} +4. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} a la derecha del reporte que quieres resolver. Posteriormente, da clic en **Marcar como resuelto**. !["Marcar como resuleto" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-mark-report-as-resolved.png) + +### Marcar un reporte como no resuelto + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.sidebar-moderation-reported-content %} +{% data reusables.repositories.reported-content-resolved-tab %} +5. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} a la derecha del reporte que quisieras marcar como no resuelto. Posteriormente, da clic en **Marcar como no resuelto**. !["Marcar como no resuelto" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-mark-report-as-unresolved.png) + +### Further reading + +- "[Acerca de la administración y moderación de la comunidad](/github/building-a-strong-community/about-community-management-and-moderation)" diff --git a/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md new file mode 100644 index 0000000000000..74ece73aae4c9 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -0,0 +1,71 @@ +--- +title: Crear de forma manual una plantilla de propuesta única para tu repositorio +intro: 'Cuando agregas una plantilla de propuesta creada de forma manual a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la propuesta.' +redirect_from: + - /articles/creating-an-issue-template-for-your-repository/ + - /articles/manually-creating-a-single-issue-template-for-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.legacy-issue-template-tip %} + +Puedes crear un subdirectorio de *ISSUE_TEMPLATE/* (PLANTILLA DE PROPUESTA) en alguna de las carpetas admitidas para incluir múltiples plantillas de propuestas, y utilizar el parámetro de consulta `template` para especificar la plantilla que completará el cuerpo de la propuesta. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" + +Puede añadir texto preliminar de YAML a cada plantilla de reporte de problemas para pre-llenar el título del mismo, añadir etiquetas y personal asignado automáticamente, y asignar un nombre y descripción que se mostrará en el selector de la misma, el cual verán las personas cuando se cree un nuevo reporte de problemas en su repositorio. + +Aquí hay un ejemplo de texto preliminar de YAML. + +``` +--- +nombre: Problema de rastreo +acerca de: Utilice esta plantilla para rastrear nuevas características. +título: "[DATE]: [FEATURE NAME]" +etiquetas: problema de rastreo, necesita clasificación +asignados: octocat +--- +``` +{% note %} + +**Nota:** Si un valor del texto preliminar incluye algún caracter reservado para YAML tal como `:`, deberás poner dicho valor entre comillas íntegramente. Por ejemplo, `":bug: Bug"` o `":new: triage needed, :bug: bug"`. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% data reusables.repositories.valid-community-issues %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +{% data reusables.repositories.default-issue-templates %} + +{% endif %} + +### Agregar una plantilla de propuesta + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo para el nombre del archivo: + - Para que tu plantilla de propuesta sea visible en el directorio raíz del repositorio, escribe el nombre de tu *issue_template* (plantilla de propuesta). Por ejemplo, `issue_template.md`. ![Nuevo nombre de la plantilla de propuesta en un directorio raíz](/assets/images/help/repository/issue-template-file-name.png) + - Para que tu plantilla de propuesta sea visible en el directorio `docs` del repositorio, escribe *docs/* seguido del nombre de tu *issue_template*. Por ejemplo, `docs/issue_template.md`, ![Nueva plantilla de propuesta en el directorio docs](/assets/images/help/repository/issue-template-file-name-docs.png) + - Para almacenar tu archivo en un directorio escondido, escribe *.github/* seguido del nombre de tu *issue_template*. Por ejemplo, `.github/issue_template.md`. ![Nueva plantilla de propuesta en un directorio oculto](/assets/images/help/repository/issue-template-hidden-directory.png) + - Para crear múltiples plantillas de propuestas y utilizar el parámetro de consulta `template` para especificar una plantilla para que complete el cuerpo de la propuesta, escribe *.github/ISSUE_TEMPLATE/*, después el nombre de tu plantilla de propuesta. Por ejemplo, `.github/ISSUE_TEMPLATE/issue_template.md`. Puedes también almacenar múltiples plantillas de propuestas en un subdirectorio `ISSUE_TEMPLATE` dentro de la raíz o directorios `docs/`. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" ![Nueva plantilla de propuesta múltiple en un directorio oculto](/assets/images/help/repository/issue-template-multiple-hidden-directory.png) +4. En el cuerpo del nuevo archivo, agrega tu plantilla de propuesta. Puede incluir: + - Texto preliminar de YAML + - Comportamiento esperado y comportamiento real + - Pasos para reproducir el problema + - Especificaciones como la versión del proyecto, sistema operativo o hardware +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Las plantillas están disponibles para los colaboradores cuando están fusionadas dentro de la rama predeterminada del repositorio. +{% data reusables.files.propose_new_file %} + +### Further reading + +- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" +- "[Configurar las plantillas de reporte de problemas en su repositorio](/articles/configuring-issue-templates-for-your-repository)" +- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Crear una propuesta](/articles/creating-an-issue)" diff --git a/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md b/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md new file mode 100644 index 0000000000000..730a45585a3ed --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md @@ -0,0 +1,12 @@ +--- +title: Moderar comentarios y conversaciones +intro: 'Moderar las conversaciones crea una comunidad amigable para todos los colaboradores de tu proyecto al promover la colaboración saludable y disminuir la intensidad del conflicto. Puedes aplicar el código de conducta de tu comunidad a las discusiones viendo el contenido reportado, editando y eliminando comentarios, y fijando conversaciónes.' +mapTopic: verdadero +redirect_from: + - /articles/moderating-comments-and-conversations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md new file mode 100644 index 0000000000000..8cd3150012d60 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md @@ -0,0 +1,22 @@ +--- +title: Anclar un debate del equipo +intro: 'Puedes anclar debates importantes en las páginas del equipo de tu organización para una referencia fácil, y desanclar debates que ya no son relevantes.' +redirect_from: + - /articles/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. Haz clic en {% octicon "pin" aria-label="The pin icon" %} al lado del debate de equipo que deseas anclar. También puedes desanclar un debate al hacer clic en el ícono. ![Anclar un debate](/assets/images/help/projects/pin-discussion-button.png) + +### Further reading + + - "[Acerca de los debates del equipo](/articles/about-team-discussions)" + - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" + - "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md b/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md new file mode 100644 index 0000000000000..730302da6f483 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md @@ -0,0 +1,64 @@ +--- +title: Informar abuso o spam +intro: Puedes reportar el contenido y comportamientos que violen los lineamientos y condiciones de la comunidad. +redirect_from: + - /articles/reporting-abuse-or-spam +versions: + free-pro-team: '*' +--- + +Los propietarios, colaboradores actuales y previos, y personas con acceso de escritura pueden reportar los comentarios que se hagan en los informes de problemas, solicitudes de extracción y confirmaciones. Cualquier persona puede informar apps en {% data variables.product.prodname_marketplace %}. + +### Acerca de reportar abusos y spam + +{% data reusables.policies.github-community-guidelines-and-terms %} + +Puedes reportar a los usuarios que hayan violado las condiciones de servicio o los lineamientos comunitarios de {% data variables.product.prodname_dotcom %} a través de {% data variables.contact.report_abuse %} o {% data variables.contact.report_content %}. También puedes reportar los comentarios en informes de problemas, solicitudes de extracción y confirmaciones. + +Si se ha habilitado la capacidad para reportar contenido en un repositorio público, también puedes reportarlo directamente a los mantenedores del mismo. + +### Informar un usuario + +{% data reusables.profile.user_profile_page_navigation %} +{% data reusables.profile.user_profile_page_block_or_report %} +3. Haz clic en **Report abuse** (Informar abuso). ![Cuadro de modo con opciones para bloquear a un usuario o reportar abusos](/assets/images/help/profile/profile-report-abuse.png) +4. Completa el formulario de contacto para informarle a {% data variables.contact.contact_support %} sobre el comportamiento del usuario, luego haz clic en **Send request** (Enviar solicitud). + +### Informar una propuesta o solicitud de extracción + +1. Navega hasta la propuesta o solicitud de extracción que quieras informar. +2. En la esquina superior derecha de la propuesta o solicitud de cambios, da clic en +{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} y luego en **Reportar contenido**. + ![Botón para informar un comentario](/assets/images/help/repository/menu-report-issue-or-pr.png) +{% data reusables.community.report-content %} + +### Informar un comentario + +1. Navega hasta el comentario que quieras informar. +2. En la esquina superior derecha del comentario, da clic en +{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} y luego en **Reportar contenido**. +![Menú Kebab con opción para informar un comentario](/assets/images/help/repository/menu-report-comment.png) +{% data reusables.community.report-content %} + +### Informar una app en {% data variables.product.prodname_marketplace %} + +{% data reusables.marketplace.visit-marketplace %} +2. Navega hasta la app que quieras informar. +3. En la barra lateral izquierda, en la sección "Developer links" (Enlaces del programador), haz clic en {% octicon "report" aria-label="The report symbol" %} **Report abuse** (Informar abuso). ![Botón para informar una app en {% data variables.product.prodname_marketplace %}](/assets/images/help/marketplace/marketplace-report-app.png) +4. Completa el formulario de contacto para informarle a {% data variables.contact.contact_support %} sobre el comportamiento de la app, luego haz clic en **Send request** (Enviar solicitud). + +### Reportar abusos en enlaces de contacto dentro del selector de plantillas + +1. Navega al repositorio que contiene el enlace de contacto que deseas reportar. +2. Debajo del nombre del repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Problemas**. +3. En la esquina inferior derecha del selector de plantillas, haz clic en **Report Abuse (Reportar abuso)**. ![Enlace para denunciar un abuso](/assets/images/help/repository/template-chooser-report-abuse.png) +4. Completa el formato de contacto para informar a {% data variables.contact.contact_support %} acerca del comportamiento del enlace, posteriormente, da clic en **Enviar solicitud**. + +### Further reading + +- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" +- [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} +- [Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" +- [Limitar las interacciones en tu repositorio](/github/building-a-strong-community/limiting-interactions-in-your-repository)"{% endif %} +- "[Rastrear cambios en un comentario](/articles/tracking-changes-in-a-comment)" diff --git a/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md new file mode 100644 index 0000000000000..e8f2c5d5f4dec --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -0,0 +1,61 @@ +--- +title: Configurar pautas para los colaboradores de repositorios +redirect_from: + - /articles/how-do-i-set-up-guidelines-for-contributors/ + - /articles/setting-guidelines-for-repository-contributors +intro: Puedes crear pautas para comunicar cómo pueden contribuir las personas a tu proyecto. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para ayudar a los colaboradores de tu proyecto a realizar un buen trabajo, puedes agregar un archivo con las pautas de colaboración a la raíz del repositorio de tu proyecto, carpeta `docs`, o `.github`. Cuando alguien abre una solicitud de extracción o crea una propuesta, verán un enlace a ese archivo. + +![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png) + +Para el propietario del repositorio, las pautas de contribución son una manera de comunicar cómo deben contribuir las personas. + +Para los colaboradores, las pautas los ayudan a verificar que están presentando solicitudes de extracción conformadas correctamente y abriendo propuestas útiles. + +Tanto para los propietarios como para los colaboradores, las pautas de contribución ahorran tiempo y evitan inconvenientes generados por solicitudes de extracción o propuestas creadas de manera incorrecta que deben ser rechazadas o se deben volver a presentar. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Puedes crear lineamientos de colaboración predeterminados para tu cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% endif %} + +{% tip %} + +**Sugerencia:** los mantenedores de repositorios pueden establecer pautas específicas para las propuestas al crear una plantilla de propuesta o de solicitud de extracción para el repositorio. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". + +{% endtip %} + +### Agregar un archivo *CONTRIBUTING* + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. Decide si almacenar tus pautas de contribución en la raíz de tu repositorio, el directorio `docs`, o el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Los nombres de archivos de las pautas de contribución no distinguen entre mayúsculas y minúsculas y pueden tener una extensión *.md* o *.txt*. ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) + - Para hacer visibles tus pautas de contribución en el directorio raíz del repositorio, escribe *CONTRIBUTING*. + - Para hacer visibles tus pautas de contribución en el directorio `docs` del repositorio, escribe *docs/* para crear el nuevo directorio, y luego *CONTRIBUTING*. +4. En el nuevo archivo, agrega las pautas de contribución. Pueden incluir: + - Pasos para crear buenas propuestas o solicitudes de extracción. + - Enlaces a la documentación externa, listas de correos o un código de conducta. + - Expectativas de comportamiento y de la comunidad. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Ejemplos de pautas de contribución + +Si estás confundido, aquí hay algunos buenos ejemplos de pautas de contribución: + +- Pautas de contribución del Editor Atom [](https://github.com/atom/atom/blob/master/CONTRIBUTING.md). +- Pautas de contribución de Ruby on Rails [](https://github.com/rails/rails/blob/master/CONTRIBUTING.md). +- Pautas de contribución de Open Government [](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md). + +### Further reading +- La sección de las Open Source Guides llamada "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% if currentVersion == "free-pro-team@latest" %} +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)"{% endif %} diff --git a/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md b/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md new file mode 100644 index 0000000000000..d5c4b04c0e574 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md @@ -0,0 +1,13 @@ +--- +title: Configurar tu proyecto para contribuciones saludables +intro: 'Los mantenedores del repositorio pueden configurar pautas de contribuciones para ayudar a los colaboradores a hacer contribuciones significativas y útiles a tu proyecto.' +redirect_from: + - /articles/helping-people-contribute-to-your-project/ + - /articles/setting-up-your-project-for-healthy-contributions +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md b/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md new file mode 100644 index 0000000000000..ac5016be872d7 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md @@ -0,0 +1,33 @@ +--- +title: Rastrear cambios en un comentario +intro: Puedes ver el historial de edición para un comentario o eliminar información sensible del mismo. +redirect_from: + - /articles/tracking-changes-in-a-comment +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Ver detalles del historial de edición de un comentario + +Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. + +1. Navega hasta el comentario del que quieres ver el historial de edición. +{% data reusables.repositories.edited-comment-list %} + +### Eliminar información confidencial del historial de un comentario + +Los autores de los comentarios y cualquiera con acceso de escritura aun repositorio pueden borrar comentarios sensibles del historial de edición de los mismos. + +Cuando eliminas información confidencial del historial de edición del comentario, la persona que hizo la edición y el momento en que la hizo siguen visibles en el historial del comentario, pero el contenido de la edición deja de estar disponible. + +1. Navega hasta el comentario del que quieres eliminar la información confidencial del historial de edición. +{% data reusables.repositories.edited-comment-list %} +3. En el margen superior derecho de la ventana del historial de edición, haz clic en **Options** (Opciones). Luego haz clic en **Delete revision from history** (Eliminar revisión del historial) para eliminar la diferencia que muestra el contenido que se agrega. ![Eliminar detalles de edición de un comentario](/assets/images/help/repository/delete-comment-edit-details.png) +4. Para confirmar la eliminación, haz clic en **OK**. + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %}- "[Reportar abuso o spam](/articles/reporting-abuse-or-spam)"{% endif %} +- "[Editar un comentario](/articles/editing-a-comment)" diff --git a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md new file mode 100644 index 0000000000000..9fb751c4a9dc4 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md @@ -0,0 +1,39 @@ +--- +title: Desbloquear un usuario desde tu organización +intro: 'Los propietarios de la organización pueden desbloquear un usuario que se haya bloqueado previamente y restaurar su acceso a los repositorios de la organización.' +redirect_from: + - /articles/unblocking-a-user-from-your-organization +versions: + free-pro-team: '*' +--- + +Después de desbloquear un usuario desde tu organización, este podrá contribuir con los repositorios de tu organización. + +Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se desbloqueará de forma automática cuando termine ese período de tiempo. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/articles/blocking-a-user-from-your-organization)". + +{% tip %} + +**Sugerencia**: Las configuraciones que se hayan eliminado cuando bloqueaste al usuario de tu organización, como el estado de colaborador, las estrellas y las observaciones, no se restaurarán cuando desbloquees al usuario. + +{% endtip %} + +### Desbloquear un usuario en un comentario + +1. Navega hasta el comentario cuyo autor quieres desbloquear. +2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **Unblock user** (Desbloquear usuario). ![Ícono kebab horizontal y menú de moderación de comentarios que muestra la opción de desbloquear usuario](/assets/images/help/repository/comment-menu-unblock-user.png) +3. Para confirmar que quieres desbloquear al usuario, haz clic en **Okay**. + +### Desbloquear un usuario en los parámetros de la organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.block_users %} +5. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png) + +### Further reading + +- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" +- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md new file mode 100644 index 0000000000000..002b28ee44bef --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md @@ -0,0 +1,39 @@ +--- +title: Desbloquear un usuario desde tu cuenta personal +intro: 'Si mejoraste la relación con un {% data variables.product.prodname_dotcom %} usuario que habías bloqueado, puedes desbloquear su cuenta.' +redirect_from: + - /articles/unblocking-a-user-from-your-personal-account +versions: + free-pro-team: '*' +--- + +Cuando desbloqueas un usuario, podrá invitarte a ser colaborador de sus repositorios. Si te [@mention menciona](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) en cualquier parte de GitHub, recibirás notificaciones. + +En los repositorios que te pertenecen, el usuario podrá colaborar con normalidad. + +Puedes desbloquear un usuario en los parámetros de tu cuenta o desde la página de perfil del usuario. + +### Desbloquear a un usuario en tus parámetros de cuenta + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.blocked_users %} +3. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png) + +### Desbloquear un usuario desde su página de perfil + +{% data reusables.profile.user_profile_page_navigation %} +2. En la barra lateral izquierda, debajo de la foto de perfil del usuario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Desbloquear o reportar usuario**. ![Enlace Unblock or report user (Desbloquear o informar usuario)](/assets/images/help/profile/profile-unblock-or-report-user.png) +3. Haz clic en **Unblock user** (Desbloquear usuario). ![Casilla modal con la opción para desbloquear un usuario o informar abuso](/assets/images/help/profile/profile-unblockuser.png) + +{% tip %} + +**Sugerencia**: Las configuraciones que se hayan eliminado cuando bloqueaste al usuario, como el estado de colaborador, las estrellas y las cosas que sigue, no se restaurarán cuando desbloquees al usuario. + +{% endtip %} + +### Further reading + +- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" +- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md b/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md new file mode 100644 index 0000000000000..0ef775da89e1c --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md @@ -0,0 +1,14 @@ +--- +title: Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles +intro: Los mantenedores del repositorio pueden agregar plantillas en un repositorio para ayudar a los contribuyentes a crear propuestas y solicitudes de extracción de alta calidad. +mapTopic: verdadero +redirect_from: + - /github/building-a-strong-community/using-issue-and-pull-request-templates + - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository/ + - /articles/using-issue-and-pull-request-templates +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/building-a-strong-community/viewing-a-wikis-history-of-changes.md b/translations/es-ES/content/github/building-a-strong-community/viewing-a-wikis-history-of-changes.md new file mode 100644 index 0000000000000..d3f7d560e9d84 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/viewing-a-wikis-history-of-changes.md @@ -0,0 +1,45 @@ +--- +title: Ver el historial de cambios de una wiki +intro: 'Debido a que las wikis son repositorios de Git, cada cambio que realices es una confirmación que puedes ver.' +product: '{% data reusables.gated-features.wikis %}' +redirect_from: + - /articles/viewing-a-wiki-s-history-of-changes + - /articles/viewing-a-wikis-history-of-changes +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Ver el historial de una wiki + +El historial de una wiki incluye: +- El usuario que realizó el cambio +- El mensaje de confirmación que proporcionó +- Cuándo se realizó el cambio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-wiki %} +3. Utilizando la barra lateral de wiki, desplázate hasta la página cuyo historial deseas ver. +4. En la parte superior de la wiki, haz clic en el vínculo de revisión. ![Vínculo de revisión de wiki](/assets/images/help/wiki/wiki_revision_link.png) + +### Ver el contenido previo + +En la tabla del historial de wiki, puedes hacer clic en el [hash SHA-1](http://en.wikipedia.org/wiki/SHA-1) (la secuencia de letras y números al extremo derecho) para ver una página de wiki tal como existía en un punto determinado en el tiempo. + +![Número SHA de wiki](/assets/images/help/wiki/wiki_sha_number.png) + +### Comparar dos revisiones + +1. Selecciona dos filas que deseas comparar. +2. En la parte superior de la tabla del historial, haz clic en **Compare Revisions (Comparar revisiones)**. ![Botón de revisiones de comparación de wiki](/assets/images/help/wiki/wiki_compare_revisions.png) +3. Verás una diferencia de los cambios que muestra qué líneas se agregaron, se eliminaron y se modificaron. + +### Revertir los cambios previos + +Puedes únicamente revertir cambios si tienes permiso para editar la wiki. + +1. Selecciona una fila que deseas revertir. +2. En la parte superior de la tabla del historial, haz clic en **Compare Revisions (Comparar revisiones)**. ![Botón de revisiones de comparación de wiki](/assets/images/help/wiki/wiki_compare_revisions.png) +3. Verás una diferencia de los cambios que muestra qué líneas se agregaron, se eliminaron y se modificaron. ![Diferencia de revisión de wiki](/assets/images/help/wiki/wiki_revision_diff.png) +4. Para revertir los cambios más recientes, haz clic en **Revert Changes (Revertir cambios)**. ![Botón para revertir cambios de wiki](/assets/images/help/wiki/wiki_revert_changes.png) diff --git a/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md new file mode 100644 index 0000000000000..268d658492b10 --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Ver usuarios que están bloqueados de tu organización +intro: 'Puedes ver una lista de todos los usuarios a quienes tú u otras personas han bloqueado de tu organización. Si un usuario fue bloqueado durante una cantidad de tiempo específica, puedes ver la cantidad de tiempo durante la cual fue bloqueado.' +redirect_from: + - /articles/viewing-users-who-are-blocked-from-your-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.block_users %} +5. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que fueron bloqueados de tu organización. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users-for-org.png) + +### Further reading + +- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" +- "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)" diff --git a/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md new file mode 100644 index 0000000000000..a98d600660d3d --- /dev/null +++ b/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md @@ -0,0 +1,19 @@ +--- +title: Ver usuarios que has bloqueado de tu cuenta personal +intro: Puedes ver una lista de todos los usuarios que has bloqueado de tu cuenta personal. +redirect_from: + - /articles/viewing-users-you-ve-blocked-from-your-personal-account + - /articles/viewing-users-youve-blocked-from-your-personal-account +versions: + free-pro-team: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.blocked_users %} +3. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que has bloqueado de tu cuenta. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users.png) + +### Further reading + +- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" +- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" +- "[Ver usuarios que están bloqueados en tu organización](/articles/viewing-users-who-are-blocked-from-your-organization)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md new file mode 100644 index 0000000000000..fabf44b6b0384 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -0,0 +1,84 @@ +--- +title: Acerca de las ramas +intro: 'Usa una rama para identificar tareas de desarrollo sin afectar otras ramas en el repositorio. Cada repositorio tiene una rama por defecto y puede tener muchas otras ramas. Puedes fusionar una rama en otra rama usando una solicitud de extracción.' +redirect_from: + - /articles/working-with-protected-branches/ + - /articles/about-branches +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Acerca de las ramas + +Las ramas te permiten desarrollar características, corregir errores, o experimentar con seguridad las ideas nuevas en un área contenida de tu repositorio. + +Siempre puedes crear una rama a partir de otra rama existente. Habitualmente, puedes crear una rama nueva desde la rama predeterminada de tu repositorio. Podrás entonces trabajar en esta rama nueva aislado de los cambios que otras personas hacen al repositorio. A la rama que creas para construir una característica se le conoce como rama de característica o rama de tema. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)". + +También puedes usar una rama para publicar un sitio {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_pages %}](/articles/what-is-github-pages)". + +Debes tener acceso de escritura para un repositorio para crear una rama, abrir una solicitud de extracción o eliminar y restablecer ramas en una solicitud de extracción. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)." + +### Acerca de la rama predeterminada + +{% data reusables.branches.new-repo-default-branch %} La rama predeterminada es la rama que {% data variables.product.prodname_dotcom %} muestra cuando alguien visita tu repositorio. La rama predeterminada también es la rama inicial que Git verifica localmente cuando alguien clona el repositorio. {% data reusables.branches.default-branch-automatically-base-branch %} + +Predeterminadamente, {% data variables.product.product_name %} nombra la rama predeterminada como {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %} en cualquier repositorio nuevo. + +{% data reusables.branches.change-default-branch %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + +{% data reusables.branches.set-default-branch %} + +{% endif %} + +### Trabajando con las ramas + +Una vez que estés satisfecho con tu trabajo, puedes abrir una solicitud de extracción para fusionar los cambios en la rama actual (la rama de *encabezado*) en otra rama (la rama *base*). Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." + +Después de que se ha fusionado o cerrado la solicitud de extracción, puedes borrar la rama de encabezado, dado que ésta ya no se requerirá. Debes tener acceso de escritura en el repositorio para borrar las ramas. No puedes borrar ramas que estén directamente asociadas con solicitudes de extracción abiertas. Para obtener más información, consulta la sección "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% data reusables.pull_requests.retargeted-on-branch-deletion %} +Los siguientes diagramas son un ejemplo de esto. + + Aquí alguien creó una rama llamada `feature1` desde la rama `master`, y desde entonces, has creado una rama llamada `feature2` desde `feature1`. Hay solicitudes de extracción abiertas para ambas ramas. Las flechas indican la rama base actual para cada solicitud de extracción. En este punto, `feature1` es la rama base para `feature2`. Si la solicitud de extracción para `feature2` se fusiona ahora, la rama `feature2` se fusionará en `feature1`. + + ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/branches/pr-retargeting-diagram1.png) + +En el siguiente diagrama, alguien fusionó la solicitud de extracción para `feature1` en la rama `master`, u borraron la rama `feature1`. Como resultado, {% data variables.product.prodname_dotcom %} ha redireccionado automáticamente la solicitud de extracción para `feature2` para que su rama base sea ahora `master`. + + ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/branches/pr-retargeting-diagram2.png) + +Ahora cuando fusiones la solicitud de extracción `feature2`, ésta se fusionará con la rama `master`. +{% endif %} + +### Trabajar con ramas protegidas + +Los administradores de un repositorio pueden activar las protecciones en una rama. Si estás trabajando en una rama que está protegida, no podrás eliminar ni hacer un empuje forzado a la rama. Los administradores de un repositorio además pueden activar varios parámetros de rama protegida para implementar varios flujos de trabajo antes de que se pueda fusionar una rama. + +{% note %} + +**Nota:** Si eres administrador de un repositorio, puedes fusionar las solicitudes de extracción en ramas con las protecciones de rama activadas incluso si la solicitud de extracción no cumple con los requisitos, a menos que las protecciones de rama hayan sido configuradas con "Incluir administradores". + +{% endnote %} + +Para ver si tu solicitud de extracción se puede fusionar, mira en la casilla de fusión en la parte inferior de la pestaña **Conversación** de la solicitud de extracción. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". + +Cuando una rama está protegida: + +- No podrás eliminar ni hacer un empuje forzado a la rama. +- Si las verificaciones de estado requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que todas las pruebas de integración continua (CI) requeridas estén aprobadas. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". +- Si las revisiones de solicitud de extracción requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que se hayan cumplido todos los requisitos en la política de revisión de solicitud de extracción. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". +- Si la revisión requerida de un propietario del código está activada en una rama y una solicitud de extracción modifica un código que tiene un propietario, un propietario del código debe aprobar la solicitud de extracción antes de que se pueda fusionar. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners)." +- Si la firma de confirmación requerida está activada en una rama, no podrás subir ninguna confirmación de cambios a la rama que no esté firmada ni verificada. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +- Si utilizas el editor de conflictos de {% data variables.product.prodname_dotcom %} para arreglar los conflictos de una solicitud de cambios que creaste desde una rama protegida, {% data variables.product.prodname_dotcom %} te ayuda a crear una rama alternativa para la solicitud de cambios para que tu resolución de conflictos se pueda fusionar. Para obtener más información, consulta la sección "[Resolver un conflicto de fusión en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".{% endif %} + +### Further reading + +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" +- "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} +- "[Ramas en resumen](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" en la documentación de Git diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md new file mode 100644 index 0000000000000..51096417d9639 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md @@ -0,0 +1,27 @@ +--- +title: Acerca de los modelos de desarrollo colaborativo +intro: El modo en que usas las solicitudes de extracción depende del tipo de modelo de desarrollo que uses en tu proyecto. +redirect_from: + - /articles/types-of-collaborative-development-models/ + - /articles/about-collaborative-development-models +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Hay dos tipos principales de modelos de desarrollo con los cuales usar las solicitudes de extracción. En el *modelo de bifurcación y extracción*, cualquiera puede bifurcar un repositorio existente y subir los cambios a su bifurcación personal. No necesitas permiso del repositorio fuente para subir información a una bifurcación que sea propiedad del usuario. El mantenedor del proyecto puede extraer los cambios hacia el repositorio de origen. Cuando abres una solicitud de extracción que proponga cambios desde la bifurcación que es propiedad de tu usuario para ramificar en el repositorio fuente (ascendente), puedes permitir que cualquiera con acceso de escritura en éste haga cambios en dicha solicitud. Este modelo es muy usado con los proyectos de código abierto, ya que reduce la cantidad de fricción para los colaboradores nuevos y le permite a las persona trabajar de forma independiente sin una coordinación inicial. + +{% tip %} + +**Sugerencia:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %} + +{% endtip %} + +En el *modelo de repositorio compartido*, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados. + +### Further reading + +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" +- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" +- "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md new file mode 100644 index 0000000000000..fd9fccb66e923 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md @@ -0,0 +1,67 @@ +--- +title: Acerca de comparar ramas en solicitudes de extracción +intro: Las solicitudes de extracción muestran las diferencias para comparar los cambios que haz hecho en tu rama de tema respecto a la rama en la cual quieres fusionar tus cambios. +redirect_from: + - /articles/about-comparing-branches-in-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Cuando creas tu solicitud de extracción, puedes modificar la rama base frente a la cual estás comparando tus cambios. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)". + +{% endnote %} + +Puedes ver los cambios propuestos en una solicitud de extracción en la pestaña Archivos modificados. + +![Pestaña Archivos modificados de la solicitud de extracción](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) + +En lugar de ver las confirmaciones de cambios, puedes ver los cambios propuestos ya que aparecerán en los archivos una vez que se fusiona la solicitud de extracción. Los archivos aparecen en orden alfabético dentro de la pestaña Archivos modificados. Las adiciones a los archivos aparecen en verde y están precedidas por un signo `+`, mientras que el contenido que ha sido eliminado aparece en rojo y está precedido por un signo `-`. + +### Opciones de diferentes vistas + +{% tip %} + +**Sugerencia:** Si te está resultando difícil comprender el contexto de un cambio, puedes hacer clic en **View** (Ver) en la pestaña Files changed (Archivos modificados) para ver el archivo completo con los cambios propuestos. + +{% endtip %} + +Tienes varias opciones para ver una diferencia: +- La vista unificada muestra el contenido actualizado y el existente en conjunto en una vista lineal. +- La vista en dos paneles muestra el contenido viejo de un lado y el contenido nuevo del otro. +- La vista diferencia rica muestra una previsualización de cómo se verán los cambios una vez que se fusione la solicitud de extracción. +- La vista de origen muestra los cambios en el origen sin el formato de la vista diferencia rica. + +También puedes elegir ignorar los cambios de espacio en blanco para obtener una vista más precisa de los cambios sustanciales en una solicitud de extracción. + +![Menú Opciones de visualización de diferencias](/assets/images/help/pull_requests/diff-settings-menu.png) + +Para simplificar la revisión de cambios en una solicitud de cambios grande, puedes filtrar el diff para que solo muestre los tipos de archivo seleccionados, muestre menos archivos de los cuales seas CODEOWNER, oculte archivos que ya hayas visto, u oculte archivos borrados. Para obtener más información, consulta "[Filtrar archivos en una solicitud de extracción por tipo de archivo](/articles/filtering-files-in-a-pull-request)". + + ![Menú desplegable Filtro de archivo](/assets/images/help/pull_requests/file-filter-menu.png) + +### Comparaciones de diferencias de Git de tres puntos y de dos puntos + +Por defecto, las solicitudes de extracción en {% data variables.product.prodname_dotcom %} muestran una diferencia de tres puntos o una comparación entre la versión más reciente de la rama de tema y la confirmación donde la rama de tema fue sincronizada por última vez con la rama base. + +Para ver dos referencias confirmables en una comparación de diferencia de dos puntos en {% data variables.product.prodname_dotcom %}, puedes editar la URL de la página "Comparar cambios" de tu repositorio. Para obtener más información, consulta el [Glosario de Git para "confirmable"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) del sitio del libro _Pro Git_. + +{% data reusables.repositories.two-dot-diff-comparison-example-urls %} + +Una diferenciación de dos puntos compara dos referencias confirmables de Git, como SHA u OID (ID de objeto), directamente entre sí. En {% data variables.product.prodname_dotcom %}, las referencias confirmables de Git en una comparación de diferenciación de dos puntos se deben subir al mismo repositorio o a sus bifurcaciones. + +Si quieres simular una diferenciación de dos puntos en una solicitud de extracción y ver una comparación entre las versiones más recientes de cada rama, puedes fusionar la rama base en tu rama de tema, que actualiza el último antepasado común entre tus ramas. + +Para obtener más información acerca de los comandos de Git para comparar los cambios, consulta "[Opciones de los diffs de Git](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" en el sitio del libro de _Pro Git_. + +### No se mostrarán las diferencias de motivos +- Has excedido el límite total de archivos o de ciertos tipos de archivos. Para obtener más información, consulta "[Límites para ver el contenido y las diferencias en un repositorio](/articles/limits-for-viewing-content-and-diffs-in-a-repository/#diff-limits)". +- Tus archivos coinciden con una regla en el archivo *.gitattributes* del repositorio para bloquear ese archivo de mostrarse por defecto. Para obtener más información, consulta "[Personalizar cómo aparecen los archivos modificados en GitHub](/articles/customizing-how-changed-files-appear-on-github)". + +### Further reading + +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" +- "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md new file mode 100644 index 0000000000000..aaf28586dc992 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -0,0 +1,47 @@ +--- +title: Acerca de las conversaciones en GitHub +intro: 'Puedes debatir cambios y proyectos específicos, así como objetivos de equipos o proyectos más amplios, usando diferentes tipos de debates en {% data variables.product.product_name %}.' +redirect_from: + - /articles/about-discussions-in-issues-and-pull-requests/ + - /articles/about-conversations-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Debates en {% data variables.product.product_name %} + +Puedes crear y participar de propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener. + +Las propuestas son útiles para debatir detalles específicos de un proyecto como registros de errores y mejoras planificadas. Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". Las solicitudes de extracción te permiten comentar directamente en los cambios propuestos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" y "[Comentar en una solicitud de extracción](/articles/commenting-on-a-pull-request)". + +{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)". + +### Reaccionar a las ideas en los comentarios + +Puedes mostrar tu apoyo o tu desacuerdo sobre una idea en una conversación. Cuando agregas una reacción a un comentario o al cuerpo de un debate de equipo, informe de problemas o solicitud de extracción, las personas suscritas a la conversación no recibirán una notificación. Para obtener más información acerca de las suscripciones, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"{% else %}"[Suscribirse y desuscribirse de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}". + +![Ejemplo de una propuesta con reacciones](/assets/images/help/repository/issue-reactions.png) + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Sugerencia:** También puedes agregar reacciones usando tu dispositivo móvil. + +{% endtip %} + +{% endif %} +### Seguir las pautas de contribución + +Antes de abrir una propuesta o solicitud de extracción, comprueba si el repositorio tiene pautas de contribución. El archivo *CONTRIBUTING.md* incluye información acerca de cómo el mantenedor del repositorio quisiera que aportes ideas al proyecto. + +Al igual que las pautas de contribución, el mantenedor del repositorio puede haber incluido una plantilla para información para incluir en una propuesta o solicitud de extracción. Completar las indicaciones desde la plantilla puede ayudarte a obtener una mejor respuesta de los mantenedores. + +### Further reading + +- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" +- [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderar comentarios y conversaciones](/articles/moderating-comments-and-conversations)" +- "[Escribir en {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md new file mode 100644 index 0000000000000..9a73afd63de5a --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md @@ -0,0 +1,34 @@ +--- +title: Acerca de las bifurcaciones +intro: Una bifurcación es una copia de un repositorio que administras. Las bifurcaciones te permiten realizar cambios a un proyecto sin afectar el repositorio original. Puedes recuperar actualizaciones o enviar cambios al repositorio original con solicitudes de extracción. +redirect_from: + - /articles/about-forks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Bifurcar un repositorio es similar a copiar un repositorio, con dos diferencias principales: + +* Puedes utilizar una solicitud de extracción para sugerir cambios desde las bifurcaciones de las cuales sea dueño tu usuario hacia el repositorio original, también conocido como el repositorio *ascendente*. +* Puedes llevar cambios desde tu repositorio ascendente a tu bifurcación local sincronizando tu bifurcación con el repositorio ascendente. + +{% data reusables.repositories.you-can-fork %} + +{% data reusables.repositories.desktop-fork %} + +Eliminar una bifurcación no eliminará el repositorio ascendente original. Puedes hacer cualquier cambio que quieras a tu bifurcación—agregar colaboradores, renombrar archivos, generar {% data variables.product.prodname_pages %}—sin que haya efecto alguno en el original.{% if currentVersion == "free-pro-team@latest" %} No puedes restablecer un repositorio bifurcado que se haya borrado. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)".{% endif %} + +En proyectos de código abierto, las bifurcaciones suelen iterar en ideas o cambios antes de que se presenten al repositorio ascendente. Cuando realizas cambios en la bifurcación que es propiedad de tu usuario y abres una solicitud de extracción que compara tu trabajo con el repositorio ascendente, puedes dar permiso a cualquiera con permiso de escritura en el repositorio ascendente para subir cambios a tu rama de solicitudes de extracción. Esto agiliza la colaboración permitiendo que los mantenedores del repositorio puedan hacer confirmaciones de cambios o ejecutar pruebas locales a tu rama de solicitud de extracción desde una bifurcación propiedad de un usuario antes de fusionarlas. No puedes otorgar permisos de escritura a una bifurcación que sea propiedad de una organización. + +{% data reusables.repositories.private_forks_inherit_permissions %} + +Si quieres crear un repositorio nuevo desde el contenido de uno existente pero no quieres fusionar tus cambios ascendentemente en ocasiones futuras, puedes duplicar el repositorio o, si éste es una plantilla, utilizarlo como plantilla. Para obtener más información, consulta "[Duplicar un repositorio](/articles/duplicating-a-repository)" y [Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". + +### Further reading + +- "[Acerca de los modelos de desarrollo colaborativo](/articles/about-collaborative-development-models)" +- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" +- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md new file mode 100644 index 0000000000000..0163f8753876b --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md @@ -0,0 +1,38 @@ +--- +title: Acerca de los conflictos de fusión +intro: 'Los conflictos de fusión suceden cuando fusionas ramas que tienen confirmaciones de cambios contrapuestas, y Git necesita tu ayuda para decidir qué cambios incorporar en la fusión final.' +redirect_from: + - /articles/about-merge-conflicts +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Por lo general, Git puede resolver las diferencias entre las ramas y fusionarlas automáticamente. Generalmente, los cambios están en diferentes líneas o incluso en diferentes archivos, lo que hace que sea simple para los equipos comprender la fusión. Sin embargo, a veces hay cambios contrapuestos que Git no puede resolver sin tu ayuda. Por lo general, los conflictos de fusión suceden cuando las personas realizan diferentes cambios en la misma línea en el mismo archivo o cuando una persona edita un archivo y otra persona elimina el mismo archivo. + +Debes resolver todos los conflictos de fusión antes de poder fusionar un solicitud de extracción en {% data variables.product.product_name %}. Si tienes un conflicto de fusión entre la rama de comparación y la rama base en tu solicitud de extracción, puedes ver una lista de archivos con cambios conflictivos arriba del botón **Fusionar solicitud de extracción**. El botón **Fusionar solicitud de extracción** se desactiva hasta que hayas resuelto todos los conflictos entre la rama de comparación y la rama base. + +![mensaje de error de conflicto de fusión](/assets/images/help/pull_requests/merge_conflict_error_on_github.png) + +### Resolver conflictos de fusión + +Para resolver un conflicto de fusión, debes editar de forma manual el archivo conflictivo para seleccionar los cambios que quieres mantener en la fusión final. Hay un par de maneras diferentes de resolver un conflicto de fusión: + +- Si tu conflicto de fusión es ocasionado por cambios de líneas contrapuestos, como cuando las personas realizan diferentes cambios en la misma línea del mismo archivo en diferentes ramas en tu repositorio de Git, lo puedes resolver en {% data variables.product.product_name %} usando el editor de conflictos. Para obtener más información, consulta "[Resolver un conflicto de fusión en {% data variables.product.prodname_dotcom %}](/articles/resolving-a-merge-conflict-on-github)". +- Para todos los otros tipos de conflictos de fusión, debes resolver el conflicto de fusión en un clon local del repositorio y subir el cambio a tu rama en {% data variables.product.product_name %}. Puedes usar la línea de comandos o una herramienta como [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) para subir el cambio. Para obtener más información, consulta "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line)". + +Si tienes un conflicto de fusión en la línea de comandos, no puedes subir tus cambios locales a {% data variables.product.product_name %} hasta que resuelvas el conflicto de fusión localmente en tu equipo. Si intentas fusionar ramas en la línea de comandos que tiene un conflicto de fusión, recibirás un mensaje de errror. Para obtener más información, consulta "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line/)". +```shell +$ git merge BRANCH-NAME +> Auto-merging styleguide.md +> CONFLICT (content): Merge conflict in styleguide.md +> Automatic merge failed; fix conflicts and then commit the result +``` + +### Further reading + +- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" +- "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line)" +- "[Resolver un conflicto de fusión en GitHub](/articles/resolving-a-merge-conflict-on-github)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md new file mode 100644 index 0000000000000..c51034324b8c5 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md @@ -0,0 +1,55 @@ +--- +title: Acerca de las fusiones de las solicitudes de extracción +intro: 'Puedes [fusionar solicitudes de extracción](/articles/merging-a-pull-request) conservando todas las confirmaciones de cambios en una rama de característica, combinando todas las confirmaiones en una única confirmación o cambiando de base confirmaciones individuales desde la rama `head` hacia la rama `base`.' +redirect_from: + - /articles/about-pull-request-merge-squashing/ + - /articles/about-pull-request-merges +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pull_requests.default_merge_option %} + +### Combinar y fusionar las confirmaciones de cambios de tus solicitudes de extracción + +{% data reusables.pull_requests.squash_and_merge_summary %} + +#### Mensaje de fusión para una fusión de combinación + +Cuando combinas y fusionas, {% data variables.product.prodname_dotcom %} genera un mensaje de confirmación que puedes cambiar si así lo deseas. El mensaje predeterminado depende de si la solicitud de extracción contiene varias confirmaciones o solo una. + +| Cantidad de confirmaciones | Resumen | Descripción | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | +| Una confirmación | El título del mensaje de confirmación para la confirmación única, seguido de el número de la solicitud de extracción | El cuerpo de texto del mensaje de la confirmación para la confirmación única | +| Más de una confirmación | El título de la solicitud de extracción, seguido por el número de dicha solicitud | Un listado de los mensajes de confirmación para todas las confirmaciones combinadas, en orden cronológico | + +#### Combinar y fusionar una rama extensa + +Si planeas seguir trabajando en la [rama principal](/github/getting-started-with-github/github-glossary#head-branch) de una solicitud de extracción después de que ésta se fusiona, te recomendamos no combinarla y fusionarla. + +Cuando creas una solicitud de extracción, {% data variables.product.prodname_dotcom %} identifica la confirmación más reciente que se encuentre tanto en la rama principal como en la [rama base](/github/getting-started-with-github/github-glossary#base-branch): la confirmación del ancestro común. Cuando combinas y fusionas la solicitud de extracción, {% data variables.product.prodname_dotcom %} crea una confirmación en la rama base que contiene todos los cambios que realizaste en la rama principal desde la confirmación del ancestro común. + +Ya que esta confirmación se realizó únicamente en la rama base y no en la principal, el ancestro común de las dos ramas permanece sin cambios. Si sigues trabajando en la rama principal, entonces crea una solicitud de extracción nueva entre las dos ramas, la solicitud de extracción incluirá todas las confirmaciones que se hayan realizado desde el ancestro común, incluyendo aquellas que combinaste y fusionaste en la solicitud de extracción previa. Si no hay conflictos, puedes fusionar estas confirmaciones con seguridad. Sin embargo, este flujo de trabajo hace que los conflictos de fusión sean más probables. Si sigues combinando y fusionando las solicitudes de extracción para una rama principal extensa, tendrás que resolver los mismos conflictos repetidamente. + +### Cambiar de base y fusionar las confirmaciones de cambios de tus solicitudes de extracción + +{% data reusables.pull_requests.rebase_and_merge_summary %} + +No es posible cambiar de base y fusionar automáticamente en {% data variables.product.product_location %} cuando: +- La solicitud de extracción tiene conflictos de fusión. +- Cambiar de base las confirmaciones desde la rama base a la rama encabezado conlleva a tener conflictos. +- Cambiar de base las confirmaciones se considera "no seguro", como cuando un cambio de base es posible sin conflictos de fusión, pero produciría un resultado diferente del que produciría una fusión. + +Si aún quieres cambiar de base las confirmaciones, pero no puedes cambiar de base y fusionar automáticamente en {% data variables.product.product_location %}, debes hacer lo siguiente: +- Cambiar de base la rama de tema (o rama de encabezado) hacia la rama base de forma local en la línea de comandos. +- [Resolver cualquier conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line/). +- Realizar un empuje forzado de las confirmaciones cambiadas de base a la rama de tema de la solicitud de extracción (o rama de encabezado remota). + +Cualquiera con permisos de escritura en el repositorio, entonces puede [fusionar los cambios](/articles/merging-a-pull-request/) usando el botón Cambiar de base y fusionar en {% data variables.product.product_location %}. + +### Further reading + +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" +- "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md new file mode 100644 index 0000000000000..1179f16b6b403 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -0,0 +1,59 @@ +--- +title: Acerca de las revisiones de solicitudes de extracción +intro: 'Las revisiones le permiten a los colaboradores comentar los cambios propuestos en las solicitudes de extracción, aprobar los cambios o solicitar más cambios antes de que se fusione la solicitud de extracción. Los administradores de repositorio pueden solicitar que todas las solicitudes de extracción sean aprobadas antes de ser fusionadas.' +redirect_from: + - /articles/about-pull-request-reviews +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las revisiones de solicitudes de extracción + +Después de abrir una solicitud de extracción, cualquiera con acceso de *lectura* puede revisar y comentar sobre los cambios propuestos. También puedes sugerir cambios específicos a las líneas de código que el autor puede aplicar directamente desde las solicitud de extracción. Para obtener más información, consulta "[Revisar las modificaciones propuestas en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)." + +Los colaboradores y los propietarios del repositorio pueden solicitar la revisión de una solicitud de extracción por parte de una persona específica. Los miembros de la organización también pueden solicitar la revisión de una solicitud de extracción por parte de un equipo con acceso de lectura al repositorio. Para obtener más información, consulta "[Solicitar la revisión de una solicitud de extracción](/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" %}Puedes especificar un subconjunto de miembros de un equipo para que se asignen automáticamente en lugar de que se haga con todo el equipo. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)".{% endif %} + +Las revisiones permiten el debate de los cambios propuestos y ayudan a asegurarse de que los cambios cumplen con las pautas de contribución del repositorio y otras normas de calidad. Puedes definir qué individuos o equipos poseen ciertos tipos o áreas de código en un archivo CODEOWNERS. Cuando una solicitud de extracción modifica un código que tiene un propietario definido, ese individuo o equipo será solicitado automáticamente como revisor. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners/)". + +{% if currentVersion == "free-pro-team@latest" %}Puedes programar recordatorios para solicitudes de cambios que necesiten revisarse. Para obtener más información, consulta la sección "[ Administrar los recordatorios programados para solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)".{% endif %} + +![Encabezado de revisión solicitando cambios con comentarios en la línea](/assets/images/help/pull_requests/review-header-with-line-comment.png) + +Un revisión tiene tres posibles estado: +- **Comentario**: envía opiniones en general sin aprobar explicitamente los cambios ni solicitar cambios adicionales. +- **Aprobar**: envía opiniones y aprueba la fusión de los cambios propuestos en la solicitud de extracción. +- **Solicitar cambios**: envía opiniones que deben ser abordadas antes de que se pueda fusionar la solicitud de extracción. + +![Imagen de los estados de revisión](/assets/images/help/pull_requests/pull-request-review-statuses.png) + +{% data reusables.repositories.request-changes-tips %} + +Puedes ver todas las revisiones que ha recibido una solicitud de extracción en la cronología de conversaciones y puedes ver las revisiones realizadas por los colaboradores y los propietarios del repositorio en la casilla de fusión de la solicitud de extracción. + +![Imagen de las revisiones en una casilla de fusión](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png) + +{% data reusables.search.requested_reviews_search_tip %} + +{% data reusables.pull_requests.resolving-conversations %} + +### Volver a solicitar una revisión + +{% data reusables.pull_requests.re-request-review %} + +### Revisiones requeridas + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." + +{% tip %} + +**Sugerencia**: De ser necesario, las personas con acceso de *administración* o de *escritura* a un repositorio pueden descartar una revisión de solicitud de extracción. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". + +{% endtip %} + +### Further reading + +- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" +- "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" +- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md new file mode 100644 index 0000000000000..f79f242ed04c6 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md @@ -0,0 +1,72 @@ +--- +title: Acerca de las solicitudes de extracción +intro: 'Las solicitudes de extracción te permiten comentarle a otros acerca de los cambios que has subido a una rama en un repositorio en {% data variables.product.product_name %}. Una vez que se abre una solicitud de extracción, puedes debatir y revisar los posibles cambios con los colaboradores y agregar confirmaciones de seguimientos antes de que tus cambios se fusionen en la rama base.' +redirect_from: + - /articles/using-pull-requests/ + - /articles/about-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las solicitudes de extracción + +{% note %} + +**Nota:** Cuando trabajas con solicitudes de extracción, ten lo siguiente en cuenta: +* Si estás trabajando en el [modelo de repositorio compartido](/articles/about-collaborative-development-models), te recomendamos que uses una rama de tema para tu solicitud de extracción. Si bien puedes enviar solicitudes de extracción desde cualquier rama o confirmación, con una rama de tema puedes subir confirmaciones de seguimiento para actualizar tus cambios propuestos. +* Cuando subas confirmaciones a una solicitud de extracción, no realices un empuje forzado. El empuje forzado puede dañar tu solicitud de extracción. + +{% endnote %} + +Después de inicializar una solicitud de extracción, verás una página de revisión que muestra una descripción general de alto nivel de los cambios entre tu rama (la rama de comparación) y la rama base del repositorio. Puedes agregar un resumen de los cambios propuestos, revisar los cambios hechos por las confirmaciones, agregar etiquetas, hitos y asignatarios, y hacer @mención de equipos o colaboradores individuales. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)". + +Una vez que has creado una solicitud de extracción, puedes subir confirmaciones desde tu rama de tema para agregarlas a tu solicitud de extracción existente. Estas confirmaciones aparecerán en orden cronológico dentro de tu solicitud de extracción y los cambios serán visibles en la pestaña "Archivos modificados". + +Otros colaboradores pueden revisar tus cambios propuestos, agregar comentarios de revisión, contribuir con el debate sobre la solicitud de extracción e incluso agregar confirmaciones a la solicitud de extracción. + +{% if currentVersion == "free-pro-team@latest" %} +Puedes ver información sobre el estado de despliegue actual de la rama y la actividad anterior de despliegue en la pestaña de "Conversación". Para obtener más información, consulta "[Ver la actividad de implementación de un repositorio](/articles/viewing-deployment-activity-for-your-repository)". +{% endif %} + +Una vez que estás conforme con los cambios propuestos, puedes fusionar la solicitud de extracción. Si estás trabajando en un modelo de repositorio compartido, creas una solicitud de extracción y tú o alguien más fusionará tus cambios desde tu rama de característica en la rama base que especificaste en tu solicitud de extracción. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". + +{% data reusables.pull_requests.required-checks-must-pass-to-merge %} + +{% data reusables.pull_requests.close-issues-using-keywords %} + +{% tip %} + +**Tips:** +- Para alternar entre expandir y contraer todos los comentarios de revisión desactualizados en una solicitud de extracción, presiona opciónAltAlty da clic en **Mostrar desactualizados** u **Ocultar desactualizados**. Para conocer más atajos del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)". +- Puedes combinar confirmaciones cuando fusionas una solicitud de extracción para obtener una visión optimizada de los cambios. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/articles/about-pull-request-merges)". + +{% endtip %} + +Puedes visitar tu tablero para encontrar de forma rápida los enlaces a las solicitudes de extracción recientemente actualizadas en las que estás trabajando o estás suscripto. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +### Solicitudes de extracción en borrador + +{% data reusables.gated-features.draft-prs %} + +Cuando creas una solicitud de extracción, puedes elegir crear una solicitud de extracción que está lista para revisión o una solicitud de extracción en borrador. Las solicitudes de extracción en borrador no se pueden fusionar y no se les solicita automáticamentes a los propietarios del código que revisen las solicitudes de extracción en borrador. Para obtener más información acerca de la creación de una solicitud de extracción en borrador, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" y "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)". + +{% data reusables.pull_requests.mark-ready-review %} Puedes convertir una solicitud de extracción en borrador cuando lo desees. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/articles/changing-the-stage-of-a-pull-request)". + +### Diferencias entre confirmaciones en las páginas de comparación y de solicitudes de cambios + +Las páginas de comparación y de solicitudes de cambios utilizan métodos diferentes para calcular el diff de los archivos que cambiaron: + +- Las páginas de comparación muestran el diff entre la punta de la ref de encabezado y el actual ancestro en común (es decir, la base de fusión) del encabezado y de la ref base. +- Las páginas de solicitud de cambios muestran el diff entre la punta de la ref de encabezado y el ancestro común del encabezado y la ref base en el momento en el que la solicitud de cambios se crea. Por consecuencia, la base de fusión que se utilizó para la comparación puede ser diferente. + +### Further reading + +- "[Solicitud de extracción](/articles/github-glossary/#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} +- "[Acerca de las ramas](/articles/about-branches)" +- "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" +- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" +- "[Cerrar una solicitud de extracción](/articles/closing-a-pull-request)" +- "[Eliminar ramas no utilizadas](/articles/deleting-unused-branches)" +- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md new file mode 100644 index 0000000000000..c21da0972d84c --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md @@ -0,0 +1,68 @@ +--- +title: Acerca de las verificaciones de estado +intro: Las verificaciones de estado te permiten saber si tus confirmaciones cumplen con las condiciones establecidas para el repositorio con el que estás colaborando. +redirect_from: + - /articles/about-statuses/ + - /articles/about-status-checks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las verificaciones de estado se basan en procesos externos, como compilaciones de integración continua, que se ejecutan para cada subida que haces a un repositorio. Puedes ver el estado *pendiente*, *aprobado* o *error* de las verificaciones de estado junto a las confirmaciones individuales en tu solicitud de extracción. + +![Listado de confirmaciones y estados](/assets/images/help/pull_requests/commit-list-statuses.png) + +Cualquier persona con permisos de escritura a un repositorio puede determinar el estado de cualquier comprobación de estado en el repositorio. + +Puedes ver el estado general de la última confirmación para una rama en la página de ramas de tu repositorio o en la lista de solicitudes de extracción de tu repositorio. + +{% data reusables.pull_requests.required-checks-must-pass-to-merge %} + +### Tipos de verificaciones de estado en {% data variables.product.product_name %} + +Hay dos tipos de verificaciones de estado en {% data variables.product.product_name %}: + +- Verificaciones +- Estados + +Las _verificaciones_ son diferentes de los _estados_, porque brindan anotaciones por línea, mensajes más detallados y solo están disponibles para el uso con {% data variables.product.prodname_github_app %}s. + +Los propietarios de la organización y los usuarios con acceso de escritura a un repositorio pueden crear verificaciones y estados con la API de {% data variables.product.product_name %}. Para obtener más información, consulta la secciónes "[Verificaciones](/rest/reference/checks)" y "[Estados](/rest/reference/repos#statuses)". + +### Verificaciones + +Cuando se configuran las _verificaciones_ en un repositorio, las solicitudes de extracción tienen una pestaña **Checks** (Verificaciones) en la que puedes ver los resultados detallados de la compilación desde las verificaciones de estado y volver a ejecutar las verificaciones fallidas. + +![Verificaciones de estado dentro de una solicitud de extracción](/assets/images/help/pull_requests/checks.png) + +Cuando una línea específica en una confirmación hace que una verificación falle, verás los detalles acerca de la falla, adevertencia o aviso al lado del código relevante en la pestaña **Archivos** de la solicitud de extracción. + +![Detalles de una verificación de estado](/assets/images/help/pull_requests/checks-detailed.png) + +Puedes navegar entre los resúmenes de las verificaciones para varias confirmaciones en una solicitud de extracción, usando el menú desplegable de la confirmación en la pestaña **Conversación**. + +![Resúmenes de verificación para diferentes confirmaciones en un menú desplegable](/assets/images/help/pull_requests/checks-summary-for-various-commits.png) + +#### Omitir y solicitar verificaciones para confirmaciones individuales + +Cuando un repositorio se configura para que solicite automáticamente las verificaciones para las subidas, puedes elegir omitir las verificaciones para una confirmación indvidual que subes. Cuando un repositorio _no_ se configura para que solicite automáticamente las verificaciones para las subidas, puedes solicitar verificaciones para una confirmación indvidual que subes. Para obtener más información acerca de estas configuraciones, consulta la sección "[Suites de verificación](/rest/reference/checks#update-repository-preferences-for-check-suites)". + +Para omitir o solicitar verificaciones para tu confirmación, agrega una de las siguientes lineas de introducción al final de tu mensaje de confirmación: + +- Para _omitir verificaciones_ para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `skip-checks: true`: + ```shell + $ git commit -m "Update README. + > + > + skip-checks: true + ``` + - Para _solicitar_ verificaciones para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `request-checks: true`: + ```shell + $ git commit -m "Refactor usability tests. + > + > + request-checks: true + ``` + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md new file mode 100644 index 0000000000000..8de582657cba1 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md @@ -0,0 +1,12 @@ +--- +title: Abordar conflictos de fusión +intro: 'Si tus cambios tienen conflictos de fusión con la sucursal de base, debes ocuparte de los conflictos de fusión antes de que puedas fusionarlo con tus cambios de solicitud de extracción.' +mapTopic: verdadero +redirect_from: + - /articles/addressing-merge-conflicts +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md new file mode 100644 index 0000000000000..dff111a472ef6 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -0,0 +1,30 @@ +--- +title: Permitir cambios para una rama de solicitud de extracción creada desde una bifurcación +intro: 'Para tener una mejor colaboración, puedes permitir confirmaciones de cambios en ramas que hayas creado a partir de bifurcaciones de las cuales sea dueño tu usuario.' +redirect_from: + - /articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork +permissions: Las personas con acceso de escritura en el repositorio ascendente de una bifurcación de la cual tu usuario sea dueño pueden confirmar cambios en las ramas bifurcadas. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo los autores de las solicitudes de extracción pueden otorgar permisos a los mantenedores del repositorio ascendente, o a aquellos con acceso de escritura en dicho repositorio, para realizar confirmaciones de cambios en sus solicitudes de extracción para comparar ramas en una bifurcación propiedad de un usuario. Para conocer más sobre los repositorios ascendentes, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". + +Los autores de las solicitudes de extracción pueden otorgar estos permisos antes o después de crear dicha solicitud inicial. desde una bifurcación propiedad de un usuario. Para obtener más información, consulta la sección "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)." + +Puedes establecer permisos de confirmación al crear por primera vez una solicitud de extracción desde una bifurcación. Para obtener más información, consulta la sección "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)." Además, puedes modificar una solicitud de extracción existente para permitir que los mantenedores de un repositorio realicen confirmaciones a tu rama. + +### Habilitar permisos del mantenedor del repositorio en solicitudes de extracción existentes + +1. En {% data variables.product.product_name %}, desplázate hasta la página principal del repositorio ascendente de tu solicitud de extracción. +2. En el nombre del repositorio ascendente, haz clic en {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests** (Solicitudes de extracción). ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png) +3. En la lista de solicitudes de extracción, desplázate hasta la solicitud de extracción en la que deseas realizar las confirmaciones. +{% data reusables.repositories.allow-maintainers-user-forks %} + + ![allow-maintainers-to-make-edits-sidebar-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png) + +### Further reading + +- "[Confirmar cambios en una rama de la solicitud de extracción creada desde una bifurcación](/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md new file mode 100644 index 0000000000000..4ab397fb1982f --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -0,0 +1,38 @@ +--- +title: Aprobar una solicitud de extracción con revisiones requeridas +intro: 'Si tu repositorio requiere revisiones, las solicitud de extracción deben tener un número específico de revisiones de aprobación de personas con permisos de _escritura_ o _administración_ en el repositorio antes de que puedan ser fusionados.' +redirect_from: + - /articles/approving-a-pull-request-with-required-reviews +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." + +Puedes comentar una solicitud de extracción, aprobar los cambios o solicitar mejoras antes de aprobarlas. Para obtener más información, consulta "[Revisar las modificaciones propuestas en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)." + +{% data reusables.search.requested_reviews_search %} + +{% tip %} + +**Sugerencia**: Si una solicitud de extracción que aprobaste ha cambiado significativamente, puedes descartar tu revisión. La solicitud de extracción necesitará una nueva revisión antes de que pueda fusionarse. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". + +{% endtip %} + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} +4. Revisa los cambios en la solicitud de extracción, y opcionalmente, [comenta sobre las líneas específicas](/articles/reviewing-proposed-changes-in-a-pull-request/#starting-a-review). +{% data reusables.repositories.review-changes %} +{% data reusables.repositories.review-summary-comment %} +7. Selecciona **Approve** (Aprobar) para aprobar la fusión de los cambios propuestos en la solicitud de extracción. +{% data reusables.repositories.submit-review %} + +{% data reusables.repositories.request-changes-tips %} + +### Further reading + +- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" +- "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md new file mode 100644 index 0000000000000..265368867fc7d --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -0,0 +1,38 @@ +--- +title: Fusionar una solicitud de cambios automáticamente +intro: 'Puedes incrementar la velocidad de desarrollo si habilitas la fusión automática para una solicitud de cambios para que ésta se fusione automáticamente cuando todos los requisitos de fusión se cumplan.' +product: '{% data reusables.gated-features.auto-merge %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.pull_requests.auto-merge-release-phase %} + +### Acerca de la fusión automática + +Si habilitas la fusión automática para una solicitud de cambios, ésta se fusionará automáticamente cuando se cumplan todas las revisiones requeridas y cuando todas las verificaciones de estado hayan pasado. La fusión automática te evita el esperar a que los requisitos se cumplan para que puedas continuar con otras tareas. + +Antes de que utilices la fusión automática con una solicitud de cambios, esta característica se debe habilitar en el repositorio. Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)". + +Puedes proporcionar retroalimentación sobre la fusión automática si [nos contactas](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). + +### Habilitar la fusión automática + +Las personas con permisos de escritura en un repositorio pueden habilitar la fusión automática para una solicitud de cambios. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +1. En la lista de "Solicitudes de cambios", da clic en aquella que quieras fusionar automáticamente. +1. Opcionalmente, para elegir un método de fusión, selecciona el menú desplegable de **Habilitar fusión automática** y da clic en el método de fusión. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)". ![Menú desplegable de "Habilitar fusión automática"](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png) +1. Da clic en **Habilitar fusión automática**. ![Botón para habilitar la fusión automática](/assets/images/help/pull_requests/enable-auto-merge-button.png) +1. Si eliges los métodos de fusión o de fusión y combinación, teclea un mensaje de confirmación y descripción, y elige la dirección de correo electrónico con la que quieres hacer la confirmación de fusión. ![Campos para ingresar el mensaje de confirmación y descripción y elegir el correo electrónico para hacer la confirmación](/assets/images/help/pull_requests/pull-request-information-fields.png) +1. Da clic en **Confirmar fusión automática**. ![Botón para confirmar la fusión automática](/assets/images/help/pull_requests/confirm-auto-merge-button.png) + +### Inhabilitar la fusión automática + +Las personas con permisos de escritura en un repositorio y los autores de la solicitud de cambios pueden inhabilitar la fusión automática en estas solicitudes. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +1. En la lista de "Solicitudes de cambios", da clic en aquella en la que quieras inhabilitar la fusión automática. +1. En la caja de fusión, da clic en **Inhabilitar la fusión automática**. ![Botón para inhabilitar la fusión automática](/assets/images/help/pull_requests/disable-auto-merge-button.png) diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md new file mode 100644 index 0000000000000..04eb8443365d1 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md @@ -0,0 +1,34 @@ +--- +title: Cambiar la rama base de una solicitud de extracción +intro: 'Una vez abierta una solicitud de extracción, puedes cambiar la rama base para comparar los cambios en la solicitud de extracción frente a una rama diferente.' +redirect_from: + - /articles/changing-the-base-branch-of-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% warning %} + +**Advertencia**: Cuando cambias la rama base de tu solicitud de extracción, algunas confirmaciones se eliminarán de la cronología. La revisión de los comentarios también puede estar desactualizada, ya que es posible que la línea del código a la que el comentario hizo referencia no sea parte de los cambios en la solicitud de extracción. + +{% endwarning %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas modificar. +3. Junto al título de la solicitud de extracción, haz clic en **Edit** (Editar). ![Botón Pull request edit (Edición de solicitud de extracción)](/assets/images/help/pull_requests/pull-request-edit.png) +4. En el menú desplegable de la rama base, seleccione aquella contra la que desea [comparar cambios](/github/committing-changes-to-your-project/comparing-commits#comparing-branches). ![Menú desplegable de la rama base ](/assets/images/help/pull_requests/pull-request-edit-base-branch.png) +5. Lee la información sobre cómo cambiar la rama base y haz clic en **Change base** (Cambiar base). ![Botón de confirmación para cambiar la rama base ](/assets/images/help/pull_requests/pull-request-base-branch-confirm.png) + +{% tip %} + +**Tip:** Cuando abres una solicitud de cambios, {% data variables.product.product_name %} configurará la base en la confirmación que referencie esa rama. Si la rama se actualiza en el futuro, {% data variables.product.product_name %} no actualizará la confirmación de la rama base. + +{% endtip %} + +### Further reading + +- "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" +- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" +- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md new file mode 100644 index 0000000000000..d1ebab6857475 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md @@ -0,0 +1,37 @@ +--- +title: Cambiar la etapa de una solicitud de extracción +intro: 'Puedes marcar una solicitud de cambios como lista para su revisión{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} o convertir una solicitud de cambios en un borrador{% endif %}.' +permissions: Las personas con permisos de escritura en un repositorio y los autores de las solicitudes de extracción pueden cambiar la etapa de dichas solicitudes. +product: '{% data reusables.gated-features.draft-prs %}' +redirect_from: + - /articles/changing-the-stage-of-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Marcar una solicitud como lista para revisión + +{% data reusables.pull_requests.mark-ready-review %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista "Pull requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas marcar como disponibles para revisión. +3. En la caja de fusión, da clic en **Listo para revisión**. ![Botón Ready for review (Disponible para revisión)](/assets/images/help/pull_requests/ready-for-review-button.png) + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +### Convertir una solicitud de extracción en borrador + +Puedes convertir una solicitud de extracción en borrador en cualquier momento. Por ejemplo, si accidentalmente abriste una solicitud de extracción en vez de un borrador, o si recibiste retroalimentación en tu solicitud de extracción, la cual necesitas atender, puedes convertirla en borrador para indicar que requiere más cambios. Nadie puede fusionar la solicitud de extracción hasta que la marques nuevamente como lista para revisión. Las personas que ya se han suscrito a las notificaciones de la solicitud de extracción no podrán darse de baja de éstas cuando la conviertas en borrador. + +{% data reusables.repositories.sidebar-pr %} +2. En las lista de "Solicitudes de extracción", da clic en aquella que quieras convertir en borrador. +3. En la barra lateral derecha, debajo de "Revisores", da clic en **Convertir en borrador**. ![Enlace para convertir en borrador](/assets/images/help/pull_requests/convert-to-draft-link.png) +4. Da clic en **Convertir en borrador**. ![Confirmación de conversión a borrador](/assets/images/help/pull_requests/convert-to-draft-dialog.png) + +{% endif %} + +### Further reading + +- "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md new file mode 100644 index 0000000000000..3edfd6b67d070 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md @@ -0,0 +1,74 @@ +--- +title: Revisar solicitudes de extracción localmente +intro: 'Cuando alguien te manda una solicitud de extracción desde una bifurcación o rama de tu repositorio, puedes fusionarla localmente para resolver un conflicto de fusión o para probar y verificar los cambios antes de fusionarlos en {% data variables.product.product_name %}.' +redirect_from: + - /articles/checking-out-pull-requests-locally +permissions: Cualquiera con acceso de escritura a un repositorio puede extraer una solicitud de extracción remota localmente. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + {% note %} + + **Nota:** Los autores de solicitudes de extracción pueden otorgar permisos a los mantenedores del repositorio ascendente, o a aquellos con acceso de escritura en dicho repositorio, para realizar confirmaciones de cambios en sus solicitudes de extracción para comparar ramas en una bifurcación propiedad de un usuario. Para más información, consulta "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" + + {% endnote %} + +### Modificar una solicitud de extracción activa localmente + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de cambios, da clic en aquella que quieras modificar.{% if currentVersion == "free-pro-team@latest" %} +3. Para elegir dónde te gustaría abrir la solicitud de extracción, selecciona la opción **Abrir con {% octicon "triangle-down" aria-label="The down triangle icon" %}** del menú desplegable y da clic en una de las pestañas. ![Link to access command line pull request instructions](/assets/images/help/pull_requests/open-with-button.png){% else %} +3. En la caja de fusión, da clic en **instrucciones para línea de comandos**. Sigue la secuencia de pasos para disminuir la solicitud de extracción propuesta. ![Enlace para acceder a las instrucciones de la solicitud de extracción de la línea de comando](/assets/images/help/pull_requests/pull_request_show_command_line_merge.png) +4. De manera opcional, para ver los cambios propuestos en {% data variables.product.prodname_desktop %}, da clic en **abrir en {% data variables.product.prodname_desktop %}**. ![Link to open a pull request locally in Desktop](/assets/images/help/desktop/open-pr-in-desktop.png){% endif %} + +### Modificar una solicitud de extracción inactiva localmente + +Si algún autor de una solicitud de extracción no responde a las solicitudes o ha eliminado su bifurcación, dicha solicitud se fusionará de todos modos. Sin embargo, si deseas realizar cambios a una solicitud de extracción y el autor no responde, necesitarás realizar algunos pasos adicionales para actualizar la solicitud de extracción. + +Una vez que se abre una solicitud de extracción, {% data variables.product.product_name %} almacena todos los cambios remotamente. Es decir, Los repositorios cuentan con confirmaciones de cambios en una solicitud de extracción aún antes de que esta solicitud se fusione. Puedes extraer una solicitud y recrearla como tuya. + +Cualquier persona puede trabajar con una solicitud de extracción abierta anteriormente para seguir trabajando en ella, probarla o incluso abrir nuevas solicitud de extracción con cambios adicionales. Sin embargo, solo los colaboradores con acceso de escritura pueden fusionar las solicitudes de extracción. + +{% data reusables.repositories.sidebar-issue-pr %} +2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas fusionar. +3. Busca el número de la ID de la solicitud de extracción inactiva. Esta es la secuencia de dígitos inmediatamente después del título de la solicitud de extracción. ![Número de ID de las solicitudes de extracción](/assets/images/help/pull_requests/pull_request_id_number.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +5. Extrae la referencia de la solicitud de extracción en función de su número de ID, creando una nueva rama en el proceso. + ```shell + $ git fetch origin pull/ID/head:BRANCHNAME + ``` +6. Cambia a la rama nueva que está basada en esta solicitud de extracción: + ```shell + [main] $ git checkout BRANCHNAME + > Switched to a new branch 'BRANCHNAME' + ``` +7. En este punto, puedes hacer lo que desees con esta rama. Puedes ejecutar algunas pruebas locales o fusionar otras ramas en esta rama. +8. Cuando estés listo, puedes subir la rama nueva: + ```shell + [pull-inactive-pull-request] $ git push origin BRANCHNAME + > Counting objects: 32, done. + > Delta compression using up to 4 threads. + > Compressing objects: 100% (26/26), done. + > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. + > Total 29 (delta 8), reused 0 (delta 0) + > To https://{% data variables.command_line.codeblock %}/username/repository.git + > * [new branch] BRANCHNAME -> BRANCHNAME + ``` +9. [Crea una nueva solicitud de extracción](/articles/creating-a-pull-request) con tu nueva rama. + +### Error: Error al subir algunas referencias + +El espacio de nombres remoto de `refs/pull/` es *read-only*. Si intentas subir alguna confirmación allí, verás este error: +```shell +! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref) +error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git' +``` + +{% tip %} + +**Sugerencia:** Cuando alguien elimina o cambia el nombre de una referencia remota, tu espacio de nombre `refs/pull/origin/` local no se verá afectado por las llamadas a `git-remote`. + +{% endtip %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md new file mode 100644 index 0000000000000..0f3d8fba7c517 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md @@ -0,0 +1,21 @@ +--- +title: Cerrar una solicitud de extracción +intro: 'Puedes *cerrar* una solicitud de extracción sin [fusionarla en una rama ascendente] (/articles/merging-a-pull-request). Esto puede resultar útil si los cambios propuestos en la rama ya no son necesarios, o si se ha propuesto otra solución en otra rama.' +redirect_from: + - /articles/closing-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia**: Si abriste una solicitud de extracción con la rama base equivocada, en lugar de cerrarla y abrir una nueva, puedes cambiar la rama base. Para obtener más información, consulta "[Cambiar la rama base de una solicuitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)". + +{% endtip %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas cerrar. +3. En la parte inferior de la solicitud de extracción, debajo del cuadro de comentarios, haz clic en **Close pull request** (Cerrar solicitud de extracción). ![El botón para cerrar las solicitudes de extracción](/assets/images/help/pull_requests/pullrequest-closebutton.png) +4. De forma opcional, [elimina la rama](/articles/deleting-unused-branches). Esto mantiene ordenado el listado de ramas en tu repositorio. diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md new file mode 100644 index 0000000000000..d7bc7b7887ba7 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md @@ -0,0 +1,13 @@ +--- +title: Colaborar en repositorios con características de calidad de código +intro: 'Las características de la calidad del flujo de trabajo como estados, {% if enterpriseServerVersions contains currentVersion %}ganchos de pre-recepción. {% endif %}ramas protegidas y verificación de estado requerida ayudan a los colaboradores a hacer contribuciones que cumplan con las condiciones establecidas por la organización y los administradores del repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/collaborating-on-repositories-with-code-quality-features-enabled/ + - /articles/collaborating-on-repositories-with-code-quality-features +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md new file mode 100644 index 0000000000000..11c3776093842 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md @@ -0,0 +1,59 @@ +--- +title: Comentar en una solicitud de extracción +redirect_from: + - /articles/adding-commit-comments/ + - /articles/commenting-on-the-diff-of-a-pull-request/ + - /articles/commenting-on-differences-between-files/ + - /articles/commenting-on-a-pull-request +intro: 'Luego de abrir una solicitud de extracción en un repositorio, los colaboradores o miembros del equipo pueden comentar sobre la comparación de archivos entre dos ramas especificadas, o dejar comentarios generales en el proyecto en general.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los comentarios de las solicitudes de extracción + +Puedes comentar en la pestaña **Conversation** (Conversación) de una solicitud de extracción para dejar comentarios generales, preguntas o apoyos. También puedes sugerir cambios que el autor de la solicitud de extracción puede aplicar directamente desde tu comentario. + +![Conversación de solicitud de extracción](/assets/images/help/pull_requests/conversation.png) + +También puedes comentar sobre secciones específicas de un archivo en la pestaña **Files changed** (Archivos cambiados) de una solicitud de extracción en forma de comentarios en la línea o como parte de una [revisión de solicitud de extracción](/articles/about-pull-request-reviews). Agregar comentarios en la línea es una gran manera de debatir preguntas sobre la implementación o brindar retroalimentación al autor. + +Para obtener más información sobre cómo agregar comentarios en la línea a una revisión de solicitud de extracción, consulta ["Revisar cambios propuestos en una solicitud de extracción".](/articles/reviewing-proposed-changes-in-a-pull-request) + +{% note %} + +**Nota:** Si respondes una solicitud de extracción por correo electrónico, tu comentario se agregará a la pestaña **Conversation** (Conversación) y no será parte de una revisión de solicitud de extracción. + +{% endnote %} + +Para responder un comentario en la línea que ya existe, deberás ir hasta el comentario en la pestaña **Conversation** (Conversación) o en la pestaña **Files changed** (Archivos modificados) y agregar otro comentario en la línea debajo. + +{% tip %} + +**Tips:** +- Los comentarios de las solicitudes de extracción soportan el mismo [ formato](/categories/writing-on-github) que los comentarios regulares en {% data variables.product.product_name %}, como @menciones, emojis y referencias. +- Puedes [agregar reacciones](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) a los comentarios en las solicitudes de extracción en la pestaña **Files changed** (Archivos cambiados). + +{% endtip %} + +### Agregar comentarios en la línea a una solicitud de extracción + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción en la que deseas dejar los comentarios en la línea. +{% data reusables.repositories.changed-files %} +{% data reusables.repositories.start-line-comment %} +{% data reusables.repositories.type-line-comment %} +{% data reusables.repositories.suggest-changes %} +5. Cuando hayas terminado, haz clic en **Add single comment** (Agregar comentario único). ![Ventana de comentario en línea](/assets/images/help/commits/inline-comment.png) + +Cualquier persona que observe la solicitud de extracción o el repositorio recibirá una notificación de tu comentario. + +{% data reusables.pull_requests.resolving-conversations %} + +### Further reading + +- [Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)" +{% if currentVersion == "free-pro-team@latest" %}- "[Reportar abuso o spam](/articles/reporting-abuse-or-spam)" +{% endif %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md new file mode 100644 index 0000000000000..d5165995bcf4d --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -0,0 +1,89 @@ +--- +title: Confirmar cambios a una rama de solicitud de extracción desde una bifurcación +intro: Puedes confirmar cambios en una rama de solicitud de extracción que se creó desde una bifurcación de tu repositorio con permiso del creador de la solicitud de extracción. +redirect_from: + - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo puedes realizar confirmaciones en las ramas de la solicitud de extracción que: +- están abiertas en un repositorio al que tienes acceso de escritura y que se crearon a partir de una bifurcación de ese repositorio +- se encuentren en una bifurcación propiedad del usuario +- tienes permiso otorgado por parte del creador de la solicitud de extracción +- no tengan [restricciones de rama](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) que te impidan la confirmación + +Solo el usuario que creó la solicitud de extracción puede darte permiso para subir confirmaciones de cambios en la bifurcación de la cual es dueño. Para más información, consulta "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" + +{% note %} + +**Nota:** También puedes realizar confirmaciones a una rama de solicitud de extracción desde una bifurcación de tu repositorio a través de {% data variables.product.product_location %} al crear tu propia copia (o bifurcación) de la bifurcación de tu repositorio y confirmar los cambios en la misma rama de encabezado en la que se crearon los cambios de la solicitud de extracción original. Para conocer algunos lineamientos generales, consulta "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)". + +{% endnote %} + +1. Activado + +{% data variables.product.product_name %}, navega a la página principal de la bifurcación (o copia de tu repositorio) en donde se creó la rama de la solicitud de cambios. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} + {% tip %} + + **Sugerencia:** Si prefieres clonar la bifurcación mediante {% data variables.product.prodname_desktop %}, consulta "[Clonar un repositorio en {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)". + + {% endtip %} +4. Cambia el directorio de trabajo actual a la ubicación donde deseas descargar el directorio clonado. + ```shell + $ cd open-source-projects + ``` +5. Escribe `git clone`, y luego pega la URL que copiaste en el Paso 3. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + ``` +6. Presiona **Enter** (Intro). Se creará tu clon local. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + > Cloning into `FORK-OF-THE-REPOSITORY`... + > remote: Counting objects: 10, done. + > remote: Compressing objects: 100% (8/8), done. + > remove: Total 10 (delta 1), reused 10 (delta 1) + > Unpacking objects: 100% (10/10), done. + ``` + {% tip %} + + **Sugerencia:** El mensaje de error "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" significa que tu directorio de trabajo actual ya contiene un repositorio con el mismo nombre. Para resolver el error, debes clonar la bifurcación en un directorio diferente. + + {% endtip %} +7. Desplázate hasta el nuevo repositorio clonado. + ```shell + $ cd FORK-OF-THE-REPOSITORY + ``` +7. Alterna las ramas para comparar la rama de la solicitud de extracción donde se realizaron los cambios originales. Si te desplazas hasta la solicitud de extracción original, verás la rama de comparación en la parte superior de la solicitud de extracción. ![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) En este ejemplo, la rama de comparación es `test-branch`: + ```shell + $ git checkout test-branch + ``` + + {% tip %} + + **Sugerencia:** Para obtener más información acerca de las ramas de las solicitudes de extracción, con ejemplos incluidos, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)". + + {% endtip %} +8. En este punto, puedes hacer lo que desees con esta rama. Puedes subir confirmaciones nuevas a ella, ejecutar algunas pruebas locales, o fusionar otras ramas en esta rama. Realiza las modificaciones que desees. +9. Una vez que confirmas tus cambios en la rama de encabezado de la solicitud de extracción, puedes subir los cambios a la solicitud original directamente. En este ejemplo, la rama de encabezado es `test-branch`: + ```shell + $ git push origin test-branch + > Counting objects: 32, done. + > Delta compression using up to 4 threads. + > Compressing objects: 100% (26/26), done. + > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. + > Total 29 (delta 8), reused 0 (delta 0) + > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git + > 12da2e9..250e946 test-branch -> test-branch + ``` + +Tus nuevas confirmaciones se reflejarán en la solicitud de extracción original en {% data variables.product.product_location %}. + +### Leer más + +- "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md new file mode 100644 index 0000000000000..f88a6dd70784d --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md @@ -0,0 +1,30 @@ +--- +title: Configurar un remoto para una bifurcación +intro: 'Debes configurar un remoto que apunte al repositorio ascendente en Git para [sincronizar los cambios que realizas en una bifurcación](/articles/syncing-a-fork) con el repositorio original. Esto también te permite sincronizar los cambios en el repositorio original con la bifurcación.' +redirect_from: + - /articles/configuring-a-remote-for-a-fork +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Enumera el repositorio remoto configurado actualmente para tu bifurcación. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. Especifica un nuevo repositorio *ascendente* remoto que se sincronizará con la bifurcación. + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. Verifica el nuevo repositorio ascendente que especificaste para tu bifurcación. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md new file mode 100644 index 0000000000000..4d066ab915193 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md @@ -0,0 +1,33 @@ +--- +title: Crear una solicitud de extracción desde una bifurcación +intro: Puedes crear una solicitud de extracción para proponer cambios que has hecho a una bifurcación de un repositorio ascendente. +redirect_from: + - /articles/creating-a-pull-request-from-a-fork +permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +También puedes otorgar permiso a los mantenedores del repositorio ascendente para subir confirmaciones de cambios en una bifurcación propiedad del usuario. Si tu solicitud de extracción compara tu rama de tema con una rama del repositorio ascendente como la rama base, entonces tu rama de tema también se llamará rama de comparación de la solicitud de extracción. Para obtener más información acerca de las ramas de solicitud de extracción, incluyendo ejemplos, consulta la sección "[Crear una solicitud de extracción](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)." + +{% data reusables.pull_requests.perms-to-open-pull-request %} + +1. Navega al repositorio original de donde creaste tu bifurcación. +{% data reusables.repositories.new-pull-request %} +3. En la página Comparar haz clic en **Comparar entre bifurcaciones**. ![Enlace para comparar entre las bifurcaciones](/assets/images/help/pull_requests/compare-across-forks-link.png) +4. En el menú desplegable de la "rama base", selecciona la rama del repositorio ascendente en donde quieras fusionar los cambios. ![Menús desplegables para elegir la bifurcación y la rama base](/assets/images/help/pull_requests/choose-base-fork-and-branch.png) +5. En el menú desplegable de la "bifurcación principal", selecciona tu bifurcación. Posteriormente, utiliza el menú desplegable de "comparar rama" para seleccionar aquella en la que realizaste los cambios. ![Menús desplegables para elegir la bifurcación del encabezado y la rama de comparación](/assets/images/help/pull_requests/choose-head-fork-compare-branch.png) +{% data reusables.repositories.pr-title-description %} +{% data reusables.repositories.allow-maintainers-user-forks %} + + ![allow-maintainers-to-make-edits-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits.png) +{% data reusables.repositories.create-pull-request %} + +{% data reusables.repositories.asking-for-review %} + +### Further reading + +- "[Trabajar con bifurcaciones](/articles/working-with-forks)" +- "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md new file mode 100644 index 0000000000000..2ba418027f2bc --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md @@ -0,0 +1,80 @@ +--- +title: Crear una solicitud de extracción +intro: 'Crea una solicitud de extracción para proponer y colaborar en los cambios en un repositorio. Estos cambios se proponen en una *rama*, lo cual garantiza que la rama predeterminada contenga únicamente trabajo finalizado y aprobado.' +redirect_from: + - /articles/creating-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Todo usuario que tenga permisos de lectura para un repositorio puede crear una solicitud de extracción, pero tú debes tener permisos de escritura para poder crear una rama. Si deseas crear una rama nueva para tu solicitud de extracción y no tienes permisos de escritura para el repositorio, puedes bifurcar antes el repositorio. Para obtener más información, consulta "[Crear una solicitud de extracción a partir de una bifurcación](/articles/creating-a-pull-request-from-a-fork)" y " +[Acerca de las bifurcaciones](/articles/about-forks)".

    + +Puedes especificar en qué rama deseas fusionar tus cambios cuando creas tu solicitud de extracción. Las solicitudes de extracción solo se pueden abrir entre dos ramas que sean diferentes. + +{% data reusables.pull_requests.perms-to-open-pull-request %} + +{% data reusables.pull_requests.close-issues-using-keywords %} + + + +### Cambiar el rango de la rama y el repositorio de destino + +Predeterminadamente, las solicitudes de cambios se basan en la rama predeterminada del repositorio padre. Para obtener más información, consulta "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." + +Si el repositorio padre predeterminado no es el correcto, puedes cambiar tanto el repositorio padre como la rama con las listas desplegables. También puedes intercambiar tus ramas base y encabezado con las listas desplegables para establecer diferencias entre los puntos de referencia. Las referencias que aparecen aquí deben ser nombres de ramas en tu repositorio GitHub. + +![Ramas para editar la solicitud de extracción](/assets/images/help/pull_requests/pull-request-review-edit-branch.png) + +Cuando pienses en las ramas, recuerda que la *rama base* es **el lugar donde** se deben aplicar los cambios y la *rama encabezado* contiene **los cambios** que deseas que se apliquen. + +Cuando cambias el repositorio base, también puedes cambiar las notificaciones de la solicitud de extracción. Cualquier usuario que pueda subir al repositorio base recibirá una notificación por correo electrónico y verá la nueva solicitud de extracción en su tablero la próxima vez que inicie sesión. + +Cuando cambies alguna información en el rango de la rama, las áreas de vista previa modificadas Confirmar y Campos se actualizarán para mostrar tu nuevo rango. + +{% tip %} + +**Tips**: + +- Usando la vista comparativa, puedes configurar comparaciones en todo el periodo. Para obtener más información, consulta la sección "[Comparar confirmaciones de cambios](/github/committing-changes-to-your-project/comparing-commits)." +- Los mantenedores de proyecto pueden agregar una plantilla de solicitud de extracción para un repositorio. Las plantillas incluyen indicaciones para la información en el cuerpo de una solicitud de extracción. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". + +{% endtip %} + + + +### Crear una solicitud de extracción + +{% tip %} + +**Tip**: También puedes utilizar {% data variables.product.prodname_desktop %} para crear una solicitud de extracción. Para obtener más información, consulta la sección “[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" en la documentación de {% data variables.product.prodname_desktop %}. + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} + +2. En el menú "Branch" (Rama), elige la rama que contiene tus confirmaciones. ![Menú desplegable de ramas](/assets/images/help/pull_requests/branch-dropdown.png) + + {% data reusables.repositories.new-pull-request %} + +4. Usa el menú desplegable de la rama _base_ para seleccionar la rama en la que deseas fusionar tus cambios y luego usa el menú desplegable de la rama de _comparación_ para elegir la rama de tema en la que hiciste los cambios. ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/pull_requests/choose-base-and-compare-branches.png) + + {% data reusables.repositories.pr-title-description %} + + + + {% data reusables.repositories.create-pull-request %} + +{% data reusables.repositories.asking-for-review %} + +Una vez que tu solicitud de extracción ha sido revisada, esta se puede [fusionar en un repositorio](/articles/merging-a-pull-request). + + + +### Further reading + +- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" +- "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" +- "[Agregar propuestas y solicitudes de extracción al tablero de proyecto desde la barra lateral](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md new file mode 100644 index 0000000000000..a2e1152248e98 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -0,0 +1,46 @@ +--- +title: Crear y eliminar ramas en tu repositorio +intro: 'Puedes crear o eliminar ramas directamente en {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-branches-in-a-pull-request/ + - /articles/creating-and-deleting-branches-within-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Cómo crear una rama + +{% data reusables.repositories.navigate-to-repo %} + +1. Opcionalmente, si quieres crear tu nueva rama desde una rama diferente a la predeterminada para el repositorio, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **NUMBER branches** y luego elige otra rama: ![Vínculo de ramas en página de resumen](/assets/images/help/branches/branches-link.png) +1. Haz clic en el menú del selector de ramas. ![menú del selector de ramas](/assets/images/help/branch/branch-selection-dropdown.png) +1. Escribe un nombre único para tu nueva rama y luego selecciona **Crear rama**. ![cuadro de texto de creación de ramas](/assets/images/help/branch/branch-creation-text-box.png) + +### Cómo eliminar una rama + +{% data reusables.pull_requests.automatically-delete-branches %} + +{% note %} + +**Nota:** Si la rama que quieres borrar es la rama predeterminada del repositorio, debes elegir una rama predeterminada nueva antes de borrarla. Para obtener màs informaciòn, consulta la secciòn "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)". + +{% endnote %} + +Si la rama que quieres borrar está asociada con una solicitud de cambios abierta, debes fusionar o cerrar dicha solicitud antes de borrar la rama. Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" o la sección "[Cerrar una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. Desplázate hasta la rama que deseas eliminar y luego haz clic en {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![eliminar la rama](/assets/images/help/branches/branches-delete.png) + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% data reusables.pull_requests.retargeted-on-branch-deletion %} +{% endif %} +Para obtener más información, consulta "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)." + +### Further reading + +- "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)" +- "[Ver las ramas en tu repositorio](/github/administering-a-repository/viewing-branches-in-your-repository)" +- "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md new file mode 100644 index 0000000000000..d141027823bd5 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -0,0 +1,27 @@ +--- +title: Descartar una revisión de una solicitud de extracción +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' +redirect_from: + - /articles/dismissing-a-pull-request-review +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pull_requests.dismiss_review %} +Esto cambia el estado de la revisión, que pasa a ser un comentario de revisión. Cuando descartas una revisión, debes agregar un comentario que explique por qué la descartaste. Tu comentario se agregará a la conversación de la solicitud de extracción. + +{% data reusables.search.requested_reviews_search %} + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +3. En la pestaña "Conversación", desplázate hasta la revisión que deseas descartar y haz clic en {% octicon "chevron-down" aria-label="The down button" %}. ![Icono de comillas angulares en el cuadro de fusión](/assets/images/help/pull_requests/merge_box/pull-request-open-menu.png) +4. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego haz clic en **Descartar revisión**. ![Icono de kebab en el cuadro de fusión](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review.png) +5. Escribe la razón por la que descartas la revisión y luego haz clic en **Descartar revisión**. ![Botón Dismiss review (Descartar revisión)](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review-button.png) + +### Further reading + +- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" +- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" +- "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md new file mode 100644 index 0000000000000..81aac643627d2 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md @@ -0,0 +1,30 @@ +--- +title: Filtrar archivos en una solicitud de extracción +intro: 'Para ayudarte a revisar rápidamente los cambios en una solicitud de extracción grande, puedes filtrar los archivos modificados.' +redirect_from: + - /articles/filtering-files-in-a-pull-request-by-file-type/ + - /articles/filtering-files-in-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes filtrar archivos en una solicitud de cambios por tipo de extensión, tal como `.html` o `.js`, por falta de extensión, propietario del código, o dotfiles. + +{% tip %} + +**Tip:** Para simplificar tu vista de diff de solicitudes de cambios, también puedes ocultar temporalmente los archivos borrados o aquellos archivos que ya hayas visto en el diff de dicha solicitud, desde el menú desplegable de filtro de archivos. + +{% endtip %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas filtrar. +{% data reusables.repositories.changed-files %} +4. Usa el menú desplegable para Filtrar archivos y selecciona, elimina la marca de selección o haz clic en los filtros deseados. ![Opción Filtrar archivos sobre la diferencia de la solicitud de extracción](/assets/images/help/pull_requests/file-filter-option.png) +5. Para borrar la selección de filtro en la pestaña **Archivos modificados** puedes hacer clic en **Borrar**. ![Borrar selección de filtro de archivo](/assets/images/help/pull_requests/clear-file-filter.png) + +### Further reading + +- "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" +- "[Encontrar métodos y funciones modificados en una solicitud de extracción](/articles/finding-changed-methods-and-functions-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md new file mode 100644 index 0000000000000..6a625144b6ad6 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md @@ -0,0 +1,38 @@ +--- +title: Encontrar funciones y métodos cambiados en una solicitud de extracción +intro: 'Puedes encontrar rápidamente los cambios propuestos en un método o función en los archivos *.go*, *.js*, *.ts*, *.py*, *.php*, and *.rb*.' +redirect_from: + - /articles/finding-changed-methods-and-functions-in-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cualquier usuario con acceso de lectura a un repositorio puede ver una lista resumida de los cambios en las funciones y los métodos en determinados archivos o solicitud de extracción. + +La lista resumida de métodos y funciones se crea a partir de estos tipos de archivos compatibles: + - Go + - JavaScript (incluidos Typescript, Flow y otros tipos de JavaScript) + - PHP + - Python + - Ruby + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción en la que deseas encontrar los métodos y funciones modificados. +{% data reusables.repositories.changed-files %} +4. Para ver una lista resumida de los métodos y funciones modificados, haz clic en **Ir a...**. ![Ir al menú desplegable](/assets/images/help/pull_requests/jump-to-menu.png) +5. Selecciona el método o la función cambiada dentro del menú desplegable. También puedes ingresar el nombre del método o la función en los resultados del filtro. ![Filtrar función y métodos](/assets/images/help/pull_requests/filter-function-and-methods.png) + + {% note %} + + **Nota:** Si no encuentras las funciones o los métodos que esperabas, confirma que tu código se compile y no contenga errores. En el menú desplegable aparecen solo las funciones y los métodos modificados en esta solicitud de extracción que se encuentran en los archivos *.go*, *.js*, *.ts*, *.py*, *.php* y *.rb*.. + + {% endnote %} + +6. Serás redireccionado a la primera línea de la función o el método seleccionado. ![ver la función o el método en los archivos modificados](/assets/images/help/pull_requests/view-selected-function-or-method.png) + +### Further reading + +- "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" +- "[Filtrar archivos en una solicitud de extracción por tipo de archivo](/articles/filtering-files-in-a-pull-request-by-file-type)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md new file mode 100644 index 0000000000000..ed9a9a03e8c29 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -0,0 +1,25 @@ +--- +title: Flujo de GitHub +intro: 'En GitHub, utilizamos nuestros productos todos los días y hemos desarrollado un flujo de trabajo para colaborar en proyectos. Para hacer que funcione para equipos, independientemente de su tamaño o conocimiento técnico, nos aseguramos de que cada paso de nuestro flujo de trabajo se pueda completar dentro de la interfaz con base en la web.' +redirect_from: + - /articles/creating-and-editing-files-in-your-repository/ + - /articles/github-flow-in-the-browser/ + - /articles/github-flow +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Seguir el flujo de GitHub + +1. [Crea una rama](/articles/creating-and-deleting-branches-within-your-repository) de un repositorio. +2. [Crea](/articles/creating-new-files), [edita](/articles/editing-files), [renombra](/articles/renaming-a-file), [mueve](/articles/moving-a-file-to-a-new-location) o [elimina](/github/managing-files-in-a-repository/deleting-files-in-a-repository) archivos. +3. [Envía una solicitud de extracción](/articles/creating-a-pull-request) desde tu rama con tus modificaciones propuestas para iniciar un debate. +4. Realiza modificaciones en tu rama, según sea necesario. Tu solicitud de extracción se actualizará de manera automática. +5. [Fusiona la solicitud de extracción](/articles/merging-a-pull-request) una vez que la rama esté lista para ser fusionada. +6. [Organiza](/articles/deleting-unused-branches) tus ramas utilizando el botón de eliminación de la solicitud de extracción o en la página de ramas. + +### Further reading + +- La guía ilustrada para "[Comprender el flujo de GitHub](https://guides.github.com/introduction/flow/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md new file mode 100644 index 0000000000000..9eb540945b31f --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md @@ -0,0 +1,12 @@ +--- +title: Incorporar modificaciones desde una solicitud de extracción +intro: 'Puedes proponer modificaciones para tu trabajo en {% data variables.product.product_name %} a través de solicitudes de extracción. Aprende a crear, administrar y fusionar solicitudes de extracción.' +mapTopic: verdadero +redirect_from: + - /articles/incorporating-changes-from-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md new file mode 100644 index 0000000000000..fe1add0ff4df5 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md @@ -0,0 +1,42 @@ +--- +title: Incorporar comentarios en tu solicitud de extracción +intro: 'Cuando los revisores sugieran cambios en una solicitud de extracción, puedes incorporar automáticamente los cambios a la solicitud de extracción o abrir una propuesta para hacer un seguimiento de las sugerencias que están fuera de alcance.' +redirect_from: + - /articles/incorporating-feedback-in-your-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Aplicar modificaciones sugeridas + +Otras personas pueden sugerir modificaciones específicas a tu solicitud de extracción. Puedes aplicar estas modificaciones sugeridas directamente en una solicitud de extracción si tienes acceso de escritura al repositorio. Si la solicitud de extracción se creó desde una bifurcación, y el autor permitió que los mantenedores realicen ediciones, también puedes aplicar las modificaciones sugeridas si tienes acceso de escritura al repositorio ascendente. Para obtener más información, consulte las secciones"[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)". + +Para incorporar rápidamente más de una de las modificaciones sugeridas en una confirmación simple, también puedes aplicar las modificaciones sugeridas como lote. Aplicar una modificación sugerida o un lote de modificaciones sugeridas genera una confirmación simple en la rama comparada de la solicitud de extracción. + +Cada una de las personas que sugirieron alguna de las modificaciones incluidas en la confirmación será coautora de la confirmación. La persona que aplica las modificaciones sugeridas será coautora y persona que confirma el cambio de la confirmación. Para obtener más información acerca del término "persona que confirma el cambio en Git", consulta "[Principios de Git - Ver el historial de confirmaciones](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History)" desde el sitio del libro _Pro Git_. + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción a la que quieras aplicarle una modificación sugerida. +3. Navega hasta la primera modificación sugerida que quieras aplicar. + - Para aplicar la modificación en su propia confirmación, haz clic en **Commit suggestion** (Confirmar sugerencia). ![Botón Commit suggestion (Confirmar sugerencia)](/assets/images/help/pull_requests/commit-suggestion-button.png) + - Para agregar la sugerencia a un lote de modificaciones, haz clic en **Add suggestion to batch** (Agregar sugerencia a un lote). Continúa agregando las modificaciones sugeridas que quieras incluir en una única confirmación. Cuando hayas terminado de agregar las modificaciones sugeridas, haz clic en **Commit suggestions** (Confirmar sugerencias). ![Botón Add suggestion to batch (Agregar sugerencia al lote)](/assets/images/help/pull_requests/add-suggestion-to-batch.png) +4. En el campo de mensaje de confirmación, escribe un mensaje de confirmación corto y significativo que describa la modificación que le hiciste al archivo o los archivos. ![Campo para mensaje de confirmación](/assets/images/help/pull_requests/suggested-change-commit-message-field.png) +5. Haz clic en **Commit changes.** (Confirmar modificaciones) ![Botón Commit changes (Confirmar cambios)](/assets/images/help/pull_requests/commit-changes-button.png) + +### Volver a solicitar una revisión + +{% data reusables.pull_requests.re-request-review %} + +### Abrir una propuesta para una sugerencia fuera de alcance + +Si alguna persona sugiere cambios para tu solicitud de extracción, y los cambios están fuera del alcance de la solicitud de extracción, puedes abrir una propuesta nueva para hacer el seguimiento de los comentarios. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". + +### Further reading + +- "[Acerca de las revisiones de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" +- "[Revisar los cambios propuestos en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" +- "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" +- "[Solicitar una revisión de solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review)" +- "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md new file mode 100644 index 0000000000000..161d9068d4fd3 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -0,0 +1,65 @@ +--- +title: Colaborar con propuestas y solicitudes de extracción +intro: 'Usa el flujo {% data variables.product.prodname_dotcom %} para hacer el seguimiento y debatir los cambios en las propuestas, luego propone y revisa los cambios en las solicitudes de extracción.' +redirect_from: + - /categories/63/articles/ + - /categories/collaborating/ + - /categories/collaborating-on-projects-using-pull-requests/ + - /categories/collaborating-on-projects-using-issues-and-pull-requests/ + - /categories/collaborating-with-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /overview %} + {% link_in_list /github-flow %} + {% link_in_list /about-collaborative-development-models %} + {% link_in_list /about-conversations-on-github %} +{% topic_link_in_list /working-with-forks %} + {% link_in_list /about-forks %} + {% link_in_list /configuring-a-remote-for-a-fork %} + {% link_in_list /syncing-a-fork %} + {% link_in_list /merging-an-upstream-repository-into-your-fork %} + {% link_in_list /allowing-changes-to-a-pull-request-branch-created-from-a-fork %} + {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} +{% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} + {% link_in_list /about-status-checks %} + {% link_in_list /working-with-pre-receive-hooks %} +{% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} + {% link_in_list /about-branches %} + {% link_in_list /creating-and-deleting-branches-within-your-repository %} + {% link_in_list /about-pull-requests %} + {% link_in_list /about-comparing-branches-in-pull-requests %} + {% link_in_list /creating-a-pull-request %} + {% link_in_list /creating-a-pull-request-from-a-fork %} + {% link_in_list /changing-the-stage-of-a-pull-request %} + {% link_in_list /requesting-a-pull-request-review %} + {% link_in_list /changing-the-base-branch-of-a-pull-request %} + {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} +{% topic_link_in_list /addressing-merge-conflicts %} + {% link_in_list /about-merge-conflicts %} + {% link_in_list /resolving-a-merge-conflict-on-github %} + {% link_in_list /resolving-a-merge-conflict-using-the-command-line %} +{% topic_link_in_list /reviewing-changes-in-pull-requests %} + {% link_in_list /about-pull-request-reviews %} + {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} + {% link_in_list /filtering-files-in-a-pull-request %} + {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} + {% link_in_list /commenting-on-a-pull-request %} + {% link_in_list /viewing-a-pull-request-review %} + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} + {% link_in_list /incorporating-feedback-in-your-pull-request %} + {% link_in_list /approving-a-pull-request-with-required-reviews %} + {% link_in_list /dismissing-a-pull-request-review %} + {% link_in_list /checking-out-pull-requests-locally %} +{% topic_link_in_list /incorporating-changes-from-a-pull-request %} + {% link_in_list /about-pull-request-merges %} + {% link_in_list /merging-a-pull-request %} + {% link_in_list /automatically-merging-a-pull-request %} + {% link_in_list /closing-a-pull-request %} + {% link_in_list /reverting-a-pull-request %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md new file mode 100644 index 0000000000000..bb802f0070db6 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -0,0 +1,77 @@ +--- +title: Fusionar una solicitud de extracción +intro: Fusionar una solicitud de extracción dentro de una rama ascendente cuando el trabajo está completo. Cualquier persona con acceso de escritura al repositorio puede completar la fusión. +redirect_from: + - /articles/merging-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Acerca de las fusiones de las solicitudes de extracción + +En una solicitud de extracción, propones que los cambios que hayas hecho en una rama de encabezado se fusionen en una rama base. Por defecto, cualquier solicitud de extracción se puede fusionar en cualquier momento, a menos que la rama de encabezado esté en conflicto con la rama base. However, there may be restrictions on when you can merge a pull request into a specific branch. Por ejemplo, puede que solo puedas fusionar una solicitud de extracción en la rama predeterminada si están pasando las verificaciones de estado requeridas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". + +{% data reusables.pull_requests.you-can-auto-merge %} + +Si la solicitud de extracción tiene conflictos de fusión, o si deseas probar los cambios antes de la fusión, puedes [revisar la solicitud de extracción de forma local](/articles/checking-out-pull-requests-locally) y fusionarla utilizando la línea de comando. + +No puedes fusionar un borrador de solicitud de cambios. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)". + +{% data reusables.pull_requests.automatically-delete-branches %} + +Si decides que no deseas que los cambios en una rama de tema se fusionen con la rama ascendente, puedes [cerrar la solicitud de extracción](/articles/closing-a-pull-request) sin fusionar. + +### Fusionar una solicitud de extracción en {% data variables.product.prodname_dotcom %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas fusionar. +3. Según las opciones de fusión habilitadas para tu repositorio, puedes: + - [Fusionar todas las confirmaciones de cambios dentro de la rama base](/articles/about-pull-request-merges/) al hacer clic en **Merge pull request (Fusionar solicitud de extracción)**. Si no se muestra la opción **Merge pull request** (Fusionar solicitud de extracción), haz clic en el menú desplegable de fusiones y selecciona **Create a merge commit** (Crear una confirmación de fusión). ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/pull_requests/pullrequest-mergebutton.png) + - [Combinar las confirmaciones de cambios en una sola confirmación](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) haciendo clic en el menú desplegable, luego selecciona **Squash and merge** (Combinar y fusionar) y haz clic en el botón **Squash and merge** (Combinar y fusionar). ![click-squash-and-merge-button (hacer clic en el botón para combinar y fusionar)](/assets/images/help/pull_requests/select-squash-and-merge-from-drop-down-menu.png) + - [Rebasar las confirmaciones por separado sobre la rama base](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) haciendo clic en el menú desplegable de fusión, luego selecciona **Rebase and merge** (Rebasar y fusionar) y haz clic en el botón **Rebase and merge** (Rebasar y fusionar). ![select-rebase-and-merge-from-drop-down-menu (seleccionar del menú desplegable para rebasar y fusionar)](/assets/images/help/pull_requests/select-rebase-and-merge-from-drop-down-menu.png) + + {% note %} + + **Nota:** Rebasar y fusionar siempre actualizará la información de la persona que confirma el cambio y creará una nueva SHA de confirmación de cambio. Para obtener más información, consulta "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)." + + {% endnote %} +4. Si se solicita, escribe un mensaje de confirmación de cambios, o acepta el mensaje predeterminado. + + {% data reusables.pull_requests.default-commit-message-squash-merge %} + ![Campo para mensaje de confirmación](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png) + +{% data reusables.files.choose-commit-email %} + + {% note %} + + **Nota:** El selector de correo electrónico no se encuentra disponible para las fusiones de rebase, lo cual no crea una confirmación de fusión, o para fusiones de combinación, lo cual acredita al usuario que creó la solicitud de cambios como el autor de la confirmación combinada. + + {% endnote %} + +6. Haz clic en **Confirm merge** (Confirmar fusión), **Confirm squash and merge** (Confirmar combinación y fusión) o **Confirm rebase and merge** (Confirmar rebase y fusión). +6. De forma opcional, [elimina la rama](/articles/deleting-unused-branches). Esto mantiene ordenado el listado de ramas en tu repositorio. + +El repositorio podría configurarse para que la rama de encabezado para una solicitud de cambios se borre automáticamente cuando fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)". + + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Nota:** {% data reusables.pull_requests.retargeted-on-branch-deletion %} + Para obtener más información, consulta la sección "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)". + + {% endnote %} + {% endif %} + +Las solicitudes de extracción se fusionan utilizando [la opción `--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge), excepto [las solicitudes de extracción con confirmaciones de rebase y combinación](/articles/about-pull-request-merges), que se fusionan utilizando la opción de avance rápido. + +{% data reusables.pull_requests.close-issues-using-keywords %} + +### Further reading + +- "[Revertir una solicitud de extracción](/articles/reverting-a-pull-request)" +- "[Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" utilizando {% data variables.product.prodname_desktop %} +- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" +- "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md new file mode 100644 index 0000000000000..c9f84783eb4e0 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md @@ -0,0 +1,28 @@ +--- +title: Fusionar un repositorio ascendente dentro de tu bifurcación +intro: 'Si no tienes acceso de subida (escritura) en un repositorio ascendente, entonces puedes extraer confirmaciones de cambios de ese repositorio dentro tu propia bifurcación.' +redirect_from: + - /articles/merging-an-upstream-repository-into-your-fork +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambiar el directorio de trabajo actual en tu proyecto local. +3. Revisa la rama a la que deseas fusionar. Habitualmente, fusionarás en la rama predeterminada. + ```shell + $ git checkout DEFAULT_BRANCH_NAME + ``` +4. Extrae la rama deseada del repositorio ascendente. Este método conservará el historial de confirmación de cambios sin modificación. + ```shell + $ git pull https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git BRANCH_NAME + ``` +5. Si hay conflictos, resuélvelos. Para obtener más información, consulta "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)". +6. Confirma la fusión. +7. Revisa los cambios y asegúrate que sean correctos. +8. Sube la fusión en tu repositorio de GitHub. + ```shell + $ git push origin DEFAULT_BRANCH_NAME + ``` diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md new file mode 100644 index 0000000000000..76b5468bed717 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md @@ -0,0 +1,10 @@ +--- +title: Resumen +intro: 'Aprende sobre el flujo de {% data variables.product.prodname_dotcom %} y las formas diferentes para debatir y colaborar en tus proyectos.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md new file mode 100644 index 0000000000000..67fa5e0159536 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md @@ -0,0 +1,12 @@ +--- +title: Proponer cambios a tu trabajo con solicitudes de extracción +intro: 'Después de agregar cambios a una rama de tema o bifurcación, puedes abrir una solicitud de extracción para pedirle a tus colaboradores o al administrador del repositorio que revisen tus cambios antes de fusionarlos con el proyecto.' +mapTopic: verdadero +redirect_from: + - /articles/proposing-changes-to-your-work-with-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md new file mode 100644 index 0000000000000..40e6b282ae87c --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -0,0 +1,34 @@ +--- +title: Solicitar una revisión de solicitud de extracción +intro: 'Después de crear una solicitud de extracción, le puedes pedir a una persona específica que revise los cambios que propusiste. Si eres miembro de la organización, también puedes solicitarle a un equipo específico que revise tus cambios.' +redirect_from: + - /articles/requesting-a-pull-request-review +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios y colaboradores de un repositorio que pertenece a una cuenta de usuario pueden asignar revisiones de solicitud de extracción. Los miembros de la organización con permisos de clasificación de un repositorio pueden asignar una revisión de solicitud de extracción. + +Los propietarios o colaboradores pueden asignar una revisión de solicitud de extracción a cualquier persona que tenga [acceso de lectura](/articles/access-permissions-on-github) explícitamente garantizado a un repositorio que es propiedad del usuario. Los miembros de la organización pueden asignar la revisión de una solicitud de extracción a una persona o equipo con acceso de lectura a un repositorio. El revisor o equipo solicitado recibirá una notificación sobre tu solicitud de revisión de la solicitud de extracción. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si solicitas una revisión de un equipo y se habilita una asignación de revisión de código, se solicitarán miembros específicos y el equipo se eliminará como revisor. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)".{% endif %} + +{% note %} + +**Nota:** Los autores de solicitudes de extracción no pueden solicitar revisiones a menos que sean propietarios del repositorio o colaboradores con acceso de escritura al repositorio. + +{% endnote %} + +Puedes solicitar una revisión de una persona sugerida o de una persona específica. Los revisores sugeridos se basan en los [datos del último responsable de git](/articles/tracking-changes-in-a-file/). Si solicitas una revisión, otras personas con acceso de escritura al repositorio pueden seguir revisando tu solicitud de extracción. Una vez que alguien haya revisado tu solicitud de código y hayas implementado los cambios necesarios, puedes volver a solicitar la revisión al mismo revisor. Si el revisor solicitado no emite una revisión y la solicitud de extracción cumple con los [requisitos para fusión](/articles/defining-the-mergeability-of-pull-requests) del repositorio, puedes fusionarla de todos modos. + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que quieres que una persona específica o un equipo revise. +3. Navega hacia **Reviewers** (Revisores) en la barra lateral derecha. +4. Para solicitar la revisión de una persona sugerida en **Reviewers** (Revisores), al lado del nombre de usuario, haz clic en **Request** (Solicitar). ![Icono Reviewers request (Solicitud de revisores) en la barra lateral derecha](/assets/images/help/pull_requests/request-suggested-review.png) +5. De manera opcional, para solicitar una revisión de alguna persona que no sea una persona sugerida, haz clic en **Reviewers** (Revisores), luego haz clic en un nombre en el menú desplegable. ![Icono Reviewers gear (Parámetro de revisores) en la barra lateral derecha](/assets/images/help/pull_requests/request-a-review-not-suggested.png) +6. De manera opcional, si conoces el nombre de la persona o el equipo del que quieres una revisión, haz clic en **Reviewers** (Revisores), luego escribe el nombre de usuario de la persona o el nombre del equipo al que le solicitarás que revise tus cambios. Haz clic en su nombre de equipo o nombre de usuario para solicitar una revisión. ![Campo para ingresar el nombre de usuario de un revisor y desplegable con el nombre del revisor](/assets/images/help/pull_requests/choose-pull-request-reviewer.png) +7. Después de que la solicitud de extracción esté revisada y de que hayas hecho los cambios necesarios, le puedes pedir a un revisor que vuelva a revisar tu solicitud de extracción. Navega hasta **Reviewers** (Revisores) en la barra lateral derecha y haz clic en {% octicon "sync" aria-label="The sync icon" %} al lado del nombre del revisor del que quieres la revisión. ![Icono Re-review sync (Sincronización de volver a revisar) en la barra lateral derecha](/assets/images/help/pull_requests/request-re-review.png) + +### Further reading + +- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md new file mode 100644 index 0000000000000..d6be465eaaac8 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md @@ -0,0 +1,61 @@ +--- +title: Resolver un conflicto de fusión en GitHub +intro: 'Puedes resolver conflictos de fusión simples que impliquen realizar cambios de líneas en GitHub, usando el editor de conflictos.' +redirect_from: + - /articles/resolving-a-merge-conflict-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo puedes resolver los conflictos de fusión en {% data variables.product.product_name %} que hayan sido provocados por realizar cambios de líneas, como cuando las personas hacen cambios diferentes en la misma línea del mismo archivo en ramas diferentes de tu repositorio de Git. Para todos los demás tipos de conflictos de fusión, debes resolver el conflicto de manera local desde la línea de comando. Para obtener más información, consulta "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line/)". + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +Si un administrador de sitio inhabilita el editor de conflicto de fusión para las solicitudes de cambios entre repositorios, no podrás utilizar dicho editor de conflictos en +{% data variables.product.product_name %} y deberás resolver los conflictos de fusión en la línea de comandos. Por ejemplo, si el editor de conflictos de fusión está inhabilitado, no podrás utilizarlo en una solicitud de extracción entre una bifurcación y el repositorio ascendente. +{% endif %} + +{% warning %} + +{% if currentVersion ver_lt "enterprise-server@2.22" %} +**Advertencia:** Cuando resuelves un conflicto de fusión en +{% data variables.product.product_name %}, toda la [rama base](/github/getting-started-with-github/github-glossary#base-branch) de tu solicitud de cambios se fusiona en la [rama de encabezado](/github/getting-started-with-github/github-glossary#head-branch), aún si esta es la rama predeterminada de tu repositorio o si es una rama protegida. Asegúrate que realmente quieras hacer una confirmación para esta rama. +{% else %} +**Advertencia:** Cuando resuelves un conflicto de fusión en +{% data variables.product.product_name %}, toda la [rama base](/github/getting-started-with-github/github-glossary#base-branch) de tu solicitud de cambios se fusiona en la [rama de encabezado](/github/getting-started-with-github/github-glossary#head-branch). Asegúrate que realmente quieras hacer una confirmación para esta rama. Si la rama de encabezado es la predeterminada para tu repositorio, se te dará la opción de crear una rama nueva para que funcione como rama de encabezado para tu solicitud de extracción. Si la rama principal está protegida, no podrás fusionar tu resolución de conflictos con ella, así que se te pedirá crear una nueva rama principal. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". +{% endif %} + +{% endwarning %} + +{% data reusables.repositories.sidebar-pr %} +1. En la lista de "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción con un conflicto de fusión que quieres resolver. +1. Cerca de la parte de abajo de tu solicitud de extracción, haz clic en **Resolve conflicts** (Resolver conflictos). ![Botón para resolver conflictos de fusión](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) + + {% tip %} + + **Tip:** si se desactiva el botón de **Resolve conflicts** el conflicto de fusión de tu solicitud de cambios es demasiado complejo para resolverse en {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} o el administrador inhabilitó el editor de conflictos para las solicitudes de cambios entre los repositorios{% endif %}. Debes resolver el conflicto de fusión utilizando un cliente de Git alterno, o utilizando Git en la línea de comandos. Para obtener más información, consulta "[Resolver un conflicto de fusión con la línea de comando](/articles/resolving-a-merge-conflict-using-the-command-line)". + + {% endtip %} +{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} + ![Ver el ejemplo de conflicto de fusión con los marcadores de conflicto](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) +1. Si tienes más de un conflicto de fusión en tu archivo, desplázate hacia abajo hasta el siguiente conjunto de marcadores de conflicto y repite los pasos cuatro y cinco para resolver el conflicto de fusión. +1. Una vez que hayas resuelto todos los conflictos en el archivo, haz clic en **Mark as resolved** (Marcar como resuelto). ![Dar clic en el botón de marcar como resuelto](/assets/images/help/pull_requests/mark-as-resolved-button.png) +1. Si tienes más de un archivo con conflictos, selecciona el siguiente archivo que quieres editar del lado izquierdo de la página en "conflicting files" (archivos conflictivos) y repite los pasos cuatro a siete hasta que hayas resuelto todos los conflictos de fusión de tu solicitud de extracción. ![Seleccionar el siguiente archivo conflictivo, de ser aplicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) +1. Una vez que hayas resuelto todos tus conflictos de fusión, haz clic en **Commit merge** (Confirmar fusión). Esto fusiona toda la rama de base con tu rama de encabezado. ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png){% if currentVersion ver_lt "enterprise-server@2.22" %} +1. Si se te solicita, revisa la rama para la que vas a confirmar. Si quieres confirmar para esta rama, haz clic en **I understand, update _BRANCH_** (Comprendo, actualizar RAMA). ![Merge conflict confirmation window](/assets/images/help/pull_requests/merge-conflict-confirmation.png){% else %} +1. Si se te solicita, revisa la rama para la que vas a confirmar. + + Si la rama principal es la rama predeterminada del repositorio, puedes escoger ya sea actualizar esta rama con los cambios que hiciste para resolver el conflicto, o crear una rama nueva y utilizarla como la rama principal de la solicitud de extracción. ![Mensaje para revisar la rama que se actualizará](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) + + Si eliges crear una rama nueva, ingresa un nombre para ésta. + + Si la rama principal de tu solicitud de extracción está protegida, debes crear una rama nueva. No tendrás la opción para actualizar la rama protegida. + + Da clic en **Crear rama y actualizar mi solicitud de extracción** o en **Entiendo, continuar actualizando la _RAMA_**. El texto del botón corresponde a la acción que estás realizando. +{% endif %} +1. Para fusionar tu solicitud de extracción, haz clic en **Merge pull request** (Fusionar solicitud de extracción). Para obtener más información acerca de otras opciones de fusión de solicitudes de extracción, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request/)". + +### Further reading + +- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md new file mode 100644 index 0000000000000..f1eb0ff4be5f8 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -0,0 +1,125 @@ +--- +title: Resolver un conflicto de fusión con la línea de comando +intro: Puedes resolver conflictos de fusión con la línea de comando y un editor de texto. +redirect_from: + - /articles/resolving-a-merge-conflict-from-the-command-line/ + - /articles/resolving-a-merge-conflict-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los conflictos de fusión ocurren cuando se hacen cambios contrapuestos en la misma línea de un archivo o cuando una persona edita un archivo y otra persona borra el mismo archivo. Para obtener más información, consulta "[Acerca de los conflictos de fusión](/articles/about-merge-conflicts/)". + +{% tip %} + +**Sugerencia:** Puedes utilizar el editor de conflictos en {% data variables.product.product_name %} para resolver conflictos de fusión de cambios de líneas contrapuestos entre ramas que son parte de una solicitud de extracción. Para obtener más información, consulta "[Resolver un conflicto de fusión en GitHub](/articles/resolving-a-merge-conflict-on-github)". + +{% endtip %} + +### Conflictos de fusión de cambios de líneas contrapuestos + +Para resolver un conflicto de fusión causado por cambios de líneas contrapuestos, debes decidir qué cambios incorporar desde las diferentes ramas de una confirmación nueva. + +Por ejemplo, si usted y otra persona editaron el archivo _styleguide.md_ en las mismas líneas de diferentes ramas del mismo repositorio de Git, recibirás un error de conflicto de fusión cuando trates de fusionar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Navega en el repositorio de Git local que tiene el conflicto de fusión. + ```shell + cd REPOSITORY-NAME + ``` +3. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *styleguide.md* tiene un conflicto de fusión. + ```shell + $ git status + > # On branch branch-b + > # You have unmerged paths. + > # (fix conflicts and run "git commit") + > # + > # Unmerged paths: + > # (use "git add ..." to mark resolution) + > # + > # both modified: styleguide.md + > # + > no changes added to commit (use "git add" and/or "git commit -a") + ``` +4. Abre tu editor de texto preferido, como [Atom](https://atom.io/), y navega hasta el archivo que tiene los conflictos de fusión. +5. Para ver el origen de un conflicto de fusión en tu archivo, busca el archivo para el marcador de conflicto `<<<<<<<`. Cuando abras el archivo en tu editor de texto, verás los cambios desde la rama HEAD (encabezado) o base después de la línea `<<<<<<< HEAD`. Luego verás `=======`, que separa tus cambios de los cambios en la otra rama, seguido de `>>>>>>> BRANCH-NAME`. En este ejemplo, una persona escribió "abrir una propuesta" en la rama base o HEAD (encabezado), y otra persona escribió "haz tu pregunta en IRC" en la rama de comparación o `branch-a`. + + ``` +If you have questions, please +<<<<<<< HEAD +open an issue +======= +ask your question in IRC. +>>>>>>> branch-a + ``` +{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}En este ejemplo, ambos cambios se incorporaron en la fusión final: + + ```shell + Si tienes preguntas, abre una propuesta o consulta en nuestro canal IRC si es más urgente. + ``` +7. Agrega o almacena tus cambios. + ```shell + $ git add . + ``` +8. Confirma tus cambios con un comentario. + ```shell + $ git commit -m "Conflicto de fusión resuelto incorporando ambas sugerencias". + ``` + +Ahora puedes fusionar las ramas en la línea de comando o [subir tus cambios a tu repositorio remoto](/articles/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [fusionar tus cambios](/articles/merging-a-pull-request/) en una solicitud de extracción. + +### Conflictos de fusión de archivos eliminados + +Para resolver un conflicto de fusión causado por cambios contrapuestos en un archivo, cuando una persona elimina un archivo en una rama y otra persona edita el mismo archivo, debes decidir si eliminar o conservar el archivo eliminado en una confirmación nueva. + +Por ejemplo, si editaste un archivo, como *README.md*, y otra persona eliminó el mismo archivo en otra rama del mismo repositorio de Git, recibirás un error de conflicto de fusión cuando trates de fusionar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Navega en el repositorio de Git local que tiene el conflicto de fusión. + ```shell + cd REPOSITORY-NAME + ``` +2. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *README.md* tiene un conflicto de fusión. + ```shell + $ git status + > # On branch main + > # Your branch and 'origin/main' have diverged, + > # and have 1 and 2 different commits each, respectively. + > # (use "git pull" to merge the remote branch into yours) + > # You have unmerged paths. + > # (fix conflicts and run "git commit") + > # + > # Unmerged paths: + > # (use "git add/rm ..." as appropriate to mark resolution) + > # + > # deleted by us: README.md + > # + > # no changes added to commit (use "git add" and/or "git commit -a") + ``` +3. Abre tu editor de texto preferido, como [Atom](https://atom.io/), y navega hasta el archivo que tiene los conflictos de fusión. +6. Decide si quieres conservar el archivo eliminado. Puede que quieras ver los últimos cambios hechos en el archivo eliminado en tu editor de texto. + + Para volver a agregar el archivo eliminado a tu repositorio: + ```shell + $ git add README.md + ``` + Para eliminar este archivo de tu repositorio: + ```shell + $ git rm README.md + > README.md: needs merge + > rm 'README.md' + ``` +7. Confirma tus cambios con un comentario. + ```shell + $ git commit -m "Resolved merge conflict by keeping README.md file." + > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d + ``` + +Ahora puedes fusionar las ramas en la línea de comando o [subir tus cambios a tu repositorio remoto](/articles/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [fusionar tus cambios](/articles/merging-a-pull-request/) en una solicitud de extracción. + +### Further reading + +- "[Acerca de los conflictos de fusión](/articles/about-merge-conflicts)" +- "[Revisar las solicitudes de extracción de forma local](/articles/checking-out-pull-requests-locally/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md new file mode 100644 index 0000000000000..25d3c57accecc --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md @@ -0,0 +1,32 @@ +--- +title: Revertir una solicitud de extracción +intro: Puedes revertir una solicitud de extracción después de que se haya fusionado con la rama ascendente. +redirect_from: + - /articles/reverting-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de revertir una solicitud de extraccción + +Revertir una solicitud de extracción en {% data variables.product.product_name %} genera una nueva solicitud de extracción que contiene una reversión de la confirmación de fusión de la solicitud de extracción fusionada original. + +### Revertir una solicitud de extracción + +{% note %} + +**Nota:** Podrías tener que revertir las confirmaciones individuales en tu solicitud de extracción si cualquiera de los siguientes casos aplica. + +- Revertir la solicitud de extracción provoca conflictos de fusión +- La solicitud de extracción original no se fusionó originalmente en {% data variables.product.product_name %}. Por ejemplo, alguien pudo haber fusionado la solicitud de extracción utilizando una fusión adelantada en la línea de comandos. + +Para obtener más información acerca de utilizar Git para revertir las confirmaciones individuales manualmente, consulta la sección [Revertir con Git](https://git-scm.com/docs/git-revert.html) en la documentación de Git. + +{% endnote %} + +{% data reusables.repositories.sidebar-pr %} +2. En la lista de "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que quieras revertir. +3. Cerca de la parte de abajo de la solicitud de extracción, haz clic en **Revert** (Revertir). ![Enlace Revert pull request (Revertir solicitud de extracción)](/assets/images/help/pull_requests/revert-pull-request-link.png) +4. Fusionar la solicitud de extracción resultante. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)". diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md new file mode 100644 index 0000000000000..91ab4b46fcaeb --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Revisar cambios en solicitudes de extracción +redirect_from: + - /articles/reviewing-and-discussing-changes-in-pull-requests/ + - /articles/reviewing-changes-in-pull-requests +intro: 'Después de haber abierto una solicitud de extracción, puedes revisar y opinar sobre el conjunto de cambios propuestos.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000000..ec61619aebed9 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,72 @@ +--- +title: Revisar los cambios de las dependencias en una solicitud de cambios +intro: 'Si una solicitud de cambios contiene cambios a las dependencias, puedes ver un resumen de lo que ha cambiado y si es que existen vulnerabilidades conocidas en cualquiera de estas dependencias.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** Las revisiones de dependencias se encuentran actualmente en beta y están sujetas a cambios. + +{% endnote %} + +### Acerca de la revisión de dependencias + +Si una solicitud de cambios apunta a la rama predeterminada de tu repositorio y contiene cambios a los archivos de bloqueo o de manifiesto empaquetados, puedes mostrar una revisión de dependencias para ver qué ha cambiado. La revisión de dependencias incluye detalles de los cambios a las dependencias indirectas en los archivos de bloqueo, y te dice si cualquiera de las dependencias que se agregaron o actualizaron contienen vulnerabilidades conocidas. + +La revisión de dependencias se encuentra disponible en: + +* Todos los repositorios públicos. +* Los repositorios privados que pertenecen a las organizaciones con una licencia de {% data variables.product.prodname_advanced_security %} que tengan la gráfica dependencias habilitada. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". + +Algunas veces puede que solo quieras actualizar la versión de una dependencia en un manifiesto y generar una solicitud de cambios. Sin embargo, si la versión actualizada de esta dependencia directa también tiene dependencias actualizadas, tu solicitud de cambios podría tener más cambios de lo que esperas. La revisión de dependencias para cada archivo de bloqueo y de manifiesto proporciona un aforma sencilla para ver lo que ha cambiado y te deja saber si cualquiera de las versiones nuevas de las dependencias contienen vulnerabilidades conocidas. + +Cuando verificas las revisiones de dependencias en una solicitud de cambios y cambias cualquier dependencia que se marque como vulnerable, puedes evitar que las vulnerabilidades se agreguen a tu proyecto. Las {% data variables.product.prodname_dependabot_alerts %} encontrarán vulnerabilidades que ya existan en tus dependencias, pero es mucho mejor evitar introducir problemas potenciales que arreglarlos en el futuro. Para obtener más informació acera de las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". + +La revisión de dependencias es compatible con los mismos lenguajes de programación y ecosistemas de administración de paquetes que la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". + +### Revisar las dependencias en una solicitud de cambios + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. Si la solicitud de cambios contiene muchos archivos, utiliza el menú desplegable de **Filtro de archivos** para que colapse todos los archivos que no registran dependencias. Esto facilitará que te enfoques en tu revisión de cambios a las dependencias. + + ![El menú de filtro de archivo](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. + + ![El botón de diff rica](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Nota:** La revisión de dependencias proporciona una vista más clara de lo que ha cambiado en los archivos de bloqueo grandes, donde la diff origen no se representa predeterminadamente. + + {% endnote %} + +1. Verifica las dependencias que se listan en la revisión de dependencias. + + ![Alertas de vulnerabilidades en una revisión de dependencias](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Cualquier dependencia que se cambie o agregue y que tenga vulnerabilidades se listará primero, se organizará por severidad y luego por nombre de dependencia. Esto significa que la severidad de dependencias más alta siempre se encontrará en la parte superior de la revisión de dependencias. El resto de las dependencias se lista por orden alfabético de acuerdo con el nombre de la dependencia. + + El icono a un costado de cada dependencia indica si ésta se agregó ({% octicon "diff-added" aria-label="Dependency added icon" %}), actualizó ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), o eliminó ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) en esta solicitud de cambios. + + El resto de la información incluye: + + * La versión o rango de versiones de la dependencia nueva, actualizada o borrada. + * Para el caso de las versiones específicas de una dependencia: + * La antigüedad del lanzamiento de la dependencia. + * La cantidad de proyectos que dependen de este software. Esta información se toma de la gráfica de dependencias. Verificar la cantidad de dependientes que pueden ayudarte a evitar el agregar accidentalmente la dependencia incorrecta. + * La licencia que utiliza esta dependencia si es que esta información se encuentra disponible. Esto es útil si quieres evitar el código que utilice licencias específicas, el cual utilizas en tu proyecto. + + Cuando una dependencia tiene una vulnerabilidad conocida, el mensaje de advertencia incluye: + + * Una descripción breve de la vulnerabilidad. + * Un archivo de Vulnerabilidades y Exposiciones Comunes (CVE) o un número de identificación (GHSA) de {% data variables.product.prodname_security_advisories %}. Puedes dar clic en esta ID para conocer más sobre la vulnerabilidad. + * La severidad de la vulnerabilidad. + * La versión de la dependencia en la cual se arregló la vulnerabilidad. Si estás revisando una solicitud de cambios para alguien, puedes pedir al contribuyente que actualice la dependencia a la versión parchada o a un lanzamiento más reciente. + +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md new file mode 100644 index 0000000000000..b7cc034a47854 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -0,0 +1,71 @@ +--- +title: Revisar los cambios propuestos en una solicitud de extracción +intro: 'En una solicitud de extracción, puedes revisar y opinar sobre las confirmaciones, los archivos cambiados y las diferencias (o "diff") entre los archivos de las ramas de base y comparada.' +redirect_from: + - /articles/reviewing-proposed-changes-in-a-pull-request +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de revisar las solicitudes de extracción + +Puedes revisar los cambios de una solicitud de extracción en un archivo por vez. Mientras revisas los archivos en una solicitud de extracción, puedes dejar comentarios individuales en cambios específicos. Después de que terminas de revisar cada archivo, puedes marcarlo como visto. Esto colapsa el archivo, lo cual te ayuda a identificar los archivos que aún debes revisar. Una barra de progreso en el encabezado de la solicitud de cambios muestra la cantidad de archivos que has visto. Después de revisar tantos archivos como quieras, puedes aprobar la solicitud de cambios o solicitar cambios adicionales si emites tu revisión con un comentario de resumen. + +{% data reusables.search.requested_reviews_search_tip %} + +### Comenzar una revisión + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} +{% data reusables.repositories.start-line-comment %} +{% data reusables.repositories.type-line-comment %} +{% data reusables.repositories.suggest-changes %} +5. Cuando estés listo, haz clic en **Start a review** (Comenzar una revisión). Si ya comenzaste una revisión, puedes hacer clic en **Add review comment** (Agregar comentario de revisión). ![Botón Start a review (Comenzar una revisión)](/assets/images/help/pull_requests/start-a-review-button.png) + +Antes de enviar tu revisión, tus comentarios de líneas quedan _pendientes_, y solo tú los puedes ver. Puedes editar los comentarios pendientes en cualquier momento antes de enviar tu revisión. Para cancelar una revisión pendiente, incluidos todos sus comentarios pendientes, desplázate hasta el final de la cronología en la pestaña Conversation (Conversación) y haz clic en **Cancel review** (Cancelar revisión). + +![Botón Cancel review (Cancelar revisión)](/assets/images/help/pull_requests/cancel-review-button.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Revisar los cambios de las dependencias + +Si la solicitud de cambios contiene cambios para las dependencias, puedes utilizar la revisión de dependencias para un archivo de bloqueo o de manifiesto para ver qué ha cambiado y verificar si los cambios introducen vulnerabilidades de seguridad. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". + +{% data reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. + + ![El botón de diff rica](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} +{% endif %} + +### Marcar un archivo como visto + +Después de que hayas terminado de revisar un archivo, puedes marcar el archivo como visto, y el archivo se colapsará. Si el archivo se modifica después de que lo hayas visto, dejará de estar marcado como visto. + +{% data reusables.repositories.changed-files %} +2. A la derecha del encabezado del archivo que terminaste de revisar, selecciona **Viewed** (Visto). ![Casilla Viewed (Visto)](/assets/images/help/pull_requests/viewed-checkbox.png) + +### Enviar tu revisión + +Después de que hayas terminado de revisar todos los archivos que quieras de la solicitud de extracción, envía tu revisión. + +{% data reusables.repositories.changed-files %} +{% data reusables.repositories.review-changes %} +{% data reusables.repositories.review-summary-comment %} +4. Selecciona el tipo de revisión que te gustaría proporcionar: ![Botones Radio con opciones de revisión](/assets/images/help/pull_requests/pull-request-review-statuses.png) + - Selecciona **Comment** (Comentario) para dejar una opinión general sin aprobar de manera explícita los cambios ni solicitar cambios adicionales. + - Selecciona **Approve** (Aprobar) para enviar tus comentarios y aprobar la fusión de los cambios propuestos en la solicitud de extracción. + - Selecciona **Request changes** (Solicitar cambios) para enviar comentarios que se deban tener en cuenta antes de que se pueda fusionar la solicitud de extracción. +{% data reusables.repositories.submit-review %} + +{% data reusables.repositories.request-changes-tips %} + +### Further reading + +- "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" +- "[Filtrar solicitudes de extracción por estado de revisión](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md new file mode 100644 index 0000000000000..811c407ffb207 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md @@ -0,0 +1,54 @@ +--- +title: Sincronizar una bifurcación +intro: Sincronizar una bifurcación de un repositorio para mantenerla actualizada con el repositorio ascendente. +redirect_from: + - /articles/syncing-a-fork +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Antes de sincronizar una bifurcación con un repositorio ascendente, debes [configurar un remoto que apunte al repositorio ascendente ](/articles/configuring-a-remote-for-a-fork) en Git. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambiar el directorio de trabajo actual en tu proyecto local. +3. Extrae las ramas y sus respectivas confirmaciones desde el repositorio ascendente. Las confirmaciones a `BRANCHNAME` se almacenarán en la rama local `upstream/BRANCHNAME`. + ```shell + $ git fetch upstream + > remote: Counting objects: 75, done. + > remote: Compressing objects: 100% (53/53), done. + > remote: Total 62 (delta 27), reused 44 (delta 9) + > Unpacking objects: 100% (62/62), done. + > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY + > * [new branch] main -> upstream/main + ``` +4. Revisa la rama predeterminada local de tu bifurcación - en este caso, utilizamos `main`. + ```shell + $ git checkout main + > Switched to branch 'main' + ``` +5. Fusiona los cambios de la rama predeterminada ascendente - en este caso, `upstream/main` - en tu rama predeterminada local. Esto hace que la rama predeterminada de tu bifurcación se sincronice con el repositorio ascendente sin perder tus cambios locales. + ```shell + $ git merge upstream/main + > Updating a422352..5fdff0f + > Fast-forward + > README | 9 ------- + > README.md | 7 ++++++ + > 2 files changed, 7 insertions(+), 9 deletions(-) + > delete mode 100644 README + > create mode 100644 README.md + ``` If your local branch didn't have any unique commits, Git will instead perform a "fast-forward": + ```shell + $ git merge upstream/main + > Updating 34e91da..16c56ad + > Fast-forward + > README.md | 5 +++-- + > 1 file changed, 3 insertions(+), 2 deletions(-) + ``` + +{% tip %} + +**Sugerencia:**: sincronizar tu bifurcación únicamente actualiza tu copia local del repositorio. Para actualizar tu bifurcación en {% data variables.product.product_location %}, debes [subir tus cambios](/articles/pushing-commits-to-a-remote-repository/). + +{% endtip %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md new file mode 100644 index 0000000000000..00e2c343fdcdf --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md @@ -0,0 +1,23 @@ +--- +title: Ver una revisión de solicitud de extracción +intro: Puedes ver todos los comentarios realizados en una revisión de revisión de solicitud de extracción única. +redirect_from: + - /articles/viewing-a-pull-request-review +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.search.requested_reviews_search %} + +Cuando ves una revisión completa, verás la misma versión de la solicitud de extracción como el revisor lo hizo al momento de la revisión. + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +3. En la pestaña "Conversation" (Conversación), desplázate hasta la revisión que deseas ver y luego haz clic en **View changes (Ver cambios)**. ![Encabezado de revisión con el vínculo de revisión completa](/assets/images/help/pull_requests/view-full-review-view-changes.png) + +### Further reading + +- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" +- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md new file mode 100644 index 0000000000000..c84b288684f5c --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -0,0 +1,81 @@ +--- +title: '¿Qué le sucede a las bifurcaciones cuando se elimina un repositorio o cambia la visibilidad?' +intro: Eliminar tu repositorio o cambiar su visibilidad afecta las bifurcaciones de ese repositorio. +redirect_from: + - /articles/changing-the-visibility-of-a-network/ + - /articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +#### Eliminar un repositorio privado + +Cuando eliminas un repositorio privado, todas sus bifurcaciones privadas también se eliminan. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +#### Eliminar un repositorio público + +Cuando eliminas un repositorio público, se elige una de sus bifurcaciones públicas para ser el nuevo repositorio padre. Todos los otros repositorios se bifurcan fuera de este nuevo repositorio y las solicitudes de extracción siguientes van a este nuevo padre. + +{% endif %} + +#### Permisos y bifurcaciones privadas + +{% data reusables.repositories.private_forks_inherit_permissions %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +#### Convertir un repositorio público en un repositorio privado + +Si un repositorio público se convierte en privado, sus bifurcaciones públicas se separan a una nueva red. Como con la eliminación de un repositorio público, se elige una de las bifurcaciones públicas existentes para ser el nuevo repositorio padre y todos los otros repositorios se bifurcan fuera de este nuevo padre. Las solicitudes de extracción siguientes van a este nuevo padre. + +En otras palabras, las bifurcaciones de un repositorio público permanecerán en su propia red separada del repositorio incluso después de que un repositorio padre se convierte en privado. Esto permite que los propietarios de las bifurcaciones continúen trabajando y colaboren sin interrupción. Si las bifurcaciones públicas no se mueven a una red separada de esta manera, los propietarios de esas bifurcaciones podrían necesitar obtener los [permisos de acceso](/articles/access-permissions-on-github) adecuados para extraer cambios y enviar solicitudes de extracción desde el repositorio padre (ahora privado) y hacia él, incluso si no necesitaban esos permisos anteriormente. + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +Si un repositorio público tiene habilitado el acceso de lectura anónimo de Git, y el repositorio se vuelve privado, todas las bifurcaciones del repositorio perderán el acceso de lectura anónimo de Git y regresarán a la configuración predeterminada inhabilitada. Si un repositorio bifurcado se convierte en público, los administradores del repositorio pueden volver a habilitar el acceso de lectura anónimo de Git. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". +{% endif %} + +##### Eliminar el repositorio privado + +Si un repositorio público se convierte en privado, y después se elimina, sus bifurcaciones públicas continuarán existiendo en una red separada. + +#### Convertir un repositorio privado en un repositorio público + +Si un repositorio privado se convierte en público, cada una de sus bifurcaciones se convierte en un repositorio privado independiente y se vuelve el padre de su propia red de repositorio nueva. Las bifurcaciones privadas nunca se convierten en públicas automáticamente ya que podrían contener confirmaciones confidenciales que no deberían divulgarse públicamente. + +##### Eliminar el repositorio público + +Si un repositorio privado se convierte en público y después se elimina, sus bifurcaciones privadas continuarán existiendo como repositorios privados independientes en redes separadas. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} + +#### Cambiar la visibilidad de un repositorio interno + +{% note %} + +**Nota:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Si la política deSi la política para tu empresa permite las bifurcaciones, cualquier bifurcación de un repositorio interno será privada. Si cambias la visibilidad de un repositorio interno, cualquier bifurcación que pertenezca a una cuenta de organización o de usuario permanecerá como privada. + +##### Borrar el repositorio interno + +Si cambias la visibilidad de un repositorio interno y luego lo borras, las bifurcaciones seguirán existiendo en una red separada. + +{% endif %} + +### Further reading + +- "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)" +- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" +- "[Administrar la política de bifurcación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "{% if currentVersion == "free-pro-team@latest" %}[Requerir políticas de administración de repositorios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md new file mode 100644 index 0000000000000..8eae498f1903c --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md @@ -0,0 +1,12 @@ +--- +title: Trabajar con bifurcaciones +intro: 'Las bifurcaciones se suelen usar en desarrollo de código abierto en {% data variables.product.product_name %}.' +mapTopic: verdadero +redirect_from: + - /articles/working-with-forks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md new file mode 100644 index 0000000000000..02b1c7292a401 --- /dev/null +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -0,0 +1,30 @@ +--- +title: Trabajar con ganchos de pre-recepción +intro: 'Los *ganchos de pre-recepción* hacen cumplir las reglas para las contribuciones antes de que las confirmaciones se puedan subir a un repositorio.' +redirect_from: + - /articles/working-with-pre-receive-hooks +versions: + enterprise-server: '*' +--- + +Los ganchos de pre-recepción ejecutan pruebas en código que se suben a un repositorio para asegurar que las contribuciones cumplan con las políticas del repositorio o de la organización. Si los contenidos de la confirmación pasan las pruebas, se aceptará que se suban al repositorio. Si los contenidos de la confirmación no pasan las pruebas, no se aceptará que se suban al repositorio. + +Si no se acepta tu subida, verás un mensaje de error que corresponde al gancho de pre-recepción fallido. + +``` +$ git push +Counting objects: 3, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (2/2), done. +Writing objects: 100% (3/3), 916 bytes | 0 bytes/s, done. +Total 3 (delta 0), reused 0 (delta 0) +remote: always_reject.sh: failed with exit status 1 +remote: error: rejecting all pushes +To https://54.204.174.51/hodor/nope.git + ! [remote rejected] main -> main (pre-receive hook declined) +error: failed to push some refs to 'https://54.204.174.51/hodor/nope.git' +``` + +![Mensaje de error para gancho de pre-recepción fallido](/assets/images/help/pull_requests/pre-receive-hook-failed-error.png) + +Tu {% data variables.product.product_name %} administrador del sitio puede crear y eliminar ganchos de pre-recepción para tu organización o repositorio y puede permitirle a los administradores de la organización o del repositorio habilitar o inhabilitar ganchos de pre-recepción. Para obtener más información, consulta "[Usar ganchos de pre-recepción para implementar políticas](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy)." diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md new file mode 100644 index 0000000000000..ea6a7051eb717 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md @@ -0,0 +1,25 @@ +--- +title: Acerca de las confirmaciones +intro: Puedes guardar grupos pequeños de cambios significativos como confirmaciones. +redirect_from: + - /articles/why-are-my-commits-in-the-wrong-order + - /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las confirmaciones + +{% data reusables.commits.about-commits %} + +Puedes agregar un co-autor en cualquier confirmación en la que colabores. Para obtener más información, consulta "[Crear una confirmación con múltiples autores](/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors)". + +{% if currentVersion == "free-pro-team@latest" %} +También puedes crear una confirmación en nombre de una organización. Para obtener más información, consulta la sección "[Crear una confirmación en nombre de una organización](/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization)".{% endif %} + +El rebase te permite cambiar varias confirmaciones y puede modificar el órden de éstas en tu línea de tiempo. Para obtener más información, consulta la sección [Accerca del rebase de Git](/github/using-git/about-git-rebase)". + +### Further reading +- "[Confirmar y revisar los cambios a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" en {% data variables.product.prodname_desktop %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md b/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md new file mode 100644 index 0000000000000..0d44701a5a76e --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md @@ -0,0 +1,121 @@ +--- +title: Cambiar un mensaje de confirmación +redirect_from: + - /articles/can-i-delete-a-commit-message/ + - /articles/changing-a-commit-message +intro: 'Si un mensaje de confirmación contiene información poco clara, incorrecta o confidencial, puedes modificarlo localmente y subir una nueva confirmación con un nuevo mensaje para {% data variables.product.product_name %}. También puedes cambiar un mensaje de confirmación para agregar la información faltante.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Volver a escribir el mensaje de confirmación más reciente + +Puedes cambiar el mensaje de confirmación más reciente usando el comando `git commit --amend`. + +En Git, el texto del mensaje de confirmación es parte de la confirmación. Cambiar el mensaje de la confirmación cambiará la commit ID-- es decir, el checksum de SHA1 que designa la confirmación. Efectivamente, estás creando una nueva confirmación que reemplaza a la anterior. + +### La confirmación no se ha subido en línea + +Si la confirmación solo existe en tu repositorio local y no se ha subido a {% data variables.product.product_location %}, puedes modificar el mensaje de confirmación con el comando `git commit --amend`. + +1. En la línea de comando, desplázate hasta el repositorio que contiene la confirmación que deseas modificar. +2. Escribe `git commit --amend` y presiona **Enter** (Intro). +3. En tu editor de texto, edita el mensaje de confirmación y guarda la confirmación. + - Puedes agregar un coautor al agregar una introducción a la confirmación. Para obtener más información, consulta "[Crear una confirmación con múltiples autores](/articles/creating-a-commit-with-multiple-authors)". +{% if currentVersion == "free-pro-team@latest" %} + - Puedes crear confirmaciones en nombre de tu organización agregando una introducción al mensaje de la confirmación. Para obtener más información, consulta "[Crear una confirmación en nombre de una organización](/articles/creating-a-commit-on-behalf-of-an-organization)" +{% endif %} + +El nuevo mensaje y la confirmación aparecerán en {% data variables.product.product_location %} la próxima vez que subas un cambio. + +{% tip %} + +Puedes cambiar el editor de texto predeterminado para Git si cambias el parámetro `core.editor`. Para obtener más información, consulta la sección "[Configuración Básica del Cliente](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" en el manual de Git. + +{% endtip %} + +### Medificar mensajes de confirmación antiguos o múltiples + +Si ya subiste la confirmación a {% data variables.product.product_location %}, tendrás que subir forzadamente una confirmación con un mensaje modificado. + +{% warning %} + +Desalentamos enfáticamente que se realicen subidas forzadas, dado que esto cambia el historial de tu repositorio. Si haces subidas forzadas, las personas que ya hayan clonado tu repositorio tendrán que arreglar su historial local manualmente. Para obtener más información, consulta la sección "[Recuperarse de un rebase ascendente](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" en el manual de Git. + +{% endwarning %} + +**Cambiar el mensaje de la confirmaciòn subida màs recientemente** + +1. Sigue los [pasos anteriores](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) para modificar el mensaje de confirmación. +2. Usa el comando `push --force` para realizar un empuje forzado sobre la confirmación anterior. + ```shell + $ git push --force example-branch + ``` + +**Cambiar el mensaje de los mensajes de confirmaciòn mùtilples o del màs antiguo** + +Si necesitas modificar el mensaje de varias confirmaciones o de una confirmación antigua, puedes utilizar un rebase interactivo y luego hacer una subida forzada para cambiar el historial de la confirmación. + +1. En la línea de comando, desplázate hasta el repositorio que contiene la confirmación que deseas modificar. +2. Usa el comando `git rebase -i HEAD~n` para mostrar una lista de las últimas confirmaciones `n` en tu editor de texto predeterminado. + + ```shell + # Displays a list of the last 3 commits on the current branch + $ git rebase -i HEAD~3 + ``` + La lista se verá parecida a la siguiente: + + ```shell + pick e499d89 Delete CNAME + pick 0c39034 Better README + pick f7fde4a Change the commit message but push the same commit. + + # Rebase 9fdb3bd..f7fde4a sobre 9fdb3bd + # + # Comandos: + # p, escoger = usar confirmación + # r, volver a redactar = usar confirmación, pero editar el mensaje de confirmación + # e, editar = usar confirmación, pero detener la modificación + # s, machacar = usar confirmación, pero fusionarla con la confirmación anterior + # f, arreglar = como "machacar", pero descartar el mensaje de registro de confirmación + # x, exec = ejecutar comando (el resto de la línea) usando shell + # + # Estas líneas pueden reordenarse, pero se ejecutan desde arriba hacia abajo. + # + # Si eliminas una línea aquí ESA CONFIRMACIÓN SE PERDERÁ. + # Sin embargo, si eliminas todo, la rebase será interrumpida. + # + # Note that empty commits are commented out + ``` +3. Reemplaza `pick` (escoger) por `reword` (volver a redactar) antes de cada mensaje de confirmación que desees cambiar. + ```shell + pick e499d89 Delete CNAME + reword 0c39034 Better README + reword f7fde4a Change the commit message but push the same commit. + ``` +4. Guardar y cerrar el archivo con la lista de confirmaciones. +5. En cada archivo de confirmación resultante, escribe el nuevo mensaje de confirmación, guarda el archivo, y ciérralo. +6. Cuando estès listo para subir tus cambios a GitHub, utiliza el comando push --force para subir el cambio forzadamente sobre la confirmaciòn antigua. +```shell +$ git push --force example-branch +``` + +Para obtener más información sobre el rebase interactivo, consulta la sección "[Modo interactivo](https://git-scm.com/docs/git-rebase#_interactive_mode)" en el manual de Git. + +{% tip %} + +Como se mencionó anteriormente, el modificar el mensaje de confirmación dará como resultado una confirmación nueva con una ID nueva. Sin embargo, en este caso, cada confirmación que siga a la confirmación modificada también obtendrá una ID nueva, ya que cada confirmación contiene también la id de su padre. + +{% endtip %} + +{% warning %} + +Si incluiste información sensible en un mensaje de confirmación, el subir dicha confirmación forzadamente con una confirmación modificada no eliminará la confirmación original de {% data variables.product.product_name %}. La confirmación anterior no será parte del clon siguiente; sin embargo, es posible que siga almacenada en el caché de {% data variables.product.product_name %} y que se pueda acceder a ella a través de la ID de la confirmación. Debes contactar a {% data variables.contact.contact_support %} con la ID de confirmación anterior para que la purguen del repositorio remoto. + +{% endwarning %} + +### Further reading + +* "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md b/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md new file mode 100644 index 0000000000000..e815b578628cc --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md @@ -0,0 +1,23 @@ +--- +title: Confirmar rama y etiquetas +intro: Puedes ver fácilmente qué rama es una confirmación al mirar las etiquetas debajo de la confirmación en la página de confirmación. +redirect_from: + - /articles/commit-branch-and-tag-labels +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si tu confirmación no está en la rama predeterminada, un indicador mostarará las ramas que contienen la confirmación. Si la confirmación es parte de una solicitud de extracción no fusionada, mostrará un enlace. + +![Etiqueta Commit branch (Confirmar rama)](/assets/images/help/commits/Commit-branch-label.png) + +Una vez que la confirmación está en la rama por defecto, todas las etiquetas que contienen la confirmación se mostrarán y la rama por defecto será la única rama enumerada. + +![Commit-main-label](/assets/images/help/commits/Commit-master-label.png) + +### Further reading + +* "[Firmar confirmaciones](/articles/signing-commits)" +* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md new file mode 100644 index 0000000000000..fd4177faf3352 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md @@ -0,0 +1,78 @@ +--- +title: La confirmación existe en GitHub pero no en mi clon local +intro: 'Algunas veces una confirmación estará visible en {% data variables.product.product_name %}, pero no existirá en tu clon local del repositorio.' +redirect_from: + - /articles/commit-exists-on-github-but-not-in-my-local-clone +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando usas `git show` para ver una confirmación específica en la línea de comando, puedes obtener un error fatal. + +Por ejemplo, puedes recibir un error `bad object` localmente: + +```shell +$ git show 1095ff3d0153115e75b7bca2c09e5136845b5592 +> fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592 +``` + +Sin embargo, cuando ves la confirmación en {% data variables.product.product_location %}, podrás verla sin problemas: + +`github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592` + +Existen varias explicaciones posibles: + +* El repositorio local está desactualizado. +* La rama que contiene la contiene la confirmación fue eliminada, por lo que ya no se hace referencia a la confirmación. +* Alguien realizó un empuje forzado sobre la confirmación. + +### El repositorio local está desactualizado + +Es posible que tu repositorio local aún no esté confirmado. Para obtener información desde tu repositorio remoto hasta tu clon local, usa `git fetch`: + +```shell +$ git fetch remote +``` + +Esto copia información de manera segura desde el repositorio remoto hasta tu clon local sin hacer cambios a los archivos que has revisado. Puedes usar `git fetch upstream` para obtener información desde un repositorio que has bifurcado o `git fetch origin` para obtener información desde un repositorio que solo has clonado. + +{% tip %} + +**Sugerencia**: Para obtener información, lee sobre [cómo administrar remotos y extraer datos](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) en el libro [Pro Git](https://git-scm.com/book). + +{% endtip %} + +### La rama que contenía la confirmación fue eliminada + +Si un colaborador del repositorio ha eliminado la rama que contiene la confirmación o ha realizado un empuje forzado sobre la rama, es posible que la confirmación faltante haya quedado huérfana (es decir, no puede ser alcanzado desde cualquier referencia) y, por lo tanto, no se extraerá en tu clon local. + +Afortunadamente, si un colaborador tiene un clon local del repositorio con la confirmación faltante, puede volver a forzarla en {% data variables.product.product_name %}. Necesitan asegurarse de que la confirmación sea utilizada como referencia por parte de una rama local y que luego la suban como una rama nueva a {% data variables.product.product_name %}. + +Digamos que la persona todavía tiene una rama local (llamémosla `B`) que contiene la confirmación. Esto puede realizar el seguimiento de la rama que tuvo un empuje forzado o eliminado y que simplemente todavía no han actualizado. Para preservar la confirmación, pueden subir esa rama local a una rama nueva (llamémosla `recover-B`) en {% data variables.product.product_name %}. Para este ejemplo, supongamos que tienen un remoto denominado `ascendente` mediante el cual tienen acceso de escritura a `github.com/$account/$repository`. + +La otra persona ejecuta: + +```shell +$ git branch recover-B B +# Crea una nueva rama local que hace referencia a la confirmación +$ git push upstream B:recover-B +# Sube la B local a la nueva rama ascendente, creando una nueva referencia a la confirmación +``` + +Ahora, *tú* puedes ejecutar: + +```shell +$ git fetch upstream recover-B +# Crea la confirmación en tu repositorio local. +``` + +### Evitar empujes forzados + +Evita los empujes forzados a un repositorio a menos que sea absolutamente necesario. Esto es especialmente cierto si más de una persona puede subir al repositorio. + +### Further reading + +- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- ["Recuperación de datos" sde el libro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md new file mode 100644 index 0000000000000..288f224f37bbc --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md @@ -0,0 +1,64 @@ +--- +title: Comparar confirmaciones +redirect_from: + - /articles/comparing-commits-across-time + - /github/committing-changes-to-your-project/comparing-commits-across-time +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes comparar el estado de tu repositorio a través de ramas, etiquetas, confirmaciones de cambios y fechas. Para comparar versiones diferentes de tu repositorio, añade `/compare` a la ruta del mismo. + +Demostraremos el poder de Compare (Comparar) al observar la página de comparación para [una bifurcación del repositorio Lingüista](https://github.com/octocat/linguist), que está en [https://github.com/octocat/linguist/compare/master...octocat:master](https://github.com/octocat/linguist/compare/master...octocat:master). + +Cada vista Compare (Comparar) del repositorio contiene dos menús desplegables: `base` y `compare`. + +`base` debería ser considerado como punto de partida de tu comparación, d `compare` es el punto final. Durante una comparación, siempre puedes cambiar tus puntos `base` y `compare` al hacer clic en **Edit** (Editar). + +### Comparar ramas + +El uso más común de "Compare" es comparar ramas, tal como cuando estás iniciando una solicitud de extracción nueva. Siempre se te llevará a la vista de comparación de ramas cuando inicies una [solicitud de extracción nueva](/articles/creating-a-pull-request). + +Para comparar ramas, puedes seleccionar un nombre de rama desde el menú desplegable `compare` en la parte superior de la página. + +Aquí hay un ejemplo de una [comparación entre dos ramas](https://github.com/octocat/linguist/compare/master...octocat:an-example-comparison-for-docs). + +### Comparar etiquetas + +Cuando compares etiquetas de lanzamiento se te mostrarán los cambios que se han realizado a tu repositorio desde el último lanzamiento. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Comparar lanzamientos](/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" %}Para comparar etiquetas, puedes seleccionar el nombre de una de ellas desde el menú desplegable de `compare` en la parte superior de la página.{% else %} en vez de teclear el nombre de rama, teclea el nombre de tu etiqueta en el menú desplegable de `compare`.{% endif %} + +Aquí hay un ejemplo de una [comparación entre dos etiquetas](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). + +### Comparar confirmaciones + +También puedes comparar dos confirmaciones arbitrarias en tu repositorio o sus bifurcaciones en {% data variables.product.prodname_dotcom %} en una comparación de diferencias de dos puntos. + +Para comparar rápidamente dos confirmaciones en Git Object IDs (OID por sus siglas en inglés) directamente entre sí en una comparación de diferencias de dos puntos en {% data variables.product.prodname_dotcom %}, edita la URL de la página "Comparing changes" (Comparar cambios) en tu repositorio. + +{% data reusables.repositories.two-dot-diff-comparison-example-urls %} + +Para obtener más información sobre otras opciones de comparación, consulta "[Comparaciones de diferencia de tres puntos y dos puntos](/articles/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons)". + +### Comparar entre bifurcaciones + +Puedes comparar tu repositorio base y otro repositorio bifurcado. Esta es la vista que se presenta cuando un usuario realiza una Solicitud de extracción a un proyecto. + +Para comparar ramas en repositorios diferentes, antepone los nombres de la rama con los nombres del usuario. Por ejemplo, si especificas `octocat:main` para `base` y `octo-org:main` para `compare`, puedes comparar la rama `main` de los repositorios que pertenezcan a `octocat` y a `octo-org` respectivamente. + +Aquí hay un ejemplo de una [comparación entre dos repositorios](https://github.com/octocat/linguist/compare/master...octo-org:master). + +### Comparaciones entre confirmaciones + +A modo de atajo, Git usa la notación `^` para referirse a "una confirmación anterior". + +Puedes usar esta notación para comparar una sola confirmación o rama con sus predecesores inmediatos. Por ejemplo, `96d29b7^^^^^` indica cinco confirmaciones anteriores a `96d29b7`, porque hay cinco marcas `^`. Si escribes `96d29b7^^^^^` en la rama `base` y `96d29b7` en la rama `compare` se compararán las cinco confirmaciones que se hicieron antes de `96d29b7` con la confirmación `96d29b7`. + +Aquí hay un ejemplo de una [comparación usando la notación `^`](https://github.com/octocat/linguist/compare/octocat:96d29b7%5E%5E%5E%5E%5E...octocat:96d29b7). + +### Further reading + +- "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md new file mode 100644 index 0000000000000..9ad4f60f0eaf6 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -0,0 +1,71 @@ +--- +title: Crear una confirmación en nombre de una organización +intro: 'Puedes crear confirmaciones en nombre de una organización agregando una introducción al mensaje de la confirmación. Las confirmaciones atribuidas a una organización incluyen un distintivo `on-behalf-of` (en nombre de) en {% data variables.product.product_name %}.' +redirect_from: + - /articles/creating-a-commit-on-behalf-of-an-organization +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** La capacidad de crear una confirmación en nombre de una organización se encuentra actualmente en la versión beta de acceso público y está sujeta a modificaciones. + +{% endnote %} + +Para crear confirmaciones en nombre de una organización: + +- debes ser miembro de la organización indicada en la introducción +- debes firmar la confirmación +- tu correo electrónico de confirmación y el correo electrónico de la organización debe estar dentro de un dominio verificado por la organización +- tu mensaje de confirmación debe finalizar con la introducción de la confirmación `on-behalf-of: @org ` + - `org` es el inicio de sesión de la organización + - `name@organization.com` se encuentra en el dominio de la organización + +Las organizaciones pueden usar el correo electrónico `name@organization.com` como punto de contacto público para los esfuerzos de código abierto que se hagan. + +### Crear confirmaciones con un distintivo `on-behalf-of` en la línea de comando + +1. Teclea tu mensaje de confirmación y una descripción corta y significativa sobre tus cambios. Después de tu descripción de la confirmación, en vez de cerrar las comillas, agrega dos líneas vacías. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} + +2. En la línea siguiente del mensaje de confirmación, escriba `on-behalf-of: @org ` y luego coloque comillas de cierre. + + ```shell + $ git commit -m "Refactor usability tests. + > + > + on-behalf-of: @org <name@organization.com>" + ``` + +El nuevo mensaje de confirmación y el distintivo aparecerán en {% data variables.product.product_location %} la próxima vez que subas un cambio. Para obtener más información, consulta "[Subir cambios a un repositorio remoto](/articles/pushing-commits-to-a-remote-repository/)." + +### Crear confirmaciones con un distintivo `on-behalf-of` en {% data variables.product.product_name %} + +Una vez que hayas realizado los cambios en un archivo usando el editor web en {% data variables.product.product_name %}, puedes crear una confirmación en nombre de tu organización agregando una introducción `on-behalf-of:` al mensaje de confirmación. + +1. Luego de hacer tus cambios, en la parte inferior de la página, escribe un mensaje de confirmación breve y significativo que describa tus cambios. ![Mensaje de confirmación de tu cambio](/assets/images/help/repository/write-commit-message-quick-pull.png) + +2. En el cuadro de texto que aparece debajo de tu mensaje de confirmación, agrega `on-behalf-of: @org `. + + ![Ejemplo de introducción de mensaje de confirmación on-behalf-of en el segundo cuadro de texto para el mensaje de confirmación](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) +4. Haz clic en **Confirmar cambios** o **Proponer cambios**. + +La confirmación, el mensaje y el distintivo nuevos aparecerán en {% data variables.product.product_location %}. + +### Further reading + +- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" +- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" +- "[Ver un resumen de la actividad del repositorio](/articles/viewing-a-summary-of-repository-activity)" +- "[Ver los colaboradores de un proyecto](/articles/viewing-a-projects-contributors)" +- "[Cambiar un mensaje de confirmación](/articles/changing-a-commit-message)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md new file mode 100644 index 0000000000000..8ca96eb4fde92 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -0,0 +1,87 @@ +--- +title: Crear una confirmación con distintos autores +intro: 'Puedes atribuir una confirmación a más de un autor agregando una o más introducciones `Co-authored-by` al mensaje de la confirmación. Las confirmaciones conjuntas pueden verse en {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} y pueden incluirse en la gráfica de contribuciones del perfil y en la estadística del repositorio{% endif %}.' +redirect_from: + - /articles/creating-a-commit-with-multiple-authors +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Información del coautor requerida + +Antes de agregar un coautor a una confirmación, debes saber el correo electrónico correcto para usar con cada coautor. Para que la confirmación del coautor se considere como una contribución, debes usar el correo electrónico asociado con su cuenta {% data variables.product.product_name %}. + +{% if currentVersion == "free-pro-team@latest" %} + +Si una persona elige mantener la privacidad de su dirección de correo electrónico, debes usar su correo electrónico `no-reply` proporcionado por {% data variables.product.product_name %} para proteger su privacidad. Si no lo haces, el correo electrónico del coautor estará disponible para el público en el mensaje de confirmación. Si deseas mantener la privacidad de tu correo electrónico, puedes optar por usar un correo electrónico `no-reply` proporcionado por {% data variables.product.product_name %} para las operaciones Git y solicitar a los otros coautores que incluyan tu correo electrónico `no-reply` en las introducciones de cada confirmación. + +Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". + + {% tip %} + + **Sugerencia:** Puedes ayudar a un coautor a encontrar una dirección de correo electrónico de su preferencia compartiendo esta información: + - Para encontrar tu correo electrónico `no-reply` proporcionado por {% data variables.product.product_name %} dirígete a la página de configuración de tu correo electrónico en "Mantener la privacidad de mi dirección de correo electrónico". + - Para encontrar el correo electrónico que usaste para configurar Git en tu computadora, ejecuta `git config user.email` en la línea de comando. + + {% endtip %} + +{% endif %} + +### Crear confirmaciones conjuntas usando {% data variables.product.prodname_desktop %} + +Puedes usar {% data variables.product.prodname_desktop %} para crear una confirmación con un coautor. Para obtener más información, consulta "[Escribe un mensaje de confirmación y sube tus cambios](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" y [{% data variables.product.prodname_desktop %}](https://desktop.github.com). + +![Agregar un coautor al mensaje de confirmación](/assets/images/help/desktop/co-authors-demo-hq.gif) + +### Crear confirmaciones conjuntas en la línea de comando + +{% data reusables.pull_requests.collect-co-author-commit-git-config-info %} + +1. Teclea tu mensaje de confirmación y una descripción corta y significativa sobre tus cambios. Después de tu descripción de la confirmación, en vez de cerrar las comillas, agrega dos líneas vacías. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** Si utilizas un editor de texto en la línea de comandos para teclear tu mensaje de confirmación, asegúrate de que existen dos líneas nuevas entre el final de la descripción y el indicador `Co-authored-by:`. + + {% endtip %} + +3. En la línea siguiente del mensaje de confirmación, escribe `Co-authored-by:name ` con información específica para cada coautor. Luego de la información del coautor, agrega comillas de cierre. + + Si estás agregando distintos coautores, asigna una línea y una introducción de la confirmación `Co-authored-by` a cada coautor. + ```shell + $ git commit -m "Refactor usability tests. + > + > + Co-authored-by: name <name@example.com> + Co-authored-by: another-name <another-name@example.com>" + ``` + +El nuevo mensaje y la confirmación aparecerán en {% data variables.product.product_location %} la próxima vez que subas un cambio. Para obtener más información, consulta "[Subir cambios a un repositorio remoto](/articles/pushing-commits-to-a-remote-repository/)." + +### Crear confirmaciones conjuntas en {% data variables.product.product_name %} + +Una vez que hayas realizado los cambios en un archivo usando el editor web en {% data variables.product.product_name %}, puedes crear una confirmación conjunta agregando una introducción `Co-authored-by:` al mensaje de confirmación. + +{% data reusables.pull_requests.collect-co-author-commit-git-config-info %} +2. Luego de hacer tus cambios de forma conjunta, en la parte inferior de la página, escribe un mensaje de confirmación breve y significativo que describa los cambios que realizaste. ![Mensaje de confirmación de tu cambio](/assets/images/help/repository/write-commit-message-quick-pull.png) +3. En el cuadro de texto que aparece debajo de tu mensaje de confirmación, agrega `Co-authored-by:name ` con información específica para cada coautor. Si estás agregando distintos coautores, asigna una línea y una introducción de la confirmación `Co-authored-by` a cada coautor. + + ![Ejemplo de introducción de coautor del mensaje de confirmación en el cuadro de texto para el mensaje de confirmación](/assets/images/help/repository/write-commit-message-co-author-trailer.png) +4. Haz clic en **Confirmar cambios** o **Proponer cambios**. + +La confirmación y el mensaje nuevos aparecerán en {% data variables.product.product_location %}. + +### Further reading +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" +- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} +- "[Ver un resumen de la actividad del repositorio](/articles/viewing-a-summary-of-repository-activity)" +- "[Ver los colaboradores de un proyecto](/articles/viewing-a-projects-contributors)" +- "[Cambiar un mensaje de confirmación](/articles/changing-a-commit-message)" +- "[Confirmar y revisar los cambios en tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" en la documentación de {% data variables.product.prodname_desktop %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md new file mode 100644 index 0000000000000..744b380843401 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md @@ -0,0 +1,12 @@ +--- +title: Crear y editar confirmaciones de cambios +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/creating-and-editing-commits +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md b/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md new file mode 100644 index 0000000000000..f17cb5f0d6e74 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md @@ -0,0 +1,29 @@ +--- +title: Diferencias entre las vistas de las confirmaciones +redirect_from: + - /articles/differences-between-commit-views +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +En {% data variables.product.product_name %}, puedes ver el historial de confirmaciones de un repositorio al: + +- Navegar directamente hasta [la página de confirmaciones](https://github.com/mozilla/rust/commits/master) de un repositorio +- Hacer clic en un archivo y luego hacer clic en **History** (Historial), para ir al [historial de confirmaciones para un archivo específico](https://github.com/mozilla/rust/commits/master/README.md) + +Es posible que estas dos vistas de confirmación muestren información _diferente_ ocasionalmente. El historial de un archivo único puede omitir confirmaciones que se encuentran en el historial de confirmaciones del repositorio. + +Git tiene diferentes maneras de mostrar el historial de un repositorio. Cuando Git muestra el historial de un archivo único, lo "simplifica" omitiendo las confirmaciones que no generaron cambios en el archivo. En lugar de analizar todas las confirmaciones para decidir si afectaron el archivo o no, Git omitirá la rama completa en caso de que esta, cuando se fusionó, no haya tenido impacto en el contenido final del archivo. No se muestra ninguna confirmación en la rama que haya afectado el archivo. + +Para el historial de confirmaciones de un archivo, {% data variables.product.product_name %} sigue explícitamente esta estrategia simple. Simplifica el historial al eliminar las confirmaciones que en realidad no contribuyen al resultado final. Por ejemplo, si una rama lateral ha realizado un cambio y luego lo ha revertido, esa confirmación no se mostrará en el historial de la rama. Esto permite que la revisión de las ramas sea más eficiente, dado que solo ves las confirmaciones que afectan al archivo. + +Ws posible que esta vista truncada no contenga la información que estás buscando. Si deseas ver el historial completo, {% data variables.product.product_name %} proporciona una vista con más información acerca de la página de confirmaciones de un repositorio. + +Para obtener más información acerca de cómo Git considera el historial de confirmaciones, consulta la sección [ "Simplificación del historial"](https://git-scm.com/docs/git-log#_history_simplification) del artículo de ayuda de `git log`. + +### Further reading + +- "[Firmar confirmaciones](/articles/signing-commits)" +- "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/index.md b/translations/es-ES/content/github/committing-changes-to-your-project/index.md new file mode 100644 index 0000000000000..8475e9424f82d --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/index.md @@ -0,0 +1,27 @@ +--- +title: Confirmar cambios en su proyecto +redirect_from: + - /categories/21/articles/ + - /categories/commits/ + - /categories/committing-changes-to-your-project +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /creating-and-editing-commits %} + {% link_in_list /about-commits %} + {% link_in_list /creating-a-commit-with-multiple-authors %} + {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} + {% link_in_list /changing-a-commit-message %} +{% topic_link_in_list /viewing-and-comparing-commits %} + {% link_in_list /commit-branch-and-tag-labels %} + {% link_in_list /comparing-commits %} + {% link_in_list /differences-between-commit-views %} +{% topic_link_in_list /troubleshooting-commits %} + {% link_in_list /commit-exists-on-github-but-not-in-my-local-clone %} + {% link_in_list /why-are-my-commits-linked-to-the-wrong-user %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md new file mode 100644 index 0000000000000..8d57b5b5f36ff --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md @@ -0,0 +1,12 @@ +--- +title: Confirmaciones de solución de problemas +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/troubleshooting-commits +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md new file mode 100644 index 0000000000000..035327d3b62f4 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md @@ -0,0 +1,12 @@ +--- +title: Ver y comparar confirmaciones de cambios +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/viewing-and-comparing-commits +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md new file mode 100644 index 0000000000000..c0e0a16849bd9 --- /dev/null +++ b/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -0,0 +1,54 @@ +--- +title: '¿Por qué mis confirmaciones están vinculadas al usuario incorrecto?' +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 %} usa la dirección de correo electrónico en el encabezado de la confirmación para vincular la confirmación con un usuario de GitHub. Si tus confirmaciones se están vinculando con otro usuario o no se pueden vincular con alguno de ellos, puede que necesites cambiar los ajustes de tu configuración local de Git{% if currentVersion != "github-ae@latest" %}, agrega una dirección de correo electrónico a los ajustes de correo electrónico de tu cuenta, o haz ambos{% endif %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +{% tip %} + +**Nota**: Si tus confirmaciones se vinculan con otro usuario, eso no significa que el usuario puede acceder a tu repositorio. Un usuario solo puede acceder a un repositorio de tu propiedad si lo agregas como colaborador o lo agregas a un equipo que tiene acceso al repositorio. + +{% endtip %} + +### Las confirmaciones se vinculan con otro usuario + +Si tus confirmaciones están vinculadas a otro usuario, eso significa que la dirección de correo electrónico en tus ajustes de configuración locales de git están conectados a esa cuenta de usuario en {% data variables.product.product_name %}. En este caso, puedes cambiar el correo electrónico en los ajustes de tu configuración local de Git{% if currentVersion == "github-ae@latest" %} a la dirección asociada con tu cuenta en {% data variables.product.product_name %} para vincular tus confirmaciones subsecuentes. Las confirmaciones antiguas no se vincularán. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %} y agregar una dirección de correo electrónico nueva a tu cuenta de {% data variables.product.product_name %} para vincular confirmaciones futuras a tu cuenta. + +1. Para cambiar la dirección de correo electrónico en tu configuración local de Git, sigue los pasos en "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Si trabajas en máquinas múltiples, necesitarás cambiar esta configuración en cada una de ellas. +2. Agrega la dirección de correo electrónico del paso 2 los ajustes de tu cuenta siguiendo los pasos en "[Agregar una dirección de correo electrónico a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %} + +Las confirmaciones que haces desde este punto en adelante se vincularán con tu cuenta. + +### Las confirmaciones no se vinculan con ningún usuario + +Si tus confirmaciones de cambios no se vinculan con ningún usuario, el nombre del autor de las mismas no se mostrará como un enlace a un perfil de usuario. + +Para revisar la dirección de correo electrónico que se usó para esas confirmaciones y conectar las confirmaciones con tu cuenta, sigue los siguientes pasos: + +1. Desplázate hasta la confirmación haciendo clic en el enlace del mensaje de confirmación. ![Enlace de mensaje de confirmación](/assets/images/help/commits/commit-msg-link.png) +2. Para leer un mensaje acerca del porqué la confirmación no se vinculó, pasa el puntero sobre el {% octicon "question" aria-label="Question mark" %} azul a la derecha del nombre de usuario. ![Mensaje de confirmación con el puntero](/assets/images/help/commits/commit-hover-msg.png) + + - **Unrecognized author (con una dirección de correo electrónico)** Si ves este mensaje con una dirección de correo electrónico, la dirección que utilizaste para hacer la confirmación no está conectada con tu cuenta en {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}Para enlazar tus confirmaciones, [agrega la dirección de correo electrónico a tus ajustes de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %} Si la dirección de correo electrónico tiene un Gravatar asociado con ella, éste se mostrará junto a la confirmación en vez de el Octocat gris predeterminado. + - **Unrecognized author (sin dirección de correo electrónico)** Si ves este mensaje sin una dirección de correo electrónico, utilizaste una dirección de correo electrónico genérica que no puede conectarse con tu cuenta en {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} Necesitarás [configurar tu dirección de correo electrónico para confirmaciones en Git](/articles/setting-your-commit-email-address) y luego [agregar la dirección nueva a tus ajustes de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account) para enlazar tus confirmaciones subsecuentes. No se vincularán las confirmaciones antiguas.{% endif %} + - **Invalid email** La dirección de correo electrónico en los ajustes de tu configuración local de Git es ya sea nual o no tiene el formato de una dirección de correo electrónico.{% if currentVersion != "github-ae@latest" %} Necesitarás [configurar tu dirección de correo electrónico para confirmaciones en git](/articles/setting-your-commit-email-address), y luego [Agregar la nueva dirección de correo electrónico en tus ajustes de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular tus confirmaciones subsecuentes. No se vincularán las confirmaciones antiguas.{% endif %} + +{% if currentVersion == "github-ae@latest" %} +Puedes cambiar el correo electrónico en tus ajustes de configuración local de Git a la dirección asociada con tu cuenta para vincular tus confirmaciones subsecuentes. Las confirmaciones antiguas no se vincularán. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". +{% endif %} + +{% warning %} + +Si tu configuración de Git local contiene una dirección de correo electrónico general, o una dirección de correo electrónico que ya se adjuntó a la cuenta de otro usuario, entonces tus confirmaciones anteriores no se vincularán a tu cuenta. Si bien Git te permite cambiar la dirección de correo electrónico que usaste para confirmaciones anteriores, desaconsejamos esto totalmente, en especial en un repositorio compartido. + +{% endwarning %} + +### Further reading + +* "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md new file mode 100644 index 0000000000000..ae072a5e2c3c4 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md @@ -0,0 +1,31 @@ +--- +title: Acerca de archivar el contenido y los datos en GitHub +intro: 'Puedes archivar contenido y datos en {% data variables.product.product_name %} para que otras personas puedan verlos y hacer referencia.' +redirect_from: + - /articles/about-archiving-content-and-data-on-github +versions: + free-pro-team: '*' +--- + +### Persistencia de repositorios públicos + +{% data variables.product.product_name %} intenta mantener disponibles tus repositorios públicos, a menos que los elimines. En algunos casos, hacemos que el contenido público no esté disponible, por ejemplo si: + +- Recibimos un [aviso de retiro de DMCA](/articles/dmca-takedown-policy) para el contenido en un repositorio. +- Determinamos que el contenido de un repositorio viola nuestras [Pautas de la comunidad](/articles/github-community-guidelines) o nuestros [Términos de servicio](/articles/github-terms-of-service/). + +Académicos e investigadores pueden hacer referencia a esta información en los planes de administración de datos. + +### Acerca de {% data variables.product.prodname_archive %} + +{% data reusables.repositories.about-github-archive-program %} + +El {% data variables.product.prodname_archive %} permite que los socios terceros archiven repositorios públicos utilizando la API pública. Estos socios archivan diferentes tipos de datos en frecuencias variables y hacen que éstos estén disponibles al público. El {% data variables.product.prodname_archive %} también protege los datos constantemente al almacenar varias copias de ellos en formatos de datos y ubicaciones diversas. Por ejemplo, {% data variables.product.company_short %} almacena repositorios en el {% data variables.product.prodname_arctic_vault %}, un archivo de muy largoplazo que pretende durar por lo menos 1,000 años. Para obtener más información, consulta [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com/). + +El uso responsable de los archivos incluye respetar la privacidad de los usuarios. Para obtener más información, consulta "[Información pública sobre GitHub](/articles/github-privacy-statement/#public-information-on-github)". + +Puedes optar por que tu repositorio salga del {% data variables.product.prodname_archive %}. Para obtener más información, consulta la sección "[Optar por que tu repositorio público entre o salga del {% data variables.product.prodname_archive %}](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository)". + +### Agregar una licencia de código abierto para aumentar la capacidad de archivado + +Bibliotecas e investigadores pueden requerir protecciones legales para crear archivos de contenido disponible públicamente. Si quieres que terceros consideren tu trabajo en {% data variables.product.product_name %} para archivado, puedes agregar una [licencia de código abierto](/articles/open-source-licensing) a tus proyectos. Una licencia de código abierto le brinda a los colaboradores permisos explícitos para copiar y distribuir el material en tu repositorio. diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md new file mode 100644 index 0000000000000..6e58ee62b363d --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md @@ -0,0 +1,29 @@ +--- +title: Acerca de archivar repositorios +intro: 'Cuando archivas un repositorio, le dejas saber a las personas que un proyecto ya no se mantiene activamente.' +redirect_from: + - /articles/about-archiving-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:** Si tienes un plan de facturación por repositorio heredado, aún así se te cobrará por tu repositorio archivado. Si no quieres que se te cobre por un repositorio archivado, debes actualizar a un producto nuevo. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". + +{% endnote %} +{% endif %} + +{% data reusables.repositories.archiving-repositories-recommendation %} + +Una vez que se archiva un repositorio, no puedes agregar ni eliminar colaboradores ni equipos. Solo los colaboradores con acceso al repositorio pueden bifurcar o iniciar tu proyecto. + +Cuando se archiva un repositorio, sus propuestas, solicitudes de cambios, còdigo, etiquetas, hitos, proyectos, wiki, lanzamientos, confirmaciones, etiquetas, ramas, reacciones, alertas de escaneo de còdigo y comentarios se hacen de solo lectura. Para realizar cambios en un repositorio archivado, primero debes desarchivar el repositorio. + +Puedes buscar repositorios archivados. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". + +### Further reading +- "[Archivar repositorios](/articles/archiving-repositories)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md new file mode 100644 index 0000000000000..9ffd1f018ebab --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -0,0 +1,97 @@ +--- +title: Acerca de los propietarios del código +intro: Puedes usar un archivo CODEOWNERS para definir individuos o equipos que sean responsables del código en un repositorio. +redirect_from: + - /articles/about-codeowners/ + - /articles/about-code-owners +product: '{% data reusables.gated-features.code-owners %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos administrativos o de propietario pueden configurar un archivo CODEOWNERS en un repositorio. + +Las personas que elijas como propietarios del código deben tener permisos de escritura para el repositorio. Cuando el propietario del código es un equipo, ese equipo debe tener permisos de escritura, incluso si todos los miembros individuales del equipo ya tienen permisos de escritura, a través de la membresía de la organización o a través de la membresía de otro equipo. + +### Acerca de los propietarios del código + +Cuando alguien abre una solicitud de extracción que modifica el código que pertenece a alguien, automáticamente se les solicita una revisión a los propietarios del mismo. Lo que no se solicita automáticamente a estos propietarios es la revisión de los borradores de solicitudes de extracción. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Se notificará automáticamente a los dueños del código cuando marques un borrador de solicitud de extracción como listo para revisión. Si conviertes una solicitud de extracción en borrador, las personas que ya estén suscritas a las notificaciones no se darán de baja automáticamente. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". + +Cuando alguien con permisos administrativos o de propietario ha activado las revisiones requeridas, opcionalmente, también pueden solicitar aprobación de un propietario del código antes de que el autor pueda fusionar una solicitud de extracción en el repositorio. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si un equipo habilitó las asignaciones de revisión de código, las aprobaciones individuales no serán suficientes para el requisito de obtener la aprobación del propietario del código en una rama protegida. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/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" %} +Si un archivo tiene un propietario del código, puedes ver quién es éste antes de que abras una solicitud de extracción. En el repositorio, puedes buscar el archivo y pasar el puntero del mouse por encima +{% octicon "shield-lock" aria-label="The edit icon" %}. + +![Dueño del código de un archivo en un repositorio](/assets/images/help/repository/code-owner-for-a-file.png) +{% endif %} + +### Ubicación del archivo CODEOWNERS + +Para usar un archivo CODEOWNERS, crea un archivo nuevo llamado `CODEOWNERS` en la raíz, `docs/`, o en el directorio `.github/` del repositorio, en la rama en la que quieras agregar los propietarios del código. + +Cada archivo CODEOWNERS asigna los propietarios del código para una única rama en el repositorio. Por lo tanto, puedes asignar propietarios diferentes para el código en ramas diferentes, tal como `@octo-org/codeowners-team` para una base de código en la rama predeterminada y `@octocat` para un sitio de {% data variables.product.prodname_pages %} en la rama de `gh-pages`. + +Para que los propietarios del código reciban las solicitudes de revisión, el archivo CODEOWNERS debe estar en la rama base de la solicitud de extracción. Por ejemplo, si asignas `@octocat` como el propietario del código para los archivos *.js* en la rama `gh-pages` de tu repositorio, `@octocat` recibirá las solicitudes de revisión cuando una solicitud de extracción con cambios en los archivos *.js* se abra entre la rama de encabezado y `gh-pages`. + +### Sintáxis de CODEOWNERS + +Un archivo de CODEOWNERS utiliza un patrón que sigue la mayoría de las mismas reglas que utilizan los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), con [algunas excepciones](#syntax-exceptions). El patrón es seguido por uno o más nombres de usuarios o nombres de equipos de {% data variables.product.prodname_dotcom %} usando el formato estándar `@username` o `@org/team-name`. También puedes hacer referencia a un usuario mediante una dirección de correo electrónico que haya sido agregada a su cuenta de {% data variables.product.product_name %}, por ejemplo `user@example.com`. + +Si cualquier línea de tu archivo de CODEOWNERS contiene una sintaxi inválida, el archivo no se detectará y no se utilizará para solicitar revisiones. +#### Ejemplo de un archivo CODEOWNERS +``` +# Este es un comentario. +# Cada línea es el patrón de un archivo seguido por uno o más propietarios. + +# Estos propietarios serán los propietarios predeterminados para todo en # el repositorio. A menos que una coincidencia posterior tenga prioridad, se le solicitará # revisión a # @global-owner1 y @global-owner2 cuando alguien abra una solicitud de extracción. +* @global-owner1 @global-owner2 + +# El orden es importante; el último patrón en coincidir tiene la mayor +# prioridad. Cuando alguien abre una solicitud de extracción que solo +# modifica archivos JS, solo se le solicitará una revisión a @js-owner y no al/los # propietario(s) general(es). +*.js @js-owner + +# Si prefieres, también puedes usar direcciones de correo electrónico. Serán +# usadas para buscar usuarios como hacemos para los +# correos electrónicos del autor de la confirmación. +*.go docs@example.com + +# En este ejemplo, @doctocat posee cualquier archivo en el +# directorio build/logs en la raíz del repositorio y cualquiera de sus +# subdirectorios. +/build/logs/ @doctocat + +# El patrón `docs/*` coincidirá con archivos como +# `docs/getting-started.md` pero no con otros archivos anidados como +# `docs/build-app/troubleshooting.md`. +docs/* docs@example.com + +# En este ejemplo, @octocat posee cualquier archivo en el directorio de las apps +# en cualquier lugar en tu repositorio. +apps/ @octocat + +# In this example, @doctocat owns any file in the `/docs` +# directory in the root of your repository and any of its +# subdirectories. +/docs/ @doctocat +``` +#### Excepciones de sintaxis +Hay algunas reglas de sintaxis para los archivos de gitignore que no funcionan con los archivos de CODEOWNERS: +- Escapar un patrón que comience con `#` utilizando `\` para que se le trate como un patrón y no como un comentario +- Utilizar `!` para negar un patrón +- Utilizar `[ ]` para definir un rango de carácter + + + +### Further reading + +- "[Crear archivos nuevos](/articles/creating-new-files)" +- "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)" +- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" +- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" +- "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md new file mode 100644 index 0000000000000..73daa4f699ae7 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -0,0 +1,54 @@ +--- +title: Acerca de los archivos README +intro: 'Puedes agregar un archivo README a tu repositorio para comentarle a otras personas por qué tu proyecto es útil, qué pueden hacer con tu proyecto y cómo lo pueden usar.' +redirect_from: + - /articles/section-links-on-readmes-and-blob-pages/ + - /articles/relative-links-in-readmes/ + - /articles/about-readmes +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los archivos README + +Puedes agregar un archivo README a un repositorio para comunicar información importante sobre tu proyecto. Un README, junto con una licencia de repositorio{% if currentVersion == "free-pro-team@latest" %}, lineamientos de contribución y un código de conducta{% elsif enterpriseServerVersions contains currentVersion %} y lineamientos de contribución{% endif %}, comunica las expectativas de tu proyecto y te ayuda a administrar las contribuciones. + +Para obtener más información acerca de cómo proporcionar lineamientos para tu proyecto, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Agregar un código de conducta para tu proyecto](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" y {% endif %}"[Configurar tu proyecto para que tenga contribuciones sanas](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)". + +Un archivo README suele ser el primer elemento que verá un visitante cuando entre a tu repositorio. Los archivos README habitualmente incluyen información sobre: +- Qué hace el proyecto. +- Por qué el proyecto es útil. +- Cómo pueden comenzar los usuarios con el proyecto. +- Dónde pueden recibir ayuda los usuarios con tu proyecto +- Quién mantiene y contribuye con el proyecto. + +Si colocas tu archivo README en la raíz de tu repositorio, `docs`, o en el directorio oculto `.github`, {% data variables.product.product_name %} lo reconocerá y automáticamente expondrá tu archivo README a los visitantes del repositorio. + +![Página principal del repositorio github/scientist y su archivo 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" %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21"%} + +{% data reusables.profile.profile-readme %} + +{% endif %} + +![El archivo de README en tu nombre de usuario/repositorio de nombre de usuario](/assets/images/help/repository/username-repo-with-readme.png) + +{% endif %} + +### Enlaces de sección en los archivos README y las páginas blob + +Muchos proyectos usan un índice al comienzo de un archivo README para dirigir a los usuarios a diferentes secciones del archivo. {% data reusables.repositories.section-links %} + +### Enlaces relativos y rutas con imágenes en los archivos README + +{% data reusables.repositories.relative-links %} + +### Further reading + +- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" +- 18F's "[Hacer que los archivos README sean de lectura](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md new file mode 100644 index 0000000000000..ac853accb2c24 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -0,0 +1,41 @@ +--- +title: Acerca de los repositorios +intro: Un repositorio contiene todos los archivos de tu proyecto y el historial de revisiones de cada uno de ellos. Puedes debatir y administrar el trabajo de tu proyecto dentro del repositorio. +redirect_from: + - /articles/about-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes ser propietario de repositorios individualmente o puedes compartir la propiedad de los repositorios con otras personas en una organización. + +Puedes restringir quién tiene acceso a un repositorio seleccionando la visibilidad del mismo. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +Para los repositorios que son propiedad de un usuario, les puedes dar a otras personas acceso de colaborador para que puedan colaborar en tu proyecto. Si un repositorio es propiedad de una organización, les puedes dar a los miembros de la organización permisos de acceso para colaborar en tu repositorio. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/)" y "[Niveles de permiso de repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". + +{% if currentVersion == "free-pro-team@latest" %} +Con +{% data variables.product.prodname_free_team %} para cuentas de usuario y organizaciones, puedes trabajar con colaboradores o repositorios públicos ilimitados con un juego completo de características, o con repositorios privados ilimitados con un juego de características limitado. Para obtener herramientas avanzadas para repositorios privados, puedes mejorar tu plan a {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +{% else %} +Cada persona y organización puede tener repositorios ilimitados e invitar a un número ilimitado de colaboradores a todos ellos. +{% endif %} + +Puedes utilizar repositorios para administrar tu trabajo y colaborar con otros. +- Puedes utilizar propuestas para recolectar la retroalimentación de los usuarios, reportar errores de software y organizar las tareas que te gustaría realizar. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} +- Puedes utilizar las solicitudes de cambios para proponer cambios a un repositorio. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +- Puedes utilizar tableros de proyecto para organizar y priorizar tus propuestas y solicitudes de cambios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/github/managing-your-work-on-github/about-project-boards)." + +{% data reusables.repositories.repo-size-limit %} + +### Further reading + +- "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" +- "[Colaborar con propuestas y solicitudes de extracción](/categories/collaborating-with-issues-and-pull-requests)" +- "[Administrar tu trabajo en {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" +- "[Administrar un repositorio](/categories/administering-a-repository)" +- "[Visualizar datos del repositorio con gráficos](/categories/visualizing-repository-data-with-graphs/)" +- "[Acerca de los wikis](/articles/about-wikis)" +- "[Glosario de {% data variables.product.prodname_dotcom %}](/articles/github-glossary)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md new file mode 100644 index 0000000000000..49aa1a5531b59 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -0,0 +1,24 @@ +--- +title: Acerca de los idiomas del repositorio +intro: Los archivos y los directorios dentro de un repositorio determinan los idiomas que componen el repositorio. Puedes ver los idiomas de un repositorio para obtener una descripción general rápida del repositorio. +redirect_from: + - /articles/my-repository-is-marked-as-the-wrong-language/ + - /articles/why-isn-t-my-favorite-language-recognized/ + - /articles/my-repo-is-marked-as-the-wrong-language/ + - /articles/why-isn-t-sql-recognized-as-a-language/ + - /articles/why-isn-t-my-favorite-language-recognized-by-github/ + - /articles/about-repository-languages +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data variables.product.product_name %} utiliza la [biblioteca de Linguist](https://github.com/github/linguist) de código abierto para +determinar los lenguajes de un archivo para resaltar la sintaxis y obtener la estadística del repositorio. Las estadísticas de lenguaje se actualizarán después de que subas los cambios a tu rama predeterminada. + +Algunos archivos son difíciles de identificar y, a veces, los proyectos contienen más archivos de biblioteca y de proveedor que su código primario. Si estás recibiendo resultados incorrectos, consulta la [Guía de solución de problemas](https://github.com/github/linguist#troubleshooting) del Lingüista para obtener ayuda. + +### Lenguaje Markup + +Los lenguajes Markup están representados para HTML y mostrados en línea usando nuestra [Biblioteca Markup](https://github.com/github/markup) de código abierto. En este momento, no estamos aceptando nuevos lenguajes para mostrar dentro de {% data variables.product.product_name %}. Sin embargo, mantenemos activamente nuestros lengujes Markup actuales. Si encuentras un problema, [crea una propuesta](https://github.com/github/markup/issues/new). diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md new file mode 100644 index 0000000000000..e8df3740a4c40 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -0,0 +1,43 @@ +--- +title: Acerca de la visibilidad de un repositorio +intro: 'Puedes restringir quién tiene acceso a un repositorio si eliges la visibilidad del mismo: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} pública, interna, o privada{% elsif currentVersion == "github-ae@latest" %}privada o interna{% else %} pública o privada{% endif %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de la visibilidad de un repositorio + +{% if currentVersion == "github-ae@latest" %}Cuando creas un repositorio que pertenece a tu cuenta de usuario, éste siempre será privado. Cuando creas un repositorio que pertenece a una organización, puedes elegir hacerlo privado o interno.{% else %}Cuando creas un repositorio, puedes elegir hacerlo público o privado.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} Si estás creando el repositorio en una organización{% if currentVersion == "free-pro-team@latest" %} que pertenece a una cuenta empresarial{% endif %}, también puedes elegir hacer el repositorio interno.{% endif %}{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +Si +{% data variables.product.product_location %} no está en modo privado o detrás de un cortafuegos, cualquiera en la internet podrá acceder a los repositorios públicos. De lo contrario, los repositorios públicos estarán disponibles para cualquiera que utilice {% data variables.product.product_location %}, incluyendo a los colaboradores externos. Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados. {% if currentVersion ver_gt "enterprise-server@2.19" %} Los miembros de la empresa pueden acceder a los repositorios internos. Para obtener más información, consulta la sección "[Acerca de los repositorios internos](#about-internal-repositories)."{% endif %} +{% elsif currentVersion == "github-ae@latest" %} +Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados. Todos los miembros de la empresa pueden acceder a los repositorios internos. Para obtener más información, consulta la sección "[Acerca de los repositorios internos](#about-internal-repositories)". +{% else %} +Cualquiera en la internet puede acceder a los repositorios públicos. Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados. Los miembros de las empresas pueden acceder a los repositorios internos. Para obtener más información, consulta la sección "[Acerca de los repositorios internos](#about-internal-repositories)". +{% endif %} + +Los propietarios de la organización siempre tiene acceso a todos los repositorios creados en la misma. Para obtener más información, consulta la sección "[Niveles de permiso en un repositorio para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". + +Las personas con permisos de administrador para un repositorio pueden cambiar la visibilidad de los repositorios existentes. Para obtener más información, consulta la sección "[Configurar la visibilidad de los repositorios](/github/administering-a-repository/setting-repository-visibility)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +### Acerca de los repositorios internos + +{% note %} + +**Nota:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +{% data reusables.repositories.about-internal-repos %}Para obtener más información sobre innersource, consulta la documentación técnica de {% data variables.product.prodname_dotcom %} "Introducción a innersource". + +Todos los miembros de las empresas tienen permiso de lectura para los repositorios internos, pero las personas {% if currentVersion == "free-pro-team@latest" %}externas a la empresa{% else %}que no sean miembros de una organización{% endif %}, incluyendo los colaboradores externos en los repositorios organizacionales, no pueden verlos. Para obtener más información, consulta las secciones {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" y {% endif %}"[Niveles de permiso en un repositorio de una organización](/articles/repository-permission-levels-for-an-organization)". + +{% data reusables.repositories.internal-repo-default %} + +Si se elimina a un usuario de todas las organizaciones que pertenezcan a la empresa, las bifurcaciones de dicho usuario para los repositorios internos se eliminarán automáticamente. +{% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md new file mode 100644 index 0000000000000..f6dc95dac0f90 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md @@ -0,0 +1,14 @@ +--- +title: Archivar un repositorio de GitHub +intro: 'Puedes archivar, respaldar y mencionar tu trabajo mediante {% data variables.product.product_name %}, la API o herramientas y servicios de terceros.' +redirect_from: + - /articles/can-i-archive-a-repository/ + - /articles/archiving-a-github-repository + - /enterprise/admin/user-management/archiving-and-unarchiving-repositories +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md new file mode 100644 index 0000000000000..e0e24e60e358c --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md @@ -0,0 +1,22 @@ +--- +title: Archivar repositorios +intro: Puedes archivar un repositorio para que sea de solo lectura para todos los usuarios e indicar que ya no necesita mantenerse activamente. También puedes desarchivar los repositorios que han sido archivados. +redirect_from: + - /articles/archiving-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.archiving-repositories-recommendation %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Danger Zone" (Zona de peligro), haz clic en **Archive this repository** (Archivar este repositorio) o **Unarchive this repository** (Desarchivar este repositorio. este repositorio). ![Botón Archive this repository (Archivar este repositorio)](/assets/images/help/repository/archive-repository.png) +4. Lee las advertencias. +5. Escribe el nombre del repositorio que deseas archivar o desarchivar. ![Advertencias para archivar el repositorio](/assets/images/help/repository/archive-repository-warnings.png) +6. Haz clic en **I understand the consequences, archive this repository** (Comprendo las consecuencias, archivar este repositorio). + +### Further reading +- [Acerca de Archivar repositorios](/articles/about-archiving-repositories)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md new file mode 100644 index 0000000000000..08417babd7d71 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -0,0 +1,44 @@ +--- +title: Realizar una copia de seguridad de un repositorio +intro: 'Puedes utilizar{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git y{% endif %} la API {% if currentVersion == "free-pro-team@latest" %}or a third-party tool {% endif %}para respaldar tu repositorio.' +redirect_from: + - /articles/backing-up-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +Para descargar un archivo en tu repositorio, puedes usar la API para migraciones del usuario o la organizacion. Para obtener más información, consulta la sección "[Migraciones](/rest/reference/migrations)". +{% else %} + +Puedes descargar y realizar una copia de seguridad de tus repositorios manualmente: + +- Para descargar los datos Git de un repositorio en tu máquina local, necesitarás clonar el repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". +- También puedes descargar las wiki de un repositorio. Para obtener más información, consulta "[Agregar o editar páginas wiki](/articles/adding-or-editing-wiki-pages)". + +Cuando clonas un repositorio o wiki, solo se descargan los datos Git, como archivos de proyecto o historial de confirmaciones. Puedes usar nuestra API para exportar otros elementos de tu repositorio {% data variables.product.product_name %} en tu máquina local: + +- [Problemas](/rest/reference/issues#list-issues-for-a-repository) +- [Solicitudes de cambios](/rest/reference/pulls#list-pull-requests) +- [Bifurcaciones](/rest/reference/repos#list-forks) +- [Comentarios](/rest/reference/issues#list-issue-comments-for-a-repository) +- [Hitos](/rest/reference/issues#list-milestones) +- [Etiquetas](/rest/reference/issues#list-labels-for-a-repository) +- [Observadores](/rest/reference/activity#list-watchers) +- [Stargazers](/rest/reference/activity#list-stargazers) +- [Proyectos](/rest/reference/projects#list-repository-projects) +{% endif %} + +Una vez que tengas {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}una versión local de todo el contenido que quieras respaldar, puedes crear un archivo zip y {% else %}descargar tu archivo, puedes {% endif %}copiarlo a un disco duro externo y/o cargarlo a algún servicio de respaldo basado en la nube, tal como [Google Drive](https://www.google.com/drive/) o [Dropbox](https://www.dropbox.com/). + +{% if currentVersion == "free-pro-team@latest" %} +### Herramientas de copias de seguridad de terceros + +Existe un número de herramientas de autoservicio que automatizan las copias de seguridad de los repositorios. A diferencia de los proyectos de archivo, los cuales archivan _todos_ los repositorios públicos en {% data variables.product.product_name %} que no hayan optado por salir y que ponen todos los datos a disposición de cualquiera, las herramientas de respaldo descargarán los datos de repositorios _específicos_ y los organizarán en una nueva rama o directorio. Para obtener más información acerca de los proyectos de archivo, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". +Puedes respaldar todos los datos de Git de un repositorio (tales como archivos de proyecto e historial de confirmaciones), así como muchos de los datos de + +{% data variables.product.product_name %} (tales como propuestas y solicitudes de cambios), con [BackHub](https://github.com/marketplace/backhub), el cual crea respaldos recurrentes diarios de tus repositorios con capturas de pantalla de hasta 30 días atrás. BckHub está disponible en {% data variables.product.prodname_marketplace %}. +{% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md new file mode 100644 index 0000000000000..4ab68eb51e468 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md @@ -0,0 +1,12 @@ +--- +title: Clonar un repositorio desde GitHub +intro: 'Puedes clonar un repositorio remoto desde tu máquina local. Si encuentras errores, existen algunas soluciones de problemas comunes.' +mapTopic: verdadero +redirect_from: + - /articles/cloning-a-repository-from-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md new file mode 100644 index 0000000000000..13f2793d0fd0c --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md @@ -0,0 +1,74 @@ +--- +title: Clonar un repositorio +intro: 'Cuando creas un repositorio en {% data variables.product.product_location %}, este existe como un repositorio remoto. Puedes clonar tu repositorio para crear una copia local en tu computadora y sincronizarla entre las dos ubicaciones.' +redirect_from: + - /articles/cloning-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de clonar un repositorio + +Puedes clonar un repositorio desde {% data variables.product.product_location %} hacia tu computadora local para que sea más fácil fusionar conflictos, agregar o eliminar archivos, y subir confirmaciones más grandes. Cuando clonas un repositorio, lo copias desde {% data variables.product.product_location %} hacia tu máquina local. + +Clonar un repositorio extrae una copia integral de todos los datos del mismo que {% data variables.product.product_location %} tiene en ese momento, incluyendo todas las versiones para cada archivo y carpeta para el proyecto. Puedes subir tus cambios al repositorio remoto en {% data variables.product.product_location %}, o extraer los cambios de otras personas desde {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Utilizar los comandos comunes de Git](/github/using-git/using-common-git-commands)". + +Puedes clonar tu repositorio existente o clonar el repositorio existente de alguien más para contribuir con un proyecto. + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% tip %} + +**Tip**: También puedes clonar un repositorio utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta la sección "[`gh repo clone`](https://cli.github.com/manual/gh_repo_clone)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +### Clonar un repositorio utilizando la línea de comando + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} + +### Clonar un repositorio a {% data variables.product.prodname_desktop %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +4. Sigue las indicaciones en {% data variables.product.prodname_desktop %} para completar la clonación. + +Para obtener más información, consulta "[Clonar un repositorio de {% data variables.product.prodname_dotcom %} a {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". + +### Clonar un repositorio vacío + +Un repositorio vacío no contiene archivos. Habitualmente se hace si no inicias el repositorio con un README antes de crearlo. + +{% data reusables.repositories.navigate-to-repo %} +2. Para clonar tu repositorio utilizando la línea de comandos a través de HTTPS, debajo de "Configuración rápida", da clic en {% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar el repositorio utilizando una llave SSH, incluyendo un certificado que emita la autoridad de certificados SSH de tu organización, da clic en **SSH** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. ![Botón de URL de clon de repositorio vacío](/assets/images/help/repository/empty-https-url-clone-button.png) + + Como alternativa, para clonar tu repositorio en el escritorio, da clic en {% octicon "desktop-download" aria-label="The desktop download button" %} **Configurar en el escritorio** y sigue las indicaciones para completar el clon. ![Botón de escritorio para clonar repositorio vacío](/assets/images/help/repository/empty-desktop-clone-button.png) + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} + +### Solucionar los errores de clonado + +Cuando clonas un repositorio, es posible que puedas encontrar algunos errores. + +Si no puedes clonar un repositorio, revisa que: + +- Puedas conectarte utilizando HTTPS. Para obtener más información, consulta la sección "[Errores de clonado de HTTPS](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)". +- Tienes permiso para acceder al repositorio que quieres clonar. Para obtener más información, consulta la sección "[Error: Repositorio no encontrado](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)". +- La rama predeterminada que quieres clonar aún existe. Para obtener más información, verifica que tienes permiso para acceder al repositorio que quieres clonar. Para obtener más información, consulta "[Error: El HEAD remoto se refiere a una ref inexistente, imposible registrar](/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)", + +{% if currentVersion == "free-pro-team@latest" %} + +### Further reading + +- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" +{% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md new file mode 100644 index 0000000000000..62692b18bca4e --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md @@ -0,0 +1,52 @@ +--- +title: Crear un repositorio nuevo +intro: Puedes crear un repositorio nuevo en tu cuenta personal o la cuenta de cualquier organización en la que tengas los permisos suficientes. +redirect_from: + - /creating-a-repo/ + - /articles/creating-a-repository-in-an-organization/ + - /articles/creating-a-new-organization-repository/ + - /articles/creating-a-new-repository + - /articles/creating-an-internal-repository + - /github/setting-up-and-managing-your-enterprise-account/creating-an-internal-repository + - /github/creating-cloning-and-archiving-repositories/creating-an-internal-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Los propietarios pueden restringir los permisos de creación de repositorios en una organización. Para obtener más información, consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". + +{% endtip %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% tip %} + +**Tip**: También puedes crear un repositorio utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +{% data reusables.repositories.create_new %} +2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +3. En el menú desplegable de Propietario, selecciona la cuenta en la cual quieres crear el repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) +{% data reusables.repositories.repo-name %} +{% data reusables.repositories.choose-repo-visibility %} +6. Si no estás utilizando una plantilla, hay varios elementos opcionales que puedes pre-cargar en tu repositorio. Si estás importando un repositorio existente a {% data variables.product.product_name %}, no elijas ninguna de estas opciones, ya que producirás un conflicto de fusión. Puedes agregar o crear nuevos archivos usando la interfaz de usuario o elegir agregar nuevos archivos usando luego la línea de comando. Para obtener más información, consulta "[Importar un repositorio Git usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line/)," "[Agregar un archivo a un repositorio usando la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)," y "[Resolver conflictos de fusión](/articles/addressing-merge-conflicts/)". + - Puedes crear un README, que es un documento que describe tu proyecto. Para obtener más información, consulta "[Acerca de los README](/articles/about-readmes/)". + - Puedes crear un archivo *.gitignore*, que es un conjunto de reglas de ignorar. Para obtener más información, consulta la sección "[Ignorar archivos](/articles/ignoring-files)".{% if currentVersion == "free-pro-team@latest" %} + - Puedes elegir agregar una licencia de software a tu proyecto. Para más información, consulta "[Licenciando un repositorio](/articles/licensing-a-repository)."{% endif %} +{% data reusables.repositories.select-marketplace-apps %} +{% data reusables.repositories.create-repo %} +{% if currentVersion == "free-pro-team@latest" %} +9. En la parte inferior de la página de Configuración rápida resultante, en "Importar el código del repositorio anterior", puedes elegir importar un proyecto en tu nuevo repositorio. Para hacerlo, haz clic en **Importar código**. +{% endif %} + +### Further reading + +- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" +- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md new file mode 100644 index 0000000000000..fc478369802b1 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md @@ -0,0 +1,44 @@ +--- +title: Crear un repositorio desde una plantilla +intro: Puedes generar un nuevo repositorio con la misma estructura de directorio y los mismos archivos que un repositorio existente. +redirect_from: + - /articles/creating-a-repository-from-a-template +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las plantillas de repositorio + +Cualquier usuario con permisos de lectura para un repositorio de plantillas puede crear un repositorio a partir de esa plantilla. Para obtener más información, consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +{% tip %} + +**Tip**: También puedes crear un repositorio a partir de una plantilla utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. +{% endif %} + +Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes: +- Una nueva bifurcación incluye todo el historial de confirmaciones del repositorio padre, mientras que un repositorio creado a partir de una plantilla comienza con una única confirmación. +- Las confirmaciones en una bifurcación no aparecen en tu gráfico de contribuciones, mientras que las confirmaciones en un repositorio creado a partir de una plantilla sí se muestran en tu gráfico de contribuciones. +- Una bifurcación puede ser una forma temporaria de contribuir código a un proyecto existente, mientras que crear un repositorio a partir de una plantilla permite iniciar rápidamente un proyecto nuevo. + +Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". + +### Crear un repositorio desde una plantilla + +{% data reusables.repositories.navigate-to-repo %} +2. Sobre la lista, haz clic en **Usar esta plantilla**. ![Botón Use this template button (Usar esta plantilla)](/assets/images/help/repository/use-this-template-button.png) +{% data reusables.repositories.owner-drop-down %} +{% data reusables.repositories.repo-name %} +{% data reusables.repositories.choose-repo-visibility %}{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +6. De manera opcional, para incluir la estructura de directorio y los archivos de todas las ramas en la plantilla, y no únicamente aquellos de la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +{% data reusables.repositories.select-marketplace-apps %} +8. Haz clic en **Crear un repositorio a partir de una plantilla**. diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md new file mode 100644 index 0000000000000..4992a55177d90 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md @@ -0,0 +1,12 @@ +--- +title: Crear un repositorio en GitHub +intro: 'Luego de crear tu repositorio en {% data variables.product.product_name %}, puedes personalizar sus parámetros y su contenido.' +mapTopic: verdadero +redirect_from: + - /articles/creating-a-repository-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md new file mode 100644 index 0000000000000..e6ffb44b92646 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md @@ -0,0 +1,25 @@ +--- +title: Crear un repositorio desde una plantilla +intro: 'Puedes hacer una plantilla a partir de un repositorio existente para que tú y otras personas puedan generar repositorios nuevos con la misma estructura de directorios{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, ramas,{% endif %} y archivos.' +permissions: Cualquier usuario con permisos de administrador para un repositorio puede convertir el repositorio en una plantilla. +redirect_from: + - /articles/creating-a-template-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota**: Ty repositorio de plantilla no puede incluir archivos que se almacenen utilizando {% data variables.large_files.product_name_short %}. + +{% endnote %} + +Para crear un repositorio de plantilla, debes crear un repositorio y luego convertirlo en una plantilla. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)." + +Después de que conviertas tu repositorio en una plantilla, cualquiera con acceso a éste podrá generar un repositorio nuevo con la misma estructura de directorios y archivos que tu rama predeterminada.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} También podrán elegir incluir el resto de las ramas en tu repositorio.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. Selecciona **Repositorio de plantilla**. ![Casilla de verificación para convertir un repositorio en una plantilla](/assets/images/help/repository/template-repository-checkbox.png) diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md new file mode 100644 index 0000000000000..7b9c8cd010a3d --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md @@ -0,0 +1,21 @@ +--- +title: Crear un repositorio solo para propuestas +intro: '{% data variables.product.product_name %} no otorga permisos de acceso solo para propuestas, pero puedes cumplir con este requisito usando un segundo repositorio que contenga solo las propuestas.' +redirect_from: + - /articles/issues-only-access-permissions/ + - /articles/is-there-issues-only-access-to-organization-repositories/ + - /articles/creating-an-issues-only-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +1. Crea un repositorio **privado** para alojar el código fuente de tu proyecto. +2. Crea un segundo repositorio con los permisos que deseas alojar para el usuario a cargo del seguimiento de la propuesta. +3. Agrega un archivo README al repositorio de propuestas que explique el propósito de este repositorio y establezca un enlace con la sección de las propuestas. +4. Indica a tus colaboradores o equipos que den acceso a los repositorios que desees. + +Los usuarios con acceso de escritura a ambos pueden referenciar y cerrar las propuestas a través de los repositorios, pero los usuarios que no tengan los permisos requeridos verán referencias que contienen información mínima. + +Por ejemplo, si subiste una confirmación a la rama predeterminada del repositorio privado con un mensaje que dice `Fixes organization/public-repo#12`, la propuesta se cerrará, pero solo los usuarios con los permisos adecuados verán la referencia entre los repositorios que indica la confirmación que determinó que se cerrara la propuesta. Sin los permisos sigue apareciendo una referencia, pero se omiten los detalles. diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md new file mode 100644 index 0000000000000..95b33070cc12f --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -0,0 +1,82 @@ +--- +title: Duplicar un repositorio +intro: 'Para duplicar un repositorio sin bifurcarlo, puedes ejecutar un comando de clonación especial y luego subirlo en espejo al nuevo repositorio.' +redirect_from: + - /articles/duplicating-a-repo/ + - /articles/duplicating-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para que puedas duplicar un repositorio y subirlo a tu nueva copia, o _espejo_ del repositorio, antes debes [crear el nuevo repositorio](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. En estos ejemplos, `exampleuser/new-repository` o `exampleuser/mirrored` son los espejos. + +### Generar un espejo de un repositorio + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Crea un clon desnudo de un repositorio. + ```shell + $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + ``` +3. Sube en espejo al nuevo repositorio. + ```shell + $ cd old-repository.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + ``` +4. Eliminar el repositorio local temporal que creaste previamente. + ```shell + $ cd .. + $ rm -rf old-repository.git + ``` + +### Replicar un repositorio que contiene objetos de {% data variables.large_files.product_name_long %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Crea un clon desnudo de un repositorio. Reemplaza el nombre de usuario del ejemplo por el nombre de la persona u organización propietaria del repositorio y reemplaza el nombre del repositorio del ejemplo por el nombre del repositorio que deseas duplicar. + ```shell + $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + ``` +3. Dirígete al repositorio que acabas de clonar. + ```shell + $ cd old-repository.git + ``` +4. Extra los objetos {% data variables.large_files.product_name_long %} del repositorio. + ```shell + $ git lfs fetch --all + ``` +5. Sube en espejo al nuevo repositorio. + ```shell + $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + ``` +6. Sube los objetos {% data variables.large_files.product_name_long %} del repositorio a tu espejo. + ```shell + $ git lfs push --all https://github.com/exampleuser/new-repository.git + ``` +7. Eliminar el repositorio local temporal que creaste previamente. + ```shell + $ cd .. + $ rm -rf old-repository.git + ``` + +### Replicar un repositorio en otra ubicación + +Si quieres replicar un repositorio en otra ubicación, incluido obtener actualizaciones del original, puedes clonar una réplica y subir periódicamente los cambios. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Crea un clon desnudo en espejo del repositorio. + ```shell + $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git + ``` +3. Establece la ubicación para subir en tu espejo. + ```shell + $ cd repository-to-mirror.git + $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored + ``` + +Al igual que sucede con un clon básico, un clon replicado incluye todas las ramas y etiquetas remotas, pero todas las referencias locales se sobrescribirán cada vez que extraigas elementos, por eso siempre será igual al repositorio original. El proceso para subir elementos a tu espejo se simplifica si estableces la URL para los elementos que subes. Para actualizar tu espejo, extrae las actualizaciones y súbelas. + +```shell +$ git fetch -p origin +$ git push --mirror +``` diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md new file mode 100644 index 0000000000000..daf8a52f5560f --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md @@ -0,0 +1,45 @@ +--- +title: 'Error: HEAD remoto remite a una referencia que no existe, imposible de controlar' +intro: 'Este error ocurre si la rama por defecto de un repositorio se ha eliminado en {% data variables.product.product_location %}.' +redirect_from: + - /articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Es muy fácil detectar este error; Git te dará una advertencia cuando intentes clonar el repositorio: + +```shell +$ git clone https://{% data variables.command_line.codeblock %}/user/repo.git +# Clone a repo +> Cloning into 'repo'... +> remote: Counting objects: 66179, done. +> remote: Compressing objects: 100% (15587/15587), done. +> remote: Total 66179 (delta 46985), reused 65596 (delta 46402) +> Receiving objects: 100% (66179/66179), 51.66 MiB | 667 KiB/s, done. +> Resolving deltas: 100% (46985/46985), done. +> warning: remote HEAD refers to nonexistent ref, unable to checkout. +``` + +Para resolver el error, es necesario que seas un administrador del repositorio en {% data variables.product.product_location %}. Desearás [cambiar la rama por defecto](/github/administering-a-repository/changing-the-default-branch) del repositorio. + +Luego de hacerlo, puedes obtener una lista de todas las ramas disponibles en la línea de comando: + +```shell +$ git branch -a +# Lists ALL the branches +> remotes/origin/awesome +> remotes/origin/more-work +> remotes/origin/new-main +``` + +Luego, puedes pasar a tu nueva rama: + +```shell +$ git checkout new-main +# Create and checkout a tracking branch +> Branch new-main set up to track remote branch new-main from origin. +> Switched to a new branch 'new-main' +``` diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md new file mode 100644 index 0000000000000..991a595f41a25 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -0,0 +1,54 @@ +--- +title: 'Error: Repositorio no encontrado' +intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}Si ves este error al clonar un repositorio, significa que éste no existe o que no tienes permiso para acceder a él.{% else %}Si ves este error cuando clonas un repositorio, significa que éste no existe, no tienes permiso para acceder a él, o {% data variables.product.product_location %} se encuentra en modo privado.{% endif %} Hay algunas cuantas formas de solucionar este error, dependiendo de cuál sea su causa.' +redirect_from: + - /articles/error-repository-not-found +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Comprueba que no haya errores tipográficos + +Los errores tipográficos suceden, y los nombres de los repositorios distinguen mayúsculas de minúsculas. Si intentas clonar `git@{% data variables.command_line.codeblock %}:user/repo.git`, pero el repositorio se llama en realidad `User/Repo` recibirás este error. + +Para evitar este error, cuando clonas, copia y pega siempre la URL del clon desde la página del repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". + +Para actualizar el remoto en un repositorio existente, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". + +### Comprobar tus permisos + +Si estás tratando de clonar un repositorio privado pero no tienes permiso para ver el repositorio, recibirás este error. + +Verifica si tienes acceso al repositorio de alguna de las siguientes maneras: + +* Como propietario del repositorio +* Como [colaborador](/articles/inviting-collaborators-to-a-personal-repository) del repositorio +* Como [miembro de un equipo](/articles/adding-organization-members-to-a-team) que tiene acceso al repositorio (si el repositorio pertenece a una organización) + +### Comprueba tu acceso SSH + +En muy raros casos, es posible que no tengas el acceso SSH correcto al repositorio. + +Debes asegurarte de que la clave SSH que estás usando se encuentre conectada con tu usuario de {% data variables.product.product_name %}. Para comprobarlo, escribe lo siguiente en la línea de comando: + +```shell +$ ssh -T git@{% data variables.command_line.codeblock %} +> Hi username! You've successfully authenticated, but GitHub does not +> provide shell access. +``` + +Si el repositorio pertenece a una organización y estás utilizando una llave SSH generada por una OAuth App, puede que algún dueño de la organización haya restringido el acceso OAuth App. Para obtener más información, consulta la sección "Acerca de las restricciones al acceso OAuth App". + +Para obtener más información, consulta "[Agregar una nueva clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)". + +{% if enterpriseServerVersions contains currentVersion %} +### Comprueba si tu instancia se encuentra en el modo privado + +Si tu administrador del sitio ha habilitado el modo privado en tu instancia de GitHub Enterprise, los clones anónimos creados sobre `git://` se inhabilitarán. Si no puedes clonar un repositorio, comunícate con el administrador de tu sitio. +{% endif %} + +### Comprueba que el repositorio realmente exista + +Si nada de lo anterior funciona, verifica que el repositorio realmente exista en {% data variables.product.product_location %}. Si estás intentando subir a un repositorio que no existe, se producirá este error. diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md new file mode 100644 index 0000000000000..b46c44f2f8337 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -0,0 +1,80 @@ +--- +title: Errores de clonación de HTTPS +intro: 'Existen algunos errores comunes cuando se utiliza HTTPS con Git. Estos errores suelen indicar que tienes una versión antigua de Git o que no tienes acceso al repositorio.' +redirect_from: + - /articles/error-the-requested-url-returned-error-403/ + - /articles/error-the-requested-url-returned-error-401/ + - /articles/error-did-you-run-git-update-server-info-on-the-server/ + - /articles/error-the-requested-url-returned-error-403-while-accessing-https-github-com-user-repo-git-info-refs/ + - /articles/https-cloning-errors +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Aquí aparece un ejemplo de un error de HTTPS que puedes recibir: + +```shell +> error: La URL solicitada generó el error: 401 al intentar acceder a +> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs?service=git-receive-pack +> fatal: la solicitud de HTTP falló +``` + +```shell +> Error: La URL solicitada generó el error: 403 al intentar acceder a +> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs +> fatal: la solicitud de HTTP falló +``` + +```shell +> Error: https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs no encontrado: ¿ejecutaste git +> update-server-info en el servidor? +``` + +### Comprueba tu versión de Git + +No hay una versión mínima de Git que sea necesaria para interactuar con {% data variables.product.product_name %}, pero hemos descubierto que la versión 1.7.10 es una versión estable y cómoda que está disponible en muchas plataformas. Siempre puedes [descargar la última versión en el sitio web de Git](https://git-scm.com/downloads). + +### Asegúrate de que el remoto sea correcto + +El repositorio que estás tratando de extraer debe existir en {% data variables.product.product_location %}, y la URL distingue entre mayúsculas y minúsculas. + +Puedes encontrar la URL del repositorio local abriendo la línea de comando y escribiendo `git remote -v`: + +```shell +$ git remote -v +# Visualiza los remotos existentes +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) + +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git +# Cambia la URL del remoto 'origen' + +$ git remote -v +# Verifica la nueva URL remota +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) +``` + +Como alternativa, puedes cambiar la URL a través de nuestra aplicación [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). + +### Proporciona un token de acceso + +Para acceder a {% data variables.product.prodname_dotcom %}, debes autenticarte con un token de acceso personal en vez de con tu contraseña. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +{% data reusables.command_line.provide-an-access-token %} + +### Comprueba tus permisos + +Cuando se te solicite un nombre de usuario y contraseña, asegúrate de usar una cuenta que tenga acceso al repositorio. + +{% tip %} + +**Tip**: Si no quieres ingresar tu nombre de usuario y contraseña cada vez que interactúes con el repositorio remoto, puedes activar el [almacenamiento en caché de las contraseñas](/github/using-git/caching-your-github-credentials-in-git). Si ya estás utilizando el almacenamiento de credenciales en caché, por favor, asegúrate de que tu computadora tenga las credenciales correctas almacenadas en caché. Las credenciales erróneas o desactualizadas causarán que falle la autenticación. + +{% endtip %} + +### Usar SSH en su lugar + +Si ya has configurado claves SSH, puedes usar el clon SSH en lugar de HTTPS. Para obtener más información, consulta "[¿Qué URL remota debo usar?](/articles/which-remote-url-should-i-use)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/index.md new file mode 100644 index 0000000000000..6688d24ba806d --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/index.md @@ -0,0 +1,40 @@ +--- +title: 'Crear, clonar y archivar repositorios' +intro: 'Puedes elegir de entre diversas opciones de configuración cuando creas o clonas un repositorio. También puedes utilizar repositorios para archivar contenido y datos en {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /categories/repositories/ + - /categories/24/articles/ + - /categories/creating-cloning-and-archiving-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /creating-a-repository-on-github %} + {% link_in_list /about-repositories %} + {% link_in_list /about-repository-visibility %} + {% link_in_list /creating-a-new-repository %} + {% link_in_list /creating-a-repository-from-a-template %} + {% link_in_list /about-readmes %} + {% link_in_list /about-code-owners %} + {% link_in_list /about-repository-languages %} + {% link_in_list /licensing-a-repository %} + {% link_in_list /creating-a-template-repository %} + {% link_in_list /creating-an-issues-only-repository %} + {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} + {% link_in_list /duplicating-a-repository %} +{% topic_link_in_list /cloning-a-repository-from-github %} + {% link_in_list /cloning-a-repository %} + {% link_in_list /https-cloning-errors %} + {% link_in_list /error-repository-not-found %} + {% link_in_list /error-remote-head-refers-to-nonexistent-ref-unable-to-checkout %} +{% topic_link_in_list /archiving-a-github-repository %} + {% link_in_list /about-archiving-repositories %} + {% link_in_list /archiving-repositories %} + {% link_in_list /about-archiving-content-and-data-on-github %} + {% link_in_list /referencing-and-citing-content %} + {% link_in_list /backing-up-a-repository %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md new file mode 100644 index 0000000000000..4ffed65bbd964 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -0,0 +1,94 @@ +--- +title: Generar licencia para un repositorio +intro: 'Los repositorios públicos de GitHub se suelen utilizar para compartir software de código abierto. Para que tu repositorio sea verdaderamente de código abierto, tendrás que generarle una licencia. De este modo, las demás personas podrán usar, modificar y distribuir el software con libertad.' +redirect_from: + - /articles/open-source-licensing/ + - /articles/licensing-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Elegir la licencia correcta + +Creamos [choosealicense.com](http://choosealicense.com), para ayudarte a entender cómo generar una licencia para tu código. Una licencia de software les informa a las demás personas lo que pueden y no pueden hacer con tu código fuente; por lo tanto, es importante tomar una decisión informada. + +No tienes la obligación de elegir una licencia. Sin embargo, sin una licencia, se aplican las leyes de derecho de autor predeterminadas, lo que implica que conservas todos los derechos de tu código fuente, y nadie puede reproducir, distribuir o crear trabajos a partir de tu trabajo. Si estás creando un proyecto de código abierto, te alentamos fuertemente a que incluyas una licencia de código abierto. La [Guía de código abierto](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) brinda más orientación para elegir la licencia correcta para tu proyecto. + +{% note %} + +**Nota:** Si publicas tu código fuente en un repositorio público en {% data variables.product.product_name %}, {% if currentVersion == "free-pro-team@latest" %}de acuerdo con las [Condiciones de servicio](/articles/github-terms-of-service), {% endif %}otros usuarios de {% data variables.product.product_location %} tiene el derecho de ver y bifurcar tu repositorio. Si ya creaste un repositorio y no quieres que los usuarios tengan acceso a él, puedes hacer este repositorio privado. Cuando cambias la visibilidad de un repositorio a privada, las bifurcaciones existentes o copias locales que crean otros usuarios seguirán existiendo. Para obtener más información, consulta la sección "[Configurar la visibilidad de los repositorios](/github/administering-a-repository/setting-repository-visibility)". + +{% endnote %} + +### Determinar la ubicación de tu licencia + +La mayoría de las personas coloca su texto de licencia en un archivo denominado`LICENSE.txt` (o `LICENSE.md`) en la raíz del repositorio; [aquí hay un ejemplo de Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). + +Algunos proyectos incluyen información acerca de sus licencias en sus README. Por ejemplo, el README de un proyecto puede incluir una nota que diga "Este proyecto cuenta con licencia conforme a los términos de la licencia MIT". + +Como buena práctica, te alentamos a que incluyas el archivo de licencia en tu proyecto. + +### Buscar en GitHub por tipo de licencia + +Puedes filtrar repositorios en función de su licencia o familia de licencia usando el calificador de `licencia` y la palabra clave exacta de la licencia: + +| Licencia | Palabra clave de la licencia | +| -------- | ------------------------------------------------------------- | +| | Academic Free License v3.0 | `afl-3.0` | +| | Apache license 2.0 | `apache-2.0` | +| | Artistic license 2.0 | `artistic-2.0` | +| | Boost Software License 1.0 | `bsl-1.0` | +| | BSD 2-clause "Simplified" license | `bsd-2-clause` | +| | BSD 3-clause "New" or "Revised" license | `bsd-3-clause` | +| | BSD 3-clause Clear license | `bsd-3-clause-clear` | +| | Creative Commons license family | `cc` | +| | Creative Commons Zero v1.0 Universal | `cc0-1.0` | +| | Creative Commons Attribution 4.0 | `cc-by-4.0` | +| | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | +| | Do What The F*ck You Want To Public License | `wtfpl` | +| | Educational Community License v2.0 | `ecl-2.0` | +| | Eclipse Public License 1.0 | `epl-1.0` | +| | Eclipse Public License 2.0 | `epl-2.0` | +| | European Union Public License 1.1 | `eupl-1.1` | +| | GNU Affero General Public License v3.0 | `agpl-3.0` | +| | GNU General Public License family | `gpl` | +| | GNU General Public License v2.0 | `gpl-2.0` | +| | GNU General Public License v3.0 | `gpl-3.0` | +| | GNU Lesser General Public License family | `lgpl` | +| | GNU Lesser General Public License v2.1 | `lgpl-2.1` | +| | GNU Lesser General Public License v3.0 | `lgpl-3.0` | +| | ISC | `isc` | +| | LaTeX Project Public License v1.3c | `lppl-1.3c` | +| | Microsoft Public License | `ms-pl` | +| | MIT | `mit` | +| | Mozilla Public License 2.0 | `mpl-2.0` | +| | Open Software License 3.0 | `osl-3.0` | +| | PostgreSQL License | `postgresql` | +| | SIL Open Font License 1.1 | `ofl-1.1` | +| | University of Illinois/NCSA Open Source License | `ncsa` | +| | The Unlicense | `unlicense` | +| | zLib License | `zlib` | + +Cuando busques por una licencia de familia, los resultados incluirán todas las licencias de esa familia. Por ejemplo, cuando utilices la consulta `license:gpl`, los resultados incluirán los repositorios con licencia de GNU General Public License v2.0 y GNU General Public License v3.0. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-license)." + +### Detectar una licencia + +[El titular de licencia de la gema de código abierto Ruby](https://github.com/licensee/licensee) compara el archivo *LICENSE* (LICENCIA) del repositorio con una lista corta de licencias conocidas. El titular de licencia también proporciona las [API de licencias](/rest/reference/licenses) y [nos da información sobre las licencias que tienen los repositorios de {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Si tu repositorio utiliza una licencia que no está detallada en el [Sitio web Choose a License](http://choosealicense.com/appendix/), puedes[solicitar incluir la licencia](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). + +Si tu repositorio utiliza una licencia que está detallada en el sitio web Choose a License y no se muestra claramente en la parte superior de la página del repositorio, puede que contenga múltiples licencias u otra complejidad. Para que se detecten tus licencias, simplifica tu archivo *LICENSE* y anota la complejidad en algún otro lado, como en el archivo *README* de tu repositorio. + +### Aplicar una licencia a un repositorio con una licencia existente + +El selector de licencias solo está disponible cuando creas un proyecto nuevo en GitHub. Puedes agregar manualmente una licencia utilizando el buscador. Para obtener más información acerca de agregar una licencia a un repositorio, consulta "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)." + +![Captura de pantalla del selector de licencias en GitHub.com](/assets/images/help/repository/repository-license-picker.png) + +### Descargo + +El objetivo de los esfuerzos de generación de licencias de código abierto de GitHub es proporcionar un punto de partida para ayudarte a hacer una elección informada. GitHub muestra información de licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados y que cometemos errores como todo el mundo. Por ese motivo, GitHub proporciona la información sobre una base hipotética de "cómo es" y no da garantías al respecto de ninguna información o licencia proporcionada en función o a través de esta. Tampoco se hace responsable de los daños que surjan por el uso de la información de la licencia. Si tienes alguna pregunta al respecto de la licencia correcta para tu código o cualquier otro problema legal relacionado con esto, siempre es mejor consultar con un profesional. + +### Further reading + +- La sección de las Open Source Guides llamada "[The Legal Side of Open Source](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/es-ES/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md new file mode 100644 index 0000000000000..4c08891926234 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md @@ -0,0 +1,33 @@ +--- +title: Límites para ver contenido y diferencias en un repositorio +intro: 'Determinados tipos de recursos pueden ser bastante grandes y requerir mucho procesamiento en {% data variables.product.product_name %}. Por este motivo, se establecen límites para asegurar que las solicitudes se realicen en una cantidad de tiempo razonable.' +redirect_from: + - /articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository/ + - /articles/limits-for-viewing-content-and-diffs-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La mayoría de los límites que aparecen a continuación afectan tanto {% data variables.product.product_name %} como la API. + +### Límites de texto + +Los archivos de texto de más de **1 MB** siempre se muestran como texto sin formato. El código no es de sintaxis resaltada, y los archivos de prosa no se convierten a HTML (como Markdown, AsciiDoc, *etc.*). + +Los archivos de texto de más de **5 MB** están disponibles solo a través de sus URL originales, que se ofrecen a través de `{% data variables.product.raw_github_com %}`; por ejemplo, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Haz clic en el botón **Raw** (Original) para obtener la URL original de un archivo. + +### Límites de diferencias + +Como las diferencias se pueden volver muy grandes, imponemos los siguientes límites en las diferencias para las confirmaciones, las solicitudes de extracción y las vistas comparadas: + +- La diferencia de un archivo único no puede superar *20.000 líneas que puedes cargar* o *1 MB* de datos de la diferencia original. *Cuatrocientas líneas* y *20 KB* se cargan de forma automática para un archivo único. +- La cantidad máxima de archivos en una diferencia única se limita a *3.000*. +- La cantidad máxima de archivos de representación (como PDF y archivos GeoJSON) en una diferencia única está limitada a *25*. + +Se pueden mostrar algunas partes de una diferencia limitada, pero no se muestra nada que supere el límite. + +### Límites de listas de confirmaciones + +Las páginas de vista comparada y de solicitudes de extracción muestran una lista de confirmaciones entre las revisiones de `base` y de `encabezado`. Estas listas están limitadas a **250** confirmaciones. Si superan ese límite, una nota indica que existen más confirmaciones (pero no se muestran). diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/referencing-and-citing-content.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/referencing-and-citing-content.md new file mode 100644 index 0000000000000..8bcf6469b32c1 --- /dev/null +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/referencing-and-citing-content.md @@ -0,0 +1,34 @@ +--- +title: Referenciar y citar contenido +intro: Puedes utilizar herramientas de terceros para citar y referenciar contenido en GitHub. +redirect_from: + - /articles/referencing-and-citing-content +versions: + free-pro-team: '*' +--- + +### Emitir un identificador persistente para tu repositorio con Zenodo + +Para hacer que sea más sencillo referenciar tus repositorios en la literatura académica, puedes crear identificadores persistentes, también conocidos como Identificadores de Objetos Digitales (DOI). Puedes utilizar la herramienta de archivo de datos [Zenodo](https://zenodo.org/about) para archivar un repositorio {% data variables.product.product_name %} y emitir un DOI para el archivo. + +{% tip %} + +**Tips:** +- Zenodo puede acceder solo a repositorios públicos, así que asegúrate de que el repositorio que quieres archivar sea [público](/articles/making-a-private-repository-public). +- Si quieres archivar un repositorio que le pertenece a una organización, puede que el propietario de la organización deba [aprobar el acceso](/articles/approving-oauth-apps-for-your-organization) para la aplicación Zenodo. +- Asegúrate de incluir una [licencia](/articles/open-source-licensing) en tu repositorio para que los lectores sepan cómo pueden reutilizar tu trabajo. + +{% endtip %} + +1. Navega hasta [Zenodo](http://zenodo.org/). +2. En la esquina superior izquierda de la pantalla, haz clic en **Log in** (Registrarse). ![Botón Zenodo log in (Registrarse en Zenodo)](/assets/images/help/repository/zenodo_login.png) +3. Haz clic en **Log in with GitHub** (Registrarse con GitHub). ![Registrarse en Zenodo con GitHub](/assets/images/help/repository/zenodo_login_with_github.png) +4. Revisa la información acerca de los permisos de acceso, luego haz clic en **Authorize application** (Autorizar aplicación). ![Autorizar Zenodo](/assets/images/help/repository/zenodo_authorize.png) +5. Navega hasta la [Página de GitHub de Zenodo](https://zenodo.org/account/settings/github/). ![Página de GitHub de Zenodo](/assets/images/help/repository/zenodo_github_page.png) +6. A la derecha del nombre del repositorio que quieras archivar, cambia el botón de **Off** (Apagado) a **On** (Encendido) para habilitarlo para el archivo. ![Habilitar que Zenodo archive en el repositorio](/assets/images/help/repository/zenodo_toggle_on.png) + +Zenodo archiva tu repositorio y emite un DOI nuevo cada vez que creas un {% data variables.product.product_name %} [lanzamiento](/articles/about-releases/) nuevo. Sigue los pasos en "[Creating releases](/articles/creating-releases/)" (Crear lanzamientos) para crear uno nuevo. + +### Publicitar y citar material de investigación con Figshare + +Los académicos pueden utilizar el servicio de gestión de datos [Figshare](http://figshare.com) para publicitar y citar el material de investigación. Para obtener más información, consulta el [Sitio de asistencia de Figshare](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account). diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md new file mode 100644 index 0000000000000..8eb1d3a1251b5 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -0,0 +1,33 @@ +--- +title: Acerca de Mercado GitHub +intro: '{% data variables.product.prodname_marketplace %} contiene herramientas que adicionan funcionalidad y mejoran tu flujo de trabajo.' +redirect_from: + - /articles/about-github-marketplace +versions: + free-pro-team: '*' +--- + +En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas gratuitas y de pago, incluyendo {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, y {% data variables.product.prodname_actions %}. + +Si compras una herramienta paga, pagarás por tu suscripción a la herramienta con la misma información de facturación que usas para pagar la suscripción de {% data variables.product.product_name %} y recibirás una factura en tu fecha de facturación regular. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +También puedes tener la opción de seleccionar una prueba gratuita de 14 días en algunas herramientas. Puedes cancelar en cualquier momento durante tu prueba y no se te cobrará, pero automáticamente perderás acceso a la herramienta. Tu suscripción paga comenzará al finalizar la prueba de 14 días. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +### Encontrar herramientas en {% data variables.product.prodname_marketplace %} + +Puedes descubrir, buscar e instalar apps y acciones que otros hayan creado en {% data variables.product.prodname_marketplace %}, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". + +{% data reusables.actions.actions-not-verified %} + +Cualquiera puede listar una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} gratuita en {% data variables.product.prodname_marketplace %}. {% data variables.product.company_short %} verifica a aquellos que publican apps de pago, y los listados de dichas apps se muestran con una insignia de creador verificado {% octicon "verified" aria-label="Verified creator badge" %}. También podrás ver insignias para las apps verificadas y sin verificar. Estas apps se publicaron utilizando el método anterior para verificar apps individuales. Para obtener más información acerca del proceso actual, consulta las secciones "[Acerca de los creadores verificados](/developers/github-marketplace/about-verified-creators)" y "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". + +### Crear y hacer aparecer una herramienta en {% data variables.product.prodname_marketplace %} + +Para obtener más información acerca de cómo crear tu propia herramienta para que se liste en {% data variables.product.prodname_marketplace %}, consulta las secciones de "[Aplicaciones](/developers/apps)" y "[{% data variables.product.prodname_actions %}](/actions)". + +### Further reading + +- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" +- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" +- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" +- "[Diferencias entre las GitHub Apps y las Apps de OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/about-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/about-integrations.md new file mode 100644 index 0000000000000..41a186976e033 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/about-integrations.md @@ -0,0 +1,40 @@ +--- +title: Acerca de las integraciones +intro: 'Las integraciones son herramientas y servicios que se conectan con {% data variables.product.product_name %} para complementar y extender tu flujo de trabajo.' +redirect_from: + - /articles/about-integrations +versions: + free-pro-team: '*' +--- + +Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. También puedes instalar {% data variables.product.prodname_github_app %}s de un tercero en un repositorio específico donde tengas permisos de administrador o que sea propiedad de tu organización. + +### Diferencias entre {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s + +Las integraciones pueden ser {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s o cualquiera que utilice API de {% data variables.product.product_name %} o webhooks. + +{% data variables.product.prodname_github_app %}s ofrece permisos granulares y solicita acceso solo a lo que necesita la aplicación. {% data variables.product.prodname_github_app %}s también ofrece permisos de nivel de usuario específicos que cada usuario debe autorizar de forma individual cuando se instala una aplicación o cuando el integrador cambia los permisos solicitados por la aplicación. + +Para obtener más información, consulta: +- "[Diferencias entre las {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)". +- "[Acerca de las apps](/apps/about-apps/)" +- "[Permisos a nivel de usario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)" +- "[Autorizar {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps/)" +- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations/)" + +Puedes instalar una {% data variables.product.prodname_github_app %} preconfigurada, si los integradores o los creadores de la aplicación han creado su aplicación con el flujo de manifiesto de {% data variables.product.prodname_github_app %}. Para obtener más información sobre cómo ejecutar tu {% data variables.product.prodname_github_app %} con configuración automatizada, comunícate con el integrador o el creador de la aplicación. + +Puedes crear una {% data variables.product.prodname_github_app %} con configuración simplificada si creas tu aplicación con Probot. Para obtener más información, consulta el sitio [Documentos de Probot](https://probot.github.io/docs/). + +### Descubrir integraciones en {% data variables.product.prodname_marketplace %} + +Puedes encontrar una integración para instalar o publicar tu propia integración en {% data variables.product.prodname_marketplace %}. + +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contiene {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". + +### Integraciones compradas directamente a los integradores + +También puedes comprar algunas integraciones directamente a los integradores. Como miembro de una organización, si encuentras una {% data variables.product.prodname_github_app %} que te gustaría usar, puedes solicitar que una organización apruebe o instale la aplicación para la organización. + +Si tienes permisos de administrador para todos los repositorios que son propiedad de una organización en la que la aplicación está instalada, puedes instalar {% data variables.product.prodname_github_app %}s con los permisos de nivel de repositorio sin tener que solicitar al propietario de la organización que apruebe la aplicación. Cuando un integrador cambia los permisos de la aplicación, si los permisos son solo para un repositorio, los propietarios de la organización y las personas con permisos de administrador para un repositorio con esa aplicación instalada pueden revisar y aceptar los nuevos permisos. + diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md new file mode 100644 index 0000000000000..e446564cd0255 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md @@ -0,0 +1,10 @@ +--- +title: Explorar integraciones +intro: "Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y\n servicios diseñados por la comunidad de {% data variables.product.product_name %}." +mapTopic: verdadero +redirect_from: + - /articles/exploring-integrations +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md new file mode 100644 index 0000000000000..8263e999a019d --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md @@ -0,0 +1,41 @@ +--- +title: Extensiones e integraciones de GitHub +intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.' +redirect_from: + - /articles/about-github-extensions-for-third-party-applications/ + - /articles/github-extensions-and-integrations +versions: + free-pro-team: '*' +--- + +### Herramientas del editor + +Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y Visual Studio. + +#### {% data variables.product.product_name %} para Atom + +Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para obtener más información, consulta el [{% data variables.product.product_name %} oficial para el sitio de Atom](https://github.atom.io/). + +#### {% data variables.product.product_name %} para Unity + +Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs). + +#### {% data variables.product.product_name %} para Visual Studio + +Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs). + +#### {% data variables.product.prodname_dotcom %} para Visual Studio Code + +Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github). + +### Herramientas de gestión de proyectos + +Puedes integrar tu cuenta personal o de organización de {% data variables.product.product_name %} con las herramientas de administración de proyectos de terceros tales como Jira o Slack. + +#### Integración de Jira Cloud y {% data variables.product.product_name %}.com + +Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. Para obtener más información, visita la [App de integración de Jira](https://github.com/marketplace/jira-software-github) en marketplace. + +#### Integración con Slack y con {% data variables.product.product_name %} + +Puedes integrar Slack con tu cuenta de organización o personal para suscribirte a las notificaciones, cerrar o abrir propuestas, y proporcionar referencias enriquecidas a las propuestas y solicitudes de cambios sin salir de Slack. Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace. diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/index.md b/translations/es-ES/content/github/customizing-your-github-workflow/index.md new file mode 100644 index 0000000000000..5fe4b87a9d955 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/index.md @@ -0,0 +1,18 @@ +--- +title: Personalizar tu flujo de trabajo de GitHub +redirect_from: + - /categories/customizing-your-github-workflow +versions: + free-pro-team: '*' +--- + + +### Índice + +{% topic_link_in_list /exploring-integrations %} + {% link_in_list /about-integrations %} + {% link_in_list /about-github-marketplace %} + {% link_in_list /github-extensions-and-integrations %} +{% topic_link_in_list /purchasing-and-installing-apps-in-github-marketplace %} + {% link_in_list /installing-an-app-in-your-personal-account %} + {% link_in_list /installing-an-app-in-your-organization %} diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md new file mode 100644 index 0000000000000..072ef1cec38d3 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md @@ -0,0 +1,47 @@ +--- +title: Instalar una app en tu organización +intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu organización.' +redirect_from: + - /articles/installing-an-app-in-your-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.marketplace.marketplace-apps-only %} + +{% data reusables.marketplace.marketplace-org-perms %} + +Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu organización usando el método de pago existente de tu organización. + +{% data reusables.marketplace.free-trials %} + +### Instalar una {% data variables.product.prodname_github_app %} en tu organización + +{% data reusables.marketplace.visit-marketplace %} +{% data reusables.marketplace.browse-to-app %} +{% data reusables.marketplace.choose-plan %} +{% data reusables.marketplace.install-buy %} +{% data reusables.marketplace.confirm-install-account-org %} +{% data reusables.marketplace.add-payment-method-org %} +{% data reusables.marketplace.complete-order-begin-installation %} +8. Si la aplicación requiere acceso a los repositorios, decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) +{% data reusables.marketplace.select-installation-repos %} +{% data reusables.marketplace.review-app-perms-install %} + +### Instalar una {% data variables.product.prodname_oauth_app %} en tu organización + +{% data reusables.saml.saml-session-oauth %} + +{% data reusables.marketplace.visit-marketplace %} +{% data reusables.marketplace.browse-to-app %} +{% data reusables.marketplace.choose-plan %} +{% data reusables.marketplace.install-buy %} +{% data reusables.marketplace.confirm-install-account-org %} +{% data reusables.marketplace.add-payment-method-org %} +{% data reusables.marketplace.complete-order-begin-installation %} +8. Revisa la información acerca del acceso de la app a tu cuenta personal, a tus organizaciones y a los datos, luego haz clic en **Authorize application** (Autorizar aplicación). + +### Further reading + +- "[Actualizar el método de pago de tu organización](/articles/updating-your-organization-s-payment-method)" +- "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md new file mode 100644 index 0000000000000..d3c0b92253600 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md @@ -0,0 +1,45 @@ +--- +title: Instalar una app en tu cuenta personal +intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu cuenta personal.' +redirect_from: + - /articles/installing-an-app-in-your-personal-account +versions: + free-pro-team: '*' +--- + +{% data reusables.marketplace.marketplace-apps-only %} + +Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu cuenta personal usando tu método de pago existente. + +{% data reusables.marketplace.free-trials %} + +### Instalar una {% data variables.product.prodname_github_app %} en tu cuenta personal + +{% data reusables.marketplace.visit-marketplace %} +{% data reusables.marketplace.browse-to-app %} +{% data reusables.marketplace.choose-plan %} +{% data reusables.marketplace.install-buy %} +{% data reusables.marketplace.confirm-install-account-personal %} +{% data reusables.marketplace.add-payment-method-personal %} +{% data reusables.marketplace.complete-order-begin-installation %} +8. Decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) +{% data reusables.marketplace.select-installation-repos %} +{% data reusables.marketplace.review-app-perms-install %} + +### Instalar una {% data variables.product.prodname_oauth_app %} en tu cuenta personal + +{% data reusables.saml.saml-session-oauth %} + +{% data reusables.marketplace.visit-marketplace %} +{% data reusables.marketplace.browse-to-app %} +{% data reusables.marketplace.choose-plan %} +{% data reusables.marketplace.install-buy %} +{% data reusables.marketplace.confirm-install-account-personal %} +{% data reusables.marketplace.add-payment-method-personal %} +{% data reusables.marketplace.complete-order-begin-installation %} +8. Revisa la información acerca del acceso de la app a tu cuenta personal y a tus datos, luego haz clic en **Authorize application** (Autorizar aplicación). + +### Further reading + +- "[Actualizar el método de pago de tu cuenta personal](/articles/updating-your-personal-account-s-payment-method)" +- "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md b/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md new file mode 100644 index 0000000000000..e791c4f627c71 --- /dev/null +++ b/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md @@ -0,0 +1,10 @@ +--- +title: Comprar e instalar aplicaciones en el Mercado GitHub +intro: '{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Cuando encuentras una aplicación paga que desearías usar para tu cuenta personal u organización, puedes comprar e instalar la app utilizando tu información de facturación existente.' +mapTopic: verdadero +redirect_from: + - /articles/purchasing-and-installing-apps-in-github-marketplace +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md new file mode 100644 index 0000000000000..08463c41004db --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md @@ -0,0 +1,27 @@ +--- +title: Acerca de la facturación para Codespaces +intro: 'Cuando {% data variables.product.prodname_codespaces %} se hace generalmente disponible, se te cobrará por el almacenamiento y uso del procesamiento.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +{% data reusables.codespaces.about-billing-for-codespaces %} + +Se incurre en los usos de procesamiento cuando un codespace está activo. Cuando utilizas un codespace, éste está activo. Después de 30 minutos de inactividad, el codespace se suspende automáticamente. + +El uso de procesamiento se cobra por hora, con una tasa que depende del tipo de instancia de tu codespace. Durante el beta, {% data variables.product.prodname_codespaces %} ofrece un solo tpo de instancia de Linux. Con disponibilidad general, tendremos compatibilidad con tres tipos de instancia de Linux. + +| Tipo de instancia (Linux) | Tasa por hora | +| ----------------------------------------------- | ------------- | +| Básica (2 núcleos, 4GB de RAM, 32 GB en SSD) | $0.085 (USD) | +| Estándar (4 núcleos, 8 GBde RAM, 32 GB en SSD) | $0.169 (USD) | +| Premium (8 núcleos, 16 GB de RAM, 32 GB en SSD) | $0.339 (USD) | + +Los precios de procesamiento pueden variar para tipos de instancias adicionales y sistemas operativos que serán compatibles posteriormente. + +Cada codespace también incurre en costos de almacenamiento mensual hasta que lo borres. Los costos de almacenamiento para todos los tipos de instancia son de $0.10/GB-mes. + +Compartiremos más información acerca de cualquier uso de procesamiento y de almacenamiento que se incluya en cada plan con la disponibilidad general. diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md new file mode 100644 index 0000000000000..83be3aac7894e --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md @@ -0,0 +1,59 @@ +--- +title: Acerca de Codespaces +intro: '{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo en línea, hospedado en {% data variables.product.prodname_dotcom %} e impulsado por {% data variables.product.prodname_vscode %}, que te permite desarrollar completamente en la nube.' +product: '{% data reusables.gated-features.codespaces %}' +redirect_from: + - /github/developing-online-with-github-codespaces/about-github-codespaces +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. Para obtener más información acerca de unirse al beta, consulta la sección "[Unirse al beta](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". + +{% endnote %} + +### Acerca de {% data variables.product.prodname_codespaces %} + +{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo en la nube que está disponible en tu buscador. Un codespace incluye todo lo que necesitas para hacer desarrollos para un repositorio específico, incluyendo un editor de texto con resaltamiento de sintaxis y auto-compleción, una terminal, herramientas de depuración, y comandos de Git, todo dentro de {% data variables.product.prodname_dotcom %}. También puedes instalar extensiones de {% data variables.product.prodname_vscode %} en tu codespace para agregar más funcionalidades. + +{% data variables.product.prodname_codespaces %} facilita la integración de desarrolladores a una nueva compañía, o el comenzar a contribuir en un proyecto de código abierto. Los mantenedores de proyecto pueden configurar un repositorio para que, cuando crees un codespace para el mismo, las dependencias de dicho proyecto se incluyan automáticamente. Puedes comenzar a crear código más rápido reduciendo el tiempo que gastas en configurar tu ambiente. + +{% data variables.product.prodname_codespaces %} te permite desarrollar en la nube en vez de hacerlo localmente. Los desarrolladores pueden contribuir desde donde sea, en cualquier máquina, incluyendo tablets o Chromebooks, y no es necesario mantener copias locales o propiedad intelectual. + +![Un codespace abierto](/assets/images/help/codespaces/codespace-overview.png) + +### Uso de {% data variables.product.prodname_codespaces %} + +Cada desarrollador puede crear uno o más codespaces para cualquier repositorio público, o para cualquier repositorio privado que pertenezca a su cuenta de usuario. {% data reusables.codespaces.unsupported-repos %} {% data reusables.codespaces.codespaces-are-personal %} + +{% data reusables.codespaces.codespaces-are-per-branch %}{% data reusables.codespaces.concurrent-codespace-limit %}Para obtener más información, consulta la sección "[Borrar un codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". + +{% data reusables.codespaces.use-visual-studio-features %} + +{% data reusables.codespaces.connect-to-codespace-from-vscode %} + +{% data reusables.codespaces.about-configuration %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". + +{% data reusables.codespaces.about-personalization %}Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". + +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + +{% data reusables.codespaces.you-can-see-all-your-codespaces %} + +{% data reusables.codespaces.beta-functionality-limited %} + +### Acerca de la facturación para {% data variables.product.prodname_codespaces %} + +{% data reusables.codespaces.about-billing-for-codespaces %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)". + +### Unirse al beta + +Se invitará a una cantidad limitada de personas para unirse al beta. Para unirse a la lista de espera, consulta la sección [Registrarse para el beta de Codespaces](https://github.com/features/codespaces/signup). + +### Contáctanos para conocer sobre {% data variables.product.prodname_codespaces %} + +Si encuentras problemas al utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Solución de problemas para tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". + +Si aún necesitas ayuda o tienes algún tipo de retroalimentación sobre {% data variables.product.prodname_codespaces %}, utiliza el [Foro Comunitario](https://github.community/c/codespaces-beta/45). diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md new file mode 100644 index 0000000000000..4d33ae113e427 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -0,0 +1,80 @@ +--- +title: Configurar Codespaces para tu proyecto +intro: Puedes configurar ajustes predeterminados para cada codespace nuevo de tu repositorio para garantizar que los colaboradores tengan todas las herramientas y configuraciones que requieran en su ambiente de desarrollo en línea. +product: '{% data reusables.gated-features.codespaces %}' +permissions: Las personas con permisos de escritura en un repositorio pueden crear o editar la configuración predeterminada del codespace. +redirect_from: + - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +### Acerca de las configuraciones predeterminadas de los codespaces + +{% data reusables.codespaces.about-configuration %} + +Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace con una imagen base de Linux. La imagen base de Linux incluye herramientas para Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, y Rust. Para obtener más información acerca de la imagen base de Linux, consulta el repositorio [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux). + +{% data reusables.codespaces.about-personalization %}{% data reusables.codespaces.codespace-config-order %}Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". + +Puedes crear una configuración predeterminada para tus codespaces utilizando una configuración de contenedor pre-compilado para tu tipo de proyecto, o puedes crear una configuración personalizada específica para las necesidades de tu proyecto. + +{% data variables.product.prodname_codespaces %} utiliza ajustes contenidas en un archivo de configuración que se llama `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} + +Puedes utilizar tu `devcontainer.json` para configurar ajustes predeterminados para todo el ambiente de codespace, incluyendo el editor {% data variables.product.prodname_vscode %}, pero también puedes configurar los ajustes específicos para el editor en un archivo que se llame `.vscode/settings.json`. + +Los cambios a la configuración de un codespace en un repositorio se aplican únicamente a cada codespace nuevo y no afectan a los ya existentes. + +### Utilizar una configuración de contenedor pre-compilado + +Puedes utilizar cualquier configuración de contenedor pre-compilado para {% data variables.product.prodname_vscode %} que se encuentre disponible en el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). Las definiciones de los contenedores pre-compilados incluyen una configuración común para un tipo de proyecto en particular, y pueden ayudarte a comenzar rápidamente con una configuración que ya tenga las opciones adecuadas para el contenedor, los ajustes de {% data variables.product.prodname_vscode %}, y las extensiones de {% data variables.product.prodname_vscode %} que deben estar instaladas. + +1. Clona o descarga el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). +1. En el repositorio `vscode-dev-containers`, navega a la carpeta [`containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers), y luego escoge una configuración de contenedor de acuerdo con las necesidades de tu proyecto. Utilizaremos la configuración del contenedor de [Node.js & JavaScript](https://aka.ms/vscode-dev-containers/definitions/node) como ejemplo. +1. Desde la carpeta de [`Node.js & JavaScript`](https://aka.ms/vscode-dev-containers/definitions/node), copia la carpeta `.devcontainer` a la raíz del repositorio de tu proyecto. +1. Confirma y carga la nueva confirmación al repositorio de tu proyecto en {% data variables.product.prodname_dotcom %}. + +Cada coedspace nuevo que crées desde una rama que contenga la carpeta `.devcontainer` se configurará de acuerdo con el contenido de la misma. Para obtener más información, consulta la sección "[Crear un codespace](/github/developing-online-with-codespaces/creating-a-codespace)". + +### Crear una configuración personalizada para un codespace + +Si ninguna de las configuraciones pre-compiladas se ajusta a tus necesidades, puedes crear una configuración personalizada si agregas un archivo `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} + +En el archivo, puedes utilizar claves de configuración compatibles para especificar aspectos del ambiente del codespace, como por ejemplo, qué extensiones de {% data variables.product.prodname_vscode %} deben instalarse. + +{% data reusables.codespaces.vscode-settings-order %} + +Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares. + +* La configuración del editor que se definió en `.vscode/settings.json` se aplica como una configuración con alcance de _Workspace_- en este codespace. +* La configuración del editor que se definió en la clave `settings` en `devcontainer.json` se aplica como una configuración con alcance de _Remote [Codespaces]_ en este codespace. + +### Claves de configuración compatibles con los codespaces + +Puedes utilizar claves de configuración compatibles con {% data variables.product.prodname_codespaces %} en `devcontainer.json`. + +#### Ajustes generales + +- `name (nombre)` +- `parámetros` +- `extensions` +- `forwardPorts` +- `postCreateCommand` + +#### Ajustes de Docker, Dockerfile o de imagen + +- `imagen` +- `dockerFile` +- `context` +- `containerEnv` +- `remoteEnv` +- `containerUser` +- `remoteUser` +- `mounts` +- `runArgs` +- `overrideCommand` +- `dockerComposeFile` + +Para obtener más información acerca de los ajustes disponibles para `devcontainer.json`, consulta la sección [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) en la documentación de {% data variables.product.prodname_vscode %}. diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/creating-a-codespace.md b/translations/es-ES/content/github/developing-online-with-codespaces/creating-a-codespace.md new file mode 100644 index 0000000000000..b78ff2fb0a44b --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/creating-a-codespace.md @@ -0,0 +1,37 @@ +--- +title: Crear un codespace +intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea. +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'Cualquiera puede crear un codespace para cualquier repositorio público, o para cualquier repositorio que pertenezca a su cuenta de usuario.' +redirect_from: + - /github/developing-online-with-github-codespaces/creating-a-codespace +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +### Acerca de la creación de codespaces + +{% data reusables.codespaces.codespaces-are-personal %} + +{% data reusables.codespaces.codespaces-are-per-branch %}{% data reusables.codespaces.concurrent-codespace-limit %}Para obtener más información, consulta la sección "[Borrar un codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". + +{% data reusables.codespaces.unsupported-repos %} + +No puedes crear un codespace en un repositorio vacío. Si tu repositorio está vacío, crea un archivo en él antes de crear un codespace. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/github/managing-files-in-a-repository/adding-a-file-to-a-repository)" y "[Agregar un archivo a un repositorio utilizando la línea de comandos](/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line)". + +El ambiente del codespace que crees se basará en la configuración del repositorio. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". + +{% data reusables.codespaces.about-personalization %}Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". + +{% data reusables.codespaces.use-visual-studio-features %} + +{% data reusables.codespaces.you-can-see-all-your-codespaces %} + +### Crear un codespace + +{% data reusables.repositories.navigate-to-repo %} +2. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear un codespace. ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png) +3. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**. ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) +4. Si ya tienes un codespace para la rama, da clic en {% octicon "plus" aria-label="The plus icon" %}**Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/deleting-a-codespace.md b/translations/es-ES/content/github/developing-online-with-codespaces/deleting-a-codespace.md new file mode 100644 index 0000000000000..d88aedb8110e3 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/deleting-a-codespace.md @@ -0,0 +1,17 @@ +--- +title: Borrar un codespace +intro: Puedes borrar un codespace que ya no necesites. +product: '{% data reusables.gated-features.codespaces %}' +permissions: Cualquiera puede borrar un codespace que pertenezca a su cuenta de usuario. +redirect_from: + - /github/developing-online-with-github-codespaces/deleting-a-codespace +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +{% data reusables.codespaces.concurrent-codespace-limit %} + +{% data reusables.codespaces.navigate-to-codespaces %} +2. A la derecha del codespace que quieras borrar, da clic en **Borrar**. ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/github/developing-online-with-codespaces/developing-in-a-codespace.md new file mode 100644 index 0000000000000..90ebc6c5bbe0d --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/developing-in-a-codespace.md @@ -0,0 +1,43 @@ +--- +title: Desarrollar en un codespace +intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.' +product: '{% data reusables.gated-features.codespaces %}' +permissions: Cualquiera puede desarrollar en un codespace que pertenezca a su cuenta de usuario. +redirect_from: + - /github/developing-online-with-github-codespaces/developing-in-a-codespace +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +{% data reusables.codespaces.use-visual-studio-features %} + +{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". + +### Conectarse a un codespace desde {% data variables.product.prodname_vscode %} +{% data reusables.codespaces.connect-to-codespace-from-vscode %} + +### Navegar a tu codespace +{% data reusables.codespaces.navigate-to-codespaces %} +2. Da clic en el nombre del codespace en el cual quieras desarrollar. ![Nombre del codespace](/assets/images/help/codespaces/click-name-codespace.png) + +### Puertos de redireccionamiento + +La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web en el puerto 3000, puedes acceder a la aplicación desde tu buscador para probarla y depurarla. + +Cuando una aplicación que se ejecuta dentro de un codespace tiene una salida en un puerto de la consola, {% data variables.product.prodname_codespaces %} detecta el patrón de la URL del localhost y redirecciona esos puertos automáticamente. Puedes dar clic en la URL dentro de la terminal para abrirla en un buscador. Por ejemplo, si una aplicación da como salida `http://127.0.0.1:3000` o `http://localhost:3000` en la consola, la bitácora convertirá la salida automáticamente en una URL para el puerto 3000 en la que se puede dar clic. + +![Reenvío Automático de Puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) + +Como alternativa, también puedes utilizar cualquiera de las siguientes formas para redirigir un puerto. + +* Puedes redirigir un puerto bajo demanda si activas la paleta de comandos (`shift command P` / `shift control P`) y tecleas "Codespaces: Forward Port". Entonces puedes ingresar el número del puerto que quieras redirigir. + + ![Paleta de Comandos para la Redirección de Puertos](/assets/images/help/codespaces/command-palette-port-forwarding.png) + +* Puedes configurar automáticamente los puertos en un archivo de `.devcontainer.json` utilizando la propiedad `forwardPorts`. + +* Puedes agregar o eliminar los puertos redirigidos dentro de la extensión de Explorador Remoto. Desde el Explorador Remoto, puedes copiar y pegar las URL para los puertos redirigidos, lo cual te permite acceder a ellos a través de tu buscador. + + ![Redirección de Puertos para el Explorador Remoto](/assets/images/help/codespaces/remote-explorer-port-forwarding.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/index.md b/translations/es-ES/content/github/developing-online-with-codespaces/index.md new file mode 100644 index 0000000000000..cfbb1d14a027a --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/index.md @@ -0,0 +1,28 @@ +--- +title: 'Desarrollar en línea con {% data variables.product.prodname_codespaces %}' +shortTitle: Codespaces +intro: 'Puedes desarrollar íntegramente en la nube utilizando {% data variables.product.prodname_codespaces %}, un ambiente de desarrollo integrado (IDE) en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.codespaces %}' +redirect_from: + - /github/developing-online-with-github-codespaces +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +### Índice + +{% link_in_list /about-codespaces %} +{% link_in_list /about-billing-for-codespaces %} +{% link_in_list /configuring-codespaces-for-your-project %} +{% link_in_list /creating-a-codespace %} +{% link_in_list /developing-in-a-codespace %} +{% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} +{% link_in_list /deleting-a-codespace %} +{% link_in_list /troubleshooting-your-codespace %} +{% link_in_list /using-codespaces-in-visual-studio-code %} +{% link_in_list /using-codespaces-in-visual-studio %} diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..1986a6630acd1 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Haz clic en **Agregar secreto** (Agregar secreto). + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Haz clic en **Guardar cambios**. + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Lee la advertencia y da clic en **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md new file mode 100644 index 0000000000000..71bfb57fb3b80 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -0,0 +1,47 @@ +--- +title: Personalizar Codespaces para tu cuenta +intro: '{% data variables.product.prodname_codespaces %} utiliza tu repositorio de `dotfiles` en {% data variables.product.product_name %} para personalizar cualquier codespace nuevo que crees.' +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'Cualquiera puede crear un repositorio `dotfiles` para personalizar {% data variables.product.prodname_codespaces %} para su cuenta de usuario.' +redirect_from: + - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +Los Dotfiles son archivos y carpetas de sistemas parecidos a Unix que comienzan con `.` y que controlan la configuración de aplicaciones y shells de tu sistema. Puedes alamacenar y administrar tus dotfiles en un repositorio en {% data variables.product.prodname_dotcom %}. Para encontrar consejos y tutoriales sobre qué incluir en tu repositorio de `dotfiles`, consulta la sección [GitHub maneja dotfiles](https://dotfiles.github.io/). + +Si tu cuenta de usuario en {% data variables.product.prodname_dotcom %} es propietaria de un repositorio público llamado `dotfiles`, {% data variables.product.prodname_dotcom %} utilizará este repositorio automáticamente para personalizar el ambiente de tu codespace. Actualmente, no son compatibles los repositorios `dotfiles` privados. + +Tu repositorio `dotfiles` puede incluir los alias de tu shell y tus preferencias, cualquier herramienta que quieras instalar, o cualquier otra personalización del codespace que quieras hacer. + +La personalización de codespaces utilizando el repositorio `dotfiles` aplica a cualquier codespace que crees. Los mantenendores de proyecto también pueden definir una configuración predeterminada que aplique a cada codespace para un repositorio que cree alguien más. {% data reusables.codespaces.codespace-config-order %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". + +Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} clona tu repositorio `dotfiles` hacia el ambiente del codespace, y busca uno de los siguientes archivos para configurar el ambiente. + +* _install.sh_ +* _install_ +* _bootstrap.sh_ +* _bootstrap_ +* _setup.sh_ +* _setup_ + +Si no encuentra alguno de estos archivos, entonces cualquier archivo o carpeta en `dotfiles` que comience con `.` se enlazará simbólicamente al directorio `~` o `$HOME` del codespace. + +Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada codespace nuevo, y no afectará a ningún codespace existente. + +Para obtener más información, consulta la sección "[Personalizing](https://docs.microsoft.com/visualstudio/online/reference/personalizing) en la documentación de {% data variables.product.prodname_vscode %}. + +{% note %} + +**Nota:** Actualmente, {% data variables.product.prodname_codespaces %} no es compatible con la personalización de la configuración de _Usuario_ para el editor de {% data variables.product.prodname_vscode %} con tu repositorio de `dotfiles`. Puedes configurar ajustes predeterminados de _Workspace_ y _Remote [Codespaces]_ para un proyecto específico en el repositorio de éste. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)". + +{% endnote %} + +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + +### Further reading + +* "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md b/translations/es-ES/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md new file mode 100644 index 0000000000000..6772936e6a532 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md @@ -0,0 +1,21 @@ +--- +title: Solucionar problemas de tu codespace +intro: Puedes solucionar los problemas de un codespace si revisas los problemas conocidos en el repositorio `microsoft/vscode`. +product: '{% data reusables.gated-features.codespaces %}' +redirect_from: + - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +{% data reusables.codespaces.beta-functionality-limited %} + +{% data reusables.codespaces.unsupported-repos %} + +Si encuentras problemas al utilizar un buscador que no se base en Chromium, intenta cambiar a uno que sí se base en él, o revisa los problemas conocidos de tu buscador en el repositorio `microsoft/vscode` buscando los problemas etiquetados con el nombre del buscador, tales como [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) o [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). + +Si encuentras problemas al utilizar un buscador basado en Chromium, puedes revisar si estás experimentando otro problema conocido con {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). + +Si aún necesitas ayuda, puedes contactarnos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)". diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md new file mode 100644 index 0000000000000..701af0e740895 --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -0,0 +1,44 @@ +--- +title: Utilizar codespaces en Visual Studio Code +intro: 'Puedes desarrollar tu codespace directamente en {% data variables.product.prodname_vscode %} si conectas la extensión de {% data variables.product.prodname_github_codespaces %} con tu cuenta en {% 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 +versions: + free-pro-team: '*' +--- + +{% data reusables.codespaces.release-stage %} + +### Prerrequisitos + +Para hacer desarrollos en un codespace directamente desde {% data variables.product.prodname_vscode %}, debes ingresar en la extensión de {% data variables.product.prodname_github_codespaces %}. La extensión de {% data variables.product.prodname_github_codespaces %} requiere el lanzamiento 1.51 de octubre de 2020 de {% data variables.product.prodname_vscode %} o superior. + +1. Utiliza + +{% data variables.product.prodname_vs %} Marketplace para instalar la extensión de [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obtener más información, consulta la sección[Extensión de Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) en la documentación de {% data variables.product.prodname_vscode %}. +{% data reusables.codespaces.click-remote-explorer-icon-vscode %} +2. Utiliza el menú desplegable de "REMOTE EXPLORER" y luego da clic en **{% data variables.product.prodname_github_codespaces %}**. ![El encabezado {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) +3. Da clic en **Registrarse para ver {% data variables.product.prodname_codespaces %}...**. ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) +4. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**. +5. Regístrate en {% data variables.product.product_name %} para aprobar la extensión. + +### Crear un codespace en {% data variables.product.prodname_vscode %} + +Despuès de que conectas tu cuenta de {% data variables.product.product_name %} a la extensiòn de {% data variables.product.prodname_vs_codespaces %}, puedes desarrollar en un codespace que hayas creado en {% data variables.product.product_name %} o en {% data variables.product.prodname_vscode %}. + +{% data reusables.codespaces.click-remote-explorer-icon-vscode %} +2. Da clic en el icono de Agregar y luego en **Crear codespace nuevo**. ![La opciòn de crear un codespace nuevo en {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) +3. Teclea y luego da clic en el nombre del repositorio en el que quieras desarrollar. ![Buscar un repositorio para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-repository-vscode.png) +4. Da clic en la rama en la que quieras desarrollar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-branch-vscode.png) +5. Da clic en el tipo de instancia en el que quieras desarrollar. ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png) +### Abrir un codespace en {% data variables.product.prodname_vscode %} + +{% data reusables.codespaces.click-remote-explorer-icon-vscode %} +2. Debajo de Codespaces, da clic en el codespace en el que quieras desarrollar. +3. Da clic en en el icono de conexión al codespace. ![Icono de conectarse al codespace en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + +### Borrar un codespace en {% data variables.product.prodname_vscode %} + +1. Debajo de codespaces, da clic derecho en aquèl que quieras borrar. +2. En el menù desplegable, da clic en **Borrar codespace**. ![Borrar un codespace en {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md new file mode 100644 index 0000000000000..e2b265c4e8cad --- /dev/null +++ b/translations/es-ES/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -0,0 +1,57 @@ +--- +title: Utilizar Codespaces en Visual Studio +intro: 'Puedes desarrollar en tu codespace directamente en {% data variables.product.prodname_vs %} si conectas tu cuenta con {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. [Regístrate para el beta público limitado](https://github.com/features/codespaces/signup-vs). Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". + +{% endnote %} + +### Acerca de los codespaces en {% data variables.product.prodname_vs %} + +Puedes crear un codespace en {% data variables.product.prodname_vs %} para desarrollar aplicaciones en un ambiente Windows. Cuando usas un codespace en {% data variables.product.prodname_vs %}, puedes buscar código fuente, crear soluciones, y confirmar cambios a tu repositorio. + +Debes crear un codespace en {% data variables.product.prodname_vs %} para utilizarlo con la aplicación. Los codespaces que se crean fuera de {% data variables.product.prodname_vs %} no pueden utilizarse con {% data variables.product.prodname_vs %} actualmente. + +### Prerrequisitos + +Antes de que configures un codespace en {% data variables.product.prodname_vs %}, debes descargar la última versión de la [Vista previa de {% data variables.product.prodname_vs %}](https://aka.ms/vspreview). + +#### Habilitar la conexión entre {% data variables.product.prodname_vs %} y {% data variables.product.prodname_github_codespaces %} + +La conexión a {% data variables.product.prodname_github_codespaces %} con la vista previa de {% data variables.product.prodname_vs %} no se encuentra habilitada predeterminadamente, así que primero necesitarás habilitar la opción de Vista Previa de las Características. + +1. En la vista previa de {% data variables.product.prodname_vs %}, utiliza el menú desplegable de herramientas y da clic en **Opciones**. +2. Debajo de **Ambiente**, selecciona **Características de la vista previa** y selecciona la característica de vista previa que dice **Conectarse a {% data variables.product.prodname_github_codespaces %}**. ![Verifica la característica de conectarse a la vista previa de {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) +3. Necesitarás reiniciar {% data variables.product.prodname_vs %} para que la característica esté disponible. + +### Crear un codespace en {% data variables.product.prodname_vs %} + +1. Cuando lanzas a {% data variables.product.prodname_vs %}, la ventana de inicio mostrará un botón de **Conectarse a un codespace** debajo de "Iniciar". ![Ventana de inicio de Visual Studio con conexión a un codespace](/assets/images/help/codespaces/visual-studio-start-window.png) +2. Da clic en **Conectarse a un codespace**. +3. Da clic en **Ingresar a {% data variables.product.prodname_dotcom %}** y sigue las indicaciones, o da clic en **¡Crear uno!** para crear una cuenta de {% data variables.product.prodname_dotcom %} nueva e ingresar en ella. ![Inicio de sesión de Visual Studio a {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) +4. Debajo de "Detalles del codespace", teclea la URL del repositorio que quieres que {% data variables.product.prodname_github_codespaces %} clone en tu codespace. +5. Opcionalmente, utiliza los menúes de "Tipo de instancia" y "Suspender después" para configurar más detalles del codespace. ![Detalles de codespace de Visual Studio](/assets/images/help/codespaces/visual-studio-codespace-details.png) +6. Da clic en **Crear y conectar**. {% data variables.product.prodname_github_codespaces %} comenzará a preparar el codespace y abrirá {% data variables.product.prodname_vs %} después de que el codespace esté listo. El nombre del codespace aparecerá en el indicador remoto en el menú. ![Visual Studio conectado al codespace del repositorio de eShopOnWeb](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) + +### Abrir un codespace en {% data variables.product.prodname_vs %} + +1. Utiliza el menú desplegable de "Archivo" y da clic en **Conectarse a un codespace**. ![Conexión de archivos de Visual Studio a un elemento de menú de un codespace](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) +2. Debajo de "{% data variables.product.prodname_github_codespaces %}", da clic en el codespace al que quieres conectarte y luego da clic en **Conectar**. ![Visual Studio mostrando los detalles y codespaces disponibles](/assets/images/help/codespaces/visual-studio-connect-codespace.png) + +### Configurar un codespace para {% data variables.product.prodname_vs %} + +Un codespace que se crea con {% data variables.product.prodname_vs %} puede personalizarse mediante una herramienta nueva llamada devinit, una herramienta de la línea de comandos que se incluye con {% data variables.product.prodname_vs %}. + +#### devinit + +[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) te permite instalar marcos de trabajo y herramientas adicionales en tus codespaces de desarrollo de Windows, modificar variables de ambiente y más. + +devinit es compatible con un archivo de configuración que se llama [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). Puedes agregar este archivo a tu proyecto si quieres crear un ambiente de desarrollo repetible y personalizado. Cuando utilizas devinit con un archivo [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace), tus codespaces se configurarán automáticamente cuando los crees. + +Para obtener más información acerca de la configuración de devinit y de los codespaces de Windows, consulta la sección [Personalizar un codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) en la documentación de {% data variables.product.prodname_vs %}. Para obtener más información sobre devinit, consulta la sección de [Iniciar con devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). diff --git a/translations/es-ES/content/github/extending-github/about-webhooks.md b/translations/es-ES/content/github/extending-github/about-webhooks.md new file mode 100644 index 0000000000000..21e0e27562f41 --- /dev/null +++ b/translations/es-ES/content/github/extending-github/about-webhooks.md @@ -0,0 +1,30 @@ +--- +title: Acerca de webhooks +redirect_from: + - /post-receive-hooks/ + - /articles/post-receive-hooks/ + - /articles/creating-webhooks/ + - /articles/about-webhooks +intro: Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:**{% data reusables.organizations.owners-and-admins-can %} administrar webhooks para una organización. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +Los webhooks se pueden disparar siempre que se realicen una variedad de acciones en un repositorio o una organización. Por ejemplo, puedes configurar tus webhooks para ejecutarse siemrpe que: + +* Se suba a un repositorio. +* Se abra una solicitud de extracción. +* Se cree un sitio {% data variables.product.prodname_pages %}. +* Se agregue un nuevo miembro a un equipo. + +Al usar la API de {% data variables.product.product_name %}, puedes hacer que estos webhooks actualicen un seguimiento de la propuesta, disparen compilaciones de CI, actualicen un espejo de copia de seguridad o incluso se implementen en tu servidor de producción. + +Para configurar un webhook nuevo, necesitarás acceso a un servidor externo y estar familiarizado con los procedimientos técnicos involucrados. Para obtener ayuda para crear un webhook, lo cual incluye un listado completo de las acciones con las que lo puedes asociar, consulta la secicón "[Webhooks](/webhooks)". diff --git a/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md new file mode 100644 index 0000000000000..a7d38a6026f48 --- /dev/null +++ b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md @@ -0,0 +1,18 @@ +--- +title: Comenzar con la API +redirect_from: + - /articles/getting-started-with-the-api +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para automatizar las tareas comunes, respaldar tus datos, o crear integraciones que se extienden {% data variables.product.product_name %}, puedes utilizar la API de {% data variables.product.product_name %}. + +Para obtener más información acerca de la API, consulta la [API de REST de GitHub](/rest) y la [API de GraphQL de GitHub](/graphql). También puedes mantenerte actualizado respecto de las novedades relacionadas con la API siguiendo el [{% data variables.product.prodname_dotcom %}Blog del programador](https://developer.github.com/changes/). + +### Further reading + +- "[Respaldar un repositorio](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} diff --git a/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md new file mode 100644 index 0000000000000..c6c4d4b75c5ac --- /dev/null +++ b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -0,0 +1,46 @@ +--- +title: Automatización Git con tokens de OAuth +redirect_from: + - /articles/git-over-https-using-oauth-token/ + - /articles/git-over-http-using-oauth-token/ + - /articles/git-automation-with-oauth-tokens +intro: 'Puedes utilizar tokens de OAuth para interactuar con {% data variables.product.product_name %} a través de scripts automatizados.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Paso 1: Obtener un token de OAuth + +Crea un token de acceso personal en tu página de configuración de la aplicación. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +{% tip %} + +{% if currentVersion == "free-pro-team@latest" %} +**Tips:** +- Debes verificar tu dirección de correo electrónico antes de que puedas crer un token de acceso personal. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". +- {% data reusables.user_settings.review_oauth_tokens_tip %} +{% else %} +**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} +{% endif %} + +{% endtip %} + +{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} + +### Paso 2: Clonar un repositorio + +{% data reusables.command_line.providing-token-as-password %} + +Para evadir estos mensajes, puedes utilizar el almacenamiento de contraseñas en caché de Git. Para obtener más información, consulta la sección "[Almacenar tus credenciales de GitHub en caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git)". + +{% warning %} + +**Advertencia**: Los tokens tienen acceso de escritura/lectura y deben tratarse como contraseñas. Si ingresas tu token en la URL del clon cuando clonas o agregas un remoto, Git la escribe en tu archivo _.git/config_ como texto plano, lo que representa un riesgo de seguridad. + +{% endwarning %} + +### Further reading + +- "[Autorizar las Apps de OAuth](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/es-ES/content/github/extending-github/index.md b/translations/es-ES/content/github/extending-github/index.md new file mode 100644 index 0000000000000..e0b41816869b3 --- /dev/null +++ b/translations/es-ES/content/github/extending-github/index.md @@ -0,0 +1,18 @@ +--- +title: Extender GitHub +redirect_from: + - /categories/86/articles/ + - /categories/automation/ + - /categories/extending-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% link_in_list /getting-started-with-the-api %} +{% link_in_list /git-automation-with-oauth-tokens %} +{% link_in_list /about-webhooks %} diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md new file mode 100644 index 0000000000000..e2c5685c74ecc --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -0,0 +1,60 @@ +--- +title: Acerca del escaneo de código +intro: 'Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades de seguridad y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/managing-security-vulnerabilities/about-automated-code-scanning +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} + +### Acerca de {% data variables.product.prodname_code_scanning %} + +{% data reusables.code-scanning.about-code-scanning %} + +Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar, clasificar y priorizar los arreglos a problemas existentes en tu código. {% data variables.product.prodname_code_scanning_capc %} también previene a los desarrolladores de introducir nuevos problemas. Puedes programar días y horas específicos para los escaneos, o activarlos cuando ocurra un evento específico en el repositorio, tal como una carga de información. + +Si {% data variables.product.prodname_code_scanning %} encuentra una vulnerabilidad potencial o un error en tu código, {% data variables.product.prodname_dotcom %} mostrará una alerta en el repositorio. {% data variables.product.prodname_dotcom %} cerrará la alerta una vez que arregles el código que la activó. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/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 webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." + +Para comenzar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)". + +### Acerca de {% data variables.product.prodname_codeql %} + +Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). {% data variables.product.prodname_codeql %} trata el código como datos, lo cual te permite encontrar vulenrabilidades potenciales en tu código con más confianza que en los anallizadores estáticos trandicionales. + +{% data variables.product.prodname_ql %}Es el lenguaje de consulta que impulsa a {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} es un lenguaje de programación lógico orientado a objetos. {% data variables.product.company_short %}, los expertos del lenguaje, y los investigadores de seguridad crean las consultas que se utilizan para {% data variables.product.prodname_code_scanning %}, y éstas son de código abierto. La comunidad mantiene y actualiza estas consultas para mejorar el análisis y reducir los falsos positivos. Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab. + +Para obtener más información acerca de las terminales de la API para {% data variables.product.prodname_code_scanning %}, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)". + +{% data reusables.code-scanning.supported-languages %} + +Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) en la documentación de {% data variables.product.prodname_codeql %}. + +{% if currentVersion == "free-pro-team@latest" %} + +### Acerca de la facturación para {% data variables.product.prodname_code_scanning %} + +{% data variables.product.prodname_code_scanning_capc %} utiliza {% data variables.product.prodname_actions %}, y cada ejecución de un flujo de trabajo de {% data variables.product.prodname_code_scanning %} consume minutos para {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". + +{% endif %} + +### Acerca de las herramientas de escaneo de código de terceros + +{% data reusables.code-scanning.you-can-upload-third-party-analysis %} + +{% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %} + +{% data reusables.code-scanning.get-started-uploading-third-party-data %} + +### Further reading + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" +- [{% 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) en el sitio web del Comité OASIS diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md new file mode 100644 index 0000000000000..0a82d33ace2f9 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md @@ -0,0 +1,26 @@ +--- +title: Acerca de la integración con el escaneo de código +shortTitle: Acerca de la integración +intro: 'Puedes llevar a cabo un {% data variables.product.prodname_code_scanning %} externamente y luego mostrar los resultados en {% data variables.product.prodname_dotcom %}, o configurar webhooks que escuchen a la actividad de {% data variables.product.prodname_code_scanning %} en tu repositorio.' +product: '{% data reusables.gated-features.code-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} + +Como alternativa a ejecutar un {% data variables.product.prodname_code_scanning %} dentro de {% data variables.product.prodname_dotcom %}, puedes realizar el análisis en cualquier otra parte y luego cargar los resultados. Las alertas para {% data variables.product.prodname_code_scanning %} que puedes ejecutar externamente se muestran de la misma forma que aquellas para el {% data variables.product.prodname_code_scanning %} que ejecutas con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". + +Si utilizas una herramienta de análisis estático de terceros que pueda producir resultados como datos del Formato de Intercambio de Resultados para Análisis Estático (SARIF) 2.1.0, puedes cargarlos a {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". + +### Integraciones con webhooks + +Puedes utilizar los webhooks del {% data variables.product.prodname_code_scanning %} para crear o configurar integraciones, tales como [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), que se suscriban a los eventos de {% data variables.product.prodname_code_scanning %} en tu repositorio. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_location %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". + +### Further reading + +* "[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" +* "[Utilizar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} con tu sistema de IC existente](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)" +* "[Soporte de SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md new file mode 100644 index 0000000000000..b4e5c181a5f06 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md @@ -0,0 +1,11 @@ +--- +title: Escanear tu código automáticamente para encontrar vulnerabilidades y errores +shortTitle: Escanear automáticamente +intro: 'Puedes encontrar vulnerabilidades y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' +mapTopic: verdadero +product: '{% data reusables.gated-features.code-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md new file mode 100644 index 0000000000000..d18a99b925a57 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -0,0 +1,316 @@ +--- +title: Configurar el escaneo de código +intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea el código en tu proyecto para encontrar vulnerabilidades y errores.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar {% data variables.product.prodname_code_scanning %} para el mismo.' +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Acerca de la configuración de {% data variables.product.prodname_code_scanning %} + +Puedes ejecutar el {% data variables.product.prodname_code_scanning %} dentro de {% data variables.product.product_location %} utilizando {% data variables.product.prodname_actions %}, o desde tu sistema de integración continua (IC) utilizando el {% data variables.product.prodname_codeql_runner %}. Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". Para obtener más información acerca del {% data variables.product.prodname_codeql_runner %}, consulta la sección [Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". + +Este artìculo es acerca de ejecutar el {% 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 %}. + +Antes de que puedas configurar {% data variables.product.prodname_code_scanning %} para un repositorio, debes habilitar {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a dicho repositorio. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. + +{% data reusables.code-scanning.edit-workflow %} + +El análisis de {% data variables.product.prodname_codeql %} es tan solo un tipo de {% data variables.product.prodname_code_scanning %} que puedes hacer en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} en {% data variables.product.prodname_dotcom_the_website %}{% endif %} contiene otros flujos de trabajo de {% data variables.product.prodname_code_scanning %} que puedes utilizar. {% if currentVersion == "free-pro-team@latest" %}Puedes encontrar una selección de estos en la página de "Iniciar con el {% data variables.product.prodname_code_scanning %}", a la cual puedes acceder desde la pestaña de **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**.{% endif %} Los ejemplos especificos que se muestran en este artículo se relacionan con el archivo del {% data variables.product.prodname_codeql_workflow %}. + +### Editing a code scanning workflow + +{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. 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. En tu repositorio, navega hasta el archivo de flujo de trabajo que deseas editar. +1. En el ángulo superior derecho de la vista del archivo, para abrir el editor de flujo de trabajo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.![Botón para editar un archivo de flujo de trabajo](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. Después de que hayas editado el archivo, da clic en **Iniciar confirmación** y completa el formato de "Cambios de la confirmación". Puedes elegir confirmar directamente en la rama actual, o crear una rama nueva e iniciar una solicitud de extracción. ![Confirmar la actualización del flujo de trabajo de codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png) + +Para obtener más información acerca de cómo editar los archivos de flujo de trabajo, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." + +### Configurar la frecuencia + +Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio. + +Escanear el código en cada carga al repositorio, y cada vez que se crea una solicitud de extracción, previene que los desarrolladores introduzcan vulnerabilidades y errores nuevos en dicho código. Escanear el código con una programación definida te informará de las últimas vulnerabilidades y errores que {% data variables.product.company_short %}, los investigadores de seguridad, y la comunidad descubren, aún cuando los desarrolladores no estén manteniendo el repositorio activamente. + +#### Escanear cuando se carga información + +Si utilizas el flujo de trabajo predeterminado, el {% data variables.product.prodname_code_scanning %} escaneará el código en tu repositorio una vez por semana, adicionalmente a los escaneos activados por los eventos. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)". + +#### Escanear las solicitudes de extracción + +El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. {% if currentVersion ver_gt "enterprise-server@2.21" %}El evento de `pull_request` no se activará si la solicitud de cambios se abrió desde una bifurcación privada.{% else %}Si una solicitud de cambios es de una bifurcación privada, el evento de `pull_request` solo se activará si seleccionaste la opción de "Ejecutar flujos de trabajo desde solicitudes de cambios de la bifurcación" en la configuración del repositorio. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". + +Para obtener más información acerca del evento `pull_request`, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". + +#### Evitar escaneos innecesarios en las solicitudes de cambios + +Puede que quieras evitar que se active un escaneo de código en solicitudes de cambio específicas que se dirijan a la rama predeterminada, independientemente de los archivos que se hayan cambiado. Puedes configurar esto si especificas `on:pull_request:paths-ignore` o `on:pull_request:paths` en el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. Por ejemplo, si los únicos cambios en una solicitud de cambios se hacen en archivos con las extensiones `.md` o `.txt`, puedes utilizar el siguiente arreglo de `paths-ignore`. + +``` yaml +on: + push: + branches: [main, protected] + pull_request: + branches: [main] + paths-ignore: + - '**/*.md' + - '**/*.txt' +``` + +{% note %} + +**Notas** + +* `on:pull_request:paths-ignore` y `on:pull_request:paths` configuran condiciones que determinan si una acción en el flujo de trabajo se ejecutará en una solicitud de cambios. No determinan qué archivos se analizarán cuando las acciones _se_ ejecuten. Cuando una solicitud de cambios contiene cualquier archivo que no coincida con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, el flujo de trabajo ejecuta las acciones y escanea todos los archivos que cambiaron en la solicitud de cambios, incluyendo aquellos que coincidieron con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, a menos de que éstos se hayan excluido. Para obtener más información sobre cómo excluir archivos del análisis, consulta la sección "[Especificar directorios para escanear](#specifying-directories-to-scan)". +* Para los archivos de flujo de trabajo del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, no utilices las palabras clave `paths-ignore` o `paths` con el evento `on:push`, ya que es probable que cause que falten análisis. Para obtener resultados precisos, el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} necesita poder comparar los cambios nuevos con el análisis de la confirmación previa. + +{% endnote %} + +Para obtener más información acerca de utilizar `on:pull_request:paths-ignore` y `on:pull_request:paths` para determinar cuando se ejecutará un flujo de trabajo para una solicitud de cambios, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". + +#### Escanear de forma pre-programada + +El flujo de trabajo del {% data variables.product.prodname_code_scanning %} utiliza el evento `pull_request` para activar un escaneo de código en la confirmación `HEAD` de una solicitud de extracción. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)". + +{% note %} + +**Nota**: {% data variables.product.prodname_dotcom %} solo ejecuta jobs pre-programados que se encuentren en flujos de trabajo de la rama predeterminada. Cambiar la programación en un flujo de trabajo en cualquier otra rama no tendrá efecto hasta que fusiones esta rama con la predeterminada. + +{% endnote %} + +#### Ejemplo + +El siguiente ejemplo muestra un {% data variables.product.prodname_codeql_workflow %} para un repositorio particular que tiene una rama predeterminada que se llama `main` y una protegida que se llama `protected`. + +``` yaml +on: + push: + pull_request: + schedule: + - cron: '0 15 * * 0' +``` + +Este flujo de trabajo escanea: +* Cada subida a la rama predeterminada y a la rama protegida +* Cada solicitud de cambios a la rama predeterminada +* La rama predeterminada a las 3 P.M. cada domingo + +### Especificar un sistema operativo + +Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Especificas el sistema operativo utilizando una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% else %} + +Si eliges utilizar une ejecutor auto-hospedado para el escaneo de código, puedes especificar un sistema operativo si utilizas una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% endif %} + +``` yaml +jobs: + analyze: + name: Analyze + runs-on: [self-hosted, ubuntu-latest] +``` + +{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} + +{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. Para obtener más información, consulta las secciones {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" y "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}". + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Debes asegurarte de qeu Git esté en la variable "PATH" en tus ejecutores auto-hospedados.{% else %}Si utilizas el ejecutor auto-hospedado, debes asegurarte de que git esté en la variable "PATH".{% endif %} + +### Cambiar los lenguajes que se analizan + +El {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} detecta automáticamente el código que se escribe en los lenguajes compatibles. + +{% data reusables.code-scanning.supported-languages %} + +El archivo predeterminado del {% data variables.product.prodname_codeql_workflow %} contiene una matriz de compilación que se llama `language`, la cual lista los lenguajes en tu repositorio que se han analizado. El {% data variables.product.prodname_codeql %} llena automáticamente esta matriz cuando agregas el {% data variables.product.prodname_code_scanning %} a un repositorio. Cuando se utiliza la matriz de `language` se optimiza a {% data variables.product.prodname_codeql %} para ejecutar cada análisis en paralelo. Te recomendamos que todos los flujos de trabajo adopten esta configuración debido a los beneficios de rendimiento que implica el paralelizar las compilaciones. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)". + +{% data reusables.code-scanning.specify-language-to-analyze %} + +Si tu flujo de trabajo utiliza la matriz `language`, entonces {% data variables.product.prodname_codeql %} se codifica fijamente para analizar únicamente los lenguajes en dicha matriz. Para cambiar los lenguajes que quieres analizar, edita el valor de la variable de la matriz. Puedes eliminar un lenguaje para que no se analice, o puedes agregar alguno que no estuviera presente ene l repositorio cuando se habilitó el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se habilitó el {% data variables.product.prodname_code_scanning %}, y luego quieres agregar código de Python, entonces necesitarás agregar `python` a la matriz. + +```yaml +jobs: + analyze: + name: Analyze + ... + strategy: + fail-fast: false + matrix: + language: ['javascript', 'python'] +``` + +Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces {% data variables.product.prodname_codeql %} se configurará para ejecutar un análisis secuencialmente. Si no especificas los lenguajes en los flujos de trabajo, {% data variables.product.prodname_codeql %} detectará e intentará analizar cualquier lenguaje compatible que haya en el repositorio. Si quieres elegir qué lenguajes analizar sin utilizar una matriz, puedes utilizar el parámetro `languages` en la acción de `init`. + +```yaml +- uses: github/codeql-action/init@v1 + with: + languages: cpp, csharp, python +``` +{% if currentVersion == "free-pro-team@latest" %} +### Analizar las dependencias de Python + +Para los ejecutores hospedados en GitHub que utilicen solo Linux, el {% data variables.product.prodname_codeql_workflow %} intentarà instalar automàticamente las dependencias de Python para dar màs resultados para el anàlisis de CodeQL. Puedes controlar este comportamiento si especificas el paràmetro `setup-python-dependencies` para la acciòn que el paso "Initialize CodeQL" llama. Predeterminadamente, este paràmetro se configura como `true`: + +- Si el repositorio contiene còdigo escrito en Python, el paso "Initialize CodeQL" instala las dependencias necesarias en el ejecutor hospedado en GitHub. Si la instalaciòn automàtica es exitosa, la acciòn tambièn configura la variable de ambiente `CODEQL_PYTHON` en el archivo ejecutable de Python que incluye las dependencias. + +- Si el repositorio no tiene ninguna dependencia de Python o si las dependencias se especifican en una forma inesperada, obtendràs una advertencia y la acciòn seguirà con los jobs restantes. La acciòn puede ejecutarse exitosamente aùn cuando existan problemas para interpretar las dependencias, pero los resultados podrìan estar incompletos. + +Como alternativa, puedes instalar las dependencias de Python manualmente en cualquier sistema operativo. Necesitaràs agregar a `setup-python-dependencies` y configurarlo como `false`, asì como configurar `CODEQL_PYTHON` para el ejecutable de Python que incluye las dependencias, tal como se muestra en este extracto de flujo de trabajo: + +```yaml +jobs: + CodeQL-Build: + + runs-on: ubuntu-latest + + steps: + - name: Checkout repository + uses: actions/checkout@v2 + - name: Set up Python + uses: actions/setup-python@v2 + with: + python-version: '3.x' + - name: Install dependencies + run: | + python -m pip install --upgrade pip + if [ -f requirements.txt ]; + then pip install -r requirements.txt; + fi + # Set the `CODEQL-PYTHON` environment variable to the Python executable + # that includes the dependencies + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV + - name: Initialize CodeQL + uses: github/codeql-action/init@v1 + with: + languages: python + # Override the default behavior so that the action doesn't attempt + # to auto-install Python dependencies + setup-python-dependencies: false +``` +{% endif %} + +### Ejecutar consultas adicionales + +{% data reusables.code-scanning.run-additional-queries %} + +Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. + +``` yaml +- uses: github/codeql-action/init@v1 + with: + queries: COMMA-SEPARATED LIST OF PATHS +``` + +También puedes ejecutar conjuntos de consultas adicionales si los especificas en un archivo de configuración. Los conjuntos de consultas son colecciones de consultas que a menudo se agrupan por propósito o lenguaje. + +{% data reusables.code-scanning.codeql-query-suites %} + +Puedes ejecutar consultas adicionales si las especificas en un archivo de configuración. So quieres ejecutar el conjunto combinado de consultas adicionales que se especifica aquí y en el archivo de configuración, agrega como prefijo el valor `queries` en el flujo de trabajo con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)". + +En el siguiente ejemplo, el símbolo `+` se asegura de que las consultas adicionales especificadas se utilicen en conjunto con cualquier otra consulta que se especifique en el archivo de configuración referenciado. + +``` yaml +- uses: github/codeql-action/init@v1 + with: + config-file: ./.github/codeql/codeql-config.yml + queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main +``` + +### Utilizar una herramienta de escaneo de código de terceros + +Como alternativa para especificar qué consultas se ejecutarán en un archivo de flujo de trabajo, puedes hacer esto en un archivo de configuración diferente. También puedes utilizar un archivo de configuración para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis. + +En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acción `init` para especificar la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _./.github/codeql/codeql-config.yml_. + +``` yaml +- uses: github/codeql-action/init@v1 + with: + config-file: ./.github/codeql/codeql-config.yml +``` + +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +La configuración en el archivo se escribe en formato YAML. + +#### Especificar consultas adicionales + +Puedes especificar consultas adicionales en una matriz de `queries`. Cada elemento de la matriz contiene un parámetro de `uses` con un valor que identifica un archivo de consulta simple, un directorio que contiene los archivos de consulta, o un archivo de suite de definiciones de una consulta. + +``` yaml +queries: + - uses: ./my-basic-queries/example-query.ql + - uses: ./my-advanced-queries + - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls +``` + +Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración. + +Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)". + +#### Inhabilitar las consultas predeterminadas + +Si solo quieres ejecutar consultas personalizadas, puedes inhabilitar las consultas de seguridad predeterminadas si agregas `disable-default-queries: true` a tu archivo de configuración. + +#### Especificar directorios para escanear + +Para los lenguajes interpretados compatibles con {% data variables.product.prodname_codeql %} (Python y JavaScript/TypeScript), puedes restringir el {% data variables.product.prodname_code_scanning %} para los archivos que estén en directorios específicos si agregas una matriz de `paths` al archivo de configuración. Puedes excluir del análisis los archivos en los directorios específicos si agregas un arreglo de `paths-ignore`. + +``` yaml +paths: + - src +paths-ignore: + - src/node_modules + - '**/*.test.js' +``` + +{% note %} + +**Nota**: + +* Las palabras clave `paths` y `paths-ignore` que se utilizan en el contexto del archivo de configuración del {% data variables.product.prodname_code_scanning %} no deben confundirse con las mismas palabras clave cuando se utilizan para `on..paths` en un flujo de trabajo. Cuando se tulizan para modificar `on.` en un flujo de trabajo, éstas determinan si las acciones se ejecutarán cuando alguien modifique el código en los directorios especificados. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% 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 ejemplo, `foo/**`, `**/foo`, y `foo/**/bar` son todas sintaxis permitidas, pero `**foo` no lo es. Sin embargo, puedes utilizar asteriscos sencillos con otros caracteres, tal como se muestra en el ejemplo. Tendrás que poner entre comillas todo lo que contenga un caracter de `*`. + +{% endnote %} + +Para los lenguajes compilados, si quieres limitar el {% data variables.product.prodname_code_scanning %} para directorios específicos en tu proyecto, debes especificar los pasos de compilación adecuados en el flujo de trabajo. Los comandos que necesites utilizar para excluir un directorio de la compilación dependerán en tu sistema de compilación. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". + +Puedes analizar rápidamente partes pequeñas de un monorepo cuando modificas el código en directorios específicos. Necesitarás tanto excluir los directorios en tus pasos de compilación como utilizar las palabras clave `paths-ignore` y `paths` para [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) en tu archivo de flujo de trabajo. + +#### Ejemplos de archivos de configuración + +{% data reusables.code-scanning.example-configuration-files %} + +### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados + +{% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} + +{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información acerca de cómo configurar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)". + +### Acceder a repositorios privados + +Si tu flujo de trabajo para {% data variables.product.prodname_code_scanning %} accede a repositorios privados en {% data variables.product.prodname_dotcom %}, necesitarás configurar Git para autenticarte con un token de acceso personal. Define el secreto en el ambiente de ejecución utilizando `jobs..steps[*].env` en tu flujo de trabajo antes de cualquier acción de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" y "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". + +Por ejemplo, la siguiente configuración hace que Git reemplace las URL enteras de los repositorios `ghost/foo`, `ghost/bar`, y `ghost/baz` en {% data variables.product.prodname_dotcom_the_website %} con aquellas que incluyen tu token de acceso personal y que almacenaste en la variable de ambiente `ACCESS_TOKEN`. + +{% raw %} +```yaml +steps: +- name: Configure access to private repositories + env: + TOKEN: ${{ secrets.ACCESS_TOKEN }} + run: | + git config --global url."https://${TOKEN}@github.com/ghost/foo".insteadOf "https://github.com/ghost/foo" + git config --global url."https://${TOKEN}@github.com/ghost/bar".insteadOf "https://github.com/ghost/bar" + git config --global url."https://${TOKEN}@github.com/ghost/baz".insteadOf "https://github.com/ghost/baz" +``` +{% endraw %} + +### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. + +{% data variables.product.prodname_dotcom %} puede mostrar los datos de análisis de código que se generan externamente con una herramienta de terceros. Puedes mostrar el análisis de código de una herramienta de terceros en {{ site.data.variables.product.prodname_dotcom }} su agregas la acción `upload-sarif` en tu flujo de trabajo. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md new file mode 100644 index 0000000000000..1b6831d3b96ee --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -0,0 +1,165 @@ +--- +title: Configurar el escaneo de còdigo de CodeQL en tu sistema de IC +shortTitle: Configuración en tu IC +intro: 'Puedes configurar la forma en la que {% data variables.product.prodname_codeql_runner %} escanea el código en tu proyecto y en la que carga los resultados a {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.code-scanning %}' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} + +### Acerca de configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC + +Para integrar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC, puedes utilizar el {% data variables.product.prodname_codeql_runner %}. Para obtener màs informaciòn, consulta la secicòn "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". + +En general, se invoca el {% data variables.product.prodname_codeql_runner %} de la siguiente manera. + +``` +$ /path/to-runner/codeql-runner-OS +``` + +`/path/to-runner/` depende de si descargaste el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC. `codeql-runner-OS` depende del sistema operativo que utilices. Hay tres versiones del {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, y `codeql-runner-win`, para sistemas Linux, macOS y Windows respectivamente. + +Para personalizar la forma en la que el {% data variables.product.prodname_codeql_runner %} escanea tu código, puedes utilizar marcadores, tales como `--languages` y `--queries`,o puedes especificar configuraciones personalizadas en un archivo de configuración por separado. + +### Invalidar la detección automática de lenguaje + +El {% data variables.product.prodname_codeql_runner %} detecta automáticamente y escanea el código que se ha escrito en los lenguajes compatibles. + +{% data reusables.code-scanning.supported-languages %} + +{% data reusables.code-scanning.specify-language-to-analyze %} + +Para anular la detección automática de lenguajes, ejecuta el comando `init` con el marcador `--languages`, seguido de una lista separada por comas de las palabras clave de los lenguajes. Las palabras clave para los lenguajes compatibles son `cpp`, `csharp`, `go`, `java`, `javascript`, y `python`. + +``` +$ /path/to-runner/codeql-runner-linux init --languages cpp,java +``` + +### Ejecutar consultas adicionales + +{% data reusables.code-scanning.run-additional-queries %} + +{% data reusables.code-scanning.codeql-query-suites %} + +Para agregar una o más consultas, pasa una lista separada por comas de las rutas al marcador `--queries` del comando `init`. También puedes especificar consultas adicionales en un archivo de configuración. + +Si también estás usando un archivo de configuración para los ajustes personalizados y también estás especificando consultas adicionales con el marcador de `--queries`, el {% data variables.product.prodname_codeql_runner %} utilizará consultas adicionales que se especifican con el marcador `--queries` en vez de con cualquier otro en el archivo de configuración. Si quieres ejecutar el conjunto combinado de consultas adicionales que se especifican con el marcador y en el archivo de configuración, usa un prefijo en el valor que se pasa a `--queries` con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)". + +En el siguiente ejemplo, el símbolo `+` garantiza que el {% data variables.product.prodname_codeql_runner %} utilizará consultas adicionales junto con cualquier otra consulta que se especifique en el archivo de configuración referenciado. + +``` +$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml + --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main +``` + +### Utilizar una herramienta de escaneo de código de terceros + +En vez de pasar información adicional a los comandos de {% data variables.product.prodname_codeql_runner %}, puedes especificar ajustes personalizados en un archivo de configuración por separado. + +El archivo de configuración es un archivo de YAML. Utiliza una sintaxis similar a aquella del flujo de trabajo para {% data variables.product.prodname_actions %}, de acuerdo como se ilustra en los siguientes ejemplos. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)". + +Utiliza el marcador `--config-file` del comando `init` para especificar el archivo de configuración. El valor de `--config-file` es la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _.github/codeql/codeql-config.yml_. + +``` +$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml +``` + +#### Ejemplos de archivos de configuración + +{% data reusables.code-scanning.example-configuration-files %} + +### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados + +Para los lenguajes C/C++, C#, y Java, {% data variables.product.prodname_codeql %} compila el código antes de analizarlo. {% data reusables.code-scanning.analyze-go %} + +Para varios sistemas de compilación comunes, el {% data variables.product.prodname_codeql_runner %} puede compilar el código automáticamente. Para intentar compilar el código automáticamente, ejecuta `autobuild` entre los pasos de `init` y `analyze`. Nota que, si tu repositorio necesita una versión específica de una herramienta de compilación, puede que necesites instalar dicha herramienta manualmente primero. + +El proceso de `autobuild` solo intenta siempre compilar _un_ solo lenguaje compilado para un repositorio. El lenguaje que se selecciona automáticamente para su análisis es aquél presente en más archivos. Si quieres elegir un lenguaje explícitamente, utiliza el marcador `--language` del comando `autobuild`. + +``` +$ /path/to-runner/codeql-runner-linux autobuild --language csharp +``` + +Si el comando `autobuild` no puede compilar tu código, tú mismo puedes ejecutar los pasos de compilación entre los pasos de `init` y `analyze`. Para obtener màs informaciòn, consulta la secciòn "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system#compiled-language-example)". + +### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. + +Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} carga los resultados del {% data variables.product.prodname_code_scanning %} cuando ejecutas el comando `analyze`. También puedes cargar archivos de SARIF por separado si utilizas el comando `upload`. + +Una vez que hayas cargado los datos, {% data variables.product.prodname_dotcom %} mostrará las alertas en tu repositorio. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". + +### Referencia de comandos de {% data variables.product.prodname_codeql_runner %} + +El {% data variables.product.prodname_codeql_runner %} es compatible con los siguientes comandos y marcadores. + +#### `init` + +Inicializa el {% data variables.product.prodname_codeql_runner %} y crea una base de datos de {% data variables.product.prodname_codeql %} para analizar cada lenguaje. + +| Marcador | Requerido | Valor de entrada | +| -------------------------------- |:---------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repositorio` | ✓ | Nombre del repositorio a inicializar. | +| `--github-url` | ✓ | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio. | +| `--github-auth` | ✓ | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal. | +| `--languages` | | Lista separada por comas de los lenguajes a analizar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} detecta y analiza todos los lenguajes compatibles en el repositorio. | +| `--queries` | | Lista separada por comas de las consultas adicionales a ejecutar, adicionalmente a la suite predeterminada de consultas de seguridad. | +| `--config-file` | | Ruta al archivo de configuración personalizado. | +| `--codeql-path` | | Ruta a una copia del CLI ejecutable de {% data variables.product.prodname_codeql %} a utilizar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} descarga una copia. | +| `--temp-dir` | | Directorio donde se almacenan los archivos temporales. El predeterminado es _./codeql-runner_. | +| `--tools-dir` | | Directorio donde las herramientas de {% data variables.product.prodname_codeql %} y otros archivos se almacenan entre ejecuciones. El predeterminado es un subdirectorio del directorio principal. | +| `--checkout-path` | | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo. | +| `--debug` | | Ninguno. Imprime una salida más verbosa. | +| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | + +#### `autobuild` + +Intenta compilar el código para los lenguajes compilados de C/C++, C#, y Java. Para estos lenguajes, {% data variables.product.prodname_codeql %} compila el código antes de analizarlo. Ejecuta `autobuild` entre los pasos de `init` y `analyze`. + +| Marcador | Requerido | Valor de entrada | +| --------------------------- |:---------:| ------------------------------------------------------------------------------------------------------------------------------------------- | +| `--language` | | El lenguaje a compilar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} compila el lenguaje con más archivos. | +| `--temp-dir` | | Directorio donde se almacenan los archivos temporales. El predeterminado es _./codeql-runner_. | +| `--debug` | | Ninguno. Imprime una salida más verbosa. | +| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | + +#### `analyze` + +Analiza el código en las bases de datos de {% data variables.product.prodname_codeql %} y carga los resultados a {% data variables.product.product_location %}. + +| Marcador | Requerido | Valor de entrada | +| -------------------------------- |:---------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repositorio` | ✓ | Nombre del repositorio que se analizará. | +| `--commit` | ✓ | SHA de la confirmación que se analizará. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`. | +| `--ref` | ✓ | Nombre de la referencia a analizar, por ejemplo `refs/heads/main`. En Git y en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`. | +| `--github-url` | ✓ | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio. | +| `--github-auth` | ✓ | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal. | +| `--checkout-path` | | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo. | +| `--no-upload` | | Ninguno. Impide que el {% data variables.product.prodname_codeql_runner %} cargue los resultados a {% data variables.product.product_location %}. | +| `--output-dir` | | Directorio en donde se almacenan los archivos SARIF de salida. El predeterminado está en el directorio de archivos temporales. | +| `--temp-dir` | | Directorio donde se almacenan los archivos temporales. El predeterminado es _./codeql-runner_. | +| `--debug` | | Ninguno. Imprime una salida más verbosa. | +| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | + +#### `upload` + +Carga los archivos SARIF a {% data variables.product.product_location %}. + +| Marcador | Requerido | Valor de entrada | +| -------------------------------- |:---------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--sarif-file` | ✓ | El archivo SARIF a cargar, o un directorio que contiene varios archivos SARIF. | +| `--repositorio` | ✓ | Nombre del repositorio que se analizó. | +| `--commit` | ✓ | SHA de la confirmación que se analizó. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`. | +| `--ref` | ✓ | Nombre de la referencia que se analizó, por ejemplo `refs/heads/main`. En Git y en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`. | +| `--github-url` | ✓ | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio. | +| `--github-auth` | ✓ | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal. | +| `--checkout-path` | | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo. | +| `--debug` | | Ninguno. Imprime una salida más verbosa. | +| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md new file mode 100644 index 0000000000000..86a83ee68d0d8 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -0,0 +1,116 @@ +--- +title: Configurar el flujo de trabajo de CodeQL para los lenguajes compilados +shortTitle: Configurar para los lenguajes compilados +intro: 'Puedes configurar cómo {% data variables.product.prodname_dotcom %} utiliza el {% data variables.product.prodname_codeql_workflow %} para escanear el código escrito en los lenguajes compilados para las vulnerabilidades y errores.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'Si tienes permisos de escritura en un repositorio, puedes configurar el {% data variables.product.prodname_code_scanning %} para éste.' +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 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Acerca de {% data variables.product.prodname_codeql_workflow %} y los lenguajes compilados + +Habilitas {% data variables.product.prodname_dotcom %} para que ejecute el {% data variables.product.prodname_code_scanning %} para tu repositorio si agregas un flujo de trabajo de {% data variables.product.prodname_actions %} a éste. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. + +{% data reusables.code-scanning.edit-workflow %} +Para obtener información general acerca de cómo configurar +el {% data variables.product.prodname_code_scanning %} y cómo editar archivos de flujo de trabajo, consulta las secciones "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" y "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +### Acerca de autobuild para {% data variables.product.prodname_codeql %} + +El escaneo de código funciona ejecutando consultas contra una o más bases de datos. Cada base de datos contiene una representación de todo el código de tu repositorio en un solo lenguaje. Para los lenguajes compilados de C/C++, C#, y Java, el proceso de poblar esta base de datos involucra compilar el código y extraer los datos. {% data reusables.code-scanning.analyze-go %} + +{% data reusables.code-scanning.autobuild-compiled-languages %} + +Si tu flujo de trabajo utiliza una matriz de `language`, el `autobuild` intentará compilar cada uno de los lenguajes que se listen en ella. Sin una matriz, el `autobuild` intentará compilar el lenguaje compatible que tenga más archivos de origen en el repositorio. Con la excepción de Go, el análisis de otros lenguajes compilados en tu repositorio siempre fallará a menos de que proporciones comandos de compilación específicos. + +{% note %} + +**Nota**: Si utilizas los ejecutores auto-hospedados para {% data variables.product.prodname_actions %}, tal vez necesites instalar software adicional para utilizar el proceso de `autobuild`. Adicionalmente, si tu repositorio requiere de una versión específica de una herramienta de compilación, tal vez necesites instalarla manualmente. Para obtener más información, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". + +{% endnote %} + +#### C/C++ + +| Tipo de sistema compatible | Nombre del sistema | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Sistema operativo | Windows, macOS, y Linux | +| Sistema de compilación | Windows: MSbuild y scripts de compilación
    Linux y macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, y scripts de compilación | + +El comportamiento del paso de `autobuild` varía de acuerdo con el sistema operativo en el que se ejecute la extracción. En Windows, el paso de `autobuild` intenta autodetectar un método de compilación adecuado para C/C++ utilizando el siguiente enfoque: + +1. Invocar a`MSBuild.exe` en el archivo de la solución (`.sln`) o del proyecto (`.vcxproj`) que esté más cercano a la raíz. Si `autobuild` detecta soluciones o archivos de proyecto múltiples en la misma profundidad (la más corta) desde el directorio de nivel superior, entonces intentará compilarlos todos. +2. Invocar un script que se ve como un script de compilación—_build.bat_, _build.cmd_, _and build.exe_ (en ese órden). + +En Linux y macOS, el paso de `autobuild` revisa los archivos presentes en el repositorio para determinar el sistema de compilación que se utilizó: + +1. Busca un sistema de compilación en el directorio raíz. +2. Si no se encuentra ninguno, busca un directorio único en los subdirectorios, el cual cuente con un sistema de compilación para C/C++. +3. Ejecuta un comando adecuado para configurar el sistema. + +#### C + +| Tipo de sistema compatible | Nombre del sistema | +| -------------------------- | --------------------------------------------------- | +| Sistema operativo | Windows y Linux | +| Sistema de compilación | .NET y MSbuild, así como los scripts de compilación | + +El proceso de `autobuild` intenta autodetectar un método de compilación adecuado para C# utilizando el siguiente acercamiento: + +1. Invoca a `dotnet build` en el archivo (`.sln`) de la solución o en el archivo (`.csproj`) del proyecto que esté más cercano a la raíz. +2. Invoca a `MSbuild` (Linux) o a `MSBuild.exe` (Windows) en el archivo de la solución o del proyecto más cercano a la raíz. Si `autobuild` detecta soluciones o archivos de proyecto múltiples en la misma profundidad (la más corta) desde el directorio de nivel superior, entonces intentará compilarlos todos. +3. Invoca un script que se parece a un script de compilación—_build_ y _build.sh_ (en ese orden, para Linux) o _build.bat_, _build.cmd_, _y build.exe_ (en ese orden, para Windows). + +#### Java + +| Tipo de sistema compatible | Nombre del sistema | +| -------------------------- | ----------------------------------------- | +| Sistema operativo | Windows, macOS, y Linux (sin restricción) | +| Sistema de compilación | Gradle, Maven y Ant | + +El proceso de `autobuild` intenta determinar el sistema de compilación para las bases de código de Java aplicando esta estrategia: + +1. Busca un archivo de compilación en el directorio raíz. Busca a Gradle en Maven y luego Ant compila los archivos. +2. Ejecuta el primer archivo de compilación que encuentre. Si tanto los archivos de Gradle como los de Maven están presentes, se utiliza el archivo de Gradle. +3. De lo contrario, usca los archivos de compilación en los subidrectorios directos del directorio raíz. Si solo un subdirectorio contiene archivos de compilación, ejecuta el primer archivo identificado en este subdirectorio (utilizando la misma preferencia que para 1). Si más de un subdirectorio contiene archivos de compilación, reporta un error. + +### Agregar pasos de compilación para un lenguaje compilado + +{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información sobre cómo editar el archivo de flujo de trabajo, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)". + +Después de eliminar el paso de `autobuild`, quita el comentario del paso de `run` y agrega los comandos de compilación que son adecuados para tu repositorio. El paso de `run` en el flujo de trabajo ejecuta programas de línea de comandos que utiizan el shell del sistema operativo. Puedes modificar estos comandos y agregar más de ellos para personalizar el proceso de compilación. + +``` yaml +- run: | + make bootstrap + make release +``` + +Para obtener más información acerca de la palabra clave `run`, consulta la sección "[Sintaxis de flujo de trabajo para { site.data.variables.product.prodname_actions }}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)". + +Si tu repositorio contiene lenguajes compilados múltiples, puedes especificar los compandos de compilación específicos de estos lenguajes. Por ejemplo, si tu repositorio contiene C/C++, C# y Java, y el `autobuild` compila correctamente C/C++ y C#, pero falla con Java, puedes utilizar la siguiente configuración en tu flujo de trabajo, después del paso `init`. Esto especifica los pasos de compilación para Java mientras que aún utiliza el `autobuild` para C/C++ y C#: + +```yaml +- if: matrix.language == 'cpp' || matrix.language == 'csharp' + name: Autobuild + uses: github/codeql-action/autobuild@v1 + +- if: matrix.language == 'java' + name: Build Java + run: | + make bootstrap + make release +``` + +Para obtener más información acerca del condicional `if`, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)". + +Para obtener más tips e ides sobre por qué el `autobuild` no está compilando tu código, consulta la sección "[Solucionar errores en el flujo de trabajo de {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)". + +Si agregas pasos de compilación manualmente para los lenguajes compilados y el {% data variables.product.prodname_code_scanning %} aún no funciona en tu repositorio, contacta a {% data variables.contact.contact_support %}. diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md new file mode 100644 index 0000000000000..4c3641a0e5704 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -0,0 +1,116 @@ +--- +title: Habilitar el escaneo de código para un repositorio +shortTitle: Habilitar el escaneo de código +intro: 'Puedes habilitar {% data variables.product.prodname_code_scanning %} para el repositorio de tu proyecto.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'Si tienes permiso de escritura en un repositorio, puedes habilitar el {% data variables.product.prodname_code_scanning %} para éste.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Opciones para habilitar el {% data variables.product.prodname_code_scanning %} + +Tú decides cómo generar las alertas del {% data variables.product.prodname_code_scanning %} y qué herramientas utilizarás a nivel del repositorio. {% data variables.product.product_name %} te proporciona compatibilidad total e integrada para el análisis de {% data variables.product.prodname_codeql %} y también es compatible con el análisis de herramientas de terceros. Para obtener más información, consulta la sección "[Acerca de{% 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 %} + +### Habilitar el {% data variables.product.prodname_code_scanning %} utilizando acciones + +{% if currentVersion == "free-pro-team@latest" %}Si utilizas acciones para ejecutar el {% data variables.product.prodname_code_scanning %} se utilizarán minutos. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +3. A la derecha de "{% data variables.product.prodname_code_scanning_capc %}", da clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. ![Botón de "Configurar el {% data variables.product.prodname_code_scanning %}" a la derecha de "{% data variables.product.prodname_code_scanning_capc %}" en el resumen de seguridad](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Debajod e "Iniciar con el {% data variables.product.prodname_code_scanning %}", da clic en **Configurar este flujo de trabajo** en el {% data variables.product.prodname_codeql_workflow %} o en el flujo de trabajo de terceros. ![Botón de "Configurar este flujo de trabajo" debajo del encabezado de " Iniciar con el {% data variables.product.prodname_code_scanning %}"](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) +5. Para personalizar la forma en que el {% data variables.product.prodname_code_scanning %} escanea tu còdigo, edita el flujo de trabajo. + + Generalmente, puedes confirmar el {% data variables.product.prodname_codeql_workflow %} sin hacerle ningùn cambio. Sin embargo, muchos de los flujos de trabajo de terceros requieren de configuraciones adicionales, asì que lee los comentarios en el flujo de trabajo antes de confirmar. + + Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)". +6. Utiliza el menú desplegable de**Comenzar confirmación**, y teclea un mensaje de confirmación. ![Iniciar confirmación](/assets/images/help/repository/start-commit-commit-new-file.png) +7. Escoge si te gustaría confirmar directamente en la rama predeterminada, o crear una nueva rama y comenzar una solicitud de extracción. ![Escoger dónde confirmar](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. Da clic en **Confirmar archivo nuevo** o en **Proponer archivo nuevo**. + +En el {% data variables.product.prodname_codeql_workflow %} predeterminado, el {% data variables.product.prodname_code_scanning %} se configura para analizar tu código cada vez que ya sea subas un cambio a la rama predeterminada o a cualquier rama protegida, o que levantes una solicitud de cambios contra la rama predeterminada. Como resultado, el {% data variables.product.prodname_code_scanning %} comenzarà ahora. + +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + +### Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} + +Despuès de habilitar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones conforme se ejecutan. + +{% data reusables.repositories.actions-tab %} + + Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. The text of the entry is the title you gave your commit message. + + ![Lista de acciones que muestran el flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. + +1. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. + + ![Registro de salida del flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. + +1. Una vez que todos los jobs se completen, puedes ver los detalles de cualquier alerta del {% data variables.product.prodname_code_scanning %} que se hayan identificado. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". + +{% note %} + +**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}. + + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + +{% endnote %} + +### Entender las verificaciones de la solicitud de cambios + +Cada flujo de trabajo del {% data variables.product.prodname_code_scanning %} que habilites para ejecutarse en las soilcitudes de cambios siempre tiene por lo menos dos entradas que se listan en la secciòn de verificaciones de ellas. Solo hay una entrada para cada uno de los jobs de anàlisis en el flujo de trabajo y uno final para los resultados del anàlisis. + +Los nombres de las verificaciones del anàlisis del {% data variables.product.prodname_code_scanning %} se expresan en la forma: "NOMBRE DE LA HERRAMIENTA / NOMBRE DEL JOB (ACTIVADOR)." Por ejemplo, para {% data variables.product.prodname_codeql %}, el anàlisis de còdigo en C++ tiene la entrada "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)". Puedes dar clic en **Detalles** en una entrada de anàlisis de {% data variables.product.prodname_code_scanning %} para ver los datos de registro. Esto te permite depurar un problema si falla el job de anàlisis. Por ejemplo, para el anàlisis del {% data variables.product.prodname_code_scanning %} de los lenguajes compilados, esto puede suceder si la acciòn no puede compilar el còdigo. + + ![Verificaciones de solicitudes de cambios del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) + +Cuando se completan los jobs del {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} averigua si la solicitud de cambios agregò alguna alerta y agrega la entrada "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA" a la lista de verificaciones. Despuès de que se lleve a cabo el {% data variables.product.prodname_code_scanning %} por lo menos una vez, puedes dar clic en **Detalles** para ver los resultados del anàlisis. Si utilizaste una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} al repositorio, veràs inicialmente un mensaje de "Missing analysis" cuando des clic en la parte de **Detalles** de la verificaciòn "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA". + + ![Falta el análisis para el mensaje de confirmación](/assets/images/help/repository/code-scanning-missing-analysis.png) + +#### Razones para recibir un mensaje de "missing analysis" + +Despuès de que el {% data variables.product.prodname_code_scanning %} analiza el còdigo en una solicitud de cambios, necesita comparar el anàlisis de la rama de tema (la rama que utilizaste para crear la silicolicitud de cambios) con el anàlisis de la rama base (la rama en la cual quieres fusionar la solicitud de cambios). Esto permite al {% data variables.product.prodname_code_scanning %} calcular què alertas introdujo la solicitud de cambios recientemente, cuàles ya estaban presentes en la rama base y si es que cualquiera de las alertas existentes se arreglan con los cambios que lleva la solicitud. Inicialmente, si utilizas una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} a un repositorio, la rama base no se ha analizado, asì que no es posible calcular estos detalles. En este caso, cuando das clic en la verificaciòn de los resultados de la solicitud de cambios, veràs el mensaje "Missing analysis for base commit SHA-HASH". + +Existen otras situaciones en donde puede que no haya un anàlisis para la ùltima confirmaciòn hacia la rama base para una solicitud de cambios. Entre estas se incluyen cuando: + +* La solicitud de cambios se levantó contra una rama diferente a la predeterminada y ésta no se ha analizado. + + Para verificar si se ha escaneado una rama, ve a la pàgina de {% data variables.product.prodname_code_scanning_capc %}, da clic en el menù desplegable de **Rama** y selecciona la rama relevante. + + ![Elige una rama del menú desplegable de Rama](/assets/images/help/repository/code-scanning-branch-dropdown.png) + + La soluciòn a esta situaciòn es agregar el nombre de esta rama base a las especificaciones de `on:push` y `on:pull_request` en el flujo de trabajo del {% data variables.product.prodname_code_scanning %} en esta rama y luego hacer un cambio que actualice la solicitud de cambios abierta que quieres escanear. + +* La ùltima confirmaciòn en la rama base para la solicitud de cambios se està analizando actualmente y dicho anàlisis no està disponible aùn. + + Espera algunos minutos y luego sube un cambio a la solicitud de extracciòn para reactivar el {% data variables.product.prodname_code_scanning %}. + +* Ocurriò un error mientras se analizaba la ùltima confirmaciòn en la rama base y el anàlisis para esa confirmaciòn no està disponible. + + Fusiona un cambio trivial en la rama base para activar el {% data variables.product.prodname_code_scanning %} en esta ùltima confirmaciòn, luego sube un cambio a la solicitud de extracciòn para volver a activar el {% data variables.product.prodname_code_scanning %}. + +### Pasos siguientes + +Despuès de habilitar el {% data variables.product.prodname_code_scanning %} y permitir que sus acciones se completen, puedes: + +- Ver todas las alertas del {% data variables.product.prodname_code_scanning %} que se han generado para este repositorio. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". +- Ver cualquier alerta que se genere para una solicitud de cambios que se emita despuès de que habilitaste el {% data variables.product.prodname_code_scanning %}. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de extracción](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". +- Configurar las notificaciones para las ejecuciones que se hayan completado. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)". +- Investigar cualquier problema que ocurre con la configuración inicial del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Solucionar problemas del flujo de trabajo de {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)". +- Personaliza cómo el {% data variables.product.prodname_code_scanning %} escanea el código en tu repositorio. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)". diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md new file mode 100644 index 0000000000000..585412abaf7dd --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -0,0 +1,30 @@ +--- +title: Encontrar errores y vulnerabilidades de seguridad en tu código +shortTitle: Encontrar vulnerabilidades y errores de código +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Índice + +{% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} + {% link_in_list /about-code-scanning %} + {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} + {% link_in_list /enabling-code-scanning %} + {% link_in_list /managing-code-scanning-alerts-for-your-repository %} + {% link_in_list /configuring-code-scanning %} + {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} + {% link_in_list /troubleshooting-the-codeql-workflow %} + {% link_in_list /running-codeql-code-scanning-in-a-container %} +{% topic_link_in_list /managing-results-from-code-scanning %} + {% link_in_list /about-integration-with-code-scanning %} + {% link_in_list /uploading-a-sarif-file-to-github %} + {% link_in_list /sarif-support-for-code-scanning %} +{% topic_link_in_list /using-codeql-code-scanning-with-your-existing-ci-system %} + {% link_in_list /running-codeql-code-scanning-in-your-ci-system %} + {% link_in_list /configuring-codeql-code-scanning-in-your-ci-system %} + {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %} diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md new file mode 100644 index 0000000000000..9c8218e6795c8 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md @@ -0,0 +1,13 @@ +--- +title: Integrarse con el escaneo de código +shortTitle: Integración +intro: 'Puedes integrar las herramientas de análisis de código de terceros con el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_dotcom %} su cargas datos como archivos SARIF.' +mapTopic: verdadero +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md new file mode 100644 index 0000000000000..de32f24ca576f --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -0,0 +1,129 @@ +--- +title: Administrar las alertas del escaneo de código para tu repositorio +shortTitle: Administrar alertas +intro: 'Desde la vista de seguridad, puedes ver, arreglar, {% if currentVersion == "enterprise-server@2.22" %}o cerrar{% else %}descartar, o borrar{% endif %} las alertas para las vulnerabilidades potenciales o para los errores en el código de tus proyectos.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'Si tienes permiso de escritura en un repositorio, puedes administrar las alertas del {% data variables.product.prodname_code_scanning %} para éste.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +redirect_from: + - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning +--- + +{% data reusables.code-scanning.beta %} + +### Acerca de las alertas de {% data variables.product.prodname_code_scanning %} + +Puedes configurar el {% data variables.product.prodname_code_scanning %} para que verifique el código en un repositorio utilizando el análisis predeterminado de {% data variables.product.prodname_codeql %}, un análisis de terceros, o varios tipos de análisis. Cuando se complete el análisis, las alertas resultantes se mostrarán unas junto a otras en la vista de seguridad del repositorio. Los resultados de las herramientas de terceros o de las consultas personalizadas podrían no incluir todas las propiedades que ves para las alertas que se detectan con el análisis predeterminado del {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. + +Predeterminadamente, el {% data variables.product.prodname_code_scanning %} analiza tu código periódicamente en la rama predeterminada y durante las solicitudes de cambios. Para obtener información acerca de la administración de alertas en una solicitud de cambios, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". + +### Acerca de los detalles de las alertas + +Cada alerta resalta un problema en el código y el nombre de la herramienta que lo identificó. Puedes ver la línea de código que activó la alerta, así como las propiedades de la misma, tales como la severidad y la naturaleza de dicho problema. Las alertas también te dicen si el problema se introdujo por primera vez. Para las alertas que identificó el análisis de {% data variables.product.prodname_codeql %}, también verás información de cómo arreglar elproblema. + +![Ejemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) + +Si habilitas el {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_codeql %}, esto también detectará problemas de flujo de datos en tu código. El análisis de flujo de datos encuentra problemas de seguridad potenciales en el código, tales como: utilizar los datos de formas no seguras, pasar argumentos peligrosos a las funciones y tener fugas de información sensible. + +Cuando {% data variables.product.prodname_code_scanning %} reporta alertas de flujo de datos, {% data variables.product.prodname_dotcom %} te muestra como se mueven los datos a través del código. El {% data variables.product.prodname_code_scanning_capc %} te permite identificar las áreas de tu código que filtran información sensible y que podrían ser el punto de entrada para los ataques que hagan los usuarios malintencionados. + +### Visualizar las alertas de un repositorio + +Cualquiera con permisos de escritura en un repositorio puede ver las anotaciones del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de extracción](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". + +Necesitas permisos de escritura para ver un resumen de todas las alertas de un repositorio en la pestaña de **Seguridad**. Predeterminadamente, las alertas se muestran para la rama predeterminada. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-code-scanning-alerts %} +1. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar. ![Resumen de alertas](/assets/images/help/repository/code-scanning-click-alert.png) +1. Opcionalmente, si la alerta resalta un problema con el flujo de datos, da clic en **Mostrar rutas** para mostrar la ruta desde la fuente de datos hacia el consumidor de datos en donde se utiliza. ![El enlace de "Mostrar rutas" en una alerta](/assets/images/help/repository/code-scanning-show-paths.png) +1. Las alertas del análisis de {% data variables.product.prodname_codeql %} incluyen una descripción del problema. Da clic en **Mostrar más** para obtener orientación sobre cómo arreglar tu código. ![Detalles de una alerta](/assets/images/help/repository/code-scanning-alert-details.png) + +### Arreglar una alerta + +Cualquiera con permisos de escritura en un repositorio puede arreglar una alerta si confirma una corrección en el código. Si el repositorio tiene programado un {% data variables.product.prodname_code_scanning %} para ejecutarse en las solicitudes de cambios, es mejor levantar una solicitud de cambios con tu corrección. Esto activará el análisis del {% data variables.product.prodname_code_scanning %} en los cambios y probará que tu arreglo no introduciría ningún problema nuevo. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" y "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". + +Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrados" muestra las alertas solucionadas y aquellas que los usuarios {% if currentVersion == "enterprise-server@2.22" %}cerraron{% else %}descartaron{% endif %}. + +Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utilizar el menú desplegable de "Rama", en el resumen de las alertas, para verificar si una alerta se arregló en una rama en particular. + +![Filtrar alertas por rama](/assets/images/help/repository/code-scanning-branch-filter.png) + +{% if currentVersion == "enterprise-server@2.22" %} + +### Cerrar una alerta + +Cerrar una alerta es una forma de resolverla si no crees que necesita un arreglo. {% data reusables.code-scanning.close-alert-examples %} + +{% else %} + +### Descartar o borrar las alertas + +Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Borrar las alertas es úti en situaciones en donde habilitaste una herramienta de {% data variables.product.prodname_code_scanning %} y después decidiste eliminarla, o cuando habilitas el análisis de {% data variables.product.prodname_codeql %} con un conjunto más grande de consultas del que quieres seguir utilizando y luego eliminaste algunas de las consultas de esa herramienta. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**. + +El descartar una alerta es una forma de cerrar aquellas que no crees que necesiten arreglo. {% data reusables.code-scanning.close-alert-examples %} Puedes eliminar alertas desde las anotaciones del {% data variables.product.prodname_code_scanning %} en el código, o desde la lista de resumen dentro de la pestaña de **Seguridad**. + +Cuando descartas una alerta: + +- Se descarta en todas las ramas. +- La alerta se elimina de la cantidad de alertas actuales para tu proyecto. +- La alerta se mueve a la lista de "Cerrado" en el resumen de alertas, desde donde puedes volver a abrirla en caso de que lo necesites. +- La razón por la cual cerraste la alerta se registra. +- La siguiente vez que se ejecute el {% data variables.product.prodname_code_scanning %}, este código no volverá a generar una alerta. + +Cuando borras una alerta: + +- Se borra en todas las ramas. +- La alerta se elimina de la cantidad de alertas actuales para tu proyecto. +- _No_ seagrega a la lista de "Cerrado" en el resumen de las alertas. +- Si el código que generó la alerta se mantiene tal cual, y se ejecuta nuevamente la misma herramienta del {% data variables.product.prodname_code_scanning %} sin ningún cambio de configuración, la alerta se mostrará nuevamente en los resultados de tu análisis. + +Para descartar o borrar una alerta: + +{% endif %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-code-scanning-alerts %} +{% if currentVersion == "enterprise-server@2.22" %} +{% data reusables.code-scanning.click-alert-in-list %} +1. Selecciona el menú desplegable de **Cerrar** y da clic en una razón para cerrar la alerta. + ![Elegir una razón apra cerrar la alerta a través del menú desplegable de "Cerrar"](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) + +{% data reusables.code-scanning.false-positive-fix-codeql %} + +{% else %} + +1. Si tienes permisos administrativos en el repositorio y quieres borrar las alertas para esta herramienta del {% data variables.product.prodname_code_scanning %}, selecciona algunas o todas las casillas de verificación y da clic en **Borrar**. + + ![Borrar alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) + + Opcionalmente, puedes utilizar los filtros para mostrar un subconjunto de alertas y luego borrar simultáneamente todas las que empaten. Por ejemplo, si eliminaste una consulta desde el análisis de {% data variables.product.prodname_codeql %}, puedes utilizar el filtro de "Regla" para listar solo las alertas para esa consulta y luego seleccionar y borrar todas esas alertas. + + ![Filtrar alertas por regla](/assets/images/help/repository/code-scanning-filter-by-rule.png) + +1. Si quieres descartar una alerta, es importante explorarla primero para que puedas elegir la razón correcta para descartarla. Da clic en la alerta que quisieras explorar. + + ![Abrir una alerta desde la lista de sumario](/assets/images/help/repository/code-scanning-click-alert.png) + +1. Revisa la alerta y da clic en **Descartar** y elije una razón para cerrarla. ![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) + + {% data reusables.code-scanning.choose-alert-dismissal-reason %} + + {% data reusables.code-scanning.false-positive-fix-codeql %} + +#### Descartar varias alertas al mismo tiempo + +Si un proyecto tiene varias alertas que quieras descartar por la misma razón, puedes descartarlas por lote desde el resúmen de las alertas. Habitualmente quieres filtrar la lista y luego descartar todas las alertas coincidentes. Por ejemplo, puede que quieras descartar todas las alertas actuales del proyecto que se hayan etiquetado para una vulnerabilidad de Enumeración de Debilidades (CWE, por sus siglas en inglés) Común en particular. + +{% endif %} + +### Further reading + +- "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)" +- "[Habilitar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)" +- "[Acerca de la integración con {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md new file mode 100644 index 0000000000000..2ee8de9bd02ce --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -0,0 +1,69 @@ +--- +title: Ejecutarel escaneo de código de CodeQL en un contenedor +shortTitle: '{% data variables.product.prodname_code_scanning_capc %} en un contenedor' +intro: 'Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en un contenedor si garantizas que todos los procesos se ejecutan en el mismo contenedor.' +product: '{% data reusables.gated-features.code-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} + +### Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor + +Si estás configurando el {% data variables.product.prodname_code_scanning %} para un lenguaje compilado, y estás compilando el código en un ambiente contenido, el análisis podría fallar con el mensaje de error "No source code was seen during the build". Esto indica que {% data variables.product.prodname_codeql %} no fue capaz de monitorear tu código mientras se compilaba. + +Debes ejecutar {% data variables.product.prodname_codeql %} en el mismo contenedor en donde compilaste tu código. Esto aplica ya sea que estés utilizando el {% data variables.product.prodname_codeql_runner %} o {% data variables.product.prodname_actions %}. Si estás utilizando el {% data variables.product.prodname_codeql_runner %}, ejecútalo en el contenedor en donde se compila tu código. Para obtener más información acerca del {% data variables.product.prodname_codeql_runner %}, consulta la sección [Ejecutar el {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)". Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)". + +### Dependencias + +Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). Si te encuentras con algún problema en las dependencias, revisa la lista de software que habitualmente se incluye en los ambientes virtuales de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta los archivos `readme` específicos de la versión en estas ubicaciones: + +* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* Windows: https://github.com/actions/virtual-environments/tree/main/images/win + +### Ejemplo de flujo de trabajo + +Este flujo de trabajo de muestra utiliza {% data variables.product.prodname_actions %} para ejecutar un análisis de {% data variables.product.prodname_codeql %} en un ambiente contenido. El valor de `container.image` identifica el contenedor que se debe utilizar. En este ejemplo, se le llama a la imagen `codeql-container`, con una etiqueta de `f0f91db`. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)". + +``` yaml +name: "{% data variables.product.prodname_codeql %}" + +on: + push: + branches: [main] + pull_request: + branches: [main] + schedule: + - cron: '0 0 * * 0' + +jobs: + analyze: + name: Analyze + runs-on: ubuntu-latest + + strategy: + fail-fast: false + matrix: + language: [java] + + # Specify the container in which actions will run + container: + image: codeql-container:f0f91db + + steps: + - name: Checkout repository + uses: actions/checkout@v2 + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + with: + languages: {% raw %}${{ matrix.language }}{% endraw %} + - name: Build + run: | + ./configure + make + - name: Perform {% data variables.product.prodname_codeql %} Analysis + uses: github/codeql-action/analyze@v1 +``` diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md new file mode 100644 index 0000000000000..f93a4d2233a12 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -0,0 +1,173 @@ +--- +title: Ejecurar el escaneo de código de CodeQL en tu sistema de IC +shortTitle: Ejecución en tu IC +intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_runner %} para llevar a cabo el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en un sistema de integración contínua de terceros.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + + + +{% data reusables.code-scanning.beta-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} + +### Utilizar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} con tu sistema de IC + +Si utilizas un sistema de integración contínua o de desliegue/entrega contínua (IC/EC) diferente al de {% data variables.product.prodname_actions %}, puedes utilizar tu sistema actual para ejecutar el análisis de {% data variables.product.prodname_codeql %} de {% data variables.product.prodname_dotcom %} y cargar los resultados a {% data variables.product.prodname_dotcom %}. Para hacerlo, utiliza el {% data variables.product.prodname_codeql_runner %}. + +### Acerca de {% data variables.product.prodname_codeql_runner %} + +{% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". + +Puedes utilizar el {% data variables.product.prodname_codeql_runner %} para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración continua (IC) de terceros. Como alternativa, puedes utilizar {% data variables.product.prodname_actions %} para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)". + +El {% data variables.product.prodname_codeql_runner %} es una herramienta de línea de comandos que ejecuta un análisis de {% data variables.product.prodname_codeql %} en un control de un repositorio de {% data variables.product.prodname_dotcom %}. Agregas el ejecutor a tu sistema de terceros y luego lo llamas para que analice el código y cargue los resultados a {% data variables.product.product_location %}. Estos resultados se muestran como alertas del {% data variables.product.prodname_code_scanning %} en el repositorio. + +{% note %} + +**Notas:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. Se puede utilizar gratuitamente en los repositorios que mantiene {% data variables.product.prodname_dotcom_the_website %}, y está disponible para utilizarse en aquellos que pertenecen a los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} + +### Descargar el {% data variables.product.prodname_codeql_runner %} + +Puedes descargar el {% data variables.product.prodname_codeql_runner %} desde https://github.com/github/codeql-action/releases. En algunos sistemas operativos, puede que necesites cambiar permisos para el archivo de descarga antes de que lo puedas ejecutar. + +En Linux: + +```shell +chmod +x codeql-runner-linux +``` + +En macOS: + +```shell +chmod +x codeql-runner-macos +sudo xattr -d com.apple.quarantine codeql-runner-macos +``` + +En Windows, el archivo `codeql-runner-win.exe` habitualmente no necesita que se hagan cambios a los permisos. + +### Agregar el {% data variables.product.prodname_codeql_runner %} a tu sistema de IC + +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: + +```shell +wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux +chmod +x codeql-runner-linux +``` + +Además, cada servidor de IC necesitará también: + +- Un token de acceso personal o de {% data variables.product.prodname_github_app %} para que utilice el {% data variables.product.prodname_codeql_runner %}. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. Para obtener más información, consulta las secciones "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" y "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +- Acceso al paquete de {% data variables.product.prodname_codeql %} asociado con este lanzamiento del {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". + +Las opciones para proporcionar acceso al paquete de {% data variables.product.prodname_codeql %} son: + +1. Dar acceso a {% data variables.product.prodname_dotcom_the_website %} a los servidores de IC para que el {% data variables.product.prodname_codeql_runner %} pueda descargar el paquete automáticamente. +1. Descargar/extraer manualmente el paquete, almacenarlo con otros recursos centrales, y utilizar el marcador de `--codeql-path` para especificar la ubicación del paquete en las llamadas para inicializar el +{% data variables.product.prodname_codeql_runner %}. +{% if enterpriseServerVersions contains currentVersion %} +1. Puedes replicar el repositorio de `github/codeql-action` en {% data variables.product.product_location %}. A menos de que especifiques el marcador de `--codeql-path` , el ejecutor verificará automáticamente que el paquete esté en esta ubicación y en {% data variables.product.prodname_dotcom_the_website %}.{% endif %} + +### Llamar al {% data variables.product.prodname_codeql_runner %} + +Debes llamar al {% data variables.product.prodname_codeql_runner %} desde la ubicación de verificación del repositorio que quieres analizar. Los dos comandos principales son: + +1. `init` que se requiere para inicializar el ejecutor y para crear una base de datos de {% data variables.product.prodname_codeql %} para que se analice cada lenguaje. Estas bases de datos se llenan y analizan mediante comandos subsecuentes. +1. `analyze` que se requiere para llenar las bases de datos de {% data variables.product.prodname_codeql %}, analizarlas y cargar los resultados a {% data variables.product.product_location %}. + +Para ambos comandos, debes especificar la URL de {% data variables.product.product_location %}, el repositorio *OWNER/NAME*, y el token de acceso personal o de GitHub Apps que se utilizará para autenticación. También tendrás que especificar la ubicación del paquete de CodeQL a menos de que el servidor de IC tenga acceso para descargarlo directamente desde el repositorio `github/codeql-action` en {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} o el que está replicado en {% data variables.product.product_location %}{% endif %}. + +Puedes configurar la ubicación en la que {% data variables.product.prodname_codeql_runner %} almacenará el paquete de CodeQL para un análisis futuro un un servidor utilizando el marcador `--tools-dir` , así como en dónde almacena archivos temporales utilizando el marcador `--temp-dir`. + +Para ver la referencia de línea de comandos para el ejecutor, utiliza el marcador `-h`. Por ejemplo, para listar todos los comandos, ejecuta: `codeql-runner-OS -h`, o para listar todos los marcadores disponibles para el comando `init`, ejecuta: `codeql-runner-OS init -h` (en donde el `OS` variará de acuerdo con el ejecutable que estés utilizando). Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)". + +#### Ejemplo básico + +Este ejemplo ejecuta un análisis de {% data variables.product.prodname_codeql %} en un servidor de IC con Linux para el repositorio de `octo-org/example-repo` en `{% data variables.command_line.git_url_example %}`. El proceso es muy simple, ya que el repositorio contiene únicamente los lenguajes que puede analizar {% data variables.product.prodname_codeql %} directamente, sin que se tenga que compilar (es decir, Go, JavaScript, Python, y TypeScript). + +1. Verifica el repositorio a analizar. +1. Posiciónate en el directorio donde se seleccionó el repositorio. +1. Inicializa el {% data variables.product.prodname_codeql_runner %} y crea bases de datos de {% data variables.product.prodname_codeql %} para los lenguajes detectados. + + ```shell + $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo + --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN + > Cleaning temp directory /srv/checkout/example-repo/codeql-runner + > ... + > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript. + ``` + +1. Llena las bases de datos de {% data variables.product.prodname_codeql_runner %}, analízalas, y carga los resultados a{% data variables.product.product_name %}. + + ```shell + $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo + --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN + --commit 5b6a3078b31dc346e5ce7b86837d6abbe7a18bbd --ref refs/heads/main + > Finalizing database creation + > ... + > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms + > Successfully uploaded results + ``` + +El servidor tiene acceso para descargar el paquete de {% data variables.product.prodname_codeql %} directamente del repositorio de `github/codeql-action` en {% data variables.product.prodname_dotcom_the_website %}{% if enterpriseServerVersions contains currentVersion %} o en el que está replicado en {% data variables.product.product_location %}{% endif %}, así que no se necesita utilizar el marcador `--codeql-path`. Cuando se complete el análisis, el {% data variables.product.prodname_codeql_runner %} cargará los resultados a la vista del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". + +#### Ejemplo de lenguaje compilado + +Este ejemplo es similar al anterior, sin embargo, esta vez el repositorio tiene código en C/C++, C#, o Java. Para crear una base de datos de {% data variables.product.prodname_codeql %} para estos lenguajes, el CLI necesita monitorear la compilación. Al final del proceso de inicialización, el ejecutor reportará el comando que necesitas configurar en el ambiente antes de compilar el código. Necesitas ejecutar este comando antes de llamar al proceso normal de compilación de IC y luego ejecutar el comando `analyze`. + +1. Verifica el repositorio a analizar. +1. Posiciónate en el directorio donde se seleccionó el repositorio. +1. Inicializa el {% data variables.product.prodname_codeql_runner %} y crea bases de datos de {% data variables.product.prodname_codeql %} para los lenguajes detectados. + + ```shell + $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 + --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN + > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner + > ... + > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json" + and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". + Please export these variables to future processes so that CodeQL can monitor the build, for example by running " + . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". + ``` + +1. Ejecuta el script que generó la acción `init` para configurar el ambiente para monitorear la compilación. + + ```shell + $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh + ``` + +1. Compila el código. +1. Llena las bases de datos de {% data variables.product.prodname_codeql %}, analízalas, y carga los resultados a GitHub. + + ```shell + $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo-2 + --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN + --commit ae7b655ef30b50fb726ae7b3daa79571a39d194d --ref refs/heads/main + > Finalizing database creation + > ... + > POST /repos/octo-org/example-repo-2/code-scanning/sarifs - 202 in 573ms + > Successfully uploaded results + ``` + +{% note %} + +**Nota:** Si utilizas una compilación que usa contenedores, necesitarás ejecutar el {% data variables.product.prodname_codeql_runner %} en el contenedor donde toma lugar tu tarea de compilaión. + +{% endnote %} + +### Further reading + +- "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)" +- "[Solucionar problemas del {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md new file mode 100644 index 0000000000000..755e76c3639ab --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -0,0 +1,425 @@ +--- +title: Soporte de SARIF para escaneo de código +shortTitle: Soporte de SARIF +intro: 'Para mostrar los resultados de una herramienta de análisis estático de terceros en tu repositorio en {% data variables.product.prodname_dotcom %}, necesitas que éstos se almacenen en un archivo SARIF que sea compatible con un subconjunto del modelo de JSON para SARIF 2.1.0 para el {% data variables.product.prodname_code_scanning %}. Si utilizas el motor de análisis estático predeterminado de {% data variables.product.prodname_codeql %}, tus resultados se mostrarán automáticamente en tu repositorio de {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} + +### Acerca del soporte de SARIF + +SARIF (Formato de Intercambio de Resultados de Análisis Estático, por sus siglas en inglés) es un [Estándar de OASIS](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define un formato de archivo de salida. El estándar SARIF se utiliza para optimizar la manera en el que las herramientas de análisis estático comparten sus resultados. {% data variables.product.prodname_code_scanning_capc %} es compatible con un subconjunto del modelo SARIF 2.1.0 JSON. + +Para cargar un archivo SARIF desde un motor de análisis estático de código desde un tercero, necesitaras asegurarte de que los archivos cargados utilicen la versión SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analizará el archivo SARIF y mostrará las alertas utilizando los resultados en tu repositorio como parte de la experiencia del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". Para obtener más información acerca del modelo SARIF 2.1.0, consulta [`sari-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json). + +Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" o "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". + +{% data variables.product.prodname_dotcom %} utiliza propiedades en el archivo SARIF para mostrar alertas. Por ejemplo, la `shortDescription` y `fullDescription` aparecen hasta arriba de una alerta de {% data variables.product.prodname_code_scanning %}. La `location` permite a {% data variables.product.prodname_dotcom %} mostrar anotaciones en tu archivo de código. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". + +Si SARIF es nuevo para ti y quieres aprender más, consulta el repositorio [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) de Microsoft. + +### Prevenir alertas duplicadas utilizando huellas dactilares + +Cada vez que el flujo de trabajo de {{ site.data.variables.product.prodname_actions }} ejecuta un nuevo escaneo de código, los resultados de cada ejecución se procesan y se agregan alertas al repositorio. Para prevenir las alertas duplicadas para el mismo problema, {% data variables.product.prodname_code_scanning %} utiliza huellas dactilares para empatara los resultados a través de diversas ejecuciones para que solo aparezcan una vez en la última ejecución para la rama seleccionada. Esto hace posible empatar las alertas con la línea de código correcta cuando se editan los archivos. + +{% data variables.product.prodname_dotcom %} utiliza la propiedad `partialFingerprints` en el estándar OASIS para detectar cuando dos resultados son lógicamente idénticos. Para obtener más información, consulta la sección "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" en la documentación de OASIS. + +Los archivos SARIF que crea el {% data variables.product.prodname_codeql_workflow %} o los que utilizan el {% data variables.product.prodname_codeql_runner %} incluyen datos de huellas digitales. Si cargas un archivo SARIF utilizando la acción `upload-sarif` y no se encuentran estos datos, {% data variables.product.prodname_dotcom %} intentará poblar el campo `partialFingerprints` desde los archivos de origen. Para obtener más información acerca de cargar los resultados, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". + +Si cargaste un archivo SARIF sin datos de huella digital utilizando la terminal de la API de `/code-scanning/sarifs`, se procesarán y se mostrarán las alertas del {% data variables.product.prodname_code_scanning %}, pero los usuarios podrían ver alertas duplicadas. Para evitar el ver alertas duplicadas, debes calcular los datos de la huella digital y llenar la propiedad de `partialFingerprints` antes de que cargues el archivo SARIF. Puede que el script que utiliza la acción `upload-sarif` te sea útil como punto de inicio: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Para obtener más información acerca de la API, consulta la sección "[Cargar un archivo SARIF](/rest/reference/code-scanning#upload-a-sarif-file)". + +### Validar tu archivo SARIF + + + +Puedes verificar si un archivo SARIF es compatible con el {% data variables.product.prodname_code_scanning %} si lo pruebas contra las reglas de ingestión de {% data variables.product.prodname_dotcom %}. Para obtener más información, visita el [Validador de archivos SARIF de Microsoft](https://sarifweb.azurewebsites.net/). + +### Propiedades compatibles de archivo de salida SARIF + +Si utilizas un motor de análisis de código diferente a {% data variables.product.prodname_codeql %}, puedes revisar las propiedades SARIF compatibles para optimizar cómo aparecerán los resultados de tu análisis en {% data variables.product.prodname_dotcom %}. + +Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% data variables.product.prodname_code_scanning %} utilizará únicamente las siguientes propiedades compatibles. + +#### Objeto `sarifLog` + +| Nombre | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `$schema` | **Requerido.** la URI del modelo SARIF JSON para la versión 2.1.0. Por ejemplo, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | +| `version` | **Requerido.**{% data variables.product.prodname_code_scanning_capc %} solo es compatible con la versión `2.1.0` de SARIF. | +| `runs[]` | **Requerido.** Un archivo SARIF contiene un arreglo de una o más ejecuciones. Cada ejecución representa una sola ejecución de una herramienta de análisis. Para obtener más información acerca de una `run`, consulta el [ objeto `run`](#run-object). | + +#### Objeto `run` + +{% data variables.product.prodname_code_scanning_capc %} utiliza el objeto `run` para filtrar los resultados por herramienta y proporcionar información acerca del origen de un resultado. El objeto `run` contienen el objeto componente de herramienta `tool.driver`, el cual contiene información acerca de la herramienta que generó el resultado. Cada `run` puede tener únicamente resultados para la herramienta de análisis. + +| Nombre | Descripción | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `tool.driver.name` | **Requerido.** El nombre de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre en {% data variables.product.prodname_dotcom %} para permitirte filtrar los resultados por herramienta. | +| `tool.driver.version` | **Opcional.** La versión de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. | +| `tool.driver.semanticVersion` | **Opcional.** La versión de la herramienta de análisis, especificada por el formato de Semantic Versioning 2.0. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. Para obtener más información, consulta la sección "[Semantic Versioning 2.0.0](https://semver.org/)" en la documentación de Semantic Versioning. | +| `tool.driver.rules[]` | **Requerido.** Un arreglo de objetos `reportingDescriptor` que representen reglas. La herramienta de análisis utiliza reglas para encontrar problemas en el código que se analiza. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | +| `results[]` | **Requerido.** Los resultados de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra los resultados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta el [objeto `result`](#result-object). | + +#### Objeto `reportingDescriptor` + +| Nombre | Descripción | +| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | **Requerido.** Un identificador único para la regla. El `id` se referencia de otras partes del archivo SARIF y {% data variables.product.prodname_code_scanning %} puede utilizarlo para mostrar las URL en {% data variables.product.prodname_dotcom %}. | +| `name (nombre)` | **Opcional.** El nombre de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre para permitir que se filtren los resultados por regla en {% data variables.product.prodname_dotcom %}. | +| `shortDescription.text` | **Requerido** Una descripción breve de la acción. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción corta en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. | +| `fullDescription.text` | **Requerido** Una descripción de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción completa en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. La cantidad máxma de caracteres se limita a 1000. | +| `defaultConfiguration.level` | **Opcional.** Nivel de severidad predeterminado de la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza niveles de severidad para ayudarte a entender qué tan crítico es el resultado de una regla. El atributo `level` en el objeto `result` anular este valor. Para obtener más información, consulta el [objeto `result`](#result-object). Predeterminado: `warning`. | +| `help.text` | **Requerido.** Documentación para la regla utilizando el formato de texto. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. | +| `help.markdown` | **Recomendado.** Documentación para la regla utilizando el formato Markdown. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. Cuando `help.markdown` está disponible, se muestra en vez de `help.text`. | +| `properties.tags[]` | **Opcional.** Un arreglo de secuencias. {% data variables.product.prodname_code_scanning_capc %} utiliza `tags` para permitirte filtrar los resultados en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes filtrar todos los resultados que tengan la etiqueta `security`. | +| `properties.precision` | **Recomendado.** una secuencia que indica qué tan frecuentemente son verdaderos los resultados que indica esta regla. Por ejemplo, si una regla tiene una tasa alta de falsos positivos, la precisión debería ser `low`. {% data variables.product.prodname_code_scanning_capc %} ordena los resultados de acuerdo con su precisión en {% data variables.product.prodname_dotcom %} para que aquellos con el `level` y la `precision` más altos se muestren primero. Puede ser uno de entre: `very-high`, `high`, `medium`, o `low`. | + +#### `result` object + +| Nombre | Descripción | +| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Opcional.** El identificador único de la regla (`reportingDescriptor.id`). Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} utiliza el identificador de reglas para filtrar los resultados por regla en {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Opcional.** El índice de la regla asociada (`reportingDescriptor` object) en el arreglo de `rules` del componente de la herramienta. Para obtener más información, consulta el [objeto `run`](#run-object). | +| `rule` | **Opcional.** Una referencia que se utiliza para ubicar la regla (descriptor de reporte) para este resultado. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | +| `level` | **Opcional.** La severidad del resultado. Este nivel invalida la severidad predeterminada que se define en la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza el nivel para filtrar los resultados en {% data variables.product.prodname_dotcom %} por severidad. | +| `message.text` | **Requerido.** Un mensaje que describe el resultado. {% data variables.product.prodname_code_scanning_capc %} muestra el texto del mensaje como el título del resultado. Se mostrará únicamente la primera oración del mensaje cuando el espacio visible esté limitado. | +| `locations[]` | **Requerido.** El conjunto de ubicaciones donde se detectó el resultado. Sólo se deberá incluir una ubicación a menos de que el problema solo pueda corregirse realizando un cambio en cada ubicación especificada. **Nota:** Se requiere por lo menos una ubicación para que {% data variables.product.prodname_code_scanning %} muestre el resultado. {% data variables.product.prodname_code_scanning_capc %} utilizará esta propiedad para decidir qué archivo anotar con el resultado. Únicamente si se utiliza el primer valor de este arreglo. Se ignorará al resto de los otros valores. | +| `partialFingerprints` | **Requerido.** Un conjunto de secuencias utilizadas para rastrear la identidad única del resultado. {% data variables.product.prodname_code_scanning_capc %} utiliza `partialFingerprints` para identificar con exactitud qué resultados son los mismos a través de las confirmaciones y ramas. {% data variables.product.prodname_code_scanning_capc %} intentará utilizar `partialFingerprints` si es que existe. Si estás cargando un archivo SARIF de terceros con el `upload-action`, la acción creará un `partialFingerprints` para ti cuando no se incluya en el archivo SARIF. Para obtener más información, consulta "[Prevenir alertas duplicadas utilizando huellas dactilares](#preventing-duplicate-alerts-using-fingerprints)". **Nota:** {% data variables.product.prodname_code_scanning_capc %} utilizará únicamente el `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Un arreglo de objetos de `location` para un objeto de `threadFlow`, el cual describe el progreso de un programa a través de un hilo de ejecución. Un objeto de `codeFlow` describe un patrón de ejecución de código que se utiliza para detectar un resultado. Si se proporcionan flujos de código, {% data variables.product.prodname_code_scanning %} los expandirá en {% data variables.product.prodname_dotcom %} para el resultado relevante. Para obtener más información, consulta el [objeto `location`](#location-object). | +| `relatedLocations[]` | Un conjunto de ubicaciones relevantes para el resultado. {% data variables.product.prodname_code_scanning_capc %} vinculará las ubicaciones cuando se incorporen en el mensaje de resultado. Para obtener más información, consulta el [objeto `location`](#location-object). | +| `suppressions[].state` | **Opcional.** Cuando el `state` se configura como `accepted`, {% data variables.product.prodname_code_scanning %} actualizará el estado del resultado a `Closed` en {% data variables.product.prodname_dotcom %}. | + +#### Objeto `location` + +Una ubicación dentro de un artefacto de programación, tal como un archivo en el repositorio o un archivo que se generó durante una compilación. + +| Nombre | Descripción | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| `location.id` | **Opcional.** Un identificador único que distingue esta ubicación del resto de las ubicaciones dentro de un objeto de un único resultado. | +| `location.physicalLocation` | **requerido.** Identifica el artefacto y la región. Para obtener más información, consulta la [`physicalLocation`](#physicallocation-object). | +| `location.message.text` | **Opcional.** Un mensaje relevante para la ubicación. | + +#### Objeto `physicalLocation` + +| Nombre | Descripción | +| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `artifactLocation.uri` | **Requerido.** Un URI que indica la ubicación de un artefacto, a menudo un archivo ya sea en el repositorio o generado durante una compilación. Si el URI es relativo, deberá ser relativo a la raíz del repositorio de {% data variables.product.prodname_dotcom %} que se está analizando. Por ejemplo, main.js o src/script.js son relativos a la raíz del repositorio. Si la URI es absoluta, {% data variables.product.prodname_code_scanning %} puede utilizarla para revisar el artefacto y empatar archivos en el repositorio. Por ejemplo, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | +| `region.startLine` | **Requerido.** El número del línea para el primer caracter en la región. | +| `region.startColumn` | **Requerido.** El número de columna del primer caracter en la región. | +| `region.endLine` | **Requerido.** El número de línea de el último caracter en la región. | +| `region.endColumn` | **Requerido.** El número de columna del caracter que sigue al final de la región. | + +### Ejemplos de archivo de salida SARIF + +Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo. + +#### Ejemplo con las propiedades mínimas requeridas + +Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedades mínimas requeridas para que los resultados de {% data variables.product.prodname_code_scanning %} funcionen como se espera. Si eliminas cualquier propiedad u omites valores, estos datos no se mostrarán correctamente ni se sincronizarán en {% data variables.product.prodname_dotcom %}. + + +```json +{ + "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", + "version": "2.1.0", + "runs": [ + { + "tool": { + "driver": { + "name": "Tool Name", + "rules": [ + { + "id": "R01" + } + ] + } + }, + "results": [ + { + "ruleId": "R01", + "message": { + "text": "Result text. This result does not have a rule associated." + }, + "locations": [ + { + "physicalLocation": { + "artifactLocation": { + "uri": "fileURI" + }, + "region": { + "startLine": 2, + "startColumn": 7, + "endColumn": 10 + } + } + } + ], + "partialFingerprints": { + "primaryLocationLineHash": "39fa2ee980eb94b0:1" + } + } + ] + } + ] +} +``` + +#### Ejemplo que muestra todas las propiedades compatibles con SARIF + +Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}. + +```json +{ + "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", + "version": "2.1.0", + "runs": [ + { + "tool": { + "driver": { + "name": "Tool Name", + "semanticVersion": "2.0.0", + "rules": [ + { + "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad", + "name": "js/unused-local-variable", + "shortDescription": { + "text": "Unused variable, import, function or class" + }, + "fullDescription": { + "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully." + }, + "defaultConfiguration": { + "level": "note" + }, + "properties": { + "tags": [ + "maintainability" + ], + "precision": "very-high" + } + }, + { + "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", + "name": "js/inconsistent-use-of-new", + "shortDescription": { + "text": "Inconsistent use of 'new'" + }, + "fullDescription": { + "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'." + }, + "properties": { + "tags": [ + "reliability", + "correctness", + "language-features" + ], + "precision": "very-high" + } + }, + { + "id": "R01" + } + ] + } + }, + "results": [ + { + "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad", + "ruleIndex": 0, + "message": { + "text": "Unused variable foo." + }, + "locations": [ + { + "physicalLocation": { + "artifactLocation": { + "uri": "main.js", + "uriBaseId": "%SRCROOT%" + }, + "region": { + "startLine": 2, + "startColumn": 7, + "endColumn": 10 + } + } + } + ], + "partialFingerprints": { + "primaryLocationLineHash": "39fa2ee980eb94b0:1", + "primaryLocationStartColumnFingerprint": "4" + } + }, + { + "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0", + "ruleIndex": 1, + "message": { + "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))." + }, + "locations": [ + { + "physicalLocation": { + "artifactLocation": { + "uri": "src/promises.js", + "uriBaseId": "%SRCROOT%" + }, + "region": { + "startLine": 2 + } + } + } + ], + "partialFingerprints": { + "primaryLocationLineHash": "5061c3315a741b7d:1", + "primaryLocationStartColumnFingerprint": "7" + }, + "relatedLocations": [ + { + "id": 1, + "physicalLocation": { + "artifactLocation": { + "uri": "src/ParseObject.js", + "uriBaseId": "%SRCROOT%" + }, + "region": { + "startLine": 2281, + "startColumn": 33, + "endColumn": 55 + } + }, + "message": { + "text": "here" + } + }, + { + "id": 2, + "physicalLocation": { + "artifactLocation": { + "uri": "src/LiveQueryClient.js", + "uriBaseId": "%SRCROOT%" + }, + "region": { + "startLine": 166 + } + }, + "message": { + "text": "here" + } + } + ] + }, + { + "ruleId": "R01", + "message": { + "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies." + }, + "level": "error", + "locations": [ + { + "physicalLocation": { + "artifactLocation": { + "uri": "full.sarif", + "uriBaseId": "%SRCROOT%" + }, + "region": { + "startLine": 54, + "startColumn": 10, + "endLine": 55, + "endColumn": 25 + } + } + } + ], + "relatedLocations": [ + { + "id": 1, + "physicalLocation": { + "artifactLocation": { + "uri": "full.sarif" + }, + "region": { + "startLine": 81, + "startColumn": 10, + "endColumn": 18 + } + }, + "message": { + "text": "here" + } + }, + { + "id": 2, + "physicalLocation": { + "artifactLocation": { + "uri": "full.sarif" + }, + "region": { + "startLine": 82, + "startColumn": 10, + "endColumn": 21 + } + }, + "message": { + "text": "here" + } + } + ], + "codeFlows": [ + { + "threadFlows": [ + { + "locations": [ + { + "location": { + "physicalLocation": { + "region": { + "startLine": 11, + "endLine": 29, + "startColumn": 10, + "endColumn": 18 + }, + "artifactLocation": { + "uriBaseId": "%SRCROOT%", + "uri": "full.sarif" + } + }, + "message": { + "text": "Rule has index 0" + } + } + }, + { + "location": { + "physicalLocation": { + "region": { + "endColumn": 47, + "startColumn": 12, + "startLine": 12 + }, + "artifactLocation": { + "uriBaseId": "%SRCROOT%", + "uri": "full.sarif" + } + } + } + } + ] + } + ] + } + ], + "partialFingerprints": { + "primaryLocationLineHash": "ABC:2" + } + } + ], + "columnKind": "utf16CodeUnits" + } + ] +} +``` diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md new file mode 100644 index 0000000000000..6bafe08098ba4 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -0,0 +1,66 @@ +--- +title: Clasificar las alertas del escaneo de código en las solicitudes de cambios +shortTitle: Clasificar las alertas en las solicitudes de cambios +intro: 'Cuando el {% data variables.product.prodname_code_scanning %} identifica un problema en una solicitud de extracción, puedes revisar el código que se ha resaltado y resolver la alerta.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'Si tienes permiso de lectura en un repositorio, puedes ver las anotaciones en las solicitudes de cambios. Con los permisos de escritura, puedes ver la información detallada y resolver las alertas del {% data variables.product.prodname_code_scanning %} para el repositorio en cuestión.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} + +### Acerca de los resultados del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios + +En los repositorios donde se configura el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambios, éste verificará el código en dicha solicitud. Predeterminadamente, esto se limita a solicitudes de cambios que apuntan a la rama predeterminada, pero puedes cambiar esta configuración dentro de {% data variables.product.prodname_actions %} o en un sistema de IC/EC de terceros. Si el fusionar los cambios puede introducir alertas nuevas de {% data variables.product.prodname_code_scanning %} a la rama destino, éstas se reportarán como resultados de verificación en la solicitud de cambios. Las alertas también se muestran como anotaciones en la pestaña de **Archivos que cambiaron** de la solicitud de cambios. Si tienes permisos de escritura para el repositorio, puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} existente en la pestaña de **Seguridad**. Para obtener más información sobre las alertas de los repositorios, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". + +Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que se habilitó para el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o {% if currentVersion == "enterprise-server@2.22" %}cerrar{% else %}descartar{% endif %} todas las alertas de error antes de que se pueda fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". + +![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png) + +### Acerca del {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio + +Hay muchas opciones para configurar el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio, así que la configuración de cada repositorio variará y algunas tendrán más de una verificación. La verificación que contiene los resultados del {% data variables.product.prodname_code_scanning %} se llama: **Resultados del escaneo de código**. + +Si el repositorio utiliza el {% data variables.product.prodname_codeql_workflow %}, se ejecutará una verificación de **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** para cada lenguaje antes de que la verificación de resultados se ejecute. La verificación del análisis podría fallar si existieran problemas de configuración o si la solicitud de cambios impide la compilación para un lenguaje que el análisis necesita compilar (por ejemplo, C/C++, C# o Java). Así como con otras verificaciones de solicitudes de cambios, puedes ver todos los detalles de la falla de la verificación en la pestaña de **Verificaciones**. Para obtener más información acerca de la configuración y la soución de problemas, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" o "[Solucionar problemas del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)". + +### Clasificar una alerta en tu solicitud de cambios + +Cuando ves la pestaña de **Archivos que cambiaron** en una solicitud de cambios, puedes ver anotaciones de cualquier línea de código que haya activado la alerta. + +![Anotación de alerta dentro de un diff de una solicitud de cambios](/assets/images/help/repository/code-scanning-pr-annotation.png) + +Si tienes permisos de escritura para el repositorio, algunas anotaciones contendrán enlaces con un contexto adicional de la alerta. En el ejemplo anterior del análisis de {% data variables.product.prodname_codeql %}, puedes dar clic en **valor proporcionado por el usuario** para ver en dónde ingresarían los datos no confiables dentro del flujo de datos (a esto se le conoce como la fuente). En este caso, también puedes ver la ruta completa desde la fuente hasta el código que utiliza los datos (el consumidor de datos) dando clic en **Mostrar rutas**. Esto facilita la revisión, ya sea que los datos no sean confiables o que el análisis falle en reconocer un paso de sanitización de datos entre la fuente y el consumidor de datos. Para obtener información sobre cómo analizar el flujo de datos utilizando {% data variables.product.prodname_codeql %}, consulta la sección "[Acerca del análisis de flujo de datos](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)". + +Para ver más información sobre una alerta, los usuarios con permisos de escritura pueden dar clic en el enlace de **Mostrar más detalles** que se muestra en la anotación. Esto te permite ver todo el contexto y los metadatos que proporciona la herramienta en una vista de alertas. En el siguiente ejemplo, puedes ver que las etiquetas muestran la severidad, tipo y las enumeraciones de los puntos débiles comunes (los CWE) del problema. La vista también muestra qué confirmación introdujo el problema. + +En la vista detallada de una alerta, algunas herramientas del {% data variables.product.prodname_code_scanning %}, como el análisis de {% data variables.product.prodname_codeql %}, también incluyen una descripción del problema y un enlace de **Mostrar más** para orientarte sobre cómo arreglar tu código. + +![Descripción de alerta y enlace para mostrar más información](/assets/images/help/repository/code-scanning-pr-alert.png) + +### {% if currentVersion == "enterprise-server@2.22" %}Resolver{% else %}Arreglar{% endif %} una alerta en tu solicitud de cambios + +Cualquiera con acceso de subida a una solicitud de cambios puede arreglar una alerta del {% data variables.product.prodname_code_scanning %}, la cual se identifique en dicha solicitud. Si confirmas cambios en la solicitud de extracción, esto activará una ejecución nueva de las verificaciones de dicha solicitud. Si tus cambios arreglan el problema, la alerta se cierra y la anotación se elimina. + +{% if currentVersion == "enterprise-server@2.22" %} + +Si no crees que alguna alerta deba arreglarse, los usuarios con permisos de escritura pueden cerrarla manualmente. {% data reusables.code-scanning.close-alert-examples %} El botón de **Cerrar** se encuentra disponible en las anotaciones y en la vista de alertas si tienes permisos de escritura en el repositorio. + +{% data reusables.code-scanning.false-positive-fix-codeql %} + +{% else %} + +### Descartar una alerta en tu solicitud de cambios + +Una forma alterna de cerrar una alerta es descartarla. Puedes descartar una alerta si no crees que necesite arreglarse. {% data reusables.code-scanning.close-alert-examples %} Si tienes permisos de escritura en el repositorio, el botón de **Descartar** está disponible en las anotaciones de código y en el resumen de alertas. Cuando das clic en **Descartar** se te pedirá elegir una razón para cerrar la alerta. + +![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) + +{% data reusables.code-scanning.choose-alert-dismissal-reason %} + +{% data reusables.code-scanning.false-positive-fix-codeql %} + +Para obtener más información acerca de descartar alertas, consulta la sección "[Administrar alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)". + +{% endif %} diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md new file mode 100644 index 0000000000000..16ad43554bb9c --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -0,0 +1,53 @@ +--- +title: Solucionar problemas del escaneo de código de CodeQL en tu sistema de IC +shortTitle: Solucionar problemas en tu IC +intro: 'Si estás teniendo problemas con el {% data variables.product.prodname_codeql_runner %}, puedes solucionarlos si utilizas estos tips.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} + +### El comando `init` tarda demasiado + +Antes de que el {% data variables.product.prodname_codeql_runner %} pueda compilar y analizar código, necesita tener acceso al paquete de {% data variables.product.prodname_codeql %}, el cual contiene el CLI y las bibliotecas de {% data variables.product.prodname_codeql %}. + +Cuando utilizas el {% data variables.product.prodname_codeql_runner %} por primera vez en tu máquina, el comando `init` descargará el paquete de {% data variables.product.prodname_codeql %} a tu máquina. Esta descarga puede demorar algunos minutos. El paquete de {% data variables.product.prodname_codeql %} se guarda en el caché entre las ejecuciones, así que si utilizas el {% data variables.product.prodname_codeql_runner %} nuevamente en la misma máquina, no descargará el paquete de {% data variables.product.prodname_codeql %} nuevamente. + +Para evitar esta descarga automática, puedes descargar manualmente el paquete de {% data variables.product.prodname_codeql %} a tu máquina ye specifica la ruta utilizando el marcador de `--codeql-path` del comando `init`. + +### No se encontró código durante la compilación + +Si el comando `analyze` para el {% data variables.product.prodname_codeql_runner %} falla con un error de `No source code was seen during the build`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla. + +1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo que se asocia con un lenguaje de programación específico como un archivo `.h`, o `.gyp`, pero no existe el código ejecutable correspondiente a dicho lenguaje en el repositorio. Para resolver el problema, puedes definir manualmente los lenguajes que quieres analizar si utilizas el marcador `--languages` del comando `init`. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)". + +1. Estás analizando un lenguaje compilado sin utilizar el comando `autobuild` y ejecutaste los pasos de compilación después del paso `init`. Para que la compilación funcione, debes configurar el ambiente para que el {% data variables.product.prodname_codeql_runner %} pueda monitorear el código. El comando `init` genera instrucciones de cómo exportar las variables de ambiente requeridas, así que puedes copiar y ejecutar el script después de que has ejecutado el comando `init`. + - En macOS y Linux: + ```shell + $ . codeql-runner/codeql-env.sh + ``` + - En Windows, utilizando el shell de comandos (`cmd`) o un archivo de lote (`.bat`): + ```shell + > call codeql-runner\codeql-env.bat + ``` + - En Windows, utilizando PowerShell: + ```shell + > cat codeql-runner\codeql-env.sh | Invoke-Expression + ``` + + Las variables de ambiente también se almacenan en el archivo `codeql-runner/codeql-env.json`. Este archivo contiene solo un objeto de JSON que mapea las claves de variable de ambiente a valores. Si no puedes ejecutar el script que generó el comando `init`, entonces puedes utilizar los datos en formato JSON. + + {% note %} + + **Nota:** Si utilizaste el marcador `--temp-dir` flag del comando `init` para especificar un directorio personalizado para los archivos temporales, la ruta hacia los archivos de `codeql-env` podría ser diferente. + + {% endnote %} + +1. El código se compila en un contenedor o en una máquina independiente. Si utilizas una compilación que ya esté en un contenedor o si terciarizas la compilación a otra máquina, asegúrate de ejecutar el {% data variables.product.prodname_codeql_runner %} en el contenedor o en la máquina en donde toma lugar tu tarea de compilación. Para obtener más información, consulta la sección "[Ejecutar el escaneo de código de CodeQL en un contenedor](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)". diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md new file mode 100644 index 0000000000000..64cb745d45e72 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -0,0 +1,171 @@ +--- +title: Solucionar problemas en el flujo de trabajo de CodeQL +shortTitle: Solucionar problemas de CodeQL +intro: 'Si tienes problemas con el {% data variables.product.prodname_code_scanning %}, puedes solucionarlos si utilizas estos tips para resolver estos asuntos.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} + +### Compilación automática para los fallos de un lenguaje compilado + +Si una compilación automática de código para un lenguaje compilado dentro de tu proyecto falla, intenta los siguientes pasos de solución de problemas. + +- Elimina el paso de `autobuild` de tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} y agrega los pasos de compilación específicos. Para obtener información sobre cómo editar el flujo de trabajo, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)". Para obtener más información sobre cómo reemplazar el paso de `autobuild`, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". + +- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edita el flujo de trabajo y agrega una matriz de compilación que especifique los lenguajes que quieres analizar. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz. + + Los siguientes extractos de un flujo de trabajo te muestran cómo puedes utilizar una matriz dentro de la estrategia del job para especificar lenguajes, y luego hace referencia a cada uno de ellos con el paso de "Inicializar {% data variables.product.prodname_codeql %}": + + ```yaml + jobs: + analyze: + ... + strategy: + fail-fast: false + matrix: + language: ['csharp', 'cpp', 'javascript'] + + ... + + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + with: + languages: {% raw %}${{ matrix.language }}{% endraw %} + ``` + + Para obtener más información acerca de editar el flujo de trabajo, consulta la sección "[Configurar el escaneo de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)". + +### No se encontró código durante la compilación + +Si tu flujo de trabajo falla con un error de `No source code was seen during the build` o de `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla: + +1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo que se asocia con un lenguaje de programación específico como un archivo `.h`, o `.gyp`, pero no existe el código ejecutable correspondiente a dicho lenguaje en el repositorio. Para resolver el problema, puedes definir manualmente los lenguajes que quieras analizar si actualizas la lista de éstos en la matriz de `language`. Por ejemplo, la siguiente configuración analizará únicamente a Go y a Javascript. + + ```yaml + strategy: + fail-fast: false + matrix: + # Override automatic language detection by changing the list below + # Supported options are: + # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] + language: ['go', 'javascript'] + ``` +Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente. +1. Tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} está analizando un lenguaje compilado (C, C++, C#, o Java), pero el código no se compiló. Predeterminadamente, el flujo de trabajo de análisis de {% data variables.product.prodname_codeql %} contiene un paso de `autobuild`, sin embargo, este paso representa un proceso de mejor esfuerzo y podría no tener éxito en compilar tu código, dependiendo de tu ambiente de compilación específico. También podría fallar la compilación si eliminaste el paso de `autobuild` y no incluiste manualmente los pasos de compilación. Para obtener más información acerca de especificar los pasos de compilación, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". +1. Tu flujo de trabajo está analizando un lenguaje compilado (C, C++, C#, or Java), pero algunas porciones de tu compilación se almacenan en caché para mejorar el rendimiento (esto muy probablemente ocurra con los sistemas de compilación como Gradle o Bazel). Ya que {% data variables.product.prodname_codeql %} observa la actividad del compilador para entender los flujos de datos en un repositorio, {% data variables.product.prodname_codeql %} requiere que suceda una compilación completa para poder llevar a cabo este análisis. +1. Tu flujo de trabajo está analizando un lenguaje compilado (C, C++, C#, or Java), pero no ocurre ninguna compilación entre los pasos de `init` y `analyze` en el flujo de trabajo. {% data variables.product.prodname_codeql %} requiere que tu compilación tome lugar entre estos dos pasos para poder observar la actividad del compilador y llevar a cabo el análisis. +1. Tu código compilado (en C, C++, C#, or Java) se compiló con éxito, pero {% data variables.product.prodname_codeql %} no pudo detectar las invocaciones del compilador. Las causas más comunes son: + + * Ejecutar tu proceso de compilación en un contenedor separado a {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Ejecutar el escaneo de código de CodeQL en un contenedor](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)". + * Compilar utilizando un sistema de compilación distribuida externo a GitHub Actions, utilizando un proceso de daemon. + * {% data variables.product.prodname_codeql %} no está consciente del compilador específico que estás utilizando. + + Para los proyectos de .NET Framework y los de C# que utilicen ya sea `dotnet build` o `msbuild` y que apunten a .NET Core 2, debes especificar `/p:UseSharedCompilation=false` en el paso `run` de tu flujo de trabajo cuando compiles tu código. No es necesario el marcador `UseSharedCompilation` para .NET Core 3.0 o superior. + + Por ejemplo, la siguiente configuración para C# pasará el marcador durante el primer paso de compilación. + + ``` yaml + - run: | + dotnet build /p:UseSharedCompilation=false + ``` + + Si encuentras otro problema con tu compilador específico o con tu configuración, contacta a {% data variables.contact.contact_support %}. + +Para obtener más información acerca de especificar los pasos de compilación, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". + +### Algunas porciones de mi repositorio no se analizaron con `autobuild` + +La característica de `autobuild` de {% data variables.product.prodname_codeql %} utiliza la heurística para compilar el código en un repositorio, sin embargo, algunas veces este acercamiento da como resultado un análisis incompleto de un repositorio. Por ejemplo, cuando existen comandos múltiples de `build.sh` en un solo repositorio, el análisis podría no completarse, ya que el paso de `autobuild` solo se ejecutará en uno de los comandos. La solución es reemplazar el paso de `autobuild` con los pasos de compilación que compilarán todo el código fuente que quieras analizar. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". + +### La compilación tarda demasiado + +Si tu compilación con análisis de {% data variables.product.prodname_codeql %} toma demasiado para ejecutarse, hay varios acercamientos que puedes intentar para reducir el tiempo de compilación. + +#### Incrementar la memoria o los núcleos + +Si utilizas ejecutores auto-hospedados para ejecutar el análisis de {% data variables.product.prodname_codeql %}, puedes incrementar la memoria o la cantidad de núcleos en estos ejecutores. + +#### Utilizar matrices de compilación para paralelizar el análisis + +El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza una matriz de lenguajes, la cual causa que el análisis de cada uno de ellos se ejecute en paralelo. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente. + +#### Reducir la cantidad de código que se está analizando en un solo flujo de trabajo + +El tiempo de análisis es habitualmente proporcional a la cantidad de código que se esté analizando. Puedes reducir el tiempo de análisis si reduces la cantidad de código que se analice en cada vez, por ejemplo, si excluyes el código de prueba o si divides el análisis en varios flujos de trabajo que analizan únicamente un subconjunto de tu código a la vez. + +Para los lenguajes compilados como Java, C, C++ y C#, {% data variables.product.prodname_codeql %} analiza todo el código que se haya compilado durante la ejecución del flujo de trabajo. Para limitar la cantidad de código que se está analizando, compila únicamente el código que quieres analizar especificando tus propios pasos de compilación en un bloque de `run`. Puedes combinar el especificar tus propios pasos de compilación con el uso de filtros de `paths` o `paths-ignore` en los eventos de `pull_request` y de `push` para garantizar que tu flujo de trabajo solo se ejecute cuando se cambia el código específico. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". + +Para los lenguajes interpretados como Go, JavaScript, Python y TypeScript que analiza {% data variables.product.prodname_codeql %} sin una compilación específica, puedes especificar opciones de configuración adicionales para limitar la cantidad de código a analizar. Para obtener más información, consulta la sección "[Especificar los directorios a escanear](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)". + +Si divides tu análisis en varios flujos de trabajo como se describió anteriormente, aún te recomendamos que por lo menos tengas un flujo de trabajo que se ejecute con un `schedule` que analice todo el código en tu repositorio. Ya que {% data variables.product.prodname_codeql %} analiza los flujos de datos entre componentes, algunos comportamientos de seguridad complejos podrían detectarse únicamente en una compilación completa. + +#### Ejecutar únicamente durante un evento de `schedule` + +Si tu análisis aún es muy lento como para ejecutarse durante eventos de `push` o de `pull_request`, entonces tal vez quieras activar el análisis únicamente en el evento de `schedule`. Para obtener más información, consulta la sección "[Eventos](/actions/learn-github-actions/introduction-to-github-actions#events)". + +{% if currentVersion == "free-pro-team@latest" %} +### Los resultados difieren de acuerdo con la plataforma de análisis + +Si estás analizando código escrito en Python, podrías ver resultados diferentes dependiendo de si ejecutas el {% data variables.product.prodname_codeql_workflow %} en Linux, macOS o Windows. + +En los ejecutores hospedados en GitHub que utilizan Linux, el {% data variables.product.prodname_codeql_workflow %} intenta instalar y analizar las dependencias de Python, lo cual podría llevar a más resultados. Para inhabilitar la auto instalación, agrega `setup-python-dependencies: false` al paso de "Initialize CodeQL" en el flujo de trabajo. Para obtener más información acerca de la configuración del análisis para las dependencias de Python, consulta la sección "[Analizar las dependencias de Python](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)". + +{% endif %} + +### Error: "Error de servidor" + +Si la ejecución de un flujo de trabajo para {% data variables.product.prodname_code_scanning %} falla debido a un error de servidor, trata de ejecutar el flujo de trabajo nuevamente. Si el problema persiste, contaca a {% data variables.contact.contact_support %}. + +### Error: "Out of disk" o "Out of memory" +En proyectos muy grandes, + +{% data variables.product.prodname_codeql %} podría quedarse sin memoria de disco en el ejecutor. +{% if currentVersion == "free-pro-team@latest" %}Si te encuentras con este problema en un ejecutor de {% data variables.product.prodname_actions %}, contacta a {% data variables.contact.contact_support %} para que podamos investigar el problema. +{% else %}Si llegas a tener este problema, intenta incrementar la memoria en el ejecutor.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md new file mode 100644 index 0000000000000..57609d9122c45 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -0,0 +1,116 @@ +--- +title: Subir un archivo SARIF a GitHub +shortTitle: Cargar un archivo SARIF +intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}' +permissions: 'Las personas con permisos de escritura en un repositorio pueden cargar datos de {% data variables.product.prodname_code_scanning %} desde una herramienta de terceros.' +product: '{% data reusables.gated-features.code-scanning %}' +redirect_from: + - /github/managing-security-vulnerabilities/uploading-a-code-scanning-analysis-to-github +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} + +### Acerca de la carga de archivos SARIF para {% data variables.product.prodname_code_scanning %} + +{% data variables.product.prodname_dotcom %} crea alertas de {% data variables.product.prodname_code_scanning %} en un repositorio utilizando información de los archivos de Formato de Intercambio para Resultados de Análisis Estático (SARIF). El archivo SARIF puede generarse desde una herramienta de análisis compatible con SARIF que ejecutes en el mismo flujo de trabajo de {% data variables.product.prodname_actions %} que utilizaste para cargar el archivo. Como alternativa, cuando se genere el archivo como un artefacto fuera de tu repositorio, puedes cargar el archivo SARIF directamente a algún repositorio y utilizar el flujo de trabajo para subir este archivo. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". + +Puedes generar archivos SARIF utilizando muchas herramientas de prueba de seguridad para análisis estático, incluyendo a {% data variables.product.prodname_codeql %}. Para cargar resultados desde herramientas de terceros debes utilizar el Formato de Intercambio para Resultados de Análisis Estático (SARIF) 2.1.0. Para obtener más información, consulta la sección "[Acerca de la compatibilidad de SARIF con {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning)". + +Puedes cargar los resultados utilizando las {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (disponibles si tu organización está participando en el programa del beta){% endif %}, la API del {% data variables.product.prodname_code_scanning %}, o el {% data variables.product.prodname_codeql_runner %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas: + +- {% data variables.product.prodname_actions %} para ejecutar la acción de {% data variables.product.prodname_codeql %}, no hay que hacer nada más. La acción de {% data variables.product.prodname_codeql %} carga el archivo de SARIF automáticamente cuando completa el análisis. +- "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" +- {% data variables.product.prodname_dotcom %} mostrará alertas de {% data variables.product.prodname_code_scanning %} desde el archivo SARIF cargado en tu repositorio. Si bloqueas la carga automática, cuando estés listo para cargar los resultados, puedes utilizar el comando `upload` (para obtener más información, consulta la seción "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)"). +- Una herramienta que genera resultados como un artefacto fuera de tu repositorio, puedes utilizar la API de {% data variables.product.prodname_code_scanning %} para cargar el archivo (para obtener más ifnormación, consulta la sección "[Cargar un archivo de SARIF](/rest/reference/code-scanning#upload-a-sarif-file)"). + +{% data reusables.code-scanning.not-available %} + +### Cargar un análisis de {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_actions %} + +Para cargar un archivo SARIF de terceros a {% data variables.product.prodname_dotcom %}, necesitarás un flujo de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" y "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Tu flujo de trabajo necesitará utilizar la acción `upload-sarif`, que tiene parámetros de entrada que puedes utilizar para configurar la carga. Tiene parámetros de entrada que puedes utilizar para configurar la carga. El parámetro de entrada principal que utilizarás será `sarif-file`, el cual configura el archivo o directorio de los archivos SARIF a cargar. El directorio o ruta de archivo es relativo a la raíz del repositorio. Para obtener más información, consulta la [acción `upload-sarif`](https://github.com/github/codeql-action/tree/HEAD/upload-sarif). + +La acción `upload-sarif` puede configurarse para ejecutarse cuando ocurren los eventos `push` y `scheduled`. Para obtener más información acerca de los eventos {% data variables.product.prodname_actions %}, consulta la sección [Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)". + +Si tu archivo SARIF no incluye `partialFingerprints`, la acción `upload-sarif` calculará el campo `partialFingerprints` para ti e intentará prevenir las alertas duplicadas. {% data variables.product.prodname_dotcom %} solo puede crear `partialFingerprints` cuando el repositorio contenga tanto el archivo SARIF como el código fuente utilizado en el análisis estático. Para obtener más información acerca de prevenir alertas duplicadas, consulta la sección "[Acerca de la compatibilidad de SARIF con el escaneo de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)". + +#### Ejemplo de flujo de trabajo para los archivos SARIF generados fuera de un repositorio + +Puedes crear un nuevo flujo de trabajo que cargue archivos SARIF después de que los confirmes en tu repositorio. Esto es útil cuando el archivo SARIF se genera como un artefacto fuera de tu repositorio. + +Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". + +Este flujo de trabajo carga el archivo `results.sarif` ubicado en la raíz del repositorio. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +Como alternativa, puedes modificar este flujo de trabajo para cargar un directorio de archivos SARIF. Por ejemplo, puedes colocar todos los archivos SARIF en un directorio en la raíz de tu repositorio, el cual se llame `sarif-output` y configurar el parámetro de entrada de la acción `sarif_file` como `sarif-output`. + +```yaml +name: "Upload SARIF" + +# Run workflow each time code is pushed to your repository and on a schedule. +# The scheduled workflow runs every at 00:00 on Sunday UTC time. +on: + push: + schedule: + - cron: '0 0 * * 0' + +jobs: + build: + runs-on: ubuntu-latest + steps: + # This step checks out a copy of your repository. + - name: Checkout repository + uses: actions/checkout@v2 + - name: Upload SARIF file + uses: github/codeql-action/upload-sarif@v1 + with: + # Path to SARIF file relative to the root of the repository + sarif_file: results.sarif +``` + +#### Ejemplo de flujo de trabajo que ejecuta la herramienta de análisis ESLint + +Si generas tu archivo SARIF de terceros como parte de un flujo de trabajo de integración contínua (IC), puedes agregar la acción `upload-sarif` como un paso después de ejecutar tus pruebas de IC. Si aún no tienes un flujo de trabajo de IC, puedes crearlo utilizando una plantilla de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)". + +Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". + +El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y da como salida el archivo `results.sarif`. El flujo de trabajo entonces carga el archivo `results.sarif` a {% data variables.product.prodname_dotcom %} utilizando la acción `upload-sarif`. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Introducción a Github Actions](/actions/learn-github-actions/introduction-to-github-actions)". + +```yml +name: "ESLint analysis" + +# Run workflow each time code is pushed to your repository and on a schedule. +# The scheduled workflow runs every at 00:00 on Sunday UTC time. +on: + push: + schedule: + - cron: '0 0 * * 0' + +jobs: + build: + steps: + - uses: actions/checkout@v2 + - name: Run npm install + run: npm install + # Runs the ESlint code analysis + - name: Run ESLint + # eslint exits 1 if it finds anything to report + run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true + # Uploads results.sarif to GitHub repository using the upload-sarif action + - uses: github/codeql-action/upload-sarif@v1 + with: + # Path to SARIF file relative to the root of the repository + sarif_file: results.sarif +``` + +### Further reading + +- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" +- "[Visualizar tu historial de flujos de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)" +- "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)" +- "[Cargar un archivo SARIF](/rest/reference/code-scanning#upload-a-sarif-file)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md new file mode 100644 index 0000000000000..9a9d8c28ff08c --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md @@ -0,0 +1,11 @@ +--- +title: Utilizar el escaneo de código de CodeQL en tu sistema de IC existente +shortTitle: Soporte de CodeQL para sistemas de IC +intro: 'El {% data variables.product.prodname_codeql_runner %} te permite utilizar tu sistema de IC existente para ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}.' +mapTopic: verdadero +product: '{% data reusables.gated-features.code-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md b/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md new file mode 100644 index 0000000000000..8310add832024 --- /dev/null +++ b/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md @@ -0,0 +1,35 @@ +--- +title: Acerca de Empleos GitHub +redirect_from: + - /articles/how-to-write-a-great-job-post/ + - /articles/about-github-jobs +intro: 'Puedes publicar un empleo en {% data variables.product.prodname_jobs %} para encontrar talentos para tu negocio.' +versions: + free-pro-team: '*' +--- + +Antes de poder publicar un empleo, debes crear una cuenta de {% data variables.product.prodname_dotcom %} y verificar tu dirección de correo electrónico. Para obtener más información, consulta "[Registrarse con una nueva cuenta de {% data variables.product.prodname_dotcom %} ](/articles/signing-up-for-a-new-github-account)" y "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". + +### Mejores prácticas para escribir la publicación de un empleo + +Cuando escribas la publicación de un empleo, haz que el título sea lo más descriptivo posible. Intenta mencionar el idioma o las tecnologías que requiere el empleo. + +En la descripción del empleo, incluye información acerca de la cultura de tu empresa y los beneficios que ofreces. Describe el puesto detalladamente, incluyendo información acerca de las responsabilidades del empleo y el equipo con el que el candidato trabajará. Enumera las principales habilidades requeridas para el empleo en orden de importancia. + +Para ayudar a los candidatos a encontrar tu publicación del empleo, verifica **Búsquedas de máxima actualidad** en la parte inferior de la página principal. Si alguna de estas categorías aplica para tu puesto vacante, inclúyelas en tu descripción del empleo. + +![Sección Búsquedas de máxima actualidad de {% data variables.product.prodname_dotcom %}](/assets/images/help/jobs/hot-searches.png) + +{% tip %} + +**Sugerencia:** {% data variables.product.prodname_dotcom %} no hace un seguimiento de las vistas de tu publicación del empleo ni del número de clics. Si quieres hacer un seguimiento del número de clics, puedes agregar parámetros de seguimiento a la URL que incluyes en el campo **Cómo postularse**. Para obtener más información, consulta "[Parámetros de la URL](https://support.google.com/google-ads/answer/6277564?hl=en)" de Google. + +{% endtip %} + +### Dar formato a tu publicación del empleo + +Puedes usar Markdown para dar formato a tu publicación del empleo. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". + +### Further reading + +- [Cómo funiona {% data variables.product.prodname_jobs %} ](https://jobs.github.com/faq) en {% data variables.product.prodname_jobs %} diff --git a/translations/es-ES/content/github/finding-talent-with-github-jobs/index.md b/translations/es-ES/content/github/finding-talent-with-github-jobs/index.md new file mode 100644 index 0000000000000..648e2a6d01b60 --- /dev/null +++ b/translations/es-ES/content/github/finding-talent-with-github-jobs/index.md @@ -0,0 +1,14 @@ +--- +title: Encontrar talento con Empleos GitHub +redirect_from: + - /categories/72/articles/ + - /categories/jobs/ + - /categories/finding-talent-with-github-jobs +versions: + free-pro-team: '*' +--- + + +### Índice + +{% link_in_list /about-github-jobs %} diff --git a/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..90aa71eacd8aa --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### Acerca de {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md new file mode 100644 index 0000000000000..7a882392fa8ce --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md @@ -0,0 +1,39 @@ +--- +title: Permisos de acceso en GitHub +redirect_from: + - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/ + - /articles/what-are-the-different-types-of-team-permissions/ + - /articles/what-are-the-different-access-permissions/ + - /articles/access-permissions-on-github +intro: 'Si bien puedes otorgar acceso de lectura/escritura a los colaboradores en un repositorio personal, los miembros de una organización pueden tener más permisos de acceso granular para los repositorios de la organización.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Cuentas de usuarios personales + +Un repositorio que es propiedad de una cuenta de usuario y tiene dos niveles de permiso: el *propietario del repositorio* y los *colaboradores*. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)". + +### Cuentas de organización + +Los miembros de la organización pueden tener roles de *propietario*{% if currentVersion == "free-pro-team@latest" %}, *gerente de facturación*,{% endif %} o de *miembro*. Los propietarios tienen acceso administrativo íntegro a tu organización{% if currentVersion == "free-pro-team@latest" %}, mientras que los gerentes de facturación pueden administrar la configuración de facturación{% endif %}. El miembro tiene un rol predeterminado para todos los demás. Puedes administrar los permisos de acceso para múltiples miembros a la vez con equipos. Para obtener más información, consulta: +- [Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" +- [Acerca de los equipos](/articles/about-teams)" + +{% if currentVersion == "free-pro-team@latest" %} + +### Cuentas de empresa + +Los *propietarios de empresa* tienen máximo poder sobre la cuenta de la empresa y pueden tomar medidas en la cuenta de la empresa. Los *gerentes de facturación* pueden administrar los parámetros de facturación de la cuenta de la empresa. Los miembros y colaboradores externos de las organizaciones que son propiedad de tu cuenta empresarial automáticamente son miembros de la cuenta empresarial, si bien no tienen acceso a la cuenta empresarial en sí o a sus parámetros. Para obtener más información, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". + +{% data reusables.gated-features.enterprise-accounts %} + +{% endif %} + +### Further reading + +- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/github/getting-started-with-github/be-social.md b/translations/es-ES/content/github/getting-started-with-github/be-social.md new file mode 100644 index 0000000000000..3eed4619fcb74 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/be-social.md @@ -0,0 +1,69 @@ +--- +title: Ser social +redirect_from: + - /be-social/ + - /articles/be-social +intro: 'Puedes interactuar con personas, repositorios y organizaciones en {% data variables.product.prodname_dotcom %}. Ve en qué están trabajando los demás y con quién se están conectando desde tu tablero personal.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para conocer más sobre cómo acceder a tu tablero personal, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +### Seguir a personas + +Cuando sigues a alguien en {% data variables.product.product_location %}, recibirás notificaciones en tu tablero personal sobre su actividad. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +Haz clic en **Follow** (Seguir) en la página de perfil de una persona para seguirla. + +![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) + +### Ver un repositorio + +Puedes ver un repositorio para recibir notificaciones para las nuevas solicitudes de extracción y propuestas. Cuando el propietario actualiza el repositorio, verás los cambios en tu tablero personal. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)"{% else %}"[Observar y dejar de observar los repositorios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}". + +Haz clic en **Watch** (Ver) en la parte superior del repositorio que desas ver. + +![Botón Watch repository (Ver repositorio)](/assets/images/help/repository/repo-actions-watch.png) + +### Unirse a la conversación + +{% data reusables.support.ask-and-answer-forum %} + +### Hacer un poco más + +#### Crear solicitudes de extracción + + Es posible que desees contribuir al proyecto de otras personas, ya sea para agregar características o para arreglar errores. Luego de realizar cambios, permite que el autor original lo sepa al enviar una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." + + ![Botón Pull request (Solicitud de extracción)](/assets/images/help/repository/repo-actions-pullrequest.png) + +#### Usar propuestas + +Al colaborar en un repositorio, usa las propuestas para realizar el seguimiento de ideas, mejoras, tareas o errores. Para obtener más información, consulta '[Acerca de las propuestas](/articles/about-issues/)". + +![Botón Issues (Propuestas)](/assets/images/help/repository/repo-tabs-issues.png) + +#### Participación en las organizaciones + +Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y administradores pueden establecer equipos con permisos especiales, tener un perfil de organización pública y realizar el seguimiento de la actividad dentro de la organización. Para obtener más información, consulta "[Acerca de las organizaciones](/articles/about-organizations)". + +![Desplegable de contexto para cambiar cuenta](/assets/images/help/overview/dashboard-contextswitcher.png) + +#### Explorar otros proyectos en {% data variables.product.prodname_dotcom %} + +Descubre proyectos interesantes al utilizar {% data variables.explore.explore_github %}, [Explorar repositorios](https://github.com/explore), y el {% data variables.explore.trending_page %}. Marca con una estrella los proyectos interesantes y regresa posteriormente. Visita tu {% data variables.explore.your_stars_page %} para ver todos los proyectos marcados con una estrella. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard/)". + +### Celebrar + +Ahora estás conectado con la comunidad de {% data variables.product.product_name %}. ¿Qué deseas hacer ahora? + +![Marcar un proyecto con una estrella](/assets/images/help/stars/star-a-project.png) + +- [Configurar Git](/articles/set-up-git) +- [Crear un repositorio](/articles/create-a-repo) +- [Bifurcar un repositorio](/articles/fork-a-repo) +- **Ser social** +- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md b/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md new file mode 100644 index 0000000000000..40668828523c4 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md @@ -0,0 +1,77 @@ +--- +title: Crear un repositorio +redirect_from: + - /create-a-repo/ + - /articles/create-a-repo +intro: 'Para subir tu proyecto a {% data variables.product.product_location %}, deberás crear un repositorio donde alojarlo.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +Puedes almacenar distintos proyectos en los repositorios de {% data variables.product.product_name %}, incluso proyectos de código abierto. Con [proyectos de código abierto](http://opensource.org/about), puedes compartir el código para hacer que el software funcione mejor y sea más confiable. + +{% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +Puedes almacenar varios proyectos en los repositorios de {% data variables.product.product_name %}, incluyendo los proyectos de innersource. Con innersource, puedes compartir el código para hacer software mejor y más confiable. Para obtener más información sobre innersource, consulta la documentación técnica de {% data variables.product.company_short %}"[Una introducción a innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)". + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** Puedes crear repositorios públicos para un proyecto de código abierto. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](http://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %} + +{% endnote %} + +{% endif %} + +{% data reusables.repositories.create_new %} +2. Escribe un nombre corto y fácil de recordar para tu repositorio. Por ejemplo: "hola-mundo". ![Campo para ingresar un nombre para el repositorio](/assets/images/help/repository/create-repository-name.png) +3. También puedes agregar una descripción de tu repositorio. Por ejemplo, "Mi primer repositorio en +{% data variables.product.product_name %}". + ![Campo para ingresar una descripción para el repositorio](/assets/images/help/repository/create-repository-desc.png) +{% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} + +¡Felicitaciones! Has creado correctamente tu primer repositorio y lo has inicializado con un archivo *README*. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% tip %} + +**Tip**: También puedes crear repositorios utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +### Confirma tu primer cambio + +Una *[confirmación](/articles/github-glossary#commit)* es como una instantánea de todos los archivos de tu proyecto en un momento en particular. + +Cuando creaste tu nuevo repositorio, lo inicializaste con un archivo *README*. Los archivos *README* son un lugar ideal para describir tu proyecto en más detalle o agregar documentación, como la forma en que se debe instalar o usar tu proyecto. El contenido de tu archivo *README* se mostrará automáticamente en la página inicial de tu repositorio. + +Confirmemos un cambio en el archivo *README*. + +1. Es la lista de archivos de tu repositorio, haz clic en ***README.md***. ![Archivo Readme en la lista de archivos](/assets/images/help/repository/create-commit-open-readme.png) +2. En el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. +3. En la pestaña **Editar archivo**, escribe alguna información sobre ti. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) +{% data reusables.files.preview_change %} +5. Revisa los cambios que realizaste en el archivo. Verás el contenido nuevo en verde. ![Vista previa del archivo](/assets/images/help/repository/create-commit-review.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Celebrar + +¡Felicitaciones! Has creado un repositorio, además de un archivo *README*, y has creado tu primera confirmación en {% data variables.product.product_location %}. ¿Qué deseas hacer ahora? + +- "[Configurar Git](/articles/set-up-git)" +- **Crear un repositorio** +- "[Bifurcar un repositorio](/articles/fork-a-repo)" +- "[Socializar](/articles/be-social)" +- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md b/translations/es-ES/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md new file mode 100644 index 0000000000000..867fb90db8cee --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/exploring-early-access-releases-with-feature-preview.md @@ -0,0 +1,25 @@ +--- +title: Explorar versiones de acceso anticipado con vista previa de la característica +intro: Puedes usar la vista previa de las características para ver los productos o las características que están disponibles en beta y para activar o desactivar cada característica de tu cuenta de usuario. +redirect_from: + - /articles/exploring-early-access-releases-with-feature-preview +versions: + free-pro-team: '*' +--- + +### ciclo de lanzamiento de {% data variables.product.prodname_dotcom %} + +Los productos y características de {% data variables.product.product_name %}pueden pasar por varias fases de lanzamiento. + +| Fase | Descripción | +| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Alfa | El producto o la característica está bajo un gran desarrollo y a menudo tiene requisitos y alcance cambiantes. Esta característica se encuentra disponible para propósitos de demostración y pruebas, pero puede no documentarse. Las versiones Alpha no necesariamente tienen una función completa, no se proporcionan Acuerdo de nivel de servicio (SLA) y no hay obligaciones de apoyo técnico. | +| Beta | El producto o característica está listo para una distribución más amplia. Las versiones beta pueden ser públicas o privadas, están documentadas, pero no tienen ningún SLA u obligación de soporte técnico. | +| Disponibilidad general (GA) | El producto o característica está completamente probado y abierto públicamente a todos los usuarios. Las versiones de GA están listas para su uso en producción, y se aplican el Acuerdo de nivel de servicio y las obligaciones de asistencia técnica asociados. | + +### Explorar versiones beta con vista previa de la característica + +Puedes ver una lista de características disponibles en beta y una breve descripción de cada característica. Cada característica incluye un enlace para proporcionar retroalimentación. + +{% data reusables.feature-preview.feature-preview-setting %} +2. Opcionalmente, a la derecha de una función, haz clic en **Enable** (Habilitar) o **Disable** (Inhabilitar). ![Activar el botón en la vista previa de la característica](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md b/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md new file mode 100644 index 0000000000000..12e3d5cac9c09 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md @@ -0,0 +1,15 @@ +--- +title: Explorar proyectos en GitHub +intro: '' +mapTopic: verdadero +redirect_from: + - /categories/stars/ + - /categories/87/articles/ + - /categories/exploring-projects-on-github/ + - /articles/exploring-projects-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md b/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md new file mode 100644 index 0000000000000..741502244a064 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md @@ -0,0 +1,90 @@ +--- +title: Preguntas frecuentes sobre los cambios en los planes de GitHub +intro: 'Desde el primero de abril de 2020, GitHub anunció que todas las características principales de la empresa son ahora gratuitas para todos.' +versions: + free-pro-team: '*' +--- + +### ¿Qué cambios en precios y planes para GitHub se anunciaron en el 14 de abril? + +GitHub anunció los siguientes cambios en sus planes y precios: + +- GitHub Free para organizaciones se encuentra inmediatamente disponible e incluye repositorios privados para usuarios ilimitados +- Todas las organizaciones que estaban utilizando Team para Código Abierto previamente tendrán ahora GitHub Free +- Github Free para desarrolladores individuales incluye ahora colaboradores ilimitados +- Las organizaciones e individuos que utilicen GitHub Free recibirán el Soporte de la Comunidad de GitHub +- GitHub Pro incluirá ahora 2GB de almacenamiento de paquetes y 10GB de transferencia de datos +- GitHub Pro ahora redujo su precio mensual a $4 +- GitHub Team tiene ahora un precio mensual reducido de $4 por usuario +- GitHub Team ya no tiene una cantidad mínima requerida de cinco plazas +- GitHub Team incluye 3,000 minutos de Acciones mensuales para los repositorios privados + +### ¿Cómo puedo mejorar mi plan? + +Para mejorar el plan de tu cuenta de usuario, consulta "[Mejorar tu suscripción de cuenta personal](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#upgrading-your-personal-accounts-subscription)". Para mejorar el plan de tu organización, consulta "[Mejorar la suscripción de tu organización](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". + +### ¿Cómo puedo bajar mi plan? + +Para bajar el plan de tu cuenta de usuario, consulta "[Bajar la suscripción de tu cuenta de usuario](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#downgrading-your-user-accounts-subscription)". Para bajar el plan de tu organización, consulta "[Bajar la suscripción de tu organización](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#downgrading-your-organizations-subscription)". + +### Si bajo de categoría desde GitHub Team o un plan tradicional hacia GitHub Free, ¿qué características perderé? +- Revisores requeridos en repositorios privados +- Ramas protegidas en repositorios privados +- Propietarios de código en repositorios privados +- GitHub Pages en repositorios privados +- Wikis en repositorios privados +- Asignados múltiples para informes de problemas y solicitudes de extracción en repositorios privados +- Revisores múltiples para solicitudes de extracción en repositorios privados +- Borradores de solicitudes de extracción en repositorios privados +- Referencias auto-vinculadas en repositorios privados +- Soporte estándar + +### ¿Cómo puedo crear una organización de GitHub Free o GitHub Team? + +Si tienes una cuenta en GitHub, crea una nueva organización en nuestra [página de plan de equipo](https://github.com/organizations/plan). Si no tienes una cuenta en GitHub, puedes [crear una en nuestra página principal](https://github.com/) y se te pedirá crear una organización durante el proceso de registro. + +### ¿Cómo puedo comparar las características de cada plan? + +Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. + +### ¿Por cuánto tiempo se permitirá un número ilimitado de colaboradores en GitHub Free? + +¡Por siempre! Este cambio es permanente. + +### Ya pagué por el plan anual de Pro o Team, ¿se me reembolsará por la diferencia de precio? + +Los clientes que están pagando anualmente por los planes de Pro o Team y se registraron antes del 14 de abril recibirán un reembolso por una cantidad prorrateada hasta finalizar su periodo de facturación anual. Por ejemplo, si llevas dos meses de suscripción y se te factura anualmente, recibirás un reembolso por la diferencia de precios de los diez meses restantes. Estos reembolsos se procesarán en 30 días, aproximadamente. Una vez que se haya procesado tu reembolso, se te enviará una notificación a la dirección de correo electrónico que hayas elegido para facturación. + +### ¿Cuál es la diferencia entre GitHub Free para desarrolladores individuales y GitHub Free para organizaciones? + +Para encontrar los detalles de las diferencias entre los productos de GitHub free, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". + +### ¿Cómo puedo tener más minutos de Actions si necesito más que la cantidad que se designa en el plan de GitHub Team? + +La mayoría de los equipos pequeños utiliza menos de 3,000 minutos mensuales de Actions, pero algunos equipos podrían utilizar más. Si tu equipo necesita minutos adicionales para repositorios privados, puedes incrementar tu límite de gastos para GitHub Actions. Los minutos de Actions y almacenamiento de paquetes siguen siendo gratuitos para tus repositorios públicos. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para GitHub Actions](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)". + +### ¿Cómo me afectan los cambios en el límite de plazas? + +Ahora que {% data variables.product.prodname_team %} no requiere de un mínimo de plazas, si utilizas menos de cinco en tu organización, podrás eliminar las plazas pagadas para reducir tu cuenta. Para obtener más información, consulta la sección "[Bajar la categoría de tu suscripción de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#removing-paid-seats-from-your-organization)". + +### ¿Cambiará algo para los equipos con plan de GitHub Team para código abierto? + +Si tu cuenta de organización utiliza el plan de GitHub Team para código abierto, se te migrará automáticamente a GitHub Free, lo cual incluye repositorios privados con colaboradores ilimitados, 2,000 minutos de actions para repositorios privados, y el Soporte de la Comunidad de GitHub. Los minutos de Actions y almacenamiento de paquetes siguen siendo gratuitos para tus repositorios públicos. + +### ¿Qué es el Soporte de la Comunidad de GitHub? + +El Soporte de la Comunidad de GitHub incluye soporte a través de nuestro [Foro de la Comunidad](https://github.community/), en donde puedes buscar soluciones de la comunidad de GitHub, hacer preguntas nuevas, y compartir ideas. Los Ingenieros de Soporte de GitHub Team son quienes atienden la parte de Soporte de la Comunidad de Github, y quienes moderan el Foro de la Comunidad en conjunto con nuestros miembros más activos en la misma. Si necesitas reportar spam, algún tipo de abuso, o si tienes problemas con el acceso a tu cuenta, puedes enviar un mensaje a nuestro Equipo de Soporte en https://support.github.com/.. + +### ¿Cómo afecta este cambio a los beneficios educacionales? + +Los estudiantes y maestros seguirán recibiendo todos los beneficios que reciben hoy en día. GitHub continuará ofreciendo GitHub Pro como parte de los beneficios de su [Paquete de Desarrollador para Estudiantes](https://education.github.com/pack) a todos los estudiantes. Adicionalmente, los maestros continuarán teniendo acceso a GitHub Team como parte de las [Herramientas para Maestros](https://education.github.com/toolbox). + +### ¿Cómo me afecta esto si actualmente pago por factura? + +Si actualmente eres un cliente que paga por factura, contacta por correo electrónico a tu representante de ventas para recibir más detalles. Si no sabes quién es tu representante de ventas, contacta a tu gerente de facturación o propietario de cuenta. + +### ¿Cómo va afectar esto a los usuarios y organizaciones que se encuentran en regiones donde se aplican las sanciones del gobierno de los EE.UU? government sanctions are applied? + +Due to U.S. Debido a los controles de comercio y restricciones legales, GitHub no puede proporcionar servicios para repositorios privados y servicios pagados a cuentas que se encuentren en las zonas sancionadas por los EE.UU. sanctioned regions. Sin embargo, GitHub ha preservado el acceso a los servicios gratuitos para repositorios públicos. Por favor lee sobre [GitHub y los Controles Comerciales](/github/site-policy/github-and-trade-controls) para obtener más información. + +GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU., el mejor acceso posible a los servicios colaborativos de código abierto para desarrolladores en regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. de fomentar el flujo libre de información y libertad de expresión en estas regiones. . Consideramos que ofrecer estos servicios gratuitos apoya a EE. UU. foreign policy of encouraging the free flow of information and free speech in those regions. diff --git a/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md new file mode 100644 index 0000000000000..bafb09e6a9643 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -0,0 +1,52 @@ +--- +title: Encontrar maneras para colaborar con el código abierto en GitHub +intro: 'Puedes encontrar maneras de contribuir a los proyectos de código abierto en {% data variables.product.product_name %} que te parezcan relevantes.' +redirect_from: + - /articles/where-can-i-find-open-source-projects-to-work-on/ + - /articles/finding-interesting-projects-on-github/ + - /articles/about-official-github-mirrors/ + - /articles/about-github-mirrors/ + - /articles/finding-open-source-projects-on-github + - /github/getting-started-with-github/finding-open-source-projects-on-github +versions: + free-pro-team: '*' +--- + +### Descubrir proyectos relevantes + +Si hay un tema en particular que te interese, visita `github.com/topics/`. Por ejemplo, si te interesa el aprendizaje automático, puedes encontrar proyectos relevantes e informes de problemas iniciales si visitas https://github.com/topics/machine-learning. Puedes buscar temas populares si visitas [Temas](https://github.com/topics). También puedes buscar repositorios que empaten con algún tema que te interese. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)". + +Si has tenido actividad en {% data variables.product.product_name %} recientemente, puedes encontrar recomendaciones personalizadas para proyectos e informes de problemas iniciales que se basen en tus contribuciones, estrellas y otras actividades previas en [Explore](https://github.com/explore). También puedes registrarte para el boletín Explore para recibir correos electrónicos sobre las oportunidades disponibles para colaborar con {% data variables.product.product_name %} de acuerdo a tus intereses. Para registrarte, consulta [Boletín Explore por correo](https://github.com/explore/subscribe). + +Mantente al tanto de las actividades recientes de los repositorios y personas que sigues en la sección "Toda la actividad" de tu tablero personal. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +{% data reusables.support.ask-and-answer-forum %} + +### Encontrar informes de problemas iniciales + +Si ya sabes en qué proyecto quieres trabajar, puedes encontrar informes de problemas aptos para principiantes en ese repositorio si visitas `github.com///contribute`. Como ejemplo, puedes encontrar cómo realizar tu primera contribución a `electron/electron` en https://github.com/electron/electron/contribute. + +### Proyectos de código abierto con espejos en {% data variables.product.prodname_dotcom %} + +Algunos proyectos de código abierto presentan espejos en {% data variables.product.prodname_dotcom_the_website %} además de sus repositorios oficiales, que se alojan en otro lugar. + +Los siguientes son algunos de los repositorios más importantes que tienen sus espejos en {% data variables.product.prodname_dotcom_the_website %}: + +- [Android Open Source Project](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) +- [The FreeBSD Project](https://github.com/freebsd) +- [Glasgow Haskell Compiler](https://github.com/ghc) +- [GNOME](https://github.com/GNOME) +- [Linux kernel source tree](https://github.com/torvalds/linux) +- [Qt](https://github.com/qt) + +Para configurar tu propio espejo, puedes configurar [un gancho posrecepción](https://git-scm.com/book/en/Customizing-Git-Git-Hooks) en tu repositorio oficial del proyecto para subir automáticamente las confirmaciones a un repositorio espejo en {% data variables.product.product_name %}. + +Puedes buscar repositorios en función de si tienen un espejo o no. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-a-mirror)". + +### Further reading + +- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" +- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-ES/content/github/getting-started-with-github/following-people.md b/translations/es-ES/content/github/getting-started-with-github/following-people.md new file mode 100644 index 0000000000000..9a5b52f4243a2 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/following-people.md @@ -0,0 +1,23 @@ +--- +title: Seguir a personas +intro: 'Puedes seguir personas en {% data variables.product.product_name %} para recibir notificaciones acerca de su actividad{% if currentVersion == "free-pro-team@latest" %} y descubrir proyectos en sus comunidades{% endif %}.' +redirect_from: + - /articles/following-people +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando sigues a las personas, verás su actividad pública en la vista de actividad de tus noticias.{% if currentVersion == "free-pro-team@latest" %} Si alguien que sigues marca como favorito un repositorio público, {% data variables.product.product_name %} podría recomendártelo en la vista de descubrimientos de tus noticias.{% endif %} Para seguir a alguien, visita su página de perfil y da clic en la opción **Seguir** debajo de su imagen de perfil. + +![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) + +Para dejar de seguir a alguien, visita su página de perfil y haz clic en **Dejar de seguir** debajo de su imagen de perfil. + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" +- "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" +{% endif %} diff --git a/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md b/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md new file mode 100644 index 0000000000000..5e364e0741914 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md @@ -0,0 +1,153 @@ +--- +title: Bifurcar un repositorio +redirect_from: + - /fork-a-repo/ + - /forking/ + - /articles/fork-a-repo +intro: Una ramificación es una copia de un repositorio. Bifurcar un repositorio te permite experimentar libremente con cambios sin afectar el proyecto original. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Casi siempre las bifurcaciones se usan para proponer cambios al proyecto de otra persona o para usar el proyecto de otra persona como inicio de tu propia idea. + +#### Proponer cambios para el proyecto de otra persona + +Por ejemplo, puedes utilizar ramificaciones para proponer cambios relacionados con arreglar un error. En lugar de registrar una propuesta para un error que has encontrado, puedes hacer lo siguiente: + +- Bifurcar el repositorio. +- Solucionar el problema. +- Emitir solicitudes de cambios al propietario del proyecto. + +#### Usar el proyecto de otra persona como inicio de tu propia idea + +El software de código abierto se basa en la idea de que, si compartimos el código, podemos crear software más confiable y mejor. Para obtener más información, consulta la sección "[Acerca de la Iniciativa de Código Abierto](http://opensource.org/about)" en la Iniciativa de Código Abierto. + +Para obtener más información sobre cómo aplicar los principios de código abierto en el trabajo de desarrollo de tu organización en {% data variables.product.product_location %}, consulta la documentación técnica de {% data variables.product.prodname_dotcom %} en "[Introducción al innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)". + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Cuando creas tu repositorio público desde una ramificación del proyecto de alguien más, asegúrate de incluir el archivo de licencia que determine cómo quieres que se comparta tu proyecto con los demás. Para obtener más información, consulta la sección "[Elegir una licencia de código abierto](http://choosealicense.com/)" en choosealicense. + +{% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %} + +{% endif %} + +{% note %} + +**Nota**: {% data reusables.repositories.desktop-fork %} + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% tip %} + +**Tip**: También puedes bifurcar un repositorio utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo fork`](https://cli.github.com/manual/gh_repo_fork)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +### Bifurcar un repositorio a modo de ejemplo + +Bifurcar un repositorio es un proceso muy simple que lleva dos pasos. Hemos creado un repositorio para que practiques. + +1. En {% data variables.product.product_location %}, dirígete al repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). +2. En el ángulo superior derecho de la página, haz clic en **Bifurcar**. ![Botón Bifurcar](/assets/images/help/repository/fork_button.jpg) + +### Mantener tu bifurcación sincronizada + +Puedes ramificar un proyecto para proponer cambios en los repositorios precedentes u originales. En este caso, es una buena práctica sincronizar tu bifurcación periódicamente con el repositorio ascendente. Para hacerlo, deberás usar Git en la línea de comando. Puedes practicar cómo configurar el repositorio precedente utilizando el mismo repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) que acabas de ramificar. + +#### Paso 1: Configurar Git + +Si todavía no lo has hecho, primero debes [configurar Git](/articles/set-up-git). No olvides [configurar la autenticación a {% data variables.product.product_location %} desde Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). + +#### Paso 2: Crear un clon local de tu bifurcación + +Ahora tienes una bifurcación del repositorio Spoon-Knife, pero no tienes los archivos de ese repositorio en tu computadora. Vamos a crear un clon de tu bifurcación en tu computadora. + +1. Activado + +{% data variables.product.product_name %}, navega a **tu bifurcación** del repositorio Spoon-Knife. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +4. Escribe `git clone`, y luego pega la URL que copiaste antes. Se verá así, con tu nombre de usuario de {% data variables.product.product_name %} en lugar de `YOUR-USERNAME`: + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + ``` + +5. Presiona **Enter** (Intro). Se creará tu clon local. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + > Cloning into `Spoon-Knife`... + > remote: Counting objects: 10, done. + > remote: Compressing objects: 100% (8/8), done. + > remove: Total 10 (delta 1), reused 10 (delta 1) + > Unpacking objects: 100% (10/10), done. + ``` + +Ahora tienes una copia local de tu ramificación en el repositorio Spoon-Knife. + +#### Paso 3: Configurar Git para sincronizar tu bifurcación con el repositorio original Spoon-Knife + +Cuando bifurcas un proyecto para proponer cambios en el repositorio original, puedes configurar Git para extraer cambios del original, o repositorio ascendente, en el clon local de tu bifurcación. + +1. Activado + +{% data variables.product.product_name %}, navega al repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +4. Cambia los directorios a la ubicación de la bifurcación que clonaste en el [Paso 2: Crear un clon local de tu bifurcación](#step-2-create-a-local-clone-of-your-fork). + - Para ir a tu directorio de inicio, escribe solo `cd` sin ningún otro texto. + - Para generar una lista de los archivos y carpetas en tu directorio actual, escribe `ls`. + - Para ir a uno de los directorios de la lista, escribe `cd your_listed_directory`. + - Para subir un directorio, escribe `cd ..`. +5. Escribe `git remote -v` y presiona **Intro**. Verás el repositorio remoto configurado actualmente para tu bifurcación. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` + +6. Escribe `git remote add upstream` y luego pega la URL que copiaste en el Paso 2 y presiona **Intro**. Se verá así: + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git + ``` + +7. Para verificar el nuevo repositorio ascendente que has especificado para tu bifurcación, escribe nuevamente `git remote -v`. Debes ver la URL para tu bifurcación como `origin` y la URL para el repositorio original como `upstream`. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` + +Ahora, puedes mantener tu bifurcación sincronizada con el repositorio ascendente con unos pocos comandos Git. Para obtener más información, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". + +#### Pasos siguientes + +Puedes hacer cualquier cambio a una ramificación, incluyendo: + +- **Crear ramas:** [Las *ramas*](/articles/creating-and-deleting-branches-within-your-repository/) te permiten diseñar nuevas características o probar ideas sin poner en riesgo tu proyecto principal. +- **Abrir solicitudes de extracción:** Si deseas colaborar con el repositorio original, puedes enviar una solicitud al autor original para extraer tu bifurcación en su repositorio enviando una [solicitud de extracción](/articles/about-pull-requests). + +### Encontrar otro repositorio para bifurcar + +Bifurca un repositorio para comenzar a colaborar con un proyecto. {% data reusables.repositories.you-can-fork %} + +{% if currentVersion == "free-pro-team@latest" %}Puedes buscar manualmente en [Explorar](https://github.com/explore) para encontrar proyectos y comenzar a colaborar con los repositorios de código abierto. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." + +{% endif %} + +### Celebrar + +Ahora ya has bifurcado un repositorio, has practicado la clonación de tu bifurcación y has configurado un repositorio ascendente. ¿Qué deseas hacer ahora? + +- "[Configurar Git](/articles/set-up-git)" +- "[Crear un repositorio](/articles/create-a-repo)" +- "[Socializar](/articles/be-social)" +- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md new file mode 100644 index 0000000000000..2d379f4308f12 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -0,0 +1,62 @@ +--- +title: Recursos de aprendizaje de Git y GitHub +redirect_from: + - /articles/good-resources-for-learning-git-and-github/ + - /articles/what-are-other-good-resources-for-learning-git-and-github/ + - /articles/git-and-github-learning-resources +intro: 'Hay muchos recursos útiles de Git y {% data variables.product.product_name %} disponibles en la web. La siguientes es una pequeña lista de nuestros favoritos.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +authors: + - GitHub +--- + +### Utilizar GitHub + +Para familiarizarte con Git, visita el [sitio oficial del proyecto Git](https://git-scm.com) y lee el [libro electrónico Progit](http://git-scm.com/book). Puedes revisar la [lista de comandos de Git](https://git-scm.com/docs) o la [referencia para buscar comandos de Git](http://gitref.org) mientras usas el simulador [Try Git](https://try.github.com). + +### Uso de {% data variables.product.product_name %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% data variables.product.prodname_learning %} ofrece cursos interactivos gratuitos integrados en {% data variables.product.prodname_dotcom %} con evaluación y asistencia instantáneas y automatizadas. Aprende a abrir tu primera solicitud de extracción, hacer tu primera contribución de código abierto, crear un sitio {% data variables.product.prodname_pages %}, y mucho más. Para obtener más información acerca de los cursos ofrecidos, consulta [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). + +{% endif %} + +Adquiere más conocimientos con {% data variables.product.product_name %} a través de nuestros artículos de [seminario intensivo](/categories/bootcamp/). Consulta nuestro [ flujo de {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow) para acceder a una introducción del proceso. Consulta nuestras [guías de descripción general](https://guides.github.com) para conocer nuestros conceptos básicos. + +{% data reusables.support.ask-and-answer-forum %} + +#### Ramas, bifurcaciones y solicitudes de extracción + +Conoce más sobre las [ramas de Git](http://learngitbranching.js.org/) usando una herramienta interactiva. Lee más acerca de [bifrucaciones](/articles/about-forks) y [solicitudes de extracción](/articles/using-pull-requests), además de [cómo usar las solicitudes de extracción](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) en {% data variables.product.prodname_dotcom %}. + +Accede a guías de referencia rápida acerca de la [línea de comando](https://hub.github.com) y de [guías de comprobación, hojas de referencia de {% data variables.product.prodname_dotcom %}, y mucho más](https://services.github.com/on-demand/resources). + +#### Ponte al día + +Nuestro {% data variables.product.prodname_dotcom %} [canal con guías y capacitación de YouTube](https://youtube.com/githubguides) ofrece tutoriales acerca de [solicitudes de extracción](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [ bifurcaciones](https://www.youtube.com/watch?v=5oJHRbqEofs), las funciones de [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) y [reinicio](https://www.youtube.com/watch?v=BKPjPMVB81g). Cada tema se cubre en menos de 5 minutos. + +### Capacitación + +#### Clases gratuitas + +{% data variables.product.product_name %} ofrece una serie de cursos de capacitación interactivos a pedido [on-demand training courses](https://services.github.com/on-demand/), entre otros, {% data variables.product.prodname_dotcom %} 101: [Introducción](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop) y {% data variables.product.prodname_dotcom %} 103: [Línea de comando](https://services.github.com/on-demand/github-cli). + +#### Programas educativos basados en la web de {% data variables.product.prodname_dotcom %} + +{% data variables.product.prodname_dotcom %} ofrece [capacitaciones](https://services.github.com/#upcoming-events) en vivo con un enfoque práctico basado en proyectos tanto para los amantes de la línea de comando como para quienes no están familiarizados con esta herramienta. + +#### Capacitación para tu compañía + +{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contáctanos](https://services.github.com/#contact) para que podamos responder tus preguntas relacionadas con la capacitación. + +### Extras + +Un [curso de Git en línea](http://www.codeschool.com/courses/git-real) interactivo de [Code School](http://codeschool.com) con siete niveles y muchos ejercicios en un formato amigable. Adapta libremente nuestras [plantillas .gitignore](https://github.com/github/gitignore) para que resuelvan tus necesidades. + +Extiende tu alcance de {% data variables.product.prodname_dotcom %} a través de las {% if currentVersion == "free-pro-team@latest" %}[integraciones](/articles/about-integrations){% else %}integraciones{% endif %}, o mediante la instalación de [{% data variables.product.prodname_desktop %}](https://desktop.github.com) y del robusto editor de texto de [Atom](https://atom.io). + +Descubre cómo lanzar y hacer crecer tu proyecto de código abierto con las [Guías de código abierto](https://opensource.guide/). diff --git a/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md b/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md new file mode 100644 index 0000000000000..cdea80d06154f --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md @@ -0,0 +1,13 @@ +--- +title: Hoja introductoria de Git +redirect_from: + - /articles/git-cheatsheet +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Aprender todos los comandos de Git disponibles de una sola vez puede resultan una tarea intimidante. Mantén uno de nuestras [Hojas introductorias de Git](https://services.github.com/on-demand/resources/cheatsheets/) cerca para poder consultarla. El uso de Hojas introductorias de Git se encuentra disponible en distintos idiomas. Para obtener más información, consulta la [página de recursos en el sitio web GitHub Services](https://services.github.com/on-demand/resources/). + +Además, visita nuestra página de [recursos para el aprendizaje de Git y GitHub](/articles/git-and-github-learning-resources/), que tiene enlaces a guías, videos, y mucho más. diff --git a/translations/es-ES/content/github/getting-started-with-github/github-cli.md b/translations/es-ES/content/github/getting-started-with-github/github-cli.md new file mode 100644 index 0000000000000..e0580becfdc0a --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/github-cli.md @@ -0,0 +1,29 @@ +--- +title: CLI de GitHub +intro: 'El {% data variables.product.prodname_cli %} es una herramienta de línea de comandos para utilizar las características de {% data variables.product.product_name %} en tu computadora.' +versions: + free-pro-team: '*' + enterprise-server: '>2.19' + github-ae: '*' +--- + +### Acerca de {% data variables.product.prodname_cli %} + +{% data variables.product.prodname_cli %} es una herramienta de código abierto para utilizar {% data variables.product.product_name %} desde la línea de comandos de tu computadora. Cuando trabajas desde la línea de comandos, puedes utilizar el {% data variables.product.prodname_cli %} para ahorrar tiempo y evitar cambiar de contexto. + +Puedes utilizar las siguientes características de {% data variables.product.prodname_dotcom %} con el {% data variables.product.prodname_cli %}. + +- Ver, crear, clonar, y bifurcar repositorios +- Crear, cerrar y listar propuestas y solicitudes de cambios +- Revisar, fusionar y hacer diffs con las solicitudes de cambios +- Crear, editar, listar y ver gists + +Para obtener más información acerca de lo que puedes hacer con {% data variables.product.prodname_cli %}, consulta el [{% data variables.product.prodname_cli %}manual](https://cli.github.com/manual). + +### Instalar {% data variables.product.prodname_cli %} + +Ver las instrucciones de instalación de {% data variables.product.prodname_cli %} para MacOS, Windows y Linux en la [{% data variables.product.prodname_cli %}página](https://cli.github.com). + +### Compartir retroalimentación + +Si tienes retroalimentación o solicitudes de características, puedes abrir un informe de problemas en el [repositorio `cli/cli`](https://github.com/cli/cli). diff --git a/translations/es-ES/content/github/getting-started-with-github/github-desktop.md b/translations/es-ES/content/github/getting-started-with-github/github-desktop.md new file mode 100644 index 0000000000000..b3d1a578a3f5a --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/github-desktop.md @@ -0,0 +1,18 @@ +--- +title: GitHub Desktop +intro: '{% data variables.product.prodname_desktop %} extiende y simplifica el flujo de trabajo de tu Git y tu {% data variables.product.prodname_dotcom %} utilizando una interface visual.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de {% data variables.product.prodname_desktop %} + +{% data reusables.desktop.about-github-desktop %} + +Para obtener información acerca de {% data variables.product.prodname_desktop %}, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop)" en la documentación de {% data variables.product.prodname_desktop %}. + +### Compartir retroalimentación + +Si tienes retroalimentación o solicitudes de características, puedes abrir un informe de problema en el [repositorio `desktop/desktop`](https://github.com/desktop/desktop). diff --git a/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md new file mode 100644 index 0000000000000..ac16c891172b8 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md @@ -0,0 +1,85 @@ +--- +title: GitHub para móviles +intro: 'Clasifica, colabora y administra tu trabajo en {% data variables.product.product_name %} desde tu dispositivo móvil.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.mobile.ghes-release-phase %} + +### Acerca de {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} + +{% data variables.product.prodname_mobile %} te proporciona una manera de realizar trabajo de alto impacto en {% data variables.product.product_name %} de forma rápida y desde cualquier lugar. {% data variables.product.prodname_mobile %} es una manera segura y estable de acceder a tus datos de {% data variables.product.product_name %} a través de una aplicación cliente confiable de primera parte. + +Con {% data variables.product.prodname_mobile %} puedes: +- Administrar, clasificar y borrar las notificaciones +- Leer, revisar y colaborar en informes de problemas y solicitudes de extracción +- Buscar, navegar e interactuar con usuarios, repositorios y organizaciones +- Recibir notificaciones para subir información cuando alguien menciona tu nombre de usuario + +Para obtener más información sobre las notificaciones de {% data variables.product.prodname_mobile %}, consulta "[Configurando notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." + +### Instalar {% data variables.product.prodname_mobile %} + +Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, consulta la sección [{% data variables.product.prodname_mobile %}](https://github.com/mobile). + +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### Prerrequisitos + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + +### Idiomas compatibles para {% data variables.product.prodname_mobile %} + +{% data variables.product.prodname_mobile %} se encuentra disponible en los siguientes idiomas. + +- Inglés +- Japonés +- Portugués brasileño +- Simplified Chinese +- Español + +Si configuras el idioma en tu dispositivo para que sea uno de los compatibles, {% data variables.product.prodname_mobile %} estará predeterminadamente en este idioma. Puedes cambiar el idioma de {% data variables.product.prodname_mobile %} en el menú de **Ajustes** de {% data variables.product.prodname_mobile %}. + +### Administrar Enlaces Universales para {% data variables.product.prodname_mobile %} en iOS + +{% data variables.product.prodname_mobile %} habilita automáticamente los Enlaces Universales para iOS. Cuando tocas en cualquier enlace de {% data variables.product.product_name %}, la URL destino se abrirá en {% data variables.product.prodname_mobile %} en vez de en Safari. Para obtener más información, consulta la sección[Enlaces Universales](https://developer.apple.com/ios/universal-links/) en el sitio para Desarrolladores de Apple. + +Para inhabilitar los Enlaces Universales, presiona sostenidamente cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir**. Cada vez que toques en un enlace de {% data variables.product.product_name %} posteriormente, la URL destino se abrirá en Safari en vez de en {% data variables.product.prodname_mobile %}. + +Para volver a habilitar los Enlaces Universales, sostén cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir en {% data variables.product.prodname_dotcom %}**. + +### Compartir retroalimentación + +Si encuentras un error en {% data variables.product.prodname_mobile %}, puedes mandarnos un mensaje de correo electrónico a mobilefeedback@github.com. + +Puedes emitir solicitudes de características u otro tipo de retroalimentación para {% data variables.product.prodname_mobile %}[en los debates de GitHub](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). + +### Abandonar los lanzamientos beta para iOS + +Si estás probando un lanzamiento beta de {% data variables.product.prodname_mobile %} para iOS utilizando TestFlight, puedes abandonar el beta en cualquier momento. + +1. En tu dispositivo iOS, abre la aplicación de TestFlight. +2. Debajo de "Apps", toca en **{% data variables.product.prodname_dotcom %}**. +3. En la parte inferior de la página, toca en **Dejar de Probar**. diff --git a/translations/es-ES/content/github/getting-started-with-github/github-glossary.md b/translations/es-ES/content/github/getting-started-with-github/github-glossary.md new file mode 100644 index 0000000000000..1ae3e191da166 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/github-glossary.md @@ -0,0 +1,24 @@ +--- +title: Glosario de GitHub +intro: 'A continuación aparece una lista de algunos términos específicos de Git y {% data variables.product.prodname_dotcom %} que usamos en nuestros sitios y en la documentación.' +redirect_from: + - /articles/github-glossary +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% for term in site.data.glossaries.external %} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} + --- +{% endfor %} + +--- + +### Further reading + +- [El glosario oficial de Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) +- [Referencia de Git](http://gitref.org/) +- [SCM de Git](https://git-scm.com/doc) diff --git a/translations/es-ES/content/github/getting-started-with-github/githubs-products.md b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md new file mode 100644 index 0000000000000..86806372cf891 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md @@ -0,0 +1,104 @@ +--- +title: Productos de GitHub +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' +redirect_from: + - /articles/github-s-products + - /articles/githubs-products +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data variables.product.prodname_dotcom %} ofrece productos gratuitos y pagos. Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} + +### {% data variables.product.prodname_free_user %} for user accounts + +Con {% data variables.product.prodname_free_team %} para cuentas de usuario, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, y en repositorios privados ilimitados con un conjunto limitado de características. + +Con {% data variables.product.prodname_free_user %}, tu cuenta de usuario incluye: +- {% data variables.product.prodname_gcf %} +- {% data variables.product.prodname_dependabot_alerts %} +- Aplicación de la autenticación de dos factores +- 2,000 minutos de {% data variables.product.prodname_actions %} +- 500MB de almacenamiento de {% data variables.product.prodname_registry %} + +### {% data variables.product.prodname_pro %} + +Adicionalmente a las características disponibles con {% data variables.product.prodname_free_user %} para cuentas de usuario, {% data variables.product.prodname_pro %} incluye: +- {% data variables.contact.github_support %} por correo electrónico +- 3,000 minutos de {% data variables.product.prodname_actions %} +- 2GB de almacenamiento de {% data variables.product.prodname_registry %} +- Herramientas y perspectivas avanzadas en repositorios privados: + - Revisores requeridos para solicitudes de extracción + - Revisores múltiples para solicitudes de extracción + - Referencias auto-vinculadas + - {% data variables.product.prodname_pages %} + - Wikis + - Ramas protegidas + - Propietarios del código + - Gráficos de información del repositorio: pulso, contribuyentes, tráfico, confirmaciones, frecuencia de código, red y bifurcaciones + +### {% data variables.product.prodname_free_team %} para organizaciones + +Con {% data variables.product.prodname_free_team %} para organizaciones, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, o en repositorios privados ilimitados con un conjunto limitado de características. + +Adicionalmente a las características disponibles con {% data variables.product.prodname_free_user %} para cuentas de usuario, {% data variables.product.prodname_free_team %} para organizaciones incluye: +- {% data variables.product.prodname_gcf %} +- Debates de equipo +- Controles de acceso del equipo para administrar grupos +- 2,000 minutos de {% data variables.product.prodname_actions %} +- 500MB de almacenamiento de {% data variables.product.prodname_registry %} + +### {% data variables.product.prodname_team %} + +Adicionalmente a las características disponibles con {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %} incluye: +- {% data variables.contact.github_support %} por correo electrónico +- 3,000 minutos de {% data variables.product.prodname_actions %} +- 2GB de almacenamiento de {% data variables.product.prodname_registry %} +- Herramientas y perspectivas avanzadas en repositorios privados: + - Revisores requeridos para solicitudes de extracción + - Revisores múltiples para solicitudes de extracción + - {% data variables.product.prodname_pages %} + - Wikis + - Ramas protegidas + - Propietarios del código + - Gráficos de información del repositorio: pulso, contribuyentes, tráfico, confirmaciones, frecuencia de código, red y bifurcaciones + - Solicitudes de extracción en borrador + - Revisores de equipo para solicitudes de extracción + - Recordatorios programados + +{% data reusables.github-actions.actions-billing %} + +### {% data variables.product.prodname_enterprise %} + +{% data variables.product.prodname_enterprise %} incluye dos opciones de despliegue: hospedado en la nuba y auto-hospedado. + +Adicionalmente a las características disponibles con {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} incluye: +- {% data variables.contact.enterprise_support %} +- Controles de seguridad, cumplimiento e implementación adicionales +- Autenticación con inicio de sesión único SAML +- Provisión de acceso con SAML o SCIM +- {% data variables.product.prodname_github_connect %} + +{% data variables.product.prodname_ghe_cloud %} también incluye lo siguiente: +- {% data variables.contact.enterprise_support %}. Para obtener más información, consulta "{% data variables.product.prodname_ghe_cloud %} soporte" y "{% data variables.product.prodname_ghe_cloud %} Adenda." +- 50,000 minutos de {% data variables.product.prodname_actions %} +- 50GB de almacenamiento de {% data variables.product.prodname_registry %} +- Un acuerdo de nivel de servicio del 99.9% de tiempo activo mensual +- La opción de administrar de forma centralizada las políticas y la facturación de múltiples organizaciones {% data variables.product.prodname_dotcom_the_website %} con una cuenta de empresa. Para obtener más información, consulta la sección "Acerca de las cuentas empresariales." + +Puedes configurar una prueba para evaluar {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}". + +Para obtener más información acerca de hospedar tu propia instancia de [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contacta a {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %} + +### {% data variables.product.prodname_ghe_one %} + +{% data variables.product.prodname_ghe_one %} incluye [{% data variables.product.prodname_enterprise %}](#github-enterprise), mas: + +- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} +- {% data variables.product.prodname_insights %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} +- [{% data variables.product.prodname_learning %} para organizaciones](https://lab.github.com/organizations) + +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/es-ES/content/github/getting-started-with-github/index.md b/translations/es-ES/content/github/getting-started-with-github/index.md new file mode 100644 index 0000000000000..5b6ad2c0d8637 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/index.md @@ -0,0 +1,54 @@ +--- +title: Comenzar con GitHub +shortTitle: Empezar +intro: 'Aprende sobre los productos de {% data variables.product.prodname_dotcom %}, regístrate para obtener una cuenta y explora la comunidad {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /categories/54/articles/ + - /categories/bootcamp/ + - /categories/32/articles/ + - /categories/2/articles/ + - /categories/organizations/ + - /categories/about-github/ + - /categories/53/articles/ + - /categories/setup/ + - /categories/getting-started-with-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /quickstart %} + {% link_in_list /set-up-git %} + {% link_in_list /create-a-repo %} + {% link_in_list /fork-a-repo %} + {% link_in_list /be-social %} +{% topic_link_in_list /learning-about-github %} + {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} + {% link_in_list /exploring-early-access-releases-with-feature-preview %} + {% link_in_list /types-of-github-accounts %} + {% link_in_list /faq-about-changes-to-githubs-plans %} + {% link_in_list /github-cli %} + {% link_in_list /github-desktop %} + {% link_in_list /github-for-mobile %} + {% link_in_list /access-permissions-on-github %} + {% link_in_list /github-glossary %} + {% link_in_list /git-cheatsheet %} + {% link_in_list /git-and-github-learning-resources %} +{% topic_link_in_list /signing-up-for-github %} + {% link_in_list /signing-up-for-a-new-github-account %} + {% link_in_list /verifying-your-email-address %} + {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} + {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} +{% topic_link_in_list /exploring-projects-on-github %} + {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} + {% link_in_list /saving-repositories-with-stars %} + {% link_in_list /following-people %} +{% topic_link_in_list /using-github %} + {% link_in_list /supported-browsers %} + {% link_in_list /troubleshooting-connectivity-problems %} + {% link_in_list /keyboard-shortcuts %} diff --git a/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md new file mode 100644 index 0000000000000..93afec0bbac08 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -0,0 +1,197 @@ +--- +title: Atajos del teclado +intro: 'Prácticamente todas las páginas de {% data variables.product.product_name %} tienen atajos del teclado para realizar acciones más rápido.' +redirect_from: + - /articles/using-keyboard-shortcuts/ + - /categories/75/articles/ + - /categories/keyboard-shortcuts/ + - /articles/keyboard-shortcuts +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Acerca de los atajos del teclado + +Escribir ? en {% data variables.product.product_name %} genera un cuadro de diálogo que detalla los atajos del teclado disponibles para esa página. Puedes aprovechar estos atajos del teclado para realizar acciones en todo el sitio sin recurrir al mouse para navegar. + +A continuación aparece una lista de algunos de los atajos del teclado disponibles. + +### Atajos en todo el sitio + +| Atajo del teclado | Descripción | +| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s o / | Se concentra en la barra de búsqueda. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". | +| g n | Dirige a tus notificaciones. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". | +| esc | Cuando se concentra en la hovercard de un usuario, de una propuesta o de una solicitud de extracción, se cierra la hovercard y se vuelve a centrar en el elemento en el que está la hovercard | + +### Repositorios + +| Atajo del teclado | Descripción | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| g c | Dirige a la pestaña **Code** (Código) | +| g i | Dirige a la pestaña **Issues** (Propuestas). Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". | +| g p | Dirige a la pestaña **Pull requests** (Solicitudes de extracción). Para obtener más información, consulta la sección "[Acerca de las solicitudes de cambios](/articles/about-pull-requests)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| g a | Ve a la pestaña de **Acciones**. Para obtener más información, consulta la sección "[Acerca de las acciones](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %} +| g b | Dirige a la pestaña **Projects** (Proyectos). Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)." | +| g w | Dirige a la pestaña **Wiki**. Para obtener más información, consulta "[Acerca de las wikis](/articles/about-wikis)". | + +### Edición del código fuente + +| Atajo del teclado | Descripción | +| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | +| e | Abre el archivo de código fuente en la pestaña **Editar archivo** | +| control f o comando f | Comienza la búsqueda en el editor de archivos | +| control g o comando g | Busca el siguiente | +| shift control g o shift comando g | Busca el anterior | +| shift control f o opción de comando f | Reemplaza | +| shift control r o shift opción de comando f | Reemplaza todo | +| alt g | Salta la línea | +| control z o comando z | Deshace | +| control y o comando y | Rehace | +| cmd + shift + p | Alterna entre las pestañas **Edit file** (Editar comentario) y **Preview changes** (Vista previa de cambios) | + +Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands). + +### Exploración del código fuente + +| Atajo del teclado | Descripción | +| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| t | Activa el buscador de archivos | +| l | Salta a una línea de tu código | +| w | Cambia a una rama o etiqueta nueva | +| y | Expande una URL a su forma canónica. Para obtener más información, consulta "[Obtener enlaces permanentes a los archivos](/articles/getting-permanent-links-to-files)". | +| i | Muestra u oculta comentarios en diferencias. Para obtener más información, consulta "[Comentar en la diferencia de una solicitud de extracción](/articles/commenting-on-the-diff-of-a-pull-request)". | +| b | Abre la visualización del último responsable. Para obtener más información, consulta "[Rastrear las modificaciones de un archivo](/articles/tracing-changes-in-a-file)". | + +### Comentarios + +| Atajo del teclado | Descripción | +| ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| control b o comando b | Inserta el formato Markdown para el texto en negrita | +| control i o comando i | Inserta el formato Markdown para el texto en cursiva | +| control k o comando k | Inserta el formato Markdown para crear un enlace | +| control shift p o comando shift p | Alterna entre las pestañas de comentarios **Write** (Escribir) y **Preview** (Vista previa) | +| control enter | Envía un comentario | +| control . y luego control [número de respuesta guardada] | Abre el menú de respuestas guardadas y luego completa automáticamente el campo de comentarios con una respuesta guardada. Para obtener más información, consulta la sección "[Acerca de las respuestas guardadas](/articles/about-saved-replies)".{% if currentVersion == "free-pro-team@latest" %} +| control g o comando g | Inserta una sugerencia. Para obtener más información, consulta "[Revisar las modificaciones propuestas en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} +| r | Cita el texto seleccionado en tu respuesta. Para obtener más información, consulta "[Escritura básica y sintaxis de formato](/articles/basic-writing-and-formatting-syntax#quoting-text)". | + +### Listas de propuestas y solicitudes de extracción + +| Atajo del teclado | Descripción | +| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| c | Crear un informe de problemas | +| control / o comando / | Hace que el cursor se concentre en la barra de propuestas o solicitudes de respuesta. Para obtener más información, consulta "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)".| | +| u | Filtra por autor | +| l | Filtra por etiquetas o edita etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| alt y haz clic | Al filtrar por etiquetas, excluye etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| m | Filtra por hitos o edita hitos. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por hito](/articles/filtering-issues-and-pull-requests-by-milestone)". | +| a | Filtra por asignatario s o edita asignatarios. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)". | +| o o enter | Abre una propuesta | + +### Propuestas y solicitudes de extracción +| Atajo del teclado | Descripción | +| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| q | Solicita un revisor. Para obtener más información, consulta "[Solicitar una revisión de solicitud de extracción](/articles/requesting-a-pull-request-review/)". | +| m | Establece un hito. Para obtener más información, consulta "[Asociar hitos a propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests/)". | +| l | Aplica una etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests/)". | +| a | Establece un asignatario. Para obtener más información, consulta "[Asignar propuestas y solicitudes de extracción a otros{% data variables.product.company_short %} usuarios](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | +| cmd + shift + p or control + shift + p | Alterna entre las pestañas **Write** (Escribir) y **Preview** (Vista previa) | + +### Modificaciones en las solicitudes de extracción + +| Atajo del teclado | Descripción | +| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Abre la lista de confirmaciones de la solicitud de extracción | +| t | Abre la lista de archivos modificados de la solicitud de extracción | +| j | Mueve la selección hacia abajo en la lista | +| k | Mueve la selección hacia arriba en la lista | +| cmd + shift + enter | Agrega un comentario simple en una diferencia de solicitud de extracción | +| alt y haz clic | Alterna entre colapsar y expandir todos los comentarios de revisión desactualizados en una solicitud de cambios presionando `alt` y dando clic en **Mostrar desactualizados** U **Ocultar.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} desactualizados** | +| Da clic, luego shift y clic | Comenta en líneas múltiples de una solicitud de extracción dando clic en un número de línea, sosteniendo shift, y luego dando clic en otro número de línea. Para obtener más información, consulta "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} + +### Tableros de proyecto + +#### Mover una columna + +| Atajo del teclado | Descripción | +| ------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | +| enter o space | Comienza a mover la columna enfocada | +| escape | Cancela el movimiento en curso | +| enter | Completa el movimiento en curso | +| ← o h | Mueve la columna hacia la izquierda | +| command + ← o command + h o control + ← o control + h | Mueve la columna hacia la posición más a la izquierda | +| → o l | Mueve la columna hacia la derecha | +| command + → o command + l o control + → o control + l | Mueve la columna hacia la posición más a la derecha | + +#### Mover una tarjeta + +| Atajo del teclado | Descripción | +| --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | +| enter o space | Comienza a mover la tarjeta focalizada | +| escape | Cancela el movimiento en curso | +| enter | Completa el movimiento en curso | +| ↓ o j | Mueve la tarjeta hacia abajo | +| command + ↓ o command + j o control + ↓ o control + j | Mueve una tarjeta hacia la parte de abajo de la columna | +| ↑ o k | Mueve una tarjeta hacia arriba | +| command + ↑ o command + k o control + ↑ o control + k | Mueve una tarjeta hacia la parte de arriba de la columna | +| ← o h | Mueve una tarjeta hacia la parte de abajo de la columna de la izquierda | +| shift + ← o shift + h | Mueve una tarjeta hacia la parte de arriba de la columna de la izquierda | +| command + ← o command + h o control + ← o control + h | Mueve una tarjeta hacia la parte de abajo de la columna de más a la izquierda | +| command + shift + ← o command + shift + h o control + shift + ← o control + shift + h | Mueve una tarjeta hacia la parte de arriba de la columna de más a la izquierda | +| → | Mueve una tarjeta hacia la parte de abajo de la columna de la derecha | +| shift + → o shift + l | Mueve una tarjeta hacia la parte de arriba de la columna de la derecha | +| command + → o command + l o control + → o control + l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | +| command + shift + → o command + shift + l o control + shift + → o control + shift + l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | + +#### Previsualizar una tarjeta + +| Atajo del teclado | Descripción | +| ----------------- | -------------------------------------------- | +| esc | Elige el panel de vista previa de la tarjeta | + +{% if currentVersion == "free-pro-team@latest" %} +### {% data variables.product.prodname_actions %} + +| Atajo del teclado | Descripción | +| -------------------------------------------------------- | --------------------------------------------------------------------------------------------- | +| command + space o control + space | En el editor del flujo de trabajo, obtén las sugerencias para tu archivo de flujo de trabajo. | +| g f | Go to the workflow file | +| shift + t or T | Toggle timestamps in logs | +| shift + f or F | Toggle fullscreen logs | +| esc | Exit fullscreen logs | + +{% endif %} + +### Notificaciones +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| Atajo del teclado | Descripción | +| -------------------- | ---------------------- | +| e | Marcar como completado | +| shift + u | Marcar como no leído | +| shift + i | Marca como leído | +| shift + m | Unsubscribe | + +{% else %} + +| Atajo del teclado | Descripción | +| ------------------------------------------ | ---------------- | +| e o I o y | Marca como leído | +| shift + m | Silencia el hilo | +{% endif %} + +### Network graph + +| Atajo del teclado | Descripción | +| ------------------------------------------- | -------------------------------- | +| ← o h | Desplaza hacia la izquierda | +| → o l | Desplaza hacia la derecha | +| ↑ o k | Desplaza hacia arriba | +| ↓ o j | Desplaza hacia abajo | +| shift + ← o shift + h | Desplaza todo hacia la izquierda | +| shift + → o shift + l | Desplaza todo hacia la derecha | +| shift + ↑ o shift + k | Desplaza todo hacia arriba | +| shift + ↓ o shift + j | Desplaza todo hacia abajo | diff --git a/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md new file mode 100644 index 0000000000000..08c5c88efeaaf --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md @@ -0,0 +1,12 @@ +--- +title: Obtener información sobre GitHub +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/learning-about-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/getting-started-with-github/quickstart.md b/translations/es-ES/content/github/getting-started-with-github/quickstart.md new file mode 100644 index 0000000000000..178b837936ff6 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/quickstart.md @@ -0,0 +1,10 @@ +--- +title: Inicio Rápido +intro: 'Inicia rápidamente las tareas comunes en {% data variables.product.prodname_dotcom %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md b/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md new file mode 100644 index 0000000000000..8153d59dc0f30 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md @@ -0,0 +1,53 @@ +--- +title: Guardar repositorios con estrellas +intro: 'Puedes marcar los repositorios y temas como favoritos para llevar el seguimiento de los proyectos que te parezcan interesantes{% if currentVersion == "free-pro-team@latest" %} y descubrir el contenido relacionado en tu sección de noticias{% endif %}.' +redirect_from: + - /articles/stars/ + - /articles/about-stars/ + - /articles/browsing-friends-stars/ + - /articles/managing-your-stars/ + - /articles/saving-repositories-with-stars +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar, clasificar y filtrar tus repositorios y temas marcados con estrella en tu {% data variables.explore.your_stars_page %}.' + +### Acerca de las estrellas + +Marcar con estrellas tus repositorios y temas favoritos te facilitará encontrarlos posteriormente. Puedes ver todos los repositorios y temas que has marcado con estrellas visitando tu {% data variables.explore.your_stars_page %}. + +{% if currentVersion == "free-pro-team@latest" %} +Puedes marcar los repositorios y temas como favoritos para descubrir proyectos similares en +{% data variables.product.product_name %}. Cuando marcas repositorios o temas con estrellas, {% data variables.product.product_name %} puede recomendar contenido relacionado en la vista de tus noticias. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." +{% endif %} + +Marcar un repositorio con estrella también muestra reconocimiento al mantenedor del repositorio por su trabajo. Muchas de las clasificaciones de los repositorios de {% data variables.product.prodname_dotcom %} dependen de la cantidad de estrellas que tiene un repositorio. Además, [Explore](https://github.com/explore) muestra repositorios populares en base a la cantidad de estrellas que tienen. + +### Buscar estrellas + +![Buscar a través de las estrellas](/assets/images/help/stars/stars_search_bar.png) + +Puedes utilizar la barra de búsqueda para encontrar rápidamente los repositorios y temas que has marcado con estrella. La barra de búsqueda únicamente busca en los nombres de los temas y repositorios, y no en cualquier otro calificador (tal como el tamaño del repositorio o la fecha en la que se actualizó la última vez). + +### Clasificar y filtrar estrellas + +![Clasificar estrellas](/assets/images/help/stars/stars_sort_menu.png) + +En la esquina superior derecha de tu página de marcados con estrella, puedes clasificar los repositorios y temas marcados con las categorías de "recientemente marcado con estrella", "recientemente activo" y "más estrellas". + +En el lateral derecho de la página, puedes filtrar tu lista de repositorios con estrellas en base a su lenguaje. + +![Filtrar estrellas por lenguaje](/assets/images/help/stars/stars_filter_language.png) + +### Explorar las estrellas de tus amigos + + En el ángulo inferior derecho de la página, puedes explorar las estrellas de tus amigos. Puedes utilizar esto para encontrar repositorios nuevos y temas para marcar como favoritos. + +![Ver las estrellas de tus amigos](/assets/images/help/stars/stars_jump_to_a_friend.png) + +### Further reading + +- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/github/getting-started-with-github/set-up-git.md b/translations/es-ES/content/github/getting-started-with-github/set-up-git.md new file mode 100644 index 0000000000000..0f202adc10fd3 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/set-up-git.md @@ -0,0 +1,57 @@ +--- +title: Configurar Git +redirect_from: + - /git-installation-redirect/ + - /linux-git-installation/ + - /linux-set-up-git/ + - /mac-git-installation/ + - /mac-set-up-git/ + - /set-up-git-redirect/ + - /win-git-installation/ + - /win-set-up-git/ + - /articles/set-up-git +intro: 'En el centro de {% data variables.product.product_name %} hay un sistema de control de versión de código abierto (VCS) llamado Git. Git es responsable de todo lo relacionado con {% data variables.product.product_name %} que suceda de forma local en tu computadora.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} También puedes instalar {% data variables.product.prodname_cli %} para utilizar {% data variables.product.product_name %} desde la línea de comandos. Para obtener más información sobre {% data variables.product.prodname_cli %}, consulta la [documentación de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/).{% endif %} + +Si deseas trabajar con Git de forma local, pero no deseas utilizar la línea de comando, puedes descargar e instalar en su lugar el cliente [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obtener más información, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". + +Si no deseas trabajar con archivos de forma local, {% data variables.product.product_name %} te permite realizar muchas acciones relacionadas con Git de forma directa en el navegador, lo que incluye: + +- [Crear un repositorio](/articles/create-a-repo) +- [Bifurcar un repositorio](/articles/fork-a-repo) +- [Administrar archivos](/articles/managing-files-on-github/) +- [Socializar](/articles/be-social) + +### Configurar Git + +1. [Descarga e instala la última versión de Git](https://git-scm.com/downloads). +2. [Configura tu nombre de usuario en Git](/articles/setting-your-username-in-git). +3. [Configura tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address). + +### Pasos siguientes: Autenticación con {% data variables.product.prodname_dotcom %} desde Git + +Cuando te conectas a un repositorio {% data variables.product.product_name %} desde Git, deberás autenticarte con {% data variables.product.product_name %} utilizando HTTPS o SSH. + +#### Conectar por HTTPS (recomendado) + +Si [clonas con HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), puedes [almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git) utilizando un asistente de credenciales. + +#### Conectar por SSH + +Si clonas [con SSH](/articles/which-remote-url-should-i-use#cloning-with-ssh-urls), debes [generar las claves de SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) en cada computadora que utilices para subir o extraer desde {% data variables.product.product_name %}. + +### Celebrar + +¡Felicitaciones, ahora tienes configurado todo Git y {% data variables.product.product_name %}! ¿Qué deseas hacer ahora? + +- **Configurar Git** +- "[Crear un repositorio](/articles/create-a-repo)" +- "[Bifurcar un repositorio](/articles/fork-a-repo)" +- "[Socializar](/articles/be-social)" +- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md new file mode 100644 index 0000000000000..aef4cfd77b11e --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -0,0 +1,60 @@ +--- +title: Configurar una prueba de la nube de GitHub Enterprise +intro: 'Puedes probar {% data variables.product.prodname_ghe_cloud %} de manera gratuita.' +redirect_from: + - /articles/setting-up-a-trial-of-github-enterprise-cloud +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de las pruebas de {% data variables.product.prodname_ghe_cloud %} + +Puedes configurar una prueba de 14 días para evaluar {% data variables.product.prodname_ghe_cloud %} en una cuenta nueva de organización. No es necesario que proporciones un método de pago durante la prueba a menos que agreges aplicaciones de {% data variables.product.prodname_marketplace %} en tu organización que requieran de un método de pago. Para obtener más información, consulta "Acerca de la facturación para {% data variables.product.prodname_marketplace %}". + +Tu prueba incluye 50 asientos. Si necesitas más plazas para evaluar a {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Al finalizar la prueba, puedes elegir una cantidad diferente de asientos. + +También hay pruebas disponibles para {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)". + +{% data reusables.products.which-product-to-use %} + +### Configurar tu prueba de {% data variables.product.prodname_ghe_cloud %} + +Antes de poder comenzar con tu prueba de {% data variables.product.prodname_ghe_cloud %}, debes tener una cuenta de usuario existente o crear una nueva cuenta de usuario. Para obtener más información, consulta "Iniciar sesión para una nueva cuenta de {% data variables.product.prodname_dotcom %}". + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. En "Enterprise", haz clic en **Iniciar tu prueba de 14 días**. ![Botón para iniciar tu prueba](/assets/images/help/organizations/start-trial-button.png) +5. Escribe tu nombre de empresa. ![Campo de nombre de empresa](/assets/images/help/organizations/company-name-field.png) +{% data reusables.organizations.organization-name %} +7. En "Nombre completo", escribe tu nombre completo. ![Campo nombre completo](/assets/images/help/organizations/full-name-field.png) +8. En "Correo electrónico laboral", escribe la dirección de correo electrónico que usas para trabajar. ![Campo correo electrónico laboral](/assets/images/help/organizations/work-email-field.png) +8. Usa el menú desplegable **Industria** y selecciona la industria a la que pertenece tu empresa. ![Menú desplegable Industria](/assets/images/help/organizations/industry-drop-down.png) +9. Usa el menú desplegable **Cantidad de empleados** y selecciona la cantidad de empleados de tu empresa. ![Menú desplegable Cantidad de empleados](/assets/images/help/organizations/employees-drop-down.png) +10. Revisa el Acuerdo de licencia de evaluación, luego haz clic en **Next** (Siguiente). + +### Explorar {% data variables.product.prodname_ghe_cloud %} + +Una vez configurada tu prueba de 15 días, puedes explorar {% data variables.product.prodname_ghe_cloud %} siguiendo la [Guía de incorporación de empresas](https://resources.github.com/enterprise-onboarding/). + +{% data reusables.products.product-roadmap %} + +### Finalizar tu prueba + +Puedes comprar {% data variables.product.prodname_enterprise %} o bajar de categoría a {% data variables.product.prodname_team %} en cualquier momento durante tu prueba. + +Si no compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %} antes de que termine tu periodo de prueba, tu organización bajará a {% data variables.product.prodname_free_team %} y perderá acceso a cualquier tipo de herramienta o características que solo se incluya en los productos pagados, incluyendo a los sitios de {% data variables.product.prodname_pages %} que se publican desde esos repositorios privados. Si no planeas mejorar tu plan, para evitar perder acceso a estas características avanzadas, haz públicos los repositorios antes de que termine tu periodo de prueba. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". + +El bajar de categoría a {% data variables.product.prodname_free_team %} en organizaciones también inhabilita cualquier configuración de SAML durante el periodo de prueba. Una vez que compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %}, tus parámetros de SAML serán activados nuevamente para que los usuarios de tu organización los autentiquen. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Debajo de "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Prueba gratis de {% data variables.product.prodname_ghe_cloud %}), haz clic en **Buy Enterprise** (Comprar empresa) o **Downgrade to Team** (Bajar de categoría a equipo). ![Botones Comprar Enterprise y Bajar de categoría a Team](/assets/images/help/organizations/finish-trial-buttons.png) +6. Sigue las indicaciones para ingresar tu método de pago, a continuación haz clic en **Enviar**. + +### Further reading + +- "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" diff --git a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md new file mode 100644 index 0000000000000..ba4ee7122c1dc --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md @@ -0,0 +1,61 @@ +--- +title: Configurar una prueba del servidor de GitHub Enterprise +intro: 'Puedes probar {% data variables.product.prodname_ghe_server %} de manera gratuita.' +redirect_from: + - /articles/requesting-a-trial-of-github-enterprise/ + - /articles/setting-up-a-trial-of-github-enterprise-server +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de las pruebas de {% data variables.product.prodname_ghe_server %} + +Puedes solicitar una prueba de 45 días para evaluar {% data variables.product.prodname_ghe_server %}. La prueba se instalará a modo de aparato virtual, con opciones para la implementación en el entorno local o en la nube. Para acceder a una lista de plataformas de visualización compatibles, consulta "[Configurar un servidor de GitHub Enterprise](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Las alertas de{% else %}Seguridad{% endif %} del {% data variables.product.prodname_dependabot %} y de{% data variables.product.prodname_github_connect %} no están actualmente disponibles durante las pruebas de {% data variables.product.prodname_ghe_server %}. Para obtener una demostración de estas características, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información acerca de estas características, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Conectar el {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". + +También hay pruebas disponibles para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)". + +{% data reusables.products.which-product-to-use %} + +### Configurar tu prueba de {% data variables.product.prodname_ghe_server %} + +{% data variables.product.prodname_ghe_server %} está instalado como aparato virtual. Determina la mejor persona de tu organización para configurar una máquina virtual y pídele que envíe una [solicitud de prueba](https://enterprise.github.com/trial). Puedes comenzar tu prueba de forma inmediata después de enviar una solicitud. + +Para configurar una cuenta para el {% data variables.product.prodname_enterprise %} portal web, haz clic en el enlace del correo electrónico que recibiste después de enviar tu solicitud de prueba y sigue las instrucciones. A continuación, descarga tu archivo de licencia. Para obtener más información, consulta "[Administrar tu licencia {% data variables.product.prodname_enterprise %}](/enterprise/admin/installation/managing-your-github-enterprise-license)". + +Para instalar {% data variables.product.prodname_ghe_server %}, descarga los elementos necesarios y carga tu archivo de licencia. Para obtener más información, consulta las instrucciones para tu plataforma de visualización elegida en "[Configurar una {% data variables.product.prodname_ghe_server %} instancia](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". + +### Pasos siguientes + +Para sacar el mejor provecho de tu prueba, sigue los siguientes pasos: + +1. [Crear una organización](/enterprise/admin/user-management/creating-organizations). +2. Para aprender lo básico para usar {% data variables.product.prodname_dotcom %}, consulta lo siguiente: + - [Guía de iniciación rápida a {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast + - [Comprender el {% data variables.product.prodname_dotcom %} flujo](https://guides.github.com/introduction/flow/) en {% data variables.product.prodname_dotcom %} Guías + - [Hola, mundo](https://guides.github.com/activities/hello-world/) en {% data variables.product.prodname_dotcom %} Guides +3. Para configurar tu instancia a fin de que satisfaga las necesidades de tu organización, consulta la sección "[Configurar tu empresa](/enterprise/admin/configuration/configuring-your-enterprise)". +4. Para integrar {% data variables.product.prodname_ghe_server %} con tu proveedor de identidad, consulta "[Utilizar SAML](/enterprise/admin/user-management/using-saml)" y "[Utilizar LDAP](/enterprise/admin/authentication/using-ldap)" +5. Invita a una cantidad ilimitada de personas a unirse a tu prueba. + - Agregar usuarios a tu instancia {% data variables.product.prodname_ghe_server %} utilizando la autenticación incorporada o tu proveedor de identidad configurado. Para obtener más información, consulta "[Utilizar la autenticación incorporada](/enterprise/admin/user-management/using-built-in-authentication)". + - Para invitar a personas a que se conviertan en administradores de cuenta, visita el [{% data variables.product.prodname_enterprise %} portal web](https://enterprise.github.com/login). + + {% note %} + + **Nota::** Las personas que invites para que sean administradores de cuenta recibirán un correo electrónico con un enlace para aceptar tu invitación. + + {% endnote %} + +{% data reusables.products.product-roadmap %} + +### Finalizar tu prueba + +Puedes subir la categoría a licencias totales en el [{% data variables.product.prodname_enterprise %} portal web](https://enterprise.github.com/login) en cualquier momento durante el período de prueba. + +Si no has subido la categoría para el último día de tu prueba, recibirás un correo electrónico notificando que tu prueba ha terminado. Si necesitas más tiempo para evaluar {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión. + +### Further reading + +- "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)" diff --git a/translations/es-ES/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md new file mode 100644 index 0000000000000..da353cd686b48 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -0,0 +1,22 @@ +--- +title: Registrar una nueva cuenta GitHub +shortTitle: Registrarse para una cuenta nueva de GitHub +intro: '{% data variables.product.product_name %} ofrece cuentas de usuario para personas y organizaciones para equipos de personas que trabajan juntas.' +redirect_from: + - /articles/signing-up-for-a-new-github-account +versions: + free-pro-team: '*' +--- + +Para obtener más información sobre tipos de cuentas y productos, consulta "[Tipos de cuentas {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" y productos de "[{% data variables.product.product_name %}](/articles/github-s-products)." + +{% data reusables.accounts.create-account %} +1. Sigue las indicaciones para crear tu cuenta personal o de organización. + +### Pasos siguientes + +- [Verifica tus dirección de correo electrónico](/articles/verifying-your-email-address)" +- [Configura autenticación de dos factores](/articles/configuring-two-factor-authentication)" +- [Agrega una biografía a tu perfil](/articles/adding-a-bio-to-your-profile)" +- "[Crea una organización](/articles/creating-a-new-organization-from-scratch)" +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md new file mode 100644 index 0000000000000..fde568c151736 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md @@ -0,0 +1,12 @@ +--- +title: Registrarse en GitHub +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/signing-up-for-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/getting-started-with-github/supported-browsers.md b/translations/es-ES/content/github/getting-started-with-github/supported-browsers.md new file mode 100644 index 0000000000000..8f3f1b37f9e25 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/supported-browsers.md @@ -0,0 +1,20 @@ +--- +title: Navegadores compatibles +redirect_from: + - /articles/why-doesn-t-graphs-work-with-ie-8/ + - /articles/why-don-t-graphs-work-with-ie8/ + - /articles/supported-browsers +intro: 'Diseñamos {% data variables.product.product_name %} para admitir las últimas versiones de los navegadores web. Admitimos las versiones actuales de [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), y [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Lanzamiento de soporte extendido de Firefox + +Nos esforzamos para admitir el más reciente [Lanzamiento de soporte extendido](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) de Firefox. Las versiones anteriores de Firefox pueden inhabilitar algunas funciones en {% data variables.product.product_name %} y necesitan la última versión de Firefox. + +### Construcciones de programador y beta + +Puedes encontrar errores inesperados en beta y en construcciones de programador de nuestros navegadores compatibles. Si encuentras un error en {% data variables.product.product_name %} en uno de estas construcciones no lanzadas, verifica que también exista en la versión estable del mismo navegador. Si el error solo existe en la versión inestable, considera informar el error al programador del navegador. diff --git a/translations/es-ES/content/github/getting-started-with-github/troubleshooting-connectivity-problems.md b/translations/es-ES/content/github/getting-started-with-github/troubleshooting-connectivity-problems.md new file mode 100644 index 0000000000000..db35e48230ad4 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/troubleshooting-connectivity-problems.md @@ -0,0 +1,43 @@ +--- +title: Solucionar problemas de conectividad +intro: 'Si tienes problemas para conectarte a {% data variables.product.prodname_dotcom %}, puedes solucionar los problemas de conexión. Utiliza la herramienta {% data variables.product.prodname_debug %} para diagnosticar problemas.' +redirect_from: + - /articles/troubleshooting-connectivity-problems +versions: + free-pro-team: '*' +--- + + +La mayoría de las veces, los problemas de conexión ocurren porque un firewall, servidor proxy, red corporativa u otra red está configurada de una forma que bloquea {% data variables.product.prodname_dotcom %}. + +### Permitir las direcciones IP de {% data variables.product.prodname_dotcom %} + +Asegúrate de que tu red esté configurada para permitir las direcciones IP de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Acerca de las direcciones IP de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-ip-addresses)". + +### Utilizar la red de una empresa u organización + +Si tienes problemas de conectividad con la red de tu empresa u organización, consulta con tu administrador de red para saber si se le aplican reglas a la red para bloquear determinados tráficos. Si ya existen reglas configuradas, consulta con tu administrador de red para permitir el tráfico hacia {% data variables.product.prodname_dotcom %}. + +### Solucionar problemas de captcha + +Si no puedes verificar con el captcha: +- Asegúrate de que javascript esté habilitado en tu navegador. +- Asegúrate de que tu navegador sea compatible. Si tu navegador no es compatible, actualízalo o instala un navegador compatible. Para obtener una lista de navegadores compatibles, consulta "[Navegadores compatibles](/articles/supported-browsers)". +- Asegúrate de que tu configuración de red no esté bloqueando https://octocaptcha.com/ o https://arkoselabs.com/. Si estás detrás de un cortafuegos corporativo, contacta a tu administrador de TI para que incluya esos dominios. Para verificar el acceso a estos dominios, visita https://octocaptcha.com/test y asegúrate de que se muestre el texto "¡La conexión se llevó a cabo exitosamente!", luego visita https://client-demo.arkoselabs.com/github y asegúrate de que puedes cargar el captcha. +- Asegúrate de que tu navegador no tenga plug-ins o extensiones que puedan estar interfiriendo con GitHub. En tal caso, inhabilita de manera temporal los plug-ins o extensiones durante la verificación del captcha. + +### Cambiar métodos de clonación + +Cambiar desde la clonación por SSH a la clonación por HTTPS, o viceversa, puede mejorar la conectividad. Para obtener más información, consulta "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %}](/articles/cloning-a-repository-from-github)". + +Si están ocurriendo interrupciones con SSH, consulta "[Error: Número de archivo erróneo](/articles/error-bad-file-number)". + +### Solucionar problemas de descargas lentas y conexiones lentas intermitentes + +{% data variables.product.prodname_dotcom %} no alterna el ancho de banda por usuario. + +Si tienes conexiones lentas en determinados momentos del día, pero no en otros, las velocidades lentas normalmente se deben a la congestión de red. Ya que {% data variables.product.prodname_dotcom %} no puede resolver congestiones de red, debes escalar el problema a tu proveedor de servicio de internet. + +### Solucionar problemas con {% data variables.product.prodname_debug %} + +Si has seguido todas las sugerencias para solucionar problemas antes detalladas y sigues teniendo problemas de conexión, puedes seguir las indicaciones del sitio {% data variables.product.prodname_debug %} para ejecutar pruebas y enviar un informe a {% data variables.product.prodname_dotcom %} Support (Asistencia). Para obtener más información, consulta [{% data variables.product.prodname_debug %}](https://github-debug.com/). diff --git a/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md b/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md new file mode 100644 index 0000000000000..e9c1d05d88277 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md @@ -0,0 +1,78 @@ +--- +title: Tipos de cuentas de GitHub +intro: 'Tu cuenta de usuario es tu identidad en {% data variables.product.product_location %}. Tu cuenta de usuario puede ser miembro de cualquier cantidad de organizaciones.{% if currentVersion == "free-pro-team@latest" %} Las organizaciones pueden pertenecer a cuentas empresariales.{% endif %}' +redirect_from: + - /manage-multiple-clients/ + - /managing-clients/ + - /articles/what-s-the-difference-between-user-and-organization-accounts/ + - /articles/differences-between-user-and-organization-accounts/ + - /articles/types-of-github-accounts +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} +Para encontrar una lista completa de cada +producto de {% data variables.product.product_name %}, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)". +{% endif %} + +### Cuentas de usuarios personales + +Toda persona que utilice {% data variables.product.product_location %} tiene su propia cuenta de usuario, la cual incluye: + +{% if currentVersion == "free-pro-team@latest" %} + +- Repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %} +- Colaboradores ilimitados con {% data variables.product.prodname_free_user %} +- Funciones adicionales para los repositorios privados con {% data variables.product.prodname_pro %} +- Capacidad para [invitar colaboradores del repositorio](/articles/inviting-collaborators-to-a-personal-repository) + +{% else %} + +- Repositorios y [colaboradores](/articles/permission-levels-for-a-user-account-repository) ilimitados +- Capacidad para [agregar colaboradores del repositorio ilimitados](/articles/inviting-collaborators-to-a-personal-repository) + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Tips**: + +- Puedes utilizar una cuenta para múltiples propósitos, como uso personal y uso comercial. No recomendamos crear más de una cuenta. Para obtener más información, consulta "[Fusionar múltiples cuentas de usuario](/articles/merging-multiple-user-accounts)". +- Las cuentas de usuario están pensadas para seres humanos, pero le puedes dar una a un robot, como un bot de integración continua, si resulta necesario. + +{% endtip %} + +{% else %} + +{% tip %} + +**Sugerencia**: Las cuentas de usuario están pensadas para seres humanos, pero le puedes dar una a un robot, como un bot de integración continua, si resulta necesario. + +{% endtip %} + +{% endif %} + +### Cuentas de organización + +Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Cuentas de empresa + +Con las cuentas de empresa, puedes administrar de forma centralizada la política y la facturación de múltiples {% data variables.product.prodname_dotcom_the_website %} organizaciones. {% data reusables.gated-features.enterprise-accounts %} + +{% endif %} + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %}- "[Inicia sesión para crear una cuenta nueva de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" +- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)"{% endif %} +- "[Crear una cuenta de organización nueva](/articles/creating-a-new-organization-account)" diff --git a/translations/es-ES/content/github/getting-started-with-github/using-github.md b/translations/es-ES/content/github/getting-started-with-github/using-github.md new file mode 100644 index 0000000000000..7d0b9c89bad31 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/using-github.md @@ -0,0 +1,12 @@ +--- +title: Utilizar GitHub +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/using-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md b/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md new file mode 100644 index 0000000000000..9fc08551dca74 --- /dev/null +++ b/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md @@ -0,0 +1,64 @@ +--- +title: Verificar tu dirección de correo electrónico +intro: 'Verificar tu dirección principal de correo electrónico garantiza mayor seguridad, permite que el personal {% data variables.product.prodname_dotcom %} te ayude mejor si olvidas tu contraseña y te brinda acceso a más funciones en {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /articles/troubleshooting-email-verification/ + - /articles/setting-up-email-verification/ + - /articles/verifying-your-email-address +versions: + free-pro-team: '*' +--- + +### Acerca de la verificación del correo electrónico + +Puedes verificar tu dirección de correo electrónico después de registrarte con una cuenta nueva o cuando agregas una dirección de correo electrónico nueva. Si una dirección de correo electrónico no es válida para el envío o devuelve correos, quedará como no verificada. + +Si no verificas tu dirección de correo electrónico, no podrás hacer lo siguiente: + - Crear o bifurcar repositorios + - Crear propuestas o solicitudes de extracción + - Comentar sobre las propuestas, solicitudes de extracción o confirmaciones + - Autorizar aplicaciones de {% data variables.product.prodname_oauth_app %} + - Generar tokens de acceso personal + - Recibir notificaciones por correo electrónico + - Poner estrellas en repositorios + - Crear o actualizar tableros de proyecto, incluido agregar tarjetas + - Crear o actualizar gists + - Crear o utilizar {% data variables.product.prodname_actions %} + - Patrocinar desarrolladores con {% data variables.product.prodname_sponsors %} + +{% warning %} + +**Advertencias**: + +- {% data reusables.user_settings.no-verification-disposable-emails %} +- {% data reusables.user_settings.verify-org-approved-email-domain %} + +{% endwarning %} + +### Verificar tu dirección de correo electrónico + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +1. Debajo de tu dirección de correo electrónico, da clic en **Reenviar correo de verificación**. ![Reenviar enlace de verificación por correo electrónico](/assets/images/help/settings/email-verify-button.png) +4. {% data variables.product.prodname_dotcom %} te enviará un correo electrónico con un enlace. Después de hacer clic en el enlace, se te llevará a tu tablero {% data variables.product.prodname_dotcom %} y verás un mensaje emergente de confirmación. ![Mensaje emergente que confirma que se verificó tu correo electrónico](/assets/images/help/settings/email-verification-confirmation-banner.png) + +### Solución de problemas de verificación de correo electrónico + +#### No se pudo enviar el correo electrónico de verificación + +{% data reusables.user_settings.no-verification-disposable-emails %} + +#### Página de error después de hacer clic en el enlace de verificación + +El enlace de verificación vence después de 24 horas. Si no verificas tu correo electrónico dentro de las 24 horas, puedes solicitar otro enlace de verificación de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". + +Si haces clic en el enlace del correo electrónico de confirmación dentro de las 24 horas, y te dirige a una página de error, debes asegurarte de haberte registrado en la cuenta {% data variables.product.prodname_dotcom %} correcta. + +1. {% data variables.product.signout_link %} de tu cuenta personal {% data variables.product.prodname_dotcom %}. +2. Sal y vuelve a iniciar tu navegador. +3. {% data variables.product.signin_link %} a tu cuenta personal {% data variables.product.prodname_dotcom %}. +4. Haz clic en el enlace de verificación del correo electrónico que te enviamos. + +### Further reading + +- "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md new file mode 100644 index 0000000000000..62c9d827acaf0 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md @@ -0,0 +1,28 @@ +--- +title: Acerca de Importador GitHub +intro: 'Si tienes un código fuente en Subversion, Mercurial, Team Foundation Server u otro repositorio de Git, puedes moverlo a GitHub usando el Importador GitHub.' +redirect_from: + - /articles/about-github-importer +versions: + free-pro-team: '*' +--- + +Importador GitHub es una herramienta que importa de forma rápida repositorios de código fuente, incluido el historial de revisiones y confirmaciones de cambios, a GitHub para tí. + +![Importar un gif de repositorio](/assets/images/help/importer/github-importer.gif) + +Durante una importación, dependiendo del sistema de control de la versión del que estás importando, puedes autenticar con tu repositorio remoto, actualizar la atribución del autor de la confirmación e importar repositorios con archivos grandes (o eliminar archivos grandes si no quieres usar Large File Storage de Git). + +| Acción de importación | Subversion | Mercurial | Team Foundation Server | Git | +|:-------------------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:| +| Autenticar con repositorio remoto | **X** | **X** | **X** | **X** | +| [Actualizar la atribución del autor de la confirmación](/articles/updating-commit-author-attribution-with-github-importer) | **X** | **X** | **X** | | +| Mover archivos grandes a [Large File Storage de Git](/articles/about-git-large-file-storage) | **X** | **X** | **X** | | +| Eliminar archivos grandes de tu repositorio | **X** | **X** | **X** | | + +### Further reading + +- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" +- "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" +- "[Importar un repositorio de Git usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line)" +- "[Herramientas de migración de código fuente](/articles/source-code-migration-tools)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md new file mode 100644 index 0000000000000..0e9dc8d59c7b5 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -0,0 +1,139 @@ +--- +title: Agregar un proyecto existente a GitHub utilizando la línea de comando +intro: 'Poner tu trabajo existente en {% data variables.product.product_name %} puede permitirte compartir y colaborar de muchas maneras increíbles.' +redirect_from: + - /articles/add-an-existing-project-to-github/ + - /articles/adding-an-existing-project-to-github-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.migrating-from-codeplex %} + +{% tip %} + +**Sugerencia:** Si estás más a gusto con una interfaz de usuario de tipo "apuntar y hacer clic", trata de agregar tu proyecto con {% data variables.product.prodname_desktop %}. Para más información, consulta "[Agregar un repositorio de tu computadora local a GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" en *{% data variables.product.prodname_desktop %} Ayuda*. + +{% endtip %} + +{% data reusables.repositories.sensitive-info-warning %} + +{% mac %} + +1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en + +{% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. + ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Cambiar el directorio de trabajo actual en tu proyecto local. +4. Inicializar el directorio local como un repositorio de Git. + ```shell + $ git init -b main + ``` +5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. + ```shell + $ git add . + # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} + ``` +6. Confirmar los archivos que has preparado en tu repositorio local. + ```shell + $ git commit -m "First commit" + # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. + ```shell + $ git remote add origin remote repository URL + # Sets the new remote + $ git remote -v + # Verifies the new remote URL + ``` +9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. + ```shell + $ git push -u origin main + # Pushes the changes in your local repository up to the remote repository you specified as the origin + ``` + +{% endmac %} + +{% windows %} + +1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en + +{% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. + ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Cambiar el directorio de trabajo actual en tu proyecto local. +4. Inicializar el directorio local como un repositorio de Git. + ```shell + $ git init -b main + ``` +5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. + ```shell + $ git add . + # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} + ``` +6. Confirmar los archivos que has preparado en tu repositorio local. + ```shell + $ git commit -m "First commit" + # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. En la indicación Command (Comando), [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. + ```shell + $ git remote add origin remote repository URL + # Sets the new remote + $ git remote -v + # Verifies the new remote URL + ``` +9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. + ```shell + $ git push origin main + # Pushes the changes in your local repository up to the remote repository you specified as the origin + ``` + +{% endwindows %} + +{% linux %} + +1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en + +{% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. + ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Cambiar el directorio de trabajo actual en tu proyecto local. +4. Inicializar el directorio local como un repositorio de Git. + ```shell + $ git init -b main + ``` +5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. + ```shell + $ git add . + # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} + ``` +6. Confirmar los archivos que has preparado en tu repositorio local. + ```shell + $ git commit -m "First commit" + # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. + ```shell + $ git remote add origin remote repository URL + # Sets the new remote + $ git remote -v + # Verifies the new remote URL + ``` +9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. + ```shell + $ git push origin main + # Pushes the changes in your local repository up to the remote repository you specified as the origin + ``` + +{% endlinux %} + +### Further reading + +- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md new file mode 100644 index 0000000000000..11484d9b7def1 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md @@ -0,0 +1,44 @@ +--- +title: Importar un repositorio de Git usando la línea de comando +intro: '{% if currentVersion == "free-pro-team@latest" %}Si [GitHub Importer](/articles/importing-a-repository-with-github-importer) no se ajusta a tus necesidades, por ejemplo, si tu código existente se hospeda en una red privada, entonces te recomendamos importar utilizando la línea de comandos.{% else %}Importar proyectos de Git utilizando la línea de comandos es adecuado cuando tu código existente se encuentra hospedado en una red privada.{% endif %}' +redirect_from: + - /articles/importing-a-git-repository-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Antes de comenzar, asegúrate de saber lo siguiente: + +- Tu nombre de usuario {% data variables.product.product_name %} +- La URL del clon del repositorio externo, como `https://external-host.com/user/repo.git` o `git://external-host.com/user/repo.git` (quizás con un `user@` adelante del nombre de dominio `external-host.com`) + +{% tip %} + +A los fines de demostración, usaremos lo siguiente: + +- Una cuenta externa llamada **extuser** +- Un host de Git externo llamado `https://external-host.com` +- Una cuenta de usuario personal {% data variables.product.product_name %} llamada **ghuser** +- Un repositorio {% data variables.product.product_name %} llamado **repo.git** + +{% endtip %} + +1. [Crear un repositorio nuevo en {% data variables.product.product_name %}](/articles/creating-a-new-repository). Importarás tu repositorio de Git externo a este repositorio nuevo. +2. En la línea de comando, haz un clon "en blanco" del repositorio usando la URL del clon externo. Esto crea una copia completa de los datos, pero sin un directorio de trabajo para editar archivos, y asegura una exportación limpia y nueva de todos los datos antiguos. + ```shell + $ git clone --bare https://external-host.com/extuser/repo.git + # Makes a bare clone of the external repository in a local directory + ``` +3. Sube el repositorio clonado de forma local a {% data variables.product.product_name %} usando la opción "espejo", que asegura que todas las referencias, como ramas y etiquetas, se copien en el repositorio importado. + ```shell + $ cd repo.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/repo.git + # Pushes the mirror to the new {% data variables.product.product_name %} repository + ``` +4. Elimina el repositorio local temporal. + ```shell + $ cd .. + $ rm -rf repo.git + ``` diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md new file mode 100644 index 0000000000000..872cf0631f87d --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md @@ -0,0 +1,36 @@ +--- +title: Importar un repositorio con el Importador GitHub +intro: 'Si tienes un proyecto alojado en otro sistema de control de versión, puedes importarlo automáticamente a GitHub usando la herramienta Importador GitHub.' +redirect_from: + - /articles/importing-from-other-version-control-systems-to-github/ + - /articles/importing-a-repository-with-github-importer +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** El Importador GitHub no útil para todas las importaciones. Por ejemplo, si tu código existente está alojado en una red privada, nuestra herramienta no podrá acceder a él. En estos casos, recomendamos [importar usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line) para los repositorios de Git o una [herramienta de migración de código fuente](/articles/source-code-migration-tools) externa para los proyectos importados desde otros sistemas de control de versión. + +{% endtip %} + +Si quieres hacer coincidir las confirmaciones de tu repositorio con las cuentas de usuario de GitHub de los autores durante la importación, asegúrate de que cada contribuyente de tu repositorio tenga una cuenta de GitHub antes de comenzar la importación. + +{% data reusables.repositories.migrating-from-codeplex %} + +{% data reusables.repositories.repo-size-limit %} + +1. En la esquina superior derecha de cada página, haz clic en {% octicon "plus" aria-label="Plus symbol" %} y luego haz clic en **Import repository** (Importar repositorio). ![Opción de Importar repositorio en el menú del nuevo repositorio](/assets/images/help/importer/import-repository.png) +2. En "La URL del clon de tu repositorio antiguo", escribe la URL del proyecto que quieres importar. ![Campo de texto para la URL del repositorio importado](/assets/images/help/importer/import-url.png) +3. Elige tu cuenta de usuario o una organización como propietaria del repositorio, luego escribe un nombre para el repositorio en GitHub. ![Menú del propietario del repositorio y campo del nombre del repositorio](/assets/images/help/importer/import-repo-owner-name.png) +4. Especifica si el repositorio nuevo debe ser *público* o *privado*. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". ![Botones Radio para el repositorio público o privado](/assets/images/help/importer/import-public-or-private.png) +5. Revisa la información que ingresaste, luego haz clic en **Begin import** (Comenzar importación). ![Botón Begin import (Comenzar importación)](/assets/images/help/importer/begin-import-button.png) +6. Si tus proyectos antiguos estaban protegidos con contraseña, escribe tu información de inicio de sesión para ese proyecto, luego haz clic en **Submit** (Enviar). ![Formulario de contraseña y botón Submit (Enviar) para proyecto protegido con contraseña](/assets/images/help/importer/submit-old-credentials-importer.png) +7. Si hay múltiples proyectos alojados en la URL del clon de tu proyecto antiguo, elige el proyecto que quieras importar, luego haz clic en **Submit** (Enviar). ![Lista de proyectos para importar y botón Submit (Enviar)](/assets/images/help/importer/choose-project-importer.png) +8. Si tu proyecto contiene archivos mayores a 100 MB, elige si importarás los archivos grandes usando [Git Large File Storage](/articles/versioning-large-files), luego haz clic en **Continue** (Continuar). ![Menú de Git Large File Storage y botón Continue (Continuar)](/assets/images/help/importer/select-gitlfs-importer.png) + +Recibirás un correo electrónico cuando se haya importado todo el repositorio. + +### Further reading + +- "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md new file mode 100644 index 0000000000000..0d32b3d82377f --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md @@ -0,0 +1,16 @@ +--- +title: Importar código fuente a GitHub +intro: 'Puedes importar repositorios a GitHub utilizando el {% if currentVersion == "free-pro-team@latest" %}Importador de GitHub, la línea de comandos,{% else %}la línea de comandos{% endif %} o las herramientas de migración externa.' +redirect_from: + - /articles/importing-an-external-git-repository/ + - /articles/importing-from-bitbucket/ + - /articles/importing-an-external-git-repo/ + - /articles/importing-your-project-to-github/ + - /articles/importing-source-code-to-github +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/index.md b/translations/es-ES/content/github/importing-your-projects-to-github/index.md new file mode 100644 index 0000000000000..ab7a1412356a2 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/index.md @@ -0,0 +1,27 @@ +--- +title: Importar tus proyectos a GitHub +shortTitle: Importar tus proyectos +redirect_from: + - /categories/67/articles/ + - /categories/importing/ + - /categories/importing-your-projects-to-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /importing-source-code-to-github %} + {% link_in_list /about-github-importer %} + {% link_in_list /importing-a-repository-with-github-importer %} + {% link_in_list /updating-commit-author-attribution-with-github-importer %} + {% link_in_list /importing-a-git-repository-using-the-command-line %} + {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} + {% link_in_list /source-code-migration-tools %} +{% topic_link_in_list /working-with-subversion-on-github %} + {% link_in_list /what-are-the-differences-between-subversion-and-git %} + {% link_in_list /support-for-subversion-clients %} + {% link_in_list /subversion-properties-supported-by-github %} diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md new file mode 100644 index 0000000000000..4ffa5292f8aa4 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md @@ -0,0 +1,56 @@ +--- +title: Herramientas de migración de código fuente +intro: Puedes utilizar herramientas externas para mover tus proyectos a GitHub. +redirect_from: + - /articles/importing-from-subversion/ + - /articles/source-code-migration-tools +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +Recomendamos utilizar [GitHub Importer](/articles/about-github-importer) para importar proyectos desde Subversion, Mercurial, Team Foundation Server u otro repositorio de Git. También puedes utilizar estas herramientas externas para convertir tus proyectos a Git. + +{% endif %} + +### Importar desde Subversion + +En un entorno normal de Subversion, se almacenan varios proyectos en un único repositorio raíz. En GitHub, cada uno de estos proyectos generalmente se mapeará a un repositorio de Git separado para una cuenta de usuario o de organización. Sugerimos importar cada parte de tu repositorio de Subversion a un repositorio de GitHub separado si: + +* Los colaboradores necesitan revisar o confirmar esa parte del proyecto de forma separada desde las otras partes +* Deseas que distintas partes tengan sus propios permisos de acceso + +Recomendamos estas herramientas para convertir repositorio de Subversion a Git: + +- [`git-svn`](https://git-scm.com/docs/git-svn) +- [svn2git](https://github.com/nirvdrum/svn2git) + +### Importar desde Mercurial + +Recomendamos [hg-fast-export](https://github.com/frej/fast-export) para convertir repositorios de Mercurial a Git. + +### Importar desde Team Foundation Server + +Recomendamos estas herramientas para mover cambios entre Team Foundation Server y Git: + +- [git-tfs](https://github.com/git-tfs/git-tfs) +- [Git-TF](https://gittf.codeplex.com/) + +{% tip %} + +**Sugerencia:** después de haber convertido con éxito tu proyecto a Git, puedes [subirlo a {% data variables.product.prodname_dotcom %}](/articles/pushing-commits-to-a-remote-repository/). + +{% endtip %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Further reading + +- "[Acerca del Importador GitHub](/articles/about-github-importer)" +- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) + +{% endif %} diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/subversion-properties-supported-by-github.md b/translations/es-ES/content/github/importing-your-projects-to-github/subversion-properties-supported-by-github.md new file mode 100644 index 0000000000000..683efd2c8295e --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/subversion-properties-supported-by-github.md @@ -0,0 +1,25 @@ +--- +title: Propiedades de Subversion admitidas por GitHub +intro: 'Existen varios flujos de trabajo y propiedades de Subversion que son similares a la funcionalidad existente en {% data variables.product.product_name %}.' +redirect_from: + - /articles/subversion-properties-supported-by-github +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Archivos ejecutables (svn:executable) + +Convertimos propiedades `svn:executable` al actualizar el modo archivo directamente antes de agregarlo al repositorio de Git. + +### Tipos MIME (svn:mime-type) + +{% data variables.product.product_name %} internalmente rastrea las propiedades mime-type de los archivos y las confirmaciones que los agregaron. + +### Ignorar elementos sin versión (svn:ignore) + +Si has configurado que los archivos y los directorios se ignoren en Subversion, {% data variables.product.product_name %} los rastrearemos de manera interna. Los archivos ignorados por los clientes de Subversion son completamente distintos a las entradas en un archivo *.gitignore*. + +### Propiedades admitidas actualmente + +{% data variables.product.product_name %} no admite actualmente `svn:externals`, `svn:global-ignores`, o culaquier propiedad no enumerada anteriormente, incluidas las propiedades personalizadas. diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md b/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md new file mode 100644 index 0000000000000..442c890042c3b --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md @@ -0,0 +1,130 @@ +--- +title: Soporte para clientes de Subversion +intro: Los repositorios de GitHub pueden accederse desde los clientes de Git y de Subversion (SVN). En este artículo se aborda el uso de un cliente de Subversion en GitHub y algunos problemas comunes que puedes llegar a encontrar. +redirect_from: + - /articles/support-for-subversion-clients +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +GitHub admite clientes de Subversion por medio del protocolo HTTPS. Utilizamos el puente de Subversion para comunicar los comandos svn a GitHub. + +### Funciones de Subversion admitidas en GitHub + +#### Control + +La primera cosa que desearás realizar es un control de Subversion. Ya que los clones de Git mantienen un directorio de trabajo (donde editas los archivos) separado de los datos del repositorio, solo hay una rama en el directorio de trabajo a la vez. + +Los controles de Subversion son diferentes: combinan los datos del repositorio en los directorios de trabajo, por lo que hay un directorio de trabajo para cada rama y etiqueta que has revisado. Para los repositorios con muchas ramas y etiquetas, revisar cada cosa puede ser una sobrecarga del ancho de banda, por lo que deberías comenzar con un control parcial. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.copy-clone-url %} + +3. Realiza un control vacío del repositorio: + ```shell + $ svn co --depth empty https://github.com/user/repo + > Checked out revision 1. + $ cd repo + ``` + +4. Llega hasta la rama `trunk` (tronco). El puente de Subversion mapea a trunk en la rama HEAD de Git. + ```shell + $ svn up trunk + > A trunk + > A trunk/README.md + > A trunk/gizmo.rb + > Updated to revision 1. + ``` + +5. Consigue un control vacío del directorio de `branches` (ramas). Aquí es donde están todas las ramas non-`HEAD` (no encabezado), y donde harás las ramas de características. + ```shell + $ svn up --depth empty branches + Updated to revision 1. + ``` + +#### Crear ramas + +También puedes crear ramas usando el puente de Subversion a GitHub. + +Desde tu cliente de svn, asegúrate de que la rama predeterminada es la más reciente actualizando `trunk`: +```shell +$ svn up trunk +> At revision 1. +``` + +A continuación, puedes utilizar `svn copy` para crear una nueva rama: +```shell +$ svn copy trunk branches/more_awesome +> A branches/more_awesome +$ svn commit -m 'Added more_awesome topic branch' +> Adding branches/more_awesome + +> Revisión confirmada 2. +``` + +Puedes confirmar que la nueva rama existe en el menú desplegable de la rama del repositorio: + +![branch-snapshot](/assets/images/help/branch/svnflow-branch-snapshot.png) + +También puedes confirmar la nueva rama por medio de la línea de comando: + +```shell +$ git fetch +> From https://github.com/user/repo/ +> * [new branch] more_awesome -> origin/more_awesome +``` + +#### Realizar confirmaciones de cambios en Subversion + +Después de haber agregado algunas características y haber arreglado algunos errores, desearás confirmar estos cambios en GitHub. Esto funciona de la misma forma en la que estás acostumbrado en Subversion. Edita tus archivos y utiliza `svn commit` para registrar tus cambios: + +```shell +$ svn status +> M gizmo.rb +$ svn commit -m 'Guard against known problems' +> Sending more_awesome/gizmo.rb +> Transmitiendo los datos del archivo. +> Revisión confirmada 3. +$ svn status +> ? test +$ svn add test +> A test +> A test/gizmo_test.rb +$ svn commit -m 'Test coverage for problems' +> Adding more_awesome/test +> Adding more_awesome/test/gizmo_test.rb +> Transmitiendo los datos del archivo. +> Revisión confirmada 4. +``` + +#### Alternar entre ramas + +Para alternar entre ramas, probablemente desearás comenzar con un control del `trunk` (tronco): + +```shell +$ svn co --depth empty https://github.com/user/repo/trunk +``` + +Luego, puedes alternar a otra rama: + +```shell +$ svn switch https://github.com/user/repo/branches/more_awesome +``` + +### Encontrar el SHA de confirmación de Git para una confirmación de Subversion + +El servidor de Subversion de GitHub muestra el sha de confirmación de Git para cada confirmación de Subversion. + +Para ver el SHA de confirmación, deberías solicitar la propiedad remota sin versión de `git-commit`. + +```shell +$ svn propget git-commit --revprop -r HEAD https://github.com/user/repo +05fcc584ed53d7b0c92e116cb7e64d198b13c4e3 +``` + +Con este SHA de confirmación, puedes, por ejemplo, consultar la correspondiente confirmación Git en GitHub. + +### Further reading + +* "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md new file mode 100644 index 0000000000000..850dc986e759d --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md @@ -0,0 +1,39 @@ +--- +title: Actualizar la atribución del autor de la confirmación con Importador GitHub +intro: 'Durante una importación, puedes hacer coincidir las confirmaciones de tu repositorio con la cuenta de GitHub del autor de la confirmación.' +redirect_from: + - /articles/updating-commit-author-attribution-with-github-importer +versions: + free-pro-team: '*' +--- + +El Importador GitHub busca los usuarios de GitHub cuyas direcciones de correo electrónico coincidan con los autores de las confirmaciones del repositorio que estás importando. Luego puedes conectar una confirmación con su autor utilizando su dirección de correo electrónico o el nombre de usuario de GitHub del autor. + +### Actualizar autores de la confirmación + +1. Después de que hayas importado tu repositorio, en la página de estado de importación, haz clic en **Match authors** (Hacer coincidir autores). ![Botón Match authors (Hacer coincidir autores)](/assets/images/help/importer/match-authors-button.png) +2. Al lado del autor cuya información quieres actualizar, haz clic en **Connect** (Conectar). ![Lista de autores de la confirmación](/assets/images/help/importer/connect-commit-author.png) +3. Escribe la dirección de correo electrónico o el nombre de usuario de GitHub del autor, luego presiona **Enter**. + +### Atribuir confirmaciones a un usuario de GitHub con una dirección de correo electrónico pública + +Si el autor de una confirmación en tu repositorio importado tiene una cuenta de GitHub asociada con la dirección de correo electrónico que utilizó para figurar como autor de la confirmación y no estableció [su dirección de correo electrónico de confirmaciones como privada](/articles/setting-your-commit-email-address), el Importador GitHub hará coincidir la dirección de correo electrónico asociada a la confirmación con la dirección de correo electrónico pública asociada a su cuenta de GitHub, y atribuirá la confirmación a su cuenta de GitHub. + +### Atribuir confirmaciones a un usuario de GitHub sin una dirección de correo electrónico pública + +Si el autor de una confirmación en tu repositorio importado no estableció una dirección de correo electrónico pública en su perfil de GitHub ni [estableció su dirección de correo electrónico de confirmaciones como privada](/articles/setting-your-commit-email-address), el Importador GitHub no podrá hacer coincidir la dirección de correo electrónico asociada a la confirmación con su cuenta de GitHub. + +El autor de la confirmación puede resolver esto estableciendo su dirección de correo electrónico como privada. Sus confirmaciones luego se le atribuirán a `@users.noreply.github.com`, y las confirmaciones importadas se asociarán a su cuenta de GitHub. + +### Atribuir confirmaciones utilizando una dirección de correo electrónico + +Si la dirección de correo electrónico del autor no está asociada a su cuenta de GitHub, puede [agregar la dirección a su cuenta](/articles/adding-an-email-address-to-your-github-account) después de la importación, y las confirmaciones se atribuirán de manera correcta. + +Si el autor no tiene una cuenta de GitHub, el Importador GitHub atribuirá sus confirmaciones a la dirección de correo electrónico asociada a las confirmaciones. + +### Further reading + +- "[Acerca del Importador GitHub](/articles/about-github-importer)" +- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" +- "[Agregar una dirección de correo electrónico a tu cuenta](/articles/adding-an-email-address-to-your-github-account/)" +- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md b/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md new file mode 100644 index 0000000000000..e2836ba217eab --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md @@ -0,0 +1,67 @@ +--- +title: '¿Cuáles son las diferencias entre Subversion y Git?' +intro: 'Los repositorios de Subversion (SVN) son similares a los repositorios de Git, pero hay diferencias cuando se refiere a la arquitectura de tus proyectos.' +redirect_from: + - /articles/what-are-the-differences-between-svn-and-git/ + - /articles/what-are-the-differences-between-subversion-and-git +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Estructura del directorio + +Cada *referencia*, o instantánea etiquetada de una confirmación, en un proyecto se organiza dentro de subdirectorios específicos, como `tronco`, `ramas` y `etiquetas`. Por ejemplo, un proyecto SVN con dos características bajo desarrollo debería parecerse a esto: + + sample_project/trunk/README.md + sample_project/trunk/lib/widget.rb + sample_project/branches/new_feature/README.md + sample_project/branches/new_feature/lib/widget.rb + sample_project/branches/another_new_feature/README.md + sample_project/branches/another_new_feature/lib/widget.rb + +Un flujo de trabajo SVN se parece a esto: + +* El directorio `tronco` representa el último lanzamiento estable de un proyecto. +* El trabajo de característica activa se desarrolla dentro de subdirectorios dentro de `ramas`. +* Cuando una característica se termina, el directorio de la característica se fusiona dentro del `tronco` y se elimina. + +Los proyectos de Git también se almacenan dentro de un directorio único. Sin embargo, Git oculta los detalles de sus referencias al almacenarlos en un directorio *.git* especial. Por ejemplo, un proyecto Git con dos características bajo desarrollo debería parecerse a esto: + + sample_project/.git + sample_project/README.md + sample_project/lib/widget.rb + +Un flujo de trabajo Git se parece a esto: + +* Un repositorio Git almacena el historial completo de todas sus ramas y etiquetas dentro del directorio de *.git*. +* El último lanzamiento estables se contiene dentro de la rama predeterminada. +* El trabajo de característica activa se desarrolla en ramas separadas. +* Cuando una característica finaliza, la rama de característica se fusiona en la rama predeterminada y se borra. + +A diferencia de SVN, con Git la estructura del directorio permanece igual, pero los contenidos de los archivos cambia en base a tu rama. + +### Incluir los subproyectos + +Un *subproyecto* es un proyecto que se ha desarrollado y administrado en algún lugar fuera del proyecto principal. Normalmente importas un subproyecto para agregar alguna funcionalidad a tu proyecto sin necesidad de mantener el código. Cada vez que el proyecto se actualiza, puedes sincronizarlo con tu proyecto para garantizar que todo esté actualizado. + +En SVN, un subproyecto se llama un *SVN externo*. En Git, se llama un *submódulo Git*. A pesar de que conceptualmente son similares, los submódulos Git no se mantienen actualizados de forma automática; debes solicitar explícitamente que se traiga una nueva versión a tu proyecto. + +Para obtener más información, consulta la sección "[Submódulos de las Git Tools](https://git-scm.com/book/en/Git-Tools-Submodules)" en la documentación de Git. + +### Mantener el historial + +SVN está configurado para suponer que el historial de un proyecto nunca cambia. Git te permite modificar cambios y confirmaciones previas utilizando herramientas como [`git rebase`](/articles/about-git-rebase). + +{% tip %} + +[GitHub admite clientes de Subversion](/articles/support-for-subversion-clients), lo que puede generar algunos resultados inesperados si estás utilizando tanto Git como SVN en el mismo proyecto. Si has manipulado el historial de confirmación de Git, esas mismas confirmaciones siempre permanecerán dentro del historial de SVN. Si accidentalmente confirmaste algunos datos confidenciales, hay un [artículo que te ayudará a eliminarlo del historial de Git](/articles/removing-sensitive-data-from-a-repository). + +{% endtip %} + +### Further reading + +- "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" +- ["Branching and Merging" del libro _Git SCM_](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging) +- "[Importar código fuente a GitHub](/articles/importing-source-code-to-github)" +- "[Herramientas de migración de código fuente](/articles/source-code-migration-tools)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md new file mode 100644 index 0000000000000..cdf2466f61e27 --- /dev/null +++ b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md @@ -0,0 +1,11 @@ +--- +title: Trabajar con Subversion en GitHub +intro: Puedes usar clientes de Subversion y algunos flujos de trabajo y propiedades de Subversion con GitHub. +mapTopic: verdadero +redirect_from: + - /articles/working-with-subversion-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md new file mode 100644 index 0000000000000..d44e92ca60973 --- /dev/null +++ b/translations/es-ES/content/github/index.md @@ -0,0 +1,70 @@ +--- +title: GitHub.com +redirect_from: + - /articles/ + - /common-issues-and-questions/ + - /troubleshooting-common-issues/ +intro: 'Documentación, guías y temas de ayuda para programadores de software, diseñadores y gerentes de proyectos. Cubre el uso de Git, solicitudes de extracción, propuestas, wikis, gists y todo lo necesario para sacar el máximo provecho de GitHub para programación.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_in_list /getting-started-with-github %} + +{% link_in_list /setting-up-and-managing-your-github-user-account %} + +{% link_in_list /setting-up-and-managing-your-github-profile %} + +{% link_in_list /authenticating-to-github %} + + +{% link_in_list /managing-subscriptions-and-notifications-on-github %} + + +{% link_in_list /receiving-notifications-about-activity-on-github %} + +{% link_in_list /setting-up-and-managing-organizations-and-teams %} +{% link_in_list /setting-up-and-managing-your-enterprise %} +{% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} + +{% link_in_list /writing-on-github %} + +{% link_in_list /creating-cloning-and-archiving-repositories %} + +{% link_in_list /using-git %} + +{% link_in_list /committing-changes-to-your-project %} + +{% link_in_list /collaborating-with-issues-and-pull-requests %} + +{% link_in_list /managing-your-work-on-github %} +{% link_in_list /developing-online-with-codespaces %} + +{% link_in_list /building-a-strong-community %} + +{% link_in_list /searching-for-information-on-github %} + +{% link_in_list /importing-your-projects-to-github %} + +{% link_in_list /administering-a-repository %} + +{% link_in_list /visualizing-repository-data-with-graphs %} +{% link_in_list /managing-security-vulnerabilities %} + +{% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} + +{% link_in_list /managing-files-in-a-repository %} + +{% link_in_list /managing-large-files %} +{% link_in_list /customizing-your-github-workflow %} + +{% link_in_list /extending-github %} + +{% link_in_list /working-with-github-pages %} +{% link_in_list /supporting-the-open-source-community-with-github-sponsors %} +{% link_in_list /finding-talent-with-github-jobs %} +{% link_in_list /working-with-github-support %} +{% link_in_list /understanding-how-github-uses-and-protects-your-data %} +{% link_in_list /site-policy %} diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md b/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md new file mode 100644 index 0000000000000..027acd31260ad --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md @@ -0,0 +1,63 @@ +--- +title: Visualizador de archivos 3D +redirect_from: + - /articles/stl-file-viewer/ + - /articles/3d-file-viewer +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data variables.product.product_name %} puede alojar y representar archivos 3D con la extensión *.stl*. + +Al buscar directamente en un archivo STL en {% data variables.product.product_name %} puedes: + +* Hacer clic y arrastrar para girar el modelo. +* Hacer clic con el botón derecho y arrastrar para traducir la vista. +* Desplazarse para acercar y alejar. +* Hacer clic en los diferentes modos para cambiar la vista. + +### Diferencias + +Cuando miras una confirmación de cambios o un conjunto de cambios que incluyen un archivo STL, podrás ver una diferencia de antes y después del archivo. + +Por defecto, obtendrás una vista donde todo lo que no ha cambiado está en el esquema de página. Las adiciones aparecen en verde y las partes eliminadas aparecen en rojo. + +![wireframe](/assets/images/help/repository/stl_wireframe.png) + +También puedes seleccionar la opción **Control deslizante de la revisión**, que te permite usar un control deslizante en la parte superior del archivo para cambiar entre las revisiones actuales y las anteriores. + +### Solucionar un rendimiento reducido + +Si ves este ícono en la esquina del visualizador, entonces la tecnología WebGL no está disponible en tu navegador: + +![error emergente de WebGL](/assets/images/help/repository/render_webgl_error.png) + +WebGL es necesario para aprovechar el hardware de tu equipo al máximo. Te recomendamos que intentes con navegadores como [Chrome](https://www.google.com/intl/en/chrome/browser/) o [Firefox](https://www.mozilla.org/en-US/firefox/new/), que vienen con WebGL activado. + +### Error: "No se puede mostrar" + +Si tu modelo no es válido, es posible que GitHub no pueda mostrar el archivo. Además, los archivos de más de 10 MB son demasiado grandes para que GitHub los muestre. + +### Insertar tu modelo en otro lugar + +Para mostrar tu archivo 3D en algún otro lugar de Internet, modifica esta plantilla y colócala en cualquier página HTML que sea compatible con JavaScript: + +```html + +``` + +Por ejemplo, si la URL de tu modelo es [github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl), tu código para insertar sería: + +```html + +``` + +Por defecto, la representación insertada es de 420 píxeles de ancho por 620 de alto, pero puedes personalizar la salida, pasando las variables de altura y ancho como parámetros al final de la URL, como `?height=300&width=500`. + +{% tip %} + +**Nota**: `ref` puede ser una rama del hash para una confirmación individual (como `2391ae`). + +{% endtip %} diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md new file mode 100644 index 0000000000000..f978a50694d95 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md @@ -0,0 +1,43 @@ +--- +title: Agregar un archivo a un repositorio utilizando la línea de comando +intro: 'Puedes cargar un archivo existente a un repositorio {% data variables.product.product_name %} utilizando la línea de comando.' +redirect_from: + - /articles/adding-a-file-to-a-repository-from-the-command-line/ + - /articles/adding-a-file-to-a-repository-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** También puedes [agregar un archivo existente a un repositorio desde el sitio web de {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository). + +{% endtip %} + +{% data reusables.command_line.manipulating_file_prereqs %} + +{% data reusables.repositories.sensitive-info-warning %} + +1. En tu computadora, mueve el archivo que que quisieras cargar a + +{% data variables.product.product_name %} hacia el directorio local que se creó cuando clonaste el repositorio. +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.switching_directories_procedural %} +{% data reusables.git.stage_for_commit %} + ```shell + $ git add . + # Agrega el archivo a tu repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} + ``` +{% data reusables.git.commit-file %} + ```shell + $ git commit -m "Add existing file" + # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +{% data reusables.git.git-push %} + +### Further reading + +- "[Crear archivos nuevos](/articles/creating-new-files)" +- [Agregar un proyecto existente a GitHub mediante la línea de comando](/articles/adding-an-existing-project-to-github-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository.md new file mode 100644 index 0000000000000..12c687ef0c90c --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository.md @@ -0,0 +1,31 @@ +--- +title: Agregar un archivo a un repositorio +intro: 'Puedes cargar y confirmar un archivo existente a un repositorio {% data variables.product.product_name %}. Arrastra y suelta un archivo en cualquier directorio en el árbol de archivos desde la página principal del repositorio.' +redirect_from: + - /articles/adding-a-file-to-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los archivos que agregues a un repositorio mediante un navegador están limitados a {% data variables.large_files.max_github_browser_size %} por archivo. Puedes agregar archivos más grandes, de hasta {% data variables.large_files.max_github_size %} cada uno, mediante la línea de comando. Para obtener más información, consulta "[Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)". + +{% tip %} + +**Tips:** +- Puedes cargar múltiples archivos en {% data variables.product.product_name %} a la vez. +- {% data reusables.repositories.protected-branches-block-web-edits-uploads %} + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +2. Debajo del nombre del repositorio, haz clic en **Upload files** (Cargar archivos). ![Botón Upload files (Cargar archivos)](/assets/images/help/repository/upload-files-button.png) +{% else %} +2. Sobre la lista de archivos, da clic en **Cargar archivos** utilizando el menú desplegable de **Agregar archivo**. !["Archivos cargados" en el menú desplegable de "Agregar archivo"](/assets/images/help/repository/upload-files-button.png) +{% endif %} +3. Arrastra y suelta el archivo o la carpeta que te gustaría cargar en tu repositorio en el árbol del archivo. ![Área para arrastrar y soltar](/assets/images/help/repository/upload-files-drag-and-drop.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +6. Haz clic en **Commit changes** (Confirmar cambios). ![Botón Commit changes (Confirmar cambios)](/assets/images/help/repository/commit-changes-button.png) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md new file mode 100644 index 0000000000000..8c39c6a6f33e8 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md @@ -0,0 +1,33 @@ +--- +title: Crear nuevos archivos +intro: 'Puedes crear nuevos archivos directamente en {% data variables.product.product_name %} en cualquier repositorio al que tengas acceso de escritura.' +redirect_from: + - /articles/creating-new-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando crees un archivo en {% data variables.product.product_name %}, ten en cuenta lo siguiente: + +- Si intentas crear un nuevo archivo en un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original una vez que confirmes tu cambio. +- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para usar otros caracteres, [crea y confirma los archivos de manera local, y luego súbelos al repositorio en {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line). + +{% data reusables.repositories.sensitive-info-warning %} + +{% data reusables.repositories.navigate-to-repo %} +2. En tu repositorio, dirígete a la carpeta en la que deseas crear un archivo. +{% data reusables.files.add-file %} +4. En el campo para el nombre del archivo, escribe el nombre y la extensión del archivo. Para crear subdirectorios, escribe el separador de directorio `/`. ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) +5. En la pestaña **Editar nuevo archivo**, agrega contenido al archivo. ![Contenido del nuevo archivo](/assets/images/help/repository/new-file-content.png) +6. Para revisar el nuevo contenido, haz clic en **Vista previa**. ![Botón New file preview (Vista previa del archivo nuevo)](/assets/images/help/repository/new-file-preview.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Further reading + +- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" +- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..a0e1589a6aee7 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. Para obtener más información, consulta "[Eliminar datos confidenciales de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". + +### Deleting a file + +1. Dirígete al archivo que deseas eliminar de tu repositorio. +2. En la parte superior del archivo, da clic en +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md new file mode 100644 index 0000000000000..7b34393d525c4 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md @@ -0,0 +1,26 @@ +--- +title: Editar archivos en el repositorio de otro usuario +intro: 'Cuando edites un archivo en el repositorio de otro usuario, automáticamente [bifurcaremos el repositorio](/articles/fork-a-repo) y [abriremos una solicitud de extracción](/articles/creating-a-pull-request) por ti.' +redirect_from: + - /articles/editing-files-in-another-users-repository/ + - /articles/editing-files-in-another-user-s-repository + - /articles/editing-files-in-another-users-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +1. En el repositorio de otro usuario, dirígete a la carpeta que contiene el archivo que deseas editar. Haz clic en el nombre del archivo que deseas editar. +2. Sobre el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. En este punto del proceso, GitHub bifurca el repositorio por ti. +3. Realiza todos los cambios que necesites en el archivo. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) +{% data reusables.files.preview_change %} +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +6. Haz clic en **Proponer cambio en el archivo**. ![Botón Confirmar cambios](/assets/images/help/repository/propose_file_change_button.png) +7. Escribe un título y una descripción para tu solicitud de extracción. ![Página de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png) +8. Haz clic en **Create Pull Request** (Crear solicitud de extracción). ![Botón Solicitud de extracción](/assets/images/help/pull_requests/pullrequest-send.png) + +### Further reading + +* "[Editar archivos en un repositorio](/articles/editing-files-in-your-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md new file mode 100644 index 0000000000000..5e6520ae68458 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md @@ -0,0 +1,36 @@ +--- +title: Editar archivos en tu repositorio +intro: 'Puedes editar archivos directamente en {% data variables.product.product_name %} en cualquiera de tus repositorios usando el editor de archivos.' +redirect_from: + - /articles/editing-files/ + - /articles/editing-files-in-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia**:{% data reusables.repositories.protected-branches-block-web-edits-uploads %} + +{% endtip %} + +{% note %} + +**Nota:** El editor de archivos de {% data variables.product.product_name %} usa [CodeMirror](https://codemirror.net/). + +{% endnote %} + +1. En tu repositorio, dirígete al archivo que deseas editar. +{% data reusables.repositories.edit-file %} +3. En la pestaña **Editar archivo**, realiza todos los cambios que sean necesarios. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) +{% data reusables.files.preview_change %} +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Further reading + +* "[Editar archivos en el repositorio de otro usuario](/articles/editing-files-in-another-user-s-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md new file mode 100644 index 0000000000000..c39a9a0221a10 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md @@ -0,0 +1,52 @@ +--- +title: Obtener enlaces permanentes a archivos +intro: 'Cuando ves un archivo en {% data variables.product.product_location %}, puedes presionar la tecla "y" para actualizar la URL y obtener un enlace permanente para la versión exacta del archivo que estás viendo.' +redirect_from: + - /articles/getting-a-permanent-link-to-a-file/ + - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url/ + - /articles/getting-permanent-links-to-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia**: Presiona "?" en cualquier página en {% data variables.product.product_name %} para ver todos los atajos del teclado disponibles. + +{% endtip %} + +### Vistas del archivo que muestran la versión más reciente en una rama + +Cuando ves un archivo en {% data variables.product.product_location %}, por lo general, accedes a la versión en el encabezado actual de una rama. Por ejemplo: + +* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) + +se refiere al repositorio `codeql` de GitHub, y muestra la versión más reciente de la rama `main` del archivo `README.md`. + +La versión de un archivo en el encabezado de una rama puede cambiar cuando se realizan nuevas confirmaciones, por eso si copias la URL normal, el contenido del archivo puede no ser el mismo cuando alguien lo vea más tarde. + +### Presiona y para obtener un enlace permanente en archivo en una confirmación específica + +Para encontrar un enlace permanente a la versión específica de un archivo que veas, en vez de utilizar el nombre de la rama en la URL (por ejemplo, la parte de `main` en el ejemplo anterior), coloca una id de confirmación. Esto generará un enlace permanente a la versión exacta del archivo en esa confirmación. Por ejemplo: + +* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) + +reemplaza `main` con la id de confirmación específica y el contenido del archivo no cambiará. + +Buscar de manera manual el SHA de confirmación es muy poco práctico. No obstante, a modo de atajo, puedes escribir y para actualizar automáticamente la URL para la versión del enlace permanente. Luego puedes copiar la URL sabiendo que todas las personas con quienes la compartas verán exactamente lo mismo que tú viste. + +{% tip %} + +**Sugerencia**: Puedes colocar un identificador que se puede resolver para una confirmación en la URL, incluidos los nombres de las ramas, los SHA de confirmación específicos o las etiquetas. + +{% endtip %} + +### Crear un enlace permanente a un fragmento de código + +Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. Para obtener más información, consulta "[Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)". + +### Further reading + +- "[Archivar un repositorio de GitHub](/articles/archiving-a-github-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/index.md b/translations/es-ES/content/github/managing-files-in-a-repository/index.md new file mode 100644 index 0000000000000..1622e3e3995b1 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/index.md @@ -0,0 +1,38 @@ +--- +title: Administrar archivos en un repositorio +redirect_from: + - /categories/81/articles/ + - /categories/manipulating-files/ + - /categories/managing-files-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-files-on-github %} + {% link_in_list /navigating-code-on-github %} + {% link_in_list /creating-new-files %} + {% link_in_list /adding-a-file-to-a-repository %} + {% link_in_list /moving-a-file-to-a-new-location %} + {% link_in_list /editing-files-in-your-repository %} + {% link_in_list /editing-files-in-another-users-repository %} + {% link_in_list /tracking-changes-in-a-file %} + {% link_in_list /deleting-files-in-a-repository %} + {% link_in_list /renaming-a-file %} + {% link_in_list /getting-permanent-links-to-files %} +{% topic_link_in_list /managing-files-using-the-command-line %} + {% link_in_list /adding-a-file-to-a-repository-using-the-command-line %} + {% link_in_list /renaming-a-file-using-the-command-line %} + {% link_in_list /moving-a-file-to-a-new-location-using-the-command-line %} +{% topic_link_in_list /working-with-non-code-files %} + {% link_in_list /rendering-and-diffing-images %} + {% link_in_list /3d-file-viewer %} + {% link_in_list /rendering-csv-and-tsv-data %} + {% link_in_list /rendering-pdf-documents %} + {% link_in_list /rendering-differences-in-prose-documents %} + {% link_in_list /mapping-geojson-files-on-github %} + {% link_in_list /working-with-jupyter-notebook-files-on-github %} diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md new file mode 100644 index 0000000000000..d82bfea3790b1 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md @@ -0,0 +1,12 @@ +--- +title: Administrar archivos en GitHub +intro: 'En {% data variables.product.product_name %}, puedes crear, editar, mover y eliminar archivos en un repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/managing-files-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md new file mode 100644 index 0000000000000..bba985f058b5c --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md @@ -0,0 +1,12 @@ +--- +title: Administrar archivos utilizando la línea de comando +intro: 'Utilizando la línea de comando, puedes agregar, renombrar y mover archivos en un repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/managing-files-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md new file mode 100644 index 0000000000000..5c1eb239a320a --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md @@ -0,0 +1,80 @@ +--- +title: Mapear archivos geoJSON en GitHub +redirect_from: + - /articles/mapping-geojson-files-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data variables.product.product_name %} admite representar archivos de mapa geoJSON y topoJSON dentro de repositorios {% data variables.product.product_name %}. Simplemente confirma el archivo como lo harías normalmente utilizando una extensión `.geojson` o `.topojson`. También se admiten archivos con una extensión `.json`, pero únicamente si `type` están configurados para `FeatureCollection`, `GeometryCollection`, o `topology`. Después, navega hasta la ruta del archivo geoJSON en GitHub.com. + +Cuando haces clic en el ícono de papel a la derecha, también verás los cambios realizados a ese archivo como parte de una confirmación de cambios. + +![Captura de pantalla de conmutación de representación de fuente](/assets/images/help/repository/source-render-toggle-geojson.png) + +### Tipos de Geometry + +Los mapas en {% data variables.product.product_name %} utilizan [Leaflet.js](http://leafletjs.com) y admiten todos los tipos de Geometry indicados en [las especificaciones de geoJSON](http://www.geojson.org/geojson-spec.html) (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon y GeometryCollection). Los archivos TopoJSON deberían ser del tipo "Topology" y adherir a las especificaciones [topoJSON](https://github.com/mbostock/topojson/wiki/Specification). + +### Características de estilo + +Puedes personalizar la manera en que se muestran las características, como especificar un color particular o agregar un ícono descriptivo, al pasar metadatos adicionales dentro de las propiedades del objeto geoJSON. Las opciones son: + +* `marker-size` - `small`, `medium`, o `large` +* `marker-color` - color RGB hex válido +* `marker-symbol` - un ID del ícono del [proyecto Maki ](http://mapbox.com/maki/) o un carácter único alfanumérico (a-z o 0-9). +* `stroke` - color de una línea o borde de un polígono (RGB) +* `stroke-opacity` - opacidad de una línea o borde de un polígono (0.0 - 1.0) +* `stroke-width` - ancho de una línea o borde de un polígono +* `fill` - el color del interior de un polígono (GRB) +* `fill-opacity` - la opacidad del interior de un polígono (0.0-1.0) + +Consulta la versión [1.1.0 de las especificaciones de estilo simple abierto](https://github.com/mapbox/simplestyle-spec/tree/master/1.1.0) para obtener más información. + +### Incrustrar tu mapa en otro lugar + +Deseas hacer disponible tu mapa geoJSON en un lugar distinto a {% data variables.product.product_name %}? Simplemente modifica esta plantilla, y colócala en alguna página HTML que admita javascript (p. ej., [{% data variables.product.prodname_pages %}](http://pages.github.com)): + +```html + +``` + +Por ejemplo, si la URL de tu mapa es [github.com/benbalter/dc-wifi-social/blob/master/bars.geojson](https://github.com/benbalter/dc-wifi-social/blob/master/bars.geojson), tu código de incrustación sería: + +```html + +``` + +Por defecto, el mapa incrustado es 420px x 620px, pero puedes personalizar el resultado al pasar variables de alto y ancho como parámetros al final, como `?height=300&width=500`. + +{% tip %} + +**Nota**: `ref` puede ser una rama del hash para una confirmación individual (como `2391ae`). + +{% endtip %} + +### Agrupación + +Si tu mapa contiende una gran cantidad de marcadores (aproximadamente más de 750), GitHub automáticamente agrupará marcadores cercanos en niveles superiores de zoom. Simplemente haz clic la agrupación o el zoom de acercamiento para ver los marcadores individuales. + +### Algo sucede con el mapa subyacente + +Los datos del mapa subyacente (nombres de calles, caminos, etc.) están controlados por [OpenStreetMap](http://www.openstreetmap.org/), un proyecto colaborativo para crear un mapa editable gratuito del mundo. Si notas que algo no está del todo bien, ya que es código abierto, simplemente [sign up](https://www.openstreetmap.org/user/new) y envía un arreglo. + +### Solución de problemas + +Si estás teniendo problemas al representar archivos geoJSON, asegúrate que tienes un archivo geoJSON válido al ejecutarlo en un [limpiador de geoJSON](http://geojsonlint.com/). Si tus puntos no aparecen donde lo esperas (p. ej., aparecen en la mitad del océano), es probable que los datos estén en una proyección que actualmente no se admite. Actualmente, {% data variables.product.product_name %} admite únicamente la proyección `urn:ogc:def:crs:OGC:1.3:CRS84`. + +Por otra parte, si tu archivo `.geojson` es particularmente grande (superior a 10 MB), no es posible representarlo dentro del navegador. Si ese es el caso, por lo general verás un mensaje similar a este: + +![Archivo de gran tamaño](/assets/images/help/repository/view_raw.png) + +Todavía se podrían representar los datos al convertir el archivo `.geojson` a [TopoJSON](https://github.com/mbostock/topojson), un formato de compresión que, en algunos casos, puede reducir el tamaño del archivo hasta un 80 %. Por supuesto, siempre puedes partir el archivo en fragmentos más pequeños (como por estado o por año), y almacenar los datos como archivos múltiples dentro del repositorio. + +### Recursos adicionales + +* [Documentación Leaflet.js geojson](http://leafletjs.com/examples/geojson.html) +* [Documentación de estilización de marcador MapBox](http://www.mapbox.com/developers/simplestyle/) +* [TopoJSON Wiki](https://github.com/mbostock/topojson/wiki) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md new file mode 100644 index 0000000000000..679ca90635e3a --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md @@ -0,0 +1,62 @@ +--- +title: Mover un archivo a una nueva ubicación utilizando la línea de comando +intro: Puedes utilizar la línea de comando para mover archivos dentro de un repositorio al eliminar el archivo de la ubicación anterior y después agregarlo en la nueva ubicación. +redirect_from: + - /articles/moving-a-file-to-a-new-location-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Muchos archivos pueden [moverse directamente en {% data variables.product.product_name %}](/articles/moving-a-file-to-a-new-location), pero algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. + +{% data reusables.command_line.manipulating_file_prereqs %} + +1. En la computadora, mueve el archivo a una nueva ubicación dentro del directorio que fue creado localmente en tu computadora cuando clonaste el repositorio. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Utiliza `git status` para verificar la nueva ubicación y la ubicación anterior del archivo. + ```shell + $ git status + > # On branch your-branch + > # Changes not staged for commit: + > # (use "git add/rm ..." to update what will be committed) + > # (use "git checkout -- ..." to discard changes in working directory) + > # + > # deleted: /old-folder/image.png + > # + > # Untracked files: + > # (use "git add ..." to include in what will be committed) + > # + > # /new-folder/image.png + > # + > # no changes added to commit (use "git add" and/or "git commit -a") + ``` +{% data reusables.git.stage_for_commit %} Esto eliminará, o `git rm`, el archivo de la ubicación antigua y agregará, o `git add`, el archivo en la nueva ubicación. + ```shell + $ git add . + # Agrega el archivo a tu repositorio local y lo presenta para la confirmación. + # {% data reusables.git.unstage-codeblock %} + ``` +5. Utiliza `git status` para verificar los cambios preparados para confirmar. + ```shell + $ git status + > # On branch your-branch + > # Changes to be committed: + > # (use "git reset HEAD ..." to unstage) + > # + > # renamed: /old-folder/image.png -> /new-folder/image.png + # Displays the changes staged for commit + ``` +{% data reusables.git.commit-file %} + ```shell + $ git commit -m "Move file to new directory" + # Commits the tracked changes and prepares them to be pushed to a remote repository. + # {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +{% data reusables.git.git-push %} + +### Further reading + +- "[Renombrar un archivo utilizando la línea de comando](/articles/renaming-a-file-using-the-command-line)" +- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md new file mode 100644 index 0000000000000..4cf1f5b0c08e9 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md @@ -0,0 +1,31 @@ +--- +title: Mover un archivo a una nueva ubicación +intro: 'Cuando editas un archivo, puedes elegir moverlo a cualquier lugar dentro de tu repositorio, incluso si el directorio no existe.' +redirect_from: + - /articles/moving-a-file-to-a-new-location +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Además de cambiar la ubicación del archivo, también puedes [actualizar los contenidos de tu archivo](/articles/editing-files-in-your-repository), o [darle un nuevo nombre](/articles/renaming-a-file) en la misma confirmación. + +{% tip %} + +**Tips**: + +- Si tratas de mover un archivo en un repositorio al cual no tienes acceso, bifurcaremos el proyecto a tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de confirmar tu cambio. +- Algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. Para obtener más información, consulta "[Mover un archivo a una nueva ubicación utilizando la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)". +- {% data reusables.repositories.protected-branches-block-web-edits-uploads %} + +{% endtip %} + +1. En tu repositorio, navega hasta el archivo que deseas mover. +2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/move-file-edit-file-icon.png) +3. En el campo de nombre de archivo, cambia el nombre del archivo utilizando estos lineamientos: ![Editar el nombre del archivo](/assets/images/help/repository/moving_files.gif) + - Para mover el archivo **dentro de una subcarpeta**, escribe el nombre de la carpeta que deseas, seguido de `/`. El nombre de tu nueva carpeta se convierte en el nuevo elemento en la ruta de navegación. + - Para mover el archivo dentro de un directorio **encima de la ubicación actual del archivo**, coloca tu cursor al comienzo del campo de nombre de archivo, después escribe `../` para subir un nivel completo de directorio, o presiona la tecla de `retroceso` para editar el nombre de la carpeta padre. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md new file mode 100644 index 0000000000000..f3961f36619f7 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -0,0 +1,42 @@ +--- +title: Código de navegación en GitHub +intro: 'Puedes comprender las relaciones dentro y a través de los repositorios al navegar directamente por código en {% data variables.product.product_name %}.' +redirect_from: + - /articles/navigating-code-on-github +versions: + free-pro-team: '*' +--- + +### Acerca de la navegación de código en {% data variables.product.prodname_dotcom %} + +Las funciones del código de navegación usan la biblioteca de código abierto [semántica](https://github.com/github/semantic). Los siguientes idiomas son compatibles: +- C# +- CodeQL +- Go +- Java +- JavaScript +- PHP +- Python +- Ruby +- TypeScript + +{% note %} + +**Nota**: La navegación de código funciona para las ramas activas. Si tienes la función habilitada pero no ves los enlaces a las definiciones de las funciones y los métodos, sube a la rama y trata nuevamente. + +{% endnote %} + +### Saltar a la definición de una función o método + +Puedes saltar a una definición de función o de método dentro del mismo repositorio si das clic en la llamada a dicha función o método dentro de un archivo. + +![Pestaña Jump-to-definition](/assets/images/help/repository/jump-to-definition-tab.png) + +### Buscar todas las referencias de una función o método + +Puedes encontrar todas las referencias para una función o método dentro del mismo repositorio si das clic en el llamado a dicha función o método en un archivo y posteriormente das clic en la pestaña de **Referencias**. + +![Pestaña Find all references (Buscar todas las referencias)](/assets/images/help/repository/find-all-references-tab.png) + +### Further reading +- "[Buscar código](/github/searching-for-information-on-github/searching-code)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md new file mode 100644 index 0000000000000..d7b1fa872077a --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md @@ -0,0 +1,42 @@ +--- +title: Renombrar un archivo usando la línea de comando +intro: Puedes usar la línea de comando para renombrar cualquier archivo de tu repositorio. +redirect_from: + - /articles/renaming-a-file-using-the-command-line +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Muchos archivos se pueden [renombrar directamente en {% data variables.product.product_name %}](/articles/renaming-a-file), pero algunos, como las imágenes, requieren que los renombres desde la línea de comando. + +{% data reusables.command_line.manipulating_file_prereqs %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.switching_directories_procedural %} +3. Renombra el archivo, especificando el nombre de archivo antiguo y el nombre de archivo nuevo que le quieres asignar. Esto preparará tu cambio para la confirmación. + ```shell + $ git mv old_filename new_filename + ``` +4. Utiliza `git status` para comprobar los nombres de archivo antiguo y nuevo. + ```shell + $ git status + > # On branch your-branch + > # Changes to be committed: + > # (use "git reset HEAD ..." to unstage) + > # + > # renamed: old_filename -> new_filename + > # + ``` +{% data reusables.git.commit-file %} + ```shell + $ git commit -m "Rename file" + # Commits the tracked changes and prepares them to be pushed to a remote repository. + # {% data reusables.git.reset-head-to-previous-commit-codeblock %} + ``` +{% data reusables.git.git-push %} + +### Further reading +- "[Mover un archivo a una ubicación nueva mediante la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)" +- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file.md b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file.md new file mode 100644 index 0000000000000..6a47ebc875a06 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file.md @@ -0,0 +1,27 @@ +--- +title: Renombrar un archivo +intro: 'Puedes renombrar cualquier archivo de tus repositorios directamente en {% data variables.product.product_name %}. Renombrar un archivo también te da la posibilidad de [mover el archivo a una ubicación nueva](/articles/moving-a-file-to-a-new-location).' +redirect_from: + - /articles/renaming-a-file +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Tips**: + +- Si intentas renombrar un archivo de un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de que confirmes tu cambio. +- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para utilizar otros caracteres, crea y confirma los archivos de forma local y luego súbelos al repositorio. +- Algunos archivos, como las imágenes, requieren que los renombres desde la línea de comando. Para obtener más información, consulta "[Renombrar un archivo usando la línea de comando](/articles/renaming-a-file-using-the-command-line)". + +{% endtip %} + +1. En tu repositorio, busca el archivo que quieres renombrar. +2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/edit-file-icon.png) +3. En el campo de nombre del archivo, cambia el nombre del archivo con el nombre de archivo nuevo que quieras. También puedes actualizar los contenidos de tu archivo en el mismo momento. ![Editar el nombre del archivo](/assets/images/help/repository/changing-file-name.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md new file mode 100644 index 0000000000000..915488d983452 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md @@ -0,0 +1,46 @@ +--- +title: Representar y comparar imágenes +intro: '{% data variables.product.product_name %} puede mostrar varios formatos de imagen comunes, incluidos PNG, JPG, GIF, PSD y SVG. Asimismo, para simplificar mostrarlas, existen diversas formas de comparar las diferencias entre las versiones de esos formatos de imagen.' +redirect_from: + - /articles/rendering-and-diffing-images +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Si estás utilizando el navegador Firefox, puede que los SVG en {% data variables.product.prodname_dotcom %} no se representen. + +{% endnote %} + +### Ver imágenes + +Puedes navegar y ver imágenes directamente en tu {% data variables.product.product_name %} repositorio: + +![imagen alineada](/assets/images/help/images/view.png) + +Los SVG actualmente no admiten scripting alineado o animación. + +### Ver diferencias + +Puedes comparar visualmente las imágenes de tres modos diferentes: [2-up](#2-up), [deslizar](#swipe) y [papel cebolla](#onion-skin). + +#### 2-up + +**2-up** es el modo predeterminado; te muestra una descripción rápida de ambas imágenes. Asimismo, si la imagen cambió de tamaño entre las versiones, se muestra el cambio de dimensión real. Esto debería ser muy evidente cuando las cosas cambian de tamaño, como cuando los activos se suben de categoría a resoluciones más altas. + +![2-up](/assets/images/help/repository/images-2up-view.png) + +#### Deslizar + +**Deslizar**te deja ver partes de tus imágenes. ¿No estás seguro de si cambiaron los colores en las diferentes versiones? Arrastra el control deslizante de deslizamiento sobre el área en cuestión y compara los píxeles tú mismo. + +![Deslizar](/assets/images/help/repository/images-swipe-view.png) + +#### Papel cebolla + +**Papel cebolla** realmente ayuda cuando los elementos apenas se desplazan y cuesta percibir el cambio. ¿Un icono se corrió dos píxeles a la izquierda? Arrastra el control deslizante de opacidad hacia atrás un poco y comprueba si las cosas se desplazaron. + +![Papel cebolla](/assets/images/help/repository/images-onion-view.gif) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md new file mode 100644 index 0000000000000..3a86865725ced --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -0,0 +1,34 @@ +--- +title: Representar datos CSV y TSV +redirect_from: + - /articles/rendering-csv-and-tsv-data +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +GitHub admite la representación de datos tabulares en la forma de archivos *.csv* (separados por coma) y .*tsv* (separados por pestaña). + +![Muestra de CSV representado](/assets/images/help/repository/rendered_csv.png) + +Cuando se visualiza, cualquier archivo _.csv_ o _.tsv_ confirmado en un repositorio de {% data variables.product.product_name %} se representa automáticamente como una tabla interactiva, completa con encabezados y numeración de filas. Por defecto, siempre asumimos que la primera fila es tu fila de encabezados. + +Puedes generar un enlace a una fila particular haciendo clic en el número de fila o seleccionar varias filas manteniendo presionada la tecla shift. Tan solo copia la URL y envíasela a un amigo. + +### Buscar datos + +Si quieres encontrar un valor determinado en tu conjunto de datos, puedes comenzar escribiendo en la barra de búsqueda directamente arriba del archivo. The rows will filter automatically: + +![Buscar valores](/assets/images/help/repository/searching_csvs.gif) + +### Manejar errores + +De manera ocasional, puede que descubras que tu archivo CSV o TSV no se representa. En esas instancias, aparece un cuadro de error al pie del texto original que sugiere cuál puede ser el error. + +![Mensaje de error de representación de CSV](/assets/images/help/repository/csv_render_error.png) + +Los errores comunes incluyen los siguientes: + +* Conteos de columnas que no coinciden. Debes tener la misma cantidad de separadores en cada fila, incluso si la celda está en blanco +* Superar el tamaño de archivo. Nuestra representación solo funciona para archivos de hasta 512KB. Cualquier cosa más grande hace que el navegador se vuelva más lento. diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md new file mode 100644 index 0000000000000..7053df0ea9a14 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md @@ -0,0 +1,59 @@ +--- +title: Representar diferencias en documentos en prosa +redirect_from: + - /articles/rendering-differences-in-prose-documents +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las confirmaciones y solicitudes de extracción que incluyen documentos en prosa tienen la capacidad de representar esos documentos con vistas *de origen* y *representadas*. + +La vista de origen muestra el texto en bruto que se escribió, mientras que la vista representada muestra la manera en que ese texto se vería una vez que se represente en {% data variables.product.product_name %}. Por ejemplo, esto puede ser la diferencia entre mostrar `**negrita**` en Markdown y **negrita** en la vista representada. + +Se admite la representación en prosa para documentos representados compatibles con [github/markup](https://github.com/github/markup): + +* Markdown +* AsciiDoc +* Textile +* ReStructuredText +* Rdoc +* Org +* Creole +* MediaWiki +* Pod + +![Icono Paper (Papel) para ver el documento en prosa representado](/assets/images/help/repository/rendered_prose_diff.png) + +Puedes hacer clic en {% octicon "file" aria-label="The paper icon" %} para ver los cambios hechos al documento como parte de una confirmación. + +![Cambios en prosa representados](/assets/images/help/repository/rendered_prose_changes.png) + +### Ver los cambios del atributo + +Proporcionamos una información de herramienta que describe los cambios en los atributos que, a diferencia de las palabras, no serían visibles en el documento representado. Por ejemplo, si la URL de un enlace cambia de un sitio web a otro, mostraríamos una información de herramienta como la siguiente: + +![Cambios en atributos de la prosa representados](/assets/images/help/repository/prose_diff_attributes.png) + +### Comentar cambios + +Solo se pueden agregar [comentarios de la confirmación](/articles/commenting-on-differences-between-files) en los archivos dentro de la vista *de origen*, línea por línea. + +### Vincular a encabezados + +Como con [otros documentos en prosa representados](/articles/about-readmes), deslizarse sobre un encabezado de tu documento crea un icono de enlace. Puedes vincular a los lectores de tu diferencia de prosa representada a secciones específicas. + +### Ver diferencias complejas + +Algunas solicitudes de extracción incluyen una gran cantidad de cambios con documentos grandes y complejos. Cuando los cambios toman demasiado tiempo en su análisis, {% data variables.product.product_name %} no siempre puede producir una vista renderizada de los cambios. Si esto pasa, verás un mensaje de error cuando das clic en el botón renderizado. + +![Mensaje cuando la vista no se puede renderizar](/assets/images/help/repository/prose_diff_rendering.png) + +Aún puedes utilizar la vista de origen para analizar y comentar cambios. + +### Ver elementos HTML + +No admitimos directamente vistas representadas de confirmaciones en documentos HTML. Algunos formatos, como Markdown, te permiten insertar HTML arbitrarios en un documento. Cuando estos documentos se muestran en {% data variables.product.product_name %}, algunos de esos HTML insertados pueden aparecer en una vista previa, mientras que con otros no es posible hacerlo (como un video de YouTube insertado). + +En general, las vistas representadas de los cambios en un documento que contiene HTML insertados mostrarán los cambios en los elementos que se admiten en la vista del documento de {% data variables.product.product_name %}. Los cambios en los documentos que contienen HTML insertados siempre se deben verificar en las vistas de origen y representada para corroborar que estén todos. diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-pdf-documents.md b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-pdf-documents.md new file mode 100644 index 0000000000000..09f0da97246ad --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-pdf-documents.md @@ -0,0 +1,15 @@ +--- +title: Representar documentos PDF +redirect_from: + - /articles/rendering-pdf-documents +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +GitHub admite la representación de documentos PDF. + +![Documento PDF representado](/assets/images/help/repository/rendered-pdf.png) + +Actualmente, se ignoran los enlaces dentro de los PDF. diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md b/translations/es-ES/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md new file mode 100644 index 0000000000000..54c3051dc0345 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md @@ -0,0 +1,31 @@ +--- +title: Rastrear cambios en un archivo +intro: Puedes rastrear cambios de líneas en un archivo y descubrir la manera en que las partes del archivo fueron evolucionando. +redirect_from: + - /articles/using-git-blame-to-trace-changes-in-a-file/ + - /articles/tracing-changes-in-a-file/ + - /articles/tracking-changes-in-a-file +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Con la vista de último responsable, puedes ver el historial de revisión línea por línea para todo un archivo o ver el historial de revisión de una única línea dentro de un archivo haciendo clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que hagas clic en {% octicon "versions" aria-label="The prior blame icon" %}, verás la información de revisión anterior para esa línea, incluido quién y cuándo confirmó el cambio. + +![Vista de último responsable de Git](/assets/images/help/repository/git_blame.png) + +En un archivo o solicitud de extracción, también puedes utilizar el menú {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para ver el último responsable de Git para una línea o rango de líneas seleccionado. + +![Menú Kebab con opciones para ver el último responsable de Git para una línea seleccionada](/assets/images/help/repository/view-git-blame-specific-line.png) + +{% tip %} + +**Sugerencia:** En la línea de comando, también puedes utilizar `git blame` para ver el historial de revisión de líneas dentro de un archivo. Para obtener más información, consulta la documentación de [ `git blame`](https://git-scm.com/docs/git-blame) de Git. + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Haz clic para abrir el archivo cuyo historial de líneas quieres ver. +3. En la esquina superior derecha de la vista del archivo, haz clic en **Blame** (Último responsable) para abrir la vista del último responsable. ![Botón Blame (Último responsable)](/assets/images/help/repository/blame-button.png) +4. Para ver versiones anteriores de una línea específica, o el siguiente último responsable, haz clic en {% octicon "versions" aria-label="The prior blame icon" %} hasta que hayas encontrado los cambios que quieres ver. ![Botón Prior blame (Último responsable anterior)](/assets/images/help/repository/prior-blame-button.png) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md new file mode 100644 index 0000000000000..6e292a3a6c2ce --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md @@ -0,0 +1,30 @@ +--- +title: Trabajar con archivos notebook Jupyter en GitHub +intro: 'Cuando agregas archivos notebook Jupyter o notebook iPython con una extensión *.ipynb* en {% data variables.product.product_location %}, se representarán como archivos HTML estáticos en tu repositorio.' +redirect_from: + - /articles/working-with-jupyter-notebook-files-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Las funciones interactivas de notebook, como los gráficos JavaScript personalizados, no funcionarán en tu repositorio en {% data variables.product.product_location %}. Para obtener un ejemplo, consulta [*Enlaces e interacciones.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). + +Para ver tu notebook Jupyter con el contenido representado de JavaScript o para compartir tus archivos notebook con otros, puedes usar [nbviewer](https://nbviewer.jupyter.org/). Para obtener un ejemplo, consulta [*Enlaces e interacciones.ipynb*](https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb) representados en nbviewer. + +Para ver una versión completamente interactiva de tu notebook Jupyter, puedes configurar un servidor notebook de manera local. Para obtener más información, consulta [Documentación oficial de Jupyter](http://jupyter.readthedocs.io/en/latest/index.html). + +### Solución de problemas + +Si tienes problemas para representar los archivos notebook Jupyter en HTML estático, puedes convertir el archivo de forma local en la línea de comando usando el comando [`nbconvert`](https://github.com/jupyter/nbconvert): + +```shell +$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb +``` + +### Further reading + +- [Repositorio GitHub de notebook Jupyter](https://github.com/jupyter/jupyter_notebook) +- [Galería de notebooks Jupyter](https://github.com/jupyter/jupyter/wiki/A-gallery-of-interesting-Jupyter-Notebooks) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md new file mode 100644 index 0000000000000..04afb106f5bb1 --- /dev/null +++ b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md @@ -0,0 +1,13 @@ +--- +title: Trabajar con archivos sin código +intro: '' +mapTopic: verdadero +redirect_from: + - /categories/89/articles/ + - /articles/working-with-non-code-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md new file mode 100644 index 0000000000000..e1b42b0c998ab --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md @@ -0,0 +1,55 @@ +--- +title: Acerca de Large File Storage de Git +intro: '{% data variables.large_files.product_name_short %}te permite subir los archivos que sean más grandes que el límite de subida en Git a {% data variables.product.product_name %}.' +redirect_from: + - /articles/about-large-file-storage/ + - /articles/about-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data variables.large_files.product_name_short %} maneja archivos grandes almacenando referencias del archivo en el repositorio, pero no el archivo real. Para trabajar en la arquitectura de Git, {% data variables.large_files.product_name_short %} crea un archivo puntero que actúa como una referencia del archivo real (que se almacena en otro lugar). {% data variables.product.product_name %} administra este archivo puntero en tu repositorio. Cuando clonas el repositorio, {% data variables.product.product_name %} usa el archivo puntero como un mapa para ir y buscar el archivo grande por ti. + +{% if currentVersion == "free-pro-team@latest" %} +Cuando utilizas +{% data variables.large_files.product_name_short %}, puedes almacenar archivos de hasta: + +| Producto | Tamaño máximo de archivo | +| ------------------------------------------------- | ------------------------ | +| {% data variables.product.prodname_free_user %} | 2 GB | +| {% data variables.product.prodname_pro %} | 2 GB | +| {% data variables.product.prodname_team %} | 4 GB | +| {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} + Cuando utilizas +{% data variables.large_files.product_name_short %}, puedes almacenar archivos de hasta {% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} en tu repositorio. +{% endif %} + +Tambié puedes usar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de cómo clonar repositorios LFS de Git en {% data variables.product.prodname_desktop %}, consulta "[Cómo clonar un repositorio desde GitHub hasta GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". + +{% data reusables.large_files.can-include-lfs-objects-archives %} + +#### Formato de archivo puntero + +El archivo puntero de {% data variables.large_files.product_name_short %} se ve así: + +``` +version {% data variables.large_files.version_name %} +oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 +size 84977953 +``` + +Hace un seguimiento de la `version` de {% data variables.large_files.product_name_short %} que estás usando, seguido de un identificador único para el archivo (`oid`). También almacena el `size` del archivo final. + +{% note %} + +**Notas**: +- {% data variables.large_files.product_name_short %} no puede utilizarse con los sitios de {% data variables.product.prodname_pages %}. +- {% data variables.large_files.product_name_short %} no se puede utilizar con repositorios de plantilla. + +{% endnote %} + +### Further reading + +- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md new file mode 100644 index 0000000000000..a9d10f740297b --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -0,0 +1,46 @@ +--- +title: Acerca del uso de ancho de banda y del almacenamiento +intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}' +redirect_from: + - /articles/billing-plans-for-large-file-storage/ + - /articles/billing-plans-for-git-large-file-storage/ + - /articles/about-storage-and-bandwidth-usage +versions: + free-pro-team: '*' +--- + +{% data variables.large_files.product_name_short %} está disponible para cada repositorio en {% data variables.product.product_name %}, ya sea que tu cuenta u organización tenga o no una suscripción paga. + +### Hacer un seguimiento del uso de ancho de banda y del almacenamiento + +Cuando confirmas y subes un cambio a un archivo seguido con {% data variables.large_files.product_name_short %}, se sube una nueva versión del archivo completo y el tamaño total del archivo cuenta para el límite de almacenamiento del propietario del repositorio. Cuando descargas un archivo seguido con {% data variables.large_files.product_name_short %}, el tamaño total del archivo cuenta para el límite de ancho de banda del propietario del repositorio. Las cargas de {% data variables.large_files.product_name_short %} no cuentan para el lpimite de ancho de banda. + +Por ejemplo: +- Si subes un archivo de 500 MB a {% data variables.large_files.product_name_short %}, usarás 500 MB de tu almacenamiento asignado y nada de tu ancho de banda. Si realizas un cambio de 1 byte y subes el archivo de nuevo, usarás otros 500 MB de almacenamiento y no de ancho de banda, llevando tu uso total por esas dos subidas a 1 GB de almacenamiento y cero ancho de banda. +- Si descargas un archivo de 500 MB que es seguido con LFS, usarás 500 MB del ancho de banda asignado del propietario del repositorio. Si un colaborador sube un cambio al archivo y extraes la versión nueva a tu repositorio local, usarás otros 500 MB de ancho de banda, llevando el uso total por esas dos descargas a 1 GB de ancho de banda. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Si +los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluyen en los archivos de código fuente de tu repositorio. Las descargas de estos archivos contarán en el uso de ancho de banda del repositorio. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +{% endif %} + +{% tip %} + +**Tips**: +- {% data reusables.large_files.owner_quota_only %} +- {% data reusables.large_files.does_not_carry %} + +{% endtip %} + +### Cuota de almacenamiento + +Si utilizas más de {% data variables.large_files.initial_storage_quota %} de almacenamiento sin comprar un paquete de datos, aún puedes clonar repositorios con elementos grandes, pero solo podrás descargar los archivos puntero, y no podrás subir archivos nuevos otra vez. Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". + +### Cuota de ancho de banda + +Si usas más de {% data variables.large_files.initial_bandwidth_quota %} de ancho de banda por mes sin comprar un paquete de datos, el soporte de {% data variables.large_files.product_name_short %} se desactiva en tu cuenta hasta el próximo mes. + +### Further reading + +- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" +- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md new file mode 100644 index 0000000000000..e6a352c51020f --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md @@ -0,0 +1,43 @@ +--- +title: Colaboración con el almacenamiento de archivos de gran tamaño de Git +intro: 'Con {% data variables.large_files.product_name_short %} habilitado, podrás extraer, modificar y subir archivos de gran tamaño del mismo modo que lo harías con cualquier archivo que administre Git. Sin embargo, un usuario que no tiene {% data variables.large_files.product_name_short %} experimentará un flujo de trabajo diferente.' +redirect_from: + - /articles/collaboration-with-large-file-storage/ + - /articles/collaboration-with-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si los colaboradores en tu repositorio no tienen {% data variables.large_files.product_name_short %} instalado, no tendrán acceso al archivo de gran tamaño original. Si intentan clonar tu repositorio, solo extraerán los archivos punteros, y no tendrán acceso a los datos trues. + +{% tip %} + +**Tip:** Te recomendamos configurar lineamientos para los contribuyentes del repositorio, los cuales describan la forma de trabajar con archivos grandes, para todo usuario que no tenga {% data variables.large_files.product_name_short %} habilitado. Por ejemplo, puedes pedirles a los colaboradores que no modifiquen archivos de gran tamaño o que carguen los cambios a un servicio de intercambio de archivos como [Dropbox](http://www.dropbox.com/) o Google Drive. Para obtener más información, consulta "[Establecer pautas para los colaboradores del repositorio](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)". + +{% endtip %} + +### Ver archivos de gran tamaño en solicitudes de extracción + +{% data variables.product.product_name %} no representa {% data variables.large_files.product_name_short %} objectos en solicitudes de extracción. Únicamente se muestra el archivo de puntero: + +![Ejemplo de PR para archivos de gran tamaño](/assets/images/help/large_files/large_files_pr.png) + +Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". + +Para ver los cambios que se realizaron en los archivos grandes, verifica localmente la solicitud de extracción para revisar la diferencia. Para obtener más información, consulta la sección "[Revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". + +{% if currentVersion == "free-pro-team@latest" %} + +### Subir archivos de gran tamaño a bifurcaciones + +La subida de archivos de gran tamaño cuenta para el ancho de banda de un repositorio padre y las cuotas de almacenamiento, en lugar de hacerlo para las cuotas del propietario de la bifurcación. + +Puedes subir {% data variables.large_files.product_name_short %} objetos a las bifurcaciones públicas si la red del repositorio ya tiene {% data variables.large_files.product_name_short %} objetos o si tienes acceso de escritura a la raíz de la red del repositorio. + +{% endif %} + +### Further reading + +- "[Duplicar un repositorio con objetos de almacenamiento de gran tamaño de Git](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" diff --git a/translations/es-ES/content/github/managing-large-files/conditions-for-large-files.md b/translations/es-ES/content/github/managing-large-files/conditions-for-large-files.md new file mode 100644 index 0000000000000..e6ad60d87145a --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/conditions-for-large-files.md @@ -0,0 +1,20 @@ +--- +title: Condiciones para archivos grandes +intro: '{% data variables.product.product_name %} limita el tamaño permitido para los archivos de los repositorios y bloqueará una subida de información si estos superan el tamaño máximo.' +redirect_from: + - /articles/conditions-for-large-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.large_files.use_lfs_tip %} + +### Advertencia para archivos mayores a {% data variables.large_files.warning_size %} + +Recibirás una advertencia de Git si intentas añadir o actualizar un archivo mayor a {% data variables.large_files.warning_size %}. Los cambios aún se subirán a tu repositorio, pero puedes considerar eliminar la confirmación para minimizar el impacto en el rendimiento. Para obtener más información, consulta la sección "[Eliminar archivos del historial de un repositorio](/github/managing-large-files/removing-files-from-a-repositorys-history)". + +### Subidas bloquadas para archivos grandes + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Predeterminadamente, {% endif %}{% data variables.product.product_name %} bloquea las subidas que excedan {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Sin embargo, un administrador de sitio puede configurar un límite diferente para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Configurar los límites de subida de Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} diff --git a/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md new file mode 100644 index 0000000000000..79c36fb386239 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -0,0 +1,63 @@ +--- +title: Configurar el almacenamiento de archivos Git de gran tamaño +intro: 'Una vez que {[{% data variables.large_files.product_name_short %} está instalado], (/articles/installing-git-large-file-storage/), deberás asociarlo con un archivo de gran tamaño en tu repositorio.' +redirect_from: + - /articles/configuring-large-file-storage/ + - /articles/configuring-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si hay archivos existentes en tu repositorio con los que te gustaría usar {% data variables.product.product_name %}, primero debes eliminarlos del repositorio y luego agregarlas a {% data variables.large_files.product_name_short %} localmente. Para obtener más información, consulta "[Mover un archivo en tu repositorio a {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)". + +{% data reusables.large_files.resolving-upload-failures %} + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + +{% tip %} + +**Nota:** Antes de que intentes subir un archivo grande a {% data variables.product.product_name %}, asegúrate de haber habilitado {% data variables.large_files.product_name_short %} en tu empresa. Para obtener más información, consulta "[Configurar almacenamiento de archivos Git de gran tamaño en GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)". + +{% endtip %} + +{% endif %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambia tu directorio de trabajo actual a un repositorio existente que desees usar con {% data variables.large_files.product_name_short %}. +3. Para asociar un tipo de archivo en tu repositorio con {% data variables.large_files.product_name_short %}, escribe `git {% data variables.large_files.command_name %} track` seguido por el nombre de la extensión de archivo a la que deseas cargar automáticamente {% data variables.large_files.product_name_short %}. + + Por ejemplo, para asociar un archivo _.psd_, escribe el siguiente comando: + ```shell + $ git {% data variables.large_files.command_name %} track "*.psd" + > Adding path *.psd + ``` + Cada tipo de archivo que desees asociar con {% data variables.large_files.product_name_short %} deberá agregarse con `got{% data variables.large_files.command_name %} track`. Este comando enmienda tu archivo *.gitattributes* del repositorio y asocia archivos de gran tamaño {% data variables.large_files.product_name_short %}. + + {% tip %} + + **Sugerencia:** Sugerimos enfáticamente que confirmes el archivo *.gitattributes* local en tu repositorio. Basándose en un archivo global *.gitattributes* asociado con {% data variables.large_files.product_name_short %} puede causar conflictos al contribuir con otros proyectos Git. + + {% endtip %} + +4. Agrega un archivo al repositorio que coincide con la extensión que has asociado: + ```shell + $ git add path/to/file.psd + ``` +5. Confirma el archivo y súbelo a {% data variables.product.product_name %}: + ```shell + $ git commit -m "add file.psd" + $ git push + ``` + Deberías ver información de diagnóstico sobre la carga del archivo: + ```shell + > Sending file.psd + > 44.74 MB / 81.04 MB 55.21 % 14s + > 64.74 MB / 81.04 MB 79.21 % 3s + ``` + +### Further reading + +- "[Colaboraciones con {% 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@3.0" or currentVersion == "github-ae@latest" %} +- "[Administrar objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/es-ES/content/github/managing-large-files/distributing-large-binaries.md b/translations/es-ES/content/github/managing-large-files/distributing-large-binaries.md new file mode 100644 index 0000000000000..6591308842d77 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/distributing-large-binaries.md @@ -0,0 +1,20 @@ +--- +title: Distribuir binarios grandes +intro: 'Algunos proyectos requieren la distribución de archivos grandes, como los binarios o instaladores, además de la distribución del código fuente.' +redirect_from: + - /articles/distributing-large-binaries +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %}. Los lanzamientos te permiten empaquetar el software, notas de lanzamiento y enlaces a los archivos binarios para que otras personas puedan utilizarlos. Para obtener más información, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)". + +{% if currentVersion == "free-pro-team@latest" %} + +No limitamos el tamaño total de los archivos binarios en los lanzamientos o anchos de banda que se utilizan para entregarlos. Sin embargo, cada archivo individual debe ser menor a {% data variables.large_files.max_lfs_size %}. + +{% endif %} + +{% data reusables.large_files.use_lfs_tip %} diff --git a/translations/es-ES/content/github/managing-large-files/index.md b/translations/es-ES/content/github/managing-large-files/index.md new file mode 100644 index 0000000000000..c60fc1f30ab7d --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/index.md @@ -0,0 +1,27 @@ +--- +title: Administrar archivos grandes +redirect_from: + - /categories/managing-large-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /working-with-large-files %} + {% link_in_list /conditions-for-large-files %} + {% link_in_list /removing-files-from-a-repositorys-history %} + {% link_in_list /distributing-large-binaries %} + {% link_in_list /what-is-my-disk-quota %} +{% topic_link_in_list /versioning-large-files %} + {% link_in_list /about-git-large-file-storage %} + {% link_in_list /installing-git-large-file-storage %} + {% link_in_list /configuring-git-large-file-storage %} + {% link_in_list /about-storage-and-bandwidth-usage %} + {% link_in_list /collaboration-with-git-large-file-storage %} + {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} + {% link_in_list /removing-files-from-git-large-file-storage %} + {% link_in_list /resolving-git-large-file-storage-upload-failures %} diff --git a/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md new file mode 100644 index 0000000000000..959d37d5b97d3 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md @@ -0,0 +1,114 @@ +--- +title: Instalar Git Large File Storage +intro: 'Para utilizar {% data variables.large_files.product_name_short %}, tendrás que descargar e instalar un programa nuevo, además de Git.' +redirect_from: + - /articles/installing-large-file-storage/ + - /articles/installing-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% mac %} + +1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). También puedes instalar {% data variables.large_files.product_name_short %} utilizando un administrador de paquete: + - Para utilizar [Homebrew](http://brew.sh/), ejecuta `brew install git-lfs`. + - Para utilizar [MacPorts](https://www.macports.org/), ejecuta `port install git-lfs`. + + Si instalas {% data variables.large_files.product_name_short %} con Homebrew o MacPorts, dirígete al paso seis. + +2. En tu computadora, ubica y descomprime el archivo descargado. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo. + ```shell + $ cd ~/Downloads/git-lfs-1.X.X + ``` + {% note %} + + **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}. + + {% endnote %} +4. Para instalar el archivo, ejecuta este comando: + ```shell + $ ./install.sh + > {% data variables.large_files.product_name_short %} initialized. + ``` + {% note %} + + **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo. + + {% endnote %} +5. Verifica que la instalación haya sido exitosa: + ```shell + $ git {% data variables.large_files.command_name %} install + > {% data variables.large_files.product_name_short %} initialized. + ``` +6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. + +{% endmac %} + +{% windows %} + +1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). + + {% tip %} + + **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Windows, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started). + + {% endtip %} +2. En tu computadora, ubica el archivo descargado. +3. Haz doble clic en el archivo llamado *git-lfs-windows-1.X.X.exe*, donde 1.X.X se reemplazará con la versión LFS de Git que descargaste. Cuando abres este archivo, Windows ejecutará un asistente de configuración para instalar +{% data variables.large_files.product_name_short %}. +{% data reusables.command_line.open_the_multi_os_terminal %} +5. Verifica que la instalación haya sido exitosa: + ```shell + $ git {% data variables.large_files.command_name %} install + > {% data variables.large_files.product_name_short %} initialized. + ``` +6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. + +{% endwindows %} + +{% linux %} + +1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). + + {% tip %} + + **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Linux, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started). + + {% endtip %} +2. En tu computadora, ubica y descomprime el archivo descargado. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo. + ```shell + $ cd ~/Downloads/git-lfs-1.X.X + ``` + {% note %} + + **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}. + + {% endnote %} +4. Para instalar el archivo, ejecuta este comando: + ```shell + $ ./install.sh + > {% data variables.large_files.product_name_short %} initialized. + ``` + {% note %} + + **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo. + + {% endnote %} +5. Verifica que la instalación haya sido exitosa: + ```shell + $ git {% data variables.large_files.command_name %} install + > {% data variables.large_files.product_name_short %} initialized. + ``` +6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. + +{% endlinux %} + +### Further reading + +- "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md new file mode 100644 index 0000000000000..eaa8a44ac432d --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md @@ -0,0 +1,29 @@ +--- +title: Mover un archivo en tu repositorio a Git Large File Storage +intro: 'Si has configurado {% data variables.large_files.product_name_short %}, y tienes un archivo existente en tu repositorio que debe ser rastreado en {% data variables.large_files.product_name_short %}, debes primero eliminarlo de tu repositorio.' +redirect_from: + - /articles/moving-a-file-in-your-repository-to-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Después de instalar {% data variables.large_files.product_name_short %} y configurar el rastreo de {% data variables.large_files.product_name_short %}, puedes mover archivos del rastreo habitual de Git hacia {% data variables.large_files.product_name_short %}. Para obtener más información, consulta la sección "[Instalar {% data variables.large_files.product_name_long %}](/github/managing-large-files/installing-git-large-file-storage)" y "[Configurar {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". + +{% data reusables.large_files.resolving-upload-failures %} + +{% tip %} + +**Sugerencia:** si te aparece un error "esto excede el límite de tamaño de archivo {% data variables.large_files.product_name_short %} de {% data variables.large_files.max_github_size %}" cuando tratas de subir archivos a Git, puedes utilizar `git lfs migrate` en lugar de `filter branch` o del BFG Repo Cleaner, para mover un archivo grande a {% data variables.large_files.product_name_long %}. Para obtener más información acerca del comando `git lfs migrate`, consulta el anuncio de lanzamiento de [Git LFS 2.2.0](https://github.com/blog/2384-git-lfs-2-2-0-released). + +{% endtip %} + +1. Elimina el archivo del historial del repositorio de Git utilizando el comando `filter-branch` o BFG Repo-Cleaner. Para obtener información detallada sobre sus usos, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". +2. Configura el rastreo para tu archivo y súbelo a {% data variables.large_files.product_name_short %}. Para obtener más información sobre este procedimiento, consulta "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)." + +### Further reading + +- "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" +- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" +- "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/removing-files-from-a-repositorys-history.md b/translations/es-ES/content/github/managing-large-files/removing-files-from-a-repositorys-history.md new file mode 100644 index 0000000000000..218765fef3cd6 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/removing-files-from-a-repositorys-history.md @@ -0,0 +1,45 @@ +--- +title: Eliminar archivos del historial de un repositorio +intro: 'Para eliminar un archivo grande de tu repositorio, debes eliminarlo por completo de tu repositorio local y de {% data variables.product.product_location %}.' +redirect_from: + - /articles/removing-files-from-a-repository-s-history + - /articles/removing-files-from-a-repositorys-history +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% warning %} + +**Advertencia**: Estos procedimientos eliminarán archivos de manera permanente del repositorio de tu computadora y de {% data variables.product.product_location %}. Si el archivo es importante, haz una copia de seguridad local en un directorio por fuera del repositorio. + +{% endwarning %} + +### Eliminar un archivo agregado en la confirmación más reciente no subida + +Si el archivo se agregó con tu confirmación más reciente, y no lo subiste a {% data variables.product.product_location %}, puedes eliminar el archivo y modificar la confirmación: + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.switching_directories_procedural %} +3. Para eliminar el archivo, ingresa a `git rm --cached`: + ```shell + $ git rm --cached giant_file + # Stage our giant file for removal, but leave it on disk + ``` +4. Confirma este cambio usando `--amend -CHEAD`: + ```shell + $ git commit --amend -CHEAD + # Amend the previous commit with your change + # Simply making a new commit won't work, as you need + # to remove the file from the unpushed history as well + ``` +5. Sube tus confirmaciones a {% data variables.product.product_location %}: + ```shell + $ git push + # Push our rewritten, smaller commit + ``` + +### Eliminar un archivo que se añadió en una confirmación de cambios previa + +Si añadiste un archivo en una confirmación previa, necesitas eliminarlo del historial del repositorio. Para eliminar archivos de la historia del repositorio, puedes utilizar BFG Repo-Cleaner o el comando `git filter-branch`. Para obtener más información, consulta la sección "[Eliminar datos sensibles de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". diff --git a/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md new file mode 100644 index 0000000000000..4389b8002c4d6 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md @@ -0,0 +1,53 @@ +--- +title: Eliminar archivos de Git Large File Storage +intro: 'Si has configurado {% data variables.large_files.product_name_short %} para tu repositorio, puedes eliminar todos los archivos o un subconjunto de archivos desde {% data variables.large_files.product_name_short %}.' +redirect_from: + - /articles/removing-files-from-git-large-file-storage +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Eliminar un único archivo + +1. Elimina el archivo del historial del repositorio de Git utilizando el comando `filter-branch` o BFG Repo-Cleaner. Para obtener información detallada sobre sus usos, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". +2. Navega hasta tu archivo *.gitattributes*. + + {% note %} + + **Nota:** Tu archivo *.gitattributes* generalmente se guarda dentro de tu repositorio local. En algunos casos, puede que hayas creado un archivo *.gitattributes* global que contiene todas tus {% data variables.large_files.product_name_short %} asociaciones. + + {% endnote %} +3. Encuentra y elimina la regla de seguimiento {% data variables.large_files.product_name_short %} asociada dentro del archivo *.gitattributes*. +4. Guarda y cierra el archivo *.gitattributes*. + +### Eliminar todos los archivos dentro de un repositorio {% data variables.large_files.product_name_short %} + +1. Eliminar los archivos del historial de Git del repositorio usando el comando `filter-branch` o BFG Repo-Cleaner. Para obtener información detallada sobre sus usos, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". +2. De manera opcional, para desinstalar {% data variables.large_files.product_name_short %} en el repositorio, ejecuta: + ```shell + $ git lfs uninstall + ``` + Para las versiones {% data variables.large_files.product_name_short %} más bajas que 1.1.0, ejecuta: + ```shell + $ git lfs uninit + ``` + +### objetos {% data variables.large_files.product_name_short %} en tu repositorio + +Después de eliminar los archivos de {% data variables.large_files.product_name_short %}, los objetos de {% data variables.large_files.product_name_short %} aún existirán en el almacenamiento remoto{% if currentVersion == "free-pro-team@latest" %} y seguirán contando en tu cuota de almacenamiento de {% data variables.large_files.product_name_short %}{% endif %}. + +Para eliminar los objetos de {% data variables.large_files.product_name_short %} de un repositorio, {% if currentVersion == "free-pro-team@latest" %}borra y vuelve a crear el repositorio. Cuando se borra un repositorio también se borra cualquier informe de problemas, estrellas y bifurcaciones asociados al mismo. Para obtener más información, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)".{% else %}contacta a tu administrador de {% data variables.product.prodname_enterprise %} para archivar los objetos. Los objetos archivados se purgan después de tres meses.{% endif %} + +{% note %} + +**Nota:** Si eliminaste un solo archivo y tienes otros objetos de {% data variables.large_files.product_name_short %} que quieres mantener en tu repositorio, después de borrar y volver a crear dicho repositorio, reconfigura tus archivos asociados de {% data variables.large_files.product_name_short %}. Para obtener más información, consulta la sección "[Eliminar un solo archivo](#removing-a-single-file)" y "[{% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". + +{% endnote %} + +### Further reading + +- "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" +- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" +- "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/resolving-git-large-file-storage-upload-failures.md b/translations/es-ES/content/github/managing-large-files/resolving-git-large-file-storage-upload-failures.md new file mode 100644 index 0000000000000..c6b93a715fbc7 --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/resolving-git-large-file-storage-upload-failures.md @@ -0,0 +1,24 @@ +--- +title: Resolver fallas de carga de Git Large File Storage +intro: 'Si tus archivos {% data variables.large_files.product_name_short %} no se cargaron bien, puedes tomar varias medidas para solucionar los problemas de error de carga.' +redirect_from: + - /articles/resolving-git-large-file-storage-upload-failures +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La {% data variables.large_files.product_name_short %} comprobación de integridad asegura que todos los archivos {% data variables.large_files.product_name_short %} referenciados en una subida se hayan cargado bien. Si la comprobación detecta archivos referenciados que no se cargaron, recibirás un mensaje de error y se bloqueará la subida. + +Para resolver el mensaje de error, debes reinstalar tu cliente local de {% data variables.large_files.product_name_short %} para garantizar que los archivos referenciados de {% data variables.large_files.product_name_short %} pueden subirse adecuadamente en ocasiones posteriores. + +1. Abre Terminal. +2. Reinstala {% data variables.large_files.product_name_short %}. + ```shell + $ git lfs install + ``` +3. Sube todos los archivos referenciados {% data variables.large_files.product_name_short %}. + ```shell + $ git lfs push --all origin + ``` diff --git a/translations/es-ES/content/github/managing-large-files/versioning-large-files.md b/translations/es-ES/content/github/managing-large-files/versioning-large-files.md new file mode 100644 index 0000000000000..0fb017ea4116d --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/versioning-large-files.md @@ -0,0 +1,12 @@ +--- +title: Control de versiones de archivos grandes +intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' +mapTopic: verdadero +redirect_from: + - /articles/versioning-large-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-large-files/what-is-my-disk-quota.md b/translations/es-ES/content/github/managing-large-files/what-is-my-disk-quota.md new file mode 100644 index 0000000000000..560248d4cfd2b --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/what-is-my-disk-quota.md @@ -0,0 +1,47 @@ +--- +title: '¿Cuál es mi cuota de disco?' +redirect_from: + - /articles/what-is-the-size-limit-for-a-repository/ + - /articles/what-is-my-disk-quota +intro: '{% data variables.product.product_name %} intenta proporcionar almacenamiento abundante para todos los repositorios de Git, aunque existen límites físicos para los tamaños de los archivos y repositorios.' +versions: + free-pro-team: '*' +--- + +{% data reusables.large_files.use_lfs_tip %} + +### Límites de tamaños para archivos y repositorios + +Para garantizar el rendimiento y la legibilidad para nuestros usuarios, monitoreamos activamente las señales de la salud general de los repositorios. La salud de los repositorios es una función de varios factores de interacción, incluyendo el tamaño, frecuencia de confirmaciones y estructura. + +Te recomendamos que los repositorios sean siempre pequeños, idealmente, de menos de 1 GB, y se recomienda ampliamente que sean de menos de 5GB. Los repositorios más pequeños se clonan más rápido y se puede mantenerlos mejor y trabajar en ellos más fácilmente. Los archivos individuales en un repositorio se limitan estrictamente a un límite de tamaño máximo de {% data variables.large_files.max_github_size %}. Para obtener más información, consulta "[Trabajar con archivos grandes](/github/managing-large-files/working-with-large-files)." + +Si tu repositorio impacta excesivamente nuestra infraestructura, puede que recibas un mensaje de correo electrónico de {% data variables.contact.github_support %}, el cual te solicitará que tomes acciones correctivas. Intentamos ser flexibles, especialmente con proyectos grandes que tienen muchos colaboradores, y trabajaremos junto contigo para encontrar una resolución cada que sea posible. Puedes prevenir que tu repositorio impacte nuestra infraestructura si administras el tamaño de tu repositorio y su salud general con eficacia. Puedes encontrar consejos y una herramienta para análisis de repositorios en el repositorio [`github/git-sizer`](https://github.com/github/git-sizer). + +{% note %} + +**Nota:** si agregas un archivo a un repositorio por medio de un navegador, el archivo no puede ser mayor de {% data variables.large_files.max_github_browser_size %}. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/github/managing-files-in-a-repository/adding-a-file-to-a-repository)." + +{% endnote %} + +### Copias de seguridad + +Git no está diseñado para fungir como una herramienta de respaldo. Sin embargo, existen muchas soluciones diseñadas específicamente para realizar respaldos, tales como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), y [CrashPlan](https://www.crashplan.com/en-us/). + +### Vertederos de base de datos + +Los sistemas de control de versiones, tales como Git, no se diseñan para manejar archivos grandes de SQL. Para compartir bases de datos grandes con otros desarrolladores, te recomendamos utilizar [Dropbox](https://www.dropbox.com/). + +Git no debe utilizarse como respaldo para tus servidores productivos. Para obtener más información, consulta la sección "Respaldos". + +### Dependencias externas + +Las dependencias externas pueden causar que los repositorios de Git se hagan muy grandes. Para evitar llenar un repositorio con dependencias externas, te recomendamos utilizar un administrador de paquetes. Los administradores de paquetes populares para lenguajes (de programación) comunes incluyen a [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), y [Maven](http://maven.apache.org/). Estos administradores de paquetes soportan la utilización directa de repositorios de Git para que no dependas de fuentes pre-empacadas. + +### Versiones de lanzamiento empaquetado + +No recomendamos distribuir código compilado y lanzamientos empaquetados previamente dentro de tu repositorio. Para obtener más información, consulta la sección "[Distribuir archivos binarios grandes](/github/managing-large-files/distributing-large-binaries)". + +### Cambiar el historial de un repositorio existente + +Si ya tienes un repositorio considerablemente grande, puedes reducir su tamaño si eliminas archivos grandes de su historial. Para obtener más información, consulta la sección "[Eliminar archivos del historial de un repositorio](/github/managing-large-files/removing-files-from-a-repositorys-history)". diff --git a/translations/es-ES/content/github/managing-large-files/working-with-large-files.md b/translations/es-ES/content/github/managing-large-files/working-with-large-files.md new file mode 100644 index 0000000000000..afe4bf5a8542a --- /dev/null +++ b/translations/es-ES/content/github/managing-large-files/working-with-large-files.md @@ -0,0 +1,12 @@ +--- +title: Trabajar con archivos de gran tamaño +intro: 'Un repositorio Git contiene cada versión de cada archivo. Pero para algunos tipos de archivos, esto no es práctico. Las revisiones múltiples de archivos de gran tamaño incrementan los tiempos de clonación y extracción para otros usuarios de un repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/working-with-large-files +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md new file mode 100644 index 0000000000000..86d5eaaf8c0de --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -0,0 +1,95 @@ +--- +title: Acerca de las alertas para las dependencias vulnerables +intro: '{% data variables.product.product_name %} envía {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} cuando detectamos vulnerabilidades que afectan tu repositorio.' +redirect_from: + - /articles/about-security-alerts-for-vulnerable-dependencies + - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de las dependencias vulnerables + +{% data reusables.repositories.a-vulnerability-is %} + +Cuando tu código depende de un paquete que tiene una vulnerabilidad de seguridad, esta dependencia puede causar una serie de problemas para tu proyecto o para las personas que lo utilizan. + +### Detección de dependencias vulnerables + + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}El {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detecta dependencias vulnerables y envía alertas de seguridad{% endif %} cuando: + +{% if currentVersion == "free-pro-team@latest" %} +- Se agrega una vulnerabilidad nueva a la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)". +- Se procesan los datos de las vulnerabilidades nuevas que se toman de [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database).{% else %} +- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.prodname_ghe_server %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información acerca de los datos de las asesorías, consulta la sección "Buscar vulnerabilidades de seguridad en el {% data variables.product.prodname_advisory_database %}".{% endif %} +- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de las cuales depende{% if currentVersion == "free-pro-team@latest" %}, o cuando el código de una de las dependencias cambia{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". + +{% data reusables.repositories.dependency-review %} + +Para encontrar una lista de ecosistemas para las cuales {% data variables.product.product_name %} puede detectar vulnerabilidades y dependencias, consulta la sección [ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". + +{% note %} + +**Nota:** Es importante mantener actualizados tu manifiesto y tus archivos bloqueados. Si la gráfica de dependencias no refleja con exactitud tus versiones y dependencias actuales, entonces podrías dejar pasar las alertas de las dependencias vulnerables que utilizas. También podrías obtener alertas de las dependencias que ya no utilizas. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} +### Alertas del {% data variables.product.prodname_dependabot %} para dependencias vulnerables +{% else %} +### Alertas de seguridad para las dependencias vulnerables +{% endif %} + +{% data reusables.repositories.enable-security-alerts %} + +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependencias vulnerables en repositorios _públicos_ y genera {% data variables.product.prodname_dependabot_alerts %} predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. + +También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". + +{% data variables.product.product_name %} comienza a generar la gráfica de dependencias inmediatamente y genera alertas de cualquier dependencia vulnerable tan pronto como las identifique. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio 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" %} +Cuando +{% data variables.product.product_name %} identifica una dependencia vulnerable, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad para el repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada. {% data variables.product.product_name %} también notifica a los mantenedores de los repositorios afectados sobre la nueva alerta de acuerdo con sus preferencias de notificaciones. Para obtener más información, consulta la sección "[Configurar notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Para los repositorios en donde +{% data variables.product.prodname_dependabot_security_updates %} se encuentra habilitado, la alerta también podría contener un enlace a una solicitud de cambios para actualizar el archivo de manifiesto o de bloqueo a la versión mínima que resuelva la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las {% 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" %} +Cuando +{% data variables.product.product_name %} identifica una dependencia vulnerable, enviamos una alerta de seguridad a los mantenedores de los repositorios afectados con detalles de la vulnerabilidad, un enlace al archivo afectado en el proyecto, e información acerca de una versión arreglada. +{% endif %} + +{% warning %} + +**Nota**: Las características de seguridad de {% data variables.product.product_name %} no aseguran que se detectarán todas las vulnerabilidades. Aunque siempre estamos tratando de actualizar nuestra base de datos de vulnerabilidades y de generar alertas con nuestra información más actualizada, no podremos atrapar todo o garantizar decirte acerca de las vulnerabilidades conocidas dentro de un periodo de tiempo determinado. Estas características no son sustitutos de la revisión humana de cada dependencia por posibles vulnerabilidades o cualquier otra cuestión. Te recomendamos consultar con un servicio de seguridad o realizar una revisión de vulnerabilidad exhaustiva cuando sea necesario. + +{% endwarning %} + +### Acceso a las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %} + +Puedes ver todas las alertas que afectaron un proyecto en particular{% if currentVersion == "free-pro-team@latest" %} en la pestaña de seguridad del repositorio o{% endif %} en la gráfica de dependencias del mismo.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +Predeterminadamente, notificamos a las personas con permisos adminsitrativos en los repositorios afectados sobre las +{% data variables.product.prodname_dependabot_alerts %} nuevas.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades que se identifican en los repositorios. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +Enviamos alertas de seguridad para las personas con permisos de administrador en los repositorios por defecto afectados. +{% data variables.product.product_name %} nunca disemina públicamente las vulnerabilidades identificadas de ningún repositorio. +{% endif %} + +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega para tus notificaciones](/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" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos"{% endif %}
diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md new file mode 100644 index 0000000000000..f192d428f8c86 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -0,0 +1,39 @@ +--- +title: About Dependabot security updates +intro: '{% data variables.product.prodname_dependabot %} puede arreglar tus dependencias vulnerables levantando solicitudes de extracción con actualizaciones de seguridad.' +shortTitle: About Dependabot security updates +redirect_from: + - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates +versions: + free-pro-team: '*' +--- + +### Acerca de las {% data variables.product.prodname_dependabot_security_updates %} + +Las {% data variables.product.prodname_dependabot_security_updates %} te facilitan el arreglar las dependencias vulnerables en tu repositorio. Si habilitas esta característica, cuando se levante una alerta del {% data variables.product.prodname_dependabot %} para una dependencia vulnerable en la gráfica de dependencias de tu repositorio, {% data variables.product.prodname_dependabot %} intentará arreglarla automáticamente. Para obtener más información, consulta las seccciones "[Acerca de las alertas para las depedencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". + +{% data variables.product.prodname_dependabot %} verifica si es posible actualizar la dependencia vulnerable a una versión arreglada sin irrumpir en la gráfica de dependencias para el repositorio. Posteriormente, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para actualizar la dependencia a la versión mínima que incluye el parche y los enlaces a la solicitud de cambios para la alerta del {% data variables.product.prodname_dependabot %}, o reporta un error en la alerta. Para obtener más información, consulta la sección "[Solucionar problemas para los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". + +{% note %} + +**Note** + +La característica de {% data variables.product.prodname_dependabot_security_updates %} se encuentra disponible para los repositorios en donde hayas habilitado la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %}. Verás una alerta del {% data variables.product.prodname_dependabot %} por cada dependencia vulnerable que se haya identificado en toda tu gráfica de dependencias. Sin embargo, las actualizaciones de seguridad se activan únicamente para las dependencias que se especifican en un archivo de manifiesto o de bloqueo. El {% data variables.product.prodname_dependabot %} no puede actualizar una dependencia indirecta o transitoria si no se define explícitamente. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)". + +{% endnote %} + +### Acerca de las solicitudes de cambios para las actualizaciones de seguridad + +Cada solicitud de cambios contiene todo lo que necesitas para revisar y fusionar de forma rápida y segura un arreglo propuesto en tu proyecto. Esto incluye la información acerca de la vulnerabilidad, como las notas de lanzamiento, las entradas de bitácora de cambios, y los detalles de confirmación. Los detalles de qué vulnerabilidad resuelve una solicitud de cambios se encuentran ocultos para cualquiera que no tenga acceso a las {% data variables.product.prodname_dependabot_alerts %} del repositorio en cuestión. + +Cuando fusionas una solicitud de cambios que contiene una actualización de seguridad, la alerta correspondiente del {% data variables.product.prodname_dependabot %} se marca como resuelta en el repositorio. Para obtener más información acerca de las solicitudes de cambios del {% data variables.product.prodname_dependabot %}, consulta la sección "[Administrar las solicitudes de cambios para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)". + +{% data reusables.dependabot.automated-tests-note %} + +### Acerca de las puntuaciones de compatibilidad + +Las {% data variables.product.prodname_dependabot_security_updates %} podrían incuir puntuaciones de compatibilidad para hacerte saber si el actualizar una vulnerabilidad podría causar cambios sustanciales en tu proyecto. Estos se calculan de las pruebas de IC en otros repositorios públicos en donde se ha generado la misma actualización de seguridad. La puntuación de compatibilidad de una actualización es el porcentaje de ejecuciones de IC que pasaron cuando se hicieron actualizaciones en versiones específicas de la dependencia. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". \ No newline at end of file diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-github-security-advisories.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-github-security-advisories.md new file mode 100644 index 0000000000000..01e3b37285fcd --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-github-security-advisories.md @@ -0,0 +1,51 @@ +--- +title: Acerca de GitHub Security Advisories +intro: 'Puedes usar {% data variables.product.prodname_security_advisories %} para discutir, corregir y publicar información sobre vulnerabilidades de seguridad en tu repositorio.' +redirect_from: + - /articles/about-maintainer-security-advisories + - /github/managing-security-vulnerabilities/about-maintainer-security-advisories +versions: + free-pro-team: '*' +--- + +{% data reusables.repositories.security-advisory-admin-permissions %} + +{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} + +### Acerca de {% data variables.product.prodname_security_advisories %} + +{% data variables.product.prodname_security_advisories %} permite a los mantenedores del repositorio discutir en privado y corregir una vulnerabilidad de seguridad en un proyecto. Después de colaborar en una corrección, los mantenedores del repositorio pueden publicar el aviso de seguridad para revelar públicamente la vulnerabilidad de seguridad a la comunidad del proyecto. Al publicar avisos de seguridad, los mantenedores de repositorios facilitan que su comunidad actualice las dependencias de los paquetes e investigue el impacto de las vulnerabilidades de seguridad. + +Con {% data variables.product.prodname_security_advisories %}, puedes: + +1. Crear un borrador de asesoría de seguridad y utilizarlo para debatir de manera privada sobre el impacto de la vulnerabilidad en tu proyecto. +2. Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. +3. Publicar la asesoría de seguridad para enviar una alerta sobre la vulnerabilidad a tu comunidad. + +{% data reusables.repositories.security-advisories-republishing %} + +Para empezar, ve "[Creando un aviso de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)." + +Puedes dar crédito a los individuos que contribuyeron con una asesoría de seguridad. Para obtener más información, consulta la sección " + +Editar una asesoría de seguridad".

+ +{% data reusables.repositories.security-guidelines %} + +{% data reusables.repositories.github-security-lab %} + + + +### Números de identificación CVE + +Las {% data variables.product.prodname_security_advisories %} se construyen sobre las bases de la lista de Vulnerabilidades y Exposiciones Comunes (CVE, por sus siglas en inglés). {% data variables.product.prodname_dotcom %} es una Autoridad de Numeración de CVE (CNA, por sus siglas en inglés) y está autorizado para asignar números de identificación de CVE. Para obtener más información, consulta las secciones "[Acerca de CVE](https://cve.mitre.org/about/index.html)" y "[Autoridades de Numeración de CVE](https://cve.mitre.org/cve/cna.html)" en el sitio de CVE. + +Cuando creas una asesoría de seguridad para un repositorio público en {% data variables.product.prodname_dotcom %}, tienes la opción de proporcionar un número de identificación de CVE para la vulnerabilidad de seguridad. {% data reusables.repositories.request-security-advisory-cve-id %} + +Una vez que hayas publicado la asesoría de seguridad y que {% data variables.product.prodname_dotcom %} haya asignado un número de identificación CVE a la vulnerabilidad, {% data variables.product.prodname_dotcom %} publicará el CVE a la base de datos de MITRE. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)". + + + +### {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas + +{% data reusables.repositories.github-reviews-security-advisories %} diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000000..0cf8c28e0f196 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: Acerca de la administración de dependencias vulnerables +intro: '{% data variables.product.prodname_dotcom %} te ayuda a evitar el utilizar software de terceros que contenga vulnerabilidades conocidas.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} te proporciona las siguientes herramientas para eliminar y evitar las dependencias vulnerables. + +#### Gráfica de dependencias +La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Te muestra los ecosistemas y paquetes de los cuales depende tu base de código (sus dependencias) y los repositorios y paquetes que dependen de tu proyecto (sus dependencias). Tanto la revisión de dependencias como el {% data variables.product.prodname_dependabot %} utilizan la información en la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". + +#### Revisión de dependencias +Si verificas las revisiones de dependencias en las solicitudes de cambios puedes evitar introducir las vulnerabilidades de las dependencias en tu base de código. Si las solicitudes de cambios agregan una dependencia vulnerable o cambian una dependencia a una versión vulnerable, esto se resaltará en la revisión de dependencias. Puedes cambiar la dependencia a una versión parchada antes de fusionar la solicitud de cambios. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} puede crear {% data variables.product.prodname_dependabot_alerts %} cuando detecta dependencias vulnerables en tu repositorio. La alerta se muestra en la pestaña de seguridad del repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada. {% data variables.product.prodname_dotcom %} también notifica a los mantenedores del repositorio, de acuerdo con sus preferencias de notificación. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +#### {% data variables.product.prodname_dependabot_security_updates %} +Cuando {% data variables.product.prodname_dotcom %} genera una alerta del {% data variables.product.prodname_dependabot %} para una dependencia vulnerable en tu repositorio, el {% data variables.product.prodname_dependabot %} puede intentar arreglarla automáticamente. las {% data variables.product.prodname_dependabot_security_updates %} son solicitudes de cambios que se generan automáticamente y que actualizan una dependencia vulnerable a una versión arreglada. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + + +#### {% data variables.product.prodname_dependabot_version_updates %} +El habilitar las {% data variables.product.prodname_dependabot_version_updates %} hace que el mantener tus dependencias tome menos esfuerzo. Con las {% data variables.product.prodname_dependabot_version_updates %}, cada que {% data variables.product.prodname_dotcom %} identifique una dependencia desactualizada, levantará una solicitud de cambios para actualizar el manifiesto a la versión más reciente de la dependencia. Como contraste, las {% data variables.product.prodname_dependabot_security_updates %} solo levantan solicitudes de cambios para arreglar dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md new file mode 100644 index 0000000000000..9b8bc0a5a3042 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md @@ -0,0 +1,34 @@ +--- +title: Añadir un colaborador a una asesoría de seguridad +intro: Puedes agregar otros usuarios o equipos para que colaboren contigo en un aviso de seguridad. +redirect_from: + - /articles/adding-a-collaborator-to-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory +versions: + free-pro-team: '*' +--- + +Las personas con permisos de administrador en una asesoría de seguridad pueden añadir colaboradores a la misma. + +### Añadir un colaborador a una asesoría de seguridad + +Los colaboradores tienen permisos de escritura para el aviso de seguridad. Para obtener más información, consulte la sección "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)". + +{% note %} + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %}Para encontrar más información acerca de eliminar a un colaborador de una asesoría de seguridad, consulta la sección "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)". + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En la lista de "Asesorías de Seguridad", da clic en la asesoría a la cual quieras añadir un colaborador. +5. En la parte derecha de la página, debajo de "Colaboradores", teclea el nombre de usuario o equipo que quieras añadir a la asesoría de seguridad.![Campo para escribir el nombre del equipo o el usuario](/assets/images/help/security/add-collaborator-field.png) +6. Da clic en **Agregar**. ![Botón Add (Agregar)](/assets/images/help/security/security-advisory-add-collaborator-button.png) + +### Further reading + +- "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" +- "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" +- "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md new file mode 100644 index 0000000000000..cf3b2f798570c --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md @@ -0,0 +1,42 @@ +--- +title: Agregar una política de seguridad a tu repositorio +intro: Puedes brindar instrucciones sobre cómo informar responsablemente una vulnerabilidad de seguridad en tu proyecto al agregar una política de seguridad a tu repositorio. +redirect_from: + - /articles/adding-a-security-policy-to-your-repository +versions: + free-pro-team: '*' +--- + +### Acerca de las políticas de seguridad + +Para brindar instrucciones sobre cómo informar responsablemente las vulnerabilidades de seguridad en tu proyecto, puedes agregar un archivo _SECURITY.md_ a la raíz de tu repositorio, `docs`, o carpeta `.github`. Cuando alguien crea una propuesta en tu repositorio, verán un enlace en la política de seguridad de tu proyecto. + +Puedes crear una política de seguridad predeterminada para tu cuenta de usuario o de organización. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + +{% tip %} + +**Sugerencia:** Para que las demás personas puedan encontrar tu política de seguridad, puedes vincular tu archivo _SECURITY.md_ desde otros lugares en tu repositorio, como un archivo README. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". + +{% endtip %} + +Después de que alguien reporte una vulnerabilidad de seguridad en tu proyecto, puedes utilizar {% data variables.product.prodname_security_advisories %} para divulgar, arreglar y publicar información acerca de la misma. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". + +{% data reusables.repositories.github-security-lab %} + +### Agregar una política de seguridad a tu repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +3. En la barra lateral izquierda, haz clic en **Policy** (Política). ![Pestaña Policy (Política)](/assets/images/help/security/policy-tab.png) +4. Haz clic en **Start setup** (Iniciar configuración). ![Botón Start setup (Iniciar configuración)](/assets/images/help/security/start-setup-policy-button.png) +5. En el archivo _SECURITY.md_ nuevo, agrega información sobre las versiones compatibles de tu proyecto y cómo informar una vulnerabilidad. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Further reading + +- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" +- "[Configurar tu proyecto para contribuciones positivas](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)" +- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md new file mode 100644 index 0000000000000..e5705ebe346df --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -0,0 +1,65 @@ +--- +title: Buscar vulnerabilidades de seguridad en la Base de Datos de Asesorías de GitHub +intro: 'La {% data variables.product.prodname_advisory_database %} te permite buscar vulnerabilidades que afecten proyectos de código abierto, ya sea manualmente o por coincidencia exacta, en {% data variables.product.company_short %}.' +shortTitle: Buscar en la Base de Datos de Asesorias +versions: + free-pro-team: '*' +--- + +### Acerca de las vulnerabilidades de seguridad + +{% data reusables.repositories.a-vulnerability-is %} + +{% data variables.product.product_name %} te enviará {% data variables.product.prodname_dependabot_alerts %} si detectamos que cualquiera de las vulnerabilidades de la {% data variables.product.prodname_advisory_database %} afecta los paquetes de los que depende tu repositorio. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +### Acerca de {% data variables.product.prodname_advisory_database %} + +La {% data variables.product.prodname_advisory_database %} contiene una lista selecta de vulnerabilidades de seguridad que se han mapeado para los paquetes que rastrea la gráfica de dependencias de {% data variables.product.company_short %}. {% data reusables.repositories.tracks-vulnerabilities %} + +Cada asesoría de seguridad contiene información acerca de la vulnerabilidad, incluyendo la descripción, severidad, paquete afectado, paquete de ecosistema, versiones afectadas y versiones parchadas, impacto, e información opcional tal como referencias, soluciones alternas, y créditos. Adicionalmente, las asesorías de la National Vulnerability Database contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología. + +El nivel de gravedad es uno de cuatro niveles posibles definidos en el [Sistema de clasificación de vulnerabilidades comunes (CVSS), Sección 2.12](https://www.first.org/cvss/specification-document): +- Low +- Moderate +- High +- Crítico + +La {% data variables.product.prodname_advisory_database %} utiliza estándares de CVSS versión 3.0 y los niveles de CVSS descritos anteriormente. {% data variables.product.product_name %} no publica los puntajes de CVSS. + +{% data reusables.repositories.github-security-lab %} + +### Acceder a una asesoría en la {% data variables.product.prodname_advisory_database %} + +1. Navega hasta https://github.com/advisories. +2. Opcionalmente, para filtrar la lista, utiliza cualquiera de los menúes desplegables. ![Filtros desplegables](/assets/images/help/security/advisory-database-dropdown-filters.png) +3. Da clic en cualquier asesoría para ver los detalles. + +{% note %} + +También se puede acceder a la base de datos utilizando la API de GraphQL. Para obtener más información, consulta la sección "[evento de webhook de `security_advisory`](/webhooks/event-payloads/#security_advisory)". + +{% endnote %} + +### Buscar en la {% data variables.product.prodname_advisory_database %} por coincidencia exacta +Puedes buscar coincidencias exactas en la base de datos y utilizar calificadores para reducir tu búsqueda y encontrar asesorías que se crearon en cierta fecha, en un ecosistema específico o en una biblioteca en particular. + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará únicamente asesorías que afecten paquetes NPM. | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará únicamente asesorías con nivel de gravedad alto. | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará únicamente asesorías que afecten la biblioteca lodash. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) organizará los resultados para mostrar las asesorías más viejas primero. | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) organizará los resultados para mostrar las asesorías más nuevas primero. | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) organizará los resultados para mostrar aquellos actualizados menos recientemente. | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) organizará los resultados para mostrar los aquellos actualizados más recientemente. | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará únicamente las asesorías que se han retirado. | +| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) mostrará únicamente las asesorías creadas en esta fecha. | +| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) mostrará únicamente asesorías actualizadas en esta fecha. | + +### Further reading + +- [Definición de MITRE de "vulnerabilidad"](https://cve.mitre.org/about/terminology.html#vulnerability) diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md new file mode 100644 index 0000000000000..3f11765c5e8cf --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md @@ -0,0 +1,75 @@ +--- +title: Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad +intro: Puedes crear una bifurcación privada temporal para colaborar de manera privada en la resolución de una vulnerabilidad de seguridad en tu repositorio. +redirect_from: + - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability +versions: + free-pro-team: '*' +--- + +### Prerrequisitos + +Antes de que puedas colaborar en una bifurcación privada temporal, debes crear un borrador de asesoría de seguridad. Para obtener más información, consulta la sección "[Crear una asesoría de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)". + +### Crear una bifurcación privada temporal + +Cualquier persona con permisos de administración para un aviso de seguridad puede crear una bifurcación privada temporal. + +Para garantizar la seguridad de la información sobre vulnerabilidades, las integraciones, entre las que se incluye CI, no pueden acceder a las bifurcaciones privadas temporales. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En la lista de "Asesorías de Seguridad", da clic en aquella en la cual desees crear una bifurcación privada temporal. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. Haz clic en **New temporary private fork** (Nueva bifurcación privada temporal). ![Nuevo botón de bifurcación privada temporal](/assets/images/help/security/new-temporary-private-fork-button.png) + +### Añadir colaboradores a una bifurcación privada temporal + +Cualquiera con permisos de administrador en una asesoría de seguridad puede añadir colaboradores adicionales a la misma, y estos pueden acceder a la bifurcación privada temporal. Para obtener más información, consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)". + +### Agregar cambios a una bifurcación privada temporal + +Cualquier persona con permisos de escritura para un aviso de seguridad puede agregar cambios a una bifurcación privada temporal. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que quieras añadir cambios. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. Agrega tus cambios en {% data variables.product.product_name %} o localmente: + - Para añadir cambios en {% data variables.product.product_name %}, debajo de "Añadir cambios a esta asesoría", da clic en **la bifurcación privada temporal**. Luego, crea una nueva rama y edita los archivos. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository)" y "[Editar archivos en tu repositorio](/articles/editing-files-in-your-repository)". + - Para añadir cambios localmente, sigue las instrucciones descritas en "Clonar y crear una nueva rama" y "Haz tus cambios, posteriormente, súbelos". ![Agregar cambios en este cuadro de aviso](/assets/images/help/security/add-changes-to-this-advisory-box.png) + +### Crear una solicitud de extracción desde una bifurcación privada temporal + +Cualquier persona con permisos de escritura para un aviso de seguridad puede crear una solicitud de extracción desde una bifurcación privada temporal. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que desees crear una solicitud de extracción. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. A la derecha del nombre de tu rama, haz clic en **Compare & pull request** (Comparar solicitudes de extracción). ![Botón Compare & pull request (Comparar y solicitud de extracción)](/assets/images/help/security/security-advisory-compare-and-pr.png) +{% data reusables.repositories.pr-title-description %} +{% data reusables.repositories.create-pull-request %} + +{% data reusables.repositories.merge-all-pulls-together %}Para obtener más información, consulta la sección [Fusionar cambios en una asesoría de seguridad](#merging-changes-in-a-security-advisory)". + +### Fusionar cambios en una asesoría de seguridad + +Cualquiera con permisos de administrador en una asesoría de seguridad puede fusionar los cambios en la misma. + +{% data reusables.repositories.merge-all-pulls-together %} + +Antes de que puedas fusionar cambios en una asesoría de seguridad, cada solicitud de extracción abierta en la bifurcación privada temporal debe ser fusionable. No puede haber conflictos de fusión, y se deben cumplir los requisitos de protección de la rama. Para garantizar la seguridad de la información sobre las vulnerabilidades, las verificaciones de estado no ejecutan solicitudes de extracción en bifurcaciones privadas temporales. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic sobre aquella que tiene los cambios que quieras fusionar. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. Para fusionar todas las solicitudes de extracción abiertas en la bifurcación privada temporal, haz clic en **Merge pull requests** (Fusionar solicitudes de extracción). ![Botón para fusionar solicitud de extracción](/assets/images/help/security/merge-pull-requests-button.png) + +Después de que fusiones cambios en una asesoría de seguridad, puedes publicarla para alertar a tu comunidad sobre las vulnerabilidades de seguridad en versiones previas de tu proyecto. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". + +### Further reading + +- "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" +- "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md new file mode 100644 index 0000000000000..5cd5d1734e1b6 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -0,0 +1,62 @@ +--- +title: Configuring Dependabot security updates +intro: 'Puedes utilizar las {% data variables.product.prodname_dependabot_security_updates %} o las solicitudes de extracción manuales para actualizar fácilmente las dependencias vulnerables.' +shortTitle: Configuring Dependabot security updates +redirect_from: + - /articles/configuring-automated-security-fixes + - /github/managing-security-vulnerabilities/configuring-automated-security-fixes + - /github/managing-security-vulnerabilities/configuring-automated-security-updates + - /github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates +versions: + free-pro-team: '*' +--- + +### Acerca de la configuración de las {% data variables.product.prodname_dependabot_security_updates %} + +Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + +Puedes inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual o para todos los repositorios que pertenezcan a tu organización o cuenta de usuario. Para obtener más información, consulta la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)" acontinuación. + +{% data reusables.dependabot.dependabot-tos %} + +### Repositorios compatibles + +{% data variables.product.prodname_dotcom %} habilita las {% data variables.product.prodname_dependabot_security_updates %} automáticamente para cada repositorio que cumpla con estos pre-requisitos. + +{% note %} + +**Nota**: Puedes habilitar manualmente las {% data variables.product.prodname_dependabot_security_updates %}, aún si el repositorio no cumple con alguno de los siguientes prerrequisitos. Por ejemplo, puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} en una bifurcación, o para un administrador de paquetes que no sea directamente compatible si sigues las instrucciones en la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)". + +{% endnote %} + +| Pre-requisito de habilitación automática | Más información | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Que el repositorio no sea una bifrucación | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Que el repositorio no esté archivado | "[Archivar repositorios](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" | +| Que el repositorio sea público, o que sea privado y hayas habilitado un análisis de solo lectura por {% data variables.product.prodname_dotcom %}, gráfica de dependencias y alertas de vulnerabilidades en la configuración del mismo | "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". | +| Que el repositorio contenga un archivo de manifiesto de dependencias de un ecosistema de paquete que sea compatible con {% data variables.product.prodname_dotcom %} | "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" | +| Las {% data variables.product.prodname_dependabot_security_updates %} no se han inhabilitado para el repositorio | "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tu repositorio](#managing-dependabot-security-updates-for-your-repositories)" | +| Que el repositorio no esté utilizando ya una integración para administración de dependencias | "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)" | + +Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sabes por qué, intenta primero habilitarles de acuerdo con las instrucciones que se encuentran en los procedimientos siguientes. Si las actualizaciones aún no funcionan, puedes [contactar a soporte](https://support.github.com/contact). + +### Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios + +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). + +También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". + +Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta "[Repositorios soportados](#supported-repositories)". + +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) + +### Further reading + +- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +- "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". +- "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md new file mode 100644 index 0000000000000..7f46458ff3f79 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -0,0 +1,58 @@ +--- +title: Configurar las notificaciones para las dependencias vulnerables +shortTitle: Configurar notificaciones +intro: 'Optimiza la forma en la que recibes las notificaciones sobre las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' +--- + +### Acerca de las notificaciones para las dependencias vulnerables + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}Cuando el {% data variables.product.prodname_dependabot %} detecta dependencias vulnerables en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificación.{% else %}Cuando{% data variables.product.product_name %} detecta dependencias vulnerables en tus repositorios, manda alertas de seguridad.{% endif %}{% if currentVersion == "free-pro-team@latest" %} El {% data variables.product.prodname_dependabot %} se habilita predeterminadamente en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. También puedes configurar si se habilitará o inhabilitará la detección de dependencias vulnerables para los repositorios recién creados. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} +Tu administrador de sitio necesita habilitar las alertas de seguridad para las dependencias vulnerables de +{% data variables.product.product_location %} antes de que puedas utilizar la característica. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %} +Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para notificaciones en tu empresa, recibirás +{% if currentVersion ver_gt "enterprise-server@2.21" %}Alertas de {% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} por correo electrónico.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.21" %}Los administradores de sitio también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} + +{% if currentVersion ver_lt "enterprise-server@2.22" %}Los administradores de sitio también pueden habilitar las alertas de seguridad sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las alertas de seguridad para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} + +### Configurar notificaciones para las {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} + +Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". + +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} +{% data reusables.notifications.vulnerable-dependency-notification-options %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png) +{% else %} + ![Opciones de alertas de seguridad](/assets/images/help/notifications-v2/security-alerts-options.png) +{% endif %} + +{% note %} + +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} Para obtener más información, consulta la sección"[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}".{% endif %} + +### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables + +Si te preocupa recibir demasiadas notificaciones para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las {% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que decidas ingresar en el resúmen semanal por correo electrónico, o apagar las notificaciones mientras aún tienes {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} las {% else %}alertas de seguridad{% endif %} de las {% data variables.product.prodname_dependabot_alerts %} habilitadas. Aún puedes navegar para ver tus {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} en la pestaña de seguridad de tu repositorio.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %} + +### Further reading + +- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" +- "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md new file mode 100644 index 0000000000000..190b4fb79e5c3 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/creating-a-security-advisory.md @@ -0,0 +1,34 @@ +--- +title: Crear una asesoría de seguridad +intro: Puedes crear un borrador de asesoría de seguridad para debatir en privado y arreglar una vulnerabilidad de seguridad en tu proyecto de código abierto. +redirect_from: + - /articles/creating-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory +versions: + free-pro-team: '*' +--- + +Cualquier usuario con permisos de administrador puede crear un aviso de seguridad. + +{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} + +### Crear una asesoría de seguridad + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. Da clic en **Nuevo borrador de asesoría de seguridad**. ![Botón Abrir aviso en borrador](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png) +5. Escribe un título para tu aviso de seguridad. ![Campo de título](/assets/images/help/security/security-advisory-title.png) +{% data reusables.repositories.security-advisory-edit-details %} +{% data reusables.repositories.security-advisory-edit-description %} +8. Da clic en **Crear asesoría de seguridad**". ![Botón para crear asesoría de seguridad](/assets/images/help/security/security-advisory-create-security-advisory-button.png) + +### Pasos siguientes + +- Comentar en el borrador de asesoría de seguridad para debatir sobre la vulnerabilidad con tu equipo. +- Añadir colaboradores a la asesoría de seguridad. Para obtener más información, consulta la sección "[Añadir un colaborador a la asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory)". +- Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. Para obtener más información, consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". +- Agregar individuos que deberían recibir crédito por contribuir con la asesoría de seguridad. Para obtener más información, consulta la sección " +Editar una asesoría de seguridad". + + - Publicar la asesoría de seguridad para notificar a tu comunidad sobre la vulnerabilidad de seguridad en cuestión. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md new file mode 100644 index 0000000000000..aa5db66eee9fd --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md @@ -0,0 +1,33 @@ +--- +title: Editar una asesoría de seguridad +intro: Puedes editar los metadatos y la descripción de una asesoría de seguridad si necesitas actualizar los detalles o corregir los errores en la misma. +versions: + free-pro-team: '*' +--- + +Las personas con permisos de administrador en una asesoría de seguridad pueden editarla. + +### Acerca de los créditos para las asesorías de seguridad + +Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arreglar una vulnerabilidad de seguridad. Si le das crédito a alguien, ellos pueden elegir aceptarlo o declinarlo. + +Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en la sección "Créditos" de la asesoría de seguridad. Cualquiera con acceso de lectura al repositorio puede ver la asesoría y las personas que aceptaron el crédito por ella. + +### Editar una asesoría de seguridad + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic en aquella que quieras editar. +5. En la esquina superior derecha de los detalles para la asesoría de seguridad, da clic en +{% octicon "pencil" aria-label="The edit icon" %}. + ![Botón de editar para una asesoría de seguridad](/assets/images/help/security/security-advisory-edit-button.png) +{% data reusables.repositories.security-advisory-edit-details %} +{% data reusables.repositories.security-advisory-edit-description %} +8. Opcionalmente, puedes editar los "Créditos" para la asesoría de seguridad. ![Créditos para una asesoría de seguridad](/assets/images/help/security/security-advisory-credits.png) +9. Da clic en **Actualizar asesoría de seguridad**". ![Botón Add (Agregar)](/assets/images/help/security/update-advisory-button.png) +10. Las personas listadas en la sección de "Créditos" recibirán una notificación web o por correo electrónico que los invita a aceptar el crédito. Si la persona acepta, su nombre de usuario estará visible al público una vez que la asesoría de seguridad se publique. + +### Further reading + +- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/index.md b/translations/es-ES/content/github/managing-security-vulnerabilities/index.md new file mode 100644 index 0000000000000..bc255a5a76478 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/index.md @@ -0,0 +1,32 @@ +--- +title: Administrar vulnerabilidades de seguridad +redirect_from: + - /categories/managing-security-vulnerabilities +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + + +### Índice +{% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} + {% link_in_list /adding-a-security-policy-to-your-repository %} + {% link_in_list /about-github-security-advisories %} + {% link_in_list /permission-levels-for-security-advisories %} + {% link_in_list /creating-a-security-advisory %} + {% link_in_list /adding-a-collaborator-to-a-security-advisory %} + {% link_in_list /removing-a-collaborator-from-a-security-advisory %} + {% link_in_list /collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability %} + {% link_in_list /publishing-a-security-advisory %} + {% link_in_list /editing-a-security-advisory %} + {% link_in_list /withdrawing-a-security-advisory %} +{% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} + {% link_in_list /about-managing-vulnerable-dependencies %} + {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} + {% link_in_list /about-alerts-for-vulnerable-dependencies %} + {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} + {% link_in_list /about-dependabot-security-updates %} + {% link_in_list /configuring-dependabot-security-updates %} + {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} + {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} + {% link_in_list /troubleshooting-dependabot-errors %} diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md new file mode 100644 index 0000000000000..18adffef97311 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md @@ -0,0 +1,10 @@ +--- +title: Administrar las vulnerabilidades de seguridad en tu proyecto +intro: 'Puedes descubrir, discutir, reparar y divulgar vulnerabilidades de seguridad en tus repositorios.' +mapTopic: verdadero +redirect_from: + - /articles/managing-security-vulnerabilities-in-your-project +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md new file mode 100644 index 0000000000000..5247a91ffae58 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md @@ -0,0 +1,14 @@ +--- +title: Administrar vulnerabilidades en las dependencias de tus proyectos +intro: 'Puedes rastrear las dependencias de tu repositorio y recibir{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% endif %}cuando {% data variables.product.product_name %} detecta dependencias vulnerables.' +mapTopic: verdadero +redirect_from: + - /articles/updating-your-project-s-dependencies/ + - /articles/updating-your-projects-dependencies/ + - /articles/managing-security-vulnerabilities-in-your-projects-dependencies/ + - /articles/managing-vulnerabilities-in-your-projects-dependencies +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md b/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md new file mode 100644 index 0000000000000..dda4d6350d11a --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md @@ -0,0 +1,34 @@ +--- +title: Niveles de permiso para las asesorías de seguridad +intro: Las acciones que puedes tomar en una asesoría de seguridad dependen de si tienes permisos de administrador o de escritura en la misma. +redirect_from: + - /articles/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories +versions: + free-pro-team: '*' +--- + +### Resumen de permisos + +{% data reusables.repositories.security-advisory-admin-permissions %} Para obtener más información sobre cómo añadir un colaborador a una asesoría de seguridad, consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)". + +| Acción | Permisos de escritura | Permisos de administrador | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ------------------------- | +| Ver un borrador de asesoría de seguridad | X | X | +| Añadir colaboradores a la asesoría de seguridad (consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)") | | X | +| Editar y borrar cualquier comentario en la asesoría de seguridad | X | X | +| Crear una bifurcación privada temporal en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)) | | X | +| Añadir cambios a una bifurcación privada temporal en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | X | X | +| Crear solicitudes de extracción en una bifurcación privada temporaria (consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | X | X | +| Fusionar cambios en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | | X | +| Añadir y editar los metadatos de la asesoría de seguridad (consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)") | X | X | +| Agrega y elimina los créditos para una asesoría de seguridad (consulta "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)") | X | X | +| Cerrar el borrador de la asesoría de seguridad | | X | +| Publicar la asesoría de seguridad (consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)") | | X | + +### Further reading + +- "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" +- "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" +- "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" +- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md new file mode 100644 index 0000000000000..185394feb7b06 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -0,0 +1,71 @@ +--- +title: Publicar una asesoría de seguridad +intro: Puedes publicar una asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad de seguridad en tu proyecto. +redirect_from: + - /articles/publishing-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory +versions: + free-pro-team: '*' +--- + +Cualquiera con permisos de administrador en una asesoría de seguridad puede publicarla. + +### Prerrequisitos + +Antes de que puedas publicar una asesoría de seguridad o solicitar un número de identificación de CVE, debes crear un borrador de asesoría de seguridad y proporcionar información acerca de las versiones de tu proyecto que se vieron afectadas por la vulnerabilidad de seguridad. Para obtener más información, consulta la sección "[Crear una asesoría de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)". + +Si creaste una asesoría de seguridad pero no has proporcionado detalles sobre las versiones de tu proyecto que afectó la vulnerabilidad, puedes editarla. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". + +### Acerca de publicar una asesoría de seguridad + +Cuando publicas una asesoría de seguridad, notificas a tu comunidad acerca de la vulnerabilidad de seguridad que se dirige en dicha asesoría. El publicar una asesoría de seguridad facilita a tu comunidad el actualizar las dependencias de los paquetes y el investigar el impacto de la vulnerabilidad de seguridad. + +{% data reusables.repositories.security-advisories-republishing %} + +Antes de que publiques una asesoría de seguridad, puedes hacer una colaboración privada para arreglar la vulnerabilidad en una bifurcación privada. Para obtener más información, consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". + +Cuando publicas un borrador de asesoría desde un repositorio público, todos pueden ver: + +- La versión actual de los datos de la asesoría. +- Cualquier asesoría atribuye que los usuarios acreditados han aceptado. + +{% note %} + +**Nota**: El público en general jamás tendrá acceso al historial de ediciones de la asesoría y solo verá la versión publicada. + +{% endnote %} + +Después de que publicas una asesoría de seguridad, la URL de la misa permanecerá tal como antes de publicarla. Cualquiera con acceso de lectura al repositorio puede verla. Los colaboradores de la asesoría de seguridad pueden seguir viendo las conversaciones pasadas, incluyendo el flujo completo de comentarios, en la asesoría de seguridad a menos de que alguien con permisos administrativos elimine al colaborador de la asesoría de seguridad. + +Si necesitas actualizar o corregir información en una asesoría de seguridad que hayas publicado, puedes editarla. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". + +### Pedir el número de identificación de CVE + +Cualquiera con permisos de administrador en una asesoría de seguridad puede solicitar un número de identificación de CVE para la asesoría de seguridad. + +{% data reusables.repositories.request-security-advisory-cve-id %} Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic en aquella para la cual quieras solicitar un número de identificación de CVE. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. Utiliza el menú desplegable de **Publicar asesoría** y da clic en **Solicitar CVE**. ![Solicitar un CVE en el menú desplegable](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Da clic en **Solicitar CVE**. ![Botón "Solicitar CVE"](/assets/images/help/security/security-advisory-request-cve-button.png) + +### Publicar una asesoría de seguridad + +El publicar una asesoría de seguridad borra la bifurcación temporal privada para la misma. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic sobre la que quieras publicar. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. En la parte inferior de la página, da clic sobre **Publicar asesoría**. ![Botón para publicar aviso](/assets/images/help/security/publish-advisory-button.png) + +### {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas + +{% data reusables.repositories.github-reviews-security-advisories %} + +### Further reading + +- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md new file mode 100644 index 0000000000000..ad5638a9da611 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md @@ -0,0 +1,24 @@ +--- +title: Eliminar a un colaborador de una asesoría de seguridad +intro: 'Cuando eliminas a un colaborador de una asesoría de seguridad, este pierde el acceso de lectura y escritura en el debate y metadatos de la misma.' +versions: + free-pro-team: '*' +--- + +Las personas con permisos administrativos en una asesoría de seguridad pueden eliminar a los colaboradores de la misma. + +### Eliminar a un colaborador de una asesoría de seguridad + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic sobre aquella en la que quieras eliminar a algún colaborador. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. En el lado derecho de la página, debajo de "Colaboradores", encuentra el nombre del usuario o equipo al que quieres eliminar de la asesoría de seguridad. ![Colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-collaborator.png) +6. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Icono X para eliminar al colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-remove-collaborator-x.png) + +### Further reading + +- "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" +- "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md new file mode 100644 index 0000000000000..c8c86912cfdbc --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -0,0 +1,92 @@ +--- +title: Solucionar problemas de los errores del Dependabot +intro: 'Algunas veces, el {% data variables.product.prodname_dependabot %} no puede levantar solicitudes de cambios para actualizar tus dependencias. Puedes revisar el error y desbloquear al {% data variables.product.prodname_dependabot %}.' +shortTitle: Solución de errores +redirect_from: + - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors +versions: + free-pro-team: '*' +--- + +{% data reusables.dependabot.beta-note %} + +### Acerca de los errores del {% data variables.product.prodname_dependabot %} + +{% data reusables.dependabot.pull-request-introduction %} + +Si existe algo que impida que el {% data variables.product.prodname_dependabot %} levante una solicitud de cambios, esto se reporta como un error. + +### Investigar los errores de las {% data variables.product.prodname_dependabot_security_updates %} + +Cuando se bloquea al {% data variables.product.prodname_dependabot %} y no puede crear una solicitud de cambios para arreglar una alerta del {% data variables.product.prodname_dependabot %}, éste publica el mensaje de error en la alerta. La vista de {% data variables.product.prodname_dependabot_alerts %} muestra una lista de cualquier alerta que aún no se haya resuelto. Para acceder a la vista de alertas, da clic en **{% data variables.product.prodname_dependabot_alerts %}** en la pestaña de **Seguridad** del repositorio. Donde sea que se genere una solicitud de cambios que arregle una dependencia vulnerable, la alerta incluirá un enlace a dicha solicitud. + +![Vista de las {% data variables.product.prodname_dependabot_alerts %} que muestra un enlace a una solicitud de cambios](/assets/images/help/dependabot/dependabot-alert-pr-link.png) + +Hay tres razones por las cuales una alerta pudiera no tener un enlace a una solicitud de cambios: + +1. No se han habilitado las {% data variables.product.prodname_dependabot_security_updates %} en el repositorio. +1. La alerta es para una dependencia transitoria o indirecta que no se definió explícitamente en un archivo de bloqueo. +1. Un error bloqueó al {% data variables.product.prodname_dependabot %} y éste no puede crear una solicitud de cambios. + +Si existe un error que bloqueó al {% data variables.product.prodname_dependabot %} y éste no puede crear una solicitud de cambios, puedes mostrar los detalles del error si das clic en la alerta. + +![Alerta del {% data variables.product.prodname_dependabot %} que mustra el error que bloqueó la creación de una solicitud de cambios](/assets/images/help/dependabot/dependabot-security-update-error.png) + +### Investigar los errores de las {% data variables.product.prodname_dependabot_version_updates %} + +Cuando el {% data variables.product.prodname_dependabot %} se bloquea y no puede crear una solicitud de cambios para actualizar una dependencia en un ecosistema, éste publica el icono de error en el archivo de manifiesto. Los archivos de manifiesto que administra el {% data variables.product.prodname_dependabot %} se listan en la pestaña de {% data variables.product.prodname_dependabot %}. Para acceder a esta pestaña, en la pestaña de **perspectivas** del repositorio, da clic en **Gráfica de dependencias**, y luego en la pestaña **{% data variables.product.prodname_dependabot %}**. + +![vista del {% data variables.product.prodname_dependabot %} que muestra un error](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png) + +Para ver el archivo de bitácora de cualquier archivo de manifiesto, da clic en el enlace de **Última revisión hace TIEMPO**. Cuando muestras el archivo de bitácora de un manifiesto que se muestra con un símbolo de error (por ejemplo, Maven en la impresión de pantalla anterior), cualquier error se mostrará también. + +![Error y bitácora de una actualizacón de versión del {% data variables.product.prodname_dependabot %} ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) + +### Entender los errores del {% data variables.product.prodname_dependabot %} + +Las solicitudes de cambios para las actualizaciones de seguridad actúan para mejorar una dependencia vulnerable a la versión mínima que incluya un arreglo de la vulnerabilidad. Por el contrario, las solicitudes de cambios para las actualizaciones de versión actúan para mejorar una dependencia a la última versión que permite el paquete de archivos de manifiesto y de configuración del {% data variables.product.prodname_dependabot %}. Como consecuencia, algunos errores son específicos de un tipo de actualización. + +#### El {% data variables.product.prodname_dependabot %} no puede actualizar la DEPENDENCIA a una versión no-vulnerable + +**Únicamente actualizaciones de seguridad.** El {% data variables.product.prodname_dependabot %} no puede crear una solicitud de cambios para actualizar la dependencia vulnerable a una versión segura sin afectar otras dependencias en la gráfica de dependencias de este repositorio. + +Cada aplicación que tenga dependencias tiene una gráfica de dependencias, esto es, una gráfica acíclica dirigida de cada versión de paquete de la cual depende la aplicación directa o indirectamente. Cada vez que se actualiza una dependencia, esta gráfica debe resolverse o la aplicación no se compilará. Cuando un ecosistema tiene una gráfica de dependencias profunda y compleja, por ejemplo, npm y RubyGems, es a menudo imposible mejorar una sola dependencia sin mejorar todo el ecosistema. + +La mejor forma de evitar este problema es mantenerse actualizado con los lanzamientos de versiones más recientes, por ejemplo, habilitando las actualizaciones de versión. Esto aumenta la probabilidad de que una vulnerabilidad en alguna dependencia pueda resolverse con una mejora simple que no afecte la gráfica de dependencias. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". + +#### El {% data variables.product.prodname_dependabot %} no puede actualizar a la versión requerida porque ya existe una solicitud de cambios abierta para la última versión + +**Únicamente actualizaciones de seguridad.** El {% data variables.product.prodname_dependabot %}no creará una solicitud de cambios para actualizar la dependencia vulnerable a una versión segura porque ya existe una solicitud de cambios abierta para actualizar dicha dependencia. Verás éste error cuando se detecte una vulnerabilidad en una dependencia específica y ya exista una solicitud de cambios abierta para actualizar dicha dependencia a la última versión disponible. + +Existen dos opciones: puedes revisar la solicitud de cambios abierta y fusionarla tan pronto como puedas garantizar que el cambio es seguro, o cerrar la solicitud de cambios y activar una solicitud nueva de actualización de seguridad. Para obtener más información, consulta la sección "[Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". + +#### El {% data variables.product.prodname_dependabot %} agotó el tiempo de espera durante su actualización + +El {% data variables.product.prodname_dependabot %} tardó más del límite de tiempo máximo permitido para valorar la actualización requerida y preparar una solicitud de cambios. Este error a menudo se ve únicamente en los repositorios grandes con muchos archivos de manifiesto, por ejemplo, en los proyectos de npm o yarn monorepo, que tienen cientos de archivos *package.json*. Las actualizaciones en el ecosistema de Composer también llevan más tiempo para su valoración y podrían exceder el tiempo de espera. + +Es difícil tratar a este error. Si una actualización de versión excede el tiempo de espera, podrías especificar las dependencias más importantes a actualizar utilizando el parámetro `allow` o, como alternativa, utilizar el parámetro `ignore` para excluir algunas de las dependencias de estas actualizaciones. El actualizar tu configuración podría permitir que el {% data variables.product.prodname_dependabot %} revise la actualización de versión y genere la solicitud de cambios en el tiempo disponible. + +Si una actualización de seguridad excede el tiempo de espera, puedes reducir la probabilidad de que esto suceda si mantienes las dependencias actualizadas, por ejemplo, habilitando las actualizaciones de versión. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". + +#### El {% data variables.product.prodname_dependabot %} no puede abrir más solicitudes de cambios + +Hay un límite en la cantidad de solicitudes de cambios abiertas que el {% data variables.product.prodname_dependabot %} puede generar. Cuando se llega a éste límite, no se podrán abrir más solicitudes de cambios y se reportará este error. La mejor forma de resolver este error es revisar y fusionar algunas de las solicitudes de cambios abiertas. + +Hay límites separados para las solicitudes de cambios de actualización de seguridad y de versión, y esto es para que aquellas de actualización de versión no bloqueen la creación de las de actualización de seguridad. El límite para las solicitudes de cambios de actualizaciones de seguridad es de 10. Predeterminadamente, el límite para las actualizaciones de versión es de 5, pero puedes cambiar ésto utilizando el parámetro `open-pull-requests-limit` en el archivo de configuración. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)". + +La mejor forma de resolver este error es fusionar o cerrar algunas de las solicitudes de cambios existentes y activar una solicitud de cambios nueva manualmente. Para obtener más información, consulta la sección "[Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". + +#### El {% data variables.product.prodname_dependabot %} no puede resolver tus archivos de dependencia + +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. + +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". + +### Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente + +Si desbloqueas al {% data variables.product.prodname_dependabot %}, puedes activar manualmente un nuevo intento de crear una solicitud de cambios. + +- **Actualizaciones de seguridad**—muestra la alerta del {% data variables.product.prodname_dependabot %} que presente el error que arreglaste y da clic en **Crear una actualización de seguridad del {% data variables.product.prodname_dependabot %}**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md new file mode 100644 index 0000000000000..f4837cbe6dcb9 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -0,0 +1,101 @@ +--- +title: Solucionar problemas en la detección de dependencias vulnerables +intro: 'Si la información de la dependencia que reportó {% data variables.product.product_name %} no es lo que esperabas, hay varios puntos a considerar y varias cosas que puedes revisar.' +shortTitle: Solución de problemas de las detecciones +versions: + free-pro-team: '*' +--- + +Los resultados de la detección de dependencias que reporta {% data variables.product.product_name %} pueden ser diferentes a aquellos que devuelven otras herramientas. Esto está justificado y es útil el entender cómo {% data variables.product.prodname_dotcom %} determina las dependencias para tu proyecto. + +### ¿Por qué parece que faltan algunas dependencias? + +{% data variables.product.prodname_dotcom %} genera y muestra los datos de las dependencias de forma diferente a otras herramientas. En consecuencia, si has estado utilizando otra herramienta para identificar dependencias, muy probablemente encuentres resultados diferentes. Considera lo sigueinte: + +* {% data variables.product.prodname_advisory_database %} es una de las fuentes de datos que utiliza {% data variables.product.prodname_dotcom %} para identificar las dependencias vulnerables. Es una base de datos de información de vulnerabilidades orgtanizada y gratuita para los ecosistemas de paquetes comunes en {% data variables.product.prodname_dotcom %}. Esta incluye tanto los datos reportados directamente a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_security_advisories %}, así como las fuentes oficiales y las comunitarias. {% data variables.product.prodname_dotcom %} revisa y organiza estos datos para garantizar que la información falsa o inprocesable no se comparta con la comunidad de desarrollo. Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" y [Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +* La gráfica de dependencias analiza todos los archivos de manifiesto de paquetes conocidos en un repositorio de usuario. Por ejemplo, para npm analizará el archivo _package-lock.json_. Construye una gráfica de todas las dependencias del repositorio y de los dependientes públicos. Esto sucede cuando habilitas la gráfica de dependencias y cuando alguien hace cargas a la rama predeterminada, y esto incluye a las confirmaciones que hacen cambios a un formato de manifiesto compatible. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +* {% data variables.product.prodname_dependabot %} escanea cualquier subida a la rama predeterminada que contenga un archivo de manifiesto. Cuando se agrega un registro de vulnerabilidad nuevo, este escanea todos los repositorios existentes y genera una alerta para cada repositorio vulnerable. Las {% data variables.product.prodname_dependabot_alerts %} se agregan a nivel del repositorio, en vez de crear una alerta por cada vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +* Las {% data variables.product.prodname_dependabot_security_updates %} se activan cuando recibes una alerta sobre una dependencia vulnerable en tu repositorio. Cuando sea posible, el {% data variables.product.prodname_dependabot %} creará una solicitud de cambios en tu repositorio para actualizar la dependencia vulnerable a la versión segura mínima posible que se requiere para evitar la vulnerabilidad. Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" y "[Solucionar problemas en los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". + + El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables bajo ninguna programación, sino cuando algo cambia. Por ejemplo, se activa un escaneo cuando se agrega una dependencia ({% data variables.product.prodname_dotcom %} verifica esto en cada subida), o cuando se descubre una vulnerabilidad nueva y ésta se agrega en la base de datos de asesorías. + +### ¿Por qué no me llegan alertas de vulnerabilidades de algunos ecosistemas? + +{% data variables.product.prodname_dotcom %} limita su soporte para alertas de vulnerabilidades a un conjunto de ecosistemas donde podemos proporcionar datos procesables de alta calidad. Las vulnerabilidades que se organizan en la {% data variables.product.prodname_advisory_database %}, la gráfica de dependencias, las alertas de {% data variables.product.prodname_dependabot_alerts %}, y las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} se proporcionan para varios ecosistemas, incluyendo Maven de Java, npm y Yarn de JavaScript, NuGet de .NET, pip de Python, RubyGems de Ruby y Composer de PHP. Seguiremos agregando soporte para más ecosistemas a la larga. Para obtener una vista general de los ecosistemas de paquete que soportamos, consulta la sección "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". + +Vale la pena señalar que podrían existir [Asesorías de Seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) para otros ecosistemas. La información en una asesoría de seguridad la porporcionan los mantenedores de un repositorio específico. Estos datos no se organizan de la misma forma que la información para los ecosistemas compatibles. + +**Verifica**: ¿Acaso la vulnerabilidad que no se detectó aplica a algún ecosistema no compatible? + +### ¿Acaso la gráfica de dependencias solo encuentra depedencias en los manifiestos y lockfiles? + +La gráfica de dependencias incluye información sobre las dependencias, la cual se declara explícitamente en tu ambiente. Esto es, dependencias que se especifican en un manifiesto o en un lockfile. La gráfica de dependencias también incluye dependencias transitivas generalmente, aún cuando no se especifican en un lockfile, mediante la revisión de las dependencias de las dependencias en un archivo de manifiesto. + +Las {% data variables.product.prodname_dependabot_alerts %} te asesoran sobre las dependencias que debes actualizar, incluyendo aquellas transitivas en donde la versión se puede determinar desde un manifiesto o lockfile. Las alertas de seguridad de {% data variables.product.prodname_dependabot %} solo sugieren un cambio en donde puedan "arreglar" directamente la dependencia, esto es cuando estas son: +* Dependencias directas declaradas explícitamente en un manifiesto o lockfile +* Dependencias transitivas declaradas en un lockfile + +La gráfica de dependencias no incluye las dependencias "sueltas". Las dependencias "sueltas" son archivos individuales que se copian de otra fuernte y se revisan directamente en el repositorio o dentro de un archivo (tal como un archivo ZIP o JAR) en ves de que se referencien en un manifiesto de paquete de administrador o en un lockfile. + +**Verifica**; ¿Acaso no se especifica la vulnerabilidad no detectada para un componente en el manifiesto o lockfile del repositorio? + +### ¿Acaso la gráfica de dependencias detecta dependencias que se especifican utilizando variables? + +La gráfica de dependencias analiza los manifiestos mientras se suben a {% data variables.product.prodname_dotcom %}. Por lo tanto, la gráfica de dependencias no tiene acceso al ambiente de compilación del proyecto, así que no puede resolver variables que se utilizan dentro de los manifiestos. Si utilizas variables dentro de un manifiesto para especificar el nombre, o más comunmente la versión de una dependencia, entonces dicha dependencia no se incluirá en la gráfica de dependencias. + +**Verifica**: ¿Acaso la dependencia faltante se declara en el manifiesto utilizando una variable para su nombre o versión? + +### ¿Existen límites que afecten los datos de la gráfica de dependencias? + +Sí, la gráfica de dependencias tiene dos categorías de límites: + +1. **Límites de procesamiento** + + Estos afectan la gráfica de dependencias que se muestra dentro de {% data variables.product.prodname_dotcom %} y también previenen la creación de {% data variables.product.prodname_dependabot_alerts %}. + + Los manifiestos mayores a 0.5 MB solo se procesan para las cuentas empresariales. En el caso de otras cuentas, los manifiestos mayores a 0.5 MB se ingoran y no crearán {% data variables.product.prodname_dependabot_alerts %}. + + Predeterminadamente, {% data variables.product.prodname_dotcom %} no procesará más de 20 manifiestos por repositorio. Las {% data variables.product.prodname_dependabot_alerts %} no deben crearse para los manifiestos mas allá de éste límite. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}. + +2. **Límites de visualización** + + Estos afectan a lo que se muestra en la gráfica de dependencias dentro de {% data variables.product.prodname_dotcom %}. Sin embargo, estos no afectan las {% data variables.product.prodname_dependabot_alerts %} que se crean. + + La vista de dependencias de la gráfica de dependencias para un repositorio solo muestra 1000 manifiestos. Habitualmente, esto es tan adecuado como es significativamente más alto que el límite de procesamiento descrito anteriormente. En situaciones en donde le límite de procesamiento es mayor a 100, las {% data variables.product.prodname_dependabot_alerts %} se crearán aún para cualquier manifiesto que no se muestre dentro de {% data variables.product.prodname_dotcom %}. + +**Verifica**: ¿La dependencia faltante está en un archivo de manifiesto que tiene más de 0.5 MB, o en un repositorio con una gran cantidad de manifiesto? + +### ¿Acaso el {% data variables.product.prodname_dependabot %} genera alertas para vulnerabilidades que se han conocido por muchos años? + +La {% data variables.product.prodname_advisory_database %} se lanzó en noviembre de 2019 e incialmente rellenó la inclusión de vulnerabilidades informáticas para los ecosistemas compatibles, comenzando en 2017. Cuando agregas CVE a la base de datos, priorizamos la organización de CVE nuevos y los CVE que afecten las versiones nuevas del software. + +Alguna información sobre las vulnerabilidades antiguas se encuentra disponible, especialmente en donde estos CVE se diseminan específicamente, sin embargo, algunas vulnerabilidades no se incluyen en la {% data variables.product.prodname_advisory_database %}. Si hay una vulnerabilidad antigua específica la cual necesites incluir en la base de datos, contacta a {% data variables.contact.contact_support %}. + +**Verifica**: ¿Acaso la vulnerabilidad no detectada tiene una fecha depublicación más antigua de 2017 en la Base de Datos de Vulnerabilidades Nacional? + +### Por qué la {% data variables.product.prodname_advisory_database %} utiliza un subconjunto de datos de vulnerabilidades publicados? + +Algunas herramientas de terceros utilizan datos de CVE sin organizar y no las verificó ni filtró un humano. Esto significa que los CVE con errores de etiquetado o de severidad, o con cualquier problema de calidad, causarán alertas más frecuentes, ruidosas y menos útiles. + +Ya que {% data variables.product.prodname_dependabot %} utiliza datos organizado en la {% data variables.product.prodname_advisory_database %}, la cantidad de alertas podría ser menor, pero las alertas que sí recibas serán exactas y relevantes. + +### ¿Acaso cada vulnerabilidad de la dependencia genera una alerta separada? + +Cuadno una dependencia tiene vulnerabilidades múltiples, solo se genera una alerta agregada para esta dependencia en vez de una por cada vulnerabilidad. + +Las {% data variables.product.prodname_dependabot_alerts %} cuentan en {% data variables.product.prodname_dotcom %} y muestran un total para la cantidad de alertas, es decir, la cantidad de dependencias con vulnerabilidades y no la cantidad de vulnerabilidades. + +![Vista de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-view.png) + +Cuando das clic para mostrar los detalles de la alerta puedes ver cuántas vulnerabilidades se incluyen en la misma. + +![Vulnerabilidades múltiples para una alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png) + +**Verifica**: Si hay una discrepancia en la cantidad total que ves, verifica si no estás comparando la cantidad de alertas con la cantidad de vulnerabilidades. + +### Further reading + +- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" +- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md new file mode 100644 index 0000000000000..4e14d8cfd8b1b --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -0,0 +1,39 @@ +--- +title: Ver y actualizar dependencias vulnerables en tu repositorio +intro: 'Si {% data variables.product.product_name %} descubre una dependencia vulnerable en tu proyecto, podrás verla en la pestaña de alertas del Dependabot de tu repositorio. Posteriormente, podrás actualizar tu proyecto para resolver o descartar la vulnerabilidad.' +redirect_from: + - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository +permissions: Los administradores de repositorio y propietarios de la organización pueden ver y actualizar las dependencias. +shortTitle: Ver y actualizar las dependencias vulnerables +versions: + free-pro-team: '*' +--- + +La pestaña de alertas del {% data variables.product.prodname_dependabot %} de tu repositorio lista todas las {% data variables.product.prodname_dependabot_alerts %} abiertas y cerradas, y las {% data variables.product.prodname_dependabot_security_updates %} correspondientes. Puedes clasificar la lista de alertas utilizando el menú desplegable y hacer clic en alertas específicas para obtener más detalles. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +Puedes habilitar las alertas de seguridad automáticas para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + +{% data reusables.repositories.dependency-review %} + +### Acerca de las actualizaciones para las dependencias vulnerables en tu repositorio + +{% data variables.product.product_name %} genera {% data variables.product.prodname_dependabot_alerts %} cuando detectamos que tu base de código está utilizando dependencias con vulnerabilidades conocidas. Para los repositorios en donde se habilitan las {% data variables.product.prodname_dependabot_security_updates %} cuando {% data variables.product.product_name %} detecta una dependencia vulnerable en la rama predeterminada, {% data variables.product.prodname_dependabot %} crea una solicitud de cambios para arreglarla. La solicitud de extracción mejorará la dependencia a la versión segura mínima que sea posible y necesaria para evitar la vulnerabilidad. + +### Ver y actualizar las dependencias vulnerables + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Haz clic en la alerta que quieres ver. ![Alerta seleccionada en la lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list.png) +1. Revisa los detalles de la vulnerabilidad y, en caso de que esté disponible, la solicitud de extracción que contienen la actualización de seguridad automatizada. +1. Opcionalmente, si no existe ya una actualización de {% data variables.product.prodname_dependabot_security_updates %} para la alerta, para crear una solicitud de extracción o para resolver la vulnerabilidad, da clic en **Crear una actualización de eguridad del {% data variables.product.prodname_dependabot %}**. ![Crea un botón de actualización de seguridad del {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button.png) +1. Cuando estés listo para actualizar tu dependencia y resolver la vulnerabilidad, fusiona la solicitud de extracción. Cada solicitud de extracción que levante el {% data variables.product.prodname_dependabot %} incluye información sobre los comandos que puedes utilizar para controlar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Adminsitrar las solicitudes de extracción para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)". +1. Opcionalmente, si se está arreglando la alerta, si es incorrecta o si se ubica en una sección de código sin utilizar, utiliza el menú desplegable de "Descartar" y da clic en una razón para descartar la alerta.![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) + +### Further reading + +- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" +- "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)" +- "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" +- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" +- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md new file mode 100644 index 0000000000000..68364d6830ee1 --- /dev/null +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md @@ -0,0 +1,12 @@ +--- +title: Retirar una asesoría de seguridad +intro: Puedes retirar una asesoría de seguridad que hayas publicado. +versions: + free-pro-team: '*' +--- + +Si publicas una asesoría de seguridad por error, puedes retirarla contactando a {% data variables.contact.contact_support %}. + +### Further reading + +- [Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory) diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md new file mode 100644 index 0000000000000..7bc70494e0db4 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -0,0 +1,104 @@ +--- +title: Acerca de las notificaciones +intro: 'Las notificaciones proporcionan actualizaciones sobre las actividades de {% data variables.product.product_name %} a las que te hayas suscrito. Puedes utilizar la bandeja de notificaciones para personalizar, clasificar y administrar tus actualizaciones.' +redirect_from: + - /articles/notifications/ + - /articles/about-notifications + - /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Notificaciones y suscripciones + +Puedes elegir recibir actualizaciones continuas sobre actividades específicas en {% data variables.product.product_name %} mediante una suscripción. Las notificaciones son actualizaciones que recibes por alguna actividad específica a la que te hayas suscrito. + +#### Opciones de suscripción + +Puedes elegir suscribirte a las notificaciones de: +- Una conversación sobre un informe de problemas, solicitud de extracción o gist específico. +- Todas las actividades en un repositorio o en un debate de equipo. +- Actividades de CI, tales como el estado de los flujos de trabajo en los repositorios configurados con {% data variables.product.prodname_actions %}. +{% if currentVersion == "free-pro-team@latest" %} +- Propuestas, solicitudes de cambios, lanzamientos y debates (si están habilitados) de un repositorio. +{% endif %} +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +- Lanzamientos en un repositorio. +{% endif %} + +También puedes elegir seguir automáticamente todos los repositorios en los que tienes acceso de escritura, con excepción de sus bifurcaciones. Puedes seguir de cerca manualmente a cualquier otro repositorio al que tengas acceso si das clic en **Seguir**. + +Si ya no te interesa alguna conversación, te puedes dar de baja, dejar de seguir o personalizar los tipos de notificaciones que recibirás en el futuro. Por ejemplo, si ya no quieres recibir notificaciones de algún repositorio en particular, puedes dar clic en **Darse de baja**. Para obtener más información, consulta la sección "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". + +#### Suscripciones predeterminadas + +Generalmente, estarás suscrito automática y predeterminadamente a las conversaciones cuando: +- No has inhabilitado el seguimiento automático a través de tu configuración de notificaciones para los repositorios o equipos a los cuales te has unido. Esta configuración está predeterminadamente habilitada. +- Te han asignado a un informe de problemas o solicitud de extracción. +- Has abierto una solicitud de extracción, informe de problemas, o has creado una publicación para que un equipo la debata. +- Has comentado en un hilo. +- Te has suscrito a un hilo manualmente dando clic en **Seguir** o **Suscribirse**. +- Han @mencionado tu nombre de usuario. +- Has cambiado el estado de un hilo, como cuando cierras un informe de problemas o fusionas una solicitud de extracción. +- Se ha @mencionado a algún equipo al que pertenezcas. + +También está predeterminado que sigas automáticamente a todos los repositorios que has creado y sean propiedad de tu cuenta de usuario. + +Para darte de baja de las conversaciones a las cuales estás suscrito automáticamente, puedes cambiar tu configuración de notificaciones o darte de baja directamente o dejar de seguir la actividad de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". + +### Personalizar notificaciones y suscripciones + +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. + +Para personalizar los tipos de actualizaciones que deseas recibir y el lugar a donde quieras que se envíen, modifica tu configuración de notificaciones. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". + +Para poder seguir administrando tus suscripciones, revisa los repositorios que sigues y las suscripciones que tienes y date de baja de aquellos que ya no quieras seguir. Para obtener más información, consulta la sección "[Administrar suscripciones de actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". + +Para personalizar la manera en la que deseas recibir actualizaciones para solicitudes de extracción o informes de problemas específicos, puedes configurar tus preferencias dentro de las mismas. Para obtener más información, consulta la sección "[Categorizar una notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} +Puedes habilitar las notificaciones de subida en la +app de {% data variables.product.prodname_mobile %}. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)". +{% endif %} + +### Razones para que recibas notificaciones + +Tu bandeja de entrada se configura con filtros predeterminados que representan las razones más comunes para que la gente necesite dar seguimiento a sus notificaciones. Para obtener más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)". + +Tu bandeja de entrada muestra las `reasons` (razones) para que recibas notificaciones a modo de etiqueta. + +![Etiquetas de razones en la bandeja de entrada](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) + +Puedes filtrar tu bandeja de entrada por razón por la cual estás suscrito a notificaciones. Por ejemplo, para ver únicamente solicitudes de extracción en donde alguien solicitó tu revisión, puedes utilizar el filtro de búsqueda `review-requested` (revisión solicitada). + +![Filtrar notificaciones por revisión de la razón solicitada](/assets/images/help/notifications-v2/review-requested-reason.png) + +Si configuraste las notificaciones para que se enviaran por correo electrónico y crees que estás recibiendo notificaciones que no te pertenecen, considera dar solución a los problemas especificando el tema en los encabezados de correo electrónico que muestren el receptor al que se pretende llegar. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)". + +### Clasificar las notificaciones de tu bandeja de entrada + +Para administrar tus notificaciones de manera efectiva, puedes clasificar tu bandeja de entrada con opciones para: +- Eliminar una notificación de la bandeja de entrada marcada como **Completada**. Puedes revisar las notificaciones **Completadas** en un mismo lugar dando clic en **Completada** en la barra lateral o utilizando el query `is:done`. +- Marcar la notificación como leída o no leída. +- **Guardar** una notificación para su revisión posterior. Las notificaciones **Guardadas** se resaltan en tu bandeja de entrada. Puedes revisar las notificaciones **Guardadas** en un mismo lugar en la barra lateral si das clic en **Guardadas**" o utilizando el query `is:saved`. +- Darte de baja automáticamente de esta notificación y de las actualizaciones futuras a esta conversación. Darte de baja también elimina la notificación de tu bandeja de entrada. Si te das de baja de una conversación y alguien menciona tu nombre de usuario o el equipo al que perteneces, del cual recibes notificaciones, entonces comenzarás a recibirlas de nuevo para dicha conversación. + +También puedes clasificar varias notificaciones al mismo tiempo desde tu bandeja de entrada. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)". + +### Personalizar tu bandeja de entrada de notificaciones + +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. Por ejemplo, puedes crear un filtro personalizado para un proyecto de código abierto en el que contribuyes y únicamente ver notificaciones para el repositorio en el que se te mencione. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para ver más ejemplos de cómo personalizar tu flujo de trabajo de clasificaciones, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". + +### Política de retención de notificaciones + +Las notificaciones que no se marquen como **Guardadas** se mantendrán por 5 meses. Aquellas marcadas como **Guardadas** se mantendrán por tiempo indefinido. Si tu notificación guardada tiene más de 5 meses y la dejas de guardad, ésta desaparecerá de tu bandeja de entrada en un día. + +### Retroalimentación y soporte + +Si tienes retroalimentación o alguna solicitud de características, utiliza el [formato de retroalimentación para notificaciones](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback). diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md new file mode 100644 index 0000000000000..7730050202dc1 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -0,0 +1,227 @@ +--- +title: Configurar notificaciones +intro: 'Elige el tipo de actividad en {% data variables.product.product_name %} para el que deseas recibir notificaciones y cómo deseas que se entreguen estas actualizaciones.' +redirect_from: + - /articles/about-web-notifications + - /format-of-notification-emails/ + - /articles/configuring-notification-emails/ + - /articles/about-notification-emails/ + - /articles/about-email-notifications + - /articles/accessing-your-notifications + - /articles/configuring-notification-delivery-methods/ + - /articles/managing-notification-delivery-methods/ + - /articles/managing-notification-emails-for-organizations/ + - /articles/choosing-the-delivery-method-for-your-notifications + - /articles/choosing-the-types-of-notifications-you-receive/ +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Opciones de entrega de notificaciones + +Puedes recibir notificaciones de actividad en {% data variables.product.product_name %} en las siguientes ubicaciones. + + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} + - La bandeja de notificaciones en {% data variables.product.prodname_mobile %}, la cual sesincroniza con aquella de {% data variables.product.product_name %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} +{% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obtener más información, consulta la sección "[Escoger tu configuración de notificaciones](#choosing-your-notification-settings)". +{% endif %} + +{% data reusables.notifications.shared_state %} + +#### Beneficios de la bandeja de entrada de notificaciones + +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: + - Clasificar varias notificaciones al mismo tiempo. + - Marcar las notificaciones como **Completadas** y eliminarlas de tu bandeja de entrada. Para ver todas tus notificaciones marcadas como **Completadas**, utiliza el query `is:done`. + - Guardar una notificación para revisarla más tarde. Las notificaciones se resaltan en tu bandeja de entrada y se mantienen indefinidamente. Para ver todas tus notificaciones guardadas, utiliza el query `is:saved`. + - Darse de baja y eliminar una notificación de tu bandeja de entrada. + - Prever el informe de problemas, solicitud de extracción o debate de equipo de donde se origina la notificación en {% data variables.product.product_name %} desde dentro de la bandeja de notificaciones. + - Ver una de las últimas razones por las cuales estás recibiendo una notificación desde tu bandeja de entrada con la etiqueta `razones`. + - Crear filtros personalizados para enfocarte en diferentes notificaciones cuando así lo quieras. + - Agrupar notificaciones por repositorio o fecha en tu bandeja de entrada para obtener un resumen rápido con menos cambios de contexto + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} +Adicionalmente, la bandeja de notificaciones en +{% data variables.product.prodname_mobile %} te permite clasificarlas en modo oscuro y recibir notificaciones de subida para las menciones directas. Para obtener más información, consulta la sección "[Habilitar notificaciones de carga con GitHub para dispositivos móviles](#enabling-push-notifications-with-github-for-mobile)" o "[GitHub para dispositivos móbiles](/github/getting-started-with-github/github-for-mobile)". +{% endif %} + +#### Beneficios de utilizar un cliente de correo electrónico para las notificaciones + +Un beneficio de utilizar un cliente de correo electrónico es que todas tus notificaciones se pueden mantener por tiempo indefinido dependiendo de la capacidad de almacenamiento de éste. Tus notificaciones en bandeja de entrada se mantendrán únicamente por 5 meses a menos de que las hayas marcado como **Guardadas**. Las notificaciones **Guardadas** se mantendrán por tiempo indefinido. Para obtener más información acerca de la política de retención de tu bandeja de entrada, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)". + +Enviar notificaciones a tu cliente de correo electrónico también te permite personalizar tu bandeja de entrada de acuerdo con la configuración del mismo, lo cual puede incluir etiquetas personalizadas o con códigos de color. + +Las notificaciones por correo electrónico también permiten la flexibilidad con los tipos de notificaciones que recibes y te permiten escoger diferentes direcciones para las actualizaciones. Por ejemplo, puedes enviar ciertas notificaciones para un repositorio a una dirección de correo electrónico personal verificada. Para obtener más información acerca de las opciones de personalización para tu correo electrónico, consulta la secicón "[Personalizar tus notificaciones por correo electrónico](#customizing-your-email-notifications)". + +### Acerca de participar y seguir de cerca las notificaciones + +Cuando observas un repositorio, te suscribes a las actualizaciones de la actividad en el mismo. De forma similar, cuando observas las discusiones específicas de un equipo, te suscribes a todas las actualizaciones de la conversación en la página de ese equipo. Para obtener más información, consulta [Acerca de los debates del equipo](/github/building-a-strong-community/about-team-discussions)". + +Para ver los repositorios que estás observando, dirígete a tu [página de observados](https://github.com/watching). Para obtener más información, consulta la sección "[Administrar suscricpiones y notificaciones en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} +#### Configurar notificaciones +{% endif %} +Puedes configurar las notificaciones de un repositorio en la página del mismo, o en tu página de observados. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Puedes elegir solo recibir notificaciones para los lanzamientos de un repositorio o ignorar todas las notificaciones del mismo.{% endif %}{% if currentVersion == "free-pro-team@latest" %} + +#### Acerca de las notificaciones personalizadas +{% data reusables.notifications-v2.custom-notifications-beta %} +Puedes personalizar las notificaciones de un repositorio, por ejemplo, puedes elegir que solo se te notifique cuando sucedan actualizaciones en uno o más tipos de eventos (propuestas, solicitudes de cambios, lanzamientos, debates) dentro de un repositorio, o ignorar todas las notificaciones del mismo. +{% endif %} Para obtener más información, consulta la sección "[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)". + +#### Participar en conversaciones +Siempre que comentes en una conversación, o cuando alguien @menciona tu nombre de usuario, estarás _participando_ en una conversación. Predeterminadamente, estás suscrito automáticamente a una conversación cuando participas en ella. Puedes desuscribirte manualmente de una conversación en la que hayas participado si das clic en **Desuscribir** en el informe de problemas o solicitud de extracción, o a través de la opción de **Desuscribir** en la bandeja de notificaciones. + +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. + +![Opciones de notificación para observar y participar](/assets/images/help/notifications-v2/participating-and-watching-options.png) + +Por ejemplo: + - Si no quieres que se te envíen notificaciones a tu correo electrónico, deselecciona **email** de la opción en participar y seguir de cerca las notificaciones. + - Si quieres recibir notificaciones por correo electrónico cuando hayas participado en una conversación, entonces puedes seleccionar **email** debajo de "Participando". + +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. + +### Personalizar tus notificaciones de correo electrónico + +Después de activar las notificaciones por correo electrónico, {% data variables.product.product_name %} te enviará notificaciones como correos electrónicos con varias partes que contienen copias del contenido tanto en HTML como en texto simple. El contenido de las notificaciones por correo electrónico incluye cualquier Markdown, @menciones, emojis, vínculos hash, etc., que aparecen en el contenido original en {% data variables.product.product_name %}. Si solo quieres ver el texto en el correo electrónico, puedes configurar tu cliente de correo electrónico para que muestre solo la copia de texto simple. + +{% data reusables.notifications.outbound_email_tip %} + +{% data reusables.notifications.shared_state %} + +{% if currentVersion == "free-pro-team@latest" %} + +Si usas Gmail, puedes hacer clic en un botón al lado del correo electrónico para notificaciones para visitar la propuesta o la solicitud de extracción original que generó la notificación. + +![Botones en Gmail](/assets/images/help/notifications/gmail-buttons.png) + +{% endif %} + +Escoge una dirección de correo electrónico predeterminada en donde quieras enviar actualizaciones para las conversaciones que observes o en las cuales participes. También puedes especificar la actividad de {% data variables.product.product_name %} sobre la cual quieras recibir actualizaciones para utilizar tu dirección de correo electrónico predeterminada. Por ejemplo, escoge si quieres recibir actualizaciones en tu correo electrónico predeterminado sobre: + - Comentarios sobre informes de problemas y solicitudes de extracción. + - Revisiones de solicitudes de extracción. + - Subidas de solicitudes de extracción. + - Tus propias actualizaciones, tales como cuando abres, comentas o cierras un informe de problemas o solicitud de extracción. + +Dependiendo de la organización a la que pertenezca el repositorio, también puedes enviar notificaciones a direcciones de correo electrónico distintas. Tu organización podría requerir que dicha dirección se verifique en un dominio específico. Para obtener más información, consulta la sección "[Escoger a dónde se envían las notificaciones de tu organización por correo electrónico](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)". + +También puedes enviar las notificaciones para un repositorio específico a una dirección decorreo electrónico. Para obtener más información, consulta la sección "[Acerca de las notificaciones por correo electrónico para las cargas a tu repositorio](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". + +{% data reusables.notifications-v2.email-notification-caveats %} + +### Filtrar las notificaciones por correo electrónico + +Cada notificación por correo electrónico que envía {% data variables.product.product_name %} contiene información de encabezado. La información del encabezado en cada correo electrónico es consistente, para que puedas usarla en tu cliente de correo electrónico para filtrar o enviar todas las notificaciones de {% data variables.product.product_name %} o ciertos tipos de notificaciones de {% data variables.product.product_name %}. + +Si crees que estás recibiendo notificaciones que no te pertenecen, examina los encabezados `X-GitHub-Recipient` y `X-GitHub-Recipient-Address`. Estos encabezados te muestran quién es el destinatario previsto. Dependiendo de tu configuración de correo electrónico, podrías recibir notificaciones destinadas para otro usuario. + +Las notificaciones por correo electrónico de {% data variables.product.product_name %} contienen la siguiente información de encabezado: + +| Encabezado | Información | +| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| dirección `De` | Esta dirección siempre será {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'aquella dirección de correo electrónico de "no-reply" que configuró tu administrador de sitio'{% endif %}. | +| campo `Para` | Este campo se conecta directamente al hilo.{% if currentVersion != "github-ae@latest" %} Si respondes al correo electrónico, agregarás un comentario nuevo a la conversación.{% endif %} +| dirección `Cc` | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son:
  • `assign`: Te asignaron a una propuesta o solicitud de extracción.
  • `author`: Creaste una propuesta o solicitud de extracción.
  • `comment`: Comentaste una propuesta o solicitud de extracción.
  • `manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.
  • `mention`: Te mencionaron en una propuesta o solicitud de extracción.
  • `push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.
  • `review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.
    • {% if currentVersion != "github-ae@latest" %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.
    • {% endif %}
  • `state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.
  • `subscribed`: Hubo una actualización en un repositorio que estás mirando.
  • `team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.
  • `your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.
| +| Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `..{% 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 %} Los posibles niveles de gravedad son:
  • `low`
  • `moderate`
  • `high`
  • `critical`
Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". |{% endif %} + +### Escoger tu configuración de notificaciones + +{% data reusables.notifications.access_notifications %} +{% data reusables.notifications-v2.manage-notifications %} +3. En la página de configuración de notificaciones, elige cómo deseas recibir las notificaciones cuando: + - Existen actualizaciones en repositorios o debates de equipo que estás siguiendo de cerca, o en una conversación en la que estás participando. Para obtener más información, consulta la sección "[Acerca de participar y seguir notificaciones](#about-participating-and-watching-notifications)". + - Obtienes acceso a un repositorio nuevo o te has unido a un equipo nuevo. Para obtener más información, consulta la sección "[Observar automáticamente](#automatic-watching)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + - Hay nuevas {% if page.version == 'dotcom' %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} en tu repositorio. Para obtener más información, consulta la sección "[{% data variables.product.prodname_dependabot_alerts %} opciones de notificación](#dependabot-alerts-notification-options)". {% endif %}{% if currentVersion == "enterprise-server@2.21" %} + - Hay nuevas alertas de seguridad en tu repositorio. Para obtener más información, consulta la sección "[Opciones de las notificaciones para las alertas de seguridad](#security-alert-notification-options)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} + - Hay actualizaciones en la ejecución de flujos de trabajo en los repositorios configurados con {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[opciones de notificación de {% data variables.product.prodname_actions %}](#github-actions-notification-options)".{% endif %} + +### Seguimiento automático + +Predeterminadamente, cada que obtienes acceso a un repositorio nuevo, comenzarás automáticamente a observarlo. En cualquier momento que te unas a un equipo, te suscribirás automáticamente a las actualizaciones y recibirás notificaciones cuando se @mencione a dicho equipo. Si no te quieres suscribir automáticamente, puedes deseleccionar las opciones de observar automáticamente. + + ![Opciones de observar automáticamente](/assets/images/help/notifications-v2/automatic-watching-options.png) + +Si inhabilitas la opción de "Observar los repositorios automáticamente", no podrás observar automáticamente tus propios repositorios. Debes navegar hasta tu página de repositorio y escoger la opción de observar. + +### Elegir a dónde se envían las notificaciones por correo electrónico de tu organización + +Si perteneces a una organización, puedes escoger la cuenta de correo electrónico a la que desees que se envíen las notificaciones de la actividad de la empresa. Por ejemplo, si perteneces a una organización de trabajo, es posible que desees que tus notificaciones se envíen a tu dirección de correo electrónico laboral, en lugar de tu dirección personal. + +{% data reusables.notifications-v2.email-notification-caveats %} + +{% data reusables.notifications.access_notifications %} +{% data reusables.notifications-v2.manage-notifications %} +3. En "Default notification email" (Correo electrónico de notificación predeterminado), selecciona la dirección de correo electrónico a la que deseas que se envíen las notificaciones. + ![Desplegable de direcciones de correo electrónico de notificación predeterminadas](/assets/images/help/notifications/notifications_primary_email_for_orgs.png) +4. Haz clic en **Save ** (guardar). + +#### Personalizar rutas de correo electrónico por organización + +Si eres un miembro de más de una organización, puedes configurar cada una para enviar notificaciones a cualquiera de{% if currentVersion == "free-pro-team@latest" %} tus direcciones de correo electrónico verificadas{% else %} las direcciones de correo electrónico que hayas agregado a tu cuenta de {% data variables.product.product_name %}{% endif %}. {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Verificar tus direcciones de correo electrónico](/articles/verifying-your-email-address)".{% endif %} + +{% data reusables.notifications.access_notifications %} +{% data reusables.notifications-v2.manage-notifications %} +3. En "Custom routing" (Enrutamiento personalizado) busca el nombre de tu organización en la lista. + ![Lista de organizaciones y direcciones de correo electrónico](/assets/images/help/notifications/notifications_org_emails.png) +4. Haz clic en **Edit** (Editar) junto a la dirección de correo electrónico que deseas cambiar. ![Editar las direcciones de correo electrónico de la organización](/assets/images/help/notifications/notifications_edit_org_emails.png) +5. Selecciona una de las direcciones de correo electrónico verificadas, luego haz clic en **Save** (Guardar). + ![Alternar tus direcciones de correo electrónico por organización](/assets/images/help/notifications/notifications_switching_org_email.gif) + +{% if currentVersion != "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot_alerts %}opciones de notificación +{% else %} +### Opciones de notificación para las alertas de seguridad +{% endif %} + +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} +{% data reusables.notifications.vulnerable-dependency-notification-options %} +Para obtener más información acerca de los métodos de entrega de notificaciones que tienes disponibles y para obtener consejos sobre cómo optimizar tus notificaciones para + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}las alertas de seguridad{% endif %}, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_actions %}opciones de notificación + +Elige cómo quieres recibir las actualizaciones para las ejecuciones de flujo de trabajo en los repositorios que estás observando y que se configuraron con {% data variables.product.prodname_actions %}. También puedes elegir recibir únicamente las notificaciones para las ejecuciones de flujo de trabajo fallidas. + + ![Opciones de alerta del {% data variables.product.prodname_dependabot_short %}](/assets/images/help/notifications-v2/github-actions-notification-options.png) + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} +### Habilitar notificaciones de carga con {% data variables.product.prodname_mobile %} + +Cuando instalas {% data variables.product.prodname_mobile %}, ingresarás automáticamente en las notificaciones web. Puedes entonces habilitar las notificaciones de carga para las menciones directas desde la app. + +Por el momento, solo puedes recibir notificaciones para cargas a repositorios en {% data variables.product.prodname_mobile %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +#### Habilitar notificaciones de carga con {% data variables.product.prodname_ios %} + +1. Toca tu foto de perfil sobre "Principal". +2. Para ver tu configuración, toca en {% octicon "gear" aria-label="The Gear icon" %}. ![Icono de configuración de GitHub en iOS](/assets/images/help/mobile/ios-settings-icon.png) +3. Para actualizar tu configuración de notificaciones, toca en **Notificaciones de carga**. +4. Para habilitar las notificaciones de carga para menciones directas, utiliza el habilitador de **Menciones Directas**. + +{% if currentVersion == "free-pro-team@latest" %} +#### Habilitar notificaciones de carga con {% data variables.product.prodname_android %} + +1. Toca tu foto de perfil sobre "Principal". +2. Para ver tu configuración, toca en {% octicon "gear" aria-label="The Gear icon" %}. ![Icono de configuración de GitHub en Android](/assets/images/help/mobile/android-settings-icon.png) +3. Para habilitar las notificaciones de carga para menciones directas, utiliza el habilitador de **Menciones Directas**. +{% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md new file mode 100644 index 0000000000000..978ae2b3fa585 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md @@ -0,0 +1,66 @@ +--- +title: Personalizar un flujo de trabajo para clasificar tus notificaciones +intro: 'Para crear un flujo de trabajo ideal para clasificar tus notificaciones, puedes adaptar y personalizar estos flujos de trabajo de ejemplo.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +### Comenzar la clasificación en tu bandeja de entrada + +Antes de que comiences a clasificar tu bandeja de entrada, considera si prefieres encontrar y responder primero a las actualizaciones más importantes o si quieres vaciar tu bandeja de entrada de las actualizaciones que te distraen y que son fáciles de clasificar o de eliminar. + +Puedes decidir utilizar una combinación de ambos acercamientos en varios momentos, dependiendo del volumen de notificaciones que tengas. + +Para encontrar un flujo de trabajo de ejemplo que trata sobre encontrar y responder a las notificaciones más importantes, consulta la sección "[Revisar tus notificaciones con prioridad más alta](#checking-your-highest-notification-priorities)". + +Para encontrar un ejemplo de flujo de trabajo que muestra cómo eliminar las notificaciones que se pueden clasificar o eliminar fácilmente, consulta la sección "[Borrar tus notificaciones menos importantes](#clearing-your-least-important-notifications)". + +### Revisar las notificaciones con prioridades más altas + +Elige qué tipo de notificaciones son más urgentes de revisar y escoge un la hora en la que te sea más conveniente revisarlas. Deberás considerar la pregunta "¿A quién estoy bloqueando?" + +Por ejemplo, puedes elegir revisar tus notificaciones en este orden en la mañana mientras haces la planeación de tu día en general: + - Solicitudes de extracción en donde se solicita tu revisión. (filtra por `reason:review-requested`) + - Eventos en donde se @menciona tu nombre de usuario, también llamadas menciones directas. (filtra por `reason:mention`) + - Eventos en donde se @menciona un equipo del cual eres miembro, también llamadas menciones de equipo. (filtra por `reason:team-mention`) + - Fallos de flujo de trabajo de IC para un repositorio en específico. (filtra por by `reason:ci-activity` y `repo:owner/repo-name` y asegúrate de que habilitaste las notificaciones de IC para fallas en el flujo de trabajo en tu configuración de notificaciones) + + {% tip %} + + **Tip:** Para revisar rápidamente tus prioridades más altas, configura los filtros personalizados de acuerdo con su prioridad de revisión. Para obtener más información, consulta la sección "[Administrar notificación desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#customizing-your-inbox-with-custom-filters)". + + {% endtip %} + +### Dar seguimiento a las actualizaciones de las notificaciones en curso + +Para dar seguimiento a las notificaciones, podrías considerar la pregunta "¿En qué estaba bloqueado y ya no lo estoy?" Elige tus prioridades de notificaciones para seguimiento. Elige tus prioridades de notificaciones de seguimiento. + +Por ejemplo, puedes decidir dar seguimiento en este orden: + - Los informes de problemas y solicitudes de extracción a los que estás asignado. Inmediatamente cierra cualquier informe de problemas o solicitudes de extracción que puedas y añade actualizaciones. Guarda las notificaciones que desees revisar después conforme lo necesites. + - Revisa las notificaciones en la bandeja de guardados, especialmente las que no leídas. Si el hilo ya no es relevante, desmarca {% octicon "bookmark" aria-label="The bookmark icon" %} para eliminar la notificación de la bandeja de guardados, y márcala como no guardada. + +### Administrar notificaciones de prioridad más baja + +Después de clasificar las notificaciones de prioridad alta, revisa las notificaciones restantes, tales como las de participación. Considera las siguientes preguntas: + - ¿Puedes darte de baja de esta notificación? ¿Se ha completado la notificación y se encuentra lista para marcarse como **Completada**? + {% tip %} + + **Tip:**Cuando te das de baja de una notificación, ya no recibirás nuevas actualizaciones a menos de que comiences a participar en el hilo o que @mencionen a tu usuario o a algún equipo al que pertenezcas. Cuando marcas alguna notificación como **Completada**, esta se elimina de la vista de tu bandeja principal y se puede visualizar con el query `is:read`. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)". + + {% endtip %} + - ¿Te gustaría recibir actualizaciones en el futuro cuando este informe de problemas o solicitud de extracción se cierre o se reabra, o cuando se fusione una solicitud de extracción? Para obtener más información sobre estas opciones, consulta la sección [Clasificar solo una notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". + - ¿Te gustaría evitar el seguir recibiendo notificaciones como esta posteriormente? En ese caso, considera darte de baja. Para obtener más información, consulta la sección "[Administrar suscripciones de actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". + +### Limpiar tus notificaciones menos importantes + +Elige qué tipo de notificaciones son las que puedes clasificar y eliminar de tu bandeja de entrada mas rápida y fácilmente, idealmente, clasificar varias notificaciones al mismo tiempo. + +Por ejemplo, puedes decidir eliminar las notificaciones en este orden: + - Notificaciones de participación en las que te puedes dar de baja. + - Actualizaciones de repositorios que no son relevantes como para continuar con su seguimiento. + +Para obtener más información sobre la administración de notificaciones múltiples en tu bandeja de entrada al mismo tiempo, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)". + +También podrías considerar cambiar tus ajustes de notificaciones o desuscribirte de estas actualizaciones si es posible. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" o "[Administrar tus suscripciones para la actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/index.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/index.md new file mode 100644 index 0000000000000..4ee3452ce9d93 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/index.md @@ -0,0 +1,26 @@ +--- +title: Administrar suscripciones y notificaciones en GitHub +redirect_from: + - /categories/76/articles/ + - /categories/notifications/ + - /categories/receiving-notifications-about-activity-on-github +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +### Índice + +{% topic_link_in_list /setting-up-notifications %} + {% link_in_list /about-notifications %} + {% link_in_list /configuring-notifications %} + +{% topic_link_in_list /viewing-and-triaging-notifications %} + {% link_in_list /managing-notifications-from-your-inbox %} + {% link_in_list /triaging-a-single-notification %} + {% link_in_list /customizing-a-workflow-for-triaging-your-notifications %} + +{% topic_link_in_list /managing-subscriptions-for-activity-on-github %} + {% link_in_list /viewing-your-subscriptions %} + {% link_in_list /managing-your-subscriptions %} diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md new file mode 100644 index 0000000000000..0862dd1995a7a --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -0,0 +1,185 @@ +--- +title: Administrar las notificaciones en tu bandeja de entrada +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' +redirect_from: + - /articles/marking-notifications-as-read + - /articles/saving-notifications-for-later +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Acerca de tu bandeja de entrada + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} +{% data reusables.notifications-v2.notifications-inbox-required-setting %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". +{% endif %} + +Para acceder a tu bandeja de notificaciones, en la esquina superior derecha de cualquier página, da clic en {% octicon "bell" aria-label="The notifications bell" %}. + + ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) + +Tu bandeja de entrada muestra todas las notificaciones de las cuales aún no te has desuscrito o que no has marcado como **Hecho**. Puedes personalizar tu bandeja de entrada como mejor se acople con tu flujo de trabajo utilizando filtros, visualizando todas las notificaciones o únicamente las que no se han leído, y agrupando tus notificaciones para obtener un resumen rápido. + + ![vista de bandeja de entrada](/assets/images/help/notifications-v2/inbox-view.png) + +Predeterminadamente, tu bandeja de entrada mostrará las notificaciones leídas y no leídas. Para solo ver las no leídas, da clic en **No leídas** o utiliza la consulta `is:unread`. + + ![vista de no leídos en bandeja de entrada](/assets/images/help/notifications-v2/unread-inbox-view.png) + +### Opciones de clasificación + +Tienes varias opciones para clasificar las notificaciones de tu bandeja de entrada. + +| Opción de clasificación | Descripción | +| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Save | Guarda tu notificación para revisarla posteriormente. Para guardar una notificación, da clic en {% octicon "bookmark" aria-label="The bookmark icon" %} al lado derecho de la misma.

Las notificaciones guardadas se mantienen por tiempo indefinido y puedes verlas si das clic en **Guardadas** en la barra lateral o con el query `is:saved`. Si guardas las notificaciones por más de 5 meses y luego las dejas de guardar, estas desaparecerán de tu bandeja de entrada en un día. | +| Done | Marca una notificación como completada y elimina la notificación de tu bandeja de entrada. Puedes ver todas las notificaciones completadas dando clic en **Hecho** dentro de la barra lateral o con el query `is:done`. Las notificaciones marcadas como **Hecho** se guardan por 5 meses. | +| Unsubscribe | Elimina automáticamente la notificación de tu bandeja de entrada y te da de baja de la conversación hasta que se @mencione a tu usuario o a algún equipo al que pertenezcas, o cuando se te solicite una revisión. | +| Read | Marca la notificación como leída. Para ver únicamente las notificaciones leídas en tu bandeja de entrada, utiliza el query `is:read`. Este query no incluirá a las notificaciones marcadas como **Hecho**. | +| Unread | Mara la notificación como no leída. Para ver únicamente las notificaciones sin leer en tu bandeja de entrada, utiliza el query `is:unread`. | + +Para ver los atajos de teclado disponibles, consulta la sección "[Atajos de Teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)". + +Antes de escoger una opción de clasificación, puedes prever los detalles de la notificación e investigar. Para obtener más información, consulta la sección "[Clasificar una sola notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)". + +### Clasificar varias notificaciones al mismo tiempo + +Para clasificar varias notificaciones de una sola vez, selecciona las notificaciones relevantes y utiliza el menú desplegable de {% octicon "kebab-horizontal" aria-label="The edit icon" %} para elegir una opción de clasificación. + +![Menú desplegable con opciones de clasificación y notificaciones seleccionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) + +### Filtros de notificación predeterminados + +Predeterminadamente, tu bandeja de entrada tiene filtros para cuando se te asigna, participas en un hilo, se te solicita revisar una solicitud de extracción, o cuando se @menciona a tu usuario directamente o a un equipo del cual eres miembro. + + ![Filtros personalizados predeterminados](/assets/images/help/notifications-v2/default-filters.png) + +### Personalizar tu bandeja de entrada con filtros personalizados + +Puedes agregar hasta 15 de tus filtros personalizados. + +{% data reusables.notifications.access_notifications %} +2. Para abrir la configuración de filtros, en la barra lateral izquierda, a lado de "Filtros", da clic en {% octicon "gear" aria-label="The Gear icon" %}. + + {% tip %} + + **Tip:** Puedes prever rápidamente los resultados del filtro en la bandeja de entrada si creas un query en ella y das clic en **Guardar**, lo cual abrirá la configuración del filtro personalizado. + + {% endtip %} + +3. Añade un nombre para tu filtro y query del mismo. Por ejemplo, para ver únicamente las notificaciones de un repositorio específico, puedes crear un filtro utilizando el query `repo:octocat/open-source-project-name reason:participating`. También puedes añadir emojis con un teclado que los tenga como nativos. Para ver una lista de queries de búsqueda compatibles, consulta la sección "[Queries compatibles para filtros personalizados](#supported-queries-for-custom-filters)". + + ![Ejemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png) + +4. Da clic en **Crear**. + +### Limitaciones de los filtros personalizados + +Los filtros personalizados no son compatibles actualmente con: + - Búsquedas de texto completo en tu bandeja de entrada, incluyendo búsquedas de los títulos de los informes de problemas o solicitudes de extracción. + - Distinción entre los queries de filtro `is:issue`, `is:pr`, y `is:pull-request`. Estos queries darán como resultado tanto informes de verificación como solicitudes de extracción. + - Crear más de 15 filtros personalizados. + - Cambiar los filtros predeterminados o su orden. + - Busca la [exclusión](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) utilizando `NOT` o `-QUALIFIER`. + +### Queries compatibles para filtros personalizados + +These are the types of filters that you can use: + - Filtrar por repositorio con `repo:` + - Filtrar por tipo de debate con `is:` + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} + +#### Supported `repo:` queries + +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. + +#### Queries de tipo `is:` compatibles + +Para filtrar las notificaciones para una actividad específica en {% data variables.product.product_name %}, puedes utililzar la consulta `is`. Por ejemplo, para ver únicamente las actualizaciones de las invitaciones al repositorio, utiliza `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, y para ver únicamente las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}, utiliza `is:repository-vulnerability-alert`.{% endif %} + +- `is:check-suite` +- `is:commit` +- `is:gist` +- `is:issue-or-pull-request` +- `is:release` +- `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} +- `is:repository-vulnerability-alert` +- `is:repository-advisory`{% endif %} +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} + +{% if currentVersion != "github-ae@latest" %} +Para obtener más información sobre la reducción de ruido de las notificaciones de +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}las alertas de seguridad{% endif %}, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". +{% endif %} + +También puedes utilizar la consulta `is:` para describir cómo se clasificó la notificación. + +- `is:saved` +- `is:done` +- `is:unread` +- `is:read` + +#### Queries de tipo `reason:` compatibles + +Para filtrar las notificaciones de acuerdo con la razón por la cual recibiste una actualización, puedes utilizar la consulta `reason:`. Por ejemplo, para ver las notificaciones cuando se solicita (a ti o a un equipo al que pertenezcas) revisar una solicitud de extracción, utiliza `reason:review-requested`. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)". + +| Consulta | Descripción | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `reason:assign` | Cuando hay una actualización en un informe de problemas o solicitud de extracción en los que estés asignado. | +| `reason:author` | Cuando abres una solicitud de extracción o informe de problemas y ésta ha tenido una actualización o comentario nuevo. | +| `reason:comment` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo. | +| `reason:participating` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo en el que te @mencionaron. | +| `reason:invitation` | Cuando se te invita a un equipo, organización o repositorio. | +| `reason:manual` | Cuando das clic en **Suscribirse** en un informe de problemas o solicitud de extracción al que no estuvieras suscrito. | +| `reason:mention` | Cuando te @mencionan directamente. | +| `reason:review-requested` | Ya sea tú o un equipo en el que estás solicitó revisar una solicitud de cambios.{% if currentVersion != "github-ae@latest" %} +| `reason:security-alert` | Cuando se emite una alerta de seguridad para un repositorio.{% endif %} +| `reason:state-change` | Cuando el estado de un informe de problemas o solicitud de extracción cambia. Por ejemplo, se cierra un informe de problemas o se fusiona una solicitud de extracción. | +| `reason:team-mention` | Cuando se @menciona a algún equipo al que pertenezcas. | +| `reason:ci-activity` | Cuando un repositorio tiene una actualización de IC, tal como un nuevo estado de ejecución en un flujo de trabajo. | + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md new file mode 100644 index 0000000000000..a472d79a81dc7 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md @@ -0,0 +1,10 @@ +--- +title: Administrar suscripciones de actividades en GitHub +intro: 'Para mantener notificaciones de flujo de trabajo sostenibles, entender y revisar frecuentemente tus suscripciones.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md new file mode 100644 index 0000000000000..0086b2abaee8c --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -0,0 +1,67 @@ +--- +title: Administrar tus suscripciones +intro: 'Hay varias maneras de darte de baja para ayudarte a administrar tus notificaciones de manera eficiente.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +Para ayudarte a entender tus suscripciones y decidir si quieres desuscribirte, consulta la sección "[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)". + +{% note %} + +**Nota:** En vez de desuscribirte, tienes la opción de ignorar un repositorio. Si ignoras un repositorio, no recibirás ninguna notificación. No recomendamos ignorar repositorios ya que no se te notificará si eres mencionado. {% if currentVersion == "free-pro-team@latest" %}Si te encuentras con algún tipo de abuso y quieres ignorar un repositorio, por favor, contacta a {% data variables.contact.contact_support %} para que podamos ayudarte. {% data reusables.policies.abuse %}{% endif %} + +{% endnote %} + +### Elegir cómo darte de baja + +Para dejar de observar (o para desuscribirte de) un repositorio rápidamente, ve a la página de "Repositorios en observación", donde puedes ver todos los repositorios que estás observando. Para obtener más información, consulta la sección "[Dejar de observar un repositorio](#unwatch-a-repository)". + +Para desuscribirte de varias notificaciones al mismo tiempo, puedes hacerlo utilizando tu bandeja de entrada o en la página de suscripciones. Ambas de estas opciones ofrecen más contexto acerca de tus suscripciones que la página de "Repositorios en observación". + +#### Beneficios de darte de baja desde tu bandeja de entrada + +Cuando te desuscribes de las notificaciones en tu bandeja de entrada, tienes varias otras opciones de clasificación y puedes filtrar tus notificaciones con filtros personalizados y tipos de discusión. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". + +#### Beneficios de darte de baja desde la página de suscripciones + +Cuando te desuscribes de las notificaciones en la página de suscripciones, puedes ver más notificaciones a las que estés suscrito y clasificarlas por "Suscrito más recientemente" o "Suscrito más antiguamente". + +La página de suscripciones te muestra todas las notificaciones a las que estás actualmente suscrito, incluyendo aquellas que hayas marcado como **Listas** en tu bandeja de entrada. + +Solo puedes filtrar tus suscripciones por repositorio y por la razón que estás recibiendo la notificación. + +### Darte de baja de las notificaciones en tu bandeja de entrada + +Cuando te desuscribes de las notificaciones en tu bandeja de entrada, desaparecerán automáticamente de ésta. + +{% data reusables.notifications.access_notifications %} +1. Desde la bandeja de notificaciones, selecciona aquellas de las cuales deseas darte de baja. +2. Utiliza el menú desplegable de **seleccionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para dar clic en **Desuscribirse**. ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) + +### Darse de baja de las notificaciones en la página de suscripciones + +{% data reusables.notifications.access_notifications %} +1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable de "Administrar notificaciones" para dar clic en **Suscripciones**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) + +2. Selecciona las notificaciones de las cuales quieres darte de baja. En la esquina superior derecha, da clic en **Darse de baja** ![Página de suscripciones](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png) + +### Dejar de seguir un repositorio + +Cuando dejas de observar un repositorio, de desuscribes de notificaciones futuras del mismo, a menos de que participes en una conversación o te @mencionen. + +{% data reusables.notifications.access_notifications %} +1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable de "Administrar notificaciones" para dar clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) +2. En la página de repositorios que sigues, después de que hayas evaluado aquellos que estás siguiendo, decide si quieres: +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + - dejar de seguir un repositorio + - únicamente seguir los lanzamientos de un repositorio + - ignorar todas las notificaciones de un repositorio +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + - dejar de seguir un repositorio + - ignorar todas las notificaciones de un repositorio + - personalizar los tipos de evento para los cuales recibes notificaciones (propuestas, solicitudes de cambio, lanzamientos o debates, si es que están habilitados) +{% endif %} diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md new file mode 100644 index 0000000000000..a9b9122fb3e23 --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md @@ -0,0 +1,12 @@ +--- +title: Configurar las notificaciones +intro: 'Para mejorar la relevancia de tus notificaciones y simplificar tu flujo de trabajo de clasificación, configura tus notificaciones para que empaten con tus prioridades.' +mapTopic: verdadero +redirect_from: + - /articles/getting-started-with-notifications +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md new file mode 100644 index 0000000000000..0d374976c2cbd --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md @@ -0,0 +1,41 @@ +--- +title: Clasificar solo una notificación +intro: 'Cuando revisas e investigas solo una notificación, tienes varias opciones de clasificación que se optimizan para la vista detallada de la misma.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +### Guardar solo una notificación + +Para guardar una notificación y revisarla más tarde, a la derecha de la misma, da clic en {% octicon "bookmark" aria-label="The bookmark icon" %}. Solo puedes guardar una notificación a la vez. + +Las notificaciones guardadas se mantienen indefinidamente y se pueden ver si das clic en **Guardado** en la barra lateral o con la consulta `is:saved`. Si guardas las notificaciones por más de 5 meses y luego las dejas de guardar, estas desaparecerán de tu bandeja de entrada en un día. + + ![Opción de clasificación en guardados](/assets/images/help/notifications-v2/save-triaging-option.png) + +### Investigar una notificación + +Cuando das clic en una notificación individual de tu bandeja de entrada, se te dirige a la conversación que la provocó. Desde la parte superior de la página, puedes: +- Marcar la notificación individual como completada +- Darte de baja de las notificaciones posteriores +- Marcar la notificación como leída +- Guardar la notificación para después +- Regresar a tu bandeja de notificaciones + +Para obtener más información acerca de tus opciones de clasificación, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)". + +### Personalizar cuándo recibir actualizaciones posteriores para un informe de problemas o solicitud de extracción + +Puedes elegir como quieres recibir las notificaciones posteriores para una solicitud de extracción o informe de problemas. + +1. En la columna derecha del informe de problemas o solicitud de extracción, a un costado de "Notificaciones", da clic en **Personalizar**". + + ![Personalizar opción debajo de "Notificaciones"](/assets/images/help/notifications-v2/customize-notifications-for-specific-thread.png) + +2. Selecciona **Personalizado** y elige cuando quieres recibir una actualización de notificación para este hilo. Por ejemplo, puedes elegir recibir una actualización cuando se fusiona, cierra o reabre la solicitud de extracción. Te suscribirás nuevamente si participas en el hilo, si se @menciona a tu nombre de usuario, o si se @menciona a algún equipo del cual formes parte. + + ![Opciones para personalizar las notificaciones](/assets/images/help/notifications-v2/custom-options-for-customizing-notification-thread-updates.png) + +3. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md new file mode 100644 index 0000000000000..6368ea9a2a41b --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md @@ -0,0 +1,13 @@ +--- +title: Ver y clasificar las notificaciones +intro: 'Para optimizar el flujo de trabajo de tus notificaciones, puedes personalizar como las visualizas y clasificas.' +mapTopic: verdadero +redirect_from: + - /articles/managing-notifications/ + - /articles/managing-your-notifications +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md new file mode 100644 index 0000000000000..cd62e418fa53d --- /dev/null +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -0,0 +1,101 @@ +--- +title: Visualizar tus suscripciones +intro: 'Para entender de dónde están llegando las notificaciones y la cantidad de las mismas, te recomendamos revisarlas frecuentemente, así como los repositorios que sigues de cerca.' +redirect_from: + - /articles/subscribing-to-conversations/ + - /articles/unsubscribing-from-conversations/ + - /articles/subscribing-to-and-unsubscribing-from-notifications + - /articles/listing-the-issues-and-pull-requests-youre-subscribed-to + - /articles/watching-repositories/ + - /articles/unwatching-repositories/ + - /articles/watching-and-unwatching-repositories + - /articles/watching-and-unwatching-releases-for-a-repository + - /articles/watching-and-unwatching-team-discussions + - /articles/listing-watched-repositories/ + - /articles/listing-the-repositories-you-re-watching + - /articles/listing-the-repositories-youre-watching +versions: + free-pro-team: '*' + enterprise-server: '>=2.21' + github-ae: '*' +--- + +Recibes notificaciones para tus suscripciones de la actividad reciente en {% data variables.product.product_name %}. Hay muchas razones por las cuales puedes estar suscrito a una conversación. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)". + +Te recomendamos auditar tus suscripciones y desuscribirte de las que no sean necesarias como parte de un flujo de trabajo de notificaciones saludable. Para obtener más información acerca de tus opciones para desuscribirte, consulta la sección "[Administrar suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". + +### Diagnosticar el por qué recibes tantas notificaciones + +Cuando tu bandeja de entrada tiene demasiadas notificaciones como para administrarlas, considera si estás suscrito a más de las que puedas manejar, o cómo puedes cambiar tu configuración de notificaciones para reducir aquellas que ya tienes y ver los tipos de notificaciones que estás recibiendo. Por ejemplo, puedes considerar inhabilitar la configuración para que observes automáticamente todos los repositorios y discusiones de equipo cada que te unas a un equipo o repositorio. + +![Seguimiento automático](/assets/images/help/notifications-v2/automatic-watching-example.png) + +Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)". + +Para ver un resumen de tus suscripciones a repositorios, consulta la sección "[Revisar los repositorios que estás observando](#reviewing-repositories-that-youre-watching)". +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Tip:** Puedes seleccionar los tipos de evento para los cuales quieres recibir notificaciones si utilizas la opción **Personalizar** de la lista desplegable **Observar/Dejar de observar** en tu [página de observados](https://github.com/watching) o en cualquier página de repositorio en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Configurar tus ajustes de observación para repositorios individuales](#configuring-your-watch-settings-for-an-individual-repository)" a continuación. + +{% endtip %} +{% endif %} + +Muchas personas se olvidan de los repositorios que han marcado para observar. Desde la página de "Repositorios observados" puedes dejar de observar los repositorios rápidamente. Para obtener más información sobre las formas de dejar de suscribirse, consulta la sección "[Dejar de observar las recomendaciones](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" en {% data variables.product.prodname_blog %} y "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". También puedes crear un flujo de trabajo de clasificación para que te ayude con las notificaciones que recibes. Para obtener orientación sobre los flujos de trabajo de clasificación, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". + +### Revisar todas tus suscripciones + +{% data reusables.notifications.access_notifications %} +1. En la barra lateral izquierda, debajo de la lista de repositorios de los cuales recibes notificaciones, utiliza el menú desplegable "Administrar notificaciones" para dar clic en **Suscripciones**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) + +2. Utiliza los filtros y organiza para reducir la lista de suscripciones y comenzar a darte de baja de las conversaciones de las cuales ya no quieres recibir notificaciones. + + ![Página de suscripciones](/assets/images/help/notifications-v2/all-subscriptions.png) + +{% tip %} + +**Tips:** +- Para revisar las suscripciones que pudiste haber olvidado, organiza por "suscripciones menos recientes" + +- Para revisar una lista de repositorios de los cuales aún puedes recibir notificaciones, despliega el menú "filtrar por repositorio" para ver el listado. + +{% endtip %} + +### Revisar los repositorios que estás siguiendo de cerca + +1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" y da clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) +2. Evalúa si los repositorios que estás siguiendo de cerca tienen actualizaciones que aún sean útiles y relevantes. Cuando sigues de cerca un repositorio, se te notificará de todas las conversaciones en el mismo. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% endif %} + + {% tip %} + + **Tip:** En vez de observar un repositorio, considera solo recibir notificaciones {% if currentVersion == "free-pro-team@latest" %}cuando existan actualizaciones a las propuestas, solicitudes de cambios, lanzamientos o debates (si se habilitaron en el repositorio), o cualquier combinación de estas opciones,{% else %}para los lanzamientos en un repositorio,{% endif %} o dejar de observar el repositorio completamente. + + Cuando dejas de seguir un repositorio, aún se te puede notificar cuando te @mencionan o cuando participas en un hilo. Cuando configuras el recibir notificaciones para ciertos tipos de evento, solo se te notificará cuando existan actualizaciones en éstos dentro del repositorio, si estás participando en un hilo, o si tú o un equipo al que perteneces tiene alguna @mención. + + {% endtip %} + +### Configurar los ajustes de observación para un repositorio individual + +Puedes elegir si quieres observar o dejar de observar un repositorio individual. También puedes elegir que solo se te notifique de {% if currentVersion == "free-pro-team@latest" %}algunos tipos de eventos, tales como propuestas, solicitudes de cambios, debates (si se habilitaron en el repositorio) y {% endif %}lanzamientos nuevos, o puedes ignorar completamente un repositorio específico. + +{% data reusables.repositories.navigate-to-repo %} +2. En la esquina superior derecha, da clic en el menú desplegable "Observar" para seleccionar una opción de observación. +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom.png) +{% data reusables.notifications-v2.custom-notifications-beta %} +La opción **Personalizar** te permite personalizar aún más las notificaciones para que solo se te notifique cuando suceden eventos específicos en el repositorio, adicionalmente a participar y tener @menciones. + + ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom2.png) + +Si seleccionas "propuestas", se te notificará sobre y suscribirá a las actualizaciones de cada propuesta (incluyendo aquellas que existieron antes de que seleccionaras esta opción) del repositorio. Si se te @menciona en una solicitud de cambios de este repositorio, también recibirás notificaciones por este evento y se te suscribirá a las actualizaciones de esa solicitud de cambios específica adicionalmente a las notificaciones que tendrás sobre las propuestas. + +{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md new file mode 100644 index 0000000000000..af03c580d956e --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md @@ -0,0 +1,48 @@ +--- +title: Acerca de la automatización para propuestas y solicitudes de extracción con parámetros de consulta +intro: Puedes usar los parámetros de consulta para compartir URLs con información personalizada. +redirect_from: + - /articles/about-automation-for-issues-and-pull-requests-with-query-parameters +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los parámetros de consulta son partes opcionales de una URL que puedes personalizar para compartir una vista de página web específica, como los resultados de filtro de búsqueda o una plantilla de propuestas en {% data variables.product.prodname_dotcom %}. Para crear tus propios parámetros de consulta, debes hacer coincidir el par de clave y valor. + +{% tip %} + +**Sugerencia:** También puedes crear plantillas de propuestas que se abran con etiquetas, asignatarios y un título de propuesta predeterminados. Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/articles/configuring-issue-templates-for-your-repository)" o "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". + +{% endtip %} + +Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para agregar una etiqueta a una propuesta para usar el parámetro de consulta `labels`. + +Si creas una URL no válida usando los parámetros de consulta o si no tienen los permisos adecuados, la URL devolverá una página de error 404. + +### Parámetros de consulta admitidos + +| Parámetro de consulta | Ejemplo | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `body` | `https://github.com/octo-org/octo-repo/compare/main...pull-request-test?quick_pull=1&body=Fixes+the+problem.` creates a pull request, comparing the branches `main` and `pull-request-test`, with the comment "Fixes the problem" in the pull request body. | +| `título` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` crea una propuesta en la etiqueta "error" y el título "Nuevo informe de error". | +| `etiquetas` | `https://github.com/octo-org/octo-repo/compare/main...pull-request-test?quick_pull=1&labels=bug` creates a pull request, comparing the branches `main` and `pull-request-test`, with the label "bug." | +| `template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` crea una propuesta con una plantilla en el cuerpo de la propuesta. | +| `milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` crea una propuesta con el hito "probando hitos". | +| `asignatarios` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` crea una propuesta y la asigna a @octocat. | +| `proyectos` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` crea una propuesta con el título "Solución del problema" y la agrega al tablero de proyecto 1 de la organización. | + +### Completar propuestas y solicitudes de extracción con plantillas personalizadas + +{% data reusables.repositories.legacy-issue-template-tip %} + +Puedes usar el parámetro de consulta `template` para especificar una plantilla para completar de forma automática la propuesta o el cuerpo de la solicitud de extracción. El parámetro de consulta `template` funciona con las plantillas almacenadas en el subdirectorio `ISSUE_TEMPLATE` o `PULL_REQUEST_TEMPLATE` dentro de la raíz, del directorio `docs/` o `.github/` en un repositorio. + +Si un repositorio contiene solo la solicitud de extracción o la plantilla de propuesta predeterminada, cualquier propuesta o solicitud de extracción nueva tendrá la plantilla predeterminada en el cuerpo. + +Para obtener más información, consulta "[Crear una plantilla de solicitud de extracción para tu repositorio](/articles/creating-a-pull-request-template-for-your-repository)" o "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". + +### Further reading + +- "[Automatización para formularios de lanzamiento con parámetros de consulta](/articles/automation-for-release-forms-with-query-parameters)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md new file mode 100644 index 0000000000000..a558a2c49612f --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md @@ -0,0 +1,40 @@ +--- +title: Acerca de automatización de tableros de proyecto +intro: Puedes configurar flujos de trabajo automáticos para mantener el estado de las tarjetas del tablero de proyecto en sincronización con las propuestas y las solicitudes de extracción asociadas. +redirect_from: + - /articles/about-automation-for-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.project-management.automate-project-board-permissions %} Para obtener más información, consulta "[Permisos del tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". + +Puedes automatizar acciones en función de los eventos desencadenantes para las columnas del tablero de proyecto. Esto elimina algunas tareas manuales en la administración de un tablero de proyecto. Por ejemplo, puedes configurar una columna "Tareas pendientes", donde cualquier propuesta o solicitud de extracción que agregues a un tablero de proyecto se mueva automáticamente a la columna configurada. Para obtener más información, consulta "[Configurar automatización para tableros de proyecto](/articles/configuring-automation-for-project-boards)". + +{% data reusables.project-management.use-automated-template %} + +{% data reusables.project-management.copy-project-boards %} + +La automatización del tablero de proyecto también puede ayudar a los equipos a desarrollar un entendimiento común del propósito de un tablero de proyecto y del proceso de desarrollo del equipo creando un flujo de trabajo estándar para ciertas acciones. + +{% data reusables.project-management.resync-automation %} + +### Opciones de automatización + +| Columna preestablecida | Opciones de configuración | +| ---------------------- | ------------------------- | +| Tarea pendientes |
  • Mover todas las propuestas agregadas recientemente aquí.
  • Mover todas las solicitudes de extracción agregadas recientemente aquí.
  • Mover todas las propuestas que se volvieron a abrir aquí.
  • Mover todas las solicitudes de extracción que se volvieron a abrir aquí.
| +| En curso |
  • Mover todas las solicitudes de extracción que se volvieron a abrir recientemente aquí.
  • Mover todas las propuestas que se volvieron a abrir aquí.
  • Mover todas las solicitudes de extracción que se volvieron a abrir aquí.
  • Mover todas las solicitudes de extracción que cumplen con la cantidad mínima de revisiones requeridas de la rama base aquí.
  • Mover todas las solicitudes de extracción que ya no cumplen con la cantidad mínima de revisiones requeridas de la rama base aquí.
| +| Done |
  • Mover todas las propuestas cerradas aquí.
  • Mover todas las solicitudes de extracción fusionadas aquí.
  • Mover todas las solicitudes de extracción cerradas, sin fusionar aquí.
| + +### Seguimiento de progreso del proyecto + +Puedes rastrear el progreso en tu tablero de proyecto. Las tarjetas en las columnas "por hacer", "en curso", o "hecho" cuentan sobre el progreso general del proyecto. {% data reusables.project-management.project-progress-locations %} + +Para obtener más información, consulta la sección "[Rastrear el progreso en tu tablero de proyecto](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)". + +### Further reading +- "[Configurar la automatización para los tableros de proyecto](/articles/configuring-automation-for-project-boards)"{% if currentVersion == "free-pro-team@latest" %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md new file mode 100644 index 0000000000000..f87f563158c36 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md @@ -0,0 +1,24 @@ +--- +title: Acerca de duplicar propuestas y solicitudes de extracción +intro: Marca una propuesta o solicitud de extracción como un duplicado para hacer un seguimiento de propuestas o solicitudes de extracción similares en conjunto y eliminar una responsabilidad innecesaria, tanto para los mantenedores como para los colaboradores. +redirect_from: + - /articles/about-duplicate-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para que aparezca un evento cronológico "marcado como duplicado", el usuario que crea el comentario de referencia duplicado debe tener acceso de escritura al repositorio donde crea el comentario. + +### Marcar duplicados + +Para marcar una propuesta o solicitud de extracción como un duplicado, escribe "Duplicado de" seguido del número de propuesta o solicitud de extracción que se duplica en el cuerpo de un comentario nuevo. También puedes usar las respuestas guardadas "Duplicar propuesta" o "Duplicar solicitud de extracción" provistas por GitHub para marcar una propuesta o solicitud de extracción como un duplicado. Para obtener más información, consulta "[Acerca de las respuestas guardadas](/articles/about-saved-replies)". + +![Duplicar la sintaxis de la propuesta](/assets/images/help/issues/duplicate-issue-syntax.png) + +### Desmarcar duplicados + +Puedes desmarcar propuestas o solicitudes de extracción duplicadas haciendo clic en la cronología **Deshacer**. Esto agregará un evento cronológico nuevo, indicando que la propuesta o la solicitud de extracción fue desmarcada. + +![Botón Desmarcar propuesta duplicada](/assets/images/help/issues/unmark-duplicate-issue-button.png) diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-issues.md b/translations/es-ES/content/github/managing-your-work-on-github/about-issues.md new file mode 100644 index 0000000000000..117d99e7955fa --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-issues.md @@ -0,0 +1,40 @@ +--- +title: Acerca de las propuestas +intro: 'Usa las propuestas para rastrear ideas, mejoras, tareas o errores para tu trabajo en {% data variables.product.product_name %}.' +redirect_from: + - /articles/creating-issues/ + - /articles/about-issues/ +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las propuestas + +Puedes recopilar opiniones del usuario, informar errores de software y organizar tareas que quieras realizar con las propuestas en un repositorio. Las propuestas pueden actuar como más que un simple lugar para informar errores de software. + +{% if currentVersion == "free-pro-team@latest" %} +Otras conversaciones son más adecuadas para los debates. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} + +{% data reusables.pull_requests.close-issues-using-keywords %} + +Para estar actualizado sobre los comentarios más recientes en una propuesta, puedes ver una propuesta para recibir notificaciones acerca de los últimos comentarios. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". + +Para encontrar rápidamente los enlaces a los informes de problemas recientemente actualizados a los cuales te has suscrito, visita tu tablero. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +### Trabajar con propuesta + +Con las propuestas, puedes hacer lo siguiente: +- Rastrear y priorizar tu trabajo usando tableros de proyecto. Para obtener más información, consulta "[Cómo usar tableros de proyecto](/articles/about-project-boards)". +- Crear nuevos informes de problemas para rastrear la retroalimentación fuera de ámbito desde un comentario en una revisión de informe de problemas o de solicitud de extracción. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". +- Crear plantillas de propuestas para ayudar a los colaboradores a abrir propuestas significativas. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". +- Transferir propuestas abiertas a otros repositorios. Para obtener más información, consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)". +- Anclar propuestas importantes para hacer que sea más fácil encontrarlas, evitando las propuestas duplicadas y reduciendo el ruido. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/articles/pinning-an-issue-to-your-repository)". +- Rastrear propuestas duplicadas usando las respuestas guardadas. Para obtener más información, consulta la sección "[Acerca de las respuestas guardadas](/articles/about-saved-replies)".{% if currentVersion == "free-pro-team@latest" %} +- Informar comentarios que violan las [Pautas de la comunidad](/articles/github-community-guidelines) de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Informar abuso o spam](/articles/reporting-abuse-or-spam)".{% endif %} + +Las propuestas también se pueden [asignar a otros usuarios](/articles/assigning-issues-and-pull-requests-to-other-github-users), [marcar con etiquetas](/articles/applying-labels-to-issues-and-pull-requests) para una búsqueda más rápida y [agrupar con hitos](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md b/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md new file mode 100644 index 0000000000000..1ed5c7d26a775 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md @@ -0,0 +1,43 @@ +--- +title: Acerca de los hitos +intro: Puedes usar hitos para hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. +redirect_from: + - /articles/about-milestones +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando [creas un hito](/articles/creating-and-editing-milestones-for-issues-and-pull-requests), puedes [asociarlo con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests). + +Para administrar mejor tu proyecto, puedes [ver detalles acerca de tu hito](/articles/viewing-your-milestone-s-progress). Desde la página del hito, puedes ver lo siguiente: + +- Una descripción del hito proporcionada por el usuario, que puede incluir información como la descripción general del proyecto, los equipos relevantes y las fechas de vencimiento previstas. +- La fecha de vencimiento del hito. +- El porcentaje de finalización del hito. +- La cantidad de propuestas y solicitudes de extracción abiertas y cerradas asociadas con el hito. +- Una lista de las propuestas y las solicitudes de extracción abiertas y cerradas asociadas con el hito. + +Además, puedes editar el hito desde la página del hito y crear nuevas propuesta que estén, de forma predeterminada, asociadas con el hito. + +![Página del hito](/assets/images/help/issues/milestone-info-page.png) + +### Priorizar propuestas y solicitudes de extracción en hitos + +Puedes priorizar propuestas y solicitudes de extracción abiertas en un hito haciendo clic a la izquierda de la casilla de verificación de una propuesta o solicitud de extracción, arrastrándola a una nueva ubicación y colocándola ahí. + +{% note %} + +**Nota:** Si hay más de 500 propuestas abiertas en un hito, no podrás priorizar propuestas. + +{% endnote %} + +![Hito reordenado](/assets/images/help/issues/milestone-reordered.gif) + +### Further reading + +- "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" +- "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" +- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" +- "[Ver el progreso de tus hitos](/articles/viewing-your-milestone-s-progress)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md new file mode 100644 index 0000000000000..451e4292f23fc --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md @@ -0,0 +1,67 @@ +--- +title: Acerca de los tableros de proyecto +intro: 'Los tableros de proyecto en {% data variables.product.product_name %} te ayudan a organizar y priorizar tu trabajo. Puedes crear tableros de proyecto para un trabajo con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos. Con los tableros de proyecto, tienes la flexibilidad de crear flujos de trabajo personalizados que se adapten a tus necesidades.' +redirect_from: + - /articles/about-projects/ + - /articles/about-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los tableros de proyecto están compuestos por propuestas, solicitudes de extracción y notas que se categorizan como tarjetas en columnas a tu elección. Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas dentro de una columna, mover tarjetas de columna a columna y cambiar el orden de las columnas. + +Las tarjetas del tablero de proyecto contienen metadatos relevantes para las propuestas y las solicitudes de extracción, como etiquetas, asignatarios, el estado y quién la abrió. {% data reusables.project-management.edit-in-project %} + +También puedes crear notas dentro de las columnas para servir como recordatorios de tarea, referencias a propuestas y solicitudes de extracción desde cualquier repositorio en {% data variables.product.product_name %}, o agregar información relacionada con tu tablero de proyecto. Puedes crear una tarjeta de referencia para otro tablero de proyecto agregando un enlace a una nota. Si la nota no es suficiente para tus necesidades, puedes convertirla en una propuesta. Para obtener más información sobre cómo convertir las notas del tablero de proyecto en propuestas, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". + +Tipos de tableros de proyecto: + +- Los **tableros de proyecto propiedad del usuario** pueden contener propuestas y solicitudes de extracción de cualquier repositorio personal. +- Los **tableros de proyecto para toda la organización** pueden contener propuestas y solicitudes de extracción de cualquier repositorio que pertenezca a una organización. {% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta "[Enlazar un repositorio a un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". +- Los **tableros de proyecto para un repositorio** están limitados a las propuestas y las solicitudes de extracción dentro de un único repositorio. También pueden incluir notas que hacen referencia a las propuestas y las solicitudes de extracción en otros repositorios. + +### Crear y ver tableros de proyecto + +Para crear un tablero de proyecto para tu organización, debes ser un miembro de la organización. Los propietarios de la organización y las personas con permisos de administrador para el tablero de proyecto pueden personalizar el acceso al tablero de proyecto. + +Si un tablero de proyecto propiedad de la organización incluye propuestas o solicitudes de extracción de un repositorio del que no tienes permiso para ver, la tarjeta será censurada. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". + +La vista actividad muestra el historial reciente del tablero de proyecto, como las tarjetas que alguien creó o movió entre las columnas. Para acceder a la vista actividad, haz clic en **Menú** y desplázate hacia abajo. + +Para encontrar tarjetas específicas en un tablero de proyecto o para ver un subconjunto de tarjetas, puedes filtrar las tarjetas del tablero de proyecto. Para obtener más información, consulta "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)". + +Para simplificar tu flujo de trabajo y para mantener las tareas completadas al margen de tu tablero de proyecto, puedes archivar tarjetas. Para obtener más información, consulta "[Archivar tarjetas en un tablero de proyecto](/articles/archiving-cards-on-a-project-board)". + +Si has completado todas las tareas de tu tablero de proyecto o ya no necesitas usar tu tablero de proyecto, puedes cerrar el tablero de proyecto. Para obtener más información, consulta "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". + +También puedes [desactivar tableros de proyecto en un repositorio](/articles/disabling-project-boards-in-a-repository) o [desactivar tableros de proyecto en tu organización](/articles/disabling-project-boards-in-your-organization), si prefieres hacer un seguimiento de tu trabajo de manera diferente. + +{% data reusables.project-management.project-board-import-with-api %} + +### Plantillas para tableros de proyecto + +Puedes usar plantillas para configurar de forma rápida un nuevo tablero de proyecto. Cuando usas una plantilla para crear un tablero de proyecto, tu nuevo tablero incluirá columnas, así como tarjetas con sugerencias para usar los tableros de proyecto. También puedes elegir una plantilla con la automatización ya configurada. + +| Plantilla | Descripción | +| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Kanban básico | Hace un seguimiento de tus tareas con las columnas Tareas pendientes, En progreso y Hecho | +| Kanban automatizado | Las tarjetas se mueven automáticamente entre las columnas Tareas pendientes, En progreso y Hecho | +| Kanba automatizado con revisión | Las tarjetas se mueven automáticamente entre las columnas Tareas pendientes, En progreso y Hecho, con disparos adicionales para el estado de la revisión de solicitud de extracción | +| Evaluación de error | Evalúa y prioriza errores con las columnas Tareas pendientes, Prioridad alta, Prioridad baja y Cerrado | + +Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". + +![Tablero de proyecto con plantilla de kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png) + +{% data reusables.project-management.copy-project-boards %} + +### Further reading + +- "[Crear un tablero de proyecto](/articles/creating-a-project-board)" +- "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" +- "[Atajos del teclado](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md b/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md new file mode 100644 index 0000000000000..dd5434fba7340 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md @@ -0,0 +1,32 @@ +--- +title: Acerca de las listas de tareas +intro: Puedes usar listas de tareas para crear una lista de elementos con casillas de verificación dentro de los comentarios de una solicitud de extracción y de una propuesta o archivos Markdown en tu repositorio. +redirect_from: + - /articles/about-task-lists +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las listas de tareas están representadas con casillas de verificación interactivas en los comentarios. Puedes seleccionar o quitar la marca de selección de las casillas de verificación para marcarlas como completas o incompletas. + +Las listas de tareas están representadas como casillas de verificación de solo lectura en los archivos Markdown. Las personas con permisos de escritura en el repositorio pueden editar el archivo para seleccionar o quitar la marca de selección de las casillas de verificación. + +Puedes ver la información del resúmen de la lista de tareas en las listas de una propuesta y una solicitud de extracción, cuando la lista de tareas está en el comentario inicial. + +![Resúmen de lista de tareas](/assets/images/help/issues/task-list-summary.png) + +### Crear listas de tareas + +{% data reusables.repositories.task-list-markdown %} + +### Volver a ordenar tareas + +Puedes volver a ordenar las listas de tareas dentro de un comentario único haciendo clic a la izquierda de la casilla de verificación de una tarea, arrastrándola a una nueva ubicación y colocándola ahí. Si tienes varias listas dentro de un comentario, puedes volver a ordenar tareas en el comentario único. Puedes agregar o volver a ordenar tareas en diferentes comentarios. + +![Volver a ordenar lista de tareas](/assets/images/help/writing/task-list-reordered.gif) + +### Further reading + +* [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md new file mode 100644 index 0000000000000..35372c797da82 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md @@ -0,0 +1,65 @@ +--- +title: Agregar propuestas y solicitudes de extracción a un tablero de proyecto +intro: Puedes agregar propuestas y solicitudes de extracción a un tablero de proyecto en la forma de tarjetas y jerarquizarlas en columnas. +redirect_from: + - /articles/adding-issues-and-pull-requests-to-a-project/ + - /articles/adding-issues-and-pull-requests-to-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes agregar propuestas o tarjetas de solicitudes de extracción a un tablero de proyecto al: +- Arrastrar tarjetas desde la sección **Triage** (Jerarquizar) en la barra lateral. +- Escribir la propuesta o URL de solicitud de extracción en una tarjeta. +- Buscar las propuestas o solicitudes de extracción en la barra lateral de búsqueda del tablero de proyecto. + +Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una columna ha alcanzado un número máximo de tarjetas, ninguna tarjeta puede moverse a esa columna. + +![El cursor mueve la tarjeta de propuestas desde la barra lateral de clasificación hasta la columna del tablero](/assets/images/help/projects/add-card-from-sidebar.gif) + +{% note %} + +**Nota:** También puedes agregar notas a tu tablero de proyecto para servir como recordatorios de tarea, referencias a propuestas y solicitudes de extracción desde un repositorio en {% data variables.product.product_name %}, o agregar información relacionada con tu tablero de proyecto. Para obtener más información, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". + +{% endnote %} + +{% data reusables.project-management.edit-in-project %} + +{% data reusables.project-management.link-repos-to-project-board %} Cuando buscas propuestas y solicitudes de extracción para agregar a tu tablero de proyecto, la búsqueda automáticamente llega a tus repositorios relacionados. Puedes eliminar estos calificadores para buscar dentro de todos los repositorios de la organización. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". + +### Agregar propuestas y solicitudes de extracción a un tablero de proyecto + +1. Navegue hasta el tablero de proyecto donde deseas agregar propuestas y solicitudes de extracción. +2. En tu tablero de proyecto, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Add cards** (Agregar tarjetas). ![Agregar botón de tarjetas](/assets/images/help/projects/add-cards-button.png) +3. Buscar propuestas y solicitudes de extracción para agregar a tu tablero de proyecto mediante calificadores de búsqueda. Para más información sobre la búsqueda de calificadores que puedes usar, consulta "[Buscar propuestas](/articles/searching-issues)". ![Buscar propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) + + {% tip %} + + **Tips:** + - También puedes agregar una propuesta o solicitud de extracción al escribir la URL en una tarjeta. + - Si estás trabajando en una característica específica, puedes aplicar una etiqueta a cada propuesta relacionada o solicitud de extracción para esa característica, y luego agregar tarjetas fácilmente a tu tablero de proyecto al buscar por el nombre de la etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)". + + {% endtip %} +4. En la lista filtrada de propuestas y solicitudes de extracción, arrastra la tarjeta que te gustaría agregar a tu tablero de proyecto y colócala en la columna correcta. Como alternativa, puedes mover las tarjetas usando los atajos del teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} + + {% tip %} + + **Sugerencia:** Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas y moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} + + {% endtip %} + +### Agregar propuestas y solicitudes de extracción a un tablero de proyecto de la barra lateral + +1. En el lateral derecho de una propuesta o solicitud de extracción, haz clic en **Projects{% octicon "gear" aria-label="The Gear icon" %} (Proyectos**. ![Botón del tablero de proyecto en la barra lateral](/assets/images/help/projects/sidebar-project.png) +2. Da clic en la pestaña **Reciente**,**Repositorio**,**Usuario**, u **Organización** del tablero de proyecto que te gustaría agregar. ![Pestañas Recent (Reciente), Repository (Repositorio) y Organization (Organización)](/assets/images/help/projects/sidebar-project-tabs.png) +3. Escribe el nombre del proyecto en el campo **Filter projects** (Filtrar proyectos). ![Cuadro de búsqueda del tablero de proyecto](/assets/images/help/projects/sidebar-search-project.png) +4. Selecciona uno o más tableros de proyecto en donde quieras agregar la propuesta o solicitud de cambios. ![Tablero de proyecto seleccionado](/assets/images/help/projects/sidebar-select-project.png) +5. Haz clic en {% octicon "triangle-down" aria-label="The down triangle icon" %}, luego haz clic en la columna en la que quieras colocar tu propuesta o solicitud de extracción. La tarjeta se moverá al final de la columna del tablero de proyecto que selecciones. ![Menú Move card to column (Mover tarjeta a la columna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Editar un tablero de proyecto](/articles/editing-a-project-board)" +- "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md new file mode 100644 index 0000000000000..0fe2fed0e8061 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md @@ -0,0 +1,70 @@ +--- +title: Agregar notas a tu tablero de proyecto +intro: Puedes agregar notas a tu tablero de proyecto para que funcionen como recordatorios de tareas o para agregar información relacionada con el tablero de proyecto. +redirect_from: + - /articles/adding-notes-to-a-project/ + - /articles/adding-notes-to-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Tips:** +- Puedes dar formato a tu nota usando la sintaxis de Markdown. Por ejemplo, puedes usar encabezados, enlaces, listas de tareas o emojis. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". +- Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas y moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} +- Tu tablero de proyecto debe tener al menos una columna antes de que puedas agregar notas. Para obtener más información, consulta "[Crear un tablero de proyecto](/articles/creating-a-project-board)". + +{% endtip %} + +Cuando agregas una URL para una propuesta, solicitud de extracción u otro tablero de proyecto para una nota, verás la vista previa en una tarjeta de resumen debajo de tu texto. + +![Tarjetas de tableros de proyecto mostrando una vista previa de una propuesta y otro tablero de proyecto](/assets/images/help/projects/note-with-summary-card.png) + +### Agregar notas a tu tablero de proyecto + +1. Desplázate hasta el tablero de proyecto donde quieres agregar notas. +2. En la columna en la que deseas agregar una nota, haz clic en {% octicon "plus" aria-label="The plus icon" %}. ![Icono de adición en el encabezado de la columna](/assets/images/help/projects/add-note-button.png) +3. Escribe tu nota, luego haz clic en **Add** (Agregar). ![Campo para escribir una nota y botón Add card (Agregar tarjeta)](/assets/images/help/projects/create-and-add-note-button.png) + + {% tip %} + + **Sugerencia:** Puedes hacer referencia a una propuesta o solicitud de extracción en tu nota al escribir su URL en la tarjeta. + + {% endtip %} + +### Convertir una nota en una propuesta + +Si has creado una nota y consideras que no es suficiente para tus necesidades, puedes convertirla en una propuesta. + +Cuando conviertes una nota en una propuesta, la propuesta se crea automáticamente usando el contenido de la nota. La primera línea de la nota será el título de la propuesta y cualquier información adicional de la nota se agregará a la descripción de la propuesta. + +{% tip %} + +**Sugerencia:** Puedes agregar el contenido en el cuerpo de tu nota para @mencionar a alguien, vincular otra propuesta o solicitud de extracción, y agregar un emoji. Estas características de formato Markdown de {% data variables.product.prodname_dotcom %} no son compatibles con las notas del tablero de proyecto, pero una vez que tu nota se convierte en una propuesta, aparecerán correctamente. Para obtener más información sobre cómo usar estas características, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". + +{% endtip %} + +1. Desplázate hasta la nota que deseas convertir en propuesta. +{% data reusables.project-management.project-note-more-options %} +3. Haz clic en **Convert to issue** (Convertir en propuesta). ![Botón para convertir en propuesta](/assets/images/help/projects/convert-to-issue.png) +4. Si la tarjeta está en un tablero de proyecto en toda la organización, en el menú desplegable, elige el repositorio en el que deseas agregar la propuesta. ![Menú desplegable enumerando los repositorios donde puedes crear la propuesta](/assets/images/help/projects/convert-note-choose-repository.png) +5. Opcionalmente, edita el título de la propuesta completada previamente, y escribe el cuerpo de la propuesta. ![Campos para título y cuerpo de la propuesta](/assets/images/help/projects/convert-note-issue-title-body.png) +6. Haz clic en **Convert to issue** (Convertir en propuesta). +7. La nota se convertirá automáticamente en una propuesta. En el tablero de proyecto, la nueva tarjeta de propuesta estará en la misma ubicación que la nota anterior. + +### Editar o eliminar una nota + +1. Desplázate hasta la nota que deseas editar o eliminar. +{% data reusables.project-management.project-note-more-options %} +3. Para editar los contenidos de la nota, haz clic en **Edit note** (Editar nota). ![Botón para editar notas](/assets/images/help/projects/edit-note.png) +4. Para eliminar los contenidos de las notas, haz clic en **Delete note** (Eliminar nota). ![Botón para eliminar notas](/assets/images/help/projects/delete-note.png) + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Crear un tablero de proyecto](/articles/creating-a-project-board)" +- "[Editar un tablero de proyecto](/articles/editing-a-project-board)" +- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md new file mode 100644 index 0000000000000..51284f7fda362 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md @@ -0,0 +1,23 @@ +--- +title: Archivar tarjetas en un tablero de proyecto +intro: Puedes archivar tarjetas en un tablero de proyecto para organizar tu flujo de trabajo sin perder el contexto histórico de un proyecto. +redirect_from: + - /articles/archiving-cards-on-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La automatización en tu tablero de proyecto no se aplica a las tarjetas del tablero de proyecto archivado. Por ejemplo, si cierras una propuesta en un archivo del tablero de proyecto, la tarjeta archivada no se mueve automáticamente a la columna "Done" (Listo). Cuando restauras una tarjeta del archivo del tablero de proyecto, la tarjeta volverá a la columna donde fue archivada. + +### Archivar tarjetas en un tablero de proyecto + +1. En un tablero de proyecto, busca la tarjeta que quieres archivar y luego haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Lista de opciones para editar una tarjeta del tablero de proyecto](/assets/images/help/projects/select-archiving-options-project-board-card.png) +2. Da clic en **Archivo**. ![Opción para seleccionar archivos desde el menú.](/assets/images/help/projects/archive-project-board-card.png) + +### Restaurar tarjetas en un tablero de proyecto desde la barra lateral + +{% data reusables.project-management.click-menu %} +2. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **View archive** (Ver archivo). ![Seleccionar la opción para ver el archivo desde el menú](/assets/images/help/projects/select-view-archive-option-project-board-card.png) +3. Encima de la tarjeta del tablero de proyecto que deseas desarchivar, haz clic en **Restore** (Restaurar). ![Seleccionar la restauración de la tarjeta del tablero de proyecto](/assets/images/help/projects/restore-card.png) diff --git a/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md new file mode 100644 index 0000000000000..e39271fab7bb6 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md @@ -0,0 +1,24 @@ +--- +title: Asignar propuestas y solicitudes de extracción a otros usuarios de GitHub +intro: Los asignatarios aclaran quién está trabajando en propuestas y solicitudes de extracción específicas. +redirect_from: + - /articles/assigning-issues-and-pull-requests-to-other-github-users +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cualquier persona con permisos de escritura en un repositorio puede asignar propuestas y solicitudes de extracción. + +Puedes asignar hasta 10 personas a cada propuesta o solicitud de cambios, incluyéndote a ti mismo, a cualquiera que haya comentado en la propuesta o solicitud de cambios, a cualquiera con permisos de escritura en el repositorio y a los miembros de la organización con permisos de lectura en el repositorio. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. Selecciona la casilla de verificación junto a los elementos que deseas asignar a alguien. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) +4. En el margen superior derecho, haz clic en **Assignee** (Asignatario). +5. Para asignar los elementos a un usuario, comienza escribiendo su nombre de usuario, luego haz clic en su nombre cuando aparezca. Puedes seleccionar y asignar hasta 10 asignatarios a una propuesta o solicitud de extracción. ![Desplegable de la asignación de propuestas](/assets/images/help/issues/issues_assigning_dropdown.png) + +### Further reading + +* "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md new file mode 100644 index 0000000000000..e2504b19d2379 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md @@ -0,0 +1,27 @@ +--- +title: Asociar hitos con propuestas y solicitudes de extracción +intro: Puedes asociar propuestas y solicitudes de extracción similares con un hito para realizar un mejor seguimiento de su progreso. +redirect_from: + - /articles/associating-milestones-with-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. Selecciona la casilla de verificación junto a los elementos que deseas asociar a un hito. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) +4. En el margen superior derecho, haz clic en **Milestone** (Hito), luego comienza a escribir el nombre de un [hito existente](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). Haz clic en el nombre del hito para asociarlo con el elemento. ![Desplegable de la asignación de los hitos de propuestas](/assets/images/help/issues/issues_assigning_milestone_dropdown.png) + +{% tip %} + +A medida que trabajas en las propuestas y las solicitudes de extracción, puedes [realizar el seguimiento del progreso de tu hito](/articles/viewing-your-milestone-s-progress). + +{% endtip %} + +### Further reading + +- "[Acerca de los hitos](/articles/about-milestones)" +- "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" +- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md new file mode 100644 index 0000000000000..5699f8e509269 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -0,0 +1,26 @@ +--- +title: Cambiar la visibilidad del tablero de proyecto +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' +redirect_from: + - /articles/changing-project-board-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.project-management.project-board-visibility %} + +{% tip %} + +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. Puedes brindar a los miembros de la organización permisos de escritura o administración específicos al brindar acceso al tablero de proyecto a los equipos en los que están y al agregarlos en un tablero de proyecto como colaboradores. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". + +{% endtip %} + +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.choose-visibility %} +1. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md new file mode 100644 index 0000000000000..b84512128efb3 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md @@ -0,0 +1,27 @@ +--- +title: Cerrar un tablero de proyecto +intro: 'Si has completado todas las tareas de tu tablero de proyecto o ya no necesitas usar un tablero de proyecto, puedes cerrarlo.' +redirect_from: + - /articles/closing-a-project/ + - /articles/closing-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando cierras un tablero de proyecto, todas las automatizaciones del flujo de trabajo configuradas se pausarán por defecto. + +Si vuelves a abrir un tablero de proyecto, tienes la opción de *sincronizar* la automatización, lo que actualiza la posición de las tarjetas en el tablero de acuerdo con los parámetros de automatización configurados para el tablero. Para obtener más información, consulta "[Volver a abrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board)" o "[Acerca de la automatización de los tableros de proyectos](/articles/about-automation-for-project-boards)". + +1. Navega hasta la lista de tableros de proyectos en tu repositorio u organización o los que le pertenezcan a tu cuenta de usuario. +2. En la lista de proyectos, junto al tablero de proyectos que deseas cerrar, haz clic en {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Icono de comillas angulares a la derecha del nombre del tablero de proyecto](/assets/images/help/projects/project-list-action-chevron.png) +3. Da clic en **Cerrar**. ![Menú desplegable para cerrar elementos en el tablero de proyecto](/assets/images/help/projects/close-project.png) + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" +- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" +- "[Inhabilitar tableros de proyectos en tu organización](/articles/disabling-project-boards-in-a-repository)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md new file mode 100644 index 0000000000000..9489ebccca723 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md @@ -0,0 +1,32 @@ +--- +title: Configurar la automatización para tableros de proyecto +intro: Puedes establecer flujos de trabajo automáticos para mover propuestas y solicitudes de extracción a una columna de tablero de proyecto cuando se produce un evento especificado. +redirect_from: + - /articles/configuring-automation-for-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.project-management.automate-project-board-permissions %} Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". + +{% data reusables.project-management.use-automated-template %} + +{% data reusables.project-management.resync-automation %} + +{% tip %} + +**Sugerencia** Para editar columnas que ya tienen configurada la automatización, haz clic en **Manage** (Administrar) en la parte inferior de la columna. + +{% endtip %} + +1. Dirígete al tablero de proyecto que deseas automatizar. +2. En la columna que deseas automatizar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Icono Editar](/assets/images/help/projects/edit-column-button.png) +3. Haz clic en **Manage automation** (Administrar automatización). ![Botón Manage automation (Administrar automatización)](/assets/images/help/projects/manage-automation-button.png) +4. En el menú desplegable Preset (Preestablecer), selecciona el preestablecimiento de la automatización. ![Selecciona preestablecer la automatización desde el menú](/assets/images/help/projects/select-automation.png) +5. Selecciona las automatizaciones del flujo de trabajo que deseas configurar para la columna. ![Lista de opciones para automatizar la columna](/assets/images/help/projects/select-automation-options-existing-column.png) +6. Haz clic en **Update automation** (Actualizar automatización). + +### Further reading +- "[Acerca de la automatización de los tableros de proyecto](/articles/about-automation-for-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/copying-a-project-board.md new file mode 100644 index 0000000000000..1498b499d8d56 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -0,0 +1,26 @@ +--- +title: Copiar un tablero de proyecto +intro: Puedes copiar un tablero de proyecto para crear rápidamente un proyecto nuevo. Si copias los tableros de proyecto altamente personalizados o que se usan con frecuencia te ayudará a estandarizar tu flujo de trabajo. +redirect_from: + - /articles/copying-a-project-board +versions: + free-pro-team: '*' +--- + +Copiar un tablero de proyecto te permite volver a usar el título, la descripción y la configuración automática de un tablero de proyecto. Puedes copiar los tableros de proyecto para eliminar el proceso manual de creación de nuevos tableros de proyecto para flujos de trabajo similares. + +Debes tener acceso de lectura de un tablero de proyecto para copiarlo en un repositorio u organización donde tengas acceso de lectura. + +Cuando copias un tablero de proyecto a una organización, la visibilidad del tablero de proyecto se predeterminará en privada, con la opción de cambiar la visibilidad. Para obtener más información, consulta "[Cambiar la visibilidad del tablero de proyecto](/articles/changing-project-board-visibility/)". + +La automatización del tablero de proyecto también está habilitada por defecto. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards/)". + +1. Navega hasta el tablero de proyecto que quieres copiar. +{% data reusables.project-management.click-menu %} +3. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **Copy** (Copiar). ![Opción para copiar en el menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-copy-setting.png) +4. Debajo de "Owner" (Propietario), usa el menú desplegable y haz clic en el repositorio o la organización donde deseas copiar el tablero de proyecto. ![Selecciona el propietario del tablero de proyecto copiado desde el menú desplegable](/assets/images/help/projects/copied-project-board-owner.png) +5. Opcionalmente, debajo de "Project board name" (Nombre del tablero de proyecto), haz clic en el nombre del tablero de proyecto copiado. ![Campo para escribir un nombre para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-name.png) +6. Opcionalmente, debajo de "Description" (Descripción), escribe una descripción del tablero de proyecto copiado que verán otras personas. ![Campo para escribir una descripción para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-description.png) +7. Opcionalmente, debajo de "Automation settings " (Parámetros de automatización), selecciona si deseas copiar los flujos de trabajo automáticos configurados. Esta opción está habilitada por defecto. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards/)". ![Selecciona los parámetros de automatización para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-automation-settings.png) +{% data reusables.project-management.choose-visibility %} +9. Haz clic en **Copy project** (Copiar proyecto). ![Botón para confirmar copia](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md new file mode 100644 index 0000000000000..2a7f7b5aef5ab --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md @@ -0,0 +1,35 @@ +--- +title: Crear un enlace permanente a un fragmento de código +intro: Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. +redirect_from: + - /articles/creating-a-permanent-link-to-a-code-snippet +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Este tipo de enlace permanente se presentará como un fragmento de código únicamente en el repositorio en el que se originó. En los demás repositorios, el fragmento de código de enlace permanente se presentará como una URL. + +![Fragmento de código que se presenta en un comentario](/assets/images/help/repository/rendered-code-snippet.png) + +{% tip %} + +**Sugerencia:** Para crear un enlace permanente para un archivo completo, consulta "[Obtener enlaces permanentes a los archivos](/articles/getting-permanent-links-to-files)". + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Busca el código con el que deseas establecer el enlace: + - Para enlazar el código desde un archivo, dirígete hacia ese archivo. + - Para enlazar el código desde una solicitud de extracción, dirígete a la solicitud de extracción y haz clic en {% octicon "diff" aria-label="The file diff icon" %}**Archivos con cambios**. Luego, desplázate hasta el archivo que contiene el código que deseas incluir en tu comentario y haz clic en **Ver**. +{% data reusables.repositories.choose-line-or-range %} +4. A la izquierda de la línea o del rango de líneas, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. En el menú desplegable, haz clic en **Copiar enlace permanente**. ![Menú kebab con la opción de copiar un enlace permanente desde una línea seleccionada](/assets/images/help/repository/copy-permalink-specific-line.png) +5. Dirígete a la conversación en la que deseas enlazar el fragmento de código. +6. Pega tu enlace permanente en un comentario y haz clic en **Comentar**. ![Enlace permanente pegado en un comentario en el mismo repositorio](/assets/images/help/repository/code-snippet-permalink-in-comment.png) + +### Further reading + +- [Crear una propuesta](/articles/creating-an-issue/)" +- "[Abrir una propuesta desde el código](/articles/opening-an-issue-from-code/)" +- "[Revisar los cambios en las solicitudes de extracción](/articles/reviewing-changes-in-pull-requests/)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md new file mode 100644 index 0000000000000..8307023197eba --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -0,0 +1,91 @@ +--- +title: Crear un tablero de proyecto +intro: 'Los tableros de proyecto se pueden usar para crear flujos de trabajo personalizados de acuerdo con tus necesidades, como hacer un seguimiento y priorizar trabajos con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos.' +redirect_from: + - /articles/creating-a-project/ + - /articles/creating-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.project-management.use-automated-template %} + +{% data reusables.project-management.copy-project-boards %} + +{% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta "[Enlazar un repositorio a un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". + +Una vez que has creado tu tablero de proyecto, puedes agregarle propuestas, solicitudes de extracción y notas. Para obtener más información, consulta "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" y "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". + +También puedes configurar automatizaciones de flujo de trabajo para mantener tu tablero de proyecto sincronizado con el estado de las propuestas y solicitudes de extracción. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". + +{% data reusables.project-management.project-board-import-with-api %} + +### Crear un tablero de proyecto propiedad de un usuario + +{% data reusables.profile.access_profile %} +2. En la parte superior de tu página de perfil, en la navegación principal, da clic en +{% octicon "project" aria-label="The project board icon" %} **Proyectos**. +![Pestaña Project (Proyecto)](/assets/images/help/projects/user-projects-tab.png) +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} +{% data reusables.project-management.linked-repositories %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} + +{% data reusables.project-management.edit-project-columns %} + +### Crear un tablero de proyecto para toda la organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} +{% data reusables.project-management.linked-repositories %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} + +{% data reusables.project-management.edit-project-columns %} + +### Crear un tablero de proyecto para un repositorio + +{% data reusables.repositories.navigate-to-repo %} +2. Under your repository name, click +{% octicon "project" aria-label="The project board icon" %} **Proyectos**. +![Pestaña Project (Proyecto)](/assets/images/help/projects/repo-tabs-projects.png) +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} + +{% data reusables.project-management.edit-project-columns %} + +### Further reading + +- "[Acerca de los tableros de proyectos](/articles/about-project-boards)" +- "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" +- "[Acerca de la automatización de los tableros de proyecto](/articles/about-automation-for-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md new file mode 100644 index 0000000000000..b63c4d2c0082a --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md @@ -0,0 +1,49 @@ +--- +title: Crear una propuesta +intro: 'Las propuestas se pueden usar para hacer un seguimiento de los errores, mejoras u otras solicitudes.' +permissions: 'Las personas con permisos de lectura pueden crear una propuesta en un repositorio en donde las propuestas se hayan habilitado.' +redirect_from: + - /articles/creating-an-issue +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes abrir una nueva propuesta basada en el código a partir de una solicitud de extracción existente. Para obtener más información, consulta la sección "[Abrir una propuesta desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". + +Puedes abrir una propuesta nueva desde un comentario en algún otro informe o en una solicitud de cambios. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% tip %} + +**Tip**: También puedes crear una propuesta si usas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh issue create`](https://cli.github.com/manual/gh_issue_create)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} + +Si utilizas un tablero de proyecto para rastrear y priorizar tu trabajo, puedes convertir las notas del mismo en informes de problemas. Para obtener más información, consulta la sección "[Acerca de los tableros de proyecto](/github/managing-your-work-on-github/about-project-boards)" y "[Agregar notas a un tablero de proyecto](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)". + +{% tip %} + +**Sugerencias**: Los mantenedores del proyecto pueden elegir hacer lo siguiente: + - Crear una plantilla de propuesta para un repositorio. Las plantillas incluyen indicaciones para brindar información en el cuerpo de una propuesta. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/github/building-a-strong-community/about-issue-and-pull-request-templates)". + - Inhabilitar las propuestas para un repositorio. Para obtener más información, consulta la sección "[Inhabilitar propuestas](/github/managing-your-work-on-github/disabling-issues)". Las solicitudes de cambios no pueden apagarse y siempre están disponibles. + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +3. Haz clic en **Propuesta nueva**. ![Botón Nuevas propuestas](/assets/images/help/issues/new_issues_button.png) +4. Si hay distintos tipos de propuestas, haz clic en **Empezar** junto al tipo de propuesta que deseas abrir. ![Selecciona el tipo de propuesta que quieres crear](/assets/images/help/issues/issue_template_get_started_button.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion >= "enterprise-server@2.21" %} +5. Opcionalmente, da clic en **Abrir una propuesta en blanco** si el tipo de propuesta que quieres abrir no se incluye en las opciones disponibles. ![Enlace para abrir una propuesta en blanco](/assets/images/help/issues/blank_issue_link.png) +{% else %} +5. Opcionalmente, da clic en **Abrir una propuesta normal** si el tipo de propuesta que quieres abrir no se incluye en las opciones disponibles. ![Enlace para abrir una propuesta normal](/assets/images/help/issues/regular_issue_link.png) +{% endif %} +{% data reusables.repositories.type-issue-title-and-description %} +{% data reusables.repositories.assign-an-issue-as-project-maintainer %} +{% data reusables.repositories.submit-new-issue %} +### Further reading + +- "[Crear un enlace permanente a un fragmento de código](/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet)". diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md new file mode 100644 index 0000000000000..e8f78b59b5ada --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md @@ -0,0 +1,35 @@ +--- +title: Crear y editar hitos para propuestas y solicitudes de extracción +intro: Puedes crear un hito para hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. +redirect_from: + - /articles/creating-milestones-for-issues-and-pull-requests/ + - /articles/creating-and-editing-milestones-for-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.milestones %} +4. Elige una de las siguientes opciones: + - Para crear un nuevo hito, haz clic en **Nuevo hito**. ![Botón Nuevo hito](/assets/images/help/repository/new-milestone.png) + - Para editar un hito, haz clic en **Editar** junto al hito que deseas editar. ![Opción Editar hito](/assets/images/help/repository/edit-milestone.png) +5. Escribe el título, la descripción y los demás cambios del hito, y luego haz clic en **Create milestone** (Crear hito) o **Save changes** (Guardar cambios). + +### Eliminar hitos + +Cuando eliminas hitos, las propuestas y las solicitudes de extracción no se ven afectadas. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.milestones %} +4. Junto al hito que deseas eliminar, haz clic en **Eliminar**. ![Opción Eliminar hito](/assets/images/help/repository/delete-milestone.png) + +### Further reading + +- "[Acerca de los hitos](/articles/about-milestones)" +- "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" +- "[Ver el progreso de tus hitos](/articles/viewing-your-milestone-s-progress)" +- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md new file mode 100644 index 0000000000000..a58565649664b --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md @@ -0,0 +1,29 @@ +--- +title: Eliminar un tablero de proyecto +intro: Puedes eliminar un tablero de proyecto existente si ya no necesitas acceder a su contenido. +redirect_from: + - /articles/deleting-a-project/ + - /articles/deleting-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia**: Si deseas conservar el acceso a un tablero de proyecto que ya no necesitas o que ya está completo sin perder acceso a su contenido, puedes [cerrar el tablero de proyecto](/articles/closing-a-project-board) en lugar de eliminarlo. + +{% endtip %} + +1. Dirígete al tablero de proyecto que deseas eliminar. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.click-edit-sidebar-menu-project-board %} +4. Haz clic en **Eliminar proyecto**. ![Botón Eliminar proyecto](/assets/images/help/projects/delete-project-button.png) +5. Para confirmar que deseas eliminar el tablero de proyecto, haz clic en **Aceptar**. + +### Further reading + +- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" +- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" +- "[Inhabilitar tableros de proyectos en tu organización](/articles/disabling-project-boards-in-a-repository)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md new file mode 100644 index 0000000000000..0f4b2a74d4af3 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md @@ -0,0 +1,24 @@ +--- +title: Eliminar una propuesta +intro: Los usuarios con permisos de administración en un repositorio determinado pueden eliminar una propuesta de manera permanente de ese repositorio. +redirect_from: + - /articles/deleting-an-issue +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo puedes eliminar una propuesta en un repositorio que sea propiedad de tu cuenta de usuario. No puedes eliminar una propuesta en un repositorio que sea propiedad de otra cuenta de usuario, aun si eres una colaborador de esa cuenta. + +Para eliminar una propuesta en un repositorio que sea propiedad de una organización, un propietario de la organización debe habilitar la eliminación de una propuesta para los repositorios de la organización, y tú debes tener permisos de propietario o de administración en ese repositorio. Para obtener más información, consulta "[Permitir que se eliminen propuestas en tu organización](/articles/allowing-people-to-delete-issues-in-your-organization)" y "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". + +Los colaboradores no reciben una notificación cuando eliminas una propuesta. Cuando visiten la URL de una propuesta que ha sido eliminada, los colaboradores verán un mensaje que dice que la propuesta se ha eliminado. Los usuarios con permisos de propietario o de administración en el repositorio verán también el nombre de usuario de la persona que eliminó la propuesta y la fecha en que se la eliminó. + +1. Dirígete a la propuesta que deseas eliminar. +3. En la barra lateral derecha, debajo de "Notificaciones", da clic en **Borrar informe de problemas**. ![Texto de "Borrar informe de problemas" resaltado al final de la barra lateral derecha de la página del informe de problemas](/assets/images/help/issues/delete-issue.png) +4. Para confirmar la eliminación, haz clic en **Eliminar esta propuesta**. + +### Further reading + +- "[Enlazar una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/disabling-issues.md b/translations/es-ES/content/github/managing-your-work-on-github/disabling-issues.md new file mode 100644 index 0000000000000..b1172604c8ce9 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/disabling-issues.md @@ -0,0 +1,28 @@ +--- +title: Inhabilitar propuestas +intro: Es posible que desees desactivar las propuestas de tu repositorio en caso de que no aceptes contribuciones o informes de errores. +redirect_from: + - /articles/disabling-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En Características, quita la marca de selección de la casilla de verificación **Propuestas**. ![Casilla de verificación Eliminar propuestas](/assets/images/help/issues/issues_settings_remove_from_repo.png) + +Si decides habilitar las propuestas nuevamente en el futuro, todas las propuestas que se hayan agregado previamente estarán disponibles. + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} +Porfavor contacta a + +{% data variables.contact.contact_support %} si quieres desactivar las propuestas para evitar el abuso de personas desconocidas. +{% data reusables.policies.abuse %} + +{% endtip %} + +{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md new file mode 100644 index 0000000000000..71247f5068eb2 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md @@ -0,0 +1,18 @@ +--- +title: Inhabilitar los tableros de proyecto en un repositorio +intro: Los administradores de los repositorios pueden desactivar los tableros de proyecto para un repositorio si tanto tu equipo como tú administran el trabajo de forma diferente. +redirect_from: + - /articles/disabling-project-boards-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando inhabilitas los tableros de proyecto, ya no ves la información de los tableros de proyecto de manera cronológica o de acuerdo con los [registros de auditoría](/articles/reviewing-your-security-log/). + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. En "Características", quita la marca de selección de la casilla de verificación **Proyectos**. ![Casilla de verificación Eliminar proyectos](/assets/images/help/projects/disable-projects-checkbox.png) + +Una vez que se inhabilitan los tableros de proyecto, ya no se puede acceder a ellos en sus URL anteriores. {% data reusables.organizations.disable_project_board_results %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md new file mode 100644 index 0000000000000..d5be330ad375e --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md @@ -0,0 +1,33 @@ +--- +title: Inhabilitar los tableros de proyecto en tu organización +intro: Los propietarios de la organización pueden desactivar tableros de proyecto que se usan en toda la organización y tableros de proyecto de repositorios en una organización. +redirect_from: + - /articles/disabling-project-boards-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Una vez que inhabilites tableros de proyecto que se usan en toda la organización, ya no se podrán crear nuevos tableros de proyecto a nivel de la organización, y ya no se podrá acceder a ningún tablero de proyecto existente a nivel de la organización en su URL anterior. Los tableros de proyecto en los repositorios de la organización no se ven afectados. + +Una vez que inhabilites tableros de proyecto de repositorios en una organización, ya no se podrán crear nuevos tableros de proyecto en ningún repositorio de la organización, y ya no se podrá acceder a ningún tablero de proyecto de los repositorios existentes en la organización en sus URL anteriores. Los tableros de proyecto a nivel de la organización no se ven afectados. + +Cuando inhabilitas tableros de proyecto, ya no ves su información de manera cronológica o de acuerdo con los [registros de auditoría](/articles/reviewing-your-security-log/). + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos": + - Para inhabilitar los tableros de proyecto que se usan en toda la organización, quita la marca de selección de **Habilitar proyectos para la organización**. + - Para inhabilitar los tableros de proyecto de los repositorios en la organización, quita la marca de selección de **Habilitar proyectos para todos los repositorios**. ![Casillas de verificación para inhabilitar proyectos para una organización o para todos los repositorios de una organización](/assets/images/help/projects/disable-org-projects-checkbox.png) +5. Haz clic en **Save ** (guardar). + +{% data reusables.organizations.disable_project_board_results %} + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" +- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" +- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md new file mode 100644 index 0000000000000..b18fde040c8e5 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md @@ -0,0 +1,29 @@ +--- +title: Editar un tablero de proyecto +intro: Puedes editar el título y la descripción de un tablero de proyecto existente. +redirect_from: + - /articles/editing-a-project/ + - /articles/editing-and-deleting-a-project/ + - /articles/editing-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Para conocer detalles sobre cómo agregar, eliminar o editar columnas en tu tablero de proyecto, consulta "[Crear un tablero de proyecto](/articles/creating-a-project-board)". + +{% endtip %} + +1. Dirígete al tablero de proyecto que deseas editar. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.click-edit-sidebar-menu-project-board %} +4. Modifica el nombre y la descripción del tablero de proyecto según sea necesario y luego haz clic en **Guardar proyecto**. ![Campos con el nombre y la descripción del tablero de proyecto y botón Guardar proyecto](/assets/images/help/projects/edit-project-board-save-button.png) + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md new file mode 100644 index 0000000000000..60b8ad8690c3e --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md @@ -0,0 +1,42 @@ +--- +title: Adjuntos de archivos en propuestas y solicitudes de extracción +intro: 'Cuando abres una propuesta o actualizas una solicitud de extracción, puedes usar los adjuntos de propuestas para cargar imágenes de las características propuestas o capturas de pantalla de errores.' +redirect_from: + - /articles/issue-attachments/ + - /articles/file-attachments-on-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% warning %} + +**Advertencia:** Si agregas una imagen a una solicitud de extracción o un comentario sobre una propuesta, cualquier usuario podrá ver la URL de la imagen anonimizada sin autenticación, aun si la solicitud de extracción se encuentra en un repositorio privado{% if enterpriseServerVersions contains currentVersion %} o si el modo privado se encuentra habilitado{% endif %}. Para mantener las imágenes confidenciales en privado, limítalas a una red privada o a un servidor que requiera de autenticación. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información sobre las URL anonimozadas, consulta la sección "[Acerca de las URL de imagen anonimizadas](/articles/about-anonymized-image-urls)".{% endif %} + +{% endwarning %} + +Para adjuntar un archivo a una propuesta o una conversación de una solicitud de extracción, arrástralo y suéltalo en el cuadro de comentarios. Como alternativa, puedes dar clic en la barra al final del recuadro de comentarios para buscar, seleccionar y agregar un archivo desde tu ordenador. + +![Seleccionar adjuntos desde el ordenador](/assets/images/help/pull_requests/select-bar.png) + +{% tip %} + +**Tip:** En varios buscadores, puedes copiar y pegar las imágenes directamente en el campo. + +{% endtip %} + +El tamaño máximo de los archivos es de 25 MB y el tamaño máximo de las imágenes es de 10 MB. + +Archivos compatibles: + +* PNG (*.png*) +* GIF (*.gif*) +* JPEG (*.jpg*) +* Archivos de registro (*.log*) +* Documentos de Microsoft Word (*.docx*), Powerpoint (*.pptx*) y Excel (*.xlsx*) +* Archivos de texto (*.txt*) +* PDF (*.pdf*) +* ZIP (*.zip*, *.gz*) + +![GIF animados adjuntos](/assets/images/help/pull_requests/dragging_images.gif) diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md new file mode 100644 index 0000000000000..7e6d0df42e324 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md @@ -0,0 +1,41 @@ +--- +title: Filtrar tarjetas en un tablero de proyecto +intro: Puedes filtrar las tarjetas en un tablero de proyecto para buscar tarjetas específicas o ver un subconjunto de tarjetas. +redirect_from: + - /articles/filtering-cards-on-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +En una tarjeta, puedes dar clic en cualquier asignado, hito, o etiqueta para filtrar el tablero de proyecto de acuerdo con ese calificador. Para limpiar la búsqueda, puedes dar clic en el mismo asignado, hito o etiqueta nuevamente. + +También puedes usar la barra de búsqueda "Filtrar tarjetas" en la parte superior de cada tablero de proyecto para buscar tarjetas. Puedes filtrar tarjetas usando los siguientes calificadores de búsqueda en cualquier combinación, o simplemente escribir el texto que deseas buscar. + +- Filtrar tarjetas por autor usando `author:USERNAME` +- Filtrar tarjetas por asignatario usando `assignee:USERNAME` o `no:assignee` +- Filtra las tarjetas por etiqueta utilizando `label:LABEL`, `label:"MULTI-WORD LABEL NAME"`, o `no:label` +- Filtrar por hito usando `milestone:MY-MILESTONE` +- Filtrar tarjetas por estado usando `state:open`, `state:closed` o `state:merged` +- Filtrar por estado de revisión usando `review:none`, `review:required`, `review:approved`, o `review:changes_requested` +- Filtrar por comprobación de estado usando `status:pending`, `status:success` o `status:failure` +- Filtrar tarjetas por tipo usando `type:issue`, `type:pr` o `type:note` +- Filtrar tarjetas por estado y tipo usando `is:open`, `is:closed` o `is:merged` y `is:issue`, `is:pr` o `is:note` +- Filtra tarjetas por las propuestas que están vinculadas a una solicitud de cambios mediante una referencia de cierre utilizando `linked:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- Filtrar tarjetas por repositorio en un tablero de proyecto de toda la organización utilizando `repo:ORGANIZATION/REPOSITORY`{% endif %} + +1. Dirígete al tablero de proyecto que contenga las tarjetas que desees filtrar. +2. Sobre las columnas de las tarjetas del proyecto, haz clic en la barra de búsqueda "Filtrar tarjetas" y escribe la consulta de búsqueda para filtrar las tarjetas. ![Barra de búsqueda Filtrar tarjetas](/assets/images/help/projects/filter-card-search-bar.png) + +{% tip %} + +**Sugerencia:** Puedes arrastrar y soltar las tarjetas filtradas o usar los atajos del teclado para moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} + +{% endtip %} + +### Further reading + +- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" +- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md new file mode 100644 index 0000000000000..43ce98e4d4db0 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md @@ -0,0 +1,31 @@ +--- +title: Filtrar propuestas y solicitudes de extracción por asignatarios +intro: 'Una vez que has [asignado una propuesta o solicitud de extracción a alguien] (/articles/assigning-issues-and-pull-requests-to-other-github-users), puedes buscar elementos que se basan en la persona que se encuentra trabajando en estas.' +redirect_from: + - /articles/filtering-issues-and-pull-requests-by-assignees +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.cli.filter-issues-and-pull-requests-tip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. En el ángulo superior derecho, selecciona el menú desplegable Asignatario. +4. El menú desplegable Asignatario menciona a todos los usuarios que tienen acceso de escritura a tu repositorio. Haz clic en el nombre de la persona cuyos elementos asignados deseas ver, o haz clic en **No asignado a nadie** para ver qué propuestas no están asignadas. ![Utilizar la pestaña desplegable Asignatarios](/assets/images/help/issues/issues_assignee_dropdown.png) + +{% tip %} + +Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. + +{% endtip %} + +### Further reading + +- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" +- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +- "[Compartir filtros](/articles/sharing-filters)" +- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md new file mode 100644 index 0000000000000..4821fd80f1b72 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md @@ -0,0 +1,30 @@ +--- +title: Filtrar propuestas y solicitudes de extracción por etiquetas +intro: 'Una vez que has [aplicado etiquetas a una propuesta o solicitud de extracción] (/articles/applying-labels-to-issues-and-pull-requests), puedes encontrar elementos basados en sus etiquetas.' +redirect_from: + - /articles/filtering-issues-and-pull-requests-by-labels +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.cli.filter-issues-and-pull-requests-tip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. En la lista de etiquetas, haz clic en una etiqueta para ver las propuestas y solicitudes de extracción a las que se ha aplicado. ![Lista de etiquetas de repositorio](/assets/images/help/issues/labels-page.png) + +{% tip %} + +**Sugerencia:** Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. + +{% endtip %} + +### Further reading + +- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" +- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +- "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md new file mode 100644 index 0000000000000..13f32f4f17c36 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md @@ -0,0 +1,33 @@ +--- +title: Filtrar propuestas y solicitudes de extracción por hito +intro: 'Las propuestas y solicitudes de extracción se pueden filtrar según el hito con el que están asociadas. Una vez que has [asociado una propuesta o solicitud de extracción con un hito](/articles/associating-milestones-with-issues-and-pull-requests), puedes buscar elementos basados en sus hitos. Dentro de un hito, puedes priorizar las propuestas y solicitudes de extracción.' +redirect_from: + - /articles/filtering-issues-and-pull-requests-by-milestone +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Tips:** + +- Si prefieres filtrar propuestas y solicitudes de extracción usando la barra de búsqueda, puedes usar la sintaxis de búsqueda de hitos. Para un hito llamado My milestone, la sintaxis de búsqueda sería: `milestone:"My Milestone"`. +- Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. +- También puedes filtrar las propuestas o solicitudes de cambios si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" o "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. Selecciona **Hitos** para ver una lista de todos los hitos disponibles para el repositorio. ![Botón Hitos](/assets/images/help/issues/issues_milestone_button.png) +4. Selecciona el hito que te interesa en la lista. En la página del hito puedes ver información relevante sobre el hito, incluidas todas las propuestas y solicitudes de extracción asociadas con él. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones)". + +### Further reading + +- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" +- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +- "[Compartir filtros](/articles/sharing-filters)" +- "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md new file mode 100644 index 0000000000000..d0c97871ce3ba --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md @@ -0,0 +1,34 @@ +--- +title: Filtrar propuestas y solicitudes de extracción +intro: Las propuestas y las solicitudes de extracción vienen con un conjunto de filtros predeterminados que puedes aplicar para organizar tus listas. +redirect_from: + - /articles/filtering-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.search.requested_reviews_search %} + +Puedes filtrar propuestas y solicitudes de extracción para buscar: +- Todas las propuestas y solicitudes de extracción abiertas +- Las propuestas y solicitudes de extracción creadas por ti +- Las propuestas y solicitudes de extracción que se te han asignado +- Las propuestas y solicitudes de extracción en las que eres [**@mencionado**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) + +{% data reusables.cli.filter-issues-and-pull-requests-tip %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. Haz clic en **Filtros** para elegir el tipo de filtro que te interesa. ![Usar el menú desplegable Filtros](/assets/images/help/issues/issues_filter_dropdown.png) + +### Further reading + +- "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" +- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" +- [Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)" +- "[Filtrar solicitudes de extracción por estado de revisión](/articles/filtering-pull-requests-by-review-status)" +- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +- "[Compartir filtros](/articles/sharing-filters)" +- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md new file mode 100644 index 0000000000000..7e252d5c05fd1 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -0,0 +1,29 @@ +--- +title: Filtrar solicitudes de extracción por estado de revisión +intro: Puedes usar filtros para ver en una lista las solicitudes de extracción por estado de revisión y buscar las solicitudes de extracción que has revisado o que otras personas te han pedido que revises. +redirect_from: + - /articles/filtering-pull-requests-by-review-status +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes filtrar la lista de solicitudes de extracción de un repositorio para buscar: +- Solicitudes de extracción que no han sido [revisadas](/articles/about-pull-request-reviews) todavía +- Solicitudes de extracción que [requieren una revisión](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de que puedan fusionarse +- Solicitudes de extracción que ha aprobado un revisor +- Solicitudes de extracción en las que un revisor ha pedido cambios +- Solicitudes de extracción que tú has revisado +- Solicitudes de extracción que [alguien te ha pedido a ti que revises o a un equipo del que eres miembro](/articles/requesting-a-pull-request-review) + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +3. En el ángulo superior derecho, selecciona el menú desplegable Revisiones. ![Menú desplegable Revisiones en el menú de filtros sobre la lista de solicitudes de extracción](/assets/images/help/pull_requests/reviews-filter-dropdown.png) +4. Elige un filtro para buscar todas las solicitudes de extracción con ese estado de filtro. ![Lista de filtros en el menú desplegable Revisiones](/assets/images/help/pull_requests/pr-review-filters.png) + +### Further reading + +- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" +- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md new file mode 100644 index 0000000000000..0cf9f3f735f1e --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md @@ -0,0 +1,12 @@ +--- +title: Buscar información en un repositorio +intro: 'Para buscar información detallada acerca de un repositorio en GitHub, puedes filtrar, clasificar y buscar propuestas y solicitudes de extracción que son relevantes para el repositorio.' +mapTopic: verdadero +redirect_from: + - /articles/finding-information-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-your-work-on-github/index.md b/translations/es-ES/content/github/managing-your-work-on-github/index.md new file mode 100644 index 0000000000000..045008e38f7b0 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/index.md @@ -0,0 +1,68 @@ +--- +title: Administrar tu trabajo en GitHub +redirect_from: + - /categories/100/articles/ + - /categories/managing-projects/ + - /categories/managing-projects-on-github/ + - /categories/managing-your-work-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} + {% link_in_list /about-issues %} + {% link_in_list /creating-an-issue %} + {% link_in_list /deleting-an-issue %} + {% link_in_list /opening-an-issue-from-a-comment %} + {% link_in_list /opening-an-issue-from-code %} + {% link_in_list /transferring-an-issue-to-another-repository %} + {% link_in_list /pinning-an-issue-to-your-repository %} + {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} + {% link_in_list /managing-labels %} + {% link_in_list /about-task-lists %} + {% link_in_list /about-automation-for-issues-and-pull-requests-with-query-parameters %} + {% link_in_list /file-attachments-on-issues-and-pull-requests %} + {% link_in_list /assigning-issues-and-pull-requests-to-other-github-users %} + {% link_in_list /viewing-all-of-your-issues-and-pull-requests %} + {% link_in_list /disabling-issues %} + {% link_in_list /linking-a-pull-request-to-an-issue %} + {% link_in_list /about-duplicate-issues-and-pull-requests %} +{% topic_link_in_list /managing-project-boards %} + {% link_in_list /about-project-boards %} + {% link_in_list /creating-a-project-board %} + {% link_in_list /editing-a-project-board %} + {% link_in_list /linking-a-repository-to-a-project-board %} + {% link_in_list /about-automation-for-project-boards %} + {% link_in_list /configuring-automation-for-project-boards %} + {% link_in_list /copying-a-project-board %} + {% link_in_list /closing-a-project-board %} + {% link_in_list /reopening-a-closed-project-board %} + {% link_in_list /deleting-a-project-board %} + {% link_in_list /disabling-project-boards-in-a-repository %} + {% link_in_list /disabling-project-boards-in-your-organization %} + {% link_in_list /changing-project-board-visibility %} +{% topic_link_in_list /tracking-the-progress-of-your-work-with-project-boards %} + {% link_in_list /adding-issues-and-pull-requests-to-a-project-board %} + {% link_in_list /adding-notes-to-a-project-board %} + {% link_in_list /tracking-progress-on-your-project-board %} + {% link_in_list /filtering-cards-on-a-project-board %} + {% link_in_list /archiving-cards-on-a-project-board %} +{% topic_link_in_list /tracking-the-progress-of-your-work-with-milestones %} + {% link_in_list /about-milestones %} + {% link_in_list /creating-and-editing-milestones-for-issues-and-pull-requests %} + {% link_in_list /associating-milestones-with-issues-and-pull-requests %} + {% link_in_list /filtering-issues-and-pull-requests-by-milestone %} + {% link_in_list /viewing-your-milestones-progress %} +{% topic_link_in_list /finding-information-in-a-repository %} + {% topic_link_in_list /finding-information-in-a-repository %} + {% link_in_list /filtering-issues-and-pull-requests-by-assignees %} + {% link_in_list /filtering-issues-and-pull-requests-by-labels %} + {% link_in_list /filtering-pull-requests-by-review-status %} + {% link_in_list /sorting-issues-and-pull-requests %} + {% link_in_list /using-search-to-filter-issues-and-pull-requests %} + {% link_in_list /sharing-filters %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md new file mode 100644 index 0000000000000..ce3a07566d455 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md @@ -0,0 +1,71 @@ +--- +title: Vincular una solicitud de cambios a una propuesta +intro: 'Puedes vincular una solicitud de cambios a una propuesta para mostrar que una solución está en progreso y para cerrar automáticamente la propuesta cuando se fusione la solicitud de cambios.' +redirect_from: + - /articles/closing-issues-via-commit-message/ + - /articles/closing-issues-via-commit-messages/ + - /articles/closing-issues-using-keywords + - /github/managing-your-work-on-github/closing-issues-using-keywords +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Las palabras clave especiales en una descripción de una solicitud de cambios se interpretan cuando la solicitud de cambios apunte a la rama *predeterminada* del repositorio. Sin embargo, si la base de la solicitud es *cualquier otra rama*, entonces estas palabras clave se ignorarán, no se creará ningún enlace, y el fusionar la solicitud no tendrá efecto alguno en las propuestas. **Si quieres vincular una solicitud de cambios con una propuesta utilizando una palabra clave, la solicitud debe estar en la rama predeterminada.** + +{% endnote %} + +### Acerca de las propuestas y solicitudes de cambios vinculadas + +Puedes vincular una propuesta a una solicitud de cambios {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manualmente o {% endif %} utilizando una palabra clave compatible en la descripción de dicha solilcitud de cambios. + +Cuando enlazas una solicitud de extracción al informe de problemas al que ésta hace referencia, los colaboradores pueden ver si alguien está trabajando en dicho informe. {% if currentVersion ver_lt "enterprise-server@2.21" %}Si la solicitud de cambios y la propuesta se encuentran en repositorios diferentes, {% data variables.product.product_name %} mostrará el enlace después de que se fusione la solicitud de cambios, si la persona que fusiona la solicitud también tiene permiso para cerrar la propuesta{% endif %} + +Cuando fusionas una solicitud de cambios que se ha vinculado y se encuentra en la rama predeterminada de un repositorio, su propuesta vinculada se cierra automáticamente. Para obtener más información acerca de la rama predeterminada, consulta la sección "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +### Vincular una solicitud de cambios manualmente a una propuesta + +Cualquiera con permisos de escritura en un repositorio puede enlazar una solicitud de extracción a un problema manualmente. + +Puedes enlazar hasta diez informes de problemas a cada solicitud de extracción manualmente. El informe de problemas y la solicitud de extracción deberán encontrarse en el mismo repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-pr %} +3. En la lista de solicitudes de extracción, da clic en aquella que quieras enlazar a un informe de problemas. +4. En la barra lateral derecha, da clic en **Propuestas vinculadas**. ![Informes de problemas enlazados en la barra lateral derecha](/assets/images/help/pull_requests/linked-issues.png) +5. Da clic en la propuesta que quieras enlazar a la solicitud de cambios. ![Menú desplegable para enlazar un informe de problemas](/assets/images/help/pull_requests/link-issue-drop-down.png) +{% endif %} + +### Vincular una solicitud de cambios a una propuesta utilizando una palabra clave + +Puedes vincular una solicitud de cambios con una propuesta si utilizas una palabra clave compatible en la descripción de la solicitud o en un mensaje de confirmación (por favor, considera que la solicitud de cambios debe estar en la rama predeterminada). + +* close +* closes +* closed +* fix +* fixes +* fixed +* resolve +* resuelve +* resuelto + +La sintaxis para palabras clave de cierre dependerá de si el informe de problemas se encuentra en el mismo repositorio que la solicitud de extracción. + +| Informe vinculado | Sintaxis | Ejemplo | +| ------------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------- | +| Propuesta en el mismo repositorio | Closes #10 | `Closes #10` | +| Propuesta en un repositorio diferente | *PALABRA CLAVE* *PROPIETARIO*/*Repositorio*#*NÚMERO DE PROPUESTA* | `Fixes octo-org/octo-repo#100` | +| Propuestas múltiples | Utilizar la sintaxis completa para cada informe | `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" %}Únicamente las solilcitudes de cambios que se han vinculado manualmente podrán desvincularse de la misma forma. Para desenlazar un informe de problemas que hayas enlazado previamente utilizando una palabra clave, deberás editar la descripción de la solicitud de extracción y así poder eliminar la palabra clave.{% endif %} + +También puedes utilizar palabras clave de cierre en un mensaje de confirmación. La propuesta se cerrará cuando fusiones la confirmación en la rama predeterminada, pero la solicitud de cambios que contiene la confirmación no se listará como una solicitud de cambios enlazada. + +### Further reading + +- "[URL y referencias auto-enlazadas](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md new file mode 100644 index 0000000000000..7f7ba6d977e2d --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md @@ -0,0 +1,32 @@ +--- +title: Vincular un repositorio a un tablero de proyecto +intro: Puedes vincular un repositorio a tu tablero de proyecto de la organización o de la cuenta de usuario. +redirect_from: + - /articles/linking-a-repository-to-a-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** Para poder vincular el repositorio a tu tablero de proyectos que pertenece a tu organización o usuario, el repositorio necesita que se le habiliten las propuestas. Para obtener información sobre cómo ver si las propuestas están inhabilitadas para un repositorio, consulta la sección "[Inhabilitar las propuestas](/github/managing-your-work-on-github/disabling-issues)". + +{% endnote %} + +Cualquiera con permisos de escritura en un tablero de proyecto puede enlazar repositorios que sean propiedad de la cuenta de usuario u organización al mismo. Para obtener más información, consulta la sección "[Permisos para una organización sobre el tablero de proyecto](/articles/project-board-permissions-for-an-organization/)" o "[Niveles de permiso para tableros de proyecto propiedad de un usuario](/articles/permission-levels-for-user-owned-project-boards/)". + +{% data reusables.project-management.link-repos-to-project-board %} Puedes agregar propuestas y solicitudes de extracción desde cualquier repositorio no vinculado escribiendo la URL de la propuesta o de la solicitud de extracción en una tarjeta. Para obtener más información, consulta "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)". + +1. Navega hasta el tablero de proyecto al que quieras vincular un repositorio. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +4. En la barra lateral izquierda, haz clic en **Linked repositories** (Repositorios vinculados). ![Opción del menú Linked repositories (Repositorios vinculados) en la barra lateral izquierda](/assets/images/help/projects/project-board-linked-repositories-setting.png) +5. Haz clic en **Link a repository** (Vincular un repositorio). ![Botón Link a repository (Vincular un repositorio) en la pestaña Linked repositories (Repositorios vinculados)](/assets/images/help/projects/link-repository-button.png) +6. Busca el repositorio que quieras vincular. ![Campo de búsqueda en la ventana Link a repository (Vincular un repositorio)](/assets/images/help/projects/search-to-link-repository.png) +7. Da clic en **Enlace**. Para desvincular, haz clic en **Unlink** (Desvincular). ![Botón Link (Vincular)](/assets/images/help/projects/link-button.png) + +### Further reading + +- "[Acerca de los tableros de proyectos](/articles/about-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md new file mode 100644 index 0000000000000..c497d5a058dfa --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md @@ -0,0 +1,96 @@ +--- +title: Administrar las etiquetas +intro: 'Puedes clasificar las propuestas y solicitudes de cambios si creas, editas, aplicas y borras etiquetas.' +redirect_from: + - /articles/managing-Labels + - /articles/labeling-issues-and-pull-requests + - /github/managing-your-work-on-github/labeling-issues-and-pull-requests + - /articles/about-labels + - /github/managing-your-work-on-github/about-labels + - /articles/creating-and-editing-labels-for-issues-and-pull-requests + - /articles/creating-a-label + - /github/managing-your-work-on-github/creating-a-label + - /articles/customizing-issue-labels/ + - /articles/applying-labels-to-issues-and-pull-requests + - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests + - /articles/editing-a-label + - /github/managing-your-work-on-github/editing-a-label + - /articles/deleting-a-label + - /github/managing-your-work-on-github/deleting-a-label +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las etiquetas + +Puedes administrar tu trabajo en {% data variables.product.product_name %} creando etiquetas para clasificar las propuestas y las solicitudes de extracción. Puedes aplicar etiquetas en el repositorio en el que éstas se hayan creado. Una vez que existe una etiqueta, puedes utilizarla en cualquier propuesta o solicitud de cambios dentro del repositorio en cuestión. + +Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquetas del repositorio. Anyone with triage access to a repository can apply/dismiss existing labels. Para crear, editar, aplicar o eliminar una etiqueta, debes tener acceso de escritura al repositorio. + +### Acerca de las etiquetas predeterminadas + +{% data variables.product.product_name %} ofrece etiquetas predeterminadas en cada repositorio nuevo. Puedes usar estas etiquetas predeterminadas para ayudar a crear un flujo de trabajo estándar en un repositorio. + +| Etiqueta | Descripción | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `error` | Indica un problema inesperado o un comportamiento no deseado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `documentación` | Indica una necesidad de mejoras o adiciones a la documentación{% endif %} +| `duplicado` | Indica propuestas o solicitudes de extracción similares | +| `mejora` | Indica solicitudes de nueva función | +| `primera buena propuesta` | Indica una buena propuesta para los colaboradores por primera vez | +| `se busca ayuda` | Indica que un mantenedor necesita ayuda en una propuesta o solicitud de extracción | +| `no válida` | Indica que una propuesta o solicitud de extracción ya no es relevante | +| `pregunta` | Indica que una propuesta o solicitud de extracción necesita más información | +| `wontfix` | Indica que no continuará el trabajo en una propuesta o solicitud de extracción | + +Las etiquetas predeterminadas se incluyen en todos los repositorios nuevos cuando se crea el repositorio, pero luego puedes editarlas o eliminarlas. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +Los propietarios de la organización pueden personalizar las etiquetas predeterminadas para los repositorios de la organización. Para obtener más información, consulta "[Administrar etiquetas predeterminadas para los repositorios en tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)". +{% endif %} + +### Crear una etiqueta + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +4. A la derecha del campo de búsqueda, haz clic en **Nueva etiqueta**. +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Aplicar etiquetas para propuestas y solicitudes de extracción + + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.repositories.select-items-in-issue-or-pr-list %} +4. En el ángulo superior derecho, haz clic en **Label** (Etiqueta), luego comienza a escribir el nombre de una etiqueta existente. Haz clic en el nombre de la etiqueta para asociarla con los elementos seleccionados. ![Desplegable de la asignación de los hitos de propuestas](/assets/images/help/issues/issues_applying_labels_dropdown.png) + +### Editar una etiqueta + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Eliminar una etiqueta +El borrar una etiqueta la eliminará de las propuestas y soilcitudes de cambios. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.labels %} +{% data reusables.project-management.delete-label %} + +### Further reading +- "[Filtrar propuestas y solicitudes de cambios por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[Administrar las etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Fomentar las contribuciones sanas a tu proyecto con etiquetas](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md new file mode 100644 index 0000000000000..1ce9ca4c9c757 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md @@ -0,0 +1,12 @@ +--- +title: Administrar tableros de proyecto +intro: Puedes usar tableros de proyecto para organizar propuestas y solicitudes de extracción y administrar tu flujo de trabajo a través de un repositorio u organización. +mapTopic: verdadero +redirect_from: + - /articles/managing-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md new file mode 100644 index 0000000000000..9d7994d118332 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -0,0 +1,13 @@ +--- +title: Administrar tu trabajo con propuestas y solicitudes de cambios +intro: 'Puedes administrar tu trabajo en {% data variables.product.product_name %} al crear propuestas para rastrear ideas, mejoras, tareas o errores.' +mapTopic: verdadero +redirect_from: + - /github/managing-your-work-on-github/managing-your-work-with-issues + - /articles/managing-your-work-with-issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md new file mode 100644 index 0000000000000..0f875a62c7e31 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md @@ -0,0 +1,26 @@ +--- +title: Abrir un informe de problemas desde un comentario +intro: Puedes abrir un nuevo informe de problemas desde un comentario específico en un informe de problemas o solicitud de extracción. +permissions: 'Las personas con permisos de lectura pueden crear una propuesta en un repositorio en donde las propuestas se hayan habilitado.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando abres un informe de problemas desde un comentario, este informe contiene un fragmento de código que muestra en dónde se hizo el comentario originalmente. + +{% data reusables.repositories.administrators-can-disable-issues %} + +1. Navega al comentario desde el cual quieras abrir un informe de problemas. + +2. Dentro del comentario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Botón Kebab en el comentario de la revisión de solicitud de extracción](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png) +3. Haz clic en **Reference in new issue** (Referencia en la propuesta nueva). ![Referencia en el elemento del menú de propuestas nuevas](/assets/images/help/pull_requests/reference-in-new-issue.png) +4. Usa el menú desplegable "Repository" (Repositorio) y selecciona el repositorio donde desees abrir la propuesta. ![Repositorio desplegable para nueva propuesta](/assets/images/help/pull_requests/new-issue-repository.png) +5. Escribe un título descriptivo y un cuerpo para la propuesta. ![Título y cuerpo para la nueva propuesta](/assets/images/help/pull_requests/new-issue-title-and-body.png) +6. Haz clic en **Create issue** (Crear propuesta). ![Botón para crear la nueva propuesta](/assets/images/help/pull_requests/create-issue.png) +{% data reusables.repositories.assign-an-issue-as-project-maintainer %} + +### Further reading + +- [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md new file mode 100644 index 0000000000000..954e71dad6371 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md @@ -0,0 +1,35 @@ +--- +title: Abrir una propuesta desde el código +intro: Puedes abrir una nueva propuesta desde una línea específica o líneas de código en un archivo o solicitud de extracción. +permissions: 'Las personas con permisos de lectura pueden crear una propuesta en un repositorio en donde las propuestas se hayan habilitado.' +redirect_from: + - /articles/opening-an-issue-from-code +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando abres una propuesta desde el código, la propuesta contiene un fragmento de código que muestra la línea o rango de código que elegiste. Solo puedes abrir una propuesta en el mismo repositorio donde se almacena el código. + +![Fragmento de código representado en una propuesta abierta desde el código](/assets/images/help/repository/issue-opened-from-code.png) + +{% data reusables.repositories.administrators-can-disable-issues %} + +{% data reusables.repositories.navigate-to-repo %} +2. Ubica el código que deseas hacer referencia en una propuesta: + - Para abrir una propuesta acerca de un código en un archivo, navega hasta el archivo. + - Para abrir una propuesta acerca de un código en una solicitud de extracción, navega hasta la solicitud de extracción y haz clic en {% octicon "diff" aria-label="The file diff icon" %} **Files changed (Archivos modificados)**. Luego, desplázate hasta el archivo que contiene el código que deseas incluir en tu comentario y haz clic en **Ver**. +{% data reusables.repositories.choose-line-or-range %} +4. A la izquierda del rango de código, da clic en +{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. En el menú desplegable, da clic en **Referenciar en nuevo informe de problemas**. + ![Menú Kebab con opción para abrir una propuesta nueva desde una línea seleccionada](/assets/images/help/repository/open-new-issue-specific-line.png) +{% data reusables.repositories.type-issue-title-and-description %} +{% data reusables.repositories.assign-an-issue-as-project-maintainer %} +{% data reusables.repositories.submit-new-issue %} + +### Further reading + +- [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" +- "[Obtener enlaces permanentes a los archivos](/github/managing-files-in-a-repository/getting-permanent-links-to-files)" +- "[Crear un enlace permanente a un fragmento de código](/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet)". diff --git a/translations/es-ES/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md new file mode 100644 index 0000000000000..a15930a6ad9db --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md @@ -0,0 +1,19 @@ +--- +title: Anclar una propuesta a tu repositorio +intro: Puedes anclar hasta tres propuestas importantes encima de las propuestas enumeradas en tu repositorio. +redirect_from: + - /articles/pinning-an-issue-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +![Propuestas ancladas](/assets/images/help/issues/pinned-issues.png) + +Para anclar una propuesta, debes tener permisos de escritura para el repositorio dentro del cual se encuentra la propuesta. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +3. En la lista de propuestas, haz clic en la propuesta que deseas anclar. +4. En la barra lateral derecha, haz clic **Pin issue (Anclar una propuesta)**. ![Botón para anclar una propuesta](/assets/images/help/repository/pin-issue.png) diff --git a/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md new file mode 100644 index 0000000000000..09185f7d7c732 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md @@ -0,0 +1,24 @@ +--- +title: Reabrir un tablero de proyecto cerrado +intro: Puedes reabrir un tablero de proyecto cerrado y reiniciar cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto. +redirect_from: + - /articles/reopening-a-closed-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando cierras un tablero de proyecto, por defecto, se detiene cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto. Para obtener más información, consulta "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". + +Cuando reabres un tablero de proyecto, tienes la opción de *sync* (sincronizar) automatización, lo cual actualiza la posición de las tarjetas en el tablero de acuerdo con los parámetros de automatización establecidos para el tablero. + +1. Navega hasta el tablero de proyecto que quieres reabrir. +{% data reusables.project-management.click-menu %} +3. Elige la sincronización de la automatización para tu tablero de proyecto o reabre tu tablero de proyecto sin sincronizar. + - Para reabrir tu tablero de proyecto y sincronizar la automatización, haz clic en **Reopen and sync project** (Reabrir y sincronizar proyecto). ![Selecciona el botón "Reopen and resync project" (Reabrir y resincronizar proyecto)](/assets/images/help/projects/reopen-and-sync-project.png) + - Para reabrir tu tablero de proyecto sin sincronizar la automatización, utilizando el menú desplegable, haz clic en **Reopen only** (Solo reabrir). Luego, haz clic en **Reopen only** (Solo reabrir). ![Menú desplegable para reabrir tablero de proyecto cerrado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png) + +### Further reading + +- "[Configurar la automatización para los tableros de proyecto](/articles/configuring-automation-for-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md b/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md new file mode 100644 index 0000000000000..35cd81029750d --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md @@ -0,0 +1,24 @@ +--- +title: Compartir filtros +intro: 'Cuando filtras o clasificas propuestas y solicitudes de extracción, la URL de tu navegador se actualiza automáticamente para coincidir con la nueva vista.' +redirect_from: + - /articles/sharing-filters +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes enviar la URL que genera esa propuesta a cualquier usuario, que podrá ver el mismo filtro que tú ves. + +Por ejemplo, si filtras propuestas asignadas a Hubot, y clasificas las propuestas abiertas más antiguas, tu URL se actualizaría a algo similar a esto: + +``` +/issues?q=state:open+type:issue+assignee:hubot+sort:created-asc +``` + +### Further reading + +* [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +* [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" +* "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md new file mode 100644 index 0000000000000..d4d3e3e97ad7b --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md @@ -0,0 +1,32 @@ +--- +title: Clasificar propuestas y solicitudes de extracción +intro: Los filtros pueden ser clasificados para ofrecer mejor información durante un período de tiempo específico. +redirect_from: + - /articles/sorting-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes clasificar cualquier vista filtrada por: + +* Las propuestas y solicitudes de extracción creadas más recientemente +* Las propuestas y solicitudes de extracción creadas con mayor antigüedad +* Las propuestas y solicitudes de extracción más comentadas +* Las propuestas y solicitudes de extracción menos comentadas +* Las propuestas y solicitudes de extracción actualizadas más recientemente +* Las propuestas y solicitudes de extracción actualizadas con mayor antigüedad +* La [reacción](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) más agregada en propuestas o solicitudes de extracción + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. En el ángulo superior derecho, selecciona el menú desplegable de Clasificación. ![Utilizar la pestaña desplegable de Clasificación](/assets/images/help/issues/issues_sort_dropdown.png) + +Para borrar tu selección de clasificación, haz clic en **Sort** > (Clasificar); **Newest** (Más reciente). + +### Further reading + +* [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +* "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" +* "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md new file mode 100644 index 0000000000000..0be2909f24fdd --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md @@ -0,0 +1,17 @@ +--- +title: Rastrear el progreso en tu tablero de proyecto +intro: Puedes ver el progreso general de tu proyecto en una barra de progreso. +redirect_from: + - /articles/tracking-progress-on-your-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.project-management.project-progress-locations %} + +1. Navega hasta el tablero de proyecto en donde quieras habilitar o inhabilitar el rastreo de progreso del proyecto. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.click-edit-sidebar-menu-project-board %} +4. Selecciona o deselecciona **Rastrear el progreso del proyecto**. diff --git a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md new file mode 100644 index 0000000000000..00b600730d3c3 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md @@ -0,0 +1,12 @@ +--- +title: Rastrear el progreso de tu trabajo con hitos +intro: 'Puedes hacer el seguimiento de tu trabajo en {% data variables.product.product_name %} creando hitos con propuestas y solicitudes de extracción asociadas.' +mapTopic: verdadero +redirect_from: + - /articles/tracking-the-progress-of-your-work-with-milestones +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md new file mode 100644 index 0000000000000..ea56d41f8ba0e --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md @@ -0,0 +1,13 @@ +--- +title: Rastrear el progreso de tu trabajo con tableros de proyecto +intro: 'Puedes hacer el seguimiento y priorizar tu trabajo en {% data variables.product.product_name %} creando un tablero de proyecto con propuestas, solicitudes de extracción y notas asociadas.' +redirect_from: + - /articles/tracking-the-progress-of-your-work-with-projects/ + - /articles/tracking-the-progress-of-your-work-with-project-boards +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md new file mode 100644 index 0000000000000..7fe090d54dc19 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -0,0 +1,33 @@ +--- +title: Transferir una propuesta a otro repositorio +intro: 'Para mover una propuesta a un repositorio al que mejor se ajuste, puedes transferir propuestas abiertas a otros repositorios.' +redirect_from: + - /articles/transferring-an-issue-to-another-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para transferir una propuesta abierta a otro repositorio, debes tener permisos de escritura sobre el repositorio en el que está la propuesta y sobre el repositorio al que le estás transfiriendo la propuesta. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". + +Solo puedes transferir propuestas entre repositorios que pertenezcan a la misma cuenta de usuario o de organización.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}No puedes transferir una propuesta desde un repositorio privado a un repositorio público.{% endif %} + +Cuando transfieres un informe de problemas, se retendrá tanto los comentarios como las personas asignadas. No se retendrán los hitos y etiquetas de la propuesta. Esta propuesta se mantendrá en cualquier tablero de proyecto que pertenezca al usuario o que se encuentre en la organización y se eliminará de cualquier tablero de proyecto de los repositorios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)." + +Las personas o equipos que se mencionan en la propuesta recibirán una notificación que les haga saber que la propuesta se transfirió a un repositorio nuevo. La URL original se redirige a la URL nueva de la propuesta. Las personas que no tengan permisos de lectura en el repositorio nuevo verán un anuncio que les hará saber que la propuesta se transfirió a un repositorio nuevo al que no pueden acceder. + +### Transferir una propuesta abierta a otro repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +3. En la lista de propuestas, haz clic en la propuesta que quieres transferir. +4. En la barra lateral derecha, haz clic en **Transfer issue** (Transferir propuesta). ![Botón para transferir propuesta](/assets/images/help/repository/transfer-issue.png) +5. Utiliza el menú desplegable **Choose a repository** (Elegir un repositorio) y selecciona el repositorio al que quieres transferir la propuesta. ![Elige una selección de repositorio](/assets/images/help/repository/choose-a-repository.png) +6. Haz clic en **Transfer issue** (Transferir propuesta). ![Botón Transfer issue (Transferir propuesta)](/assets/images/help/repository/transfer-issue-button.png) + +### Further reading + +- "[Acerca de las propuestas](/articles/about-issues)" +- "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)" +- "[Revisar el registro de auditoría para tu organización](/articles/reviewing-the-audit-log-for-your-organization)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md new file mode 100644 index 0000000000000..88c4087fe3124 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -0,0 +1,52 @@ +--- +title: Utilizar búsqueda para filtrar propuestas y solicitudes de extracción +intro: Cada vista de propuestas y solicitudes de extracción viene con una barra de búsqueda para la administración de filtros avanzada. +redirect_from: + - /articles/using-search-to-filter-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La barra de búsqueda de propuestas y solicitudes de extracción te permite definir tus propios filtros personalizados y clasificar por una amplia variedad de criterios. Puedes encontrar la barra de búsqueda en las pestañas **Issues** (Propuestas) y **Pull requests** (Solicitudes de extracción) de cada repositorio y en tus [tableros de Issues (Propuestas) y Pull requests (Solicitudes de extracción)](/articles/viewing-all-of-your-issues-and-pull-requests). + +![La barra de búsqueda de propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) + +{% tip %} + +**Sugerencia:** {% data reusables.search.search_issues_and_pull_requests_shortcut %} + +{% endtip %} + +Con los términos de búsqueda de propuestas y solicitudes de extracción, puedes hacer lo siguiente: + +- Filtrar propuestas y solicitudes de extracción por autor: `state:open type:issue author:octocat` +- Filtrar propuestas y solicitudes de extracción que involucren, aunque no necesariamente [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) (mencionen), determinadas personas: `state:open type:issue involves:octocat` +- Filtrar propuestas y solicitudes de extracción por asignatario: `state:open type:issue assignee:octocat` +- Filtrar propuestas y solicitudes de extracción por etiqueta: `state:open type:issue label:"bug"` +- Filtra los términos de búsqueda utilizando `-` antes del término: `state:open type:issue -author:octocat` + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +Para el caso de informes de problemas, también puedes utilizar la búsqueda para: + +- Filtrar los informes de problemas enlazados a una solicitud de extracción mediante una referencia de cierre: `linked:pr` +{% endif %} + +Para las solicitudes de cambios, también puedes utilizar la búsqueda para: +- Filtrar solicitudes de extracción [en borrador](/articles/about-pull-requests#draft-pull-requests): `is:draft` +- Filtrar solicitudes de extracción que aún no hayan sido [revisadas](/articles/about-pull-request-reviews): `state:open type:pr review:none` +- Filtrar solicitudes de extracción que [requieran una revisión](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de que se puedan fusionar: `state:open type:pr review:required` +- Filtrar solicitudes de extracción que haya aprobado un revisor: `state:open type:pr review:approved` +- Filtrar solicitudes de extracción en las que un revisor haya solicitado cambios: `state:open type:pr review:changes_requested` +- Filtrar solicitudes de extracción por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` +- Filtrar solicitudes de extracción por el usuario específico [que solicitó la revisión](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filtra las solicitudes de cambios de acuerdo con el equipo al que se le solicitó la revisión: `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" %} +- Filtrar por las solicitudes de extracción enlazadas con un informe de problemas que se pudiera cerrar con dicha solicitud: `linked:issue`{% endif %} + +### Further reading + +- "[Buscar propuestas](/articles/searching-issues)" +- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" +- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" +- "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md new file mode 100644 index 0000000000000..d671ee6ac88c1 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md @@ -0,0 +1,19 @@ +--- +title: Ver todas tus propuestas y solicitudes de extracción +intro: 'Los tableros de propuestas y solicitudes de extracción enumeran las propuestas y solicitudes de extracción abiertas que has creado. Puedes utilizarlos para actualizar los elementos que se han puesto en espera, que has cerrado o que mantienes un registro de dónde has sido mencionado a lo largo de todos los repositorios (incluidos aquellos en los que no estás suscrito).' +redirect_from: + - /articles/viewing-all-of-your-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Tus tableros de propuestas y solicitudes de extracción están disponibles en la parte superior de cualquier página. En cada tablero, puedes filtrar la lista para encontrar propuestas y solicitudes de extracción que creaste, que están asignadas a ti o en las cuales estás mencionado. También puedes encontrar solicitudes de extracción que te han pedido que revises. + +1. En la partes superior de cualquier página, haz clic en **Pull requests (Solicitudes de extracción)** o **Issues (Propuestas)**. ![Tableros de solicitudes de extracción o propuestas globales](/assets/images/help/overview/issues_and_pr_dashboard.png) +2. Como alternativa, elige un filtro o [utiliza la barra de búsqueda para filtrar resultados más específicos](/articles/using-search-to-filter-issues-and-pull-requests). ![Lista de solicitudes de extracción con el filtro "Created" (Creado) seleccionado](/assets/images/help/overview/pr_dashboard_created.png) + +### Further reading + +- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar los repositorios que estás observando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md b/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md new file mode 100644 index 0000000000000..ac00fc6c58d36 --- /dev/null +++ b/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md @@ -0,0 +1,25 @@ +--- +title: Ver el avance de tu hito +intro: 'Con el fin de rastrear tus hitos, querrás obtener una mejor comprensión de cuántas propuestas y solicitudes de extracción abiertas están pendientes.' +redirect_from: + - /articles/viewing-your-milestone-s-progress + - /articles/viewing-your-milestones-progress +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. En el ángulo superior izquierdo, haz clic en **Milestones (Hitos)**. ![Botón de propuestas del hito](/assets/images/help/issues/issues_milestone_button.png) +4. Selecciona el hito sobre el que deseas ver más información. + +![Resumen de propuestas del hito](/assets/images/help/issues/issues_milestone_overview.png) + +Para administrar mejor tu proyecto, puedes priorizar propuestas o solicitudes de extracción dentro de un hito. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones#prioritizing-issues-and-pull-requests-in-milestones)." + +### Further reading + +* "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" +* "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md new file mode 100644 index 0000000000000..1145697312243 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -0,0 +1,35 @@ +--- +title: Acerca de las notificaciones por correo electrónico +intro: 'Cuando activas las notificaciones por correo electrónico, recibirás notificaciones de participación y de observación en tu cliente de correo electrónico y puedes filtrarlas usando la información del encabezado del correo electrónico.' +versions: + enterprise-server: <2.21 +--- + +Para obtener más información acerca de las diferencias entre las notificaciones de *participar* y *observar*, consulta la sección [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". + +Después de activar las notificaciones por correo electrónico, {% data variables.product.product_name %} te enviará notificaciones como correos electrónicos con varias partes que contienen copias del contenido tanto en HTML como en texto simple. El contenido de las notificaciones por correo electrónico incluye cualquier Markdown, @menciones, emojis, vínculos hash, etc., que aparecen en el contenido original en {% data variables.product.product_name %}. Si solo quieres ver el texto en el correo electrónico, puedes configurar tu cliente de correo electrónico para que muestre solo la copia de texto simple. Para obtener más información acerca de habilitar las notificaciones por correo electrónico, consulta la sección "[Elegir el método de entrega de tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". + +{% data reusables.notifications.outbound_email_tip %} + +{% data reusables.notifications.shared_state %} + +### Filtrar las notificaciones por correo electrónico + +Cada notificación por correo electrónico que envía {% data variables.product.product_name %} contiene información de encabezado. La información del encabezado en cada correo electrónico es consistente, para que puedas usarla en tu cliente de correo electrónico para filtrar o enviar todas las notificaciones de {% data variables.product.product_name %} o ciertos tipos de notificaciones de {% data variables.product.product_name %}. + +Las notificaciones por correo electrónico de {% data variables.product.product_name %} contienen la siguiente información de encabezado: + +| Encabezado | Información | +| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| dirección `De` | Esta dirección siempre será la dirección de correo electrónico de tipo "no-reply" que configure tu administrador de sitio. | +| campo `Para` | Este campo se conecta directamente con el hilo de correo. Si respondes al correo electrónico, agregarás un nuevo comentario a la conversación. | +| dirección `Cc` | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son:
  • `assign`: Te asignaron a una propuesta o solicitud de extracción.
  • `author`: Creaste una propuesta o solicitud de extracción.
  • `comment`: Comentaste una propuesta o solicitud de extracción.
  • `manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.
  • `mention`: Te mencionaron en una propuesta o solicitud de extracción.
  • `push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.
  • `review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.
  • `security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.
  • `state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.
  • `subscribed`: Hubo una actualización en un repositorio que estás mirando.
  • `team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.
  • `your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.
| +| Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} +| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
  • `low`
  • `moderate`
  • `high`
  • `critical`
Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". |{% endif %} + +### Further reading + +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" +- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" +- "[Crear gists](/articles/creating-gists)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md new file mode 100644 index 0000000000000..f73dcc3b0e342 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md @@ -0,0 +1,55 @@ +--- +title: Acerca de las notificaciones +intro: 'Las notificaciones ofrecen actualizaciones acerca de las actividades y las conversaciones en las que estás interesado. Puedes recibir notificaciones en {% data variables.product.product_name %} o mediante tu cliente de correo electrónico.' +versions: + enterprise-server: <2.21 +--- + +### Tipos de notificaciones + +Las notificaciones que recibes serán notificaciones de *participación* o notificaciones de *observación*. Ambos tipos de notificaciones se pueden recibir como notificaciones web o notificaciones por correo electrónico. Para obtener más información, consulta: + +- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" +- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" +- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" + +{% data reusables.notifications.outbound_email_tip %} + +{% data reusables.notifications.shared_state %} + +#### Notificaciones de participación + +{% data variables.product.product_name %} envía notificaciones de *participación* cuando estás directamente involucrado en las actividades o las conversaciones dentro de un repositorio o equipo del que eres miembro. Recibirás una notificación si: + - Te mencionan a tí o a un equipo del que eres miembro. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". + - Se menciona al equipo padre de un equipo hijo del que eres miembro. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". + - Eres asignado a una propuesta o solicitud de extracción. + - Se agrega un comentario en una conversación a la cual estás suscripto. + - Se realiza una confirmación de una solicitud de extracción a la que estás suscripto. + - Abres, comentas o cierras una propuesta o una solicitud de extracción. + - Se envía una revisión que aprueba o solicita cambios en una solicitud de extracción a la que estás suscripto. + - Se te solicita a tí o a un equipo del que eres miembro revisar una solicitud de extracción. + - Se te designa a tí o a un equipo del que eres miembro como propietario de un archivo y alguien abre una solicitud de extracción que modifica ese archivo. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners)." + - Creas o respondes a un debate de equipo. + +#### Notificaciones de observación + +{% data variables.product.product_name %} envía notificaciones de *observación* para actualizaciones en repositorios o debates de equipos que estés mirando. {% data reusables.notifications.auto-watch %}Para obtener más información, consulta la sección "[Observar y dejar de observar repositorios](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)." +Recibirás una notificación si: + - Se abre una propuesta. + - Se agrega un comentario a una propuesta abierta. + - Se abre una solicitud de extracción. + - Se agrega un comentario a una solicitud de extracción abierta. + - Se agrega un comentario a una confirmación de cambios. + - Se publica un lanzamiento. Para obtener más información, consulta "[Acerca de los lanzamientos](/articles/about-releases)." También puedes ver solo los lanzamientos publicados en un repositorio, en lugar de todas las actualizaciones de un repositorio. Para obtener más información, consulta la sección "[Observar y dejar de observar los lanzamientos para un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository)". + - Se envía una revisión que aprueba o solicita cambios en una solicitud de extracción. + - Se crea o se responde a una publicación de un debate de equipo para un equipo que estás mirando. + - Se abre, se edita o se responde a una publicación de un debate de equipo para un equipo padre o un equipo del que eres miembro y estás mirando. Para obtener más información, consulta "[Equipos anidados](/articles/about-teams/#nested-teams)". + +También puedes explorar las actividades de las personas que sigues, los repositorios que miras y las organizaciones de las que eres miembro en tu tablero. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". + +### Further reading + +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" +- "[Observar y dejar de observar los debates de equipo](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions)" +- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md new file mode 100644 index 0000000000000..75331687daaac --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md @@ -0,0 +1,24 @@ +--- +title: Acerca de las notificaciones web +intro: 'Si estás recibiendo notificaciones web, puedes ver tus notificaciones de participación y de observación en la página de notificaciones en {% data variables.product.product_name %}.' +versions: + enterprise-server: <2.21 +--- + +Para obtener más información acerca de las diferencias entre las notificaciones de *participar* y *observar*, consulta la sección [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". + +Cuando las notificaciones web están activadas para tu cuenta, puedes hacer clic en un elemento en tu página de notificaciones y serás redirigido a la conversación a la que hace referencia la notificación. Para obtener más información sobre cómo habilitar las notificaciones web, consulta la sección "[Elegir el método de entrega de tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". Para obtener más información sobre habilitar las notificaciones web, consulta la sección "[Elegir el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". + +{% data reusables.notifications.shared_state %} + +Desde la página de notificaciones, también puedes marcar las notificaciones como leídas, guardar las notificaciones para más adelante y cancelar la suscripción a los hilos. Para obtener más información, consulta: + +- "[Marcar las notificaciones como leídas](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read)" +- "[Guardar las notificaciones para después](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later)" +- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" + +### Further reading + +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" +- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md new file mode 100644 index 0000000000000..dc1b8bf64fa12 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md @@ -0,0 +1,23 @@ +--- +title: Acceder a tus notificaciones +intro: 'Según el modo en que se configuró tu entrega de notificaciones, puedes acceder a tus notificaciones en {% data variables.product.product_name %} o a través de tu cliente de correo electrónico.' +versions: + enterprise-server: <2.21 +--- + +### Acceder a tus notificaciones web + +Para acceder a las notificaciones web en {% data variables.product.product_name %}, debes tener las notificaciones web habilitadas. Para obtener más información, consulta la sección "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" y "[Elegir el método de entrega de tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". + +{% data reusables.notifications.access_notifications %} +2. En la barra lateral izquierda, para ver todas las notificaciones de las actividades en las que estás participando, haz clic en **Participating** (Participación). ![Enumerar las notificaciones de participación](/assets/images/help/notifications/notifications_sidebar_participating.png) +3. En la barra lateral izquierda, haz clic en el nombre de un repositorio para ver las notificaciones de un repositorio específico. ![Enumerar las notificaciones de repositorio individual](/assets/images/help/notifications/notifications_sidebar_specific_repos.png) + +### Acceder a tus notificaciones por correo electrónico + +Si tienes configuradas las notificaciones por correo electrónico, puedes acceder a tus notificaciones a través de tu cliente de correo electrónico. Para obtener más información sobre habilitar las notificaciones por correo electrónico, consulta la sección "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Elegir el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md new file mode 100644 index 0000000000000..f5f1584d50a60 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md @@ -0,0 +1,46 @@ +--- +title: Elegir el método de entrega para tus notificaciones +intro: 'Puedes recibir tus notificaciones en {% data variables.product.product_location %} o recibirlas mediante tu cliente de correo electrónico.' +versions: + enterprise-server: <2.21 +--- + +Para las cuentas personales, los correos electrónicos de notificación se envían automáticamente a tu correo electrónico de notificación predeterminado. + +{% data reusables.notifications.outbound_email_tip %} + +### Elegir el método de entrega para notificaciones sobre la actividad del repositorio + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.notifications %} +3. Configura cómo deseas recibir las notificaciones en las que participas u observas al seleccionar las casillas de verificación: + - Si seleccionas **Email** (Correo electrónico) se envía un correo electrónico a tu correo electrónico predeterminado. + - Si seleccionas **Web** podrás acceder a las notificaciones en {% data variables.product.product_location %}. ![Configurar ajustes de notificaciones](/assets/images/help/settings/ent-notifications-settings.png) +4. Si seleccionaste **Email** (Correo electrónico) para conversaciones en las que participas u observas, elige qué actualizaciones recibirás al seleccionar las casillas de verificación en la sección "Notification email" (Correo electrónico de notificación): + - Selecciona **Comments on Issues and Pull Requests** (Comentarios sobre propuestas y solicitudes de extracción) para recibir un correo electrónico cuando alguien realiza un comentario en una propuesta en la pestaña "Conversation" (Conversación) de una solicitud de extracción. + - Selecciona **Pull request reviews** (Revisiones de solicitudes de extracción) para recibir un correo electrónico cuando alguien realiza un comentario de revisión en la pestaña "Files changed" (Archivos cambiados) de una solicitud de extracción. + - Selecciona **Pull request pushes** (Impulsos de solicitud de extracción) para recibir un correo electrónico cuando alguien agrega confirmaciones a una solicitud de extracción a la que te suscribiste. + - Selecciona **Include your own updates** (Incluir tus propias actualizaciones) para recibir un correo electrónico cuando abras, comentes o cierres una propuesta o solicitud de extracción. ![Configurar opciones de notificación por correo electrónico](/assets/images/help/settings/email_notification_settings.png) + +### Elegir el método de entrega para alertas de seguridad para dependencias vulnerables + +{% data reusables.repositories.security-alert-delivery-options %} + +{% data reusables.repositories.enable-security-alerts %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.notifications %} +3. Debajo de "Alertas de seguridad", configura cómo te gustaría recibir las notificaciones cuando {% data variables.product.product_name %} detecte una dependencia vulnerable en tu repositorio: ![Opciones para configurar notificaciones para alertas de seguridad](/assets/images/help/settings/vulnerability-alerts-options.png) + - Si seleccionas **UI alerts** (Alertas de UI) muestra un mensaje emergente en la interfaz de {% data variables.product.product_name %}. + - Si seleccionas **Command Line** (Línea de comando) muestra advertencias como una devolución cuando subes a un repositorio con vulnerabilidades. + - Si seleccionas **Web** podrás acceder a las notificaciones en {% data variables.product.product_location %}. + - Si seleccionas **Email each time a vulnerabilidad is found** (Enviar un correo electrónico cada vez que se encuentra una vulnerabilidad) se envía un correo electrónico a tu correo electrónico predeterminado. + - Si seleccionas **Email a digest summary of vulnerabilities** (Enviar un correo electrónico con un resumen de vulnerabilidades) envía un correo electrónico condensado con un resumen de hasta 10 alertas de seguridad de los repositorios. Usa el menú desplegable para recibir correos electrónicos condensados diariamente o semanalmente. + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" +- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" +- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md new file mode 100644 index 0000000000000..1e6192e925efc --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md @@ -0,0 +1,8 @@ +--- +title: Comenzar con las notificaciones +intro: 'Las notificaciones te ayudan a hacer un seguimiento de las conversaciones y las actualizaciones que te interesan. Puedes recibir notificaciones en {% data variables.product.product_name %} o a través de tu cliente de correo electrónico sobre conversaciones en las que estás participando o actualizaciones que estás observando.' +mapTopic: verdadero +versions: + enterprise-server: <2.21 +--- + diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/index.md new file mode 100644 index 0000000000000..a4b7f68406ee2 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/index.md @@ -0,0 +1,23 @@ +--- +title: Recibir notificaciones acerca de la actividad en GitHub +versions: + enterprise-server: <2.21 +--- + +### Índice + +{% topic_link_in_list /getting-started-with-notifications %} + {% link_in_list /about-notifications %} + {% link_in_list /about-web-notifications %} + {% link_in_list /about-email-notifications %} + {% link_in_list /accessing-your-notifications %} + {% link_in_list /choosing-the-delivery-method-for-your-notifications %} +{% topic_link_in_list /managing-your-notifications %} + {% link_in_list /marking-notifications-as-read %} + {% link_in_list /saving-notifications-for-later %} + {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} + {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} + {% link_in_list /watching-and-unwatching-repositories %} + {% link_in_list /watching-and-unwatching-releases-for-a-repository %} + {% link_in_list /watching-and-unwatching-team-discussions %} + {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to.md new file mode 100644 index 0000000000000..e527cd33f54f9 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to.md @@ -0,0 +1,20 @@ +--- +title: Detallar las propuestas y las solicitudes de extracción a las que estás suscrito +intro: 'Puedes ver un resumen de todas las propuestas y solicitudes de extracción a las que estás suscrito. Esto simplifica la navegación hacia las conversaciones que te interesan, pero sobre las que no has recibido notificaciones recientes.' +versions: + enterprise-server: <2.21 +--- + +La lista de suscripciones no incluye todas las propuestas y solicitudes de extracción de los repositorios que estás observando. Puedes suscribirte de forma manual a una propuesta o solicitud de extracción específica para incluirla en tu lista de suscripciones. Para obtener más información consulta la sección "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" y "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)". + +### Ver una lista de tus suscripciones + +1. En la esquina superior derecha de cualquier página, haz clic en {% octicon "bell" aria-label="The notifications bell" %}. Si inhabilitaste las notificaciones web y no ves el icono de la campana, puedes navegar hasta . Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) +2. Da clic en **Suscripciones** ![Pestaña Subscriptions (Suscripciones)](/assets/images/help/notifications/subscriptions-tab.png) + +### Cancelar la suscripción desde propuestas y solicitudes de extracción + +Puedes cancelar la suscripción desde propuestas y solicitudes de extracción directamente desde tu lista de suscripciones. + +1. A la izquierda de cada propuesta o solicitud de extracción de la que quieras cancelar la suscripción, selecciona la casilla. ![Casilla para cancelar la suscripción](/assets/images/help/notifications/unsubscribe-checkbox.png) +2. En la esquina superior derecha de la página, haz clic en **Unsubscribe** (Cancelar suscripción). ![Botón Unsubscribe (Cancelar suscripción)](/assets/images/help/notifications/unsubscribe-button.png) diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md new file mode 100644 index 0000000000000..3043d7f5e6966 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md @@ -0,0 +1,17 @@ +--- +title: Detallar los repositorios que estás observando +intro: Puedes obtener un resumen de todos los repositorios que estés observando para poder eliminar fácilmente cualquiera del que ya no te interese recibir notificaciones. +versions: + enterprise-server: <2.21 +--- + +{% data reusables.notifications.access_watching %} +2. Haz clic en **Watching** (Ver) para ver la lista de repositorios que estás observando. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) +3. Da clic en **Dejar de Seguir** o en **Dejar de seguir los lanzamientos** junto al repositorio del que ya no quieras recibir notificaciones. + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" + +- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md new file mode 100644 index 0000000000000..f39203f16351d --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md @@ -0,0 +1,8 @@ +--- +title: Administrar tus notificaciones +intro: 'Para que sea más sencillo recibir las notificaciones que te interesan, puedes marcar notificaciones como leer, suscribir y cancelar la suscripción de notificaciones y ver y dejar de ver repositorios.' +mapTopic: verdadero +versions: + enterprise-server: <2.21 +--- + diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md new file mode 100644 index 0000000000000..8a464227baf9b --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md @@ -0,0 +1,37 @@ +--- +title: Marcar notificaciones como leídas +intro: 'Puedes marcar notificaciones web como leídas sin revisarlas. Si se realiza una actualización a la conversación, recibirás una nueva notificación. También puedes marcar las notificaciones leídas como no leídas, para que las puedas encontrar fácilmente despues.' +versions: + enterprise-server: <2.21 +--- + +Para obtener más información acerca de cómo acceder a tus notificaciones web, consulta "[Acceder a tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications)". + +### Marcar una notificación como leída + +{% data reusables.notifications.access_notifications %} +1. En la lista de notificaciones no leídas, encuentra la notificación que desearías marcar como leída. +1. En el lateral derecho de la notificación, haz clic en {% octicon "check" aria-label="The check symbol" %}. ![Botón para marcar una notificación única como leída](/assets/images/help/notifications/notifications_mark_individual_as_read.png) + +### Marcar una notificación como no leída + +{% data reusables.notifications.access_notifications %} +1. En la barra lateral izquierda, haz clic en **Read (Leída)**. ![Botón de todas las notificaciones](/assets/images/help/notifications/sidebar_read_notifications.png) +1. En la lista de notificaciones leídas, encuentra la notificación que desearías marcar como no leída. +1. En el lateral derecho de la notificación, haz clic en {% octicon "dot-fill" aria-label="The dot symbol" %}. ![Botón para marcar una notificación como leída](/assets/images/help/notifications/notifications_mark_individual_as_unread.png) + +### Marcar todas las notificaciones como leídas + +{% data reusables.notifications.access_notifications %} +1. En la esquina superior derecha de la página, haz clic en **Mark all as read (Marcar todas como leídas)**. ![Botón para marcar todas las notificaciones como leídas](/assets/images/help/notifications/notifications_mark_all_as_read.png) + +### Marcar todas las notificaciones de un repositorio como leídas + +{% data reusables.notifications.access_notifications %} +1. En la barra lateral izquierda, haz clic en el nombre del repositorio para el cual desearías marcar todas las notificaciones como leídas. +1. En la lista de notificaciones, en el lateral derecho del nombre del repositorio, haz clic en {% octicon "check" aria-label="The check symbol" %}. ![Botón para marcar todas las notificaciones de un repositorio como leídas](/assets/images/help/notifications/notifications_repositories_mark_all_as_read.png) + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md new file mode 100644 index 0000000000000..7e3cc9477cd67 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md @@ -0,0 +1,30 @@ +--- +title: Guardar notificaciones para más tarde +intro: Puedes guardar notificaciones web para hacerles un seguimiento posterior. +versions: + enterprise-server: <2.21 +--- + +Cuando guardas una notificación, se mueve a la pestaña Saved for later (Guardado para más tarde) en tu página de notificaciones. Para obtener más información, consulta la sección "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)". + +### Guardar una notificación para más tarde + +{% data reusables.notifications.access_notifications %} +1. En la lista de notificaciones, encuentra la notificación que deseas guardar para más tarde. +1. A lado derecho de la notificación, da clic en +{% octicon "bookmark" aria-label="The bookmark button" %}. +![Botón para guardar una notificación](/assets/images/help/notifications/save_notification.png) +{% data reusables.notifications.saved_for_late_sidebar %} + +### Eliminar una notificación guardada + +{% data reusables.notifications.access_notifications %} +{% data reusables.notifications.saved_for_late_sidebar %} +1. En tu lista de notificaciones guardadas, encuentra la notificación guardada que desearías eliminar. +1. En el lateral derecho de la notificación guardada, haz clic en {% octicon "bookmark" aria-label="The bookmark button" %}. ![Botón para eliminar una notificación guardada](/assets/images/help/notifications/remove-saved-notification.png) + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Acceder a tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications)" +- "[Marcar las notificaciones como leídas](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md new file mode 100644 index 0000000000000..768aacdc144d3 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md @@ -0,0 +1,43 @@ +--- +title: Suscribirse y cancelar las suscripciones de las notificaciones +intro: 'Puedes suscribirte a conversaciones individuales en propuestas, solicitudes de extracción y debates de equipo, incluso si no estás observando el repositorio o un miembro del equipo donde se está dando el debate. Si ya no estás interesado en una conversación, puedes cancelar la suscripción o personalizar los tipos de notificaciones que recibes.' +versions: + enterprise-server: <2.21 +--- + +### Administrar tus configuraciones de notificación para una propuesta o solicitud de extracción + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +3. Elige una propuesta o solicitud de extracción a la que suscribirte. +4. En el barra lateral derecha, haz clic en **Subscribe (Suscribirse)** o **Unsubscribe (Cancelar la suscripción)**. ![Botón para suscribirte a una conversación](/assets/images/help/notifications/subscribe_button_with_gear.png) +5. Para personalizar tus notificaciones, haz clic en {% octicon "gear" aria-label="The gear icon" %}. ![Botón de ajustes al lado de Suscribirse a una conversación](/assets/images/help/notifications/subscribe_button_with_gear_chosen.png) +6. Selecciona el tipo de notificaciones que deseas recibir de esta conversación, después haz clic en **Save (Guardar)**. ![Conversation Subscribe options list](/assets/images/help/notifications/subscribe_options.png) Puedes ver una lista de todas las propuestas y solicitudes de cambios a las cuales estás suscrito. Para obtener más información, consulta la sección "[ Listar los informes de problemas y solicitudes de extracción a los que estás suscrito](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to)". + +### Suscribirte a debates de equipo + +{% data reusables.organizations.team-discussions-are-for-orgs %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +5. En la página del equipo, encuentra el debate al que deseas suscribirte. +6. En el ángulo superior derecho del debate, haz clic en {% octicon "unmute" aria-label="The subscribe symbol" %} para suscribirte al debate. ![Botón para suscribirse a un debate de equipo](/assets/images/help/notifications/team-discussion-subscribe-button.png) + +### Cancelar la suscripción a debates de equipo + +{% data reusables.organizations.team-discussions-are-for-orgs %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +5. En la página del equipo, encuentra el debate del que deseas cancelar la suscripción. +6. En el ángulo superior derecho del debate, haz clic en {% octicon "mute" aria-label="The unsubscribe symbol" %} para cancelar la suscripción al debate. ![Botón para suscribirse a un debate de equipo](/assets/images/help/notifications/team-discussion-unsubscribe-button.png) + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Acerca de los debates en {% data variables.product.product_name %}](/articles/about-conversations-on-github)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" + +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md new file mode 100644 index 0000000000000..7e27d9655fd30 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md @@ -0,0 +1,23 @@ +--- +title: Ver y dejar de ver los lanzamientos de un repositorio +intro: Puedes ver lanzamientos en un repositorio para recibir notificaciones cuando un nuevo lanzamiento se publica sin recibir notificaciones sobre otras actualizaciones en el repositorio. También puedes dejar de ver lanzamientos si ya no deseas recibir notificaciones de nuevos lanzamientos en un repositorio. +versions: + enterprise-server: <2.21 +--- + +### Ver lanzamientos en un repositorio + +{% data reusables.repositories.navigate-to-repo %} +2. En el ángulo superior derecho, haz clic en **Releases only (Solo lanzamientos)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para lanzamientos](/assets/images/help/notifications/watch-releases.png) + +### Dejar de ver lanzamientos en un repositorio + +{% data reusables.repositories.navigate-to-repo %} +2. En el ángulo superior derecho, haz clic en **Not watching (Dejar de ver)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para lanzamientos](/assets/images/help/notifications/unwatch-repository.png) + +### Further reading + +- "[Acerca de los lanzamientos](/articles/about-releases)" +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" + diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md new file mode 100644 index 0000000000000..adf23fb6f81fc --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md @@ -0,0 +1,43 @@ +--- +title: Ver y dejar de ver repositorios +intro: Puedes ver un repositorio para recibir notificaciones por las nuevas solicitudes de extracción y propuestas que se crearon. También puedes dejar de ver un repositorio si ya no deseas recibir notificaciones de ese repositorio específico. +versions: + enterprise-server: <2.21 +--- + +{% data reusables.notifications.auto-watch %} Para obtener más información, consulta la sección "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". + +También puedes observar y dejar de observar los lanzamientos en un repositorio. Para obtener más información, consulta la sección "[Observar y dejar de observar los lanzamientos para un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository)". + +### Ver todos los repositorios a los que tienes acceso de escritura + +{% data reusables.notifications.access_watching %} +2. Da clic en **Observando**. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) +3. En el lateral derecho de la página, selecciona **Automatically watch (Ver automáticamente)**. ![Una casilla de verificación para configurar ver automáticamente repositorios](/assets/images/help/notifications/ent-automatically-watch-repos.png) + +### Ver un repositorio único + +{% data reusables.repositories.navigate-to-repo %} +2. En el ángulo superior derecho, haz clic en **Watching (Ver)** del menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications/watch-repository.png) + +### Dejar de ver todos los repositorios a los que tienes acceso de escritura + +{% data reusables.notifications.access_watching %} +2. Da clic en **Observando**. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) +3. En el lateral derecho de la página, deselecciona **Automatically watch (Ver automáticamente)**. ![Una casilla de verificación para configurar ver automáticamente repositorios](/assets/images/help/notifications/ent-automatically-watch-repos.png) + +### Dejar de ver un repositorio único + +{% data reusables.repositories.navigate-to-repo %} +2. En el ángulo superior derecho, haz clic en **Unwatch (Dejar de ver)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications/unwatch-repository.png) + +{% note %} + +**Nota:** también puedes elegir ignorar un repositorio. Si ignoras un repositorio, no recibirás ninguna notificación. No recomendamos ignorar repositorios ya que no se te notificará si eres mencionado. {% if currentVersion == "free-pro-team@latest" %}Si te encuentras con algún tipo de abuso y quieres ignorar un repositorio, por favor, contacta a {% data variables.contact.contact_support %} para que te podamos ayudar. {% data reusables.policies.abuse %}{% endif %} + +{% endnote %} + +### Further reading + +- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" +- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md new file mode 100644 index 0000000000000..d71c61a2a8dd3 --- /dev/null +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md @@ -0,0 +1,62 @@ +--- +title: Ver y dejar de ver debates de equipo +intro: Puedes ver un equipo para recibir notificaciones de los debates del equipo. Puedes dejar de ver un equipo si ya no quieres recibir notificaciones de los debates de ese equipo. +versions: + enterprise-server: <2.21 +--- + +Por defecto, recibirás automáticamente notificaciones de los debates del equipo del que eres miembros. Si no quieres recibir determinadas notificaciones para un debate de equipo existente, debes dejar de ver ese equipo. También puedes cancelar la suscripción o suscribirte a publicaciones de debates de equipo específicas. Para obtener más información, consulta la sección "[Acerca de los debates de equipo](/articles/about-team-discussions)" y "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)." + +Si no deseas ver automáticamente debates de equipo cuando te conviertes en miembro de equipos nuevos, puedes actualizar tus configuraciones automáticas de observación. + +### Ver los debates de todos los equipos nuevos a los que te unes + +Para ver automáticamente todos los debates de los equipos nuevos a los que te unes, configura tus parámetros de notificaciones automáticas de observación. + +{% note %} + +**Nota:** por defecto, esta configuración se realiza para **Automatically watching teams (Ver automáticamente equipos)**. + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.notifications %} +{% data reusables.user_settings.automatic_watching_box %} selecciona **Automatically watch teams** (Ver equipos automáticamente). +![Casilla de verificación para ver automáticamente equipos](/assets/images/help/notifications/automatic-team-discussions-watching.png) + +### Ver debates de un equipo único + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.watch-team-options %} haz clic en **Watch** (Ver) para abrir tus opciones de notificaciones. Después haz clic en **Watching (Ver)**. +![Ver opciones en un menú desplegable para un equipo específico](/assets/images/help/notifications/specific-team-watch-options.png) + +### Dejar de ver los debates de todos los equipos nuevos a los que te unes + +Si no deseas recibir de forma automática las notificaciones de debates de equipo cuando te unes a un equipo, puedes cambiar tus configuraciones de notificación para dejar de ver todos los nuevos equipos a los que te unes. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.notifications %} +{% data reusables.user_settings.automatic_watching_box %} anula la selección de **Automatically watch teams** (Ver equipos automáticamente). +![Configuración para ver automáticamente equipos seleccionada por defecto](/assets/images/help/notifications/automatic-team-discussions-watching.png) + +### Dejar de ver debates de un equipo único + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.watch-team-options %} haz clic en **Unwatch** (Dejar de ver) para abrir tus opciones de notificaciones. Después haz clic en **Not watching (No ver)**. +![Ver opciones en un menú desplegable para un equipo específico](/assets/images/help/notifications/specific-team-unwatch.png) + +{% note %} + +**Nota:** también puedes elegir ignorar las notificaciones de un equipo. Si ignoras un equipo, no recibirás ninguna notificación. No recomendamos ignorar equipos ya que no se te notificará si eres mencionado. + +{% endnote %} + +### Further reading + +- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" +- "[Acerca de los debates del equipo](/articles/about-team-discussions)" +- [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md new file mode 100644 index 0000000000000..768f15d728930 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -0,0 +1,76 @@ +--- +title: Acerca de la búsqueda en GitHub +intro: 'Nuestra búsqueda integrada cubre los diversos repositorios, usuarios y líneas de código en {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.search.you-can-search-globally %} + +- Para hacer una búsqueda global en todo {% data variables.product.product_name %}, escribe lo que estás buscando en el campo de búsqueda en la parte superior de cualquier página y elige "Todo {% data variables.product.prodname_dotcom %}" en el menú de búsqueda desplegable. +- Para buscar dentro de un repositorio o una organización en particular, navega a la página del repositorio o de la organización, escribe lo que estás buscando en el campo de búsqueda en la parte superior de la página y presiona **Aceptar**. + +{% note %} + +**Notas:** + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- {% data reusables.search.required_login %}{% endif %} +- Los sitios {% data variables.product.prodname_pages %} no se pueden buscar en {% data variables.product.product_name %}. Sin embargo, puedes buscar el contenido fuente si existe en la rama por defecto de un repositorio, usando la búsqueda de código. Para obtener más información, consulta "[Código de búsqueda](/articles/searching-code)". Para obtener más información acerca de {% data variables.product.prodname_pages %}, consulta "[¿Qué son las Páginas de GitHub?](/articles/what-is-github-pages/)" +- Actualmente, nuestra búsqueda no es compatible con las coincidencias exactas. +- Cuando estés buscando dentro de archivos de código, únicamente se devolverán los primeros dos resultados de cada archivo. + +{% endnote %} + +Después de ejecutar una búsqueda en {% data variables.product.product_name %}, puedes clasificar los resultados o refinarlos más haciendo clic en uno de los idiomas de la barra lateral. Para obtener más información, consulta "[Clasificar los resultados de búsqueda](/articles/sorting-search-results)". + +La búsqueda de {% data variables.product.product_name %} usa una agrupación ElasticSearch para indexar los proyectos cada vez que se sube un cambio a {% data variables.product.product_name %}. Las propuestas y las solicitudes de extracción son indexadas cuando son creadas o modificadas. + +### Tipos de búsquedas en {% data variables.product.prodname_dotcom %} + +Puedes buscar la siguiente información a través de todos los repositorios a los que puedes acceder en {% data variables.product.product_location %}. + +- [Repositorios](/articles/searching-for-repositories) +- [Temas](/articles/searching-topics) +- [propuestas y solicitudes de cambios](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Debates](/github/searching-for-information-on-github/searching-discussions){% endif %} +- [Código](/articles/searching-code) +- [Confirmaciones](/articles/searching-commits) +- [Usuarios](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} +- [Paquetes](/github/searching-for-information-on-github/searching-for-packages){% endif %} +- [Wikis](/articles/searching-wikis) + +### Buscar usando una interfaz visual + +Alternativamente, puedes buscar {% data variables.product.product_name %} usando {% data variables.search.search_page_url %} o {% data variables.search.advanced_url %}. + +{% data variables.search.advanced_url %} ofrece una interfaz visual para construir consultas de búsqueda. Puedes filtrar tus búsquedas por diferentes factores, como la cantidad de estrellas o la cantidad de bifurcaciones que tiene un repositorio. A medida que completas los campos de búsqueda de avanzada, tu consulta se construirá automáticamente en la barra de búsqueda superior. + +![Búsqueda avanzada](/assets/images/help/search/advanced_search_demo.gif) + +{% if currentVersion != "github-ae@latest" %} +### Buscar en todo {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_dotcom_the_website %} simultáneamente + +Si usas {% data variables.product.prodname_enterprise %} y eres miembro de una organización de {% data variables.product.prodname_dotcom_the_website %} que usa {% data variables.product.prodname_ghe_cloud %}, tu administrador del sitio {% data variables.product.prodname_enterprise %} puede activar {% data variables.product.prodname_github_connect %} para que puedas buscar en ambos entornos al mismo tiempo. Para obtener más información, consulta "[Activar {% data variables.product.prodname_unified_search %} entre {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com)". + +También solo puedes buscar en ambos entornos desde {% data variables.product.prodname_enterprise %}. Para limitar tu búsqueda por entorno, puedes usar una opción de filtro en {% data variables.search.advanced_url %} o puedes usar el prefijo de búsqueda `environment:`. Para solo buscar contenido en {% data variables.product.prodname_enterprise %}, usa la sintaxis de búsqueda `environment:local`. Para solo buscar contenido en {% data variables.product.prodname_dotcom_the_website %}, usa la sintaxis de búsqueda `environment:github`. + +El administrador de tu sitio {% data variables.product.prodname_enterprise %} puede activar {% data variables.product.prodname_unified_search %} para todos los repositorios públicos, todos los repositorios privados o solo ciertos repositorios privados en la organización de {% data variables.product.prodname_ghe_cloud %} conectada. +Si tu administrador de sitio habilita + +la {% data variables.product.prodname_unified_search %} en los repositorios privados, solo podrás hacer búsquedas en los repositorios privados para los cuales el administrador haya habilitado la {% data variables.product.prodname_unified_search %} y a los cuales tengas acceso en la organización de {% data variables.product.prodname_dotcom_the_website %} conectada. Los administradores de {% data variables.product.prodname_enterprise %} y los propietarios de la organización en {% data variables.product.prodname_dotcom_the_website %} no pueden buscar en repositorios privados que son propiedad de tu cuenta. Para buscar los repositorios privados aplicables, debes activar la búsqueda de repositorio privado para tus cuentas personales en {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Activar la búsqueda de repositorio privado de {% data variables.product.prodname_dotcom_the_website %} en tu cuenta de {% data variables.product.prodname_enterprise %} account](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)". +{% endif %} + +### Further reading + +- "[Comprender la sintaxis de búsqueda](/articles/understanding-the-search-syntax)" +- "[Búsqueda en GitHub](/articles/searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md b/translations/es-ES/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md new file mode 100644 index 0000000000000..0e5598670496e --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md @@ -0,0 +1,22 @@ +--- +title: Habilitar la búsqueda de repositorios de GitHub.com en tu cuenta de servidor de GitHub Enterprise +intro: 'Puedes conectar tus cuentas personales para {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.prodname_ghe_server %} a fin de buscar contenido en determinados repositorios privados de {% data variables.product.prodname_dotcom_the_website %} de {% data variables.product.prodname_ghe_server %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-githubcom-repository-search-in-github-enterprise-server +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Si usas {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} tu administrador del sitio {% data variables.product.prodname_ghe_server %} ha habilitado {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %} para repositorios privados, podrás buscar repositorios privados designados en la organización conectada. + +Para ver los repositorios privados en tus resultados de búsqueda, ya debes tener acceso a esos repositorios y debes conectar tus cuentas {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información acerca de los repositorios en los que puedes buscar, consulta "[Buscar en {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} simultáneamente](/articles/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)". + +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.github-connect.access-profile-settings %} +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} diff --git a/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md new file mode 100644 index 0000000000000..aa1fc669bb046 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md @@ -0,0 +1,33 @@ +--- +title: Buscar archivos en GitHub +intro: 'Puedes buscar un archivo en un repositorio utilizando el buscador de archivos. Para buscar un archivo en distintos repositorios en {% data variables.product.product_name %}, usa el [calificados de búsqueda de código`filename`](/articles/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Tips:** + +- Los resultados del buscador de archivos excluyen algunos directorios como `build`, `log`, `tmp` y `vendor`. Para buscar archivos dentro de estos directorios, usa el [calificador de búsqueda de código `filename`](/articles/searching-code#search-by-filename). +- También puedes abrir el buscador de archivos presionando `t` en tu teclado. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#comments)". + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +{% if currentVersion ver_lt "enterprise-server@2.22" %} +2. Debajo del nombre del repositorio, haz clic en **Buscar archivo**. ![Botón Buscar archivo](/assets/images/help/search/find-file-button.png) +{% else %} +2. Sobre la lista de archivos, da clic en **Ir al archivo**. ![Botón Buscar archivo](/assets/images/help/search/find-file-button.png) +{% endif %} +3. En el campo de búsqueda, escribe el nombre del archivo que deseas buscar. ![Campo de búsqueda Buscar archivo](/assets/images/help/search/find-file-search-field.png) +4. En la lista de resultados, haz clic en el archivo que deseas buscar. + +### Further reading + +- "[Acerca de buscar en GitHub](/articles/about-searching-on-github)" + diff --git a/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md new file mode 100644 index 0000000000000..bfcea12d255df --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md @@ -0,0 +1,11 @@ +--- +title: Comenzar con la búsqueda en GitHub +mapTopic: verdadero +redirect_from: + - /articles/getting-started-with-searching-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/searching-for-information-on-github/index.md b/translations/es-ES/content/github/searching-for-information-on-github/index.md new file mode 100644 index 0000000000000..be30a7b2f16c6 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/index.md @@ -0,0 +1,34 @@ +--- +title: Buscar información en GitHub +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /getting-started-with-searching-on-github %} + {% link_in_list /about-searching-on-github %} + {% link_in_list /understanding-the-search-syntax %} + {% link_in_list /troubleshooting-search-queries %} + {% link_in_list /sorting-search-results %} + {% link_in_list /enabling-githubcom-repository-search-in-github-enterprise-server %} +{% topic_link_in_list /searching-on-github %} + {% link_in_list /finding-files-on-github %} + {% link_in_list /searching-for-repositories %} + {% link_in_list /searching-topics %} + {% link_in_list /searching-code %} + {% link_in_list /searching-commits %} + {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} + {% link_in_list /searching-github-marketplace %}{% endif %} + {% link_in_list /searching-users %} + {% link_in_list /searching-for-packages %} + {% link_in_list /searching-wikis %} + {% link_in_list /searching-in-forks %} diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md new file mode 100644 index 0000000000000..1b8eb9ee1a6be --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md @@ -0,0 +1,107 @@ +--- +title: Buscar código +intro: 'Puedes buscar código en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de código en cualquier combinación.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.search.you-can-search-globally %} Para obtener más información, consulta la sección "[Acerca de buscar en GitHub](/articles/about-searching-on-github)". + +Únicamente puedes buscar código utilizando estos calificadores de búsqueda de código. Los calificadores de búsqueda especialmente para repositorios, usuarios o confirmaciones de cambios, no funcionarán cuando busques código. + +{% data reusables.search.syntax_tips %} + +### Consideraciones sobre la búsqueda de código + +Debido a la complejidad de la búsqueda de código, hay algunas restricciones sobre cómo se realizan las búsquedas: + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- {% data reusables.search.required_login %}{% endif %} +- El código en [bifurcaciones](/articles/about-forks) es únicamente indexado si la bifurcación tiene más estrellas que el repositorio padre. Las bifurcaciones con menos estrellas que el repositorio padre **no** son indexadas para la búsqueda de código. Para incluir bifurcaciones con más estrellas que sus padres en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/articles/searching-in-forks)". +- Únicamente se indiza la _rama predeterminada_ para la búsqueda de código.{% if currentVersion == "free-pro-team@latest" %} +- Solo los archivos menores de 384 KB son indexados.{% else %}* Solo los archivos menores de 5 MB son indexados. +- Solo los primeros 500 KB de cada archivo son indexados.{% endif %} +- Solo se pueden hacer búsquedas en los repositorios con menos de 500,000 archivos.{% if currentVersion == "free-pro-team@latest" %} +- Solo se pueden hacer búsquedas en los repositorios que han tenido actividad o que se han devuelto en los resultados de búsqueda dentro del último año.{% endif %} +- Excepto con las búsquedas por [`nombre de archivo`](#search-by-filename), siempre debes incluir por lo menos un término de búsqueda cuando buscas el código fuente. Por ejemplo, no es válido buscar por [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults), mientras que sí los es por [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults). +- A lo sumo, los resultados de búsqueda pueden mostrar dos fragmentos del mismo archivo, pero puede haber más resultados dentro del archivo. +- No puedes utilizar los siguientes caracteres comodines como parte de la consulta de búsqueda: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]. La búsqueda simplemente ignorará estos símbolos. + +### Buscar según los contenidos del archivo o la ruta de archivo + +Con el calificador `in` puedes restringir tu búsqueda a los contenidos del archivo del código fuente, de la ruta del archivo, o de ambos. Cuando omites este calificador, únicamente se busca el contenido del archivo. + +| Qualifier | Ejemplo | +| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) encuentra el código donde aparece "octocat" en la ruta del archivo. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo o la ruta del archivo. | + +### Buscar dentro de los repositorios de un usuario u organización + +Para buscar el código en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`. Para buscar el código en un repositorio específico, puedes utilizar el calificador `repo`. + +| Qualifier | Ejemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) encuentra el código de @defunkt que termina en .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) encuentra el código de GitHub que termina en .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) encuentra el código del proyecto shumway de @mozilla que termina en .as. | + +### Buscar por ubicación del archivo + +Puedes utilizar el calificador `path` (ruta) para buscar el código fuente que aparece en una ubicación específica en un repositorio. Utiliza `path:/` para buscar archivos que estén ubicados a nivel de la raíz de un repositorio. O especifica un nombre de directorio o ruta a un directorio para buscar archivos que estén ubicados dentro de ese directorio o alguno de sus subdirectorios. + +| Qualifier | Ejemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) encuentra los archivos _readme_ con la palabra "octocat" que se encuentran al nivel de raíz de un repositorio. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) encuentra los archivos Perl con la palabra "form" en un directorio cgi-bin o en cualquiera de sus subdirectorios. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) encuentra los archivos JavaScript con la palabra "console" en un directorio app/public o en cualquiera de sus subdirectorios (incluso si se encuentran en app/public/js/form-validators). | + +### Buscar por lenguaje + +Puedes buscar el código basado en el lenguaje en que está escrito. + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) encuentra código con la palabra "element" que está marcada como XML y tiene exactamente 100 bytes. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) encuentra código con la palabra "display," que está marcada como SCSS. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) encuentra código de todos los repositorios de @mozilla que están marcados como Markdown. | + +### Buscar por tamaño de archivo + +Puedes utilizar el calificador `size` (tamaño) para buscar código fuente en base al tamaño del archivo donde existe el código. El calificador `size` utiliza [calificadores mayor que, menor que y rango](/articles/understanding-the-search-syntax) para filtrar resultados en base al tamaño de bytes del archivo en donde se encuentra el código. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) encuentra código con la palabra "function," escrita en Python, en archivos que son mayores a 10 KB. | + +### Buscar por nombre de archivo + +El calificador `filename` (nombre de archivo) encuentra archivos de código con un determinado nombre de archivo. También puedes encontrar un archivo en un repositorio utilizando el buscador de archivo. Para obtener más información, consulta "[Encontrar archivos en GitHub](/articles/finding-files-on-github)." + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) encuentra archivos con el nombre de "linguist." | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) encuentra los archivos *.vimrc* con la palabra "commands". | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) encuentra archivos Ruby con el nombre *test_helper* dentro del directorio *test*. | + +### Buscar por extensión de archivo + +El calificador `extension` (extensión) encuentra archivos de código con una determinada extensión de archivo. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) encuentra el código con la palabra "form", debajo de cgi-bin, con la extensión de archivo .pm. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) busca archivos más grandes de 200 KB que terminan en .css y tienen la palabra "icon". | + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" +- "[Buscar en las bifurcaciones](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %} +- "[Navegar en el código de {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md new file mode 100644 index 0000000000000..10ca313fb01b2 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md @@ -0,0 +1,107 @@ +--- +title: Buscar confirmaciones de cambios +intro: 'Puedes buscar confirmaciones de cambios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de confirmaciones con cualquier combinación.' +redirect_from: + - /articles/searching-commits +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar confirmaciones de cambios globalmente a través de todos los {% data variables.product.product_name %}, o buscar confirmaciones de cambios dentro de un repositorio particular u organización. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". + +Cuando buscas confirmaciones de cambios, se busca únicamente la [rama predeterminada](/articles/about-branches) de un repositorio. + +{% data reusables.search.syntax_tips %} + +### Buscar dentro de los mensajes de confirmación + +Puedes encontrar confirmaciones que contengan determinadas palabras en el mensaje. Por ejemplo, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) encuentra las confirmaciones que contienen las palabras "fix" y "typo." + +### Buscar por el autor o la persona que confirma el cambio + +Puedes encontrar confirmaciones de cambios por un usuario particular con los calificadores `author` (autor) o `committer` (persona que confirma el cambio). + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) encuentra confirmaciones cuya autoría corresponde a @defunkt. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) encuentra confirmaciones de @defunkt. | + +Los calificadores `author-name` y `committer-name` encuentran confirmaciones por el nombre de su autor o de la persona que confirma el cambio. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de autor. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de la persona que confirma el cambio. | + +Los calificadores `author-email` y `committer-email` encuentran confirmaciones por la dirección completa de correo electrónico del autor o de la persona que confirma el cambio. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) encuentra confirmaciones cuyo autor es chris@github.com. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) encuentra confirmaciones de chris@github.com. | + +### Buscar por fecha de autoría o de confirmación + +Utiliza los calificadores `author-date` y `committer-date` para encontrar confirmaciones que fueron creadas o confirmadas dentro de un rango de fechas especificado. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) encuentra confirmaciones creadas antes del 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | + +### Filtrar confirmaciones de fusión + +Los filtros del calificador `merge` de confirmación de fusión. + +| Qualifier | Ejemplo | +| ------------- | ---------------------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) encuentra confirmaciones de fusión. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) encuentra confirmaciones de no fusión. | + +### Filtrar por hash + +El calificador `hash` encuentra confirmaciones con el hash SHA-1 especificado. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) encuentra confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +### Filtrar por padre + +El calificador `parent` (padre) encuentra confirmaciones cuyo padre tiene el hash SHA-1 especificado. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) encuentra el hijo de las confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +### Filtrar por árbol + +El calificador `tree` (árbol) encuentra confirmaciones con el hash de árbol de git SHA-1 especificado. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) encuentra confirmaciones que se refieren al hash del árbol `99ca967`. | + +### Buscar dentro de los repositorios de un usuario u organización + +Para buscar confirmaciones en todos los repositorios que son propiedad de una determinada organización o usuario, utiliza el calificador `user` (usuario) u `org` (organización). Para buscar confirmaciones en un repositorio específico, utiliza el calificador `repo`. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) encuentra mensajes de confirmación con la palabra "gibberish" en repositorios propiedad de @defunkt. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) encuentra mensajes de confirmación con la palabra "test" en repositorios propiedad de @github. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) encuentra mensajes de confirmación con la palabra "language" en un repositorio "gibberish" de @defunkt. | + +### Filtrar por visibilidad de repositorio + +El calificador `is` coincide con las confirmaciones de los repositorios con la visibilidad especificada. para obtener más información, consulta "[Acerca de la visibilidad en los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility). + +| Calificador| Ejemplo | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) coincide con las confirmaciones de los repositorios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) coincide con las confirmaciones de los repositorios internos. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) coincide con las confirmaciones de los repositorios privados. + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000000..8585bb03e4596 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Buscar debates +intro: Puedes buscar debates en {% data variables.product.product_name %} y reducir los resultados utilizando calificadores. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Acerca de buscar debates + +Puedes buscar debates globalmente a través de todo {% data variables.product.product_name %}, o buscar debates dentro de una organización o repositorio específicos. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +### Buscar por título, cuerpo o comentarios + +Puedes restringir la búsqueda de debates al título, cuerpo o comentarios si utilizas el calificador `in`. También puedes combinar los calificadores para buscar una combinación de título, cuerpo o comentarios. Cuando omites el calificador `in`, {% data variables.product.product_name %} busca el título, cuerpo y comentarios. + +| Qualifier | Ejemplo | +|:------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) coincide con los debates que tengan "welcome" en el título. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) coincide con los debates que tengan "onboard" en el título o en el cuerpo. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) coincide con los debates que tengan "thanks" en sus comentarios. | + +### Buscar dentro de los repositorios de un usuario u organización + +Para buscar los debates en todos los repositorios que pertenezcan a algún usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar los debates en un repositorio específico, puedes utilizar el calificador `repo`. + +| Qualifier | Ejemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) coincide con debates con la palabra "retroalimentación" de los repositorios que pertenezcan a @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) coincide con los debates en los repositorios que pertenezcan a la organización GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) coincide con los debates del proyecto de tiempo de ejecución de Node.js de @nodejs que se crearon antes de enero de 2021. | + +### Filtrar por visibilidad de repositorio + +Puedes filtrar los resultados por la visibilidad del repositorio que contenga los debates que utilicen el calificador `is`. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +| Calificador| Ejemplo | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) coincide con los debates en los repositorios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) coincide con los debates en los repositorios internos. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) coincide con los debates que contiene la palabra "tiramisu" en los repositorios privados a los que puedes acceder. + +### Buscar por autor + +El calificador `author` encuentra debates crean usuarios específicos. + +| Qualifier | Ejemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) coincide con debates que tienen la palabra "cool" y que creó @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) coincide con debates que creó @octocat y que contienen la palabra "bootstrap" enel cuerpo. | + +### Buscar por comentarista + +El calificador `commenter` encuentra debates que contienen un comentario de un usuario específico. + +| Qualifier | Ejemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) coincide con debates en los repositorios que pertenecen a GitHub, los cuales contengan la palabra "github" y un comentario de @becca. | + +### Buscar por un usuario que está involucrado en un debate + +Puedes utilizar el calificador `involves` para encontrar debates que involucren a algún usuario. El calificador devuelve los debates que un usuario haya creado, que mencionen al usuario, o que contengan sus comentarios. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `mentions`, y `commenter` para un usuario único. + +| Qualifier | Ejemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** coincide con debates en los que se involucre ya sea a @becca o a @octocat. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) coincide con debates en los que se involucre a @becca, en los cuales no se contenga la palabra "beta" dentro del cuerpo. | + +### Buscar por cantidad de comentarios + +Puedes utilizar el calificador `comments` junto con los calificadores de mayor que, menor que y de rango para buscar por cantidad de comentarios. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) coincide con debates de más de 100 comentarios. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) coincide con debates que tengan entre 500 y 1,000 comentarios. | + +### Buscar por cantidad de interacciones + +Puedes filtrar debates por el número de interacciones con el calificador `interactions` junto con los calificadores de mayor qué, menor qué y de rango. El conteo de interacciones es la cantidad de reacciones y comentarios en un debate. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) coincide con los debates de más de 2,000 interacciones. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) coincide con los debates que tengan entre 500 y 1,000 interacciones. | + +### Buscar por cantidad de reacciones + +Puedes filtrar los debates de acuerdo con la cantidad de reacciones si utilizas el calificador `reactions` junto con los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) coincide con debates con más de 500 reacciones. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) coincide con los debtes que tengan entre 500 y 1,000 reacciones. | + +### Buscar por cuándo se creó o actualizó por última vez un debate + +Puedes filtrar los debates con base en las fechas de creación o por cuándo se actualizaron por última vez. Para la creación de debates, puedes utilizar el calificador `created`; para saber cuándo se actualizó por última vez el debate, utiliza el calificador `updated`. + +Ambos calificadores toman la fecha como parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +|:-------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) coincide con debates que se crearon después del 15 de noviembre de 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) coincide con debates que tengan la palabra "weird" en el cuerpo y que se hayan actualizado después de diciembre de 2020. | + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-for-packages.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-packages.md new file mode 100644 index 0000000000000..015e7e5301311 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-packages.md @@ -0,0 +1,41 @@ +--- +title: Buscar paquetes +intro: 'Puedes buscar paquetes en {% data variables.product.product_name %} y acotar los resultados utilizando los calificadores de búsqueda.' +product: '{% data reusables.gated-features.packages %}' +permissions: Cualquiera puede buscar paquetes a los que tengan acceso. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Acerca de la búsqueda de paquetes + +Puedes buscar paquetes globalmente a través de todo {% data variables.product.product_name %}, o buscarlos dentro de una organización en particular. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github)". + +{% if enterpriseServerVersions contains currentVersion %} +Solo puedes buscar paquetes en +{% data variables.product.product_name %}, no en {% data variables.product.prodname_dotcom_the_website %}, aún si habilitas {% data variables.product.prodname_github_connect %}. +{% endif %} + +{% data reusables.search.syntax_tips %} + +### Buscar dentro de los paquetes de una organización o usuario + +Para encontrar paquetes que sean propiedad de cierto usuario u organización, utiliza el calificador `user` u `org`. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) coincidirá con paquetes que sean propiedad de @codertocat | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) coincidirá con paquetes que sean propiedad de la organización {% data variables.product.prodname_dotcom %} + +### Filtrar por visibilidad del paquete + +Para filtrar tu búsqueda por el criterio de si el paquete es público o privado, utiliza el calificador `is`. + +| Qualifier | Ejemplo | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) coincidirá con los paquetes públicos que contengan la palabra "angular" | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) coincidirá con los paquetes privados que contengan la palabra "php" | diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md new file mode 100644 index 0000000000000..e8a975b653805 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md @@ -0,0 +1,185 @@ +--- +title: Buscar repositorios +intro: 'Puedes buscar repositorios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de repositorio en cualquier combinación.' +redirect_from: + - /articles/searching-for-repositories + - /articles/searching-for-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar repositorios globalmente a través de todos los {% data variables.product.product_location %}, o buscar repositorios dentro de una organización particular. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github)". + +Para incluir bifurcaciones en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/articles/searching-in-forks)". + +{% data reusables.search.syntax_tips %} + +### Buscar por nombre de repositorio, descripción o contenidos del archivo README + +Con el calificador `in` puedes restringir tu búsqueda al nombre del repositorio, su descripción, los contenidos del archivo README, o cualquier combinación de estos. Cuando omites este calificador, únicamente se buscan el nombre del repositorio y la descripción. + +| Qualifier | Ejemplo | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) coincide con repositorios que tengan "jquery" en su nombre. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) coincide con repositorios que tengan "jquary" en su nombre o descripción. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "jquery" en su archivo README. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) encuentra un nombre de repositorio específico. | + +### Buscar en base a los contenidos de un repositorio + +Puedes encontrar un repositorio si buscas el contenido de su archivo README utilizando el calificador `in:readme`. Para obtener más información, consulta "[Acerca de los README](/github/creating-cloning-and-archiving-repositories/about-readmes)". + +Además de utilizar `in:readme`, no es posible encontrar repositorios al buscar por el contenido específico dentro del repositorio. Para buscar un archivo o contenido específico dentro de un repositorio, puedes utilizar el buscador de archivo o los calificadores de búsqueda específica. Para obtener más información, consulta "[Encontrar archivos en {% data variables.product.prodname_dotcom %}](/articles/finding-files-on-github)" y "[Buscar código](/articles/searching-code)." + +| Qualifier | Ejemplo | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "octocat" en su archivo README. | + +### Buscar dentro de los repositorios de un usuario u organización + +Para buscar en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`. + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) encuentra repositorios de @defunkt que tienen más de 100 bifurcaciones. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) encuentra repositorios de GitHub. | + +### Buscar por tamaño del repositorio + +El calificador `size` encuentra repositorios que coinciden con un tamaño determinado (en kilobytes), utilizando los calificadores de mayor que, menor que y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) encuentra repositorios que tienen más de 1 MB con exactitud. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) encuentra repositorios que tienen por lo menos 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) encuentra repositorios que son menores de 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) encuentra repositorios que están entre 50 KB y 120 KB. | + +### Buscar por cantidad de seguidores + +Puedes filtrar los repositorios con base en la cantidad de usuarios que los siguen, utilizando el calificador `followers` con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) coincidirá con repositorios que tengan 10,000 o más seguidores y en donde se mencione la palabra "node". | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) encuentra repositorios con 1 a 10 seguidores, que mencionan la palabra "styleguide linter." | + +### Buscar por cantidad de bifurcaciones + +El calificador `forks` especifica la cantidad de bifurcaciones que un repositorio debería tener, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) encuentra repositorios con solo cinco bifurcaciones. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) encuentra repositorios con por lo menos 205 bifurcaciones. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) encuentra repositorios con menos de 90 bifurcaciones. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) encuentra repositorios con 10 a 20 bifurcaciones. | + +### Buscar por cantidad de estrellas + +Puedes buscar repositorios con base en la cantidad de estrellas que tienen, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Guardar los repositorios con estrellas](/github/getting-started-with-github/saving-repositories-with-stars)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) encuentra repositorios con exactamente 500 estrellas. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) encuentra repositorios con 10 a 20 estrellas, que son menores que 1000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) encuentra repositorios con al menos 500 estrellas, incluidas los bifurcados, que están escritos en PHP. | + +### Buscar por cuándo fue creado o actualizado por última vez un repositorio + +Puedes filtrar repositorios en base al momento de creación o al momento de la última actualización. Para la creación de un repositorio, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). El calificador `pushed` devolverá una lista de repositorios, clasificados por la confirmación más reciente realizada en alguna rama en el repositorio. + +Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) encuentra repositorios con la palabra "webos" que fueron creados antes del 2011. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) encuentra repositorios con la palabra "css" que fueron subidos después de enero de 2013. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) encuentra repositorios con la palabra "case" que fueron subidos el 6 de marzo de 2013 o después, y que son bifurcaciones. | + +### Buscar por lenguaje + +Puedes buscar repositorios con base en el lenguaje de programación del código que contienen. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) encuentra repositorios con la palabra "rails" que están escritos en JavaScript. | + +### Buscar por tema + +Puedes encontrar todos los repositorios que se clasifiquen con un tema particular. Para obtener más información, consulta "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)". + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) encuentra repositorios que se han clasificado con el tema "jekyll." | + +### Buscar por cantidad de temas + +Puedes buscar repositorios por la cantidad de temas que se les hayan aplicado utilizando el calificador `topics` en conjunto con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) encuentra repositorios que tienen cinco temas. | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) coincidirá con repositorios que tengan más de tres temas. | + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +### Buscar por licencia + +Puedes buscar repositorios con por su tipo de licencia. Debes utilizar una palabra clave de licencia para filtrar los repositorios por algún tipo particular o familia de licencias. Para obtener más información, consulta "[Licenciar un repositorio](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)". + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) encuentra repositorios que tienen licencia de Apache License 2.0. | + +{% endif %} + +### Buscar por visibilidad del repositorio + +Puedes filtrar tu búsqueda con base en la visibilidad de los repositorios. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +| Calificador| Ejemplo | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) coincide con los repositorios públicos que pertenezcan a {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) coincide con los repositorios internos a los que puedas acceder y que contengan la palabra "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) coincide con los repositorios privados a los cuales puedes acceder y que contengan la palabra "pages". + +{% if currentVersion == "free-pro-team@latest" %} + +### Buscar en base a si un repositorio es un espejo + +Puedes buscar repositorios con base en si éstos son espejos y se hospedan en otro lugar. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." + +| Qualifier | Ejemplo | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) coincide con los repositorios que son espejos y que contienen la palabra "GNOME". | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) coincide con los repositorios que no son espejos y que contienen la palabra "GNOME". | + +{% endif %} + +### Buscar en base a si un repositorio está archivado + +Puedes buscar los repositorios con base en si se archivaron o no. Para obtener más información, consulta la sección "[Acerca de archivar los repositorios](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)". + +| Qualifier | Ejemplo | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) coincide con los repositorios que se archivan y que contienen la palabra "GNOME". | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) coincide con los repositorios que no están archivados y que contienen la palabra "GNOME". | + +{% if currentVersion == "free-pro-team@latest" %} + +### Buscar en base a la cantidad de propuestas con las etiquetas `good first issue` o `help wanted` + +Puedes buscar repositorios que tienen una cantidad mínima de propuestas etiquetadas como `help-wanted` (se necesita ayuda) o `good-first-issue` (buena propuesta inicial) con los calificadores `help-wanted-issues:>n` y `good-first-issues:>n`. Para encontrar más información, consulta "[Fomentar las contribuciones útiles a tu proyecto con etiquetas](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)." + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) encuentra repositorios con más de dos propuestas etiquetadas como `good-first-issue` y que contienen la palabra "javascript." | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) encuentra repositorios con más de cuatro propuestas etiquetadas como `help-wanted` y que contienen la palabra "React." | + +{% endif %} + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" +- "[Búsqueda en bifurcaciones](/articles/searching-in-forks)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000000..dfc299fe9c119 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md @@ -0,0 +1,32 @@ +--- +title: Buscar en el Mercado de GitHub +intro: 'Puedes buscar aplicaciones y acciones disponibles en{% data variables.product.prodname_marketplace %}.' +versions: + free-pro-team: '*' +--- + +### Acerca de buscar en {% data variables.product.prodname_marketplace %} + +Puedes encontrar aplicaciones y acciones en{% data variables.product.prodname_marketplace %} de dos formas: + +- Buscar en{% data variables.product.prodname_marketplace %}. +- Buscar a través de todo {% data variables.product.prodname_dotcom_the_website %} y filtrar los resultados posteriormente. + +### Buscar en {% data variables.product.prodname_marketplace %} + +1. En la parte superior de cualquier página, da clic en **Mercado**. ![Enlace a Mercado](/assets/images/help/search/marketplace-link.png) +2. Teclea cualquier palabra clave y presiona **Enter**. ![Buscar linter en {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Opcionalmente, filtra tus resultados dando clic en una o más opciones en la barra lateral. + +### Buscar a través de {% data variables.product.prodname_dotcom_the_website %} + +Cada vez que buscas en todo {% data variables.product.prodname_dotcom_the_website %}, puedes filtrar los resultados para ver las coincidencias de aplicaciones y acciones de {% data variables.product.prodname_marketplace %}. + +1. Navega hasta https://github.com/search. +2. Teclea cualquier palabra clave y presiona **Enter**. ![campo buscar](/assets/images/help/search/search-field.png) +3. En la barra lateral, da clic en **Mercado**. ![Buscar resultados para linter con la opción del menú lateral del Mercado resaltada](/assets/images/help/search/marketplace-left-side-navigation.png) + +### Further reading + +- "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- "[Utilizar acciones de {% data variables.product.prodname_marketplace %} en tu flujo de trabajo](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md new file mode 100644 index 0000000000000..0aa8f3bfa1e6d --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md @@ -0,0 +1,28 @@ +--- +title: Buscar en bifurcaciones +intro: 'Por defecto, las bifurcaciones [forks](/articles/about-forks) no se muestran en los resultados de la búsqueda. Puedes elegir incluirlas en las búsquedas de repositorios y en las búsquedas de código si cumplen con determinados criterios.' +redirect_from: + - /articles/searching-in-forks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para mostrar bifurcaciones en los resultados de la [búsqueda de repositorios](/articles/searching-for-repositories), agrega `fork:true` o `fork:only` en tu consulta. + +Las fiburcaciones solo se indexan por [búsqueda de código](/articles/searching-code) cuando tienen más estrellas que el repositorio padre. No podrás buscar el código en una bifurcación que tenga menos estrellas que su padre. Para mostrar bifurcaciones con más estrellas que el repositorio padre en los resultados de una búsqueda de código, agrega `fork:true` o `fork:only` en tu consulta. + +El calificador `fork:true` encuentra todos los resultados que coinciden con tu consulta de búsqueda, incluidas las bifurcaciones. El calificador `fork:only` encuentra _únicamente_ bifurcaciones que coinciden con tu consulta de búsqueda. + +| Qualifier | Ejemplo | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) encuentra todos los repositorios que contienen la palabra "github," incluidas las bifurcaciones. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) encuentra código con la palabra "android" que está escrito en Java, tanto en bifurcaciones como en repositorios normales. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) encuentra todos los repositorios de bifurcaciones que contienen la palabra "github." | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) coincidirá con repositorios de más de 500 ramificaciones, y regresará únicamente aquellos que son ramificaciones. | + +### Further reading + +- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[Acerca de buscar en GitHub](/articles/about-searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md new file mode 100644 index 0000000000000..02fe2056ebb55 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,330 @@ +--- +title: Buscar propuestas y solicitudes de extracción +intro: 'Puedes buscar propuestas y solicitudes de extracción en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda en cualquier combinación.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar propuestas y solicitudes de extracción globalmente a través de todos los {% data variables.product.product_name %}, o buscar propuestas y solicitudes de extracción dentro de una organización particular. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". + +{% tip %} + +**Tips:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + - Este artículo contiene búsquedas de ejemplo en el sitio web {% data variables.product.prodname_dotcom %}.com, pero puedes utilizar los mismos filtros de búsqueda en {% data variables.product.product_location %}.{% endif %} + - Para obtener una lista de sintaxis de búsqueda que puedas agregar a cualquier calificador para mejorar aún más tus resultados, consulta "[Comprender la sintaxis de búsqueda](/articles/understanding-the-search-syntax)". + - Utiliza comillas alrededor de los términos de búsqueda que contengan varias palabras. Por ejemplo, si deseas buscar propuestas con la etiqueta "In progress" (En curso), buscarías por la etiqueta `label:"in progress"`. Buscar no distingue entre mayúsculas y minúsculas. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +### Buscar únicamente propuestas o solicitudes de extracción + +Por defecto, la búsqueda de {% data variables.product.product_name %} devolverá tanto propuestas como solicitudes de extracción. Sin embargo, puedes restringir los resultados de la búsqueda a solo propuestas y solicitudes de extracción utilizando el calificador `type` o `is`. + +| Qualifier | Ejemplo | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) encuentra solicitudes de extracción con la palabra "cat." | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) encuentra propuestas que contienen la palabra "github," y tienen un comentario de @defunkt. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) encuentra solicitudes de extracción con la palabra "event." | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) encuentra propuestas cerradas con la etiqueta "bug." | + +### Buscar por título, cuerpo o comentarios + +Con el calificador `in` puedes restringir tu búsqueda por título, cuerpo, comentarios o cualquier combinación de estos. Cuando omites este calificador, se buscan el título, el cuerpo y los comentarios, todos ellos. + +| Qualifier | Ejemplo | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) encuentra propuestas con "warning" en su título. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) encuentra propuestas con "error" en su título o cuerpo. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) encuentra propuestas que mencionan "shipit" en sus comentarios. | + +### Buscar dentro de los repositorios de un usuario u organización + +Para buscar propuestas y solicitudes de extracción en todos los repositorios que son propiedad de un determinado usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar propuestas y solicitudes de extracción en un repositorio específico, puedes utilizar el calificador `repo`. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) encuentra propuestas con la palabra "ubuntu" de repositorios que son propiedad de @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) encuentra propuestas en repositorios que son propiedad de la organización de GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) coincidirá con informes de problemas del proyecto de shumway de @mozilla que fueron creados antes de marzo de 2012. | + +### Buscar por estado abierto o cerrado + +Puedes filtrar propuestas y solicitudes de extracción en base a si están abiertas o cerradas utilizando el calificador `state` o `is`. + +| Qualifier | Ejemplo | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) encuentra propuestas abiertas que mencionan a @vmg con la palabra "libraries." | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) encuentra propuestas cerradas con la palabra "design" en el cuerpo. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) encuentra propuestas abiertas con la palabra "performance." | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "android." | + +### Filtrar por visibilidad de repositorio + +Puedes filtrar por la visibilidad del repositorio que contenga las propuestas y solicitudes de cambios utilizando el calificador `is`. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +| Calificador| Ejemplo | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) coincide con las propuestas y solicitudes de cambios en los repositorios públicos.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) coincide con las propuestas y solicitudes de cambios en los repositorios internos.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) coincide con las propuestas y solicitudes de cambios que contienen la palabra "cupcake" en los repositorios privados a los que puedes acceder. + +### Buscar por autor + +El calificador `author` (autor) encuentra propuestas y solicitudes de extracción creadas por un determinado usuario o cuenta de integración. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) coincide con las propeustas y solicitudes de cambios que contienen la palabra "cool" y que creó @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) coincide con las propuestas que escribió @mdo y que contienen la palabra "bootstrap" en el cuerpo. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) coincide con las propuestas que creó la cuenta de integración llamada "robot". | + +### Buscar por asignatario + +El calificador `assignee` (asignatario) encuentra propuestas y solicitudes de extracción que están asignadas a un determinado usuario. No puedes buscar propuestas y solicitudes que tengan _algún_ asignado cualquiera, sin embargo, puedes buscar por [propuestas y solicitudes de cambios que no tengan asignados](#search-by-missing-metadata). + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) coincide con las propuestas y solicitudes de cambio en el proyecto de libgit2 que se hayan asignado a @vmg. | + +### Buscar por mención + +El calificador `mentions` (menciones) encuentra propuestas que mencionan a un determinado usuario. Para obtener más información, consulta [Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) coincide con las propuestas que tengan la palabra "resque" y que mencionen a @defunkt. | + +### Buscar por mención de equipo + +Para las organizaciones y los equipos a los que perteneces, puedes utilizar el calificador `team` (equipo) para encontrar propuestas y solicitudes de extracción que mencionan a un determinado equipo dentro de esa organización. Reemplaza estos nombres de ejemplo con el nombre de tu organización y equipo para realizar una búsqueda. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** coincide con las propeustas en donde se menciona al equipo `@jekyll/owners`. | +| | **team:myorg/ops is:open is:pr** coincide con las solicitudes de cambios en donde se menciona al equipo `@myorg/ops`. | + +### Buscar por comentarista + +El calificador `commenter` (comentarista) encuentra propuestas que contienen un comentario de un determinado usuario. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) coincide con las propuestas en los repositorios que le pertenecen a GitHub y que contienen la palabra "github" y un comentario de @defunkt. | + +### Buscar por usuario que participa en una propuesta o solicitud de extracción + +Puedes utilizar el calificador `involves` para encontrar propuestas que de algún modo involucran a un determinado usuario. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `assignee`, `mentions` y `commenter` para un usuario único. En otras palabras, este calificador encuentra propuestas y solicitudes de extracción que fueron creadas por un determinado usuario, asignadas a ese usuario, que lo mencionan o que fueron comentadas por ese usuario. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** coincide con las propeustas en donde estén involucrados ya sea @defunkt o @jlord. | +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) coincide con las propuestas en donde se involucra a @mdo y que no contienen la palabra "bootstrap" en el cuerpo. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +### Buscar reportes de problemas y solicitudes de extracción enlazados +Puedes acotar tus resultados para que solo incluyan informes de problemas que se enlazaron con solicitudes de extracción con una referencia cerrada, o solicitudes de extracción que se enlazaron a un informe de problemas que se pueden cerrar con otra solicitud de extracción. + +| Qualifier | Ejemplo | +| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que se enlazan a una solicitud de extracción con una referencia cerrada. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) coincidirá con las solicitudes de extracción cerradas en el repositorio `desktop/desktop` que se enlazaron a un informe de problemas que se pudo haber cerrado con una solicitud de extracción. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que no estén enlazados a una solicitud de extracción por una referencia cerrada. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) Coincidirá con las solicitudes de extracción abiertas en el repositorio `desktop/desktop` que no se hayan enlazado con un informe de problemas que la solicitud de extracción haya creado. |{% endif %} + +### Buscar por etiqueta + +Puedes acotar tus resultados por etiquetas, utilizando el calificador `label` (etiqueta). Ya que las propuestas pueden tener múltiples etiquetas, puedes enumerar un calificador separado para cada propuesta. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) encuentra propuestas con la etiqueta "help wanted" (se necesita ayuda) que están en los repositorios Ruby. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) encuentra propuestas con la palabra "broken" en el cuerpo, que no tienen la etiqueta "bug" (error), pero *que tienen* la etiqueta "priority" (prioridad). | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) encuentra propuestas con las etiquetas "bug" (error) y "resolved" (solucionado). | + +### Buscar por hito + +El calificador `milestone` (hito) encuentra propuestas o solicitudes de extracción que son parte de un [hito](/articles/about-milestones) dentro de un repositorio. + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) encuentra propuestas que son un hito con el nombre de "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) encuentra propuestas que están en un hito con el nombre de "bug fix." | + +### Buscar por tablero de proyecto + +Puedes utilizar el calificador `project` (proyecto) para encontrar propuestas que están asociadas con un [tablero de proyecto](/articles/about-project-boards/) específico en un repositorio u organización. Debes buscar tableros de proyecto por el número del tablero de proyecto. Puedes encontrar el número del tablero de proyecto al final de la URL de cada tablero de proyecto. + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** encuentra propuestas propiedad de GitHub que están asociadas con el tablero de proyecto de la organización número 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** encuentra propuestas que están asociadas con el tablero de proyecto 1 en el repositorio lingüístico de @github. | + +### Buscar por estado de confirmación + +Puedes filtrar solicitudes de extracción en base al estado de las confirmaciones. Esto es particularmente útil si estás utilizando [el estado API](/rest/reference/repos#statuses) o un servicio CI. + +| Qualifier | Ejemplo | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) encuentra solicitudes de extracción abiertas en repositorios Go donde el estado es pendiente. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) encuentra solicitudes de extracción abiertas con la palabra "finally" en el cuerpo con un estado exitoso. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) encuentra solicitudes de extracción abiertas en mayo de 2015 con un estado falló. | + +### Buscar por SHA de confirmación + +Si sabes el hash SHA específico de una confirmación, puedes utilizarlo para buscar solicitudes de extracción que contienen ese SHA. La sintaxis SHA debe ser por lo menos de siete caracteres. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) encuentra solicitudes de extracción con una confirmación SHA que comience con `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) encuentra solicitudes de extracción fusionadas con una confirmación SHA que comience con `0eff326d6213c`. | + +### Buscar por nombre de la rama + +Puedes filtrar solicitudes de extracción en base a la rama de la que provienen (la rama "head" [de encabezado]) o la rama en la que están fusionadas (en la rama "base" [base]). + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) encuentra solicitudes de extracción abiertas desde los nombres de las ramas que comienzan con la palabra "change" que están cerradas. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) encuentra solicitudes de extracción que se están fusionando dentro de la rama `gh-pages`. | + +### Buscar por lenguaje + +Con el calificador `language` (lenguaje) puedes buscar propuestas y solicitudes de extracción dentro de repositorios que están escritos en un determinado lenguaje. + +| Qualifier | Ejemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) encuentra propuestas abiertas que están en los repositorios Ruby. | + +### Buscar por cantidad de comentarios + +Puedes utilizar el calificador `comments` (comentarios) junto con los calificadores [mayor que, menor que y rango ](/articles/understanding-the-search-syntax) para buscar por cantidad de comentarios. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) encuentra propuestas cerradas con más de 100 comentarios. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) encuentra propuestas con comentarios que van desde 500 a 1000. | + +### Buscar por cantidad de interacciones + +Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de interacciones, utilizando el calificador `interactions` (interacciones) y junto con [los calificadores mayor que, menor que y rango](/articles/understanding-the-search-syntax). El conteo de interacciones es la cantidad de reacciones y comentarios sobre una propuesta o solicitud de extracción. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) encuentra solicitudes de extracción o propuestas con más de 2000 interacciones. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) encuentra solicitudes de extracción o propuestas con un rango de interacciones entre 500 a 1000. | + +### Buscar por cantidad de reacciones + +Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de reacciones, utilizando el calificador `reactions` (reacciones) y junto con [los calificadores mayor que, menor que y rango](/articles/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) encuentra propuestas con más de 1000 reacciones. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) encuentra propuestas con reacciones con un rango de entre 500 a 1000. | + +### Buscar solicitudes de extracción en borrador +Puedes filtrar por solicitudes de extracción en borrador. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)." + +| Calificador | Ejemplo | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) coincide con los borradores de las solicitudes de cambios. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) coincidirá con las solicitudes de extracción listas para revisión.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) coincidirá con las solicitudes de extracción en estado de borrador.{% endif %} + +### Buscar por estado de revisión de solicitud de extracción y revisor + +Puedes filtrar las solicitudes de extracción en función de su [estado de revisión](/articles/about-pull-request-reviews) (_ninguno_, _requerido_, _aprobado_ o _cambios solicitados_), por revisor y por revisor solicitado. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) encuentra solicitudes de extracción que no han sido revisadas. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) encuentra solicitudes de extracción que requieren una revisión antes de poder ser fusionadas. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) encuentra solicitudes de extracción que un revisor ha aprobado. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) encuentra solicitudes de extracción en las cuales un revisor ha solicitado cambios. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) encuentra revisión de solicitudes de extracción por una persona particular. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) encuentra solicitudes de extracción donde una persona específica solicitó una revisión. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. Si la persona solicitada es sobre un equipo al que se lo solicita la revisión, entonces las solicitudes de revisión de ese equipo también aparecerán en los resultados de búsqueda. | +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) encuentra solicitudes de extracción que tienen solicitudes de revisión de un equipo `atom/design`. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. | + +### Buscar por cuándo una propuesta o solicitud de extracción fue creada o actualizada por última vez + +Puedes filtrar propuestas en base al momento de creación o al momento de su última actualización. Para la creación de una propuesta, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). + +Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) encuentra las propuestas que se crearon antes de 2011 en los repositorios que están escritos en C#. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) encuentra las propuestas con la palabra "weird" en el cuerpo, las cuales se actualizaron después de febrero del 2013. | + +### Buscar por cuándo una propuesta o solicitud de extracción fue cerrada + +Puedes filtrar propuestas y solicitudes de extracción en base a su momento de cierre, utilizando el calificador `closed` (cerrada). + +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) encuentra las propuestas y solicitudes de cambios en Swift que se cerraron después del 11 de junio de 2014. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) encuentra las propuestas y solicitudes de cambio con la palabra "data" en el cuerpo, las cuales se cerrron antes de octubre de 2012. | + +### Buscar por cuándo una solicitud de extracción fue fusionada + +Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas, utilizando el calificador `merged` (fusionada). + +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) encuntra las solicitudes de cambio en los repositorios de JavaScript que se fusionaron antes de 2011. | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) encuentra las solicitudes de cambiosen Ruby con la palabra "fast" en el título, los cuales se hayan fusionado después de mayo de 2014. | + +### Buscar en base a si una solicitud de extracción se fusionó o se desagrupó + +Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas o desagrupadas, utilizando el calificador `is`. + +| Qualifier | Ejemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) encuentra solicitudes de extracción fusionadas con la palabra "bugfix." | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "error." | + +### Buscar en base a si un repositorio está archivado + +El calificador `archived` (archivado) filtra tus resultados en base a si una propuesta o una solicitud de extracción está en un repositorio archivado. + +| Qualifier | Ejemplo | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios archivados a los que tienes acceso. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios no archivados a los que tienes acceso. | + +### Buscar en base a si una conversación está bloqueada + +Puedes buscar por una propuesta o solicitud de extracción que tiene una conversación utilizando el calificador `is`. Para obtener más información, consulta "[Bloquear conversaciones](/articles/locking-conversations)." + +| Qualifier | Ejemplo | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación bloqueada en un repositorio que no se ha archivado. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación desbloqueada en un repositorio que no se ha archivado. | + +### Buscar por metadatos faltantes + +Puedes acotar tu búsqueda a propuestas y solicitudes de extracción que tienen determinados metadatos faltantes, utilizando el calificador `no`. Esos metadatos incluyen: + +* Etiquetas +* Hitos +* Asignatarios +* Proyectos + +| Qualifier | Ejemplo | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) encuentra propuestas y solicitudes de extracción con la palabra "priority" que tampoco tienen ninguna etiqueta. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un hito que contienen la palabra "sprint." | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un asignatario, que contienen la palabra "important," y en repositorios Java. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) encuentra propuestas no asociadas con un tablero de proyecto, que contienen la palabra "build." | + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md new file mode 100644 index 0000000000000..e5c1d3a8750b5 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md @@ -0,0 +1,11 @@ +--- +title: Buscar en GitHub +mapTopic: verdadero +redirect_from: + - /articles/searching-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md new file mode 100644 index 0000000000000..51480cdb89c16 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md @@ -0,0 +1,51 @@ +--- +title: Buscar temas +intro: 'Puedes buscar temas asociados con los repositorios en {% data variables.product.product_name %}.' +redirect_from: + - /articles/searching-topics +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Buscar temas en {% data variables.product.product_name %} + +Puedes buscar temas en {% data variables.product.product_name %}, explorar temas relacionados y ver cuántos repositorios están asociados con un tema determinado. + +1. Navega hasta https://github.com/search. +2. Escribe una palabra clave del tema. ![campo buscar](/assets/images/help/search/search-field.png) +3. En la barra lateral de la izquierda, para acotar tu búsqueda por temas, haz clic en **Topics (Temas)**. +{% if currentVersion == "free-pro-team@latest" %} + ![La página de resultados de búsqueda de repositorios de Jekyll con la opción de menú lateral de temas resaltada](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +### Acotar tu búsqueda con calificadores de búsqueda + +Si deseas explorar repositorios sobre un determinado tema, encontrar proyectos en los que contribuir, o conocer qué temas son más populares en {% data variables.product.product_name %}, puedes buscar temas con los calificadores de búsqueda `is:featured`, `is:curated`, `repositories:n` y `created:YYYY-MM-DD`. + +El calificador de búsqueda `is:featured` acotará los resultados de búsqueda a los temas con la mayor cantidad de repositorios en {% data variables.product.product_name %}. Estos temas también se muestran en https://github.com/topics/. + +El calificador de búsqueda de `is:curated` acotará los resultados de búsqueda en los temas a los que los miembros de la comunidad han agregado información adicional. Para obtener más información, consulta la sección de [explorar repositorios](https://github.com/github/explore). + +Puedes filtrar temas en base a cuándo se crearon utilizando el parámetro de fecha y `created:` o en base a cuántos repositorios están asociados con este tema utilizando `repositories:n`. Estos dos calificadores pueden utilizar los calificadores de rango mayor que y menor que [](/articles/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) encuentra temas que están conservados y contienen la palabra "javascript." | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) encuentra temas que se muestran en https://github.com/topics/ y contienen la palabra "javascript." | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) encuentra temas que no tienen información extra, como una descripción o un logo, y que contienen la palabra "javascript." | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) encuentra temas que no se muestran en https://github.com/topics/ y contienen la palabra "javascript." | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) encuentra temas que tienen más de 5000 repositorios. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) encuentra temas con la palabra "serverless" que fueron creados después de 2018. | + +### Buscar repositorios por tema + +Puedes utilizar el calificador `topic:` (tema) para encontrar cada repositorio conectado a un tema particular. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)." + +### Further reading +- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md new file mode 100644 index 0000000000000..eab9871d4854b --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md @@ -0,0 +1,90 @@ +--- +title: Buscar usuarios +intro: 'Puedes buscar usuarios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de usuarios en cualquier combinación.' +redirect_from: + - /articles/searching-users +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar usuarios globalmente a través de todos los {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +### Buscar únicamente por usuarios u organizaciones + +Por defecto, buscar usuarios mostrará personas y organizaciones. Sin embargo, puedes utilizar el calificador `type` (tipo) para restringir los resultados de la búsqueda a cuentas personales o de organizaciones únicamente. + +| Qualifier | Ejemplo | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) encuentra cuentas personales con el nombre "mike" que fueron creadas antes de 2011. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) encuentra organizaciones con la palabra "data" en su correo electrónico. | + +### Buscar por nombre de cuenta, nombre completo o correo electrónico público + +Puedes filtrar tu búsqueda al nombre de la cuenta de usuario personal o de una organización con los calificadores `user` u `org`. + +Con el calificador `in` puedes restringir tu búsqueda al nombre de usuario (`login`), el nombre completo, el correo electrónico público, o cualquier combinación de ellos. Cuando omites este calificador, únicamente se buscan el nombre de usuario y la dirección de correo electrónico. Por razones de privacidad, no puedes buscar por nombre de dominio de correo electrónico. + +| Qualifier | Ejemplo | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) encuentra el usuario con el nombre de usuario "octocat". | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) encuentra el nombre de la cuenta de la organización Electron. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) encuentra los usuarios con la palabra "kenya" en su nombre de usuario. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) encuentra a los usuarios cuyo nombre real contiene la palabra "bolton." | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) encuentra un usuario con el nombre completo "Nat Friedman." Nota: este calificador de búsqueda es sensible a los espacios. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) encuentra a los usuarios con la palabra "data" en su correo electrónico. | + +### Buscar por cantidad de repositorios que posee el usuario + +Puedes filtrar usuarios en base a la cantidad de repositorios que poseen, utilizando el calificador `repos` y [los calificadores mayor que, menor que y rango](/articles/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) coincidirá con los usuarios cuyo número de repositorios sea mayor a 9.000. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) encuentra usuarios con la palabra "bert" en su nombre de usuario o nombre real que poseen de 10 a 30 repositorios. | + +### Buscar por ubicación + +Puedes buscar usuarios por la ubicación indicada en su perfil. + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) encuentra usuarios con exactamente un repositorio que viven en Islandia. | + +### Buscar por lenguaje del repositorio + +Utilizando el calificador `language` (lenguaje) puedes buscar usuarios en base al lenguaje de los repositorios que poseen. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) encuentra usuarios en Rusia con una mayoría de sus repositorios escritos en JavaScript. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) encuentra usuarios con repositorios en JavaScript cuyos nombres completos contienen la palabra "jenny." | + +### Buscar por cuándo fue creada la cuenta del usuario + +Puedes filtrar usuarios en base a cuándo se unieron a {% data variables.product.product_name %} con el calificador `created` (creada). Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) coincidirá con los usuarios que se hayan unido antes de 2011. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) coincidirá con los usuarios que se hayan unido en o después del 11 de mayo. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) encuentra usuarios que se unieron el 6 de marzo de 2013, y que muestran su ubicación como Londres. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) encuentra usuarios que se unieron entre 2010 y 2011 con la palabra "john" en su nombre de usuario. | + +### Buscar por cantidad de seguidores + +Puedes filtrar usuarios en base a la cantidad de seguidores que tienen, utilizando el calificador `followers` (seguidores) con los calificadores [mayor que, menor que y rango](/articles/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) coincidirá con los usuarios con 1,000 o más seguidores. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) encuentra usuarios entre 1 y 10 seguidores, con la palabra "sparkle" en su nombre. | + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md new file mode 100644 index 0000000000000..dc8f652fd5ff0 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md @@ -0,0 +1,47 @@ +--- +title: Buscar wikis +intro: 'Puedes buscar wikis en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de wiki en cualquier combinación.' +redirect_from: + - /articles/searching-wikis +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes buscar wikis globalmente a través de todos los {% data variables.product.product_name %}, o buscar wikis dentro de un repositorio u organización particular. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +### Buscar dentro de los repositorios de un usuario u organización + +Para encontrar páginas wiki de todos los repositorios propiedad de un determinado usuario u organización, utiliza el calificador `user` u `org`. Para buscar páginas wiki en un repositorio específico, utiliza el calificador `repo`. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) encuentra páginas wiki de los repositorios propiedad de @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) encuentra wikis en repositorios propiedad de la organización de GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) encuentra páginas wiki del repositorio "gibberish" de @defunkt. | + +### Buscar dentro del título o el texto del cuerpo de una página wiki + +El calificador `in` acota la búsqueda al título o al texto del cuerpo de la página wiki. Sin el calificador, se busca tanto en el título como en el texto del cuerpo. + +| Qualifier | Ejemplo | +| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) encuentra títulos de página wiki con la palabra "usage." | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) encuentra páginas wiki con la palabra "installation" en el texto de su cuerpo principal. | + +### Buscar por la última fecha de actualización + +El calificador `updated` (actualizada) empareja páginas wiki que fueron actualizadas por última vez dentro de un rango específico de fechas. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) coincidirá con las páginas de wiki con la palabra "uso" que se actualizaron por última vez después del 2016-01-01. | + +### Further reading + +- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md b/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md new file mode 100644 index 0000000000000..bc2bf4d64a576 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md @@ -0,0 +1,71 @@ +--- +title: Clasificar resultados de búsqueda +intro: 'Puedes clasificar los resultados de búsqueda [{% data variables.product.product_name %} search](/articles/searching-on-github) utilizando el menú de Clasificación, o al agregar un calificador `sort` a tu consulta.' +redirect_from: + - /articles/sorting-search-results +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Utiliza el menú Sort (Clasificar) para clasificar resultados por relevancia, cantidad de estrellas, cantidad de bifurcaciones y qué tan recientemente se actualizaron los elementos. + + ![Menú con opciones para clasificar resultados de búsqueda](/assets/images/help/search/repo-search-sort.png) + +Para clasificar por interacciones, reacciones, fecha de autor, fecha de persona que confirma el cambio, o qué tan recientemente se actualizaron los elementos, puedes agregar un calificador `sort` a tu consulta de búsqueda. + +### Clasificar por interacciones + +El calificador `sort:interactions` clasifica según el mayor número combinado de reacciones y comentarios. + +| Qualifier | Ejemplo | +| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` or `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por el mayor número combinado de reacciones y comentarios. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por el menor número combinado de reacciones y comentarios. | + +### Clasificar por reacciones + +El calificador `sort:reactions` clasifica por la cantidad o el tipo de reacciones. + +| Qualifier | Ejemplo | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` or `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la cantidad ascendente de reacciones (desde la menor a la mayor). | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones positivas (:+1:). | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones negativas (:-1:). | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por las mayores reacciones de risa (:smile:). | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones buenas (:tada:). | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones corazón(:heart:). | + +### Clasificar por fecha de autor + +El calificador `sort:author-date` clasifica por fecha de autor descendente o ascendente. + +| Qualifier | Ejemplo | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` or `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de autor descendente. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de autor ascendente. | + +### Clasificar por fecha de persona que confirma el cambio + +El calificador `sort:committer-date` clasifica por fecha de persona que confirma el cambio descendente o ascendente. + +| Qualifier | Ejemplo | +| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` or `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de la persona que confirma el cambio descendente. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha ascendente de la persona que confirma el cambio. | + +### Clasificar por fecha de actualización + +El calificador `sort:updated` clasifica según qué tan recientemente se actualizaron los elementos. + +| Qualifier | Ejemplo | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:updated` or `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización más reciente. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización menos reciente. | + +### Further reading + +- [Acerca de la búsqueda en GitHub](/articles/about-searching-on-github) +- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests/) diff --git a/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md b/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000000..54f5d76f91b44 --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md @@ -0,0 +1,29 @@ +--- +title: Solucionar problemas de consultas de búsqueda +intro: 'Si encuentras resultados inesperados cuando buscas en {% data variables.product.product_name %}, puedes solucionar los problemas revisando los problemas comunes y las limitaciones.' +redirect_from: + - /articles/troubleshooting-search-queries +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Interrupciones potenciales + +Algunas consultas son costosas desde el punto de vista informático para que las ejecute nuestra infraestructura de búsqueda. Para que la búsqueda siga siendo rápida para todos, limitamos la cantidad de tiempo que se puede ejecutar una consulta individual. En pocas situaciones, cuando una consulta supera el límite de tiempo, la búsqueda devuelve todas las coincidencias que se encontraron antes de que se acabara el tiempo y te informa que se acabó el tiempo. + +Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Solo significa que la consulta se interrumpió antes de que se buscara en todos los datos posibles. + +### Limitaciones sobre la longitud de la consulta + +Existen algunos límites en la longitud de las consultas cuando se busca en {% data variables.product.product_name %}: + +* No se admiten consultas que superen los 256 caracteres +* No puede elaborar una consulta que utilice más de cinco operadores `AND`, `OR` o `NOT` + +Los tipos de búsqueda específicos, como la búsqueda de código, pueden tener más limitaciones. Revisa la documentación de estos tipos de búsqueda para obtener más información. + +### Further reading + +- "[Acerca de buscar en GitHub](/articles/about-searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/understanding-the-search-syntax.md b/translations/es-ES/content/github/searching-for-information-on-github/understanding-the-search-syntax.md new file mode 100644 index 0000000000000..a8f06292db5fb --- /dev/null +++ b/translations/es-ES/content/github/searching-for-information-on-github/understanding-the-search-syntax.md @@ -0,0 +1,95 @@ +--- +title: Entender la sintaxis de búsqueda +intro: 'Cuando buscas {% data variables.product.product_name %}, puedes construir consultas que coincidan con números y palabras específicas.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Consulta para valores mayores o menores que otro valor + +Puedes utilizar `>`, `>=`, `<` y `<=` para buscar valores que sean mayores, mayores o iguales, menores y menores o iguales a otro valor. + +| Consulta | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan más de 1000 estrellas. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan 5 o más temas. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** coincidirá con el código que tenga la palabra "cats" en los archivos que sean menores a 10 KB. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y 50 estrellas o menos. | + +También puedes utilizar [consultas por rango](#query-for-values-between-a-range) para buscar valores que sean mayores o iguales, o menores o iguales a otro valor. + +| Consulta | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| n..* | **[gatos estrellas:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** equivale a `estrellas:>=10` y busca repositorios con la palabra "gatos" que tengan 10 o más estrellas. | +| *..n | **[gatos estrellas:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** equivale a `estrellas:<=10` y busca repositorios con la palabra "gatos" que tengan 10 o menos estrellas. | + +### Consulta para valores entre un rango + +Puedes utilizar la sintaxis de rango n..n para buscar valores dentro de un rango, en los que el primer número _n_ sea el valor más bajo y el segundo sea el valor más alto. + +| Consulta | Ejemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[gatos estrellas:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** busca repositorios con la palabra "gatos" que tengan entre 10 y 50 estrellas. | + +### Consulta por fechas + +Puedes buscar fechas que sean anteriores o posteriores a otra fecha o que entren en un rango de fechas, utilizando `>`, `>=`, `<`, `<=` y [consultas por rango](#query-for-values-between-a-range). {% data reusables.time_date.date_format %} + +| Consulta | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >AAAA-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** coincidirá con informes de problemas que tengan la palabra "cats" y se hayan creado después del 29 de abril de 2016. | +| >=AAAA-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** coincidirá con informes de problemas que contengan la palabra "cats" y se hayan creado en o después del 1 de abril de 2017. | +| <AAAA-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** coincidirá con el código que contenga la palabra "cats" en los repositorios en los que se subió información antes del 5 de julio de 2012. | +| <=AAAA-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** coincidirá con los informes de problemas que contengan la palabra "cats" y se hayan creado en o antes del 4 de julio de 2012. | +| AAAA-MM-DD..AAAA-MM-DD | **[gatos subidos:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** busca repositorios con la palabra "gatos" que se hayan subido entre fines de abril y julio de 2016. | +| AAAA-MM-DD..* | **[gatos creados:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** busca propuestas que se hayan creado después del 30 de abril de 2012 y contengan la palabra "gatos". | +| *..AAAA-MM-DD | **[gatos creados:*..2012-04-30](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** busca propuestas creadas antes del 4 de julio de 2012 que contengan la palabra "gatos". | + +{% data reusables.time_date.time_format %} + +| Consulta | Ejemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| AAAA-MM-DDTHH:MM:SS+00:00 | **[gatos creados:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** busca propuestas creadas entre el 1 de enero de 2017 a la 1 a. m. con una compensación de UTC de `07:00` y el 1 de marzo de 2017 a las 3 p. Con un desplazamiento UTC de `07:00` y 1 de marzo de 2017 a las 3 p.m. m. con una compensación de UTC de `07:00`. | +| AAAA-MM-DDTHH:MM:SSZ | **[gatos creados:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** busca propuestas creadas entre el 21 de marzo de 2016 a las 2:11 p. m. y el 7 de abril de 2106 a las 8:45 p. m. | + +### Excluye determinados resultados + +Puedes excluir resultados que contengan una determinada palabra utilizando la sintaxis `NOT` (NO). El operador `NOT` solo se puede utilizar para las palabras clave en cadena. No funciona para números o fechas. + +| Consulta | Ejemplo | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hola NOT mundo](https://github.com/search?q=hello+NOT+world&type=Repositories)** busca repositorios que tengan la palabra "hola", pero no la palabra "mundo" | + +Otra manera de reducir los resultados de búsqueda es excluir determinados subconjuntos. Puedes usar como prefijo de cualquier calificador de búsqueda un `-` para excluir todos los resultados que coincidan con ese calificador. + +| Consulta | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -CALIFICADOR | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan más de 10 estrellas, pero no se hayan escrito en JavaScript. | +| | **[menciones:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** busca propuestas que mencionan a @defunkt y no estén en repositorios de la organización de GitHub | + +### Utiliza comillas para las consultas con espacios en blanco + +Si tu consulta de búsqueda contiene espacios en blanco, tendrás que encerrarla entre comillas. Por ejemplo: + +* [gatos NOT "hola mundo"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) busca repositorios con la palabra "gatos", pero sin las palabras "hola mundo". +* [construir etiqueta:"corrección de error"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) busca propuestas con la palabra "construir" que tengan la etiqueta "corrección de error". + +Algunos símbolos que no son alfanuméricos, como los espacios, se quitan de las consultas de búsqueda de código que van entre comillas; por lo tanto, los resultados pueden ser imprevistos. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +### Consultas con nombres de usuario + +Si tu consulta de búsqueda contiene un calificador que requiere un nombre de usuario, tal como `user`, `actor`, o `assignee`, puedes utilizar cualquier nombre de usuario de {% data variables.product.product_name %} para especificar una persona en concreto, o utilizar `@me`, para especificar el usuario actual. + +| Consulta | Ejemplo | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) coincidirá con las confirmaciones del autor @nat | +| `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) coincidirá con los informes de problemas asignados a la persona que está viendo los resultados | + +Solo puedes utilizar `@me` con un calificador y no como un término de búsqueda, tal como `@me main.workflow`. +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md new file mode 100644 index 0000000000000..99972f4c438e4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md @@ -0,0 +1,33 @@ +--- +title: Acerca de la facturación para Large File Storage de Git +intro: 'Si compras ancho de banda y almacenamiento adicional para {% data variables.large_files.product_name_long %}, tu compra comparte la fecha de facturación, el método de pago y el recibo existentes de tu cuenta.' +redirect_from: + - /articles/about-billing-for-git-large-file-storage +versions: + free-pro-team: '*' +--- + +### Acerca de la facturación para {% data variables.large_files.product_name_long %} + +{% data reusables.large_files.free-storage-bandwidth-amount %} {% data reusables.large_files.does_not_carry %} + +{% data reusables.large_files.owner_quota_only %} + +### Comprar ancho de banda y almacenamiento adicional + +Se ofrece ancho de banda y almacenamiento adicional en un paquete de datos simple. Un paquete de datos cuesta {% data variables.large_files.pack_monthly_price %} y ofrece una cuota mensual de {% data variables.large_files.pack_monthly_bandwidth %} para ancho de banda y {% data variables.large_files.pack_monthly_storage %} para almacenamiento. Puedes comprar tantos paquetes de datos como necesites. Por ejemplo, si necesitas 150 GB de almacenamiento, comprarías tres paquetes de datos. + +La compra de paquetes de datos para {% data variables.large_files.product_name_short %} es independiente de cualquier otra característica paga o producto en {% data variables.product.product_name %}. + +### Bajar de categoría el almacenamiento y el ancho de banda + +Si bajas de categoría tu cantidad de paquetes de datos adicionales, tus cambios entrarán en vigencia en tu próxima fecha de facturación. + +### Further reading + +- "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" +- "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" +- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" +- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" +- "[Actualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)" +- "[Bajar de categoría {% data variables.large_files.product_name_long %}](/articles/downgrading-git-large-file-storage)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts.md new file mode 100644 index 0000000000000..93f3b4649ac70 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts.md @@ -0,0 +1,27 @@ +--- +title: Acerca de la facturación para las cuentas de GitHub +intro: '{% data variables.product.product_name %} ofrece productos gratuitos y pagos para cada programador o equipo.' +redirect_from: + - /articles/what-is-the-total-cost-of-using-an-organization-account/ + - /articles/what-are-the-costs-of-using-an-organization-account/ + - /articles/what-plan-should-i-choose/ + - /articles/do-you-have-custom-plans/ + - /articles/user-account-billing-plans/ + - /articles/organization-billing-plans/ + - /articles/github-s-billing-plans + - /articles/about-billing-for-github-accounts +versions: + free-pro-team: '*' +--- + +Para obtener más información sobre los productos disponibles para tu cuenta, consulta los productos de"[{% data variables.product.product_name %}](/articles/github-s-products)". Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} no ofrece productos personalizados ni suscripciones. + +Puedes elegir una facturación mensual o anual y puedes actualizar o bajar de categoría tu suscripción en cualquier momento. Para obtener más información, consulta "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)". + +Puedes comprar otras características o productos con tu información de pago de {% data variables.product.product_name %} existente. Para obtener más información, consulta "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". + +{% tip %} + +**Sugerencia:** {% data variables.product.prodname_dotcom %} tiene programas para estudiantes validados y académicos, que incluyen descuentos académicos. Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/). + +{% endtip %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md new file mode 100644 index 0000000000000..6c26774334e81 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -0,0 +1,78 @@ +--- +title: Acerca de la facturación para GitHub Actions +intro: 'Si quieres utilizar {% data variables.product.prodname_actions %} con más almacenamiento o minutos de los que se incluyen en tu cuenta, se te cobrará por estos recursos adicionales.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' +--- + +### Acerca de la facturación para {% data variables.product.prodname_actions %} + +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)". + +Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenamiento. + +| Producto | Almacenamiento | Minutos (por mes) | +| --------------------------------------------------------------------- | -------------- | ----------------- | +| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 | +| {% data variables.product.prodname_pro %} | 1 GB | 3,000 | +| {% data variables.product.prodname_free_team %} para organizaciones | 500 MB | 2,000 | +| {% data variables.product.prodname_team %} | 2 GB | 3,000 | +| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 | + +Los jobs que se ejecutan en Windows y macOS y que se hospedan en {% data variables.product.prodname_dotcom %} consumen minutos en una proporción de 2 a 10 veces mayor que aquellos que se ejecutan en Linux. Por ejemplo, utilizar 1,000 minutos en Windows consumirá 2,000 de los minutos incluidos en tu cuenta. Utilizar 1,000 minutos en macOS consumiría 10,000 de los minutos incluidos en tu cuenta. + +| Sistema operativo | Multiplicador de minutos | +| ----------------- | ------------------------ | +| Linux | 1 | +| macOS | 10 | +| Windows | 2 | + +El almacenamiento que utilza un repositorio es el total del almacenamiento utilizado por los artefactos de {% data variables.product.prodname_actions %} y por {% data variables.product.prodname_registry %}. Tu costo de almacenamiento es el uso total para todos los repositorios que pertenezcan a tu cuenta. Para obtener más información sobre los costos de {% data variables.product.prodname_registry %}, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". + + Si tu uso de cuenta sobrepasa estos límites y habías configurado un límite de gastos mayor a $0, pagarás $0.25 USD por GB de almacenamiento por mes y por minuto de uso dependiendo en el sistema operativo que utilice el ejecutor hospedado en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} redondea hacia arriba los minutos que utiliza cada job. + +{% note %} + +**Nota:**Los multiplicadores de minutos no se aplican a las tasas por minuto que se muestran a continuación. + +{% endnote %} + +| Sistema operativo | Tasa por minuto | +| ----------------- | --------------- | +| Linux | $0.008 | +| macOS | $0.08 | +| Windows | $0.016 | + +La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los repositorios que pertenezcan a tu cuenta de usuario u organización dependerá de tu plan de GitHub. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados. + +### Calcular los gastos por minuto y por almacenamiento + +Al final de cada mes, {% data variables.product.prodname_dotcom %} calcula el costo de los minutos y almacenamiento utilizados en comparación con lo que se incluye en tu cuenta. Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 15,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 (USD) dependiendo de los sistemas operativos que se utilizan para ejecutar jobs. + +- 5,000 minutos (3,000 de Linux y 2,000 de Windows) = $56 ($24 + $32) (USD). + - 3,000 minutos de Linux a $0.008 por minuto = $24 (USD). + - 2,000 minutos de Windows a $0.016 por minuto = $32 (USD). + +Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu transferencia de datos al número de GB más cercano. + +{% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes. Por ejemplo, si utilizas 3 GB de almacenamiento durante 10 días de Marzo y 12 GB durante 21 días de Marzo, tu uso de almacenamiento sería: + +- 3 GB x 10 días x (24 horas por día) = 720 GB-Horas +- 12 GB x 21 días x (24 horas por día) = 6,048 GB-Horas +- 720 GB-Horas + 6,048 GB-Horas = 6,768 GB-Horas +- 6,768 GB-Horas/ (744 horas por mes) = 9.0967 GB-Meses + +Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Por lo tanto, tu uso de almacenamiento para marzo sería de 9.097 GB. + +Tu uso de {% data variables.product.prodname_actions %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %} + +### Acerca de los límites de gasto + +{% data reusables.github-actions.actions-spending-limit-detailed %} + +Para obtener más información sobre cómo administrar y cambiar el límite de gastos de tu organización, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)". + +{% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md new file mode 100644 index 0000000000000..615ac1badd434 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md @@ -0,0 +1,55 @@ +--- +title: Acerca de la facturación para el Mercado GitHub +intro: 'Si instalas una app paga en {% data variables.product.prodname_marketplace %}, tu suscripción comparte la fecha de facturación, el método de pago y el recibo existentes de tu cuenta.' +redirect_from: + - /articles/about-billing-for-github-marketplace +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Después de comprar e instalar una app, puedes actualizar, bajar de categoría o cancerla en cualquier momento. + +{% data reusables.marketplace.marketplace-apps-only %} + +{% data reusables.marketplace.marketplace-org-perms %} + +### Métodos de pago y ciclos de facturación para las compras de {% data variables.product.prodname_marketplace %} + +Tendrás el mismo método de pago para todas las suscripciones y los planes pagos en todo {% data variables.product.prodname_dotcom %}. + +Si tu cuenta personal u organización no tienen un método de pago en el archivo, cuando eliges un plan pago para una app: +- Tu fecha de facturación es hoy. +- Debes agregar un método de pago a tu cuenta personal o a la organización en la que quieres instalar la app. +- Tu método de pago será cargado con el monto total de tu suscripción. +- Tu recibo se envía a la dirección de correo electrónico de facturación o a la principal en el archivo para tu cuenta personal u organización. + +Si tu cuenta personal u organización tienen un método de pago existente, cuando eliges un plan pago para una app: +- Al método de pago en el archivo se le cobrará de inmediato un monto prorrateado por el tiempo restante hasta tu próxima fecha de facturación. +- La fecha de facturación mensual o anual para la suscripción de tu app es la misma que la fecha de facturación regular de tu cuenta u organización. +- En tu próxima fecha de facturación, tu recibo detalla los cargos por tu plan {% data variables.product.prodname_dotcom %} pago y tu suscripción a la app. + +Cuando eliges un plan pago con una prueba gratuita: +- Debes tener un método de pago existente o agregar un método de pago nuevo para tu cuenta personal o para la organización en la que quieres instalar la app. +- Si no tienes ninguna otra suscripción ni plan pago, se te cobrará el monto total de tu suscripción al finalizar la prueba gratuita de 14 días. +- Si tienes otras suscripciones o planes pagos, una vez que finaliza tu prueba de 14 días, al método de pago en el archivo se le cobrará de inmediato un monto prorrateado por el tiempo restante hasta tu próxima fecha de facturación. +- Si tienes otras suscripciones o planes pagos, en tu próxima fecha de facturación, tu recibo detalla los cargos por tu plan {% data variables.product.prodname_dotcom %} pago y tu suscripción a la app. + +### Limites de plan unitario + +Si eliges un plan unitario (por ejemplo, un plan que cobra por usuario) y excedes las unidades por las que estás pagando, el integrador puede desactivar tu acceso hasta que actualices la app. Para obtener más información, consulta [Actualizar el plan de facturación para una app del {% data variables.product.prodname_marketplace %}](/articles/upgrading-the-billing-plan-for-a-github-marketplace-app)". + +### Bajar de categoría una app {% data variables.product.prodname_marketplace %} + +Si bajas de categoría la suscripción de tu app a un plan más económico o si cancelas la suscripción de una app paga, tus cambios entrarán en vigencia al finalizar tu ciclo de facturación actual. Tu suscripción se moverá a tu nuevo plan en tu próxima fecha de facturación. + +Si cancelas una app en un plan gratuito, tu suscripción terminará de inmediato y perderás el acceso a la app. + +{% data reusables.marketplace.downgrade-marketplace-only %} + +Si cancelas un prueba gratuita en un plan pago, tu suscripción se cancela de inmediato y perderás el acceso a la app. Para obtener más información, consulta [Cancelar una app de {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app)". + +### Further reading + +- "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" +- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" +- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md new file mode 100644 index 0000000000000..1375602251d25 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -0,0 +1,59 @@ +--- +title: Acerca de la facturación para GitHub Packages +intro: 'Si quieres utilizar {% data variables.product.prodname_registry %} con más almacenamiento o transferencia de datos de los que se incluyen en tu cuenta, se te cobrará por este uso adicional.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +### Acerca de la facturación para {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.packages-billing %} + +{% data reusables.package_registry.packages-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)". + +{% data reusables.package_registry.container-registry-beta-billing-note %} + +La transferencia de datos se restablece cada mes, pero no así el uso de almacenamiento. + +| Producto | Almacenamiento | Transferencia de datos (por mes) | +| --------------------------------------------------------------------- | -------------- | -------------------------------- | +| {% data variables.product.prodname_free_user %} | 500MB | 1GB | +| {% data variables.product.prodname_pro %} | 2GB | 10GB | +| {% data variables.product.prodname_free_team %} para organizaciones | 500MB | 1GB | +| {% data variables.product.prodname_team %} | 2GB | 10GB | +| {% data variables.product.prodname_ghe_cloud %} | 50GB | 100GB | + +Todos los datos de transferencia saliente, cuando se desencadenan mediante {% data variables.product.prodname_actions %}, y aquellos de transferencia entrante desde cualquier origen, son gratuitos. Determinamos que estás descargando paquetes mediante el uso de {% data variables.product.prodname_actions %} cuando ingresas en {% data variables.product.prodname_registry %} utilizando un `GITHUB_TOKEN`. + +| | Hospedado | Auto-Hospedado | +| --------------------------------------------- | --------- | -------------- | +| Acceso utilizando un `GITHUB_TOKEN` | Free | Free | +| Acceso utilizando un token de acceso personal | Free | $ | + +El uso de almacenamiento se comparte con los artefactos de compilación que produce {% data variables.product.prodname_actions %} para los repositorios que pertenecen a tu cuenta. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". + +{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. Si tu uso de cuenta sobrepasa estos límites y has configurado un límite de gastos mayor a $0, pagarás $0.25 USD por GB de almacenamiento y $0.50 USD por GB de transferencia de datos. + +Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, permite los gastos ilimitados, utiliza 150GB de almacenamiento, y tiene 50GB de transferencia de datos durante un mes, ésta tendrá un excedente de 148GB en el almacenamiento y de 40GB en transferencia de datos para ese mes. El excedente de almacenamiento costaría $0.25 por GB, o $37. El excedente para transferencia de datos costaría $0.50 por GB, o $20. + +Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu transferencia de datos al número de GB más cercano. + +{% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes. Por ejemplo, si utilizas 3 GB de almacenamiento durante 10 días de Marzo y 12 GB durante 21 días de Marzo, tu uso de almacenamiento sería: + +- 3 GB x 10 días x (24 horas por día) = 720 GB-Horas +- 12 GB x 21 días x (24 horas por día) = 6,048 GB-Horas +- 720 GB-Horas + 6,048 GB-Horas = 6,768 GB-Horas +- 6,768 GB-Horas/ (744 horas por mes) = 9.0967 GB-Meses + +Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Por lo tanto, tu uso de almacenamiento para marzo sería de 9.097 GB. + +Tu uso de {% data variables.product.prodname_registry %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %} + +### Acerca de los límites de gasto + +{% data reusables.package_registry.packages-spending-limit-detailed %} + +Para obtener más información sobre cómo administrar y cambiar el límite de gastos de tu cuenta, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)". + +{% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md new file mode 100644 index 0000000000000..26736be77ec71 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -0,0 +1,19 @@ +--- +title: Acerca de la facturación de los Patrocinadores de GitHub +intro: Recibirás la factura por tus patrocinios con el resto de tus características y productos pagos. +redirect_from: + - /articles/about-billing-for-github-sponsors +versions: + free-pro-team: '*' +--- + +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %} + +{% data reusables.dotcom_billing.view-all-subscriptions %} + +### Further reading + +- "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" +- "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md new file mode 100644 index 0000000000000..85bf3d9a0af3e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md @@ -0,0 +1,31 @@ +--- +title: Acerca de la facturación en GitHub +intro: 'Todo lo que compras en {% data variables.product.prodname_dotcom %} comparte la fecha de facturación, el método de pago y el recibo de tu cuenta.' +redirect_from: + - /articles/about-billing-on-github +versions: + free-pro-team: '*' +--- + +### Productos y características pagos + +Puedes actualizar tu cuenta personal u organización a una suscripción paga en cualquier momento. También puedes elegir comprar apps desde {% data variables.product.prodname_marketplace %} o actualizar el almacenamiento y el ancho de banda para {% data variables.large_files.product_name_long %}. Para obtener más información, consulta: +- "[Acerca de la facturación para las cuentas de {% data variables.product.product_name %}](/articles/about-billing-for-github-accounts)" +- "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)" +- "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)" +- "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)" + +### Administrar parámetros de facturación + +Debes administrar los parámetros de facturación, el método de pago y las características y los productos pagos para cada una de tus cuentas por separado. Puedes elegir pagar mensual o anualmente las características y los productos pagos de cada cuenta. Cada característica o producto pago asociado con una cuenta comparten una fecha de facturación, el método de pago y el recibo. + +{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %} + +Para obtener más información, consulta "[Administrar tus parámetros de facturación {% data variables.product.prodname_dotcom %}](/articles/managing-your-github-billing-settings)". + +### Further reading + +- "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" +- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" +- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" +- "[Administrar la facturación para {% data variables.product.prodname_sponsors %}](/articles/managing-billing-for-github-sponsors)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md new file mode 100644 index 0000000000000..e552b00e9da91 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md @@ -0,0 +1,32 @@ +--- +title: Acerca de las organizaciones para empresas de contratación +intro: 'Las empresas usan las organizaciones para colaborar en proyectos compartidos con varios propietarios y administradores. Puedes crear una organización para tu cliente, realizar un pago en su nombre, y entonces transferir la propiedad de la organización a tu cliente.' +redirect_from: + - /articles/about-organizations-for-resellers/ + - /articles/about-organizations-for-procurement-companies +versions: + free-pro-team: '*' +--- + +Para acceder a una organización, cada miembro debe iniciar sesión en su cuenta de usuario personal. + +Los miembros de la organización pueden tener diferentes roles, como *propietario* o *gerente de facturación*: + +- Los **Propietarios** tienen acceso administrativo completo a una organización y sus contenidos. +- Los **Gerentes de facturación** pueden administrar los parámetros de facturación y no pueden acceder a los contenidos de la organización. Los gerentes de facturación no se muestran en la lista de miembros de la organización. + +### Pagos y precios para las organizaciones + +No proporcionamos cotizaciones para los precios de las organizaciones. Puedes ver nuestros precios publicados para [organizaciones](https://github.com/pricing) y [Large File Storage de Git](/articles/about-storage-and-bandwidth-usage/). No ofrecemos descuentos para empresas de contratación ni para pedidos de renovación. + +Aceptamos pagos en dólares estadounidenses, aunque los usuarios finales pueden estar en cualquier parte del mundo. + +Aceptamos pagos mediante tarjeta de crédito y PayPal. No aceptamos pagos mediante factura ni orden de compra. + +Para una compra más fácil y más eficaz, recomendamos que las empresas de contratación configuren una facturación anual para las organizaciones de sus clientes. + +### Further reading + +- "[Crear una organización y pagar por ella en nombre de un cliente](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)" +- "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" +- "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md new file mode 100644 index 0000000000000..bfc68632b749b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md @@ -0,0 +1,36 @@ +--- +title: Acerca del precio por usuario +intro: 'Con el precio por usuario, las organizaciones pagan en función del tamaño del equipo para acceder a la colaboración de avanzada y a las herramientas de administración para equipos, y opcionalmente, controles de seguridad, cumplimiento e implementación.' +redirect_from: + - /articles/about-per-user-pricing +versions: + free-pro-team: '*' +--- + +Las organizaciones nuevas pueden crear proyectos de código abierto y públicos con {% data variables.product.prodname_free_team %} o [actualizarse]({% data variables.product.pricing_url %}) a un producto pago con el precio por usuario. + +Las organizaciones que usan una suscripción paga antes del 11 de mayo de 2016 pueden elegir permanecer en su plan existente por repositorio o cambiar al precio por usuario. Te notificaremos doce meses antes de cualquier cambio impuesto en tu suscripción. Para obtener más información sobre cómo cambiar tu suscripción, consulta "[Actualizar tu {% data variables.product.prodname_dotcom %} suscripción](/articles/upgrading-your-github-subscription)". + +Para obtener más información sobre los productos con precio por usuario, consulta "[Productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". + +### ¿Cuántas licencias necesito para mi organización? + +Los propietarios y miembros de las organizaciones deberán contar con una licencia individual por persona. Si has enviado una invitación pendiente para un miembro prospecto de una organización, ésta tomará una licencia. {% data reusables.organizations.org-invite-expiration %} + +Los colaboradores externos y cuentas bot contarán en el total de las licencias pagadas de tu organización si se les da acceso a un repositorio privado. + +### ¿Cómo puedo añadir o bajar de categoría a las licencias pagadas de mi organización? + +Puedes añadir licencias pagadas a tu organización en cualquier momento. Si pagas por más licencias de las que utilizas, también puedes eliminar las licencias pagadas de tu organización. Para obtener más información, consulta "[Actualizar tu suscripción de {% data variables.product.prodname_dotcom %}](/articles/upgrading-your-github-subscription)" y "[Bajar de categoría tu suscripción de {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-subscription)". + +Si tienes consultas acerca de la suscripción de tu organización, comunícate con {% data variables.contact.contact_support %}. + +### Si mantengo mi organización en un plan por repositorio, ¿puedo actualizar o bajar de categoría a un plan de repositorio diferente? + +Puedes actualizar o bajar de categoría entre planes pagos heredados en los parámetros de facturación de tu organización. Cuando te actualizas a un plan con más repositorios privados, inmediatamente moveremos tu cuenta a tu nuevo plan y te facturaremos la diferencia en el precio, prorrateado por la cantidad de días que quedan en tu ciclo de facturación. + +Cuando bajas de categoría a un plan pago heredado con menos repositorios privados, tu nuevo plan entrará en vigencia en tu próxima fecha de facturación. Si tienes más repositorios privados de los que permite tu nuevo plan, tus repositorios privados se bloquearán cuando tu nuevo plan entre en vigencia. Para reducir la cantidad de repositorios privados, puedes hacer que algunos de tus repositorios privados sean públicos o puedes clonar tus repositorios privados localmente y eliminar las copias en {% data variables.product.prodname_dotcom %}. + +### Further reading + +- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md new file mode 100644 index 0000000000000..cb829cbe886df --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md @@ -0,0 +1,46 @@ +--- +title: Agregar información a tus recibos +intro: 'Puedes agregar información adicional a tus recibos de {% data variables.product.product_name %}, como información fiscal o contable solicitada por tu empresa o país.' +redirect_from: + - /articles/can-i-add-my-credit-card-number-to-my-receipts/ + - /articles/can-i-add-extra-information-to-my-receipts--2/ + - /articles/how-can-i-add-extra-information-to-my-receipts/ + - /articles/could-you-add-my-card-number-to-my-receipts/ + - /articles/how-can-i-add-extra-information-to-my-personal-account-s-receipts/ + - /articles/adding-information-to-your-personal-account-s-receipts/ + - /articles/how-can-i-add-extra-information-to-my-organization-s-receipts/ + - /articles/adding-information-to-your-organization-s-receipts/ + - /articles/adding-information-to-your-receipts +versions: + free-pro-team: '*' +--- + +Tus recibos incluyen tu suscripción de {% data variables.product.prodname_dotcom %} así como otras suscripciones para [otras funciones y productos remunerados](/articles/about-billing-on-github). + +{% warning %} + +**Advertencia**: Por motivos de seguridad, recomendamos enfáticamente no incluir información confidencial o financiera (como número de tarjeta de crédito) en tus recibos. + +{% endwarning %} + +### Agregar información a tus recibos de cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.payment-info-tab %} +{% data reusables.dotcom_billing.extra_info_receipt %} + +### Agregar información a los recibos de tu organización + +{% note %} + +**Nota**: {% data reusables.dotcom_billing.org-billing-perms %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.payment-info-tab %} +{% data reusables.dotcom_billing.extra_info_receipt %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md new file mode 100644 index 0000000000000..748b4aa1869c9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md @@ -0,0 +1,44 @@ +--- +title: Agregar o eliminar un método de pago +intro: Puedes agregar un método de pago a tu cuenta o actualizar el método de pago existente de tu cuenta en cualquier momento. +redirect_from: + - /articles/updating-your-personal-account-s-payment-method/ + - /articles/how-do-i-update-my-credit-card/ + - /articles/updating-your-account-s-credit-card/ + - /articles/updating-your-personal-account-s-credit-card/ + - /articles/updating-your-personal-account-s-paypal-information/ + - /articles/does-github-provide-invoicing/ + - /articles/switching-payment-methods-for-your-personal-account/ + - /articles/paying-for-your-github-organization-account/ + - /articles/updating-your-organization-s-credit-card/ + - /articles/updating-your-organization-s-paypal-information/ + - /articles/updating-your-organization-s-payment-method/ + - /articles/switching-payment-methods-for-your-organization/ + - /articles/adding-or-editing-a-payment-method +versions: + free-pro-team: '*' +--- + +{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %} + +No entregamos facturas u órdenes de compra de respaldo a cuentas personales. Enviamos recibos por correo electrónico mensual o anualmente a la fecha de facturación de tu cuenta. Si tu empresa, país o contador necesita que tus recibos sean más detallados, también puedes [agregar información adicional](/articles/adding-information-to-your-personal-account-s-receipts) a tus recibos. + +### Actualizar el método de pago de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.update_payment_method %} +{% data reusables.dotcom_billing.enter-payment-info %} + +### Actualizar el método de pago de tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +Si tu organización está fuera de los EE. UU. o si estás usando una cuenta corriente corporativa para pagar {% data variables.product.product_name %}, PayPal puede ser un método de pago útil. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.update_payment_method %} +{% data reusables.dotcom_billing.enter-payment-info %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md new file mode 100644 index 0000000000000..bbc84e4dd0c64 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md @@ -0,0 +1,56 @@ +--- +title: Cancelar una app Mercado GitHub +intro: 'Puedes cancelar y eliminar una app {% data variables.product.prodname_marketplace %} desde tu cuenta en cualquier momento.' +redirect_from: + - /articles/canceling-an-app-for-your-personal-account/ + - /articles/canceling-an-app-for-your-organization/ + - /articles/canceling-a-github-marketplace-app +versions: + free-pro-team: '*' +--- + +Al cancelar una app, tu suscripción se mantiene activa hasta el final de tu ciclo de facturación actual. La cancelación entra en vigencia en tu siguiente fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +Cuando cancelas una prueba gratis de un plan pago, tu suscripción se cancela inmediatamente y perderás acceso a la app. Si no cancelas tu prueba gratis dentro del período de pago, el método de pago en el registro de tu cuenta se cargará para el plan que elegiste al final del período de prueba. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +{% data reusables.marketplace.downgrade-marketplace-only %} + +### Cancelar una app en tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.cancel-app-billing-settings %} +{% data reusables.marketplace.cancel-app %} + +### Cancelar una prueba gratis para una app en tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.cancel-free-trial-billing-settings %} +{% data reusables.marketplace.cancel-app %} + +### Cancelar una app para tu organización + +{% data reusables.marketplace.marketplace-org-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.cancel-app-billing-settings %} +{% data reusables.marketplace.cancel-app %} + +### Cancelar una prueba gratis para una app en tu organización + +{% data reusables.marketplace.marketplace-org-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.cancel-free-trial-billing-settings %} +{% data reusables.marketplace.cancel-app %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md new file mode 100644 index 0000000000000..dbca86087aba4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md @@ -0,0 +1,40 @@ +--- +title: Cambiar la duración de tu ciclo de facturación +intro: Puedes pagar la suscripción de tu cuenta y otras características y productos remunerados en un ciclo de facturación mensual o anual. +redirect_from: + - /articles/monthly-and-yearly-billing/ + - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account/ + - /articles/switching-between-monthly-and-yearly-billing-for-your-organization/ + - /articles/changing-the-duration-of-your-billing-cycle +versions: + free-pro-team: '*' +--- + +Al cambiar la duración de tu ciclo de facturación, tu suscripción a {% data variables.product.prodname_dotcom %}, junto con otras características y productos remunerados, se moverán al nuevo ciclo de facturación en tu próxima fecha de facturación. + +### Cambiar la duración del ciclo de facturación de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.change_plan_duration %} +{% data reusables.dotcom_billing.confirm_duration_change %} + +### Cambiar la duración del ciclo de facturación de tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +#### Cambiar la duración de una suscripción por usuario + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.change_plan_duration %} +{% data reusables.dotcom_billing.confirm_duration_change %} + +#### Cambiar la duración de un plan heredado por repositorio + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.billing %} +4. En "Billing overview" (Resumen de facturación), haz clic en **Change plan** (Cambiar plan). ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/billing_overview_change_plan.png) +5. En el ángulo superior derecho, haz clic en **Switch to monthly billing** (Cambiar a facturación mensual) o **Switch to yearly billing** (Cambiar a facturación mensual). ![Sección de información de facturación](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md new file mode 100644 index 0000000000000..e161f6d645b23 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md @@ -0,0 +1,96 @@ +--- +title: Crear una organización y pagar por ella en nombre de un cliente +intro: 'Puedes crear una organización {% data variables.product.prodname_dotcom %} y pagar por ella en nombre de un cliente.' +redirect_from: + - /articles/creating-and-paying-for-an-organization-on-behalf-of-a-client +versions: + free-pro-team: '*' +--- + +### Requisitos + +Antes de comenzar, asegúrate de saber lo siguiente: +- El nombre de usuario {% data variables.product.prodname_dotcom %} del cliente que se convertirá en el propietario de la organización que creaste +- El nombre que tu cliente deseará usar para la organización +- La dirección de correo electrónico a la que deseas que se envíen los recibos +- El [producto](/articles/github-s-products) que tu cliente desea comprar +- El número de [asientos pagos](/articles/about-per-user-pricing/) que tu cliente desea comprar para la organización + +### Paso 1: Crea tu cuenta personal de {% data variables.product.prodname_dotcom %}. + +Usarás tu cuenta personal para configurar la organización. También necesitarás iniciar sesión en esta cuenta para renovar la suscripción de tu cliente o hacer cambios en ella en el futuro. + +Si ya posees una cuenta de usuario de {% data variables.product.prodname_dotcom %}, omite el [paso 2](#step-2-create-the-organization). + +1. Dirígete a la página [Unirse a GitHub](https://github.com/join). +2. En "Crear tu cuenta personal", escribe tu nombre de usuario, dirección de correo electrónico y contraseña, y luego haz clic en **Crear una cuenta**. ![Crear el formulario de ingreso a una cuenta personal](/assets/images/help/billing/billing_create_your_personal_account_form.png) +3. Selecciona {% data variables.product.prodname_free_user %} para tu cuenta personal. +4. Haz clic en **Finalizar registración**. + +### Paso 2: Crea la organización. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +3. Dentro de "Choose a plan" (Elegir un plan), haz clic en **Choose (Elegir) {% data variables.product.prodname_free_team %}**. Actualizarás la organización en el próximo paso. +{% data reusables.organizations.organization-name %} +5. Debajo de "Contact email" (Correo electrónico de contacto), escribe una dirección de correo electrónico de contacto para tu cliente. ![Campo para el correo electrónico de contacto](/assets/images/help/organizations/contact-email-field.png) +{% data reusables.dotcom_billing.owned_by_business %} +8. Da clic en **Siguiente**. + +### Paso 3: Actualiza la organización para que tenga una suscripción anual paga. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.upgrade_org %} +{% data reusables.dotcom_billing.choose_org_plan %} (Puedes agregar más asientos a la organización en el siguiente paso). +6. En "Actualizar resumen", selecciona **Pago anual** para pagar por la organización de forma anual. ![Botón de selección para la facturación anual](/assets/images/help/billing/choose-annual-billing-org-resellers.png) +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.add-payment-method %} +1. En "Pagar con" escribe los datos de tu tarjeta de crédito.![Formulario para ingresar datos de tarjeta de crédito](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png) +1. Haz clic en **Actualizar tarjeta de crédito**. +{% data reusables.dotcom_billing.finish_upgrade %} + +### Paso 4: Actualiza el número de asientos pagos de la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.add-seats %} +{% data reusables.dotcom_billing.number-of-seats %} +{% data reusables.dotcom_billing.confirm-add-seats %} + +### Paso 5: Invita a tu cliente a unirse a la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +5. Escribe el nombre de usuario de {% data variables.product.prodname_dotcom %} de tu cliente y presiona **Enter**. ![Campo para escribir el nombre de usuario de tu cliente](/assets/images/help/organizations/org-invite-modal.png) +6. Elige el rol de *propietario* para tu cliente y luego haz clic en **Enviar invitación**. ![Botón de selección para el propietario y botón para enviar invitación](/assets/images/help/organizations/add-owner-send-invite-reseller.png) +7. Tu cliente recibirá un correo electrónico en el que se lo invitará a unirse a la organización. Será necesario que acepte la invitación para que puedas continuar con el paso siguiente. + +### Paso 6: Transfiere la propiedad de la organización a tu cliente. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Verifica que tu cliente se encuentre en la lista de miembros de la organización y tenga el rol de *propietario* asignado. +5. A la derecha de tu nombre de usuario, usa el menú desplegable {% octicon "gear" aria-label="The Settings gear" %} y haz clic en **Administrar**. ![Enlace de acceso al gerente](/assets/images/help/organizations/member-manage-access.png) +6. A la izquierda, haz clic en **Eliminar de la organización**. ![Botón para eliminar de la organización ](/assets/images/help/organizations/remove-from-org-button.png) +7. Confirma tu opción y haz clic en **Eliminar miembros**. ![Botón para confirmar la eliminación de miembros](/assets/images/help/organizations/confirm-remove-from-org.png) + +### Pasos siguientes + +1. Ponte en contacto con tu cliente y pídele que [te agregue a la organización como gerente de facturación](/articles/adding-a-billing-manager-to-your-organization). Será necesario que seas un gerente de facturación de la organización para que puedas renovar la suscripción de tu cliente o hacer cambios en esta en el futuro. +2. Si deseas que la tarjeta de crédito de tu organización se elimine de la organización para que no vuelvan a hacerse cargos en ella, ponte en contacto con {% data variables.contact.contact_support %}. +3. Cuando sea el momento de renovar la suscripción paga de tu cliente, consulta "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)". + +### Further reading + +- "[Acerca de las organizaciones para empresas de contratación](/articles/about-organizations-for-procurement-companies)" +- "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" +- "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md new file mode 100644 index 0000000000000..068e8c5831117 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -0,0 +1,35 @@ +--- +title: Suscripciones con descuentos para cuentas GitHub +intro: '{% data variables.product.product_name %} ofrece descuentos a estudiantes, educadores, instituciones educativas, bibliotecas y organizaciones sin fines de lucro.' +redirect_from: + - /articles/discounted-personal-accounts/ + - /articles/discounted-organization-accounts/ + - /articles/discounted-billing-plans/ + - /articles/discounted-subscriptions-for-github-accounts +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia**: Los descuentos para {% data variables.product.prodname_dotcom %} no se tienen vigencia para las suscripciones de otros productos y características pagos. + +{% endtip %} + +### Descuentos para cuentas personales + +Además del número ilimitado de repositorios públicos y privados para estudiantes y miembros del cuerpo docente con {% data variables.product.prodname_free_user %}, los estudiantes validados pueden solicitar el {% data variables.product.prodname_student_pack %} para recibir beneficios adicionales ofrecidos por los socios de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Postularse para un paquete de desarrollo para estudiantes](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)". + +### Descuentos para escuelas y universidades + +Los miembros del cuerpo docente validados pueden solicitar {% data variables.product.prodname_team %} para la enseñanza y la investigación académica. Para obtener más información, consulta la sección "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)". Para obtener más información, consulta "[Usar {{ site.data.variables.product.prodname_dotcom }} en tu clase y en tu investigación](/articles/using-github-in-your-classroom-and-research)". Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/). + +### Descuentos para bibliotecas y organizaciones sin fines de lucro + +{% data variables.product.product_name %}proporciona {% data variables.product.prodname_team %} gratuito para organizaciones y cuenta con repositorios privados ilimitados, colaboradores ilimitados, y un juego completo de características a organizaciones y bibliotecas que califiquen como 501(c)3 (o equivalentes). Puedes solicitar un descuento para tu organización en [nuestra página de organizaciones sin fines de lucro](https://github.com/nonprofit). + +Si tu organización ya tiene una suscripción paga, la última transacción de tu organización se reembolsará una vez que se haya aplicado tu descuento para organizaciones sin fines de lucro. + +### Further reading + +- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md new file mode 100644 index 0000000000000..19581a2e60f24 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -0,0 +1,30 @@ +--- +title: Bajar de categoría un patrocinio +intro: Puedes bajar de categoría un patrocinio y llevarlo a un nivel inferior, o bien cancelar tu patrocinio. +redirect_from: + - /articles/downgrading-a-sponsorship +versions: + free-pro-team: '*' +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +### Acerca de las degradaciones de patrocinios + +Cuando bajas de categoría o cancelas un patrocinio, el cambio entra en vigencia en tu próxima fecha de facturación. {% data reusables.sponsors.no-refunds %} + +### Bajar de categoría un patrocinio + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.select-a-tier %} +{% data reusables.sponsors.update-sponsorship %} + +### Cancelar un patrocinio + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.sponsors.billing-switcher %} +{% data reusables.user_settings.subscriptions-tab %} +3. Debajo de "{% data variables.product.prodname_sponsors %}", a la derecha del contribuyente de código abierto, da clic en {% octicon "triangle-down" aria-label="The down triangle octicon" %} a un costado de tu cantidad patrocinada. Posteriormente, da clic en **Cancelar patrocinio**. ![Botón Cancelar patrocinio](/assets/images/help/billing/edit-sponsor-billing.png) +4. Revisa la información acerca de la cancelación de tu patrocinio y luego haz clic en **Aceptar**. ![Casilla de confirmación de cancelación](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md new file mode 100644 index 0000000000000..a9a4d6c861c67 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md @@ -0,0 +1,67 @@ +--- +title: Bajar de categoría Large File Storage de Git +intro: 'Puedes bajar de categoría y modificar el ancho de banda para {% data variables.large_files.product_name_short %} aplicando incrementos de 50 GB por mes.' +redirect_from: + - /articles/downgrading-storage-and-bandwidth-for-a-personal-account/ + - /articles/downgrading-storage-and-bandwidth-for-an-organization/ + - /articles/downgrading-git-large-file-storage +versions: + free-pro-team: '*' +--- + +Si bajas de categoría tu cantidad de paquetes de datos, tu cambio entrará en vigencia en tu próxima fecha de facturación. Para obtener más información, consulta " +[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)".

+ + + +### Bajar de categoría y reducir el ancho de banda para una cuenta personal + +{% data reusables.user_settings.access_settings %} + + + +{% data reusables.user_settings.billing %} + + + +{% data reusables.user_settings.subscriptions-tab %} + + + +{% data reusables.dotcom_billing.lfs-remove-data %} + + + +{% data reusables.large_files.downgrade_data_packs %} + + + +### Bajar de categoría y reducir el ancho de banda para una organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} + + + +{% data reusables.profile.access_org %} + + + +{% data reusables.organizations.org_settings %} + + + +{% data reusables.organizations.billing %} + + + +{% data reusables.user_settings.subscriptions-tab %} + + + +{% data reusables.dotcom_billing.lfs-remove-data %} + + + +{% data reusables.large_files.downgrade_data_packs %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md new file mode 100644 index 0000000000000..0f958087f58b2 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md @@ -0,0 +1,40 @@ +--- +title: Bajar de categoría el plan de facturación para la app Mercado GitHub +intro: 'Si deseas usar un plan de facturación diferente, puedes bajar de categoría tu app {% data variables.product.prodname_marketplace %} en cualquier momento.' +redirect_from: + - /articles/downgrading-an-app-for-your-personal-account/ + - /articles/downgrading-an-app-for-your-organization/ + - /articles/downgrading-the-billing-plan-for-a-github-marketplace-app +versions: + free-pro-team: '*' +--- + +Cuando bajas de categoría una app, tu suscripción permanece activa hasta el final de tu ciclo de facturación actual. El cambio entra en vigencia en tu próxima fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +{% data reusables.marketplace.downgrade-marketplace-only %} + +### Bajar de categoría una app para tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.marketplace.downgrade-app-billing-settings %} +{% data reusables.marketplace.choose-new-plan %} +{% data reusables.marketplace.choose-new-quantity %} +{% data reusables.marketplace.issue-plan-changes %} + +### Bajar de categoría una app para tu organización + +{% data reusables.marketplace.marketplace-org-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.marketplace.downgrade-app-billing-settings %} +{% data reusables.marketplace.choose-new-plan %} +{% data reusables.marketplace.choose-new-quantity %} +{% data reusables.marketplace.issue-plan-changes %} + +### Further reading + +- "[Cancelar una app {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md new file mode 100644 index 0000000000000..94024496132f7 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md @@ -0,0 +1,90 @@ +--- +title: Bajar de categoría tu suscripción de GitHub +intro: 'Puedes bajar tu suscripción de nivel para cualquier tipo de cuenta de {% data variables.product.product_name %} en cualquier momento.' +redirect_from: + - /articles/downgrading-your-personal-account-s-billing-plan/ + - /articles/how-do-i-cancel-my-account/ + - /articles/downgrading-a-user-account-to-free/ + - /articles/removing-paid-seats-from-your-organization/ + - /articles/downgrading-your-organization-s-paid-seats/ + - /articles/downgrading-your-organization-s-billing-plan/ + - /articles/downgrading-an-organization-with-per-seat-pricing-to-free/ + - /articles/downgrading-an-organization-with-per-repository-pricing-to-free/ + - /articles/downgrading-your-organization-to-free/ + - /articles/downgrading-your-organization-from-the-business-plan-to-the-team-plan/ + - /articles/downgrading-your-organization-from-github-business-cloud-to-the-team-plan/ + - /articles/downgrading-your-github-billing-plan/ + - /articles/downgrading-your-github-subscription +versions: + free-pro-team: '*' +--- + +### Bajar de nivel tu suscripción de {% data variables.product.product_name %} + +Cuando bajas de nivel tu suscricpión de cuenta de usuario o de organización, los precios y características cambian y toman efecto en tu siguiente fecha de facturación. Los cambios a tu suscripción de cuenta de usuario u organización no afectan aquellas suscripciones o pagos para otras características pagadas de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[¿Cómo afecta subir o bajar de categoría el proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)." + +### Bajar de nivel tu suscripción de cuenta de usuario + +Si bajas tu cuenta de usuario de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, esta perderá acceso a las herramientas avanzadas de revisión de código en los repositorios privados. {% data reusables.gated-features.more-info %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +4. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Downgrade to Free** (Bajar de categoría a Gratis). ![Botón Downgrade to free (Bajar de categoría a gratis)](/assets/images/help/billing/downgrade-to-free.png) +5. Lee la información sobre de las características a las cuales perderá acceso tu cuenta de usuario en tu siguiente fecha de facturación, y luego da clic en **Entiendo. Bajar de nivel**. ![Botón de proceder con la baja de categoría](/assets/images/help/billing/continue-with-downgrade.png) + +Si publicaste un sitio de {% data variables.product.prodname_pages %} en un repositorio privado y añadiste un dominio personalizado, retira o actualiza tus registros de DNS antes de bajarlo de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, para evitar el riesgo de que te ganen el dominio. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +### Bajar de nivel tu suscripción de orgnización + +{% data reusables.dotcom_billing.org-billing-perms %} + +Si bajas tu organización de nivel desde {% data variables.product.prodname_team %} a {% data variables.product.prodname_free_team %} para organizaciones, la cuenta perderá acceso a las herramientas de administración y colaboración para equipos. + +Si bajas a tu organización de nivel desde {% data variables.product.prodname_ghe_cloud %} a {% data variables.product.prodname_team %} o {% data variables.product.prodname_free_team %}, la cuenta perderá acceso a los controles avanzados de seguridad, cumplimiento y despliegue. {% data reusables.gated-features.more-info %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +6. Utiliza el menú desplegable de **Editar** y da clic en la opción a la cual desees bajar. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-option-button.png) +{% data reusables.dotcom_billing.confirm_cancel_org_plan %} + +### Bajar de nivel la suscripción de una organización con precios tradicionales por repositorio + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta la sección "[Cambiar a tu organización de precios por repositorio a precios por usuario](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Debajo de "Suscripciones", selecciona el menú desplegable de "Editar" y da clic en **Editar plan**. ![Menú desplegable de Editar Plan](/assets/images/help/billing/edit-plan-dropdown.png) +1. Debajo de "Facturación/Planes", a un costado del plan que quieras cambiar, da clic en **Bajar categoría**. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-plan-option-button.png) +1. Ingresa la razón por la cual estás degradando tu cuenta y luego haz clic en **Degradar plan**. ![Caja de texto para la razón de degradar la versión y botón de degradar](/assets/images/help/billing/downgrade-plan-button.png) + +### Eliminar asientos pagos de tu organización + +Para reducir el número de asientos pagos que usa tu organización, puedes eliminar miembros de tu organización o convertirlos en colaboradores externos y darles acceso únicamente a los repositorios públicos. Para obtener más información, consulta: +- "[Eliminar un miembro de tu organización](/articles/removing-a-member-from-your-organization)" +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +6. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Remove seats** (Eliminar asientos). ![menú desplegable para eliminar plazas](/assets/images/help/billing/remove-seats-dropdown.png) +1. En "Eliminar asientos" selecciona el número de asientos pagos de la categoría a la que deseas bajar. ![opción de eliminar plazas](/assets/images/help/billing/remove-seats-amount.png) +1. Revisa la información sobre tu nuevo pago en tu siguiente fecha de facturación, posteriormente, da clic en **Eliminar plazas**. ![botón de eliminar plazas](/assets/images/help/billing/remove-seats-button.png) + +### Further reading + +- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" +- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". +- "[Eliminar un método de pago](/articles/removing-a-payment-method)" +- "[Acerca del precio por usuario](/articles/about-per-user-pricing)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md new file mode 100644 index 0000000000000..c90e7a3291948 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md @@ -0,0 +1,35 @@ +--- +title: '¿Cómo impacta subir o bajar de categoría en el proceso de facturación?' +intro: 'Cuando subes de categoría la suscripción de tu cuenta personal u organización, las modificaciones se aplican de inmediato. Cuando bajas de categoría tu suscripción, las modificaciones se aplican al final de tu ciclo de facturación actual.' +redirect_from: + - /articles/how-does-upgrading-or-downgrading-affect-the-billing-process +versions: + free-pro-team: '*' +--- + +Los cambios en tu suscripción pagada de cuenta de usuario u organización no afectan las suscripciones o pagos de otras características pagadas de {% data variables.product.prodname_dotcom %}, tales como {% data variables.large_files.product_name_long %} o aplicaciones pagadas que compraste en {% data variables.product.prodname_marketplace %}. + +Para obtener más información, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" y "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." + +#### Ejemplo de cancelación de una suscripción paga de una cuenta personal u organización + +Kumiko paga una suscripción mensual el día 5 de cada mes. Si Kimiko se baja de categoría de la suscripción pagada a {% data variables.product.prodname_free_user %} en el 10 de octubre, su suscripción se mantendrá efectiva hasta el final de su ciclo actual de facturación en el 4 de noviembre. En el 5 de noviembre, su cuenta se migrará a {% data variables.product.prodname_free_user %}. + +#### Ejemplo de cambiar de una suscripción anual a una mensual para una cuenta personal u organización + +Ravi paga una suscripción anual el 5 de octubre de cada año. Si el 10 de diciembre Ravi cambia de una facturación anual a una mensual, su cuenta sigue en la suscripción anual hasta el final de su ciclo de facturación actual, el 4 de octubre del siguiente año. El 5 de octubre del siguiente año, a Ravi se le cobrará por un servicio mensual. Su próxima fecha de facturación será el 5 de noviembre. + +#### Ejemplo de agregar asientos pagos a tu organización + +La organización de Mada paga por 25 asientos el día 15 de cada mes. Si el 4 de junio Mada agrega diez asientos pagos, de inmediato se le cobrará a su organización un monto prorrateado por los diez asientos adicionales por el tiempo que transcurre entre el 4 y el 14 de junio, y los asientos estarán disponibles de inmediato para el uso. El 15 de junio, la organización de Mada pagará por 35 asientos. + +#### Ejemplo de eliminar asientos pagos de tu organización + +La organización de Stefan paga por 50 asientos el 20 de mayo de cada año. Si Stefan elimina 20 asientos y baja de categoría a un nuevo total de 30 asientos pagos el 30 de septiembre, su organización puede seguir accediendo a sus 50 asientos pagos hasta el final de su ciclo de facturación actual, el 19 de mayo. El 20 de mayo, entrará en vigor la categoría más baja, la organización de Stefan pagará por 30 asientos y tendrá acceso a 30 asientos pagos. + +### Further reading + +- "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" +- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" +- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" +- "[Acerca del precio por usuario](/articles/about-per-user-pricing)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md new file mode 100644 index 0000000000000..449bf800bc21d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md @@ -0,0 +1,59 @@ +--- +title: Configurar y administrar la facturación y los pagos en GitHub +shortTitle: Facturación y pagos +redirect_from: + - /categories/setting-up-and-managing-billing-and-payments-on-github +versions: + free-pro-team: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-your-github-billing-settings %} + {% link_in_list /about-billing-on-github %} + {% link_in_list /viewing-your-subscriptions-and-billing-date %} + {% link_in_list /adding-or-editing-a-payment-method %} + {% link_in_list /viewing-your-payment-history-and-receipts %} + {% link_in_list /adding-information-to-your-receipts %} + {% link_in_list /setting-your-billing-email %} + {% link_in_list /changing-the-duration-of-your-billing-cycle %} + {% link_in_list /redeeming-a-coupon %} + {% link_in_list /troubleshooting-a-declined-credit-card-charge %} + {% link_in_list /unlocking-a-locked-account %} + {% link_in_list /removing-a-payment-method %} +{% topic_link_in_list /managing-billing-for-your-github-account %} + {% link_in_list /about-billing-for-github-accounts %} + {% link_in_list /about-per-user-pricing %} + {% link_in_list /how-does-upgrading-or-downgrading-affect-the-billing-process %} + {% link_in_list /upgrading-your-github-subscription %} + {% link_in_list /viewing-and-managing-pending-changes-to-your-subscription %} + {% link_in_list /downgrading-your-github-subscription %} + {% link_in_list /discounted-subscriptions-for-github-accounts %} +{% topic_link_in_list /managing-billing-for-github-marketplace-apps %} + {% link_in_list /about-billing-for-github-marketplace %} + {% link_in_list /upgrading-the-billing-plan-for-a-github-marketplace-app %} + {% link_in_list /downgrading-the-billing-plan-for-a-github-marketplace-app %} + {% link_in_list /canceling-a-github-marketplace-app %} +{% topic_link_in_list /managing-billing-for-github-actions %} + {% link_in_list /about-billing-for-github-actions %} + {% link_in_list /viewing-your-github-actions-usage %} + {% link_in_list /managing-your-spending-limit-for-github-actions %} +{% topic_link_in_list /managing-billing-for-git-large-file-storage %} + {% link_in_list /about-billing-for-git-large-file-storage %} + {% link_in_list /viewing-your-git-large-file-storage-usage %} + {% link_in_list /upgrading-git-large-file-storage %} + {% link_in_list /downgrading-git-large-file-storage %} +{% topic_link_in_list /managing-billing-for-github-sponsors %} + {% link_in_list /about-billing-for-github-sponsors %} + {% link_in_list /upgrading-a-sponsorship %} + {% link_in_list /downgrading-a-sponsorship %} +{% topic_link_in_list /managing-billing-for-github-packages %} + {% link_in_list /about-billing-for-github-packages %} + {% link_in_list /viewing-your-github-packages-usage %} + {% link_in_list /managing-your-spending-limit-for-github-packages %} +{% topic_link_in_list /setting-up-paid-organizations-for-procurement-companies %} + {% link_in_list /about-organizations-for-procurement-companies %} + {% link_in_list /creating-and-paying-for-an-organization-on-behalf-of-a-client %} + {% link_in_list /upgrading-or-downgrading-your-clients-paid-organization %} + {% link_in_list /renewing-your-clients-paid-organization %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md new file mode 100644 index 0000000000000..4ef890bef0ed1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md @@ -0,0 +1,13 @@ +--- +title: Administrar la facturación para Large File Storage de Git +intro: 'Puedes ver el uso, la actualización y el cambio a una versión anterior{% data variables.large_files.product_name_long %}.' +redirect_from: + - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account/ + - /articles/managing-large-file-storage-and-bandwidth-for-your-organization/ + - /articles/managing-storage-and-bandwidth-usage/ + - /articles/managing-billing-for-git-large-file-storage +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md new file mode 100644 index 0000000000000..cdb1e6f876db6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md @@ -0,0 +1,8 @@ +--- +title: Administrar la facturación para GitHub Actions +intro: 'Puedes ver el uso y configurar un límite de gastos para {% data variables.product.prodname_actions %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md new file mode 100644 index 0000000000000..91c2d7bff3bfa --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md @@ -0,0 +1,12 @@ +--- +title: Administrar la facturación por las aplicaciones de Mercado GitHub +intro: 'Puedes actualizar, bajar de categoría, o cancelar aplicaciones {% data variables.product.prodname_marketplace %} en cualquier momento.' +redirect_from: + - /articles/managing-your-personal-account-s-apps/ + - /articles/managing-your-organization-s-apps/ + - /articles/managing-billing-for-github-marketplace-apps +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md new file mode 100644 index 0000000000000..92c9bbefed744 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md @@ -0,0 +1,8 @@ +--- +title: Administrar la facturación para GitHub Packages +intro: 'Puedes ver tu uso de {% data variables.product.prodname_registry %} y configurar un límite de gastos para {% data variables.product.prodname_registry %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md new file mode 100644 index 0000000000000..570ec8d09dcd3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md @@ -0,0 +1,10 @@ +--- +title: Administrar la facturación de Patrocinadores de GitHub +intro: Puedes actualizar o bajar de categoría el nivel de cada uno de tus patrocinadores. +mapTopic: verdadero +redirect_from: + - /articles/managing-billing-for-github-sponsors +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md new file mode 100644 index 0000000000000..de6c392bbdf2d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md @@ -0,0 +1,18 @@ +--- +title: Administrar la facturación para tu cuenta de GitHub +intro: '{% data variables.product.product_name %} ofrece productos gratuitos y pagos para cada cuenta. Puedes actualizar, bajar de categoría y visualizar los cambios pendientes de la suscripción de tu cuenta en cualquier momento.' +redirect_from: + - /categories/97/articles/ + - /categories/paying-for-user-accounts/ + - /articles/paying-for-your-github-user-account/ + - /articles/managing-billing-on-github/ + - /articles/changing-your-personal-account-s-billing-plan/ + - /categories/billing/ + - /categories/3/articles/ + - /articles/managing-your-organization-s-paid-seats/ + - /articles/managing-billing-for-your-github-account +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md new file mode 100644 index 0000000000000..0f1b620dadab1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md @@ -0,0 +1,16 @@ +--- +title: Administrar tus configuraciones de facturación de GitHub +intro: 'Las configuraciones de facturación de tu cuenta se aplican a cada característica paga o producto que agregas a la cuenta. Puedes administrar configuraciones como tu método de pago, el ciclo de facturación y el correo electrónico de facturación. También puedes visualizar la información de facturación como tu suscripción, la fecha de facturación, el historial de pagos y los recibos pasados.' +redirect_from: + - /articles/viewing-and-managing-your-personal-account-s-billing-information/ + - /articles/paying-for-user-accounts/ + - /articles/viewing-and-managing-your-organization-s-billing-information/ + - /articles/paying-for-organization-accounts/ + - /categories/paying-for-organization-accounts/articles/ + - /categories/99/articles/ + - /articles/managing-your-github-billing-settings +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md new file mode 100644 index 0000000000000..28cb039901100 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -0,0 +1,54 @@ +--- +title: Administrar tu límite de gastos para GitHub Actions +intro: 'Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' +--- + +### Acerca de los límites de gastos para {% data variables.product.prodname_actions %} + +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} + +{% data reusables.actions.actions-packages-set-spending-limit %}Para obtener más información acerca de los costos de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de los costos de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". + +Tan pronto como configures un límite de gastos diferente a $0, serás responsable de cualquier uso excedente que se suscite en el periodo de facturación actual. Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, no permite excedentes, y crea artefactos de flujo de trabajo que incrementan tu uso de almacenamiento para el mes en curso de 1.9GB a 2.1GB, utilizarás un poco más de almacenamiento que los 2Gb incluidos en tu producto. + +Ya que no has habilitado los excedentes, tu siguiente intento de crear un artefacto de un flujo de trabajo fallará. No recibirás una cuenta por esos 0.1GB extras en ese mes. Sin embargo, si habilitas los excedentes, tu primer factura incluirá el excedente de 0.1GB del ciclo de facturación actual, así como cualquier otro excedente que acumules. + +### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu cuenta de usuario + +Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_actions %} para su propia cuenta de usuario. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.cost-management-tab %} +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} + +### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu organización + +Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_actions %} para una organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.cost-management-tab %} +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} + +### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu cuenta empresarial + +Los propietarios de la empresa y gerentes de facturación pueden administrar el límite de gastos para {% data variables.product.prodname_actions %} para una cuenta empresarial. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +1. Debajo de " +uso mensual de Paquetes y {% data variables.product.prodname_actions %}", da clic en **Administración de costos**. + ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png) +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md new file mode 100644 index 0000000000000..ab30259d8d83c --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -0,0 +1,54 @@ +--- +title: Administrar tu límite de gastos para GitHub Packages +intro: 'Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_registry %}.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +### Acerca de los límites de gastos para {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.packages-billing %} + +{% data reusables.package_registry.packages-spending-limit-brief %} + +{% data reusables.actions.actions-packages-set-spending-limit %}Para obtener más información acerca de los costos de utilización de {% data variables.product.prodname_registry %}, consulta la sección "[Acerca de los costos de {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". + +Tan pronto como configures un límite de gastos diferente a $0, serás responsable de cualquier uso excedente que se suscite en el periodo de facturación actual. Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, no permite excedentes, y publica una nueva versión de un paquete privado que incrementa tu uso de almacenamiento para el mes en curso de 1.9GB a 2.1GB, la publicación de esta versión usará un poco más de los 2GB que se incluyen en tu paquete. + +Ya que no has habilitado los excedentes, tu siguiente intento de publicar una versión del paquete no será exitosa. No recibirás una cuenta por esos 0.1GB extras en ese mes. Sin embargo, si habilitas los excedentes, tu primer factura incluirá el excedente de 0.1GB del ciclo de facturación actual, así como cualquier otro excedente que acumules. + +### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu cuenta de usuario + +Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_registry %} para su propia cuenta de usuario. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.cost-management-tab %} +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} + +### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu organización + +Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_registry %} para una organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.cost-management-tab %} +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} + +### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu cuenta empresarial + +Los propietarios de la empresa y gerentes de facturación pueden administrar el límite de gastos para {% data variables.product.prodname_registry %} para una cuenta empresarial. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +1. Debajo de " +uso mensual de Paquetes y {% data variables.product.prodname_actions %}", da clic en **Administración de costos**. + ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png) +{% data reusables.dotcom_billing.monthly-spending-limit %} +{% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md new file mode 100644 index 0000000000000..f11893d8afafb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -0,0 +1,29 @@ +--- +title: Canjear un cupón +intro: 'Si tienes un cupón, puedes canjearlo por una suscripción {% data variables.product.prodname_dotcom %} paga.' +redirect_from: + - /articles/where-do-i-add-a-coupon-code/ + - /articles/redeeming-a-coupon-for-your-personal-account/ + - /articles/redeeming-a-coupon-for-organizations/ + - /articles/redeeming-a-coupon +versions: + free-pro-team: '*' +--- + +{% data variables.product.product_name %} no puede emitir un reembolso si pagas una cuenta antes de aplicar un cupón. Tampoco podemos transferir un cupón canjeado o entregarte un cupón nuevo si lo aplicas a la cuenta equivocada. Confirma que estás aplicando el cupón a la cuenta correcta antes de canjear un cupón. + +No puedes aplicar cupones a planes pagos de {% data variables.product.prodname_marketplace %} apps. + +### Canjear un cupón para tu cuenta personal + +{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %} +4. En "Redeem your coupon" (Canjear tu cupón), haz clic en **Choose** (Elegir) al lado del nombre de usuario de tu cuenta *personal*. ![Botón Choose (Elegir)](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png) +{% data reusables.dotcom_billing.redeem_coupon %} + +### Canjear un cupón para tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %} +4. En "Redeem your coupon" (Canjear tu cupón), haz clic en **Choose** (Elegir) al lado de la *organización* a la que quieras aplicarle el cupón. Si le quieres aplicar el cupón a una organización nueva que aún no existe, haz clic en **Create a new organization** (Crear una organización nueva). ![Botón Choose (Elegir)](/assets/images/help/settings/redeem-coupon-choose-button.png) +{% data reusables.dotcom_billing.redeem_coupon %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md new file mode 100644 index 0000000000000..7d80117328e9b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -0,0 +1,40 @@ +--- +title: Eliminar un método de pago +intro: 'Si no estás usando tu método de pago para ninguna suscripción paga en {% data variables.product.prodname_dotcom %}, puedes eliminar el método de pago para que no siga almacenado en tu cuenta.' +redirect_from: + - /articles/removing-a-credit-card-associated-with-your-user-account/ + - /articles/removing-a-payment-method-associated-with-your-user-account/ + - /articles/removing-a-credit-card-associated-with-your-organization/ + - /articles/removing-a-payment-method-associated-with-your-organization/ + - /articles/removing-a-payment-method +versions: + free-pro-team: '*' +--- + +Si vas a pagar tu {% data variables.product.product_name %} suscripción con un cupón y no vas a usar tu método de pago para ninguna [otra función o producto pago](/articles/about-billing-on-github) en {% data variables.product.product_name %}, puedes eliminar tu información de tarjeta de crédito o de PayPal. + +{% tip %} + +**Sugerencia:** Si [bajas la categoría de tu cuenta a producto gratuito](/articles/downgrading-your-github-subscription) y no tienes suscripciones a ninguna otra función o producto pago, eliminaremos automáticamente tu información de pago. + +{% endtip %} + +### Eliminar el método de pago de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.payment-info-tab %} +{% data reusables.dotcom_billing.remove-payment-method %} +{% data reusables.dotcom_billing.remove_payment_info %} + +### Eliminar el método de pago de tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.payment-info-tab %} +{% data reusables.dotcom_billing.remove-payment-method %} +{% data reusables.dotcom_billing.remove_payment_info %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md new file mode 100644 index 0000000000000..1c9c31207859d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md @@ -0,0 +1,27 @@ +--- +title: Renovar la organización paga de tu cliente +intro: 'Si la organización de tu cliente tiene un método de pago válido archivado, su suscripción anual se renovará automáticamente. Los gerentes de facturación pueden ver y actualizar el método de pago y la suscripción de la organización.' +redirect_from: + - /articles/renewing-your-client-s-paid-organization + - /articles/renewing-your-clients-paid-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.organizations.reseller-ask-to-become-billing-manager %} + +{% tip %} + +**Sugerencia**: Los gerentes de facturación también pueden [cambiar la cantidad de asientos pagos de la organización](/articles/upgrading-or-downgrading-your-client-s-paid-organization) en cualquier momento. + +{% endtip %} + +### Actualizar la tarjeta de crédito de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.update_payment_method %} +1. Escribe la información nueva de tu tarjeta de crédito en el formulario seguro. ![Formulario de información de tarjeta de crédito](/assets/images/help/settings/creditcard-billing-form.png) +1. Haz clic en **Update credit card** (Actualizar tarjeta de crédito) o **Save credit card** (Guardar tarjeta de crédito). diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md new file mode 100644 index 0000000000000..ae8e4f7e05eea --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md @@ -0,0 +1,12 @@ +--- +title: Configurar organizaciones remuneradas para empresas de contratación +intro: 'Si pagas por {% data variables.product.product_name %} en nombre de un cliente, puedes configurar sus parámetros de organización y pago para optimizar la conveniencia y la seguridad.' +redirect_from: + - /articles/setting-up-and-paying-for-organizations-for-resellers/ + - /articles/setting-up-and-paying-for-organizations-for-procurement-companies/ + - /articles/setting-up-paid-organizations-for-procurement-companies +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md new file mode 100644 index 0000000000000..1de9fc3fd9c22 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md @@ -0,0 +1,64 @@ +--- +title: Configurar tu correo electrónico de facturación +intro: 'El correo electrónico de facturación de tu cuenta es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación.' +redirect_from: + - /articles/setting-your-personal-account-s-billing-email/ + - /articles/can-i-change-what-email-address-received-my-github-receipt/ + - '/articles/how-do-i-change-the-billing-email,setting-your-billing-email/' + - /articles/setting-your-organization-s-billing-email/ + - /articles/setting-your-billing-email +versions: + free-pro-team: '*' +--- + +### Configurar el correo electrónico de facturación de tu cuenta personal + +El correo electrónico principal de tu cuenta personal es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación. + +Tu dirección principal de correo electrónico es el primer correo electrónico enumerado en las configuraciones de correo electrónico de tu cuenta. También utilizamos tu dirección principal de correo electrónico como nuestra dirección de correo electrónico de facturación. + +Si deseas cambiar tu correo electrónico de facturación, consulta "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)." + +### Configurar el correo electrónico de facturación de tu organización + +El correo electrónico de facturación de tu organización es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación. + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Dentro de **Billing email (Correo electrónico de facturación)**, escribe una dirección de correo electrónico válida. El correo electrónico no necesariamente debe ser único para la cuenta de la organización. ![Casilla de texto para el correo electrónico de facturación](/assets/images/help/settings/org-billing-email.png) +5. Para confirmar tus cambios, haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/settings/update-profile-button.png) + +### Administrar los destinatarios adicionales para tu correo electrónico de facturación de la organización + +Si tienes usuarios que quieran recibir reportes de facturación, puedes agregar sus direcciones de correo electrónico como destinatarios del correo de facturación. Esta característica se encuentra únicamente disponible para las organizaciones que no gestione una empresa. + +#### Agregar un destinatario para las notificaciones de facturación + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +1. Debajo de "Administración de facturación", a la derecha de "Destinatarios de correo electrónico", da clic en **Agregar**. ![Agregar destinatario](/assets/images/help/billing/billing-add-email-recipient.png) +1. Teclea la dirección de correo electrónico del destinatario y luego da clic en **Agregar**. ![Agregar modal de destinatario](/assets/images/help/billing/billing-add-email-recipient-modal.png) + +#### Cambiar el destinatario principal de las notificaciones de facturación + +Siempre debe existir una dirección designada como el destinatario principal. La dirección con esta designación no puede eliminarse hasta que se seleccione un destinatario primario. + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +1. Debajo de "Administración de facturación", encuentra la dirección de correo electrónico que quieras configurar como el destinatario principal. +1. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable de "Editar", y da clic en **Marcar como principal**. ![Marcar destinatario principal](/assets/images/help/billing/billing-change-primary-email-recipient.png) + +#### Eliminar un destinatario de las notificaciones de facturación + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +1. Debajo de "Destinatarios de correo electrónico", encuentra la dirección de correo electrónico que quieres eliminar. +1. Para la entrada del usuario en la lista, da clic en **Editar**. ![Editar destinatario](/assets/images/help/billing/billing-edit-email-recipient.png) +1. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable de "Editar", y da clic en *Eliminar**. ![Eliminar destinatario](/assets/images/help/billing/billing-remove-email-recipient.png) +1. Revisa el mensaje de confirmación y luego da clic en **Eliminar**. diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge.md new file mode 100644 index 0000000000000..c2cbb51e18684 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge.md @@ -0,0 +1,31 @@ +--- +title: Solucionar problemas de un pago de tarjeta de crédito rechazado +intro: 'Si se rechaza la tarjeta de crédito que utilizas para pagar {% data variables.product.product_name %}, puedes tomar varias medidas para asegurarte de que tus pagos se concreten y de no estar bloqueado de tu cuenta.' +redirect_from: + - /articles/what-do-i-do-if-my-card-is-declined/ + - /articles/troubleshooting-a-declined-credit-card-charge +versions: + free-pro-team: '*' +--- + +Si se rechaza tu tarjeta, te enviaremos un correo electrónico acerca del motivo por el que se rechazó el pago. Tendrás algunos días para resolver el problema antes de que tratemos de volver a cobrarte. + +### Verifica la fecha de vencimiento de tu tarjeta + +Si tu tarjeta está vencida, tendrás que actualizar la información de pago de tu cuenta. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". + +### Revisa la política de tu banco sobre restricciones de tarjetas + +Algunos bancos internacionales colocan restricciones en las transacciones internacionales, de comercio electrónico o automáticamente recurrentes. Si tienes problemas para hacer un pago con tu tarjeta de crédito internacional, llama a tu banco para ver si hay alguna restricción sobre tu tarjeta. + +También admitimos pagos por PayPal. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". + +### Contáctate con tu banco para obtener detalles acerca de la transacción + +Tu banco puede proporcionar más información acerca de los pagos rechazados si, específicamente, preguntas por la transacción que se intentó realizar. Si existen restricciones sobre tu tarjeta, y debes llamar al banco, proporciona la siguiente información: + +- **El monto que se te cobra.** El monto de tu suscripción aparece en tus recibos de cuenta. Para obtener más información, consulta "[Ver tu historial de pagos y tus recibos](/articles/viewing-your-payment-history-and-receipts)". +- **La fecha en que {% data variables.product.product_name %} te factura.** La fecha de facturación de tu cuenta aparece en tus recibos. +- **El número de Id. de tu transacción.** El Id. de transacción de tu cuenta aparece en tus recibos. +- **El nombre del vendedor.** El nombre del vendedor es {% data variables.product.prodname_dotcom %}. +- **El mensaje de error que te envió el banco con el pago rechazado.** Puedes encontrar el mensaje de error del banco en el correo electrónico que te enviamos cuando se rechaza un pago. diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account.md new file mode 100644 index 0000000000000..6722c33c533dd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account.md @@ -0,0 +1,24 @@ +--- +title: Desbloquear una cuenta bloqueada +intro: Las características pagadas de tu organización se bloquearán si tu pago no se recibe a tiempo debido a problemas de facturación. +redirect_from: + - /articles/what-happens-if-my-account-is-locked/ + - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-owe-anything-for-previous-time/ + - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-pay-backcharges/ + - /articles/what-happens-if-my-repository-is-locked/ + - /articles/unlocking-a-locked-personal-account/ + - /articles/unlocking-a-locked-organization-account/ + - /articles/unlocking-a-locked-account +versions: + free-pro-team: '*' +--- + +Puedes desbloquear y acceder a tu cuenta si actualizas el método de pago de tu organización y el estado final del pago. No te pediremos que pagues el tiempo transcurrido en modo bloqueado. + +Puedes bajar a tu organización de nivel a {% data variables.product.prodname_free_team %} para continuar con las mismas características avanzadas en los repositorios públicos. Para obtener más información, consulta la sección "[Bajar de nivel tu suscripción de {% data variables.product.product_name %}](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription)". + +### Desbloquear las características de una organización debido a un pago rechazado + +Si las características avanzadas de tu organización se bloquearon debido a un pago rechazado, necesitarás actualizar tu información de facturación para activar un cargo recién autorizado. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". + +Si se aprueba la información de facturación nueva, te cobraremos de inmediato el producto pago que elegiste. La organización se desbloqueará automáticamente cuando se haya realizado un pago exitoso. diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md new file mode 100644 index 0000000000000..0fdd55de4110e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -0,0 +1,21 @@ +--- +title: Subir de categoría un patrocinio +intro: Puedes subir de categoría tu patrocinio a un nivel superior. +redirect_from: + - /articles/upgrading-a-sponsorship +versions: + free-pro-team: '*' +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +### Acerca de las mejoras de los patrocinios + +Cuando subes de categoría tu nivel de patrocinio, el cambio entrará en vigor de inmediato. {% data reusables.sponsors.prorated-sponsorship %} + +### Subir de categoría un patrocinio + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.select-a-tier %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md new file mode 100644 index 0000000000000..f5a10b7de4cb5 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md @@ -0,0 +1,39 @@ +--- +title: Subir de categoría Git Large File Storage +intro: 'Puedes comprar más paquetes de datos para aumentar tu cuota de banda ancha mensual y la capacidad de almacenamiento total para {% data variables.large_files.product_name_short %}.' +redirect_from: + - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account/ + - /articles/purchasing-additional-storage-and-bandwidth-for-an-organization/ + - /articles/upgrading-git-large-file-storage +versions: + free-pro-team: '*' +--- + +### Comprar más almacenamiento y ancho de banda para una cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.lfs-add-data %} +{% data reusables.large_files.pack_selection %} +{% data reusables.large_files.pack_confirm %} + +### Comprar más almacenamiento y ancho de banda para una organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.lfs-add-data %} +{% data reusables.large_files.pack_selection %} +{% data reusables.large_files.pack_confirm %} + +### Further reading + +- "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)" +- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" +- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" +- "[Control de versiones de archivos grandes](/articles/versioning-large-files)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md new file mode 100644 index 0000000000000..0d18c8d90d0d0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md @@ -0,0 +1,42 @@ +--- +title: Subir o bajar de categoría la organización paga de tu cliente +intro: Los gerentes de facturación pueden subir o bajar de categoría la organización paga de un cliente en cualquier momento. +redirect_from: + - /articles/upgrading-or-downgrading-your-client-s-paid-organization + - /articles/upgrading-or-downgrading-your-clients-paid-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.organizations.reseller-ask-to-become-billing-manager %} + +{% tip %} + +**Tips**: +- Antes de subir de categoría la organización de tu cliente, puedes [ver o actualizar el método de pago archivado para la organización](/articles/adding-or-editing-a-payment-method). +- Estas indicaciones son para subir o bajar de categoría organizaciones en la *suscripción por asiento*. Si tu cliente paga {% data variables.product.product_name %} utilizando un plan *por repositorio heredado*, puedes subir o [bajar de categoría](/articles/downgrading-your-github-subscription) su plan heredado o [cambiar su organización a un precio por asiento](/articles/upgrading-your-github-subscription). + +{% endtip %} + +### Subir de categoría la cantidad de asientos pagos de una organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.add-seats %} +{% data reusables.dotcom_billing.number-of-seats %} +{% data reusables.dotcom_billing.confirm-add-seats %} + +Después de agregar asientos, al método de pago archivado para la organización se le cobrará un monto prorrateado en función de la cantidad de asientos que agregues y la cantidad de tiempo que quede en tu ciclo de facturación. + +### Bajar la categoría de la cantidad de asientos pagos de una organización a gratuita + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.downgrade-org-to-free %} +{% data reusables.dotcom_billing.confirm_cancel_org_plan %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md new file mode 100644 index 0000000000000..1b6615c1e63eb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md @@ -0,0 +1,36 @@ +--- +title: Subir de categoría el plan de facturación de una app del Mercado GitHub +intro: 'Puedes subir de categoría tu {% data variables.product.prodname_marketplace %} app a un plan diferente en cualquier momento.' +redirect_from: + - /articles/upgrading-an-app-for-your-personal-account/ + - /articles/upgrading-an-app-for-your-organization/ + - /articles/upgrading-the-billing-plan-for-a-github-marketplace-app +versions: + free-pro-team: '*' +--- + +Cuando subes de categoría una app, a tu método de pago se le cobra un monto prorrateado en función del tiempo restante hasta tu próxima fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". + +### Subir de categoría una app para tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.upgrade-app-billing-settings %} +{% data reusables.marketplace.choose-new-plan %} +{% data reusables.marketplace.choose-new-quantity %} +{% data reusables.marketplace.issue-plan-changes %} + +### Subir de categoría una app para tu organización + +{% data reusables.marketplace.marketplace-org-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.marketplace.upgrade-app-billing-settings %} +{% data reusables.marketplace.choose-new-plan %} +{% data reusables.marketplace.choose-new-quantity %} +{% data reusables.marketplace.issue-plan-changes %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md new file mode 100644 index 0000000000000..24fb6168984ee --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -0,0 +1,100 @@ +--- +title: Subir de categoría tu suscripción de GitHub +intro: 'Puedes subir de categoría la suscripción para cualquier tipo de {% data variables.product.product_name %} cuenta en cualquier momento.' +redirect_from: + - /articles/upgrading-your-personal-account-s-billing-plan/ + - /articles/upgrading-your-personal-account/ + - /articles/upgrading-your-personal-account-from-free-to-a-paid-account/ + - /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card/ + - /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal/ + - /articles/500-error-while-upgrading/ + - /articles/upgrading-your-organization-s-billing-plan/ + - /articles/changing-your-organization-billing-plan/ + - /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card/ + - /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal/ + - /articles/upgrading-your-organization-account/ + - /articles/switching-from-per-repository-to-per-user-pricing/ + - /articles/adding-seats-to-your-organization/ + - /articles/upgrading-your-github-billing-plan/ + - /articles/upgrading-your-github-subscription +versions: + free-pro-team: '*' +--- + +### Subir de categoría la suscripción de tu cuenta personal + +Puedes mejorar tu cuenta personal desde {% data variables.product.prodname_free_user %} a {% data variables.product.prodname_pro %} para obtener herramientas avanzadas de revisión de código en repositorios privados. {% data reusables.gated-features.more-info %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +4. Junto a " +{% data variables.product.prodname_free_user %}", da clic en **Mejorar**. + ![Botón para actualizar](/assets/images/help/billing/settings_billing_user_upgrade.png) +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.finish_upgrade %} + +### Subir de categoría la suscripción de tu organización + +Puedes mejorar a tu organización desde {% data variables.product.prodname_free_team %} para organizaciones a {% data variables.product.prodname_team %} para acceder a herramientas de administración y colaboración avanzadas para equipos, o mejorarla a {% data variables.product.prodname_ghe_cloud %} para tener controles adicionales de seguridad, cumplimiento y despliegue. {% data reusables.gated-features.more-info-org-products %} + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.upgrade_org %} +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} + +#### Próximos pasos para las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} + +Si mejoras a tu organización a {% data variables.product.prodname_ghe_cloud %}, puedes configurar la administración de accesos e identidad para la misma. Para obtener más información, consulta "[Administrar el inicio de sesión único de SAML para tu organización](/articles/managing-saml-single-sign-on-for-your-organization)". + +Si quisieras utilizar una cuenta empresarial con {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)". + +### Agregar asientos a tu organización + +Si quisieras que usuarios adicionales tengan acceso a los repositorios privados de {% data variables.product.prodname_team %} en tu organización, puedes comprar más plazas en cualquier momento. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.add-seats %} +{% data reusables.dotcom_billing.number-of-seats %} +{% data reusables.dotcom_billing.confirm-add-seats %} + +### Cambiar tu organización de precio por repositorio a precio por usuario + +{% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta "[Acerca de los precios por usuario](/articles/about-per-user-pricing)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. A la derecha de tu nombre de plan, utiliza el menú desplegable de **Editar** y selecciona **Editar plan**. ![Menú desplegable de editar](/assets/images/help/billing/per-user-upgrade-button.png) +6. A la derecha de "Herramientas avanzadas para equipos", da clic en **Mejorar ahora**. ![Botón de mejorar ahora](/assets/images/help/billing/per-user-upgrade-now-button.png) +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} + +### Solucionar problemas de un error 500 al subir de categoría + +{% data reusables.dotcom_billing.500-error %} + +### Further reading + +- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" +- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md new file mode 100644 index 0000000000000..94de153401e28 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md @@ -0,0 +1,39 @@ +--- +title: Ver y administrar cambios pendientes en tu suscripción +intro: Puedes ver y cancelar cambios pendientes en tus suscripciones antes de que se hagan efectivas en la próxima fecha de facturación. +redirect_from: + - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan/ + - /articles/viewing-and-managing-pending-changes-to-your-organization-s-billing-plan/ + - /articles/viewing-and-managing-pending-changes-to-your-billing-plan/ + - /articles/viewing-and-managing-pending-changes-to-your-subscription +versions: + free-pro-team: '*' +--- + +Puedes cancelar cambios pendientes en la suscripción de tu cuenta y cambios pendientes en tus suscripciones a otras funciones y productos pagos. + +Cuando cancelas un cambio pendiente, tu suscripción no cambiará en tu próxima fecha de facturación (a menos que hagas un cambio posterior en tu suscripción antes de la próxima fecha de facturación). + +### Ver y administrar cambios pendientes en tu suscripción de cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.review-pending-changes %} +{% data reusables.dotcom_billing.cancel-pending-changes %} +{% data reusables.dotcom_billing.confirm-cancel-pending-changes %} + +### Ver y administrar cambios pendientes en tu suscripción de organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.review-pending-changes %} +{% data reusables.dotcom_billing.cancel-pending-changes %} +{% data reusables.dotcom_billing.confirm-cancel-pending-changes %} + +### Further reading + +- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md new file mode 100644 index 0000000000000..5116bdce86fbf --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md @@ -0,0 +1,35 @@ +--- +title: Ver tu uso de Git Large File Storage +intro: 'Puedes auditar la cuota de ancho de banda mensual de cuenta y el almacenamiento restante para {% data variables.large_files.product_name_short %}.' +redirect_from: + - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account/ + - /articles/viewing-storage-and-bandwidth-usage-for-an-organization/ + - /articles/viewing-your-git-large-file-storage-usage +versions: + free-pro-team: '*' +--- + +{% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %} + +### Ver el uso del almacenamiento y del ancho de banda para una cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.lfs-data %} + +### Ver el uso del almacenamiento y del ancho de banda para una organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.user_settings.subscriptions-tab %} +{% data reusables.dotcom_billing.lfs-data %} + +### Further reading + +- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" +- "[Actualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md new file mode 100644 index 0000000000000..88267f860bf44 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md @@ -0,0 +1,50 @@ +--- +title: Visualizar el uso de tu GitHub Actions +intro: 'Puedes ver los detalles de tu uso de minutos y almacenamiento para {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' +--- + +También puedes ver los minutos de ejecución facturables para los jobs en una ejecución de flujo de trabajo individual. Para obtener más información, consulta la sección "[Visualizar el tiempo de ejecución del job](/actions/managing-workflow-runs/viewing-job-execution-time)". + +### Visualizar el uso de {% data variables.product.prodname_actions %} para tu cuenta de usuario + +Cualquiera puede ver el uso de {% data variables.product.prodname_actions %} para su cuenta de usuario personal. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.actions-minutes %} +{% data reusables.dotcom_billing.actions-packages-storage %} +{% data reusables.dotcom_billing.actions-packages-report-download %} + +### Visualizar el uso de {% data variables.product.prodname_actions %} para tu organización + +Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_actions %} para una organización. Para organizaciones que gestione una cuenta empresarial, únicamente los propietarios de éstas pueden ver el uso de {% data variables.product.prodname_actions %} en la página de facturación de la misma. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.actions-minutes %} +{% data reusables.dotcom_billing.actions-packages-storage %} +{% data reusables.dotcom_billing.actions-packages-report-download %} + +### Visualizar el uso de {% data variables.product.prodname_actions %} para tu cuenta empresarial + +Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_actions %} para una cuenta empresarial. + +{% note %} + +**Nota:** Los detalles de facturación para las cuentas empresariales no resumen el uso de los minutos para cada sistema operativo. {% data reusables.github-actions.enterprise-billing-details %} + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +1. Debajo de " +{% data variables.product.prodname_actions %}", visualiza los detalles de uso de las transferencias de datos clasificados por organización en tu cuenta empresarial. + ![Detalles del uso de minutos](/assets/images/help/billing/actions-minutes-enterprise.png) +{% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} +{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md new file mode 100644 index 0000000000000..3c26dea54fb80 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md @@ -0,0 +1,48 @@ +--- +title: Visualizar el uso de tu GitHub Packages +intro: 'Puedes ver los detalles de uso de almacenamiento y transferencia de datos para {% data variables.product.prodname_registry %}.' +product: '{% data reusables.gated-features.packages %}' +versions: + free-pro-team: '*' +--- + +### Visualizar el uso de {% data variables.product.prodname_registry %} para tu cuenta de usuario + +Cualquiera puede ver el uso de {% data variables.product.prodname_registry %} para su cuenta de usuario personal. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.packages-data %} +{% data reusables.dotcom_billing.actions-packages-storage %} +{% data reusables.dotcom_billing.actions-packages-report-download %} + +### Visualizar el uso de {% data variables.product.prodname_registry %} para tu organización + +Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_registry %} para una organización. Para organizaciones que gestione una cuenta empresarial, únicamente los propietarios de éstas pueden ver el uso de {% data variables.product.prodname_registry %} en la página de facturación de la misma. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.packages-data %} +{% data reusables.dotcom_billing.actions-packages-storage %} +{% data reusables.dotcom_billing.actions-packages-report-download %} + +### Visualizar el uso de {% data variables.product.prodname_registry %} para tu cuenta empresarial + +Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_registry %} para una cuenta empresarial. + +{% note %} + +**Nota:** Los detalles de facturación para cuentas empresariales únicamente resumen el uso de almacenamiento de datos por organización. {% data reusables.github-actions.enterprise-billing-details %} + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +1. Debajo de " +{% data variables.product.prodname_registry %}", visualiza los detalles de uso de las transferencias de datos clasificados por organización en tu cuenta empresarial. + ![Detalles de uso de transferencia de datos](/assets/images/help/billing/packages-data-enterprise.png) +{% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} +{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md new file mode 100644 index 0000000000000..c82d99736340d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md @@ -0,0 +1,29 @@ +--- +title: Ver tu historial de pagos y recibos +intro: Puedes ver el historial de pagos de tu cuenta y descargar los últimos recibos en cualquier momento. +redirect_from: + - /articles/downloading-receipts/ + - /articles/downloading-receipts-for-personal-accounts/ + - /articles/downloading-receipts-for-organizations/ + - /articles/viewing-your-payment-history-and-receipts +versions: + free-pro-team: '*' +--- + +### Ver los recibos de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.view-payment-history %} +{% data reusables.dotcom_billing.download_receipt %} + +### Ver los recibos de tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.view-payment-history %} +{% data reusables.dotcom_billing.download_receipt %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md new file mode 100644 index 0000000000000..9c8243ac91253 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md @@ -0,0 +1,32 @@ +--- +title: Ver tus suscripción y fecha de facturación +intro: 'Puedes ver la suscripción de tu cuenta, tu otras características y productos de pago y tu próxima fecha de facturación en las configuraciones de facturación de tu cuenta.' +redirect_from: + - /articles/finding-your-next-billing-date/ + - /articles/finding-your-personal-account-s-next-billing-date/ + - /articles/finding-your-organization-s-next-billing-date/ + - /articles/viewing-your-plans-and-billing-date/ + - /articles/viewing-your-subscriptions-and-billing-date +versions: + free-pro-team: '*' +--- + +### Encontrar la próxima fecha de facturación de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing %} +{% data reusables.dotcom_billing.next_billing_date %} + +### Encontrar la próxima fecha de facturación de tu organización + +{% data reusables.dotcom_billing.org-billing-perms %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +{% data reusables.dotcom_billing.next_billing_date %} + +### Further reading + +- "[Acerca de la facturación para las cuentas de {% data variables.product.product_name %}](/articles/about-billing-for-github-accounts)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..0c876f5bb84ac --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,58 @@ +--- +title: Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML +intro: 'Si administras centralmente las identidades y aplicaciones de tus usuarios con un provedor de identidad (IdP), puedes configurar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) para proteger los recursos de tu organización en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +--- + +### Acerca de SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +Después de configurar el SSO de SAML, los miembros de tu organización de {% data variables.product.prodname_dotcom %} continuarán ingresando en sus cuentas de usuario en {% data variables.product.prodname_dotcom %}. Cuando un miembro accede a recursos dentro de tu organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redirecciona a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización. + +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". + +{% data reusables.saml.outside-collaborators-exemption %} + +Antes de habilitar el SSO de SAML para tu organización, necesitarás conectar tu IdP a la misma. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)." + +En una organización, el SSO de SAML puede inhabilitarse, habilitarse pero no requerirse, o habilitarse y requerirse. Después de habilitar exitosamente el SSO de SAML para tu organización y que sus miembros se autentiquen exitosamente con tu IdP, puedes requerir la configuración del SSO de SAML. Para obtener más información acerca de requerir el SSO de SAML para tu organización en {% data variables.product.prodname_dotcom %}, consulta la sección "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". + +Los miembros deben autenticarse regularmente con tu IdP y obtener acceso a los recursos de tu organización. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que los usuarios se vuelvan a identificar para continuar. + +Para acceder a los recursos protegidos de tu organización tulizando la API y Git en la línea de comando, los miembros deberán autorizar y autentificarse con un token de acceso personal o llave SSH. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)". + +La primera vez que un miembro utilice el SSO de SAML para acceder a tu organización, {% data variables.product.prodname_dotcom %} creará automáticamente un registro que vinculará a tu organización, la cuenta de {% data variables.product.prodname_dotcom %} del miembro y la cuenta del miembro en tu IdP. Puedes ver y retirar la identidad de SAML que se ha vinculado, activar sesiones, y autorizar las credenciales para los miembros de tu organización o cuenta empresarial. Para obtener más información, consulta la sección "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" y [Visualizar y administrar un acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". + +Si los miembros ingresan con una sesión de SSO de SAML cuando crean un nuevo repositorio, la visibilidad predeterminada de dicho repositorio será privada. De lo contrario, la visibilidad predeterminada es pública. Para obtener más información sobre los tipos de visibilidad para los repositorios, visita "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +Los miembros de una organización también deben contar con una sesión activa de SAML para autorizar un {% data variables.product.prodname_oauth_app %}. Puedes decidir no llevar este requisito si contactas a {% data variables.contact.contact_support %}. {% data variables.product.product_name %} no recomienda que renuncies a este requisito, ya que expondrá a tu organización a un riesgo mayor de que se roben las cuentas y de que exista pérdida de datos. + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Servicios SAML admitidos + +{% data reusables.saml.saml-supported-idps %} + +Algunos IdP admiten acceso de suministro a una organización de {% data variables.product.prodname_dotcom %} a través de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +### Agregar miembros a una organización usando SAML SSO + +Una vez que activas SAML SSO, hay varias maneras de poder agregar nuevos miembros a tu organización. Los propietarios de la organización pueden invitar a los miembros de forma manual en {% data variables.product.product_name %} o usando la API. Para obtener más información, consulta las secciones "[Invitar usuarios a unirse a tu organización](/articles/inviting-users-to-join-your-organization)" y "[Miembros](/rest/reference/orgs#add-or-update-organization-membership)". + +Para aprovisionar nuevos usuarios sin una invitación de un propietario de la organización, puedes usar la URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, reemplazando _ORGANIZATION_ con el nombre de tu organización. Por ejemplo, puedes configurar tu IdP para que cualquiera con acceso al IdP pueda hacer clic en el tablero del IdP para unirse a tu organización de {% data variables.product.prodname_dotcom %}. + +Si tu IdP admite SCIM, {% data variables.product.prodname_dotcom %} puede invitar automáticamente a los miembros para que se unan a tu organización cuando les otorgas acceso en tu IdP. Si eliminas el acceso de un miembro a tu organización de {% data variables.product.prodname_dotcom %} en tu IdP de SAML, éste se eliminará automáticamente de la organización de{% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Further reading + +- "[Acerca de la autenticación de dos factores y el inicio de sesión único de SAML ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000000..a397122becc2e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md @@ -0,0 +1,56 @@ +--- +title: Acerca de las restricciones de acceso a App OAuth +intro: 'Las organizaciones pueden elegir qué {% data variables.product.prodname_oauth_app %}s tienen acceso a sus repositorios y otros recursos al activar las restricciones de acceso a {% data variables.product.prodname_oauth_app %}.' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +--- + +Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están activadas, los miembros de la organización no pueden autorizar el acceso de {% data variables.product.prodname_oauth_app %} a los recursos de la organización. Los miembros de la organización pueden solicitar la aprobación de los propietarios para las {% data variables.product.prodname_oauth_app %}s que quieran usar y los propietarios de la organización reciben una notificación de solicitudes pendientes. + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Sugerencia**: Cuando una organización no ha configurado las restricciones de acceso a {% data variables.product.prodname_oauth_app %}, cualquier {% data variables.product.prodname_oauth_app %} autorizada por un miembro de la organización también puede acceder a los recursos privados de la organización. + +{% endtip %} + +### Configurar las restricciones de acceso a {% data variables.product.prodname_oauth_app %} + +Cuando el propietario de una organización configura las restricciones de acceso a {% data variables.product.prodname_oauth_app %} por primera vez: + +- Las **Aplicaciones que son propiedad de la organización** automáticamente ganan acceso a los recursos de la organización. +- Las **{% data variables.product.prodname_oauth_app %}s** inmediatamente pierden acceso a los recursos de la organización. +- Las **claves SSH creadas antes de febrero de 2014** inmediatamente pierden acceso a los recursos de la organización (esto incluye claves de implementación y usuarios). +- Las **claves SSH creadas por {% data variables.product.prodname_oauth_app %}s durante o después de febrero de 2014** inmediatamente pierden acceso a los recursos de la organización. +- Las **entregas de enlace de los repositorios privados de una organización** ya no serán enviadas a {% data variables.product.prodname_oauth_app %}s no aprobadas. +- El **acceso de API** a los recursos privados de la organización no está disponible para las {% data variables.product.prodname_oauth_app %}s no aprobadas. Además, no hay acciones de creación, actualización ni eliminación privilegiadas en los recursos públicos de la organización. +- Los **enlaces creados por los usuarios y los enlaces creados antes de mayo de 2014** no se verán afectados. +- Las **bifurcaciones privadas de los repositorios que son propiedad de una organización** están sujetas a las restricciones de acceso de la organización. + +### Resolver las fallas de acceso a SSH + +Cuando una clave SSH creada antes de febrero de 2014 pierde acceso a una organización con las restricciones de acceso a {% data variables.product.prodname_oauth_app %} activadas, los subsiguientes intentos de acceso a SSH fallarán. Los usuarios se encontrarán con un mensaje de error que los redirecciona a una URL donde pueden aprobar la clave o cargar una clave de confianza en su lugar. + +### Webhooks + +Cuando se le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %} una vez que las restricciones están activadas, cualquier webhook preexistente creado por esa {% data variables.product.prodname_oauth_app %} retomará el despacho. + +Cuando una organización elimina el acceso de una {% data variables.product.prodname_oauth_app %} previamente aprobada, cualquier webhook preexistente creado por esa aplicación ya no será despachado (estos enlaces de desactivarán, pero no se eliminarán). + +### Volver a activar las restricciones de acceso + +Si una organización desactiva las restricciones de aplicación de acceso de {% data variables.product.prodname_oauth_app %}, y más tarde las vuelve a activar, automáticamente se le otorga acceso a los recursos de la organización a la {% data variables.product.prodname_oauth_app %} previamente aprobada . + +### Further reading + +- "[Activar las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" +- "[Aprobar {% data variables.product.prodname_oauth_app %}s para tu organización](/articles/approving-oauth-apps-for-your-organization)" +- "[Revisar las integraciones instaladas de tu organización](/articles/reviewing-your-organization-s-installed-integrations)" +- "[Denegar el acceso a una {% data variables.product.prodname_oauth_app %} anteriormente aprobada para tu organización](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" +- "[Desactivar las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" +- "[Solicitar aprobación de la organización para las {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)" +- "[Autorizar las{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-organizations.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-organizations.md new file mode 100644 index 0000000000000..6186b0b5c14d1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-organizations.md @@ -0,0 +1,29 @@ +--- +title: Acerca de las organizaciones +intro: Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. +redirect_from: + - /articles/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organizaciones y cuentas de empresa + +Las cuentas de empresa le permiten a los propietarios administrar en forma centralizada las políticas y la facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. + +Para las organizaciones que pertenecen a una cuenta de empresa, la facturación se administra en el nivel de cuenta de empresa y los parámetros de facturación no están disponibles en el nivel de organización. Los propietarios de la empresa pueden establecer políticas para todas las organizaciones en la cuenta de empresa o permitirle a los propietarios de la organización establecer las políticas en el nivel de organización. Los propietarios de la organización no pueden cambiar los parámetros implementados para tu organización en el nivel de cuenta de empresa. Si tienes consultas sobre una política o la configuración para tu organización, comunícate con el propietario de tu cuenta de empresa. + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} Para obtener más información, consulta la sección "[Mantener la continuidad de propiedad para tu organización](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)". + +### Términos de servicio y protección de datos para organizaciones + +Una entidad, como una empresa, una organización sin fines de lucro o un grupo, puede aceptar los Términos de servicio estándar o los Términos de servicio corporativos para su organización. Para obtener más información, consulta "[Actualizarse a los Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)". + +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md new file mode 100644 index 0000000000000..7c92512bede83 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -0,0 +1,27 @@ +--- +title: Acerca de SCIM +intro: 'Con Sistema para la administración de identidades entre dominios (SCIM), los administradores pueden automatizar el intercambio de información de identidad del usuario entre los sistemas.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim +versions: + free-pro-team: '*' +--- + +Si usas [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) en tu organización, puedes implementar SCIM para agregar, administrar y eliminar el acceso de los miembros de la organización a {% data variables.product.product_name %}. Por ejemplo, un administrador puede desaprovisionar a un miembro de la organización usando el SCIM y eliminar automáticamente el miembro de la organización. + +Si usas SAML SSO sin implementar SCIM, no tendrás un desaprovisionamiento automático. Cuando las sesiones de los miembros de la organización expiran una vez que su acceso ha sido eliminado del IdP, no se eliminan automáticamente de la organización. Los tokens autorizados otorgan acceso a la organización incluso una vez que las sesiones han expirado. Para eliminar el acceso, los administradores de la organización pueden eliminar de forma manual el token autorizado de la organización o automatizar su eliminación con SCIM. + +Estos proveedores de identidad son compatibles con la API de SCIM de {% data variables.product.product_name %} para organizaciones. Para obtener más información, consulta [SCIM](/rest/reference/scim) en la documentación de {% data variables.product.product_name %} API. +- Azure AD +- Okta +- OneLogin + +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)" +- "[Activar y probar el inicio de sesión único de SAML para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000000..4f2db3e316056 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md @@ -0,0 +1,39 @@ +--- +title: Acerca de las autoridades de certificación de SSH +intro: 'Con una autoridad de certificación de SSH, tu cuenta de empresa u organización puede ofrecer certificados SSH que los miembros pueden usar para aceder a tus recursos con Git.' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Un certificado SSH es un mecanismo para que una clave SSH firme otra clave SSH. Si usas una autoridad de certificación de SSH (CA) para ofrecerle a los miembros de tu organización certificados SSH firmados, puedes agregar la CA a tu cuenta de empresa u organización para permitirle a los miembros de la organización usar sus certificados para acceder a los recursos de la organización. Para obtener más información, consulta [Administrar las autoridades de certificación de SSH de tu organización ](/articles/managing-your-organizations-ssh-certificate-authorities)". + +Una vez que agregas una CA de SSH a tu cuenta de empresa u organización, puedes usar la CA para firmar certificados de SSH de clientes para los miembros de la organización. Los miembros de la organización pueden usar los certificados firmados para acceder a los repositorios de tu organización (y solo los repositorios de tu organización) con Git. Puedes requerir que los miembros utilicen certificados SSH para acceder a los recursos organizacionales.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[requerir ajustes de seguridad en tu cuenta empresarial](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)".{% endif %} + +Por ejemplo, puedes crear un sistema interno que emita un nuevo certificado para tus programadores cada mañana. Cada programador puede usar su certificado diario para trabajar en los repositorios de tu organización en {% data variables.product.product_name %}. Al finalizar el día, el certificado puede expirar automáticamente, protegiendo tus repositorios si el certificado más tarde se ve comprometido. + +Cuando emites cada certificado, debes incluir una extensión que especifique para qué usuario de {% data variables.product.product_name %} es el certificado. Por ejemplo, puedes usar el comando `ssh-keygen` de OpenSSH, reemplazando _KEY-IDENTITY_ por tu identidad de clave y _USERNAME_ por un nombre de usuario de {% data variables.product.product_name %}: + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME ./user-key.pub +``` + +Para emitir un certificado para alguien que tiene diferentes nombres de usuario para {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}, puedes incluir dos extensiones de inicio de sesión. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=CLOUD-USERNAME extension:login@HOSTNAME=SERVER-USERNAME ./user-key.pub +``` + +Puedes restringir las direcciones IP desde las que un miembro de la organización puede acceder a los recursos de tu organización usando una extensión `source-address`. La extensión acepta una dirección IP específica o una gama de direcciones IP con la notación CIDR. Puedes especificar múltiples direcciones o rangos separando los valores con comas. Para obtener más información, consulta "[Enrutamiento entre dominios sin clases](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" en Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +Los miembros de la organización pueden usar sus certificados firmados para la autenticación, incluso si has aplicado el inicio de sesión único de SAML. A menos que hagas que los certificados SSH sean un requisito, los miembros de la organización pueden seguir usando otros medios para la autenticación para acceder a los recursos de tu organización con Git, incluyendo sus nombre de usuario y contraseña, tokens de acceso personales y sus propias claves SSH. + +Para evitar errores de autenticación, los miembros de la organización deben usar una URL especial que incluya el ID de la organización para clonar los repositorios mediante certificados firmados. Cualquier persona con acceso de lectura al repositorio puede buscar esta URL en la página del repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md new file mode 100644 index 0000000000000..04635026b3185 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md @@ -0,0 +1,75 @@ +--- +title: Acerca de los equipos +intro: Los equipos son grupos de miembros de una organización que reflejan la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. +redirect_from: + - /articles/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +![Listado de equipos en una organización](/assets/images/help/teams/org-list-of-teams.png) + +Los propietarios de la organización y los mantenedores del equipo le pueden otorgar a los equipos acceso de escritura, de lectura o de administrador a los repositorios de la organización. Los miembros de la organización pueden enviar una notificación a todo un equipo al mencionar el nombre del equipo. Los miembros de la organización también pueden enviar una notificación a todo un equipo al solicitar una revisión de ese equipo. Los miembros de la organización pueden solicitar revisiones de equipos específicos con acceso de lectura al repositorio donde la solicitud de extracción esté abierta. Los equipos pueden ser designados como propietarios de ciertos tipos o áreas de código en un archivo CODEOWNERS. + +Para obtener más información, consulta: +- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" +- "[Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[Acerca de los propietarios del código](/articles/about-code-owners/)" + +![Imagen de la mención a un equipo](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +También puedes usar la sincronización LDAP para sincronizar los roles del equipo y los miembros del equipo de {% data variables.product.product_location %} con tus grupos de LDAP establecidos. Esto te permite establecer un control de acceso para usuarios basado en roles desde tu servidor LDAP, en lugar de hacerlo de forma manual dentro de {% data variables.product.product_location %}. Para obtener más información, consulta "[Activar sincronización LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Visibilidad del equipo + +{% data reusables.organizations.types-of-team-visibility %} + +### Paginas del equipo + +Cada equipo tiene su propia página dentro de una organización. En la página de un equipo, puedes ver los miembros del equipo, los equipos hijo y los repositorios del equipo. Los propietarios de la organización y los mantenedores del equipo pueden acceder a los parámetros del equipo y actualizar la foto de perfil y la descripción del equipo desde la página del equipo. + +Los miembros de la organización pueden crear y participar en debates con el equipo. Para obtener más información, consulta [Acerca de los debates del equipo](/articles/about-team-discussions)". + +![Página del equipo que enumera los miembros del equipo y los debates](/assets/images/help/organizations/team-page-discussions-tab.png) + +### Equipos anidados + +Puedes reflejar la jerarquía de tu grupo o empresa dentro de tu organización de {% data variables.product.product_name %} con varios niveles de equipos anidados. Un equipo padre puede tener varios equipos hijo, mientras que cada equipo hijo solo tiene un equipo padre. No puedes anidar equipos secretos. + +Los equipos hijo heredan los permisos de acceso del padre, lo que simplifica la administración de permisos para los grupos grandes. Los miembros de los equipos hijo también reciben notificaciones cuando se hace una @mención al equipo padre, simplificando la comunicación con varios grupos de personas. + +Por ejemplo, si la estructura de tu equipo es Empleados > Ingeniería > Ingeniería de aplicación> Identidad, otorgar acceso de escritura a Ingeniería en un repositorio implicará que también se podrá acceder a Ingeniería de aplicación e Identidad. Si haces una @mención al equipo de Identidad o a cualquier equipo de la parte inferior de la jerarquía de la organización, son los únicos que recibirán una notificación. + +![Página de los equipos con un equipo padre y equipos hijo](/assets/images/help/teams/nested-teams-eng-example.png) + +Para comprender fácilmente quién comparte las menciones y los permisos de un equipo padre, puedes ver todos los miembros de los equipos hijo de un equipo padre en la pestaña Miembros de la página del equipo padre. Los miembros de un equipo hijo no son miembros directos del equipo padre. + +![Página del equipo padre con todos los miembros de los equipos hijo](/assets/images/help/teams/team-and-subteam-members.png) + +Puedes elegir un padre cuando creas el equipo o puedes mover un equipo más tarde en la jerarquía de tu organización. Para obtener más información, consulta [Mover un equipo dentro de la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Prepararse para anidar equipos en tu organización + +Si tu organización ya tiene equipos existentes, deberías auditar los permisos de acceso a los repositorios de cada equipo antes de anidar equipos por arriba o por debajo del mismo. También deberías considerar la nueva estructura que te gustaría implementar para tu organización. + +En la parte superior de la jerarquía del equipo, deberías otorgar permisos de acceso a los repositorios de los equipos padre que son seguros para cada miembro del equipo padre y sus equipos hijo. A medida que te mueves hacia la parte inferior de la jerarquía, puedes otorgar a los equipos hijo un acceso adicional, más pormenorizado para los repositorios más confidenciales. + +1. Eliminar todos los miembros de los equipos existentes. +2. Auditar y ajustar los permisos de acceso a los repositorios de cada equipo y darle a cada equipo un padre. +3. Crear todos los equipos nuevos que quieras, elegir un padre para cada equipo nuevo y otorgarles acceso a los repositorios. +4. Agregar las personas directamente a los equipos. + +### Further reading + +- "[Crear un equipo](/articles/creating-a-team)" +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000000..a7f1811aac475 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,22 @@ +--- +title: Acerca de la autenticación de dos factores y el inicio de sesión único de SAML +intro: Los administradores de las organizaciones pueden activar tanto el inicio de sesión único de SAML como la autenticación de dos factores para agregar medidas de autenticación adicionales para sus miembros de la organización. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +--- + +La autenticación de dos factores (2FA) ofrece una autenticación básica para los miembros de la organización. Al activar la 2FA, los administradores de la organización limitan la probabilidad de que la cuenta de {% data variables.product.product_name %} de un miembro se vea comprometida. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)". + +Para agregar medidas de autenticación adicionales, los administradores de la organización también pueden [activar el inicio de sesión único (SSO) de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que los miembros de la organización deban usar el inicio de sesión único para acceder a una organización. Para obtener más información sobre SAML SSO, consulta "[Acerca de la administración de identidad y acceso con inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)". + +Si tanto la 2FA como SAML SSO están activados, los miembros de la organización deben hacer lo siguiente: +- Usar la 2FA para iniciar sesión en su cuenta de {% data variables.product.product_name %}. +- Usar el inicio de sesión único para acceder a la organización. +- Usar un token autorizado para el acceso a Git o a la API y usar el inicio de sesión único para autorizar el token. + +### Further reading + +- "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md new file mode 100644 index 0000000000000..be3bc3a5d0e58 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md @@ -0,0 +1,45 @@ +--- +title: Acerca del tablero de tu organización +intro: 'Como miembro de una organización, puedes visitar el tablero de tu organización durante todo el día para estar actualizado sobre la actualidad reciente y hacer un seguimiento de las propuestas y las solicitudes de extracción en las que estás trabajando o siguiendo en la organización.' +redirect_from: + - /articles/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acceder al tablero de tu organización + +{% data reusables.dashboard.access-org-dashboard %} + +### Encontrar tu actividad reciente + +En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes buscar las propuestas y solicitud de extracción de tu organización recientemente actualizadas y hacerles el seguimiento. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Encontrar repositorios en tu organización + +En la barra lateral izquierda de tu tablero, puedes acceder a los principales repositorios de tu organización en los que estás activo. + +![Listado delos repositorios en los que eres más activo de tu organización](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Estar actualizado con la actividad desde tu organización + +En la sección "All activity" (Toda la actividad) de tus noticias, puedes ver actualizaciones de otros equipos y repositorios en tu organización. + +La sección "All activity" (Toda la actividad) muestra toda la actividad reciente en la organización, incluida la actividad en los repositorios a los que no estás suscrito y de las personas que no sigues. Para obtener más información, consulta las secciones {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Observar y dejar de observar los repositorios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" y "[Seguir a las personas](/articles/following-people)". + +Por ejemplo, las noticias de la organización muestran actualizaciones cuando alguien en la organización: + - Crea una rama nueva. + - Comenta en una propuesta o una solicitud de extracción. + - Envía un comentario de revisión de solicitud de extracción. + - Bifurca un repositorio. + - Crea una página wiki. + - Sube las confirmaciones.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - Crea un repositorio público.{% endif %} + +### Información adicional + +- "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md new file mode 100644 index 0000000000000..05b7497f1fd8f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md @@ -0,0 +1,22 @@ +--- +title: Acerca de las noticias de tu organización +intro: Puedes usar las noticias de tu organización para mantenerte al corriente de las actividades recientes en los repositorios que posee esa organización. +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las noticias de una organización muestran las actividades de otras personas en los repositorios que posee esa organización. Puedes usar las noticias de tu organización para ver cuando alguien abre, cierra o fusiona una propuesta o solicitud de extracción, crea o elimina una rama, crea una etiqueta o un lanzamiento, comenta en una propuesta, una solicitud de extracción o una confirmación de cambios o sube confirmaciones nuevas a {% data variables.product.product_name %}. + +### Acceder a las noticias de tu organización + +1. {% data variables.product.signin_link %} a tu cuenta de {% data variables.product.product_name %}. +2. Abre tu {% data reusables.user_settings.personal_dashboard %}. +3. Haz clic en el cambiador de contexto de la cuenta en la esquina superior izquierda de la página. ![Botón cambiador de contexto en Enterprise](/assets/images/help/organizations/account_context_switcher.png) +4. Selecciona una organización del menú desplegable.{% if currentVersion == "free-pro-team@latest" %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} +![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000000..918f8e0db2b76 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,27 @@ +--- +title: Acceder a tu organización si tu proveedor de identidad no está disponible +intro: 'Los administradores de la organización pueden iniciar sesión en {% data variables.product.product_name %} incluso si su proveedor de identidad no está disponible al saltear el inicio de sesión único y usar sus códigos de recuperación.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +--- + +Los administradores de la organización pueden usar [uno de los códigos de reuperación descargados o guardados](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)para saltear un inicio de sesión único. Es posible que los hayas guardado en un administrador de contraseñas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/). + +{% note %} + +**Nota:** Solo puedes usar los códigos de recuperación una vez y debes usarlos en un orden consecutivo. Los códigos de recuperación garantizan el acceso durante 24 horas. + +{% endnote %} + +1. En la parte inferior del diálogo de inicio de sesión único, haz clic en **Use a recovery code** (Usar un código de recuperación) para saltear el inicio de sesión único. ![Enlace para ingresar tu código de recuperación](/assets/images/help/saml/saml_use_recovery_code.png) +2. En el campo "Recovery Code" (Código de recuperación), escribe tu código de recuperación. ![Código para ingresar tu código de recuperación](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Da clic en **Verificar**. ![Botón para verificar tu código de recuperación](/assets/images/help/saml/saml_verify_recovery_codes.png) + +Una vez que has usado un código de verificación, asegúrate de anotar que ya no es válido. No podrás volver a usar el código de recuperación. + +### Further reading + +- [Acerca de la administración de acceso e identidad con SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings.md new file mode 100644 index 0000000000000..848280751e6b9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings.md @@ -0,0 +1,30 @@ +--- +title: Acceder a los parámetros de tu organización +redirect_from: + - /articles/who-can-access-organization-billing-information-and-account-settings/ + - /articles/managing-the-organization-s-settings/ + - /articles/who-can-see-billing-information-account-settings/ + - /articles/who-can-see-billing-information-and-access-account-settings/ + - /articles/managing-an-organization-s-settings/ + - /articles/accessing-your-organization-s-settings + - /articles/accessing-your-organizations-settings +intro: 'La página de los parámetros de la cuenta de la organización brinda varias maneras de administrar la cuenta, como parámetros de facturación, miembros del equipo y repositorio.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Sugerencia:** Solo los propietarios de la organización y los gerentes de facturación pueden ver y cambiar la información de facturación y la configuración de la cuenta para una organización. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000000..9b41049d698ea --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,52 @@ +--- +title: Agregar un gerente de facturación a tu organización +intro: 'Un *gerente de facturación* es un usuario que administra los parámetros de facturación de tu organización, como la actualización de la información de pago. Esta es una gran opción si los miembros regulares de tu organización habitualmente no tienen acceso a los recursos de facturación.' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +--- + +Los miembros del equipo Propietarios de tu organización pueden permitir que los *gerentes de facturación* proporcionen permisos a las personas. Una vez que una persona acepta la invitación para convertirse en gerente de facturación para tu organización, puede invitar a otras personas para convertirse en gerentes de facturación. + +{% note %} + +**Nota:**Los gerentes de facturación no utilizan licencias pagadas en la suscripción de tu organización. + +{% endnote %} + +### Permisos para los gerentes de facturación + +Los gerentes de facturación pueden: + +- Actualizar o bajar la categoría de la cuenta +- Agregar, actualizar o eliminar métodos de pago +- Ver historial de pagos +- Descargar recibos +- Ver, invitar y eliminar gerentes de facturación + +Además, todos los gerentes de facturación recibirán recibos de facturación por correo electrónico en la fecha de facturación de la organización. + +Los gerentes de facturación**no** pueden: + +- Crear o acceder repositorios en tus organizaciones +- Ver miembros privados de tu organización +- Ser visto en la lista de los miembros de la organización +- Comprar, editar o cancelar suscripciones para aplicaciones de {% data variables.product.prodname_marketplace %} + +{% tip %} + +**Sugerencia:** Si tu organización [requiere que los miembros, gerentes de facturación y colaboradores externos usen autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), el usuario debe habilitar la autenticación de dos factores antes de que puedan aceptar tu invitación para convertirse en gerentes de facturación para la organización. + +{% endtip %} + +### Invitar a un gerente de facturación + +La persona invitada recibirá una invitación por correo electrónico solicitándole que se convierta en gerente de facturación para tu organización. Una vez que la persona invitada hace clic en el enlace de aceptación en el correo electrónico de la invitación, se agregarán automáticamente a la organización como gerentes de facturación. Si todavía no tienen una cuenta GitHub, deberán iniciar sesión para una cuenta, y se agregarán automáticamente a la organización como gerentes de facturación luego de crear una cuenta. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Junto a Billing managers (Gerentes de facturación), haz clic en **Add a billing manager** (Agregar un gerente de facturación). ![Invitar gerente de facturación](/assets/images/help/billing/settings_billing_managers_list.png) +6. Escribe el nombre de usuario o la dirección de correo electrónico de la persona a la que deseas agregar y haz clic en **Send invitation** (Enviar invitación). ![Página Invitar gerente de facturación](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000000..e1a2122d0b338 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Agregar un colaborador externo al tablero de proyecto de tu organización +intro: 'Como propietario de una organización o administrador de un tablero de proyecto, puedes agregar un colaborador externo y personalizar sus permisos para un tablero de proyecto.' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Un colaborador externo es una persona que no es explícitamente un miembro de tu organización, pero tiene permisos para un tablero de proyecto en tu organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +9. Debajo de "Buscar por nombre de usuario, nombre completo o dirección de correo electrónico", teclea el nombre del colaborador externo, nombre de usuario, o +correo electrónico de {% data variables.product.prodname_dotcom %}. + ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000000..8decbfec7c55f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,38 @@ +--- +title: Agregar administradores de App GitHub a tu organización +intro: 'Los propietarios de la organización pueden conceder a los usuarios la capacidad para administrar alguna o todas las {% data variables.product.prodname_github_app %}s que le pertenecen a la organización.' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para más información sobre los permisos del administrador de {% data variables.product.prodname_github_app %}, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization#github-app-managers)". + +### Brindar a alguien la posibilidad de administrar todos los {% data variables.product.prodname_github_app %} que son propiedad de la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. En "Management" (Administración), escribe el nombre de usuario de la persona a quien deseas designar como gerente de {% data variables.product.prodname_github_app %} en la organización, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png) + +### Brindar a alguien la posibilidad de administrar un {% data variables.product.prodname_github_app %} individual + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Debajo de " +{% data variables.product.prodname_github_app %}s", da clic en el avatar de la app para el cual te gustaría agregar un administrador de {% data variables.product.prodname_github_app %}. +![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. En "App managers" (Administradores de la app), escribe el nombre de usuario de la persona a quien deseas designar como administrador de la App GitHub para la app, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %} para una app específica](/assets/images/help/organizations/add-github-app-manager-for-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000000..2953a8cbfa2f9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,28 @@ +--- +title: Agregar miembros de la organización a un equipo +intro: 'Las personas con permisos de propietario o mantenedor del equipo pueden agregar miembros de la organización a los equipos. Las personas con permisos de administrador también pueden {% if currentVersion == "free-pro-team@latest" %}invitar a personas que no sean miembros para que se unan{% else %}agregar a personas que no sean miembros para que se unan{% endif %} a un equipo y a la organización.' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +6. Encima de la lista de los miembros del equipo, haz clic en **Add a member** (Agregar un miembro). ![Botón Add member (Agregar miembro)](/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 + +- [Acerca de los equipos](/articles/about-teams)" +- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000000..68ecb487ab771 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,38 @@ +--- +title: Agregar colaboradores externos a los repositorios en tu organización +intro: 'Un *colaborador externo* es una persona que no es explícitamente un miembro en tu organización pero tiene premisos de lectura.' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.owners-and-admins-can %} agregar colaboradores externos a un repositorio, a menos que un propietario de la organización haya restringido la capacidad para invitar colaboradores. Para obtener más información, consulta "[Establecer permisos para agregar colaboradores externos](/articles/setting-permissions-for-adding-outside-collaborators)". + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +Si tu organización [requiere miembros y colaboradores externos para usar la autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), deben habilitar la autenticación de dos factores antes de que puedan aceptar tu invitación para colaborar en el repositorio de una organización. +{% endif %} + +{% data reusables.organizations.outside_collaborator_forks %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.repositories.navigate-to-manage-access %} +{% data reusables.organizations.invite-teams-or-people %} +5. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Debajo de "Selecciona un rol", selecciona los permisos que quieres otorgar a la persona, luego da clic en **"Añadir NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para la persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Barra lateral de configuraciones del repositorio con Colaboradores y equipos resaltados](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. En "Collaborators" (Colaboradores), escribe el nombre de la persona a la que te gustaría brindar acceso al repositorio, luego haz clic en **Add collaborator** (Agregar colaborador). ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Junto al nombre del colaborador, escribe el nivel de permiso correspondiente: *Write* (Escritura) *Read* (Lectura) o *Admin* (Administración). ![El recolector de permisos del repositorio](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### Further reading + +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md new file mode 100644 index 0000000000000..08abb354b0063 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Agregar personas a tu organización +intro: 'Puedes hacer que cualquier persona se convierta en miembro de tu organización usando el nombre de usuario de {% data variables.product.product_name %} o la dirección de correo electrónico.' +redirect_from: + - /articles/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Los propietarios de las organizaciones pueden agregar a las personas a éstas.' +--- + +{% if currentVersion != "github-ae@latest" %} +Si tu organización[requiere que los miembros usen autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), los usuarios deben [habilitar la autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedas agregarlos a la organización. +{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.invite_to_org %} +{% data reusables.organizations.choose-to-restore-privileges %} +{% data reusables.organizations.choose-user-role %} +{% data reusables.organizations.choose-user-license %} +{% data reusables.organizations.add-user-to-teams %} +{% data reusables.organizations.send-invitation %} + +### Further reading +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000000..91266503ac68b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,21 @@ +--- +title: Permitir que personas eliminen propuestas en tu organización +intro: Los propietarios de la organización pueden permitir que determinadas personas eliminen propuestas en repositorios que pertenecen a tu organización. +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Por defecto, las propuestas no pueden eliminarse en los repositorios de una organización. El propietario de la organización debe habilitar esta característica para todos los repositorios de la organización en primer lugar. + +Una vez habilitados, los propietarios de la organización y las personas con permisos de administración en un repositorio que es propiedad de la empresa pueden eliminar propuestas. Entre las personas con permisos de administración en un repositorio se incluyen los miembros de la organización y los colaboradores externos con privilegios de administración. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)" y "[Eliminar una propuesta"](/articles/deleting-an-issue)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. En "Issue deletion" (Eliminación de la propuesta), selecciona **Permitir que los miembros eliminen propuestas para esta organización**. ![Casilla de verificación para permitir que las personas eliminen propuestas](/assets/images/help/settings/issue-deletion.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000000..07dad39f41fe6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,22 @@ +--- +title: Aprobar aplicaciones OAuth para tu organización +intro: 'Cuando un miembro de la organización solicita a {% data variables.product.prodname_oauth_app %} que acceda a los recursos de la organización, los propietarios de la organización pueden aprobar o rechazar la solicitud.' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +--- + +Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están habilitadas, los miembros de la organización deben [solicitar la aprobación](/articles/requesting-organization-approval-for-oauth-apps) de un propietario de la organización antes de que puedan autorizar una {% data variables.product.prodname_oauth_app %} que tiene acceso a los recursos de la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Junto a la aplicación que quieres aprobar, haz clic en **Review** (Revisar). ![Enlace de revisión de solicitud](/assets/images/help/settings/settings-third-party-approve-review.png) +6. Una vez que revises la información sobre la aplicación solicitada, haz clic en **Grant access** (Otorgar acceso). ![Botón para otorgar acceso](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### Further reading + +- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000000..868c2f5370cb9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,17 @@ +--- +title: '¿Puedo crear cuentas para personas en mi organización?' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization +intro: 'Si bien puedes agregar usuarios a una organización que has creado, no puedes crear cuentas de usuario personales en nombre de otra persona.' +versions: + free-pro-team: '*' +--- + +Dado que accedes a una organización iniciando sesión mediante tu cuenta personal, cada uno de los miembros del equipo necesita una cuenta personal. Una vez que tienes los nombres de usuario de cada persona que deseas agregar a tu organización, puedes agregarlos a los equipos. + +### Agregar usuarios a tu organización + +1. Brinda a cada persona las instrucciones para [crear una cuenta personal](/articles/signing-up-for-a-new-github-account). +2. Preguntar el nombre de usuario a cada persona a la que deseas dar membresía a la organización. +3. [Invitar a las nuevas cuentas personales para que se unan](/articles/inviting-users-to-join-your-organization) a tu organización. Usar [roles de la organización](/articles/permission-levels-for-an-organization) y [permisos de repositorio](/articles/repository-permission-levels-for-an-organization) para limitar el acceso a cada cuenta. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000000..bab61a1805fa4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,19 @@ +--- +title: Cancelar una invitación para convertirse en un colaborador externo en tu organización +intro: Puedes cancelar todas las invitaciones para que las personas se conviertan en un colaborador externo en los repositorios que pertenecen a tu organización. +permissions: Los propietarios de la organización pueden cancelar una invitación para convertirse en un colaborador externo en la misma. +versions: + free-pro-team: '*' +--- + +Puedes ver una lista de todas las personas con invitaciones pendientes para convertirse en colaboradores externos en cualquier repositorio que pertenezca a tu organización. + +Para cada colaborador pendiente, puedes cancelar al mismo tiempo todas las invitaciones para unirse a los repositorios de la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Da clic en **colaboradores pendientes**. ![Botón de "Colaboradores pendientes"](/assets/images/help/organizations/pending-collaborator-list.png) +6. A la derecha de la persona para la cual quieres cancelar las invitaciones, da clic en **Cancelar invitaciones**. ![Botón de "Cancelar invitación"](/assets/images/help/organizations/cancel-pending-collaborators.png) +7. Da clic en **Cancelar invitaciones para los colaboradores pendientes**. ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000000..93c5fab6214fe --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Cancelar o editar una invitación a unirse a tu organización +intro: Los propietarios de la organización pueden editar o cancelar una invitación para convertirte en miembro de tu organización en cualquier momento antes de que el usuario acepte. +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. En la pestaña (People) Personas, haz clic en **Pending invitation** (Invitación pendiente). ![Enlace a invitación pendiente](/assets/images/help/organizations/pending-invitation-link.png) +5. Junto al nombre de usuario o la dirección de correo electrónico de la persona cuya invitación deseas editar o cancelar, haz clic en **Edit invitation** (Editar invitación). ![Botón Edit invitation (Editar invitación)](/assets/images/help/organizations/edit-invitation-button.png) + + Es posible que necesites hacer clic en **View all invitations** (Ver todas las invitaciones) en la parte inferior de la ventana para encontrar a la persona que estás buscando. +6. Decide si deseas edita o cancelar la invitación del usuario para unirse a tu organización. ![Botones Update invitation (Actualizar invitación) y Cancel invitation (Cancelar invitación)](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - Para editar la invitación del usuario, selecciona un rol o equipo diferente, luego haz clic en **Update invitation** (Actualizar invitación). + - Para cancelar la invitación del usuario para unirte a tu organización, haz clic en **Cancel invitation** (Cancelar invitación). + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %} +- "[Invitar a usuarios para que se unan a nuestra organización](/articles/inviting-users-to-join-your-organization)" +{% endif %} +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility.md new file mode 100644 index 0000000000000..2bf965845acb4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility.md @@ -0,0 +1,25 @@ +--- +title: Cambiar la visibilidad del equipo +intro: Los mantenedores del equipo y los propietarios de la organización pueden determinar si un equipo es *visible* o *secreto*. +redirect_from: + - /articles/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**Sugerencia:** Si un equipo tiene [equipos padres o hijos](/articles/about-teams), no puedes convertirlo en un equipo secreto. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. Selecciona el equipo o los equipos cuya visibilidad deseas cambiar. ![Lista de miembros con dos equipos seleccionados](/assets/images/help/teams/list-of-teams-selected.png) +4. Arriba de la lista de equipos, usa el menú desplegable y haz clic en **Change visibilidad** (Cambiar visibilidad). ![Menú desplegable con opción para cambiar la visibilidad del equipo](/assets/images/help/teams/team-bulk-management-options.png) +5. Elige si deseas hacer que el equipo o los equipos sean visibles o secretos, luego haz clic en **Change visibilidad** (Cambiar visibilidad). ![Botones de opción para hacer que un equipo sea visible o secreto y botón Change visibility (Cambiar visibilidad)](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000000..c309d90c22ff0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,20 @@ +--- +title: Cambiar la visibilidad de la información de dependencias de la organización +intro: Puedes permitir que todos los miembros de la organización vean información de dependencias para tu organización o limiten la visualización de los propietarios de la organización. +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +--- + +Los propietarios de la organización pueden establecer limitaciones para ver la información de dependencias de la organización. De manera predeterminada, todos los miembros de una organización pueden ver información de la dependencia de la organización. + +Los propietarios de la empresa pueden establecer limitaciones para ver la información de las dependencias de la organización en todas las organizaciones de tu cuenta de empresa. Para obtener más información, consulta "[Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. En "Member organization permissions" (Permisos para miembros de la organización), selecciona o quita la marca de selección de **Allow members to view dependency insights** (Permitir que los miembros vean información de dependencias). ![Casilla de verificación para permitir que los miembros vean información](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md new file mode 100644 index 0000000000000..79cb563313476 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md @@ -0,0 +1,13 @@ +--- +title: Colaborar con grupos en organizaciones +intro: Los grupos de personas pueden colaborar en muchos proyectos a la vez en cuentas d ela organización. +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000000..384c2957f2d2e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,76 @@ +--- +title: Cofnigurar SCIM y el inicio de sesión único de SAML con Okta +intro: 'Puedes utilizar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) y un Sistema para la Administración de Identidad a través de los Dominios (SCIM) con Okta para administrar automáticamente el acceso a tu organización en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Los propietarios de las organizaciones pueden configurar el SSO de SAML y SCIM utilizando Okta para su organización. +versions: + free-pro-team: '*' +--- + +### Acerca de SAML y SCIM con Okta + +Puedes controlar el acceso a tu organización de {% data variables.product.prodname_dotcom %} y a otras aplicaciones web desde una interface central si configuras la organización para que utilice el SSO de SAML con Okta, un Proveedor de Identidad (IdP). + +El SSO de SAML controla y asegura el acceso a los recursos organizacionales como los repositorios, informes de problemas y solicitudes de extracción. SCIM agrega automáticamente, administra y elimina el acceso de los miembros a tu organización de {% data variables.product.prodname_dotcom %} cuando haces cambios en Okta. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidad con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)" y "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +Después de que habilites SCIM, las siguientes características de aprovisionamiento estarán disponibles para cualquier usuario al que asignes tu aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta. + +| Característica | Descripción | +| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Subir Usuarios Nuevos | Cuando creas un usuario nuevo en Okta, éste recibirá un correo electrónico para unirse a tu organización de {% data variables.product.prodname_dotcom %}. | +| Subir Desactivaciones de Usuarios | Cuando desactivas un usuario en Okta, Okta lo eliminará de tu organización de {% data variables.product.prodname_dotcom %}. | +| Subir Actualizaciones de Perfil | Cuando actualizas el perfil de un usuario en Okta, Okta actualizará los metadatos de su membrecía en tu organización de {% data variables.product.prodname_dotcom %}. | +| Reactivar Usuarios | Cuando reactivas un usuario en Okta, Okta le enviará una invitación por correo electrónico para que vuelva a unirse a tu organización de {% data variables.product.prodname_dotcom %}. | + +### Prerrequisitos + +{% data reusables.saml.use-classic-ui %} + +### Agregar la aplicación {% data variables.product.prodname_ghe_cloud %} en Okta + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. Da clic en **Agregar** a la derecha de "Github Enterprise Cloud - Organization". ![Dar clic en "Agregar" para la aplicación de {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png) + +5. En el campo **Organizaciòn de GitHub**, teclea el nombre de tu organizaciòn de {% data variables.product.prodname_dotcom %}. Por ejemplo, si la URL de de tu organizaciòn es https://github.com/octo-org, el nombre de organizaciòn serìa `octo-org`. ![Teclear el nombre de organización de GitHub](/assets/images/help/saml/okta-github-organization-name.png) + +6. Haz clic en **Done** (listo). + +### Habilitar y probar el SSO de SAML + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.okta-applications-click-ghec-application-label %} +{% data reusables.saml.assign-yourself-to-okta %} +{% data reusables.saml.okta-sign-on-tab %} +{% data reusables.saml.okta-view-setup-instructions %} +6. Habilita y prueba el SSO de SAML en {% data variables.product.prodname_dotcom %} utilizando la URL de registro, URL del emisor, y certificados pùblicos de la guìa "Còmo configurar SAML 2.0". Para obtener mas información, consulta la sección "[Habilitar y probar el inicio de sesión único de SAML para tu organización](/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization)". + +### Configurar el aprovisionamiento de acceso con SCIM en Okta + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.okta-applications-click-ghec-application-label %} +{% data reusables.saml.okta-provisioning-tab %} +{% data reusables.saml.okta-configure-api-integration %} +{% data reusables.saml.okta-enable-api-integration %} + + +6. Da clic en **Autenticar con Github Enterprise Cloud - Ortanizaction**. ![Botón "Autenticar con GitHub Enterprise Cloud - Organization" para la aplicación de Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. A la derecha del nombre de tu organizaciòn, da clic en **Otorgar**. ![Botón "Otorgar" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **Nota**: si no ves tu organización en la lista, dirígete a `https://github.com/orgs/ORGANIZATION-NAME/sso` en tu buscador y autentícate con ella a través del SSO de SAML utilizando tu cuenta de administrador en el IdP. Por ejemplo, si tu nombre de organización es `octo-org`, La URL sería `https://github.com/orgs/octo-org/sso`. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + + {% endnote %} +1. Da clic en **Autorizar OktaOAN**. ![Botón "Autorizar a OktaOAN" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### Further reading + +- "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)" +- "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) en la documentación de Okta +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) en la documentación de Okta diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000000..60834dddcdf5b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,16 @@ +--- +title: Configurar el periodo de retención para los artefactos y bitácoras de las GitHub actions en tu organización +intro: 'Puedes configurar el periodo de retención para los artefactos y las bitácoras de {% data variables.product.prodname_actions %} en tu organización.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' +--- + +{% data reusables.actions.about-artifact-log-retention %} + +## Configurar el periodo de retención para una organización + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000000..dbc6146519fc3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Conectar tu proveedor de identidad con tu organización +intro: 'Para usar el inicio de sesión único de SAML y SCIM, debes conectar tu proveedor de identidad con tu organización {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +--- + +Antes de [habilitar SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) en tu organización {% data variables.product.product_name %}, deberás conectar tu proveedor de identidad (IdP) con tu organización. + +Puedes buscar los detalles de la implementación de SAML y SCIM para tu IdP en su documentación: +- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) +- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) y [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) +- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) y [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) y [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) +- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) +- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) + +{% note %} + +**Nota:** Los proveedores de identidad que soportan {% data variables.product.product_name %} SCIM son Azure AD, Okta y OneLogin. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/articles/about-scim)". + +{% endnote %} + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000000..904e19335384a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,28 @@ +--- +title: Convertir un equipo de administradores a los permisos de organización mejorados +intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Puedes eliminar la capacidad de los miembros del equipo de administración heredado para crear repositorios al crear un nuevo equipo para esos miembros, asegurándote de que el equipo tenga el acceso necesario a los repositorios de la organización, y eliminando el equipo de administración heredado. + +Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". + +{% warning %} + +**Advertencias:** +- Si hay miembros de su equipo de administración heredados que no son miembros de otros equipos, la eliminación del equipo eliminará a esos miembros de la organización. Antes de eliminar el equipo, asegúrate de que los miembros ya sean miembros directos de la organización, o que tengan acceso de colaborador a los repositorios necesarios. +- Para evitar la pérdida de bifurcaciones privadas realizadas por los miembros del equipo de administradores heredado, debes seguir los pasos 1-3 a continuación antes de eliminar el equipo de administradores heredado. +- Dado que "admin" es un término para los miembros de la organización con [acceso específico a determinados repositorios](/articles/repository-permission-levels-for-an-organization) en la organización, te recomendamos evitar ese término en cualquier nombre de equipo sobre el que puedas decidir. + +{% endwarning %} + +1. [Crear un equipo nuevo](/articles/creating-a-team). +2. [Agregar cada uno de los miembros](/articles/adding-organization-members-to-a-team) de tu equipo de administradores heredado al nuevo equipo. +3. [Brindar al equipo nuevo el acceso equivalente](/articles/managing-team-access-to-an-organization-repository) a cada uno de los repositorios a los que podía acceder el equipo heredado. +4. [Eliminar el equipo de administradores heredado](/articles/deleting-a-team). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000000..1bb80bcaffe17 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user.md @@ -0,0 +1,29 @@ +--- +title: Convertir una organización en un usuario +intro: 'No es posible convertir una organización en una cuenta de usuario personal, pero puedes crear una nueva cuenta de usuario y transferirle los repositorios de la organización.' +redirect_from: + - /articles/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [Regístrate](/articles/signing-up-for-a-new-github-account) para una nueva cuenta de usuario de GitHub. +2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. +4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. +5. [Elimina la organización](/articles/deleting-an-organization-account). +6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. + +{% else %} + +1. Inicia sesión para una nueva cuenta de usuario de GitHub Enterprise. +2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. +4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. +5. [Elimina la organización](/articles/deleting-an-organization-account). +6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. + +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000000..8afa122fbbdeb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,40 @@ +--- +title: Convertir a un miembro de la organización en un colaborador externo +intro: 'Si un miembro actual de tu organización solo necesita acceso a determinados repositorios, como consultores o empleados temporales, puedes convertirlo en un *colaborador externo".' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.owners-and-admins-can %} convertir a los miembros de la organización en colaboradores externos. + +{% data reusables.organizations.outside-collaborators-use-seats %}{% data reusables.organizations.outside_collaborator_forks %} + +Luego de convertir a un miembro de la organización en un colaborador externo, solo tendrá acceso a los repositorios que permite su membresía de equipo actual. La persona ya no será un miembro explícito de la organización, y ya no podrá: + +- Crear equipos +- Ver todos los miembros y equipos de la organización +- @mencionar cualquier equipo visible +- Ser un mantenedor del equipo + +Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)". + +Recomendamos revisar el acceso del miembro de la organización a los repositorios para garantizar que su acceso sea el que esperas. Para obtener más información, consulta la sección "[Administrar el acceso de un individuo a un repositorio de la organización](/articles/managing-an-individual-s-access-to-an-organization-repository)". + +Cuando conviertes a un miembro de la organización en colaborador externo, sus privilegios de miembros de la organización se guardan por tres meses para que puedas restablecer sus privilegios de membrecía si los{% if currentVersion == "free-pro-team@latest" %} invitas a volver a unirse{% else %} agregas de nuevo{% endif %} a tu organización dentro del límite de tiempo establecido. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecciona la persona o las personas a quienes deseas convertir en colaboradores externos. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Menú desplegable con la opción para convertir miembros en colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png) +6. Lee la información sobre cómo convertir miembros en colaboradores externos, luego haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Información sobre permisos de colaboradores externos y botón Convert to outside collaborators (Convertir en colaboradores externos)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### Further reading + +- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" +- "[Convertir a un colaborador externoe en un miembro de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000000..e8bd5ebbc86c9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,40 @@ +--- +title: Convertir un colaborador externo en un miembro de la organización +intro: 'Si te gustaría otorgar más permisos dentro de tu organización a un colaborador externo de los repositorios de la misma, puedes {% if currentVersion == "free-pro-team@latest" %}invitarlo para que se convierta en un miembro de{% else %}hacerlo un miembro de{% endif %} la organización.' +redirect_from: + - /articles/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: Los propietarios de las organizaciones pueden {% if currentVersion == "free-pro-team@latest" %}invitar usuarios para que se unan{% else %}agregar usuarios a{% endif %} éstas. +--- + +{% if currentVersion == "free-pro-team@latest" %} +Si tu organización está en una suscripción de pago por usuario, debes contar con una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro a unirse a tu organización o a reinstalar a un miembro previo de la misma. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". +{% data reusables.organizations.org-invite-expiration %}{% endif %} + +{% if currentVersion != "github-ae@latest" %} +Si tu organización [requiere que los miembros utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization), los usuarios +{% if currentVersion == "free-pro-team@latest" %}que invites deberán [habilitar la autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedan aceptar la invitación.{% else %}deberán [habilitar la autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedas agregarlos a la organización.{% endif %} +{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +{% if currentVersion == "free-pro-team@latest" %} +5. A la derecha del nombre del colaborador externo que quieres convertir en miembro, utiliza el +{% octicon "gear" aria-label="The gear icon" %} menú desplegable y da clic en **Invitar a la organización**.![Invitar colaboradores externos a la organización](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +{% else %} +5. A la derecha del nombre del colaborador externo que quieres hacer miembro, haz clic en **Invite to organization** (Invitar a la organización).![Invitar colaboradores externos a la organización](/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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Further reading + +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000000..4c914ff95c247 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,48 @@ +--- +title: Convertir un equipo de Propietarios a los permisos de organización mejorados +intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. El "Propietario" ahora tiene un rol administrativo otorgado a los miembros individuales de tu organización. Los miembros de tu equipo de Propietarios heredado automáticamente reciben los privilegios del propietario.' +redirect_from: + - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program/ + - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions/ + - /articles/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Tienes algunas opciones para convertir tu equipo de Propietarios heredado: + +- Coloca un nuevo nombre al equipo que denote que los miembros tienen un estado especial en la organización. +- Elimina el equipo luego de asegurarte de que todos los miembros han sido agregados a los equipos que garantizan las acciones necesarias a los repositorios de la organización. + +### Proporcionar al equipo de Propietarios un nuevo nombre + +{% tip %} + + **Nota:** Dado que "admin" es un término para los miembros de la organización con [acceso específico a determinados repositorios](/articles/repository-permission-levels-for-an-organization) en la organización, te recomendamos evitar ese término en cualquier nombre de equipo sobre el que puedas decidir. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. En el campo de nombre del equipo, escoge un nuevo nombre para el equipo Propietarios. Por ejemplo: + - Si muy pocos miembros de tu organización fuesen miembros del equipo Propietarios, puedes designarlo como equipo "Central". + - Si todos los miembros de tu organización fuesen miembros del equipo Propietarios de manera que puedan [@mencionar equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), puedes designar al equipo como "Empleados". ![El campo de nombre del equipo, con el equipo Propietarios con el nuevo nombre Central](/assets/images/help/teams/owners-team-new-name.png) +6. Debajo de la descripción del equipo, haz clic en **Save and continue** (Guardar y continuar). ![El botón para guardar y continuar](/assets/images/help/teams/owners-team-save-and-continue.png) +7. Opcionalmente, [puedes hacer que el equipo sea *público*](/articles/changing-team-visibility). + +### Eliminar el equipo de Propietarios heredado + +{% warning %} + +**Advertencia**: Si hay miembros del equipo de Propietarios heredado que no son miembros de otros equipos, la eliminación del equipo eliminará a esos miembros de la organización. Antes de eliminar el equipo, asegúrate de que los miembros ya sean miembros directos de la organización, o que tengan acceso de colaborador a los repositorios necesarios. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. En la parte inferior de la página, revisa la advertencia y haz clic en **Delete the Owners team** (Eliminar el equipo de Propietarios). ![Enlace para eliminar el equipo de Propietarios](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000000..2dde0c1f9819f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md @@ -0,0 +1,24 @@ +--- +title: Crear una organización nueva desde cero +intro: Crea una organización para aplicar permisos de acceso refinados a los repositorios. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations +--- + +Cuando creas una organización nueva desde cero, esta no tiene ningún repositorio asociado. Para obtener más información acerca de cómo agregar repositorios a tu organización, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" y "[Transferir un repositorio](/articles/transferring-a-repository)". + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Sigue las propuestas para crear tu organización. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información acerca de los planes disponibles para tu equipo, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)".{% endif %} + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %} +- "[Establecer tu correo electrónico de facturación](/articles/setting-your-billing-email)"{% endif %} +- "[Acerca de las organizaciones](/articles/about-organizations)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md new file mode 100644 index 0000000000000..eaace35036953 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md @@ -0,0 +1,34 @@ +--- +title: Crear un equipo +intro: Puedes crear equipos independientes o anidados para administrar los permisos del repositorio y las menciones de grupos de personas. +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo los propietarios y mantenedores de la organización en un equipo padre pueden crear un nuevo equipo hijo debajo del padre. Los propietarios también pueden restringir los permisos de creación para todos los equipos en una organización. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +{% data reusables.organizations.create-team-choose-parent %} +{% if currentVersion == "free-pro-team@latest" %} +1. Como opción, si tu cuenta organizacional o empresarial utiliza la sincronización de equipos, para conectar un grupo de proveedor de identidad a tu equipo, utiliza el menú desplegable "Grupos de Proveedor de Identidad", y selecciona hasta 5 grupos. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. También puede [darle acceso al equipo a los repositorios de la organización](/articles/managing-team-access-to-an-organization-repository). + +### Further reading + +- [Acerca de los equipos](/articles/about-teams)" +- "[Cambiar la visibilidad del equipo](/articles/changing-team-visibility)" +- [Mover un equipo dentro de la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-a-team.md new file mode 100644 index 0000000000000..2b0e3eea57d95 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-a-team.md @@ -0,0 +1,23 @@ +--- +title: Eliminar un equipo +intro: Los propietarios de la organización pueden eliminar equipos en cualquier momento desde la página de configuración del equipo. +redirect_from: + - /articles/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Solo los propietarios de la organización pueden eliminar equipos padres. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Selecciona los equipos que deseas eliminar. ![Lista de miembros con dos equipos seleccionados](/assets/images/help/teams/list-of-teams-selected.png) +5. Sobre la lista de equipos, usa el menú desplegable y haz clic en **Eliminar**. ![Menú desplegable con opción para cambiar la visibilidad del equipo](/assets/images/help/teams/team-bulk-management-options.png) +6. Revisa los equipos que se eliminarán y luego haz clic en **Comprendo. Eliminar estos equipos**. ![Lista de equipos que se eliminarán y botón Eliminar equipos](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md new file mode 100644 index 0000000000000..2fef359b74c3f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -0,0 +1,30 @@ +--- +title: Eliminar una cuenta de una organización +intro: 'Cuando eliminas una organización, se eliminan también todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas del proyecto y de la organización. {% if currentVersion == "free-pro-team@latest" %}El nombre de la organización estará disponible para que otra cuenta de usuario o de organización lo utilice, y tu facturación terminará.{% endif %}' +redirect_from: + - /articles/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Sugerencia**: Si deseas cancelar tu suscripción paga, puedes [bajar la categoría de tu organización a {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) en lugar de eliminar la organización y su contenido. + +{% endtip %} + +{% endif %} + +### 1. Haz una copia de respaldo del contenido de tu organización + +Una vez que eliminas una organización, GitHub **no puede restaurar su contenido**. Por lo tanto, antes de que borres tu organización, asegúrate de que tengas una copia de todos los repositorios, wikis, propuestas y tableros de proyecto de la cuenta. + +### 2. Elimina la organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Junto a la parte inferior de la página de configuración de la organización, haz clic en **Eliminar esta organización**. ![Botón Eliminar esta organización](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000000..759984c1e9650 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,16 @@ +--- +title: Denegar el acceso a una App OAuth anteriormente aprobada para tu organización +intro: 'Si una organización ya no requiere una {% data variables.product.prodname_oauth_app %} previamente autorizada, los propietarios pueden eliminar el acceso de la aplicación a los recursos de la organización.' +redirect_from: + - /articles/denying-access-to-a-previously-approved-application-for-your-organization/ + - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Junto a la aplicación que deseas inhabilitar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Icono Editar](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. Haz clic en **Denegar acceso**. ![Botón Denegar confirmación](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000000..2e5bb236dfe84 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,22 @@ +--- +title: Inhabilitar las restricciones de acceso de las App OAuth para tu organización +intro: 'Los propietarios de la organización pueden inhabilitar las restricciones de las {% data variables.product.prodname_oauth_app %} que tienen acceso a los recursos de la organización.' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +--- + +{% danger %} + +**Advertencia**: Cuando inhabilitas las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización, cualquier miembro de la organización autorizará automáticamente el acceso de {% data variables.product.prodname_oauth_app %} a los recursos privados de la organización cuando aprueben una aplicación para el uso en los parámetros de su cuenta personal. + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Haz clic en **Eliminar restricciones**. ![Botón Eliminar restricciones](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. Revisa la información acerca de la inhabilitación de las restricciones de las aplicaciones de terceros y luego haz clic en **Sí, eliminar las restricciones de las aplicaciones**. ![Botón de eliminar confirmación](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000000..a12147610f136 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Inhabilitar o limitar GitHub Actions para tu organización +intro: 'Los propietarios de organización pueden inhabilitar, habilitar y limitar GitHub Actions para la misma.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Acerca de los permisos de {% data variables.product.prodname_actions %} para tu organización + +{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". + +Puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.enabled-actions-description %}Puedes inhabilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.disabled-actions-description %} + +De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización, pero limitando las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Debajo de **Acciones locales y de terceros**, selecciona una opción. ![Habilitar, inhabilitar o limitar acciones para esta organización](/assets/images/help/repository/enable-org-actions.png) +1. Haz clic en **Save ** (guardar). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización + +Puedes inhabilitar todos los flujos de trabajo para una organización o configurar una política que configure qué acciones pueden utilizarse en una organización. + +{% data reusables.actions.actions-use-policy-settings %} + +{% note %} + +**Nota:** Tal vez no puedas administrar estas configuraciones si la empresa que administra tu organización tiene una política que lo anule. Para obtener más información {% if currentVersion == "free-pro-team@latest" %}"[Requerir las políticas de {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% else %}"[Requerir las políticas de {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Debajo de **Políticas**, selecciona una opción. ![Configurar la política de acciones para esta organización](/assets/images/help/organizations/actions-policy.png) +1. Haz clic en **Save ** (guardar). + +### Permitir que se ejecuten acciones específicas + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Haz clic en **Save ** (guardar). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configurar la política de bifurcaciones privadas para una organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000000..9910356dfa8c7 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Inhabilitar la publicación de sitios de GitHub Pages para tu organización +intro: 'Puedes prevenir que los miembros de tu organización publiquen sitios de {% data variables.product.prodname_pages %} desde repositorios de la misma.' +permissions: 'Los propietarios de la organización pueden inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios en la misma.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>2.22' + github-ae: '*' +--- + +### Acerca de las restricciones de la publicación de sitios de {% data variables.product.prodname_pages %} + +Puedes controlar si los miembros de tu organización pueden publicar sitios web desde repositorios en tu organización utilizando {% data variables.product.prodname_pages %}. Para obtener más información acerca de las {% data variables.product.prodname_pages %}, consulta la sección "[Acerca del {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)". + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet, aún si el repositorio del sitio es privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %}. Para obtener más información, consulta las secciones{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configurar {% data variables.product.prodname_pages %} para tu empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" y {% endif %} "[Acerca de la visibilidad del repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +### Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} + +Después de que inhabilites la publicación de sitios de {% data variables.product.prodname_pages %}, cualquier sitio publicado permanecerá así. Puedes anular la publicación del sitio manualmente. Para obtener más información, consulta la sección "[Anular la publicación de un sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/unpublishing-a-github-pages-site)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +1. Debajo de "Creación de páginas", deselecciona la opción **Permitir que los miembros publiquen sitios**. ![Casilla deseleccionada para la opción "Permitir que los miembros publiquen sitios"](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png) +1. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la opción "Permitir que los miembros publiquen sitios"](/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000000..6e1967740963a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,19 @@ +--- +title: Inhabilitar los debates de equipo para tu organización +intro: Los propietarios de la organización pueden optar por habilitar o inhabilitar los debates de equipo en toda la organización. +redirect_from: + - /articles/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.team-discussions-default %}Para obtener más información acerca de los debates de equipo, consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. En "Debates de equipo", quita la marca de selección de **Habilitar debates de equipo para esta organización**. ![Casilla de verificación para inhabilitar debates de equipo para una organización](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000000..b7bbf211907ab --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,32 @@ +--- +title: Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización +intro: 'Los administradores de la organización deben descargar los códigos de recuperación de inicio de sesión único SAML de la organización para asegurarse de poder acceder a {% data variables.product.product_name %} aun cuando el proveedor de identidad no se encuentre disponible para la organización.' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +--- + +Los códigos de recuperación no se deben compartir ni distribuir. Te recomendamos guardarlos con un administrador de contraseñas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/). + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. En "Inicio de sesión único SAML", en la nota acerca de los códigos de recuperación, haz clic en **Guardar tus códigos de recuperación**. ![Enlace para ver y guardar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_codes.png) +6. Guarda tus códigos de recuperación haciendo clic en **Download** (Descargar), **Print** (Imprimir) o **Copy** (Copiar). ![Botones para descargar, imprimir o copiar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **Nota:** Tus códigos de recuperación te ayudarán a acceder nuevamente a {% data variables.product.product_name %} si tu IdP no está disponible. Si generas nuevos códigos de recuperación, los códigos de recuperación que se muestran en la página "Códigos de recuperación de inicio de sesión único" se actualizarán automáticamente. + + {% endnote %} + +7. Una vez que usas un código de recuperación para obtener acceso nuevamente a {% data variables.product.product_name %}, no puedes volver a usarlo. El acceso a {% data variables.product.product_name %} solo estará disponible durante 24 horas antes de que se te solicite que inicies sesión usando inicio de sesión único. + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Acceder a tu organización cuando tu proveedor de identidad no está disponible](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000000..2327158b72ea3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,48 @@ +--- +title: Habilitar y probar el inicio de sesión único SAML para tu organización +intro: Los administradores y los propietarios de la organización pueden habilitar el inicio de sesión único SAML para agregar una capa más de seguridad a su organización. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +--- + +Puedes habilitar SAML SSO (inicio de sesión único) en tu organización sin requerir que todos los miembros lo usen. Habilitar pero no exigir SAML SSO en tu organización puede facilitar la adopción de SAML SSO por parte de la organización. Una vez que la mayoría de los miembros usen SAML SSO, podrás exigirlo en toda la organización. + +Si habilitas pero no exiges SAML SSO, los miembros de la organización que elijan no usar SAML SSO pueden seguir siendo miembros de esta. Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". + +{% data reusables.saml.outside-collaborators-exemption %} + +Antes de exigir SAML SSO en tu organización, verifica que ya tengas configurado tu proveedor de identidad (IP). Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. En "inicio de sesión único SAML", selecciona **Habilitar autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/saml/saml_enable.png) + + {% note %} + + **Nota:** Luego de habilitar SAML SSO, puedes descargar tus códigos de recuperación de inicio de sesión único para poder acceder a tu organización aun cuando tu IdP no se encuentre disponible. Para obtener más información, consulta "[Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)". + + {% endnote %} + +6. En el campo "URL de inicio de sesión único", escribe el extremo del HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url.png) +7. También puedes escribir tu nombre de emisor SAML en el campo "Emisor". Esto verifica la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) +8. En "Certificado público", copia un certificado para verificar las respuestas SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) +9. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} y luego en los menús desplegables de Método de firma y Método de resumen y elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las solicitudes. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png) +10. Antes de habilitar SAML SSO para tu organización, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png) + + {% tip %} + + **Sugerencia:**{% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. Para implementar SAML SSO y eliminar a todos los miembros de la organización que no se hayan autenticado mediante tu IdP, selecciona **Require SAML SSO authentication for all members of the _organization name_ organization**.** (Requerir autenticación SAML SSO a todos los miembros de la organización [nombre de la organización]). Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Casilla de verificación para requerir SAML SSO para tu organización ](/assets/images/help/saml/saml_require_saml_sso.png)

+12 +Haz clic en **Save ** (guardar). ![Botón para guardar la configuración de SAML SSO](/assets/images/help/saml/saml_save.png) + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000000..d4714b92e510a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Habilitar las restricciones de acceso de las App OAuth para tu organización +intro: 'Los propietarios de la organización pueden habilitar restricciones de acceso de las {% data variables.product.prodname_oauth_app %} para evitar que las aplicaciones que no sean confiables accedan a los recursos de la organización y para permitir que los miembros de la organización usen las {% data variables.product.prodname_oauth_app %} para sus cuentas personales.' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**Advertencias**: +- Habilitar las restricciones de acceso de las {% data variables.product.prodname_oauth_app %} revocará los acesos de la organización a todas las {% data variables.product.prodname_oauth_app %} y claves SSH que hayan sido previamente autorizadas. Para obtener más información, consulta "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)". +- Una vez que hayas configurado las restricciones de acceso de {% data variables.product.prodname_oauth_app %}, asegúrate de autorizar nuevamente toda {% data variables.product.prodname_oauth_app %} que requiera acceso a los datos privados de la organización de manera continua. Todos los miembros de la organización deberán crear nuevas claves SSH y la organización deberá crear nuevas llaves de implementación, según sea necesario. +- Cuando se habilitan las restricciones de acceso de {% data variables.product.prodname_oauth_app %}, las aplicaciones pueden usar un token de OAuth para acceder a información acerca de transacciones en {% data variables.product.prodname_marketplace %}. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. En "Política de acceso de aplicaciones de terceros", haz clic en **Configurar restricciones de acceso de aplicaciones**. ![Botón Configurar restricciones](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. Luego de revisar la información acerca de las restricciones de acceso de las aplicaciones de terceros, haz clic en **Restringir el acceso de aplicaciones de terceros**. ![Botón Confirmar restricciones](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000000..e85dca6a031d4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Hacer cumplir el inicio de sesión único de SAML para tu organización +intro: Los propietarios y los administradores de la organización pueden hacer cumplir el inicio de sesión único de SAML para que todos los miembros de la organización se tengan que autenticar a través de un proveedor de identidad. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +--- + +Si haces cumplir el inicio de sesión único de SAML en tu organización, todo miembro que no se haya autenticado mediante tu proveedor de identidad de SAML (IdP), incluidos los administradores, será eliminado de la organización y recibirá un correo electrónico en el que se le notificará la eliminación. También se eliminarán los bots y las cuentas de servicio que no tengan identidades externas configuradas en el IdP de tu organización. Para obtener más información acerca de los bots y las cuentas de servicio, consulta "[Administrar los bots y las cuentas de servicio con el inicio de sesión único de SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)". Puedes restaurar los miembros de la organización una vez que realizas el inicio de sesión único sin problemas. + +Si tu organización le pertenece a una cuenta de empresa, al habilitar SAML para la cuenta de empresa, se reemplazará la configuración SAML al nivel de organización. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)". + +{% tip %} + +**Sugerencia:**{% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Habilita y prueba el inicio de sesión único de SAML para tu organización. Para obtener más información acerca de este proceso, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)". +2. Luego de seleccionar **Requerir autenticación del inicio de sesión único de SAML para todos los miembros de la organización SAML SSO Org**, se mostrarán los miembros de la organización que no se hayan autenticado mediante tu IdP. Si haces cumplir el inicio de sesión único de SAML, estos miembros se eliminarán de la organización. +3. Haz clic en **Hacer cumplir el inicio de sesión único de SAML** para hacer cumplir el inicio de sesión único de SAML y eliminar a los miembros de la organización que figuren en la lista. + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000000..c4e6541e750cb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,25 @@ +--- +title: Otorgar permisos de "mantenedor del equipo" a un miembro de la organización +intro: 'Un propietario de la organización puede promover a cualquier miembro de la organización a *mantenedor del equipo* de un equipo, otorgándole un subconjunto de privilegios disponibles para los propietarios de la organización.' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Promover un miembro de la organización a mantenedor del equipo + +Antes de promover un miembro de la organización a mantenedor del equipo, la persona ya debe ser miembro del equipo. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. Selecciona la persona o las personas que desees promover a mantenedor del equipo. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) +5. Por encima de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Change role...** (Cambiar rol). ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) +6. Selecciona un rol nuevo y haz clic en **Change role** (Cambiar rol). ![Botones Radio para los roles de Mantenedor o Miembro](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..71591b185c802 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md @@ -0,0 +1,10 @@ +--- +title: Conceder acceso a tu organización con el inicio de sesión único SAML +intro: 'Los administradores de la organización pueden conceder acceso con el inicio de sesión único SAML. Este acceso se les puede conceder a los miembros de la organización, a los bots y a las cuentas de servicio.' +mapTopic: verdadero +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md new file mode 100644 index 0000000000000..55c803083bf2a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -0,0 +1,137 @@ +--- +title: Configurar y administrar organizaciones y equipos +shortTitle: Organizaciones y equipos +intro: Colaborar en muchos proyectos mientras se administra el acceso a proyectos y datos, y se personalizan las configuraciones para tu organización. +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /collaborating-with-groups-in-organizations %} + {% link_in_list /about-organizations %} + {% link_in_list /about-your-organization-dashboard %} + {% link_in_list /creating-a-new-organization-from-scratch %} + {% link_in_list /accessing-your-organizations-settings %} + {% link_in_list /about-your-organizations-news-feed %} + {% link_in_list /viewing-insights-for-your-organization %} +{% topic_link_in_list /managing-membership-in-your-organization %} + {% link_in_list /inviting-users-to-join-your-organization %} + {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} + + {% link_in_list /adding-people-to-your-organization %} + {% link_in_list /removing-a-member-from-your-organization %} + {% link_in_list /reinstating-a-former-member-of-your-organization %} + {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} +{% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} + {% link_in_list /permission-levels-for-an-organization %} + {% link_in_list /maintaining-ownership-continuity-for-your-organization %} + {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} + {% link_in_list /adding-a-billing-manager-to-your-organization %} + {% link_in_list /removing-a-billing-manager-from-your-organization %} +{% topic_link_in_list /organizing-members-into-teams %} + {% link_in_list /about-teams %} + {% link_in_list /creating-a-team %} + {% link_in_list /setting-your-teams-profile-picture %} + {% link_in_list /adding-organization-members-to-a-team %} + {% link_in_list /managing-code-review-assignment-for-your-team %} + {% link_in_list /renaming-a-team %} + {% link_in_list /changing-team-visibility %} + {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} + {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} + {% link_in_list /requesting-to-add-a-child-team %} + {% link_in_list /requesting-to-add-or-change-a-parent-team %} + {% link_in_list /removing-organization-members-from-a-team %} + {% link_in_list /disabling-team-discussions-for-your-organization %} + {% link_in_list /managing-scheduled-reminders-for-your-team %} + {% link_in_list /deleting-a-team %} +{% topic_link_in_list /managing-access-to-your-organizations-repositories %} + {% link_in_list /repository-permission-levels-for-an-organization %} + {% link_in_list /setting-base-permissions-for-an-organization %} + {% link_in_list /viewing-people-with-access-to-your-repository %} + {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} + {% link_in_list /managing-team-access-to-an-organization-repository %} + {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} + {% link_in_list /canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization %} + {% link_in_list /removing-an-outside-collaborator-from-an-organization-repository %} + {% link_in_list /converting-an-organization-member-to-an-outside-collaborator %} + {% link_in_list /converting-an-outside-collaborator-to-an-organization-member %} + {% link_in_list /reinstating-a-former-outside-collaborators-access-to-your-organization %} +{% topic_link_in_list /managing-access-to-your-organizations-project-boards %} + {% link_in_list /project-board-permissions-for-an-organization %} + {% link_in_list /managing-access-to-a-project-board-for-organization-members %} + {% link_in_list /managing-team-access-to-an-organization-project-board %} + {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} + {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} + {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} +{% topic_link_in_list /managing-access-to-your-organizations-apps %} + {% link_in_list /adding-github-app-managers-in-your-organization %} + {% link_in_list /removing-github-app-managers-from-your-organization %} +{% topic_link_in_list /managing-organization-settings %} + {% link_in_list /verifying-your-organizations-domain %} + {% link_in_list /renaming-an-organization %} + {% link_in_list /transferring-organization-ownership %} + {% link_in_list /restricting-repository-creation-in-your-organization %} + {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} + {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} + {% link_in_list /managing-the-forking-policy-for-your-organization %} + {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} + {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} + {% link_in_list /setting-permissions-for-adding-outside-collaborators %} + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} + {% link_in_list /setting-team-creation-permissions-in-your-organization %} + {% link_in_list /managing-scheduled-reminders-for-your-organization %} + {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} + {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} + {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} + {% link_in_list /managing-the-display-of-member-names-in-your-organization %} + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} + {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /deleting-an-organization-account %} + {% link_in_list /converting-an-organization-into-a-user %} + {% link_in_list /integrating-jira-with-your-organization-project-board %} + {% link_in_list /upgrading-to-the-corporate-terms-of-service %} +{% topic_link_in_list /migrating-to-improved-organization-permissions %} + {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} + {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} + {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} +{% topic_link_in_list /restricting-access-to-your-organizations-data %} + {% link_in_list /about-oauth-app-access-restrictions %} + {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} + {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} + {% link_in_list /approving-oauth-apps-for-your-organization %} + {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} +{% topic_link_in_list /keeping-your-organization-secure %} + {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} + {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} + {% link_in_list /requiring-two-factor-authentication-in-your-organization %} + {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} + {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} + {% link_in_list /restricting-email-notifications-to-an-approved-domain %} + {% link_in_list /reviewing-the-audit-log-for-your-organization %} + {% link_in_list /reviewing-your-organizations-installed-integrations %} +{% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} + {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} + {% link_in_list /about-scim %} + {% link_in_list /connecting-your-identity-provider-to-your-organization %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-using-okta %} + {% link_in_list /enabling-and-testing-saml-single-sign-on-for-your-organization %} + {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} + {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} + {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} + {% link_in_list /managing-team-synchronization-for-your-organization %} + {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} +{% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} + {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} + {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} + {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} +{% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} + {% link_in_list /about-ssh-certificate-authorities %} + {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000000..02cf661e1c444 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,25 @@ +--- +title: Integrar Jira al tablero de proyecto de tu organización +intro: 'Puedes integrar Jira Cloud a la cuenta de tu organización para escanear confirmaciones y solicitudes de extracción, creando los metadatos e hipervínculos correspondientes en cualquier propuesta de Jira mencionada.' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. ![Barra lateral Organization name (Nombre de la organización)](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. Haz clic en **Register a new application** (Registrar una aplicación nueva). +5. En **Application name** (Nombre de la aplicación), escribe "Jira". +6. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira. +7. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira. +8. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png) +9. En **Organization owned applications** (Aplicaciones propiedad de la organización), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### Further reading + +- ["Integrar Jira a tus proyectos personales"](/articles/integrating-jira-with-your-personal-projects) +- Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000000..15e5ffea04c17 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Invitar a usuarios para que se unan a tu organización +intro: 'Puedes invitar a cualquier persona a que se convierta en miembro de tu organización usando su nombre de usuario o dirección de correo electrónico {% data variables.product.product_name %}.' +permissions: Los propietarios de las organizaciones pueden invitar usuarios para volverse a unir a una organización. +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tips**: +- Si tu organización tiene una suscripción de pago por usuario, debe de existir una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro para que se una a la organización o antes de reinstaurar a algún miembro previo de la misma. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} +- Si tu organización requiere que los miembros utilicen autenticación bifactorial, los usuarios que invites deben habilitarla antes de aceptar la invitación. Para obtener más información, consulta las secciones "[Requerir autenticación bifactorial en tu organización](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)" y "[Asegurar tu cuenta con la autenticación bifactorial (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.invite_to_org %} +{% data reusables.organizations.choose-to-restore-privileges %} +{% data reusables.organizations.choose-user-role %} +{% data reusables.organizations.add-user-to-teams %} +{% data reusables.organizations.send-invitation %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} + +### Further reading +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md new file mode 100644 index 0000000000000..ff977966b18bd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md @@ -0,0 +1,13 @@ +--- +title: Mantener segura tu organización +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure +intro: 'Los propietarios de la organización tienen varias funciones que los ayudan a mantener seguros los proyectos y los datos. Si eres el propietario de una organización, deberás revisar frecuentemente las bitácoras de auditoría de la misma{% if currentVersion != "github-ae@latest" %}, los estados de 2FA de los miembros,{% endif %} y la configuración de las aplicaciones para garantizar que no haya ocurrido ningún tipo de actividad maliciosa o no autorizada.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000000..5ae3965e7d927 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Mantener la continuidad de propiedad para tu organización +intro: Las organizaciones pueden tener más de un propietario para evitar las intermitencias de propiedad. +redirect_from: + - /articles/changing-a-person-s-role-to-owner + - /articles/changing-a-persons-role-to-owner + - /github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner +permissions: Los propietarios de organizaciones pueden promover a cualquier miembro de una organización a propietario de la misma. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de mantener la continuidad de propiedad para tu organización + +{% data reusables.organizations.org-ownership-recommendation %} + +Los propietarios de una organización tienen acceso administrativo completo a la misma. {% data reusables.organizations.new-org-permissions-more-info %} + +### Designar un propietario de organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecciona la persona o las personas que quisieras promover a propietario. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Arriba de la lista de miembros, usa el menú desplegable y haz clic en **Change role...** (Cambiar rol). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png) +6. Selecciona un nuevo rol para la persona o las personas, luego haz clic en **Change role** (Cambiar rol). ![Botones de opción con roles de propietario y miembros y botón Change role (Cambiar rol)](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000000..3b931c6df32cb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,35 @@ +--- +title: Administrar el acceso a un tablero de proyecto para los miembros de una organización +intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes configurar un nivel de permiso predeterminado para un tablero de proyecto para todos los miembros de la organización.' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Por defecto, los miembros de una organización tienen acceso de escritura a sus tableros de proyecto de la organización excepto que los propietarios de la organización o los administradores de un tablero de proyecto configuren permisos diferentes para tableros de proyecto específicos. + +### Configurar un nivel de permiso base para todos los miembros de la organización + +{% tip %} + +**Sugerencia:** Puedes darle a un miembro de la organización mayores permisos a un tablero de proyecto. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +8. Debajo de "Organization member permission" (Permiso para miembro de la organización), elige un nivel base de permiso para todos los miembros de la organización: **Read** (Lectura), **Write** (Escritura), **Administrar** o **None** (Ninguno). ![Opciones de permiso base a un tablero de proyecto para todos los miembros de una organización](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Haz clic en **Save ** (guardar). + +### Further reading + +- "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md new file mode 100644 index 0000000000000..0fd7e236905a8 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md @@ -0,0 +1,13 @@ +--- +title: Administrar el acceso a las aplicaciones de tu organización +intro: 'Como propietario de la organización, puedes permitir a los miembros individuales de la organización a administrar las aplicaciones {% data variables.product.prodname_github_app %} en tu organización.' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md new file mode 100644 index 0000000000000..5421cdf9cf661 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md @@ -0,0 +1,13 @@ +--- +title: Administrar el acceso a los tableros de proyecto de tu organización +intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes darles a los miembros de la organización, a los equipos o a colaboradores externos diferentes niveles de acceso a tableros de proyecto que son propiedad de tu organización.' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md new file mode 100644 index 0000000000000..46026bf2cd5e1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md @@ -0,0 +1,14 @@ +--- +title: Administrar el acceso a los repositorios de tu organización +intro: Los propietarios de la organización pueden administrar el acceso individual y de equipo a los repositorios de una organización. Los mantenedores del equipo también pueden administrar el acceso a un repositorio de equipo. +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000000..c1d45ab6cb97e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,62 @@ +--- +title: Administrar las direcciones IP permitidas en tu organización +intro: Puedes restringir el acceso a los activos de tu organización si configuras una lista de direcciones IP que se pueden conectar a ella. +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +versions: + free-pro-team: '*' +--- + +Los propietarios de las organizaciones pueden administrar las direcciones IP permitidas en las mismas. + +### Acerca de las direcciones IP permitidas + +Puedes restringir el acceso a los activos de la organización configurando un listado de direcciones IP específicas permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} + +{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} + +{% data reusables.identity-and-permissions.ip-allow-lists-enable %} + +También puedes configurar las direcciones IP permitidas para las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". + +### Agregar una dirección IP permitida + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-description %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} + +### Habilitar direcciones IP permitidas + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. Haz clic en **Save ** (guardar). + +### Editar una dirección IP permitida + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %} +8. Da clic en **Actualizar**. + +### Eliminar una dirección IP permitida + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} +{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %} + +### Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000000..78c2b50d37e7f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,60 @@ +--- +title: Administrar un acceso individual a un tablero de proyecto de una organización +intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes administrar al acceso de un miembro individual a un tablero de proyecto propiedad de tu organización.' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** {% data reusables.project-management.cascading-permissions %} Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)." + +{% endnote %} + +### Otorgarle acceso a un miembro de la organización a un tablero de proyecto + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +9. Debajo de "Buscar por nombre de usuario, nombre completo o dirección de correo electrónico", teclea el nombre del colaborador, nombre de usuario, o +correo electrónico de {% data variables.product.prodname_dotcom %}. + ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} + +### Cambiar el acceso de un miembro de la organización a un tablero de proyecto + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.collaborator-permissions %} + +### Eliminar el acceso de un miembro de la organización a un tablero de proyecto + +Cuando eliminas a un colaborador de un tablero de proyecto, es posible que conserve acceso a un tablero en base a los permisos que tiene por otros roles. Para eliminar de forma completa el acceso a un tablero de proyecto, debes eliminar el acceso para cada rol que tenga esa persona. Por ejemplo, una persona puede tener acceso al tablero de proyecto como miembro de la organización o miembro del equipo. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.remove-collaborator %} + +### Further reading + +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000000..ce45b95e39ad1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,35 @@ +--- +title: Administrar el acceso de una persona a un repositorio de una organización +intro: Puedes administrar el acceso de una persona a un repositorio propiedad de tu organización. +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program/ + - /articles/managing-an-individual-s-access-to-an-organization-repository + - /articles/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos de administrador pueden administrar el acceso de los miembros de la organización y de los colaboradores externos a un repositorio de la organización. + +### Eliminar el acceso a los repositorios + +Cuando eliminas a un colaborador de un repositorio en tu organización, el colaborador pierde el acceso de lectura y escritura al repositorio. Si el repositorio es privado y el colaborador ha bifurcado el repositorio, entonces su bifurcación también se elimina, pero el colaborador conservará cualquier clon local de tu repositorio. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Administrar el acceso de una persona a un repositorio de una organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Haz clic en **Members (Miembros)** o **Outside collaborators (Colaboradores externos)** para administrar las personas con diferentes tipos de acceso. ![Botón para invitar a miembros o colaboradores externos a una organización](/assets/images/help/organizations/select-outside-collaborators.png) +5. A la derecha del nombre de la persona que desearías administrar, utiliza el menú desplegable {% octicon "gear" aria-label="The Settings gear" %}, y haz clic en **Manage (Administrar)**. ![Enlace de acceso al gerente](/assets/images/help/organizations/member-manage-access.png) +6. En la página "Manage access" (Administrar el acceso), al lado del repositorio, haz clic en **Manage access (Administrar el acceso)**. ![Botón de administración de acceso a un repositorio](/assets/images/help/organizations/repository-manage-access.png) +7. Revisa el acceso de la persona a un repositorio determinado, como si fuera un colaborador o si tuviera acceso a un repositorio por medio de una membresía de equipo. ![Matriz de acceso a repositorio para el usuario](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### Further reading + +{% if currentVersion == "free-pro-team@latest" %}- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)"{% endif %} +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000000..1a08d79297c6f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,21 @@ +--- +title: Administrar bot y cuentas de servicio con inicio de sesión único de SAML +intro: Las organizaciones que han habilitado el inicio de sesión único de SAML pueden conservar el acceso para los bot y las cuentas de servicio. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +--- + +Para conservar el acceso a los bot y a las cuentas de servicio, los administradores de la organización pueden [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), pero **no** [implementar](/articles/enforcing-saml-single-sign-on-for-your-organization) el inicio de sesión único de SAML para sus organizaciones. Si debes implementar el inicio de sesión único de SAML para tu organización, puedes crear una identidad externa para el bot o la cuenta de servicio con tu proveedor de identidad (IdP). + +{% warning %} + +**Nota:** Si implementas el inicio de sesión único de SAML para tu organización y **no** tienes identidades externas configuradas para bots y cuentas de servicio con tu IdP, estas se eliminarán de tu organización. + +{% endwarning %} + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000000..ea8b6f6ddec2e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,46 @@ +--- +title: Administrar una tarea de revisión de código para tu equipo +intro: Las tareas de revisión de código indican claramente qué miembros de un equipo se espera emitan una revisión para una solicitud de extracción. +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +--- + +Los mantenedores de equipo y propietarios de organización pueden configurar tareas de revisión de código. + +### Acerca de las tareas de revisión de código + +Al utilizar tareas de revisión de código, cada que se pida a tu equipo revisar una solicitud de extracción, éste se eliminará como revisor y se asignará un subconjunto de miembros específicos del mismo en sustitución. Las tareas de revisión de código te permiten decidir si se notificará a todo el equipo o solo a un subconjunto de miembros del mismo cuando se solicite que éste realice una revisión. + +Cuando se les solicita automáticamente una revisión a los propietarios del código, el equipo se eliminará y reemplazará con los individuos de todos modos. Las aprobaciones individuales no satisfacen el requisito de aprobación del propietario del código en una rama protegida. Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + +### Rutear algoritmos + +Las asignaciones de revisión de código eligen y asignan revisores automáticamente con base en uno de dos algoritmos posibles. + +El algoritmo de round robin (turno rotativo) escoge revisores basándose en quién recibe la solicitud de revisión menos reciente, y se enfoca en alternar entre todos los miembros del equipo sin importar el número de revisiones pendientes que tengan en el momento. + +El algoritmo de balanceo de carga escoge a los revisores basándose en la cantidad total de solicitudes de revisión recientes para cada miembro, y considera el número de revisiones pendientes para cada uno de ellos. El algoritmo de balanceo de carga intenta asegurarse de que cada miembro del equipo revise una cantidad igual de solicitudes de extracción en cualquier periodo de 30 días. + +### Configurar una tarea de revisión de código +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. En la barra lateral izquierda, da clic en **Tarea de revisión de código** ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-button.png) +6. Selecciona **Habilitar auto asignación**. ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-enable.png) +7. Debajo de "¿Cuántos miembros del equipo deberán asignarse para revisión?", utiliza el menú desplegable y elije el número de revisores que se asignarán a cada solicitud de extracción. ![Menú desplegable de cantidad de revisores](/assets/images/help/teams/review-assignment-number.png) +8. Debajo de "Algoritmo de ruteo", utiliza el menú desplegable y elige qué algoritmo quieres utilizar. Para obtener más información, consulta la sección "[Algoritmos de ruteo](#routing-algorithms)". ![Menú desplegable de algoritmo de ruteo](/assets/images/help/teams/review-assignment-algorithm.png) +9. De manera opcional, para siempre omitir miembros específicos del equipo, selecciona **Nunca asignar ciertos miembros del equipo**. Después, selecciona uno o más miembros del equipo que quieras omitir siempre. ![Menú desplegable y casilla de "nunca asignar ciertos miembros del equipo"](/assets/images/help/teams/review-assignment-skip-members.png) +10. De manera opcional, para notificar únicamente a los miembros del equipo que se escogieron por tarea de revisión en cada solicitud revisión de código, selecciona **No notificar a todo el equipo si se asignan miembros específicos** debajo de "Notificaciones". ![Notificaciones de tarea de revisión de código](/assets/images/help/teams/review-assignment-notifications.png) +11. Haz clic en **Guardar cambios**. + +### Inhabilitar una tarea de revisión de código +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Selecciona **Habilitar auto asignación** para eliminar la marca. ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-enable.png) +6. Haz clic en **Guardar cambios**. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000000..230e47b2546af --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Administrar etiquetas predeterminadas para los repositorios de tu organización +intro: Puedes personalizar las etiquetas que se incluirán en todos los repositorios nuevos de tu organización. +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +--- + +Los propietarios de la organización pueden administrar las etiquetas predeterminadas para los repositorios de la organización. + +Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de tu organización, pero luego cualquier usuario con acceso de escritura al repositorio puede editar o eliminar las etiquetas de ese repositorio. Agregar, editar o eliminar una etiqueta predeterminada no agrega, edita o elimina la etiqueta de los repositorios existentes. + +### Crear una etiqueta predeterminada + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.organizations.repository-defaults %} +{% else %} +{% data reusables.organizations.repository-labels %} +{% endif %} +5. Debajo de "Repository labels" (Etiquetas del repositorio), haz clic en **New label** (Etiqueta nueva). ![Botón New update (Actualización nueva)](/assets/images/help/organizations/new-label-button.png) +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.create-label %} + +### Editar una etiqueta predeterminada + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.organizations.repository-defaults %} +{% else %} +{% data reusables.organizations.repository-labels %} +{% endif %} +{% data reusables.project-management.edit-label %} +{% data reusables.project-management.name-label %} +{% data reusables.project-management.label-description %} +{% data reusables.project-management.label-color-randomizer %} +{% data reusables.project-management.save-label %} + +### Eliminar una etiqueta predeterminada + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.organizations.repository-defaults %} +{% else %} +{% data reusables.organizations.repository-labels %} +{% endif %} +{% data reusables.project-management.delete-label %} +{% data reusables.project-management.confirm-label-deletion %} + +### Further reading + +- "[Acerca de las etiquetas](/articles/about-labels)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000000..041367a88c141 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Administrar la creación de debates para los repositorios de tu organización +intro: Puedes elegir los niveles de permiso que requieren los miembros para crear los debates en los repositorios que pertenezcan a tu organización. +permissions: Los propietarios de las organizaciones pueden administrar la creación de debates para los repositorios que pertenecen a éstas. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Permitir o dejar de permitir usuarios con acceso de lectura para crear debates + +Predeterminadamente, los miembros de la organización que tengan acceso de lectura pueden crear debates si un administrador de repositorio o propietario de organización habilita los debates en cualquier repositorio que pertenezca a ella. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Debajo de "Debates del repositorio", selecciona o deselecciona **Permitir que los usuarios con acceso de lectura creen debates**. ![Casilla de verificación para permitir que las personas con acceso de lectura creen debates](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración de debates](/assets/images/help/discussions/click-save.png) + +### Further reading + +- "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md new file mode 100644 index 0000000000000..bf0641ab90452 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md @@ -0,0 +1,14 @@ +--- +title: Administrar el acceso de Git a los repositorios de tu organización +intro: Puedes agregar una autoridad de certificados (CA) SSH a tu organización y permitir que los miembros accedan a los repositorios de la organización sobre Git mediante claves firmadas por la CA SSH. +mapTopic: verdadero +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities/ + - /articles/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md new file mode 100644 index 0000000000000..562096b05144f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Administrar la membresía en tu organización +intro: 'Después de que creas tu organización, puedes {% if currentVersion == "free-pro-team@latest" %}invitar a las personas para convertirse en{% else %}agregar personas como{% endif %} miembros de la organización. También puedes eliminar a miembros de la organización y reinstalar a miembros antiguos.' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md new file mode 100644 index 0000000000000..9350a93c05431 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md @@ -0,0 +1,12 @@ +--- +title: Administrar configuraciones de la organización +intro: 'Los administradores de la organización pueden cambiar diversas configuraciones, incluidos los nombres de los repositorios que pertenecen a la organización y la membresía de equipo de los propietarios. Además, los administradores de la organización pueden eliminar a la organización y a todos sus repositorios.' +mapTopic: verdadero +redirect_from: + - /articles/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md new file mode 100644 index 0000000000000..6d571356c5cc4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md @@ -0,0 +1,13 @@ +--- +title: Administrar el acceso de las personas a tu organización con roles +intro: 'El rol de una persona en tu organización define su nivel de acceso a tu organización, sus configuraciones y tus datos. Puedes convertir a personas en propietarios, miembros o gerentes de facturación para tu organización, o puedes darles permisos de mantenedor del equipo.' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000000..29b8c0086e3d0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,11 @@ +--- +title: Administrar el inicio de sesión único de SAML para tu organización +intro: Los administradores de la organización pueden administrar las identidades y el acceso a la organización de los miembros con el inicio de sesión único (SSO) de SAML. +mapTopic: verdadero +redirect_from: + - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on/ + - /articles/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000000..f1455416069ed --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,59 @@ +--- +title: Administrar los recordatorios programados para tu organización +intro: Puedes obtener recordatorios en Slack para todas las solicitudes de extracción de las cuales se haya solicitado revisión por parte de los equipos en tu organización. +versions: + free-pro-team: '*' +--- + +### Acerca de los recordatorios programados para las solicitudes de extracción + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Los propietarios de la organización pueden programar un recordatorio para uno mas equipos en ella que contemple todas las solicitudes de extracción que han solicitado la revisión de uno o más equipos de ésta. + +### Crear un recordatorio programado para una organización +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.add-reminder %} +{% data reusables.reminders.authorize-slack %} +{% data reusables.reminders.slack-channel %} +{% data reusables.reminders.days-dropdown %} +{% data reusables.reminders.times-dropdowns %} +{% data reusables.reminders.tracked-repos %} +11. Da clic en el menú desplegable de **Añadir equipo** debajo de "Filtrar por equipo asignado para revisar el código", y elige uno o más equipos. Puedes agregar hasta 100 equipos. Si el equipo que seleccionas carece de acceso a los "Repositorios rastreados" seleccionados anteriormente, no podrás crear el recordatorio programado. ![Menú desplegable de añadir un equipo](/assets/images/help/organizations/scheduled-reminders-add-teams.png) +{% data reusables.reminders.ignore-drafts %} +{% data reusables.reminders.no-review-requests %} +{% data reusables.reminders.author-reviews %} +{% data reusables.reminders.approved-prs %} +{% data reusables.reminders.min-age %} +{% data reusables.reminders.min-staleness %} +{% data reusables.reminders.ignored-terms %} +{% data reusables.reminders.ignored-labels %} +{% data reusables.reminders.required-labels %} +{% data reusables.reminders.create-reminder %} + +### Administrar un recordatorio programado para una organización +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Borrar un recordatorio programado para una organización +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### Further reading + +- "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000000..e1dc1c80ad0a3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,63 @@ +--- +title: Administrar recordatorios programados para tu equipo +intro: Puedes obtener recordatorios en Slack cuando existan solicitudes de extracción pendientes de revisión por parte de tu equipo. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests +versions: + free-pro-team: '*' +--- + +### Acerca de los recordatorios programados para equipos + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Los mantenedores de equipo y propietarios de organización pueden configurar recordatorios programados para cualquier solicitud de extracción que tenga una solicitud de revisión por parte de sus equipos. Antes de que puedas crear un recordatorio programado para tu equipo, un propietario de la organización debe autorizar tu espacio de trabajo de Slack. Para obtener más información, consulta la sección "[Administrar recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)". + +### Crear un recordatorio programado para un equipo +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.add-reminder %} +{% data reusables.reminders.authorize-slack %} +{% data reusables.reminders.slack-channel %} +{% data reusables.reminders.days-dropdown %} +{% data reusables.reminders.times-dropdowns %} +{% data reusables.reminders.tracked-repos %} +{% data reusables.reminders.ignore-drafts %} +{% data reusables.reminders.no-review-requests %} +{% data reusables.reminders.author-reviews %} +{% data reusables.reminders.approved-prs %} +{% data reusables.reminders.min-age %} +{% data reusables.reminders.min-staleness %} +{% data reusables.reminders.ignored-terms %} +{% data reusables.reminders.ignored-labels %} +{% data reusables.reminders.required-labels %} +{% data reusables.reminders.create-reminder %} + +### Administrar un recordatorio programado para un equipo +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Borrar un recordatorio programado para un equipo +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### Further reading + +- "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" +- "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000000..fa9c18a924335 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,102 @@ +--- +title: Administrar los parámetros de seguridad y análisis para tu organización +intro: 'Puedes controlar las características que aseguran y analizan el código en los proyectos de tu organización en {% data variables.product.prodname_dotcom %}.' +permissions: Los propietarios de la organización pueden administrar los parámetros de seguridad y de análisis para los repositorios en la organización. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### Acerca de la administración de los parámetros de seguridad y análisis + +{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar los repositorios en tu organización. Puedes administrar las características de seguridad y de análisis para todos los repositorios existentes que los miembros creen en tu organización. {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} + +### Mostrar la configuración de seguridad y de análisis + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security-and-analysis %} + +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} + +### Habilitar o inhabilitar una característica para todos los repositorios existentes + +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + +1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". +1. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. + {% if currentVersion == "free-pro-team@latest" %} + ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. + {% if currentVersion == "free-pro-team@latest" %} + ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Da clic en **Inhabilitar CARACTERÍSTICA** o en **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios en tu organización. + {% if currentVersion == "free-pro-team@latest" %} + ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} + +### Enabling or disabling a feature automatically when new repositories are added + +1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Permitir que el Dependabot acceda a los repositorios privados + +{% data reusables.dependabot.beta-note %} + +El {% data variables.product.prodname_dependabot %} puede verificar si hay referencias obsoletas de las dependencias en un proyecto y generar automáticamente una solicitud de cambios para actualizarlas. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios privados. Sin embargo, si una dependencia se encuentra en un repositorio privado de {% data variables.product.prodname_dotcom %} dentro de la misma organización que el proyecto que la utiliza, puedes permitir al {% data variables.product.prodname_dependabot %} actualizar la versión exitosamente si le otorgas acceso al repositorio en el que se hospeda. Para obtener más información, incluyendo los detalles de las limitaciones para el soporte de la dependencia privada, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". + +1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". +1. En la sección de "acceso al repositorio del {% data variables.product.prodname_dependabot %}", da clic en el botón de configuración **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) Se muestra una lista que presenta todos los repositorios privados de tu organización. ![La lista de repositorios](/assets/images/help/organizations/repositories-dialog.png) +1. Selecciona los repositorios a los que puede acceder el {% data variables.product.prodname_dependabot %}. +1. Da clic en **Seleccionar repositorios**. +{% endif %} + +### Further reading + +- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} +- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Administrar las vulnerabilidades en las dependencias de tu proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000000..94303813439e9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,48 @@ +--- +title: Administrar acceso de equipo a un tablero de proyecto de una organización +intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes darle acceso de equipo a un tablero de proyecto propiedad de tu organización.' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% warning %} + +**Advertencias:** +- Puedes cambiar el nivel de permiso de un equipo si el equipo tiene acceso directo a un tablero de proyecto. Si el acceso del equipo a un tablero de proyecto se hereda de un equipo padre, debes cambiar el acceso del equipo padre al tablero de proyecto. +- Si agregas o eliminas acceso a un tablero de proyecto para un equipo padre, cada uno de esos equipos hijos también recibirá o perderá acceso al tablero de proyecto. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". + +{% endwarning %} + +### Otorgarle a un equipo acceso a un tablero de proyecto + +Puedes otorgarle a un equipo completo el mismo nivel de permiso a un tablero de proyecto. + +{% note %} + +**Nota:** {% data reusables.project-management.cascading-permissions %} Por ejemplo, si un propietario de la organización le ha otorgado a un equipo permisos de lectura a un tablero de proyecto y un administrador de tablero de proyecto le otorga a uno de los miembros del equipo permisos de administrador a ese tablero como colaborador individual, esa persona tendría permisos de administrador al tablero de proyecto. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)." + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +8. En la barra lateral izquierda, haz clic en **Teams (Equipos)**. +9. Para agregar un equipo, haz clic en **Add a team: Select team (Agregar un equipo: seleccionar equipo)**. Después, elige un equipo del menú desplegable o busca el equipo que deseas agregar. ![Agregar un menú desplegable de equipo con una lista de equipos en la organización](/assets/images/help/projects/add-a-team.png) +10. Junto al nombre del equipo, utiliza el menú desplegable para seleccionar el nivel de permiso deseado: **Read** (Lectura), **Write** (Escritura) o **Admin** (Administración). ![Menú desplegable de permisos de equipo con opciones de lectura, escritura o administrador](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### Configurar el acceso de un equipo a un tablero de proyecto + +Si un equipo hereda el acceso a un tablero de proyecto desde un equipo padre, deberás cambiar el acceso de dicho equipo padre a este tablero para actualizar el acceso de los equipos hijos. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Encima de la conversación del equipo, haz clic en {% octicon "project" aria-label="The Projects icon" %} **Projects (Proyectos)**. ![La pestaña de repositorios del equipo](/assets/images/help/organizations/team-project-board-button.png) +5. Para cambiar los niveles de permiso, utiliza el menú desplegable que se encuentra al costado derecho del tablero de proyecto que quieres actualizar. Para elminar un tablero de proyecto, da clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botón para eliminar un tablero de proyecto de la papelera del equipo](/assets/images/help/organizations/trash-button.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000000..ee001422a169f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,49 @@ +--- +title: Administrar el acceso de equipo a un repositorio de la organización +intro: 'Puedes darle acceso de equipo a un repositorio, eliminar el acceso del equipo sobre un repositorio, o cambiar el nivel de permiso del equipo sobre un repositorio.' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con acceso de administrador a un repositorio pueden administrar el acceso del equipo a un repositorio. Los mantenedores del equipo pueden eliminar el acceso de un equipo a un repositorio. + +{% warning %} + +**Advertencias:** +- Puedes cambiar el nivel de permiso de un equipo si el equipo tiene acceso directo a un repositorio. Si el acceso del equipo a un repositorio se hereda de un equipo padre, debes cambiar el acceso del equipo padre al repositorio. +- Si agregas o eliminas el acceso al repositorio de un equipo padre, cada uno de sus equipos hijos también recibirá o perderá el acceso al repositorio. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". + +{% endwarning %} + +### Otorgarle a un equipo acceso a un repositorio + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Encima de la lista de repositorios, haz clic en **Add repository (Agregar repositorio)**. ![Botón Agregar repositorio](/assets/images/help/organizations/add-repositories-button.png) +6. Escribe el nombre de un repositorio, después haz clic en **Add repository to team (Agregar repositorio al equipo)**. ![Campo Buscar repositorio](/assets/images/help/organizations/team-repositories-add.png) +7. De forma opcional, a la derecha del nombre del repositorio, utiliza el menú desplegable y elige un nivel de permiso diferente para el equipo. ![Menú desplegable de nivel de acceso a un repositorio](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### Eliminar el acceso de un equipo a un repositorio + +Puedes eliminar el acceso de un equipo a un repositorio si el equipo tiene acceso directo a un repositorio. Si el acceso de un equipo al repositorio se hereda de un equipo padre, debes eliminar el repositorio del equipo padre para poder eliminar el repositorio de los equipos hijos. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Selecciona el repositorio o los repositorios que deseas eliminar del equipo. ![Lista de repositorios de equipo con casillas de verificación para algunos repositorios seleccionados](/assets/images/help/teams/select-team-repositories-bulk.png) +6. Encima de la lista de repositorios, utiliza el menú desplegable, y haz clic en **Remove from team (Eliminar del equipo)**. ![Menú desplegable con la opción de eliminar un repositorio de un equipo](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. Revisa el o los repositorios que serán eliminados del equipo, después haz clic en **Remove repositories (Eliminar repositorios)**. ![Casilla modal con una lista de repositorios a los que el equipo ya no tiene acceso](/assets/images/help/teams/confirm-remove-team-repos.png) + +### Further reading + +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000000..b06af7908536e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,75 @@ +--- +title: Administrar la sincronización de equipos para tu organización +intro: 'Puedes habilitar e inhabilitar la sincronización entre tu Proveedor de Identidad (IdP) y tu organización en {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.team-synchronization %}' +redirect_from: + - /articles/synchronizing-teams-between-your-identity-provider-and-github + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github + - /github/articles/synchronizing-teams-between-okta-and-github +permissions: Los propietarios de las organizaciones pueden administrar la sincronización de equipos a una organización. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Acerca de la sincronización de equipo + +Puedes habilitar la sincronización de equipos entre tu IdP y {% data variables.product.product_name %} para permitir a los propietarios de la organización y a los mantenedores de equipo conectar equipos en tu organización con grupos de IdP. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.supported-idps-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +También puedes habilitar la sincronización de equipos para las organizaciones que pertenezcan a tu cuenta empresarial. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)". + +### Habilitar la sincronización de equipo + +Los pasos para habilitar la sincronización de equipos dependen del IdP que quieras utilizar. Existen prerrequisitos aplicables a cada IdP para habilitar la sincronización de equipos. Cada IdP individual tiene prerrequisitos adicionales. + +#### Prerrequisitos + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +Debes habilitar el inicio de sesión único de SAML para tu organización y tu IdP compatible. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". + +Debes autenticarte con tu organización utilizando el SSO de SAML y el IdP compatible. Para obtener más información, consulta "[Acerca de la autenticación con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)". + +#### Habilitar la sincronización de equipos para Azure AD + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después haz clic en **Approve (Aprobar)**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) + +#### Habilitar la sincronización de equipos para Okta + +{% data reusables.identity-and-permissions.team-sync-okta-requirements %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-okta %} +7. Debajo del nombre de tu organización, teclea un token SSWS válido y la URL de tu instancia de Okta. ![Formulario organizacional de Okta para habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después da clic en **Crear**. ![Botón de crear en habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Inhabilitar la sincronización de equipo + +{% data reusables.identity-and-permissions.team-sync-disable %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. Dentro de "Team synchronization" (Sincronización de equipo), haz clic en **Disable team synchronization (Inhabilitar la sincronización de equipo)**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000000..b75b08fd4d5bd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Administrar el nombre de la rama predeterminada para los repositorios en tu organización +intro: 'Puedes configurar el nombre de la rama predeterminada para los repositorios que los miembros crean en tu organización en {% data variables.product.product_location %}.' +permissions: Los propietarios de la organización pueden administrar el nombre de la rama predeterminada para los repositorios nuevos de la misma. +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +--- + +### Acerca de la administración del nombre de la rama predeterminada + +Cuadno un miembro de tu organización crea un repositorio nuevo en la misma, éste contendrá una rama que será la predeterminada. Puedes cambiar el nombre que {% data variables.product.product_name %} utiliza para dicha rama en los repositorios nuevos que creen los miembros de tu organización. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". + +{% data reusables.branches.change-default-branch %} + +Si un propietario de la empresa requirió una política para el nombre de la rama predeterminada de tu empresa, no puedes configurar dicho nombre en tu organización. En su lugar, puedes cambiar la rama predeterminada para los repositorios individuales. Para obtener más información, consulta las secciones {% if currentVersion == "free-pro-team@latest" %}"[Requerir políticas de administración de repositorios en tu 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 %}"[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)"{% endif %} y "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)". + +### Configurar el nombre de la rama predeterminada + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Debajo de "Rama predeterminada del repositorio", da clic en **Cambiar el nombre de la rama predeterminada ahora**. ![Botón de ignorar](/assets/images/help/organizations/repo-default-name-button.png) +4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/organizations/repo-default-name-text.png) +5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/organizations/repo-default-name-update.png) + +### Further reading + +- "[Administrar el nombre de la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000000..511e04c817d21 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Administrar la visualización de los nombres de los miembros en tu organización +intro: Puedes permitir que los miembros de tu organización vean un nombre de perfil del autor de un comentarios en los repositorios privados en la organización. +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios de la organización pueden administrar la visualización de los nombres de los miembros en una organización. + +![Nombre del perfil del autor del comentario que se muestra en un comentario](/assets/images/help/issues/commenter-full-name.png) + +Cada miembro de la organización elige su propio nombre de perfil en sus configuraciones. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Dentro de "Admin repository permissions" (Permisos del administrador del repositorio), selecciona o quita la marca de selección **Allow members to see comment author's profile name in private repositories (Permitir que los miembros vean el nombre de perfil del autor del comentario en los repositorios privados)**. ![Casilla de verificación para permitir que los miembros vean el nombre completo del autor del comentario en los repositorios privados](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000000..fbf902e05dd99 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Administrar la política de bifurcación para tu organización +intro: 'Puedes permitir o prevenir la bifurcación de cualquier repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} e interno{% endif %} que pertenezca a tu organización.' +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: Los propietarios de la organización pueden administrar la política de bifurcación para la misma. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Predeterminadamente, las organizaciones nuevas se configuran para no permitir que se bifurquen los repositorios privados{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} e internos{% endif %}. + +Si permites que se bifurquen los repositorios privados{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} e internos{% endif %} a nivel organizacional, también puedes configurar la capacidad de bifurcar un repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} específico. Para obtener más información, consulta la sección "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Debajo de "Bifurcación de repositorios", selecciona **Permitir la bifurcación de repositorios privados** o **Permitir la bifurcación de repositorios privados e internos**. ![Casilla de verificación para permitir o prohibir la bifurcación en la organización](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Haz clic en **Save ** (guardar). + +### Further reading + +- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000000..ac3876f1fd959 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Administrar las actualizaciones de las cuentas que patrocina tu organización +intro: Puedes administrar la dirección de correo electrónico que recibe las actualizaciones de las cuentas que patrocina tu organización. +versions: + free-pro-team: '*' +permissions: Los propietarios de las organizaciones pueden administrar las actualizaciones de las cuentas que patrocinan dichas organizaciones. +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +Los desarrolladores y organizaciones que patrocine tu organización pueden enviarte actualizaciones sobre su trabajo. Puedes administrar la dirección de correo electrónico que recibe estas actualizaciones. + +También puedes inhabilitar las actualizaciones de las cuentas que tu organización patrocine. Para obtener más información, consulta "[Administar tu patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. Debajo de "correo electrónico de actualización de patrocinios (Privado)", teclea la dirección de correo electrónico de la cual deseas recibir actualizaciones sobre las cuentas que patrocina tu organización. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/organizations/update-profile-button.png) + +### Further reading + +- "[Apoyar a la comunidad de código abierto con {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" \ No newline at end of file diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000000..1481c5263bf0d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,34 @@ +--- +title: Administrar las autoridades de certificación SSH de tu organización +intro: Puedes agregar o eliminar autoridades de certificación SSH desde tu organización. +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios de la organización pueden administrar autoridades de certificado (CA) SSH de la organización + +Puedes permitir que los miembros accedan a los repositorios d ela organización mediante certificados SSH que brindas al agregar un CA SSH a tu organización. {% data reusables.organizations.can-require-ssh-cert %}Para obtener más información, consulta "[Acerca de las autoridades de certificados de SSH](/articles/about-ssh-certificate-authorities)". + +### Agregar una autoridad de certificado de SSH + +{% data reusables.organizations.add-extension-to-cert %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.new-ssh-ca %} +{% data reusables.organizations.require-ssh-cert %} + +### Eliminar una autoridad de certificado de SSH + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.delete-ssh-ca %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000000..b53b3a79edd81 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,40 @@ +--- +title: Migrar los equipos de administradores a permisos de organización mejorados +intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Por defecto, todos los miembros de la organización pueden crear repositorios. Si restringes los [permisos de creación de repositorios](/articles/restricting-repository-creation-in-your-organization) a los propietarios de la organización y tu organización fue creada dentro de la estructura heredada de permisos de organización, los miembros de los equipos de administración heredados seguirán teniendo la capacidad de crear repositorios. + +Los equipos de administración heredados son equipos que fueron creados con el nivel de permiso de administración dentro de la estructura heredada de permisos de organización. Los miembros de estos equipos pudieron crear repositorios para la organización, y hemos conservado esta capacidad en la estructura mejorada de permisos de la organización. + +Puedes eliminar esta capacidad al migrar tus equipos de administradores heredados a los permisos mejorados de la organización. + +Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". + +{% warning %} + +**Advertencia:** si tu organización ha inhabilitado [los permisos de creación de repositorio](/articles/restricting-repository-creation-in-your-organization) para todos los miembros, algunos miembros de los equipos de administradores heredados pueden perder los permisos de creación de repositorio. Si tu organización ha habilitado la creación de repositorio de miembro, migrar los equipos de administradores heredados a los permisos mejorados de la organización no afectará la capacidad de los miembros del equipo de crear repositorios. + +{% endwarning %} + +### Migrar todos tus equipos de administradores heredados de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Revisa tus equipos de administradores heredados de la organización, después haz clic en **Migrate all teams (Migrar todos los equipos)**. ![Botón Migrar todos los equipos](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. Lee la información sobre los posibles cambios en permisos para los miembros de estos equipos, después haz clic en **Migrate all teams (Migrar todos los equipos).** ![Botón Confirmar migración](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### Migrar un equipo de administradores único + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. En la casilla de descripción de equipo, haz clic en **Migrate team (Migrar equipo)**. ![Botón Migrar equipo](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md new file mode 100644 index 0000000000000..447439fd04ec6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md @@ -0,0 +1,14 @@ +--- +title: Migrar a permisos de organización mejorados +intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización incluye los permisos de la organización mejorados por defecto. Es posible que las organizaciones creadas antes de septiembre de 2015 necesiten migrar a los antiguos equipos de administradores para el modelo mejorado de permisos de la organización.' +mapTopic: verdadero +redirect_from: + - /articles/improved-organization-permissions/ + - /articles/github-direct-organization-membership-pre-release-guide/ + - /articles/migrating-your-organization-to-improved-organization-permissions/ + - /articles/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000000..175875daba9d9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,38 @@ +--- +title: Mover un equipo en la jerarquía de tu organización +intro: 'Los mantenedores del equipo y los propietarios de la organización pueden anidar un equipo bajo un equipo padre, o cambiar o eliminar un equipo padre de un equipo anidado.' +redirect_from: + - /articles/changing-a-team-s-parent/ + - /articles/moving-a-team-in-your-organization-s-hierarchy + - /articles/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios de la organización pueden cambiar el padre de cualquier equipo. Los mantenedores del equipo pueden cambiar el equipo padre de un equipo si son mantenedores tanto en el equipo hijo como en el equipo padre. Los mantenedores del equipo sin permisos de mantenedor en el equipo hijo puede solicitar agregar un equipo padre o hijo. Para obtener más información, consulta "[Solicitar agregar o cambiar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team)" y "[Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team)." + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**Tips:** +- No puedes cambiar el equipo padre de un equipo a un equipo secreto. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". +- No puedes anidar un equipo padre debajo de uno de sus equipos hijos. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. En la lista de equipos, haz clic en el nombre del equipo cuyo padre deseas cambiar. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Utiliza el menú desplegable para elegir un equipo padre, o para eliminar un equipo padre existente, selecciona **Clear selected value (Borrar el valor seleccionado)**. ![Menú desplegable que enumera los equipos de la organización](/assets/images/help/teams/choose-parent-team.png) +7. Da clic en **Actualizar**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Haz clic en **Confirm new parent team (Confirmar nuevo equipo padre)**. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) + +### Further reading + +- [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md new file mode 100644 index 0000000000000..c04c48ba04676 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md @@ -0,0 +1,20 @@ +--- +title: Organizar miembros en un equipo +intro: Puedes agrupar miembros de la organización en equipos que reflejen la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. +redirect_from: + - /articles/setting-up-teams-improved-organization-permissions/ + - /articles/setting-up-teams-for-accessing-organization-repositories/ + - /articles/creating-teams/ + - /articles/adding-people-to-teams-in-an-organization/ + - /articles/removing-a-member-from-a-team-in-your-organization/ + - /articles/setting-up-teams/ + - /articles/maintaining-teams-improved-organization-permissions/ + - /articles/maintaining-teams/ + - /articles/organizing-members-into-teams +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md new file mode 100644 index 0000000000000..df9549201566f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -0,0 +1,139 @@ +--- +title: Niveles de permiso para una organización +intro: 'Después de seleccionar [create an organization (crear una organización)](/articles/creating-a-new-organization-account), deberías dar permisos de propietario a un pequeño grupo de personas que administrarán la cuenta de la organización.' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Niveles de permiso para una organización + +Los miembros de la organización pueden tener roles de *propietario*{% if currentVersion == "free-pro-team@latest" %}, *gerente de facturación*,{% endif %} o de *miembro*: + +- Los **Propietarios** tienen acceso administrativo completo a tu organización. Este rol debe limitarse a dos personas, por lo mucho, en tu organización. Para obtener más información, consulta la sección "[Mantener la continuidad de la propiedad para tu organización](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)". +{% if currentVersion == "free-pro-team@latest" %} +- El acceso como **Gerente de facturación** le permite a una persona administrar las configuraciones de facturación. Para obtener más información, consulta "[Agregar un gerente de facturación a tu organización](/articles/adding-a-billing-manager-to-your-organization)". +{% endif %} +- El acceso como **Miembros** es el rol por defecto para todo el resto. + +{% if currentVersion == "free-pro-team@latest" %} + + +| Acción de organización | Propietarios | Miembros | Gerentes de facturación | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------:|:--------:|:--------------------------------------------------:| +| Crear repositorios (consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)" para obtener más detalles) | **X** | **X** | | +| Ver y editar la información de facturación | **X** | | **X** | +| Invitar personas para que se unan a la organización | **X** | | | +| Editar y cancelar invitaciones para unirse a la organización | **X** | | | +| Eliminar miembros de tu organización | **X** | | | +| Reinstalar antiguos miembros a la organización | **X** | | | +| Agregar o eliminar personas de **todos los equipos** | **X** | | | +| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | | | +| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Configurar los recordatorios programados (consulta la sección "[Administrar los recordatorios programados para solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Agregar colaboradores a **todos los repositorios** | **X** | | | +| Acceder al registro de auditoría de la organización | **X** | | | +| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/articles/about-your-organization-s-profile)" para obtener más detalles) | **X** | | | +| Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles) | **X** | | | +| Restringir las notificaciones de correo electrónico a los dominios verificados (consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" para obtener más detalles) | **X** | | | +| Eliminar **todos los equipos** | **X** | | | +| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | | +| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | | +| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | +| Ver todos los miembros y equipos de la organización | **X** | **X** | | +| @mencionar cualquier equipo visible | **X** | **X** | | +| Poder convertirse en *mantenedor del equipo* | **X** | **X** | | +| Ver información de la organización (consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization)" para obtener más detalles) | **X** | **X** | | +| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | **X** | | +| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | +| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | | +| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} +| Administrar vistas de la información de las dependencias de la organización (consulta "[Cambiar la visibilidad de la información de las dependencias de tu organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para obtener más detalles) | **X** | | |{% endif %} +| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | | +| Patrocinar cuentas y administrar los patrocionos de la organización (consulta la sección "[Patrocinar contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para obener más detalles) | **X** | **X** | | +| Administrar las actualizaciones de las cuentas patrocinadas (consulta la sección "[Administrar las actualizaciones de los patrocinadores de tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" para obtener más detalles) | **X** | | | +| Atribuir tus patrocinios a otra organización (consulta la sección "[Atribuir los patrocionios a tu organización](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obtener más detalles) | **X** | | | +| Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización (consulta "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para encontrar más detalles) | **X** | | | +| Administrar la configuración de seguridad y de análisis (consulta la sección "[Administrar la configuración de seguridad y de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **X** | | | +| Habilitar y aplicar el [inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [Administrar el acceso de SAML de un usuario a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | | +| Transferir repositorios | **X** | | | +| Comprar, instalar, administrar la facturación y cancelar aplicaciones {% data variables.product.prodname_marketplace %} | **X** | | | +| Enumerar aplicaciones en {% data variables.product.prodname_marketplace %} | **X** | | |{% if currentVersion != "github-ae@latest" %} +| Recibe [{% data variables.product.prodname_dependabot_alerts %} sobre las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos los repositorios de una organización | **X** | | | +| Administrar las {% data variables.product.prodname_dependabot_security_updates %} (consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | |{% endif %} +| [Administrar la política de bifurcación](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limitar la actividad en repositorios públicos en una organización](/articles/limiting-interactions-in-your-organization) | **X** | | | +| Extraer (leer), subir (escribir) y clonar (copiar) *todos los repositorios* en la organización | **X** | | | +| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | | +| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Administrar el nombre de la rama predeterminada (consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Habilitar la sincronización de equipos (consulta la sección "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obtener más detalles) | **X** | | | + +{% else %} + + +| Acción de organización | Propietarios | Miembros | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------:|:---------------------------------------------------------------------------------------------------:| +| Invitar personas para que se unan a la organización | **X** | | +| Editar y cancelar invitaciones para unirse a la organización | **X** | | +| Eliminar miembros de tu organización | **X** | | | +| Reinstalar antiguos miembros a la organización | **X** | | | +| Agregar o eliminar personas de **todos los equipos** | **X** | | +| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} +| Agregar colaboradores a **todos los repositorios** | **X** | | +| Acceder al registro de auditoría de la organización | **X** | | +| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/articles/about-your-organization-s-profile)" para obtener más detalles) | **X** | | | +| Eliminar **todos los equipos** | **X** | | +| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | +| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | +| Ver todos los miembros y equipos de la organización | **X** | **X** | +| @mencionar cualquier equipo visible | **X** | **X** | +| Poder convertirse en *mantenedor del equipo* | **X** | **X** | +| Transferir repositorios | **X** | | +| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | +| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | +| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | **X** | | +| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | +| Editar y eliminar debates del equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | **X** | +| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | | +| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización (consulta "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para encontrar más detalles) | **X** | | |{% endif %} +| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Extraer (leer), subir (escribir) y clonar (copiar) *todos los repositorios* en la organización | **X** | | +| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | +| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %} administadores + +Por defecto, únicamente los propietarios de la organización pueden administrar las configuraciones de las {% data variables.product.prodname_github_app %}s que le pertenecen a una organización. Para permitir que más usuarios administren las {% data variables.product.prodname_github_app %}s que le pertenecen a una organización, un propietario puede otorgarles permisos de administrador de {% data variables.product.prodname_github_app %}. + +Cuando designas un usuario como administrador de {% data variables.product.prodname_github_app %} en tu organización, puedes otorgarle acceso para administrar las configuraciones de algunas o todas las {% data variables.product.prodname_github_app %}s que le pertenecen a la organización. Para obtener más información, consulta: + +- "[Agregar administradores de GitHub App en tu organización](/articles/adding-github-app-managers-in-your-organization)" +- "[Eliminar administradores de GitHub App de tu organización](/articles/removing-github-app-managers-from-your-organization)" + +### Colaboradores externos + +Para mantener seguros los datos de tu organización mientras que permites el acceso a los repositorios, puedes agregar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %} + +### Further reading + +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" +- [Acerca de los equipos](/articles/about-teams)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000000..4fe1d60f49183 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Prepararse para aplicar el inicio de sesión único SAML en tu organización +intro: 'Antes de aplicar el inicio de sesión único de SAML en tu organización, deberías verificar la membresía de tu organización y configurar las configuraciones de conexión para tu proveedor de identidad.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +--- + +Cuando [aplicas el inicio de sesión único de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) en tu organización, los miembros que no se han autenticado por medio de tu proveedor de identidad (IdP) serán eliminados de la organización y recibirán un correo electrónico informándoles acerca de la eliminación. + +Antes de aplicar un SSO de SAML en tu organización, deberías: + +- [Agregar](/articles/inviting-users-to-join-your-organization) o [eliminar](/articles/removing-a-member-from-your-organization) miembros de tu organización si es necesario. +- Si no lo has hecho, conectar tu IdP a tu organización. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)." +- Asegurar que los miembros de tu organización se hayan registrado y hayan vinculado sus cuentas con tu IdP. + +{% data reusables.saml.outside-collaborators-exemption %} + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000000..80aea20e098ea --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,19 @@ +--- +title: Prepararse para requerir autenticación de dos factores en tu organización +intro: 'Antes de requerir la autenticación de dos factores (2FA), puedes notificar a los usuarios acerca del futuro cambio y verificar quien ya utiliza 2FA.' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Te recomendamos que notifiques {% if currentVersion == "free-pro-team@latest" %}a los miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} por lo menos una semana antes de que comiences a requerir 2FA para tu organización. + +Cuando solicitas que se use la autenticación de dos factores para tu organización, los miembros, los colaboradores externos y los gerentes de facturación (incluidas las cuentas bot) que no utilizan 2FA se eliminarán de tu organización y perderán acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. + +Antes de solicitar 2FA en tu organización, recomendamos que: + - [Habilites 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) en tu cuenta personal + - Le solicites a las personas en tu organización que configuren 2FA en sus cuentas + - Consultes si [los usuarios en tu organizacipon tienen habilitado el 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - Le adviertas a los usuarios que una vez que el 2FA esté habilitado, aquellos sin 2FA se eliminarán automáticamente de la organización diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000000..8a143c011a00e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -0,0 +1,40 @@ +--- +title: Permisos de tablero de proyecto para una organización +intro: 'Los propietarios de la organización y las personas con permisos de administradores de los tableros de proyecto pueden personalizar quién tiene permisos de lectura, escritura y de administrador en los tableros de proyecto de tu organización.' +redirect_from: + - /articles/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Resumen de permisos + +Hay tres niveles de permisos para las personas y para los equipos a un tablero de proyecto: + +{% data reusables.project-management.project-board-permissions %} + +Los propietarios de la organización y las personas con permisos de administrador pueden otorgarle acceso a una persona a un tablero de proyecto de una organización de manera individual, como un colaborador externo o como miembro de la organización, o a través de su membresía en un equipo o una organización. Un colaborador externo es alguien que no es miembro de la organización pero a quien le han otorgado permisos para colaborar en tu organización. + +Los propietarios de la organización y las personas con permisos de administrador a un tablero de proyecto también pueden: +- Configurar permisos predeterminados a un tablero de proyecto para todos los miembros de la organización. +- Administrar el acceso al tablero de proyecto para los miembros de la organización, los equipos y los colaboradores externos. Para obtener más información, consulta "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)", "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)", o "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." +- Administrar la visibilidad del tablero de proyecto. Para obtener más información, consulta "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." + +### Permisos en cascada para tableros de proyecto + +{% data reusables.project-management.cascading-permissions %} + +Por ejemplo, si el propietario de la organización ha otorgado a todos los miembros de la organización permisos de lectura a un tablero de proyecto y un administrador de tablero de proyecto le otorga a un miembro de la organización permisos de escritura a ese tablero como colaborador individual, esa persona tendría permisos de escritura al tablero de proyecto. + +### Visibilidad del tablero de proyecto + +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". + +### Further reading + +- "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)." +- "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)" +- "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000000..3e1242777be86 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,59 @@ +--- +title: Volver a admitir a un miembro anterior de tu organización +intro: 'Los propietarios de la organización pueden {% if currentVersion == "free-pro-team@latest" %}invitar a miembros anteriores de la organización para volverse a unir a{% else %}agregar a miembros anteriores a{% endif%} tu organización y elegir si quieren restablecer el rol, permisos de acceso, bifurcaciones y configuraciones anteriores de dicha persona.' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Los propietarios de las organizaciones pueden reinstaurar a un miembro previo de las mismas.' +--- + +### Acerca de la reinstauración de miembros + +Si [eliminas a un usuario de tu organización](/articles/removing-a-member-from-your-organization){% if currentVersion == "github-ae@latest" %} o{% else %},{% endif %}[conviertes a un miembro de tu organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion != "github-ae@latest" %}, o se elimina a un usuario de tu organización porque [requeriste que los miembros y colaboradores externos habiliten la autenticación bifactorial (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, los privilegios de acceso y configuraciones de estos usuarios se guardarán por tres meses. Puedes restablecer los privilegios del usuario si los vuelves a{% if currentVersion =="free-pro-team@latest" %}invitar{% else %} agregar{% endif %} a la organización dentro de este periodo de tiempo. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Cuando vuelvas a admitir a un miembro antiguo de la organización, puedes restaurar lo siguiente: + - El rol del usuario en la organización + - Cualquier bifurcación privada de los repositorios que son propiedad de la organización + - La membresía a los equipos de la organización + - El acceso y los permisos previos para los repositorios de la organización + - Las estrellas para los repositorios de la organización + - Las asignaciones de propuestas en la organización + - Las suscripciones a repositorios (los parámetros de notificaciones para observar, no observar o ignorar la actividad de un repositorio) + +{% if enterpriseServerVersions contains currentVersion %} +Si se eliminó de la organización a un miembro de la organización porque no utilizó la autenticación de dos factores, y tu organización aún requiere que los miembros utilicen la 2FA, el miembro antiguo debe habilitar la autenticación de dos factores antes de que puedas reinstalar su membresía. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Si tu organización tiene una suscripción de pago por usuario, debes de contar con una licencia disponible antes de que puedas volver a admitir a algún miembro anterior de la organización. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} +{% endif %} + +### Volver a admitir a un miembro anterior de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.reinstate-user-type-username %} +{% if currentVersion == "free-pro-team@latest" %} +6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Invite and reinstate** (Invitar y reinstalar) o **Invite and start fresh** (Invitar e iniciar de nuevo). ![Decide si quieres restaurar la información o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Add and reinstate** (Agregar y reinstalar) o **Add and start fresh** (Agregar e iniciar de nuevo). ![Decide si quieres restaurar los privilegios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Si eliminaste los privilegios anteriores de un miembro anterior de la organización, elige un rol para el usuario, y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Enviar invitación**. ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Si eliminaste los privilegios anteriores de un miembro anterior de la organización, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Agregar miembro**. ![Opciones de rol y equipo y botón para agregar miembros](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Further reading + +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000000..e7d82163cd691 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,72 @@ +--- +title: Reinstalar el acceso de un colaborador externo antiguo a tu organización +intro: "Puedes reinstaurar los permisos de acceso de un colaborador externo previo para los repositorios, bifurcaciones y configuraciones de la organización." +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando se elimina el acceso de un colaborador externo a los repositorios privados de tu organización, los privilegios de acceso y configuraciones de éste se guardan por tres meses. Puedes restablecer los privilegios del usuario si los vuelves a{% if currentVersion =="free-pro-team@latest" %}invitar{% else %} agregar{% endif %} a la organización dentro de este periodo de tiempo. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Cuando reinstalas un colaborador externo antiguo, puedes restaurar lo siguiente: + - El acceso antiguo del usuario a los repositorios de la organización + - Cualquier bifurcación privada de los repositorios que son propiedad de la organización + - La membresía a los equipos de la organización + - El acceso y los permisos previos para los repositorios de la organización + - Las estrellas para los repositorios de la organización + - Las asignaciones de propuestas en la organización + - Las suscripciones a repositorios (los parámetros de notificaciones para observar, no observar o ignorar la actividad de un repositorio) + +{% tip %} + +**Tips**: + - Solo los propietarios de la organización pueden reinstalar el acceso de colaboradores externos a una organización. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". + - El flujo para restablecer a un miembro en {% data variables.product.product_location %} puede utilizar el término "miembro" para describir el restablecimiento de un colaborador externo, pero si restableces a esta persona y mantienes sus privilegios anteriores, únicamente verán sus [permisos de colaborador externo](/articles/permission-levels-for-an-organization/#outside-collaborators) previos.{% if currentVersion == "free-pro-team@latest" %} + - Si tu organización tiene una suscripción de pago por usuario, debe de existir una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro para que se una a la organización o antes de reinstaurar a algún miembro previo de la misma. Para obtener más información, consulta "[Acerca del precio por usuario](/articles/about-per-user-pricing)."{% endif %} + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.reinstate-user-type-username %} +{% if currentVersion == "free-pro-team@latest" %} +6. Decide si quieres restaurar los privilegios antiguos del colaborador externo en la organización haciendo clic en **Invite and reinstate** (Invitar y reinstalar) o decide eliminar los privilegios antiguos y establecer nuevos permisos de acceso haciendo clic en **Invite and start fresh** (Invitar e iniciar de nuevo). + + {% warning %} + + **Advertencia:** Si quieres subir de categoría el colaborador externo a miembro de tu organización, elige **Invite and start fresh** (Invitar e iniciar de nuevo) y elige un rol nuevo para esta persona. Sin embargo, ten en cuenta que las bifurcaciones privadas de los repositorios de tu organización de esa persona se perderán si decides iniciar de nuevo. En cambio, para hacer que el colaborador externo antiguo sea miembro de tu organización *y* conserve sus bifurcaciones privadas, elige **Invite and reinstate** (Invitar y reinstalar). Una vez que esta persona acepte la invitación, puedes convertirla en miembro de la organización [invitándola a que se una a la organización como miembro](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Decide si quieres restaurar los parámetros o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Decide si quieres restaurar los privilegios antiguos del colaborador externo en la organización haciendo clic en **Add and reinstate** (Agregar y reinstalar) o decide eliminar los privilegios antiguos y establecer nuevos permisos de acceso haciendo clic en **Add and start fresh** (Agregar e iniciar de nuevo). + + {% warning %} + + **Advertencia:** Si quieres subir de categoría el colaborador externo a miembro de tu organización, elige **Add and start fresh** (Agregar e iniciar de nuevo) y elige un rol nuevo para esta persona. Sin embargo, ten en cuenta que las bifurcaciones privadas de los repositorios de tu organización de esa persona se perderán si decides iniciar de nuevo. En cambio, para hacer que el colaborador externo antiguo sea miembro de tu organización *y* conserve sus bifurcaciones privadas, elige **Add and reinstate** (Agregar y reinstalar). Luego puedes convertirla en miembro de la organización [agregándola a la organización como miembro](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Decide si quieres restaurar los parámetros o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Si eliminaste los privilegios anteriores de un colaborador externo antiguo, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Send invitation** (Enviar invitación). ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Si eliminaste los privilegios anteriores de un colaborador externo antiguo, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Opciones de rol y equipo y botón para agregar miembros](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. La persona invitada recibirá un correo electrónico invitándola a la organización. Tendrá que aceptar la invitación antes de convertirse en colaborador externo de la organización. {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Leer más + +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000000..fee237ca591af --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Eliminar un gerente de facturación de tu organización +intro: 'Si una persona con el rol de *gerente de facturación* no necesita seguir viendo o modificando la información de facturación de tu organización, puedes eliminar su acceso a la organización.' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +--- + +{% warning %} + +**Nota:** {% data reusables.dotcom_billing.org-billing-perms %} + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. En la lista de Gerentes de facturación, al lado del nombre de la persona que quieres eliminar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Eliminar gerente de facturación](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000000..fa39ab39a77db --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md @@ -0,0 +1,56 @@ +--- +title: Eliminar a un miembro de tu organización +intro: 'Si miembros de tu organización ya no necesitan acceso a ningún repositorio que le pertenece a la organización, puedes eliminarlos de la organización.' +redirect_from: + - /articles/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Solo los propietarios de la organización pueden eliminar usuarios de una organización. + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Advertencia:** Cuando eliminas a algún miembro de una organización: +- La cuenta de licencias pagadas no baja de categoría automáticamente. Para pagar por menos licencias después de eliminar usuarios de tu organización, sigue los pasos de la sección "[Bajar el cupo límite de plazas pagadas en tu organización](/articles/downgrading-your-organization-s-paid-seats)". +- Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. +- Cualquier invitación a una organización que envíe un miembro eliminado, y que no se haya aceptado, se cancelará y no se podrá acceder a ella. + +{% endwarning %} + +{% else %} + +{% warning %} + +**Advertencia:** Cuando eliminas a algún miembro de una organización: + - Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. + - Cualquier invitación a una organización que envíe el usuario eliminado y que no se haya aceptado se cancelará y no se podrá acceder a ella. + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Para ayudar con la transición de la persona que estás eliminando de tu organización y ayudar a asegurar que elimine la información confidencial o propiedad intelectual, recomendamos compartir una lista de verificación para salir de tu organización. Para ver un ejemplo, consulta "[Buenas prácticas para salir de tu empresa](/articles/best-practices-for-leaving-your-company/)". + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### Revocar la membresía del usuario + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecciona el miembro o los miembros que quieres eliminar de la organización. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Remove from organization** (Eliminar de la organización). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png) +6. Revisa el miembro o los miembros que se eliminarán de la organización, luego haz clic en **Remove members** (Eliminar miembros). ![Lista de miembros que se eliminarán y botón Remove members (Eliminar miembros)](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### Further reading + +- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000000..79c4f35c7d524 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,19 @@ +--- +title: Eliminar un colaborador externo de un tablero de proyecto de la organización +intro: 'Como propietario de la organización o administrador del tablero de proyecto, puedes eliminar el acceso de un colaborador externo a un tablero de proyecto.' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.organization-wide-project %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.remove-collaborator %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000000..eecac1cfb0671 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Eliminar un colaborador externo de un repositorio de la organización +intro: Los propietarios y los administradores del repositorio pueden eliminar el acceso a un repositorio de un colaborador externo. +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Advertencia:** +- Cuando se elimina un colaborador externo de un repositorio privado, el conteo de licencias pagadas no baja de categoría automáticamente. Para pagar por menos licencias después de eliminar usuarios de tu organización, sigue los pasos de la sección "[Bajar el cupo límite de plazas pagadas en tu organización](/articles/downgrading-your-organization-s-paid-seats)". + +- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. + +{% endwarning %} + +{% endif %} + +Aunque se borren las bifurcaciones de los repositorios privados cuando se elimina un colaborador, la persona seguirá teniendo todos los clones locales de tu repositorio. + +### Eliminar colaboradores externos de todos los repositorios de una organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Selecciona el colaborador externo o los colaboradores externos que quieres eliminar de la organización. ![Lista de colaboradores externos con dos colaboradores externos seleccionados](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. Arriba de la lista de colaboradores externos, usa el menú desplegable y haz clic en **Remove from all repositories** (Eliminar de todos los repositorios). ![Menú desplegable con la opción para eliminar colaboradores externos ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Revisa el colaborador externo o los colaboradores externos que se eliminarán de la organización, luego haz clic en **Remove outside collaborators** (Eliminar colaboradores externos). ![Lista de colaboradores externos que se eliminarán y botón Remove outside collaborators (Eliminar colaboradores externos)](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### Eliminar un colaborador externo de un repositorio particular de una organización + +Si solo quieres eliminar un colaborador externo de determinados repositorios de tu organización, puedes eliminar el acceso de esa persona a un repositorio específico por vez. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. A la derecha del nombre de usuario de la persona que quieres eliminar, utiliza el menú desplegable {% octicon "gear" aria-label="The Settings gear" %} y haz clic en **Manage** (Administrar). ![Botón Manage access (Administrar acceso)](/assets/images/help/organizations/member-manage-access.png) +6. A la derecha del repositorio del que quieres eliminar al colaborador externo, haz clic en **Manage access** (Administrar acceso). ![Selecciona el botón Manage access (Administrar acceso) al lado del repositorio al que tiene acceso el colaborador externo](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. Para eliminar por completo el acceso del colaborador externo al repositorio, en la esquina superior derecha, haz clic en **Remove access to this repository** (Eliminar acceso a este repositorio). ![Botón Remove access to this repository (Eliminar acceso a este repositorio)](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. Para confirmar, haz clic en **Remove access** (Eliminar acceso). ![Confirmar el colaborador externo que se eliminará del repositorio](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### Further reading + +- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000000..fc6865b487040 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,38 @@ +--- +title: Eliminar administradores de App GitHub de tu organización +intro: 'Los propietarios de la organización pueden revocar los permisos de administrador {% data variables.product.prodname_github_app %} que se le hayan concedido a un miembro de la organización.' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para más información sobre los permisos del administrador de {% data variables.product.prodname_github_app %}, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization#github-app-managers)". + +### Eliminar los {% data variables.product.prodname_github_app %} permisos de un administrador para toda la organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. En "Management" (Administración), encuentra el nombre de usuario de la persona para la que quieres eliminar {% data variables.product.prodname_github_app %} los permisos de administrador, luego haz clic en **Revoke** (Revocar). ![Revocar {% data variables.product.prodname_github_app %} permisos de administrador](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### Eliminar los {% data variables.product.prodname_github_app %} permisos de administrador para una persona {% data variables.product.prodname_github_app %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Debajo de " +{% data variables.product.prodname_github_app %}s", da clic en el avatar de la app para la cual te gustaría eliminar a un administrador de ésta. +![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. En "App managers" (Administradores de app), encuentra el nombre de usuario de la persona para la que quieres eliminar {% data variables.product.prodname_github_app %} los permisos de administrador, luego haz clic en **Revoke** (Revocar). ![Revocar {% data variables.product.prodname_github_app %} permisos de administrador](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000000..0be198c0daca1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,19 @@ +--- +title: Eliminar de un equipo a miembros de la organización +intro: 'Las personas con permisos de *propietario* o *mantenedor del equipo* pueden eliminar de un equipo a miembros del equipo. Puede que se deba hacer esto si una persona no necesita más el acceso a un repositorio que otorga el equipo, o si una persona no se dedica más a los proyectos de un equipo.' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Selecciona la persona o las personas que quieres eliminar. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) +5. Arriba de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Remove from team** (Eliminar del equipo). ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-a-team.md new file mode 100644 index 0000000000000..9bce57deacf18 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-a-team.md @@ -0,0 +1,17 @@ +--- +title: Renombrar un equipo +intro: Los mantenedores del equipo y los propietarios de la organización pueden editar el nombre y la descripción de un equipo. +redirect_from: + - /articles/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Escribe un nombre o descripción nuevos para el equipo. ![Campos para el nombre y la descripción del equipo](/assets/images/help/teams/team-name-description.png) +6. Da clic en **Actualizar**. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md new file mode 100644 index 0000000000000..a25c410fcf6eb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md @@ -0,0 +1,46 @@ +--- +title: Renombrar una organización +intro: 'Si tu proyecto o empresa cambió de nombre, puedes actualizar el nombre de tu organización para que coincida.' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Solo los propietarios de la organización pueden renombrar una organización. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### ¿Qué sucede cuando cambio el nombre de mi organización? + +Después de cambiar el nombre de tu organización, el nombre antiguo de tu organización se pone a disposición para quien lo quiera utilizar. Cuando cambias el nombre de tu organización, la mayoría de las referencias a los repositorios bajo el nombre antiguo de tu organización se cambiarán automáticamente al nombre nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. + +#### Cambios que ocurren automáticamente + +- {% data variables.product.prodname_dotcom %} redirige automáticamente las referencias a tus repositorios. Los enlaces web a los **repositorios** existentes de tu organización seguirán funcionando. Puede tomar algunos minutos para que se complete luego de que inicies el cambio. +- Puedes continuar subiendo tus repositorios locales a la URL de seguimiento del remoto antiguo sin actualizarla. Sin embargo, recomendamos que actualices todas las URL de repositorios remotos existentes después de cambiar el nombre de tu organización. Como el nombre antiguo de tu organización queda disponible para que lo utilice cualquier otra persona después de que lo cambies, el propietario de la organización nuevo puede crear repositorios que remplacen las entradas redirigidas a tu repositorio. Para obtener más información, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url). +- Las confirmaciones de Git anteriores también se atribuirán según corresponda a los usuarios de tu organización. + +#### Cambios que no son automáticos + +Después de cambiar el nombre de tu organización: +- Los enlaces a la página de perfil de tu organización anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, generarán un error 404. Te recomendamos que actualices los enlaces a tu organización desde otros sitios{% if currentVersion == "free-pro-team@latest" %}, tales como tus perfiles de LinkedIn o Twitter{% endif %}. +- Las solicitudes API que utilizan el nombre de la organización antiguo generarán un error 404. Recomendamos que actualices el nombre de la organización antiguo en tus solicitudes API. +- No existen redireccionamientos automáticos [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) para los equipos que utilizan el nombre de la organización antiguo. + +### Cambiar el nombre de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Cerca de la parte de abajo de la página de parámetros, en "Rename organization" (Renombrar organización), haz clic en **Rename Organization** (Renombrar organización). ![Botón Rename organization (Renombrar organización)](/assets/images/help/settings/settings-rename-organization.png) + +### Further reading + +* "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)" +* "[¿Por qué mis confirmaciones están vinculadas al usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000000..94595eee7bce0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -0,0 +1,139 @@ +--- +title: Niveles de permiso del repositorio para una organización +intro: 'Puedes personalizar el acceso a cada repositorio de tu organización con niveles de permiso granulares, dándoles a las personas acceso a las funciones y tareas que necesitan.' +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos de administrador pueden administrar el acceso individual o del equipo al repositorio que le pertenece a la organización. + +### Niveles de permiso para los repositorios que le pertenecen a una organización + +Puedes otorgar diferentes niveles de acceso a los miembros de la organización, los colaboradores externos y los equipos de personas para los repositorios que le pertenecen a una organización. Cada nivel de permiso aumenta de manera progresiva el acceso al contenido y los parámetros de un repositorio. Elige el nivel que mejor se adecue a cada rol de persona o equipo de tu proyecto, evitando otorgar a las personas más acceso al proyecto del que necesitan. + +Del menor acceso al mayor acceso, los niveles de permiso para el repositorio de una organización son los siguientes: +- **Lectura**: Recomendado para los contribuyentes sin código que quieren ver tu proyecto u opinar sobre él +- **Prueba**: Recomendado para los contribuyentes que necesiten administrar propuestas y solicitudes de extracción de manera proactiva sin acceso de escritura +- **Escritura**: Recomendado para los contribuyentes que suben contenido a tu proyecto de manera activa +- **Mantenimiento (beta)**: Recomendado para los gerentes del proyecto que necesiten administrar el repositorio sin acceder a las acciones confidenciales o destructivas +- **Administrador**: Recomendado para las personas que necesitan acceso total al proyecto, incluidas las acciones conflictivas y destructivas, como gestionar la seguridad o eliminar un repositorio + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +Para obtener más información acerca de otorgar acceso a los repositorios a las personas y los equipos, consulta "[Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organizations-repositories)". + +Los dueños de las organizaciones pueden configurar permisos base que apliquen a todos los miembros de la misma cuando accedan a cualquiera de los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Configurar los permisos base para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization#setting-base-permissions)". + +Los propietarios de la organización también pueden decidir limitar más el acceso a determinados parámetros y acciones de la organización. Para obtener más información sobre las opciones de parámetros específicos, consulta "[Administrar los parámetros de la organización](/articles/managing-organization-settings)". + +Además de administrar los parámetros al nivel de la organización, los propietarios de la organización tienen permisos de administradores para cada repositorio que le pertenece a la organización. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". + +{% warning %} + +**Advertencia:** Cuando una persona agrega una llave de implementación a un repositorio, cualquier usuario que tenga la llave privada puede leer o escribir en el repositorio (según los parámetros de la llave), incluso si luego es eliminada de la organización. + +{% endwarning %} + +### Acceso al repositorio para cada nivel de permiso + +| Acción del repositorio | Read | Triage | Escritura | Mantenimiento | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:---------:|:-------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Extraer desde los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | +| Bifurcar los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | +| Editar y eliminar sus propios comentarios | **X** | **X** | **X** | **X** | **X** | +| Abrir propuestas | **X** | **X** | **X** | **X** | **X** | +| Cerrar propuestas que abrieron ellos mismos | **X** | **X** | **X** | **X** | **X** | +| Reabrir propuestas que cerraron ellos mismos | **X** | **X** | **X** | **X** | **X** | +| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | +| Enviar solicitudes de extracción desde bifurcaciones de repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | +| Enviar revisiones o solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | +| Ver lanzamientos publicados | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Ver las [Ejecuciones de flujo de trabajo de 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" %} +| [Informar contenido abusivo o de spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Crear, editar, borrar etiquetas | | | **X** | **X** | **X** | +| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar e inhabilitar la fusión automática en una solicitud de cambios](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| Aplicar hitos | | **X** | **X** | **X** | **X** | +| Marcar [duplicar propuestas y solicitudes de extracción](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Solicitar [revisiones de solicitudes de extracción](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | | **X** | **X** | **X** | +| Editar y eliminar comentarios o confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | | **X** | **X** | **X** | +| [Ocultar los comentarios de cualquier persona](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversaciones](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Transferir propuestas (consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para obtener detalles) | | | **X** | **X** | **X** | +| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Marcar un borrador de solicitud de extracción como listo para revisión](/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" %} +| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| Enviar revisiones que afecten la capacidad de fusión de una solicitud de extracción | | | **X** | **X** | **X** | +| [Aplicar cambios sugeridos](/articles/incorporating-feedback-in-your-pull-request) a las solicitudes de extracción | | | **X** | **X** | **X** | +| Crear [comprobaciones de estado](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Crear, editar, ejecutar, volver a ejecutar y cancelar [Flujos de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Crear y editar lanzamientos | | | **X** | **X** | **X** | +| Ver lanzamientos en borrador | | | **X** | **X** | **X** | +| Editar la descripción de un repositorio | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Ver e instalar paquetes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publicar paquetes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Borrar paquetes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Habilitar wikis y restringir editores de wikis | | | | **X** | **X** | +| Habilitar tableros de proyecto | | | | **X** | **X** | +| Configurar las [fusiones de la solicitud de extracción](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configurar [una fuente de publicaciones para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Subir a ramas protegidas](/articles/about-protected-branches) | | | | **X** | **X** | +| [Crear y editar las tarjetas sociales del repositorio](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Limitar las [interacciones en un repositorio](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| Eliminar una propuesta (consulta "[Eliminar una propuesta](/articles/deleting-an-issue)") | | | | | **X** | +| Fusionar solicitudes de extracción en ramas protegidas, incluso si no existen revisiones en aprobación | | | | | **X** | +| [Definir propietarios del código para un repositorio](/articles/about-code-owners) | | | | | **X** | +| Añadir un repositorio a un equipo (consulta la sección "[Administrar el acceso de un equipo a un repositorio de la organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obtener más detalles) | | | | | **X** | +| [Gestionar el acceso de un colaborador externo a un repositorio](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Cambiar la visibilidad de un repositorio](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** | +| Cambiar los parámetros de un repositorio | | | | | **X** | +| Administrar el acceso de un equipo o colaborador al repositorio | | | | | **X** | +| Editar la rama predeterminada del repositorio | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| Administrar webhooks y desplegar llaves | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar el gráfico de dependencias](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) de un repositorio privado | | | | | **X** | +| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **X** | +| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para las dependencias vulnerables | | | | | **X** | +| [Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | +| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [Ver las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [Listar, descartar y borrar las alertas del {% 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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} +| [Administrar la política de bifurcación de un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transferir repositorios a la organización](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Eliminar o transferir repositorios fuera de la organización](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archivar repositorios](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Mostrar el botón de un patrocinador (consulta "[Mostrar el botón de un patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Crear referencias de enlace automático a recursos externos, como JIRA o Zendesk (consulta "[Configurar enlaces automáticos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) en un repositorio | | | | **X** | **X** | +| [Crear y editar categorías](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Mover un debate a una categoría diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transferir un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) a un repositorio nuevo | | | **X** | **X** | **X** | +| [Administrar debates fijados](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Converitr propuestas en debates por lote](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Convertir las propuestas en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Crear debates nuevos y comentar sobre los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} + +### Further reading + +- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" +- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000000..547b93fae954d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,32 @@ +--- +title: Solicitar agregar un equipo hijo +intro: 'Si tienes permisos de mantenedor en un equipo, puedes solicitar anidar un equipo existente en tu equipo en la jerarquía de tu organización.' +redirect_from: + - /articles/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando solicitas agregar un equipo como hijo, se envía una solicitud a los mantenedores del equipo hijo. Una vez que un mantenedor del equipo hijo aprueba tu solicitud, el equipo hijo se anida en el equipo padre de la jerarquía de tu organización. + +Si eres propietario de una organización o tienes permisos de mantenedor del equipo tanto en el equipo hijo como en el equipo padre, puedes agregar el equipo hijo sin solicitar aprobación o modificar el padre del equipo hijo desde la página de configuraciones del equipo hijo. Para obtener más información, consulta "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. En la lista de equipos, haz clic en el nombre del equipo al que quieres agregar el equipo hijo. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) +5. En la parte superior de la página del equipo, haz clic en {% octicon "people" aria-label="The people icon" %} **Teams** (Equipos). ![Pestaña de equipos en la página de un equipo](/assets/images/help/teams/team-teams-tab.png) +6. Haz clic en **Add a team** (Agregar un equipo). ![Botón Add a team (Agregar un equipo) en una página de equipo](/assets/images/help/teams/add-a-team.png) +7. Escribe el nombre del equipo que quieres agregar como equipo hijo y selecciónalo desde la lista desplegable. ![Recuadro para escribir y menú desplegable para seleccionar el nombre del equipo hijo](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar al equipo hijo. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) + +### Further reading + +- [Acerca de los equipos](/articles/about-teams)" +- "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Solicitar agregar o modificar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000000..2cb0d48a7e4ea --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,32 @@ +--- +title: Solicitar agregar o modificar un equipo padre +intro: 'Si tienes permisos de mantenedor en un equipo, puedes solicitar anidar tu equipo bajo un equipo padre en la jerarquía de tu organización.' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando solicitas agregar o modificar el padre de tu equipo, se envía una solicitud a los mantenedores del equipo padre. Cuando un mantenedor del nuevo equipo padre aprueba tu solicitud, tu equipo se anida como equipo hijo en bajo el equipo padre en la jerarquía de tu organización. + +Si eres propietario de la organización o tienes permisos de mantenedor del equipo en el equipo hijo y el equipo padre, puedes agregar el equipo padre sin solicitar aprobación ni modificar el padre de tu equipo desde la página de parámetros del equipo. Para obtener más información, consulta "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. En la lista de equipos, haz clic en el nombre del equipo que quieres anidar bajo un padre. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. En "Parent team" (Equipo padre), utiliza el menú desplegable "Select parent team" (Seleccionar equipo padre) y haz clic en el nombre del nuevo equipo padre. ![Menú desplegable que enumera los equipos de la organización](/assets/images/help/teams/choose-parent-team.png) +7. Haz clic en **Guardar cambios**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar o modificar el padre de tu equipo. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) + +### Further reading + +- [Acerca de los equipos](/articles/about-teams)" +- "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000000..1dcdefd7e7de6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Solicitar autenticación de dos factores en tu organización +intro: 'Los propietarios de la organización pueden requerir que los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} habiliten la autenticación bifactorial para sus cuentas personales, lo cual hará más difícil que los actores malintencionados accedan a los repositorios y configuración de una organización.' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de la autenticación bifactorial para las organizaciones + +{% data reusables.two_fa.about-2fa %} Puedes requerir que todos los {% if currentVersion == "free-pro-team@latest" %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} en tu organización habiliten la autenticación bifactorial en {% data variables.product.product_name %}. Para obtener más información acerca de la autenticación bifactorial, consulta la sección "[Asegurar tu cuenta con la autenticación bifactorial (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". + +{% if currentVersion == "free-pro-team@latest" %} + +También puedes requerir autenticación bifactorial para las organizaciones en una empresa. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)". + +{% endif %} + +{% warning %} + +**Advertencias:** + +- Cuando requieres que se utilice la autenticación bifactorial en tu organización, {% if currentVersion == "free-pro-team@latest" %}los miembros, colaboradores externos y gerentes de facturación{% else %}los miembros y colaboradores externos{% endif %} (incluyendo las cuentas bot) que no utilicen 2FA se eliminarán de la misma y perderán el acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes [reinstalar sus privilegios y parámetros de acceso](/articles/reinstating-a-former-member-of-your-organization) si habilitan la autenticación de dos factores para su cuenta personal en el transcurso de los tres meses posteriores a la eliminación desde tu organización. +- Si un propietario, miembro,{% if currentVersion == "free-pro-team@latest" %} gerente de facturación,{% endif %} o colaborador externo de la organización inhabilita la 2FA para su cuenta personal después de que hayas habilitado que ésta se requiera, automáticamente se eliminarán de dicha organización. +- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización. + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### Prerrequisitos + +Antes de que requieras que los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} utilicen la autenticación bifactorial, debes habilitarla para tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta "[Proteger tu cuenta con la autenticación de dos factores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". + +Antes de que requieras que se utilice la autenticación bifactorial, te recomendamos notificar a los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} y pedirles que configuren la 2FA en sus cuentas. Puedes ver si los miembros y colaboradores externos ya utilizan la 2FA. Para obtener más información, consulta "[Ver si los usuarios en tu organización tienen la 2FA habilitada](/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled)". + +### Solicitar autenticación de dos factores en tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.require_two_factor_authentication %} +{% data reusables.organizations.removed_outside_collaborators %} +{% if currentVersion == "free-pro-team@latest" %} +8. Si algún miembro o colaborador externo se elimina de tu organización, te recomendamos enviarle una invitación para reinstalar sus privilegios antiguos y el acceso a tu organización. Deben habilitar la autenticación de dos factores para poder aceptar la invitación. +{% endif %} + +### Ver las personas que se eliminaron de tu organización + +Para ver las personas que se eliminaron automáticamente de tu organización por no cumplir cuando les requeriste la autenticación de dos factores, puedes [buscar el registro de auditoría de tu organización](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log) para las personas eliminadas de tu organización. El evento de registro de auditoría mostrará si se eliminó a una persona por no cumplir con la 2FA. + +![Evento de registro de auditoría que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png) + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} +4. Ingresa tu consulta de búsqueda. Para buscar por: + - Miembros de la organización eliminados, utiliza `action:org.remove_member` en tu consulta de búsqueda + - Colaboradores externos eliminados, utiliza `action:org.remove_outside_collaborator` en tu consulta de búsqueda{% if currentVersion == "free-pro-team@latest" %} + - Gerentes de facturación eliminados, utiliza `action:org.remove_billing_manager`en tu consulta de búsqueda{% endif %} + + También puedes ver las personas que se eliminaron de tu organización utilizando un [período de tiempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) en tu búsqueda. + +### Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización + +Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. + +### Further reading + +- "[Ver si los usuarios de tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Proteger tu cuenta con autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstalar un miembro antiguo de tu organización](/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstalar el acceso a tu organización de un colaborador externo antiguo](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md new file mode 100644 index 0000000000000..9d5ff5279afa1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md @@ -0,0 +1,11 @@ +--- +title: Restringir el acceso a los datos de tu organización +intro: '{% data variables.product.prodname_oauth_app %} las restricciones de acceso le permiten a los propietarios de la organización que restrinjan el acceso de una app no confiable a los datos de la organización. Luego los miembros de la organización pueden utilizar {% data variables.product.prodname_oauth_app %}s para sus cuentas de usuario personales mientras mantienen seguros los datos de la organización.' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000000..8deef7d26c22b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,27 @@ +--- +title: Restringir las notificaciones por correo electrónico para un dominio aprobado +intro: 'Para evitar que se fugue información de la organización a las cuentas personales, los propietarios de la organización pueden restringir las notificaciones por correo electrónico sobre la actividad de una organización para un dominio verificado.' +product: '{% data reusables.gated-features.restrict-email-domain %}' +redirect_from: + - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/ + - /articles/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +--- + +### Acerca de las restricciones de correo electrónico + +Cuando se habilita la restricción de notificaciones por correo electrónico en una organización, los miembros solo pueden utilizar una dirección de correo electrónico que se haya asociado con los dominios verificados de dicha organización para recibir notificaciones de correo electrónico sobre la actividad de ésta. Para obtener más información, consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)". + +Los colabores externos no están sujetos a las restricciones en las notificaciones por correo electrónico para los dominios verificados. Para obtener más información sobre los colaboradores externos, consulta la sección "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". + +Si tu organización le pertenece a una cuenta empresarial, sus miembros podrán recibir notificaciones de cualquier dominio verificado para la cuenta empresarial adicionalmente a cualquier dominio verificado de la organización. Para obtener más información, consulta la sección "[Verificar el dominio de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)". + +### Restringir las notificaciones por correo electrónico para un dominio aprobado + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +{% data reusables.organizations.restrict-email-notifications %} +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000000..b95aa1a939fee --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Restringir la creación de repositorios en tu organización +intro: 'Para proteger los datos de tu organización, puedes configurar permisos para crear repositorios en tu organización.' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes elegir si los miembros pueden crear repositorios en tu organización o no. Si permites que los miembros creen repositorios, puedes elegir qué tipos de repositorios pueden crear. {% if currentVersion == "free-pro-team@latest" %} Para permitir que los miembros creen únicamente repositorios privados, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}.{% endif %} Para obtener más información, consulta la sección "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +Los propietarios de la organización siempre pueden crear cualquier tipo de repositorio. + +{% if currentVersion == "free-pro-team@latest" %}Los propietarios de las empresas{% else %}Los administradores de sitio{% endif %} pueden restringir las opciones que tienes disponibles para la política de creación de repositorios de tu empresa. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Requerir políticas de administración de repositorios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account)".{% else %}"[restringir la creación de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% endif %} + +{% warning %} + +**Advertencia**: Este ajuste solo restringe las opciones de visibilidad disponibles cuando los repositorios se crean y no restringe la capacidad de cambiar la visibilidad del repositorio posteriormente. Para obtener más información acerca de cómo restringir los cambios a las visibilidades existentes de los repositorios, consulta la sección "[Restringir la visibilidad de los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)". + +{% endwarning %} + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Debajo de "Creación de repositorios", selecciona una o más opciones. ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000000..ea8c106e5938f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Restringir cambios en la visibilidad de los repositorios en tu organización +intro: 'Para proteger los datos de tu organización, puedes configurar permisos para cambiar la visibilidad de los repositorios en tu organización.' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes restringir la habilidad de cambiar la visibilidad de un repositorio para solo los propietarios de la organización o permitir que los miembros con privilegios administrativos en éste también cambien la visibilidad. + +{% warning %} + +**Advertencia**: En caso de habilitarse, este ajuste permite a las personas con permisos administrativos cambiar un repositorio existente a cualquier visibilidad, aún si no permites que se cree este tipo de repositorio. Para obtener más información acerca de cómo restringir la visibilidad de los repositorios durante su creación, consulta la sección "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". + +{% endwarning %} + + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. En "Repository visibility change" (Cambio en la visibilidad de los repositorios), anula la selección de **Allow members to change repository visibilities for this organization** (Permitir que los miembros cambien las visibilidades de los repositorios para esta organización). ![Casilla para permitir que los miembros cambien la visibilidad de los repositorios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. Haz clic en **Save ** (guardar). + +### Further reading + +- "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000000..a586ebf70c6c0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,598 @@ +--- +title: Revisar el registro de auditoría para tu organización +intro: 'El registro de auditoría les permite a los administradores de la organización revisar rápidamente las acciones que realizaron los miembros de la organización. Incluye detalles como quién realizó la acción, de qué acción se trata y cuándo se realizó.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acceder al registro de auditoría + +La bitácora de auditoría lista los eventos que activan las actividades, los cuales afectan tu organización, dentro de los últimos 90 días. Solo los propietarios pueden acceder al registro de auditoría de una organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} + +### Buscar el registro de auditoría + +{% data reusables.audit_log.audit-log-search %} + +#### Búsqueda basada en la acción realizada + +Para buscar eventos específicos, utiliza el calificador `action` en tu consulta. Las acciones detalladas en el registro de auditoría se agrupan dentro de las siguientes categorías: + +| Nombre de la categoría | Descripción | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`account`](#account-category-actions) | Contiene todas las actividades relacionadas con tu cuenta de organización. | +| [`advisory_credit`](#advisory_credit-category-actions) | Contiene todas las actividades relacionadas con darle crédito a un contribuyente por una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| [`billing`](#billing-category-actions) | Contiene todas las actividades relacionadas con la facturación de tu organización. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios nuevos que se crean en la organización. | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% 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) | Contiene las actividades de configuración a nivel de organización para las {% data variables.product.prodname_dependabot_security_updates %} para los repositorios nuevos que se crean en ella. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contiene las actividades de configuración a nivel de organización para las gráficas de dependencia de los repositorios. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para los repositorios nuevos que se crean en ella.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contiene todas las actividades relacionadas con los debates publicados en una página de equipo. | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contiene todas las actividades relacionadas con las respuestas a los debates publicados en una página de equipo. | +| [`hook`](#hook-category-actions) | Contiene todas las actividades relacionadas con los webhooks. | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contiene todas las actividades relacionadas con las solicitudes de los miembros de la organización para que los propietarios aprueben las integraciones para el uso en la organización. | +| [`issue`](#issue-category-actions) | Contiene las actividades relacionadas con borrar una propuesta. |{% if currentVersion == "free-pro-team@latest" %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}. | +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas a listar apps en {% 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) | Contiene todas las actividades relacionadas con inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. Para obtener más información, consulta la sección "[Restringir la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". |{% endif %} +| [`org`](#org-category-actions) | Contiene las actividades relacionadas con la membrecía de la organización.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contiene todas las actividades relacionadas con autorizar credenciales para su uso con el inicio de sesión único de SAML.{% 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) | Contiene todas las actividades relacionadas con las etiquetas predeterminadas para los repositorios de tu organización.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contiene todas las actividades relacionadas con las Apps de OAuth. |{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con la manera en que tu organización le paga a GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contiene todas las actividades relacionadas con la foto de perfil de tu organización. | +| [`project`](#project-category-actions) | Contiene todas las actividades relacionadas con los tableros de proyecto. | +| [`rama_protegida`](#protected_branch-category-actions) | Contiene todas las actividades relacionadas con las ramas protegidas. | +| [`repo`](#repo-category-actions) | Contiene las actividades relacionadas con los repositorios que le pertenecen a tu organización.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contiene actividades a nivel de repositorio relacionadas con las asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contiene todas las actividades relacionadas con [habilitar o inhabilitar el uso de datos para un repositorio privado](/articles/about-github-s-use-of-your-data){% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contiene las actividades a nivel de repositorio para habilitar o inhabilitar la gráfica de dependencias para un | +| repositorio {% if currentVersion == "free-pro-team@latest" %}privado{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/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) | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contiene las actividades de configuración a nivel de repositorio para las alertas del {% data variables.product.prodname_dependabot %}. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contiene las actividades de configuración a nivel de organización para el escaneo de secretos en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para el escane de secretos para los repositorios nuevos que se crean en ella. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contiene todas los eventos relacionados con los botones del patrocinador (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} +| [`team`](#team-category-actions) | Contiene todas las actividades relacionadas con los equipos en tu organización. | +| [`team_discussions`](#team_discussions-category-actions) | Contiene las actividades relacionadas con administrar los debates de equipos para una organización. | + +Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: + + * `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo. + * `-action:hook` excluye todos los eventos en la categoría de webhook. + +Cada categoría tiene un conjunto de acciones asociadas que puedes filtrar. Por ejemplo: + + * `action:team.create` encuentra todos los eventos donde se creó un equipo. + * `-action:hook.events_changed` excluye todos los eventos en que se modificaron los eventos sobre un webhook. + +#### Búsqueda basada en el momento de la acción + +Utiliza el calificador `created` para filtrar los eventos en la bitácora de auditoría con base en su fecha de ocurrencia. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +Por ejemplo: + + * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014. + * `created:>=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o después. + * `created:<=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o antes. + * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014. + +El registro de auditoría contiene datos de los últimos 90 días, pero puedes utilizar el calificador `created` para buscar eventos anteriores a ese momento. + +#### Búsqueda basada en la ubicación + +Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora de auditoría con base en el país en donde se originaron. Puedes utilizar un código corto de dos letras del país o el nombre completo. Ten presente que los países con espacios en sus nombres se deben poner entre comillas. Por ejemplo: + + * `country:de` encuentra todos los eventos ocurridos en Alemania. + * `country:Mexico` encuentra todos los eventos ocurridos en México. + * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos. + +{% if currentVersion == "free-pro-team@latest" %} +### Exportar el registro de auditoría + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Utilizar la API de bitácoras de auditoría + +Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{% if currentVersion == "free-pro-team@latest" %} o la API de REST{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Utilizar la API de GraphQL + +{% endif %} + +{% note %} + +**Nota**: La API de bitácora de auditoría de GraphQL está disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +Para garantizar una IP segura y mantener el cumplimiento para tu organización, puedes utilizar la API de bitácora de auditoría de GraphQL para mantener las copias de tu bitácora de auditoría y monitorear: +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +Ten en cuenta que no puedes recuperar los eventos de Git utilizando la API de GraphQL. +{% endif %} + +La respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. + +Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros nuevos de la organización agregados a tu organización. Para obtener más información, consulta la "[Bitácora de Auditoría de la API de GraphQL](/graphql/reference/interfaces#auditentry/)". + +{% if currentVersion == "free-pro-team@latest" %} + +#### Utilizar la API de REST + +{% note %} + +**Nota**: La API de bitácora de auditoría de REST se encuentra disponible como un beta limitado únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para unirse al beta, habla con tu contacto de servicios o de ventas en {% data variables.product.company_short %}. + +{% endnote %} + +Para garantizar una IP segura y mantener el cumplimiento para tu organización, puedes utilizar la API de bitácora de Auditoría de REST para mantener las copias de tus datos de bitácora de auditoría y monitorear: +{% data reusables.audit_log.audit-log-api-info %} +* Eventos de Git, tales como clonar, recuperar y subir + +{% data reusables.audit_log.audit-log-git-events-retention %} + +Para obtener más información sobre la API de bitácora de auditoría de REST, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)" en la documentación de la API de REST. + +{% endif %} + +### Acciones de la bitácora de auditoría + +Un resumen de algunas de las acciones más comunes que se registran como eventos en la bitácora de auditoría. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Acciones de la categoría `account` + +| Acción | Descripción | +| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change (cambio del plan de facturación)` | Se activa cuando cambia el [ciclo de facturación](/articles/changing-the-duration-of-your-billing-cycle) de una organización. | +| `plan_change (cambio de plan)` | Se activa cuando cambia la [suscripción](/articles/about-billing-for-github-accounts) de una organización. | +| `pending_plan_change (cambio de plan pendiente)` | Se activa cuando un propietario de la organización o gerente de facturación [cancela o baja de categoría una suscripción paga](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | +| `pending_subscription_change (cambio de suscripción pendiente)` | Se activa cuando comienza o se vence una [{% data variables.product.prodname_marketplace %} prueba gratuita](/articles/about-billing-for-github-marketplace/). | + +#### Acciones de la categoría `advisory_credit` + +| Acción | Descripción | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `accept` | Se activa cuando alguien acepta el crédito de una asesoría de seguridad. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". | +| `create (crear)` | Se activa cuando el administrador de una asesoría de seguridad agrega a alguien a la sección de crédito. | +| `decline` | Se activa cuando alguien rechaza el crédito para una asesoría de seguridad. | +| `destroy (destruir)` | Se activa cuando el administrador de una asesoría de seguridad elimina a alguien de la sección de crédito. | + +#### acciones de la categoría `billing` + +| Acción | Descripción | +| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando tu organización [cambia la manera en que paga {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | +| `change_email (cambiar correo electrónico)` | Se activa cuando cambia la [dirección de correo electrónico de facturación](/articles/setting-your-billing-email) de tu organización. | + +#### Acciones de la categoría `dependabot_alerts` + +| Acción | Descripción | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de organización inhabilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `enable` | Se activa cuando el propietario de la organización habilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} existentes. | + +#### Acciones de la categoría `dependabot_alerts_new_repos` + +| Acción | Descripción | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando el propietario de una organización inhabilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/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 new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +#### Acciones de la categoría `dependabot_security_updates` + +| Acción | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `enable` | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes. | + +#### Acciones de la categoría `dependabot_security_updates_new_repos` + +| Acción | Descripción | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `enable` | Se activa cuando un propietario de la organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos. | + +#### Acciones de la categoría `dependency_graph` + +| Acción | Descripción | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `enable` | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios existentes. | + +#### Acciones de la categoría `dependency_graph_new_repos` + +| Acción | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `disable` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `enable` | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios nuevos. | + +{% endif %} + +#### acciones de la categoría `discussion_post` + +| Acción | Descripción | +| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| `update` | Se activa cuando se edita [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy (destruir)` | Se activa cuando se elimina [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | + +#### acciones de la categoría `discussion_post_reply` + +| Acción | Descripción | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `update` | Se activa cuando se edita [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy (destruir)` | Se activa cuando se elimina [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#deleting-a-comment). | + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `git` + +{% note %} + +**Nota:** Para acceder a los eventos de Git en la bitácora de auditoría, debes utilizar la API de la bitácora de auditoría de REST. Esta funcionalidad se encuentra disponible como un beta limitado únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para unirse al beta, habla con tu contacto de servicios o de ventas en {% data variables.product.company_short %}. + +Para obtener más información sobre la API de bitácora de auditoría de REST, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)" en la documentación de la API de REST. + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Acción | Descripción | +| ------- | -------------------------------------------------------- | +| `clone` | Se activa cuando se clona un repositorio. | +| `fetch` | Se activa cuando se recuperan cambios de un repositorio. | +| `push` | Se activa cuando se suben cambios a un repositorio. | + +{% endif %} + +#### acciones de la categoría `hook` + +| Acción | Descripción | +| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando [se agregó un enlace nuevo](/articles/creating-webhooks)a un repositorio que le pertenece a tu organización. | +| `config_changed (configuración modificada)` | Se activa cuando se modifica la configuración de un enlace existente. | +| `destroy (destruir)` | Se activa cuando se eliminó un enlace existente de un repositorio. | +| `events_changed (eventos modificados)` | Se activa cuando se modificaron los eventos en un enlace. | + +#### Acciones de la categoría`integration_installation_request` + +| Acción | Descripción | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando un miembro de la organización solicita que un propietario de la organización instale una integración para utilizar en la organización. | +| `close` | Se activa cuando un propietario de la organización aprueba o rechaza una solicitud para instalar una integración para que se utilice en una organización, o cuando la cancela el miembro de la organización que abrió la solicitud. | + +#### acciones de la categoría `issue` + +| Acción | Descripción | +| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `destroy (destruir)` | Se activa cuando un propietario de la organización o alguna persona con permisos de administrador en un repositorio elimina una propuesta de un repositorio que le pertenece a la organización. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `marketplace_agreement_signature` + +| Acción | Descripción | +| ---------------- | ----------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. | + +#### acciones de la categoría `marketplace_listing` + +| Acción | Descripción | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | +| `approve` | Se activa cuando se aprueba tu lista para ser incluida en {% data variables.product.prodname_marketplace %}. | +| `create (crear)` | Se activa cuando creas una lista para tu app en {% data variables.product.prodname_marketplace %}. | +| `delist (quitar de la lista)` | Se activa cuando se elimina tu lista de {% data variables.product.prodname_marketplace %}. | +| `redraft` | Se activa cuando tu lista se vuelve a colocar en estado de borrador. | +| `reject (rechazar)` | Se activa cuando no se acepta la inclusión de tu lista en {% 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" %} + +#### Acciones de la categoría `members_can_create_pages` + +Para obtener más información, consulta la sección "[Restringir la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". + +| Acción | Descripción | +|:--------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enable` | Se activa cuando el propietario de una organización habilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. | +| `disable` | Se activa cuando el propietario de una organización inhabilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. | + +{% endif %} + +#### acciones de la categoría `org` + +| Acción | Descripción | +| -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | +| `audit_log_export` | Se activa cuando un administrador de la organización [crea una exportación del registro de auditoría de la organización](#exporting-the-audit-log). Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta. | +| `block_user` | Se activa cuando un propietario de la organización [bloquea a un usuario para que no pueda acceder a los repositorios de la organización](/articles/blocking-a-user-from-your-organization). | +| `cancel_invitation` | Se activa cuando se revocó una invitación de la organización. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Se activa cuando un administrador de la organización [crea un secreto de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} |{% if currentVersion == "free-pro-team@latest"%} +| `disable_oauth_app_restrictions` | Se activa cuando un propietario [inhabilita {% data variables.product.prodname_oauth_app %} restricciones de acceso](/articles/disabling-oauth-app-access-restrictions-for-your-organization) para tu organización. | +| `disable_saml` | Se activa cuando un administrador de la organización inhabilita el inicio de sesión único de SAML para una organización{% endif %} +| `disable_member_team_creation_permission` | Se activa cuando un propietario de la organización limita la creación de equipos para los propietarios. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} +| `disable_two_factor_requirement` | Se activa cuando un propietario inhabilitael requisito de autenticación bifactorial para todos los miembros{% if currentVersion == "free-pro-team@latest" %}, gerentes de facturación, {% endif %} y colaboradores externos en una organización.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | Se activa cuando un propietario [habilita restricciones de acceso de {% data variables.product.prodname_oauth_app %} ](/articles/enabling-oauth-app-access-restrictions-for-your-organization) para tu organización. | +| `enable_saml` | Se activa cuando un administrador de la organización [habilita el inicio de sesión único de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para una organización.{% endif %} +| `enable_member_team_creation_permission` | Se activa cuando un propietario de la organización permite que los miembros creen equipos. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Se activa cuando un propietario requiere la autenticación bifactorial para todos los miembros{% if currentVersion == "free-pro-team@latest" %}, gerentes de facturación,{% endif %} y colaboradores externos en una organización.{% endif %} +| `invite_member` | Se activa cuando [se invita a un usuario nuevo a que se una a tu organización](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | Se activa cuando un propietario [le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | +| `oauth_app_access_denied` | Se activa cuando un propietario [inhabilita un acceso de {% data variables.product.prodname_oauth_app %} anteriormente aprobado](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) para tu organización. | +| `oauth_app_access_requested` | Se activa cuando un miembro de la organización solicita que un propietario otorgue un acceso de una {% data variables.product.prodname_oauth_app %} para tu organización.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Se activa cuando un propietario de la organización [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | +| `remove_actions_secret` | Se activa cuando el administrador de una organización elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | Se activa cuando un [propietario elimina un gerente de facturación de una organización](/articles/removing-a-billing-manager-from-your-organization/) o cuando [se requiere autenticación de dos factores en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no usa la 2FA o inhabilita la 2FA. |{% endif %} +| `remove_member (eliminar miembro)` | Se activa cuando un [propietario elimina a un miembro de una organización](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. También se activa cuando un [miembro de la organización se elimina a sí mismo](/articles/removing-yourself-from-an-organization/) de una organización. | +| `remove_outside_collaborator` | Se activa cuando un propietario elimina a un colaborador externo de una organización{% if currentVersion != "github-ae@latest" %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no utiliza la 2FA o la inhabilita{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | Se activa cuando un propietario de la organización [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `revoke_external_identity` | Se actuva cuando un dueño de una organización retira la identidad vinculada de un mimebro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | +| `revoke_sso_session` | Se activa cuando el dueño de una organización retira la sesión de SAML de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `runner_group_created` | Se activa cuando un administrador de la organización [crea un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization). | +| `runner_group_removed` | Se activa cuando un administrador de la organización elimina el grupo de ejecutores auto-hospedados. | +| `runner_group_renamed` | Se activa cuando un administrador de la organización renombra un grupo de ejecutores auto-hospedados. | +| `runner_group_runners_added` | Se activa cuando un administrador de la organización [agrega un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runners_removed` | Se activa cuando un administrador de la organización elimina un ejecutor auto-hospedado de un grupo. |{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `unblock_user` | Se acvita cuando el propietario de una organización [desbloquea a un usuario de la misma](/articles/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Se activa cuando un administrador de la organización actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `update_new_repository_default_branch_setting` | Se activa cuando el propietario cambia el nombre de la rama predeterminada para los repositorios nuevos de la organización. Para obtener más información, consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)".{% endif %} +| `update_default_repository_permission` | Se activa cuando un propietario cambia el nivel de permiso al repositorio predeterminado para los miembros de la organización. | +| `update_member` | Se activa cuando un propietario cambia el rol de una persona de propietario a miembro o de miembro a propietario. | +| `update_member_repository_creation_permission` | Se activa cuando un propietario cambia el permiso de crear repositorios para los miembros de la organización.{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Se activa cuando se actualizan las configuraciones del proveedor SAML de una organización. | +| `update_terms_of_service` | Se activa cuando una organización cambia de los Términos de servicio estándar a los Términos de servicio corporativos. Para obtener más información, consulta "[Subir de categoría a Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `org_credential_authorization` + +| Acción | Descripción | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `grant` | Se activa cuando un miembro [autoriza credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `deauthorized` | Se activa cuando un miembro [quita la autorización de credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `revoke` | Se desencadena cuando un dueño [revoca las credenciales autorizadas](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization). | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +#### Acciones de la categoría `organization_label` + +| Acción | Descripción | +| -------------------- | ----------------------------------------------------- | +| `create (crear)` | Se activa cuando se crea una etiqueta por defecto. | +| `update` | Se activa cuando se edita una etiqueta por defecto. | +| `destroy (destruir)` | Se activa cuando se elimina una etiqueta por defecto. | + +{% endif %} + +#### acciones de la categoría `oauth_application` + +| Acción | Descripción | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | +| `create (crear)` | Se activa cuando se crea una {% data variables.product.prodname_oauth_app %} nueva. | +| `destroy (destruir)` | Se activa cuando se elimina una {% data variables.product.prodname_oauth_app %} existente. | +| `reset_secret (restablecer secreto)` | Se activa cuando se restablece un secreto de cliente de {% data variables.product.prodname_oauth_app %}. | +| `revoke_tokens (revocar tokens)` | Se activa cuando se revocan los tokens de usuario de una {% data variables.product.prodname_oauth_app %}. | +| `transfer` | Se activa cuando se transfiere una {% data variables.product.prodname_oauth_app %} existente a una organización nueva. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `payment_method` + +| Acción | Descripción | +| ------------------ | ------------------------------------------------------------------------------------------------------------- | +| `clear (eliminar)` | Se activa cuando un método de pago archivado se [elimina](/articles/removing-a-payment-method). | +| `create (crear)` | Se activa cuando se agrega un método de pago nuevo, como una tarjeta de crédito nueva o una cuenta de PayPal. | +| `update` | Se activa cuando se actualiza un método de pago existente. | + +{% endif %} + +#### acciones de la categoría `profile_picture` +| Acción | Descripción | +| ------ | ------------------------------------------------------------------------------ | +| update | Se activa cuando estableces o actualizas la foto de perfil de tu organización. | + +#### acciones de la categoría `project` + +| Acción | Descripción | +| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create (crear)` | Se activa cuando se crear un tablero de proyecto. | +| `enlace` | Se activa cuando un repositorio se vincula a un tablero de proyecto. | +| `rename (renombrar)` | Se activa cuando se renombra un tablero de proyecto. | +| `update` | Se activa cuando se actualiza un tablero de proyecto. | +| `eliminar` | Se activa cuando se elimina un tablero de proyecto. | +| `unlink (desvincular)` | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto. | +| `update_org_permission (actualizar permiso de la organización)` | Se activa cuando se cambia o elimina el permiso al nivel de base para todos los miembros de la organización. | +| `update_team_permission (actualizar permiso del equipo)` | Se activa cuando se cambia el nivel de permiso del tablero de proyecto de un equipo o cuando se agrega un equipo a un tablero de proyecto o se elimina de este. | +| `update_user_permission` | Se activa cuando un miembro de la organización o colaborador externo se agrega a un tablero de proyecto o se elimina de este, o cuando se le cambia su nivel de permiso. | + +#### acciones de la categoría `protected_branch` + +| Acción | Descripción | +| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando se habilita la protección de rama en una rama. | +| `destroy (destruir)` | Se activa cuando se inhabilita la protección de rama en una rama. | +| `update_admin_enforced (actualizar administrador aplicado)` | Se activa cuando se aplica la protección de rama para los administradores del repositorio. | +| `update_require_code_owner_review (actualizar requerir revisión del propietario del código)` | Se activa cuando se actualiza en una rama la aplicación de revisión del propietario del código requerida. | +| `dismiss_stale_reviews (descartar revisiones en espera)` | Se activa cuando se actualiza en una rama la aplicación de las solicitudes de extracción en espera descartadas. | +| `update_signature_requirement_enforcement_level (actualizar nivel de aplicación del requisito de firma)` | Se activa cuando se actualiza la aplicación de la firma de confirmación requerida en una rama. | +| `update_pull_request_reviews_enforcement_level (actualizar nivel de aplicación de revisiones de solicitudes de extracción)` | Se activa cuando se actualiza el cumplimiento de las revisiones de solicitudes de extracción requeridas en una rama. | +| `update_required_status_checks_enforcement_level (actualizar nivel de aplicación de verificaciones de estado requeridas)` | Se activa cuando se actualiza en una rama la aplicación de verificaciones de estado requeridas. | +| `update_strict_required_status_checks_policy` | Se activa cuando se cambia el requisito para que una rama se encuentre actualizada antes de la fusión. | +| `rejected_ref_update (actualización de referencia rechazada)` | Se activa cuando se rechaza el intento de actualización de una rama. | +| `policy_override (anulación de política)` | Se activa cuando un administrador de repositorio anula un requisito de protección de rama.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| `update_allow_force_pushes_enforcement_level` | Se activa cuando se habilitan o inhabilitan las subidas de información forzadas en una rama protegida. | +| `update_allow_deletions_enforcement_level` | Se activa cuando se habilita o inhabilita el borrado de ramas en una rama protegida. | +| `update_linear_history_requirement_enforcement_level` | Se activa cuando se habilita o inhabilita el historial de confirmaciones linear requerido para una rama protegida. | +{% endif %} + +#### acciones de la categoría `repo` + +| Acción | Descripción | +| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access (acceder)` | Se activa cuando un usuario [cambia la visibilidad](/github/administering-a-repository/setting-repository-visibility) de un repositorio en la organización. | +| `add_member (agregar miembro)` | Se activa cuando un usuario acepta una [invitación para tener acceso de colaboración a un repositorio](/articles/inviting-collaborators-to-a-personal-repository). | +| `add_topic (agregar tema)` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". | +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} +| `archived (archivado)` | Se activa cuando un administrador del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)` | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)` | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)` | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create (crear)` | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Se activa cuando un administrador de repositorio [crea un secreto de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} +| `destroy (destruir)` | Se activa cuando [se borra un repositorio](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `disable` | Se activa cuando se inhabilita un repositorio (p. ej., por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %} +| `enable` | Se activa cuando se rehabilita un repositorio{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_actions_secret` | Se activa cuando un administrador de repositorio elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %} +| `remove_member (eliminar miembro)` | Se activa cuando un usuario se [elimina de su puesto de colaborador en un repositorio](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Se activa cuando un administrador del repositorio [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `remove_self_hosted_runner` | Se activa cuando un administrador del repositorio [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | +| `rename (renombrar)` | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository). | +| `transfer` | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository). | +| `transfer_start (comienzo de transferencia)` | Se activa cuando está por ocurrir una transferencia de repositorio. | +| `unarchived (desarchivado)` | Se activa cuando un administrador de repositorio deja de archivar un repositorio.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Se activa cuando un administrador de repositorio actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### acciones de la categoría `repository_advisory` + +| Acción | Descripción | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `close` | Se activa cuando alguien cierra una asesoría de seguridad. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| `cve_request` | Se activa cuando alguien solicita un número de CVE (Vulnerabilidades y Exposiciones Comunes) de {% data variables.product.prodname_dotcom %} para un borrador de asesoría de seguridad. | +| `github_broadcast` | Se activa cuando {% data variables.product.prodname_dotcom %} hace pública una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Se activa cuando {% data variables.product.prodname_dotcom %} retira una asesoría de seguridad que se publicó por error. | +| `open` | Se activa cuando alguien abre un borrador de asesoría de seguridad. | +| `publish` | Se activa cuando alguien publica una asesoría de seguridad. | +| `reopen` | Se activa cuando alguien vuelve a abrir un borrador de asesoría de seguridad. | +| `update` | Se activa cuando alguien edita un borrador de asesoría de seguridad o una asesoría de seguridad publicada. | + +#### Acciones de la categoría `repository_content_analysis` + +| Acción | Descripción | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enable` | Se activa cuando un propietario de la organización o persona con acceso administrativo al repositorio [habilita la configuración de uso de datos para un repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| `disable` | Se habilita cuando un propietario de la organización o una persona con acceso administrativo en el repositorio [inhabilita la configuración de uso de datos para un repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### Acciones de la categoría `repository_dependency_graph` + +| Acción | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo en el repositorio inhabilita la gráfica de dependencias para un repositorio {% if currentVersion == "free-pro-team@latest" %}privado {% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | +| `enable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo en el repositorio habilita la gráfica de dependencias para un repositorio {% if currentVersion == "free-pro-team@latest" %}privado {% endif %}. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Acciones de la categoría `repository_secret_scanning` + +| Acción | Descripción | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo en el repositorio inhabilita el escaneo de secretos para un repositorio {% if currentVersion == "free-pro-team@latest" %}privado {% endif %}. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | +| `enable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo en el repositorio habilita el escaneo de secretos para un repositorio {% if currentVersion == "free-pro-team@latest" %}privado {% endif %}. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### acciones de la categoría `repository_vulnerability_alert` + +| Acción | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando {% data variables.product.product_name %} crea una alerta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad del {% data variables.product.prodname_dependabot %}{% endif %} para un repositorio que utiliza una dependencia vulnerable. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | +| `dismiss` | Se activa cuando un propietario de organización o persona con acceso administrativo en el repositorio descarta una alerta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}seguridad del {% else %}{% data variables.product.prodname_dependabot %}{% endif %} sobre una dependencia vulnerable. | +| `resolve` | Se activa cuando alguien con acceso de escritura en un repositorio sube cambios para actualizar y resolver una vulnerabilidad en una dependencia de proyecto. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `repository_vulnerability_alerts` + +| Acción | Descripción | +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `authorized_users_teams` | Se activa cuando un propietario de la organización o un miembro con permisos de administrador en el repositorio actualiza la lista de personas o equipos autorizados para recibir las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en dicho repositorio. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". | +| `disable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este inhabilita las {% data variables.product.prodname_dependabot_alerts %}. | +| `enable` | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este habilita las {% data variables.product.prodname_dependabot_alerts %}. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Acciones de la categoría `secret_scanning` + +| Acción | Descripción | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de organización inhabilita el escaneo de secretos para todos los repositorios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} existentes. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | +| `enable` | Se activa cuando un propietario de organización habilita el escaneo de secretos para todos los repositorios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} existentes. | + +#### Acciones de la categoría `secret_scanning_new_repos` + +| Acción | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `disable` | Se activa cuando un propietario de organización inhabilita el escaneo de secretos para todos los repositorios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} nuevos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). | +| `enable` | Se activa cuando un propietario de organización habilita el escaneo de secretos para todos los repositorios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} nuevos. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `sponsors` + +| Acción | Descripción | +| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo_funding_link_button_toggle (alternar botón de enlace al financiamiento del repositorio)` | Se activa cuando habilitas o inhabilitas un botón de patrocinador en tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)` | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)` | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)` | Se activa cuando patrocinas una cuenta (consulta "[Patrocinar a un contribuyente de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de una cuenta patrocinada (consulta "[Administrar tu patrocinio](/articles/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)` | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve (aprobación de programador patrocinado)` | Se activa cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create (creación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Se activa cuando editas tu perfil de organización patrocinada (consulta "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Se activa cuando emites tu solicitud para {% data variables.product.prodname_sponsors %} para su aprobación (consulta "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta "[Cambiar tus niveles de patrocinio](/articles/changing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado) | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta "[Contactar a tus patrocinadores](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `waitlist_join (incorporación a la lista de espera)` | Se activa cuando te unes a la lista de espera para convertirte en una organización patrocinada (consulta "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +{% endif %} + +#### acciones de la categoría `team` + +| Acción | Descripción | +| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member (agregar miembro)` | Se activa cuando un miembro de una organización se [agrega a un equipo](/articles/adding-organization-members-to-a-team). | +| `add_repository (agregar repositorio)` | Se activa cuando se le otorga el control de un repositorio a un equipo. | +| `change_parent_team (cambiar equipo padre)` | Se activa cuando se crea un equipo hijo o [se modifica el padre de un equipo hijo](/articles/moving-a-team-in-your-organization-s-hierarchy). | +| `change_privacy (cambiar privacidad)` | Se activa cuando se modifica el nivel de privacidad de un equipo. | +| `create (crear)` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. + +#### acciones de la categoría `team_discussions` + +| Acción | Descripción | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Se activa cuando un propietario de la organización inhabilita los debates de equipo para una organización. Para obtener más información, consulta "[Desactivar los debates del equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)". | +| `enable` | Se activa cuando un propietario de la organización habilita los debates de equipo para una organización. | + +### Further reading + +- "[Mantener segura tu organización](/articles/keeping-your-organization-secure)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000000..32984b5af09bd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,21 @@ +--- +title: Revisar las integraciones instaladas de tu organización +intro: Puedes revisar los niveles de permiso para las integraciones instaladas de tu organización y configurar cada accedo de integración a los repositorios de la organización. +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. En la barra lateral izquierda, haz clic en **Installed {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s instaladas). ![Pestaña de {% data variables.product.prodname_github_app %}s instaladas en la barra lateral de parámetros de la organización](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). ![Botón Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Revisa el acceso al repositorio y los permisos de {% data variables.product.prodname_github_app %}. ![Opción para darle acceso a {% data variables.product.prodname_github_app %} a todos los repositorios o a repositorios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png) + - Para darle acceso a la {% data variables.product.prodname_github_app %} a todos los repositorios de tu organización, selecciona **All repositories** (Todos los repositorios). + - Para elegir repositorios específicos para darle acceso a la aplicación, selecciona **Only select repositories** (Solo repositorios seleccionados), luego escribe el nombre de un repositorio. +7. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000000..b7fe5cccbf59f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md @@ -0,0 +1,31 @@ +--- +title: Configurar los permisos base para una organización +intro: Puedes configurar permisos base para los repositorios que pertenezcan a una organización. +permissions: Los dueños de la organización pueden configurar permisos base para la misma. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los permisos base para una organización + +Puedes configurar permisos base que apliquen a todos los miembros de una organización cuando accedan a cualquiera de los repositorios de la misma. Los permisos base no aplican para los colaboradores externos. + +{% if currentVersion == "free-pro-team@latest" %}Predeterminadamente, los miembros de una organización tendrán permisos de **Lectura** en los repositorios de la organización.{% endif %} + +Si alguien con permisos administrativos en un repositorio de la organización otorga un nivel superior de permisos en el mismo a algún miembro, este nivel de permiso superior anulará el permiso base. + +### Configurar los permisos base + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Debajo de "Permisos Base", utiliza el menú desplegable para seleccionar los nuevos permisos base. ![Selección de nuevo nivel de permiso desde el menú desplegable de "permisos base"](/assets/images/help/organizations/base-permissions-drop-down.png) +6. Revisa los cambios. Da clic en **Cambiar el permiso predeterminado por PERMISO** para confirmar. ![Revisar y confirmar el cambio de permisos base](/assets/images/help/organizations/base-permissions-confirm.png) + +### Further reading + +- "[Niveles de permisopara una organización en un repositorio](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- "[Añadir colaboradores externos a los repositorios de tu organización](/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000000..37543c81dfe4c --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,24 @@ +--- +title: Configurar permisos para agregar colaboradores externos +intro: 'Para proteger los datos de tu organización y la cantidad de licencias pagadas que se utilizan en ella, puedes permitir que únicamente los propietarios inviten colaboradores externos a los repositorios que le pertenezcan.' +product: '{% data reusables.gated-features.restict-add-collaborator %}' +redirect_from: + - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/ + - /articles/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios de la organización y los miembros con privilegios administrativos en los repositorios pueden invitar colaboradores externos para trabajar en ellos. También puedes restringir los permisos de invitación de colaboradores externos para que solo los propietarios de la organización puedan emitirlos. + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Debajo de "Invitaciones al repositorio", selecciona **Permitir que los miembros inviten colaboradores externos a los repositorios de esta organización**.{% 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. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000000..e24ccb17dca6a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,20 @@ +--- +title: Configurar permisos para eliminar o transferir repositorios en tu organización +intro: 'Puedes permitir que los miembros de una organización con permisos de administrador accedan a un repositorio para eliminar o transferir el repositorio, o limitar la capacidad para borrar o transferir repositorios únicamente a los propietarios de la organización.' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios pueden configurar permisos para eliminar o transferir repositorios en una organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Dentro de "Repository deletion and transfer" (Eliminación o transferencia de repositorios), selecciona o deselecciona **Allow members to delete or transfer repositories for this organization (Permitir que los miembros puedan eliminar o transferir repositorios para esta organización)**. ![Casilla de verificación para permitir que los miembros eliminen repositorios](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000000..966ae250d9ecb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,21 @@ +--- +title: Configurar permisos de creación de equipos en tu organización +intro: Puedes permitirle a todos los miembros de la organización crear equipos o limitar la creación de equipos a los propietarios de la organización. +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los propietarios de la organización pueden establecer permisos de creación de equipos. + +Si no configuras permisos de creación de equipos, todos los miembros de la organización podrán crear equipos por defecto. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Dentro de "Team creation rules" (Reglas de creación de equipos), selecciona o deselecciona **Allow members to create teams (Permitirle a los miembros crear equipos)**. ![Casilla de verificación para permitir que los miembros creen equipos](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000000..1a53fd078bbe7 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,20 @@ +--- +title: Configurar la imagen de perfil de tu equipo +intro: 'Los mantenedores del equipo y los propietarios de la organización pueden establecer una imagen de perfil para un equipo, que se muestra en la página del equipo.' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Excepto que configures una imagen de perfil para un equipo, la imagen de perfil del equipo coincidirá con la imagen de perfil de la organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Haz clic en **Upload new picture (Cargar una imagen)** o selecciona la imagen de perfil que deseas. ![Cargar nueva imagen](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. Haz clic y arrastra el recorte de la imagen según se necesite, después haz clic en **Set new team avatar (Establecer nuevo avatar del equipo)**. ![Establecer nuevo avatar del equipo](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000000..fcca3f5725cb5 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,71 @@ +--- +title: Sincronizar un equipo con un grupo de proveedor de identidad +intro: 'Puedes sincronizar un equipo de {% data variables.product.prodname_dotcom %} con un grupo de proveedor de identidad (IdP) para agregar y eliminar miembros del grupo automáticamente.' +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Los propietarios de la organización y mantenedores de equipo pueden sincronizar un equipo de {% data variables.product.prodname_dotcom %} con un grupo de IdP.' +versions: + free-pro-team: '*' +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Acerca de la sincronización de equipo + +{% data reusables.identity-and-permissions.about-team-sync %} + +Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.prodname_dotcom %}. Un grupo de IdP puede asignarse a varios equipos de {% data variables.product.prodname_dotcom %} sin restricción. + +Team synchronization does not support IdP groups with more than 5000 members. + +Una vez que un equipo de {% data variables.product.prodname_dotcom %} se conecta a un grupo de IdP, tu administrador de IdP debe hacer cambios en la membrecía del equipo a través del proveedor de identidad. No puedes administrar la membrecía del equipo en {% data variables.product.product_name %} ni utilizando la API. + +Todos los cambios a la membrecía de equipo que se hagan con tu IdP aparecerán en la bitácora de auditoría en {% data variables.product.product_name %} como cambios que realiza el bot de sincronización de equipos. Tu IdP enviará datos de la membresía de equipo a {% data variables.product.prodname_dotcom %} una vez por hora. Conectar un equipo a un grupo IdP puede eliminar a algunos miembros del equipo. Para obtener más información, consulta "[Requisitos para los miembros de los equipos sincronizados](#requirements-for-members-of-synchronized-teams)." + +Los equipos padre no pueden sincronizarse con los grupos de IdP. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre. Para obtener más información, consulta las secciónes "[Acerca de los equipos](/articles/about-teams#nested-teams)", "[Crear un equipo](/github/setting-up-and-managing-organizations-and-teams/creating-a-team)", y "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organizations-hierarchy)". + +Para administrar el acceso de un repositorio para cualquier equipo de {% data variables.product.prodname_dotcom %}, incluyendo los equipos conectados a un grupo de IdP debes hacer cambios con {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams)" y "[Administrar el acceso de equipo a un repositorio de la organización](/articles/managing-team-access-to-an-organization-repository)." + +También puedes administrar la sincronización de equipos con la API. Para obtener más información, consulta la sección "[Sincronización de equipos](/rest/reference/teams#team-sync)". + +### Requisitos para los miembros de los equipos sincronizados + +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. + +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." + +Puedes volver a agregar automáticamente a aquellos miembros del equipo que hayas eliminado una vez que se autentiquen en la cuenta empresarial u organizacional utilizando el SSO y así se migren al grupo de IdP conectado. + +Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +Si tu organización pertenece a una cuenta empresarial, habilitar la sincronización de equipos para la cuenta empresarial anulará la configuración de sincronización de equipos a nivel organizacional. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Prerrequisitos + +Antes de poder conectar a un equipo con un grupo de proveedor de identidad, un propietario de organización o de empresa debe habilitar la sincronización de equipos para tu organización o cuenta empresarial. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +Para evitar el eliminar miembros del equipo accidentalmente, visita el protal administrativo para tu IdP y confirma que cada miembro actual del equipo también se encuentre en los grupos de IdP que quieras conectar a este equipo. Si no tienes este acceso a tu proveedor de identidad, puedes comunicarte con tu administrador de IdP. + +Debes autenticarte utilizando el SSO de SAML. Para obtener más información, consulta "[Acerca de la autenticación con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)". + +### Conectar un grupo de IdP a tu equipo + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Debajo de "Grupos del Proveedor de Identidad", utiliza el menú desplegable y selecciona hasta 5 grupos del proveedor de identidad. ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) +6. Haz clic en **Guardar cambios**. + +### Desconectar un grupo de IdP de un equipo + +Si desconectas un grupo de IdP de un equipo de {% data variables.product.prodname_dotcom %}, los miembros de este equipo que fueran asignados al equipo {% data variables.product.prodname_dotcom %} a través del grupo de IdP se eliminarán de dicho equipo. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +6. Debajo de "Grupos del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. ![Deselecciona un grupo IdP conectado desde el equipo de GitHub](/assets/images/help/teams/unselect-idp-group.png) +7. Haz clic en **Guardar cambios**. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md new file mode 100644 index 0000000000000..910597c1b438c --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md @@ -0,0 +1,25 @@ +--- +title: Transferir la propiedad de la organización +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership +intro: 'Para que alguien más sea el propietario de una cuenta organizacional, debes agregar un propietario nuevo{% if currentVersion == "free-pro-team@latest" %}, asegurarte de que la información de facturación esté actualizada,{% endif %} y luego eliminarte a ti mismo de la cuenta.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +1. Si eres el único miembro con privilegios de *propietario*, otorga el rol de propietario a otro miembro de la organización. Para obtener más información, consulta "[Designar a un propietario de la organización](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)". +2. Contáctacte con el propietario nuevo y asegúrate de que pueda [acceder a los parámetros de la organización](/articles/accessing-your-organization-s-settings). +{% if currentVersion == "free-pro-team@latest" %} +3. Si actualmente eres responsable de pagarle a GitHub en tu organización, también tendrás que hacer que el propietario nuevo o un [gerente de facturación](/articles/adding-a-billing-manager-to-your-organization/) actualice la información de pago de la organización. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". + + {% warning %} + + **Advertencia**: Eliminarte de la organización **no** actualiza la información de facturación archivada para la cuenta de la organización. El propietario nuevo o un gerente de facturación debe actualizar la información de facturación archivada para eliminar tu información de tarjeta de crédito o de PayPal. + + {% endwarning %} + +{% endif %} +4. [Eliminarte](/articles/removing-yourself-from-an-organization) de la organización. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000000..f4a1a8f6eb5c6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,22 @@ +--- +title: Subir de categoría a los Términos de servicio corporativos +intro: Las organizaciones pueden subir de categoría desde los Términos de servicio estándar a los Términos de servicio corporativos. +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +--- + +Los Términos de servicio estándar son un acuerdo entre {% data variables.product.prodname_dotcom %} y tú como individualidad. Para suscribir un acuerdo con {% data variables.product.prodname_dotcom %} en nombre de una entidad, como una empresa, una organización sin fines de lucro o un grupo, los propietarios de la organización pueden subir de categoría a los Términos de servicio corporativos. + +1. Contacto + +{% data variables.contact.contact_support %} para solicitar una mejora a las Condiciones de Servicio Corporativas. Habilitarán un anuncio en el tablero de tu organización que te permitirá aceptar los Términos de servicio corporativos. +{% data reusables.dashboard.access-org-dashboard %} +3. En la parte de arriba de la página, a la derecha del anuncio de los Términos de servicio, haz clic en **Sign now** (Firmar ahora). ![Botón Sign now (Firmar ahora)](/assets/images/help/organizations/sign-now-button.png) +4. Lee la información acerca de los Términos de servicio corporativos, luego selecciona **Yes, I want to sign these terms on behalf of my business.** (Sí, quiero firmar estos términos en nombre de mi empresa.). ![Casilla para firmar en nombre de tu empresa](/assets/images/help/organizations/sign-on-behalf-business.png) +5. Escribe el nombre de la empresa, organización sin fines de lucro o grupo al que le pertenece la cuenta de la organización. Esta es la entidad que celebrará el acuerdo con {% data variables.product.prodname_dotcom %}. ![Campo del nombre de la empresa](/assets/images/help/organizations/business-name-field.png) +6. Para aceptar los Términos de servicio corporativos en nombre de tu entidad, haz clic en **Accept terms** (Aceptar términos). ![Botón Accept terms (Aceptar términos)](/assets/images/help/organizations/accept-terms-button.png) + +### Further reading +- "[Términos de servicio corporativos de GitHub](/articles/github-corporate-terms-of-service/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md new file mode 100644 index 0000000000000..3b86692fb387c --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md @@ -0,0 +1,38 @@ +--- +title: Verificar el dominio de tu organización +intro: 'Puedes verificar los dominios controlados por tu organización para confirmar la identidad de tu organización en {% data variables.product.product_name %}.' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain +versions: + free-pro-team: '*' +--- + +### Acerca de la verificación de dominios + +Para verificar dominios en {% data variables.product.product_name %}, debes tener permisos de propietario en la organización. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". También necesitarás acceso para modificar los registros de dominio con tu servicio de alojamiento de dominio. + +Después de verificar la propiedad de los dominios de tu organización, se mostrará un distintivo "Verified" (Verificado) en el perfil de la organización. Si tu organización está en {% data variables.product.prodname_ghe_cloud %} y ha aceptado los Términos de servicio corporativos, los propietarios de la organización podrán verificar la identidad de los miembros de la organización al ver la dirección de correo electrónico de cada miembro dentro del dominio verificado. Para obtener más información, consulta "[Acerca de la página de perfil de tu organización](/articles/about-your-organization-s-profile/)" y "[Actualizar a los Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)." + +Si tu organización le pertenece a una cuenta empresarial, se mostrará una "insignia verificada" en el perfil de tu organización para cualquier dominio verificado en dicha cuenta, adicinalmente a cualquier dominio verificado para la organización. Para obtener más información, consulta la sección "[Verificar el dominio de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)". + +{% data reusables.organizations.verified-domains-details %} + +En {% data variables.product.prodname_ghe_cloud %}, después de verificar la propiedad del dominio de tu organización, puedes restringir las notificaciones por correo electrónico para la organización a ese dominio. Para obtener más información, consulta "[Restringir las notificaciones por correo electrónico a un dominio aprobado](/articles/restricting-email-notifications-to-an-approved-domain)". + +### Verificar el dominio de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. Haz clic en **Add a domain (Agregar un dominio)**. ![Botón para agregar un dominio](/assets/images/help/organizations/add-a-domain-button.png) +{% data reusables.organizations.add-domain %} +{% data reusables.organizations.add-dns-txt-record %} +1. Espera a que cambie la configuración de tu DNS, lo cual puede llevar hasta 72 horas. Puedes confirmar que tu configuración de DNS cambió si ejecutas el comando `dig` en la línea de comandos, reemplazando `ORGANIZATION` con el nombre de tu organización y `example.com` con el dominio que te gustaría verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando. + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. Después de confirmar que tu registro de TXT se agregó en tu DNS, desplázate hasta la pestaña Verified domains (Dominios verificados) en las configuraciones de tu organización. Puedes seguir los pasos anteriores uno a cuatro para ubicar la pestaña Dominios verificados. ![Página de configuraciones de dominios verificados con dominio pendiente](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. Como alternativa, una vez que la insignia "Verified" (Verificado) es visible en la página de perfil de tu organización, puedes eliminar la entrada de TXT desde el registro de DNS en tu servicio de alojamiento de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000000..ad8b1be621a85 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Visualizar y administrar el acceso de SAML de un miembro a tu organización +intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la organización, sesiones activas y credenciales autorizadas.' +permissions: Los dueños de organización pueden ver y administrar el acceso de SAML de un miembro a la misma. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/viewing-and-revoking-organization-members-authorized-access-tokens + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-revoking-organization-members-authorized-access-tokens +versions: + free-pro-team: '*' +--- + +### Acerca del acceso de SAML a tu organización + +Cuando habilitas el inicio de sesión único de SAML para tu organización, cada miembro de ella puede vincular su identidad externa con tu proveedor de identidad (IdP) a su cuenta existente de {% data variables.product.product_name %}. Para acceder a los recursos de tu organización en {% data variables.product.product_name %}, el miembro debe tener una sesión activa de SAML en su buscador. Para acceder a los recursos de tu organización utilizando Git o la API, el miembro debe utilizar un token de acceso personal o llave SSH que se le haya autorizado para su uso con tu organización. + +Puedes ver y revocar la identidad vinculada de cada miembro, sesiones activas y credenciales auotrizadas en la misma página. + +### Visualizar y revocar una identidad vinculada + +{% data reusables.saml.about-linked-identities %} + +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} + +### Visualizar y revocar una sesión activa de SAML + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} + +### Visualizar y revocar credenciales autorizadas + +{% data reusables.saml.about-authorized-credentials %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} + +### Further reading + +- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000000..b2f1f5c53407a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md @@ -0,0 +1,48 @@ +--- +title: Ver información de tu organización +intro: 'La información de tu organización brinda datos acerca de la actividad, las contribuciones y las dependencias de tu organización.' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +--- + +Todos los miembros de una organización pueden ver información de la organización. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". + +Puedes utilizar la información sobre la actividad de la organización para ayudarte a comprender mejor cómo los miembros de tu organización están utilizando {% data variables.product.product_name %} para colaborar y trabajar con el código. La información sobre las dependencias puede ayudarte a rastrear, informar y actuar en relación al uso del código abierto de tu organización. + +### Ver la información de la actividad de la organización + +{% note %} + +**Nota:**las perspectivas de actividad en las organizaciones se encuentran actualmente en un beta público y están sujetos a cambio. + +{% endnote %} + +Con la información sobre la actividad de la organización puedes ver semanal, mensual y anualmente las visualizaciones de datos de toda tu organización o de repositorios específicos, incluida la actividad de las propuestas y las solicitudes de extracción, los principales lenguajes utilizados e información acumulada sobre dónde los miembros de tu organización pasan su tiempo. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Haz clic en la pestaña de información de la organización](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Como alternativa, en el ángulo superior derecho de la página, elige ver los datos del/de la último/a **semana**, **mes** o **año**. ![Elige un período de tiempo para ver la información de la organización](/assets/images/help/organizations/org-insights-time-period.png) +5. Alternativamente, en el ángulo superior derecho de la página, elige ver hasta tres repositorios y haz clic en **Apply (Aplicar)**. ![Elige repositorios para ver la información de la organización](/assets/images/help/organizations/org-insights-repos.png) + +### Ver la información de las dependencias de la organización +Con la información sobre las dependencias puedes ver vulnerabilidades, licencias y otra información importante de los proyectos de código abierto de los que depende tu organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Pestaña de información en la barra de navegación principal de la organización](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Para ver las dependencias de esta organización, haz clic en **Dependencies (Dependencias)**. ![Pestaña de dependencias debajo de la barra de navegación principal de la organización](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. Para ver la información de las dependencias de todas tus organizaciones {% data variables.product.prodname_ghe_cloud %}, haz clic en **My organizations (Mis organizaciones)**. ![Botón Mi organización dentro de la pestaña de dependencias](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. Puedes hacer clic en los resultados de los gráficos **Open security advisories** (Avisos de seguridad abiertos) y **Licenses** (Licencias) para filtrar por estado de vulnerabilidad, por licencia o por una combinación de ambos. ![Gráficas de "las vulnerabilidades de mis organizaciones" y de licencias](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. Puedes hacer clic en {% octicon "package" aria-label="The package icon" %} **dependents (dependientes)** al lado de cada vulnerabilidad para ver qué dependiente en tu organización está usando cada biblioteca. ![Dependientes vulnerables de mis organizaciones](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + + + ### Further reading + + - "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" + - "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - "[Cambiar la visibilidad de la información de dependencias de tu organización](/github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights)" + - "[Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000000..2f5d66ef4fd3e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,37 @@ +--- +title: Ver personas con acceso a tu repositorio +intro: 'Los propietarios de la organización pueden ver el acceso de las personas a un repositorio dentro de una organización. Los propietario de organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %} también pueden exportar una lista CSV de personas que tienen acceso a un repositorio.' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los administradores pueden utilizar esta información para ayudar a personas externas, reunir datos de cumplimiento y otras verificaciones generales de seguridad. + +![Lista de permisos de personas a un repositorio](/assets/images/help/repository/repository-permissions-list.png) + +### Ver personas con acceso a tu repositorio + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota**: También puedes tener una vista general combinada de los equipos y personas con acceso a tu repositorio. Para obtener más información, consulta la sección "[Administrar los equipos y personas con acceso a tu repositorio](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)". + +{% endnote %} +{% endif %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} + +### Exportar una lista de personas con acceso a tu repositorio + +Los propietario de organizaciones en {% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %} pueden exportar una lista CSV de personas que tienen acceso a un repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. Haz clic en **Export CSV (Exportar CSV)**. ![Pestaña de personas en la barra lateral del repositorio](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000000..f5e3691604957 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,26 @@ +--- +title: Ver si los usuarios en tu organización han habilitado 2FA +intro: 'Puedes ver los propietarios de la organización, miembros y colaboradores externos que han habilitado la autenticación de dos factores.' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% note %} + +**Nota:** Puedes requerir que todos los miembros{% if currentVersion == "free-pro-team@latest" %}, incluyendo a los propietarios, gerentes de facturación y{% else %} y{% endif %} colaboradores externos en tu organización, deban habilitar la autenticación bifactorial. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)". + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Para ver los miembros de la organización, incluidos los propietarios de la organización, que han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. Para ver los colaboradores externos en tu organización, dentro de la pestaña "People" (Personas), haz clic en **Outside collaborators (Colaboradores externos)**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. Para ver qué colaboradores externos han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### Further reading + +- "[Ver los roles de las personas en un organización](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md new file mode 100644 index 0000000000000..71382466828c9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -0,0 +1,45 @@ +--- +title: Acerca de las cuentas de empresa +intro: 'Con {% data variables.product.prodname_ghe_cloud %}, puedes crear una cuenta de empresa para activar la colaboración entre tus organizaciones, al mismo tiempo que le das a los administradores un punto único de visibilidad y administración.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/about-github-business-accounts/ + - /articles/about-enterprise-accounts + - /github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de las cuentas de empresa + +Una cuenta empresarial te permite administrar varias organizaciones de {% data variables.product.prodname_dotcom %} e instancias de {% data variables.product.prodname_ghe_server %}. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. Los administradores de empresas pueden administrar los parámetros y las referencias, como: + +- El acceso de los miembros y la administración (miembros de la organización, colaboradores externos). +- Facturación y uso (instancias de {% data variables.product.prodname_ghe_server %}, licencias de usuario, paquetes de {% data variables.large_files.product_name_short %}) +- Seguridad (inicio de sesión único, autenticación de dos factores). +- Solicitudes y paquetes de soporte compartidos con {% data variables.contact.enterprise_support %} + +{% data reusables.enterprise-accounts.enterprise-accounts-billing %} Para obtener más información sobre cómo administrar tu suscripción de {% data variables.product.prodname_ghe_cloud %}, consulta la sección "[Visualizar la suscripción y uso de tu cuenta empresarial](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)". Para obtener más información acerca de cómo administrar tu configuración de facturación de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Administrar la facturación de tu empresa](/admin/overview/managing-billing-for-your-enterprise)". + +Para obtener más información acerca de las diferencias entre {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}, consulta la sección "[ productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". Para mejorar tu cuenta a {% data variables.product.prodname_enterprise %} o para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}. + +Para obtener más información sobre el acceso y la administración de los miembros, consulta la sección "{% if currentVersion == "free-pro-team@latest" %}[Administrar a los usuarios en tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Administrar a los usuarios, organizaciones y repositorios](/admin/user-management){% endif %}". + +Para obtener más información acerca de cómo administrar las cuentas empresariales utilizando la API de GraphQL, consulta la sección "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)". + +{% if currentVersion == "free-pro-team@latest" %} + +### Administrar las organizaciones vinculadas con tu cuenta de empresa + +Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Los propietarios pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. Para obtener más información, consulta "[Acerca de las organizaciones](/articles/about-organizations)". + +Los propietarios de la empresa pueden crear organizaciones y vincularlas a la empresa. Después de añadir organizaciones a tu cuenta empresarial, podrás administrar y hacer cumplir las políticas organizacionales. Las opciones de cumplimiento específicas varían según el parámetro, generalmente, puedes elegir implementar una política única para cada organización en tu cuenta de empresa o puedes permitirle a los propietarios configurar la política en el nivel de organización. + +Para obtener más información, consulta "[Administrar las organizaciones de tu cuenta de empresa](/articles/managing-organizations-in-your-enterprise-account)" y "[Configurar políticas para las organizaciones de tu cuenta de empresa](/articles/setting-policies-for-organizations-in-your-enterprise-account)". + +{% endif %} + +### Administrar las licencias de {% data variables.product.prodname_ghe_server %} enlazadas con tu cuenta empresarial + +{% data reusables.enterprise-accounts.admin-managing-licenses %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..e4fb6eda766ad --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. Para obtener más información, consulta la sección [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio web de OASIS. + +| IdP | SAML | User provisioning | Sincronización de equipos | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..ea52a2c463bdd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} Opcionalmente, puedes habilitar el aprovisionamiento de SAML y, por separado, el desaprovisionamiento. + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. Si habilitas el aprovisionamiento de SAML, cada que un miembro de la empresa acceda a un recurso que protege tu configuración de SAML en la cuenta de la empresa, esa aserción de SAML activará el aprovisionamiento. + +Para cada llamada de SCIM o aserción de SAML, {% data variables.product.product_name %} verificará los grupos de IdP a los cuales pertenece el usuario y realizará las siguientes operaciones: + +- Si el usuario es un miembro de un grupo de IdP que corresponda a una organización que pertenezca a tu cuenta empresarial, y el usuario no es actualmente miembro de dicha organización, agrégalo a la organización (aserción de SAML) o envía una invitación por correo electrónico al usuario para que se una a una organización (llamado de SCIM). +- Cancela cualquier invitación que exista para que el usuario se una a la organización que pertenece a tu cuenta empresarial. + +Para cada llamada de SCIM y, en caso de que habilites el desaprovisionamiento de SAML, en cada aserción de SAML, {% data variables.product.product_name %} también realizará la siguiente operación: + +- Si el usuario no es un miembro de un grupo de IdP que corresponde a una organización que pertenezca a tu cuenta empresarial y éste es un miembro actual de dicha organización, elimina al usuario de la organización. + +Si el desaprovisionamiento eleimina al último propietario que queda en una organización, ésta quedará sin propietario. Los propietarios de las empresas pueden asumir la propiedad de las organizaciones sin propietario. Para obtener más información, consulta la sección "[Administrar las organizaciones sin dueño en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)". + +Para habilitar el aprovisionamiento de usuarios en tu cuenta empresarial utilizandoOkta, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md new file mode 100644 index 0000000000000..1639231503fa1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md @@ -0,0 +1,27 @@ +--- +title: Agregar organizaciones en tu cuenta de empresa +intro: Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/adding-organizations-to-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/adding-organizations-to-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Los propietarios de la empresa pueden crear nuevas organizaciones dentro de los parámetros de la cuenta de empresa. + +Para agregar una organización a tu cuenta de empresa, debes crear la organización desde el interior de los parámetros de la cuenta de empresa. No puedes transferir las organizaciones existentes a una cuenta de empresa. + +### Crear una organización en tu cuenta de empresa + +Las organizaciones nuevas que crees dentro de los parámetros de la cuenta de empresa se incluyen en la suscripción de la cuenta de empresa de {% data variables.product.prodname_ghe_cloud %}. Para más información sobre la colaboración en organizaciones, consulta "[Configurar y administrar organizaciones y equipo](/categories/setting-up-and-managing-organizations-and-teams)". + +Los propietarios de empresas que creen una organización que es propiedad de una cuenta de empresa se convierten automáticamente en los propietarios de la organización. Para obtener más información sobre los propietarios de organizaciones, consulta "[Niveles de permiso de una organización](/articles/permission-levels-for-an-organization)." + +{% data reusables.enterprise-accounts.access-enterprise %} +2. En la pestaña **Organizations** (Organizaciones), encima de la lista d elas organizaciones, haz clic en **New organization** (Organización nueva). ![Botón de la nueva organización](/assets/images/help/business-accounts/enterprise-account-add-org.png) +3. En "Organization name" (Nombre de la organización) escribe un nombre para tu organización. ![Campo para escribir el nombre de una organización nueva](/assets/images/help/business-accounts/new-organization-name-field.png) +4. Haz clic en **Create organization** (Crear organización). +5. En "Invite owners" (Invitar propietarios), escribe el nombre de usuario de una persona a la que te gustaría invitar para convertir en propietario de la organización, luego clic en **Invite** (Invitar). ![Campo de búsqueda del propietario de la organización y botón Invite (Invitar)](/assets/images/help/business-accounts/invite-org-owner.png) +6. Da clic en **Finalizar**. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..3dd5bdf2aeca3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md new file mode 100644 index 0000000000000..5633fa000a119 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -0,0 +1,103 @@ +--- +title: Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta +intro: 'Puedes utilizar el inicio de sesión único (SSO, por sus siglas en inglés) del Lenguaje de Marcado para Confirmaciones (SAML, por sus siglas en inglés) y la Adminsitración de Identidad a Través de Dominios (SCIM, por sus siglas en inglés) con Okta para adminsitrar automáticamente el acceso a tu cuenta empresarial en {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-and-scim-for-your-enterprise-account-using-okta + - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +### Acerca de SAML y SCIM con Okta + +Puedes controlar el acceso a tu cuenta empresarial en {% data variables.product.product_name %} y en otras aplicaciones web desde una interface central si configuras dicha cuenta para que utilice el SSO de SAML y SCIM con Okta, un proveedor de identidad (IdP). + +El SSO de SAML controla y protege el acceso a los recursos de la cuenta empresarial como las organizaciones, repositorios, informes de problemas y solicitudes de extracción. El SCIM agrega, administra y elimina automáticamente el acceso de los miembros a las organizaciones que pertenezcan a tu cuenta empresarial cuando haces cambios en Okta. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)". + +Después de que habilites SCIM, las siguientes características de aprovisionamiento estarán disponibles para cualquier usuario al que asignes tu aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta. + +| Característica | Descripción | +| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Subir Usuarios Nuevos | Los usuarios nuevos que se crean en Okta obtendrán acceso a los recursos de la cuenta empresarial y, opcionalmente, se pueden invitar a cualquiera de las organizaciones que pertenezcan a esta cuenta | +| Subir Desactivaciones de Usuarios | Desactivar un usuario en Okta revocará el acceso del mismo a los recursos de la cuenta empresarial y eliminará al usuario de todas las organizaciones que pertenezcan a esta cuenta | +| Subir Actualizaciones de Perfil | Las actualizaciones que se hagan al perfil de usuario en Okta se subirán a los metadatos de la cuenta empresarial del usuario | +| Reactivar Usuarios | Reactivar al usuario en Okta rehabilitará el acceso del mismo a la cuenta empresarial y, opcionalmente, enviará invitaciones por correo electrónico al usuario para volverse a unir a cualquiera de las organizaciones que pertenezcan a la cuenta empresarial de la cual era miembro este usuario previamente | + +### Prerrequisitos + +{% data reusables.saml.use-classic-ui %} + +### Agregar la aplicación {% data variables.product.prodname_ghe_cloud %} en Okta + +{% data reusables.saml.okta-admin-button %} +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +1. Da clic en "{% data variables.product.prodname_ghe_cloud %} - Cuentas Empresariales". +1. Da clic en **Agregar**. +1. Opcionalmente, a la derecha de la "Etiqueta de aplicación", teclea un nombre descriptivo para la aplicación. ![Campo de etiqueta de la aplicación](/assets/images/help/saml/okta-application-label.png) +1. A la derecha de "Empresas de {% data variables.product.prodname_dotcom %}", teclea el nombre de tu cuenta empresarial. Por ejemplo, si la URL de tu cuenta empresarial es `https://github.com/enterprises/octo-corp`, teclea `octo-corp`. ![Campo de Github Enterprises](/assets/images/help/saml/okta-github-enterprises.png) +1. Haz clic en **Done** (listo). + +### Habilitar y probar el SSO de SAML + +{% data reusables.saml.okta-admin-button %} +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.click-enterprise-account-application %} +{% data reusables.saml.assign-yourself-to-okta %} +{% data reusables.saml.okta-sign-on-tab %} +1. A la derecha de los Ajustes, da clic en **Editar**. +1. Debajo de "Atributos de SAML Configurados", a la derecha de "grupos"; utiliza el menú desplegable y selecciona **Coincidencias de regex**. +1. A la derecha del menú desplegable, teclea `.*.*`. +1. Haz clic en **Save ** (guardar). +{% data reusables.saml.okta-view-setup-instructions %} +1. Habilita SAML para tu cuenta empresarial utilizando la información en las instrucciones de configuración. Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". + +### Crear grupos en Okta + +1. En Okta, crea un grupo para que empate con la organización que pertenezca a tu cuenta empresarial. El nombre de cada grupo debe coincidir con el nombre de cuenta de la organización (no así, con el nombre mostrado de la misma). Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, nombra `octo-org` al grupo. +1. Asigna la aplicación que creaste para tu cuenta empresarial a cada grupo. {% data variables.product.prodname_dotcom %} recibirá todos los datos de los `groups` para cada usuario. +1. Agrega usuarios a los grupos basándote en las organizaciones a las cuales quisieras que pertenezcan dichos usuarios. + +### Configurar el aprovisionamiento de usuarios con SCIM en Okta + +{% data reusables.scim.enterprise-account-scim %} + +Para configurar el aprovisionamiento de usuarios con SCIM en Okta, debes autorizar una aplicación de OAuth para que cree un token que Okta pueda utilizar para autenticarse en {% data variables.product.product_name %} a tu nombre. Okta creó la aplicación okta-oauth en asociación con {% data variables.product.prodname_dotcom %}. + +{% data reusables.saml.okta-admin-button %} +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.click-enterprise-account-application %} +{% data reusables.saml.okta-provisioning-tab %} +{% data reusables.saml.okta-configure-api-integration %} +{% data reusables.saml.okta-enable-api-integration %} +1. Da clic en **Autenticarse con GitHub Enterprise Cloud - Cuentas Empresariales**. ![Botón para autenticarse con {% data variables.product.prodname_dotcom %}](/assets/images/help/business-accounts/authenticate-with-github-button.png) +1. A la derecha del nombre de tu cuenta empresarial, da clic en **Otorgar**. +1. Da clic en **Autorizar a okta-oauth**. +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} +1. Debajo del nombre de la aplicación, da clic en **Grupos de Subida**. ![Pestaña de Grupos de Subida](/assets/images/help/business-accounts/okta-push-groups-tab.png) +1. Utiliza el menú desplegable de **Grupos de Subida** y selecciona **Encontrar grupos por nombre**. ![Menú desplegable de Grupos de Subida](/assets/images/help/business-accounts/okta-push-groups-drop-down.png) +1. Agrega un grupo de subida para cada organización en tu cuenta empresarial en la cual quieras habilitar el aprovisionamiento de usuarios. + - Debajo de "GRUPOS DE SUBIDA POR NOMBRE", busca el grupo que corresponda a una organización que pertenezca a tu cuenta empresarial, luego da clic en el grupo dentro de los resultados de la búsqueda. + - A la derecha del nombre de grupo, en el menú desplegable de "Empatar resultados & acción de subida", verifica que se encuentre seleccionada la opción **Crear Grupo**. ![Menú desplegable con resultados coincidentes para la opción Crear Grupo seleccionada](/assets/images/help/saml/create-group-okta.png) + - Haz clic en **Save ** (guardar). + - Repite esto para cada organización. +1. Debajo del nombre de tu aplicación, da clic en **Tareas**. ![Pestaña de tareas](/assets/images/help/business-accounts/okta-assignments-tab.png) +1. Si ves la opción **Aprovisionar usuarios**, los usuarios que fuesen miembros de un grupo de Okta antes de que agregaras un grupo de subida para este grupo no se han aprovisionado. Para enviar datos de SCIM de estos usuarios a {% data variables.product.product_name %}, da clic en **Aprovisionar usuarios**. + +### Habilitar SAML utilizando el aprovisionamiento + +Después de que habilitas el aprovisionamiento y desaprovisionamiento de SCIM, puedes habilitar opcionalmente el aprovisionamiento y desaprovisionamiento de usuarios de SAML. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Debajo de "Aprovisionamiento de Usuarios de SAML", selecciona **Habilitar el aprovisionamiento de usuarios de SAML**. ![Casilla para habilitar el aprovisionamiento de usuarios con SAML](/assets/images/help/business-accounts/user-provisioning.png) +1. Haz clic en **Save ** (guardar). +1. Opcionalmente, habilita el desaprovisionamiento de usuarios de SAML. + - Selecciona **Habilitar el resaprovisionamiento de usuarios de SAML**, y luego da clic en **Guardar**. ![Casilla para habilitar el desaprovisionamiento de usuarios con SAML](/assets/images/help/business-accounts/saml-deprovisioning.png) + - Lee la advertencia y da clic en **Habilitar el desaprovisionamiento de SAML**. ![Botón para habilitar el desaprovisionamiento de usuarios de SAML](/assets/images/help/business-accounts/saml-deprovisioning-confirm.png) diff --git a/translations/es-ES/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/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md new file mode 100644 index 0000000000000..89a885b9160cc --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md @@ -0,0 +1,21 @@ +--- +title: Configurar el periodo de retención de los artefactos y las bitácoras de las GitHub Actions en tu cuenta empresarial +intro: 'Los propietarios de las empresas pueden configurar el periodo de retención para los artefactos y las bitácoras de las {% data variables.product.prodname_actions %} en una cuenta empresarial.' +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 +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' +--- + +{% data reusables.actions.about-artifact-log-retention %} + +## Configurar el periodo de retención para una empresa + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account.md new file mode 100644 index 0000000000000..2bd642358d440 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account.md @@ -0,0 +1,23 @@ +--- +title: Configurar webhooks para eventos de la organización en tu cuenta de empresa +intro: Los propietarios de empresas pueden configurar webhooks para eventos en organizaciones que son propiedad de una cuenta de empresa. +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/configuring-webhooks-for-organization-events-in-your-business-account/ + - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Puedes configurar webhooks para recibir eventos de organizaciones que son propiedad de tu cuenta de empresa. Para obtener más información acerca de los webhooks, consulta la sección "[Webhooks](/webhooks/)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +4. Al lado de "Webhooks", haz clic en **Add webhook** (Agregar webhook). ![Botón para agregar webhook en la barra lateral Webhooks](/assets/images/help/business-accounts/add-webhook-button.png) +5. Escribe una URL de carga, luego opcionalmente personaliza la configuración. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/#creating-webhooks)". ![Campos para la URL de carga y otras opciones de personalización](/assets/images/help/business-accounts/webhook-payload-url-and-customization-options.png) +6. En "Which events would you like to trigger this webhook?" (¿Qué eventos desaría desencadenar este webhook?), selecciona **Let me select individual events** (Dejarme seleccionar eventos individuales). ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-let-me-select-individual-events.png) +7. Selecciona uno o más eventos de la cuenta de empresa para que reciba tu webhook. Para obtener más información, consulta la sección "[Tipos de eventos y cargas útiles](/webhooks/event-payloads/)". ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-selected-events.png) +8. Para recibir los eventos seleccionados para los webhooks desencadenados, selecciona **Active** (Activar). ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-active.png) +9. Haz clic en **Add webhook** (Agregar webhook). diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..0448ef0e0f9eb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta de empresa +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %}Para obtener más información, consulta "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %}Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %}Si no estás participando en el beta privado, SCIM no será compatible para las cuentas empresariales. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Nota:** Habilitar la autenticación con inicio de sesión único de SAML para tu cuenta de empresa reemplazará cualquier configuración de SAML existente al nivel de la organización. + +{% endnote %} + +Para obtener información más detallada sobre cómo habilitar el SAML utilizando Okta, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "inicio de sesión único SAML", selecciona **Habilitar autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. En el campo **URL de inicio de sesión**, escribe el extremo HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) +8. En **Certificado público**, pega un certificado para verificar las respuestas de SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) +9. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png) +10. Antes de habilitar SAML SSO para tu empresa, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png) +11. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md new file mode 100644 index 0000000000000..b3b4571902dd0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md @@ -0,0 +1,19 @@ +--- +title: Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa +intro: 'En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir o no permitir que los miembros vean la información de dependencias o puedes permitir que los propietarios administren este parámetro a nivel de la organización.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/enforcing-a-policy-on-dependency-insights/ + - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +En las organizaciones que son propiedad de una cuenta de empresa, los propietarios de la organización pueden establecer limitaciones para la visualización de la información de dependencias de la organización. Para obtener más información, consulta "[Cambiar la visibilidad de la información de dependencias de la organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la barra lateral de la cuenta de empresa, haz clic en **Organizaciones**. ![Pestaña Organizaciones en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/settings-policies-org-tab.png) +4. En "Políticas de la organización", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Políticas de la organización", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de la organización](/assets/images/help/business-accounts/organization-policy-drop-down.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md new file mode 100644 index 0000000000000..0b70e28d39f22 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -0,0 +1,48 @@ +--- +title: Requerir las políticas de Github Actions en tu cuenta empresarial +intro: 'Los propietarios de las empresas pueden habilitar, inhabilitar y limitar las {% data variables.product.prodname_actions %} para una cuenta empresarial.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +--- + +### Acerca de los permisos de las {% data variables.product.prodname_actions %} para tu cuenta empresarial + +Predeterminadamente, {% data variables.product.prodname_actions %} se habilita en todas las organizaciones que pertenezcan a una cuenta empresarial. Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para todas las organizaciones que pertenezcan a una cuenta empresarial, o permitirlas únicamente para una organización epecífica. También puedes limitar el uso de acciones públicas, para que las personas solo puedan utilizar acciones locales que existen en tu organización. + +Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". + +### Adminsitrar los permisos de {% data variables.product.prodname_actions %} para tu cuenta empresarial + +Puedes inhabilitar todos los flujos de trabajo de una empresa o configurar una política que configure qué acciones pueden utilizarse en una organización. + +{% data reusables.actions.actions-use-policy-settings %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} +1. Haz clic en **Save ** (guardar). + +### Permitir que se ejecuten acciones específicas + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + +### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configurar la política de bifurcaciones privadas para tu cuenta empresarial + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account.md new file mode 100644 index 0000000000000..7d00a39f9a25f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account.md @@ -0,0 +1,34 @@ +--- +title: Hacer cumplir políticas de tableros de proyecto en tu cuenta de empresa +intro: 'Los propietarios de empresas pueden hacer cumplir determinadas políticas de tableros de proyecto para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que las políticas se establezcan en cada organización.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account/ + - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account/ + - /articles/enforcing-project-board-policies-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Para obtener más información acerca de los tipos de tableros de proyecto, consulta "[Acerca de los tableros de proyecto](/articles/about-project-boards)." + +### Hacer cumplir una política para tableros de proyecto en toda la organización + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar tableros de proyecto en toda la organización o permitir que los propietarios administren este parámetro a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.projects-tab %} +4. En "Proyectos de la organización", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Proyectos de la organización", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de la organización](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png) + +### Hacer cumplir una política para tableros de proyecto de repositorios + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar tableros de proyecto a nivel de los repositorios o permitir que los propietarios administren este parámetro a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.projects-tab %} +4. En "Proyectos de repositorios", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Proyectos de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de repositorios](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md new file mode 100644 index 0000000000000..ab45e32788b55 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md @@ -0,0 +1,89 @@ +--- +title: Hacer cumplir políticas de administración de repositorios para las organizaciones en tu cuenta de empresa +intro: 'Los propietarios de empresas pueden hacer cumplir determinadas políticas de administración de repositorios para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que las políticas se establezcan en cada organización.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account/ + - /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account/ + - /articles/enforcing-repository-management-policies-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". + +### Hacer cumplir una política sobre los permisos de repositorios predeterminados + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes establecer un nivel de permiso predeterminado para los repositorios (ninguno, de lectura, de escritura o de administrador) para los miembros de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +4. En la pestaña **Políticas de repositorios**, en "Permisos predeterminados", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Permisos predeterminados", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de permisos de repositorios](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png) + +### Hacer cumplir una política sobre la creación de repositorios + +En todas las organizaciones que le pertenecen a tu cuenta de empresa, puedes permitir que los miembros creen repositorios, restringir la creación de repositorios para los propietarios de la organización o permitir que los propietarios administren los ajustes en el nivel de la organización. Si permites que los miembros creen repositorios, puedes decidir si pueden crear cualquier combinación de repositorios públicos, privados e internos. {% data reusables.repositories.internal-repo-default %} Para obtener más información acerca de los repositorios internos, consulta "[Crear un repositorio interno](/articles/creating-an-internal-repository)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Creación de repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +{% data reusables.enterprise-accounts.repo-creation-policy %} +{% data reusables.enterprise-accounts.repo-creation-types %} +6. Haz clic en **Save ** (guardar). + +### Requerir una política para bifurcar repositorios privados o internos + +En todas las organizaciones que pertenezcan a tu cuenta empresarial, puedes permitir o prohibir la bifurcación de un repositorio privado o interno o permitir a los propietarios administrar la configuración a nivel organizacional para todos los que tengan acceso a éstos. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Bifurcación de repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +4. En "Bifurcación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de bifurcación de repositorios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png) + +### Hacer cumplir una política sobre la invitación de colaboradores externos a los repositorios + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros inviten colaboradores externos a los repositorios, restringir las invitaciones de colaboradores externos a los propietarios de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Invitaciones a los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +4. Debajo de "Invitaciones a los repositorios", utiliza el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de invitación de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) + +### Hacer cumplir una política sobre cambios en la visibilidad de los repositorios + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador modifiquen la visibilidad de un repositorio, puedes restringir los cambios en la visibilidad del repositorio a los propietarios de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Cambio en la visibilidad de los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +{% data reusables.enterprise-accounts.repository-visibility-policy %} + +### Hacer cumplir una política sobre la eliminación o la transferencia de repositorios + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador eliminen o transfieran un repositorio, puedes restringir la eliminación o la transferencia de repositorios a los propietarios de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Eliminación y transferencia de los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +{% data reusables.enterprise-accounts.repository-deletion-policy %} + +### Hacer cumplir una política sobre la eliminación de propuestas + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador eliminen propuestas en un repositorio, puedes restringir la eliminación de propuestas a los propietarios de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña **Políticas de repositorios**, en "Eliminación de propuestas en los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +4. En "Eliminación de propuestas en los repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de eliminación de propuestas](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png) + +### Requerir una política para el nombre de la rama predeterminada + +Puedes configurar el nombre de la rama predeterminada para cualquier repositorio nuevo que creen los miembros s lo largo de todas las organizaciones que pertenezcan a tu cuenta empresarial. Puedes elegir el requerir un nombre de rama predeterminado a través de todas las organizaciones o permitir a algunas configurar un nombre diferente. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la pestaña de **Políticas de los repositorios**, debajo de "Nombre de la rama predeterminada", ingresa el nombre de rama predeterminada que deberán utilizar los repositorios nuevos. ![Caja de texto para ingresar un nombre de rama predeterminado](/assets/images/help/business-accounts/default-branch-name-text.png) +4. Opcionalmente, para requerir el nombre de rama predeterminado para todas las organizaciones en la empresa, selecciona **Requerir en toda la empresa**. ![Casilla de requerir](/assets/images/help/business-accounts/default-branch-name-enforce.png) +5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/business-accounts/default-branch-name-update.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md new file mode 100644 index 0000000000000..40db124930122 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -0,0 +1,118 @@ +--- +title: Hacer cumplir los parámetros de seguridad en tu cuenta de empresa +intro: Los propietarios de empresa pueden hacer cumplir determinadas políticas de seguridad para todas las organizaciones que son propiedad de una cuenta de empresa. +product: '{% data reusables.gated-features.enterprise-accounts %}' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/enforcing-security-settings-for-organizations-in-your-business-account/ + - /articles/enforcing-security-settings-for-organizations-in-your-enterprise-account/ + - /articles/enforcing-security-settings-in-your-enterprise-account + - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +### Requerir autenticación de dos factores para las organizaciones en tu cuenta de empresa + +Los propietarios de empresa pueden requerir que los miembros de la organización, gerentes de facturación y colaboradores externos en todas las organizaciones que sean propiedad de una cuenta de empresa usen autenticación de dos factores para proteger sus cuentas personales. + +Para requerir la autenticación de dos factores para todas las organizaciones que sean propiedad de tu cuenta de empresa, primero debes habilitar la autenticación de dos factores para tu propia cuenta. Para obtener más información, consulta "[Proteger tu cuenta con la autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)". + +{% warning %} + +**Advertencias:** + +- Cuando requieras que se use la autenticación de dos factores para tu cuenta de empresa, los miembros, los colaboradores externos y los gerentes de facturación (incluidas las cuentas bot) en todas las organizaciones que sean propiedad de tu cuenta de empresa que no utilicen 2FA se eliminarán de tu organización y perderán acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes reinstalar sus privilegios de acceso y sus parámetros de configuración si habilitan la autenticación de dos factores para sus cuentas personales dentro de un plazo de tres meses a partir de su eliminación de tu organización. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". +- Todo propietario de la organización, miembro, gerente de facturación o colaborador externo en cualquiera de las organizaciones que sean propiedad de tu cuenta de empresa será automáticamente eliminado de tu organización si inhabilita la autenticación de dos factores de su cuenta personal una vez que hayas habilitado la autenticación de dos factores requerida. +- Si eres el único propietario de una cuenta de empresa que requiere autenticación de dos factores, no podrás inhabilitar la 2FA para tu cuenta personal sin inhabilitar la autenticación de dos factores requerida para la cuenta de empresa. + +{% endwarning %} + +Antes de solicitar el uso de la autenticación de dos factores, te recomendamos notificar a los miembros de la organización, a los colaboradores externos y a los gerentes de facturación y pedirles que configuren la 2FA para sus cuentas. Los propietarios de la organización pueden ver si los miembros y los colaboradores externos ya usan 2FA en la página Personas de cada organización. Para obtener más información, consulta "[Ver si los usuarios en tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. En "Autenticación de dos factores", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Debajo de "Two-factor authentication" ¨(Autenticación de dos factores), selecciona **Require two-factor authentication for all organizations in your business** (Requerir autenticación de dos factores para todas las organizaciones en tu empresa) y luego haz clic en **Save** (Guardar). ![Casilla de verificación para requerir autenticación de dos factores](/assets/images/help/business-accounts/require-2fa-checkbox.png) +6. Si se lo solicita, lee la información acerca de los miembros y colaboradores externos que serán eliminados de las organizaciones que son propiedad de tu cuenta de empresa. Para confirmar el cambio, escribe el nombre de tu cuenta de empresa y luego haz clic en **Eliminar miembros y requerir autenticación de dos factores**. ![Cuadro Confirmar aplicación obligatoria de dos factores](/assets/images/help/business-accounts/confirm-require-2fa.png) +7. Si algún miembro o colaborador externo es eliminado de las organizaciones que son propiedad de tu cuenta de empresa, también te recomendamos enviarle una invitación para reinstalar sus privilegios anteriores y su acceso a tu organización. Cada persona debe habilitar la autenticación de dos factores para poder aceptar tu invitación. + +### Administrar direcciones IP permitidas para organizaciones en su cuenta de empresa + +Los propietarios de empresa pueden restringir el acceso a los activos que pertenezcan a las organizaciones dentro de la cuenta empresarial mediante la configuración de una lista de direcciones IP permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} + +{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} + +{% data reusables.identity-and-permissions.ip-allow-lists-enable %} + +También puedes configurar las direcciones IP permitidas para una organización individual. Para obtener más información, consulta "[Administrar las direcciones IP permitidas en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". + +#### Agregar una dirección IP permitida + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-description %} +{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} + +#### Habilitar direcciones IP permitidas + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +3. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) +4. Haz clic en **Save ** (guardar). + +#### Editar una dirección IP permitida + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} +{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %} +8. Da clic en **Actualizar**. + +#### Eliminar una dirección IP permitida + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} +{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %} + +#### Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +### Administrar las autoridades de los certificados de SSH de tu cuenta de empresa + +Los propietarios de empresa pueden agregar y eliminar las autoridades de los certificados de SSH de una cuenta de empresa (CA). + +Al agregar una CA de SSH a tu cuenta de empresa, puedes permitir que los miembros de cualquier organización que sea propiedad de tu cuenta de empresa acceda a los repositorios de esa organización usando los certificados de SSH proporcionados por ti. {% data reusables.organizations.can-require-ssh-cert %}Para obtener más información, consulta "[Acerca de las autoridades de certificados de SSH](/articles/about-ssh-certificate-authorities)". + +#### Agregar una autoridad de certificado de SSH + +{% data reusables.organizations.add-extension-to-cert %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.organizations.new-ssh-ca %} +{% data reusables.organizations.require-ssh-cert %} + +#### Eliminar una autoridad de certificado de SSH + +La eliminación de un CA no se puede deshacer. Si deseas usar la misma CA en el futuro, deberás cargarla nuevamente. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.organizations.delete-ssh-ca %} + +### Further reading + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md new file mode 100644 index 0000000000000..908fca70be035 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -0,0 +1,22 @@ +--- +title: Hacer cumplir políticas de equipo en tu cuenta de empresa +intro: 'Los propietarios de empresa pueden hacer cumplir determinadas políticas de equipo para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que estas políticas se establezcan en cada organización.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/enforcing-team-settings-for-organizations-in-your-business-account/ + - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account/ + - /articles/enforcing-team-policies-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +### Hacer cumplir una política para los debates de equipo + +En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar los debates de equipo o permitir que los propietarios administren este parámetro a nivel de la organización. Para obtener más información, consulta [Acerca de los debates de equipo](/articles/about-team-discussions)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +3. En la barra lateral de la cuenta de empresa, haz clic en **Equipos**. ![Pestaña Equipos en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/settings-teams-tab.png) +4. En "Debates de equipo", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Debates de equipo", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de debate de equipo](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md new file mode 100644 index 0000000000000..e45867ba9057b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md @@ -0,0 +1,47 @@ +--- +title: Configurar y administrar tu empresa +shortTitle: Tu empresa +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account + - /categories/setting-up-and-managing-your-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-your-enterprise-account %} + {% link_in_list /about-enterprise-accounts %} + {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} + {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} +{% topic_link_in_list /managing-users-in-your-enterprise %} + {% link_in_list /roles-in-an-enterprise %} + {% link_in_list /inviting-people-to-manage-your-enterprise %} + {% link_in_list /viewing-people-in-your-enterprise %} + {% link_in_list /viewing-and-managing-a-users-saml-access-to-your-enterprise %} +{% topic_link_in_list /managing-organizations-in-your-enterprise-account %} + {% link_in_list /adding-organizations-to-your-enterprise-account %} + {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} + {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} +{% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} + {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} + {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} + {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} + {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} + {% link_in_list /verifying-your-enterprise-accounts-domain %} + {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} + {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} + {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} + {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md new file mode 100644 index 0000000000000..e7c60e812c522 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -0,0 +1,44 @@ +--- +title: Invitar a las personas para que administren tu empresa +intro: Puedes invitar a personas a que se vuelvan propietarios de empresa o administradores de facturación en tu cuenta de empresa. También puedes eliminar propietarios de empresa o administradores de facturación que no necesiten seguir teniendo acceso a la cuenta de empresa. +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account + - /articles/inviting-people-to-collaborate-in-your-business-account/ + - /articles/inviting-people-to-manage-your-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de invitar a personas a administrar tu cuenta de empresa + +{% data reusables.enterprise-accounts.enterprise-administrators %} Para obtener más información, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". + +{% tip %} + +**Sugerencia:**Para obtener más información acerca de administrar usuarios dentro de una organización que le pertenece a tu cuenta de empresa, consulta "[Administrar membresías de tu organización](/articles/managing-membership-in-your-organization)" y "[Administrar el acceso de personas a tu organización con roles](/articles/managing-peoples-access-to-your-organization-with-roles)." + +{% endtip %} + +### Invitar a un administrador de empresa a tu cuenta de empresa + +Solo los propietarios de empresa pueden invitar a otras personas a que se conviertan en administradores de empresa. + +Después de que invites a alguna persona a que se una a la cuenta de empresa, esta debe aceptar la invitación enviada por correo electrónico antes de poder acceder a la cuenta de empresa. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +3. En la barra lateral izquierda, haz clic en **Administrators** (Administradores). ![Pestaña Administrators (Administradores) en la barra lateral izquierda](/assets/images/help/business-accounts/administrators-tab.png) +4. Arriba de la lista de administradores, haz clic en **Invite admin** (Invitar administrador). ![Botón Invite admin (Invitar administrador) arriba de la lista de propietarios de empresa](/assets/images/help/business-accounts/invite-admin-button.png) +5. Escribe el nombre de usuario, el nombre completo o la dirección de correo electrónico de la persona a la que quieres invitar a que se convierta en administrador de empresa, luego selecciona la persona adecuada en los resultados. ![Casilla modal con campo para escribir el nombre de usuario, el nombre completo o la dirección de correo electrónico de una persona y botón Invite (Invitar)](/assets/images/help/business-accounts/invite-admins-modal-button.png) +6. Selecciona **Owner** (Propietario) o **Billing Manager** (Gerente de facturación). ![Casilla modal con opciones de roles](/assets/images/help/business-accounts/invite-admins-roles.png) +7. Haz clic en **Send Invitation** (Enviar invitación). ![Botón Send invitation (Enviar invitación)](/assets/images/help/business-accounts/invite-admins-send-invitation.png) + +### Eliminar un administrador de empresa de tu cuenta de empresa + +Solo los propietarios de empresa pueden eliminar a otros administradores de empresa de la cuenta de empresa. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +3. Junto al nombre de usuario de la persona que quieres eliminar, haz clic en {% octicon "gear" aria-label="The Settings gear" %}, luego haz clic en **Remove owner** (Eliminar propietario) o **Remove billing manager** (Eliminar gerente de facturación). ![Parámetros con opción del menú para eliminar un administrador de empresa](/assets/images/help/business-accounts/remove-admin.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md new file mode 100644 index 0000000000000..4b987ae4788f2 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -0,0 +1,48 @@ +--- +title: Administrar las licencias para la suscripción a Visual Studio con GitHub Enterprise +intro: 'Puedes administrar las licencias 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 +versions: + free-pro-team: '*' +--- + +### Acerca de {% data variables.product.prodname_vss_ghe %} + +{% data variables.product.prodname_vss_ghe %} es una oferta combinada de Microsoft que permite a los suscriptores utilizar tanto {% data variables.product.prodname_enterprise %} como {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} se encuentra disponible desde Microsoft bajo las condiciones del Acuerdo Empresarial de Microsoft. Para obtener más información, consulta la sección [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) en el sitio web de {% data variables.product.prodname_vs %}. + +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. + +Para obtener más información acerca de {% data variables.product.prodname_enterprise %}, consulta los productos de "[{% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)." Para obtener más información acerca de las cuentas en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". + +### Prerrequisitos + +1. Después de que compres {% data variables.product.prodname_vss_ghe %}, contacta a {% data variables.contact.contact_enterprise_sales %} y menciona "{% data variables.product.prodname_vss_ghe %}". El equipo de ventas te ayudará para crear una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. Si ya tienes una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}, o si no estás seguro de ello, por favor, comunícaselo a nuestro equipo de ventas. + +2. Asigna licencias de {% data variables.product.prodname_vss_ghe %} a los suscriptores en {% data variables.product.prodname_vss_admin_portal_with_url %}. Para obtener más información acerca de la asignación de licencias, consulta la sección [Administrar las suscripciones de {% data variables.product.prodname_vs %} con {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/assign-github) en los documentos de Microsoft. + +3. En {% data variables.product.prodname_dotcom_the_website %}, crea por lo menos una organización que pertenezca a tu cuenta empresarial. Para obtener más información, consulta la sección "[Agregar organizaciones a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)". + +### Invitar a un suscriptor para que utilice {% data variables.product.prodname_enterprise %} + +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." + +### Visualizar el licenciamiento de {% data variables.product.prodname_enterprise %} + +Después de asignar una licencia para {% data variables.product.prodname_vss_ghe %} en el {% data variables.product.prodname_vss_admin_portal_with_url %}, puedes ver la cantidad de licencias de {% data variables.product.prodname_enterprise %} que están disponibles para tu cuenta empresarial. Para obtener más información, consulta "[Ver la suscripción y el uso de tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)". + +También puedes ver las invitaciones pendientes de {% data variables.product.prodname_enterprise %} para los suscriptores en {% data variables.product.prodname_vss_admin_portal_with_url %}. La lista de invitaciones pendientes incluye a los suscriptores que aún no son miembros de por lo menos una organización en tu cuenta empresarial. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)". + +### Further reading + +- [Introducir las suscripciones de Visual Studio con GitHub enterprise](https://docs.microsoft.com/visualstudio/subscriptions/access-github) en los documentos de Microsoft diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..de9fdeb9b6041 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md @@ -0,0 +1,11 @@ +--- +title: Administrar organizaciones en tu cuenta de empresa +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: verdadero +redirect_from: + - /articles/managing-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..dea1d2cf35586 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +También puedes configurar y administrar la sincronización de equipos para una organización individual. Para obtener más información, consulta la sección [Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)". + +### Prerrequisitos + +Tú o tu administrador de Azure AD debe ser un administrador global o un administrador de Rol Privilegiado en Azure AD. + +Debes habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial con tu IdP compatible. Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". + +Debes autenticarte en tu cuenta empresarial utilizando el SSO de SAML y el IdP compatible. Para obtener más información, consulta "[Acerca de la autenticación con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)". + +### Administrar la sincronización de equipos para Azure AD + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) +8. Para inhabilitar la sincronización de equipos, da clic en **Inhabilitar la sincronización de equipos**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..3c3ea187fc606 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -0,0 +1,17 @@ +--- +title: Administrar las organizaciones que no te pertenecen en tu cuenta empresarial +intro: Puedes convertirte en propietario de una organización en tu cuenta empresarial si ésta no tiene propietarios actualmente. +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Los propietarios de las empresas pueden adminsitrar organizaciones sin propietario en una cuenta empresarial. +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Si habilitas el desaprovisionamiento de usuarios para administrar las membrecías organizacionales en tu cuenta empresarial, podrías terminar teniendo una organización que no tiene propietarios. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +{% data reusables.enterprise-accounts.access-enterprise %} +2. A la derecha del campo de búsqueda, da clic en **X sin propietario**. ![Botón para ver las organizaciones sin propietario](/assets/images/help/business-accounts/unowned-organizations-button.png) +3. A la derecha de la organización sobre la cual quieres asumirte como propietario, da clic en **Convertirte en propietario**. ![Botón de convertirte en propietario](/assets/images/help/business-accounts/become-an-owner-button.png) +4. Lee la advertencia y luego da clic en **Convertirte en propietario**. ![Botón de convertirte en propietario](/assets/images/help/business-accounts/become-an-owner-confirmation.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md new file mode 100644 index 0000000000000..8094618c1fb93 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md @@ -0,0 +1,15 @@ +--- +title: Administrar los usuarios en tu empresa +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: verdadero +redirect_from: + - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account + - /articles/managing-users-in-your-enterprise-account + - /articles/managing-users-in-your-enterprise +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md new file mode 100644 index 0000000000000..45fa8db88a0cc --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md @@ -0,0 +1,11 @@ +--- +title: Administrar tu cuenta de empresa +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: verdadero +redirect_from: + - /articles/managing-your-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md new file mode 100644 index 0000000000000..fbe61e9c95ac6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -0,0 +1,26 @@ +--- +title: Restringir las notificaciones de correo electrónico para tu cuenta empresarial a los dominios aprobados +intro: "Puedes prevenir que exista una fuga de la información de tu empresa en las cuentas personales si restringes las notificaciones de correo electrónico sobre la actividad en las organizaciones que le pertenecen a tu cuenta empresarial para que solo se acepten los dominios verificados." +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +permissions: Los propietarios de las empresas pueden restringir las notificaciones por correo electrónico para una cuenta empresarial. +--- + +{% data reusables.enterprise-accounts.verifying-domains-release-phase %} + +### Acerca de las restricciones para tu cuenta empresarial + +Cuando restringes las notificaciones por correo electrónico para los dominios verificados, los miembros empresariales solo pueden utilizar la dirección de correo electrónico asociada con un dominio verificado para recibir notificaciones por este medio sobre la actividad en las organizaciones que le pertenezcan a tu cuenta empresarial. Los dominios se pueden heredar desde la cuenta empresarial, o los puedes configurar una organización específica. Para obtener más información sobre las restricciones de correo electrónico para las organizaciones, consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)". + +Si se habilitan las restricciones de correo electrónico para una cuenta empresarial, los propietarios de la organización no las pueden inhabilitar para ninguna organización que pertenezca a la cuenta empresarial. Si ocurre cualquier cambio que dé como resultado que una organización tenga dominios sin verificar, ya se que los herede de una cuenta empresarial que sea propietaria de la organización o que se configuren para la organización específica, las restricciones por correo electrónico se ihabilitarán para dicha organización. + +### Restringir las notificaciones por correo electrónico para tu cuenta empresarial + +Antes de que puedas restringir las notificaciones por correo electrónico para tu cuenta empresarial, debes verificar por lo menos un dominio para esta. Para obtener más información, consulta la sección "[Verificar el dominio de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.verified-domains-tab %} +{% data reusables.organizations.restrict-email-notifications %} +1. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md new file mode 100644 index 0000000000000..299ab8364ea34 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -0,0 +1,61 @@ +--- +title: Roles en una empresa +intro: 'Todas las personas en una empresa son miembros de ella. Para controlar el acceso a los datos y configuraciones de tu empresa, puedes asignar roles diferentes a los miembros de ella.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account + - /articles/permission-levels-for-a-business-account/ + - /articles/roles-for-an-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los roles en una empresa + +Todas las personas en una empresa son miembros de ella. También puedes asignar roles administrativos a los miembros de tu empresa. Cada rol de admnistrador mapea las funciones de negocio y proporciona permisos para llevar a cabo tareas específicas dentro de la empresa. + +{% data reusables.enterprise-accounts.enterprise-administrators %} + +Para obtener más información acerca de agregar personas a tu empresa, consulta la sección "{% if currentVersion == "free-pro-team@latest" %}[Invitar personas para administrar tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Autenticación](/admin/authentication){% endif %}". + +### Propietario de empresa + +Los propietarios de las empresas tienen el control absoluto de las mismas y pueden tomar todas las acciones, incluyendo: +- Gestionar administradores +- {% if currentVersion == "free-pro-team@latest" %}Agregar y eliminar {% elsif currentVersion == "github-ae@latest" %}Administrar{% endif %} organizaciones{% if currentVersion == "free-pro-team@latest" %}to and from {% elsif currentVersion == "github-ae@latest" %} en{% endif %} la empresa +- Administrar parámetros de la empresa +- Aplicar políticas en las organizaciones +{% if currentVersion == "free-pro-team@latest" %}- Administrar la configuración de facturación{% endif %} + +Los propietarios de empresa no pueden acceder a los parámetros o el contenido de la organización, a menos que se conviertan en propietarios de la organización o que se les otorgue acceso directo al repositorio que le pertenece a una organización. De forma similar, los propietarios de las organizaciones en tu empresa no tienen acceso a la empresa misma a menos de que los conviertas en propietarios de ella. + +Puedes agregar tantos propietarios de la empresa como quieras. {% if currentVersion == "free-pro-team@latest" %}Los propietrios de la empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.{% endif %} Como mejor práctica, te recomendamos que solo algunas personas en tu compañía se conviertan en propietarios, para reducir el riesgo en tu negocio. + +### Miembros de empresa + +Los miembros de las organizaciones que pertenezcan a tu empresa también son miembros de ella automáticamente. Los miembros pueden colaborar en las organizaciones y pueden ser dueños de éstas, pero no pueden configurar ni acceder a los ajustes empresariales{% if currentVersion == "free-pro-team@latest" %}, including billing settings{% endif %}. + +Las personas en tu empresa podrían tener niveles de acceso diferentes para las diversas organizaciones que pertenecen a tu empresa y para los repositorios dentro de ellas. Puedes ver los recursos a los que tiene acceso cada persona. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)". + +Para obtener más información acerca de los permisos al nivel de la organización, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". + +Las personas con acceso de colaborador externo a los repositorios que pertenecen a tu organización también se listan en la pestaña de "Personas" de tu empresa, pero no son miembros empresariales y no tienen ningún tipo de acceso a la empresa. Para obtener más información sobre los colaboradores externos, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". + +{% if currentVersion == "free-pro-team@latest" %} + +### Gerente de facturación + +Los gerentes de facturación solo tienen acceso a la configuración de facturación de tu empresa. Los gerentes de facturación de tu empresa pueden: +- Ver y administrar las licencias de usuario, {% data variables.large_files.product_name_short %} los paquetes y otros parámetros de facturación +- Ver una lista de gerentes de facturación +- Agregar o eliminar otros gerentes de facturación + +Los gerentes de facturación no tienen acceso a las organizaciones o repositorios de tu empresa y no pueden agregar o eliminar propietarios de la misma. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. + +### Further reading + +- "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)" + +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..b5235864ce11d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,11 @@ +--- +title: Establecer políticas para organizaciones en tu cuenta de empresa +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: verdadero +redirect_from: + - /articles/setting-policies-for-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md new file mode 100644 index 0000000000000..315afe5516887 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -0,0 +1,42 @@ +--- +title: Verificar el dominio de tu cuenta empresarial +intro: 'Puedes confirmar la identidad de las organizaciones que le pertenecen a tu cuenta empresarial si verificas la propiedad de tus nombres de dominio con {% data variables.product.company_short %}.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +permissions: Los propietarios de las empresas pueden verificar los dominios de su cuenta empresarial. +redirect_from: + - /github/articles/verifying-your-enterprise-accounts-domain + - /early-access/github/articles/verifying-your-enterprise-accounts-domain +--- + +{% data reusables.enterprise-accounts.verifying-domains-release-phase %} + +### Acerca de la verificación de dominios + +Puedes confirmar que tu empresa controle los sitios web y direcciones de correo electrónico que se listan en los perfiles de cualquier organización que le pertenezca a tu cuenta empresarial si verificas los dominios. Los dominios que se verifiquen para una cuenta empresarial aplicarán a todas las organizaciones que le pertenezcan a dicha cuenta, y los propietarios de las organizaciones podrán verificar dominios adicionales para éstas. Para obtener más información, consulta la sección "[Verificar el dominio de tu organización](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)". + +Después de que verificas la propiedad de los dominios de tus cuentas empresariales, se mostrará una insignia de "Verificado" en el perfil de cada organización que liste el dominio en su perfil. {% data reusables.organizations.verified-domains-details %} + +Los propietarios de las organizaciones podrán verificar la identidad de los miembros de éstas si visualizan la dirección de correo electrónico de cada miembro dentro del dominio verificado. + +Después de que verificas los dominios para tu cuenta empresarial, puedes restringir las notificaciones de correo electrónico a los dominios verificados para todas las organizaciones que le pertenezcan a tu cuenta empresarial. Para obtener más información, consulta la sección "[Restringir las notificaciones de correo electrónico para tu cuenta empresarial a los dominios aprobados](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)". + +Incluso si no restringieras las notificaciones para la cuenta empresarial, si un propietario de la organización restringió las notificaciones de correo electrónico para ella, sus miembros podrán recibir notificaciones de cualquier dominio verificado para la cuenta empresarial, adicionalmente a cualquier dominio verificado para la organización. Para obtener más información acerca de la restricción de notificaciones para una organización, consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)". + +### Verificar el dominio de tu cuenta empresarial + +Para verificar el dominio de tu cuenta empresarial, debes tener acceso para modificar los registros del dominio con tu servicio de hospedaje de dominios. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.verified-domains-tab %} +1. Haz clic en **Add a domain (Agregar un dominio)**. ![Botón para agregar un dominio](/assets/images/help/enterprises/add-a-domain-button.png) +{% data reusables.organizations.add-domain %} +{% data reusables.organizations.add-dns-txt-record %} +1. Espera a que cambie la configuración de tu DNS, lo cual puede llevar hasta 72 horas. Puedes confirmar que tu configuración de DNS cambió si ejecutas el comando `dig` en la línea de comandos, reemplazando `ENTERPRISE-ACCOUNT` con el nombre de tu cuenta empresarial, y `example.com` con el dominio que te gustaría verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando. + ```shell + dig _github-challenge-ENTERPRISE-ACCOUNT.example.com +nostats +nocomments +nocmd TXT + ``` +{% data reusables.organizations.continue-verifying-domain %} +1. Opcionalmente, después de que la insignia de "Verificado" se pueda ver en el perfil de tus organizaciones, borra la entrada de TxT del registro de DNS en tu servicio de hospedaje de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md new file mode 100644 index 0000000000000..7235d6935c182 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -0,0 +1,54 @@ +--- +title: Visualizar y administrar el acceso de SAML de un usuario a tu empresa +intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la empresa, sesiones activas y credenciales autorizadas.' +permissions: Los propietarios de empresa pueden ver y administrar el acceso de SAML para los miembros en las organizaciones. +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account +versions: + free-pro-team: '*' +--- + +### Acerca del acceso de SAML a tu cuenta empresarial + +Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial, cada miembro de la empresa puede vincular su identidad externa en tu proveedor de identidad (IdP) para su cuenta existente de {% data variables.product.product_name %}. {% data reusables.saml.about-saml-access-enterprise-account %} + +### Visualizar y revocar una identidad vinculada + +{% data reusables.saml.about-linked-identities %} + +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} + +### Visualizar y revocar una sesión activa de SAML + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} + +### Visualizar y revocar credenciales autorizadas + +{% data reusables.saml.about-authorized-credentials %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} + +### Further reading + +- "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md new file mode 100644 index 0000000000000..aaf59f61fcfb4 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md @@ -0,0 +1,38 @@ +--- +title: Visualizar a las personas en tu empresa +intro: 'Para auditar el acceso a los recursos que pertenezcan a tu empresa o al uso de licencias de usuario, los propietarios de la empresa pueden ver a cada administrador y miembro de la misma.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account + - /articles/viewing-people-in-your-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Visualizar a los propietarios{% if currentVersion == "free-pro-team@latest" %} y gerentes de facturación de la empresa{% endif %} + +Puedes ver a los propietarios {% if currentVersion == "free-pro-team@latest" %}y gerentes de facturación de la empresa, {% endif %}así como una lista de invitaciones pendientes para convertirse en propietarios{% if currentVersion == "free-pro-team@latest" %} y gerentes de facturación. Puedes filtrar la lista de administradores de la empresa por rol{% endif %}. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre completo. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.enterprise-accounts.administrators-tab %} +{% if currentVersion == "free-pro-team@latest" %}1. Opcionalmente, para ver una lista de invitaciones pendientes, da clic en **_CANTIDAD_ pendientes**. + ![botón de "CANTIDAD pendientes" a la derecha de las opciones de búsqueda y de filtrado](/assets/images/help/enterprises/administrators-pending.png){% endif %} + +### Ver miembros y colaboradores externos + +Puedes ver la cantidad de miembros y colaboradores externos pendientes. Puedes filtrar la lista de miembros por {% if currentVersion == "free-pro-team@latest" %}lanzamiento ({% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %}),{% endif %}rol {% if currentVersion == "free-pro-team@latest" %}, y{% elsif currentVersion == "github-ae@latest" %}u {% endif %}organización. Puedes filtrar la lista de colaboradores externos por la visibilidad de los repositorios a los que el colaborador tiene acceso. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre que se muestra. + +Puedes ver {% if currentVersion == "free-pro-team@latest" %}todas las organizaciones de {% data variables.product.prodname_ghe_cloud %} e instancias de {% data variables.product.prodname_ghe_server %} a las cuales pertenece un miembro, y {% endif %}a qué repositorios tiene acceso un colaborador externo{% if currentVersion == "free-pro-team@latest" %}, {% endif %} dand clic en el nombre de una persona. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +1. De manera opcional, para ver una lista de colaboradores externos en lugar de una lista de miembros, haz clic en **Outside collaborators (Colaboradores externos)**. ![Pestaña de colaboradores externos en la página de miembros de la organización](/assets/images/help/business-accounts/outside-collaborators-tab.png) +{% if currentVersion == "free-pro-team@latest" %}1. Opcionalmente, para ver una lista de invitaciones pendientes, da clic en **_CANTIDAD_ pendientes**. + ![botón de "CANTIDAD pendientes" a la derecha de las opciones de búsqueda y de filtrado](/assets/images/help/enterprises/members-pending.png){% endif %} + +### Further reading + +- "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..22e1a8d68edfa --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,26 @@ +--- +title: Ver los registros de auditoría para organizaciones en tu cuenta de empresa +intro: Los propietarios de la empresa pueden ver accciones acumuladas de todas las organizaciones propiedad de una cuenta de empresa en su registro de auditoría. +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account/ + - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account +versions: + free-pro-team: '*' +--- + +Cada entrada del registro de auditoría muestra información vigente acerca de un evento, como: + +- La organización en la que se realizó una acción +- El usuario que realizó la acción +- En qué repositorio se realizó una acción +- La acción que se realizó +- En qué país se realizó la acción +- La fecha y hora en que se produjo la acción + +Puedes buscar el registro de auditoría para eventos específicos y exportar los datos del registro de auditoría. Para obtener más información acerca de buscar el registro de auditoría y eventos en una organización específica, consulta "[Revisar el registro de auditoría para tu organización](/articles/reviewing-the-audit-log-for-your-organization)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md new file mode 100644 index 0000000000000..34bd29c3470dd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -0,0 +1,29 @@ +--- +title: Ver la suscripción y el uso de tu cuenta de empresa +intro: 'Puedes ver la suscripción actual, el uso de la licencia, las facturas, el historial de pagos y otra información de facturación de tu cuenta de empresa.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: 'Los propietarios de la empresa y los gerente de facturación pueden acceder y administrar todas las configuraciones de facturación para las cuentas de empresa.' +redirect_from: + - /github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account + - /articles/viewing-the-subscription-and-usage-for-your-enterprise-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de la facturación para las cuentas de empresa + +Las cuentas empresariales actualmente están disponibles para los clientes de {% data variables.product.prodname_enterprise %} que pagan por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas con tu cuenta empresarial se conjunta en un solo cargo por factura para todos tus servicios pagados de {% data variables.product.prodname_dotcom_the_website %} (incluyendo las licencias pagadas en organizaciones, paquetes de datos de {% data variables.large_files.product_name_long %}, y suscripciones a las apps de {% data variables.product.prodname_marketplace %}). + +Para obtener más información acerca de administrar a los gerentes de facturación, consulta la sección "[Invitar a las personas a administrar tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +### Ver la suscripción y el uso de tu cuenta de empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Debajo de +"{% if currentVersion == "free-pro-team@latest" %}Licencias{% else %}licencias{% endif %}de usuario", visualiza el total de tus licencias, cantidad de licencias utilizadas, y la fecha de vencimiento de tu suscripción. + {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} + ![Información de licencia y suscripción en las configuraciones de facturación de la empresa](/assets/images/enterprise/enterprises/enterprise-server-billing-license-info.png){% endif %} +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md new file mode 100644 index 0000000000000..a2c854f530851 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -0,0 +1,24 @@ +--- +title: Acerca del perfil de tu organización +intro: La página del perfil de tu organización muestra la información básica acerca de tu organización. +redirect_from: + - /articles/about-your-organization-s-profile + - /articles/about-your-organizations-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Opcionalmente, puedes optar por agregar una descripción, una ubicación, un sitio web y una dirección de correo electrónico para tu organización y anclar repositorios importantes en la parte superior de la página. + +{% if currentVersion == "free-pro-team@latest" %}Para confirmar la identidad de tu organización y mostrar una insignia de "Verificado" en la página de perfil de la misma, debes verificar sus dominios con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar el dominio de tu organización](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)". + +![Muestra de página de perfil de una organización verificada](/assets/images/help/profile/org_profile_verified.png) +{% else %} +![Muestra de la página de perfil de una organización](/assets/images/help/profile/org_profile.png) +{% endif %} + +### Further reading + +- "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md new file mode 100644 index 0000000000000..67b00dd7a4803 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md @@ -0,0 +1,39 @@ +--- +title: Acerca de tu perfil +intro: 'La página de tu perfil le cuenta a las personas la historia de tu trabajo a través de los repositorios en los que te interesas, las colaboraciones que has realizado y las conversaciones que has tenido.' +redirect_from: + - /articles/viewing-your-feeds/ + - /articles/profile-pages/ + - /articles/about-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes agregar información personal acerca de ti mismo en tu biobiografía, como lugares en los que has trabajado previamente, proyectos con los que has colaborado o intereses que tengas que a otras personas les pueda interesar conocer sobre tí. Para obtener más información, consulta "[Agregar una biografía en tu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + +{% data reusables.profile.profile-readme %} + +![Archivo de README del perfil que se muestra en éste](/assets/images/help/repository/profile-with-readme.png) + +{% endif %} + +Las personas que visitan tu perfil ven una cronología de tu actividad de colaboración, como las propuestas y las solicitudes de extracción que has abierto, las confirmaciones que has realizado y las solicitudes de extracción que has revisado. Puedes elegir mostrar solo las contribuciones públicas o también incluir las contribuciones privadas, anonimizadas. Para obtener más información, consulta "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" o "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". + +Las personas que visitan tu perfil también pueden ver la siguiente información. + +- Repositorios y gists que te pertenezcan o en los que contribuyas. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Puedes mostrar tu mejor trabajo si fijas los repositorios y gists a tu perfil. Para obtener más información, consulta la sección "[Anclar elementos en tu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %} +- Repositorios que has destacado. Para obtener más información, consulta la sección "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)". +- Una descripción general de tu actividad en organizaciones, repositorios y equipos en los que eres más activo. Para obtener más información, consulta la sección "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile).{% if currentVersion == "free-pro-team@latest" %} +- Las insignias que muestran si utilizas {% data variables.product.prodname_pro %} o si participas en programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, o el programa de desarrollador de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %} + +También puedes establecer un estado en tu perfil para brindar información sobre tu disponibilidad. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". + +### Further reading + +- "[¿Cómo configuro mi foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)" +- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md new file mode 100644 index 0000000000000..c6cab2efbecb0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md @@ -0,0 +1,12 @@ +--- +title: Personalizar tu perfil +intro: Puedes personalizar tu perfil para que los demás usuarios puedan comprender mejor quién eres y qué trabajo realizas. +mapTopic: verdadero +redirect_from: + - /articles/customizing-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/index.md new file mode 100644 index 0000000000000..b6bdeb92441de --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/index.md @@ -0,0 +1,27 @@ +--- +title: Configurar y administrar tu perfil de GitHub +shortTitle: Perfiles +redirect_from: + - /categories/setting-up-and-managing-your-github-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /customizing-your-profile %} + {% link_in_list /about-your-profile %} + {% link_in_list /about-your-organizations-profile %} + {% link_in_list /personalizing-your-profile %} + {% link_in_list /managing-your-profile-readme %} + {% link_in_list /pinning-items-to-your-profile %} +{% topic_link_in_list /managing-contribution-graphs-on-your-profile %} + {% link_in_list /viewing-contributions-on-your-profile %} + {% link_in_list /showing-an-overview-of-your-activity-on-your-profile %} + {% link_in_list /publicizing-or-hiding-your-private-contributions-on-your-profile %} + {% link_in_list /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile %} + {% link_in_list /why-are-my-contributions-not-showing-up-on-my-profile %} + {% link_in_list /troubleshooting-commits-on-your-timeline %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md new file mode 100644 index 0000000000000..7e3757c63beb5 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md @@ -0,0 +1,12 @@ +--- +title: Administrar los gráficos de contribución en tu perfil +intro: 'Tus contribuciones, incluidas las confirmaciones de cambios, las solicitudes de extracción propuestas y las propuestas abiertas, se muestran en tu perfil para que las personas puedan ver fácilmente el trabajo que has realizado.' +mapTopic: verdadero +redirect_from: + - /articles/managing-contribution-graphs-on-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md new file mode 100644 index 0000000000000..1b91eed783018 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -0,0 +1,64 @@ +--- +title: Administrar el README de tu perfil +intro: 'Puedes agregar un README a tu perfil de {% data variables.product.prodname_dotcom %} para que otras personas sepan sobre ti.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Acerca del README de tu perfil + +Puedes compartir información acerca de ti mismo con la comunidad en {% data variables.product.prodname_dotcom %} si creas un README para tu perfil. {% data variables.product.prodname_dotcom %} muestra el README de tu perfil al inicio de tu página de perfil. + +Tú decides qué información incluir en el README de tu perfil, así que tienes todo el contro sobre cómo te presentas con los demás en {% data variables.product.prodname_dotcom %}. Aquí tienes algunos ejemplos de información que puede ser interesante, divertida o útil para los visitantes que lean el README en tu perfil. + +- Una sección de "sobre mí" que describa tu trabajo y tus intereses +- Las contribuciones de las cuales estás orgulloso y el contexto de las mismas +- Orientación para obtener ayuda en las comunidades en las que estás involucrado + +![Archivo de README del perfil que se muestra en éste](/assets/images/help/repository/profile-with-readme.png) + +Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README de tu perfil si utilizas el Marcado Enriquecido de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)". + +### Prerrequisitos + +GitHub mostrará el README de tu perfil en tu página de perfil si cuentas con todo lo siguiente. + +- Has creado un repositorio con un nombre que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}. +- Este repositorio es público. +- Este repositorio contiene un archivo de nombre README.md en su raíz. +- El archivo README.md contiene cualquier tipo de contenido. + +{% note %} + +**Nota**: Si creaste un repositorio público con el mismo nombre de tu nombre de usuario antes de julio del 2020, {% data variables.product.prodname_dotcom %} no mostrará automáticamente el README de tu repositorio en tu perfil. Puedes compartir manualmente el README de tu repositorio en tu perfil si te diriges al repositorio en {% data variables.product.prodname_dotcom_the_website %} y das clic en **Compartir en mi perfil**. + +![Botón para compartir el README en el perfil](/assets/images/help/repository/share-to-profile.png) + +{% endnote %} + +### Agregar un README de perfil + +{% data reusables.repositories.create_new %} +2. Debajo de "Nombre de repositorio", teclea un nombre de repositorio que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}. Por ejemplo, si tu nombre de usuario es "octocat", el nombre de repositorio debe ser "octocat". ![Campo de nombre de repositorio que empata con el nombre de usuario](/assets/images/help/repository/repo-username-match.png) +3. También puedes agregar una descripción de tu repositorio. Por ejemplo, "Mi repositorio personal". ![Campo para ingresar una descripción para el repositorio](/assets/images/help/repository/create-personal-repository-desc.png) +4. Selecciona **Público**. ![Botón radial para seleccionar la visibilidad con la opción de público seleccionada](/assets/images/help/repository/create-personal-repository-visibility.png) +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} +7. Sobre la barra lateral derecha, da clic en **Editar README**. ![Botón para editar el archivo README](/assets/images/help/repository/personal-repository-edit-readme.png) + + El archivo de README que se ha generado está pre-llenado con una plantilla para que te inspires en completarlo. ![Archivo README con la plantilla pre-llenada](/assets/images/help/repository/personal-repository-readme-template.png) + +### Eliminar un README de perfil + +El README de tu perfil se eliminará de tu perfil de {% data variables.product.prodname_dotcom %} si sucede cualquiera de los siguientes escenarios: + +- El archivo README está vacío o no existe. +- El repositorio es privado. +- El nombre del repositorio no empata con tu nombre de usuario. + +The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. Para encontrar los pasos de cómo hacer tu repositorio privado, consulta la sección ["Cambiar la visibilidad de un repositorio".](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility) + +### Further reading + +- [Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md new file mode 100644 index 0000000000000..e057a41793993 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md @@ -0,0 +1,124 @@ +--- +title: Personalizar tu perfil +intro: 'Puedes compartir información sobre tI con otros usuarios de {% data variables.product.product_name %} al configurar una imagen de perfil y agregar una biografía a tu perfil.' +redirect_from: + - /articles/adding-a-bio-to-your-profile/ + - /articles/setting-your-profile-picture/ + - /articles/how-do-i-set-up-my-profile-picture/ + - /articles/gravatar-problems/ + - /articles/how-do-i-set-up-my-avatar/ + - /articles/personalizing-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Cambiar tu imagen de perfil + +Tu imagen de perfil ayuda a identificarte dentro de {% data variables.product.product_name %} en solicitudes de extracción, comentarios, páginas de contribuciones y gráficos. + +Cuando te registras en una cuenta, {% data variables.product.product_name %} te proporciona un "identicon" generado al azar. [Tu identicon](https://github.com/blog/1586-identicons) se genera a partir de un hash de tu ID de usuario, por lo que no hay manera de controlar su color o patrón. Puedes reemplazar tu identicon con una imagen que te represente. + +{% tip %} + +**Sugerencia**: la imagen de tu perfil debería ser un archivo PNG, JPG, o GIF menor de 1 MB de tamaño. Para mostrar la mejor calidad, recomendamos mantener la imagen en alrededor de 500 por 500 píxeles. + +{% endtip %} + +#### Configurar una imagen de perfil + +{% data reusables.user_settings.access_settings %} +2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) +3. Haz clic en **Upload a photo... (Cargar una foto...)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.png) +3. Recorta tu imagen. Cuando hayas terminado, haz clic en **Set new profile picture (Configurar nueva imagen de perfil)**. ![Recortar foto cargada](/assets/images/help/profile/avatar_crop_and_save.png) + +#### Restablecer tu imagen de perfil al identicon + +{% data reusables.user_settings.access_settings %} +2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) +3. Para regresar a tu identicon, haz clic en **Remove photo (Eliminar foto)**. Si tu dirección de correo electrónico está asociada con [Gravatar](https://en.gravatar.com/), no puedes regresar a tu identicon. Haz clic en **Revert to Gravatar (Revertir a Gravatar)** en su lugar. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.png) + +### Cambiar tu nombre de perfil + +Puedes cambiar el nombre que se muestra en tu perfil. Este nombre también podría mostrarse junto a los comentarios que haces en los repositorios privados que pertenezcan a una organización. Para obtener más información, consulta "[Administrar cómo se ven los nombres de los miembros en tu organización](/articles/managing-the-display-of-member-names-in-your-organization)." + +{% data reusables.user_settings.access_settings %} +2. Dentro de "Nombre", escribe el nombre que deseas que se muestre en tu perfil. ![Campo Nombre en configuraciones de perfil](/assets/images/help/profile/name-field.png) + +### Agregar una biografía en tu perfil + +Agrega una biografía a tu perfil para compartir información sobre ti con otros usuarios de {% data variables.product.product_name %}. Con la ayuda de [@mentions](/articles/basic-writing-and-formatting-syntax) y emoji, puedes incluir información sobre dónde estás trabajando actualmente o dónde trabajaste anteriormente, qué tipo de trabajo realizas, o incluso qué tipo de café tomas. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + +Para encontrar un formato más largo y una forma más prominente de mostrar la información acerca de ti mismo, también puedes utilizar un README de perfil. Para obtener más información, consulta la sección "[Administrar el README de tu perfil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". + +{% endif %} + +{% note %} + +**Nota:** Si tienes habilitada la sección de resumen de la actividad para tu perfil y @mencionas a una organización a la que pertenezcas en tu biografía de perfil, esta organización se presentará primero en tu resumen de actividad. Para obtener más información, consulta "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +2. Dentro de **Bio (Biografía)**, agrega el contenido que deseas mostrar en tu perfil. El campo biografía tiene un límite de 160 caracteres. ![Actualizar biografía en el perfil](/assets/images/help/profile/bio-field.png) + + {% tip %} + + **Sugerencia:** cuando mencionas una organización, únicamente aquellas de las que eres miembro se completarán automáticamente. Incluso puedes mencionar organizaciones de las que no eres miembro, como un antiguo empleador, pero el nombre de la organización no se completará automáticamente. + + {% endtip %} + +3. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/profile/update-profile-button.png) + +### Configurar un estado + +Puedes configurar un estado para mostrar información acerca de tu disponibilidad actual en {% data variables.product.product_name %}. Tu estado se mostrará: +- en tu página de perfil {% data variables.product.product_name %}. +- cuando las personas se desplacen sobre tu nombre de usuario o avatar en {% data variables.product.product_name %}. +- en una página de equipo en un equipo del cual eres un miembro. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams/#team-pages)." +- en el tablero de la organización en una organización de la cual eres miembro. Para obtener más información, consulta "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard/)." + +Cuando configuras tu estado, también puedes permitir que las personas sepan que tienes disponibilidad limitada en {% data variables.product.product_name %}. + +![El nombre de usuario mencionado muestra una nota de "busy" (ocupado) al lado del nombre de usuario](/assets/images/help/profile/username-with-limited-availibilty-text.png) + +![El revisor solicitado muestra una nota de "busy" (ocupado) la lado del nombre de usuario](/assets/images/help/profile/request-a-review-limited-availability-status.png) + +Si seleccionas la opción, "Busy" (Ocupado), cuando las personas mencionan tu nombre de usuario, te asignan una propuesta o una solicitud de extracción o te solicitan una revisión de solicitud de extracción, una nota al lado de tu nombre de usuario mostrará que estás ocupado. + +1. En el ángulo superior derecho de {% data variables.product.product_name %}, haz clic en tu foto de perfil, después haz clic en **Set your status (Configurar tu estado)** o, si ya tienes un estado configurado, haz clic en tu estado actual. ![Botón en el perfil para configurar tu estado](/assets/images/help/profile/set-status-on-profile.png) +2. Para agregar un texto personalizado a tu estado, haz clic en el campo texto y escribe un mensaje de estado. ![Campo para escribir un mensaje de estado](/assets/images/help/profile/type-a-status-message.png) +3. De manera opcional, para configurar un estado de emoji, haz clic en el ícono sonriente y selecciona un emoji de la lista. ![Botón para seleccionar un estado de emoji](/assets/images/help/profile/select-emoji-status.png) +4. Como alternativa, si te gustaría compartir que tienes disponibilidad limitada, selecciona "Busy" (Ocupado). ![Opción ocupado seleccionada en las opciones de Editar estado](/assets/images/help/profile/limited-availability-status.png) +5. Utiliza el menú desplegable **Clear status (Borrar estado)** y selecciona cuándo deseas que venza tu estado. Si no deseas seleccionar un vencimiento de estado, mantendrás tu estado hasta que lo borres o edites. ![Menú desplegable para elegir cuando vence tu estado](/assets/images/help/profile/status-expiration.png) +6. Utiliza el menú desplegable y haz clic en la organización para la que deseas que tu estado sea visible. Si no seleccionas una organización, tu estado será público. ![Menú desplegable para elegir para quién es visible tu estado](/assets/images/help/profile/status-visibility.png) +7. Haz clic en **Set status (Configurar estado)**. ![Botón para establecer el estado](/assets/images/help/profile/set-status-button.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Mostrar las insignias en tu perfil + +Cuando participas en algunos programas, {% data variables.product.prodname_dotcom %} muestra automáticamente una insignia en tu perfil. + +| Insignia | Programa | Descripción | +| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% octicon "north-star" aria-label="The North Star icon" %} | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Si eres el autor de cualquier confirmación en la rama predeterminada de un repositorio que se archivó en el programa del 2020 del Vaúl del Ártico, obtendrás una insignia de colaborador de {% data variables.product.prodname_arctic_vault %} en tu perfil. Para obtener más información sobre el programa, consulta la sección [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). | +| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Miembro del Programa de Desarrolladores** | Si eres un miembro registrado del Programa de Desarrolladores de GitHub, crear una app con la API de GitHub te otorgará una insignia de Miembro del Programa de Desarrolladores en tu perfil. Para obtener más información sobre el Programa de Desarrolladores de Github, consulta la sección [Desarrolladores de GitHub](/program/). | +| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **Patrocinador de GitHub** | Si patrocinaste a un colaborador de código abierto a través de {% data variables.product.prodname_sponsors %} obtendrás una insignia de Patrocinador de GitHub en tu perfil. Para obtener más información, consulta la sección "[Patrocinar colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)". | +| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | Si utilizas {% data variables.product.prodname_pro %} obtendrás una insignia de PRO en tu perfil. Para obtener más información acerca de {% data variables.product.prodname_pro %}, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)." | + +### Inhabilitar las insignias en tu perfil + +Puedes inhabilitar algunas de las insignias de los programas de {% data variables.product.prodname_dotcom %} en los cuales participas, incluyendo las insignias de PRO y de {% data variables.product.prodname_arctic_vault %}. + +{% data reusables.user_settings.access_settings %} +2. Debajo de "Configuración del perfil", deselecciona la insignia que quieres inhabilitar. ![Casilla para dejar de mostrar una insignia en tu perfil](/assets/images/help/profile/display-pro-badge-checkbox.png) +3. Haz clic en **Update preferences (Actualizar preferencias)**. + +{% endif %} + +### Further reading + +- "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md new file mode 100644 index 0000000000000..7fc3328dcbbad --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md @@ -0,0 +1,29 @@ +--- +title: Anclar elementos a tu perfil +intro: 'Puedes fijar gists y repositorios en tu perfil para que otras personas puedan ver tus mejores trabajos rápidamente.' +redirect_from: + - /articles/pinning-repositories-to-your-profile/ + - /articles/pinning-items-to-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Puedes anclar un repositorio público si eres propietario del repositorio o has realizado contribuciones al repositorio. Las confirmaciones de las bifurcaciones no cuentan como contribuciones, por ello no puedes anclar una bifurcación de la que no eres propietario. Para obtener más información, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" + +Puedes fijar cualquier gist público que te pertenezca. + +Los elementos fijados incluyen información importante sobre ellos, como el número de estrellas que ha recibido el repositorio, o algunas de las primeras líneas de un gist. Una vez que hayas anclado elementos a tu perfil, la sección "Pinned" (Anclados) reemplaza a la sección "Popular repositories" (Repositorios populares) en tu perfil. + +Puedes reordenar los elementos en la sección "Anclados". En el ángulo superior derecho de un elemento anclado, haz clic en {% octicon "grabber" aria-label="The grabber symbol" %} y arrastra el anclado a una nueva ubicación. + +{% data reusables.profile.access_profile %} +2. En la sección "Repositorios populares" o "Anclados", haz clic en **Customize your pins (Personalizar tus anclados)**. ![Botón para personalizar tus elementos anclados](/assets/images/help/profile/customize-pinned-repositories.png) +3. Para mostrar una lista de búsqueda de elementos por anclar, selecciona "Repositories" (Repositorios), "Gists" o ambos. ![Casillas de verificación para seleccionar los tipos de elementos a mostrar](/assets/images/help/profile/pinned-repo-picker.png) +4. Como opción, para que sea más sencillo encontrar un elemento específico, en el campo de filtro, escribe el nombre de un usuario, una organización, un repositorio o un gist. ![Filtrar elementos](/assets/images/help/profile/pinned-repo-search.png) +5. Selecciona una combinación de hasta seis repositorios o gists para mostrar. ![Seleccionar elementos](/assets/images/help/profile/select-items-to-pin.png) +6. Haz clic en **Save pins (Guardar anclados)**. ![Botón guardar elementos anclados](/assets/images/help/profile/save-pinned-repositories.png) + +### Further reading + +- "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md new file mode 100644 index 0000000000000..c38c300057aa6 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -0,0 +1,26 @@ +--- +title: Divulgar u ocultar tus contribuciones privadas en tu perfil +intro: 'Tu perfil {% data variables.product.product_name %} muestra un gráfico de las contribuciones a tu repositorio durante el último año. Puedes elegir mostrar la actividad anonimizada de los repositorios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}privados e internos{% else %}privados{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} adicionalmente a aquella de los repositorios públicos{% endif %}.' +redirect_from: + - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si publicas tus contribuciones privadas, las personas sin acceso a los repositorios privados en los que trabajas no podrán ver los detalles de tus contribuciones privadas. En su lugar, verán la cantidad de contribuciones privadas que has realizado durante un determinado día. Tus contribuciones públicas incluirán información detallada. Para obtener más información, consulta "[Ver contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)". + +### Cambiar la visibilidad de tus contribuciones privadas + +Por defecto, los visitantes únicamente ven las contribuciones públicas en tu perfil. + +{% data reusables.profile.access_profile %} +2. Divulga u oculta tus contribuciones privadas en tu perfil: + - Para publicitar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y selecciona **Private contributions** (Contribuciones privadas). Los visitantes verán tus recuentos de contribuciones privadas sin más detalles. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-on.png) + - Para ocultar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y anula la selección de **Private contributions** (Contribuciones privadas). Los visitantes únicamente verán tus contribuciones públicas. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-off.png) + +### Further reading + +- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" +- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md new file mode 100644 index 0000000000000..84af8f4416bb8 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md @@ -0,0 +1,33 @@ +--- +title: Enviar tus contribuciones de GitHub Enterprise Server a tu perfil de GitHub.com +intro: 'Puedes resaltar tu trabajo en {% data variables.product.prodname_ghe_server %} al enviar los recuentos de contribuciones a tu perfil {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% note %} + +**Notas:** +- La conexión entre tus cuentas está regulada por la Declaración de privacidad de GitHub, y los usuarios que habilitan la conexión aceptan los Términos de servicio de GitHub. + +- Antes de que puedas conectar tu perfil de {% data variables.product.prodname_ghe_server %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, un administrador de sitio debe habilitar {% data variables.product.prodname_github_connect %} y permitir que se compartan contribuciones entre los entornos. Para obtener más información, contacta a tu administrador del sitio {% data variables.product.prodname_ghe_server %}. + +{% endnote %} + +Tu perfil de {% data variables.product.prodname_dotcom_the_website %} muestra los recuentos de contribuciones de {% data variables.product.prodname_ghe_server %} durante los últimos 90 días. Los recuentos de contribuciones de {% data reusables.github-connect.sync-frequency %} de {% data variables.product.prodname_ghe_server %} se consideran contribuciones privadas. Los detalles de confirmación mostrarán únicamente los recuentos de contribuciones y que estas contribuciones se realizaron en {% data variables.product.prodname_ghe_server %}. + +Si los usuarios finales de {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} desean que sus recuentos de contribuciones privadas sean públicas, pueden divulgar sus recuentos de contribuciones privadas. Para obtener más información, consulta "[Publicar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)." + +Para obtener más información acerca de cómo se calculan las contribuciones, consulta "[Administrar gráficos de contribuciones en tu perfil](/articles/managing-contribution-graphs-on-your-profile/)." + +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.github-connect.access-profile-settings %} +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +6. Debajo de "Contributions" (Contribuciones), selecciona **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Enviar mi recuento de contribuciones a {% data variables.product.prodname_dotcom_the_website %}), luego haz clic en **Update contributions** (Actualizar contribuciones). ![Casilla para enviar contribuciones y botón para actualizar contribuciones](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md new file mode 100644 index 0000000000000..fb777137e58e1 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md @@ -0,0 +1,17 @@ +--- +title: Mostrar un resumen de tu actividad en tu perfil +intro: Puedes habilitar la sección de resumen de actividad en tu perfil para darle a los observadores más contexto acerca de los tipos de contribuciones que realizas. +redirect_from: + - /articles/showing-an-overview-of-your-activity-on-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.profile.activity-overview-summary %} Para obtener más información, consulta "[Ver contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)." + +![Sección de resumen de actividad en el perfil](/assets/images/help/profile/activity-overview-section.png) + +{% data reusables.profile.access_profile %} +2. Arriba de tu gráfica de contribuyentes, utiliza el menú desplegable de **configuración de contribuciones** y selecciona o deselecciona **Resumen de la actividad**. ![Habilita el resumen de actividad desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/activity-overview.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md new file mode 100644 index 0000000000000..f3401bd00feaa --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -0,0 +1,63 @@ +--- +title: Confirmaciones de solución de problemas en tu cronología +intro: 'Puedes ver los detalles de las confirmaciones desde tu cronología del perfil. Si no ves las confirmaciones que esperas en tu perfil o no puedes encontrar los detalles de confirmaciones desde la página de tu perfil, puede que sean diferentes la fecha de la confirmación y el autor de la confirmación.' +redirect_from: + - /articles/troubleshooting-commits-on-your-timeline +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Comportamiento esperado para ver detalles de confirmaciones + +En la cronología de la página de tu perfil, puedes hacer clic en el número de confirmaciones al lado de un repositorio específico para ver más detalles acerca de tus confirmaciones desde ese período de tiempo, incluida una diferencia de cambios específicos hechos en un repositorio. + +![Enlace de confirmación en la cronología del perfil](/assets/images/help/profile/commit-link-on-profile-timeline.png) + +![Detalles de confirmaciones](/assets/images/help/commits/commit-details.png) + +### Detalles de confirmaciones faltantes de las confirmaciones de tu cronología + +Si haces clic en un enlace de confirmación desde tu página de perfil y no ves todas las confirmaciones esperadas en la página de confirmaciones del repositorio, es posible que el historial de confirmaciones de Git se haya rescrito y que el autor de la confirmación y la fecha de la confirmación sean diferentes. + +![Página del repositorio con el mensaje que dice "no commits found for octocat" (no se encontraron confirmaciones para octocat)](/assets/images/help/repository/no-commits-found.png) + +### Cómo utiliza GitHub la fecha de autor y la fecha de confirmación de Git + +En Git, la fecha de autor es cuando alguna persona crea por primera vez una confirmación con `git commit`. La fecha de la confirmación es idéntica a la fecha de autor, a menos que alguna persona cambie la fecha de confirmación utilizando `git commit --amend`, un empuje forzado, una rebase u otro comando de Git. + +En tu página de perfil, la fecha de autor se utiliza para calcular cuándo se realizó una confirmación. Por otro lado, en un repositorio, la fecha de confirmación se utiliza para calcular cuándo se hizo una confirmación en el repositorio. + +La mayoría de las veces, la fecha de autor y la fecha de confirmación son las mismas, pero puedes notar que tu secuencia de confirmaciones no funciona si se modifica el historial de confirmaciones. Para obtener más información, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" + +### Ver detalles de confirmaciones faltantes de las confirmaciones de tu cronología + +Puedes utilizar el comando `git show` con la marca `--pretty=fuller` para comprobar si la fecha de autor de la confirmación y la fecha de confirmación son diferentes. + +```shell +$ git show Your commit SHA number --pretty=fuller +commit Your commit SHA number +Author: octocat user email +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 +Commit: Sally Johnson user email +CommitDate: Tue Apr 10 06:25:08 2018 +0900 +``` + +Si la fecha de autor y de confirmación son diferentes, puedes cambiar de forma manual la fecha de confirmación en la URL para ver los detalles de la confirmación. + +Por ejemplo: +- Esta URL utiliza la fecha de autor del `2018-04-03`: + + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- Esta URL utiliza la fecha de confirmación del `2018-04-10`: + + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` + +Cuando abres la URL con la fecha de confirmación modificada, puedes ver los detalles de la confirmación. + +![Detalles de confirmaciones](/assets/images/help/commits/commit-details.png) + +### Confirmaciones esperadas faltantes en tu cronología + +Si no estás viendo las confirmaciones esperadas en tu cronología, es posible que el historial de confirmaciones de Git se haya rescrito y que la fecha de autor de la confirmación y la fecha de confirmación sean diferentes. Para conocer otras posibilidades, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md new file mode 100644 index 0000000000000..54dfe0ab7eaf0 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -0,0 +1,99 @@ +--- +title: Ver contribuciones en tu perfil +intro: 'Tu perfil de {% data variables.product.product_name %} presume {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}tus repositorios anclados, así como{% endif %} una gráfica de tus contribuciones al repositorio en el último año.' +redirect_from: + - /articles/viewing-contributions/ + - /articles/viewing-contributions-on-your-profile-page/ + - /articles/viewing-contributions-on-your-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Tu gráfica de contribuciones muestra la actividad de los repositorios públicos. {% endif %}Puedes elegir que se muestre la actividad tanto de {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}los repositorios públicos como la de {% endif %}los privados, con detalles específicos de tu actividad anonimizada en los repositorios privados. Para obtener más información, consulte "[Publicar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." + +{% note %} + +**Nota:** Las confirmaciones solo aparecerán en tu gráfica de contribuciones si la dirección de correo electrónico que utilizaste para crear las confirmaciones está conectada a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta"[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" + +{% endnote %} + +### Qué cuenta como una contribución + +En tu página de perfil, determinadas acciones cuentan como contribuciones: + +- Confirmar cambios en una rama por defecto de un repositorio o en la rama `gh-pages` +- Abrir una propuesta +- Proponer una solicitud de extracción +- Emitir una revisión de una solicitud de cambios{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Confirmar como coautor en la rama por defecto de un repositorio o en la rama `gh-pages`{% endif %} + +{% data reusables.pull_requests.pull_request_merges_and_contributions %} + +### Repositorios populares + +Esta sección muestra tus repositorios con la mayor cantidad de observadores. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Una vez que [anclas los repositorios a tu perfil](/articles/pinning-repositories-to-your-profile), esta sección cambiará a "Repositorios anclados".{% endif %} + +![Repositorios populares](/assets/images/help/profile/profile_popular_repositories.png) + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +### Repositorios anclados + +Esta sección muestra hasta seis repositorios públicos y puede incluir tus repositorios y los repositorios a los que has contribuidos. Para ver fácilmente detalles importantes sobre los repositorios que has seleccionado para mostrar, cada repositorio en esta sección incluye un resumen del trabajo que se está realizando, la cantidad de [estrellas](/articles/saving-repositories-with-stars/) que el repositorio ha recibido y el lenguaje de programación principal utilizado en el repositorio. Para obtener más información, consulta "[Anclar repositorios en tu perfil](/articles/pinning-repositories-to-your-profile)." + +![Repositorios anclados](/assets/images/help/profile/profile_pinned_repositories.png) + +{% endif %} + +### Calendario de contribuciones + +Tu calendario de contribuciones muestra tu actividad de contribuciones. + +#### Ver contribuciones de momentos específicos + +- Haz clic en el cuadrado de un día para mostrar las contribuciones realizadas durante ese período de 24 horas. +- Presiona *Shift* y haz clic en el cuadrado de otro día para mostrar las contribuciones realizadas durante ese período de tiempo. + +{% note %} + +**Nota:** puedes seleccionar hasta un rango de un mes en tu calendario de contribuciones. Si seleccionas un período de tiempo más extenso, únicamente se mostrarán las contribuciones de un mes. + +{% endnote %} + +![Tu gráfico de contribuciones](/assets/images/help/profile/contributions_graph.png) + +#### Cómo se calculan los momentos de los eventos de las contribuciones + +Las marcas horarias se calculan de forma diferente para las confirmaciones y las solicitudes de extracción: +- **Confirmaciones** utilizan la información de la zona horaria en la marca de tiempo de la confirmación. Para obtener más información, consulta "[Solución de problemas con confirmaciones en tu cronología](/articles/troubleshooting-commits-on-your-timeline)." +- **Las solicitudes de extracción** y **las propuestas** abiertas en {% data variables.product.product_name %} utilizan la zona horaria de tu navegador. Aquellas abiertas a través de API utilizan la marca horaria o la zona horaria [especificada en la llamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). + +### Activity overview + +{% data reusables.profile.activity-overview-summary %} Para obtener más información, consulta "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." + +![Sección de resumen de actividad en el perfil](/assets/images/help/profile/activity-overview-section.png) + +Las organizaciones que se muestran en el resumen de la actividad se priorizan de acuerdo con qué tan activo estés en la organización. Si mencionas una organización en tu biografía de perfil y eres miembro de una organización, entonces esa organización se prioriza en el resumen de la actividad. Para obtener más información, consulta “[Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” o "[Agregar una biografía en tu perfil](/articles/adding-a-bio-to-your-profile/)." + +### Actividad de contribución + +La sección de actividad de contribuciones incluye una cronología detallada de tu trabajo, incluyendo confirmaciones que has realizado o de las que eres coautor, solicitudes de extracción que propusiste y propuestas que abriste. Puedes ver tus contribuciones en el tiempo al hacer clic en **Show more activity (Mostrar más actividad)** en la parte inferior de tu actividad de contribuciones o al hacer clic en el año que te interesa ver hacia la derecha de la página. Momentos importantes, como la fecha en que te uniste a una organización, propusiste tu primera solicitud de extracción o abriste una propuesta de alto perfil, se resaltan en tu actividad de contribuciones. Si no puedes ver determinados eventos en tu cronología, asegúrate de que todavía tengas acceso a la organización o al repositorio donde ocurrió el evento. + +![Filtro de tiempo de actividad de contribuciones](/assets/images/help/profile/contributions_activity_time_filter.png) + +{% if currentVersion != "github-ae@latest" %} +### Ver contribuciones de {% data variables.product.product_location_enterprise %} en {% data variables.product.prodname_dotcom_the_website %} +Si tu administrador de sitio habilitó + +{% data variables.product.prodname_unified_contributions %}, puedes enviar un conteo de contribuciones de {% data variables.product.prodname_enterprise %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Enviar tus contribuciones {% data variables.product.prodname_ghe_server %} a tu {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." +{% endif %} + +### Further reading + +- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" +- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" +- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Mostrar una revisión de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md new file mode 100644 index 0000000000000..6318f14a707a8 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -0,0 +1,88 @@ +--- +title: '¿Por qué mis contribuciones no aparecen en mi perfil?' +intro: 'Tu gráfico de contribución de perfil es un registro de las contribuciones que hiciste a los repositorios {% data variables.product.product_name %}. Las contribuciones son registros horarios de acuerdo a la zona horaria universal coordinada (UTC) en lugar de tu zona horaria local. Las contribuciones solo se cuentan si cumplen con determinados criterios. En algunos casos, necesitamos reconstruir tu gráfico para que aparezcan las contribuciones.' +redirect_from: + - /articles/why-are-my-contributions-not-showing-up-on-my-profile +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Contribuciones que se cuentan + +#### Issues, pull requests and discussions + +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. + +#### Confirmaciones +Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **todas** las condiciones a continuación: +- La dirección de correo electrónico que se usa para las confirmaciones se asocia con tu cuenta {% data variables.product.product_name %}. +- Las confirmaciones se hicieron en un repositorio independiente, no en una bifurcación. +- Las confirmaciones se hicieron: + - En la rama predeterminada del repositorio + - En la rama `gh-pages` (para los repositorios con sitios de proyecto) + +Para obtener más información sobre los sitios del proyecto, consulta "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)" + +Asimismo, **al menos una** de las siguientes afirmaciones debe ser verdadera: +- Eres un colaborador en el repositorio o eres miembro de la organización a la que pertenece el repositorio. +- Has bifurcado el repositorio. +- Has abierto una solicitud de extracción o una propuesta en el repositorio. +- Has destacado el repositorio. + +### Razones comunes por las que las contribuciones no se cuentan + +{% data reusables.pull_requests.pull_request_merges_and_contributions %} + +#### La confirmación se hizo hace menos de 24 horas + +Después de hacer una confirmación que cumpla con los requisitos para contar como una contribución, es posible que debas esperar hasta 24 horas para que aparezca la contribución en tu gráfico de contribución. + +#### Tu correo electrónico de confirmaciones de Git no está conectado a tu cuenta + +Las confirmaciones deben hacerse con una dirección de correo electrónico que esté conectada a tu cuenta en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}, o a la dirección de correo elecrónico de tipo `noreply` que proporcionó {% data variables.product.product_name %} y que se te dio en tu configuración de correo electrónico,{% endif %} para poder aparecer en tu gráfica de contribuciones.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información sobre las direcciones de correo electrónico de tipo `noreply`, consulta la sección "[Configurar tu dirección de correo de confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)".{% endif %} + +Puedes verificar la dirección de correo electrónico para una confirmación si agregas `.patch` al final de la URL de la confirmación, por ejemplo https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: + +``` +From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 +From: The Octocat +Date: Sun, 27 Apr 2014 15:36:39 +0530 +Subject: [PATCH] índice actualizado para un mejor mensaje de bienvenida +``` + +La dirección de correo electrónico en el campo `From: (Desde:)` es la dirección que se estableció en los [parámetros de configuración de Git local](/articles/set-up-git). En este ejemplo, la dirección de correo electrónico que se usó para la confirmación es `octocat@nowhere.com`. + +Si la dirección de correo electrónico que se utiliza para la confirmación no está conectada a tu cuenta en {% data variables.product.product_name %}, {% if currentVersion == "github-ae@latest" %}cambia aquella que se utiliza para crear confirmaciones en Git. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %}debes [agregar la dirección de correo electrónico](/articles/adding-an-email-address-to-your-github-account) a tu cuenta de {% data variables.product.product_name %}. Tu gráfica de contribuciones se reconstruirá automáticamente cuando agregues la nueva dirección.{% endif %} + +{% warning %} + +Las direcciones de correo electrónico generales, tales como `jane@computer.local`, no se pueden agregar a las cuentas {% data variables.product.product_name %}. Si usas un correo electrónico de ese estilo para tus confirmaciones, las confirmaciones no se vincularán a tu perfil {% data variables.product.product_name %} y no aparecerán en tu gráfico de contribución. + +{% endwarning %} + +#### La confirmación no se hizo en la rama predeterminada o en la rama `gh-pages` + +Las confirmaciones solo se cuentan si se realizan en la rama predeterminada o en la rama `gh-pages` (para los repositorios con sitios de proyecto). Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". + +Si tus confirmaciones están en una rama que no es una rama predeterminada ni es la rama `gh-pages` y te gustaría que contaran para tus contribuciones, necesitarás realizar las siguientes acciones: +- [Abre una solicitud de extracción](/articles/creating-a-pull-request) para obtener la fusión de tus cambios en la rama predeterminada o la rama `gh-pages`. +- [Cambia la rama predeterminada](/github/administering-a-repository/changing-the-default-branch) del repositorio. + +{% warning %} + +Cambiar la rama por defecto del repositorio la cambiará para todos los colaboradores del repositorio. Realiza esta acción solamente si quieres que la nueva rama se convierta en la base respecto de todas las confirmaciones y las solicitudes de extracción que se harán en el futuro. + +{% endwarning %} + +#### La confirmación se hizo en una bifurcación + +Las confirmaciones que se hicieron en una bifurcación no contarán para tus contribuciones. Para hacer que cuenten, debes realizar una de las siguientes acciones: +- [Abre una solicitud de extracción](/articles/creating-a-pull-request) para que se fusionen tus cambios en el repositorio padre. +- Para desconectar la bifurcación y convertirla en un repositorio independiente en {% data variables.product.product_name %}, contacta {% data variables.contact.contact_support %}. Si la bifurcación tiene a su vez más bifurcaciones, indica a {% data variables.contact.github_support %} si éstas deberán moverse junto con tu repositorio a una nueva red o permanecer en la actual. Para obtener más información, consulta "[Acerca de las bifurcaciones](/articles/about-forks/)." + +### Further reading + +- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md new file mode 100644 index 0000000000000..abc2ade79cbbb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md @@ -0,0 +1,47 @@ +--- +title: Acerca de la membresía de una organización +intro: Puedes convertirte en miembro de una organización para colaborar con los compañeros de trabajo o los colaboradores de código abierto en muchos repositorios a la vez. +redirect_from: + - /articles/about-organization-membership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Un propietario de la organización puede invitarte a unirte a su organización como miembro, gerente de facturación o propietario. Un miembro o propietario de la organización con privilegios de administrador para un repositorio puede invitarte a colaborar en uno o más repositorios como un colaborador externo. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". + +Puedes acceder a las organizaciones de las que eres miembro en tu página de perfil. Para obtener más información, consulta "[Acceder a una organización](/articles/accessing-an-organization)". + +Cuando aceptas una invitación para unirte a una organización, el propietario de la organización puede ver lo siguiente: + +- La información de tu perfil público. +- Tu dirección de correo electrónico. +- Si tienes la autorización de dos factores activada. +- Los repositorios a los que tienes acceso dentro de la organización y tu nivel de acceso. +- Ciertas actividades dentro de la organización. +- País del origen de la solicitud. +- Tu dirección IP. + +Para obtener más información, consulta la {% data variables.product.prodname_dotcom %} Declaración de privacidad. + + {% note %} + + **Nota:** Los propietarios no pueden ver las direcciones IP del miembro en el registro de auditoría de la organización. En el caso de un incidente de seguridad, como una cuenta comprometida o la divulgación involuntaria de datos confidenciales, los propietarios de la organización pueden solicitar los detalles de acceso a los repositorios privados. La información que devolvemos puede incluir tu dirección IP. + + {% endnote %} + +Por defecto, la visibilidad de los miembros de tu organización se establece como privada. Puede elegir publicar miembros individuales de la organización en tu perfil. Para obtener más información, consulta "[Publicar u ocultar los miembros de la organización](/articles/publicizing-or-hiding-organization-membership)". + +{% if currentVersion == "free-pro-team@latest" %} + +Si tu organización pertenece a una cuenta de empresa, automáticamente eres un miembro de la cuenta de empresa y visible para los propietarios de la cuenta de empresa. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)". + +{% endif %} + +Puedes dejar una organización en cualquier momento. Para obtener más información, consulta "[Cómo eliminarte de una organización](/articles/removing-yourself-from-an-organization)". + +### Further reading + +- "[Acerca de las organizaciones](/articles/about-organizations)" +- "[Administrar tu membresía en organizaciones](/articles/managing-your-membership-in-organizations)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md new file mode 100644 index 0000000000000..79471546172bf --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -0,0 +1,56 @@ +--- +title: Acerca de tu tablero personal +redirect_from: + - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/ + - /articles/opting-into-the-public-beta-for-a-new-dashboard/ + - /articles/about-your-personal-dashboard +intro: 'Puedes visitar tu tablero personal para hacer un seguimiento de las propuestas y las solicitudes de extracción que estás siguiendo o en las que estás trabajando, navegar hacia las páginas de equipo y tus repositorios principales, estar actualizado sobres las actividadess recientes en las organizaciones y los repositorios en los que estás suscripto y explorar los repositorios recomendados.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acceder a tu tablero personal + +Tu tablero personal es la primera página que verás cuando inicias sesión en {% data variables.product.product_name %}. + +Para acceder a tu tablero personal una vez que has iniciado sesión, haz clic en el {% octicon "mark-github" aria-label="The github octocat logo" %} en la esquina superior izquierda de cualquier página en {% data variables.product.product_name %}. + +### Encontrar tu actividad reciente + +En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes encontrar las propuestas y solicitudes de extracción recién actualizadas en las que estás trabajando y hacerles el seguimiento. En "Recent activity" (Actividad reciente), puedes previsualizar hasta 12 actualizaciones recientes, realizadas durante las últimas dos semanas. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Encontrar tus equipos y repositorios principales + +En la barra lateral izquierda de tu tablero, puedes acceder a los equipos y los repositorios principales que usas. + +![listado de repositorios y equipos de diferentes organizaciones](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png) + +La lista de repositorios principales se genera automáticamente y puede incluir cualquier repositorio con el que hayas interactuado, ya sea que pertenezca directamente a tu cuenta o no. Las interacciones incluyen el realizar confirmaciones y abrir o comentar en propuestas y solicitudes de cambios. La lista de repositorios principales no puede editarse, pero los repositorios saldrán de la lista en 4 meses después de la última interacción que hayas tenido con ellos. + +También puedes encontrar un listado de los repositorios, los equipos y los tableros de proyecto recientemente visitados al hacer clic en la barra de búsqueda en la parte principal de cualquier página en {% data variables.product.product_name %}. + +### Estar actualizado con la actividad desde tu organización + +En la sección "All activity" (Todas las actividades) de tus noticias, puedes ver las actualizaciones de los repositorios a los que estás suscrito y de las personas que sigues. La sección "All activity" (Todas las actividades) muestra las actualizaciones de los repositorios que observas o has marcado con una estrella, y de los usuarios a quienes sigues. + +Verás actualizaciones en tus noticias cuando un usuario que sigues: +- Destaca un repositorio. +- Siga a otro usuario.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- Crea un repositorio público.{% endif %} +- Abre una propuesta o una solicitud de extracción con la etiqueta "se busca ayuda" o "primera buena propuesta" en un repositorio que estás mirando. +- Suba confirmaciones a un repositorio que estés observando.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- Bifurque un repositorio público.{% endif %} + +Para obtener más información acerca de cómo destacar repositorios y seguir personas, consulta "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" y "[Seguir a personas](/articles/following-people)". + +### Explorar los repositorios recomendados + +Puedes explorar los repositorios recomendados en tus comunidades en la sección "Explorar repositorios" en el costado derecho de tu tablero. Las recomendaciones se basan en los repositorios que hayas visitado o marcado como favoritos, las personas que sigues, y la actividad dentro de los repositorios a los que tienes acceso.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Encontrar formas para contribuir con los proyectos de código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".{% endif %} + +### Further reading + +- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md new file mode 100644 index 0000000000000..8cc99d200c9b2 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md @@ -0,0 +1,22 @@ +--- +title: Acceder a una organización +intro: 'Para acceder a una organización de la que eres miembro, debes iniciar sesión en tu cuenta de usuario personal.' +redirect_from: + - /articles/error-cannot-log-in-that-account-is-an-organization/ + - /articles/cannot-log-in-that-account-is-an-organization/ + - /articles/how-do-i-access-my-organization-account/ + - /articles/accessing-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Solo los propietarios de la organización pueden ver y cambiar los parámetros de la cuenta para una organización. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md new file mode 100644 index 0000000000000..0810465d5898f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md @@ -0,0 +1,28 @@ +--- +title: Agregar una dirección de correo electrónico a tu cuenta de GitHub +intro: '{% data variables.product.product_name %} permite que agregues a tu cuenta tantas direcciones de correo electrónico como desees. Si estableces una dirección de correo electrónico en tu configuración de Git local, necesitarás agregarla a los parámetros de tu cuenta a fin de conectar tus confirmaciones con tu cuenta. Para más información sobre las direcciones de correo electrónico y las confirmaciones, consulta "[Setting your commit email address](/articles/setting-your-commit-email-address/)".' +redirect_from: + - /articles/adding-an-email-address-to-your-github-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %} + +{% endnote %} + +{% endif %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +{% data reusables.user_settings.add_and_verify_email %} +{% data reusables.user_settings.select_primary_email %} + +### Further reading + +- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md new file mode 100644 index 0000000000000..5afa65a7e44c8 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md @@ -0,0 +1,34 @@ +--- +title: Mejores prácticas para abandonar la empresa +intro: 'Cambiar de trabajo es una realidad. Si usas tu cuenta de usuario de GitHub para tus objetivos personales *y* laborales, hay algunas cosas que debes tener en cuenta al dejar la empresa u organización.' +redirect_from: + - /articles/best-practices-for-leaving-your-company +versions: + free-pro-team: '*' +--- + +Antes de abandonar tu empresa, asegúrate de actualizar la siguiente información en tu cuenta de usuario: + +- Quitar la marca de verificación de la dirección de correo electrónico de la empresa al [eliminarla de los parámetros de Correo electrónico](/articles/changing-your-primary-email-address). Puedes volver a agregarla sin verificar para conservar todas las confirmaciones asociadas vinculadas con tu cuenta. +- [Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address) del correo electrónico de tu empresa a tu correo electrónico personal. +{% if currentVersion == "free-pro-team@latest" %} +- [Verificar tu nueva dirección principal de correo electrónico](/articles/verifying-your-email-address). +{% endif %} +- [Cambiar tu nombre de usuario de GitHub](/articles/changing-your-github-username) para eliminar cualquier referencia a tu empresa u organización, si es necesario. + +## Abandonar las organizaciones + +Si has estado trabajando con repositorios que pertenecen a una organización, deberás [eliminarte como miembro de la organización](/articles/removing-yourself-from-an-organization). Ten en cuenta que si eres el propietario de la organización, primero deberías [transferir tu pertenencia a la organización](/articles/transferring-organization-ownership) a otra persona. + +## Eliminar asociaciones profesionales con repositorios personales. + +Si has estado colaborando profesionalmente con otra persona en repositorios que pertenecen a su cuenta de usuario personal, deberás [eliminarte como colaborador](/articles/removing-yourself-from-a-collaborator-s-repository) desde otros repositorios. + +- [Deja de mirar repositorios](https://github.com/watching) relacionados con tu trabajo. No desearás volver a ver esas notificaciones. +- [Transfiere los repositorios que posees](/articles/how-to-transfer-a-repository) a otros que deben seguir trabajando con ellos una vez que te marches. +- [Elimina bifurcaciones que te pertenecen](/articles/deleting-a-repository) y que están relacionadas con el trabajo que estabas haciendo. No te preocupes, si eliminas una bifurcación no eliminarás el repositorio ascendente. +- Elimina copias locales de las bifurcaciones que pueden existir en tu computadora. + +```shell +$ rm -rf work_directory +``` diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md new file mode 100644 index 0000000000000..19a13beb1a83a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -0,0 +1,21 @@ +--- +title: Bloquear las inserciones de la línea de comando que muestran tu dirección de correo electrónico personal +intro: 'Si decidiste mantener tu dirección de correo electrónico privada al realizar operaciones basadas en la web, también puedes optar por bloquear las inserciones de la línea de comando que pueden exponer tu dirección de correo electrónico personal.' +redirect_from: + - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address +versions: + free-pro-team: '*' +--- + +Cuando subes las confirmaciones de la línea de comando, la dirección de correo electrónico que has [establecido en Git](/articles/setting-your-commit-email-address) están asociadas con tus confirmaciones. Este parámetro impide que subas confirmaciones a la línea de comando que usa tu dirección de correo electrónico personal. + +{% data reusables.user_settings.about-commit-email-addresses %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +{% data reusables.user_settings.keeping_your_email_address_private %} +4. Para que tu dirección de correo electrónico siga siendo privada en las confirmaciones desde la línea de comando, selecciona **Block command line pusses that expose my email** (Bloquear inserciones de la línea de comando que expone mi correo electrónico). ![Opción para bloquear las inserciones de la línea de comando que expone tus correos electrónicos](/assets/images/help/settings/email_privacy_block_command_line_pushes.png) + +### Further reading + +- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md new file mode 100644 index 0000000000000..f0f8024bef7ae --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md @@ -0,0 +1,57 @@ +--- +title: Cambiar tu nombre de usuario de GitHub +intro: 'Puedes cambiar tu nombre de usuario de {% data variables.product.product_name %} en cualquier momento.' +redirect_from: + - /articles/how-to-change-your-username/ + - /articles/changing-your-github-user-name/ + - /articles/renaming-a-user/ + - /articles/what-happens-when-i-change-my-username/ + - /articles/changing-your-github-username +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de los cambios de nombre de usuario + +Puedes cambiar tu nombre de usuario por uno diferente si es que nadie más lo tiene.{% if currentVersion == "free-pro-team@latest" %} Si el nombre de usuario que tienes no está disponible, verás la información referente a si puedes solicitar que se libere cuando tecleas tu nombre deseado. + +Si el nombre de usuario no puede usarse y no posees una marca comercial para el nombre de usuario, puedes elegir otro nombre de usuario o conservar tu nombre de usuario actual. {% data variables.contact.github_support %} no puede publicar el nombre de usuario que no está disponible para ti. Para obtener más información, consulta "[Cambiar tu nombre de usuario](#changing-your-username)".{% endif %} + +Una vez que cambies tu nombre de usuario, el nombre de usuario anterior estará disponible para todas las personas que lo reclamen. La mayoría de las referencias a tus repositorios con el nombre de usuario anterior automáticamente cambian al nombre de usuario nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. + +{% data variables.product.product_name %} no puede configurar redirecciones para: +- [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) con tu nombre de usuario anterior +- Enlaces a los [gists](/articles/creating-gists) que incluyen tu nombre de usuario anterior + +### Referencias del repositorio + +Después de cambiar tu nombre de usuario, {% data variables.product.product_name %} automáticamente redirigirá las referencias a tus repositorios. +- Los enlaces web a tus repositorios existentes seguirán funcionando. Esto puede tardar algunos minutos en completarse después de realizar el cambio. +- Las inserciones de la línea de comando desde tus clones de repositorio local hasta las URL del registro remoto anterior seguirán funcionando. + +Si el nuevo propietario de tu nombre de usuario anterior crea un repositorio con el mismo nombre que tu repositorio, se sobrescribirá el registro de redirección y tu redirección dejará de funcionar. Debido a esta posibilidad, recomendamos que actualices todas las URL de repositorios remotos existentes luego de cambiar tu nombre de usuario. Para obtener más información, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url). + +### Enlaces a tu página de perfil anterior + +Luego de cambiar tu nombre de usuario, los enlaces a tu página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, arrojarán un error 404. Te recomendamos actualizar cualquier enlace a tu cuenta de {% data variables.product.product_name %} desde cualquier otra parte{% if currentVersion == "free-pro-team@latest" %}, así como tu perfil de LinkedIn o de Twitter{% endif %}. + +### Tus confirmaciones Git + +{% if currentVersion == "free-pro-team@latest"%}No se les atribuirá tu nombre de usuario a las confirmaciones de Git que estaban asociadas con tu dirección de correo de tipo `noreply` que proporcionó {% data variables.product.product_name %} ni tampoco aparecerá en tu gráfica de contribuciones.{% endif %} Si tus confirmaciones de Git están asociadas con otra dirección de correo electrónico que hayas [agregado a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account), {% if currentVersion == "free-pro-team@latest"%} incluyendo la dirección de correo electrónico de tipo `noreply` basada en ID que proporcionó {% data variables.product.product_name %}, {% endif %}Estas se te seguirán atribuyendo y aparecerán en tu gráfica de contribuciones después de que hayas cambiado tu nombre de usuario. Para obtener más información sobre cómo establecer tu dirección de correo electrónico, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". + +### Cambiar tu nombre de usuario + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.account_settings %} +3. En la sección "Change username" (Cambiar nombre de usuario), haz clic en **Change username** (Cambiar nombre de usuario). ![Change Username button](/assets/images/help/settings/settings-change-username.png){% if currentVersion == "free-pro-team@latest" %} +4. Lee las advertencias sobre cómo cambiar tu nombre de usuario. Si aún deseas cambiar tu nombre de usuario, haz clic en **I understand, let's change my username** (Comprendo, cambiaré mi nombre de usuario). ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-username-warning-button.png) +5. Escribe un nuevo nombre de usuario. ![Campo New username (Nuevo nombre de usuario)](/assets/images/help/settings/settings-change-username-enter-new-username.png) +6. Si el nombre de usuario que elegiste está disponible, haz clic en **Change my username** (Cambiar mi nombre de usuario). Si el nombre de usuario que elegiste no está disponible, puedes probar un nombre de usuario diferente o una de las sugerencias que ves. ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-my-username-button.png) +{% endif %} + +### Further reading + +- "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)" +- "[¿Por qué se enlazan mis confirmaciones a un usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% if currentVersion == "free-pro-team@latest" %} +- "[{% data variables.product.prodname_dotcom %} Política de nombre de usuario](/articles/github-username-policy)"{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md new file mode 100644 index 0000000000000..a2181369a0cda --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md @@ -0,0 +1,30 @@ +--- +title: Cambiar tu dirección principal de correo electrónico +intro: Puedes cambiar la dirección de correo electrónico asociada con tu cuenta de usuario en cualquier momento. +redirect_from: + - /articles/changing-your-primary-email-address +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% note %} + +**Nota:** No puedes cambiar tu dirección de correo electrónico primaria a una que ya se haya configurado como tu dirección de respaldo. + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +3. Si deseas agregar una nueva dirección de correo electrónico para que sea tu dirección principal de correo electrónico, en "Add email address" (Agregar dirección de correo electrónico), escribe una nueva dirección de correo electrónico y haz clic en **Add** (Agregar). ![Botón Add another email address (Agregar otra dirección de correo electrónico)](/assets/images/help/settings/add_another_email_address.png) +4. En "Primary email address" (dirección principal de correo electrónico), usa el menú desplegable para hacer clic en la dirección de correo electrónico que deseas establecer como tu dirección principal de correo electrónico, y haz clic en **Save** (Guardar). ![Botón Set as primary (Establecer como principal)](/assets/images/help/settings/set_as_primary_email.png) +5. Para eliminar la dirección de correo electrónico antigua de tu cuenta, junto dicha dirección, da clic en +{% octicon "trashcan" aria-label="The trashcan symbol" %}. +{% if currentVersion == "free-pro-team@latest" %} +6. Verifica tu nueva dirección principal de correo electrónico. Sin una dirección de correo electrónico verificada, no podrás utilizar todas las +características de {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". +{% endif %} + +### Further reading + +- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md new file mode 100644 index 0000000000000..f5e03724bb650 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -0,0 +1,60 @@ +--- +title: Convertir un usuario en una organización +redirect_from: + - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization/ + - /articles/explaining-the-account-transformation-warning/ + - /articles/converting-a-user-into-an-organization +intro: Puedes convertir tu cuenta de usuario en una organización. Esto permite que haya más permisos granulares para repositorios que pertenecen a la organización. +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% warning %} + +**Advertencia**: Antes de convertir un usuario en una organización, ten en cuenta estos puntos: + + - **Ya no** podrás iniciar sesión con la cuenta de usuario convertida. + - **Ya no** podrás crear o modificar gists que pertenecen a la cuenta de usuario convertida. + - Una organización **no puede** volver a convertirse en un usuario. + - Las llaves SSH, tokens de OAuth, perfiles de trabajo, reacciones, y el resto de la información asociada con el usuario, **no** se transferirán a la organización. Esto es solo true para la cuenta de usuario que se convertirá, no para cualquiera de los colaboradores de la cuenta del usuario. + - Todas las confirmaciones realizadas a la cuenta del usuario convertida **ya no se asociarán** con esa cuenta. Las confirmaciones **permanecerán** intactas. + +{% endwarning %} + +### Conservar la cuenta de usuario personal y crear una nueva organización manualmente + +Si deseas que tu organización tenga el mismo nombre que estás usando actualmente para tu cuenta personal, o si deseas que la información de la cuenta del usuario personal permanezca intacta, debes crear una organización nueva y trasnferirla a tus repositorios en lugar de convertir tu cuenta de usuario en una organización. + +1. Para conservar el nombre de la cuenta de usuario para uso personal, [cambia el nombre de tu cuenta de usuario personal](/articles/changing-your-github-username) por uno nuevo y maravilloso. +2. [Crea una nueva organización](/articles/creating-a-new-organization-from-scratch) con el nombre original de tu cuenta de usuario personal. +3. [Transfiere tus repositorios](/articles/transferring-a-repository) a tu nueva cuenta de la organización. + +### Convertir tu cuenta personal en una organización automáticamente + +Puedes convertir tu cuenta de usuario personal directamente en una organización. Convertir tu cuenta: + - Preserva los repositorios ya que no tienen la necesidad de ser transferidos a otra cuenta manualmente + - Invita automáticamente a que los colaboradores se unan a los equipos con permisos equivalentes a los que tenían antes + {% if currentVersion == "free-pro-team@latest" %}- Para las cuentas de usuario en {% data variables.product.prodname_pro %}, la facturación se trasladará automáticamente a [el {% data variables.product.prodname_team %} de pago](/articles/about-billing-for-github-accounts) sin que sea necesario volver a ingresar la información de pago, ajustar tu ciclo de facturación, o pagar doble en cualquier momento{% endif %} + +1. Crea una nueva cuenta personal, que usarás para iniciar sesión en GitHub y acceder a la organización y a tus repositorios después de la conversión. +2. [Sal de todas las organizaciones](/articles/removing-yourself-from-an-organization) a las que se ha unido la cuenta de usuario que estás convirtiendo. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +5. En "Transform account" (Transformar cuenta), haz clic en **Turn into an organization** (Convertir en una organización). ![Botón para convertir la organización](/assets/images/help/settings/convert-to-organization.png) +6. En el cuadro de diálogo Account Transformation Warning (Advertencia de transformación de la cuenta), revisa y confirma la confirmación. Ten en cuenta que la información en este cuadro es la misma que la advertencia en la parte superior de este artículo. ![Advertencia de conversión](/assets/images/help/organizations/organization-account-transformation-warning.png) +7. En la página "Transform your user into an organization" (Transformar tu usuario en una organización), debajo de "Choose an organization owner" (Elegir un propietario de la organización), elige la cuenta personal secundaria que creaste en la sección anterior u otro usuario en quien confías para administrar la organización. ![Página Add organization owner (Agregar propietario de la organización)](/assets/images/help/organizations/organization-add-owner.png) +8. Escoge la nueva suscripción de la organización y escribe tu información de facturación si se te solicita. +9. Haz clic en **Create Organization** (Crear organización). +10. Inicia sesión en la nueva cuenta de usuario que creaste en el paso uno, luego usa el cambiador de contexto para acceder a la organización nueva. + +{% tip %} + +**Sugerencia**: Cuando conviertas una cuenta de usuario en una organización, agregaremos los colaboradores a los repositorios que le pertenecen a la cuenta de la nueva organización como *colaboradores externos*. Luego puedes invitar a los *colaboradores externos* para que se conviertan en miembros de la organización nueva, si así lo deseas. Para obtener más información, consulta "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." + +{% endtip %} + +### Further reading +- "[Configurar equipos](/articles/setting-up-teams)" +{% if currentVersion == "free-pro-team@latest" %}- "[Invitar usuarios para que se unan a tu organización](/articles/inviting-users-to-join-your-organization)"{% endif %} +- "[Acceder a una organización](/articles/accessing-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md new file mode 100644 index 0000000000000..359da7342b839 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md @@ -0,0 +1,44 @@ +--- +title: Eliminar tu cuenta de usuario +intro: 'Puedes eliminar tu cuenta de usuario de {% data variables.product.product_name %} en cualquier momento.' +redirect_from: + - /articles/deleting-a-user-account/ + - /articles/deleting-your-user-account +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +Al eliminar tu cuenta de usuario se eliminan todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta. {% if currentVersion == "free-pro-team@latest" %} Las propuestas y solicitudes de cambios que has creado y los comentarios que has hecho en los repositorios que pertenecen a otros usuarios no se borrarán - en vez de esto, se asociarán con nuestro [Usuario fantasma](https://github.com/ghost).{% else %}Las propuestas y solicitudes de cambios que has creado y los comentarios que has hecho en los repositorios que pertenecen a otros usuarios no se borrarán.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} El nombre de cuenta también estará disponible para cualquiera lo utilice en una cuenta nueva, y dejaremos de facturarte por él. La dirección de correo electrónico asociada con la cuenta pasará a estar disponible para el uso por parte de otra cuenta de {% data variables.product.product_name %}. {% endif %} + +Si eres el único propietario de una organización, debes transferir la propiedad a otra persona o eliminar la organización primero para que puedas eliminar tu cuenta de usuario. Si hay otros propietarios de la organización, debes eliminarte de la organización primero para que puedas eliminar tu cuenta de usuario. + +Para obtener más información, consulta: +- "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)" +- "[Eliminar una cuenta de la organización](/articles/deleting-an-organization-account)" +- "[Eliminarte de una organización](/articles/removing-yourself-from-an-organization/)" + +### Copias de seguridad de los datos de tu cuenta + +Antes de eliminar tu cuenta de usuario, haz una copia de todos los repositorios, bifurcaciones privadas, wikis, propuestas y solicitudes de extracción que sean propiedad de tu cuenta. + +{% warning %} + +**Advertencia:** Una vez que tu cuenta de usuario se ha eliminado, GitHub no puede restaurar su contenido. + +{% endwarning %} + +### Eliminar tu cuenta de usuario + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.account_settings %} +3. En la parte inferior de la página de configuración de la cuenta, en "Eliminar cuenta", haz clic en **Eliminar tu cuenta**. Para que puedas eliminar tu cuenta de usuario, antes debes tener en cuenta lo siguiente: + - Si eres el único propietario de la organización, debes transferir la propiedad a otra persona o eliminar tu organización. + - Si hay otros propietarios de la organización dentro de la organización, debes eliminarte de la organización. ![Botón Eliminación de cuenta](/assets/images/help/settings/settings-account-delete.png) +4. En el cuadro de diálogo "Make sure you want to do this" (Asegúrate de que quieres hacer esto), realiza los siguientes pasos para confirmar que comprendes lo que sucede cuando se elimina tu cuenta: ![Diálogo de confirmación para eliminar cuenta](/assets/images/help/settings/settings-account-deleteconfirm.png) + {% if currentVersion == "free-pro-team@latest" %}- Recuerda que todos los repositorios, bifurcaciones o repositorios privados, wikis, propuestas, solicitudes de cambios y páginas que pertenezcan a tu cuenta se borrarán, tu facturación finalizará, y tu nombre de usuario estará disponible para que cualquiera lo use en {% data variables.product.product_name %}. + {% else %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. + {% endif %}- En el primer campo, escribe tu nombre de usuario de {% data variables.product.product_name %} o tu correo electrónico. + - En el segundo campo, escribe la frase que se indica. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/index.md new file mode 100644 index 0000000000000..53bac8a249c0c --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -0,0 +1,51 @@ +--- +title: Configurar y administrar tu cuenta de usuario de GitHub +shortTitle: Cuentas de usuario +redirect_from: + - /categories/setting-up-and-managing-your-github-user-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /managing-user-account-settings %} + {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} + {% link_in_list /changing-your-github-username %} + {% link_in_list /merging-multiple-user-accounts %} + {% link_in_list /converting-a-user-into-an-organization %} + {% link_in_list /deleting-your-user-account %} + {% link_in_list /permission-levels-for-a-user-account-repository %} + {% link_in_list /permission-levels-for-user-owned-project-boards %} + {% link_in_list /managing-the-default-branch-name-for-your-repositories %} + {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} + {% link_in_list /integrating-jira-with-your-personal-projects %} + {% link_in_list /best-practices-for-leaving-your-company %} + {% link_in_list /what-does-the-available-for-hire-checkbox-do %} +{% topic_link_in_list /managing-email-preferences %} + {% link_in_list /adding-an-email-address-to-your-github-account %} + {% link_in_list /changing-your-primary-email-address %} + {% link_in_list /setting-a-backup-email-address %} + {% link_in_list /setting-your-commit-email-address %} + {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} + {% link_in_list /remembering-your-github-username-or-email %} + {% link_in_list /types-of-emails-github-sends %} + {% link_in_list /managing-marketing-emails-from-github %} +{% topic_link_in_list /managing-access-to-your-personal-repositories %} + {% link_in_list /inviting-collaborators-to-a-personal-repository %} + {% link_in_list /removing-a-collaborator-from-a-personal-repository %} + {% link_in_list /removing-yourself-from-a-collaborators-repository %} + {% link_in_list /maintaining-ownership-continuity-of-your-user-accounts-repositories %} +{% topic_link_in_list /managing-your-membership-in-organizations %} + {% link_in_list /about-organization-membership %} + {% link_in_list /accessing-an-organization %} + {% link_in_list /viewing-peoples-roles-in-an-organization %} + {% link_in_list /requesting-organization-approval-for-oauth-apps %} + {% link_in_list /publicizing-or-hiding-organization-membership %} + {% link_in_list /managing-your-scheduled-reminders %} + {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md new file mode 100644 index 0000000000000..1d8cf2bc67ce9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -0,0 +1,25 @@ +--- +title: Integrar Jira con tus proyectos personales +intro: 'Puedes integrar Jira Cloud a tu cuenta de usuario para escanear confirmaciones y solicitudes de extracción, creando los metadatos e hipervínculos correspondientes en cualquier propuesta de Jira mencionada.' +redirect_from: + - /articles/integrating-jira-with-your-personal-projects +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +3. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_oauth_app %}s**. ![Pestaña de {% data variables.product.prodname_oauth_app %}s en la barra lateral izquierda](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. Haz clic en **Register a new application** (Registrar una aplicación nueva). +4. En **Application name** (Nombre de la aplicación), escribe "Jira". +5. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira. +6. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira. +7. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png) +8. En **Developer applications** (Aplicaciones del programador), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### Further reading + +- ["Integrar Jira al tablero de proyecto de tu organización"](/articles/integrating-jira-with-your-organization-project-board) +- Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md new file mode 100644 index 0000000000000..1a249d97aa0bb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -0,0 +1,56 @@ +--- +title: Invitar colaboradores a un repositorio personal +intro: 'Puedes {% if currentVersion == "free-pro-team@latest" %}Invitar usuarios para que se conviertan en{% else %}agregar usuarios como{% endif %} colaboradores en tu repositorio personal.' +redirect_from: + - /articles/how-do-i-add-a-collaborator/ + - /articles/adding-collaborators-to-a-personal-repository/ + - /articles/inviting-collaborators-to-a-personal-repository +product: '{% data reusables.gated-features.user-repo-collaborators %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los repositorios que son propiedad de una organización pueden conceder acceso más pormenorizado. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.product_name %}](/articles/access-permissions-on-github)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +{% data reusables.organizations.org-invite-expiration %} +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** {% data variables.product.company_short %} limita la cantidad de personas que se pueden invitar a un repositorio dentro de un período de 24 horas. Si excedes este límite, espera 24 horas o crea una organización para colaborar con más personas. + +{% endnote %} + +{% endif %} + +1. Solicita el nombre de usuario de la persona que estás invitando como colaboradora. + +{% if currentVersion == "free-pro-team@latest" %} Si no tienen un nombre de usuario aún, pueden registrarse en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Registrarse para obtener una cuenta nueva de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)".{% endif %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.repositories.navigate-to-manage-access %} +1. Da clic en **Invitar un colaborador**. ![botón de "invitar un colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png) +2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png) +3. Da clic en **Añadir NOMBRE a REPOSITORIO**. ![Botón para añadir un colaborador](/assets/images/help/repository/add-collaborator-user-repo.png) +{% else %} +5. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Barra lateral de configuraciones del repositorio con Colaboradores resaltados](/assets/images/help/repository/user-account-repo-settings-collaborators.png) +6. En "Colaboradores", comienza a escribir el nombre de usuario del colaborador. +7. Selecciona el nombre de usuario del colaborador del menú desplegable. ![Menú desplegable de la lista de colaboradores](/assets/images/help/repository/repo-settings-collab-autofill.png) +8. Haz clic en **Add collaborator** (Agregar colaborador). ![Botón Add (Agregar)](/assets/images/help/repository/repo-settings-collab-add.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +9. El usuario recibirá un correo electrónico invitándolo al repositorio. Una vez que acepte la invitación, tendrá acceso de colaborador a tu repositorio. +{% endif %} + +### Further reading + +- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" +- "[Eliminar un colaborador de un repositorio personal](/articles/removing-a-collaborator-from-a-personal-repository)" +- "[Eliminarte a ti mismo del repositorio de un colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)" +- "[Organizar los miembros en equipos](/articles/organizing-members-into-teams)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md new file mode 100644 index 0000000000000..e4e46560131b9 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md @@ -0,0 +1,30 @@ +--- +title: Mantener la continuidad de la propiedad para los repositorios de tu cuenta de usuario +intro: Puedes invitar a alguien para administrar los repositorios que pertenezcan a tu usuario si no puedes hacerlo tú mismo. +versions: + free-pro-team: '*' +--- + +### Acerca de los sucesores + +Te recomendamos invitar a otro usuario de {% data variables.product.company_short %} para que sea tu sucesor y que así administre los repositorios que te pertenezcan si tú no puedes hacerlo. Como sucesores, tendrán permisos para: + +- Archivar tus repositorios públicos. +- Transferir tus repositorios públicos a su propia cuenta de usuario. +- Transferir tus repositorios públicos a una organización donde puedan crear repositorios. + +Los sucesores no pueden iniciar sesión en tu cuenta. + +Un sucesor designado puede administrar tus repositorios públicos después de presentar un certificado de defunción y esperar por 7 días o presentar un obituario y esperar por 21 días. Para obtener más información, consulta la sección "[Política de Usuario Finado de {% data variables.product.company_short %}](/github/site-policy/github-deceased-user-policy)". + +Para solicitar acceso para administrar los repositorios como sucesor, contacta a[Soporte de GitHub](https://support.github.com/contact). + +### Invitar un sucesor +La persona que invites para ser tu sucesor deberá tener una cuenta de {% data variables.product.company_short %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.account_settings %} +3. Debajo de "Ajustes de sucesor", para invitar a un sucesor, comienza a escribir el nombre de usuario, nombre completo, o dirección de correo electrónico. Posteriormente, da clic en su nombre cuando éste aparezca. ![Campo de bísqueda para invitación de sucesor](/assets/images/help/settings/settings-invite-successor-search-field.png) +4. Da clic en **Agregar sucesor**. +{% data reusables.user_settings.sudo-mode-popup %} +5. El usuario que has invitado se listará como "Pendiente" hasta que acepte convertirse en tu sucesor. ![Invitación de sucesor pendiente](/assets/images/help/settings/settings-pending-successor.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md new file mode 100644 index 0000000000000..f974caf14d979 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md @@ -0,0 +1,15 @@ +--- +title: Administrar el acceso a tus repositorios personales +intro: Puedes otorgarle a las personas acceso de colaborador a los repositorios que sean propiedad de tu cuenta personal. +redirect_from: + - /categories/101/articles/ + - /categories/managing-repository-collaborators/ + - /articles/managing-access-to-your-personal-repositories +product: '{% data reusables.gated-features.user-repo-collaborators %}' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md new file mode 100644 index 0000000000000..ea6fac568d793 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md @@ -0,0 +1,33 @@ +--- +title: Administrar el acceso a los tableros de proyecto de tu cuenta de usuario +intro: 'Como propietario de un tablero de proyecto, puedes agregar o eliminar a un colaborador y personalizar sus permisos a un tablero de proyecto.' +redirect_from: + - /articles/managing-project-boards-in-your-repository-or-organization/ + - /articles/managing-access-to-your-user-account-s-project-boards + - /articles/managing-access-to-your-user-accounts-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Un colaborador es una persona que tiene permisos a tablero de proyecto de tu propiedad. Un colaborador tendrá como predeterminado permisos de acceso de lectura. Para obtener más información, consulta "[Niveles de permiso para tableros de proyecto propiedad del usuario](/articles/permission-levels-for-user-owned-project-boards)." + +### Invitar a colaboradores a un tablero de proyecto propiedad del usuario + +1. Navegua hasta el tablero de proyecto donde deseas agregar a un colaborador. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +5. Debajo de "Buscar por nombre de usuario, nombre completo o dirección de correo electrónico", teclea el nombre del colaborador, nombre de usuario, o +correo electrónico de {% data variables.product.prodname_dotcom %}. + ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +7. Por defecto, el nuevo colaborador tiene permisos de lectura. De forma opcional, al lado del nombre del nuevo colaborador, utiliza el menú desplegable y elige un nivel de permiso diferente. ![Sección Colaboradores con el menú desplegable de permisos seleccionado](/assets/images/help/projects/user-project-collaborators-edit-permissions.png) + +### Eliminar a un colaborador de un tablero de proyecto propiedad del usuario + +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.remove-collaborator %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md new file mode 100644 index 0000000000000..de47363f4b016 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md @@ -0,0 +1,13 @@ +--- +title: Administrar preferencias de correo electrónico +intro: 'Puedes agregar o cambiar las direcciones de correo electrónico asociadas con tu cuenta {% data variables.product.product_name %}. También puedes administrar correos electrónicos que recibes de {% data variables.product.product_name %}.' +redirect_from: + - /categories/managing-email-preferences/ + - /articles/managing-email-preferences +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md new file mode 100644 index 0000000000000..86c49a8733e13 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md @@ -0,0 +1,26 @@ +--- +title: Administrar correos electrónicos de marketing de GitHub +intro: 'Además de las notificaciones y de los correos electrónicos de la cuenta, {% data variables.product.prodname_dotcom %} ocasionalmente envía correos electrónicos de marketing con novedades e información sobre nuestros productos. Si cancelas la suscripción de los correos electrónicos de marketing existentes, no se te incluirá en las futuras campañas excepto que cambies tus configuraciones de correo electrónico {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /articles/managing-marketing-emails-from-github +versions: + free-pro-team: '*' +--- + +### Cancelar la suscripción de los correos electrónicos de marketing de {% data variables.product.prodname_dotcom %} + +{% tip %} + +**Sugerencia:** si cancelas la suscripción de todos los correos electrónicos de marketing y después te suscribes en el boletín informativo de Explore, solo recibirás el boletín informativo de Explore y no recibirás otros correos electrónicos de marketing. + +{% endtip %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +3. Dentro de *Email preferences (Preferencias de correo electrónico)*, selecciona **Only receive account related emails, and those I subscribe to (Recibir únicamente correos electrónicos relacionados con la cuenta y aquellos a los cuales me suscribo)**. ![Captura de pantalla de la cancelación de la suscripción de un correo electrónico de marketing](/assets/images/help/notifications/email_preferences.png) +4. Haz clic en **Save email preferences (Guardar preferencias de correo electrónico)**. ![Botón para guardar las preferencias de correo electrónico](/assets/images/help/notifications/save_email_preferences.png) + +### Further reading + +- "[Tipos de correos electrónicos que envía GitHub](/articles/types-of-emails-github-sends)" +- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md new file mode 100644 index 0000000000000..78528c1cf8cd3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md @@ -0,0 +1,38 @@ +--- +title: Administrar la configuración de seguridad y análisis para tu cuenta de usuario +intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tus proyectos dentro de {% data variables.product.prodname_dotcom %}.' +versions: + free-pro-team: '*' +--- + +### Acerca de la administración de los parámetros de seguridad y análisis + +{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar tus repositorios. Este tema te muestra cómo puedes administrar las características de seguridad y análisis para todos tus repositorios existentes o nuevos. + +Aún puedes administrar las características de seguridad y análisis para los repositorios individuales. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". + +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} + +{% data reusables.security.security-and-analysis-features-enable-read-only %} + +Para encontrar un resumen de la seguridad a nivel de repositorio, consulta la sección "[Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)". + +### Habilitar o inhabilitar las características para los repositorios existentes + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security-analysis %} +3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png) +6. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png) +7. Da clic en **Inhabilitar CARACTERÍSTICA** o **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios que te pertenezcan. ![Botón para inhabilitar o habilitar la característica](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png) + +### Habilitar o inhabilitar las características para los repositorios nuevos + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.security-analysis %} +3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, habilítala o inhabilítala para los repositorios nuevos en tu organización. ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Further reading + +- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Administrar las vulnerabilidades en las dependencias de tu proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" +{% if currentVersion == "free-pro-team@latest" %}- "[Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md new file mode 100644 index 0000000000000..a5bb049098fa3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -0,0 +1,26 @@ +--- +title: Administrar el nombre de la rama predeterminada para tus repositorios +intro: 'Puedes configurar el nombre de la rama predeterminada de los repositorios nuevos que crees en {% data variables.product.product_location %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +--- + +### Acerca de la administración del nombre de la rama predeterminada + +Cuando creas un repositorio nuevo en {% data variables.product.product_location %}, éste contiene una rama predeterminada. Puedes cambiar el nombre que {% data variables.product.product_name %} usa para dicha rama en los repositorios que crees. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". + +{% data reusables.branches.change-default-branch %} + +### Configurar el nombre de la rama predeterminada + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.repo-tab %} +3. Debajo de "Rama predeterminada del repositorio", da clic en **Cambiar el nombre de la rama predeterminada ahora**. ![Botón de ignorar](/assets/images/help/settings/repo-default-name-button.png) +4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/settings/repo-default-name-text.png) +5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/settings/repo-default-name-update.png) + +### Further reading + +- "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md new file mode 100644 index 0000000000000..1c17795cb0bcd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md @@ -0,0 +1,14 @@ +--- +title: Administrar las configuraciones del usuario de la cuenta +intro: 'Puedes cambiar varias configuraciones de tu cuenta personal, lo que incluye cambiar tu nombre de usuario y eliminar tu cuenta.' +redirect_from: + - /categories/29/articles/ + - /categories/user-accounts/ + - /articles/managing-user-account-settings +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md new file mode 100644 index 0000000000000..cec417616f4be --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md @@ -0,0 +1,12 @@ +--- +title: Administrar tu membresía en organizaciones +intro: 'Si eres un miembro de una organización, puedes publicar u ocultar tu membresía, ver los roles de otras personas y eliminarte de una organización.' +mapTopic: verdadero +redirect_from: + - /articles/managing-your-membership-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md new file mode 100644 index 0000000000000..2f77eb4cc1529 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -0,0 +1,50 @@ +--- +title: Administrar tus recordatorios programados +intro: Obtén recordatorios en Slack cuando tú o tu equipo tenga solicitudes de extracción pendientes de revisión. +versions: + free-pro-team: '*' +--- + +### Acerca de los recordatorios programados para usuarios + +Los recordatorios programados se utilizan para garantizar que los usuarios se enfoquen en las solicitudes de revisión más importantes que requieren de su atención. Los recordatorios programados para solicitudes de extracción te enviarán un mensaje en Slack con las solicitudes de extracción que estén abiertas y necesiten de tu revisión en un periodo específico. Por ejemplo, puedes configurar tus recordatorios programados para que te envíen un mensaje en Slack cada mañana a las 10 AM con las solicitudes de extracción que requieren de tu revisión o de la de alguno de tus equipos. + +Para ciertos eventos, también puedes habilitar las alertas en tiempo real para los recordatorios programados. Las alertas en tiempo real se envían a tu canal de Slack tan pronto se suscita un evento importante, tal como cuando se te asigna una revisión. + +Puedes configurar recordatorios programados para solicitudes de revisión a nivel personal o a nivel de equipo para las solicitudes de extracción en las organizaciones de las cuales eres miembro. Antes de que puedas crear un recordatorio programado para ti mismo, un propietario de la organización debe autorizar tu espacio de trabajo en Slack. Para obtener más información, consulta la sección "[Administrar recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)". + +### Crear recordatorios programados para tu cuenta de usuario + +{% data reusables.user_settings.access_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) +3. Da clic en **Editar** a un costado de la organización para la cual quieres programar un recordatorio. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) +{% data reusables.reminders.add-reminder %} +{% data reusables.reminders.authorize-slack %} +{% data reusables.reminders.days-dropdown %} +{% data reusables.reminders.times-dropdowns %} +8. Opcionalmente, para recibir recordatorios programados para las revisiones a las cuales se te ha asignado, selecciona **Revisar las solicitudes que se te han asignado**. ![Casilla de revisar las solicitudes que se te han asignado](/assets/images/help/profile/scheduled-reminders-your-requests.png) +9. Opcionalmente, para recibir los recordatorios programados para las revisiones que se han asignado a algún equipo del cual seas miembro, selecciona **Revisar solicitudes asignadas a tu equipo**. ![Casilla de revisar las solicitudes que se han asignado a tu equipo](/assets/images/help/profile/scheduled-reminders-your-team-requests.png) +{% data reusables.reminders.real-time-alerts %} +![Casilla para habilitar las alertas en tiempo real](/assets/images/help/settings/scheduled-reminders-real-time-alerts-personal.png) +{% data reusables.reminders.create-reminder %} + +### Administrar recordatorios programados para tu cuenta de usuario +{% data reusables.user_settings.access_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) +3. Da clic en **Editar** a un costado de la organización para la cual quieres editar los recordatorios programados. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Borrar recordatorios programados para tu cuenta de usuario +{% data reusables.user_settings.access_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) +3. Da clic en **Editar** a un costado de la organización para la cual quieres borrar un recordatorio. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) +{% data reusables.reminders.delete %} + +### Further reading + +- "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" +- "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000000..080a8328c265e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Administrar la configuración de tu tema +intro: Puedes administrar la vista que tienes de {% data variables.product.product_name %} si configuras una preferencia de tema que ya sea se acople a la configuración de tu sistema o siempre utilice el modo claro u oscuro. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** La configuración de tema se encuentra actualmente en beta y está sujeta a cambios. + +{% endnote %} + +Para obtener elecciones y flexibilidad en la forma y momento de utilizar {% data variables.product.product_name %}, puedes configurar los ajustes de tema para cambiar la forma en la que ves a {% data variables.product.product_name %}. Puedes elegir de entre dos temas, claro y oscuro, o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. Algunos desarrolladores utilizan el tema oscuro por sus preferencias personales, para reducir el consumo de energía en algunos dispositivos, o para reducir el cansancio de los ojos en las condiciones de iluminación baja. + +{% data reusables.user_settings.access_settings %} +1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Debajo de "Tema", selecciona una preferencia de tema. ![Botones radiales para la configuración de tema](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### Further reading + +- "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md new file mode 100644 index 0000000000000..43849d1e3e22b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md @@ -0,0 +1,24 @@ +--- +title: Fusionar cuentas de usuarios múltiples +intro: 'Si tienes cuentas separadas para uso laboral y personal, puedes fusionar las cuentas.' +redirect_from: + - /articles/can-i-merge-two-accounts/ + - /articles/keeping-work-and-personal-repositories-separate/ + - /articles/merging-multiple-user-accounts +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** recomendamos utilizar únicamente una cuenta de usuario para administrar los repositorios personales y laborales. + +{% endtip %} + +1. [Transfiere cualquier repositorio](/articles/how-to-transfer-a-repository) desde la cuenta que deseas eliminar a la cuenta que deseas mantener. También se transfieren propuestas, solicitudes de extracción y wikis. Verifica que los repositorios existan en la cuenta que deseas mantener. +2. [Actualiza las URL remotas](/articles/changing-a-remote-s-url) en cualquier clon local de los repositorios que se movieron. +3. [Elimina la cuenta](/articles/deleting-your-user-account) que ya no deseas utilizar. + +### Further reading + +- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md new file mode 100644 index 0000000000000..f25fe10ba8c0b --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -0,0 +1,87 @@ +--- +title: Niveles de permiso para un repositorio de cuenta de usuario +intro: 'Un repositorio que pertenece a una cuenta de usuario tiene dos niveles de permiso: propietario del repositorio y colaboradores.' +redirect_from: + - /articles/permission-levels-for-a-user-account-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los niveles de permisos para un repositorio de una cuenta de usuario + +Los repositorios que pertenecen a las cuentas de usuario tienen un propietario. Los permisos de propiedad no pueden compartirse con otra cuenta de usuario. + +También puedes {% if currentVersion == "free-pro-team@latest" %}invitar{% else %}agregar{% endif %} usuarios de {% data variables.product.product_name %} a tu repositorio como colaboradores. Para obtener más información, consulta la sección "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)". + +{% tip %} + +**Tip:** Si necesitas un acceso más granular para un repositorio que le pertenezca a tu cuenta de usuario, considera transferirlo a una organización. Para obtener más información, consulta "[Transferir un repositorio](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)". + +{% endtip %} + +### Acceso de propietarios a un repositorio que pertenezca a una cuenta de usuario + +El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes. + +| Acción | Más información | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| {% if currentVersion == "free-pro-team@latest" %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %} | | +| "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | +| Cambiar la visibilidad del repositorio | "[Configurar la visibilidad del repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} +| Limitar las interacciones con el repositorio | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" | +| Eliminar el repositorio | "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)" | +| Administrar los temas del repositorio | "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} +| Administrar la seguridad y la configuración de análisis del repositorio | "[Administrar la configuración de análisis y seguridad de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Habilitar la gráfica de dependencias para un repositorio privado | "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Borrar paquetes | "[Borrar un paquete](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalizar la vista previa de las redes sociales de tu repositorio](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| Crear una plantilla del repositorio | "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| Recibir | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} para las dependencias vulnerables | "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Administrar el uso de datos para un repositorio privado | "[Administrar la configuración del uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} +| Definir propietarios del código para un repositorio | "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Archivar el repositorio | "[Acerca de archivar los repositorios](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} +| Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Mostrar el botón del patrocinador | "[Mostrar un botón de patrocinador en tu repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | +| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} + +### Acceso de colaborador para un repositorio que pertenezca a una cuenta de usuario + +Los colaboradores de un repositorio personal pueden extraer (leer) el contienido del mismo y subir (escribir) los cambios al repositorio. + +{% note %} + +**Nota:** en un repositorio privado, los propietarios del repositorio solo pueden otorgar acceso de escritura a los colaboradores. Los colaboradores no pueden tener acceso de solo lectura a los repositorio propiedad de una cuenta de usuario. + +{% endnote %} + +Los colaboradores también pueden realizar las siguientes acciones. + +| Acción | Más información | +|:-------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bifurcar el repositorio | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio |
  • "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"
  • "[Comentar en una solilcitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Administrar los comentarios perturbadores](/github/building-a-strong-community/managing-disruptive-comments)"
| +| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administrar tu trabajo con las propuestas](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetar las propuestas y solicitudes de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Administrar hitos para las propuestas y solicitudes de cambios en el repositorio | "[Crear y editar hitos para propuestas y solicitudes de extracción](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Marcar una propuesta o solicitud de cambios en el repositorio como duplicada | "[Acerca de las propuestas y soicitudes de cambio duplicadas](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Crear, fusionar y cerrar las solicitudes de cambios en el repositorio | "[Proponer cambios en tu trabajo con solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" %} +| Habilitar e inhabilitar la fusión automática para una solicitud de cambios | "[Fusionar automáticamente una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} +| Aplicar los cambios sugeridos a las solicitudes de cambios en el repositorio | "[Incorporar retroalimentación en tu solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Crear una solicitud de cambios desde una bifurcación del repositorio | "[Crear una solicitud de extracción desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Emitir una revisión de una solicitud de cambios que afecte la capacidad de fusión de una solicitud de cambios | "[Revisar los cambios propuestos en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Crear y editar un wiki para el repositorio | "[Acerca de los wikis](/github/building-a-strong-community/about-wikis)" | +| Crear y editar los lanzamientos del repositorio | "[Administrar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Actuar como propietario del código del repositorio | "[Acerca de los propietarios del código](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} +| Publicar, ver o instalar paquetes | "[Publicar y mantener paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Eliminarse como colaboradores del repositorio | "[Eliminarte a ti mismo del repositorio de un colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | + +### Further reading + +- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md new file mode 100644 index 0000000000000..199ddc22634eb --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -0,0 +1,58 @@ +--- +title: Niveles de permiso para tableros de proyecto propiedad del usuario +intro: 'Un tablero de proyecto propiedad de una cuenta de usuario tiene dos niveles de permiso: el del propietario del tablero de proyecto y el de los colaboradores.' +redirect_from: + - /articles/permission-levels-for-user-owned-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Resumen de permisos + +Solamente hay un único propietario de un tablero de proyecto propiedad de un usuario; este permiso no puede compartirse con otra cuenta de usuario. Además del propietario, otras personas pueden colaborar en tableros de proyecto. + +Hay tres niveles de permisos para los colaboradores de un tablero de proyecto: + +{% data reusables.project-management.project-board-permissions %} + +### Permisos de propietario y de administrador para un tablero de proyecto propiedad del usuario + +El propietario del tablero de proyecto y los colaboradores con acceso de administrador tienen control completo del tablero de proyecto. Además de todos los permisos admitidos por los colaboradores del tablero de proyecto, un propietario y un colaborador de un tablero de proyecto con acceso de administrador pueden: + +- [Administrar, ver y agregar colaboradores](/articles/managing-access-to-your-user-account-s-project-boards) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) +- [Eliminar un tablero de proyecto](/articles/deleting-a-project-board/) +- [Cerrar un tablero de proyecto](/articles/closing-a-project-board/) +- [Volver a abrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board) + +### Permisos de lectura y escritura para un tablero de proyecto propiedad del usuario + +Los colaboradores con acceso de lectura a un tablero de proyecto propiedad del usuario pueden: + +- Ver un tablero de proyecto +- Copiar un tablero de proyecto +- Filtrar tarjetas en un tablero de proyecto + +Los colaboradores con acceso de escritura a un tablero de proyecto propiedad del usuario pueden: + +- Ver un tablero de proyecto +- Copiar un tablero de proyecto +- Filtrar tarjetas en un tablero de proyecto +- Editar un tablero de proyecto +- Vincular un repositorio a un tablero de proyecto +- Configurar la automatización de tableros de proyecto +- Copiar un tablero de proyecto +- Agregar propuestas y solicitudes de extracción a un tablero de proyecto +- Agregar notas a un tablero de proyecto +- Rastrear el avance de un tablero de proyecto +- Archivar tarjetas en un tablero de proyecto + +### Visibilidad del tablero de proyecto + +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Por defecto, los tableros de proyecto propiedad del usuario son privados. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". + +### Further reading + + - "[Administrar el acceso a los tableros de proyectos de tu cuenta de usuario](/articles/managing-access-to-your-user-account-s-project-boards)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md new file mode 100644 index 0000000000000..467650a795516 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md @@ -0,0 +1,23 @@ +--- +title: Divulgar u ocultar membresía de la organización +intro: 'Si te gustaría decirle al mundo a qué organizaciones perteneces, puedes mostrar los avatares de las organizaciones en tu perfil.' +redirect_from: + - /articles/publicizing-or-concealing-organization-membership/ + - /articles/publicizing-or-hiding-organization-membership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +![Casilla de perfil de organizaciones](/assets/images/help/profile/profile_orgs_box.png) + +### Cambiar la visibilidad de la membresía de tu organización + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Ubica tu nombre de usuario en la lista de miembros. Si la lista es grande, puedes buscar tu nombre de usuario en la casilla de búsqueda. ![Casilla de búsqueda de miembro de la organización](/assets/images/help/organizations/member-search-box.png) +5. En el menú a la derecha de tu nombre de usuario, elige una nueva opción de visibilidad: + - Para divulgar tu membresía, elige **Public (Pública)**. + - Para esconder tu membresía, elige **Private (Privada)**. ![Enlace de visibilidad de un miembro de la organización](/assets/images/help/organizations/member-visibility-link.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md new file mode 100644 index 0000000000000..867b5254d1ee5 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md @@ -0,0 +1,69 @@ +--- +title: Recordar tu nombre de usuario o correo electrónico de GitHub +intro: '¿Vas a iniciar sesión en {% data variables.product.product_location %} por primera vez después de un tiempo? Si es así, ¡bienvenido de nuevo! Si no puedes recordar tu {% data variables.product.product_name %} nombre de la cuenta de usuario, puedes intentar estos métodos para hacerlo.' +redirect_from: + - /articles/oh-noes-i-ve-forgotten-my-username-email/ + - /articles/oh-noes-i-ve-forgotten-my-username-or-email/ + - /articles/remembering-your-github-username-or-email +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +{% mac %} + +### Usuarios {% data variables.product.prodname_desktop %} + +1. En el menú de **GitHub Desktop** (GitHub Desktop), haz clic en **Preferences** (Preferencias). +2. En la ventana Preferences (Preferencias), comprueba lo siguiente: + - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas). + - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address). + +{% endmac %} + +{% windows %} + +### Usuarios {% data variables.product.prodname_desktop %} + +1. En el menú de **Archivo**, da clic en **Opciones**. +2. En la ventana Options (Opciones), comprueba lo siguiente: + - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas). + - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address). + +{% endwindows %} + +### Encontrar tu nombre de usuario en tu configuración `user.name` + +Durante la configuración, puede que debas [establecer tu nombre de usuario en Git](/articles/setting-your-username-in-git). En tal caso, puedes revisar el valor de este parámetro de configuración: + +```shell +$ git config user.name +# Ver el parámetro +YOUR_USERNAME +``` + +### Encontrar tu nombre de usuario en la URL de repositorios remotos + +Si tienes alguna copia local de los repositorios personales que has creado o bifurcado, puedes verificar la URL del repositorio remoto. + +{% tip %} + +**Sugerencia**: Este método solo funciona si tienes un repositorio original o tu propia bifurcación del repositorio de alguna otra persona. Si clonas el repositorio de alguna otra persona, se mostrará su nombre de usuario en lugar del tuyo. Del mismo modo, los repositorios de la organización mostrarán el nombre de la organización en lugar del de un usuario particular en la URL remota. + +{% endtip %} + +```shell +$ cd YOUR_REPOSITORY +# Cambia los directorios para el repositorio de Git inicializado +$ git remote -v +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) +``` + +Tu nombre de usuario es lo que le sigue inmediatamente a `https://{% data variables.command_line.backticks %}/`. + +{% if currentVersion == "free-pro-team@latest" %} +### Further reading + +- "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)" +{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md new file mode 100644 index 0000000000000..3425ee8383aa8 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md @@ -0,0 +1,39 @@ +--- +title: Eliminar un colaborador de un repositorio personal +intro: 'Cuando eliminas un colaborador de tu proyecto, pierde el acceso de lectura o escritura a tu repositorio. Si el repositorio es privado, y la persona creó una bifurcación, esa bifurcación también se elimina.' +redirect_from: + - /articles/how-do-i-remove-a-collaborator/ + - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository/ + - /articles/removing-a-collaborator-from-a-private-repository/ + - /articles/deleting-a-private-fork-of-a-private-user-repository/ + - /articles/how-do-i-delete-a-fork-of-my-private-repository/ + - /articles/removing-a-collaborator-from-a-personal-repository +product: '{% data reusables.gated-features.user-repo-collaborators %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Eliminar bifurcaciones de repositorios privados + +Aunque se borren las bifurcaciones de los repositorios privados cuando se elimina un colaborador, la persona seguirá teniendo todos los clones locales de tu repositorio. + +### Eliminar los permisos de colaborador de una persona que contribuye con un repositorio + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.repositories.navigate-to-manage-access %} +4. A la derecha del colaborador que quieres eliminar, da clic en +{% octicon "trashcan" aria-label="The trashcan icon" %}. + ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png) +{% else %} +3. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Pestaña Collaborators (Colaboradores)](/assets/images/help/repository/repo-settings-collaborators.png) +4. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Enlace Remove (Eliminar)](/assets/images/help/organizations/Collaborator-Remove.png) +{% endif %} + +### Further reading + +- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" +- "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md new file mode 100644 index 0000000000000..7bed26d1f89cf --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md @@ -0,0 +1,20 @@ +--- +title: Eliminarte del repositorio de un colaborador +intro: 'Si no quieres seguir siendo colaborador del repositorio de otra persona, te puedes eliminar.' +redirect_from: + - /leave-a-collaborative-repo/ + - /leave-a-repo/ + - /articles/removing-yourself-from-a-collaborator-s-repo/ + - /articles/removing-yourself-from-a-collaborator-s-repository + - /articles/removing-yourself-from-a-collaborators-repository +product: '{% data reusables.gated-features.user-repo-collaborators %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/settings-sidebar-repositories.png) +3. Junto al repositorio que quieres abandonar, haz clic en **Leave** (Abandonar). ![Botón Leave (Abandonar)](/assets/images/help/repository/repo-leave.png) +4. Lee la advertencia con atención, luego haz clic en "I understand, leave this repository" (Comprendo, abandonar este repositorio). ![Cuadro de diálogo con advertencia sobre el abandono](/assets/images/help/repository/repo-leave-confirmation.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md new file mode 100644 index 0000000000000..5ea20f687d4cd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md @@ -0,0 +1,27 @@ +--- +title: Eliminarte de una organización +intro: 'Si eres colaborador externo o miembro de una organización, puedes abandonar la organización en cualquier momento.' +redirect_from: + - /articles/how-do-i-remove-myself-from-an-organization/ + - /articles/removing-yourself-from-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Advertencia:** Si actualmente eres responsable de pagar {% data variables.product.product_name %} en tu organización, eliminarte de la organización **no** actualiza la información de facturación archivada de la organización. Si actualmente eres responsable de la facturación, **debes** hacer que otro propietario o gerente de facturación de la organización [actualice el método de pago de la organización](/articles/adding-or-editing-a-payment-method). + +Para obtener más información, consulta "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)". + +{% endwarning %} + +{% endif %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +3. En "Organizations" (Organizaciones), busca la organización de la que quieres eliminarte, luego haz clic en **Leave** (Abandonar). ![Botón Leave organization (Abandonar organización) con roles exhibidos](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps.md new file mode 100644 index 0000000000000..4f7dddd7a2e15 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps.md @@ -0,0 +1,23 @@ +--- +title: Solicitar aprobación de la organización para OAuth Apps +intro: 'Los miembros de la organización pueden solicitar que un propietario apruebe el acceso a los recursos de la organización para {% data variables.product.prodname_oauth_app %}.' +redirect_from: + - /articles/requesting-organization-approval-for-third-party-applications/ + - /articles/requesting-organization-approval-for-your-authorized-applications/ + - /articles/requesting-organization-approval-for-oauth-apps +versions: + free-pro-team: '*' +--- + +### Solicitar aprobación de la organización para una {% data variables.product.prodname_oauth_app %} que ya has autorizado para tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.access_applications %} +{% data reusables.user_settings.access_authorized_oauth_apps %} +3. En la lista de aplicaciones, haz clic en el nombre de la {% data variables.product.prodname_oauth_app %} para la que quieres solicitar acceso. ![Botón View application (Ver aplicación)](/assets/images/help/settings/settings-third-party-view-app.png) +4. Al lado de la organización a la que quieres que {% data variables.product.prodname_oauth_app %} acceda, haz clic en **Request access** (Solicitar acceso). ![Botón Request access (Solicitar acceso)](/assets/images/help/settings/settings-third-party-request-access.png) +5. Después de revisar la información acerca de solicitarle a {% data variables.product.prodname_oauth_app %} acceso, haz clic en **Request approval from owners** (Solicitar aprobación de los propietarios). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/settings/oauth-access-request-approval.png) + +### Further reading + +- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md new file mode 100644 index 0000000000000..b6a82d614b01d --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md @@ -0,0 +1,20 @@ +--- +title: Configurar una dirección de correo electrónico de respaldo +intro: Utiliza una dirección de correo electrónico de respaldo como un destino adicional para las notificaciones de seguridad relevantes para tu cuenta{% if currentVersion != "github-ae@latest" %} y para restablecer de forma segura tu contraseña si ya no puedes acceder a tu dirección de correo electrónico primaria{% endif %}. +redirect_from: + - /articles/setting-a-backup-email-address +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +3. Dentro de "Backup email address" (Dirección de correo electrónico de respaldo), selecciona la dirección que deseas configurar como tu dirección de correo electrónico de respaldo utilizando el menú desplegable. ![Dirección de correo electrónico de respaldo](/assets/images/help/settings/backup-email-address.png) +4. Haz clic en **Save ** (guardar). + +### Further reading + +- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" +- "[Actualizar tus credenciales de acceso de GitHub](/articles/updating-your-github-access-credentials/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md new file mode 100644 index 0000000000000..3f5698686558a --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md @@ -0,0 +1,98 @@ +--- +title: Configurar tu dirección de correo electrónico de confirmación +intro: 'Puedes configurar la dirección de correo electrónico que se utiliza para crear confirmaciones en {% data variables.product.product_name %} y en tu computadora.' +redirect_from: + - /articles/keeping-your-email-address-private/ + - /articles/setting-your-commit-email-address-on-github/ + - /article/about-commit-email-addresses/ + - /articles/git-email-settings/ + - /articles/setting-your-email-in-git/ + - /articles/set-your-user-name-email-and-github-token/ + - /articles/setting-your-commit-email-address-in-git/ + - /articles/setting-your-commit-email-address +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las dirección de correo electrónico de confirmación + +{% data variables.product.product_name %} utiliza tu dirección de correo electrónico de confirmación para asociar las confirmaciones con tu cuenta {% data variables.product.product_name %}. Puedes elegir la dirección de correo electrónico que se asociará con las confirmaciones que subes desde la línea de comando y las operaciones de Git con base en la web que realizas. + +Para las operaciones de Git con base en la web, puedes configurar tu dirección de correo electrónico de confirmación en {% data variables.product.product_name %}. Para las confirmaciones que subes desde la línea de comando, puedes configurar tu dirección de correo electrónico de confirmaciones en Git. + +{% if currentVersion == "free-pro-team@latest" %}Cualquier confirmación que hagas antes de cambiar tu dirección de correo electrónico para confirmaciones aún se asociará con tu dirección de correo electrónico anterior.{% else %}Después de cambiar tu dirección de correo electrónico para confirmaciones en {% data variables.product.product_name %}, la dirección nueva podrá visualizarse en todas tus operaciones web futuras de Git predeterminadamente. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociada a tu dirección de correo electrónico anterior.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %} + +{% endnote %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %}Si te gustaría mantener tu dirección de correo electrónico personal como privada, puedes utilizar una dirección de tipo `no-reply` que proporcione {% data variables.product.product_name %} para las confirmaciones. Para utilizar tu dirección de correo electrónico `noreply` para confirmaciones que subes desde la línea de comando, utiliza esa dirección de correo electrónico cuando configuras tu dirección de correo electrónico de confirmaciones en Git. Para utilizar tu dirección `noreply` para las operaciones de Git con base en la web, configura tu dirección de correo electrónico de confirmaciones en GitHub y elige **Keep my email address private (Mantener mi dirección de correo electrónico privada)**. + +También puedes elegir bloquear las confirmaciones que subes desde la línea de comando que muestra tu dirección de correo electrónico personal. Para obtener más información, consulta "[Bloquear las subidas de línea de comando que muestran tu correo electrónico personal](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %} + +Para garantizar que las confirmaciones se te atribuyan y aparezcan en tu gráfica de contribuciones, utiliza una dirección de correo electrónico que esté conectada a tu cuenta de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}, o a la dirección de tipo `noreply` que se te proporcionó en la configuración de correo electrónico{% endif %}. {% if currentVersion != "github-ae@latest" %}Para obtener más información, consulta la sección "[Agregar una dirección de correo electrónico a tu cuenta 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" %} + +{% note %} + +**Nota:** Si creaste tu cuenta de {% data variables.product.product_name %} _después_ del 18 de julio de 2017, tu dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} es un número de Id. de siete dígitos, y tu nombre de usuario tiene la forma de ID+username@users.noreply.github.com. Si creaste tu cuenta de {% data variables.product.product_name %} _antes del_ 18 de julio de 2017, tu dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} es tu nombre de usuario con la forma de username@users.noreply.github.com. Puedes obtener una dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} con base en el ID al seleccionar (o deseleccionar y volver a seleccionar) **Keep my email address private (Mantener mi dirección de correo electrónico privada)** en tus configuraciones. + +{% endnote %} + +Si utilizas tu dirección de correo electrónico `noreply` provista por {% data variables.product.product_name %} para realizar confirmaciones y después [cambias tu nombre de usuario](/articles/changing-your-github-username), esas confirmaciones no estarán asociadas a tu cuenta {% data variables.product.product_name %}. Esto no se aplica si estás usando una dirección `noreply` basada en el ID provista por {% data variables.product.product_name %}. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username)"{% endif %} + +### Configurar tu dirección de correo electrónico de confirmación en {% data variables.product.prodname_dotcom %} + +{% data reusables.files.commit-author-email-options %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.emails %} +{% data reusables.user_settings.add_and_verify_email %} +{% data reusables.user_settings.select_primary_email %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.user_settings.keeping_your_email_address_private %}{% endif %} + +### Configurar tu dirección de correo electrónico de confirmación en Git + +Puedes utilizar el comando `git config` para cambiar la dirección de correo electrónico que asocias a tus confirmaciones de Git. La nueva dirección de correo electrónico que configures será visible en cualquier confirmación futura que subas a {% data variables.product.product_name %} desde la línea de comando. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociadas a tu dirección de correo electrónico anterior. + +#### Configurar tu dirección de correo electrónico para cada repositorio en tu computadora + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. {% data reusables.user_settings.set_your_email_address_in_git %} + ```shell + $ git config --global user.email "email@example.com" + ``` +3. {% data reusables.user_settings.confirm_git_email_address_correct %} + ```shell + $ git config --global user.email + email@example.com + ``` +4. {% data reusables.user_settings.link_email_with_your_account %} + +#### Configurar tu dirección de correo electrónico para un repositorio único + +{% data variables.product.product_name %} utiliza la dirección de correo electrónico configurada en tu configuración local de Git para asociar las confirmaciones subidas desde la línea de comando con tu cuenta {% data variables.product.product_name %}. + +Puedes cambiar la dirección de correo electrónico asociada a las confirmaciones que realizas en un repositorio único. Esto sustituirá tus configuraciones globales de Git en este único repositorio, pero no afectará otros repositorios. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambia el directorio de trabajo actual al repositorio local donde deseas configurar la dirección de correo electrónico que asocias con tus confirmaciones de Git. +3. {% data reusables.user_settings.set_your_email_address_in_git %} + ```shell + $ git config user.email "email@example.com" + ``` +4. {% data reusables.user_settings.confirm_git_email_address_correct %} + ```shell + $ git config user.email + email@example.com + ``` +5. {% data reusables.user_settings.link_email_with_your_account %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md new file mode 100644 index 0000000000000..9ef0db7c782d3 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -0,0 +1,36 @@ +--- +title: Tipos de correos electrónicos que envía GitHub +intro: 'Existen varios tipos de correos electrónicos que puedes recibir de {% data variables.product.product_name %}, incluidas notificaciones, información de cuenta y comunicaciones de marketing.' +redirect_from: + - /articles/types-of-emails-github-sends +versions: + free-pro-team: '*' +--- + +### Correos electrónicos de notificación + +Puedes decidir si quieres recibir algunas o todas las notificaciones de tu actividad por correo electrónico. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)". Los correos electrónicos de notificación pueden incluir: + +- Actividad relacionada con la seguridad de los repositorios a los que tienes acceso de administrador +- Actividad de los repositorios que estás observando +- Conversaciones en las que estás participando +- Conversaciones en las que te han mencionado @mentioned +- Subidas a solicitudes de extracción en las que estás participando +- Invitaciones a colaborar en una organización o repositorio +- Tu propia actividad, como abrir, comentar o cerrar propuestas y solicitudes de extracción + +También puedes elegir qué tipo de actualizaciones de correo electrónico quieres recibir sobre las conversaciones en las que estás participando o que estás observando. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". + +### Correos electrónico de la cuenta + +Si subiste de categoría a productos o funciones pagas, recibirás los recibos de facturación en la dirección principal de correo electrónico de la cuenta. Para obtener más información, consulta "[Establecer tu correo electrónico de facturación](/articles/setting-your-billing-email)". + +### Correos electrónicos de marketing + +{% data variables.product.product_name %}, en algunas ocasiones, envía estos tipos de correos electrónicos de marketing: + +- Trucos y sugerencias para comenzar con tu cuenta +- Información personalizada acerca de participar en proyectos o funciones nuevas +- Boletines a los que te suscribiste, tales como {% data variables.explore.explore_github %} + +Para obtener más información, consulta "[Administrar los correos electrónicos de marketing desde GitHub](/articles/managing-marketing-emails-from-github)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md new file mode 100644 index 0000000000000..31f2c9013993e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md @@ -0,0 +1,22 @@ +--- +title: Ver los roles de las personas en una organización +intro: 'Puedes ver una lista de personas en tu organización y filtrar por su rol. Para obtener más información sobre roles en la organización, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)."' +redirect_from: + - /articles/viewing-people-s-roles-in-an-organization + - /articles/viewing-peoples-roles-in-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% note %} + +**Nota:** debes ser miembro de una organización para ver los roles de las personas en tu organización. + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Verás una lista de personas en tu organización. Para filtrar esta lista por rol, haz clic en **Role (Rol)** y seleccionar el rol que estás buscando. ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md new file mode 100644 index 0000000000000..76737106c38fd --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md @@ -0,0 +1,15 @@ +--- +title: '¿Qué función cumple la casilla de verificación ''Available for hire'' (Disponible para contratación)?' +intro: Utiliza la casilla de verificación **Available for hire** (Disponible para contratación) para ver las publicaciones de Empleos de GitHub dentro de GitHub. +redirect_from: + - /articles/what-does-the-available-for-hire-checkbox-do +versions: + free-pro-team: '*' +--- + +El tablero [Empleos de GitHub](https://jobs.github.com/) es una buena manera de encontrar trabajo en el sector de tecnología. Puedes elegir para ver los trabajos publicados allí en tu tablero de GitHub. + +![Anuncios de Empleos GitHub en el tablero](/assets/images/help/settings/jobs-ads-on-dashboard.png) + +{% data reusables.user_settings.access_settings %} +2. Dentro de Jobs Profile (Perfil de trabajos), selecciona **Available for hire (Disponible para contratación)**, después haz clic en **Save jobs profile (Guardar perfil de trabajos)**. ![Configuraciones de perfil de trabajos](/assets/images/help/settings/jobs-profile-settings.png) diff --git a/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md b/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md new file mode 100644 index 0000000000000..fa24f662105bf --- /dev/null +++ b/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md @@ -0,0 +1,99 @@ +--- +title: Política de retiro de DMCA +redirect_from: + - /dmca/ + - /dmca-takedown/ + - /dmca-takedown-policy/ + - /articles/dmca-takedown/ + - /articles/dmca-takedown-policy +versions: + free-pro-team: '*' +--- + +Bienvenido a la Guía sobre la Ley de Derechos de Autor del Milenio Digital de GitHub, comúnmente conocida como la "DMCA". Esta página no está pensada como un manual extenso del estatuto. Sin embargo, si has recibido un aviso de retiro de la DMCA orientado al contenido que has publicado en GitHub o si eres un titular de derechos que busca proponer dicho aviso, esperamos que esta página ayude a desmitificar la ley un poco, así como nuestras políticas para cumplirla. + +(Si solo deseas enviar un aviso, puedes [ir al final del documento](#f-submitting-notices).) + +Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. + +### ¿Qué es la DMCA? + +Para entender la DMCA y algunas de las orientaciones de la política, tal vez sea útil considerar la duración antes de que se promulgara. + +La DMCA proporciona un puerto seguro para los proveedores de servicios que albergan contenido generado por los usuarios. Dado que incluso una sola reclamación de infracción de derechos de autor puede conllevar daños estatutarios por hasta $150,000, la posibilidad de responsabilizarse de los contenidos generados por los usuarios podría ser muy perjudicial para los proveedores de servicios. Con daños potenciales multiplicados a través de millones de usuarios, la computación en la nube y los sitios de contenido generados por usuarios como YouTube, Facebook, o GitHub probablemente [nunca habrían existido](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) sin la DMCA (o al menos sin pasar parte de ese costo a sus usuarios). + +La DMCA aborda este problema mediante la creación de un [puerto seguro de responsabilidad de derechos de autor](https://www.copyright.gov/title17/92chap5.html#512) para los proveedores de servicios de Internet que presuntamente infrinjan el contenido generado por los usuarios. Esencialmente, mientras un proveedor de servicios siga las reglas de notificación y retiro de la DMCA, no será responsable de la infracción de derechos de autor con base en el contenido generado por los usuarios. Debido a esto, es importante que GitHub mantenga su estado de puerto seguro de la DMCA. + +### Avisos de la DMCA en Nutshell + +La DMCA proporciona dos procedimientos claros y sencillos sobre los que todos los usuarios de GitHub deberían tener conocimiento: (i) un procedimiento [de notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) para que los titulares de los derechos de autor soliciten que se elimine el contenido; y (ii) una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice) para que se reactive el contenido, cuando se elimina por error o identificación incorrecta. + +Los propietarios de derechos de autor utilizan [notificaciones de retiro de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice) para solicitar a GitHub que retire el contenido que consideran infractor. Si eres diseñador de software o desarrollador, creas contenido con derechos de autor todos los días. Si alguien más está utilizando tu contenido con derechos de autor sin autorización dentro de GitHub, puedes enviarnos una notificación de retiro de la DMCA para solicitar que se cambie o elimine el contenido que comete dicha violación. + +Por otro lado, se pueden utilizar [contra notificaciones](/articles/guide-to-submitting-a-dmca-counter-notice) para corregir errores. Quizá la persona que envía la notificación de retiro no tiene los derechos de autor o no se percató que tienes una licencia o cometió algún otro error en su notificación de retiro. Ya que GitHub normalmente no puede saber si ha ocurrido un error, la contra notificación de la DMCA te permite hacernos saber y solicitar que le volvamos a poner el contenido nuevamente. + +El proceso de eliminación notificación y retiro de la DMCA debe utilizarse únicamente para reclamaciones sobre violaciones de derechos de autor. Las notificaciones enviadas a través de nuestro proceso DMCA deben identificar obras o trabajos protegidos por derechos de autor que supuestamente están siendo infringidos. El proceso no puede utilizarse para otras reclamaciones, tales como quejas sobre presuntas [infracciones de marcas](/articles/github-trademark-policy/) o [datos sensibles](/articles/github-sensitive-data-removal-policy/); ofrecemos procesos separados para esas situaciones. + +### A. ¿Cómo funciona realmente? + +El marco de la DMCA es un poco como pasar notas en clase. El propietario de los derechos de autor entrega a GitHub una reclamación sobre un usuario. Si está redactado correctamente, pasamos la queja al usuario. Si el usuario cuestiona la reclamación, puede regresar una nota afirmando. GitHub ejerce poca discreción en el proceso aparte de determinar si los avisos cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio. + +Aquí están los pasos básicos en el proceso. + +1. **El Propietario de Derechos de Autor investiga.** Un propietario de los derechos de autor siempre debe realizar una investigación inicial para confirmar (a) que son propietarios de los derechos de autor de una obra original y (b) que el contenido de GitHub no está autorizado y es infractor. Esto incluye confirmar que el uso no está protegido como [uso razonable](https://www.lumendatabase.org/topics/22). Un uso particular puede ser justo si solamente utiliza una pequeña cantidad de contenido protegido por derechos de autor, utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado. +> **Ejemplo:** Un empleado de Acme Web Company encuentra parte del código de la empresa en un repositorio de GitHub. Acme Web Company otorga licencias de su código fuente a diversos socios de confianza. Antes de enviar una notificación de retiro, Acme debe revisar dichas licencias y sus acuerdos para confirmar que el código en GitHub no esté autorizado bajo ninguna de ellas. + +2. **El propietario de los derechos de autor envía una notificación.** Después de realizar una investigación, un propietario de los derechos de autor prepara y envía una [notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) a GitHub. Suponiendo que la notificación de retiro esté suficientemente detallada de acuerdo con los requisitos legales (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-takedown-notice)), [publicaremos la notificación](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el enlace al usuario afectado. + +3. **GitHub solicita a sus usuarios hacer cambios.** Si la notificación declara que todo el contenido de un repositorio o un paquete están cometiendo una violación, saltaremos al Paso 6 e inhabilitaremos todo el repositorio o paquete expeditamente. De lo contrario, debido a que GitHub no puede inhabilitar el acceso a archivos específicos dentro de un repositorio, nos contactaremos con el usuario que creó el repositorio y les daremos aproximadamente 1 día hábil para eliminar o modificar el contenido especificado en el aviso. Notificaremos al propietario de los derechos de autor si y cuando demos al usuario la oportunidad de hacer cambios. Ya que los paquetes son inmutables, si solo una parte de un paquete incurre en una violación, GitHub necesitará inhabilitar todo el paquete, pero permitiremos su restablecimiento una vez que se elimine la parte que comete la violación. + +4. **El usuario notifica a GitHub acerca de los cambios.** Si el usuario opta por realizar los cambios especificados, *Debe* avísanos dentro de la ventana de aproximadamente 1 día hábil. Si no lo hacen, deshabilitaremos el repositorio (como se describe en el paso 6). Si el usuario nos notifica que realizó cambios, verificaremos que los cambios se hayan realizado y posteriormente notificaremos al propietario de los derechos de autor. + +5. **El titular de los derechos de autor revisa o retrae la notificación.** Si el usuario realiza cambios, el propietario de los derechos de autor debe revisarlos y renovar o revisar su aviso de eliminación si los cambios son insuficientes. GitHub no tomará ninguna acción adicional a menos que el propietario de los derechos de autor se ponga en contacto con nosotros para renovar la notificación de retiro original o presentar uno revisado. Si el propietario de los derechos de autor está satisfecho con los cambios, puede presentar una retracción formal o no hacer nada. GitHub interpretará el silencio durante más de dos semanas como una retracción implícita del aviso de retiro. + +6. **GitHub puede inhabilitar el acceso al contenido.** GitHub inhabilitará el contenido de un usuario si: (i) el propietario de los derechos de autor reclama dichos derechos sobre un paquete o todo el repositorio del usuario (como se explica en el Paso 3); (ii) el usuario no ha realizado cambios después de habérsele proporcionado una oportunidad para hacerlo (de acuerdo con el Paso 4); o (iii) el propietario de los derechos de autor renovó su notificación de retiro después de que el usuario tuvo una oportunidad de realizar los cambios. Si el propietario de los derechos de autor elige *revisar* la notificación, volveremos al paso 2 y repetiremos el proceso como si la notificación revisada fuera un nuevo aviso. + +7. **El usuario puede enviar una contra notificación.** Alentamos a los usuarios que han deshabilitado contenido a consultar con un abogado sobre sus opciones. Si un usuario considera que su contenido fue deshabilitado como resultado de un error o identificación incorrecta, pueden enviarnos una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Como en la notificación original, nos aseguraremos de que la contra notificación esté lo suficientemente detallada (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-counter-notice)). Si es así, [lo publicaremos](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el aviso al propietario de los derechos de autor enviándole el enlace. + +8. **El propietario de los derechos de autor puede presentar una acción legal.** Si un propietario de derechos de autor desea mantener el contenido deshabilitado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedir que el usuario se implique en actividades relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado. Si el propietario de los derechos de autor no da aviso a GitHub en un plazo de 10-14 días, enviando una copia de una queja legal válida presentada en un tribunal de jurisdicción competente, GitHub rehabilitará el contenido inhabilitado. + +### B. ¿Qué hay de las bifurcaciones? (o ¿Qué es una bifurcación?) + +Una de las mejores características de GitHub es la capacidad de los usuarios de "bifurcar" los repositorios de otros. ¿Qué significa esto? En esencia, significa que los usuarios pueden hacer una copia de un proyecto en GitHub en sus propios repositorios. Como la licencia o la ley permite, los usuarios pueden hacer cambios en esa bifurcación para volver al proyecto principal o simplemente mantener como su propia variación de un proyecto. Cada una de estas copias es una "[bifurcación](/articles/github-glossary#fork)" del repositorio original, que a su vez también se puede llamar la "matriz" de la bifurcación. + +GitHub *no deshabilitará automáticamente* las bifurcaciones cuando se deshabilite un repositorio matriz. Esto se debe a que las bifurcaciones pertenecen a diferentes usuarios, pueden haber sido alteradas de manera significativa y pueden ser licenciadas o utilizada de una manera diferente que estén protegidas por la doctrina de uso leal. GitHub no lleva a cabo ninguna investigación independiente sobre las bifucaciones. Esperamos que los propietarios de los derechos de autor lleven a cabo esa investigación y, si creen que las bifurcaciones también están infringiendo, incluyan expresamente bifurcaciones en su notificación de retiro. + +### C. ¿Qué pasa si perdí inadvertidamente el período para hacer cambios? + +Reconocemos que existen muchas razones válidas para que no puedas hacer cambios dentro de la ventana de aproximadamente 1 día laborable que proporcionamos antes de que tu repositorio se inhabilite. Quizá nuestro mensaje fue marcado como spam, tal vez estabas de vacaciones, tal vez no revisas esa cuenta de correo electrónico regularmente, o probablemente solo estabas ocupado. Lo entendemos. Si respondes para hacernos saber que te hubiera gustado hacer los cambios, pero de alguna manera faltaste a la primera oportunidad, rehabilitaremos el repositorio un tiempo adicional durante aproximadamente 1 día hábil para permitir que realices los cambios. Nuevamente, debes notificarnos que has realizado los cambios con el fin de mantener el repositorio habilitado después de esa ventana de aproximadamente 1 día hávil, como se mencionó anteriormente en el [Paso A. 4](#a-how-does-this-actually-work). Ten en cuenta que sólo te daremos una oportunidad adicional. + +### D. Transparencia + +Creemos que la transparencia es una virtud. El público debería saber qué contenido se está eliminando de GitHub y por qué. Un público informado puede notar y descubrir posibles problemas superficiales que de otro modo pasarían desapercibidos en un sistema poco claro. Publicamos copias redactadas de cualquier aviso legal que recibamos (incluyendo notificaciones originales, contra notificaciones o retracciones) en . No haremos pública tu información de contacto personal; eliminaremos la información personal (excepto los nombres de usuario en las URLs) antes de publicar notificaciones. Sin embargo, no redactaremos ninguna otra información de tu notificación a menos que nos lo solicites específicamente. Estos son algunos ejemplos de una [notificación ](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) publicada y [una contra notificación](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) para que veas cómo son. Cuando eliminemos el contenido, publicaremos un enlace al aviso relacionado en su lugar. + +Ten también en cuenta que, aunque no publicaremos avisos no modificados, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente a cualquier parte cuyos derechos se verían afectados por ella. + +### E. Retición de una infracción + +Es la política de GitHub, en circunstancias apropiadas y a su entera discreción, desactivar y terminar las cuentas de los usuarios que puedan infringir los derechos de autor u otros derechos de propiedad intelectual de GitHub u otros. + +### F. Cómo enviar notificaciones + +Si estás listo para enviar una notificación o una contra notificación: +- [Cómo enviar una notificación de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice) +- [Cómo enviar una contra notificación de la DMCA](/articles/guide-to-submitting-a-dmca-counter-notice) + +### Conoce más y comunícate + +Si exploras Internet, no es demasiado difícil encontrar comentarios y críticas sobre el sistema de derechos de autor en general y la DMCA en particular. Mientras que GitHub reconoce y aprecia el importante papel que ha desempeñado la DMCA en la promoción de la innovación en línea creemos que las leyes de derechos de autor probablemente podrían usar un patch o dos, o bien una versión completamente nueva. En software, estamos constantemente mejorando y actualizando nuestro código. Piensa en cuánto ha cambiado la tecnología desde 1998, cuando se redactó la DMCA. ¿No tiene sentido actualizar estas leyes que se aplican al software? + +No presumimos de tener todas las respuestas. Pero si eres curioso, aquí tienes algunos enlaces a artículos informativos y entradas de blog que hemos encontrado con opiniones y propuestas para la reforma: + +- [Consecuencias no deseadas: Doce años bajo la DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Constitución de la Frontera Electrónica) +- [Daños y Perjuicios Reglamentarios en la Ley de Derechos de Autor: Un recordatorio en la necesidad de la reforma](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Revisión de la ley María) +- [¿El plazo de protección de los derechos de autor es demasiado largo?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (el 1709 blog) +- [Si vamos a cambiar 'Notificación y Retiro', de la DMCA, centrémonos en su amplio abuso](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt) +- [Oportunidades para la reforma de los derechos de autor](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato sin asociar) +- [Uso Justo de la Doctrina y la Ley de Derechos de Autor del Milenio Digital: ¿Existe un uso justo en Internet bajo la DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Revisión de la Ley de Santa Clara) + +GitHub no necesariamente respalda ninguno de los puntos de vista en esos artículos. Proporcionamos los enlaces para invitarte a conocer más, formar tus propias opiniones y posteriormente llegar a tu(s) representante(s) electos (por ejemplo, en el [Congreso de los Estados Unidos](https://www.govtrack.us/congress/members) o [Parlamento de los EE. UU.](https://www.europarl.europa.eu/meps/en/home)) para buscar los cambios que consideras que deberían llevarse a cabo. Congreso o [EE. UU. Parlamento](https://www.europarl.europa.eu/meps/en/home)) para buscar los cambios que consideres necesarios. diff --git a/translations/es-ES/content/github/site-policy/github-acceptable-use-policies.md b/translations/es-ES/content/github/site-policy/github-acceptable-use-policies.md new file mode 100644 index 0000000000000..e53405b360afd --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-acceptable-use-policies.md @@ -0,0 +1,94 @@ +--- +title: Políticas de uso aceptable de GitHub +redirect_from: + - /articles/github-acceptable-use-policies +versions: + free-pro-team: '*' +--- + +**Versión simplificada:** _Presentamos una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con nuestras políticas de uso aceptable, que incluyen algunas restricciones sobre el contenido que puedes publicar o gestionar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí._ + +Los términos en mayúsculas que se utilizan, pero no se definen en estas Políticas de uso aceptable tienen significados asignados en nuestros [Términos de servicio](/articles/github-terms-of-service), [Términos de servicio corporativos](/articles/github-corporate-terms-of-service) y [Declaración de privacidad](/articles/github-privacy-statement). Para los clientes sujetos a los [Términos de servicio corporativos](/articles/github-corporate-terms-of-service), "tú" y "tu/tus" se refieren al "Cliente" o los "Usuarios". "Nosotros", "nuestro", "nuestros" se refieren a "GitHub". + +### 1. Cumplimiento con las leyes y regulaciones +Eres responsable de usar el Servicio de conformidad con todas las leyes, regulaciones y con todas nuestras Políticas de uso aceptable que correspondan. Estas políticas se pueden actualizar cada cierto tiempo y se presentan a continuación. También se puede acceder a ellas en nuestros [Términos de servicio](/articles/github-terms-of-service) y [Términos de servicio corporativos](/articles/github-corporate-terms-of-service). + +### 2. Restricciones de contenido +Bajo ninguna circunstancia los usuarios cargarán, publicarán, presentarán, realizarán o transmitirán ningún contenido en ninguno de los repositorios: + +- que sea ilícito o promueva actividades ilícitas; + +- que constituya o contenga contenido sexualmente explícito u obsceno; + +- que sea calumnioso, difamatorio o fraudulento; + +- que sea discriminatorio u ofensivo hacia cualquier persona o grupo; + +- que represente violencia o la glorifique injustificadamente, incluidas imágenes violentas; + +- que sea o contenga información falsa, inexacta o intencionalmente engañosa que pueda afectar negativamente el interés público (incluyendo la salud, seguridad, integridad de la elección y participación cívica); + +- que contenga o instale cualquier malware o vulnerabilidad de seguridad, o use nuestra plataforma para el envío de vulnerabilidades de seguridad (como parte de un comando y un sistema de control); + +- que infrinja algún derecho de propiedad de cualquiera de las partes, incluidos la patente, el nombre comercial, el secreto comercial, la propiedad intelectual, el derecho a publicidad o cualquier otro derecho. + +### 3. Restricciones de conducta +Mientras usas el Servicio, en ninguna circunstancia puedes hacer lo siguiente: + +- acosar, abusar o amenazar a cualquier persona o grupo, incluidos nuestros empleados, funcionarios y agentes, o cualquier otro usuario, ni incitar violencia hacia ellos; + +- publicar contenido fuera de tema o interactuar con las características de la plataforma, de una manera que interrumpa de forma significativa o repetida la experiencia de otros usuarios; + +- usar nuestros servidores para llevar a cabo cualquier forma de actividad masiva automática excesiva (por ejemplo, correo no deseado o masivo) o colocar una carga indebida en nuestros servidores a través de medios automatizados o retransmitir alguna otra forma de publicidad o solicitudes no requeridas a través de nuestros servidores, como esquemas del tipo "hazte rico rápidamente"; + +- usar nuestros servidores para interrumpir o intentar interrumpir, obtener o intentar obtener acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (a menos que lo autorice el [programa Bug Bounty GitHub](https://bounty.github.com)); + +- hacerte pasar por cualquier persona o entidad, incluidos cualquiera de nuestros empleados o representantes, incluso a través de asociación falsa con GitHub, o falsear de manera fraudulenta tu identidad o el propósito del sitio; + +- violar la privacidad de cualquier tercero, como publicar información personal de otra persona sin su consentimiento. + +### 4. Límites de uso de los servicios +No reproducirás, duplicarás, copiarás, venderás, revenderás o aprovecharás ninguna parte del Servicio, el uso del Servicio o el acceso al Servicio sin autorización expresa por escrito. + +### 5. Restricciones de uso de información +Puedes utilizar la información de nuestro Servicio por las siguientes razones, independientemente de si se eliminó la información, se recopiló través de nuestra API o se obtuvo de otra forma: + +- Los investigadores pueden utilizar información pública y no personal del Servicio con fines de investigación, solo si cualquier publicación resultante de dicha investigación es [de acceso abierto](https://en.wikipedia.org/wiki/Open_access). +- Los archivistas pueden utilizar la información pública del Servicio con fines de archivo. + +La eliminación se refiere a extraer datos de nuestro Servicio a través de un proceso automático, como un bot o agente de búsqueda. No se refiere a la recopilación de información a través de nuestra API. Por favor, consulta la sección H de nuestras [Condiciones de Servicio](/articles/github-terms-of-service#h-api-terms) para nuestras Condiciones de la API. + +No puedes utilizar la información del Servicio (ya sea eliminada, recopilada a través de nuestra API u obtenida de otra forma) con fines de enviar correo basura, incluyendo para los fines de enviar correos electrónicos no solicitados a los usuarios o vender información personal del usuario (como se define en la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement)), tales como reclutadores, cazatalentos y bolsas de trabajo. + +Tu uso de la información del Servicio debe cumplir con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). + +### 6. Privacy +Está prohibido el uso indebido de la Información personal del Usuario. + +Cualquier persona, entidad o servicio que recopile datos del Servicio debe cumplir con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement), en particular, al respecto de la recopilación de Información personal del Usuario. Si recopilas cualquier Información personal del Usuario desde el Servicio, debes aceptar que solo usarás esa Información personal del Usuario para los fines que ese Usuario autorizó. Aceptas que asegurarás de manera razonable cualquier Información personal del Usuario que hayas reunido desde el Servicio y responderás de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" que hagamos nosotros u otros usuarios. + +### 7. Uso del ancho de banda excesivo +Las limitaciones de ancho de banda del servicio varían en función de las características que utilices. Si determinamos que tu uso del ancho de banda es significativamente excesivo en relación con el de otros usuarios, nos reservamos el derecho a suspender tu Cuenta o limitar el alojamiento de tu archivo o, de otra forma, limitar tu actividad hasta que puedas reducir tu consumo de ancho de banda. Tambien nos reservamos los derechos—después de proporcionar una notificación por adelantado—de borrar repositorios que creamos están colocando una tensión indebida en nuestra infraestructura. Para obtener orientación sobre el uso aceptado de almacenamiento de objetos en los repositorios, refiérete a la sección "[¿Cuál es mi cuota de disco?](/github/managing-large-files/what-is-my-disk-quota)". Para obtener más detalles sobre las limitaciones de ancho de banda de características especiales, consulta la sección [Condiciones Adicionales de Producto de GitHub](/github/site-policy/github-additional-product-terms). + +### 8. Hacer publicidad en GitHub +**Versión simplificada:** *Generalmente no prohibimos el uso de GitHub para publicidad. Sin embargo, esperamos que nuestros usuarios sigan ciertas limitaciones, por lo que GitHub no se convierta en un espacio lleno de spam. Nadie desea eso.* + +Aunque entendemos que tal vez deseas promover tu Contenido publicando los nombres o logos de los seguidores de tu Cuenta, el enfoque principal del Contenido publicado en o a través de tu Cuenta al Servicio no debe ser publicidad o marketing promocional. Esto incluye Contenido publicado en o a través de Páginas, Paquetes, repositorios y todas las demás partes del Servicio. Puedes incluir imágenes estáticas, enlaces y textos promocionales en los documentos README o secciones de descripción del proyecto asociadas con tu Cuenta, pero deben estar relacionados con el proyecto que estás alojando en GitHub. No puedes publicitar en las Cuentas de otros Usuarios, por ejemplo, mediante la publicación de contenido monetizado o excesivo en masa. + +No puedes promover o distribuir contenido o actividad ilegal o prohibida por nuestros [Términos de servicio](/github/site-policy/github-terms-of-service/), [Directrices de la comunidad](/github/site-policy/github-community-guidelines/), o [Política de Uso Aceptable](/github/site-policy/github-acceptable-use-policies/), incluyendo una actividad masiva automatizada excesiva (por ejemplo, spamming), esquemas "hazte rico rápidamente" y distorsión o engaño relacionados con tu promoción. + +Si decides alojar cualquier material publicitario o promocional en tu Cuenta, eres el único responsable de cumplir con todas las leyes y regulaciones correspondientes, incluyendo, entre otras, las Directrices sobre Endosos y Testimonios de la Comisión Federal de Comercio de los EE. UU. Directrices de la Comisión Federal de Comercio sobre los respaldos y testimonios. Nos reservamos el derecho de eliminar cualquier material promocional o publicidad que, a nuestra entera discreción, viole cualquier término o política de GitHub. + +### 9. Spam y actividad falsa en GitHub +En GitHub se prohíbe la actividad excesiva automatizada y la actividad coordinada falsa, como el spamming. Las actividades prohibidas incluyen: +* distribución masiva de promociones y publicidad prohibida por los términos y políticas de GitHub +* interacciones falsas, tales como cuentas falsas y la actividad automatizada falsa +* abuso de rango, por ejemplo, protagonización automática o la +* creación o participación posterior en los mercados secundarios con la intención de la proliferación de actividades falsas +* usar a GitHub como una plataforma para propagar abusos en otras plataformas +* phishing o intento de phishing + +GitHub se reserva el derecho de eliminar cualquier Contenido que viole esta política. + +### 10. Protección del Usuario +No debes participar de actividades que dañen de manera significativa a otros usuarios. Resolveremos las disputas en favor de la protección de los usuarios como totalidad. diff --git a/translations/es-ES/content/github/site-policy/github-additional-product-terms.md b/translations/es-ES/content/github/site-policy/github-additional-product-terms.md new file mode 100644 index 0000000000000..7ecd50908e5e8 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-additional-product-terms.md @@ -0,0 +1,109 @@ +--- +title: Términos adicionales de los productos de GitHub +versions: + free-pro-team: '*' +--- + +Fecha de entrada en vigencia de la versión: 14 de diciembre de 2020 + +Al crear una Cuenta, se le da acceso a muchas características y productos diferentes que forman parte del Servicio. Debido a que muchas de estas características y productos ofrecen una funcionalidad diferente, pueden requerir términos y condiciones adicionales específicas de esa característica o producto. A continuación, listamos estas características y productos, junto con las condiciones adicionales correspondientes que aplican a el uso que les des. + +La utilización del servicio está sujeta a tus condiciones aplicables (el "Acuerdo"). Cuando utilizas productos y características adicionales, también estás aceptando estas Condiciones Adicionales del Producto. Cualquier violación de las Condiciones Adicionales del Producto constituye una violación al acuerdo. Las condiciones en mayúscula que no se definen en las Condiciones Adicionales del Producto tendrán el mismo significado que se les atribuye en el acuerdo. + +Si estás utilizando GitHub AE, entonces solo podrás acceder a los siguientes productos y características: Integraciones de Terceros, Soporte de Git LFS, Páginas. + +### 1. Marketplace + +Si registras un Producto de Desarrollador a través de GitHub Marketplace, entonces debes aceptar el [Acuerdo de Desarrollador de GitHub Marketplace](/github/site-policy/github-marketplace-developer-agreement), antes de enviar el proyecto a registrar. + +Si compras Productos de Desarollador a través de GitHub Marketplace, los [Términos de servicio de GitHub Marketplace](/github/site-policy/github-marketplace-terms-of-service) controlarán tu compra. El Acuerdo, así como los [Términos de Servicio de GitHub Marketplace](/github/site-policy/github-marketplace-terms-of-service), regirán tu uso de GitHub Marketplace. + +### 2. Integraciones de terceros + +#### a. Crear Aplicaciones +Si creas una aplicación de terceros u otro producto de desarrollador que recopile Información Personal de Usuario o Contenido Generado por el Usuario e que se integre con el Servicio a través de la API de GitHub, el Mecanismo OAuth, o de otro modo ("Producto de Desarrollador") y está a disposición de otros usuarios, entonces debe cumplir con los siguientes requisitos: +- Debes cumplir con este Acuerdo y la Declaración de privacidad de GitHub. +- Excepto que se permita de otra manera, por ley o por una licencia, debes limitar tu uso de la Información Personal del Usuario o el Contenido Generado por el Usuario que recopiles para ese propósito para el cual el Usuario ha autorizado su recopilación. +- Debes tomar todas las medidas de seguridad razonables apropiadas para los riesgos, por ejemplo, contra la destrucción accidental o ilegal, o pérdidas accidentales, alteración, divulgación o acceso no autorizado, presentado mediante el procesamiento de la Información Personal del Usuario o Contenido Generado por el Usuario. +- No debes recopilar información personal o contenido generado por el usuario en nombre de GitHub y proporcionar un aviso necesario de tus prácticas de privacidad al Usuario, como por ejemplo, mediante la publicación de una política de privacidad. +- Debes ofrecerle a los Usuarios un método para borrar cualquier Información personal del Usuario o Contenido generado por el Usuario que hayas recopilado por medio de GitHub cuando deje de ser necesario para los fines limitados y especificados para los cuales el Usuario autorizó su recopilación, excepto cuando se requiera su retención por ley o se permita lo contrario, por ejemplo, a través de una licencia. + +#### b. Solicitudes de uso de terceros +Puedes conceder una autorización de Producto de Desarrollador para usar, ingresar y divulgar el contenido de sus repositorios, incluyendo sus repositorios privados. Algunos Productos de Desarrollador están disponibles a través de [GitHub Marketplace](https://github.com/marketplace). Algunos Productos de Desarrollador pueden usarse para realizar tareas automatizadas y a menudo diversos usuarios pueden dirigir las acciones de un Producto de Desarrollador. Sin embargo, si compras y/o configuras un Producto de Desarrollador en tu Cuenta o eres propietario de una Cuenta con un Producto de Desarrollador integrado, entonces serás responsable de las acciones del Producto del Desarrollador que se llevan a cabo en o a través de tu Cuenta. Consulta nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#third-party-applications) para obtener más información sobre cómo compartimos datos con los Productos del Desarrollador. + +**GitHub no ofrece ninguna garantía de ningún tipo en relación con los Productos de Desarrollador y no se hace responsable de las revelaciones a terceros que autorice a acceder a Tu Contenido. El uso que hagas de cualquier solicitud de terceros corre por tu cuenta y riesgo.** + +### 3. Soporte de Git LFS + +Si activas Git Large File Storage ("Git LFS") en tu Cuenta, podrás obtener, modificar y extraer archivos grandes como esperarías con cualquier archivo que Git gestione. Tu Cuenta viene con cierta cantidad de ancho de banda y almacenamiento para usar con Git LFS, que se puede encontrar en la [documentación de Git LFS](/github/managing-large-files/about-storage-and-bandwidth-usage). El ancho de banda y el uso de almacenamiento de Git LFS se muestran en la [configuración de Tu cuenta](https://github.com/settings/billing). Si deseas utilizar Git LFS más allá del ancho de banda y almacenamiento asignados, puedes [comprar paquetes de datos adicionales](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage). + +### 4. Pages + +Cada cuenta incluye acceso al [servicio de hospedaje estático de GitHub pages](/github/working-with-github-pages/about-github-pages). Este servicio de alojamiento está destinado a albergar páginas web estáticas para todos los usuarios, pero principalmente como escaparate para proyectos personales y organizativos. Se permiten algunas iniciativas de monetización en las Páginas, tales como botones de donación y enlaces de financiación colectiva. + +Las páginas de GitHub están sujetas a algunos límites específicos de ancho de banda y uso y podrían no ser adecuadas para algunos usos de alto ancho de banda u otros usos prohibidos. Consulte nuestras [directrices de páginas de GitHub](/github/working-with-github-pages/about-github-pages) para obtener más información. GitHub se reserva el derecho en todo momento de reclamar cualquier subdominio de GitHub sin responsabilidad. + +### 5. Acciones y paquetes + +#### a. Uso de acciones +GitHub Actions se factura conforme a su uso. La [Documentación de las acciones](/actions) incluye detalles como las cantidades de procesamiento y almacenamiento (dependiendo del plan de tu cuenta), y el cómo monitorear el uso de minutos de tus acciones y configurar los límites de uso. + +Las acciones y cualquier elemento del servicio de ellas no puede utilizarse para violar el acuerdo, las [Políticas de uso aceptable de GitHub](/github/site-policy/github-acceptable-use-policies), ni las limitaciones del servicio de Github, las cuales se establecen en la [Documentación de las acciones](/actions). Además, las acciones no deben utilizarse para: +- criptominería; +- utilizar nuestros servicios para perturbar u obtener o intentar obtener acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (diferente a aquellas que utiliza el [programa de recompensas de bugs de GitHub](https://bounty.github.com)); +- el aproviosionamiento de las aplicaciones autónomas o integradas o del servicio que ofrece acciones o cualquier elemento de ellas para propósitos comerciales; +- cualquier actividad que coloque un peso en nuestros servidores, ya sea que dicho peso sea excesivo para los beneficios que se proporcionan a los usuarios (por ejemplo, no utilizamos acciones como una red de entrega de contenido o como parte de una aplicación sin servidores, pero una acción de beneficio mínimo podría estar bien si también implica un peso mínimo); o +- cualquier otra actividad no relacionada con la producción, prueba, despliegue o publicación del proyecto de software asociado con el repositorio donde se utilizan las Acciones de GitHub. + +Para evitar violaciones de estas limitaciones y abuso de las Acciones de GitHub, GitHub puede controlar tu uso de Acciones de GitHub. El uso indebido de Acciones de GitHub puede resultar en la terminación de trabajos o restricciones en tu capacidad de usar Acciones de GitHub. + +#### b. Uso de paquetes +GitHub Packages se factura de acuerdo con su uso. La [Documentación de paquetes](/packages) incluye los detalles como las cantidades de ancho de banda y almacenamiento (dependiendo del plan de tu cuenta), y la forma en la que puedes monitorear el uso de los paquetes y configurar los límites de uso. El uso de ancho de banda de los paquetes se limita por las [Políticas de uso aceptable de GitHub](/github/site-policy/github-acceptable-use-policies). + +### 6. Laboratorio de aprendizaje + +**Inscripción.** Para completar la inscripción en Learning Lab for Organizations, aceptas crear una organización diferente para los fines de laboratorio de aprendizaje y nos autorizas a agregar materiales del curso Learning Lab a esa organización en tu nombre. + +**Materiales del curso Learning Lab.** Todos los materiales del curso que ofrece GitHub son propiedad únicamente de GitHub; sin embargo, siempre que GitHub te conceda una licencia a nivel mundia, no exclusiva, a plazo limitado, no transferible y exenta de regalías para copiar, mantener, usar y ejecutar dicho material del curso para tus fines comerciales internos asociados con el uso de Learning Lab. Esta concesión de licencia está sujeta a cualquier acuerdo de licencia de código abierto adicional que se pueda proporcionar junto con el código fuente. Los materiales del curso que origines son propiedad únicamente tuya, considerando que concedes a GitHub una licencia mundial, no exclusiva, perpetua, no transferible y exenta de regalías para copiar, mantener, usar, alojar y ejecutar (según corresponda) en el servicio, dichos materiales del curso. Tu uso de los materiales del curso de GitHub y tu creación y almacenamiento de tus propios materiales del curso no constituye una propiedad conjunta en la propiedad intelectual respectiva de cualquiera de las partes por parte de la otra. + +**Privacidad.** Learning Lab puede recopilar información personal. Controlas qué Information Learning Lab recopila en tu panel de ajustes del perfil de GitHub.com. Si Learning Lab recopila información personal en nombre de GitHub, GitHub procesará esa información de acuerdo con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). Si te inscribes o estás completando un curso privado a través de Learning Lab, GitHub puede compartir tu información de inscripción y el progreso del curso mediante la finalización con los administradores de la organización. Esto puede incluir datos individuales como el nombre de usuario de GitHub, la fecha de inicio del curso y la fecha de finalización del curso. Los datos de finalización del curso también se pueden presentar en forma agregada para ayudar a orientar las mejoras en el contenido del curso. + +### 7. Conexión + +Para acceder a GitHub Connect, el cliente debe tener por lo menos una (1) cuenta en GitHub.com y una (1) instancia con licencia del software. El acceso del cliente y el uso de github.com a través de Connect se rige mediante el acuerdo aplicable a este uso del servicio. La Conexión con GitHub se puede usar para ejecutar tareas automatizadas. Además, múltiples Usuarios pueden dirigir determinadas acciones con Conexión con GitHub. El cliente es responsable por las acciones que se realizan con o a través de sus cuentas. GitHub puede recopilar información sobre la manera en que el Cliente usa la Conexión con GitHub para proporcionar y mejorar la función. Al utilizar GitHub Connect, el cliente autoriza a GitHub para recolectar los datos protegidos, lo cual incluye los datos de repositorios privados y la información personal del usuario (de acuerdo a lo que se define en la Declaración de Privacidad de GitHub), desde las cuentas del cliente. El Cliente también autoriza la transferencia de información de la instancia de identificación a GitHub por medio de la Conexión con GitHub. Esta información se rige por la Declaración de privacidad de GitHub. + +### 8. Programa de patrocinadores + +Para convertirse en un Desarrollador Patrocinado, debes aceptar los [Términos Adicionales del Programa de Patrocinadores de GitHub](/github/site-policy/github-sponsors-additional-terms). + +### 9. GitHub Advanced Security + +GitHub Advanced Security tiene licencias con base en un "Confirmador único". Un "Confirmador único" es un usuario con licencia de GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, o GitHub AE, quien realizó una confirmación de código en los últimos 90 días para cualquier repositorio con cualquier funcionalidad de GitHub Advanced Security activada. Debes adquirir una licencia de usuario de GitHub Advanced Security para cada uno de tus Confirmadores Únicos. Solo puedes utilizar GitHub Advanced Security en las bases de código que desarrollas o que se desarrollan para ti. Si utilizas la GitHub Advanced Security como parte de GitHub Enterprise Cloud, muchas de las características de la primera, incluyendo el escaneo automatizado de código para repositorios privados, también requerirán que utilices GitHub Actions. + +### 10. Vista previa de Dependabot + +Tu uso de la vista previa de Dependabot se rige por los [Términos de Servicio](https://dependabot.com/terms) y la [Política de Privacidad](https://dependabot.com/privacy) por separado. + +### 11. Spectrum + +Tu uso de Spectrum se rige por las [Condiciones de Servicio](/github/site-policy/github-terms-of-service) de GitHub y por la [Declaración de Privacidad](/github/site-policy/github-privacy-statement). + +### 12. Base de datos consultiva + +#### a. Licencia otorgada + +Necesitamos el derecho legal de enviar tus contribuciones a la base de datos consultiva de GitHub a los conjuntos de datos de dominio público como la [Base de datos nacional de vulnerabilidad](https://nvd.nist.gov/) y para licenciar la base de datos consultiva de GitHub bajo condiciones abiertas para su uso por investigadores de seguridad, la comunidad de código abierto, la industria y el público. Aceptas publicar tus contribuciones a la base de datos consultiva de GitHub bajo la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). + +#### b. Licencia para la base de datos consultiva de GitHub + +La base de datos consultiva de GitHub está bajo la licencia [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/). La condición de la atribución se puede cumplir enlazando a la base de datos consultiva de GitHub en [https://github. om/advisories](https://github.com/advisories) o a registros individuales de la base de datos consultiva de GitHub usada, con la calificación de . + +### 13. GitHub Enterprise Server + +#### a. Imagenes de SQL Server + +Puedes descargar la imagen de contenedor de la Edición Estándar de Microsoft SQL Server para archivos Linux ("SQL Server Images"). Debes desinstalar las imagenes de SQL Server cuando termine tu derecho de utilizar el software. Microsoft Corporation puede inhabilitar las imágenes de SQL Server en cualquier momento. + +#### b. Componentes de terceros + +El Software incluye componentes autorizados por terceros a GitHub, incluido el software cuya licencia exige que GitHub facilite el código fuente para que esos componentes estén disponibles. El código fuente para dichos componentes se facilitará previa solicitud. diff --git a/translations/es-ES/content/github/site-policy/github-and-trade-controls.md b/translations/es-ES/content/github/site-policy/github-and-trade-controls.md new file mode 100644 index 0000000000000..61a0b9fcdf16f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-and-trade-controls.md @@ -0,0 +1,96 @@ +--- +title: GitHub y controles comerciales +redirect_from: + - /articles/github-and-export-controls + - /articles/github-and-trade-control + - /articles/github-and-trade-controls + - /github/site-policy/github-and-export-controls +versions: + free-pro-team: '*' +--- + +GitHub.com, GitHub Enterprise Server y la información que subas a cualquiera de los productos puede estar sujeta a las regulaciones de control de comercio, incluso bajo las Regulaciones sobre Exportación de la Administracción de los Estados Unidos (EAR). Regulaciones de Administración de Exportación (las EAR). + +La visión de GitHub deber ser la plataforma global para la colaboración de desarrolladores, sin importar dónde residan. Nos tomamos en serio nuestra responsabilidad de examinar a fondo los mandatos del gobierno para estar seguros de que los usuarios y clientes no se van afectados más allá de lo que exige la ley. This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. + +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). + +Aunque hemos proporcionado la siguiente información para tu comodidad, es tu responsabilidad asegurar que el uso de los productos y servicios de GitHub cumple con todas las leyes y regulaciones aplicables, incluyendo las leyes de control de exportaciones de EE. UU. . + +### Información general sobre exportaciones + +#### GitHub.com + +Bajo nuestras [Condiciones del servicio](/articles/github-terms-of-service), los usuarios solo pueden acceder y usar GitHub.com en cumplimiento con la ley aplicable, incluyendo las leyes de control de exportación y sanciones de EE. UU. . + +Los usuarios son responsables de garantizar que el contenido que desarrollen y compartan en GitHub.com cumplA con los requisitos de las leyes de control de exportaciones, incluyendo las EAR y el Reglamento sobre Tráfico Internacional de Armas (ITAR) de los Estados Unidos. las EAR y el Reglamento sobre Tráfico Internacional de Armas (ITAR) de los Estados Unidos. La oferta de servicio alojado en la nube disponible en [GitHub.com](https://github.com) no ha sido diseñado para alojar datos sujetos al ITAR y actualmente no ofrece la posibilidad de restringir el acceso al repositorio por país. Si deseas colaborar en los datos controlados por exportación o el ITAR, te recomendamos que consideres [GitHub Enterprise Server](https://enterprise.github.com), la oferta local de GitHub. + +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Además, los usuarios no pueden utilizar GitHub.com para o en nombre de dichos partes, incluyendo los Gobiernos de los países sancionados. Además, GitHub.com no puede utilizarse para propósitos prohibidos bajo las leyes de control de exportaciones aplicables, incluyendo usos finales prohibidos descritos en [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). + +#### GitHub Enterprise Server + +GitHub Enterprise Server es una aplicación virtual autoalojada que se puede ejecutar dentro de su propio centro de datos o nube privada virtual. Como tal, GitHub Enterprise Server se puede utilizar para almacenar información controlada por ITAR u otra exportación, sin embargo, los usuarios finales son responsables de garantizar el cumplimiento del ITAR y de otros controles de exportación aplicables. + +GitHub Enterprise Server es un producto comercial de mercado masivo y se le ha asignado el Número de Clasificación de Control de Exportación (ECCN) de `5D992.` y puede exportarse a la mayoría de destinos sin necesidad de licencia (NLR). + +GitHub Enterprise Server no puede venderse, exportarse o reexportarse a ningún país listado en el Grupo de Países E:1 que se encuentran en el Suplemento No. 1 a la parte 740 del EAR o a la región de Crimea de Ucrania. Esta lista contiene actualmente a Cuba, Irán, Corea del Norte y Syria, pero está sujeta a cambios. + +### Preguntas frecuentes + +#### ¿En qué países y territorios se aplican las sanciones del gobierno estadounidense? . + +Crimea, Cuba, Irán, Corea del Norte y Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. + +#### ¿Cómo garantiza GitHub que las personas que no viven o que tienen vínculos profesionales con los países y territorios sancionados continúan teniendo acceso o capacidad de solicitud? + +En el raro caso de que una cuenta se vea afectada involuntariamente o por error, tenemos un proceso de apelación para atender dichos casos. + +Si un usuario individual o administrador de la organización considera que ha sido marcado por error, entonces ese usuario tiene la oportunidad de apelar la marca proporcionando información de verificación a GitHub. Si GitHub recibe suficiente información para verificar que el usuario u organización no está afiliado con una jurisdicción sancionada por EE.UU o restringida por las sanciones económicas estadounidenses, entonces la marca se eliminará . Consulte el [formulario de solicitud de apelación de cuenta individual](https://airtable.com/shrGBcceazKIoz6pY) y [el formulario de solicitud de apelación de cuenta organizacional](https://airtable.com/shrB2je5RBkqLEt5D). + +#### ¿Se verán afectados los viajes por estas regiones? + +Los viajes en estas regiones podrían impactar el estado de tu cuenta, pero la disponibilidad se podría reincorporar una vez que estés fuera de la región sancionada y al momento de emitir una [solicitud de petición de cuenta individual](https://airtable.com/shrGBcceazKIoz6pY) o una [solicitud de petición de cuenta organizacional](https://airtable.com/shrB2je5RBkqLEt5D) con éxito. + +#### ¿Qué está disponible y qué no está disponible? + +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +GitHub está comprometido a continuar con la oferta de servicios de repositorios públicos gratuitos para desarrolladores con cuentas individuales y organizacionales en las regiones sancionadas por los EE.UU. Esto incluye el acceso limitado a los servicios gratuitos, tales como los repositorios públicos para proyectos de código abierto (y las páginas públicas asociadas), gists públicos, y los minutos gratuitos asignados de acciones, únicamente para las comunicaciones personales, y no así para propósitos comerciales. + +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. + +GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU., el mejor acceso posible a los servicios colaborativos de código abierto para desarrolladores en regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. de fomentar el flujo libre de información y libertad de expresión en estas regiones. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. + +#### ¿Cómo defines estos usuarios específicos? + +Si GitHub determina que un usuario o cliente se encuentra en una región que está sujeta a las restricciones de control de comercio de EE.UU o un usuario está restringido bajo las sanciones económicas de EE. UU., entonces, la cuenta afiliada se restringió al cumplimiento de dichos requisitos legales. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. La determinación de la ubicación del usuario y del cliente para implementar estas restricciones legales se deriva de una serie de fuentes, incluyendo direcciones IP e historial de pagos. La nacionalidad y la etnicidad no se utilizan para marcar a los usuarios para las restricciones de sanciones. + +#### ¿Cómo se ven afectadas las cuentas de la organización? + +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. . + +La restricción suspende el acceso a servicios de repositorios privados y servicios de pago, tal como la disponibilidad de repositorios privados pagados o gratuitos, gists secretos, minutos de acciones pagados, patrocinadores y servicios de GitHub Marketplace. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. + +#### ¿Se pueden hacer públicos los repositorios privados de usuarios restringidos al intercambio? + +Los usuarios de cuentas individuales gratuitas pueden hacer públicos los repositorios privados restringidos, solo para comunicaciones personales, y no para propósitos comerciales. Los usuarios pueden hacer esto navegando a la pestaña de configuración del repositorio y haciendo clic en el botón "hacer público". Una vez que el repositorio sea público, los usuarios tendrán acceso a los servicios de repositorios públicos. Esta acción no puede revertirse. + +#### ¿Los usuarios restringidos al intercambio pueden acceder a datos del repositorio privado (por ejemplo, descargar o eliminar datos del repositorio)? + +Desafortunadamente, nuestra comprensión de la ley no nos da la opción de permitir descargas o eliminación de contenido de repositorio privado hasta que lo autorice de otra forma el gobierno de EE. UU. . . Defenderemos firmemente, junto con los reguladores estadounidenses, el derecho de los usuarios restringidos al intercambio a asegurar el contenido de sus repositorios privados. También abogaremos por una mayor disponibilidad de servicios de GitHub para desarrolladores en mercados sancionados y subrayaremos la importancia de la colaboración en código para apoyar las comunicaciones personales para los desarrolladores en todo el mundo. + +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. . + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/es-ES/content/github/site-policy/github-anti-bribery-statement.md b/translations/es-ES/content/github/site-policy/github-anti-bribery-statement.md new file mode 100644 index 0000000000000..4a79091e6c4bf --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-anti-bribery-statement.md @@ -0,0 +1,54 @@ +--- +title: Declaración antisoborno de GitHub +redirect_from: + - /articles/github-anti-bribery-statement +versions: + free-pro-team: '*' +--- + +GitHub defiende nuestro compromiso con prácticas comerciales éticas, que incluyen prohibir el soborno y la corrupción. Como la [Transparencia Internacional](https://www.transparency.org/what-is-corruption#costs-of-corruption) lo explica, los costos de la corrupción son: +- **políticos**, que plantean un gran obstáculo para la democracia y el estado de derecho +- **económicos**, agotando la riqueza nacional +- **sociales**, al socavar la confianza de las personas en la sociedad, las instituciones y los líderes políticos +- **ambientales**, al facilitar la no aplicación de las leyes y regulaciones ambientales. + +Según el [Banco Mundial](https://www.worldbank.org/en/topic/governance/brief/anti-corruption) en 2017, las empresas y personas pagan un estimado de $1.5 billones en sobornos cada año. + +### Políticas de GitHub que prohíben el soborno + +GitHub hace que nuestro compromiso con el anti-soborno sea claro en una cantidad de políticas de la empresa. Como parte de la familia de Microsoft, GitHub también se compromete con la política anticorrupción de Microsoft, que se aplica a todos los empleados y contratistas de GitHub, además de las políticas aquí descritas. + +El **código de ética** de GitHub prohíbe que los empleados y los contratistas participen o contribuyan con el soborno o la corrupción y establece requisitos de mantenimiento de registros: +> Nunca debes pagar, ofrecer pagar, prometer pagar, inducir, aceptar o autorizar el pago de ninguna otra cosa de valor, a ninguna persona, incluyendo a ninguna persona en una posición de poder o autoridad, por ejemplo, funcionarios del gobierno o en transacciones comerciales, con el fin de obtener o mantener negocios, o asegurar cualquier otra ventaja inapropiada para GitHub o Microsoft. Tampoco debes solicitar o aceptar sobornos, ni ningún otro pago indebido en efectivo. ... [Los empleados de GitHub] están obligados a mantener registros precisos y razonables de todas las transacciones que implican cualquier gasto hecho en nombre de GitHub, por ejemplo, al mantener los recibos y proporcionar descripciones precisas de tus gastos, o cualquier otra transacción que implique la eliminación o la transferencia de los activos de GitHub. . . Estas acciones se exigen por la ley de prácticas corruptas extranjeras de los EE. UU., la ley de soborno del Reino Unido de 2010 y las leyes antisoborno de otras jurisdicciones en las que GitHub hace negocios y que también son simplemente la manera correcta de proceder. + +El código ético de GitHub detalla ciertas situaciones, incluyendo sobre regalos, viajes y entretenimiento; facilitación de pagos; donaciones caritativas; puestos laborales y trabajar con representantes, así como la descripción de quién se considera un funcionario del gobierno. + +Las normas de conducta de GitHub prohíben: +> Sobornar a funcionarios del gobierno u otras personas para obtener una ventaja injusta y tomar sobornos de cualquier persona. + +La **política de regalos y entretenimiento** de GitHub explica que el soborno no está permitido en relación con los viajes o el entretenimiento y proporciona ejemplos para ilustrar conductas inadecuadas. La política describe los regalos adecuados e inadecuados, los gastos de viajes y entretenimiento; los procesos de la empresa para que los directores de GitHub, funcionarios, empleados y agentes hagan regalos y los requisitos para el mantenimiento de registros, sanciones; y la denuncia de violaciones. Incluye umbrales monetarios claros para los regalos junto con las limitaciones anuales, con excepciones limitadas para los regalos aprobados por la administración adecuada. La política es clara y de fácil acceso para los empleados y los contratistas de GitHub. + +### Formación para nuestros empleados + +Los empleados de GitHub están obligados a participar en la capacitación sobre corrupción, incluyendo sobornos. También proporcionamos capacitación adicional para personas y equipos particularmente relevantes, como nuestro equipo de ventas. . La capacitación explica los elementos pertinentes de la ley de prácticas corruptas extranjeras de los EE. UU. y la ley de soborno del Reino Unido de 2010. . Por ejemplo, +- definición y efectos estructurales de la corrupción +- que está cubierto, incluyendo + - funcionarios públicos u otros en una posición de poder + - terceros +- qué tipo de actividad está cubierta, incluyendo + - efectivo, regalos, viajes y entretenimiento + - pagos de facilitación + - contribuciones caritativas y patrocinio +- para qué propósito, incluyendo + - intento + - ventaja o influencia incorrecta +- diligencia debida y señales de alerta +- requisitos de mantenimiento de registros + +Además, la capacitación cubre las políticas internas de GitHub relacionadas con la lucha contra la corrupción y el soborno, incluyendo nuestra política de no represalias (denuncia de irregularidades). + +. . Si bien la FCPA de los EE. UU. se enfoca en las interacciones con los oficiales gubernamentales, la ley contra el soborno del Reino Unido es más amplia y se extiende al soborno de cualquiera, sin importar si son un dirigente gubernamental o no. Ambas leyes pueden extenderse a las acciones de GitHub en otro lugar del mundo. Las políticas de GitHub prohíben sobornar a cualquier persona, en cualquier parte del mundo. + +### Involucrar a nuestros socios +- Los acuerdos de reventa de GitHub ** con socios de canal** incluyen cláusulas de anti-corrupción obligatorias. En adelante, GitHub requirá que nuestros socios de canal se comprometan a cumplir con esta declaración anticorrupción. +- En adelante, los **contratos de vendedores** de GitHub requerirán un compromiso para cumplir con el código de conducta del proveedor de Microsoft o con esta declaración anticorrupción. diff --git a/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md new file mode 100644 index 0000000000000..98240b6691ec4 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -0,0 +1,34 @@ +--- +title: Disposición de seguridad legal del programa de recompensas de errores de GitHub +redirect_from: + - /articles/github-bug-bounty-program-legal-safe-harbor +versions: + free-pro-team: '*' +--- + +### Resumen +1. Deseamos que divulgues responsablemente a través de nuestro programa de recompensa de errores y no queremos que los investigadores se atemoricen por las consecuencias legales debido a sus intentos de buena fe para cumplir con nuestra política de recompensas por errores. No podemos vincular a ningún tercero, por lo que no presuponemos que esta protección se extiende a ningún tercero. Si tienes dudas, pregúntanos antes de participar en cualquier acción específica que consideres que _Podría_ vaya fuera de los límites de nuestra política. +2. Dado que tanto la información de identificación como la no identificativa pueden poner a un investigador en riesgo, limitamos lo que compartimos con terceros. Es posible que proporcionemos información sustantiva no identificativa de tu informe a un tercero afectado, pero solo después de notificarte a ti y de recibir un compromiso de que el tercero no perseguirá acciones legales en tu contra. Solo compartiremos la información de identificación (nombre, dirección de correo electrónico, número de teléfono, etc.) con un tercero si le proporcionas tu permiso por escrito. +3. Si tu investigación de seguridad como parte del programa de recompensas por errores viola ciertas restricciones en nuestras políticas del sitio, los términos del puerto seguro permiten una exención limitada. + +### 1. Condiciones de la disposición de seguridad + +Para alentar la investigación y la divulgación responsable de las vulnerabilidades de seguridad, no perseguiremos acciones civiles o penales, o enviaremos un aviso a la aplicación de la ley por violaciones fortuitas o de buena fe de esta política. Consideramos que las investigaciones de seguridad y las actividades de divulgación de vulnerabilidades llevadas a cabo de acuerdo con esta política son conductas "autorizadas" conforme a la ley de fraude y abuso informático, la DMCA y otras leyes aplicables de uso informático, como Código Penal de Cal. 502(c). Renunciamos a cualquier demanda potencial de DMCA en tu contra por eludir las medidas tecnológicas que hemos utilizado para proteger las aplicaciones en este alcance del programa de recompensas de errores. + +Por favor, entiende que si tu investigación de seguridad involucra las redes, sistemas, información, aplicaciones, productos o servicios de un tercero (que no seamos nosotros), no podemos vincular a ese tercero y pueden perseguir acciones legales o aviso de cumplimiento de la ley. No podemos y no autorizamos la investigación de seguridad en el nombre de otras entidades, y de ninguna manera podemos ofrecer defenderte, indemnizarte o protegerte de ninguna manera de cualquier acción de terceros en base a sus acciones. + +Se espera, como siempre, cumplir con todas las leyes aplicables a ti, y no interrumpir o comprometer ningún dato más allá de lo que este programa de recompensas de errores permite. + +Ponte en contacto con nosotros antes de participar en una conducta que puede ser incompatible con esta política o no ser tratada por esta. Nos reservamos el derecho exclusivo de hacer la determinación de si una violación de esta política es accidental o de buena fe y el contacto proactivo con nosotros antes de participar en cualquier acción es un factor significativo en esa decisión. Si tienes dudas, ¡Pregúntanos primero! + +### 2. Disposición de seguridad de terceros + +Si envías un informe a través de nuestro programa de recompensas de errores que afecta a un servicio de terceros, limitaremos lo que compartamos con cualquier tercero afectado. Es posible que compartamos contenido no identificable de tu informe con un tercero afectado, pero solo después de notificarte que tenemos la intención de hacerlo y de obtener el compromiso por escrito del tercero de que no perseguirán acciones legales en tu contra o de iniciar contacto con las fuerzas del orden de las leyes en base a tu informe. No compartiremos tu información de identificación con ningún tercero afectado sin obtener primero tu permiso por escrito para hacerlo. + +Ten en cuenta que no podemos autorizar pruebas fuera de alcance en nombre de terceros y dichas pruebas están fuera del alcance de nuestra política. Consulta la política de recompensas de errores de ese tercer, si tiene una, o comunícate directamente con el tercero o a través de un representante legal antes de iniciar cualquier prueba en ese tercero o en sus servicios. Esto no es, y no debe entenderse como, cualquier acuerdo de nuestra parte para defender, indemnizar o de cualquier otra manera protegerte de cualquier acción de terceros con base a tus acciones. + +Dicho esto, si un tercero inicia una acción legal, incluyendo las fuerzas del orden, en tu contra por tu participación en este programa de recompensa de errores y has cumplido suficientemente con nuestra política de recompensas por errores (es decir, no has hecho violaciones intencionales o de mala fe), tomaremos las medidas para hacer que se conozca que tus acciones se realizaron de conformidad con esta política. Si bien consideramos que los informes presentados son documentos confidenciales y potencialmente privilegiados y protegidos frente a la divulgación forzada en la mayoría de las circunstancias, ten en cuenta que un tribunal puede, a pesar de nuestras objeciones, ordenarnos que compartamos información con un tercero. + +### 3. Exención limitada de otras políticas del sitio + +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. De la misma forma que se menciona anteriormente, si tienes dudas, ¡Pregúntanos primero! diff --git a/translations/es-ES/content/github/site-policy/github-community-forum-code-of-conduct.md b/translations/es-ES/content/github/site-policy/github-community-forum-code-of-conduct.md new file mode 100644 index 0000000000000..3230658684e33 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-community-forum-code-of-conduct.md @@ -0,0 +1,117 @@ +--- +title: Código de conducta del foro de la comunidad GitHub +redirect_from: + - /articles/github-community-forum-code-of-conduct +versions: + free-pro-team: '*' +--- + +### Descripción y propósito + +Millones de programadores albergan millones de proyectos en GitHub — tanto de código abierto como de código cerrado — y tenemos el honor de participar en permitir la colaboración de toda la comunidad de programadores todos los días. Juntos tenemos una emocionante oportunidad y responsabilidad de hacer de esta una comunidad de la que podemos estar orgullosos. + +El Foro de la Comunidad de GitHub está previsto para ser un lugar para más colaboración, apoyo y reunión de reflexión. Este es un lugar civilizado para conectarse con otros usuarios, aprender nuevas habilidades, compartir comentarios e ideas y encontrar todo el apoyo que necesitas para tus proyectos de GitHub. Al participar en esta Comunidad, aceptas los mismos [Términos de Servicio](/articles/github-terms-of-service/) que se aplican a GitHub.com, así como este Código de Conducta específico para la Comunidad. + +Con este Código de Conducta esperamos ayudarte a entender cómo colaborar mejor en el Foro de la Comunidad de GitHub, lo que puedes esperar de los moderadores y qué tipo de acciones o contenidos pueden resultar en una suspensión temporal o permanente de la participación en la Comunidad. Investigaremos cualquier reporte de abuso y podremos moderar el contenido público dentro de la Comunidad que determinemos que viola los Términos de Servicio de GitHub o de este Código de Conducta. + +Los usuarios de GitHub en todo el mundo ofrecen perspectivas, ideas y experiencias diferentes y van desde personas que crearon su primer proyecto "Hola Mundo" la semana pasada hasta los desarrolladores de software más conocidos del mundo. Estamos comprometidos a hacer de GitHub y el Foro de la Comunidad de GitHub un entorno acogedor para todas las diferentes voces y perspectivas aquí, manteniendo un espacio donde la gente es libre de expresarse. + +### Compromiso + +En interés de fomentar un entorno abierto y acogedor, como colaboradores y mantenedores nos comprometemos a hacer de la participación en el Foro de la Comunidad de GitHub una experiencia sin acoso para todos, sin importar la edad, complexión, capacidad, etnicidad, identidad y expresión de género, nivel de experiencia, nacionalidad, apariencia personal, raza, religión o identidad y orientación sexual. + +### Estándares + +Trata el Foro de la Comunidad de GitHub con respeto. Somos un recurso compartido — un lugar para compartir habilidades, conocimientos e intereses a través de una conversación continua. + +Lo siguiente no son normas duras y rápidas, sino ayudas al juicio humano de nuestra Comunidad. Utiliza estas pautas para mantener este lugar limpio y bien iluminado para el discurso público civilizado. + +#### *Mejores prácticas para construir una comunidad sólida* + +- Se respetuoso y considerado. + - **Se bienvenido y abierto.** Es posible que otros miembros de la comunidad no tengan el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para contribuir. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar. + - **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. + + Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación. + - **Comunícate con empatía.** Los desacuerdos o diferencias de opinión son un hecho de la vida. Formar parte de una comunidad significa interactuar con personas de diferentes orígenes y perspectivas, muchas de las cuales pueden no ser propias. Si no estás de acuerdo con alguien, trata de entender y compartir sus sentimientos antes de abordarlos. Esto promoverá un ambiente respetuoso y amistoso donde la gente se sienta cómoda haciendo preguntas, participando en discusiones y haciendo contribuciones. +- Contribuye de forma positiva y constructiva. + - **Mejorar el debate.** Ayúdanos a hacer de esto un gran lugar para el debate trabajando siempre para mejorar la discusión de alguna manera, sin embargo siempre breve. Si no estás seguro de que tu publicación sume a la conversación, piensa en lo que quieres decir e inténtalo de nuevo más tarde. + + Los temas debatidos aquí nos importan y esperamos que actúes como si también te importasen. Se respetuoso con los temas y con las personas que los debaten, aunque no estés de acuerdo con algo de los que se dice. + - **Se claro y enfócate en el tema.** Comunicarse con extraños en Internet puede ser incómodo. Es difícil transmitir o leer el tono y el sarcasmo es frecuentemente mal entendido. Intenta usar un lenguaje claro y piensa cómo será recibido por la otra persona. + + Esto también se aplica al intercambio de vínculos. Cualquier enlace compartido en el Foro de la Comunidad debe compartirse con la intención de proporcionar información relevante y apropiada. Los enlaces no deben publicarse para simplemente conducir el tráfico o la atención a un sitio. Los enlaces siempre deberán ir acompañados de una explicación completa del contenido y propósito de los mismos. Publicar enlaces, especialmente los no solicitados, sin un contexto relevante y valioso puede parecer publicidad o con fines aún más maliciosos. + + Además, el Foro de la Comunidad de GitHub tiene el objetivo de colaborar, compartir ideas y ayudarse mutuamente a hacer cosas. Los comentarios fuera del tema son una distracción (en ocasiones bien recibido, pero generalmente no) sobre realizar el trabajo y ser productivo. Mantener el tema ayuda a producir discusiones positivas y productivas. + - **Comparte con precaución.** Al pedir a otros que te den comentarios o colaboren en un proyecto, solo comparte recursos valiosos y relevantes para proporcionar un contexto. No publiques enlaces que no añadan valor al tema y no publiques enlaces no solicitados a tus propios proyectos o sitios en los temas de otros usuarios. + + Además, no compartas información confidencial. Esto incluye tu propia dirección de correo electrónico. No permitimos compartir dicha información en este Foro de la Comunidad, ya que puede crear riesgos de seguridad y privacidad para la persona que publica, así como para otros usuarios. Si quieres invitar a otros miembros del Foro a colaborar en un proyecto o trabajar contigo, comparte un enlace al repositorio en el que existe el proyecto en el que estás trabajando. Al compartir el enlace al repositorio de tu proyecto - con alguna información sobre lo que es tu proyecto y qué tipo de ayuda o retroalimentación estás buscando, puedes invitar a otros a colaborar contigo a través de temas o solicitudes de extracción sin tener que compartir tu información privada. También puedes añadir a otros como colaboradores externos en el repositorio de tu proyecto para darles permisos especiales que te ayuden a desarrollar tu proyecto. + - **Mantén el orden.** Haz el esfuerzo de colocar las cosas en el lugar correcto, para que podamos pasar más tiempo debatiendo y menos tiempo resolviendo problemas. Así que: + - No inicies un tema en la categoría equivocada. + - No publiques lo mismo en múltiples temas. + - No publiques respuestas sin contenido. + - No "infles" publicaciones, a menos que tengas información nueva y relevante que compartir. + - No desvíes un tema cambiándolo a midstream. + + En lugar de publicar “+1” o “De acuerdo”, utiliza el botón Kudos. En lugar de tomar un tema existente en una dirección radicalmente diferente, abre un nuevo tema. + +- Se digno de confianza. + - **Siempre se honesto.** No compartas conscientemente información incorrecta o confundas intencionalmente a otros miembros del foro de la comunidad de GitHub. Si no conoces la respuesta a la pregunta de alguien pero deseas ayudarle, puedes intentar ayudarle a investigar o encontrar recursos en su lugar. El personal de GitHub también estará activo en la Comunidad, así que si no estás seguro de una respuesta, es probable que un moderador pueda ayudar. + +#### *Lo que no está permitido* + +- **Amenazas de violencia.** No puede amenazar la violencia hacia otros ni utilizar el sitio para organizar, promover o incitar a actos de violencia o terrorismo en el mundo real. Piensa detenidamente en las palabras que usas, las imágenes que publicas e incluso el software que escribas y cómo lo pueden interpretar otros. Incluso si dices algo como una broma, es posible que no se reciba de esa forma. Si crees que alguien más pudiera interpretar el contenido que publicas como una amenaza, o como promoción de violencia o terrorismo, detente. No lo publiques. En casos extraordinarios podemos denunciar amenazas de violencia a la aplicación de la ley si creemos que puede haber un verdadero riesgo de daños físicos o una amenaza para la seguridad pública. + +- **Discurso de odio y discriminación.** Aunque no está prohibido abordar temas como edad, complexión, capacidad, etnia, identidad de género y expresión, nivel de experiencia, nacionalidad, apariencia personal, raza, religión u identidad y orientación sexual, no toleramos el discurso que ataque a una persona o grupo de personas en función de quiénes son. Sólo date cuenta de que hablar de estos u otros temas delicados puede hacer que otros se sientan insólitos, o quizás incluso inseguros si se enfoca de forma agresiva o aislante. Esperamos que nuestros miembros de la Comunidad sean respetuosos a la hora de debatir temas delicados. + +- **Intimidación y acoso** No toleramos acoso ni intimidación. Esto significa cualquier acoso o intimidación habitual dirigida a una persona o grupo específico de personas. En general, si tus acciones son indeseables y continúas participando en ellas, hay una buena posibilidad de que te dirijas a territorio de intimidación o acoso. + +- **Suplantación.** No puedes suplantar a otra persona copiando su avatar, publicando contenido bajo su dirección de correo electrónico, utilizar intencionalmente un nombre de usuario engañosamente similar o de otro modo hacer publicaciones como alguien más. La suplantación es una forma de acoso. + +- **Doxing e invasión de privacidad** - No publiques información personal de otras personas, como números de teléfono, direcciones de correo electrónico privadas, direcciones físicas, números de tarjetas de crédito, números de seguridad social o de identificación nacional o contraseñas. Dependiendo del contexto, como en el caso de intimidación o acoso, podemos considerar otra información, tales como fotos o vídeos que fueron tomados o distribuidos sin el consentimiento de la persona, una invasión de la privacidad, especialmente cuando dicho material representa un riesgo para la seguridad del sujeto. + +- **Contenido impúdico/sexualmente explícito.** Básicamente, no publique pornografía. Esto no significa que toda la desnudez o contenido sexual esté prohibido. Reconocemos que la sexualidad es parte de la vida y que el contenido sexual no pornográfico puede ser parte de su proyecto o puede presentarse con fines educativos o artísticos. Si tienes alguna pregunta o inquietud sobre algo que quieras publicar, [no dudes en contactar y preguntar](https://support.github.com/contact) de antemano. + +- **Spam.** Respeta el Foro de la Comunidad de GitHub. No publiques anuncios, enlaces a sitios web con spam ni vandalices de otro modo a la Comunidad. Esta comunidad está diseñada para que los usuarios de GitHub debatan sobre proyectos, aprendan y compartan ideas entre sí - no para publicidad u otro contenido como spam. Los contenidos que consideremos spam serán eliminados. + +- **Contenido con derechos de autor o ilegal.** Publica solo tus propias cosas. Eres responsable de lo que publicas. Si publicas algo que no te creaste, debes tener derecho a publicarlo. Ni puedes publicar contenido ilegal, incluyendo contenido ilegal bajo las leyes de copyright y marca registrada, enlaces a contenido ilegal, o métodos para eludir la ley. + +- **Malware activo o explotación de vulnerabilidad** - Ser parte de una comunidad incluye no aprovecharse de otros miembros de la comunidad. No permitimos que nadie utilice nuestra plataforma para la entrega de explotación (p. ej. Utilizar la Comunidad como medio para entregar ejecutables maliciosos) o como infraestructura de ataque (p. ej. Organizar ataques de denegación de servicio o administrar servidores de comandos y control). Sin embargo, ten en cuenta, que no prohibimos la publicación de código fuente que podría utilizarse para desarrollar malware o explotación de vulnerabilidad, ya que la publicación y distribución de dicho código fuente tiene un valor educativo y proporciona un beneficio neto a la comunidad de seguridad. + +- **Cualquier persona menor de 13 años.** Si eres menor de 13 años, no puedes tener una cuenta en el Foro de la Comunidad de GitHub (o en el propio GitHub). GitHub no recopila intencionalmente información de niños menores de 13 años ni dirige ninguno de nuestros contenidos de manera específica a ellos. Si aprendemos o tenemos motivos para sospechar que eres un usuario menor de 13 años, desafortunadamente tendremos que cerrar tanto tu Foro de la Comunidad de GitHub como tus cuentas en GitHub.com. No queremos desalentarte de que aprendas nuestro código, pero esas son las reglas. Consulta nuestras [Términos de servicio](/articles/github-terms-of-service/) para obtener información sobre la cancelación de la cuenta. + +- **Otras conductas que podrían considerarse razonablemente inadecuadas en un entorno profesional.** El Foro de la Comunidad de GitHub es un espacio profesional y debe ser tratado como tal. + +### Cumplimiento + +#### *Qué actividades pueden realizar los miembros de los foros de la comunidad de GitHub* + +- **Si ves un problema, repórtalo.** Los moderadores tienen autoridad especial; son responsables de esta comunidad. Pero tú también. Con tu ayuda, los moderadores pueden ser facilitadores de la comunidad, no sólo personal de limpieza o policía. + + Cuando observes un mal comportamiento, no respondas. Fomenta el mal comportamiento al reconocerlo, consume tu energía y pierde el tiempo de todos. Simplemente repórtalo a través de "Reporte de contenido inapropiado" en el Menú Opción. Si se acumulan suficientes informes, se tomarán medidas, ya sea automáticamente o mediante la intervención del moderador. + +#### Nuestras responsabilidades + +Existe una variedad de acciones que podemos tomar en respuesta al comportamiento o contenido inadecuado. Por lo general, depende de las circunstancias exactas de un caso en particular. Reconocemos que en ocasiones la gente puede decir o hacer cosas inadecuadas por diversas razones. Tal vez no se dieron cuenta de cómo se percibirían sus palabras. O tal vez sólo dejan que sus emociones saquen lo mejor de ellos. Por supuesto, en ocasiones, hay gente que sólo quiere hacer spam o causar problemas. + +Cada caso requiere un enfoque diferente, e intentamos adaptar nuestra respuesta para satisfacer las necesidades de la situación. Revisaremos cada situación caso por caso. En cada caso, tendremos un equipo diverso que investigue el contenido y los hechos relacionados y responda según corresponda, usando este Código de Conducta para guiar nuestra decisión. + +Las acciones que podemos llevar a cabo en respuesta a un reporte de abuso incluyen, pero no se limitan a: + - Eliminación de contenido + - Bloqueo de contenido + - Suspensión de la cuenta del Foro de la Comunidad + - Terminación de la cuenta del Foro de la Comunidad + +Los moderadores del Foro de la Comunidad que no sigan o no hagan cumplir el Código de Conducta de buena fe pueden enfrentarse a repercusiones temporales o permanentes según lo determine el liderazgo de otros miembros del Foro de la Comunidad. + +### Contacto con el personal de GitHub + +Si por cualquier razón quieres contactar en privado al personal de GitHub, los Gerentes Comunitarios, Administradores o Moderadores de este foro, puedes utilizar nuestro [Formulario de contacto para soporte](https://support.github.com/contact?tags=community-support). Se recomienda fuertemente que no contactes a ningún miembro del personal de GitHub a través de cualquier canal diferente al foro mismo o del formato de contacto para soporte y, el hacerlo, podria considerarse como una violación a nuestra prohibición contra el acoso. + +Trabajemos juntos para mantener el foro un lugar donde las personas se sientan seguras de participar por ser respetuosas con ellos y su tiempo. + +### Avisos legales + +Sí, los términos legales son aburridos, pero debemos protegernos –y por extensión, tú y tus datos– de las personas poco amistosas. Tenemos [Términos de Servicio](/articles/github-terms-of-service/) y la [Declaración de Privacidad](/articles/github-privacy-statement/) que describe tu comportamiento (y nuestro) y los derechos relacionados con el contenido, privacidad y leyes. Para utilizar este servicio, debes aceptar cumplir nuestros [Términos de Servicio](/articles/github-terms-of-service/) y la [Declaración de Privacidad](/articles/github-privacy-statement/). + +Este Código de Conducta no modifica nuestros [Términos de Servicio](/articles/github-terms-of-service/) y no pretende ser una lista completa. GitHub conserva toda la discreción bajo los [Términos de Servicio](/articles/github-terms-of-service/) para eliminar cualquier contenido o cancelar cualquier cuenta de actividad que sea "ilegal, ofensivo, amenazante, calumnioso, difamatorio, pornográfico, obsceno o de otro modo censurable o que viole la propiedad intelectual de cualquier parte o estos Términos de Servicio. Este Código de Conducta describe cuándo ejerceremos esa discreción. diff --git a/translations/es-ES/content/github/site-policy/github-community-guidelines.md b/translations/es-ES/content/github/site-policy/github-community-guidelines.md new file mode 100644 index 0000000000000..c050a9680648f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-community-guidelines.md @@ -0,0 +1,88 @@ +--- +title: Pautas de la comunidad GitHub +redirect_from: + - /community-guidelines/ + - /articles/github-community-guidelines +versions: + free-pro-team: '*' +--- + +Millones de desarrolladores albergan millones de proyectos en GitHub — tanto de código abierto como de código cerrado — y tenemos el honor de participar en la colaboración de toda la comunidad todos los días. Juntos tenemos una emocionante oportunidad y responsabilidad de hacer de esta una comunidad de la que podemos estar orgullosos. + +Los usuarios de GitHub en todo el mundo ofrecen perspectivas, ideas y experiencias diferentes y van desde personas que crearon su primer proyecto "Hola Mundo" la semana pasada hasta los desarrolladores de software más conocidos del mundo. Estamos comprometidos a hacer de GitHub un ambiente acogedor para todas las diferentes voces y perspectivas de nuestra comunidad, manteniendo un espacio donde la gente sea libre de expresarse. + +Dependemos de nuestros miembros de la comunidad para que comuniquen las expectativas, [moderen](#what-if-something-or-someone-offends-you) sus proyectos, y {% data variables.contact.report_abuse %} o {% data variables.contact.report_content %}. Al esbozar lo que esperamos ver dentro de nuestra comunidad, esperamos ayudarte a entender cómo colaborar de mejor forma en GitHub y qué tipo de acciones o contenido pueden violar nuestros [Términos de servicio](#legal-notices), que incluyen nuestras [Políticas de uso aceptables](/github/site-policy/github-acceptable-use-policies). Investigaremos cualquier reporte de abuso y podremos moderar el contenido público en nuestro sitio que determinemos que infringe nuestros Términos de Servicio. + +### Construir una comunidad sólida + +El propósito principal de la comunidad de GitHub es colaborar en proyectos de software. Deseamos que la gente trabaje mejor juntos. Aunque mantenemos el sitio, esta es una comunidad que construimos *juntos* y necesitamos tu ayuda para que sea lo mejor. + +* **Se cordial y de mentalidad abierta** - Otros colaboradores pueden no tener el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para aportar. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar. + +* **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. + + Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación. + +* **Comunícate con empatía.** Los desacuerdos o diferencias de opinión son un hecho de la vida. Formar parte de una comunidad significa interactuar con personas de diferentes orígenes y perspectivas, muchas de las cuales pueden no ser propias. Si no estás de acuerdo con alguien, trata de entender y compartir sus sentimientos antes de abordarlos. Esto promoverá un ambiente respetuoso y amistoso donde la gente se sienta cómoda haciendo preguntas, participando en discusiones y haciendo contribuciones. + +* **Se claro y permanece en el tema** -Las personas usan GitHub para hacer el trabajo y ser más productivos. Los comentarios fuera del tema son una distracción (en ocasiones bien recibido, pero generalmente no) sobre realizar el trabajo y ser productivo. Mantener el tema ayuda a producir discusiones positivas y productivas. + + Además, comunicarse con extraños en Internet puede ser incómodo. Es difícil transmitir o leer el tono y el sarcasmo es frecuentemente mal entendido. Intenta usar un lenguaje claro y piensa cómo será recibido por la otra persona. + +### ¿Qué pasa si algo o alguien te ofende? + +Confiamos en que la comunidad nos comunique cuándo sea necesario abordar una cuestión. No monitoreamos activamente el sitio por contenido ofensivo. Si encuentras algo o alguien en el sitio que sea censurable, aquí hay algunas herramientas que proporciona GitHub para ayudarte a tomar acción inmediatamente: + +* **Comunica las expectativas** - Si participas en una comunidad que no haya establecido sus propias pautas específicas de la comunidad, invítalos a realizarlo en el archivo README o [CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/), o en [un código de conducta dedicado](/articles/adding-a-code-of-conduct-to-your-project/), enviando una solicitud de extracción. + +* **Modera comentarios** - Si tienes [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) para un repositorio, puedes editar, eliminar u ocultar los comentarios de cualquier persona sobre confirmaciones, solicitudes de extracción y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Los autores del comentario y las personas con acceso de escritura a un repositorio pueden eliminar información confidencial del historial de edición de un comentario. Para obtener más información, consulta "[Seguimiento de cambios en un comentario](/articles/tracking-changes-in-a-comment)" y "[Gestión de comentarios perturbadores](/articles/managing-disruptive-comments)." + +* **Bloquea Conversaciones**- Si una discusión en una propuesta o solicitud de extracción sale de control, puedes [bloquear la conversación](/articles/locking-conversations/). + +* **Bloquea usuarios** - Si encuentras a un usuario que continúa presentando un mal comportamiento, puedes [bloquear al usuario desde su cuenta personal](/articles/blocking-a-user-from-your-personal-account/) o [bloquear al usuario desde su organización](/articles/blocking-a-user-from-your-organization/). + +Claro que siempre podrás contactarnos en {% data variables.contact.report_abuse %} si necesitas más ayuda con alguna situación. + +### ¿Qué no está permitido? + +Estamos comprometidos a mantener una comunidad donde los usuarios sean libres de expresarse y desafiar las ideas de los demás, tanto técnicas como de otro tipo. Sin embargo, es poco probable que dichos debates fomenten un diálogo fructífero cuando se silencian las ideas porque los miembros de la comunidad están siendo bloqueados o tienen miedo de hablar. Esto significa que deberías ser respetuoso y civil en todo momento y que deberías esforzarse por no atacar a los demás considerando quiénes son. No toleramos un comportamiento que cruce la línea de lo siguiente: + +- #### Amenaza de violencia - No puedes amenazar con violencia a otros ni usar el sitio para organizar, promover o incitar a actos de violencia o terrorismo en el mundo real. Piensa detenidamente en las palabras que usas, las imágenes que publicas e incluso el software que escribas y cómo lo pueden interpretar otros. Incluso si dices algo como una broma, es posible que no se reciba de esa forma. Si crees que alguien más *podría* interpretar el contenido que publicas como una amenaza o como una promoción de la violencia o el terrorismo, detente. No lo publiques en GitHub. En casos extraordinarios podemos denunciar amenazas de violencia a la aplicación de la ley si creemos que puede haber un verdadero riesgo de daños físicos o una amenaza para la seguridad pública. + +- #### Discurso de odio y discriminación - Aunque no está prohibido abordar temas como edad, complexión corporal, discapacidad, etnia, identidad de género y expresión, nivel de experiencia, nacionalidad, apariencia personal, raza, religión e identidad y orientación sexual, no toleramos el discurso que ataque a una persona o grupo de personas en función de quiénes son. Sólo date cuenta de que cuando se trata de una forma agresiva o insultante, estos (y otros) temas delicados pueden hacer que otros se sientan no deseados o incluso inseguros. Aunque siempre existe la posibilidad de malentendidos, esperamos que los miembros de nuestra comunidad continúen siendo respetuosos y corteses cuando discutan temas delicados. + +- #### Acosamiento y acoso No toleramos la intimidación o acoso. Esto significa cualquier acoso o intimidación habitual dirigida a una persona o grupo específico de personas. En general, si tus acciones son indeseables y continúas participando en ellas, hay una buena posibilidad de que te dirijas a territorio de intimidación o acoso. + +- #### Interrumpir la experiencia de otros usuarios Ser parte de una comunidad incluye reconocer cómo afecta tu comportamiento a los demás y tu participación en interacciones significativas y productivas con las personas y la plataforma en la que confían. No están permitidos los comportamientos tales como publicar repetidamente comentarios fuera del tema, abrir asuntos sin contenido o sin sentido o solicitudes de extracción o usar cualquier otra característica de la plataforma de una manera que interrumpa continuamente la experiencia de otros usuarios. Mientras animamos a los mantenedores a moderar sus propios proyectos de forma individual. El personal de GitHub puede tomar medidas más restrictivas contra las cuentas que están participando en este tipo de comportamientos. + +- #### Suplantación No puedes intentar engañar a los demás en cuanto a tu identidad al copiar el avatar de otra persona, publicar contenido bajo su dirección de correo electrónico, usar un nombre de usuario similar o presentarte de otra manera como alguien más. La suplantación es una forma de acoso. + +- #### Doxing e invasión de privacidad - No publiques información personal de otras personas, como números de teléfono, direcciones de correo electrónico privadas, direcciones físicas, números de tarjetas de crédito, números de seguridad social o de identificación nacional o contraseñas. Dependiendo del contexto, como en el caso de intimidación o acoso, podemos considerar otra información, tales como fotos o vídeos que fueron tomados o distribuidos sin el consentimiento de la persona, una invasión de la privacidad, especialmente cuando dicho material representa un riesgo para la seguridad del sujeto. + +- #### Contenido sexualmente obsceno - No publiques contenido pornográfico. Esto no significa que toda la desnudez o todo el código y contenido relacionados con la sexualidad, esté prohibido. Reconocemos que la sexualidad es parte de la vida y que el contenido sexual no pornográfico puede ser parte de su proyecto o puede presentarse con fines educativos o artísticos. No permitimos contenidos sexuales obscenos que puedan implicar la explotación o la sexualización de menores. + +- #### Contenido violento injustificadamente - No publiques imágenes, texto u otro contenido sin un contexto o advertencias razonables. Aunque a menudo es correcto incluir contenido violento en videojuegos, reportes de noticias y descripciones de acontecimientos históricos, no permitimos contenido violento que se publique de forma indiscriminada o que se publique de una manera que dificulte a otros usuarios evitarlo (por ejemplo, un avatar de perfil o un comentario sobre una propuesta). Una clara advertencia o renuncia de responsabilidad en otros contextos ayuda a los usuarios a tomar una decisión educada sobre si quieren participar en dichos contenidos o no. + +- #### Información errónea y desinformación - No puedes publicar contenido que presente una visión distorsionada de la realidad, ya sea inexacta o falsa (información errónea) o que sea intencionalmente engañosa (desinformación) donde dicho contenido probablemente resulte en daño al público o que interfiera con oportunidades justas y equitativas para que todos participen en la vida pública. Por ejemplo, no permitimos contenido que pueda poner el bienestar de grupos de personas en riesgo o limitar su capacidad de participar en una sociedad libre y abierta. Fomentamos la participación activa en la expresión de ideas, perspectivas y experiencias y podríamos no estar en posición de disputar cuentas personales u observaciones. Por lo general, permitimos la parodia y la sátira que está en línea con nuestras políticas de uso aceptable y consideramos que el contexto es importante en la manera en que se recibe y se entiende la información; por lo tanto, puede ser adecuado aclarar tus intenciones mediante renuncias u otros medios, así como la fuente(s) de tu información. + +- #### Malware activo o explotación de vulnerabilidad - Ser parte de una comunidad incluye no aprovecharse de otros miembros de la comunidad. No permitimos que nadie utilice nuestra plataforma para la entrega de explotación de vulnerabilidad, por ejemplo usar GitHub como un medio para entregar ejecutables maliciosos, o como infraestructura de ataques, por ejemplo organizando ataques de denegación de servicio o gestionando servidores de comando y control. Sin embargo, ten en cuenta, que no prohibimos la publicación de código fuente que podría utilizarse para desarrollar malware o explotación de vulnerabilidad, ya que la publicación y distribución de dicho código fuente tiene un valor educativo y proporciona un beneficio neto a la comunidad de seguridad. + + +### ¿Qué sucede si alguien no comple con las reglas? + +Hay una serie de acciones que podemos tomar cuando un usuario reporta un comportamiento o contenido inadecuado. Por lo general, depende de las circunstancias exactas de un caso en particular. Reconocemos que en ocasiones la gente puede decir o hacer cosas inadecuadas por diversas razones. Tal vez no se dieron cuenta de cómo se percibirían sus palabras. O tal vez sólo dejan que sus emociones saquen lo mejor de ellos. Por supuesto, en ocasiones, hay gente que sólo quiere hacer spam o causar problemas. + +Cada caso requiere un enfoque diferente e intentamos adaptar nuestra respuesta para satisfacer las necesidades de la situación que se ha informado. Revisaremos cada informe de abuso caso por caso. En cada caso, tendremos un equipo diverso que investigue el contenido y los hechos relacionados y responda según corresponda, utilizando estas directrices para guiar nuestra decisión. + +Las acciones que podemos emprender en respuesta a un informe de abuso incluyen, pero no se limitan a: + +* Eliminación de contenido +* Bloqueo de contenido +* Suspensión de la cuenta +* Terminación de la cuenta + +### Avisos legales + +Dedicamos estas Pautas de la Comunidad al dominio público para que cualquiera pueda usar, reutilizar, adaptar o lo que sea, bajo los términos de [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/). + +Estas son solo directrices; no modifican nuestros [Términos de Servicio](/articles/github-terms-of-service/) y no pretenden ser una lista completa. GitHub mantiene total discreción bajo los [Términos de Servicio](/articles/github-terms-of-service/#c-acceptable-use) para eliminar cualquier contenido o cancelar cualquier cuenta por actividad que infrinja nuestros Términos del Uso Aceptable. Estas directrices describen en qué situaciones ejerceremos dicha discreción. diff --git a/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md new file mode 100644 index 0000000000000..68cc7a320dd02 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md @@ -0,0 +1,313 @@ +--- +title: Términos de servicio corporativos de GitHub +redirect_from: + - /articles/github-corporate-terms-of-service +versions: + free-pro-team: '*' +--- + +GRACIAS POR ELEGIR GITHUB PARA CUBRIR LAS NECESIDADES COMERCIALES DE SU EMPRESA. LEE ESTE ACUERDO CUIDADOSAMENTE YA QUE RIGE EL USO DE LOS PRODUCTOS (COMO SE DEFINEN A CONTINUACIÓN), A MENOS QUE GITHUB HAYA CELEBRADO UN ACUERDO POR ESCRITO POR SEPARADO CON EL CLIENTE PARA DICHO PROPÓSITO. AL HACER CLIC EN EL BOTÓN "ACEPTO" O EN UN BOTÓN SIMILAR O AL UTILIZAR CUALQUIERA DE LOS PRODUCTOS, EL CLIENTE ACEPTA TODOS LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO. SI EL CLIENTE ESTÁ CELEBRANDO ESTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA PERSONA MORAL, EL CLIENTE REPRESENTA QUE TIENE LA AUTORIDAD LÉGAL DE VINCULAR A LA EMPRESA U OTRAS PERSONAS MORALES AL PRESENTE ACUERDO. + +### Términos de servicio corporativos de GitHub +Fecha de entrada en vigencia de la versión: 16 de noviembre de 2020 + +El presente Acuerdo se aplica a las siguientes ofertas de GitHub, como se define a continuación (colectivamente, los **“Productos”**): +- El servicio; +- Cualquier Vista previa Beta; +- Cualquier Soporte relacionado; y +- Cualquier Servicio profesional relacionado. + +### A. Definiciones + +**"Filial"** significa cualquier entidad que controle directa o indirectamente, esté controlada por, o esté bajo control común con una parte donde el "control" signifique tener más del cincuenta por ciento (50%) de la propiedad o el derecho a dirigir la gestión de la entidad. + +**"Acuerdo"** significa, colectivamente, todos los términos, condiciones, avisos contenidos o referenciados en este documento y todas las demás reglas operativas. políticas y procedimientos que GitHub puede publicar periódicamente en el Servicio. Las políticas de sitio de GitHub están disponibles en [https://docs.github.com/categories/site-policy](/categories/site-policy). + +**“Todos los usuarios”** se refiere, en conjunto, a los Usuarios del Cliente y los Usuarios externos que usan el Servicio. + +**“Américas”** se refiere a los Estados Unidos, Canadá, México o un país de América Central o América del Sur o el Caribe. + +**"Vistas previas beta"** se refiere al software, los servicios o las funciones identificadas como alfa, beta, vista previa, acceso temprano o evaluación, o a las palabras o frases con significados similares. + +**"Información confidencial"** se refiere a toda la información no pública divulgada por cualquiera de las Partes a otros, ya sea por escrito, en forma oral o por otros medios, designada como confidencial o que la Parte receptora sabe o razonablemente debe saber, conforme a las circunstancias en torno a la divulgación y la naturaleza de la información, que es confidencial para la Parte reveladora. Para evitar dudas, ningún Contenido publicado en el Servicio se considerará Información confidencial excepto el Contenido del Cliente almacenado únicamente en los Repositorios privados del Cliente. La Información confidencial no incluye ninguna información que (i) era de conocimiento público o se dio a conocer públicamente por motivos ajenos a la parte receptora; (ii) era legítimamente conocida o se dio a conocer en forma legítima a la Parte receptora sin restricciones de propiedad o confidencialidad por parte de una fuente que no es la parte reveladora y que tiene derecho a divulgarla; (iii) es aprobada por la Parte reveladora para su divulgación sin restricciones en un documento escrito firmado por un funcionario debidamente autorizado de dicha Parte reveladora; (iv) la Parte receptora desarrolla independientemente sin el acceso a la Información confidencial de la otra Parte ni el uso de esta; o (v) está o estuvo almacenada o publicada en el Servicio y fuera de los Repositorios privados del Cliente. + +**"Contenido"** significa, sin limitaciones, código, texto, datos, artículos, imágenes, paquetes, fotografías, gráficos, software, aplicaciones, diseños, características y otros materiales que se destacan, muestran o se ponen a disposición a través del Servicio. + +**"Cuenta corporativa"** se refiere a una cuenta creada por el Usuario en nombre de una entidad. + +**"Cliente"** se refiere a la empresa u organización que ha celebrado el presente Acuerdo con GitHub haciendo clic en el botón "AGREE" o similar o ingresando a los Productos. + +**"Customer Content"** means Content that Customer creates, owns, or to which Customer holds the rights. + +**"Documentación"** hace referencia a cualquier manual, documentación y otros materiales de soporte relacionados con los productos que GitHub proporciona o pone a disposición del cliente. + +**"Fecha efectiva"** es la fecha anterior sobre la cual el cliente (i) hace clic en "Acepto" los términos y condiciones de este acuerdo, o (ii) hace primero un pedido de los Productos. + +**"Usuario externo"** se refiere a un individuo, que no incluye a los Usuarios del Cliente, que visita o usa el Servicio. + +**"Feedback"** means any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback on GitHub products or services. + +**"Cuotas"** hace referencia las tarifas que el Cliente debe pagar a GitHub para (i) usar los Productos durante el término aplicable o (ii) recibir Servicios Profesionales, ya que dichas tarifas se reflejan en un Formulario de Pedido o SOW. + +**“Fork”** means to copy the Content of one repository into another repository. + +**"GitHub"** significa GitHub, Inc., sus filiales y sus representantes. + +**"GitHub Content"** means Content that GitHub creates, owns, or to which it holds the rights. + +**“Machine Account”** means an account registered by an individual human who accepts the applicable terms of service on behalf of the Machine Account, provides a valid email address, and is responsible for its actions. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una Cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. + +**"Formulario de pedidos"** significa documentación escrita o electrónica (incluyendo una cotización), que las Partes pueden utilizar para ordenar los Productos. + +**“Organization”** means a shared workspace that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. Un Usuario puede ser miembro de más de una Organización. + +**“Private Repository”** means a repository which allows a User to control access to Content. + +**"Servicios Profesionales"** se refiere a la capacitación, consulta o servicios de implementación que GitHub proporciona al Cliente de acuerdo con una SOW ejecutada recíprocamente. Los Servicios profesionales no incluyen el Soporte. + +**"Professional Services Credits"** means the upfront payment method for purchasing Professional Services (exclusive of travel and lodging expenses) that Customer may use over a period of twelve (12) months (unless otherwise stated in an Order Form) for Professional Services. Cualquier Crédito de servicios profesionales que quede sin uso luego de los doce (12) meses posteriores a la fecha de compra (o como se indique en un Formulario de pedidos) quedará automáticamente cancelado y no será reembolsable. + +**“Public Repository”** means a repository whose Content is visible to All Users. + +**"Representantes"** hace referencia a los empleados, oficiales, agentes, contratistas independientes, consultores y asesores jurídicos y financieros. + +**“Scraping”** means extracting data from the Service via an automated process, such as a bot or webcrawler, and does not include the collection of information through GitHub's API. + +**"Servicio"** significa el servicio alojado de GitHub y cualquier Documentación aplicable. + +**"SOW"** significa una declaración de trabajo ejecutada recíprocamente que detalla los Servicios Profesionales que GitHub realizará, cualquier tarifa relacionada y las obligaciones relacionadas con cada parte. + +**"Licencia de suscripción"** hace referencia a la licencia asignada a cada Usuario para instalar, operar, ingresar y utilizar el Servicio en nombre del Cliente. El cliente sólo puede asignar una Licencia de Suscripción por Usuario a través de sus Organizaciones. Para mayor claridad, una vez que el Cliente asigna una Licencia de Suscripción a un Usuario, el Cliente no estará autorizado a bifurcar la Licencia de Suscripción de modo que un Usuario podrá usar una Licencia de Suscripción en una Organización mientras que otro Usuario utiliza la misma Licencia de Suscripción en otra Organización. + +**“Soporte”** se refiere al soporte técnico para el Servicio que GitHub puede proporcionar. + +**"Usuario"** significa una cuenta individual o de máquina que (a) ingresa o utiliza el Servicio, (b) ingresa o utilizar cualquier parte de la cuenta del cliente; o (c) dirige el uso de la cuenta del Cliente en el desempeño de las funciones, en cada caso en nombre del Cliente. La cantidad de Usuarios no debe exceder el número de Licencias de suscripción que el Cliente compró. + +**“User-Generated Content”** means Content created or owned by a third party or External User. + +### B. Términos de la cuenta + +#### 1. Account Controls. + * _Usuarios._ El cliente reconoce que los Usuarios conservan el control administrativo definitivo sobre sus cuentas individuales y el Contenido dentro de ellas. [GitHub's Standard Terms of Service](/articles/github-terms-of-service) govern Users' use of the Service, except with respect to Users' activities under this Section B. + + * _Organizaciones._ El cliente conserva el control administrativo definitivo sobre cualquier organización creada en nombre del cliente y el contenido generado por el usuario publicado en los repositorios dentro de la(s) organización(es), sujeto a esta Sección B. Esta Sección B regirá el uso de la Organización(es) del Cliente. + +#### 2. Requisitos de la cuenta +Para crear una cuenta, el Cliente debe adherirse a los siguientes puntos: + +* El cliente no debe crear una cuenta para el uso de ninguna persona menor de 13 años. Si GitHub se entera de que existe algún Usuario menor de 13 años, cancelará esa cuenta de Usuario de inmediato. Si el Cliente o su(s) Usuario(s) están ubicados en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. + +* El inicio de sesión de un usuario no puede compartirse por varias personas. + +- El cliente no debe utilizar los productos (a) si violan las leyes de sanción o de control de exportaciones de los Estados Unidos o de cualquier otra jurisdicción aplicable; (b) si se ubica en, o si es residente ordinario de un país o territorio que esté sujeto a sanciones generales que administre la Oficina de Control de Bienes Extranjeros (OFAC, por sus siglas en inglés); o (c) si es, o si trabaja en nombre de un [Nacional Especialmente designado (SDN, por sus siglas en inglés)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o de una persona sujeta a un bloqueo similar o a la que se le niegan las prohibiciones de dicha parte. For more information, please see our [Export Controls policy](/articles/github-and-export-controls). + +#### 3. Seguridad de la cuenta +El Cliente es responsable de: (i) todo el Contenido publicado y la actividad que se produce bajo su Cuenta Corporativa; (ii) mantener la seguridad de las credenciales de inicio de sesión de su cuenta; y (iii) [notificar rápidamente a GitHub](https://github.com/contact) al darse cuenta de cualquier uso no autorizado de, o ingreso al Servicio a través de su cuenta. GitHub no será responsable de ninguna pérdida o daño por el incumplimiento por parte del Cliente de esta Sección B. + +#### 4. Términos de terceros +En algunas situaciones, pueden aplicarse términos de terceros al uso del Cliente de GitHub. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Aunque este Acuerdo es el acuerdo completo de GitHub con el Cliente, los términos de otras partes rigen sus relaciones con el Cliente. + +#### 5. Feriado en EE.UU. Términos del Gobierno federal de los EE.⁰UU +Si el cliente es una entidad gubernamental de los EE.UU. o accede o utiliza de otra manera el servicio en calidad de gobierno, aplicará la [Enmienda del Gobierno Federal de los EE.UU.](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users), y el cliente acordará con estas disposiciones. + +#### 6. Acuerdo sobre los Niveles de Servicio de Enterprise Cloud +El compromiso de tiempo activo trimestral de Github para Github Enterprise Cloud se proporciona en el [Acuerdo de Nivel de Servicio Empresarial](/github/site-policy/github-enterprise-service-level-agreement). Si el cliente se registra para GitHub Enterprise Cloud, entonces éste será acreedor a un crédito de servicio en caso de que GitHub no cumpla con sus niveles de servicio. + +### C. Cumplimiento con las leyes; Uso aceptable; Privacidad + +#### 1. Cumplimiento con las leyes y regulaciones +El uso del cliente de los Productos no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o marcas comerciales, leyes de control de exportación o regulaciones en su jurisdicción. + +#### 2. Uso aceptable +El uso que el Cliente dé al servicio deberá cumplir con las [Políticas de Uso Aceptado de GitHub](/articles/github-acceptable-use-policies) y los [Lineamientos de la Comunidad de GitHub](/articles/github-community-guidelines). El Cliente no debe usar el Servicio en ninguna jurisdicción si contiene Contenidos o actividades ilegales, obscenos, ofensivos o fraudulentos, tales como promover o causar daño, vulnerar la integridad o la seguridad de una red o sistema o interferir en ellos, evadir filtros, enviar mensajes no solicitados, abusivos o engañosos, virus o códigos perjudiciales, o socavar los derechos de terceros. + +#### 3. Privacy +La [Declaración de Privacidad de GitHub](/articles/github-privacy-statement) y la [Adenda de Protección de Datos de Github](/github/site-policy/github-data-protection-addendum) proporcionan una notificación detallada de las prácticas de privacidad y para el uso de datos de GitHub así como el procesamiento de GitHub y las obligaciones de seguridad con respecto a los Datos Personales del Cliente. Cualquier persona, entidad o servicio que recolecte datos del Servicio debe cumplir con la Declaración de Privacidad de GitHub, en particular en lo que se refiere a la recopilación de datos personales de los usuarios (como se define en la Declaración de Privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos. + +### D. Responsabilidad del Contenido; Propiedad; Derechos de la licencia + +#### 1. Responsabilidad para el Contenido generado por el usuario +El Cliente puede crear o cargar Contenido generado por el Usuario mientras usa el Servicio. El cliente es el único responsable de cualquier Contenido Generado por el Usuario que publique, suba, enlace o ponga a disposición a través del Servicio, independientemente de la forma de ese Contenido Generado por el Usuario. GitHub no es responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. + +#### 2. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia +El cliente mantiene la propiedad del Contenido del Cliente que este crea o posee. El Cliente reconoce lo siguiente: (a) que es responsable del Contenido del Cliente, (b) que solo enviará el Contenido del Cliente que el Cliente tenga derecho a publicar (incluido el Contenido generado por el Usuario o por terceros) y (c) que el Cliente cumplirá plenamente con cualquier licencia de terceros relacionada con el Contenido del Cliente que el Cliente publica. El Cliente otorga los derechos establecidos en las Secciones D.3 a D.6, de forma gratuita y para los propósitos identificados en dichas secciones hasta que el Cliente retire el Contenido del Cliente de los servidores de GitHub, excepto por el contenido que el cliente ha anunciado públicamente y que los usuarios externos han bifurcado, en cuyo caso la licencia es perpetua hasta que todos los Forks del Contenido del Cliente se hayan eliminado de los servidores de GitHub. Si el Cliente carga Contenido del Cliente que ya viene con una licencia y le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. + +#### 3. Licencia otorgada +El cliente otorga a GitHub el derecho de almacenar, archivar, analizar y mostrar el contenido del cliente y realizar copias incidentales, sólo cuando sea necesario para proporcionar el Servicio, incluyendo la mejora del Servicio con el paso del tiempo. Esta licencia incluye el derecho a copiar el contenido del cliente a la base de datos de GitHub y hacer copias de seguridad; mostrar el contenido del cliente al cliente y a aquellos a quienes el cliente decide mostrarlo; analizar el contenido del cliente en un índice de búsqueda o analizarlo en los servidores de GitHub; compartir el contenido del cliente con usuarios externos con quienes el cliente desee compartirlo; y ejecutar el contenido del cliente, en caso de que sea algo como música o vídeo. Estos derechos se aplican tanto a los Repositorios privados como a los públicos. Esta licencia no otorga a GitHub el derecho de vender Contenido del Cliente. Tampoco otorga a GitHub el derecho de distribuir o usar Contenido del Cliente fuera de nuestra prestación del Servicio, excepto a que como parte del derecho a archivar el contenido del cliente, GitHub pueda permitir que nuestros socios almacenen y archiven el contenido del cliente en los repositorios públicos en conexión con el Programa del Código Ártico de GitHub y el Archivo GitHub. El Cliente le otorga a GitHub los derechos que necesita para usar el Contenido del Cliente sin atribución y para hacer las adaptaciones razonables del Contenido del Cliente como sea necesario para proporcionar el Servicio. + +#### 4. Otorgamiento de la Licencia a Usuarios Externos +Cualquier Contenido que el Cliente anuncie públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de usuarios externos, puede ser visto por otros. El Cliente acepta permitir que Usuarios externos vean y bifurquen los repositorios del Cliente cuando configura sus repositorios para que se vean públicamente. Si el Cliente coloca sus páginas y repositorios para ser vistos públicamente, el Cliente concede a los usuarios externos una licencia no exclusiva a nivel mundial para usar, mostrar, y realizar Contenido del Cliente a través del Servicio y reproducir Contenido del Cliente únicamente en el Servicio según lo permitido a través de la funcionalidad proporcionada por GitHub (por ejemplo, a través de Forking). El Cliente puede conceder más derechos al Contenido del Cliente si adopta una licencia. Si el Cliente está cargando Contenido del Cliente que no creó ni posee, el Cliente es responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos + +#### 5. Contribuciones conforme a la Licencia del repositorio +Cada vez que el cliente añade contenido a un repositorio que contiene una notificación de una licencia, otorga licencias a dicho contenido bajo los mismos términos y acepta que tiene derecho a licenciarlo bajo dichos términos. Si el Cliente tiene un acuerdo por separado para licenciar dicho contenido bajo términos diferentes, tales como un contrato de licencia de colaborador, ese acuerdo prevalecerá. + +#### 6. Derechos morales +El Cliente conserva todos los derechos morales sobre el Contenido del Cliente que carga, publica o envía a cualquier parte del Servicio, incluidos los derechos de integridad y atribución. Sin embargo, el cliente renuncia a estos derechos y acuerda no establecerlos contra GitHub, únicamente para permitir a GitHub ejercer razonablemente los derechos otorgados en la Sección D, pero no de otro modo. + +### E. Repositorios privados + +#### 1. Control +El cliente es responsable de administrar el acceso a sus Repositorios Privados, incluyendo invitaciones, control administrativo de Organizaciones y equipos y de acceso. + +#### 2. Confidencialidad +GitHub considera que el Contenido del Cliente en los Repositorios privados del Cliente constituye Información confidencial del Cliente. GitHub protegerá y mantendrá estrictamente confidencial el Contenido del Cliente de los Repositorios Privados de acuerdo con la Sección P. + +#### 3. Acceso +El personal de GitHub solo puede ingresar a los Repositorios Privados del Cliente en las situaciones descritas en nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#repository-contents). + +El Cliente puede decidir habilitar más acceso a sus Repositorios privados. Por ejemplo, el Cliente puede habilitar varios servicios o funciones de GitHub que requieren derechos adicionales sobre el Contenido del Cliente en los Repositorios privados. Estos derechos pueden variar según el servicio o la función, pero GitHub continuará considerando el Contenido del Cliente en los Repositorios privados del Cliente como Información confidencial. GitHub proporcionará una explicación sobre esos derechos si esos servicios o funciones requieren más derechos de los que necesita para proporcionar el Servicio. + +Además, podemos estar [obligados por ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de tus repositorios privados. + +GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad. + +### F. Notificación de propiedad intelectual + +#### 1. Derechos de GitHub sobre el Contenido +La apariencia del Servicio es propiedad intelectual de © GitHub, Inc. Todos los derechos reservados. El Cliente no puede duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. + +#### 2. Nombres comerciales y logos de GitHub +Si el Cliente desea usar los nombres comerciales de GitHub, debe seguir todas las pautas de nombres comerciales de GitHub, incluyendo las que se encuentran en la [página de logos de GitHub](https://github.com/logos). + +#### 3. Licencia a políticas de GitHub +Este Acuerdo está licenciado bajo la [licencia Creative Commons Cero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). + +#### 4. Violación de la propiedad intelectual y la política de DMCA +Si el cliente es un propietario de derechos de autor y considera que el Contenido del servicio viola los derechos de autor del Cliente, el cliente puede notificar a GitHub de acuerdo con la[Ley de Derechos de Autor del Milenio Digital](/articles/dmca-takedown-policy/) de GiHub a través del [formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. + +#### 5. Derechos de propiedad intelectual reservados +Como fue acordado entre las Partes, GitHub posee todos los derechos, títulos e intereses, incluidos todos los derechos de propiedad intelectual, sobre los Productos y para ellos. GitHub se reserva todos los derechos sobre los Productos y para ellos no otorgados expresamente al Cliente conforme a lo dispuesto en el presente Acuerdo. + +### G. Términos adicionales de los productos de GitHub +Algunas características de servicio pueden estar sujetas a términos adicionales como se establece en los [términos de producto adicionales de GitHub](/github/site-policy/github-additional-product-terms). Al acceder o utilizar estas características, el cliente acepta las condiciones de producto adicionales de GitHub. + +### H. Licencias de suscripción +Las Licencias de suscripción se otorgan por Usuario y la misma Licencia de suscripción no puede ser utilizada por múltiples Usuarios. El Cliente puede reasignar una Licencia de suscripción a un nuevo Usuario solo después de noventa (90) días desde la última reasignación de esa misma Licencia de suscripción, excepto que la reasignación se deba a (i) la pérdida o la falla permanente del hardware, (ii) la terminación del empleo o el contrato del Usuario, o (iii) la readjudicación temporal de las Licencias de Suscripción para cubrir una ausencia del Usuario. Cuando el Cliente reasigna una Licencia de suscripción de un Usuario a otro, el Cliente debe bloquear el acceso del Usuario anterior a la Licencia de suscripción y a las Organizaciones del Cliente. + +### I. Afiliados +Los afiliados del cliente están autorizados a utilizar los Productos de conformidad con este Acuerdo, siempre y cuando el Cliente sea plenamente responsable de su acceso y uso de los Productos. + +### J. Pago + +#### 1. Precios; Tarifas + +**Términos de pago** Nuestro precio está disponible en [github.com/pricing](https://github.com/pricing) (a menos que las partes lo negocien de otra forma y lo indiquen en un Formulario de Pedido). El Cliente acepta pagar las Tarifas por completo, desde el inicio sin deducciones ni compensaciones de ningún tipo, en Dólares estadounidenses. estadounidenses. El cliente debe pagar las Tarifas dentro de los treinta (30) días de la fecha de la factura de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el cliente no cumple con el pago de las Cuotas a tiempo, GitHub se reserva el derecho, adicionalmente a tomar cualquier otra acción legal o equitativa, de (i) cobrar intereses sobre cantidades atrasadas con valor de 1.0% mensual o la tasa de interés más alta permitida por la ley, la que fuese menor, y cargar todos los gastos de recuperación, y (ii) terminar el Formato de Compra o SOW aplicable. El Cliente es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en conexión con el presente Acuerdo. + +**Facturación basada en el uso** Algunas características del servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en arreares, siempre y cuando para los clientes facturados, las funciones de Servicio de pago se facturan por adelantado. Consulte [Términos de producto adicionales de GitHub para obtener más detalles](/github/site-policy/github-additional-product-terms). + +#### 2. Comprar Licencias de suscripción adicionales +El cliente puede obtener Licencias de Suscripción adicionales bajo este Contrato enviando una solicitud a través del Servicio o a través de su equipo de ventas. Si el Cliente compra las Licencias de suscripción adicionales, el Cliente debe pagar por ellas las Tarifas correspondientes vigentes en ese momento, prorrateadas por el saldo de la Vigencia de suscripción aplicable. Al momento de la renovación de las Licencias de suscripción del Cliente por otro Plazo de suscripción, GitHub facturará todas las Licencias de suscripción una sola vez al año excepto que se especifique lo contrario en un Formulario de pedidos. + +#### 3. Créditos de servicios profesionales. +Si el Cliente usa Créditos de servicios profesionales para pagar por Servicios profesionales, una vez que el Cliente reciba una SOW, los Créditos de servicios profesionales aplicables se deducirán del saldo de los Créditos de servicios profesionales del Cliente. El Cliente es responsable de asegurar que su orden de compra emitida a GitHub por los Servicios profesionales refleje los precios establecidos en la SOW. Si existiera una diferencia en los precios que figuran en la SOW y los precios que figuran en la orden de compra del Cliente, prevalecerán los precios de la SOW. Las Partes acuerdan que las SOW pagaderas a través de Créditos de servicios profesionales no necesitan firmarse por ninguna de las Partes para ser válidas y ejecutables. Todos los Créditos de servicios profesionales deben utilizarse durante el tiempo establecido en el Formulario de pedidos o se cancelarán automáticamente y serán no reembolsables. El Cliente no puede aplicar los Créditos de servicios profesionales en viajes y gastos de alojamiento, los cuales se deben facturar por separado. + +#### 4. Autorización +El cliente autoriza a GitHub a hacer un cargo en la tarjeta de crédito en el archivo, a la cuenta PayPal, u otros métodos de pago aprobados para Tarifas. + +### K. Término; Terminación; Suspensión + +#### 1. Plazo +Este Contrato comienza en la Fecha de entrada en Vigencia y continuará en vigor hasta que una Parte lo rescinda de acuerdo con esta sección K. + +#### 2. Terminación por Conveniencia; Cancelación de Cuenta +Cualquiera de las Partes puede cancelar un Formulario de Pedido (si aplica) o este Contrato, sin causa, al menos treinta (30) días antes de la notificación por escrito. Si el Cliente elige poner fin a un Formulario de pedidos o a un Acuerdo, es responsabilidad del Cliente cancelar debidamente su cuenta con GitHub ingresando en Configuraciones en la barra de navegación global en la parte superior de la pantalla. GitHub no puede cancelar cuentas en respuesta a un correo electrónico o a una solicitud telefónica. + +#### 3. Terminación por Incumplimiento sustancial +Cada Parte podrá terminar el presente Acuerdo inmediatamente al recibir la notificación de que la otra Parte haya incumplido sustancialmente con una obligación bajo este Acuerdo y no pueda subsanar dicho incumplimiento dentro de los treinta (30) días posteriores desde la fecha en la que se recibe dicha notificación. GitHub puede rescindir este Contrato si la Cuenta del Cliente se suspendió por más de 90 días. + +#### 4. Efecto de la terminación +- _Formularios de Pedido._ Una vez rescindido el presente Contrato, el Cliente no podrá ejecutar Formularios de Pedido adicionales (si aplica); sin embargo, este Acuerdo permanecerá en vigor para el resto de los Formularios de Pedido activos. Cuando un Formulario de Pedido termina o expira, en cuanto a ese Formulario de Pedido: (i) el Plazo terminará inmediatamente; (ii) cualquier Licencia de Suscripción en el Formulario de Pedido cancelará automáticamente y el Cliente ya no tendrá derecho a usar el Servicio; (iii) si se adeuda alguna Tarifa antes de la terminación, el Cliente debe abonar dichas tasas inmediatamente; (iv) cada Parte devolverá rápidamente (o, si la otra parte lo solicita, destruirá) toda la Información Confidencial perteneciente al otro en la medida permitida por el Servicio. No obstante lo anterior, GitHub hará un esfuerzo razonable para proporcionar al Cliente una copia de sus Contenidos de cuenta legítimos y no infractores cuando lo solicite; siempre que el Cliente haga esta solicitud dentro de los 90 días siguientes a la terminación, suspensión o descenso de categoría. + +- GitHub conservará y utilizará la información del Cliente según sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir los acuerdos de GitHub, pero abandonando los requisitos legales, GitHub eliminará el perfil completo del Cliente y el Contenido de sus repositorios dentro de los 90 días posteriores a la terminación o caducidad (aunque cierta información puede permanecer en copias de seguridad cifradas). Esta información no se puede recuperar una vez que la cuenta del Clientse se cancele. + +- GitHub no eliminará el Contenido que el Cliente ha contribuido a los repositorios de Usuarios Externos o que los Usuarios Externos han bifurcado. + +#### 5. Suspensión +GitHub tiene el derecho de suspender el acceso a todo o cualquier parte del Servicio, incluyendo la eliminación de Contenido, en cualquier momento por violación de este Contrato o para proteger la integridad, operabilidad y seguridad del Servicio, efectiva inmediatamente, con o sin previo aviso. A menos que esté prohibido por ley o proceso legal o para prevenir daños inminentes al Servicio o a cualquier tercero, GitHub normalmente proporciona un aviso en forma de banner o correo electrónico en o antes de dicha suspensión. GitHub personalizará, a su criterio y de buena fe, cualquier suspensión que sea necesaria para preservar la integridad, operatividad y seguridad del Servicio. + +#### 6. Continuidad +Todas las disposiciones de este Acuerdo que por su naturaleza deberían sobrevivir a la terminación sobrevivirán a la terminación, incluyendo, sin limitación, las provisiones de propiedad, las exenciones de garantía, indemnización y limitaciones de responsabilidad. + +### L. Comunicaciones con GitHub + +#### 1. Comunicación electrónica requerida +Con fines contractuales, el Cliente (1) consiente recibir comunicaciones en un formulario electrónico a través de la dirección de correo electrónico que se envío o a través del Servicio; y (2) acepta que todos los Términos de Servicio, acuerdos, avisos, revelaciones y otras comunicaciones que GitHub proporciona electrónicamente cumple con cualquier requerimiento legal que estas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta los derechos no renunciables del Cliente. + +#### 2. El aviso legal para GitHub debe ser por escrito +Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería del soporte de GitHub no constituirán un aviso legal a GitHub en ninguna situación en la que el contrato o cualquier ley o regulación requieran aviso a GitHub. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). + +### M. Garantía limitada; descargo de responsabilidad + +_Garantía General_. Cada una de las Partes manifiesta y garantiza a la otra Parte que tiene el poder legal y la autoridad para celebrar el presente Acuerdo, y que este Acuerdo y todos los Formularios de pedidos y SOW son concertados por un empleado o agente de dicha Parte con toda la autoridad necesaria para vincular a la Parte mencionada con los términos y condiciones del presente Acuerdo. + +_Garantía de Servicios Profesionales._ A menos que se exponga lo contrario en una SOW, GitHub garantiza que todos los Servicios Profesionales realizados bajo este Contrato se realizarán de forma profesional y con mano de obra por personal debidamente cualificada. La única obligación de GitHub, y el único remedio del cliente, por un incumplimiento de esta garantía serán, a opción y coste de GitHub: (i) realizar nueva y rápidamente los Servicios Profesionales que no cumplan con esta garantía o (ii) si la infracción no se puede remediar, rescindir la SOW y reembolsar las tarifas prepagadas no utilizadas. + +_Descargo de responsabilidad del Servicio._ GitHub proporciona el Servicio **"TAL CUAL"** y **"SEGÚN ESTÉ DISPONIBLE"** sin garantía de ningún tipo. Sin perjuicio de esto, GitHub renuncia expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto del Servicio incluidas entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento. GitHub no garantiza que los Servicios cumplan con los requisitos del Cliente; que los Servicios no se interrumpan y sean oportunos, seguros o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. GitHub no será responsable por cualquier riesgo de pérdida que resulte de la descarga del Cliente y/o el uso de archivos, información, Contenido u otro material obtenido del Servicio. + +_(iii) Descargo de Responsabilidad de Vista previa Beta._ El Cliente puede elegir utilizar la Vista previa Beta a su exclusivo criterio. Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Las Vistas previas Beta pueden no ser tan confiables o no estar disponibles como el Servicio. Las Vistas previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que el Servicio se encuentra sujeto. GitHub no tendrá ninguna responsabilidad que surja de las Vistas previas Beta o que esté relacionado con ellas. **Customer uses Beta Previews at its own risk.** + +### N. Limitaciones de responsabilidad +**_Daños indirectos_ En la medida máxima permitida por la ley aplicable, en ningún caso será responsable ante la otra parte o ante terceros por ningún daño indirecto, especial, incidental, punitivo o consecuente (incluyendo pérdidas de ganancias, ingresos, o datos) o por el coste de obtener productos sustitutos que surjan de o en conexión con este Acuerdo, sea cual fuere la causa, si dicha responsabilidad surge de cualquier reclamación basada en el contrato, garantía, agravio (incluyendo negligencia), responsabilidad estricta o de otra forma y si una parte ha sido advertida o no de la posibilidad de dichos daños.** + +**_Restricción de la responsabilidad total._ En la medida máxima permitida por la ley aplicable, en ningún caso la responsabilidad acumulada total de ninguna de las partes en virtud de este Acuerdo por todas las causas de acción y todas las teorías de responsabilidad excederán las Tarifas que el Cliente ha pagado a GitHub durante los 12 meses anteriores a la reclamación que da lugar a dicha responsabilidad. Para los productos y los servicios (incluido el uso de los Productos) que se brindan gratis, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰5000,00. Para las Vistas previas Beta, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰500,00.** + +**_Exclusiones._ Las exclusiones y limitaciones expuestas en esta Sección N no se aplicarán a la responsabilidad derivada de (1) la violación por parte de una Parte de sus obligaciones de confidencialidad en la Sección P (excepto toda responsabilidad relacionada con el Contenido (excluyendo el contenido de GitHub), que permanecerán sujetas a las limitaciones y exclusiones anteriores) o (2) las obligaciones de defensa de una Parte en la Sección O.** + +### O. Defensa de demandas; Liberación + +Las Partes se defenderán mutuamente contra las demandas de terceros, hasta el punto que se establece en la presente Sección O y pagarán la cantidad correspondiente de cualquier sentencia firme adversa resultante o convenio aprobado, solamente si se notifica de inmediato a la Parte demandada por escrito sobre la reclamación y tiene el derecho de controlar la defensa y cualquiera de sus convenios. La Parte defendida debe proveer a la Parte demandada toda la asistencia, la información y la autoridad que se solicita. La Parte demandada reembolsará a la otra Parte por los gastos de bolsillo razonables en que incurra al proveer asistencia y no resolverá ni hará ninguna admisión con respecto a un reclamo de terceros sin previo consentimiento escrito de la otra Parte, sin que sea indebidamente demorado o retenido. La presente Sección O describe los únicos recursos de las Partes y la responsabilidad total para dichas demandas. + +#### 1. Por GitHub +GitHub defenderá al Cliente contra cualquier demanda presentada por un tercero sin afiliación en la medida en que alegue que el uso autorizado del Servicio o el Software por parte del Cliente infringe un derecho de propiedad, una patente o un nombre comercial, o que malversa un secreto comercial de un tercero sin afiliación. Si GitHub no puede resolver alguna de dichas demandas en términos comercialmente razonables, puede, según su criterio: (a) modificar, reparar o reemplazar el Servicio (si corresponde); o (b) poner fin a la suscripción del Cliente y reembolsar cualquier tarifa de suscripción pagada anticipadamente sin usar. GitHub no tendrá ninguna obligación conforme a lo dispuesto en la presente Sección O.1 por cualquier reclamación que surja de las siguientes situaciones: i) la modificación del Servicio; o la combinación, la operación o el uso del Servicio con equipos, dispositivos, software, sistemas o datos que no sean los expresamente autorizados por este Acuerdo (incluyendo la Documentación); (ii) el incumplimiento por parte del Cliente de dejar de usar el Servicio después de recibir la correspondiente notificación; (iii) las obligaciones del Cliente según lo dispuesto por la Sección O.2; (iv) los productos o servicios (incluyendo el uso del Servicio) que GitHub proporciona en forma gratuita; o (v) el acceso o uso de las Vistas previas Beta. Para los fines de la obligación de GitHub conforme a lo dispuesto en la presente Sección O.1,. el Servicio incluye componentes de código abierto que GitHub ha incorporado al mismo. + +#### 2. Por el Cliente +El cliente defenderá a GitHub contra cualquier demanda presentada por un tercero no afiliado que surja de: (i) el Contenido del Cliente que carga al Servicio; (ii) la violación por parte del Cliente de este Contrato, incluyendo la violación de la confidencialidad o violación de la Sección C; o (ii) cualquier equipo de marca de terceros, dispositivos, software, sistemas o datos que el Cliente combine, opere o utilice con el Servicio. + +#### 3. Disputas con otros usuarios +Si el Cliente tiene una disputa con uno o más Usuarios, el Cliente libera a GitHub de todos los reclamos, demandas y dañoss (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o que estén relacionados de alguna forma con dichas disputas. + +### P. Confidencialidad +Ninguna de las Partes utilizará la Información confidencial de la otra Parte, excepto de acuerdo con lo permitido en el presente Acuerdo. Cada una de las Partes acepta mantener de forma confidencial y proteger la Información confidencial de la otra Parte utilizando al menos el mismo grado de cuidado con el que protege la información propia de la misma naturaleza, pero en cualquier caso al menos a niveles razonables de cuidado. Cada una de las Partes acepta tomar todas las precauciones razonables para evitar cualquier divulgación no autorizada de la Información confidencial de la otra Parte, incluyendo, entre otras, las divulgaciones de dicha Información confidencial solamente a sus Representantes, quienes (i) necesiten conocer dicha información, (ii) sean partes de acuerdos lo suficientemente adecuados como para cumplir con la presente Sección P y (iii) se encuentran informados sobre las restricciones del uso y la divulgación establecidas en la presente Sección P. Cada una de las Partes es responsable de todos los actos y omisiones de sus Representantes. Las obligaciones mencionadas no restringirán que ninguna de las Partes divulgue la Información Confidencial de la otra Parte en cumplimiento con una solicitud o exigencia de un juzgado, de una agencia administrativa o de otro organismo gubernamental, _siempre y cuando_ la Parte obligada a hacer dicha divulgación dé una notificación razonable a la otra Parte para habilitar a dicha Parte a objetar la orden o exigencia, excepto que la notificación esté prohibida por ley. Las restricciones establecidas en la presente Sección P continuarán en vigencia después de la terminación o caducidad del presente Acuerdo. + +### Q. Servicios profesionales +Al momento de la solicitud de Servicios profesionales por parte del Cliente, GitHub proporcionará una SOW detallando tales Servicios profesionales. GitHub realizará los Servicios profesionales que se describen en cada SOW. GitHub controlará la forma y los medios utilizados para llevar a cabo los Servicios profesionales y se reserva el derecho de determinar el personal asignado. GitHub puede utilizar a terceros para realizar los Servicios profesionales, siempre y cuando GitHub siga teniendo responsabilidad por sus actos y omisiones. El Cliente reconoce y acepta que GitHub conserva todos los derechos, títulos e intereses sobre cualquier cosa que se usa o se desarrolla en conexión con los Servicios profesionales, incluido el software, las herramientas, las especificaciones, las ideas, los conceptos, las invenciones, los procesos, las técnicas y las habilidades. En la medida en que GitHub entregue cualquier cosa al Cliente mientras realiza los Servicios Profesionales, GitHub otorga al Cliente una licencia no exclusiva, intransferible en todo el mundo, exenta de regalías, de plazo limitado para usar dichos entregables durante el término de este Contrato, únicamente en conjunción con el uso del Servicio por parte del Cliente. + +### R. Cambios al servicio o a los términos +GitHub se reserva el derecho, a su exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizará este Acuerdo en el caso en que ocurran dichas modificaciones. GitHub notificará al cliente sobre los cambios materiales al presente acuerdo, como aumentos de precios, al menos 30 días antes de que el cambio entre en vigencia al publicar un aviso en el servicio o enviar un correo electrónico a la dirección principal de correo electrónico especificada en tu cuenta de GitHub. El uso continuo del Servicio por parte del cliente después de dichos 30 días constituye el acuerdo a las revisiones del presente Acuerdo. Para modificaciones no sustanciales, el uso continuo del Servicio por parte del Cliente representa la aceptación de nuestras revisiones sobre el presente Acuerdo. El Cliente puede visualizar todas las modificaciones al presente Acuerdo en nuestro repositorio [Site Policy](https://github.com/github/site-policy). + +GitHub cambia el Servicio mediante Actualizaciones y adición de nuevas características. Sin perjuicio de lo anterior, GitHub se reserva el derecho de modificar o interrumpir en cualquier momento temporal o permanentemente el Servicio (o cualquier parte del mismo) con o sin previo aviso. + +### S. Asistencia +GitHub proporcionará Soporte técnico estándar para el Servicios sin ningún cargo adicional veinticuatro (24) horas al día, cinco (5) días a la semana, excluyendo los fines de semana y los días feriados nacionales de los Estados Unidos. holidays. El Soporte estándar solo se ofrece por medio de tickets basados en la web a través del Soporte de GitHub y las solicitudes de Soporte deben ser iniciadas por un Usuario con el que el equipo de Soporte de GitHub pueda interactuar. GitHub puede proporcionar Soporte premium (sujeto a los términos [de GitHub Premium para Enterprise Cloud](/articles/about-github-premium-support)) o Soporte técnico dedicado para el Servicio en el nivel de Soporte, Tarifas y Términos de Suscripción especificados en un Formulario de Pedido o SOW. + +### T. Varios + +#### 1. Legislación aplicable +Si la sede principal del cliente se encuentra en el Continente Americano, el presente Acuerdo se regirá por las leyes del estado de California y se interpretará de acuerdo a ellas sin dar efecto a los principios de conflicto de leyes, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes federales o estatales ubicadas en el Distrito Norte de California, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Si la sede principal del Cliente se encuentra fuera de América, el presente Acuerdo se regirá por las leyes de Irlanda, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes ubicadas en Dublín, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Las partes acuerdan expresamente que no se aplicarán a este Acuerdo la Convención de las Naciones Unidas sobre Contratos de Compraventa Internacional de Bienes y la Ley Uniforme de Transacciones Electrónicas. Sin perjuicio de cualquier disposición contraria anterior, GitHub puede presentar una reclamación para obtener una compensación equitativa en cualquier corte de jurisdicción competente. + +#### 2. Comentarios +El Cliente puede proporcionar Retroalimentación a GitHub con respecto a los Productos. La retroalimentación es voluntaria y no es Información Confidencial del Cliente, incluso si se designa como tal. GitHub puede ejercer y explotar plenamente dicha Retroalimentación con el propósito de (i) mejorar la operación, funcionalidad y uso de las ofertas de productos existentes y futuras de GitHub; y (ii) publicación de estadísticas agregadas sobre la calidad de los Productos, siempre que no se utilicen datos en ninguna de estas publicaciones para identificar específicamente al Cliente, sus empleados o el código de software propietario del Cliente. + +#### 3. Intransferible +Ninguna de las Partes puede asignar o de otro modo transferir el presente Acuerdo, ni total ni parcialmente, sin previo consentimiento escrito de la otra Parte, dicho consentimiento no será retenido injustificadamente y cualquier intento de hacerlo será nulo y sin efecto, salvo que GitHub pueda asignar el presente Acuerdo en su totalidad, previa notificación a la otra parte pero sin el consentimiento de la otra Parte, en conexión con una fusión, adquisición, reorganización corporativa o venta de todos o casi todos los negocios o activos de la parte que asigna. + +#### 4. Cláusula de excención +Se puede renunciar a las obligaciones de una de las Partes según lo dispuesto en el presente Acuerdo solamente por escrito con la firma de un representante autorizado de la otra Parte. Ninguna demora o falta de una de las Partes en relación a este Acuerdo en el ejercicio de algún derecho según este documento obrará como renuncia a dicho derecho, y el ejercicio único o parcial de estos derechos no imposibilitará otro ejercicio al respecto o el ejercicio de cualquier derecho según este documento por ley o normas de equidad. + +#### 5. Cláusula de separabilidad +Si una corte de jurisdicción competente considera que alguna disposición del presente Acuerdo es ilegal, nula o inaplicable, las Partes modificarán o reformarán el presente Acuerdo para darle el mayor efecto posible a esa disposición. Cualquier disposición que no se pueda modificar o reformar de esta forma se considerará eliminada y las provisiones restantes del presente Acuerdo continuarán en pleno vigor y efecto. + +#### 6. Enmiendas; Contrato Completo; Orden de Precedencia +Este Acuerdo solo se puede modificar por una enmienda por escrito firmada por un representante autorizado de GitHub, o por GitHub publicando una versión revisada de acuerdo con la Sección T. Este Acuerdo representa el acuerdo completo y exclusivo entre las Partes. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre las Partes relacionadas con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. En el caso en que exista algún conflicto entre los términos del presente Acuerdo y cualquier Formulario de pedidos o SOW, los términos del Formulario de pedidos o SOW prevalecerán solamente con respecto a ese Formulario de pedidos o SOW. + +#### 7. Publicidad +Si el cliente muestra públicamente el nombre de su empresa u organización en su cuenta o si de otro modo muestra públicamente sus marcas o logotipos en su página de perfil, el Cliente permite a GitHub utilizar el nombre de su empresa u organización para identificar al Cliente como un cliente de GitHub en materiales promocionales. El cliente puede revocar este permiso ocultando el nombre de su empresa u organización de la exhibición pública y notificando a GitHub por escrito para dejar de usar el nombre de su organización en materiales promocionales. Sin embargo, GitHub no tendrá ninguna obligación de eliminar o recuperar ningún uso o distribución previa de los materiales promocionales. + +#### 8. Fuerza mayor +GitHub será excusado de la responsabilidad hasta el punto en que sea incapaz de ejecutar cualquier obligación conforme a lo dispuesto en el presente Acuerdo debido a causas extraordinarias más allá de su control razonable, incluidos los hechos fortuitos, los desastres naturales, las huelgas, los disturbios, los bloqueos, los actos de guerra, las epidemias, o las fallas eléctricas, en las telecomunicaciones o en las redes. + +#### 9. Contratistas independientes +Cada una de las Partes es un contratista independiente con respecto al objeto del presente Acuerdo. Nada de lo dispuesto en el presente Acuerdo será considerado o interpretado de forma tal que dé lugar a la creación de una asociación legal, sociedad, empresa mixta, empleo, agencia, fiduciaria u otra relación similar entre las Partes, y ninguna de las Partes puede vincular a la otra por contrato. + +#### 10. Preguntas +¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://github.com/contact/). diff --git a/translations/es-ES/content/github/site-policy/github-deceased-user-policy.md b/translations/es-ES/content/github/site-policy/github-deceased-user-policy.md new file mode 100644 index 0000000000000..721d52603b4d9 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-deceased-user-policy.md @@ -0,0 +1,21 @@ +--- +title: Política de Usuario Finado de Github +versions: + free-pro-team: '*' +--- + +En caso de que fallezca un usuario de GitHub, podemos trabajar con un individuo autorizado para determinar qué sucederá con el contenido de la cuenta. + +Si eres un familiar cercano, un [sucesor pre-designado](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories), u otro individuo autorizado (que podría incluir a colaboradores o socios de negocios) de un usuario que a fallecido y te gustaría hacer una solicitud con respecto a la cuenta, puedes contactarnos en https://support.github.com/contact. Por favor, porporciona a siguiente información en tu mensaje: + +- Nombre +- Información de Contacto +- Nombre del cuentahabiente finado +- Nombre de usuario de GitHub del cuentahabiente finado +- Tu parentezco con el cuentahabiente finado (por favor incluye si se te ha designado como el sucesor de la cuenta en GitHub.com) +- Si se te designó como sucesor de cuenta, proporciona el nombre de usuario de tu cuenta de GitHub +- La acción que buscas (por ejemplo, transferir repositorios públicos, cancelar la facturación en una cuenta) + +Una vez que hayamos recibido tu solicitud, podremos dar seguimiento con otra solicitud de información adicional, tal como la copia de tu identificación con fotografía, copia del certificado de defunción, y la documentación que confirme que estás autorizado para actuar con relación a la cuenta del usuario finado, para verificar que estamos autorizados adecuadamente para procesar tu solicitud. + +Por favor, nota que la información que proporciones en tu solicitud se recabará de acuerdo con nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement), y retendremos la información únicamente de acuerdo con lo necesario para cumplir con nuestras obligaciones legales y resolver disputas. diff --git a/translations/es-ES/content/github/site-policy/github-event-code-of-conduct.md b/translations/es-ES/content/github/site-policy/github-event-code-of-conduct.md new file mode 100644 index 0000000000000..f8b583157a482 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-event-code-of-conduct.md @@ -0,0 +1,49 @@ +--- +title: Código de conducta del evento de GitHub +redirect_from: + - /articles/github-event-code-of-conduct +versions: + free-pro-team: '*' +--- + +Los eventos de GitHub son eventos comunitarios destinados a la creación de redes y la colaboración en la comunidad tecnológica. + +Valoramos la participación de cada miembro y deseamos que todos los asistentes tengan una experiencia agradable y satisfactoria. En consecuencia, se espera que todos los asistentes muestren respeto y cortesía a otros asistentes durante todos los eventos alojados en el espacio de GitHub. + +Para dejar en claro lo que se espera, todos los asistentes, oradores, expositores, organizadores y voluntarios en cualquier evento en el espacio de GitHub están obligados a cumplir con el siguiente código de conducta. Los organizadores aplicarán este código a lo largo de todo el evento. + +### Código de conducta + +GitHub se dedica a brindar una experiencia de evento positiva y sin acoso para todo el mundo, independientemente de su edad, género, identidad y expresión de género, orientación sexual, discapacidad, apariencia personal, complexión, etnia, raza, religión, nacionalidad o nivel de experiencia. No toleramos el acoso a los participantes del evento en ninguna forma, ni toleramos ningún comportamiento que razonablemente conduzca a que otro participante del evento se sienta en peligto, inseguro o asustado por su bienestar físico o emocional. Todas las comunicaciones deben ser adecuadas para un público profesional que incluya personas de muchos orígenes diferentes. + +Algunos ejemplos de comportamientos alentados que contribuyen a un entorno positivo incluyen los siguientes: + +* Uso de un lenguaje acogedor e inclusivo +* Ser respetuoso desde diferentes puntos de vista y experiencias +* Aceptar con agradecimiento las críticas constructivas +* Centrarse en lo que es mejor para todos en el evento +* Mostrar empatía hacia otros participantes + +Un comportamiento inaceptable incluye: + +* El uso de lenguaje o imágenes sexualizados o el contacto físico inapropiado, la atención sexual o los acercamientos +* Trolleo, comentarios insultantes o despectivos, ataques personales o políticos, o alteración sostenida de las conversaciones u otras situaciones +* Intimidación deliberada, acecho, seguimiento o acoso con fotografías o grabaciones +* Acoso de cualquier tipo, incluso de una manera graciosa o irónica +* Otras conductas que razonablemente podrían considerarse inapropiadas en un entorno profesional + +Sé amable con los demás. No insultes ni desanimes a otros asistentes. Comportarte profesionalmente. Recuerda que el acoso y las bromas sexistas, racistas o excluyentes no son adecuadas en este evento. + +Cada huésped del evento es totalmente responsable de sus propias acciones. + +Gracias por ayudar a hacer de este un espacio acogedor y agradable para todos. + +#### Informe de un incidente + +Si estás siendo hostigado, notas que alguien más está siendo acosado, o tienes alguna otra inquietud, comunícate con el organizador por correo electrónico (events@github.com) o por teléfono/texto (+ 1 415 842 2837), o habla con otro empleado de GitHub o un oficial de seguridad. + +GitHubbers estará encantado de ayudar a los participantes a ponerse en contacto con la seguridad o la aplicación de la ley local, acompañar a seguridad o de otro modo ayudar a aquellos que experimentan acoso a sentirse seguros durante la conferencia. Valoramostu asistencia. + +### Crédito + +Algunas partes de este código de conducta se basan en el [ejemplo de política anti-acoso](https://geekfeminism.wikia.org/wiki/Conference_anti-harassment/Policy) de Geek Feminism wiki, creado por la iniciativa Ada y otros voluntarios, bajo una licencia Creative Commons Zero. diff --git a/translations/es-ES/content/github/site-policy/github-event-terms.md b/translations/es-ES/content/github/site-policy/github-event-terms.md new file mode 100644 index 0000000000000..169fb4dd4d64f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-event-terms.md @@ -0,0 +1,56 @@ +--- +title: Términos del evento de GitHub +redirect_from: + - /articles/github-event-terms +versions: + free-pro-team: '*' +--- + +Al confirmar su asistencia o asistiendo a un evento de GitHub, incluyendo cualquiera de los eventos o actividades organizadas por GitHub en asociación con el evento de GitHub (en conjunto, el "Evento"), señalas que has leído, comprendes y aceptas los siguientes términos y condiciones del evento. + +### 1. Requisitos básicos para asistir, incluyendo el [Código de conducta del evento](/articles/github-event-code-of-conduct) + +Para participar en el Evento afirmas que: + +- tienes el poder y la autoridad necesarios para participar en los presentes términos del evento + +- has leído y comprendido estos términos del evento, así como los [términos de servicio de GitHub.com ](/articles/github-terms-of-service/) + +- aceptas regirte por el [Código de conducta del evento](/articles/github-event-code-of-conduct), que busca brindar una experiencia libre de acoso para todos + +- si se sirve alcohol en un evento de GitHub, afirmas que tienes al menos 21 años de edad, o de cualquier otra manera eres mayor de edad legal de consumo en tu jurisdicción. + +Se espera que los participantes detengan cualquier acoso u otro comportamiento prohibido para cumplir de inmediato. Si un participante se involucra en un comportamiento que viola el [Código de Conducta del Evento](/articles/github-event-code-of-conduct) o estos términos, los organizadores del evento pueden tomar cualquier acción que consideren adecuada, incluyendo la advertencia del infractor o la expulsión del evento o la conferencia sin reembolso. + +### 2. Fotos + +GitHub o sus socios en ocasiones toman fotos y videos en eventos de GitHub. Al participar o asistir al evento, aceptas que puedas aparecer en algunas de estas fotos y vídeos y autorizas el uso de los mismos por parte de GitHub. Por otro lado, si llevas fotos o vídeos de los asistentes en el evento y nos los proporcionas, nos autorizas a utilizarlos de la misma manera y representamos que los asistentes que aparecen en tus fotos y vídeos también han dado su consentimiento para dicho uso. + +### 3. Riesgo, responsabilidad e indemnización + +#### Asunción del riesgo +A pesar de que intentamos crear un entorno seguro en el evento, suceden accidentes u otras cosas malas, incluso para las personas buenas. Te pedimos que hagas tu parte para ayudar a limitar la posibilidad de que puedas lesionarte en el evento. + +Aceptas considerar detenidamente los riesgos inherentes a cualquier actividad en la que elijas participar y tomar las precauciones razonables antes de elegir asistir a un evento de GitHub o participar en él. Por ejemplo, deberías asegurarte de estar en buena salud física antes de participar en cualquier actividad física en un evento de GitHub y siempre deberías beber de manera responsable teniendo en cuenta los riesgos asociados con conducir ebrio y participar en actividades mientras se deteriora tu juicio. Siempre es bueno recordar que otros asistentes al evento pueden ser menos responsables que tú y pueden crear un riesgo adicional para ti a pesar de sus mejores intenciones. + +En resumen, comprendes que tu asistencia y participación en cualquier evento de GitHub es voluntaria y aceptas asumir la responsabilidad de cualquier lesión resultante en la máxima medida permitida por la ley aplicable. + +De la misma forma, aceptas que GitHub no es responsable de ninguna lesión o accidente que puedas sostener en cualquier evento que GitHub no organice o controle. + +#### Liberación de responsabilidad +Tú (por ti mismo, tus herederos, representantes personales o cesionarios, y cualquier otra persona que pueda hacer un reclamo en tu nombre) por la presente se liberan, renuncian, descargan y hacen el pacto de no demandar a GitHub y sus respectivas empresas matrices, subsidiarias, afiliadas, funcionarios, directores, socios, accionistas, miembros, agentes, empleados, vendedores, patrocinadores y voluntarios de todas las reclamaciones, demandas, causas de acción, daños, pérdidas o gastos (incluyendo los costos judiciales y los honorarios razonables de abogados) que puedan surgir, resultar o relacionarse de alguna manera con tu asistencia en el evento o cualquier evento relacionado, excepto, por supuesto, por cualquier negligencia grave o mala conducta intencional de nuestra parte. + +#### Indemnización +De la misma forma, aceptas indemnizar y eximir de toda responsabilidad a GitHub, sus matrices, subsidiarias, afiliados, funcionarios, directores, empleados, agentes y representantes, incluyendo los costos, pasivos y honorarios legales, de cualquier reclamación o demanda hecha por cualquier tercero por causa, que esté relacionada o en conexión con tu asistencia o conducta en el evento o cualquier evento relacionado. + +### 4. Termination + +Si bien esperamos que no lo haga, GitHub puede prohibir tu asistencia a cualquier evento de GitHub en cualquier momento si no cumples con los presentes términos del evento y el [Código de conducta del evento](/articles/github-event-code-of-conduct), los[términos de servicio de GitHub.com](/articles/github-terms-of-service/), o por cualquier motivo o sin motivo, sin previo aviso ni responsabilidad de ningún tipo. La sección 3 (riesgo, responsabilidad e indemnización) continuará aplicándose después de cualquier terminación. + +### 5. Elección de la ley y lugar de residencia + +La ley de California regirá estos términos del evento, así como cualquier reclamación, causa de acción o disputa que pueda surgir entre tú y GitHub (una "reclamación"), sin tener en cuenta las disposiciones de conflicto de leyes. PARA CUALQUIER RECLAMACIÓN PRESENTADA POR CUALQUIERA DE LAS PARTES, ACEPTAS SOMETERTE Y DAR TU CONSENTIMIENTO A LA JURISDICCIÓN PERSONAL Y EXCLUSIVA EN EL LUGAR EXCLUSIVO DE LOS TRIBUNALES ESTATALES Y FEDERALES UBICADOS DENTRO DEL CONDADO DE SAN FRANCISCO, CALIFORNIA. + +### 6. Términos varios + +Aceptas que no te representarás a ti mismo como empleado, representante o agente de GitHub (a menos que, por supuesto, realmente estés contratado por GitHub). Nos reservamos el derecho a cancelar el evento o cualquier evento relacionado en cualquier momento, por cualquier motivo y sin responsabilidad o perjuicio. Cualquier falla por parte de GitHub para ejercer o hacer cumplir cualquier derecho o disposición de estos términos no constituye una renuncia a tal derecho o disposición. Si alguna disposición de estos términos se encuentra como inejecutable o inválida, esa disposición se limitará o eliminará en la medida mínima necesaria para que los términos del evento permanezcan en plena vigencia y efecto y exigibles. diff --git a/translations/es-ES/content/github/site-policy/github-gifts-and-entertainment-policy.md b/translations/es-ES/content/github/site-policy/github-gifts-and-entertainment-policy.md new file mode 100644 index 0000000000000..6d71123605a0f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-gifts-and-entertainment-policy.md @@ -0,0 +1,63 @@ +--- +title: Política de entretenimiento y obsequios de GitHub +redirect_from: + - /articles/github-gifts-and-entertainment-policy +versions: + free-pro-team: '*' +--- + +GitHub reconoce que nuestro negocio se basa en relaciones positivas y transparentes. Si bien las interacciones informales y los intercambios de regalos pueden ser parte del desarrollo de esas relaciones e incluso pueden considerarse habituales en algunos países, debemos asegurarnos de que estemos siguiendo las leyes antisoborno. Tenemos la obligación legal de comportarnos éticamente, incluyendo no usar dichas interacciones para crear una ventaja especial o influir en una transacción. + +### Políticas de empresa +Como recordatorio, nuestro Código de Ética dice: +> Nunca debes pagar, ofrecer pagar, prometer pagar, inducir, aceptar o autorizar el pago de ninguna otra cosa de valor, a ninguna persona, incluyendo a ninguna persona en una posición de poder o autoridad, por ejemplo, funcionarios del gobierno o en transacciones comerciales, con el fin de obtener o mantener negocios, o asegurar cualquier otra ventaja inapropiada para GitHub o Microsoft. Tampoco debes solicitar o aceptar sobornos, ni ningún otro pago indebido en efectivo. ... [Los empleados de GitHub] están obligados a mantener registros precisos y razonables de todas las transacciones que implican cualquier gasto hecho en nombre de GitHub, por ejemplo, al mantener los recibos y proporcionar descripciones precisas de tus gastos, o cualquier otra transacción que implique la eliminación o la transferencia de los activos de GitHub. . . Estas acciones se exigen por la ley de prácticas corruptas extranjeras de los EE. UU., la ley de soborno del Reino Unido de 2010 y las leyes antisoborno de otras jurisdicciones en las que GitHub hace negocios y que también son simplemente la manera correcta de proceder. + +El código ético de GitHub detalla ciertas situaciones, incluyendo sobre regalos, viajes y entretenimiento; facilitación de pagos; donaciones caritativas; puestos laborales y trabajar con representantes, así como la descripción de quién se considera un funcionario del gobierno. + +Nuestras Normas de Conducta prohíben: +> Sobornar a funcionarios del gobierno u otras personas para obtener una ventaja injusta y tomar sobornos de cualquier persona. + +Eso significa que no solo se debe administrar dinero en efectivo o equivalente en efectivo de ningún tipo, sino no entregar nada de valor a nadie (incluyendo los empleados públicos, funcionarios del gobierno o cualquier persona en una posición de poder o autoridad, así como personas que no estén en cualquiera de esas posiciones privilegiadas) con el fin de influir en ellos o de que cualquier persona pueda influir en GitHub. Such activity is prohibited by the U.S. Se prohíbe dicha actividad por la ley de prácticas corruptas extranjeras de los EE. UU. y las leyes antisoborno del Reino Unido, que rigen las acciones de GitHub en todo el mundo. + +### Ejemplos de regalos aceptables e inaceptables +Entonces, ¿Qué significa "de valor"? Ten en cuenta que no se aceptan regalos a funcionarios del gobierno (ok, tal vez calcomanías). Siempre debes preguntarles qué permiten y qué prohíben sus políticas. Pero si tienes dudas, por favor, consulta la ley para asegurarte. For example, many U.S. Por ejemplo, muchos legisladores estadounidenses no te permitirán llevarlos a cenar y pagar. + +En cuanto a otros clientes o clientes potenciales, ciertas cosas pueden parecer triviales pero tienen un gran valor para otra persona. Por ejemplo, si bien puede que no parezca una gran cosa para ti lograr que se contrate a la hija de tu amigo como pasante, puede ser de gran valor para ellos. Pero si no está calificada y mueves influencias para hacer que suceda, entonces no está bien. Además, si la intención es influir de manera inadecuada, cualquier cosa, por pequeña que sea, se puede considerar "de valor". + +🙅 _Aquí hay otras cosas que no son correctas:_ + +- Pasaje aéreo de primera clase para las oficinas de GitHub para sesiones de instrucción ejecutiva ✈️ + 🍾 +- Tours en bodegas 🍷 +- Recomendar al niño de un amigo para admisión a una escuela privada prestigiosa 🎓 +- Entradas a Disneyland 👸, la Copa del mundo 🥅, los Juegos Olímpicos 🏅 +- Un balón ⚽️ autografiado por un jugador famoso +- Una contribución a una organización benéfica + +🙆 _Aquí se presentan algunas cosas que en realidad están bien para los clientes o clientes potenciales:_ + +- Flores +- Pasaje aéreo de clase turista a las oficinas de GitHub para sesiones de reuniones ejecutivas ✈️ +- Boletos tipo gradas para un evento deportivo ⚾️ +- Una cena de precio razonable en la ciudad 🍽 +- Una pequeña caja de chocolates como agradecimiento de fin de año 🍫 + +Todo lo anterior se aplica a la _toma_ de sobornos también. Por lo tanto, si un proveedor o posible proveedor te envía algo "de valor", no lo aceptes o, al menos, aplica la ley antes de hacerlo. + +### Proceso +Si estás planeando brindar o aceptar un regalo informal (que no es uno de nuestros artículos promocionales como camisetas y conjunto de calcomanías), por favor asegúrate de seguir el proceso que se presenta a continuación. + +Ten en cuenta que lo que es una cantidad aceptable puede variar. Por ejemplo, gastar $50 en la cena puede considerarse mucho dinero en algunos países, pero no tanto en otros. Por lo tanto, si tienes duda, ¡Pregunta! + +1. En términos generales, para cualquier gasto que exceda de $150, necesitarás aprobación (en cada ocasion) del Jurídico, por escrito. Y para cualquier regalo que recibas que supere los $150, deberás informar de ello (en cada ocasión) a Jurídico, por escrito. (Jurídico sólo lo pondera en el tema de soborno. Es posible que aún debas verificar con Finanzas por otras razones.) + +2. Cuando envíes tu informe de gastos para el reembolso, por favor: + - Indica el destinatario y el propósito del regalo en las notas; e + - Incluye una copia de la aprobación por correo electrónico + +### Consecuencias +¿Qué sucede si no sigues la política y GitHub termina pagando a un cliente potencial y a su familia para volar en primera clase a Japón y asistir a los Juegos Olímpicos de Tokio? ¿O si le entregas con arreglo previo una maleta de euros a un funcionario del gobierno en un casillero de estación de tren? + +MULTAS y CÁRCEL. No necesariamente solo para GitHub. Puedes llegar a pasar algunos años en la cárcel y no importará si el cliente alguna vez envió una orden a GitHub después de su viaje a Japón o si el funcionario del gobierno incluso recogió la maleta de dinero en efectivo. Básicamente, no importa si realmente _hiciste_ un soborno. Sin embargo, el intento es lo que cuenta. + +### Más información +Para obtener más información y contexto sobre las reglas, el cumplimiento y las sanciones, el Departamento de Justicia de los EE. UU. [Guía de recursos para la ley de prácticas corruptas extranjeras de los EE. UU.](https://www.justice.gov/sites/default/files/criminal-fraud/legacy/2015/01/16/guide.pdf) es un excelente recurso. La ley de prácticas corruptas extranjeras es un excelente recurso. diff --git a/translations/es-ES/content/github/site-policy/github-government-takedown-policy.md b/translations/es-ES/content/github/site-policy/github-government-takedown-policy.md new file mode 100644 index 0000000000000..9f5be9c5522a3 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-government-takedown-policy.md @@ -0,0 +1,31 @@ +--- +title: Política de retiro gubernamental de GitHub +versions: + free-pro-team: '*' +--- + +#### ¿Qué es esto? +De vez en cuando, GitHub recibe solicitudes de los gobiernos para retirar contenido que se declaró ilegal en su jurisdicción local. Aunque no siempre estemos de acuerdo con esas leyes, podemos necesitar bloquear el contenido si recibimos una solicitud completa de un funcionario del gobierno para que nuestros usuarios en esa jurisdicción puedan continuar teniendo acceso a GitHub para colaborar y construir software. + +#### ¿Qué es una solicitud completa de retiro del gobierno? +Para que cuente como una solicitud completa, una solicitud o aviso debe: +- provenir de una agencia gubernamental oficial correspondiente +- identificar contenido ilegal +- especificar la fuente de ilegalidad en dicha jurisdicción (ley u orden judicial). + +#### ¿Qué ocurre cuando recibimos una solicitud de retiro completa de un gobierno? + +Cuando recibimos una notificación de una agencia gubernamental oficial correspondiente que identifique contenido ilegal y especifique la fuente de la ilegalidad, nosotros +- notificamos a los usuarios afectados del contenido específico que presuntamente viola la ley y que esta es una solicitud de retiro legal +- permitimo a los usuarios afectados apelar la decisión como parte de dicha notificación +- limitamos el alcance geográfico de la retiro cuando sea posible y lo incluimos como parte de la notificación +- publicamos la solicitud oficial que condujo al retiro en nuestro repositorio [gov-takedowns](https://github.com/github/gov-takedowns) público. + +#### ¿Por qué publicamos avisos de retiro? +Nos preocupa la censura de Internet y creemos que la transparencia a un nivel específico y actual es esencial para una buena gobernanza. Al hacer públicamente los avisos, podemos informar mejor al público sobre el contenido que se retiene de GitHub y las razones. Publicamos notificaciones de retiro para documentar su potencial de desintensificar el discurso. + +#### ¿Qué significa que publiquemos una notificación en nuestro repositorio de retiro del gobierno? +Significa que recibimos la notificación en la fecha indicada. *No* significa que el contenido es ilegal o sea incorrecto. *No* significa que el usuario identificado en la notificación haya hecho algo incorrecto. No hacemos ni implicamos ningún juicio sobre el mérito de las reclamaciones que hacen. Publicamos estas notificaciones y solicitudes sólo para propósitos informativos. + +#### Reportes de transparencia +Además de publicar notificaciones de retiro del gobierno en nuestro repositorio de retiros del gobierno, las informamos en nuestro reporte de transparencia. También rastreamos e informamos en nuestro reporte de transparencia sobre los retiros del gobierno con base en violaciones de los Términos de Servicio de GitHub. Procesamos dichas violaciones como procesaríamos una violación de los Términos de Servicio denunciada por cualquier otro. diff --git a/translations/es-ES/content/github/site-policy/github-gpl-cooperation-commitment.md b/translations/es-ES/content/github/site-policy/github-gpl-cooperation-commitment.md new file mode 100644 index 0000000000000..30d2aeec10251 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-gpl-cooperation-commitment.md @@ -0,0 +1,33 @@ +--- +title: Compromiso de Cooperación de GPL de GitHub +redirect_from: + - /articles/github-gpl-cooperation-commitment +versions: + free-pro-team: '*' +--- + +Este compromiso se refiere a las contribuciones de GitHub a Git, el kernel de Linux y otros programas bajo licencias cubiertas (desplácese hasta el final para las definiciones). + +Basamos nuestra proposición en la plantilla [](https://github.com/gplcc/gplcc/blob/master/Company/GPL%20Cooperation%20Commitment-Company-Template.md) para empresas. Consulta el [sitio del Comité de Cooperación GPL](https://gplcc.github.io/gplcc/) para conocer cómo otras empresas, individuos y proyectos pueden adoptar este compromiso. + +### Nuestro compromiso + +Antes de presentar o continuar procesando cualquier procedimiento legal o reclamación (excepto una acción defensiva) que surja de la terminación de una licencia cubierta, GitHub se compromete a extenderse a la persona o entidad (“tú”) acusada de violar la Licencia Cubierta, las siguientes disposiciones relativas a la subsanación y la reincorporación, tomado de la versión 3 de GPL. Tal y como se utiliza aquí, el término "esta Licencia" se refiere a la Licencia cubierta específica que se está cumpliendo. + +Sin embargo, si cesas toda violación de esta Licencia, entonces tu licencia de un titular de derechos de autor particular se reestablece (a) de forma proporcional, a menos y hasta que el titular de los derechos de autor explícitamente y finalmente termina tu licencia, y (b) de forma permanente, si el titular de los derechos de autor no te notifica la violación por algún medio razonable antes de los 60 días posteriores a la cesación. + +Además, tu licencia de un determinado titular de derechos de autor se reestablece permanentemente si el titular de los derechos de autor te notifica la violación por algunos medios razonables, esta es la primera vez que recibes un aviso de violación de esta Licencia (por cualquier trabajo) de ese titular de los derechos de autor y subsanas la violación antes de 30 días después de la recepción de la notificación. + +GitHub pretende que este Comité sea irrevocable, vinculante y exigible contra GitHub y asignados o sucesores de los derechos de autor de GitHub. + +GitHub puede modificar este Comité publicando una nueva edición en esta página o una ubicación posterior. + +Definiciones + +‘Licencia cubierta’ hace referencia a la Licencia Pública General GNU, versión 2 (GPLv2), la Licencia Pública General Menor GNU, versión 2. (LGPLv2.1), o la Licencia Pública General de la Biblioteca GNU, versión 2 (LGPLv2), todo publicado por la Free Software Foundation. + +‘Acción Defensiva’ significa un proceso legal o una reclamación de GitHub contra ti en respuesta a un proceso previo o reclamación iniciada por ti o tu afiliado. + +'GitHub' significa GitHub, Inc. y sus filiales. + +Este trabajo está disponible bajo una licencia interlacional Creative Commons Attribution-ShareAlike 4.0. diff --git a/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md new file mode 100644 index 0000000000000..3f509e89749fe --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md @@ -0,0 +1,48 @@ +--- +title: GitHub Insights y la protección de datos para tu organización +intro: '{% data variables.product.prodname_insights %} analiza tus datos de {% data variables.product.prodname_ghe_server %}. Estos datos podrían incluir datos personales de individuos en tu organización quienes podrían tener derecho a entender cómo se utilizan éstos.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization + - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization + - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization + - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization +versions: + free-pro-team: '*' +--- + +Para obtener más información acerca de las condiciones normativas de {% data variables.product.prodname_insights %}, consulta tu contrato de suscripción de {% data variables.product.prodname_ghe_one %}. + +Para evitar las dudas, ninguna información anterior deberá considerarse como asesoría legal proporcionada por {% data variables.product.prodname_dotcom %}. Eres responsable de asegurar tu propio análisis legal de la información aquí proporcionada y de dar cumplimiento a las leyes de protección de privacidad y datos. Dependerá de ti si quieres utilizar {% data variables.product.prodname_insights %} para procesar los datos de tus usuarios y empleados, y si lo haces, serás el único responsable para ejecutar dicho procesamiento en cumplimiento con las leyes aplicables. + +### Los roles y responsabilidades de la organización + +Cuando utilizas {% data variables.product.prodname_insights %}, tu organización es el controlador de los datos, porque ésta determina cómo, cuándo y si {% data variables.product.prodname_insights %} procesará cualquier tipo de datos personales de los individuos. Tu organización es la única responsable para garantizar que cumples con todas las leyes aplicables sobre el procesamiento de datos con {% data variables.product.prodname_insights %}. + +### Recomendaciones de privacidad de datos + +Tienes todo el control sobre las métricas, reportes, repositorios y colaboradores a incluir antes de comenzar a utilizar {% data variables.product.prodname_insights %}. Los datos que proceses con {% data variables.product.prodname_insights %} podrán descargarse únicamente de tu instalación de {% data variables.product.prodname_ghe_server %}. Considera equilibrar los riesgos con los beneficios de analizar datos personales. + +- **Desarrolla un plan claro de análisis de datos**: Debes entender claramente lo que quieres analizar, y por qué, y después considerar como puede ayudarte {% data variables.product.prodname_insights %} a encontrar estas respuestas. + +- **Considera una valoración de impacto en la protección de datos**: Si el uso de {% data variables.product.prodname_insights %} que propones involucra el procesamiento de datos personales, considera completar una valoración de impacto en la protección de datos o completar de otra forma un análisis legal del uso que pretendes tener. + +### Decidir qué datos utilizar + +- **Decide qué repositorios incluir**: Antes de comenzar un análisis en {% data variables.product.prodname_insights %}, considera qué repositorios incluirás. Los administradores pueden incluir repositorios cuando agregan organizaciones y pueden habilitar o inhabilitar los repositorios en cualquier momento. Para obtener más información sobre agregar organizaciones a {% data variables.product.prodname_insights %}, consulta la sección "[Administrar organizaciones](/insights/installing-and-configuring-github-insights/managing-organizations)". Para obtener más información sobre habilitar e inhabilitar repositorios, consulta la sección "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)". + +- **Decide las métricas y reportes a incluir**: Los administradores pueden habilitar e inhabilitar las métricas y reportes disponibles para todos los usuarios en cualquier momento. Los administradores controlan los datos de {% data variables.product.prodname_insights %} a los cuales tienen acceso los usuarios en tu instalación de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Administrar métricas y reportes disponibles](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)" + +- **Decide qué colaboradores incluir**: Los administradores pueden inhabilitar los datos de un colaborador específico para que no se procesen en las métricas y reportes. Para obtener más información acerca de administrar los datos de un colaborador, consulta la sección "[Administrar colaboradores y equipos](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)". + +### Derechos del usuario + +De acuerdo con diversas regulaciones de protección de datos, tales como la Regulación General para la Protección de Datos (GDPR, por sus siglas en inglés), los usuarios podrían tener derecho a solicitar que se les excluya del procesamiento, acceso y corrección, o de solicitar que se borre sus datos personales. Como el controlador de los datos, tu organización deberá evaluar si la solicitud de un usuario en particular es válida, y de ser adecuado, tomar las acciones para completar la solicitud. + +- **Exclusión del procesamiento**: Los usuarios tendrán el derecho de que se excluya su información personal del procesamiento. Los administradores tienen la capacidad de eliminar los datos de los contribuyentes del procesamiento en {% data variables.product.prodname_insights %}, y los reportes y métricas resultantes excluirán los datos del colaborador como consecuencia. Para obtener más información, consulta "[Administrar colaboradores y equipos](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)". + +- **Acceso**: Los usuarios podrían tener el derecho de solicitar ver qué datos personales se están procesando. Cada métrica y reporte cuenta con una descripción detallada de qué datos personales se están procesando. Para obtener más información, consulta la sección "[Métricas disponibles con {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)". Los datos sin procesar están disponibles a través de la API de {% data variables.product.prodname_enterprise %}. Tu organización es responsable por cualquier decisión para procesar datos personales y por llevar a cabo dichas solicitudes. + +- **Corrección y borrado**: Los usuarios podrían tener el derecho de rectificar o eliminar sus datos personales. Los datos utilizados en {% data variables.product.prodname_insights %} se derivan de los datos existentes que agregas o generas desde tu instalación de {% data variables.product.prodname_ghe_server %}. La corrección y borrado deberán seguir los procesos existentes de tu organización para corregir y eliminar los datos de {% data variables.product.prodname_ghe_server %}. + +- **Transparencia con respecto al procesamiento**: Cada métrica y reporte tiene una descripción detallada de los datos personales que se están procesando. Para obtener más información, consulta la sección "[Métricas disponibles con {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)". diff --git a/translations/es-ES/content/github/site-policy/github-logo-policy.md b/translations/es-ES/content/github/site-policy/github-logo-policy.md new file mode 100644 index 0000000000000..57e1e155b91ad --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-logo-policy.md @@ -0,0 +1,13 @@ +--- +title: Política de logo de GitHub +redirect_from: + - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know/ + - /articles/using-an-octocat-to-link-to-github-or-your-github-profile/ + - /articles/github-logo-policy +versions: + free-pro-team: '*' +--- + +Puede añadir {% data variables.product.prodname_dotcom %} logos a tu sitio web o aplicación de terceros en algunos escenarios. Para obtener más información y directrices específicas, consulta la[{% data variables.product.prodname_dotcom %} página de Logos y Uso](https://github.com/logos). + +También puedes usar un octocat como tu avatar personal o en tu sitio web para vincular a tu cuenta, {% data variables.product.prodname_dotcom %} pero no para tu empresa o un producto que estás construyendo. {% data variables.product.prodname_dotcom %} tiene una extensa colección de octocats en el [Octodex](https://octodex.github.com/). Para obtener más información sobre cómo usar los octocats de Octodex, consulta las [preguntas frecuentes de Octodex](https://octodex.github.com/faq/). diff --git a/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md b/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md new file mode 100644 index 0000000000000..fe973510ca6d9 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md @@ -0,0 +1,270 @@ +--- +title: GitHub Marketplace Developer Agreement +redirect_from: + - /articles/github-marketplace-developer-agreement +versions: + free-pro-team: '*' +--- + +**ESTOS TÉRMINOS Y CONDICIONES (EL "ACUERDO") REGULAN TU PARTICIPACIÓN EN EL PROGRAMA DEL MERCADO DE GITUB. AL INSCRIBIRTE PARA PARTICIPAR EN EL PROGRAMA DE MERCADO O AL HACER CLIC EN "ACEPTO" A CONTINUACIÓN, CONFIRMAS QUE ENTIENDES EL PRESENTE ACUERDO Y QUE ACEPTAS TODOS SUS TÉRMINOS Y CONDICIONES. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS.** + +Effective Date: January 1, 2021 + +### 1. DEFINICIONES + +Los términos con mayúscula inicial utilizados en el presente acuerdo y no definidos en el presente documento deberán tener el significado establecido en los términos de servicio de GitHub ubicados en [https://docs.github.com/articles/github-terms-of-service](/articles/github-terms-of-service) (los "Términos" o "ToS"). + +"Acción" significa un mecanismo que te permite implementar lógica personalizada sin tener que crear una aplicación para realizar una tarea particular con GitHub. + +"Características de la marca" se refiere a los nombres comerciales, marcas comerciales, marcas de servicio, logotipos, nombres de dominio y otras características distintivas de la marca de cada parte, respectivamente, ya que son propiedad de dicha parte (o con licencia) de vez en cuando. + +"Programador" se refiere a ti y tu eres la empresa o persona que ha creado el software y los materiales digitales para su uso en conexión con GitHub y accesibles a través del mercado. + +"Aplicación del Programador" o "Producto del Programador" significa el Software, contenido y materiales digitales creados por ti para su uso en conexión con GitHub y que son accesibles a través del mercado e incluye Acciones. + +"Usuario final" hace referencia a cualquier persona, empresa u otra entidad legal que adquiera licencias para el Producto de Programadores a través del mercado de GitHub. + +"GitHub API" se refiere a la interfaz del programa de aplicación patentada de GitHub. El acceso y el uso de la API de GitHub se rige por los ToS. + +"Mercado de GitHub" o "mercado" se refiere al sitio del mercado en línea patentado operado por GitHub, donde los productos del programador se pueden entregar a los usuarios finales. + +“Listado” hace referencia al contenido proporcionado para listar el producto del Programador en el mercado de GitHub. + +"Impuestos" se refiere a cualquier ingreso federal, estatal, local o extranjero, ingresos brutos, franquicia, estimación, mínimo alternativo, ventas, uso, transferencia, valor agregado, consumo, propiedad real o personal, retenciones u otros impuestos, de cualquier tipo, incluyendo los intereses, sanciones o adiciones a impuestos o importes adicionales con respecto a lo anterior." + +"Datos de uso" hace referencia a los datos relacionados con el mercado generados en relación con el uso del usuario final del mercado de GitHub y la licencia de los productos para Programadores, incluyendo, sin limitación a estadísticas de uso y datos de ventas agregados. Los datos de uso no incluyen y específicamente excluyen la información bancaria y de pago. + +### 2. OBJETIVO Y CONCESIÓN DE LICENCIA + +**2.1** El presente acuerdo establece los términos y condiciones de acuerdo con los cuales el Programador puede publicar listados en el mercado GitHub para la compra de productos del programador por parte de los usuarios finales y el uso en conexión con GitHub.com. El presente acuerdo se aplica a los productos del Programador distribuidos para productos gratuitos y de Programador para los cuales se cobra una tarifa a los usuarios finales. El programador acepta usar el mercado de GitHub únicamente para los fines permitidos por el presente acuerdo o según lo permita la legislación aplicable. Entre GitHub y el Programador, el Programador es el único responsable de los productos del Programador. + +**2.2** El Programador otorga a GitHub una licencia no exclusiva, en todo el mundo, transferible, sublicenciable, totalmente pagada y exenta de regalías para (a) alojar, vincular, reproducir, modificar, ejecutar públicamente, exhibir públicamente, probar, distribuir, poner a disposición, licenciar y usar de cualquier otra manera el listado; (b) reproducir, ejecutar, exhibir, usar y acceder a la lista con fines de administración y demostración en relación con la operación y la comercialización del mercado; y (c) reproducir, mostrar, distribuir y usar de cualquier otra manera las características de la marca del Programador que este le haya suministrado a GitHub conforme a lo dispuesto en el presente acuerdo únicamente para su uso en relación con el mercado y para cumplir con sus obligaciones conforme al acuerdo. + +**2.3** Además de las licencias concedidas anteriormente, GitHub puede incluir características de la marca del Programador suministradas por el programador para GitHub conforme a lo dispuesto en el presente acuerdo en cualquier presentación, comunicación, material de marketing, comunicados de prensa, listas de clientes (incluyendo, entre otras, las listas de clientes, publicadas en los sitios web de GitHub), campañas publicitarias y otras garantías publicitarias para propósitos de comercializar el mercado. Si el Programador descontinúa la distribución de productos específicos del programador en el mercado, GitHub dejará de usar las características de marca de los productos del Programador descontinuados después de un período de tiempo comercialmente razonable. Nada en el presente acuerdo otorga al Programador un derecho a usar ninguna de las características de la marca GitHub. + +**2.4** El programador otorga a cada usuario final un derecho o licencia no exclusivo, en todo el mundo, para llevar a cabo, mostrar y usar los productos del Programador y cualquier contenido al que se acceda o se transmita a través de los productos del Programador en relación con el mercado. El Programador debe incluir un acuerdo de licencia de usuario final ("EULA") por separado en sus productos de Programador que regirá los derechos del usuario final sobre los productos del Programador en lugar de la frase anterior. El Programador reconoce y acepta que el EULA aplicable para cada producto de Programador se encuentra únicamente entre el Programador y el usuario final. GitHub no será responsable, ni tendrá ninguna responsabilidad en absoluto, en virtud de ningún EULA. + +**2.5** Excepto por los derechos de licencia concedidos en el presente acuerdo, (a) el programador retiene todos los derechos sobre los productos del Programador; (b) cada una de las partes conserva todos los derechos que tiene independientes del presente acuerdo, incluyendo los derechos conforme a la ley de derechos de autor de los Estados Unidos o leyes similares de otras jurisdicciones; y (c) cada una de las partes posee todos los derechos, título e interés en sus respectivas características de marca. Cada una de las partes es responsable de proteger y hacer cumplir sus propios derechos respectivos y ninguna de las partes tiene la obligación de hacerlo en nombre del otro. + +**2.6** El programador reconoce y acepta que GitHub tendrá derecho a proporcionar el nombre del Programador, la dirección y otros detalles de contacto a cualquier tercero que razonablemente, en la única determinación de GitHub, afirme que el Programador no posee todos los derechos de propiedad intelectual necesarios sobre o para los productos del programador. + +### 3. RESTRICCIONES Y RESPONSABILIDADES + +Independientemente de cualquiera de los requisitos establecidos en la sección 2, Propósito y Concesión de Licencia, antes mencionados, el Programador reconoce y acepta que su uso del mercado y la participación en el programa están explícitamente condicionados al apego del Programador al presente acuerdo, incluyendo, entre otras, las restricciones y los requisitos de cumplimiento establecidos en la presente sección 3. + +**3.1** El Programador acepta que protegerá la privacidad y los derechos legales de todos los usuarios finales. Si un usuario final proporciona a un Programador, o el producto de lo contrario recopila, divulga, accede o usa, nombres de usuario final, contraseñas u otra información personal, el Programador debe (a) informar a los usuarios finales que dicha información estará disponible para los productos del programador; y (b) proporcionar un aviso de privacidad legalmente adecuado y protección a los usuarios finales. Además, los productos de Programador solo pueden usar la información para el propósito limitado para el cual el Programador ha obtenido permiso del usuario final. Si los productos del Programador almacenan o transmiten información personal o confidencial proporcionada u obtenida por los usuarios finales, entonces el Programador debe asegurarse de que toda esa actividad se realice de manera segura y deba responder de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de los usuarios finales del mercado. + +**3.2** Para usar y acceder a la API de GitHub, el Programador debe obtener las credenciales de la API (un "token") al convertirse en un suscriptor. El Programador no puede compartir su token con ningún tercero, debe mantener seguro dicho token y toda la información de inicio de sesión y usará el token como el único medio del programador para acceder a la API de GitHub. + +**3.3** El programador reconoce y acepta que no participará en ninguna actividad con el mercado, incluyendo la distribución de productos del programador, que viola las políticas del mercado o que: + +- 1\. Viola cualquier ley o normativa aplicable o promueve actividades ilícitas; +- 2\. Contiene o instala cualquier malware o exploits activos, o utiliza nuestra plataforma para la entrega de exploits (como parte de un sistema de comando y control); +- 3\. Interfiere, altera, interrumpe, daña o accede de manera no autorizada a las máquinas, los sistemas, el hardware, los servidores, las redes, los dispositivos, los datos u otras propiedades o servicios de cualquier tercero; +- 4\. Incluye contenido falso o engañoso; +- 5\. Infringes on any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other rights; +- 6\. Is libelous, defamatory, or fraudulent; +- 7\. Habilita la descarga no autorizada de contenido de streaming o medios; +- 8\. Muestra o vincula a contenido ilegal; +- 9\. Acosa, abusa, amenaza o incita a cualquier persona o grupo, incluyendo los empleados, los funcionarios y los agentes de GitHub, o cualquier usuario final; +- 10\. Is or contains sexually obscene content; +- 11\. Sea discriminatorio o abusivo hacia cualquier persona o grupo; +- 12\. Desvía a los usuarios finales o proporciona enlaces a cualquier otro sitio que imita al mercado o se hace pasar a sí mismo como mercado. + +**3.4** El Programador no podrá, en ningún caso, a través de productos de desarrollo o de cualquier otra manera, empaquetar nuevamente o revender el mercado, la API de GitHub o los datos de uso. Al Programador no se les permite usar la API de GitHub ni ningún dato de uso de ninguna manera que pueda socavar la seguridad del servicio, la API de GitHub, los datos de uso o cualquier otro dato o información almacenada o transmitida utilizando el mercado. Además, el Programador no debe, y no intentará, interferir, modificar o inhabilitar ninguna característica, control de funcionalidad o seguridad del mercado o de la API de GitHub, rechazar, evitar, eludir, eliminar, desactivar o impedir ningún mecanismo de protección para el mercado o la API de GitHub, o realizar ingeniería inversa, descompilar, desmontar o derivar código fuente, ideas subyacentes, algoritmos, estructura o formulario organizativo desde el mercado o la API de GitHub. + +**3.5** El Programador reconoce que el Programador es el único responsable y que GitHub no tiene responsabilidad ni obligación de ningún tipo, por el contenido, desarrollo, operación, soporte o mantenimiento de los productos del programador. Sin limitar el comienzo, el Programador será el único responsable de: +- (i) la instalación técnica y el funcionamiento de sus productos de Programador; +- (ii) crear y mostrar información y contenido sobre, a través o dentro de sus productos de Programador; +- (iii) asegurar que sus productos de Programador no violen o infrinjan los derechos de propiedad intelectual de un tercero; +- (iv) asegurar que los productos del Programador no sean ofensivos, profanos, obscenos, injuriosos o ilegales; +- (v) asegurar que sus productos de Programador no contengan o introduzcan software malintencionado en el mercado, la API de GitHub, cualquier dato de uso u otros datos almacenados o transmitidos utilizando el mercado; y +- (vi) asegurar que sus productos de Programador no estén diseñados o utilizados con el fin de enviar mensajes electrónicos comerciales a ningún usuario, agente o usuario final de GitHub.com sin su consentimiento. + +**3.6** El programador respetará y cumplirá con las limitaciones técnicas e implementadas por políticas de la API de GitHub y las restricciones del presente acuerdo en el diseño y la implementación de productos para Programador. Sin perjuicio de lo anterior, el Programador no violará ninguna limitación de tasa explícita en la convocatoria o el uso de la API de GitHub. + +**3.7** GitHub se reserva el derecho a rescindir el presente acuerdo de inmediato si GitHub determina que el programador ha incumplido cualquier requisito u obligación de la presente sección 3. + +**3.8** Ninguna disposición del presente Acuerdo impedirá que alguna de las partes desarrolle y/o publique aplicaciones que sean similares o que compitan de cualquier otra manera con las solicitudes de la otra parte. + +### 4. ELIMINACIONES + +**4.1** Tus eliminaciones. Al proporcionar a GitHub una notificación por escrito de treinta (30) días antes del 1er día del mes calendario subsiguiente, puedes eliminar tus anuncios de la distribución futura por medio del mercado, pero debes cumplir con el presente acuerdo para cualquier lista distribuida a través del mercado, incluyendo, entre otros, los requisitos de reembolso. Eliminar tu lista de la distribución futura por medio del mercado no (a) afecta los derechos de licencia de los usuarios finales que previamente compraron o instalaron tu perfil o (b) cambia tu obligación de entregar o apoyar un listado que haya sido adquirido o instalado previamente por los usuarios. + +Sin perjuicio de lo anterior, en ningún caso GitHub mantendrá en ninguna parte del mercado, ninguna lista que hayas eliminado del mercado y le haya dado un aviso por escrito a GitHub de que dicha eliminación se debió a: + +- (i) una acusación de infracción o infracción real de cualquier derecho de autor, marca registrada, secreto comercial, imagen comercial, patente u otro derecho de propiedad intelectual de ninguna persona, +- (ii) una acusación de difamación o difamación real, +- (iii) una acusación de violación o violación real de los derechos de publicidad o privacidad de un tercero, o +- (iv) una acusación o determinación de que dicha lista no cumple con la legislación aplicable. + +Si eliminas una lista del mercado conforme a las cláusulas (i), (ii), (iii) or (iv) de la presente sección 4.1 y un usuario final que compró dicho listado dentro de un año antes de la fecha de retirada, GitHub no es responsable de los reembolsos al comprador afectado de ninguna cantidad pagada por dicho cliente final durante el año anterior a la fecha de retirada de dicha lista afectada. + +**4,2** Revisión y eliminaciones de GitHub. Si bien GitHub no está obligada a supervisar el listado o su contenido, GitHub puede, en cualquier momento, revisar o evaluar tu lista para cumplir con el presente acuerdo, las políticas del programa de mercado y cualquier otro término, obligación, ley o regulación aplicables. GitHub se reserva el derecho de negarse a incluir una lista en el mercado a su entera discreción. Es posible que se te solicite que proporciones información sobre ti (como la identificación o los detalles de contacto) como parte del proceso de registro del mercado o como parte de tu uso continuo del mercado. Aceptas que cualquier información que le des al mercado siempre será precisa, correcta y actualizada. Como parte de la especificación de tu lista, GitHub puede pedirte que incluyas en el archivo la información de tu lista, como tu nombre y dirección de correo electrónico. GitHub puede usar esta información cuando presente la lista en nuestro directorio o para otros usos. + +Si notificas a GitHub o de otra forma tiene conocimiento y determina a su exclusivo criterio que una lista o cualquier parte de la misma o de tus características de marca: +- (a) viola los derechos de propiedad intelectual o cualquier otro derecho de terceros; +- (b) viola cualquier ley aplicable o está sujeta a un mandato; +- (c) es pornográfica, obscena o de otro modo viola las políticas de alojamiento de GitHub u otros términos de servicio que puedan actualizarse por GitHub de vez en cuando a su entera discreción; +- (d) se está distribuyendo incorrectamente; +- (e) puede crear responsabilidad por parte de GitHub o a cualquier tercero; +- (f) se considera como maliciosa o defectuosa por GitHub; +- (g) viola los términos de este Acuerdo o las políticas del programa del mercado; +- (h) la visualización de la lista está afectando a la integridad de los servidores de GitHub (es decir, los usuarios no pueden acceder a dicho contenido o de otra forma experimentan dificultad); +- (i) se considera por GitHub que adiciona un riesgo indebido a los datos de los usuarios finales del mercado o perjudica la experiencia del usuario del mercado o de GitHub; +- (j) está sujeta a quejas de los usuarios en cuanto a la violación de su EULA, o +- (k) de otro modo viola los Términos o este Acuerdo, + +GitHub puede: Evitar que la lista se pueda poner a disposición en el mercado; eliminar el listado del mercado; marcar, filtrar o modificar materiales relacionados (incluyendo, entre otros, descripciones, capturas de pantalla o metadatos); o reclasificar la lista a su exclusivo criterio. GitHub se reserva el derecho a suspender u obstruir cualquier lista del mercado a su exclusivo criterio. + +En el caso de que tu publicación se elimine involuntariamente porque es defectuosa, maliciosa, viola los derechos de propiedad intelectual de otra persona, difama, viola el derecho de publicidad o privacidad de un tercero, o no cumple con las leyes aplicables y un usuario final compró dicho listado dentro de un año antes de la fecha de la eliminación: + +- (i) debes reembolsar al comprador afectado todas las cantidades pagadas por dicho cliente final durante el año anterior a la fecha de eliminación de dicha lista afectada. +- (ii) GitHub puede, a su exclusivo criterio, retener de tus ventas futuras la cantidad en la subsección (i) anterior. + +**4.3** De vez en cuando, GitHub puede revisar si hay actualizaciones disponibles para el listado, incluyendo pero sin limitación a correcciones de errores o funcionalidad mejorada. Si actualizas tu lista en el mercado, aceptas que dicha actualización se solicitará, descargará e instalará automáticamente sin previo aviso. GitHub no ofrece ninguna garantía con respecto al momento de dichas actualizaciones. Para evitar dudas, las actualizaciones al listado están sujetas a los mismos términos y condiciones que el listado, incluyendo, sin limitación, la sección 4.2 del presente acuerdo (revisión y eliminación de GitHub). + +**4.4** Eliminaciones del usuario final. Si un usuario final usa tu producto de Programador de manera que viole los términos, entonces tenemos el derecho de suspender o terminar el acceso del usuario final al producto del Programador sin ninguna responsabilidad para ti. + +### 5. REPRESENTACIONES, GARANTÍAS Y CONVENIOS + +**5.1** El Programador declara y garantiza que el Programador notificó a todos los usuarios de dichas aplicaciones de desarrollo que los datos de su cuenta se transmitirán fuera del servicio y los términos del programador controlarán la privacidad, seguridad o integridad de los datos de la cuenta. El Programador además declara y garantiza que, en la medida en que las aplicaciones del programador almacenen, procesen o transmitan datos de la cuenta, ni el programador ni la aplicación del programador, sin el consentimiento del usuario previo adecuado o excepto en la medida que lo exija la ley aplicable, +- (i) modificará el contenido de los datos de la cuenta de una manera que afecte negativamente a la integridad de los datos de la misma; +- (ii) revelará datos de cuenta a terceros; o +- (iii) usará datos de cuenta para cualquier otro propósito que no sea proporcionar la funcionalidad de la aplicación del Programador a los usuarios de dicha aplicación de Programador. El programador debe mantener y manejar todos los datos de la cuenta de acuerdo con las medidas de privacidad y seguridad razonablemente adecuadas para preservar la confidencialidad y la seguridad de todos los datos de la cuenta y todas las leyes y regulaciones de privacidad aplicables. + +**5.2** El Programador acepta que cumplirá con el Anexo de protección de datos de GitHub. + +**5.3** El Programador declara, garantiza y pacta que: (i) sus productos de Programador y las características de la marca del Programador no violarán, malinterpretarán o infringirán los derechos de propiedad intelectual de ningún tercero; (ii) el Programador cumplirá con todas las leyes y regulaciones locales, estatales, nacionales e internacionales aplicables, incluidas, entre otras, todas las leyes de control de exportación aplicables y mantendrá todas las licencias, permisos y otros permisos necesarios para desarrollar, implementar y distribuir sus productos de desarrollo; y (iii) sus productos de Programador no contendrán o introducirán en el mercado, la API de GitHub, cualquier dato de uso u otros datos almacenados o transmitidos utilizando el mercado, cualquier software malintencionado; (vi) sus productos de Programador no estarán diseñados o se utilizarán con el fin de enviar mensajes electrónicos comerciales a ningún cliente de GitHub, agentes o usuarios finales sin su consentimiento; (v) tendrán todo derecho, poder y autoridad para otorgar las licencias concedidas a GitHub y a los usuarios finales en el presente documento; (vi) reconocerá el derecho de GitHub a cobrar las tarifas de las transacciones y/o los listados conforme a lo dispuesto en la sección 6 del presente documento; las imágenes y el texto que se usan para comercializar los productos de desarrollo o que el programador ha subido al mercado son veraces, precisos y no pretenden confundir o confundir al usuario final. + +**5.4** DESCARGO DE GARANTÍAS. TODOS LOS ASPECTOS DEL MERCADO Y DE LA API DE GITHUB, INCLUYENDO TODOS LOS COMPONENTES DEL SERVIDOR Y DE LA RED, SE PROPORCIONAN "TAL CUAL" Y "SEGÚN DISPONIBILIDAD", SIN GARANTÍAS DE NINGÚN TIPO EN LA MEDIDA EN QUE LO PERMITA LA LEY Y GITHUB RENUNCIA EXPRESAMENTE A TODAS LAS GARANTÍAS, YA SEAN EXPRESAS O IMPLÍCITAS, INCLUYENDO, ENTRE OTRAS, CUALQUIER GARANTÍA IMPLÍCITA DE COMERCIABILIDAD, TÍTULO, IDONEIDAD PARA UN PROPÓSITO PARTICULAR Y NO EL DE INFRACCIÓN. EL PROGRAMADOR RECONOCE QUE GITHUB NO GARANTIZA QUE EL MERCADO O LA API DE GITHUB NO SE INTERRUMPIRÁN, OPORTUNAMENTE, DE MANERA SEGURA, SIN ERRORES O QUE ESTARÁ LIBRE DE VIRUS, MALWARE O GUSANOS (TAMBIÉN CONOCIDO COMO CÓDIGO INFORMÁTICO U OTRA TECNOLOGÍA ESPECÍFICAMENTE DISEÑADA PARA INTERRUMPIR, INHABILITAR O DAÑAR TU SOFTWARE, HARDWARE, SISTEMA INFORMÁTICO O RED) Y NINGUNA INFORMACIÓN O ASESORAMIENTO OBTENIDO POR PARTE DE UN PROGRAMADOR DE GITHUB O A TRAVÉS DEL MERCADO O DE LA API DE GITHUB CREARÁ NINGUNA GARANTÍA QUE NO ESTÉ EXPRESAMENTE ESTABLECIDA EN LOS PRESENTES TÉRMINOS. GITHUB NO ES RESPONSABLE Y ESPECÍFICAMENTE RECHAZA CUALQUIER RESPONSABILIDAD POR CUALQUIER USO NO AUTORIZADO DE PRODUCTOS DEL PROGRAMADOR FUERA DEL MERCADO. + +### 6. PRECIOS Y TÉRMINOS DE PAGO + +**6.1** GitHub será el comerciante de los productos de Programador comprados por usuarios finales a través del mercado. + +**6.2** Los precios de las listas del mercado de las aplicaciones del Desarrollador se configurarán en dólares estadounidenses (USD). El desarrollador tiene un control total sobre la fijación de precios para cada listado y una vez establecido, dicho precio no se puede cambiar. Puedes retirar un plan de precios para un listado existente y agregar un nuevo plan de precios para dicho listado, siempre que dicho plan de precios nuevo no afecte de forma negativa a los usuarios finales existentes. Los precios que configuraste para los productos de Programador determinarán la cantidad de pago que recibirás. GitHub remitirá el 95% del precio de venta en dólares estadounidenses sin reducción para los impuestos, excepto para cualquier retención de impuestos que se requiera conforme a la legislación aplicable. El 5% restante del precio de venta se asignará y retendrá por GitHub. Al final de cada mes y al alcanzar un valor mínimo de $500 USD, GitHub reenviará tu parte de los pagos. + +**6.3** Requisitos de Reembolso. Serás responsable de especificar los términos y condiciones relativos a los reembolsos a tus usuarios finales. En ningún caso GitHub será responsable de proporcionar ayuda alguna con los reembolsos, ni será GitHub será responsable del pago de ningún reembolso. + +**6.4** Apoyas tu producto de Programador. Serás el único responsable del soporte y el mantenimiento de tus productos de Programador y de cualquier queja sobre tus productos de Programador. Tu información de contacto de soporte será mostrada en cada página de detalles de la aplicación y estará a disposición de los usuarios con fines de soporte al cliente. Si no se proporciona el soporte adecuado para tus productos de Programador, se puede dar como resultado una exposición del producto menos destacada o, en algunos casos, la eliminación del mercado o en cualquier otro lugar en GitHub.com donde los productos del programador previamente comprados o descargados se almacenen en nombre de los usuarios. + +### 7. PROPIEDAD + +Sujeto a las licencias limitadas expresamente establecidas en el presente Acuerdo, nada en el presente acuerdo transfiere o asigna a una parte ninguno de los derechos de propiedad intelectual de la otra parte sobre sus características de marca u otra tecnología, y nada en el presente acuerdo transfiere o asigna a una parte ninguno de los derechos de propiedad intelectual de la otra parte. + +### 8. LIMITACIÓN DE RESPONSABILIDAD + +BAJO NINGUNA CIRCUNSTANCIA Y BAJO NINGUNA TEORÍA LEGAL (YA SEA EN EL CONTRATO, AGRAVIO, NEGLIGENCIA O DE CUALQUIER OTRA MANERA) GITHUB, O SUS AFILIADOS, EJECUTIVOS, DIRECTORES, EMPLEADOS, AGENTES O PROVEEDORES SERÁN RESPONSABLES ANTE EL PROGRAMADOR O CUALQUIER TERCERO CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO POR NINGÚN DAÑO INDIRECTO, INCIDENTAL, ESPECIAL, EJEMPLAR, CONSECUENTE, PUNITIVO U OTRO DAÑO SIMILAR, INCLUYENDO PÉRDIDAS DE BENEFICIOS, VENTAS O NEGOCIOS PERDIDOS, DATOS PERDIDOS, INTERRUPCIONES COMERCIALES O CUALQUIER OTRA PÉRDIDA INCURRIDA POR EL PROGRAMADOR O CUALQUIER TERCERO EN RELACIÓN EL PRESENTE ACUERDO, INDEPENDIENTEMENTE DE SI SE HA ADVERTIDO A LOS DESARROLLADORES DE LA POSIBILIDAD O DE HABER PODIDO PREVER DICHOS DAÑOS, INDEPENDIENTEMENTE DE CUALQUIER DISPOSICIÓN CONTRARIA EN EL PRESENTE ACUERDO, LA RESPONSABILIDAD AGREGADA DE GITHUB AL PROGRAMADOR O A CUALQUIER TERCERO QUE SURJA DEL PRESENTE ACUERDO NO SUPERARÁ LOS SEIS (6) MESES DE GASTO. + +### 9. INDEMNIZACIÓN + +**9.1** En la medida máxima permitida por la legislación aplicable, el Programador acepta defender, indemnizar y eximir de toda responsabilidad a GitHub, sus filiales y sus respectivos directores, funcionarios, empleados y agentes de cualquier reclamación, acciones, demandas o procedimientos, así como cualquier pérdida, responsabilidad, daño, costo y gasto (incluyendo los honorarios razonables de abogados) que surjan de o estén relacionados con (a) el uso del mercado por parte de un programador en violación del presente acuerdo, los términos o cualquier ley o regulación aplicable; (b) productos del programador que infrinjan cualquier derecho de autor, marca registrada, secreto comercial, patente u otro derecho de propiedad intelectual de cualquier tercero; (c) cualquier pérdida o divulgación de datos o información personal por parte de los productos del programador; y (d) EULA (o ToS) del Programador. + +### 10. TERMINACIÓN + +**10.1** El presente acuerdo continuará aplicándose hasta que se rescinda por cualquiera de las partes como se indica a continuación. + +**10.2** Cualquiera de las partes puede rescindir el presente acuerdo por cualquier motivo al proporcionar un aviso por escrito a los otros cuarenta y cinco (45) días anteriores al mes calendario inmediatamente siguiente. Durante este período de 45 días, los términos vigentes en el momento en que se proporcionó la notificación de terminación regirán por la duración del período de aviso de 45 días hasta la fecha de terminación real. + +**10.3** GitHub puede rescindir el presente acuerdo en cualquier momento si (a) has incumplido alguna disposición del presente acuerdo o (b) que GitHub está obligado a hacerlo por ley. + +**10.4** Efectos de la terminación por parte del Programador. Al recibir una notificación por escrito con anticipación de cuarenta y cinco (45) días de terminación por parte del Programador, se inhabilitará al programador para que no tome nuevos clientes a través del mercado. Cualquier tarifa pendiente se reenviará tras la terminación y la eliminación del producto de Programador del mercado. Si la terminación se inicia como resultado de que GitHub modificó estas condiciones (Sección 11), las condiciones en efecto inmediatamente antes de dicha modificación deberán regir la duración del periodo de notificación de 45 días hasta la fecha de terminación real. + +**10.5** Las obligaciones en las secciones 2, 3, 4, 5, 8, 9 y 12-18 sobrevivirán a cualquier vencimiento o terminación del presente acuerdo. + +### 11. MODIFICACIÓN + +El programador reconoce y acepta que GitHub puede modificar el presente acuerdo, el mercado, la API de GitHub, las políticas generales de la API, la política de privacidad de GitHub, los ToS del programa de Programadores de GitHub y los ToS de GitHub.com de vez en cuando (una "Modificación"). Todas las modificaciones se comunicarán a través del mercado, el sitio web de GitHub en www.GitHub.com o mediante una forma de comunicación directa de GitHub al Programador. El Programador reconoce y acepta que dichas modificaciones pueden implementarse en cualquier momento y sin previo aviso al Programador. El Programador debe, dentro de los cuarenta y cinco (45) días a partir de la fecha de la primera notificación de cualquier modificación (o dicho período de tiempo más corto especificado en el aviso de la(s) modificación es)) (el "Período de Conformidad") cumplir con dichas modificaciones mediante la implementación y el uso de la versión más reciente de la API de GitHub en la versión más reciente de los productos del Programador y la realización de cualquier cambio en los productos del programador que puede requerirse como resultado de dichas modificaciones. El Programador reconoce que una modificación puede tener un efecto adverso en los productos del programador, incluyendo, entre otros, el cambio de la manera en que las aplicaciones se comunican con la API de GitHub. GitHub no será responsable de ningún tipo del Programador o de ningún usuario final con respecto a dichas modificaciones o cualquier efecto adverso derivado de dichas modificaciones. El acceso continuado del Programador o el uso del mercado o de la API de GitHub después del período de conformidad constituirá la aceptación vinculante de la(s) modificación(es) en litigio. + +### 12. ASIGNACIÓN; ACUERDO COMPLETO; REVISIONES + +**12.1** El programador no puede, directa o indirectamente, por operación de la ley o de cualquier otra manera, asignar la totalidad o parte del presente acuerdo o los derechos del Programador conforme a lo dispuesto en el presente acuerdo o delegar el desempeño de las obligaciones del Programador conforme a lo dispuesto en el presente acuerdo sin el consentimiento previo por escrito de GitHub. Los derechos otorgados en el presente acuerdo pueden asignarse o transferirse por GitHub sin la aprobación previa del programador. Además, GitHub puede delegar sus responsabilidades u obligaciones conforme a lo dispuesto en el presente acuerdo sin el consentimiento del Programador. + +**12.2** El presente acuerdo, junto con los términos, constituye el acuerdo completo entre las partes con respecto al objeto del presente acuerdo. El incumplimiento por parte de GitHub de hacer cumplir en cualquier momento cualquier disposición del presente acuerdo no constituye una renuncia a esa disposición o a cualquier otra disposición del presente acuerdo. + +### 13. DIVISIBILIDAD + +Si alguna disposición del presente acuerdo se considera inejecutable por parte de un tribunal de jurisdicción competente, dicha disposición se modificará por el Tribunal y se interpretará de manera que se logre mejor la disposición original en la medida en que lo permita la ley y las disposiciones restantes del presente acuerdo permanecerán vigentes. + +### 14. RELACIÓN DE LAS PARTES + +Las partes son contratistas independientes. El presente acuerdo no crea una relación de colaboración, franquicia, empresa conjunta, agencia, fiduciaria o de empleo entre las partes. El Programador acepta que cada miembro del grupo de compañías al que pertenece GitHub será un tercero beneficiario del presente acuerdo y que dichas otras compañías tendrán derecho a hacer cumplir y basarse directamente en cualquier disposición del presente acuerdo que confiere un beneficio o otorga un derecho a favor o GitHub. Ninguna otra persona, empresa o entidad legal será un tercero beneficiario del acuerdo. + +### 15. AVISOS + +Todas las notificaciones que GitHub debe proporcionar al Programador conforme a lo dispuesto en el presente acuerdo pueden entregarse por escrito (i) por el servicio de entrega a domicilio ("Courier") reconocido a nivel nacional o por correo electrónico a la dirección de correo electrónico de contacto proporcionada por el programador a GitHub; o (ii) correo electrónico a la dirección de correo electrónico proporcionada por el Programador. mail to the contact mailing address provided by Developer to GitHub; or (ii) electronic mail to the electronic mail address provided by Developer. El programador debe dar aviso a GitHub por escrito por mensajería o EE. UU. GitHub, Inc., en atención al: Departamento Jurídico, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107 EE. UU. Todas las notificaciones se considerarán entregadas inmediatamente después de la entrega por correo electrónico, o si se entregan de otra manera al recibirlo o, si son anteriores, dos (2) días hábiles después de haber sido depositadas por correo o con un mensajero como se permitió anteriormente. + +### 16. LEGISLACIÓN APLICABLE + +El presente acuerdo se regirá por las leyes del estado de California sin tener en cuenta los principios de conflicto de leyes. Por la presente, el Programador acepta expresamente someterse a la jurisdicción personal exclusiva de los tribunales federales y estatales del estado de California, en el Condado de San Francisco, con el fin de resolver cualquier disputa relacionada con el presente acuerdo. Sin perjuicio de lo anterior, GitHub tendrá derecho a buscar acciones cautelares u otros tipos de remedio legal urgente en cualquier jurisdicción. + +### 17. RESTRICCIONES DE EXPORTACIÓN + +LOS PRODUCTOS PARA PROGRAMADORES QUE SE DISTRIBUYEN POR MEDIO DEL MERCADO PUEDEN ESTAR SUJETOS A CONTROLES DE EXPORTACIÓN O RESTRICCIONES POR PARTE DE LOS ESTADOS UNIDOS U OTROS PAÍSES O TERRITORIOS. EL PROGRAMADOR ACEPTA CUMPLIR CON TODAS LAS LEYES Y REGULACIONES VIGENTES EN LOS ESTADOS UNIDOS Y LAS EXPORTACIONES INTERNACIONALES. ESTAS LEYES PUEDEN INCLUIR RESTRICCIONES EN LOS DESTINOS, EL CONTENIDO Y/O LOS USUARIOS FINALES. + +### 18. DATOS DE USO +Con el fin de operar y mejorar el mercado, GitHub puede recopilar datos de uso del mercado y API de GitHub o en cualquier lugar que los productos de programador previamente comprados o descargados se almacenen en nombre de los usuarios finales por parte de GitHub. Los datos de uso se mantendrán de acuerdo con las políticas de privacidad de GitHub vigentes en ese momento. Los datos de uso limitados pueden estar disponibles para su uso por parte del Programador a la exclusiva discreción de GitHub. + +# Anexo 1: Anexo de protección de datos + +El presente anexo de protección de datos (este "Anexo") se adjunta y forma parte del acuerdo del Programador del mercado de GitHub entre tú y GitHub (el "Acuerdo"). Los términos que no se definen en el presente Anexo tienen los significados que se les atribuyen en el Acuerdo. En el caso de un conflicto o incoherencia, los términos del presente Anexo sustituirán a los del acuerdo. + +**A1-1. Propósito y ámbito** GitHub mantiene la información personal de personas en todo el mundo, algunas de las cuales son residentes de países y áreas con leyes de protección de datos sólidas. Este Anexo establece tus responsabilidades cuando recibes y procesas cualquier dato protegido de GitHub. + +**A1-2. Definiciones** + +- a. "Leyes Aplicables de Protección de Datos" significa cualquier ley, regulación, marco de trabajo regulatorio u otras legislaciones relacionadas con el procesamiento y uso de la Información Personal de acuerdo a como sean aplicables al Acuerdo, incluyendo: + - El Reglamento General de Protección de Datos de la UE 2016/679 (“GDPR”), en conjunto con cualquier regulación o ley correspondiente o implementada equivalente; + - La Ley de Privacidad de los Consumidores de California de 2018, Cal. Civ. Code §§1798.100 et seq. ("CCPA"); and + - La Ley de Protección de Datos del Reino Unido de 2018 y la implementación de RGDP que se contiene en la misma. +- b. "Información personal" se refiere a cualquier información que se relacione con Usuario Final de GitHub, cliente o empleado individuales que pudiera, sola o en conjunto con otra información, identificarle personalmente, ya sea que la suministre GitHub para que el desarrollador la procese o que la genere el Desarrollador en el transcurso de llevar a cabo sus obligaciones bajo este acuerdo. +- c. "Procesamiento" se refiere a cualquier operación o conjunto de operaciones realizadas en los datos protegidos de GitHub, ya sea por medios manuales o automáticos, que incluyen recopilación, registro, organización, almacenamiento, adaptación, alteración, recuperación, consulta, uso, divulgación mediante transmisión, difusión o puesta a disposición, bloqueo, supresión o destrucción de cualquier otra manera. +- d. "Datos protegidos" se refiere a cualquier información confidencial transferida por GitHub al Programador sobre un usuario final de GitHub, que incluya la información personal, los metadatos, los datos de uso u otros datos o información que esté asociada con los usuarios finales de GitHub. + +**A1-3. Cumplimiento con las Leyes de Transferencia de Datos** + +- a. Cumplimiento con GitHub. GitHub cumple con las Leyes de Protección de Datos Aplicables. GitHub se basa en las Cláusulas Contractuales Estándar ("SCCs") para todas las transferencias fuera de la Unión Europea, Área Económica Europea, Reino Unido, y Suiza para proporcionar sus servicios. Adicionalmente, GitHub está certificado en el Marco del Escudo de Privacidad de U.E. - E.U.A. y de Suiza - E.U.A. y los compromisos que estos implican, aunque GitHub no depende de los de U.E.-E.U.A. Marco de Escudo de Privacidad como base jurídica para la transferencia de información personal a la luz de la sentencia del Tribunal de Justicia de la UE en el caso C-311/18. GitHub solo transferirá información personal al Programador para los fines limitados y especificados para los cuales se recopiló. +- b. Cumplimiento del Programador. El desarrollador representa y garantiza que (i) cumplirá con las Leyes de Protección de Datos Aplicables; y (ii) cumplirá con los requisitos del Área Económica Europea y la ley Suiza de protección de datos con respecto a la recolección, uso, transferencia, retenció y otro tipo de Información Personal del Área Económica Europea, Reino Unido y Suiza. Todas las transferencias de Información Personal a un país tercero o a una organización internacional estarán sujetos a las salvaguardas adecuadas como se describe en el artículo 46 de la RGPD y dichas transferencias y salvaguardas se documentarán de acuerdo con el artículo 30(2) de la misma. + +**A1-4. Protección de datos** + +- a. Notificaciones. El Programador debe identificarse como el recopilador y procesador de todos los datos que reúne del usuario final. El Programador no debe limitarse a recopilar información personal en nombre de GitHub. El Programador debe proporcionar un aviso suficiente de sus prácticas de privacidad al usuario final, por ejemplo, al publicar una política de privacidad. +- b. Limitación de propósitos. + - i. GitHub proporcionará a los Programadores los elementos de datos protegidos con el fin de establecer y facilitar una relación entre el Programador y el usuario final y permitir que el Programador brinde servicios al usuario final. El Programador debe limitar su uso de los datos protegidos con ese fin, a menos que el usuario final acepte permitir diferentes usos. + - ii. El Programador debe procesar y comunicar los datos protegidos a terceros únicamente para los fines limitados y específicos de proporcionar sus servicios al usuario final, tal como se describe en su acuerdo con el usuario final, a menos que este acepte permitir diferentes usos. +- c. Calidad y proporcionalidad de los datos. El Programador debe mantener los datos protegidos precisos y actualizados. +- d. Seguridad. El Programador debe tomar todas las medidas de seguridad razonables adecuadas para los riesgos, por ejemplo, contra la destrucción accidental o ilícita, o la pérdida accidental, alteración, divulgación o acceso no autorizado, presentadas al procesar los datos protegidos. +- e. Retención y eliminación de datos. Tras la solicitud razonable de GitHub, a menos que se prohiba por ley, el Programador debe regresar o destruir toda la información personal y los datos relacionados en todas las ubicaciones en las que se almacena después de que ya no sean necesarios para los fines limitados y especificados para los cuales fueron recopilados. El Programador debe tener disponible o desarrollar procesos de destrucción de la información que cumplan con los requisitos de seguridad de GitHub en la sección 3.8 del acuerdo. +- f. Subprocesamiento y transferencia ulterior. El Programador es responsable de las transferencias posteriores de datos protegidos a sus subprocesadores. En caso de que el desarrollador deba transferir los datos protegidos a un tercero, o de que se instale, use o habilite servicios de terceros para procesar dichos datos en nombre del desarrollador, dicho desarrollador deberá garantizar que el tercero proporcionará por lo menos el mismo nivel de protección de la privacidad como se requiere en el presente. + +**A1-5. Uso de datos protegidos** + +- a. Uso permitido. El Programador solo puede procesar los datos protegidos para los fines establecidos en la sección 4 (b) (i) y ningún otro propósito. +- b. Sin uso en Marketing. El Programador no debe usar los datos protegidos para publicitar ningún producto o servicio de terceros y no puede vender los datos protegidos a ningún tercero. +- c. Decisiones automatizadas. En el caso de que el Programador tome decisiones automatizadas que afecten los derechos de los clientes de GitHub, incluyendo el empleo, el crédito o el estado, el Programador debe proporcionar un aviso a las personas. + +**A1-6. Cumplimiento** + +- a. El programador debe cumplir con las solicitudes razonables de información sobre sus prácticas de privacidad y el uso de datos de la siguiente manera: + - i. A petición, el Programador hará su declaración de privacidad, política de privacidad, aviso de privacidad o cualquier documentación similar disponible. El Programador también proporcionará un aviso de cualquier informe de cumplimiento relevante, incluyendo el cumplimiento del escudo de la privacidad. + - ii. El Programador cumplirá con las obligaciones de seguridad de la información y auditoría en la sección 3.7 del acuerdo del Programador del mercado de GitHub. + +**A1-7. Termination** + +- a. Suspensión. En el caso de que el Programador incumpla con sus obligaciones de mantener un nivel adecuado de protección de la privacidad, GitHub puede suspender de forma temporal la transferencia de datos protegidos o prohibir la recopilación y el procesamiento de datos protegidos en nombre de GitHub hasta que se repare el incumplimiento o se termine el acuerdo. +- b. Terminación con causa. GitHub puede rescindir el Acuerdo sin perjuicio de cualquier otra reclamación en derecho o en equidad en el caso de que: + - i. el Programador notifique a GitHub que ya no puede cumplir con sus obligaciones de privacidad; + - ii. la transferencia, recopilación o procesamiento de los datos protegidos se haya suspendido temporalmente por más de un mes conforme a 7(a); + - iii. el Programador esté en incumplimiento sustancial o persistente de cualquier garantía o representación conforme a lo dispuesto en el presente anexo de protección de datos; + - iv. el Programador ya no dirige el negocio, se disuelve, entra en suspensión de pagos o se realiza una orden de liquidación en nombre del Programador. +- c. Incumplimiento. El incumplimiento de lo dispuesto en el presente anexo de protección de datos se considera una violación material conforme al acuerdo de servicios maestros. +- d. Notificación. En el caso de que el programador determine que ya no puede cumplir con sus obligaciones de privacidad conforme a lo dispuesto en el presente acuerdo, debe notificar a GitHub de inmediato. En el caso de que el programador haya sido certificado bajo el escudo de la privacidad y permita que la certificación caduque o no pueda permanecer certificada bajo el escudo de la privacidad, el Programador debe notificar a GitHub de inmediato. +- e. Modificaciones. GitHub puede modificar el presente Anexo de vez en cuando, según lo requiera la ley, con un aviso de treinta días para el Programador. Si el Programador no puede cumplir con las modificaciones del anexo, GitHub puede rescindir el acuerdo. +- f. Después de la terminación, el Programador debe: + - i. tomar las medidas razonables y apropiadas para detener el procesamiento de los datos protegidos; + - ii. dentro de los treinta días posteriores a la terminación, eliminar cualquier tienda de desarrolladores de datos protegidos en nombre de GitHub; y + - iii. proporcionar a GitHub la garantía razonable de que el Programador ha dejado de procesar los datos protegidos y eliminado los datos protegidos almacenados. + +**A1-8. Responsabilidad por el procesamiento de datos** +- a. Responsabilidad directa. El programador será responsable ante GitHub de los daños reales causados por cualquier incumplimiento del presente anexo sujeto a los términos de la sección 8, Limitación de Responsabilidad del Acuerdo del Programador del Mercado. diff --git a/translations/es-ES/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-marketplace-terms-of-service.md new file mode 100644 index 0000000000000..b8dbcd338227d --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-marketplace-terms-of-service.md @@ -0,0 +1,87 @@ +--- +title: Términos de servicio de Mercado GitHub +redirect_from: + - /articles/github-marketplace-terms-of-service +versions: + free-pro-team: '*' +--- + +¡Bienvenido a Mercado GitHub ("Mercado")! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio ("Términos del Mercado") antes de ingresar o usar Mercado GitHub. Mercado GitHub es una plataforma que te permite seleccionar aplicaciones o acciones del programador (de forma gratuita o con cobro) que se puede usar con tu cuenta de GitHub.com ("productos del programador"). Aunque GitHub, Inc. ("GitHub", "nosotros") lo ofrece, GitHub puede desarrollar y mantener productos del programador o los proveedores de software de terceros. Tu selección o uso de los productos del programador están sujetos a los presentes términos del mercado y a cualquier tarifa aplicable, y puede solicitarte que ingreses a los términos adicionales proporcionados por el licenciante externo de ese producto de programador (el "proveedor del producto"). + +Al usar el Mercado, aceptas estar obligado por estas Condiciones de Mercado. + +Fecha de entrada en vigencia: 20 de noviembre de 2020 + +### A. Términos de servicio de GitHub.com + +GitHub proporciona el mercado y se rige por los [Términos de servicio](/articles/github-terms-of-service/) o el [Términos de servicio corporativos](/articles/github-corporate-terms-of-service/) ("Términos de GitHub"), dependiendo de tu tipo de cuenta, así como de los presentes términos del mercado. Si configuras los Productos de Programador para que trabajen con una o más cuentas en el sitio web GitHub.com, tu uso de los Productos de Programador también se regirá por sus Términos de GitHub aplicables. Cualquier término en mayúsculas no definido en este documento se definirá en los términos aplicables de GitHub. + +No puedes utilizar un Producto de Programador para violar tus Términos de GitHub aplicables. Muchos de estos Productos de Programadro se utilizan exclusivamente para realizar tareas automatizadas. Además, varios usuarios pueden dirigir las acciones de un Producto de Programador. Sin embargo, si compras y/o configuras un Producto de Programador en tu cuenta o eres propietario de una cuenta con un Producto de Programador integrado, entonces serás responsable de las acciones del Producto del Programador que se llevan a cabo en o a través de tu cuenta. + +### B. Requisitos de uso + +A fin de poder usar el Mercado, debes tener 13 años o más (si vives en los Estados Unidos; si vives en otro país, debes cumplir con las leyes de edad mínima de tu país), tener una cuenta de GitHub válida y haber aceptado tus términos de GitHub y estos términos de mercado aplicables. + +Si estás de acuerdo con estos Términos de Mercado en nombre de una empresa, organización u otra entidad legal, significa que tienes la autoridad para vincular a esa entidad, a sus afiliados y a todos los usuarios que ingresen al mercado en su nombre a estos Términos del Mercado. Si no tienes autoridad, no debe aceptar estos Términos del Mercado y no puedes utilizar los servicios del mismo. + +### C. Productos de Programador y Proveedores de Productos + +Si instalas y/o compras un Producto de Programador, entonces estás comprando los Productos de Programador de GitHub y tienes que hacer los pagos relacionados directamente a GitHub. Sin embargo, estás recibiendo acceso y los derechos de usar ese Producto de Programador de un proveedor de productos, no de GitHub (a menos que sea un producto de programador propiedad de GitHub). El Proveedor del Producto es el único responsable del Producto de Programador que proporciona, el contenido del mismo y cualquier reclamación que tú o cualquier otra parte pueda tener relacionada con ese Producto de Programador o el uso de ese Producto de Programador. + +No somos parte del acuerdo entre tú y el Proveedor de Productos con respecto a dicho Producto de Programador. No somos responsables de dicho Producto de Programador, el contenido en él, o cualquier reclamación que tú o cualquier otra parte pueda tener relacionada con ese Producto de Programador o el uso de dicho Producto de Programador. Sin embargo, somos un tercero beneficiario del acuerdo entre tú y el proveedor de productos para cada producto de programador y tendremos el derecho (y se considerará que has aceptado el derecho) de hacer cumplir ese acuerdo en tu contra como un tercero beneficiario. + +### D. Pago, calendario de facturación y cancelación + +GitHub tramitará todos los pagos por Productos de Programador. Las condiciones de tu pago y las comisiones se regirán por [Sección K. Pago](/articles/github-terms-of-service/#k-payment) o la sección análoga de tus Condiciones de GitHub aplicables. Al usar el Mercado aceptas pagar a GitHub cualquier cargo incurrido en relación con tu compra del Producto de Programador. Cada compra es un contrato electrónico entre tú y GitHub y tú y el Proveedor de Productos. Eres responsable de proporcionarnos un medio de pago válido para las compras de Productos de Programador. Si sólo estás comprando productos de programador gratuitos, no estás obligado a proporcionar información de pago. + +**Calendario de facturación; Sin reembolsos.** Tu calendario de pago se determina por el calendario de pago que elegiste cuando creaste tu cuenta de GitHub (por ejemplo, gratis, mensual, anual). Para planes de pago mensuales o anuales, las compras en el mercado se facturan por adelantado de forma mensual o anual respectivamente y no son reembolsables. No habrá reembolsos o créditos por meses parciales de servicio, reembolsos por descenso de categoría o reembolsos por meses sin uso; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Si deseas cancelar los servicios del Producto de Programador, puedes hacerlo entrando en sus Ajustes en la barra de navegación global en la parte superior de la pantalla. + +Si tienes una pregunta, inquietud o disputa con respecto a tu facturación, ponte en contacto con [el soporte de GitHub](https://support.github.com/contact). + +### E. Tus datos y la política de privacidad de GitHub + +**Privacidad.** Cuando seleccionas o utilizas un Producto de Desarrollador, GitHub puede compartir cierta Información Personal (como se define en la[Declaración de Privacidad de GitHub](/articles/github-privacy-statement/)) con el Proveedor de Producto (si se recibe dicha Información Personal de tu parte) para proporcionarte el Producto de Desarrollador, independientemente de su configuración de privacidad. Dependiendo de los requisitos del producto para programador que elijas, GitHub puede compartir solamente el nombre de tu cuenta de usuario, ID y la dirección de correo electrónico principal o el acceso al contenido de tus repositorios, incluyendo la capacidad de leer y modificar tus datos privados. Podrás ver el alcance de los permisos que el Producto del Programador está solicitando y aceptarlos o rechazarlos cuando le concedes la autorización a través de OAuth. + +Si ya no usas el producto de programador y revocas el acceso a través de los parámetros de tu cuenta, el proveedor del producto ya no podrá acceder a tu cuenta. El Proveedor de Producto es responsable de eliminar tu Información Personal de tus sistemas dentro de su ventana definida. Ponte en contacto con el Proveedor del Producto para asegurar que tu cuenta se canceló correctamente. + +**Aviso de seguridad de datos y privacidad.** Cuando seleccionas o usas un producto de programador, la seguridad del producto del programador y la custodia de tus datos, incluyendo tu información personal (si la hay), es responsabilidad del proveedor del producto. Eres responsable de comprender las consideraciones de seguridad y privacidad de la selección o el uso del producto de programador por tus propios riesgos de seguridad y privacidad y consideraciones de cumplimiento. + +### F. Derechos a Productos de Programador + +Los derechos que se te otorgan para usar cualquier Producto de Programador son personales y no son transferibles a terceros, como tus usuarios finales. Cualquier derecho de proporcionar o revender los Productos de Programador a terceros debe otorgarse directamente por el Proveedor del Producto. + +### G. Actualizaciones a Productos de Programador + +De vez en cuando, GitHub.com puede comprobar con servidores remotos (alojados por GitHub o por terceros) si existen actualizaciones disponibles para los Productos de Programador, incluyendo pero sin limitación a correcciones de errores o funcionalidad mejorada. Aceptas que dichas actualizaciones se solicitarán, descargarán e instalarán automáticamente, sin previo aviso. + +### H. Bloqueo de Productos de Programador + +GitHub puede bloquear un Producto de Programador de nuestros servidores, o desactivar su funcionalidad, por razones legales o de política. En el caso que debamos bloquear o desactivar un Producto de Programador, trabajaremos con el Proveedor del Producto para notificar a los usuarios afectados. + +### I. Descargo de responsabilidad; Limitación de responsabilidad; Liberación e indemnización + +**Descargo de responsabilidad.** El uso que hagas del Mercado y de los Productos de Programador obtenidos a través del mercado es bajo tu propio riesgo. Además de lo indicado expresamente, GitHub proporciona el mercado y los Productos de Programador “TAL CUAL” y “SEGÚN ESTÉN DISPONIBLES”. GitHub no hace o implica ninguna garantía o compromiso sobre el mercado y los Productos de Programador, incluyendo, sin limitación a la funcionalidad específica disponible a través del mercado y los Productos de Programador, su fiabilidad, disponibilidad o capacidad para satisfacer tus necesidades. + +Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el mercado b (o cualquier parte de este) con o sin notificación. + +**Limitación de responsabilidades.** Comprendes y aceptas que GitHub no será responsable ante ti o ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad o datos, o por ningún incidente, daños indirectos, especiales, consecuenciales o ejemplares que surjan o resulten de: (i) el uso o la incapacidad de utilizar el mercado o cualquier producto de programador; (ii) cualquier modificación, cambio de precios, suspensión o interrupción del mercado o productos de programador; (iii) el mercado en general o el software o sistemas que hacen que el mercado esté disponible; (iv) acceso no autorizado a tus transmisiones o datos no autorizados; (v) declaraciones o conducta de cualquier tercero, Proveedor de Productos, o Producto del Programador en el mercado; (vi) cualesquier otra interacción de usuario que introduzcas o recibas a través de tu uso del mercado; o (vii) cualquier otro asunto relacionado con el mercado. + +**Liberación e indemnización.** Si tienes una disputa con uno o más Proveedor de Productos, aceptas liberar a GitHub de todos y cada uno de las reclamaciones, demanda y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o en cualquier forma relacionados con dichas disputas. + +Aceptas indemnizarnos, defendernos y eximirnos de toda responsabilidad contra cualquiera y toda reclamación, responsabilidad y gastos, incluyendo los honorarios de los abogados, que surgen de tu uso del mercado, incluyendo, sin limitación a la violación de estos Términos del Mercado, considerando que GitHub (1) le dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y liquidación del reclamo, demanda, traje o procedimiento (siempre y cuando no pueda liquidar ninguna reclamación, demanda, juicio o procedimiento a menos que la liquidación libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporciona toda la asistencia razonable, a tu cargo. + +### J. Varios + +1. **Ley aplicable** Aceptas que estos Términos del Mercado y tu uso de los Productos de Programador se rigen por la ley de California y cualquier disputa relacionada con los Productos de Programador debe llevarse ante un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. + +2. **No asignable.** GitHub puede asignar o delegar estos Términos del Mercado y/o la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/), total o parcialmente, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos o Declaración de Privacidad del Mercado sin nuestro consentimiento previo por escrito y cualquier asignación no autorizada y delegación por ti es nula. + +3. **Divisibilidad, sin exención y supervivencia.** Si alguna parte de estos Términos del Mercado no es válida o no aplica, esa parte de los Términos del Mercado se interpretará para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. El hecho de que GitHub no ejerza o ejecute cualquier derecho o provisión de estos Términos del Mercado no constituirá una renuncia a dicho derecho o disposición. Nuestros derechos bajo estos Términos del Mercado sobrevivirán a cualquier cancelación de estos Términos del Mercado. + +4. **Sin modificaciones; Acuerdo completo.** Estos Términos del Mercado sólo pueden modificarse mediante una enmienda por escrito firmada por un representante autorizado de GitHub, o por la publicación por GitHub de una versión revisada. Estos Términos del Mercado, junto con la [Declaración de Privacidad de GitHub](/articles/github-privacy-statement/), representan la declaración completa y exclusiva del acuerdo entre usted y nosotros. Estos Términos del Mercado reemplazan cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre tú y GitHub relacionada con el tema de estos términos. + +5. **Encabezados de las secciones.** A lo largo de estos Términos del Mercado, cada sección incluye títulos de los siguientes términos y condiciones. Los títulos de estas secciones no son legalmente vinculantes. + +6. **Licencia para las Políticas de GitHub.** Estos Términos del Mercado están licenciados bajo esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). + +7. **Póngase en contacto con nosotros.** ¿Preguntas sobre las condiciones del mercado? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md b/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md new file mode 100644 index 0000000000000..9729f3b5fd324 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md @@ -0,0 +1,63 @@ +--- +title: Términos y condiciones de la aplicación de código abierto de GitHub +redirect_from: + - /articles/github-open-source-applications-terms-and-conditions +versions: + free-pro-team: '*' +--- + +Estos términos y condiciones de las aplicaciones de código abierto de GitHub ("términos de la aplicación") son un acuerdo legal entre tú (ya sea como individuo o en nombre de una entidad) y GitHub, Inc. sobre el uso de las aplicaciones de GitHub, como GitHub Desktop™ y la documentación asociada ("Software"). Estos Términos de la Aplicación se aplican a la versión ejecutable del Software. El código fuente para el software está disponible por separado y de forma gratuita en los acuerdos de licencia de software de código abierto. Si no estás de acuerdo con todos los términos en los presentes términos de la aplicación, no descargues, instales, uses o copies el software. + +### Conexión a GitHub + +Si configuras el software para que funcione con una o más cuentas en el sitio web GitHub.com o con una instancia de GitHub Enterprise, tu uso del software también se regirá por tus términos de servicio del sitio web GitHub.com aplicables y/o el acuerdo de licencia aplicable a tu instancia de GitHub Enterprise ("términos de GitHub"). + +Cualquier uso del software que viole los Términos de GitHub aplicables también será una violación de estos Términos de la Aplicación. + +### Licencias y avisos de código abierto + +La licencia de código abierto para el Software está incluida en la documentación de "Avisos de Código Abierto" que se incluye con el software. Esa documentación también incluye copias de todas las licencias de código abierto aplicables. + +En la medida en que los términos de las licencias aplicables a los componentes de código abierto requieran que GitHub realice una oferta para proporcionar código fuente en conexión con el software, se hará la presente oferta y puedes ejecutarla poniéndote en contacto con GitHub: https://github.com/contact + +A menos que se acepte lo contrario por escrito con GitHub, tu acuerdo con GitHub siempre incluirá, como mínimo, estos términos de aplicación. Las licencias de software de código abierto para el código fuente del software constituyen acuerdos escritos por separado. En la medida limitada en que las licencias de software de código abierto sustituyan de forma expresa estos términos de aplicación, las licencias de código abierto rigen tu acuerdo con GitHub para el uso del software o componentes específicos incluidos del software. + +### Logotipos de GitHub + +La concesión de licencia incluida con el software no es para las marcas comerciales de GitHub, que incluyen los diseños de logotipos de software. GitHub se reserva todos los derechos de marca comercial y derecho de autor sobre todas las marcas de GitHub. Los logotipos de GitHub incluyen, por ejemplo, los diseños estilizados que incluyen el "logotipo" en el título del archivo en la carpeta "Logotipos". + +Los nombres GitHub, GitHub Desktop, GitHub para Mac, GitHub para Windows, Atom, The Octocat y los logotipos de GitHub relacionados y/o los nombres estilizados son marcas comerciales de GitHub. Aceptas no mostrar o usar estas marcas comerciales de ninguna manera sin el permiso previo por escrito de GitHub, excepto según lo permitido por los logotipos y la política de uso de GitHub: https://github.com/logos. + +### Privacy + +El software puede recopilar información personal. Puedes controlar qué información recopila el software en el panel de configuraciones. Si el software recopila información personal en nombre de GitHub, GitHub procesará esa información de acuerdo con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/). + +### Servicios adicionales + +**Servicios de actualización automática** + +El Software puede incluir un servicio de actualización automática ("Servicio"). Si decides utilizar el servicio o descargas software que habilita automáticamente el servicio, GitHub actualizará automáticamente el software cuando haya una nueva versión disponible. + +**Renuncias y limitaciones de responsabilidad** + +EL SERVICIO SE PROPORCIONA "TAL CUAL" Y NO SE OTORGA NINGUNA GARANTÍA, YA SEA EXPLÍCITA O IMPLÍCITA. TU USO DEL SERVICIO ES A TU PROPIO RIESGO. GitHub no garantiza que (i) el servicio cumplirá con tus requisitos específicos; (II) el servicio es totalmente compatible con cualquier plataforma en particular; (III) tu uso del servicio se ininterrumpirá, oportunamente, de manera segura o libre de errores; (IV) los resultados que se pueden obtener del uso del servicio serán exactos o confiables; (v) la calidad de cualquier producto, servicio, información u otro material adquirido u obtenido por ti a través del servicio cumplirá con tus expectativas; o (VI) se corregirán cualquier error en el servicio. + +EXPRESAMENTE COMPRENDES Y ACEPTAS QUE GITHUB NO SERÁ RESPONSABLE DE NINGÚN DAÑO DIRECTO, INDIRECTO, INCIDENTAL, ESPECIAL, CONSECUENTE O EJEMPLARES, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR PÉRDIDA DE BENEFICIOS, BUENA VOLUNTAD, USO, DATOS U OTRAS PÉRDIDAS INTANGIBLES (INCLUSO SI SE HA ADVERTIDO A GITHUB SOBRE LA POSIBILIDAD DE DICHOS DAÑOS) RELACIONADOS CON EL SERVICIO, incluyendo, por ejemplo: (i) el uso o la incapacidad de usar el servicio; (II) el costo de la adquisición de bienes y servicios sustitutivos resultantes de cualquier mercancía, dato, información o servicios adquiridos u obtenidos o mensajes recibidos o transacciones concertados a través o desde del servicio; (III) acceso no autorizado o alteración de tus transmisiones o datos; (IV) declaraciones o conductas de cualquier tercero en el servicio; (v) o cualquier otro asunto relacionado con el servicio. + +GitHub se reserva el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, de manera temporal o permanente, el servicio (o cualquier parte del mismo) con o sin aviso. GitHub no será responsable ante ti ni ante ningún tercero por cualquier cambio de precio, suspensión o interrupción del servicio. + +### Varios + +1. Ninguna renuncia. La incapacidad de GitHub para ejercer o hacer cumplir cualquier derecho o disposición de estos términos de la aplicación no constituirá una renuncia a dicho derecho o disposición. + +2. Acuerdo completo. Estos términos de la aplicación, junto con cualquier aviso de privacidad aplicable, constituyen el acuerdo completo entre tú y GitHub y rigen tu uso del software, reemplazando cualquier acuerdo anterior entre tú y GitHub (incluyendo, entre otras, cualquier versión anterior de los términos de la aplicación). + +3. Governing Law. Aceptas que estos términos de la aplicación y tu uso del software están regidos por la ley de California y cualquier disputa relacionada con el software debe ser llevada a un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. + +4. Paquetes de terceros. El software admite "paquetes" de terceros que pueden modificar, agregar, eliminar o alterar la funcionalidad del software. Estos paquetes no están cubiertos por los presentes términos de la aplicación y pueden incluir su propia licencia que rige tu uso de ese paquete en particular. + +5. Sin modificaciones; contrato completo. Estos términos de la aplicación solo se pueden modificar mediante una enmienda por escrito firmada por un representante autorizado de GitHub, o mediante la publicación por parte de GitHub de una versión revisada. Estos términos de la aplicación, junto con cualquier licencia y aviso de código abierto aplicable y la declaración de privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tú y nosotros. Estos términos de la aplicación sustituyen cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre tú y GitHub relacionada con el tema de estos términos. + +6. Licencia a políticas de GitHub. Estos términos de aplicación están licenciados bajo esta [Licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). + +7. Contáctanos. ¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-ES/content/github/site-policy/github-pre-release-program.md b/translations/es-ES/content/github/site-policy/github-pre-release-program.md new file mode 100644 index 0000000000000..e249c7a9de460 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-pre-release-program.md @@ -0,0 +1,95 @@ +--- +title: Programa de prelanzamiento de GitHub +redirect_from: + - /articles/github-pre-release-program +versions: + free-pro-team: '*' +--- + +¡Gracias por registrarte para participar en los programas de prelanzamiento de GitHub! Como miembro de confianza de nuestra comunidad, tu opinión sobre las características nuevas y experimentales es importante para nosotros. Con el fin de compartir con ustedes estos nuevos productos y servicios, muchos de los cuales siguen siendo secretos y en desarrollo, necesitaremos que acepten un conjunto especial de términos. Bienvenido al acuerdo del programa de prelanzamiento ("Acuerdo"). + +El presente acuerdo es un acuerdo legal entre tú ("tú", "tu") y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer el presente acuerdo detenidamente - solo puedes ser un participante del programa de prelanzamiento si aceptas todos los términos del presente acuerdo. Al hacer clic en el botón "registrarse para el programa de prelanzamiento de GitHub", o al participar como participante del programa de pre-lanzamiento de cualquier manera - por ejemplo, al ingresar a información acerca de los productos o servicios de GitHub que aún no están disponibles para el público en general, estás aceptando regirte por todos los términos del presente acuerdo. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS. SI NO TIENES ESA AUTORIDAD, O SI NO ESTÁS DE ACUERDO CON LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO, NO DEBES HACER CLIC EN EL BOTÓN "REGISTRARSE PARA EL PROGRAMA DE PRELANZAMIENTO DE GITHUB" Y NO PUEDES SER UN PARTICIPANTE DEL PROGRAMA DE PRELANZAMIENTO. SI ERES UNA EMPRESA U OTRA ENTIDAD LEGAL, REPRESENTAS QUE LA PERSONA QUE HACE CLIC EN EL BOTÓN "REGISTRARSE PARA EL PROGRAMA DE PRELANZAMIENTO DE GITHUB" TIENE LA AUTORIDAD PARA VINCULARTE CON EL PRESENTE ACUERDO. + +### 1. Se aplicarán los términos de uso de GitHub.com o el acuerdo de licencia de software de GitHub Enterprise + + Debes tener una cuenta en GitHub.com o en una instancia con licencia de GitHub Enterprise para ser un participante del programa de prelanzamiento. Además de los términos de servicio de GitHub.com o tu acuerdo de licencia de GitHub Enterprise aplicable, según corresponda, (los "términos generalmente aplicables"), al hacer clic en el botón "registrarse para el programa de prelanzamiento de GitHub", también aceptas regirte por el presente acuerdo, de manera que ambos acuerdos se apliquen a ti simultáneamente. En el caso de un conflicto directo entre este Acuerdo y los Términos Generalmente Aplicables, tus Términos Generalmente Aplicables controlarán, excepto con respecto a cualquier uso de materiales de preliberación, en cuyo caso el presente Contrato controlará. + +### 2. Confidencialidad; acceso a los materiales de prelanzamiento + + Como participante del programa de prelanzamiento, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. + + Aceptas que toda información no pública que te proporcionemos, o a la que puedas tener acceso como participante del programa de prelanzamiento, se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas utilizar esa información confidencial únicamente para el propósito expreso de las pruebas y la evaluación de los materiales de prelanzamiento (el "propósito") y no para ningún otro propósito. Debes usar el mismo grado de cuidado que usarías con tu información confidencial, pero no menos de las precauciones razonables para evitar cualquier uso no autorizado, divulgación, publicación o diseminación de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero que no sea tus empleados y contratistas y posteriormente solo en la medida en que: (i) necesiten conocer la información confidencial para el propósito; (II) les haces conocer la naturaleza confidencial de la información confidencial; (III) sigues siendo responsable de los actos y omisiones de dichos empleados y contratistas; y (IV) no prohibimos o restringimos dicha divulgación. + + Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. + + Las obligaciones de la presente sección 2 no se aplicarán a la información que puedas probar que: (i) estuvo generalmente disponible para el público antes de que te la revelaramos; (II) estuvo generalmente disponible para el público después de que te la revelamos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) conocías antes de que te la revelaramos; (IV) te fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. Si te damos acceso a cualquier software, software de prelanzamiento o documentación o materiales relacionados, que pueden incluir videos u otras formas de contenido ("materiales de prelanzamiento"), entonces, sujeto a tu cumplimiento con los términos y condiciones del presente acuerdo y en los términos generalmente aplicables, por la presente te otorgamos un derecho y una licencia no exclusivos, intransferibles y revocable para usar los materiales de prelanzamiento durante la vigencia del presente acuerdo, exclusivamente para el propósito. Si los materiales de prelanzamiento están acompañados de un acuerdo de licencia separado, aceptas que se aplicarán el acuerdo de licencia por separado (además de cualquier disposición más restrictiva contenida en el presente acuerdo o tus términos de aplicación general). Aceptas no descompilar, hacer ingeniería inversa, desmontar o reducir de cualquier otra manera los materiales de prelanzamiento a una forma perceptible por el hombre y prometes no modificar, establecer redes, alquilar, arrendar, transmitir, vender o prestar los materiales de prelanzamiento, en su totalidad o en parte. Comprendes que no estamos obligados a proporcionarte ningún material de prelanzamiento, a proporcionarte actualizaciones, mejoras o correcciones en los materiales de prelanzamiento, o a notificarte de los cambios que realicemos a nuestros productos y servicios, ahora o en el futuro. + +### 3. Plazo y terminación + + El presente acuerdo comienza en la fecha en que haces clic en "acordar", y continúa durante un período de un (1) año. El presente acuerdo se renovará automáticamente por términos sucesivos de un año, a menos que cualquiera de las partes le dé un aviso por escrito al menos treinta (30) días antes del vencimiento del plazo actual que desea terminar, o una parte la terminará antes de acuerdo con lo dispuesto en la presente sección 3. + + Tanto tú como GitHub pueden rescindir el presente acuerdo por cualquier motivo, sin causa, después de treinta (30) días de aviso previo por escrito a la otra. El presente acuerdo terminará de inmediato, sin la obligación de aviso, si incumple cualquier término del presente acuerdo, los términos del programa o los TOS. + + Los derechos y obligaciones de las Secciones 1, 2 y 4 hasta 17 sobrevivirán a la rescisión o caducidad del presente Contrato. Tras la terminación o la expiración del presente acuerdo, todos los derechos y las licencias que te otorgaron en el presente acuerdo dejarán de existir de inmediato, regresarás (o, a petición nuestra, destruirás) toda nuestra información confidencial y cualquier copia (incluidas las copias electrónicas) que estén en tu posesión o control y certificaras por escrito que has cumplido con estos requisitos. + +### 4. Garantías y limitaciones de responsabilidades + + Nos garantizas que: (i) tienes la autoridad para ejecutar el presente acuerdo y para cumplir con sus obligaciones; (II) no harás declaraciones o representaciones falsas o engañosas con respecto a GitHub o a nuestros productos y servicios; y (III) no tomarás ninguna obligación o responsabilidad, ni hará ninguna representación, garantía o endoso a nadie en nuestro nombre (incluidos, entre otros, alguno de nuestros productos o servicios). + + COMPRENDES Y ACEPTAS QUE CUALQUIER MATERIAL O INFORMACIÓN QUE TE DEMOS O A LA QUE TENGAS ACCESO CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO (INCLUYENDO, ENTRE OTROS, CUALQUIER INFORMACIÓN CONFIDENCIAL O MATERIALES DE PRELANZAMIENTO) SE PROPORCIONAN "TAL CUAL", Y SIN GARANTÍA DE NINGÚN TIPO, EXPRESA O IMPLÍCITA. RENUNCIAMOS ESPECÍFICAMENTE A TODAS LAS GARANTÍAS O CONDICIONES IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN PROPÓSITO Y NO INFRACCIÓN PARTICULAR. + +### 5. Indemnización + + Te daremos acceso a muchos productos, servicios e información de prelanzamiento útiles, como los materiales de prelanzamiento y existen formas en las que puedes usarlos de manera inadecuada que podrían causarnos daño. Con eso en mente y dado que no podemos controlar las formas en las que usas lo que te proporcionamos, aceptas que nos indemnizarás, defenderás y eximirás de toda responsabilidad de cualquier reclamación que pueda surgir por debajo o fuera de tu participación en cualquier programa de prelanzamiento; tu negligencia o mala conducta intencional; cualquier tergiversación que realices con respecto a nosotros o a nuestros productos o servicios; o tu violación de cualquier parte del presente acuerdo. + +### 6. Limitación de responsabilidad + + EN NINGÚN CASO SEREMOS RESPONSABLES ANTE TI O ANTE NINGÚN TERCERO POR NINGÚN DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, CONSECUENTE, EJEMPLAR O PUNITIVO, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR DATOS PERDIDOS, PÉRDIDAS DE BENEFICIOS O COSTOS DE ADQUISICIÓN DE BIENES O SERVICIOS SUSTITUTIVOS, SIN PERJUICIO DE LO QUE SE CAUSE Y BAJO CUALQUIER TEORÍA DE RESPONSABILIDAD, YA SEA POR CONTRATO, AGRAVIO (INCLUYENDO LA RESPONSABILIDAD DE PRODUCTOS , RESPONSABILIDAD ESTRICTA Y NEGLIGENCIA), O CUALQUIER OTRA TEORÍA, Y SI SABÍAMOS O NO O DEBERÍAMOS HABER SABIDO SOBRE LA POSIBILIDAD DE DICHOS DAÑOS. EN NINGÚN CASO NUESTRA RESPONSABILIDAD TOTAL ANTE TI DERIVADA DEL PRESENTE ACUERDO O RELACIONADA CON ÉL POR CUALQUIER CAUSA, E INDEPENDIENTEMENTE DE LA FORMA DE ACCIÓN, YA SEA POR CONTRATO O POR AGRAVIO, EXCEDE EL MAYOR DE (I) LOS MONTOS QUE REALMENTE PAGÓ CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO; O (II) 500 DÓLARES ($500). LAS LIMITACIONES ANTERIORES SE APLICARÁN A PESAR DEL FRACASO DEL PROPÓSITO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA QUE SE INDIQUE EN EL PRESENTE ACUERDO. + +### 7. Control de exportación + + No se te permite exportar o volver a exportar ninguna información confidencial, excepto según lo autorizado por la ley de los Estados Unidos y las leyes de la jurisdicción en la que se obtuvo la información confidencial. Particularmente, no se te permite exportar o re-exportar nuestra información confidencial a ningun país embargado por los EE.UU., a ninguna de las listas de Nacionales Especialmente Designados del Departamento de Tesorería de los EE.UU, ni a alguien de La Lista de Entidades o Lista de Personas Denegadas por el Departamento de Comenrcio de los EE.UU. Al participar en un programa de prelanzamiento o recibir alguna de nuestra información confidencial, declaras y garantizas que no estás ubicado en ningún país de este tipo o en ninguna lista. + +### 8. Derechos de propiedad + + Aceptas que GitHub y sus licenciantes son propietarios de todos los derechos, títulos e interés en los materiales de prelanzamiento y todos los demás productos y servicios de GitHub; toda la información y los datos relativos a sus configuraciones y combinaciones; y todas las modificaciones y obras derivadas de cualquiera de las anteriores. Aceptas no eliminar, alterar, cubrir o ofuscar ningún derecho de autor u otros avisos de derechos de propiedad que colocamos o insertamos en los materiales de prelanzamiento o cualquier otro producto y servicio de GitHub. + +### 9. Usuarios gubernamentales + + Si eres una entidad gubernamental, esta sección aplica para ti. Cierta parte de nuestra información confidencial puede considerarse "artículos comerciales", ya que ese término se define en 48 C. § 2,101, que consiste en "software informático comercial" y "documentación del software informático comercial", ya que dichos términos se usan en 48 C. § 12,212 o 48 C. § 227.7202, según corresponda. Consistente con 48 C. § 12,212 o 48 C. § 227.7202-1 a 227.7202-4, según corresponda, la documentación del software informático comercial y del software informático comercial se licencia para los usuarios finales del gobierno de los EE. UU. (a) únicamente como elementos comerciales y (b) con solo aquellos derechos que se conceden a todos los demás usuarios finales conforme a los términos y condiciones del presente documento. GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107. + +### 10. Desarrollo independiente + + Ninguna parte del presente acuerdo perjudicará nuestro derecho a desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que puedan competir con tus productos. + +### 11. Privacy + + Como parte del desarrollo y la evaluación de nuestros programas de evaluación, GitHub necesita recopilar información sobre cómo tu uso de los servicios y los programas y cómo GitHub puede mejorarlos. Al aceptar participar en los programas de prelanzamiento de GitHub, aceptas que has leído y has dado tu consentimiento a nuestra [Política de privacidad completa](/articles/github-privacy-statement/). + + Es posible que recopilemos cierta información personal adicional de los participantes en los programas de prelanzamiento. Por ejemplo, es posible que invites a los participantes a enviarnos comentarios (como se explica en la sección 12). Podríamos hacer preguntas acerca de las experiencias de cada usuario, la familiaridad con el producto o la información demográfica. Utilizamos esta información para mejorar nuestros productos y servicios y no las vendemos a terceros o anunciantes. Puedes declinar enviarnos tus comentarios, declinar la respuesta a preguntas específicas o contactarnos para eliminar o alterar la información que hemos recopilado sobre ti. + + Los servidores de GitHub se encuentran en los Estados Unidos. Procesamos y controlamos tus datos en los Estados Unidos. Sin embargo, solo tú eres responsable de determinar qué datos personales nos envías. Consulta nuestra política de privacidad para obtener más información. + +### 12. Comentarios + + Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como un participante del programa de pre-lanzamiento nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación. + +### 13. Contratistas independientes + + Las partes del presente acuerdo son contratistas independientes. Ninguna de las partes se considerará como un empleado, agente, socio, franquiciador, franquiciada o representante legal de la otra para ningún propósito y ninguna de las partes tendrá ningún derecho, poder o autoridad para crear ninguna obligación o responsabilidad en nombre de la otra. + +### 14. Asignación + + No puedes ceder o transferir el presente acuerdo o ninguno de tus derechos en virtud del mismo, en su totalidad o en parte, por el funcionamiento de la ley o de cualquier otra manera, sin nuestro consentimiento previo por escrito. + +### 15. Legislación aplicable y jurisdicción + + El presente acuerdo se interpretará y entenderá de acuerdo con las leyes del estado de California, sin tener en cuenta los principios de conflicto de leyes. Todas las disputas que surjan del presente Acuerdo estarán sujetas a la jurisdicción exclusiva del estado y los tribunales federales ubicados en el Condado de San Francisco, California y cada una de las partes consiente a la jurisdicción personal en dicho lugar. + +### 16. Modificaciones; renuncias; inexistencia de terceros beneficiarios + + Es posible que el presente acuerdo no se cambie, excepto mediante un escrito firmado por ambas partes. Cualquier renuncia a las disposiciones del presente acuerdo o de los derechos o recursos de una parte conforme a lo dispuesto en el presente acuerdo debe ser por escrito para que sea efectiva. Si se encuentra que algún término, condición o disposición del presente acuerdo no es válido o no ejecutable, los términos restantes seguirán siendo válidos y exigibles en la medida en que lo permita la ley. Cada uno de nosotros acepta expresamente que no hay terceros beneficiarios del presente acuerdo. + +### 17. Acuerdo completo + + El presente acuerdo y los términos generalmente aplicables contienen el acuerdo completo de las partes con respecto al tema y sustituyen todas las comunicaciones, representaciones, entendimientos y acuerdos previos, ya sean escritos u orales. Los términos o condiciones de cualquiera de tus pedidos de compras, confirmacones u otros documentos que nos envíes en relación con el presente acuerdo serán nulos y sin efecto. diff --git a/translations/es-ES/content/github/site-policy/github-privacy-statement.md b/translations/es-ES/content/github/site-policy/github-privacy-statement.md new file mode 100644 index 0000000000000..5dadba7ee42b4 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-privacy-statement.md @@ -0,0 +1,339 @@ +--- +title: GitHub Privacy Statement +redirect_from: + - /privacidad/ + - /privacy-policy/ + - /privacy-statement/ + - /github-privacy-policy/ + - /articles/github-privacy-policy/ + - /articles/github-privacy-statement/ +versions: + free-pro-team: '*' +--- + +Effective date: December 19, 2020 + +Gracias por confiar a GitHub Inc. (“GitHub”, “nosotros”) tu código fuente, tus proyectos y tu información personal. Mantener tu información privada es una responsabilidad importante, y queremos que sepas cómo lo hacemos. + +Todos los términos en mayúsculas tienen su definición en las [Condiciones de Servicio de GitHub](/github/site-policy/github-terms-of-service) a menos de que se indique lo contrario. + + +### La versión corta + +Utilizamos tu información personal como lo describe la presente Declaración de Privacidad. Sin importar quién seas, dónde vives, o cuál sea tu nacionalidad, proporcionames el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo, sin importar su país de orígen o su ubicación. + +Por supuesto, la versión corta y el Resumen que aparecen a continuación no informan todos los detalles, por lo tanto, sigue leyendo para acceder a ellos. + +### Resumen + +| Sección | ¿Qué puedes encontrar allí? | +| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [Qué información recopila GitHub](#what-information-github-collects) | GitHub recopila información directamente a partir de tu registro, tus pagos, tus transacciones y del perfil del usuario. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. Puede que GitHub también recopile Información personal del usuario a partir de terceros. Solo recopilamos la mínima cantidad de información personal necesaria a través de ti, a menos que decidas proporcionar más. | +| [Qué información GitHub _no_ recopila](#what-information-github-does-not-collect) | No recopilamos intencionalmente información de niños menores de 13 años y no recopilamos [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/). | +| [Cómo utiliza GitHub tu información](#how-github-uses-your-information) | En esta sección, describimos las formas en las que utilizamos tu información, incluyendo el proporcionarte el Servicio, comunicarnos contigo, para propósitos de seguridad y cumplimiento, y para mejorar nuestro Servicio. También describimos la base legal sobre la cual procesamos tu información personal, cuando se exige legalmente. | +| [Cómo compartimos la información que recopilamos](#how-we-share-the-information-we-collect) | Puede que compartamos tu información con terceros en una de las siguientes circunstancias: con tu consentimiento, con nuestros proveedores de servicio, por motivos de seguridad, para cumplir con nuestras obligaciones legales o cuando exista un cambio de control o venta de las entidades corporativas o unidades de negocios. En GitHub, no vendemos tu información personal y no alojamos publicidad. Puedes consultar una lista de los proveedores de servicio que acceden a tu información. | +| [Otra información importante](#other-important-information) | Proporcionamos más información específica sobre los contenidos del repositorio, la información pública y las Organizaciones de GitHub. | +| [Servicios adicionales](#additional-services) | Proporcionamos información sobre las ofertas de servicio adicionales, incluso aplicaciones de terceros, Páginas de GitHub y aplicaciones de GitHub. | +| [Cómo puedes acceder y controlar la información que recopilamos](#how-you-can-access-and-control-the-information-we-collect) | Proporcionamos formas para que accedas, modifiques o elimines tu información personal. | +| [Uso de cookies y seguimiento](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. Ofrecemos una página que hace que esto sea muy transparente. Consulta esta sección para obtener más información. | +| [Cómo asegura GitHub tu información](#how-github-secures-your-information) | Tomamos todas las medidas razonablemente necesarias para proteger la confidencialidad, integridad y disponibilidad de tu información personal en GitHub y para proteger la resistencia de nuestros servidores. | +| [Prácticas de privacidad mundiales de GitHub](#githubs-global-privacy-practices) | Proporcionamos el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo entero. | +| [Cómo nos comunicamos contigo](#how-we-communicate-with-you) | Nos comunicamos contigo por correo electrónico. Puedes controlar la manera en que te contactamos en las configuraciones de la cuenta o poniéndote en contacto con nosotros. | +| [Resolver reclamos](#resolving-complaints) | En el caso improbable de que no podamos resolver una inquietud sobre la privacidad de forma rápida y exhaustiva, proporcionaremos un medio de resolución por medio de una disputa. | +| [Cambios en tu Declaración de privacidad](#changes-to-our-privacy-statement) | Te notificamos los cambios importantes en esta Declaración de privacidad 30 días antes de que cualquier cambio entre en vigencia. Puedes rastrear los cambios en nuestro repositorio de Políticas del sitio. | +| [Licencia](#license) | La presente Declaración de privacidad está autorizada por la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | +| [Contactarse con GitHub](#contacting-github) | Siéntete libre de contactarnos si tienes preguntas acerca de nuestra Declaración de privacidad. | +| [Traducciones](#translations) | Proporcionamos enlaces a algunas traducciones de la Declaración de privacidad. | + +## GitHub Privacy Statement + +### Qué información recopila GitHub + +La "**Información personal del usuario**" es cualquier información acerca de alguno de nuestros Usuarios que podría, de manera independiente o junto con otra información, identificarlo individualmente, o que está vinculada o conectada de cualquier otra forma con él. Información como un nombre de usuario y contraseña, una dirección de correo electrónico, un nombre real, una dirección de Protocolo de Internet (IP) y una fotografía son ejemplos de "Información personal del usuario". + +La Información personal del usuario no incluye información agregada, información de carácter no personal que no identifica a un Usuario o que no se puede vincular o conectar de manera razonable con él. Podemos utilizar dicha información agregada que no identifica de manera personal a un usuario con motivos de investigación y para operar, analizar y optimizar nuestro Sitio web y el Servicio. + +#### Información que los usuarios proporcionan directamente a GitHub + +##### Información de registro +Necesitamos cierta información básica al momento de creación de la cuenta. Cuando creas tu propio nombre de usuario y contraseña, te solicitamos una dirección de correo electrónico válida. + +##### Información de Pago +Si te registras para una Cuenta paga, envías fondos a través del Programa de patrocinadores de GitHub o compras una aplicación en el Mercado GitHub, recopilamos tu nombre completo y la información de la tarjeta de crédito o la información de PayPal. Ten en cuenta que GitHub no procesa ni almacena tu información de tarjeta de crédito o información de PayPal, pero sí lo hace nuestro procesador de pago subcontratado. + +Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. Si recabas fondos a través del [Programa de Patrocinadores de GitHub](https://github.com/sponsors), necesitamos algo de [información adicional](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) mediante el proceso de registro para que participes y recibas los fondos a través de estos servicios y para propósitos de cumplimiento. + +##### Información de perfil +Puedes decidir proporcionarnos más información para tu Perfil de cuenta, como tu nombre completo, un avatar que puede incluir una fotografía, tu biografía, tu ubicación, tu empresa y una URL a un sitio web de terceros. Esta información puede incluir Información personal del usuario. Ten en cuenta que tu información de perfil puede ser visible para otros Usuarios de nuestro Servicio. + +#### Información que GitHub recopila automáticamente a partir del uso del Servicio + +##### Información transaccional +Si tienes una Cuenta paga con nosotros, vendes una aplicación detallada en el [Mercado GitHub](https://github.com/marketplace) o recaudas fondos a través del [Programa de patrocinadores de GitHub](https://github.com/sponsors), automáticamente recopilamos determinada información acerca de tus transacciones en el Servicio, como la fecha, la hora y el monto cobrado. + +##### Información de uso +Si accedes a nuestro Servicio o Sitio web, automáticamente recopilamos la misma información básica que recopila la mayoría de los servicios, sujeto a tu consentimiento cuando resulte necesario. Esto incluye información acerca de cómo utilizas el Servicio, por ejemplo, las páginas que miras, el sitio referido, tu dirección IP e información de sesión, y la fecha y hora de cada solicitud. Recopilamos esta información de todos los visitantes del Sitio web, tengan o no una Cuenta. Esta información puede incluir Información personal del usuario. + +##### Cookies +As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service. + +##### Información de dispositivo +Puede que recopilemos determinada información acerca de tu dispositivo, como la dirección IP, el navegador o información de la aplicación del cliente, preferencias de idioma, sistema operativo y versión de la aplicación, tipo e ID del dispositivo y modelo y fabricante del dispositivo. Esta información puede incluir Información personal del usuario. + +#### Información que recopilamos de terceros + +GitHub puede recopilar Información personal del usuario a partir de terceros. Por ejemplo, esto puede ocurrir si inicias sesión para capacitarte o recibir información acerca de GitHub de parte de alguno de nuestros proveedores, socios o subsidiarias. GitHub no compra Información personal del usuario a agentes de datos de terceros. + +### Qué información no recopila GitHub + +No recopilamos de manera intencional “**[Información personal sensible](https://gdpr-info.eu/art-9-gdpr/)**”, como datos personales que revelan origen racial o étnico, opiniones políticas, creencias religiosas o filosóficas o afiliación sindical, y tampoco procesamos datos genéticos ni datos biométricos con el único fin de identificar a una persona física, datos del estado de salud o datos sobre la vida sexual o la orientación sexual de una persona física. Si decides almacenar alguna Información personal en tus servidores, eres responsable de cumplir con cualquier control regulatorio al respecto de esos datos. + +Si eres un niño menor de 13 años, no puedes tener una Cuenta en GitHub. GitHub no recopila intencionalmente información de niños menores de 13 años ni dirige ninguno de nuestros contenidos de manera específica a ellos. Si sabemos o tenemos motivos para sospechar que eres un Usuario menor de 13 años, tendremos que cerrar tu Cuenta. No queremos desalentarte de que aprendas nuestro código, pero esas son las reglas. Por favor, consulta nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service) para la información acerca de la cancelación de la cuenta. Puede que los diferentes países tengan diferentes límites de edad mínimos. Si estás por debajo de la edad mínima para brindar consentimiento para la recopilación de datos en tu país, no puedes tener una Cuenta en GitHub. + +No recopilamos de manera intencional la Información personal del usuario que está **almacenada en tus repositorios** u otros ingresos de contenido de forma libre. Toda información personal dentro del repositorio de un usuario es responsabilidad del propietario del repositorio. + +### Cómo utiliza GitHub tu información + +- Podemos utilizar tu información con los siguientes fines: +- Utilizamos tu [Información de registro](#registration-information) para crear tu cuenta y para proporcionarte el Servicio. +- Utilizamos tu [Información de pago](#payment-information) para proporcionarte el servicio de Cuenta paga, el servicio de Mercado, el Programa de patrocinadores o cualquier otro servicio pago de GitHub que solicites. +- Utilizamos tu Información personal del usuario, específicamente tu nombre de usuario, para identificarte en GitHub. +- Utilizamos tu [Información del perfil](#profile-information) para completar tu perfil de Cuenta y para compartir ese perfil con otros usuarios, si nos pides que lo hagamos. +- Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Consulta nuestra sección en [comunicación por correo electrónico](#how-we-communicate-with-you) para obtener más información. +- Utilizamos Información personal del usuario para responder a las solicitudes de soporte técnico. +- Utilizamos Información personal del usuario y otros datos para hacerte recomendaciones, por ejemplo, sugerir proyectos que puedes querer seguir o con los que puedes querer contribuir. Aprendemos de tu comportamiento público en GitHub, por ejemplo, los proyectos a los que les pones estrellas, para determinar tus intereses de codificación y recomendamos proyectos similares. Estas recomendaciones son decisiones automáticas, pero no tienen un impacto legal en tus derechos. +- Podemos utilizar Información personal del usuario para invitarte a formar parte de las encuestas, los programas beta u otros proyectos de investigación, sujeto a tu consentimiento cuando resulte necesario. +- Utilizamos [Información de uso](#usage-information) e [Información del dispositivo](#device-information) para comprender mejor cómo utilizan GitHub nuestros Usuarios y para mejorar nuestro Sitio web y el Servicio. +- Si es necesario, podemos utilizar tu Información personal del usuario por motivos de seguridad o para investigar posibles fraudes o intentos de dañar a GitHub o a nuestros Usuarios. +- Podríamos utilizar tu Información personal de usuario para cumplir con nuestras obligaciones legales, proteger nuestra propiedad intelectual y hacer cumplir nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service). +- Restringimos nuestro uso de tu Información personal del Usuario para los fines detallados en esta Declaración de privacidad. Si necesitamos utilizar tu Información personal del usuario para otros fines, te pediremos permiso primero. Siempre puedes ver qué información tenemos, cómo la estamos utilizando y qué permisos nos has dado en tu [perfil de usuario](https://github.com/settings/admin). + +#### Nuestras bases legales para el procesamiento de información + +En la medida que el procesamiento de tu Información personal del usuario esté sujeto a determinadas normas internacionales (incluido, entre otros, el Reglamento General de Protección de Datos [RGPD]) de la Unión Europea, se le exige a GitHub que te notifique acerca de la base legal sobre la cual procesamos la Información personal del usuario. GitHub procesa la Información personal del usuario sobre las siguientes bases legales: + +- Ejecución del contrato: + * Cuando creas una Cuenta de GitHub, proporcionas tu [Información de registro](#registration-information). Solicitamos esta información para que celebres el acuerdo de Términos del Servicio con nosotros y procesamos esa información sobre la base de la ejecución de ese contrato. También procesamos tu nombre de usuario y dirección de correo electrónico sobre otras bases legales, como se describe a continuación. + * Si tienes una Cuenta paga con nosotros, recopilamos y procesamos más [Información de pago](#payment-information) sobre la base de la ejecución de ese contrato. + * Cuando compras o vendes una aplicación listada en nuestro Marketplace o, cuando envías o recibes fondos a través del Programa GitHub Sponsors, procesamos la [Información de pago](#payment-information) y elementos adicionales para realizar el contrato que se aplica a esos servicios. +- Consentimiento: + * Dependemos de tu consentimiento para utilizar tu Información personal del usuario en las siguientes circunstancias: cuando completas la información en tu [perfil de usuario](https://github.com/settings/admin); cuando decides participar en una capacitación de GitHub, proyecto de investigación, programa beta o encuesta; y con fines de marketing cuando corresponda. Toda esta Información personal del Usuario es completamente opcional, y tienes la capacidad de acceder a ella, modificarla y eliminarla en cualquier momento. Aunque no puedes eliminar tu dirección de correo electrónico por completo, puedes volverlo privado. Puedes retirar tu consentimiento en cualquier momento. +- Intereses legítimos: + * En general, el recordatorio del procesamiento de Información personal del usuario que hacemos es necesario con fines de nuestro legítimo interés, por ejemplo, con fines de cumplimiento legal, fines de seguridad o para mantener la permanente confidencialidad, integridad, disponibilidad y resistencia de los sistemas, el sitio web y el Servicio de GitHub. +- Si quieres solicitar la eliminación de datos que procesamos sobre la base del consentimiento u objetar el procesamiento de la información personal que hacemos, utiliza nuestro [Formulario de contacto sobre Privacidad](https://support.github.com/contact/privacy). + +### Cómo compartimos la información que recopilamos + +Podemos compartir tu Información personal del usuario con terceros en alguna de las siguientes circunstancias: + +#### Con tu consentimiento +Compartimos tu Información Personal del Usuario, si lo consientes, después de dejarte saber qué información será compartida, con quién y por qué. Por ejemplo, si compras una aplicación detallada en nuestro Mercado, compartimos tu nombre de usuario para permitirle al Programador de la aplicación que te proporcione los servicios. Asimismo, te puedes dirigir a nosotros a través de tus acciones en GitHub para compartir tu Información personal del usuario. Por ejemplo, si te unes a una Organización, indicas tu intención de proporcionarle al usuario de la Organización la capacidad de ver tu actividad en el registro de acceso de la Organización. + +#### Con proveedores de servicios +Compartimos información personal del usuario con un número limitado de proveedores de servicios que la procesan en nuestro nombre para proporcionar o mejorar nuestro servicio, y quienes han aceptado restricciones de privacidad similares a las de nuestra Declaración de Privacidad firmando acuerdos de protección de datos o haciendo compromisos similares. Nuestros proveedores de servicio realizan el procesamiento de pagos, la emisión de tickets de soporte técnico del cliente, la transmisión de datos de red, la seguridad y otros servicios similares. Mientras GitHub procesa toda la Información Personal del Usuario en los Estados Unidos, nuestros proveedores de servicios pueden procesar datos fuera de los Estados Unidos o de la Unión Europea. Si te gustaría saber quiénes son nuestros proveedores de servicios, por favor consulta nuestra página sobre nuestros [Subprocesadores](/github/site-policy/github-subprocessors-and-cookies). + +#### Con fines de seguridad +Si eres un miembro de una organización, GitHub puede compartir tu nombre de usuario, [Información de Uso](#usage-information), e [Información de Dispositivo](#device-information) asociadas con dicha organización con un propietario y/o administrador de la misma al punto en que tal información se proporcione únicamente para investigar o responder a un incidente de seguridad que afecte o ponga en riesgo la seguridad de esta organización en particular. + +#### Para divulgación legal +GitHub se esfuerza por conseguir transparencia en el cumplimiento de los procesos legales y las obligaciones legales. A menos que no lo permita la ley o una orden judicial, o en circunstancias únicas y apremiantes, hacemos un esfuerzo razonable para notificarles a los usuarios cualquier divulgación obligatoria o exigida de su información personal. Si así se requiere, GitHub puede divulgar Información personal del usuario u otra información que recopilamos acerca de ti para cumplir con la ley y responder una citación válida, orden judicial, orden de allanamiento u orden gubernamental similar, o cuando consideremos de buena fe que la divulgación es necesaria para cumplir con nuestras obligaciones legales, para proteger nuestra propiedad o nuestros derechos, los de terceros o los del público en general. + +Para obtener más información acerca de la divulgación en respuesta a solicitudes legales, consulta nuestros [Lineamientos para las Solicitudes Legales de Datos de Usuario](/github/site-policy/guidelines-for-legal-requests-of-user-data). + +#### Cambios por control o venta +Podemos compartir Información Personal del Usuario si estamos involucrados en una fusión, venta o adquisición de entidades corporativas o unidades de negocio. Si ocurre cualquier cambio de propiedad, nos aseguraremos de que sea conforme a los términos que preservan la confidencialidad de la Información personal del usuario y, antes de hacer cualquier transferencia de tu Información personal del usuario, lo notificaremos en nuestro Sitio web o por correo electrónico. La organización que reciba alguna Información personal del usuario tendrá que respetar cualquier compromiso que hayamos asumido en nuestra Declaración de privacidad o Términos del Servicio. + +#### Información agregada y sin indentificación personal +Compartimos cierta información agregada y no identificativa personal con otros acerca de cómo nuestros usuarios, de forma colectiva, utilice GitHub, o cómo nuestros usuarios responden a nuestras otras ofertas, tales como nuestras conferencias o eventos. + +**No** vendemos tu Información personal del usuario con fines monetarios o en función de consideraciones de otro tipo. + +Tenga en cuenta: La Ley de Privacidad del Consumidor de California de 2018 (“CCPA”) les exige a las empresas que expliciten en su política de seguridad si divulgan o no información personal a cambio de retribuciones monetarias u otras consideraciones de valor. Si bien la CCPA solo cubre a los residentes de California, extenderemos voluntariamente a _todos_ nuestros usuarios los derechos nucleares de ésta para que las personas controlen sus datos, y no solamente a los residentes de California. Puedes conocer más acerca de la CCPA y de cómo cumplimos con sus disposiciones [aquí](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). + +### Contenidos del repositorio + +#### Acceso a repositorios privados + +Si tu repositorio es privado, tú controlas el acceso a tu Contenido. Si incluyes información personal del usuario o información personal confidencial, dicha información solo GitHub puede ingresar a ella de acuerdo con la presente declaración de privacidad. El personal de GitHub [no ingresa al contenido del repositorio privado](/github/site-policy/github-terms-of-service#e-private-repositories) excepto +- con fines de seguridad +- para ayudar al propietario del repositorio con un asunto de soporte +- para mantener la integridad del Servicio +- para cumplir con nuestras obligaciones legales +- si tenemos motivos para creer que los contenidos están en violación de la ley, o +- con tu consentimiento. + +Sin embargo, si bien generalmente no buscamos contenido en tus repositorios, es posible que exploremos nuestros servidores y contenido para detectar determinados tokens o firmas de seguridad, malware activo conocido, vulnerabilidades conocidas en las dependencias u otro contenido que se sabe que viola nuestros términos de servicio, como contenido violento extremista o terrorista o imágenes de explotación infantil, basada en técnicas de huellas dactilares algorítmicas (colectivamente, "escaneo automatizado"). Nuestros términos de servicio ofrecen más detalles sobre [repositorios privados](/github/site-policy/github-terms-of-service#e-private-repositories). + +Ten en cuenta que puedes optar por inhabilitar cierto acceso a tus repositorios privados que están habilitados por defecto como parte de la prestación del servicio (por ejemplo, un escaneo automatizado necesario para habilitar las alertas del gráfico de dependencias y del Dependabot). + +GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad. + +#### Repositorios públicos + +Si tu repositorio es público, cualquier persona puede ver los contenidos. Si incluyes información personal del usuario, [información personal confidencial](https://gdpr-info.eu/art-9-gdpr/)o información confidencial, como direcciones de correo electrónico o contraseñas, en tu repositorio público, esa información puede ser indexada por los motores de búsqueda o utilizada por terceros. + +Por favor, consulta más sobre la [Información Personal del Usuario en los repositorios públicos](/github/site-policy/github-privacy-statement#public-information-on-github). + +### Otra información importante + +#### Información pública en GitHub + +Muchos de los servicios y características de GitHub están orientados al público. Si tu contenido es público, los terceros pueden acceder y utilizarlo de acuerdo con nuestros Términos de servicio, como ver tu perfil o los repositorios o extraer datos por medio de nuestra API. Nosotros no vendemos ese contenido; es tuyo. Sin embargo, permitimos que terceros, como organizaciones de investigación o archivos, compilen información de GitHub orientada al público. Se ha sabido que otros terceros, como corredores de datos, también han extraído y compilado información de GitHub. + +Tu Información personal del usuario, asociada con tu contenido, puede ser recopilada por terceros en estas compilaciones de datos de GitHub. Si no quieres que tu información personal de usuario aparezca en las compilaciones de los datos de GitHub de terceros, por favor no hagas tu Información Personal de Usuario disponible públicamente y asegúrate de [configurar tu dirección de correo electrónico en tu perfil de usuario para que sea privada](https://github.com/settings/emails), así como en tu [configuración de confirmaciones de git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Actualmente configuramos la dirección de correo electrónico de los usuarios como privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones. + +Si deseas compilar datos de GitHub, debes cumplir con nuestros términos de servicio con respecto al [uso de la información](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) y [](/github/site-policy/github-acceptable-use-policies#6-privacy)de privacidad y solo puedes usar información personal del usuario orientada al público que reúnes para el propósito para el cual la autorizó nuestro usuario. Por ejemplo, cuando un usuario de GitHub ha hecho que una dirección de correo electrónico esté orientada al público con el fin de identificación y atribución, no uses esa dirección de correo electrónico con el fin de enviar correos electrónicos no solicitados a los usuarios o vender información personal del usuario, por ejemplo, reclutadores, cazatalentos y bolsas de trabajo o para publicidad comercial. Esperamos que protejas de manera razonable cualquier Información Personal de Usuario que hayas reunido de GitHub y respondas de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" que haga GitHub u otros usuarios de GitHub. + +Del mismo modo, los proyectos en GitHub pueden incluir Información Personal de Usuario disponible públicamente como parte del proceso de colaboración. Si tienes alguna queja sobre cualquier tipo de Información Personal de Usuario en GitHub, por favor, consulta nuestra sección de [resolución de quejas](/github/site-policy/github-privacy-statement#resolving-complaints). + + +#### Organizaciones + +Puedes indicar, a través de tus acciones en GitHub, que estás dispuesto a compartir tu Información Personal de Usuario. Si colaboras o te conviertes en miembro de una Organización, los propietarios de su cuenta podrán recibir tu Información personal del usuario. Cuando aceptas una invitación a una Organización, se te notificará de los tipos de información que los propietarios pueden ver (para obtener más información, consulta la sección [Acerca de la Membrecía de Organización](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Si aceptas una invitación a una organización con un [dominio verificado](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain), entonces los propietarios de dicha organización podrán ver tu(s) dirección(es) de correo electrónico completa(s) dentro de l(los) dominio(s) verificado(s) de la organización. + +Por favor, nota que GitHub podría compartir tu nombre de usuario, [información de uso](#usage-information). e [Información de Dispositivo](#device-information) con el(los) propietario(s) de la organización a la cual perteneces, en medida en que tu Información Personal de Usuario se proporcione únicamente para investigar o responder a incidentes de seguridad que afecten o pongan en riesgo la seguridad de esta organización en particular. + +Si colaboras con, o te conviertes en miembro de una cuenta que ha aceptado las [Condiciones de Servicio Corporativas](/github/site-policy/github-corporate-terms-of-service) y con una Adenda de Protección de Datos (DPA) para esta Declaración de Privacidad, entonces, dicha DPA regirá sobre los otros instrumentos en caso de que haya un conflicto con esta Declaración de Privacidad y con la DPA con respecto a tu actividad en la cuenta. + +Contacta a los propietarios de la cuenta para obtener más información sobre la manera en que procesan tu Información personal del usuario y los modos de acceder, actualizar, modificar o borrar la Información personal del usuario almacenada en esa cuenta. + +### Servicios adicionales + +#### Aplicaciones de terceros + +Tienes la opción de habilitar o agregar aplicaciones de terceros, conocidas como "Productos de programador", a tu cuenta. Estos Productos de Desarrollador no son necesarios para usar GitHub. Compartirás tu Información personal del usuario a terceros cuando nos lo solicites, como al comprar un Producto de programador de Marketplace; sin embargo, eres responsable del uso del Producto de programador de un tercero y por la cantidad de Información personal del usuario que eliges compartir con este. Puede revisar nuestra [documentación de API](/rest/reference/users) para ver qué información se proporciona cuando te autenticas en un Producto de Desarrollador usando tu perfil de GitHub. + +#### GitHub Pages + +Si creas un sitio web de Páginas de GitHub, es tu responsabilidad publicar una declaración de privacidad que describa con precisión cómo recolectar, usar y compartir información personal y otra información de visitantes, y cómo cumples con las leyes, normas y reglamentos de privacidad de datos vigentes. Ten en cuenta que GitHub puede recopilar Información personal del usuario de los visitantes a tu sitio web de Páginas de GitHub incluyendo registros de las direcciones IP del visitante, para mantener la seguridad e integridad del sitio web y del servicio. + +#### Aplicaciones de GitHub + +También puedes agregar aplicaciones desde GitHub, tales como nuestra aplicación de Escritorio, nuestra aplicación de Atom, u otras aplicaciones y características de las cuentas, a tu propia cuenta. Estas aplicaciones tienen sus propios términos y pueden recopilar diferentes tipos de Información personal del usuario; sin embargo, todas las aplicaciones de GitHub están sujetas a esta Declaración de Privacidad, y siempre recogeremos la cantidad mínima de Información personal del usuario necesaria y la usaremos únicamente para el propósito por el que nos la diste. + +### Cómo puedes acceder y controlar la información que recopilamos + +Si ya eres un usuario de GitHub, puedes acceder, actualizar, modificar o eliminar la información básica de tu perfil de usuario [editando tu perfil de usuario](https://github.com/settings/profile) o poniéndote en contacto con [el Soporte de GitHub](https://support.github.com/contact) o [el Soporte Premium de GitHub](https://enterprise.githubsupport.com/hc/en-us). Puedes controlar la información que recopilamos acerca de ti limitando la información que contiene tu perfil, manteniendo tu información actual, o poniéndote en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). + +Si GitHub procesa información sobre ti, como la información que [GitHub recibe de terceros](#information-we-collect-from-third-parties), y no tienes una cuenta, entonces puedes, sujeto a la ley vigente, acceder, actualizar, modificar, eliminar u objetar el procesamiento de tu información personal poniéndote en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). + +#### Portabilidad de datos + +Como usuario de GitHub, siempre puedes llevar tus datos contigo. Puedes [clonar tus repositorios en tu escritorio](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), por ejemplo, o puedes utilizar nuestras [herramientas de portabilidad de datos](https://developer.github.com/changes/2018-05-24-user-migration-api/) para descargar la información que tenemos sobre ti. + +#### Retención de datos y eliminación de datos + +Generalmente, GitHub conserva la Información personal del usuario mientras tu cuenta esté activa o cuando sea necesaria para brindarte servicios. + +Si deseas cancelar tu cuenta o eliminar tu Información personal del usuario, puedes hacerlo en tu perfil de usuario [](https://github.com/settings/admin). Conservamos y utilizamos tu información según se necesita para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero salvo requisitos legales, eliminaremos tu perfil completo (dentro de lo razonable) dentro de los 90 días siguientes a tu solicitud. Puedes ponerte en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us) para solicitar la eliminación de los datos que procesamos sobre la base del consentimiento en un plazo de 30 días. + +Después de que una cuenta se ha eliminado, ciertos datos, tales como contribuciones a los repositorios de otros usuarios y comentarios en asuntos ajenos, permanecerán. Sin embargo, eliminaremos o desidentificaremos tu Información personal del usuario, incluyendo tu nombre de usuario y dirección de correo electrónico del campo de autor de propuestas, solicitudes de extracción y comentarios al asociarlos con un [usuario fantasma](https://github.com/ghost). + +Una vez dicho esto, la dirección de correo electrónico que suministraste [a través de tu configuración de confirmaciones de Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) siembre se asociará con tus confirmaciones en el sistema de Git. Si eliges hacer tu dirección de correo electrónico privada, también deberías actualizar la configuración de tu confirmación de cambios de Git. No podemos cambiar o eliminar datos en el historial de confirmación de Git (el software de Git está diseñado para mantener un registro) pero te permitimos controlar qué información pones en ese registro. + +### Uso de cookies y seguimiento + +#### Cookies + +GitHub only uses strictly necessary cookies. Las cookies son pequeños archivos de texto que los sitios web almacenan a menudo en discos duros o dispositivos móviles de los visitantes. + +We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers. + +By using our service, 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 our service. + +Proporcionamos más información acerca de las [cookies en GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) en nuestra página de [Subprocesadores y cookies de GitHub](/github/site-policy/github-subprocessors-and-cookies), en la cual se describen las cookies que configuramos, las necesidades que tenemos para utilizarlas, y la vigencia de las mismas. + +#### DNT + +"[No Rastrear](https://www.eff.org/issues/do-not-track)" (DNT, por sus siglas en inglés) es una preferencia de privacidad que puedes configurar en tu buscador si no quieres que los servicios en línea recolecten y compartan ciertos tipos de información acerca de tu actividad en línea desde los servicios de rastreo de terceros. GitHub responde a las señales DNT del navegador y sigue el estándar [W3C para responder a las señales DNT](https://www.w3.org/TR/tracking-dnt/). Si deseas configurar tu navegador para que indique que no deseas que se rastree, revisa la documentación de tu navegador acerca de cómo habilitar esa señal. También hay buenas aplicaciones que bloquean el seguimiento en línea, como [Privacy Badger](https://privacybadger.org/). + +### Cómo asegura GitHub tu información + +GitHub toma todas las medidas razonablemente necesarias para proteger la Información personal del usuario contra accesos no autorizados, modificación o destrucción; mantener la exactitud de los datos y ayudar a asegurar el uso adecuado de la Información personal del usuario. + +GitHub aplica un programa escrito de información de seguridad. Nuestro programa: +- se alinea con los marcos reconocidos de la industria; +- incluye protecciones de seguridad diseñadas de manera razonable para proteger la confidencialidad, la integridad, la disponibilidad y la flexibilidad de los datos de usuarios; +- es adecuado para la naturaleza, el tamaño y la complejidad de las operaciones comerciales de GitHub; +- incluye procesos de respuesta frente a un incidente y notificación de filtración de datos; y +- cumple con las leyes y regulaciones vigentes relacionadas a la seguridad de la información en las regiones geográficas donde GitHub realiza operaciones. + +En caso de una filtración de datos que afecte tu Información personal del usuario, actuaremos rápidamente para mitigar el impacto de una infracción y notificar a los usuarios afectados sin demoras indebidas. + +La transmisión de datos en GitHub es cifrada usando SSH, HTTPS (TLS) y el contenido del repositorio de git es cifrado en reposo. Administramos nuestras propias jaulas y racks en centros de datos de alto nivel con un alto nivel de seguridad física y de red, y cuando los datos se almacenan con un proveedor de almacenamiento de terceros se cifran. + +Ningún método de transmisión, o método de almacenamiento electrónico, es 100 % seguro. Por lo tanto, no podemos garantizar su seguridad absoluta. Para obtener más información, consulta nuestras [divulgaciones de seguridad](https://github.com/security). + +### Prácticas de privacidad mundiales de GitHub + +GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B. V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement). + +Nuestras direcciones físicas son: + +- GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107. +- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands. + +Almacenamos y procesamos la información que recolectamos en los Estados Unidos de acuerdo con esta Declaración de Privacidad, aunque nuestros proveedores de servicios podrían almacenar y procesar los datos fuera de los Estados Unidos. Sin embargo, entendemos que tenemos usuarios de diferentes países y regiones con diferentes expectativas de privacidad e intentamos satisfacer esas necesidades incluso cuando los Estados Unidos no tienen el mismo marco de privacidad que otros países. + +Proporcionamos el mismo estándar alto de protección de privacidad—como se describe en la presente Declaración de Privacidad—a todos nuestros usuarios en todo el mundo, sin importar su país de origen o ubicación, y estamos orgullosos de los niveles de notificaciones, elección, responsabilidad, seguridad, integridad de datos, acceso y recursos que proporcionamos. Trabajamos duro para cumplir con las leyes vigentes sobre privacidad de datos dondequiera que hagamos negocios, al trabajar con nuestro Oficial de Protección de Datos como parte de un equipo multifuncional que supervisa nuestros esfuerzos de cumplimiento de la privacidad. Además, si nuestros proveedores o afiliados tienen acceso a la Información personal del usuario, deben firmar acuerdos que los obliguen a cumplir con nuestras políticas de privacidad y con las leyes vigentes sobre privacidad de datos. + +En particular: + + - GitHub proporciona métodos claros de consentimiento sin ambigüedad, informado, específico y libremente dado en el momento de la recopilación de datos, cuando recopilamos tu Información personal del usuario utilizando el consentimiento como base. + - Solo recopilamos la cantidad mínima de Información personal del usuario necesaria para nuestros propósitos, a menos que decidas proporcionar más. Te animamos a que sólo nos proporciones la cantidad de datos que consideres oportuno compartir. + - Te ofrecemos métodos sencillos de acceso, modificación o eliminación de la Información personal del usuario que hemos recopilado, en los casos legalmente permitidos. + - Proporcionamos a nuestros usuarios aviso, elección, responsabilidad, seguridad y acceso con respecto a su Información personal del usuario y limitamos el propósito por el cual procesarla. También proporcionamos a nuestros usuarios un método de recurso y cumplimiento. + +#### Cross-border data transfers + +GitHub procesa información personal tanto dentro como fuera de los Estados Unidos y se basa en las Cláusulas Contractuales Estándar como un mecanismo legal para transferir datos legalmente desde el Área Económica Europea, el Reino Unido y Suiza hacia los Estados Unidos. Adicionalmente, GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A. y Suiza-U. S. A. Para conocer más sobre las transferencias de datos interfronterizas, consulta nuestras [Prácticas de Privacidad Globales](/github/site-policy/global-privacy-practices). + +### Cómo nos comunicamos contigo + +Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Por ejemplo, si contactas a nuestro equipo de Soporte con una solicitud, te responderemos por correo electrónico. Tienes mucho control sobre cómo se utiliza y comparte tu dirección de correo electrónico en y a través de GitHub. Puedes administrar tus preferencias de comunicación en tu perfil de usuario [](https://github.com/settings/emails). + +Por diseño, el sistema de control de versiones de Git asocia muchas acciones con la dirección de correo electrónico de un usuario, como mensajes de confirmación. No podemos cambiar muchos aspectos del sistema Git. Si deseas que tu dirección de correo electrónico siga siendo privada, incluso cuando estés comentando en los repositorios públicos, [puedes crear una dirección de correo electrónico privada en tu perfil de usuario](https://github.com/settings/emails). También deberías [actualizar tu configuración local de Git para utilizar tu dirección de correo electrónico privada](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Esto no cambiará la forma en que nos pondremos en contacto contigo, pero afectará la manera en que otros te vean. Actualmente configuramos la dirección de correo electrónico de los usuarios de forma privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones. Por favor, consulta la información adicional sobre las direcciones de correo electrónico en los mensajes de confirmación [aquí](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). + +Dependiendo de tu [configuración de correo electrónico](https://github.com/settings/emails), GitHub puede enviar ocasionalmente correos electrónicos de notificación sobre los cambios en un repositorio que estás viendo, nuevas características, solicitudes de comentarios, cambios importantes en la política o para ofrecer asistencia al cliente. También enviamos correos electrónicos de marketing, basados en tus opciones y de acuerdo con las leyes y regulaciones vigentes. Hay un enlace "darse de baja" ubicado en la parte inferior de cada uno de los correos electrónicos de marketing que te enviamos. Ten en cuenta que no puedes optar por no recibir comunicaciones importantes de nosotros, como correos electrónicos de nuestro equipo de soporte o correos electrónicos del sistema, pero puedes configurar la configuración de las notificaciones en tu perfil para optar por no recibir otras comunicaciones. + +Nuestros correos electrónicos pueden contener una etiqueta de píxeles, que es una pequeña imagen clara que puede decirnos si has abierto o no un correo electrónico y cuál es tu dirección IP. Utilizamos esta etiqueta de píxeles para que nuestro correo electrónico sea más efectivo para ti y para asegurarnos de que no te estamos enviando correo electrónico no deseado. + +### Resolver reclamos + +Si tienes inquietudes acerca de la forma en que GitHub está manejando tu Información personal del usuario, por favor haznos un comentario inmediatamente. Queremos ayudar. Puedes ponerte en contacto con nosotros completando el [Formulario de contacto de privacidad](https://support.github.com/contact/privacy). También puedes enviarnos un correo electrónico directamente a privacy@github.com con el asunto "Confirmaciones de privacidad". Responderemos rápidamente, dentro de los 45 días a más tardar. + +También puedes ponerte en contacto directamente con nuestro Responsable de Protección de Datos. + +| Nuestra casa central de los Estados Unidos | Nuestra oficina de la UE | +| ------------------------------------------ | ------------------------ | +| Oficial de Protección de Datos de GitHub | GitHub BV | +| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 | +| San Francisco, CA 94107 | 1017 HL Amsterdam | +| Estados Unidos | Países Bajos | +| privacy@github.com | privacy@github.com | + +#### Proceso de resolución de disputas + +En el improbable caso de que surja una disputa entre tú y GitHub con respecto al manejo de tu Información personal del usuario, haremos todo lo posible por resolverla. Adicionalmente, si eres un residente de un estado miembro de la UE, tienes el derecho de emitir una queja con tu autoridad supervisora local, y podrías tener más [opciones](/github/site-policy/global-privacy-practices#dispute-resolution-process). + +### Cambios en tu Declaración de privacidad + +Aunque es probable que la mayoría de los cambios sean mínimos, GitHub puede cambiar nuestra Declaración de privacidad de manera ocasional. Les notificaremos a los Usuarios acerca de los cambios materiales a esta Declaración de privacidad por medio de nuestro Sitio web, al menos, 30 días antes de que el cambio entre en vigencia a través de la publicación de un aviso en nuestra página de inicio o enviando un correo electrónico a la dirección principal de correo electrónico que se especifica en tu cuenta de GitHub. También actualizaremos nuestro [Repositorio de políticas del sitio](https://github.com/github/site-policy/), que realiza un seguimiento de todos los cambios de esta política. Para otros cambios en esta declaración de privacidad, invitamos a los usuarios a [consultar](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) o a revisar el repositorio de nuestra política del sitio con frecuencia. + +### Licencia + +La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). + +### Contactarse con GitHub +Las preguntas al respecto de la Declaración de privacidad de GitHub o de las prácticas de manejo de la información se deben realizar por medio de nuestro [Formulario de contacto de privacidad](https://support.github.com/contact/privacy). + +### Traducciones + +A continuación, aparecen traducciones de este documento a otros idiomas. En caso de cualquier conflicto, incertidumbre o aparente inconsistencia entre cualquiera de esas versiones y la versión en inglés, la versión en inglés es la versión que prima. + +#### Francés +Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf) + +#### Otras traducciones + +Para las traducciones de esta declaración hacia otros idiomas, por favor visita [https://docs.github.com/](/) y selecciona el idioma desde el menú desplegable debajo de "Inglés". diff --git a/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md b/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md new file mode 100644 index 0000000000000..132d15cadab53 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md @@ -0,0 +1,121 @@ +--- +title: Acuerdo de programador registrado de GitHub +redirect_from: + - /articles/github-registered-developer-agreement +versions: + free-pro-team: '*' +--- + +GitHub tiene la suerte de tener muchos programadores integrándose a nuestra plataforma. Creemos que es grandioso y deseamos mejorar aún más esa experiencia. El Programa de Programadores de GitHub (el “Programa”) nos ayuda a contactarte, compartir información contigo y apoyar tus esfuerzos creativos mejor que nunca. La relación especial entre GitHub y la comunidad de programadores que el Programa crea requiere un conjunto especial de términos. Bienvenido al Acuerdo de Programador Registrado (“Contrato”). + +Este Acuerdo es un acuerdo legal entre tú (“tú”) y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer cuidadosamente este Acuerdo - regula tu participación en el Programa, y sólo podemos permitirte participar en el Programa si aceptas todos los términos de este Acuerdo. Al hacer clic en "Acepto" abajo, o al participar en el Programa de cualquier otra forma - por ejemplo, accediendo a la información sobre los productos o características de GitHub que aún no están disponibles para el público en general, estás de acuerdo en cumplir todos los términos de este Acuerdo. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS. SI NO TIENES DICHA AUTORIDAD O SI NO ESTÁS DE ACUERDO CON LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO, DEBES SELECCIONAR EL BOTÓN "CANCEL" (CANCELAR) Y NO PUEDES PARTICIPAR EN EL PROGRAMA. SI ERES UNA EMPRESA U OTRA ENTIDAD LEGAL, REPRESENTAS QUE LA PERSONA QUE HACE CLIC EN "ACEPTO" TIENE LA AUTORIDAD PARA VINCULARTE CON EL PRESENTE ACUERDO. + +1. **Se aplicarán los términos de uso de GitHub.com** + + Necesitas tener una cuenta en GitHub.com para poder participar en el programa. Al hacer clic en "Acepto" en la parte inferior del presente acuerdo, también aceptas estar obligado por los [](/articles/github-terms-of-service) (los "TOS") de GitHub.com. En el caso de un conflicto directo entre el presente acuerdo y los TOS, el presente acuerdo regulará; a menos que se establezca de otra forma, ambos acuerdos se aplicarán al mismo tiempo. + +2. **Términos del programa** + + Publicamos los [Beneficios y lineamientos del programa](/program/) (el "Resumen del programa"). Como es de esperarse, la descripción general del programa cambiará de vez en cuando. Estos cambios se te aplicarán como participante en el programa, por lo que te invitamos a que revises de forma periódica la descripción del programa para seguir informado de cualquier cambio. Por una variedad de razones, es posible que necesitemos cambiar, suspender o interrumpir el programa o algunos de los beneficios que ofrecemos. Aceptas que podemos tomar dichas acciones sin responsabilidad contigo, excepto como se especifica en la sección 8. + +3. **Licencia API** + + Siempre y cuando continúes cumpliendo con los TOS, el presente acuerdo y los términos del programa, te otorgamos una licencia limitada, en todo el mundo, no exclusiva y no transferible durante la vigencia del presente acuerdo para acceder y utilizar nuestra API (tal como se define en el [O](/articles/github-terms-of-service)) únicamente con el fin de desarrollar, demostrar, probar y respaldar la interoperabilidad y las integraciones entre tus productos y servicios y nuestros productos y servicios. + + Prometes no actuar de forma incorrecta con nuestra API. Entre otras cosas, esto significa que no vas y no permitirás que otros modifiquen, publiquen, vendan, arrienden, licencien, distribuyan o sublicencien nuestra API; o descompilen, desarticulen, usen ingeniería inversa o intenten derivar el código fuente de nuestra API; reproduzcan, modifiquen o originen trabajos derivados de nuestra API; utilicen nuestra API para proporcionar servicios de burocracia, alojamiento de aplicaciones o procesamiento a terceros; incorporen o combinen de otro modo nuestra API con cualquiera de sus productos o servicios; o utilicen nuestra API para participar, apoyar, o habilitar cualquier tipo de actividad ilegal. + + Nos reservamos el derecho en cualquier momento a modificar o interrumpir, de manera temporal o permanente, tu acceso a la API (o cualquier parte de la misma) con o sin aviso. Es tu responsabilidad exclusiva asegurarte de que tu uso de la API sea compatible con la API vigente en ese momento. Además de los derechos que te otorgamos expresamente en el presente acuerdo o en los TOS, no te otorgamos ningún derecho o licencia a nuestra API, o a cualquier otro producto o servicio de GitHub. + +4. **Tus productos, servicios e integraciones** + + Tus productos, servicios e integraciones (colectivamente, tus “Productos”) son responsabilidad tuya. Eso significa que eres el único responsable de desarrollar, operar y mantener todos los aspectos de tus productos; asegurar que todos los materiales utilizados con o en tus productos sean legales en todas las jurisdicciones donde se usan tus productos y que no promocionen actividades ilegales; obtener cualquier derecho o licencia necesarios para usar y/o distribuir cualquier software de terceros que uses, incluyas, integres o distribuyas con tus productos; y proporcionar a los clientes del usuario final el mismo soporte técnico de alta calidad para tus productos cuando operan en conjunción con nuestra API o cualquier otro de nuestros productos y servicios como lo haces cuando operan por tu cuenta. + +5. **Marketing y Publicidad** + + El marketing y la divulgación de tus integraciones con GitHub es valioso para ambos. Queremos asegurarnos de que suceda de la manera correcta, por lo que hemos incluido un lenguaje aquí para ayudar a aclarar algunas cosas que "hacer" y que "evitar" básicas. + + Aceptas que no harás ninguna representación, garantía o endoso a nadie en nombre de GitHub (incluyendo, entre otras cosas, cualquier producto o servicio de GitHub). A menos que digamos específicamente que está bien en los términos del programa, prometes no declarar o insinuar que hemos desarrollado, respaldado, revisado o aprobado de alguna manera cualquiera de tus productos. + + Si decides promover o publicitar alguno de nuestros productos o servicios en relación con tus productos, deberás asegurarte de cumplir con los términos del presente acuerdo, los términos del programa, los TOS, nuestra [política de marcas comerciales](/articles/github-trademark-policy), y cualquier otra política de GitHub aplicable. Sujeto a los términos y condiciones del presente acuerdo y de los TOS y durante la vigencia del presente acuerdo, te otorgamos una licencia limitada, revocable, en todo el mundo, no exclusiva e intransferible para usar nuestras marcas comerciales, marcas de servicio y logotipos (colectivamente, las "marcas de GitHub") de acuerdo con nuestra [política de marcas comerciales](/articles/github-trademark-policy) y como se especifica en los términos del programa, únicamente con el fin de publicar tu membresía en el programa. + + Queremos decirle al mundo sobre ti y tu participación en el Programa. Para ayudarnos a hacerlo, nos otorgas una licencia limitada, revocable, en todo el mundo, no exclusiva y no transferible para usar tus marcas comerciales, marcas de servicio y logotipos (colectivamente, las "marcas de socios") en nuestros materiales de marketing, únicamente con el fin de promover el programa y publicar tu participación en él. + + A excepción de lo establecido en el presente acuerdo y en los términos de servicio, ninguna parte del presente acuerdo se considerará que otorga a una de las partes, algún derecho, título o interés sobre las marcas de la otra parte. Aceptas no, ya sea durante o después del plazo del presente acuerdo: (i) desafiar o ayudar a otras personas a desafiar las marcas de GitHub, o nuestro registro o cumplimiento de las marcas de GitHub; (II) tratar de adoptar, usar, solicitar o registrar cualquier marca comercial, marca de servicio, logotipo, URL, nombre de dominio de Internet o símbolo que sea confusamente similar a las marcas de GitHub; o (III) hacer que cualquier declaración negativa, falsa o despectivo (ya sea escrita u oral) a cualquier tercero acerca de nosotros, nuestros productos o nuestros servicios. + +6. **Confidencialidad; materiales de pre-lanzamiento** + + Como programador registrado en el programa, puedes obtener acceso a información especial que no esté disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. + + Aceptas que toda información no pública que te demos, o a la que puedas tener acceso como parte del programa, se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas únicamente utilizar dicha información confidencial para tus fines autorizados como participante en el programa (el "propósito") y no para ningún otro propósito. Debes tomar las precauciones razonables para evitar cualquier uso, divulgación, publicación o divulgación no autorizada de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero que no sea tus empleados y contratistas y posteriormente solo en la medida en que: (i) necesiten conocer la información confidencial para el propósito; (II) les haces conocer la naturaleza confidencial de la información confidencial; (III) continúes siendo responsable de los actos y omisiones de dichos empleados y contratistas; y (IV) no prohibimos o restringimos dicha divulgación. + + Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. + + Las obligaciones de la presente sección 6 no se aplicarán a la información que puedas probar que: (i) estuviera generalmente disponible para el público antes de que te la revelemos; (II) se convirtió generalmente disponible para el público después de que te la revelemos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) que conocías antes de que te la revelemos; (IV) le fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. + + Si te otortamos algún software de prelanzamiento o documentación o materiales relacionados, que puedan ncluir videos u otras formas de contenido ("materiales de prelanzamiento"), entonces, sujeto al cumplimiento de los términos y condiciones del presente acuerdo y de los TOS, por la presente te otorgamos un derecho y una licencia no exclusivos, intransferibles y revocables para usar los materiales de prelanzamiento únicamente para respaldar tus pruebas y/o el desarrollo de productos o servicios que están diseñados para funcionar en combinación con los sistemas o programas para los cuales se diseñan los materiales prelanzamiento. Si los materiales de prelanzamiento están acompañados de un acuerdo de licencia separado, aceptas que se aplicarán el acuerdo de licencia separado (además de cualquier disposición más restrictiva contenida en el presente acuerdo o en los términos de servicio). Aceptas no descompilar, hacer ingeniería inversa, desmontar o reducir de cualquier otra manera los materiales de prelanzamiento a una forma perceptible por el hombre y prometes no modificar, establecer redes, alquilar, arrendar, transmitir, vender o prestar los materiales de prelanzamiento, en su totalidad o en parte. Comprendes que no estamos obligados a proporcionarte ningún material de prelanzamiento, a proporcionarte actualizaciones, mejoras o correcciones en los materiales de prelanzamiento, o a notificarte de los cambios que realicemos a nuestros productos y servicios, ahora o en el futuro. + +7. **Cuotas y pago** + + Pueden haber honorarios asociados con la participación en el programa. Te diremos cuáles son esas tarifas en los términos del programa, ya que las actualizamos de vez en cuando (las "tarifas del programa"). Si nos proporcionaste tu información de pago antes, aceptas que podemos cobrar la misma tarjeta de crédito o cuenta de PayPal como parte del presente acuerdo. De lo contrario, deberás otortarnos una cuenta de pago válida y otra información de respaldo. Excepto que se disponga expresamente lo contrario en la sección 8, cualquier pago que nos realices para el programa no es reembolsable. Nos otorgas permiso para cobrar automáticamente tu cuenta de pago en el aniversario de tu primera fecha de pago para cubrir todas las tarifas del programa del año que viene, a menos que canceles el presente acuerdo de acuerdo con la sección 8. All fees are due in U.S. Todas las tarifas se deben pagar en dólares estadounidenses y son exclusivas de todos los impuestos, gravámenes o deberes impuestos por las autoridades fiscales (eres responsable de todos ellos, a excepción de los impuestos basados en nuestros ingresos). + +8. **Plazo y terminación** + + El presente acuerdo comienza en la fecha en que haces clic en "acordar", y continúa durante un período de un (1) año. El presente acuerdo se renovará automáticamente por términos sucesivos de un año, a menos que cualquiera de las partes le dé un aviso por escrito al menos treinta (30) días antes del vencimiento del plazo actual que quiere terminar o uno de nosotros lo terminará antes de acuerdo con lo dispuesto en la presente sección 8. + + Tanto tú como GitHub pueden rescindir el presente acuerdo por cualquier motivo, sin causa, después de treinta (30) días de aviso previo por escrito a la otra. Si finalizamos el presente acuerdo o suspendemos tu acceso al programa por cualquier motivo que no sea tu incumplimiento del presente acuerdo, los términos del programa o los TOS, nosotros, como tu único recurso y nuestra única obligación de dicha terminación, te reembolsaremos la parte proporcional de las tarifas del programa que nos pagaste por el plazo actual del presente acuerdo. El presente acuerdo terminará de inmediato, sin la obligación de aviso, si incumple cualquier término del presente acuerdo, los términos del programa o los TOS. + + Los derechos y obligaciones en las secciones 1, 2, 3 (segundo y tercer párrafo), 4, 5 (segundo y último párrafo), 6, 7 y 9 a 21 del presente acuerdo sobrevivirán a la terminación o a la expiración del presente acuerdo. Tras la terminación o la expiración del presente acuerdo, todos los derechos y las licencias que te otorgaron en el presente acuerdo dejarán de existir de inmediato, regresarás (o, a petición nuestra, destruirás) toda nuestra información confidencial y cualquier copia (incluidas las copias electrónicas) que estén en tu posesión o control y certificaras por escrito que has cumplido con estos requisitos. + +9. **Garantías y limitaciones de responsabilidades** + + Nos garantizas que: (i) tienes la autoridad para celebrar el presente acuerdo y para cumplir con sus obligaciones; (II) llevarás a cabo negocios de una manera que refleje favorablemente en todo momento en los productos y servicios de GitHub y nuestro buen nombre, buena voluntad y reputación; (III) no hará declaraciones o representaciones falsas o engañosas con respecto a GitHub o a nuestros productos y servicios; (IV) no tomarás ninguna obligación o responsabilidad, ni harás ninguna representación, garantía o endoso a nadie en nuestro nombre (incluyendo, entre otros, alguno de nuestros productos o servicios); y (v) no declararás o implicarás que hemos desarrollado, respaldado, revisado o aprobado de alguna manera cualquiera de tus productos. + + EL PROGRAMA, LA API Y CUALQUIER INFORMACIÓN CONFIDENCIAL QUE TE OTORGUEMOS (INCLUYENDO, ENTRE OTROS, LOS MATERIALES DE PRELANZAMIENTO) SE PROPORCIONAN "TAL CUAL" Y SIN GARANTÍAS DE NINGÚN TIPO, EXPRESAS O IMPLÍCITAS. RENUNCIAMOS ESPECÍFICAMENTE A TODAS LAS GARANTÍAS O CONDICIONES IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN PROPÓSITO Y NO INFRACCIÓN PARTICULAR. NO GARANTIZAMOS QUE LOS SERVICIOS O PRODUCTOS QUE PONGAMOS A TU DISPOSICIÓN SE REUNIRÁN CON LOS REQUISITOS DE TUS USUARIOS FINALES. + +10. **Indemnización** + + Te ofrecemos muchas cosas útiles de pre-lanzamiento como parte del programa y existen maneras en las que podrías usar esas cosas de forma inadecuada que podrían dañarnos. Con eso en mente y dado que no podemos controlar las formas en que participas en el programa, aceptas que nos indemnizarás, defenderás y eximirás de toda responsabilidad a cualquier reclamación que pueda surgir por debajo o fuera de tu participación en el programa; tu uso de la API, nuestra información confidencial o cualquier otro producto y servicio de GitHub; tu negligencia o mala conducta intencional; tus productos o cualquier integración que desarrolles, diseñes, promociones o distribuyas usando nuestra API o cualquier información confidencial; cualquier tergiversaciones que realices con respecto a nosotros o a nuestros productos o servicios; o tu violación de cualquier parte del presente acuerdo. + +11. **Limitación de responsabilidad** + + EN NINGÚN CASO SEREMOS RESPONSABLES ANTE TI O ANTE NINGÚN TERCERO POR NINGÚN DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, CONSECUENTE, EJEMPLAR O PUNITIVO, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR DATOS PERDIDOS, PÉRDIDAS DE BENEFICIOS O COSTOS DE ADQUISICIÓN DE BIENES O SERVICIOS SUSTITUTIVOS, SIN PERJUICIO DE LO QUE SE CAUSE Y BAJO CUALQUIER TEORÍA DE RESPONSABILIDAD, YA SEA POR CONTRATO, AGRAVIO (INCLUYENDO LA RESPONSABILIDAD DE PRODUCTOS , RESPONSABILIDAD ESTRICTA Y NEGLIGENCIA), O CUALQUIER OTRA TEORÍA, Y SI SABÍAMOS O NO O DEBERÍAMOS HABER SABIDO SOBRE LA POSIBILIDAD DE DICHOS DAÑOS. EN NINGÚN CASO NUESTRA RESPONSABILIDAD TOTAL ANTE TI DERIVADA DEL PRESENTE ACUERDO O RELACIONADA CON ÉL POR CUALQUIER CAUSA, E INDEPENDIENTEMENTE DE LA FORMA DE ACCIÓN, YA SEA POR CONTRATO O POR AGRAVIO, EXCEDE EL MAYOR DE (I) LOS MONTOS QUE REALMENTE PAGÓ CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO; O (II) 500 DÓLARES ($500). LAS LIMITACIONES ANTERIORES SE APLICARÁN A PESAR DEL FRACASO DEL PROPÓSITO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA QUE SE INDIQUE EN EL PRESENTE ACUERDO. + +12. **Control de exportación** + + No se te permite exportar o volver a exportar ninguna información confidencial, excepto según lo autorizado por la ley de los Estados Unidos y las leyes de la jurisdicción en la que se obtuvo la información confidencial. Particularmente, no se te permite exportar o re-exportar nuestra información confidencial a ningun país embargado por los EE.UU., a ninguna de las listas de Nacionales Especialmente Designados del Departamento de Tesorería de los EE.UU, ni a alguien de La Lista de Entidades o Lista de Personas Denegadas por el Departamento de Comenrcio de los EE.UU. Al unirte al programa o recibir cualquiera de nuestra información confidencial, declaras y garantizas que no estás ubicado en ningún país de estos o en una lista de esa índole. + +13. **Derechos de propiedad** + + Aceptas que GitHub y sus licenciantes son propietarios de todo derecho, título e interés en la API, los materiales de prelanzamiento y todos los demás productos y servicios de GitHub; toda la información y los datos relativos a sus configuraciones y combinaciones; y todas las modificaciones y obras derivadas de cualquiera de las anteriores. Aceptas no eliminar, alterar, cubrir u confundir ningún derecho de autor u otros avisos de derechos de propiedad que colocamos o insertamos en la API, los materiales de prelanzamiento o cualquier otro producto y servicios de GitHub. + +14. **Usuarios gubernamentales** + + Si eres una entidad gubernamental, esta sección aplica para ti. Cierta parte de nuestra información confidencial puede considerarse "artículos comerciales", ya que ese término se define en 48 C. § 2,101, que consiste en "software informático comercial" y "documentación del software informático comercial", ya que dichos términos se usan en 48 C. § 12,212 o 48 C. § 227.7202, según corresponda. Consistente con 48 C. § 12,212 o 48 C. § 227.7202-1 a 227.7202-4, según corresponda, la documentación del software informático comercial y del software informático comercial se licencia para los usuarios finales del gobierno de los EE. UU. (a) únicamente como elementos comerciales y (b) con solo aquellos derechos que se conceden a todos los demás usuarios finales conforme a los términos y condiciones del presente documento. GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107. + +15. **Desarrollo independiente** + + Ninguna parte del presente acuerdo perjudicará nuestro derecho a desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que puedan competir con tus productos. + +16. **Comentarios** + + Siempre estamos tratando de mejorar y tus comentarios nos ayudarán a hacerlo. Si decides hacernos comentarios, sugerencias o recomendaciones para el programa o para nuestros productos o servicios (colectivamente, "comentarios"), reconoces y aceptas que somos libres de usar esos comentarios de cualquier manera que queramos, sin restricciones (sujeto a cualquier patente o derecho de autor aplicable, por supuesto). + +17. **Contratistas independientes** + + Las partes del presente acuerdo son contratistas independientes. Ninguno de nosotros será considerado como empleado, agente, socio, franquiciador, franquiciado o representante legal del otro para ningún propósito y ninguno de nosotros tendrá ningún derecho, poder o autoridad para crear ninguna obligación o responsabilidad en nombre de la otra. + +18. **Asignación** + + No puedes ceder o transferir el presente acuerdo o ninguno de tus derechos en virtud del mismo, en su totalidad o en parte, por el funcionamiento de la ley o de cualquier otra manera, sin nuestro consentimiento previo por escrito. + +19. **Legislación aplicable y jurisdicción** + + El presente acuerdo se interpretará y entenderá de acuerdo con las leyes del estado de California, sin tener en cuenta los principios de conflicto de leyes. Todas las disputas que surjan del presente Acuerdo estarán sujetas a la jurisdicción exclusiva del estado y los tribunales federales ubicados en el Condado de San Francisco, California y cada uno de nosotros consiente la jurisdicción personal allí. + +20. **Modificaciones; renuncias; inexistencia de terceros beneficiarios** + + Es posible que el presente acuerdo no se cambie, excepto mediante un escrito firmado por ambas partes. Cualquier renuncia a las disposiciones del presente acuerdo o de los derechos o recursos de una parte conforme a lo dispuesto en el presente acuerdo debe ser por escrito para que sea efectiva. Si se encuentra que algún término, condición o disposición del presente acuerdo no es válido o no ejecutable, los términos restantes seguirán siendo válidos y exigibles en la medida en que lo permita la ley. Cada una de las partes acepta expresamente que no hay terceros beneficiarios del presente acuerdo. + +21. **Acuerdo completo** + + El presente acuerdo, los términos de servicio y los términos del programa contienen el acuerdo completo de las partes con respecto al tema y sustituyen todas las comunicaciones, representaciones, entendimientos y acuerdos previos, ya sean escritos u orales. Los términos o condiciones de cualquiera de tus pedidos de compras, confirmacones u otros documentos que nos envíes en relación con el presente acuerdo serán nulos y sin efecto. diff --git a/translations/es-ES/content/github/site-policy/github-research-program-terms.md b/translations/es-ES/content/github/site-policy/github-research-program-terms.md new file mode 100644 index 0000000000000..3379af805f2e3 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-research-program-terms.md @@ -0,0 +1,63 @@ +--- +title: Términos del programa de investigación de GitHub +redirect_from: + - /articles/github-research-program-terms +versions: + free-pro-team: '*' +--- + +¡Bienvenido al programa de investigación de GitHub (el "Programa")! Para participar, necesitaremos que accedas a un conjunto especial de términos, el acuerdo del programa de investigación de GitHub ("Acuerdo"). + +El presente acuerdo es un acuerdo legal entre tú ("tú", "tu") y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer el presente Acuerdo detenidamente - solo puedes ser un participante del programa si aceptas todos los términos del presente acuerdo. Al participar en el programa de cualquier manera, por ejemplo, al ingresar a información sobre los productos o servicios de GitHub que aún no están disponibles para el público en general, estás aceptando estar sujeto a todos los términos del presente acuerdo. + +### A. Tu retroalimentación + +Siempre intentamos mejorar nuestros productos y servicios y tu retroalimentación como participante del programa nos ayudará a hacerlo. Si decides darnos alguna idea, conocimiento algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios a través del programa (colectivamente, "Retroalimentación"), entonces necesitamos los derechos legales para usar y analizar esa información para dichos fines. En la jerga legal, eso significa que otorgas a GitHub una licencia libre de regalías, totalmente pagada, en todo el mundo, transferible, sublicenciable, irrevocable y perpetua para implementar, usar, modificar, explotar comercialmente y/o incorporar los comentarios en nuestros productos, servicios y documentación. + +### B. Confidencialidad + +GitHub puede proporcionarle acceso a la información especial que no está disponible para el resto del mundo con el propósito de proporcionarnos comentarios a través del programa (el "Objetivo"). Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. + +Aceptas que toda información no pública que compartamos contigo o a la que puedas tener acceso como participante del programa se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas usar esa información confidencial únicamente para el propósito que se indica arriba y no para ningún otro propósito. Debes usar el mismo grado de cuidado que usarías con tu información confidencial, pero no menos de las precauciones razonables para evitar cualquier uso no autorizado, divulgación, publicación o diseminación de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero. + +Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. + +Las obligaciones de la presente sección 2 no se aplicarán a la información que puedas probar que: (i) estuvo generalmente disponible para el público antes de que te la revelaramos; (II) estuvo generalmente disponible para el público después de que te la revelamos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) conocías antes de que te la revelaramos; (IV) te fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. + +### C. Salvaguarda de derechos + +Toda la información confidencial sigue siendo propiedad exclusiva y propiedad de GitHub. Ninguna de las partes adquiere ningún derecho de propiedad intelectual conforme a lo dispuesto en el presente acuerdo, salvo que se especifique expresamente aquí. + +### D. Privacy + +Al participar en este programa, aceptas el uso de tu información personal con fines de investigación y para ningún otro propósito. Como parte del programa, es posible que uses tu información personal para contactarte o conservar tu información, para contactarte en una fecha posterior. La información personal no incluye información agregada, que no identifiques personalmente. Es posible que uses la información de identificación personal o agregada que se recopila a través del programa para operar, analizar y mejorar nuestros productos y servicios. + +Puedes retirar tu consentimiento en cualquier momento y solicitar acceso o la eliminación de la información personal que tenemos sobre ti. Para obtener más información acerca de cómo puedes acceder, actualizar, modificar o eliminar la información personal que GitHub recopila a través del programa, consulta la[Declaración de privacidad de GitHub](/articles/github-privacy-statement/) o contáctanos a través de nuestra {% data variables.contact.contact_privacy %}. + +### E. Términos del software y los servicios de GitHub + +Si se necesita acceso a los servicios o al software de GitHub para participar en determinados estudios o actividades del programa, los servicios o el acuerdo de software correspondientes se aplicarán a tu uso de esos productos (los "términos generalmente aplicables"). En el caso de un conflicto directo entre el presente acuerdo y los términos generalmente aplicables, tus términos generalmente aplicables controlarán, excepto con respecto a cualquier uso de información confidencial (como se define a continuación), en cuyo caso el presente acuerdo controlará. + +### F. Exención de garantías + +Toda la información confidencial y otros materiales que recibes a través del programa se proporcionan "tal cual" y sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean expresas, implícitas o reglamentarias, relacionadas con el programa, incluidas, entre otras, cualquier garantía de comerciabilidad, idoneidad para un propósito particular, título, seguridad, exactitud y no infracción. + +### G. Limitación de responsabilidad + +A excepción de lo prohibido por la ley, entiendes y aceptas que no seremos responsables ante ti o ningún tercero por cualquier pérdida de beneficios, uso, buena voluntad o datos, o por cualquier daño incidental, indirecto, especial, consecuente o ejemplar. + +Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable. + +### H. Varios + +#### 1. Legislación aplicable +Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California. + +#### 2. Intransferible +GitHub podría asignar o delegar este acuerdo, total o parcialmente, a cualquier persona o entidad en cualquier momento, con o sin consentimiento, incluyendo el otorgamiento de licencia descrito en la sección A. No podrás asignar o delegar ningún derecho u obligación establecido bajo este acuerdo sin nuestro consentimiento previo por escrito, y cualquier asignación o delegación no autorizada que realices será nula. + +#### 3. Divisibilidad, sin exención y supervivencia +Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo. + +#### 4. Enmiendas, acuerdo completo +El presente acuerdo solo puede modificarse mediante una enmienda por escrito firmada por un representante autorizado de GitHub. El presente Acuerdo, junto con los términos generalmente aplicables y la declaración de privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tú y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. diff --git a/translations/es-ES/content/github/site-policy/github-sensitive-data-removal-policy.md b/translations/es-ES/content/github/site-policy/github-sensitive-data-removal-policy.md new file mode 100644 index 0000000000000..f1fd596bf1a2c --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-sensitive-data-removal-policy.md @@ -0,0 +1,83 @@ +--- +title: Política de eliminación de datos sensibles de GitHub +redirect_from: + - /articles/github-sensitive-data-removal-policy +versions: + free-pro-team: '*' +--- + +Si crees que el contenido en GitHub infringe un derecho de autor válido que posees, por favor consulta nuestra [política de retiro DMCA](/articles/dmca-takedown-policy/) y nuestra [Guía para enviar una notificación de retiro DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice/). Confiamos en la notificación de la DMCA y en el proceso de retiro para la mayoría de nuestras acciones de eliminación. + +Sin embargo, entendemos que de vez en cuando se puede publicar contenido sensible y relacionado con la seguridad en GitHub, ya sea accidentalmente o con propósito. Proporcionamos nuestro proceso de eliminación de datos sensibles para borrar estos datos sensibles en determinadas circunstancias excepcionales en las que el proceso DMCA no aplicaría, tales como cuando su seguridad está en riesgo de contraseñas expuestas y no posees los derechos de autor sobre el contenido específico que necesitas eliminar, o el contenido no está protegido por derechos de autor. Esta guía describe la información que GitHub necesita de usted para procesar una solicitud para eliminar datos sensibles de un repositorio. + +### ¿Qué son los datos sensibles? + +Para los propósitos de este documento, "datos sensibles" se refiere al contenido que (i) deberías haberse mantenido confidencial, *y* (ii) cuya disponibilidad pública plantea un riesgo específico o dirigido de seguridad para ti o tu organización. + +#### Las solicitudes de eliminación de datos sensibles son adecuadas para: +- Credenciales de acceso, como nombres de usuario combinados con contraseñas, tokens de acceso, u otros secretos sensibles que pueden conceder acceso al servidor, red o dominio de tu organización. +- Los token AWS y otras credenciales de acceso similares que conceden acceso a un tercero en tu nombre. Debes tener la capacidad de mostrar que el token te pertenece. +- Documentación (como diagramas de red) que plantea un riesgo específico de seguridad para una organización. Los nombres de servidores internos, direcciones IP y URL, por sí solos, no son lo suficientemente sensibles; debe ser capaz de mostrar que el uso del nombre del servidor interno en un archivo o parte del código en particular que representa una amenaza para la seguridad. + +#### Las solicitudes de eliminación de datos sensibles son _no_ adecuadas para: +- Solicitudes para eliminar contenido que pueda infringir los derechos de autor de tu empresa o de tu organización. Si tienes preguntas sobre cómo maneja GitHub los asuntos relacionados con los derechos de autor o te gustaría informar sobre contenido que potencialmente infractor, por favor revisa nuestra [política de retiro DMCA](/articles/dmca-takedown-policy/). El proceso de eliminación de datos sensibles generalmente no está destinado a la eliminación de archivos o repositorios completos — solo para las partes específicas de datos sensibles en esos archivos. Mientras que puede haber casos en los que los archivos contienen solamente información confidencial, debes justificar el riesgo de seguridad para la eliminación de dichos archivos y esto puede aumentar el tiempo necesario para procesar tu solicitud. +- Disputas de marcas registradas. Si tiene preguntas sobre cómo maneja GitHub los asuntos relacionados con la marca o deseas informar sobre contenido que contiene marcas comerciales o marcas de servicio, revisa nuestra [Política de Marcas](/articles/github-trademark-policy/). +- Menciones simples de la identidad de tu empresa, nombre, marca, nombre de dominio, u otras referencias a tu empresa en archivos en GitHub. Debes tener la capacidad de articular por qué un uso de la identidad de tu empresa es una amenaza para la postura de seguridad de tu empresa antes de tomar medidas en virtud de esta política. +- Reclamaciones de privacidad. Si tiene inquietudes sobre tu propia privacidad o te estás comunicando con nosotros en nombre de tus empleados debido a una preocupación por la privacidad — por ejemplo, si hay direcciones de correo electrónico privadas u otra información personal publicada, por favor contáctanos a través de [nuestro formulario de contacto sobre privacidad](https://github.com/contact/privacy). +- Archivos completos o repositorios que no plantean un riesgo de seguridad específico, pero consideras que son censurables de otro modo. +- Contenido regido por nuestras [Directrices de la comunidad](/articles/github-community-guidelines/), tales como malware o herramientas de uso general. Si tienes dudas sobre nuestros Lineamientos de Comunidad crees que algún contenido de GitHub podría violarlos, puedes utilizar {% data variables.contact.report_content %} para contactarnos. + +### Cosas que debes saber + +**Realiza preguntas educadamente.** Un gran primer paso antes de enviarnos una solicitud para eliminar datos es intentar contactar directamente con el usuario. Pueden haber ingresado información de contacto en su página de perfil público o en el archivo de soporte o README del repositorio o podrías ponerte en contacto creando una propuesta o solicitud de extracción en el repositorio. Esto no es estrictamente necesario, pero es común. + +**Sin bots.** Debes tener un profesional capacitado para evaluar los hechos de cada solicitud que envíes. Si estás subcontratando tus labores a un tercero, asegúrate de saber cómo trabaja y asegúrate que no estén utilizando bots automatizados para presentar quejas en masa. Estas quejas a menudo incluyen datos que no suponen ninguna amenaza para la seguridad y no incluyen suficientes explicaciones, que requieran un retroceso adicional y resulten en retrasos, incluso cuando la queja es válida. + +**Envía la solicitud correcta.** Ofrecemos este proceso de eliminación de datos sensibles como un servicio excepcional únicamente para contenido de alto riesgo. No podemos utilizar este proceso para eliminar otros tipos de contenidos, como potencialmente infringir contenido y no podemos procesar ningún otro tipo de solicitudes de eliminación simultáneamente mientras procesamos solicitudes de eliminación de información sensible. Podremos ayudarlo más rápidamente si envías tus solicitudes de eliminación de datos confidenciales por separado de cualquier solicitud para eliminar contenido potencialmente infractor. Si no estás seguro de que su solicitud implique sólo datos confidenciales o también involucre otros asuntos legales, por favor pide asesoramiento legal. + +**Tiempo de procesamiento.** Mientras procesamos solicitudes de eliminación de datos sensibles lo antes posible, debido al volumen de solicitudes que procesamos, puede tomar algún tiempo para que tu solicitud se revise.< Las solicitudes adicionales, o múltiples solicitudes de puntos de contacto adicionales, pueden provocar retrasos. + +### ¿Cómo funciona realmente? + +1. **El reclamante investiga.** Corresponde a la parte solicitante llevar a cabo su propia investigación y proporcionarnos los [detalles que necesitamos](#your-request-must-include) — lo que es más importante, una explicación de cómo los datos plantean un riesgo para la seguridad. GitHub no está en posición de buscar o hacer determinaciones iniciales sobre datos sensibles en nombre de cualquier persona u organización. + +2. **El reclamante envía una solicitud de eliminación de datos sensibles.** Después de realizar una investigación, el demandante prepara y [envía una solicitud de eliminación de datos sensibles](#sending-a-sensitive-data-removal-request) a GitHub. Si la solicitud no está lo suficientemente detallada para demostrar el riesgo de seguridad y para que GitHub localice los datos, te responderemos y te solicitaremos más información. + +3. **GitHub pide al usuario que haga cambios.** En la mayoría de los casos, nos pondremos en contacto con el usuario que creó el repositorio y le daremos la oportunidad de eliminar o modificar los datos sensibles especificados en la solicitud o de disputar el reclamo. + +4. **El usuario notifica a GitHub de los cambios.** Si el usuario decide realizar los cambios especificados, debe comunicarnos dentro del período de tiempo que hayan sido permitidos. Si no lo hace, deshabilitaremos el repositorio. Si el usuario nos notifica que ha realizado cambios, verificaremos que los cambios se hayan realizado y notificaremos al demandante. + + O + +5. **El usuario puede impugnar la solicitud.** Si un usuario cree que el contenido en cuestión no es información sensible sujeta a esta Política, puede impugnarlo. Si lo hacen, generalmente dejaremos que el demandante se ponga en contacto con el usuario y trabaje directamente con él, dentro de los límites razonables. + +6. **Cambios a las revisiones del demandante.** Si el usuario realiza cambios, el demandante debe revisarlos. Si los cambios son insuficientes, el demandante debe proporcionar a GitHub detalles explicando por qué. GitHub puede desactivar el repositorio o dar al usuario una oportunidad adicional de hacer los cambios. + +7. **El usuario puede solicitar una ventana adicional para realizar cambios.** Si el usuario perdió su oportunidad de eliminar los datos confidenciales especificados en el aviso, podríamos permitirle una ventana adicional de aproximadamente 1 día hábil, previa solicitud, para realizar esos cambios. En ese caso, GitHub notificará al demandante. + +#### ¿Qué hay de las bifurcaciones? (o ¿Qué es una bifurcación?) +Una de las mejores características de GitHub es la capacidad de los usuarios de "bifurcar" los repositorios de otros. ¿Qué significa esto? En esencia, significa que los usuarios pueden hacer una copia de un proyecto en GitHub en sus propios repositorios. Como la licencia o la ley permite, los usuarios pueden hacer cambios en esa bifurcación para volver al proyecto principal o simplemente mantener como su propia variación de un proyecto. Cada una de estas copias es una "[bifurcación](/articles/github-glossary/#fork)" del repositorio original, que a su vez también se puede llamar la "matriz" de la bifurcación. + +GitHub no deshabilitará automáticamente las bifurcaciones cuando se deshabilite un repositorio matriz. Esto se debe a que las bifurcaciones pertenecen a diferentes usuarios y pueden haber sido alteradas de manera significativa. GitHub no lleva a cabo ninguna investigación independiente sobre las bifucaciones. Esperamos que quienes envíen solicitudes de eliminación de datos sensibles lleven a cabo esa investigación y, si consideran que las bifurcaciones también contienen datos sensibles, incluyan expresamente bifurcaciones en su solicitud. + +### Cómo enviar una solicitud de eliminación de datos sensibles + +Debido al tipo de contenido de los hosts de GitHub (principalmente de código de software) y a la forma en que se gestiona el contenido (con Git), necesitamos que las demandas sean lo más específicas posible. Para que podamos verificar que un usuario ha eliminado por completo los datos sensibles, necesitamos saber exactamente dónde buscar. + +Estas directrices están diseñadas para que el procesamiento de solicitudes para eliminar datos sensibles sean lo más sencillas posible. + +#### Tu solicitud debe incluir: + +1. Un enlace funcional y seleccionable a cada archivo que contiene datos sensibles. (Ten en cuenta que no podemos trabajar a partir de resultados de búsqueda, ejemplos o capturas de pantalla.) +2. Números de línea específicos dentro de cada archivo que contenga los datos sensibles. +3. Una breve descripción de cómo cada elemento identificado supone un riesgo de seguridad para ti o tu organización. ***Es importante que proporciones una explicación de cómo plantean los datos un riesgo de seguridad más allá de simplemente indicar que lo hace.*** +4. Si eres un tercero actuando como agente de una organización que se enfrenta a un riesgo de seguridad, incluye una declaración de que tienes un derecho legal a actuar en nombre de dicha organización. +5. OPCIONAL: Haznos saber si tu solicitud es especialmente urgente y por qué. Respondemos a todas las solicitudes de eliminación de datos sensibles lo antes posible. Sin embargo, si esta solicitud es especialmente sensible al tiempo, como una exposición de credenciales muy reciente, por favor explica por qué. + +### Como presentar tu solicitud + +Puedes enviar tu solicitud para eliminar datos confidenciales a través de nuestro [formulario de contacto](https://support.github.com/contact?tags=docs-sensitive-data). Por favor, incluye una versión de texto plano de tu solicitud en el cuerpo de tu mensaje. El envío de tu solicitud en un archivo adjunto puede resultar en retrasos en el proceso. + +### Disputas + +Si recibiste una solicitud de eliminación de datos confidencial por nuestra parte puedes discutirlo respondiendo a nuestro correo electrónico y haciéndonos saber —con el mayor detalle posible— por qué consideras que el contenido en cuestión no es información sensible sujeta a esta Política. diff --git a/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md b/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md new file mode 100644 index 0000000000000..4699d8b2b92aa --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md @@ -0,0 +1,184 @@ +--- +title: Términos adicionales de los Patrocinadores de GitHub +redirect_from: + - /articles/github-sponsors-additional-terms +versions: + free-pro-team: '*' +--- + +Tu participación en el Programa de Patrocinadores de GitHub (el "Programa") está sujeta a las [Condiciones de Servicio de GitHub](/github/site-policy/github-terms-of-service) (el "Acuerdo") así como a las siguientes condiciones adicionales ("Condiciones Adicionales"). Cualquier uso del Programa de Patrocinadores de GitHub que viole el Acuerdo también constituirá una violación de estos Términos Adicionales. Todos los términos en mayúscula que se utilizan, pero no se definen a continuación, tienen los significados que se les asignan en el Acuerdo. Estos Términos Adicionales para el Programa de Patrocinadores de GitHub describen la relación entre GitHub y tú, el "Programador Patrocinado", para el Programa. Los Términos adicionales entran en vigor a partir de la fecha en que los aceptas ("Fecha de entrada en vigor"). + +### 1. Definiciones. + +Las "**Políticas de GitHub" **se refieren a todas las políticas y procedimientos ahora actuales de GitHub que el Desarrollador Patrocinado debe seguir de acuerdo con lo que se indica en el programa, incluyendo los [Lineamientos de la Comunidad de GitHub](/github/site-policy/github-community-guidelines). + +"**Patrocinador**" se refiere al Usuario que te compró una Suscripción o te pagó un Patrocinio a través de tu Cuenta de programador patrocinado. + +"**Cuenta de programador patrocinado**" se refiere a la cuenta que estableces a través del Programa para recibir el pago de los Patrocinadores. + +"**Contenido del programador patrocinado**" se refiere a todo el contenido que le envías a GitHub en relación con el Programa, incluido el Contenido generado por el usuario y Tu contenido, tus marcas, marcas registradas, marcas de servicio, nombres comerciales, logos o indicaciones de origen ("**Marcas del programador patrocinado**"), y los datos relacionados con tu Cuenta de programador patrocinado. + +"**Patrocinio**" se refiere a un pago que se te efectúa a través del Programa y el Servicio. + +"**Suscripción**" se refiere a un Patrocinio mensual periódico a cambio de bienes, servicios u otras ofertas que les proporcionas a los Patrocinadores. + +"**Pago del Desarrollador Patrocinado**" significa el valor neto del cien por ciento (100%) de los pagos brutos mensuales de GitHub que se reciben a modo de Patrocinios y Suscripciones a Cuentas de Desarrollador Patrocinado, mas cualquier Fondo Compensatorio aplicable, y otros montos de opciones de monetización que el Desarrollador Patrocinado elija utilizar, según sea aplicable, menos cualquier descuento, impuestos, cuotas, cantidades que GitHub no recolecte o que se reembolsen o cobren de vuelta, y cantidades debidas a cualquier tercero en conexión con el Programa con respecto a la Cuenta del Desarrollador Patrocinado, y otras Exclusiones según se detalla en la Sección 4. + +"**USD**" significa Dólar Estadounidense. + +### 2. Uso aceptable. + +#### 2.1. Programa de Patrocinios de GitHub + +Para poder participar en el programa, debes cumplir con las leyes de mayoría de edad de tu país (por ejemplo, debes tener por lo menos 13 años de edad si vives en los Estados Unidos), tener una cuenta de GitHub válida y haber aceptado la [Sección de Uso Aceptable](/github/site-policy/github-terms-of-service#c-acceptable-use) en el acuerdo y en las Políticas de GitHub Aplicables, así como estas Condiciones Adicionales de los Patrocinadores de GitHub. + +Si tienes más de 13 años pero menos de 18, puedes otorgar y recibir fondos de Patrocinio, tomando en cuenta que Stripe, nuestro procesador de pagos, pueda recolectar información de verificación de tu tutor legal. + +Bajo ninguna circunstancia recibirás pagos o recabarás fondos que involucren: + +* fraude, rescate, violaciones de la propiedad intelectual u otros fines ilícitos; + +* tergiversación o engaño relacionado con los motivos por los cuales estás recaudando fondos o solicitando patrocinio; + +* la compra o venta de ICO, tokens de la utilidad u otros tipos de criptomoneda; + +* la compra o venta de valores, acciones u otros tipos de ofertas de inversión; + +* la venta de información personal o el procesamiento de información personal que viole cualquier legislación; + +* loterías, rifas, juegos de azar, esquemas piramidales, autonegociación, "esquemas hazte rico rápido", esquemas de marketing engañosos, esquemas de "donación por donación" o cualquier intento de jugar con los sistemas o servicios de GitHub o de terceros; y, + +* actividades con países, regiones, gobiernos, personas o entidades que no estén permitidas conforme a las sanciones impuestas por los EE. UU. y demás sanciones económicas que imponga la ley correspondiente, o actividades dentro de ellos o que los involucren. Y otras sanciones económicas bajo la legislación aplicable. + +#### 2.2. GitHub Sponsors Matching Fund +El Fondo Compensatorio para Patrocinios de GitHub pretende alentar a la comunidad que participa en el ecosistema de Software de Código Abierto (OSS, por sus siglas en inglés) para contribuir con fondos sostenibles para los individuos elegibles con Cuentas de Desarrollador Patrocinado. Todos los individuos que apliquen al Programa antes del 1 de enero de 2020 se revisarán para elegibilidad para el fondo Compensatorio, pero no todas las Cuentas de Desarrollador Patrocinado elegibles se escogerán. Las organizaciones no pueden participar en el Fondo Compensatorio para Patrocinios de GitHub, y no se escogerán las Cuentas de Desarrollador Patrocinadas elegibles que ya se encuentren patrocinadas por una organización. Encuentra las reglas adicionales a continuación. + +##### 2.2.1. Condiciones para el Fondo Compensatorio. +La elegibilidad para el Fondo Compensatorio para Patrocinios de GitHub se evalúa caso por caso y está sujeto a las siguientes limitaciones: + +* Debes tener una cuenta de GitHub, ser aceptado en el programa como un individuo, y contribuir activamente al OSS. Por favor nota que GitHub no permite operar más de una cuenta de usuario gratuita. De esta manera, la elegibilidad está disponible de manera individual y no se aprobará en cuentas múltiples de la misma persona. + +* Tu uso de GitHub y de tu Cuenta de Desarrollador Patrocinada debe ser, según nuestra determinación y exclusivo criterio, consistente con la misión de Patrocinios de GitHub para expandir las oportunidades para contribuir con el código abierto que se describe en los [Lineamientos de Comunidad de GitHub](/github/site-policy/github-community-guidelines). + +* No se te podrá elegir para ningún patrocinio que se origine de una cuenta de usuario u organización con un perfil de Patrocinios de GitHub publicado. + +* GitHub se reserva el derecho de mantener o rescindir el dinero del Fondo Compensatorio y de bloquear a cualquier usuario de su participación en el Fondo de Compensación para Patrocinios de GitHub, incluyendo, mas no limitándose a publicar el contenido o proyectos que GitHub determine como ofensivos u objetables de cualquier otra manera. + +##### 2.2.2. Periodo de Elección. +El periodo de elección comienza después de que GitHub acepta una Cuenta de Desarrollador Patrocinado individual en sus Patrocinios y publica el perfil de patrocinio para la cuenta. Para cada Cuenta de Desarrollador Patrocinada elegible para el Fondo Compensatorio para Patrocinios de GitHub, GitHub podrá elegir un patrocinio comunitario de hasta $5,000 dólares estadounidenses totales durante los primeros 12 meses en que la Cuenta de Desarrollador Patrocinada esté en el Programa. El periodo de consideraciones no puede extenderse por razón alguna. Durante el periodo deelección, GitHub no cobrará cuota alguna, así que el desarrollador patrocinado recibirá el 100% del patrocinio. Posteriormente, podríamos cobrar una cuota nominal por procesamiento. + +* Si el Patrocinio o la Suscripción Patrocinadora cesa por cualquier motivo, la elección asociada también cesará. No podrán elegirse aquellos fondos que se reembolsen al Patrocinador antes de la fecha de pago al Desarrollador Patrocinado. + +* Si sales de los Patrocinios de GitHub y te vuelves a unir posteriormente, el tiempo transcurrido entre tus periodos de participación podrá contarse en el periodo de elección, o éste podría caducar. + + +* Si GitHub descubre cualquier violación potencial, antes de que se otorgue el pago de cualquier fondo compensatorio durante el periodo de elección, GitHub podrá inhabilitar los pagos hasta que se haya completado una investigación, y los fondos compensatorios que se hayan otorgado al desarrollador patrocinado podrán revocarse si se encuentra que éstos constituyen una violación de la presente política. + +* {% data reusables.sponsors.github-contact-applicants %} + +### 3. Obligaciones del programador patrocinado. + +#### 3.1. General. +Tú: (A) crearás una Cuenta de programador patrocinado; (B) pondrás a disposición el Contenido del programador patrocinado a través del Programa y el Servicio, y (C) cumplirás con todas las políticas de GitHub. Serás el único responsable de la asistencia, el desarrollo y el mantenimiento de tu Cuenta de programador patrocinado y del Contenido del programador patrocinado, y de cualquier queja acerca de ellos. + +#### 3.2. Registro. +Si decides postularte al Programa, la entrada al Programa está supeditada a que completes el proceso de registro y a la aceptación en el Programa de parte de GitHub. Asimismo, puede que debas registrarte con el (los) proveedor(es) de servicio de pago seleccionado(s) por GitHub (como Stripe) para acceder y usar determinadas funciones del Programa. Te debes registrar con tu verdadera identidad y aceptar proporcionar y mantener tu información verdadera, precisa, actual y completa, tal como la solicita el formulario de registro del Programa. Los datos de registro y otra información determinada sobre ti se rigen por nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement) y por cualquier declaración de privacidad proporcionada por nuestro procesador de pagos. GitHub se reserva el derecho a rechazar la aceptación al Programa. + +#### 3.3. Monetización del contenido. +A través del Programa y el Servicio, GitHub puede proporcionarte varias opciones para monetizar tu Contenido del programador patrocinado. Algunas opciones pueden requerir que actualices determinadas configuraciones de tu Cuenta del programador patrocinado. Asimismo, pueden variar las maneras en que el Programa admite cada opción de monetización. Si utilizas una (o más) de estas opciones cambiando las configuraciones correspondientes, entonces, aceptas los términos que corresponden a esa opción. Algunas opciones de monetización pueden requerir que le proporciones más información a GitHub o a sus proveedores de servicio, o que aceptes otros términos de GitHub o términos de terceros. + +##### 3.3.1. Suscripciones. +El Programa te proporciona la capacidad de ofrecer Suscripciones. Si decides ofrecer Suscripciones, GitHub te pagará el Patrocinio de la suscripción, tal como se describe en la Sección 4. Eres responsable de determinar la naturaleza, contenido y capacidades de tu oferta de Suscrpciones, sujeta a estas Condiciones Adicionales y Políticas de GitHub aplicables. + +##### 3.3.2. Otros Patrocinios. +El Programa o Servicio podría proporcionarte la capacidad de aceptar una donación u otra clase de Patrocinio directo de otro Usuario sin una oferta de Suscripción. Sin embargo, ya que GitHub no lleva a cabo estos tipos de Patrocinio, deberás establecer una cuenta comercial con un servicio de pagos de terceros (tal como Stripe) y estar sujeto a los términos, condiciones y políticas de privacidad de la cuenta comercial de dicho proveedor. Cualquier cantidad que se te otorgue, sea o no una donación, se pagará directamente a tu cuenta comercial y no incluirá ningún Pago de Desarrollador Patrocinado. Aceptas que no le harás ningún reclamo ni le pedirás ninguna compensación a GitHub vinculado con las donaciones, y cualquier disputa relacionada con una donación será únicamente entre tú y el proveedor de servicios de pago externo. Eres responsable de dar cumplimiento a cualquier acuerdo, política y leyes o regulaciones aplicables del tercero proveedor de servicios. Para tu comodidad, GitHub puede decidir proporcionarte información o brindarte un informe sobre el monto de las donaciones que recibiste. + +##### 3.3.3. Publicidad. +Si bien entendemos que podrías querer promover a tus Patrocinadores publicando sus nombres o logos en tu cuenta, el enfoque principal de tu Contenido de Desarrolador Patrocinado no deberá ser la publicidad o el marketing promocional. Adicionalmente, no deberás celebrar ningún contrato de publicidad para promover cualquier producto o marca, ya que esto estaría prohibido por el [Acuerdo](/github/site-policy/github-terms-of-service) o por los Lineamientos de la Comunidad de GitHub. Si decides hospedar cualquier material promocional o publicitario en tu Contenido de Desarrollador Patrocinado, serás el único responsable de cumplir con todas las regulaciones y leyes aplicables, incluyendo los Lineamientos de la Comisión Federal de Comercio sobre Testimonios y Apoyos. Directrices de la Comisión Federal de Comercio sobre los respaldos y testimonios. + +### 4. Términos financieros. + +#### 4.1. Pago. +GitHub hará el Pago de Desarrollador Patrocinado de acuerdo con esta sección 4, siempre y cuando cumplas con las Obligaciones del Desarrollador Patrocinado descritas en la sección 3 y que no hayas violado ninguna de estas condiciones adicionales. Si algún mes no cumples con estas obligaciones, a nuestra absoluta discreción, podemos retener el Pago del programador patrocinado correspondiente a ese mes. Si no cumples o mantienes las Obligaciones del programador patrocinado durante dos (2) meses o más del Plazo (consecutivos o no consecutivos), GitHub puede cancelar estos Términos adicionales, tal como se describe en la Sección 6. + +#### 4.2. Exclusiones de Pago para el Desarrollador Patrocinado. +Los siguientes montos no están incluidos en los Pagos del programador patrocinado, o GitHub los puede retener, según corresponda. + +##### 4.2.1. Gastos del Desarrollador Patrocinado. +Deberás absorber todos los gastos que generes en relación con tu rendimiento bajo estas Condiciones Adicionales. No te reembolsaremos ni adelantaremos ningún gasto. + +##### 4.2.2. Impuestos. +GitHub pretende cumplir con todas las leyes de reporte de información y retención de impuestos que GitHub determine, razonablemente en su juicio, como aplicables a estos pagos. Si se deben retener impuestos sobre cualquier monto que te pagará GitHub o sobre los montos sujetos a la presentación de información impositiva conforme a las leyes correspondientes, GitHub deducirá tales impuestos del monto adeudado y se los pagará a la autoridad fiscal adecuada. Cuando sea necesario, obtendrá y te hará llegar un recibo oficial por cualquier impuesto retenido, según lo exijan las leyes correspondientes. GitHub hará los esfuerzos razonables para minimizar tales impuestos en la medida que la ley correspondiente lo permita, y cada parte cooperará de manera razonable con la otra parte para lograr las mínimas tasas impositivas o la eliminación de tales impuestos en virtud de las leyes o tratados de impuesto a las ganancias correspondientes. Esto incluye que le proporciones a GitHub la información adecuada requerida conforme a las leyes correspondientes, como los Formularios IRS W-8, W-9 u otra información para establecer exenciones a la retención. También serás responsable de cumplir con todos los términos y condiciones del procesador de pagos externo al respecto de la retención de impuestos y la presentación de informes, si corresponde. Asimismo, GitHub se reserva el derecho a suspender los pagos a tu cuenta hasta que le proporciones a GitHub la documentación o información adecuada requerida conforme a las leyes correspondientes para que GitHub determine cualquier retención de impuestos u obligaciones de presentación de informes que se apliquen a los pagos, de acuerdo con los presentes Términos adicionales o con el Acuerdo. + +##### 4.2.3. Retención de Pagos del Desarrollador Patrocinado por Incumplimiento. +En caso de que un Desarrollador Patrocinado incumpla, o se sospeche que incumpla, el Acuerdo o estas Condiciones Adicionales, GitHub se reserva el derecho de retener los pagos al Desarrollador patrocinado bajo estas Condiciones adicionales o, de otra manera, que estén pendientes de una investigación razonable por parte de GitHub. Si GitHub determina, a su absoluto criterio, que un Desarrollador Patrocinado se encuentra en incumplimiento del Acuerdo o de Estas Condiciones Adicionales, GitHub retendrá permanentemente cualquier cantidad debida al Desarrollador Patrocinado. + +#### 4.3. Plazos de Pago. +Durante el plazo, GitHub te emitirá todos los Pagos de Desarrollador patrocinados recibidos en cualquier mes dentro de 30 días después del cierre de dicho mes, sujeto a las variaciones descritas posteriormente. Los pagos se envían a través de Stripe Connect, transferencia ACH, o transferencia bancaria, a la cuenta bancaria que proporcionaste cuando aplicaste para los Patrocinios de Github. No somos responsables de la demora o la aplicación incorrecta de ningún pago del Programador patrocinado que se deba a que tú o tu banco hayan suministrado información incorrecta o incompleta, o a la falla del banco en la acreditación del pago a tu cuenta. + +- Para Cuentas de Desarrollador Patrocinadas recién creadas, GitHub te emitirá todos los Pagos de Desarrollador Patrocinado que se reciban en cualquier mes dentro de 90 días de la creación de tu Cuenta de Desarrollador Patrocinado, sujeto a las variaciones descritas posteriormente. Los pagos posteriores se emitirán en 30 días desde el cierre de mes, de acuerdo con esta sección. + +- Si se te paga mediante Stripe Connect, recibirás pagos en el día 22 de cada mes de acuerdo con tu balance al final del mes previo, sin importar la cantidad en el balance. + +- Si se te paga por transferencia ACH o transferencia bancaria, recibiras pagos en el tercer jueves del mes. GitHub te emitirá un pago por cada mes en el que tu balance llegue a $100 USD. Las contribuciones del Fondo de Compensación para Patrocinios de GitHub no no cuenta en este umbral. Si tu saldo está por debajo de los $100 al finalizar el mes, el saldo se acumulará hasta la próxima vez que tu saldo esté por encima del límite al finalizar el mes. Si sales de los Patrocinios de GitHub, GitHub emitirá un pago por el restante de tu balance, aún si éste es menor a $100. + +- Después de la terminación, te emitiremos todos los Pagos de Desarrollador Patrocinado, tanto recibidos como no pagados, en aproximadamente 90 días después del fin del mes calendario en el cual ubiquemos que estas Condiciones Adicionales han finalizado. + +#### 4.4. Método de Pago. +Remitiremos los pagos del Programador patrocinado por ACH/SEPA o los giraremos a la cuenta que especifiques, sujeto a los límites, los métodos y los plazos establecidos en nuestras políticas de pago vigentes al momento, que actualizaremos cada cierto tiempo. El método y límite de pago puede variar en función del país y de la información de cuenta que proporciones. Podemos, a nuestro absoluto criterio, combinar el Pago del programador patrocinado con cualquier otro pago que se te pueda deber. + +#### 4.5. Moneda. +Todas las referencias a la moneda son en dólares estadounidenses. Si te encuentras fuera de los Estados Unidos, puede que convirtamos los dólares estadounidenses a la moneda local de tu dirección de pago, utilizando nuestras tasas de conversión vigentes al momento. + +#### 4.6. Requisitos de reembolso. +Serás responsable de especificar los términos y condiciones sobre cualquier reembolso a tus patrocinadores, si hubiera alguno. En ningún caso GitHub será responsable de proporcionar ayuda alguna con los reembolsos, ni será GitHub será responsable del pago de ningún reembolso. + +#### 4.7. Información de pago solicitada. +Para pagarte, nos debes proporcionar la información financiera, impositiva y bancaria completa y precisa que solicitemos (por ejemplo, a través de la creación o configuración de cuenta, o de cualquier otra manera). Te notificaremos por cualquier medio de comunicación acerca de los cambios en el tipo de información que se requiere. Si no cumples en proporcionar de manera adecuada (o en mantener de manera adecuada) tal información, (a) podemos deducir de tu Pago de programador patrocinado cualquier tarifa bancaria relacionada, y (b) podemos poner fin a los presentes Términos adicionales, y puede que pierdas cualquier monto que te adeude GitHub. + +### 5. Declaraciones y garantías, limitación de responsabilidad, resarcimiento. + +#### 5.1. Por el Programador patrocinado. +El programador patrocinado declara y garantiza que: + +* tú tienes la autoridad para celebrar los presentes Términos adicionales y para realizarlos plenamente; + +* la ejecución y realización de los presentes Términos adicionales no violará ningún otro acuerdo u obligación entre tú y cualquier otra parte; + +* el contenido del Programador patrocinado no infringe, viola o malversa ningún derecho de terceros, incluido cualquier derecho de autor, marca comercial, patente, secreto comercial, derecho moral, derecho a la privacidad, derecho de publicidad o cualquier otra propiedad intelectual; + +* cumplirás con todas las leyes y regulaciones, y tu Contenido del programador patrocinado no es ilegal y no viola ninguna ley o regulación. + +#### 5.2. Descargo de garantías, limitación de responsabilidad, resarcimiento. +ACEPTAS DE MANERA EXPLÍCITA QUE LAS SECCIONES O (DESCARGO DE GARANTÍAS), P (LIMITACIÓN DE RESPONSABILIDAD) Y Q (EXENCIÓN Y RESARCIMIENTO) DEL ACUERDO SE APLICAN A LOS PRESENTES TÉRMINOS ADICIONALES. + +### 6. Plazo y terminación. + +#### 6.3. Terminación. +Los presentes Términos adicionales comienzan en la fecha de entrada en vigor y seguirán rigiendo siempre que participes del Programa. + +#### 6.2. Suspensión. +GitHub puede suspender tu Cuenta de programador patrocinado de inmediato si violas de cualquier manera los presentes Términos adicionales o el Acuerdo, o si eres colocado o ubicado en una lista comercial restringida, o si eres residente habitual de un país o territorio sujeto a las sanciones generales que administra la Oficina de Control de Activos Extranjeros (OFAC, por sus siglas en inglés) de los EE. UU. Office of Foreign Assets Control (OFAC). No poder corregir o solucionar el motivo de la suspensión puede dar lugar a la terminación de tu Cuenta de programador patrocinado. + +#### 6.4. Terminación. +Cualquiera de las partes podrá rescindir estos Términos Adicionales y tu Cuenta de Desarrollador Patrocinado en cualquier momento con o sin causa, con o sin previo aviso. Si incumples los presentes Términos adicionales o el Acuerdo, podemos ofrecerte un período para solucionar el incumplimiento, aunque no estamos obligados a hacerlo. + +#### 6. Plazo y terminación. +Si cualquiera de las Partes decide ponerles fin conforme a la Sección 6.3, la única obligación de GitHub será pagarle al Programador patrocinado el monto del Pago del programador patrocinado acumulado hasta la fecha de terminación, a menos que dichos pagos estén prohibidos por ley. + +### 7. Varios. + +#### 7.1. Acuerdo completo. +Los presentes Términos adicionales, junto con el Acuerdo, las Políticas de GitHub, la Declaración de privacidad de GitHub y cualquier término adicional por opciones de monetización diferentes constituyen el acuerdo completo entre tú y GitHub. + +#### 7.2. Modificaciones a los términos. +Nos reservamos el derecho, a nuestro absoluto criterio, de modificar los presentes Términos adicionales en cualquier momento. Te notificaremos acerca de las modificaciones sustanciales de los presentes Términos adicionales, tales como los cambios de precio, al menos 30 días antes de que entren en vigor, por medio de la publicación de un aviso en nuestro sitio web. La continuación de tu participación en el Programa implica que acuerdas con nuestras revisiones de los presentes Términos adicionales. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-. + +#### 7.3. Beneficiarios externos. +Con excepción de lo indicado expresamente, no se considerará que ninguna persona, firma, grupo o corporación además de las partes haya adquirido ningún derecho en virtud de ningún contenido de los presentes Términos adicionales. + +#### 7.4. Contratistas independientes. +Las partes son contratistas independientes. Ninguna parte es empleadora, empleada, agente, socia o representante legal de la otra para ningún propósito, y ninguna tiene ningún derecho, poder o autoridad para generar ninguna obligación o responsabilidad en nombre de la otra. + +#### 7.5. Publicidad. +Podemos emitir un comunicado de prensa u otra comunicación pública relacionada con tu participación en el Programa. diff --git a/translations/es-ES/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/es-ES/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md new file mode 100644 index 0000000000000..40f6921f85a17 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md @@ -0,0 +1,107 @@ +--- +title: Acuerdo de GitHub contra la esclavitud moderna y el trabajo infantil +redirect_from: + - /articles/github-statement-against-modern-slavery-and-child-labor +versions: + free-pro-team: '*' +--- + +*Declaración 2018* + +Según la organización internacional del trabajo (OIT), [40 millones de personas fueron víctimas de la esclavitud moderna y 152 millones niños fueron sometidos a trabajo infantil](https://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_574717/lang--en/index.htm) globalmente en 2016. Como lo informa la OIT[](https://www.ilo.org/global/topics/forced-labour/lang--en/index.htm): + - 1 de cada 4 víctimas de esclavitud moderna son niños. + - De los 24.9 millones de personas atrapadas en el trabajo forzoso, se explotan 16 millones personas en el sector privado, como el trabajo doméstico, la construcción o la agricultura; 4.8 millones de personas en la explotación sexual forzada y 4 millones de personas en el trabajo forzoso impuestas por las autoridades del estado. + - Las mujeres y las niñas se ven afectadas de manera desproporcionada por el trabajo forzoso, que representa el 99% de las víctimas en la industria sexual comercial y el 58% en otros sectores. + +GitHub deplora la presencia y la persistencia de la esclavitud moderna y el trabajo infantil y toma en serio su responsabilidad de asegurar que ni la esclavitud moderna ni el trabajo infantil se lleven a cabo en su cadena de suministro o en cualquier parte de su negocio. ("Esclavitud moderna" en esta declaración se refiere a la esclavitud, el trabajo forzoso u obligatorio, el tráfico, la servidumbre y los trabajadores que están encarcelados, identificados o Unidos. "Trabajo infantil" se refiere al trabajo realizado por alguien menor de 16 años de edad o menor de 14 años para trabajo liviano, considerando que no se limite a los periodos que interfieaen con la educación del niño y no en condiciones que interfieran con la salud o el bienestar del niño.) + +De acuerdo con la [Ley de Esclavitud Moderna del Reino Unido](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), y en cumplimiento con el [ILO 2014 Protocolo para la Convención de Trabajo Forzado](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029)", la [ILO Declaración de Principios Fundamentales y Derechos en el Trabajo](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), y la [meta 8.7 de las Metas de Desarrollo Sostenible de las Naciones Unidas](https://sustainabledevelopment.un.org/sdg8), esta Declaración de 2018 Contra la Esclavitud Moderna y el Trabajo Infantil ("la Declaración") describe los pasos que ha tomado GitHub para prevenir que se suscite la esclavitud moderna y el trabajo infantil en su negocio o cadena de suministro. + +### La estructura, empresas y las cadenas de suministro de GitHub + +GitHub es una plataforma de desarrollo de software con su sede en San Francisco y empleados y contratistas que trabajan en numerosos países. + +Todos los empleados de GitHub y los contratistas independientes individuales son voluntarios y están a la misma disposición. GitHub tiene una mano de obra distribuida en gran medida y se esfuerza por brindar compensaciones y beneficios competitivos a sus empleados y contratistas, independientemente de su ubicación. Esto es cierto ya sea que contratemos contratistas independientes directamente o a través de un intermediario. + +GitHub no conduce la manufactura o produce hardware, ni GitHub utiliza agencias de reclutamiento para los tipos de servicios a menudo realizados por los trabajadores migrantes. La naturaleza del negocio de GitHub no la somete a cambios repentinos en las presiones de carga de trabajo o de precios, que a menudo impulsan la demanda de prácticas que aumentan el riesgo de trabajo forzoso en las cadenas de suministro, como las horas extras forzadas. + +GitHub ofrece software gratuito y de pago y software basado en la web como un servicio para los clientes en todo el mundo. Los productos de GitHub incluyen: + - GitHub.com: Colaboración basada en la web y plataforma de hospedaje de código + - GitHub Enterprise: Colaboración local y software de alojamiento de código + - Atom: Editor de texto + - Electron: Marco para escribir aplicaciones multiplataforma de escritorio + - Escritorio de GitHub: Aplicación de escritorio para acceder a GitHub.com y GitHub Enterprise + +La cadena de suministro de GitHub está formada por bienes y servicios para nuestros productos y operaciones que incluyen servicios de computación, planificación de eventos, compra de artículos comerciales y promocionales, suministros de oficina y arrendamiento de instalaciones, como espacios de oficinas y centros de datos. + +### Políticas en relación con la esclavitud moderna y el trabajo infantil + +#### Esclavitud moderna y trabajo infantil + +**El código de ética de GitHub** prohíbe usar, participar, apoyar o tolerar de manera consciente la esclavitud moderna (esclavitud, trabajo forzoso u obligatorio, tráfico, servidumbre o trabajadores que están encarcelados, matriculados o adheridos) o trabajo infantil en sus operaciones comerciales. Cualquier empleado o contratista de GitHub que viole esta prohibición estará sujeto a la terminación de la relación laboral o comercial. + +**Los estándares de conducta de GitHub** prohíben conductas inseguras e ilegales, que incluyen el uso a sabiendas, la participación, el apoyo o la tolerancia de la esclavitud moderna (esclavitud, trabajo forzoso u obligatorio, tráfico, servidumbre o trabajadores que están encarcelados, identificados o vinculados) o trabajo infantil. + +GitHub cumple con las leyes que prohíben la trata y el trabajo infantil en las jurisdicciones en las que opera, incluyendo la [Regulación de adquisición federal de EE. UU. 22.17 sobre la lucha contra la trata de personas](https://www.govinfo.gov/content/pkg/CFR-2009-title48-vol1/pdf/CFR-2009-title48-vol1-part22-subpart22-17.pdf). + +Además, GitHub estableció una asociación con el programa FairHotel, lo que significa que GitHub alienta a sus empleados a elegir Hoteles aprobados por FairHotel, donde los trabajadores tienen salarios justos, beneficios adecuados y una voz en el trabajo. Ser un socio de FairHotel también significa que GitHub brinda negocios a los hoteles como un empleador justo. + +En el futuro, GitHub comunicará esta declaración a todos los empleados, contratistas y proveedores, incluyendo reclutadores y agencias de empleo. Además, GitHub está desarrollando capacitación para todos los empleados de GitHub sobre esclavitud moderna y trabajo infantil. Github [publica su declaración frente a la esclavitud moderna y el trabajo infantil públicamente.](/articles/github-statement-against-modern-slavery-and-child-labor) + +GitHub tiene una política de no represalias para informar las inquietudes relacionadas con el lugar de trabajo. De acuerdo con esta afirmación, GitHub les permite a los empleados y contratistas informar las propuestas relacionadas con la esclavitud moderna y el trabajo infantil sin temor a represalias. + +### Legislaciones y prácticas laborales + +Las prácticas laborales de GitHub son + +**justas**: + - GitHub paga a sus empleados y contratistas un salario justo, de acuerdo con los salarios legales aplicables + - GitHub mantiene condiciones de trabajo humanas + - GitHub no requiere que los trabajadores excedan las horas máximas de trabajo diario establecidas por las leyes o regulaciones locales y nacionales + - GitHub paga a sus empleados y contratistas de manera oportuna, con documentación (como un talón de pago) que indica la base sobre la que se les paga y mantiene los registros de los empleados de acuerdo con las leyes locales y nacionales + +**humanas y éticas**: + - GitHub usa solo mano de obra voluntaria + - GitHub prohíbe el trabajo infantil + - GitHub no participa en disciplina física o abuso + - GitHub no tolera acoso o discriminación ilegal en la fuerza laboral o en el lugar de trabajo + +**respetuosas**: + - GitHub protege los derechos de sus empleados a la libertad de asociación y la negociación colectiva de acuerdo con los requisitos legales, incluyendo el de publicar avisos legales de los derechos de los empleados conforme a la ley nacional de relaciones laborales + - GitHub brinda beneficios a los empleados en exceso o por encima de los niveles esperados en la industria + - GitHub invita a los empleados a informar cualquier queja en el lugar de trabajo y no tolera represalias por informar + +### Procesos de diligencia debida en relación con la esclavitud moderna y el trabajo infantil en sus cadenas comerciales y de suministro + +GitHub evalúa su cadena de negocio y de suministro para los riesgos relacionados con la esclavitud moderna y el trabajo infantil. Aprovechando la experiencia interna y externa en materia de derechos humanos, GitHub participó en un análisis de funcionalidad cruzada (que incluye políticas, asesoría legal, adquisiciones, finanzas y operaciones, especialmente recursos humanos) para determinar dónde existen los servicios laborales en su cadena de negocios y de suministro y para identificar los riesgos potenciales relacionados con la esclavitud moderna y el trabajo infantil. GitHub prioriza las áreas en las que esos riesgos pueden ser más significativos en términos de gravedad, escala o probabilidad para una mayor diligencia debida, monitoreo y verificación. GitHub continúa considerando dónde pueden ocurrir riesgos y cómo abordarlos. Además, GitHub ahora obtiene la certeza de sus proveedores de que tienen prácticas consistentes con esta declaración, incluso al cumplir con las leyes relacionadas con la esclavitud moderna o el trabajo infantil. + +### Lugares en las cadenas de negocios y suministros de GitHub donde hay un riesgo de esclavitud moderna y trabajo infantil y los pasos que GitHub ha tomado para evaluar y administrar dicho riesgo + +GitHub no identificó a ningún proveedor de alto riesgo; sin embargo, la esclavitud moderna o el trabajo infantil sería más probable que ocurra con los proveedores de servicios que implican mano de obra manual, como el apoyo a eventos, construcción, servicios de instalaciones y servicios de alimentos. GitHub auditará a sus proveedores existentes y requerirá que aquellos en esas áreas de mayor riesgo confirmen que brindan servicios consistentes con esta declaración. + +A pesar de que GitHub no sabe de ninguna esclavitud moderna o alegada moderna o trabajo infantil en su cadena de negocios o de suministro y no tiene una base creíble para creer que está ocurriendo, GitHub se compromete a proveer remedios si GitHub en sí misma causara la esclavitud moderna o el trabajo infantil y la remediación de patrones más amplios de no conformidad con esta declaración causada por deficiencias en los sistemas o procesos. La remediación de GitHub a las víctimas individuales incluiría protocolos de acción inmediata adecuada para eliminar las prácticas modernas de esclavitud y trabajo infantil, junto con recursos para servicios razonables y apropiados de víctimas diseñados para compensar el daño experimentado. + +### Efectividad para asegurar que no se esté produciendo la esclavitud moderna ni el trabajo infantil en las cadenas comerciales o de suministro de GitHub + +GitHub cumple y seguirá cumpliendo con las leyes relacionadas con la esclavitud moderna y el trabajo infantil. + +En el futuro, GitHub ahora requiere que sus proveedores cumplan con esta declaración, así como con las leyes relacionadas con la esclavitud moderna y el trabajo infantil. GitHub ahora también requiere que sus proveedores: + - no usen, participen, apoyen o toleren la esclavitud moderna o el trabajo infantil + - no utilicen prácticas engañosas o fraudulentas de reclutamiento o compromiso para empleados o trabajadores contratados + - no cobren a los empleados o a los trabajadores contratados cuotas de compromiso + - no destryan, oculten, confisquen o nieguen el acceso de un empleado o de cualquier trabajador contratante al pasaporte, la licencia de conducir u otros documentos de identidad; + - nos permitan terminar nuestros acuerdos con ellos por cualquier violación de sus obligaciones relacionadas con la esclavitud moderna o el trabajo infantil; y + - remedien cualquier daño causado a cualquier trabajador que se encuentre sometido a cualquier forma de esclavitud moderna o trabajo infantil, si así lo solicita la ley. + +Además, GitHub recomienda firmemente a sus proveedores que: + - lleven a cabo procesos antimodernos de esclavitud y diligencia debida del trabajo infantil, incluyendo evaluaciones de riesgo, para sus proveedores; + - tomen medidas para abordar riesgos identificados; y + - utilicen una esclavitud antimoderna similar y un lenguaje de trabajo infantil con sus proveedores. + +Las instrucciones de contratación de GitHub a los empleados que realizan compras de la empresa ahora incluyen una referencia al requisito de que los proveedores cumplan con el código de conducta del proveedor de Microsoft o esta declaración. + +### Capacitación para el personal de GitHub sobre la esclavitud moderna y la trata de personas + +GitHub está desarrollando la esclavitud moderna y la capacitación de trabajo infantil que será obligatoria para todos los empleados, con vistas a los negocios y la cadena de suministro de GitHub. GitHub hará hincapié en los proveedores que prestan servicios relacionados con el trabajo manual, como el apoyo a eventos, la construcción, los servicios de instalaciones y los servicios de alimentos, como áreas de mayor riesgo potencial. + +**El Consejo de administración de GitHub aprobó [esta declaración](/assets/images/help/site-policy/github-statement-against-modern-slavery-and-child-labor.pdf).** diff --git a/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md new file mode 100644 index 0000000000000..26166ac1191dd --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md @@ -0,0 +1,79 @@ +--- +title: Subprocesadores y cookies de GitHub +redirect_from: + - /subprocessors/ + - /github-subprocessors/ + - /github-tracking/ + - /github-cookies/ + - /articles/github-subprocessors-and-cookies +versions: + free-pro-team: '*' +--- + +Effective date: **January 6, 2021** + +GitHub ofrece una gran cantidad de transparencia en cuanto a cómo usamos tus datos, cómo recopilamos tus datos y con quién los compartimos. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). + +### Subprocesadores de GitHub + +Cuando compartimos tu información con subprocesadores de terceros, como nuestros vendedores y proveedores de servicios, seguimos siendo responsables de ella. Trabajamos arduamente para mantener tu confianza cuando traemos nuevos proveedores y exigimos que todos los proveedores celebren acuerdos de protección de datos con nosotros que restrinjan su procesamiento de la información personal de los usuarios (tal como se define en la [Declaración de Privacidad](/articles/github-privacy-statement/)). + +| Nombre del subprocesador | Descripción del procesamiento | Ubicación del procesamiento | Ubicación Corporativa | +|:------------------------ |:----------------------------------------------------------- |:--------------------------- |:--------------------- | +| Automattic | Servicio de alojamiento | Estados Unidos | Estados Unidos | +| AWS Amazon | Alojamiento de datos | Estados Unidos | Estados Unidos | +| Braintree (PayPal) | Procesador de pagos de suscripción con tarjeta de crédito | Estados Unidos | Estados Unidos | +| Clearbit | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | +| Discourse | Proveedor de software del foro de la comunidad | Estados Unidos | Estados Unidos | +| Eloqua | Automatización de campañas de marketing | Estados Unidos | Estados Unidos | +| Google Apps | Infraestructura interna de la empresa | Estados Unidos | Estados Unidos | +| Google Analytics | Analítica y rendimiento | Estados Unidos | Estados Unidos | +| MailChimp | Proveedor de servicios de correo de billetaje de clientes | Estados Unidos | Estados Unidos | +| Mailgun | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | +| Microsoft | Servicios de Microsoft | Estados Unidos | Estados Unidos | +| Monday.com | Plataforma de colaboración en equipo y gestión de proyectos | Estados Unidos | Israel | +| Nexmo | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | +| Salesforce.com | Gestión de relaciones con clientes | Estados Unidos | Estados Unidos | +| Sendgrid | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | +| Sentry.io | Proveedor de monitoreo de aplicaciones | Estados Unidos | Estados Unidos | +| Stripe | Proveedor de pagos | Estados Unidos | Estados Unidos | +| Twilio | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | +| Zendesk | Sistema de tickets de soporte al cliente | Estados Unidos | Estados Unidos | +| Zuora | Sistema de facturación corporativa | Estados Unidos | Estados Unidos | + +Cuando traemos un nuevo subprocesador que maneja la información personal de nuestros usuarios o eliminas un subprocesador, o cambiamos la manera en que usamos un subprocesador, actualizaremos esta página. Si tienes preguntas o inquietudes acerca de un nuevo subprocesador, estaremos encantados de ayudarte. Ponte en contacto con nosotros vía{% data variables.contact.contact_privacy %}. + +### Cookies en GitHub + +GitHub uses 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. Por favor, echa un vistazo a nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) si te gustaría obtener más información sobre las cookies y sobre cómo y por qué las utilizamos. + +Ya que la cantidad y los nombres de las cookies podrían cambiar, la siguiente tabla podría actualizarse de vez en cuándo. + +| Proveedor de servicios | Nombre de la Cookie | Descripción | Vencimiento* | +|:---------------------- |:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------ | +| GitHub | `app_manifest_token` | Esta cookie se utiliza durante el flujo del manifiesto de la app para mantener su estado durante la redirección para obtener una sesión de usuario. | cinco minutos | +| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | un año | +| GitHub | `dotcom_user` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | +| GitHub | `_gh_ent` | Esta cookie se utiliza para la aplicación temporal y el estado del marco de trabajo entre las páginas como en qué paso se encuentra el cliente dentro de un formulario de varios pasos. | dos semanas | +| GitHub | `_gh_sess` | Esta cookie se usa para la aplicación temporal y el estado del marco entre las páginas copara indicar en qué paso está el usuario en un formulario de múltiples pasos. | session | +| GitHub | `gist_oauth_csrf` | Esta cookie se establece por Gist para asegurar que el usuario que inició el flujo OAuth sea el mismo usuario que lo completa. | se borra al validar el estado de oauth | +| GitHub | `gist_user_session` | Esta cookie es usada por Gist cuando se ejecuta en un host por separado. | dos semanas | +| GitHub | `has_recent_activity` | Esta cookie se utiliza para prevenir que se muestre la seguridad que es intersticial a los usuarios que han visitado la app recientemente. | una hora | +| GitHub | `__Host-gist_user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | +| GitHub | `__Host-user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | +| GitHub | `logged_in` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | +| GitHub | `marketplace_repository_ids` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | +| GitHub | `marketplace_suggested_target_id` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | +| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | un año | +| GitHub | `org_transform_notice` | Esta cookie se utiliza para proporcionar notificaciones durante las transformaciones de las organizaciones. | una hora | +| GitHub | `private_mode_user_session` | Esta cookie se utiliza para las solicitudes de autenticación empresarial. | dos semanas | +| GitHub | `saml_csrf_token` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_csrf_token_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_return_to` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_return_to_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | +| GitHub | `user_session` | Esta cookie se utiliza para que inicies sesión. | dos semanas | + +_*_ Las fechas de **vencimiento** para las cookies que se listan a continuación generalmente se aplican permanentemente. + +(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. Por ejemplo, es posible que insertamos contenido, como vídeos, desde otro sitio que establezca una cookie. Si bien tratamos de minimizar estas cookies de terceros, no siempre podemos controlar qué cookies establece este contenido de terceros. diff --git a/translations/es-ES/content/github/site-policy/github-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-terms-of-service.md new file mode 100644 index 0000000000000..8376e86b84b21 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-terms-of-service.md @@ -0,0 +1,312 @@ +--- +title: Términos de servicio de GitHub +redirect_from: + - /tos/ + - /terms/ + - /terms-of-service/ + - /github-terms-of-service-draft/ + - /articles/github-terms-of-service +versions: + free-pro-team: '*' +--- + +¡Gracias por usar GitHub! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio antes de ingresar o usar GitHub. Ya que se trata de un contrato tan importante entre nosotros y nuestros usuarios, intentamos ser muy claros. Para tu comodidad, presentamos estos términos en un breve resumen no vinculante seguido de los términos legales completos. + +### Resumen + +| Sección | ¿Qué puedes encontrar allí? | +| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [A. Definiciones](#a-definitions) | Algunos términos básicos, definidos de forma que te ayude a entender este acuerdo. Consulta la copia de seguridad de esta sección para obtener una aclaración. | +| [B. Términos de la cuenta](#b-account-terms) | Estos son los requisitos básicos para tener una cuenta en GitHub. | +| [C. Uso aceptable](#c-acceptable-use) | Estas son las reglas básicas que debes seguir cuando uses tu cuenta de GitHub. | +| [D. Contenido generado por el usuario](#d-user-generated-content) | Eres responsable del contenido que publicas en GitHub. Sin embargo, tienes ciertas responsabilidades al respecto y te pedimos que nos otorgues algunos derechos de manera que podamos proporcionarte los servicios. | +| [E. Repositorios privados](#e-private-repositories) | Esta sección expone cómo tratará GitHub el contenido que publiques en los repositorios privados. | +| [F. Copyright & Política DMCA](#f-copyright-infringement-and-dmca-policy) | Esta sección explica la forma en la que GitHub responderá si crees que alguien está infringiendo tus derechos de autor en GitHub. | +| [G. Notificación de propiedad intelectual](#g-intellectual-property-notice) | Describe los derechos de GitHub en el sitio web y el servicio. | +| [H. Términos de la API](#h-api-terms) | Estas son las reglas para usar las API de GitHub, ya sea que estés usando la API para el desarrollo o la recopilación de datos. | +| [I. Términos de producto adicionales](#i-github-additional-product-terms) | Tenemos algunas reglas específicas para las características y productos de GitHub. | +| [J. Vista previa Beta](#j-beta-previews) | Estos son algunos de los términos adicionales que se aplican a las características de GitHub que continúan en desarrollo. | +| [K. Pago](#k-payment) | Eres responsable del pago. Somos responsables de facturarte con exactitud. | +| [L. Cancelación y terminación](#l-cancellation-and-termination) | Puedes cancelar este acuerdo y cerrar tu cuenta en cualquier momento. | +| [M. Comunicaciones con GitHub](#m-communications-with-github) | Sólo utilizamos el correo electrónico y otros medios electrónicos para estar en contacto con nuestros usuarios. No ofrecemos soporte telefónico. | +| [N. Exención de garantías](#n-disclaimer-of-warranties) | Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. **Lee esta sección cuidadosamente; deberías entender qué esperar.** | +| [O. Limitación de responsabilidad](#o-limitation-of-liability) | No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. **Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.** | +| [P. Liberación e indemnización](#p-release-and-indemnification) | Eres completamente responsable de tu uso del servicio. | +| [Q. Cambios a estos Términos de Servicio](#q-changes-to-these-terms) | Podemos modificar este acuerdo, pero te avisaremos con 30 días de antelación de cambios materiales. | +| [R. Varios](#r-miscellaneous) | Consulta esta sección para obtener detalles legales, incluyendo nuestra elección de la ley. | + +### Términos de servicio de GitHub +Fecha de entrada en vigencia: 16 de noviembre de 2020 + + +### A. Definiciones +**Versión resumida:** *Utilizamos estos términos básicos a lo largo del acuerdo y tienen significados específicos. Es necesario que comprendas el significado de cada uno de nuestros términos. No habrá una evaluación sobre ello, pero es información útil.* + +1. Una "Cuenta" representa tu relación legal con GitHub. Una "Cuenta de Usuario" representa la autorización individual del Usuario para iniciar sesión y utilizar el Servicio y sirve como identidad del Usuario en GitHub. “Organización” se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Una Cuenta de Usuario puede ser miembro de cualquier número de organizaciones. +2. El "Acuerdo" se refiere, colectivamente, a todos los términos, condiciones, avisos contenidos o a los que se hace referencia en el presente documento (los "Términos de Servicio" o los "Términos") y todas las demás reglas de funcionamiento, políticas (incluyendo la Declaración de Privacidad de GitHub, disponible en [github.com/site/privacy](https://github.com/site/privacy)) y procedimientos que podemos publicar de vez en cuando en el Sitio Web. La mayoría de nuestras políticas de sitio están disponibles en [docs.github.com/categories/site-policy](/categories/site-policy). +3. "Vistas Previas Beta" se refiere al software, los servicios o las características identificadas como alfa, beta, vista previa, acceso temprano o evaluación o a las palabras o frases con significados similares. +4. "Contenido" se refiere al contenido presentado o mostrado a través del sitio web, incluyendo, sin limitación al código, texto, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, paquetes, diseños, características y otros materiales disponibles en el Sitio Web o disponibles de otra forma a través del Servicio. "Contenido" también incluye Servicios. “Contenido generado por el usuario” es Contenido, escrito o no, creado o cargado por nuestros Usuarios. "Tu Contenido" es Contenido que creas o posees. +5. “GitHub” y “Nosotros” se refieren a GitHub, Inc., así como a nuestros afiliados, directores, subsidiarios, contratistas, licenciadores, oficiales, agentes y empleados. +6. El “Servicio” se refiere a las aplicaciones, software, productos y servicios proporcionados por GitHub, incluyendo cualquier Vista Previa Beta. +7. “El Usuario”, “Tú” y “tu” se refieren a la persona, empresa u organización que ha visitado o está utilizando el Sitio Web o Servicio; que ingresa o utiliza cualquier parte de la Cuenta; o que dirije el uso de la Cuenta en el desempeño de sus funciones. Un usuario debe tener al menos 13 años de edad. Las condiciones especiales pueden aplicarse para cuentas empresariales o gubernamentales (véase [Section B(5): Términos Adicionales](#5-additional-terms)). +8. El "Sitio Web" se refiere al sitio web de GitHub ubicado en [github. om](https://github.com/) y todos los contenidos, servicios y productos proporcionados por GitHub en o a través del sitio web. También se refiere a subdominios propiedad de GitHub de github.com, tales como [education.github.com](https://education.github.com/) y [pages.github.com](https://pages.github.com/). Estos Términos también rigen los sitios web de la conferencia de GitHub, como [githubuniverse.com](https://githubuniverse.com/) y sitios web de productos, como [atom.io](https://atom.io/). Ocasionalmente, los sitios web propiedad de GitHub pueden proporcionar condiciones de servicio diferentes o adicionales. Si estos términos adicionales entran en conflicto con este Contrato, los términos más específicos se aplican a la página o servicio correspondiente. + +### B. Términos de la cuenta +**Versión resumida:** *Las Cuentas de Usuario y las Organizaciones tienen diferentes controles administrativos; una persona debe crear tu cuenta; debes tener 13 años o más; debes proporcionar una dirección de correo electrónico válida; y no es posible tener más de una cuenta gratuita. Eres el único responsable de tu Cuenta y de todo lo que ocurra mientras estas conectado o usando tu Cuenta. Eres responsable de mantener tu cuenta segura.* + +#### 1. Controles de la cuenta +- Usuarios. Sujeto a estos términos, conserva el control administrativo definitivo sobre tu cuenta de usuario y el Contenido dentro de ella. + +- Organizaciones. El "propietario" de una Organización que fue creada bajo estos Términos tiene el control administrativo final sobre esa Organización y el Contenido dentro de ella. Dentro del Servicio, un propietario puede administrar el acceso del Usuario a los datos y proyectos de la Organización. Una Organización puede tener múltiples propietarios, pero debe haber al menos una Cuenta de Usuario designada como propietario de una Organización. Si eres el propietario de una Organización bajo estos términos, te consideramos responsable de las acciones que se llevan a cabo en o a través de dicha Organización. + +#### 2. Información requerida +Debes proporcionar una dirección de correo electrónico válida para completar el proceso de registro. Cualquier otra información solicitada, como tu nombre real, es opcional, a menos que aceptes estos términos en nombre de una entidad legal (en cuyo caso necesitamos más información sobre la entidad legal) o si optas por una [Cuenta de pago](#k-payment), en cuyo caso será necesaria información adicional para fines de facturación. + +#### 3. Requisitos de la cuenta +Tenemos unas cuantas reglas simples para cuentas de usuario en el servicio de GitHub. +- Debes ser una persona para crear una cuenta. No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados. Permitimos cuentas de máquina: +- Una cuenta de máquina se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. No puedes mantener más de una cuenta de máquina gratuita además de tu cuenta de usuario gratuita. +- Una persona o entidad legal no puede mantener más de una cuenta gratuita (si también decide controlar una cuenta de máquina, está bien, pero sólo se puede utilizar para ejecutar una máquina). +- Debes ser mayor de 13 años. Si bien estamos encantados de ver a los geniales programadores jóvenes entusiasmados aprendiendo a programar, debemos cumplir con la ley de los Estados Unidos. GitHub no dirige nuestro Servicio a niños menores de 13 años y no permitimos ningún Usuario menor de 13 años en nuestro Servicio. Si tenemos conocimiento de algún usuario menor de 13 años, [daremos por terminada inmediatamente la cuenta del usuario](#l-cancellation-and-termination). Si estás ubicado en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. +- Su inicio de sesión sólo puede usarse por una persona — es decir, un único inicio de sesión no puede ser compartido por varias personas. Una Organización de pago sólo puede proporcionar acceso a tantas cuentas de usuario como su suscripción lo permita. +- No puedes usar GitHub en violación de las leyes de control de exportación o sanciones de los Estados Unidos o de cualquier otra jurisdicción aplicable. No puedes usar GitHub si estás trabajando o en nombre de un [Nacional Especialmente Diseñado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o una persona sujeta a prohibiciones similares de bloqueo o denegadas por una agencia gubernamental de EE. UU. government agency. GitHub puede permitir que personas en ciertos países o territorios sancionados accedan a ciertos servicios de GitHub de conformidad con las autorizaciones del gobierno de los Estados Unidos. government authorizations. For more information, please see our [Export Controls policy](/articles/github-and-export-controls). + +#### 4. Seguridad de la cuenta de usuario +Eres responsable de mantener tu Cuenta segura mientras utilizas nuestro Servicio. Ofrecemos herramientas como autenticación de dos factores para ayudarte a mantener la seguridad de tu cuenta pero el contenido de tu Cuenta y su seguridad depende de ti. +- Eres responsable de todo el contenido publicado y la actividad que se produzca bajo tu Cuenta (incluso cuando el contenido sea publicado por otros que tienen Cuentas bajo tu Cuenta). +- Eres responsable de mantener la seguridad de tu cuenta y contraseña. GitHub no será responsable de ninguna pérdida o daño que surja del incumplimiento de esta obligación de seguridad. +- Debes notificar inmediatamente [a GitHub](https://support.github.com/contact) si tienes conocimiento de cualquier uso no autorizado, o acceso a nuestro Servicio a través de tu Cuenta, incluyendo cualquier uso no autorizado de tu contraseña o Cuenta. + +#### 5. Términos adicionales +En algunas situaciones, pueden aplicarse términos de terceros a tu uso de GitHub. Por ejemplo, puedes ser miembro de una Organización en GitHub con tus propios términos o acuerdos de licencia; puedes descargar una aplicación que se integre con GitHub; o puedes usar el Servicio para autenticarte a otro servicio. Ten en cuenta que aunque estos Términos son nuestro acuerdo total contigo, los términos de otras partes rigen sus relaciones contigo. + +Si eres un usuario del gobierno o de otro modo accedes o utilizas cualquier servicio de GitHub en una capacidad gubernamental, esta [Enmienda del Gobierno a los Términos de Servicio de GitHub](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) aplican para ti y debes aceptar sus disposiciones. + +Si te registraste en la nube GitHub Enterprise, la [ Apéndice Enterprise Cloud ](/articles/github-enterprise-cloud-addendum/) aplica para ti y debes aceptar sus disposiciones. + +### C. Uso aceptable +**Versión simplificada:** *GitHub presenta una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con los términos de esta sección, que incluyen algunas restricciones sobre el contenido que puedes publicar, que realizar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí.* + +Tu uso del sitio web y del servicio no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o de marcas, leyes de control de exportación o sanciones, u otras leyes de su jurisdicción. Eres responsable de asegurarte que tu uso del Servicio cumpla con las leyes y cualquier normativa aplicable. + +Aceptas que en ningún caso violarás nuestras [Políticas de uso aceptable](/articles/github-acceptable-use-policies) o [Directrices de la comunidad](/articles/github-community-guidelines). + +### D. Contenido generado por el usuario +/**Versión resumida+*:** *Eres propietario del contenido que creas, pero nos permitirás ciertos derechos para que podamos mostrar y compartir el contenido que publiques. Continúas teniendo el control sobre tu contenido y responsabilidad por el mismo y los derechos que nos concedes están limitados a aquellos que necesitamos para proporcionar el servicio. Tenemos derecho a eliminar el contenido o cerrar cuentas si lo necesitamos.* + +#### 1. Responsabilidad para el Contenido generado por el usuario +Puedes crear o cargar Contenido generado por el Usuario mientras usas el Servicio. Eres el único responsable del contenido y por cualquier daño que resulte de cualquier Contenido generado por el Usuario que publiques, cargues, enlaces o que de otra forma esté disponible a través del Servicio, independientemente de la forma de dicho Contenido. No eres responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. + +#### 2. GitHub puede eliminar contenido +Tenemos el derecho de rechazar o eliminar cualquier contenido generado por el usuario que, a nuestro exclusivo criterio, viole alguna ley o [términos o políticas de GitHub](/github/site-policy). El contenido generado por el usuario que se muestra en GitHub para móvil puede estar sujeto a los términos adicionales de las tiendas de aplicaciones móviles. + +#### 3. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia +Conservas la propiedad y la responsabilidad de tu contenido. Si estás publicando algo que no hayas creado tu mismo o de lo cual no posees los derechos, aceptas que eres responsable de cualquier Contenido que publiques; que sólo enviarás contenido que tengas derecho a publicar; y que cumplirás plenamente con cualquier licencia de terceros relacionada con el Contenido que publiques. + +Ya que conservas la propiedad y la responsabilidad de tu contenido, necesitamos que nos concedas — y a otros usuarios de GitHub — ciertos permisos legales, listados en las Secciones D. — D.7. Estas licencias se aplican a Tu Contenido. Si cargas Contenido que ya viene con una licencia que le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. Debes comprender que no recibirás ningún pago por ninguno de los derechos otorgados en las Secciones D.4 — D.7. Las licencias que nos concedes terminarán cuando retires Tu Contenido de nuestros servidores, a menos que otros Usuarios lo hayan bifurcado. + +#### 4. Licencia otorgada +Necesitamos el derecho legal de hacer cosas como alojar Tu Contenido, publicarlo y compartirlo. Nos otorgas a nosotros y a nuestros sucesores legales el derecho a almacenar, archivar, analizar y mostrar tu contenido, y hacer copias incidentales, según sea necesario para proporcionar el servicio, incluyendo la mejora del servicio con el paso del tiempo. Esta licencia incluye el derecho a hacer cosas como copiarlo en nuestra base de datos y hacer copias de seguridad; mostrártelo y a otros usuarios; analizarlo en un índice de búsqueda o analizarlo de cualquier otra manera en nuestros servidores; compartirlo con otros usuarios; y reproducirlo, en caso de que tu contenido sea algo así como música o video. + +Esta licencia no le otorga a GitHub el derecho a vender tu contenido. Tampoco le otorga a GitHub el derecho a distribuir o usar tu contenido fuera de nuestra prestación del servicio, excepto que como parte del derecho a archivar tu contenido, GitHub pueda permitir que nuestros socios almacenen y archiven tu contenido en repositorios públicos en conexión con el [GitHub Arctic Code Vault y el programa de archivado de GitHub](https://archiveprogram.github.com/). + +#### 5. Otorgamiento de la licencia a otros Usuarios +Cualquier contenido generado por el usuario que postees públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de otros usuarios, puede ser visto por otros. Al configurar tus repositorios para ser vistos públicamente, aceptas permitir a otros ver y "bifurcar" tus repositorios (esto significa que otros pueden hacer sus propias copias de Contenido de tus repositorios en los repositorios que controlan). + +Si configuras tus páginas y repositorios para ser vistos públicamente, estás otorgando a cada usuario de GitHub una licencia no exclusiva a nivel mundial para usar, mostrar, y reproducir Tu Contenido a través del Servicio de GitHub y para reproducir Tu Contenido únicamente en GitHub según lo permitido a través de la funcionalidad de GitHub (por ejemplo, a través de bifurcación). Puedes otorgar derechos adicionales si [adoptas una licencia](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Si estás cargando Contenido que no creaste ni posees, eres responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos. + +#### 6. Contribuciones conforme a la Licencia del repositorio +Cada vez que agregas contenido a un repositorio que contiene un aviso de una licencia, tienes la licencia de ese contenido bajo los mismos términos, y aceptas que tienes el derecho de licenciar dicho contenido conforme a esos términos. Si tienes un acuerdo por separado para licenciar dicho contenido bajo diferentes términos, como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. + +¿No es así justo como funciona ahora? Sí. Esto se acepta ampliamente como la norma en la comunidad de código abierto; se conoce comúnmente por el abreviado "inbound=outbound". Lo estamos haciendo explícito. + +#### 7. Derechos morales +Conservas todos los derechos morales sobre Tu Contenido que cargas, publicas o envías a cualquier parte del Servicio, incluyendo los derechos de integridad y atribución. Sin embargo, renuncias a estos derechos y aceptas no ejercerlos contra nosotros para ejercer razonablemente los derechos otorgados en la Sección D.4, pero no de otra manera. + +En la medida en que este acuerdo no sea exigible por la legislación aplicable, concedes a GitHub los derechos que necesitamos para usar Tu Contenido sin atribución y para hacer adaptaciones razonables de Tu Contenido según sea necesario para prestar el Sitio Web y el Servicio. + +### E. Repositorios privados +**Resumen:** *Tratamos el contenido de los repositorios privados como confidencial y sólo accedemos a este tal y como se describe en nuestra Declaración de Privacidad—con fines de seguridad—para ayudar al propietario del repositorio con un asunto de soporte, para mantener la integridad del servicio, cumplir con nuestras obligaciones legales, si tenemos motivos para creer que el contenido viola la ley o con tu consentimiento.* + +#### 1. Control de repositorios privados +Algunas cuentas pueden tener repositorios privados, que permiten al Usuario controlar el acceso al Contenido. + +#### 2. Control de repositorios privados +GitHub considera que el contenido de los repositorios privados es confidencial para ti. GitHub protegerá el contenido de los repositorios privados del uso no autorizado, el acceso, o divulgación de la misma manera que utilizaríamos para proteger nuestra propia información confidencial de naturaleza similar y, en ningún caso, con un grado de atención más razonable. + +#### 3. Acceso +El personal de GitHub solo puede ingresar al contenido de tus repositorios privados en las situaciones descritas en nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#repository-contents). + +Puedes decidir habilitar acceso adicional a tus repositorios privados. Por ejemplo: +- Puedes habilitar diversos servicios o funciones de GitHub que requieren derechos adicionales sobre Tu Contenido en los repositorios privados. Estos derechos pueden variar dependiendo del servicio o función, pero GitHub continuará tratando su contenido de repositorio privado como confidencial. Si estos servicios o características requieren derechos además de aquellos que necesitamos para proporcionar el servicio de GitHub, le daremos una explicación sobre esos derechos. + +Además, podemos estar [obligados por ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de tus repositorios privados. + +GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad. + +### F. Violación de la propiedad intelectual y la política de DMCA +Si crees que el contenido de nuestro sitio web viola tus derechos de autor, por favor contáctanos de acuerdo con nuestra [Política sobre la Ley de Derechos de Autor Digital del Milenio](/articles/dmca-takedown-policy/). Si eres propietario de derechos de autor y consideras que el contenido en GitHub viola tus derechos, por favor contáctanos a través de [nuestro sencillo formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. Puede haber consecuencias legales por enviar un aviso de sumisión falso o poco serio. Antes de enviar una solicitud de sumisión, debes considerar usos legales tales como uso justo y usos autorizados. + +Cancelaremos las Cuentas de [infractores insistentes](/articles/dmca-takedown-policy/#e-repeated-infringement) de esta política. + +### G. Notificación de propiedad intelectual +**Versión resumida:** *Somos dueños del servicio y de todo nuestro contenido. Para que puedas utilizar nuestro contenido, te damos ciertos derechos, pero sólo puedes utilizar nuestro contenido de la forma que lo hemos permitido.* + +#### 1. Derechos de GitHub sobre el Contenido +GitHub y nuestros licenciatarios, vendedores, agentes y/o nuestros proveedores de contenidos conservan la propiedad de todos los derechos de propiedad intelectual de cualquier tipo relacionados con el Sitio Web y el Servicio. Nos reservamos todos los derechos que no se le conceden expresamente en virtud de este Acuerdo o por ley. La apariencia del Sitio Web y el Servicio es propiedad intelectual de GitHub, Inc. Todos los derechos reservados. No puedes duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. + +#### 2. Nombres comerciales y logos de GitHub +Si deseas usar las marcas registradas de GitHub, debes seguir todas nuestras directrices de marca registrada, incluyendo las que aparecen en nuestra página de logos: https://github.com/logos. + +#### 3. Licencia a políticas de GitHub +La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). + +### H. Términos de la API +**Versión resumida:** *Aceptas estos términos de servicio, además de esta sección H, al usar cualquiera de las API de GitHub (Interfaz del Proveedor de la Aplicación), incluyendo el uso de la API a través de un producto de terceros que ingresa a GitHub.* + +Las solicitudes abusivas o excesivamente frecuentes a GitHub a través de la API pueden resultar en la suspensión temporal o permanente del acceso de tu Cuenta a la API. GitHub, a nuestra sola discreción, determinará el abuso o el uso excesivo de la API. Intentaremos avisarte por correo electrónico antes de la suspensión. + +No puedes compartir tokens API para exceder las limitaciones de velocidad de GitHub. + +No puedes utilizar la API para descargar datos o Contenido de GitHub con fines de spamming, incluyendo el propósito de vender la información personal de los usuarios de GitHub, tales como reclutadores, cazatalentos y bolsas de trabajo. + +Todo uso de la API de GitHub está sujeto a estos términos de servicio y a la [Declaración de privacidad de GitHub](https://github.com/site/privacy). + +GitHub puede ofrecer acceso basado en suscripción a nuestra API para aquellos usuarios que requieren acceso de alto rendimiento o acceso que resultaría en reventa del servicio de GitHub. + +### I. Términos adicionales de los productos de GitHub +**Versión resumida:** *Debes seguir ciertos términos y condiciones específicos para las diversas características y productos de GitHub y aceptas los Términos y Condiciones Suplementarios cuando estés de acuerdo con este Contrato.* + +Algunas características del servicio pueden estar sujetas a términos adicionales específicos de esa característica o producto según lo establecido en los términos adicionales del producto de GitHub. Al ingresar o utilizar los Servicios, también aceptas los [Términos de adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms). + +### J. Vista previa Beta +**Versión resumida:** *Las vistas previas Beta no pueden ser soportadas o pueden cambiar en cualquier momento, puedes recibir información confidencial a través de aquellos programas que deben permanecer confidenciales mientras el programa es privado y nos encantaría tener tu opinión para mejorar nuestras Vistas Previas Beta.* + +#### 1. Sujeto a cambio + +Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Además, las Vistas Previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que se encuentra sujeto el Servicio. **Al hacer uso de una Vista Previa beta, la estás utilizando bajo tu propio riesgo.** + +#### 2. Confidencialidad + +Como usuario de las Vistas Previas Beta, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. + +**Obligaciones de confidencialidad.** Aceptas que cualquier información no pública de Vista Previa Beta que te proporcionamos, como información sobre una vista previa privada Beta, se considerará información confidencial de GitHub (colectivamente, “Información Confidencial”), independientemente de si está marcada o identificada como tal. Aceptas usar dicha Información Confidencial únicamente para el propósito expreso de probar y evaluar la Vista Previa Beta (el “Propósito”) y para ningún otro propósito. Debes tener el mismo cuidado que con tu propia información confidencial pero no menos de las precauciones razonables para prevenir cualquier uso no autorizado, revelación, publicación o divulgación de nuestra Información Confidencial. Te comprometes a no revelar, publicar o divulgar ninguna Información Confidencial a terceros a menos que no prohibamos o restrinjamos dicha divulgación (por ejemplo, puede ser parte de una discusión de grupo organizada por GitHub acerca de una característica de la Vista Previa Beta). + +**Excepciones.** La Información Confidencial no incluirá información que: (a) sea o esté disponible públicamente sin violación de este Contrato a través de ningún acto o inacción por su parte (como cuando una Vista Previa Beta privada se convierte en una Vista Previa Beta pública); (b) conozcas antes de que lo divulguemos; (c) esté desarrollada independientemente por ti sin violación de ninguna obligación de confidencialidad con nosotros o con terceros; o (d) sea revelada con permiso de GitHub. No violarás los términos de este Acuerdo si se te pide revelar Información Confidencial de acuerdo con el funcionamiento de la ley, siempre y cuando GitHub haya recibido un aviso por escrito razonable para objetar, a menos que la ley lo prohíba. + +#### 3. Comentarios + +Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como usuario de las Vistas Previas Beta nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación. + +### K. Pago +**Versión resumida:** *Eres responsable de cualquier cargo asociado con tu uso de GitHub. Somos responsables de comunicarte esos cobros con claridad y precisión y de hacerte saber con mucha antelación si esos precios cambian.* + +#### 1. Precios +Nuestros precios y términos de pago están disponibles en [github.com/pricing](https://github.com/pricing). Si aceptas un precio de suscripción, ese seguirá siendo tu precio durante la duración del plazo de pago; sin embargo, los precios están sujetos a cambios al final de un plazo de pago. + +#### 2. Mejoras, descensos y cambios +- Te cobraremos inmediatamente cuando pase del plan gratuito a cualquier plan de pago. +- Si cambias de un plan de facturación mensual a un plan de facturación anual, GitHub te cobrará por un año completo en la próxima fecha de facturación mensual. +- Si mejoras a un mayor nivel de servicio, te cobraremos el plan actualizado inmediatamente. +- Puedes cambiar tu nivel de servicio en cualquier momento [eligiendo una opción de plan](https://github.com/pricing) o entrando a tu [configuración de facturación](https://github.com/settings/billing). Si decides bajar la categoría de tu Cuenta, puedes perder el acceso al Contenido, características o capacidad de tu Cuenta. Consulta nuestra sección sobre [Cancelación](#l-cancellation-and-termination) para obtener información sobre cómo obtener una copia de ese contenido. + +#### 3. Programación de facturación; no reembolsos +**Pago basado en el plan** para planes de pago mensuales o anuales, el Servicio se cobra con antelación de forma mensual o anual respectiva y no es reembolsable. No habrá reembolsos o créditos Para meses parciales de servicio, reembolsos o reembolsos durante meses sin usar con una cuenta abierta; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Para tratar a todos por igual, no se harán excepciones. + +**Pago basado en el uso** Algunas funciones de servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en mora. Consulte los [Términos adicionales del producto de GitHub para conocer más detalles](/github/site-policy/github-additional-product-terms). + +**Facturación** Para usuarios facturados, el usuario acepta pagar los cobros en su totalidad, por adelantado sin deducción ni saldar cuentas de ningún tipo, en dólares americanos. estadounidenses. El usuario debe pagar las cuotas dentro de treinta (30) días a partir de la fecha de facturación de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el usuario no paga las cuotas a tiempo, GitHub se reserva el derecho, además de tomar cualquier otra acción conforme a derecho o equidad, a (i) cobrar intereses sobre importes vencidos en 1.0% al mes o el tipo de interés más alto permitido por la ley, el que sea menor y a cobrar todos los gastos de recuperación y (ii) cancelar el formulario de pedido aplicable. El usuario es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en relación con el presente Acuerdo. + +#### 4. Autorización +Al aceptar estos términos, nos das permiso para hacer un cargo a tu tarjeta de crédito en el archivo Cuenta de PayPal, u otros métodos de pago aprobados para los cobros que autorizas para GitHub. + +#### 5. Responsabilidad de pago +Eres responsable de todas las cuotas, incluyendo los impuestos, asociados con tu uso del Servicio. Al utilizar el Servicio, aceptas pagar a GitHub cualquier cobro incurrido en relación con tu uso del Servicio. Si impugnas el asunto, ponte en contacto con [el soporte de GitHub](https://support.github.com/contact). Eres responsable de proporcionarnos un medio de pago válido para las pagar las Cuentas. Las cuentas gratuitas no están obligadas a proporcionar información de pago. + +### L. Cancelación y terminación +**Versión resumida:** *Puedes cerrar tu Cuenta en cualquier momento. Si lo haces, trataremos tu información de forma responsable.* + +#### 1. Cancelación de la cuenta +Es tu responsabilidad cancelar correctamente tu cuenta con GitHub. Puedes [cancelar tu cuenta en cualquier momento](/articles/how-do-i-cancel-my-account/) entrando a tu Configuración en la barra de navegación global en la parte superior de la pantalla. La pantalla de la Cuenta proporciona un enlace simple y sin preguntas de cancelación. No podemos cancelar Cuentas en respuesta a una solicitud de correo electrónico o teléfono. + +#### 2. Tras la cancelación +Conservaremos y usaremos tu información cuando sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero sin requerimientos legales, borraremos tu perfil completo y el Contenido de tus repositorios dentro de los 90 días posteriores a la cancelación o terminación (aunque es posible que permanezca alguna información en las copias de seguridad cifradas). Esta información no se puede recuperar una vez que su cuenta sea cancelada. + +No eliminaremos el contenido con el que hayas contribuido a los repositorios de otros usuarios o que otros usuarios hayan bifurcado. + +Si se solicita, haremos un esfuerzo razonable para proporcionar al propietario de una cuenta una copia de los contenidos legales, no infringido de la Cuenta después de la cancelación, terminación o descenso de categoría. Debes hacer esta solicitud dentro de los 90 días siguientes a la cancelación, terminación o descenso de categoría. + +#### 3. GitHub pueder rescindir +GitHub tiene derecho a suspender o rescindir tu acceso a todas o a cualquier parte del sitio web en cualquier momento con o sin causa, con o sin previo aviso, efectivo inmediatamente. GitHub se reserva el derecho de denegar el servicio a cualquier persona por cualquier motivo en cualquier momento. + +#### 4. Continuidad +Todas las disposiciones de este Acuerdo que, por su naturaleza, deben sobrevivir a la terminación *sobrevivirán* la terminación — incluyendo, sin limitación: Disposiciones de propiedad, exenciones de garantía, indemnización y limitaciones de responsabilidad. + +### M. Comunicaciones con GitHub +**Versión resumida:** *Utilizamos correo electrónico y otros medios electrónicos para mantenernos en contacto con nuestros usuarios.* + +#### 1. Comunicación electrónica requerida +Para propósitos contractuales, (1) otorgarás tu consentimiento para recibir nuestras comunicaciones en forma electrónica a través de la dirección de correo electrónico que ingresaste o a través del Servicio; y (2) aceptarás que todos los Términos de Servicio, acuerdos, avisos, revelaciones, y otras comunicaciones que le proporcionamos electrónicamente satisfacen cualquier requisito legal que dichas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta tus derechos no renunciables. + +#### 2. El aviso legal para GitHub debe ser por escrito +Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería de soporte de GitHub no constituirán un aviso legal a GitHub ni a ninguno de sus oficiales, empleados, agentes o representantes en cualquier situación en la que el aviso a GitHub se requiera por contrato o cualquier ley o reglamento. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). + +#### 3. Sin soporte telefónico +GitHub sólo ofrece soporte por correo electrónico, comunicaciones en el servicio y mensajes electrónicos. No ofrecemos soporte telefónico. + +### N. Exención de garantías +**Versión resumida:** *Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. Lee esta sección cuidadosamente; deberías entender qué esperar.* + +GitHub proporciona el sitio web y el servicio “tal cual” y “según disponibilidad”, sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto al Servicio Web y el Servicio incluyendo entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento. + +GitHub no garantiza que los Servicios cumplan con tus requisitos; que el Servicio no se interrumpa y sea oportuno, seguro o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. Asumes toda la responsabilidad y el riesgo de pérdida resultante de su descarga y/o uso de archivos, información, contenido u otro material obtenido del Servicio. + +### O. Limitación de responsabilidad +**Versión resumida:** *No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.* + +Comprendes y aceptas que no seremos responsables ante ti o ante ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad, o datos, o para cualquier daño accidental, indirecto, especial, consecuencial o exemplatorio, que surjan sin embargo de + +- el uso, divulgación o visualización de tu contenido generado por el usuario; +- tu uso o incapacidad para usar el Servicio; +- cualquier modificación, cambio de precios, suspensión o interrupción del Servicio; +- el Servicio generalmente o el software o sistemas que hacen el Servicio disponible; +- acceso no autorizado a o alteraciones de tus transmisiones o datos; +- declaración o conducta de cualquier tercero en el Servicio; +- cualquier otra interacción de usuario que introduzca o reciba a través del uso del Servicio; o +- cualquier otro asunto relacionado con el Servicio. + +Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable. + +### P. Liberación e indemnización +**Versión resumida:** *Eres responsable de tu uso del servicio. Si dañas a otra persona o entras en una disputa con otra persona, no estaremos implicados.* + +Si tienes una disputa con uno o más usuarios, aceptas liberar a GitHub de todos y cada uno de los reclamos, demandas y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o de cualquier forma relacionados con tales disputas. + +Aceptas indemnizarnos, defendernos y liberarnos de toda responsabilidad contra cualquier reclamación, responsabilidad y gastos, incluyendo los honorarios de abogados, derivados del uso del Sitio Web y del Servicio, incluyendo sin limitación a tu violación de este Acuerdo, considerando que GitHub (1) te dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y resolución de reclamaciones, demanda, juicio o diligencia (siempre y cuando no pueda solucionar ninguna reclamación, demanda, juicio o diligencia, a menos que el acuerdo libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporcione toda la asistencia razonable, a su cargo. + +### Q. Modificaciones a estos términos +**Versión resumida:** *Desamos que nuestros usuarios estén informados sobre los cambios importantes en nuestros términos, pero algunos cambios no son tan importantes — no queremos molestarte cada vez que arreglamos un error tipográfico. Por ello, si bien es posible que modifiquemos el presente acuerdo en cualquier momento, notificaremos a los usuarios sobre cualquier cambio material y te daremos tiempo para ajustarlos.* + +Nos reservamos el derecho, a nuestro exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizaremos este Acuerdo en el caso en que ocurran dichas modificaciones. Notificaremos a nuestros usuarios de los cambios materiales en el presente acuerdo, como aumentos de precios, al menos 30 días antes de que el cambio entre en vigencia al publicar un aviso en nuestro sitio web o al enviar un correo electrónico a la dirección principal de correo electrónico especificada en tu cuenta de GitHub. El uso continuo del Servicio por parte del cliente después de dichos 30 días constituye el acuerdo a las revisiones del presente Acuerdo. Para cualquier otra modificación, tu uso continuo del sitio web constituye un acuerdo con nuestras revisiones de estos términos de servicio. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-. + +Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el Sitio Web (o cualquier parte de este) con o sin notificación. + +### R. Varios + +#### 1. Legislación aplicable +Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California. + +#### 2. Intransferible +GitHub puede asignar o delegar estos Términos de Servicio y/o la [Declaración de privacidad de GitHub](https://github.com/site/privacy), en su totalidad o en parte, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento, incluyendo la concesión de licencia en la Sección D.4. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos de Servicio o Declaración de Privacidad sin nuestro previo consentimiento por escrito y ninguna asignación no autorizada y delegación por ti es nula. + +#### 3. Encabezados y resúmenes de sección +A lo largo de este Acuerdo, cada sección incluye títulos y breves resúmenes de los siguientes términos y condiciones. Estos títulos de sección y breves resúmenes no son legalmente vinculantes. + +#### 4. Divisibilidad, sin exención y supervivencia +Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo. + +#### 5. Enmiendas, acuerdo completo +Este Acuerdo sólo puede modificarse por una enmienda por escrito firmada por un representante autorizado de GitHub o por la publicación de GitHub de una versión revisada de acuerdo con la sección [Q. Cambios a estos términos](#q-changes-to-these-terms). Estos Términos de Servicio, junto con la Declaración de Privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tu persona y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. + +#### 6. Preguntas +¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-ES/content/github/site-policy/github-trademark-policy.md b/translations/es-ES/content/github/site-policy/github-trademark-policy.md new file mode 100644 index 0000000000000..b10766065ee26 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-trademark-policy.md @@ -0,0 +1,50 @@ +--- +title: Política de marca registrada de GitHub +redirect_from: + - /articles/github-trademark-policy +versions: + free-pro-team: '*' +--- + +### ¿Qué es una Violación de la Política de Marcas de GitHub? + +Utilizar el nombre de una empresa o negocio, logotipo, u otros materiales protegidos por marca registrada de una manera que pueda inducir a un error o confundir a otros con respecto a su marca o afiliación comercial pueden considerarse una violación de la política de marcas registradas. + +### ¿Qué no es una Violación de la Política de Marcas de GitHub? + +El uso de la marca de otro de una manera que no tenga nada que ver con el producto o servicio para el que se concedió la marca no es una violación de la política de marcas registradas. Los nombres de usuario de GitHub están disponibles en una base de primera vez, en el orden de solicitud y no se pueden reservar. Una cuenta de GitHub con un nombre de usuario que resulte ser la misma que una marca registrada no es, por sí mismo, necesariamente una violación de nuestra política de marcas. + +### ¿Cómo responde GitHub al reporte de las Violaciones de Política de Marcas? + +Cuando recibimos reportes de violaciones de la política de marcas registradas por parte de titulares de registros de marcas federales o internacionales, revisamos la cuenta y podemos tomar las siguientes acciones: + +* Cuando exista una intención clara de engañar a otros a través del uso no autorizado de una marca, GitHub suspenderá la cuenta y notificará al titular de la misma. +* Cuando determinamos que una cuenta parece estar confundiendo a los usuarios, pero no se hace pasar de manera intencional como el bien o servicio con marca registrada, le damos al titular de la cuenta la oportunidad de aclarar cualquier posible confusión. También podemos lanzar un nombre de usuario para el uso activo del titular de la marca. + +### ¿Cómo reporto una violación de la política de marcas? + +Los titulares de marcas registradas pueden denunciar posibles violaciones de la política de marcas a GitHub a través de nuestro [formulario de contacto](https://support.github.com/contact?tags=docs-trademark). Envía solicitudes relacionadas con marcas comerciales utilizando tu dirección de correo electrónico de la empresa e incluye toda la información que se solicita a continuación para ayudar a agilizar nuestra respuesta. También asegúrate de describirnos claramente por qué la cuenta puede causar confusión con tu marca o cómo puede la cuenta debilitar o perjudicar a tu marca. + +### ¿Qué información se requiere cuando se informa de las violaciones de las políticas de marcas? + +Para investigar las violaciones de la política de marcas, por favor proporciona toda la siguiente información: + +* Nombre de usuario de la cuenta reportada +* Nombre de tu empresa +* La cuenta GitHub de tu empresa (si existe) +* Sitio web de la empresa +* La palabra de tu marca, símbolo, etc. +* Número de registro de marca +* Oficina de registro de marcas (ej., USPTO) +* Descripción de la confusión (por ejemplo, se hace pasar por su empresa, incluyendo descripciones específicas de contenido o comportamiento) +* Acción solicitada (por ejemplo, eliminación de una cuenta en violación o transferencia de un nombre de usuario con marca a una cuenta de empresa existente) +* Incluye la siguiente declaración: "Tengo la creencia de buena fe de que el uso de la marca descrita anteriormente no está autorizado por el propietario de la marca, o su agente, o la ley. He considerado los usos nominativos y otros usos legítimos". +* También incluye la siguiente declaración: "Juro, bajo pena de perjurio, que la información de esta notificación es fiel y que soy el propietario de los derechos de autor o estoy autorizado para actuar en nombre del propietario, de un derecho exclusivo que se infringe presuntamente." +* Incluye tu firma física o electrónica. + +* Nota: Se requiere un número de registro federal o internacional de marcas registradas. Si el nombre que estás reportando no es **** una marca registrada (por ejemplo, una agencia gubernamental u organización sin fines de lucro), comunícanos: + * Tu nombre y apellido + * Posición + * Dirección + * Teléfono + * Correo electrónico (debe ser de dominio de una empresa) diff --git a/translations/es-ES/content/github/site-policy/github-username-policy.md b/translations/es-ES/content/github/site-policy/github-username-policy.md new file mode 100644 index 0000000000000..6ac4aaf11a9f9 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-username-policy.md @@ -0,0 +1,24 @@ +--- +title: Política de nombre de usuario de GitHub +redirect_from: + - /articles/name-squatting-policy/ + - /articles/github-username-policy +versions: + free-pro-team: '*' +--- + +Los nombres de cuentas de GitHub se proporcionan dependiendo de quién los reclame primero, y se pretende que se comiencen a utilizar activamente de inmediato. + +#### ¿Qué pasa si el nombre de usuario que quiero ya está en uso? + +Ten en mente que no toda la actividad en GitHub está disponible públicamente para su consulta; puede que las cuentas sin actividad visible estén activas. + +Si ya han reclamado el nombre de usuario que quieres, considera otros nombres o variaciones únicas de éste. Puedes identificar un nombre de usuario aún disponible si utilizas números, guiones, o una morfología alterna. + +#### Política de marcas + +Si consideras que la cuenta de alguien está violando tus derechos de marca, puedes encontrar más información sobre cómo hacer una queja de marca en nuestra página de [Política de Marca](/articles/github-trademark-policy/). + +#### Política de ocupación de nombre + +GitHub prohibe el acaparamiento de nombres de cuenta, y dichos nombres de cuenta no pueden reservarse o mantenerse en inactividad para reclamarse posteriormente. Las cuentas que violen esta política de acaparamiento serán eliminadas o renombradas sin previo aviso. Los intentos de vender, comprar o solicitar otras formas de pago a cambio de nombres de cuenta están prohibidos y pueden resultar en una suspensión de cuenta permanente. diff --git a/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md new file mode 100644 index 0000000000000..7887d2229ed7f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -0,0 +1,73 @@ +--- +title: Aviso de GitHub acerca de la Ley de Privacidad del Consumidor de California +versions: + free-pro-team: '*' +--- + +Válida desde el 1 de enero de 2020 + +### Aviso de GitHub para los Residentes de California + +La [Ley de Privacidad del Consumidor de California](https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375) de 2018, (Cal. Civ. Code §1798.100 y siguientes., en su texto reformado, “CCPA”) otorga a los residentes de California los derechos y control sobre su información personal. ("GitHub", "nosotros") proporciona esta declaración a los residentes ("tú") de acuerdo con los requisitos bajo la CCPA para realizar ciertas divulgaciones sobre la recolección y procesamiento de su información personal. Esta es la descripción de los derechos del consumidor de GitHub específica para California bajo la CCPA. Para obtener más información acerca de cómo hemos extendido los derechos básicos de la CCPA para controlar la información personal de todos nuestros usuarios en los Estados unidos, por favor consulta nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement). + +### No vendemos tu información personal + +Bajo la CCPA, un negocio que vende la información personal de los residentes de California a otros: 1) debe notificar a los residentes de California antes de vender su información personal a otros; y 2) deberá proporcionar el derecho de negarse a la venta de su información personal. + +GitHub _no_ vende información personal, incluyendo aquella de cualquier menor de 16 años. Por lo tanto, esta notificación y los requisitos para negarse no aplican a GitHub. + +## Tus derechos bajo la CCPA + +La CCPA proporciona a los residentes de California ciertos derechos relacionados con su información personal. Para emitir una solicitud basada en estos derechos, por favor contáctanos a través de nuestro [formulario de contacto](https://support.github.com/contact). + +Cuando recibimos una solicitud, verificamos que la persona que la hace sea el dueño de la misma de acuerdo con dicha solicitud. Los residentes de California podrán ejercer sus derechos por ellos mismos, o podrán utilizar a un agente autorizado para hacer solicitudes para divulgar cierta información acerca del procesamiento de la suya o para eliminar la información personal en su represetnación. Si utilizas a un agente autorizado para emitir una solicitud, podríamos solicitar que nos proporciones información adicional para demostrar que el agente está actuando en tu representación. + +Con respecto a su información personal, los residentes de California podrán ejercer los derechos descritos posteriormente. + +### 1. Derecho a saber qué tipo de información personal se está recolectando, para qué propósito y con quién se comparte + +Los residentes de California tiene el derecho a solicitar una divulgación de negocios sobre las categorías y partes específicas de la información personal que se ha recolectado de ellos en los 12 meses anteriores, y las categorías de las fuentes de donde dicha información personal se recabó, el propósito comercial o de negocios para recolectarla o venderla, y las categorías de terceros con quienes el negocio comparte la información personal. + +Si solicitas que un negocio divulgue las categorías y partes específicas de la información personal que se ha recolectado de ti, tienes el derecho a recibir dicha información, sin costo alguno, dos veces por año. La información podrá entregarse electrónicamente o por correo, y si se proporciona electrónicoamente, deberá estar en un formato portable y, hasta donde sea técnicamente posible, listo para su uso, que permita al residente de California transmitir dicha información de forma relativamente fácil a otra entidad. Puedes usar la API de migración de usuarios de [de GitHub](/rest/reference/migrations#users) para ingresar y descargar tus datos. Conoce más [aquí](https://github.blog/2018-12-19-download-your-data/). + +### 2. Derecho a conocer si tu información personal se vende o divulga para propósitos de negocios y a quién + +Los residentes de California tienen el derecho a solicitar información de un negocio que vende o divulga la información personal para propósitos de negocios en listas separadas de categorías de la información personal recolectada, vendida o divulgada para propósitos de negocios en 12 meses previos, incluyendo las categorías de terceros a quienes se vendió o divulgó la información por motivo de negocios. + +### 3. Derecho a negarse a la venta de su información personal + +Como se explica anteriormente, la CCPA requiere que los negocios que venden información personal permitan a los residentes negarse a la venta de su información. + +Reiteramos, GitHub no vende información personal. + +### 4. Derecho a no discriminar servicios o precios si ejerces tus derechos a la privacidad + +La CCPA prohíbe que los negocios discriminen a un residente de California por ejercer cualquiera de sus derechos bajo la misma, incluyendo el +- negar bienes o servicios +- cobrar precios o tasas diferentes por bienes o servicios, incluyendo a través del uso de descuentos u otros beneficios o mediante la imposición de multas +- proporcionar un nivel de calidad o de bienes o servicios diferente +- sugerir que la persona que está ejerciendo sus derechos recibirá un precio o tasa diferente en los bienes o servicios o un nivel de calidad diferente en éstos + +### 5. Derecho al borrado + +Los residentes de california tienen el derecho de solicitar que un negocio elimine cualquier información personal que éste haya recolectado de ellos, sujeto a las excepciones en la CCPA §1798.105. + +## Nuestro manejo de la Información Personal + +Aunque la siguiente tabla contiene información acerca de las categorías de información personal que recolectamos, procesamos y compartimos, por favor consulta la [Declaración de Privacidad](/github/site-policy/github-privacy-statement) para encontrar todos los detalles. + +| **Categoría de información personal recolectada en los últimos 12 meses** | **Categoría de fuentes desde donde se ha recolectado la información personal** | **Propósito(s) comercial o de negocios para recolectar la información personal** | **Categorías de los terceros con los que se comparte la información personal** | **Categorías de la información personal divulgada por propósitos comerciales o de negocios** | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Identificadores (tales como nombre real, alias, dirección postal, identificador personal único, dirección de Protocolo de Internet de identificación en línea, dirección de correo electrónico, nombre de cuenta, u otros identificadores similares) | Información que proporciona el consumidor directamente o automáticamente a través de su interacción con nuestro Servicio y/o Sitio Web | Detectar incidentes de seguridad, proteger contra actividad maligna, engañosa, fraudulenta o ilegal, y perseguir a los responsables de dicha actividad

Arreglo de errores para identificarlos y repararlos si impiden la funcionalidad existente buscada

Llevar a cabo servicios por parte del negocio o proveedor de servicios

Llevar a cabo investigaciones internas para desarrollo tecnológico y demostración

Llevar a cabo actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorar, actualizar o ampliar el servicio | Proveedores de servicios, clientes aplicables, aplicación de la ley | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | +| Cualquier categoría de información personal descrita en la subdivisión (e) de Cal. Civ. Code §1798.80 (la cual define a la "información personal" como "cualquier tipo de información que identifica, relaciona, describe, o es capaz de asociarse con un individuo en particular" — con ejemplos que incluyen nombre, dirección, número de tarjeta de crédito o débito—y excluye la información disponible al público en general) | Información que el consumidor proporciona directamente | Perseguir a aquellos responsables por actividades malignas, engañosas, fraudulentas o ilegales.

Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | +| Las características de las clasificaciones protegidas bajo la ley federal de California (tales como género, edad) | Información que el consumidor decida proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | +| Información comercial (tal como aquella acerca de la compra, obtención, consideración de bienes o servicios, u otro tipo de historial o tendencia de compra o consumo) | Información que proporciona el consumidor directamente o automáticamente a través de su interacción con nuestros Servicios | Depuración para identificar y reparar errores que perjudican la funcionalidad deseada

Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para propósitos comerciales o de negocios | | Información de actividad en internet o en otra red electrónica (tal como historial de internet, historial de búsqueda, e información relacionada con la interacción de un cliente con una aplicación o sitio web de internet) | Información que el cliente proporciona automáticamente a través de su interacción con nuestros Servicios | Detectar incidentes de seguridad, proteger contra la actividad maligna, engañosa, fraudulenta, o ilegal, y perseguir a los responsables de dicha actividad

Depurar para identificar y reparar errores que perjudican la funcionalidad deseada

Llevar a cabo servicios a nombre del negocio o proveedor de servicios

Realizar investigación interna sobre demostraciones y desarrollo tecnológico

Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | + Datos de Geolocalización (tales como la dirección IP) | Información que el consumidor proporciona automáticamente a través de su interacción con nuestros servicios | Detectar incidentes de seguridad, proteger contra actividades malignas, engañosas fraudulentas o ilegales, y perseguir a los responsables de dicha actividad

Depurar para identificar y reparar los errores que perjudican la funcionalidad deseada

Llevar a cabo servicios a nombre del negocio o proveedor de servicios

Realizar investigación interna sobre demostraciones y desarrollo tecnológico

Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios |Información de audio, electrónica, visual o similar | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Información profesional o relacionada con el empleo | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Infomración de la educación que no está disponible públicamente ni identifica a las personas | Esta categoría de información personal se ha divulgado con fines comerciales o de negocios | Información como se define en la Ley de Privacidad y Derechos Educacionales Familiares (20 U. S.C. Sec. Sección 1232g; 34 C. F.R. Parte 99) | Información que el consumidor pudiera proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Inferencias extraídas de cualquier información identificada en esta tabla para crear un perfil acerca de un consumidor, el cual refleje las preferencias del mismo | Información que el consumidor proporciona directamente o automáticamente a través de su interacción con nuestros Servicios | Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | + +## Ejemplos bajo la CCPA + +La CCPA proporciona exclusiones hasta, e incluyendo, el 31 de diciembre de 2020, de ciertas divulgaciones de las antes citadas, las cuales se sitúen en los 12 últimos meses incluyendo la **exclusión de negocio a negocio**: + + la información personal que se refleje en comunicaciones verbales o escritas o en transacciones entre GitHub y una persona natural, en donde la persona natural actúe como un empleado, propietario, director, oficial, o contratista de una compañía, sociedad, único dueño, organización sin fines de lucro, o agencia de gobierno, y cuyas comunicaciones o transacciones con GitHub ocurran únicamente dentro del contexto de que GitHub lleve a cabo indagaciones previas, o proporcione o reciba un producto o servicio de o por parte de tal compañía, sociedad, duelo único, organización sin fines de lucro o agencia del gobierno. + +Si tienes cualquier duda acerca de esta página, por favor contáctanos a través de nuestro [formulario de contacto](https://support.github.com/contact). diff --git a/translations/es-ES/content/github/site-policy/global-privacy-practices.md b/translations/es-ES/content/github/site-policy/global-privacy-practices.md new file mode 100644 index 0000000000000..e2c8208b1d9e5 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/global-privacy-practices.md @@ -0,0 +1,72 @@ +--- +title: Prácticas de Privacidad Globales +redirect_from: + - /eu-safe-harbor/ + - /articles/global-privacy-practices +versions: + free-pro-team: '*' +--- + +Fecha de entrada en vigor: 22 de julio del 2020 + +GitHub Proporciona el mismo estándar alto de protección de privacidad—tal como se describe en la [Declaración de Privacidad](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices) de GitHub—a todos nuestros usuarios y clientes en todo el mundo, sin importar su país de origen o ubicación, y GitHub se enorgullece del nivel de notificación, elección, responsabilidad, seguridad, integridad de datos, acceso, y recursos que proporcionamos. + +GitHub también cumple con ciertos marcos de trabajo relacionados con la transferencia de los datos desde el Área Económica Europea, el Reino Unido y Suiza (colectivamente conocidos como "UE") hacia los Estados Unidos. Cuando GitHub se involucra en dichas transferencias, GitHub se basa en las Cláusulas Contractuales Estándar como el mecanismo legal para ayudarlo a garantizar tus derechos y que tu información personal viaje con la protección adecuada. Adicionalmente, GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A. y Suiza-U. S. A. Para aprender más sobre las decisiones de la Comisión Europea sobre la transferencia internacioal de datos, consulta este artículo en el [Sitio web de la Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en). + +### Cláusulas Contractuales Estándar + +GitHub se basa en las Cláusulas Contractuales Estándar aprobadas por la Comisión Europea ("SCCs") como un mecanismo legal para las transferencia de datos desde la UE. Las SCCs son compromisos contractuales entre compañías que transfieren datos personales que las vinculan para proteger la privacidad y seguridad de dichos datos. GitHub adoptó las SCCs para que los flujos de datos necesarios puedan protegerse cuando se transfieren hacia afuera de la UE a países que la Comisión Europea no ha estimado pueden proteger los datos personales adecuadamente, incluyendo el proteger la transferencia de estos hacia los Estados Unidos. + +Para aprender más sobre las SCCs, consulta este artículo en el [Sitio web dela Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). + +### Marco del Escudo de Privacidad + +GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A y U. S. A-Suiza y en los compromisos que éstos conllevan, a pear de que GitHub no se basa en el Marco de Trabajo de Escudo de Privacidad de UE-U. S. A. como una base legal para transferencias de información personal ante el juicio de la Corte de Justicia de la UE en el caso C-311/18. + +Los Marcos de Trabajo de Escudo de Privacidad de UE-E.U.A. y Suiza-E.U.A. se implementan por el Departamento de Comercio de los E.U.A. de acuerdo con la recoleción, uso, y retención de la Información Personal transferida desde la Unión Europea, el Reino Unido, y Suiza hacia los Estados Unidos. GitHub ha certificado al Departamento de Comercio que se apega a los Principios del Escudo de Privacidad. Si nuestros proveedores o afiliados procesan la Información Personal de los Usuarios en nuestro nombre de forma inconsistente con los principios de cualquiera de los Marcos de Trabajo de Escudo de Privacidad, GitHub seguirá siendo responsable a menos de que provemos que no lo somos para dicho evento que genera el daño. + +Para propósitos de nuestras certificaciones bajo los Marcos de Trabajo del Escudo de Privacidad, si hubiese cualquier conflicto entre las condiciones en estas Prácticas de Privacidad Globales y en los Principios del Escudo de Privacidad, los últimos deberán prevalecer. Para obtener más información sobre el programa Escudo de Privacidad y para ver nuestra certificación, visite el sitio web [de Escudo de Privacidad](https://www.privacyshield.gov/). + +Los Marcos de Trabajo del Escudo de Privacidad se basan en siete principios, y GitHub se apega a ellos de las siguientes formas: + +- **Notificaciones** + - Te informamos cuando recopilamos tu información personal. + - Te damos a conocer, en nuestra [Declaración de Privacidad](/articles/github-privacy-statement/)de los fines que tenemos para recopilar y utilizar tu información a quién compartimos esa información con y bajo qué restricciones y qué acceso tiene a tus datos. + - Te informamos que estamos participando en el marco del Escudo de Privacidad y lo qué significa para ti. + - Tenemos un {% data variables.contact.contact_privacy %} donde puedes contactarnos con preguntas sobre tu privacidad. + - Te informamos acerca de tu derecho a invocar arbitraje vinculante, sin costo alguno para ti, en el improbable caso de una disputa. + - Te informamos que estamos sujetos a la jurisdicción de la Comisión Federal de Comercio. +- **Opción** + - Te permitimos elegir lo que sucede con tus datos. Antes de que utilicemos tus datos para un propósito distinto para el cual nos los proporcionaste, te avisaremos y obtendremos tu permiso. + - Te proporcionarremos mecanismos razonables para hacer tu elección. +- **Responsabilidad de la transferencia continua** + - Cuando transferimos tu información a proveedores de terceros que la procesan en nuestro nombre, sólo estamos enviando tus datos a terceros, bajo contrato con nosotros, que los salvaguardarán consistentemente con nuestra Declaración de Privacidad. Cuando transferimos tus datos a nuestros proveedores bajo el Escudo de Privacidad, seguimos siendo responsables de ello. + - Compartimos sólo la cantidad de datos con nuestros proveedores de terceros cuando sea necesario para completar tu transacción. +- **Seguridad** + - Protegeremos tu información personal con [todas las medidas de seguridad razonables y apropiadas](https://github.com/security). +- **Limitación de integridad y propósito de datos** + - Solo recopilamos tus datos para las finalidades pertinentes para proporcionarte nuestros servicios. + - Recopilamos tan poca información tuya como podamos, a menos que decidas proporcionarnos más. + - Tomamos medidas razonables para asegurar que tus datos sean exactos, actuales y fiables para su uso previsto. +- **Acceso** + - Siempre puedes acceder a los datos que tenemos sobre ti en tu perfil de usuario [](https://github.com/settings/profile). Puedes ingresar, actualizar, alterar o eliminar tu información allí. +- **Recursos, cumplimiento y responsabilidad** + - Si tienes alguna pregunta sobre nuestras prácticas de privacidad, puedes contactarnos con nuestro {% data variables.contact.contact_privacy %} y responderemos en un plazo máximo de 45 días. + - En el improbable caso de una disputa que no podamos resolver, tienes acceso a un arbitraje vinculante sin coste alguno para ti. Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información. + - Realizaremos auditorías periódicas de nuestras prácticas de privacidad relevantes para verificar el cumplimiento de las promesas que hemos hecho. + - Exigimos a nuestros empleados que respeten nuestras promesas de privacidad y la violación de nuestras políticas de privacidad está sujeta a una acción disciplinaria e inclusive hasta la terminación del empleo. + + +#### Proceso de resolución de disputas + +Como se explica a detalle en la sección de [Resolución de Quejas](/github/site-policy/github-privacy-statement#resolving-complaints) de nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement), te exhortamos a contactarnos en caso de que tengas alguna queja relacionada con el Escudo de Privacidad (o sobre la privacidad en general). Para cualquier queja que no pueda resolverse directamente con GitHub, hemos escogido cooperar con la Autoridad de Protección de datos de la UE reelevante, o con un panel establecido por las autoridades europeas de protección de datos, para resolver disputas con los individuos de la UE, y con la Comisión Federal para la Protección de Datos y la Información (FDPIC, por sus siglas en inglés) para resolver las disputas con los individuos suizos. Por favor contáctanos si deseas que te dirijamos a los contactos de tu autoridad de protección de datos. + +Además, si eres residente de un estado miembro de la UE, tienes derecho a presentar una queja ante tu autoridad supervisora local. + +#### Arbitraje independiente + +En determinadas circunstancias limitadas, la UE, el Espacio Económico Europeo (EEE), Suiza y las personas del Reino Unido pueden recurrir al arbitraje vinculante del Escudo de privacidad como último recurso, si todas las demás formas de resolución de disputas no tuvieron éxito. Para obtener más información acerca de este método de resolución y su disponibilidad, consulta más detalles sobre el [Escudo de privacidad](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). El arbitraje no es obligatorio, es una herramienta que puedes utilizar si así lo decides. + +Estamos sujetos a la jurisdicción de la Comisión Federal de Comercio (FTC) de los EE. UU. + +Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información. diff --git a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md new file mode 100644 index 0000000000000..9e3571eae23c1 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md @@ -0,0 +1,74 @@ +--- +title: Guía para enviar una contranotificación de DMCA +redirect_from: + - /dmca-counter-notice-how-to/ + - /articles/dmca-counter-notice-how-to/ + - /articles/guide-to-submitting-a-dmca-counter-notice +versions: + free-pro-team: '*' +--- + +Esta guía describe la información que GitHub necesita para procesar una contra notificación de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy). + +Si consideras que tu contenido en GitHub fue inhabilitado erróneamente por una solicitud de retiro de DMCA. tienes derecho de disputar el retiro enviando una contra notificación. Si lo haces, esperaremos 10-14 días y posteriormente volveremos a habilitar tu contenido a menos que el propietario de los derechos de autor inicie una acción legal contra ti antes de entonces. Nuestro formulario de contra notificación indicado a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: . Sitio web oficial de la Oficina de Derechos de Autor: . + +Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. + +### Antes de comenzar + +***Di la Verdad.*** La DMCA requiere que jures tu contra notificación *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [Código de Estados Unidos, Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Code, Title 18, Section 1621.) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. + +***Investiga.*** Enviar una contra notificación DMCA puede tener consecuencias legales reales. Si la parte que denuncia no está de acuerdo en que tu notificación de retiro fue errónea, podrían decidir presentar una demanda contra ti para mantener el contenido deshabilitado. Deber llevar a cabo una investigación exhaustiva sobre las acusaciones hechas en la notificación de retiro y probablemente hablar con un abogado antes de enviar una contra notificación. + +***Debes tener una razón fundada para emitir una contranotificación.*** Para emitir una contranotificación, deberás tener una "certeza de buena fe de que el material se eliminó o inhabilitó como resultado de un error o mala identificación del material que se quiere eliminar o inhabilitar". (U.S. ([Título 17 del Código de los EEUU, Sección 512(g)](https://www.copyright.gov/title17/92chap5.html#512)). Ya sea que decidas explicar o no el por qué crees que hubo un error, dependerá de ti y de tu abogado, pero *sí* necesitas identificar un error antes de emitir una contranotificación. En el pasado, recibimos contra notificaciones que citan errores en la notificación de retiro, tales como: La parte que reclama no tiene el derecho de autor; tengo una licencia; el código se liberó bajo una licencia de código abierto que permite mi uso; o la queja no tiene en cuenta el hecho de que mi uso está protegido por la doctrina del uso legal. Por supuesto, podría haber otros defectos con la notificación de retiro.

+ +***Las leyes de derechos de autor son complicadas.*** En ocasiones una notificación de retiro podría hacer referencia a una infracción que parece extraña o indirecta. Las leyes de derechos de autor son complicadas y pueden dar lugar a resultados inesperados. En algunos casos una notificación de retiro podría señalar que su código fuente infringe por lo que puede ocasiones posteriormente que se compile y ejecute. Por ejemplo: + + - La notificación podrá reclamar que tu software se utiliza para [evitar los controles de acceso](https://www.copyright.gov/title17/92chap12.html) a los trabajos con derechos de autor. + - [Algunas veces](https://www.copyright.gov/docs/mgm/) la distribución de software puede considerarse como una infracción a los derechos de autor, si induces a los usuarios finales a utilizar el software para infringir el trabajo con derechos de autor. + - Una queja de derechos de autor también podría basarse en [copia no literal](https://en.wikipedia.org/wiki/Substantial_similarity) de elementos de diseño en el software, en lugar del código fuente en sí mismo, en otras palabras, alguien envió una notificación diciendo que piensa que tu *diseño* es demasiado similar al de ellos. + +Estos son sólo algunos ejemplos de la complejidad de la legislación sobre derechos de autor. Dado que hay muchos matices a la ley y algunas preguntas sin resolver en este tipo de casos, es especialmente importante obtener asesoramiento profesional si las acusaciones de infracción no parecen sencillas. + +***Una contra notificación es una declaración legal.*** Te pedimos que completes todos los campos de una contra notificación en su totalidad, porque una denuncia es una declaración legal — no sólo para nosotros, sino para la parte demandante. Como mencionamos anteriormente, si la parte reclamante desea mantener el contenido desactivado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedirle participar en actividades de infracción relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado (y das tu consentimiento en la contra notificación). + +***Tu contra notificación se publicará.*** Como se indica en nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy#d-transparency), **después de redactar información personal,** publicamos todas las contra notificaciones completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca). También ten en cuenta que, aunque sólo publicaremos notificaciones rectificadas, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente para cualquier parte cuyos derechos se verían afectados por esta. Si estás preocupado por tu privacidad, podrías pedir que un abogado u otro representante legal presente la contra notificación en tu nombre. + +***GitHub no es el juez.*** GitHub ejerce poca discreción en este proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio. + +***Recursos Adicionales.*** Si necesitas ayuda adicional, hay muchos recursos de autoayuda en línea. Lumen tiene un conjunto informativo de guías sobre [copyright](https://www.lumendatabase.org/topics/5) y [puerto seguro de DMCA](https://www.lumendatabase.org/topics/14). Si estás implicado con un proyecto de código abierto que necesita asesoramiento legal, puedes ponerse en contacto con el [Centro de asesoramiento legal sobre software libre](https://www.softwarefreedom.org/about/contact/). Y si consideras que tienes un caso especialmente desafiante, organizaciones sin fines de lucro como la [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) también pueden estar dispuestas a ayudarte directamente o a referirte a un abogado. + + + +### Tu contra notificación debe... + +1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una contra notificación DMCA.** No nos negaremos a procesar una contra notificación completa si no incluye esta declaración; sin embargo, sabremos que no has leído estas directrices y podríamos solicitarte que lo hagas. + +2. ***Identificar el contenido que fue desactivado y la ubicación donde apareció.*** El contenido deshabilitado debería haber sido identificado por la URL en la notificación de retiro. Simplemente necesitas copiar la(s) URL(s) que deseas cuestionar. + +3. **Proporcionar tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección. + +4. ***Incluir la siguiente declaración: "Juro, bajo pena de perjurio, que tengo una creencia de buena fe de que el material se eliminó o deshabilitó como resultado de un error o mala identificación del material a ser eliminado o desactivado.*** También puedes elegir comunicar las razones por las que crees que hubo un error o una mala identificación. Si piensas en tu contra notificación como una "nota" a la parte reclamante, Esta es una oportunidad para explicar por qué no deben dar el siguiente paso y presentar una demanda en respuesta. Esta es otra razón más para trabajar con un abogado al enviar una contra notificación. + +5. ***Incluir la siguiente declaración: "Acepto la jurisdicción del Tribunal Federal de Distrito para el distrito judicial en el que se encuentra mi dirección (si es en los Estados Unidos, de lo contrario el Distrito Norte de California donde se encuentra GitHub) y aceptaré el servicio de trámite de la persona que proporcionó la notificación del DMCA o de un agente de dicha persona."*** + +6. **Incluye tu firma física o electrónica.** + + + +### Cómo enviar tu contra notificación + +La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}. + +También puedes enviar una notificación por correo electrónico a . Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje. + +Si debes enviar tu notificación por correo físico, también puedes hacerlo pero tardaremos *substancialmente* en recibirla y responder a ella y el periodo de espera de 10 a 14 días comienza a partir de cuando *recibamos* tu contra notificación. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es: + + + +``` +GitHub, Inc +En atención a: Agente de DMCA +88 Colin P Kelly Jr St +San Francisco, CA. 94107 +``` diff --git a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md new file mode 100644 index 0000000000000..f461c7c9564e5 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md @@ -0,0 +1,86 @@ +--- +title: Guía para enviar un aviso de retiro de DMCA +redirect_from: + - /dmca-notice-how-to/ + - /articles/dmca-notice-how-to/ + - /articles/guide-to-submitting-a-dmca-takedown-notice +versions: + free-pro-team: '*' +--- + +Esta guía describe la información que GitHub necesita para procesar una solicitud de retiro de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy). + +Debido al tipo de contenido de los hosts de GitHub (principalmente de código de software) y a la forma en que se gestiona el contenido (con Git), necesitamos que las demandas sean lo más específicas posible. Estas directrices están diseñadas para que el procesamiento de las notificaciones de supuestas infracciones sea lo más sencillo posible. Nuestra forma de notificación indicada a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: . Sitio web oficial de la Oficina de Derechos de Autor: . + +Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. + +### Antes de comenzar + +***Di la Verdad.*** La DMCA requiere que prestes atención a los hechos en tu queja de derechos de autor *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [Código de Estados Unidos, Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Code, Title 18, Section 1621.) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. La DMCA por sí misma [proporciona daños](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra cualquier persona que, a sabiendas, tergiversa materialmente dicha actividad o material infractor. + +***Investiga.*** Millones de usuarios y organizaciones se esfuerzan demasiado en los proyectos que crean y contribuyen en GitHub. La presentación de una queja de DMCA contra un proyecto de este tipo es una acusación legal seria que conlleva consecuencias reales para las personas reales. Por eso, te pedimos que realices una investigación exhaustiva y consultes con un abogado antes de enviar una solicitud de retiro para asegurarte que el uso no sea realmente permisible. + +***Primero pregunta amablemente.*** Un gran primer paso antes de enviarnos una notificación de retiro es intentar contactar directamente al usuario. Pueden haber enumerado información de contacto en su página de perfil público o en el README del repositorio, o podrías ponerse en contacto abriendo una propuesta o solicitud de extracción en el repositorio. Esto no es estrictamente necesario, pero es común. + +***Envia una solicitud de corrección.*** Sólo podemos aceptar notificaciones de retiro de DMCA para obras protegidas por derechos de autor y que identifiquen un trabajo específico con derechos de autor. Si tienes una queja sobre el abuso de la marca registrada, consulta nuestra [política de marcas](/articles/github-trademark-policy/). Si desea eliminar datos sensibles como contraseñas, consulta nuestra [política sobre datos sensibles](/articles/github-sensitive-data-removal-policy/). Si usted está tratando con difamación u otro comportamiento abusivo, por favor consulta nuestras [Directrices de la comunidad](/articles/github-community-guidelines/). + +***El código es diferente de otro contenido creativo.*** GitHub está construido para colaborar en el código de software. Esto hace que la identificación de una infracción válida de derechos de autor sea más complicada de lo que podría ser de otra manera para, fotos, música o videos, por ejemplo. + +Existen diversas razones por las que el código es diferente de otros contenidos creativos. Por ejemplo: + +- Un repositorio puede incluir bits y partes de código de muchas personas diferentes, pero sólo un archivo o incluso una subrutina dentro de un archivo infringe tus derechos de autor. +- El código mezcla funcionalidad con expresión creativa, pero los derechos de autor sólo protegen los elementos expresivos, no las partes que son funcionales. +- A menudo hay licencias a considerar. El hecho de que una parte del código tenga una notificación de derechos de autor no significa necesariamente que sea infractora. Es posible que el código se esté utilizando de acuerdo con una licencia de código abierto. +- Un uso particular puede ser [uso legítimo](https://www.lumendatabase.org/topics/22) si solamente utiliza una pequeña cantidad del contenido protegido por derechos de autor, si utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado. +- Se puede alegar que el código infringe de muchas formas diferentes, exigiendo explicaciones detalladas e identificaciones de obras. + +Esta lista no es exhaustiva, por lo que hablar con un profesional legal sobre tu propuesta de reclamación es doblemente importante cuando se trata de un código. + +***Sin bots.*** Deberías contar con un profesional capacitado para evaluar los datos de cada notificación de retito que envíes. Si estás subcontratando tus labores a un tercero, asegúrate de saber cómo trabajand y asegúrate que no estén utilizando bots automatizados para presentar quejas en masa. ¡Estas quejas a menudo no son válidas y su procesamiento da lugar a la supresión innecesaria de proyectos! + +***Los temas de derechos de autor son difíciles.*** Puede ser muy difícil determinar si un trabajo en particular está protegido o no por derechos de autor. Por ejemplo, los hechos (incluyendo los datos) generalmente no tienen derechos de autor. Las palabras y las frases cortas generalmente no tienen derechos de autor. Las URLs y los nombres de dominio generalmente no tienen derechos de autor. Dado que sólo puede utilizar el proceso DMCA para abordar contenido protegido por derechos de autor, deberías hablar con un abogado si tienes preguntas sobre si tu contenido es o no protegible. + +***Puedes recibir una contra notificación.*** Cualquier usuario afectado por tu notificación de retiro puede decidir enviar una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Si lo hacen, reactivaremos tu contenido en un plazo de 10 a 14 días a menos que nos notifique que has iniciado una acción legal encaminada a impedir que el usuario se involucre en infringir la actividad relacionada con el contenido en GitHub. + +***Tu queja se publicará.*** Como se indica en nuestra [política de DMCA](/articles/dmca-takedown-policy#d-transparency), después de modificar la información personal, publicamos todas las notificaciones de retiro completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca). + +***GitHub no es el juez.*** GitHub ejerce poca discreción en el proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio. + +### Tu queja debe ... + +1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una notificación de DMCA.** No nos negaremos a procesar una queja completa si no incluye esta declaración. Pero sabremos que no has leído estas directrices y podríamos solicitarte que regreses y lo lleves a cabo. + +2. **Identifica el trabajo con derechos de autor que consideras que ha sido infringido.** Esta información es importante porque ayuda al usuario afectado a evaluar su reclamación y le da la capacidad de comparar su trabajo con el tuyo. La especificidad de su identificación dependerá de la naturaleza del trabajo que consideras que ha sido infringido. Si has publicado tu trabajo, solo podrás enlazar a una página web donde reside. Si es autónoma y no está publicada, puedes describirlo y explicar que es propietario. Si lo has registrado en la Oficina de Derechos de Autor, debes incluir el número de registro. Si estás alegando que el contenido alojado es una copia directa y literal de tu trabajo, también puedes explicar ese hecho. + +3. **Identifica el material al que haces referencia que está infringiendo el trabajo protegido por derechos de autor que aparece en el artículo #2, anterior.** Es importante ser lo más específico posible en tu identificación. Esta identificación debe ser razonablemente suficiente para permitir a GitHub localizar el material. Como mínimo, esto significa que debe incluir la URL del material que supuestamente infringe sus derechos de autor. Si aseguras que se infringe menos de un repositorio completo, identifica el(los) archivo(s) específicos o números de línea dentro de un archivo al que te refieres. Si aseguras que se infringe todo el contenido en una URL, por favor se explícito al respecto también. Por último, ten en cuenta que GitHub *no* deshabilitará automáticamente los [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) al desactivar un repositorio matriz. Si has investigado y analizado los forks de un repositorio y crees que también están infringiendo, por favor identifique explícitamente cada fork supuestamente infractor. Por favor, confirma también que has investigado cada caso individual y que tus declaraciones juradas se aplican a cada fork identificado. + +4. **Explica lo que el usuario afectado tendría que hacer para remediar la infracción.** De nuevo, la especificidad es importante. Cuando transmitimos su queja al usuario, esto les dirá lo que tienen que hacer para evitar que el resto de su contenido esté desactivado. ¿Necesita el usuario añadir una declaración de atribución? ¿Necesitan eliminar ciertas líneas dentro de su código, o archivos completos? Por supuesto, entendemos en algunos casos, todo el contenido de un usuario puede infringirse presuntamente y no hay nada que puedan hacer más que borrarlo todo. Si ese es el caso, por favor deja esto claro también. + +5. **Proporciona tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección. + +6. **Proporciona información de contacto, si la conoces, para el presunto infractor.** Generalmente esto se realizará proporcionando el nombre de usuario de GitHub asociado con el contenido presuntamente infractor. Sin embargo, puede haber casos en los que tengas conocimientos adicionales sobre el presunto infractor. Si es así, por favor comparte esa información con nosotros. + +7. **Incluye la siguiente declaración: "Tengo buena fe en que el uso de los materiales protegidos por derechos de autor descritos anteriormente en las páginas web infractoras no está autorizado por el propietario de los derechos de autor, o su agente, o la ley. He tenido en cuenta el uso justo."** + +8. **También incluye la siguiente declaración: "Juro, bajo pena de perjurio, que la información de esta notificación es exacta y que soy el propietario de los derechos de autor, o estoy autorizado para actuar en nombre del propietario, de un derecho exclusivo que se infringe presuntamente".** + +9. **Incluye tu firma física o electrónica.** + +### Quejas sobre Tecnología de Anti Elusión + +La Ley de Derechos de Autor también prohíbe la elusión de medidas tecnológicas que controlen eficazmente el acceso a las obras protegidas por los derechos de autor. Si crees que el contenido alojado en GitHub viola esta prohibición, por favor envíanos un informe a través de nuestro {% data variables.contact.contact_dmca %}, e incluye información específica sobre qué contenido viola esa prohibición, qué medidas tecnológicas aplicas y por qué el contenido viola la prohibición. + +### Como presentar tu queja + +La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}. + +También puedes enviar una notificación por correo electrónico a . Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje. + +Si debes enviar tu aviso por correo físico, también puedes hacerlo pero tardará *substancialmente* en que lo recibamos y respondamos al mismo. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es: + +``` +GitHub, Inc +En atención a: Agente de DMCA +88 Colin P Kelly Jr St +San Francisco, CA. 94107 +``` diff --git a/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md new file mode 100644 index 0000000000000..09b7c27243e6a --- /dev/null +++ b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -0,0 +1,183 @@ +--- +title: Pautas para las solicitudes legales de los datos del usuario +redirect_from: + - /law-enforcement-guidelines/ + - /articles/guidelines-for-legal-requests-of-user-data +versions: + free-pro-team: '*' +--- + +¿Eres un agente de la policía que lleva a cabo una investigación que pueda implicar contenido de usuario alojado en GitHub? O quizá seas una persona consciente de la privacidad y te gustaría saber qué información compartimos con las fuerzas policiales y bajo qué circunstancias. Cualquiera que sea la razón, estás en la página correcta. + +En estas pautas, proporcionamos algunos antecedentes sobre lo que es GitHub, los tipos de datos que tenemos y las condiciones bajo las cuales divulgaremos información privada del usuario. Sin embargo, antes de entrar en los detalles, aquí se presentan algunos detalles importantes que quizás deseas saber: + +- [**Notificaremos a los usuarios afectados**](#we-will-notify-any-affected-account-owners) sobre cualquier solicitud de información de su cuenta a menos que se prohíba hacerlo por ley u orden judicial. +- No divulgaremos **datos de seguimiento de ubicación**, tales como registros de direcciones IP, sin una [orden judicial válida o orden de registro](#with-a-court-order-or-a-search-warrant). +- No divulgaremos ningún **contenido privado del usuario**, incluyendo el contenido de repositorios privados, sin una [orden de registro válida](#only-with-a-search-warrant). + +### Acerca de estas pautas + +Nuestros usuarios confían en nosotros con sus proyectos de software y código - a menudo algunos de sus activos personales o comerciales más valiosos. Mantener esa confianza es esencial para nosotros, lo que significa mantener los datos de los usuarios seguros y privados. + +Mientras que la abrumadora mayoría de nuestros usuarios utilizan los servicios de GitHub para crear nuevas empresas, para construir nuevas tecnologías y para el mejoramiento general de la humanidad, reconocemos que con millones de usuarios repartidos por todo el mundo, no hay duda de que habrá algunas excepciones. En esos casos, deseamos ayudar a las fuerzas policiales a servir a su legítimo interés de proteger al público. + +Al proporcionar pautas para el personal encargado de hacer cumplir la ley, esperamos lograr un equilibrio entre los intereses a menudo contrapuestos de la privacidad y la justicia de los usuarios. Esperamos que estas pautas ayuden a establecer expectativas por ambas partes, así como a añadir transparencia a los procesos internos de GitHub. Nuestros usuarios deben saber que valoramos su información privada y que hacemos nuestro mejor esfuerzo para protegerla. Como mínimo, esto significa la liberación de datos a terceros solo cuando se hayan cumplido los requisitos legales adecuados. Por el mismo token, también esperamos educar a los profesionales de la aplicación de la ley sobre los sistemas de GitHub, para que puedan adaptar de manera más eficiente sus solicitudes de datos y dirigir justo esa información necesaria para llevar a cabo su investigación. + +### Terminología GitHub + +Antes de solicitarnos que divulguemos datos, podría ser útil entender cómo se implementa nuestro sistema. GitHub aloja millones de repositorios de datos usando el [sistema de control de versiones Git](https://git-scm.com/video/what-is-version-control). Los repositorios en GitHub—que pueden ser públicos o privados—se utilizan más comúnmente para proyectos de desarrollo de software pero también se utilizan a menudo para trabajar en el contenido de todo tipo. + +- [**Usuarios**](/articles/github-glossary#user) — Los usuarios están representados en nuestro sistema como cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede tener múltiples repositorios. Los usuarios pueden crear o ser invitados a unirse a organizaciones o a colaborar en el repositorio de otro usuario. + +- [**Colaboradores**](/articles/github-glossary#collaborator) — Un colaborador es un usuario con acceso de lectura y escritura a un repositorio que ha sido invitado a contribuir por el propietario del repositorio. + +- [**Organizaciones**](/articles/github-glossary#organization) — Las organizaciones son un grupo de dos o más usuarios que normalmente reflejan las organizaciones del mundo real, como empresas o proyectos. Son administrados por usuarios y pueden contener tanto repositorios como equipos de usuarios. + +- [**Repositorios**](/articles/github-glossary#repository) — Un repositorio es uno de los elementos más básicos de GitHub. Pueden ser los más fáciles de imaginar como una carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena cada historial de revisión del archivo. Los repositorios pueden tener múltiples colaboradores y, a discreción de sus administradores, pueden ser públicos o no. + +- [**Páginas**](/articles/what-is-github-pages) — Las páginas de GitHub son páginas web públicas libremente alojadas por GitHub que los usuarios pueden publicar fácilmente a través del código almacenado en sus repositorios. Si un usuario u organización tiene una página de GitHub, generalmente se puede encontrar en una URL como `https://username. ithub.io` o pueden tener la página web mapeada a su propio nombre de dominio personalizado. + +- [**Gists**](/articles/creating-gists) — Gists son fragmentos de código fuente u otro texto que los usuarios pueden usar para almacenar ideas o compartir con amigos. Al igual que los repositorios normales de GitHub, las listas se crean con Git, por lo que son automáticamente versionadas, bifurcables y descargables. Las listas pueden ser públicas o secretas (accesibles solo a través de una URL conocida). Los Gists públicos no pueden convertirse en Gists secretos. + +### Datos de usuario en GitHub.com + +Aquí hay una lista no exhaustiva de los tipos de datos que mantenemos sobre usuarios y proyectos en GitHub. + +- +**Datos de cuenta pública** — Hay una variedad de información disponible públicamente en GitHub sobre los usuarios y sus repositorios. Los perfiles de usuario se pueden encontrar en una URL como `https://github.com/username`. Los perfiles de usuario muestran información acerca de cuándo creó su cuenta el usuario, así como su actividad pública en GitHub.com e interacciones sociales. Los perfiles de usuario públicos también pueden incluir información adicional que un usuario pudo haber decidido compartir públicamente. Visualización de todos los perfiles públicos del usuario: + - Nombre de usuario + - Los repositorios que el usuario ha marcado + - Los otros usuarios de GitHub que el usuario sigue + - Los usuarios que los siguen + + Opcionalmente, un usuario también puede elegir compartir la siguiente información públicamente: + - Su nombre real + - Un avatar + - Una empresa afiliada + - Su ubicación + - Una dirección de correo electrónico pública + - Su página web personal + - Organizaciones de las que el usuario es miembro (*dependiendo de las preferencias de las organizaciones o de los usuarios*) + +- +**Datos privados de la cuenta** — GitHub también recopila y mantiene cierta información privada sobre los usuarios como se describe en nuestra [Política de Privacidad](/articles/github-privacy-statement).+ Puede incluir: + - Direcciones de correo electrónico privadas + - Detalles de pago + - Registros de acceso de seguridad + - Datos sobre interacciones con los repositorios privados + + Para obtener un sentido del tipo de información de cuenta privada que recopila GitHub, puedes visitar tu {% data reusables.user_settings.personal_dashboard %} y navegar por las secciones de la barra de menú de la izquierda. + +- +**Datos de cuenta de la organización** — La información sobre organizaciones, sus usuarios administrativos y repositorios está disponible públicamente en GitHub. Los perfiles de la organización se pueden encontrar en una URL como `https://github.com/organization`. Los perfiles de las organizaciones públicas también pueden incluir información adicional que los propietarios han decidido compartir públicamente. Visualización de todos los perfiles públicos de la organización: + - Nombre de la organización + - Los repositorios que los propietarios han marcado + - Todos los usuarios de GitHub que son propietarios de la organización + + Opcionalmente, los usuarios administrativos también pueden optar por compartir públicamente la siguiente información: + - Un avatar + - Una empresa afiliada + - Su ubicación + - Miembros directos y equipos + - Colaboradores + +- +**Datos del repositorio público** — GitHub es el hogar de millones de proyectos públicos de software de código público. Puede navegar casi cualquier repositorio público (por ejemplo, el [Proyecto Atom](https://github.com/atom/atom)) para tener un sentido de la información que GitHub recopila y mantiene sobre repositorios. Puede incluir: + + - El código + - Versiones anteriores del código + - Versiones de lanzamiento estables del proyecto + - Información sobre colaboradores, contibuyentes y miembros del repositorio + - Registros de operaciones de Git como confirmaciones, ramificar, subir, extraer, bifurcar y clonar + - Conversaciones relacionadas con operaciones de Git como comentarios sobre solicitudes de extracción o confirmaciones + - Documentación del proyecto como Cuestiones y páginas Wiki + - Estadísticas y gráficos que muestran contribuciones al proyecto y a la red de colaboradores + +- +**Datos privados del repositorio** — GitHub recopila y mantiene el mismo tipo de datos para los repositorios privados que se pueden ver en los repositorios públicos, excepto que solamente los usuarios invitados específicamente puedan acceder a los datos del repositorio privado. + +- +**Otros datos** - Adicionalmente, GitHub recopila datos analíticos tales como visitas de páginas e información ocasionalmente voluntaria por nuestros usuarios (por ejemplo, comunicaciones con nuestro equipo de soporte, información de la encuesta y/o registros del sitio). + +### Notificaremos a los propietarios de las cuentas afectadas + +Es nuestra política notificar a los usuarios sobre cualquier solicitud pendiente con respecto a sus cuentas o repositorios, a menos que se nos prohíba por ley u orden judicial hacerlo. Antes de revelar la información del usuario haremos un esfuerzo razonable para notificar a cualquier dueño de la cuenta afectada enviando un mensaje a su dirección de correo electrónico verificada proporcionándoles una copia de la cita, orden judicial u orden para que puedan tener la oportunidad de impugnar el proceso legal si lo desean. En circunstancias (raras) exigentes, podemos retrasar la notificación si determinamos que el retraso es necesario para prevenir la muerte o daños graves. + +### Divulgación de información no pública + +Es nuestra política divulgar información de usuario no pública en relación con una investigación civil o criminal solo con el consentimiento del usuario o tras la recepción de una citación válida, demanda de investigación civil, orden judicial, orden de búsqueda u otro proceso legal válido similar. En ciertas circunstancias exigentes (véase abajo), también podemos compartir información limitada pero sólo correspondiente a la naturaleza de las circunstancias y requeriremos un proceso legal para cualquier tema adicional. GitHub se reserva el derecho de objetar cualquier solicitud de información no pública. Cuando GitHub acuerde producir información no pública en respuesta a una solicitud legal, realizaremos una búsqueda razonable para la información solicitada. Estos son los tipos de información que acordaremos producir, dependiendo del tipo de proceso legal que atendamos: + +- +**Con el consentimiento del usuario** — GitHub proporcionará información de cuenta privada, si se solicita, directamente al usuario (o un propietario, en el caso de una cuenta de organización) o a un tercero designado con el consentimiento por escrito del usuario una vez que GitHub esté satisfecho de que el usuario haya verificado su identidad. + +- +**Con una citación ** — Si atiende una solicitud de investigación civil válida o un proceso legal similar emitido en relación con una investigación penal o civil oficial, podemos proporcionar cierta información de cuenta no pública, que puede incluir: + + - Nombre(s) asociados con la cuenta + - Dirección(es) de correo electrónico asociada(s) a la cuenta + - Información de facturación + - Fecha de registro y fecha de finalización + - Dirección IP, fecha y hora al momento del registro de la cuenta + - Dirección(es) IP utilizada para acceder a la cuenta en un momento o evento específico relevante para la investigación + +En el caso de cuentas de organización, podemos proporcionar el(los) nombre(s) y la(s) dirección(es) de correo electrónico del propietario(s) de la cuenta, así como la fecha y la dirección IP en el momento de la creación de la cuenta de la organización. No produciremos información sobre otros miembros o colaboradores, si existen, a la cuenta de la organización o cualquier información adicional relacionada con el propietario o dueño de la cuenta identificada sin una solicitud de seguimiento para esos usuarios específicos. + +Tenga en cuenta que la información disponible variará de un caso a otro. Parte de la información es opcional para que los usuarios la proporcionen. En otros casos, es posible que no hayamos recopilado ni conservado la información. + +- +**Con una orden judicial *o* una orden de registro** — No divulgaremos registros de acceso a la cuenta a menos que se nos obligue a hacerlo por (i) una orden judicial emitida bajo 18 U. S.C. Sección 2703(d), sobre una muestra de hechos específicos y articulables que demuestran que existen motivos razonables para creer que la información solicitada es relevante y material para una investigación criminal en curso; o (ii) una orden de búsqueda emitida bajo los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal sobre una muestra de causa probable. Además de la información no pública de la cuenta de usuario listada anteriormente podemos proporcionar registros de acceso a la cuenta en respuesta a una orden judicial o a una orden de registro, que puede incluir: + + - Cualquier registro que revele los movimientos de un usuario a lo largo de un período de tiempo + - Configuración de la cuenta o repositorio privado (por ejemplo, qué usuarios tienen ciertos permisos, etc.) + - Datos analíticos específicos del usuario o IP, como el historial de navegación + - Registros de acceso de seguridad distintos a la creación de cuentas o para una fecha y hora específica + +- +**Sólo con una orden de registro** — No divulgaremos el contenido privado de ninguna cuenta de usuario a menos que se lo obligue a hacerlo bajo una orden de registro emitida de acuerdo con los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal al mostrar una causa probable. Además de la información no pública de la cuenta de usuario y los registros de acceso a la cuenta mencionados anteriormente también proporcionaremos contenido privado de la cuenta de usuario en respuesta a una orden de registro, que puede incluir: + + - Contenidos de Gists secretos + - Código fuente u otro contenido en los repositorios privados + - Registros de contribución y colaboración para los repositorios privados + - Comunicaciones o documentación (como Cuestiones o Wikis) en depósitos privados + - Cualquier clave de seguridad usada para autenticación o cifrado + +- +**Bajo circunstancias exigentes** — Si recibimos una solicitud de información bajo ciertas circunstancias exigentes (donde creemos que la divulgación es necesaria para prevenir una emergencia que implique peligro de muerte o lesiones físicas graves a una persona), podemos divulgar información limitada que determinamos necesaria para permitir que las fuerzas policiales atiendan la emergencia. Para cualquier información adicional, necesitaríamos una citación, una orden de registro, una orden judicial, como se describe anteriormente. Por ejemplo, no divulgaremos contenidos de repositorios privados sin una orden de registro. Antes de divulgar la información, confirmamos que la solicitud procedía de una agencia policial, que una autoridad haya enviado una notificación oficial resumiendo la emergencia y cómo la información solicitada ayudará a resolver la emergencia. + +### Reembolso de costes + +Nos reservamos el derecho de solicitar el reembolso de los gastos administrativos asociados con la respuesta a las solicitudes de información, de acuerdo con lo permitido por la ley. + +### Conservación de datos + +Tomaremos medidas para preservar los registros de la cuenta por hasta 90 días desde que se tenga una solicitud formal de las autoridades policiales de los EE. UU. en conexión con las investigaciones criminales oficiales, y pendiente de emitir una orden judicial u otro proceso. + +### Cómo enviar solicitudes + +Envía solicitudes a: + +``` +GitHub, Inc. +c/o Corporation Service Company +2710 Gateway Oaks Drive, Suite 150N +Sacramento, CA 95833-3505 +``` + +Por favor, realiza tus solicitudes lo más específicas y limitadas posible, incluyendo la siguiente información: + +- Información completa sobre la autoridad que emite la solicitud de información +- El nombre y el gafete/ID del agente responsable +- Una dirección de correo electrónico oficial y número de teléfono de contacto +- El usuario, organización, nombre(s) del repositorio de interés +- Las URLs de cualquier página, lista o archivos de interés +- La descripción de los tipos de registros que necesitas + +Por favor, espera al menos dos semanas para que podamos examinar tu solicitud. + +### Solicitudes de aplicación de la ley extranjera + +Como empresa de Estados Unidos con sede en California, GitHub no está obligada a proporcionar datos a los gobiernos extranjeros en respuesta al proceso legal emitido por autoridades extranjeras. Los funcionarios encargados de hacer cumplir la ley extranjera que deseen solicitar información a GitHub deben ponerse en contacto con la Oficina de Asuntos Internacionales del Departamento de Justicia de los Estados Unidos. GitHub responderá rápidamente a las solicitudes que se emitan a través del tribunal de los Estados Unidos mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory. + +### Preguntas + +¿Tiene otras preguntas, comentarios o sugerencias? Ponte en contacto con {% data variables.contact.contact_support %}. diff --git a/translations/es-ES/content/github/site-policy/index.md b/translations/es-ES/content/github/site-policy/index.md new file mode 100644 index 0000000000000..b9c717f5084e2 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/index.md @@ -0,0 +1,50 @@ +--- +title: Política del sitio +redirect_from: + - /categories/61/articles/ + - /categories/site-policy +versions: + free-pro-team: '*' +--- + + +### Índice + +{% link_in_list /github-terms-of-service %} +{% link_in_list /github-corporate-terms-of-service %} +{% link_in_list /github-privacy-statement %} +{% link_in_list /global-privacy-practices %} +{% link_in_list /github-insights-and-data-protection-for-your-organization %} +{% link_in_list /github-sponsors-additional-terms %} +{% link_in_list /github-additional-product-terms %} +{% link_in_list /github-logo-policy %} +{% link_in_list /github-username-policy %} +{% link_in_list /submitting-content-removal-requests %} +{% link_in_list /dmca-takedown-policy %} +{% link_in_list /guide-to-submitting-a-dmca-takedown-notice %} +{% link_in_list /guide-to-submitting-a-dmca-counter-notice %} +{% link_in_list /github-trademark-policy %} +{% link_in_list /github-sensitive-data-removal-policy %} +{% link_in_list /github-subprocessors-and-cookies %} +{% link_in_list /github-bug-bounty-program-legal-safe-harbor %} +{% link_in_list /responsible-disclosure-of-security-vulnerabilities %} +{% link_in_list /guidelines-for-legal-requests-of-user-data %} +{% link_in_list /github-government-takedown-policy %} +{% link_in_list /github-acceptable-use-policies %} +{% link_in_list /githubs-notice-about-the-california-consumer-privacy-act %} +{% link_in_list /github-community-guidelines %} +{% link_in_list /github-community-forum-code-of-conduct %} +{% link_in_list /github-registered-developer-agreement %} +{% link_in_list /github-marketplace-terms-of-service %} +{% link_in_list /github-marketplace-developer-agreement %} +{% link_in_list /github-pre-release-program %} +{% link_in_list /github-research-program-terms %} +{% link_in_list /github-open-source-applications-terms-and-conditions %} +{% link_in_list /github-and-trade-controls %} +{% link_in_list /github-deceased-user-policy %} +{% link_in_list /github-statement-against-modern-slavery-and-child-labor %} +{% link_in_list /github-anti-bribery-statement %} +{% link_in_list /github-gifts-and-entertainment-policy %} +{% link_in_list /github-event-terms %} +{% link_in_list /github-event-code-of-conduct %} +{% link_in_list /github-gpl-cooperation-commitment %} diff --git a/translations/es-ES/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md b/translations/es-ES/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md new file mode 100644 index 0000000000000..290e4618a95aa --- /dev/null +++ b/translations/es-ES/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md @@ -0,0 +1,16 @@ +--- +title: Divulgación responsable de vulnerabilidades de seguridad +redirect_from: + - /responsible-disclosure/ + - /articles/responsible-disclosure-of-security-vulnerabilities +versions: + free-pro-team: '*' +--- + +Deseamos mantener a GitHub seguro para todos. Si has descubierto una vulnerabilidad de seguridad en GitHub, apreciamos tu ayuda para revelárnosla de manera responsable. + +### Programa de recompensas + +Al igual que muchas otras grandes empresas de software, GitHub proporciona una recompensa de errores para mejorar la relación con los investigadores de seguridad. La idea es simple: Los hackers y los investigadores de seguridad (como tú) encuentran y reportan vulnerabilidades a través de nuestro proceso de divulgación responsable. Posteriormente, para reconocer el esfuerzo significativo que estos investigadores suelen presentan cuando cazan errores, los recompensamos con algo de dinero en efectivo. + +Revisa el sitio [Recompensa de Errores de GitHub](https://bounty.github.com) para obtener detalles de recompensas, revisa también nuestros términos amplios de la [Disposición de seguridad legal ](/articles/github-bug-bounty-program-legal-safe-harbor) y ¡Feliz caza! diff --git a/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md new file mode 100644 index 0000000000000..de65b2a5cb23d --- /dev/null +++ b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md @@ -0,0 +1,22 @@ +--- +title: Enviar solicitudes de eliminación de contenido +redirect_from: + - /articles/submitting-content-removal-requests +versions: + free-pro-team: '*' +--- + +Entendemos que los derechos de autor, marca registrada, o contenido sensible puede publicarse en GitHub –ya sea accidentalmente o con fin– a veces en repositorios que no posees. Debido a que la naturaleza de este contenido varía y debido a las diferentes leyes aplicables, cada categoría tiene sus propios requisitos de presentación de informes definidos en nuestras políticas. + +Si quieres solicitar que el contenido se elimine de GitHub, por favor toma algo de tiempo para consultar cada una de estas políticas y sus respectivos requisitos para informar antes de enviar un informe. Si recibimos un informe incompleto, tendremos que pedir aclaraciones o revisiones y tendrás que enviar nuevamente un informe revisado. + +Ten en cuenta que no podemos ayudarte a determinar qué política es adecuada para su situación específica. Si revisaste las siguientes políticas y aún tienes preguntas sobre si el contenido debe informarse o no como copyright o datos sensibles, recomendamos consultar con asesoría jurídica independiente. + +### [Política de retiro de DMCA](/articles/dmca-takedown-policy) +La Política de Retiro de DMCA se puede utilizar para informar del contenido que consideras que infringe un copyright propiedad de tu parte o de su organización. Una vez que hayas revisado la política, es posible que también desees revisar nuestra [Guía para enviar una Política de Retiro de DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice/) antes de enviar un informe. + +### [Política de marca registrada de GitHub](/articles/github-trademark-policy) +La Política de Marcas de GitHub se puede utilizar para informar del contenido que parece utilizar su nombre de empresa o de negocio, logotipo, u otros materiales protegidos por marca de una manera que pueda engañar o confundir a otros sobre la marca o la afiliación comercial. + +### [Política de eliminación de datos sensibles de GitHub](/articles/github-sensitive-data-removal-policy) +La Política de Eliminación de Datos Sensibles de GitHub se puede utilizar para informar de datos que son sensibles o confidenciales y plantean un riesgo de seguridad, pero eso no está necesariamente protegido por derechos de autor o marca registrada. diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md new file mode 100644 index 0000000000000..2b7dfe96adb29 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -0,0 +1,36 @@ +--- +title: Acerca de los patrocinadores para colaboradores de código abierto en GitHub +intro: 'Si aportas valor a un proyecto de código abierto, puedes convertirte en un colaborador patrocinado para recibir pagos por tu trabajo.' +redirect_from: + - /articles/about-github-sponsors-for-sponsored-developers + - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers +versions: + free-pro-team: '*' +--- + +### Unirte a {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.you-can-be-a-sponsored-developer %}Para obtener más información, consulta [Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". + +{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". + +Una vez que te hayas unido a {% data variables.product.prodname_sponsors %}, puedes añadir un botón de "patrocinar" al repositorio de código abierto en el que contribuyes para incrementar la visibilidad de tu perfil de {% data variables.product.prodname_sponsors %} y de otras plataformas de fondeo. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)". + +Puedes configurar una meta para tus patrocinios. Para obtener más información, consulta la sección "[Administrar tu meta de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal)". + +{% data reusables.sponsors.github-contact-applicants %} + +### Niveles de patrocinio + +{% data reusables.sponsors.tier-details %}Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)", "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)", y "[Cambiar tus niveles de patrocinio](/articles/changing-your-sponsorship-tiers)". + +### Pagos de patrocinios + +{% data reusables.sponsors.no-fees %} + +{% data reusables.sponsors.payout-info %} + +Para obtener más información, consulta "[Administrar tus pagos de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)". + +### Further reading +- "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md new file mode 100644 index 0000000000000..61b97f9b7dffd --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -0,0 +1,43 @@ +--- +title: Acerca de los Patrocinadores de GitHub +intro: '{% data variables.product.prodname_sponsors %}permite a la comunidad de desarrolladores apoyar financieramente al personal y organizaciones que diseñan, construyen y mantienen los proyectos de código abierto de los cuales dependen, directamente en {% data variables.product.product_name %}.' +redirect_from: + - /articles/about-github-sponsors +versions: + free-pro-team: '*' +--- + +### Acerca de {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". + +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario ](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". + +{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". + +Cuando te conviertes en un desarrollador patrocinado u organización patrocinada, aplicarán las condiciones adicionales de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta la sección "[Condiciones Adicionales de GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms)". + +### Acerca de {% data variables.product.prodname_matching_fund %} + +{% note %} + +**Nota:**{% data reusables.sponsors.matching-fund-eligible %} + +{% endnote %} + +El {% data variables.product.prodname_matching_fund %} pretende beneficiar a los miembros de la comunidad de {% data variables.product.prodname_dotcom %} quienes desarrollan software de código abierto que promueve los [Lineamientos de la Comunidad de {% data variables.product.prodname_dotcom %}](/github/site-policy/github-community-guidelines). Los pagos desde las organizaciones y hacia las organizaciones patrocinadas no son elegibles para {% data variables.product.prodname_matching_fund %}. + +Para ser elegible para el {% data variables.product.prodname_matching_fund %}, debes crear un perfil que atraiga a la comunidad que te mantendrá a largo plazo. Para obtener más información acerca de crear un perfil llamativo, consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)". + +{% data reusables.sponsors.legal-additional-terms %} + +### Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %} + +Este es sólo el inicio — nos encantaría tener tu opinión para garantizar que {% data variables.product.prodname_sponsors %} siga satisfaciendo tus necesidades. Por favor, envíanos tu retroalimentación o sugerencias contactando a [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). + +### Further reading +- "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" +- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". +- "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000000..e190dee73bec1 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Atribuir los patrocinios a tu organización +intro: 'Puedes atribuir los patrocinios que paga una de tus organizaciones a otra organización.' +versions: + free-pro-team: '*' +permissions: Los propietarios que sean dueños de ambas organizaciones, pueden atribuir los patrocinios de una a otra de ellas. +--- + +1. Navega a la organización cuyo patrocinio quieras atribuir a otra organización. +1. Debajo del nombre de tu organización, da clic en {% octicon "heart" aria-label="The heart icon" %}**Patrocinar**. ![Pestaña de "Patrocinar"](/assets/images/help/sponsors/sponsoring-tab.png) +1. En la esquina superior derecha, da clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**. ![Botón de "Configuración"](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Debajo de "Vincular patrocinios con otra cuenta", utiliza el menú desplegable y da clic en la organización a la que quieras atribuir los patrocinios de ésta. ![Menú desplegable para seleccionar una cuenta](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Da clic en **Vincular cuenta**. ![Botón de "Vincular cuenta"](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md new file mode 100644 index 0000000000000..416569078ec14 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -0,0 +1,32 @@ +--- +title: Cambiar tus niveles de patrocinio +intro: 'Puedes agregar un nuevo nivel de patrocinio o editar o retirar un nivel existente.' +redirect_from: + - /articles/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +--- + +### Acerca de los niveles de patrocinio + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +### Agregar un nivel + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.click-add-tier %} +{% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.save-tier-draft %} +{% data reusables.sponsors.review-and-publish-tier %} + +### Editar o retirar un nivel + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.edit-tier %} +{% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.tier-update %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md new file mode 100644 index 0000000000000..2ed35fbcd2cf5 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -0,0 +1,22 @@ +--- +title: Configurar webhooks para eventos en tu cuenta patrocinada +intro: Puedes configurar wehbhooks para que te envíen una alerta cuando recibas nuevos patrocinios o cuando los patrocinadores existentes realicen cambios a sus patrocinios. +versions: + free-pro-team: '*' +--- + +### Acerca de los webhooks para los eventos en tu cuenta patrocinada + +Para monitorear los cambios a tus patrocinios, tales como las cancelaciones al final de un periodo de pago, puedes crear webhooks para tu cuenta patrocinada de usuario u organización. Cuando configuras un webhook para tu cuenta patrocinada, recibirás las actualizaciones cuando los patrocinios se creen, editen o borren. Para obtener más información, consulta el [evento de webhook de `sponsorship`](/webhooks/event-payloads/#sponsorship). + +### Administrar los webhooks para los eventos en tu cuenta patrocinada + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-webhooks-tab %} +{% data reusables.sponsors.add-webhook %} +{% data reusables.sponsors.add-payload-url %} +{% data reusables.sponsors.webhook-content-formatting %} +{% data reusables.sponsors.webhook-secret-token %} +{% data reusables.sponsors.add-active-triggers %} +{% data reusables.sponsors.confirm-add-webhook %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md new file mode 100644 index 0000000000000..87a9832b4afea --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Comunicarse con tus patrocinadores +intro: Puedes enviar un correo electrónico a los patrocinadores que optaron por recibir actualizaciones sobre tu trabajo. +redirect_from: + - /articles/contacting-your-sponsors +versions: + free-pro-team: '*' +--- + +### Acerca de las actualizaciones de los patrocinios + +Tus patrocinadores pueden elegir si desean recibir actualizaciones por correo electrónico sobre tu trabajo. Para obtener más información, consulta "[Administar tu patrocinio](/articles/managing-your-sponsorship)". + +Para las cuentas de desarrollador patrocinado, la actualización vendrá de la cuenta de correo electrónico primaria de tu cuenta de usuario. Si habilitaste la privacidad de direcciones de correo electrónico en tu cuenta de usuario, la actualización vendrá entonces de `noreply@github.com`. Para las organizaciones patrocinadas, la actualización vendrá de la dirección de correo electrónico de tipo `noreply@github.com` de la organización. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". + +### Comunicarse con tus patrocinadores + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.sponsors-updates-tab %} +{% data reusables.sponsors.draft-new-update %} +{% data reusables.sponsors.send-update-to-sponsors %} +{% data reusables.sponsors.write-sponsor-update %} +{% data reusables.sponsors.publish-sponsor-update %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md new file mode 100644 index 0000000000000..b7c9bee8b6219 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -0,0 +1,26 @@ +--- +title: Editar los detalles de tu perfil para los Patrocinadores de GitHub +intro: Puedes actualizar la información que ven los patrocinadores potenciales acerca de tu trabajo. +redirect_from: + - /articles/editing-your-sponsored-developer-profile + - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile +versions: + free-pro-team: '*' +--- + +### Acerca de los perfiles de patrocinador + +Tu perfil de {% data variables.product.prodname_sponsors %} les dice a los patrocinadores potenciales por qué deberían patrocinarte. Las personas ven tu perfil de patrocinador cuando dan clic en el botón **Patrocinador** de tu perfil. Te recomendamos incluir la información siguiente. + +- Trabajo de código abierto al que has contribuido +- Por qué estás comprometido con el desarrollo de código abierto + +### Editar las credenciales de tu perfil + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-profile-tab %} +{% data reusables.sponsors.short-bio %} +{% data reusables.sponsors.add-introduction %} +{% data reusables.sponsors.edit-featured-work %} +{% data reusables.sponsors.opt-in-to-being-featured %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/index.md new file mode 100644 index 0000000000000..de4805d98a48f --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -0,0 +1,31 @@ +--- +title: Soporte a la comunidad de código abierto con los patrocinadores de GitHub +shortTitle: Patrocinadores de GitHub +intro: 'Puedes apoyar a las personas y a los desarrolladores que diseñan, crean y mantienen los proyectos de código abierto de los cuales dependes si ofreces una compensación por ellos a través de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /categories/supporting-the-open-source-community-with-github-sponsors +versions: + free-pro-team: '*' +--- + + +### Índice + +{% topic_link_in_list /overview %} + {% link_in_list /about-github-sponsors %} +{% topic_link_in_list /sponsoring-open-source-contributors %} + {% link_in_list /sponsoring-an-open-source-contributor %} + {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} +{% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} + {% link_in_list /about-github-sponsors-for-open-source-contributors %} + {% link_in_list /setting-up-github-sponsors-for-your-user-account %} + {% link_in_list /setting-up-github-sponsors-for-your-organization %} + {% link_in_list /editing-your-profile-details-for-github-sponsors %} + {% link_in_list /managing-your-sponsorship-goal %} + {% link_in_list /changing-your-sponsorship-tiers %} + {% link_in_list /viewing-your-sponsors-and-sponsorships %} + {% link_in_list /managing-your-payouts-from-github-sponsors %} + {% link_in_list /configuring-webhooks-for-events-in-your-sponsored-account %} + {% link_in_list /contacting-your-sponsors %} + {% link_in_list /tax-information-for-github-sponsors %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md new file mode 100644 index 0000000000000..e2a8746d7edc5 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -0,0 +1,20 @@ +--- +title: Administrar tus pagos desde Patrocinadores de GitHub +intro: 'Puedes ver información sobre pagos pasados y futuros desde {% data variables.product.prodname_sponsors %} y editar tu información bancaria.' +redirect_from: + - /articles/managing-your-payouts-from-github-sponsors +versions: + free-pro-team: '*' +--- + +### Acerca de los pagos de {% data variables.product.prodname_sponsors %} + +Solo puedes administrar tus pagos de {% data variables.product.prodname_sponsors %} si recibes tu pago a través de Stripe Connect. Si se te paga a través de transferencia ACH o transferencia bancaria en tu cuenta de usuario, no verás la pestaña de **Pagos** en tu tablero de colaborador de código abierto. Las organizaciones patrocinadas solo podrán utilizar Stripe Connect para los pagos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %} para los colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)". + +{% data reusables.sponsors.payout-info %} + +### Visualizar y editar la información de pago + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-payouts-tab %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md new file mode 100644 index 0000000000000..33c2082a2149b --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -0,0 +1,39 @@ +--- +title: Administrar tu meta de patrocinio +intro: Puedes configurar una meta para tu cuenta de desarrollador u organización patrocinados para ayudar a que la comunidad entienda el impacto de patrocinarte. +versions: + free-pro-team: '*' +--- + +### Acerca de las metas de patrocinio + +Puedes configurar una meta de financiamiento para tu cuenta patrocinada y compartir la meta con tu comunidad. Las metas te ayudan a entender el impacto que tienes en la comunidad de código abierto y aumentan tu presencia en el programa de {% data variables.product.prodname_sponsors %}. + +Tu meta puede configurar un objetivo para la cantidad de patrocinadores que quieres tener o la cantidad de dinero que quieres ganar mensualmente. Solo puedes configurar una meta a la vez. Después de que llegues a tu meta, puedes configurar otra. + +### Configurar una meta + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-your-goals-tab %} +{% data reusables.sponsors.set-a-goal %} +{% data reusables.sponsors.select-goal-type %} +{% data reusables.sponsors.publish-goal %} + +### Editar una meta + +Cuando editas una meta, no puedes escoger la meta que ya hayas alcanzado. Por ejemplo, si ya tienes 5 patrocinadores, no puedes editar tu meta para que ahora sea de 4 patrocinadores. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-your-goals-tab %} +{% data reusables.sponsors.edit-goal %} +{% data reusables.sponsors.select-goal-type %} +{% data reusables.sponsors.publish-goal %} + +### Retirar una meta + +Después de que retiras una meta, no podrás reactivarla. En vez de esto, debes crear una meta nueva. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-your-goals-tab %} +{% data reusables.sponsors.edit-goal %} +{% data reusables.sponsors.retire-goal %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md new file mode 100644 index 0000000000000..c28562af82aec --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -0,0 +1,35 @@ +--- +title: Administrar tu patrocinio +intro: Puedes administrar quién puede ver tu patrocinio y si recibes actualizaciones por correo electrónico para la cuenta patrocinada. +redirect_from: + - /articles/managing-your-sponsorship +versions: + free-pro-team: '*' +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +### Administrar la configuración de privacidad para tu patrocinio + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.who-can-see-your-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} + +### Administrar las actualizaciones de correo electrónico para tu patrocinio + +Puedes elegir si una cuenta que patrocinas puede enviarte actualizaciones por correo electrónico sobre su trabajo o no. La cuenta patrocinada no tendrá acceso a tu dirección de correo electrónico. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.update-sponsorship %} + +### Further reading + +- "[Mejorar un patrocinio](/articles/upgrading-a-sponsorship)" +- "[Degradar un patrocinio](/articles/downgrading-a-sponsorship)" \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md new file mode 100644 index 0000000000000..56bffa7b93def --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md @@ -0,0 +1,8 @@ +--- +title: Resumen +intro: 'Aprende sobre {% data variables.product.prodname_sponsors %} y sobre cómo puedes involucrarte como patrocinador o como colaborador de código abierto.' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md new file mode 100644 index 0000000000000..9c42775755e29 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md @@ -0,0 +1,12 @@ +--- +title: Recibir patrocinios a través de patrocinadores de GitHub +shortTitle: Recibir patrocinios +intro: 'Tu organización o tú pueden convertirse en un colaborador de código abierto para recibir pagos por su trabajo, actualizar sus detalles de patrocinio y ver y contactar a sus patrocinadores.' +mapTopic: verdadero +redirect_from: + - /articles/receiving-sponsorships-as-a-sponsored-developer + - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md new file mode 100644 index 0000000000000..3312db091b2fb --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: Configurar los Patrocinadores de GitHub para tu organización +intro: 'Tu organización puede unirse a {% data variables.product.prodname_sponsors %} para recibir pagos por tu trabajo.' +redirect_from: + - /articles/setting-up-github-sponsorship-for-your-organization + - /articles/receiving-sponsorships-as-a-sponsored-organization +permissions: 'Los propietarios de organización pueden configurar {% data variables.product.prodname_sponsors %} para una organización.' +versions: + free-pro-team: '*' +--- + +### Unirte a {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %} + +Después de recibir una invitación para que tu organización se una a {% data variables.product.prodname_sponsors %} puedes completar los pasos a continuación para que se convierta en una organización patrocinada. + +Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador individual independiente a una organización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". + +{% data reusables.sponsors.navigate-to-github-sponsors %} +{% data reusables.sponsors.view-eligible-accounts %} +3. A la derecha de tu organización, da clic en **Unirse a la lista de espera**. +{% data reusables.sponsors.contact-info %} +{% data reusables.sponsors.accept-legal-terms %} + +### Completar un perfil de organización patrocinada + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-profile-tab %} +{% data reusables.sponsors.short-bio %} +{% data reusables.sponsors.add-introduction %} +{% data reusables.sponsors.meet-the-team %} +{% data reusables.sponsors.edit-featured-work %} +{% data reusables.sponsors.opt-in-to-being-featured %} +{% data reusables.sponsors.save-profile %} + +### Crear niveles de patrocinio + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.click-add-tier %} +{% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.save-tier-draft %} +{% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.add-more-tiers %} + +### Emitir tu información bancaria + +Como organización patrocinada, deberás recibir pagos en una cuenta bancaria dedicada a tu organización en una región compatible. Puedes obtener una cuenta bancaria comercial a través de servicios como [Open Collective](https://opencollective.com/) y [Stripe Atlas](https://stripe.com/atlas). La región en la cual opera legalmente tu organización y la región de tu cuenta bancaria deberán coincidir. La persona que configura a {% data variables.product.prodname_sponsors %} para la organización debe vivir en la región compatible también. {% data reusables.sponsors.stripe-supported-regions %} + +{% data reusables.sponsors.double-check-stripe-info %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.create-stripe-account %} + +Para obtener más información acerca de cómo configurar Stripe Connect utilizando Open Collective, consulta la sección [Configurar {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) en los documentos de Open Collective. + +### Emitir tu información de facturación + +{% data reusables.sponsors.tax-form-information-org %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.settings-tab %} +{% data reusables.sponsors.country-of-residence %} +{% data reusables.sponsors.overview-tab %} +{% data reusables.sponsors.tax-form-link %} + +### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %} + +Antes de que tu organización pueda convertirse en patrocinada, deberás habilitar la autenticación de dos factores en tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". + +### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.request-approval %} + +{% data reusables.sponsors.github-review-app %} + +### Further reading +- "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" +- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md new file mode 100644 index 0000000000000..c2a53048cb09b --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -0,0 +1,79 @@ +--- +title: Configurar a los Patrocinadores de GitHub para tu cuenta de usuario +intro: 'Puedes convertirte en un programador patrocinado al unirte a {% data variables.product.prodname_sponsors %}, completar tu perfil de programador patrocinado, crear niveles de patrocinio, enviar tu información bancaria y fiscal, y permitir una autenticación de dos factores en tu cuenta de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /articles/becoming-a-sponsored-developer + - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer +versions: + free-pro-team: '*' +--- + +### Unirte a {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %} + +Para unirte a {% data variables.product.prodname_sponsors %} comoorganización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". + +{% data reusables.sponsors.navigate-to-github-sponsors %} +2. Si eres un propietario de organización, tienes más de una cuenta elegible. Da clic en **Ver tus cuentas elegibles** y, posteriormente, en la lista de cuentas, encuentra tu cuenta de usuario. +3. Da clic en **Unirse a la lista de espera**. +{% data reusables.sponsors.contact-info %} +{% data reusables.sponsors.accept-legal-terms %} + +Si tienes una cuenta bancaria en una región compatible, {% data variables.product.prodname_dotcom %} revisará tu aplicación dentro de dos semanas. + +### Completar un perfil de programador patrocinado + +Una vez que {% data variables.product.prodname_dotcom %} revise tu aplicación, podrás configurar tu perfil de desarrollador patrocinado para que las personas puedan comenzar a patrocinarte. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-profile-tab %} +{% data reusables.sponsors.short-bio %} +{% data reusables.sponsors.add-introduction %} +{% data reusables.sponsors.edit-featured-work %} +{% data reusables.sponsors.opt-in-to-being-featured %} +{% data reusables.sponsors.save-profile %} + +### Crear niveles de patrocinio + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.click-add-tier %} +{% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.save-tier-draft %} +{% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.add-more-tiers %} + +### Emitir tu información bancaria + +Si vives en una región compatible, puedes seguir estas instrucciones para emitir tu información bancaria y crear una cuenta de Stripe Connect. La región en la cual resides y aquella en la que está tu cuenta bancaria deben coincidir. {% data reusables.sponsors.stripe-supported-regions %} + +{% data reusables.sponsors.double-check-stripe-info %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.create-stripe-account %} + +### Emitir tu información de facturación + +{% data reusables.sponsors.tax-form-information-dev %} + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.settings-tab %} +{% data reusables.sponsors.country-of-residence %} +{% data reusables.sponsors.overview-tab %} +{% data reusables.sponsors.tax-form-link %} + +### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %} + +Antes de que puedas convertirte en un programador patrocinado, debes habilitar 2FA en tu cuenta {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". + +### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +4. Haz clic en **Request approval** (Solicitar aprobación). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/sponsors/request-approval-button.png) + +{% data reusables.sponsors.github-review-app %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md new file mode 100644 index 0000000000000..1cb9b5d5c3930 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -0,0 +1,61 @@ +--- +title: Patrocinar a un colaborador de código abierto +intro: 'Puedes generar un pago mensual recurrente para un desarrollador u organización que diseñe, cree, o mantenga los proyectos de código abierto de los que dependes.' +redirect_from: + - /articles/sponsoring-a-developer + - /articles/sponsoring-an-open-source-contributor + - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer +versions: + free-pro-team: '*' +permissions: Cualquiera puede patrocinar cuentas en nombre de su propia cuenta de usuario. Los propietarios y gerentes de facturación de las organizaciones pueden patrocinar cuentas en nombre de su organización. +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +### Acerca de los patrocinios + +{% data reusables.sponsors.sponsorship-details %} + +Puedes patrocinar una cuenta en nombre de tu cuenta de usuario para invertir en los proyectos de los cuales te beneficies personalmente. Puedes patrocinar una cuenta en nombre de tu organización por varias razones. +- Mantener bibliotecas específicas de las cuales dependa el trabajo de tu organización +- Invertir en el ecosistema del cual dependes como organización (tal como blockchain) +- Desarrollar una conciencia de marca como una organización que valora el código abierto +- Agradecer a los desarrolladores de código abierto por crear bibliotecas que complementan el producto que ofrece tu organización + +Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. Si tu organización necesita que se le emita una factura, [contáctanos](https://support.github.com/contact/org-sponsors-waitlist). + +{% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". + +Cuando patrocinas una cuenta utilizando una tarjeta de crédito, el cargo tomará efecto de inmediato. {% data reusables.sponsors.prorated-sponsorship %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +Si la cuenta patrocinada retira tu nivel, éste permanecerá configurado hasta que elijas uno diferente o hasta que canceles tu suscripción. Para obtener más información, consulta "[Actualizar un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)." + +Si la cuenta que quieres patrocinar no tiene un perfil en {% data variables.product.prodname_sponsors %}, puedes alentarla a que se una. Para obtener más información, consulta las secciónes "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". + +{% data reusables.sponsors.sponsorships-not-tax-deductible %} + +{% note %} + +**Nota:**{% data variables.product.prodname_dotcom %} no se responzabiliza por cómo se auto-representan los desarrolladores ni tampoco respalda ninguno de los proyectos de código abierto patrocinados. Las alegaciones son responsabilidad total del desarrollador que recibe los fondos. Asegúrate de que confías en una persona antes de ofrecerle un patrocinio. Para obtener más información, consulta la sección de [Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms). + +{% endnote %} + +### Patrocinar una cuenta + +Antes de que puedas patrocinar una cuenta, debes tener una dirección de correo electrónico verificada. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)". + +1. En {% data variables.product.product_name %}, navega al perfil del usuario u organización que quieras patrocinar. +1. Navega a tu panel de patrocinios para la cuenta. + - Para patrocinar a un desarrollador, debajo de su nombre, da clic en **Patrocinar**. ![Botón de Patrocinador](/assets/images/help/profile/sponsor-button.png) + - Para patrocinar a una organización, a la derecha de su nombre, da clic en **Patrocinar**. ![Botón de Patrocinador](/assets/images/help/sponsors/sponsor-org-button.png) +1. Opcionalmente, a la derecha de la página, para patrocinar una cuenta en nombre de tu organización, utiliza el menú desplegable de **Patrocinar como**, y da clic en la organización. ![Menú desplegable para elegier la cuenta bajo la cual harás el patrocinio](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) +{% data reusables.sponsors.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} +{% data reusables.sponsors.select-sponsorship-billing %} + ![Botón de Editar pago](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) +{% data reusables.sponsors.who-can-see-your-sponsorship %} + ![Botones radiales para elegir quién puede ver tu patrocinio](/assets/images/help/sponsors/who-can-see-sponsorship.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md new file mode 100644 index 0000000000000..2b155ba87ac5c --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md @@ -0,0 +1,11 @@ +--- +title: Patrocinar a colaboradores de código abierto +intro: 'Puedes patrocinar colaboradores, recibir actualizaciones sobre los programadores y las organizaciones que patrocinas, y mostrar una insignia de patrocinador en todo {% data variables.product.product_name %}.' +mapTopic: verdadero +redirect_from: + - /articles/sponsoring-open-source-developers + - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md new file mode 100644 index 0000000000000..c7f2bf2e9ad1e --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md @@ -0,0 +1,21 @@ +--- +title: Información de facturación para los Patrocinadores de GitHub +intro: 'Los desarrolladores y organizaciones patrocinados deben emitir su información fiscal a {% data variables.product.prodname_dotcom %} y son responsables de evaluar y pagar sus propios impuestos.' +redirect_from: + - /articles/tax-information-for-sponsored-developers + - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers +versions: + free-pro-team: '*' +--- + +Si eres contribuyente en los Estados Unidos, debes enviar un W-9 antes de poder recibir pagos. Si eres un contribuyente en cualquier otra región de los Estados Unidos, deberás emitir un W-8BEN antes de que puedas recibir pagos. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)". {% data variables.product.prodname_dotcom %}te enviará los formatos adecuados, te notificará cuando vayan a expirar, y te dará una cantidad razonable de tiempo para completarlos y enviarlos. + +Si eres contribuyente en los Estados Unidos y ganas más de $600 en un año fiscal, {% data variables.product.prodname_dotcom %} te enviará un 1099 antes del 31 de enero del siguiente año calendario. No proporcionamos formularios fiscales para los contribuyentes internacionales. + +{% data variables.product.prodname_dotcom %} no retiene impuestos de {% data variables.product.prodname_sponsors %} pagos. Los programadores patrocinados son responsables de estimar y pagar sus propios impuestos. + +{% data reusables.sponsors.sponsorships-not-tax-deductible %} + +### Further reading + +- [Ver tus patrocinadores y patrocinios](/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md new file mode 100644 index 0000000000000..3bd17927c7d6b --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -0,0 +1,31 @@ +--- +title: Ver tus patrocinadores y patrocinios +intro: Puedes ver y exportar la información detallada y la analítica de tus patrocinadores y patrocinios. +redirect_from: + - /articles/viewing-your-sponsors-and-sponsorships +versions: + free-pro-team: '*' +--- + +### Acerca de los patrocinadores y los patrocinios + +Puedes ver la analítica de tus patrocinios actuales y pasados, los pagos que has recibido de tus patrocinadores, y los eventos tales como las cancelaciones y cambios de nivel de patrocinio para tus patrocinios. También puedes ver la actividad tal como los nuevos patrocinios, cambios, y cancelaciones de los mismos. Puedes filtrar la lista de actividades por fecha. También puedes exportar datos del patrocinio en formato CSV o JSON para la cuenta que estás viendo. + +### Ver tus patrocinadores y patrocinios + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +1. Como alternativa, para filtrar los patrocinadores por nivel, utiliza el menú desplegable de **Filter** (Filtro), haz clic en **Active tiers** (Niveles activos) o **Retired tiers** (Niveles retirados) y selecciona un nivel. ![Menú desplegable para filtrar por nivel](/assets/images/help/sponsors/filter-drop-down.png) + +### Visualizar la actividad de patrocinio reciente + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.activity-tab %} + +### Exportar tus datos de patrocinio + +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. Después de que se complete la exportación, puedes exportar otor mes de datos. Puedes exportar hasta 10 conjuntos de datos por hora para cualquiera de tus cuentas patrocinadas. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Botón de exportar](/assets/images/help/sponsors/export-all.png) +1. Elige un formato y periodo de tiempo para los datos que quieres exportar. Posteriormente, da clic en **Comenzar exportación**. ![Opciones para exportar datos](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md new file mode 100644 index 0000000000000..69bb4e996f73a --- /dev/null +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md @@ -0,0 +1,35 @@ +--- +title: Acerca del uso de tus datos de GitHub +redirect_from: + - /articles/about-github-s-use-of-your-data + - /articles/about-githubs-use-of-your-data +intro: '{% data variables.product.product_name %} usa los datos de tu repositorio para conectarte con información, proyectos, personas y herramientas relevantes.' +versions: + free-pro-team: '*' +--- + +### Acerca del uso de tus datos de {% data variables.product.product_name %} + +{% data variables.product.product_name %} agrega metadatos y analiza patrones de contenidos con el fin de suministrar información generalizada dentro del producto. Usa datos de los repositorios públicos y también usa metadatos y agrega datos de repositorios privados cuando el propietario de un repositorio ha elegido compartir los datos con {% data variables.product.product_name %} mediante una opción. Si aceptas el uso de datos de un repositorio privado, entonces se realizará un análisis de solo lectura de ese repositorio privado específico. + +{% data reusables.repositories.about-github-archive-program %} Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". + +{% data reusables.user_settings.export-data %} Para obtener más información, consulta "[Solicitar un archivo de los datos de tu cuenta personal](/articles/requesting-an-archive-of-your-personal-account-s-data)". + +Si decides utilizar datos para un repositorio privado, seguiremos tratando tus datos privados, código abierto, o secretos comerciales como confidenciales y privados de acuerdo con nuestras [Condiciones de Servicio](/articles/github-terms-of-service/). La información que obtenemos viene solo de los datos agregados. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". + +Anunciaremos nuevas funciones sustanciales que usen metadatos o datos agregados en el [{% data variables.product.prodname_dotcom %}blog](https://github.com/blog). + +### Cómo mejoran los datos las recomendaciones de seguridad + +Como ejemplo de cómo deberían usarse tus datos, podemos detectar y alertarte sobre una vulnerabilidad de seguridad en las dependencias de tu repositorio público. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +Para detectar posibles vulnerabilidades de seguridad {% data variables.product.product_name %} escanea los contenidos del archivo de manifiesto de dependencias para hacer una lista de las dependencias de tu proyecto. + +{% data variables.product.product_name %} también aprende de los cambios que realizas en tu manifiesto de dependencias. Por ejemplo, si actualizas una dependencia vulnerable a una versión segura después de recibir una alerta de seguridad y otros hacen lo mismo, {% data variables.product.product_name %} aprende cómo hacer un parche en la vulnerabiidad y puede recomendar un parche similar para el repositorio afectado. + +### Privacidad y uso compartido de datos + +Los datos del repositorio privado se escanean mediante una máquina y nunca es leído por el personal de {% data variables.product.product_name %}. El ojo humano nunca verá los contenidos de tus repositorios privados, a excepción de lo que se describe en nuestros [Términos de servicio](/articles/github-terms-of-service/#3-access). + +Tus datos personales individuales o del repositorio no se compartirán con terceros. Podemos compartir datos agregados obtenidos de nuestro análisis con nuestros socios. diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/index.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/index.md new file mode 100644 index 0000000000000..4d6c2b9e1aa75 --- /dev/null +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/index.md @@ -0,0 +1,15 @@ +--- +title: Comprender cómo GitHub usa y protege tus datos +redirect_from: + - /categories/understanding-how-github-uses-and-protects-your-data +versions: + free-pro-team: '*' +--- + + +### Índice + +{% link_in_list /about-githubs-use-of-your-data %} +{% link_in_list /requesting-an-archive-of-your-personal-accounts-data %} +{% link_in_list /managing-data-use-settings-for-your-private-repository %} +{% link_in_list /opting-into-or-out-of-the-github-archive-program-for-your-public-repository %} diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md new file mode 100644 index 0000000000000..decb95e352dfb --- /dev/null +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -0,0 +1,30 @@ +--- +title: Administrar la configuración de uso de datos para tu repositorio privado +intro: 'Para ayudar a que {% data variables.product.product_name %} te conecte a las herramientas, proyectos, personas e información relevantes, puedes configurar el uso de datos para tu repositorio privado.' +redirect_from: + - /articles/opting-into-or-out-of-data-use-for-your-private-repository + - /github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository +versions: + free-pro-team: '*' +--- + +### Acerca del uso de datos para tu repositorio privado + +Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a la gráfica de dependencias, en donde puedes rastrear las dependencias de tus repositorios y recibir las {% data variables.product.prodname_dependabot_alerts %} cuando {% data variables.product.product_name %} detecte las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". + +### Habilitar o inhabilitar las características para el uso de datos + +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} + +{% data reusables.security.security-and-analysis-features-enable-read-only %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + +### Further reading + +- "[Acerca del uso de tus datos de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)" +- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md new file mode 100644 index 0000000000000..285c8a230257b --- /dev/null +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md @@ -0,0 +1,18 @@ +--- +title: Aceptar o rechazar el ingreso al Prgrama de GitHub Archive para tu repositorio público +intro: 'Puedes gestionar si {% data variables.product.prodname_dotcom %} incluye tu repositorio público en el {% data variables.product.prodname_archive %} para ayudarte a garantizar la preservación a largo plazo del código abierto global.' +permissions: 'Las personas con permisos administrativos a un repositorio público puede acepar o rechazar el ingreso al {% data variables.product.prodname_archive %}.' +versions: + free-pro-team: '*' +--- + +{% data reusables.repositories.about-github-archive-program %} Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". + +Si rechazas el ingreso de un repositorio al {% data variables.product.prodname_archive %}, éste se excluirá de cualquier archivo a largo plazo que {% data variables.product.prodname_dotcom %} pudiera crear posteriormente. También enviaremos una solicitud a cada una de nuestras organizaciones socias para eliminar el repositorio de sus datos. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "Características", selecciona o deselecciona **Preservar este repositorio**. ![Casilla para permitir a {% data variables.product.prodname_dotcom %} incluir tu código en el {% data variables.product.prodname_archive %}](/assets/images/help/repository/github-archive-program-checkbox.png) + +### Further reading +- [{% data variables.product.prodname_archive %} Preguntas Frecuentes](https://archiveprogram.github.com/faq/) diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md new file mode 100644 index 0000000000000..bbf2ae9116190 --- /dev/null +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md @@ -0,0 +1,36 @@ +--- +title: Solicitar un archivo de tus datos de cuenta personal +redirect_from: + - /articles/requesting-an-archive-of-your-personal-account-s-data + - /articles/requesting-an-archive-of-your-personal-accounts-data +intro: '{% data reusables.user_settings.export-data %}' +versions: + free-pro-team: '*' +--- + +{% data variables.product.product_name %} almacena metadatos del repositorio y del perfil desde tu actividad de cuenta personal. Puedes exportar tus datos de cuenta personal a través de los parámetros {% data variables.product.prodname_dotcom_the_website %} o con la API de migración de usuarios. + +Para obtener más información, acerca de los datos que almacena {% data variables.product.product_name %} y que está disponible para exportarse, consulta las secciones "[Descargar el archivo de migración de un usuario](/rest/reference/migrations#download-a-user-migration-archive)" y "[Acerca del uso de {% data variables.product.product_name %} para tus datos](/articles/about-github-s-use-of-your-data). + +Cuando solicites una exportación de tus datos personales a través de los parámetros de {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.product_name %} comprime tus datos personales en un archivo `tar.gz` y te envía un correo electrónico a tu dirección principal de correo electrónico con un enlace de descarga. + +Por defecto, el enlace de descarga vence después de siete días. En cualquier momento previo a que venza el enlace de descarga, puedes habilitar el enlace desde los parámetros del usuario. Para obtener más información, consulta "[Eliminar el acceso a un archivo de datos de tu cuenta personal](/articles/requesting-an-archive-of-your-personal-account-s-data/#deleting-access-to-an-archive-of-your-personal-accounts-data)". + +Si tu sistema operativo no puede descomprimir el archivo `tar.gz` de forma nativa, puedes utilizar una herramienta de terceros para extraer los archivos archivados. Para obtener más información, consulta "[Cómo descomprimir un tar.gz file](https://opensource.com/article/17/7/how-unzip-targz-file)" en Opensource.com. + +El archivo `tar.gz` generado refleja los datos almacenados en el momento que comenzaste la exportación de datos. + +### Descargar un archivo de datos de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.account_settings %} +3. En "Export account data" (Exportar datos de cuenta), haz clic en **Start export** (Comenzar exportación) o **New export** (Nueva exportación). ![Botón Start personal data export (Comenzar exportación de datos personales) resaltado](/assets/images/help/repository/export-personal-data.png) ![Botón New personal data export (Nueva exportación de datos personales) resaltado](/assets/images/help/repository/new-export.png) +4. Una vez que la exportación esté lista para descargar, {% data variables.product.product_name %} te enviará un enlace de descarga a tu dirección principal de correo electrónico. +5. Haz clic en el enlace de descarga de tu correo electrónico y vuelve a ingresar tu contraseña, si se te solicita. +6. Serás redirigido a un archivo `tar.gz` que podrás descargar. + +### Eliminar acceso a un archivo de datos de tu cuenta personal + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.account_settings %} +3. Para inhabilitar el enlace de descarga que se te envió al correo electrónico antes de que venza, en "Export account data" (Exportar datos de cuenta), encuentra la descarga de exportación de datos que quieres inhabilitar y haz clic en **Delete** (Eliminar). ![Botón Delete personal data export package (Eliminar paquete de exportación de datos personales) resaltado](/assets/images/help/repository/delete-export-personal-account-data.png) diff --git a/translations/es-ES/content/github/using-git/about-git-rebase.md b/translations/es-ES/content/github/using-git/about-git-rebase.md new file mode 100644 index 0000000000000..333a436305ef4 --- /dev/null +++ b/translations/es-ES/content/github/using-git/about-git-rebase.md @@ -0,0 +1,110 @@ +--- +title: Acerca del cambio de base de Git +redirect_from: + - /rebase/ + - articles/interactive-rebase/ + - /articles/about-git-rebase +intro: 'El comando `git rebase` te permite cambiar fácilmente una serie de confirmaciones, modificando el historial de tu repositorio. Puedes reordenar, editar o combinar confirmaciones.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Generalmente, usarás `git rebase` para: + +* Editar mensajes de confirmación previos. +* Combinar varias confirmaciones en una. +* Eliminar o revertir confirmaciones que ya no son necesarias. + +{% warning %} + +**Advertencia**: Como cambiar el historial de tu confirmación puede hacer las cosas difíciles para todos los que usan el repositorio, se considera una mala práctica cambiar de base las confirmaciones cuando ya las subiste a un repositorio. Para aprender cómo cambiar de base de forma segura en {% data variables.product.product_location %}, consulta "[Acerca de las fusiones de solicitud de extracción](/articles/about-pull-request-merges)". + +{% endwarning %} + +### Cambiar de base las confirmaciones con una rama + +Para cambiar de base todas las confirmaciones entre otra rama y el estado de rama actual, puedes ingresar el siguiente comando en tu shell (ya sea el símbolo del sistema para Windows o la terminal para Mac y Linux): + +```shell +$ git rebase --interactive other_branch_name +``` + +### Cambiar de base las confirmaciones en un momento específico + +Para cambiar de base las últimas confirmaciones en tu rama actual, puedes ingresar el siguiente comando en tu shell: + +```shell +$ git rebase --interactive HEAD~7 +``` + +### Comandos disponibles mientras se cambia de base + +Hay seis comandos disponibles mientras se cambia la base: + +
+
pick
+
pick simplemente significa que la confirmación está incluida. Reordenar los comandos pick cambia el orden de las confirmaciones cuando el cambio de base está en progreso. Si eliges no incluir una confirmación, debes eliminar la línea completa.
+ +
reword
+
El comando reword es similar a pick, pero después de usarlo, el proceso de cambio de base se pausará y te dará una oportunidad de alterar el mensaje de confirmación. Cualquier cambio hecho por la confirmación no se ve afectado.
+ +
editar
+
Si eliges edit una confirmación, se te dará la oportunidad de modificar la confirmación, lo que significa que puedes agregar o cambiar la confirmación por completo. También puedes realizar más confirmaciones antes de continuar con el cambio de base. Esto te permite dividir una confirmación grande en otras más pequeñas o eliminar cambios erróneos hechos en una confirmación.
+ +
squash
+
Este comando te permite combinar dos o más confirmaciones en una única confirmación. Una confirmación se combina en la confirmación de arriba. Git te da la oportunidad de escribir un mensaje de confirmación nuevo describiendo ambos cambios.
+ +
fixup
+
Esto es similar a squash, pero se descarta el mensaje de la confirmación que se fusiona. La confirmación simplemente se fusiona en la confirmación de arriba y el mensaje de la confirmación anterior se usa para describir ambos cambios.
+ +
exec
+
Esto te permite ejecutar comandos shell de forma arbitraria con una confirmación.
+
+ +### Un ejemplo del uso de `git rebase` + +Sin importar qué comando uses, Git iniciará [tu editor de texto predeterminado](/articles/associating-text-editors-with-git) y abrirá un archivo que detalla las confirmaciones en el rango que has elegido. Ese archivo se ve así: + +``` +pick 1fc6c95 Patch A +pick 6b2481b Patch B +pick dd1475d something I want to split +pick c619268 A fix for Patch B +pick fa39187 something to add to patch A +pick 4ca2acc i cant' typ goods +pick 7b36971 something to move before patch B + +# Cambiar de base 41a72e6..7b36971 a 41a72e6 +# +# Commandos: +# p, pick = usar la confirmación +# r, reword = usar la confirmación, pero editar el mensaje de confirmación +# e, edit = usar la confirmación, pero detenerse para correcciones +# s, squash = usar la confirmación, pero unirla con la confirmación anterior +# f, fixup = como "squash", pero descartar el mensaje de registro de esta confirmación +# x, exec = ejecutar comando (el resto de la línea) usando shell +# +# Si eliminas una línea aquí, ESA CONFIRMACIÓN SE PERDERÁ. +# Sin embargo, si eliminas todo, este cambio de base será interrumpido. +# +``` + +Desglosando esta información, de principio a fin, vemos que: + +- Se enumeran siete confirmaciones, lo que indica que hubo siete cambios entre nuestro punto de partida y el estado de nuestra rama actual. +- Las confirmaciones que eliges cambiar de base se clasifican en el orden de los cambios más antiguos (arriba) a los cambios más nuevos (abajo). +- Cada línea detalla un comando (por defecto, `pick`), la confirmación SHA y el mensaje de confirmación. Todo el procedimiento `git rebase` se centra en tu manipulación de estas tres columnas. The changes you make are *rebased* onto your repository. +- Después de las confirmaciones, Git te dice el rango de confirmaciones con las que estamos trabajando (`41a72e6..7b36971`). +- Finalmente, Git te ayuda diciéndote los comandos que están disponibles para ti cuando cambias de base las confirmaciones. + +### Further reading + +- "[Usar Git rebase](/articles/using-git-rebase)" +- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing) +- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) +- "[Combinar confirmaciones con cambio de base](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" +- "[Sincronizar tu rama](/desktop/contributing-to-projects/syncing-your-branch)" en la documentación de {% data variables.product.prodname_desktop %} diff --git a/translations/es-ES/content/github/using-git/about-git-subtree-merges.md b/translations/es-ES/content/github/using-git/about-git-subtree-merges.md new file mode 100644 index 0000000000000..419ad7bc714bb --- /dev/null +++ b/translations/es-ES/content/github/using-git/about-git-subtree-merges.md @@ -0,0 +1,109 @@ +--- +title: Acerca de las fusiones de subárbol de Git +redirect_from: + - /articles/working-with-subtree-merge/ + - /subtree-merge/ + - /articles/about-git-subtree-merges +intro: 'Si necesitas gestionar múltiples proyectos dentro de un solo repositorio, puedes usar una "fusión de subárbol" para manejar todas las referencias.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Habitualmente, una fusión de subárbol se usa para contener un repositorio dentro de otro repositorio. El "subrepositorio" se almacena en una carpeta del repositorio principal. + +La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Haremos lo siguiente: + +- Crear un repositorio vacío llamado `test` que represente nuestro proyecto. +- Fusionar otro repositorio en él como un subárbol llamado `Spoon-Knife`. +- El proyecto `test` usará ese subproyecto como si fuera parte del mismo repositorio. +- Recuperar actualizaciones desde `Spoon-Knife` hacia el proyecto `test`. + +### Configurar el repositorio vacío para una fusión de subárbol + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Crear un directorio nuevo y navegar a él. + ```shell + $ mkdir test + $ cd test + ``` +3. Inicializar un repositorio de Git nuevo. + ```shell + $ git init + > Initialized empty Git repository in /Users/octocat/tmp/test/.git/ + ``` +4. Crear y confirmar un archivo nuevo. + ```shell + $ touch .gitignore + $ git add .gitignore + $ git commit -m "initial commit" + > [main (root-commit) 3146c2a] initial commit + > 0 files changed, 0 insertions(+), 0 deletions(-) + > create mode 100644 .gitignore + ``` + +### Agregar un nuevo repositorio como subárbol + +1. Agregar una URL remota nueva que apunte a un proyecto por separado en el que estemos interesados. + ```shell + $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git + > Updating spoon-knife + > warning: no common commits + > remote: Counting objects: 1732, done. + > remote: Compressing objects: 100% (750/750), done. + > remote: Total 1732 (delta 1086), reused 1558 (delta 967) + > Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done. + > Resolving deltas: 100% (1086/1086), done. + > From git://github.com/octocat/Spoon-Knife + > * [new branch] main -> Spoon-Knife/main + ``` +2. Fusionar el proyecto `Spoon-Knife` en el proyecto de Git local. Esto no modifica ninguno de tus archivos localmente, pero prepara Git para el siguiente paso. + + Si estás usando Git 2.9 o superior: + ```shell + $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main + > Automatic merge went well; stopped before committing as requested + ``` + + Si estás usando Git 2.8 o inferior: + ```shell + $ git merge -s ours --no-commit spoon-knife/main + > Automatic merge went well; stopped before committing as requested + ``` +3. Crear un nuevo directorio denominado **spoon-knife**, y copiar el historial de Git del proyecto `Spoon-Knife` en él. + ```shell + $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main + ``` +4. Confirmar los cambios para mantenerlos seguros. + ```shell + $ git commit -m "Subtree merged in spoon-knife" + > [main fe0ca25] Subtree merged in spoon-knife + ``` + +Aunque solo hemos agregado un subproyecto, se puede incorporar cualquier número de subproyectos en un repositorio de Git. + +{% tip %} + +**Sugerencia**: Si creas un clon nuevo del repositorio en el futuro, no se crearán los remotos que agregaste. Deberás volver a agregarlos mediante [el comando `git remote add`](/articles/adding-a-remote). + +{% endtip %} + +### Sincronizando con actualizaciones y cambios + +Cuando se agrega un subproyecto, no se mantiene sincronizado automáticamente con los cambios ascendentes. Necesitarás actualizar el subproyecto con el siguiente comando: + +```shell +$ git pull -s subtree remotename branchname +``` + +Para el ejemplo de más arriba, esto sería: + +```shell +$ git pull -s subtree spoon-knife main +``` + +### Further reading + +- [El capítulo de "Fusión Avanzada" del libro de _Pro Git_](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) +- "[Cómo usar la estrategia de fusión de subárbol](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/es-ES/content/github/using-git/about-remote-repositories.md b/translations/es-ES/content/github/using-git/about-remote-repositories.md new file mode 100644 index 0000000000000..51255ba42385e --- /dev/null +++ b/translations/es-ES/content/github/using-git/about-remote-repositories.md @@ -0,0 +1,35 @@ +--- +title: Acerca de los repositorios remotos +redirect_from: + - /articles/working-when-github-goes-down/ + - /articles/sharing-repositories-without-github/ + - /articles/about-remote-repositories +intro: 'El enfoque colaborador de GitHub para el desarrollo depende en publicar confirmaciones de cambios desde tu repositorio local para que otras personas lo vean, lo extraigan y lo actualicen.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Una URL remota es la manera de Git de decir "el lugar donde se almacena tu código". Esa URL podría ser tu repositorio en GitHub o la bifurcación de otro usuario o incluso en un servidor completamente diferente. + +Solo puedes subir a dos tipos de direcciones URL: + +* Una URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git` +* Una URL SSH como `git@{% data variables.command_line.backticks %}:user/repo.git` + +Git asocia una URL remota con un nombre y tu remoto predeterminado generalmente se llama `origen`. + +Para obtener información sobre las diferencias entre estas URL, consulta "[¿Qué URL remota debo usar?](/articles/which-remote-url-should-i-use)" + +### Crear remotos + +Puedes usar el comando `git remote add` para hacer coincidir una URL remota con un nombre. Por ejemplo, escribirás lo siguiente en la línea de comandos: + +```shell +git remote add origin <REMOTE_URL> +``` + +Esto asocia el nombre `origin` con `REMOTE_URL`. + +Puedes usar el comando `git remote set-url` para [cambiar la URL de un remoto](/articles/changing-a-remote-s-url). diff --git a/translations/es-ES/content/github/using-git/adding-a-remote.md b/translations/es-ES/content/github/using-git/adding-a-remote.md new file mode 100644 index 0000000000000..0a2df5c632773 --- /dev/null +++ b/translations/es-ES/content/github/using-git/adding-a-remote.md @@ -0,0 +1,52 @@ +--- +title: Agregar un remoto +intro: 'Para agregar un remoto nuevo, usa el comando `git remote add` en el terminal, dentro del directorio donde está almacenado tu repositorio.' +redirect_from: + - /articles/adding-a-remote +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El comando `git remote add` toma dos argumentos: + +* Un nombre remoto, por ejemplo, `origin` +* Una URL remota, por ejemplo, `https://{% data variables.command_line.backticks %}/user/repo.git` + +Por ejemplo: + +```shell +$ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git +# Set a new remote + +$ git remote -v +# Verify new remote +> origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/user/repo.git (push) +``` + +¿No estás seguro de que URL usar? Examina "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" + +### Solución de problemas + +Puedes encontrar estos errores al tratar de agregar un remoto. + +#### El `nombre` remoto ya existe + +Este error significa que trataste de agregar un remoto con un nombre que ya existe en tu repositorio local: + +```shell +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git +> fatal: remote origin already exists. +``` + +Para arreglar esto, puedes + +* Usar un nombre diferente para el nuevo remoto +* [Renombrar el remoto existente](/articles/renaming-a-remote) +* [Eliminar el remoto existente](/articles/removing-a-remote) + +### Further reading + +- "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/associating-text-editors-with-git.md b/translations/es-ES/content/github/using-git/associating-text-editors-with-git.md new file mode 100644 index 0000000000000..5099c55d4f9ae --- /dev/null +++ b/translations/es-ES/content/github/using-git/associating-text-editors-with-git.md @@ -0,0 +1,122 @@ +--- +title: Asociar editores de texto con Git +intro: Usar un editor de texto para abrir y editar tus archivos con Git. +redirect_from: + - /textmate/ + - /articles/using-textmate-as-your-default-editor/ + - /articles/using-sublime-text-2-as-your-default-editor/ + - /articles/associating-text-editors-with-git +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% mac %} + +### Usar Atom como editor + +1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "atom --wait" + ``` + +### Utilizar Visual Studio Code como tu editor + +1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "code --wait" + ``` + +### Usar Sublime Text como tu editor + +1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "subl -n -w" + ``` + +### Usar TextMate como editor + +1. Instala [TextMate](https://macromates.com/). +2. Instala la utilidad de shell `mate` de TextMate. Para obtener más información, consulta "[mate y rmate](https://macromates.com/blog/2011/mate-and-rmate/)" en la documentación de TextMate. +{% data reusables.command_line.open_the_multi_os_terminal %} +4. Escribe este comando: + ```shell + $ git config --global core.editor "mate -w" + ``` +{% endmac %} + +{% windows %} + +### Usar Atom como editor + +1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +3. Escribe este comando: + ```shell + $ git config --global core.editor "atom --wait" + ``` + +### Utilizar Visual Studio Code como tu editor + +1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "code --wait" + ``` + +### Usar Sublime Text como tu editor + +1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w" + ``` + +### Usar Notepad++ como editor + +1. Instala Notepad++ desde https://notepad-plus-plus.org/. Para obtener más información, consulta la sección "[Comenzar](https://npp-user-manual.org/docs/getting-started/)" en la documentación de Notepad++. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" + ``` +{% endwindows %} + +{% linux %} + +### Usar Atom como editor + +1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "atom --wait" + ``` + +### Utilizar Visual Studio Code como tu editor + +1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "code --wait" + ``` + +### Usar Sublime Text como tu editor + +1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Escribe este comando: + ```shell + $ git config --global core.editor "subl -n -w" + ``` + +{% endlinux %} diff --git a/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md b/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md new file mode 100644 index 0000000000000..4156e631b47ab --- /dev/null +++ b/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md @@ -0,0 +1,102 @@ +--- +title: Almacenar tus credenciales de GitHub en el caché dentro de Git +redirect_from: + - /firewalls-and-proxies/ + - /articles/caching-your-github-password-in-git + - /github/using-git/caching-your-github-password-in-git +intro: 'Si estás [clonando los repositorios de {% data variables.product.product_name %} mediante HTTPS](/github/using-git/which-remote-url-should-i-use), puedes utilizar un asistente de credenciales para decirle a Git que recuerde tus credenciales.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si clonas repositorios de {% data variables.product.product_name %} mediante SSH, entonces te autenticas utilizando una llave SSH en vez de utilizar otras credenciales. Para obtener información acerca de cómo configurar una conexión SSH, consulta la sección "[Generar una llave SSH](/articles/generating-an-ssh-key)". + +{% mac %} + +{% tip %} + +**Tips:** + +- Debes tener Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales osxkeychain. +- Si has instalado Git mediante [Homebrew](http://brew.sh/), el `osxkeychain helper` debe estar instalado anteriormente. +- Si estás utilizando Mac OS X10.7 o superior y tienes instalado Git a través de las herramientas de la línea de comando Xcode de Apple, luego `osxkeychain helper` se incluirá automáticamente en tu instalación Git. + +{% endtip %} + +Instala Git y `osxkeychain helper` e informa a Git que lo use. + +1. Descubre si Git y `osxkeychain helper` ya están instalados: + ```shell + $ git credential-osxkeychain + # Test for the cred helper + > Usage: git credential-osxkeychain <get|store|erase> + ``` +2. Si el asistente `osxkeychain helper` no está instalado, y estás utilizando OS X versión 10.9 o superior, tu computadora te pedirá que lo descargues como parte de las Herramientas de la línea de comandos de Xcode: + ```shell + $ git credential-osxkeychain + > xcode-select: note: no developer tools were found at '/Applications/Xcode.app', + > requesting install. Choose an option in the dialog to download the command line developer tools. + ``` + + Como opción, puedes instalar Git y el asistente `osxkeychain helper` usando [Homebrew](http://brew.sh/): + ```shell + $ brew install git + ``` + +4. Pídele a Git que use el asistente `osxkeychain helper` con la configuración global `credential.helper`: + ```shell + $ git config --global credential.helper osxkeychain + # Set git to use the osxkeychain credential helper + ``` + +La próxima vez que clones una URL de HTTPS que requiera autenticación, Git te pedirá tu nombre de usuario y contraseña. {% data reusables.user_settings.password-authentication-deprecation %} + +Ya que te hayas autenticado exitosamente, tus credenciales se almacenarán en el llavero de macOS y se utilizarán cada que clones una URL con HTTPS. No se te solicitará teclear tus credenciales en Git nuevamente a menos de que éstas cambien. + +{% endmac %} + +{% windows %} + +{% tip %} + +**Sugerencia:** Necesitarás Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales. + +{% endtip %} + +También puedes instalar un shell Git nativo, como [Git para Windows](https://git-for-windows.github.io/). Con Git para Windows, al ejecutar lo siguiente en la línea de comandos, se almacenarán tus credenciales: + +```shell +$ git config --global credential.helper wincred +``` + +{% endwindows %} + +{% linux %} + +{% tip %} + +**Sugerencia:** Necesitarás Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales. + +{% endtip %} + +Activa tu ayudante de credenciales de manera que Git guarde tu contraseña en la memoria para otra oportunidad. Por defecto, Git guardará en la memoria caché tu contraseña durante 15 minutos. + +1. En Terminal, escribe lo siguiente: + ```shell + $ git config --global credential.helper cache + # Set git to use the credential memory cache + ``` +2. Para cambiar el intervalo por defecto de la memoria caché de la contraseña, escribe lo siguiente: + ```shell + $ git config --global credential.helper 'cache --timeout=3600' + # Set the cache to timeout after 1 hour (setting is in seconds) + ``` + +{% endlinux %} + +### Further reading + +- "[Actualizar credenciales desde la Keychain OSX](/articles/updating-credentials-from-the-osx-keychain/)" +- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-ES/content/github/using-git/changing-a-remotes-url.md b/translations/es-ES/content/github/using-git/changing-a-remotes-url.md new file mode 100644 index 0000000000000..2a7d5ee07facc --- /dev/null +++ b/translations/es-ES/content/github/using-git/changing-a-remotes-url.md @@ -0,0 +1,97 @@ +--- +title: Cambiar la URL de un remoto +redirect_from: + - /articles/changing-a-remote-s-url + - /articles/changing-a-remotes-url +intro: El comando `git remote set-url` cambia una URL del repositorio remoto existente. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% tip %} + +**Sugerencia:** Para obtener información sobre la diferencia entre las URL HTTPS y SSH consulta "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" + +{% endtip %} + +El comando `git remote set-url` toma dos argumentos: + +* Un nombre de remoto existente. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes. +* Una nueva URL para el remoto. Por ejemplo: + * Si estás actualizando para usar HTTPS, tu URL puede verse como: +```shell +https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git +``` + * Si estás actualizando para usar SSH, tu URL puede verse como: +```shell +git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git +``` + +### Cambiar direcciones URL remotas de SSH a HTTPS + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambiar el directorio de trabajo actual en tu proyecto local. +3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar. + ```shell + $ git remote -v + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + ``` +4. Cambiar tu URL remota de SSH a HTTPS con el comando `git remote set-url`. + ```shell + $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git + ``` +5. Verificar que la URL remota ha cambiado. + ```shell + $ git remote -v + # Verify new remote URL + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + ``` + +La próxima vez que ejecutes `git`, `git pull` o `git push` en el repositorio remoto, se te pedirá el nombre de usuario y la contraseña de GitHub. {% data reusables.user_settings.password-authentication-deprecation %} + +Puedes [utilizar un ayudante de credenciales](/github/using-git/caching-your-github-credentials-in-git) para que Git recuerde tu nombre de usuario y token de acceso personal cada vez que se comunique con GitHub. + +### Cambiar las URL remotas de HTTPS a SSH + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambiar el directorio de trabajo actual en tu proyecto local. +3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + ``` +4. Cambiar tu URL remota de HTTPS a SSH con el comando `git remote set-url`. + ```shell + $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git + ``` +5. Verificar que la URL remota ha cambiado. + ```shell + $ git remote -v + # Verify new remote URL + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + ``` + +### Solución de problemas + +Puedes encontrar estos errores cuando intentes cambiar un remoto. + +#### No existe tal remoto '[name]' + +Este error significa que el remoto que trataste de cambiar no existe: + +```shell +$ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +> fatal: No such remote 'sofake' +``` + +Comprueba que escribiste correctamente el nombre del remoto. + +### Further reading + +- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md new file mode 100644 index 0000000000000..abad70e410542 --- /dev/null +++ b/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md @@ -0,0 +1,130 @@ +--- +title: Configurar Git para manejar finales de línea +intro: 'Para evitar problemas en tus diferencias, puedes configurar Git para manejar correctamente los finales de línea.' +redirect_from: + - /dealing-with-lineendings/ + - /line-endings/ + - /articles/dealing-with-line-endings/ + - /articles/configuring-git-to-handle-line-endings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cada vez que presionas Enter en tu teclado, insertas un caracter invisible denominado fin de línea. Esto se maneja de forma diferente en los diferentes sistemas operativos. + +Cuando colaboras en proyectos con Git y {% data variables.product.product_name %}, Git puede producir resultados inesperados si, por ejemplo, trabajas en una máquina Windows y tu colaborador hizo un cambio desde OS X. + +Puedes configurar Git para que maneje los fines de línea automáticamente y así puedas colaborar eficazmente con las personas que utilizan otros sistemas operativos. + +### Parámetros globales para finales de línea + +El comando `git config core.autocrlf` se usa para cambiar el modo en que Git maneja los finales de línea. Toma un solo argumento. + +{% mac %} + +En OS X, simplemente escribes `input` en la configuración. Por ejemplo: + +```shell +$ git config --global core.autocrlf input +# Configure Git to ensure line endings in files you checkout are correct for OS X +``` + +{% endmac %} + +{% windows %} + +En Windows, simplemente escribes `true` en la configuración. Por ejemplo: + +```shell +$ git config --global core.autocrlf true +# Configure Git to ensure line endings in files you checkout are correct for Windows. +# For compatibility, line endings are converted to Unix style when you commit files. +``` + +{% endwindows %} + +{% linux %} + +En Linux, simplemente escribes `input` en la configuración. Por ejemplo: + +```shell +$ git config --global core.autocrlf input +# Configure Git to ensure line endings in files you checkout are correct for Linux +``` + +{% endlinux %} + +### Parámetros por repositorio + +Como ocpión, puedes configurar un archivo de tipo *.gitattributes* para administrar cómo Git lee los fines de línea en un repositorio específico. Cuando confirmas este archivo en un repositorio, éste invalida la configuración de `core.autocrlf` para todos los colaboradores del mismo. Esto garantiza un comportamiento consistente para todos los usuarios, sin importar su configuración y ambiente de Git. + +El archivo *.gitattributes* debe crearse en la raíz del repositorio y confirmarse como cualquier otro archivo. + +Un archivo *.gitattributes* se asemeja a una tabla con dos columnas: + +* A la izquierda está el nombre del archivo que coincide con Git. +* A la derecha está la configuración de fin de línea que Git debería usar para esos archivos. + +#### Ejemplo + +Aquí hay un ejemplo de archivo *.gitattributes*. Puedes usarlo como plantilla para tus repositorios: + +``` +# Esteblece el comportamiento predeterminado, en caso de que las personas no tengan configurado core.autocrlf. +* text=auto + +# Declara explícitamente los archivos de texto que siempre quieres que estén normalizados y convertidos +# a finales de línea nativos en el control. +*.c text +*.h text + +# Declara los archivos que siempre tendrán los finales de línea CRLF en el control. +*.sln text eol=crlf + +# Denota todos los archivos que son absolutamente binarios y no deberían modificarse. +*.png binary +*.jpg binary +``` + +Notarás que los archivos coinciden—`*.c`, `*.sln`, `*.png`—, separados con un espacio, y luego se les dará una configuración —`text`, `text eol=crlf`, `binary`. Revisaremos algunas configuraciones posibles a continuación. + +- `text=auto` Git manejará los archivos en cualquier manera que crea sea mejor. Esta es una buena opción predeterminada. + +- `text eol=crlf` Git siempre convertirá los fines de línea en `CRLF` a la salida. Deberías usar esto para los archivos que deben conservar los finales `CRLF`, incluso en OSX o Linux. + +- `text eol=lf` Git siempre convertirá los finales de línea en `LF` a la salida. Deberías usar esto para los archivos que deben conservar los finales LF, incluso en Windows. + +- `binary` Git entenderá que los archivos especificados no son de texto, y no deberá intentar cambiarlos. El parámetro `binario` también es un alias para `text -diff`. + +### Actualizar un repositorio después de los finales de línea + +Cuando configuras la opción `core.autocrlf` o confirmas un archivo de tipo *.gitattributes* podrías encontrar que Git reporta cambios a archivos que no has modificado. Git ha cambiado los fines de línea para que concuerden con tu nueva configuración. + +Para garantizar que todos los fines de línea en tu repositorio concuerdan con tu nueva configuración, respalda tus archivos con Git, borra los archivos en tu repositorio (con excepción de el directorio `.git`), y luego restablece todos los archivos al mismo tiempo. + +1. Guarda los archivos actuales en Git, de manera que nada de tu trabajo se pierda. + ```shell + $ git add . -u + $ git commit -m "Saving files before refreshing line endings" + ``` +2. Agrega todos los archivos cambiados nuevamente y normaliza los finales de línea. + ```shell + $ git add --renormalize . + ``` +3. Muestra los archivos reescritos, normalizados. + ```shell + $ git status + ``` +4. Confirma los cambios en tu repositorio. + ```shell + $ git commit -m "Normalize all the line endings" + ``` + +### Further reading + +- [Personalizar Git - Atributos de Git](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) en el libro de Pro Git +- [git-config](https://git-scm.com/docs/git-config) en las páginas man para Git +- [Comenzar -Configuración Inicial](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) en el libro de Pro Git +- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) por [Tim Clem](https://github.com/tclem) diff --git a/translations/es-ES/content/github/using-git/dealing-with-non-fast-forward-errors.md b/translations/es-ES/content/github/using-git/dealing-with-non-fast-forward-errors.md new file mode 100644 index 0000000000000..86ea034e7ed07 --- /dev/null +++ b/translations/es-ES/content/github/using-git/dealing-with-non-fast-forward-errors.md @@ -0,0 +1,38 @@ +--- +title: Tratamiento de errores sin avance rápido +intro: 'En ocasiones, Git no puede efectuar tu cambio en un repositorio remoto sin perder confirmaciones. Cuando esto sucede, los cambios que deseas subir se rechazan.' +redirect_from: + - /articles/dealing-with-non-fast-forward-errors +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si otra persona ha subido cambios en la misma rama que tú, Git no podrá subir tus cambios: + +```shell +$ git push origin main +> To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git +> ! [rejected] main -> main (non-fast-forward) +> error: failed to push some refs to 'https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git' +> To prevent you from losing history, non-fast-forward updates were rejected +> Merge the remote changes (e.g. 'git pull') before pushing again. See the +> 'Note about fast-forwards' section of 'git push --help' for details. +``` + +Puedes resolver este problema [extrayendo y fusionando](/articles/getting-changes-from-a-remote-repository) los cambios realizados en la rama remota con los cambios que has hecho localmente: + +```shell +$ git fetch origin +# Fetches updates made to an online repository +$ git merge origin YOUR_BRANCH_NAME +# Merges updates made online with your local work +``` + +O bien, puedes simplemente usar `git pull` para ejecutar al mismo tiempo ambos comandos: + +```shell +$ git pull origin YOUR_BRANCH_NAME +# Grabs online updates and merges them with your local work +``` diff --git a/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md b/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md new file mode 100644 index 0000000000000..3f9a975d01740 --- /dev/null +++ b/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md @@ -0,0 +1,75 @@ +--- +title: Obtener cambios de un repositorio remoto +intro: Puedes usar los comandos Git más frecuentes para acceder a repositorios remotos. +redirect_from: + - /articles/fetching-a-remote/ + - /articles/getting-changes-from-a-remote-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Estos comandos son muy útiles cuando interactúas con [un repositorio remoto](/articles/about-remote-repositories). `clone` y `fetch` descargan código remoto de la URL de un repositorio remoto en tu computadora local, `merge` se usa para fusionar el trabajo de diferentes personas con el tuyo, y `pull` es una combinación de `fetch` y `merge`. + +### Clonar un repositorio + +Para obtener una copia completa del repositorio de otro usuario, usa `git clone` de la siguientes manera: + +```shell +$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git +# Clona el repositorio en tu computadora +``` + +Puedes elegir entre [distintas URL](/articles/which-remote-url-should-i-use) cuando clonas un repositorio. Cuando inicias sesión en {% data variables.product.prodname_dotcom %}, estas URL están disponibles debajo de los detalles del repositorio: + +![Lista de URL remotas](/assets/images/help/repository/remotes-url.png) + +Cuando ejecutas `git clone`, se producen las siguientes acciones: +- Se forma una nueva carpeta llamada `repo`. +- Esta carpeta se inicializa como un repositorio de Git. +- Se crea un remoto llamado `origin` que apunta a la URL desde donde clonaste. +- Todos los archivos y confirmaciones del repositorio se descargan aquí. +- La rama predeterminada está desmarcada + +Para cada rama `foo` en el repositorio remoto, se crea la rama de seguimiento remoto correspondiente `refs/remotes/origin/foo` en tu repositorio local. Por lo general, puedes abreviar estos nombres de rama de seguimiento remoto como `origin/foo`. + +### Extraer cambios de un repositorio remoto + +Usa `git fetch` para recuperar trabajo nuevo realizado por otras personas. Extraer desde un repositorio permite obtener todas las etiquetas y ramas de seguimiento remoto *sin* fusionar estos cambios en tus propias ramas. + +Si ya tienes un repositorio local [con una URL remota](/articles/adding-a-remote) configurada para el proyecto deseado, puedes obtener toda la información nueva usando `git fetch *remotename*` en la terminal: + +```shell +$ git fetch remotename +# Extrae las actualizaciones realizadas en un repositorio remoto +``` + +Si no, siempre puedes [agregar un nuevo remoto](/articles/adding-a-remote) y luego extraer. + +### Fusionar cambios en tu rama local + +La fusión combina tus cambios locales con los cambios realizados por otros. + +Por lo general, fusionas una rama de seguimiento remoto (es decir, una rama extraída desde un repositorio remoto) con tu rama local: + +```shell +$ git merge remotename/branchname +# Fusiona actualizaciones realizadas en línea con tu trabajo local +``` + +### Extraer cambios de un repositorio remoto + +`git pull` es un atajo conveniente para realizar tanto `git fetch` y `git merge` en el mismo comando: + +```shell +$ git pull remotename branchname +# Obtiene actualizaciones en línea y las fusiona con tu trabajo local. +``` + +Como `pull` realiza una fusión en los cambios recuperados, debes asegurarte de que tu trabajo local esté confirmado antes de ejecutar el comando `pull`. Si se produce un [conflicto de fusión](/articles/resolving-a-merge-conflict-using-the-command-line) que no puedes resolver, o si decides abandonar la fusión, puedes usar `git merge --abort` para hacer que la rama vuelva al estado anterior antes de que extrajeras. + +### Further reading + +- ["Trabajar con remotos" del libro de _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% if currentVersion == "free-pro-team@latest" %} +- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)"{% endif %} diff --git a/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md b/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md new file mode 100644 index 0000000000000..5e352611f27a4 --- /dev/null +++ b/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md @@ -0,0 +1,12 @@ +--- +title: Comenzar con Git y GitHub +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/getting-started-with-git-and-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/using-git/git-workflows.md b/translations/es-ES/content/github/using-git/git-workflows.md new file mode 100644 index 0000000000000..07dc7926ec728 --- /dev/null +++ b/translations/es-ES/content/github/using-git/git-workflows.md @@ -0,0 +1,13 @@ +--- +title: Flujos de trabajo de Git +intro: 'El flujo de {% data variables.product.prodname_dotcom %} es un flujo de trabajo ligero basado en ramas que soporta equipos y proyectos que despliegan frecuentemente.' +redirect_from: + - /articles/what-is-a-good-git-workflow/ + - /articles/git-workflows +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes adoptar el método de flujo de {% data variables.product.prodname_dotcom %} para estandarizar como funciona tu equipo y como colabora con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Flujo de GitHub](/github/collaborating-with-issues-and-pull-requests/github-flow)" y " [Entender el flujo de GitHub](http://guides.github.com/overviews/flow/)" en las Guías de {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/content/github/using-git/ignoring-files.md b/translations/es-ES/content/github/using-git/ignoring-files.md new file mode 100644 index 0000000000000..6fae5d82aac54 --- /dev/null +++ b/translations/es-ES/content/github/using-git/ignoring-files.md @@ -0,0 +1,60 @@ +--- +title: Ignorar archivos +redirect_from: + - /git-ignore/ + - /ignore-files/ + - /articles/ignoring-files +intro: 'Puedes configurar Git para que ignore archivos que no quieres ingresar en {% data variables.product.product_name %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Configurar archivos ignorados para solo un repositorio + +Puedes crear un archivo de tipo *.gitignore* en el directorio raíz de tu repositorio para indicarle a Git qué archivos y directorios ignorar cuando haces una confirmación. Para compartir las reglas para ignorar con otros usuarios que clonan el repositorio, confirma el archivo de tipo *.gitignore* en tu repositorio. + +GitHub mantiene una lista oficial de archivos recomendados de tipo *.gitignore* para varios sistemas operativos, ambientes y lenguajes de programación populares en el repositorio público `github/gitignore`. También puedes usar gitignore.io para crear un archivo *.gitignore* para tu sistema operativo, lenguaje de programación o IDE. Para obtener más información, consulta la sección "[github/gitignore](https://github.com/github/gitignore)" y el sitio "[gitignore.io](https://www.gitignore.io/)". + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Navega a la ubicación de tu repositorio de Git. +3. Crea un archivo de tipo *.gitignore* para tu repositorio. + ```shell + $ touch .gitignore + ``` + +Para ver un archivo de tipo *.gitignore* de ejemplo, consulta la sección "[Algunas configuraciones comunes de .gitignore](https://gist.github.com/octocat/9257657)" en el repositorio de Octocat. + +Si quieres ignorar un archivo que ya se haya ingresado, deberás dejar de rastrearlo antes de que agregues una regla para ignorarlo. Desde tu terminal, deja de rastrear el archivo. + +```shell +$ git rm --cached FILENAME +``` + +### Configurar archivos ignorados para todos los repositorios en tu computador + +También puedes crear un archivo global de tipo *.gitignore* para definir una lista de reglas para ignorar archivos en cada repositorio de Git en tu computador. Por ejemplo, puedes crear el archivo en *~/.gitignore_global* y agregarle algunas normas. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Configura Git para que utilice el archivo de exclusión *~/.gitignore_global* en todos los repositorios de Git. + ```shell + $ git config --global core.excludesfile ~/.gitignore_global + ``` + +### Excluir archivos locales sin crear un archivo de tipo *.gitignore* + +Si no quieres crear un archivo *.gitignore* para compartir con otros, puedes crear normas que no estén confirmadas con el repositorio. Puedes utilizar esta técnica para los archivos generados de forma local que no esperas que otros usuarios generen, tales como los archivos creados por tu editor. + +Utiliza tu editor de texto favorito para abrir el archivo llamado *.git/info/exclude* dentro de la raíz de tu repositorio de Git. Cualquier norma que agregues aquí no se registrará y solo ignorará archivos de tu repositorio local. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Navega a la ubicación de tu repositorio de Git. +3. Utilizando tu editor de texto favorito, abre el archivo *.git/info/exclude*. + +### Leer más + +* [Ignorar archivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) en el libro de Pro Git +* [.gitignore](https://git-scm.com/docs/gitignore) en las páginas de man de Git +* [Una colección de plantillas útiles de *.gitignore* ](https://github.com/github/gitignore) en el repositorio github/gitignore +* Sitio de [gitignore.io](https://www.gitignore.io/) diff --git a/translations/es-ES/content/github/using-git/index.md b/translations/es-ES/content/github/using-git/index.md new file mode 100644 index 0000000000000..2ddbc1804ed84 --- /dev/null +++ b/translations/es-ES/content/github/using-git/index.md @@ -0,0 +1,42 @@ +--- +title: Utilizar GitHub +intro: 'Conoce los flujos de trabajo comunes y avanzados de Git para mejorar tu experiencia con {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /categories/19/articles/ + - /categories/using-git +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /getting-started-with-git-and-github %} + {% link_in_list /setting-your-username-in-git %} + {% link_in_list /caching-your-github-credentials-in-git %} + {% link_in_list /why-is-git-always-asking-for-my-password %} + {% link_in_list /updating-credentials-from-the-osx-keychain %} +{% topic_link_in_list /learning-about-git %} + {% link_in_list /git-workflows %} + {% link_in_list /associating-text-editors-with-git %} + {% link_in_list /configuring-git-to-handle-line-endings %} + {% link_in_list /ignoring-files %} +{% topic_link_in_list /using-common-git-commands %} + {% link_in_list /pushing-commits-to-a-remote-repository %} + {% link_in_list /getting-changes-from-a-remote-repository %} + {% link_in_list /dealing-with-non-fast-forward-errors %} +{% topic_link_in_list /managing-remote-repositories %} + {% link_in_list /about-remote-repositories %} + {% link_in_list /which-remote-url-should-i-use %} + {% link_in_list /adding-a-remote %} + {% link_in_list /changing-a-remotes-url %} + {% link_in_list /renaming-a-remote %} + {% link_in_list /removing-a-remote %} +{% topic_link_in_list /using-advanced-git-commands %} + {% link_in_list /about-git-rebase %} + {% link_in_list /using-git-rebase-on-the-command-line %} + {% link_in_list /resolving-merge-conflicts-after-a-git-rebase %} + {% link_in_list /about-git-subtree-merges %} + {% link_in_list /splitting-a-subfolder-out-into-a-new-repository %} diff --git a/translations/es-ES/content/github/using-git/learning-about-git.md b/translations/es-ES/content/github/using-git/learning-about-git.md new file mode 100644 index 0000000000000..126ff7773d93d --- /dev/null +++ b/translations/es-ES/content/github/using-git/learning-about-git.md @@ -0,0 +1,12 @@ +--- +title: Obtener información sobre Git +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/learning-about-git +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/using-git/managing-remote-repositories.md b/translations/es-ES/content/github/using-git/managing-remote-repositories.md new file mode 100644 index 0000000000000..cc017ba8e3cd5 --- /dev/null +++ b/translations/es-ES/content/github/using-git/managing-remote-repositories.md @@ -0,0 +1,15 @@ +--- +title: Administrar repositorios remotos +intro: 'Aprende a trabajar con tus repositorios locales en tu computadora y repositorios remotos alojados en {% data variables.product.product_name %}.' +mapTopic: verdadero +redirect_from: + - /categories/18/articles/ + - /remotes/ + - /categories/managing-remotes/ + - /articles/managing-remote-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md b/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md new file mode 100644 index 0000000000000..1fb3bf250ef38 --- /dev/null +++ b/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md @@ -0,0 +1,101 @@ +--- +title: Subir confirmaciones de cambios a un repositorio remoto +intro: Utiliza `git push` para subir confirmaciones de cambios realizadas en tu rama local a un repositorio remoto. +redirect_from: + - /articles/pushing-to-a-remote/ + - /articles/pushing-commits-to-a-remote-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El comando `git push` toma dos argumentos: + +* Un nombre remoto, por ejemplo, `origin` +* Un nombre de rama, por ejemplo, `main` + +Por ejemplo: + +```shell +git push <REMOTENAME> <BRANCHNAME> +``` + +Como ejemplo, habitualmente ejecutas `git push origin main` para subir tus cambios locales a tu repositorio en línea. + +### Renombrar ramas + +Para renombrar una rama, utilizarías el mismo comando `git push`, pero agregarías un argumento más: el nombre de la nueva rama. Por ejemplo: + +```shell +git push <REMOTENAME> <LOCALBRANCHNAME>:<REMOTEBRANCHNAME> +``` + +Esto sube `LOCALBRANCHNAME` a tu `REMOTENAME`, pero es renombrado a `REMOTEBRANCHNAME`. + +### Abordar errores sin avance rápido + +Si tu copia local de un repositorio está desincronizada, o "atrasada", con respecto al repositorio ascendente al que estás subiendo, recibirás un mensaje que dice que `non-fast-forward updates were rejected (las actualizaciones sin avance rápido se rechazaron)`. Esto significa que debes recuperar, o "extraer", los cambios ascendentes, antes de poder subir tus cambios locales. + +Para obtener más información sobre este error, consulta "[Resolver errores sin avance rápido](/articles/dealing-with-non-fast-forward-errors)." + +### Subir etiquetas + +Por defecto, y sin parámetros adicionales, `git push` envía todas las ramas que coinciden para que tengan el mismo nombre que las ramas remotas. + +Para subir una etiqueta única, puedes emitir el mismo comando que al subir una rama: + +```shell +git push <REMOTENAME> <TAGNAME> +``` + +Para subir todas tus etiquetas, puede escribir el comando: + +```shell +git push <REMOTENAME> --tags +``` + +### Eliminar una etiqueta o rama remota + +La sintaxis para borrar una rama es un poco críptica a primera vista: + +```shell +git push <REMOTENAME> :<BRANCHNAME> +``` + +Nota que hay un espacio antes de los dos puntos. El comando se parece a los mismos pasos que tomarías para renombrar una rama. Sin embargo, aquí estás informándole a Git que no suba _nada_ dentro de `BRANCHNAME` en `REMOTENAME`. Debido a esto, `git push` elimina la rama en el repositorio remoto. + +### Remotos y bifurcaciones + +Posiblemente ya sepas que [puedes "bifurcar" repositorios](https://guides.github.com/overviews/forking/) en GitHub. + +Cuando clonas un repositorio de tu propiedad, le proporcionas una URL remota que le indica a Git dónde extraer y subir actualizaciones. Si deseas colaborar con el repositorio original, agregarías una nueva a URL remota, normalmente llamada `upstream` (ascendente), a tu clon de Git local: + +```shell +git remote add upstream <THEIR_REMOTE_URL> +``` + +Ahora, puedes extraer actualizaciones y ramas de *sus* bifurcaciones: + +```shell +git extrae ascendente +# Toma las ramas de los remotos ascendentes +> remoto: Contando objetos: 75, realizado. +> remote: Compressing objects: 100% (53/53), done. +> remoto: Total 62 (delta 27), reutilizados 44 (delta 9) +> Descompimiendo objetos: 100 % (62/62), realziado. +> From https://{% data variables.command_line.codeblock %}/octocat/repo +> * [new branch] main -> upstream/main +``` + +Cuando hayas finalizado tus cambios locales, puedes subir tu rama local a GitHub e [iniciar una solicitud de extracción](/articles/about-pull-requests). + +Para obtener más información sobre cómo trabajar con bifurcaciones, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". + +### Further reading + +- [El capítulo "Remotos" del libro "Pro Git"](https://git-scm.com/book/ch5-2.html) +- [Documentación en línea sobre `git remote`](https://git-scm.com/docs/git-remote.html) +- "[Git cheatsheet](/articles/git-cheatsheet)" (Hoja introductoria de Git) +- "[Flujos de trabajo de Git](/articles/git-workflows)" +- "[Manual de Git](https://guides.github.com/introduction/git-handbook/)" diff --git a/translations/es-ES/content/github/using-git/removing-a-remote.md b/translations/es-ES/content/github/using-git/removing-a-remote.md new file mode 100644 index 0000000000000..54acf55be75fe --- /dev/null +++ b/translations/es-ES/content/github/using-git/removing-a-remote.md @@ -0,0 +1,59 @@ +--- +title: Eliminar un remoto +intro: Utiliza el comando `git remote rm` para eliminar una URL remota de tu repositorio. +redirect_from: + - /articles/removing-a-remote +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El comando `git remote rm` toma un argumento: + +* El nombre de un remoto, por ejemplo `destination` (destino) + +### Ejemplo + +Estos ejemplos asumen que estás [clonando con HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), lo cual se recomienda. + +```shell +$ git remote -v +# Ver los remotos actuales +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) + +$ git remote rm destination +# Eliminar remoto +$ git remote -v +# Verificar que se haya ido +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +``` + +{% warning %} + +**Nota**: `git remote rm` no elimina el repositorio remoto del servidor. Simplemente, elimina de tu repositorio local el remoto y sus referencias. + +{% endwarning %} + +### Solución de problemas + +Te puedes encontrar con estos errores al intentar eliminar un remoto. + +#### No se pudo eliminar la sección de configuración 'remote.[name]' + +Este error significa que el remoto que trataste de eliminar no existe: + +```shell +$ git remote rm sofake +> error: No se pudo eliminar la sección de configuración 'remote.sofake' +``` + +Comprueba que escribiste correctamente el nombre del remoto. + +### Further reading + +- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/renaming-a-remote.md b/translations/es-ES/content/github/using-git/renaming-a-remote.md new file mode 100644 index 0000000000000..211300d9cbcc6 --- /dev/null +++ b/translations/es-ES/content/github/using-git/renaming-a-remote.md @@ -0,0 +1,59 @@ +--- +title: Renombrar un remoto +intro: Utiliza el comando `git remote rename` para renombrar un remoto existente. +redirect_from: + - /articles/renaming-a-remote +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El comando `git remote rename` toma dos argumentos: + +* Un nombre de remoto existente, por ejemplo, `origen` +* Un nombre nuevo para el remoto, por ejemplo, `destino` + +### Ejemplo + +Estos ejemplos asumen que estás [clonando con HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), lo cual se recomienda. + +```shell +$ git remote -v +# Ver remotos existentes +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) + +$ git remote rename origin destination +# Cambiar el nombre del remoto de 'origen' a 'destino' + +$ git remote -v +# Verificar el nombre nuevo del remoto +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +``` + +### Solución de problemas + +Puedes encontrar estos errores cuando intentes renombrar un remoto. + +#### No se pudo renombrar la sección de configuración 'remoto.[nombre antiguo]' con 'remoto.[nombre nuevo]' + +Este error significa que el remoto que probaste con el nombre del remoto antiguo que escribiste no existe. + +Puedes verificar los remotos que existen actualmente con el comando `git remote -v`: + +```shell +$ git remote -v +# Ver remotos existentes +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +``` + +#### El [nombre nuevo] del remoto ya existe. + +Este error significa que el nombre del remoto que quieres utilizar ya existe. Para resolverlo, utiliza un nombre de remoto diferente o renombra el remoto original. + +### Further reading + +- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/resolving-merge-conflicts-after-a-git-rebase.md b/translations/es-ES/content/github/using-git/resolving-merge-conflicts-after-a-git-rebase.md new file mode 100644 index 0000000000000..656e0592983d2 --- /dev/null +++ b/translations/es-ES/content/github/using-git/resolving-merge-conflicts-after-a-git-rebase.md @@ -0,0 +1,30 @@ +--- +title: Resolver conflictos de fusión después de una rebase de Git +intro: 'Cuando realizas una operación `git rebase`, normalmente mueves confirmaciones de un lado a otro. Por este motivo, puedes generar una situación en la que se introduzca un conflicto de fusión. Esto implica que dos de tus confirmaciones modificaron la misma línea del mismo archivo, y Git no sabe qué cambio aplicar.' +redirect_from: + - /articles/resolving-merge-conflicts-after-a-git-rebase +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Después de reordenar y manipular confirmaciones utilizando `git rebase`, si ocurre un conflicto de fusión, Git te lo informará con el siguiente mensaje impreso en el terminal: + +```shell +error: no se pudo aplicar fa39187... algo para agregar al parte A + +Cuando hayas resuelto este problema, ejecuta "git rebase --continue". +Si prefieres saltear este parche, ejecuta "git rebase --skip". +Para revisar la rama original y detener el proceso de rebase, ejecuta "git rebase --abort". +No se pudo aplicar fa39187f3c3dfd2ab5faa38ac01cf3de7ce2e841... Cambia el archivo falso +``` + +Aquí Git te está diciendo qué confirmación está causando el conflicto (`fa39187`). Se te ofrecen tres opciones: + +* Puedes ejecutar `git rebase --abort` para deshacer por completo la rebase. Git te regresará al estado de tu rama tal como estaba antes de haber pedido `git rebase`. +* Puedes ejecutar `git rebase --skip` para saltear por completo la confirmación. Esto significa que no se incluirá ninguno de los cambios introducidos por la confirmación problemática. Es muy poco común que elijas esta opción. +* Puedes corregir el conflicto. + +Para corregir el conflicto, puedes seguir [los procedimientos estándar para resolver conflictos de fusión desde la línea de comando](/articles/resolving-a-merge-conflict-using-the-command-line). Cuando termines, tendrás que pedir `git rebase --continue` para que Git continúe procesando el resto de la rebase. diff --git a/translations/es-ES/content/github/using-git/setting-your-username-in-git.md b/translations/es-ES/content/github/using-git/setting-your-username-in-git.md new file mode 100644 index 0000000000000..56331e37d11a1 --- /dev/null +++ b/translations/es-ES/content/github/using-git/setting-your-username-in-git.md @@ -0,0 +1,51 @@ +--- +title: Configurar tu nombre de usuario en Git +intro: 'Git utiliza un nombre de usuario para asociar las confirmaciones con una identidad. El nombre de usuario de Git no es tu mismo nombre de usuario de {% data variables.product.product_name %}.' +redirect_from: + - /articles/setting-your-username-in-git +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes cambiar el nombre que está asociado con tus confirmaciones de Git utilizando el comando `git config`. El nuevo nombre que configures será visible en cualquier confirmación futura que subas a {% data variables.product.product_name %} desde la línea de comando. Si deseas mantener tu nombre real privado, puedes utilizar cualquier texto como nombre de usuario de Git. + +Cambiar el nombre asociado con tus confirmaciones de Git utilizando `git config` afectará únicamente a las confirmaciones futuras y no cambiará el nombre utilizado para las confirmaciones anteriores. + +### Configurar tu nombre de usuario de Git para *cada* repositorio en tu computadora + +{% data reusables.command_line.open_the_multi_os_terminal %} + +2. {% data reusables.user_settings.set_your_git_username %} + ```shell + $ git config --global user.name "Mona Lisa" + ``` + +3. {% data reusables.user_settings.confirm_git_username_correct %} + ```shell + $ git config --global user.name + > Mona Lisa + ``` + +### Configurar tu nombre de usuario de Git para un repositorio único + +{% data reusables.command_line.open_the_multi_os_terminal %} + +2. Cambia el directorio de trabajo actual al repositorio local donde deseas configurar el nombre que está asociado con tus confirmaciones de Git. + +3. {% data reusables.user_settings.set_your_git_username %} + ```shell + $ git config user.name "Mona Lisa" + ``` + +3. {% data reusables.user_settings.confirm_git_username_correct %} + ```shell + $ git config user.name + > Mona Lisa + ``` + +### Further reading + +- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" +- ["Configuración de Git" del libro _Pro Git_](https://git-scm.com/book/en/Customizing-Git-Git-Configuration) diff --git a/translations/es-ES/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/es-ES/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md new file mode 100644 index 0000000000000..79e322261ec03 --- /dev/null +++ b/translations/es-ES/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -0,0 +1,76 @@ +--- +title: Dividir una subcarpeta en un nuevo repositorio +redirect_from: + - /articles/splitting-a-subpath-out-into-a-new-repository/ + - /articles/splitting-a-subfolder-out-into-a-new-repository +intro: Puedes convertir una carpeta dentro de un repositorio de Git en un nuevo repositorio. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Si creas un nuevo clon del repositorio, no perderás ninguno de tus historiales o cambios de Git cuando divides una carpeta en un repositorio separado. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Cambia el directorio de trabajo actual a la ubicación donde deseas crear tu nuevo repositorio. +3. Clona el repositorio que contiene la subcarpeta. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME + ``` +4. Cambia el directorio de trabajo actual por tu repositorio clonado. + ```shell + $ cd REPOSITORY-NAME + ``` +5. Para filtrar la subcarpeta desde el resto de los archivos en el repositorio, ejecuta [`git filter-branch`](https://git-scm.com/docs/git-filter-branch), proporcionando esta información: + - `FOLDER-NAME`: la carpeta dentro de tu proyecto desde la que desearías crear un repositorio separado. + + {% windows %} + + {% tip %} + + **Sugerencia:** los usuarios de Windows deberían utilizar `/` para delimitar carpetas. + + {% endtip %} + + {% endwindows %} + - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. + ```shell + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + # Filter the specified branch in your directory and remove empty commits + > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) + > Ref 'refs/heads/BRANCH-NAME' was rewritten + ``` + El repositorio debería ahora únicamente contener archivos que estuvieron en tu subcarpeta. + +6. [Crea un nuevo repositorio](/articles/creating-a-new-repository/) en {% data variables.product.product_name %}. +7. En la parte superior de la página nueva Quick Setup del repositorio {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto. ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) + + {% tip %} + + **Sugerencia:** Para obtener información sobre la diferencia entre las URL HTTPS y SSH consulta "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" + + {% endtip %} + +8. Verifica el nombre remoto existente para tu repositorio. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) + ``` + +9. Configura una URL remota nueva para tu nuevo repositorio utilizando el nombre remoto existente y la URL del repositorio remoto que copiaste en el paso 7. + ```shell + git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git + ``` +10. Verifica que la URL remota haya cambiado con el nombre de tu nuevo repositorio. + ```shell + $ git remote -v + # Verify new remote URL + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) + ``` +11. Sube tus cambios al nuevo repositorio en {% data variables.product.product_name %}. + ```shell + git push -u origin BRANCH-NAME + ``` diff --git a/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md b/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md new file mode 100644 index 0000000000000..6db041bab53d2 --- /dev/null +++ b/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md @@ -0,0 +1,37 @@ +--- +title: Actualizar credenciales desde la Keychain OSX +intro: 'Necesitarás actualizar tus credenciales guardadas en el ayudante `git-credential-osxkeychain` si cambias tu{% if currentVersion != "github-ae@latest" %} nombre de usuario, contraseña, o{% endif %} token de acceso personal en {% data variables.product.product_name %}.' +redirect_from: + - /articles/updating-credentials-from-the-osx-keychain + - Entrada de contraseña de GitHub en Keychain +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.password-authentication-deprecation %} + +### Actualizar tus credenciales a través de Keychain Access (Acceso keychain) + +1. Da clic en el icono de Spotlight (lupa) en el costado derecho de la barra de menú. Teclea `Keychain access` y luego presiona la tecla Enter para lanzar la app. ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png) +2. En Keychain Access (Acceso keychain), busca **{% data variables.command_line.backticks %}**. +3. Encuentra la entrada "internet password" (contraseña de internet) para `{% data variables.command_line.backticks %}`. +4. Edita o borra la entrada según corresponda. + +### Eliminar tus credenciales a través de la línea de comando + +A través de la línea de comandos, puedes utilizar el ayudante de credenciales directamente para borrar la entrada de keychain. + +```shell +$ git credential-osxkeychain erase +host={% data variables.command_line.codeblock %} +protocol=https +> [Press Return] +``` + +Si resulta exitoso, no se imprimirá nada. Para probar su funcionamiento, trata de clonar un repositorio desde {% data variables.product.product_location %}. Si se te pide una contraseña, la entrada de keychain se borró. + +### Further reading + +- [Almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git/)" diff --git a/translations/es-ES/content/github/using-git/using-advanced-git-commands.md b/translations/es-ES/content/github/using-git/using-advanced-git-commands.md new file mode 100644 index 0000000000000..48b246fa58689 --- /dev/null +++ b/translations/es-ES/content/github/using-git/using-advanced-git-commands.md @@ -0,0 +1,15 @@ +--- +title: Utilizar comandos de Git avanzados +intro: '' +mapTopic: verdadero +redirect_from: + - /categories/52/articles/ + - /categories/advanced-git/ + - /articles/using-advanced-git-commands + - /github/using-git/changing-author-info +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/using-git/using-common-git-commands.md b/translations/es-ES/content/github/using-git/using-common-git-commands.md new file mode 100644 index 0000000000000..ee40fb8c0a164 --- /dev/null +++ b/translations/es-ES/content/github/using-git/using-common-git-commands.md @@ -0,0 +1,12 @@ +--- +title: Utilizar comandos de Git comunes +intro: '' +mapTopic: verdadero +redirect_from: + - /articles/using-common-git-commands +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md new file mode 100644 index 0000000000000..170a9e7c3cfd2 --- /dev/null +++ b/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -0,0 +1,142 @@ +--- +title: Utilizar la rebase de Git en la línea de comando +redirect_from: + - /articles/using-git-rebase/ + - /articles/using-git-rebase-on-the-command-line +intro: Aquí hay un breve tutorial acerca de usar `git rebase` en la línea de comando. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +En este ejemplo, abordaremos todos los comandos disponibles de `git rebase`, excepto `exec`. + +Comenzaremos nuestra rebase ingresando `git rebase --interactive HEAD~7` en el terminal. Nuestro editor de texto preferido mostrará las siguientes líneas: + +``` +pick 1fc6c95 Patch A +pick 6b2481b Patch B +pick dd1475d something I want to split +pick c619268 A fix for Patch B +pick fa39187 something to add to patch A +pick 4ca2acc i cant' typ goods +pick 7b36971 something to move before patch B +``` + +En este ejemplo, haremos lo siguiente: + +* Combinar la quinta confirmación (`fa39187`) con la confirmación `"Patch A"` (`1fc6c95`), utilizando `squash` (combinar). +* Mover la última confirmación (`7b36971`) hacia arriba antes de la confirmación `"Patch B"` (`6b2481b`) y la conservarla como `pick`. +* Fusionar la confirmación `"A fix for Patch B"` (`c619268`) con la confirmación `"Patch B"` (`6b2481b`) y omitir el mensaje de confirmación utilizando `fixup`. +* Separar la tercera confirmación (`dd1475d`) en dos confirmaciones más pequeñas utilizando `edit` (editar). +* Corregir el mensaje de confirmación de la confirmación mal escrita (`4ca2acc`), utilizando `reword` (otro texto). + +¡Uf! Parece mucho trabajo, pero haciendo cada paso por vez, podemos concretar esos cambios fácilmente. + +Para comenzar, tendremos que modificar los comandos en el archivo para que luzca como sigue: + +``` +pick 1fc6c95 Patch A +squash fa39187 something to add to patch A +pick 7b36971 something to move before patch B +pick 6b2481b Patch B +fixup c619268 A fix for Patch B +edit dd1475d something I want to split +reword 4ca2acc i cant' typ goods +``` + +Hemos cambiado cada comando de la línea desde `pick` al comando que nos interesa. + +Ahora, guarda y cierra el editor; esto comenzará la rebase interactiva. + +Git saltea el primer comando de rebase, `pick 1fc6c95`, ya que no necesita hacer nada. Va al siguiente comando, `squash fa39187`. Como esta operación requiere tu entrada, Git vuelve a abrir tu editor de texto. El archivo que abre luce parecido a lo siguiente: + +``` +# Es una combinación de dos confirmaciones. +# El mensaje de la primera confirmación es: + +Patch A + +# Este es el mensaje de la 2.a confirmación: + +something to add to patch A + +# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con +# con '#' se ignoran, y un mensaje vacío anula la confirmación. +# Actualmente no se encuentra en una rama. +# Cambios por confirmar: +# (usa "git reset HEAD ..." para deshacer) +# +# modificado: a +# +``` + +Este archivo es la manera de Git de decir, "Oye, esto es lo que estoy a punto de hacer con esta `squash` (combinación)". Detalla el primer mensaje de confirmación (`"Patch A"`) y el segundo mensaje de confirmación (`"something to add to patch A"`). Si estás satisfecho con estos mensajes de confirmación, puedes guardar el archivo y cerrar el editor. De lo contrario, tienes la opción de cambiar el mensaje de confirmación, simplemente, cambiando el texto. + +Cuando el editor esté cerrado, la rebase continúa: + +``` +pick 1fc6c95 Patch A +squash fa39187 something to add to patch A +pick 7b36971 something to move before patch B +pick 6b2481b Patch B +fixup c619268 A fix for Patch B +edit dd1475d something I want to split +reword 4ca2acc i cant' typ goods +``` + +Git procesa los dos comandos `pick` (para `pick 7b36971` y `pick 6b2481b`). *También* procesa el comando `fixup` (`fixup c619268`), ya que este no necesita ninguna interacción. `fixup` fusiona los cambios de `c619268` en la confirmación que tiene ante sí, `6b2481b`. Ambos cambios tendrán el mismo mensaje de confirmación: `"Patch B"`. + +Git llega a la operación `edit dd1475d`, se detiene e imprime el siguiente mensaje para el terminal: + +```shell +Puedes modificar la confirmación ahora con + + git commit --amend + +Una vez que estés satisfecho con tus cambios, ejecuta + + git rebase --continue +``` + +En este punto, puedes editar cualquiera de los archivos de tu proyecto para hacer más cambios. Para cada cambio que hagas, tendrás que realizar una confirmación nueva. Lo puedes hacer ingresando el comando `git commit --amend`. Cuando termines de hacer todos tus cambios, puedes ejecutar `git rebase --continue`. + +Luego Git llega al comando `reword 4ca2acc`. Este abre tu editor de texto una vez más y presenta la siguiente información: + +``` +i cant' typ goods + +# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con +# con '#' se ignoran, y un mensaje vacío anula la confirmación. +# Actualmente no se encuentra en una rama. +# Cambios por confirmar: +# (use "git reset HEAD^1 ..." to unstage) +# +# modificado: a +# +``` + +Como antes, Git muestra el mensaje de confirmación para que lo edites. Puedes cambiar el texto (`"i cant' typ goods"`), guardar el archivo y cerrar el editor. Git terminará la rebase y te devolverá al terminal. + +### Subir código de rebase a GitHub + +Como has modificado el historial de Git, el `git push origin` común **no** funcionará. Tendrás que modificar el comando realizando un "empuje forzado" de tus últimos cambios: + +```shell +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes +$ git push origin main --force +``` + +{% warning %} + +El cargar forzadamente tiene implicaciones serias ya que cambia la secuencia del historial de confirmaciones para la rama. Utilízalo con cuidado, especialmente si muchas personas acceden a tu repositorio. + +{% endwarning %} + +### Further reading + +* "[Resolver conflictos de fusión después de una rebase de Git](/articles/resolving-merge-conflicts-after-a-git-rebase)" diff --git a/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md b/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md new file mode 100644 index 0000000000000..7abbd8f830ac8 --- /dev/null +++ b/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md @@ -0,0 +1,70 @@ +--- +title: '¿Qué URL remota debería utilizar?' +redirect_from: + - /articles/which-url-should-i-use/ + - /articles/which-remote-url-should-i-use +intro: 'Existen varias formas de clonar los repositorios disponibles en {% data variables.product.product_location %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando ves un repositorio mientras estás registrado en tu cuenta, las URL que puedes utilizar para clonar el proyecto en tu computadora están disponibles debajo de los detalles del repositorio: + +Para obtener información acerca de configurar o cambiar tu URL remota, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". + +### Clonar con las URL con HTTPS + +Las URL clon `https://` se encuentran disponibles en todos los repositorios, sin importar su visibilidad. Las URL clon `https://` funcionan aún si estás detrás de un cortafuegos o de un proxy. + +Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio mendiante URL con HTTPS en la línea de comando, Git te pedirá tu nombre de usuario y contraseña de {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %} + +{% data reusables.command_line.provide-an-access-token %} + +{% tip %} + +**Tips**: + +- Puedes utilizar un asistente de credenciales para que Git recuerde tus credenciales de {% data variables.product.prodname_dotcom %} cada que habla con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[ Almacenar tus credencialesde {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git)". + +- Para clonar un repositorio sin autenticarse en {% data variables.product.product_name %} desde la línea de comando, puedes utilizar {% data variables.product.prodname_desktop %} como alternativa. Para obtener más información, consulta la sección "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". + +{% endtip %} + + {% if currentVersion == "free-pro-team@latest" %}Si prefieres utilizar SSH pero no puedes conectarte por el puerto 22, podrías utilizar SSH sobre el puerto de HTTPS. Para obtener más información, consulta la sección "[Utilizar SSH a través del puerto HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %} + +### Clonar con URL de SSH + +Las URL de SSH brindan acceso a un repositorio de Git por medio de SSH, un protocolo seguro. Para utilizar estas URL, debes generar un par de claves SSH en tu computador y añadir la llave **pública** a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Conectarse a {% data variables.product.prodname_dotcom %} con SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)". + +Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio remoto utilizando URL de SSH, se te solicitará una contraseña y deberás ingresar tu frase de acceso con llave de SSH. Para obtener más información, consulta la sección "[Trabajar con frases de acceso con llave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". + +{% if currentVersion == "free-pro-team@latest" %}Si estás accediendo a una organización que utiliza el inicio de sesión único (SSO) de SAML, debes autorizar a tu llave SSH para que acceda a la organización antes de que te autentiques. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" y "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". {% endif %} + +{% tip %} + +**Tip**: Puedes utilizar una URL con SSH para clonar un repositorio a tu computador, o como una forma segura de desplegar tu código en servidores productivos. También puedes utilizar el envío a un agente de SSH con tu script de despliegue para evitar administrar llaves en el servidor. Para obtener más información, consulta la sección "[Utilizar el Reenvío de Agente de SSH](/developers/overview/using-ssh-agent-forwarding)". + +{% endtip %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} + +### Clonar con {% data variables.product.prodname_cli %} + +También puedes instalar {% data variables.product.prodname_cli %} para utilizar flujos de trabajo de {% data variables.product.product_name %} en tu terminal. Para obtener más información, consulta la documentación de [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/). + +{% endif %} + +{% if currentVersion != "github-ae@latest" %} +### Clonar con Subversion + +También puedes utilizar un cliente de [Subversion](https://subversion.apache.org/) para acceder a cualquier repositorio en {% data variables.product.prodname_dotcom %}. Subversion ofrece características diferentes a Git. Para obtener más información, consulta la sección "[¿Cuáles son las diferencias entre Subversion y Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" +También puedes acceder a los repositorios en + +{% data variables.product.prodname_dotcom %} desde los clientes de Subversion. Para obtener más información, consulta la sección "[Soporte para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". +{% endif %} + +### Further reading + +- [Trabajar con URL Remotas](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) del sitio del libro de _Pro Git_ diff --git a/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md b/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md new file mode 100644 index 0000000000000..48f4763a55254 --- /dev/null +++ b/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md @@ -0,0 +1,22 @@ +--- +title: '¿Por qué Git me pregunta siempre mi contraseña?' +intro: 'Si Git te solicita el nombre de usuario y la contraseña cada vez que tratas de interactuar con GitHub, probablemente estás usando la URL del clon HTTPS para tu repositorio.' +redirect_from: + - /articles/why-is-git-always-asking-for-my-password +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Utilizar una URL remota de tipo HTTPS tiene algunas ventajas comparadas con el uso de SSH. Es más fácil de configurar que SSH, y habitualmente trabaja mediante cortafuectos y proxies estrictos. Sin embargo, también te solicita que ingreses tus credenciales de {% data variables.product.product_name %} cada vez que extraes o subes un repositorio. + +{% data reusables.user_settings.password-authentication-deprecation %} + +Puedes evitar que se te solicite tu contraseña si configuras Git para que [almacene tus credenciales en el caché](/github/using-git/caching-your-github-credentials-in-git). Ya que hayas configurado el almacenamiento de credenciales en caché, Git utilizará to token de acceso personal almacenado en caché automáticamente cada que extraigas o subas información a un repositorio utilizando HTTPS. + +### Further reading + +* "[¿Qué URL remota debería utilizar?](/articles/which-remote-url-should-i-use/#cloning-with-https-urls)" +* "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +* "[Agregar tu llave SSH al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)" diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md new file mode 100644 index 0000000000000..909416e68ba5a --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md @@ -0,0 +1,33 @@ +--- +title: Acerca de los gráficos del repositorio +intro: Los gráficos del repositorio te ayudan a ver y analizar datos para tu repositorio. +redirect_from: + - /articles/using-graphs/ + - /articles/about-repository-graphs +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La gráfica de un repositorio te proporciona información sobre {% if currentVersion == "free-pro-team@latest" %} el tráfico, los proyectos que dependen del repositorio,{% endif %} los colaboradores y las confirmaciones al repositorio, y las bifurcaciones y red de un repositorio. Si tú mantienes un repositorio, puedes usar estos datos para comprender mejor quién está usando tu repositorio y por qué lo están usando. + +{% if currentVersion == "free-pro-team@latest" %} + +Algunos gráficos del repositorio solo están disponibles en repositorios públicos con {% data variables.product.prodname_free_user %}: +- Pulso +- Colaboradores +- Tráfico +- Confirmaciones +- Frecuencia de código +- Red + +Todos los otros gráficos del repositorio están disponibles en todos los repositorios. Cada gráfico del repositorio está disponible en repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} y {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} + +{% endif %} + +### Further reading + +- "[Acceso a datos básicos del repositorio](/articles/accessing-basic-repository-data)" +- "[Analizar cambios en el contenido de un repositorio](/articles/analyzing-changes-to-a-repository-s-content)" +- "[Comprender las conexiones entre repositorios](/articles/understanding-connections-between-repositories)" diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md new file mode 100644 index 0000000000000..13b26a1b0dd9d --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -0,0 +1,90 @@ +--- +title: Acerca del gráfico de dependencias +intro: 'Información detallada sobre la gráfica de dependencias, el ecosistema con el que es compatible, y sobre cómo determina de qué paquetes depende un repositorio.' +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Disponibilidad de la gráfica de dependencias + +La gráfica de dependencias se encuentra disponible para cada{% if currentVersion == "free-pro-team@latest" %} repositorio público{% endif %} que define las dependencias en un ecosistema de paquetes compatible utilizando un formato de archivo compatible.{% if currentVersion == "free-pro-team@latest" %} Los administradores del repositorio también pueden configurar la gráfica de dependencias para los repositorios privados.{% endif %} + +{% data reusables.repositories.enable-security-alerts %} + +### Acerca del gráfico de dependencias + +La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Para cada repositorio, muestra{% if currentVersion == "free-pro-team@latest" %}: + +- Las dependencias, ecosistemas y paquetes de los cuales depende +- Los dependientes, repositorios y paquetes que dependen de ella{% else %} dependencias, es decir, los ecosistemas y los paquetes de los cuales depende. {% data variables.product.prodname_ghe_server %} no calcula información alguna sobre los dependientes, repositorios y paquetes que dependen de un repositorio.{% endif %} + +Cuando subes una confirmación a {% data variables.product.product_name %} que cambia o agrega un archivo bloqueado o de manifiesto compatible a la rama predeterminada, la gráfica de dependencias se actualiza automáticamente.{% if currentVersion == "free-pro-team@latest" %} Adicionalmente, la gráfica se actualiza cuando cualquiera carga un cambio al repositorio de una de tus dependencias.{% endif %} Para obtener más información sobre los archivos de manifiesto y ecosistemas compatibles, consulta la sección "[Ecosistemas de paquetes compatibles](#supported-package-ecosystems)" más adelante. + +{% if currentVersion == "free-pro-team@latest" %} +Cuando creas una solicitud de cambios que contenga cambios para las dependencias que apunten a la rama predeterminada, +{% data variables.product.prodname_dotcom %} utilizará la gráfica de dependencias para agregar revisiones de dependencias a la soicitud de cambios. Estas indican si las dependencias contendrán vulnerabilidades y, si es el caso, la versión de la dependencia en la cual se arregló la vulnerabilidad. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +{% endif %} + +### Dependencias que se incluyen + +La gráfica de dependencias incluye todas las dependencias de un repositorio que se describan en los archivos de manifiesto y de bloqueo o sus equivalentes para los ecosistemas compatibles. Esto incluye: + +- Las dependencias directas que se definen explícitamente en el archivo de manifiesto o de bloqueo +- Las dependencias indirectas de estas dependencias directas, también conocidas como dependencias transitorias o sub-dependencias + +La gráfica de dependencias identifica las dependencias indirectas{% if currentVersion == "free-pro-team@latest" %} ya sea explícitamente desde un archivo bloqueado o mediante la verificación de las dependencias de tus dependencias directas. Para la gráfica más confiable, debes utilizar archivos de bloqueo (o su equivalente), ya que estos definen exactamente qué versiones de las dependencias directas e indirectas estás utilizando actualmente. Si utilizas archivos de bloqueo, también te aseguras de que todos los contribuyentes del repositorio están utilizando las mismas versiones, lo cual te facilitará el probar y depurar el código{% else %} de los archivos de bloqueo{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +### Dependientes incluídos + +Para los repositorios públicos, únicamente se reportan los repositorios públicos que dependen de éste o de los paquetes que publicas. Esta información no se reporta para los repositorios privados.{% endif %} + +### Utiizar la gráfica de dependencias + +Puedes utilizar la gráfica de dependencias para: + +- Explora los repositorios de los cuales depende tu código{% if currentVersion == "free-pro-team@latest" %} y aquellos que dependen de él{% endif %}. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% if currentVersion == "free-pro-team@latest" %} +- Ver en un solo tablero un resumen de las dependencias que se utilizan en los repositorios de tu organización. Para obtener más información, consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} +- Ver y actualizar las dependencias vulnerables de tu repositorio. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".{% if currentVersion == "free-pro-team@latest" %} +- Consulta la información sobre las dependencias vulnerables en las solicitudes de cambios. Para obtener más información, consulta la sección "[Revisar los cambios de dependencia en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %} + +### Habilitar la gráfica de dependencias + +{% if currentVersion == "free-pro-team@latest" %}Para generar una gráfica de dependencias, {% data variables.product.product_name %} necesita acceso de solo lectura a los archivos bloqueados y de manifiesto de la dependencia para el repositorio en cuestión. La gráfica de dependencias se genera automáticamente para todos los repositorios públicos y puedes elegir habilitarla para los privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}Si la gráfica de dependencias no se encuentra disponible en tu sistema, tu administrador de sitio puede habilitarla junto con las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Si la gráfica de dependencias no está disponible en tu sistema, tu administrador de sitio puede habilitarla, así como puede habilitar las alertas de seguridad. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". + +{% endif %} + +Cuando la gráfica de dependencias se habilita por primera vez, cualquier manifiesto y archivo de bloqueo para los ecosistemas compatibles se pasarán de inmediato. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Una vez que se habilite, la gráfica se actualiza automáticamente con cada subida al repositorio{% if currentVersion == "free-pro-team@latest" %} y con cada subida a otros repositorios en la gráfica{% endif %}. + +### Ecosistemas de paquetes compatibles + +Los formatos recomendados definen explícitamente qué versiones se utilizan para todas las dependencias directas e indirectas. Si utilizas estos formatos, tu gráfica de dependencias será más precisa. También refleja la configuración actual de la compilación y habilita la gráfica de dependencias para reportar vulnerabilidades tanto en las dependencias directas como en las indirectas.{% if currentVersion == "free-pro-team@latest" %} Las dependencias directas que se infieran de un archivo de manifiesto (o de su equivalente) se excluirán de las verificaciones para las dependencias vulnerables.{% endif %} + +| Administración de paquetes | Idiomas | Formatos recomendados | Todos los formatos compatibles | +| -------------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | +| Maven | Java, Scala | `pom.xml` | `pom.xml` | +| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json` | +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | + +{% note %} + +**Nota:** Si listas tus dependencias de Python dentro de un archivo `setup.py`, es probable que no podamos analizar y listar cada una de las dependencias en tu proyecto. + +{% endnote %} + +### Further reading + +- "[Gráfica de dependencias](https://en.wikipedia.org/wiki/Dependency_graph)" en Wikipedia +- "[Explorando las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- "[Visualizar las perspectivas para tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md new file mode 100644 index 0000000000000..717db538ec99a --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md @@ -0,0 +1,12 @@ +--- +title: Acceso a datos básicos del repositorio +intro: 'Puedes ver la información básica de un repositorio, tal como la actividad del mismo{% if currentVersion == "free-pro-team@latest" %}, su tráfico,{% endif %} y la actividad de las contribuciones.' +mapTopic: verdadero +redirect_from: + - /articles/accessing-basic-repository-data +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md new file mode 100644 index 0000000000000..b03d193a6bdc3 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md @@ -0,0 +1,14 @@ +--- +title: Analizar cambios en el contenido de un repositorio +intro: 'Puedes ver los cambios en el contenido de un repositorio al analizar las confirmaciones del repositorio, la frecuencia de confirmación, y las incorporaciones y eliminaciones de contenido.' +redirect_from: + - /articles/viewing-commit-frequency-in-a-repository/ + - /articles/analyzing-changes-to-a-repository-s-content + - /articles/analyzing-changes-to-a-repositorys-content +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md new file mode 100644 index 0000000000000..660520b06b2a7 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -0,0 +1,122 @@ +--- +title: Explorar las dependencias de un repositorio +intro: 'Al utilizar la gráfica de dependencias, puedes ver los paquetes de los cuales depende tu proyecto{% if currentVersion == "free-pro-team@latest" %} y los repositorios que dependen de él{% endif %}. Adicionalmente, puedes ver cualquier vulnerabilidad que se detecte en sus dependencias.' +redirect_from: + - /articles/listing-the-packages-that-a-repository-depends-on + - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on + - /articles/listing-the-projects-that-depend-on-a-repository + - /github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository + - /github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Visualizar la gráfica de dependencias + +{% data reusables.repositories.enable-security-alerts %} + +La gráfica de dependencias muestra las dependencias{% if currentVersion == "free-pro-team@latest" %} y los dependientes{% endif %} de tu repositorio. Para obtener más información acerca de la detección de dependencias y de cuáles ecosistemas son compatibles, consulta la sección [Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %} +4. Opcionalmente, debajo de "Gráfica de dependencias", da clic en **Dependientes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} + +#### Vista de dependencias + +{% if currentVersion == "free-pro-team@latest" %} +Las dependencias se agrupan por ecosistema. Puedes expandir una dependencia para ver a su vez sus dependencias. Para las dependencias de los repositorios públicos que se hospedan en +{% data variables.product.product_name %}, también puedes dar clic en la dependencia para ver el repositorio. Las dependencias en los repositorios privados, paquetes privados, o archivos no reconocidos se muestran en texto simple. + +Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a {% data variables.product.prodname_dependabot_alerts %}. + +![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph.png) + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a las +{% data variables.product.prodname_dependabot_alerts %}. + +![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png) + +{% note %} + +**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. + +{% endnote %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se detectan vulnerabilidades en el repositorio, estas se mostrarán en la parte superior de la vista para los usuarios con acceso a las alertas de seguridad. + +![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png) + +{% note %} + +**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. + +{% endnote %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### Vista de dependientes + +Para los repositorios públicos, la vista de dependientes muestra cómo otros repositorios utilizan este repositorio. Para mostrar únicamente los repositorios que contienen una biblioteca en un administrador de paquetes, da cilc en **CANTIDAD de paquetes** inmediatamente sobre la lista de repositorios dependientes. La cantidad de dependientes es aproximada y podría no siempre empatar con los dependientes listados. + +![Dependents graph](/assets/images/help/graphs/dependents_graph.png) + +### Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado + +Los administradores del repositorio pueden habilitar o inhabilitar la gráfica de dependencias para los repositorios privados. + +También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Lee los mensajes sobre el otorgar acceso de solo lectura a {% data variables.product.product_name %} para los datos del repositorio para así habilitar la gráfica de dependencias, posteriormente, da clic en **Habilitar** junto a "Gráfica de Dependencias". ![Botón de "Habilitar" para la gráfica de dependencias](/assets/images/help/repository/dependency-graph-enable-button.png) + +Puedes inhabilitar la gráfica de dependencias en cualquier momento si das clic en **Inhabilitar** junto a "Gráfica de Dependencias" en la pestaña de Seguridad & análisis. + +### Changing the "Used by" package + +If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." + +The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects. + +!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png) + +Clicking any item in this section takes you to the **Dependents** tab of the dependency graph. + +The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png) + +{% endif %} + +### Solución de problemas del gráfico de dependencias + +Si tu gráfica de dependencias está vacía, puede que haya un problema con el archivo que contiene tus dependencias. Revisa el archivo para asegurarte de que tiene el formato correcto para el tipo de archivo. + +{% if currentVersion == "free-pro-team@latest" %} +Si este archivo tiene el formato correcto, entonces revisa su tamaño. La gráfica de dependencias ignora los archivos bloqueados y de manifiesto individuales que tengan más de 0.5 Mb de tamaño, a menos de que seas un +usuario de {% data variables.product.prodname_enterprise %}. Este procesa hasta 20 archivos de manifiesto o de bloqueo por repositorio predeterminadamente, así que puedes dividir las dependencias en archivos más pequeños en los subdirectorios del repositorio.{% endif %} + +Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omiten de la gráfica de dependencias y no podrán verificar si hay dependencias vulnerables. + +### Further reading + +- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} +- "[Visualizar las perspectivas para tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- " +Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos"

+ + {% endif %} diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/index.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/index.md new file mode 100644 index 0000000000000..ab47c8c19463a --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/index.md @@ -0,0 +1,29 @@ +--- +title: Visualizar datos del repositorio con gráficos +redirect_from: + - /categories/44/articles/ + - /categories/graphs-and-contributions/ + - /categories/graphs/ + - /categories/visualizing-repository-data-with-graphs +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /accessing-basic-repository-data %} + {% link_in_list /about-repository-graphs %} + {% link_in_list /viewing-a-summary-of-repository-activity %} + {% link_in_list /viewing-a-projects-contributors %} + {% link_in_list /viewing-traffic-to-a-repository %} +{% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} + {% link_in_list /visualizing-commits-in-a-repository %} + {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} +{% topic_link_in_list /understanding-connections-between-repositories %} + {% link_in_list /viewing-a-repositorys-network %} + {% link_in_list /listing-the-forks-of-a-repository %} + {% link_in_list /about-the-dependency-graph %} + {% link_in_list /exploring-the-dependencies-of-a-repository %} diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md new file mode 100644 index 0000000000000..8be422d34777d --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md @@ -0,0 +1,28 @@ +--- +title: Detallar las bifurcaciones de un repositorio +intro: El Gráfico de miembros muestra todas las bifurcaciones de un repositorio. +redirect_from: + - /articles/listing-the-forks-of-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las bifurcaciones se detallan alfabéticamente por el nombre de usuario de la persona que bifurcó el repositorio. Puedes hacer clic en el nombre de usuario para ser redirigido a la página de perfil del usuario {% data variables.product.product_name %} o hacer clic en el nombre de la bifurcación para ser redirigido a la bifurcación específica del repositorio. + +{% if currentVersion == "free-pro-team@latest" %} + +![Gráfico de miembros del repositorio](/assets/images/help/graphs/repo_forks_graph_dotcom.png) + +{% else %} + +![Gráfico de miembros del repositorio](/assets/images/help/graphs/repo_members_graph.png) + +{% endif %} + +### Acceder al Gráfico de miembros + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Forks** (Bifurcaciones). ![Pestaña Forks (Bifurcaciones)](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md new file mode 100644 index 0000000000000..cccf34fada1eb --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md @@ -0,0 +1,12 @@ +--- +title: Entender las conexiones entre repositorios +intro: 'Puedes entender mejor las conexiones que existen entre repositorios si ves la red de un repositorio{% if currentVersion == "free-pro-team@latest" %}, los proyectos que dependen de él,{% endif %} y sus bifurcaciones.' +mapTopic: verdadero +redirect_from: + - /articles/understanding-connections-between-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md new file mode 100644 index 0000000000000..1ae89cb62e9e6 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -0,0 +1,45 @@ +--- +title: Ver los colaboradores de un proyecto +intro: 'Puedes ver tanto quién contribuyó con las confirmaciones en un repositorio{% if currentVersion == "free-pro-team@latest" %}, como sus dependencias{% endif %}.' +redirect_from: + - /articles/i-don-t-see-myself-in-the-contributions-graph/ + - /articles/viewing-contribution-activity-in-a-repository/ + - /articles/viewing-a-projects-contributors +product: '{% data reusables.gated-features.repository-insights %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los colaboradores + +Puedes ver los 100 colaboradores principales de un repositorio{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, incluyendo los coautores de las confirmaciones,{% endif %} en la gráfica de colaboradores. Las confirmaciones de fusión y las confirmaciones vacías no se cuentan en las contribuciones para este gráfico. + +{% if currentVersion == "free-pro-team@latest" %} +También puedes ver una lista de personas que han contribuido con las dependencias de Python del proyecto. Para acceder a esta lista de colaboradores de la comunidad, visita `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. +{% endif %} + +### Acceder al gráfico de colaboradores + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Contributors (Colaboradores)**. ![Pestaña de colaboradores](/assets/images/help/graphs/contributors_tab.png) +4. Como alternativa, para ver colaboradores durante un período de tiempo específico, haz clic, después arrastra hasta que se selecciona el período de tiempo. ![Rango de tiempo seleccionado en el gráfico de colaboradores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) + +### Resolución de problemas con colaboradores + +Si no apareces en el gráfico de colaboradores de un repositorio, puede deberse a que: +- No eres uno de los 100 colaboradores principales. +- Tus confirmaciones no se han fusionado en la rama por defecto. +- La dirección de correo electrónico que utilizaste para crear las confirmaciones no está conectada a tu cuenta en {% data variables.product.product_name %}. + +{% tip %} + +**Tip:** Para listar todos los colaboradores de una confirmación en un repositorio, consulta la sección "[Repositorios](/rest/reference/repos#list-contributors)". + +{% endtip %} + +Si todas tus confirmaciones en el repositorio están en ramas que no son por defecto, no estarás en el gráfico de colaboradores. Por ejemplo, las confirmaciones en la rama `gh-pages` no están incluidas en el gráfico excepto que `gh-pages` sea la rama por defecto del repositorio. Para que tus confirmaciones se fusionen en la rama por defecto, puedes crear una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." + +Si la dirección de correo electrónico que utilizaste para crear las confirmaciones no está conectada a tu cuenta en {% data variables.product.product_name %}, tus confirmaciones no se enlazarán a ésta, y no aparecerás en la gráfica de colaboradores. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}" y "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.product_name %}](/articles/adding-an-email-address-to-your-github-account){% endif %}". diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md new file mode 100644 index 0000000000000..9e92732bcb726 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md @@ -0,0 +1,26 @@ +--- +title: Ver la red de un repositorio +intro: 'El gráfico de red muestra el historial de la rama de la red del repositorio completa, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones únicas de la red.' +product: '{% data reusables.gated-features.repository-insights %}' +redirect_from: + - /articles/viewing-a-repository-s-network + - /articles/viewing-a-repositorys-network +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +![Gráfico de red del repositorio](/assets/images/help/graphs/repo_network_graph.png) + +{% tip %} + +**Sugerencia:** para ver ramas antiguas, haz clic y arrastra dentro del gráfico. + +{% endtip %} + +### Acceder al gráfico de la red + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Network (Red)**. ![Pestaña de red](/assets/images/help/graphs/network_tab.png) diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md new file mode 100644 index 0000000000000..f31bfbc1dfcec --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md @@ -0,0 +1,24 @@ +--- +title: Ver un resumen de la actividad de un repositorio +intro: 'Puedes ver un resumen de la actividad de un repositorio a través de Pulse. Pulse incluye una lista de solicitudes de extracción abiertas y fusionadas, propuestas abiertas y cerradas y un gráfico que muestra la actividad de confirmación de los 15 usuarios principales que confirmaron la rama por defecto del proyecto en el [período de tiempo] seleccionado [time period](/articles/viewing-a-summary-of-repository-activity#filtering-by-time).' +product: '{% data reusables.gated-features.repository-insights %}' +redirect_from: + - /articles/viewing-a-summary-of-repository-activity +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los coautores de confirmación están incluidos en el resumen de actividad de confirmación si sus confirmaciones fueron fusionadas dentro de la rama por defecto del repositorio y están en los 15 usuarios principales que contribuyeron en la mayoría de las confirmaciones. + +### Acceder a Pulse + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} + +### Filtrar por tiempo + +Por defecto, Pulse muestra los últimos siete días de actividad del repositorio. Para elegir un período de tiempo diferente, haz clic en el menú desplegable de **Period (Período)** en el ángulo superior derecho del resumen de Pulse. + +![Filtrar la actividad de Pulse por tiempo](/assets/images/help/pulse/pulse_time_filter_dropdown.png) diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md new file mode 100644 index 0000000000000..3e4e061d4ddd1 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md @@ -0,0 +1,27 @@ +--- +title: Ver el tráfico de un repositorio +intro: 'Cualquier persona con acceso de escritura a un repositorio puede ver su tráfico, incluidos los clones completos (no recuperaciones), los visitantes de los últimos 14 días, sitios de referencia y contenido popular en el gráfico de tráfico.' +product: 'Esta gráfica de perspectivas del repositorio se encuentra disponible en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios privados y públicos con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, y {% data variables.product.prodname_ghe_cloud %}.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta las secciones "[Acerca de las gráficas de los repositorios](/articles/about-repository-graphs)" y "[productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)."{% endif %}' +redirect_from: + - /articles/viewing-traffic-to-a-repository +versions: + free-pro-team: '*' +--- + +Puedes desplazarte a los sitios de referencia, excluidos los motores de búsqueda y {% data variables.product.product_name %} propiamente dicho, desde los vínculos donde se hizo la referencia a las rutas específicas. El contenido popular vincula al contenido específico que generó tráfico. + +Los sitios de referencia y el contenido popular se ordenan por vistas y visitantes únicos. Los clones completos y la información del visitante se actualizan cada hora, mientras que las secciones de los sitios de referencia y del contenido popular se actualizan diariamente. Todos los datos en el gráfico de tráfico utiliza la zona horaria UTC+0, sin importar tu ubicación. + +{% tip %} + +**Tip:** Puedes pasar el puntero del mouse sobre un día específico en la gráfica de tráfico para ver los datos exactos para ese día. + +{% endtip %} + +![Gráficos de tráfico del repositorio con una información de herramienta](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png) + +### Acceder al gráfico de tráfico + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, da clic en **Tráfico**. ![Pestaña de tráfico](/assets/images/help/graphs/traffic_tab.png) diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md new file mode 100644 index 0000000000000..fbc79705459af --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md @@ -0,0 +1,23 @@ +--- +title: Ver incorporaciones y eliminaciones al contenido de un repositorio +intro: El gráfico de frecuencia de código muestra las incorporaciones y eliminaciones de contenido de cada semana en el historial de un repositorio. +product: '{% data reusables.gated-features.repository-insights %}' +redirect_from: + - /articles/visualizing-additions-and-deletions-to-content-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% if currentVersion == "free-pro-team@latest" %} + +![Code frequency graph](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png) + +{% endif %} + +### Acceder al gráfico de frecuencia de código + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Code frequency (Frecuencia del código)**. ![Pestaña de frecuencia de código](/assets/images/help/graphs/code_frequency_tab.png) diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md new file mode 100644 index 0000000000000..216c7f2736c98 --- /dev/null +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md @@ -0,0 +1,25 @@ +--- +title: Ver confirmaciones en un repositorio +intro: Puedes ver todas las confirmaciones realizadas a un repositorio en el último año (excluidas las confirmaciones de fusión) en el gráfico de confirmación. +product: '{% data reusables.gated-features.repository-insights %}' +redirect_from: + - /articles/visualizing-commits-in-a-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +El gráfico superior muestra las confirmaciones del año completo por semana. + +![Gráfico anual de confirmaciones de un repositorio](/assets/images/help/graphs/repo_commit_activity_year_graph.png) + +El gráfico inferior muestra la cantidad promedio de confirmaciones por día de la semana para la semana seleccionada. + +![Gráfico semanal de confirmaciones de un repositorio](/assets/images/help/graphs/repo_commit_activity_week_graph.png) + +### Acceder al gráfico de confirmación + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +3. En la barra lateral izquierda, haz clic en **Commits (Confirmaciones)**. ![Pestaña de confirmaciones](/assets/images/help/graphs/commits_tab.png) diff --git a/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000000..7371163e2ee0e --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md @@ -0,0 +1,63 @@ +--- +title: Acerca de los dominios personalizados y las Páginas de GitHub +intro: '{% data variables.product.prodname_pages %} respalda el uso de dominios personalizados o el cambio la raíz de la URL del sitio desde el valor predeterminado, como `octocat.github.io`, para cualquier dominio que posea.' +redirect_from: + - /articles/about-custom-domains-for-github-pages-sites/ + - /articles/about-supported-custom-domains/ + - /articles/custom-domain-redirects-for-your-github-pages-site/ + - /articles/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +--- + +### Dominios personalizados compatibles + +{% data variables.product.prodname_pages %} trabaja con dos tipos de dominios: subdominios y dominios apex. Para conocer un lista de los dominios personalizados compatibles, consulta "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)". + +| Tipo de dominio personalizado compatible | Ejemplo | +| ---------------------------------------- | ------------------ | +| Subdominio `www` | `www.example.com` | +| Subdominio personalizado | `blog.example.com` | +| Dominio apex | `example.com` | + +Puedes configurar uno o ambos tipos de dominios personalizados para tu sitio. Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. Para obtener más información, consulta "[Usar un dominio apex para tu sitio {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)". + +Después de que configuras un dominio personalizado para un usuario o sitio de organización, el dominio personalizado reemplazará a la porción de `.github.io` o `.github.io` de la URL para cualquier sitio de proyecto que pertenezca a la cuenta que no haya configurado un dominio personalizado. Por ejemplo, si el dominio personalizado para tu sitio de usuario es `www.octocat.com`, y tienes un sitio de proyecto sin un dominio personalizado configurado que se publica desde un repositorio denominado `octo-project`, el sitio {% data variables.product.prodname_pages %} para ese repositorio estará disponible en `www.octocat.com/octo-project`. + +### Uso de un subdominio para tu sitio {% data variables.product.prodname_pages %} + +Un subdominio es la parte de una URL antes del dominio raíz. Puedes configurar tu subdominio como `www` o como una sección distinta de tu sitio, como `blog.example.com`. + +Los subdominios se configuran con un registro `CNAME` a través de su proveedor DNS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)". + +#### Subdominios `www` + +Un subdominio `www` es el tipo de subdominio más usado comúnmente. Por ejemplo, `www.example.com` incluue un subdominio `www`. + +Los subdominios `www` son el tipo de dominio personalizado m ás estable porque los subdominios `www` no están afectados por los cambios en las direcciones IP de los servidores de {% data variables.product.product_name %}. Tu sitio también se cargará más rápido porque la protección del ataque de denegación de servicio (DoS) puede implementarse de forma más eficiente. + +#### Subdominios personalizados + +Un subdominio personalizado es un tipo de subdominio que no usa el subdominio `www` estándar. Los subdominios personalizados se utilizan principalmente cuando se necesitan dos secciones distintas de su sitio. Por ejemplo, puedes crear un sitio llamado `blog.example.com` y personalizar esa sección independientemente de `www.example.com`. + +### Uso de un dominio apex para tu sitio {% data variables.product.prodname_pages %} + +Un dominio apex es un dominio personalizado que no contiene un subdominio, como `ejemplo.com`. Los dominios apex también son conocidos como dominios apex base, vacíos, desnudos, o de zona. + +Un dominio apex está configurado con un registro `A`, `ALIAS` o `ANAME` a través de su proveedor DNS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)". + +{% data reusables.pages.www-and-apex-domain-recommendation %} + +### Actualizar dominios personalizados cuando tu sitio de {% data variables.product.prodname_pages %} está inhabilitado + +Si tu sitio {% data variables.product.prodname_pages %} no está habilitado pero tiene configurado un dominio personalizado, inmediatamente deberías actualizar o eliminar tus registros de DNS para evitar el riesgo de una adquisición de dominio. La configuración de tu dominio personalizado con tu proveedor DNS mientras tu sitio está inhabilitado, podría hacer que alguien más aloje un sitio en un o de tus subdominios. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Existen algunos motivos por los que tu sitio pueda estar inhabilitado automáticamente. + +- Si bajaste de categoría de {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, todos los sitios de {% data variables.product.prodname_pages %} que se publicaron actualmente desde repositorios privados en tu cuenta quedarán sin publicar. Para obtener más información, consulta "[Bajar de categoría tu plan de facturación de {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-billing-plan)". +- Si transfieres a un repositorio privado a una cuenta personal que está usando {% data variables.product.prodname_free_user %}, el repositorio perderá acceso a la función de {% data variables.product.prodname_pages %}, y el sitio de {% data variables.product.prodname_pages %} actualmente publicado, quedará sin publicar. Para obtener más información, consulta "[Transferir un repositorio](/articles/transferring-a-repository)". + +### Further reading + +- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000000..267b71e05bd7f --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -0,0 +1,129 @@ +--- +title: Acerca de las Páginas de GitHub y Jekyll +intro: 'Jekyll es un generador de sitios estáticos con soporte integrado para {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/about-jekyll-themes-on-github + - /articles/configuring-jekyll + - /articles/configuring-jekyll-plugins + - /articles/using-syntax-highlighting-on-github-pages + - /articles/files-that-start-with-an-underscore-are-missing + - /articles/sitemaps-for-github-pages/ + - /articles/search-engine-optimization-for-github-pages/ + - /articles/repository-metadata-on-github-pages/ + - /articles/atom-rss-feeds-for-github-pages/ + - /articles/redirects-on-github-pages/ + - /articles/emoji-on-github-pages/ + - /articles/mentions-on-github-pages/ + - /articles/using-jekyll-plugins-with-github-pages/ + - /articles/adding-jekyll-plugins-to-a-github-pages-site/ + - /articles/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de Jekyll + +Jekill es un generador de sitio estático con soporte incorporado para {% data variables.product.prodname_pages %} y un proceso de construcción simplificado. Jekyll toma los archivos Markdown y HTML y crea un sitio web estático completo en función de la opción de diseño. Jekyll soporta Markdown y Liquid, un lenguaje de plantillas que carga contenido dinámico en tu sitio. Para obtener más información, consulta [Jekyll](https://jekyllrb.com/). + +Jekyll no está oficialmente admitido por Windows. Para obtener más información, consulta "[Jekyll en Windows](http://jekyllrb.com/docs/windows/#installation)" en la documentación de Jekyll. + +Recomandamos usar Jekyll con {% data variables.product.prodname_pages %}. Si lo prefieres, puedes usar otros generadores de sitio estático o personalizar tu propio proceso de compilación localmente o en otro servidor. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)". + +### Configurando Jekyll en tu sitio {% data variables.product.prodname_pages %} + +Puedes configurar la mayoría de los parámetros de Jekyll, como los temas y los plugins del sitio, al editar tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll. + +Algunos parámetros de configuración no pueden cambiarse para los sitios {% data variables.product.prodname_pages %} sites. + +``` +lsi: false +safe: true +source: [your repo's top level directory] +incremental: false +highlighter: rouge +gist: + noscript: false +kramdown: + math_engine: mathjax + syntax_highlighter: rouge +``` + +De manera predeterminada, Jekyll no compila archivos o carpetas que: +- están situados en una carpeta denominada `/node_modules` o `/vendor` +- comienza con `_`, `.`, o `#` +- termina con `~` +- están excluidos por el parámetro `exclude` en tu archivo de configuración + +Si deseas que Jekyll procese alguno de estos archivos, puedes usar el parámetro `includes` en tu archivo de configuración. + +### Texto preliminar + +{% data reusables.pages.about-front-matter %} + +Puedes añadir `site.github` a una publicación o página para añadir cualquier metadato de referencias de repositorio a tu sitio. Para obtener más información, consulta "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" en la documentación de metadatos de Jekyll. + +### Temas + +{% data reusables.pages.add-jekyll-theme %} Para obtenerr más información, consulta "[Temas](https://jekyllrb.com/docs/themes/)" en la documentación de Jekyll. + +{% if currentVersion == "free-pro-team@latest" %} +Puedes agregar un tema compatible a tu sitio en +{% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Temas soportados](https://pages.github.com/themes/)" en el sitio {% data variables.product.prodname_pages %} y "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el selector de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)." + +Para usar cualquier otro tema de código abierto de Jekyll que se hospede en {% data variables.product.prodname_dotcom %}, puedes añadirlo manualmente.{% else %} Puedes añadir el tema a tu sitio manualmente. {% endif %} Para obtener más información, consulta {% if currentVersion == "free-pro-team@latest" %}los "[temas hospedados en {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) y {% else %}los "[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %} y {% endif %}la sección"[Añadir un tema a tu sitio de {% data variables.product.prodname_pages %} usando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". + +Puedes sobrescribir cualquiera de los valores por defecto de tu tema editando los archivos del tema. Para obtener más información, consulta la documentación de tu tema y "[Sobrescribir los valores predeterminados del tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" en la documentación de Jekyll. + +### Plugins + +Puedes descargar o crear plugins Jekyll para ampliar la funcionalidad de Jekyll para tu sitio. Por ejemplo, el plugin [jemoji](https://github.com/jekyll/jemoji) te permite usar el emoji con formato {% data variables.product.prodname_dotcom %} en cualquier página de tu sitio del mismo modo que lo harías en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Plugins](https://jekyllrb.com/docs/plugins/)" en la documentación de Jekyll. + +{% data variables.product.prodname_pages %} usa plugins que están habilitados por defecto y no pueden estar inhabilitados: +- [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript) +- [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout) +- [`jekyll-gist`](https://github.com/jekyll/jekyll-gist) +- [`jekyll-github-metadata`](https://github.com/jekyll/github-metadata) +- [`jekyll-optional-front-matter`](https://github.com/benbalter/jekyll-optional-front-matter) +- [`jekyll-paginate`](https://github.com/jekyll/jekyll-paginate) +- [`jekyll-readme-index`](https://github.com/benbalter/jekyll-readme-index) +- [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings) +- [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links) + +Puedes habilitar plugins adicionales al agregar la gema del plugin en los ajustes de `plugins` en tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll. Para conocer la lista de los plugins soportados, consulta "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio {% data variables.product.prodname_pages %}. + +Para obtener información de uso de un plugin específico, consulta la documentación del plugin. + +{% tip %} + +**Sugerencia:** Puedes asegurarte de que estás usando la versión más reciente de todos los plugins al mantener actualizada la gema de {% data variables.product.prodname_pages %}. Para obtener más información, consulta "[Comprobar tus páginas de GitHub localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" y "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio de {% data variables.product.prodname_pages %}. + +{% endtip %} + +{% data variables.product.prodname_pages %} no puede compilar sitios mediante plugins no compatibles. Si deseas usar plugins no compatibles, genera tu sitio localmente y luego sube los archivos estáticos del sitio a {% data variables.product.product_name %}. + +### Resaltado de la sintaxis + +Para facilitar la lectura de tu sitio, los fragmentos de código se resaltan en los sitios de {% data variables.product.prodname_pages %} de la misma manera que se resaltan en {% data variables.product.product_name %}. Para más información sobre como enfatizar sintaxis en {% data variables.product.product_name %}, vea "[Creando y resaltando bloques de código](/articles/creating-and-highlighting-code-blocks)." + +Por defecto, los bloques de código en su sitio serán resaltados por Jekyll. Jekyll utiliza el resaltador de [Rouge](https://github.com/jneen/rouge), compatible con [Pygments](http://pygments.org/). Si especificas Pygments en tu archivo *_config.yml*, el Rouge se utilizará en su lugar. Jekyll no puede usar ningún otro resaltador de sintaxis, y obtendrás una advertencia de compilación de página si especificas otro en tu archivo *_config.yml*. Para más información, vea "[Acerca de los errores de construcción de sitios Jekyll {% data variables.product.prodname_pages %} ](/articles/about-jekyll-build-errors-for-github-pages-sites)." + +Si quieres usar otro resaltador, como `highlight.js`, debes desactivar el resaltador de sintaxis de Jekyll actualizando el archivo de tu proyecto *_config.yml*. + +``` +kramdown: + syntax_highlighter_opts: + disable : true +``` + +Si tu tema no incluye CSS para resaltar la sintaxis, puedes generar la sintaxis de {% data variables.product.prodname_dotcom %} resaltando CSS y añadirlo a tu archivo `style.css` de proyecto. + +```shell +$ rougify style github > style.css +``` + +### Construyendo tu sitio localmente + +{% data reusables.pages.test-locally %} diff --git a/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000000..1ff28543c5c11 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md @@ -0,0 +1,155 @@ +--- +title: Acerca de GitHub Pages +intro: 'Puedes usar {% data variables.product.prodname_pages %} para albergar un sitio web sobre ti mismo, tu organización o tu proyecto directamente desde un repositorio {% data variables.product.product_name %}.' +redirect_from: + - /articles/what-are-github-pages/ + - /articles/what-is-github-pages/ + - /articles/user-organization-and-project-pages/ + - /articles/using-a-static-site-generator-other-than-jekyll/ + - /articles/mime-types-on-github-pages/ + - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio/ + - /articles/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de {% data variables.product.prodname_pages %} + +{% data variables.product.prodname_pages %} es un servicio de alojamiento de sitio estático que toma archivos HTML, CSS y JavaScript directamente desde un repositorio en {% data variables.product.product_name %}, opcionalmente ejecuta los archivos a través de un proceso de complilación y publica un sitio web. Puedes ver ejemplos de sitios de {% data variables.product.prodname_pages %} en la recopilación de ejemplos de [{% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples). + +{% if currentVersion == "free-pro-team@latest" %} +Puedes hospedar tu sitio en +El dominio `github.io` de {% data variables.product.prodname_dotcom %} o en tu propio dominio personalizado. Para obtener más información, consulta "[Utilizar un dominio personalizado con {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". +{% endif %} + +Para empezar, vea "[Creando un sitio {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +Los propietarios de la organización pueden inhabilitar la publicación de +sitios de {% data variables.product.prodname_pages %} desde los repositorios de la organización. Para obtener más información, consulta la sección "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". +{% endif %} + +### Tipos de sitios {% data variables.product.prodname_pages %} + +Existen tres tipos básicos de {% data variables.product.prodname_pages %} sitios: de proyecto, de usuario y de la organización. Los sitios de proyecto están conectados coon un proyecto específico alojado en {% data variables.product.product_name %}, como una biblioteca JavaScript o una colección de recetas. Los sitios de usuario y organización están conectados a una cuenta específica de {% data variables.product.product_name %}. + +Para publicar un sitio de usuario, debes crear un repositorio que pertenezca a tu cuenta de usuario que se llame {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. Para publicar un sitio de organización, debes crear un repositorio que pertenezca a una organización y que se llame {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}A menos de que estés utilizando un dominio personalizado, los sitios de usuario y de organización se encuentran disponibles en `http(s)://.github.io` o `http(s)://.github.io`.{% elsif currentVersion == "github-ae@latest" %}los sitios de organizaciones y usuarios se encuentran disponibles en `http(s)://pages./` o `http(s)://pages./`.{% endif %} + +Los archivos fuente para un sitio de proyecto se almacenan en el mismo repositorio que su proyecto. {% if currentVersion == "free-pro-team@latest" %}A menos de que estés utilizando un dominio personalizado, los sitios de proyecto se encuentran disponibles en `http(s)://.github.io/` o `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Los sitios de proyecto se encuentran disponibles en `http(s)://pages.///` o `http(s)://pages.///`.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Para obtener más información sobre cómo los dominios personalizados afectan a la URL de tu sitio, consulta "[Acerca de los dominios personalizados y {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". +{% endif %} + +Solo puedes crear un sitio de organización o de usuario para cada cuenta en {% data variables.product.product_name %}. Los sitios de proyectos, ya sean propiedad de una cuenta de organización de de usuario, son ilimitados. + +{% if enterpriseServerVersions contains currentVersion %} +La URL en donde tu sitio está disponible dependerá de si habilitaste o no el aislamiento de subdominios para +{% data variables.product.product_location %}. + +| Tipo de sitio | Aislamiento de subdominio habilitado | Aislamiento de subdominio inhabilitado | +| ------------- | ------------------------------------ | -------------------------------------- | +| | | | + Usuario| + +`http(s)://pages./` | `http(s):///pages/` | Organización| `http(s)://pages./` | `http(s):///pages/` | Sitio de proyecto que pertenece a una cuenta de usuario | `http(s)://pages.///` | `http(s):///pages///` Sitio de proyecto que pertenece a una cuenta de organización | `http(s)://pages.///` | `http(s):///pages///` + +Para obtener más información, consulta "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o comunícate con el administrador del sitio. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:** Los repositorios que usan el esquema de nombres `.github.com` tradicional seguirán publicándose, pero los visitantes serán redirigidos desde `http(s)://.github.com` a `http(s)://.github.io`. Si existen tanto un repositorio de `.github.com` como de `.github.io`, solo se publicará el repositorio de `.github.io`. + +{% endnote %} +{% endif %} + +### Publicar fuentes para sitios {% data variables.product.prodname_pages %} + +La fuente de publicación para tu sitio de {% data variables.product.prodname_pages %} es la rama y carpeta en donde se almacenan los archivos fuente de tu sitio. + +{% data reusables.pages.private_pages_are_public_warning %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + +Si la fuente de publicación predeterminada existe en tu repositorio, {% data variables.product.prodname_pages %} publicará automáticamente un sitio desde esta fuente. La fuente de publicación predeterminada para los sitios de usuario y de organización es la raíz de la rama predeterminada para el repositorio. La fuente de publicación predeterminada para los sitios de proyecto es la raíz de la rama `gh-pages`. + +Si quieres mantener los archivos fuente para tu sitio en una ubicación distinta, puedes cambiar la fuente de publicación para tu sitio. Puedes publicar tu sitio desde cualquier rama en el repositorio, ya sea desde la raíz del repositorio en esa rama, `/`, o desde la carpeta de `/docs` en ella. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". + +Si eliges la carpeta `/docs` de cualquier rama como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluyendo el archivo de _CNAME_,{% endif %} de la carpeta `/docs`. {% if currentVersion == "free-pro-team@latest" %} Por ejemplo, cuando editas tu dominio personalizado a través de la configuración de {% data variables.product.prodname_pages %}, dicho dominio escribirá en `/docs/CNAME`. Para más información sobre los archivos _CNAME_, consulta "[Administrar un dominio personalizado para tu sitio {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} + +{% else %} + +La fuente de publicación predeterminada para los sitios de usuario y organización es la rama `principal`. Si el repositorio para tu sitio de usuario u organización tiene una rama `principal`, tu sitio se publicará automáticamente desde esa rama. No puedes elegir una fuente de publicación diferente para sitios de usuario u organización. + +La fuente de publicación predeterminada para un sitio de proyecto es la rama `gh-pages`. Si el repositorio para tu sitio de proyecto tiene una rama `gh-pages`, tu sitio se publicará automáticamente desde esa rama. + +Los sitios del proyecto también pueden publicarse desde la rama `principal` o una carpeta `/docs` en la rama `master`. Para publicar tu sitio desde una de estas fuentes, debes configurar una fuente de publicación diferente. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". + + Si eliges la carpeta `/docs` de la rama `master` como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluyendo el archivo de _CNAME_,{% endif %} de la carpeta `/docs`. {% if currentVersion == "free-pro-team@latest" %} Por ejemplo, cuando editas tu dominio personalizado a través de la configuración de {% data variables.product.prodname_pages %}, dicho dominio escribirá en `/docs/CNAME`. Para más información sobre los archivos _CNAME_, consulta "[Administrar un dominio personalizado para tu sitio {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} + + No puedes publicar tu sitio de proyecto desde ninguna otra rama, aún si la rama predeterminada es diferente a `master` o `gh-pages`. + +{% endif %} + +### Generadores de sitios estáticos + +{% data variables.product.prodname_pages %} publica cualquier archivo estático que subas a tu repositorio. Puedes crear tus propios archivos estáticos o usar un generador de sitios estáticos para que desarrolle tu sitio. También puedes personalizar tu propio proceso de compilación de forma local o en otro servidor. Recomendamos Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %} y un proceso de compilación simplificado. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll)". + +{% data variables.product.prodname_pages %} usará Jekyll para compilar tu sitio por defecto. Si deseas usar un generador de sitio estático diferente a Jekyll, desactiva el proceso de compilación de Jekyll creando un archivo vacío denominado `en la raíz de tu fuente de publicación, luego seguir las instrucciones del generador de sitio estático para desarrollar tu sitio localmente.

+ +

{% data variables.product.prodname_pages %} no soporta idiomas del lado del servidor como PHP, Ruby o Python.

+ +

Guías para usar {% data variables.product.prodname_pages %}

+ +

{% if currentVersion == "free-pro-team@latest" %}

+ +
    +
  • los sitios {% data variables.product.prodname_pages %} creados después del 15 de junio de 2016 y utilizando dominios github.io` se brindan a través de HTTPS. Si creaste tu sitio antes del 15 de junio de 2016, puedes habilitar el soporte HTTPS para el tráfico hasta tu sitio. Para obtener más información, consulta "[Asegurar tu {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)".
    • +- {% data reusables.pages.no_sensitive_data_pages %} +- Tu uso de {% data variables.product.prodname_pages %} está sujeto a los [Términos del servicio de GitHub](/articles/github-terms-of-service/), incluida la prohibición de reventa.
+ +#### Límites de uso +{% endif %} +los sitios {% data variables.product.prodname_pages %} están sujetos a los siguientes límites de uso: + + - Los repositorios de código fuente de {% data variables.product.prodname_pages %} tienen un límite de 1GB.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[¿Cuál es mi cuota de disco?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} + - Los sitios de {% data variables.product.prodname_pages %} publicados no pueden ser mayores a 1 GB. +{% if currentVersion == "free-pro-team@latest" %} + - Los sitios de {% data variables.product.prodname_pages %} tienen un ancho de banda *virtual* de 100GB por mes. + - Los sitios de {% data variables.product.prodname_pages %} tienen un límite *virtual* de 10 compilaciones por hora. + +Si tu sitio excede estas cuotas de uso, es posible que no podamos prestar servicio a tu sitio, o puedes recibir un correo electrónico formal de {% data variables.contact.contact_support %} sugiriendo estrategias para reducir el impacto de tu sitio en nuestros servidores, lo que incluye poner una red de distribución de contenido de un tercero (CDN) al frente de tu sitio, usar las otras características de {% data variables.product.prodname_dotcom %}, como lanzamientos, o mudar a un servicio de alojamiento diferente que pueda satisfacer mejor tus necesidades. + +#### Usos prohibidos + +{% data variables.product.prodname_pages %} no pretende ser un servicio de alojamiento web gratuito ni permite que se use de ese modo para realizar tus negocios en línea, un sitio de comercio electrónico, o cualquier otro sitio web que esté principalmente dirigido a facilitar las operaciones comerciales o brindar software comercial como un servicio (SaaS). + +Además, los sitios de {% data variables.product.prodname_pages %} deben evitar: + + - el contenido o la actividad que sea ilegal o esté prohibida por nuestros [Términos de servicio](/articles/github-terms-of-service/) o [Pautas de la comunidad](/articles/github-community-guidelines/) + - el contenido o la actividad violentas o amenazadoras + - la actividad masiva automatizada excesiva (por ejemplo, envío de spam) + - la actividad que comprometa a los usuarios o los servicios de GitHub + - los esquemas del tipo 'hágase rico rápidamente' + - el contenido sexualmente obsceno + - el contenido que falsea de manera fraudulenta tu identidad o el propósito del sitio +Si tienes cualquier duda sobre si tu uso o intención de uso cae en alguna de estas categorías, por favor contacta a + +{% data variables.contact.contact_support %}. +{% endif %} + +### Tipos MIME en {% data variables.product.prodname_pages %} + +Un tipo MIME es un encabezado que un servidor envía a un navegador, proporcionando información sobre la naturaleza y el formato de los archivos que solicitó el navegador. {% data variables.product.prodname_pages %} soporta más de 750 tipos MIME entre las miles de extensiones de archivo. La lista de los tipos de MIME compatibles se genera desde el [mime-db project](https://github.com/jshttp/mime-db). + +Si bien no puedes especificar los tipos de MIME personalizados en una base por perfil o por repositorio, puedes agregar o modificar los tipos de MIME para usar en {% data variables.product.prodname_pages %}. Para obtener más información, consulta [los lineamientos de contribución de mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). + +### Further reading + +- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) en {% data variables.product.prodname_learning %} +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000000..bc2073bcde1c3 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,59 @@ +--- +title: Acerca de los errores de compilación para sitios de Páginas de GitHub +intro: 'Si Jekyll encuentra un error al compilar tu sitio de {% data variables.product.prodname_pages %} localmente o en {% data variables.product.product_name %}, recibirás un mensaje de error con más información.' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los errores de compilación de Jekyll + +Algunas veces, {% data variables.product.prodname_pages %} no intentará compilar tu sitio después de que subas cambios a la fuente de publicación del mismo.{% if currentVersion == "free-pro-team@latest" %} +- La persona que subió los cambios no ha verificado su dirección de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".{% endif %} +- Estás subiendo con una llave de despliegue. Si deseas automatizar las subidas al repositorio de tu sitio, puedes configurar un usuario de máquina en su lugar. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys#machine-users)". +- Estás usando un servicio CI que no está configurado para compilar tu fuente de publicación. Por ejemplo, Travis CI no compilará la rama `gh-pages` a menos que añadas la rama a una lista de seguridad. Para obtener más información, consulta "[Personalizar la compilación](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" en Travis CI o en la documentación del servicio de CI. + +{% note %} + +**Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. + +{% endnote %} + +Si Jekyll intenta compilar tu sitio y encuentra un error, recibirás un mensaje de error de compilación. Hay dos tipos principales de mensajes de error de construcción de Jekyll. +- Un mensaje de "Aviso de compilación de página" significa que la compilación se ha completado correctamente, pero es posible que debas hacer cambios para prevenir problemas futuros. +- Un mensaje "Page build failed" (Falló la construcción de página) significa que no se pudo completar la compilación. Si Jekyll puede detectar el motivo de la falla, verás un mensaje de error descriptivo. + +Para obtener más información sobre cómo resolver errores de compilación, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)". + +### Ver mensajes de error de construcción de Jekyll + +Recomendamos probar su sitio localmente, lo que le permite ver mensajes de error de compilación en la línea de comandos, y abordar cualquier fallo de construcción antes de presionar los cambios a {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". + +Cuando creas una solicitud de extracción para actualizar tu fuente de publicación en {% data variables.product.product_name %}, puedes ver los mensajes de error de compilación en la pestaña **Checks** (Comprobaciones) de la solicitud de extracción. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". + +Cuando subas los cambios a tu fuente de publicación en {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} intentará compilar tu sitio. Si se produce un error durante la compilación, recibirás un corro electrónico en tu dirección principal de correo electrónico. También recibirás correos electrónicos para advertencias de compilación. {% data reusables.pages.build-failure-email-server %} + +Puedes ver errores de compilación (pero no advertencias de compilación) para tu sitio en {% data variables.product.product_name %} en la pestaña **Settings** (Configuración) del repositorio de tu sitio. + +Puedes configurar un servicio externo como [Travis CI](https://travis-ci.org/) para que muestre mensajes de error después de cada confirmación. + +1. Si no lo has hecho, agrega un archivo denominado _Gemfile_ en la raíz de tu fuente de publicación, con el siguiente contenido: + ``` + source `https://rubygems.org` + gem `github-pages` + ``` + +2. Configura el repositorio de tu sitio para el servicio de comprobación que elijas. Por ejemplo, para usar [Travis CI](https://travis-ci.org/), agrega un archivo denominado _.travis.yml_ en la raíz de tu fuente de publicación, con el siguiente contenido: + ``` + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. Es posible que necesites activar tu repositorio con el servicio de comprobación de terceros. Para obtener más información, consulta la documentación del servicio de comprobación. diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000000..a03c22c8eb642 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,68 @@ +--- +title: Agregar un tema a tu sitio de Páginas de GitHub con Jekyll +intro: Puedes personalizar tu sitio Jekyll agregando y personalizando un tema. +redirect_from: + - /articles/customizing-css-and-html-in-your-jekyll-theme/ + - /articles/adding-a-jekyll-theme-to-your-github-pages-site/ + - /articles/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos de escritura para un repositorio pueden agregar un tema a un sitio de {% data variables.product.prodname_pages %} con Jekyll. + +{% data reusables.pages.test-locally %} + +### Agregar un tema + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. Navega hasta *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Agrega una nueva línea al archivo para el nombre del tema. + - Para utilizar un tema compatible, teclea `theme: THEME-NAME`, reemplazando _THEME-NAME_ con el nombre del tema como se muestra en el archivo README del repositorio del tema. Para conocer la lista de temas compatibles, consulta "[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %}. ![Tema compatible en el archivo de configuración](/assets/images/help/pages/add-theme-to-config-file.png) + - Para usar cualquier otro tema de Jekyll alojado en {% data variables.product.prodname_dotcom %}, escribe `remote_theme: THEME-NAME`, reemplazando THEME-NAME por el nombre del tema, tal como se muestra en el README del repositorio del tema. ![Tema no compatible en el archivo de configuración](/assets/images/help/pages/add-remote-theme-to-config-file.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Personalizar el CSS de tu tema + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +1. Crea un archivo nuevo denominado _/assets/css/style.scss_. +2. Agrega el siguiente contenido en la parte superior del archivo: + ``` + --- + --- + + @import "{{ site.theme }}"; + ``` +3. Agrega cualquier CSS o Sass personalizado que quieras (incluidas importaciones) inmediatamente después de la línea `@import`. + +### Personalizar el diseño HTML de tu tema + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. En {% data variables.product.prodname_dotcom %}, desplázate hasta el repositorio fuente de tu tema. Por ejemplo, el repositorio fuente para Minima es https://github.com/jekyll/minima. +2. En la carpeta *_layouts*, desplázate hasta el archivo _default.html_ de tu tema. +3. Copia los contenidos del archivo. +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. Crea un archivo denominado *_layouts/default.html*. +7. Pega el contenido del diseño personalizado que copiaste anteriormente. +8. Personaliza el diseño como desees. + +### Further reading + +- "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000000..b806021667573 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,42 @@ +--- +title: Agregar un tema a tu sitio de Páginas de GitHub con el selector de tema +intro: 'Puedes añadir un tema a tu sitio de {% data variables.product.prodname_pages %} para personalizar la apariencia de tu sitio.' +redirect_from: + - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser/ + - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser/ + - /articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +--- + +Las personas con permisos de administración para un repositorio pueden usar el selector de temas para agregar un tema al sitio de {% data variables.product.prodname_pages %}. + +### Acerca del selector de temas + +El selector de temas agrega un tema de Jekyll a tu repositorio. Para obtener más información acerca de Jekyll, consulta "[Acerca de las {% data variables.product.prodname_pages %} y Jekyll](/articles/about-github-pages-and-jekyll)". + +La forma en que funciona el selector de temas depende de si tu repositorio es público o privado. + - Si las {% data variables.product.prodname_pages %} ya están habilitadas para tu repositorio, el selector de temas agregará tu tema a la fuente de publicación actual. + - Si tu repositorio es público y {% data variables.product.prodname_pages %} se encuentra inhabilitado para éste, mediante el selector de temas podrás habilitar {% data variables.product.prodname_pages %} y configurar la rama predeterminada como tu fuente de publicación. + - Si tu repositorio es público, y las {% data variables.product.prodname_pages %} están inhabilitadas para tu repositorio, debes habilitar las {% data variables.product.prodname_pages %} configurando una fuente de publicación antes de poder usar el selector de temas. + +Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". + +Si antes agregaste manualmente un tema de Jekyll a tu repositorio, puede que esos archivos se apliquen incluso después de que uses el selector de temas. Para evitar conflictos, elimina todas las carpetas y archivos de temas agregados manualmente antes de usar el selector de temas. Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". + +### Agregar un tema con el selector de temas + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "{% data variables.product.prodname_pages %}", haz clic en **Choose a theme** (Elegir un tema) o **Change theme** (Cambiar tema). ![Elija un botón del tema](/assets/images/help/pages/choose-a-theme.png) +4. Para elegir un tema, haz clic en el tema que quieras y luego haz clic en **Select theme** (Seleccionar tema). ![Opciones de temas y botón Select theme (Seleccionar tema)](/assets/images/help/pages/select-theme.png) +5. Puede que se te solicite que edites el archivo *README.md* de tu sitio. + - Para editar el archivo más tarde, haz clic en **Cancel** (Cancelar). ![Enlace de cancelación al editar un archivo](/assets/images/help/pages/cancel-edit.png) + - Para editar el archivo ahora, consulta "[Editar archivos en tu repositorio](/articles/editing-files-in-your-repository/)". + +El tema elegido se aplicará automáticamente a los archivos markdown de tu repositorio. Para aplicar el tema a los archivos HTML de tu repositorio, debes agregar el texto preliminar de YAML que especifica un diseño para cada archivo. Para obtener más información, consulta "[Texto preliminar](https://jekyllrb.com/docs/front-matter/)" en el sitio de Jekyll. + +### Further reading + +- [Temas](https://jekyllrb.com/docs/themes/) en el sitio de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000000..7393b9fada18c --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,69 @@ +--- +title: Agregar contenido a tu sitio de Páginas de GitHub con Jekyll +intro: 'Puedes agregar una página nueva o publicar tu sitio Jekyll a tu sitio en las {% data variables.product.prodname_pages %}.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos de escritura para un repositorio pueden agregar contenido a un sitio de {% data variables.product.prodname_pages %} con Jekyll. + +### Acerca del contenido en sitios Jekyll + +Antes de poder agregar contenido a un sitio Jekyll en las {% data variables.product.prodname_pages %}, debes crear un sitio Jekyll. Para obtener más información, consulta "[Crear un sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". + +Los principales tipos de contenido para sitios Jekyll son páginas y publicaciones. Una página es para el contenido independiente que no está asociado con una fecha específica, como una página "Acerca de". El sitio Jekyll predeterminado contiene un archivo denominado `about.md`, que se representa como una página en tu sitio en `TU-SITE-URL/about`. Puedes editar los contenidos de ese archivo para personalizar tu página "Acerca de" y usar la página "Acerca de" como plantilla para crear páginas nuevas. Para obtener más información, consulta "[Páginas](https://jekyllrb.com/docs/pages/)" en la documentación de Jekyll. + +Una publicación es una entrada de blog. El sitio Jekyll predeterminado contiene un directorio denominado `_posts` que contiene un archivo de publicación predeterminada. Puedes editar los contenidos de esa publicación y usar la publicación predeterminada como plantilla para crear publicaciones nuevas. Para obtener más información, consulta "[Publicaciones](https://jekyllrb.com/docs/posts/)" en la documentación de Jekyll. + +Tu tema incluye diseños predeterminados, inclusiones y hojas de estilos que se aplicarán automáticamente a las páginas y publicaciones nuevas de tu sitio; sin embargo, puedes reemplazar cualquiera de estas formas predeterminadas. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll#themes)". + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### Agregar una página nueva a tu sitio + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. En la raíz de tu fuente de publicación, crea un archivo nuevo para tu página denominado _PAGE-NAME.md_, reemplazando _PAGE-NAME_ por un nombre de archivo significativo para la página. +4. Agrega el siguiente texto preliminar de YAML a la parte superior del archivo, reemplazando _PAGE TITLE_ por el título de la página y _URL-PATH_ por la ruta que quieras para la URL de la página. Por ejemplo, si la URL base de tu sitio es `https://octocat.github.io` y tu _URL-PATH_ es `/about/contact/`, tu página se encontrará en `https://octocat.github.io/about/contact`. + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. Debajo del texto preliminar, agrega contenido para tu página. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Agregar una publicación nueva a tu sitio + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Desplázate hasta el directorio `_posts`. +4. Crea un archivo nuevo denominado _YYYY-MM-DD-NAME-OF-POST.md_, reemplazando _YYY-MM-DD_ por la fecha de tu publicación y _NAME-OF-POST_ por el nombre de tu publicación. +4. Agrega el siguiente texto preliminar de YAML en la parte superior del archivo, reemplazando _POST TITLE_ por el título de la publicación, _YYYYY-MM-DD hh:mm:ss -0000_ por la fecha y hora de la publicación, y _CATEGORY-1_ y _CATEGORY-2_ por tantas categorías como las que quieras para tu publicación. + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. Debajo del texto preliminar, agrega contenido para tu publicación. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + +### Pasos siguientes + +{% data reusables.pages.add-jekyll-theme %} Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". diff --git a/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000000..2ebfa9cda059e --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,18 @@ +--- +title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub +intro: 'Puedes personalizar el nombre de dominio de tu sitio de {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/tips-for-configuring-an-a-record-with-your-dns-provider/ + - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site/ + - /articles/configuring-an-a-record-with-your-dns-provider/ + - /articles/using-a-custom-domain-with-github-pages/ + - /articles/tips-for-configuring-a-cname-record/ + - /articles/setting-up-a-custom-domain-with-pages/ + - /articles/setting-up-a-custom-domain-with-github-pages/ + - /articles/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +mapTopic: verdadero +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000000..8d0bd8650a6b8 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Configurar una fuente de publicación para tu sitio de Páginas de GitHub +intro: 'Si usas la fuente de publicación predeterminada para tu sitio de {% data variables.product.prodname_pages %}, tu sitio se publicará automáticamente. También puedes elegir publicar tu {% if currentVersion ver_lt "enterprise-server@2.23" %} sitio de proyecto{% endif %}desde una carpeta o rama diferente.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'Las personas con permisos de administrador o de mantenedor para un repositorio pueden configurar una fuente de publicación para un sitio de {% data variables.product.prodname_pages %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". + +### Elegir una fuente de publicación + +Antes de que configures una fuente de publicación, asegúrate de que la rama{% if currentVersion ver_lt "enterprise-server@2.23" %} o carpeta{% endif %} que quieras utilizar como tal ya exista en tu repositorio.{% if currentVersion ver_lt "enterprise-server@2.23" %} Por ejemplo, antes de que puedas publicar tu sitio de proyecto desde la carpeta `/docs` en la rama `master` de tu repositorio, ya sea algún colaborador o tú mismo deberán crear una carpeta de `/docs` enla rama predeterminada `master` de tu repositorio.{% endif %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Debajo de "{% data variables.product.prodname_pages %}", utiliza el menú desplegable de **Ninguno** o de **Rama** y selecciona una fuente de publicación. ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) +4. Opcionalmente, utiliza el menú desplegable para seleccionar una carpeta para tu fuente de publicación. ![Menú desplegable para seleccionar una carpeta para una fuente de publicación](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Haz clic en **Save ** (guardar). ![Botón para guardar los cambios en la configuración de la fuente de publicación](/assets/images/help/pages/publishing-source-save.png) + {% else %} +3. Debajo de " +{% data variables.product.prodname_pages %}", usa el menú desplegable de **Fuente** y selecciona una fuente de publicación. + ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### Solución de problemas de publicación con tu sitio de {% data variables.product.prodname_pages %} + +{% data reusables.pages.admin-must-push %} + +Si eliges la carpeta `docs` en {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}cualquier rama {% else %}la rama `master`{% endif %} como tu fuente de publicación, y eliminas la carpeta de `/docs` de esta rama en tu repositorio posteriormente, tu sitio no compilará y obtendrás un mensaje de error para dicha compilación debido a que falta la carpeta `/docs`. Para obtener más información, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000000..992cbab2a07f4 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,32 @@ +--- +title: Crear una página 404 personalizada para tu sitio de Páginas de GitHub +intro: Puedes mostrar una página personalizada de error 404 cuando se intente acceder a páginas que no existen en tu sitio. +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. En el campo para el nombre de archivo, escribe `404.html` o `404.md`. ![Campo File name (Nombre de archivo)](/assets/images/help/pages/404-file-name.png) +4. Si denominaste tu archivo `404.md`, agrega el siguiente texto preliminar de YAML al comienzo del archivo: + ``` + --- + permalink: /404.html + --- + ``` +5. Debajo del texto preliminar de YAML, si aparece, agrega el contenido que quieras mostrar en tu página 404. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Further reading + +- [Texto preliminar](http://jekyllrb.com/docs/frontmatter) en la documentación de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000000..b6a0a4ae7ea27 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,107 @@ +--- +title: Crear un sitio de Páginas de GitHub con Jekyll +intro: 'Puedes usar Jekyll para crear un sitio de {% data variables.product.prodname_pages %} en un repositorio nuevo o existente.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll +permissions: 'Las personas con permisos de administración para un repositorio pueden crear un sitio de {% data variables.product.prodname_pages %} con Jekyll.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Prerrequisitos + +Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product.prodname_pages %}, debes instalar Jekyll y Git. Para obtener más información, consulta [Instalación](https://jekyllrb.com/docs/installation/) en la documentación de Jekyll y "[Configurar Git](/articles/set-up-git)". + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Crear un repositorio para tu sitio + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} + +### Crear tu sitio + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Si aún no tienes una copia local de tu repositorio, desplázate hasta la ubicación en la que quieras almacenar los archivos fuente de tu sitio y reemplaza _PARENT-FOLDER_ por la carpeta que quieras que contenga la carpeta para su repositorio. + ```shell + $ cd PARENT-FOLDER + ``` +3. Si aún no lo has hecho, inicia un repositorio de Git local reemplazando _REPOSITORY-NAME_ por el nombre de tu repositorio. + ```shell + $ git init REPOSITORY-NAME + > Initialized empty Git repository in /Users/octocat/my-site/.git/ + # Creates a new folder on your computer, initialized as a Git repository + ``` + 4. Cambio los directorios para el repositorio. + ```shell + $ cd REPOSITORY-NAME + # Changes the working directory + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + Por ejemplo, si decides publicar tu sitio desde la carpeta `docs` de la rama predeterminada, crea y cambia los directorios para la carpeta `docs`. + ```shell + $ mkdir docs + # Creates a new folder called docs + $ cd docs + ``` + Si decides publicar tu sitio desde la rama `gh-pages`, crea y controla la rama `gh-pages`. + ```shell + $ git checkout --orphan gh-pages + # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch + ``` + 7. Para crear un sitio Jekyll nuevo, usa el comando `jekyll new` y reemplaza _VERSION_ por la versión de dependencias actual para Jekyll. Para obtener más información, consulta "[Versiones de dependencias](https://pages.github.com/versions/)" en el sitio de {% data variables.product.prodname_pages %}. + - Si instalaste Bundler: + ```shell + $ bundle exec jekyll VERSION new . + # Creates a Jekyll site in the current directory + ``` + - Si no tienes instalado Bundler: + ```shell + $ jekyll VERSION new . + # Creates a Jekyll site in the current directory + ``` +8. Abre el Gemfile que se creó y sigue las instrucciones de los comentarios del Gemfile para usar las {% data variables.product.prodname_pages %}. ![Instrucciones para actualizar Gemfile](/assets/images/help/pages/gemfile-instructions.png) +9. Actualiza la línea `gem "github-pages"` para que luzca así, reemplazando _VERSION_ por la versión de dependencias actual para `github-pages`. Para obtener más información, consulta "[Versiones de dependencias](https://pages.github.com/versions/)" en el sitio de {% data variables.product.prodname_pages %}. +```shell +gem "github-pages", "~> VERSION", group: :jekyll_plugins +``` +10. Guarda y cierra el Gemfile. +11. De forma opcional, prueba tu sitio localmente. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". +12. Agrega tu repositorio de {% data variables.product.product_name %} como remoto, reemplazando {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ con el nombre de host de tu aplicativo,{% endif %} _USER_ con la cuenta a la que pertenece el repositorio{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} y _REPOSITORY_ con el nombre del repositorio. +```shell +{% if currentVersion == "free-pro-team@latest" %} +$ git remote add origin https://github.com/USER/REPOSITORY.git +{% else %} +$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git +{% endif %} +``` +13. Sube el repositorio a {% data variables.product.product_name %}, reemplazando _BRANCH_ por el nombre de la rama en la que estás trabajando. + ```shell + $ git push -u origin BRANCH + ``` +{% data reusables.pages.configure-publishing-source %} +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Pasos siguientes + +Para agregar una página o publicación nueva a tu sitio, consulta "[Agregar contenido a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)". + +{% data reusables.pages.add-jekyll-theme %} Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000000..aeba92786eead --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,56 @@ +--- +title: Crear un sitio de Páginas de GitHub +intro: 'Puede crear un sitio de {% data variables.product.prodname_pages %} en un repositorio nuevo o existente.' +redirect_from: + - /articles/creating-pages-manually/ + - /articles/creating-project-pages-manually/ + - /articles/creating-project-pages-from-the-command-line/ + - /articles/creating-project-pages-using-the-command-line/ + - /articles/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Crear un repositorio para tu sitio + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} + +### Crear tu sitio + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. Si ya existe la fuente de publicación que elegiste, desplázate hasta la fuente de publicación. Si la fuente de publicación que elegiste no existe, crear la fuente de publicación. +4. En la raíz de la fuente de publicación, crea un archivo nuevo denominado `index.md` que contenga el contenido que quieras mostrar en la página principal de tu sitio. +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Pasos siguientes + +Puedes agregar más páginas a tu sitio creando más archivos nuevos. Cada archivo estará disponible en tu sitio en la misma estructura de directorios que tu fuente de publicación. Por ejemplo, si la fuente de publicación para tu sitio de proyecto es la rama `gh-pages`, y creas un archivo nuevo que se llama `/about/contact-us.md` en la rama `gh-pages`, el archivo estará disponible en {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. + +También puedes agregar un tema para personalizar la apariencia de tu sitio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el seleccionador de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} utilizando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}". + +Para personalizar aún más tu sitio, puedes usar Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll)". + +### Further reading + +- "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" +- "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md new file mode 100644 index 0000000000000..cfa0f90ba317d --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md @@ -0,0 +1,15 @@ +--- +title: Comenzar con Páginas de GitHub +intro: 'Puedes configurar un sitio básico de {% data variables.product.prodname_pages %} para ti, para tu organización o para tu proyecto.' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/working-with-github-pages/index.md b/translations/es-ES/content/github/working-with-github-pages/index.md new file mode 100644 index 0000000000000..e64dac4e1d1fd --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/index.md @@ -0,0 +1,44 @@ +--- +title: Trabajar con Páginas de GitHub +shortTitle: GitHub Pages +intro: 'Puedes crear un sitio web directamente desde un repositorio de {% data variables.product.product_name %}.' +redirect_from: + - /categories/20/articles/ + - /categories/95/articles/ + - /categories/github-pages-features/ + - /pages/ + - /categories/96/articles/ + - /categories/github-pages-troubleshooting/ + - /categories/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /getting-started-with-github-pages %} + {% link_in_list /about-github-pages %} + {% link_in_list /creating-a-github-pages-site %} + {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} + {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} + {% link_in_list /securing-your-github-pages-site-with-https %} + {% link_in_list /using-submodules-with-github-pages %} + {% link_in_list /unpublishing-a-github-pages-site %} +{% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} + {% link_in_list /about-github-pages-and-jekyll %} + {% link_in_list /creating-a-github-pages-site-with-jekyll %} + {% link_in_list /testing-your-github-pages-site-locally-with-jekyll %} + {% link_in_list /adding-content-to-your-github-pages-site-using-jekyll %} + {% link_in_list /setting-a-markdown-processor-for-your-github-pages-site-using-jekyll %} + {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} + {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} + {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} +{% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} + {% link_in_list /about-custom-domains-and-github-pages %} + {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} + {% link_in_list /troubleshooting-custom-domains-and-github-pages %} diff --git a/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000000..f6f7206dd803d --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,92 @@ +--- +title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub +intro: 'Puedes configurar o actualizar determinados registros DNS y las configuraciones de tu repositorio para que apunten el dominio predeterminado de tu sitio de {% data variables.product.prodname_pages %} a un dominio personalizado.' +redirect_from: + - /articles/quick-start-setting-up-a-custom-domain/ + - /articles/setting-up-an-apex-domain/ + - /articles/setting-up-a-www-subdomain/ + - /articles/setting-up-a-custom-domain/ + - /articles/setting-up-an-apex-domain-and-www-subdomain/ + - /articles/adding-a-cname-file-to-your-repository/ + - /articles/setting-up-your-pages-site-repository/ + - /articles/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +--- + +Las personas con permisos de administración para un repositorio pueden configurar un dominio personalizado para un sitio de {% data variables.product.prodname_pages %}. + +### Acerca de la configuración de dominios personalizados + +Asegúrate de agregar tu dominio personalizado al sitio de {% data variables.product.prodname_pages %} antes de configurar el dominio personalizado con tu proveedor DNS. Configurar tu dominio personalizado con tu proveedor DNS sin agregar tu dominio personalizado a {% data variables.product.product_name %} podría dar como resultado que alguien aloje un sitio en uno de tus subdominios. + +{% windows %} + +El comando `dig`, que se puede usar para verificar la correcta configuración de los registros DNS, no está incluido en Windows. Antes de poder verificar que tus registros DNS estén configurados correctamente, debes instalar [BIND](https://www.isc.org/bind/). + +{% endwindows %} + +{% note %} + +**Nota:** Los cambios DNS pueden tardar hasta 24 horas en propagarse. + +{% endnote %} + +### Configurar un subdominio + +Para configurar un `www` o un subdominio personalizado, como `www.example.com` o `blog.example.com`, debes crear un archivo _CNAME_ en el repositorio de tu sitio y configurar un registro `CNAME` con tu proveedor DNS. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.save-custom-domain %} +5. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte tu subdominio al dominio predeterminado de tu sitio. Por ejemplo, si quieres usar el subdominio `www.example.com` para tu sitio de usuario, crea un registro `CNAME` que apunte `www.example.com` a `.github.io`. Si quieres utilizar el subdominio `www.anotherexample.com` para el sitio de tu organización, crea un registro de `CNAME` que apunte a `www.anotherexample.com` hacia `.github.io`. El registro `CNAME` siempre deberá apuntar hacia `.github.io` o `.github.io`, excluyendo el nombre del repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _WW.EXAMPLE.COM_ por tu subdominio. +```shell + $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd + > ;WWW.EXAMPLE.COM. IN A + > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io. + > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER . + > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1 +``` +{% data reusables.pages.build-locally-download-cname %} +{% data reusables.pages.enforce-https-custom-domain %} + +### Configurar un dominio apex + +Para configurar un dominio apex, como `example.com`, debes configurar un archivo _CNAME_ en tu repositorio de {% data variables.product.prodname_pages %} y un registro `ALIAS`, `ANAME` o `A` con tu proveedor DNS. + +{% data reusables.pages.www-and-apex-domain-recommendation %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.save-custom-domain %} +5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. {% data reusables.pages.contact-dns-provider %} + - Para crear un registro `ALIAS` o `ANAME`, apunta tu dominio apex al dominio predeterminado de tu sitio. {% data reusables.pages.default-domain-information %} + - Para crear un registro `A`, apunta tu dominio apex a las direcciones IP para {% data variables.product.prodname_pages %}. + ```shell + 185.199.108.153 + 185.199.109.153 + 185.199.110.153 + 185.199.111.153 + ``` + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _EXAMPLE.COM_ por tu dominio apex. Confirma que los resultados coincidan con las direcciones IP de las {% data variables.product.prodname_pages %} que aparecen arriba. + ```shell + $ dig EXAMPLE.COM +noall +answer + > EXAMPLE.COM 3600 IN A 185.199.108.153 + > EXAMPLE.COM 3600 IN A 185.199.109.153 + > EXAMPLE.COM 3600 IN A 185.199.110.153 + > EXAMPLE.COM 3600 IN A 185.199.111.153 + ``` +{% data reusables.pages.build-locally-download-cname %} +{% data reusables.pages.enforce-https-custom-domain %} + +### Further reading + +- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/es-ES/content/github/working-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000000..27afbb999277d --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,53 @@ +--- +title: Asegurar tu sitio de Páginas de GitHub con HTTPS +intro: 'HTTPS agrega una capa de encriptación que evita que otros se entrometan o manipulen el tráfico en tu sitio. Puedes aplicar HTTPS en tu sitio {% data variables.product.prodname_pages %} para redirigir de forma transparente todas las solicitudes de HTTP a HTTPS.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +--- + +Las personas con permisos de administración para un repositorio pueden aplicar HTTPS para un sitio de {% data variables.product.prodname_pages %}. + +### Acerca de HTTPS y de las {% data variables.product.prodname_pages %} + +Todos los sitios {% data variables.product.prodname_pages %}, incluidos los sitios que están correctamente configurados con un dominio personalizado, admiten HTTPS y la aplicación de HTTPS. Para obtener más información acerca de los dominios personalizados, consulta "[Acerca de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" y "[Solución de problemas de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)". + +La aplicación de HTTPS es necesaria para los sitios {% data variables.product.prodname_pages %} utilizando un dominio `github.io` que fueron creados después del 15 de junio de 2016. Si creaste tu sitio antes del 15 de junio de 2016, puedes habilitar de forma manual la aplicación de HTTPS. + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### Aplicar HTTPS en tu sitio {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "{% data variables.product.prodname_pages %}", selecciona **Enforce HTTPS** (Aplicar HTTPS). ![Aplicar casilla de verificación de HTTPS](/assets/images/help/pages/enforce-https-checkbox.png) + +### Resolver problemas con contenido mixto + +Si habilitas HTTPS para tu sitio de {% data variables.product.prodname_pages %}, pero el HTML de tu sitio sigue referenciando imágenes, CSS o JavaScript a través de HTTP, significa que tu sitio está ofreciendo *contenido mixto*. Ofrecer contenido mixto puede hacer que tu sitio sea menos seguro y generar problemas al cargar activos. + +Para eliminar el contenido mixto de tu sitio, asegúrate de que todos tus activos se ofrezcan mediante HTTPS cambiando `http://` por `https://` en el HTML de tu sitio. + +Normalmente, los activos se encuentran en las siguientes ubicaciones: +- Si tu sitio usa Jekyll, es probable que tus archivos HTML se encuentren en la carpeta de *_layouts*. +- Habitualmente, CSS se encuentra en la sección `` de tu archivo HTML. +- Habitualmente, JavaScript se encuentra en la sección `` o simplemente antes de la etiqueta de cierre ``. +- Las imágenes se suelen encontrar en la sección ``. + +{% tip %} + +**Sugerencia:** Si no puedes encontrar tus activos en los archivos fuente de tu sitio, prueba buscando los archivos fuente de tu sitio para `http` en el editor de texto o en {% data variables.product.product_name %}. + +{% endtip %} + +#### Ejemplos de activos referenciados en un archivo HTML + +| Tipo de activo | HTTP | HTTPS | +|:--------------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| Image | `Logo` | `Logo` | diff --git a/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000000..8e3bbe1d090f8 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,33 @@ +--- +title: Configurar un procesador Markdown para tu sitio de páginas de GitHub usando Jekyll +intro: 'Puedes elegir un procesador Markdown para determinar la manera en que Markdown se representa en tu sitio de {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/migrating-your-pages-site-from-maruku/ + - /articles/updating-your-markdown-processor-to-kramdown/ + - /articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Las personas con permisos de escritura para un repositorio pueden configurar el procesador Markdown para un sitio de {% data variables.product.prodname_pages %}. + +{% data variables.product.prodname_pages %} es compatible con dos procesadores de Markdown: [kramdown](http://kramdown.gettalong.org/) y el procesador extendido de [CommonMark](https://commonmark.org/) de {% data variables.product.prodname_dotcom %}, el cual se utiliza para interpretar el lenguaje de marcado enriquecido de {% data variables.product.prodname_dotcom %} a través de {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." + +Puedes usar Flavored Markdown de {% data variables.product.prodname_dotcom %} con cualquiera de los procesadores, pero solamente nuestro procesador CommonMark siempre encontrará los resultados que ves en {% data variables.product.product_name %}. + +{% data reusables.pages.navigate-site-repo %} +2. En tu repositorio, navega hasta el archivo *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Encuentra la línea que comienza con `markdown:` y cambia el valor a `kramdown` o `GFM`. ![Configuración Markdown en config.yml](/assets/images/help/pages/config-markdown-value.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Further reading + +- [Documentación de kramdown](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) diff --git a/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000000..6c707304a38ba --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md @@ -0,0 +1,15 @@ +--- +title: Configurar un sitio de Páginas de GitHub con Jekyll +intro: 'Puedes usar Jekyll, un generador de sitio estático popular, para personalizar aún más tu sitio de {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/using-jekyll-with-pages/ + - /articles/using-jekyll-as-a-static-site-generator-with-github-pages + - /articles/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000000..7362c9c95b1fd --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,58 @@ +--- +title: Probar tu sitio de Páginas de GitHub localmente con Jekyll +intro: 'Puedes compilar tu sitio de {% data variables.product.prodname_pages %} localmente para previsualizar y probar los cambios en tu sitio.' +redirect_from: + - /articles/setting-up-your-pages-site-locally-with-jekyll/ + - /articles/setting-up-your-github-pages-site-locally-with-jekyll/ + - /articles/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cualquier persona con permisos de lectura para un repositorio puede probar un sitio de {% data variables.product.prodname_pages %} localmente. + +### Prerrequisitos + +Antes de que puedas usar Jekyll para probar un sitio, debes hacer lo siguiente: + - Instalar [Jekyll](https://jekyllrb.com/docs/installation/). + - Crear un sitio de Jekyll. Para obtener más información, consulta "[Crear un sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Construyendo tu sitio localmente + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Ejecuta tu sitio Jekyll de forma local. + ```shell + $ bundle exec jekyll serve + > Configuration file: /Users/octocat/my-site/_config.yml + > Source: /Users/octocat/my-site + > Destination: /Users/octocat/my-site/_site + > Incremental build: disabled. Enable with --incremental + > Generating... + > done in 0.309 seconds. + > Auto-regeneration: enabled for '/Users/octocat/my-site' + > Configuration file: /Users/octocat/my-site/_config.yml + > Server address: http://127.0.0.1:4000/ + > Server running... press ctrl-c to stop. + ``` +3. Para previsualizar tu sitio, en tu navegador web, navega hasta `http://localhost:4000`. + +### Actualizar la gema de {% data variables.product.prodname_pages %} + +Jekyll es un proyecto de código abierto activo que se actualiza de manera frecuente. Si la gema de `github-pages` de tu computadora está desactualizada con respecto a la gema de `github-pages` del servidor de {% data variables.product.prodname_pages %}, tu sitio puede verse diferente cuando se compile localmente en comparación a cómo se vea cuando se publique en {% data variables.product.product_name %}. Para evitar esto, actualiza de manera regular la gema de `github-pages` en tu computadora. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Actualiza la gema de `github-pages`. + - Si instalaste Bundler, ejecuta `bundle update github-pages`. + - Si no tienes instalado Bundler, ejecuta `gem update github-pages`. + +### Further reading + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) en la documentación de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000000..44e311ca8daf8 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,60 @@ +--- +title: Solucionar problemas de dominios personalizados y Páginas de GitHub +intro: 'Puedes buscar errores comunes para resolver los problemas que existan con los dominios personalizados o HTTPS para tu sitio de {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/my-custom-domain-isn-t-working/ + - /articles/custom-domain-isn-t-working/ + - /articles/troubleshooting-custom-domains/ + - /articles/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +--- + +### Errores _CNAME_ + +Los dominios personalizados se almacenan en un archivo _CNAME_ en la raíz de tu fuente de publicación. Puedes agregar o actualizar este archivo a través de la configuración del repositorio o manualmente. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Para que tu sitio se represente en el dominio correcto, asegúrate de que el archivo _CNAME_ aún exista en el repositorio. Por ejemplo, muchos generadores de sitios estáticos realizan empujes forzados a tu repositorio, que pueden sobrescribir el archivo _CNAME_ que se agregó a tu repositorio cuando configuraste tu dominio personalizado. Si compilas tu sitio localmente y subes los archivos generados a {% data variables.product.product_name %}, asegúrate de extraer primero la confirmación que agregó el archivo _CNAME_ a tu repositorio local. De este modo, el archivo se incluirá en la compilación. + +Luego, asegúrate de que el archivo _CNAME_ tenga el formato correcto. + +- El nombre de archivo _CNAME_ debe estar todo en mayúsculas. +- El archivo _CNAME_ puede contener solo un dominio. Para apuntar múltiples dominios a tu sitio, debes configurar un redireccionamiento a través de tu proveedor DNS. +- La entrada _CNAME_ debe ser el dominio solo. Por ejemplo, `www.example.com`,`blog.example.com` o `example.com`. +- La entrada _CNAME_ solo se puede usar una vez en {% data variables.product.product_name %}. Por ejemplo, si el archivo _CNAME_ de otro repositorio contiene `example.com`, no puedes usar `example.com` en el archivo _CNAME_ para tu repositorio. + +### Error de configuración DNS + +Si tienes problemas para apuntar el dominio predeterminado para tu sitio a tu dominio personalizado, contáctate con tu proveedor DNS. + +También puedes probar si los registros DNS de tu dominio personalizado están configurados correctamente. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +### Nombres de dominios personalizados que no son compatibles + +Si tu dominio personalizado no es compatible, puede que debas cambiar tu dominio a un dominio compatible. También te puedes contactar con tu proveedor DNS para ver si ofrece servicios de reenvío para los nombres de dominio. + +Asegúrate de que en tu sitio no ocurra lo siguiente: +- Uso de más de un dominio apex. Por ejemplo, `example.com` y `anotherexample.com`. +- Uso de más de un subdominio `www`. Por ejemplo, `www.example.com` y `www.anotherexample.com`. +- Uso de un dominio apex y de un subdominio personalizado. Por ejemplo, `example.com` y `docs.example.com`. + +{% data reusables.pages.wildcard-dns-warning %} + +Para obtener una lista de dominios personalizados que son compatibles, consulta "[Acerca de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)". + +### Errores HTTPS + +A los sitios {% data variables.product.prodname_pages %} que utilizan dominios personalizados que no están configurados de manera correcta con _CNAME_, `ALIAS`, `ANAME` o registros DNS `A` se puede acceder por HTTPS. Para obtener más información, consulta "[Asegurar tu sitio de {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)". + +Puede tardar hasta una hora que tu sitio se vuelva disponible a través de HTTPS una vez que configures tu dominio personalizado. Después de actualizar los ajustes DNS existentes, puede que debas eliminar y volver a agregar tu dominio personalizado a tu repositorio del sitio para activar el proceso de habilitación HTTPS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Si estás usando registros de Autorización de la Autoridad de Certificación (CAA), debe existir al menos un registro CAA con el valor `letsencrypt.org` para que tu sitio sea accesible a través de HTTPS. Para obtener más información, consulta "[Autorización de la Autoridad de Certificado (CAA)](https://letsencrypt.org/docs/caa/)" en la documentación de Let's Encrypt. + +### Formato de URL en Linux + +Si la URL de tu sitio contiene un nombre de usuario o nombre de organización que comienza o termina con un guion, o que contiene guiones consecutivos, las personas que naveguen con Linux recibirán un error del servidor cuando traten de visitar tu sitio. Para corregir esto, cambia tu nombre de usuario de {% data variables.product.product_name %} y elimina cualquier caracter que no sea alfanumérico. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username/)" + +### Caché del navegador + +Si has cambiado o eliminado recientemente tu dominio personalizado y no puedes acceder a la URL nueva en tu navegador, puede que debas limpiar el caché de tu navegador para llegar a la URL nueva. Para obtener más información acerca de limpiar tu caché, consulta la documentación de tu navegador. diff --git a/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000000..2d34e77141d4f --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,188 @@ +--- +title: Solucionar problemas de errores de compilación de Jekyll para sitios de Páginas de GitHub +intro: 'Puedes usar los mensajes de error de compilación de Jekyll para solucionar los problemas de tu sitio de {% data variables.product.prodname_pages %}.' +redirect_from: + - /articles/page-build-failed-missing-docs-folder/ + - /articles/page-build-failed-invalid-submodule/ + - /articles/page-build-failed-missing-submodule/ + - /articles/page-build-failed-markdown-errors/ + - /articles/page-build-failed-config-file-error/ + - /articles/page-build-failed-unknown-tag-error/ + - /articles/page-build-failed-tag-not-properly-terminated/ + - /articles/page-build-failed-tag-not-properly-closed/ + - /articles/page-build-failed-file-does-not-exist-in-includes-directory/ + - /articles/page-build-failed-file-is-a-symlink/ + - /articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository/ + - /articles/page-build-failed-file-is-not-properly-utf-8-encoded/ + - /articles/page-build-failed-invalid-post-date/ + - /articles/page-build-failed-invalid-sass-or-scss/ + - /articles/page-build-failed-invalid-highlighter-language/ + - /articles/page-build-failed-relative-permalinks-configured/ + - /articles/page-build-failed-syntax-error-in-for-loop/ + - /articles/page-build-failed-invalid-yaml-in-data-file/ + - /articles/page-build-failed-date-is-not-a-valid-datetime/ + - /articles/troubleshooting-github-pages-builds/ + - /articles/troubleshooting-jekyll-builds/ + - /articles/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Solucionar problemas de errores de compilación + +Si Jekyll encuentra un error al compilar tu sitio de {% data variables.product.prodname_pages %} localmente o en {% data variables.product.product_name %}, puede usar los mensajes de error para solucionar los problemas. Para obtener más información acerca de los mensajes de error y de cómo verlos, consulta "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + +Si recibiste un mensaje de error genérico, revisa los problemas comunes. +- Estás usando plugins no compatibles. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll#plugins)".{% if currentVersion == "free-pro-team@latest" %} +- Tu repositorio ha excedido nuestros límites de tamaño del repositorio. Para obtener más información, consulta "[¿Cuál es mi cuota de disco?](/articles/what-is-my-disk-quota)"{% endif %} +- Cambiaste el parámetro `fuente` de tu archivo *_config.yml*. {% data variables.product.prodname_pages %} reemplaza este parámetro durante el proceso de compilación. +- Un nombre de archivo en tu fuente de publicación contiene dos puntos (`:`), los cuales no se admiten. + +Si recibiste un mensaje de error específico, revisa la información de solución de problemas para el mensaje de error que aparece a continuación. + +Después de haber corregido los errores, sube los cambios a la fuente de publicación de tu sitio para activar otra compilación en {% data variables.product.product_name %}. + +### Error de archivo de configuración + +Este error significa que su sitio no se pudo compilar porque el archivo *_config.yml* contiene errores de sintaxis. + +Para solucionar el problema, asegúrate de que tu archivo *_config.yml* respete estas reglas: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### La fecha no es una fecha válida + +Este error significa que una de las páginas de tu sitio incluye una fecha inválida. + +Para solucionar el problema, busca el archivo en el mensaje de error y los diseños del archivo para encontrar llamadas a cualquier filtro Liquid relacionado con la fecha. Asegúrate de que todas las variables ingresadas en los filtros Liquid relacionados con la fecha contengan valores en todos los casos y nunca ingreses `nil` o `""`. Para obtener más información, consulta "[Filtros Liquid](https://help.shopify.com/en/themes/liquid/filters)" en la documentación de Liquid. + +### El archivo no existe en el directorio includes + +Este error significa que tu código hace referencia a un archivo que no existe en el directorio *_includes*. + +{% data reusables.pages.search-for-includes %} Si alguno de los archivos a los que has hecho referencia no se encuentra en el directorio *_includes*, copia o mueve los archivos al directorio *_includes*. + +### El archivo es un enlace simbólico + +Este error significa que tu código hace referencia a un archivo simbólico que no existe en la fuente de publicación de tu sitio. + +{% data reusables.pages.search-for-includes %} Si alguno de los archivos a los que has hecho referencia es un enlace simbólico, copia o mueve los archivos al directorio *_includes*. + +### El archivo no está correctamente codificado en UTF-8 + +Este error significa que usaste caracteres no latinos, como `日本語`, sin decirle a la computadora que esperara estos símbolos. + +Para solucionar el problema, fuerza la codificación en UTF-8 agregando la siguiente línea a tu archivo *_config.yml*: +``` +codificación: UTF-8 +``` + +### Lenguaje de resaltado inválido + +Este error significa que has especificado un resaltador de sintaxis distinto de [Rouge](https://github.com/jneen/rouge) o [Pygments](http://pygments.org/) en tu archivo de configuración. + +Para solucionar el problema, actualiza tu archivo *_config.yml* para especificar [Rouge](https://github.com/jneen/rouge) o [Pygments](http://pygments.org/). Para obtener más información, consulta "[Acerca de las {% data variables.product.product_name %} y Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)". + +### Fecha de publicación inválida + +Este error significa que una publicación en tu sitio contiene una fecha inválida en el nombre de archivo o en el asunto de la parte delantera de YAML. + +Para solucionar el problema, asegúrate de que todas las fechas tengan el formato de AAAA-MM-DD HH:MM:SS para UTC y que sean fechas del calendario reales. Para especificar una zona horaria con un desplazamiento desde UTC, utiliza el formato AAAA-MM-DD HH:MM:SS +/-TTTT, como `2014-04-18 11:30:00 +0800`. + +Si especificas un formato de fecha en tu archivo *_config.yml*, asegúrate de que tenga el formato correcto. + +### Sass o SCSS inválido + +Este error significa que tu repositorio contiene un archivo Sass o SCSS con contenido inválido. + +Para solucionar el problema, revisa el número de línea incluido en el mensaje de error para el Sass o SCSS inválido. Para ayudar a prevenir errores futuros, instala un limpiador de Sass o SCSS para tu editor de texto favorito. + +### Submódulo inválido + +Este error significa que tu repositorio incluye un submódulo que no se ha iniciado correctamente. + +{% data reusables.pages.remove-submodule %} + +Si quieres usar el submódulo, asegúrate de usar `https://` cuando hagas referencia al submódulo (no `http://`) y que el submódulo esté en un repositorio público. + +### YAML inválido en el archivo de datos + +Este error significa que uno o más archivos en la carpeta *_data* contiene un YAML inválido. + +Para solucionar el problema, asegúrate de que tu archivo YAML de la carpeta *_data* respete estas reglas: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +Para obtener más información sobre los archivos de datos de Jekyll, consulta "[Archivos de datos](https://jekyllrb.com/docs/datafiles/)" en la documentación de Jekyll. + +### Errores de Markdown + +Este error significa que tu repositorio contiene errores de Markdown. + +Para solucionar el problema, asegúrate de estar usando un procesador Markdown compatible. Para obtener más información, consulta "[Configurar un procesador Markdown para tu sitio de {% data variables.product.prodname_pages %} usando Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)". + +Luego asegúrate de que el archivo del mensaje de error utilice una sintaxis Markdown válida. Para obtener más información, consulta "[Markdown: sintaxis](https://daringfireball.net/projects/markdown/syntax)" en Daring Fireball. + +### Falta carpeta de docs + +Este error significa que has elegido la carpeta `docs` en una rama como tu fuente de publicación, pero no hay una carpeta `docs` en la raíz de tu repositorio en esa rama. + +Para solucionar el problema, si tu carpeta `docs` se movió accidentalmente, trata de volver a mover la carpeta `docs` a la raíz de tu repositorio en la rama que elegiste como tu fuente de publicación. Si la carpeta `docs` se eliminó accidentalmente, también puedes hacer lo siguiente: +- Usar Git para revertir o deshacer la eliminación. Para obtener más información, consulta "[git-revert](https://git-scm.com/docs/git-revert.html)" en la documentación de Git. +- Crea una carpeta de `docs` nueva en la raíz de tu repositorio en la rama que elegiste para ser tu fuente de publicación y agrega los archivos fuente de tu sitio a la carpeta. Para obtener más información, consulta "[Crear nuevos archivos](/articles/creating-new-files)." +- Cambiar tu fuente de publicación. Para obtener más información, consulta "[Configurar una fuente de publicación para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)". + +### Falta submódulo + +Este error significa que tu repositorio incluye un submódulo que no existe o no se ha iniciado correctamente. + +{% data reusables.pages.remove-submodule %} + +Si quieres utilizar un submódulo, inicia el submódulo. Para obtener más información, consulta "[Herramientas Git - Submódulos](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" en el libro _Pro Git_. + +### Enlaces permanentes relativos configurados + +Este error significa que tienes enlaces permanentes relativos que no son compatibles con {% data variables.product.prodname_pages %} en tu archivo *_config.yml*. + +Los enlaces permanentes son URL permanentes que hacen referencia a una página particular en tu sitio. Los enlaces permanentes absolutos comienzan con la raíz del sitio, mientras que los enlaces permanentes relativos comienzan con la carpeta que contiene la página referenciada. {% data variables.product.prodname_pages %} y Jekyll ya no admiten enlaces permanentes relativos. Para obtener más información acerca de los enlaces permanentes, consulta "[Enlaces permanentes](https://jekyllrb.com/docs/permalinks/)" en la documentación de Jekyll. + +Para solucionar el problema, elimina la línea `relativa_permalinks` de tu archivo *_config.yml* y vuelve a formatear cualquier enlace permanente relativo de tu sitio con enlaces permanentes absolutos. Para obtener más información, consulta "[Editar archivos en tu repositorio](/articles/editing-files-in-your-repository)". + +### El enlace simbólico no existe dentro del repositorio de tu sitio + +Este error significa que tu sitio incluye un enlace simbólico (symlink) que no existe en la fuente de publicación de tu sitio. Para obtener más información acerca de los enlaces simbólicos, consulta "[Enlace simbólico](https://en.wikipedia.org/wiki/Symbolic_link)" en Wikipedia. + +Para solucionar el problema, determina si el archivo en el mensaje de error se utiliza para compilar tu sitio. De lo contrario, o si no quieres que el archivo sea un enlace simbólico, elimina el archivo. Si el archivo de enlace simbólico se necesita para compilar tu sitio, asegúrate de que el archivo o el directorio al que hace referencia el enlace simbólico esté en la fuente de publicación de tu sitio. Para incluir los activos externos, considera utilizar {% if currentVersion == "free-pro-team@latest" %}`git submodule` o {% endif %}un administrador de paquetes de terceros tal como [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Utilizar los submódulos con {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)".{% endif %} + +### Error de sintaxis en el bucle 'for' + +Este error significa que tu código incluye una sintaxis inválida en una declaración de bucle `for` de Liquid. + +Para solucionar el problema, asegúrate de que todos los bucles `for` en el archivo del mensaje de error tengan una sintaxis adecuada. Para obtener más información acerca de la sintaxis adecuada para los bucles `for`, consulta "[Etiquetas de iteración](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" en la documentación de Liquid. + +### Etiqueta no cerrada correctamente + +Este mensaje de error significa que tu código incluye una etiqueta lógica que no está correctamente cerrada. Por ejemplo, {% raw %}`{% capture example_variable %}` debe estar cerrada con `{% endcapture %}`{% endraw %}. + +Para solucionar el problema, asegúrate de que todas las etiquetas lógicas en el archivo del mensaje de error estén correctamente cerradas. Para obtener más información, consulta "[Etiquetas de Liquid](https://help.shopify.com/en/themes/liquid/tags)" en la documentación de Liquid. + +### Etiqueta no finalizada correctamente + +Este error significa que tu código incluye una etiqueta de salida que no está correctamente finalizada. Por ejemplo, {% raw %}`{{ page.title }` en lugar de `{{ page.title }}`{% endraw %}. + +Para solucionar el problema, asegúrate de que todas las etiquetas de salida en el archivo del mensaje de error finalicen con `}}`. Para obtener más información, consulta "[Objetos de Liquid](https://help.shopify.com/en/themes/liquid/objects)" en la documentación de Liquid. + +### Error de etiqueta desconocido + +Este error significa que tu código contiene una etiqueta de Liquid no reconocida. + +Para solucionar el problema, asegúrate de que todas las etiquetas de Liquid en el archivo del mensaje de error coincidan con las variables predeterminadas de Jekyll y que no haya ningún error de escritura en los nombres de las etiquetas. Para encontrar una lista de variables predeterminadas, consulta la sección "[Variables](https://jekyllrb.com/docs/variables/)" en la documentación de Jekyll. + +Los plugins no compatibles son una fuente común de etiquetas no reconocidas. Si usas un plugin no compatible en tu sitio cuando lo generas localmente y subes tus archivos estáticos a {% data variables.product.product_name %}, asegúrate de que el plugin no esté introduciendo etiquetas que no están en las variables predeterminadas de Jekyll. Para obtener una lista de plugin compatibles, consulta "[Acerca de las {% data variables.product.prodname_pages %} y Jekyll](/articles/about-github-pages-and-jekyll#plugins)". diff --git a/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000000..d263d3d3443e6 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,34 @@ +--- +title: Anular la publicación de un sitio de Páginas de GitHub +intro: 'Puedes dejar de publicar tu sitio de {% data variables.product.prodname_pages %} para que éste ya no esté disponible para el {% if currentVersion == "free-pro-team@latest" %}público{% else %}todos si utilizas {% data variables.product.product_location %}{% endif %}.' +redirect_from: + - /articles/how-do-i-unpublish-a-project-page/ + - /articles/unpublishing-a-project-page/ + - /articles/unpublishing-a-project-pages-site/ + - /articles/unpublishing-a-user-pages-site/ + - /articles/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'Las personas con permisos administrativos en un repositorio pueden anular la publicación de un sitio de {% data variables.product.prodname_pages %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Anular la publicación de un sitio de proyecto + +{% data reusables.repositories.navigate-to-repo %} +2. Si existe una rama de `gh-pages` en el repositorio, elimina la rama de `gh-pages`. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". +3. Si la rama de `gh-pages` fue tu fuente de publicación, +{% if currentVersion == "free-pro-team@latest" %}salta al paso 6{% else %}tu sitio dejó de publicarse ahora y puedes saltar el resto de los pasos{% endif %}. +{% data reusables.repositories.sidebar-settings %} +5. Debajo de " +{% data variables.product.prodname_pages %}", utiliza el menú desplegable **Fuente** y selecciona **Ninguno** + ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### Anular la publicación de un sitio de usuario o de organización + +{% data reusables.repositories.navigate-to-repo %} +2. Borra la rama que estás utilizando como fuente de publicación, o borra todo el repositorio. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" y "[Eliminar un repositorio](/articles/deleting-a-repository)". +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000000..194b034ddec28 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,21 @@ +--- +title: Usar submódulos con las Páginas de GitHub +intro: 'Puedes usar submódulos con las {% data variables.product.prodname_pages %} para incluir otros proyectos en el código de tu sitio.' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +--- + +Si el repositorio para tu sitio de {% data variables.product.prodname_pages %} contiene submódulos, sus contenidos se extraerán automáticamente cuando se compile tu sitio. + +Solo puedes usar submódulos que apunten a los repositorios públicos, porque el servidor de {% data variables.product.prodname_pages %} no puede acceder a los repositorios privados. + +Utiliza la URL de solo lectura `https://` para tus submódulos, incluidos los submódulos anidados. Puedes hacer este cambio en tu archivo _.gitmodules_. + +### Further reading + +- "[Heramientas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" del libro _Pro Git_ +- "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md new file mode 100644 index 0000000000000..aeecc73d6ccb9 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md @@ -0,0 +1,69 @@ +--- +title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Cloud +intro: '{% data variables.contact.premium_support %} es una oferta de soporte suplementaria y pagada para los clientes de {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_one %}.' +redirect_from: + - /articles/about-github-premium-support + - /articles/about-github-premium-support-for-github-enterprise-cloud +versions: + free-pro-team: '*' +--- + +{% note %} + +**Notas:** + +- Los términos del {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y entraron en vigencia a partir de septiembre de 2018. + +- {% data reusables.support.data-protection-and-privacy %} + +- Este artículo contiene los términos de {% data variables.contact.premium_support %} para clientes de {% data variables.product.prodname_ghe_cloud %}. Es posible que los términos sean diferentes para los clientes de {% data variables.product.prodname_ghe_server %} o los clientes de {% data variables.product.prodname_enterprise %} que compran {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Para obtener más información, consulta "[Acerca de {% 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)" y "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)". + +{% endnote %} + +### Acerca de {% data variables.contact.premium_support %} + +{% data variables.contact.premium_support %} ofrece: + - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. + - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. + - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados. + - Acceso a contenido prémium. + - Revisiones de estado programadas. + - Servicios administrados. + +{% data reusables.support.about-premium-plans %} + +{% data reusables.support.signing-up-for-premium-support %} + +{% data reusables.support.scope-of-support %} + +{% data reusables.support.contacting-premium-support %} + +### Horas de operación + +{% data variables.contact.premium_support %} está disponible 24 horas al día, 7 días a la semana. + +{% data reusables.support.service-level-agreement-response-times %} + +### Asignar una prioridad a un ticket de soporte + +Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. + +{% data reusables.support.github-can-modify-ticket-priority %} + +{% data reusables.support.ghec-premium-priorities %} + +### Resolver y cerrar tickets de soporte + +{% data variables.contact.premium_support %} puede considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucción de uso, o de solución alternativa, + +Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible. + +{% data variables.contact.premium_support %}Puede cerrar los tickets si están fuera del alcance de soporte o si se te ha intentado contactar varias veces sin recibir una respuesta. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra. + +{% data reusables.support.receiving-credits %} + +{% data reusables.support.accessing-premium-content %} + +### Further reading + +- "[Enviar un ticket](/articles/submitting-a-ticket)" diff --git a/translations/es-ES/content/github/working-with-github-support/about-github-support.md b/translations/es-ES/content/github/working-with-github-support/about-github-support.md new file mode 100644 index 0000000000000..d8333d387a62b --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/about-github-support.md @@ -0,0 +1,34 @@ +--- +title: Acerca del Soporte de GitHub +intro: '{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas con los que te encuentres cuando utilices {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /articles/about-github-support +versions: + free-pro-team: '*' +--- + +### Acerca de {% data variables.contact.github_support %} + +Las opciones de soporte varían dependiendo de tu producto de {% data variables.product.prodname_dotcom_the_website %}. Si cuentas con un producto pagado, puedes contactar a {% data variables.contact.github_support %} en inglés. Tu cuenta también puede incluir {% data variables.contact.premium_support %}. + +| | {% data variables.product.prodname_gcf %} | Soporte estándar | Soporte premium | +| -------------------------------------------------- | ----------------------------------------- | ---------------- | --------------- | +| {% data variables.product.prodname_free_user %} | X | | | +| {% data variables.product.prodname_pro %} | X | X | | +| {% data variables.product.prodname_team %} | X | X | | +| {% data variables.product.prodname_ghe_cloud %} | X | X | X | +| {% data variables.product.prodname_ghe_server %} | X | X | X | + +Para ver si actualmente hay algún incidente que afecte los servicios en {% data variables.product.prodname_dotcom %}, o para suscribirse y recibir notificaciones de actualizaciones de estado futuras, visita la [Página de Estado](https://www.githubstatus.com/) de {% data variables.product.prodname_dotcom %}. + +### Contactar a {% data variables.contact.github_support %} + +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. + +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. + +### Otorgar a {% data variables.contact.github_support %} acceso temporal a un repositorio privado + +Si {% data variables.contact.github_support %} necesita acceder a un repositorio privado para tratar tu solicitud de soporte, el dueño de éste recibirá un correo electrónico con un enlace para aceptar o rechazar el acceso temporal. El propietario tendrá 20 días para aceptar o rechazar la solicitud antes de que ésta caduque. Si el propietario acepta la solicitud, {% data variables.contact.github_support %} tendrá acceso al repositorio por cinco días. + +{% data variables.contact.github_support %} jamás accederá a tus repositorios privados sin tu consentimiento explícito. Para obtener más información, consulta las [Condiciones de Servicio](/articles/github-terms-of-service#3-access). diff --git a/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md b/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md new file mode 100644 index 0000000000000..236609c859bab --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md @@ -0,0 +1,48 @@ +--- +title: Asistencia para Enterprise Cloud de GitHub +redirect_from: + - /articles/business-plan-support/ + - /articles/github-business-cloud-support/ + - /articles/github-enterprise-cloud-support +intro: '{% data variables.product.prodname_ghe_cloud %} incluye un tiempo de respuesta objetivo de ocho horas para las solicitudes de asistencia prioritarias, de lunes a viernes en tu zona horaria local.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Notq:** Los clientes de {% data variables.product.prodname_ghe_cloud %} pueden registrarse para {% data variables.contact.premium_support %}. Para obtener más información, consulta "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)". + +{% endnote %} + +Puedes enviar preguntas prioritarias si has comprado {% data variables.product.prodname_ghe_cloud %} o si eres miembro, colaborador externo o gerente de facturación de una organización {% data variables.product.prodname_dotcom %} actualmente suscrita en {% data variables.product.prodname_ghe_cloud %}. + +Preguntas que califican para recibir respuestas prioritarias: +- Incluyen preguntas relacionadas con tu imposibilidad para acceder o usar la funcionalidad de control de la versión principal de {% data variables.product.prodname_dotcom %} +- Incluyen situaciones relacionadas con la seguridad de tu cuenta +- No incluyen servicios y funciones periféricos, como preguntas acerca de Gists, {% data variables.product.prodname_pages %} o notificaciones de correo electrónico +- Incluyen preguntas acerca de organizaciones que actualmente usan {% data variables.product.prodname_ghe_cloud %} + +Para calificar para una respuesta prioritaria, debes hacer lo siguiente: +- Enviar tu pregunta a [{% data variables.contact.enterprise_support %}](https://enterprise.githubsupport.com/hc/en-us/requests/new?github_product=cloud) desde una dirección de correo verificada que esté asociada con la organización que actualmente usa {% data variables.product.prodname_ghe_cloud %} +- Enviar un ticket de asistencia nuevo para cada situación prioritaria particular +- Enviar tu pregunta de lunes a viernes en tu zona horaria local +- Comprender que la respuesta a una pregunta prioritaria será recibida por correo electrónico +- Colaborar con {% data variables.contact.github_support %} y proporcionar toda la información que solicite {% data variables.contact.github_support %} + +{% tip %} + +**Consejo:** Las preguntas no califican para recibir respuestas prioritarias si se envían durante un feriado local de tu jurisdicción. + +{% endtip %} + +El tiempo de respuesta objetivo de ocho horas: +- Comienza cuando {% data variables.contact.github_support %} recibe tu pregunta que califica +- No comienza hasta que hayas proporcionada la suficiente información para responder la pregunta, a menos que específicamente indiques que no cuentas con la información suficiente +- No aplica durante los fines de semana de tu zona horaria local o durante los feriados locales de tu jurisdicción + +{% note %} + +**Nota:** {% data variables.contact.github_support %} no garantiza una resolución para tu pregunta prioritaria. {% data variables.contact.github_support %} puede escalar problemas al estado de pregunta prioritaria o bajarlos en función de nuestra evaluación razonable de la información que nos proporcionas. + +{% endnote %} diff --git a/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md b/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md new file mode 100644 index 0000000000000..a6210ccb97e39 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md @@ -0,0 +1,24 @@ +--- +title: Asistencia de Mercado GitHub +intro: 'Para recibir ayuda con la compra o el pago de una app desde {% data variables.product.prodname_marketplace %}, contáctate con {% data variables.contact.contact_support %}. Para recibir ayuda con el uso de una app {% data variables.product.prodname_marketplace %}, contáctate con el proveedor de la app.' +redirect_from: + - /articles/github-marketplace-support +versions: + free-pro-team: '*' +--- + + +### Contactarse con el proveedor de la app para recibir asistencia + +Todas las apps de {% data variables.product.prodname_marketplace %} incluyen un enlace para contactarse con el equipo de asistencia de la app. + +{% data reusables.marketplace.visit-marketplace %} +2. Navega por la página de tu app. +3. En la barra lateral izquierda, dentro de "Developer tools" (Herramientas del programador), haz clic en **Support** (Asistencia). +4. En la página de asistencia de la app, sigue las instrucciones de la página de la app para contactarte con el equipo de asistencia de la app. + +### Further reading + +- "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" +- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" +- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" diff --git a/translations/es-ES/content/github/working-with-github-support/index.md b/translations/es-ES/content/github/working-with-github-support/index.md new file mode 100644 index 0000000000000..2ab91be0a007b --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/index.md @@ -0,0 +1,17 @@ +--- +title: Trabajar con el soporte de GitHub +redirect_from: + - /categories/working-with-github-support + - /forum +versions: + free-pro-team: '*' +--- + + +### Índice + +{% link_in_list /about-github-support %} +{% link_in_list /github-enterprise-cloud-support %} +{% link_in_list /about-github-premium-support-for-github-enterprise-cloud %} +{% link_in_list /github-marketplace-support %} +{% link_in_list /submitting-a-ticket %} diff --git a/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md new file mode 100644 index 0000000000000..7d7149ba5db37 --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md @@ -0,0 +1,37 @@ +--- +title: Envío de ticket +intro: 'Puedes enviar un ticket a {% data variables.contact.github_support %} utilizando el portal de soporte.' +redirect_from: + - /articles/submitting-a-ticket +versions: + free-pro-team: '*' +--- + +Si tu cuenta utiliza un producto pagado de {% data variables.product.prodname_dotcom %}, puedes contactar directamente a {% data variables.contact.github_support %}. Si tu cuenta utiliza {% data variables.product.prodname_free_user %} para cuentas organizacionales y de usuario, puedes contactar a {% data variables.contact.contact_support %} para reportar problemas con la cuenta, seguridad y abuso. Para obtener más informaciónm, consulta la sección "[Acerca de GitHub Support](/github/working-with-github-support/about-github-support)". + +Si utilizas {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, o el {% data variables.product.premium_support_plan %} deberás emitir tickets utilizando el {% data variables.contact.enterprise_portal %}. + +### Emitir un ticket utilizando el {% data variables.contact.support_portal %} + +1. Navega por el {% data variables.contact.contact_support_portal %}. +2. Debajo de "Nombre", ingresa tu nombre. ![Campo de nombre](/assets/images/help/support/name-field.png) +3. Utiliza el menú desplegable de correo electrónico y selecciona la dirección de correo electrónico que deseas contacte {% data variables.contact.github_support %}.![Campo de correo electrónico](/assets/images/help/support/email-field.png) +4. Debajo de "Tema", teclea un título descriptivo para el problema que estás experimentando. ![Campo de asuto](/assets/images/help/support/subject-field.png) +5. Debajo de "Cómo podemos ayudar", proporciona cualquier tipo de información adicional que ayudará al equipo de soporte a solucionar el problema. La información útil podría incluir: ![Campo de cómo podemos ayudar](/assets/images/help/support/how-can-we-help-field.png) + - Pasos para reproducir el incidente + - Cualquier circunstancia especial relacionada con el descubrimiento del problema (por ejemplo, la primera vez que se suscitó, o su materialización después de cierto evento, frecuencia en la que se presenta, impacto al negocio, y urgencia sugerida) + - Redacción exacta de los mensajes de error +6. Opcionalmente, adjunta archivos arrastrando y soltando, cargando, o pegando desde el portapapeles. +7. Da clic en **Enviar solicitud**. ![Botón de eenviar solicitud](/assets/images/help/support/send-request-button.png) + +### Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} + +1. Navegar por el {% data variables.contact.contact_enterprise_portal %}. +5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) +{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} +{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} + +### Further reading +- "[Productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)" +- "[Acerca de {% data variables.contact.github_support %}](/articles/about-github-support)" +- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)." diff --git a/translations/es-ES/content/github/writing-on-github/about-saved-replies.md b/translations/es-ES/content/github/writing-on-github/about-saved-replies.md new file mode 100644 index 0000000000000..cce9b27807d36 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/about-saved-replies.md @@ -0,0 +1,27 @@ +--- +title: Acerca de las respuestas guardadas +intro: Puedes usar una respuesta guardada para responder a una propuesta o una solicitud de extracción. +redirect_from: + - /articles/about-saved-replies +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +![Respuestas guardadas](/assets/images/help/settings/saved-replies.png) + +Las respuestas guardadas te permiten crear una respuesta reusable para las propuestas y las solicitudes de extracción. Ahorra tiempo creando una respuesta guardada para las respuestas que usas con mayor frecuencia. + +Una vez que has agregado una respuesta guardada, se puede usar tanto en las propuestas como en las solicitudes de extracción. Las respuestas guardadas están asociadas a tu cuenta de usuario. Una vez que son creadas, podrás usarlas en todos los repositorios y las organizaciones. + +Puedes crear un máximo de 100 respuestas guardadas. Si has alcanzado el límite máximo, puedes eliminar las respuestas guardadas que ya no usas o editar las respuestas guardadas existentes. + +También puedes usar la respuesta guardada "Duplicar propuesta" proporcionada por {% data variables.product.product_name %} para marcar una propuesta como un duplicado y hacerle un seguimiento con una propuesta similar. + +### Further reading + +- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" +- "[Usar respuestas guardadas](/articles/using-saved-replies)" +- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" +- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md b/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md new file mode 100644 index 0000000000000..5b016da2b58d9 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md @@ -0,0 +1,29 @@ +--- +title: Acerca de escritura y formato en GitHub +intro: GitHub combina una sintáxis para el texto con formato llamado formato Markdown de GitHub con algunas características de escritura únicas. +redirect_from: + - /articles/about-writing-and-formatting-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +[Markdown](http://daringfireball.net/projects/markdown/) es una sintáxis fácil de leer y fácil de escribir para el texto simple con formato. + +Le hemos agregado alguna funcionalidad personalizada para crear el formato Markdown de {% data variables.product.prodname_dotcom %}, usado para dar formato a la prosa y al código en todo nuestro sitio. + +También puedes interactuar con otros usuarios en las solicitudes de extracción y las propuestas, usando funciones como [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [propuesta y referencias PR](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) y [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji). + +### Barra de herramientas de formato de texto + +Cada campo de comentario en {% data variables.product.product_name %} contiene una barra de herramientas de formato de texto, lo que te permite dar formato a tu texto sin tener que aprender la sintáxis de Markdown. Además del formato de Markdown como la negrita y la cursiva y crear encabezados, enlaces y listados, la barra de herramientas incluye características específicas de {% data variables.product.product_name %}, como las @menciones, los listados de tareas y los enlaces a propuestas y solicitudes de extracción. + +![Barra de herramientas de Markdown](/assets/images/help/writing/markdown-toolbar.gif) + +### Further reading + +- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) +- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" +- "[Trabajar con formato avanzado](/articles/working-with-advanced-formatting)" +- "[Dominar Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md new file mode 100644 index 0000000000000..eb39a46d74e7e --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md @@ -0,0 +1,57 @@ +--- +title: Referencias y direcciones URL autovinculadas +intro: 'Las referencias a las direcciones URL, propuestas, solicitudes de extracción y confirmaciones se acortan automáticamente y se convierten en vínculos.' +redirect_from: + - /articles/autolinked-references-and-urls +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Direcciones URL + +{% data variables.product.product_name %} automáticamente crea vínculos desde las direcciones URL estándar. + +`Visita https://github.com` + +![URL autovinculada presentada](/assets/images/help/writing/url-autolink-rendered.png) + +Para obtener información sobre cómo crear vínculos, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#links)". + +### Propuestas y solicitudes de extracción + +Dentro de las conversaciones en {% data variables.product.product_name %}, las referencias a las propuestas y solicitudes de extracción se convierten automáticamente en vínculos acortados. Para obtener más información, consulta "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)". + +{% note %} + +**Nota:** Las referencias autovinculadas no se crearon en páginas wikis o archivos en un repositorio. + +{% endnote %} + +| Tipo de referencia | Referencia en bruto | Vínculo acortado | +| --------------------------------------------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------- | +| URL de propuesta o solicitud de extracción | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) | +| `#` y número de propuesta o solicitud de extracción | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) | +| `GH` y número de propuesta y solicitud de extracción | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) | +| `Nombre de usuario/N.º de repositorio` y número de propuesta o solicitud de extracción. | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26) | +| `Organization_name/Repository#` y número propuesta o solicitud de extracción | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039) | + +### Confirmar SHA + +Las referencias a un hash SHA de confirmación se convertirán automáticamente en enlaces acortados para la confirmación en {% data variables.product.product_name %}. + +| Tipo de referencia | Referencia en bruto | Vínculo acortado | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | +| URL de confirmación | [`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) | + +### Personalizar enlaces automáticos a recursos externos + +{% data reusables.repositories.autolink-references %} + +### Further reading + +- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md new file mode 100644 index 0000000000000..944511f8d9d61 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -0,0 +1,239 @@ +--- +title: Sintaxis de escritura y formato básicos +intro: Crear formatos sofisticados para tu prosa y código en GitHub con sintaxis simple. +redirect_from: + - /articles/basic-writing-and-formatting-syntax +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Encabezados + +Para crear un encabezado, agrega uno a seis símbolos `#` antes del encabezado del texto. La cantidad de `#` que usas determinará el tamaño del ecanbezado. + +``` +# El encabezado más largo +## El segundo encabezado más largo +###### El encabezado más pequeño +``` + +![Encabezados H1, H2 y H6 representados](/assets/images/help/writing/headings-rendered.png) + +### Estilo de texto + +Puedes indicar énfasis con texto en negrita, cursiva o tachado. + +| Estilo | Sintaxis | Atajo del teclado | Ejemplo | Resultado | +| ---------------------------- | ----------------- | ------------------- | ----------------------------------------------- | --------------------------------------------- | +| Negrita | `** **` o `__ __` | command/control + b | `**Este texto está en negrita**` | **Este texto está en negrita** | +| Cursiva | `* *` o `_ _` | command/control + i | `*Este texto está en cursiva*` | *Este texto está en cursiva* | +| Tachado | `~~ ~~` | | `~~Este texto está equivocado~~` | ~~Este texto está equivocado~~ | +| Cursiva en negrita y anidada | `** **` y `_ _` | | `**Este texto es _extremadamente_ importante**` | **Este texto es _extremadamente_ importante** | +| Todo en negrita y cursiva | `*** ***` | | `***Todo este texto es importante***` | ***Todo este texto es importante*** | + +### Cita de texto + +Puedes citar texto con un `>`. + +``` +Tal como dice Abraham Lincoln: + +> Con perdón de la expresión +``` + +![Texto citado representado](/assets/images/help/writing/quoted-text-rendered.png) + +{% tip %} + +**Sugerencia:** Al revisar una conversación, puedes citar un texto automáticamente en un comentario al resaltar el texto y luego escribir el código `r`. Puedes citar un comentario completo al hacer clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, y luego en **Quote reply** (Citar respuesta). Para obtener más información sobre atajo del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)". + +{% endtip %} + +### Código de cita + +Puedes indicar un código o un comando dentro de un enunciado con comillas simples. El texto dentro de las comillas simples no será formateado. + +``` +Usa `git status` para enumerar todos los archivos nuevos o modificados que aún no han sido confirmados. +``` + +![Bloque de código en línea representado](/assets/images/help/writing/inline-code-rendered.png) + +Para formatear código o texto en su propio bloque distintivo, usa comillas triples. + +
+Algunos de los comandos de Git básicos son:
+```
+git status
+git add
+git commit
+```
+
+ +![Bloque de código representado](/assets/images/help/writing/code-block-rendered.png) + +Para obtener más información, consulta "[Crear y resaltar bloques de código](/articles/creating-and-highlighting-code-blocks)". + +### Enlaces + +Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes `[ ]`, y luego encerrar la URL entre paréntesis `( )`. También puedes usar el atajo del teclado `command + k` para crear un enlace. + +`Este sitio se construyó usando [GitHub Pages](https://pages.github.com/).` + +![Enlace representado](/assets/images/help/writing/link-rendered.png) + +{% tip %} + +**Sugerencias:** {% data variables.product.product_name %} automáticamente crea enlaces cuando las direcciones URL válidas están escritas en un comentario. Para obtener más información, consulta "[Referencias autovinculadas y direcciones de URL](/articles/autolinked-references-and-urls)". + +{% endtip %} + +### Enlaces de sección + +{% data reusables.repositories.section-links %} + +### Enlaces relativos + +{% data reusables.repositories.relative-links %} + +### Listas + +Puedes realizar una lista desordenada al anteceder una o más líneas de texto con `-` o `*`. + +``` +- George Washington +- John Adams +- Thomas Jefferson +``` + +![Lista desordenada representada](/assets/images/help/writing/unordered-list-rendered.png) + +Para ordenar tu lista, antecede cada línea con un número. + +``` +1. James Madison +2. James Monroe +3. John Quincy Adams +``` + +![Lista ordenada representada](/assets/images/help/writing/ordered-list-rendered.png) + +#### Listas anidadas + +Puedes crear una lista anidada al dejar sangría en uno o más elementos de la lista debajo de otro elemento. + +Para crear una lista anidada mediante el editor web en {% data variables.product.product_name %} o un editor de texto que usa una fuente monoespaciada, como [Atom](https://atom.io/), puedes alinear tu lista visualmente. Escribe los caracteres con espacio frente a tu elemento de la lista anidada hasta que el carácter del marcador de lista (`-` or `*`) se encuentre directamente debajo del primer carácter del texto en el elemento que se encuentra por debajo. + +``` +1. Primer elemento de la lista + - Primer elemento de la lista anidado + - Segundo elemento de la lista anidado +``` + +![Lista anidada con alineación resaltada](/assets/images/help/writing/nested-list-alignment.png) + +![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-1.png) + +Para crear una lista anidada en el editor de comentarios en {% data variables.product.product_name %}, que no usa una fuente monoespaciada, puedes observar el elemento de la lista inmediatamente anterior a la lista anidada y contar el número de caracteres que aparecen antes del contenido del elemento. Luego escribe ese número de caracteres de espacio frente al elemento de la lista anidada. + +En este ejemplo, puedes agregar un elemento de la lista anidada debajo del elemento de la lista `100. Primer elemento de la lista` con una sangría mínima de cinco espacios para el elemento de la lista anidada, dado que hay cinco caracteres (`100.`) antes del `Primer elemento de la lista`. + +``` +100. Primer elemento de la lista + - Primer elemento de la lista anidada +``` + +![Lista con un elemento de lista anidado](/assets/images/help/writing/nested-list-example-3.png) + +Puedes crear múltiples niveles de listas anidadas mediante el mismo método. Por ejemplo, dado que el primer elemento de la lista tiene siete espacios (`␣␣␣␣␣-␣`) antes del contenido de la lista anidada `Primer elemento de la lista anidada`, deberías colocar sangría en el primer elemento de la lista anidada por siete espacios. + +``` +100. Primer elemento de la lista + - Primer elemento de la lista anidada + - Segundo elemento de la lista anidada +``` + +![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-2.png) + +Para conocer más ejemplos, consulta las [Especificaciones de formato Markdown de GitHub](https://github.github.com/gfm/#example-265). + +### Listas de tareas + +{% data reusables.repositories.task-list-markdown %} + +Si la descripción de un elemento de la lista de tareas comienza con un paréntesis, necesitarás escapar de ella con `\`: + +`- [ ] \(Optional) Abre una propuesta de seguimiento` + +Para obtener más información, consulta "[Acerca de las listas de tareas](/articles/about-task-lists)". + +### Mencionar personas y equipos + +Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir `@` más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. Para obtener más información acerca de las notificaciones, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". + +`@github/support ¿Qué piensas sobre estas actualizaciones?` + +![@mention representado](/assets/images/help/writing/mention-rendered.png) + +Cuando mencionas a un equipo padre, los miembros de los equipos hijo también reciben notificaciones, simplificando la comunicación con múltiples grupos de personas. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". + +Si escribes un símbolo `@` aparecerá una lista de personas o equipos en el proyecto. La lista filtra a medida que escribes, por lo que una vez que escribes el nombre de la persona o del equipo que estás buscando, puedes usar las teclas de flecha para seleccionarlos y presionar cada pestaña para ingresar para completar el nombre. En el caso de los equipos, escribe el nombre de la @organización/equipo y todos los miembros del equipo que se suscribirán a la conversación. + +Los resultados autocompletados se restringen a los colaboradores del repositorio y a otros participantes en el hilo. + +### Hacer referencia a propuestas y solicitudes de extracción + +Puedes mencionar una lista de las propuestas y las solicitudes de extracción sugeridas dentro del repositorio al escribir `#`. Escribe el número o el título de la propuesta o la solicitud de extracción para filtrar la lista, y luego presiona cada pestaña o ingresa para completar el resultado resaltado. + +Para obtener más información, consulta "[Referencias y direcciones URL autovinculadas](/articles/autolinked-references-and-urls)". + +### Hacer referencia a recursos externos + +{% data reusables.repositories.autolink-references %} + +### Adjuntos de contenido + +Algunas {% data variables.product.prodname_github_app %} brindan información en {% data variables.product.product_name %} para las URL que se vinculan con sus dominios registrados. {% data variables.product.product_name %} presenta la información suministrada por la app debajo de la URL en el cuerpo o comentario de una propuesta o solicitud de extracción. + +![Adjunto de contenido](/assets/images/help/writing/content-attachment.png) + +Para ver los adjuntos de contenido, debes tener una {% data variables.product.prodname_github_app %} que utilice la API de adjuntos de contenido instalada en el repositorio.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta las secciones "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" e "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)".{% endif %} + +Los adjuntos de contenido no se mostrarán para las URL que son parte de un enlace de Markdown. + +Para obtener más información sobre el desarrollo de una {% data variables.product.prodname_github_app %} que utilice adjuntos de contenido, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments)". + +### Usar emojis + +Puedes agregar emojis a tu escritura al escribir `:EMOJICODE:`. + +`@octocat :+1: This PR looks great - it's ready to merge! :shipit:` + +![Emoji representado](/assets/images/help/writing/emoji-rendered.png) + +Si escribes `:` aparecerá una lista con los emojis sugeridos. La lista filtrará a medida que escribes; por lo tanto, una vez que encuentres el emoji que estás buscando, presiona **Tab** (Tabulador) o **Enter** (Intro) para completar el resultado resaltado. + +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). + +### Párrafos + +Puedes crear un nuevo párrafo al dejar una línea en blanco entre las líneas de texto. + +### Importar formato de Markdown + +Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) el formato de Markdown usando la `\` antes del caracter de Markdown. + +`Cambiemos el nombre de \*our-new-project\* a \*our-old-project\*.` + +![Carácter evadido representado](/assets/images/help/writing/escaped-character-rendered.png) + +Para obtener más información, consulta "[Sintaxis de Markdown" de Daring Fireball](https://daringfireball.net/projects/markdown/syntax#backslash), + +### Further reading + +- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) +- "[Acerca de escritura y formato en GitHub](/articles/about-writing-and-formatting-on-github)" +- "[Trabajar con formato avanzado](/articles/working-with-advanced-formatting)" +- "[Dominar Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md new file mode 100644 index 0000000000000..f58824426b1a2 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md @@ -0,0 +1,23 @@ +--- +title: Crear una respuesta guardada +intro: 'Si sueles agregar el mismo comentario una y otra vez, puedes crear una respuesta guardada.' +redirect_from: + - /articles/creating-a-saved-reply +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.saved_replies %} +3. En "Agregar una respuesta guardada", agrega el título de tu respuesta guardada. ![Título de la respuesta guardada](/assets/images/help/settings/saved-replies-title.png) +4. En el campo "Escribir", agrega el contenido que deseas usar para la respuesta guardada. Para obtener más información acerca de la escritura en {% data variables.product.product_name %}, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". ![Escribir una respuesta guardada](/assets/images/help/settings/saved-replies-settings-adding.png) +5. Para revisar tu respuesta, haz clic en **Vista previa**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-preview.png) +6. Haz clic en **Agregar respuesta guardada**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-add-button.png) + +### Further reading + +- "[Usar respuestas guardadas](/articles/using-saved-replies)" +- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" +- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md new file mode 100644 index 0000000000000..ffc04fcce7007 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md @@ -0,0 +1,52 @@ +--- +title: Crear y resaltar bloques de código +intro: Compartir muestras de código con bloques de código cercados y habilitar el resaltado de la sintaxis +redirect_from: + - /articles/creating-and-highlighting-code-blocks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Bloques de código cercados + +Puedes crear bloques de código cercados al colocar comillas simples triples \`\`\` antes y después del bloque de código. Te recomendamos dejar una línea en blanco antes y después de los bloques de código para facilitar la lectura del formato sin procesar. + +
+```
+function test() {
+  console.log("notice the blank line before this function?");
+}
+```
+
+ +![Bloque de código cercado representado](/assets/images/help/writing/fenced-code-block-rendered.png) + +{% tip %} + +**Sugerencia:** Para preservar tu formato en una lista, asegúrate de dejar una sangría de ocho espacios para los bloques de código no cercados. + +{% endtip %} + +### Resaltado de la sintaxis + +Puedes agregar un identificador opcional de idioma para habilitar el resaltado de la sintaxis en tu bloque de código cercado. + +Por ejemplo, para resaltar la sintaxis del código Ruby: + + ```ruby + require 'redcarpet' + markdown = Redcarpet.new("Hello World!") + puts markdown.to_html + puts markdown.to_html + ``` + +![Bloque de código cercado representado con sintaxis de Ruby resaltada](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png) + +Usamos [Lingüista](https://github.com/github/linguist) para realizar la detección del idioma y seleccionar [gramáticas independientes](https://github.com/github/linguist/blob/master/vendor/README.md) para el resaltado de la sintaxis. Puedes conocer las palabra clave válidas en [el archivo YAML de idiomas](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +### Further reading + +- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) +- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-gists.md b/translations/es-ES/content/github/writing-on-github/creating-gists.md new file mode 100644 index 0000000000000..54a31d48943ce --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/creating-gists.md @@ -0,0 +1,76 @@ +--- +title: Crear gists +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' +redirect_from: + - /articles/about-gists/ + - /articles/cannot-delete-an-anonymous-gist/ + - /articles/deleting-an-anonymous-gist/ + - /articles/creating-gists +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los gists + +Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. + +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean. + +Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist. + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} + +{% if enterpriseServerVersions contains currentVersion %} + +Si el administrador de tu sitio ha inhabilitado el modo privado, también puedes usar gists anónimos, que pueden ser públicos o privados. + +{% data reusables.gist.anonymous-gists-cannot-be-deleted %} + +{% endif %} + +Recibirás una notificación si: +- Seas el autor de un gist. +- Alguien te mencione en un gist. +- Puedes suscribirte a un gist haciendo clic en **Suscribir** en la parte superior de cualquier gist. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Puedes fijar los gists a tu perfil para que otras personas los puedan ver fácilmente. Para obtener más información, consulta "[A nclar elementos a tu perfil](/articles/pinning-items-to-your-profile)". + +{% endif %} + +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/articles/searching-code). + +Dado que los gists son repositorios Git, puedes ver su historial de confirmaciones completo, que incluye todas las diferencias que existan. También puedes bifurcar o clonar gists. Para obtener más información, consulta "[Bifurcar y clonar gists"](/articles/forking-and-cloning-gists). + +Puedes descargar un archivo ZIP de un gist haciendo clic en el botón **Descargar ZIP** en la parte superior del gist. Puedes insertar un gist en cualquier campo de texto compatible con Javascript, como una publicación en un blog. Para insertar el código, haz clic en el icono del portapapeles junto a la URL **Insertar** de un gist. Para insertar un archivo de gist específico, anexa la URL **Insertar** con `?file=FILENAME`. + +{% if currentVersion == "free-pro-team@latest" %} + +Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran como gists insertos, para que las asignaciones se puedan compartir e insertar fácilmente. Para obtener más información, consulta "[Asignar archivos GeoJSON en {% data variables.product.product_name %}](/articles/mapping-geojson-files-on-github)". + +{% endif %} + +### Crear un gist + +También puedes arrastrar y soltar un archivo de texto desde tu escritorio directamente en el editor de gist. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% note %} + +También puedes crear un gist si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" en el {% data variables.product.prodname_cli %}. + +{% endnote %} +{% endif %} + +1. Inicia sesión en {% data variables.product.product_name %}. +2. Dirígete a tu {% data variables.gists.gist_homepage %}. +3. Escribe una descripción opcional y un nombre para tu gist. ![Descripción del nombre del gist](/assets/images/help/gist/gist_name_description.png) + +4. Escribe el texto de tu gist en el cuadro de texto para el gist. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png) + +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} + +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/es-ES/content/github/writing-on-github/deleting-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/deleting-a-saved-reply.md new file mode 100644 index 0000000000000..6f96e3543e9ee --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/deleting-a-saved-reply.md @@ -0,0 +1,15 @@ +--- +title: Eliminar una respuesta guardada +intro: 'Si adviertes que ya no usas una respuesta guardada, puedes eliminarla.' +redirect_from: + - /articles/deleting-a-saved-reply +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.saved_replies %} +3. En "Respuestas guardadas", junto a la respuesta guardada que deseas eliminar, haz clic en {% octicon "x" aria-label="The X" %}. + ![Eliminar respuesta guardada](/assets/images/help/settings/saved-replies-delete-existing.png) diff --git a/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md new file mode 100644 index 0000000000000..e45bf48764160 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md @@ -0,0 +1,24 @@ +--- +title: Editar una respuesta guardada +intro: Puedes editar el título y el cuerpo de una respuesta guardada. +redirect_from: + - /articles/changing-a-saved-reply/ + - /articles/editing-a-saved-reply +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.saved_replies %} +3. En "Respuestas guardadas", junto a la respuesta guardada que deseas editar, haz clic en {% octicon "pencil" aria-label="The pencil" %}. + ![Editar una respuesta guardada](/assets/images/help/settings/saved-replies-edit-existing.png) +4. En "Editar una respuesta guardada", puedes editar el título y el contenido de la respuesta guardada. ![Editar título y contenido](/assets/images/help/settings/saved-replies-edit-existing-content.png) +5. Haz clic en **Actualizar una respuesta guardada**. ![Actualizar una respuesta guardada](/assets/images/help/settings/saved-replies-save-edit.png) + +### Further reading + +- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" +- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" +- "[Usar respuestas guardadas](/articles/using-saved-replies)" diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md new file mode 100644 index 0000000000000..89a6332bdb5e2 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md @@ -0,0 +1,14 @@ +--- +title: Editar y compartir contenido con gists +intro: '' +mapTopic: verdadero +redirect_from: + - /categories/23/articles/ + - /categories/gists/ + - /articles/editing-and-sharing-content-with-gists +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md new file mode 100644 index 0000000000000..b901cecd21fed --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md @@ -0,0 +1,32 @@ +--- +title: Bifurcar y clonar gists +intro: 'Los gists son en realidad repositorios de Git, lo que significa que puedes bifurcar o clonar cualquier gist, aunque no seas el autor original. También puedes ver el historial completo de confirmaciones de un gist, incluidas las diferencias.' +redirect_from: + - /articles/forking-and-cloning-gists +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Bifurcar gists + +Each gist indicates which forks have activity, making it easy to find interesting changes from others. + +![Bifurcaciones del gist](/assets/images/help/gist/gist_forks.png) + +### Clonar gists + +Si deseas hacer cambios locales en un gist y subirlos a la web, puedes clonar un gist y hacer confirmaciones de la misma manera que lo harías con cualquier repositorio de Git. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". + +![Botón Clonar gist](/assets/images/help/gist/gist_clone_btn.png) + +### Ver el historial de confirmaciones de un gist + +Para ver el historial completo de confirmaciones de un gist, haz clic en la pestaña "Revisiones" en la parte superior del gist. + +![Pestaña Revisiones de gist](/assets/images/help/gist/gist_revisions_tab.png) + +Verás el historial completo de confirmaciones del gist con sus diferencias. + +![Página de revisiones de gist](/assets/images/help/gist/gist_history.png) diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md new file mode 100644 index 0000000000000..7fbb9e2f3a367 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md @@ -0,0 +1,14 @@ +--- +title: Introducción a la escritura y el formato en GitHub +redirect_from: + - /articles/markdown-basics/ + - /articles/things-you-can-do-in-a-text-area-on-github/ + - /articles/getting-started-with-writing-and-formatting-on-github +intro: 'Puedes usar características simples para darles formato a tus comentarios e interactuar con otros en propuestas, solicitudes de extracción y wikis en GitHub.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/writing-on-github/index.md b/translations/es-ES/content/github/writing-on-github/index.md new file mode 100644 index 0000000000000..30d922dc04d1e --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/index.md @@ -0,0 +1,32 @@ +--- +title: Escribir en GitHub +redirect_from: + - /categories/88/articles/ + - /articles/github-flavored-markdown/ + - /articles/writing-on-github/ + - /categories/writing-on-github +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +### Índice + +{% topic_link_in_list /getting-started-with-writing-and-formatting-on-github %} + {% link_in_list /about-writing-and-formatting-on-github %} + {% link_in_list /basic-writing-and-formatting-syntax %} +{% topic_link_in_list /working-with-advanced-formatting %} + {% link_in_list /organizing-information-with-tables %} + {% link_in_list /creating-and-highlighting-code-blocks %} + {% link_in_list /autolinked-references-and-urls %} +{% topic_link_in_list /working-with-saved-replies %} + {% link_in_list /about-saved-replies %} + {% link_in_list /creating-a-saved-reply %} + {% link_in_list /editing-a-saved-reply %} + {% link_in_list /deleting-a-saved-reply %} + {% link_in_list /using-saved-replies %} +{% topic_link_in_list /editing-and-sharing-content-with-gists %} + {% link_in_list /creating-gists %} + {% link_in_list /forking-and-cloning-gists %} diff --git a/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md b/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md new file mode 100644 index 0000000000000..2f24e8bcd8afa --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md @@ -0,0 +1,77 @@ +--- +title: Organizar la información en tablas +intro: 'Puedes construir tablas para organizar la información en comentarios, propuestas, solicitudes de extracción y wikis.' +redirect_from: + - /articles/organizing-information-with-tables +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Crear una tabla + +Puede crear tablas con barras verticales `|` y guiones `-`. Los guiones se usan para crear el encabezado de cada columna, mientras que las barras verticales separan cada columna. Debes incluir una línea en blanco antes de tu tabla para que se representen correctamente. + +``` + +| Primer encabezado | Segundo encabezado | +| ------------- | ------------- | +| Contenido de la celda | Contenido de la celda | +| Contenido de la celda | Contenido de la celda | +``` + +![Tabla presentada](/assets/images/help/writing/table-basic-rendered.png) + +Las barras verticales en cada lado de la tabla son opcionales. + +Las celdas pueden variar en el ancho y no es necesario que estén perfectamente alineadas dentro de las columnas. Debe haber al menos tres guiones en cada columna de la línea de encabezamiento. + +``` +| Comando | Descripción | +| --- | --- | +| git status | Enumera todos los archivos nuevos o modificados | +| git diff | Muestra las diferencias de archivo que no han sido preparadas | +``` + +![Tabla presentada con ancho de celda variado](/assets/images/help/writing/table-varied-columns-rendered.png) + +### Formatear el contenido dentro de tu tabla + +Puedes utilizar [formato](/articles/basic-writing-and-formatting-syntax) como enlaces, bloques de códigos insertados y el estilo de texto dentro de tu tabla: + +``` +| Comando | Descripción | +| --- | --- | +| `git status` | Enumera todos los archivos *nuevos o modificados* | +| `git diff` | Muestra las diferencias de archivo que **no han sido** preparadas | +``` + +![Tabla presentada con texto formateado](/assets/images/help/writing/table-inline-formatting-rendered.png) + +Puedes alinear el texto a la izquierda, la derecha o en el centro de una columna al incluir dos puntos `:` a la izquierda, la derecha, o en ambos lados de los guiones dentro de la línea de encabezamiento. + +``` +| Alineado a la izquierda | Alineado en el centro | Alineado a la derecha | +| :--- | :---: | ---: | +| git status | git status | git status | +| git diff | git diff | git diff | +``` + +![Tabla presentada con alineación de texto a la izquierda, a la derecha o al centro](/assets/images/help/writing/table-aligned-text-rendered.png) + +Para incluir una barra vertical `|` como contenido dentro de tu celda, utiliza una `\` antes de la barra: + +``` +| Nombre | Símbolo | +| --- | --- | +| Comilla simple | ` | +| Barra vertical | \| | +``` + +![Tabla presentada con una barra vertical liberada](/assets/images/help/writing/table-escaped-character-rendered.png) + +### Further reading + +- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) +- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/using-saved-replies.md b/translations/es-ES/content/github/writing-on-github/using-saved-replies.md new file mode 100644 index 0000000000000..3b0b823c48606 --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/using-saved-replies.md @@ -0,0 +1,30 @@ +--- +title: Utilizar respuestas guardadas +intro: 'Cuando comentas una propuesta o solicitud de extracción, puedes agregar una respuesta guardada que ya hayas establecido. La respuesta guardada puede ser todo el comentario o, si quieres personalizarlo, puedes agregar o eliminar contenido.' +redirect_from: + - /articles/using-saved-replies +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +2. Haz clic en la propuesta o solicitud de extracción deseada. +3. Para agregar una respuesta guardada, en el campo de comentarios, haz clic en {% octicon "reply" aria-label="The mail reply" %}. ![Botón Saved replies (Respuestas guardadas)](/assets/images/help/writing/saved-replies-button.png) +4. Desde la lista, selecciona la respuesta guardada que quieres agregar en el comentario. ![Respuestas guardadas](/assets/images/help/settings/saved-replies.png) + +{% tip %} + +**Tips:** +- Puedes utilizar un atajo del teclado para completar automáticamente el comentario con una respuesta guardada. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#comments)". +- Puedes filtrar la lista escribiendo el título de la respuesta guardada. + +{% endtip %} + +### Further reading + +- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" +- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" +- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md new file mode 100644 index 0000000000000..34a24c3e5718a --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md @@ -0,0 +1,12 @@ +--- +title: Trabajar con formato avanzado +intro: 'Los formatos como tablas, resaltado de la sintaxis y enlace automático te permiten organizar la información compleja claramente en tus solicitudes de extracción, propuestas y comentarios.' +mapTopic: verdadero +redirect_from: + - /articles/working-with-advanced-formatting +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md new file mode 100644 index 0000000000000..c211c9df3eb7b --- /dev/null +++ b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md @@ -0,0 +1,12 @@ +--- +title: Trabajar con respuestas guardadas +intro: 'Para ahorrar tiempo y asegurarte de enviar un mensaje consistente, puedes agregar respuestas guardadas a las propuestas y los comentarios de la solicitud de extracción.' +mapTopic: verdadero +redirect_from: + - /articles/working-with-saved-replies +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + diff --git a/translations/es-ES/content/graphql/README.md b/translations/es-ES/content/graphql/README.md new file mode 100644 index 0000000000000..c07c3b3d14342 --- /dev/null +++ b/translations/es-ES/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +¡El directorio de `/content/graphql` es donde viven los documentos de la API de GraphQL de GitHub! + +* Los directorios `/content/graphql/guides` y `/content/graphql/overview` contienen artículos que pueden editar las personas. +* El directorio `/content/graphql/reference` contiene un artículo para cada tipo de datos de GraphQL que se utiliza en la API de GraphQL de GitHub. La mayoría del contenido en este directorio se procesa utilizando etiquetas de `include`. + + El contenido que se procesa con las etiquetas de `include` se toma del directorio `/lib/graphql/static`, el cual se genera automáticamente desde el código fuente de la API en GitHub, y las personas no pueden editarlo. Para obtener más información, consulta el archivo [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **Como resultado, no podemos aceptar contribuciones para el contenido de referencia de la API de GraphQL en este repositorio.** diff --git a/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md new file mode 100644 index 0000000000000..d6ae97f9fa56a --- /dev/null +++ b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md @@ -0,0 +1,412 @@ +--- +title: Formar llamados con GraphQl +intro: 'Aprende cómo autenticarte en la API de GraphQL, y luego cómo crear y ejecutar consultas y mutaciones.' +redirect_from: + - /v4/guides/forming-calls + - /graphql/guides/forming-calls +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Autenticarse con GraphQL + +Para comunicarte con el servidor de GraphQL, deberás tener un token OAuth con el alcance correcto. + +Sigue los pasos en "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" para crear un token. Los alcances que requieres dependen del tipo de datos que quieras solicitar. Por ejemplo, selecciona los alcances del **Usuario** para solicitar datos de usuario. Si necesitas acceder a la información de un repositorio, selecciona los alcances de **Repositorio** adecuados. + +{% if currentVersion == "free-pro-team@latest" %} + +Para empatar el comportamiento del [Explorador de GraphQL](/graphql/guides/using-the-explorer), solicita los siguientes alcances: + +{% else %} + +Se recomiendan los siguientes alcances: + +{% endif %} + +``` +user +public_repo +repo +repo_deployment +repo:status +read:repo_hook +read:org +read:public_key +read:gpg_key +``` + +La API te notifica si algún recurso requiere de un alcance específico. + +### Terminal de GraphQL + +La API de REST tiene varias terminales; la API de GraphQL solo tiene una terminal: + +
{% data variables.product.graphql_url_pre %}
+ +La terminal permanece constante sin importar la operación que realices. + +### Comunicarse con GraphQL + +Ya que las operaciones de GraphQL consisten en JSON de línea múltiple, GitHub te recomienda utilizar el [Explorador](/graphql/guides/using-the-explorer) para hacer llamados de GraphQL. También puedes utilizar cURL o cualquier otra biblioteca que entienda HTTP. + +En REST, [Los verbos HTTP](/rest#http-verbs) determinan la operación realizada. En GraphQL, proporcionarás un cuerpo codificado con JSON ya sea que realices una consulta o una mutación, para que el verbo HTTP sea `POST`. La excepción es una [consulta de introspección](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), lo cual es un simple `GET` en la terminal. Para obtener más información sobre GraphQL contra REST, consulta la sección "[Migrarse desde REST a GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". + +Para consultar GraphQL utilizando cURL, realiza una solicitud de `POST` con una carga útil de JSON. La carga útil deberá contener una cadena llamada `query`: + +```shell +curl -H "Authorization: bearer token" -X POST -d " \ + { \ + \"query\": \"query { viewer { login }}\" \ + } \ +" {% data variables.product.graphql_url_code %} +``` + +{% tip %} + +**Nota**: El valor de cadena de `"query"` deve escaoar caracteres de nueva línea o el modelo no lo analizará correctamente. Para el cuerpo `POST`, utiliza comillas dobles externas y comillas dobles internas escapadas. + +{% endtip %} + +#### Acerca de las operaciones de consulta y mutación + +Los dos tipos de operación permitidos en la API de GraphQL de GitHub son _consultas_ y _mutaciones_. Comparando GraphQL con REST, las consultas operan como solicitudes de tipo `GET`, mientras que las mutaciónes operan como `POST`/`PATCH`/`DELETE`. El [nombre de la mutación](/graphql/reference/mutations) determina qué modificación se llevará a cabo. + +Para obtener información acerca de la limitación de tasas, consulta la sección "[Limitaciones de recursos para GraphQL](/graphql/overview/resource-limitations)". + +Las consultas y mutaciones comparten formatos similares con algunas diferencias importantes. + +#### Acerca de las consultas + +Las consultas de GraphQL devuelven únicamente datos que especificas. Para formar una consulta, debes especificar [campos dentro de campos](/graphql/guides/introduction-to-graphql#field) (tambien conocidos como _subcampos anidados_) hasta que te devuelva únicamente [escalares](/graphql/reference/scalars). + +Las consultas se estructuran de la siguiente forma: + +
query {
+  JSON objects to return
+}
+ +Para ver un ejemplo de uso real, consulta "[Ejemplo de consulta](#example-query)". + +#### Acerca de las mutaciones + +Para formar una mutación, debes especificar tres cosas: + +1. _Nombre de la mutación_. El Tipo de modificación que quieres realizar. +2. _Objeto de entrada_. Los datos que quieres enviar al servidor, compuestos de _campos de entrada_. Pásalo como un argumento al nombre de la mutación. +3. _Objeto de la carga útil_. Los datos que quieres retribuir del servidor, compuestos de _campos de devolución_. Pásalos como el cuerpo del nombre de la mutación. + +Las mutaciones se estructuran de la siguiente forma: + +
mutation {
+  mutationName(input: {MutationNameInput!}) {
+    MutationNamePayload
+  }
+}
+ +El objeto de entrada en este ejemplo es `MutationNameInput`, y la carga útil del objeto es `MutationNamePayload`. + +En la referencia de [mutaciones](/graphql/reference/mutations), los _campos de entrada_ listados son los que quieres pasar como el objeto de entrada. Los _campos de devolución_ son lo que pasas como el objeto de carga útil. + +Para ver un ejemplo de uso real, consulta "[Ejemplo de mutación](#example-mutation)". + +### Trabajar con variables + +Las [variables](https://graphql.github.io/learn/queries/#variables) pueden conformar consultas más dinámicas y poderosas, y pueden reducir la complejidad cuando pasas objetos de entrada de las mutaciones. + +{% note %} + +**Nota**: si estás utilizando el explorador, asegúrate de ingresar las variables en el [Panel de Variables de Consulta](/graphql/guides/using-the-explorer#using-the-variable-pane), y no incluyas la palabra `variables` antes del objeto JSON. + +{% endnote %} + +Aquí hay una consulta de ejemplo con una sola variable: + +```graphql +query($number_of_repos:Int!) query($number_of_repos:Int!) { + viewer { + name + repositories(last: $number_of_repos) { + nodes { + name + } + } + } +} +variables { + "number_of_repos": 3 +} +``` + +Hay tres pasos para utilizar las variables: + +1. Definir la variable fuera de la operación en un objeto `variables`: + + ```graphql + variables { + "number_of_repos": 3 + } + ``` + + El objeto debe ser un JSON válido. Este ejemplo muestra una variable de tipo `Int`, pero es posible definir tipos de variable más complejos, tales como los objetos de entrada. También puedes definir variables múltiples aquí. + +2. Pasa la variable a la operación como un argumento: + + ```graphql + query($number_of_repos:Int!){ + ``` + + El argumento es un par de valor-clave, en donde la clave es el _nombre_ que comienza con `$` (por ejemplo, `$number_of_repos`), y el valor es el _tipo_ (por ejemplo, `Int`). Agrega un `!` para indicar si se requiere el tipo. Si has identificado variables múltiples, inclúyelas aquí como argumentos múltiples. + +3. Utiliza la variable dentro de la operación: + + ```graphql + repositories(last: $number_of_repos) { + ``` + + En este ejemplo, sustituimos la variable por la cantidad de repositorios a devolver. Especificamos un tipo en el paso 2, ya que GraphQL requiere de una escritura inflexible. + +Este proceso hace dinámico al argumento de la consulta. Ahora podemos simplemente cambiar el valor en el objeto `variables` y mantener el resto del query tal cual. + +Utilizar variables como argumentos te permite actualizar los valores en el objeto `variables` dinámicamente sin cambiar la consulta. + +### Consulta de ejemplo + +Analicemos una consulta más compleja y pongamos esta información en contexto. + +La siguiente consulta busca el repositorio `octocat/Hello-World`, encuentra los 20 informes de problemas más recientes que se han cerrado, y devuelve el título de cada informe de problemas, la URL, y las primeras 5 etiquetas: + +```graphql +query { + repository(owner:"octocat", name:"Hello-World") { + issues(last:20, states:CLOSED) { + edges { + node { + title + url + labels(first:5) { + edges { + node { + name + } + } + } + } + } + } + } +} +``` + +Analizando la composición línea por línea: + +* `query {` + + Ya que queremos leer los dtos del servidor, y no modoficarlo, `query` es la operación raíz. (si no especificas una operación, `query` también es la operación predeterimanda). + +* `repository(owner:"octocat", name:"Hello-World") {` + + Para iniciar la consulta, queremos encontrar un objeto [`repository`](/graphql/reference/objects#repository). La validación del modelo indica que este objeto requiere un argumento `owner` y `name`. + +* `issues(last:20, states:CLOSED) {` + + Para explicar que se buscan todos los informes de problemas en el repositorio, llamamos al objeto `issues`. (_Podríamos_ consultar un solo `issue` en un `repository`, pero eso necesitaría que sepamos el número del informe de problemas que queremos se devuelva y proporcionarlo como argumento). + + Algunos detalles acerca del objeto `issues`: + + - Los [docs](/graphql/reference/objects#repository) nos dicen que este objeto es del tipo `IssueConnection`. + - La validación del modelo indica que este objeto requiere de una cantidad de resultados `last` o `first` como un argumento, así que proporcionamos `20`. + - Los [docs](/graphql/reference/objects#repository) también nos dicen que este objeto acepta un argumento `sttes`, el cual es un enumerador [`IssueState`](/graphql/reference/enums#issuestate) que acepta valores de `OPEN` o `CLOSED`. Para encontrar únicamente los informes de problemas cerrados, le damos a la clave `states` un valor de `CLOSED`. + +* `edges {` + + Sabemos que `issues` es una conexión, ya que tiene el tipo `IssueConnection`. Para devolver datos acerca de los informes de problemas individuales, tenemos que acceder al nodo a través de `edges`. + +* `node {` + + Aquí devolvemos el nodo al final del borde. Los [docs `IssueConnection`](/graphql/reference/objects#issueconnection) indican que el nodo al final del tipo `IssueConnection` es un objeto `Issue`. + +* Ahora que sabemos que estamos recuperando un objeto `Issue`, podemos ver al [docs](/graphql/reference/objects#issue) y especificar los campos que queremos recuperar: + + ```graphql + title + url + labels(first:5) { + edges { + node { + name + } + } + } + ``` + + Aquí especificamos los campos `title`, `url`, y `labels` del objeto `Issue`. + + El campo `labels` tiene el tipo [`LabelConnection`](/graphql/reference/objects#labelconnection). Así como el con el objeto `issues`, ya que `labels` es una conexión, debemos navegar por sus bordes hacia un nodo conectado: el objeto `label`. En el nodo, podemos especificar los campos del objeto `label` que intentamos recuperar, en este caso, `name`. + +Notarás que ejecutar esta consulta en el repositorio público `Hello-World` de Octocat no recuperará muchas etiquetas. Intenta ejecutarlo en uno de tus propios repositorios que utilice etiquetas, y seguramente verás la diferencia. + +### Mutación de ejemplo + +Las mutaciones a menudo requieren información que solo puedes encontrar si realizas una consulta primero. Este ejemplo muestra dos operaciones: + +1. Una consulta para obtener la ID de un informe de problemas. +2. Una mutación para agregar una reacción de emoji a dicho informe. + +```graphql +query FindIssueID { + repository(owner:"octocat", name:"Hello-World") { + issue(number:349) { + id + } + } +} + +mutation AddReactionToIssue { + addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) { + reaction { + content + } + subject { + id + } + } +} +``` + +{% tip %} + +Aunque puedes incluir una consulta y una mutación en la misma ventana del explorador si le das nombres ( en este ejemplo, `FindIssueID` y `AddReactionToIssue`), las operaciones se ejecutará como llamados separados a la terminal de GraphQL. No se puede realizar una consulta al mismo tiempo que una mutación, o viceversa. + +{% endtip %} + +Analicemos el ejemplo. La tarea parece simple: agregar una reacción de emoji a un informe de problemas. + +Así que, ¿qué es lo que sabemos para comenzar con la consulta? Aún no sabemos nada. + +Ya que queremos modificar los datos en el servidor (agregar un emoji a un informe de problemas), comenzamos buscando el modelo para una mutación útil. Los docs de referencia muestran la mutación [`addReaction`](/graphql/reference/mutations#addreaction) con la descripción: `Adds a reaction to a subject.`. ¡Perfecto! + +Los documentos para la mutación listan tres campos de entrada: + +* `clientMutationId` (`String`) +* `subjectId` (`ID!`) +* `content` (`ReactionContent!`) + +Los signos `!` indican que `subjectId` y `content` son campos requeridos. Hace sentido que se requiera de un `content`: queremos agregar una reacción, así que necesitaremos especificar qué emoji se utilizará. + +Pero, ¿por qué se requiere la `subjectId`? Esto es porque `subjectId` es la única manera de identificar a _cuál_ informe de problemas en _cuál_ repositorio se reaccionará. + +Es por esto que comenzamos el ejemplo con una consulta: para obtener la `ID`. + +Examinemos la consulta línea por línea: + +* `query FindIssueID {` + + Aquí estamos realizando una consulta, y la nombramos `FindIssueID`. Nota que el nombrar una consulta es opcional; le dimos un nombre para que podamos incluirlo en la misma ventana del explorador que utiliza la mutación. + +* `repository(owner:"octocat", name:"Hello-World") {` + + Especificamos el repositorio consultando el objeto `repository` y pasando los argumentos `owner` y `name`. + +* `issue(number:349) {` + + Especificamos el informe de problemas al cual se reaccionará consultando el objeto `issue` y pasando un argumento `number`. + +* `id` + + Aquí es donde recuperamos la `id` de `https://github.com/octocat/Hello-World/issues/349` para pasar como la `subjectId`. + +Cuando ejecutamos la consulta, obtenemos la `id`: `MDU6SXNzdWUyMzEzOTE1NTE=` + +{% tip %} + +**Nota**: La `id` que se devuelve en la consulta es el valor que pasaremos como la `subjectID` en la mutación. Ni los docs ni la introspección de modelo indicarán esta relación; necesitarás entender los conceptos detrás de los nombres para averiguarla. + +{% endtip %} + +Una vez conociendo la ID, podemos proceder con la mutación: + +* `mutation AddReactionToIssue {` + + Aquí realizamos una mutación, y la nombramos `AddReactionToIssue`. Como con las consultas, nombrar una mutación es opcional; le dimos un nombre para poder incluirlo en la misma ventana del explorador que la consulta. + +* `addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {` + + Examinemos esta línea: + + - `addReaction` es el nombre de la mutación. + - `input` es la clave de argumento requerida. Esto siempre será la `input` para una mutación. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` es el valor requerido del argumento. Esto siempre será un [objeto de entrada](/graphql/reference/input-objects) (de ahí las corcheas) compuesto de campos de entrada (`subjectId` y `content` en este caso) para una mutación. + + ¿Cómo sabemos qué valor utilizar para el contenido? Los [docs `addReaction`](/graphql/reference/mutations#addreaction) nos dicen que el campo `content` es de tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), lo cual es un [enumerador](/graphql/reference/enums) ya que solo ciertas reacciones de emoji son compatibles con los informes de problemas de GitHub. Estos son los valores permitidos para las reacciones (nota que algunos valores son diferentes de sus nombres de emoji correspondientes): + + {% data reusables.repositories.reaction_list %} + +* El resto del llamado se compone del objeto de carga útil. Aquí es donde especificamos los datos que queremos recuperar del servidor después de que realicemos la mutación. Estas líneas vienen de los [docs `AddReaction`](/graphql/reference/mutations#addreaction), que tienen tres campos de recuperación posibles: + + - `clientMutationId` (`String`) + - `reaction` (`Reaction!`) + - `subject` (`Reactable!`) + + En este ejemplo, recuperamos los dos campos requeridos (`reaction` y `subject`), ambos de los cuales tienen subcampos requeridos (respectivamente, `content` y `id`). + +Cuando ejecutamos la mutación, esta es la respuesta: + +```json +{ + "data": { + "addReaction": { + "reaction": { + "content": "HOORAY" + }, + "subject": { + "id": "MDU6SXNzdWUyMTc5NTQ0OTc=" + } + } + } +} +``` + +¡Listo! Revisa tu [reacción al informe de problemas](https://github.com/octocat/Hello-World/issues/349) pasando el puntero del mouse sobre :tada: para encontrar tu nombre de usuario. + +Una última nota: cuando pasas varios campos en un objeto de entrada, la sintaxis puede ser difícil de manejar. Mover los campos hacia una [variable](#working-with-variables) puede ayudar. Así es como podrías reescribir la mutación original utilizando una variable: + +```graphql +mutation($myVar:AddReactionInput!) mutation($myVar:AddReactionInput!) { + addReaction(input:$myVar) { + reaction { + content + } + subject { + id + } + } +} +variables { + "myVar": { + "subjectId":"MDU6SXNzdWUyMTc5NTQ0OTc=", + "content":"HOORAY" + } +} +``` + +{% note %} + +Podrás notar que el valor de campo `content` en el ejemplo pasado (en donde se usa directamente en la mutación) no tiene comillas encerrando a `HOORAY`, pero sí las tiene cuando se incluye en la variable. Esto es por una razón: +* Cuando utlilzas `content` directamente en la mutación, el modelo espera que el valor sea de tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), lo cual es un _enumerador_, no una cadena. La validación del modelo arrojará un error si agregas comillas antes y después del valor de enumerador, ya que éstas están reservadas para las cadenas. +* Cuando utilizas `content` en una variable, la sección de variables debe ser un JSON válido, así que las comillas son necesarias. La validación del modelo interpreta correctamente el tipo `ReactionContent` cuando se pasa la variable a la mutación durante la ejecución. + +Para obtener más información acerca de la diferencia entre enumeradores y cadenas, consulta [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). + +{% endnote %} + +### Further reading + +Puedes hacer mucho _más_ cuando conformes llamados de GraphQL. Aquí hay algunos lugares que te pueden interesar posteriormente: + +* [Paginación](https://graphql.github.io/learn/pagination/) +* [Fragmentos](https://graphql.github.io/learn/queries/#fragments) +* [Fragmentos dentro de líneas](https://graphql.github.io/learn/queries/#inline-fragments) +* [Directivas](https://graphql.github.io/learn/queries/#directives) diff --git a/translations/es-ES/content/graphql/guides/index.md b/translations/es-ES/content/graphql/guides/index.md new file mode 100644 index 0000000000000..52aea11771b68 --- /dev/null +++ b/translations/es-ES/content/graphql/guides/index.md @@ -0,0 +1,22 @@ +--- +title: Guías +intro: 'Aprende sobre como emepzar con GraphQL, migrarte desde REST hacia GraphQL, y cómo utilizar la API de GraphQL de GitHub para tareas diversas.' +redirect_from: + - /v4/guides +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_in_list /introduction-to-graphql %} + +{% link_in_list /forming-calls-with-graphql %} + +{% link_in_list /using-global-node-ids %} + +{% link_in_list /migrating-from-rest-to-graphql %} + +{% link_in_list /using-the-explorer %} + +{% link_in_list /managing-enterprise-accounts %} diff --git a/translations/es-ES/content/graphql/guides/introduction-to-graphql.md b/translations/es-ES/content/graphql/guides/introduction-to-graphql.md new file mode 100644 index 0000000000000..c730421fef964 --- /dev/null +++ b/translations/es-ES/content/graphql/guides/introduction-to-graphql.md @@ -0,0 +1,133 @@ +--- +title: Introducción a GraphQL +intro: Aprende terminología y conceptos útiles para utilizar la API de GraphQL de GitHub. +redirect_from: + - /v4/guides/intro-to-graphql + - /graphql/guides/intro-to-graphql +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Terminología de GraphQL + +La API de GraphQL de GitHub representa un cambio conceptual y arquitectónico de la API de REST de GitHub. Seguramente encontrarás nueva terminología en los [documentos de referencia](/graphql) de la API de GraphQL. + +### Modelo + +Un modelo define un tipo de sistema de la API de GraphQL. Describe el conjunto de datos posibles (objetos, campos, relaciones, todo) a los que puede acceder un cliente. Los llamados desde el cliente se [validan](https://graphql.github.io/learn/validation/) y [ejecutan](https://graphql.github.io/learn/execution/) contra un modelo. Un cliente puede encontrar información acerca del modelo a través de [introspección](#discovering-the-graphql-api). UN modelo reside en el servidor de la API de GraphQL. Para obtener más información, consulta la sección "[Descubriendo la API de GraphQL](#discovering-the-graphql-api)". + +### Campo + +Un campo es una unidad de datos que puedes recuperar de un objeto. Como dicen los [documentos oficiales de GraphQL](https://graphql.github.io/learn/schema/): "El lenguaje de consulta GraphQL se trata básicamente de seleccionar campos en los objetos". + +Las [especificaciones oficiales](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) dicen también acerca de los campos: + +> Todas las operaciones de GraphQL deben especificar sus selecciones en campos que regresarán valores escalares para garantizar una respuesta conformada sin ambigüedad. + +Esto significa que si intentas recuperar un campo que no es un valor escalar, la validación del modelo arrojará un error. Debes agregar subcampos anidados hasta que todos los campos recuperen valores escalares. + +### Argumento + +Un argumento es un conjuto de pares clave-valor adjuntos a un campo específico. Algunos campos requieren un argumento. Las [mutaciones](/graphql/guides/forming-calls-with-graphql#about-mutations) requieren un objeto de entrada como argumento. + +### Implementación + +El modelo de GraphQL podría utilizar el término _implementa_ para definir cómo un objeto hereda de una [interface](/graphql/reference/interfaces). + +Aquí se muestra un ejemplo artificial de un modelo que define la interface `X` y el objeto `Y`: + +``` +interface X { + some_field: String! + other_field: String! +} + +type Y implements X { + some_field: String! + other_field: String! + new_field: String! +} +``` + +Esto significa que el objeto `Y` requiere los mismos tipos de campos/argumentos/recuperaciones que requiere la interface `X`, mientras que agregan nuevos campos específicos para el objeto `Y`. (El signo `!` significa que el campo es requerido). + +En los documentos de referencia, podrás notar que: + +* Cada [objeto](/graphql/reference/objects) lista la(s) interface(s) _de la(s) cual(es) hereda_ debajo de **Implementa**. + +* Cada [interface](/graphql/reference/interfaces) lista los objetos _que heredan desde ella_ bajo **Implementaciones**. + +### Conexión + +Las conexiones permiten consultar objetos relacionados como parte del mismo llamado. Con las conexiones, puedes utilizar un solo llamado de GraphQL y, en contraste, tendrías que utilizar múltiples llamados en una API de REST. Para obtener más información, consulta "[Migrar de REST a GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". + +Es útil imaginar una gráfica: puntos conectados con líneas. Los puntos son nodos, las líneas son bordes. Una conexión define una relación entre nodos. + +### Borde + +Los bordes representan las conexiones entre nodos. Cuando consultas una conexión, cruzas sus bordes para obtener sus nodos. Cada campo de `edges` tiene un campo de `node` y uno de `cursor`. Los cursores se utilizan para la [paginación](https://graphql.github.io/learn/pagination/). + +### Nodo + +_Nodo_ es un término genérico para un objeto. Puedes buscar un nodo directamente, o puedes acceder a nodos relacionados a través de una conexión. Si especificas un `node` que no regrese un valor [escalar](/graphql/reference/scalars), deberás incluir los subcampos hasta que todos los campos recuperen valores escalares. Para obtener información sobre el acceso a las ID de los nodos a través de la API de REST y utilizarlos en las consultas de GraphQL, consulta la sección "[Utilizar ID de Nodos Globales](/graphql/guides/using-global-node-ids)". + +## Descubrir la API de GraphQL + +GraphQL es [introspectivo](https://graphql.github.io/learn/introspection/). Esto significa que puedes consultar un modelo de GraphQL para encontrar detalles de éste mismo. + +* Consulta `__schema` para listar todos los tipos definidos en el modelo y obtener detalles de cada uno: + + ```graphql +query { + __schema { + types { + name + kind + description + fields { + name + } + } + } +} + ``` + +* Consulta `__type` para obtener detalles de cualquier tipo: + + ```graphql +query { + __type(name: "Repository") { + name + kind + description + fields { + name + } + } +} + ``` + +* También puedes ejecutar una _consulta de introspección_ del modelo a través de la solicitud `GET`: + + ```shell + $ curl -H "Authorization: bearer token" {% data variables.product.graphql_url_pre %} + ``` + + Estos resultados están en JSON, así que recomendamos imprimirlos notablemente para su lectura y búsqueda más fácil. Puedes utilizar una herramienta de línea de comandos como [jq](https://stedolan.github.io/jq/) o enlazar los resultados en `python -m json.tool` para lograrlo. + + Como alternativa, puedes pasar el tipo de medios `idl` para recuperar los resultados en formato IDL, el cual es una versión condensada del mismo modelo: + + ```shell + $ curl -H "Authorization: bearer token" -H "Accept: application/vnd.github.v4.idl" \ + {% data variables.product.graphql_url_pre %} + ``` + + {% note %} + + **Nota**: La consulta de introspección probablemente es la única solicitud de tipo `GET` que ejecutarás en GraphQL. Si estás pasando un cuerpo, el método de solicitud de GraphQL es de tipo `POST`, ya sea para consultas o mutaciones. + + {% endnote %} + + Para obtener más información acerca de realizar consultas, consulta la sección "[Formar llamados con GraphQL](/graphql/guides/forming-calls-with-graphql)". diff --git a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md new file mode 100644 index 0000000000000..88f494c030591 --- /dev/null +++ b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md @@ -0,0 +1,198 @@ +--- +title: Administrar cuentas empresariales +intro: Puedes administrar tu cuenta empresarial y las organizaciones que le pertenecen con la API de GraphQL. +redirect_from: + - /v4/guides/managing-enterprise-accounts +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de administrar cuentas empresariales con GraphQL + +Para ayudarte a monitorear y hacer cambios en tu organización y mantener el cumplimiento, puedes utilizar la API de Cuentas Empresariales y la API de Bitácoras de Auditoría, las cuales se encuentran disponibles únicamente como API de GraphQL. + +Las terminales de cuenta empresarial funcionan tanto para GitHub Enterprise Cloud y GitHub Enterprise Server. + +GraphQL te permite solicitar y recuperar únicamente los datos que especificas. Por ejemplo, puedes crear una consulta de GraphQL, o hacer una solicitud de información, para ver todos los nuevos miembros que se agregaron a tu organización. O puedes hacer una mutación, o cambio, para invitar a un administrador a tu cuenta empresarial. + +Con la API de Bitácoras de Auditoria, puedes monitorear cuando alguien: +- Accede a tu configuración de organización o de repositorio. +- Cambia los permisos. +- Agrega o elimina usuarios en una organización, repositorio, o equipo. +- Promueve algún usuario a administrador. +- Cambia los permisos de GitHub App. + +La API de Bitácoras de Auditoría te permite mantener las copias de tus datos de bitácoras de auditoria. Para las consultas realizadas con la API de Bitácoras de Auditoria, la respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. Para encontrar una lista de los campos disponibles con la API de Bitácoras de Auditoria, consulta la "[interface AuditEntry](/graphql/reference/interfaces#auditentry/)". + +Con la API de Cuentas Empresariales puedes: +- Listar y revisar todas las organizaciones y repositorios que pertenecen a tu cuenta empresarial. +- Cambiar la configuración de la cuenta empresarial. +- Configurar políticas para la configuración en tu cuenta empresarial y sus organizaciones. +- Invitar administradores a tu cuenta empresarial. +- Crear nuevas organizaciones en tu cuenta empresarial. + +Para encontrar una lista de los campos disponibles con la API de Cuentas Empresariales, consulta "[Campos y tipos de GraphQL para la API de cuenta empresarial](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)". + +### Comenzar a utilizar GraphQL para cuentas empresariales + +Sigue estos pasos para comenzar a utilizar GraphQL para administrar tus cuentas empresariales: + - Autenticarte con un token de acceso personal + - Elegir un cliente de GraphQL o utilizar el Explorador de GraphQL + - Configurar Insomnia para utilizar la API de GraphQL + +Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta de ejemplo utilizando la API de Cuentas Empresariales](#an-example-query-using-the-enterprise-accounts-api)". + +#### 1. Autenticarte con tu token de acceso personal + +1. Para autenticarte con GraphQL, necesitas generar un token de acceso personal (PAT) desde la configuración de desarrollador. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". + +2. Porporciona permisos de control total a tu token de acceso personal para las áreas de GHES a las que quisieras acceder. Para tener permiso total a los repositorios privados, organizaciones, equipos, datos de usuario y acceso a la facturación empresarial y datos de perfil, te recomendamos que selecciones estos alcances para tu token de acceso personal: + - `repo` + - `admin:org` + - `user` + - `admin:enterprise` + + Los alcances específicos para la cuenta empresarial son: + - `admin:enterprise`: otorga control total de las empresas (incluye`manage_billing:enterprise` y `read:enterprise`) + - `manage_billing:enterprise`: Lee y escribe datos de facturación de la empresa. + - `read:enterprise`: Lee datos del perfil empresarial. + + ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/permissions-for-access-token.png) + +4. Copia tu token de acceso personal y mantenlo en un lugar seguro hasta que lo agregues a tu cliente de GraphQL. + +#### 2. Elige un cliente de GraphQL + +Te recomendamos utilizar GraphiQL u otro cliente independiente de GraphQL que te permita configurar la URL base. + +También podrás considerar utilizar estos clientes de GraphQL: + - [Insomnia](https://insomnia.rest/graphql/) + - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) + - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/) + +Los siguientes pasos utilizarán Insomnia. + +#### 3. Configurar Insomnia para utilizar la API de GraphQL de GitHub con cuentas empresariales + +1. Agrega la url base y el método `POST` a tu cliente de GraphQL. Cuando utilices GraphQL para solicitar información (consultas), cambiar información (mutaciones), o transferir datos utilizando la API de GitHub, el método HTTP predeterminado es `POST` y la url base sigue esta sintaxis: + - Para tu instancia empresarial: `https:///api/graphql` + - Para GitHub Enterprise Cloud: `https://api.github.com/graphql` + +2. Para autenticarte, abre el menú de opciones de autenticación y selecciona **Token titular**. A continuación, agrega tu token de acceso personal, el cual habías copiado. + + ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) + + ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-bearer-token-option.png) + +3. Incluye la información del encabezado. + - Agrega `Content-Type` como el encabezado y `application/json` como el valor. ![Encabezado estándar](/assets/images/developer/graphql/json-content-type-header.png) ![Encabezado con valor de vista previa para la API de Bitácoras de Auditoría](/assets/images/developer/graphql/preview-header-for-2.18.png) + +Ahora estás listo para comenzar a hacer consultas. + +### Un ejemplo de consulta utilizando la API de Cuentas Empresariales + +Esta consulta de GraphQL solicita la cantidad total de repositorios `public` en cada una de las organizaciones de tus aplicativos utilizando la API de cuentas empresariales. Para personalizar esta consulta, reemplaza `` con el slug de tu instancia empresarial. + +```graphql +query publicRepositoriesByOrganization { + organizationOneAlias: organization(login: "") { + # How to use a fragment + ...repositories + } + organizationTwoAlias: organization(login: "") { + ...repositories + } + # organizationThreeAlias ... and so on up-to lets say 100 +} +# How to define a fragment +fragment repositories on Organization { + name + repositories(privacy: PUBLIC){ + totalCount + } +} +``` + +La siguiente consulta de GraphQL muestra lo retador que es recuperar la cantidad de repositorios `public` en cada organización sin utilizar la API de Cuenta Empresarial. Nota que la API de Cuentas Empresariales de GraphQL ha hecho esta tarea más simple para las empresas, ya que solo necesitas personalizar una sola variable. Para personalizar esta consulta, reemplaza `` y ``, etc. con los nombres de organización en tu instancia. + +```graphql +# Each organization is queried separately +{ + organizationOneAlias: organization(login: "nameOfOrganizationOne") { + # How to use a fragment + ...repositories + } + organizationTwoAlias: organization(login: "nameOfOrganizationTwo") { + ...repositories + } + # organizationThreeAlias ... and so on up-to lets say 100 +} + +## How to define a fragment +fragment repositories on Organization { + name + repositories(privacy: PUBLIC){ + totalCount + } +} +``` + +### Consulta a cada organización por separado + +```graphql +query publicRepositoriesByOrganization { + organizationOneAlias: organization(login: "") { + # How to use a fragment + ...repositories + } + organizationTwoAlias: organization(login: "") { + ...repositories + } + # organizationThreeAlias ... and so on up-to lets say 100 +} +# How to define a fragment +fragment repositories on Organization { + name + repositories(privacy: PUBLIC){ + totalCount + } +} +``` + +Esta consulta de GraphQL solicita las últimas 5 entradas de bitácora para una organización empresarial. Para personalizar este query, reemplaza `` y ``. + +```graphql +{ + organization(login: "") { + auditLog(last: 5, query: "actor:") { + edges { + node { + ... on AuditEntry { +# Get Audit Log Entry by 'Action' + action + actorLogin + createdAt +# User 'Action' was performed on + user{ + name + email + } + } + } + } + } + } +} +``` + +Para obtener más información acerca de cómo comenzar con GraphQL, consulta las secciónes "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)" y "[Formar Llamados con GraphQL](/graphql/guides/forming-calls-with-graphql)". + +### Campos y tipos de GraphQL para la API de Cuentas Empresariales + +Aquí tienes un resumen de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales. + +Para obtener más detalles acerca de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales, observa la barra lateral con las definiciones detalladas de GraphQL desde cualquier [página de referencia de GraphQL](/graphql). + +Puedes acceder a los documentos de referencia desde dentro del explorador de GraphQL en GitHub. Para obtener más información, consulta la sección "[Utilizar el explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)". Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/graphql/guides). diff --git a/translations/es-ES/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/es-ES/content/graphql/guides/migrating-from-rest-to-graphql.md new file mode 100644 index 0000000000000..817ab7e8ea5e7 --- /dev/null +++ b/translations/es-ES/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -0,0 +1,209 @@ +--- +title: Migrar desde Rest hacia GraphQL +intro: 'Aprende las mejores prácticas y consideraciones para migrar desde la API de Rest de {% data variables.product.prodname_dotcom %} hacia la API de GrpahQL de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/guides/migrating-from-rest + - /graphql/guides/migrating-from-rest +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Diferencias en la lógica de la API + +Migrar desde Rest hacia GraphQL represente un cambio significativo en la lógica de las API. Las diferencias entre REST como un estilo y GraphQL como una especificación hacen difícil —y a menudo indeseable— reemplazar los llamados de la API de REST con las consultas de la API de GraphQL de una forma uno a uno. Hemos incluido ejemplos específicos de migración a continuación. + +Para migrar tu código desde la [API de REST](/rest) hacia la API de GraphQL: + +- Revisa las [especificaciones de GraphQL](https://graphql.github.io/graphql-spec/June2018/) +- Revisa el [Modelo de GraphQL](/graphql/reference) de GitHUb +- Considera la manera en la que cualquier código existente que tengas interactúa con la API de REST de GitHub +- Utiliza las [ID de nodo global](/graphql/guides/using-global-node-ids) para referenciar los objetos entre las versiones de la API + +Las ventajas significativas de GraphQL incluyen: + +- [Obtener los datos que necesitas y únicamente eso](#example-getting-the-data-you-need-and-nothing-more) +- [Campos anidados](#example-nesting) +- [Escritura inflexible](#example-strong-typing) + +Aquí hay algunos ejemplos de cada una. + +## Ejemplo: obtener los datos que necesitas y únicamente eso + +Una sola llamada de la API de REST recupera una lista de los miembros de tu organización: +```shell +curl -v {% data variables.product.api_url_pre %}/orgs/:org/members +``` + +La carga útil de REST contiene datos en exceso si tu meta es recuperar únicamente los nombres y enlaces a los avatares. Sin embargo, la consulta de GraphQL recupera únicamente lo que especificas: + +```graphql +query { + organization(login:"github") { + membersWithRole(first: 100) { + edges { + node { + name + avatarUrl + } + } + } + } +} +``` + +Considera otro ejemplo: recuperar una lista de solicitudes de extracción y revisar si cada una es fusionable. El hacer una llamada a la API de REST recupera una lista de solicitudes de cambios y su [resumen de representaciones](/rest#summary-representations): +```shell +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls +``` + +El determinar si una solicitud de cambios se puede fusionar requiere que se recupere cada solicitud de cambios individualmente de acuerdo con su [representación detallada](/rest#detailed-representations) (una carga útil grande) y verificar si su atributo de `mergeable` es verdadero o falso: +```shell +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number +``` + +Con GraphQL, puedes recuperar únicamente los atributos `number` y `mergeable` para cada solicitud de extracción: + +```graphql +query { + repository(owner:"octocat", name:"Hello-World") { + pullRequests(last: 10) { + edges { + node { + number + mergeable + } + } + } + } +} +``` + +## Ejemplo: Anidar + +Hacer consultas con campos anidados te permite reemplazar varios llamados de REST con menos consultas de GraphQL. Por ejemplo, recuperar una solicitud de extracción junto con sus confirmaciones, comentarios no revisados, y revisiones utilizando la **API de REST** requiere de cuatro llamados por separado: +```shell +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/commits +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/issues/:number/comments +curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/reviews +``` + +Utilizando la **API de GraphQL**, puedes recuperar los datos con una sola consulta utilizando los campos anidados: + +```graphql +{ + repository(owner: "octocat", name: "Hello-World") { + pullRequest(number: 1) { + commits(first: 10) { + edges { + node { + commit { + oid + message + } + } + } + } + comments(first: 10) { + edges { + node { + body + author { + login + } + } + } + } + reviews(first: 10) { + edges { + node { + state + } + } + } + } + } +} +``` + +También puedes extender la capacidad de esta consulta si [sustituyes una variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) para el número de la solicitud de extracción. + +## Ejemplo: Escritura inflexible + +Los modelos de GraphQL tienen una escritura inflexible, lo cual hace más seguro el manejo de los datos. + +Considera como ejemplo agregar un comentario a un informe de problemas o solicitud de extracción utilizando una [mutación](/graphql/reference/mutations) de GraphQL, y por error, especificar un integral en vez de una cadena para el valor de [`clientMutationId`](/graphql/reference/mutations#addcomment): + +```graphql +mutation { + addComment(input:{clientMutationId: 1234, subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) "Looks good to me!"}) { + clientMutationId + commentEdge { + node { + body + repository { + id + name + nameWithOwner + } + issue { + number + } + } + } + } +} +``` + +Ejecutar esta consulta recuperará errores que especificarán los tipos esperados para esta operación: + +```json +{ + "data": null, + "errors": [ + { + "message": "Argument 'input' on Field 'addComment' has an invalid value. Expected type 'AddCommentInput!'.", + "locations": [ + { + "line": 3, + "column": 3 + } + ] + }, + { + "message": "Argument 'clientMutationId' on InputObject 'AddCommentInput' has an invalid value. Expected type 'String'.", + "locations": [ + { + "line": 3, + "column": 20 + } + ] + } + ] +} +``` + +Poner comillas en `1234` transformará el valor de un integral al de una cadena, el tipo esperado: + +```graphql +mutation { + addComment(input:{clientMutationId: "1234", subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) { + clientMutationId + commentEdge { + node { + body + repository { + id + name + nameWithOwner + } + issue { + number + } + } + } + } +} +``` diff --git a/translations/es-ES/content/graphql/guides/using-global-node-ids.md b/translations/es-ES/content/graphql/guides/using-global-node-ids.md new file mode 100644 index 0000000000000..836a41b28393d --- /dev/null +++ b/translations/es-ES/content/graphql/guides/using-global-node-ids.md @@ -0,0 +1,125 @@ +--- +title: Utilizar las ID de nodo global +intro: Puedes obtener ID de nodo global de objetos a través de la API de REST y utilizarlos en operaciones de GraphQL. +redirect_from: + - /v4/guides/using-global-node-ids +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes acceder a la mayoría de objetos en GitHub (usuarios, informes de problemas, solicitudes de extracción, etc.) utilizando ya sea la API de Rest o la de GraphQL. Con una [actualización reciente](https://developer.github.com/changes/2017-12-19-graphql-node-id/), puedes encontrar la **ID de nodo global** de muchos objetos desde dentro de la API de REST y utilizar estas ID en tus operaciones de GraphQL. + +{% note %} + +**Nota:** en REST, el campo de ID de nodo global se llama `node_id`. En GraphQL, es un campo de `id` en la interface del `node`. Para repasar lo que significa "nodo" en GraphQL, consulta la sección "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql#node)". + +{% endnote %} + +### Darle uso a las ID de nodo global + +Puedes seguir estos tres pasos para utilizar las ID de nodo global efectivamente: + +1. Llama a una terminal de REST que recupere el `node_id` de un objeto. +2. Encuentra el tipo del objeto en GraphQL. +3. Utiliza la ID y tipo para hacer una búsqueda directa de nodo en GraphQL. + +Revisemos un ejemplo. + +### 1. Llama a una terminal de REST que recupere la ID de nodo de un objeto + +Si [solicitas el usuario autenticado](/rest/reference/users#get-the-authenticated-user): + +```shell +$ curl -i -u username:token {% data variables.product.api_url_pre %}/user +``` + +obtendrás una respuesta que incluye el `node_id` del usuario autenticado: + +```json +{ + "login": "octocat", + "id": 1, + "avatar_url": "https://github.com/images/error/octocat_happy.gif", + "gravatar_id": "", + "url": "https://api.github.com/users/octocat", + "html_url": "https://github.com/octocat", + "followers_url": "https://api.github.com/users/octocat/followers", + "following_url": "https://api.github.com/users/octocat/following{/other_user}", + "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}", + "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/octocat/subscriptions", + "organizations_url": "https://api.github.com/users/octocat/orgs", + "repos_url": "https://api.github.com/users/octocat/repos", + "events_url": "https://api.github.com/users/octocat/events{/privacy}", + "received_events_url": "https://api.github.com/users/octocat/received_events", + "type": "User", + "site_admin": false, + "name": "monalisa octocat", + "company": "GitHub", + "blog": "https://github.com/blog", + "location": "San Francisco", + "email": "octocat@github.com", + "hireable": false, + "bio": "There once was...", + "public_repos": 2, + "public_gists": 1, + "followers": 20, + "following": 0, + "created_at": "2008-01-14T04:33:35Z", + "updated_at": "2008-01-14T04:33:35Z", + "private_gists": 81, + "total_private_repos": 100, + "owned_private_repos": 100, + "disk_usage": 10000, + "collaborators": 8, + "two_factor_authentication": true, + "plan": { + "name": "Medium", + "space": 400, + "private_repos": 20, + "collaborators": 0 + }, + "node_id": "MDQ6VXNlcjU4MzIzMQ==" +} +``` + +### 2. Encuentra el tipo de objeto en GraphQL + +En este ejemplo, el valor de `node_id` es `MDQ6VXNlcjU4MzIzMQ==`. Puedes utilizar este valor para consultar el mismo objeto en GraphQL. + +Aunque necesitas saber el _tipo_ del objeto primero. Puedes revisar el tipo con una consulta simple de GraphQl: + +```graphql +query { + node(id:"MDQ6VXNlcjU4MzIzMQ==") { + __typename + } +} +``` + +Este tipo de consulta —que es encontrar el nodo por ID— se conoce como "búsqueda directa de nodo". + +Cuando ejecutas esta consulta, encontrarás que el `__typename` es [`User`](/graphql/reference/objects#user). + +### 3. Haz una búsqueda directa de nodo en GraphQL + +Una vez que hayas confirmado el tipo, puedes utilizar un [fragmento dentro de la línea](https://graphql.github.io/learn/queries/#inline-fragments) para acceder al objeto por su ID y recuperar datos adicionales. En este ejemplo, definimos los campos que queremos consultar en `User`: + +```graphql +query { + node(id:"MDQ6VXNlcjU4MzIzMQ==") { + ... on User { + name + login + } + } +} +``` + +Este tipo de consulta es el acercamiento estándar para buscar un objeto por su ID de nodo global. + +### Utilizar las ID de nodo global en migraciones + +Cuando construyes integraciones que utilizan ya sea la API de REST o de GraphQL, la mejor práctica es persistir la ID de nodo global para que puedas referenciar fácilmente los objetos a través de las versiones de las API. Para obtener más información sobre cómo manejar la transición entre REST y GraphQL, consulta la sección "[Migrarse de REST a GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". diff --git a/translations/es-ES/content/graphql/guides/using-the-explorer.md b/translations/es-ES/content/graphql/guides/using-the-explorer.md new file mode 100644 index 0000000000000..6520b9a1ac4f7 --- /dev/null +++ b/translations/es-ES/content/graphql/guides/using-the-explorer.md @@ -0,0 +1,152 @@ +--- +title: Utilizar el Explorador +intro: 'Puedes ejecutar consultas en datos reales de {% data variables.product.prodname_dotcom %} utilizando el explorador de GraphQL, un ambiente de desarrollo integrado en tu buscador que incluye documentos, sintaxis resaltada y errores de validación.' +redirect_from: + - /v4/guides/using-the-explorer +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +## Acerca del explorador de GraphQL + +{% if currentVersion == "free-pro-team@latest" %} + +El [Explorador de GraphQL](/graphql/overview/explorer) es una instancia de [GraphQL](https://github.com/graphql/graphiql), la cual es una "IDE de GraphQL gráfica e interactiva en el mismo buscador". + +{% note %} + +**Nota**: {% data variables.product.prodname_dotcom %} ha inhabilitado las [mutaciones](/graphql/reference/mutations) en el explorador, pero puedes utilizarlas en tu propia instancia de GraphiQL. + +{% endnote %} + +{% else %} + +[GraphiQL](https://github.com/graphql/graphiql), también mencionado en esta documentación como el explorador de GraphQL, es una "IDE de GraphQL gráfica e interactiva en el mismo buscador". + +{% endif %} + +### Utilizar GrpahiQL + +Para utilizar la app de GraphiQL, descárgala e instálala desde https://github.com/skevy/graphiql-app. + +#### Configurar GraphiQL + +1. Obtén un [token de OAuth](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql). +1. Lanzar GraphiQL. +1. En la esquina superior derecha de GraphiQL, da clic en **Editar Encabezados de HTTP**. +1. En el campo **Clave**, ingresa `Authorization`. En el campo **Valor**, ingresa `Bearer `, en donde `` es tu token de OAuth generado. ![encabezados de graphiql](/assets/images/developer/graphiql-headers.png) +1. Da clic en la casilla a la derecha del token para guardarlo. +1. Para gregresar al editor, da clic fuera de el modo **Editar Encabezados de HTTP**. +1. En el campo **Terminal GraphQL** ingresa `{% data variables.product.graphql_url_pre %}`. +1. En el menú desplegable **Método**, selecciona **POST**. + +{% note %} + +**Nota**: Para obtener más información acerca del porqué `POST` es el método, consulta la sección "[Comunicarse con GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)". + +{% endnote %} + +Puedes probar tu acceso si te consultas a ti mismo: + +```graphql +query { + viewer { + login + } +} +``` + +Si todo funcionó correctamente, esto mostrará tu ingreso. Estás listo para comenzar a hacer consultas. + +### Acceder a los documentos de la barra lateral + +Todos los tipos en el modelo de GraphQL incluyen un campo de `description` compilado en la documentación. El pánel retráctil **Docs** en el costado derecho de la página del explorador te permite buscar documentación acerca de tu tipo de sistema. Los documentos se actualizan automáticamente y eliminarán los campos obsoletos. + +{% note %} + +La barra lateral de **Docs** tiene el mismo contenido que se genera automáticamente del modelo bajo "[Referencia](/graphql)", aunque con diferente formato en algunas partes. + +{% endnote %} + +### Utilizar el pánel de variable + +Algunos llamados de ejemplo incluyen [variables](/graphql/guides/forming-calls-with-graphql#working-with-variables) escritas como éstas: + +```graphql +query($number_of_repos:Int!){ + viewer { + name + repositories(last: $number_of_repos) { + nodes { + name + } + } + } +} +variables { + "number_of_repos": 3 +} +``` + +Este es el formato correcto para emitir la llamada a través de `POST` en cURL (mientras que [escapes las líneas nuevas](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)). + +Si quieres ejecutar la llamada en el explorador, ingresa el segmento `query` en el panel principal y las variables en el panel de **Variables de Consulta** debajo de éste. Omite la palabra `variables` en el explorador: + +```graphql +{ + "number_of_repos": 3 +} +``` + +### Solicitar soporte + +{% data reusables.support.help_resources %} + +### Solución de errores + +Ya que GraphQL es [introspectivo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), el explorador soporta: + +* Autocompleción inteligente consciente del modelo actual +* Vistas previas de validación de errores mientras tecleas + +Si ingresas una consulta que no esté bien estructurada o no pase el [modelo de validación](/graphql/guides/introduction-to-graphql#schema), un mensaje emergente te avisará de un error. Si ejecutas la consulta, el error se devolverá en el panel de respuesta. + +Una respuesta de GraphQL contiene varias claves: un hash de `data` y un arreglo de `errors`. + +```json +{ + "data": null, + "errors": [ + { + "message": "Objects must have selections (field 'nodes' returns Repository but has no selections)", + "locations": [ + { + "line": 5, + "column": 8 + } + ] + } + ] +} +``` + +Es posible que te encuentres con un error inesperado que no está relacionado con el modelo. Si esto pasa, el mensaje incluirá el código de referencia que puedes utilizar cuando reportas el problema: + +```json +{ + "data": null, + "errors": [ + { + "message": "Something went wrong while executing your query. This is most likely a GitHub bug. Please include \"7571:3FF6:552G94B:69F45B7:5913BBEQ\" when reporting this issue." + } + ] +} +``` + +{% note %} + +**Nota:** {% data variables.product.prodname_dotcom %} recomienda que revises si hay errores antes de utilizar datos en un ambiente productivo. En GraphQL, la falla no es total: algunas porciones de las consultas de GraphQL pueden tener éxito y otras pueden fallar. + +{% endnote %} diff --git a/translations/es-ES/content/graphql/index.md b/translations/es-ES/content/graphql/index.md new file mode 100644 index 0000000000000..50032283fb34f --- /dev/null +++ b/translations/es-ES/content/graphql/index.md @@ -0,0 +1,17 @@ +--- +title: API de GraphQL de GitHub +intro: 'Puedes utilizar la API de GraphQL de {% data variables.product.prodname_dotcom %} para crear consultas precisas y flexibles para los datos que necesitas integrar con {% data variables.product.prodname_dotcom %}.' +shortTitle: API de GraphQL +redirect_from: + - /v4 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_with_intro /overview %} + +{% link_with_intro /reference %} + +{% link_with_intro /guides %} diff --git a/translations/es-ES/content/graphql/overview/about-the-graphql-api.md b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md new file mode 100644 index 0000000000000..38c3e73bcb714 --- /dev/null +++ b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md @@ -0,0 +1,54 @@ +--- +title: Acerca de la API de GraphQL +intro: 'La API de GraphQL de {% data variables.product.prodname_dotcom %} ofrece flexibilidad y la capacidad de definir precisamente los datos que quieres recuperar.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Resumen + +Aquí hay algunos enlaces rápidos para ponerte en marcha con la API de GraphQL v4: + +* [Autenticación](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) +* [Terminal raíz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) +* [Introspección del modelo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) +* [Límites de tasa](/graphql/overview/resource-limitations) +* [Migrar desde REST](/graphql/guides/migrating-from-rest-to-graphql) + +### Acerca de GraphQL + +El lenguaje de consulta de [GraphQL](https://graphql.github.io/) es: + +* **Una [especificación](https://graphql.github.io/graphql-spec/June2018/).** La especificación determina la validez del [modelo](/graphql/guides/introduction-to-graphql#schema) en el servidor de la API. El modelo determina la validez de las llamadas al cliente. + +* **[Lenguaje inflexible](#about-the-graphql-schema-reference).** El modelo define el sistema de tipos de la API y todas las relaciones con objetos. + +* **[Introspectivo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** Un cliente puede consultar el modelo para obtener detalles del mismo. + +* **[Jerárquico](/graphql/guides/forming-calls-with-graphql).** La forma de un llamado de GraphQL imita la forma de los datos JSON que recupera. Los [Campos anidados](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) te permiten consultar y recibir únicamente los dtos que especificas en una sola transacción. + +* **Una capa de aplicación.** GraphQL no es un modelo de almacenamiento o un lenguaje de consulta de bases de datos. _graph_ se refiere a estructuras gráficas definidas en el modelo, en donde los [nodos](/graphql/guides/introduction-to-graphql#node) definen objetos y los [bordes](/graphql/guides/introduction-to-graphql#edge) definen relaciones entre objetos. La API recorre y recupera datos de la aplicación basándose en las definiciones del modelo, independientemente de cómo se almacenan los datos. + +### Por qué GitHub utiliza GraphQL + +GitHub eligió GraphQL para la API v4 porque ofrece significativamente más flexibilidad para nuestros intregradores. La capacidad de definir precisamente los datos que quieres —y _únicamente_ estos— es una ventaja poderosa sobre las terminales de la API de REST v3. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques. + +Para obtener más detalles acerca de por qué GitHub se ha migrado a GraphQL, consulta la[publicación de anuncios del blog](https://githubengineering.com/the-github-graphql-api/). + +### Acerca de la referencia del modelo de GraphQL + +Los documentos en la barra lateral se generan del [modelo](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) de GraphQL de {% data variables.product.prodname_dotcom %}. Todas las llamadas se validan y ejecutan contra el modelo. Utiliza estos documentos para encontrar los datos a los que puedes llamar: + +* Operaciones permitidas: [consultas](/graphql/reference/queries) y [mutaciones](/graphql/reference/mutations). + +* Tipos definidos por el modelo: [escalares](/graphql/reference/scalars), [objetos](/graphql/reference/objects), [enumeradores](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [uniones](/graphql/reference/unions), y [objetos de entrada](/graphql/reference/input-objects). + +Puedes acceder a este mismo contenido a través de la [Barra lateral de documentos del explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Nota que podrías necesitar depender de ambos, los documentos y la validación del modelo, para hacer una llamada a la API de GraphQL. + +Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/graphql/guides). + +### Solicitar soporte + +{% data reusables.support.help_resources %} diff --git a/translations/es-ES/content/graphql/overview/breaking-changes.md b/translations/es-ES/content/graphql/overview/breaking-changes.md new file mode 100644 index 0000000000000..7ee21c01b160e --- /dev/null +++ b/translations/es-ES/content/graphql/overview/breaking-changes.md @@ -0,0 +1,37 @@ +--- +title: Cambios sustanciales +intro: 'Aprende sobre los cambios sustanciales recientes y venideros a la API de GraphQL de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/breaking_changes +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los cambios sustanciales + +Los cambios sustanciales son aquellos que pudieran necesitar que nuestros integradores realicen alguna acción al respecto. Dividimos estos cambios en dos categorías: + + - **Sustanciales:** Cambios que modificarán consultas existentes a la API de GraphQL. Por ejemplo, eliminar un campo sería un cambio sustancial. + - **Peligrosos:** Cambios que no modificaran las consultas existentes, pero podrían afectar el comportamiento del tiempo de ejecución de los clientes. Agregar un valor de enumerador es un ejemplo de un cambio peligroso. + +Nos esforzamos por proporcionar API estables para nuestros integradores. Cuando alguna característica nueva está evolucionando aún, la lanzamos detrás de una [vista previa del modelo](/graphql/overview/schema-previews). + +Anunciaremos los cambios sustanciales por venir por lo menos tres meses antes de aplicarlos al modelo de GraphQL, para proporcionar a los integradores tiempo para realizar los ajustes necesarios. Los cambios toman efecto en el primer día de un trimestre (1 de enero, 1 de abril, 1 de julio, o 1 de octubre). Por ejemplo, si anunciamos un cambio en el 15 de enero, se aplicará en el 1 de julio. + +{% for date in graphql.upcomingChangesForCurrentVersion %} +### Cambios programados para {{ date[0] }} + +{% for change in date[1] %} +
    +
  • {% if change.criticality == 'breaking' %}Sustancial{% else %}Peligroso{% endif %}Se hará un cambio a {{ change.location }}. + +

    Descripción: {{ change.description }}

    + +

    Razón:{{ change.reason }}

    +
    • +
+ +{% endfor %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/overview/changelog.md b/translations/es-ES/content/graphql/overview/changelog.md new file mode 100644 index 0000000000000..8bcc43c9566d6 --- /dev/null +++ b/translations/es-ES/content/graphql/overview/changelog.md @@ -0,0 +1,41 @@ +--- +title: Bitácora de Cambios +intro: 'La bitácora de cambios del modelo de GraphQL es una lista de cambios recientes y venideros a nuestro modelo de la API de GraphQL. Este incluye cambios compatibles con versiones anteriores, y cambios sustanciales venideros.' +redirect_from: + - /v4/changelog +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Los cambios sustanciales incluyen aquellos que modificarán las consultas existentes o que podrían afectar el comportamiento del tiempo de ejecución de los clientes. Para un listado de cambios sustanciales y cuándo ocurrirán, consulta nuestra [bitácora de cambios sustanciales](/graphql/overview/breaking-changes). + +{% for entry in graphql.changelog %} +### Cambios de modelo para {{ entry.date }} + +{% for schemaChange in entry.schemaChanges %} +{{ schemaChange.title }} + +{% for change in schemaChange.changes %} +* {{ change }} +{% endfor %} +{% endfor %} + +{% for previewChange in entry.previewChanges %} +{{ previewChange.title }} + +{% for change in previewChange.changes %} +* {{ change }} +{% endfor %} +{% endfor %} + +{% for upcomingChange in entry.upcomingChanges %} +{{ upcomingChange.title }} + +{% for change in upcomingChange.changes %} +* {{ change }} +{% endfor %} +{% endfor %} + +{% endfor %} diff --git a/translations/es-ES/content/graphql/overview/explorer.md b/translations/es-ES/content/graphql/overview/explorer.md new file mode 100644 index 0000000000000..74540b78a43af --- /dev/null +++ b/translations/es-ES/content/graphql/overview/explorer.md @@ -0,0 +1,12 @@ +--- +title: Explorer +redirect_from: + - /v4/explorer + - /v4/explorer-new +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +layout: graphql-explorer +--- + diff --git a/translations/es-ES/content/graphql/overview/index.md b/translations/es-ES/content/graphql/overview/index.md new file mode 100644 index 0000000000000..df7952043608a --- /dev/null +++ b/translations/es-ES/content/graphql/overview/index.md @@ -0,0 +1,22 @@ +--- +title: Resumen +intro: 'Aprende acerca de la API de GraphQL de {% data variables.product.prodname_dotcom %}, las vistas previas para los cambios venideros, sustanciales y sobre las limitaciones. También puedes utilizar el explorador de GraphQL para interactuar con la API en datos reales de {% data variables.product.prodname_dotcom %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_in_list /about-the-graphql-api %} + +{% link_in_list /public-schema %} + +{% link_in_list /schema-previews %} + +{% link_in_list /breaking-changes %} + +{% link_in_list /changelog %} + +{% link_in_list /explorer %} + +{% link_in_list /resource-limitations %} diff --git a/translations/es-ES/content/graphql/overview/public-schema.md b/translations/es-ES/content/graphql/overview/public-schema.md new file mode 100644 index 0000000000000..906ee6dc7427b --- /dev/null +++ b/translations/es-ES/content/graphql/overview/public-schema.md @@ -0,0 +1,32 @@ +--- +title: Modelo público +intro: 'Descarga el modelo público para la API de GraphQL de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/public_schema +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes [realizar una introspección](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) contra la API de GraphQL directamente. + +Como alternativa, puedes descargar la última versión del modelo público aquí: + +{% if currentVersion == "free-pro-team@latest" %} + +[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs.graphql`](/public/schema.docs.graphql) + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }}) + +{% endif %} + +{% if currentVersion == "github-ae@latest" %} + +[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }}) + +{% endif %} diff --git a/translations/es-ES/content/graphql/overview/resource-limitations.md b/translations/es-ES/content/graphql/overview/resource-limitations.md new file mode 100644 index 0000000000000..c773275022b34 --- /dev/null +++ b/translations/es-ES/content/graphql/overview/resource-limitations.md @@ -0,0 +1,223 @@ +--- +title: Limitaciones de los recursos +intro: 'La API de GraphQL de {% data variables.product.prodname_dotcom %} cuenta con limitaciones para la protección contra las llamadas excesivas o abusivas a los servidores de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/guides/resource-limitations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +## Límite de nodo + +Para pasar la validación del [modelo](/graphql/guides/introduction-to-graphql#schema), todas las [llamadas](/graphql/guides/forming-calls-with-graphql) la API v4 de GraphQL deben cumplir con los siguientes estándares: + +* Los clientes deben suministrar un argumento `first` o `last` en cualquier [conexión](/graphql/guides/introduction-to-graphql#connection). +* Los valores de `first` y `last` deben estar dentro de 1-100. +* Las llamadas individuales no pueden solicitar más de 500,000 [nodos](/graphql/guides/introduction-to-graphql#node) en total. + +#### Calcular los nodos en una llamada + +Estos dos ejemplos te muestran cómo calcular los nodos totales en una llamada. + +1. Consulta simple: 
query {
+    viewer {
+      repositories(first: 50) {
+        edges {
+          repository:node {
+            name
+
+            issues(first: 10) {
+              totalCount
+              edges {
+                node {
+                  title
+                  bodyHTML
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+ + Cálculo: 
50         = 50 repositories
+   +
+  50 x 10  = 500 repository issues
+
+              = 550 total nodes
+ +2. Consulta compleja: 
query {
+    viewer {
+      repositories(first: 50) {
+        edges {
+          repository:node {
+            name
+
+            pullRequests(first: 20) {
+              edges {
+                pullRequest:node {
+                  title
+
+                  comments(first: 10) {
+                    edges {
+                      comment:node {
+                        bodyHTML
+                      }
+                    }
+                  }
+                }
+              }
+            }
+
+            issues(first: 20) {
+              totalCount
+              edges {
+                issue:node {
+                  title
+                  bodyHTML
+
+                  comments(first: 10) {
+                    edges {
+                      comment:node {
+                        bodyHTML
+                      }
+                    }
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+
+      followers(first: 10) {
+        edges {
+          follower:node {
+            login
+          }
+        }
+      }
+    }
+  }
+ + Cálculo: 
50              = 50 repositories
+   +
+  50 x 20       = 1,000 pullRequests
+   +
+  50 x 20 x 10 = 10,000 pullRequest comments
+   +
+  50 x 20       = 1,000 issues
+   +
+  50 x 20 x 10 = 10,000 issue comments
+   +
+  10              = 10 followers
+
+                   = 22,060 total nodes
+ +## Limite de tasa + +El límite de la API v4 de GraphQL es diferente a los [límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting) de la API v3 de REST. + +¿Por qué son diferentes los límites de tasa de la API? Con [GraphQL](/graphql), una llamada de GraphQL puede reemplazar [varias llamadas de REST](/graphql/guides/migrating-from-rest-to-graphql). Una sola llamada compleja de GraphQL puede ser el equivalente a miles de solicitudes de REST. Si bien una sola llamada de GraphQL caería muy debajo del límite de tasa de la API de REST, la consulta podría ser igual de cara en términos de procesamiento para los servidores de GitHub. + +Para representar con precisión el costo de una consulta al servidor, la API v4 de GraphQL calcula la **puntuación de tasa límite** de una llamada con base en una escala de puntos normalizada. Los factores de puntuación de una consulta en argumentos "firs" y "last" en una conexión padre y sus hijos. + +* La fórmula utiliza los argumentos `first` y `last` en una conexión padre y en sus hijos para pre-calcular la carga potencial en los sistemas de GitHub, tal como MySQL, ElasticSearch y Git. +* Cada conexión nueva tiene su propio valor de puntos. Los puntos se combinan con otros puntos desde la llamada en una puntuación de tasa límite general. + +El límite de tasa de la API v4 de GraphQL es de **5,000 puntos por hora**. + +Nota que 5,000 puntos por hora no es lo mismo que 5,000 llamadas por hora: la API v4 de GraphQL y la API v3 de REST utilizan límites de tasa diferentes. + +{% note %} + +**Nota**: La fórmula y el límite de tasa actuales están sujetos a cambio mientras observamos cómo los desarrolladores utilizan la API v4 de GraphQL. + +{% endnote %} + +#### Recuperar el estado de límite de tasa de una llamada + +Con la API v3 de REST, puedes revisar el estado de límite de tasa si [inspeccionas](/rest/overview/resources-in-the-rest-api#rate-limiting) los encabezados HTTP devueltos. + +Con la API v4 de GraphQL, puedes revisar el estado de límite de tasa si consultas los campos en el objeto `rateLimit`: + +```graphql +query { + viewer { + login + } + rateLimit { + limit + cost + remaining + resetAt + } +} +``` + +* El campo `limit` devuelve el número máximo de puntos que se permite consumir al cliente en una ventana de 60 minutos. + +* El campo `cost` devuelve el costo en puntos para la llamada actual que cuenta contra el límite de tasa. + +* El campo `remaining` devuelve la cantidad de puntos restantes en la ventana de límite de tasa actual.) + +* EL campo `resetAt` devuelve la hora en la que se reinicia la ventana de límite de tasa actual en [segundos de satélite UTC](http://en.wikipedia.org/wiki/Unix_time). + +#### Calcular el puntaje de límite de tasa antes de ejecutar la llamada + +Al consultar el objeto `rateLimit` se devuelve el puntaje de una llamada, pero ejecutar la llamada tiene un costo en el límite. Para evitar este dilema, puedes calcular el puntaje de una llamada antes de ejecutarla. Los siguientes cálculos funcionan casi de la misma manera que lo que devuelve `rateLimit { cost }`. + +1. Agrega la cantidad de solicitudes requeridas para completar cada conexión única en la llamada. Asume que cada solicitud alcanzará los límites de los argumentos `first` o `last`. +2. Divide la cantidad entre **100** y redondea el resultado para obtener el costo final agregado. Este paso normaliza las cantidades grandes. + +{% note %} + +**Nota**: El costo mínimo de una llamada a la API v4 de GraphQL es **1**, lo cual representa solo una solicitud. + +{% endnote %} + +Aquí se muestra una consulta y cálculo de puntaje de ejemplo: + +```graphql +query { + viewer { + login + repositories(first: 100) { + edges { + node { + id + + issues(first: 50) { + edges { + node { + id + + labels(first: 60) { + edges { + node { + id + name + } + } + } + } + } + } + } + } + } + } +} +``` + +Esta consulta requiere de 5,101 solicitudes para completarse: + +* Aunque se devolvieron 100 repositorios, la API se tiene que conectar a la cuenta del visualizador **una vez** para obtener la lista de repositorios. Así que, las solicitudes de repositorios = **1** +* Aunque estámos obteniendo 50 informes de problemas de vuelta, la API tiene que conectarse a cada uno de los **100** repositorios para obtener la lista de informes de problemas. Así que, las solicitudes de informes de problemas = **100** +* Aunque estamos obteniendo 60 etiquetas de vuelta, la API se tiene que conectar a cada uno de los **5,000** informes de problemas potenciales totales para obtener la lista de etiquetas. Así que, las solicitudes de etiquetas = **5,000** +* Total = **5,101** + +Si lo dividimos entre 100 y lo redondeamos, obtenemos el puntaje final de la consulta: **51** diff --git a/translations/es-ES/content/graphql/overview/schema-previews.md b/translations/es-ES/content/graphql/overview/schema-previews.md new file mode 100644 index 0000000000000..7752d78bef55b --- /dev/null +++ b/translations/es-ES/content/graphql/overview/schema-previews.md @@ -0,0 +1,51 @@ +--- +title: Vistas previas del modelo +intro: 'Puedes obtener una vista previa de las características y cambios por venir para el modelo de GraphQL de {% data variables.product.prodname_dotcom %} antes de que se agreguen a la API de GraphQL de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/previews +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las vistas previas del modelo + +Durante el periodo de vista previa, podríamos cambiar algunas características con base en la retroalimentación de los desarrolladores. Si realizamos cambios, lo anunciaremos en el [blog de desarrolladores](https://developer.github.com/changes/) sin aviso previo. + +Para aceder a una vista previa de modelo, necesitamos que nos proporciones un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado `Accept` para tus solicitudes. La documentación de características para cada vista previa especifica qué tipo de medios personalizados proporcionar. + +{% note %} + +**Nota:** En este momento no se puede acceder a los miembros de modelo de GraphQL bajo vista previa a través del explorador. + +{% endnote %} + +{% for preview in graphql.previewsForCurrentVersion %} +### {{ preview.title }} + +{{ preview.description }} + +Para alternar esta vista previa y acceder a los siguientes miembros de modelo, debes proporcionar un tipo de medios personalizado en el encabezado `Accept`: + +``` +{{ preview.accept_header }} +``` + +Miembros del modelo previstos: + +{% for schemaMemberPath in preview.toggled_on %} +- `{{ schemaMemberPath }}` +{% endfor %} + +{% if preview.announcement %} +**Anunciados:** [{{ preview.announcement.date }}]({{ preview.announcement.url }}) +{% endif %} + +{% if preview.updates %} +{% for update in preview.updates %} +**Actualizados:** [{{ update.date }}]({{ update.url }}) +{% endfor %} +{% endif %} + +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/enums.md b/translations/es-ES/content/graphql/reference/enums.md new file mode 100644 index 0000000000000..ad059ff44f0a4 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/enums.md @@ -0,0 +1,22 @@ +--- +title: Enumeradores +redirect_from: + - /v4/enum + - /v4/reference/enum +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los enumeradores + +Los [Enumeradores](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) representan conjuntos de valores posibles para un campo. + +Por ejemplo, el objeto [`Issue`](/graphql/reference/objects#issue) tiene un campo llamado `state`. El estado es un enumerador (específicamente, de tipo [`IssueState`](/graphql/reference/enums#issuestate)) ya que éste puede ser `OPEN` o `CLOSED`. + +Para obtener más información, consulta la sección "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)". + +{% for item in graphql.schemaForCurrentVersion.enums %} + {% include graphql-enum %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/index.md b/translations/es-ES/content/graphql/reference/index.md new file mode 100644 index 0000000000000..7fafbf090695a --- /dev/null +++ b/translations/es-ES/content/graphql/reference/index.md @@ -0,0 +1,26 @@ +--- +title: Referencia +intro: 'Consulta la documentación de referencia para aprender sobre los tipos de datos disponibles en el modelo de la API de GraphQL de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /v4/reference +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_in_list /queries %} + +{% link_in_list /mutations %} + +{% link_in_list /objects %} + +{% link_in_list /interfaces %} + +{% link_in_list /enums %} + +{% link_in_list /unions %} + +{% link_in_list /input-objects %} + +{% link_in_list /scalars %} diff --git a/translations/es-ES/content/graphql/reference/input-objects.md b/translations/es-ES/content/graphql/reference/input-objects.md new file mode 100644 index 0000000000000..768544aacc80a --- /dev/null +++ b/translations/es-ES/content/graphql/reference/input-objects.md @@ -0,0 +1,22 @@ +--- +title: Objetos de entrada +redirect_from: + - /v4/input_object + - /v4/reference/input_object +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los objetos de entrada + +Los [objetos de entrada](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) pueden describirse como "objetos estructurables" ya que incluyen un conjunto de campos de entrada que definen al objeto. + +Por ejemplo, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) toma un campo llamado `emails`. Proporcionar un valor para `emails` transforma a `CommitAuthor` en una lista de objetos `User` que contienen esa dirección de correo electrónico. Nota que los [objetos](/graphql/reference/objects) **podrían** tener objetos de entrada, mientras que las [mutaciones](/graphql/reference/mutations) **requieren** objetos de entrada. + +Para obtener más información, consulta la sección "[Acerca de las mutaciones](/graphql/guides/forming-calls-with-graphql#about-mutations)". + +{% for item in graphql.schemaForCurrentVersion.inputObjects %} + {% include graphql-input-object %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/interfaces.md b/translations/es-ES/content/graphql/reference/interfaces.md new file mode 100644 index 0000000000000..a585b0eec2089 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/interfaces.md @@ -0,0 +1,22 @@ +--- +title: Interfaces +redirect_from: + - /v4/interface + - /v4/reference/interface +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las interfaces + +Las [interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) sirven como objetos padre de los cuales obtendrán sus herencias los demás objetos. + +Por ejemplo, [`Lockable`](/graphql/reference/interfaces#lockable) es una interface, ya que tanto los objetos [`Issue`](/graphql/reference/objects#issue) como los objetos [`PullRequest`](/graphql/reference/objects#pullrequest) se pueden fijar. Una interface tiene su propia lista de campos nombrados que se comparte mediante objetos de implementación. + +Para obtener más información, consulta la sección "[Implementación](/graphql/guides/introduction-to-graphql#implementation)". + +{% for item in graphql.schemaForCurrentVersion.interfaces %} + {% include graphql-interface %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/mutations.md b/translations/es-ES/content/graphql/reference/mutations.md new file mode 100644 index 0000000000000..6171f4ec65316 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/mutations.md @@ -0,0 +1,20 @@ +--- +title: Mutaciones +redirect_from: + - /v4/mutation + - /v4/reference/mutation +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las mutaciones + +Cada modelo de GraphQL tiene un tipo de raíz tanto para consultas como para mutaciones. El [tipo mutación](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define las operaciones de GraphQL que cambian los datos en el servidor. Es análogo a realizar verbos HTTP tales como `POST`, `PATCH`, y `DELETE`. + +Para obtener más información, consulta la sección "[Acerca de las mutaciones](/graphql/guides/forming-calls-with-graphql#about-mutations)". + +{% for item in graphql.schemaForCurrentVersion.mutations %} + {% include graphql-mutation %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/objects.md b/translations/es-ES/content/graphql/reference/objects.md new file mode 100644 index 0000000000000..db67b2e81e706 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/objects.md @@ -0,0 +1,21 @@ +--- +title: Objetos +redirect_from: + - /v4/object + - /v4/reference/object +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los objetos + +Los [objetos](https://graphql.github.io/graphql-spec/June2018/#sec-Objects) en GraphQL representan los recursos a los cuales puedes acceder. Un objeto puede contener una lista de campos, los cuales se teclean específicamente. + +Por ejemplo, el objeto [`Repository`](/graphql/reference/objects#repository) tiene un campo llamado `name`, el cual es una `String`. + +Para obtener más información, consulta la sección "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)". + + + diff --git a/translations/es-ES/content/graphql/reference/queries.md b/translations/es-ES/content/graphql/reference/queries.md new file mode 100644 index 0000000000000..30b87fcb2a9ad --- /dev/null +++ b/translations/es-ES/content/graphql/reference/queries.md @@ -0,0 +1,35 @@ +--- +title: Consultas +miniTocMaxHeadingLevel: 2 +redirect_from: + - /v4/query + - /v4/reference/query +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las consultas + +Cada modelo de GraphQL tiene un tipo de raíz tanto para consultas como para mutaciones. El [tipo de consulta](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define las operaciones de GraphQL que recuperan datos del servidor. + +Paraobtener más información, consulta la sección "[Acerca de las consultas](/graphql/guides/forming-calls-with-graphql#about-queries)". + +{% note %} + +**Nota:** Para solicitudes de {% data variables.product.prodname_github_app %} de tipo [usuario a servidor](/developers/apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests), debes separar las consultas para las propuestas y para las solicitudes de cambios. Por ejemplo, utiliza filtros de `is:issue` o de `is:pull-request` y sus equivalentes. Utilizar la conexión `search` para devolver una combinación de propuestas y solicitudes de cambios en una sola consulta dará como resultado un conjunto de nodos vacío. + +{% endnote %} + +## Conexiones + +{% for item in graphql.schemaForCurrentVersion.queries.connections %} + {% include graphql-query %} +{% endfor %} + +## Campos + +{% for item in graphql.schemaForCurrentVersion.queries.fields %} + {% include graphql-query %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/scalars.md b/translations/es-ES/content/graphql/reference/scalars.md new file mode 100644 index 0000000000000..435424c232d30 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/scalars.md @@ -0,0 +1,22 @@ +--- +title: Escalares +redirect_from: + - /v4/scalar + - /v4/reference/scalar +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los escalares + +Los [escalares](https://graphql.github.io/graphql-spec/June2018/#sec-Scalars) son valores primitivos: `Int`, `Float`, `String`, `Boolean`, o `ID`. + +Cuando llamas a la API de GraphQL, debes especificar subcampos anidados hasta que recuperes únicamente escalares. + +Para obtener más información, consulta la sección "[introducción a GraphQL](/graphql/guides/introduction-to-graphql#field)". + +{% for item in graphql.schemaForCurrentVersion.scalars %} + {% include graphql-scalar %} +{% endfor %} diff --git a/translations/es-ES/content/graphql/reference/unions.md b/translations/es-ES/content/graphql/reference/unions.md new file mode 100644 index 0000000000000..174d58f7c47d6 --- /dev/null +++ b/translations/es-ES/content/graphql/reference/unions.md @@ -0,0 +1,22 @@ +--- +title: Uniones +redirect_from: + - /v4/union + - /v4/reference/union +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de las uniones + +Una [unión](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) es un tipo de objeto que representa muchos otros objetos. + +Por ejemplo, un campo marcado como un [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) podría ser un [`Issue`](/graphql/reference/objects#issue) o una [`PullRequest`](/graphql/reference/objects#pullrequest) ya que cada uno de estos objetos puede estar dentro de una tarjeta de proyecto. Utilizar una unión en vez de un objeto te otorga flexibilidad. + +Para obtener más información, consulta la sección "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)". + +{% for item in graphql.schemaForCurrentVersion.unions %} + {% include graphql-union %} +{% endfor %} diff --git a/translations/es-ES/content/index.md b/translations/es-ES/content/index.md new file mode 100644 index 0000000000000..98bfc96b0b40c --- /dev/null +++ b/translations/es-ES/content/index.md @@ -0,0 +1,17 @@ +--- +title: '{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}.com{% endif %} Documentación de Ayuda' +featuredLinks: + gettingStarted: + - /github/getting-started-with-github/set-up-git + - /github/authenticating-to-github/connecting-to-github-with-ssh + - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github + - /github/writing-on-github/basic-writing-and-formatting-syntax + popular: + - /github/collaborating-with-issues-and-pull-requests/about-pull-requests + - /github/authenticating-to-github + - /github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line + - /github/using-git/managing-remote-repositories + - /github/working-with-github-pages +versions: '*' +--- + diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/index.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/index.md new file mode 100644 index 0000000000000..125f4f022e2f7 --- /dev/null +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/index.md @@ -0,0 +1,14 @@ +--- +title: Explorando tu uso de GitHub Enterprise +shortTitle: Explorando tu uso +intro: Puedes utilizar métricas e informes para entender y mejorar tu proceso de entrega de software a través de datos. +redirect_from: + - /github/installing-and-configuring-github-insights/exploring-your-usage-of-github-enterprise +versions: + enterprise-server: '*' +--- + +{% link_in_list /metrics-available-with-github-insights %} +{% link_in_list /viewing-key-metrics-and-reports %} +{% link_in_list /setting-your-timezone-for-github-insights %} +{% link_in_list /navigating-between-github-enterprise-and-github-insights %} diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md new file mode 100644 index 0000000000000..71eb86fee1d6c --- /dev/null +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md @@ -0,0 +1,76 @@ +--- +title: Métricas disponibles con GitHub Insights +product: '{% data reusables.gated-features.github-insights %}' +intro: '{% data variables.product.prodname_insights %} incluye una variedad de métricas para darte visibilidad en el proceso de entrega de software de tu equipo.' +redirect_from: + - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights + - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests +versions: + enterprise-server: '*' +--- + +### Acerca de métricas en {% data variables.product.prodname_insights %} + +{% data reusables.github-insights.key-metrics-and-reports %} + +{% data reusables.github-insights.about-key-metrics %} Puedes configurar y medir tus metas para cada métrica clave. Para obtener más información, consulta "[Administrar metas](/insights/installing-and-configuring-github-insights/managing-goals)". + +{% data reusables.github-insights.about-reports %} + +{% data reusables.github-insights.manage-metrics %} + +### Métricas clave para la colaboración en solicitudes de extracción (pull requests) + +Las métricas clave para la colaboración en solicitudes de extracción ayudan a los equipos a eliminar los cuellos de botella en el proceso, a mejorar la colaboración y a entregar los proyectos más rápido, con mayor calidad. La mejora de estas métricas resulta en un equipo más productivo. + +- [Distribución de revisión de código](#code-review-distribution) +- [Respuesta de revisión de código](#code-review-turnaround) +- [Tiempo de apertura](#time-to-open) +- [Tamaño de solicitud de extracción](#pull-request-size) +- [Trabajo en curso](#work-in-progress) + +#### Distribución de revisión de código + +Mide la distribución de revisiones de código en un equipo u organización. Un valor más cercano a 1 indica una distribución más igualitaria. Incluye los miembros que previamente han abierto, revisado o comentado en una solicitud de extracción o se han confirmado a una rama. + +El índice es igual a 1 menos el coeficiente de Gini de revisiones de código para una organización o equipo. Para obtener más información, consulta [Coeficiente de Gini](https://en.wikipedia.org/wiki/Gini_coefficient) en Wikipedia. + +#### Respuesta de revisión de código + +El tiempo transcurrido entre una asignación de revisión y una revisión completada. + +Para contrarrestar las revisiones de código como un bloqueador para los equipos, las organizaciones pueden optimizar su proceso de asignación de revisiones y establecer metas para el tiempo de respuesta. + +#### Tiempo de apertura + +El tiempo transcurrido entre la primera confirmación de un usuario a una rama y la apertura de una solicitud de extracción para esa rama. + +Disminuir este período de tiempo les permite a los colaboradores recibir más temprano comentarios en el proceso y garantiza más tiempo para la colaboración y la iteración. + +#### Tamaño de solicitud de extracción + +Tamaño de diferencia total de una solicitud de extracción (total de líneas agregadas, eliminadas y modificadas). + +Las solicitudes de extracción de gran tamaño conllevan más riesgo cuando se implementan en la producción y son más difíciles de revisar, fusionar y lanzar. Implementar solicitudes de extracción de un tamaño razonable le permite a tu equipo revisar y enviar nuevas características a una cadencia más rápida y con mayor confianza + +#### Trabajo en curso + +La cantidad de solicitudes de extracción abiertas para un equipo o una organización dada, expresada como total y como proporción de solicitudes de extracción abiertas para el programador. + +Un retraso importante en la solicitud de extracción significa que el trabajo puede estar desactualizado, lo que indica un esfuerzo desaprovechado de tu equipo. Esta métrica ayuda a mantener centrado a tu equipo al mismo tiempo que garantiza que nadie en el equipo esté bloqueado o sobrecargado. + +### Informes + +| Métrica | Descripción | +| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Actividad | Una actividad es cualquiera de las siguientes:
  • Confirmarse a una rama
  • Abrir una solicitud de extracción
  • Cerrar una solicitud de extracción
  • Fusionar una solicitud de extracción
  • Comentar en una solicitud de extracción
  • Aprobar una solicitud de extracción
| +| Actividad, hora | Una hora con actividad es cualquier hora en la que al menos un colaborador registra una actividad. | +| Código de renovación | El código de renovación es un código cambiado dentro de las tres semanas desde que se agregó o cambió por última vez. Esto incluye las líneas de código que fueron sobrescritas por el autor o por otro colaborador. | +| Líneas de código añadidas y cambiadas | Recuento total de las nuevas líneas de código añadidas además de las líneas de código modificadas. Puedes incluir o excluir un código de renovación. | +| Propiedad | Porcentaje de desglose de líneas de código añadidas y modificadas por el último colaborador para agregar o cambiar cada línea de código. | +| Emparejamientos | Colaboradores que modifican o eliminan el código de otro colaborador. | +| Porcentaje de base de código cambiada | Líneas de código agregadas o modificadas en la base de código como un porcentaje del total de líneas de código en la base de código. | +| Porcentaje de código nuevo y cambiado frente al código de renovación | Líneas de código añadidas y cambiadas, excepto el código de renovación, como porcentaje del total de líneas de código añadidas y cambiadas, incluido el código de renovación. | +| Solicitudes de extracción abiertas | El recuento de todas las solicitudes de extracción que están abiertas al final del período seleccionado o el intervalo de tiempo que se muestra en el gráfico. | +| Retención | Porcentaje de líneas de código que se conservan en la base de código después de cada semana, agrupadas por la semana en la que se crearon las líneas. | +| Tiempo para fusionar | Tiempo entre la primera confirmación en una rama y la acción de fusión de una solicitud de extracción en esa rama. La marca de tiempo de la primera confirmación en una rama se resta de la marca de tiempo en la acción de fusión de la solicitud de extracción. | diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md new file mode 100644 index 0000000000000..379f7471740af --- /dev/null +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md @@ -0,0 +1,12 @@ +--- +title: Navegar entre GitHub Enterprise y GitHub Insights +intro: '' +product: '{% data reusables.gated-features.github-insights %}' +permissions: 'Cualquier persona con acceso a {% data variables.product.prodname_insights %} puede navegar entre {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_insights %}.' +versions: + enterprise-server: '*' +--- + +Antes de que puedas navegar entre {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_insights %}, un administrador del sitio debe habilitar un enlace entre {% data variables.product.prodname_insights %} y {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Habilitar un enlace entre {% data variables.product.prodname_insights %} y {% data variables.product.prodname_enterprise %}](/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise)." + +1. En la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **GitHub Insights**. ![Enlace a GitHub Insights](/assets/images/help/insights/github-insights-link.png) diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md new file mode 100644 index 0000000000000..eab91447fa093 --- /dev/null +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md @@ -0,0 +1,14 @@ +--- +title: Configurando tu zona horaria para GitHub Insights +intro: 'Puedes establecer la zona horaria para las métricas que ves en {% data variables.product.prodname_insights %}.' +product: '{% data reusables.gated-features.github-insights %}' +permissions: 'Cualquiera con acceso a {% data variables.product.prodname_insights %} puede establecer su propia zona horaria.' +versions: + enterprise-server: '*' +--- + +Tu configuración de zona horaria solo afecta a cómo ves los datos en {% data variables.product.prodname_insights %}. La configuración no se aplica a otros usuarios. + +{% data reusables.github-insights.settings-tab %} +2. Utiliza el menú desplegable "Timezone (Zona horaria)" y selecciona tu zona horaria. ![Menú desplegable zona horaria](/assets/images/help/insights/timezone-drop-down.png) +3. Haz clic en **Save Changes (Guardar cambios)**. diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md new file mode 100644 index 0000000000000..b28d0946b3bdd --- /dev/null +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md @@ -0,0 +1,41 @@ +--- +title: Ver métricas e informes clave +intro: Puedes ver y filtrar métricas e informes clave para ayudarte a comprender y mejorar tu proceso de entrega de software mediante datos. +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /GitHub/Installing-and-Configuring-GitHub-Insights/Viewing-and-Filtering-Key-Metrics-and-Reports +permissions: 'Cualquier persona con acceso a {% data variables.product.prodname_insights %} puede ver los informes y las métricas clave.' +versions: + enterprise-server: '*' +--- + +### Acerca de las métricas y los informes + +{% data reusables.github-insights.key-metrics-and-reports %} Para obtener más información acerca de las métricas disponibles, consulta "[Métricas disponibles con {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)". + +Puedes ver las metas y tasas de éxito para cada métrica clave. Para obtener más información, consulta "[Administrar las metas](/insights/installing-and-configuring-github-insights/managing-goals)" + +Solo tendrás acceso a los mismos datos de {% data variables.product.prodname_insights %} que tienes acceso en {% data variables.product.prodname_enterprise %}. + +Puedes filtrar los datos incluidos en las métricas o los informes clave por equipos, repositorios o intervalo de fechas. + +### Ver métricas clave + +{% data reusables.github-insights.navigate-to-key-metrics %} +{% data reusables.github-insights.choose-key-metric %} +{% data reusables.github-insights.filter-reports %} +{% data reusables.github-insights.view-events %} + +### Ver informes + +1. En {% data variables.product.prodname_insights %}, haz clic en **{% octicon "file" aria-label="The file icon" %} Reports** (Informes). ![Pestaña Reports (Informes)](/assets/images/help/insights/reports-tab.png) +2. Debajo de **{% octicon "file" aria-label="The file icon" %} Reports** (Informes), haz clic en el nombre del informe que deseas ver. ![Lista de informes](/assets/images/help/insights/reports-list.png) +{% data reusables.github-insights.filter-reports %} +{% data reusables.github-insights.view-events %} + +### Further reading + +- "[Administrar colaboradores y equipos](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)" +- "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)" +- "[Administrar organizaciones](/insights/installing-and-configuring-github-insights/managing-organizations)" +- "[Administrar eventos](/insights/installing-and-configuring-github-insights/managing-events)" diff --git a/translations/es-ES/content/insights/index.md b/translations/es-ES/content/insights/index.md new file mode 100644 index 0000000000000..61fc5bc414276 --- /dev/null +++ b/translations/es-ES/content/insights/index.md @@ -0,0 +1,21 @@ +--- +title: Documentación de GitHub Insights +shortTitle: GitHub Insights +intro: 'Entiende y mejora tu proceso de entrega de software a través de datos con {% data variables.product.prodname_insights %}. Puedes ver informes personalizados basados en datos de {% data variables.product.prodname_enterprise %}.' +featuredLinks: + gettingStarted: + - /insights/installing-and-configuring-github-insights/about-github-insights + - /insights/installing-and-configuring-github-insights/system-overview-for-github-insights + - /insights/installing-and-configuring-github-insights/installing-github-insights + - /insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports + popular: + - /insights/installing-and-configuring-github-insights/about-data-in-github-insights + - /insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights +redirect_from: + - /github/installing-and-configuring-github-insights +versions: + enterprise-server: '*' +--- + +{% link_with_intro /installing-and-configuring-github-insights %} +{% link_with_intro /exploring-your-usage-of-github-enterprise %} diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md new file mode 100644 index 0000000000000..2520272e32c27 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md @@ -0,0 +1,22 @@ +--- +title: Acerca de los datos en la información de GitHub +intro: 'Los datos incluidos en las métricas de {% data variables.product.prodname_insights %} son altamente personalizables.' +product: '{% data reusables.gated-features.github-insights %}' +permissions: '' +versions: + enterprise-server: '*' +--- + +{% data variables.product.prodname_insights %} muestra datos sobre el trabajo de tu equipo en métricas e informes clave. Puedes elegir cuál de estas métricas se mostrarán. Para obtener más información, consulta la sección "[Administrar métricas y reportes disponibles](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)" + +Puedes administrar qué organizaciones de {% data variables.product.prodname_enterprise %} se incluyen en las métricas. Para obtener más información, consulta "[Administrar organizaciones](/insights/installing-and-configuring-github-insights/managing-organizations)". + +Después de agregar una organización a {% data variables.product.prodname_insights %}, puedes elegir qué repositorios de esa organización se incluirán en las métricas. {% data reusables.github-insights.repository-groups %} Para obtener más información, consulta "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)". + +Puedes elegir qué colaboradores se incluirán en las métricas y crear equipos de colaboradores. Para obtener más información, consulta "[Administrar colaboradores y equipos](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)". + +{% data reusables.github-insights.events %} Para obtener más información, consulta "[Administrar eventos](/insights/installing-and-configuring-github-insights/managing-events)". + +### Further reading +- "[Métricas disponibles con {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)" +- "{% data variables.product.prodname_insights %} y protección de datos para tu organización" \ No newline at end of file diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md new file mode 100644 index 0000000000000..6f2f43f62b792 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md @@ -0,0 +1,28 @@ +--- +title: Acerca de GitHub Insights +intro: '{% data variables.product.prodname_insights %} proporciona métricas e informes analíticos para ayudar a los equipos de ingeniería a comprender y mejorar su proceso de entrega de software.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/about-github-insights +versions: + enterprise-server: '*' +--- + +### Acerca de {% data variables.product.prodname_insights %} + +{% data variables.product.prodname_insights %} es una aplicación autónoma que ofrece informes analíticos basados en datos de {% data variables.product.product_location %} para ayudarte a comprender y mejorar tu proceso de entrega de software. Puedes usar estas métricas para eliminar los cuellos de botella en el proceso, mejorar la colaboración y entregar los proyectos más rápido, con mayor calidad. + +{% data variables.product.prodname_insights %} está alojado en una máquina e interactúa con {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Descripción del sistema para {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/system-overview-for-github-insights)." + +Cualquier persona con acceso a {% data variables.product.prodname_insights %} puede ver e interactuar con las métricas, mediante filtros de equipo y de repositorios para contextualizar los datos. Para obtener más información, consulta "[Explorar tu uso de {% data variables.product.prodname_enterprise %}](/insights/exploring-your-usage-of-github-enterprise)." + +Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden elegir las métricas que se muestran y las organizaciones, los repositorios y las personas que se incluyen en esas métricas. También pueden agregar contexto a las métricas al administrar eventos. Para obtener más información, consulta "[Acerca de los datos en {% data variables.product.prodname_insights %} ](/insights/installing-and-configuring-github-insights/about-data-in-github-insights)." + +### Contactar con soporte técnico + +Puedes recibir soporte para {% data variables.product.prodname_insights %} de {% data variables.contact.github_support %}. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Emitir un ticket](/github/working-with-github-support/submitting-a-ticket)".{% else %}"[Contactar a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/reaching-github-support)".{% endif %} + +### Further reading + +- "[Instalar {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/installing-github-insights)" +- "[Configurar {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/configuring-github-insights)" diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md new file mode 100644 index 0000000000000..a473d34dc3cfc --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md @@ -0,0 +1,9 @@ +--- +title: Configurar información de GitHub +shortTitle: Configuración +intro: 'Puedes administrar la conexión entre {% data variables.product.prodname_insights %} Y {% data variables.product.prodname_enterprise %}, y administrar permisos para los usuarios de {% data variables.product.prodname_insights %}.' +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md new file mode 100644 index 0000000000000..b5a8847923814 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md @@ -0,0 +1,23 @@ +--- +title: Configurar la conexión entre GitHub Insights y GitHub Enterprise +intro: 'Puedes administrar de qué manera {% data variables.product.prodname_insights %} se conecta con {% data variables.product.prodname_enterprise %}.' +product: '{% data reusables.gated-features.github-insights %}' +permissions: 'Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden configurar la conexión con {% data variables.product.prodname_enterprise %}.' +versions: + enterprise-server: '*' +--- + +{% data reusables.github-insights.settings-tab %} +2. Debajo de +Ajustes {% octicon "gear" aria-label="The gear icon" %}, da clic en **Empresa**. + ![Laboratorio de Empresa](/assets/images/help/insights/enterprise-tab.png) +{% data reusables.github-insights.enterprise-api-url %} +{% data reusables.github-insights.app-id %} +{% data reusables.github-insights.client-id %} +{% data reusables.github-insights.client-secret %} +{% data reusables.github-insights.private-key %} +{% data reusables.github-insights.webhook-secret %} +{% data reusables.github-insights.skip-ssl %} +10. Haz clic en **Save ** (guardar). +{% data reusables.github-insights.insights-license %} +11. Haz clic en **Update License (Actualizar licencia)**. diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md new file mode 100644 index 0000000000000..3a1fd3aa85a00 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -0,0 +1,34 @@ +--- +title: Habilitar enlace entre la información de GitHub y GitHub Enterprise +intro: 'Puedes habilitar un enlace que permitirá a los usuarios navegar desde {% data variables.product.prodname_ghe_server %} hacia {% data variables.product.prodname_insights %}.' +product: '{% data reusables.gated-features.github-insights %}' +permissions: 'Los administradores del sitio de {% data variables.product.prodname_ghe_server %} pueden habilitar un enlace entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_insights %}.' +redirect_from: + - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise + - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise +versions: + enterprise-server: '*' +--- + +Una vez que habilitas el enlace, cada usuario puede navegar directamente desde {% data variables.product.prodname_ghe_server %} hasta {% data variables.product.prodname_insights %}. Para obtener más información, consulta "[Navegar entre {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights)". + +1. Conéctate al shell administrativo de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." +2. Ejecuta el siguiente comando. + ``` + ghe-config 'app.github.insights-available' 'true' && ghe-config-apply + ``` +3. Regresa a +{% data variables.product.prodname_ghe_server %}. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +7. Debajo de +{% octicon "gear" aria-label="The Settings gear" %} **Ajustes**, da clic en **{% data variables.product.prodname_insights %}**. + {% note %} + + **Nota:** Después de ejecutar el comando de configuración, tarda varios minutos hasta que esta opción se vuelve disponible en {% data variables.product.prodname_enterprise %}. Si no ves **{% data variables.product.prodname_insights %}**, espera o reinicia {% data variables.product.prodname_enterprise %}. + + {% endnote %} + + ![Pestaña {% data variables.product.prodname_insights %}](/assets/images/help/business-accounts/github-insights-tab.png) +3. Debajo de "URL de la instancia de {% data variables.product.prodname_insights %}", escribe la URL del servidor que usa tu empresa para {% data variables.product.prodname_insights %}. ![URL de la instancia de {% data variables.product.prodname_insights %}](/assets/images/help/business-accounts/insights-instance-url.png) +4. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/index.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/index.md new file mode 100644 index 0000000000000..4b04b8090eed3 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/index.md @@ -0,0 +1,25 @@ +--- +title: Instalar y configurar GitHub Insights +shortTitle: Instalar y configurar +intro: Puedes comenzar a usar GitHub Insights al instalar y configurar la aplicación. +versions: + enterprise-server: '*' +--- + +{% topic_link_in_list /installing-and-updating-github-insights %} + {% link_in_list /about-github-insights %} + {% link_in_list /system-overview-for-github-insights %} + {% link_in_list /installing-github-insights %} + {% link_in_list /updating-github-insights %} +{% topic_link_in_list /configuring-github-insights %} + {% link_in_list /configuring-the-connection-between-github-insights-and-github-enterprise %} + {% link_in_list /managing-permissions-in-github-insights %} + {% link_in_list /enabling-a-link-between-github-insights-and-github-enterprise %} +{% topic_link_in_list /managing-data-in-github-insights %} + {% link_in_list /about-data-in-github-insights %} + {% link_in_list /managing-available-metrics-and-reports %} + {% link_in_list /managing-contributors-and-teams %} + {% link_in_list /managing-repositories %} + {% link_in_list /managing-organizations %} + {% link_in_list /managing-goals %} + {% link_in_list /managing-events %} diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md new file mode 100644 index 0000000000000..1b60b5dc95ffb --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md @@ -0,0 +1,9 @@ +--- +title: Instalar y actualizar la información de GitHub +shortTitle: Instalar y actualizar +intro: 'Puedes instalar a aplicación de {% data variables.product.prodname_insights %} y actualizarla a la última versión.' +mapTopic: verdadero +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md new file mode 100644 index 0000000000000..fb96c9f9d63db --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -0,0 +1,102 @@ +--- +title: Instalar la información de GitHub +intro: 'Puedes instalar {% data variables.product.prodname_insights %} y conectar la aplicación autónoma para {% data variables.product.prodname_ghe_server %}.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/installing-github-insights +permissions: 'Los propietarios de la organización en {% data variables.product.prodname_enterprise %} con los permisos de lectura para el repositorio `github/insights-releases` y el acceso administrativo al servidor de aplicaciones pueden instalar {% data variables.product.prodname_insights %}.' +versions: + enterprise-server: '*' +--- + +### Prerrequisitos + +- Debes tener un archivo de licencia {% data variables.product.prodname_enterprise %} que incluya {% data variables.product.prodname_insights %}. Después de comprar {% data variables.product.prodname_insights %}, puedes descargar el archivo de licencia actualizado en el portal web [{% data variables.product.prodname_enterprise %}](https://enterprise.github.com/download). +- {% data reusables.github-insights.requires-machine %} Para obtener más información, consulta "[Descripción general del sistema para {% data variables.product.prodname_insights %}](/github/installing-and-configuring-github-insights/system-overview-for-github-insights#requirements-for-running-github-insights)". +- Debes instalar dependencias en el servidor de aplicaciones. + - [Docker](https://docs.docker.com/install/) 1.13.0 + + - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + + {% note %} + + **Nota:** {% data reusables.github-insights.docker-requirements %} + + {% endnote %} + +### Crear un {% data variables.product.prodname_github_app %} + +Para conectar {% data variables.product.prodname_insights %} a {% data variables.product.prodname_enterprise %}, debes crear un {% data variables.product.prodname_github_app %} en una organización en {% data variables.product.prodname_enterprise %}. Se mostrará una versión con slugged del nombre de tu app en {% data variables.product.prodname_enterprise %} cuando tu integración realiza una acción. + +{% data reusables.enterprise_site_admin_settings.sign-in %} +2. Navega a la organización con la cual te quieres conectar +{% data variables.product.prodname_insights %}. +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +5. Haz clic en **New (nuevo) {% data variables.product.prodname_github_app %}**. ![Botón nueva app de GitHub](/assets/images/help/apps/github_apps_new.png) +6. En "Name (nombre) {% data variables.product.prodname_github_app %}", escribe un nombre para la app. Tu app no puede tener el mismo nombre que un usuario o una organización existente, a menos que el nombre sea tu propio nombre de usuario o de organización. ![Campo de nombre de app de GitHub](/assets/images/help/apps/github_apps_app_name.png) +7. En "Homepage URL" (URL de página principal), escribe la URL del servidor de aplicaciones para {% data variables.product.prodname_insights %}. Para obtener más información, consulta "[Descripción general del sistema para {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/system-overview-for-github-insights#requirements-for-running-github-insights)". ![Campo de URL de página principal](/assets/images/help/apps/github_apps_homepage_url.png) +8. En "User authorization callback URL" (URL de llamada de vuelta de autorización del usuario), escribe lo siguiente, reemplazando `` con la URL del servidor de aplicaciones. + ``` + /Public/applogin + ``` + ![Campo llamada de vuelta de autorización del usuario](/assets/images/help/apps/github_apps_user_authorization.png) +9. En "Setup URL" (configurar URL), escribe `/public/setup`. ![Campo de configuración de URL](/assets/images/help/apps/github-apps-setup-url.png) +9. En "Webhook URL" (URL de webhook), escribe `/webhooks`. ![Campo de URL de webhook](/assets/images/help/apps/github_apps_webhook_url.png) +10. En "Secreto de webhook", escribe un secreto y luego graba el secreto para una referencia posterior. ![Campo secreto de webhook](/assets/images/help/apps/github_apps_webhook_secret.png) +11. En "Permissions" (permisos), usa los menús desplegables y configura los siguientes permisos para la app. + - Repositorio: + - Contenido: **De solo lectura** + - Metadatos: **De solo lectura** + - Solicitudes de extracción: **De solo lectura** + - Estados de confirmación: **De solo lectura** + - Organización: + - Miembros: **De solo lectura** + - Proyectos: **De solo lectura** + + ![Menús desplegables de permisos](/assets/images/help/apps/github_apps_new_permissions_post2dot13.png) +12. En "Subscribe to Events" (suscribirse a eventos), selecciona: + - Miembro + - Solicitud de extracción + - Subir + - Repositorio + - Equipo![Casillas de verificación para suscribirse a eventos](/assets/images/help/apps/github_apps_subscribe_to_events_pr_push_repository.png) + +13. Para habilitar el {% data variables.product.prodname_github_app %} para acceder a los datos de cualquier usuario u organización en {% data variables.product.product_location %}, en "¿Dónde puede {% data variables.product.prodname_github_app %} ser instalado? ", selecciona **Cualquier cuenta**. ![Botones de opción para habilitar el acceso a cualquier cuenta](/assets/images/help/apps/github_apps_installation_options_any_account.png) +14. Haz clic en **Create (crear) {% data variables.product.prodname_github_app %}**. ![Botón crear una app de GitHub](/assets/images/help/apps/github_apps_create_github_app.png) +15. Revisa la configuración de tu app. +16. En "Private Keys" (claves privadas), haz clic en **Generar una clave privada**. ![Genera un botón de llave privada](/assets/images/help/apps/generate-private-key.png) +17. Guarda el archivo PEM resultante para una referencia posterior. +18. Anota la siguiente información acerca de tu app para una referencia posterior. + - ID de app + - ID de cliente + - Secreto del cliente + - Llave privada + - Secreto de webhook + +### Instalar {% data variables.product.prodname_insights %} + +{% data reusables.github-insights.download-latest-release %} +{% data reusables.github-insights.install-script %} +{% data reusables.github-insights.run-script %} + +### Configurar {% data variables.product.prodname_insights %} + +Para configurar {% data variables.product.prodname_insights %} para conectarse a {% data variables.product.prodname_ghe_server %}, debes proporcionar la información que grabaste en los pasos anteriores. + +1. En tu navegador, desplázate hasta `/setup`. +{% data reusables.github-insights.enterprise-api-url %} +{% data reusables.github-insights.insights-license %} +{% data reusables.github-insights.app-id %} +{% data reusables.github-insights.client-id %} +{% data reusables.github-insights.client-secret %} +{% data reusables.github-insights.private-key %} +{% data reusables.github-insights.webhook-secret %} +{% data reusables.github-insights.skip-ssl %} +11. Haz clic en **Submit** (enviar). +12. Haz clic en **Log in with (inicia sesión con) {% data variables.product.prodname_dotcom %}**. +13. Para autorizar el {% data variables.product.prodname_github_app %} y acceder a {% data variables.product.prodname_insights %}, haz clic en **Authorize (autorizar) {% data variables.product.prodname_github_app %}**. + +### Further reading + +- "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)" +- "{% data variables.product.prodname_insights %} y protección de datos para tu organización" diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md new file mode 100644 index 0000000000000..3e6877fd9cfc3 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md @@ -0,0 +1,16 @@ +--- +title: Gestión de métricas e informes disponibles +intro: 'Puedes activar y desactivar métricas específicas en {% data variables.product.prodname_insights %}.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights +permissions: 'Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden administrar las métricas e informes disponibles.' +versions: + enterprise-server: '*' +--- + +Cuando inhabilitas una métrica, la métrica no será visible para ningún usuario, en cualquier lugar en {% data variables.product.prodname_insights %}. + +{% data reusables.github-insights.settings-tab %} +2. En **Settings (Ajustes de {% octicon "gear" aria-label="The gear icon" %})**, haz clic en **Toggle reports (Informes de conmutación)**. ![Pestaña Informes de conmutación](/assets/images/help/insights/toggle-reports-tab.png) +3. A la derecha de la métrica que deseas administrar, usa el menú desplegable **Enabled (Habilitado)** o **Disabled (Deshabilitado)**. ![Menú desplegable para métrica de conmutación](/assets/images/help/insights/toggle-report-drop-down.png) diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md new file mode 100644 index 0000000000000..020451a72a44a --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md @@ -0,0 +1,118 @@ +--- +title: Administrar colaboradores y equipos +intro: Puedes administrar las personas y los equipos incluidos en las métricas y los informes. +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/managing-contributors-and-teams +permissions: 'Las personas con permisos de administrador en {% data variables.product.prodname_insights %} pueden administrar colaboradores y equipos.' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '*' +--- + +### Acerca de los colaboradores y los equipos en {% data variables.product.prodname_insights %} + +Un colaborador en {% data variables.product.prodname_insights %} es una entidad asociada con los datos de {% data variables.product.prodname_enterprise %}. Puedes editar y ocultar los colaboradores. + +A veces, la misma persona puede aparecer como más de un colaborador. Por ejemplo, si una persona ha usado múltiples direcciones de correo electrónico de confirmación en Git, habrá un colaborador único para cada dirección de correo electrónico en {% data variables.product.prodname_insights %}. Puedes fusionar múltiples colaboradores para combinar todos los datos de una persona. + +También puedes agrupar los colaboradores en los equipos. Puedes usar los equipos como un filtro en los informes. Para obtener más información, consulta "[Ver métricas e informes clave](/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports)". + +### Editar un colaborador + +Puedes editar el nombre para mostrar de un colaborador en {% data variables.product.prodname_insights %}. + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.contributors-tab %} +{% data reusables.github-insights.edit-contributor %} +4. En "First Name" (nombre), escribe el nombre del colaborador. ![Campo de nombre](/assets/images/help/insights/first-name.png) +5. En "Last Name" (apellido), escribe el apellido del colaborador. ![Campo de apellido](/assets/images/help/insights/last-name.png) +6. Haz clic en **Rename** (Renombrar). + +### Administrar la visibilidad del colaborador + +Ocultar un colaborador excluye todos los datos asociados con ese colaborador de todas las métricas. + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.contributors-tab %} +{% data reusables.github-insights.edit-contributor %} +3. Selecciona o deselecciona **Show contributor** (mostrar colaborador). ![Casilla de verificación para mostrar u ocultar colaborador](/assets/images/help/insights/show-contributor.png) +4. Haz clic en **Done** (listo). + +### Fusionar datos del colaborador + +Cuando fusionas dos o más colaboradores, los datos {% data variables.product.prodname_insights %} para esos colaboradores se asocian con un colaborador principal. Todos los datos del colaborador fusionado pertenecen al colaborador principal en las métricas. + +Puedes fusionar colaboradores de manera manual o automática, según los colaboradores que {% data variables.product.prodname_insights %} ha detectado con nombres coincidentes. + +#### Fusionar automáticamente colaboradores + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.contributors-tab %} +3. En "All Contributors" (todos los colaboradores), haz clic en **Auto-Merge** (fusionar automáticamente) ![Botón fusionar automáticamente](/assets/images/help/insights/auto-merge.png) +4. Opcionalmente, para excluir que un colaborador se fusione, a la derecha del colaborador, haz clic en **Skip** (omitir). ![Botón omitir](/assets/images/help/insights/skip-contributor.png) +5. Para cada grupo, selecciona un colaborador principal. ![Botones de selección para seleccionar un colaborador principal](/assets/images/help/insights/select-primary.png) +6. Haz clic en **Merge All** (fusionar todos). + +#### Fusionar de forma manual los colaboradores + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.contributors-tab %} +3. Selecciona los colaboradores que deseas fusionar. ![Seleccionar colaboradores](/assets/images/help/insights/select-contributors.png) +4. En "All contributors", haz clic en **Merge** (fusionar). ![Botón fusionar](/assets/images/help/insights/merge-button.png) +5. Selecciona un colaborador principal. ![Botones de selección para seleccionar un colaborador principal](/assets/images/help/insights/select-primary.png) +6. Haz clic en **Merge accounts** (fusionar cuentas). + +#### Deshacer la fusión de un colaborador + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.contributors-tab %} +4. A la derecha del colaborador, haz clic en **Unmerge** (deshacer la fusión). ![Botón deshacer fusión](/assets/images/help/insights/unmerge-contributor.png) + +### Administrar equipos en {% data variables.product.prodname_insights %} + +Existen dos tipos de equipos en {% data variables.product.prodname_insights %}: equipos importados desde {% data variables.product.product_name %} y equipos personalizados. + +Cuando se agrega una organización a {% data variables.product.prodname_insights %}, todos los equipos de éstas se importan desde {% data variables.product.product_name %}. Puedes buscar y filtrar por estos equipos en {% data variables.product.prodname_insights %}. Puedes administrar equipos en {% data variables.product.product_name %}. + +Puedes crear y administrar equipos personalizados en {% data variables.product.prodname_insights %}. Los equipos personalizados podrían incluir miembros de organizaciones múltiples en {% data variables.product.product_name %}. + +#### Creear un equipo personalizado + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.teams-tab %} +2. A la derecha de "Teams" (equipos), haz clic en **Create Team** (crear equipo). ![Botón crear equipo](/assets/images/help/insights/create-team.png) +3. En "Team name" (nombre del equipo), escribe un nombre único para tu equipo. ![Campo de nombre del equipo](/assets/images/help/insights/team-name.png) +4. Da clic en **Crear**. + +#### Agregar colaboradores a un equipo personalizado + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.teams-tab %} +{% data reusables.github-insights.edit-team %} +3. En "Contributors" (colaboradores), usa el menú desplegable y selecciona un colaborador. ![Menú desplegable de colaboradores](/assets/images/help/insights/contributors-drop-down.png) +4. Haz clic en **Done** (listo). + +#### Eliminar a un colaborador de un equipo personalizado + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.teams-tab %} +{% data reusables.github-insights.edit-team %} +3. A la derecha del colaborador que deseas eliminar, haz clic en {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Botón papelera](/assets/images/help/insights/contributor-trashcan.png) + +#### Renombrar un equipo personalizado + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.teams-tab %} +{% data reusables.github-insights.edit-team %} +3. En "Team name" (nombre del equipo), escribe un nombre único para tu equipo. ![Campo de nombre del equipo](/assets/images/help/insights/rename-team.png) +4. Haz clic en **Rename** (Renombrar). ![Botón renombrar](/assets/images/help/insights/rename-button-team.png) +5. Haz clic en **Done** (listo). + +#### Borrar un equipo personalizado + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.teams-tab %} +{% data reusables.github-insights.edit-team %} +3. Haz clic en **Delete Team** (eliminar equipo). ![Botón eliminar equipo](/assets/images/help/insights/delete-team.png) +4. Haz clic en **Confirm (Confirmar)**. diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md new file mode 100644 index 0000000000000..f512c60d89599 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md @@ -0,0 +1,11 @@ +--- +title: Administrar datos en GitHub Insights +shortTitle: Administrar datos +intro: 'Puedes elegir qué métricas se muestran en {% data variables.product.prodname_insights %} y qué organizaciones, repositorios y personas están incluidas en esas métricas. Puedes configurar objetivos y agregar contexto a las métricas.' +mapTopic: verdadero +redirect_from: + - /github/installing-and-configuring-github-insights/managing-data-in-github-insights +versions: + enterprise-server: '*' +--- + diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md new file mode 100644 index 0000000000000..bdcd8ca1bd9d6 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md @@ -0,0 +1,33 @@ +--- +title: Administrar eventos +intro: '{% data reusables.github-insights.events %}' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/creating-and-managing-events +permissions: 'Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden administrar eventos.' +versions: + enterprise-server: '*' +--- + +### Acerca de los eventos + +Los eventos agregan contexto a las métricas. Por ejemplo, las fechas de vacaciones o de lanzamiento pueden causar cambios en los patrones de trabajo, por lo que saber cuándo ocurrieron esos eventos puede cambiar tu evaluación de las métricas. Puedes crear eventos para la reorganización de los equipos, las fechas de inicio de los nuevos empleados, los cambios en el alcance de los equipos y cualquier otra cosa que afecte el trabajo de tu equipo. + +Después de crear un evento en {% data variables.product.prodname_insights %}, cualquier persona puede ver el evento como una anotación en algunas métricas. Para obtener más información, consulta "[Ver métricas e informes clave](/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports)". + +### Crear un evento + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.events-tab %} +2. Haz clic en **Add Event** (agregar evento). ![Botón agregar evento](/assets/images/help/insights/add-event.png) +3. En "Title" (título), escribe un nombre descriptivo para tu evento. ![Campo de título](/assets/images/help/insights/title-field.png) +4. Usa el menú desplegable "Start Date" (iniciar fecha) y selecciona una fecha de inicio para tu evento. ![Menú desplegable de fecha de inicio](/assets/images/help/insights/start-date.png) +5. Usa el menú desplegable "End Date" (fecha de finalización) y selecciona una fecha de finalización para tu evento. ![Menú desplegable de fecha de finalización](/assets/images/help/insights/end-date.png) +6. Haz clic en **Save ** (guardar). + +### Eliminar un evento + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.events-tab %} +3. A la derecha del evento que deseas eliminar, haz clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botón papelera](/assets/images/help/insights/trashcan-button.png) +4. Haz clic en **Confirm (Confirmar)**. diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md new file mode 100644 index 0000000000000..ea8dce009b978 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md @@ -0,0 +1,26 @@ +--- +title: Administrar objetivos +intro: Puedes utilizar objetivos para configurar metas para las métricas clave y medir el éxito al lograr dichas metas. +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/creating-and-managing-goals +permissions: 'Cualquiera con acceso a {% data variables.product.prodname_insights %} puede administrar metas.' +versions: + enterprise-server: '*' +--- + +### Acerca de las metas + +Las metas son objetivos que puedes configurar para que las métricas clave midan el éxito de tu equipo. Cuando configuras una meta para una métrica clave, puedes ver cómo se compara el rendimiento de tu equipo con la meta utilizando una línea de meta en los gráficos y en la métrica de tasa de éxito. Por ejemplo, puedes configurar la meta de `code review turnaround time` para que sea de 4 horas. Una línea de meta en los gráficos de métricas clave muestra qué revisiones de código lograron la meta y cuáles no lo hicieron. Si tu equipo completa la mitad de las revisiones de código en menos de 4 horas, tu `success rate` será de 50%. + +Las metas sólo se encuentran disponibles en métricas clave. Algunos reportes también muestran qué trabajo, tal como las solicitudes de extracción individuales, no cumplió con tu meta. Para obtener más información, consulta "[Ver métricas e informes clave](/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports)". + +Las metas no pueden crearse o borrarse. Cuando editas una meta, esta nueva meta aplica a todo aquél que use tu aplicación de {% data variables.product.prodname_insights %}. + +### Editar una meta + +{% data reusables.github-insights.navigate-to-key-metrics %} +{% data reusables.github-insights.choose-key-metric %} +1. A la derecha de la meta, da clic en {% octicon "gear" aria-label="The gear icon" %}. ![Icono de engrane para editar meta](/assets/images/help/insights/edit-goal.png) +2. En el campo de texto, teclea un nuevo valor para la meta. ![Campo de valor de la meta](/assets/images/help/insights/input-goal.png) +3. Haz clic en **Save ** (guardar). ![Guardar meta](/assets/images/help/insights/save-goal.png) diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md new file mode 100644 index 0000000000000..86c57d66b1c42 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md @@ -0,0 +1,39 @@ +--- +title: Administrar organizaciones +intro: 'Puedes administrar las organizaciones {% data variables.product.prodname_enterprise %} que están incluidas en las métricas.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/managing-organizations +permissions: 'Las personas con permisos de administrador en {% data variables.product.prodname_insights %} pueden administrar organizaciones.' +versions: + enterprise-server: '*' +--- + +### Acerca de la administración de la organización + +Cuando agregas una organización a {% data variables.product.prodname_insights %}, los repositorios que son propiedad de esa organización se incluyen en las métricas. Puedes elegir agregar todos los repositorios o seleccionar repositorios específicos para agregar. + +Puedes agregar una organización a {% data variables.product.prodname_insights %} si eres propietario de esa organización en {% data variables.product.prodname_enterprise %}. Si no eres propietario de la organización, puedes enviar una solicitud para que un propietario agregue la organización a {% data variables.product.prodname_insights %}. + +### Agregar una organización a {% data variables.product.prodname_insights %} + +Agregar una organización a {% data variables.product.prodname_insights %} instala el {% data variables.product.prodname_github_app %} para {% data variables.product.prodname_insights %} en esa organización. Para obtener más información acerca de {% data variables.product.prodname_github_app %}, consulta [Instalar {% data variables.product.prodname_insights %}](/github/installing-and-configuring-github-insights/installing-github-insights)". + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repositories-tab %} +{% data reusables.github-insights.add-organizations %} +4. Haz clic en la organización que deseas agregar a {% data variables.product.prodname_insights %}. +5. Selecciona si deseas agregar todos los repositorios o especificar los repositorios que deseas incluir. ![Casillas de verificación para agregar todos los repositorios o seleccionar repositorios](/assets/images/help/insights/all-or-select-repos.png) +6. Si eliges instalar {% data variables.product.product_name %} en repositorios selectos, usa el menú desplegable y selecciona los repositorios que deseas incluir. ![Menú desplegable para seleccionar repositorios](/assets/images/help/insights/select-repos.png) +5. Haz clic en **Install** (instalar) o **Request** (solicitar). + +### Eliminar una organización de {% data variables.product.prodname_insights %} + +Eliminar una organización de {% data variables.product.prodname_insights %} desinstala el {% data variables.product.prodname_github_app %} para {% data variables.product.prodname_insights %} de la organización. Para obtener más información acerca de {% data variables.product.prodname_github_app %}, consulta [Instalar {% data variables.product.prodname_insights %}](/github/installing-and-configuring-github-insights/installing-github-insights)". + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repositories-tab %} +{% data reusables.github-insights.add-organizations %} +4. Haz clic en la organización que deseas eliminar de {% data variables.product.prodname_insights %}. +4. En "Uninstall (desinstalar) {% data variables.product.prodname_insights %}", haz clic en **Uninstall**. ![Botón desinstalar](/assets/images/help/insights/uninstall-button.png) +5. Haz clic en **OK** (aceptar). diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md new file mode 100644 index 0000000000000..e8f23fe051018 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md @@ -0,0 +1,14 @@ +--- +title: Gestionar permisos en GitHub Insights +intro: 'Puedes actualizar los permisos de un usuario en {% data variables.product.prodname_insights %}.' +product: '{% data reusables.gated-features.github-insights %}' +permissions: 'Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden administrar los permisos.' +versions: + enterprise-server: '*' +--- + +{% data reusables.github-insights.permissions-levels %} + +Si deseas otorgar permisos de administrador a alguien que no sea un administrador del sitio en {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.github_support %}. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Emitir un ticket](/github/working-with-github-support/submitting-a-ticket)".{% else %}"[Contactar a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/reaching-github-support)".{% endif %} + +Para eliminar el acceso de un usuario de {% data variables.product.prodname_insights %}, debes eliminar al usuario de {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md new file mode 100644 index 0000000000000..16c5cdced4623 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md @@ -0,0 +1,114 @@ +--- +title: Administrar repositorios +intro: 'Puedes administrar los repositorios conectados a {% data variables.product.prodname_insights %} y los datos incluidos en las métricas de cada repositorio.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/managing-repositories +permissions: 'Las personas con permisos de administrador en {% data variables.product.prodname_insights %} puede administrar repositorios.' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '*' +--- + +### Acerca de la administración del repositorio + +Para que {% data variables.product.prodname_insights %} incluya datos de un repositorio en {% data variables.product.prodname_enterprise %}, debes agregar la organización a la que pertenece el repositorio a {% data variables.product.prodname_insights %}. Para obtener más información, consulta "[Administrar organizaciones](/github/installing-and-configuring-github-insights/managing-organizations)." + +Después de agregar una organización a {% data variables.product.prodname_insights %}, cada repositorio que le pertenece a la organización se importa automáticamente si el repositorio: +- Tiene al menos una confirmación +- No es privado +- No se archiva +- Ha sido subido en los últimos 6 meses + +Los datos del repositorio se actualizan mediante webhooks y sincronizaciones periódicas. Puedes actualizar de forma manual los datos del repositorio en cualquier momento o cancelar una importación de datos que esté en progreso. + +{% data reusables.github-insights.repository-groups %} + +Puedes excluir archivos específicos de {% data variables.product.prodname_insights %} para un repositorio específico o para todos los repositorios. + +### Acerca de los tiempos de importación + +{% data variables.product.prodname_insights %} importa los últimos tres años de datos para cada repositorio. Dependiendo del tamaño y la complejidad de tus repositorios, la importación inicial puede demorar un tiempo, durante el cual los datos de {% data variables.product.prodname_insights %} están incompletos. Habitualmente, la importación inicial de unos cuantos equipos tomará un día o dos. Las importaciones iniciales largas y complejas pueden tomar hasta dos semanas. + +| Tamaño del repositorio | Tiempo de importación inicial | +| ---------------------------------- | ----------------------------- | +| < 10.000 confirmaciones | < 1 hora | +| de 10,000 a 300,000 confirmaciones | de 1 a 10 días | +| 300,000 confirmaciones o más | 10 días o más | + +Una vez que se completa la importación inicial, las importaciones posteriores de los cambios incrementales deberían demorar dos minutos o menos. + +Para reducir los tiempos de importación, puedes excluir cualquier biblioteca de terceros en carpetas no estándar desde {% data variables.product.prodname_insights %} antes de la importación. Para obtener más información, consulta "[Administrar filtros de exclusión](#managing-exclusion-filters)." + +Si tienes muchos repositorios de gran tamaño, puedes mejorar los tiempos de importación iniciales al proporcionar más núcleos al servidor de aplicaciones. Los servidores de aplicaciones con más núcleos pueden realizar más trabajos paralelos de importación. + +| Núcleos de servidores de aplicaciones | Trabajos paralelos de importación inicial | +| ------------------------------------- | ----------------------------------------- | +| 16 núcleos | 1 job | +| 32 núcleos | 4 puestos de trabajo | + +Importar un gran número de solicitudes de extracción puede desencadenar la limitación de tasa desde {% data variables.product.prodname_enterprise %}. En este caso, la importación se detendrá durante una hora antes de reanudarse. Puedes aumentar de forma temporal el límite de tasa de {% data variables.product.prodname_enterprise %} para mejorar los tiempos de importación. Para obtener más información, consulta "[Configurar límites de tasa](/enterprise/{{ currentVersion }}/admin/installation/configuring-rate-limits)." + +### Ver y administrar repositorios + +Puedes ver los repositorios importados y los repositorios que están disponibles para importar. Si una importación está en progreso, puedes ver el estado de la importación y una estimación de tiempo hasta que se complete la importación. + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repositories-tab %} +3. Como alternativa, para agregar un repositorio que no se ha importado, a la derecha del nombre del repositorio, haz clic en **Add (Añadir)**. ![Botón Add (Agregar)](/assets/images/help/insights/add-button.png) +4. Como alternativa, para actualizar de forma manual los datos del repositorio, a la derecha del nombre del repositorio, haz clic en el icono de actualización **{% octicon "sync" aria-label="The refresh icon" %}**. ![Botón Actualizar](/assets/images/help/insights/refresh-button.png) +5. Como alternativa, para cancelar una importación en progreso, a la derecha del nombre del repositorio, haz clic en **Cancel (Cancelar)**. ![Botón Cancelar](/assets/images/help/insights/cancel-button.png) +6. Como alternativa, para eliminar un repositorio importado, a la derecha del nombre del repositorio, haz clic en **Remove (Eliminar)**. ![Botón Eliminar](/assets/images/help/insights/remove-button.png) + +### Administrar grupos de repositorios para informes + +Puedes crear un grupo de repositorios, agregar o eliminar repositorios a un grupo y eliminar un grupo de repositorios. + +#### Crear un grupo de repositorios + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repo-groups-tab %} +2. En el ángulo superior derecho, haz clic en **Create group (Crear grupo)**. ![Botón Crear grupo](/assets/images/help/insights/create-group.png) +3. En "Group Name" (Nombre del grupo), escribe un nombre para tu grupo. ![Campo de nombre de grupo](/assets/images/help/insights/group-name.png) +4. Da clic en **Crear**. + +#### Agregar un repositorio a un grupo de repositorios + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repo-groups-tab %} +{% data reusables.github-insights.edit-group %} +4. En "Repositories" (Repositorios), usa el menú desplegable y selecciona un repositorio para agregar al grupo. ![Menú desplegable de repositorios](/assets/images/help/insights/repositories-drop-down.png) +5. Haz clic en **Done** (listo). + +#### Eliminar un grupo de repositorios + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.repo-groups-tab %} +{% data reusables.github-insights.edit-group %} +4. Haz clic en **Delete Group (Eliminar grupo)**. ![Botón Eliminar grupo](/assets/images/help/insights/delete-group.png) +5. Haz clic en **Confirm (Confirmar)**. + +### Administrar filtros de exclusión + +Puedes crear una lista de reglas de exclusión de archivos para omitir los archivos especificados de todos los datos de {% data variables.product.prodname_insights %}. Las reglas de exclusión de archivos siguen las mismas reglas que se usan en los archivos *. gitignore*. Para obtener más información, consulta "[gitignore](https://git-scm.com/docs/gitignore)"en la documentación de Git. + +#### Agregar una regla de exclusión de archivos para todos los repositorios + +Los cambios en las exclusiones de archivos globales solo se aplican a los datos recién importados y no afectarán de manera retroactiva a los datos existentes. Para aplicar nuevas reglas de exclusión a los datos existentes, puedes eliminar y volver a agregar repositorios a {% data variables.product.prodname_insights %}. + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.exclude-files-tab %} +3. De manera opcional, en "Exclude files" (Excluir archivos), selecciona **Include all binaries (Incluir todos los binarios)**. ![Casilla de verificación para incluir todos los binarios](/assets/images/help/insights/include-all-binaries-global.png) +4. En el editor de código, agrega una nueva regla de exclusión a la lista. ![Editor de código para agregar una regla de exclusión global](/assets/images/help/insights/global-exclusion-list.png) +5. Haz clic en **Save Changes (Guardar cambios)**. + +#### Agregar una regla de exclusión de archivos para un repositorio + +{% data reusables.github-insights.settings-tab %} +{% data reusables.github-insights.exclude-files-tab %} +3. A la derecha de "Repositories with File Filters" (Repositorios con filtros de archivos), haz clic en **Add Filter (Agregar filtro)**. ![Botón Agregar filtro](/assets/images/help/insights/add-filter.png) +4. Usa el menú desplegable "Repository" (Repositorio) y selecciona un repositorio. ![Menú desplegable del repositorio](/assets/images/help/insights/repository-drop-down-exclude.png) +5. De forma opcional, para aplicar reglas de exclusión a los datos existentes, selecciona **Re-import (Volver a importar)**. ![Casilla de verificación de re-importación](/assets/images/help/insights/re-import-checkbox.png) +6. Como alternativa, selecciona **Include all binaries (Incluir todos los binarios)**. ![Casilla de verificación para incluir todos los binarios](/assets/images/help/insights/include-all-binaries-repo.png) +7. En el editor de código, agrega las reglas de exclusión que deseas aplicar al repositorio. ![Editor de código para agregar una regla de exclusión de repositorios](/assets/images/help/insights/repo-exclusion-list.png) +8. Haz clic en **Create Filter (Crear filtro)**. diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md new file mode 100644 index 0000000000000..7f39d8b0a91a1 --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md @@ -0,0 +1,55 @@ +--- +title: Descripción general del sistema para la información de GitHub +intro: '{% data variables.product.prodname_insights %} es una aplicación autónoma que interactúa con {% data variables.product.prodname_enterprise %}.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/system-overview-for-github-insights +versions: + enterprise-server: '*' +--- + +### Requisitos para la ejecución {% data variables.product.prodname_insights %} + +{% data variables.product.prodname_insights %} requiere una versión compatible de {% data variables.product.prodname_ghe_server %}. + +{% data reusables.github-insights.requires-machine %} Se admiten máquinas de tipo estándar con un sistema operativo base de Debian Buster, Debian Stretch o cualquier versión LTS de Ubuntu 16.04 +. + +Para aprovisionar {% data variables.product.prodname_insights %}, el servidor de aplicaciones debe poder ejecutar ciertas dependencias, incluido Docker. {% data reusables.github-insights.docker-requirements %} Para obtener más información, consulta "[Instalar {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/installing-github-insights#prerequisites)". + +El servidor de aplicaciones debe cumplir con las especificaciones mínimas. + +| Especificación | Mínimo | +| -------------- | ------ | +| vCPU | 16 | +| Ram | GB | +| Disco | 250GB | + +Si vas a usar {% data variables.product.prodname_insights %} para importar grandes cantidades de datos, recomendamos especificaciones mínimas mayores. Para obtener más información, consulta "[Administrar repositorios](/github/installing-and-configuring-github-insights/managing-repositories#about-import-times)." + +### Seguridad y autenticación para {% data variables.product.prodname_insights %} + +{% data variables.product.prodname_insights %} se ejecuta en tu infraestructura y se rige por tus controles de seguridad de la información existentes. {% data variables.product.prodname_insights %} utiliza cuentas de usuario existentes en {% data variables.product.prodname_enterprise %} para autenticación y permisos de acceso. + +#### Seguridad de la red + +El firewall interno de {% data variables.product.prodname_insights %} restringe el acceso a la red a los servicios del servidor de la aplicación. Solo se encuentran disponibles en la red los servicios necesarios para que el servidor de aplicación funcione. + +{% data variables.product.prodname_insights %} requiere que los siguientes puertos estén abiertos para el tráfico entrante y saliente. + +| Port (Puerto) | Servicio | Protocolo | +| ------------- | -------------- | --------- | +| 22 | USUARIO DE SSH | TCP | +| 80 | USUARIO HTTP | TCP | +| 443 | USUARIO HTTPS | TCP | + +#### Permisos de autenticación y acceso + +La autenticación para {% data variables.product.prodname_insights %} se maneja mediante {% data variables.product.prodname_enterprise %}. Durante la instalación, crearás un {% data variables.product.prodname_github_app %}, que permite que {% data variables.product.prodname_insights %} autorice a los usuarios. El {% data variables.product.prodname_github_app %} también se usa para interactuar con {% data variables.product.prodname_enterprise %} dentro del alcance de los permisos del usuario y de la app. + +{% data reusables.github-insights.permissions-levels %} + +El acceso a los datos en {% data variables.product.prodname_insights %} está restringido según el acceso a los datos de cada usuario en {% data variables.product.prodname_enterprise %}. Un usuario nunca verá datos en {% data variables.product.prodname_insights %} para los repositorios a los que el usuario no tiene acceso en {% data variables.product.prodname_enterprise %}. + +### Arquitectura de {% data variables.product.prodname_insights %} + +![Arquitectura del sistema](/assets/images/help/insights/github-isights-system-diagram.png) diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md new file mode 100644 index 0000000000000..661040fac137d --- /dev/null +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md @@ -0,0 +1,36 @@ +--- +title: Actualizar la información de GitHub +intro: 'Puedes actualizar a la última versión de {% data variables.product.prodname_insights %} para beneficiarte de las mejoras y correcciones de errores.' +product: '{% data reusables.gated-features.github-insights %}' +redirect_from: + - /github/installing-and-configuring-github-insights/updating-github-insights +permissions: 'Las personas con permisos de lectura para el repositorio de `github/insights-releases` y el acceso administrativo al servidor de aplicaciones pueden actualizar {% data variables.product.prodname_insights %}.' +versions: + enterprise-server: '*' +--- + +### Acerca de las actualizaciones {% data variables.product.prodname_insights %} + +Antes de actualizar {% data variables.product.prodname_insights %}, puedes comprobar la versión que estás usando actualmente en el ángulo inferior derecho de cualquier página. + +El proceso de actualización tardará hasta 10 minutos. Durante este tiempo, los usuarios no pueden acceder a {% data variables.product.prodname_insights %}. + +### Actualizar desde {% data variables.product.prodname_insights %} 0.4.0 + + +Para actualizar {% data variables.product.prodname_insights %} desde 0.4.0 +, puedes instalar la última versión. {% data variables.product.prodname_insights %} pedirá que uses la configuración de instalación anterior. + +{% data reusables.github-insights.download-latest-release %} +4. Ejecuta el script del shell `Install.sh`. +5. Si el SSL se habilitó previamente, {% data variables.product.prodname_insights %} encontrará un certificado SSL existente. Escribe "Y" para aceptar o "n" para cambiar el certificado SSL o inhabilitar SSL. +6. Si el SSL se habilitó previamente, {% data variables.product.prodname_insights %} encontrará una clave SSL existente. Escribe "Y" para aceptar o "n" para cambiar la clave SSL. +5. {% data variables.product.prodname_insights %} encontrará un nombre de host existente. Escribe "Y" para aceptar o "n" para ingresar a un nombre de host diferente. El nombre del host es la misma URL que usaste para el servidor de aplicaciones al crear el {% data variables.product.prodname_github_app %}. +6. La instalación tomará unos cuantos minutos en ejecutarse. Una vez que esté completo, verás un mensaje impreso en el terminal. + ``` + Installation complete + Run /opt/insights/scripts/start.sh to start GitHub Insights + ``` +{% data reusables.github-insights.run-script %} + +### Actualizar desde {% data variables.product.prodname_insights %} 0.3.1 o inferior + +Las versiones {% data variables.product.prodname_insights %} 0.3.1 o inferiores no son compatibles con las versiones 0.4.0+. Para actualizar desde {% data variables.product.prodname_insights %} 0.3.1 o inferior, instalar y configurar {% data variables.product.prodname_insights %} en un nuevo servidor de aplicaciones. diff --git a/translations/es-ES/content/packages/guides/about-github-container-registry.md b/translations/es-ES/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000000..8cb24fb210fcf --- /dev/null +++ b/translations/es-ES/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +title: Acerca del Registro Contenedor de GitHub +intro: 'Puedes utilizar el {% data variables.product.prodname_github_container_registry %} para hospedar y mantener contínuamente las imágenes de contenedor de Docker en tu cuenta de organización o de usuario personal de {% data variables.product.prodname_dotcom %}. El {% data variables.product.prodname_github_container_registry %} te permite configurar quién puede administrar y acceder a los paquetes utilizandopermisos específicos.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** El {% data variables.product.prodname_github_container_registry %} se encuentra actualmente en su fase de beta público y está sujeto a cambios. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la característica para tu cuenta. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)". + +{% endnote %} + +### Acerca de {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.container-registry-feature-highlights %} + +Para compartir el contexto sobre el uso de tu paquete, puedes vincular un repositorio a tu imagen de contenedor en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Conectar un repositorio a una imagen de contenedor](/packages/guides/connecting-a-repository-to-a-container-image)". + +El {% data variables.product.prodname_github_container_registry %} tiene ubicaciones de hospedaje, permisos y visibilidades diferentes a las de otros registros de paquete. + +| | Registros de los paquetes | {% data variables.product.prodname_github_container_registry %} +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Ubicaciones de hospedaje | Puedes hospedar paquetes múltiples en un repositorio. | Puedes hospedar imagenes de contenedor múltiples en una cuenta de organización o de usuario. | +| Permisos | {{ site.data.reusables.package_registry.public-or-private-packages }} Puedes utilizar los roles y equipos de {{ site.data.variables.product.prodname_dotcom }} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | Para cada imagen de contenedor, puedes elegir el nivel de acceso que tienen los demás. Los permisos para acceso a la imagen de contenedor son independientes de aquellos para tu organización y repositorio. | + Visibilidad | {% data reusables.package_registry.public-or-private-packages %} | Puedes configurar la visibilidad de cada una de tus imagenes de contenedor. Solo las personas y equipos a las cuales se les haya otorgado acceso dentro de tu organización podrán ver las imágenes de contenedor privadas. Cualquiera puede ver las imágenes de contenedor públicas. | Acceso anónimo | N/A | Puedes acceder anónimamente a las imágenes de contenedor públicas. + +Para obtener más información, consulta la sección "[Acerca de los alcances y permisos para {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)". + +### Formatos compatibles + +El {% data variables.product.prodname_container_registry %} es actualmente compatible con los siguientes formatos de contenedores de imagen: + +* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Especificaciones de Open Container Initiavie (OCI)](https://github.com/opencontainers/image-spec) + +El {% data variables.product.prodname_github_container_registry %} hospeda los contenedores en `ghcr.io/OWNER/IMAGE-NAME`. + +| Cliente del paquete | Lenguaje | Formato del paquete | Descripción | +| ------------------- | -------- | ------------------- | ----------------------- | +| docker | N/A | `Dockerfile` | Gestor de paquetes Node | + + +#### Índices de Listas/Imágenes de Manifiesto + +El {% data variables.product.prodname_github_container_registry %} también es compatible con los formatos de la [Lista de Manifiestos de Docker](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/el [Índice de Imágenes de OCI](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) que se definen en las especificaciones de Docker V2, Modelo 2, y de la Imágen de OCI. + +### Permisos de visibilidad y acceso para las imágenes de contenedor + +Si tienes permisos administratibos en una imagen de contenedor, puedes configurar la imagen de la misma como privada o pública. Las imágenes públicas permiten el acceso anónimo y pueden extraerse sin autenticación o ingresar a ellas através del CLI. + +Como administrador, también puedes otorgar permisos de acceso para una imagen de contenedor que esté separada de los permisos que configuraste a nivel de organización y de repositorio. + +Puedes otorgar un rol de acceso a cualquier persona en el caso de las imagenes de contenedor que pertenecen a, o que publica una cuenta de usuario. Puedes otorgar un rol de acceso a cualquier persona o equipo en la organización para las imágenes de contenedor que pertenecen a, o que publica una cuenta de usuario. + +| Rol de permisos | Descripción del acceso | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Read | Puede descargar el paquete.
Puede leer los metadatos del paquete. | +| Escritura | Puede cargar y descargar este paquete.
Puede leer y escribir metadatos del paquete. | +| Admin | Puede cargar, descargar, borrar y administrar este paquete.
Puede leer y escribir metadatos del paquete.
Puede otorgar permisos del paquete. | + +Para obtener más información, consulta la sección "[Configurar el control de accesos y la visibilidad para las imagenes de contenedor](/packages/guides/configuring-access-control-and-visibility-for-container-images)". + +### Sobre tokens + +Para instalar o publicar un paquete, debes usar un token con el ámbito adecuado, y tu cuenta de usuario debe tener los permisos pertinentes para ese repositorio. + +| Ámbito | Descripción | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `read:packages` | Descarga e instala las imágenes de contenedor desde {% data variables.product.prodname_github_container_registry %} +| `write:packages` | Carga y publica las imágenes de contenedor a {% data variables.product.prodname_github_container_registry %} +| `delete:packages` | Borra versiones específicas de imágenes de contenedor privadas o públicas del {% data variables.product.prodname_github_container_registry %}. Para obtener más información, consulta la sección "[Borrar una imagen de contenedor](/packages/guides/deleting-a-container-image)". | + +Para aprender más sobre los alcances y permisos disponibles para las imágenes de contenedor, consulta la sección "[Configurar el control de accesos y la visibilidad para las imagenes de contenedor](/packages/guides/configuring-access-control-and-visibility-for-container-images)". + +Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)" y "[Alcances disponibles](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)". + +### Acerca de la facturación para {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.billing-for-container-registry %} + +### Contactar con soporte técnico + +Si tienes retroalimentación o solicitudes de características para el {% data variables.product.prodname_github_container_registry %}, utiliza el [formato de retroalimentación](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). + +Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_github_container_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: + +* Experimentas alguna cosa que contradice la documentación. +* Encuentras errores vagos o poco claros. +* Tu paquete publicado contiene datos sensibles, tales como violaciones del RGPD, Claves de la API, o información de identificación personal. diff --git a/translations/es-ES/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/es-ES/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000000..57d7692d724ae --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: Configurar el control de accesos y la visibilidad para las imagenes de contenedor +intro: 'Elige quién ha leído, escrito, o administrado el acceso a tu imagen de contenedor y la visibilidad de tus imágenes de contenedor en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Configurar el acceso a las imágenes de contenedor para tu cuenta personal + +Si tienes permisos de administrador para una imagen de contenedor que pertenezca a una cuenta de usuario, puedes asignar, leer, escribir, o administrar roles para otros usuarios. Para obtener más información acerca de estos roles de permisos, consulta la sección "[Permisos de visibilidad y acceso para las imágenes de contenedor](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)". + +{% data reusables.package_registry.package-settings-from-user-level %} +1. En la página de configuración del paquete, da clic en **Invitar equipos o personas** e ingresa el nombre real, nombre de usuario, o dirección de correo electrónico de la persona a la que quieras dar acceso. No se puede otorgar acceso a los equipos para aquellas imágenes de contenedor que pertenezcan a una cuenta de usuario. ![Botón de invitación para el acceso al contenedor](/assets/images/help/package-registry/container-access-invite.png) +1. Junto al equipo o nombre de usuario, utiliza el menú desplegable de "Rol" para seleccionar un nivel de permisos que desees. ![Opciones de acceso al contenedor](/assets/images/help/package-registry/container-access-control-options.png) + +Se otorgará acceso automáticamente a los usuarios seleccionados y no necesitarán aceptar una invitación previamente. + +### Configurar el acceso a las imágenes de contenedor para una organización + +Si tienes permisos administrativos en una imágen de contenedor que pertenezca a una organización, puedes asignar roles de lectura, escritura o administración a otros usuarios y equipos. Para obtener más información acerca de estos roles de permisos, consulta la sección "[Permisos de visibilidad y acceso para las imágenes de contenedor](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)". + +Si tu paquete pertenece a una organización y es privador, entonces solo podrás dar acceso a otros miembros o equipos de la organización. + +Para los contenedores de imagen de la organizción, los administradores de la organización deben habilitar los paquetes antes de que puedas configurar la visibilidad como pública. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +{% data reusables.package_registry.package-settings-from-org-level %} +1. En la página de configuración del paquete, da clic en **Invitar equipos o personas** e ingresa el nombre real, nombre de usuario, o dirección de correo electrónico de la persona a la que quieras dar acceso. También puedes ingresar un nombre de equipo desde la organización para otorgar acceso a todos los miembros de éste. ![Botón de invitación para el acceso al contenedor](/assets/images/help/package-registry/container-access-invite.png) +1. Junto al equipo o nombre de usuario, utiliza el menú desplegable de "Rol" para seleccionar un nivel de permisos que desees. ![Opciones de acceso al contenedor](/assets/images/help/package-registry/container-access-control-options.png) + +Se otorgará acceso automáticamente a los usuarios o equipos seleccionados y no necesitarán aceptar una invitación previamente. + +### Configurar la visibilidad de las imágenes de contenedor para tu cuenta personal + +Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada y solo tú puedes verlo. Puedes modificar el acceso a las imágenes de contenedor públicas si cambias la configuración de acceso. + +Se puede acceder anónimamente a un paquete público sin autenticación. Una vez que hagas tu paquete público, no puedes hacerlo privado nuevamente. + +{% data reusables.package_registry.package-settings-from-user-level %} +5. Debajo de "Zona de peligro", elige una configuración de visibilidad: + - Para que la imagen del contenedor sea visible para todos, da clic en **Hacer público**. + {% warning %} + + **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado. + + {% endwarning %} + - Para hacer la la imagen de contenedor sea visible para una selección personalizada de individuos, da clic en **Hacer privada**. ![Opciones de visibilidad del contenedor](/assets/images/help/package-registry/container-visibility-option.png) + +### Configurar la visibilidad de las imágenes de contenedor para una organización + +Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada y solo tú puedes verlo. Puedes otorgar roles de acceso diferentes a los usuarios o equipos para tu imagen de contenedor a través de la configuración de acceso. + +Se puede acceder anónimamente a un paquete público sin autenticación. Una vez que hagas tu paquete público, no puedes hacerlo privado nuevamente. + +Para las imágenes de contenedor organizacionales, los administradores de las organizaciones deben habilitar los paquetes públicos antes de que puedas configurar la visibilidad como pública. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +{% data reusables.package_registry.package-settings-from-org-level %} +5. Debajo de "Zona de peligro", elige una configuración de visibilidad: + - Para que la imagen del contenedor sea visible para todos, da clic en **Hacer público**. + {% warning %} + + **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado. + + {% endwarning %} + - Para hacer la la imagen de contenedor sea visible para una selección personalizada de individuos, da clic en **Hacer privada**. ![Opciones de visibilidad del contenedor](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000000..494b574592777 --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,197 @@ +--- +title: Configurar Apache Maven para usar con paquetes de GitHub +intro: 'Puedes configurar Apache Maven para publicar paquetes para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Java.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Puedes autenticar en {% data variables.product.prodname_registry %} con Apache Maven editando tu archivo *~/.m2/settings.xml* para incluir tu token de acceso personal. Crear un nuevo archivo *~/.m2/settings.xml* si no existe uno. + +En la etiqueta `servidores`, agrega una etiqueta `servidor` hijo con una `Id`, reemplazando *USERNAME* con tu nombre de usuario {% data variables.product.prodname_dotcom %} y *Token* con tu token de acceso personal. + +En la etiqueta `repositorios`, configura un repositorio al mapear el `Id` del repositorio a la `Id` que agregaste en la etiqueta `servidor` que contiene tus credenciales. Reemplaza {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* con el nombre del host de tu instancia de {% data variables.product.prodname_ghe_server %}, {% endif %}*REPOSITORY* con el nombre del repositorio en el cual te gustaría publicar un paquete, o desde el cual te gustaría instalar un paquete, y *OWNER* con el nombre de la cuenta de usuario o de organización a la cual pertenezca el repositorio. Dado que las letras mayúsculas no son compatibles, debes usar minúsculas para el propietario del repositorio si el nombre de usuario o el nombre de la organización de {% data variables.product.prodname_dotcom %} contiene letras mayúsculas. + +Si deseas interactuar con múltiples repositorios, puedes agregar cada repositorio para separar hijos del `repositorio` en la etiqueta `repositorios`, asignando la `Id` de cada una a las credenciales en la etiqueta `servidores`. + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### Autenticando con el `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar un paquete + +{% data reusables.package_registry.default-name %} Por ejemplo, {% data variables.product.prodname_dotcom %} publicará un paquete denominado `com.example:test` en un repositorio llamado `OWNER/test`. + +Si quisieras publicar paquetes múltiples en el mismo repositorio, puedes incluir la URL del mismo en el ``elemento del archivo *pom.xml*. {% data variables.product.prodname_dotcom %} coincidirá con el repositorio según ese campo. Dado que el nombre del repositorio también es parte del elemento `distributionManagement`, no hay pasos adicionales para publicar múltiples paquetes en el mismo repositorio. + +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + +1. Edita el elemento `distributionManagement` del archivo *POM.

+ +{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* con el nombre del host de tu instancia de {% data variables.product.prodname_ghe_server %}, {% endif %}`OWNER` con el nombre de la cuenta de usuario o de organización a la cual pertenezca el repositorio y `REPOSITORY` con el nombre del repositorio que contiene tu proyecto. + {% if enterpriseServerVersions contains currentVersion %} + Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2 +Publicar el paquete. + + ```shell + $ mvn deploy + ``` + + +{% data reusables.package_registry.viewing-packages %} + +### Instalar un paquete + +Para instalar un paquete de Apache Maven desde {% data variables.product.prodname_registry %}, edita el *POM. XML* archivo para incluir el paquete como una dependencia. Si deseas instalar paquetes desde más de un repositorio, agrega una etiqueta `repositorio` para cada uno. Para obtener más información acerca del uso de un archivo *pom.xml* en tu proyecto, consulta "[Introducción al POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)"en la documentación de Apache Maven. + +{% data reusables.package_registry.authenticate-step %} +2. Agrega las dependencias del paquete al elemento `dependencias` del archivo *pom.xml* de tu proyecto, reemplazando `com.example:test` con tu paquete. + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. Instala el paquete. + + ```shell + $ mvn install + ``` + +### Further reading + +- "[Configurar Gradle para usar con {% data variables.product.prodname_registry %}](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- "[Eliminar un paquete](/packages/manage-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000000..9ded5c573c4ad --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,284 @@ +--- +title: Configurar Docker para usar con paquetes de GitHub +intro: 'Puedes configurar el cliente Docker para usar {% data variables.product.prodname_registry %} para publicar y recuperar imágenes de docker' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +### Autenticar a {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +Puedes autenticarte en {% data variables.product.prodname_registry %} con Docker utilizando el comando de ingreso `docker`. + +{% if currentVersion == "enterprise-server@2.22" %} + +Antes de que puedas utilizar el registro de Docker en el {% data variables.product.prodname_registry %}, el administrador de sitio de {% data variables.product.product_location %} debe habilitar la compatibilidad de Docker y el aislamiento de subdominios para tu instancia. Para obtener más informacón, consulta la sección "[Administrar GitHub Packages para tu empresa](/enterprise/admin/packages)". + +{% endif %} + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Puedes autenticar a {% data variables.product.prodname_registry %} con Docker usando el comando de inicio de sesión `Docker`. + +Para mantener tus credenciales seguras, te recomendamos que guardes tu token de acceso personal en un archivo local de tu computadora y utilices el marcador `--password-stdin` de Docker, el cual lee tu token desde un archivo local. + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} +{% raw %} + ```shell + $ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Etiqueta la imagen con OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Sube la imagen a {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` +{% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +{% endif %} + +Para utilizar este ejemplo de comando de ingreso, reemplaza `USERNAME` con tu nombre de usuario de {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` con la URL de {% data variables.product.product_location %},{% endif %} y `~/TOKEN.txt` con la ruta de archivo de tu token de acceso personal para {% data variables.product.product_name %}. + +Para obtener más información, consulta la sección "[Inicio de sesión de Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." + +#### Autenticando con el `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar una imagen + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Nota:** Los nombres de imagen deben utilizar letras en minúscula únicamente. + +{% endnote %} + +{% data variables.product.prodname_registry %} admite varias imágenes Docker de primer nivel por repositorio. Un repositorio puede tener cualquier cantidad de etiquetas de imagen. Puedes experimentar un servicio de menor calidad al publicar o instalar imágenes de Docker de más de 10 GB, las capas tienen un límite de 5 GB cada una. Para obtener más información, consulta "[Etiqueta Docker](https://docs.docker.com/engine/reference/commandline/tag/)" en la documentación de Docker. + +{% data reusables.package_registry.viewing-packages %} + +1. Determina el nombre y la ID de la imagen Docker utilizando `imágenes docker`. + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. Con la ID de la imagen Docker, etiqueta la imagen Docker, reemplazando *OWNER* con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio, *REPOSITORY* con el nombre del repositorio que contiene tu proyecto, *IMAGE_NAME* con el nombre del paquete o la imagen y *VERSION* con la versión del paquete en tiempo de construcción. +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* con el nombre de host de {% data variables.product.product_location %},{% endif %} y *VERSION* con la versión del paquete en la hora de creación. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + {% endif %} + ```shell + Puedes publicar una nueva imagen de Docker por primera vez y nombrarla monalisa. + ``` +. + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% endif %} +3. Si aún no has creado una imagen de docker para el paquete, crea la imagen, reemplaza *OWNER* con el nombre de la cuenta de usuario o de organización a la que pertenezca el repositorio, *REPOSITORY* con el nombre del repositorio que contiene tu proyecto, *IMAGE_NAME* con el nombre del paquete o imagen, *VERSION* con la versión y hora de creación del paquete, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* con el nombre de host de {% data variables.product.product_location %},{% endif %} y *PATH* hacia la imagen si no está en el directorio de trabajo actual. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + {% endif %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} + {% endif %} +4. Publicar la imagen en +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + {% endif %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% endif %} + {% note %} + + **Nota:** Debes subir tu imagen usando `IMAGE_NAME: VERSION` y no utilizar `IMAGE_NAME: SHA`. + + {% endnote %} + +#### Ejemplo de publicación de una imagen Docker + +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} + +Puedes publicar la versión 1.0 de la imagen `monalisa` en el repositorio `octocat/octo-app` usando una ID de imagen. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Etiqueta la imagen con OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Sube la imagen a {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +Puedes publicar una nueva imagen de Docker por primera vez y nombrarla `monalisa`. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Construye la imagen con docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Asume que Dockerfile reside en el directorio de trabajo actual (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Sube la imagen a {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Descargar una imagen + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +Puedes utilizar el comando `docker pull` para instalar una imagen de docker desde {% data variables.product.prodname_registry %}, reemplazando *OWNER* con el nombre de la cuenta de usuario o de organización a la cual pertenece el repositorio, *REPOSITORY* con el nombre del repositorio que contiene tu proyecto, *IMAGE_NAME* con el nombre del paquete o imagen,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}, {% endif %} y *TAG_NAME* con la etiqueta de la imagen que quieres instalar. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} +{% endif %} + +{% note %} + +**Nota:** Debes extraer la imagen utilizando `IMAGE_NAME:VERSION` y no así, utilizando `IMAGE_NAME:SHA`. + +{% endnote %} + +### Further reading + +- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000000..3aa43b0c58d87 --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,224 @@ +--- +title: Configurar la CLI `dotnet` para usar con paquetes de GitHub +intro: 'Puedes configurar la interfaz de línea de comando (CLI) `dotnet` para publicar paquetes NuGet en {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto de .NET.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Para autenticarte en {% data variables.product.prodname_registry %} con la interfaz de la línea de comando (CLI) `dotnet`, crea un archivo *nuget.config* en el directorio de tu proyecto especificando {% data variables.product.prodname_registry %} como una fuente en `packageSources` para el cliente de la CLI `Dotnet`. + +Debes reemplazar: +- `USERNAME` (nombre de usuario) por el nombre de tu cuenta de usuario en {% data variables.product.prodname_dotcom %}. +- `TOKEN` por tu token de acceso personal. +- `OWNER` con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %} +- `HOSTNAME` con el nombre de host para tu instancia de {% data variables.product.prodname_ghe_server %}. + +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +```xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://github.com/octo-org/octo-cats-and-dogs + + + +``` +{% endif %} + +#### Autenticando con el `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar un paquete + +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. Crear un proyecto nuevo. + ```shell + dotnet new console --name OctocatApp + ``` +2. Empaquetar el proyecto. + ```shell + dotnet pack--lanzamiento de configuración + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` + +{% data reusables.package_registry.viewing-packages %} + +{% endif %} + +#### Publishing a package using a *nuget.config* file + +Al publicar, debes usar el mismo valor para `OWNER` en tu archivo *csproj* que usas en tu archivo de autenticación *nuget.config*. Especifica o incrementa el número de versión en tu archivo *.csproj* y luego usa el comando `dotnet pack` para crear un archivo *.nuspec* para esa versión. Para obtener más información sobre cómo crear tu paquete, consulta la sección "[Crear y publicar un paquete](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" en la documentación de Microsoft. + +{% data reusables.package_registry.authenticate-step %} +2. Crear un proyecto nuevo. + ```shell + dotnet new console --name OctocatApp + ``` +3. Agrega la información específica de tu proyecto al archivo de tu proyecto, que finaliza en *.csproj*. Debes reemplazar: + - `OWNER` por el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto. + - `REPOSITORY` por el nombre del repositorio que contiene el paquete que deseas publicar. + - `1.0.0` con el número de versión del paquete.{% if enterpriseServerVersions contains currentVersion %} + - `HOSTNAME` con el nombre de host para tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. Empaquetar el proyecto. + ```shell + dotnet pack--lanzamiento de configuración + ``` + +5. Publicar el paquete utilizando la `clave` que especificaste en el archivo *nuget.config*. + ```shell + dotnet nuget subir "bin/Release/OctocatApp. 1.0.0. nupkg"--Source "GitHub" + ``` + +{% data reusables.package_registry.viewing-packages %} + +### Publicar varios paquetes en el mismo repositorio + +Para publicar varios paquetes en el mismo repositorio, puedes incluir la misma URL del repositorio de {% data variables.product.prodname_dotcom %} en los campos `RepositoryURL` en todos los archivos del proyecto *.csproj*. {% data variables.product.prodname_dotcom %} coincide con el repositorio en base a ese campo. + +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### Instalar un paquete + +El uso de paquetes desde {% data variables.product.prodname_dotcom %} en tu proyecto es similar al uso de paquetes desde *nuget.org*. Agrega las dependencias de tu paquete a tu archivo *.csproj*, especificando el nombre del paquete y la versión. Para obtener más información sobre cómo utilizar un archivo *.csproj* en tu proyecto, consulta "[Trabajar con paquetes NuGet](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)"en la documentación de Microsoft. + +{% data reusables.package_registry.authenticate-step %} + +2. Para usar un paquete, agrega `ItemGroup` y configura el campo `PackageReference` en el archivo de proyecto *.csproj*, reemplaza el paquete `OctokittenApp` por la dependencia de tu paquete y `1.0.0` por la versión que deseas usar: + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. Instalar los paquetes con el comando `restore (restaurar)`. + ```shell + restaurar dotnet + ``` + +### Further reading + +- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000000..07e25e9988f6b --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: Configurar Gradle para usar con paquetes de GitHub +intro: 'Puedes configurar Gradle para publicar paquetes para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Java.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Puedes autenticar a {% data variables.product.prodname_registry %} con Gradle usando ya sea Gradle Groovy o Kotlin DSL editando tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL) para incluir tu token de acceso personal. También puedes configurar Gradle Groovy y Kotlin DSL para que reconozcan un paquete único o múltiples paquetes en un repositorio. + +{% if enterpriseServerVersions contains currentVersion %} +Reemplaza *REGISTRY-URL* con la URL para el registro Maven de tu instancia. Si tu instancia tiene habilitado el aislamiento de subdominios, utiliza `maven.HOSTNAME`. Si tu instancia tiene inhabilitado el aislamiento de subdominios, utiliza `HOSTNAME/_registry/maven`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre del host de tu +instancia de {% data variables.product.prodname_ghe_server %}. +{% endif %} + +Reemplaza *USERNAME* con tu nombre de usuario {% data variables.product.prodname_dotcom %}, *TOKEN* con tu token de acceso personal, *REPOSITORY* con el nombre del repositorio que contiene el paquete que deseas publicar y *OWNER* con el nombre de la cuenta de usuario o de organización en {% data variables.product.prodname_dotcom %} que posee el repositorio. Dado que las letras mayúsculas no son compatibles, debes usar minúsculas para el propietario del repositorio si el nombre de usuario o el nombre de la organización de {% data variables.product.prodname_dotcom %} contiene letras mayúsculas. + +{% note %} + +**Nota:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Para obtener un ejemplo, consulta "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." + +{% endnote %} + +##### Ejemplo de uso de Gradle Groovy para un paquete único en un repositorio + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### Ejemplo usando Gradle Groovy para múltiples paquetes en el mismo repositorio + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### Ejemplo de uso de Kotlin DSL para un paquete único en el mismo repositorio + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### Ejemplo de uso de Kotlin DSL para múltiples paquetes en el mismo repositorio + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### Autenticarse con el `GITHUB_TOKEN` + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + Para obtener más información acerca del uso de `GITHUB_TOKEN` con Maven, consulta "[Publicar paquetes Java con Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)". + + ### Publicar un paquete + + {% data reusables.package_registry.default-name %} Por ejemplo, {% data variables.product.prodname_dotcom %} publicará un paquete denominado `com.example.test` en el repositorio `OWNER/test` {% data variables.product.prodname_registry %}. + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. Después de crear tu paquete, puedes publicar el paquete. + + ```shell + $ gradle publish + ``` + +### Instalar un paquete + +Puedes instalar un paquete agregando el paquete como una dependencia a tu proyecto. Para obtener más información, consulta "[Declarar dependencias](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" en la documentación de Gradle. + +{% data reusables.package_registry.authenticate-step %} +2. Agrega las dependencias del paquete a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL). + + Ejemplo utilizando Gradle Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Ejemplo de uso de Kotlin DSL: + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. Agrega el complemento Maven a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL). + + Ejemplo utilizando Gradle Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Ejemplo de uso de Kotlin DSL: + ```shell + plugins { + `maven` + } + ``` + + 3. Instala el paquete. + + ```shell + $ gradle install + ``` + +### Further reading + +- "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000000..9adea8a612be4 --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,220 @@ +--- +title: Configurar npm para usar con Paquetes de GitHub +intro: 'Puedes configurar npm para publicar paquetes en {% data variables.product.prodname_registry %} y para usar los paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto npm.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Limits for published npm versions + +If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage. + +To reduce the number of versions you have published for your npm package, consider deleting package versions. Para obtener más información, consulta "[Eliminar un paquete](/packages/manage-packages/deleting-a-package)". + +In the future, {% data variables.product.company_short %} will enforce a hard limit on publishing more than 1,000 versions of an npm package. When we start enforcing the 1,000 versions limit for each npm package hosted on {% data variables.product.prodname_registry %}, we will offer more guidance on how to manage your package versions. + +{% endif %} + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Puedes autenticarte en {% data variables.product.prodname_registry %} con npm al editar tu archivo *~/.npmrc* por usuario para incluir tu token de acceso personal o al iniciar sesión en npm en la línea de comando por medio tu nombre de usuario y token de acceso personal. + +Para autenticarte agregando tu token de acceso personal a tu archivo *~/.npmrc*, edita el archivo *~/.npmrc* para que tu proyecto incluya la siguiente línea, reemplazando {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %} y {% endif %}*TOKEN* con tu token de acceso personal. Crea un nuevo archivo *~/.npmrc* si no existe uno. + +{% if enterpriseServerVersions contains currentVersion %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +```shell +$ npm login --registry=https://npm.pkg.github.com +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +Para autenticarte al iniciar sesión en npm, usa el comando `npm login`, reemplaza *USERNAME* por tu nombre de usuario de {% data variables.product.prodname_dotcom %}, *TOKEN* por tu token de acceso personal y *PUBLIC-EMAIL-ADDRESS* por tu dirección de correo electrónico. + +Si el {% data variables.product.prodname_registry %} no es tu registro de paquetes predeterminado para utilizar npm y quieres utilizar el comando `npm audit`, te recomendamos que utilices el marcador `--scope` con el propietario del paquete cuando te autentiques en {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### Autenticando con el `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar un paquete + +{% note %} + +**Nota:** Los nombres y alcances de los paquetes deben escribirs exclusivamente en minúscula. + +{% endnote %} + +De forma predeterminada, {% data variables.product.prodname_registry %} publica un paquete en el repositorio de {% data variables.product.prodname_dotcom %} que especifiques en el campo nombre del archivo *package.json*. Por ejemplo, si publicas un paquete denominado `@my-org/test` en el repositorio de `my-org/test` {% data variables.product.prodname_dotcom %}. Puedes agregar un resumen para la página de descripción del paquete al incluir un archivo *README.md* en el directorio de tu paquete. Para obtener más información, consulta "[Trabajar con package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" y "[Cómo crear módulos Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" en la documentación de npm. + +Puedes publicar varios paquetes en el mismo repositorio de {% data variables.product.prodname_dotcom %} al incluir un campo `URL` en el archivo *package.json*. Para obtener más información, consulta "[Publicar varios paquetes en el mismo repositorio](#publishing-multiple-packages-to-the-same-repository)". + +Puedes configurar la asignación de alcance de tu proyecto por medio de un archivo *.npmrc* local en el proyecto o mediante la opción `publishConfig` en *package.json*. {% data variables.product.prodname_registry %} solo admite paquetes npm con alcance definido. Los paquetes con alcance definido tienen nombres con el formato de `@owner/name`. Además, siempre comienzan con un símbolo `@`. Es posible que tengas que actualizar el nombre en tu *package.json* para usar el nombre de alcance definido. Por ejemplo, `"name": "@codertocat/hello-world-npm"`. + +{% data reusables.package_registry.viewing-packages %} + +#### Publicar un paquete por medio de un archivo *.npmrc* local + +Puedes usar un archivo *.npmrc* para configurar la asignación del alcance de tu proyecto. En el archivo *.npmrc*, usa la URL y el propietario de la cuenta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} sepa dónde enrutar las solicitudes del paquete. Usar un archivo *.npmrc* impide que otros programadores publiquen accidentalmente el paquete en npmjs.org en lugar de {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Verifica el nombre de tu paquete en el *package.json* de tu proyecto. El campo `name (nombre)` debe contener el alcance y el nombre del paquete. Por ejemplo, si tu paquete se llama "prueba", y estás publicando hacia la organización +"My Org" de {% data variables.product.prodname_dotcom %}, entonces el campo de `name` en tu *package.json* debe ser `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### Publicar un paquete por medio de `publishConfig` en el archivo *package.json* + +Puedes usar el elemento `publishConfig` en el archivo *package.json* para especificar el registro en el que deseas que se publique el paquete. Para obtener más información, consulta "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" en la documentación de npm. + +1. Edita el archivo *package.json* de tu paquete e incluye una entrada de `publishConfig`. + {% if enterpriseServerVersions contains currentVersion %} + Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### Publicar varios paquetes en el mismo repositorio + +Para publicar varios paquetes en el mismo repositorio, puedes incluir la URL del repositorio de {% data variables.product.prodname_dotcom %} en el campo `repository (repositorio)` del archivo *package.json* para cada paquete. + +Para asegurarte de que la URL del repositorio sea correcta, reemplaza REPOSITORY por el nombre del repositorio que contiene el paquete que deseas publicar y OWNER por el nombre de la cuenta de usuario o de organización en {% data variables.product.prodname_dotcom %} que posee el repositorio. + +{% data variables.product.prodname_registry %} coincidirá con el repositorio en base a la URL, en lugar de basarse en el nombre del paquete. + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### Instalar un paquete + +Puedes instalar paquetes desde {% data variables.product.prodname_registry %} al agregar los paquetes como dependencias en el archivo *package.json* para tu proyecto. Para obtener más información sobre el uso de un *package.json* en tu proyecto, consulta "[Trabajar con package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" en la documentación de npm. + +Por defecto, puedes agregar paquetes de una organización. Para obtener más información, consulta la sección "[Instalar paquetes de otras organizaciones](#installing-packages-from-other-organizations)". + +También debes agregar el archivo *.npmrc* a tu proyecto por lo que todas las solicitudes de instalación de paquetes pasarán por {% data variables.product.prodname_registry %}. Cuando enrutas todas las solicitudes de paquete a través de {% data variables.product.prodname_registry %}, puedes usar paquetes con alcance definido y sin alcance definido de *npmjs.com*. Para obtener más información, consulta "[npm-scope](https://docs.npmjs.com/misc/scope)" en la documentación de npm. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configura *package.json* en tu proyecto para usar el paquete que estás instalando. Para agregar las dependencias de tu paquete al archivo *package.json* para {% data variables.product.prodname_registry %}, especifica el nombre del paquete de alcance completo, como `@my-org/server`. Para paquetes de *npmjs.com*, especifica el nombre completo, como `@babel/core` o `@lodash`. Por ejemplo, el archivo *package.json* a continuación utiliza el paquete `@octo-org/octo-app` como una dependencia. + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. Instala el paquete. + + ```shell + $ npm install + ``` + +#### Instalar paquetes de otras organizaciones + +Por defecto, solo puedes usar paquetes de {% data variables.product.prodname_registry %} de una organización. Si te gustaría enrutar las solicitudes de paquetes a varias organizaciones y usuarios, puedes agregar líneas adicionales a tu archivo *.npmrc* reemplazando {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %} y {% endif %}*OWNER* con el nombre de la cuenta de usuario o de organización a la cual pertenece el repositorio que contiene tu proyecto. + +{% if enterpriseServerVersions contains currentVersion %} +Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio: + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + +### Further reading + +- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000000..5d3d783021355 --- /dev/null +++ b/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,149 @@ +--- +title: Configurar RubyGems para usar con paquetes de GitHub +intro: 'Puedes configurar RubyGems para publicar un paquete para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Ruby con Bundler.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. + +### Prerrequisitos + +- Debes tener RubyGems 2.4.1 o superiores. Para encontrar tu versión de RubyGems: + + ```shell + $ gem --version + ``` + + - Debes tener Bundler 1.6.4 o superiores. Para encontrar tu versión Bundler: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Instala keycutter para administrar múltiples credenciales. Para instalar keycutter: + ```shell + $ gem install keycutter + ``` + +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Autenticarte con un token de acceso personal + +{% data reusables.package_registry.required-scopes %} + +Puedes autenticar a {% data variables.product.prodname_registry %} con RubyGems editando el archivo *~/.gem/credentials* para publicar gemas, editar el archivo *~/.gemrc* para instalar una gema única o usar Bundler para rastrear e instalar una o más gemas. + +Para publicar gemas nuevas, debes autenticarte para {% data variables.product.prodname_registry %} con RubyGems editando tu archivo *~/.gem/credentials* para incluir tu token de acceso personal. Crear un nuevo archivo *~/.gem/credentials* si este archivo no existe. + +Por ejemplo, crearías o editarías un *~/.gem/credentials* para incluir lo siguiente, reemplazando *TOKEN* con tu token de acceso personal. + +```shell +--- +:github: Bearer TOKEN +``` + +Para instalar gemas, necesitas autenticarte en el {% data variables.product.prodname_registry %} mediante la edición del archivo *~/.gemrc* para que tu proyecto incluya `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Debes reemplazar: + - `USERNAME` con tu nombre de usuario {% data variables.product.prodname_dotcom %}. + - `TOKEN` por tu token de acceso personal. + - `OWNER` con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %} + - `REGISTRY-URL` con la URL para el registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}. +{% endif %} + +Si no tienes un archivo *~/.gemrc*, crea un nuevo archivo *~/.gemrc* usando este ejemplo. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +Para autenticar con Bundler, configura Bundler para que use tu token de acceso personal, reemplazando *USERNAME* con tu nombre de usuario de {% data variables.product.prodname_dotcom %}, *TOKEN* con tu token de acceso personal y *OWNER* con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} + +```shell +$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN +``` + +#### Autenticando con el `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar un paquete + +{% data reusables.package_registry.default-name %} Por ejemplo, cuando publicas `octo-gem` a la organización `octo-org`, {% data variables.product.prodname_registry %} publica la gema en el repositorio `octo-org/octo-gem`. Para obtener más información sobre la creación de tu gema, consulta "[Crear tu propia gema](http://guides.rubygems.org/make-your-own-gem/)" en la documentación de RubyGems. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Construye el paquete desde el *gemspec* para crear el paquete *.gem*. + ```shell + gem build OCTO-GEM.gemspec + ``` +3. Publica un paquete en el {% data variables.product.prodname_registry %}, reemplazando `OWNER` con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto y `OCTO-GEM` con el nombre de tu paquete de gemas.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### Publicar varios paquetes en el mismo repositorio + +Para publicar múltiples gemas en el mismo repositorio, puedes incluir la URL al repositorio {% data variables.product.prodname_dotcom %} en el campo `github_repo` en `gem.metadata`. Si incluyes este campo, {% data variables.product.prodname_dotcom %} empatará el repositorio con base en este valor en vez de utilizar el nombre de la gema.{% if enterpriseServerVersions contains currentVersion %} Reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} + +``` +gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } +``` + +### Instalar un paquete + +Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual que usas gemas de *rubygems.org*. Debes autenticar para {% data variables.product.prodname_registry %} al agregar tu usuario u organización {% data variables.product.prodname_dotcom %} como fuente en el archivo *~/.gemrc* o mediante el uso de Bundler y la edición de *Gemfile*. + +{% data reusables.package_registry.authenticate-step %} +2. Para Bundler, agrega tu usuario u organización {% data variables.product.prodname_dotcom %} como fuente en tu *Gemfile* para extraer gemas de esta nueva fuente. Por ejemplo, puedes agregar un bloque nuevo de `source` al *Gemfile* que utiliza el {% data variables.product.prodname_registry %} únicamente para los paquetes que especifiques, reemplzando *GEM NAME* con el paquete que quieres instalar desde el {% data variables.product.prodname_registry %} y *OWNER* con el usuario u organización al que pertenece el repositorio que contienen la gema que quieres instalar.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. Para las versiones de Bundler anteriores a 1.7.0, debes agregar una nueva `fuente` global. Para obtener más información acerca del uso de Bundler, consulta la [documentación bundler.io](http://bundler.io/v1.5/gemfile.html). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Instala el paquete: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### Further reading + +- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/es-ES/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000000..e81b447d5928e --- /dev/null +++ b/translations/es-ES/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: Conectar un repositorio a una imagen de contenedor +intro: 'Puedes vincular un repositorio con una imagen de contenedor tanto localmente como en {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +Cuando vinculas una imagen de contenedor con un repositorio, la página de llegada del paquete mostrará información y enlaces del repositorio, tales como el README. + +Para conectar un repositorio y una imagen de contenedor en {% data variables.product.prodname_dotcom %}, estos deben compartir el mismo propietario en {% data variables.product.prodname_dotcom %}. Por ejemplo, tanto `my_repo` como `hello_docker` pertenecen al usuario `monalisa`: +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### Conectar un repositorio a una imagen de contenedor que pertenezca a un usuario en {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Conectar un repositorio a una imagen de contenedor que pertenezca a una organización en {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Conectar un repositorio a una imagen de contenedor en la línea de comandos + +1. En tu Dockerfile, agrega esta línea, reemplazando a `OWNER` y `REPO` con tu información: + + ```shell + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO + ``` + Por ejemplo, si eres el usuario `monalisa` y eres propietario de `my-repo`, agregarías esta línea a tu Dockerfile: + ```shell + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo + ``` + Para obtener más información, consulta "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" en la documentación oficial de Docker, y "[Llaves de Anotación Predefinidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" en el repositorio `opencontainers/image-spec`. + +2. Crea tu imagen de contenedor. Este ejemplo crea una imagen del Dockerfile en el directorio actual y asigna el nombre de imagen `hello_docker`. + + ```shell + $ docker build -t hello_docker . + ``` +3. Opcionalmente, revisa los detalles para la imagen de Docker que quieres etiquetar. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Etiqueta tu imagen de Docker con el nombre que hayas elegido para la imagen y con el destino del host. + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + Por ejemplo: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. Si aún no te autenticas en el + +{% data variables.product.prodname_github_container_registry %}. Para obtener más información, consulta la sección "[Autenticarse en el Registro de Contenedores de GitHub](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)". + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. Sube tu imagen de contenedor a {% data variables.product.prodname_github_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + Por ejemplo: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md b/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000000..af43d1e1e7890 --- /dev/null +++ b/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Guías de contenedor para GitHub Packages +shortTitle: Guías de contenedor para GitHub Packages +intro: 'Puedes publicar y recuperar las imágenes de Docker utilizando {% data variables.product.prodname_registry %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/packages/guides/deleting-a-container-image.md b/translations/es-ES/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000000..f71cfa7e82ffd --- /dev/null +++ b/translations/es-ES/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,53 @@ +--- +title: Borrar una imagen de contenedor +intro: 'You can delete a specific version or all versions of a private or public container image on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Acerca de la eliminación de paquetes + +Puedes eliminar una imagen de contenedor completa o una versión específica en {% data variables.product.prodname_dotcom %}. Para borrar una imagen de contenedor, debes utilizar la IU. Por el momento no se puede utilizar GraphQLpara borrar una imagen de contenedor. + +Para borrar una imagen de contenedor debes tener permisos administrativos en la misma. + +Cuando borres paquetes públicos, toma en cuenta que podrías dañar proyetos que dependen de ellos. + +### Borrar una versión de una imagen de contenedor que pertenezca a un usuario en {% data variables.product.prodname_dotcom %} + +To only delete specific versions of a container image, you can use these steps. To delete an entire package, see "[Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-a-user-owned-container-image-on-github)." + +{% data reusables.package_registry.package-settings-from-user-level %} +5. A la izquierda, da clic en **Administrar versiones**. +6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) +5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**. ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png) +6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) + +### Borrar una versión de una imagen de contenedor que pertenezca a una organización en {% data variables.product.prodname_dotcom %} + +To only delete specific versions of a container image that you have admin , you can use these steps. To delete an entire package, see "[Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-an-organization-owned-container-image-on-github)." + +{% data reusables.package_registry.package-settings-from-org-level %} +5. A la izquierda, da clic en **Administrar versiones**. +6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) +5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**. ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png) +6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) + +### Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} +5. On the left, click **Options**. !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png) +6. Under "Danger zone", click **Delete this package**. ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**. ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png) + +### Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} +5. On the left, click **Options**. !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png) +6. Under "Danger zone", click **Delete this package**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-container-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-container-package-deletion.png) diff --git a/translations/es-ES/content/packages/guides/enabling-improved-container-support.md b/translations/es-ES/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000000..c10c78c8359c8 --- /dev/null +++ b/translations/es-ES/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Habilitar el soporte de contenedores mejorado +intro: 'Para utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitarlo para tu cuenta de usuario o de organización.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** El {% data variables.product.prodname_github_container_registry %} se encuentra actualmente en su fase de beta público y está sujeto a cambios. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". + +{% endnote %} + +### Habilitar el {% data variables.product.prodname_github_container_registry %} para tu cuenta personal + +Una vez que habilites el {% data variables.product.prodname_github_container_registry %} para tu cuenta de usuario personal, puedes publicar contenedores en el {% data variables.product.prodname_github_container_registry %}, los cuales le pertenezcan a dicha cuenta. + +Para utilizar el {% data variables.product.prodname_github_container_registry %} dentro de una organización, el propietario de ésta debe habilitar la característica para los miembros de la misma. + +{% data reusables.feature-preview.feature-preview-setting %} +2. A la izquierda, selecciona "mejorar el soporte de contenedores" y luego da clic en **Habilitar**. ![Soporte de contenedores mejorado](/assets/images/help/settings/improved-container-support.png) + +### Habilitar el {% data variables.product.prodname_github_container_registry %} para tu cuenta de organización + +Antes de que los miembros o propietarios de una organización puedan publicar imágenes de contenedores en el {% data variables.product.prodname_github_container_registry %}, un propietario de la organización debe habilitar la vista previa de características para la misma. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. A la izquierda, da clic en **Paquetes**. +5. Debajo de "Soporte mejorado para contenedores", selecciona "Habilitar el soporte mejorado para contenedores" y da clic en **Guardar**. ![Opción para habilitar el soporte del registro de contenedores y botón de guardar](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Debajo de "Creación de contenedores", selecciona si quieres habilitar la creación de imágenes de contenedor privadas o públicas. + - Para habilitar a los miembros de la organización para que creen imágenes de contenedor, da clic en **Públicas**. + - Para habilitar a los miembros de la organización para que creen imágenes de contenedor que solo sean visibles para otros miembros de la organización, da clic en **Privadas**. Puedes personalizar aún más la visibilidad de las imagenes de contenedor privadas. Para obtener más información, consulta la sección "[Configurar el control de accesos y la visibilidad para las imagenes de contenedor](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)". + + ![Opciones para habilitar los paquetes públicos o privados ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/es-ES/content/packages/guides/index.md b/translations/es-ES/content/packages/guides/index.md new file mode 100644 index 0000000000000..d433994adb27b --- /dev/null +++ b/translations/es-ES/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: Guías +shortTitle: Guías +intro: 'Estas guías te ayudan a configurar las {% data variables.product.prodname_actions %} en tu cliente de paquetes para trabajar con {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Índice + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/es-ES/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/es-ES/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000000..deb4ccdc26c6f --- /dev/null +++ b/translations/es-ES/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Migrarse al Registro de Contenedores de GitHub para las imágenes de Docker +intro: 'Si utilizaste el registro de Docker de GitHub Packages para almacenar imagenes de Docker, puedes migrarte al nuevo {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### Diferencias clave entre el {% data variables.product.prodname_github_container_registry %} y el registro de paquetes de Docker + +{% data reusables.package_registry.container-registry-beta %} + +El {% data variables.product.prodname_github_container_registry %} sustituye el registro de Docker para Paquetes y está optimizado para ser compatible con algunas de las necesidades específicas de los contenedores. + +{% data reusables.package_registry.container-registry-feature-highlights %} + +Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". + +### Cambios en la facturación + +{% data reusables.package_registry.billing-for-container-registry %} + +### Cambios de dominio + +El dominio para el {% data variables.product.prodname_container_registry %} es `ghcr.io`. + +| Registro | URL de Ejemplo | +| ---------------------------------------------------------------------- | --------------------------------------------------- | +| Registro de Docker para {% data variables.product.prodname_registry %} | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### Autenticarse con el registro de contenedores + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +Necesitarás autenticarte en el {% data variables.product.prodname_container_registry %} con la URL base `ghcr.io`. Te recomendamos crear un token de acceso nuevo para utilizar el {% data variables.product.prodname_container_registry %}. + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Migrar la imagen de Docker utilizando el Docker CLI + +Para mover las imágenes de Docker que hospedes en el registro de Docker para {% data variables.product.prodname_registry %} debes republicar las imágenes en {% data variables.product.prodname_container_registry %}. Te recomendamos volver a publicar tus imágenes existentes de Docker utilizando la línea de comandos en tu máquina local. + +1. Ingresa en el registro de Docker utilizando un PAT temporal con un alcance mínimo de `read:packages`. Este PAT solo se utilizará para ingresar al registro de Docker para extraer imágenes y puede borrarse después. + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. Extrae la imagen que quieres migrar reemplazando OWNER con el nombre de la cuenta de usuario u organización a la que pertenece el repositorio, REPOSITORY con el nombre del repositorio que contiene tu proyecto, IMAGE_NAME con el nombre del paquete o imagen, y VERSION con la etiqueta para la imagen que quieres instalar. Por ejemplo, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` extraerá la última etiqueta de la imagen `octoshift/octoshift` en la organización octo-org. + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. Vuelve a etiquetar la imagen con el dominio nuevo y con un nombre de imagen nuevo. Para obtener más información, consulta "[Etiqueta Docker](https://docs.docker.com/engine/reference/commandline/tag/)" en la documentación de Docker. Utiliza la misma URL que utilizaste en el paso anterior para la SOURCE URL. Reemplaza el TARGET_OWNER con el usuario u organización al cual estás migrando la imagen de contenedor y reemplaza TARGET_IMAGE_NAME con el nombre de imagen para {% data variables.product.prodname_container_registry %} nuevo. + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. Ingresa al nuevo + +{% data variables.product.prodname_container_registry %}. Te recomendamos crear un PAT limitado nuevo con los alcances de `read:packages` y `write:packages`, dado que ya no necesitas el alcance `repo` y tu PAT anterior podría no tener el alcance `write:packages`. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. Sube tu imagen reetiquetada al {% data variables.product.prodname_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %} + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +Si tienes un flujo de trabajo de {% data variables.product.prodname_actions %} que utiliza una imagen de Docker desde el registro de Docker para {% data variables.product.prodname_registry %}, tal vez quieras actualizarlo al {% data variables.product.prodname_container_registry %} para permitir el acceso anónimo para las imágenes de contenedor públicas, permisos de acceso más específicos, y para tener mejor compatibilidad de almacenamiento y ancho de banda para los contenedores. + +1. Migra tus imágenes de Docker al nuevo {% data variables.product.prodname_container_registry %} en `ghcr.io`. Para encontrar un ejemplo, consulta la sección "[Migrar una imagen de Docker utilizando el CLI de Docker](#migrating-a-docker-image-using-the-docker-cli)". + +2. En tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %}, actualiza la url del paquete de `https://docker.pkg.github.com` a `ghcr.io`. + +3. Agrega tu token de acceso personal (PAT) para autenticación en el {% data variables.product.prodname_container_registry %} como un secreto de GitHub Actions. El {% data variables.product.prodname_github_container_registry %} no es compatible con el uso de `GITHUB_TOKEN` para tu PAT, así que debes de utilizar una variable personalizada diferente, tale como `CR_PAT`. Para obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". + +4. En tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %}, actualiza el PAT de autenticación reemplazando tu PAT del registro de Docker ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) con una variable nueva para tu PAT del {% data variables.product.prodname_container_registry %}, tal como {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. + +#### Ejemplo de un flujo de trabajo actualizado + +Si parte de tu flujo de trabajo accedió a una imagen de Docker que se hospeda en el registro de Docker de esta forma: + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +Entonces necesitarás actualizar tu flujo de trabajo con la URL de {% data variables.product.prodname_container_registry %} y PAT nuevos de esta forma: + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md b/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000000..bff856b307a01 --- /dev/null +++ b/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Las guías de cliente de paquetes para GitHub Packages +shortTitle: Las guías de cliente de paquetes para GitHub Packages +intro: 'Puedes publicar y recuperar imágenes de cliente de paquetes utilizando {% data variables.product.prodname_registry %}.' +mapTopic: verdadero +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/es-ES/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/es-ES/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000000..42acfcec637b7 --- /dev/null +++ b/translations/es-ES/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Subir y extraer imágenes de Docker +intro: 'Puedes almacenar y administrar imágenes de Docker en {% data variables.product.prodname_github_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +Para cargar y extraer imágenes de contenedor que pertenezcan a una organización, un administrador de dicha organización debe habilitar el {% data variables.product.prodname_github_container_registry %} para la misma. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +### Autenticarte en {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Subir imágenes de contenedor + +Este ejemplo sube la última versión de `IMAGE-NAME`. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +Este ejemplo sube la versión `2.5` de la imagen. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada. Para cambiar la visibilidad o para configurar los permisos de acceso, consulta la sección "[Configurar el control de accesos y la visibilidad para las imágenes de contenedor](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)". + +### Extraer imágenes de contenedor + +#### Extraer por resúmen + +Para garantizar que siempre utilices la misma imagen, puedes especificar la versión exacta de la imagen de contenedor que quieres extraer de acuerdo con su valor de SHA de `digest`. + +1. Para encontrar el valor de SHA de resúmen, utiliza `docker inspect` o `docker pull` y copia el valor de SHA después de `Digest:` + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. Elimina la imagen localmente de acuerdo a tus necesidades. + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. Extrae la imagen de contenedor con `@YOUR_SHA_VALUE` después del nombre de dicha imagen. + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### Extraer por nombre + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### Extraer por nombre y versión + +Ejemplo de CLI de Docker que muestra una imagen que se extrae por su nombre y por la etiqueta de la versión `1.14.1`: + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### Extraer por nombre y última versión + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### Crear imagenes de contenedor + +Este ejemplo crea la imagen `hello_docker`: + ```shell + $ docker build -t hello_docker . + ``` + +### Etiquetar las imágenes de contenedor + +1. Encuentra la ID para la imagen de Docker que quieres etiquetar. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. Etiqueta tu imagen de Docker utilizando la ID ed imagen y el nombre que quieras poner a la misma, así como el destino en donde se hospedará ésta. + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` diff --git a/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md b/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md new file mode 100644 index 0000000000000..a2c07cb78dde6 --- /dev/null +++ b/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,317 @@ +--- +title: Usar GitHub Packages con GitHub Actions +intro: 'Puedes configurar un flujo de trabajo en {% data variables.product.prodname_actions %} para publicar o instalar automáticamente un paquete desde {% data variables.product.prodname_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Acerca de {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %} + +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." + +Puedes ampliar las capacidades de CI y CD de tu repositorio publicando o instalando paquetes como parte de tu flujo de trabajo. + +{% if currentVersion == "free-pro-team@latest" %} +#### Autenticarte en {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.container-registry-beta %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +Para ver un ejemplo de autenticación, consulta la sección "[Autenticarse con el {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)". + +{% endif %} + +#### Autenticarse en los registros de paquetes en {% data variables.product.prodname_dotcom %} + +{% if currentVersion == "free-pro-team@latest" %}Si quieres que tu flujo de trabajo se autentique en {% data variables.product.prodname_registry %} para acceder a un registro de paquetes diferente al {% data variables.product.prodname_container_registry %} en {% data variables.product.product_name %}, entonces{% else %}Para autenticarse en los registros de paquetes de {% data variables.product.product_name %},{% endif %} te recomendamos utilizar el `GITHUB_TOKEN` que {% data variables.product.product_name %} crea automáticamente para tu repositorio cuando habilitas las {% data variables.product.prodname_actions %} en vez de un token de acceso personal para autenticación. El `GITHUB_TOKEN` tiene ámbitos `read:packages` y `write:packages` en el repositorio actual. Para las bifurcaciones, el token también tiene el ámbito `read:packages` para el repositorio padre. + +Puedes hacer referencia al `GITHUB_TOKEN` en tu archivo de flujo de trabajo mediante el contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." + +### Publicar un paquete mediante una acción + +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.actions-configuration %} + +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
+ +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
+ +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
+ +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
+ +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
+ +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
+ +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
+ +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
+ +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
+ +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
+ +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + +### Instalar un paquete mediante una acción + +Puedes instalar paquetes como parte de tu flujo de CI mediante {% data variables.product.prodname_actions %}. Por ejemplo, podrías configurar un flujo de trabajo para que cada vez que un programador suba código a una solicitud de extracción, el flujo de trabajo resuelva las dependencias al descargar e instalar paquetes alojados por el {% data variables.product.prodname_registry %}. Luego, el flujo de trabajo puede ejecutar pruebas de CI que requieran las dependencias. + +El instalar paquetes que hospeda el {% data variables.product.prodname_registry %} a través de las {% data variables.product.prodname_actions %} requiere una configuración mínima o autenticación adicional cuando utilizas un `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} También, la transferencia de datos es gratuita cuando una acción instala un paquete. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". + +{% if currentVersion == "free-pro-team@latest" %} +`GITHUB_TOKEN` no puede instalar paquetes desde ningún repositorio privado además del repositorio donde se ejecuta la acción. Actualmente, no puedes utilizar `GITHUB_TOKEN` para autenticarte en el +{% data variables.product.prodname_github_container_registry %}. +{% endif %} + +{% data reusables.package_registry.actions-configuration %} diff --git a/translations/es-ES/content/packages/index.md b/translations/es-ES/content/packages/index.md new file mode 100644 index 0000000000000..552e59ec0be5c --- /dev/null +++ b/translations/es-ES/content/packages/index.md @@ -0,0 +1,47 @@ +--- +title: Documentación de GitHub Packages +shortTitle: Registro del paquete de GitHub +intro: 'Aprende a publicar y consumir paquetes de forma segura, almacena tus paquetes junto con tu código y comparte tus paquetes de forma privada con tu equipo o de manera pública con la comunidad de código abierto. También puedes automatizar tus paquetes con {% data variables.product.prodname_actions %}.' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages +featuredLinks: + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package + popular: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Los nombres de contenedor ghcr.io redireccionan a la página de dicho contenedor + date: '2020-12-14' + href: https://github.blog/changelog/2020-12-14-ghcr-io-container-names-redirect-to-the-container-page/ + - + title: Filtrar para contenedores etiquetados y no etiquetados + date: '2020-12-14' + href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ + - + title: El soporte para los contenedores de los paquetes es un beta al que puedes decidir ingresar + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support +redirect_from: + - /github/managing-packages-with-github-packages + - /categories/managing-packages-with-github-package-registry + - /github/managing-packages-with-github-package-registry +layout: product-landing +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + + + + + diff --git a/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md new file mode 100644 index 0000000000000..4aad622c8d793 --- /dev/null +++ b/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,173 @@ +--- +title: Acerca de GitHub Packages +intro: '{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquete de software que te permite alojar tus paquetes de software de forma privada o pública y usar paquetes como dependencias en tus proyectos.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Acerca de {% data variables.product.prodname_registry %} + +{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquetes, totalmente integrado con {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina tu código fuente y tus paquetes en un solo lugar para proporcionar facturación y gestión de permisos integrada, para que puedas centralizar tu desarrollo de software en {% data variables.product.product_name %}. + +Puedes integrar {% data variables.product.prodname_registry %} con las API de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} y webhooks para crear un flujo de trabajo de DevOps de extremo a extremo que incluya tu código, CI y soluciones de implementación. + +Puedes alojar múltiples paquetes en un repositorio y ver más información acerca de cada paquete al ver el README del paquete, las estadísticas de descarga, el historial de la versión y mucho más. + + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)". + +{% data reusables.package_registry.container-registry-beta %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### Visualizar paquetes + +Puedes revisar el README del paquete, algunos metadatos como los detalles de la licencia, las estadísticas de descarga, el historial de versiones y más en {% data variables.product.product_name %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/manage-packages/viewing-packages)". + +#### Acerca de los permisos y la visibilidad de los paquetes + +| | Registros de los paquetes | +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Ubicaciones de hospedaje | Puedes hospedar paquetes múltiples en un repositorio. | +| Permisos | {{ site.data.reusables.package_registry.public-or-private-packages }} Puedes utilizar los roles y equipos de {{ site.data.variables.product.prodname_dotcom }} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | +| Visibilidad | {% data reusables.package_registry.public-or-private-packages %} + +{% if currentVersion == "free-pro-team@latest" %} +### Acerca de la facturación para {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.packages-billing %}{% data reusables.package_registry.packages-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". + +{% data reusables.package_registry.container-registry-beta-billing-note %} +{% endif %} + +### Formatos y clientes admitidos + +{% data variables.product.prodname_registry %} usa los comandos de herramientas del paquete nativo con los que ya estás familiarizado para publicar e instalar versiones del paquete. +#### Soporte para los registros de paquetes + +{% if currentVersion == "free-pro-team@latest" %} +Los registros de paquetes utilizan a `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de paquetes, reemplazando `PACKAGE-TYPE` con el espacio de nombre de paquete. Por ejemplo, tu Gemfile se hospedará en `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. + +{% else %} + +Los tipos de paquete compatibles en {% data variables.product.product_location %} pueden variar ya que tu administrador de sitio puede habilitar o inhabilitar el soporte para diferentes tipos de paquetes. Para obtener más informacón, consulta la sección "[Administrar GitHub Packages para tu empresa](/enterprise/admin/packages)". + +Si {% data variables.product.product_location %} tiene habilitado el aislamiento de subdominio, entonces los registros de paquete utilizarán `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de paquetes, reemplazando a `PACKAGE-TYPE` con el espacio de nombre del paquete. Por ejemplo, tu Dockerfile se hospedará en `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. + +Si se inhabilitó el aislamiento de subdominios en {% data variables.product.product_location %}, entonces los registros de paquete utilizarán `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de pquetes. Por ejemplo, tu Gemfile se hospedaría en `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, reemplazando *HOSTNAME* con el nombre del host de tu instancia de {% data variables.product.prodname_ghe_server %}. |{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | +| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------------- | +| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | + +{% else %} + +Con el aislamiento de subdominios habilitado en {% data variables.product.product_location %}: + +| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | +| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------- | +| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| N/A | Plataforma de administración del contenedor Docker | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | + +Con el aislamiento de subdominios inhabilitado en {% data variables.product.product_location %}: + +| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | +| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | --------------------------------------------------------- | +| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | + +{% note %} + +**Nota:** Docker no es compatible cuando inhabilitas el aislamiento de subdominios. + +{% endnote %} + +Para obtener más información acerca del aislamiento de subdominios, consulta la sección "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". + +{% endif %} + +Para obtener más información sobre cómo configurar tu cliente de paquetes para utilizarlo con el {% data variables.product.prodname_registry %}, consulta la sección "[Guías del cliente de paquetes para el {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)". + +{% if currentVersion == "free-pro-team@latest" %} +Para obtener más información acerca de Docker y del +{% data variables.product.prodname_github_container_registry %}, consulta la sección "[Guías de contenedor para {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)". +{% endif %} +### Autenticarte en {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +### Administrar paquetes + +Para instalar o publicar un paquete, debes usar un token con el ámbito adecuado, y tu cuenta de usuario debe tener los permisos pertinentes para ese repositorio. + +Por ejemplo: +- Para descargar e instalar paquetes desde un repositorio, tu token debe tener el ámbito `read:packages`, y tu cuenta de usuario debe tener permisos de lectura para el repositorio. +- Para eliminar una versión especificada de un paquete privado en {% data variables.product.product_name %}, tu token debe tener los ámbitos `delete:packages` y `repo`. Los paquetes públicos no se pueden eliminar. Para obtener más información, consulta "[Eliminar un paquete](/packages/manage-packages/deleting-a-package)". + +| Ámbito | Descripción | Permisos de repositorio | +| ----------------- | ------------------------------------------------------------------------------------------------------ | ----------------------- | +| `read:packages` | Descarga e instala paquetes de {% data variables.product.prodname_registry %} | lectura | +| `write:packages` | Carga y publica paquetes en {% data variables.product.prodname_registry %} | escritura | +| `delete:packages` | Elimina versiones especificadas de paquetes privados de {% data variables.product.prodname_registry %} | admin | +| `repo` | Carga y borra los paquetes (junto con los `write:packages`, o los `delete:packages`) | escritura o admin | + +Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. + +Para obtener más información, consulta: +- Encuentras algo que contradice la documentación +- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)" +- Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal + +### Administrar paquetes + +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. Cuando usas la API de GraphQL para consultar y eliminar paquetes privados, debes usar el mismo token que usas para autenticarte en {% data variables.product.prodname_registry %}. Para obtener más información, consulta las secciones "[Borrar un paquete](/packages/manage-packages/deleting-a-package)" y "[Formar llamadas con GraphQL](/graphql/guides/forming-calls-with-graphql)". + +Puedes configurar webhooks para suscribirte a eventos relacionados con paquetes, como cuando se publica o se actualiza un paquete. Para obtener más información, consulta el "[evento de webhook de `package`](/webhooks/event-payloads/#package)". + +### Contactar con soporte técnico + +{% if currentVersion == "free-pro-team@latest" %} +Si tienes retroalimentación o solicitudes de características para +{% data variables.product.prodname_registry %}, utiliza el [formato de retroalimentación para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). + +Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: + +* Experimentas alguna cosa que contradice la documentación +* Encuentras errores vagos o poco claros +* Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal + +{% else %} +Si necesitas soporte para +{% data variables.product.prodname_registry %}, por favor, contacta a tus administradores de sistema. + +{% endif %} diff --git a/translations/es-ES/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000000..d1193f88aba83 --- /dev/null +++ b/translations/es-ES/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Conceptos básicos para GitHub Packages +intro: 'A continuación encontrarás una lista de términos comunes del {% data variables.product.prodname_registry %} que utilizamos en nuestros sitios y documentación.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Para GitHub + +Un paquete es un software auto-contenido y reutilizable que incluye código y metadatos que un desarrollador junta en un lugar común para que los demás lo utilicen. Los metadatos de un paquete pueden incluir el número de versión, el nombre, y las dependencias del código. Los paquetes simplifican el uso y la distribución de soluciones para problemas comunes tales como el necesitar marcos de trabajo para desarrollo o probar un proyecto, limpiadores de código para mejorar la calidad del mismo, o herramientas de aprendizaje automatizado estándares de la industria para impulsar tu aplicación. Los paquetes existen en muchos ecosistemas. Por ejemplo, puedes empaquetar código de Node.js y de Java o imágenes de contenedor. + +### Contenedor + +Un contenedor es una unidad de software que se diseña para desplegar software de forma confiable en un modo estandarizado en cualquier plataforma. Un contenedor opera como un ambiente virtual aislado o una instancia que puede ejecutar varios paquetes de software y componentes en el mismo kernel del host como tu sistema operativo. Los contenedores utilizan menos recursos que las máquinas virtuales porque no necesitan incluir su porpio hardware virtual para ejecutarse. Los contenedores se crean utilizando un archivo de imagen de contenedor, tal como un Dockerfile, y un cliente de contenedor o programa de tiempo de ejecución. + +### Imagen de contenedor + +Una imagen de contenedor es un tipo de archivo empaquetado que especifica los requisitos de software para ejecutar una app desde un contenedor. Una imagen de contenedor habitualmente incluye el código de la app, bibliotecas e instrucciones del tiempo de ejecución. Para garantizar que se utilizan los mismos detalles de imagen donde sea que ésta se despliegue y ejecutem las imagenes de contenedor se versionan automáticamente y no se pueden cambiar una vez que una imagen de contenedor se compile en un contenedor. + +### Contenedor Docker + +Un contenedor de Docker es un tipo de contenedor de código abierto que se crea en la plataforma de Docker. El formato de imagen original de Docker se ha convertido en la Especificación de Imagen de la OCI (Iniciativa de Contenedores Abiertos, por sus siglas en inglés). Para obtener más información, consulta la "[Documentación de Docker](https://docs.docker.com/get-started/overview/)". diff --git a/translations/es-ES/content/packages/learn-github-packages/index.md b/translations/es-ES/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000000..004491e9028eb --- /dev/null +++ b/translations/es-ES/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Aprende sobre GitHub Packages +shortTitle: Aprende sobre GitHub Packages +intro: 'Puedes encontrar más información sobre GitHub Packages, incluyendo la publicación de paquetes nuevos en el {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md b/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000000..32a941272b011 --- /dev/null +++ b/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: Publicar un paquete +intro: 'Puedes publicar un paquete en {% data variables.product.prodname_registry %} para que el paquete esté disponible para que otros lo descarguen y lo vuelvan a utilizar.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: Cualquier persona con permisos de escritura para un repositorio puede publicar un paquete en ese repositorio. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Acerca de los paquetes publicados + +Puedes ayudar a la gente a entender y usar tu paquete proporcionando una descripción y otros detalles como instrucciones de instalación y uso en la página del paquete. GitHub proporciona metadatos para cada versión, como la fecha de publicación, la actividad de descarga y las versiones recientes. Para obtener una página de paquete de ejemplo, consulta [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). + +{% data reusables.package_registry.public-or-private-packages %} Un repositorio puede contener más de un paquete. Para evitar confusiones, asegúrate de que el archivo README y la descripción proporcionen información clara de cada paquete. + +{% if currentVersion == "free-pro-team@latest" %} +Si una versión nueva de un paquete soluciona una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio. +{% data variables.product.prodname_dotcom %} revisa cada asesoría de seguridad que se publica y podría utilizarla para enviar {% data variables.product.prodname_dependabot_alerts %} a los repositorios afectados. Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". +{% endif %} + +### Publicar un paquete + +Puedes publicar un paquete en el {% data variables.product.prodname_registry %} si utilizas cualquier {% if currentVersion == "free-pro-team@latest" %}cliente de paquete compatible{% else %}tipo de paquete habilitado para tu instancia{% endif %} si sigues los mismos lineamientos generales. + +1. Crea o usa un token de acceso existente con los ámbitos adecuados para la tarea que deseas realizar. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". +2. Autentícate en {% data variables.product.prodname_registry %} mediante tu token de acceso y las instrucciones para tu cliente del paquete. +3. Publica el paquete siguiendo las instrucciones para el cliente de tu paquete. + +Para obtener instrucciones específicas para tu cliente de paquete, consulta "[Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)". + +Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Ver paquetes](/packages/publishing-and-managing-packages/viewing-packages)." diff --git a/translations/es-ES/content/packages/manage-packages/deleting-a-package.md b/translations/es-ES/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000000..b15ffde2d1314 --- /dev/null +++ b/translations/es-ES/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: Eliminar un paquete +intro: 'Puedes eliminar una versión de un paquete privado utilizando GraphQL o en {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### Acerca de la eliminación de paquetes privados + +Para borrar un paquete de imágenes de contenedor en {% data variables.product.product_name %}, consulta la sección "[Borrar una imagen de contenedor](/packages/guides/deleting-a-container-image)". + +{% endif %} + +### Acerca de la eliminación de paquetes privados + +Solo puedes eliminar una versión especificada de un paquete privado en {% data variables.product.product_name %} o con la API de GraphQL. Para hacer que un paquete privado completo deje de aparecer en {% data variables.product.product_name %}, primero debes eliminar todas las versiones del paquete. + +{% if currentVersion == "free-pro-team@latest" %} +### Acerca de la eliminación paquetes públicos + +Para evitar que se rompan proyectos que puedan depender de tus paquetes, no puedes eliminar un paquete público completo o versiones específicas de un paquete público. + +En circunstancias especiales, por ejemplo, por razones legales o para cumplir con los estándares del RGPD, puedes solicitarle a {% data variables.contact.github_support %} que elimine un paquete público por ti, usando [nuestro formulario de contacto](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). + +{% else %} + +En este momento, el {% data variables.product.prodname_registry %} en {% data variables.product.product_location %} no es compatible con el borrado de paquetes públicos. + +{% endif %} + +### Eliminar una versión de un paquete privado en {% data variables.product.product_name %} + +Para eliminar una versión de un paquete privado, debes tener permisos de administrador en el repositorio. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. Haz clic en el nombre del paquete que deseas eliminar. ![Nombre del paquete](/assets/images/help/package-registry/select-pkg-cloud.png) +4. A la derecha, usa el menú desplegable **Edit package (Editar paquete)** y selecciona "Manage versions" (Administrar versiones). ![Nombre del paquete](/assets/images/help/package-registry/manage-versions.png) +5. A la derecha de la versión que deseas eliminar, haz clic en **Delete (Eliminar)**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-package-button.png) +6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Eliminar una versión de un paquete privado con GraphQL + +Usa la mutación `deletePackageVersion` en la API de GraphQL. Debes usar un token con ámbitos `read:packages`, `delete:packages` y `repo`. Para obtener más información acerca de los tokens, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". + +Aquí hay un comando cURL de ejemplo para eliminar una versión de paquete con el ID de versión del paquete de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, mediante un token de acceso personal. + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +Para encontrar todos los paquetes privados que publicaste en {% data variables.product.prodname_registry %}, junto con los ID de versión de los paquetes, puedes usar la conexión `registryPackagesForQuery`. Necesitarás un token con los ámbitos `read:packages` y `repo`. Necesitarás un token con los ámbitos `read:packages` y `repo`. + +Para obtener más información acerca de la mutación `deletePackageVersion`, consulta "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)". + +No puedes eliminar un paquete completo, pero si eliminas todas las versiones de un paquete, dejará de aparecer en {% data variables.product.product_name %} diff --git a/translations/es-ES/content/packages/manage-packages/index.md b/translations/es-ES/content/packages/manage-packages/index.md new file mode 100644 index 0000000000000..ba96579a495a8 --- /dev/null +++ b/translations/es-ES/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Administrar los paquetes de GitHub +shortTitle: Administrar los paquetes de GitHub +intro: 'Puedes publicar nuevos paquetes en {% data variables.product.prodname_registry %}, ver e instalar paquetes existentes y, en circunstancias especiales, eliminar paquetes existentes.' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/es-ES/content/packages/manage-packages/installing-a-package.md b/translations/es-ES/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000000..8b59db1166aea --- /dev/null +++ b/translations/es-ES/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: Instalar un paquete +intro: 'Puedes instalar un paquete desde {% data variables.product.prodname_registry %} y usar el paquete como dependencia en tu propio proyecto.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete desde ese repositorio. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Acerca de la instalación del paquete + +Puedes buscar {% data variables.product.product_name %} para encontrar los paquetes en {% data variables.product.prodname_registry %} que puedes instalar en tu propio proyecto. Para obtener más información, consulta "[Buscar {% data variables.product.prodname_registry %} para paquetes](/github/searching-for-information-on-github/searching-for-packages)". + +Una vez que encuentres un paquete, puedes leer las instrucciones de la descripción y la instalación y el uso del paquete en la página del paquete. + +### Instalar un paquete + +Puedes instalar un paquete del {% data variables.product.prodname_registry %} si utilizas cualquier {% if currentVersion == "free-pro-team@latest" %}cliente de paquetes compatible{% else %}tipo de paquete habilitado en tu instancia{% endif %} siguiendo los mismos lineamientos generales. + +1. Autenticar para {% data variables.product.prodname_registry %} usando las instrucciones para tu cliente de paquete. Para obtener más información, consulta "[Acerca de los tokens](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". +2. Instala el paquete usando las instrucciones para tu cliente de paquete. + +Para obtener instrucciones específicas para tu cliente de paquete, consulta "[Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)". diff --git a/translations/es-ES/content/packages/manage-packages/viewing-packages.md b/translations/es-ES/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000000..5adf88e588c7f --- /dev/null +++ b/translations/es-ES/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: Visualizar paquetes +intro: 'Puedes ver los detalles de los paquetes que se publican en un repositorio y filtrar los resultados por organización o usuario.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: Cualquiera con permisos de lectura en un repositorio puede ver los paquetes del mismo. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Ver paquetes de un repositorio + +Los paquetes deben estar instalados al nivel del repositorio, pero puedes ver todos los paquetes de una organización y todos los paquetes que has publicado. {% data reusables.package_registry.package-page-info %} + +### Visualizar los paquetes de un repositorio + +Puedes ver todos los paquetes en un repositorio y buscar paquetes específicos en el mismo. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Visualizar los paquetes de una organización + +Puedes ver todos los paquetes instalados en una organización y buscar un paquete específico instalado en los repositorios de una organización. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Under your organization name, click +{% octicon "package" aria-label="The package icon" %} **Paquetes**. +{% data reusables.package_registry.navigate-to-packages %} + +### Visualizar tus paquetes + +Puedes ver todos los paquetes que has instalado y buscar uno específico en todas las organizaciones y repositorios. + +{% data reusables.profile.access_profile %} +2. En la zona de navegación principal, sobre la página de perfil, da clic en **Paquetes**. ![Pestaña Project (Proyecto)](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### Further reading + +- "[Buscar paquetes](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md new file mode 100644 index 0000000000000..61fdddedb372b --- /dev/null +++ b/translations/es-ES/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Guía de inciio rápido para GitHub Packages +intro: 'Publica en el {% data variables.product.prodname_registry %} en 5 minutos o menos con {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: verdadero +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introducción + +Solo necesitas un repositorio existente de {% data variables.product.prodname_dotcom %} para publicar un paquete en el {% data variables.product.prodname_registry %}. En esta guía, crearás un flujo de trabajo de {% data variables.product.prodname_actions %} para probar tu código y luego lo publicarás en el {% data variables.product.prodname_registry %}. Ten la libertad de crear un repositorio nuevo para esta guía de incio rápido. Puedes utilizarlo para probar este flujo de trabajo de {% data variables.product.prodname_actions %}, y los subsecuentes. + +### Publicar tu paquete + +1. Crea un repositorio nuevo en {% data variables.product.prodname_dotcom %}, agregando el `.gitignore` para Node. Crea un repositorio si te gustaría borrar este paquete posteriormente. Los paquetes públicos no podrán borrarse. Para obtener más información, consulta la sección "[Crear un nuevo repositorio](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clona el repositorio en tu máquina local. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Crea un archivo `index.js` y agrega una alerta básica que diga "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Inicializa un paquete de npm. En el asistente de inicialización de paquetes, ingresa tu paquete con el nombre _`@YOUR-USERNAME/YOUR-REPOSITORY`_, y configura el script de prueba como `exit 0` si no tienes ninguna prueba. Confirma tus cambios y súbelos a +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. Desde tu repositorio en {% data variables.product.prodname_dotcom %}, crea un archivo nuevo en el directorio `.github/workflows` que se llame `release-package.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." +6. Copia el siguiente contenido de YAML en el archivo `release-package.yml`. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. Desplázate hasta el final de la página y selecciona **Crear una rama nueva para esta confirmación e iniciar una solicitud de cambios**. Después, para crear una solicitud de cambios, da clic en **Proponer un archivo nuevo**. +8. **Fusiona** la solicitud de cambios. +9. Navega a la pestaña de **Código** y crea un lanzamiento nuevo para probar el flujo de trabajo. Para obtener más información, consulta la sección "[Gestionar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)". + +El crear un lanzamiento nuevo en tu repositorio activa el flujo de trabajo para compilar y probar tu código. Si las pruebas pasan, entonces el paquete se publicará en {% data variables.product.prodname_registry %}. + +### Visualizar tu paquete publicado + +Los paquetes se publican a nivel del repositorio. Puedes ver todos los paquetes en un repositorio y buscar un paquete específico. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Instalar un paquete publicado + +Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, consulta la sección "[Configurar npm para utilizarlo con el {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)". + +### Pasos siguientes + +El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero, este es solo el principio de lo que puedes hacer con {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más. + +El combinar el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu proceso de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí hay algunos recursos útiles para llevar a cabo los siguientes pasos con el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %}: + +- "[Aprende sobre el {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para un tutorial más a fondo de GitHub Packages +- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para un tutorial más a fondo de GitHub Actions +- "[Guías](/packages/guides)" para los casos de uso y ejemplos específicos diff --git a/translations/es-ES/content/rest/README.md b/translations/es-ES/content/rest/README.md new file mode 100644 index 0000000000000..4f963e6916ee1 --- /dev/null +++ b/translations/es-ES/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +¡El directorio `/content/rest` es donde viven los documentos de la API de REST de GitHub! + +* Los directorios `/content/rest/guides` y `/content/rest/overview` contienen artículos normales. Estos los puede editar una persona. +* El directorio `/content/rest/reference` contiene un artículo para cada grupo de terminales en la API de REST de GitHub. La mayoría del contenido en este directorio se procesa utilizando etiquetas de `include`. + + El contenido que se procesa con las etiquetas de `include` se toma del directorio `/lib/rest/static`, el cual se genera automáticamente desde el código abierto de la API en GitHub y no debe editarlo ninguna persona. Para obtener más información, consulta el archivo [`/lib/rest/README.md`](/lib/rest/README.md). + + **Como resultado, no podemos aceptar contribuciones a la referencia de la API de REST en este repositorio.** diff --git a/translations/es-ES/content/rest/guides/basics-of-authentication.md b/translations/es-ES/content/rest/guides/basics-of-authentication.md new file mode 100644 index 0000000000000..72b012f4bc49e --- /dev/null +++ b/translations/es-ES/content/rest/guides/basics-of-authentication.md @@ -0,0 +1,309 @@ +--- +title: Información básica sobre la autenticación +intro: Aprende acerca de las formas diferentes de autenticarse con algunos ejemplos. +redirect_from: + - /guides/basics-of-authentication + - /v3/guides/basics-of-authentication + - /rest/basics-of-authentication +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +En esta sección, vamos a enfocarnos en lo básico de la autenticación. Específicamente, vamos a crear un servidor en Ruby (utilizando [Sintatra][Sinatra]) que implemente el [flujo web][webflow] de una aplicación en varias formas diferentes. + +{% tip %} + +Puedes descargar todo el código fuente de este proyecto [del repo platform-samples](https://github.com/github/platform-samples/tree/master/api/). + +{% endtip %} + +### Registrar tu app + +Primero, necesitas [registrar tu aplicación][new oauth app]. A cada aplicación de OAuth que se registra se le asigna una ID de Cliente única y un Secreto de Cliente. ¡El Secreto de Cliente no puede compartirse! Eso incluye el verificar la secuencia en tu repositorio. + +Puedes llenar toda la información como más te guste, con excepción de la **URL de rellamado para la autorización**. Esta es fácilmente la parte más importante para configurar tu aplicación. Es la URL de rellamado a la cual {% data variables.product.product_name %} devuelve al usuario después de una autenticación exitosa. + +Ya que estamos ejecutando un servidor común de Sinatra, la ubicación de la instancia local se configura como `http://localhost:4567`. Vamos a llenar la URL de rellamado como `http://localhost:4567/callback`. + +### Aceptar la autorización del usuario + +{% data reusables.apps.deprecating_auth_with_query_parameters %} + +Ahora, vamos a comenzar a llenar nuestro servidor común. Crea un archivo que se llame _server.rb_ y pégale esto: + +``` ruby +require 'sinatra' +require 'rest-client' +require 'json' + +CLIENT_ID = ENV['GH_BASIC_CLIENT_ID'] +CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID'] + +get '/' do + erb :index, :locals => {:client_id => CLIENT_ID} +end +``` + +Tu ID de cliente y tus llaves secretas de cliente vienen de [la página de configuración de tu aplicación][app settings]. +{% if currentVersion == "free-pro-team@latest" %} **Nunca, _jamás_** almacenes estos valores en +{% data variables.product.product_name %} ni en algún otro lugar público, para el caso.{% endif %} Te recomendamos almacenarlos como +[variables de ambiente][about env vars]--que es exactamente lo que hemos hecho aquí. + +Posteriormente, pega este contenido en _views/index.erb_: + +``` erb + + + + +

+ Well, hello there! +

+

+ We're going to now talk to the GitHub API. Ready? + Click here to begin! +

+

+ If that link doesn't work, remember to provide your own Client ID! +

+ + +``` + +(Si no estás familiarizado con la forma en que funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra guide].) + +También, ten en cuenta que la URL utiliza el parámetro de consulta `scope` para definir los [alcances][oauth scopes] que solicita la aplicación. Para nuestra aplicación, estamos solicitando el alcance `user:email` para leer las direcciones de correo electrónico privadas. + +Navega en tu buscador hacia `http://localhost:4567`. Después de dar clic en el enlace, se te llevará a {% data variables.product.product_name %} y se te mostrará un diálogo que se ve más o menos así: ![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png) + +Si confías en ti mismo, da clic en **Autorizar App**. ¡Oh-oh! Sinatra te arroja un error `404`. ¡¿Qué pasa?! + +Bueno, ¡¿recuerdas cuando especificamos la URL de rellamado como `callback`? No proporcionamos una ruta para ésta, así que {% data variables.product.product_name %} no sabe dónde dejar al usuario después de autorizar la app. ¡Arreglémoslo ahora! + +#### Proporcionar un rellamado + +En _server.rb_, agrega una ruta para especificar lo que debe hacer la rellamada: + +``` ruby +get '/callback' do + # get temporary GitHub code... + session_code = request.env['rack.request.query_hash']['code'] + + # ... and POST it back to GitHub + result = RestClient.post('https://github.com/login/oauth/access_token', + {:client_id => CLIENT_ID, + :client_secret => CLIENT_SECRET, + :code => session_code}, + :accept => :json) + + # extract the token and granted scopes + access_token = JSON.parse(result)['access_token'] +end +``` + +Después de que la app se autentica exitosamente, {% data variables.product.product_name %} proporciona un valor temporal de `code`. Necesitas hacer `POST` para este código en {% data variables.product.product_name %} para intercambiarlo por un `access_token`. Para simplificar nuestras solicitudes HTTP de GET y de POST, utilizamos el [rest-client][REST Client]. Nota que probablemente jamás accedas a la API a través de REST. Para aplicarlo con más seriedad, probablemente debas usar [una biblioteca escrita en tu lenguaje preferido][libraries]. + +#### Verificar los alcances otorgados + +Los usuarios pueden editar los alcances que solicitaste cambiando directamente la URL. Esto puee otorgar a tu aplicación menos accesos de los que solicitaste originalmente. Antes de hacer cualquier solicitud con el token, verifica los alcances que el usuario le otorgó a éste. Para obtener más información acerca de los alcances solicitados y otorgados, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)". + +Los alcances que otorgamos se devuelven como parte de la respuesta de intercambiar un token. + +``` ruby +get '/callback' do + # ... + # Get the access_token using the code sample above + # ... + + # check if we were granted user:email scope + scopes = JSON.parse(result)['scope'].split(',') + has_user_email_scope = scopes.include? 'user:email' +end +``` + +En nuestra aplicación, estamos utilizando `scopes.include?` para verificar si se nos otorgó el alcance de `user:email` que necesitamos para recuperar las direcciones de correo electrónico. Si la aplicación hubiera preguntado por otros alcances, habríamos verificado esas también. + +También, ya que hay una relación jerárquica entre alcances, debes verificar que se te haya otorgado el nuvel más bajo de los alcances que se requieren. Por ejemplo, si la aplicación hubiera pedido el alcance `user`, puede que se le haya otorgado únicamente el alcance `user:email`. En ese caso, a la applicación no se le hubiera otorgado lo que pidió, pero los alcances que obtuvo hubieran seguido siendo suficientes. + +No es suficiente verificar los alcances solo antes de hacer las solicitudes, ya que es posible que los usuarios cambien los alcances entre tus solicitudes de verificación y las solicitudes reales. En caso de que esto suceda, las llamadas a la API que esperas tengan éxito podrían fallar con un estado `404` o `401`, o bien, podrían devolver un subconjunto de información diferente. + +Para ayudarte a manejar estas situaciones fácilmente, todas las respuestas de la API a las solicitudes que se hagan con tokens válidos también contienen un [encabezado de `X-OAuth-Scopes`][oauth scopes]. Este encabezado contiene la lista de alcances del token que se utilizó para realizar la solicitud. Adicionalmente a esto, la API de Aplicaciones de OAuth proporciona una terminal para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[verificar la validez de un token\]\[/rest/reference/apps#check-a-token\]{% else %}\[verificar la validez de un token\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Utiliza esta información para detectar los cambios en los alcances de los tokens, y para informar a tus usuarios sobre los cambios diposnibles en la funcionalidad de la aplicación. + +#### Realizar solicitudes autenticadas + +Por fin, con este token de acceso, podrás hacer solicitudes autenticadas como el usuario que inició sesión: + +``` ruby +# fetch user information +auth_result = JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user', + {:params => {:access_token => access_token}})) + +# if the user authorized it, fetch private emails +if has_user_email_scope + auth_result['private_emails'] = + JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails', + {:params => {:access_token => access_token}})) +end + +erb :basic, :locals => auth_result +``` + +Podemos hacer lo que queramos con nuestros resultados. En este caso, solo las vaciaremos directamente en _basic.erb_: + +``` erb +

Hello, <%= login %>!

+

+ <% if !email.nil? && !email.empty? %> It looks like your public email address is <%= email %>. + <% else %> It looks like you don't have a public email. That's cool. + <% end %> +

+

+ <% if defined? private_emails %> + With your permission, we were also able to dig up your private email addresses: + <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %> + <% else %> + Also, you're a bit secretive about your private email addresses. + <% end %> +

+``` + +### Implementar la autenticación "persistente" + +Estaríamos hablando de un pésimo modelo si requerimos que los usuarios inicien sesión en la app cada vez que necesiten acceder a la página web. Por ejemplo, intenta navegar directamente a `http://localhost:4567/basic`. Obtendrás un error. + +¿Qué pasaría si pudiéramos evitar todo el proceso de "da clic aquí", y solo lo _recordáramos_, mientras que los usuarios sigan en sesión dentro de +{% data variables.product.product_name %}, y pudieran acceder a esta aplicación? Agárrate, +porque _eso es exactamente lo que vamos a hacer_. + +Nuestro pequeño servidor que mostramos antes es muy simple. Para poder insertar algún tipo de autenticación inteligente, vamos a optar por utilizar sesiones para almacenar los tokens. Esto hará que la autenticación sea transparente para el usuario. + +También, ya que estamos haciendo persistir a los alcances dentro de la sesión, necesitaremos gestionar los casos cuando el usuario actualice los alcances después de que los verifiquemos, o cuando revoque el token. Para lograrlo, utilizaremos un bloque de `rescue` y verificaremos que la primera llamada a la API sea exitosa, lo cual verificará que el token sea válido. Después de esto, verificaremos el encabezado de respuesta de `X-OAuth-Scopes` para verificar que el usuario no haya revocado el alcance `user:email`. + +Crea un archivo que se llame _advanced_server.rb_, y pega estas líneas en él: + +``` ruby +require 'sinatra' +require 'rest_client' +require 'json' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +# if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET'] +# CLIENT_ID = ENV['GITHUB_CLIENT_ID'] +# CLIENT_SECRET = ENV['GITHUB_CLIENT_SECRET'] +# end + +CLIENT_ID = ENV['GH_BASIC_CLIENT_ID'] +CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID'] + +use Rack::Session::Pool, :cookie_only => false + +def authenticated? + session[:access_token] +end + +def authenticate! + erb :index, :locals => {:client_id => CLIENT_ID} +end + +get '/' do + if !authenticated? + authenticate! + else + access_token = session[:access_token] + scopes = [] + + begin + auth_result = RestClient.get('{% data variables.product.api_url_code %}/user', + {:params => {:access_token => access_token}, + :accept => :json}) + rescue => e + # request didn't succeed because the token was revoked so we + # invalidate the token stored in the session and render the + # index page so that the user can start the OAuth flow again + + session[:access_token] = nil + return authenticate! + end + + # the request succeeded, so we check the list of current scopes + if auth_result.headers.include? :x_oauth_scopes + scopes = auth_result.headers[:x_oauth_scopes].split(', ') + end + + auth_result = JSON.parse(auth_result) + + if scopes.include? 'user:email' + auth_result['private_emails'] = + JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails', + {:params => {:access_token => access_token}, + :accept => :json})) + end + + erb :advanced, :locals => auth_result + end +end + +get '/callback' do + session_code = request.env['rack.request.query_hash']['code'] + + result = RestClient.post('https://github.com/login/oauth/access_token', + {:client_id => CLIENT_ID, + :client_secret => CLIENT_SECRET, + :code => session_code}, + :accept => :json) + + session[:access_token] = JSON.parse(result)['access_token'] + + redirect '/' +end +``` + +La mayoría de este código debería serte familiar. Por ejemplo, aún estamos utilizando `RestClient.get` para llamar a la API de {% data variables.product.product_name %}, y aún estamos pasando nuestros resultados par que se interpreten en una plantilla de ERB (en esta ocasión, se llama `advanced.erb`). + +También, ahora tenemos el método `authenticated?`, el cual verifica si el usuario ya se autenticó. Si no, se llamará al método `authenticate!`, el cual lleva a cabo el flujo de OAuth y actualiza la sesión con el token que se otorgó y con los alcances. + +Después, crea un archivo en _views_, el cual se llame _advanced.erb_ y pega este markup dentro de él: + +``` erb + + + + +

Well, well, well, <%= login %>!

+

+ <% if !email.empty? %> It looks like your public email address is <%= email %>. + <% else %> It looks like you don't have a public email. That's cool. + <% end %> +

+

+ <% if defined? private_emails %> + With your permission, we were also able to dig up your private email addresses: + <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %> + <% else %> + Also, you're a bit secretive about your private email addresses. + <% end %> +

+ + +``` + +Desde la líne de comandos, llama a `ruby advanced_server.rb`, lo cual inicia tu servidor en el puerto `4567` -- el mismo puerto que utilizamos cuando tuvimos una app de Sinatra sencilla. Cuando navegas a `http://localhost:4567`, la app llama a `authenticate!`, lo cual te redirige a `/callback`. Entonces, `/callback` nos regresa a `/` y, ya que estuvimos autenticados, interpreta a _advanced.erb_. + +Podríamos simplificar completamente esta ruta redonda si solo cambiamos nuestra URL de rellamado en {% data variables.product.product_name %} a `/`. Pero, ya que tanto _server.rb_ como _advanced.rb_ dependen de la misma URL de rellamado, necesitamos hacer un poco más de ajustes para que funcione. + +También, si nunca hubiéramos autorizado esta aplicación para acceder a nuestros datos de {% data variables.product.product_name %}, habríamos visto el mismo diálogo de confirmación del pop-up anterior para advertirnos. + +[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ +[Sinatra]: http://www.sinatrarb.com/ +[about env vars]: http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables +[Sinatra guide]: https://github.com/sinatra/sinatra-book/blob/master/book/Introduction.markdown#hello-world-application +[REST Client]: https://github.com/archiloque/rest-client +[libraries]: /libraries/ +[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[new oauth app]: https://github.com/settings/applications/new +[app settings]: https://github.com/settings/developers diff --git a/translations/es-ES/content/rest/guides/best-practices-for-integrators.md b/translations/es-ES/content/rest/guides/best-practices-for-integrators.md new file mode 100644 index 0000000000000..9b4de0d708498 --- /dev/null +++ b/translations/es-ES/content/rest/guides/best-practices-for-integrators.md @@ -0,0 +1,164 @@ +--- +title: Mejores prácticas para los integradores +intro: 'Crea una app que interactúe confiablemente con la API de {% data variables.product.prodname_dotcom %} y proporcione la mejor experiencia para tus usuarios.' +redirect_from: + - /guides/best-practices-for-integrators/ + - /v3/guides/best-practices-for-integrators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +¡Estás interesado en integrarte con la plataforma de GitHub? [Estás en las manos correctas](https://github.com/integrations). Esta guía te ayudará a crear una app que proporcione la mejor de las experiencias para tus usuarios *y* que garantice su confiabilidad al interactuar con la API. + +### Asegura las cargas útiles que se entregen desde GitHub + +Es muy importante que asegures [las cargas útiles que se envíen desde GitHub][event-types]. Aunque en una carga útil jamás se transmita información personal (como las contraseñas), no es bueno filtrar *ninguna* información. Algunos de los tipos de información que pudieran ser sensibles incluyen las direcciones de correo electrónico del confirmante o los nombres de los repositorios privados. + +Hya varios pasos que puedes tomar para asegurar la recepción de las cárgas útiles que GitHub entregue: + +1. Asegúrate de que tu servidor receptor tenga una conexión HTTPS. Predeterminadamente, GitHub verificará los certificados SSl cuando entregue las cargas útiles.{% if currentVersion == "free-pro-team@latest" %} +1. Puedes agregar [La dirección IP que utilizamos cuando entregamos ganchos](/github/authenticating-to-github/about-githubs-ip-addresses) a tu lista de conexiones permitidas de tu servidor. Para garantizar que siempre estés verificando la dirección IP correcta, puedes [utilizar la terminal de `/meta`](/rest/reference/meta#meta) para encontrar la dirección que utilizamos.{% endif %} +1. Proporciona [un token secreto](/webhooks/securing/) para garantizar que las cargas útiles vengan de GitHub definitivamente. Al requerir un token secreto, te estás asegurando de que ninguno de los datos que recibe tu servidor viene de GitHub en lo absoluto. Idealmente, deberías proporcionar un token secreto diferente *por cada usuario* de tu servicio. Así, si un token se pone en riesgo, nadie más se vería afectado. + +### Favorece el trabajo asincrónico sobre el sincronizado + +GitHub espera que las integraciones respondan dentro de los primeros {% if currentVersion == "free-pro-team@latest" %}10{% else %}30{% endif %} segundos de que se reciba la carga útil del webhook. Si tu servicio demora más que eso para completarse, entonces GitHub finaliza la conexión y se pierde la carga útil. + +Ya que es imposible predecir qué tan rápido completará esto tu servidor, deberías hacer todo "el trabajo real" en un job que actúe en segundo plano. [Resque](https://github.com/resque/resque/) (para Ruby), [RQ](http://python-rq.org/) (para Python), o [RabbitMQ](http://www.rabbitmq.com/) (para JAVA) son algunos ejemplos de bibliotecas que pueden manejar jobs de segundo plano para procesamiento y formación en cola. + +Nota que, aún si tienes un job ejecutándose en segundo plano, GitHub sigue esperando que tu servidor responda dentro de {% if currentVersion == "free-pro-team@latest" %}diez{% else %}veinte{% endif %} segundos. Tu servidor necesita reconocer que recibió la carga útil mediante el envío de algún tipo de respuesta. Es crítico que tu servicio realice cualquier validación de una carga útil tan pronto sea posible, para que puedas reportar con exactitud si tu servidor continuará con la solicitud o no. + +### Utiliza códigos de estado de HTTP adecuados cuando respondas a GitHub + +Cada webhook tiene su propia sección de "Entregas Recientes", la cual lista si los despliegues tuvieron éxito o no. + +![Vista de entregas recientes](/assets/images/webhooks_recent_deliveries.png) + +Deberías utilizar códigos de estado de HTTP adecuados para informar a los usuarios. Puedes utilizar códigos como el `201` o el `202` para reconocer la recepción de las cargas útiles que no se van a procesar (por ejemplo, una carga útil que entregue una rama que no sea la predeterminada). Reserva el código de error `500` para las fallas catastróficas. + +### Proporciona al usuario tanta información como sea posible + +Los usuarios pueden profundizar en las respuestas del servidor que envíes de vuelta a GitHub. Asegúrate de que tus mensajes son claros e informativos. + +![Visualizar la respuesta de una carga útil](/assets/images/payload_response_tab.png) + +### Sigue cualquier redireccionamiento que te envíe la API + +GitHub es muy explícito en decirte cuando un recurso se migró y lo hace proporcionándote un código de estado de redirección. Debes seguir estas redirecciones. Cada respuesta de redirección configura el encabezado `Location` con la URI nueva a la cual debes dirigirte. Si recibes una redirección, es mejor que actualices tu código para seguir a la nueva URI, en caso de que estés utilizando una ruta obsoleta que tal ves eliminemos. + +Hemos proporcionado [una lista de códigos de estado de HTTP](/rest#http-redirects) que puedes consultar cuando estés diseñando tu app para seguir las redirecciones. + +### No analices las URL manualmente + +A menudo, las respuestas a la API contienen datos en forma de URL. Por ejemplo, cuando solicitamos un repositorio, estamos enviando una clave denominada `clone_url` con la URL que puedes utilizar para clonar el repositorio. + +Para mantener la estabilidad de tu app, no deberías analizar estos datos o tratr de adivinar y construir el formato de las URL futuras. Tu app puede fallar si decidimos cambiar la URL. + +Por ejemplo, cuando estamos trabajando con resultados paginados, a menudo es tentador construir las URL que adjunten `?page=` al final. Evita esa tentación. [Nuestra guía sobre paginación](/guides/traversing-with-pagination) te ofrece tips de seguridad sobre cómo seguir resultados paginados de manera confiable. + +### Verifica el tipo de evento y de acción antes de procesar el evento + +Hay varios [tipos de eventos de webhook][event-types], y cada evento puede tener varias acciones. En medida en que el conjunto de características de GitHub crece, de vez en cuando agregaremos tipos de evento para nuevas acciones a los tipos de evento existentes. Asegúrate de que tu aplicación verifique el tipo y acción de un evento explícitamente antes de que hagas cualquier procesamiento de webhook. El encabezado de solicitud de `X-GitHub-Event` puede utilizarse para saber qué evento se recibió, para que el procesamiento se pueda gestionar de manera adecuada. De manera similar, la carga útil tiene una clave de `action` de alto nivel que puede utilizarse para saber qué acción se llevó a cabo en el objeto relevante. + +Por ejemplo, si configuraste un webhook de GitHub para "Enviarme **todo**", tu aplicación comenzará a recibir tipos de evento y acciones nuevos conforme se agreguen. Por lo tanto, **no se recomienda utilizar ningún tipo de cláusula "else" que reciba todo**. Toma como ejemplo el siguiente extracto de código: + +```ruby +# Not recommended: a catch-all else clause +def receive + event_type = request.headers["X-GitHub-Event"] + payload = request.body + + case event_type + when "repository" + process_repository(payload) + when "issues" + process_issues(payload) + else + process_pull_requests + end +end +``` + +En este ejemplo, se llamará correctamente a los métodos de `process_repository` y `process_issues` si se recibió un evento de `repository` o de `issues`. Sin embargo, cualquier otro tipo de evento resultaría en que se llamara a `process_pull_requests`. En medida en que se agreguen tipos de evento nuevos, esto dará como resultado un comportamiento incorrecto y los tipos de evento nuevos se procesarían de la misma forma que se haría con un evento de `pull_request`. + +En vez de esto, te sugerimos revisar los tipos de evento explícitamente y tomar acciones adecuadas para cada caso. En el siguiente ejemplo, estamos verificando explícitamente si hay eventos de `pull_request` y la cláusula `else` simplemente registra lo que recibimos en un tipo de evento nuevo: + +```ruby +# Recommended: explicitly check each event type +def receive + event_type = request.headers["X-GitHub-Event"] + payload = JSON.parse(request.body) + + case event_type + when "repository" + process_repository(payload) + when "issues" + process_issue(payload) + when "pull_request" + process_pull_requests(payload) + else + puts "Oooh, something new from GitHub: #{event_type}" + end +end +``` + +Ya que cada evento puede tener acciones múltiples también, se recomienda que las acciones se verifiquen de forma similar. Por ejemplo, el [`IssuesEvent`](/webhooks/event-payloads/#issues) tiene muchas acciones posibles. Estas incluyen a `opened` cuando se crea el informe de problemas, a `closed` cuando el informe de problemas se cierra, y a `assigned` cuando este informe se asigna a alguien. + +De la misma forma como agregamos tipos de evento, podemos agregar acciones nuevas a los eventos existentes. Por lo tanto, nuevamente **no se recomienda utilizar ningún tipo de cláusula "else" para recibir todo** cuando verificamos la acción de un evento. En vez de esto, te sugerimos verificar las acciones de evento explícitamente como lo hicimos con el tipo de evento. Un ejemplo de esto se ve muy similar a lo que sugerimos para los tipos de evento anteriormente: + +```ruby +# Recommended: explicitly check each action +def process_issue(payload) + case payload["action"] + when "opened" + process_issue_opened(payload) + when "assigned" + process_issue_assigned(payload) + when "closed" + process_issue_closed(payload) + else + puts "Oooh, something new from GitHub: #{payload["action"]}" + end +end +``` + +En este ejemplo, la acción `closed` se verifica primero antes de llamar al método `process_closed`. Cualquier acción sin identificar se registra para referencias futuras. + +{% if currentVersion == "free-pro-team@latest" %} + +### Lidiar con los límites de tasa + +El [límite de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting) de la API de GitHub se asegura de que la API sea rápida y esté disponible para todos. + +Si alcanzas un límite de tasa, se espera que te retires y no sigas haciendo solicitudes y que intentes más tarde cuando se te permita hacerlo. Si no lo haces, podríamos prohibir tu app. + +Siempre puedes [verificar el estado de tu límite de tasa](/rest/reference/rate-limit) en cualquier momento. El verificar tu límite de tasa no representa costo alguno para éste. + +### Lidiar con los abusos al límite de tasa + +[La sobre-explotación de los límites de tasa](/rest/overview/resources-in-the-rest-api#abuse-rate-limits) es otra forma en la que garantizamos la disponibilidad de la API. Para evitar llegar a este límite, deberás asegurarte de que tu aplicación siga los siguientes lineamientos. + +* Hacer solicitudes autenticadas, o utilizar la ID de cliente y secreto de tu aplicación. Las solicitudes sin autenticar están sujetas a un abuso del límite de tasa más agresivo. +* Hacer solicitudes en serie para solo un usuario o ID de cliente. No hagas solicitudes para solo un usuario o ID de cliente simultáneamente. +* Si haces muchas solicitudes de tipo `POST`, `PATCH`, `PUT`, o `DELETE` para un solo usuario o ID de cliente, espera por lo menos un segundo entre cada una. +* Cuando se te limita, utiliza el encabezado de respuesta `Retry-After` para bajar la velocidad. El valor del encabezado `Retry-After` siembre será un número entero, el cual representará la cantidad de segundos que debes esperar antes de volver a hacer la solicitud. Por ejemplo, `Retry-After: 30` significa que debes esperar 30 segundos antes de enviar más solicitudes. +* Las solicitudes que crean contenido que activa notificaciones, tales como informes de problemas, comentarios y solicitudes de extracción, puede limitarse aún más y no incluirá un encabezado de `Retry-After` en la respuesta. Por favor, crea este contenido con un ritmo razonable para evitar que se te limite nuevamente. + +Nos reservamos el derecho de cambiar estos lineamientos como sea necesario para garantizar la disponibilidad. + +{% endif %} + +### Lidiar con los errores de la API + +Aunque tu código jamás introducirá un error, podrías encontrarte con que has dado con varios errores sucesivos cuando intentas acceder a la API. + +En vez de ignorar los códigos de estado `4xx` y `5xx` repetidamente, debes asegurarte de que estás interactuando correctamente con la API. Por ejemplo, si una terminal solicita una secuencia y estás pasando un valor numérico, vas a recibir un error de validación `5xx`, y tu llamada no tendrá éxito. De forma similar, el intentar acceder a una terminal inexistente o no autorizada dará como resultado un error `4xx`. + +El ignorar los errores de validación constantes a propóstio podría resultar en la suspensión de tu app por abuso. + +[event-types]: /webhooks/event-payloads + +[event-types]: /webhooks/event-payloads diff --git a/translations/es-ES/content/rest/guides/building-a-ci-server.md b/translations/es-ES/content/rest/guides/building-a-ci-server.md new file mode 100644 index 0000000000000..b71810ff7667c --- /dev/null +++ b/translations/es-ES/content/rest/guides/building-a-ci-server.md @@ -0,0 +1,140 @@ +--- +title: Crear un servidor de IC +intro: Crea tu propio sistema de IC utilizando la API de Estados. +redirect_from: + - /guides/building-a-ci-server/ + - /v3/guides/building-a-ci-server +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +La [API de Estados][status API] es responsable de unir las confirmaciones con un servicio de pruebas para que cada carga que hagas pueda probarse y se represente en una solicitud de extracción de {% data variables.product.product_name %}. + +Esta guía utilizará la API para demostrar una configuración que puedes utilizar. En nuestro escenario, nosotros: + +* Ejecutaremos nuestra suit de IC cuando se abra una Solicitud de Extracción (configuraremos el estado de IC como pendiente). +* Cuando finalice la IC, configuraremos el estado de la Solicitud de Extracción como corresponda. + +Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Travis, Jenkins, o algo completamente distinto. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. + +Si aún no lo has hecho, asegúrate de [descargar ngrok][ngrok], y de aprender a [utilizarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las conexiones locales. + +Nota: puedes descargar todo el código fuente para este proyecto [del repo platform-samples][platform samples]. + +### Escribir tu servidor + +Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. Comencemos con esto: + +``` ruby +require 'sinatra' +require 'json' + +post '/event_handler' do + payload = JSON.parse(params[:payload]) + "Well, it worked!" +end +``` + +(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) + +Inicia este servidor. Predeterminadamente, Sinatra inicia en el puerto `4567`, así que también debes configurar ngrok para comenzar a escuchar este puerto. + +Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. El webhook debe configurarse para que se active cada que se crea o fusiona una Solicitud de Extracción. Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerirte que sea [el repositorio Spoon/Knife de @octocat](https://github.com/octocat/Spoon-Knife)? Después de esto, crearás un webhook nuevo en tu repositorio y lo alimentarás con la URL que te dio ngrok para luego escoger a `application/x-www-form-urlencoded` como el tipo de contenido: + +![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) + +Haz clic en **Actualizar webhook**. Deberás ver una respuesta en el cuerpo que diga `Well, it worked!`. ¡Genial! Da clic en **Déjame selecionar eventos individuales**, y selecciona lo siguiente: + +* Estado +* Solicitud de Extracción + +Estos son los eventos que {% data variables.product.product_name %} enviará a nuestro servidor cuando ocurra cualquier acción relevante. Vamos a actualizar nuestro servidor para que *solo* gestione el escenario de Solicitud de Extracción ahora: + +``` ruby +post '/event_handler' do + @payload = JSON.parse(params[:payload]) + + case request.env['HTTP_X_GITHUB_EVENT'] + when "pull_request" + if @payload["action"] == "opened" + process_pull_request(@payload["pull_request"]) + end + end +end + +helpers do + def process_pull_request(pull_request) + puts "It's #{pull_request['title']}" + end +end +``` + +¿Qué está pasando? Cada evento que {% data variables.product.product_name %} envía adjunta un encabezado de HTTP de `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Desde ahí, tomaremos la carga útil de información y devolveremos el campo de título. En un escenario ideal, a nuestro servidor le interesaría cada vez que se actualiza una solicitud de extracción, no únicamente cuando se abre. Eso garantizaría que todas las cargas pasen la prueba de IC. Pero para efectos de esta demostración, solo nos interesará cuándo se abren. + +Para probar esta prueba de concepto, haz algunos cambios en una rama de tu repositorio de pruebas, y abre una solicitud de extracción. ¡Tu servidor deberá responder de acuerdo con los casos! + +### Trabajar con los estados + +Ya que configuramos el servidor, estamos listos para comenzar con nuestro primer requisito, que es configurar (y actualizar) los estados de IC. Nota que en cualquier momento que actualices tu servidor, puedes dar clic en **Volver a entregar** para enviar la misma carga útil. ¡No necesitas hacer una solicitud de extracción cada que haces un cambio! + +Ya que estamos interactuando con la API de {% data variables.product.product_name %}, utilizaremos a [Octokit.rb][octokit.rb] para administrar nuestras interacciones. Configuraremos a ese cliente con + +``` ruby +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +ACCESS_TOKEN = ENV['MY_PERSONAL_TOKEN'] + +before do + @client ||= Octokit::Client.new(:access_token => ACCESS_TOKEN) +end +``` + +Después de ésto, solo necesitaremos actualizar la solicitud de extracción en {% data variables.product.product_name %} para dejar en claro lo que estamos procesando en la IC: + +``` ruby +def process_pull_request(pull_request) + puts "Processing pull request..." + @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending') +end +``` + +Estamos haciendo tres cosas muy básicas aquí: + +* buscando el nombre completo del repositorio +* buscando el último SHA de la solicitud de extracción +* configurando el estado como "pendiente" + +¡Listo! Desde estepunto puedes ejecutar el proceso que sea que necesites para ejecutar tu suit de pruebas. Tal vez vas a pasar tu código a Jenkins, o a llamar a otro servicio web a través de su API, como con [Travis][travis api]. Después de eso, asegúrate actualizar el estado una vez más. En nuestro ejemplo, solo lo configuraremos como `"success"`: + +``` ruby +def process_pull_request(pull_request) + @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending') + sleep 2 # do busy work... + @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success') + puts "Pull request processed!" +end +``` + +### Conclusión + +En GitHub, utilizamos una versión de [Janky][janky] durante años para administrar nuestra IC. El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. En GitHub, nosotros: + +* Notificamos todo a Jenkins cuando se crea o actualiza una solicitud de extracción (a través de Janky) +* Esperamos una respuesta del estado de la IC +* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción + +Todas estas comunicaciones se canalizan de vuelta a nuestras salas de chat. No necesitas crear tu propia configuración de IC para utilizar este ejemplo. Siempre puedes confiar en las [Integraciones de GitHub][integrations]. + +[status API]: /rest/reference/repos#statuses +[ngrok]: https://ngrok.com/ +[using ngrok]: /webhooks/configuring/#using-ngrok +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server +[Sinatra]: http://www.sinatrarb.com/ +[octokit.rb]: https://github.com/octokit/octokit.rb +[travis api]: https://api.travis-ci.org/docs/ +[janky]: https://github.com/github/janky +[integrations]: https://github.com/integrations diff --git a/translations/es-ES/content/rest/guides/delivering-deployments.md b/translations/es-ES/content/rest/guides/delivering-deployments.md new file mode 100644 index 0000000000000..a01df7f33be12 --- /dev/null +++ b/translations/es-ES/content/rest/guides/delivering-deployments.md @@ -0,0 +1,156 @@ +--- +title: Entregar despliegues +intro: 'Al utilizar la API de REST de Despliegues, puedes crear herramientas personalizadas que interactúen con tu servidor y con una app de terceros.' +redirect_from: + - /guides/delivering-deployments/ + - /guides/automating-deployments-to-integrators/ + - /v3/guides/delivering-deployments +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +La [API de despliegues][deploy API] proporciona a tus proyectos hospedados en {% data variables.product.product_name %} la capadidad de lanzarlos en un servidor que te pertenezca. En combinación con [la API de estados][status API], podrás coordinar tus lanzamientos en el momento en que tu código llegue a la rama predeterminada. + +Esta guía utilizará la API para demostrar una configuración que puedes utilizar. En nuestro escenario, nosotros: + +* Fusionamos una solicitud de extracción +* Cuando finaliza la IC, configuramos el estado de la solicitud de extracción según corresponda. +* Cuando se fusiona la solicitud de extracción, ejecutamos nuestro despliegue en nuestro servidor. + +Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Heroku, Amazon, o algo completamente diferente. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. + +Si aún no lo has hecho, asegúrate de [descargar ngrok][ngrok], y de aprender a [utilizarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las conexiones locales. + +Nota: puedes descargar todo el código fuente para este proyecto [del repo platform-samples][platform samples]. + +### Escribir tu servidor + +Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. Comencemos con esto: + +``` ruby +require 'sinatra' +require 'json' + +post '/event_handler' do + payload = JSON.parse(params[:payload]) + "Well, it worked!" +end +``` + +(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) + +Inicia este servidor. Predeterminadamente, Sinatra inicia en el puerto `4567`, así que también debes configurar ngrok para comenzar a escuchar este puerto. + +Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. El webhook debe configurarse para que se active cada que se crea o fusiona una solicitud de extracción. Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerirte que sea [el repositorio Spoon/Knife de @octocat](https://github.com/octocat/Spoon-Knife)? Después de esto, crearás un webhook nuevo en tu repositorio y lo alimentarás con la URL que te dio ngrok para luego escoger a `application/x-www-form-urlencoded` como el tipo de contenido: + +![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) + +Haz clic en **Actualizar webhook**. Deberás ver una respuesta en el cuerpo que diga `Well, it worked!`. ¡Genial! Da clic en **Déjame selecionar eventos individuales**, y selecciona lo siguiente: + +* Despliegue +* Estado del despliegue +* Solicitud de Extracción + +Estos son los eventos que {% data variables.product.product_name %} enviará a nuestro servidor cuando ocurra cualquier acción relevante. Configuraremos nuestro servidor para que *solo* gestione cuando las solicitudes de extracción se fusionen ahora mismo: + +``` ruby +post '/event_handler' do + @payload = JSON.parse(params[:payload]) + + case request.env['HTTP_X_GITHUB_EVENT'] + when "pull_request" + if @payload["action"] == "closed" && @payload["pull_request"]["merged"] + puts "A pull request was merged! A deployment should start now..." + end + end +end +``` + +¿Qué está pasando? Cada evento que {% data variables.product.product_name %} envía adjunta un encabezado de HTTP de `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Cuando una solicitud de extracción se fusiona (su estado es `closed`, y `merged` se encuentra como `true`), iniciaremos un despliegue. + +Para probar esta prueba de concepto, haz algunos cambios en una rama de tu repositorio de pruebas, y abre una solicitud de extracción y fusiónala. ¡Tu servidor deberá responder de acuerdo con los casos! + +### Trabajar con despliegues + +Como ya tenemos nuestro servidor configurado, el código ya se revisó, y nuestras solicitudes de extracción se fusionaron, entonces queremos desplegar nuestro proyecto. + +Comenzaremos modificando nuestro detector de eventos para que procese las solicitudes de extracción cuando se fusiones, y para que comience a poner atención a los despliegues: + +``` ruby +when "pull_request" + if @payload["action"] == "closed" && @payload["pull_request"]["merged"] + start_deployment(@payload["pull_request"]) + end +when "deployment" + process_deployment(@payload) +when "deployment_status" + update_deployment_status +end +``` + +Basándonos en la información de la solicitud de extracción, comenzaremos llenando el método de `start_deployment`: + +``` ruby +def start_deployment(pull_request) + user = pull_request['user']['login'] + payload = JSON.generate(:environment => 'production', :deploy_user => user) + @client.create_deployment(pull_request['head']['repo']['full_name'], pull_request['head']['sha'], {:payload => payload, :description => "Deploying my sweet branch"}) +end +``` + +Los despliegues pueden tener algunos metadatos adjuntos en forma de una `payload` y una `description`. Aunque estos valores son opcionales, es de gran ayuda utilizarlos para registrar y representar la información. + +Cuando se crea un despliegue nuevo, se activa un evento completamente separado. Por eso es que tenemos un caso nuevo de `switch` en el gestor de eventos para nuestro `deployment`. Puedes utilizar esta información para que se te notifique cuando se active un despliegue. + +Los despliegues pueden tomar mucho tiempo, así que queremos detectar varios eventos, tales como cuando el despliegue se cree, y en qué estado está. + +Simulemos un despliegue que tome algunas acciones, y pondremos atención en el efecto que tiene sobre la salida. Primero, vamos a completar nuestro métoddo de `process_deployment`: + +``` ruby +def process_deployment + payload = JSON.parse(@payload['payload']) + # you can send this information to your chat room, monitor, pager, etc. + puts "Processing '#{@payload['description']}' for #{payload['deploy_user']} to #{payload['environment']}" + sleep 2 # simulate work + @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'pending') + sleep 2 # simulate work + @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'success') +end +``` + +Por último, estimularemos el almacenamiento de la información de los estados como una salida de la consola: + +``` ruby +def update_deployment_status + puts "Deployment status for #{@payload['id']} is #{@payload['state']}" +end +``` + +Bamos a explicar lo que está pasando. `start_deployment` creó un despliegue nuevo, lo cual activó el evento `deployment`. Desde ahí, llamamos a `process_deployment` para estimular las acciones que están sucediendo. Durante este procesamiento, también llamamos a `create_deployment_status`, el cual permite que un receptor sepa lo que está pasando, mientras cambiamos el estado a `pending`. + +Después de que termine el despliegue, configuramos el estado como `success`. + +### Conclusión + +En GitHub siempre hemos utilizado una versión de [Heaven][heaven] durante años para administrar nuestros despliegues. El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. En GitHub, nosotros: + +* Esperamos una respuesta del estado de la IC +* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción +* Heaven toma el código fusionado y lo despliega en nuestros servidores productivos y de pruebas +* Mientras tanto, Heaven también notifica a todos acerca de la compilación, a través de [Hubot][hubot] que espera en nuestras salas de chat + +¡Listo! No necesitas crear tu propia configuración de despliegue para utilizar este ejemplo. Siempre puedes confiar en las [Integraciones de GitHub][integrations]. + +[deploy API]: /rest/reference/repos#deployments +[status API]: /guides/building-a-ci-server +[ngrok]: https://ngrok.com/ +[using ngrok]: /webhooks/configuring/#using-ngrok +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments +[Sinatra]: http://www.sinatrarb.com/ +[heaven]: https://github.com/atmos/heaven +[hubot]: https://github.com/github/hubot +[integrations]: https://github.com/integrations diff --git a/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md b/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md new file mode 100644 index 0000000000000..ec70afb17a217 --- /dev/null +++ b/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md @@ -0,0 +1,111 @@ +--- +title: Descubrir los recursos para un usuario +intro: Aprende cómo encontrar los repositorios y organizaciones a los cuales puede acceder tu app para un usuario de manera confiable para tus solicitudes autenticadas a la API de REST. +redirect_from: + - /guides/discovering-resources-for-a-user/ + - /v3/guides/discovering-resources-for-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Cuando se hacen solicitudes autenticadas a la API de {% data variables.product.product_name %}, las aplicaciones a menudo tienen que obtener los repositorios y organizaciones del usuario. En esta guía, te explicaremos cómo descubrir estos recursos de forma confiable. + +Para interactuar con la API de {% data variables.product.product_name %}, estaremos utilizando [Octokit.rb][octokit.rb]. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples]. + +### Empezar + +Si aún no lo has hecho, deberías leer la guía de ["Conceptos Básicos de la Autenticación"][basics-of-authentication] antes de comenzar a trabajar en los siguientes ejemplos. Éstos asumen que tienes una [aplicación de OAuth registrada][register-oauth-app] y de que [tu aplicación tiene un token de OAuth para un usuario][make-authenticated-request-for-user]. + +### Descubre los repositorios a los cuales tu app puede acceder para un usuario + +Adicionalmente a tener sus propios repositorios personales, un usuario puede ser un colaborador en los repositorios que pertenezcan a otros usuarios y organizaciones. En conjunto, estos son los repositorios en donde el usuario tiene acceso privilegiado: ya sea un repositorio privado en donde el usuario tiene acceso de lectura o escritura, o un repositorio público en donde el usuario tiene acceso de escritura. + +Los [alcances de OAuth][scopes] y las [políticas de aplicación de la organización][oap] determinan a cuáles de estos repositorios puede acceder tu app para un usuario. Utiliza el siguiente flujo de trabajo para descubrir estos repositorios. + +Como siempre, primero necesitaremos la biblioteca de Ruby del [Octokit.rb de GitHub][octokit.rb]. Luego, configuraremos a Octokit.rb para que nos gestione automáticamente la [paginación][pagination]. + +``` ruby +require 'octokit' + +Octokit.auto_paginate = true +``` + +Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación: + +``` ruby +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below. +client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"] +``` + +Luego estaremos listos para obtener los [repositorios a los cuales puede acceder nuestra aplicación para el usuario][list-repositories-for-current-user]: + +``` ruby +client.repositories.each do |repository| + full_name = repository[:full_name] + has_push_access = repository[:permissions][:push] + + access_type = if has_push_access + "write" + else + "read-only" + end + + puts "User has #{access_type} access to #{full_name}." +end +``` + +### Descubre las organizaciones a las cuales puede acceder tu app para un usuario + +Las aplicaciones pueden llevar a cabo todo tipo de tareas relacionadas con las organizaciones para un usuario. Para llevar a cabo estas tareas, la app necesita una [Autorización de OAuth][scopes] con permisos suficientes. Por ejemplo, el alcance `read:org` te permite [listar los equipos][list-teams], y el alcance `user` te permite [publicitar la membresía organizacional del usuario][publicize-membership]. Una vez que un usuario haya otorgado uno o más de estos alcances a tu app, estarás listo para obtener las organizaciones de éste. + +Tal como hicimos cuando descubrimos los repositorios anteriormente, comenzaremos requiriendo la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y configurándola para que se encarge de la [paginación][pagination] por nosotros: + +``` ruby +require 'octokit' + +Octokit.auto_paginate = true +``` + +Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación para inicializar nuestro cliente de la API: + +``` ruby +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below. +client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"] +``` + +Después, podremos [listar las organizaciones a las cuales tiene acceso nuestra aplicación para el usuario][list-orgs-for-current-user]: + +``` ruby +client.organizations.each do |organization| + puts "User belongs to the #{organization[:login]} organization." +end +``` + +#### No dependas de las organizaciones públicas + +Si leíste los documentos de principio a fin, tal vez hayas notado que hay un [Método de la API para listar las membrecías de organizaciones públicas de un usuario][list-public-orgs]. La mayoría de las aplicaciones deberían evitar este método de la API. Este método solo devuelve las membrecías de las organizaciones públicas del usuario y no sus membrecías de organizaciones privadas. + +Al fungir como una aplicación, habitualmente lo que buscas es todas las organizaciones del usuario (tanto públicas como privadas) en las cuales tu app tenga acceso autorizado. El flujo de trabajo anterior te proporcionará exactamente eso. + +[basics-of-authentication]: /rest/guides/basics-of-authentication +[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user +[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user +[list-teams]: /rest/reference/teams#list-teams +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests +[oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ +[octokit.rb]: https://github.com/octokit/octokit.rb +[octokit.rb]: https://github.com/octokit/octokit.rb +[pagination]: /rest#pagination +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user +[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user +[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app +[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md new file mode 100644 index 0000000000000..993c31147cb9d --- /dev/null +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md @@ -0,0 +1,75 @@ +--- +title: Empezar con la API de Verificaciones +intro: 'La API de Ejecuciones de Verificación te permite crear GitHub Apps que ejecuten verificaciones poderosas contra los cámbios de código en un repositorio. Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Resumen + +En vez de proporcionar estados de creación de pase/fallo, las GitHub Apps pueden reportar estados enriquecidos, anotar información detallada en las líneas de código y re-ejecutar las pruebas. La funcionalidad de la API de Verificaciones se encuentra disponible exclusivamente para tus GitHub Apps. + +Para obtener un ejemplo de cómo utilizar la API de Verificaciones con una {% data variables.product.prodname_github_app %}, consulta la sección "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)". + +### Acerca de las suites de verificaciones + +Cuando alguien carga código a un repositorio, GitHub crea una suite de verificación para la última confirmación. Una suite de verificación es un conjunto de [ejecuciones de verificación](/rest/reference/checks#check-runs) que crea una sola GitHub App para una confirmación específica. Las suites de Verificación resumen el estado y la conclusión de la ejecución de verificación que incluye dicha suite. + +![Flujo de trabajo de las suites de verificación](/assets/images/check_suites.png) + +La suite de verificación reporta la `conclusion` de la ejecución de verificación con la prioridad más alta en `conclusion` de la suite de verificación. Por ejemplo, si tres ejecuciones de verificación tienen conclusiones de `timed_out`, `success`, y `neutral`, la conclusión de la suite de verificación será `timed_out`. + +Predeterminadamente, GitHub crea una suite de verificación automáticamente cuando se carga el código al repositorio. Este flujo predeterminado evía el evento `check_suite` (con la acción `requested`) a todas las GitHub Apps que tengan el permiso de `checks:write`. Cuando tu GitHub App recibe el evento `check_suite`, esta púede crear ejecuciones de verificación nuevas para la última confirmación. GitHub agrega las ejecuciones de verificación nuevas a la [suite de verificación](/rest/reference/checks#check-suites) correcta con base en el repositorio y SHA de dicha ejecución de verificación. + +Si no quieres utilizar el flujo automático predeterminado, puedes controlar cuando creas las suites de verificación. Para cambiar la configuración predeterminada para la creación de suites de verificación, utiliza la terminal [Actualizar las preferencias del repositorio para las suites de verificación](/rest/reference/checks#update-repository-preferences-for-check-suites). Todos los cambios que se realicen en la configuración del flujo automático se registran en la bitácora de auditoría del repositorio. Si inhabilitaste el flujo automático, puedes crear una suite de verificación utilizando la terminal [Crear una suite de verificación](/rest/reference/checks#create-a-check-suite). Debes seguir utilizando la terminal [Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run) para proporcionar retroalimentación sobre una confirmación. + +{% data reusables.apps.checks-availability %} + +Para utilizar la API de suites de verificación, la GitHub App debe tener el permiso de `checks:write` y también suscribirse al webhook de [check_suite](/webhooks/event-payloads/#check_suite). + +{% data reusables.shortdesc.authenticating_github_app %} + +### Acerca de las ejecuciones de verificación + +Una ejecución de verificación es una prueba individual que forma parte de una suite de verificación. Cada ejecución incluye un estado y una conclusión. + +![Flujo de trabajo de las ejecuciones de verificación](/assets/images/check_runs.png) + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +Si una ejecución de verificación permanece en un estado incompleto por más de 14 días, entonces las `conclusion` de dicha ejecución se convierten en `stale` y aparecen en +{% data variables.product.prodname_dotcom %} como quedadas con el {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Solo {% data variables.product.prodname_dotcom %} puede marcar las ejecuciones de verificación como `stale`. Para obtener más información acerca de las conclusiones posibles para una ejecución de verificación, consulta el [parámetro de `conclusion`](/rest/reference/checks#create-a-check-run--parameters). +{% endif %} + +Puedes crear la ejecución de verificación tan pronto como recibas el webhook de [`check_suite`](/webhooks/event-payloads/#check_suite), aún si ésta todavía no se completa. Puedes actualizar el `status` de la ejecución de verificación ya que se completa con los valores `queued`, `in_progress`, o `completed`, y puedes actualizar la `output` conforme vayan estando disponibles los detalles adicionales. Una ejecución de verificación puede contener estampas de tiempo, un enlace para encontrar más detalles en tu sitio externo, anotaciones detalladas para líneas de código específcas, e información acerca del análisis que se llevó a cabo. + +![Anotaciones de la ejecución de verificación](/assets/images/check_run_annotations.png) + +Una verificación también puede volverse a ejecutar en la IU de GitHub. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles. Cuando esto ocurre, la GitHub App que creó la ejecución de verificación recibirá el webhook [`check_run`](/webhooks/event-payloads/#check_run) que solicita una ejecución de verificación nueva. Si creas una ejecución de verificación sin crear una suite de verificación, GitHub la creará para tí automáticamente. + +{% data reusables.apps.checks-availability %} + +Para utilizar la API de Ejecuciones de Verificación, la GitHub App debe tener el permiso de `checks:write` y también debe poder suscribirse al webhook de [check_run](/webhooks/event-payloads#check_run). + +### Ejecuciones de verificación y acciones solicitadas + +Cuando configuras una ejecución de verificación con las acciones solicitadas (no se debe confundir esto con {% data variables.product.prodname_actions %}), puedes mostrar un botón en la vista de la solicitud de extracción en {% data variables.product.prodname_dotcom %} que permita a las personas solicitar tu {% data variables.product.prodname_github_app %} para llevar a cabo tareas adicionales. + +Por ejemplo, una app de limpieza de código puede utilizar las acciones solicitadas para mostrar un botón en una solicitud de extracción para arreglar automáticamente los errores de sintaxis detectados. + +Para crear un botón que pueda solicitarle a tu app acciones adicionales, utiliza el [objeto`actions`](/rest/reference/checks#create-a-check-run--parameters) cuando [Creas una ejecución de verificación](/rest/reference/checks/#create-a-check-run). Por ejemplo, el objeto `actions` que se muestra a continuación muestra un botón en una solicitud de extracción con la etiqueta "Fix This". El botón aparece después de que se completa la ejecución de verificación. + + ```json + "actions": [{ + "label": "Fix this", + "description": "Let us fix that for you", + "identifier": "fix_errors" + }] + ``` + + ![Botón de acción solicitada para la ejecución de verificación](/assets/images/github-apps/github_apps_checks_fix_this_button.png) + +Cuando un usuario da clic en el botón, {% data variables.product.prodname_dotcom %} envía el [webhook de `check_run.requested_action`](/webhooks/event-payloads/#check_run) a tu app. Cuando tu app recibe el evento de webhook de `check_run.requested_action`, este puede buscar la clave de `requested_action.identifier` en la carga útil del webhook para determinar qué botón se pulsó y llevar a cabo la tarea solicitada. + +Para obtener un ejemplo detallado de cómo configurar las acciones solicitadas con la API de Verificaciones, consulta la sección "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/#part-2-creating-the-octo-rubocop-ci-test)". diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-git-database-api.md new file mode 100644 index 0000000000000..f28bc2f5a8e86 --- /dev/null +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-git-database-api.md @@ -0,0 +1,46 @@ +--- +title: Comenzar con la API de la Base de Datos de Git +intro: 'La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas).' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Resumen + +Básicamente, esto te permite volver a implementar muchas de las funcionalidades de Git sobre nuestra API mediante la creación de objetos sin procesar (raw) directamente en la base de datos y actualizando las referencias de rama que técnicamente podrían hacer todo lo que pueda hacer Git sin que se éste se instale. + +La API de la Base de Datos de Git devolverá un `409 Conflict` si el repositorio de Git está vacío o no disponible. Que un repositorio se muestre como no disponible habitualmente significa que {% data variables.product.product_name %} está en el proceso de crearlo. Para los casos de repositorios vacíos, puedes utilizar la terminal "[Crear o actualizar el contenido de un archivo](/rest/reference/repos#create-or-update-file-contents)" para crear contenido e inicializar el repositorio para que puedas utilizar la API de la Base de Datos de Git. Contacta a {% data variables.contact.contact_support %} si este estado de respuesta persiste. + +![resumen de la base de datos de git](/assets/images/git-database-overview.png) + +Para obtener más información sobre la base de datos de objetos de Git, por favor lee el capítulo [Internos de Git](http://git-scm.com/book/en/v1/Git-Internals) en el libro Pro de Git. + +Como ejemplo, si quieres confirmar un cambio en un archivo de tu repositorio, lo que harías es: + +* Obtener el objeto de la confirmación actual +* Recuperar el árbol al cual apunta +* Recuperar el contenido del objeto del blob que tiene el árbol para esa ruta de archivo en particular +* Cambiar el contenido de alguna manera y publicar un objeto de blob nuevo con este contenido nuevo, obteniendo el SHA del blob a cambio +* Publicar un nuevo objeto de árbol con ese indicador de la ruta del archivo reemplazándolo con el SHA de tu blob nuevo y obteniendo a cambio el SHA del árbol +* Crear un objeo de confirmación nuevo con el SHA de la confirmación actual como el padre y el SHA del árbol nuevo, obteniendo a cambio el SHA de la confirmación +* Actualizar la referencia de tu rama para apuntar al nuevo SHA de la confirmación + +Puede que parezca complejo, pero en realidad es bastante simple cuando entiendes el modelo y te proporciona la oportunidad de hacer un sin fin de cosas cuando lo haces potencialmente con la API. + +### Verificar la capacidad de fusión de las solicitudes de extracción + +{% warning %} + +**¡Advertencia!** Por favor no dependas de utilizar git directamente o de utilizar [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) para las actualizaciones a las referencias de Git de tipo `merge`, ya que este contenido se desactualiza sin aviso previo. + +{% endwarning %} + +Una API consumible debe solicitar explícitamente que una solicitud de extracción cree una confirmación de fusión de _prueba_. Una confirmación de fusión de _prueba_ se crea cuando ves la solicitud de extracción en la IU y cuando se muestra el botón de "Fusionar", o cuando [obtienes](/rest/reference/pulls#get-a-pull-request), [creas](/rest/reference/pulls#create-a-pull-request), o [editas](/rest/reference/pulls#update-a-pull-request) una solicitud de extracción utilizando la API de REST. Sin esta solicitud, las Referencias de Git para `merge` se harán obsoletas hasta la próxima vez que alguien vea la solicitud de extracción. + +Si actualmente utilizas métodos de sondeo que produzcan referencias de Git de tipo `merge` descatualizadas, entonces GitHub te recomienda utilizar los siguientes pasos para obtener los últimos cambios de la rama predeterminada: + +1. Recibir el webhook de la solicitud de extracción. +2. Llamar a [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) para iniciar un job en segundo plano para crear el candidato de la confirmación de fusión. +3. Sondear tu repositorio utilizando [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) para ver si el atributo `mergeable` está como `true` o como `false`. Puedes utilizar Git directamente o referencias de Git de tipo [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) for updates to `merge` únicamente después de haber llevado a cabo los siguientes pasos. diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md new file mode 100644 index 0000000000000..9a061f444b70a --- /dev/null +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md @@ -0,0 +1,400 @@ +--- +title: Iniciar con la API de REST +intro: 'Aprende las bases para utilizar la API de REST, comenzando con la autenticación y algunos ejemplos de las terminales.' +redirect_from: + - /guides/getting-started/ + - /v3/guides/getting-started +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Vamos a explicar los conceptos centrales de la API mientras incluímos algunos casos de uso cotidiano. + +### Resumen + +La mayoría de las aplicaciones utilizan una [biblioteca de seguridad][wrappers] en el lenguaje de programación que escojas, pero es importante que te familiarices con los métodos HTTP básicos de la API primero. + +No hay forma más fácil de probar la mercancía que a través de [cURL][curl].{% if currentVersion == "free-pro-team@latest" %} Si estás utilizando un cliente alterno, nota que se requiere que envíes un [Encabezado de agente de usuario](/rest/overview/resources-in-the-rest-api#user-agent-required) en tu solicitud.{% endif %} + +#### Hola Mundo + +Comencemos por probar nuestra configuración. Abre una instancia de la línea de comandos e ingresa el siguiente comando: + +```shell +$ curl https://api.github.com/zen + +> Keep it logically awesome. +``` + +La respuesta será una selección aleatoria de nuestra filosofía de diseño. + +Posteriormente, vamos a hacer `GET` para el [perfil de GitHub][users api] de [Chris Wanstrath][defunkt github]: + +```shell +# GET /users/defunkt +$ curl https://api.github.com/users/defunkt + +> { +> "login": "defunkt", +> "id": 2, +> "url": "{% data variables.product.api_url_pre %}/users/defunkt", +> "html_url": "https://github.com/defunkt", +> ... +> } +``` + +Mmmm, sabe a [JSON][json]. Vamos a agregar el marcador `-i` para que incluya los encabezados: + +```shell +$ curl -i https://api.github.com/users/defunkt + +> HTTP/1.1 200 OK +> Server: GitHub.com +> Date: Sun, 11 Nov 2012 18:43:28 GMT +> Content-Type: application/json; charset=utf-8 +> Status: 200 OK +> ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6" +> X-RateLimit-Limit: 60 +> X-RateLimit-Remaining: 57 +> X-RateLimit-Reset: 1352660008 +> X-GitHub-Media-Type: github.v3 +> Vary: Accept +> Cache-Control: public, max-age=60, s-maxage=60 +> X-Content-Type-Options: nosniff +> Content-Length: 692 +> Last-Modified: Tue, 30 Oct 2012 18:58:42 GMT + +> { +> "login": "defunkt", +> "id": 2, +> "url": "{% data variables.product.api_url_pre %}/users/defunkt", +> "html_url": "https://github.com/defunkt", +> ... +> } +``` + +Hay algunas partes interesantes en los encabezados de la respuesta. Como lo esperábamos, el `Content-Type` es `application/json`. + +Cualquier encabezado que comience como `X` se refiere a un encabezado personalizado, y no se incluirá en la especificación de HTTPS. Por ejemplo: + +* `X-GitHub-Media-Type` tiene un valor de `github.v3`. Esto nos permite saber el [tipo de medios][media types] para la respuesta. Los tipos de medios nos han ayudado a versionar nuestra salida en la API v3. Hablaremos más sobre esto después. +* Toma nota de los encabezados `X-RateLimit-Limit` y `X-RateLimit-Remaining`. Este par de encabezados indica [cuántas solicitudes puede hacer un cliente][rate-limiting] en un periodo de tiempo consecutivo (habitualmente una hora) y cuántas de estas solicitudes ha gastado el cliente hasta ahora. + +### Autenticación + +Los clientes sin autenticar pueden hacer hasta 60 solicitudes por hora. Para obtener más solicitudes por hora, necesitaremos _autenticarnos_. De hecho, necesitaremos la [autenticación][authentication] para hacer cualquier cosa interesante con la API de {% data variables.product.product_name %}. + +#### Utilizar tokens de acceso personal + +La mejor y más fácil forma de autenticarse con la API de {% data variables.product.product_name %} es utilizando la Autenticación Básica [a través de los tokens de OAuth](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). Éstos incluyen [tokens de acceso personal][personal token]. + +Utiliza el marcador `-u` para configurar tu nombre de usuario: + +```shell +$ curl -i -u your_username {% data variables.product.api_url_pre %}/users/octocat + +``` + +Cuando se te solicite, puedes ingresar tu token de OAuth, pero te recomendamos que configures una variable para éste: + +Puedes utilizar `-u "username:$token"` y configurar una variable para `token` y así evitar el dejar tu token en el historial del shell, lo cual debe evitarse. + +```shell +$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat + +``` + +Cuando te autentiques, debes ver como tu límite de tasa sube hasta 5,000 solicitudes por hora, como se indicó en el encabezado `X-RateLimit-Limit`. Adicionalmente a proporcionar más llamadas por hora, la autenticación te permite leer y escribir información privada utilizando la API. + +Puedes [crear un**token de acceso personal**][personal token] fácilmente utilizando tu [página de configuración para tokens de acceso personal][tokens settings]: + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +![Selección de token personal](/assets/images/personal_token.png) +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +![Selección de token personal](/assets/images/help/personal_token_ghae.png) +{% endif %} + +#### Obtén tu propio perfil de usuario + +Cuando te autenticas adecuadamente, puedes sacar provecho de los permisos asociados con tu cuenta de {% data variables.product.product_name %}. Por ejemplo, intenta obtener + +```shell +$ curl -i -u your_username:your_token {% data variables.product.api_url_pre %}/user + +> { +> ... +> "plan": { +> "space": 2516582, +> "collaborators": 10, +> "private_repos": 20, +> "name": "medium" +> } +> ... +> } +``` + +Esta vez, adicionalmente al mismo conjunto de información pública que recuperamos antes para [@defunkt][defunkt github], deberías ver también la información no pública para tu perfil de usuario. Por ejemplo, verás un objeto de `plan` en la respuesta, el cuál proporciona detalles sobre el plan de {% data variables.product.product_name %} de la cuenta. + +#### Utiilzar tokens de OAuth para las apps + +Las apps que necesitan leer o escribir información privada utilizando la API en nombre de otro usuario deben utilizar [OAuth][oauth]. + +OAuth utiliza _tokens_. Los Tokens proporcionan dos características grandes: + +* **Acceso revocable**: los usuarios pueden revocar la autorización a las apps de terceros en cualquier momento +* **Acceso limitado**: los usuarios pueden revisar el acceso específico que proporcionará un token antes de autorizar una app de terceros + +Los tokens deben crearse mediante un [flujo web][webflow]. Una aplicación envía a los usuarios a {% data variables.product.product_name %} para que inicien sesión. Entonces, {% data variables.product.product_name %} presenta un diálogo que indica el nombre de la app así como el nivel de acceso que ésta tiene una vez que el usuario la autorice. Después de que un usuario autoriza el acceso, {% data variables.product.product_name %} lo redirecciona de vuelta a la aplicación: + +![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png) + +**¡Trata a los tokens de OAuth como si fueran contraseñas!** No los compartas con otros usuarios ni los almacenes en lugares inseguros. Los tokens en estos ejemplos son falsos y los nombres se cambiaron para proteger a los inocentes. + +Ahora que ya entendimos cómo hacer llamadas autenticadas, vamos a pasar a la [API de repositorios][repos-api]. + +### Repositorios + +Casi cualquier uso significativo de la API de {% data variables.product.product_name %} involucra algún nivel de información de un repositorio. Podemos hacer [`GET` para los detalles de un repositorio][get repo] de la misma forma que recuperamos los detalles del usuario anteriormente: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap +``` + +De la misma forma, podemos [ver los repositorios del usuario autenticado][user repos api]: + +```shell +$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ + {% data variables.product.api_url_pre %}/user/repos +``` + +O podemos [listar los repositorios de otro usuario][other user repos api]: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos +``` + +O podemos [listar los repositorios de una organización][org repos api]: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos +``` + +La información que se devuelve de estas llamadas dependerá de los alcances que tenga nuestrotoken cuando nos autenticamos: + +* Un token con el [alcance][scopes] de `public_repo` devolverá una respuesta que incluya todos los repositorios públicos a los cuales tenemos acceso de visualización en github.com. +* Un token con [scope][scopes] de `repo` devuelve una respuesta que incluye a todos los repositorios públicos y privados a los que tenemos acceso para ver en github.com. + +Como indican los [docs][repos-api], estos métodos toman un parámetro de `type` que puede filtrar los repositorios que se regresan con base en el tipo de acceso que el usuario tiene en ellos. De esta forma, podemos obtener los solo los repositorios que nos pertenezcan directamente, repositorios de organizacion o repositorios en los que el usuario colabore a través del equipo. + +```shell +$ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner" +``` + +En este ejemplo, tomamos únicamente los repositorios que pertenecen a octocat, no aquellos en los que ella colabora. Nota la URL que se cita arriba. Dependiendo de tu configuración de shell, cURL a veces requiere una URL citada, o de lo contrario ignora la secuencia de consulta. + +#### Crear un repositorio + +Un caso de común de uso es retribuir información para repositorios existentes, pero la +API de {% data variables.product.product_name %} es compatible con la creación de repositorios nuevos también. Para [crear un repositorio][create repo], +necesitamos hacer `POST` en algunos JSON que contengan los detalles y las opciones de configuración. + +```shell +$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ + -d '{ \ + "name": "blog", \ + "auto_init": true, \ + "private": true, \ + "gitignore_template": "nanoc" \ + }' \ + {% data variables.product.api_url_pre %}/user/repos +``` + +En este ejemplo mínimo, creamos un repositorio nuevo para nuestro blog (que se servirá en [GitHub Pages][pages], probablemente). Aunque el blog será público, lo hemos hecho privado. En este paso único, también lo inicializamos con un README y con una [plantilla de.gitignore][gitignore templates] aderezada con [nanoc][nanoc]. + +El repositorio que se obtiene como resultado se puede encontrar en `https://github.com//blog`. Para crear un repositorio bajo una organización para la cual eres propietario, solo cambia el método de la API de `/user/repos` a `/orgs//repos`. + +Posteriormente vamos a obtener nuestro repositorio recién creado: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog + +> HTTP/1.1 404 Not Found + +> { +> "message": "Not Found" +> } +``` + +¡Oh no! ¿A dónde se fue? Ya que creamos el repositorio como _privado_, necesitamos autenticarnos para poder verlo. Si eres un usuario experimentado en HTTP, tal vez esperes recibir un código `403` en vez de ésto. Ya que no queremos filtrar información acerca de los repositorios privados, la API de {% data variables.product.product_name %} devuelve un código `404` en este caso, como diciendo "no podemos confirmar ni negar la existencia de este repositorio". + +### Problemas + +La IU de informe de problemas en {% data variables.product.product_name %} pretende proporcionar suficiente flujo de trabajo mientras evita estorbarte. Con la [API de Informes de Problemas][issues-api] de {% data variables.product.product_name %}, puedes extraer datos para crear informes de problemas desde otras herramientas para crear flujos de trabajo que funcionan para tu equipo. + +Tal como en github.com, la API proporciona algunos cuantos métodos para ver los informes de problemas para el usuario autenticado. Para [ver todos tus informes de problemas][get issues api], llama a `GET /issues`: + +```shell +$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ + {% data variables.product.api_url_pre %}/issues +``` + +Para obtener únicamente los [informes de problemas bajo alguna de tus organizaciones de {% data variables.product.product_name %}][get issues api], llama a `GET +/orgs//issues`: + +```shell +$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ + {% data variables.product.api_url_pre %}/orgs/rails/issues +``` + +También podemos obtener [todos los informes de problemas que estén bajo un solo repositorio][repo issues api]: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues +``` + +#### Paginación + +Un proyecto con el tamaño de Rails tiene miles de informes de problemas. Necesitaremos [paginar][pagination], haciendo varias llamadas a la API para obtener los datos. Vamos a repetir la última llamada, esta vez tomando nota de los encabezados de respuesta: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues + +> HTTP/1.1 200 OK + +> ... +> Link: <{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2>; rel="next", <{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30>; rel="last" +> ... +``` + +El [encabezado de code>Link][link-header] proporciona una respuesta para enlazar a los recursos externos, en este caso, a las páginas de datos adicionales. Ya que nuestra llamada encontró más de treinta informes de problemas (el tamaño predeterminado de página), la API no s dice dónde podemos encontrar la siguiente página y la última página de los resultados. + +#### Crear una propuesta + +Ahora que hemos visto cómo paginar las listas de informes de problemas, vamos a [crear un informe de problemas][create issue] desde la API. + +Para crear un informe de problemas, necesitamos estar autenticados, así que pasaremos un token de OAuth en el encabezado. También, pasaremos el título, cuerpo, y etiquetas en el cuerpo de JSON a la ruta `/issues` debajo del repositorio en el cual queremos crear el informe de problemas: + +```shell +$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ -d '{ \ +$ "title": "New logo", \ +$ "body": "We should have one", \ +$ "labels": ["design"] \ +$ }' \ +$ {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues + +> HTTP/1.1 201 Created +> Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17 +> X-RateLimit-Limit: 5000 + +> { +> "pull_request": { +> "patch_url": null, +> "html_url": null, +> "diff_url": null +> }, +> "created_at": "2012-11-14T15:25:33Z", +> "comments": 0, +> "milestone": null, +> "title": "New logo", +> "body": "We should have one", +> "user": { +> "login": "pengwynn", +> "gravatar_id": "7e19cd5486b5d6dc1ef90e671ba52ae0", +> "avatar_url": "https://secure.gravatar.com/avatar/7e19cd5486b5d6dc1ef90e671ba52ae0?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-user-420.png", +> "id": 865, +> "url": "{% data variables.product.api_url_pre %}/users/pengwynn" +> }, +> "closed_at": null, +> "updated_at": "2012-11-14T15:25:33Z", +> "number": 17, +> "closed_by": null, +> "html_url": "https://github.com/pengwynn/api-sandbox/issues/17", +> "labels": [ +> { +> "color": "ededed", +> "name": "design", +> "url": "{% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/labels/design" +> } +> ], +> "id": 8356941, +> "assignee": null, +> "state": "open", +> "url": "{% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17" +> } +``` + +La respuesta nos entrega un par de sugerencias para el informe de problemas recién creado, tanto en el encabezado de respuesta de `Location` como en el campo de `url` de la respuesta de JSON. + +### Solicitudes condicionales + +Una gran parte de ser un buen ciudadano de la API es respetar los límites de tasa al almacenar información en el caché, la cual no haya cambiado. La API es compatible con las [solicitudes condicionales][conditional-requests] y te ayuda a hacer lo correcto. Considera el primer llamado que hicimos para obtener el perfil de defunkt: + +```shell +$ curl -i {% data variables.product.api_url_pre %}/users/defunkt + +> HTTP/1.1 200 OK +> ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6" +``` + +Además del cuerpo de JSON, toma nota del código de estado HTTP de `200` y del encabezado `ETag`. La [ETag][etag] es una huella digital de la respuesta. Si la pasamos en llamadas subsecuentes, podemos decirle a la API que nos entregue el recurso nuevamente, únicamente si cambió: + +```shell +$ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \ +$ {% data variables.product.api_url_pre %}/users/defunkt + +> HTTP/1.1 304 Not Modified +``` + +El estado `304` indica que el recurso no ha cambiado desde la última vez que lo solicitamos y que la respuesta no contendrá ningún cuerpo. Como bonificación, las respuestas `304` no contarán para tu [límite de tasa][rate-limiting]. + +¡Qué! ¡Ahora sabes los fundamentos de la API de {% data variables.product.product_name %}! + +* Autenticación básica & de OAuth +* Obtener y crear repositorios e informes de problemas +* Solicitudes condicionales + +Sigue aprendiendo con la siguiente guía de la API ¡[Fundamentos de la Autenticación][auth guide]! + +[wrappers]: /libraries/ +[curl]: http://curl.haxx.se/ +[media types]: /rest/overview/media-types +[oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ +[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ +[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[repos-api]: /rest/reference/repos +[repos-api]: /rest/reference/repos +[pages]: http://pages.github.com +[nanoc]: http://nanoc.ws/ +[gitignore templates]: https://github.com/github/gitignore +[issues-api]: /rest/reference/issues +[link-header]: https://www.w3.org/wiki/LinkHeader +[conditional-requests]: /rest#conditional-requests +[rate-limiting]: /rest#rate-limiting +[rate-limiting]: /rest#rate-limiting +[users api]: /rest/reference/users#get-a-user +[defunkt github]: https://github.com/defunkt +[defunkt github]: https://github.com/defunkt +[json]: http://en.wikipedia.org/wiki/JSON +[authentication]: /rest#authentication +[personal token]: /articles/creating-an-access-token-for-command-line-use +[personal token]: /articles/creating-an-access-token-for-command-line-use +[tokens settings]: https://github.com/settings/tokens +[pagination]: /rest#pagination +[get repo]: /rest/reference/repos#get-a-repository +[create repo]: /rest/reference/repos#create-a-repository-for-the-authenticated-user +[create issue]: /rest/reference/issues#create-an-issue +[auth guide]: /guides/basics-of-authentication +[user repos api]: /rest/reference/repos#list-repositories-for-the-authenticated-user +[other user repos api]: /rest/reference/repos#list-repositories-for-a-user +[org repos api]: /rest/reference/repos#list-organization-repositories +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user +[repo issues api]: /rest/reference/issues#list-repository-issues +[etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/es-ES/content/rest/guides/index.md b/translations/es-ES/content/rest/guides/index.md new file mode 100644 index 0000000000000..afbb15d786699 --- /dev/null +++ b/translations/es-ES/content/rest/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Guías +intro: 'Aprende como empezar con la API de REST, cómo funciona la autenticación, o cómo utilizar la API de REST para tareas diveras.' +redirect_from: + - /guides/ + - /v3/guides +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La intención de esta sección de documentos es que comiences a operar tan pronto como sea posible con aplicaciones de la API de {% data variables.product.product_name %} reales. Abordaremos todo lo que necesitas saber, desde la autenticación, hasta manipular los resultados, e incluso hasta combiar los resultados con otras apps. + +Cada tutorial en esta sección tendrá un proyecto, y cada proyecto se almacenará y documentará en nuestro repositorio público de [platform-samples](https://github.com/github/platform-samples). + +![El Electrocat](/assets/images/electrocat.png) + +### Índice + +{% link_in_list /getting-started-with-the-rest-api %} +{% link_in_list /basics-of-authentication %} +{% link_in_list /discovering-resources-for-a-user %} +{% link_in_list /delivering-deployments %} +{% link_in_list /rendering-data-as-graphs %} +{% link_in_list /working-with-comments %} +{% link_in_list /traversing-with-pagination %} +{% link_in_list /building-a-ci-server %} +{% link_in_list /best-practices-for-integrators %} +{% link_in_list /getting-started-with-the-git-database-api %} +{% link_in_list /getting-started-with-the-checks-api %} diff --git a/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md b/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md new file mode 100644 index 0000000000000..6f155be8593cd --- /dev/null +++ b/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md @@ -0,0 +1,339 @@ +--- +title: Representar los datos en gráficas +intro: Aprende a visualizar los lenguajes de programación de tu repositorio utilizando la biblioteca D3.js y el Octokit de Ruby. +redirect_from: + - /guides/rendering-data-as-graphs/ + - /v3/guides/rendering-data-as-graphs +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +En esta guía vamos a utilizar la API para obtener información acerca de los repositorios que nos pertenecen y de los lenguajes de programación que los componen. Luego, vamos a visualizar la información en un par de formas diferentes utilizando la librería [D3.js][D3.js]. Para interactuar con la API de {% data variables.product.product_name %}, estaremos utilizando la excelente biblioteca de Ruby, [Octokit][Octokit]. + +Si aún no lo has hecho, deberías leer la guía de ["Fundamentos de la Autenticación"][basics-of-authentication] antes de comenzar con este ejemplo. Puedes encontrar el código fuente completo para este proyecto en el repositorio [platform-samples][platform samples]. + +¡Comencemos de inmediato! + +### Configurar una aplicación de OAuth + +Primero, [registra una aplicación nueva][new oauth application] en {% data variables.product.product_name %}. Configura la URL principal y la de rellamado como `http://localhost:4567/`. Tal como lo hemos hecho [antes][basics-of-authentication], vamos a gestionar la autenticación para la API implementando un recurso intermedio de Rack utilizando [sinatra-auth-github][sinatra auth github]: + +``` ruby +require 'sinatra/auth/github' + +module Example + class MyGraphApp < Sinatra::Base + # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! + # Instead, set and test environment variables, like below + # if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET'] + # CLIENT_ID = ENV['GITHUB_CLIENT_ID'] + # CLIENT_SECRET = ENV['GITHUB_CLIENT_SECRET'] + # end + + CLIENT_ID = ENV['GH_GRAPH_CLIENT_ID'] + CLIENT_SECRET = ENV['GH_GRAPH_SECRET_ID'] + + enable :sessions + + set :github_options, { + :scopes => "repo", + :secret => CLIENT_SECRET, + :client_id => CLIENT_ID, + :callback_url => "/" + } + + register Sinatra::Auth::Github + + get '/' do + if !authenticated? + authenticate! + else + access_token = github_user["token"] + end + end + end +end +``` + +Configura un archivo similar de _config.ru_ como en el ejemplo previo: + +``` ruby +ENV['RACK_ENV'] ||= 'development' +require "rubygems" +require "bundler/setup" + +require File.expand_path(File.join(File.dirname(__FILE__), 'server')) + +run Example::MyGraphApp +``` + +### Obtener la información del repositorio + +En esta ocasión, para poder hablar con la API de {% data variables.product.product_name %}, vamos a utilizar la [Biblioteca de Ruby, Octokit][Octokit]. Esto es mucho más fácil que hacer un montón de llamadas de REST directamente. Además, un Githubber desarrolló Octokit, y se mantiene activamente, así que sabes que funcionará. + +Autenticarse con la API a través de Octokit es fácil. Solo pasa tu información de inicio de sesión y tu token en el constructor `Octokit::Client`: + +``` ruby +if !authenticated? + authenticate! +else + octokit_client = Octokit::Client.new(:login => github_user.login, :oauth_token => github_user.token) +end +``` + +Vamos a hacer algo interesante con los datos acerca de nuestros repositorios. Vamos a ver los diferentes lenguajes de programación que utilizan y a contar cuáles se utilizan más a menudo. Para hacerlo, primero necesitamos tomar una lista de nuestros repositorios desde la API. Con Octokit, esto se ve así: + +``` ruby +repos = client.repositories +``` + +Después, vamos a iterar sobre cada repositorio y a contar los lenguajes con los que {% data variables.product.product_name %} los asocia: + +``` ruby +language_obj = {} +repos.each do |repo| + # sometimes language can be nil + if repo.language + if !language_obj[repo.language] + language_obj[repo.language] = 1 + else + language_obj[repo.language] += 1 + end + end +end + +languages.to_s +``` + +Cuando reinicias tu servidor, tu página web debe mostrar más o menos esto: + +``` ruby +{"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1} +``` + +Hasta ahora vamos bien, pero no se ve muy amigable para un humano. Sería genial poder tener algún tipo de visualización para entender cómo se distribuye este conteo de lenguajes. Vamos a alimentar a D3 con nuestros conteos para obtener una gráfica de barras clara que represente la popularidad de los lenguajes que utilizamos. + +### Visualizar los conteos de los lenguajes + +D3.js, o simplemente D3, es una biblioteca completa para crear muchos tipos de gráficos, tablas, y visualizaciones interactivas. El utilizarlo a detalle va más allá del alcance de esta guía, pero para ver un buen artículo introductorio al respecto, revisa ["D3 para mortales"][D3 mortals]. + +D3 es una biblioteca de JavaScript a la que le gusta trabajar con matrices de datos. Así que, vamos a convertir a nuestro hash de Ruby en una matriz de JSON para que JavaScript la utilice en el buscador. + +``` ruby +languages = [] +language_obj.each do |lang, count| + languages.push :language => lang, :count => count +end + +erb :lang_freq, :locals => { :languages => languages.to_json} +``` + +Simplemente estamos iterando sobre cada par de clave-valor en nuestro objeto y lo estamos cargando en una matriz nueva. La razón por la cual no lo hicimos antes es porque no queríamos iterar sobre nuestro objeto de `language_obj` mientras lo estábamos creando. + +Ahora, _lang_freq.erb_ va a necesitar algo de JavaScript para apoyar a que se interprete una gráfica de barras. Por ahora, puedes simplemente utilizar el código que se te proporciona aquí y referirte a los recursos cuyo enlace se señala anteriormente si quieres aprender más sobre cómo funciona D3: + +``` html + + + + + + + + +

Check this sweet data out:

+
+ + + + +``` + +¡Uf! Nuevamente, no te preocupes de la mayoría de lo que está haciendo este código. La parte relevante es lo que está hasta arriba--`var data = <%= languages %>;`--lo cual indica que estamos pasando nuestra matriz previamente creada de `languages` en el ERB para su manipulación. + +Tal como sugiere la guía de "D3 para Mortales", esto no es necesariamente la mejor forma de utilizar D3. Pero nos sirve para ilustrar cómo puedes utilizar la biblioteca, junto con Octokit, para hacer algunas cosas verdaderamente increíbles. + +### Combinar las diferentes llamadas de la API + +Ahora es el momento de hacer una confesión: el atributo de `language` dentro de los repositorios solo identifica el lenguaje "primario" que se definió. Esto significa que, si tienes un repositorio que combine varios lenguajes, el que tenga más bytes de código se considera comoel primario. + +Vamos a combinar algunas llamadas a la API para obtener una representación _fidedigna_ de qué lenguaje tiene la mayor cantidad de bytes escritos en todo nuestro código. Un [diagrama de árbol][D3 treemap] deberá ser la mejor forma de visualizar los tamaños de los lenguajes de código que utilizamos, en vez de obtener solo el conteo. Necesitaremos construir una matriz de objetos que se vea más o menos así: + +``` json +[ { "name": "language1", "size": 100}, + { "name": "language2", "size": 23} + ... +] +``` + +Como ya tenemos una lista de repositorios anteriormente, vamos a inspeccionar cada uno y a llamar al [método de la API para listar los lenguajes][language API]: + +``` ruby +repos.each do |repo| + repo_name = repo.name + repo_langs = octokit_client.languages("#{github_user.login}/#{repo_name}") +end +``` + +Desde aquí, agregaremos en una lista acumulativa cada lenguaje que encontremos: + +``` ruby +repo_langs.each do |lang, count| + if !language_obj[lang] + language_obj[lang] = count + else + language_obj[lang] += count + end +end +``` + +Después de ésto, daremos formato al contenido en una estructura que entienda el D3: + +``` ruby +language_obj.each do |lang, count| + language_byte_count.push :name => "#{lang} (#{count})", :count => count +end + +# some mandatory formatting for D3 +language_bytes = [ :name => "language_bytes", :elements => language_byte_count] +``` + +(Para obtener más información sobre la magia del diagrama de árbo del D3, échale un vistazo a [este tutorial sencillo][language API].) + +Para concluir, pasamos la información de JSON a la misma plantilla de ERB: + +``` ruby +erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json} +``` + +Como antes, hay mucho JavaScript que puedes dejar directamente en tu plantilla: + +``` html +
+ +``` + +¡Y voilá! Hermosos rectángulos que contienen los lenguajes de tu repositorio con proporciones relativas que se pueden ver inmediatamente. Tal vez necesites modificar la altura y el ancho de tu diagrama de árbol para pasarlo como los primeros dos argumentos en el `drawTreemap` anterior y así lograr que se muestre adecuadamente toda la información. + + +[D3.js]: http://d3js.org/ +[basics-of-authentication]: /rest/guides/basics-of-authentication +[basics-of-authentication]: /rest/guides/basics-of-authentication +[sinatra auth github]: https://github.com/atmos/sinatra_auth_github +[Octokit]: https://github.com/octokit/octokit.rb +[Octokit]: https://github.com/octokit/octokit.rb +[D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ +[D3 treemap]: http://bl.ocks.org/mbostock/4063582 +[language API]: /rest/reference/repos#list-repository-languages +[language API]: /rest/reference/repos#list-repository-languages +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs +[new oauth application]: https://github.com/settings/applications/new diff --git a/translations/es-ES/content/rest/guides/traversing-with-pagination.md b/translations/es-ES/content/rest/guides/traversing-with-pagination.md new file mode 100644 index 0000000000000..6358a6c77d4b8 --- /dev/null +++ b/translations/es-ES/content/rest/guides/traversing-with-pagination.md @@ -0,0 +1,208 @@ +--- +title: Desplazarse con la paginación +intro: Explora las formas para utilizar la paginación en la administración de tus respuestas con algunos ejemplos de cómo utilizar la API de Búsqueda. +redirect_from: + - /guides/traversing-with-pagination/ + - /v3/guides/traversing-with-pagination +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +La API de {% data variables.product.product_name %} proporciona una gran cantidad de información para el consumo de los desarrolladores. La mayoría de las veces incluso podrías encontrar que estás pidiendo _demasiada_ información y, para mantener felices a nuestros servidores, la API [paginará los elementos solicitados][pagination] automáticamente. + +En esta guía haremos algunos llamados a la API de Búsqueda de {% data variables.product.product_name %} e iteraremos sobre los resultados utilizando la paginación. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples]. + +### Fundamentos de la Paginación + +Para empezar, es importante saber algunos hechos acerca de recibir elementos paginados: + +1. Las diferentes llamadas a la API responden con predeterminados diferentes también. Por ejemplo, una llamada a [Listar repositorios públicos](/rest/reference/repos#list-public-repositories) proporciona elementos paginados en conjuntos de 30, mientras que una llamada a la API de Búsqueda de GitHub proporciona elementos en conjuntos de 100 +2. Puedes especificar cuantos elementos quieres recibir (hasta llegar a 100 como máxmo); pero, +3. Por razones técnicas, no todas las terminales se comportan igual. Por ejemplo, los [eventos](/rest/reference/activity#events) no te dejarán usar un máximo de elementos a recibir. Asegúrate de leer la documentación sobre cómo gestionar los resultados paginados para terminales específicas. + +Te proporcionamos la información sobre la paginación en [el encabezado de enlace](http://tools.ietf.org/html/rfc5988) de una llamada a la API. Por ejemplo, vamos a hacer una solicitud de curl a la API de búsqueda para saber cuántas veces se utiliza la frase `addClass` en los proyectos de Mozilla: + +```shell +$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla" +``` + +El parámetro `-I` indica que solo nos interesan los encabezados y no el contenido en sí. Al examinar el resultado, notarás alguna información en el encabezado de enlace, la cual se ve así: + + Link: ; rel="next", + ; rel="last" + +Vamos a explicarlo. `rel="next"` dice que la siguiente página es la `page=2`. Esto tiene sentido ya que, predeterminadamente, todas las consultas paginadas inician en la página `1.` y `rel="last"` proporciona más información, lo cual nos dice que la última página de los resultados es la `34`. Por lo tanto, tenemos otras 33 páginas de información que podemos consumir acerca de `addClass`. ¡Excelente! + +Confía **siempre** en estas relaciones de enlace que se te proporcionan. No intentes adivinar o construir tu propia URL. + +#### Navegar a través de las páginas + +Ahora que sabescuántas páginas hay para recibir, puedes comenzar a navegar a través de ellas para consumir los resultados. Esto se hace pasando un parámetro de `page`. Predeterminadamente, la `page` siempre comienza en `1`. Vamos a saltar a la página 14 para ver qué pasa: + +```shell +$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla&page=14" +``` + +Aquí está el encabezado de enlace una vez más: + + Link: ; rel="next", + ; rel="last", + ; rel="first", + ; rel="prev" + +Como era de esperarse, la `rel="next"` está en 15, y la `rel="last"` es aún 34. Pero ahora tenemos más información: `rel="first"` indica la URL de la _primera_ página, y lo que es más importante, `rel="prev"` te dice el número de página de la página anterior. Al utilizar esta información, puedes construir alguna IU que le permita a los usuarios saltar entre la lista de resultados principal, previa o siguiente en una llamada a la API. + +#### Cambiar la cantidad de elementos recibidos + +Al pasar el parámetro `per_page`, puedes especificar cuantos elementos quieres que devuelva cada página, hasta un máximo de 100 de ellos. Vamos a comenzar pidiendo 50 elementos acerca de `addClass`: + +```shell +$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla&per_page=50" +``` + +Nota lo que hace en la respuesta del encabezado: + + Link: ; rel="next", + ; rel="last" + +Como habrás adivinado, la información de la `rel="last"` dice que la última página ahora es la 20. Esto es porque estamos pidiendo más información por página acerca de nuestros resultados. + +### Consumir la información + +No debes estar haciendo llamadas de curl de bajo nivel para poder trabajar con la paginación, así que escribamos un script de Ruby sencillo que haga todo lo que acabamos de describir anteriormente. + +Como siempre, primero solicitaremos la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y pasaremos nuestro [token de acceso personal][personal token]: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] +``` + +Después, ejecutaremos la búsqueda utilizando el método `search_code` de Octokit. A diferencia de cuando se utiliza `curl`, también podemos recuperar de inmediato la cantidad de resultados, así que hagámoslo: + +``` ruby +results = client.search_code('addClass user:mozilla') +total_count = results.total_count +``` + +Ahora tomemos el número de la última página de forma similar a la información de `page=34>; rel="last"` en el encabezado de enlace. Octokit.rb es compatible con información de paginación a través de una implementación llamada "[Relaciones de enlace de hipermedios][hypermedia-relations]." No entraremos en detalles sobre lo que es, pero basta con decir que cada elemento en la variable de `results` tiene un hash que se llama `rels`, el cual contiene información sobre `:next`, `:last`, `:first`, y `:prev`, dependiendo del resultado en el que estés. Estas relaciones también contienen información sobre la URL resultante llamando a `rels[:last].href`. + +Ahora que sabemos esto, vamos a tomar el número de página del último resultado y a presentar toda esta información al usuario: + +``` ruby +last_response = client.last_response +number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] + +puts "There are #{total_count} results, on #{number_of_pages} pages!" +``` + +Por último, vamos a iterar entre los resultados. Puedes hacerlo con un bucle como `for i in 1..number_of_pages.to_i`, pero mejor vamos a seguir los encabezados de `rels[:next]` para recuperar la información de cada página. Para mantener la simplicidad, solo vamos a tomar la ruta del archivo del primer resultado de cada página. Para hacerlo, vamos a necesitar un bucle; y al final de cada bucle, vamos a recuperar los datos que se configuraron para la siguiente página siguiendo la información de `rels[:next]`. El bucle terminará cuando ya no haya información de `rels[:next]` que consumir (es decir, cuando estemos en `rels[:last]`). Se verá más o menos así: + +``` ruby +puts last_response.data.items.first.path +until last_response.rels[:next].nil? + last_response = last_response.rels[:next].get + puts last_response.data.items.first.path +end +``` + +Cambiar la cantidad de elementos por página es extremadamente simple con Octokit.rb. Simplemente pasa un hash de opciones de `per_page` a la construcción del cliente inicial. Después de ésto, tu código debería permanecer intacto: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] + +results = client.search_code('addClass user:mozilla', :per_page => 100) +total_count = results.total_count + +last_response = client.last_response +number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] + +puts last_response.rels[:last].href +puts "There are #{total_count} results, on #{number_of_pages} pages!" + +puts "And here's the first path for every set" + +puts last_response.data.items.first.path +until last_response.rels[:next].nil? + last_response = last_response.rels[:next].get + puts last_response.data.items.first.path +end +``` + +### Construir enlaces de paginación + +Habitualmente, con la paginación, tu meta no es concentrar todos los resultados posibles, sino más bien producir un conjunto de navegación, como éste: + +![Muestra de los enlaces de paginación](/assets/images/pagination_sample.png) + +Vamos a modelar una micro versión de lo que esto podría implicar. + +Desde el código anterior, ya sabemos que podemos obtener el `number_of_pages` en los resultados paginados desde la primera llamada: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] + +results = client.search_code('addClass user:mozilla') +total_count = results.total_count + +last_response = client.last_response +number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] + +puts last_response.rels[:last].href +puts "There are #{total_count} results, on #{number_of_pages} pages!" +``` + +Desde aquí, podemos construir una hermosa representación en ASCII de las cajas de número: +``` ruby +numbers = "" +for i in 1..number_of_pages.to_i + numbers << "[#{i}] " +end +puts numbers +``` + +Vamos a simular que un usuario da clic en alguna de estas cajas mediante la construcción de un número aleatorio: + +``` ruby +random_page = Random.new +random_page = random_page.rand(1..number_of_pages.to_i) + +puts "A User appeared, and clicked number #{random_page}!" +``` + +Ahora que tenemos un número de página, podemos usar el Octokit para recuperar explícitamente dicha página individual si pasamos la opción `:page`: + +``` ruby +clicked_results = client.search_code('addClass user:mozilla', :page => random_page) +``` + +Si quisiéramos ponernos elegantes, podríamos también tomar la página anterior y posterior para generar los enlaces de los elementos anterior (`<<`) y posterior (`>>`): + +``` ruby +prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)" +next_page_href = client.last_response.rels[:next] ? client.last_response.rels[:next].href : "(none)" + +puts "The prev page link is #{prev_page_href}" +puts "The next page link is #{next_page_href}" +``` + +[pagination]: /rest#pagination +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination +[octokit.rb]: https://github.com/octokit/octokit.rb +[personal token]: /articles/creating-an-access-token-for-command-line-use +[hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination diff --git a/translations/es-ES/content/rest/guides/working-with-comments.md b/translations/es-ES/content/rest/guides/working-with-comments.md new file mode 100644 index 0000000000000..729212f2c3519 --- /dev/null +++ b/translations/es-ES/content/rest/guides/working-with-comments.md @@ -0,0 +1,104 @@ +--- +title: Trabajar con los comentarios +intro: 'Puedes acceder y administrar los comentarios en tus solicitudes de extracción, informes de problemas o confirmaciones si utilizas la API de REST.' +redirect_from: + - /guides/working-with-comments/ + - /v3/guides/working-with-comments +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Para cualquier solicitud de extracción, {% data variables.product.product_name %} proporciona tres tipos de visualizaciones de comentario: [comentarios en la solicitud de extracción][PR comment] integrales, [comentarios en una línea específica][PR line comment] dentro de la solicitud de extracción, y [comentarios sobre una confirmación específica][commit comment] dentro de la solicitud de extracción. + +Cada uno de estos tipos de comentario pasa por una porción diferente de la API de {% data variables.product.product_name %}. En esta guía exploraremos cómo puedes acceder y manipular cada uno de ellos. En cada ejemplo utilizaremos [esta muestra de Solicitud de Extracción que se hizo][sample PR] en el repositorio de "octocat". Como siempre, puedes encontrar las muestras en [nuestro repositorio de platform-samples][platform-samples]. + +### Comentarios de las Solicitudes de Extracción + +Para acceder a loscomentarios de una solicitud de cambios, deberás de pasar por la [API de propuestas][issues]. Esto puede parecer contraintuitivo al principio. Pero una vez que entiendes que una Solicitud de Extracción es solo un informe de problemas con código, tendrá sentido utuilizar la API de Informes de Problemas para crear comentarios en una solicitud de extracción. + +Demostraremos cómo obtener comentarios de una solicitud de extracción mediante la creación de un script de Ruby que utilice [Octokit.rb][octokit.rb]. También deberás crear un [token de acceso personal][personal token]. + +El código siguiente debería ayudarte a empezar a acceder a los comentarios de una solicitud de extracción utilizando Octokit.rb: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] + +client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment| + username = comment[:user][:login] + post_date = comment[:created_at] + content = comment[:body] + + puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n" +end +``` + +Aquí estamos llamando específicamente a la API de Informes de problemas para obtener los comentarios (`issue_comments`), proporcionando tanto el nombre del repositorio (`octocat/Spoon-Knife`) como la ID de la solicitud de extracción en la que estamos interesados (`1176`). Después, solo es cuestión de iterar a través de los comentarios para obtener la información sobre cada uno. + +### Comentarios en una línea de una solicitud de extracción + +Dentro de la vista de diferencias, puedes iniciar un debate sobre algún aspecto específico de un cambio particular que se haya hecho dentro de la solicitud de extracción. Estos comentarios ocurren en las líneas individuales dentro de un archivo que ha cambiado. La URL de la terminal para este debate veien de [la API de Revisión de Solicitudes de Cambios][PR Review API]. + +El código siguiente obtiene todos los comentarios de la solicitud de extracción que se hayan hecho en los archivos, si se le da un número particular de solicitud de extracción: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] + +client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment| + username = comment[:user][:login] + post_date = comment[:created_at] + content = comment[:body] + path = comment[:path] + position = comment[:position] + + puts "#{username} made a comment on #{post_date} for the file called #{path}, on line #{position}. It says:\n'#{content}'\n" +end +``` + +Te darás cuenta de que es increíblemente similar al ejemplo anterior. La diferencia entre esta vista y el comentario de la solicitud de extracción es el enfoque de la conversación. El comentario que se haga en una solicitud de extracción deberá reservarse para debatir ideas sobre el enfoque general del código. Cualquier comentario que se haga como parte de una revisión de una Solicitud de Extracción deberá tratar específicamente la forma en la que se implementa un cambio específico dentro de un archivo. + +### Comentarios de las confirmaciones + +El último tipo de comentarios suceden específicamente en confirmaciones individuales. Es por esto que utilizan [la API de comentarios de las confirmaciones][commit comment API]. + +Para recuperar los comentarios en una confirmación, necesitarás utilizar el SHA1 de ésta. Es decir, no utilizarás ningún identificador relacionado con la Solicitud de Extracción. Aquí hay un ejemplo: + +``` ruby +require 'octokit' + +# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! +# Instead, set and test environment variables, like below +client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] + +client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a4edd96e").each do |comment| + username = comment[:user][:login] + post_date = comment[:created_at] + content = comment[:body] + + puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n" +end +``` + +Ten en cuenta que esta llamada a la API recuperará comentarios de una sola línea, así como aquellos que se hagan en toda la confirmación. + +[PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792 +[PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889 +[commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 +[sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 +[platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments +[issues]: /rest/reference/issues#comments +[personal token]: /articles/creating-an-access-token-for-command-line-use +[octokit.rb]: https://github.com/octokit/octokit.rb +[PR Review API]: /rest/reference/pulls#comments +[commit comment API]: /rest/reference/repos#get-a-commit-comment diff --git a/translations/es-ES/content/rest/index.md b/translations/es-ES/content/rest/index.md new file mode 100644 index 0000000000000..6ad3c6e619a70 --- /dev/null +++ b/translations/es-ES/content/rest/index.md @@ -0,0 +1,15 @@ +--- +title: API de REST de GitHub +shortTitle: REST API +intro: 'Puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %} para crear llamadas y obtener los datos que necesitas para integrar con GitHub.' +redirect_from: + - /v3 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% link_with_intro /overview %} +{% link_with_intro /reference %} +{% link_with_intro /guides %} diff --git a/translations/es-ES/content/rest/overview/api-previews.md b/translations/es-ES/content/rest/overview/api-previews.md new file mode 100644 index 0000000000000..c68c324bf66ec --- /dev/null +++ b/translations/es-ES/content/rest/overview/api-previews.md @@ -0,0 +1,262 @@ +--- +title: Vistas previas de la API +intro: Puedes utilizar las vistas previas de la API para probar características nuevas y proporcionar retroalimentación antes de que dichas características se hagan oficiales. +redirect_from: + - /v3/previews +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Las vistas previas de la API te permiten probar API nuevas y cambios a los métodos existentes de las API antes de que se hagan oficiales en la API de GitHub. + +Durante el periodo de vista previa, podríamos cambiar algunas características con base en la retroalimentación de los desarrolladores. Si realizamos cambios, lo anunciaremos en el [blog de desarrolladores](https://developer.github.com/changes/) sin aviso previo. + +Para acceder a la vista previa de las API, necesitarás proporcionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado `Accept` para tus solicitudes. La documentación de características para cada vista previa especifica qué tipo de medios personalizados proporcionar. + +{% if currentVersion == "free-pro-team@latest" %} +### Migraciones + +Te permite descargar repositorios desde tu usuario de GitHub o cuenta organizacional para revisar, respaldar y [migrar](/rest/reference/migrations) los datos al {% data variables.product.prodname_ghe_server %}. + +**Tipo de medios personalizados:** `wyandotte-preview` **Anunciado en:**[2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) +{% endif %} + +### Despliegues ampliados + +Ejerce mayo control sobre los [despliegues](/rest/reference/repos#deployments) con más información y granularidad más fina. + +**Tipo de medios personalizados:** `ant-man-preview` **Anunciado en:**[2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) + +### Reacciones + +Administra las [reacciones](/rest/reference/reactions) para las confirmaciones, informes de problemas y comentarios. + +**Tipo de medios personalizado:** `squirrel-girl-preview` **Anunciado en:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Actualizado en:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) + +### Línea de tiempo + +Obtén una [lista de eventos](/rest/reference/issues#timeline) para un informe de problemas o solictud de extracción. + +**Tipo de medios personalizados:** `mockingbird-preview` **Anunciado en:**[2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) + +{% if enterpriseServerVersions contains currentVersion %} +### Ambientes de pre-recepción + +Crea, lista, actualiza y borra ambientes para los ganchos de pre-recepción. + +**Tipo de medios personalizados:** `eye-scream-preview` **Anunciado en:**[2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +### Integraciones + +Administra las [integraciones](/v3/integrations) a través de la API. + +**Tipo de medios personalizados:** `machine-man-preview` **Anunciado en:**[2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) +{% endif %} + +### Proyectos + +Administra [proyectos](/rest/reference/projects). + +**Tipo de medios personalizado:** `inertia-preview` **Anunciado en:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Actualizado en:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) + +### Búsqueda de confirmación + +[Busca confirmaciones](/rest/reference/search). + +**Tipo de medios personalizados:** `cloak-preview` **Anunciado en:**[2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) + +### Temas del repositorio + +Ver una lista de los [temas del repositorio](/articles/about-topics/) en [llamadas](/rest/reference/repos) que devuelven los resultados del mismo. + +**Tipo de medios personalizados:** `mercy-preview` **Anunciado en:**[2017-01-31](https://github.com/blog/2309-introducing-topics) + +### Códigos de conducta + +Ver todos los [códigos de conducta](/rest/reference/codes-of-conduct) u obtener qué código de conducta tiene actualmente un repositorio. + +**Tipo de medios personalizado:** `scarlet-witch-preview` + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} +### Equipos anidados + +Incluir contenido anidado del equipo en cargas útiles del [equipo](/rest/reference/teams) + +**Tipo de medios personalizados:** `hellcat-preview` **Anunciado en:**[2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} + +### Webhooks globales + +Habilita los [webhooks globales](/rest/reference/enterprise-admin#global-webhooks/) para una [organización](/webhooks/event-payloads/#organization) y para los tipos de evento del [usuario](/webhooks/event-payloads/#user). Esta vista previa de la API solo está disponible para {% data variables.product.prodname_ghe_server %}. + +**Tipo de medios personalizados:** `superpro-preview` **Anunciado en:**[2017-12-12](/rest/reference/enterprise-admin#global-webhooks) + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} +### Transferencia de repositorio + +Transfiere u [repositorio](/rest/reference/repos) a una organización o usuario. + +**Tipo de medios personalizados:** `nightshade-preview` **Anunciado en:**[2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +### Agregar razón de bloqueo + +Ahora puedes agregar una razón cuando [bloquees un informe de problemas](/rest/reference/issues#lock-an-issue). + +**Tipo de medios personalizados:** `sailor-v-preview` **Anunciado en:**[2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) +{% endif %} + +### Requerir confirmaciones firmadas + +Ahora puedes utilizar la API para administrar la configuración para [requerir confirmaciones firmadas en ramas protegidas](/rest/reference/repos#branches). + +**Tipo de medios personalizados:** `zzzax-preview` **Anunciado en:**[2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) + +### Requerir múltiples revisiones de aprobación + +Ahora puedes [requerir múltiples revisiones de aprobación](/rest/reference/repos#branches) para una solicitud de extracción que utilice la API. + +**Tipo de medios personalizados:** `luke-cage-preview` **Anunciado en:**[2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.19" %} +### Recuperar la información de la tarjeta de visita virtual + +Recupera la información de la [tarjeta de visita virtual de alguien](/rest/reference/users#get-contextual-information-for-a-user). + +**Tipo de medios personalizados:** `hagar-preview` **Anunciado en:**[2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} +### API de suites de verificación y ejecuciones de verificación + +Permite a una GitHub App ejecutar verificaciones externas en el código de un repositorio. Consulta las API de [Ejecuciones de verificación](/rest/reference/checks#runs) y [Suites de verificación](/rest/reference/checks#suites) para obtener más detalles. + +**Tipo de medios personalizados:** `antiope-preview` **Anunciado en:**[2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} + +### Acceso anónimo de Git a los repositorios + +Cuando una instancia de {% data variables.product.prodname_ghe_server %} está en modo privado, los administradores de sitio y de repositorio pueden habilitar el acceso anónimo de Git para los repositorios públicos. + +**Tipo de medios personalizados:** `x-ray-preview` **Anunciado en:**[2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) + +{% endif %} + +### Detalles de la tarjeta de proyecto + +Las respuestas de la API de REST para los [eventos de los informes de problemas](/rest/reference/issues#events) y para [los eventos de la línea de tiempo de los informes de problemas](/rest/reference/issues#timeline) ahora devuelven el campo `project_card` para los eventos relacionados con los proyectos. + +**Tipo de medios personalizados:** `starfox-preview` **Anunciado en:**[2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) + +{% if currentVersion == "free-pro-team@latest" %} + +### Manifiestos de las GitHub Apps + +Los Manifiestos de las GitHub Apps permiten a las personas crear GitHub Apps preconfiguradas. Consulta la sección "[Crear GitHub Apps desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obtener más detalles. + +**Tipo de medios personalizado:** `fury-preview` + +{% endif %} + +### Estados de despliegue + +Ahora puedes actualizar el `environment` de un [estado de despliegue](/rest/reference/repos#create-a-deployment-status) y utilizar los estados de `in_progress` y `queued`. Cuando creas estados de despliegue, ahora puedes utilizar el parámetro `auto_inactive` para marcar los despliegues de `production` antiguos como `inactive`. + +**Tipo de medios personalizados:** `flash-preview` **Anunciado en:**[2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) + +### Permisos de creación de repositorios + +Ahora puedes configurar si los miembros de la organización pueden crear repositorios y decidir qué tipos de éstos pueden crear. Consulta la sección "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" para obtener más detalles. + +**Tipo de medios personalizados:** `surtur-preview` **Anunciado en:**[2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) + +### Adjuntos de contenido + +Ahora puedes proporcionar más información en GitHub para las URL que enlazan a los dominios registrados si utilizas la API {% data variables.product.prodname_unfurls %}. Consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments/)" para obtener más detalles. + +**Tipo de medios personalizados:** `corsair-preview` **Anunciado en:**[2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +### Solicitudes de extracción en borrador + +Puedes utilizar la API de Borradores de Solicitudes de Extracción y sus terminales de [solicitudes de extracción](/rest/reference/pulls) para ver si una solicitud de extracción está en estado de borrador. Para aprender más sobre los borradores de las solicitudes de extracción, consulta la sección "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)". + +**Tipos de medios personalizados:** `shadow-cat-preview` **Anunciado en:**[2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) + +{% endif %} + +### Habilitar e inhabilitar las páginas + +Puedes utilizar las terminales nuevas en la [API de páginas](/rest/reference/repos#pages) para habilitar o inhabilitar las Páginas. Para aprender más sobre las páginas, consulta la sección "[Fundamentos de GitHub Pages](/categories/github-pages-basics)". + +**Tipo de medios personalizados:** `switcheroo-preview` **Anunciado en:**[2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) + +### Listar ramas o solicitudes de extracción para una confirmación + +Puedes utilizar dos terminales nuevas en la [API de Confirmaciones](/rest/reference/repos#commits) para listar las ramas o las solicitudes de extracción para una confirmación. + +**Tipo de medios personalizados:** `groot-preview` **Anunciado en:**[2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +### Desinstalar una GitHub App + +Los propietarios de las GitHub Apps ahora pueden desinstalar una app utilizando la [API de Apps](/rest/reference/apps#delete-an-installation-for-the-authenticated-app). + +**Tipo de medios personalizado:** `gambit-preview` +{% endif %} + +### Habilitar o inhabilitar las alertas vulnerables para un repositorio + +Puedes utilizar dos terminales nueva en la [API de Repos](/rest/reference/repos) para habilitar o inhabilitar las alertas de vulnerabilidades. + +**Tipo de medios personalizados:** `dorian-preview` **Anunciado en:**[2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) + +### Actualizar la rama de una solicitud de extracción + +Puedes utilizar una terminal nueva para [actualizar una rama de una solicitud de extracción](/rest/reference/pulls#update-a-pull-request-branch) con cambios desde el HEAD de la rama ascendente. + +**Tipo de medios personalizados:** `lydian-preview` **Anunciado en:**[2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) + +{% if currentVersion == "free-pro-team@latest" %} +### Habilitar o inhabilitar las correcciónes de seguridad automatizadas + +Puedes utilizar un conjunto de terminales nuevo para [habilitar e inhabilitar las correcciones de seguridad automatizados](/rest/reference/repos#enable-automated-security-fixes). + +**Tipo de medios personalizados:** `london-preview` **Anunciado en:**[2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) +{% endif %} + +### Crear y utilizar plantillas de repositorio + +Puedes Puedes utilizar una terminal nueva para [crear un repositorio utilizando una plantilla](/rest/reference/repos#create-a-repository-using-a-template) y para [crear un repositorio para el usuario autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que constituye un repositorio de plantilla si configuras el parámetro `is_template` como `true`. [Obten un repositorio](/rest/reference/repos#get-a-repository) para verificar si se configuró como un repositorio de plantilla utilizando la clave `is_template`. + +**Tipos de medios personalizados:** `baptiste-preview` **Anunciado en:**[2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) + +{% if currentVersion == "enterprise-server@2.20" %} +### Nuevas terminales de la API de Aplicaciones OAuth + +Puedes administrar los tokens para las Apps de OAuth de forma más segura si utilizas tokens de OAuth como parámetros de entrada en vez de como parámetros de ruta con las nuevas terminales de la [API de aplicaciones de OAuth](/rest/reference/apps#oauth-applications). + +**Tipo de medios personalizados:** `doctor-strange-preview` **Anunciado en:**[2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +### Parámetro de visibilidad nuevo para la API de Repositorios + +Puedes configurar y recuperar la visibilidad de un repositorio en la [API de Repositorios](/rest/reference/repos). + +**Tipo de medios personalizados:** `nebula-preview` **Anunciado en:**[2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} diff --git a/translations/es-ES/content/rest/overview/endpoints-available-for-github-apps.md b/translations/es-ES/content/rest/overview/endpoints-available-for-github-apps.md new file mode 100644 index 0000000000000..abefaefbfdd4d --- /dev/null +++ b/translations/es-ES/content/rest/overview/endpoints-available-for-github-apps.md @@ -0,0 +1,28 @@ +--- +title: Terminales disponibles para las Apps de GitHub +intro: Tu app puede hacer solicitudes a las siguientes terminales de REST. +redirect_from: + - /v3/apps/available-endpoints + - /rest/reference/endpoints-available-for-github-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Debes utilizar un token de acceso a la isntalación para acceder a las terminales utilizando tu {% data variables.product.prodname_github_app %}. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". + +{% for thing in rest.operationsEnabledForGitHubApps[currentVersion] %} +{% assign category = thing[0] %} +{% assign operations = thing[1] %} +{% if operations.size > 0 %} +

+ {{ category }} +

+ +{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/overview/index.md b/translations/es-ES/content/rest/overview/index.md new file mode 100644 index 0000000000000..bcae00b4d5306 --- /dev/null +++ b/translations/es-ES/content/rest/overview/index.md @@ -0,0 +1,20 @@ +--- +title: Resumen de la API de REST +shortTitle: Resumen +intro: 'Aprende sobre los recursos, bibliotecas, vistas previas y solución de problemas para la API de REST de {% data variables.product.prodname_dotcom %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Índice + +{% link_in_list /resources-in-the-rest-api %} +{% link_in_list /media-types %} +{% link_in_list /other-authentication-methods %} +{% link_in_list /troubleshooting %} +{% link_in_list /api-previews %} +{% link_in_list /libraries %} +{% link_in_list /openapi-description %} +{% link_in_list /endpoints-available-for-github-apps %} diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md new file mode 100644 index 0000000000000..4d13ab2415726 --- /dev/null +++ b/translations/es-ES/content/rest/overview/libraries.md @@ -0,0 +1,88 @@ +--- +title: Bibliotecas +intro: 'Puedes utilizar la biblioteca oficial de Octokit y otras bibliotecas de terceros para extender y simplificar cómo utilizas la API de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /libraries/ + - /v3/libraries +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +
+ El Gundamcat +

El Octokit tiene muchos sabores

+

Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.

+

+
Ruby → octokit.rb

+
.NET → octokit.net

+
JavaScript → octokit/rest.js

+
+
+ +# Bibliotecas de terceros + +### Clojure + +Nombre de biblioteca | Repositorio |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) + +### Dart + +Nombre de biblioteca | Repositorio |---|---| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) + +### Emacs Lisp + +Nombre de biblioteca | Repositorio |---|---| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) + +### Erlang + +Nombre de biblioteca | Repositorio |---|---| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) + +### Go + +Nombre de biblioteca | Repositorio |---|---| **go-github**| [google/go-github](https://github.com/google/go-github) + +### Haskell + +Nombre de biblioteca | Repositorio |---|---| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) + +### Java + +Nombre de biblioteca | Repositorio | Más información |---|---|---| **API de Java de GitHub**| [org.eclipse.egit.github.core](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) | Es parte del [Conector de Mylyn de GitHub](https://github.com/eclipse/egit-github) y pretende dar soporte a toda la API de GitHub v3. Las compilaciones se encuentran disponibles en la [Central Maven](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22). **API de GitHub para Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|define una representación de la API de GitHub orientada a objetos. **API de JCabi de GitHub**|[github.jcabi.com (Sitio Web Personal)](http://github.jcabi.com)|se basa en en la API de JSON de Java7 (JSR-353), simplifica las pruebas con una muestra de tiempo de ejecución de GitHub y cubre toda la API. + +### JavaScript + +Nombre de biblioteca | Repositorio | |---|---| **Biblioteca de NodeJS de GitHub**| [pksunkara/octonode](https://github.com/pksunkara/octonode) **wrapper v3 de la API de gh3 de cara al cliente**| [k33g/gh3](https://github.com/k33g/gh3) **wrapper de Github.js wrapper al rededor de la API de GitHub**|[michael/github](https://github.com/michael/github) **Biblioteca de CoffeeScript basada en promesas para el Buscador o para NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client) + +### Julia + +Nombre de biblioteca | Repositorio | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) + +### OCaml + +Nombre de biblioteca | Repositorio | |---|---| **ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github) + +### Perl + +Nombre de biblioteca | Repositorio | Sitio Web de metacpan de la biblioteca |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) + +### PHP + +Nombre de biblioteca | Repositorio |---|---| **Cliente PHP de GitHub **|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **API de PHP de GitHub**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **API de GitHub**|[yiiext/github-api](https://github.com/yiiext/github-api) **Paquete de GitHub Joomla! **|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **Extensión de Nette de GitHub**|[kdyby/github](https://github.com/kdyby/github) **Acceso Fácil a la API de GitHub API**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge para Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **Cliente de PHP7 & wrapper de WebHook**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) + +### Python + +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) + +### Ruby + +Nombre de biblioteca | Repositorio |---|---| **Gema de la API de GitHub API**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) + +### Scala + +Nombre de biblioteca | Repositorio |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) + +### Shell + +Nombre de biblioteca | Repositorio |---|---| **ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) diff --git a/translations/es-ES/content/rest/overview/media-types.md b/translations/es-ES/content/rest/overview/media-types.md new file mode 100644 index 0000000000000..dfc49e01dc66f --- /dev/null +++ b/translations/es-ES/content/rest/overview/media-types.md @@ -0,0 +1,150 @@ +--- +title: Tipós de medios +intro: Aprende sobre los tipos de medios para especificar el formato de los datos que quieres consumir. +redirect_from: + - /v3/media +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Los tipos de medios personalizados se utilizan en la API para permitir que los consumidores elijan el formato de los datos que quieren recibir. Esto se hace al agregar uno o más de los siguientes tipos al encabezado de `Accept` cuando haces una solicitud. Los tipos de medios son específicos para los recursos, lo que les permite cambiar independientemente y aceptar los formatos que otros usarios no aceptan. + +Todos los tipos de medios de {% data variables.product.product_name %} se ven así: + + application/vnd.github[.version].param[+json] + +Los tipos de medios más básicos que la API acepta son: + + application/json + application/vnd.github+json + +Ninguno de estos especifica una [versión][versions], así que siempre obtendrás la representación actual y predeterminada en JSON de los recursos. + +{% note %} + +**Importante:** La versión predeterminada de la API podría cambiar posteriormente. Si estás creando una aplicación y te importa la estabilidad de la API, asegúrate solicitar una versión específica en el encabezado `Accept` como se muestra en los siguientes ejemplos. + +{% endnote %} + +Puedes especificar una versión así: + + application/vnd.github.v3+json + +Si estás especificando una propiedad (tal como full/raw/etc como se define más adelante), pon la versión antes de la propiedad: + + application/vnd.github.v3.raw+json + +Puedes verificar la versión actual a través de los encabezados de cada respuesta. Busca el encabezado `X-GitHub-Media-Type`: + +```shell +$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I +> HTTP/1.1 200 OK +> X-GitHub-Media-Type: github.v3 + +$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \ +$ -H "Accept: application/vnd.github.full+json" +> HTTP/1.1 200 OK +> X-GitHub-Media-Type: github.v3; param=full; format=json + +$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \ +$ -H "Accept: application/vnd.github.v3.full+json" +> HTTP/1.1 200 OK +> X-GitHub-Media-Type: github.v3; param=full; format=json +``` + +### Porpiedades del cuerpo del comentario + +El cuerpo de un comentario puede escribirse en el [Lenguaje de Marcado Enriquecido de GitHub][gfm]. Las [propuestas](/rest/reference/issues), lso [comentarios de las propuestas](/rest/reference/issues#comments), los [comentarios de las solicitudes de cambios](/rest/reference/pulls#comments), y las API de [los comentarios de un gist](/rest/reference/gists#comments) siempre aceptan los mismos tipos de medios: + +#### Sin procesar + + application/vnd.github.VERSION.raw+json + +Devuelve el cuerpo en markdown sin procesar. La respuesta incluirá a `body`. Esto es lo predeterminado si no pasas ningún tipo de medios específico. + +#### Texto + + application/vnd.github.VERSION.text+json + +Devuelve una presentación únicamente de texto para el cuerpo de markdown. La respuesta incluirá a `body_text`. + +#### HTML + + application/vnd.github.VERSION.html+json + +Duevuelve el HTML interpretado del markdown del cuerpo. La respuesta incluirá a `body_html`. + +#### Completo + + application/vnd.github.VERSION.full+json + +Devuelve las representaciones de HTML, texto y sin procesar. La respuesta incluirá a `body`, `body_text`, y `body_html`: + +### Propiedades de los blobs de Git + +Los siguientes tipos de medios se permiten cuando [obtienes un blob](/rest/reference/git#get-a-blob): + +#### JSON + + application/vnd.github.VERSION+json + application/json + +Devuelve una representación en JSON del blob con un `content` en forma de una secuencia cifrada de base64. Esto es lo predeterminado si no se pasa nada más. + +#### Sin procesar + + application/vnd.github.VERSION.raw + +Devuelve los datos del blob sin procesar. + +### Confirmaciones, comparación de la confirmación, y solicitudes de extracción + +La [API de confirmaciones](/rest/reference/repos#commits) y la [API de solicitudes de cambios](/rest/reference/pulls) soportan los formatos de [diff][git-diff] y de [parche][git-patch]: + +#### diff + + application/vnd.github.VERSION.diff + +#### parche + + application/vnd.github.VERSION.patch + +#### sha + + application/vnd.github.VERSION.sha + +### Contenidos del repositorio + +#### Sin procesar + + application/vnd.github.VERSION.raw + +Devuelve el contenido sin procesar de un archivo. Esto es lo predeterminado si no pasas ningún tipo de medios específico. + +#### HTML + + application/vnd.github.VERSION.html + +Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto. + +### Gists + +#### Sin procesar + + application/vnd.github.VERSION.raw + +Devuelve el contenido sin procesar de un gist. Esto es lo predeterminado si no pasas ningún tipo de medios específico. + +#### base64 + + application/vnd.github.VERSION.base64 + +El contenido del gist se cifra en base64 antes de que se envíe. Esto puede serte útil si tu gist contiene cualquier secuencia inválida en UTF-8. + +[gfm]: http://github.github.com/github-flavored-markdown/ +[git-diff]: http://git-scm.com/docs/git-diff +[git-patch]: http://git-scm.com/docs/git-format-patch +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/es-ES/content/rest/overview/openapi-description.md b/translations/es-ES/content/rest/overview/openapi-description.md new file mode 100644 index 0000000000000..192683cc31068 --- /dev/null +++ b/translations/es-ES/content/rest/overview/openapi-description.md @@ -0,0 +1,27 @@ +--- +title: Descripción de OpenAPI +intro: La API de REST de {% data variables.product.product_name %} se describe íntegramente en un documento compatible con OpenAPI 3.0. +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + +### Acerca de las descripciones de OpenAPI + +[OpenAPI](https://swagger.io/docs/specification/about/) es una especificación estándar para describir las API de REST. Las descripciones de OpenAPI permiten tanto a los humanos como a las máquinas descubrir las capacidades de una API sin la necesidad de leer documentación o entender la implementación. {% data variables.product.company_short %} ha puesto si API de REST disponible para el público en general como un documento compatible con OpenAPI 3.0. + +### Obtener la descricpión de OpenAPI de {% data variables.product.company_short %} + +Puedes encontrar la descripción en el repositorio de código abierto de [Descripción de OpenAPI de la API de REST](https://github.com/github/rest-api-description). + +Proporcionamos la descripción en dos formatos. La versión en paquete funciona para la mayoría de los casos, ya que incluye componentes de OpenAPI para reutilización y legibilidad. Si tus herramientas no son compatibles con las referencias a los componentes dentro de las líneas, también te proporcionamos una versión completamente desreferenciada. + +### Utilizar la descripción de OpenAPI de {% data variables.product.company_short %} + +Hay muchos tipos de uso para la descripción de OpenAPI. Por ejemplo, podrías: + +* Generar tu propio cliente de API. +* Validar y probar una ingegración a la API de REST de {% data variables.product.company_short %}. +* Explorar e interactuar con la API de REST de {% data variables.product.product_name %} utilizando herramientas de terceros tales como Insomnia o Postman. + +Por ejemplo, {% data variables.product.company_short %} utiliza la descripción de OpenAPI de REST para generar la [documentación de referencia de la API de REST](/rest/reference) de {% data variables.product.product_name %}. diff --git a/translations/es-ES/content/rest/overview/other-authentication-methods.md b/translations/es-ES/content/rest/overview/other-authentication-methods.md new file mode 100644 index 0000000000000..accb82feba295 --- /dev/null +++ b/translations/es-ES/content/rest/overview/other-authentication-methods.md @@ -0,0 +1,131 @@ +--- +title: Otros métodos de autenticación +intro: Puedes utilizar la autenticación básica para hacer pruebas en un ambiente diferente al productivo. +redirect_from: + - /v3/auth +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +Cuando la API proporciona varios métodos de autenticación, te recomendamos fuertemente utilizar [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) para las aplicaciones productivas. Los otros métodos que se proporcionan tienen la intención de que se utilicen para scripts o para pruebas (por ejemplo, en los casos en donde utilizar todo el OAuth sería exagerado). Las aplicaciones de terceros que dependen de +{% data variables.product.product_name %} para la autenticación no deben pedir o recolectar credenciales de {% data variables.product.product_name %}. +En vez de esto, deben utilizar el [flujo web de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). + +{% endif %} + +{% if currentVersion == "github-ae@latest" %} + +Para autenticarte, te recomendamos utilizar los tokens de [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/), tales como un token de acceso personal a través del [flujo web de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). + +{% endif %} + +### Autenticación Básica + +La API es compatible con la autenticación básica de acuerdo a lo que se define en el [RFC2617](http://www.ietf.org/rfc/rfc2617.txt) con algunas diferencias menores. La diferencia principal es que el RFC requiere de solicitudes sin autenticar para que se le den respuestas `401 Unauthorized`. En muchos lugares, esto divulgaría la existencia de los datos de los usuarios. En cambio, la API de {% data variables.product.product_name %} responde con un `404 Not Found`. Esto puede causar problemas para las bibliotecas de HTTP que asumen una respuesta de `401 Unauthorized`. La solución es construir manualmente el encabezado de `Authorization`. + +#### A través de OAuth y los tokens de acceso personal + +Te recomendamos utilizar tokens de OAuth para autenticarte en la API de GitHub. Los tokens de OAuth incluyen a los [tokens de acceso personal][personal-access-tokens] y habilitan al usuario para revocar el acceso en cualquier momento. + +```shell +$ curl -u username:token {% data variables.product.api_url_pre %}/user +``` + +Este acercamiento es útil si tus herramientas solo son compatibles con la Autenticación Básica pero quieres sacar ventaja de las características de seguridad de los tokens de acceso de OAuth. + +#### A través de nombre de usuario y contraseña + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** {% data variables.product.prodname_dotcom %} descontinuó la autenticación por contraseña hacia la API desde el 13 de noviembre de 2020 para todas las cuentas de {% data variables.product.prodname_dotcom_the_website %}, incluyendo aquellas en planes {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}. {% data variables.product.prodname_team %}, o {% data variables.product.prodname_ghe_cloud %}. Debes autenticarte en la API de {% data variables.product.prodname_dotcom %} con un token de API, tal como un token de acceso de OAuth, un token de acceso de instalación para GitHub Apps, o un token de acceso personal, dependiendo de lo que necesites hacer con el token. Para obtener más información, consulta la sección "[Solución de problemas](/rest/overview/troubleshooting#basic-authentication-errors)". + +{% endnote %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +Para utilizar la autenticación básica con la +API de {% data variables.product.product_name %}, simplemente envía el nombre de usuario y +contraseña asociados con la cuenta. + +Por ejemplo, si estás accediendo a la API a través de [cURL][curl], el siguiente comando te autenticaría si lo reemplazas al `` con tu nombre de usuario de {% data variables.product.product_name %}. (cURL te pedirá ingresar la contraseña.) + +```shell +$ curl -u username {% data variables.product.api_url_pre %}/user +``` +Si habilitaste la autenticación de dos factores, asegúrate de que entiendes como [trabajar con ella](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### Autenticarse con el SSO de SAML + +{% note %} + +**Nota:** Las integraciones y las aplicaciones de OAuth que generan tokens en nombre de otros se autorizan automáticamente. + +{% endnote %} + +Si estás usando la API para acceder a una organización que requiere el [SSO de SAML][saml-sso] para la autenticación, necesitarás crear un token de acceso personal (PAT) y [autorizarlo][allowlist] para esa organización. Visita la URL especificada en `X-GitHub-SSO` para autorizar el token para la organización. + +```shell +$ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test + +> X-GitHub-SSO: required; url=https://github.com/orgs/octodocs-test/sso?authorization_request=AZSCKtL4U8yX1H3sCQIVnVgmjmon5fWxks5YrqhJgah0b2tlbl9pZM4EuMz4 +{ + "message": "Resource protected by organization SAML enforcement. You must grant your personal token access to this organization.", + "documentation_url": "https://docs.github.com" +} +``` + +Cuando solicites datos que pudieran venir de organizaciones múltiples (por ejemplo, [solicitar la lista de informes de problemas que creó el usuario][user-issues]), el encabezado `X-GitHub-SSO` indica qué organizaciones te solicitarán autorizar tu token de acceso personal: + +```shell +$ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/user/issues + +> X-GitHub-SSO: partial-results; organizations=21955855,20582480 +``` + +El valor `organizations` es una lista separada por comas de las ID de organización para aquellas que requieren autorización de tu token de acceso personal. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +### Trabajar con la autenticación de dos factores + +Cuando tienes la autenticación bifactorial habilitada, la [Autenticación Básica](#basic-authentication) para la _mayoría_ de las terminales en la API de REST requiere que utilices un token de acceso personal{% if enterpriseServerVersions contains currentVersion %} o un token de OAuth en vez de tu nombre de usuario y contraseña{% endif %}. + +Puedes generar un token de acceso personal {% if currentVersion == "free-pro-team@latest" %}utilizando la [configuración de desarrollador de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} o con la terminal de "\[Crear una autorización nueva\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" en la API de autorizciones de OAuth para generar un token de OAuth nuevo{% endif %}. Para obtener más información, consulta la sección"[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Entonces utilizarías estos tokens para [autenticarte utilizando un token de OAuth][oauth-auth] con la API de {% data variables.product.prodname_dotcom %}.{% if enterpriseServerVersions contains currentVersion %} La única ocasión en la que necesitas autenticarte con tu nombre de usuario y contraseña es cuando creas tu token de OAuth o cuando utilizas la API de autorizaciones de OAuth.{% endif %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +#### Utilizar la API de Autorizaciones de OAuth con autenticación de dos factores + +Cuando haces llamadas a la API de Autorizaciones de OAuth, la Autenticación Básica requiere que utilces una contraseña de única vez (OTP) así como tu nombre de usuario y contraseña en vez de utilizar tokens. Cuando intentas autenticarte con la API de Autorizaciones de OAuth, el servidor te responderá con un `401 Unauthorized` y con uno de estos encabezados para decirte que necesitas un código de autenticación de dos factores: + +`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. + +Este encabezado te dice cómo tu cuenta recibe sus códigos de autenticación de dos factores. Dependiendo de cómo configures tu cuenta, podrías recibir tus códigos de OTP por SMS o utilizarías una aplicación tal como Google Autenticator o como 1Password. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". Passa la OTP en el encabezado: + +```shell +$ curl --request POST \ + --url https://api.github.com/authorizations \ + --header 'authorization: Basic PASSWORD' \ + --header 'content-type: application/json' \ + --header 'x-github-otp: OTP' \ + --data '{"scopes": ["public_repo"], "note": "test"}' +``` +{% endif %} + +[curl]: http://curl.haxx.se/ +[oauth-auth]: /rest#authentication +[personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line +[saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on +[allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on +[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md new file mode 100644 index 0000000000000..7d7d98298c4cb --- /dev/null +++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md @@ -0,0 +1,621 @@ +--- +title: Recursos en la API de REST +intro: 'Aprende como navegar en los recursos que proporciona la API de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /rest/initialize-the-repo/ +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + +Esto describe los recursos que conforman la API de REST oficial de {% data variables.product.product_name %}. Si tienes cualquier tipo de problema o solicitud, por favor contacta a {% data variables.contact.contact_support %}. + +### Versión actual + +Predeterminadamente, todas las solicitudes a `{% data variables.product.api_url_code %}` reciben la [versión](/developers/overview/about-githubs-apis)**v3** de la API de REST. Te alentamos a [solicitar explícitamente esta versión a través del encabezado `Aceptar`](/rest/overview/media-types#request-specific-version). + + Accept: application/vnd.github.v3+json + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} + +Para obtener información acerca de la API de GraphQL de GitHub, consulta la [documentación de la V4](/graphql). Para obtener más información acerca de migrarse a GraphQL, consulta la sección "[Migrarse desde REST](/graphql/guides/migrating-from-rest-to-graphql)". + +{% endif %} + +### Modelo + +{% if currentVersion == "free-pro-team@latest" %}Todo el acceso a la API se hace a través de HTTPS, y {% else %}Se accede a la API {% endif %}desde `{% data variables.product.api_url_code %}`. Todos los datos se +envían y reciben como JSON. + +```shell +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs + +> HTTP/1.1 200 OK +> Server: nginx +> Date: Fri, 12 Oct 2012 23:33:14 GMT +> Content-Type: application/json; charset=utf-8 +> Status: 200 OK +> ETag: "a00049ba79152d03380c34652f2cb612" +> X-GitHub-Media-Type: github.v3 +> X-RateLimit-Limit: 5000 +> X-RateLimit-Remaining: 4987 +> X-RateLimit-Reset: 1350085394{% if enterpriseServerVersions contains currentVersion %} +> X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif currentVersion == "github-ae@latest" %} +> X-GitHub-Enterprise-Version: GitHub AE{% endif %} +> Content-Length: 5 +> Cache-Control: max-age=0, private, must-revalidate +> X-Content-Type-Options: nosniff +``` + +Los campos en blanco se incluyen como `null` en vez de omitirse. + +Todas las marcas de tiempo se regresan en formato ISO 8601: + + AAAA-MM-DDTHH:MM:SSZ + +Para obtener más información acerca de las zonas horarias en las marcas de tiempo, consulta [esta sección](#timezones). + +#### Representaciones de resumen + +Cuando recuperas una lista de recursos, la respuesta incluye un _subconjunto_ de los atributos para ese recurso. Esta es la representación "resumen" del recurso. (Algunos atributos son caros en términos de cómputo para que la API los proporcione. Por razones de rendimiento, la representación de resumen excluye esos atributos. Para obtener estos atributos, recupera la representación "detallada"). + +**Ejemplo**: Cuando obtienes una lista de repositorios, obtienes la representación de resumen de cada uno de ellos. Aquí, recuperamos la lista de repositorios que pertenecen a la organización [octokit](https://github.com/octokit): + + GET /orgs/octokit/repos + +#### Representaciones detalladas + +Cuando recuperas un recurso individual, la respuesta incluye habitualmente _todos_ los atributos para ese recurso. Esta es la representación "detallada" del recurso. (Nota que la autorización algunas veces influencia la cantidad de detalles que se incluyen en la representación). + +**Ejemplo**: Cuando obtienes un repositorio individual, obtienes la representación detallada del repositorio. Aquí, recuperamos el repositorio [octokit/octokit.rb](https://github.com/octokit/octokit.rb): + + GET /repos/octokit/octokit.rb + +La documentación proporciona un ejemplo de respuesta para cada método de la API. La respuesta de ejemplo ilustra todos los atributos que se regresan con ese método. + +### Autenticación + +{% if currentVersion == "github-ae@latest" %} Te recomendamos autenticarte en la API de REST de {% data variables.product.product_name %} creando un token de OAuth2 a través del [flujo de aplicaciones web](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} Hay dos formas de autenticarse a través de la API de REST de {% data variables.product.product_name %}.{% endif %} Las solicitudes que requieren autenticación devolverán un `404 Not Found`, en vez de un `403 Forbidden`, en algunos lugares. Esto es para prevenir la fuga accidental de los repositorios privados a los usuarios no autorizados. + +#### Autenticación básica + +```shell +$ curl -u "username" {% data variables.product.api_url_pre %} +``` + +#### Token de OAuth (enviado en un encabezado) + +```shell +$ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} +``` + +{% note %} + +Nota: GitHub recomienda enviar los tokens de OAuth utilizando el encabezado de autorización. + +{% endnote %} + +Lee [más acerca de OAuth2](/apps/building-oauth-apps/). Nota que los tokens de OAuth2 pueden adquirirse utilizando el [flujo de aplicaciones web](/developers/apps/authorizing-oauth-apps#web-application-flow) para las aplicaciones productivas. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +#### Llave/secreto de OAuth2 + +{% data reusables.apps.deprecating_auth_with_query_parameters %} + +```shell +curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' +``` + +El utilizar tu `client_id` y `client_secret` _no_ te autentica como un usuario, únicamente identifica tu aplicación de OAuth para incrementar tu límite de tasa. Los permisos se otorgan únicamente a usuarios, no a aplicaciones, y úicamente obtendrás datos que un usuario no autenticado vería. Es por esto que deberías utilizar únicamente la llave/secreto de OAuth2 en escenarios de servidor a servidor. No compartas el secreto de cliente de tu aplicación de OAuth con tus usuarios. + +No podrás autenticarte utilizndo tu llave y secreto de OAuth2 si estás en modo privado, y el intentarlo regresará el mensaje `401 Unauthorized`. Para obtener más información, consulta la sección "[Habilitar el modo privado](/enterprise/admin/installation/enabling-private-mode)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Lee [más acerca de limitar la tasa de no autenticación](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). + +{% endif %} + +#### Límite de ingresos fallidos + +Autenticarse con credenciales inválidas regresará el mensaje `401 Unauthorized`: + +```shell +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar +> HTTP/1.1 401 Unauthorized + +> { +> "message": "Bad credentials", +> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> } +``` + +Después de detectar varias solicitudes con credenciales inválidas dentro de un periodo de tiempo corto, la API rechazará temporalmente todos los intentos de autenticación para el usuario en cuestión (incluyendo aquellos con credenciales válidas) con el mensaje `403 Forbidden`: + +```shell +$ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} +-u valid_username:valid_token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u valid_username:valid_password {% endif %} +> HTTP/1.1 403 Forbidden +> { +> "message": "Maximum number of login attempts exceeded. Please try again later.", +> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> } +``` + +### Parámetros + +Muchos métodos de la API toman parámetros opcionales. Para las solicitudes de tipo `GET`, cualquier parámetro que no se haya especificado como un segmento en la ruta puede pasarse como un parámetro de secuencia de consulta HTTP: + +```shell +$ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" +``` + +En este ejemplo, los valores 'vmg' and 'redcarpet' se proporcionan para los parámetros `:owner` y `:repo` en la ruta mientras que se pasa a `:state` en la secuencia de la consulta. + +Para las solicitudes de tipo `POST`, `PATCH`, `PUT`, and `DELETE`, los parámetros que no se incluyen en la URL deben codificarse como JSON con un Content-Type de 'application/json': + +```shell +$ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations +``` + +### Terminal raíz + +Puedes emitir una solicitud de tipo `GET` a la terminal raíz para obtener todas las categorías de la terminal que son compatibles con la API de REST: + +```shell +$ 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 %} +``` + +### IDs de nodo globales de GraphQL + +Consulta la guía sobre cómo "[Utilizar las ID de Nodo Global](/graphql/guides/using-global-node-ids)" para obtener información detallada sobre cómo encontrar las `node_id` a través de la API de REST y utilizarlas en las operaciones de GraphQL. + +### Errores de cliente + +Existen tres posibles tipos de errores de cliente en los llamados a la API que reciben cuerpos de solicitud: + +1. Enviar un JSON inválido dará como resultado una respuesta de tipo `400 Bad Request`. + + HTTP/1.1 400 Bad Request + Content-Length: 35 + + {"message":"Problems parsing JSON"} + +2. Enviar el tipo incorrecto de valores de JSON dará como resultado una respuesta de tipo `400 Bad +Request`. + + HTTP/1.1 400 Bad Request + Content-Length: 40 + + {"message":"Body should be a JSON object"} + +3. Enviar campos inválidos dará como resultado una respuesta de tipo `422 Unprocessable Entity`. + + HTTP/1.1 422 Unprocessable Entity + Content-Length: 149 + + { + "message": "Validation Failed", + "errors": [ + { + "resource": "Issue", + "field": "title", + "code": "missing_field" + } + ] + } + +Todos los objetos de error tienen propiedades de campo y de recurso para que tu cliente pueda ubicar el problema. También hay un código de error para que sepas qué es lo que está mal con el campo. Estos son los posibles códigos de error de validación: + +| Nombre del código de error | Descripción | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| `missing` | Un recurso no existe. | +| `missing_field` | No se ha configurado un campo requerido en un recurso. | +| `no válida` | El formato de un campo es inválido. Review the documentation for more specific information. | +| `already_exists` | Otro recurso tiene el mismo valor que este campo. Esto puede suceder en recursos que deben tener claves únicas (tales como nombres de etiqueta). | +| `unprocessable` | Las entradas proporcionadas son inválidas. | + +Los recursos también podría enviar errores de validación personalizados (en donde `code` sea `custom`). Los errores personalizados siempre tendrán un campo de `message` que describa el error, y muchos de los errores también incluirán un campo de `documentation_url` que apunte a algún tipo de contenido que te pueda ayudar a resolver el error. + +### Redireccionamientos HTTP + +La API v3 utiliza redireccionamientos HTTP cuando sea adecuado. Los clientes deberán asumir que cualquier solicitud podría resultar en un redireccionamiento. Recibir un redireccionamiento HTTP *no* es un error y los clientes deberán seguirlo. Las respuestas de redireccionamiento tendrán un campo de encabezado de tipo `Location` que contendrá el URI del recurso al cual el cliente deberá repetir la solicitud. + +| Código de estado | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `301` | Redirección permanente. El URI que utilizaste para hacer la solicitud se reemplazó con aquél especificado en el campo de encabezado `Location`. Ésta y todas las solicitudes futuras a este recurso se deberán dirigir al nuevo URI. | +| `302`, `307` | Redireccion temporal. La solicitud deberá repetirse literalmente al URI especificado en el campo de encabezado `Location`, pero los clientes deberán seguir utilizando el URI original para solicitudes futuras. | + +Podrían utilizarse otros códigos de estado de redirección de acuerdo con la especificación HTTP 1.1. + +### Verbos HTTP + +Cuando sea posible, la API v3 intentará utilizar los verbos HTTP adecuados para cada acción. + +| Verbo | Descripción | +| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `HEAD` | Puede emitirse contra cualquier recurso para obtener solo la información del encabezado HTTP. | +| `GET` | Se utiliza para recuperar recursos. | +| `POST` | Se utiliza para crear recursos. | +| `PATCH` | Se utiliza para actualizar los recursos con datos parciales de JSON. Por ejemplo, un recurso de emisión tiene los atributos `title` y `body`. A `PATCH` request may accept one or more of the attributes to update the resource. | +| `PUT` | Se utiliza para reemplazar recursos o colecciones. Para las solicitudes de `PUT` sin el atributo `body`, asegúrate de configurar el encabezado `Content-Length` en cero. | +| `DELETE` | Se utiliza para borrar recursos. | + +### Hypermedia + +Todos los recursos pueden tener una o más propiedades de `*_url` que los enlacen con otros recursos. Estos pretenden proporcionar las URL explícitas para que los clientes adecuados de la API no tengan que construir las URL por ellos mismos. Se recomienda ampliamente que los clientes de la API los utilicen. El hacerlo facilitará a los desarrolladores el realizar mejoras futuras a la API. Se espera que todas las URL sean plantillas de URI [RFC 6570][rfc] adecuadas. + +Puedes entonces expandir estas plantillas utilizando algo como la gema [uri_template][uri]: + + >> tmpl = URITemplate.new('/notifications{?since,all,participating}') + >> tmpl.expand + => "/notifications" + + >> tmpl.expand :all => 1 + => "/notifications?all=1" + + >> tmpl.expand :all => 1, :participating => 1 + => "/notifications?all=1&participating=1" + +### Paginación + +Las solicitudes que recuperan varios elementos se paginarán a 30 elementos predeterminadamente. Puedes especificar páginas subsecuentes con el parámetro `page`. Para algunos recursos, también puedes configurar un tamaño de página personalizado de hasta 100 de ellos con el parámetro `per_page`. Toma en cuenta que, por razones técnicas, no todas las terminales respetan el parámetro `per_page`, consulta la sección de [eventos](/rest/reference/activity#events) por ejemplo. + +```shell +$ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' +``` + +Toma en cuenta que la numeración comienza en 1 y que el omitir el parámetro `page` devolverá la primera página. + +Algunas terminales utilizan una paginación basada en el cursor. Un cursor es una cadena que apunta a una ubicación en el conjunto de resultados. Con la paginación basada en un cursor, no existe un concepto fijo de "páginas" en el conjunto de resultados, así que no puedes navegar a alguna página específica. En vez de esto, puedes recorrer los resultados utilizando los parámetros `before` o `after`. + +Para obtener más información sobre la paginación, revisa nuestra guía sobre [Desplazarse con la paginación][pagination-guide]. + +#### Encabezado de enlace + +{% note %} + +**Nota:** Es importante formar llamados con valores de encabezado de enlace en vez de construir tus propias URL. + +{% endnote %} + +El [encabezado de enlace](http://tools.ietf.org/html/rfc5988) incluye la información de paginación. Por ejemplo: + + Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", + <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" + +_Este ejemplo incluye un salto de línea para legibilidad._ + +O, si la terminal utiliza una paginación basada en un cursor: + + Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", + +Este encabezado de respuesta de `Link` contiene una o más relaciones de enlace de [Hipermedios](/rest#hypermedia), algunos de los cuales requieren una expansión tal como las [plantillas de URI](http://tools.ietf.org/html/rfc6570). + +Los valores de `rel` posibles son: + +| Nombre | Descripción | +| ------- | -------------------------------------------------------------------------- | +| `next` | La relación del enlace para la página subsecuente inmediata de resultados. | +| `last` | La relación del enlace para la última página de resultados. | +| `first` | La relación del enlace para la primera parte de los resultados. | +| `prev` | La relación del enlace para la página previa inmediata de resultados. | + +### Limitación de tasas + +Para las solicitudes de la API que utilizan Autenticación Básica u OAuth, puedes hacer hasta 5,000 solicitudes por hora. Las solicitudes autenticadas se asocian con el usuario autenticado, sin importar si se utilizó [Autenticación Básica](#basic-authentication) o [un token OAuth](#oauth2-token-sent-in-a-header). Esto significa que todas las aplicaciones de OAuth que autorice un usuario compartirán la misma cuota de 5,000 solicitudes por hora cuando se autentiquen con tokens diferentes que pertenezcan al mismo usuario. + +{% if currentVersion == "free-pro-team@latest" %} + +Para los usuarios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes que se hacen utilizando un token de OAuth para los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite incrementado de 15,000 solicitudes por hora. + +{% endif %} + +Para las solicitudes no autenticadas, el límite de tasa permite hasta 60 solicitudes por hora. Las solicitudes no autenticadas se asocian con la dirección IP que las origina, y no con el usuario que realiza la solicitud. + +{% data reusables.enterprise.rate_limit %} + +Nota que [la API de búsqueda tiene reglas personalizadas de límite de tasa](/rest/reference/search#rate-limit). + +Los encabezados HTTP recuperados para cualquier solicitud de la API muestran tu estado actual de límite de tasa: + +```shell +$ curl -I {% data variables.product.api_url_pre %}/users/octocat +> HTTP/1.1 200 OK +> Date: Mon, 01 Jul 2013 17:27:06 GMT +> Status: 200 OK +> X-RateLimit-Limit: 60 +> X-RateLimit-Remaining: 56 +> X-RateLimit-Reset: 1372700873 +``` + +| Nombre del Encabezado | Descripción | +| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-RateLimit-Limit` | La cantidad máxima de solicitudes que puedes hacer por hora. | +| `X-RateLimit-Remaining` | La cantidad de solicitudes que quedan en la ventana de límite de tasa actual. | +| `X-RateLimit-Reset` | La hora en la que se restablecerá la ventana de límite de tasa actual en [segundos de tiempo satelital UTC](http://en.wikipedia.org/wiki/Unix_time). | + +Si necesitas ver la hora en un formato diferente, cualquier lenguaje de programación moderno puede ayudarte con esta tarea. Por ejemplo, si abres la consola en tu buscador web, puedes obtener fácilmente el tiempo de restablecimiento como un objeto de Tiempo de JavaScript. + +``` javascript +new Date(1372700873 * 1000) +// => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) +``` + +Si excedes el límite de tasa, se regresará una respuesta de error: + +```shell +> HTTP/1.1 403 Forbidden +> Date: Tue, 20 Aug 2013 14:50:41 GMT +> Status: 403 Forbidden +> X-RateLimit-Limit: 60 +> X-RateLimit-Remaining: 0 +> X-RateLimit-Reset: 1377013266 + +> { +> "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", +> "documentation_url": "{% data variables.product.doc_url_pre %}/v3/#rate-limiting" +> } +``` + +Puedes [revisar tu estado de límite de tasa](/rest/reference/rate-limit) sin incurrir en una consulta de la API. + +#### Incrementar el límite de tasa de no autenticados para las aplicaciones de OAuth + +Si tu aplicación de OAuth necesita hacer llamados no autenticados con un límite de tasa más alto, puedes pasar la ID de cliente y secreto de tu app ante la ruta de la terminal. + +```shell +$ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos +> HTTP/1.1 200 OK +> Date: Mon, 01 Jul 2013 17:27:06 GMT +> Status: 200 OK +> X-RateLimit-Limit: 5000 +> X-RateLimit-Remaining: 4966 +> X-RateLimit-Reset: 1372700873 +``` + +{% note %} + +**Nota:** Jamás compartas tu secreto de cliente con nadie ni lo incluyas en el código de cara al cliente del buscador. Utiliza únicamente el método que se muestra aquí para las llamadas de servidor a servidor. + +{% endnote %} + +#### Quedarse dentro del límite de tasa + +Si excedes tu límite de tasa utilizando Autenticación Básica u OAuth, es probable que puedas arreglar el problema si guardas en caché las respuestas de la API y utilizas [solicitudes condicionales](#conditional-requests). + +#### Abusar del límite de tasa + +Para prorpocionar un servicio de calidad en {% data variables.product.product_name %}, los límites de tasa adicionales podrían aplicar a algunas acciones cuando se utiliza la API. Por ejemplo, utilizar la API para crear contenido rápidamente, encuestar agresivamente en vez de utilizar webhooks, hacer solicitudes múltiples concurrentes, o solicitar repetidamente datos que son caros a nivel computacional, podría dar como resultado un abuso de tasa. + +El abuso de límite de tasa no pretende interferir con el uso legítimo de la API. Tus límites de tasa habituales deben ser el único límite en el cual te enfoques. Para garantizar que estás actuando como un buen ciudadano de la API, revisa nuestros [lineamientos de mejores prácticas](/guides/best-practices-for-integrators/). + +Si tu aplicación activa este límite de tasa, recibirás una respuesta informativa: + +```shell +> HTTP/1.1 403 Forbidden +> Content-Type: application/json; charset=utf-8 +> Connection: close + +> { +> "message": "You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.", +> "documentation_url": "{% data variables.product.doc_url_pre %}/v3/#abuse-rate-limits" +> } +``` + +{% if currentVersion == "free-pro-team@latest" %} + +### Se requiere un agente de usuario + +Todas las solicitudes a la API DEBEN incluir un encabezado de `User-Agent` válido. Las solicitudes sin encabezado de `User-Agent` se rechazarán. Te solicitamos que utilices tu nombre de usuario de {% data variables.product.product_name %}, o el nombre de tu aplicación, para el valor del encabezado de `User-Agent`. Esto nos permite contactarte en caso de que haya algún problema. + +Aquí hay un ejemplo: + +```shell +User-Agent: Awesome-Octocat-App +``` + +cURL envía un encabezado de `User-Agent` válido predeterminadamente. Si proporcionas un encabezado de `User-Agent` inválido a través de cURL (o a través de un cliente alterno), recibirás una respuesta de `403 Forbidden`: + +```shell +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +> HTTP/1.0 403 Forbidden +> Connection: close +> Content-Type: text/html + +> Request forbidden by administrative rules. +> Please make sure your request has a User-Agent header. +> Check for other possible causes. +``` + +{% endif %} + +### Solicitudes condicionales + +La mayoría de las respuestas regresan un encabezado de `ETag`. Muchas de las respuestas también regresan un encabezado de `Last-Modified`. Puedes utilizar los valores de estos encabezados para hacer solicitudes subsecuentes a estos recursos utilizando los encabezados `If-None-Match` y `If-Modified-Since`, respectivamente. Si el recurso no ha cambiado, el servidor regresará un `304 Not Modified`. + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Nota**: Hacer una solicitud condicional y recibir una respuesta de tipo 304 no cuenta contra tu [Límite de Tasa](#rate-limiting), así que te alentamos a utilizarlo cuando sea posible. + +{% endtip %} + +{% endif %} + +```shell +$ curl -I {% data variables.product.api_url_pre %}/user +> HTTP/1.1 200 OK +> Cache-Control: private, max-age=60 +> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" +> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT +> Status: 200 OK +> Vary: Accept, Authorization, Cookie +> X-RateLimit-Limit: 5000 +> X-RateLimit-Remaining: 4996 +> X-RateLimit-Reset: 1372700873 + +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +> HTTP/1.1 304 Not Modified +> Cache-Control: private, max-age=60 +> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" +> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT +> Status: 304 Not Modified +> Vary: Accept, Authorization, Cookie +> X-RateLimit-Limit: 5000 +> X-RateLimit-Remaining: 4996 +> X-RateLimit-Reset: 1372700873 + +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +> HTTP/1.1 304 Not Modified +> Cache-Control: private, max-age=60 +> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT +> Status: 304 Not Modified +> Vary: Accept, Authorization, Cookie +> X-RateLimit-Limit: 5000 +> X-RateLimit-Remaining: 4996 +> X-RateLimit-Reset: 1372700873 +``` + +### Intercambio de recursos de origen cruzado + +La API es compatible con el Intercambio de Recursos de Origen Cruzado (CORS, por sus siglas en inglés) para las solicitudes de AJAX de cualquier origen. Puedes leer la [Recomendación del W3C sobre CORS](http://www.w3.org/TR/cors/), o [esta introducción](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) de la Guía de Seguridad de HTML 5. + +Aquí hay una solicitud de ejemplo que se envió desde una consulta de buscador `http://example.com`: + +```shell +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +HTTP/1.1 302 Found +Access-Control-Allow-Origin: * +Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval +``` + +Así se ve una solicitud de prevuelo de CORS: + +```shell +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +HTTP/1.1 204 No Content +Access-Control-Allow-Origin: * +Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With +Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE +Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval +Access-Control-Max-Age: 86400 +``` + +### Rellamados de JSON-P + +Puedes enviar un parámetro de `?callback` a cualquier llamado de GET para envolver los resultados en una función de JSON. Esto se utiliza típicamente cuando los buscadores quieren insertar contenido de {% data variables.product.product_name %} en las páginas web evitando los problemas de dominio cruzado. La respuesta incluye la misma salida de datos que la API común, mas la información relevante del Encabezado HTTP. + +```shell +$ curl {% data variables.product.api_url_pre %}?callback=foo + +> /**/foo({ +> "meta": { +> "status": 200, +> "X-RateLimit-Limit": "5000", +> "X-RateLimit-Remaining": "4966", +> "X-RateLimit-Reset": "1372700873", +> "Link": [ // pagination headers and other links +> ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}] +> ] +> }, +> "data": { +> // the data +> } +> }) +``` + +Puedes escribir un agente de JavaScript para procesar la rellamada. Aquí hay un ejemplo minimalista que puedes probar: + + + + + + + +

Open up your browser's console.

+ + + +Todos los encabezados consisten en el mismo valor de secuencia que los encabezados HTTP con una excepción notoria: El Enlace. Los encabezados de enlace se pre-analizan y se presentan como una matriz de tuplas de `[url, options]`. + +Un enlace que se ve así: + + Link: ; rel="next", ; rel="foo"; bar="baz" + +... se verá así en la salida de la rellamada: + +```json +{ + "Link": [ + [ + "url1", + { + "rel": "next" + } + ], + [ + "url2", + { + "rel": "foo", + "bar": "baz" + } + ] + ] +} +``` + +### Zonas horarias + +Algunas solicitudes que crean datos nuevos, tales como aquellas para crear una confirmación nueva, te permiten proporcionar información sobre la zona horaria cuando especificas o generas marcas de tiempo. Aplicamos las siguientes reglas, en orden de prioridad, para determinar la información de la zona horaria para los llamados a la API. + +* [Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) +* [Utilizar el encabezado de `Time-Zone`](#using-the-time-zone-header) +* [Utilizar la última zona horaria conocida del usuario](#using-the-last-known-timezone-for-the-user) +* [Poner como defecto UTC en ausencia de otra información de zona horaria](#defaulting-to-utc-without-other-timezone-information) + +#### Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria + +Para las llamadas a la API que permitan que se especifique una marca de tiempo, utilizamos esa marca de tiempo exacta. Como ejemplo de esto, está la [API de Confirmaciones](/rest/reference/git#commits). + +Estas marcas de tiempo se ven más o menos como `2014-02-27T15:05:06+01:00`. También, puedes ver [este ejemplo](/rest/reference/git#example-input) de cómo se pueden especificar las marcas de tiempo. + +#### Utilizar el encabezado de `Time-Zone` + +Es posible proporcionar un encabezado de `Time-Zone` que defina la zona horaria de acuerdo con la [lista de nombres de la base de datos Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). + +```shell +$ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md +``` + +Esto significa que generamos una marca de tiempo para el momento en el se haga el llamado a tu API en la zona horaria que defina este encabezado. Por ejemplo, la [API de Contenidos](/rest/reference/repos#contents) genera una confirmación de git para cada adición o cambio y utiliza este tiempo actual como la marca de tiempo. Este encabezado determinará la zona horaria que se utiliza para generar la marca de tiempo actual. + +#### Utilizar la última zona horaria conocida del usuario + +Si no se especifica ningún encabezado de `Time-Zone` y haces una llamada autenticada a la API, utilizaremos esta última zona horaria para el usuario autenticado. La última zona horaria conocida se actualiza cuando sea que busques el sitio web de {% data variables.product.product_name %}. + +#### Poner como defecto UTC en ausencia de otra información de zona horaria + +Si los pasos anteriores no dan como resultado ninguna información, utilizaremos UTC como la zona horaria para crear la confirmación de git. + +[rfc]: http://tools.ietf.org/html/rfc6570 +[uri]: https://github.com/hannesg/uri_template + +[pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/es-ES/content/rest/overview/troubleshooting.md b/translations/es-ES/content/rest/overview/troubleshooting.md new file mode 100644 index 0000000000000..1875150b1cdb4 --- /dev/null +++ b/translations/es-ES/content/rest/overview/troubleshooting.md @@ -0,0 +1,65 @@ +--- +title: Solución de problemas +intro: Aprende cómo resolver los problemas más comunes que las personas pueden encontrar en la API de REST. +redirect_from: + - /v3/troubleshooting +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + + + +Si estás encontrando algunas situaciones extrañas en la API, aquí hay una lista de posibles soluciones a algunos de estos problemas que podrías estar experimentando. + +### Error `404` para un repositorio existente + +Habitualmente, enviamos un error `404` cuando tu cliente no está autenticado adecuadamente. Puede que esperes ver un `403 Forbidden` en estos casos. Sin embargo, ya que no queremos proporcionar _ningun_ tipo de información acerca de los repositorios privados, en vez de esto, la API devuelve un `404`. + +Para solucionar los problemas, asegúrate de que [te estás autenticando correctamente](/guides/getting-started/), que [tu token de acceso de OAuth tenga los alcances requeridos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), y que las [restricciones de las aplicaciones de terceros][oap-guide] no estén bloqueando tu acceso. + +### No se devolvieron todos los resultados + +La mayoría de las llamadas a la API que acceden a una lista de recursos (_por ejemplo_, usuarios, informes de problemas, _etc._) son compatibles con la paginación. Si estás haciendo solicitudes y recibes un conjunto de resultados incompleto, probablemente solo estás viendo la primera página. Necesitarás solicitar las páginas restantes para obtener más resultados. + +Es importante que *no* intentes adivinar el formato de la URL de paginación. No todas las llamadas a la API utilizan la misma estructura. En vez de esto, extrae la información de paginación del [Encabezado de Enlace](/rest#pagination), el cual se envía en cada solicitud. + +{% if currentVersion == "free-pro-team@latest" %} +### Errores de autenticación básicos + +Desde el 13 de noviembre de 2020, la autenticación con nombre de usuario y contraseña a la API de REST y a la API de Autorizaciones de OAuth se obsoletizaron y ya no funcionan. + +#### Utilizar `username`/`password` para la autenticación básica + +Si estás utilizando `username` y `password` para las llamadas a la API, éstas credenciales ya no funcionarán para que te autentiques. Por ejemplo: + +```bash +curl -u my_user:my_password https://api.github.com/user/repos +``` + +En vez de esto, utiliza un [token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) cuando pruebes las terminales o cuando realices desarrollos locales: + +```bash +curl -H 'Authorization: token my_access_token' https://api.github.com/user/repos +``` + +Para las Apps de Oauth, debes utilizar el [flujo de aplicaciones web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para generar un token de OAuth para utilizar el encabezado de la llamada a la API: + +```bash +curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos +``` + +#### Llamadas a la API de Autorizciones de OAuth + +Si estás haciendo llamadas a la [API de Autorizaciones de OAuth](/enterprise-server/rest/reference/oauth-authorizations) para administrar las autorizaciones de tu app de OAuth o para generar tokens de acceso de forma similar a este ejemplo: + +```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"}' +``` + +Entonces debes cambiar al [flujo de aplicaciones web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para generar tokens de acceso. + +{% endif %} + +[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md new file mode 100644 index 0000000000000..b175a6a0e2cde --- /dev/null +++ b/translations/es-ES/content/rest/reference/actions.md @@ -0,0 +1,101 @@ +--- +title: Acciones +product: '{% data reusables.gated-features.actions %}' +redirect_from: + - /v3/actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +La API de {% data variables.product.prodname_actions %} te permite administrar las {% data variables.product.prodname_actions %} utilizando la API de REST. La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} necesitan los mismos permisos que se mencionan en cada terminal. Para obtener más información, consulta la sección "[Documentación de {% data variables.product.prodname_actions %}](/actions)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Artefactos + +La API de Artefactos te permite descargar, borrar y recuperar información acerca de los artefactos de los flujos de trabajo. {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". + +{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +## Permisos + +La API de permisos te permite configurar permisos para indicar qué organizaciones y repositorios pueden ejecutar las {% data variables.product.prodname_actions %}, y qué acciones se pueden ejecutar. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)". + +También puedes configurar permisos para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#github-actions)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %} +{% endfor %} +{% endif %} + +## Secretos + +La API de Secretos te permite crear, actualizar, borrar y recuperar información acerca de los secretos cifrados. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". + +La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} debe contar con el permiso de `secrets` para utilizar esta API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Ejecutores autoalojados + +La API de Ejecutores auto-hospedados te permite registrar, ver, y borrar estos ejecutores. {% data reusables.actions.about-self-hosted-runners %} Para obtener más información, consulta "[Alojar tus propios ejecutores](/actions/hosting-your-own-runners)". + +La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. + +Puedes administrar los ejecutores auto-programados para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#github-actions)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Grupos de ejecutores auto-hospedados + +La API de Grupos de Ejecutores Auto-Hospedados te permite administrar grupos para los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". + +La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. + +Puedes administrar los grupos de ejecutores auto-hospedados para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin##github-actions)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Flujos de trabajo + +La API de flujos de trabajo te permite ver los flujos de trabajo de un repositorio. {% data reusables.actions.about-workflows %} Para obtener más información, consulta la sección "[Automatizar tu flujo de trabajo con GitHub Actions](/actions/automating-your-workflow-with-github-actions)". + +{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Jobs de los flujos de trabajo + +La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de un flujo de trabajo. {% data reusables.actions.about-workflow-jobs %} Para obtener más información, consulta la sección "[Sintaxis de flujode trabajo para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". + +{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Ejecuciones de flujo de trabajo + +La API de Ejecuciones de Flujo de Trabajo te permite ver, re-ejecutar, cancelar y ver las bitácoras de las ejecuciones de los flujos de trabajo. {% data reusables.actions.about-workflow-runs %} Para obtener más información, consulta la sección "[Administrar una ejecución de flujo de trabajo](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". + +{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md new file mode 100644 index 0000000000000..5970c20616ba2 --- /dev/null +++ b/translations/es-ES/content/rest/reference/activity.md @@ -0,0 +1,190 @@ +--- +title: Actividad +redirect_from: + - /v3/activity +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Eventos + +La API de eventos es una API de solo lectura para los eventos de {% data variables.product.prodname_dotcom %}. Estos eventos alimentan a los diversos flujos de actividad en el sitio. + +La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos, consulta la sección "[Tipos de evento en {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". Para obtener más información, consulta la "[API de Eventos de Informes de Problemas](/rest/reference/issues#events)". + +Los eventos se optimizan para el sondeo con el encabezado "ETag". Si no se han desencadenado eventos nuevos, verás la respuesta "304 Sin Modificar", y tu límite de tasa actual permanecerá intacto. También hay un encabezado de "X-Poll-Interval" que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. + +``` shell +$ curl -I {% data variables.product.api_url_pre %}/users/tater/events +> HTTP/1.1 200 OK +> X-Poll-Interval: 60 +> ETag: "a18c3bded88eb5dbb5c849a489412bf3" + +# The quotes around the ETag value are important +$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \ +$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"' +> HTTP/1.1 304 Not Modified +> X-Poll-Interval: 60 +``` + +Los eventos son compatibles con la paginación, sin embargo, la opción `per_page` no es compatible. El tamaño de página fijo es de 30 elementos. Se puede obtener hasta diez páginas para obtener un total de 300 eventos. Para obtener más información, consulta la sección "[Desplazarse con la paginación](/rest/guides/traversing-with-pagination)". + +Solo los eventos creados en los últimos 90 días se incluirán en las líneas de tiempo. Los eventos de más de 90 días de antigüedad no se incluirán (aún si la cantidad total de eventos en la línea de tiempo es de 300). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Fuentes + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %} +{% endfor %} + +### Ejemplo de obtención de un canal de Atom + +Para obtener un canal en formato de Atom, debes especificar el tipo `application/atom+xml` en el encabezado `Accept`. Por ejemplo, para obtener un canal de Atom para las asesorías de seguridad de GitHub: + + curl -H "Accept: application/atom+xml" https://github.com/security-advisories + +#### Respuesta + +```shell +Status: 200 OK +``` + +```xml + + + tag:github.com,2008:/security-advisories + + GitHub Security Advisory Feed + + GitHub + + 2019-01-14T19:34:52Z + + tag:github.com,2008:GHSA-abcd-12ab-23cd + 2018-07-26T15:14:52Z + 2019-01-14T19:34:52Z + [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp + + + <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p> + <p><strong>Affected Packages</strong></p> + + <dl> + <dt>Octoapp</dt> + <dd>Ecosystem: npm</dd> + <dd>Severity: moderate</dd> + <dd>Versions: &lt; 4.17.5</dd> + <dd>Fixed in: 4.17.5</dd> + </dl> + + <p><strong>References</strong></p> + + <ul> + <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li> + </ul> + + + + +``` + +## Notificaciones + +Los usuarios reciben notificaciones para las conversaciones en los repositorios que observan, incluyendo: + +* Las de los informes de problemas y sus comentarios +* Las de las solicitudes de extracción en sus comentarios +* Las de los comentarios en cualquier confirmación + +También se envían notificaciones para las conversaciones en los repositorios sin observar cuando el usuario está involucrado, incluyendo: + +* **@menciones** +* Asignaciones de informes de problemas +* Confirmaciones que confirme o cree el usuario +* Cualquier debate en el que el usuario participe activamente + +Todas las llamadas de la API para notificaciones necesitan los alcances de la API para `notifications` o `repo`. El hacerlo te dará acceso de solo lectura a algunos contenidos de informes de problemas y de confirmaciones. Aún necesitarás el alcance de `repo` para acceder a los informes de problemas y a las confirmaciones desde sus respectivas terminales. + +Las notificaciones se devuelven como "hilos". Un hilo contiene información acerca del debate actual sobre un informe de problemas, solicitud de extracción o confirmación. + +Las notificaciones se optimizan para el sondeo con el encabezado `Last-Modified`. Si no hay notificaciones nuevas, verás una respuesta `304 Not Modified`, la cual dejará tu límite de tasa intacto. Hay un encabezado de `X-Poll-Interval` que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. + +``` shell +# Add authentication to your requests +$ curl -I {% data variables.product.api_url_pre %}/notifications +HTTP/1.1 200 OK +Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT +X-Poll-Interval: 60 + +# Pass the Last-Modified header exactly +$ curl -I {% data variables.product.api_url_pre %}/notifications +$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" +> HTTP/1.1 304 Not Modified +> X-Poll-Interval: 60 +``` + +### Razones para obtener las notificaciones + +Cuando recuperas respuestas de la API de Notificaciones, cada carga útil tiene una clave que se titula `reason`. Estas corresponden a los eventos que activan una notificación. + +Hay una lista potencial de `reason` para recibir una notificación: + +| Nombre de la razón | Descripción | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `assign` | Se te asignó al informe de problemas. | +| `author` | Creaste el hilo. | +| `comment` | Comentaste en el hilo. | +| `invitation` | Aceptaste una invitación para colaborar en el repositorio. | +| `manual` | Te suscribiste al hilo (a través de un informe de problemas o solicitud de extracción). | +| `mention` | Se te **@mencionó** específicamente en el contenido. | +| `review_requested` | Se te solicitó, o se solicitó a un equipo del cual eres miembro, revisar una solicitud de extracción.{% if currentVersion == "free-pro-team@latest" %} +| `security_alert` | {% data variables.product.prodname_dotcom %} descubrió una [vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en tu repositorio.{% endif %} +| `state_change` | Cambiaste el estado del hilo (por ejemplo, cerraste un informe de problemas o fusionaste una solicitud de extracción). | +| `subscribed` | Estás observando el repositorio. | +| `team_mention` | Estuviste en un equipo al que se mencionó. | + +Toma en cuenta que la `reason` se modificará conforme al hilo, y puede cambiar si esta `reason` es diferente en una notificación posterior. + +Por ejemplo, si eres el autor de un informe de problemas, las notificaciones subsecuentes de dicho informe tendrán una `reason` o un `author`. Si entonces se te **@menciona** en el mismo informe de problemas, las notificaciones que obtengas de ahí en adelante tendrán una `reason` o una `mention`. La `reason` se queda como una `mention`, sin importar si nunca se te menciona. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Marcar con una estrella + +El marcar a los repositorios con una estrella es una característica que permite a los usuarios marcar a los repositorios como favoritos. Las estrellas se muestran junto a los repositorios para denotar un nivel aproximado de interés. Las estrellas no tienen efecto alguno en las notificaciones o en los canales de actividad. + +### Marcar con estrella vs. Observar + +En agosto de 2012, [cambiamos la forma en la que funciona el observar repositorios](https://github.com/blog/1204-notifications-stars) en {% data variables.product.prodname_dotcom %}. Muchas aplicaciones de cliente de la API podrían estar utilizando las terminales de "observación" originales para acceder a estos datos. Ahora puedes comenzar a utilizar las terminales de "estrella" como sustitución (como se describe más adelante). Para obtener más información, consulta la [publicación de Cambio de la API de observaciones](https://developer.github.com/changes/2012-09-05-watcher-api/) y la "[API para Observar Repositorios](/rest/reference/activity#watching)". + +### Tipos de medio personalizados para marcar con estrella + +Hay un tipo de medios personalizado compatible para la API de REST para Marcar con estrella. Cuando utilizas este tipo de medios personalizado, recibirás una respuesta con la marca de tiempo `starred_at` que indica la hora en el que se creó la estrella. La respuesta también tiene una segunda propiedad que incluye el recurso que se devuelve cuando no se incluye el tipo de medios personalizado. La propiedad que contiene el recurso puede ser `user` o `repo`. + + application/vnd.github.v3.star+json + +Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Observar + +Observar un repositorio registra al usuario para recibir notificaciones en debates nuevos, así como en los eventos de los canales de actividad del mismo. Para marcar a un repositorio como favorito de forma sencilla, consulta la sección "[Marcar repositorios con una estrella](/rest/reference/activity#starring)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/apps.md b/translations/es-ES/content/rest/reference/apps.md new file mode 100644 index 0000000000000..ef5ce3c260da7 --- /dev/null +++ b/translations/es-ES/content/rest/reference/apps.md @@ -0,0 +1,73 @@ +--- +title: Aplicaciones +redirect_from: + - /v3/apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de GitHub Apps te permite obtener información de alto nivel acerca de una GitHub App así como la información específica acerca de las instalaciones de la misma. Para conocer más sobre las GitHub Apps, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)". + +{% data reusables.apps.general-apps-restrictions %} + +Esta página lista las terminales a las que puedes acceder mientras te autenticas como una GitHub App. Consulta la sección "[Autenticarse como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para conocer más. + +Cuando estás autenticado como una GitHub App, la API de GitHub Apps te habilita para obtener información de alto nivel sobre una GitHub App así como para obtener información específica sobre las instalaciones de éstas. + +Puedes acceder a las terminales de la API v3 de REST mientras estás autenticado como una GitHub App. Estas terminales tienen una sección de "Notas" que contiene una viñeta que dice "Funciona con las GitHub Apps". También puedes acceder a estas terminales mientras estás autenticado como un usuario. + +Un subconjunto de terminales de la API v3 de REST requiere que te autentiques como una instalación de una GitHub App. Consulta las [Instalaciones](/rest/reference/apps#installations) para obtener una lista de estas terminales. + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## API de las Aplicaciones de OAuth + +Puedes utilizar esta API para administrar los tokens de OAuth que utiliza una aplicación de OAuth para acceder a las cuentas de {% data variables.product.prodname_dotcom %} de las personas. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Instalaciones + +La API de instalaciones te habilita para obtener información acerca de las instalaciones de tu GitHub App y para realizar acciones dentro de esas instalaciones. Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Para obtener más información sobre cómo autenticarte como una instalación y limitar el acceso a repositorios específicos, consulta la sección "[Autenticarte como una instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". + +Para listar las instalaciones de una GitHub App para una organización, consulta la sección "[Listar instalaciones de la app para una organización](/rest/reference/orgs#list-app-installations-for-an-organization)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" %} +## Marketplace + +Para obtener más información acerca de {% data variables.product.prodname_marketplace %}, consulta "[GitHub Marketplace](/marketplace/)". + +La API de {% data variables.product.prodname_marketplace %} te permite ver qué clientes están utilizando un plan de precios, ver sus compras y también ver si una cuenta tiene una suscripción activa. + +### Hacer pruebas con terminales de muestra + +Esta API incluye terminales que te permiten [probar tu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) con **datos de muestra**. Los datos de muestra son datos falsos y preprogramados que no cambiarán con base en las suscripciones reales. + +Para hacer pruebas con estos datos, utiliza una terminal de muestra en vez de su contraparte productiva. Esto te permite probar si la lógica de la API tendrá éxito antes de listar tus {% data variables.product.prodname_github_app %} en {% data variables.product.prodname_marketplace %}. + +Asegúrate de reemplazar tus terminales de muestra con aquellas productivas antes de desplegar tu {% data variables.product.prodname_github_app %}. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +## Webhooks + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} diff --git a/translations/es-ES/content/rest/reference/billing.md b/translations/es-ES/content/rest/reference/billing.md new file mode 100644 index 0000000000000..a74a8f00e249a --- /dev/null +++ b/translations/es-ES/content/rest/reference/billing.md @@ -0,0 +1,13 @@ +--- +title: Facturación +versions: + free-pro-team: '*' +--- + +Puedes monitorear tus cargos y uso de {% data variables.product.prodname_actions %} y de {% data variables.product.prodname_registry %} para un usuario y organización a través de la API de Facturación. + +Puedes obtener información de facturación para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#billing)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/checks.md b/translations/es-ES/content/rest/reference/checks.md new file mode 100644 index 0000000000000..a90c4d0f2719e --- /dev/null +++ b/translations/es-ES/content/rest/reference/checks.md @@ -0,0 +1,33 @@ +--- +title: Verificaciones +redirect_from: + - /v3/checks +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de Verificaciones te permite crear GitHub Apps que ejecuten verificaciones poderosas contra los cámbios de código en un repositorio. Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones. Para obtener más información, consulta la sección "[Empezar con la API de verificaciones](/rest/guides/getting-started-with-the-checks-api)" y "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Ejecuciones de Verificación + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Check Suites + +{% note %} + + **Nota:** Una GitHub App solo recibe un evento de [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de confirmación, aún si cargas este SHA en más de una rama. Para saber cuándo se carga un SHA de confirmación a una rama, puedes suscribirte a los eventos de [`create`](/webhooks/event-payloads/#create) de la misma. + +{% endnote %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/code-scanning.md b/translations/es-ES/content/rest/reference/code-scanning.md new file mode 100644 index 0000000000000..3cf6cf84d31e8 --- /dev/null +++ b/translations/es-ES/content/rest/reference/code-scanning.md @@ -0,0 +1,15 @@ +--- +title: Escaneo de código +redirect_from: + - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} + +La API del {% data variables.product.prodname_code_scanning %} te permite recuperar y actualizar las alertas de escaneo de código de un repositorio. Puedes utilizar las terminales para crear reportes automatizados para las alertas de escaneo de código en una organización o cargar los resultados de análisis que se generan utilizando herramientas de escaneo de código fuera de línea. Para obtener más información, consulta la sección "[Encontrar vulnerabilidades de seguridad y errores en tu código](/github/finding-security-vulnerabilities-and-errors-in-your-code)". + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/codes-of-conduct.md b/translations/es-ES/content/rest/reference/codes-of-conduct.md new file mode 100644 index 0000000000000..bede0b4f50b49 --- /dev/null +++ b/translations/es-ES/content/rest/reference/codes-of-conduct.md @@ -0,0 +1,14 @@ +--- +title: Códigos de conducta +redirect_from: + - /v3/codes_of_conduct + - /v3/codes-of-conduct +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Puedes usar la API de Códigos de Conducta para recuperar la información acerca del código de conducta de un repositorio. Para obtener el código de conducta de un repositorio, utiliza la terminal "[Obtener un repositorio](/rest/reference/repos#get-a-repository)". + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/emojis.md b/translations/es-ES/content/rest/reference/emojis.md new file mode 100644 index 0000000000000..ea2ca0751dba5 --- /dev/null +++ b/translations/es-ES/content/rest/reference/emojis.md @@ -0,0 +1,12 @@ +--- +title: Emojis +redirect_from: + - /v3/emojis + - /v3/misc +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md new file mode 100644 index 0000000000000..8d9183043e123 --- /dev/null +++ b/translations/es-ES/content/rest/reference/enterprise-admin.md @@ -0,0 +1,393 @@ +--- +title: Administración de GitHub Enterprise +allowTitleToDifferFromFilename: verdadero +redirect_from: + - /v3/enterprise-admin + - /v3/enterprise +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. + +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Si quieres ver la versión para {% data variables.product.prodname_ghe_server %}, utiliza el menú desplegable de **{% data ui.pages.article_version %}**. + +{% endnote %} + +{% endif %} + +### URL de las Terminales + +Las terminales de la API de REST{% if enterpriseServerVersions contains currentVersion %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL: + +```shell +http(s)://hostname/api/v3/ +``` + +{% if enterpriseServerVersions contains currentVersion %} +Las terminales de la API de [Consola de Administración](#management-console) solo llevan un prefijo con un nombre de host: + +```shell +http(s)://hostname/ +``` +{% endif %} +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +### Autenticación + +Las terminales de la API para tu instalación de {% data variables.product.product_name %} acceptan [los mismos métodos de autenticación](/rest/overview/resources-in-the-rest-api#authentication) que los de la API de GitHub.com. Puedes autenticarte con **[Tokens de OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Los tokens de OAuth deben tener el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) de `site_admin` cuando se utilicen con las terminales específicas de la empresa. {% endif %} + +Solo los administradores de sitio autenticados en {% data variables.product.product_name %} pueden acceder a las terminales de la API de administración empresarial{% if enterpriseServerVersions contains currentVersion %}, con exepción de la API de [Consola de Administración](#management-console), la cual requiere la [contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +### Información de la versión + +La versión actual de tu empresa se devuelve en el encabezado de respuesta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` También puedes leer la versión actual si llamas a la [terminal de meta](/rest/reference/meta/). + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +## Registro de auditoría + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +## Facturación + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +## GitHub Actions + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +## SCIM + +### Aprovisionamiento de SCIM para Empresas + +Los Proveedores de Identidad (IdPs) con SCIM habilitado pueden utilizar la API de SCIM para automatizar el aprovisionamiento de la membresía empresarial. La API de {% data variables.product.product_name %} se basa en la versión 2.0 del [estándar de SCIM](http://www.simplecloud.info/). + +El IdP debe utilizar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` como la terminal de SCIM. + +{% note %} + +**Nota:** La API empresarial de SCIM solo se encuentra disponible para las empresas en [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) que cuenten con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +{% endnote %} + +### Autenticar las llamadas a la API de SCIM + +Debes autenticarte como un propietario de una empresa de {% data variables.product.product_name %} para utilizar su API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También podrías utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu SSO empresarial de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). + +### Mapeo de los datos de SAML y de SCIM + +El IdP de SAML y el cliente de SCIM deben utilizar valores coincidentes de `NameID` y `userName` para cada usuario. Esto le permite al usuario que se autentica mediante SAML el poder enlazarse con su identidad aprovisionada de SCIM. + +Los grupos de SCIM se empatan con las organizaciones de {% data variables.product.product_name %} que tienen exactamente el mismo nombre, y que son propiedad de la cuenta empresarial. + +El IdP de SAML y el cliente de SCIM deben configurarse para empatar exactamente el `displayName` del grupo de SCIM con el nombre correspondiente de la organización de {% data variables.product.product_name %}. Esto le permite a {% data variables.product.product_name %} enlazar el grupo de SCIM con la membrecía organizacional de {% data variables.product.product_name %}. + +### Atributos de Usuario de SCIM compatibles + +| Nombre | Type | Descripción | +| ---------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `userName` | `secuencia` | El nombre de usuario para el usuario. | +| `name.givenName` | `secuencia` | El primer nombre del usuario. | +| `name.lastName` | `secuencia` | El apellido del usuario. | +| `emails` | `arreglo` | Lista de correos electrónicos del usuario. | +| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` para un usuario ya sea con el proveedor de SAML, o utilizar la terminal de [Listar las identidades aprovisionadas de SCIM para una empresa](#list-scim-provisioned-identities-for-an-enterprise) y filtrar otros atributos conocidos, tales como el nombre de usuario o la dirección de correo electrónico de un usuario de GitHub. | +| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. | +| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). | +| `groups` | `arreglo` | Lista opcional de las ID del grupo de SCIM del cual el usuario es miembro. | + +{% note %} + +**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula: + +```shell +GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} +``` + +{% endnote %} + +### Atributos del Grupo de SCIM compatibles + +| Nombre | Type | Descripción | +| ------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `displayName` | `secuencia` | El nombre del grupo de SCIM, el cual debe empatar exactamente con el nombre de la organización de {% data variables.product.product_name %} correspondiente. Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, el nombre del grupo debe ser `octo-org`. | +| `members` | `arreglo` | Lista de IDs de usuario de SCIM que son miembros del grupo. | + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'scim' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" %} + +## Cifrado estático + +Puedes utilizar la API de cifrado estático para administrar la llave que cifra tus datos en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar el cifrado de datos para tu empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +## Estadísticas de los Administradores + +La API de estadísticas de los administradores proporciona diversas métricas sobre tu instalación. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +## Anuncios + +La API de anuncios te permite administrar el letrero de anuncios globales en tu empresa. Para obtener más información, consulta la sección "[Personalizar los mensajes de usuario para tu empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} + +## Webhooks globales + +Los webhooks globales se instalan en tu empresa. Puedes utilizar los webhooks globales para monitorear, responder a, o requerir las reglas para los usuarios, organizaciones, equipos y repositorios en tu empresa. Los webhooks globales se pueden suscribir a los tipos de evento para [organizaciones](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuarios](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositorios](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipos](/developers/webhooks-and-events/webhook-events-and-payloads#team), [miembros](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membrecías](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifuraciones](/developers/webhooks-and-events/webhook-events-and-payloads#fork), y [pings](/developers/webhooks-and-events/about-webhooks#ping-event). + +*Esta API solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. Para aprender cómo configurar los webhooks globales, consulta la sección [Acerca de los webhooks globales](/enterprise/admin/user-management/about-global-webhooks). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +## LDAP + +Puedes utilizar la API de LDAP para actualizar las relaciones de cuenta entre un usuario de {% data variables.product.product_name %} o un equipo y su entrada enlazada de LDAP o poner en cola una sincronización nueva. + +Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, por sus siglas en inglés) al cual mapea un usuario o equipo. Nota que las terminales de LDAP generalmente solo son efectivas si tu aplicativo de {% data variables.product.product_name %} [habilitó la sincronización con LDAP](/enterprise/admin/authentication/using-ldap). La terminal de [mapeo de LDAP para actualización para un usuario](#update-ldap-mapping-for-a-user) puede utilizarse cuando se habilita LDAP, aún si la sincronización con LDAP está inhabilitada. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +## Licencia + +La API de licencias proporciona información sobre tu licencia empresarial. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +## Consola de administración + +La API de la Consola de Administración te ayuda a administrar tu {% data variables.product.product_name %} instalación. + +{% tip %} + +Debes configurar el número de puerto explícitamente cuando haces llamadas de la API hacia la Consola de Administración. Si habilitaste TLS en tu empresa, el número de puerto es `8443`; de lo contrario, el número de puerto es `8080`. + +Si no quieres proporcionar un número de puerto, necesitarás configurar tu herramienta para seguir automáticamente las redirecciones. + +También necesitas agregar el [marcador `-k`](http://curl.haxx.se/docs/manpage.html#-k) cuando utilices `curl`, ya que {% data variables.product.product_name %} utiliza un certificado auto-firmado antes de que [agregues tu propio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/). + +{% endtip %} + +### Autenticación + +Necesitas pasar tu [Contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/) como un token de autenticación para cada terminal de la API de ésta, con excepción de [`/setup/api/start`](#create-a-github-enterprise-server-license). + +Utiliza el parámetro de `api_key` para enviar este token con cada solicitud. Por ejemplo: + +```shell +$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' +``` + +También puedes utilizar la autenticación HTTP estándar para enviar este token. Por ejemplo: + +```shell +$ curl -L 'https://api_key:your-amazing-password@hostname:admin_port/setup/api' +``` + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +## Organizaciones + +La API de Administración Organizacional te permite crear organizaciones en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + + +{% if enterpriseServerVersions contains currentVersion %} +## Ganchos de Pre-recepción de la Organización + +La API de Ganchos de Pre-recepción de la Organización te permite ver y modificar la aplicación de dichos ganchos que están disponibles para una organización. + +### Atributos de objeto + +| Nombre | Type | Descripción | +| -------------------------------- | ----------- | --------------------------------------------------------- | +| `name (nombre)` | `secuencia` | El nombre del gancho. | +| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | +| `allow_downstream_configuration` | `boolean` | Si los repositorios pueden ignorar la imposición o no. | +| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | + +Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. + +`configuration_url` podría ser un enlace a esta terminal o ser la configuración global de este gancho. Solo los administradores de sistema pueden acceder a la configuración global. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +## Ambientes de pre-recepción + +La API de Ambientes de Pre-recepción te permite crear, listar, actualizar y borrar ambientes para los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. + +### Atributos de objeto + +#### Ambiente de pre-recepción + +| Nombre | Type | Descripción | +| --------------------- | ----------- | --------------------------------------------------------------------------------------------------- | +| `name (nombre)` | `secuencia` | El nombre del ambiente como se muestra en la IU. | +| `image_url` | `secuencia` | La URL del tarball que se descargará y extraerá. | +| `default_environment` | `boolean` | Si este es el ambiente predeterminado que viene con {% data variables.product.product_name %} o no. | +| `descargar` | `object` | El estado de descarga de este ambiente. | +| `hooks_count` | `número` | La cantidad de ganchos de pre-recepción que utilizan este ambiente. | + +#### Descarga del Ambiente de Pre-recepción + +| Nombre | Type | Descripción | +| --------------- | ----------- | -------------------------------------------------------------------------------- | +| `state` | `secuencia` | El estado de la mayoría de las descargas recientes. | +| `downloaded_at` | `secuencia` | La hora en la cual iniciaron la mayoría de las descrgas recientes. | +| `message` | `secuencia` | Cuando algo falla, este tendrá cualquier mensaje de error que se haya producido. | + +Los valores posibles para `state` son `not_started`, `in_progress`, `success`, `failed`. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +## Ganchos de pre-recepción + +La API de Ganchos Pre-recepción te permite crear, listar, actualizar y borrar los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. + +### Atributos de objeto + +#### Ganchos de pre-recepción + +| Nombre | Type | Descripción | +| -------------------------------- | ----------- | ----------------------------------------------------------------------------------- | +| `name (nombre)` | `secuencia` | El nombre del gancho. | +| `script` | `secuencia` | El script que ejecuta el gancho. | +| `script_repository` | `object` | El repositorio de GitHub en donde se mantiene el script. | +| `environment` | `object` | El ambiente de pre-recepción en donde se ejecuta el script. | +| `enforcement` | `secuencia` | El estado de las imposiciones para este gancho. | +| `allow_downstream_configuration` | `boolean` | Si las imposiciones pueden o no ignorarse a nivel de organización o de repositorio. | + +Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} + +## Ganchos de pre-recepción del repositorio + +La API de Ganchos de Pre-recepción para Repositorios te permite ver y modificar la imposición de los ganchos de pre-recepción que están disponibles para un repositorio. + +### Atributos de objeto + +| Nombre | Type | Descripción | +| ------------------- | ----------- | --------------------------------------------------------- | +| `name (nombre)` | `secuencia` | El nombre del gancho. | +| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | +| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | + +Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. + +`configuration_url` podría ser un enlace a este repositorio, al propietario de su organización o a su configuración global. La autorización para acceder a esta terminal en `configuration_url` se determina a nivel de administrador de sitio o de propietario. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +## Usuarios + +La API de Administración de Usuarios te permite suspender{% if enterpriseServerVersions contains currentVersion %}, dejar de suspender, promover, y degradar{% endif %}{% if currentVersion == "github-ae@latest" %} y dejar de suspender{% endif %} a los usuarios en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `403` si intentan acceder a ella. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} diff --git a/translations/es-ES/content/rest/reference/gists.md b/translations/es-ES/content/rest/reference/gists.md new file mode 100644 index 0000000000000..4a357f109caf2 --- /dev/null +++ b/translations/es-ES/content/rest/reference/gists.md @@ -0,0 +1,51 @@ +--- +title: Gists +redirect_from: + - /v3/gists +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Autenticación + +Puedes leer gists públicos {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}y crearlos para usuarios anónimos sin un token{% else %} de forma anónima, pero debes haber iniciado sesión en GitHub para crear gists.{% endif %} Para leer o escribir gists en nombre de un usuario, necesitas el alcance de OAuth para gists y un token. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)". + + + +### Truncamiento + +La API de Gist proporciona hasta un megabyte de contenido para cada archivo en el gist. Cada archivo que se devuelve para un gist a través de la API tiene una clave que se llama `truncated`. Si `truncated` aparece como `true`, significa que el archivo es demasiado grande y solo se devolvió una parte de su contenido en `content`. + +Si necesitas el contenido completo del archivo, puedes hacer una solicitud de tipo `GET` a la URL que se especifica en `raw_url`. Ten en cuent que, para los archivos mayores a diez megabytes, necesitarás clonar el gist a través de la URL que proprocionó `git_pull_url`. + +Adicionalmente a el truncamiento del contenido específico del archivo, la lista de archivos completa podría truncarse si la cantidad total excede los 300 archivos. Si la clave `truncated` de nivel superior aparece como `true`, únicamente se han devuelto los primeros 300 archivos en la lista. Si necesitas recuperar todos los archivos del gist, necesitarás clonarlo a través de la URL que te proporcionó `git_pull_url`. + +### Tipos de medios personalizados para los gists + +Estos son los tipos de medios compatibles para recuperar el contenido de los gists. + + application/vnd.github.VERSION.raw + application/vnd.github.VERSION.base64 + +Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Comentarios + +### Tipos de medios personalizados para los comentarios de los Gists + +Estos son los tipos de medios compatibles para los comentarios de los gists. + + application/vnd.github.VERSION.raw + application/vnd.github.VERSION.base64 + +Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/git.md b/translations/es-ES/content/rest/reference/git.md new file mode 100644 index 0000000000000..8218605968b26 --- /dev/null +++ b/translations/es-ES/content/rest/reference/git.md @@ -0,0 +1,65 @@ +--- +title: Base de datos de Git +allowTitleToDifferFromFilename: verdadero +redirect_from: + - /v3/git +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas). Para obtener más información acerca de utilizar la API de la Base de Datos de Git, consulta la secicón "[Empezar con la API de datos de Git](/rest/guides/getting-started-with-the-git-database-api)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Blobs + +Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types). + +### Tipos de medios personalizados para los blobs + +Estos son los tipos de medios compatibles para los blobs. + + application/json + application/vnd.github.VERSION.raw + +Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Confirmaciones + +Una confirmación de Git es una impresión de pantalla de la jerarquía ([árbol de Git](/rest/reference/git#trees)) y del contenido de los archivos ([blob de Git](/rest/reference/git#blobs)) en un reposiotorio de Git. Estas terminales te permiten leer y escribir [objetos de confirmación](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) en tu base de datos en {% data variables.product.product_name %}. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Referencias + +Una referencia (`git ref`) es simplemente un archivo que contiene un hash SHA-1 de una confirmación de Git. Cuando te refieres a una confirmación de Git, puedes utilizar la referencia de Git, la cual es un nombre fácil de recordar, en vez de utilizar el hash. La referencia de Git puede reescribirse para apuntar a una confirmación nueva. Una rama es solo una referencia de Git que almacena el hash de la confirmación de Git nueva. Estas terminales te permiten leer y escribir [referencias](https://git-scm.com/book/en/v1/Git-Internals-Git-References) en tu base de datos de Git en {% data variables.product.product_name %}. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Etiquetas + +Una etiqueta de git es similar a una [referencia de Git](/rest/reference/git#refs), pero la confirmación de Git a la que apunta jamás cambia. Las etiquetas de git son útiles cuando quieres apuntar a algún lanzamiento específico. Estas terminales te permiten leer y escribir [objetos de etiquetas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)en tu base de datos de Git en {% data variables.product.product_name %}. La API de etiquetas de Git son compatibles únicamente con los [objetos de etiqueta anotados](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), no con etiquetas ligeras. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Árboles + +Un objeto de árbol de Git crea la jerarquía entre archivos para un repositorio de Git. Puedes utilizar el objeto de árbol de Git para crear una relación entre directorios y entre los archivos que contienen. Estas terminales te permiten leer y escribir [objetos de árbol](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)en tu base de datos de Git en {% data variables.product.product_name %}. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/gitignore.md b/translations/es-ES/content/rest/reference/gitignore.md new file mode 100644 index 0000000000000..2210da47eec0c --- /dev/null +++ b/translations/es-ES/content/rest/reference/gitignore.md @@ -0,0 +1,21 @@ +--- +title: Gitignore +redirect_from: + - Gitignore +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Cuando creas un repositorio de {% data variables.product.product_name %} nuevo a través de la API, puedes especificar una [plantilla de .gitignore](/github/using-git/ignoring-files) para que aplique al repositorio cuando éste se cree. La API de plantillas de .gitignore lista y recupera plantillas del [repositorio de .gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}. + +### Tipos de medios personalizados para gitignore + +Puedes utilizar este tipo de medios personalizado cuando obtengas una plantilla de gitignore. + + application/vnd.github.VERSION.raw + +Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/index.md b/translations/es-ES/content/rest/reference/index.md new file mode 100644 index 0000000000000..0343789b50399 --- /dev/null +++ b/translations/es-ES/content/rest/reference/index.md @@ -0,0 +1,43 @@ +--- +title: Referencia +shortTitle: Referencia +intro: Lee la documentación de referencia para conocer sobre los recursos que están disponibles en la API de REST de GitHub. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Índice + +{% link_in_list /actions %} +{% link_in_list /activity %} +{% link_in_list /activity %} +{% link_in_list /billing %} +{% link_in_list /checks %} +{% link_in_list /codes-of-conduct %} +{% link_in_list /code-scanning %} +{% link_in_list /emojis %} +{% link_in_list /enterprise-admin %} +{% link_in_list /gists %} +{% link_in_list /git %} +{% link_in_list /gitignore %} +{% link_in_list /interactions %} +{% link_in_list /issues %} +{% link_in_list /licenses %} +{% link_in_list /markdown %} +{% link_in_list /meta %} +{% link_in_list /migrations %} +{% link_in_list /oauth-authorizations %} +{% link_in_list /orgs %} +{% link_in_list /projects %} +{% link_in_list /pulls %} +{% link_in_list /rate-limit %} +{% link_in_list /reactions %} +{% link_in_list /repos %} +{% link_in_list /scim %} +{% link_in_list /search %} +{% link_in_list /secret-scanning %} +{% link_in_list /teams %} +{% link_in_list /users %} +{% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/es-ES/content/rest/reference/interactions.md b/translations/es-ES/content/rest/reference/interactions.md new file mode 100644 index 0000000000000..a2f142667383f --- /dev/null +++ b/translations/es-ES/content/rest/reference/interactions.md @@ -0,0 +1,55 @@ +--- +title: Interacciones +redirect_from: + - /v3/interactions +versions: + free-pro-team: '*' +--- + +Los usuarios interactuan con los repositorios al comentar, abrir informes de problemas y crear solicitudes de extracción. La API de interacciones permite a las personas con acceso de propietario o de administrador restringir la interacción con los repositorios públicos temporalmente a un tipo específico de usuario. + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Organization + +La API de Interacciones Organizacionales permite a los propietarios el restringir temporalmente qué tipo de usuariopuede comentar, abrir propuestas, o crear solicitudes de cambios en los repositorios públicos de la organización. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}: + +* {% data reusables.interactions.existing-user-limit-definition %} en la organización. +* {% data reusables.interactions.contributor-user-limit-definition %} en la organización. +* {% data reusables.interactions.collaborator-user-limit-definition %} en la organización. + +Configurar el límite de interacciones a nivel organizacional sobreescribirá cualquier límite de interacción que se haya configurado para los repositorios individuales que pertenezcan a la organización. Para configurar los límites de interacción para los repositorios individuales que pertenezcan a la organización, mejor utiliza la terminal de interaciones del [Repositorio](#repository). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Repositorio + +La API de interacciones de repositorio permite a las personas con acceso administrativo o de propietario restringir temporalmente qué tipo de usuario puede comentar, abrir propuestas, o crear solicitudes de cambios en un repositorio privado. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}: + +* {% data reusables.interactions.existing-user-limit-definition %} en el repositorio. +* {% data reusables.interactions.contributor-user-limit-definition %} en el repositorio. +* {% data reusables.interactions.collaborator-user-limit-definition %} en el repositorio. + +Si se habilita un límite de interacción para el usuario u organización a la que pertenece el repositorio, éste no podrá cambiarse para el repositorio individual. En su lugar, utiliza las terminales de interacciones de [Usuario](#user) o de [Organización](#organization) para cambiar el límite de interacción. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Usuario + +La API de interacciones de usuario te permite restringir temporalmente qué tipo de usuario puede comentar, abrir propuestas, o crear solicitudes de cambio en tus repositorios públicos. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}: + +* {% data reusables.interactions.existing-user-limit-definition %} de interactuar con tus repositorios. +* {% data reusables.interactions.contributor-user-limit-definition %} de interactuar con tus repositorios. +* {% data reusables.interactions.collaborator-user-limit-definition %} de interactuar con tus repositorios. + +El configurar el límite de interacción a nivel de usuario sobreescribirá cualquier límite de interacción que se configure para los repositorios individuales que le pertenezcan a éste. Para configurar límites de interacción diferentes para los repositorios individuales que pertenezcan al usuario, utiliza la terminal de interacciones de [Repositorio](#repository) en su lugar. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/issues.md b/translations/es-ES/content/rest/reference/issues.md new file mode 100644 index 0000000000000..a5a14710a897c --- /dev/null +++ b/translations/es-ES/content/rest/reference/issues.md @@ -0,0 +1,70 @@ +--- +title: Problemas +redirect_from: + - /v3/issues +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Tipos de mendios personalizados para los informes de problemas + +Estos son los tipos de medios compatibles para los informes de problemas. + + application/vnd.github.VERSION.raw+json + application/vnd.github.VERSION.text+json + application/vnd.github.VERSION.html+json + application/vnd.github.VERSION.full+json + +Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Asignatarios + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Comentarios + +La API de Comentarios par los Informes de Problemas es compatible con listar, ver, editar y crear comentarios en informes de problemas y solicitudes de extracción. + +Los comentarios de los informes de problemas utilizan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Eventos + +La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos](/developers/webhooks-and-events/github-event-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Etiquetas + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Hitos + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Línea de tiempo + +La API de eventos para la línea de tiempo puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad de la línea de tiempo en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)". + +Puedes utilizar esta API para mostrar información sobre los informes de problemas y solicitudes de extracción o para determinar a quién debería notificársele sobre los comentarios en los informes de problemas. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/licenses.md b/translations/es-ES/content/rest/reference/licenses.md new file mode 100644 index 0000000000000..97a75c04d434f --- /dev/null +++ b/translations/es-ES/content/rest/reference/licenses.md @@ -0,0 +1,34 @@ +--- +title: Licencias +redirect_from: + - /v3/licenses +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de licencias devuelve metadatos acerca de las liciencias de código abierto populares y acerca de la información sobre un archivo de licencia específico de un proyecto. + +La API de licencias utiliza [el Licenciatario de código abierto de la Gema de Ruby ](https://github.com/benbalter/licensee) para intentar identificar la licencia del proyecto. Este licenciatario empata el contenido del archivo de `LICENSE` de un proyecto (si es que existe) contra una lista corta de licencias conocidas. Como resultado, la API no toma en cuenta las licencias de las dependencias del proyecto u otros medios de documentar la licencia de un proyecto tales como las referencias al nombre de la licencia en la documentación. + +Si una licencia empata, la llave de licencia y el nombre devuelto se apegan a la [especificación SPDX](https://spdx.org/). + +**Nota:** Estas terminales también devolverán la información de licencia de un repositorio: + +- [Obtener un repositorio](/rest/reference/repos#get-a-repository) +- [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user) +- [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories) +- [Listar las bifurcaciones](/rest/reference/repos#list-forks) +- [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user) +- [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories) + +{% warning %} + +GitHub puede ser muchas cosas, pero no es un buró legal. Como tal, GitHub no proporcional consejo legal. Al utilizar la API de licencias o al enviarnos un mensaje de correo electrónico acerca de ellas no estás incurriendo en ningún consejo legal ni creando una relación abogado-cliente. Si tienes cualquier pregunta acerca de lo que puedes o no hacer con una licencia específica, debes acudir a tu propio consejero legal antes de continuar. De hecho, siempre debes consultar con tu propio abogado antes de que decidas tomar cualquier decisión que pudiera tener implicaciones legales o que pudiera impactar tus derechos. + +GitHub creó la API de Licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y de los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados (por lo menos, la mayoría de nosotros no lo son) y que cometemos errores como todo el mundo. Es por esto que GitHub te proporciona una API "tal y como está" y no garantiza nada con respecto a la información o a las licencias que se proporcionan en o a través de ella, y se desllinda de cualquier responsabilidad derivada de los daños que pudiesen resultar de su uso. + +{% endwarning %} + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/markdown.md b/translations/es-ES/content/rest/reference/markdown.md new file mode 100644 index 0000000000000..5a71bd7804aff --- /dev/null +++ b/translations/es-ES/content/rest/reference/markdown.md @@ -0,0 +1,11 @@ +--- +title: Markdown +redirect_from: + - /v3/markdown +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/meta.md b/translations/es-ES/content/rest/reference/meta.md new file mode 100644 index 0000000000000..b261f929a2066 --- /dev/null +++ b/translations/es-ES/content/rest/reference/meta.md @@ -0,0 +1,11 @@ +--- +title: Meta +redirect_from: + - /v3/meta +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md new file mode 100644 index 0000000000000..1fed26a508f18 --- /dev/null +++ b/translations/es-ES/content/rest/reference/migrations.md @@ -0,0 +1,122 @@ +--- +title: Migraciones +redirect_from: + - /v3/migrations + - /v3/migration + - /v3/migration/migrations +versions: + free-pro-team: '*' +--- + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Organization + +La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)." y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)". + +{% data variables.migrations.organization_migrations_intro %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Importaciones de Código Fuente + +{% data variables.migrations.source_imports_intro %} + +Una importación de código fuente habitual inicia la importación y luego actualiza (opcionalmente) a los autores y/o actualiza las preferencias para utilizar el LFS de Ggit si existen archivos grandes en la importación. También puedes crear un webhook que escuche al [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para encontrar el estado de la importación. + +Se puede ver un ejemplo más detallado en este diagrama: + +``` ++---------+ +--------+ +---------------------+ +| Tooling | | GitHub | | Original Repository | ++---------+ +--------+ +---------------------+ + | | | + | Start import | | + |----------------------------->| | + | | | + | | Download source data | + | |--------------------------------------------->| + | | Begin streaming data | + | |<---------------------------------------------| + | | | + | Get import progress | | + |----------------------------->| | + | "status": "importing" | | + |<-----------------------------| | + | | | + | Get commit authors | | + |----------------------------->| | + | | | + | Map a commit author | | + |----------------------------->| | + | | | + | | | + | | Finish streaming data | + | |<---------------------------------------------| + | | | + | | Rewrite commits with mapped authors | + | |------+ | + | | | | + | |<-----+ | + | | | + | | Update repository on GitHub | + | |------+ | + | | | | + | |<-----+ | + | | | + | Map a commit author | | + |----------------------------->| | + | | Rewrite commits with mapped authors | + | |------+ | + | | | | + | |<-----+ | + | | | + | | Update repository on GitHub | + | |------+ | + | | | | + | |<-----+ | + | | | + | Get large files | | + |----------------------------->| | + | | | + | opt_in to Git LFS | | + |----------------------------->| | + | | Rewrite commits for large files | + | |------+ | + | | | | + | |<-----+ | + | | | + | | Update repository on GitHub | + | |------+ | + | | | | + | |<-----+ | + | | | + | Get import progress | | + |----------------------------->| | + | "status": "complete" | | + |<-----------------------------| | + | | | + | | | +``` + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Usuario + +La API de migraciones de usuario solo está disponible para los propietarios de cuentas autenticadas. Para obtener más información, consulta la sección "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)". + +{% data variables.migrations.user_migrations_intro %} Para encontrar una lista descargable de datos de migración, consulta "[Descarga un archivo de migración de usuario](#download-a-user-migration-archive)". + +Antes de descargar un archivo deberás iniciar la migración del usuario. Una vez que el estado de la migración sea `exported`, podrás descargarla. + +Ya que hayas creado el archivo de migración, este estará disponible para su descarga por siete días. Pero puedes borrar el archivo de migración del usuario antes si lo prefieres. Puedes desbloquear tu repositorio cuando la migración aparezca como `exported` para comenzar a utilizar tu repositorio nuevamente o borrarlo si ya no necesitas los datos del código fuente. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/oauth-authorizations.md b/translations/es-ES/content/rest/reference/oauth-authorizations.md new file mode 100644 index 0000000000000..946bacb4b0ea3 --- /dev/null +++ b/translations/es-ES/content/rest/reference/oauth-authorizations.md @@ -0,0 +1,14 @@ +--- +title: Autorizaciones de OAuth +redirect_from: + - /v3/oauth_authorizations + - /v3/oauth-authorizations +versions: + enterprise-server: '*' +--- + +Puedes utilizar esta API para administrar el acceso que las aplicaciones de OAuth tienen en tu cuenta. Solo puedes acceder a esta API a través de la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) utilizando tu nombre de usuario y contraseña, y no los tokens. + +Si tú o tus usuarios habilitaron la autenticación de dos factores, asegúrate de que entiendes cómo [trabajar con la autenticación de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/orgs.md b/translations/es-ES/content/rest/reference/orgs.md new file mode 100644 index 0000000000000..d0cf4b632cfc7 --- /dev/null +++ b/translations/es-ES/content/rest/reference/orgs.md @@ -0,0 +1,64 @@ +--- +title: Organizaciones +allowTitleToDifferFromFilename: verdadero +redirect_from: + - /v3/orgs +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" %} +## Bloquear usuarios + +El token que se utiliza para autenticar la llamada debe tener el alcance de `admin:org` para poder hacer cualquier llamada de bloqueo para una organización. De lo contrario, la respuesta devolverá un `HTTP 404`. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +## Miembros + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Colaboradores externos + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Webhooks + +Los webhooks de la organización te permiten recibir cargas útiles HTTP de tipo `POST` cada que suceden eventos específicos dentro de la misma. El suscribirse a estos eventos hace posible crear integraciones que reaccionan a eventos en {% data variables.product.product_name %}. Para obtener más información sobre las acciones a las cuales te puedes suscribir, consulta los "[tipos de eventos de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". + +### Alcances & Restricciones + +Todas las acciones en contra de los webhooks de una organización requieren que el usuario autenticado sea un administrador de la organización que se está administrando. Adicionalmente, los tokens de OAuth requieren el alcance `admin:org_hook`. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)". + +Para porteger los datos sensibles que pueden encontrarse en las configuraciones de los webhooks, también imponemos las siguientes reglas de control de accesos: + +- Las aplicaciones de OAuth no pueden listar, ver o editar los webhooks que no crearon ellas mismas. +- Los usuarios no pueden listar, ver o editar los webhooks que crearon las aplicaciones de OAuth. + +### Recibir Webhooks + +Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS. + +Para encontrar más de las mejores prácticas, [consulta nuestra guía](/guides/best-practices-for-integrators/). + +#### Encabezados de Webhook + +{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/webhooks/event-payloads/#delivery-headers) para encontrar más detalles. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md new file mode 100644 index 0000000000000..887979effdac3 --- /dev/null +++ b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md @@ -0,0 +1,884 @@ +--- +title: Permisos que requieren las Github Apps +intro: 'Puedes encontrar los permisos que requiere cada terminal compatible con {% data variables.product.prodname_github_app %}.' +redirect_from: + - /v3/apps/permissions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Acerca de los permisos de las {% data variables.product.prodname_github_app %} + +Las {% data variables.product.prodname_github_app %}s se crean con un conjunto de permisos. Los permisos definen a qué recursos puede acceder la {% data variables.product.prodname_github_app %} a través de la API. Para obtener más información, consulta la sección "[Configurar los permisos para las GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)". + +### Permisos de metadatos + +Las GitHub Apps tienen el permiso de metadatos de `Read-only` predeterminadamente. El permiso de metadatos proporciona acceso a una recopilación de terminales de solo lectura con los metadatos de varios recursos. Estas terminales no filtran información sensible de los repositorios privados. + +{% data reusables.apps.metadata-permissions %} + +- [`GET /`](/rest#root-endpoint) +- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct) +- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct) +- [`GET /emojis`](/rest/reference/emojis#emojis) +- [`GET /feeds`](/rest/reference/activity#get-feeds) +- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses) +- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license) +- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document) +- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode) +- [`GET /meta`](/rest/reference/meta#meta) +- [`GET /organizations`](/rest/reference/orgs#list-organizations) +- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization) +- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects) +- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories) +- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) +- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics) +{% endif %} +- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors) +- [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks) +- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages) +- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository) +- [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers) +- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity) +- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity) +- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity) +- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count) +- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day) +- [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers) +- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags) +- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics) +- [`GET /repositories`](/rest/reference/repos#list-public-repositories) +- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) +- [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) +- [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) +- [`GET /users`](/rest/reference/users#list-users) +- [`GET /users/:username`](/rest/reference/users#get-a-user) +- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user) +- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows) +- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user) +- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user) +- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user) +- [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user) +- [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user) +- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user) +- [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) + +_Colaboradores_ +- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators) +- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator) + +_Comentarios sobre confirmación de cambios_ +- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository) +- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment) +- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) +- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments) + +_Eventos_ +- [`GET /events`](/rest/reference/activity#list-public-events) +- [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories) +- [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events) +- [`GET /repos/:owner/:repo/events`](/rest/reference/activity#list-repository-events) +- [`GET /users/:username/events`](/rest/reference/activity#list-events-for-the-authenticated-user) +- [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user) + +_Git_ +- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates) +- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template) + +_Claves_ +- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user) + +_Miembros de la organización_ +- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members) +- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user) +- [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members) +- [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user) + +_Search_ +- [`GET /search/code`](/rest/reference/search#search-code) +- [`GET /search/commits`](/rest/reference/search#search-commits) +- [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests) +- [`GET /search/labels`](/rest/reference/search#search-labels) +- [`GET /search/repositories`](/rest/reference/search#search-repositories) +- [`GET /search/topics`](/rest/reference/search#search-topics) +- [`GET /search/users`](/rest/reference/search#search-users) + +{% if currentVersion == "free-pro-team@latest" %} +### Permiso sobre las "acciones" + +- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) +{% endif %} + +### Permiso sobre la "administración" + +- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) +- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) +- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) +- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) +- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write) +{% endif %} +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write) +{% endif %} +- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write) +- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write) +{% endif %} +- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write) +- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write) + +_Ramas_ +- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read) +- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read) +- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) + +_Colaboradores_ +- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) +- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write) + +_Invitaciones_ +- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read) +- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write) +- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write) + +_Claves_ +- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read) +- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write) +- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read) +- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write) + +_Equipos_ +- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) + +{% if currentVersion == "free-pro-team@latest" %} +_Tráfico_ +- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read) +- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read) +- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Permiso sobre el "bloqueo" + +- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read) +- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) +- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (:write) +- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write) +{% endif %} + +### Permiso sobre las "verificaciones" + +- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (:write) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (:write) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) + +### Permiso sobre el "contenido" + +- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read) +{% endif %} +- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read) +- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) +- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) +- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read) +- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read) +- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read) +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write) +{% endif %} +- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read) +- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read) + +_Ramas_ +- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read) +- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read) +- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write) +- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) +- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) +- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) + +_Comentarios sobre confirmación de cambios_ +- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write) +- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read) +- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read) + +_Git_ +- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write) +- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (:read) +- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (:write) +- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (:read) +- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (:write) +- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (:read) +- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (:read) +- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (:write) +- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (:write) +- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (:write) +- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (:read) +- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (:write) +- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read) + +{% if currentVersion == "free-pro-team@latest" %} +_Import_ +- [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read) +- [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write) +- [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write) +- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (:write) +- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (:read) +- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (:write) +- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (:read) +- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write) +{% endif %} + +_Reacciones_ + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% endif %} + +_Lanzamientos_ +- [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read) +- [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write) +- [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read) +- [`PATCH /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#update-a-release) (:write) +- [`DELETE /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#delete-a-release) (:write) +- [`GET /repos/:owner/:repo/releases/:release_id/assets`](/rest/reference/repos/#list-release-assets) (:read) +- [`GET /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#get-a-release-asset) (:read) +- [`PATCH /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#update-a-release-asset) (:write) +- [`DELETE /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#delete-a-release-asset) (:write) +- [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read) +- [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read) + +### Permiso sobre los "despliegues" + +- [`GET /repos/:owner/:repo/deployments`](/rest/reference/repos#list-deployments) (:read) +- [`POST /repos/:owner/:repo/deployments`](/rest/reference/repos#create-a-deployment) (:write) +- [`GET /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/repos#get-a-deployment) (:read){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/repos#delete-a-deployment) (:write){% endif %} +- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/repos#list-deployment-statuses) (:read) +- [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/repos#create-a-deployment-status) (:write) +- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/repos#get-a-deployment-status) (:read) + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +### Permiso sobre los "correos electrónicos" + +{% if currentVersion == "free-pro-team@latest" %} +- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write) +{% endif %} +- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read) +- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (:write) +- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (:write) +- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read) +{% endif %} + +### Permiso sobre los "seguidores" + +- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read) +- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read) +- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (:read) +- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write) +- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write) + +### Permiso sobre las "llaves gpg" + +- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read) +- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write) +- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (:read) +- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write) + +### Permiso sobre los "informes de problemas" + +Los informes de problemas y las solicitudes de extracción están estrechamente relacionadas. Para obtener más información, consulta la sección "[Listar informes de problemas asignados al usuario autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)". Si tu GitHub App tiene permisos sobre los informes de problemas pero no los tiene en las solicitudes de extracción, entonces estas terminales se limitaran a los informes de problemas. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en los informes de problemas como en las solicitudes de extracción se restringirán a los informes de problemas únicamente. + +- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read) +- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (:read) +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) + +_Asignatarios_ +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) + +_Eventos_ +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) + +_Etiquetas_ +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) + +_Hitos_ +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) + +_Reacciones_ +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} + +### Permiso sobre las "llaves" + +_Claves_ +- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read) +- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write) +- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read) +- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write) + +### Permiso sobre los "miembros" + +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write) +{% endif %} +- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read) +- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write) +- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write) +{% endif %} +- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +_Invitaciones_ +- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read) +- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write) +- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read) +- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read) +{% endif %} + +_Miembros de la organización_ +- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write) +- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read) +- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write) +- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (:write) +- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (:write) +- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (:write) +- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (:read) +- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read) +- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write) + +_Miembros del equipo_ +- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read) +- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read) +- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write) +- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write) + +_Equipos_ +- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read) +- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write) +- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read) +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +- [`GET /teams/:team_id`](/rest/reference/teams#get-a-team) (:read) +{% endif %} +- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write) +- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read) +- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read) +- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read) +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) +{% endif %} +- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read) +- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read) +- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read) +- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write) +- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read) + +### Permiso sobre la "administración de la oprganización" + +- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write) +{% if currentVersion == "free-pro-team@latest" %} +- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write) +{% endif %} + +### Permiso sobre los "ganchos de la organización" + +- [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read) +- [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write) +- [`GET /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#get-an-organization-webhook) (:read) +- [`PATCH /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#update-an-organization-webhook) (:write) +- [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write) +- [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write) + +_Equipos_ +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) + +{% if enterpriseServerVersions contains currentVersion %} +### Permiso sobre los "ganchos de pre-recepción de la organización" + +- [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read) +- [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read) +- [`PATCH /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) (:write) +- [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write) +{% endif %} + +### Permiso sobre los "proyectos de la organización" + +- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write) +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) + +{% if currentVersion == "free-pro-team@latest" %} +### Permiso sobre el "bloqueo de usuarios de la organización" + +- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read) +- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read) +- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (:write) +- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write) +{% endif %} + +### Permiso sobre las "páginas" + +- [`GET /repos/:owner/:repo/pages`](/rest/reference/repos#get-a-github-pages-site) (:read) +- [`POST /repos/:owner/:repo/pages`](/rest/reference/repos#create-a-github-pages-site) (:write) +- [`PUT /repos/:owner/:repo/pages`](/rest/reference/repos#update-information-about-a-github-pages-site) (:write) +- [`DELETE /repos/:owner/:repo/pages`](/rest/reference/repos#delete-a-github-pages-site) (:write) +- [`GET /repos/:owner/:repo/pages/builds`](/rest/reference/repos#list-github-pages-builds) (:read) +- [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write) +- [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read) +- [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read) + +### Permiso sobre las "solicitudes de extracción" + +Las solicitudes de extracción y los informes de problemas tienen una relación estrecha. Si tu GitHub App tiene permisos sobre las solicitudes de extracción pero no sobre los informes de problemas, estas terminales se limitarán a las solicitudes de extracción. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en solicitudes de extracción como en informes de problemas se restringirán a las solicitudes de extracción únicamente. + +- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (:read) +- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (:read) +- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (:read) +- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (:read) +- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (:read) +- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (:read) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (:read) +- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write) + +_Asignatarios_ +- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read) +- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write) + +_Eventos_ +- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read) +- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write) + +_Etiquetas_ +- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read) +- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write) +- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (:write) +- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (:write) +- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (:read) +- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write) +- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write) + +_Hitos_ +- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read) +- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read) +- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (:write) +- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write) +- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read) + +_Reacciones_ +- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write) +- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read) +- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write) +- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read) +- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write) +- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write) +- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write) +- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write) +- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write){% endif %} + +_Revisores solicitados_ +- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write) + +_Revisiones_ +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read) +- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (:write) +- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (:write) +- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read) +- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write) + +### Permisos sobre los "ganchos del repositorio" + +- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read) +- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write) +- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read) +- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write) +- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write) +- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read) +- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read) + +{% if enterpriseServerVersions contains currentVersion %} +### Permiso sobre los "ganchos de pre-recepción del repositorio" + +- [`GET /repos/:owner/:repo/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) (:read) +- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) (:write) +- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (:write) +{% endif %} + +### Permiso sobre los "proyectos del repositorio" + +- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read) +- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write) +- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (:write) +- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (:read) +- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (:write) +- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (:read) +- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (:write) +- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (:write) +- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (:read) +- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (:write) +- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (:write) +- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (:read) +- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (:write) +- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (:write) +- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write) +- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read) +- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write) + +_Equipos_ +- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read) + +{% if currentVersion == "free-pro-team@latest" %} +### Permiso sobre los "secretos" + +* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read) +* [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read) +* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (:read) +* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write) +* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (:write) +* [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (:read) +* [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (:read) +* [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (:write) +* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (:read) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (:write) +* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) +* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permiso en las "alertas de escaneo de secretos" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### Permiso sobre los "eventos de seguridad" + +- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) +- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Permiso sobre los "ejecutores auto-hospedados" +- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) +- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read) +- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (:read) +- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (:write) +- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (:write) +{% endif %} + +### Permiso sobre "un archivo" + +- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read) +- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write) +- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write) + +### Permiso sobre el "marcar con una estrella" + +- [`GET /user/starred/:owner/:repo`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) (:read) +- [`PUT /user/starred/:owner/:repo`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) (:write) +- [`DELETE /user/starred/:owner/:repo`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) (:write) + +### Permiso sobre los "estados" + +- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read) +- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read) +- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write) + +### Permiso sobre los "debates de equipo" + +- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read) +- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (:read) +- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (:write) +- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (:write) +- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (:read) +- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/es-ES/content/rest/reference/projects.md b/translations/es-ES/content/rest/reference/projects.md new file mode 100644 index 0000000000000..73bb19a788f67 --- /dev/null +++ b/translations/es-ES/content/rest/reference/projects.md @@ -0,0 +1,33 @@ +--- +title: Proyectos +redirect_from: + - /v3/projects +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Tarjetas + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Colaboradores + +Esta API te permite interactuar con los proyectos de una organización. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Columnas + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/pulls.md b/translations/es-ES/content/rest/reference/pulls.md new file mode 100644 index 0000000000000..1da9f91900b82 --- /dev/null +++ b/translations/es-ES/content/rest/reference/pulls.md @@ -0,0 +1,84 @@ +--- +title: Extracciones +redirect_from: + - /v3/pulls +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de Solicitudes de Extracción te permite listar, ver, editar, crear e incluso fusionar solicitudes de extracción. Los comentarios en las solicitudes de extracción se pueden administrar a través de la [API de Comentarios de los Informes de Problemas](/rest/reference/issues#comments). + +Cada solicitud de extracción es un informe de problemas, pero no todos los informes de problemas son una solicitud de extracción. Es por esto que las acciones "compartidas" para ambas características, como el manipular a los asignados, etiquetas e hitos, se proporcionan dentro de la [API de Informes de Problemas](/rest/reference/issues). + +### Tipos de medios personalizados para las solicitudes de extracción + +Estos son los tipos de medios compatibles para las solicitudes de extracción. + + application/vnd.github.VERSION.raw+json + application/vnd.github.VERSION.text+json + application/vnd.github.VERSION.html+json + application/vnd.github.VERSION.full+json + application/vnd.github.VERSION.diff + application/vnd.github.VERSION.patch + +Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + + + +Si existe alguna diff que se haya dañado, contacta a {% data variables.contact.contact_support %}. Incluye el nombre del repositorio y la ID de la solicitud de extracción en tu mensaje. + +### Relaciones de los enlaces + +Las solicitudes de extracción tienen estas posibles relaciones de enlaces: + +| Nombre | Descripción | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `self` | La ubicación de la API para esta Solicitud de Extracción. | +| `html` | La ubicación de HTML para esta Solicitud de Extracción. | +| `issue` | La ubicación de la API para el [informe de problemas](/rest/reference/issues) de esta Solicitud de Extracción. | +| `comments` | La ubicación de la API para los [Comentarios del informe de problemas](/rest/reference/issues#comments) de esta Solicitud de Extracción. | +| `review_comments` | La ubicación de la API para los [Comentarios de revisión](/rest/reference/pulls#comments) de esta Solicitud de Extracción. | +| `review_comment` | La [plantilla de URL](/rest#hypermedia) para construir la ubicación de la API para un [Comentario de revisión](/rest/reference/pulls#comments) en el repositorio de esta Solicitud de Extracción. | +| `commits` | La ubicación de la API para las [confirmaciones](#list-commits-on-a-pull-request) de esta solicitud de extracción. | +| `estados` | La ubicación de la API para los [estados de las confirmaciones](/rest/reference/repos#statuses) de esta Solicitud de Extracción, los cuales son los estados de su rama `head`. | + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Revisiones + +Las revisiones de las solicitudes de extracción son grupos de Comentarios de Revisión de las Solicitudes de Extracción en las mismas, los cuales se agrupan con un estado y, opcionalmente, con un comentario en el cuerpo. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Comentarios de revisión + +Los comentarios de revisión de las solicitudes de extracción son comentarios de una porción de la diff unificada durante la revisión de esta solicitud. Los comentarios de confirmación y comentarios de la solicitud de extracción son diferentes de aquellos sobre la revisión de estas solicitudes. Se aplican comentarios de confirmación directamente a un confirmación, así como se aplican comentarios del informe de problemas sin referenciar una porción de la diff unificada. Para obtener más información, consulta las secciones "[Crear un comentario sobre una confirmación](/rest/reference/git#create-a-commit)" y "[Crear un comentario sobre un informe de problemas](/rest/reference/issues#create-an-issue-comment)". + +### Tipos de medios personalizados para los comentarios sobre las revisiones de las solicitudes de extracción + +Estos son los tipos de medios compatibles para los comentarios sobre las revisiones de las solicitudes de exstracción. + + application/vnd.github.VERSION.raw+json + application/vnd.github.VERSION.text+json + application/vnd.github.VERSION.html+json + application/vnd.github.VERSION.full+json + +Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Solicitudes de revisión + +Los autores de las solicitudes de extracción y los propietarios y colaboradores de los repositorios pueden solicitar una revisión de una solicitud de extracción a cualquiera con acceso de escritura en el repositorio. Cada revisor solicitado recibirá una notificación solicitándoles revisar la solicitud de extracción. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/content/rest/reference/rate-limit.md b/translations/es-ES/content/rest/reference/rate-limit.md new file mode 100644 index 0000000000000..6046b7dcc751f --- /dev/null +++ b/translations/es-ES/content/rest/reference/rate-limit.md @@ -0,0 +1,30 @@ +--- +title: Limite de tasa +redirect_from: + - /v3/rate_limit + - /v3/rate-limit +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La documentación general de la API de REST describe las [reglas de los límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting). Puedes revisar tu estado actual de límite de tasa en cualquier momento utilizando la API de Límites de Tasa que se describe a continuación. + +### Entender el estado de tu límite de tasa + +La API de Búsqueda tiene un [límite de tasa personalizado](/rest/reference/search#rate-limit) separado de aquél que rige el resto de la API de REST. La API de GraphQL también tiene un [límite de tasa personalizado](/graphql/overview/resource-limitations#rate-limit) que está separado y se calcula diferente que los límites de tasa de la API de REST. + +Es por esto que la respuesta de la API de Límites de Tasa categoriza tu límite de tasa. Debajo de `resources`, verás cuatro objetos: + +* El objeto `core` proporciona tu estado de límite de tasa para todos los recursos no relacionados a búsquedas en la API de REST. + +* El objeto `search` proporciona el estado de tu límite de tasa para la [API de Búsqueda](/rest/reference/search). + +* El objeto `graphql` proporciona el estado de tu límite de tasa para la [API de GraphQL](/graphql). + +* El objeto `integration_manifest` proporciona el estado de tu límite de tasa para la terminal [Conversión de código para el Manifiesto de GitHub App](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). + +Para obtener más información sobre los valores y encabezados en la respuesta de límite de tasa, consulta la sección "[Limitar las tasas](/rest#rate-limiting)". + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/reactions.md b/translations/es-ES/content/rest/reference/reactions.md new file mode 100644 index 0000000000000..73bbccd66192b --- /dev/null +++ b/translations/es-ES/content/rest/reference/reactions.md @@ -0,0 +1,17 @@ +--- +title: Reacciones +redirect_from: + - /v3/reactions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +### Tipos de reacción + +Cuando creas una reacción, los valores permitidos para el parámetro `content` son los siguientes (con el emoji correspondiente como referencia): + +{% data reusables.repositories.reaction_list %} + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md new file mode 100644 index 0000000000000..67c361165ccd0 --- /dev/null +++ b/translations/es-ES/content/rest/reference/repos.md @@ -0,0 +1,333 @@ +--- +title: Repositorios +allowTitleToDifferFromFilename: verdadero +redirect_from: + - /v3/repos +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Ramas + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Colaboradores + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Comentarios + +### Tipos de medios personalizados para los comentarios de las confirmaciones + +Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más acerca del uso de los tipos de medios en la API [aquí](/rest/overview/media-types). + + application/vnd.github-commitcomment.raw+json + application/vnd.github-commitcomment.text+json + application/vnd.github-commitcomment.html+json + application/vnd.github-commitcomment.full+json + +Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Confirmaciones + +La API de Confirmaciones del Repositorio puede listar, ver y comparar las confirmaciones de un repositorio. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" %} +## Comunidad + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +## Contenido + +Las terminales de esta API te permiten crear, modificar y borrar contenido cifrado en Base64 en un repositorio. Para solicitar el formato sin procesar y interpretado en HTML (cuando sea posible), utiliza los tipos de medios personalizados para el contenido de un repositorio. + +### Tipos de medios personalizados para el contenido de un repositorio + +Los [README](/rest/reference/repos#get-a-repository-readme), [archivos](/rest/reference/repos#get-repository-content), y [symlinks](/rest/reference/repos#get-repository-content) son compatibles con los siguientes tipos de medios: + + application/vnd.github.VERSION.raw + application/vnd.github.VERSION.html + +Utiliza el tipo de medios `.raw` para recuperar el contenido del archivo. + +Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto. + +[Todos los objetos](/rest/reference/repos#get-repository-content) son compatibles con los siguientes tipos de medios personalizados: + + application/vnd.github.VERSION.object + +Utiliza el parámetro de tipo de medios `object` para recuperar el contenido en un formato de objeto consistente sin importar el tipo de contenido. Por ejemplo, en vez de ser una matriz de objetos para un directorio, la respuesta será un objeto con un atributo de `entries` que contenga la matriz de objetos. + +Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Llaves de implementación + +{% data reusables.repositories.deploy-keys %} + +Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Implementaciones + +Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas). + +Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status). + +Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue. + +GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese. + +Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones. + +``` ++---------+ +--------+ +-----------+ +-------------+ +| Tooling | | GitHub | | 3rd Party | | Your Server | ++---------+ +--------+ +-----------+ +-------------+ + | | | | + | Create Deployment | | | + |--------------------->| | | + | | | | + | Deployment Created | | | + |<---------------------| | | + | | | | + | | Deployment Event | | + | |---------------------->| | + | | | SSH+Deploys | + | | |-------------------->| + | | | | + | | Deployment Status | | + | |<----------------------| | + | | | | + | | | Deploy Completed | + | | |<--------------------| + | | | | + | | Deployment Status | | + | |<----------------------| | + | | | | +``` + +Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc. + +Nota que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo_deployment`concede acceso dirigido a los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que los alcances `public_repo` y `repo` otorgan permiso para el código también. + +### Despliegues inactivos + +Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues de ambiente no productivos y no transitorios previos en el mismo repositorio se pondrán como `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor. + +Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`. El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Bifurcaciones + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Invitaciones + +La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación. + +Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones. + +### Invitar a un usuario a un repositorio + +Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/repos#add-a-repository-collaborator)". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Fusionar + +La API de Fusión de Repositorios puede fusionar ramas en un repositorio. Esto logra esencialmente lo mismo que el fusionar una rama con otra en un repositorio local para después cargarlo a {% data variables.product.product_name %}. El beneficio es que esta fusión se lleva a cabo del lado del servidor y no se requiere un repositorio local. Esto lo hace más adecuado para la automatización y para otras herramientas mientras que el mantener repositorios locales sería incómodo e ineficiente. + +El usuario autenticado será el autor de cualquier fusión que se realice a través de esta terminal. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Pages + +La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. La información sobre este sitio y sobre las compilaciones solo es accesible mediante los propietarios autenticados, aún cuando los sitios web son públicos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)". + +En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes: +* `null`: El sitio aún tiene que crearse. +* `queued`: Se solicitó la compilación, pero no ha iniciado. +* `building`: La compilación está en curso. +* `built`: Se creó el sitio. +* `errored`: Indica que ocurrió un error durante la compilación. + +En las terminales de la API de {% data variables.product.prodname_pages %} que devulenven información del sitio de GitHub Pages, las respuestas de JSON incluyen estos campos: +* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. Por ejemplo, `https://username.github.io`. +* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye: + - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_. + - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Lanzamientos + +{% note %} + +**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos. + +{% endnote %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Estadísticas + +La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio. + +### Unas palabras sobre el almacenamiento en caché + +El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible. Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta. + +El SHA de la rama predeterminada del repositorio guarda en caché las estadísticas del repositorio; el subir información a la rama predeterminada restablece el caché de de las estadísticas. + +### Las estadísticas excluyen algunos tipos de confirmaciones + +Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs). + +Para resumir: +- Todas las estadísticas excluyen las confirmaciones de fusión. +- Las estadísticas del colaborador también excluyen a las confirmaciones vacías. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Estados + +La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones. + +Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub. + +Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados. La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación. + +Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`. Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación. + +Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados. + +Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" %} +## Tráfico + +Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "Ver el tráfico de un repositorio." + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %} +{% endfor %} +{% endif %} + +## Webhooks + +La API de Webhooks del Repositorio le permite a los administradoresd e un repositorio administrar los ganchos de post-recepción para el mismo. Los webhooks se pueden administrar utilizando la API de HTTP de JSON, o la API de [PubSubHubbub](#PubSubHubbub). + +Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks). + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} +{% endfor %} + +### Recibir Webhooks + +Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS. + +#### Encabezados de Webhook + +{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles. + +### PubSubHubbub + +GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato: + +`https://github.com/{owner}/{repo}/events/{event}` + +El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)". + +#### Formato de respuesta + +El formato predeterminado es lo que [deberían esperar los ganchos de pre-recepción existentes](/post-receive-hooks/): Un cuerpo de JSON que se envía como parámetro de `payload` en un POST. También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`. + + Accept: application/json + https://github.com/{owner}/{repo}/events/push.json + +#### URL de Rellamado +Las URL de rellamado puede utilizar el protocolo `http://`. + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}También puedes hacer rellamados de `github://` para especificar un servicio de GitHub. +{% data reusables.apps.deprecating_github_services_ghe %} +{% endif %} + + # Send updates to postbin.org + http://postbin.org/123 + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} + # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123 +{% endif %} + +#### Suscribirse + +La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así: + +``` shell +curl -u "user" -i \ + {% data variables.product.api_url_pre %}/hub \ + -F "hub.mode=subscribe" \ + -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \ + -F "hub.callback=http://postbin.org/123" +``` + +Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud. + +##### Parámetros + +| Nombre | Type | Descripción | +| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `hub.mode` | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`. | +| `hub.topic` | `secuencia` | **Requerido**. La URI del repositorio de GitHub al cual suscribirse. La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`. | +| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema. | +| `hub.secret` | `secuencia` | Una llave secreta compartida que genera un HMAC de SHA1 del contenido del cuerpo de salida. Puedes verificar si una carga vino de GitHub si comparas el cuerpo de la solicitud sin procesar con el contenido del encabezado `X-Hub-Signature`. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. | diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md new file mode 100644 index 0000000000000..07e00c6567c33 --- /dev/null +++ b/translations/es-ES/content/rest/reference/scim.md @@ -0,0 +1,49 @@ +--- +title: SCIM +redirect_from: + - /v3/scim +versions: + free-pro-team: '*' +--- + +### Aprovisionamiento de SCIM para las Organizaciones + +Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM para automatizar el aprovisionamiento de la membrecía de las organizaciones de {% data variables.product.product_name %}. La API de {% data variables.product.product_name %} se basa en la versión 2.0 del [estándar de SCIM](http://www.simplecloud.info/). La terminal de SCIM de {% data variables.product.product_name %} que deben utilizar los IdP es: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`. + +{% note %} + +**Nota:** La API de SCIM está disponible solo para las organizaciones en [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) que tienen habilitado el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso). Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +{% endnote %} + +### Autenticar las llamadas a la API de SCIM + +Debes autenticarte como un propietario de una organización de {% data variables.product.product_name %} para utilizar la API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También puedes utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu orgnización que cuenta con el SSO de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). + +### Mapeo de los datos de SAML y de SCIM + +El IdP de SAML y el cliente de SCIM deben utilizar valores coincidentes de `NameID` y `userName` para cada usuario. Esto le permite al usuario que se autentica mediante SAML el poder enlazarse con su identidad aprovisionada de SCIM. + +### Atributos de Usuario de SCIM compatibles + +| Nombre | Type | Descripción | +| ---------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `userName` | `secuencia` | El nombre de usuario para el usuario. | +| `name.givenName` | `secuencia` | El primer nombre del usuario. | +| `name.lastName` | `secuencia` | El apellido del usuario. | +| `emails` | `arreglo` | Lista de correos electrónicos del usuario. | +| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. | +| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. | +| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). | + +{% note %} + +**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula: + +```shell +GET /scim/v2/organizations/{org}/Users/{scim_user_id} +``` + +{% endnote %} + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/search.md b/translations/es-ES/content/rest/reference/search.md new file mode 100644 index 0000000000000..eb0314b471913 --- /dev/null +++ b/translations/es-ES/content/rest/reference/search.md @@ -0,0 +1,157 @@ +--- +title: Search +redirect_from: + - /v3/search +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +La API de Búsqueda te ayuda a buscar el elemento específico que quieres encontrar. Por ejemplo, puedes buscar un usuario o un archivo específico en el repositorio. Tómalo como el simil de realizar una búsqueda en Google. Se diseñó para ayudarte a encontrar el resultado exacto que estás buscando (o tal vez algunos de los resultados que buscas). Tal como la búsqueda en Google, a veces quieres ver algunas páginas de los resultados de búsqueda para que puedas encontrar el elemento que mejor satisfaga tus necesidades. Para satisfacer esta necesidad, la API de Búsqueda de {% data variables.product.product_name %} proporciona **hasta 1,000 resultados por búsqueda**. + +Puedes delimitar tu búsqueda utilizando consultas. Para aprender más sobre la sintaxis de las consultas de búsqueda, dirígete a "[Construir una consulta de búsqueda](/rest/reference/search#constructing-a-search-query)". + +### Clasificar los resultados de la búsqueda + +A menos de que se proporcione algún otro tipo de opción como parámetro de consulta, los resultados se clasificarán de acuerdo a la exactitud de la coincidencia en orden descendente. Varios factores se combinan para impulsar el elemento más relevante hasta arriba de la lista de resultados. + +### Limite de tasa + +La API de Búsqueda tiene un límite de tasa personalizado. Para las solicitudes que utilizan [Autenticación Básica](/rest#authentication), [OAuth](/rest#authentication), o [secreto e ID de cliente](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), puedes hacer hasta 30 solicitudes por minuto. Para las solicitudes sin autenticar, el límite de tasa te permite hacer hasta 10 por minuto. + +{% data reusables.enterprise.rate_limit %} + +Consulta la [documentación del límite de tasa](/rest/reference/rate-limit) para obtener más detalles sobre cómo determinar tu estado de límite de tasa actual. + +### Construir una consulta de búsqueda + +Cada terminal en la API de búsqueda utiliza [parámetros de búsqueda](https://en.wikipedia.org/wiki/Query_string) para realizar búsqeudas en {% data variables.product.product_name %}. Observa la terminal individual an la API de Búsqueda para encontrar un ejemplo que incluye los parámetros de consulta y de terminal. + +Una consulta puede contener cualquier combinación de calificadores de búsqueda que sea compatible con {% data variables.product.product_name %}. El formato de esta consulta de búsqueda es: + +``` +SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N +``` + +Por ejemplo, si quisieras buscar todos los _repositorios_ que pertenecen a `defunkt` y que contienen la palabra `GitHub` y `Octocat` en el archivo de README, utilizarías la siguiente consulta con la terminal de _buscar repositorios_: + +``` +GitHub Octocat in:readme user:defunkt +``` + +**Nota:** Asegúrate de utilizar el codificador HTML preferido de tu lenguaje de programación para construir tus cadenas de consulta. Por ejemplo: +```javascript +// JavaScript +const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); +``` + +Consulta la sección "[Buscar en GitHub](/articles/searching-on-github/)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas, o para que excluyan resultados, consulta "[Entender la sintaxis de búsqueda](/articles/understanding-the-search-syntax/)". + +### Limitaciones sobre la longitud de la consulta + +La API de búsqueda no es compatible con consultas que: +- sean mayores a 256 caracteres (sin incluir los operadores o calificativos). +- tengan más de cinco operadores de `AND`, `OR`, o `NOT`. + +Estas consultas de búsqueda devolverán un mensaje de error de "Validation failed". + +### Tiempos excedidos y resultados incompletos + +Para que la API de Búsqueda se mantenga rápida para todos, limitamos el tiempo que puede jecutarse cualquier consulta específica. Para las consultas que [exceden el límite de tiempo](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), la API devuelve las coincidencias que ya se habían encontrado antes de exceder el tiempo, y la respuesta tiene la propiedad `incomplete_results` como `true`. + +Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Puede que se hayan encontrado más resultados, pero también puede que no. + +### Errores de acceso o resultados de búsqueda faltantes + +Necesitas autenticarte exitosamente y tener acceso a los repositorios en tus consultas de búsqueda, de lo contrario, verás un error de `422 Unprocessible Entry` con un mensaje de "Validation Failed". Por ejemplo, tu búsqueda fallará si tu consulta incluye los calificadores `repo:`, `user:`, o `org:` que solicitan los recursos a los cuales no tienes acceso cuando inicias sesión en {% data variables.product.prodname_dotcom %}. + +Cuando tu consulta de búsqueda solicita recursos múltiples, la respuesta solo contendrá aquellos a los que tengas acceso y **no** proporcionará un mensaje de error que liste los recursos que no se devolvieron. + +Por ejemplo, si tu consulta de búsqueda quiere buscar en los repositorios `octocat/test` y `codertocat/test`, pero solo tienes acceso a `octocat/test`, tu respuesta mostrará los resultados de búsqueda para `octocat/test` y no mostrará nada para `codertocat/test`. Este comportamiento simula cómo funciona la búsqueda en {% data variables.product.prodname_dotcom %}. + +{% include rest_operations_at_current_path %} + + +### Metadatos en el texto coincidente + +En GitHub, puedes utilizar el contexto que te proporcionan los extractos de código y los puntos destacados en los resultados de búsqueda. La API de Búsqueda ofrece metadatos adicionales que te permiten resaltar los términos de búsqueda coincidentes cuando se muestran los resultados de la búsqueda. + +![resaltado del fragmento de código](/assets/images/text-match-search-api.png) + +Las solicitudes pueden decidir recibir esos fragmentos de texto en la respuesta, y cada fragmento se acompaña de intervalos numéricos que identifican la ubicación exacta de cada término de búsqueda coincidente. + +Para obtener estos metadatos en tus resultados de búsqueda, especifica el tipo de medios `text-match` en tu encabezado de `Accept`. + +```shell +application/vnd.github.v3.text-match+json +``` + +Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra en la carga útil de JSON llamada `text_matches`, la cual proporciona información acerca de la posición de tus términos de búsqueda dentro del texto y la `property` que incluye dicho término de búsqueda. Dentro de la matriz `text_matches`, cada objeto incluye los siguientes atributos: + +| Nombre | Descripción | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `object_url` | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda. | +| `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica. | +| `property` | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) | +| `fragment` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. | +| `matches` | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.) | + +#### Ejemplo + +Si utilizas cURL y también el [ejemplo de búsqueda de informe de problemas](#search-issues-and-pull-requests) anterior, nuestra solicitud de la API se vería así: + +``` shell +curl -H 'Accept: application/vnd.github.v3.text-match+json' \ +'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc' +``` + +La respuesta incluirá una matriz de `text_matches` para cada resultado de búsqueda. En el JSON que se muestra a continuación, tenemos dos objetos en la matriz `text_matches`. + +La primera coincidencia de texto ocurrió en la propiedad de `body` del informe de problemas. Aquí vemos un fragmento de texto del cuerpo del informe de problemas. El término de búsqueda (`windows`) aparece dos veces dentro de ese fragmento, y tenemos los índices para cada ocurrencia. + +La segunda coincidencia de texto ocurrió en la propiedad `body` de uno de los comentarios del informe de problemas. Tenemos la URL para el comentario del informe de problemas. Y, por supuesto, vemos un fragmento de texto del cuerpo del comentario. El término de búsqueda (`windows`) se muestra una vez dentro de ese fragmento. + +```json +{ + "text_matches": [ + { + "object_url": "https://api.github.com/repositories/215335/issues/132", + "object_type": "Issue", + "property": "body", + "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n", + "matches": [ + { + "text": "windows", + "indices": [ + 14, + 21 + ] + }, + { + "text": "windows", + "indices": [ + 78, + 85 + ] + } + ] + }, + { + "object_url": "https://api.github.com/repositories/215335/issues/comments/25688", + "object_type": "IssueComment", + "property": "body", + "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n", + "matches": [ + { + "text": "Windows", + "indices": [ + 163, + 170 + ] + } + ] + } + ] +} +``` diff --git a/translations/es-ES/content/rest/reference/secret-scanning.md b/translations/es-ES/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000000..287759e303071 --- /dev/null +++ b/translations/es-ES/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Escaneo de secretos +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +La API de {% data variables.product.prodname_secret_scanning %} te permite recuerar y actualizar las alertas de escaneo de secretos desde un repositorio privado. Para obtener más información sobre el escaneo de secretos para repositorios privados, consulta la sección "[Asegurar tu repositorio](/github/administering-a-repository/securing-your-repository)". + +{% include rest_operations_at_current_path %} diff --git a/translations/es-ES/content/rest/reference/teams.md b/translations/es-ES/content/rest/reference/teams.md new file mode 100644 index 0000000000000..fb85a5def4f09 --- /dev/null +++ b/translations/es-ES/content/rest/reference/teams.md @@ -0,0 +1,61 @@ +--- +title: Equipos +redirect_from: + - /v3/teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Esta API solo está disponible para los miembros autenticados de la [organization](/rest/reference/orgs) del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. {% data variables.product.prodname_dotcom %} genera el `slug` del equipo a partir del `name` del mismo. + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +## Debates + +La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Comentarios de debate + +La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Esta API solo está disponible para los miembros autenticados de la organization del equipo. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Miembros + +Esta API solo está disponible para los miembros autenticados de la organization del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +{% note %} + +**Nota:** Cuando configuras la sincornizacion de equipos para un equipo con el proveedor de identidad (IdP) de tu organización, verás un error si intentas utilizar la API para hacer cambios en la membrecía de dicho equipo. Si tienes acceso para administrar las membrecías de usuario en tu IdP, puedes administrar la membrecía del equipo de GitHub a través de tu proveedor de identidad, lo cual agrega y elimina automáticamente a los miembros en una organización. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub". + +{% endnote %} + +{% endif %} + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +## Sincronización de equipos + +La API de sincronización de equipos te permite administrar las conexiones entre los equipos de {% data variables.product.product_name %} y los grupos del proveedor de identidad (IdP) externo. Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste. El token que utilizas para autenticarte también necesitará autorizarse para su uso con tu proveedor IdP (SSO). Para obtener más información, consulta la sección "Autorizar un token de acceso personal para su uso con una organización que tiene inicio de sesión único de SAML". + +Puedes administrar a los miembros del equipo de GitHub a través de tu IdP con la sincronización de equipos. Ésta se debe habilitar para usar la API de Sincronización de Equipos. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub". + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} diff --git a/translations/es-ES/content/rest/reference/users.md b/translations/es-ES/content/rest/reference/users.md new file mode 100644 index 0000000000000..775aab18ded83 --- /dev/null +++ b/translations/es-ES/content/rest/reference/users.md @@ -0,0 +1,55 @@ +--- +title: Usuarios +redirect_from: + - /v3/users +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +Muchos de los recursos en la API de los usuarios proporcionan un atajo para obtener información acerca del usuario autenticado actualmente. Si una URL de solicitud no incluye un parámetro de `{username}`, entonces la respuesta será para el usuario que inició sesión (y debes pasar la [información de autenticación](/rest/overview/resources-in-the-rest-api#authentication) con tu solicitud).{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} La información privada adicional tal como si un usuario tiene habilitada la autenticación bifactorial se incluye cuando se está autenticado a través de la autenticación básica o a través de OAuth con el alcance de `user`.{% endif %} + +{% for operation in currentRestOperations %} + {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} +{% endfor %} + +{% if currentVersion == "free-pro-team@latest" %} +## Bloquear usuarios + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +## Emails (Correos electrónicos) + +Administrar las direcciones de correo electrónico a través de la API requiere que ingreses con la autenticación básica o con OAuth con un alcance correcto para la terminal. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + +## Seguidores + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Llaves SSH de Git + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} +{% endfor %} + +## Claves GPG + +Los datos que se devuelven en el campo de respuesta de `public_key` no son una llave con formato de GPG. Cuando un usuario carga una llave GPG, se interpreta y la llave pública criptográfica se extrae y se almacena. Esta llave criptográfica es lo que devuelven las API en esta página. Esta llave no es apta para utilizarse directamente con programas como GPG. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %} +{% endfor %} diff --git a/translations/es-ES/data/glossaries/README.md b/translations/es-ES/data/glossaries/README.md new file mode 100644 index 0000000000000..7961aba1f36f6 --- /dev/null +++ b/translations/es-ES/data/glossaries/README.md @@ -0,0 +1,7 @@ +# Glosarios + +Los siguientes archivos comprenden nuestro [Glosario de Crowdin](https://support.crowdin.com/glossary/): + +* `external.yml` contiene las entradas de glosario de cara al usuario. +* `internal.yml` contiene las entradas que solo utilizan los traductores. Estos términos se muestran en la IU de Crowdin para proporcionar contexto adicional a los traductores sobre lo que están traduciendo, además de sugerir una secuencia localizada para ese término. +* `candidates.yml` contiene términos que podrían estar potencialmente tanto en el glosario interno como en el externo, pero no se han definido aún. diff --git a/translations/es-ES/data/glossaries/candidates.yml b/translations/es-ES/data/glossaries/candidates.yml new file mode 100644 index 0000000000000..32ca2e6c9bcae --- /dev/null +++ b/translations/es-ES/data/glossaries/candidates.yml @@ -0,0 +1,203 @@ +--- +- + term: Premium Support +- + term: Standard Support +- + term: Incident +- + term: submit +- + term: contact person +- + term: Severity +- + term: Service Level Agreement +- + term: credit +- + term: account management team +- + term: ticket +- + term: Enterprise Support +- + term: support portal +- + term: Urgent +- + term: High +- + term: Moderate +- + term: Low +- + term: extended support bundle +- + term: company name +- + term: privacy mode +- + term: Authentication method +- + term: hours of operation +- + term: leadership +- + term: Escalate to Management +- + term: missed ticket responses +- + term: Geo-replication +- + term: production system +- + term: de-identified of sensitive data +- + term: business justification +- + term: Qualifying credits +- + term: Contacting sales +- + term: Contacting training +- + term: Outbound +- + term: alphanumeric +- + term: quotation +- + term: pricing plan +- + term: unit plan +- + term: role +- + term: redeem coupon +- + term: free plan +- + term: gratis +- + term: discount +- + term: stale review +- + term: contribution credit +- + term: conflict marker +- + term: Work-in-progress commit +- + term: ancestor commit +- + term: contribution graph +- + term: approve +- + term: dismiss +- + term: stage +- + term: invitation +- + term: uptime +- + term: discussion +- + term: service and privacy policy +- + term: reinstate +- + term: admin center +- + term: academic role +- + term: educational discount +- + term: disposable domain +- + term: roll over +- + term: quota +- + term: private key +- + term: public key +- + term: hotpaching +- + term: feature release +- + term: co-authored commit +- + term: subdomain isolation +- + term: built-in authentication +- + term: abuse rate limits +- + term: load average +- + term: ephemeral +- + term: pre-flight check +- + term: account representative +- + term: unified search +- + term: dormant user +- + term: delivery +- + term: legal hold +- + term: unsolicited response SSO +- + term: IdP initiated SSO +- + term: authenticity of messages +- + term: All rights reserved +- + term: Campus Advisors +- + term: Campus Experts +- + term: collaborative development models +- + term: unified view +- + term: three-dot diff +- + term: rich diff +- + term: conversation +- + term: public gist / secret gist +- + term: extension +- + term: procurement companies +- + term: renewal orders +- + term: per-user pricing +- + term: watcher +- + term: Required commit signing +- + term: Check Suites +- + term: classroom discount +- + term: student developer pack +- + term: academic research discount +- + term: Stargazers +- + term: spam unflagging diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml new file mode 100644 index 0000000000000..cef46fb9e1dc5 --- /dev/null +++ b/translations/es-ES/data/glossaries/external.yml @@ -0,0 +1,763 @@ +--- +- + term: '@mention' + description: para notificar a una persona en GitHub usando "@" antes de su nombre de usuario. Los usuarios en una organización en GitHub también pueden ser parte de un equipo que puede ser mencionado. +- + term: access token + description: >- + Un token que se usa en lugar de una contraseña cuando se realizan operaciones Git a través de HTTPS con Git en la línea de comandos o la API. También denominado un token de acceso personal. +- + term: account recovery token + description: >- + La credencial de autenticación almacenada como parte de la configuración de recuperación de una cuenta denominada Recuperar cuentas en otro lugar que te permite almacenar esta credencial de respaldo. +- + term: API preview + description: >- + Una manera de probar nuevas API y cambiar a métodos API existentes antes de que se vuelvan parte de la API de GitHub oficial. +- + term: appliance + description: >- + Una aplicación de software combinada con Sólo lo Necesario de un Sistema Operativo (JeOS) para funcionar de manera óptima en el hardware estándar de la industria (generalmente, un servidor) o en una máquina virtual. +- + term: asignatario + description: El usuario que es asignado a una propuesta. +- + term: authentication code + description: >- + Un código que suministrarás, además de tu contraseña GitHub, cuando inicias sesión con 2FA a través del buscador. Este código se genera ya sea mediante una aplicación o se envía a tu teléfono mediante un mensaje de texto. También denominado "Código de autenticación 2FA". +- + term: rama base + description: La rama en la que los cambios se combinan cuando fusionas una solicitud de extracción. Cuando creas una solicitud de extracción, puedes cambiar la rama base desde la rama predeterminada del repositorio a otra rama si lo requieres. +- + term: basic authentication + description: >- + Un método de autenticación en donde las credenciales se envían como texto sin cifrar. +- + term: bio + description: >- + La descripción generada por el usuario encontrada en un perfil: https://help.github.com/articles/adding-a-bio-to-your-profile/ +- + term: billing cycle + description: El intervalo de tiempo para tu plan de facturación específico. +- + term: billing email + description: >- + La dirección de correo electrónico de la organización donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. +- + term: billing manager + description: El miembro de la oranización que administra los parámetros de facturación para una organización. +- + term: billing plan + description: >- + Los planes de pago para usuarios y organizaciones que incluyen características establecidas para cada tipo de plan. +- + term: blame + description: >- + La función "último responsable" en Git describe las últimas modificaciones para cada línea e un archivo, que generalmente muestra la revisión, el autor y la hora. Esto es útil, por ejemplo, para detectar cuándo se agregó una función o qué confirmación de cambios llevó a un error en particular. +- + term: block + description: >- + Eliminar la posibilidad de un usuario de colaborar con los repositorios de una organización. +- + term: branch + description: >- + Una rama es una versión paralela de un repositorio. El repositorio la contiene, pero no afecta la rama primaria o principal, lo que te permite trabajar libremente sin interrumpir la versión "activa". Una vez que haz hecho las modificaciones que deseabas, puedes fusionar tu rama de nuevo en la rama principal para publicar tus modificaciones. +- + term: branch restriction + description: >- + Una restricción que los administradores de repositorio pueden activar para que solo ciertos usuarios o equipos puedan subir o hacer ciertas modificaciones en la rama. +- + term: Business plan + description: >- + Un plan de facturación de la organización donde puedes colaborar en repositorios públicos y privados ilimitados, permitir o solicitar a los miembros de la organización autenticar GitHub usando SSO de SAML y aprovisionar y desaprovisionar acceso con SAML o SCIM. +- + term: CA certificate + description: >- + Un certificado digital emitido por una entidad de certificación (CA) que garantiza que hay conexiones válidas entre dos máquinas, como el equipo de un usuario y GitHub.com y que verifica la titularidad de un sitio. +- + term: card + description: Un cuadrado móvil dentro del tablero de proyecto asociado con una propuesta o una solicitud de extracción. +- + term: Verificación + description: >- + Una revisión es un tipo de revisión de estado en {% data variables.product.product_name %}. Ver "[Revisiones de estado](#status-checks)." +- + term: checkout + description: >- + Puedes usar el "control Git" en la línea de comandos para crear una nueva rama, modificar tu rama de trabajo actual a una rama diferente o incluso cambiar a una versión diferente de un archivo desde una rama diferente con "control git [branchname] [path to file]". La acción "control" actualiza todo a parte del árbol de trabajo con un objeto de árbol o blob desde la base de datos de objetos y actualiza el índice y HEAD si todo el árbol de trabajo apunta a una rama nueva. +- + term: cherry-picking + description: >- + Para elegir un subconjunto de modificaciones de una serie de modificaciones (generalmente, confirmaciones de cambios) y registrarlas como una nueva serie de modificaciones además de un código base diferente. En Git, esto lo realiza el comando "cherry-pick Git" para extraer el cambio introducido por una confirmación de cambios en otra rama y para registrarlo en función de la sugerencia de la rama actual como una confirmación de cambios nueva. +- + term: child team + description: >- + Dentro de los equipos anidados, el subequipo que hereda los permisos de acceso y las @menciones del equipo padre. +- + term: clean + description: >- + Un árbol de trabajo está limpio si corresponde a la revisión referenciada en el HEAD actual. Consulta también "sucio". +- + term: clone + description: >- + Un clon es una copia de un repositorio que vive en tu equipo en vez de en algún lugar del servidor del sitio web o el acto de realizar dicha copia. Cuando haces un clon, puedes editar los archivos en tu editor preferido y usar Git para hacer un seguimiento de tus modificaciones sin tener que estar en línea. El repositorio que clonas sigue conectado a la versión remota para que puedas subir tus modificaciones locales al remoto para mantenerlos sincronizados cuando estás en línea. +- + term: clustering + description: >- + La posibilidad de ejecutar los servicios GitHub Enterprise en varios nodos y equilibrar la carga de las solicitudes entre ellos. +- + term: Code frequency graph + description: >- + Un gráfico del repositorio que muestra las adiciones y las eliminaciones de contenido para cada semana en el historial de un repositorio. +- + term: code of conduct + description: Documento que define las normas para participar en una comunidad. +- + term: code owner + description: >- + Persona designada como propietario de una parte del código del repositorio. Se le solicita automáticamente al propietario del código que realice una revisión cuando alguien abre una solicitud de extracción (no en el modo borrador) que introduce cambios en el código que posee el propietario. +- + term: collaborator + description: >- + Un colaborador es una persona con acceso de escritura a un repositorio que ha sido invitada a contribuir a dicho repositorio por su propietario. +- + term: commit + description: >- + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. +- + term: commit author + description: El usuario que realiza la confirmación de cambios. +- + term: Commit graph + description: >- + Un gráfico del repositorio que muestra todas las confirmaciones de cambios realizadas a un repositorio durante en el último año. +- + term: commit ID + description: También conocido como SHA. Un hash de suma de comprobación de 40 caracteres que identifica la confirmación de cambios. +- + term: commit message + description: >- + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. +- + term: rama de comparación + description: >- + La rama que utilizas para crear una solicitud de extracción. Esta rama se compara con la rama base que escojas para la solicitud de extracción, y los cambios se identifican. Cuando la solicitud de extracción se fusiona, esta rama se actualiza con los cambios de la rama de comparación, también conocida como la "rama principal" de la solicitud de extracción. +- + term: integración continua + description: >- + También conocida como CI. Un proceso que ejecuta pruebas y compilaciones automatizadas una vez que una persona confirma los cambios para un repositorio configurado en GitHub. La CI es una buena práctica común en el desarrollo de software que ayuda a detectar errores. +- + term: contribution graph + description: >- + La parte del perfil de un usuario que muestra sus contribuciones en un período de hasta un año, día a día. +- + term: contribution guidelines + description: Un documento que explica cómo las persona deberían contribuir con tu proyecto. +- + term: contributions + description: >- + Actividades específicas en GitHub que: - Agregarán un cuadrado al gráfico de contribuciones de un usuario: "[Que cuenta como una contribución](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Agregarán actividades a la cronología de un usuario en su perfil: "[Actividad de contribución](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" +- + term: contributor + description: >- + Un colaborador es alguien que no tiene acceso de colaborador a un repositorio, pero ha contribuido en un proyecto y tenía una solicitud de extracción que había abierto fusionada en el repositorio. +- + term: Contributors graph + description: Un gráfico del repositorio que muestra los principales 100 colaboradores de un repositorio. +- + term: coupon + description: >- + Un código proporcionado por GitHub que los usuarios o las organizaciones pueden usar para pagar el total o parte de su suscripción. +- + term: cron + description: Un programador de trabajo con límite de tiempo en los sistemas operativos de los equipos tipo Unix. +- + term: cURL + description: Se usa en las líneas de comandos o scripts para transferir datos. +- + term: Tablero + description: >- + Tu tablero personal es el concentrador principal para tu actividad en GitHub. Desde éste, puedes llevar el control de incidentes y solicitudes de extracción en los que estás trabajando o a los que estás siguiendo, navegar a tus repositorios y páginas de equipo principales, y aprender sobre la actividad reciente en los repositorios que estás observando o en los que estás participando. También puedes descubrir nuevos repositorios, los cuales se recomiendan con base en los usuarios que sigues y en los repositorios que has marcado con una estrella. Para ver únicamente la actividad de una organización específica, visita tu tablero de organización. Para obtener más información, consulta la sección "[Acerca de tu tablero profesional](/articles/about-your-personal-dashboard)" o "[Acerca de tu tablero de organización](/articles/about-your-organization-dashboard)." +- + term: default branch + description: >- + La rama base para las solicitudes de cambios nuevas y las confirmaciones de código en un repositorio. Cada repositorio tiene por lo menos una rama, la cual crea Git cuando lo inicializas. Habitualmente, la primera rama se llama `main`, y a menudo es la predeterminada. +- + term: Dependents graph + description: >- + Un gráfico del repositorio que muestra los paquetes, los proyectos y los repositorios que dependen de un repositorio público. +- + term: Gráfico de dependencias + description: >- + Un gráfico del repositorio que muestra los paquetes y los proyectos de los que depende el respositorio. +- + term: deploy key + description: >- + Una clave de implementación es una clave SSH que se almacena en tu servidor y concede acceso a un único repositorio GitHub. Esta clave se adjunta directamente al repositorio en lugar de a una cuenta de usuario personal. +- + term: detached HEAD + description: >- + Git te advertirá si estás trabajando en un HEAD separado, lo que significa que Git no apunta a una rama y que cualquier confirmación de cambios que realices, no aparecerá en el historial de confirmaciones de cambios. Por ejemplo, cuando revisas una confirmación de cambios arbitraria que no es la última confirmación de cualquier rama en particular, estás trabajando en un "HEAD separado". +- + term: diagnostics + description: Una descripción de los parámetros y el entorno de una instancia de GitHub Enterprise. +- + term: diff + description: >- + Una diferencia es la diferencia en cambios entre dos confirmaciones de cambios o los cambios guardados. La diferencia describirá visualmente lo que se agregó o se eliminó de un archivo desde su última confirmación de cambios. +- + term: dirty + description: >- + Un árbol de trabajo se considera "sucio" si contiene modificaciones que no han sido confirmadas en la rama actual. +- + term: email notifications + description: Las notificaciones enviadas a la dirección de correo electrónico de un usuario. +- + term: Enterprise account + description: Las cuentas empresariales te permiten administrar centralmente las políticas y facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %} +- + term: Explorer + description: >- + Una instancia de GraphiQL, que es una "IDE GraphQL en el explorador interactiva gráfica". +- + term: fast-forward + description: >- + Un avance rápido es un tipo especial de fusión donde tienes una revisión y se "fusionan" los cambios de otra rama que resulta ser un descendiente de lo que tienes. En este caso, no realizas una confirmación de cambios de fusión nueva, si no que, en cambio, solo actualizas esta revisión. Esto sucederá con frecuencia en una rama de seguimiento remoto de un repositorio remoto. +- + term: feature branch + description: >- + Una rama usada para experimentar con una nueva función o corregir una propuesta que no está en producción. También llamada rama de tema. +- + term: fenced code block + description: 'Un bloque de código sangrado que puedes crear con el formato Markdown de GitHub utilizando triple diagonal inversa \`\`\` antes y después del mismo. Consulta el [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' +- + term: fetch + description: >- + Cuando usas `git fetch`, estás agregando cambios desde el repositorio remoto a tu rama de trabajo local sin confirmarlos. A diferencia de `git pull`, la recuperación te permite revisar los cambios antes de confirmarlos en tu rama local. +- + term: following (users) + description: Obtener notificaciones acerca de la actividad y las contribuciones de otros usuarios. +- + term: force push + description: >- + Un empuje Git que sobreescribe el repositorio remoto con los cambios locales sin tener en cuenta los conflictos. +- + term: fork + description: >- + Una bifurcación es una copia personal del repositorio de otro usuario que vive en tu cuenta. Las bifurcaciones te permiten realizar cambios libremente en un proyecto sin afectar el repositorio ascendente original. También puedes abrir una solicitud de extracción en el repositorio ascendente y mantener tu bifurcación sincronizada con los últimos cambios ya que ambos repositorios aún están conectados. +- + term: Free plan + description: >- + El plan de facturación de la cuenta de un usuario que es gratuito. Los usuarios pueden colaborar en repositorios públicos ilimitados con colaboradores ilimitados. +- + term: Gist + description: >- + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. +- + term: Git + description: >- + Git es un programa de código abierto para hacer un seguimiento de los cambios en los archivos de texto. Fue escrito por el autor del sistema operativo Linux y es la tecnología principal sobre la cual está contruida GitHub, la interfaz social y de usuario. +- + term: GitHub App + description: >- + Las Apps GitHub ofrecen un servicio a toda una organización y usan su propia identidad cuando desempeñan su función. Pueden ser instaladas directamente en las cuentas de usuario y de las organizaciones y pueden garantizar acceso a repositorios específicos. Vienen con permisos exhaustivos y webhooks integrados. +- + term: GitHub Flavored Markdown + description: Markdown específico de GitHub usado para dar formato a la prosa y al código en GitHub. Consulta [Formato Markdown específico de GitHub](https://github.github.com/gfm/) o [Introducción a la escritura y el formato en GitHub](/articles/getting-started-with-writing-and-formatting-on-github). +- + term: GitHub Importer + description: >- + Una herramienta que importa de forma rápida repositorios de código fuente, incluido el historial de revisiones y confirmaciones de cambios, a GitHub para los usuarios. +- + term: GitHub Jobs + description: >- + Un sitio de GitHub donde los empleadores pueden publicar empleos en los que los usuarios de GitHub pueden estar interesados. +- + term: GitHub Marketplace + description: >- + Un subsitio para que los usuarios y las organizaciones de GitHub compren e instalen aplicaciones que extiendan y complementen su flujo de trabajo. +- + term: GitHub Pages + description: >- + También se las conoce como Páginas. Un servicio de alojamiento del sitio estático diseñado para alojar tus páginas del proyecto, de la organización o personales directamente desde un repositorio de GitHub. +- + term: GitHub Wiki + description: Una sección para alojar documentación de estilo wiki en un repositorio de GitHub. +- + term: gitfile + description: >- + Un archivo `.git` simple, que siempre está en la raíz de un árbol de trabajo y apunta al directorio de Git, que tiene el repositorio completo de Git y sus meta datos. Puedes ver este archivo para tu repositorio en la línea de comandos con `git rev-parse --git-dir`. que es el repositorio real. +- + term: GraphQL + description: >- + Un lenguaje de consulta para las API y un tiempo de ejecución para cumplir con esas consultas con tus datos existentes. +- + term: HEAD + description: Una confirmación definida de una rama, a menudo la confirmación más reciente en la punta de la rama. +- + term: rama principal + description: La rama cuyos cambios se combinaron en la rama base cuando fusionas una solicitud de extracción. También conocida como la "rama de comparación". +- + term: 'Hello, World' + description: >- + Un programa "Hola, Mundo" es un programa que genera o muestra "Hola, Mundo" para un usuario. Como este programa generalmente es muy simple, se suele usar como un ejemplo de una sintaxis básica de lenguaje de programación y sirve como un primer ejercicio común para aprender un lenguaje de programación nuevo. +- + term: alta disponibilidad + description: >- + Un sistema o componente que está continuamente operativo por un conveniente largo período de tiempo. +- + term: hook + description: >- + Durante la ejecución normal de varios comandos Git, se realizan llamadas a scripts opcionales que le permiten a un programador agregar funcionalidad o comprobación. Generalmente, los ganchos permiten que un comando sea preverificado y potencialmente interrumpido y permite una notificación posterior una vez realizada la operación. +- + term: hostname + description: >- + Sobrenombres en lenguaje natural que corresponden a la dirección de un dispositivo conectado a una red. +- + term: identicon + description: >- + Una imagen autogenerada usada como foto de perfil predeterminada cuando el usuario inicia sesión en GitHub. Los usuarios pueden reemplazar su identicon con su propia foto de perfil. +- + term: identity provider + description: >- + También conocido como IdP. Un proveedor de confianza que te permite usar el inicio de sesión único (SSO) de SAML para acceder a otros sitios web. +- + term: instance + description: >- + La copia privada de GitHub de una organización contenida dentro de una máquina virtual que ellos configuran y controlan. +- + term: integration + description: >- + Una aplicación de terceros que se integra con GitHub. Estas pueden ser Apps GitHub, Apps OAuth o webhooks. +- + term: issue + description: >- + Las propuestas son preguntas, tareas o mejoras sugeridas relacionadas al repositorio. Las propuestas pueden ser creadas por cualquiera (para repositorios públicos) y son moderadas por los colaboradores del repositorio. Cada propuesta contiene su propio hilo de debate. También puedes categorizar una propuesta con etiquetas y asignársela a alguien. +- + term: Jekyll + description: Un generador de sitio estático para sitios de una organización, de un proyecto o personales. +- + term: Jekyll Theme Chooser + description: >- + Una manera automatizada de seleccionar un tema visual para tu sitio Jekyll sin editar ni copiar archivos CSS. +- + term: key fingerprint + description: Una secuencia corta de bytes usados para identificar una clave pública más larga. +- + term: keychain + description: Un sistema de administración de contraseñas en macOS. +- + term: keyword + description: Una palabra específica que cierra una propuesta cuando se usa dentro de una solicitud de extracción. +- + term: label + description: >- + Una etiqueta en una propuesta o solicitud de extracción. Los repositorios vienen con una serie de etiquetas predeterminadas, pero los usuarios pueden crear etiquetas personalizadas. +- + term: LFS + description: >- + Large File Storage de Git. Una extensión de Git de código abierto para controlar las versiones de archivos de gran tamaño. +- + term: license + description: >- + Un documento que puedes incluir con tu proyecto para hacerle saber a las personas qué pueden y qué no pueden hacer con tu código fuente. +- + term: Linguist + description: >- + Una biblioteca usada en GitHub para detectar lenguajes blob, ignorar archivos binarios o vendorizado, suprimir los archivos generados en diffs y generar gráficos de desglose del lenguaje. +- + term: line comment + description: Un comentario dentro de una solicitud de extracción es una línea de código específica. +- + term: line ending + description: >- + Un caracter o caracteres invisibles que simbolizan el final de una línea en un archivo de texto. +- + term: locked personal account + description: >- + Una cuenta personal a la que el usuario no puede acceder. Las cuentas se bloquean cuando los usuarios degradan su cuenta paga a una gratis o si su plan de pago se venció. +- + term: Management Console + description: >- + Una sección dentro de la interfaz GitHub Enterprise que contiene funciones administrativas. +- + term: Markdown + description: >- + Markdown es un formato de archivo semántico increíblemente simple, no muy diferente a .doc, .rtf y .txt. Markdown que hace que sea fácil incluso para aquellos sin una formación en publicación web escribir prosa (incluso con enlaces, listas, viñetas, etc.) y mostrarla como un sitio web. GitHub admite Markdown y usa un formulario particular de Markdown llamado formato Markdown de GitHub. Consulta [Formato Markdown específico de GitHub](https://github.github.com/gfm/) o [Introducción a la escritura y el formato en GitHub](/articles/getting-started-with-writing-and-formatting-on-github). +- + term: Markup + description: Un sistema para anotar y dar formato a un documento. +- + term: main + description: >- + La rama predeterminada de desarrollo. Cuando creas un repositorio de Git, se crea una rama que se llama `main` y se convierte en la rama activa. En la mayoría de los casos, esta contiene el desarrollo local, aunque esto es puramente por convención y no es forzoso. +- + term: master + description: >- + La rama predeterminada en muchos de los repositorios de Git. Predeterminadamente, cuando creas un repositorio de Git nuevo en la línea de comandos, se crea una rama que se llama `master`. Muchas de las herramientas ahora utilizan un nombre alterno para la rama predeterminada. Por ejemplo, cuando creas un repositorio nuevo en GitHub, la rama predeterminada se llama `main`. +- + term: Members graph + description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio. +- + term: mention + description: >- + Una notificación enviada a un usuario anteponiendo el símbolo @ al nombre de usuario. Los usuarios de una organización de GitHub también pueden ser parte de un equipo que puede ser mencionado. +- + term: merge + description: >- + La fusión toma los cambios de una rama (en el mismo repositorio o de una bifurcación) y los aplica en otra. Esto suele suceder como una "solicitud de extracción" (que puede considerarse como una solicitud a fusionar) o mediante la línea de comandos. Una fusión se puede realizar mediante una solicitud de extracción a través de la interfaz web GitHub.com si no hay cambios conflictivos o bien siempre se puede realizar a través de la línea de comandos. +- + term: merge conflict + description: >- + Una diferencia que ocurre entre ramas fusionadas. Los conflictos de fusión suceden cuando las personas realizan diferentes cambios en la misma línea del mismo archivo o cuando una persona edita un archivo y otra persona elimina el mismo archivo. El conflicto de fusión se debe resolver antes de que puedas fusionar las ramas. +- + term: milestone + description: >- + Una manera de hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. +- + term: mirror + description: Una copia nueva de un repositorio. +- + term: nested team + description: >- + Un equipo hijo de un equipo padre. Puedes tener varios equipos hijo (o anidados). +- + term: Network graph + description: >- + Un gráfico del repositorio que muestra el historial de la rama de toda la red del repositorio, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones de cambios únicas para la red. +- + term: News Feed + description: >- + Una vista de la actividad de los repositorios o de las personas que ves. Las Noticias de una organización muestran la actividad en los repositorios que son propiedad de la organización. +- + term: non-fast-forward + description: >- + Cuando la copia local de un repositorio no está sincronizada con el repositorio ascendente y necesitas extraer los cambios ascendentes antes de subir tus cambios locales. +- + term: notification + description: >- + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. +- + term: OAuth App + description: >- + Una aplicación de terceros que usa tokens de acceso en lugar de contraseñas para acceder a información para usuarios. +- + term: OAuth token + description: El token de acceso usado en Apps OAuth para acceder a información para usuarios. +- + term: outside collaborator + description: >- + Un usuario al que se le ha dado acceso a uno o más repositorios de una organización, pero no tiene otro acceso a la organización y no es un miembro de la organización. +- + term: open source + description: >- + El software de código abierto es un software que se puede usar, modificar y compartir (tanto de la forma modificada como no modificada) libremente por cualquiera. Hoy en día el concepto de "código abierto" suele extenderse más allá del software, para representar una filosofía de colaboración en la cual se facilitan los materiales de trabajo en línea para que cualquiera los bifurque, los modifique y debata y contribuya con ellos. +- + term: organization + description: >- + Las organizaciones son un grupo de dos o más usuarios que generalmente imitan a organizaciones del mundo real. Son administradas por usuarios y pueden contener tanto repositorios como equipos. +- + term: organization owner + description: Usuarios que tienen un acceso administrativo completo a la organización que poseen. +- + term: origin + description: >- + El repositorio ascendente predeterminado. La mayoría de los proyectos tienen al menos un proyecto ascendente al que le hacen un seguimiento. Por defecto, el origen se usa con ese fin. +- + term: owner + description: >- + Miembros de una organización que tienen acceso administrativo completo a la organización. +- + term: parent team + description: >- + Dentro de los equipos anidados, el equipo principal desde el cual los equipos hijo heredan los permisos de acceso y @menciones. +- + term: participating notifications + description: >- + Una notificación acerca de una actualización en una conversación en una propuesta o solicitud de extracción donde tu nombre de usuario o equipo fue mencionado o donde previamente has respondido a un comentario. +- + term: permalink + description: Un hipervínculo estático permanente a una página web en particular. +- + term: personal account + description: >- + Una cuenta de GitHub que pertenece a un usuario individual. +- + term: primary email address + description: >- + La dirección principal de correo electrónico donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. +- + term: pinned repository + description: >- + Un repositorio que un usuario ha decidido mostrar de forma prominente en su perfil. +- + term: pre-receive hooks + description: >- + Los scripts que se ejecutan en el servidor GitHub Enterprise que puedes usar para implementar controles de calidad. +- + term: private contributions + description: Contribuciones hechas a un repositorio privado (vs. público). +- + term: private repository + description: >- + Los repositorios privados solo son visibles para el propietario del repositorio y los colaboradores que el propietario especifique. +- + term: production branch + description: >- + Una rama con cambios finales que está lista para ser usada o implementada en una aplicación o un sitio. +- + term: profile + description: La página que muestra información acerca de la actividad de un usuario. +- + term: profile photo + description: >- + Una imagen personalizada que los usuarios suben a GitHub para identificar su actividad, generalmente junto con su nombre de usuario. También se lo conoce como un avatar. +- + term: project board + description: >- + Los tableros dentro de GitHub que están hechos de propuestas, solicitudes de extracción y notas que son categorizados como tarjetas en columnas. +- + term: protected branch + description: >- + Las ramas protegidas bloquean varias funciones de Git en una rama la cual un administrador de repositorio elige proteger. No pueden tener un empuje forzado, ni ser eliminadas, ni fusionarles cambios sin la aprobación de controles requerida ni las revisiones aprobadas requeridas ni cargarle archivos a esta desde la interfaz web de GitHub. Una rama protegida generalmente es la rama por defecto. +- + term: public contributions + description: Contribuciones hechas a un repositorio público (vs. privado). +- + term: public repository + description: >- + Un repositorio público puede ser visto por cualquiera, incluso por personas que no son usuarios de GitHub. +- + term: pull + description: >- + Extraer se refiere a cuando se recuperan cambios y se fusionan. Por ejemplo, si alguien ha editado el archivo remoto en el que ambos están trabajando, querrás extraer esos cambios para tu copia local para que esté actualizado. También consulta recuperar. +- + term: pull access + description: Un sinónimo para acceso de lectura. +- + term: solicitud de cambios + description: >- + Las solicitudes de extracción son cambios propuestos para un repositorio enviado por un usuario y aceptado o rechazado por los colaboradores de un repositorio. Como las propuestas, las solicitudes de extracción tienen sus propios foros de debate. +- + term: pull request review + description: >- + Los comentarios de los colaboradores en una solicitud de extracción que aprueban los cambios o solicitan otros cambios antes de fusionar la solicitud de extracción. +- + term: Pulse graph + description: Un gráfico del repositorio que te brinda una descripción de la actividad de un repositorio. +- + term: Punch graph + description: >- + Un gráfico del repositorio que muestra la frecuencia de las actualizaciones para un repositorio en función del día de la semana y la hora del día. +- + term: push + description: >- + Subir significa enviar tus cambios confirmados a un repositorio remoto en GitHub.com. Por ejemplo, si cambias algo de forma local, puedes subir esos cambios para que otros puedan acceder a ellos. +- + term: subir una rama + description: >- + Cuando subes una rama a un repositorio remoto, actualizas la rama remota con cambios de tu rama local. Cuando "subes una rama", Git buscará el HEAD ref en el repositorio remoto y verificará que sea un ancestro directo de el HEAD ref local de la rama. Una vez que se verifique, Git extrae todos los objetos (alcanzables desde el HEAD ref local y que no estén en el repositorio remoto) en la base de datos de objetos remotos y después actualiza el HEAD ref remoto. Si el HEAD remoto no es un ancestro del HEAD local, la subida fallará. +- + term: push access + description: Un sinónimo para acceso de escritura. +- + term: read access + description: >- + Un nivel de permiso en un repositorio que permite al usuario extraer o leer información desde el repositorio. Todos los repositorios públicos otorgan acceso de lectura a todos los usuarios de GitHub. Un sinónimo para acceso de lectura. +- + term: README + description: Un archivo de texto que contiene información acerca de los archivos en un repositorio que, generalmente, es el primer archivo que verá un visitante de tu repositorio. Un archivo README, junto con una licencia de repositorio, las pautas de contribución y un código de conducta, te ayuda a compartir expectativas y administrar contribuciones para tu proyecto. +- + term: rebase + description: >- + Volver a aplicar una serie de cambios de una rama a una base diferente y restablecer el HEAD de esa rama al resultado. +- + term: Recover Accounts Elsewhere + description: >- + Le permite a los usuarios agregar un factor de seguridad extra a su cuenta de GitHub en caso de que pierdan acceso a su método de autenticación de dos factores o a sus códigos de recuperación. Los usuarios pueden asociar su cuenta de GitHub con su cuenta de Facebook almacenando una credencial de autenticación en forma de token de recuperación de cuenta para su cuenta de GitHub con Facebook. +- + term: recovery code + description: Un código que te ayuda a volver a tener acceso a tu cuenta de GitHub. +- + term: release + description: El modo que tiene GitHub de empaquetar y proporcionar el software a tus usuarios. +- + term: remote + description: >- + Esta es la versión de un repositorio o rama que está alojada en un servidor, probablemente GitHub.com. Las versiones remotas se pueden conectar a clones locales para poder sincronizar los cambios. +- + term: remote repository + description: >- + Un repositorio que se usa para hacer un seguimiento del mismo proyecto, pero reside en otro lugar. +- + term: remote URL + description: >- + El lugar donde se almacena tu código: un repositorio en GitHub, la bifurcación de otro usuario o incluso un servidor diferente. +- + term: replica + description: >- + Una instancia de GitHub Enterprise que ofrece redundancia para la instancia principal de GitHub Enterprise. +- + term: repositorio + description: >- + Un repositorio es el elemento más básico de GitHub. Son más fáciles de imaginar como la carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena el historial de revisión de cada archivo. Los repositorios pueden tener varios colaboradores y pueden ser públicos o privados. +- + term: repository graph + description: Una representación visual de los datos de tu repositorio. +- + term: repository maintainer + description: >- + Alguien que administra un repositorio. Esta persona puede ayudar a evaluar prioridades de las propuestas y usar etiquetas y otras funciones para administrar el funcionamiento del repositorio. Esta persona también puede ser responsable de mantener los archivos README y de contribución actualizados. +- + term: required pull request review + description: >- + Las revisiones requeridas garantizan que las solicitudes de extracción tengan, al menos, una revisión aprobada antes de que los colaboradores puedan realizar cambios en una rama protegida. +- + term: required status check + description: >- + Verificaciones de las solicitudes de extracción que garantizan que todas las pruebas de integración continua (CI) requeridas sean aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. +- + term: resolve + description: La acción de solucionar de forma manual lo que dejó una fusión automática fallida. +- + term: revert + description: >- + Cuando reviertes una solicitud de extracción en GitHub, automáticamente se abre una solicitud de extracción nueva, que tiene una confirmación de cambios que revierte la confirmación de fusión de la solicitud de extracción original fusionada. En Git, puedes revertir las confirmaciones de cambio con `revertir git`. +- + term: review + description: >- + Las revisiones le permiten a otros con acceso a tu repositorio comentar los cambios propuestos en las solicitudes de extracción, aprobar los cambios o solicitar más cambios antes de que se fusione la solicitud de extracción. +- + term: root directory + description: El primer directorio en jerarquía. +- + term: root filesystem + description: El sistema operativo base y el entorno de la aplicación GitHub Enterprise. +- + term: saved reply + description: >- + Un comentario que puedes guardar y agregar a tu cuenta de usuario de GitHub para que puedas usar en GitHub en las propuestas y en las solicitudes de extracción. +- + term: scope + description: >- + Grupos de permisos con nombre que una App OAuth puede solicitar para acceder tanto a los datos públicos como los no públicos. +- + term: seat + description: >- + Un usuario dentro de la organización de GitHub Enterprise. Se lo puede conocer como "cómputo de asientos". +- + term: secret team + description: >- + Un equipo que solo es visible para otras personas del equipo y personas con premisos de propietario. +- + term: security log + description: >- + Un registro que enumera las últimas 50 acciones o las realizadas dentro de los últimos 90 días. +- + term: service hook + description: >- + También llamado "webhook". Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. +- + term: single sign-on + description: >- + También llamado SSO. Le permite a los usuarios iniciar sesión en una única ubicación - un proveedor de identidad (IdP)- que luego le da acceso al usuario a otros proveedores de servicios. +- + term: snapshot + description: Un punto de control de una máquina virtual a partir de un momento específico. +- + term: squash + description: Combinar varias confirmaciones de cambios en una única confirmación. También un comando Git. +- + term: Llave SSH + description: >- + Las claves SSH son una manera de identificarte a ti mismo en un servidor en línea, usando un mensaje cifrado. Es como si tu computadora tuviera su propia contraseña única para otro servicio. {% data variables.product.product_name %} utiliza claves SSH para transferir información de forma segura a tu computadora. +- + term: staging instance + description: >- + Un modo de evaluar modificaciones antes de que sean aplicadas a tu instancia actual de GitHub Enterprise. +- + term: status + description: >- + Una representación visual dentro de una solicitud de extracción de que tus confirmaciones cumplen las condiciones establecidas para el repositorio con el que estás contribuyendo. +- + term: Verificaciones de estado + description: >- + Las verificaciones de estado son procesos externos, como compilaciones de integración continua, que se ejecutan para cada confirmación que realices en un repositorio. Para obtener más información, consulta "[acerca de las verificaciones de Estado] (/articles/about-status-checks)." +- + term: star + description: >- + Un marcador o una muestra de reconocimiento para un repositorio. Las estrellas son un modo manual de clasificar la popularidad de los proyectos. +- + term: subscription + description: Un plan GitHub de un usuario o una organización. +- + term: team + description: >- + Un grupo de miembros de una organización que refleja la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. +- + term: team maintainer + description: >- + Miembros de la organización que tienen un subconjunto de permisos disponibles para los propietarios de la organización para administrar equipos. +- + term: Team plan + description: >- + El plan de facturación de una organización que te da repositorios públicos y privados ilimitados. +- + term: timeline + description: Una serie de eventos en una solicitud de extracción o en el perfil de un usuario. +- + term: topic branch + description: >- + Una rama Git normal que usa un programador para identificar una línea conceptual de desarrollo. Como las ramas son muy fáciles de usar y económicas, suele ser conveniente tener varias ramas pequeñas y que cada una contenga conceptos muy bien definidos o cambios pequeños incrementales pero relacionados. También se puede denominar rama de característica. +- + term: topics + description: >- + Un modo de explorar repositorios en una área temática en particular, encontrar proyectos a los cuales contribuir y descubrir nuevas soluciones para un problema específico en GitHub. +- + term: Traffic graph + description: >- + Un gráfico del repositorio que muestra el tráfico de un repositorio, incluso clones completos (no recuperaciones), los visitantes de los últimos 14 días, sitios de referencia y contenido popular. +- + term: transfer + description: >- + Transferir un repositorio significa cambiar el propietario de un repositorio. El nuevo propietario podrá administrar de inmediato los contenidos, las propuestas, las solicitudes de extracción, los lanzamientos y los parámetros del repositorio. +- + term: upstream + description: >- + Cuando se habla de una rama o una bifurcación, la rama principal en el repositorio original suele conocerse como "ascendente", ya que es el lugar principal desde donde vendrán otros cambios. La rama/bifurcación en la que estás trabajando entonces se llama "descendente ". También llamada origen. +- + term: upstream branch + description: >- + La rama por defecto que se fusiona en la rama en cuestión (o la rama en cuestión en la que es rebasada). Se configura mediante `branch..remote` y `branch..merge`. Si la rama ascendente de A es la origen/B, a veces, decimos "A hace un seguimiento de la origen/B". +- + term: user + description: >- + Los usuarios son personas con cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede poseer varios repositorios, públicos o privados. Pueden crear o ser invitados a unirse a organizaciones o colaborar con el repositorio de otro usuario. +- + term: username + description: El identificador de un usuario en GitHub. +- + term: visible team + description: Un equipo que puede ser visto y @mencionado por cada miembro de la organización. +- + term: watch + description: >- + Puedes ver un repositorio o una propuesta para recibir notificaciones cuando se realizan actualizaciones a una propuesta o una solicitud de extracción. +- + term: watching notifications + description: Una notificación acerca de la actividad en un repositorio al que se ha subscripto un usuario. +- + term: web notifications + description: >- + Las notificaciones que se muestran en la interfaz web en GitHub: https://github.com/notifications +- + term: webhooks + description: >- + Los webhooks te permiten generar o configurar Apps GitHub que se suscriben a ciertos eventos en GitHub.com. Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. También llamado gancho de servicio. +- + term: Works with GitHub + description: Un listado de integraciones que son compatibles con GitHub. +- + term: write access + description: >- + Un nivel de permiso en un repositorio que le permite al usuario subir o escribir cambios para un repositorio. diff --git a/translations/es-ES/data/glossaries/internal.yml b/translations/es-ES/data/glossaries/internal.yml new file mode 100644 index 0000000000000..2653ed0dd8669 --- /dev/null +++ b/translations/es-ES/data/glossaries/internal.yml @@ -0,0 +1,755 @@ +--- +- + term: 2-up + description: El modo predeterminado de ver imágenes en GitHub. +- + term: alternate object database + description: >- + A través de mecanismos alternativos, un repositorio puede heredar parte de su base de datos de objetos de otra base de datos de objetos, que se denomina "alternativa". +- + term: AMI + description: >- + Imagen de máquina de Amazon. Un aparato virtual para usar con la Amazon Elastic Compute Cloud. +- + term: anonymized image URL + description: >- + Un proxy URL anónimo para cada imagen que oculta los detalles del navegador y la información relacionada de otros usuarios. +- + term: apex domain + description: Un dominio de raíz que no contiene una parte de subdominio. +- + term: API + description: >- + Interfaz de programación de la aplicación. Un conjunto de métodos de comunicación claramente definidos entre varios componentes de software. +- + term: API token + description: >- + Un token que se usa en lugar de una contraseña en scripts y en la línea de comando. +- + term: app + description: >- + Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. +- + term: application + description: >- + Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. +- + term: argument + description: 'En GraphQL, un conjunto de pares de clave-valor que se adjunta a un campo específico.' +- + term: AsciiDoc + description: >- + Un formato de documento de texto para escribir notas, documentación, artículos, libros, libros electrónicos, diapositivas, páginas web, páginas de manual y blogs. +- + term: assets + description: 'Archivos individuales como imágenes, fotos, videos y archivos de texto.' +- + term: Atom feed + description: Un formato XML ligero que permite una fácil sindicación del contenido web. +- + term: audit log + description: >- + En una organización, el registro de auditoría incluye detalles acerca de las actividades realizadas en la organización, como quién realizó la acción, cuál fue la acción y cuándo fue realizada. +- + term: avatar + description: >- + Una imagen personalizada que los usuarios suben a GitHub para identificar su actividad, generalmente junto con su nombre de usuario. También se lo conoce como una foto de perfil. +- + term: AWS + description: Amazon Web Services. Una plataforma segura de servicios en la nube. +- + term: Azure + description: Una plataforma de informática en la nube de Microsoft. +- + term: bare repository + description: >- + Normalmente, un repositorio en blanco es un directorio con un nombre apropiado con un sufijo .git que no tiene una copia revisada localmente de ninguno de los archivos bajo control de revisión. Es decir, todos los archivos de control y administrativos Git que normalmente estarían presentes en el subdirectorio .git oculto están presentes directamente en el directorio del repositorio.git y ningún otro archivo está presente y revisado. Generalmente, quienes publican los repositorios públicos ponen a disposición los repositorios en blanco. +- + term: BFG repo cleaner + description: BFG. Una herramienta de terceros que limpia datos del historia de tu repositorio Git. +- + term: blob object + description: 'Objeto sin tipo, p. ej., los contenidos de un archivo.' +- + term: bot + description: Una aplicación de software que ejecuta tareas automatizadas. +- + term: Bundler + description: Una manera de administrar las Ruby gems de las que depende una aplicación. +- + term: camo + description: >- + Un proxy de imagen SSL para evitar advertencias de contenido mixto en páginas seguras proporcionadas desde GitHub. +- + term: chain + description: >- + Una lista de objetos, donde cada objeto en la lista contiene una referencia para su sucesor (por ejemplo, el sucesor de una confirmación de cambios podría ser uno de sus padres). +- + term: CIDR notation + description: Una representación compacta de una dirección IP y su prefijo de enrutamiento asociado. +- + term: CLI + description: Interfaz de línea de comandos. +- + term: CNAME record + description: >- + Registro de nombre canónico. Un tipo de registro de recursos en el Sistema de nombres de dominio (DNS) usado para especificar que el nombre de un dominio es un alias para otro dominio (el dominio 'canónico'). +- + term: conditional request + description: >- + En la API REST, un método HTTP que solo se responde en ciertas circunstancias. +- + term: connection + description: 'En GraphQL, una manera de consultar objetos relacionados como parte de la misma llamada.' +- + term: core Git + description: >- + Utilidades y estructuras de datos fundamentales de Git. Expone solo herramientas de administración de código fuente limitadas. +- + term: CPU + description: Unidad de procesamiento central. +- + term: credential helper + description: A program that stores and fetches Git credentials. +- + term: creole + description: >- + Un lenguaje Markup ligero, que apunta a ser un lenguaje Markup común para wikis, que permita y simplifique la transferencia de contenido entre diferentes motores wiki. +- + term: CSV + description: Archivos delimitados por comas. +- + term: DAG + description: >- + Gráfico acíclico dirigido. Los objetos de confirmación de cambios forman un gráfico acíclico dirigido, porque tienen padres (dirigidos) y el gráfico de objetos de confirmación de cambios es acíclico (no hay cadena que comience y termine con el mismo objeto). +- + term: dangling object + description: >- + Un objeto inaccesible que no es accesible incluso desde otros objetos inaccesibles; un objeto inalcanzable no tiene referencias a él desde ninguna referencia ni objeto en el repositorio. +- + term: data pack + description: >- + Paquete de ancho de banda y de almancenamiento que los usuarios pueden comprar. Cada paquete de datos ofrece 50 GB de ancho de banda y 50 GB para almacenamiento. +- + term: DELETE + description: Un tipo de método en la API REST. +- + term: DHCP + description: >- + Protocolo de configuración dinámica de host (DHCP). Un servidor de cliente/protocolo que proporciona automáticamente un host de protocolo de Internet con su dirección IP y otra información de configuración relacionada, como la máscara de subred y la puerta de enlace predeterminada. +- + term: directive + description: >- + En GraphQL, un modo de afectar la ejecución de una consulta de la manera que el servidor lo desee. +- + term: directory + description: La lista que obtienes con el comando "ls". +- + term: disaster recovery + description: >- + También conocido como DR. Herramientas y procesos que recuperan los sistemas y la infraestructura tecnológica después de una catástrofe natural o de origen humano. +- + term: DNS provider + description: >- + Una empresa que le permite a los usuarios comprar y registrar un nombre de dominio único y conectar ese nombre a una dirección IP (Protocolo de Internet) indicando tu nombre de dominio a una dirección IP o a un nombre de dominio diferente. +- + term: DSA + description: Algoritmo de firma digital. Un estándar de procesamiento para las firmas digitales. +- + term: DSA key + description: Claves públicas y privadas usadas en DSA. +- + term: Early Access Program + description: >- + Un programa de GitHub al que ingresan individuos y organizaciones para recibir funciones prelanzadas. +- + term: EBS + description: >- + Amazon Elastic Block Store. Ofrece volúmenes de almacenamiento de bloqueo persistente para usar con la instancia de Amazon EC2 en la nube de AWS. +- + term: EC2 + description: >- + Amazon Elastic Compute Cloud. Un servicio web que ofrece capacidad de cálculo redimensionable y segura en la nube. +- + term: edge + description: 'En GraphQL, las conexiones entre nodos.' +- + term: EIP + description: IP elástica. Una dirección IPv4 estática diseñada para una informática dinámica en la nube. +- + term: ElasticSearch + description: Un motor de búsqueda basado en Lucene. +- + term: evil merge + description: >- + Un unión maliciosa es una fusión que introduce cambios que no aparecen en ningún padre. +- + term: exclude + description: >- + Una vez que una ruta coincide con cualquier pathspec no excluido, será ejecutada a través de todo pathspec excluido (firma especial: ! o su sinónimo ^). Si coincide, la ruta se ignora. Si no hay pathspec no excluido, la exclusión se aplica al resultado establecido como invocado sin ningún pathspec. +- + term: FIDO U2F + description: >- + Un estándar de autenticación abierta que refuerza y simplifica la autenticación de dos factores usando dispositivos NFC y USB especializados basado en una tecnología de seguridad similar encontrada en las tarjetas inteligentes. +- + term: field + description: 'En GraphQL, una unidad de datos que puedes recuperar de un objeto.' +- + term: file system + description: >- + Linus Torvalds originalmente diseñó Git para ser un sistema de archivos de espacio para usuarios, es decir, la infraestructura para mantener archivos y directorios. Esto garantizó la eficacia y la velocidad de Git. +- + term: flame war + description: Un debate fuerte y agresivo en línea entre usuarios. +- + term: fragment + description: 'En GraphQL, unidades reusables que te permiten crear conjuntos de campos.' +- + term: GCE + description: Google Compute Engine. +- + term: gem + description: Una herramienta de línea de comandos que puede instalar bibliotecas y administrar RubyGems. +- + term: Gemfile + description: Un formato para describir las dependencias gem para los programas Ruby. +- + term: GET + description: Un tipo de método en la API REST. +- + term: geoJSON + description: Un formato para codificar una variedad de estructuras de datos geográficos. +- + term: GitHub Marketplace Developer Agreement + description: Un acuerdo que firman los usuarios cuando usan Mercado GitHub. +- + term: GPG + description: >- + GNU Privacy Guard. Software de cifrado que puedes usar para cifrar (y descifrar) archivos que contengan datos confidenciales. +- + term: GPG key + description: Una clave de cifrado usada con GPG. +- + term: hash + description: Sinónimo para nombre del objeto. +- + term: head + description: >- + Una referencia con nombre para la confirmación de cambios en el extremo de una rama. Los encabezados se almacenan en un archivo en el directorio $GIT_DIR/refs/heads/, excepto cuando usan refs empaquetados. +- + term: HEAD + description: Un tipo de método en la API REST. +- + term: headers + description: >- + En la API REST, un componente del mensaje requerido que define los metadatos de la tranasacción. +- + term: health check + description: >- + Un modo de permitir un balanceador de carga para detener el tráfico que se envía a un nodo que no está respondiendo si falla una revisión configurada previamente en ese nodo. +- + term: HTTP verb + description: Un método HTTP. +- + term: Hyper-V + description: >- + Un producto de Microsoft que crea máquinas virtuales en sistemas x86-64 con Windows. +- + term: hypermedia + description: 'En la API REST, enlaces desde un estado de recurso a otro.' +- + term: icase + description: Coincidencia que no distingue mayúsculas de minúsculas. +- + term: implementation + description: 'En GraphQL, cómo un objeto hereda de una interfaz.' +- + term: index + description: >- + Un conjunto de archivos con información estadística, cuyos contenidos se almacenan como objetos. El índice es una versión almacenada de tu árbol de trabajo. A decir verdad, también puede contener una segunda, e incluso una tercer versión de un árbol de trabajo, que se usan cuando se fusiona. +- + term: index entry + description: >- + La información respecto a un archivo en particular, almacenada en el índice. Una entrada de índice puede ser no configurada, si se inició una fusión, pero aún no se finalizó (es decir, si el índice contiene varias versiones de ese archivo). +- + term: introspection + description: >- + También se la conoce como "introspectiva". Un modo de solicitar al esquema GraphQL información acerca de las consultas que admite. +- + term: iPython notebook + description: >- + Una aplicación basada en la web que captura todo el proceso de cálculo: desarrollo, documentación y código de ejecución, así como también comunica los resultados. +- + term: JIRA + description: Un producto de Atlassian que hace un seguimiento de las propuestas. +- + term: Jupyter notebook + description: Notebook que contiene tanto elementos de texto enriquecido como de código. +- + term: kernel + description: Un programa que es el núcleo del sistema operativo de un equipo. +- + term: kramdown + description: Procesador Markdown predeterminado 3.0.0 de Jekyll. +- + term: LDAP + description: Protocolo ligero de acceso a directorios. +- + term: linter + description: Un programa que verifica la calidad del código. +- + term: Liquid + description: Un lenguaje de plantillas que se usa para cargar contenido dinámico. +- + term: load balancer + description: >- + Un dispositivo que actúa como un proxy inverso y distribuye tráfico de aplicación o de red a través de una cantidad de servidores. +- + term: media type + description: Un identificador de dos partes para los formatos de archivo y los contenidos de formato. +- + term: MediaWiki + description: >- + Un software wiki de código abierto y gratuito escrito en el lenguaje de programación PHP que almacena los contenidos en una base de datos. +- + term: Mercurial + description: 'Una herramienta de administración de control de código fuente con distribución y gratuita.' +- + term: metadata + description: Un conjunto de datos que describen y brindan información acerca de otros datos. +- + term: MIME-type + description: >- + Extensiones de correo de Internet multipropósitos. Una manera de identificar archivos según su naturaleza y formato. +- + term: mutations + description: >- + En GraphQL, una manera de definir las operaciones GraphQL que modifican datos en el servidor. +- + term: nameserver + description: >- + Un servidor en Internet especializado en manejar consultas respecto a la ubicación de varios servicios de un nombre de dominio. +- + term: NFC + description: >- + Transmisión de datos en proximidad. Un conjunto de protocolos de comunicación que le permite a dos dispositivos electrónicos, uno de los cuales generalmente es un dispositivo portátil como un smartphone, establecer comunicación llevándolos dentro de un cierto rango uno de otro. +- + term: node + description: >- + Un dispositivo electrónico activo que se conecta a una red y es capaz de crear, recibir o transmitir información en un canal de comunicaciones. +- + term: node + description: 'En GraphQL, un término genérico para un objeto.' +- + term: NTP + description: Protocolo de tiempo de la red. +- + term: object + description: >- + La unidad de almacenamiento en Git. Se identifica de forma unívoca mediante el SHA-1 de sus contenidos. Por consiguiente, un objeto no se puede modificar. +- + term: object database + description: >- + Almacena un conjunto de "objetos" y el nombre del objeto identifica un objeto individual. Los objetos generalmente viven en $GIT_DIR/objects/. +- + term: object identifier + description: Sinónimo para nombre del objeto. +- + term: object name + description: >- + El identificador único de un objeto. El nombre del objeto generalmente se representa con una cadena hexadecimal de 40 caracteres. Coloquialmente también se lo llama SHA-1. +- + term: object type + description: >- + Uno de los identificadores "confirmación de cambios", "árbol", "etiqueta" o "blob" que describe el tipo de un objeto. +- + term: octopus + description: Fusionar más de dos ramas. +- + term: onion skin + description: >- + Una manera de ver imágenes en GitHub disminuyendo la opacidad de una imagen de reemplazo superpuesta. +- + term: OOM + description: Sin memoria. +- + term: Open Stack + description: Una plataforma de software para informática en la nube. +- + term: OpenSSH + description: >- + Un conjunto de utilidades a nivel de red relacionado con la seguridad basado en el protocolo Secure Shell (SSH). +- + term: ordered list + description: Una lista enumerada. +- + term: Org + description: >- + Un sistema de texto simple para mantener las notas, mantener las listas TODO, planificar proyectos y autorizar documentos. +- + term: pack + description: >- + Un conjunto de objetos que han sido comprimidos en un archivo (para ahorrar espacio o para transmitirlos de forma eficiente). +- + term: pack index + description: >- + La lista de identificadores, y otra información, de los objetos en un paquete, para ayudar a acceder de forma eficiente a los contenidos de un paquete. Los pathspec se usan en la línea de comandos de "git ls-files", "git ls-tree", "git add", "git grep", "git diff", "git checkout", y muchos otros comandos para limitar el alcance de las operaciones para algún subconjunto del árbol o del árbol de trabajo. +- + term: parameter + description: >- + En la API REST, datos que son enviados en la solicitud o recibidos en la respuesta como parte de un parámetro de entrada o salida. +- + term: parent + description: >- + Un objeto de confirmación de cambios contiene una lista (posiblemente vacía) de el/los predecesor/es lógico/s en la línea de desarrollo, es decir, sus padres. +- + term: passphrase + description: >- + Una secuencia de palabras u otro texto usado para controlar el acceso a un sistema del equipo, programa o datos. +- + term: PATCH + description: Un tipo de método en la API REST. +- + term: pathspec + description: Patrón usado para limitar las rutas en los comandos de Git. +- + term: PEM + description: Correo con privacidad mejorada +- + term: persistent identifier + description: >- + También conocidos como identificadores de objetos digitales (DOI). Cadenas de caracteres y/o números únicos a nivel global que hacen referencia a un objeto digital. Los identificadores persistentes pueden ser prácticos ya que le permiten a un usuario acceder al recurso digital mediante un enlace persistente. +- + term: pickaxe + description: >- + Una opción para las rutinas de núcleo diferente que ayuda a seleccionar cambios que agregan o eliminan una cadena de texto dada. Con la opción --pickaxe-all, se puede usar para ver el conjunto de cambios completo que introducido o eliminado, dice, una línea de texto particular. +- + term: plugin + description: Un componente de software que agrega una función especial a un programa existente. +- + term: Pod + description: Documentación antigua simple. Un lenguaje mark-up usado por los programadores perl. +- + term: pointer file + description: Una referencia que apunta a un archivo real. +- + term: port + description: Un punto final de comunicación en un sistema operativo. +- + term: priority question + description: >- + Preguntas para el soporte técnico de GitHub de organizaciones en el Plan Business. Las preguntas deben cumplir con los criterios establecidos por GitHub para calificar como una pregunta prioritaria. +- + term: priority response + description: >- + Respuestas del soporte técnico de GitHub para las preguntas prioritarias de organizaciones en el Plan Business. +- + term: polling + description: >- + Controles automáticos regulares de otros programas o dispositivos hechos por un programa o dispositivo para ver en qué estado están. +- + term: POST + description: Un tipo de método en la API REST. +- + term: Pre-release Program + description: >- + Un programa de GitHub que le permite a los usuarios aplicar nuevas funciones y funcionalidad antes de ser lanzados oficialmente. +- + term: PUT + description: Un tipo de método en la API REST. +- + term: QCOW2 + description: Un formato de imagen. +- + term: QR code + description: >- + Código de respuesta rápida. Un código de barras es la etiqueta óptica de lectura mecánica que contiene información acerca del elemento al que está conectado. +- + term: queries + description: 'En GraphQL, una manera de preguntar por campos específico en los objetos.' +- + term: rate limit + description: El proceso por el cual una API rechaza solicitudes. +- + term: RDoc + description: Un generador de documentación incrustada para el lenguaje de programación Ruby. +- + term: reachable + description: >- + Se dice que todos los ancestros de una confirmación de cambios dada son "accesibles" desde esa confirmación. En términos más generales, un objeto es accesible desde otro si podemos alcanzarlos de unos a otros mediante una cadena que sigue etiquetas para lo que sea que etiqueten, confirmaciones de cambios a sus padres o árboles, y árboles a los árboles o blobs que contengan. +- + term: ref + description: >- + Un nombre que comienza con refs/ (p. ej., refs/heads/master) a apunta a un nombre del objeto o a otro ref (el último se llama un ref simbólico). +- + term: reflog + description: Un reflog muestra el "historial" local de un ref. +- + term: refspec + description: >- + Un "refspec" es usado por recuperar y subir para describir la asignación entre ref remoto y ref local. +- + term: relative link + description: Un enlace que es relativo para el archivo actual. +- + term: remote-tracking branch + description: Un ref que se usa para seguir los cambios desde otro repositorio. +- + term: REST API + description: >- + Una API que define un conjunto de funciones para que los programadores puedan realizar solicitudes y recibir respuestas mediante HTTP. +- + term: reStructured text + description: Un sistema analizador y de sintaxis Markup de texto simple Lo que ves es lo que obtienes. +- + term: revision + description: Sinónimo para confirmación de cambios. +- + term: rewind + description: >- + Descartar parte del desarrollo, es decir, asignar el encabezado a una revisión anterior. +- + term: root endpoint + description: 'En la API REST, el directorio en los que todos los puntos finales están debajo.' +- + term: RSA + description: Algoritmo usado para cifrar los datos de usuario usando una clave pública y una clave privada. +- + term: RSA key + description: Una clave privada basada en el algoritmo RSA. +- + term: SAML + description: >- + Lenguaje Markup de aserción de seguridad. Un formato de datos estándar abierto basado en XML para intercambiar datos de autenticación y autorización entre las partes, en particular, entre un proveedor de identidad y un proveedor de servicios. +- + term: SAN + description: Nombre alternativo del firmante. +- + term: Sass + description: Un lenguaje de extensión CSS. +- + term: schema + description: Metadatos que nos dicen cómo están estructurados nuestros datos. +- + term: SCIM + description: >- + Sistema para la administración de identidades entre dominios. Un estándar abierto para automatizar el intercambio de información de identidad del usuario entre los dominios de identidad. +- + term: SCM + description: Administración de código fuente (herramienta). +- + term: SCSS + description: Un lenguaje de extensión CSS. +- + term: service account + description: >- + Una cuenta de usuario especial que una aplicación o servicio usa para interactuar con el sistema operativo. +- + term: SHA-1 + description: >- + "Algoritmo Hash seguro 1"; una función de hash criptográfico. En el contexto de Git se usa como un sinónimo de nombre del objeto. +- + term: shell + description: Una interfaz de usuarios para acceder a los servicios de un sistema operativo. +- + term: shallow repository + description: >- + Un repositorio superficial tiene un historial incompleto y algunas de sus confirmaciones de cambios tienen padres cauterizados aparte (en otras palabras, se le pide a Git que haga como si esas confirmaciones no tuvieran padres, aunque se graban en el objeto de la confirmación). Esto, a veces, es útil cuando solo te interesa el historial reciente de un proyecto aunque el historial real grabado en el ascendente sea mucho más grande. Un repositorio superficial se crea dando la --opción de profundidad para git-clone(1) y su historial puede ser profundizado más tarde con git-fetch(1). +- + term: SMS + description: Un mensaje de texto. +- + term: SMTP + description: Protocolo simple de transferencia de correo. Un estándar para la transmisión de correo. +- + term: SNMP + description: Protocolo simple de administración de redes. Un protocolo para la administración de redes. +- + term: spam + description: Comunicaciones no solicitadas de otro usuario. +- + term: SSD + description: Unidad de estado sólido. +- + term: SSH + description: >- + Secure Shell (SSH) es un protocolo de red criptográfico para operar servicios de red de forma segura en una red no segura. +- + term: ssh-agent + description: Un programa para retener claves privadas usadas para la autenticación de claves públicas. +- + term: SSH Key + description: >- + Las claves SSH son una manera de identificarte en un servidor en línea, usando un mensaje cifrado. Es como si tu equipo tuviera su propia contraseña única para otro servicio. GitHub usa las claves SSH para transferir información de forma segura desde GitHub.com a tu equipo. +- + term: SSH key fingerprint + description: >- + Identifica y verifica el host al que te estás conectando y está basada en la clave pública del host. +- + term: SSL + description: Capa de sockets seguros. +- + term: static site generator + description: >- + Un programa que genera un sitio web solo HTML usando datos sin procesar (como archivos Markdown) y plantillas. +- + term: String + description: Un tipo de objeto que denota texto simple. +- + term: STL file + description: >- + STL (STereoLithography) es un formato de archivo nativo para el software CAD de estereolitografía creado por los sistemas 3D. +- + term: subdomain + description: >- + Una parte personalizable y opcional del nombre de un dominio ubicada antes de la raíz o del dominio apex que se ve como el prefijo de un dominio. +- + term: submodule + description: >- + Un repositorio que contiene el historial de un proyecto independiente dentro de otro repositorio (este último se denomina superproyecto). +- + term: subproject + description: >- + Un proyecto que se desarrolla y se administra fuera de tu proyecto principal. +- + term: Subversion + description: Un sistema de control de versión de código abierto. +- + term: sudo mode + description: >- + Una manera en que los usuarios ejecutan programas con los privilegios de seguridad de otro usuario. Los usuarios proporcionan su propia contraseña y son autenticados. +- + term: superproject + description: >- + Un repositorio que hace referencia a repositorios de otros proyectos en su árbol de trabajo como submódulos. El superproyecto conoce los nombres de (pero no guarda copias de) los objetos de confirmación de cambios de los submódulos contenidos. +- + term: support bundle + description: >- + Un archivo tar comprimido en gzip que contiene registros importantes de tu instancia de GitHub Enterprise. +- + term: swipe + description: Una manera de ver porciones de tu imagen de GitHub de lado a lado. +- + term: symlink + description: >- + Un archivo que contiene una referencia a otro archivo o directorio en la forma de una ruta absoluta o relativa y que afecta la resolución del nombre de ruta. +- + term: symref + description: >- + Referencia simbólica: en lugar de contener el propio id SAH-1, es del formato ref: refs/some/thing y cuando se le hace referencia, recurrentemente se desreferencia de esta referencia. +- + term: tag + description: >- + Una ref en el espacio de nombres refs/tags/ que apunta a un objeto de un tipo arbitrario (generalmente, una etiqueta apunta ya sea a una etiqueta o a un objeto de confirmación de cambios). Una etiqueta se usa principalmente para marcar un punto en particular en la cadena de ascendencia de la confirmación. +- + term: tag object + description: >- + Un objeto que contiene una ref apuntando a otro objeto, que puede contener un mensaje como un objeto de confirmación de cambios. También puede contener una firma (PGP), en cuyo caso se llama un "objeto de etiqueta firmado". +- + term: Team Foundation Server + description: >- + Un producto de Microsoft que ofrece administración de código fuente y otros servicios de equipo. +- + term: Textile + description: >- + Un lenguaje Markup ligero que usa una sintaxis de formato de texto para convertir texto simple en un Markup HTML estructurado. +- + term: TLS + description: Seguridad de la capa de transporte. +- + term: token + description: >- + Se puede usar en lugar de una contraseña. Los tokens pueden ser tokens de acceso personal, tokens de OAuth o tokens API. +- + term: topoJSON + description: Una extensión de GeoJSON que codifica topología. +- + term: TOTP application + description: >- + Contraseña de un solo uso y duración definida. Este tipo de aplicación genera automáticamente un código de autenticación que cambia después de cierto período de tiempo. +- + term: tree + description: >- + Ya sea un árbol de trabajo o un objeto de árbol junto con el blob dependiente y objetos de árbol (es decir, una representación almacenada de un árbol de trabajo). +- + term: tree object + description: >- + Un objeto que contiene una lista de nombres de archivo y modos, junto con refs para el blob o los objetos de árbol asociados. Un árbol es equivalente a un directorio. +- + term: TSV + description: Archivos separados por tabulaciones. +- + term: two-factor authentication + description: >- + También denominada 2FA. Una capa extra de seguridad que no solo requiere de un procedimiento de inicio de sesión estándar con nombre de usuario y contraseña, si no que también de un código de autenticación que es generado por una aplicación en el smartphone del usuario o enviado como un mensaje de texto (SMS). +- + term: UFW + description: Herramienta de configuración de firewall predeterminada de Ubuntu. +- + term: unmerged index + description: Un índice que contiene entradas de índice no configuradas. +- + term: unordered list + description: Un lista con viñetas. +- + term: unreachable object + description: 'Un objeto que no es accesible desde una rama, etiqueta ni ninguna otra referencia.' +- + term: URI + description: >- + Identificador uniforme de recursos. Una cadena de caracteres usada para identificar un recurso. +- + term: UTF-8 + description: Una codificación de caracteres capaz de codificar todo punto de código Unicode posible. +- + term: variable + description: 'En GraphQL, una manera de realizar consultas más dinámicas y eficaces.' +- + term: VAT ID + description: Un número de identificación del impuesto al valor agregado para fines impositivos en la UE. +- + term: verified email address + description: >- + Una dirección de correo electrónico asociado a una cuenta personal que el usuario ha verificado que es válida con un proceso de confirmación de seguridad. +- + term: virtual machine + description: >- + Un entorno de aplicación que se instala en software e imita al hardware dedicado. También llamado una VM. +- + term: VPC + description: Nube privada virtual. Una red virtual dedicada a tu cuenta AWS. +- + term: VPN + description: Red privada virtual. +- + term: VMware + description: >- + Un producto Dell que ofrece servicios y software de virtualización de plataforma e informática en la nube. +- + term: permitido + description: >- + Una lista o registro de entidades a las que se les brinda un reconocimiento, acceso, movilidad, servicio o privilegio en particular. Las entidades en la lista serán aceptadas, aprobadas o reconocidas. +- + term: working directory + description: El directorio de archivos en el que estás trabajando actualmente. +- + term: working tree + description: >- + El árbol de archivos revisados reales. El árbol de trabajo generalmente contiene los contenidos del árbol de la confirmación de cambios del HEAD, además de cualquier cambio local que hayas realizado pero aún no confirmado. +- + term: WYSIWYG + description: >- + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. +- + term: XenServer + description: Una plataforma de virtualización. +- + term: YAML + description: >- + Un lenguaje de serialización de datos natural que comúnmente se usa para archivos de configuración. +- + term: Continuous Integration + description: También abreviada como CI. +- + term: Continuous Delivery + description: También abreviada como CD. diff --git a/translations/es-ES/data/graphql/ghae/graphql_previews.ghae.yml b/translations/es-ES/data/graphql/ghae/graphql_previews.ghae.yml new file mode 100644 index 0000000000000..3a8b9b48db8e9 --- /dev/null +++ b/translations/es-ES/data/graphql/ghae/graphql_previews.ghae.yml @@ -0,0 +1,149 @@ +--- +- + title: Acceso al borrado de versiones de paquetes + description: >- + Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml new file mode 100644 index 0000000000000..26e14af85fce8 --- /dev/null +++ b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: LegacyMigration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros pendientes consumen una licencia + date: '2020-07-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: 'se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`.' + reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryInvitationOrderField.INVITEE_LOGIN + description: 'Se eliminará a `INVITEE_LOGIN`.' + reason: '`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Sponsorship.sponsor + description: 'Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`.' + reason: 'Se eliminará a `Sponsorship.sponsor`.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores externos consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores pendientes consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: 'El `DRAFT` se eliminará. Utiliza PullRequest.isDraft en su lugar.' + reason: El estado del DRAFT se eliminará de esta enumeración y se deberá utilizar `isDraft` en su lugar + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: nplasterer diff --git a/translations/es-ES/data/graphql/ghes-2.20/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-2.20/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..fe620465014fa --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.20/graphql_previews.enterprise.yml @@ -0,0 +1,284 @@ +--- +- + title: Registro del paquete de GitHub + description: Esta vista previa agrega soporte para los objetos que se relacionen con GitHub Packages. + toggled_by: ':packages-preview' + announcement: null + updates: null + toggled_on: + - Para GitHub + - PackageFile + - PackageFileOrder + - PackageFileOrderField + - PackageOrder + - PackageOrderField + - PackageOwner + - PackageStatistics + - PackageTag + - PackageVersion + - PackageVersionOrder + - PackageVersionOrderField + - PackageVersionStatistics + - Organization.packages + - PackageMetadatum.packageVersion + - Repository.packages + - User.packages + - PackageConnection.nodes + - PackageFileConnection.nodes + - PackageTagConnection.nodes + - PackageVersionConnection.nodes + - PackageEdge.node + - PackageFileEdge.node + - PackageTagEdge.node + - PackageVersionEdge.node + - CreateRegistryPackageFilePayload.packageFile + - CreateRegistryPackageVersionMetadataPayload.packageVersion + - CreateRegistryPackageVersionPayload.packageVersion + - DeleteRegistryPackagePayload.package + - DeleteRegistryPackageTagPayload.package + - SetRegistryPackageTagPayload.package + - UpdateRegistryPackageFilePayload.packageFile + - UpdateRegistryPackageVersionPayload.packageVersion + - CreatePackageVersionPayload.packageVersion + - UpdatePackageVersionPayload.packageVersion + - CreatePackageFilePayload.packageFile + - UpdatePackageFilePayload.packageFile + - CreatePackageVersionMetadataPayload.packageVersion + - AddPackageTagPayload.package + - DeletePackageTagPayload.package + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: Vista Previa del Borrador de la Solicitud de Extracción + description: Esta vista previa agrega soporte para borradores de solicitudes de extracción. + toggled_by: ':shadow-cat-preview' + announcement: null + updates: null + toggled_on: + - Mutation.markPullRequestReadyForReview + - CreatePullRequestInput.draft + - PullRequest.isDraft + - MarkPullRequestReadyForReviewInput + - MarkPullRequestReadyForReviewPayload + owning_teams: + - '@github/pe-pull-requests' +- + title: Verificaciones + description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. + toggled_by: ':antiope-preview' + announcement: null + updates: null + toggled_on: + - CheckAnnotationRange + - CheckAnnotationPosition + - CheckAnnotationSpan + - CheckAnnotation + - CheckAnnotationConnection.nodes + - CheckAnnotationData + - CheckAnnotationEdge.node + - CheckAnnotationLevel + - CheckConclusionState + - CheckStatusState + - CheckSuiteAutoTriggerPreference + - CheckRun + - CheckRunConnection.nodes + - CheckRunEdge.node + - CheckRunAction + - CheckRunFilter + - CheckRunOutput + - CheckRunOutputImage + - CheckRunType + - CheckSuite + - CheckSuiteConnection.nodes + - CheckSuiteEdge.node + - CheckSuiteFilter + - CreateCheckRunInput + - CreateCheckRunPayload + - CreateCheckSuiteInput + - CreateCheckSuitePayload + - Commit.checkSuites + - Mutation.createCheckRun + - Mutation.createCheckSuite + - Mutation.rerequestCheckSuite + - Mutation.updateCheckRun + - Mutation.updateCheckSuitePreferences + - Subir + - RequestableCheckStatusState + - RerequestCheckSuiteInput + - RerequestCheckSuitePayload + - UpdateCheckRunInput + - UpdateCheckRunPayload + - UpdateCheckSuitePayload.checkSuite + - UpdateCheckSuitePreferencesInput + - UpdateCheckSuitePreferencesPayload + owning_teams: + - '@github/ecosystem-primitives' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/pe-repos' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Vista Previa de Comentarios Minimizados + description: >- + Esta vista previa agrega soporte para comentarios minimizados en incidentes, solicitudes de extracción, confirmaciones y gists. + toggled_by: ':queen-beryl-preview' + announcement: null + updates: null + toggled_on: + - Mutation.minimizeComment + - Mutation.unminimizeComment + - Minimizable + owning_teams: + - '@github/ce-community-and-safety' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/ecosystem-primitives' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de Comentarios de Línea Múltiple + description: Esta vista previa agrega soporte para comentarios de línea múltiple y posicionados en un blob. + toggled_by: ':comfort-fade-preview' + announcement: null + updates: null + toggled_on: + - Mutation.addPullRequestReviewThread + - AddPullRequestReviewThreadInput + - AddPullRequestReviewInput.threads + - DiffSide + - PullRequestReviewThread.startLine + - PullRequestReviewThread.originalStartLine + - PullRequestReviewThread.startDiffSide + - PullRequestReviewThread.line + - PullRequestReviewThread.originalLine + - PullRequestReviewThread.diffSide + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..9584265a3007e --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.20/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,562 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: ContributionOrder.field + description: 'Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden.' + reason: 'Se eliminará a `field`.' + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: Organization.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryOwner.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: User.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Organization.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Organization.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.color + description: 'Se eliminará a `color`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.latestVersion + description: 'Se eliminará a `latestVersion`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.name + description: 'Se eliminará a `name`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.nameWithOwner + description: 'Se eliminará a `nameWithOwner`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageFileByGuid + description: 'Se eliminará a `packageFileByGuid`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageFileBySha256 + description: 'Se eliminará a `packageFileBySha256`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageType + description: 'Se eliminará a `packageType`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.preReleaseVersions + description: 'Se eliminará a `preReleaseVersions`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.registryPackageType + description: 'Se eliminará a `registryPackageType`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.repository + description: 'Se eliminará a `repository`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.statistics + description: 'Se eliminará a `statistics`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.tags + description: 'Se eliminará a `tags`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.topics + description: 'Se eliminará a `topics`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.version + description: 'Se eliminará a `version`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionByPlatform + description: 'Se eliminará a `versionByPlatform`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionBySha256 + description: 'Se eliminará a `versionBySha256`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versions + description: 'Se eliminará a `versions`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionsByMetadatum + description: 'Se eliminará a `versionsByMetadatum`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.dependencyType + description: 'Se eliminará a `dependencyType`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.guid + description: 'Se eliminará a `guid`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.md5 + description: 'Se eliminará a `md5`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.metadataUrl + description: 'Se eliminará a `metadataUrl`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.packageVersion + description: 'Se eliminará a `packageVersion`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.sha1 + description: 'Se eliminará a `sha1`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.sha256 + description: 'Se eliminará a `sha256`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.size + description: 'Se eliminará a `size`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.url + description: 'Se eliminará a `url`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageOwner.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageSearch.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisMonth + description: 'Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisWeek + description: 'Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisYear + description: 'Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsToday + description: 'Se eliminará a `downloadsToday`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsTotalCount + description: 'Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageTag.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageTag` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageTag.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageTag` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.dependencies + description: 'Se eliminará a `dependencies`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.fileByName + description: 'Se eliminará a `fileByName`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.files + description: 'Se eliminará a `files`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.installationCommand + description: 'Se eliminará a `installationCommand`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.manifest + description: 'Se eliminará a `manifest`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.platform + description: 'Se eliminará a `platform`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.preRelease + description: 'Se eliminará a `preRelease`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.readme + description: 'Se eliminará a `readme`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.readmeHtml + description: 'Se eliminará a `readmeHtml`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.registryPackage + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.release + description: 'Se eliminará a `release`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.sha256 + description: 'Se eliminará a `sha256`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.size + description: 'Se eliminará a `size`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.statistics + description: 'Se eliminará a `statistics`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.summary + description: 'Se eliminará a `summary`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.updatedAt + description: 'Se eliminará a `updatedAt`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.viewerCanEdit + description: 'Se eliminará a `viewerCanEdit`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisMonth + description: 'Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisWeek + description: 'Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisYear + description: 'Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsToday + description: 'Se eliminará a `downloadsToday`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsTotalCount + description: 'Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Repository.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Repository.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: User.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: User.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi diff --git a/translations/es-ES/data/graphql/ghes-2.21/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-2.21/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..888d6ae384758 --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.21/graphql_previews.enterprise.yml @@ -0,0 +1,242 @@ +--- +- + title: Acceso al borrado de versiones de paquetes + description: >- + Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + - RegistryPackageVersion.deleted + owning_teams: + - '@github/pe-package-registry' +- + title: Registro del paquete de GitHub + description: Esta vista previa agrega soporte para los objetos que se relacionen con GitHub Packages. + toggled_by: ':packages-preview' + announcement: null + updates: null + toggled_on: + - Para GitHub + - PackageFile + - PackageFileOrder + - PackageFileOrderField + - PackageOrder + - PackageOrderField + - PackageOwner + - PackageStatistics + - PackageTag + - PackageVersion + - PackageVersionOrder + - PackageVersionOrderField + - PackageVersionStatistics + - Organization.packages + - PackageMetadatum.packageVersion + - Repository.packages + - User.packages + - PackageConnection.nodes + - PackageFileConnection.nodes + - PackageTagConnection.nodes + - PackageVersionConnection.nodes + - PackageEdge.node + - PackageFileEdge.node + - PackageTagEdge.node + - PackageVersionEdge.node + - CreatePackageVersionPayload.packageVersion + - UpdatePackageVersionPayload.packageVersion + - CreatePackageFilePayload.packageFile + - UpdatePackageFilePayload.packageFile + - CreatePackageVersionMetadataPayload.packageVersion + - AddPackageTagPayload.package + - DeletePackageTagPayload.package + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: Verificaciones + description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. + toggled_by: ':antiope-preview' + announcement: null + updates: null + toggled_on: + - CheckAnnotationRange + - CheckAnnotationPosition + - CheckAnnotationSpan + - CheckAnnotation + - CheckAnnotationConnection.nodes + - CheckAnnotationData + - CheckAnnotationEdge.node + - CheckAnnotationLevel + - CheckConclusionState + - CheckStatusState + - CheckSuiteAutoTriggerPreference + - CheckRun + - CheckRunConnection.nodes + - CheckRunEdge.node + - CheckRunAction + - CheckRunFilter + - CheckRunOutput + - CheckRunOutputImage + - CheckRunType + - CheckSuite + - CheckSuiteConnection.nodes + - CheckSuiteEdge.node + - CheckSuiteFilter + - CreateCheckRunInput + - CreateCheckRunPayload + - CreateCheckSuiteInput + - CreateCheckSuitePayload + - Commit.checkSuites + - Mutation.createCheckRun + - Mutation.createCheckSuite + - Mutation.rerequestCheckSuite + - Mutation.updateCheckRun + - Mutation.updateCheckSuitePreferences + - Subir + - RequestableCheckStatusState + - RerequestCheckSuiteInput + - RerequestCheckSuitePayload + - UpdateCheckRunInput + - UpdateCheckRunPayload + - UpdateCheckSuitePayload.checkSuite + - UpdateCheckSuitePreferencesInput + - UpdateCheckSuitePreferencesPayload + owning_teams: + - '@github/ce-extensibility' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/pe-repos' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/ce-extensibility' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..9f55753edcd4a --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.21/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,569 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: ContributionOrder.field + description: 'Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden.' + reason: 'Se eliminará a `field`.' + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Organization.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: RepositoryOwner.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: User.pinnedRepositories + description: 'Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución.' + reason: se eliminará a pinnedRepositories + date: '2019-10-01T00:00:00+00:00' + criticality: breaking + owner: cheshire137 + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Organization.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Organization.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.color + description: 'Se eliminará a `color`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.latestVersion + description: 'Se eliminará a `latestVersion`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.name + description: 'Se eliminará a `name`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.nameWithOwner + description: 'Se eliminará a `nameWithOwner`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageFileByGuid + description: 'Se eliminará a `packageFileByGuid`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageFileBySha256 + description: 'Se eliminará a `packageFileBySha256`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.packageType + description: 'Se eliminará a `packageType`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.preReleaseVersions + description: 'Se eliminará a `preReleaseVersions`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.registryPackageType + description: 'Se eliminará a `registryPackageType`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.repository + description: 'Se eliminará a `repository`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.statistics + description: 'Se eliminará a `statistics`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.tags + description: 'Se eliminará a `tags`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.topics + description: 'Se eliminará a `topics`. Utiliza el objeto `Package`.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.version + description: 'Se eliminará a `version`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionByPlatform + description: 'Se eliminará a `versionByPlatform`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionBySha256 + description: 'Se eliminará a `versionBySha256`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versions + description: 'Se eliminará a `versions`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackage.versionsByMetadatum + description: 'Se eliminará a `versionsByMetadatum`. Utiliza el objeto `Package` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.dependencyType + description: 'Se eliminará a `dependencyType`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageDependency.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageDependency` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.guid + description: 'Se eliminará a `guid`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.md5 + description: 'Se eliminará a `md5`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.metadataUrl + description: 'Se eliminará a `metadataUrl`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.packageVersion + description: 'Se eliminará a `packageVersion`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.sha1 + description: 'Se eliminará a `sha1`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.sha256 + description: 'Se eliminará a `sha256`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.size + description: 'Se eliminará a `size`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageFile.url + description: 'Se eliminará a `url`. Utiliza el objeto `PackageFile` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageOwner.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageSearch.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisMonth + description: 'Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisWeek + description: 'Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsThisYear + description: 'Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsToday + description: 'Se eliminará a `downloadsToday`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageStatistics.downloadsTotalCount + description: 'Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageTag.name + description: 'Se eliminará a `name`. Utiliza el objeto `PackageTag` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageTag.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageTag` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.deleted + description: 'Se eliminará a `deleted`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.dependencies + description: 'Se eliminará a `dependencies`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.fileByName + description: 'Se eliminará a `fileByName`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.files + description: 'Se eliminará a `files`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.installationCommand + description: 'Se eliminará a `installationCommand`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.manifest + description: 'Se eliminará a `manifest`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.platform + description: 'Se eliminará a `platform`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.preRelease + description: 'Se eliminará a `preRelease`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.readme + description: 'Se eliminará a `readme`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.readmeHtml + description: 'Se eliminará a `readmeHtml`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.registryPackage + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.release + description: 'Se eliminará a `release`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.sha256 + description: 'Se eliminará a `sha256`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.size + description: 'Se eliminará a `size`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.statistics + description: 'Se eliminará a `statistics`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.summary + description: 'Se eliminará a `summary`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.updatedAt + description: 'Se eliminará a `updatedAt`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.version + description: 'Se eliminará a `version`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersion.viewerCanEdit + description: 'Se eliminará a `viewerCanEdit`. Utiliza el objeto `PackageVersion` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisMonth + description: 'Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisWeek + description: 'Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsThisYear + description: 'Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsToday + description: 'Se eliminará a `downloadsToday`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: RegistryPackageVersionStatistics.downloadsTotalCount + description: 'Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageVersionStatistics` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Repository.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Repository.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: User.registryPackages + description: 'Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: User.registryPackagesForQuery + description: 'Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución.' + reason: Renombrar los campos y objetos de GitHub Packages. + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: dinahshi + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea diff --git a/translations/es-ES/data/graphql/ghes-2.22/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-2.22/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..192bbc33f2aea --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.22/graphql_previews.enterprise.yml @@ -0,0 +1,200 @@ +--- +- + title: Acceso al borrado de versiones de paquetes + description: >- + Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: Verificaciones + description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. + toggled_by: ':antiope-preview' + announcement: null + updates: null + toggled_on: + - CheckAnnotationRange + - CheckAnnotationPosition + - CheckAnnotationSpan + - CheckAnnotation + - CheckAnnotationConnection.nodes + - CheckAnnotationData + - CheckAnnotationEdge.node + - CheckAnnotationLevel + - CheckConclusionState + - CheckStatusState + - CheckSuiteAutoTriggerPreference + - CheckRun + - CheckRunConnection.nodes + - CheckRunEdge.node + - CheckRunAction + - CheckRunFilter + - CheckRunOutput + - CheckRunOutputImage + - CheckRunType + - CheckSuite + - CheckSuiteConnection.nodes + - CheckSuiteEdge.node + - CheckSuiteFilter + - CreateCheckRunInput + - CreateCheckRunPayload + - CreateCheckSuiteInput + - CreateCheckSuitePayload + - Commit.checkSuites + - Mutation.createCheckRun + - Mutation.createCheckSuite + - Mutation.rerequestCheckSuite + - Mutation.updateCheckRun + - Mutation.updateCheckSuitePreferences + - Subir + - RequestableCheckStatusState + - RerequestCheckSuiteInput + - RerequestCheckSuitePayload + - UpdateCheckRunInput + - UpdateCheckRunPayload + - UpdateCheckSuitePayload.checkSuite + - UpdateCheckSuitePreferencesInput + - UpdateCheckSuitePreferencesPayload + owning_teams: + - '@github/ce-extensibility' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/pe-repos' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/ce-extensibility' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..a899f20b5c3c8 --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-2.22/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,128 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros pendientes consumen una licencia + date: '2020-07-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: 'se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`.' + reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryCollaboratorEdge.permission + description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. + reason: Este campo podría devolver valores adicionales + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: oneill38 + - + location: RepositoryInvitation.permission + description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. + reason: Este campo podría devolver valores adicionales + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: oneill38 + - + location: RepositoryInvitationOrderField.INVITEE_LOGIN + description: 'Se eliminará a `INVITEE_LOGIN`.' + reason: '`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Sponsorship.sponsor + description: 'Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`.' + reason: 'Se eliminará a `Sponsorship.sponsor`.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: TeamRepositoryEdge.permission + description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. + reason: Este campo podría devolver valores adicionales + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: oneill38 + - + location: EnterpriseMemberEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores externos consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores pendientes consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon diff --git a/translations/es-ES/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..3a8b9b48db8e9 --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: Acceso al borrado de versiones de paquetes + description: >- + Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..476b946dca016 --- /dev/null +++ b/translations/es-ES/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros pendientes consumen una licencia + date: '2020-07-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: 'se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`.' + reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryInvitationOrderField.INVITEE_LOGIN + description: 'Se eliminará a `INVITEE_LOGIN`.' + reason: '`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Sponsorship.sponsor + description: 'Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`.' + reason: 'Se eliminará a `Sponsorship.sponsor`.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores externos consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores pendientes consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: 'El `DRAFT` se eliminará. Utiliza PullRequest.isDraft en su lugar.' + reason: El estado del DRAFT se eliminará de esta enumeración y se deberá utilizar `isDraft` en su lugar + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: nplasterer diff --git a/translations/es-ES/data/graphql/graphql_previews.yml b/translations/es-ES/data/graphql/graphql_previews.yml new file mode 100644 index 0000000000000..79f38eeccd1a5 --- /dev/null +++ b/translations/es-ES/data/graphql/graphql_previews.yml @@ -0,0 +1,166 @@ +--- +- + title: Acceso al borrado de versiones de paquetes + description: >- + Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implementaciones + description: >- + Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. + description: >- + Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Actualiza varias refs en una sola operación. + description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Acceso a la Gráfica de Dependencias de los Repositorios + description: Esta vista previa agrega soporte para leer una gráfica de dependencias para un repositorio. + toggled_by: ':hawkgirl-preview' + announcement: null + updates: null + toggled_on: + - DependencyGraphManifest + - Repository.dependencyGraphManifests + - DependencyGraphManifestEdge + - DependencyGraphManifestConnection + - DependencyGraphDependency + - DependencyGraphDependencyEdge + - DependencyGraphDependencyConnection + - DependencyGraphPackageRelease.dependencies + owning_teams: + - '@github/dsp-dependency-graph' +- + title: Detalles de Eventos del Proyecto + description: >- + Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Crear adjuntos de contenido + description: Esta vista previa agrega soporte para crear adjuntos de contenido. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Vista Previa de Incidentes Fijados + description: Esta vista previa agrega soporte para los incidentes fijados. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Vista Previa de Etiquetas + description: >- + Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Proyecto + description: Esta vista previa agrega soporte para importar proyectos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Vista Previa de las Tareas de Revisión del Equipo + description: >- + Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml new file mode 100644 index 0000000000000..a4ccba6c872c0 --- /dev/null +++ b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml @@ -0,0 +1,121 @@ +--- +upcoming_changes: + - + location: LegacyMigration.uploadUrlTemplate + description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.' + reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.' + reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.' + reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.' + reason: Los asignados ahora pueden ser maniquíes. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: Query.sponsorsListing + description: 'Se eliminará a `sponsorsListing`. Utiliza `Sponsorable.sponsorsListing` en sustitución.' + reason: 'Se eliminará a `Query.sponsorsListing`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: Sponsorship.maintainer + description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.' + reason: 'Se eliminará a `Sponsorship.maintainer`.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros pendientes consumen una licencia + date: '2020-07-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: 'se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`.' + reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Issue.timeline + description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.' + reason: 'Se eliminará a `timeline`' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryInvitationOrderField.INVITEE_LOGIN + description: 'Se eliminará a `INVITEE_LOGIN`.' + reason: '`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Sponsorship.sponsor + description: 'Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`.' + reason: 'Se eliminará a `Sponsorship.sponsor`.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los miembros consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores externos consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: 'Se eliminará a `isUnlicensed`.' + reason: Todos los colaboradores pendientes consumen una licencia + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: 'El `DRAFT` se eliminará. Utiliza PullRequest.isDraft en su lugar.' + reason: El estado del DRAFT se eliminará de esta enumeración y se deberá utilizar `isDraft` en su lugar + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: nplasterer diff --git a/translations/es-ES/data/learning-tracks/actions.yml b/translations/es-ES/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..ead26c879a746 --- /dev/null +++ b/translations/es-ES/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Inicia con {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'Puedes crear ejecutores autohospedados para ejecutar flujos de trabajo en un entorno altamente personalizable.' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/es-ES/data/products.yml b/translations/es-ES/data/products.yml new file mode 100644 index 0000000000000..6f397057938ad --- /dev/null +++ b/translations/es-ES/data/products.yml @@ -0,0 +1,16 @@ +--- +#this sequence sets the product order in the sidebar +#the product IDs match keys in lib/all-products.js +#note this file should not be translated +productsInOrder: + - github + - admin + - debates + - acciones + - packages + - developers + - rest + - graphql + - insights + - educación + - desktop diff --git a/translations/es-ES/data/release-notes/2-20/0.yml b/translations/es-ES/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000000..671ff634d3bf7 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'En una rama de repositorio, los administradores de éste pueden rechazar cualquier subida que contenga una confirmación de fusión si habilitan el `Requerir un historial lineal` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Los administradores de repositorio pueden otorgar a todos los usuarios con acceso de subida la capacidad de subir información forzadamente a una rama protegida si habilitan `Permitir las subidas forzadas` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Los administradores de repositorio pueden otorgar a todos los usuarios con permiso de subida la capacidad de borrar una rama protegida si habilitan `Permitir los borrados` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Los administradores pueden configurar un límite de `maxobjectsize` en los repositorios, [limitando el tamaño de las confirmaciones de subida](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para un repositorio que no esté en el [LFS de Git](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server).{% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Los propietarios de las organizaciones pueden crear un conjunto de etiquetas predeterminadas cuando crean un repositorio nuevo. {% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Los paquetes se actualizaron a las últimas versiones de seguridad. + bugs: + - 'Cuando los miembros de una organización intentan ver un repositorio público de éstas, un mensaje de SSO podría dañar la visualización de la página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "Cuando se visualiza el perfil de un usuario, los enlaces para los equipos de dicho usuario podrían estar rotos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Los usuarios con el rol de `maintain` no pudieron editar los temas del repositorio. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "Los usuarios que no son administradores de una organización recibieron un error 500 cuando intentaron acceder a la página de inicio de sesión. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'El mensaje emergente de edición de historial no se mostró en los comentarios de los gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'Una cuenta nueva pudo registrarse con un correo electrónico que ya estaba registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'Un servicio de almacenamiento estaba alcanzando un límite de descripción de archivo y causando el bloqueo del kernel y que otros servicios registraran errores. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'Cuando una referencia de autoenlace fue parte de una url, el hipervículo podría haberse eliminado. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'Cuando se agrega un comentario a una solicitud de cambios, la sección de `Propuestas vinculadas` de la barra lateral podría haber desaparecido. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'Al editar una invitación existente a una organización para un usuario, un encabezado duplicado pudo haber aparecido en la tabla de `Equipos`. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'El servicio `resqued` pudo haber dejado de registrar eventos cuando las colas eran muy largas. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Los certificados auto-firmados no se generan automáticamente al ejecutar el comando `ghe-config-apply` para las configuraciones de agrupamientos y de disponibilidad alta. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No se mostrará ningún logo para un tema si no se ha cargado alguno. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'Cuando se visualiza una propuesta en un buscador móvil, sus metadatos se listan en la parte superior de la página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'El dominio de nivel superior de Consul cambió de ".consul" a ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'El servicio de hooshot ya no depende de ElasticSearch y solo utiliza MySQL como almacenamiento de base de datos. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'La distinción visual entre propuestas, proyectos y debates se implementó en tarjetas de notas de proyecto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'En una revisión de solicitud de cambios, se muestra una notificación si un comentario de línea múltiple se trunca. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Los usuarios pueden visualizar su bitácora de auditoría en la pestaña de `Bitácora de seguridad` de su página de configuración personal. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Las entradas duplicadas de webhooks en la base de datos pueden causar que las mejoras de las versiones anteriores fallen. (actualizado 2020-02-26) + - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/1.yml b/translations/es-ES/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000000..90859cf64b784 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'El hacer restauraciones desde los respaldos fallará con un error de tipo `Invalid RDB version number`. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'El mejorar una replica de HA estancó indefinidamente la espera para que iniciara MySQL. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'Los comentarios de revisión de las PR con valores inesperados para "position" o "original_position" ocasionó que fallaran las importaciones. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Las entradas de webhook duplicadas en la base de datos podría causar que las mejoras de las versiones previas fallaran. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/10.yml b/translations/es-ES/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000000..738f4e8c3b5b9 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Las bitácoras de eventos excesivamente grandes podrían ocasionar inestabilidad en el reenvío de bitácoras cuando se utiliza UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "El dejar de suspender a un usuario automáticamente mediante SSO no se completa si el atributo de las llaves SSH ya está asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'El hash de permiso del repositorio desde la API de REST no indicó acceso de los miembros de negocios que tienen acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'No se interpretó adecuadamente la vista previa de la descripción de una GitHub App escrita en lenguaje de marcado. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'La bitácora de auditoría no incluyó los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "El intentar asignar una revisión de código a un miembro de un equipo vacío resultó en un '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'La asignación de revisión de código utilizando el algoritmo de balanceo de carga pudo asignarse repetidamente al mismo miembro del equipo. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/11.yml b/translations/es-ES/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000000..58c9d5e5cb36b --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '09-07-2020' +sections: + security_fixes: + - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'La gráfica de dependencias no estaba detectando dependencias cuando se desplegó en una configuración de agrupamiento con nodos múltiples de Redis. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Algunos archivos de bitácora no rotaron cada 7 días. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'La reutilización rápida de puertos origen de webhooks dio como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Los jobs incorrectos en segundo plano pudieron intentar ejecutarse en instancias que se configuraron como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Los repositorios internos no se incluyeron correctamente en los resultados de búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/12.yml b/translations/es-ES/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000000..84a499fe65140 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '21-07-2020' +sections: + security_fixes: + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'Las gráficas de monitoreo de la consola de adminsitración a veces no se muestra correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde la política de SameSite Cookie se aplicó. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Mejoras al escalamiento de HAProxy. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/13.yml b/translations/es-ES/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000000..51706af2029af --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GitHub Enterprise Server. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'Los cálculos de asignación de memoria de servicio pudieron asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo cual dio como resultado un rendimiento pobre del sistema. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'La plataforma de virtualización para los sistemas de oVirt KVM no se detectó adecuadamente, lo cual ocasionó problemas durante las mejoras. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "El mensaje de error para la autenticación inválida con una contraseña a través de la línea de comandos de Git no llenó la URL que vinculaba a agregar el token o llave SSH adecuados. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect estaba utilizando una terminal obsoleta de la API de GitHub.com. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Las propuestas no se pudieron clasificar por *Actualizadas recientemente* en los repositorios que se migraron a una instancia nueva. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'La página con error 404 contenía los enlaces de estado y contacto de GitHub.com en el pié de página. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/14.yml b/translations/es-ES/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000000..f64d20c6206c3 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Se resolvió un problema que pudo haber llevado a un uso alto de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Los cambios recientes a las asignaciones de memoria pudieron haber llevado a una degradación en el rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/15.yml b/translations/es-ES/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000000..ea9c2f763c27e Binary files /dev/null and b/translations/es-ES/data/release-notes/2-20/15.yml differ diff --git a/translations/es-ES/data/release-notes/2-20/16.yml b/translations/es-ES/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000000..fbab7d0c79422 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '08-09-2020' +sections: + bugs: + - 'Una revisión de salud del servicio causó un crecimiento de sesión que resultó en el agotamiento del sistema de archivos en el nodo. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Hacer mejoras utilizando hotpatches podría fallar con un error de `'libdbi1' was not found`{% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/17.yml b/translations/es-ES/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000000..153edb5399877 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '23-09-2020' +sections: + security_fixes: + - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/18.yml b/translations/es-ES/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000000..cca5eda8b8141 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - 'El usuario cuyo nombre de usuario del directorio de LDAP se estandarice a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'El guardar las configuraciones a través de la [consola de administración](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) añadirá una línea nueva en los archivos de la [llave y certificado TLS/SSL](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls), lo cual activó la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/19.yml b/translations/es-ES/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000000..0cb4255b590c5 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/2.yml b/translations/es-ES/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000000..c2254d14e197f --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'En algunos casos, las entradas de bitácora reenviadas, principalmente para audit.log, se estaban truncando. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'La utilidad de línea de comandos `ghe-license-check` devolvió un error de "Invalid license file" para algunas licencias válidas, lo cual causó que fallaran los cambios de configuración. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'El syslog no reenvió las bitácoras de excepciones de Alambic. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'El [evento `org_block`](https://developer.github.com/v3/activity/events/types/#orgblockevent) no se encuentra como "no disponible" pero aparecía en las GitHub Apps en GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'Las respuestas de consulta de GraphQL a veces devolvían identificadores de nodo incoincidentes para los objetos de `ProtectedBranch` {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'La credencial de GtHub App que utilizó GitHub Connect falló en actualizarse inmediatamente después de su vencimiento. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'El dejar comentarios de repsuesta en un comentario de una solicitud de cambios creó intermitentemente una revisión de solciitud de cambios pendiente. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Al utilizar a ghe-migrator o exportar desde GitHub.com, una exportación falla silenciosamente en exportar adjuntos que no sean imágenes. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Los ganchos de pre-recepción devolvieron un error 500 en la IU web cuando se encontraron caracteres UTF-8. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'La utilidad de línea de comandos ` ghe-license-usage ` incluye una opción `--unencrypted` nueva para proporcionar visibilidad en el archivo de uso de licencia exportado. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/20.yml b/translations/es-ES/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000000..3a9b2bb9994ec --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIA:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' + bugs: + - 'Los usuarios suspendidos se incluyeron en la lista de usuarios sugeridos, ocultando potencialmente a los usuarios que no se habían suspendido. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/21.yml b/translations/es-ES/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000000..09bc73f8cfb94 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/22.yml b/translations/es-ES/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000000..fe2e7e480ea5c --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Cuando se inicia sesión después de intentar visitar una página específica, se enviaba a las personas a la página de inicio en vez de a su destino previsto. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/23.yml b/translations/es-ES/data/release-notes/2-20/23.yml new file mode 100644 index 0000000000000..c573890a1f5ce --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/23.yml @@ -0,0 +1,13 @@ +--- +date: '2020-12-17' +sections: + security_fixes: + - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/3.yml b/translations/es-ES/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000000..12f3f1bfdf405 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Las mejoras y actualizaciones de configuración podrían fallar si las configuraciones en segundo plano de los trabajadores se personalizaron. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/4.yml b/translations/es-ES/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000000..829039d36d408 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'Las solicitudes de autenticación de SAML y los metadatos no se cifraron estrictamente, lo cual causó que algunos proveedores de identidad no procesaran adecuadamente las solicitudes de autenticación que inició el proveedor de servicios. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - 'Las exportaciones de `ghe-migrator no contenían usuarios de hito, lo cual pudo haber interrumpido las operaciones de importación. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'Cuando se sube información a un Gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - 'El `ghe-repl-status` podría fallar cuando se trata de mostrar los repositorios que no se replicaron integralmente. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/5.yml b/translations/es-ES/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000000..f196773ea1b2a --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '07-04-2020' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'El tamaño máximo de 100MB en un objeto de Git no se pudo seleccionar para un repositorio cuando la cuenta empresarial global configuró una opción de tamaño de objeto de Git diferente a 100MB. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Los resultados de la API de propuestas y de solicitudes de cambio pudieron tener un comportamiento inconsistente cuando se ordenaron por el campo `updated_at`. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'El campo `package` de las vulnerabilidades de seguridad no pudo consultarse a través de la API de GraphQL. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Cambiar un repositorio de *público* a *interno* mostró un mensaje de facturación irrelevante. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/6.yml b/translations/es-ES/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000000..c37a9e45954d6 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**ALTA**: OpenSSL se actualizó a la dirección [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' + - '**ALTA**: Se actualizó Git para tratar el [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) y [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). Las restricciones nuevas previenen que los repositorios maliciosos se suban a la instancia del servidor, lo cual protege a los clientes que no se hayan parchado aún. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**BAJO**: ImageMagick se actualizó a la dirección [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'El usuario de git no tenía permisos para invocar a los procesos que se requerían para convertir los repositorios existentes que utilizaban Subversion, desde el formato de la v4 al LRS de la v3. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'Una disparidad en las configuraciones de MySQL pudo haber causado que los respaldos fallaran en las instalaciones grandes. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'Cuando se hacen mejoras desde versiones previas, los trabajadores de jobs en segundo plano algunas veces no se generaron, lo cual previnió las características esenciales tales como fusionar solicitudes de cambios. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "Cuando una licencia de GitHub Enterprise Server contenía caracteres diferentes a los de ASCII, las solicitudes de tipo `GET` a la terminal `/setup/api/settings` de la API de la consola de administración resultó en un Error Interno del Servidor. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'La consola de recuperación solicitó una contraseña de raíz, aún si la cuenta raíz estaba bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'Un archivo de CODEOWNRS con una marca de orden inicial en UTF-8 causó que todas las reglas de codeowners se ignoraran. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'Cuando el job de cron de orquestador-cliente falló, varios correos electrónicos se enviaron a la cuenta raíz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "Cuando un proveedor de identidad externo controló el estado de administrador del sitio de un usuario, los usuarios no se podían bajar de categoría a través de la utilidad de la línea de comandos. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/7.yml b/translations/es-ES/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000000..79ee352ed5dab --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '05-05-2020' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - 'Tanto `ghe-repl-start` como `ghe-repl-status` presentaron errores de sintaxis. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'Si un repositorio tenía habilitada la configuración de "borrar ramas de encabezado automáticamente", la rama de encabezado no se borró automáticamente cuando una solicitud de cambios se fusionó con una instalacción de GitHub App. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'Cuando se reinstauró a un miembro de una organización, la carga útil del webhook reportó al usuario `fantasma` como el remitente y no al usuario que realmente realizó la reinstauración. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'Si un repositorio tiene habilitada la configuración de "borrar automáticamente las ramas de encabezado", la rama de encabezado no se borró cuando el repositorio de encabezado era diferente al repositorio base. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'La recolección de basura de archivos temporales pudo haber ocacionado un error de validación de licencia. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'En algunas situaciones, incluyendo cuando un repositorio se crea por primera vez, el gancho de pre-recepción se ejecutó sin un valor que se llenara para la variable de ambiente GITHUB_REPO_PUBLIC. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/8.yml b/translations/es-ES/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000000..057807a2a3b7c --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'Después de que se actualizó el archivo de licencia, los servicios no se recargaron adecuadamente, lo cual ocasionó una pérdida de funcionalidad. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Las solicitudes internas a la API que actualizaban la información de la gráfica de dependencias podrían fallar si el cuerpo de la respuesta era muy largo. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'No se respetó el argumento de `afiliaciones` en algunas de las conexiones de repositorio de GraphQL. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'El dejar de suspender un usuario mediante SSO no se completó si el atributo de correo electrónico de SAML tenía una cubierta diferente que el del correo electrónico de usuario de GitHub. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restablecer la membrecía de un usuario en una organización no instrumentó al actor en las cargas útiles del webhook y de la bitácora de auditoría. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/9.yml b/translations/es-ES/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000000..8b961d34141fa --- /dev/null +++ b/translations/es-ES/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**ALTA:** Se identificó una vulnerabilidad de control de accesos impropia en la API de GitHub Enterprise Server que permitió a un miembro de una organización escalar los permisos y obtener acceso a repositorios no autorizados dentro de la organización. Dicha vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 2.21. Hemos emitido el [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) como respuesta a este problema. La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Los motors de búsqueda pueden indizar las instancias de GitHub Enterprise Server de cara al internet. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/0.yml b/translations/es-ES/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000000..fce0ca85e98f5 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '09-06-2020' +sections: + features: + - 'Los usuarios pueden [administrar las notificaciones](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) en las propuestas, solicitudes decambios y otros temas cuando navegan desde una notificación web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Los usuarios pueden [convertir las solicitudes de cambio nuevamente en un "Borrador"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - 'Las [Sugerencias de línea múltiple](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) permiten que un usuario sugiera un cambio específico para las líneas de código múltiple cuando se está revisando una solicitud de cambios. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Los usuarios con acceso de escritura en un repositorio pueden [ocultar un comentario en una propuesta o solicitud de cambios como "Duplicado"](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'Cuando se [crea un repositorio desde una plantilla](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) los usuarios pueden seleccionar opcionalmente el incluir todas las ramas en vez de solo la predeterminada. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Las tarjetas de proyecto de las propuestas incluyen una sección de solicitudes de cambios vinculadas](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) para que los usuarios puedan ver qué tipo de trabajo de desarrollo se relaciona con la propuesta directamente desde el tablero de proyecto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'Existe un conjunto nuevo de [terminales de "borrar reacciones"](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) en la API de reacciones. Las terminales de "Borrar reacciones" existentes se obsoletizarán en la primera mitad de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'Existe un conjunto nuevo de [Terminales de la API de equipos](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirá a GitHub escalar y tener compatibilidad con la API de equipos a la larga. Las terminales existentes de la API se obsoletizarán en la primera mitad del 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Los usuarios pueden [crear enlaces entre las propeustas y las solicitudes de cambios](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) sin necesitar utilizar las palabras claves de cierre en la descripción de la solicitud de cambios. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'Se identificó una vulnerabilidad de control de accesos impropia en la API de GitHub Enterprise Server que permitió a un miembro de una organización escalar los permisos y obtener acceso a repositorios no autorizados dentro de la organización. Dicha vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 2.21. Hemos emitido el [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) como respuesta a este problema. La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "Si un usuario con acceso de subida minimiza el comentario de otro usuairio, el autor del comentario podría dejar de minimizarlo aún si tuviese privilegios insuficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Los usuarios podrían fusionar accidentalmente hacia la rama principal desde el editor de plantillas de propuesta y de blobs. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'Cuando un usuario borró una cuenta de GitHub, los registros de la bitácora de auditoría no mostraron correctamente los registros de eliminación de la organización. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'El avatar de gist para el usuario actual enlazó a una URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'La pestaña de repositorios de la organización no incluyó los repositorios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Dar clic en el botón de "Mostrar todos los equipos" cuando se transfiere un repositorio causó un error 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Los nombres de archivo grandes causan problemas de desbordamiento cuando se muestra la etiqueta 'Cambió desde la última vista' o la alternación de diff de 'Mostrar enriquecido' en la vista de archivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Las tarjetas de visita virtual para los equipos de la organización reportó mal su capacidad de miembros. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'La ventana emergente del comentario de la revisión de solicitudes de cambios tenía un problema desplazamiento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy podría saturarse y causar una ralentización en las opreaciones de git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'La característica de la gráfica de dependencias no se habilitó automáticamente después de una promoción de réplica de HA. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'Puede que se activara un límite de tiempo en la página de índice de lanzamientos para los repositorios con miles de solicitudes de cambios. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'No fue posible filtrar las solicitudes de cambios tanto por estado como por borrador al mismo tiempo. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'Si una solicitud de cambios cambió un indicador de submódulo, entonces el dar clic en "Editar archivo" en dicho archivo de submódulo desde la pestaña de "Archivos que cambiaron" de la solicitud de cambios causó un error 404. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'No fue posible agregar usuarios a una organización o borrar la organización siguiendo la eliminación por lotes de todos los usuarios y administradores de ella. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Los comentarios de revisión contra los archivos que contenían caracteres diacríticos y diferentes a los latinos en el nombre de archivo dentro de la página de "Archivos con cambios" desapareció cuando se volvió a cargar la página. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'El estado de la casilla de verificación "Visto" no se retuvo para los archivos que contenían caracteres diacríticos o diferentes a los latinos en el nombre de archivo en la páina de "Archivos que cambiaron". {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Las solicitudes de cambios mostraron la insignia "Aprobada" cuando aún no se llevaban a cabo todas las revisiones requeridas. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'El menú desplegable de la etiqueta estaba vacío cuando se buscaba una etiqueta en los repositorios con más de 100 de ellas. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Las páginas de solicitudes de extracción que mostraban anotaciones con títulos con un cifrado diferente al de UTF-8 pudieron encontrarse con errores de cifrado en la representación de la vista. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'Una condición de carrera para la actualización de la página de OAuth pudo haber causado que un redireccionamiento se ejecutara dos veces. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'La página de "Tokens de acceso personal" agotaba el tiempo si había más de 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Los jobs de sincronización programados para usuarios y equipos de LDAP pudieron haberse iniciado mientras que los jobs de sincronización programados previamente aún estaban en proceso. Un mecanismo de bloqueo se implementó para prevenir que los jobs de sincronización nuevos comenzaran si alguno de ellos aún se estaba ejecutando. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'Se actualizó la interface de notificaciones web, incluyendo los [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) y [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) nuevos. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Ahora es posible inhabilitar la reactivación de los usuarios de LDAP en la sincronización de LDAP. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'La redacción de la rama protegida de subida se actualizó para aclarar que los administradores siempre pueden subir información y que los usuarios con el rol de mantenedor pueden subir información cuando pasen las verificaciones de estado. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevenir las confirmaciones en blanco cuando la sugerencia es idéntica al original. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'La paginación es compatible como una forma de obtener más archivos en el diff asociado con una confirmación a través de la API de REST. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Los administradores pueden habilitar, inhabilitar, borrar y buscar webhooks utilizando la ID de webhook desde la línea de comandos y utilizando `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'La reorientación base automática sucederá despues de una limpieza manual de referencia de encabezado para una solicitud de cambios fusionada. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'Los archivos SVG se manejan como texto y como imágenes en el visualizador de diffs. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'La configuración de "borrar automáticamente las ramas en fusión" puede configurarse cuando se crea y actualiza un repositorio utilizando la API de REST. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'Se agregó una terminal nueva para borrar despliegues a través de la API de REST. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Los administradores pueden [habilitar las alertas de seguridad](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) pero inhabilitan todas las notificaciones de estas alertas. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'La bitácora de Pages muestra la información de inicio de sesión de un usuario que accede al sitio de GitHub Pages. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Los miembros empresariales pueden ver todas las organizaciones a las que pertenecen como parte de su cuenta empresarial desde una vista si navegan a `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[La compatibilidad de la API de REST para los roles de mantenimiento y clasificación]](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) se expandió. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'Un usuario puede crear y compartir las consultas de búsqueda que resuelven al usuario actual si utiliza la sintaxis de búsqueda `@me` {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'Se [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/) opciones de configuración nuevas para las plantillas de propuestas. {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'Se mejoró la confiabilidad y tiempo de compleción para la restauración y respaldo de MySQL. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Visibilidad mejorada](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) de las referencias de las solicitudes de cambios y propuestas en la barra lateral, tarjetas y listas de las propuestas. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Los usuarios pueden filtrar y buscar por `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Ahora es posible la recuperación automática de fallas de MySQL dentro de una sola región para los despliegues de agrupamientos. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'Un usuario puede comparar etiquetas entre dos lanzamientos para determinar qué cambios se hicieron en la página de lanzamientos. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Los comentarios desactualizados ya no se colapsan predeterminadamente en la línea de tiempo de una solicitud de cambios. Pueden colapsarse si se resuelve el hilo. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Los administradores pueden ver una lista de inicios de sesión reservados para uso interno si navegan a la pestaña de "inicios de sesión reservados" de stafftools. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/1.yml b/translations/es-ES/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000000..a7846c65f7811 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Las bitácoras de eventos excesivamente grandes podrían ocasionar inestabilidad en el reenvío de bitácoras cuando se utiliza UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'El servicio de comunicación interna que se utiliza para acceder a MySQL podría reiniciarse más frecuentemente de lo requerido, incluyendo a mitad del proceso de actualización, lo cual podría ocasionar que dicha actualización falle parcialmente. Redujimos la tasa de reinicios e hicimos el código más robusto. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "El dejar de suspender a un usuario automáticamente mediante SSO no se completa si el atributo de las llaves SSH ya está asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'El hash de permiso del repositorio desde la API de REST no indicó acceso de los miembros de negocios que tienen acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'La política empresarial de "borrado de propuestas del repositorio" no reflejó la configuración que se guardó actualmente. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'La bitácora de auditoría no incluyó los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/10.yml b/translations/es-ES/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000000..e6bbeb8e7d3a5 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/11.yml b/translations/es-ES/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000000..2303c6d1bc991 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIA:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' + bugs: + - 'El editar las plantillas de las propuestas con los nombres de archivo que contienen caracteres que no son de ASCII fallará con un mensaje de "500 Internal Server Error".{% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'Un método de recolección métrica para los jobs en segundo plano incrementó el uso del CPU. (actualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP de origen real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/12.yml b/translations/es-ES/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000000..54c30d34e3400 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Las bitácoras de auditoría podrían atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/13.yml b/translations/es-ES/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000000..a18363a796a37 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Cuando se inicia sesión después de intentar visitar una página específica, se enviaba a las personas a la página de inicio en vez de a su destino previsto. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/14.yml b/translations/es-ES/data/release-notes/2-21/14.yml new file mode 100644 index 0000000000000..cf5b9ebca406c --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-12-17' +sections: + security_fixes: + - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (Dos).{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/2.yml b/translations/es-ES/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000000..501875fbb3654 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '09-07-2020' +sections: + security_fixes: + - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Algunos archivos de bitácora no rotaron cada 7 días. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'La reutilización rápida de los puertos origen de los webhooks dieron como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Los jobs incorrectos en segundo plano pudieron intentar ejecutarse en instancias que se configuraron como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'La VPN entre nodos pudo hacerse inestable causando que los errores se registraran y que el espacio libre en el volúmen raíz se agotara. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Los repositorios internos no se incluyeron correctamente en los resultados de búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/3.yml b/translations/es-ES/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000000..0a50eda8ea7ee --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '21-07-2020' +sections: + security_fixes: + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'Las gráficas de monitoreo de la consola de adminsitración a veces no se muestra correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde la política de SameSite Cookie se aplicó. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "En algunas circunstancias, acceder a la página de 'Explorar' arrojó un error de aplicación. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/4.yml b/translations/es-ES/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000000..652512ca63899 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GHES. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'Los cálculos de asignación de memoria de servicio pudieron asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo cual dio como resultado un rendimiento pobre del sistema. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'La plataforma de virtualización para los sistemas de oVirt KVM no se detectó adecuadamente, lo cual ocasionó problemas durante las mejoras. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "El mensaje de error para la autenticación inválida con una contraseña a través de la línea de comandos de Git no llenó la URL que vinculaba a agregar el token o llave SSH adecuados. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'El crear una propuesta en un repositorio de usuario utilizando la característica de plantillas de propuestas podría fallar con un Error Interno del Servidor. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'El visitar la sección de *Explorar* falló con un error interno del servidor 500. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Las propuestas no se pudieron clasificar por *Actualizadas recientemente* en los repositorios que se migraron a una instancia nueva. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect estaba utilizando una terminal obsoleta de la API de GitHub.com. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'La recolección de métricas internas para los jobs en segundo plano contribuyó al uso innecesario de memoria y CPU. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'La página con error 404 contenía los enlaces de estado y contacto de GitHub.com en el pié de página. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Los jobs en segundo plano para una característica que no se había lanzado se pusieron en cola y se dejaron sin procesar. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/5.yml b/translations/es-ES/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000000..8fae39ac52548 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Se resolvió un problema que pudo haber llevado a un uso alto de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Los cambios recientes a las asignaciones de memoria pudieron haber llevado a una degradación en el rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Los problemas temporales de conectividad mientras se ejecutaban las migraciones de base de datos pudieron causar una pérdida de datos. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/6.yml b/translations/es-ES/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000000..a703831785aaf Binary files /dev/null and b/translations/es-ES/data/release-notes/2-21/6.yml differ diff --git a/translations/es-ES/data/release-notes/2-21/7.yml b/translations/es-ES/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000000..e054f52962dbc --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '08-09-2020' +sections: + bugs: + - 'Una revisión de salud del servicio causó un crecimiento de sesión que resultó en el agotamiento del sistema de archivos en el nodo. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Hacer mejoras utilizando hotpatches podría fallar con un error de `'libdbi1' was not found`{% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/8.yml b/translations/es-ES/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000000..c858a253382e8 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '23-09-2020' +sections: + security_fixes: + - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Los administradores no pudieron ver los webhooks de repositorio que se entregaron y vieron la leyenda "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook" en vez de esto. {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/9.yml b/translations/es-ES/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000000..d202d7ed0457f --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - 'El usuario cuyo nombre de usuario del directorio de **LDAP** se estandariza a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'El guardar las configuraciones a través de la [consola de administración](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) añadirá una línea nueva en los archivos de la [llave y certificado TLS/SSL](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls), lo cual activó la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'La mejora podría fallar si los trabajadores que se volvieron a poner en cola (resqued) invalidan la configuración que se está utilizando. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'La página de configuración de seguridad para la cuenta empresarial mostró un enlace para "Visualizar las configuraciones actuales de tus organizaciones" para la configuración de "autenticación bifactorial" cuando el modo de autenticación no es compatible con la autenticación bifactorial incluida. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/0.yml b/translations/es-ES/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000000..c02c6509df8cf --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/0.yml @@ -0,0 +1,144 @@ +--- +intro: GitHub se emociona en presentar GitHub Enterprise Server 2.22.0. +date: '23-09-2020' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) es un servicio de hospedaje de paquetes, integrado nativamente con las API, Acciones y webhooks de GitHub. Crea un [Flujo de trabajo de DevOps de extremo a extremo](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) que incluye tu código, integración contínua y soluciones de despliegue. + + El almacenamiento compatible de lado del servidor incluye a AWS S3 y a MinIO con compatibilidad para Azure blob en un lanzamiento futuro. Por favor, nota que la compatibilidad actual con Docker se reemplazará por un beta del nuevo Registro de Contenedores de Github en el próximo lanzamiento. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que actives GitHub Packages. Para aprender más, contacta al equipo de ventas de GitHub o [regístrate para el beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Escaneo Avanzado de Seguridad de Código Beta + notes: + - | + [El escaneo avanzado de seguridad de código de GitHub](https://github.com/features/security) es un ambiente de pruebas de seguridad para aplicaciones estáticas (SAST) nativo de GitHub. Encuentra vulnerabilidades de seguridad fácilmente antes de que lleguen al ambiente productivo, todo impulsado con el motor de análisis de código más poderoso del mundo: CodeQL. + + Los administradores que utilicen la Seguridad Avanzada de Github pueden [registrarse para](https://resources.github.com/beta-signup/) y [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) el beta del escaneo avanzado de seguridad de código de GitHub. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que actives el escaneo avanzado de seguridad de código. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Redireccionamiento de solicitudes de cambios + notes: + - | + Cuando una [rama de encabezado de una solicitud de cambios](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) se fusiona y borra, el resto de las solicitudes de cambios abiertas en el mismo repositorio que se dirigen a esta rama + ahora se redireccionan a la rama base fusionada de la solicitud de cambios. Anteriormente, estas solicitudes de cambios se cerraron. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspender y dejar de suspender la instalación de una app + notes: + - | + Los administradores y usuarios pueden [suspender cualquier tipo de acceso a las GitHub Apps](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) por tanto tiempo como sea necesario, y [dejar de suspender la app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) a voluntad mediante la configuración y la API. Las apps suspendidas no pueden acceder a la API o a los eventos de webhook de GitHub. Puedes utilizar esto en vez de desinstalar una aplicación, lo cual revoca la autorización a todos los usuarios. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Rendimiento mejorado a gran escala + notes: + - | + Hemos revisado el acercamiento que tomamos para programar el mantenimiento de red para los repositorios, asegurándonos que los mono-repositorios grandes puedan evitar estados de fallo. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' + + Las réplicas pasivas ahora [son compatibles y configurables en los despliegues de agrupamiento de GitHub Enterprise Server](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). Estos cambios habilitarán una recuperación de fallos más rápida, reduciendo tanto el RTO como el RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: Ver todos tus usuarios + notes: + - | + Para los equipos exepcionalmente grandes, los administradores pueden [ajustar el máximo predeterminado de 1,500 elementos para las listas de usuario](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' + changes: + - + heading: Cambios en la administración + notes: + - Los trabajadores compartidos se habilitaron para proporcionar más resiliencia a las actualizaciones en vivo al compartir las conexiones entre las pestañas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - El enlace de "Contacta a soporte" en las páginas de error de `50x` ahora te enlaza con el correo electrónico de soporte o con el enlace configurado en la consola de administración. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'Ahora es posible [administrar los anuncios globales y las fechas de vencimiento a través de la configuración de cuenta empresarial](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}' + - Ahora puedes [exentar a algunos usuarios de los límites de tasa predeterminados de la API que se configuran en la consola de administración](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), en caso de que sea necesario. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Los administradores de repositorio ahora pueden [configurar su repositorio con cualquier opción de visibilidad disponible](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) desde un diálogo único en la configuración del repositorio. Anteriormente, tenías que navegar entre secciones, botones y cajas de diálogo separadas para cambiar entre las visibilidades pública y privada y entre las internas y privadas. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - Un enlace nuevo de configuración empresarial en el menú desplegable del usuario facilita la navegación a los ajustes de la cuenta empresarial. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %} + - Se eliminó el enlace tradicional de "Centro de administración" en la página de /stafftools. El enlace de "Empresa" ahora es la mejor forma de navegar a la cuenta empresarial desde la página de /stafftools. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - El elemento de sub-menú de opciones en la configuración de la cuenta empresarial se migró desde la sección de Configuración hasta la de Políticas. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[El acceder a los recursos de acceso utilizando un token de acceso personal o una llave SSH ahora cuenta como una actividad de usuario](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). Esto evita a los administradores la carga de filtrar algunos usuarios de los reportes de usuarios durmientes y hace más seguro el uso del botón "Suspender todos" sin suspender accidentalmente a los usuarios que solo acceden a GitHub en forma de solo lectura a través de las API con un token de acceso personal (PAT) o llave SSH. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' + - + heading: Cambios de seguridad + notes: + - Los códigos de recuperación bifactoriales ya no pueden utilizarse durante el proceso de inicio de sesión con dos factores. Las contraseñas de una sola ocasión son los únicos valores aceptables. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - Cuando un usuario inicia sesión en GitHub Enterprise Server mediante un inicio de sesión único, la [selección de visibilidad predeterminada del repositorio es privada](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %} + - Los propietarios de las GitHub Apps ahora pueden escoger que sus [tokens de acceso de usuario a servidor venzan después de 8 horas](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), para ayudar a reforzar la rotación habitual de tokens y reducir el impacto de que existan tokens en riesgo. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Cambios de desarrollador + notes: + - '[La IU de GitHub actualizó su diseño](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), y la página principal de los repositorios se rediseñó e incluyó un diseño receptivo yuna experiencia web móvil mejorada. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - En el menú desplegable "Clonar con SSH" de los repositorios, se notificará ahora a los usuarios si no han configurado ninguna llave. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Las confirmaciones ahora se ordenan cronológicamente en la línea de tiempo de las solicitudes de cambios y en la pestaña de confirmaciones. Este orden nuevo también se refleja en la API de REST de ["Listar comnfirmaciones en una solicitud de cambios"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) y en el ["Objeto PullRequest"] de GraphQL (https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Los usuarios ahora pueden [configurar un tono de tema predeterminado para los resultados de autocompletado de emojis](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) en las áreas de texto de los comentarios. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) mejora el resaltado de sintaxis y ahora es la biblioteca predeterminada que se utiliza para en análisis de los lenguajes de programación. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Los usuarios y las organizaciones pueden agregar nombres de usuario de Twitter a sus perfiles de GitHub + notes: + - '[Los desarrolladores y las organizaciones ahora pueden agregar sus nombres de usuario de Twitter a sus perfiles](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' + - + heading: Cambios a la API + notes: + - | + #### Vistas previas graduadas + + Las siguientes vistas previas ahora son parte oficial de la API: + * La API y terminales de las GitHub Apps que devolvían la propiedad `performed_via_github_app` ya no requieren el encabezado de vista previa [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/). {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * Para agregar y ver una razón de bloqueo de una propuesta, ya no necesitas utilizar el encabezado de vista previa [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/). {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### Cambios al modelo de GraphQL + + * [Los cambios al modelo de GraphQL](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) incluyen aquellos retro-compatibles, vistas previas del modelo, y cambios significativos próximos. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} + bugs: + - La página de stafftools para visualizar colaboradores pendientes mostró un `500 Internal Server Error` cuando había una invitación de correo electrónico pendiente. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - La verificación desalud del repositorio en stafftools puede mostrar resultados incorrectos en los repositorios ocupados. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - Un usuario que inició sesión e intentó aceptar una invitación por correo electrónico pudo encontrarse con un error `404 Not Found`. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - Si los usuarios navegan a un repositorio cuyo nombre iniciaba con "repositories.", se les redirigió a la pestaña de "Repositorios" del propietario en vez de llegar a la página de resumen de éste. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Las etiquetas en la línea de tiempo del tablero no tienen suficiente contraste. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Futura obsoletización de GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 se obsoletizará desde el 12 de noviembre de 2020** Esto significa que no se harán lanzamientos de parches, aún para los problemas de seguirdad críticos, después de esta fecha. [actualiza a la versión más nueva de GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) tan pronto como te sea posible.' + - + heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps + notes: + - 'A partir de la versión 2.21.0 de GitHub Enterprise Server, dos webhooks relacionados con GitHub Apps tradicionales se obsoletizaron y se eliminarán en la versión 2.25.0 de dicho producto. Los eventos obsoletizados de `integration_installation` y `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Hay más información disponible en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Obsoletización de la terminal tradicional para las GitHub Apps + notes: + - 'A partir de la versión 2.21.0 de GitHub Enterprise Server, se obsoletizará la terminal tradicional de las GitHub Apps para crear tokens de acceso ainstalaciones y se eliminará en la versión 2.25.0 de dicho producto. Hay más información en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Obsoletización de la API de aplicaciones OAuth + notes: + - GitHub ya no es compatible con las terminales de las aplicaciones OAuth que contengan `access_token` como parámetro de ruta. Incluimos terminales nuevas que te permiten administrar los tokens de forma segura para las Apps de OAuth al migrar `access_token` hacia el cuerpo de la solicitud. Aunque se obsoletizaron, aún se puede acceder a las terminales en esta versión. Pretendemos eliminar estas terminales para la versión 3.4 de GitHub Enterprise Server. Para obtener más información, consulta la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - El menú desplegable de formato de ID de nombre en la consola de administración se restablece a "no especificado" después de configurar la instancia en "persistente". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - La página de configuración del repositorio para los sitios de GitHub Pages de un usuario u organización falla con un "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183, {% endcomment %} + - Los usuarios podrían experimentar un rendimiento más lento de recuperación y de Git clone en una instancia con replicas de disponibilidad alta debido a que las lecturas se reenviaron a un nodo diferente. {% comment %} https://github.com/github/spokesd/issues/746, {% endcomment %} + - 'El [crear una GitHub App desde un manifiesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falla. Para dar una solución alterna a este problema, los usuarios pueden seguir las instrucciones del manual para [crear una GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' + - Los nombres de usuario de GitHub podrían cambiar sin querer cuando se utiliza una autenticación con SAML si el nombre de usuario de GitHub no empata con el valor del atributo mapeado en el campo `username en la consola de administración. (actualizado 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - En una instancia 2.22.0 recién configurada o después de actualizar 2.22.0, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/1.yml b/translations/es-ES/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000000..d1774d993d0a1 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'Las solicitudes de una integración de una GitHub App para actualizar un token de acceso de OAuth se aceptarán si se envían con la ID de cliente y secreto de cliente de OAuth válidos que se utilizaron para crear el token de actualización. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'El usuario cuyo nombre de usuario del directorio de LDAP se estandarice a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Hacer una actualización utilizando un hotpatch podría ocasionar un fallo con un error de tipo: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + El guardar las configuraciones a través de la [consola de administración](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) añadirá una línea nueva en los archivos de la [llave y certificado TLS/SSL](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls), lo cual activó la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + La gráfica de rendimiento del servidor de MS SQL mostró las estadísticas de la instancia primaria aún cuando se seleccionó la réplica. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` saldrá silenciosamente sin ejecutar las verificaciones de almacenamiento si no se habilitaron las acciones. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + La mejora podría fallar si los trabajadores que se volvieron a poner en cola (resqued) invalidan la configuración que se está utilizando. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Algunos servicios que se ejecutan en los contenedores no estaban enviando bitácoras al diario. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + La página de configuración de seguridad para la cuenta empresarial mostró un enlace para "Visualizar las configuraciones actuales de tus organizaciones" para la configuración de "autenticación bifactorial" cuando el modo de autenticación no es compatible con la autenticación bifactorial incluida. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + Los tokens de actualización de OAuth se eliminaron prematuramente. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Las tareas de búsuqeda y reparación generaron excepciones durante la fase de migración de la configuración. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + En la página de configuración para las GitHub Apps, las "Características Beta" no se podían visualizar en algunas circunstancias. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Los usuarios experimentaron un rendimiento más lento de recuperación y de Git clone en una instancia con replicas de disponibilidad alta debido a que las lecturas se reenviaron a un nodo diferente. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + La página de configuración del repositorio para los sitios de GitHub Pages de un usuario u organización fallaron con un "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Las operaciones de mantenimiento de red del repositorio podrían haberse estancado en un estado de `running`. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + El hecho de que un repositorio se borrara inmediatamente después de cargar un resultado de escaneo de código pudo haber causado un estancamiento en el procesamiento de los resultados de dicho escaneo de código en todos los repositorios. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + Cuando se emitió una cantidad grande de resultados del escaneo de código al mismo tiempo, el procesamiento de lotes pudo haber agotado el tiempo, lo cual resultó en el estancamiento del procesamiento de los resultados del escaneo de código. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + El [Crear una GitHub App desde un manifiesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falló. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + Los nombres de usuario de GitHub se cambiaron sin querer cuando se utilizó la autentificación con SAML, cuando el nombre de usuario de GitHub no empató con el valor del atributo mapeado en el campo de `username` en la Consola de Administración. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} + changes: + - Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} + known_issues: + - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Las actualizaciones de configuración fallan cuando se restablecen los datos en una instancia que tiene habilitadas las GitHub Actions si la fuente de respaldo original no cuenta con la característica habilitada. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - Las GitHub Actions pueden fallar en su inicio exitoso si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualiza a la 2.22.1. (actualizado en 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - En una instancia 2.22.1 recién configurada o después de actualizar 2.22.1, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/2.yml b/translations/es-ES/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000000..70b44e7697980 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + Si la configuración de la cuenta de almacenamiento falló su validación cuando se configuró GitHub Actions, se requirió ejecutar `ghe-actions-teardown` antes de hacer un intento nuevo. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + Una configuración de proxy personalizado pudo haber afectado de forma adversa al ambiente de GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + En un cambio de dirección de eth0, Nomad y Consul podrían dejar de responder. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + Cuando se utilizan certificados auto-firmados, GHES podría tener excepciones de validación de SSL al configurar las GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + El utilizar una GitHub Action desde un nombre de rama con un caracter `+` o `/` resultó en un error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + En ciertas solicitudes mayores a 100MB, el buffer de Kafka pudo estar sobreasignado. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Las GitHub Actions pueden fallar en su inicio exitoso si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualiza a la 2.22.2. (actualizado en 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - En una instancia 2.22.2 recién configurada o después de actualizar 2.22.2, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/3.yml b/translations/es-ES/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000000..7bdd267c28c02 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (Dos) en el servicio del puente SVN. (actualizado 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} + bugs: + - Las GitHub Actions pueden fallar para iniciar exitosamente si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualizó a la 2.22.1 o 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Los archivos de configuración para las GitHub Actions no se copiaron a la replica cuando se configuraron las réplicas de disponibilidad alta, lo cual produjo errores durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - En una instancia 2.22.1 recién configurada o después de actualizar 2.22.1, no se pudo actualizar la fuente de actividad en el tablero de una organización. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - El editar las plantillas de las propuestas con los nombres de archivo que contienen caracteres que no son de ASCII fallará con un mensaje de "500 Internal Server Error".{% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - Un método de recolección métrica para los jobs en segundo plano incrementó el uso del CPU. (actualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP de origen real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/4.yml b/translations/es-ES/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000000..f49be20cc4e40 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - Después de actualizar a GHES con un hotpatch, los comandos `ghe-actions-precheck` y `ghe-packages-precheck` fallaron con el error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Las bitácoras de auditoría podrían atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/5.yml b/translations/es-ES/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000000..cdde22a5ae09d --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'ghe-diagnostics no estaba capturando el proceso de mejora de Elasticsearch. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'El habilitar las GitHub Actions en una configuración de disponibilidad alta mejorada causó errores en la replicación. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Los usuarios que se conectaron a una réplica activa obtuvieron un error al conectarse al websocket de las actualizaciones en vivo. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Cuando se inicia sesión después de intentar visitar una página específica, se enviaba a las personas a la página de inicio en vez de a su destino previsto. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'Para las instancias de GHES que utilizan una autenticación integrada con un proveedor de identidad de SAML interno, los usuarios sin una dirección de correo electrónico asociada no pudieron crear una confirmación desde la interfase web. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/6.yml b/translations/es-ES/data/release-notes/2-22/6.yml new file mode 100644 index 0000000000000..bef5321efe199 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/6.yml @@ -0,0 +1,18 @@ +--- +date: '2020-12-17' +sections: + security_fixes: + - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + bugs: + - 'Las solicitudes para algunos recursos de archivos como un archivo zip o un archivo raw podrían ingresar en un bucle de redirección. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' + - 'Un límite de tiempo podría prevenir que algunas búsquedas de propuestas y solicitudes de cambios proporcionen resultados de búsqueda completos. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' + - 'Las pestañas personalizadas con caracteres no alfabéticos en pantallas pequeñas no se interpretaron correctamente. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' + - 'Un comportamiento subyacente estaba causando fallas cuando se subía contenido a un repositorio de Git habilitado con LFS. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' + - 'En algunos casos poco frecuentes las propuestas podrían causar un error 500 cuando se accede a ellas a través de la interface web. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' + known_issues: + - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/3-0/0-rc.yml b/translations/es-ES/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..9c3f95d1373de --- /dev/null +++ b/translations/es-ES/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: Registro del paquete de GitHub + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Cambios en la administración + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Cambios de seguridad + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Cambios de desarrollador + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: Cambios a la API + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Obsoletización de la terminal tradicional para las GitHub Apps + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Obsoletización de la API de aplicaciones OAuth + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/reusables/accounts/create-account.md b/translations/es-ES/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000000..8763ddf88474a --- /dev/null +++ b/translations/es-ES/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. Ve a la página de {% data variables.product.product_name %}[Fijación de precios]({% data variables.product.pricing_url %}). +2. Lee la información acerca de los diferentes productos y suscripciones que ofrece {% data variables.product.product_name %}, después haz clic en el botón actualizar debajo de la suscripción que deseas elegir. diff --git a/translations/es-ES/data/reusables/actions/about-artifact-log-retention.md b/translations/es-ES/data/reusables/actions/about-artifact-log-retention.md new file mode 100644 index 0000000000000..46c975a7a562a --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-artifact-log-retention.md @@ -0,0 +1,6 @@ +Predeterminadamente, los artefactos y archivos de bitácora que generan los flujos de trabajo se retienen por 90 días antes de que se borren automáticamente. Puedes ajustar el periodo de retención dependiendo del tipo de repositorio: + +- Para los repositorios públicos: puedes cambiar este periodo de retención a cualquier cantidad entre 1 o 90 días. +- Para los repositorios privados, internos y de {% data variables.product.prodname_enterprise %}: puedes cambiar este periodo de retención a cualquier cantidad entre 1 y 400 días. + +Cuando personalizas el periodo de retención, esto aplicará solamente a los artefactos y archivos de bitácora nuevos, y no aplicará retroactivamente a los objetos existentes. Para los repositorios y organizaciones administrados, el periodo de retención máximo no puede exceder el límite que configuró la organización o empresa administradora. diff --git a/translations/es-ES/data/reusables/actions/about-artifacts.md b/translations/es-ES/data/reusables/actions/about-artifacts.md new file mode 100644 index 0000000000000..2a5cc3fd3baf5 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-artifacts.md @@ -0,0 +1 @@ +Los artefactos te habilitan para compartir datos entre jobs en un flujo de trabajo y para almacenar datos una vez que este flujo se complete. diff --git a/translations/es-ES/data/reusables/actions/about-secrets.md b/translations/es-ES/data/reusables/actions/about-secrets.md new file mode 100644 index 0000000000000..4a30c00f5c4aa --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-secrets.md @@ -0,0 +1 @@ +Los secretos cifrados te permiten almacenar información sensible, tal como los tokens de acceso, en tu repositorio u organización. diff --git a/translations/es-ES/data/reusables/actions/about-self-hosted-runners.md b/translations/es-ES/data/reusables/actions/about-self-hosted-runners.md new file mode 100644 index 0000000000000..7ff777bdea022 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-self-hosted-runners.md @@ -0,0 +1 @@ +Los ejecutores auto-hospedados te permiten hospedr tus propios ejecutores y personalizar el ambiente que se utiliza para ejecutar jobs en tus flujos de trabajo de {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/data/reusables/actions/about-workflow-jobs.md b/translations/es-ES/data/reusables/actions/about-workflow-jobs.md new file mode 100644 index 0000000000000..99e9879158ee1 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-workflow-jobs.md @@ -0,0 +1 @@ +Un job de flujode trabajo es un cconjunto de pasos que se ejecutan en el mismo ejecutor. diff --git a/translations/es-ES/data/reusables/actions/about-workflow-runs.md b/translations/es-ES/data/reusables/actions/about-workflow-runs.md new file mode 100644 index 0000000000000..0f0c72e1a623f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-workflow-runs.md @@ -0,0 +1 @@ +Una ejecución de flujode trabajo es una instancia en tu flujo de trabajo que se ejecuta cuando ocurre el evento pre-configurado. diff --git a/translations/es-ES/data/reusables/actions/about-workflows.md b/translations/es-ES/data/reusables/actions/about-workflows.md new file mode 100644 index 0000000000000..5e50f9b1630c0 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-workflows.md @@ -0,0 +1 @@ +Los flujos de trabajo automatizan el ciclo de vida de tu desarrollo de software con una amplia gama de herramientas y servicios. diff --git a/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md b/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md new file mode 100644 index 0000000000000..86cf7e34ff136 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md @@ -0,0 +1 @@ +Las {% data variables.product.prodname_github_app %}s deben contar con el permiso de `actions` para utilizar esta API. diff --git a/translations/es-ES/data/reusables/actions/actions-authentication.md b/translations/es-ES/data/reusables/actions/actions-authentication.md new file mode 100644 index 0000000000000..aa201652afae9 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/actions-authentication.md @@ -0,0 +1 @@ +Esta API está disponible para los usuarios autenticados, las {% data variables.product.prodname_oauth_app %}s, y las {% data variables.product.prodname_github_app %}s. Los tokens de acceso requieren el [alcance `repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para los repositorios privados y el [alcance `public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para aquellos públicos. diff --git a/translations/es-ES/data/reusables/actions/actions-not-verified.md b/translations/es-ES/data/reusables/actions/actions-not-verified.md new file mode 100644 index 0000000000000..0adc5aea11063 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/actions-not-verified.md @@ -0,0 +1 @@ +Cualquiera puede publicar una acción en {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifica algunas organizaciones aliadas y estas se muestran como creadores verificados. diff --git a/translations/es-ES/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/es-ES/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000000..58e5fee7b09b0 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +Puedes configurar un límite de gastos específico o, en algunas cuentas, permitir gastos ilimitados. El límite de gastos aplica a tus excedentes combinados para {% data variables.product.prodname_registry %} y {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/data/reusables/actions/actions-use-policy-settings.md b/translations/es-ES/data/reusables/actions/actions-use-policy-settings.md new file mode 100644 index 0000000000000..7016aa4912e06 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/actions-use-policy-settings.md @@ -0,0 +1,3 @@ +If you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions. Para obtener más información, consulta la sección "[Permitir que se ejecuten acciones específicas](#allowing-specific-actions-to-run)". + +Cuando permites únicamente acciones locales, las políticas bloquean todo el acceso a las acciones que haya creado {% data variables.product.prodname_dotcom %}. Por ejemplo, no se podría acceder a [`actions/checkout`](https://github.com/actions/checkout). \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md b/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md new file mode 100644 index 0000000000000..88028781bf659 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md @@ -0,0 +1,19 @@ +When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: + +- **Permitir acciones que crea {% data variables.product.prodname_dotcom %}:** Puedes permitir que los flujos de trabajo utilicen todas las acciones que haya creado {% data variables.product.prodname_dotcom %}. Las acciones que crea {% data variables.product.prodname_dotcom %} se ubican en las organizaciones de `actions` y de `github`. Para obtener más información, consulta las organizaciones [`actions`](https://github.com/actions) y [`github`](https://github.com/github). +- **Permitir las acciones de Marketplace que tengan creadores verificados:** Puedes permitir que los flujos de trabajo utilicen todas las acciones de {% data variables.product.prodname_marketplace %} que tengan creadores verificados. Cuando GitHub haya verificado al creador de la acción como una organización asociada, se mostrará la insignia de {% octicon "verified" aria-label="The verified badge" %} junto a la acción en {% data variables.product.prodname_marketplace %}. +- **Permitir acciones especificadas:** Puedes restringir los flujos de trabajo para que utilicen las acciones que se encuentren en organizciones y repositorios específicos. + + Para restringir el acceso a las etiquetas específicas o a los SHA de confirmación de una acción, puedes utilizar la misma sintaxis de `/@` en el flujo de trabajo para seleccionar la acción. Por ejemplo, `actions/javascript-action@v1.0.1` para seleccionar una etiqueta o `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` para seleccionar un SHA. Para obtener más información, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)". + + Puedes utilizar el caracter de comodín `*` para empatar los patrones. Por ejemplo, para permitir todas las acciones en organizaciones que comiencen con `space-org`, puedes especificar `space-org*/*`. Para agregar todas las acciones en los repositorios que comiencen con octocat, puedes utilizar `*/octocat*@*`. Para obtener más información sobre cómo utilizar el comodín `*`, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)". + + {% if currentVersion == "free-pro-team@latest" %} + {% note %} + + **Nota:** La opción **Permitir las acciones especificadas** solo se encuentra disponible para los repositorios públicos con los planes de {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, o {% data variables.product.prodname_team %}. + + {% endnote %} + {% endif %} + +Este procedimiento ilustra cómo agregar acciones específicas a la lista de acciones permitidas. diff --git a/translations/es-ES/data/reusables/actions/enterprise-actions-permissions.md b/translations/es-ES/data/reusables/actions/enterprise-actions-permissions.md new file mode 100644 index 0000000000000..44c9fd6175bfe --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-actions-permissions.md @@ -0,0 +1,12 @@ +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Habilita, inhabilita o limita las acciones para esta cuenta empresarial](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/es-ES/data/reusables/actions/enterprise-beta.md b/translations/es-ES/data/reusables/actions/enterprise-beta.md new file mode 100644 index 0000000000000..a51f239c30070 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-beta.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Nota:** El soporte para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 es un beta público limitado. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md b/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..b847b40dd54eb --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **Nota:**{% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-enable-checkbox.md b/translations/es-ES/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/enterprise-github-hosted-runners.md b/translations/es-ES/data/reusables/actions/enterprise-github-hosted-runners.md new file mode 100644 index 0000000000000..b2cb753922f68 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-github-hosted-runners.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Nota:** Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} no son compatibles con {% data variables.product.prodname_ghe_server %} actualmente. Puedes encontrar más información sobre el soporte que se tiene planeado en el futuro en el [{% data variables.product.prodname_roadmap %}](https://github.com/github/roadmap/issues/72). + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md b/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/es-ES/data/reusables/actions/enterprise-http-proxy.md b/translations/es-ES/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/es-ES/data/reusables/actions/enterprise-limit-actions-use.md b/translations/es-ES/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..9b860c7d3209a --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". diff --git a/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md new file mode 100644 index 0000000000000..bc30f491ca42d --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion %} + +{% note %} + +**Nota:** Las {% data variables.product.prodname_actions %} en {% data variables.product.product_location %} podrían tener acceso limitado a las acciones en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md b/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md new file mode 100644 index 0000000000000..aa11da1ebe2cd --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md @@ -0,0 +1 @@ +Las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} se diseñan para funcionar en ambientes sin acceso a internet. Predeterminadamente, los flujos de trabajo no utilizan acciones de {% data variables.product.prodname_dotcom_the_website %} y [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). diff --git a/translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..5c7e8f0ddf996 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### Pasos siguientes + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/es-ES/data/reusables/actions/enterprise-s3-permission.md b/translations/es-ES/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/es-ES/data/reusables/actions/enterprise-s3-support-warning.md b/translations/es-ES/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/enterprise-self-signed-cert.md b/translations/es-ES/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/es-ES/data/reusables/actions/enterprise-setup-prereq.md b/translations/es-ES/data/reusables/actions/enterprise-setup-prereq.md new file mode 100644 index 0000000000000..e063d552e9a00 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-setup-prereq.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} + +#### Utilizar ejecutores auto-hospedados en {% data variables.product.prodname_ghe_server %} + +Cuando utilices acciones de configuración, (tales como `actions/setup-LANGUAGE`) en {% data variables.product.prodname_ghe_server %} con ejecutores auto-hospedados, tal vez necesites configurar el caché de las herramientas en los ejecutores que no tienen acceso a internet. Para obtener más información, consulta la sección "[ Configurar el caché de herramientas en ejecutores auto-hospedados sin acceso a internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". + +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/es-ES/data/reusables/actions/environments-beta.md b/translations/es-ES/data/reusables/actions/environments-beta.md new file mode 100644 index 0000000000000..c970ff931902f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/environments-beta.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +{% note %} + +**Nota:** Los ambientes, reglas de protección de ambiente y secretos de ambiente se encuentran actualmente en beta y están sujetos a cambios. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/forked-secrets.md b/translations/es-ES/data/reusables/actions/forked-secrets.md new file mode 100644 index 0000000000000..ff5af683b8361 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/forked-secrets.md @@ -0,0 +1 @@ +Con la excepción de `GITHUB_TOKEN`, los secretos no se pasan al ejecutador cuando un flujo de trabajo se dispara desde un repositorio bifurcado. diff --git a/translations/es-ES/data/reusables/actions/registry-credentials.md b/translations/es-ES/data/reusables/actions/registry-credentials.md new file mode 100644 index 0000000000000..af6044295a549 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/registry-credentials.md @@ -0,0 +1 @@ +Si el registro del contenedor de la imagen requiere autenticación para extraerla, puedes utilizar `credentials` para configurar un `map` del `username` y `password`. Las credenciales son los mismos valores que proporcionarías al comando de [`docker login`](https://docs.docker.com/engine/reference/commandline/login/). diff --git a/translations/es-ES/data/reusables/actions/scheduled-workflows-disabled.md b/translations/es-ES/data/reusables/actions/scheduled-workflows-disabled.md new file mode 100644 index 0000000000000..4d06b44c1bb95 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/scheduled-workflows-disabled.md @@ -0,0 +1 @@ +Para prevenir las ejecuciones de flujo de trabajo innecesarias, los flujos de trabajo programados pueden inhabilitarse automáticamente. Cuando se bifurca un repositorio público, los flujos de trabajo programados se inhabilitan predeterminadamente. En un repositorio público, los flujos de trabajo programados se inhabilitan automáticamente cuando no ha habido actividad en el repositorio por 60 días. diff --git a/translations/es-ES/data/reusables/actions/visualization-beta.md b/translations/es-ES/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000000..47f74b44310a3 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Nota:** La gráfica de visualización del flujo de trabajo para {% data variables.product.prodname_actions %} se encuentra actualmente en beta y está sujeta a cambios. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/workflow-template-overview.md b/translations/es-ES/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..d6fe66b19e305 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. Por ejemplo, si tu repositorio contiene un código Node.js, verás sugerencias para los proyectos de Node.js. Puedes usar plantillas de flujo de trabajo como lugar de inicio para crear tu flujo de trabajo personalizado o usarlos tal como están. + +Puedes buscar en la lista completa de plantillas de flujo de trabajo en el repositorio {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %} el repositorio `actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}. diff --git a/translations/es-ES/data/reusables/advanced-security/more-info-ghas.md b/translations/es-ES/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..f6d188cec58c2 --- /dev/null +++ b/translations/es-ES/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)". +{% endif %} diff --git a/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/apps/accept_new_permissions_steps.md b/translations/es-ES/data/reusables/apps/accept_new_permissions_steps.md new file mode 100644 index 0000000000000..1d4f1070d96f3 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/accept_new_permissions_steps.md @@ -0,0 +1,2 @@ +1. Da clic en **Guardar cambios** al final de la página. +1. Si instalaste la app en tu cuenta, revisa tu correo electrónico y sigue el enlace para aceptar los permisos nuevos. Cada que cambias los permisos o los webhooks de tu app, los usuarios que la hayan instalado (incluyéndote a ti mismo) necesitarán aceptar los permisos nuevos antes de que los cambios surtan efecto. También puedes aceptar los permisos nuevos si navegas a tu [página de instalaciones](https://github.com/settings/installations) y das clic en "Configurar" junto a tu app. Verás un letrero en la parte superior de la página que te informará que la app está solicitando permisos diferentes. Da clic en "Detalles" y después en "Aceptar permisos nuevos". diff --git a/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md b/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md new file mode 100644 index 0000000000000..9f38778e66f95 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md @@ -0,0 +1 @@ +Las {% data variables.product.prodname_github_app %} hacen solicitudes de servidor a servidor para utilizar el límite de tasa mínimo de la instalación, que es de 5,000 solicitudes por hora. Las instalaciones de organización con más de 20 usuarios reciben 50 solicitudes adicionales por hora para cada usuario. Las instalaciones que tienen más de 20 repositorios reciben otras 50 solicitudes adicionales por hora para cada repositorio. El límite de tasa máximo para una instalación es de 12,500 solicitudes por hora. diff --git a/translations/es-ES/data/reusables/apps/app-ruby-guides.md b/translations/es-ES/data/reusables/apps/app-ruby-guides.md new file mode 100644 index 0000000000000..b58509d39db8c --- /dev/null +++ b/translations/es-ES/data/reusables/apps/app-ruby-guides.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Esta guía muestra el proceso de desarrollo de las apps utilizando el lenguaje de programación Ruby. Sin embargo, hay muchos [sabores de Octokit](/rest/overview/libraries). Si prefieres JavaScript, puedes utilizar al [Probot](https://probot.github.io/) y a [Node.js](https://octokit.github.io/rest.js/) para desarrollar las GitHub Apps. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/apps/app_manager_role.md b/translations/es-ES/data/reusables/apps/app_manager_role.md new file mode 100644 index 0000000000000..28b4f1eabced5 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/app_manager_role.md @@ -0,0 +1 @@ +Predeterminadamente, solo los propietarios de la organización pueden administrar los ajustes de las GitHub Apps en una organización. Para agregar usuarios adicionales para que administren las GitHub Apps en una organización, un propietario puede otorgarles permisos de administrador sobe ellas. Consula la sección "[Administradores de GitHub Apps](/articles/permission-levels-for-an-organization/#github-app-managers)" para aprender cómo agregar y eliminar administradores de GitHub Apps en tu organización. diff --git a/translations/es-ES/data/reusables/apps/beta_feature_activation.md b/translations/es-ES/data/reusables/apps/beta_feature_activation.md new file mode 100644 index 0000000000000..6a3233295d8c6 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/beta_feature_activation.md @@ -0,0 +1,2 @@ +4. En la barra lateral izquierda, da clic en **Características del Beta**. ![Sección de las GitHub Apps o Apps de OAuth](/assets/images/github-apps/beta-features-option.png) +5. Junto a la característica beta que quieres habilitar para tu app, da clic en **Unirse**. ![Botón de unirse para habilitar la característica beta](/assets/images/github-apps/enable-beta-features.png) diff --git a/translations/es-ES/data/reusables/apps/checks-availability.md b/translations/es-ES/data/reusables/apps/checks-availability.md new file mode 100644 index 0000000000000..ea87a2d38c905 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/checks-availability.md @@ -0,0 +1 @@ +El permiso de escritura para la API de Verificaciones solo está disponible para las Github Apps. Las Apps de OAuth y los usuarios autenticados pueden ver las ejecuciones de verificación y las suites de verificación, pero no pueden crearlas. Si no estás creando una GitHub App, puede que te interese la [API de estados](/rest/reference/repos#statuses). diff --git a/translations/es-ES/data/reusables/apps/deletes_ssh_keys.md b/translations/es-ES/data/reusables/apps/deletes_ssh_keys.md new file mode 100644 index 0000000000000..cedb78e01d2e7 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/deletes_ssh_keys.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia**: Si revocas todos los permisos de una {% data variables.product.prodname_oauth_app %} borrarás cualquier llave SSH que haya generado la aplicación en nombre del usuario, , incluyendo las [llaves de despliegue](/developers/overview/managing-deploy-keys#deploy-keys). + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md new file mode 100644 index 0000000000000..ffdf08b5d6878 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% warning %} + +**Aviso de Obsoletización:** {% data variables.product.prodname_dotcom %} descontinuará la autenticación a la API utilizando parámetros de consulta. La autenticación en la API debe hacerse con la [autenticación básica de HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} El utilizar parámetros de consulta para autenticarse en la API ya no funcionará desde el 5 de mayo de 2021. {% endif %} Para obtener más información, incluyendo los periodos de interrupción programada, consulta la [publicación del blog](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} La autenticación a la API utilizando parámetros de consulta, aunque está disponible, ya no es compatible por motivos de seguridad. En vez de ésto, recomendamos a los integradores que migren su token de acceso, `client_id`, o `client_secret` al encabezado. {% data variables.product.prodname_dotcom %} notificará sobre la eliminación de la autenticación por parámetros de consulta con tiempo suficiente. {% endif %} + +{% endwarning %} +{% endif %} diff --git a/translations/es-ES/data/reusables/apps/deprecating_github_services_ghe.md b/translations/es-ES/data/reusables/apps/deprecating_github_services_ghe.md new file mode 100644 index 0000000000000..6460009e27f71 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/deprecating_github_services_ghe.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} +{% note %} + +**Nota:** El lanzamiento 2.17 de GitHub Enterprise y las versiones superiores ya no permiten que los administradores instalen GitHub Services nuevos, y los servicios existentes dejarán de funcionar en el lanzamiento 2.20 o superior de Github Enterprise. Puedes utilzar la [Guía para reemplazar GitHub Services](/developers/overview/replacing-github-services) para ayudarte a actualizar tus servicios a webhooks. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/apps/deprecating_token_oauth_authorizations.md b/translations/es-ES/data/reusables/apps/deprecating_token_oauth_authorizations.md new file mode 100644 index 0000000000000..51acc808366cb --- /dev/null +++ b/translations/es-ES/data/reusables/apps/deprecating_token_oauth_authorizations.md @@ -0,0 +1,16 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} +{% warning %} + +**Aviso de obsoletización:** El atributo `token` se obsoletizó en algunas respuestas de la API para Autorizaciones de OAuth: +* Listar tus autorizaciones +* Obtener una sola autorización +* Obtener o crear una autorización para una app específica - aún se devuelve el `token` para "crear" +* Obtener o crear una autorización para una app y huella digital específicos - aún se devuelve `token` para "crear" +* Actualizar una autrización existente + +Para reducir el impacto de eliminar el valor de `token`, la API de Autorizaciones de OAuth ahora incluye un atributo de solicitud nuevo (`fingerprint`), tres atributos de respuesta nuevos (`token_last_eight`, `hashed_token`, y `fingerprint`), y la terminal de [Obtener o crear una autorización para una app y huella digital específica](/rest/reference/oauth-authorizations#get-or-create-an-authorization-for-a-specific-app-and-fingerprint). + +Esta fucionalidad se convirtió en predeterminada para todas las solicitudes desde el 20 de abril de 2015. Por favor, consulta la [publicación del blog](https://developer.github.com/changes/2015-04-20-authorizations-api-response-changes-are-now-in-effect/) para obtener toda la información al respecto. + +{% endwarning %} +{% endif %} diff --git a/translations/es-ES/data/reusables/apps/expiring_user_authorization_tokens.md b/translations/es-ES/data/reusables/apps/expiring_user_authorization_tokens.md new file mode 100644 index 0000000000000..f9cb9cc6dd970 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/expiring_user_authorization_tokens.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +Para mantener más seguros los tokens de acceso de usuario a servidor, puedes utilizar tokens de acceso que caducarán después de 8 horas, y un token de actualización que se puede intercambiar por un token de acceso nuevo. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)". +{% endif %} diff --git a/translations/es-ES/data/reusables/apps/general-apps-restrictions.md b/translations/es-ES/data/reusables/apps/general-apps-restrictions.md new file mode 100644 index 0000000000000..b6e75373bbbf4 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/general-apps-restrictions.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Si estás utilizando tu app con GitHub Actions y quieres modificar los archivos de flujo de trabajo, debes autenticarte en nombre del usuario con un token de OAuth que incluya el alcance `workflow`. El usuario debe tener permisos de administrador o de escritura en el repositorio que contiene el archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Entender los alcances para las apps de OAuth](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)".{% endif %} diff --git a/translations/es-ES/data/reusables/apps/maximum-github-apps-allowed.md b/translations/es-ES/data/reusables/apps/maximum-github-apps-allowed.md new file mode 100644 index 0000000000000..176200e349f3c --- /dev/null +++ b/translations/es-ES/data/reusables/apps/maximum-github-apps-allowed.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Un usuario u organización puede ser propietario de hasta 100 GitHub Apps..{% endif %} diff --git a/translations/es-ES/data/reusables/apps/maximum-oauth-apps-allowed.md b/translations/es-ES/data/reusables/apps/maximum-oauth-apps-allowed.md new file mode 100644 index 0000000000000..943f68bc93b6e --- /dev/null +++ b/translations/es-ES/data/reusables/apps/maximum-oauth-apps-allowed.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Un usuario u organización puede ser propietario de hasta 100 apps de OAuth.{% endif %} diff --git a/translations/es-ES/data/reusables/apps/metadata-permissions.md b/translations/es-ES/data/reusables/apps/metadata-permissions.md new file mode 100644 index 0000000000000..ee1c903e51259 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/metadata-permissions.md @@ -0,0 +1 @@ +Si configuras el permiso para metadatos como `No access` y seleccionas un permiso que requiere acceso al repositorio, GitHub anulará tu selección y configurará el permiso de metadatos como `Read-only` nuevamente. Para configurar el permiso de metadatos como `No access`, primero debes configurar todos los permisos que requieren acceso al repositorio como `No access`. diff --git a/translations/es-ES/data/reusables/apps/oauth-apps-restrictions.md b/translations/es-ES/data/reusables/apps/oauth-apps-restrictions.md new file mode 100644 index 0000000000000..7fdd863e2df04 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/oauth-apps-restrictions.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Si estás utilizando tu App de OAuth con GitHub Actions y quieres modificar tus archivos de flujo de trabajo, tu token de OAuth debe tener el alcance `workflow` y el usuario debe tener permisos de escritura o de lectura para el repositorio que contiene dichos archivos de flujo de trabajo. Para obtener más información, consulta la sección "[Entender los alcances para las apps de OAuth](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)".{% endif %} diff --git a/translations/es-ES/data/reusables/apps/sinatra_restart_instructions.md b/translations/es-ES/data/reusables/apps/sinatra_restart_instructions.md new file mode 100644 index 0000000000000..fc95fdf350b56 --- /dev/null +++ b/translations/es-ES/data/reusables/apps/sinatra_restart_instructions.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Necesitarás reiniciar el servidor de Sinatra antes de que puedas probar los cambios. Introduce `Ctrl-C` para parar el servidor y después ejecuta `ruby template_server.rb` nuevamente. Si no quieres hacer esto cada que cambias el código de tu app, puedes buscar en [reloading](http://sinatrarb.com/faq.html#reloading). + +{% endnote %} diff --git a/translations/es-ES/data/reusables/apps/state_description.md b/translations/es-ES/data/reusables/apps/state_description.md new file mode 100644 index 0000000000000..efa6f70e8993b --- /dev/null +++ b/translations/es-ES/data/reusables/apps/state_description.md @@ -0,0 +1 @@ +Una secuencia aleatoria indescifrable. Se utiliza para protegerte contra los ataques de falsificación de solicitudes entre sitios. diff --git a/translations/es-ES/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md b/translations/es-ES/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md new file mode 100644 index 0000000000000..c9b866580818e --- /dev/null +++ b/translations/es-ES/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** la API de Verificaciones únicamente busca las cargas en el repositorio donde se creó el conjunto o ejecución de verificaciones. No se detectan aquellas cargas en ramas de repositorios bifurcados y estas devuelven un arreglo vacío de `pull_requests` y un valor `null` para la `head_branch`. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-api-info.md b/translations/es-ES/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000000..0256a3e332c37 --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* El acceso a los parámetros de tu organización o repositorio +* Los cambios en los permisos +* Los usuarios agregados o eliminados en una organización, repositorio o equipo +* Los usuarios que se están promoviendo a administradores +* Cambios a los permisos de una {% data variables.product.prodname_github_app %} diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/es-ES/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000000..615c199eccc31 --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +La bitácora de auditoría retiene los eventos de git por 7 días. Esto es más corto que otros eventos de la bitácora de auditoría, los cuales se pueden retener por 90 días. diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-search.md b/translations/es-ES/data/reusables/audit_log/audit-log-search.md new file mode 100644 index 0000000000000..18ce188be788c --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/audit-log-search.md @@ -0,0 +1,41 @@ +El registro lista la siguiente información sobre cada acción: + +* En qué repositorio se realizó una acción +* El usuario que realizó la acción +* La acción que se realizó +* En qué país se realizó la acción +* La fecha y hora en que se produjo la acción + +Nota que no puedes buscar entradas utilizando texto. Sin embargo, puedes construir consultas de búsqueda utilizando una variedad de filtros. Muchos operadores que se utilizan cuando se busca el registro por queries, tales como `-`, `>`, o `<`, empatan con el mismo formato que si se busca con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". + +#### Búsqueda basada en la operación + +Utiliza el calificador `operation` para limitar las acciones en tipos específicos de operaciones. Por ejemplo: + + * `operation:access` encuentra todos los eventos en donde se accedió a un recurso. + * `operation:authentication` encuentra todos los eventos en donde se realizó un evento de autenticación. + * `operation:create` encuentra todos los eventos en donde se creó un recurso. + * `operation:modify` encuentra todos los eventos en donde se modificó un recurso existente. + * `operation:remove` encuentra todos los eventos en donde se eliminó un recurso existente. + * `operation:restore` encuentra todos los eventos en donde se restauró un recurso existente. + * `operation:transfer` encuentra todos los eventos en donde se transfirió un recurso existente. + +#### Búsqueda basada en el repositorio + +Utiliza el calificador `repo` para limitar las acciones a un repositorio específico. Por ejemplo: + + * `repo:my-org/our-repo` encuentra todos los eventos que ocurrieron para el repositorio `our-repo` en la organización `my-org`. + * `repo:my-org/our-repo repo:my-org/another-repo` encuentra todos los eventos que ocurrieron tanto para los repositorios `our-repo` como `another-repo` en la organización `my-org`. + * `-repo:my-org/not-this-repo` excluye todos los eventos que ocurrieron para el repositorio `not-this-repo` en la organización `my-org`. + +Nota que debes incluir el nombre de cuenta dentro del calificador `repo`; no funcionará si buscas únicamente `repo:our-repo`. + +#### Búsqueda basada en el usuario + +El calificador `actor` puede incluir eventos que se basen en quién realizó la acción. Por ejemplo: + + * `actor:octocat` encuentra todos los eventos realizados por `octocat`. + * `actor:octocat actor:hubot` encuentra todos los eventos realizados tanto por `octocat` como por `hubot`. + * `-actor:hubot` excluye todos los eventos realizados por `hubot`. + +Ten en cuenta que solo puedes utilizar un nombre de usuario {% data variables.product.product_name %}, no el nombre real de una persona. diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md new file mode 100644 index 0000000000000..7e2f6514896e2 --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md @@ -0,0 +1 @@ +1. En la barra lateral de Parámetros, haz clic en **Audit Log (Registro de auditoría)**. ![Parámetros de registro de auditoría de org en barra lateral](/assets/images/help/organizations/org-settings-audit-log.png) diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md new file mode 100644 index 0000000000000..0768fe1a42938 --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, haz clic en **Audit Log (Registro de auditoría)**. ![Pestaña de registro de auditoría](/assets/images/enterprise/site-admin-settings/audit-log-tab.png) diff --git a/translations/es-ES/data/reusables/audit_log/export-log.md b/translations/es-ES/data/reusables/audit_log/export-log.md new file mode 100644 index 0000000000000..df8dac28ce2aa --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/export-log.md @@ -0,0 +1,7 @@ +Puedes exportar el registro como datos JSON o como un archivo con valores separados por comas (V). + +![Botón de exportar](/assets/images/help/organizations/org-audit-log-export.png) + +Para filtrar los resultados en tu exportación, busca utilizando uno o más de los calificadores antes de recurrir al menú desplegable **Export**. + +{% data reusables.audit_log.keys-and-example-values %} diff --git a/translations/es-ES/data/reusables/audit_log/exported-log-keys-and-values.md b/translations/es-ES/data/reusables/audit_log/exported-log-keys-and-values.md new file mode 100644 index 0000000000000..3629909fee42c --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/exported-log-keys-and-values.md @@ -0,0 +1,16 @@ +Después de que exportes el registro como JSON o CSV, verás las siguientes claves y valores en el archivo resultante. + +| Clave | Valor de ejemplo | +| ------------------------ | ------------------------------------------------------------------------------------- | +| `Acción` | team.create | +| `actor (actor)` | octocat | +| `user` | codertocat | +| `org` | octo-org | +| `repo` | octo-org/documentation | +| `created_at (creado en)` | 1429548104000 (Los registros horarios muestran la hora desde Epoch con milisegundos). | +| `data.hook_id` | 245 | +| `data.events` | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] | +| `data.events_were` | ["push", "pull_request", "issues"] | +| `data.target_login` | octocat | +| `data.old_user` | hubot | +| `data.team` | octo-org/engineering | diff --git a/translations/es-ES/data/reusables/audit_log/keys-and-example-values.md b/translations/es-ES/data/reusables/audit_log/keys-and-example-values.md new file mode 100644 index 0000000000000..2e3fa019e3e4d --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/keys-and-example-values.md @@ -0,0 +1,8 @@ +| Qualifier | Valor de ejemplo | +| --------------- | ---------------------- | +| `Acción` | team.create | +| `actor (actor)` | octocat | +| `user` | codertocat | +| `org` | octo-org | +| `repo` | octo-org/documentation | +| `created` | 2019-06-01 | diff --git a/translations/es-ES/data/reusables/audit_log/octicon_icon.md b/translations/es-ES/data/reusables/audit_log/octicon_icon.md new file mode 100644 index 0000000000000..6193126263f62 --- /dev/null +++ b/translations/es-ES/data/reusables/audit_log/octicon_icon.md @@ -0,0 +1 @@ +1. En la esquina superior izquierda de cualquier página, haz clic en . ![Icono de Octocat](/assets/images/enterprise/navigation/octocat-icon.png) diff --git a/translations/es-ES/data/reusables/branches/change-default-branch.md b/translations/es-ES/data/reusables/branches/change-default-branch.md new file mode 100644 index 0000000000000..d7654f964161e --- /dev/null +++ b/translations/es-ES/data/reusables/branches/change-default-branch.md @@ -0,0 +1 @@ +Puedes cambiar la rama predeterminada de un repositorio existente. Para obtener màs informaciòn, consulta la secciòn "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)". diff --git a/translations/es-ES/data/reusables/branches/default-branch-automatically-base-branch.md b/translations/es-ES/data/reusables/branches/default-branch-automatically-base-branch.md new file mode 100644 index 0000000000000..05dc95b6f731e --- /dev/null +++ b/translations/es-ES/data/reusables/branches/default-branch-automatically-base-branch.md @@ -0,0 +1,2 @@ +A menos de que especifiques una rama diferente, la rama predeterminada en un repositorio será la rama base para las solicitudes de cambio nuevas y para las confirmaciones de código. + diff --git a/translations/es-ES/data/reusables/branches/new-repo-default-branch.md b/translations/es-ES/data/reusables/branches/new-repo-default-branch.md new file mode 100644 index 0000000000000..c3b365696ff59 --- /dev/null +++ b/translations/es-ES/data/reusables/branches/new-repo-default-branch.md @@ -0,0 +1,2 @@ +Cuando creas un repositorio con contenido en {% data variables.product.product_location %}, {% data variables.product.product_name %} crea el repositorio con una sola rama. Esta primera rama en el repositorio es la rama predeterminada. + diff --git a/translations/es-ES/data/reusables/branches/set-default-branch.md b/translations/es-ES/data/reusables/branches/set-default-branch.md new file mode 100644 index 0000000000000..44c00b5fc9edb --- /dev/null +++ b/translations/es-ES/data/reusables/branches/set-default-branch.md @@ -0,0 +1 @@ +Puedes configurar el nombre de la rama predeterminada para los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)", "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)", y {% if currentVersion == "free-pro-team@latest" %}"[Requerir políticas de administración de repositorio en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)".{% else %}"[requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)".{% endif %} diff --git a/translations/es-ES/data/reusables/classroom/about-assignments.md b/translations/es-ES/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000000..91a5e8e3ebec6 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Cada tarea tiene un título y una fecha límite ocpional. Puedes escoger la visibilidad de los repositorios que {% data variables.product.prodname_classroom %} crea, y elegir los permisos de acceso. También puedes calificar automáticamente las tareas y crear un espacio dedicado para debatirlas con el alumno. diff --git a/translations/es-ES/data/reusables/classroom/about-autograding.md b/translations/es-ES/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000000..c5fb1056d2e6f --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +Puedes utilizar las calificaciones automáticas para verificar el trabajo de un alumno automáticamente para una tarea en {% data variables.product.prodname_classroom %}. Configuras las pruebas para una tarea, y éstas se ejecutan automáticamente cada que un alumno las suba a un repositorio de tareas en {% data variables.product.product_location %}. El alumno puede ver los resultados de la prueba, hacer cmabios y subir información para ver resultados nuevos. diff --git a/translations/es-ES/data/reusables/classroom/about-classrooms.md b/translations/es-ES/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000000..250570bca4909 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +Un aula en {% data variables.product.prodname_classroom %} es donde los maestros y alumnos interactuan durante un curso. Los maestros pueden crear un registro de alumnos para el aula y luego crear, asignar, revisar y calificar las tareas dentro de ella. diff --git a/translations/es-ES/data/reusables/classroom/about-online-ides.md b/translations/es-ES/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000000..69ac12de24300 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +Opcionalmente, puedes configurar una tarea para utilizar un ambiente de desarrollo integrado (IDE) en línea. Los IDE en línea permiten a tus alumnos escribir código, ejecutar programas y colaborar desde un buscador, sin instalar tanto Git como una cadena de herramientas de desarrollo integral en la computadora del alumno. Si eliges un IDE en línea para una tarea, los alumnos aún pueden revisar y ejecutar el código localmente en una computadora con el software necesario. diff --git a/translations/es-ES/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/es-ES/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000000..4e4f63bf48fca --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +Debes crear un aula antes de que puedas crear una tarea. Para obtener más información, consulta la sección "[Administrar las aulas](/education/manage-coursework-with-github-classroom/manage-classrooms)". diff --git a/translations/es-ES/data/reusables/classroom/assignments-click-pencil.md b/translations/es-ES/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000000..abc49ad2e13f4 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. A la derecha de la tarea que quieras editar, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Icono de lápiz para editar una tarea en la lista de tareas](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/es-ES/data/reusables/classroom/assignments-group-definition.md b/translations/es-ES/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000000..1ec0731a2c566 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +Una tarea grupal es un trabajo de curso colaborativo para los grupos de alumnos en {% data variables.product.prodname_classroom %}. diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/es-ES/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000000..93f6a9848c6a2 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Opcionalmente, puedes asignar una fecha límite para la tarea. Debajo de "Fecha límite (opcional)", da clic en el campo de texto y luego utiliza el selector de fechas para asignar una fecha límite. + +
+ Selector de fechas para la fecha límite de la tarea +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000000..3c1096d29771c --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +Para elegir un IDE en línea para la tarea, selecciona el menú desplegable de **Seleccionar un IDE en línea** y luego da clic enel IDE que te gustaría que utilizaran tus alumnos. + +
+ Utilizar el menú desplegable de 'Seleccionar un IDE en línea' para dar clic en un IDE en línea para la tarea +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000000..63dec930bc8bf --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Debajo de "Agregar un repositorio de plantilla para dar a los alumnos un código inicial", selecciona el menú desplegable **Seleccionar un repositorio** y luego teclea la consulta de búsqueda. En la lista de resultados, da clic en el repositorio de plantilla que quieras utilizar para el código inicial. + +
+ Utilizar el menú desplegable de 'Seleccionar un repositorio' para encontrar un repositorio de plantilla para utilizar como código inicial para una tarea +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md new file mode 100644 index 0000000000000..cb79652e03c15 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +Los repositorios de una tarea pueden ser públicos o privados. Si utilizas repositorios privados, solo el alumno o equipo puede ver la retroalimentación que proporciones. + +También puedes decidir si quieres otorgar a los alumnos permisos administrativos en el repositorio para una tarea. Otorga permisos administrativos si es que el alumno debe realizar tareas administrativas en el repositorio de tareas. Para obtener más información, consulta las secciones "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" y "[Niveles de permiso para los repositorios de una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". + +Selecciona una visibilidad debajo de "Visibilidad del repositorio". Opcionalmente, selecciona **Otorgar a los alumnos acceso administrativo para el repositorio**. + +
+ Opciones de visibilidad para los repositorios de tareas +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000000..714d7ce4c4946 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
+ +Cuando termines, da clic en **Continuar** para configurar un código de inicio y un ambiente de desarrollo para la tarea. + +
+ Botón 'Continuar' +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000000..aea468c3a87d3 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
+ +Cuando termines, da clic en **Continuar** para configurar las calificaciones automáticas y la retroalimentación del proyecto. + +
+ Botón 'Continuar' +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/es-ES/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000000..6cf65b8cc44a7 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +Para crear una tarea, da clic en **Crear tarea**. + +
+ Botón de 'crear tarea' +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/es-ES/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000000..d82d7cf2c3238 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +Para crear solicitudes de cambio para el debate de retroalimentación, selecciona **Habilitar las solicitudes de cambios de retroalimentación**. + +
+ Casilla de verificación para 'Habilitar solicitudes de cambios de retroalimentación' +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000000..6318adab04abc --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +Para crear una tarea, ingresa en {% data variables.product.prodname_classroom_with_url %} y navega a un aula. En la pestaña de {% octicon "repo" aria-label="The repo icon" %} **Tareas**, da clic en **Tarea nueva**. + +
+ En el botón de 'Tarea nueva' +
diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/es-ES/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000000..49620374871e4 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Opcionalmente, decide si quieres proporcionar repositorios vacíos o con código inicial, y preconfigura el ambiente de desarrollo para tus alumnos. diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/es-ES/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000000..6290d808ad0f4 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/es-ES/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000000..f4630bb89393d --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +Puedes prevenir que los alumnos cambien los archivos que contienen pruebas para calificar automáticamente u otros archivos importantes en el repositorio de tareas. + +Debajo de "Rutas de archivo protegidas", teclea las rutas relativas que se deben proteger dentro del repositorio. + +
+ Campo de texto para teclear las rutas de archivo protegidas +
\ No newline at end of file diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/es-ES/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000000..7ec36ef91d93f --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} Para obtener más información, consulta la sección "[Utilizar las calificaciones automáticas](/education/manage-coursework-with-github-classroom/use-autograding)". + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} Para obtener más información, consulta la sección "[Métodos para calificar](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)". + +
+ Utilizar el menú desplegable de 'Agregar prueba' para dar clic en un método para calificar +
+ +
+ +Define los parámetros de tu caso de prueba, como el nombre, comandos, entradas, salidas, tiempo límite y puntos. Cuando termines, da clic en **Guardar caso de prueba**. + +
+ Botón de 'Guardar caso de prueba' para una prueba de calificación automática +
+ +
+ +Puedes agregar más pruebas con el menú desplegable de **Agregar prueba**, y puedes editar o borrar las pruebas existentes con {% octicon "pencil" aria-label="The pencil icon" %} o con {% octicon "trash" aria-label="The trash icon" %}. + +
+ Iconos de lápiz y de cesto de basura para editar o borrar una prueba de calificación automática +
\ No newline at end of file diff --git a/translations/es-ES/data/reusables/classroom/assignments-individual-definition.md b/translations/es-ES/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000000..ce82684281fb1 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +Una tarea individual es parte del trabajo del curso para cada alumno que participe en uno de ellos dentro de {% data variables.product.prodname_classroom %}. Se pretende que el alumno complete una tarea individual sin ayuda de otros alumnos. diff --git a/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000000..56a7b4ef37964 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +Para prevenir que los alumnos acepten o emitan una tarea, deselecciona **Habilitar la URL de invitación a las tareas**. Para editar la tarea, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar tarea**. diff --git a/translations/es-ES/data/reusables/classroom/assignments-type-a-title.md b/translations/es-ES/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000000..096f876efefe1 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Teclea un título para la tarea. Opcionalmente, da clic en {% octicon "pencil" aria-label="The pencil icon" %} para editar el prefijo. + +
+ Título y prefijo de la tarea +
diff --git a/translations/es-ES/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/es-ES/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000000..4be3071507156 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +Para cada tarea grupal, {% data variables.product.prodname_classroom %} creará automáticamente un repositorio único compartido para que ingrese el equipo. El repositorio puede estar vacío, o puedes crearlo desde un repositorio de plantilla con código inicial, documentación, pruebas y otros recursos. El repositorio pertenece a tu cuenta de organización en {% data variables.product.product_name %}, y {% data variables.product.prodname_classroom %} le otorga acceso a los equipos que los alumnos crean o a los cuales se unen cuando aceptan la tarea. diff --git a/translations/es-ES/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/es-ES/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000000..25e26acdedb43 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +Cuando un alumno acepta una tarea, {% data variables.product.prodname_classroom %} crea automáticamente un repositorio nuevo para un alumno. Los repositorios pueden estar vacíos, o puedes crearlos desde un repositorio de plantilla con código, documentación y pruebas iniciales, así como con otros recursos. Cada repositorio de tarea pertenece a tu cuenta de organización en {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/es-ES/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000000..7bca7ea04cfa6 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +Predeterminadamente, {% data variables.product.prodname_classroom %} habilita una URL de invitación para cada tarea que crees. Los alumnos pueden aceptar y emitir la tarea mientras que se habilita la URL de invitación. Puedes compartir la URL con tus alumnos en tu LMS, página principal del curso, o donde sea que publiques las tareas. Los alumnos también pueden navegar a la tarea en {% data variables.product.prodname_classroom %} si ya la aceptaron en el aula. diff --git a/translations/es-ES/data/reusables/classroom/click-assignment-in-list.md b/translations/es-ES/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000000..94ad6cede4842 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. En la lista de tareas, da clic en aquellaque quieras ver. ![Lista de tareas para las tareas de un aula](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/es-ES/data/reusables/classroom/click-classroom-in-list.md b/translations/es-ES/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000000..bf72fe9cd83b0 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. En la lista de aulas, da clic en aquella que quieras ver. ![Aula en la lista de aulas de una organización](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/es-ES/data/reusables/classroom/click-settings.md b/translations/es-ES/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000000..0782367223a31 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Debajo del nombre del aula, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Pestaña de "Configuración" del aula](/assets/images/help/classroom/click-settings.png) diff --git a/translations/es-ES/data/reusables/classroom/click-students.md b/translations/es-ES/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000000..ac24a38956fc1 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Debajo del nombre del aula, da clic en {% octicon "people" aria-label="The people icon" %} **Alumnos**. ![Pestaña de "Alumnos" de un aula](/assets/images/help/classroom/click-students.png) diff --git a/translations/es-ES/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/es-ES/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000000..30ce29cf93e6b --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +Para obtener más información, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". diff --git a/translations/es-ES/data/reusables/classroom/guide-create-new-classroom.md b/translations/es-ES/data/reusables/classroom/guide-create-new-classroom.md new file mode 100644 index 0000000000000..c3dc7d8330aad --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +1,3 @@ +1. En la lista de organizaciones, da clic en aquella que te gustaría utilizar para tu aula. Opcionalmente, puedes crear una organizción nueva. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". ![Organización en la lista de organizaciones para crear un aula nueva](/assets/images/help/classroom/click-organization.png) +1. Teclea el nombre de tu aula. ![Campo de texto para teclear el nombre del aula](/assets/images/help/classroom/type-classroom-name.png) +1. Da clic en **Crear aula**. ![Campo de texto para teclear el nombre del aula](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/es-ES/data/reusables/classroom/invitation-url-warning.md b/translations/es-ES/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000000..198f8a1d4a4c3 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia**: Ten cuidado de dónde compartes las URL de invitación. Cualquiera con una URL de invitación para una tarea puede aceptar dicha invitación y asociar una cuenta de usuario en {% data variables.product.product_name %} con un identificador en tu registro de alumnos. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000000..a261d06a92f0a --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +Cuando un alumno acepta una tarea con un IDE en línea, dicho repositorio incluirá un archivo _README.md_ con un botón especial en la parte superior del archivo. El botón enlaza al alumno directamente con el espacio de trabajo en el IDE en línea. diff --git a/translations/es-ES/data/reusables/classroom/sign-into-github-classroom.md b/translations/es-ES/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000000..3c87b5a9d2335 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/es-ES/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/es-ES/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000000..62d2148951489 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Debajo de "Agregar pruebas que se califiquen automáticamente", selecciona el menú desplegable de **Agregar prueba**, y luego da clic enel método para calificar que quieras utilizar. diff --git a/translations/es-ES/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/es-ES/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000000..c890b16bf75d5 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +Opcionalmente, puedes elegir un repositorio de plantilla como un código de inicio para la tarea. El repositorio de plantilla debe pertenecer a tu organización o ser un repositorio público en {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/es-ES/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000000..5efb082955143 --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +Puedes crear una solicitud de cambios automáticamente en donde puedas proporcionar retroalimentación y responder las preguntas del alumno sobre una tarea. Para obtener más información acerca de la revisión de cambios en una solicitud de cambios, consulta la sección "[Revisar los cambios en las solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)". diff --git a/translations/es-ES/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/es-ES/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000000..0865c3d63fe6e --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +Puede que quieras predefinir la configuración predeterminada para los repositorios de tareas que {% data variables.product.prodname_classroom %} crea desde un repositorio de plantilla. Por ejemplo, puede que quieras inhabilitar las propuestas, definir las etiquetas para las solicitudes de cambios o proteger una rama en alguno o todos los repositorios. diff --git a/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md new file mode 100644 index 0000000000000..2f1068273e42f --- /dev/null +++ b/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% tip %} + +**Tip**: También puedes filtrar propuestas o solicitudes de cambios si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" o "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" en la documentación de {% data variables.product.prodname_cli %}. + +{% endtip %} +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/about-code-scanning.md b/translations/es-ES/data/reusables/code-scanning/about-code-scanning.md new file mode 100644 index 0000000000000..0ea06267cd8b6 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/about-code-scanning.md @@ -0,0 +1 @@ +{% data variables.product.prodname_code_scanning_capc %} es una característica que utilizas para analizar el código en un repositorio de {% data variables.product.prodname_dotcom %} para encontrar vulnerabilidades de seguridad y errores de código. Cualquier problema que se identifique en el análisis se muestra en {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. diff --git a/translations/es-ES/data/reusables/code-scanning/analyze-go.md b/translations/es-ES/data/reusables/code-scanning/analyze-go.md new file mode 100644 index 0000000000000..53d2f894e8f93 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/analyze-go.md @@ -0,0 +1 @@ +{% data variables.product.prodname_codeql %} también ejecuta una compilación para que los proyectos de Go configuren el proyecto. Sin embargo, en contraste con el resto de los lenguajes compilados, todos los archivos de Go en el repositorio se extraen, y no únicamente aquellos que se compilaron. Los comandos de compilación personalizados no son compatibles con Go. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/autobuild-add-build-steps.md b/translations/es-ES/data/reusables/code-scanning/autobuild-add-build-steps.md new file mode 100644 index 0000000000000..eb468a112afc5 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/autobuild-add-build-steps.md @@ -0,0 +1 @@ +Si el código de C/C++, C# o de Java en tu repositorio tiene un proceso de compilación diferente al estándar, el `autobuild` podría fallar. Necesitarás eliminar el paso de `autobuild` del flujo de trabajo y agregar los pasos de compilación manualmente. diff --git a/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md new file mode 100644 index 0000000000000..18d9b599cc0ed --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/autobuild-compiled-languages.md @@ -0,0 +1 @@ +Para los lenguajes compilados compatibles, puedes utilizar la acción de `autobuild` en el {% data variables.product.prodname_codeql_workflow %} para compilar tu código. Esto te evita tener que especificar los comandos de compilación explícitos paraC/C++, C#, y Java. diff --git a/translations/es-ES/data/reusables/code-scanning/beta-codeql-runner.md b/translations/es-ES/data/reusables/code-scanning/beta-codeql-runner.md new file mode 100644 index 0000000000000..17c6b184dbd91 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/beta-codeql-runner.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** El {% data variables.product.prodname_codeql_runner %} se encuentra actualmente en beta y está sujeto a cambios. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/beta.md b/translations/es-ES/data/reusables/code-scanning/beta.md new file mode 100644 index 0000000000000..7d1b5dbc94798 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/beta.md @@ -0,0 +1,9 @@ +{% if currentVersion == "enterprise-server@2.22" %} + +{% note %} + +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/choose-alert-dismissal-reason.md b/translations/es-ES/data/reusables/code-scanning/choose-alert-dismissal-reason.md new file mode 100644 index 0000000000000..68bbb2fbb76b4 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/choose-alert-dismissal-reason.md @@ -0,0 +1 @@ +Es importante elegir la razón adecuada del menú desplegable, ya que esto puede afectar si la consulta continuará incluyéndose en los análisis futuros. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/click-alert-in-list.md b/translations/es-ES/data/reusables/code-scanning/click-alert-in-list.md new file mode 100644 index 0000000000000..360a6f80cd121 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/click-alert-in-list.md @@ -0,0 +1 @@ +1. Debajo de "Code scanning", da clic en la alerta que quieras explorar. ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) diff --git a/translations/es-ES/data/reusables/code-scanning/close-alert-examples.md b/translations/es-ES/data/reusables/code-scanning/close-alert-examples.md new file mode 100644 index 0000000000000..ceb6a6bf4ec6c --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/close-alert-examples.md @@ -0,0 +1 @@ +Por ejemplo, un error en el código que se utiliza únicamente para hacer pruebas, o cuando el esfuerzo de areglar el error es mayor que el beneficio potencial de mejorar el código. diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md new file mode 100644 index 0000000000000..f96857d61b59e --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md @@ -0,0 +1,8 @@ +Las siguientes suites de consultas se compilan en el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} y están disponibles para utilizarse. + + | Conjunto de consultas | Descripción | + |:---------------------- |:------------------------------------------------------------------------------------ | + | `security-extended` | Las consultas de severidad y precisión más baja que aquellas predeterminadas | + | `security-and-quality` | Las consultas de `security-extended`, mas aquellas de mantenibilidad y confiabilidad | + +Cuando especificas una suite de consultas, el motor de análisis de {% data variables.product.prodname_codeql %} ejecutará las consultas dentro de la suite para ti, adicionalmente a el conjunto de consultas adicional. diff --git a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md new file mode 100644 index 0000000000000..16b65940821a0 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md @@ -0,0 +1 @@ +Habitualmente, no necesitas editar el flujo de trabajo predeterminado para {% data variables.product.prodname_code_scanning %}. Sin embargo, si lo requieres, puedes editar el flujo de trabajo para personalizar algunos de los ajustes. Por ejemplo, puedes editar el {% data variables.product.prodname_codeql_workflow %} de {% data variables.product.prodname_dotcom %} para especificar la frecuencia de los escaneos, los idiomas o los directorios a escanear, y qué debe buscar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} en tu código. También podrías necesitar editar el {% data variables.product.prodname_codeql_workflow %} si utilizas un conjunto de comandos específicos para compilar tu código. diff --git a/translations/es-ES/data/reusables/code-scanning/enabling-options.md b/translations/es-ES/data/reusables/code-scanning/enabling-options.md new file mode 100644 index 0000000000000..0bf07efd6b54d --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/enabling-options.md @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + + + + + +
+ Tipo de análisis + + Opciones para generar alertas +
+ {% data variables.product.prodname_codeql %} + + Utilizar {% data variables.product.prodname_actions %} (consulta la sección "Habilitar el {% data variables.product.prodname_code_scanning %} utilizando acciones") o utilizar el {% data variables.product.prodname_codeql_runner %} en un sistema de integración continua (IC) de terceros (consulta la sección "Ejecutar el escaneo de código en tu sistema de IC"). +
+ Third‑party + + Utilizar {% data variables.product.prodname_actions %} (consulta la sección "Habilitar el {% data variables.product.prodname_code_scanning %}utilizando acciones") o generarlas externamente y cargarlas a {% data variables.product.product_name %} (consulta la sección "Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}"). +
diff --git a/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md new file mode 100644 index 0000000000000..ede2f9aec04ef --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md @@ -0,0 +1,9 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +{% note %} + +**Nota:** Tu administrador de sitio debe habilitar el {% data variables.product.prodname_code_scanning %} para {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Si quieres utilizar {% data variables.product.prodname_actions %} para escanear tu código, el administrador de sitio también puede habilitar las {% data variables.product.prodname_actions %} y configurar la infraestructura que se requiera. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_code_scanning %} en tu aplicativo](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md new file mode 100644 index 0000000000000..abbf29088ec81 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md @@ -0,0 +1,9 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +{% note %} + +**Nota:** Tu administrador de sitio debe habilitar el {% data variables.product.prodname_code_scanning %} para {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_code_scanning %} en tu aplicativo](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/example-configuration-files.md b/translations/es-ES/data/reusables/code-scanning/example-configuration-files.md new file mode 100644 index 0000000000000..5ed73d4367d3d --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/example-configuration-files.md @@ -0,0 +1,32 @@ +Este archivo de configuración agrega el conjunto de consultas `security-and-quality` a la lista de consultas que se ejecutan con {% data variables.product.prodname_codeql %} cuando se escanea tu código. Para obtener más información acerca de los conjuntos de consultas que están disponibles para utilizarse, consulta la sección "[Ejecutar consultas adicionales](#running-additional-queries)". + +``` yaml +name: "My {% data variables.product.prodname_codeql %} config" + +queries: + - uses: security-and-quality +``` + +El siguiente archivo de configuración inhabilita las consultas predeterminadas y especifica un conjunto de consultas personalizadas para ejecutarse en vez de éstas. También configura a {% data variables.product.prodname_codeql %} para escanear archivos en el directorio _src_ (relativo a la raíz), con excepción del directorio _src/node_modules_ y de los archivos cuyo nombre termine en _.test.js_. Los archivos en _src/node_modules_ y aquellos cuyos nombres terminan en _.test.js_ se excluyen por lo tanto del análisis. + +``` yaml +name: "My {% data variables.product.prodname_codeql %} config" + +disable-default-queries: true + +queries: + - name: Use an in-repository {% data variables.product.prodname_ql %} pack (run queries in the my-queries directory) + uses: ./my-queries + - name: Use an external JavaScript {% data variables.product.prodname_ql %} pack (run queries from an external repo) + uses: octo-org/javascript-qlpack@main + - name: Use an external query (run a single query from an external {% data variables.product.prodname_ql %} pack) + uses: octo-org/python-qlpack/show_ifs.ql@main + - name: Use a query suite file (run queries from a query suite in this repo) + uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls + +paths: + - src +paths-ignore: + - src/node_modules + - '**/*.test.js' +``` diff --git a/translations/es-ES/data/reusables/code-scanning/false-positive-fix-codeql.md b/translations/es-ES/data/reusables/code-scanning/false-positive-fix-codeql.md new file mode 100644 index 0000000000000..3157ab0f3a0ac --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/false-positive-fix-codeql.md @@ -0,0 +1 @@ +If you {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} a {% data variables.product.prodname_codeql %} alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the {% data variables.product.prodname_codeql %} repository and improving the analysis. Para obtener más información acerca de {% data variables.product.prodname_codeql %}, consulta la sección "[Contribuir con {% data variables.product.prodname_codeql %}](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)". diff --git a/translations/es-ES/data/reusables/code-scanning/get-started-uploading-third-party-data.md b/translations/es-ES/data/reusables/code-scanning/get-started-uploading-third-party-data.md new file mode 100644 index 0000000000000..3e2e5bdfb3d37 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/get-started-uploading-third-party-data.md @@ -0,0 +1 @@ +Para comenzar, consulta la sección "[Subir un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". diff --git a/translations/es-ES/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md b/translations/es-ES/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md new file mode 100644 index 0000000000000..04dd204c51ec3 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md @@ -0,0 +1 @@ +{% data variables.product.prodname_code_scanning_capc %} es interoperable con herramientas de escaneo de código de terceros que producen datos de Formato de Intercambio de Resultado de Análisis (SARIF). SARIF es un estándar de código abierto. Para obtener más información, consulta la sección "[Resultados de SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)". diff --git a/translations/es-ES/data/reusables/code-scanning/not-available.md b/translations/es-ES/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..6fdf6b03a0944 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md new file mode 100644 index 0000000000000..fe2cfd4a9a5c1 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md @@ -0,0 +1,9 @@ +Cuando utilizas {% data variables.product.prodname_codeql %} para escanear código, el motor de análisis de {% data variables.product.prodname_codeql %} genera una base de datos desde el código y ejecuta consultas en éste. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)". + +El {% data variables.product.prodname_codeql %} utiliza un conjunto predeterminado de consultas, pero puedes especificar más consultas para que se ejecuten, adicionalmente a las predeterminadas. Las consultas que quieras ejecutar deberán pertenecer a un paquete de {% data variables.product.prodname_ql %} y pueden estar en tu propio repositorio o en cualquier repositorio público. Para obtener más información, consulta la sección "[Acerca de los paquetes de {% data variables.product.prodname_ql %}](https://help.semmle.com/codeql/codeql-cli/reference/qlpack-overview.html)". + +Las consultas solo deberán depender de las bibliotecas estándar (es decir, aquellas referenciadas por una declaración `import LANGUAGE` en tu consulta), o de aquellas en el mismo paquete de {% data variables.product.prodname_ql %} que la consulta. Las bibliotecas estándar se ubican en el repositorio [github/codeql](https://github.com/github/codeql). Para obtener más información, consulta la sección "[Acerca de las consultas de CodeQL](https://help.semmle.com/QL/learn-ql/writing-queries/introduction-to-queries.html)". + +Puedes especificar un solo archivo _.ql_, un directorio que contenga varios archivos _.ql_, un archivo de definición de suite de consulta _.qls_, o cualquier combinación de éstos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://help.semmle.com/codeql/codeql-cli/procedures/query-suites.html)". + +{% if currentVersion == "free-pro-team@latest" %}No te recomendamos referenciar suits de consultas directamente del repositorio de `github/codeql`, como `github/codeql/cpp/ql/src@main`. Puede que dichas consultas no se compilen con la misma versión de {% data variables.product.prodname_codeql %} que se utiliza para tus otras consultas, lo cual puede llevar a que se cometan errores durante el análisis.{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/specify-language-to-analyze.md b/translations/es-ES/data/reusables/code-scanning/specify-language-to-analyze.md new file mode 100644 index 0000000000000..afb492c188f80 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/specify-language-to-analyze.md @@ -0,0 +1 @@ +Si tu repositorio contiene código en más de uno de los lenguajes compatibles, puedes elegir qué lenguajes quieres analizar. Hay varias razones que por las cuales querrías prevenir que un lenguaje se analice. Por ejemplo, el proyecto puede tener dependencias en un lenguaje distinto al del cuerpo principal de tu código, y tal vez prefieras no ver las alertas para esas dependencias. diff --git a/translations/es-ES/data/reusables/code-scanning/supported-languages.md b/translations/es-ES/data/reusables/code-scanning/supported-languages.md new file mode 100644 index 0000000000000..91222f40b4150 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/supported-languages.md @@ -0,0 +1,6 @@ +- C/C++ +- C# +- Go +- Java +- JavaScript/TypeScript +- Python diff --git a/translations/es-ES/data/reusables/code-scanning/you-can-upload-third-party-analysis.md b/translations/es-ES/data/reusables/code-scanning/you-can-upload-third-party-analysis.md new file mode 100644 index 0000000000000..9fe20ef7da912 --- /dev/null +++ b/translations/es-ES/data/reusables/code-scanning/you-can-upload-third-party-analysis.md @@ -0,0 +1 @@ +Puedes cargar archivos SARIF de herramientas de análisis estático de terceros a {% data variables.product.prodname_dotcom %} y ver las alertas de {% data variables.product.prodname_code_scanning %} en tu repositorio. diff --git a/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md new file mode 100644 index 0000000000000..6df432813bb9f --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md @@ -0,0 +1 @@ +{% data variables.product.prodname_codespaces %} es de uso gratuito durante el beta. Cuando {% data variables.product.prodname_codespaces %} se hace generalmente disponible, se te cobrará por el almacenamiento y uso del procesamiento. diff --git a/translations/es-ES/data/reusables/codespaces/about-configuration.md b/translations/es-ES/data/reusables/codespaces/about-configuration.md new file mode 100644 index 0000000000000..3ceca47b26568 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/about-configuration.md @@ -0,0 +1 @@ +Puedes crear una configuración predeterminada de codespaces para tu repositorio, la cual determine el ambiente de cada codespace nuevo que alguien cree para este repositorio. La configuración define un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y redireccionamiento de puertos. diff --git a/translations/es-ES/data/reusables/codespaces/about-personalization.md b/translations/es-ES/data/reusables/codespaces/about-personalization.md new file mode 100644 index 0000000000000..fa00ae8118f93 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/about-personalization.md @@ -0,0 +1 @@ +También puedes personalizar los aspectos del ambiente de un codespace para cada codespace que tu cuenta cree. La personalización puede incluir preferencias de shell y herramientas adicionales. diff --git a/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md b/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md new file mode 100644 index 0000000000000..2181e82fea99c --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md @@ -0,0 +1,5 @@ +Durante el beta, la funcionalidad será limitada. +- {% data reusables.codespaces.use-chrome %} +- Úicamente estará disponible un tamaño único de codespace. +- Únicamente serán compatibles los contenedores Linux. +- Un codespace no se puede reanudar completamente. Los procesos que estuvieran ejecutándose al momento en el que se paró un codespace no se reiniciarán. diff --git a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md new file mode 100644 index 0000000000000..d2f101906bf31 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -0,0 +1 @@ +1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/translations/es-ES/data/reusables/codespaces/codespace-config-order.md b/translations/es-ES/data/reusables/codespaces/codespace-config-order.md new file mode 100644 index 0000000000000..bed5b60232eb8 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/codespace-config-order.md @@ -0,0 +1 @@ +Tu personalización de `dotfiles` se aplica antes de una configuración predeterminada de codespaces de un repositorio. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md new file mode 100644 index 0000000000000..0133ab3010dfc --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md @@ -0,0 +1 @@ +Cada codespace se asocia con una rama específica de un repositorio. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md b/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md new file mode 100644 index 0000000000000..f26636327fa82 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md @@ -0,0 +1 @@ +Cada codespace que crees está únicamente disponible para ti. Nadie más puede trabajar en tu codespace. diff --git a/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md new file mode 100644 index 0000000000000..d74e19de2e56d --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md @@ -0,0 +1 @@ +Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de dos codespaces durante el beta público limitado. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. diff --git a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md new file mode 100644 index 0000000000000..363dffdd70a21 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -0,0 +1 @@ +Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección "[Utilizar codespaces en {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". diff --git a/translations/es-ES/data/reusables/codespaces/devcontainer-location.md b/translations/es-ES/data/reusables/codespaces/devcontainer-location.md new file mode 100644 index 0000000000000..4108e47069820 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/devcontainer-location.md @@ -0,0 +1 @@ +Este archivo puede ubicarse en la raíz del repositorio o en una carpeta que se llame `.devcontainer`. Si el archivo se ubica en la raíz del repositorio, el nombre del archivo debe comenzar con un punto: `.devcontainer.json`. diff --git a/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md b/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md new file mode 100644 index 0000000000000..639c7df307129 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md @@ -0,0 +1 @@ +1. En la parte superior de cualquier página, da clic en **Codespaces**. ![Enlace de {% data variables.product.prodname_codespaces %} en el encabezado](/assets/images/help/codespaces/header-link.png) diff --git a/translations/es-ES/data/reusables/codespaces/release-stage.md b/translations/es-ES/data/reusables/codespaces/release-stage.md new file mode 100644 index 0000000000000..fa1a751d6d040 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/release-stage.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/unsupported-repos.md b/translations/es-ES/data/reusables/codespaces/unsupported-repos.md new file mode 100644 index 0000000000000..e39868b20f05a --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/unsupported-repos.md @@ -0,0 +1 @@ +Durante el beta, no serán compatibles los repositorios privados que pertenezcan a las organizaciones o cualquier repositorio perteneciente a una organización que requiera el inicio de sesión único de SAML. diff --git a/translations/es-ES/data/reusables/codespaces/use-chrome.md b/translations/es-ES/data/reusables/codespaces/use-chrome.md new file mode 100644 index 0000000000000..cb55835480f2e --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/use-chrome.md @@ -0,0 +1 @@ +Para una mejor experiencia con {% data variables.product.prodname_codespaces %}, te recomenamos utilizar un buscador basado en Chromium, como Google Chrome o Microsoft Edge. diff --git a/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md b/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md new file mode 100644 index 0000000000000..17af192cf765e --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md @@ -0,0 +1 @@ +Puedes editar código, depurar y utilizar comandos de git mientras que desarrollas en un codespace con {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs). diff --git a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md new file mode 100644 index 0000000000000..1519e4c06f50a --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md @@ -0,0 +1 @@ +Cuando configuras los ajustes de editor para {% data variables.product.prodname_vscode %}, hay tres alcances disponibles: _Espacio de trabajo_, _[Codespaces] Remotos _, y _Usuario_. Si una configuración se define en varios alcances, los ajustes de _espacio de trabajo_ tomarán prioridad, luego los de _[Codespaces] Remotos_, y luego los de _Usuario_. diff --git a/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md new file mode 100644 index 0000000000000..c6b843423d94e --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md @@ -0,0 +1 @@ +Puedes ver cada codespace que pertenezca a tu cuenta de usuario en [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/es-ES/data/reusables/command_line/change-current-directory-clone.md b/translations/es-ES/data/reusables/command_line/change-current-directory-clone.md new file mode 100644 index 0000000000000..36d7e5d402b7a --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/change-current-directory-clone.md @@ -0,0 +1 @@ +4. Cambia el directorio de trabajo actual a la ubicación en donde quieres clonar el directorio. diff --git a/translations/es-ES/data/reusables/command_line/git-clone-url.md b/translations/es-ES/data/reusables/command_line/git-clone-url.md new file mode 100644 index 0000000000000..a01ca2f23094c --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/git-clone-url.md @@ -0,0 +1,4 @@ +5. Escribe `git clone`, y luego pega la URL que copiaste antes. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY + ``` diff --git a/translations/es-ES/data/reusables/command_line/local-clone-created.md b/translations/es-ES/data/reusables/command_line/local-clone-created.md new file mode 100644 index 0000000000000..dcc95bb352212 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/local-clone-created.md @@ -0,0 +1,9 @@ +6. Presiona **Enter** para crear tu clon local. + ```shell + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY + > Cloning into `Spoon-Knife`... + > remote: Counting objects: 10, done. + > remote: Compressing objects: 100% (8/8), done. + > remove: Total 10 (delta 1), reused 10 (delta 1) + > Unpacking objects: 100% (10/10), done. + ``` diff --git a/translations/es-ES/data/reusables/command_line/manipulating_file_prereqs.md b/translations/es-ES/data/reusables/command_line/manipulating_file_prereqs.md new file mode 100644 index 0000000000000..52e7ca04d2d10 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/manipulating_file_prereqs.md @@ -0,0 +1,4 @@ +Este procedimiento supone que ya has: + + - [creado un repositorio en {% data variables.product.product_name %}](/articles/creating-a-new-repository) o que tienes un repositorio existente que es propiedad de alguien más con quien desees colaborar + - [clonado el repositorio de forma local en tu computadora](/articles/cloning-a-repository) diff --git a/translations/es-ES/data/reusables/command_line/open_the_multi_os_terminal.md b/translations/es-ES/data/reusables/command_line/open_the_multi_os_terminal.md new file mode 100644 index 0000000000000..d93f5c5af274c --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/open_the_multi_os_terminal.md @@ -0,0 +1 @@ +1. Abre la TerminalTerminalGit Bash. diff --git a/translations/es-ES/data/reusables/command_line/provide-an-access-token.md b/translations/es-ES/data/reusables/command_line/provide-an-access-token.md new file mode 100644 index 0000000000000..99daf95854e1b --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/provide-an-access-token.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Si estás accediendo a una organización que utilice el SSO de SAML, también debes autorizar tu token de acceso personal para acceder a ella antes de que te autentiques. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %} diff --git a/translations/es-ES/data/reusables/command_line/providing-token-as-password.md b/translations/es-ES/data/reusables/command_line/providing-token-as-password.md new file mode 100644 index 0000000000000..bfbc541ce7158 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/providing-token-as-password.md @@ -0,0 +1,9 @@ +Una vez que tengas un token, puedes ingresarlo en lugar de tu contraseña cuando realices operaciones de Git a través de HTTPS. + +Por ejemplo, en la línea de comando ingresarás lo siguiente: + +```shell +$ git clone https://{% data variables.command_line.codeblock %}/username/repo.git +Username: your_username +Password: your_token +``` diff --git a/translations/es-ES/data/reusables/command_line/start_ssh_agent.md b/translations/es-ES/data/reusables/command_line/start_ssh_agent.md new file mode 100644 index 0000000000000..7ab5d4bfe82c7 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/start_ssh_agent.md @@ -0,0 +1,5 @@ +Inicia el agente SSH en segundo plano. +```shell +$ eval "$(ssh-agent -s)" +> Agent pid 59566 +``` diff --git a/translations/es-ES/data/reusables/command_line/switching_directories_procedural.md b/translations/es-ES/data/reusables/command_line/switching_directories_procedural.md new file mode 100644 index 0000000000000..d5075ccb36b65 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/switching_directories_procedural.md @@ -0,0 +1 @@ +1. Cambia el directorio de trabajo actual por tu repositorio local. diff --git a/translations/es-ES/data/reusables/command_line/use_with_support_only.md b/translations/es-ES/data/reusables/command_line/use_with_support_only.md new file mode 100644 index 0000000000000..a4eed392a6164 --- /dev/null +++ b/translations/es-ES/data/reusables/command_line/use_with_support_only.md @@ -0,0 +1 @@ +**No uses** este comando sin indicación del [{% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/). El uso incorrecto podría causar daño o pérdida de datos. diff --git a/translations/es-ES/data/reusables/commits/about-commits.md b/translations/es-ES/data/reusables/commits/about-commits.md new file mode 100644 index 0000000000000..09601c0d8e9ac --- /dev/null +++ b/translations/es-ES/data/reusables/commits/about-commits.md @@ -0,0 +1,7 @@ +De forma similar al guardar un archivo que se editó, una confirmación registra los cambios en uno o más archivos en tu rama. Git asigna una ID única a cada comentario, a la cual se le llama SHA o hash, la cual identifica: + +- Los cambios específicos +- Cuando se realizaron los cambios +- Quién creó los cambios + +Cuando realizas una confirmación, debes incluir un mensaje de confirmación que describa brevemente los cambios. diff --git a/translations/es-ES/data/reusables/community/interaction-limits-duration.md b/translations/es-ES/data/reusables/community/interaction-limits-duration.md new file mode 100644 index 0000000000000..fb858accd8418 --- /dev/null +++ b/translations/es-ES/data/reusables/community/interaction-limits-duration.md @@ -0,0 +1 @@ +When you enable an interaction limit, you can choose a duration for the limit: 24 hours, 3 days, 1 week, 1 month, or 6 months. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/community/interaction-limits-restrictions.md b/translations/es-ES/data/reusables/community/interaction-limits-restrictions.md new file mode 100644 index 0000000000000..1be2648d16266 --- /dev/null +++ b/translations/es-ES/data/reusables/community/interaction-limits-restrictions.md @@ -0,0 +1 @@ +Enabling an interaction limit for a repository restricts certain users from commenting, opening issues, creating pull requests, reacting with emojis, editing existing comments, and editing titles of issues and pull requests. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/community/report-content.md b/translations/es-ES/data/reusables/community/report-content.md new file mode 100644 index 0000000000000..8f7965b71b24b --- /dev/null +++ b/translations/es-ES/data/reusables/community/report-content.md @@ -0,0 +1,4 @@ +1. Puedes ver opciones de **Reportar a los administradores del repositorio** o **Reportar abuso al soporte de {% data variables.product.prodname_dotcom %}**. Si no, pasa al siguiente paso. + - Para reportar el contenido al soporte técnico de {% data variables.product.prodname_dotcom %} , haz clic en **Informar de abuso a {% data variables.product.prodname_dotcom %} Soporte**. + - Para reportar el contenido a los mantenedores de repositorio, utiliza el menú desplegable **Escoge una razón** para seleccionar una razón y da clic en **Reportar a los administradores del repositorio**. Tu reporte se ha emitido. ![modal de "Reportar contenido"](/assets/images/help/repository/report-content-modal.png) +2. Complete el formulario de "Reporte de contenido", luego haga clic en **Send Request (Enviar solicitud)**. ![formato de "Reportar contenido"](/assets/images/help/repository/report-content-to-support-form.png) diff --git a/translations/es-ES/data/reusables/community/set-interaction-limit.md b/translations/es-ES/data/reusables/community/set-interaction-limit.md new file mode 100644 index 0000000000000..468a068f7090e --- /dev/null +++ b/translations/es-ES/data/reusables/community/set-interaction-limit.md @@ -0,0 +1 @@ +5. Under "Temporary interaction limits", to the right of the type of interaction limit you want to set, use the **Enable** drop-down menu, then click the duration you want for your interaction limit. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/community/tools-for-moderating.md b/translations/es-ES/data/reusables/community/tools-for-moderating.md new file mode 100644 index 0000000000000..6e1256cf91ec9 --- /dev/null +++ b/translations/es-ES/data/reusables/community/tools-for-moderating.md @@ -0,0 +1 @@ +Cuando ocurre un comportamiento negativo en tu comunidad, {% data variables.product.prodname_dotcom %} ofrece herramientas para aplicar tu código de conducta y desescalar conflictos. Por ejemplo, puedes bloquear una conversación para terminar una discusión acalorada. Para obtener más información, consulta "[Moderando comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" diff --git a/translations/es-ES/data/reusables/community/types-of-interaction-limits.md b/translations/es-ES/data/reusables/community/types-of-interaction-limits.md new file mode 100644 index 0000000000000..e5b58c287ff2b --- /dev/null +++ b/translations/es-ES/data/reusables/community/types-of-interaction-limits.md @@ -0,0 +1,4 @@ +There are three types of interaction limits. + - **Limit to existing users** (Límites para usuarios existentes): Limita la actividad de usuarios con cuentas que tienen menos de 24 horas y que no han realizado contribuciones anteriores ni son colaboradores. + - **Limit to prior contributors**: Limits activity for users who have not previously contributed to the default branch of the repository and are not collaborators. + - **Limit to repository collaborators**: Limits activity for users who do not have write access to the repository. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/dashboard/access-org-dashboard.md b/translations/es-ES/data/reusables/dashboard/access-org-dashboard.md new file mode 100644 index 0000000000000..533540f7f80f0 --- /dev/null +++ b/translations/es-ES/data/reusables/dashboard/access-org-dashboard.md @@ -0,0 +1,2 @@ +1. Para acceder a la página del tablero de control, en la esquina superior izquierda de cualquier página en {% data variables.product.product_name %}, haz clic en el {% octicon "mark-github" aria-label="The github octocat logo" %}. +2. En la esquina superior izquierda de la página, haz clic en tu nombre de usuario y usa el menú desplegable para hacer clic en la organización deseada. ![Menú desplegable del interruptor de contexto del tablero de control que muestra diferentes opciones de organización](/assets/images/help/dashboard/dashboard-context-switcher.png) diff --git a/translations/es-ES/data/reusables/dashboard/recent-activity-qualifying-events.md b/translations/es-ES/data/reusables/dashboard/recent-activity-qualifying-events.md new file mode 100644 index 0000000000000..5371c0b827723 --- /dev/null +++ b/translations/es-ES/data/reusables/dashboard/recent-activity-qualifying-events.md @@ -0,0 +1,8 @@ +Las propuestas y las solicitudes de extracción abiertas aparecen en la sección de actividad reciente cuando: +- Has abierto una propuesta o solicitud de extracción. +- Alguien ha comentado en una propuesta o solicitud de extracción que abriste. +- Tu propuesta o solicitud de extracción fue reabierta. +- Se solicitó tu revisión en una solicitud de extracción. +- Se te asignó a una propuesta o solicitud de extracción. +- Hiciste referencia a una propuesta o solicitud de extracción por medio de un comentario. +- Hiciste un comentario en una propuesta o solicitud de extracción. diff --git a/translations/es-ES/data/reusables/dependabot/automated-tests-note.md b/translations/es-ES/data/reusables/dependabot/automated-tests-note.md new file mode 100644 index 0000000000000..e4b199f98b709 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/automated-tests-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** El tener pruebas automatizadas y procesos de aceptación establecidos para que las verificaciones se lleven a cabo antes de que se fusione la solicitud de extracción se considera como una buena práctica. Esto es particularmente importante si la versión que se sugiere mejorar contiene funcionalidades adicionales o un cambio que infrinja el código de tu proyecto. Para obtener más información acerca de la integración contínua, consulta la sección "[Acerca de la Integración Contínua](/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/dependabot/beta-note-no-link.md b/translations/es-ES/data/reusables/dependabot/beta-note-no-link.md new file mode 100644 index 0000000000000..afcc666f9d89d --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/beta-note-no-link.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Las {% data variables.product.prodname_dependabot_version_updates %} se encuentran actualmente en beta y están sujetas a cambios. Para utilizar la característica del beta, sigue las instrucciones en este artículo. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/dependabot/beta-note.md b/translations/es-ES/data/reusables/dependabot/beta-note.md new file mode 100644 index 0000000000000..f4134b6b55f5c --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Las {% data variables.product.prodname_dependabot_version_updates %} se encuentran actualmente en beta y están sujetas a cambios. Para utilizar la característica del beta, revisa el archivo de configuración para indicar al {% data variables.product.prodname_dependabot %} cuáles dependencias debe mantener para ti. Para obtener más detalles, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)." + +{% endnote %} diff --git a/translations/es-ES/data/reusables/dependabot/check-in-dependabot-yml.md b/translations/es-ES/data/reusables/dependabot/check-in-dependabot-yml.md new file mode 100644 index 0000000000000..4d7884171a983 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/check-in-dependabot-yml.md @@ -0,0 +1 @@ +1. Revisa el archivo de configuración *dependabot.yml* en el directorio `.github` del repositorio. diff --git a/translations/es-ES/data/reusables/dependabot/click-dependabot-tab.md b/translations/es-ES/data/reusables/dependabot/click-dependabot-tab.md new file mode 100644 index 0000000000000..f580ee5b734e5 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/click-dependabot-tab.md @@ -0,0 +1 @@ +4. Debajo de "Gráfica de dependencias", da clic en **{% data variables.product.prodname_dependabot %}**. ![Gráfica de dependencias, pestaña de {% data variables.product.prodname_dependabot %}](/assets/images/help/dependabot/dependabot-tab-beta.png) diff --git a/translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md b/translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md new file mode 100644 index 0000000000000..1128d1c4e89a6 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md @@ -0,0 +1 @@ +1. Crea un archivo de configuración *dependabot.yml*. diff --git a/translations/es-ES/data/reusables/dependabot/default-dependencies-allow-ignore.md b/translations/es-ES/data/reusables/dependabot/default-dependencies-allow-ignore.md new file mode 100644 index 0000000000000..6dbcc67619f26 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/default-dependencies-allow-ignore.md @@ -0,0 +1 @@ +Predeterminadamente, todas las dependencias que se definen explícitamente en un manifiesto o archivo fijado se mantienen actualizadas. Puedes utilizar `allow` e `ignore` para personalizar qué dependencias quieres mantener con las actualizaciones de versión. El {% data variables.product.prodname_dependabot %} revisa las dependencias permitidas y después filtra cualquier dependencia o versión ignorada. Así que se ignorará cualquier dependencia que empate tanto con `allow` como con `ignore`. diff --git a/translations/es-ES/data/reusables/dependabot/default-labels.md b/translations/es-ES/data/reusables/dependabot/default-labels.md new file mode 100644 index 0000000000000..ac4b7d1b7d03c --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/default-labels.md @@ -0,0 +1 @@ +Predeterminadamente, el {% data variables.product.prodname_dependabot %} levanta todas las solicitudes de extracción con la etiqueta `dependencies`. Si se define más de un administrador de paquetes, {% data variables.product.prodname_dependabot %} incluye una etiqueta adicional en cada una de las solicitudes de extracción. Esto indica qué lenguaje o ecosistema actualizará la solicitud de extracción, por ejemplo: `java` para las actualizaciones de Gradle `submodules` para las actualizaciones de los submódulos de git. El {% data variables.product.prodname_dependabot %} crea estas etiquetas predeterminadas automáticamente, de acuerdo lo necesite tu repositorio. diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-tos.md b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md new file mode 100644 index 0000000000000..d3534c1f42499 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md @@ -0,0 +1 @@ +En las [Condiciones de Servicio de {% data variables.product.prodname_dotcom %}](/github/site-policy/github-terms-of-service) se incluyen al {% data variables.product.prodname_dependabot %} y a todas sus características relacionadas. diff --git a/translations/es-ES/data/reusables/dependabot/initial-updates.md b/translations/es-ES/data/reusables/dependabot/initial-updates.md new file mode 100644 index 0000000000000..a23ab3b3790a1 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/initial-updates.md @@ -0,0 +1,3 @@ +Cuando habilitas las actualizaciones de versión por primera vez, podrías tener muchas dependencias desactualizadas y algunas podrían estar varias versiones debajo de la última. {% data variables.product.prodname_dependabot %} verifica las dependencias que estén desactualizadas tan pronto se habilita. Podrías ver nuevas solicitudes de extracción para las actualizaciones de versión después de algunos minutos de haber agregado el archivo de configuración, dependiendo de la cantidad de archivos de manifiesto para los cuales configuras las actualizaciones. + +Para mantener la fácil administración y revisión de las solicitudes de extracción, {% data variables.product.prodname_dependabot %} levanta un máximo de cinco solicitudes de extracción para comenzar a actualizar a las dependencias a su versión más reciente. Si fusionas algunas de estas primeras solicitudes de extracción antes de la siguiente actualización programada, entonces se abrirá un máximo de cinco solicitudes para todas aquellas subsecuentes (puedes cambiar este límite). diff --git a/translations/es-ES/data/reusables/dependabot/option-affects-security-updates.md b/translations/es-ES/data/reusables/dependabot/option-affects-security-updates.md new file mode 100644 index 0000000000000..9ab403e86596f --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/option-affects-security-updates.md @@ -0,0 +1 @@ +Configurar esta opción también afectará a las solicitudes de extracción para las actualizaciones de seguridad en los archivos de manifiesto de este administrador de paquete, a menos de que utilices `target-branch` para revisar las actualizaciones de versión en una rama diferente a la predeterminada. diff --git a/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md b/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000000..d851421ae990b --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". + +Actualmente, las actualizaciones de versión del {% data variables.product.prodname_dependabot %} no soportan archivos de bloqueo o de manifiesto que contengan dependencias hospedadas en registros privados, o en repositorios privados de {% data variables.product.prodname_dotcom %}, los cuales pertenezcan a una organización diferente a la del proyecto dependiente. diff --git a/translations/es-ES/data/reusables/dependabot/private-dependencies.md b/translations/es-ES/data/reusables/dependabot/private-dependencies.md new file mode 100644 index 0000000000000..7e28a5d989fc8 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/private-dependencies.md @@ -0,0 +1 @@ +Actualmente, {% data variables.product.prodname_dependabot_version_updates %} no son compatibles con archivos de bloqueo o de manifiesto que contengan dependencias o registros de git privados. Esto es porque, cuando se ejecutan las actualizaciones de versión, {% data variables.product.prodname_dependabot %} debe poder resolver todas las dependencias de su fuente para verificar que dichas actualizaciones de versión hayan sido exitosas. diff --git a/translations/es-ES/data/reusables/dependabot/pull-request-introduction.md b/translations/es-ES/data/reusables/dependabot/pull-request-introduction.md new file mode 100644 index 0000000000000..a10b452d8e07b --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/pull-request-introduction.md @@ -0,0 +1 @@ +El {% data variables.product.prodname_dependabot %} levanta solicitudes de extracción para actualizar las dependencias. Dependiendo de cómo se configure tu repositorio, el {% data variables.product.prodname_dependabot %} podría levantar solicitudes de extracción para las actualizaciones de versión y/o para las alertas de seguridad. Administrarás estas solicitudes de la misma forma que cualquier otra solicitud de extracción, pero también hay comandos extra disponibles. Para obtener más información sobre cómo habilitar las actualizaciones de dependencias del {% data variables.product.prodname_dependabot %}, consulta las secciones "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)" y "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md new file mode 100644 index 0000000000000..446e1861de13f --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md @@ -0,0 +1,34 @@ +La siguiente tabla muestra, para cada administrador de paquete, si el {% data variables.product.prodname_dependabot %} soporta: dependencias en repositorios privados de {% data variables.product.prodname_dotcom %} y dependencias delegadas. + +| Administración de paquetes | Repositorios privados de {% data variables.product.prodname_dotcom %} | Delegamiento a proveedores | +| -------------------------------- |:---------------------------------------------------------------------:|:--------------------------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| git submodule: `gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Go modules: `gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | + +{% note %} + +**Nota**: {% data variables.product.prodname_dependabot %} también es compatible con los siguientes administradores de paquetes: + +-`yarn` (solo v1) (especificar `npm`) + +-Archivos de `.gradle.kts`, para proyectos de Kotlin (especificar `gradle`) + +-`pipenv`, `pip-compile`, y `poetry` (especificar `pip`) + +Por ejemplo, si utilizas `poetry` para administrar tus dependencias de Python y quieres que el {% data variables.product.prodname_dependabot %} monitoree el archivo de manifiesto de tu dependencia para encontrar versiones nuevas, utiliza `package-ecosystem: "pip"` en tu archivo de *dependabot.yml*. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/dependabot/version-updates-for-actions.md b/translations/es-ES/data/reusables/dependabot/version-updates-for-actions.md new file mode 100644 index 0000000000000..10905155df913 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/version-updates-for-actions.md @@ -0,0 +1 @@ +También puedes habilitar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones que agregas a tu flujo de trabajo. Para obtener más información, consulta la sección "[Mantener tus acciones actualizadas con el {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot)". diff --git a/translations/es-ES/data/reusables/dependabot/warning-ignore-option.md b/translations/es-ES/data/reusables/dependabot/warning-ignore-option.md new file mode 100644 index 0000000000000..a3b9cc0382a25 --- /dev/null +++ b/translations/es-ES/data/reusables/dependabot/warning-ignore-option.md @@ -0,0 +1,7 @@ +{% warning %} + +**Advertencia**: Antes de que agregues una opción de `ignore` al archivo de configuración *dependabot.yml*, revisa si el repositorio ya tiene alguna preferencia de ignorar (Que se haya creado utilizando los comandos de `@dependabot ignore`). Cuando agregas una opción de `ignore` al archivo de configuración *dependabot.yml*, esto ignora cualquier preferencia de ignorar almacenada centralmente para ese administrador de paquetes, rama, y directorio. + +Esto afecta a las actualizaciones tanto de seguridad como de versión. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/desktop/2fa-in-browser.md b/translations/es-ES/data/reusables/desktop/2fa-in-browser.md new file mode 100644 index 0000000000000..95f254e0c50af --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/2fa-in-browser.md @@ -0,0 +1,5 @@ +1. Si has configurado la autenticación de dos factores (2FA) para {% data variables.product.prodname_dotcom %}, realiza una de las siguientes acciones: + - Si configuras 2FA por medio de SMS, recupera tu código 2FA de un mensaje SMS. + - Si configuras 2FA con una aplicación TOTP, genera un código 2FA. + + Ingresa entonces tu código de 2FA en el mensaje de {% data variables.product.prodname_dotcom %} y da clic en **Verificar**. ![El campo de código de autenticación 2FA](/assets/images/help/desktop/2fa-code-field.png) diff --git a/translations/es-ES/data/reusables/desktop/about-github-desktop.md b/translations/es-ES/data/reusables/desktop/about-github-desktop.md new file mode 100644 index 0000000000000..e9a8b75f90431 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/about-github-desktop.md @@ -0,0 +1,7 @@ +{% data variables.product.prodname_desktop %} es una herramienta de código abierto que te permite ser más productivo. {% data variables.product.prodname_desktop %} fomenta que tú y tu equipo colaboren utilizando las mejoras prácticas con Git y {% data variables.product.prodname_dotcom %}. + +Ésto es solo una parte de lo mucho que puedes hacer con {% data variables.product.prodname_desktop %}: +- Añadir cambios a tu confirmación de forma interactiva +- Añadir co-autores rápidamente en tu confirmación +- Controlar ramas con solicitudes de extracción y ver los estados de CI +- Comparar las imágenes que han cambiado diff --git a/translations/es-ES/data/reusables/desktop/authenticate-in-browser.md b/translations/es-ES/data/reusables/desktop/authenticate-in-browser.md new file mode 100644 index 0000000000000..a1a7f9151fe47 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/authenticate-in-browser.md @@ -0,0 +1,3 @@ +1. Para autenticarte en {% data variables.product.prodname_dotcom %}, escribe tus credenciales de {% data variables.product.prodname_dotcom %}.com y haz clic en **Sign in (Iniciar sesión)**. ![El botón de Inicio de sesión para {% data variables.product.prodname_dotcom %} en el navegador](/assets/images/help/desktop/sign-in-button-browser.png) + + Como alternativa, si ya hubieras iniciado sesión en {% data variables.product.prodname_dotcom %}, sigue los mensajes para regresar a {% data variables.product.prodname_desktop %} y así completar la autenticación. diff --git a/translations/es-ES/data/reusables/desktop/choose-a-branch-to-merge.md b/translations/es-ES/data/reusables/desktop/choose-a-branch-to-merge.md new file mode 100644 index 0000000000000..8eaebf8d991c9 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-a-branch-to-merge.md @@ -0,0 +1 @@ +1. Haz clic en **Choose a branch to merge into (Elige una rama para fusionarse en) BRANCH**. ![Elige una opción de rama en la lista de menús de ramas](/assets/images/help/desktop/merge-branch-button-list.png) diff --git a/translations/es-ES/data/reusables/desktop/choose-a-theme.md b/translations/es-ES/data/reusables/desktop/choose-a-theme.md new file mode 100644 index 0000000000000..1a29152be299f --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-a-theme.md @@ -0,0 +1,2 @@ +3. Haz clic en **Appearance (Apariencia)**. +4. Haz clic en el tema que quieres usar. Opcionalmente, puedes seleccionar **Cambiar de tema automáticamente para coincidir con el sistema** si quieres que {% data variables.product.prodname_desktop %} siempre haga coincidir el tema con tu computador. diff --git a/translations/es-ES/data/reusables/desktop/choose-clone-repository.md b/translations/es-ES/data/reusables/desktop/choose-clone-repository.md new file mode 100644 index 0000000000000..60d3ab7a9c992 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-clone-repository.md @@ -0,0 +1 @@ +1. En el menú **File (Archivo)** haz clic en **Clone Repository (Clonar repositorio)**. diff --git a/translations/es-ES/data/reusables/desktop/choose-pr-from-list.md b/translations/es-ES/data/reusables/desktop/choose-pr-from-list.md new file mode 100644 index 0000000000000..70430fb0f8631 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-pr-from-list.md @@ -0,0 +1 @@ +1. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas visualizar. diff --git a/translations/es-ES/data/reusables/desktop/choose-product-authenticate.md b/translations/es-ES/data/reusables/desktop/choose-product-authenticate.md new file mode 100644 index 0000000000000..1cb028f54f552 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-product-authenticate.md @@ -0,0 +1 @@ +1. A la derecha de "{% data variables.product.prodname_enterprise %} Server", da clic en **Iniciar sesión**. ![El botón de Iniciar sesión para GitHub Enterprise Server](/assets/images/help/desktop/sign-in-ghes.png) diff --git a/translations/es-ES/data/reusables/desktop/click-base-branch-in-drop-down.md b/translations/es-ES/data/reusables/desktop/click-base-branch-in-drop-down.md new file mode 100644 index 0000000000000..e66a1e5be2804 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/click-base-branch-in-drop-down.md @@ -0,0 +1 @@ +1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego, en la lista de ramas, da clic en aquella que quieras sea la base de tu nueva rama. diff --git a/translations/es-ES/data/reusables/desktop/click-discard-files.md b/translations/es-ES/data/reusables/desktop/click-discard-files.md new file mode 100644 index 0000000000000..bc8a11da9cf0f --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/click-discard-files.md @@ -0,0 +1 @@ +1. Haz clic en **Discard Changes (Descartar cambios)** o **Discard Selected Changes (Descartar cambios seleccionados)** para descartar cambios a uno o más archivos, o **Discard All Changes (Descartar todos los cambios)** para descartar cambios a todos los archivos desde la última confirmación. diff --git a/translations/es-ES/data/reusables/desktop/click-pull-requests.md b/translations/es-ES/data/reusables/desktop/click-pull-requests.md new file mode 100644 index 0000000000000..fadac59c33253 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/click-pull-requests.md @@ -0,0 +1 @@ +1. En la parte superior del menú desplegable, haz clic en **Pull Requests (Solicitudes de extracción)**. diff --git a/translations/es-ES/data/reusables/desktop/click-save-git-config.md b/translations/es-ES/data/reusables/desktop/click-save-git-config.md new file mode 100644 index 0000000000000..5dc31757ca3be --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/click-save-git-config.md @@ -0,0 +1 @@ +1. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/data/reusables/desktop/cloning-location-tab.md b/translations/es-ES/data/reusables/desktop/cloning-location-tab.md new file mode 100644 index 0000000000000..c8253e626787c --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/cloning-location-tab.md @@ -0,0 +1 @@ +1. Haz clic en la pestaña que corresponde a la ubicación del repositorio que deseas clonar. También puedes hacer clic en **URL** para introducir manualmente la ubicación del repositorio. diff --git a/translations/es-ES/data/reusables/desktop/cloning-repository-list.md b/translations/es-ES/data/reusables/desktop/cloning-repository-list.md new file mode 100644 index 0000000000000..98054b13f694b --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/cloning-repository-list.md @@ -0,0 +1 @@ +1. Elige dentro de la lista el repositorio que deseas clonar. diff --git a/translations/es-ES/data/reusables/desktop/commit-all-desc.md b/translations/es-ES/data/reusables/desktop/commit-all-desc.md new file mode 100644 index 0000000000000..cce9ee7ca1a86 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/commit-all-desc.md @@ -0,0 +1 @@ +Para agregar **todos los cambios en todos los archivos** en una única confirmación, mantén seleccionada la casilla de verificación que aparece en la parte superior de la lista seleccionada. diff --git a/translations/es-ES/data/reusables/desktop/commit-button.md b/translations/es-ES/data/reusables/desktop/commit-button.md new file mode 100644 index 0000000000000..7e4778a0dd515 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/commit-button.md @@ -0,0 +1 @@ +1. Dentro del campo Description (Descripción), haz clic en **Commit to (Confirmar a)BRANCH**. diff --git a/translations/es-ES/data/reusables/desktop/commit-message.md b/translations/es-ES/data/reusables/desktop/commit-message.md new file mode 100644 index 0000000000000..fe80032afa466 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/commit-message.md @@ -0,0 +1 @@ +1. En la parte inferior de la lista de cambios, en el campo Summary (Resumen), escribe un mensaje de confirmación corto y significativo. De forma opcional, puedes añadir más información sobre el cambio en el campo Description (Descripción). diff --git a/translations/es-ES/data/reusables/desktop/commit-some-desc.md b/translations/es-ES/data/reusables/desktop/commit-some-desc.md new file mode 100644 index 0000000000000..6f04a0cb29f4c --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/commit-some-desc.md @@ -0,0 +1 @@ +Para agregar **todos los cambios en uno o más archivos** en una confirmación única, quita la marca de selección de las casillas de verificación que se encuentran junto a los archivos que no deseas incluir y deja seleccionados solamente los archivos que deseas incluir en la confirmación. Puedes cambiar la casilla de verificación con las teclas `Barra espaciadora` o `Enter` después de seleccionar un archivo. diff --git a/translations/es-ES/data/reusables/desktop/confirm-discard-files.md b/translations/es-ES/data/reusables/desktop/confirm-discard-files.md new file mode 100644 index 0000000000000..8ae2526ef1e85 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/confirm-discard-files.md @@ -0,0 +1 @@ +1. Para confirmar los cambios, revisa los archivos afectados y haz clic en **Discard Changes (Descartar cambios)**. diff --git a/translations/es-ES/data/reusables/desktop/confirm-merging-branch.md b/translations/es-ES/data/reusables/desktop/confirm-merging-branch.md new file mode 100644 index 0000000000000..98b794a67cd4e --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/confirm-merging-branch.md @@ -0,0 +1 @@ +1. Haz clic en la rama que deseas fusionar en la rama actual y luego haz clic en **Merge (Fusionar) BRANCH en BRANCH**. diff --git a/translations/es-ES/data/reusables/desktop/confirm-new-branch-button.md b/translations/es-ES/data/reusables/desktop/confirm-new-branch-button.md new file mode 100644 index 0000000000000..ab607c196f9f8 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/confirm-new-branch-button.md @@ -0,0 +1 @@ +1. Haz clic en **Create Branch (Crear rama)**. diff --git a/translations/es-ES/data/reusables/desktop/confirm-tag.md b/translations/es-ES/data/reusables/desktop/confirm-tag.md new file mode 100644 index 0000000000000..e6fe5f975a1e7 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/confirm-tag.md @@ -0,0 +1 @@ +1. Da clic en **Crear etiqueta**. diff --git a/translations/es-ES/data/reusables/desktop/copy-email-git-config.md b/translations/es-ES/data/reusables/desktop/copy-email-git-config.md new file mode 100644 index 0000000000000..ba04ce0d0b41c --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/copy-email-git-config.md @@ -0,0 +1 @@ +1. Copia la dirección de correo electrónico que deseas usar en tu configuración local de Git. diff --git a/translations/es-ES/data/reusables/desktop/create-new-branch.md b/translations/es-ES/data/reusables/desktop/create-new-branch.md new file mode 100644 index 0000000000000..9b63a250e1ffe --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/create-new-branch.md @@ -0,0 +1 @@ +1. Haz clic en **New Branch (Nueva rama)**. diff --git a/translations/es-ES/data/reusables/desktop/create-tag.md b/translations/es-ES/data/reusables/desktop/create-tag.md new file mode 100644 index 0000000000000..ca2dec5ab2b7b --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/create-tag.md @@ -0,0 +1 @@ +1. Da clic derecho en la confirmación y da clic en **Crear Etiqueta...**. ![Selecciona el elemento de menú de crear etiqueta](/assets/images/help/desktop/select-create-tag.png) diff --git a/translations/es-ES/data/reusables/desktop/current-branch-menu.md b/translations/es-ES/data/reusables/desktop/current-branch-menu.md new file mode 100644 index 0000000000000..78b229867d6a6 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/current-branch-menu.md @@ -0,0 +1 @@ +1. En {% data variables.product.prodname_desktop %}, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual**. ![Menú desplegable de la rama actual](/assets/images/help/desktop/current-branch-menu.png) diff --git a/translations/es-ES/data/reusables/desktop/delete-branch-mac.md b/translations/es-ES/data/reusables/desktop/delete-branch-mac.md new file mode 100644 index 0000000000000..9e02fa64a1076 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/delete-branch-mac.md @@ -0,0 +1 @@ +1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar shift⌘ commandD. diff --git a/translations/es-ES/data/reusables/desktop/delete-branch-win.md b/translations/es-ES/data/reusables/desktop/delete-branch-win.md new file mode 100644 index 0000000000000..3986b153f3762 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/delete-branch-win.md @@ -0,0 +1 @@ +1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar CtrlShiftD. diff --git a/translations/es-ES/data/reusables/desktop/download-desktop-page.md b/translations/es-ES/data/reusables/desktop/download-desktop-page.md new file mode 100644 index 0000000000000..04698cd4b1f20 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/download-desktop-page.md @@ -0,0 +1 @@ +1. Visita la [página de descargas para {% data variables.product.prodname_desktop %} ](https://desktop.github.com/). diff --git a/translations/es-ES/data/reusables/desktop/get-an-account.md b/translations/es-ES/data/reusables/desktop/get-an-account.md new file mode 100644 index 0000000000000..6b37dbbd5c01f --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/get-an-account.md @@ -0,0 +1,4 @@ +debes contar previamente con una cuenta de {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. + +- Para obtener más información sobre crear una cuenta de {% data variables.product.prodname_dotcom %}, consulta "[Registrar una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account/)". +- Para una cuenta de {% data variables.product.prodname_enterprise %}, contacta a tu administrador de sitio de {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-ES/data/reusables/desktop/history-tab.md b/translations/es-ES/data/reusables/desktop/history-tab.md new file mode 100644 index 0000000000000..6be245bc91503 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/history-tab.md @@ -0,0 +1 @@ +1. Haz clic en **History (Historial)**. ![La pestaña de historial seleccionada en la barra lateral](/assets/images/help/desktop/history-tab-in-commit-sidebar.png) diff --git a/translations/es-ES/data/reusables/desktop/launch-desktop-from-command-line.md b/translations/es-ES/data/reusables/desktop/launch-desktop-from-command-line.md new file mode 100644 index 0000000000000..9fc2b2eb7412c --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/launch-desktop-from-command-line.md @@ -0,0 +1 @@ +Para iniciar {% data variables.product.prodname_desktop %} al último repositorio abierto, escribe `github`. Para lanzar {% data variables.product.prodname_desktop %} para un repositorio particular, teclea `github` seguido de la ruta al repositorio. diff --git a/translations/es-ES/data/reusables/desktop/mac-select-accounts.md b/translations/es-ES/data/reusables/desktop/mac-select-accounts.md new file mode 100644 index 0000000000000..1b14eebe3ec9f --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/mac-select-accounts.md @@ -0,0 +1 @@ +1. En la ventana Preferences (Preferencias), selecciona **Accounts (Cuentas)**. ![El panel Accounts (Cuentas) en la ventana Preferences (Preferencias)](/assets/images/help/desktop/mac-select-accounts-pane.png) diff --git a/translations/es-ES/data/reusables/desktop/mac-select-desktop-menu.md b/translations/es-ES/data/reusables/desktop/mac-select-desktop-menu.md new file mode 100644 index 0000000000000..d7ab57dd6689a --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/mac-select-desktop-menu.md @@ -0,0 +1 @@ +1. En la barra de menú, utiliza el menú desplegable de **{% data variables.product.prodname_desktop %}** y luego da clic en **Preferencias**. ![El valor de preferencias en el menú desplegable de {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-choose-preferences.png) diff --git a/translations/es-ES/data/reusables/desktop/make-changes.md b/translations/es-ES/data/reusables/desktop/make-changes.md new file mode 100644 index 0000000000000..d0f6c36d52608 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/make-changes.md @@ -0,0 +1 @@ +1. Usando tu editor de texto favorito, por ejemplo, [Atom](https://atom.io/), realiza los cambios necesarios en los archivos de tu proyecto. diff --git a/translations/es-ES/data/reusables/desktop/name-branch.md b/translations/es-ES/data/reusables/desktop/name-branch.md new file mode 100644 index 0000000000000..b39e6aa4eca64 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/name-branch.md @@ -0,0 +1 @@ +1. Dentro de **Name (Nombre)**, escribe el nombre de la nueva rama. diff --git a/translations/es-ES/data/reusables/desktop/name-field-git-config.md b/translations/es-ES/data/reusables/desktop/name-field-git-config.md new file mode 100644 index 0000000000000..4e879a099f819 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/name-field-git-config.md @@ -0,0 +1 @@ +1. En el campo **Name (Nombre)**, ingresa el nombre que deseas usar para tu configuración Git. diff --git a/translations/es-ES/data/reusables/desktop/name-tag.md b/translations/es-ES/data/reusables/desktop/name-tag.md new file mode 100644 index 0000000000000..35b951fb624cb --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/name-tag.md @@ -0,0 +1 @@ +1. Teclea el nombre de la etiqueta. ![Ingresa un nombre de eitqueta](/assets/images/help/desktop/enter-tag-name.png) diff --git a/translations/es-ES/data/reusables/desktop/paste-email-git-config.md b/translations/es-ES/data/reusables/desktop/paste-email-git-config.md new file mode 100644 index 0000000000000..78c2fb9528787 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/paste-email-git-config.md @@ -0,0 +1 @@ +1. En el campo **Email (Correo electrónico)**, pega la dirección de correo electrónico que copiaste de los parámetros de tu cuenta de {% data variables.product.prodname_dotcom %} o de {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-ES/data/reusables/desktop/preferences-options-tabs.md b/translations/es-ES/data/reusables/desktop/preferences-options-tabs.md new file mode 100644 index 0000000000000..d86faedbf6043 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/preferences-options-tabs.md @@ -0,0 +1,5 @@ + - Elige **Accounts** (Cuentas) para agregar o quitar una cuenta {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. + - Elija **Integrations (Integraciones)** para elegir un editor o shell. + - Elige **Git** para editar tu configuración de Git. + - Elige **Appearance (Apariencia)** para cambiar entre el tema claro u oscuro. + - Elige **Advanced** (Avanzado) para más opciones de configuración. diff --git a/translations/es-ES/data/reusables/desktop/protected-branches.md b/translations/es-ES/data/reusables/desktop/protected-branches.md new file mode 100644 index 0000000000000..94dd074d3c9d9 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/protected-branches.md @@ -0,0 +1 @@ +Los administradores de un repositorio pueden activar las protecciones en una rama. Si estás trabajando en una rama que está protegida, no podrás eliminar ni hacer un empuje forzado a la rama. Los administradores de repositorio pueden habilitar otras configuraciones de la rama protegida para requerir ciertos flujos de trabajo antes de que la rama se pueda fusionar. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". diff --git a/translations/es-ES/data/reusables/desktop/publish-repository.md b/translations/es-ES/data/reusables/desktop/publish-repository.md new file mode 100644 index 0000000000000..50312d51cee8b --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/publish-repository.md @@ -0,0 +1 @@ +3. Haz clic en el botón **Publish Repository (Publicar repositorio)** en la barra de herramientas. ![El botón Publicar repositorio en la barra de herramientas](/assets/images/help/desktop/publish-repository-toolbar-button.png) diff --git a/translations/es-ES/data/reusables/desktop/push-origin.md b/translations/es-ES/data/reusables/desktop/push-origin.md new file mode 100644 index 0000000000000..22ade305c84f7 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/push-origin.md @@ -0,0 +1 @@ +1. Da clic en **Cargar al origen** para cargar tus cambios locales al repositorio remoto. ![El botón Subir](/assets/images/help/desktop/push-origin-button.png) diff --git a/translations/es-ES/data/reusables/desktop/resolve-merge-conflicts.md b/translations/es-ES/data/reusables/desktop/resolve-merge-conflicts.md new file mode 100644 index 0000000000000..24f5e7b0ccb3c --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/resolve-merge-conflicts.md @@ -0,0 +1 @@ +1. Resuelve cualquier conflicto de fusión que se produzca de la manera que prefieras, usando un editor de texto, la línea de comando o cualquier otra herramienta. Para obtener más información, consulta "[Abordar conflictos de fusión](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)." diff --git a/translations/es-ES/data/reusables/desktop/retrieve-2fa.md b/translations/es-ES/data/reusables/desktop/retrieve-2fa.md new file mode 100644 index 0000000000000..aa437467afd04 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/retrieve-2fa.md @@ -0,0 +1,5 @@ +1. Si has configurado la autenticación de dos factores para {% data variables.product.prodname_enterprise %}, realiza una de las siguientes acciones: + - Si configuras 2FA por medio de SMS, recupera tu código 2FA de un mensaje SMS. + - Si configuras 2FA con una aplicación TOTP, genera un código 2FA. + + Ingresa entonces tu código de 2FA en el mensaje de {% data variables.product.prodname_desktop %} y da clic en **Iniciar Sesión**. ![El campo de código de autenticación 2FA](/assets/images/help/desktop/mac-2fa-code-prompt.png) diff --git a/translations/es-ES/data/reusables/desktop/return-to-desktop.md b/translations/es-ES/data/reusables/desktop/return-to-desktop.md new file mode 100644 index 0000000000000..e42a6e3d5bb07 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/return-to-desktop.md @@ -0,0 +1 @@ +1. Regresa a {% data variables.product.prodname_desktop %}. diff --git a/translations/es-ES/data/reusables/desktop/revert-commit.md b/translations/es-ES/data/reusables/desktop/revert-commit.md new file mode 100644 index 0000000000000..aa41833c4dae9 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/revert-commit.md @@ -0,0 +1 @@ +1. Da clic derecho en la confirmación que quieras revertir y da clic en **Revertir esta confirmación**. diff --git a/translations/es-ES/data/reusables/desktop/select-base-branch.md b/translations/es-ES/data/reusables/desktop/select-base-branch.md new file mode 100644 index 0000000000000..fe7334f8d6a59 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/select-base-branch.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable para elegir una rama base para tu rama nueva. diff --git a/translations/es-ES/data/reusables/desktop/select-branch-to-delete.md b/translations/es-ES/data/reusables/desktop/select-branch-to-delete.md new file mode 100644 index 0000000000000..6ddbfa764632a --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/select-branch-to-delete.md @@ -0,0 +1 @@ +1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego en la rama que quieres borrar. diff --git a/translations/es-ES/data/reusables/desktop/select-discard-files.md b/translations/es-ES/data/reusables/desktop/select-discard-files.md new file mode 100644 index 0000000000000..354a9bed235f1 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/select-discard-files.md @@ -0,0 +1 @@ +1. En la lista de archivos cambiados, selecciona los archivos en los que deseas descartar los cambios desde la última confirmación. Para seleccionar varios archivos, haz clic en `shift` y haz clic en el rango de archivos desde los que deseas descartar los cambios. ![Selecciona varios archivos con cambios a descartar](/assets/images/help/desktop/select-multiple-files-discard.png) diff --git a/translations/es-ES/data/reusables/desktop/sign-in-choose-product.md b/translations/es-ES/data/reusables/desktop/sign-in-choose-product.md new file mode 100644 index 0000000000000..d18944196a3d6 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/sign-in-choose-product.md @@ -0,0 +1 @@ +1. Inicia sesión en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-ES/data/reusables/desktop/switching-between-branches.md b/translations/es-ES/data/reusables/desktop/switching-between-branches.md new file mode 100644 index 0000000000000..3922ebe8ed759 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/switching-between-branches.md @@ -0,0 +1 @@ +1. Dentro de la lista de ramas, haz clic en la rama a la que deseas cambiar para continuar. diff --git a/translations/es-ES/data/reusables/desktop/tags-push-with-commits.md b/translations/es-ES/data/reusables/desktop/tags-push-with-commits.md new file mode 100644 index 0000000000000..ef3164e5970b2 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/tags-push-with-commits.md @@ -0,0 +1 @@ +Predeterminadamente, {% data variables.product.prodname_desktop %} cargará la etiqueta que creaste a tu repositorio con la confirmación asociada. diff --git a/translations/es-ES/data/reusables/desktop/update-email-address.md b/translations/es-ES/data/reusables/desktop/update-email-address.md new file mode 100644 index 0000000000000..79aed74fcdb54 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/update-email-address.md @@ -0,0 +1 @@ +Si las confirmaciones que haces en {% data variables.product.prodname_desktop %} se asocian con la cuenta incorrecta de {% data variables.product.product_name %}, actualiza la dirección de correo electrónico en tu configuración de Git utilizando {% data variables.product.prodname_desktop %}. diff --git a/translations/es-ES/data/reusables/desktop/windows-choose-options.md b/translations/es-ES/data/reusables/desktop/windows-choose-options.md new file mode 100644 index 0000000000000..2bc077e1a288a --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/windows-choose-options.md @@ -0,0 +1 @@ +1. Utiliza el menú de **Archivo** y luego da clic en **Opciones**. ![El valor de Opciones en el menú desplegable de Configuración](/assets/images/help/desktop/windows-choose-options.png) diff --git a/translations/es-ES/data/reusables/desktop/windows-select-accounts.md b/translations/es-ES/data/reusables/desktop/windows-select-accounts.md new file mode 100644 index 0000000000000..f24767759f755 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/windows-select-accounts.md @@ -0,0 +1 @@ +1. En la ventana de Opciones, selecciona **Accounts (Cuentas)**. ![El panel Accounts (Cuentas) en la ventana de Opciones](/assets/images/help/desktop/windows-select-accounts-pane.png) diff --git a/translations/es-ES/data/reusables/desktop/windows_git_bash.md b/translations/es-ES/data/reusables/desktop/windows_git_bash.md new file mode 100644 index 0000000000000..075f6353ff966 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/windows_git_bash.md @@ -0,0 +1 @@ +Si tienes [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) instalado, puedes usarlo para clonar repositorios y no manejar claves SSH. diff --git a/translations/es-ES/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md b/translations/es-ES/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md new file mode 100644 index 0000000000000..988b9dab3228b --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md @@ -0,0 +1,6 @@ +**Si estás usando Git Bash**, activa el ssh-agent: +```shell +# inicia el ssh-agent en segundo plano +$ eval "$(ssh-agent -s)" +> Agent pid 59566 +``` diff --git a/translations/es-ES/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md b/translations/es-ES/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md new file mode 100644 index 0000000000000..56513a39499b7 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md @@ -0,0 +1,6 @@ +**Si estás usando otro símbolo de terminal**, como [Git para Windows](https://git-for-windows.github.io/), activa el ssh-agent: +```shell +# start the ssh-agent in the background +$ eval $(ssh-agent -s) +> Agent pid 59566 +``` diff --git a/translations/es-ES/data/reusables/developer-site/limit_workflow_to_activity_types.md b/translations/es-ES/data/reusables/developer-site/limit_workflow_to_activity_types.md new file mode 100644 index 0000000000000..0513106c90249 --- /dev/null +++ b/translations/es-ES/data/reusables/developer-site/limit_workflow_to_activity_types.md @@ -0,0 +1 @@ +Por defecto, todos los tipos de actividad desencadenan un flujo de trabajo a ejecutarse. Puedes limitar tus ejecuciones de flujo de trabajo a tipos de actividad específicos usando la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". diff --git a/translations/es-ES/data/reusables/developer-site/multiple_activity_types.md b/translations/es-ES/data/reusables/developer-site/multiple_activity_types.md new file mode 100644 index 0000000000000..a3485ab600f34 --- /dev/null +++ b/translations/es-ES/data/reusables/developer-site/multiple_activity_types.md @@ -0,0 +1 @@ +Más de un tipo de actividad desencadena este evento. diff --git a/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md new file mode 100644 index 0000000000000..67af6685d0fb0 --- /dev/null +++ b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -0,0 +1,13 @@ +##### Eventos de solicitud de extracción para repositorios bifurcados + +{% note %} + +**Nota:** los flujos de trabajo no se ejecutan en repositorios base privados cuando abres una solicitud de extracción desde un repositorio bifurcado. + +{% endnote %} + +Cuando creas una solicitud de extracción desde un repositorio bifurcado al repositorio base, {% data variables.product.prodname_dotcom %} envía el evento `pull_request` al repositorio base y no se producen eventos de solicitud de extracción en el repositorio bifurcado. + +Los flujos de trabajo no se ejecutan en repositorios bifurcados por defecto. Debes habilitar las Acciones de GitHub en la pestaña **Actions (Acciones)** del repositorio bifurcado. + +{% data reusables.actions.forked-secrets %} Los permisos para el `GITHUB_TOKEN` en los repositorios bifurcados son de solo lectura. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". diff --git a/translations/es-ES/data/reusables/discussions/about-categories-and-formats.md b/translations/es-ES/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000000..9b4aaaa3eb8de --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +Todos los debates deben crearse en una categoría y los administradores de repositorio y mantenedores definen las categorías de un repositorio. Las categorías pueden contener conversaciones abiertas o conversaciones con un formato de pregunta/respuesta. diff --git a/translations/es-ES/data/reusables/discussions/about-discussions.md b/translations/es-ES/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000000..6d72db4134578 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Los debates son un foro abierto para tener conversaciones entre los mantenedores y la comunidad de un proyecto en {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/discussions/beta.md b/translations/es-ES/data/reusables/discussions/beta.md new file mode 100644 index 0000000000000..573c472e0cf45 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** {% data variables.product.prodname_discussions %} se encuentra acutalmente en beta y está sujeto a cambios. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/discussions/click-discussion-in-list.md b/translations/es-ES/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000000..59d79b9e81eca --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. En la lista de debates, da clic en el debate que quieras ver. ![Debate en la lista de debates de un repositorio](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/es-ES/data/reusables/discussions/discussions-tab.md b/translations/es-ES/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000000..d4f9982958e46 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de repositorio, da clic en {% octicon "comment-discussion" aria-label="The discussion icon" %} **Debates**. ![Pestaña de "Debates" en un repositorio](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/es-ES/data/reusables/discussions/edit-categories.md b/translations/es-ES/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000000..7102f65ad13aa --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. A la derecha de "Categorías", da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Icono de lápiz para editar las categorías](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/es-ES/data/reusables/discussions/edit-category-details.md b/translations/es-ES/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000000..2f8ecffa202d8 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edita el emoji, título, descripción y formato del debate para la categoría. Para obtener más información sobre los formatos de debate, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". diff --git a/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000000..c771e82c50527 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +Puedes habilitar o inhabilitar los debates para un repositorio. + +{% data reusables.repositories.navigate-to-repo %} +1. Debajo de tu nombre de repositorio, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Botón de configuración del repositorio](/assets/images/help/discussions/public-repo-settings.png) +1. Debajo de "Características", selecciona **Debates**. ![La casilla de verificación debajo de "Características" para habilitar o inhabilitar los debates de un repositorio](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/es-ES/data/reusables/discussions/github-recognizes-members.md b/translations/es-ES/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000000..bca4ed36ef259 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} reconocerá automáticamente a aquellos miembros de la comunidad que contribuyan a los debates de formato pregunta/respuesta con más comentarios marcados como respuesta. diff --git a/translations/es-ES/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/es-ES/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000000..68bfdcdaf6c81 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +Puedes marcar un comentario en el debate como una respuesta al mismo si dicho debate está dentro de una categoría que acepte respuestas. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". + +Cuando marcas una pregunta como una respuesta, {% data variables.product.product_name %} resaltará el comentario y responderá a éste para ayudar a que los visitantes encuentren la respuesta rápidamente. + +![Comentario marcado como respuesta en un debate](/assets/images/help/discussions/comment-marked-as-answer.png) + +No puedes marcar un comentario que tenga un hilo dentro de la respuesta de un comentario como la respuesta al debate. Tampoco puedes marcar un comentario minimizado como la respuesta a un debate. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. En la lista de debates, da clic en el debate sin responder que quieras marcar como respondido. ![Debate sin responder](/assets/images/help/discussions/unanswered-discussion.png) +1. En el debate, encuentra el comentario que quieras marcar como la respuesta. +1. En la esquina superior derecha del comentario, da clic en {% octicon "check-circle" aria-label="The circular check icon" %}. ![Punto circular de verificación de "Marcar como respuesta" para marcar un comentario en un debate como respuesta](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Opcionalmente, para marcar un comentario como la respuesta, da clic en {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/es-ES/data/reusables/discussions/repository-category-limit.md b/translations/es-ES/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000000..56f5e79fcf27a --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Cada repositorio puede tener hasta 10 categorías. diff --git a/translations/es-ES/data/reusables/discussions/starting-a-discussion.md b/translations/es-ES/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000000..e9726db6700a9 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Da clic en **Debate nuevo**. ![Botón de "Debate nuevo" dentro de la pestaña de "Debates" en un repositorio](/assets/images/help/discussions/new-discussion-button.png) +1. Selecciona el menú desplegable de **Seleccionar categoría** y da clic en una categoría para tu debate. ![Menú desplegable de "Seleccionar categoría" y lista de categorías disponibles en un repositorio](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Teclea un título y cuerpo para tu debate. ![Los campos de texto para el cuerpo y título de un debate nuevo](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Da clic en **Iniciar debate**. ![Botón de "Iniciar debate"](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/es-ES/data/reusables/discussions/you-can-categorize-discussions.md b/translations/es-ES/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000000..eb069b82291ea --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +Puedes categorizar debates para ayudar a los miembros de la comunidad a iniciar conversaciones en el lugar correcto y para ayudar los a encontrar los debates relacionados. diff --git a/translations/es-ES/data/reusables/discussions/you-can-convert-an-issue.md b/translations/es-ES/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000000..39e7080135b61 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +Si una propuesta resulta ser una pregunta o una conversación abierta en vez de un elemento de trabajo para rastrear y priorizar, puedes convertirla en un debate. diff --git a/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md b/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000000..5146f80a03019 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +Puedes utilizar los debates para preguntar y resoponder preguntas, compartir información, hacer anuncios y moderar o participar en las conversaciones sobre un proyecto. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/es-ES/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000000..057f990e505f0 --- /dev/null +++ b/translations/es-ES/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +No puedes convertir un debate en una propuesta. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/dotcom_billing/500-error.md b/translations/es-ES/data/reusables/dotcom_billing/500-error.md new file mode 100644 index 0000000000000..c1b005a2fbf70 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/500-error.md @@ -0,0 +1,5 @@ +Si recibes un error 500 al intentar actualizar tu cuenta: + - Intenta limpiar la caché de tu navegador, luego vuelve a enviar tu información + - Comprueba y asegúrate de haber introducido correctamente tus datos de pago + +Si esta acción no resuelve el problema, comunícate con {% data variables.contact.contact_support %}. diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-minutes.md b/translations/es-ES/data/reusables/dotcom_billing/actions-minutes.md new file mode 100644 index 0000000000000..3cfff87816e5f --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/actions-minutes.md @@ -0,0 +1 @@ +1. Debajo de "{% data variables.product.prodname_actions %}", visualiza los detalles de tus minutos usados. ![Detalles de uso de minutos](/assets/images/help/billing/actions-minutes.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md new file mode 100644 index 0000000000000..9e198c5cb70be --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md @@ -0,0 +1 @@ +1. Opcionalmente, da clic en **Obtener reporte de uso** para que se te envíe un archivo CSV por correo electrónico del uso de almacenamiento para {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} a la dirección de correo electrónico principal de la cuenta. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md new file mode 100644 index 0000000000000..7cda523dff919 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md @@ -0,0 +1 @@ +1. Debajo de " Almacenamiento de {% data variables.product.prodname_dotcom %} para Actions y Packages", visualiza los detalles de uso de almacenamiento para cada organización en tu cuenta empresarial, tanto para {% data variables.product.prodname_actions %} como para {% data variables.product.prodname_registry %}. ![Detalles de uso de almacenamiento](/assets/images/help/billing/actions-packages-storage-enterprise.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage.md b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage.md new file mode 100644 index 0000000000000..9a7b00f24390f --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-storage.md @@ -0,0 +1 @@ +1. Debajo de "Almacenamiento para Actions y Packages", visualiza los detalles de tu uso de almacenamiento combinado de {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %}. Los datos de uso de almacenamiento se sincronizan cada hora. ![Detalles de uso de almacenamiento](/assets/images/help/billing/actions-packages-storage.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-unpaid-account.md new file mode 100644 index 0000000000000..0cd8e0ce9faef --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -0,0 +1,5 @@ +Si tu cuenta tiene cargos pendientes sin pagar: + +* El almacenamiento o minutos que se incluyen en tu cuenta para {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} no se restablecerán hasta que se haya procesado exitosamente el pago. +* Para las cuentas que aún cuenten con minutos o almacenamiento libres para el periodo de facturación actual, {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} seguirán disponibles hasta que se alcance el límite de uso incluído. +* Para cuentas que han alcanzado el uso incluido para el periodo de facturación actual para {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %}, se inhabilitará tanto {% data variables.product.prodname_actions %} como {% data variables.product.prodname_registry %} para prevenir cualquier uso excedente posterior. diff --git a/translations/es-ES/data/reusables/dotcom_billing/add-payment-method.md b/translations/es-ES/data/reusables/dotcom_billing/add-payment-method.md new file mode 100644 index 0000000000000..0b7554fc15fd9 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/add-payment-method.md @@ -0,0 +1 @@ +1. Dentro de "Información de facturación", haz clic en **Add a payment method (Añadir un método de pago)**. ![Enlace para agregar un método de pago](/assets/images/help/billing/add-payment-method.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/add-seats.md b/translations/es-ES/data/reusables/dotcom_billing/add-seats.md new file mode 100644 index 0000000000000..f3c65579d9e97 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/add-seats.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable **Edit (Editar)** y haz clic en **Add seats (Añadir asientos)**. ![Menú desplegable de editar](/assets/images/help/billing/add-seats-dropdown.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/cancel-pending-changes.md b/translations/es-ES/data/reusables/dotcom_billing/cancel-pending-changes.md new file mode 100644 index 0000000000000..699751144825c --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/cancel-pending-changes.md @@ -0,0 +1 @@ +1. Junto al cambio pendiente que deseas cancelar, haz clic en **Cancel (Cancelar)**. ![Cancela el enlace junto a un cambio de suscripción pendiente](/assets/images/help/billing/cancel-pending-changes-link.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md b/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md new file mode 100644 index 0000000000000..9c980a2fe244e --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md @@ -0,0 +1 @@ +1. Dentro de "Resumen de facturación", haz clic en **Change to yearly billing (Cambiar a facturación anual)** o **Change to monthly billing (Cambiar a facturación mensual)**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/change-plan-duration-link.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md b/translations/es-ES/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md new file mode 100644 index 0000000000000..e9072f4e4da0e --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md @@ -0,0 +1 @@ +1. Dentro de "Resumen de actualización", elige si quieres pagar mensualmente o anualmente. ![Botones de selección con opción de facturación mensual o anual](/assets/images/help/billing/choose-monthly-or-yearly-billing.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md b/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md new file mode 100644 index 0000000000000..8d9dbac417e95 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md @@ -0,0 +1 @@ +1. Si estás actualizando desde {% data variables.product.prodname_free_team %}, dentro de "Actualizando a", selecciona un producto. ![Botón para actualizar](/assets/images/help/billing/upgrade-to-product.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/confirm-add-seats.md b/translations/es-ES/data/reusables/dotcom_billing/confirm-add-seats.md new file mode 100644 index 0000000000000..6fd2b21034863 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/confirm-add-seats.md @@ -0,0 +1 @@ +1. Haz clic en **Agregar plazas**. ![Botón de agregar plazas](/assets/images/help/billing/add-seats-button.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md b/translations/es-ES/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md new file mode 100644 index 0000000000000..0ea1e78e81d2a --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md @@ -0,0 +1 @@ +1. Para confirmar que deseas cancelar tus cambios de suscripción pendientes, haz clic en **OK (Aceptar)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/confirm_cancel_org_plan.md b/translations/es-ES/data/reusables/dotcom_billing/confirm_cancel_org_plan.md new file mode 100644 index 0000000000000..f2505d50d9092 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/confirm_cancel_org_plan.md @@ -0,0 +1 @@ +7. Lee la información acerca de las características a las que tu organización ya no tendrá acceso en tu próxima fecha de facturación y luego haz clic en **Comprendo. Bajar de categoría mi organización**. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-confirm-button.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/confirm_duration_change.md b/translations/es-ES/data/reusables/dotcom_billing/confirm_duration_change.md new file mode 100644 index 0000000000000..db2f76a22f389 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/confirm_duration_change.md @@ -0,0 +1 @@ +1. Revisa los detalles de tu nuevo plan de pago y luego haz clic en **Change plan duration (Cambiar duración del plan)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/downgrade-org-to-free.md b/translations/es-ES/data/reusables/dotcom_billing/downgrade-org-to-free.md new file mode 100644 index 0000000000000..49bc75122ce99 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/downgrade-org-to-free.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable de **Editar** y da clic en **Bajar de categoría a {% data variables.product.prodname_free_team %}**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/download_receipt.md b/translations/es-ES/data/reusables/dotcom_billing/download_receipt.md new file mode 100644 index 0000000000000..02b716c3f1979 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/download_receipt.md @@ -0,0 +1 @@ +1. Dentro de "Historial de pagos", revisa tus pagos anteriores. Para descargar un recibo de un pago específico, haz clic en {% octicon "download" aria-label="The download icon" %}. ![Botón de recibo de descarga](/assets/images/help/settings/settings-download-receipt.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md b/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md new file mode 100644 index 0000000000000..1d8551ce75e2b --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md @@ -0,0 +1,2 @@ +1. Debajo de "Información de facturación", elige pagar con una tarjeta de crédito o con PayPal. ![Cambiar métodos de pago de facturación](/assets/images/help/billing/billing_switch_payments.png) +1. Completa el formulario de información de pago. Posteriormente, da clic en **Emitir**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md b/translations/es-ES/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md new file mode 100644 index 0000000000000..d37a9e601b21c --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md @@ -0,0 +1,3 @@ +1. Visita la página [Redeem coupon (Canjear cupón)](https://github.com/redeem). +2. En el cuadro Enter coupon code (Ingresar el código de cupón), escribe tu código de cupón y haz clic en **Redeem (Canjear)**. ![Cuadro para Canjear cupón](/assets/images/help/settings/redeem-coupon-box.png) +3. Si no has iniciado sesión, puedes iniciar sesión en esta página, o crear una nueva cuenta para utilizar tu cupón. diff --git a/translations/es-ES/data/reusables/dotcom_billing/extra_info_receipt.md b/translations/es-ES/data/reusables/dotcom_billing/extra_info_receipt.md new file mode 100644 index 0000000000000..0f835ce8b87ed --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/extra_info_receipt.md @@ -0,0 +1,2 @@ +1. Dentro de "Información de pago", en "Información adicional", haz clic en **Add information (Agregar información)**. ![Botón de información adicional de facturación](/assets/images/help/billing/settings_billing_add_billing_extra.png) +1. Escribe la información adicional que deseas en tu recibo y haz clic en **Save contact information (Guardar información de contacto)**. ![Campo de información de contacto](/assets/images/help/settings/Billing-extra-info-field.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/finish_upgrade.md b/translations/es-ES/data/reusables/dotcom_billing/finish_upgrade.md new file mode 100644 index 0000000000000..43929c7ea6138 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/finish_upgrade.md @@ -0,0 +1 @@ +1. Revisa la información acerca del gasto y de tu fecha de facturación y luego haz clic en **Upgrade my account (Actualizar mi cuenta)** o **Upgrade my organization's account (Actualizar la cuenta de mi organización)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md b/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md new file mode 100644 index 0000000000000..36bd3d1e36ce4 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md @@ -0,0 +1 @@ +1. Junto a "Datos de {% data variables.large_files.product_name_short %}", haz clic en **Add more data (Añadir más datos)** o utiliza el menú desplegable de edición y haz clic en **Add more data packs (Añadir más paquetes de datos)**. ![Botón Agregar más datos](/assets/images/help/billing/data-pack-purchase-more.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md b/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md new file mode 100644 index 0000000000000..0d2af71e852dc --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md @@ -0,0 +1 @@ +1. Ver detalles de tu ancho de banda y el uso de almacenamiento dentro de "Datos de {% data variables.large_files.product_name_short %}". ![Detalles del uso de datos de Git LFS](/assets/images/help/billing/lfs-data.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/lfs-remove-data.md b/translations/es-ES/data/reusables/dotcom_billing/lfs-remove-data.md new file mode 100644 index 0000000000000..9e196adc8572a --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/lfs-remove-data.md @@ -0,0 +1 @@ +1. Junto a "Datos de {% data variables.large_files.product_name_short %}", usa el menú desplegable de **Edit (Editar)** y haz clic en **Remove data packs (Eliminar paquetes de datos)**. ![Bajar de categoría tu plan de datos de Git LFS](/assets/images/help/large_files/downgrade_lfs_data_packs.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit.md b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit.md new file mode 100644 index 0000000000000..0fa26818b99d2 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit.md @@ -0,0 +1 @@ +1. Debajo de "límite mensual de gastos", elige limitar los gastos o permitir los gastos ilimitados. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md b/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md new file mode 100644 index 0000000000000..1b1dd5a7e9885 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md @@ -0,0 +1 @@ +1. Dentro de "Resumen de facturación", revisa cuándo vence tu próximo pago. ![Próxima fecha de facturación](/assets/images/help/billing/settings_billing_next_payment.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/number-of-seats.md b/translations/es-ES/data/reusables/dotcom_billing/number-of-seats.md new file mode 100644 index 0000000000000..aa450221d0a03 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/number-of-seats.md @@ -0,0 +1 @@ +1. Dentro de "Agregar asientos", escribe el número de asientos que deseas añadir. ![Entrada para agregar plazas](/assets/images/help/billing/add-seats-amount.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/org-billing-perms.md b/translations/es-ES/data/reusables/dotcom_billing/org-billing-perms.md new file mode 100644 index 0000000000000..db0538bf5774b --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/org-billing-perms.md @@ -0,0 +1 @@ +Únicamente los miembros de la organización que posean los roles de [*propietario*](/articles/permission-levels-for-an-organization) o [*gerente de facturación*](/articles/adding-a-billing-manager-to-your-organization) pueden acceder a los parámetros de facturación de tu organización o modificarlos. diff --git a/translations/es-ES/data/reusables/dotcom_billing/owned_by_business.md b/translations/es-ES/data/reusables/dotcom_billing/owned_by_business.md new file mode 100644 index 0000000000000..6aae041121ad0 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/owned_by_business.md @@ -0,0 +1,2 @@ +1. Opcionalmente, si tu organización pertenece a un negocio o institución, selecciona **Esta cuenta pertenece a un negocio**. ![Casilla para organizaciones que pertenecen a un negocio](/assets/images/help/organizations/organization-belongs-to.png) +2. Si tu organización pertenece a una institución o negocio, teclea el nombre de ésta. ![Campo Nombre de empresa o institución](/assets/images/help/organizations/name-of-business.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/packages-data.md b/translations/es-ES/data/reusables/dotcom_billing/packages-data.md new file mode 100644 index 0000000000000..c65ed966b4241 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/packages-data.md @@ -0,0 +1 @@ +1. Debajo de "{% data variables.product.prodname_registry %}", visualiza los detalles de tu uso de transferencia de datos. ![Detalles de uso de transferencia de datos](/assets/images/help/billing/packages-data.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/payment-methods.md b/translations/es-ES/data/reusables/dotcom_billing/payment-methods.md new file mode 100644 index 0000000000000..ff8a72fa59978 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/payment-methods.md @@ -0,0 +1 @@ +Puedes pagar {% data variables.product.product_name %} con tarjeta de crédito o mediante una cuenta PayPal. diff --git a/translations/es-ES/data/reusables/dotcom_billing/redeem_coupon.md b/translations/es-ES/data/reusables/dotcom_billing/redeem_coupon.md new file mode 100644 index 0000000000000..e04f7354737c8 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/redeem_coupon.md @@ -0,0 +1 @@ +5. Dentro de "Tu nuevo plan", revisa la información acerca de tu plan y tu descuento, y luego haz clic en **Redeem (Canjear)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/remove-payment-method.md b/translations/es-ES/data/reusables/dotcom_billing/remove-payment-method.md new file mode 100644 index 0000000000000..c2df9ab04d7ba --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/remove-payment-method.md @@ -0,0 +1 @@ +3. En la sección "Método de pago", dentro de tu método de pago, haz clic en **Remove (Eliminar)**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/settings/remove_billing_info.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/remove_payment_info.md b/translations/es-ES/data/reusables/dotcom_billing/remove_payment_info.md new file mode 100644 index 0000000000000..a191dbf6f42bd --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/remove_payment_info.md @@ -0,0 +1 @@ +1. Confirma el cambio haciendo clic en **Remove credit card (Eliminar tarjeta de crédito)** o **Remove PayPal account (Eliminar cuenta de PayPal)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md b/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md new file mode 100644 index 0000000000000..44edfaec510a4 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md @@ -0,0 +1 @@ +1. Dentro de "Suscripciones", revisa tus cambios pendientes. ![Sección de suscripciones de la configuración de facturación listando cualquier cambio pendiente de suscripción](/assets/images/help/billing/review-pending-subscription-changes.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/same-payment-method.md b/translations/es-ES/data/reusables/dotcom_billing/same-payment-method.md new file mode 100644 index 0000000000000..c3b0875a6e827 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/same-payment-method.md @@ -0,0 +1 @@ +Cuando actualizas tu método de pago para la suscripción {% data variables.product.prodname_dotcom %} de tu cuenta, tu nuevo método de pago se agrega automáticamente a tus otras suscripciones de productos pagos. diff --git a/translations/es-ES/data/reusables/dotcom_billing/show-plan-details.md b/translations/es-ES/data/reusables/dotcom_billing/show-plan-details.md new file mode 100644 index 0000000000000..1c0f2221e52b3 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/show-plan-details.md @@ -0,0 +1 @@ +1. De forma opcional, para ver los detalles de tu plan, haz clic en **Show details (Mostrar detalles)**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/switch-legacy-billing.md b/translations/es-ES/data/reusables/dotcom_billing/switch-legacy-billing.md new file mode 100644 index 0000000000000..ab639c5d51bb7 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/switch-legacy-billing.md @@ -0,0 +1 @@ +Si tu organización está utilizando un plan de facturación por repositorio heredado, puedes cambiar a precio por usuario en cualquier momento. No podrás volver a cambiar al precio por repositorio una vez que hayas subido de categoría a precio por usuario. diff --git a/translations/es-ES/data/reusables/dotcom_billing/update-spending-limit.md b/translations/es-ES/data/reusables/dotcom_billing/update-spending-limit.md new file mode 100644 index 0000000000000..cf00d83dcde0b --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/update-spending-limit.md @@ -0,0 +1 @@ +1. Si eliges limitar los gastos, debajo de "Limitar gastos", teclea un límite y posteriormente da clic en **Actualizar límite**. ![Campo para teclear el límite de gastos y botón de actualizar límite](/assets/images/help/billing/update-limit.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md b/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md new file mode 100644 index 0000000000000..17e5ad9cde8dd --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md @@ -0,0 +1 @@ +1. Dentro de "Información de facturación", haz clic en **Update payment method (Actualizar método de pago)**. ![Botón para actualizar método de pago](/assets/images/help/billing/update_payment_method.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md b/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md new file mode 100644 index 0000000000000..1bcaa79e891c5 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md @@ -0,0 +1 @@ +1. Si estás mejorando tu producto desde {% data variables.product.prodname_free_team %}, da clic en **Opciones de mejora**. Si estás mejorando tu producto desde {% data variables.product.prodname_team %}, utiliza el menú desplegable de **Editar** y da clic en **Mejorar**. ![Botón de mejorar opciones](/assets/images/help/billing/choose-monthly-or-yearly-billing.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/view-all-subscriptions.md b/translations/es-ES/data/reusables/dotcom_billing/view-all-subscriptions.md new file mode 100644 index 0000000000000..c48a99ed6adad --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/view-all-subscriptions.md @@ -0,0 +1 @@ +Para ver todas las suscripciones para tu cuenta de {% data variables.product.product_name %}, consulta [Ver tus suscripciones y la fecha de facturación](/articles/viewing-your-subscriptions-and-billing-date)". diff --git a/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md b/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md new file mode 100644 index 0000000000000..9ae5e5b66e2a6 --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md @@ -0,0 +1 @@ +1. Dentro de "Información de facturación", haz clic en **View payment method (Ver método de pago)**. ![Ver enlace de historial de pagos](/assets/images/help/billing/view-payment-history-link.png) diff --git a/translations/es-ES/data/reusables/education/about-github-education-link.md b/translations/es-ES/data/reusables/education/about-github-education-link.md new file mode 100644 index 0000000000000..7cbac2c001fdb --- /dev/null +++ b/translations/es-ES/data/reusables/education/about-github-education-link.md @@ -0,0 +1 @@ +Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_education %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)". diff --git a/translations/es-ES/data/reusables/education/apply-for-team.md b/translations/es-ES/data/reusables/education/apply-for-team.md new file mode 100644 index 0000000000000..fdb25ed5b4a16 --- /dev/null +++ b/translations/es-ES/data/reusables/education/apply-for-team.md @@ -0,0 +1 @@ +- Solicita gratis [{% data variables.product.prodname_team %}](/articles/github-s-products), que permite tener ilimitados usuarios y repositorios privados. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)". diff --git a/translations/es-ES/data/reusables/education/benefits-page.md b/translations/es-ES/data/reusables/education/benefits-page.md new file mode 100644 index 0000000000000..71d47da819b19 --- /dev/null +++ b/translations/es-ES/data/reusables/education/benefits-page.md @@ -0,0 +1 @@ +1. Ve a [{% data variables.product.prodname_education %}](https://education.github.com) y, en la parte superior derecha, haz clic en **Get benefits (Obtener beneficios)**. diff --git a/translations/es-ES/data/reusables/education/click-get-teacher-benefits.md b/translations/es-ES/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000000..2c6cc924a988b --- /dev/null +++ b/translations/es-ES/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Debajo de "Individuos", da clic en **Obtén beneficios de docente**. !["Obtén beneficios de docente" en la página principal de {% data variables.product.prodname_education %}](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/es-ES/data/reusables/education/educator-requirements.md b/translations/es-ES/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000000..c06ea070405e2 --- /dev/null +++ b/translations/es-ES/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +Para postularte para obtener und escuento de docente o investigador, debes cumplir con los siguientes requisitos. + +- Ser educador, miembro de una factultad, o investigador. +- Tener una dirección de correo electrónico verificable que haya emitido una institución educativa. +- Cargar los documentos que comprueben tu afiliación a la institución educativa. +- Tener una cuenta de usuario en {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/education/pdf-support.md b/translations/es-ES/data/reusables/education/pdf-support.md new file mode 100644 index 0000000000000..1026c09d05edf --- /dev/null +++ b/translations/es-ES/data/reusables/education/pdf-support.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** no se admiten archivos PDF y no puedes cargarlos como prueba de tu afiliación. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/education/plan-to-use-github.md b/translations/es-ES/data/reusables/education/plan-to-use-github.md new file mode 100644 index 0000000000000..6095f7d45bf2f --- /dev/null +++ b/translations/es-ES/data/reusables/education/plan-to-use-github.md @@ -0,0 +1 @@ +1. Describe cómo planeas utilizar {% data variables.product.prodname_dotcom %}. ![Campo de descripción sobre cómo planeas utilizar {% data variables.product.prodname_dotcom %}](/assets/images/help/education/purpose-for-github-education.png) diff --git a/translations/es-ES/data/reusables/education/school-name.md b/translations/es-ES/data/reusables/education/school-name.md new file mode 100644 index 0000000000000..61df2edc9c786 --- /dev/null +++ b/translations/es-ES/data/reusables/education/school-name.md @@ -0,0 +1 @@ +5. Ingresa el nombre de tu escuela. ![Campo para el nombre de tu escuela](/assets/images/help/education/enter-school-name.png) diff --git a/translations/es-ES/data/reusables/education/select-email-address.md b/translations/es-ES/data/reusables/education/select-email-address.md new file mode 100644 index 0000000000000..b71c9e0c88582 --- /dev/null +++ b/translations/es-ES/data/reusables/education/select-email-address.md @@ -0,0 +1,7 @@ +1. Selecciona o añade la dirección de correo electrónico que utilizas para la escuela. ![Selecciona la dirección de correo](/assets/images/help/education/select-email-address.png) + + {% tip %} + + **Sugerencia**: seleccionar una dirección de correo electrónico emitida por la escuela, si tienes una, te da mayor probabilidad de una revisión rápida. + + {% endtip %} diff --git a/translations/es-ES/data/reusables/education/submit-application.md b/translations/es-ES/data/reusables/education/submit-application.md new file mode 100644 index 0000000000000..d44fcabb2dd8e --- /dev/null +++ b/translations/es-ES/data/reusables/education/submit-application.md @@ -0,0 +1,3 @@ +8. Verifica los detalles de tu aplicación, luego haz clic en **Submit your information (Enviar tu información)**. ![Botón para enviar tu información](/assets/images/help/education/submit-your-information-button.png) + + Si tu solicitud es aprobada, recibirás un correo electrónico de confirmación. Las solicitudes generalmente se procesan en pocos días, pero puede llevar más tiempo durante las horas pico, así como durante el inicio de un nuevo semestre. diff --git a/translations/es-ES/data/reusables/education/upgrade-organization.md b/translations/es-ES/data/reusables/education/upgrade-organization.md new file mode 100644 index 0000000000000..bd31713ad5ab9 --- /dev/null +++ b/translations/es-ES/data/reusables/education/upgrade-organization.md @@ -0,0 +1 @@ +1. Junto a la organización que quieras mejorar, da clic en **Mejorar**. ![Botón para actualizar](/assets/images/help/education/upgrade-org-button.png) diff --git a/translations/es-ES/data/reusables/education/upgrade-page.md b/translations/es-ES/data/reusables/education/upgrade-page.md new file mode 100644 index 0000000000000..bd8579e8d84b7 --- /dev/null +++ b/translations/es-ES/data/reusables/education/upgrade-page.md @@ -0,0 +1 @@ +1. Diríjete a "Mejorar tu organización" en la página de [Mejoras de Organización](https://education.github.com/toolbox/offers/github-org-upgrades). diff --git a/translations/es-ES/data/reusables/education/upload-different-image.md b/translations/es-ES/data/reusables/education/upload-different-image.md new file mode 100644 index 0000000000000..87889bc4a8038 --- /dev/null +++ b/translations/es-ES/data/reusables/education/upload-different-image.md @@ -0,0 +1 @@ +Al volver a solicitar, carga una imagen diferente a la que incluiste en tu primera solicitud. Asegúrate de que sea claramente visible al menos una fecha que demuestre tu situación académica actual. diff --git a/translations/es-ES/data/reusables/education/upload-proof-reapply.md b/translations/es-ES/data/reusables/education/upload-proof-reapply.md new file mode 100644 index 0000000000000..8d874ed0686e1 --- /dev/null +++ b/translations/es-ES/data/reusables/education/upload-proof-reapply.md @@ -0,0 +1 @@ +Cuando presentes nuevamente una solicitud, carga una imagen de tu número de identificación dentro de la escuela, tu certificado analítico o cualquier otro documento que sirva como evidencia de tu situación académica, en el cual se pueda visualizar con claridad al menos una fecha. diff --git a/translations/es-ES/data/reusables/education/upload-proof-status.md b/translations/es-ES/data/reusables/education/upload-proof-status.md new file mode 100644 index 0000000000000..98674a6dbd63e --- /dev/null +++ b/translations/es-ES/data/reusables/education/upload-proof-status.md @@ -0,0 +1,10 @@ +1. Si se solicita, carga la prueba de tu situación académica. + - Haz clic en **Use your camera to take a picture (Utiliza tu cámara para sacar una foto)**. ![Botón para utilizar tu cámara para sacar una foto](/assets/images/help/education/upload-proof-status.png) + - Como alternativa, para cambiar la cámara que deseas utilizar, usa el menú desplegable de la cámara. ![Menú desplegable de la cámara](/assets/images/help/education/camera-drop-down.png) + - Coloca tu ID académico válido u otra prueba de tu situación académica actual en el cuadro, después haz clic en **Take a picture (Sacar una foto)**. ![Botón para sacar una foto](/assets/images/help/education/take-photo-button.png) + - Si no puedes sacar una foto de la prueba de tu situación académica, para cargar una imagen desde tu computadora en su lugar, haz clic en **Upload image (Cargar una imagen)**. ![Enlace para subir imagen](/assets/images/help/education/upload-image-link.png) + {% note %} + + **Nota:** no se admiten archivos PDF y no puedes cargarlos como prueba de tu situación académica. + + {% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md new file mode 100644 index 0000000000000..e6b74c495971c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md @@ -0,0 +1,5 @@ +1. Ve a {% data variables.product.prodname_dotcom_the_website %}. + +1. En la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %}, da clic en tu foto de perfil y luego en **Tus empresas**. !["Tus empresas" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/enterprises/your-enterprises.png) + +1. En la lista de empresas, da clic en aquella que quieras ver. ![Nombre de una empresa en la lista de tus empresas](/assets/images/help/enterprises/your-enterprises-list.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md new file mode 100644 index 0000000000000..0c68b39925117 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md @@ -0,0 +1,11 @@ +{% if currentVersion == "free-pro-team@latest" %}1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego en **Tus empresas**. + !["Tus empresas" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/enterprises/your-enterprises.png) + +1. En la lista de empresas, da clic en aquella que quieras ver. ![Nombre de una empresa en la lista de tus empresas](/assets/images/help/enterprises/your-enterprises-list.png) + +{% elsif currentVersion ver_lt "enterprise-server@2.22" %}1. Navega a tu cuenta empresarial a través de {% raw %}https://HOSTNAME/enterprises/ENTERPRISE-NAME{% endraw %}, reemplazando `HOSTNAME` con el nombre del host de tu instancia y `ENTERPRISE-NAME` con el nombre de tu cuenta empresarial. + +{% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego en **Configuración de empresa**. + !["Configuración de empresa" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) + +{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md new file mode 100644 index 0000000000000..91170d7be7a84 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md @@ -0,0 +1 @@ +1. Opcionalmente, bajo "Uso mensual de Actions y Packages de {% data variables.product.prodname_dotcom %}", da clic en **Obtener reporte de uso** para enviar un reporte en formato CSV por correo electrónico a la dirección principal configurada sobre {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} para cada una de las organizaciones que pertenecen a tu cuenta empresarial. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download-enterprise.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-tab.md new file mode 100644 index 0000000000000..7ef49f8f60840 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-tab.md @@ -0,0 +1 @@ +1. Debajo de "{% octicon "law" aria-label="The law icon" %} Políticas", haz clic en **Acciones**. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/admin-managing-licenses.md b/translations/es-ES/data/reusables/enterprise-accounts/admin-managing-licenses.md new file mode 100644 index 0000000000000..bbc6191cd285c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/admin-managing-licenses.md @@ -0,0 +1 @@ +Los administradores de {% data variables.product.prodname_enterprise %} pueden utilizar una cuenta empresarial para ver y administrar las licencias de usuario en su instancia de {% data variables.product.prodname_ghe_server %}. Para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}, y consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/admin/installation/managing-your-github-enterprise-license)". diff --git a/translations/es-ES/data/reusables/enterprise-accounts/administrators-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/administrators-tab.md new file mode 100644 index 0000000000000..2a8a0e197e074 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/administrators-tab.md @@ -0,0 +1 @@ +1. Dentro de "Personas {% octicon "person" aria-label="The People icon" %}", haz clic en **Administrators (Administradores)**. ![Pestaña de administradores](/assets/images/help/business-accounts/business-accounts-admin-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/audit-log-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/audit-log-tab.md new file mode 100644 index 0000000000000..b120c9c73839f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/audit-log-tab.md @@ -0,0 +1 @@ +1. Dentro de " Parámetros de {% octicon "gear" aria-label="The Settings gear" %} ", haz clic en **Audit log (Registro de auditoría)**. ![Pestaña de registro de auditoría en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-audit-log-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/billing-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/billing-tab.md new file mode 100644 index 0000000000000..5028402cde1af --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/billing-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Billing (Facturación)**. ![Pestaña de facturación en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-billing-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/enterprise-accounts-billing.md b/translations/es-ES/data/reusables/enterprise-accounts/enterprise-accounts-billing.md new file mode 100644 index 0000000000000..604a7b798a0f8 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/enterprise-accounts-billing.md @@ -0,0 +1 @@ +Las cuentas empresariales están actualmente disponibles para los clientes de {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} que paguen por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas a tu cuenta empresarial se agregará en una sola factura. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/es-ES/data/reusables/enterprise-accounts/enterprise-administrators.md new file mode 100644 index 0000000000000..b2b139a5a9774 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/enterprise-administrators.md @@ -0,0 +1 @@ +{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}Actualmente, hay dos tipos de roles administrativos disponibles en las empresas: propietarios de la empresa, quienes pueden acceder y administrar toda la configuración de la empresa, y gerentes de facturación, quienes pueden acceder a y administrar únicamente la configuración de facturación de la empresa. {% endif %}Los propietarios de empresa también pueden {% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}{% endif %} ver a todos los miembros y colaboradores externos de todas las organizaciones que pertenezcan a la empresa. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md new file mode 100644 index 0000000000000..210b139862fef --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_connect %}**. ![Pestaña GitHub Connect en la barra lateral de parámetros de la cuenta de empresa](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/hooks-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/hooks-tab.md new file mode 100644 index 0000000000000..66d710113475d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/hooks-tab.md @@ -0,0 +1 @@ +1. Debajo de "{% octicon "gear" aria-label="The Settings gear" %} Configuraciones", haz clic en **Hooks** (Ganchos). ![Pestaña Hooks (Ganchos) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-hooks-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/license-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/license-tab.md new file mode 100644 index 0000000000000..e4fde8f713b28 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/license-tab.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" %} + +1. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) + +{% else %} + +1. En la barra lateral izquierda, haz clic en **License** (Licencia). ![Pestaña de "Licencia" en la barra lateral de configuración para la cuenta empresarial](/assets/images/enterprise/enterprises/license.png) + +{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/messages-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/messages-tab.md new file mode 100644 index 0000000000000..7fbfd0ffc3110 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/messages-tab.md @@ -0,0 +1 @@ +1. Debajo de "{% octicon "gear" aria-label="The Settings gear" %} Configuraciones", haz clic en **Messages** (Mensajes). ![Pestaña Messages (Mensajes) en la barra lateral de parámetros de la empresa](/assets/images/enterprise/business-accounts/settings-messages-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/options-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/options-tab.md new file mode 100644 index 0000000000000..ffb7ceed1fe71 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/options-tab.md @@ -0,0 +1 @@ +1. Debajo de {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} {% octicon "law" aria-label="The law icon" %} **Políticas**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Configuración"{% endif %}, da clic en **Opciones**. ![Pestaña Options (Opciones) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/enterprise/business-accounts/settings-options-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md b/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md new file mode 100644 index 0000000000000..774a79532c7ac --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md @@ -0,0 +1 @@ + 6. Haz clic en **Save ** (guardar). ![Save button](/assets/images/enterprise/business-accounts/pages-policies-save-button.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md new file mode 100644 index 0000000000000..5d9fb29f6465f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md @@ -0,0 +1 @@ +1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**. ![Pages tab in the enterprise sidebar](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/people-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/people-tab.md new file mode 100644 index 0000000000000..b62267b863af3 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/people-tab.md @@ -0,0 +1 @@ +1. En la barra lateral de Cuenta de empresa, haz clic en {% octicon "person" aria-label="The People icon" %} **Personas**. ![Pestaña People (Personas) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/business-account-people-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/policies-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/policies-tab.md new file mode 100644 index 0000000000000..3c6ec397b1c30 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/policies-tab.md @@ -0,0 +1 @@ +1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Policies** (Políticas). ![Pestaña Policies (Políticas) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-policies-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/projects-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/projects-tab.md new file mode 100644 index 0000000000000..3c93a06737276 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/projects-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Projects** (Proyectos). ![Pestaña Projects (Proyectos) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-projects-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-policy.md b/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-policy.md new file mode 100644 index 0000000000000..a39d234056f7b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-policy.md @@ -0,0 +1 @@ +1. Debajo de "Repository creation" (Creación de repositorios), selecciona una política. ![Menú desplegable con opciones de políticas de creación de repositorios](/assets/images/help/business-accounts/repository-creation-policy-drop-down.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-types.md b/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-types.md new file mode 100644 index 0000000000000..7b434273105ed --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/repo-creation-types.md @@ -0,0 +1 @@ +1. Si seleccionaste **Members can create repositories** (Los miembros pueden crear repositorios), selecciona uno o más tipos de repositorios. ![Casillas para tipos de repositorio](/assets/images/help/business-accounts/repository-creation-policy-repo-types.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/repositories-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/repositories-tab.md new file mode 100644 index 0000000000000..f11f284d9fca5 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/repositories-tab.md @@ -0,0 +1 @@ +1. Debajo de "{% octicon "law" aria-label="The law icon" %} Políticas", haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/policies-repositories-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/repository-deletion-policy.md b/translations/es-ES/data/reusables/enterprise-accounts/repository-deletion-policy.md new file mode 100644 index 0000000000000..4be845cba69af --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/repository-deletion-policy.md @@ -0,0 +1 @@ +1. Debajo de "Repository deletion and transfer" (Eliminación y transferencia de repositorios), usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de eliminación de repositorios](/assets/images/help/business-accounts/repository-deletion-policy-drop-down.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/repository-visibility-policy.md b/translations/es-ES/data/reusables/enterprise-accounts/repository-visibility-policy.md new file mode 100644 index 0000000000000..16eee6509aede --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/repository-visibility-policy.md @@ -0,0 +1 @@ +1. Debajo de "Repository visibility change" (Cambio de visibilidad de repositorios), usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de visibilidad de repositorios](/assets/images/help/business-accounts/repository-visibility-policy-drop-down.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/security-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/security-tab.md new file mode 100644 index 0000000000000..03d287eacd622 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/security-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). ![Pestaña Security (Seguridad) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-security-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/settings-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/settings-tab.md new file mode 100644 index 0000000000000..99f7f874d9b23 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/settings-tab.md @@ -0,0 +1 @@ +1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "gear" aria-label="The Settings gear" %} **Settings** (Configuraciones). ![Pestaña Settings (Configuraciones) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md new file mode 100644 index 0000000000000..5c89ca67cf512 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. Para solicitar acceso al beta, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md new file mode 100644 index 0000000000000..e4dbf13f79d78 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md @@ -0,0 +1 @@ +1. Debajo de "Configuración", da clic en **Dominios verificados**. ![Pestaña de "Dominios verificados"](/assets/images/help/enterprises/verified-domains-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/verifying-domains-release-phase.md b/translations/es-ES/data/reusables/enterprise-accounts/verifying-domains-release-phase.md new file mode 100644 index 0000000000000..1f87ddf52f7bd --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/verifying-domains-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** El verificar el dominio de una cuenta empresarial se encuentra actualmente en beta y está sujeto a cambios. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md b/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md new file mode 100644 index 0000000000000..e9775f0960f17 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md @@ -0,0 +1 @@ +Opcionalmente, para ver la configuración actual en todas las organizaciones de la cuenta empresarial antes de requerir alguna configuración adicional, da clic en {% octicon "eye" aria-label="The eye octicon" %} **Ver las configuraciones actuales de tus organizaciones**. ![Enlace para visualizar la configuración política actual para todas las organizaciones en el negocio](/assets/images/help/business-accounts/view-current-policy-implementation-link.png) diff --git a/translations/es-ES/data/reusables/enterprise-managed/about-billing.md b/translations/es-ES/data/reusables/enterprise-managed/about-billing.md new file mode 100644 index 0000000000000..9e7ed843b20d1 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-managed/about-billing.md @@ -0,0 +1 @@ +You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise/rate_limit.md b/translations/es-ES/data/reusables/enterprise/rate_limit.md new file mode 100644 index 0000000000000..ebefc5c176b01 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise/rate_limit.md @@ -0,0 +1,4 @@ +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +Toma en cuenta que los límites que se mencionan anteriormente son aquellos límites de tasa predeterminados para +{% data variables.product.product_name %}. Contacta a tu administrador de sitio para confirmar si los límites de tasa están habilitados y cómo se configuraron. +{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise/use-a-multiplexer.md b/translations/es-ES/data/reusables/enterprise/use-a-multiplexer.md new file mode 100644 index 0000000000000..26236318c5535 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise/use-a-multiplexer.md @@ -0,0 +1 @@ +Este comando puede demorar un poco en finalizar, así que recomendamos ejecutar el comadno en un multiplexor de terminal como `screen` o `tmux`. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/apply-configuration.md b/translations/es-ES/data/reusables/enterprise_clustering/apply-configuration.md new file mode 100644 index 0000000000000..fd8d4d20bc3e9 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/apply-configuration.md @@ -0,0 +1,3 @@ +1. Aplica la configuración nueva. {% data reusables.enterprise.use-a-multiplexer %} + + ghe-cluster-config-apply diff --git a/translations/es-ES/data/reusables/enterprise_clustering/clustering-requires-https.md b/translations/es-ES/data/reusables/enterprise_clustering/clustering-requires-https.md new file mode 100644 index 0000000000000..3ba817c920b77 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/clustering-requires-https.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** La agrupación de {% data variables.product.prodname_ghe_server %} se debe configurar con HTTPS. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise_clustering/clustering-scalability.md b/translations/es-ES/data/reusables/enterprise_clustering/clustering-scalability.md new file mode 100644 index 0000000000000..53195270fdaab --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/clustering-scalability.md @@ -0,0 +1 @@ +La agrupación proporciona una mejor escalabilidad al distribuir la carga en múltiples nodos. Este escalado horizontal puede ser conveniente para algunas organizaciones con decenas de miles de programadores. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/configuration-file-heading.md b/translations/es-ES/data/reusables/enterprise_clustering/configuration-file-heading.md new file mode 100644 index 0000000000000..0978ff143033d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/configuration-file-heading.md @@ -0,0 +1 @@ +El archivo de configuración de clúster lista cada nodo bajo un encabezado de [cluster "HOSTNAME"]. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/configuration-finished.md b/translations/es-ES/data/reusables/enterprise_clustering/configuration-finished.md new file mode 100644 index 0000000000000..5d603fa3363b2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/configuration-finished.md @@ -0,0 +1,5 @@ +1. Después de que finalice la ejecución de configuración, {% data variables.product.prodname_ghe_server %} muestra el siguiente mensaje. + + ```shell + Configuración de clúster finalizada + ``` diff --git a/translations/es-ES/data/reusables/enterprise_clustering/health_checks.md b/translations/es-ES/data/reusables/enterprise_clustering/health_checks.md new file mode 100644 index 0000000000000..858e5cc924f95 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/health_checks.md @@ -0,0 +1,5 @@ +Configura el balanceador de carga para verificar una de estas URL: + - `https://HOSTNAME/status` si HTTPS está habilitado (por defecto) + - `http://HOSTNAME/status` si HTTPS está inhabilitado + +La verificación arrojará el código de estado `200` (OK) si el nodo es correcto y está disponible para responder a las solicitudes del usuario final. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md b/translations/es-ES/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md new file mode 100644 index 0000000000000..d38fb076c9fea --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md @@ -0,0 +1 @@ +El órden de los pares de clave-valor no importa. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_dns.md b/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_dns.md new file mode 100644 index 0000000000000..fd1786f2bafac --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_dns.md @@ -0,0 +1 @@ +Las búsquedas DNS para el nombre del host de {% data variables.product.prodname_ghe_server %} se deben resolver con el balanceador de carga. Es recomendable que habilites el aislamiento de subdominio. Si el aislamiento de subdominio está habilitado, un registro comodín adicional (`*.HOSTNAME`) también se debería resolver con el balanceador de carga. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_intro.md b/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_intro.md new file mode 100644 index 0000000000000..aab677a0463b0 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/load_balancer_intro.md @@ -0,0 +1 @@ +Un diseño de balanceador de carga utiliza un dispositivo de red para dirigir el tráfico de Git y HTTP a los aparatos individuales del {% data variables.product.prodname_ghe_server %}. Puedes utilizar un balanceador de carga para restringir el tráfico directo al aparato con fines de seguridad o para redirigir el tráfico, de ser necesario, sin cambios en los registros DNS. Es altamente recomendable utilizar un balanceador de carga basado en TPC que admita el protocolo PROXY. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/open-configuration-file.md b/translations/es-ES/data/reusables/enterprise_clustering/open-configuration-file.md new file mode 100644 index 0000000000000..a625ef3562d3d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/open-configuration-file.md @@ -0,0 +1,3 @@ +1. En un editor de texto, abre el archivo de configuración de clúster ubicado en _/data/user/common/cluster.conf_. Por ejemplo, puedes utilizar Vim. + + sudo vim /data/user/common/cluster.conf diff --git a/translations/es-ES/data/reusables/enterprise_clustering/proxy_preference.md b/translations/es-ES/data/reusables/enterprise_clustering/proxy_preference.md new file mode 100644 index 0000000000000..acfe08cf91638 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/proxy_preference.md @@ -0,0 +1 @@ +Si tu balanceador de carga lo admite, es altamente recomendable implementar el protocolo PROXY. Cuando no está disponible el soporte de PROXY, también se puede balancear la carga de los puertos HTTP y HTTPS usando el encabezado `X-Forwarded-For`. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md new file mode 100644 index 0000000000000..9afca0bede61f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -0,0 +1,10 @@ +##### Mapeos de puertos de protocolo TCP de PROXY + +| Puerto fuente | Puerto de destino | Descripción del servicio | +|:-------------:|:-----------------:|:---------------------------:| +| 22 | 23 | Git sobre SSH | +| 80 | 81 | HTTP | +| 443 | 444 | HTTPS | +| 8080 | 8081 | Consola de gestión HTTP | +| 8443 | 8444 | Consola de gestión de HTTPS | +| 9418 | 9419 | Git | diff --git a/translations/es-ES/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md b/translations/es-ES/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md new file mode 100644 index 0000000000000..bf4bff292d19d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md @@ -0,0 +1,5 @@ +{% danger %} + +**Advertencia de seguridad**: Cuando estén habilitados el soporte de PROXY o el redireccionamiento de HTTP, es muy importante que ningún tráfico externo pueda llegar directamente a los aparatos del {% data variables.product.prodname_ghe_server %}. Si el tráfico externo no se bloquea correctamente, las direcciones IP de origen se pueden falsificar. + +{% enddanger %} diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md new file mode 100644 index 0000000000000..a483dc23b65ae --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md @@ -0,0 +1 @@ +1. Usando el shell administrativo o DHCP, configura **solo** la dirección IP del nodo de reemplazo. No configures los otros parámetros. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md new file mode 100644 index 0000000000000..d439ca5f7fa8d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md @@ -0,0 +1 @@ +1. Desde el mismo nodo, ejecuta `ghe-cluster-config-apply`. Esto validará el archivo de configuración, lo copiará en cada nodo de la agrupación y configurará cada nodo según el archivo `cluster.conf` modificado. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md new file mode 100644 index 0000000000000..4f45c0b070737 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md @@ -0,0 +1 @@ +1. Desde el shell administrativo del nodo con el archivo `cluster.conf` modificado, ejecuta `ghe-cluster-config-init `. Esto iniciará el nodo recién agregado en la agrupación. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md new file mode 100644 index 0000000000000..f9ce5e5c64392 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md @@ -0,0 +1,11 @@ +1. Para marcar el nodo que falló fuera de línea, en cualquier nodo, modifica el [archivo de configuración de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file) (`cluster.conf`) en la sección de nodo correspondiente para incluir el texto `offline = true`. + + Por ejemplo, este archivo `cluster.conf` modificado marcará el nodo `ghe-data-node-3` como fuera de línea: + + + 
[cluster "ghe-data-node-3"]
+ hostname = ghe-data-node-3
+ offline = true
+ ipv4 = 192.168.0.6
+ # ipv6 = fd12:3456:789a:1::6
+
diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md new file mode 100644 index 0000000000000..875b558c0e8e9 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md @@ -0,0 +1,14 @@ +1. Para agregar el nodo de reemplazo proporcionado recientemente, en cualquier nodo, modifica el archivo `cluster.conf` para eliminar el nodo fallido y agregar el nodo de reemplazo. Por ejemplo, este archivo `cluster.conf` modificado reemplaza el `ghe-data-node-3` con el nodo proporcionado recientemente, `ghe-replacement-data-node-3`: 
+  [cluster "ghe-replacement-data-node-3"]
+    hostname = ghe-replacement-data-node-3
+    ipv4 = 192.168.0.7
+    # ipv6 = fd12:3456:789a:1::7
+    git-server = true
+    pages-server = true
+    mysql-server = true
+    elasticsearch-server = true
+    redis-server = true
+    memcache-server = true
+    metrics-server = true
+    storage-server = true
+
diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md new file mode 100644 index 0000000000000..1e74882cf6035 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md @@ -0,0 +1 @@ +1. Si vas a tomar un nodo fuera de línea que tiene `git-server = true` establecido en cluster.conf, evacua el nodo. Para obtener más información, consulta "[Evacuar un nodo de la agrupación](/enterprise/{{ currentVersion }}/admin/clustering/evacuating-a-cluster-node)". diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md new file mode 100644 index 0000000000000..e1eb2f90eb019 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md @@ -0,0 +1 @@ +1. [Aprovisiona e instala el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance) con un nombre de host único en el nodo de reemplazo. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md new file mode 100644 index 0000000000000..37900972ffccf --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md @@ -0,0 +1,6 @@ +1. Si estás reemplazando el nodo primerio de MySQL o de Redis, en `cluster.conf`, modifica el valor de `mysql-master` o de `redis-master` con el nombre del nodo de reemplazo. + + Por ejemplo, este archivo `cluster.conf` modificado especifica un nodo de clúster recién aprovisionado, `ghe-replacement-data-node-1` como el nodo primario de MySQL y Redis: 
+  mysql-master = ghe-replacement-data-node-1
+  redis-master = ghe-replacement-data-node-1
+
diff --git a/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md new file mode 100644 index 0000000000000..72b3027bf915d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md @@ -0,0 +1 @@ +1. Desde el shell administrativo del nodo en el que modificaste el archivo `cluster.conf`, ejecuta `ghe-cluster-config-init`. Esto validará el archivo de configuración, lo copiará en cada nodo de la agrupación y marcará el nodo fuera de línea. diff --git a/translations/es-ES/data/reusables/enterprise_clustering/ssh-to-a-node.md b/translations/es-ES/data/reusables/enterprise_clustering/ssh-to-a-node.md new file mode 100644 index 0000000000000..80b4a124a8a83 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/ssh-to-a-node.md @@ -0,0 +1 @@ +1. Ingresa por SSH a cualquier nodo dentro de tu clúster. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)." diff --git a/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md new file mode 100644 index 0000000000000..0423edf09bf59 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -0,0 +1,10 @@ +##### Mapeos de puertos de protocolo TCP para usar sin soporte de PROXY + +| Puerto fuente | Puerto de destino | Descripción del servicio | +|:-------------:|:-----------------:|:---------------------------:| +| 22 | 22 | Git sobre SSH | +| 25 | 25 | SMTP | +| 80 | 80 | HTTP | +| 443 | 443 | HTTPS | +| 8080 | 8080 | Consola de gestión HTTP | +| 8443 | 8443 | Consola de gestión de HTTPS | diff --git a/translations/es-ES/data/reusables/enterprise_clustering/x-forwarded-for.md b/translations/es-ES/data/reusables/enterprise_clustering/x-forwarded-for.md new file mode 100644 index 0000000000000..aa6a295b9d1ca --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_clustering/x-forwarded-for.md @@ -0,0 +1 @@ +Usa el protocolo X-Forwarded-For **solo** cuando el protocolo PROXY no esté disponible. El encabezado `X-Forwarded-For` solo funciona con HTTP y HTTPS. La dirección IP informada para las conexiones de Git a través de SSH mostrarán la IP del balanceador de carga. diff --git a/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md new file mode 100644 index 0000000000000..1bf0c8547b2c8 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md @@ -0,0 +1 @@ +No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, actualiza a la última versión de GitHub Enterprise. Para obtener ayuda con la actualización, contacta al soporte de GitHub Enterprise. diff --git a/translations/es-ES/data/reusables/enterprise_deprecation/version_was_deprecated.md b/translations/es-ES/data/reusables/enterprise_deprecation/version_was_deprecated.md new file mode 100644 index 0000000000000..132ee85cc91cd --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_deprecation/version_was_deprecated.md @@ -0,0 +1 @@ +Esta versión de GitHub Enterprise se discontinuó el diff --git a/translations/es-ES/data/reusables/enterprise_deprecation/version_will_be_deprecated.md b/translations/es-ES/data/reusables/enterprise_deprecation/version_will_be_deprecated.md new file mode 100644 index 0000000000000..465b1c328471c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_deprecation/version_will_be_deprecated.md @@ -0,0 +1 @@ +Esta versión de GitHub Enterprise se discontinuará el diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/installing-releases.md new file mode 100644 index 0000000000000..bf39558022150 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/installing-releases.md @@ -0,0 +1,3 @@ +### Instalar lanzamientos del {% data variables.product.prodname_ghe_server %} + +Para asegurar que el {% data variables.product.product_location %} sea estable, debes instalar e implementar lanzamientos de {% data variables.product.prodname_ghe_server %}. Instalar lanzamientos del {% data variables.product.prodname_ghe_server %} garantiza que tengas las últimas características, modificaciones y mejoras así como también cualquier actualización a características, correcciones de código, patch u otras actualizaciones y correcciones generales para el {% data variables.product.prodname_ghe_server %}. diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/sign-in-to-support.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/sign-in-to-support.md new file mode 100644 index 0000000000000..3c760c35a0f34 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/sign-in-to-support.md @@ -0,0 +1 @@ +1. Visita https://enterprise.github.com/support e inicia sesión en (si se solicita que lo hagas). diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md new file mode 100644 index 0000000000000..1caf841046091 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md @@ -0,0 +1,18 @@ +1. Debajo de "Tu dirección de correo electrónico", teclea la dirección de correo electrónico asociada con tu cuenta de {% data variables.product.product_name %}. ![Campo Tu dirección de correo electrónico](/assets/images/enterprise/support/support-ticket-email-address-field.png) +1. Debajo de "Asunto", teclea un título descriptivo para tu problema. ![Campo de asuto](/assets/images/enterprise/support/support-ticket-subject-field.png) +1. Debajo de "Descripción", proporciona información adicional que ayudará al equipo de {% data variables.contact.enterprise_support %} para solucionar el problema. La información útil podría incluir: ![Campo Descripción](/assets/images/enterprise/support/support-ticket-description-field.png) + - Pasos para reproducir el incidente + - Cualquier circunstancia especial relacionada con el descubrimiento del problema (por ejemplo, la primera vez que se suscitó, o su materialización después de cierto evento, frecuencia en la que se presenta, impacto al negocio, y urgencia sugerida) + - Redacción exacta de los mensajes de error +1. Desde el menú desplegable de {% data variables.product.prodname_enterprise %} del producto, selecciona {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}. ![Menú desplegable Prioridad](/assets/images/enterprise/support/support-ticket-ghe-product.png) +1. Desde el menú desplegable de "Prioridad" selecciona la urgencia adecuada. Para obtener más información, consulta la sección "[Asignar una prioridad a un ticket de soporte]{% if currentVersion == "free-pro-team@latest" %}(/articles/about-github-premium-support-for-github-enterprise-cloud#assigning-a-priority-to-a-support-ticket){% else %}(/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket){% endif %}." ![Menú desplegable Prioridad](/assets/images/enterprise/support/support-ticket-priority.png) + - Elige **{% data variables.product.support_ticket_priority_urgent %}** para reportar una {% if currentVersion == "free-pro-team@latest" %}falla crítica del sistema{% else %} fallas fatales del sistema, interrupciones que impactan las operaciones críticas del sistema, incidentes de seguridad, y licencias expiradas{% endif %}. + - Elige **{% data variables.product.support_ticket_priority_high %}** para reportar incidentes que impactan las operaciones de negocios, incluyendo {% if currentVersion == "free-pro-team@latest" %} eliminar datos sensibles (confirmaciones, incidentes, solicitudes de extracción, adjuntos cargados) de tus propias restauraciones de cuenta y de organización{% else %}, incidentes de rendimiento del sistema{% endif %}, o para reportar errores críticos. + - Elige **{% data variables.product.support_ticket_priority_normal %}** para {% if currentVersion == "free-pro-team@latest" %}solicitar una recuperación de cuenta o desmarcación de spam, reportar problemas de acceso de usuario{% else %}hacer solicitudes técnicas como cambios de configuración e integraciones de terceros{% endif %}, y reportar errores no críticos. + - Elige **{% data variables.product.support_ticket_priority_low %}** para hacer preguntas generales y emitir solicitudes de características nuevas, compras, capacitación, o revisiones de estado. {% if enterpriseServerVersions contains currentVersion %} +1. Desde el +menú desplegable "Serie de {% data variables.product.prodname_enterprise %}", selecciona la versión de {% data variables.product.prodname_ghe_server %} que estás utilizando. + ![{% data variables.product.prodname_enterprise %} Menú desplegable de series](/assets/images/enterprise/support/support-ticket-ghes-series.png) +{% endif %} +1. Desde el menú desplegable de "Región Global", selecciona APAC (Asia Pacífico), EMEA (Europa, Medio Oriente, y África), o América de acuerdo con tu región. ![Menú desplegable Región global](/assets/images/enterprise/support/support-ticket-global-region.png) +1. Da clic en **Agregar archivo**, posteriormente adjunta el archivo de diagnóstico que descargaste para incluir el diagnóstico en tu ticket de soporte. ![Añadir botón de archivo](/assets/images/enterprise/support/support-ticket-add-file.png) diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md new file mode 100644 index 0000000000000..73c5c2672fcc8 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md @@ -0,0 +1,5 @@ +1. Haz clic en **Submit** (enviar). + +{% if enterpriseServerVersions contains currentVersion %} +Si eliges no incluir el diagnóstico en tu ticket de soporte, puedes compartir información de dicho diagnóstico con +el soporte de {% data variables.product.prodname_enterprise %} después de emitir tu solicitud de soporte. Para obtener más información, consulta "[Proporcionar datos a Soporte de {% data variables.product.prodname_dotcom %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)."{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md new file mode 100644 index 0000000000000..218839c2de285 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md @@ -0,0 +1 @@ +Por lo general, solo harás esto si te has [contactado con el equipo de soporte](https://enterprise.github.com/support), y se te ha solicitado que lo hagas. diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/upload-support-bundle.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/upload-support-bundle.md new file mode 100644 index 0000000000000..0ad672bbf8aa9 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/upload-support-bundle.md @@ -0,0 +1 @@ +1. Visita https://enterprise.github.com/support/bundles/new y carga tu paquete de soporte. diff --git a/translations/es-ES/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md b/translations/es-ES/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md new file mode 100644 index 0000000000000..cd6497e4e62cb --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Si vas a usar una configuración de Replicación geográfica o una Agrupación de {% data variables.product.prodname_enterprise %}, debes usar el comando `ghe-cluster-support-bundle` para recuperar el paquete de soporte. Para obtener más información, consulta "[Utilidades de la línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-cluster-support-bundle)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/add-ssh-key-to-primary.md b/translations/es-ES/data/reusables/enterprise_installation/add-ssh-key-to-primary.md new file mode 100644 index 0000000000000..3d2d84ebbec36 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/add-ssh-key-to-primary.md @@ -0,0 +1 @@ +1. Para agregar una llave pública a la lista de llaves autorizadas en el aparato principal, ingresa a `https://PRIMARY-HOSTNAME/setup/settings` y agrega a la lista la llave que copiaste de la réplica. diff --git a/translations/es-ES/data/reusables/enterprise_installation/aws-recommended-instance-types.md b/translations/es-ES/data/reusables/enterprise_installation/aws-recommended-instance-types.md new file mode 100644 index 0000000000000..671a9933d95d5 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/aws-recommended-instance-types.md @@ -0,0 +1,10 @@ +Recomendamos los siguientes tipos de instancia con base en la cantidad de licencias que tengas. | +{% if enterpriseServerVersions contains currentVersion %} +| Licencias de usuario | Tipo recomendado | +|:---------------------------------------- | ----------------:| +| Prueba, Demo o 10 usuarios no frecuentes | r4.large | +| 10 - 3000 | r4.xlarge | +| 3000 - 5000 | r4.2xlarge | +| 5000 - 8000 | r4.4xlarge | +| 8000 - 10000+ | r4.8xlarge | +{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md new file mode 100644 index 0000000000000..376fb98ffce9d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -0,0 +1,37 @@ +{% data variables.product.prodname_ghe_server %} se admite en los siguientes tipos de instancias EC2. Para obtener más información, consulta [la página de AWS de resumen de tipo de instancia EC2 ](http://aws.amazon.com/ec2/instance-types/). + +| Tipo de instancia EC2 | Modelo | +| --------------------- | ---------------------------------- | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | ---------------------------------- | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | -------------------------------------------------------------------- | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | --------------------- | +| M3 | m3.xlarge, m3.2xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | ----------------------------------------------------------- | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | --------------------------------------------------------------------- | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | -------------------------------------------------------------------- | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | + +| Tipo de instancia EC2 | Modelo | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} + +| Tipo de instancia EC2 | Modelo | +| --------------------- | ------------------------ | +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/es-ES/data/reusables/enterprise_installation/changing-hostname-not-supported.md b/translations/es-ES/data/reusables/enterprise_installation/changing-hostname-not-supported.md new file mode 100644 index 0000000000000..376504605c9cb --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/changing-hostname-not-supported.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia**: No cambies el nombre de host para {% data variables.product.prodname_ghe_server %} después de la configuración inicial. Cambiar el nombre del host ocasionará un comportamiento inesperado que puede incluir y llegar hasta la interrupción del servicio. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md b/translations/es-ES/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md new file mode 100644 index 0000000000000..0deecc6cd7782 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md @@ -0,0 +1,7 @@ +Cuando bajes de categoría una mejora que ya hayas hecho, deberás utilizar un archivo de paquete de mejora con la extensión *.pkg*. No hay compatibilidad con los archivos de paquete de hotpatch con la extensión *.hpkg*. + +```shell +ghe-upgrade --allow-patch-rollback EARLIER-RELEASE-UPGRADE-PACKAGE.pkg +``` + +Se requiere que reinicies después de ejecutar el comando. Bajar de categoría una mejora previa no afecta la partición de datos, ya que las migraciones no se ejecutan en lanzamientos parchados. diff --git a/translations/es-ES/data/reusables/enterprise_installation/configuration-recognized.md b/translations/es-ES/data/reusables/enterprise_installation/configuration-recognized.md new file mode 100644 index 0000000000000..559974ab03ba2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/configuration-recognized.md @@ -0,0 +1,5 @@ +1. Una vez que la instancia se haya reiniciado completamente y que puedas acceder a ella, usa el shell administrativo para verificar el reconocimiento de la nueva configuración de recursos: +```shell +$ ssh -p 122 admin@HOSTNAME +$ ghe-system-info +``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md b/translations/es-ES/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md new file mode 100644 index 0000000000000..bcd59e9997931 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md @@ -0,0 +1 @@ +1. Copia el nombre DNS público de la máquina virtual y pégalo en un navegador de red. diff --git a/translations/es-ES/data/reusables/enterprise_installation/create-attached-storage-volume.md b/translations/es-ES/data/reusables/enterprise_installation/create-attached-storage-volume.md new file mode 100644 index 0000000000000..ede4a43925b59 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/create-attached-storage-volume.md @@ -0,0 +1 @@ +1. Crear un nuevo disco virtual para utilizarlo como un volumen adjunto de almacenamiento para los datos de tu instancia, y configurar el tamaño con base en la cantidad de licencias de usuario disponibles. diff --git a/translations/es-ES/data/reusables/enterprise_installation/create-ghe-instance.md b/translations/es-ES/data/reusables/enterprise_installation/create-ghe-instance.md new file mode 100644 index 0000000000000..9ba84aec92e9e --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/create-ghe-instance.md @@ -0,0 +1 @@ +Para crear la instancia, deberás importar la imagen del {% data variables.product.prodname_ghe_server %} a tu máquina virtual y adjuntar un volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." diff --git a/translations/es-ES/data/reusables/enterprise_installation/disable-github-pages-warning.md b/translations/es-ES/data/reusables/enterprise_installation/disable-github-pages-warning.md new file mode 100644 index 0000000000000..f03b47285bc23 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/disable-github-pages-warning.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion %} +{% warning %} + +**Advertencia:** si se inhabilita el aislamiento de subdominios, recomendamos que también inhabilites {% data variables.product.prodname_pages %} en tu empresa. No habrá forma de aislar el contenido de {% data variables.product.prodname_pages %} que suministre un usuario del resto de los datos de tu empresa. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_pages %} para tu empresa](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/)". + +{% endwarning %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md new file mode 100644 index 0000000000000..51c91b94b16e2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md @@ -0,0 +1 @@ +1. Haz clic en **Get the latest release of {% data variables.product.prodname_ghe_server %}** (Obtener el último lanzamiento del {% data variables.product.prodname_ghe_server %}). diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-license.md b/translations/es-ES/data/reusables/enterprise_installation/download-license.md new file mode 100644 index 0000000000000..3303ad4c16043 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/download-license.md @@ -0,0 +1 @@ +1. Para descargar tu archivo de licencia, haz clic en **Download license (Descargar licencia)**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-note.md b/translations/es-ES/data/reusables/enterprise_installation/download-note.md new file mode 100644 index 0000000000000..e9c7850b0b5b4 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/download-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Si habilitaste las verificaciones de actualizaciones automáticas, no necesitas descargar el paquete de actualizaciones y puedes usar el archivo que se descargó automáticamente. Para obtener más información, consulta "[Enabling automatic update checks](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)" (Habilitar verificaciones de actualizaciones automáticas). + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-package.md b/translations/es-ES/data/reusables/enterprise_installation/download-package.md new file mode 100644 index 0000000000000..c15f19033fbf9 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/download-package.md @@ -0,0 +1,4 @@ +1. Descarga el paquete de actualizaciones a {% data variables.product.product_location %} con `curl`: +```shell +admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL +``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-procedural.md b/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-procedural.md new file mode 100644 index 0000000000000..3228e7c494f93 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-procedural.md @@ -0,0 +1 @@ +1. Visita [la {% data variables.product.prodname_ghe_server %} página de descargas](https://enterprise.github.com/download). diff --git a/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md b/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md new file mode 100644 index 0000000000000..2a1353caa2b5f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md @@ -0,0 +1 @@ +Visita la [{% data variables.product.prodname_ghe_server %} Página de lanzamientos](https://enterprise.github.com/releases). Junto a la versión a la que vas a actualizar, haz clic en **Download** (Descargar), luego haz clic en la pestaña **Upgrading** (Actualización). diff --git a/translations/es-ES/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md b/translations/es-ES/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md new file mode 100644 index 0000000000000..b4f159c7d779c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md @@ -0,0 +1,4 @@ +- **Fallo de software**, ya sea debido a una falla en el sistema operativo o a aplicaciones irrecuperables. +- **Fallas del hardware**, incluido el hardware de almacenamiento, la CPU, la RAM, las interfaces de red, etc. +- **Fallas del sistema host de virtualización**, incluidos los eventos no planeados y [de mantenimiento programado en AWS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html). +- **Red cortada lógica o físicamente**, si el error de las aplicación está en una red separada no se ve impactada por la falla. diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md new file mode 100644 index 0000000000000..50d5b70a0d947 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -0,0 +1,52 @@ +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} +- [Almacenamiento](#storage) +- [CPU y memoria](#cpu-and-memory) + +#### Requisitos mínimos + +Te recomendamos utilizar configuraciones de hardware diferentes dependiendo de la cantidad de licencias de usuario que tengas para {% data variables.product.product_location %}. Si aprovisionaste más recursos que los de los requisitos mínimos, tu instancia funcionrá y escalará mejor. + +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. + +- Debes configurar por lo menos un ejecutor para los flujos de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." +- Debes configurar un almacenamiento externo de blobs. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". +- Puede que necesites configurar recursos adicionales de memoria y CPU. Los recursos adicionales que necesitas para aprovisionar a las {% data variables.product.prodname_actions %} dependen de la cantidad de flujos de trabajo que tus usuarios ejecutan simultáneamente y de los niveles de actividad de los usuarios, automatizaciones e integraciones. + + | Jobs máximos por minuto | vCPU adicionales | Memoria adicional | + |:----------------------- | ----------------:| -----------------:| + | Pruebas ligeras | 4 | 30.5 GB | + | 25 | 8 | 61 GB | + | 35 | 16 | 122 GB | + | 100 | 32 | 244 GB | + +{% endif %} + +#### Almacenamiento + +Recomendamos un SSD de alto rendimiento con operaciones de altas de entrada/salida por segundo (IOPS) y latencia baja para {% data variables.product.prodname_ghe_server %}. Las cargas de trabajo son intensivas para las I/O. Si utilizas un hipervisor de metal puro, te recomendamos adjuntar directamente el disco o utilizar un disco de una red de área de almacenamiento (SAN). + +Tu instancia requiere un disco de datos persistentes independiente del disco raíz. Para obtener más información, consulta "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)". + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". + +{% endif %} + +Puedes redimensionar el disco raíz de tu instancia si creas una instancia nueva o si utilizas una instancia existente. Para obtener más información, consulta la sección [Incrementar la capacidad de almacenamiento](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)" + +#### CPU y memoria + +{% data variables.product.prodname_ghe_server %} requiere más recursos de memoria y de CPU dependiendo de los niveles de actividad de los usuarios, automatizaciones e integraciones. + +{% data reusables.enterprise_installation.increasing-cpus-req %} + +{% warning %} + +**Advertencia:** te recomendamos que los usuarios configuren eventos de webhooks para notificar a los sistemas externos sobre la actividad en {% data variables.product.prodname_ghe_server %}. Las verificaciones automatizadas para los cambios, o el _sondeo_, impactará negativamente el rendimiento y la escalabilidad de tu instancia. Para obtener más información, consulta la sección "[Acerca de los webhooks](/github/extending-github/about-webhooks)". + +{% endwarning %} + +Puedes incrementar los recursos de memoria o de CPU para tu instancia. Para obtener más información, consulta "[Aumentar los recursos de memoria o la CPU](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md new file mode 100644 index 0000000000000..662b594a56c9d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md @@ -0,0 +1,49 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +{% note %} + +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." + +{% endnote %} +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | +|:---------------------------------------- | -------------------------------------------:| ---------------------------------------------------:| ---------------------------------------------------:| -------------------:| +| Prueba, Demo o 10 usuarios no frecuentes | 2
o [**4**](#optional-features) | 16 GB
o [**32 GB**](#optional-features) | 100 GB
o [**150 GB**](#optional-features) | 200 GB | +| 10-3000 | 4
o [**8**](#optional-features) | 32 GB
o [**48 GB**](#optional-features) | 250 GB
o [**300 GB**](#optional-features) | 200 GB | +| 3000-5000 | 8
o [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12
o [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16
o [**20**](#optional-features) | 128 GB
o [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + +| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | +|:---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------:| -------------------:| +| Prueba, Demo o 10 usuarios no frecuentes | 2{% if currentVersion == "enterprise-server@2.22" %}
o [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
o [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
o [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | +| 10-3000 | 4{% if currentVersion == "enterprise-server@2.22" %}
o [**8**](#beta-features-in-github-enterprise-server-222){% endif %} | 32 GB{% if currentVersion == "enterprise-server@2.22" %}
o [**48 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 250 GB{% if currentVersion == "enterprise-server@2.22" %}
o [**300 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | +| 3000-5000 | 8{% if currentVersion == "enterprise-server@2.22" %}
o [**12**](#beta-features-in-github-enterprise-server-222){% endif %} | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
o [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
o [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
o [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | + +{% endif %} + +Para obtener más información sobre el ajuste de recursos para una instancia existente, consulta las secciones "[Incrementar la capacidad de almacenamiento](/enterprise/admin/installation/increasing-storage-capacity)" e "[Incrementar los recursos de memoria o de CPU](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Características beta en {% data variables.product.prodname_ghe_server %} 2.22 + +Puedes registrarte para las características del beta disponibles en {% data variables.product.prodname_ghe_server %} 2.22 tales como las {% data variables.product.prodname_actions %}, el {% data variables.product.prodname_registry %}, y el {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta las [notas de lanzamiento para la serie 2.22](https://enterprise.github.com/releases/series/2.22#release-2.22.0) en el sitio web de {% data variables.product.prodname_enterprise %}. + +Si habilitas las características beta para {% data variables.product.prodname_ghe_server %} 2.22, tu instancia requerirá de recursos de hardware adicionales. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". + +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". + +{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/hotpatching-explanation.md b/translations/es-ES/data/reusables/enterprise_installation/hotpatching-explanation.md new file mode 100644 index 0000000000000..d08b46f274ecd --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/hotpatching-explanation.md @@ -0,0 +1 @@ +Puedes mejorar {% data variables.product.prodname_ghe_server %} al último lanzamiento parchado utilizando un hotpatch, lo cual no requerirá una ventana de mantenimiento y, habitualmente, no requiere un reinicio. Puedes utilizar los hotpatches para subir de categoría a un nuevo lanzamiento parchado, pero no a un lanzamiento de características. Por ejemplo, puedes mejorar de `2.10.1` a `2.10.5` porque pertenecen a la misma serie de características, pero no de `2.10.9` a `2.11.0`, porque están en una serie de características diferente. diff --git a/translations/es-ES/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/es-ES/data/reusables/enterprise_installation/image-urls-viewable-warning.md new file mode 100644 index 0000000000000..c0afca4084fd7 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** Si agregas un adjunto de imagen a una solicitud de cambios o a un comentario de una propuesta, cualquiera podrá ver la URL anonimizada de la imagen sin autenticarse{% if enterpriseServerVersions contains currentVersion %}, aún si la solicitud de cambios se encuentra en un repositorio privado o si se habilita el modo privado. Para prevenir el acceso no autorizado a las imágenes, asegúrate de restringir el acceso de red a los sistemas que sirven las imágenes, incluyendo {% data variables.product.product_location %}{% endif %}.{% if currentVersion == "github-ae@latest" %} Para prevenir el acceso no autorizado a las URL de imagen en {% data variables.product.product_name %}, considera restringir el tráfico de red a tu empresa. Para obtener más información, consulta la sección "[Restringir el tráfico de red para tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)".{% endif %} + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/increasing-cpus-req.md b/translations/es-ES/data/reusables/enterprise_installation/increasing-cpus-req.md new file mode 100644 index 0000000000000..bce8bbba900f2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/increasing-cpus-req.md @@ -0,0 +1 @@ +Cuando incrementas tus recursos de CPU, te recomendamos agregar por lo menos 6.5 GB de memoria para cada vCPU (hasta 16 vCPU) que aprovisiones para la instancia. Cuando utilizas más de 16 CPU, no necesitas agregar 6.5 GB de memoria para cada uno, pero debes monitorear tu instancia para garantizar que tenga memoria suficiente. diff --git a/translations/es-ES/data/reusables/enterprise_installation/instance-will-restart-automatically.md b/translations/es-ES/data/reusables/enterprise_installation/instance-will-restart-automatically.md new file mode 100644 index 0000000000000..eacd65c029c95 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/instance-will-restart-automatically.md @@ -0,0 +1 @@ +4. La instancia se reiniciará automáticamente. diff --git a/translations/es-ES/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md b/translations/es-ES/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md new file mode 100644 index 0000000000000..4de02dd0f8ae6 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md @@ -0,0 +1 @@ +Para utilizar la automatización de Let's Encrypt, tu aplicativo debe configurarse con un nombre de host al que se pueda acceder públicamente mediante HTTP. También se le debe permitir al aplicativo realizar conexiones HTTPS salientes. diff --git a/translations/es-ES/data/reusables/enterprise_installation/monitoring-replicas.md b/translations/es-ES/data/reusables/enterprise_installation/monitoring-replicas.md new file mode 100644 index 0000000000000..c49b48636ad3a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/monitoring-replicas.md @@ -0,0 +1,8 @@ +Puedes verificar la disponibilidad del {% data variables.product.prodname_ghe_server %} al controlar el código de estado que devuelve la URL `https://HOSTNAME/status`. Un aparato que puede servir el tráfico de usuario devolverá un código de estado de `200` (OK). Un aparato puede devolver un `503` (Servicio no disponible) por distintas razones: + - El aparato es una réplica pasiva, como la réplica en una configuración de disponibilidad alta de dos nodos. + - El aparato está en modo de mantenimiento. + - El aparato es parte de una configuración de replicación geográfica, pero es una réplica inactiva. + +También puedes utilizar el Tablero de resumen de replicación disponible en: + +`https://HOSTNAME/setup/replication` diff --git a/translations/es-ES/data/reusables/enterprise_installation/necessary_ports.md b/translations/es-ES/data/reusables/enterprise_installation/necessary_ports.md new file mode 100644 index 0000000000000..fdc9d2bf0b534 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/necessary_ports.md @@ -0,0 +1,12 @@ +| Port (Puerto) | Servicio | Descripción | +| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 22 | SSH | Git a través de acceso SSH. Se admite clonar, extraer y subir operaciones a repositorios privados/públicos. | +| 25 | SMTP | SMTP con soporte de encriptación (STARTTLS). | +| 80 | HTTP | Acceso a aplicación web. *Todas las solicitudes se redireccionan al puerto HTTPS cuando se habilita SSL.* | +| 122 | SSH | Acceso a shell de instancia. *El puerto predeterminado (22) se dedica a la aplicación de git+el tráfico de red ssh.* | +| 161/UDP | SNMP | Se requiere para operar el protocolo de revisión de red. | +| 443 | HTTPS | Aplicación web y Git a través de acceso HTTPS. | +| 1194/UDP | VPN | Túnel de red de replicación segura en la configuración de alta disponibilidad. | +| 8080 | HTTP | {% data variables.enterprise.management_console %} basada en la web de texto simple. *No se requiere excepto que el SSL esté inhabilitado de forma manual.* | +| 8443 | HTTPS | {% data variables.enterprise.management_console %} seguro basada en la web. *Requerido para la instalación y la configuración básicas.* | +| 9418 | Git | Puerto simple de protocolo de Git. Únicamente clonar y extraer operaciones a repositorios públicos. *Comunicación de red sin cifrar.* {% data reusables.enterprise_installation.when-9418-necessary %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/open-vm-console-start.md b/translations/es-ES/data/reusables/enterprise_installation/open-vm-console-start.md new file mode 100644 index 0000000000000..2d0b8dfed887f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/open-vm-console-start.md @@ -0,0 +1,2 @@ +1. Abre la consola de la máquina virtual utilizando tus herramientas de plataforma de virtualización. ![Consola de {% data variables.product.prodname_enterprise %}](/assets/images/enterprise/network-configuration/virtual-machine-console.png) +2. Para iniciar la configuración de red, presiona **S**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/promoting-a-replica.md b/translations/es-ES/data/reusables/enterprise_installation/promoting-a-replica.md new file mode 100644 index 0000000000000..df1334981488f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/promoting-a-replica.md @@ -0,0 +1 @@ +Promover una réplica no configura la replicación para aplicativos existentes automáticamente. Despues de promoverla, si así lo quieres, puedes configurar la replicacion desde el nuevo aplicativo principal hacia uno existente y hacia el aplicativo primario previo. diff --git a/translations/es-ES/data/reusables/enterprise_installation/replica-ssh.md b/translations/es-ES/data/reusables/enterprise_installation/replica-ssh.md new file mode 100644 index 0000000000000..a2206d46b0a99 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/replica-ssh.md @@ -0,0 +1,4 @@ +1. Conéctate a la instancia réplica a través de SSH como el usuario "admin" en el puerto 122: +```shell +$ ssh -p 122 admin@replica-host +``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/replica-verify.md b/translations/es-ES/data/reusables/enterprise_installation/replica-verify.md new file mode 100644 index 0000000000000..3c937a2b372f4 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/replica-verify.md @@ -0,0 +1,5 @@ +1. Verifica la mejora ejecutando: + + ```shell + $ ghe-version + ``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/replication-command.md b/translations/es-ES/data/reusables/enterprise_installation/replication-command.md new file mode 100644 index 0000000000000..22a2babcab948 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/replication-command.md @@ -0,0 +1,9 @@ +1. Para comenzar la replicación de las bases de datos, utiliza el comando `ghe-repl-start`. + ```shell + $ ghe-repl-start + ``` + {% warning %} + + **Advertencia:** `ghe-repl-start` causa una breve interrupción en el servidor principal, durante la cual los usuarios pueden ver errores internos del servidor. Para proporcionar un mensaje más amigable, ejecuta `ghe-maintenance -s` en el nodo principal antes de ejecutar `ghe-repl-start` en el nodo réplica para poner la aplicación en modo de mantenimiento. Una vez que se inicie la replicación, deshabilita el modo de mantenimiento con `ghe-maintenance -u`. + + {% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/replication-status.md b/translations/es-ES/data/reusables/enterprise_installation/replication-status.md new file mode 100644 index 0000000000000..a8928a2ed1716 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/replication-status.md @@ -0,0 +1 @@ +1. En la instancia replicada, para garantizar que se estén ejecutando correctamente los servicios de replicación, ejecuta `ghe-repl-status`. Este comando devolverá un `OK` para todos los servicios cuando exista una replicación exitosa en progreso y la réplica se haya mejorado. diff --git a/translations/es-ES/data/reusables/enterprise_installation/request-a-trial.md b/translations/es-ES/data/reusables/enterprise_installation/request-a-trial.md new file mode 100644 index 0000000000000..f8c205ead4c01 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/request-a-trial.md @@ -0,0 +1 @@ +Puedes solicitar una prueba para evaluar {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "Configurar una prueba de {% data variables.product.prodname_ghe_server %}". diff --git a/translations/es-ES/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md b/translations/es-ES/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md new file mode 100644 index 0000000000000..b844e1ed5464b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md @@ -0,0 +1 @@ +3. En la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), configura y guarda a configuración que desees. diff --git a/translations/es-ES/data/reusables/enterprise_installation/software-license.md b/translations/es-ES/data/reusables/enterprise_installation/software-license.md new file mode 100644 index 0000000000000..fb8cf81de8f64 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/software-license.md @@ -0,0 +1 @@ +Debes tener un archivo de licencia de {% data variables.product.prodname_enterprise %}. Para descargar un archivo de licencia existente o solicitar una licencia de prueba, visita [enterprise.github.com](https://enterprise.github.com/download). Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license/)". diff --git a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md new file mode 100644 index 0000000000000..44b21c113c6f0 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md @@ -0,0 +1,4 @@ +1. SSH en {% data variables.product.product_location %}. +```shell +$ ssh -p 122 admin@HOSTNAME +``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-target-instance.md b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-target-instance.md new file mode 100644 index 0000000000000..b8e68c357849a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-target-instance.md @@ -0,0 +1,4 @@ +1. Como administrador de sitio, [Entra por SSH en tu instancia destino de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). +```shell +$ ssh -p 122 admin@HOSTNAME +``` diff --git a/translations/es-ES/data/reusables/enterprise_installation/start-replication.md b/translations/es-ES/data/reusables/enterprise_installation/start-replication.md new file mode 100644 index 0000000000000..102b69218e385 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/start-replication.md @@ -0,0 +1 @@ +1. En la instancia réplica, para comenzar la replicación, ejecuta `ghe-repl-start`. diff --git a/translations/es-ES/data/reusables/enterprise_installation/terminating-tls.md b/translations/es-ES/data/reusables/enterprise_installation/terminating-tls.md new file mode 100644 index 0000000000000..6873a1b51c950 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/terminating-tls.md @@ -0,0 +1,5 @@ +{% warning %} + + **Advertencia:** cuando se termina una conexión HTTPS en un balanceador de carga, las solicitudes de éste hacia {% data variables.product.prodname_ghe_server %} necesitarán utilizar HTTPS. Bajar la conexión de categoría a HTTP no es compatible. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md b/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md new file mode 100644 index 0000000000000..153a892f54d1a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md @@ -0,0 +1 @@ +2. En el prompt, carga tu archivo de licencia y configura una contraseña de consola de administración. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license/)". diff --git a/translations/es-ES/data/reusables/enterprise_installation/visit-your-instance.md b/translations/es-ES/data/reusables/enterprise_installation/visit-your-instance.md new file mode 100644 index 0000000000000..6b4488403cabd --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/visit-your-instance.md @@ -0,0 +1 @@ +1. Da clic en **Visitar tu instancia**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/vm-console-done.md b/translations/es-ES/data/reusables/enterprise_installation/vm-console-done.md new file mode 100644 index 0000000000000..2febe6dc2713a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/vm-console-done.md @@ -0,0 +1 @@ +1. Para terminar tu configuración, presiona **D**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/warning-on-scaling.md b/translations/es-ES/data/reusables/enterprise_installation/warning-on-scaling.md new file mode 100644 index 0000000000000..c92642b612687 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/warning-on-scaling.md @@ -0,0 +1,5 @@ +{% warning %} + +**Nota:** Siempre puedes mejorar tu CPU o memoria si cambias tu instancia de tamaño. Sin embargo, ya que cambiar de tamaño tu CPU o memoria requiere tiempo de inactividad para tus usuarios, recomendamos contar con recursos de sobra para compensar un escalamiento. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md b/translations/es-ES/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md new file mode 100644 index 0000000000000..84d1380fed9f5 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** El proceso para destinar nuevos recursos de sistema varía dependiendo de la plataforma de virtualización y tipo de recurso. Siempre deberás configurar el monitoreo y las alertas de los recursos clave del sistema. Para obtener más información, consulta la sección "[Monitorear tu aplicativo de {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-your-github-enterprise-server-appliance/)". + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/when-9418-necessary.md b/translations/es-ES/data/reusables/enterprise_installation/when-9418-necessary.md new file mode 100644 index 0000000000000..4c22f9bffed3a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/when-9418-necessary.md @@ -0,0 +1 @@ +Si habilitaste el modo privado en tu instancia, entonces solo se requerirá abrir este puerto si también habilitas el acceso de lectura anónimo para Git. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_management_console/access-monitoring.md b/translations/es-ES/data/reusables/enterprise_management_console/access-monitoring.md new file mode 100644 index 0000000000000..a09820565cd80 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/access-monitoring.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Monitoreo**. ![Pestaña de monitoreo](/assets/images/enterprise/management-console/monitoring-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/actions.md b/translations/es-ES/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..90b04ef08fd3b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Acciones**. ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..0e86b7b60469f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. La licencia de {% data variables.product.prodname_advanced_security %} te permite acceder, a ti y a tus usuarios, a las características que te permiten añadir seguridad a tus repositorios ya tu código. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md new file mode 100644 index 0000000000000..35adedc459a1d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_advanced_security %}**. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/authentication-password.md b/translations/es-ES/data/reusables/enterprise_management_console/authentication-password.md new file mode 100644 index 0000000000000..ae711954653c8 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/authentication-password.md @@ -0,0 +1 @@ +En "Contraseña de autenticación", escribe la contraseña de autenticación. diff --git a/translations/es-ES/data/reusables/enterprise_management_console/authentication-protocol.md b/translations/es-ES/data/reusables/enterprise_management_console/authentication-protocol.md new file mode 100644 index 0000000000000..ca04ba0c5829d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/authentication-protocol.md @@ -0,0 +1 @@ +En la parte derecha de "Contraseña de autenticación", en el menú desplegable de **Protocolo**, da clic en el protocolo de autenticación que quieras utilizar. diff --git a/translations/es-ES/data/reusables/enterprise_management_console/authentication.md b/translations/es-ES/data/reusables/enterprise_management_console/authentication.md new file mode 100644 index 0000000000000..853b5bf94ef0f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/authentication.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Autenticación**. ![Pestaña de autenticación en la barra lateral de configuración](/assets/images/enterprise/management-console/sidebar-authentication.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md new file mode 100644 index 0000000000000..7ea6837515b95 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md @@ -0,0 +1 @@ +Un equipo que se encuentra [sincronizado a un grupo LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) se indica con una insignia de LDAP especial. La lista de miembros para un equipo de LDAP sincronizado únicamente se puede administrar desde el grupo LDAP al que está mapeado. diff --git a/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..47f08d9681396 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia**: El cambiar esta configuración ocasionará que {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} se reinicie. Debes calcular este cambio con cuidado para minimizar el tiempo de inactividad. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_management_console/enable-snmp.md b/translations/es-ES/data/reusables/enterprise_management_console/enable-snmp.md new file mode 100644 index 0000000000000..50a596de52363 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/enable-snmp.md @@ -0,0 +1 @@ +1. Debajo de "Monitoreando", selecciona **Habilitar SNMP**. ![Botón para habilitar SNMP](/assets/images/enterprise/management-console/enable-snmp.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/hostname-menu-item.md b/translations/es-ES/data/reusables/enterprise_management_console/hostname-menu-item.md new file mode 100644 index 0000000000000..2a77561048961 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/hostname-menu-item.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, da clic en **Nombre de Host**. ![Pestaña de nombre de host en la barra lateral](/assets/images/enterprise/management-console/hostname-sidebar.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/pages-tab.md b/translations/es-ES/data/reusables/enterprise_management_console/pages-tab.md new file mode 100644 index 0000000000000..a2700d139ec12 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/pages-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Páginas**. ![Barra lateral de páginas](/assets/images/enterprise/management-console/sidebar-pages.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/privacy.md b/translations/es-ES/data/reusables/enterprise_management_console/privacy.md new file mode 100644 index 0000000000000..db9d6f7b35010 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/privacy.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Privacidad**. ![Pestaña de privacidad en la barra lateral de configuración](/assets/images/enterprise/management-console/sidebar-privacy.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md b/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md new file mode 100644 index 0000000000000..20de5c6bf9e0e --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md @@ -0,0 +1,2 @@ +1. Debajo de la barra lateral izquierda, da clic en **Guardar configuración**. ![El botón de guardar en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png) +1. Espera a que la configuración se ejecute por completo. diff --git a/translations/es-ES/data/reusables/enterprise_management_console/select-tls-only.md b/translations/es-ES/data/reusables/enterprise_management_console/select-tls-only.md new file mode 100644 index 0000000000000..39a7185d4489b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/select-tls-only.md @@ -0,0 +1 @@ +1. Selecciona **Únicamente TLS (recomendado)**. ![Casilla para escoger únicamente TLS](/assets/images/enterprise/management-console/tls-only.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/support-link.md b/translations/es-ES/data/reusables/enterprise_management_console/support-link.md new file mode 100644 index 0000000000000..e6f57ebd39b81 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/support-link.md @@ -0,0 +1 @@ +4. En la parte superior derecha de {% data variables.enterprise.management_console %}, da clic en **Soporte**. ![Botón para acceder al área de soporte](/assets/images/enterprise/management-console/support-link.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/test-domain-settings-failure.md b/translations/es-ES/data/reusables/enterprise_management_console/test-domain-settings-failure.md new file mode 100644 index 0000000000000..f439c9305515f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/test-domain-settings-failure.md @@ -0,0 +1 @@ +1. Si no ves una tilde verde al costado de todas las entradas, revisa tu configuración para los elementos de configuración que hayan fallado. Para obtener más información, consulta la sección "[Configurar los servidores de nombre de DNS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/)". ![Tabla mostrando el estado de las configuraciones de DNS y SSL](/assets/images/enterprise/management-console/domain-dns-ssl-settings-check.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/type-management-console-password.md b/translations/es-ES/data/reusables/enterprise_management_console/type-management-console-password.md new file mode 100644 index 0000000000000..c00a2aa8ab75d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/type-management-console-password.md @@ -0,0 +1 @@ +1. Si se te solicita, teclea tu contraseña de {% data variables.enterprise.management_console %}. ![Pantalla de desbloqueo de {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/unlock-password.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/updates-tab.md b/translations/es-ES/data/reusables/enterprise_management_console/updates-tab.md new file mode 100644 index 0000000000000..da57a34276405 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/updates-tab.md @@ -0,0 +1 @@ +1. En la parte superior de {% data variables.enterprise.management_console %}, da clic en **Actualizaciones**. ![Actualiza el elemento del menú](/assets/images/enterprise/management-console/updates_tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/username_normalization.md b/translations/es-ES/data/reusables/enterprise_management_console/username_normalization.md new file mode 100644 index 0000000000000..18e29d7f39c7c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/username_normalization.md @@ -0,0 +1,5 @@ +Los nombres de usuario del {% data variables.product.prodname_ghe_server %} únicamente pueden contener caracteres alfanuméricos y rayas (`-`). El {% data variables.product.prodname_ghe_server %} convertirá en raya cualquier caracter no alfanumérico en el nombre de tu cuenta de usuario. Por ejemplo, un nombre de usuario `gregory.st.john` se convertirá en `gregory-st-john`. Nota que los nombres de usuarios normalizados tampoco pueden comenzar o terminar con una raya. Tampoco pueden contener dos rayas seguidas. + +Los nombres de usuarios creados a partir de direcciones de correo electrónico se crean con los caracteres normalizados que preceden al caracter `@`. + +Si múltiples cuentas se normalizan en el mismo nombre de usuario de {% data variables.product.prodname_ghe_server %}, solo se crea la primera cuenta de usuario. Los siguientes usuarios con el mismo nombre de usuario no podrán registrarse. diff --git a/translations/es-ES/data/reusables/enterprise_management_console/username_normalization_sample.md b/translations/es-ES/data/reusables/enterprise_management_console/username_normalization_sample.md new file mode 100644 index 0000000000000..0c7419d841df0 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_management_console/username_normalization_sample.md @@ -0,0 +1,10 @@ +Esta tabla brinda ejemplos de cómo se normalizan los nombres de usuarios en el {% data variables.product.prodname_ghe_server %}: + +| Nombre de usuario | Nombre de usuario normalizado | Resultado | +| ---------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------- | +| Ms.Bubbles | `ms-bubbles` | El nombre de usuario se crea correctamente. | +| !Ms.Bubbles | `-ms-bubbles` | No se crea este nombre de usuario debido a que comienza con una raya. | +| Ms.Bubbles! | `ms-bubbles-` | No se crea este nombre de usuario debido a que termina con una raya. | +| Ms!!Bubbles | `ms--bubbles` | No se crea este nombre de usuario debido a que contiene dos rayas seguidas. | +| Ms!Bubbles | `ms-bubbles` | No se crea este nombre de usuario. A pesar de que el nombre de usuario normalizado es válido, ya existía. | +| Ms.Bubbles@example.com | `ms-bubbles` | No se crea este nombre de usuario. A pesar de que el nombre de usuario normalizado es válido, ya existía. | diff --git a/translations/es-ES/data/reusables/enterprise_migrations/exclude-file-attachments.md b/translations/es-ES/data/reusables/enterprise_migrations/exclude-file-attachments.md new file mode 100644 index 0000000000000..ff253121db829 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/exclude-file-attachments.md @@ -0,0 +1 @@ +Los archivos adjuntos pueden resultar muy grandes y es posible que sobrecarguen tu archivo de migración final de manera innecesaria. diff --git a/translations/es-ES/data/reusables/enterprise_migrations/fork-persistence.md b/translations/es-ES/data/reusables/enterprise_migrations/fork-persistence.md new file mode 100644 index 0000000000000..b48fdc0c1810d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/fork-persistence.md @@ -0,0 +1,5 @@ +{% tip %} + +**Nota:** Las relaciones de las bifurcaciones no persisten después de una migración. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md b/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md new file mode 100644 index 0000000000000..f543d86e1d4e4 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md @@ -0,0 +1,6 @@ +{% tip %} + +**Nota:**Cerrar un repositorio previene que los usuarios suban información al mismo o que modifiquen sus recursos como informes de problemas, etiquetas, hitos, wikis, y comentarios. Los nuevos equipos y colaboradores no podrán asociarse con un repositorio cerrado. + +Si estás realizando una ejecución de prueba, no necesitas cerrar el repositorio. En el resto de los casos, se recomienda ampliamente. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)". +{% endtip %} diff --git a/translations/es-ES/data/reusables/enterprise_migrations/make-a-list.md b/translations/es-ES/data/reusables/enterprise_migrations/make-a-list.md new file mode 100644 index 0000000000000..eff3aa58c7415 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/make-a-list.md @@ -0,0 +1 @@ +1. Para minimizar los tiempos de inactividad, haz una lista de repositorios que deseas exportar desde la instancia de origen. Puedes agregar múltiples repositorios a una exportación a la vez usando un archivo de texto que muestra la URL de cada repositorio en una línea separada. diff --git a/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md new file mode 100644 index 0000000000000..924da690a0d12 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -0,0 +1 @@ +1. Para importar los datos de migración archivados a una instancia de {% data variables.product.prodname_ghe_server %} , consulta "[Importando datos de migración a {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". diff --git a/translations/es-ES/data/reusables/enterprise_migrations/review-the-import-csv.md b/translations/es-ES/data/reusables/enterprise_migrations/review-the-import-csv.md new file mode 100644 index 0000000000000..408f1efe1819f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/review-the-import-csv.md @@ -0,0 +1,16 @@ +1. Revisa el archivo (CSV) separado por coma en `/PATH/REPO-NAME.git/git-import/raw-authors.csv`. Debería contener estas columnas: + - `ID`: el autor tal como se almacena en el repositorio original, seguido de un identificador único + - `NOMBRE`: el autor tal como se almacena en el repositorio original + + Para mapear autores desde el repositorio original a una dirección de correo electrónico y nombre, crea un nuevo archivo CSV con las columnas `ID,(ignorado),GIT_EMAIL,GIT_NAME`, que reemplace la información de autor por "ID" con "GIT_EMAIL" y "GIT_NAME". + + + #### Ejemplo: + + - ID del autor original: `octocat@111111-2222-3333-4444-55555555555` + - Nueva dirección de correo electrónico: `octocat@github.com` + - Nuevo nombre: `The Octocat` + + Para mapear el autor original a un nuevo usuario de Git, el archivo CSV debería incluir la línea: + + `octocat@111111-2222-3333-4444-55555555555, ,octocat@github.com,The Octocat` diff --git a/translations/es-ES/data/reusables/enterprise_migrations/specify-staging-path.md b/translations/es-ES/data/reusables/enterprise_migrations/specify-staging-path.md new file mode 100644 index 0000000000000..a32966f9c2634 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/specify-staging-path.md @@ -0,0 +1 @@ +Para especificar en donde se deben escalar los archivos de migración de acuerdo con la etapa, anexa el comando con `--staging-path=/full/staging/path`. La ruta predeterminada es `/data/user/tmp`. diff --git a/translations/es-ES/data/reusables/enterprise_migrations/token-generation.md b/translations/es-ES/data/reusables/enterprise_migrations/token-generation.md new file mode 100644 index 0000000000000..0729298906b2d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/token-generation.md @@ -0,0 +1 @@ +[Genera un acceso de token](/enterprise/user/articles/creating-an-access-token-for-command-line-use/) con los alcances `repo` y `admin:org` diff --git a/translations/es-ES/data/reusables/enterprise_migrations/unlocking-on-instances.md b/translations/es-ES/data/reusables/enterprise_migrations/unlocking-on-instances.md new file mode 100644 index 0000000000000..3e4f3c23cbfdc --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_migrations/unlocking-on-instances.md @@ -0,0 +1,5 @@ +1. Libera todos los repositorios importados con el comando `ghe-migrator unlock`. Nececitarás tu GUID de Migración: +```shell +$ ghe-migrator unlock -g MIGRATION_GUID +> Unlocked octo-org/octo-project +``` diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md new file mode 100644 index 0000000000000..4e1057532ce2b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md @@ -0,0 +1 @@ +SSH access allows you to run the {% data variables.product.product_name %} command line utilities to troubleshoot, run backups, and configure replication. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md new file mode 100644 index 0000000000000..8c622226c61c5 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md @@ -0,0 +1 @@ +You can use the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md new file mode 100644 index 0000000000000..bab0827c406a6 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md @@ -0,0 +1 @@ +You can use the site admin dashboard to manage users, organizations, and repositories in your enterprise directly in {% data variables.product.product_name %}. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/access-settings.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/access-settings.md new file mode 100644 index 0000000000000..f7650f8125284 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/access-settings.md @@ -0,0 +1 @@ +1. Desde una cuenta administrativa en {% data variables.product.product_name %}, da clic en {% octicon "rocket" aria-label="The rocket ship" %} la esquina superior derecha de cualquier página. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-tab.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-tab.md new file mode 100644 index 0000000000000..f4ab25ee824d8 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Admin (Administrador)**. ![Herramientas de administrador](/assets/images/enterprise/site-admin-settings/user/user-admin-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-top-tab.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-top-tab.md new file mode 100644 index 0000000000000..385cf4c63f66a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/admin-top-tab.md @@ -0,0 +1 @@ +1. En la parte superior derecha de la página, da clic en {% octicon "gear" %} **Admin**. ![Herramientas de administrador](/assets/images/enterprise/site-admin-settings/user/user-admin-tab-top.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/business.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/business.md new file mode 100644 index 0000000000000..0ee7016f60d86 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/business.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Descripción de empresa{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %}**. ![Pestaña de{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} descripción de la empresa{% endif %} en la configuración administrativa del sitio](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-preview.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-preview.md new file mode 100644 index 0000000000000..faeb6063c919e --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-preview.md @@ -0,0 +1 @@ +1. Para ver el mensaje, haga clic en **Preview (Vista previa)**. diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-repo.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-repo.md new file mode 100644 index 0000000000000..b53dab7634d9c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-repo.md @@ -0,0 +1 @@ +1. En los resultados de búsqueda, da clic en el nombre del repositorio. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-repo.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user-or-org.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user-or-org.md new file mode 100644 index 0000000000000..a31e8ca650d1f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user-or-org.md @@ -0,0 +1 @@ +1. En los resultados de búsqueda, da clic en el nombre de usuario u organización. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-user.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user.md new file mode 100644 index 0000000000000..9906e6913f462 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/click-user.md @@ -0,0 +1 @@ +1. En los resultados de búsqueda, da clic en el nombre del usuario. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-user.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md new file mode 100644 index 0000000000000..5118fb574c169 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md @@ -0,0 +1 @@ +{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) es una extensión de código abierto para Git que te permite trabajar con archivos grandes de la misma manera que con otros archivos de texto. diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md new file mode 100644 index 0000000000000..99dd552423930 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md @@ -0,0 +1 @@ +El umbral de inactividad es cuánto tiempo debe estar inactivo un usuario para considerarse como inactivo. El umbral de inactividad predeterminado es de 90 días, sin embargo, puedes personalizar este umbral para {% data variables.product.product_location %}. diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md new file mode 100644 index 0000000000000..a7d1a0950a7db --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md @@ -0,0 +1 @@ +1. Debajo de "{% data variables.large_files.product_name_short %}", da clic en **Habilitar** o **Inhabilitar**. ![Botón de inhabilitar](/assets/images/enterprise/management-console/git-lfs-toggle.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md new file mode 100644 index 0000000000000..6cc33bcb2eca0 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md @@ -0,0 +1 @@ +1. Teclea el nombre de usuario y dirección de correo electrónico de cada cuenta de usuario que quieras crear, posteriormente, da clic en **Generar un enlace para restablecer la contraseña**. ![Botón de generar un enlace para restablecer la contraseña](/assets/images/enterprise/site-admin-settings/generate-password-reset-link-button.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md new file mode 100644 index 0000000000000..73540910b0002 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Invitar usuario**. ![Pestaña de invitar usuario en la consola de administrador del sitio](/assets/images/enterprise/site-admin-settings/invite-user.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md new file mode 100644 index 0000000000000..7921b165d5f82 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md @@ -0,0 +1 @@ +Para ver los repositorios con acceso de lectura Git anónimo habilitado, filtra la lista de repositorios en el tablero de administración del sitio. diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md new file mode 100644 index 0000000000000..93cc041dc802d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** cuando el aplicativo se encuentre en modo de mantenimiento, la URL `https://HOSTNAME/status` devolverá un código de estado `503` (Servicio no disponible). Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/management-console.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/management-console.md new file mode 100644 index 0000000000000..af582499a004b --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/management-console.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **{% data variables.enterprise.management_console %}**. ![pestaña {% data variables.enterprise.management_console %} en la barra lateral izquierda](/assets/images/enterprise/management-console/management-console-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..eed05a84c98c4 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Haz clic en **Guardar cambios**. ![Botón Editar mensaje](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/override-policy.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/override-policy.md new file mode 100644 index 0000000000000..34d0fe8b02510 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/override-policy.md @@ -0,0 +1,5 @@ +{% tip %} + +**Nota:** Cada repositorio hereda automáticamente la configuración predeterminada de la organización o usuario al que pertenece. No puedes invalidar la configuración predeterminada si el dueño del repositorio ha requerido dicha configuración en todos sus repositorios. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/packages-tab.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/packages-tab.md new file mode 100644 index 0000000000000..77ff9ecf5db66 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/packages-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Paquetes**. ![Pestaña de paquetes en la barra lateral de la consola de administración](/assets/images/enterprise/site-admin-settings/management-console-packages-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md new file mode 100644 index 0000000000000..6afb5ae6da886 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md @@ -0,0 +1 @@ +1. En el campo de búsqueda, teclea el nombre del repositorio y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/save-changes.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/save-changes.md new file mode 100644 index 0000000000000..bf5b72a3d3daa --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/save-changes.md @@ -0,0 +1 @@ +1. En la parte inferior de la página, da clic en **Guardar cambios**. ![Guardar cambios](/assets/images/enterprise/site-admin-settings/save-changes-button.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md new file mode 100644 index 0000000000000..97356743fc22c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md @@ -0,0 +1 @@ +1. En el campo de búsqueda, teclea el nombre del usuario u organización y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md new file mode 100644 index 0000000000000..22e56e3340fb2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md @@ -0,0 +1 @@ +1. En el campo de búsqueda, teclea el nombre de usuario y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/security-tab.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/security-tab.md new file mode 100644 index 0000000000000..5c26b1060f69d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/security-tab.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de la página, haz clic en {% octicon "shield" aria-label="The shield" %} **Security (Seguridad)**. ![Pestaña de seguridad](/assets/images/enterprise/site-admin-settings/repo/repo-security-top-tab.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/sign-in.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/sign-in.md new file mode 100644 index 0000000000000..c07605cc38571 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/sign-in.md @@ -0,0 +1 @@ +1. Ingresa en {% data variables.product.product_location %} a través de `http(s)://HOSTNAME/login`. diff --git a/translations/es-ES/data/reusables/enterprise_user_management/2fa_is_available.md b/translations/es-ES/data/reusables/enterprise_user_management/2fa_is_available.md new file mode 100644 index 0000000000000..77ebf6dca59ea --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/2fa_is_available.md @@ -0,0 +1 @@ +Cuando utilices LDAP o una autenticación integrada, la autenticación de dos factores será compatible. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada. diff --git a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md new file mode 100644 index 0000000000000..c832520e8471a --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md @@ -0,0 +1 @@ +Opcionalmente, selecciona **Permitir autenticación integrada** para invitar a los usuarios a utilizar la autenticación integrada si no pertenecen a el proveedor de identidad de {% data variables.product.product_location %}. diff --git a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md new file mode 100644 index 0000000000000..9eaef9dc01de7 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md @@ -0,0 +1 @@ +Si quieres autenticar usuarios sin agregarlos a tu proveedor de identidad, puedes configurar la autenticación integrada. Para obtener más información, consulta "[Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md new file mode 100644 index 0000000000000..dc896f8db47ef --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md @@ -0,0 +1,5 @@ +{% warning %} + +**Nota:** Si habilitas al acceso de lectura anónimo de Git, eres responsable de todos los accesos y usos de esta característica. {% data variables.product.company_short %} no será responsable de ningún acceso no deseado o uso indebido de la función. También puede que no utilices esta característica para violar tu licencia desde {% data variables.product.company_short %}, incluyendo el límite de la cantidad de licencias de usuario que has comprado con nosotros. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md b/translations/es-ES/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md new file mode 100644 index 0000000000000..bc4124a74238d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md @@ -0,0 +1,8 @@ +{% note %} + +**Notas:** +- No puedes cambiar las configuraciones de acceso de lectura de Git para los repositorios bifurcados ya que heredan sus configuraciones de acceso del repositorio raíz por defecto. +- Si un repositorio público se convierte en privado, entonces el acceso de lectura anónimo de Git se inhabilitará automáticamente para ese repositorio y sus bifurcaciones. +- Si un repositorio con autenticación anónima contiene activos de {% data variables.large_files.product_name_short %}, fallará al descargar los activos de {% data variables.large_files.product_name_short %} ya que aún requerirá autenticación. Recomendamos firmemente no habilitar el acceso de lectura anónimo de Git para un repositorio con activos de {% data variables.large_files.product_name_short %}. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise_user_management/external_auth_disables_2fa.md b/translations/es-ES/data/reusables/enterprise_user_management/external_auth_disables_2fa.md new file mode 100644 index 0000000000000..63c51b33e7ab4 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/external_auth_disables_2fa.md @@ -0,0 +1 @@ +Cuando se utiliza SAML o CAS, la autenticación de dos factores no se admite o se administra en el aparato del {% data variables.product.prodname_ghe_server %}, pero es posible que lo admita un proveedor de autenticación externo. No está disponible la implementación de la autenticación de dos factores en organizaciones. Para obtener más información sobre cómo implementar la autenticación de dos factores, consulta "[Requerir autenticación de dos factores en tu organización](/enterprise/{{ currentVersion }}/user/articles/requiring-two-factor-authentication-in-your-organization/)." diff --git a/translations/es-ES/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md b/translations/es-ES/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md new file mode 100644 index 0000000000000..8962f16ca323e --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md @@ -0,0 +1,3 @@ +{% if enterpriseServerVersions contains currentVersion %} +Como parte de su cofiguración de optimización, LDAP Sync no transferirá tu estructura de equipo anidada. Para crear relaciones entre equipos padre e hijo, deberás recrear manualmente la estructura de equipo anidada y sincronizarla con el grupo de LDAP correspondiente. Para obtener más información, consulta la sección "[Crear equipos](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams/#creating-teams-with-ldap-sync-enabled)" +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_user_management/manage-global-webhooks-api.md b/translations/es-ES/data/reusables/enterprise_user_management/manage-global-webhooks-api.md new file mode 100644 index 0000000000000..6da1360c89970 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/manage-global-webhooks-api.md @@ -0,0 +1 @@ +También puedes utilizar {% data variables.product.prodname_enterprise_api %} para administrar los webhooks globales. Para encontrar una lista de acciones completa, consulta la sección "[Webhooks globales](/rest/reference/enterprise-admin#global-webhooks)". diff --git a/translations/es-ES/data/reusables/enterprise_user_management/two_factor_auth_header.md b/translations/es-ES/data/reusables/enterprise_user_management/two_factor_auth_header.md new file mode 100644 index 0000000000000..996425fdc11c1 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_user_management/two_factor_auth_header.md @@ -0,0 +1 @@ +### Autenticación de dos factores diff --git a/translations/es-ES/data/reusables/feature-preview/feature-preview-setting.md b/translations/es-ES/data/reusables/feature-preview/feature-preview-setting.md new file mode 100644 index 0000000000000..353d4dfc6e3c1 --- /dev/null +++ b/translations/es-ES/data/reusables/feature-preview/feature-preview-setting.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, haz clic en tu foto de perfil, luego haz clic en **Feature preview** (Vista previa de la característica). ![Botón Feature preview (Vista previa de la característica)](/assets/images/help/settings/feature-preview-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/files/add-file.md b/translations/es-ES/data/reusables/files/add-file.md new file mode 100644 index 0000000000000..96b1ceba3803b --- /dev/null +++ b/translations/es-ES/data/reusables/files/add-file.md @@ -0,0 +1,5 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +1. Sobre la lista de archivos, da clic en **Crear archivo nuevo**. ![Botón de "Crear archivo nuevo"](/assets/images/help/repository/create_new_file.png) +{% else %} +1. En la parte superior de la lista de archivos, utilizando el menú desplegable de **Agregar archivo**, da clic en **Crear archivo nuevo**. !["Crear archivo nuevo" en el menú desplegable de "Agregar archivo"](/assets/images/help/repository/create_new_file.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/files/choose-commit-email.md b/translations/es-ES/data/reusables/files/choose-commit-email.md new file mode 100644 index 0000000000000..3f99d20dfaeae --- /dev/null +++ b/translations/es-ES/data/reusables/files/choose-commit-email.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +1. Debajo de los campos de mensaje de confirmación, haz clic en el menú desplegable de dirección de correo electrónico y elige una dirección de correo electrónico de autor de Git. Únicamente las direcciones de correo electrónico verificadas aparecen en el menú desplegable. Si habilitaste privacidad de la dirección de correo electrónico, entonces `@users.noreply.github.com` es la dirección de correo electrónico de autor de la confirmación por defecto. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". ![Escoger direcciones de correo electrónico para confirmaciones](/assets/images/help/repository/choose-commit-email-address.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/files/choose_commit_branch.md b/translations/es-ES/data/reusables/files/choose_commit_branch.md new file mode 100644 index 0000000000000..352027c1c3ff9 --- /dev/null +++ b/translations/es-ES/data/reusables/files/choose_commit_branch.md @@ -0,0 +1 @@ +1. Debajo de los campos del mensaje de confirmación, decide si deseas agregar tu confirmación a la rama actual o a una rama nueva. Si tu rama actual es la rama predeterminada, debes elegir crear una nueva rama para tu confirmación y después crear una solicitud de extracción. Para obtener más información, consulta "[Crear una solicitud de extracción nueva](/articles/creating-a-pull-request)". ![Confirmar opciones de rama](/assets/images/help/repository/choose-commit-branch.png) diff --git a/translations/es-ES/data/reusables/files/commit-author-email-options.md b/translations/es-ES/data/reusables/files/commit-author-email-options.md new file mode 100644 index 0000000000000..6f03954bbb0b4 --- /dev/null +++ b/translations/es-ES/data/reusables/files/commit-author-email-options.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Si no has habilitado la privacidad de direcciones de correo electrónico, puedes escoger la dirección verificada con la que serás autor de los cambios cuando edites, borres o crees archivos o fusiones una solicitud de extracción en +{% data variables.product.product_name %}. Si habilitaste la privacidad de direcciones de correo electrónico, entonces la dirección del autor de los cambios no se podrá cambiar y será predeterminada a `@users.noreply.github.com`. +{% endif %} diff --git a/translations/es-ES/data/reusables/files/preview_change.md b/translations/es-ES/data/reusables/files/preview_change.md new file mode 100644 index 0000000000000..a2f11b01e9a79 --- /dev/null +++ b/translations/es-ES/data/reusables/files/preview_change.md @@ -0,0 +1 @@ +1. Arriba del contenido nuevo, da clic en **Previsualizar cambios**. ![Botón para previsualizar archivo](/assets/images/help/repository/edit-readme-preview-changes.png) diff --git a/translations/es-ES/data/reusables/files/propose_file_change.md b/translations/es-ES/data/reusables/files/propose_file_change.md new file mode 100644 index 0000000000000..cc8c12b133d09 --- /dev/null +++ b/translations/es-ES/data/reusables/files/propose_file_change.md @@ -0,0 +1 @@ +1. Haz clic en **Proponer cambio en el archivo**. ![Botón para proponer cambio de archivo](/assets/images/help/repository/propose-file-change-quick-pull.png) diff --git a/translations/es-ES/data/reusables/files/propose_new_file.md b/translations/es-ES/data/reusables/files/propose_new_file.md new file mode 100644 index 0000000000000..97d0f293ad340 --- /dev/null +++ b/translations/es-ES/data/reusables/files/propose_new_file.md @@ -0,0 +1 @@ +1. Da clic en **Proponer nuevo archivo**. ![Botón para proponer nuevo archivo](/assets/images/help/repository/new-file-commit-button.png) diff --git a/translations/es-ES/data/reusables/files/write_commit_message.md b/translations/es-ES/data/reusables/files/write_commit_message.md new file mode 100644 index 0000000000000..726582b990f9e --- /dev/null +++ b/translations/es-ES/data/reusables/files/write_commit_message.md @@ -0,0 +1 @@ +1. En la parte inferior de la página, teclea un mensaje de confirmación corto y significativo que describa el cambio que realizaste al archivo. Puedes atribuir el cambio a mas de un autor en el mensaje del mismo. Para obtener más información, consulta "[Crear una confirmación con co-autores múltiples](/articles/creating-a-commit-with-multiple-authors)". ![Mensaje de confirmación de tu cambio](/assets/images/help/repository/write-commit-message-quick-pull.png) diff --git a/translations/es-ES/data/reusables/gated-features/actions-shared.md b/translations/es-ES/data/reusables/gated-features/actions-shared.md new file mode 100644 index 0000000000000..f10d9ef47005d --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/actions-shared.md @@ -0,0 +1 @@ +{{ site.data.variables.product.prodname_actions }} se encuentra disponible con {{ site.data.variables.product.prodname_free_user }}, {{ site.data.variables.product.prodname_pro }}, {{ site.data.variables.product.prodname_free_team }} para organizaciones, {{ site.data.variables.product.prodname_team }}, {{ site.data.variables.product.prodname_ghe_cloud }}, y {{ site.data.variables.product.prodname_ghe_one }}. {% data variables.product.prodname_actions %} no se encuentra disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. diff --git a/translations/es-ES/data/reusables/gated-features/actions.md b/translations/es-ES/data/reusables/gated-features/actions.md new file mode 100644 index 0000000000000..bafbe8fae92d7 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/actions.md @@ -0,0 +1 @@ +{% data reusables.gated-features.actions-shared %} {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/allowed-ip-addresses.md b/translations/es-ES/data/reusables/gated-features/allowed-ip-addresses.md new file mode 100644 index 0000000000000..760ca3ba5ed8f --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/allowed-ip-addresses.md @@ -0,0 +1 @@ +Las direcciones IP permitidas están disponibles con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". diff --git a/translations/es-ES/data/reusables/gated-features/auto-merge.md b/translations/es-ES/data/reusables/gated-features/auto-merge.md new file mode 100644 index 0000000000000..d246a02f8c728 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/auto-merge.md @@ -0,0 +1 @@ +La fusión automática para las solicitudes de cambios se encuentra disponible en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, y {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/gated-features/autolinks.md b/translations/es-ES/data/reusables/gated-features/autolinks.md new file mode 100644 index 0000000000000..f4d213a83187d --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/autolinks.md @@ -0,0 +1 @@ +Los autoenlaces se encuentran disponibles en los repositorios con {% 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 %} y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/code-owners.md b/translations/es-ES/data/reusables/gated-features/code-owners.md new file mode 100644 index 0000000000000..14ec8826709b2 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/code-owners.md @@ -0,0 +1 @@ +Puedes definir a los propietarios del código en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios privados y públicos con {% 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 %} y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/code-review-assignment.md b/translations/es-ES/data/reusables/gated-features/code-review-assignment.md new file mode 100644 index 0000000000000..ff56ee303cf87 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/code-review-assignment.md @@ -0,0 +1 @@ +La asignación de revisión de código se encuentra disponible con {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.20+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/code-scanning.md b/translations/es-ES/data/reusables/gated-features/code-scanning.md new file mode 100644 index 0000000000000..69e6abf27f4f7 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/code-scanning.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/gated-features/codespaces.md b/translations/es-ES/data/reusables/gated-features/codespaces.md new file mode 100644 index 0000000000000..4a8a8cf28bb6d --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/codespaces.md @@ -0,0 +1 @@ +Codespaces está disponible para las cuentas de usuario que utilicen {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/gated-features/discussions.md b/translations/es-ES/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000000..37eb9a3b2f825 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +Los {% data variables.product.prodname_discussions %} se encuentran disponibles en un beta para los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/gated-features/display-names.md b/translations/es-ES/data/reusables/gated-features/display-names.md new file mode 100644 index 0000000000000..e983947932b2d --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/display-names.md @@ -0,0 +1 @@ +El permitir a los miembros ver los nombres de perfil de los autores de los comentarios se encuentra disponible con {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.18+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/draft-prs.md b/translations/es-ES/data/reusables/gated-features/draft-prs.md new file mode 100644 index 0000000000000..31eb48939b769 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/draft-prs.md @@ -0,0 +1 @@ +Los borradores de solicitudes de cambio están disponibles en los repositorios públicos con {% data variables.product.prodname_free_team %} para organizaciones y en los planes de facturación tradicionales por repositorio, y en los repositorios públicos y privados con {% 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 %} y {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md b/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md new file mode 100644 index 0000000000000..b6ed0e90ccc08 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md @@ -0,0 +1 @@ +Las cuentas empresariales se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/articles/about-enterprise-accounts)."{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/enterprise_account_webhooks.md b/translations/es-ES/data/reusables/gated-features/enterprise_account_webhooks.md new file mode 100644 index 0000000000000..80fd10b342649 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/enterprise_account_webhooks.md @@ -0,0 +1,4 @@ + +{% data reusables.gated-features.enterprise-accounts %} + +Los webhooks que se configuraron en cuentas u organizaciones empresariales y que son parte de una cuenta empresarial incluirán un objeto de cuenta de `enterprise`. diff --git a/translations/es-ES/data/reusables/gated-features/environments.md b/translations/es-ES/data/reusables/gated-features/environments.md new file mode 100644 index 0000000000000..aeb9e41f94d9c --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/environments.md @@ -0,0 +1 @@ +{% data reusables.gated-features.actions-shared %} Los ambientes, reglas de protección de ambientes, y secretos de ambiente están disponibles en los repositorios públicos para todos los productos y en los repositorios privados para {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/github-insights.md b/translations/es-ES/data/reusables/gated-features/github-insights.md new file mode 100644 index 0000000000000..5f07e45586314 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/github-insights.md @@ -0,0 +1 @@ +{% data variables.product.prodname_insights %} se encuentra disponible con {% data variables.product.prodname_ghe_one %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/internal-repos.md b/translations/es-ES/data/reusables/gated-features/internal-repos.md new file mode 100644 index 0000000000000..be85e7f08ba00 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/internal-repos.md @@ -0,0 +1 @@ +Los repositorios internos se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %} 2.20+. Para obtener más información, consulta la sección "Productos de GitHub". diff --git a/translations/es-ES/data/reusables/gated-features/more-info-org-products.md b/translations/es-ES/data/reusables/gated-features/more-info-org-products.md new file mode 100644 index 0000000000000..bcbf66321a843 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/more-info-org-products.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)."{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/more-info.md b/translations/es-ES/data/reusables/gated-features/more-info.md new file mode 100644 index 0000000000000..bcbf66321a843 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/more-info.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)."{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/okta-team-sync.md b/translations/es-ES/data/reusables/gated-features/okta-team-sync.md new file mode 100644 index 0000000000000..66c6946bc380b --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/okta-team-sync.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** La sincronización de equipos con Okta se encuentra actualmente en beta y está sujeta a cambios. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/gated-features/org-insights.md b/translations/es-ES/data/reusables/gated-features/org-insights.md new file mode 100644 index 0000000000000..b1e47226f2b57 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/org-insights.md @@ -0,0 +1 @@ +Las perspectivas de organización se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". diff --git a/translations/es-ES/data/reusables/gated-features/packages.md b/translations/es-ES/data/reusables/gated-features/packages.md new file mode 100644 index 0000000000000..9012823695766 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/packages.md @@ -0,0 +1,5 @@ +{% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, y {% data variables.product.prodname_ghe_one %}. +{% if currentVersion == "free-pro-team@latest" %} +
+{% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_one %}. {% data reusables.gated-features.more-info %} +{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/pages.md b/translations/es-ES/data/reusables/gated-features/pages.md new file mode 100644 index 0000000000000..71db392d10ab0 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/pages.md @@ -0,0 +1 @@ +{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} Está disponible en los repositorios internos y privados con {% data variables.product.prodname_ghe_managed %}. {% endif %}{% data variables.product.prodname_pages %} se encuentra disponible en los repositorios públicos con {% data variables.product.prodname_free_user %} y con {% data variables.product.prodname_free_team %} para las organizaciones, y en los repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/protected-branches.md b/translations/es-ES/data/reusables/gated-features/protected-branches.md new file mode 100644 index 0000000000000..ffae769bab961 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/protected-branches.md @@ -0,0 +1 @@ +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/repository-insights.md b/translations/es-ES/data/reusables/gated-features/repository-insights.md new file mode 100644 index 0000000000000..71016e9f967db --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/repository-insights.md @@ -0,0 +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 %} diff --git a/translations/es-ES/data/reusables/gated-features/restict-add-collaborator.md b/translations/es-ES/data/reusables/gated-features/restict-add-collaborator.md new file mode 100644 index 0000000000000..5d493a9bd7d78 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/restict-add-collaborator.md @@ -0,0 +1 @@ +La restricción de la capacidad para agregar colaboradores externos a los propietarios se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md b/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md new file mode 100644 index 0000000000000..143ae6d021c36 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md @@ -0,0 +1 @@ +La restricción de notificaciones por correo electrónico para el correo del dominio se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/saml-sso.md b/translations/es-ES/data/reusables/gated-features/saml-sso.md new file mode 100644 index 0000000000000..9fb5fe8f92ff5 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/saml-sso.md @@ -0,0 +1 @@ +SAML single sign-on is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} and {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/secret-scanning.md b/translations/es-ES/data/reusables/gated-features/secret-scanning.md new file mode 100644 index 0000000000000..fd44aaa04c778 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/secret-scanning.md @@ -0,0 +1 @@ +{% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible {% if currentVersion == "free-pro-team@latest" %}en los repositorios públicos, y en los repositorios privados que pertenezcan a las organizaciónes con {% else %}si tienes {% endif %}una {% data variables.product.prodname_advanced_security %}licencia. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md b/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md new file mode 100644 index 0000000000000..7dd434920d061 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md @@ -0,0 +1 @@ +Support for SSH certificate authorities is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 2.19+. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/team-synchronization.md b/translations/es-ES/data/reusables/gated-features/team-synchronization.md new file mode 100644 index 0000000000000..7f86941bf22b4 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/team-synchronization.md @@ -0,0 +1 @@ +La sincronización de equipos se encuentra disponible para cuentas organizacionales y empresariales que que utilicen {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md b/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md new file mode 100644 index 0000000000000..0811bb65bfbaa --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md @@ -0,0 +1 @@ +Si estás utilizando {% data variables.product.prodname_free_user %}, puedes agregar colaboradores ilimitados en repositorios públicos y privados. diff --git a/translations/es-ES/data/reusables/gated-features/wikis.md b/translations/es-ES/data/reusables/gated-features/wikis.md new file mode 100644 index 0000000000000..e32b5aacbed4a --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/wikis.md @@ -0,0 +1 @@ +{% if currentVersion == "github-ae@latest" %}Los Wikis se encuentran disponibles en los repositorios privados e internos con {% data variables.product.prodname_ghe_managed %}.{% endif %} Los Wikis se encuentran disponibles en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gist/anonymous-gists-cannot-be-deleted.md b/translations/es-ES/data/reusables/gist/anonymous-gists-cannot-be-deleted.md new file mode 100644 index 0000000000000..2600b9b67eb1a --- /dev/null +++ b/translations/es-ES/data/reusables/gist/anonymous-gists-cannot-be-deleted.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +{% warning %} + +**Advertencia:** Los gists anónimos no pueden borrarse del buscador web. Para borrar un gist anónimo, contacta a {% data variables.contact.contact_support %}. Por favor proporciona la URL del gist que deseas borrar. + +{% endwarning %} +{% endif %} diff --git a/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md new file mode 100644 index 0000000000000..535fa5cd9df20 --- /dev/null +++ b/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -0,0 +1 @@ +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/es-ES/data/reusables/git/commit-file.md b/translations/es-ES/data/reusables/git/commit-file.md new file mode 100644 index 0000000000000..3f12e264de27c --- /dev/null +++ b/translations/es-ES/data/reusables/git/commit-file.md @@ -0,0 +1 @@ +1. Confirma el archivo que has preparado en tu repositorio local. diff --git a/translations/es-ES/data/reusables/git/git-push.md b/translations/es-ES/data/reusables/git/git-push.md new file mode 100644 index 0000000000000..6ede19c30d103 --- /dev/null +++ b/translations/es-ES/data/reusables/git/git-push.md @@ -0,0 +1,5 @@ +1. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. + ```shell + $ git push origin your-branch + # Pushes the changes in your local repository up to the remote repository you specified as the origin + ``` diff --git a/translations/es-ES/data/reusables/git/remove-git-remote.md b/translations/es-ES/data/reusables/git/remove-git-remote.md new file mode 100644 index 0000000000000..cf1a48f2a18cf --- /dev/null +++ b/translations/es-ES/data/reusables/git/remove-git-remote.md @@ -0,0 +1,10 @@ +1. Con la línea de comandos, elimina cualquier remoto de git que se encuentre actualmente configurado para el repositorio. + + ```shell + # Show existing remotes + $ git remote -v + > origin git@git-server/octocat/hello-world.git (fetch) + > origin git@git-server/octocat/hello-world.git (push) + # Remove existing remotes + $ git remote remove origin + ``` diff --git a/translations/es-ES/data/reusables/git/reset-head-to-previous-commit-codeblock.md b/translations/es-ES/data/reusables/git/reset-head-to-previous-commit-codeblock.md new file mode 100644 index 0000000000000..9b2be3228c6b7 --- /dev/null +++ b/translations/es-ES/data/reusables/git/reset-head-to-previous-commit-codeblock.md @@ -0,0 +1 @@ +Para eliminar esta confirmación y modificar el archivo, usa 'git reset --soft HEAD~1' y confirma y agrega nuevamente el archivo. diff --git a/translations/es-ES/data/reusables/git/stage_for_commit.md b/translations/es-ES/data/reusables/git/stage_for_commit.md new file mode 100644 index 0000000000000..c0c6e98f70bef --- /dev/null +++ b/translations/es-ES/data/reusables/git/stage_for_commit.md @@ -0,0 +1 @@ +1. Prepara el archivo para confirmarlo para tu repositorio local. diff --git a/translations/es-ES/data/reusables/git/unstage-codeblock.md b/translations/es-ES/data/reusables/git/unstage-codeblock.md new file mode 100644 index 0000000000000..45204f439f6b0 --- /dev/null +++ b/translations/es-ES/data/reusables/git/unstage-codeblock.md @@ -0,0 +1 @@ +Para deshacer un archivo, usa 'git reset HEAD YOUR-FILE'. diff --git a/translations/es-ES/data/reusables/github-actions/actions-billing.md b/translations/es-ES/data/reusables/github-actions/actions-billing.md new file mode 100644 index 0000000000000..e966816a37882 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-billing.md @@ -0,0 +1 @@ +El uso de las {% data variables.product.prodname_actions %} es gratuito para los repositorios públicos y para los ejecutores auto-hospedados. Para los repositorios privados, cada cuenta de {% data variables.product.prodname_dotcom %} recibe una cantidad determinada de minutos y almacenamiento gratuitos dependiendo del producto que se utilice con la cuenta. Cualquier uso que no se contemple en las cantidades incluidas se controla con los límites de gasto. diff --git a/translations/es-ES/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/es-ES/data/reusables/github-actions/actions-do-not-trigger-workflows.md new file mode 100644 index 0000000000000..db22e0daad9fb --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-do-not-trigger-workflows.md @@ -0,0 +1 @@ +Cuando utilizas el `GITHUB_TOKEN` del repositorio para realizar tareas por parte de la app de {% data variables.product.prodname_actions %}, los eventos que `GITHUB_TOKEN` desencadena no crearán una ejecución de flujo de trabajo. Esto impide que crees ejecuciones de flujo de trabajo recursivas por accidente. Por ejemplo, si un flujo de trabajo sube código utilizando el `GITHUB_TOKEN` del repositorio, no se ejecutará un nuevo flujo de trabajo aún si el repositorio contiene alguno configurado para ejecutarse cuando ocurran eventos de `subida` de información. diff --git a/translations/es-ES/data/reusables/github-actions/actions-on-examples.md b/translations/es-ES/data/reusables/github-actions/actions-on-examples.md new file mode 100644 index 0000000000000..5ad2280baf953 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-on-examples.md @@ -0,0 +1,34 @@ +##### Ejemplo con un solo evento + +```yaml +# Triggered when code is pushed to any branch in a repository +on: push +``` + +##### Ejemplo con una lista de eventos + +```yaml +# Triggers the workflow on push or pull request events +on: [push, pull_request] +``` + +##### Ejemplo utilizando eventos múltiples con tipos de actividad o configuración + +Si necesitas especificar tipos de actividad o configuración para un evento, debes configurar cada evento por separado. Debes agregar dos puntos (`:`) a todos los eventos, incluyendo aquellos sin configuración. + +```yaml +on: + # Trigger the workflow on push or pull request, + # but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + # Also trigger on page_build, as well as release created events + page_build: + release: + types: # This configuration does not affect the page_build event above + - created +``` diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000000..3efce59bec39f --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +Si eres un cliente que paga mensualmente, tu cuenta tendrá un límite de gastos predeterminado de $0, lo cual previene el uso adicional de minutos o almacenamiento para los repositorios privados más allá de las cantidades que se incluyen en tu cuenta. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000000..4e837126b4a9c --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +Si tienes un límite de gastos ilimitado o configuraste un límite de gastos mayor que $0, se te cobrará por cualquier minuto adicional o almacenamiento superior a la cantidad que se incluye en tu cuenta, lo cual se conoce también como excedente. {% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenezca el repositorio en donde se ejecuta un flujo de trabajo. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/data/reusables/github-actions/actions-unused-labels.md b/translations/es-ES/data/reusables/github-actions/actions-unused-labels.md new file mode 100644 index 0000000000000..090ea743f8949 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-unused-labels.md @@ -0,0 +1 @@ + Cualquier etiqueta sin utilizar que no se asigne a un ejecutor se borrará automáticamente dentro de 24 horas. diff --git a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md new file mode 100644 index 0000000000000..e1342562c6e91 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md @@ -0,0 +1,2 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Predeterminadamente, {% data variables.product.product_name %} almacena las bitácoras de compilación y los artefactos por 90 días, y este periodo de retención se puede personalizar. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)".{% endif %} +{% if currentVersion == "enterprise-server@2.22" %} Las {% data variables.product.product_name %} almacenan las bitácoras y los artefactos por 90 días.{% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/branch-requirement.md b/translations/es-ES/data/reusables/github-actions/branch-requirement.md new file mode 100644 index 0000000000000..a30557c46bd23 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/branch-requirement.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Este evento solo activará una ejecución de flujo de trabajo si el archivo de flujo de trabajo está en la rama predeterminada. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md b/translations/es-ES/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md new file mode 100644 index 0000000000000..74831377b0eca --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md @@ -0,0 +1,2 @@ +1. Ingresa un valor nuevo debajo de **Duración de la retención para artefactos y bitácoras**. +1. Da clic en **Guardar** para aplicar el cambio. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-actions/contacting-support.md b/translations/es-ES/data/reusables/github-actions/contacting-support.md new file mode 100644 index 0000000000000..9ba6a3389e238 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/contacting-support.md @@ -0,0 +1,9 @@ +Si necesitas ayuda con lo que sea relacionado con la configuración de flujo de trabajo, tal como la sintaxis, los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, o la creación de acciones, busca un tema existente o inicia uno nuevo en la [categoría de {% data variables.product.prodname_actions %} de {% data variables.product.prodname_gcf %}](https://github.community/c/code-to-cloud/github-actions/41). + +Si tienes algún tipo de retroalimentación o solicitudes de características para {% data variables.product.prodname_actions %}, compártelas en el {% data variables.contact.contact_feedback_actions %}. + +Contacta a {% data variables.contact.contact_support %} para cualquiera de los siguientes, que tu tipo de uso o el tipo de uso que pretendes tener caiga en las siguientes categorías de limitación: + +* Si crees que tu cuenta se ha restringido de manera incorrecta +* Si llegas un error inesperado cuando ejecutas una de tus acciones, por ejemplo: una ID única +* Si llegas a una situación en donde el comportamiento existente contradice a aquél que se espera, pero no siempre se documenta diff --git a/translations/es-ES/data/reusables/github-actions/container-jobs-intro.md b/translations/es-ES/data/reusables/github-actions/container-jobs-intro.md new file mode 100644 index 0000000000000..2429ae39ff760 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/container-jobs-intro.md @@ -0,0 +1 @@ +La configuración de jobs para su ejecución en un contenedor simplifica las configuraciones de red entre el job y los contenedores de servicio. Los contenedores de Docker en el mismo puente de red definido por el usuario exponen todos los puertos entre ellos, así que no necesitas mapear ninguno de los puertos para contenedores de servicio en el alojamiento de Docker. Puedes acceder al contenedor de servicio desde el contenedor del job utilizando la etiqueta que configuras en el flujo de trabajo. diff --git a/translations/es-ES/data/reusables/github-actions/copy-workflow-file.md b/translations/es-ES/data/reusables/github-actions/copy-workflow-file.md new file mode 100644 index 0000000000000..56754f5d09cb7 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/copy-workflow-file.md @@ -0,0 +1 @@ +Puedes copiar este archivo de flujo de trabajo al directorio `.github/workflows` de tu repositorio y modificarlo como lo requieras. diff --git a/translations/es-ES/data/reusables/github-actions/defaults-override.md b/translations/es-ES/data/reusables/github-actions/defaults-override.md new file mode 100644 index 0000000000000..bdb030a76a6ad --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/defaults-override.md @@ -0,0 +1 @@ +Cuando se define más de una configuración predeterminada con el mismo nombre, {% data variables.product.prodname_dotcom %} utiliza la configuración predeterminada más específica. Por ejemplo, una configuración predeterminada definida en un job invalidará a aquella que tenga el mismo nombre definido en el flujo de trabajo. diff --git a/translations/es-ES/data/reusables/github-actions/disabled-actions-description.md b/translations/es-ES/data/reusables/github-actions/disabled-actions-description.md new file mode 100644 index 0000000000000..1b56a6ffce82c --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/disabled-actions-description.md @@ -0,0 +1 @@ +Cuando inhabilitas a {% data variables.product.prodname_actions %}, no se ejecuta ningún flujo de trabajo en tu repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md new file mode 100644 index 0000000000000..3e9f3df57f5a6 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md @@ -0,0 +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. Puedes elegir inhabilitar las {% data variables.product.prodname_actions %} o limitarlas para las acciones privadas únicamente, lo cual significa que las personas solo podrá utilizar las acciones que existan en tu repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/docker-container-os-support.md b/translations/es-ES/data/reusables/github-actions/docker-container-os-support.md new file mode 100644 index 0000000000000..13a1ea8d2bf28 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/docker-container-os-support.md @@ -0,0 +1,8 @@ +{% note %} + +**Nota:** Si tus flujos de trabajo utilizan acciones de contenedor de Docker o contenedores de servicio, entonces debes utilizar un ejecutor de Linux: + +* Si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, debes utilizar un ejecutor de Ubuntu. +* Si estás utilizando ejecutores auto-hospedados, debes utilizar una máquina Linux como tu ejecutor, y ésta debe tener Docker instalado. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/docker-tag-with-ref.md b/translations/es-ES/data/reusables/github-actions/docker-tag-with-ref.md new file mode 100644 index 0000000000000..98f196a16bb60 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/docker-tag-with-ref.md @@ -0,0 +1 @@ +El flujo de trabajo anterior verifica el repositorio {% data variables.product.prodname_dotcom %} y utiliza la acción `build-push-action` para construir y subir la imagen de Docker. Éste configura la opción [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) de `build-push-action` para que etiquete automáticamente la imagen construida de Docker con la referencia de Git del evento del flujo de trabajo. Este flujo de trabajo se desencadena cuando se publica un lanzamiento de {% data variables.product.prodname_dotcom %}, para que la referencia sea la etiqueta de Git para el lanzamiento. diff --git a/translations/es-ES/data/reusables/github-actions/dockerfile-guidelines.md b/translations/es-ES/data/reusables/github-actions/dockerfile-guidelines.md new file mode 100644 index 0000000000000..c64e0a8466f56 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/dockerfile-guidelines.md @@ -0,0 +1,3 @@ +1. Los documentos requerían argumentos en el README de las acciones y las omiten desde la instrucción `CMD`. +1. Usa los valores predeterminados que permiten usar la acción sin especificar ningún `args`. +1. Si la acción expone una marca de `--help`, o algo similar, utilízala para hacer tu propia documentación de la acción. diff --git a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md new file mode 100644 index 0000000000000..a16cd7f6376c9 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md @@ -0,0 +1 @@ +Cuando habilitas {% data variables.product.prodname_actions %}, los flujos de trabajo puede ejecutar acciones ubicadas dentro de tu repositorio y en cualquier otro repositorio público. diff --git a/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md b/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md new file mode 100644 index 0000000000000..0043c8e9608df --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md @@ -0,0 +1 @@ +When you enable local actions only, workflows can only run actions located in your repository, organization, or enterprise. diff --git a/translations/es-ES/data/reusables/github-actions/enterprise-billing-details.md b/translations/es-ES/data/reusables/github-actions/enterprise-billing-details.md new file mode 100644 index 0000000000000..1ae7ee4dfd33c --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/enterprise-billing-details.md @@ -0,0 +1 @@ +El uso incluye los minutos totales que utiliza cada organización. El resumen combinado de {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} no lista los minutos incluidos, minutos pagados, o un estimado de precio por GB de almacenamiento. diff --git a/translations/es-ES/data/reusables/github-actions/example-github-runner.md b/translations/es-ES/data/reusables/github-actions/example-github-runner.md new file mode 100644 index 0000000000000..84a1b53787590 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/example-github-runner.md @@ -0,0 +1,19 @@ +### Ejecución en un sistema operativo diferente + +La plantilla inicial de flujo de trabajo configura los jobs para que se ejecuten en Linux, utilizando los ejecutores `ubuntu-latest` hospedados en {% data variables.product.prodname_dotcom %}. Puedes cambiar la clave `runs-on` para ejecutar tus jobs en un sistema operativo diferente. Por ejemplo, puedes utilizar los ejecutores de Windows hospedados en {% data variables.product.prodname_dotcom %}. + +{% raw %} +```yaml +runs-on: windows-latest +``` +{% endraw %} + +O puedes utilizar los ejecutores de macOS hospedados en {% data variables.product.prodname_dotcom %}. + +{% raw %} +```yaml +runs-on: macos-latest +``` +{% endraw %} + +También puedes ejecutar jobs en contenedores de Docker, o puedes proporcionar un ejecutor auto-hospedado que se ejecute en tu propia infraestructura. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)". diff --git a/translations/es-ES/data/reusables/github-actions/expression-syntax-if.md b/translations/es-ES/data/reusables/github-actions/expression-syntax-if.md new file mode 100644 index 0000000000000..8c259093179c1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/expression-syntax-if.md @@ -0,0 +1 @@ +Podrías omitir la sintaxis de expresión cuando utilizas expresiones en un condicional `if` ({% raw %}`${{ }}`{% endraw %}) ya que {% data variables.product.prodname_dotcom %} evalúa automáticamente el condicional `if` como una expresión. diff --git a/translations/es-ES/data/reusables/github-actions/github-context-warning.md b/translations/es-ES/data/reusables/github-actions/github-context-warning.md new file mode 100644 index 0000000000000..709fae57c82f5 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/github-context-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** Cuando utilizas todo el contexto de `GitHub`, cuida que incluya la información sensible tal como un `github.token`. {% data variables.product.prodname_dotcom %} enmascara secretos cuando se imprimen en la consola, pero debes tener cuidado cuando exportes o imprimas el contexto. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/github-actions/gradle-workflow-steps.md b/translations/es-ES/data/reusables/github-actions/gradle-workflow-steps.md new file mode 100644 index 0000000000000..81ec8f578a30f --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/gradle-workflow-steps.md @@ -0,0 +1,4 @@ +Este flujo de trabajo realiza los siguientes pasos: + +1. Verifica una copia del repositorio del proyecto. +1. Configura el JDK de Java. diff --git a/translations/es-ES/data/reusables/github-actions/invalid-workflow-files.md b/translations/es-ES/data/reusables/github-actions/invalid-workflow-files.md new file mode 100644 index 0000000000000..942d9bf642528 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/invalid-workflow-files.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Garantiza que solo confirmes los archivos de flujo de trabajo válidos en tu repositorio. Si `.github/workflows` contiene un archivo de flujo de trabajo inválido, {% data variables.product.prodname_actions %} generará una ejecución de flujo de trabajo fallida por cada confirmación nueva. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md new file mode 100644 index 0000000000000..48147e94cfeba --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md @@ -0,0 +1,7 @@ +{% warning %} + +**Advertencia**: Si utilzas una lista de IP permitidas y también quisieras utilizar {% data variables.product.prodname_actions %}, debes usar los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)". + +{% endwarning %} + +Para permitir que los ejecutores auto-hospedados se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)". diff --git a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md new file mode 100644 index 0000000000000..86c5d9e0c0877 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md @@ -0,0 +1,19 @@ +### Especificar la versión y arquitectura de JVM + +La plantilla inicial de flujo de trabajo configura el `PATH` para que contenga OpenJDK 8 para las plataformas x64. Si quieres utilizar una versión diferente de Java, o enfocarte en una arquitectura diferente (`x64` o `x86`), puedes utilizar la acción `setup-java` para elegir un ambiente de ejecución de Java diferente. + +Por ejemplo, para utilizar la versión 9.0.4 del JDK para una plataforma x64, puedes utilizar la acción `setup-java` y configurar los parámetros `java-version` y `architecture` en `'9.0.4'` y `x64`. + +{% raw %} +```yaml +steps: + - uses: actions/checkout@v2 + - name: Set up JDK 9.0.4 for x64 + uses: actions/setup-java@v1 + with: + java-version: '9.0.4' + architecture: x64 +``` +{% endraw %} + +Para obtener más información, consulta la acción [`setup-java`](https://github.com/actions/setup-java). diff --git a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md new file mode 100644 index 0000000000000..e021cbc3eca2f --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** El ambiente virtual macOS 11.0 se proporciona actualmente solo como vista previa. La etiqueta de flujo de trabajo de YAML `macos-latest` aún utiliza el ambiente virtual de macOS 10.15. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/matrix-variable-example.md b/translations/es-ES/data/reusables/github-actions/matrix-variable-example.md new file mode 100644 index 0000000000000..b8fd69fe75e3d --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/matrix-variable-example.md @@ -0,0 +1,26 @@ +En este ejemplo, las entradas de la matriz para `node-version` se configuran para que cada una utilice valores diferentes para las variables de ambiente `site` y `datacenter`. El paso `Echo site details` utiliza entonces {% raw %}`env: ${{ matrix.env }}`{% endraw %} para referirse a las variables personalizadas: + +{% raw %} +```yaml +name: Node.js CI +on: [push] +jobs: + build: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - node-version: 10.x + site: "prod" + datacenter: "site-a" + - node-version: 12.x + site: "dev" + datacenter: "site-b" + steps: + - name: Echo site details + env: + SITE: ${{ matrix.site }} + DATACENTER: ${{ matrix.datacenter }} + run: echo $SITE $DATACENTER +``` +{% endraw %} diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-environment.md b/translations/es-ES/data/reusables/github-actions/permissions-statement-environment.md new file mode 100644 index 0000000000000..8014006068d40 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/permissions-statement-environment.md @@ -0,0 +1 @@ +Para configurar un ambiente en un repositorio de cuenta de usuario, debes ser el propietario de éste. Para configurar un ambiente en un repositorio de organización, debes tener acceso de `admin`. diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-api.md new file mode 100644 index 0000000000000..81e979382cafa --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-api.md @@ -0,0 +1 @@ +Para crear secretos utilizando la API de REST, debes tener acceso de escritura en el repositorio o acceso administrativo en la organización. Para obtener más información, consulta la sección "[ API de secretos de {% data variables.product.prodname_actions %}](/rest/reference/actions#secrets)". diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-environment.md b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-environment.md new file mode 100644 index 0000000000000..4e39764774988 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-environment.md @@ -0,0 +1 @@ +Para crear secretos para un ambiente en un repositorio de una cuenta de usuario, debes ser el propietario de éste. Para crear secretos para un ambiente en el repositorio de una organización, deberás tener acceso de `administrador`. diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-organization.md new file mode 100644 index 0000000000000..7847e05614392 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-organization.md @@ -0,0 +1 @@ +Para crear secretos a nivel organizacional, deberás tener acceso de `administrador`. diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-repository.md new file mode 100644 index 0000000000000..1fc821c214fe1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-repository.md @@ -0,0 +1 @@ +Para crear secretos para un repositorio de una cuenta de usuario, deberás ser el propietario de éste. Para crear secretos para un repositorio de una organización, deberás tener acceso de `administrador`. diff --git a/translations/es-ES/data/reusables/github-actions/postgres-environment-variables.md b/translations/es-ES/data/reusables/github-actions/postgres-environment-variables.md new file mode 100644 index 0000000000000..9d124b14a99b4 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/postgres-environment-variables.md @@ -0,0 +1 @@ +El script *client.js* busca las variables del ambiente de `POSTGRES_HOST` y `POSTGRES_PORT` para crear al cliente. El flujo de trabajo configura estas dos variables de ambiente como parte del paso "Conectar a PostgreSQL" para hacerlos disponibles para el script *client.js*. Para obtener más información acerca del script, consulta "[Probar el contenedor de servicio de PostgreSQL](#testing-the-postgresql-service-container)". diff --git a/translations/es-ES/data/reusables/github-actions/postgres-label-description.md b/translations/es-ES/data/reusables/github-actions/postgres-label-description.md new file mode 100644 index 0000000000000..ee5193d9af85f --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/postgres-label-description.md @@ -0,0 +1 @@ +El flujo de trabajo configura un contenedor de servicio con la etiqueta `postgres`. Todos los servicios se deben ejecutar en un contenedor, entonces cada servicio requiere que especifiques la `image` del mismo. Este ejemplo utiliza la imagen del contenedor `postgres`, proporciona la cotraseña predeterminada de PostgreSQL, e incluye las opciones de revisión de estado para garantizar que el servicio se está ejecutando. Para obtener más información, consulta la [imagen de postgre](https://hub.docker.com/_/postgres) en Docker Hub. diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-configure.md b/translations/es-ES/data/reusables/github-actions/private-repository-forks-configure.md new file mode 100644 index 0000000000000..f7eb90543fa7d --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/private-repository-forks-configure.md @@ -0,0 +1,2 @@ +1. Debajo de **Bifurcar los flujos de trabajo de la solicitud de extracción**, selecciona tus opciones. Por ejemplo: ![Habilita, inhabilita o limita las acciones para este repositorio](/assets/images/help/settings/actions-fork-pull-request-workflows.png) +1. Da clic en **Guardar** para aplicar la configuración. diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md new file mode 100644 index 0000000000000..33cb9f9e46a62 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md @@ -0,0 +1,5 @@ +Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Available to private repositories only, you can configure these policy settings for enterprise accounts, organizations, or repositories. For enterprise accounts, the policies are applied to all repositories in all organizations. + +- **Ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones** - permite a los usuarios ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones utilizando un `GITHUB_TOKEN` con permisos de solo lectura y sin acceso a los secretos. +- **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de extracción** - Permite a las solicitudes de extracción de las bifuraciones utilizar un `GITHUB_TOKEN` con permiso de escritura. +- **Enviar secretos a los flujos de trabajo desde las solicitudes de extracción** - Pone disponibles todos los secretos de la solicitud de extracción. diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/es-ES/data/reusables/github-actions/publish-to-maven-workflow-step.md new file mode 100644 index 0000000000000..4474f2791587b --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -0,0 +1 @@ +Ejecuta el comando `mvn --batch-mode deploy` para publicar en el repositorio `ossrh`. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md new file mode 100644 index 0000000000000..a6b00543d9ded --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -0,0 +1 @@ +Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. diff --git a/translations/es-ES/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/es-ES/data/reusables/github-actions/publishing-java-packages-intro.md new file mode 100644 index 0000000000000..b5274cf4af1e4 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/publishing-java-packages-intro.md @@ -0,0 +1 @@ +Esta guía te muestra cómo crear un flujo de trabajo que publique paquetes de Java en {% data variables.product.prodname_registry %} y en el Repositorio Central de Maven. Con un solo flujo de trabajo, puedes publicar los paquetes en un solo repositorio o en varios repositorios. diff --git a/translations/es-ES/data/reusables/github-actions/pure-javascript.md b/translations/es-ES/data/reusables/github-actions/pure-javascript.md new file mode 100644 index 0000000000000..a69d63d0bd1e7 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/pure-javascript.md @@ -0,0 +1 @@ +Para garantizar que tus acciones de JavaScript son compatibles con todos los ejecutores hospedados en GitHub (Ubuntu, Windows, y macOS), el código empaquetado de JavaScript que escribas debe ser puramente JavaScript y no depender de otros binarios. Las acciones de JavaScript se ejecutan directamente en el ejecutor y utiliza binarios que ya existen en el ambiente virtual. diff --git a/translations/es-ES/data/reusables/github-actions/redis-environment-variables.md b/translations/es-ES/data/reusables/github-actions/redis-environment-variables.md new file mode 100644 index 0000000000000..22bed48823a3b --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/redis-environment-variables.md @@ -0,0 +1 @@ +El script *client.js* busca las variables de ambiente `REDIS_HOST` y `REDIS_PORT` para crear al cliente. El flujo de trabajo configura esas dos variables de ambiente como parte del paso "Connect to Redis" para hacerlas disponibles para el script *client.js*. Para obtener más información acerca del script, consulta la sección "[Probar el contenedor de servicio de Redis](#testing-the-redis-service-container)". diff --git a/translations/es-ES/data/reusables/github-actions/redis-label-description.md b/translations/es-ES/data/reusables/github-actions/redis-label-description.md new file mode 100644 index 0000000000000..c13123527d8b8 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/redis-label-description.md @@ -0,0 +1 @@ +El flujo de trabajo configura un contenedor de servicio con la etiqueta `reds`. Todos los servicios se deben ejecutar en un contenedor, entonces cada servicio requiere que especifiques la `image` del mismo. Este ejemplo utiliza la imagen del contenedor `redis`, e incluye opciones de verificación de estado para garantizar que el servicio se está ejecutando. Para obtener más información, consulta la [imagen de redis](https://hub.docker.com/_/redis) en Docker Hub. diff --git a/translations/es-ES/data/reusables/github-actions/release-trigger-workflow.md b/translations/es-ES/data/reusables/github-actions/release-trigger-workflow.md new file mode 100644 index 0000000000000..2e194c2adc520 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/release-trigger-workflow.md @@ -0,0 +1 @@ +Cada vez que creas un nuevo lanzamiento en {% data variables.product.prodname_dotcom %}, puedes activar un flujo de trabajo para publicar tu imagen. El flujo de trabajo en el ejemplo siguiente se ejecuta cuando el se activa el evento `release` con el tipo de actividad `created`. Para obtener más información en el evento `release`, consulta la sección"[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release). diff --git a/translations/es-ES/data/reusables/github-actions/run_id_description.md b/translations/es-ES/data/reusables/github-actions/run_id_description.md new file mode 100644 index 0000000000000..50daec3f34b1f --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/run_id_description.md @@ -0,0 +1 @@ +Un número único para cada ejecución dentro de un repositorio. Este número no cambia si vuelves a ejecutar el flujo de trabajo. diff --git a/translations/es-ES/data/reusables/github-actions/run_number_description.md b/translations/es-ES/data/reusables/github-actions/run_number_description.md new file mode 100644 index 0000000000000..db3b83b0fccc5 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/run_number_description.md @@ -0,0 +1 @@ +Un número único para cada ejecución de un flujo de trabajo particular en un repositorio. Este número comienza en 1 para los flujos de trabajo que se ejecutan primero, e incrementa con cada ejecución nueva. Este número no cambia si vuelves a ejecutar el flujo de trabajo. diff --git a/translations/es-ES/data/reusables/github-actions/runner-app-open-source.md b/translations/es-ES/data/reusables/github-actions/runner-app-open-source.md new file mode 100644 index 0000000000000..90e4ac2747c78 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/runner-app-open-source.md @@ -0,0 +1 @@ +La aplicación ejecutora de {% data variables.product.prodname_actions %} es de código abierto. Puedes contribuir y emitir informes de problemas en el repositorio [runner](https://github.com/actions/runner). diff --git a/translations/es-ES/data/reusables/github-actions/secrets-org-level-overview.md b/translations/es-ES/data/reusables/github-actions/secrets-org-level-overview.md new file mode 100644 index 0000000000000..931798da93547 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/secrets-org-level-overview.md @@ -0,0 +1 @@ +Para los secretos almacenados a nivel organizacional, peudes utilizar las políticas de acceso para controlar qué repositorios pueden utilizar secretos organizacionales. Los secretos a nivel organizacional te permiten compartir secretos entre repositorios múltiples, lo cual reduce la necesidad de crear secretos duplicados. El actualizar un secreto de organización en una ubicación también garantiza que el cambio tome efecto en todos los flujos de trabajo del repositorio que lo utilicen. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-auto-removal.md new file mode 100644 index 0000000000000..d35854108bb78 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-auto-removal.md @@ -0,0 +1 @@ +Un ejecutor auto-hospedado se eliminará automáticamente de {% data variables.product.product_name %} si no se ha conectado a {% data variables.product.prodname_actions %} por más de 30 días. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md new file mode 100644 index 0000000000000..442edf5f31448 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md @@ -0,0 +1,10 @@ + +#### Revisar que tu ejecutor auto-hospedado se haya agregado exitosamente + +Después de completar los pasos para agregar un ejecutor autoalojado, el ejecutor y su estado se enumeran ahora en "Self-hosted runners" (Ejecutores autoalojados). + +La aplicación del ejecutor autoalojado debe estar activa para que el ejecutor acepte trabajos. Cuando la aplicación del ejecutor está conectada a {% data variables.product.product_name %} y lista para recibir trabajos, verás el siguiente mensaje en la terminal de la máquina. + +{% data reusables.github-actions.self-hosted-runner-connected-output %} + +Para obtener más información, consulta la sección "[Monitorear y solucionar problemas de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)". diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md new file mode 100644 index 0000000000000..51361f604abcf --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -0,0 +1,12 @@ +1. En la sección de **Ejecutores auto-hospedados** de la página de configuración, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecución que quieras configurar, luego da clic en **Editar nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. Modifica tus opciones de política o cambia el nombre del grupo ejecutor. + + {% warning %} + + **Warning** + + {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} + + Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." + + {% endwarning %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md new file mode 100644 index 0000000000000..02b7166c84529 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md @@ -0,0 +1,18 @@ +1. Selecciona el sistema operativo y arquitectura de tu máquina de ejecutor auto-hospedado. ![Selecciona el sistema operativo del ejecutor autoalojado](/assets/images/help/settings/actions-runner-architecture-os.png) + + +1. Verás instrucciones que te mostrarán cómo descargar la aplicación del ejecutor e instalarla en tu máquina de ejecutor autoalojado. + + Abre un shell en tu máquina de ejecutor autoalojado y ejecuta cada comando del shell en el orden que se muestra. + + {% note %} + + **Nota:** En Windows, si deseas instalar la aplicación del ejecutor autoalojado como un servicio, debes abrir un shell con privilegios de administrador. También recomendamos que uses `C:\actions-runner` como el directorio para la aplicación del ejecutor autoalojado de modo que las cuentas del sistema de Windows puedan acceder al directorio del ejecutor. + + {% endnote %} + + Las instrucciones te guían para completar estas tareas: + - Descargar y extraer la aplicación de ejecutor autoalojado. + - Ejecutar el script `config` para configurar la aplicación del ejecutor auto-hospedado y registrarlo con {% data variables.product.prodname_actions %}. El script `config` requiere la URL destino y un token de tiempo limitado generado automáticamente para autenticar la solicitud. + - En Windows, el script `config` también te pregunta si deseas instalar la aplicación del ejecutor autoalojado como un servicio. Para Linux y macOS, puedes instalar un servicio después de que termines de agregar el ejecutor. Para obtener más información, consulta "[Configurar la aplicación del ejecutor autoalojado como un servicio](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)." + - Ejecutar la aplicación del ejecutor autoalojado para conectar la máquina a las {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-connected-output.md new file mode 100644 index 0000000000000..91b27bd97fcda --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-connected-output.md @@ -0,0 +1,5 @@ +```shell +√ Connected to GitHub + +2019-10-24 05:45:56Z: Listening for Jobs +``` diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-description.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-description.md new file mode 100644 index 0000000000000..8971b675547e2 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-description.md @@ -0,0 +1 @@ +Los ejecutores auto-hospedados ofrecen más control sobre las herramientas del hardware, sistema operativo y software que lo que ofrecen los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Con los ejecutores auto-hospedados, puedes elegir crear una configuración de hardware personalizada con más poder de procesamiento o más memoria para ejecutar jobs más grandes, instalar software disponible en tu red local, y escoger un sistema operativo que no se ofrezca en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md new file mode 100644 index 0000000000000..0b1919b9ba6e6 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md @@ -0,0 +1,3 @@ +Para especificar un ejecutor auto-hospedado para tu trabajo, configura `runs-on` en tu archivo de flujo de trabajo con las etiquetas de dicho ejecutor. + +Todos los ejecutores auto-programados tienen la etiqueta `self-hosted` y puedes seleccionar cualquiera de ellos para proporcionar únicamente dicha etiqueta. Como alternativa, puedes utilizar `self-hosted` en un arreglo con etiquetas adicionales, tales como aquellas para un sistema operativo o arquitectura de sistema específicos, para seleccionar únicamente los tipos de ejecutor que especificas. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md new file mode 100644 index 0000000000000..a38f96f720f85 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md @@ -0,0 +1 @@ +1. Ubica el ejecutor que quieres actualizar y da clic en {% octicon "triangle-down" aria-label="The downward triangle" %} para ver el menú de selección de etiquetas. Este menú muestra todas las etiquetas personalizadas disponibles para tu ejecutor auto-hospedado. Las etiquetas que ya hayas asignado a tu ejecutor auto-hospedado tienen un {% octicon "check" aria-label="Check mark" %} junto a ellas. ![Cambiar la etiqueta del ejecutor](/assets/images/help/settings/actions-runner-list-label.png) diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list-group.md new file mode 100644 index 0000000000000..3b975c069cf56 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list-group.md @@ -0,0 +1 @@ +1. Si tu ejecutor está en un grupo, ubica el grupo ejecutor y da clic en {% octicon "chevron-down" aria-label="The downward chevron" %} para ver la lista de ejecutores. ![Listar el grupo ejecutor](/assets/images/help/settings/actions-org-enterprise-list-group-runners.png) diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md new file mode 100644 index 0000000000000..365516e1870d4 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md @@ -0,0 +1 @@ + 1. Ubica la lista de ejecutores bajo "Ejecutores auto-hospedados". diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md new file mode 100644 index 0000000000000..046dda6af7ff4 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md @@ -0,0 +1,9 @@ +A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. Para administrar un ejecutor auto-hospedado, debes tener los siguientes permisos, dependiendo de donde se agregó éste: +- **Repositorio de usuario**: debes ser el propietario del repositorio. +- **Organización**: Debes ser un propietario de la organización. +- **Repositorio de la organización**: Debes ser un propietario de la organización, o tener acceso administrativo al repositorio. +{% if currentVersion == "free-pro-team@latest" %} +- **Cuenta empresarial**: Debes ser un propietario de la empresa. +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +- **Empresa**: debes ser un administrador de sitio de {% data variables.product.prodname_enterprise %}. +{% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md new file mode 100644 index 0000000000000..ef245fb215195 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md @@ -0,0 +1 @@ +1. En tu repositorio de organización, navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md new file mode 100644 index 0000000000000..21d5b4bb7790c --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -0,0 +1,12 @@ +1. Navega a donde está registrado tu ejecutor auto-hospedado: + * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. + * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**: + + 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. + 1. En la barra lateral izquierda, da clic en **Resumen empresarial**. + 1. {% endif %} En la barra lateral de empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. +1. Navega a los ajustes de {% data variables.product.prodname_actions %}: + * **En un repositorio de organización**: da clic en **Acciones** en la barra lateral izquierda. + + ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) + * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..b5c9a384a2868 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removal-impact.md new file mode 100644 index 0000000000000..e4b917f98a2d1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removal-impact.md @@ -0,0 +1 @@ +Este procedimiento eliminará el ejecutor auto-hospedado permanentemente. Si solo deseas detener de forma temporal un ejecutor de los trabajos asignados, puedes apagar la máquina o detener la aplicación `run`. El ejecutor permanecerá asignado en un estado "fuera de línea" y no ejecutará ningún job hasta que lo reinicies utilizando la aplicación `run`. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md new file mode 100644 index 0000000000000..5e1d8cf7cca2a --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -0,0 +1,15 @@ +1. Debajo de **Ejecutores auto-hospedados**, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista. +1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al ejecutor que quieres eliminar, y luego da clic en **Eliminar**. + + ![Eliminar una configuración de ejecutor autoalojado](/assets/images/help/settings/actions-runner-remove.png) +1. Verás las instrucciones para eliminar el ejecutor auto-hospedado. Completa cualquiera de los siguientes pasos para eliminar el ejecutor, dependiendo de si aún se puede acceder a él: + + * **Si tienes acceso a la máquina del ejecutor:** Sigue las instrucciones en la pantalla para que el sistema operativo de tu máquina ejecute el comando de eliminación. Las instrucciones incluyen la URL solicitada y un token de tiempo limitado generado automáticamente. + + El comando de eliminación realiza las siguientes tareas: + + * Elimina el ejecutor de {% data variables.product.product_name %}. + * Elimina cualquier archivo de configuración de la aplicación del ejecutor autoalojado en la máquina. + * Elimina todos los servicios configurados si no se ejecuta en modo interactivo. + + * **Si no tienes acceso a la máquina:** Da clic en **Sí, forzar la eliminación de este ejecutor** para forzar a {% data variables.product.product_name %} a que remueva el ejecutor. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reqs-docker.md new file mode 100644 index 0000000000000..de3ca7dbdd3e8 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reqs-docker.md @@ -0,0 +1 @@ +Los ejecutores auto-hospedados deberán utilizar un sistema operativo Linux y tener Docker instalado para ejecutar las acciones de contenedores de Docker. Para obtener más información acerca de los requisitos de los ejecutores auto-hospedados, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#requirements-for-self-hosted-runner-machines)". diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reusing.md new file mode 100644 index 0000000000000..4287f97980ff8 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reusing.md @@ -0,0 +1 @@ +Como alternativa, si no tienes acceso al repositorio, organización o empresa en {% data variables.product.product_name %} para eliminar un ejecutor, pero te gustaría reutilizar la máquina del ejecutor, entonces puedes borrar el archivo `.runner` dentro del directorio de la aplicación del ejecutor auto-hospedado. Esto permite que el ejecutor se registre sin tener que volver a descargar la aplicación del ejecutor auto-hospedado. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-security.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-security.md new file mode 100644 index 0000000000000..052a6838928d9 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-security.md @@ -0,0 +1,3 @@ +Te recomendamos que no utilices ejecutores auto-hospedados con repositorios públicos. + +Las bifurcaciones de tu repositorio público pueden ejecutar código potencialmente peligroso en tu máquina de ejecutor auto-hospedado creando una solicitud de extracción que ejecute el código en un flujo de trabajo. diff --git a/translations/es-ES/data/reusables/github-actions/service-container-add-script.md b/translations/es-ES/data/reusables/github-actions/service-container-add-script.md new file mode 100644 index 0000000000000..399a3bd0eeb38 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-container-add-script.md @@ -0,0 +1 @@ +Agrega a tu repositorio un archivo nuevo llamado *client.js* con el siguiente código. diff --git a/translations/es-ES/data/reusables/github-actions/service-container-host-runner.md b/translations/es-ES/data/reusables/github-actions/service-container-host-runner.md new file mode 100644 index 0000000000000..0ef61112d6460 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-container-host-runner.md @@ -0,0 +1 @@ +El ejemplo utiliza el ejecutor `ubuntu-latest` hospedado en {% data variables.product.prodname_dotcom %} como el hospedaje de Docker. diff --git a/translations/es-ES/data/reusables/github-actions/service-container-host.md b/translations/es-ES/data/reusables/github-actions/service-container-host.md new file mode 100644 index 0000000000000..57da27dae6d86 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-container-host.md @@ -0,0 +1 @@ +Este flujo de trabajo configura un job que se ejecuta en el contenedor `node:10.18-jessie` y utiiza el ejecutor `ubuntu-latest` hospedado en {% data variables.product.prodname_dotcom %} como el alojamiento de Docker para el contenedor. Para obtener más información acerca del contenedor `node:10.18-jessie`, consulta la [imagen del nodo](https://hub.docker.com/_/node) en Docker Hub. diff --git a/translations/es-ES/data/reusables/github-actions/service-container-localhost.md b/translations/es-ES/data/reusables/github-actions/service-container-localhost.md new file mode 100644 index 0000000000000..ee26d0b158566 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-container-localhost.md @@ -0,0 +1 @@ +El nombre del hospedaje es `localhost` o `127.0.0.1`. diff --git a/translations/es-ES/data/reusables/github-actions/service-container-prereqs.md b/translations/es-ES/data/reusables/github-actions/service-container-prereqs.md new file mode 100644 index 0000000000000..97d130245e9b8 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-container-prereqs.md @@ -0,0 +1 @@ +Debes familiarizarte con la forma en la que trabajan los contenedores de servicio con {% data variables.product.prodname_actions %} y las diferencias de conexión de red entre los jobs que se están ejecutando directamente en el ejecutor y las que lo hacen en un contenedor. Para obtener más información, consulta la sección "[Acerca de los contenedores de servicios](/actions/automating-your-workflow-with-github-actions/about-service-containers)". diff --git a/translations/es-ES/data/reusables/github-actions/service-template-steps.md b/translations/es-ES/data/reusables/github-actions/service-template-steps.md new file mode 100644 index 0000000000000..01fd9eb0693f0 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/service-template-steps.md @@ -0,0 +1,5 @@ +El flujo de trabajo realiza los siguientes pasos: + +1. Verifica el repositorio en el ejecutor +1. Instala las dependencias +1. Ejecuta un script para crear un cliente diff --git a/translations/es-ES/data/reusables/github-actions/setup-node-intro.md b/translations/es-ES/data/reusables/github-actions/setup-node-intro.md new file mode 100644 index 0000000000000..5b828b1ba5071 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/setup-node-intro.md @@ -0,0 +1 @@ +Puedes utilizar la acción `setup-node` para crear un archivo local de tipo *.npmrc* en el ejecutor que configura el registro y alcance predeterminados. La acción `setup-node` también acepta un token de autenticación como entrada, el cual se utiliza para acceder a los registros privados o paquetes de nodo publicados. Para obtener más información, consulta la sección [`setup-node`](https://github.com/actions/setup-node/). diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-environment.md b/translations/es-ES/data/reusables/github-actions/sidebar-environment.md new file mode 100644 index 0000000000000..fa7230e71df83 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/sidebar-environment.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Ambientes**. diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md new file mode 100644 index 0000000000000..9de5376bcd9ff --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Secrets** (Secretos). diff --git a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md new file mode 100644 index 0000000000000..bfa353f5d3df9 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md @@ -0,0 +1,8 @@ +| Entorno virtual | Etiqueta de flujo de trabajo YAML | +| -------------------- | --------------------------------- | +| Windows Server 2019 | `windows-latest` o `windows-2019` | +| Ubuntu 20.04 | `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` o `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md new file mode 100644 index 0000000000000..16447a14e66f5 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** El ambiente virtual de Ubuntu 20.04 se proporciona actualmente como una vista previa únicamente. La etiqueta de flujo de trabajo de YAML `ubuntu-latest` aún utiliza el ambiente virtual de Ubuntu 18.04. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/usage-api-requests.md b/translations/es-ES/data/reusables/github-actions/usage-api-requests.md new file mode 100644 index 0000000000000..3cb00fe64b077 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/usage-api-requests.md @@ -0,0 +1 @@ +- **Solicitudes de la API** - Puedes ejecutar hasta 1000 solicitudes de API en una hora en todas las acciones dentro de un repositorio. Si esto se excede, los llamados adicionales a la API fallarán, lo cual puede ocasionar que los jobs fallen también. diff --git a/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md b/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md new file mode 100644 index 0000000000000..b9650b6e473da --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md @@ -0,0 +1 @@ +Una matriz de jobs puede generar un máximo de 256 jobs por ejecución de flujo de trabajo. Este límite también aplica para los ejecutores auto-hospedados. diff --git a/translations/es-ES/data/reusables/github-actions/usage-workflow-run-time.md b/translations/es-ES/data/reusables/github-actions/usage-workflow-run-time.md new file mode 100644 index 0000000000000..1ebba95ade520 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/usage-workflow-run-time.md @@ -0,0 +1 @@ +- **Tiempo de ejecución del flujo de trabajo** - Cada flujo de trabajo se limita a 72 horas. Si un flujo de trabajo llega a este límite, se cancelará. diff --git a/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..bfe161ec4c022 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/reference/environment-variables#default-environment-variables)." +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. Para obtener más información, consulta "[Contextos](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)". + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/es-ES/data/reusables/github-ae/about-billing.md b/translations/es-ES/data/reusables/github-ae/about-billing.md new file mode 100644 index 0000000000000..9e7ed843b20d1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-ae/about-billing.md @@ -0,0 +1 @@ +You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md b/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md new file mode 100644 index 0000000000000..dd699d9ad63fe --- /dev/null +++ b/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_managed %} enables you to move your software development to the cloud while meeting the most stringent security and compliance requirements. diff --git a/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md new file mode 100644 index 0000000000000..75c6726d7c2e2 --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -0,0 +1 @@ +1. Iniciar sesión en {% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/es-ES/data/reusables/github-connect/access-profile-settings.md b/translations/es-ES/data/reusables/github-connect/access-profile-settings.md new file mode 100644 index 0000000000000..c601a6309d164 --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/access-profile-settings.md @@ -0,0 +1 @@ +1. En {% data variables.product.product_location_enterprise %}, en el ángulo superior derecho de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Settings** (Parámetros). ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/es-ES/data/reusables/github-connect/authorize-connection.md b/translations/es-ES/data/reusables/github-connect/authorize-connection.md new file mode 100644 index 0000000000000..220d5c6ec75bb --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/authorize-connection.md @@ -0,0 +1 @@ +1. Revisa los recursos a los que {% data variables.product.prodname_ghe_server %} accederá desde tu cuenta de {% data variables.product.prodname_dotcom_the_website %}, posteriormente, da clic en **Autorizar**. ![Autorizar conexión entre GitHub Enterprise Server y GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) diff --git a/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md new file mode 100644 index 0000000000000..c375744a0159d --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -0,0 +1 @@ +1. Da clic en **Conectar con {% data variables.product.prodname_dotcom_the_website %}**. ![Conectarse con GitHub.com desde la configuración de GitHub Enterprise Server](/assets/images/help/settings/github.com_end_user_connection.png) diff --git a/translations/es-ES/data/reusables/github-connect/github-connect-tab-user-settings.md b/translations/es-ES/data/reusables/github-connect/github-connect-tab-user-settings.md new file mode 100644 index 0000000000000..1ba99c561987f --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/github-connect-tab-user-settings.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_connect %}**. ![Pestaña de GitHub Connect en la barra lateral de la configuración de usuario](/assets/images/help/settings/github-connect-tab-user-settings.png) diff --git a/translations/es-ES/data/reusables/github-connect/sync-frequency.md b/translations/es-ES/data/reusables/github-connect/sync-frequency.md new file mode 100644 index 0000000000000..93299f0265f4a --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/sync-frequency.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} envía actualizaciones cada hora. diff --git a/translations/es-ES/data/reusables/github-insights/about-key-metrics.md b/translations/es-ES/data/reusables/github-insights/about-key-metrics.md new file mode 100644 index 0000000000000..fad2d837fd904 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/about-key-metrics.md @@ -0,0 +1 @@ +{% data variables.product.prodname_insights %} resalta las métricas clave ya que éstas se pueden accionar directamente para incrementar tanto velocidad como calidad. Las métricas clave son útiles para todos en la organización, desde colaboradores individuales y sus gerentes, hasta ejecutivos que buscan un panorama más amplio. diff --git a/translations/es-ES/data/reusables/github-insights/about-reports.md b/translations/es-ES/data/reusables/github-insights/about-reports.md new file mode 100644 index 0000000000000..aa0ed75190035 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/about-reports.md @@ -0,0 +1 @@ +Todas las otras métricas se incluyen en los reportes, los cuales contienen diversas métricas sobre el mismo tema, tal como las solicitudes de extracción o el código. diff --git a/translations/es-ES/data/reusables/github-insights/add-organizations.md b/translations/es-ES/data/reusables/github-insights/add-organizations.md new file mode 100644 index 0000000000000..38536525f533d --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/add-organizations.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de la página, da clic en **Agregar Organización(es)**. Verás una lista de organizaciones asociadas con tu cuenta de {% data variables.product.prodname_enterprise %}. ![Botón de Agregar Organización(es)](/assets/images/help/insights/add-organizations.png) diff --git a/translations/es-ES/data/reusables/github-insights/app-id.md b/translations/es-ES/data/reusables/github-insights/app-id.md new file mode 100644 index 0000000000000..5a27c45ff89bd --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/app-id.md @@ -0,0 +1 @@ +1. Debajo de "App ID", teclea la ID de la App de tu {% data variables.product.prodname_github_app %}, la cual grabaste cuando creaste dicha app. ![Campo de App ID](/assets/images/help/insights/app-id.png) diff --git a/translations/es-ES/data/reusables/github-insights/choose-key-metric.md b/translations/es-ES/data/reusables/github-insights/choose-key-metric.md new file mode 100644 index 0000000000000..5396fef993b43 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/choose-key-metric.md @@ -0,0 +1 @@ +2. Debajo de **{% octicon "graph" aria-label="The graph icon" %} Métricas clave**, haz clic en el nombre de la métrica que deseas ver. ![Lista de métricas clave](/assets/images/help/insights/key-metrics-list.png) diff --git a/translations/es-ES/data/reusables/github-insights/client-id.md b/translations/es-ES/data/reusables/github-insights/client-id.md new file mode 100644 index 0000000000000..241bbd49c8b1e --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/client-id.md @@ -0,0 +1 @@ +1. Debajo de "ID de Cliente", teclea la ID de cliente de tu {% data variables.product.prodname_github_app %}, la cual grabaste cuando creaste la app. ![Campo de ID de Cliente](/assets/images/help/insights/client-id.png) diff --git a/translations/es-ES/data/reusables/github-insights/client-secret.md b/translations/es-ES/data/reusables/github-insights/client-secret.md new file mode 100644 index 0000000000000..a4112ec3011e1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/client-secret.md @@ -0,0 +1 @@ +1. Debajo de "Secreto de Cliente", teclea el secreto del cliente de tu {% data variables.product.prodname_github_app %}, el cual grabaste cuando creaste la app. ![Campo de secreto de cliente](/assets/images/help/insights/client-secret.png) diff --git a/translations/es-ES/data/reusables/github-insights/contributors-tab.md b/translations/es-ES/data/reusables/github-insights/contributors-tab.md new file mode 100644 index 0000000000000..68450baca62a3 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/contributors-tab.md @@ -0,0 +1 @@ +1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Contributors**. ![Pestaña de colaboradores](/assets/images/help/insights/contributors-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/docker-requirements.md b/translations/es-ES/data/reusables/github-insights/docker-requirements.md new file mode 100644 index 0000000000000..a2e194ab04af1 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/docker-requirements.md @@ -0,0 +1 @@ +El servidor de aplicaciones puede requerir que el demonio de Docker se ejecute como sudo. Kubernetes no es compatible. diff --git a/translations/es-ES/data/reusables/github-insights/download-latest-release.md b/translations/es-ES/data/reusables/github-insights/download-latest-release.md new file mode 100644 index 0000000000000..0df5bd819ff5e --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/download-latest-release.md @@ -0,0 +1,3 @@ +1. Desde el servidor de la aplicación, navega al último lanzamiento de {% data variables.product.prodname_insights %} en la página de lanzamientos para `github/insights-releases`. +2. Para descargar el último lanzamiento, debajo de "Activos", da clic en `insights-VERSION.tar.gz`. ![Activo de instalación](/assets/images/help/insights/installation-tgz.png) +3. Descomprime el directorio. diff --git a/translations/es-ES/data/reusables/github-insights/edit-contributor.md b/translations/es-ES/data/reusables/github-insights/edit-contributor.md new file mode 100644 index 0000000000000..41453000203e6 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/edit-contributor.md @@ -0,0 +1 @@ +1. Da clic en **Editar** a la derecha del colaborador que quieras administrar. ![Botón editar](/assets/images/help/insights/edit-contributor.png) diff --git a/translations/es-ES/data/reusables/github-insights/edit-group.md b/translations/es-ES/data/reusables/github-insights/edit-group.md new file mode 100644 index 0000000000000..c7f8f7c89db8f --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/edit-group.md @@ -0,0 +1 @@ +1. Da clic en **Editar** a la derecha del nombre del grupo. ![Botón editar](/assets/images/help/insights/edit-group-button.png) diff --git a/translations/es-ES/data/reusables/github-insights/edit-team.md b/translations/es-ES/data/reusables/github-insights/edit-team.md new file mode 100644 index 0000000000000..f03a3f2fcb4ab --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/edit-team.md @@ -0,0 +1 @@ +1. Da clic en **Editar Equipo** a un costado del equipo al que quieras agregar contribuyentes. ![Botón de editar equipo](/assets/images/help/insights/edit-team.png) diff --git a/translations/es-ES/data/reusables/github-insights/enterprise-api-url.md b/translations/es-ES/data/reusables/github-insights/enterprise-api-url.md new file mode 100644 index 0000000000000..31f9445761b45 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/enterprise-api-url.md @@ -0,0 +1 @@ +1. Debajo de "URL de la API de {% data variables.product.prodname_dotcom %}", teclea {% if currentVersion == "free-pro-team@latest" %}https://api.github.com {% else %}la URL que utilizas para acceder a {% data variables.product.prodname_enterprise %}{% endif %}. ![Campo de URL de la API de {% data variables.product.prodname_enterprise %}](/assets/images/help/insights/enterprise-api-url.png) diff --git a/translations/es-ES/data/reusables/github-insights/events-tab.md b/translations/es-ES/data/reusables/github-insights/events-tab.md new file mode 100644 index 0000000000000..8d1576cfb4a9a --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/events-tab.md @@ -0,0 +1 @@ +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Eventos**. ![Pestaña de eventos](/assets/images/help/insights/events-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/events.md b/translations/es-ES/data/reusables/github-insights/events.md new file mode 100644 index 0000000000000..adbb3ec604f2d --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/events.md @@ -0,0 +1 @@ +Puedes utilizar los eventos para marcar días o periodos importantes en las métricas para agregar contexto para los espectadores. diff --git a/translations/es-ES/data/reusables/github-insights/exclude-files-tab.md b/translations/es-ES/data/reusables/github-insights/exclude-files-tab.md new file mode 100644 index 0000000000000..aeefb67fe0c11 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/exclude-files-tab.md @@ -0,0 +1 @@ +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Excluir archivos**. ![Pestaña de excluir eventos](/assets/images/help/insights/exclude-files-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/filter-reports.md b/translations/es-ES/data/reusables/github-insights/filter-reports.md new file mode 100644 index 0000000000000..bb9e4484786a3 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/filter-reports.md @@ -0,0 +1 @@ +1. Opcionalmente, para filtrar todas las métricas de la página, debajo de éstas, utiliza los menús desplegables "Equipos", "Repos" o de rango de fechas. ![Menús desplegables de los filtros](/assets/images/help/insights/filter-drop-downs.png) diff --git a/translations/es-ES/data/reusables/github-insights/insights-license.md b/translations/es-ES/data/reusables/github-insights/insights-license.md new file mode 100644 index 0000000000000..476846e6ea865 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/insights-license.md @@ -0,0 +1 @@ +1. Debajo de "Licencia de {% data variables.product.prodname_insights %}", da clic en "Escoger Archivos", y luego carga tu archivo de licencia de {% data variables.product.prodname_enterprise %}. ![Botón de escoger archivos](/assets/images/help/insights/choose-files.png) diff --git a/translations/es-ES/data/reusables/github-insights/install-script.md b/translations/es-ES/data/reusables/github-insights/install-script.md new file mode 100644 index 0000000000000..fd83531869c45 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/install-script.md @@ -0,0 +1,9 @@ +4. Ejecuta el script del shell `Install.sh`. +5. Para habilitar SSL, ingresa el certificado SSL (`.crt/.cer/.pem`). Si no quieres habilitar SSL, déjalo en blanco. +6. Si eliges habilitar SSL, ingresa la llave SSL (`.key`). De lo contrario, déjalo en blanco. +5. Ingresa el nombre del host, el cual es la misma URL que utilizas para el servidor de la aplicación cuando creas la {% data variables.product.prodname_github_app %}. +6. La instalación tomará unos cuantos minutos en ejecutarse. Una vez que esté completo, verás un mensaje impreso en el terminal. + ``` + Installation complete + Run /opt/insights/scripts/start.sh to start GitHub Insights + ``` diff --git a/translations/es-ES/data/reusables/github-insights/key-metrics-and-reports.md b/translations/es-ES/data/reusables/github-insights/key-metrics-and-reports.md new file mode 100644 index 0000000000000..5aa1b6c7f8f53 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/key-metrics-and-reports.md @@ -0,0 +1 @@ +Los datos disponibles en {% data variables.product.prodname_insights %} se dividen en métricas clave y reportes. diff --git a/translations/es-ES/data/reusables/github-insights/manage-metrics.md b/translations/es-ES/data/reusables/github-insights/manage-metrics.md new file mode 100644 index 0000000000000..12e9c977100f9 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/manage-metrics.md @@ -0,0 +1 @@ +Las personas con permisos de administrador en {% data variables.product.prodname_insights %} pueden administrar qué métricas se mostrarán. Para obtener más información, consulta la sección "[Administrar métricas y reportes disponibles](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)" diff --git a/translations/es-ES/data/reusables/github-insights/navigate-to-key-metrics.md b/translations/es-ES/data/reusables/github-insights/navigate-to-key-metrics.md new file mode 100644 index 0000000000000..ba4d3918a7da4 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/navigate-to-key-metrics.md @@ -0,0 +1 @@ +1. En {% data variables.product.prodname_insights %}, haz clic en **{% octicon "graph" aria-label="The graph icon" %} Métricas clave**. ![Pestaña Key Metrics (Métricas clave)](/assets/images/help/insights/key-metrics-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/permissions-levels.md b/translations/es-ES/data/reusables/github-insights/permissions-levels.md new file mode 100644 index 0000000000000..9e7c315fd7007 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/permissions-levels.md @@ -0,0 +1,5 @@ +{% data variables.product.prodname_insights %} tiene dos niveles de permiso. + +- Los permisos administrativos corresponden al rol de administrador de sitio en {% data variables.product.prodname_enterprise %}. Las personas con permisos administrativos tiene acceso a todas las configuraciones de {% data variables.product.prodname_insights %}. + +- El resto de los usuarios en {% data variables.product.prodname_enterprise %} tienen cuentas de usuario en {% data variables.product.prodname_insights %}. Los usuarios pueden ver todas las métricas, pero tienen acceso limitado a las configuraciones. diff --git a/translations/es-ES/data/reusables/github-insights/private-key.md b/translations/es-ES/data/reusables/github-insights/private-key.md new file mode 100644 index 0000000000000..2176725ee4a2a --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/private-key.md @@ -0,0 +1 @@ +1. Debajo de "Llave Privada", teclea la llave privada de tu {% data variables.product.prodname_github_app %}, la cual se contiene en el archivo PEM que descargaste mientras creabas la app. ![Campo de llave privada](/assets/images/help/insights/private-key.png) diff --git a/translations/es-ES/data/reusables/github-insights/repo-groups-tab.md b/translations/es-ES/data/reusables/github-insights/repo-groups-tab.md new file mode 100644 index 0000000000000..c64ec82d9f996 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/repo-groups-tab.md @@ -0,0 +1 @@ +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Grupos de Repo**. ![Pestaña de grupos de Repo](/assets/images/help/insights/repo-groups-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/repositories-tab.md b/translations/es-ES/data/reusables/github-insights/repositories-tab.md new file mode 100644 index 0000000000000..0b75836d25c04 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/repositories-tab.md @@ -0,0 +1 @@ +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Repositorios**. ![Pestaña Repositories (Repositorios)](/assets/images/help/insights/repositories-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/repository-groups.md b/translations/es-ES/data/reusables/github-insights/repository-groups.md new file mode 100644 index 0000000000000..22c80f4b52149 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/repository-groups.md @@ -0,0 +1 @@ +Puedes crear un grupo de repositorios para ver los datos combinados para los repositorios relacionados. Puedes filtrar por grupo de repositorio en cada métrica y reporte. diff --git a/translations/es-ES/data/reusables/github-insights/requires-machine.md b/translations/es-ES/data/reusables/github-insights/requires-machine.md new file mode 100644 index 0000000000000..1e3a979f4f8e3 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/requires-machine.md @@ -0,0 +1 @@ +{% data variables.product.prodname_insights %} requiere una máquina, llamada servidor de la aplicación, hospedada ya sea en la nube o localmente. diff --git a/translations/es-ES/data/reusables/github-insights/run-script.md b/translations/es-ES/data/reusables/github-insights/run-script.md new file mode 100644 index 0000000000000..04a2265d0907b --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/run-script.md @@ -0,0 +1,5 @@ +4. Para iniciar con {% data variables.product.prodname_insights %}, ejecuta el script del shell `/opt/insights/scripts/start.sh`. +5. Si es la primera vez que inicias {% data variables.product.prodname_insights %}, el script tomará algunos minutos en ejecutarse. Una vez que esté completo, verás un mensaje impreso en el terminal. + ``` + GitHub Insights is running! + ``` diff --git a/translations/es-ES/data/reusables/github-insights/settings-tab.md b/translations/es-ES/data/reusables/github-insights/settings-tab.md new file mode 100644 index 0000000000000..069c991a2d465 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/settings-tab.md @@ -0,0 +1 @@ +1. En {% data variables.product.prodname_insights %}, da clic en **{% octicon "gear" aria-label="The gear icon" %} Configuración**. ![Pestaña Parámetros](/assets/images/help/insights/settings-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/skip-ssl.md b/translations/es-ES/data/reusables/github-insights/skip-ssl.md new file mode 100644 index 0000000000000..2877bccb31839 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/skip-ssl.md @@ -0,0 +1 @@ +1. Si no proporcionaste un certificado SSL durante la instalación, selecciona **Saltar Verificación de Certificado SSL**. ![Casilla de saltar verificación de certificado SSL](/assets/images/help/insights/skip-ssl.png) diff --git a/translations/es-ES/data/reusables/github-insights/teams-tab.md b/translations/es-ES/data/reusables/github-insights/teams-tab.md new file mode 100644 index 0000000000000..b05be6ddd542f --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/teams-tab.md @@ -0,0 +1 @@ +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Equipos**. ![Pestaña de equipos](/assets/images/help/insights/teams-tab.png) diff --git a/translations/es-ES/data/reusables/github-insights/view-events.md b/translations/es-ES/data/reusables/github-insights/view-events.md new file mode 100644 index 0000000000000..e1c12015a7d6d --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/view-events.md @@ -0,0 +1 @@ +2. Opcionalmente, para ver los eventos que ocurrieron durante cierto tiempo, da clic en el círculo enumerado sobre este lapso de tiempo. ![Círculos numerados para indicar eventos](/assets/images/help/insights/event-circles.png) diff --git a/translations/es-ES/data/reusables/github-insights/webhook-secret.md b/translations/es-ES/data/reusables/github-insights/webhook-secret.md new file mode 100644 index 0000000000000..58f2a01e14d48 --- /dev/null +++ b/translations/es-ES/data/reusables/github-insights/webhook-secret.md @@ -0,0 +1 @@ +1. Debajo de "Secretod e Webhook", teclea el secreto de webhook de tu {% data variables.product.prodname_github_app %}, el cual grabaste cuando la creaste. ![Campo secreto de webhook](/assets/images/help/insights/webhook-secret.png) diff --git a/translations/es-ES/data/reusables/gpg/copy-gpg-key-id.md b/translations/es-ES/data/reusables/gpg/copy-gpg-key-id.md new file mode 100644 index 0000000000000..772ad766b3a22 --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/copy-gpg-key-id.md @@ -0,0 +1,9 @@ +1. De la lista de llaves GPG, copia la ID de la llave GPG que quieres utilizar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: + ```shell + $ gpg --list-secret-keys --keyid-format LONG + /Users/hubot/.gnupg/secring.gpg + ------------------------------------ + sec 4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10] + uid Hubot + ssb 4096R/42B317FD4BA89E7A 2016-03-10 + ``` diff --git a/translations/es-ES/data/reusables/gpg/desktop-support-for-commit-signing.md b/translations/es-ES/data/reusables/gpg/desktop-support-for-commit-signing.md new file mode 100644 index 0000000000000..6b66186106d3e --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/desktop-support-for-commit-signing.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:**[GitHub Desktop](https://desktop.github.com/) no es compatible con el firmado de confirmaciones. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/gpg/list-keys-with-note.md b/translations/es-ES/data/reusables/gpg/list-keys-with-note.md new file mode 100644 index 0000000000000..c5344541e1df7 --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/list-keys-with-note.md @@ -0,0 +1,10 @@ + +1. Utiliza el comando `gpg --list-secret-keys --keyid-format LONG` para enumerar las llaves GPG para las cuales tienes tanto una llave pública como privada. Se requiere una llave privada para registrar confirmaciones o etiquetas. + ```shell + $ gpg --list-secret-keys --keyid-format LONG +``` + {% note %} + + **Nota:** Algunas instalaciones GPG en Linux pueden requerir que uses `gpg2 --list-keys --keyid-format LONG` para visualizar una lista de tus llaves existentes en su lugar. En este caso también deberás configurar Git para que use `gpg2` by running `git config --global gpg.program gpg2`. + + {% endnote %} diff --git a/translations/es-ES/data/reusables/gpg/paste-gpg-key-id.md b/translations/es-ES/data/reusables/gpg/paste-gpg-key-id.md new file mode 100644 index 0000000000000..1cb8593e9324b --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/paste-gpg-key-id.md @@ -0,0 +1,4 @@ +1. Para configurar tu llave de firma GPG en Git, pega el siguiente texto en sustitución de la ID de la llave GPG que quieras utilizar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: + ```shell +$ git config --global user.signingkey 3AA5C34371567BD2 +``` diff --git a/translations/es-ES/data/reusables/gpg/private-email.md b/translations/es-ES/data/reusables/gpg/private-email.md new file mode 100644 index 0000000000000..0e4d0c891be30 --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/private-email.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Para mantener tu dirección de correo electrónico privada, utiliza tu +dirección de correo de tipo `no-reply` que proporcionó {% data variables.product.product_name %}. +{% endif %} diff --git a/translations/es-ES/data/reusables/gpg/smime-git-version.md b/translations/es-ES/data/reusables/gpg/smime-git-version.md new file mode 100644 index 0000000000000..785a1da369f4a --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/smime-git-version.md @@ -0,0 +1,6 @@ + +{% note %} + +**Nota:** la verificación de firma S/MIME está disponible desde Git 2.19 o posterior. Para actualizar tu versiíon de Git, consulta el sitio web de [Git](https://git-scm.com/downloads). + +{% endnote %} diff --git a/translations/es-ES/data/reusables/gpg/supported-gpg-key-algorithms.md b/translations/es-ES/data/reusables/gpg/supported-gpg-key-algorithms.md new file mode 100644 index 0000000000000..5a91347f8e9ed --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/supported-gpg-key-algorithms.md @@ -0,0 +1,11 @@ + +### Algoritmos compatibles de llave GPG + +{% data variables.product.product_name %} es compatible con varios algoritmos GPG. Si tratas de agregar una llave generada con un algoritmo no compatible, puedes llegar a un error. + +- RSA +- ElGamal +- DSA +- ECDH +- ECDSA +- EdDSA diff --git a/translations/es-ES/data/reusables/gpg/x-509-key.md b/translations/es-ES/data/reusables/gpg/x-509-key.md new file mode 100644 index 0000000000000..49e22d5866ca5 --- /dev/null +++ b/translations/es-ES/data/reusables/gpg/x-509-key.md @@ -0,0 +1,57 @@ + +### Informarle a Git acerca de tu llave X.509 + +Puedes usar [smimesign](https://github.com/github/smimesign) para firmar confirmaciones y etiquetas utilizando S/MIME en lugar de GPG. + +{% data reusables.gpg.smime-git-version %} + +1. Instala [smimesign](https://github.com/github/smimesign#installation). +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Configura Git para que use S/MIME para firmar confirmaciones y etiquetas. En Git 2.19 o posterior, utiliza los comandos `git config gpg.x509.program` y `git config gpg.format`: + - Para utilizar S/MIME para firmar todos los repositorios: + ```shell + $ git config --global gpg.x509.program smimesign + $ git config --global gpg.format x509 + ``` + - Para utilizar S/MIME para firmar un repositorio único: + ```shell + $ cd /path/to/my/repository + $ git config --local gpg.x509.program smimesign + $ git config --local gpg.format x509 + ``` + En Git 2.18 o inferior, utiliza el comando `git config gpg.program`: + - Para utilizar S/MIME para firmar todos los repositorios: + ```shell + $ git config --global gpg.program smimesign + ``` + - Para utilizar S/MIME para firmar un repositorio único: + ```shell + $ cd /path/to/my/repository + $ git config --local gpg.program smimesign + ``` + Si estás utilizando una llave X.509 que coincide con tu identidad de persona que confirma el cambio, puedes comenzar firmando confirmaciones y etiquetas. +4. Si no estás utilizando una llave X.509 que coincide con tu identidad de persona que confirmar el cambio, enumera las llaves X.509 para las cuales tienes tanto un certificado como una llave privada utilizando el comando `smimesign --list-keys`. + ```shell + $ smimesign --list-keys + ``` +5. De la lista de llaves X.509, copia el ID del certificado de la llave X.509 que desearías utilizar. En este ejemplo, el ID del certificado es `0ff455a2708394633e4bb2f88002e3cd80cbd76f`: + ```shell + $ smimesign --list-keys + ID: 0ff455a2708394633e4bb2f88002e3cd80cbd76f + S/N: a2dfa7e8c9c4d1616f1009c988bb70f + Algorithm: SHA256-RSA + Validity: 2017-11-22 00:00:00 +0000 UTC - 2020-11-22 12:00:00 +0000 UTC + Issuer: CN=DigiCert SHA2 Assured ID CA,OU=www.digicert.com,O=DigiCert Inc,C=US + Subject: CN=Octocat,O=GitHub\, Inc.,L=San Francisco,ST=California,C=US + Emails: octocat@github.com + ``` +6. Para configurar tu llave de firma X.509 en Git, pega el texto de abajo, sustituyendo el ID del certificado que copiaste anteriormente. + - Para utilizar tu llave X.509 para firmar todos los repositorios: + ```shell + $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f + ``` + - Para utilizar tu llave X.509 para firmar un repositorio único: + ```shell + $ cd /path/to/my/repository + $ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f + ``` diff --git a/translations/es-ES/data/reusables/identity-and-permissions/about-team-sync.md b/translations/es-ES/data/reusables/identity-and-permissions/about-team-sync.md new file mode 100644 index 0000000000000..dd3dc3b79e462 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/about-team-sync.md @@ -0,0 +1 @@ +Cuando sincronizas un equipo de {% data variables.product.prodname_dotcom %} con un grupo de IdP, los cambios a este grupo se reflejan automáticamente en {% data variables.product.product_name %}, reduciendo la necesidad de hacer actualizaciones manuales y scripts personalizados. Puedes utilizar un IdP con la sincronización de equipos para gestionar las tareas administrativas tales como el incorporar miembros nuevos, otorgar permisos nuevos para hacer movimientos dentro de una organización, y eliminar el acceso de un miembro a la organización. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-azure.md b/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-azure.md new file mode 100644 index 0000000000000..b9092ba95ae01 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-azure.md @@ -0,0 +1 @@ +1. Debajo de "Sincronización de equipo", da clic en **Habilitar para Azure AD**. ![Botón para habilitar la sincronización de equipo en la página de configuraciones de seguridad](/assets/images/help/teams/enable-team-synchronization.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-okta.md b/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-okta.md new file mode 100644 index 0000000000000..c967b7a6eba67 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/enable-team-sync-okta.md @@ -0,0 +1 @@ +1. Debajo de "Sincronización de equipo", da clic en **Habilitar para Okta**. ![Botón de habilitar sincronización de equipo para Okta en la página de configuraciones de seguridad](/assets/images/help/teams/enable-team-synchronization-okta.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md new file mode 100644 index 0000000000000..e06397ae2560b --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md @@ -0,0 +1 @@ +1. Debajo de "Descripción", teclea la descripción de la dirección IP o el rango de ellas que se permitirá. ![Campo clave para agregar un nombre a la dirección IP](/assets/images/help/security/ip-address-name-field.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md new file mode 100644 index 0000000000000..c5822b5f01998 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md @@ -0,0 +1 @@ +1. Haz clic en {% octicon "plus" aria-label="The plus icon" %} **Add** (Agregar). ![Botón Add allowed ip address (Agregar dirección ip permitida)](/assets/images/help/security/new-allowlist-entry-button.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md new file mode 100644 index 0000000000000..341761ada90d2 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md @@ -0,0 +1 @@ +1. Debajo de "Dirección IP", teclea una dirección o un rango de ellas, en notación CIDR. ![Campo clave para agregar una dirección IP](/assets/images/help/security/ip-address-field.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md new file mode 100644 index 0000000000000..c5af4df841b39 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md @@ -0,0 +1 @@ +Puedes aprobar el acceso para una dirección IP única o para un rango de ellas utilizando notación CIDR. Para obtener más información, consulta "[Notación CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" en Wikipedia. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md new file mode 100644 index 0000000000000..cf93a9a028e99 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md @@ -0,0 +1 @@ +1. Para borrar permanentemente la entrada, da clic en **Sí, borrar esta lista de direcciones IP permitidas**. ![Botón Permanently delete IP allow list entry (Borrar permanentemente la entrada de la lista de IP permitida)](/assets/images/help/security/perm-delete-allowlist-entry-button.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md new file mode 100644 index 0000000000000..3337ce284de40 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md @@ -0,0 +1 @@ +1. Debajo de "Lista de IP permitidas", a la derecha de la entrada que quieres borrar, da clic en **Borrar**. ![Botón Delete allowed IP address (Eliminar dirección IP permitida)](/assets/images/help/security/ip-address-delete-button.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md new file mode 100644 index 0000000000000..3eb92cb7dece2 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md @@ -0,0 +1 @@ +1. Teclea una descripción del rango de direcciones IP permitidas. ![Campo clave para agregar un nombre a la dirección IP](/assets/images/help/security/ip-address-edit-name-field.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md new file mode 100644 index 0000000000000..4b1f4fe3754ba --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md @@ -0,0 +1 @@ +1. Debajo de "Lista de IP permitidas", a la derecha de la entrada que quieres editar, da clic en **Editar**. ![Botón Edit allowed IP address (Editar dirección IP permitida)](/assets/images/help/security/ip-address-edit-button.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md new file mode 100644 index 0000000000000..d8c518c615165 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md @@ -0,0 +1 @@ +1. Teclea una dirección IP, o rango de direcciones, en notación CIDR. ![Campo clave para agregar una dirección IP](/assets/images/help/security/ip-address-edit-field.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-enable.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-enable.md new file mode 100644 index 0000000000000..e236790aec384 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-enable.md @@ -0,0 +1 @@ +Para aplicar la lista de IP permitidas, primero debes agregar direcciones a la lista, y después habilitarla. Debes agregar tu dirección IP actual o un rango coincidente antes de habilitar la lista de permisos de IP. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md new file mode 100644 index 0000000000000..ad17976c02642 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md @@ -0,0 +1 @@ +Por ejemplo, puedes permitir el acceso desde la única dirección IP de tu red de oficina. La lista de direcciones IP permitidas bloqueará el acceso mediante la web, las API y Git desde cualquier dirección IP que no se encuentre en ella. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/identity-and-permissions/supported-idps-team-sync.md b/translations/es-ES/data/reusables/identity-and-permissions/supported-idps-team-sync.md new file mode 100644 index 0000000000000..57a0092653b69 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/supported-idps-team-sync.md @@ -0,0 +1,3 @@ +Puedes utilizar la sincronización de equipos con los IdP compatibles. + - Azure AD + - Okta diff --git a/translations/es-ES/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/es-ES/data/reusables/identity-and-permissions/sync-team-with-idp-group.md new file mode 100644 index 0000000000000..0b9fef580c7c5 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -0,0 +1 @@ +Después de que habilites la sincronización de equipos, los mantenedores de equipo y propietarios de organización pueden conectar los equipos a un grupo de IdP en {% data variables.product.prodname_dotcom %} o a través de la API. Para obtener más información, consulta las secciones "[Sincronizar un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" y "[Sincronización de equipo](/rest/reference/teams#team-sync)". diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-azure-permissions.md new file mode 100644 index 0000000000000..a81249546948d --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -0,0 +1,4 @@ +Para habilitar la sincronización de equipo para Azure AD, tu instalación de Azure AD necesita los siguientes permisos. +- Lectura de todos los perfiles completos de usuarios +- Inicio de sesión y lectura del perfil de usuario +- Lectura de los datos del directorio diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm-saml.md new file mode 100644 index 0000000000000..e25f3ba376545 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -0,0 +1 @@ +3. Confirma que el SSO de SAML esté habilitado. Para obtener más información, consulta "[Administrar el inicio de sesión único de SAML para tu organización](/articles/managing-saml-single-sign-on-for-your-organization)". diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md new file mode 100644 index 0000000000000..744b90ab28cc6 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -0,0 +1,3 @@ +5. Confirm team synchronization. + - Si tienes acceso IdP, haz clic en **Enable team synchronization (Habilitar sincronización de equipo)**. Serás redireccionado a la página de SSO de SAML de tu proveedor de identidad y se te solicitará que selecciones tu cuenta y revises los permisos requeridos. + - Si no tienes acceso de IdP, copia el vínculo de redirección de IdP y compártelo con tu administrador de IdP para continuar habilitando la sincronización de equipo. ![Botón para habilitar el redireccionamiento de la sincronización de equipo](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-disable.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-disable.md new file mode 100644 index 0000000000000..6645335892c5e --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-disable.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** Cuando inhabilitas la sincronización de equipos, cualquier miembro del equipo que se haya asignado al equipo de {% data variables.product.prodname_dotcom %} a través de un grupo de IdP se eliminará del mismo y podría perder acceso a los repositorios. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md new file mode 100644 index 0000000000000..2dc429da1ec75 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -0,0 +1,5 @@ +Para habilitar la sincronización de equipos para Okta, en tu administrador de IdP deberás: + +- Habilitar el SSO de SAML y SCIM para tu organización utilizando Okta. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM utilizando Okta](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)". +- Proporcionar la URL del inquilino para tu instancia de Okta. +- Generar un token de SSWS válido con permisos administrativos de solo lectura para tu instalación de Okta como usuario de servicio. Para obtener más información, consulta la sección [Crear el token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) y [Usuarios de servicio](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) en la documentación de Okta. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-required-permissions.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-required-permissions.md new file mode 100644 index 0000000000000..f05f83f14af56 --- /dev/null +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-required-permissions.md @@ -0,0 +1,6 @@ +Para habilitar la sincronización de equipos con cualquier IdP, debes obtener acceso administrativo con tu IdP o trabajar con tu administrador de IdP para configurar la integración y los grupos de IdP. La persona que configura tus grupos e integración de IdP debe tener alguno de los permisos requeridos. + + | IdP | Permisos requeridos | + | -------- | ------------------------- | + | Azure AD |
  • Administrador global
  • Administrador de Rol Privilegiado
| + | Okta |
  • Usuario de servicio con permisos administrativos de solo lectura
| diff --git a/translations/es-ES/data/reusables/interactions/collaborator-user-limit-definition.md b/translations/es-ES/data/reusables/interactions/collaborator-user-limit-definition.md new file mode 100644 index 0000000000000..79249a889483c --- /dev/null +++ b/translations/es-ES/data/reusables/interactions/collaborator-user-limit-definition.md @@ -0,0 +1 @@ +**Solo para colaboradores:** Cuando limitas las interacciones para `collaborators_only`, se restringirá temporalmente a los usuarios que no sean colaboradores diff --git a/translations/es-ES/data/reusables/interactions/contributor-user-limit-definition.md b/translations/es-ES/data/reusables/interactions/contributor-user-limit-definition.md new file mode 100644 index 0000000000000..b4a4381dba32f --- /dev/null +++ b/translations/es-ES/data/reusables/interactions/contributor-user-limit-definition.md @@ -0,0 +1 @@ +**Solo para contribuyentes:** Cuando limitas las interacciones para `contributors_only`, se restringirá temporalmente a los usuarios que no hayan hecho contribuciones anteriormente y que no sean colaboradores diff --git a/translations/es-ES/data/reusables/interactions/existing-user-limit-definition.md b/translations/es-ES/data/reusables/interactions/existing-user-limit-definition.md new file mode 100644 index 0000000000000..246e1bb53512c --- /dev/null +++ b/translations/es-ES/data/reusables/interactions/existing-user-limit-definition.md @@ -0,0 +1 @@ +**Usuarios existentes:** Cuando limitas las interacciones a `existing_users`, se restringirá temporalmente a los usuarios nuevos con cuentas de menos de 24 horas que no hayan hecho contribuciones anteriormente y que no sean colaboradores diff --git a/translations/es-ES/data/reusables/interactions/interactions-detail.md b/translations/es-ES/data/reusables/interactions/interactions-detail.md new file mode 100644 index 0000000000000..187a3e73074d6 --- /dev/null +++ b/translations/es-ES/data/reusables/interactions/interactions-detail.md @@ -0,0 +1 @@ +When restrictions are enabled, only the specified type of {% data variables.product.product_name %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration. diff --git a/translations/es-ES/data/reusables/issue-events/assignee-properties.md b/translations/es-ES/data/reusables/issue-events/assignee-properties.md new file mode 100644 index 0000000000000..115cad7e72810 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/assignee-properties.md @@ -0,0 +1 @@ +`assignee` | `object` | La persona a la que se desasignó del informe de problemas. `assigner` | `object` | La persona que realizó la desasignación para este informe de problemas. diff --git a/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md new file mode 100644 index 0000000000000..3942f79701976 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md @@ -0,0 +1,10 @@ +| Nombre | Type | Descripción | +| ------------------------ | ----------- | ----------------------------------------------------------------------------------------------------- | +| `id` | `número` | El identificador único del evento. | +| `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | +| `url` | `secuencia` | La URL de la API de REST para recuperar el evento. | +| `actor (actor)` | `object` | La persona que generó el evento. | +| `event` | `secuencia` | Identifica el tipo de evento real que ocurrió. | +| `commit_id` | `secuencia` | EL SHA de la confirmación que referenció este informe de problemas. | +| `commit_url` | `secuencia` | El enlace a la API de REST de GitHub para la confirmación que referenció a este informe de problemas. | +| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo ocurrió el evento. | diff --git a/translations/es-ES/data/reusables/issue-events/label-properties.md b/translations/es-ES/data/reusables/issue-events/label-properties.md new file mode 100644 index 0000000000000..c57a3e141d722 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/label-properties.md @@ -0,0 +1 @@ +`label` | `object` | La etiqueta que se eliminó del informe de problemas `label[name]` | `string` | El nombre de la etiqueta. `label[color]` | `string` | El código de color en hexadecimal. diff --git a/translations/es-ES/data/reusables/issue-events/project-card-properties.md b/translations/es-ES/data/reusables/issue-events/project-card-properties.md new file mode 100644 index 0000000000000..68dc91940d740 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/project-card-properties.md @@ -0,0 +1 @@ +`project_card` | `object` | El objeto de la tarjeta de proyecto. `project_id` | `integer` | El identificador único de la tarjeta de proyecto. `project_url` | `string` | La URL de la API de REST que recuperará la tarjeta de proyecto. `column_name` | `string` | El nombre de la columna en la cual está el informe de problemas. diff --git a/translations/es-ES/data/reusables/issue-events/review-dismissed-properties.md b/translations/es-ES/data/reusables/issue-events/review-dismissed-properties.md new file mode 100644 index 0000000000000..a4a02a36aae07 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/review-dismissed-properties.md @@ -0,0 +1 @@ +`dismissed_review` | `object` | La información de la revisión que se descartó. `dismissed_review[state]` | `string` | El estado en el que se encontraba la solicitud de extracción cuando se descartó. Puede ser uno de entre: `commented`, `approved`, o `changes_requested`. `dismissed_review[review_id]` | `string` | El identificador único de la revisión de la solicitud de extracción. `dismissed_review[dismissal_message]` | `string` | El mensaje que incluyó el usuario cuando descartó la revisión. `dismissed_review[dismissal_commit_id]` | `string` | el Identificador único de la confirmación que descartó la revisión si es que existe. diff --git a/translations/es-ES/data/reusables/issue-events/review-request-properties.md b/translations/es-ES/data/reusables/issue-events/review-request-properties.md new file mode 100644 index 0000000000000..85a675c17d018 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/review-request-properties.md @@ -0,0 +1 @@ +`requested_reviewer` | `object` | La persona a la que se le solicitó revisar la solicitud de extracción. `review_requester` | `object` | La persona que solicitó una revisión. diff --git a/translations/es-ES/data/reusables/issue-events/timeline_events_object_properties.md b/translations/es-ES/data/reusables/issue-events/timeline_events_object_properties.md new file mode 100644 index 0000000000000..7329261ef27a4 --- /dev/null +++ b/translations/es-ES/data/reusables/issue-events/timeline_events_object_properties.md @@ -0,0 +1 @@ +Las propiedades de este evento no utilizan la misma estructura que las [propiedades comunes del objeto del evento para el informe de problemas](#issue-event-object-common-properties). Se devolverán las siguientes propiedades para este evento. diff --git a/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md new file mode 100644 index 0000000000000..b3b2ae85de077 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +Puedes elegir si +{% data variables.large_files.product_name_short %} objects are included in source code archives, such as ZIP files and tarballs, that {% data variables.product.product_name %} creates for your repository. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". +{% endif %} diff --git a/translations/es-ES/data/reusables/large_files/does_not_carry.md b/translations/es-ES/data/reusables/large_files/does_not_carry.md new file mode 100644 index 0000000000000..ff56a4b98992e --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/does_not_carry.md @@ -0,0 +1 @@ +El ancho de banda no utilizado no se puede utilizar de un mes a otro. diff --git a/translations/es-ES/data/reusables/large_files/downgrade_data_packs.md b/translations/es-ES/data/reusables/large_files/downgrade_data_packs.md new file mode 100644 index 0000000000000..24574b76b036c --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/downgrade_data_packs.md @@ -0,0 +1,2 @@ +1. Debajo de "Bajar de categoría el plan de datos", selecciona la cantidad de paquetes de datos a la que quieras bajar. ![Escoge la nueva cantidad de paquetes de datos que quieres](/assets/images/help/large_files/downgrade_number_of_data_packs.png) +2. Para terminar la operación, da clic en **Bajar de categoría el plan de datos**. ![Termina de bajar tu plan de categoría](/assets/images/help/large_files/downgrade_data_plan.png) diff --git a/translations/es-ES/data/reusables/large_files/free-storage-bandwidth-amount.md b/translations/es-ES/data/reusables/large_files/free-storage-bandwidth-amount.md new file mode 100644 index 0000000000000..968fc39ad9c97 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/free-storage-bandwidth-amount.md @@ -0,0 +1 @@ +Cada cuenta que utilice {% data variables.large_files.product_name_long %} recibe {% data variables.large_files.initial_storage_quota %} de almacenamiento gratuito y {% data variables.large_files.initial_bandwidth_quota %} un mes de ancho de banda gratuito. Si las cuotas de ancho de banda y de almacenamiento no son suficientes, puedes decidir comprar una cuota adicional para {% data variables.large_files.product_name_short %}. diff --git a/translations/es-ES/data/reusables/large_files/owner_quota_only.md b/translations/es-ES/data/reusables/large_files/owner_quota_only.md new file mode 100644 index 0000000000000..4eaca49fa3a87 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/owner_quota_only.md @@ -0,0 +1 @@ +El uso de almacenamiento y ancho de banda solo se descuenta de las cuotas de los repositorios de los propietarios. En las bifurcaciones, el uso de almacenamiento y ancho de banda se descuenta de la raíz de la red del repositorio. Cualquiera con acceso de escritura en un repositorio puede subir archivos a {% data variables.large_files.product_name_short %} sin afectar sus cuotas personales de almacenamiento y ancho de banda o sin comprar paquetes de datos. Bifurcar y extraer un repositorio se descuenta de el límite de ancho de banda del repositorio padre. diff --git a/translations/es-ES/data/reusables/large_files/pack_confirm.md b/translations/es-ES/data/reusables/large_files/pack_confirm.md new file mode 100644 index 0000000000000..c14155a076551 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/pack_confirm.md @@ -0,0 +1 @@ +1. Para confirmar las cantidades en tu nuevo paquete de datos mensual, da clic en **Comprar**. ![Botón para comprar más maquetes de datos](/assets/images/help/billing/data-pack-purchase-button.png) diff --git a/translations/es-ES/data/reusables/large_files/pack_selection.md b/translations/es-ES/data/reusables/large_files/pack_selection.md new file mode 100644 index 0000000000000..a5e2cdd6b8268 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/pack_selection.md @@ -0,0 +1 @@ +1. Ingresa la cantidad de paquetes de datos que quieres agregar a tu cuenta. Cada paquete cuesta {% data variables.large_files.pack_monthly_price %}, y proporciona {% data variables.large_files.pack_monthly_bandwidth %} de ancho de banda y {% data variables.large_files.pack_monthly_storage %} de almacenamiento. ![Botón para comprar más maquetes de datos](/assets/images/help/billing/data-pack-quantity-selector.png) diff --git a/translations/es-ES/data/reusables/large_files/rejected_pushes.md b/translations/es-ES/data/reusables/large_files/rejected_pushes.md new file mode 100644 index 0000000000000..4d04d4d367be7 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/rejected_pushes.md @@ -0,0 +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. diff --git a/translations/es-ES/data/reusables/large_files/resolving-upload-failures.md b/translations/es-ES/data/reusables/large_files/resolving-upload-failures.md new file mode 100644 index 0000000000000..f6194b7ee189a --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/resolving-upload-failures.md @@ -0,0 +1 @@ +Si existen archivos de {% data variables.large_files.product_name_short %} referenciados que no se cargaron con éxito, recibiras un mensaje de error. Para obtener más información, consulta la sección "[Resolver fallas de carga de {% data variables.large_files.product_name_long %}](/articles/resolving-git-large-file-storage-upload-failures)". diff --git a/translations/es-ES/data/reusables/large_files/storage_assets_location.md b/translations/es-ES/data/reusables/large_files/storage_assets_location.md new file mode 100644 index 0000000000000..cb76cf1bcf282 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/storage_assets_location.md @@ -0,0 +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`. +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/large_files/use_lfs_tip.md b/translations/es-ES/data/reusables/large_files/use_lfs_tip.md new file mode 100644 index 0000000000000..793474127bfa6 --- /dev/null +++ b/translations/es-ES/data/reusables/large_files/use_lfs_tip.md @@ -0,0 +1,5 @@ +{% tip %} + +**Tip:** Si subes archivos grandes a {% data variables.product.product_location %} frecuentemente, considera utilizar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulta "[Control de versiones de archivos grandes](/articles/versioning-large-files)." + +{% endtip %} diff --git a/translations/es-ES/data/reusables/linux/ensure-docker.md b/translations/es-ES/data/reusables/linux/ensure-docker.md new file mode 100644 index 0000000000000..af323f3fe39a0 --- /dev/null +++ b/translations/es-ES/data/reusables/linux/ensure-docker.md @@ -0,0 +1 @@ +1. [Asegúrate de que Docker se instaló](https://www.docker.com/) localmente. diff --git a/translations/es-ES/data/reusables/marketplace/add-payment-method-org.md b/translations/es-ES/data/reusables/marketplace/add-payment-method-org.md new file mode 100644 index 0000000000000..1dac024356a0e --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/add-payment-method-org.md @@ -0,0 +1,3 @@ +1. Si eliges un plan pago, revisa tu método de pago. + - Para cambiar el método de pago existente en el archivo para tu organización, haz clic en **Edit...(Editar...)**, a continuación completa el formulario para agregar un nuevo método de pago. Después de agregar con éxito un nuevo método de pago, regresarás automáticamente a la página de orden. ![Enlace para agregar un método de pago para tu organización](/assets/images/help/marketplace/marketplace-edit-payment-method-org.png) + - Si no hay un método de pago en el archivo para la organización, haz clic en **Add a Payment Method (Agregar método de pago)**, a continuación completa el formulario para agregar una tarjeta de crédito o una cuenta de PayPal. ![Enlace para agregar un método de pago para tu organización](/assets/images/help/marketplace/marketplace-add-payment-method-org.png) diff --git a/translations/es-ES/data/reusables/marketplace/add-payment-method-personal.md b/translations/es-ES/data/reusables/marketplace/add-payment-method-personal.md new file mode 100644 index 0000000000000..1c6b4a778e57e --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/add-payment-method-personal.md @@ -0,0 +1,3 @@ +1. Si eliges un plan pago, revisa tu método de pago. + - Para cambiar el método de pago existente en el archivo para tu cuenta personal, haz clic en **Edit...(Editar...)**, a continuación completa el formulario para agregar un nuevo método de pago. Después de agregar con éxito un nuevo método de pago, regresarás automáticamente a la página de orden. ![Enlace para agregar un método de pago para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-payment-method-personal.png) + - Si no hay un método de pago en el archivo para tu cuenta personal, haz clic en **Add a Payment Method (Agregar método de pago)**, a continuación completa el formulario para agregar una tarjeta de crédito o una cuenta de PayPal. ![Enlace para agregar un método de pago para tu cuenta personal](/assets/images/help/marketplace/marketplace-add-payment-method-personal.png) diff --git a/translations/es-ES/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/es-ES/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000000..b11b74bbd32bd --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +Si quieres vender una app que pertenece a tu cuenta de usuario, primero necesitarás transferirla a una organización y luego solicitar la verificación de un listado que cree dicha organización. diff --git a/translations/es-ES/data/reusables/marketplace/browse-to-app.md b/translations/es-ES/data/reusables/marketplace/browse-to-app.md new file mode 100644 index 0000000000000..ecf5ea3ed0b5b --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/browse-to-app.md @@ -0,0 +1 @@ +1. Navega hasta la app que deseas instalar y luego haz clic en el nombre de la app. diff --git a/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md new file mode 100644 index 0000000000000..aad15ed791cd2 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable de **Editar** y da clic en **Cancelar plan**. ![Enlace de cancelación en la sección de Compras de Marketplace de tu configuración de facturación para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-ES/data/reusables/marketplace/cancel-app.md b/translations/es-ES/data/reusables/marketplace/cancel-app.md new file mode 100644 index 0000000000000..254a5132c7caa --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/cancel-app.md @@ -0,0 +1 @@ +1. En el cuadro de diálogo, da clic en **OK**. diff --git a/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md new file mode 100644 index 0000000000000..5ff8eeb3fffbb --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md @@ -0,0 +1 @@ +1. Debajo de "Suscripciones", a un costado de la prueba gratuita que quieres cancelar, utiliza el menú desplegable de Editar y da clic en **Cancelar Plan**. diff --git a/translations/es-ES/data/reusables/marketplace/cancellation-clarification.md b/translations/es-ES/data/reusables/marketplace/cancellation-clarification.md new file mode 100644 index 0000000000000..9c414b9e27829 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/cancellation-clarification.md @@ -0,0 +1 @@ +Cuando un cliente cancela una suscripción de {% data variables.product.prodname_marketplace %}, GitHub no desinstala la app automáticamente, así que el cliente puede esperar que las características gratuitas sigan funcionando. diff --git a/translations/es-ES/data/reusables/marketplace/choose-new-plan.md b/translations/es-ES/data/reusables/marketplace/choose-new-plan.md new file mode 100644 index 0000000000000..06d77434cade3 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/choose-new-plan.md @@ -0,0 +1 @@ +1. Debajo de "Editar tu plan", utiliza el menú desplegable y da clic en un nuevo plan. ![Menú desplegable listando todos los planes disponibles de la app](/assets/images/help/marketplace/marketplace-choose-new-plan.png) diff --git a/translations/es-ES/data/reusables/marketplace/choose-new-quantity.md b/translations/es-ES/data/reusables/marketplace/choose-new-quantity.md new file mode 100644 index 0000000000000..f4bb23e5094da --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/choose-new-quantity.md @@ -0,0 +1 @@ +1. Si eliges un plan unitario, teclea una nueva cantidad. ![Campo para ingresar una nueva cantidad para un plan unitario](/assets/images/help/marketplace/marketplace-new-quantity.png) diff --git a/translations/es-ES/data/reusables/marketplace/choose-plan.md b/translations/es-ES/data/reusables/marketplace/choose-plan.md new file mode 100644 index 0000000000000..feb401cec6a76 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/choose-plan.md @@ -0,0 +1 @@ +1. En la página de la aplicación, debajo de "Configuración y precios", da clic en el plan de precios que quieres utilizar. ![Lista de aplicaciones disponibles en los planes de precios](/assets/images/help/marketplace/marketplace-choose-plan.png) diff --git a/translations/es-ES/data/reusables/marketplace/complete-order-begin-installation.md b/translations/es-ES/data/reusables/marketplace/complete-order-begin-installation.md new file mode 100644 index 0000000000000..b435e46e7ff08 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/complete-order-begin-installation.md @@ -0,0 +1 @@ +1. Da clic en "**Completar orden y comenzar instalación**. ![Botón para completar orden y comenzar instalación](/assets/images/help/marketplace/marketplace-complete-order-begin-installation-button.png) diff --git a/translations/es-ES/data/reusables/marketplace/confirm-install-account-org.md b/translations/es-ES/data/reusables/marketplace/confirm-install-account-org.md new file mode 100644 index 0000000000000..06ee7789672e4 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/confirm-install-account-org.md @@ -0,0 +1 @@ +1. Debajo de "Información de Facturación", utiliza el menú desplegable de Cambiar de cuenta de facturación y escoge la organización en la cual quieres instalar la aplicación. ![Menú desplegable para cambiar de cuenta de facturación y el nombre y avatar que escogiste para la organización](/assets/images/help/marketplace/marketplace-confirm-org.png) diff --git a/translations/es-ES/data/reusables/marketplace/confirm-install-account-personal.md b/translations/es-ES/data/reusables/marketplace/confirm-install-account-personal.md new file mode 100644 index 0000000000000..376149eb4e7c6 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/confirm-install-account-personal.md @@ -0,0 +1 @@ +1. Debajo de "Información de Facturación", confirma que estás reinstalando la aplicación para tu cuenta personal. ![Tu nombre, tu avatar, el texto "Cuenta personal" y un menú desplegable para cambiar de cuenta de facturación](/assets/images/help/marketplace/marketplace-confirm-personal-account.png) diff --git a/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md new file mode 100644 index 0000000000000..597ce6e4b0b6e --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md @@ -0,0 +1 @@ +1. Debajo de "Tu suscripción", junto a la aplicación a la cual quieres bajar, utiliza el menú desplegable de Editar y da clic en **Cambiar plan** o **Cancelar plan**. ![Enlace de editar en la sección de Compras de Marketplace para la configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md new file mode 100644 index 0000000000000..e261918072cff --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md @@ -0,0 +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 %}. Si deseas cancelar todas tus suscripciones pagas en {% data variables.product.prodname_dotcom %}, debes bajar de categoría cada suscripción paga por separado. diff --git a/translations/es-ES/data/reusables/marketplace/free-apps-encouraged.md b/translations/es-ES/data/reusables/marketplace/free-apps-encouraged.md new file mode 100644 index 0000000000000..47bb2bc12d529 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/free-apps-encouraged.md @@ -0,0 +1 @@ +Se exhorta a que hayan aplicaciones gratuitas en {% data variables.product.prodname_marketplace %}, y también son una gran forma de ofrecer servicios de código abierto. Si listas una versión de paga de tu app fuera de {% data variables.product.prodname_marketplace %}, deberás ofrecer por lo menos un plan de pago cuando la lsitas en {% data variables.product.prodname_marketplace %}. diff --git a/translations/es-ES/data/reusables/marketplace/free-plan-note.md b/translations/es-ES/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000000..78b7e40b9da80 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Si estás listando una app en {% data variables.product.prodname_marketplace %}, no puedes listarla con un plan de precios gratuito si ofreces un servicio de pago fuera de {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/marketplace/free-trials.md b/translations/es-ES/data/reusables/marketplace/free-trials.md new file mode 100644 index 0000000000000..e4bfe0346643a --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/free-trials.md @@ -0,0 +1 @@ +Si eliges un plan pagado con prueba gratuita, puedes cancelarlo en cualquier momento durante tu periodo de prueba sin que se te cobre, pero perderás acceso a la app automáticamente. Tu suscripción paga comenzará al finalizar la prueba de 14 días. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". diff --git a/translations/es-ES/data/reusables/marketplace/github_apps_preferred.md b/translations/es-ES/data/reusables/marketplace/github_apps_preferred.md new file mode 100644 index 0000000000000..5461bcc41d390 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/github_apps_preferred.md @@ -0,0 +1 @@ +Las GitHub Apps son la forma oficial y recomendada de integrarse con GitHub, ya que ofrecen permisos mucho más granulares para acceder a los datos diff --git a/translations/es-ES/data/reusables/marketplace/install-buy.md b/translations/es-ES/data/reusables/marketplace/install-buy.md new file mode 100644 index 0000000000000..4b01765d4b817 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/install-buy.md @@ -0,0 +1 @@ +1. Da clic en **Instalar gratuitamente**, **Comprar con {% data variables.product.prodname_dotcom %}**, o **Evaluar gratuitamente por 14 días**. ![Botón de comprar con {% data variables.product.prodname_dotcom %}](/assets/images/help/marketplace/marketplace-buy-with-github-button.png) diff --git a/translations/es-ES/data/reusables/marketplace/issue-plan-changes.md b/translations/es-ES/data/reusables/marketplace/issue-plan-changes.md new file mode 100644 index 0000000000000..631433c517a8c --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/issue-plan-changes.md @@ -0,0 +1 @@ +1. Revisa la información de tu nuevo plan e información de facturación, después, da clic en **Emitir cambios de plan**. ![Resumen de tu plan anterior, plan nuevo, e información de facturación, y botón de emitir cambios de plan](/assets/images/help/marketplace/marketplace-issue-plan-changes.png) diff --git a/translations/es-ES/data/reusables/marketplace/launch-with-free.md b/translations/es-ES/data/reusables/marketplace/launch-with-free.md new file mode 100644 index 0000000000000..85d90751fdd53 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/launch-with-free.md @@ -0,0 +1 @@ +Puedes solicitar la publicación con o sin verificación. El solicitar una publicación sin verificación te permite lanzar una versión gratuita de tu app rápidamente. Si posteriormente solicitas la publicación con verificación, tu listado se actualizará e incluirá la insignia de creador verificado y cualquier precio de plan de pago cuando completes la verificación y la incorporación financiera. diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-apps-only.md b/translations/es-ES/data/reusables/marketplace/marketplace-apps-only.md new file mode 100644 index 0000000000000..cc934e2a0f12e --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-apps-only.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Este artículo aplica únicamente para las apps de instalación y compra de {% data variables.product.prodname_marketplace %}. Para obtener más información sobre las apps compradas a un integrador, consulta la sección "[Acerca de las integraciones](/articles/about-integrations)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/es-ES/data/reusables/marketplace/marketplace-billing-ui-requirements.md new file mode 100644 index 0000000000000..b339cee8457f1 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -0,0 +1,9 @@ +- Los clientes que cancelan un plan de pago que se haya comprado en {% data variables.product.prodname_marketplace %} deben degradar su versión automáticamente al plan gratuito de la app en caso de que éste exista. Se recomienda ampliamente la {% data reusables.marketplace.cancellation-clarification %} para permitir a los usuarios el rehabilitar su plan previo. +- Los clientes deben poder mejorar la versión de tu app desde la interface de usuario de la misma si proporcionas una [URL de mejora](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) en este formato: `https://www.github.com/marketplace//upgrade//` +- Los clientes deben poder modificar qué usuarios tienen acceso a tu app desde el sitio web de la misma si compraron plazas (plan de precios por unidad) o si el plan ofrece colaboradores ilimitados. +- Los clientes deben poder ver los siguientes cambios a su cuenta inmediatamente en la sección de facturación, perfil, o configuración de cuenta del sitio web de la app: + - Plan y precios actuales. + - Nuevos planes comprados. + - Mejoras, degradaciones, cancelaciones y la cantidad de días restantes del periodo de prueba gratuito. + - Cambios en los ciclos de facturación (mensual o anual). + - Uso y recursos restantes para los planes por unidad y de tasa fija. Por ejemplo, si el plan de precios es por unidad, el sitio de tu app debería mostrar las unidades que se utilizan y las que quedan disponibles. diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-double-purchases.md b/translations/es-ES/data/reusables/marketplace/marketplace-double-purchases.md new file mode 100644 index 0000000000000..54100607a9d44 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-double-purchases.md @@ -0,0 +1,5 @@ +{% warning %} + +**Nota:** En la versión actual de {% data variables.product.prodname_marketplace %}, es posible que un cliente compre tu app a través de {% data variables.product.prodname_marketplace %} cuando ya tienen una cuenta existente que se haya comprado desde el sitio web de tu app. Si te das cuenta de que ya tienes configurada una cuenta para el cliente que compró tu app, por favor reporta las compras "dobles" a [Soporte de GitHub](https://github.com/contact). + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-failed-purchase-event.md b/translations/es-ES/data/reusables/marketplace/marketplace-failed-purchase-event.md new file mode 100644 index 0000000000000..a4387296c05e5 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-failed-purchase-event.md @@ -0,0 +1 @@ +En caso de que un cliente mejore su plan y el pago falle, GitHub revertirá su suscripción de {% data variables.product.prodname_marketplace %} a su estado previo. GitHub también enviará un correo electrónico al cliente para informarle de dicho fallo y para permitirles volver a intentar la compra. Recibirás un webhook con la acción como `changed`, el cual te solicitará revertir el estado de la app al plan previo. diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-malicious-behavior.md b/translations/es-ES/data/reusables/marketplace/marketplace-malicious-behavior.md new file mode 100644 index 0000000000000..e56ebb9887385 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-malicious-behavior.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Si notas cualquier compra de {% data variables.product.prodname_marketplace %} que genera spam o que presenta cualquier otro comportamiento malicioso, por favor, completa el formato de [reportar abuso](https://github.com/contact/report-abuse) con más información sobre el usuario. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-org-perms.md b/translations/es-ES/data/reusables/marketplace/marketplace-org-perms.md new file mode 100644 index 0000000000000..aec00d27c0ab7 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-org-perms.md @@ -0,0 +1,5 @@ +{% tip %} + + **Tip**: Si una app requiere acceso a nivel organizacional, entonces sólo el propietario de la organización podrá comprarla, instalarla o cancelarla, así como administrar la facturación de la app para dicha organización. Si la app no requiere acceso a nivel organizacional, entonces cualquier administrador de repositorio podrá instalarla y desinstalarla. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/marketplace/marketplace-pricing-free-trials.md b/translations/es-ES/data/reusables/marketplace/marketplace-pricing-free-trials.md new file mode 100644 index 0000000000000..86f56d1553f81 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/marketplace-pricing-free-trials.md @@ -0,0 +1 @@ +Puedes ofrecer tu app gratuitamente por 14 días como un periodo de prueba gratuito. Los periodos de prueba gratuitos se convierten en suscripciones pagadas después de 14 días, a menos de que el cliente las cancele antes de que caduque dicho periodo de prueba gratuito. Selecciona "Habilitar el periodo de prueba gratuito de 14 días para este plan" para ofrecer un periodo de prueba gratuito. diff --git a/translations/es-ES/data/reusables/marketplace/review-app-perms-install.md b/translations/es-ES/data/reusables/marketplace/review-app-perms-install.md new file mode 100644 index 0000000000000..48bedff173365 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/review-app-perms-install.md @@ -0,0 +1 @@ +1. Revisa los permisos de acceso a la app y después da clic en **Instalar**. diff --git a/translations/es-ES/data/reusables/marketplace/select-installation-repos.md b/translations/es-ES/data/reusables/marketplace/select-installation-repos.md new file mode 100644 index 0000000000000..b774e51e6f07e --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/select-installation-repos.md @@ -0,0 +1 @@ +1. Si eliges otorgar acceso a la app para ingresar a repositorios limitados en vez de a todos tus repositorios, teclea el nombre de cada repositorio al cual quieras otorgarle acceso, y posteriormente da clic en el nombre de cada repositorio para seleccionarlo. ![Campo para seleccionar los repositorios a los cuales dejarás ingresar a la app](/assets/images/help/marketplace/marketplace-select-repo-field.png) diff --git a/translations/es-ES/data/reusables/marketplace/unverified-apps.md b/translations/es-ES/data/reusables/marketplace/unverified-apps.md new file mode 100644 index 0000000000000..ad61f1dff95d0 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/unverified-apps.md @@ -0,0 +1 @@ +Las apps sin verificar solo se ofrecen con planes gratuitos. Para listar los planes de pago, debes emitir una app verificada. diff --git a/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md new file mode 100644 index 0000000000000..fdda91148fbb7 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable de **Editar** y da clic en **Cambiar plan**. ![Menú desplegable de editar en la sección de compras de Marketplace para tu configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-ES/data/reusables/marketplace/visit-marketplace.md b/translations/es-ES/data/reusables/marketplace/visit-marketplace.md new file mode 100644 index 0000000000000..1a8b4ffaa6864 --- /dev/null +++ b/translations/es-ES/data/reusables/marketplace/visit-marketplace.md @@ -0,0 +1 @@ +1. En la parte superior de cualquier página, da clic en **Mercado**. ![Enlace de Marketplace en el menú de navegación global en la parte superior de todas las páginas](/assets/images/help/marketplace/marketplace-link-global-navigation.png) diff --git a/translations/es-ES/data/reusables/mobile/about-mobile.md b/translations/es-ES/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/es-ES/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/es-ES/data/reusables/mobile/ghes-release-phase.md b/translations/es-ES/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/es-ES/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md b/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/notifications-v2/custom-notifications-beta.md b/translations/es-ES/data/reusables/notifications-v2/custom-notifications-beta.md new file mode 100644 index 0000000000000..13ab5d9940bdf --- /dev/null +++ b/translations/es-ES/data/reusables/notifications-v2/custom-notifications-beta.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota:** Las notificaciones personalizadas se encuentran actualmente en beta y están sujetas a cambios. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/notifications-v2/email-notification-caveats.md b/translations/es-ES/data/reusables/notifications-v2/email-notification-caveats.md new file mode 100644 index 0000000000000..84a3128586ee9 --- /dev/null +++ b/translations/es-ES/data/reusables/notifications-v2/email-notification-caveats.md @@ -0,0 +1,5 @@ +Solo recibirás correo electrónicos de notificación si optaste por recibir notificaciones por correo electrónico en los ajustes de las notificaciones. + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.user_settings.verify-org-approved-email-domain %} +{% endif %} diff --git a/translations/es-ES/data/reusables/notifications-v2/manage-notifications.md b/translations/es-ES/data/reusables/notifications-v2/manage-notifications.md new file mode 100644 index 0000000000000..ddbd7000e0b2c --- /dev/null +++ b/translations/es-ES/data/reusables/notifications-v2/manage-notifications.md @@ -0,0 +1 @@ +1. En la barra lateral, debajo de la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" para dar clic en **Configuración de notificaciones**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) diff --git a/translations/es-ES/data/reusables/notifications-v2/notifications-inbox-required-setting.md b/translations/es-ES/data/reusables/notifications-v2/notifications-inbox-required-setting.md new file mode 100644 index 0000000000000..0f4bae876300a --- /dev/null +++ b/translations/es-ES/data/reusables/notifications-v2/notifications-inbox-required-setting.md @@ -0,0 +1 @@ +Para utilizar la bandeja de notificaciones en {% data variables.product.prodname_dotcom %} y {% data variables.product.prodname_mobile %}, debes habilitar las notificaciones web y móviles en tu configuración de notificaciones. diff --git a/translations/es-ES/data/reusables/notifications/access_notifications.md b/translations/es-ES/data/reusables/notifications/access_notifications.md new file mode 100644 index 0000000000000..a8d9e597cb34f --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/access_notifications.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, da clic en {% octicon "bell" aria-label="The notifications bell" %}. ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) diff --git a/translations/es-ES/data/reusables/notifications/access_watching.md b/translations/es-ES/data/reusables/notifications/access_watching.md new file mode 100644 index 0000000000000..72e49c0f84e48 --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/access_watching.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, haz clic en {% octicon "bell" aria-label="The notifications bell" %}. Si [inhabilitaste las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) y no ves el icono de campana, puedes navegar a . ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) diff --git a/translations/es-ES/data/reusables/notifications/auto-watch.md b/translations/es-ES/data/reusables/notifications/auto-watch.md new file mode 100644 index 0000000000000..c38428d3a1c59 --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/auto-watch.md @@ -0,0 +1 @@ +Observarás automáticamente a todos los repositorios que crees y que pertenezcan a tu cuenta de usuario. También puedes elegir seguir automáticamente todos los repositorios en los que tienes acceso de escritura, con excepción de sus bifurcaciones. Puedes observar cualquier otro repositorio manualmente. diff --git a/translations/es-ES/data/reusables/notifications/outbound_email_tip.md b/translations/es-ES/data/reusables/notifications/outbound_email_tip.md new file mode 100644 index 0000000000000..a18760fb9146f --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/outbound_email_tip.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +{% note %} + +**Nota** : Solo recibirás notificaciones si habilitas el soporte para correo electrónico externo en {% data variables.product.product_location %}. Para obtener más información, contacta a tu administrador de sitio. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/notifications/saved_for_late_sidebar.md b/translations/es-ES/data/reusables/notifications/saved_for_late_sidebar.md new file mode 100644 index 0000000000000..81155aeecfe0b --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/saved_for_late_sidebar.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, para ver tus notificaciones guardadas, da clic en **Guardado para después**. ![Botón de guardado para después](/assets/images/help/notifications/saved-for-later-tab.png) diff --git a/translations/es-ES/data/reusables/notifications/shared_state.md b/translations/es-ES/data/reusables/notifications/shared_state.md new file mode 100644 index 0000000000000..2c6a72c6c1813 --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/shared_state.md @@ -0,0 +1,5 @@ +{% tip %} + +**Tip:** Si recibes notificaciones tanto por web como por correo electrónico, puedes sincronizar automáticamente el estado de leído o no leído de las mismas para que las notificaciones web se marquen automaticamente como leídas una vez que las leas en tu correo electrónico correspondiente. Para habilitar esta sincronización, tu cliente de correo electrónico debe ser capaz de ver imágenes de {% if currentVersion == "free-pro-team@latest" %}`notifications@github.com`{% else %}la dirección de correo electrónico de `no-reply` {% if currentVersion == "github-ae@latest" %}para tu nombre de host de {% data variables.product.product_name %}{% elsif enterpriseServerVersions contains currentVersion %}para {% data variables.product.product_location %}, el cual configura tu administrador de sitio{% endif %}{% endif %}. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md new file mode 100644 index 0000000000000..d7a164d46811e --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -0,0 +1,3 @@ +Puedes elegir el método de entrega para las notificaciones sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las {% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} en los repositorios que estés observando, así como la frecuencia en las que se te envían éstas. + + diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md new file mode 100644 index 0000000000000..cd123cd86f5fe --- /dev/null +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -0,0 +1,33 @@ +{% if currentVersion == "free-pro-team@latest" %} +By default, you will receive notification of new +{% data variables.product.prodname_dependabot_alerts %}: +- by email, an email is sent every time a vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option) +- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) +- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) +- in your inbox, as web notifications for new vulnerabilities with a critical or high severity (**Web** option) +Puede spersonalizar la forma en que se te notifica sobre + +{% data variables.product.prodname_dependabot_alerts %}. Por ejemplo, puedes recibir un correo electrónico semanal con el resúmen de las alertas de hasta 10 de tus repositorios si utilizas las opciones "**Enviar un resumen de vulnerabilidades por correo electrónico** y **Resumen semanal de seguridad por correo electrónico**. +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para recibir notificaciones en tu instancia, recibirás +{% data variables.product.prodname_dependabot_alerts %}: +- por correo electrónico, se envia un correo electrónico cada vez que se enecuentre una vulnerabilidad {% if currentVersion ver_gt "enterprise-server@2.23" %}con severidad alta o crítica{% endif %} (opción **Enviar un correo electrónico cada que se encuentre una vulnerabilidad**) +- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) +- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) +- en tu bandeja de entrada, como notificaciones web {% if currentVersion ver_gt "enterprise-server@2.23" %}para vulnerabilidades nuevas con severidad alta o crítica {% endif %}(opción **Web**) +Puede spersonalizar la forma en que se te notifica sobre + +{% data variables.product.prodname_dependabot_alerts %}. Por ejemplo, puedes recibir un correo electrónico semanal con el resúmen de las alertas de hasta 10 de tus repositorios si utilizas las opciones "**Enviar un resumen de vulnerabilidades por correo electrónico** y **Resumen semanal de seguridad por correo electrónico**. +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +Predeterminadamente, si tu administrador de sitio configuró las notificaciones por correo electrónico en tu instancia, recibirás alertas de seguridad: +- por correo electrónico, se envía un conrreo electrónico cada que se encuentra una vulnerabilidad (opción de **Enviar un correo electrónico cada que se encuentre una vulnerabilidad**) +- en la interface de usuario, como advertencias en tu archivo de repositorio y vistas de código (opción de **alertas de IU**) +- en la línea de comandos, como advertencias que se muestran como rellamados cuando subes información a los repositorios, la cual tiene vulnerabilidades (opción de **Línea de comandos**) +- en tu bandeja de entrada, como notificaciones web (opción de **Web**) + +Puedes personalizar la forma en la que se te notifica sobre las alertas de seguridad. Por ejemplo, puedes recibir un correo electrónico semanal con el resúmen de las alertas de hasta 10 de tus repositorios si utilizas las opciones "**Enviar un resumen de vulnerabilidades por correo electrónico** y **Resumen semanal de seguridad por correo electrónico**. +{% endif %} diff --git a/translations/es-ES/data/reusables/open-source/open-source-guide-general.md b/translations/es-ES/data/reusables/open-source/open-source-guide-general.md new file mode 100644 index 0000000000000..509030003d073 --- /dev/null +++ b/translations/es-ES/data/reusables/open-source/open-source-guide-general.md @@ -0,0 +1 @@ +Para obtener más información sobre el código abierto, específicamente sobre como crear y hacer crecer un proyecto de código abierto, hemos creado unas [Guías de Código Abierto](https://opensource.guide/) que te ayudarán a fomentar una comunidad saludable. diff --git a/translations/es-ES/data/reusables/open-source/open-source-guide-repositories.md b/translations/es-ES/data/reusables/open-source/open-source-guide-repositories.md new file mode 100644 index 0000000000000..b4e37a8ac1263 --- /dev/null +++ b/translations/es-ES/data/reusables/open-source/open-source-guide-repositories.md @@ -0,0 +1 @@ +Para obtener más información acerca del código abierto, específicamente sobre cómo crear y hacer crecer un proyecto de código abierto, hemos creado las [Guías de Código Abierto](https://opensource.guide/) que te ayudarán fomentar una comunidad saludable mediante la recomendación de mejores prácticas para crear y mantener repositorios para tus proyectos de código abierto. diff --git a/translations/es-ES/data/reusables/open-source/open-source-learning-lab.md b/translations/es-ES/data/reusables/open-source/open-source-learning-lab.md new file mode 100644 index 0000000000000..25abe4991c65c --- /dev/null +++ b/translations/es-ES/data/reusables/open-source/open-source-learning-lab.md @@ -0,0 +1 @@ +También puedes tomar un curso gratuito de [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) sobre cómo mantener comunidades de código abierto. diff --git a/translations/es-ES/data/reusables/organizations/add-dns-txt-record.md b/translations/es-ES/data/reusables/organizations/add-dns-txt-record.md new file mode 100644 index 0000000000000..454adcf5579bb --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/add-dns-txt-record.md @@ -0,0 +1 @@ +1. Sigue las instrucciones dentro de **Add a DNS TXT record (Agregar un registro TXT de DNS)** para crear un registro TXT de DNS con tu servicio de alojamiento de dominio. ![Instrucciones para crear un registro txt de DNS](/assets/images/help/organizations/create-dns-txt-record-instructions.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/add-domain.md b/translations/es-ES/data/reusables/organizations/add-domain.md new file mode 100644 index 0000000000000..494299a7efc26 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/add-domain.md @@ -0,0 +1 @@ +1. En el campo dominio, escribe el dominio que deseas verificar, después haz clic en **Add domain (Agregar dominio)**. ![Campo para agregar un dominio](/assets/images/help/organizations/add-domain-field.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/add-extension-to-cert.md b/translations/es-ES/data/reusables/organizations/add-extension-to-cert.md new file mode 100644 index 0000000000000..3902608f0f4fd --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/add-extension-to-cert.md @@ -0,0 +1 @@ +Cuando emites cada uno de los certificados de cliente, debes incluir una extensión que especifique para cuál usuario de {% data variables.product.product_name %} es cada uno de ellos. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)". diff --git a/translations/es-ES/data/reusables/organizations/add-user-to-teams.md b/translations/es-ES/data/reusables/organizations/add-user-to-teams.md new file mode 100644 index 0000000000000..406d39193253f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/add-user-to-teams.md @@ -0,0 +1 @@ +1. Opcionalmente, agrega el usuario o equipos a la organización. ![Lista de los equipos de la organización](/assets/images/help/organizations/add-user-to-teams.png) diff --git a/translations/es-ES/data/reusables/organizations/app-managers-settings-sidebar.md b/translations/es-ES/data/reusables/organizations/app-managers-settings-sidebar.md new file mode 100644 index 0000000000000..3aa28b639921c --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/app-managers-settings-sidebar.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Administradores de la App**. ![Botón de administradores de la app en la barra lateral](/assets/images/help/organizations/app-managers-sidebar-button.png) diff --git a/translations/es-ES/data/reusables/organizations/billing.md b/translations/es-ES/data/reusables/organizations/billing.md new file mode 100644 index 0000000000000..38b46164e23b4 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/billing.md @@ -0,0 +1 @@ +1. En la barra lateral de Configuración de tu organización, da clic en **Facturación**. ![Configuración de facturación](/assets/images/help/billing/settings_organization_billing_tab.png) diff --git a/translations/es-ES/data/reusables/organizations/block_users.md b/translations/es-ES/data/reusables/organizations/block_users.md new file mode 100644 index 0000000000000..94fa39e3022ac --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/block_users.md @@ -0,0 +1 @@ +1. En la barra lateral de Configuración de tu organización, da clic en **Usuarios bloqueados**. ![Usuarios bloqueados en la configuración de la organización](/assets/images/help/organizations/org-settings-block-users.png) diff --git a/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md b/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md new file mode 100644 index 0000000000000..1ed5f3afb99ac --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md @@ -0,0 +1 @@ +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/es-ES/data/reusables/organizations/cancel_org_invite.md b/translations/es-ES/data/reusables/organizations/cancel_org_invite.md new file mode 100644 index 0000000000000..fa0893709ab33 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/cancel_org_invite.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Puedes [editar o cancelar una invitación](/articles/canceling-or-editing-an-invitation-to-join-your-organization) en cualquier momento después de que el usuario la acepte. +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/child-team-inherits-permissions.md b/translations/es-ES/data/reusables/organizations/child-team-inherits-permissions.md new file mode 100644 index 0000000000000..e2fb2896f3ae8 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/child-team-inherits-permissions.md @@ -0,0 +1 @@ +Los equipos hijo heredan los permisos de acceso del equipo padre. Para obtener más información sobre las jerarquías de equipos, consulta la sección "[Acerca de los equipos](/articles/about-teams#nested-teams)". diff --git a/translations/es-ES/data/reusables/organizations/choose-to-restore-privileges.md b/translations/es-ES/data/reusables/organizations/choose-to-restore-privileges.md new file mode 100644 index 0000000000000..db7d6fa1230f1 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/choose-to-restore-privileges.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %}1. Si la persona que estás invitando era miembro de una organización en los tres meses pasados, escoge si quieres restaurar sus privilegios o comenzar desde cero, después, da clic en **Invitar y reinstaurar** o en **Invitar y comenzar desde cero**. + ![Decide si quieres restaurar los privilegios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png){% else %} +1. Si la persona que estás agregando era miembro de una organización en los tres meses pasados, escoge si quieres restaurar sus privilegios o comenzar desde cero, después, da clic en **Agregar y reinstaurar** o en **Agregar y comenzar desde cero**. ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/choose-user-license.md b/translations/es-ES/data/reusables/organizations/choose-user-license.md new file mode 100644 index 0000000000000..452ccd6044b29 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/choose-user-license.md @@ -0,0 +1 @@ +1. Si tu organización pertenece a una cuenta empresarial con más de una licencia, escoge la licencia para el usuario. ![Opciones de licencia](/assets/images/help/organizations/choose-user-license.png) diff --git a/translations/es-ES/data/reusables/organizations/choose-user-role-send-invitation.md b/translations/es-ES/data/reusables/organizations/choose-user-role-send-invitation.md new file mode 100644 index 0000000000000..e25c8b7b2f9ed --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/choose-user-role-send-invitation.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %}1. Si la persona que estás invitando nunca fue miembro de la organización o si eliminaste sus privilegios, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Send invitation** (Enviar invitación). + ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png){% else %} +1. Si la persona que estás invitando nunca fue miembro de la organización o si eliminaste sus privilegios, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png){% else %} +1. Elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member-2.7-lower.png){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/choose-user-role.md b/translations/es-ES/data/reusables/organizations/choose-user-role.md new file mode 100644 index 0000000000000..7027fd17bf3bd --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/choose-user-role.md @@ -0,0 +1 @@ +1. Si la persona que estás invitando jamás ha sido un miembro de alguna organización o si le quitaste sus privilegios, escoge un rol para el usuario. ![Opciones para convertir a un usuario en miembro o propietario](/assets/images/help/organizations/choose-new-member-role.png) diff --git a/translations/es-ES/data/reusables/organizations/click-codespaces.md b/translations/es-ES/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md b/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md new file mode 100644 index 0000000000000..b627b7b8e44f6 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md @@ -0,0 +1,2 @@ +9. A la derecha del dominio pendiente de verificar, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Seguir verificando**. ![Botón para continuar verificando](/assets/images/help/organizations/continue-verifying-domain.png) +10. Haz clic en **Verify domain (Verificar dominio)**. ![Botón para verificar dominio](/assets/images/help/organizations/verify-domain-final-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/convert-owners-team-confirm.md b/translations/es-ES/data/reusables/organizations/convert-owners-team-confirm.md new file mode 100644 index 0000000000000..ad8afc2de3846 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/convert-owners-team-confirm.md @@ -0,0 +1 @@ +1. Debajo de la descripción del nuevo rol de propietario, da clic en **Ok, entendido**. ![Descripción de los roles de los nuevos propietarios con botón resaltado de "Ok, entendido"](/assets/images/help/teams/okay-got-it.png) diff --git a/translations/es-ES/data/reusables/organizations/create-team-choose-parent.md b/translations/es-ES/data/reusables/organizations/create-team-choose-parent.md new file mode 100644 index 0000000000000..ab8b84fae640a --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/create-team-choose-parent.md @@ -0,0 +1 @@ +6. Opcionalmente, Si estás creando un [equipo hijo](/articles/about-teams#nested-teams), utiliza el menú desplegable para escoger un equipo padre para tu nuevo equipo. ![Menú desplegable listando los equipos existentes de la organización](/assets/images/help/teams/choose-parent-team.png) diff --git a/translations/es-ES/data/reusables/organizations/create_team.md b/translations/es-ES/data/reusables/organizations/create_team.md new file mode 100644 index 0000000000000..6d23917e80646 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/create_team.md @@ -0,0 +1 @@ +1. Da clic en **Crear equipo**. diff --git a/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md new file mode 100644 index 0000000000000..2921877ac6cc2 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Cuando eliminas un usuario de la organización, sus datos de membresía se guardan durante tres meses. Si en el transcurso de ese tiempo invitas al usuario a que se vuelva a unir a la organización, puedes restaurar sus datos o cualquier bifurcación privada de tus repositorios de la organización que le haya pertenecido. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/organizations/delete-ssh-ca.md b/translations/es-ES/data/reusables/organizations/delete-ssh-ca.md new file mode 100644 index 0000000000000..de4d979dbc140 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/delete-ssh-ca.md @@ -0,0 +1,2 @@ +1. Debajo de "Autoridades de Certificados SSH", a la derecha la autoridad que quieras borrar, da clic en **Borrar**. ![Botón de borrar](/assets/images/help/organizations/ca-delete-button.png) +2. Lee la advertencia y después da clic en **Entiendo, por favor borra esta Autoridad**. ![Botón de confirmación de borrado](/assets/images/help/organizations/ca-delete-confirmation.png) diff --git a/translations/es-ES/data/reusables/organizations/deleted-repos.md b/translations/es-ES/data/reusables/organizations/deleted-repos.md new file mode 100644 index 0000000000000..cbf585528875d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/deleted-repos.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Repositorios borrados**. ![Pestaña de repositorios borrados](/assets/images/help/organizations/deleted-repos.png) diff --git a/translations/es-ES/data/reusables/organizations/disable_project_board_results.md b/translations/es-ES/data/reusables/organizations/disable_project_board_results.md new file mode 100644 index 0000000000000..4948a92f59b02 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/disable_project_board_results.md @@ -0,0 +1 @@ +Si decides habilitar nuevamente tableros de proyecto, todos los tableros de proyecto que se agregaron con anterioridad se encontrarán disponibles. diff --git a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md new file mode 100644 index 0000000000000..974ce5c5d7e43 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_app %}s**. ![Configuración de {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-apps-settings-sidebar.png) diff --git a/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md b/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md new file mode 100644 index 0000000000000..5edc88ab43994 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:** Los repositorios internos se encuentran disponibles para las organizaciones que pertenecen a una cuenta empresarial. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/invite-teams-or-people.md b/translations/es-ES/data/reusables/organizations/invite-teams-or-people.md new file mode 100644 index 0000000000000..d618fa6d1632f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/invite-teams-or-people.md @@ -0,0 +1 @@ +1. A la derecha de "Administrar acceso", da clic en **Invitar equipos o personas**. ![botón de "Invitar equipos o personas"](/assets/images/help/repository/manage-access-invite-button.png) diff --git a/translations/es-ES/data/reusables/organizations/invite_member_from_people_tab.md b/translations/es-ES/data/reusables/organizations/invite_member_from_people_tab.md new file mode 100644 index 0000000000000..7632d1b1ac513 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/invite_member_from_people_tab.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %}1. En la pestaña de Personas, da clic en **Invitar miembro**. + ![Botón de invitar miembro](/assets/images/help/organizations/people-tab-invite-member.png){% else %} +1. En la pestaña de Personas, da clic en **Agregar miembro**. ![Add member button](/assets/images/help/organizations/people-tab-invite-member-ghe.png){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/invite_to_org.md b/translations/es-ES/data/reusables/organizations/invite_to_org.md new file mode 100644 index 0000000000000..31590c86b1de6 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/invite_to_org.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %}1. Teclea el nombre de usuario, nombre completo, o dirección de correo electrónico de la persona que quieres invitar y da clic en **Invitar**. + ![Formato para invitar miembro](/assets/images/help/organizations/org-invite-modal.png){% else %} +1. Teclea el nombre de usuario, nombre completo, o dirección de correo electrónico de la persona que quieres agregar y da clic en **Invitar**. ![Invite member form](/assets/images/help/organizations/org-invite-modal-ghe.png){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/invite_to_team.md b/translations/es-ES/data/reusables/organizations/invite_to_team.md new file mode 100644 index 0000000000000..a994f1b321015 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/invite_to_team.md @@ -0,0 +1,6 @@ +{% if currentVersion == "free-pro-team@latest" %} +1. Agrega un miembro de la organización al equipo o invita a una persona que no sea miembro a unirse a un equipo: + - Si la persona que quieres agregar ya es miembro de la organización, escribe su nombre de usuario y haz clic en **Enter** (Intro). El usuario se agregará de inmediato al equipo. + - Si la persona que quieres agregar no es miembro de la organización, escribe su nombre de usuario o dirección de correo electrónico y haz clic en **Enter** (Intro). El usuario recibirá una invitación por correo electrónico para unirse a tu organización y se agregará al equipo una vez que la acepte.{% else %} +1. Escribe el nombre de usuario de la persona que quieres agregar y haz clic en **Enter** (Intro). El usuario se agregará de inmediato al equipo. ![Mensaje emergente de agregar miembro de equipo](/assets/images/help/organizations/Organization-add-team.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/member-privileges.md b/translations/es-ES/data/reusables/organizations/member-privileges.md new file mode 100644 index 0000000000000..a3bf89423ac17 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/member-privileges.md @@ -0,0 +1 @@ +4. En la barra lateral izquierda, da clic en **Privilegios de los miembros**. ![Opción de privilegios de los miembros en la configuración de la organización](/assets/images/help/organizations/org-settings-member-privileges.png) diff --git a/translations/es-ES/data/reusables/organizations/navigate-to-org.md b/translations/es-ES/data/reusables/organizations/navigate-to-org.md new file mode 100644 index 0000000000000..687b62102e4ab --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/navigate-to-org.md @@ -0,0 +1 @@ +1. En {% data variables.product.product_name %}, navega hasta la página principal de la organización. diff --git a/translations/es-ES/data/reusables/organizations/new-org-permissions-more-info.md b/translations/es-ES/data/reusables/organizations/new-org-permissions-more-info.md new file mode 100644 index 0000000000000..5b5ed46401859 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/new-org-permissions-more-info.md @@ -0,0 +1 @@ +Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". diff --git a/translations/es-ES/data/reusables/organizations/new-organization.md b/translations/es-ES/data/reusables/organizations/new-organization.md new file mode 100644 index 0000000000000..15f8d14758119 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/new-organization.md @@ -0,0 +1 @@ +1. En la sección "Organizaciones", haz clic en **New organization** (Nueva organización). ![Botón para crear una organización nueva](/assets/images/help/settings/new-org-button.png) diff --git a/translations/es-ES/data/reusables/organizations/new-repo-permissions-more-info.md b/translations/es-ES/data/reusables/organizations/new-repo-permissions-more-info.md new file mode 100644 index 0000000000000..dd351e85a706e --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/new-repo-permissions-more-info.md @@ -0,0 +1 @@ +Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". diff --git a/translations/es-ES/data/reusables/organizations/new-ssh-ca.md b/translations/es-ES/data/reusables/organizations/new-ssh-ca.md new file mode 100644 index 0000000000000..da74aca9dc30a --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/new-ssh-ca.md @@ -0,0 +1,3 @@ +1. A la derecha de "Autoridades de Certificados SSH", da clic en **Nueva Autoridad**. ![Botón de nueva autoridad](/assets/images/help/organizations/new-ca-button.png) +2. Debajo de "Llave", pega tu llave SSH pública. ![Campo de llave para agregar autoridad](/assets/images/help/organizations/ca-key-field.png) +3. Da clic en **Agregar Autoridad**. diff --git a/translations/es-ES/data/reusables/organizations/new_team.md b/translations/es-ES/data/reusables/organizations/new_team.md new file mode 100644 index 0000000000000..e26fa5717df8f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/new_team.md @@ -0,0 +1,2 @@ +1. Debajo del nombre de tu organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) +1. Al lado derecho de la pestaña de Equipos, da clic en **Equipo nuevo**. ![Botón de equipo nuevo](/assets/images/help/teams/new-team-button.png) diff --git a/translations/es-ES/data/reusables/organizations/oauth_app_access.md b/translations/es-ES/data/reusables/organizations/oauth_app_access.md new file mode 100644 index 0000000000000..64521be41fcf1 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/oauth_app_access.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} + 1. En la barra lateral de configuración, da clic en **Acceso de terceros**. ![pestaña de acceso de {% data variables.product.prodname_oauth_app %} en la barra lateral izquierda](/assets/images/help/settings/settings-sidebar-third-party-access.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/oauth_app_restrictions_default.md b/translations/es-ES/data/reusables/organizations/oauth_app_restrictions_default.md new file mode 100644 index 0000000000000..8f395d6191a1f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/oauth_app_restrictions_default.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}Cuando creas una organización nueva, las restricciones de acceso de las {% data variables.product.prodname_oauth_app %}s se habilitan predeterminadamente. Los propietarios de las organizaciones pueden [inhabilitar las restricciones de acceso de {% data variables.product.prodname_oauth_app %}](/articles/disabling-oauth-app-access-restrictions-for-your-organization) en cualquier momento.{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/org-invite-expiration.md b/translations/es-ES/data/reusables/organizations/org-invite-expiration.md new file mode 100644 index 0000000000000..3dac78e542952 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/org-invite-expiration.md @@ -0,0 +1 @@ +Las invitaciones pendientes caducarán después de 7 días. Esto restablecerá cualquier licencia sin reclamar. diff --git a/translations/es-ES/data/reusables/organizations/org-ownership-recommendation.md b/translations/es-ES/data/reusables/organizations/org-ownership-recommendation.md new file mode 100644 index 0000000000000..98b0a8844ca93 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/org-ownership-recommendation.md @@ -0,0 +1 @@ +Los proyectos mantenidos y admnistrados por un solo propietario de organización pueden llegar a ser inaccesibles con facilidad si no se puede contactar a dicho propietario. Te recomendamos que tu organización tenga por lo menos dos personas con permisos de *propietario* para garantizar que nadie tendrá acceso al proyecto. diff --git a/translations/es-ES/data/reusables/organizations/org_settings.md b/translations/es-ES/data/reusables/organizations/org_settings.md new file mode 100644 index 0000000000000..ebbbd1cc29b29 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/org_settings.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de organización, da clic en {% octicon "gear" aria-label="The Settings gear" %}**Configuración**. ![Botón de configuración de organización](/assets/images/help/organizations/organization-settings-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/organization-name.md b/translations/es-ES/data/reusables/organizations/organization-name.md new file mode 100644 index 0000000000000..0c9654fcbd652 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/organization-name.md @@ -0,0 +1 @@ +1. Debajo de "Nombre de cuenta organizacional", teclea un nombre para tu cuenta de organización. ![Campo para teclear el nombre de organización](/assets/images/help/organizations/new-org-name.png) diff --git a/translations/es-ES/data/reusables/organizations/organization-wide-project.md b/translations/es-ES/data/reusables/organizations/organization-wide-project.md new file mode 100644 index 0000000000000..c5c2097d33ccb --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/organization-wide-project.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de organización, da clic en {% octicon "project" aria-label="The Projects icon" %}**Proyectos**. ![Pestaña de proyectos para tu organización](/assets/images/help/organizations/organization-projects-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/organizations_include.md b/translations/es-ES/data/reusables/organizations/organizations_include.md new file mode 100644 index 0000000000000..d82cab580e890 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/organizations_include.md @@ -0,0 +1,8 @@ +Las organizaciones incluyen: +{% if currentVersion == "free-pro-team@latest" %}- Una opción gratuita, {% data variables.product.prodname_free_team %}, con colaboradores ilimitados en repositorios públicos ilimitados con todas las características y en repositorios privados ilimitados con características limitadas. +- La opción para mejorar a {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %} para obtener características adicionales, incluyendo administración y autenticación sofisticada para los usuarios, y opciones de soporte escaladas. {% data reusables.gated-features.more-info %}{% endif %} +- Membresía ilimitada con una variedad de roles que permiten [diferentes niveles de acceso a la organización y sus datos](/articles/permission-levels-for-an-organization) +- La capacidad de otorgarles a los miembros [un rango de permisos de acceso a los repositorios de la organización](/articles/repository-permission-levels-for-an-organization) +- [Los elementos anidados que reflejan la estructura de tu grupo o compañía](/articles/about-teams) con permisos de acceso y menciones en cascada{% if currentVersion != "github-ae@latest" %} +- La posibilidad de que los propietarios de la organización vean el [estado de autenticación de dos factores(2FA)](/articles/about-two-factor-authentication) de los miembros +- La opción de [requerir que todos los miembros de la organización utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/outside-collaborators-use-seats.md b/translations/es-ES/data/reusables/organizations/outside-collaborators-use-seats.md new file mode 100644 index 0000000000000..b4d85f7e9ff6a --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/outside-collaborators-use-seats.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}El agregar a un colaborador externo en un repositorio privado utilizará una de las licencias pagadas de tu organización. Para obtener más información, consulta "[Acerca del precio por usuario](/articles/about-per-user-pricing/)."{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/outside_collaborator_forks.md b/translations/es-ES/data/reusables/organizations/outside_collaborator_forks.md new file mode 100644 index 0000000000000..1065f0f5b33f9 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/outside_collaborator_forks.md @@ -0,0 +1 @@ +Cuando agregas un colaborador externo a un repositorio, también es necesario que lo agregues en cualquier bifurcación del repositorio al que le quieras dar acceso. diff --git a/translations/es-ES/data/reusables/organizations/outside_collaborators_description.md b/translations/es-ES/data/reusables/organizations/outside_collaborators_description.md new file mode 100644 index 0000000000000..24d0032a0fbd1 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/outside_collaborators_description.md @@ -0,0 +1,5 @@ +Un colaborador externo es una persona que tiene acceso a uno o más repositorios de la organización, pero no es explícitamente miembro de la organización, como ser, un consultor o empleado transitorio. Para obtener más información, consulta: + +- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/data/reusables/organizations/owners-and-admins-can.md b/translations/es-ES/data/reusables/organizations/owners-and-admins-can.md new file mode 100644 index 0000000000000..5f1b72ab3822c --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/owners-and-admins-can.md @@ -0,0 +1 @@ +Solo los miembros con privilegios de propietario de una organización o privilegios de administrador de un repositorio pueden diff --git a/translations/es-ES/data/reusables/organizations/owners-team.md b/translations/es-ES/data/reusables/organizations/owners-team.md new file mode 100644 index 0000000000000..bd7c6354ccb75 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/owners-team.md @@ -0,0 +1,2 @@ +1. Debajo del nombre de tu organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) +1. En la pestaña de Equipos, da clic en **Propietarios**. ![Equipo del propietario seleccionado](/assets/images/help/teams/owners-team.png) diff --git a/translations/es-ES/data/reusables/organizations/people.md b/translations/es-ES/data/reusables/organizations/people.md new file mode 100644 index 0000000000000..e8e2513452585 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/people.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de organización, da clic en {% octicon "organization" aria-label="The People icon" %}**Personas**. ![Pestaña de las Personas](/assets/images/help/organizations/organization-people-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/people_tab_outside_collaborators.md b/translations/es-ES/data/reusables/organizations/people_tab_outside_collaborators.md new file mode 100644 index 0000000000000..36d51ab95b427 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/people_tab_outside_collaborators.md @@ -0,0 +1 @@ +4. Debajo de la pestaña "Personas", da clic en **Colaboradores externos**. ![Botón para seleccionar los colaboradores externos para una organización](/assets/images/help/organizations/select-outside-collaborators.png) diff --git a/translations/es-ES/data/reusables/organizations/reinstate-user-type-username.md b/translations/es-ES/data/reusables/organizations/reinstate-user-type-username.md new file mode 100644 index 0000000000000..a6b7f6ce704f6 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/reinstate-user-type-username.md @@ -0,0 +1 @@ +1. Teclea el nombre de usuario de la persona que quieres reinstaurar y da clic en **Invitar**. diff --git a/translations/es-ES/data/reusables/organizations/removed_outside_collaborators.md b/translations/es-ES/data/reusables/organizations/removed_outside_collaborators.md new file mode 100644 index 0000000000000..6a6d99c85cf8f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/removed_outside_collaborators.md @@ -0,0 +1 @@ +1. Si se te solicita, lee la información acerca de los miembros y colaboradores externos que se eliminarán de la organización. Teclea el nombre de tu organización para confirmar el cambio y posteriormente da clic en **Eliminar miembros & requerir autenticación de dos factores**. ![Cuadro Confirmar aplicación obligatoria de dos factores](/assets/images/help/organizations/confirm-require-2fa.png) diff --git a/translations/es-ES/data/reusables/organizations/repo-creation-constants.md b/translations/es-ES/data/reusables/organizations/repo-creation-constants.md new file mode 100644 index 0000000000000..72dc1926cdd25 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/repo-creation-constants.md @@ -0,0 +1 @@ +Los propietarios de las organizaciones siempre podrán crear cualquier tipo de repositorio, y los colaboradores externos jamás podrán crear algún tipo de repositorio. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". diff --git a/translations/es-ES/data/reusables/organizations/repository-defaults.md b/translations/es-ES/data/reusables/organizations/repository-defaults.md new file mode 100644 index 0000000000000..c29be7f2c6c93 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/repository-defaults.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda da clic en **Predeterminados del repositorio**. ![Pestaña de predeterminados del repositorio](/assets/images/help/organizations/repo-defaults-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/repository-labels.md b/translations/es-ES/data/reusables/organizations/repository-labels.md new file mode 100644 index 0000000000000..13945cde16ebc --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/repository-labels.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Etiquetas de repositorio**. ![Pestaña de etiquetas de repositorio](/assets/images/help/organizations/repo-labels-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/require-ssh-cert.md b/translations/es-ES/data/reusables/organizations/require-ssh-cert.md new file mode 100644 index 0000000000000..2fcf3beb6df07 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/require-ssh-cert.md @@ -0,0 +1 @@ +1. Opcionalmente, para requerir que los miembros utilicen certificados SSH, selecciona **Requerir Certificados SSH** y después da clic en **Guardar**. ![Casilla de Requerir Certificado SSH y botón de guardar](/assets/images/help/organizations/require-ssh-cert.png) diff --git a/translations/es-ES/data/reusables/organizations/require_two_factor_authentication.md b/translations/es-ES/data/reusables/organizations/require_two_factor_authentication.md new file mode 100644 index 0000000000000..19c5b74bc365b --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/require_two_factor_authentication.md @@ -0,0 +1 @@ +1. Debajo de "Autenticación", selecciona **Requerir autenticación de dos factores para todos en tu organización**, y después da clic en **Guardar**. ![Casilla de Requerir autenticación bifactorial](/assets/images/help/organizations/require-2fa-checkbox.png) diff --git a/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md new file mode 100644 index 0000000000000..70a6fe26d9e5f --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -0,0 +1 @@ +Si no eres un gerente de facturación para la organización, pide a tu cliente que solicite a un *propietario* de la misma[añadirte a la organización como gerente de facturación](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md b/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md new file mode 100644 index 0000000000000..6fd4fd5f43c4e --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md @@ -0,0 +1 @@ +1. En "Enforcement preferences" (Preferencias de aplicación), selecciona **Restrict email notifications to domain email** (Restringir las notificaciones por correo electrónico para el correo electrónico del dominio). ![Casilla para restringir las notificaciones por correo electrónico para los correos electrónicos de dominio verificado](/assets/images/help/organizations/restrict-email-notifications-to-domain.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/review-team-repository-access.md b/translations/es-ES/data/reusables/organizations/review-team-repository-access.md new file mode 100644 index 0000000000000..e714becacaa84 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/review-team-repository-access.md @@ -0,0 +1 @@ +1. Revisa la lista de repositorios a la cual tendrá acceso el nuevo miembro del equipo, posteriormente, da clic en **Agregar _NOMBRE DE USUARIO_ a _NOMBRE DE EQUIPO_**. ![Cuadro modal con listado de repositorios a los que tendrá acceso el nuevo miembro del equipo y botón de confirmación](/assets/images/help/teams/add-team-member-repo-perms.png) diff --git a/translations/es-ES/data/reusables/organizations/security-and-analysis.md b/translations/es-ES/data/reusables/organizations/security-and-analysis.md new file mode 100644 index 0000000000000..5dbd561dc23f4 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/security-and-analysis.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Pestaña de "Seguridad & análisis"](/assets/images/help/organizations/org-settings-security-and-analysis.png) diff --git a/translations/es-ES/data/reusables/organizations/security.md b/translations/es-ES/data/reusables/organizations/security.md new file mode 100644 index 0000000000000..48156bc5fa3be --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/security.md @@ -0,0 +1,5 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +1. En la barra lateral izquierda, da clic en **Seguridad de la organización**. ![Configuración de seguridad de la organización](/assets/images/help/organizations/org-security-settings-tab.png) +{% else %} +1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). ![Configuración de seguridad de la organización](/assets/images/help/organizations/org-settings-security-tab.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/send-invitation.md b/translations/es-ES/data/reusables/organizations/send-invitation.md new file mode 100644 index 0000000000000..b5c51db484b9d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/send-invitation.md @@ -0,0 +1 @@ +1. Da clic en {% if currentVersion == "free-pro-team@latest" %}**Enviar invitación**{% else %}**Agregar miembro**{% endif %}. diff --git a/translations/es-ES/data/reusables/organizations/settings-sidebar-actions.md b/translations/es-ES/data/reusables/organizations/settings-sidebar-actions.md new file mode 100644 index 0000000000000..1a8897c829128 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/settings-sidebar-actions.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Acciones**. ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) diff --git a/translations/es-ES/data/reusables/organizations/specific_team.md b/translations/es-ES/data/reusables/organizations/specific_team.md new file mode 100644 index 0000000000000..1294d20c44e64 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/specific_team.md @@ -0,0 +1,2 @@ +1. Debajo del nombre de tu organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) +1. En la pestaña de Equipos, da clic en el nombre del equipo. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) diff --git a/translations/es-ES/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/es-ES/data/reusables/organizations/team-discussions-are-for-orgs.md new file mode 100644 index 0000000000000..98255c8e60e71 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -0,0 +1 @@ +Los debates de equipo solo se encuentran disponibles en las páginas de los equipos en las organizaciones. Para obtener más información, consulta [Acerca de los debates del equipo](/articles/about-team-discussions)". diff --git a/translations/es-ES/data/reusables/organizations/team-discussions-default.md b/translations/es-ES/data/reusables/organizations/team-discussions-default.md new file mode 100644 index 0000000000000..ac9dab5426f26 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-discussions-default.md @@ -0,0 +1 @@ +Los debates del equipo se encuentran disponibles en las organizaciones por defecto. diff --git a/translations/es-ES/data/reusables/organizations/team-discussions-permissions.md b/translations/es-ES/data/reusables/organizations/team-discussions-permissions.md new file mode 100644 index 0000000000000..2999e1f4f0bed --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-discussions-permissions.md @@ -0,0 +1 @@ +Solo los miembros del equipo y propietarios de la organización pueden ver las publicaciones *Privadas*, y todos los miembros de la organización pueden ver las publicaciones *públicas*. diff --git a/translations/es-ES/data/reusables/organizations/team-discussions-purpose.md b/translations/es-ES/data/reusables/organizations/team-discussions-purpose.md new file mode 100644 index 0000000000000..52ea6dfeff55d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-discussions-purpose.md @@ -0,0 +1 @@ +En la página de tu equipo, puedes utilizar los debates de equipo para las conversaciones que se extienden en los proyectos o repositorios y no pertenecen a un informe de problemas o solicitud de extracción específicos. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo. diff --git a/translations/es-ES/data/reusables/organizations/team-discussions-tab.md b/translations/es-ES/data/reusables/organizations/team-discussions-tab.md new file mode 100644 index 0000000000000..814c4b4f76119 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-discussions-tab.md @@ -0,0 +1 @@ +1. En la parte superior de la página del equipo, da clic en {% octicon "comment-discussion" aria-label="The discussion icon" %}**Debates**. ![Pestaña de debates de equipo](/assets/images/help/teams/org-team-page-discussions-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/team-repositories-tab.md b/translations/es-ES/data/reusables/organizations/team-repositories-tab.md new file mode 100644 index 0000000000000..531d881130291 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-repositories-tab.md @@ -0,0 +1 @@ +1. Arriba de la lista de miembros del equipo, da clic en {% octicon "repo" aria-label="The Repository icon" %}**Repositorios**. ![La pestaña de repositorios del equipo](/assets/images/help/organizations/team-repositories-button.png) diff --git a/translations/es-ES/data/reusables/organizations/team-synchronization.md b/translations/es-ES/data/reusables/organizations/team-synchronization.md new file mode 100644 index 0000000000000..874da7f527742 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team-synchronization.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". +{% endif %} diff --git a/translations/es-ES/data/reusables/organizations/team_description.md b/translations/es-ES/data/reusables/organizations/team_description.md new file mode 100644 index 0000000000000..47f580802313e --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_description.md @@ -0,0 +1 @@ +1. Opcionalmente, en el campo de "Descripción", teclea una descripción del equipo. ![Campo de descripción del equipo](/assets/images/help/teams/org-team-description.png) diff --git a/translations/es-ES/data/reusables/organizations/team_maintainers_can.md b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md new file mode 100644 index 0000000000000..b5c7888e43035 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md @@ -0,0 +1,15 @@ +Los miembros con permisos de mantenedor del equipo pueden hacer lo siguiente: + +- [Cambiar el nombre y la descripción del equipo](/articles/renaming-a-team) +- [Cambiar la visibilidad del equipo](/articles/changing-team-visibility) +- [Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team) +- [Solicitar agregar o cambiar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team) +- [Configurar la imagen de perfil del equipo](/articles/setting-your-team-s-profile-picture) +- [Editar debates de equipo](/articles/managing-disruptive-comments/#editing-a-comment) +- [Eliminar debates de equipo](/articles/managing-disruptive-comments/#deleting-a-comment) +- [Agregar a miembros de la organización al equipo](/articles/adding-organization-members-to-a-team) +- [Eliminar a miembros de la organización del equipo](/articles/removing-organization-members-from-a-team) +- [Promover un miembro del equipo existente a mantenedor del equipo](/articles/giving-team-maintainer-permissions-to-an-organization-member) +- Eliminar el acceso del equipo a los repositorios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +- [Administra la tarea de revisión de código para el equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Administrar los recordatorios programados para las solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/es-ES/data/reusables/organizations/team_members_tab.md b/translations/es-ES/data/reusables/organizations/team_members_tab.md new file mode 100644 index 0000000000000..16225581a9e84 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_members_tab.md @@ -0,0 +1 @@ +1. En la parte superior de la página del equipo, da clic en {% octicon "organization" aria-label="The members symbol" %}**Miembros**. ![Pestaña de miembros](/assets/images/help/teams/members-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/team_name.md b/translations/es-ES/data/reusables/organizations/team_name.md new file mode 100644 index 0000000000000..df70ba69a0c32 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_name.md @@ -0,0 +1 @@ +1. Debajo de "Crear un equipo nuevo", teclea el nombre para tu equipo nuevo. ![Campo de nombre de equipo](/assets/images/help/teams/org-new-team-name.png) diff --git a/translations/es-ES/data/reusables/organizations/team_settings.md b/translations/es-ES/data/reusables/organizations/team_settings.md new file mode 100644 index 0000000000000..9db1abdbada9d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_settings.md @@ -0,0 +1 @@ +1. En la parte superior de la página del equipo, da clic en {% octicon "gear" aria-label="The Settings gear" %}**Configuración**. ![Pestaña de configuración de equipo](/assets/images/help/teams/team-settings-button.png) diff --git a/translations/es-ES/data/reusables/organizations/team_visibility.md b/translations/es-ES/data/reusables/organizations/team_visibility.md new file mode 100644 index 0000000000000..c89f190a0138d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/team_visibility.md @@ -0,0 +1 @@ +1. Decide si el equipo será visible o secreto. ![Opciones de visibilidad que incluyen secreto y visible](/assets/images/help/teams/new-team-visibility.png) diff --git a/translations/es-ES/data/reusables/organizations/teams.md b/translations/es-ES/data/reusables/organizations/teams.md new file mode 100644 index 0000000000000..d205e17f57002 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/teams.md @@ -0,0 +1 @@ +1. Debajo del nombre de tu organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos en la página de la organización](/assets/images/help/organizations/organization-teams-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/teams_sidebar.md b/translations/es-ES/data/reusables/organizations/teams_sidebar.md new file mode 100644 index 0000000000000..ff6322eefef56 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/teams_sidebar.md @@ -0,0 +1 @@ +1. En la barra lateral de Configuración, da clic en **Equipos**. ![Pestaña de equipos en la barra lateral de configuración de la organización](/assets/images/help/settings/settings-sidebar-team-settings.png) diff --git a/translations/es-ES/data/reusables/organizations/types-of-team-visibility.md b/translations/es-ES/data/reusables/organizations/types-of-team-visibility.md new file mode 100644 index 0000000000000..6295d273711a1 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/types-of-team-visibility.md @@ -0,0 +1,4 @@ +Los equipos pueden ser visibles o secretos: + +- Todos los miembros en la organización pueden [ver y @mencionar](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) a los equipos visibles. +- Solo las personas en el equipo y aquellas con permisos de propietario pueden ver los equipos secretos. Son ideales para ocultar equipos con nombres o miembros sensibles, tales como aquellos que se utilizan para trabajar con socios o clientes externos. Los equipos secretos no pueden anidarse bajo equipos padre ni tener equipos hijo. diff --git a/translations/es-ES/data/reusables/organizations/user_must_accept_invite_email.md b/translations/es-ES/data/reusables/organizations/user_must_accept_invite_email.md new file mode 100644 index 0000000000000..2364cf8881e0d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/user_must_accept_invite_email.md @@ -0,0 +1 @@ +1. La persona invitada recibirá un correo electrónico invitándola a la organización. Necesitarán aceptar la invitación antes de convertirse en miembros de la organización. diff --git a/translations/es-ES/data/reusables/organizations/verified-domains-details.md b/translations/es-ES/data/reusables/organizations/verified-domains-details.md new file mode 100644 index 0000000000000..e356541dd17fc --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/verified-domains-details.md @@ -0,0 +1 @@ +Para mostrar una insignia de "Verificado", el sitio web y la información de correo electrónico que se muestran en el perfil de una organización deben coincidir con el o los dominios verificados. Si el sitio web y la dirección de correo electrónico que se muestran en el perfil de tu organización se alojan en un dominio diferente, debes verificar ambos dominios. Si el sitio web y dirección de correo electrónico utilizan variantes del mismo dominio, debes verificar ambas variantes. Por ejemplo, si el perfil muestra el sitio web `www.example.com` y la dirección de correo electrónico `info@example.com`, deberías verificar tanto `www.example.com` como `example.com`. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/verified-domains.md b/translations/es-ES/data/reusables/organizations/verified-domains.md new file mode 100644 index 0000000000000..50ecf2c70974d --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/verified-domains.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Dominios verificados**. ![Botón de dominios verificados](/assets/images/help/organizations/verified-domains-button.png) diff --git a/translations/es-ES/data/reusables/organizations/watch-team-options.md b/translations/es-ES/data/reusables/organizations/watch-team-options.md new file mode 100644 index 0000000000000..8d3db29bd2016 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/watch-team-options.md @@ -0,0 +1 @@ +1. En el lado izquierdo de la página del equipo, debajo del nombre del equipo, diff --git a/translations/es-ES/data/reusables/package_registry/actions-configuration.md b/translations/es-ES/data/reusables/package_registry/actions-configuration.md new file mode 100644 index 0000000000000..5bceb5c877efa --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/actions-configuration.md @@ -0,0 +1 @@ +Los pasos de configuración varían de acuerdo con el cliente del paquete. Para obtener información general sobre como configurar un flujo de trabajo para {% data variables.product.prodname_actions %}, consulta la sección "[Configurar un flujo de trabajo](/github/automating-your-workflow-with-github-actions/configuring-a-workflow)". diff --git a/translations/es-ES/data/reusables/package_registry/add-npmrc-to-repo-step.md b/translations/es-ES/data/reusables/package_registry/add-npmrc-to-repo-step.md new file mode 100644 index 0000000000000..06c099773f1bf --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/add-npmrc-to-repo-step.md @@ -0,0 +1 @@ +3. Agrega el archivo *.npmrc* al repositorio en donde {% data variables.product.prodname_registry %} pueda encontrar tu proyecto. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio utilizando la línea de comandos](/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line)". diff --git a/translations/es-ES/data/reusables/package_registry/admins-can-configure-package-types.md b/translations/es-ES/data/reusables/package_registry/admins-can-configure-package-types.md new file mode 100644 index 0000000000000..4b928957fdc94 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/admins-can-configure-package-types.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion %} +{% note %} + +**Nota:** Este tipo de paquete podría no estar disponible para tu instancia, ya que los administradores de sitio pueden habilitar o inhabilitar cada tipo de paquete compatible. Para obtener más información, consulta la sección "[Configurar el soporte de los paquetes para tu empresa](/enterprise/admin/packages/configuring-packages-support-for-your-enterprise)". + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md b/translations/es-ES/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md new file mode 100644 index 0000000000000..688d39e0298fe --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md @@ -0,0 +1 @@ +{% data variables.product.prodname_registry %} es compatible con versiones `SNAPSHOT` de Apache Maven. Para utilizar un repositorio para descargar este tipo de artefacto, debes habilitar las CAPTURAS (SNAPSHOTS) en tu archivo*~/.m2/settings.xml* file. diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md new file mode 100644 index 0000000000000..c85cb7bd74cc8 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md @@ -0,0 +1,11 @@ +Necesitas de un token de acceso para publicar, instalar, y borrar paquetes en {{ site.data.variables.product.prodname_registry }}. Puedes utilizar un token de acceso personal para autenticarte con tu nombre de usuario directamente en {% data variables.product.prodname_registry %} o en la API de {% data variables.product.prodname_dotcom %}. Cuando creas un token de acceso personal, puedes asignar al token diferentes ámbitos en función de tus necesidades. + +{% if currentVersion == "free-pro-team@latest" %} +Para autenticarte utilizando un +flujo de trabajo de {% data variables.product.prodname_actions %}: +- Para los registros de paquete (`PACKAGE-REGISTRY.pkg.github.com`), puedes utilizar un `GITHUB_TOKEN`. +- Para el registro de contenedor (`ghcr.io/OWNER/IMAGE-NAME`), debes utilizar un token de acceso personal. +{% else %} +Para autenticarte en el +{% data variables.product.prodname_registry %} utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}, debes utilizar `GITHUB_TOKEN`. +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-step.md b/translations/es-ES/data/reusables/package_registry/authenticate-step.md new file mode 100644 index 0000000000000..07bb226f027d7 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/authenticate-step.md @@ -0,0 +1 @@ +1. Autentícate en {% data variables.product.prodname_registry %}. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_registry %}](#authenticating-to-github-packages)." diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md new file mode 100644 index 0000000000000..3411c5301c410 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -0,0 +1,25 @@ +1. Crea un token de acceso personal nuevo (PAT) con los alcances adecuados para las tareas que quieres realizar. Si tu organización requiere SSO, debes hablitarlo para tu token nuevo. + {% warning %} + + **Nota:** Si seleccionas el alcance `write:packages`, deselecciona el alcance `repo` cuando crees el PAT. El agregar un PAT con el alcance `repo` en forma de secreto en tu repositorio permite que todos los colaboradores del repositorio accedan a esta credencial. Esto otorga acceso adicional innecesario cuando un PAT con el alcance `repo` se utiliza dentro de una acción. Para obtener más información acerca de las mejores prácticas de seguridad, consulta la sección "[Fortalecimiento de seguridad para las GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". + + {% endwarning %} + + - Selecciona el alcance `read:packages` para descargar imágenes de contenedor y leer sus metadatos. + - Selecciona el alcance `write:packages` para descargar y cargar imágenes de contenedor y leer y escribir sus metadatos. + - Selecciona el alcance `delete:packages` para borrar las imágenes de contenedor. + + Para obtener más información, consulta la sección "[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". + +2. Guarda tu PAT. Te recomendamos guardar tu PAT como una variable de ambiente. + ```shell + $ export CR_PAT=YOUR_TOKEN + ``` +3. Utilizando el CLI para tu tipo de contenedor, ingresa en el +servicio del {% data variables.product.prodname_github_container_registry %} en `ghcr.io`. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} diff --git a/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md new file mode 100644 index 0000000000000..47e0094255e0b --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" %} +Si quieres autenticarte en +el {% data variables.product.prodname_github_container_registry %} en un flujo de trabajo de {% data variables.product.prodname_actions %}, entonces debes utilizar un token de acceso personal (PAT). El `GITHUB_TOKEN` no tiene los permisos requeridos actualmente. Durante el beta del {% data variables.product.prodname_github_container_registry %}, la única forma de autenticación compatible es el PAT. + +Los PAT pueden otorgar accesos amplios a tu cuenta. Te recomendamos seleccionar únicamente los alcances necesarios de lectura, escritura o borrado de `package` cuando crees un PAT para autenticarte con el {% data variables.product.prodname_container_registry %}. Evita incluir el alcance `repo` en un pat que utilice algún flujo de trabajo de GitHub Actions, ya que otorga accesos adicionales innecesarios. + +Si te gustaría utilizar el {% data variables.product.prodname_container_registry %} en las acciones durante el beta, sigue nuestras mejores prácticas de seguridad para uso de PAT en la sección "[Fortalecimiento de seguridad para las GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". + +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/billing-for-container-registry.md b/translations/es-ES/data/reusables/package_registry/billing-for-container-registry.md new file mode 100644 index 0000000000000..8ddf10cd1c87a --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/billing-for-container-registry.md @@ -0,0 +1,3 @@ +Durante el beta de {% data variables.product.prodname_github_container_registry %}, tanto el registro de Docker de {% data variables.product.prodname_container_registry %} nuevo como el existente de {% data variables.product.prodname_registry %} serán gratuitos. Para obtener más información acerca del registro de Docker de {% data variables.product.prodname_registry %}, consulta la sección "[Configurar Docker para su uso con {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)". + +Después del beta, las mismas tasas de facturación y almacenamiento que otros registros de {% data variables.product.prodname_registry %} utilizan aplicarán al registro de contenedores. Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/es-ES/data/reusables/package_registry/container-registry-beta-billing-note.md new file mode 100644 index 0000000000000..b88e31e44013e --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Actualización de facturación para el almacenamiento de imágenes de contenedor:** durante la fase beta del {% data variables.product.prodname_github_container_registry %}, el almacenamiento y ancho de banda de las imágenes de Docker son gratuitas para los servicios de hospedaje viejos de `docker.pkg.github.com` y para los nuevos de `ghcr.io`. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-beta.md b/translations/es-ES/data/reusables/package_registry/container-registry-beta.md new file mode 100644 index 0000000000000..ed9e035957151 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/container-registry-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** El {% data variables.product.prodname_github_container_registry %} se encuentra actualmente en su fase de beta público y está sujeto a cambios. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la vista previa de características. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" y [Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-feature-highlights.md b/translations/es-ES/data/reusables/package_registry/container-registry-feature-highlights.md new file mode 100644 index 0000000000000..f191bc89de4df --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/container-registry-feature-highlights.md @@ -0,0 +1,4 @@ +Con el registro de contenedores, puedes: +- Almacenar imágenes de contenedor dentro de tu organización y cuenta de usuario, en vez de en un repositorio. +- Configurar permisos específicos y visibilidad independiente de los permisos y visibilidad del repositorio. +- Acceder a imágenes de contenedores públicos anónimamente. diff --git a/translations/es-ES/data/reusables/package_registry/create-npmrc-owner-step.md b/translations/es-ES/data/reusables/package_registry/create-npmrc-owner-step.md new file mode 100644 index 0000000000000..cc632e46ace58 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/create-npmrc-owner-step.md @@ -0,0 +1,16 @@ +2. En el mismo directorio que tu archivo `package.json`, crea o edita un archivo `.npmrc` para incluir una línea que especifique la URL de {% data variables.product.prodname_registry %} y el propietario de la cuenta. Reemplaza `OWNER` con el nombre de la cuenta de usuario u organización a la que pertenezca el repositorio que contiene tu proyecto. + +{% if currentVersion == "free-pro-team@latest" %} + ```shell +registry=https://npm.pkg.github.com/OWNER + ``` +{% else %} + Si se habilita el aislamiento de subdominios: + ```shell + registry=https://npm.HOSTNAME/OWNER + ``` + Si se inhabilita el aislamiento de subdominios: + ```shell + https://HOSTNAME/_registry/npm/OWNER + ``` +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/default-name.md b/translations/es-ES/data/reusables/package_registry/default-name.md new file mode 100644 index 0000000000000..f45ef82c0083b --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/default-name.md @@ -0,0 +1 @@ +Predeterminadamente, {% data variables.product.prodname_dotcom %} publica el paquete en un repositorio existente con el mismo nombre que éste. diff --git a/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md new file mode 100644 index 0000000000000..172e93ce170f7 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -0,0 +1,5 @@ +{% warning %} + +**Nota:** El registro De docker del {% data variables.product.prodname_registry %} se sustituirá con el {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} en un lanzamiento futuro de {% data variables.product.product_name %} {% endif %}.{% if currentVersion == "free-pro-team@latest" %} Para aprender cómo migrar tus imágenes existentes de Docker y los flujos de trabajo que las utilizan, consulta las secciones "[Migrarse al {% data variables.product.prodname_github_container_registry %} para las imágenes de Docker](/packages/guides/migrating-to-github-container-registry-for-docker-images)" y "[Guías de contenedores para el {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)".{% endif %} + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md new file mode 100644 index 0000000000000..ac76364a4ecde --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Antes de que puedas utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la característica para tu cuenta. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)". + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/package_registry/navigate-to-packages.md b/translations/es-ES/data/reusables/package_registry/navigate-to-packages.md new file mode 100644 index 0000000000000..2ae8790c43d02 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/navigate-to-packages.md @@ -0,0 +1 @@ +1. Da clic en el nombre del paquete que quieres ver. ![Nombre del paquete](/assets/images/help/package-registry/package-name.png) diff --git a/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/es-ES/data/reusables/package_registry/package-page-info.md b/translations/es-ES/data/reusables/package_registry/package-page-info.md new file mode 100644 index 0000000000000..4c6e5cedff06d --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/package-page-info.md @@ -0,0 +1 @@ +En la página del paquete, {% data variables.product.prodname_dotcom %} proporciona metadatos para cada versión, tal como la fecha de publicación. Puedes ver los detalles del paquete, incluyendo una descripción e instrucciones de uso y de instalación. Puedes descargar cualquier activo asociado con el paquete y ver la información de la actividad de descarga. Para obtener una página de paquete de ejemplo, consulta [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). diff --git a/translations/es-ES/data/reusables/package_registry/package-registry-with-github-tokens.md b/translations/es-ES/data/reusables/package_registry/package-registry-with-github-tokens.md new file mode 100644 index 0000000000000..06d58339f459c --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/package-registry-with-github-tokens.md @@ -0,0 +1 @@ +Si estás utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes utilizar un `GITHUB_TOKEN` para publicar y consumir paquetes en {% data variables.product.prodname_registry %} sin que necesites almacenar y administrar un token de acceso personal. Para obtener más información, consulta la sección "[Autenticarse con el `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". diff --git a/translations/es-ES/data/reusables/package_registry/package-settings-from-org-level.md b/translations/es-ES/data/reusables/package_registry/package-settings-from-org-level.md new file mode 100644 index 0000000000000..1dae19ed104f1 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/package-settings-from-org-level.md @@ -0,0 +1,4 @@ +1. En {% data variables.product.prodname_dotcom %}, navega a la página principal de tu organización. +2. Debajo del nombre de tu organización, haz clic en **Paquetes**. ![Botón de invitación para el acceso al contenedor](/assets/images/help/package-registry/org-tab-for-packages.png) +3. Busca y selecciona tu paquete. +4. En la parte superior derecha de la página de llegada de tu imagen de contenedor, da clic en **Configuración de paquete**. ![Botón de configuración de paquete](/assets/images/help/package-registry/packages-settings-from-package-landing-page.png) diff --git a/translations/es-ES/data/reusables/package_registry/package-settings-from-user-level.md b/translations/es-ES/data/reusables/package_registry/package-settings-from-user-level.md new file mode 100644 index 0000000000000..dc211ec33f086 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/package-settings-from-user-level.md @@ -0,0 +1,5 @@ +1. En {% data variables.product.prodname_dotcom %}, navega hasta la página principal de tu cuenta de usuario. +2. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Foto de perfil](/assets/images/help/profile/top_right_avatar.png) +3. En tu página de perfil, en la parte superior derecha, da clic en **Paquetes**. ![Opción de paquetes en la página de perfil](/assets/images/help/package-registry/packages-from-user-profile.png) +3. Busca y selecciona tu paquete. +4. En la parte superior derecha de la página de llegada de tu imagen de contenedor, da clic en **Configuración de paquete**. ![Botón de configuración de paquete](/assets/images/help/package-registry/packages-settings-from-package-landing-page.png) diff --git a/translations/es-ES/data/reusables/package_registry/packages-billing.md b/translations/es-ES/data/reusables/package_registry/packages-billing.md new file mode 100644 index 0000000000000..709cc0136f728 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-billing.md @@ -0,0 +1 @@ +El uso de {% data variables.product.prodname_registry %} es gratuito para los paquetes públicos. Para los paquetes privados, cada cuenta de {% data variables.product.product_name %} recibe una cantidad determinada de almacenamiento gratuito y de transferencia de datos, dependiendo del producto que se utilice en la cuenta. Cualquier uso que no se contemple en las cantidades incluidas se controla con los límites de gasto. diff --git a/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md b/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/packages-from-code-tab.md b/translations/es-ES/data/reusables/package_registry/packages-from-code-tab.md new file mode 100644 index 0000000000000..505e716e44280 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-from-code-tab.md @@ -0,0 +1,6 @@ +1. A la derecha de la lista de archivos, da clic en **Paquetes**. + {% if currentVersion == "free-pro-team@latest" %} + ![Enlace de paquetes en la página de resumen](/assets/images/help/package-registry/packages-link.png) + {% else %} + ![Enlace de paquetes en la página de resumen](/assets/images/help/package-registry/packages-from-repo.png) + {% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md new file mode 100644 index 0000000000000..06105e439d971 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md @@ -0,0 +1,7 @@ +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Nota:** El {% data variables.product.prodname_registry %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000000..385b9e5c61995 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +Si eres un cliente que paga mensualmente, tu cuenta tendrá un límite de gastos predeterminado de $0, lo cual previene el uso adicional de almacenamiento o transferencia de datos después de que alcances las cantidades incluidas. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. diff --git a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000000..afa06b7e4c7d3 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +Si tienes un límite de gastos ilimitado o configuraste un límite de gastos mayor a $0, se te cobrará por cualquier almacenamiento o transferencia de datos adicional, lo cual también se conoce como excedentes, sobre tu límite de gastos. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_registry %}. diff --git a/translations/es-ES/data/reusables/package_registry/public-or-private-packages.md b/translations/es-ES/data/reusables/package_registry/public-or-private-packages.md new file mode 100644 index 0000000000000..9e5f6280d6a1c --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/public-or-private-packages.md @@ -0,0 +1 @@ +Puedes publicar paquetes en un repositorio público (paquetes públicos) para compartirlos con {% if currentVersion == "free-pro-team@latest" %}todo {% data variables.product.prodname_dotcom %}{% else %}todos en tu instancia{% endif %}, o publicarlos en un repositorio privado (paquetes privados) para compartilo con colaboradores o con una organización. diff --git a/translations/es-ES/data/reusables/package_registry/publish_package.md b/translations/es-ES/data/reusables/package_registry/publish_package.md new file mode 100644 index 0000000000000..8f978e4459f7c --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/publish_package.md @@ -0,0 +1,5 @@ +1. Publicar el paquete: + + ```shell + $ npm publish + ``` diff --git a/translations/es-ES/data/reusables/package_registry/repository_connection_steps.md b/translations/es-ES/data/reusables/package_registry/repository_connection_steps.md new file mode 100644 index 0000000000000..b94c1d79d9dea --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/repository_connection_steps.md @@ -0,0 +1,3 @@ +1. Debajo de tus versiones de paquete, da clic en **Conectar repositorio**. ![Botón para conectarse a un reopsitorio en la página de llegada de paquetes](/assets/images/help/package-registry/connect-repository.png) + +1. Selecciona un repositorio y luego da clic en **Conectar repositorio**. ![Botón de conectarse a un repositorio en la ventana emergente de selección de repositorios](/assets/images/help/package-registry/select_a_repo.png) diff --git a/translations/es-ES/data/reusables/package_registry/required-scopes.md b/translations/es-ES/data/reusables/package_registry/required-scopes.md new file mode 100644 index 0000000000000..867bce4b06cdf --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/required-scopes.md @@ -0,0 +1 @@ +Debes utilizar un token de acceso personal con los alcances adecuados para publicar e instalar paquetes en {% data variables.product.prodname_registry %}. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)". diff --git a/translations/es-ES/data/reusables/package_registry/verify_repository_field.md b/translations/es-ES/data/reusables/package_registry/verify_repository_field.md new file mode 100644 index 0000000000000..c29ac87889e5d --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/verify_repository_field.md @@ -0,0 +1 @@ +1. Verifica el campo `repository` en el *package.json*. de tu proyecto. El campo `repository` debe coincidir con la URL de tu repositorio de {% data variables.product.prodname_dotcom %}. Por ejemplo, si la URL de tu repositorio es `github.com/my-org/test`, entonces el campo de repositorio debe ser `git://github.com/my-org/test.git`. diff --git a/translations/es-ES/data/reusables/package_registry/viewing-packages.md b/translations/es-ES/data/reusables/package_registry/viewing-packages.md new file mode 100644 index 0000000000000..149f08a115433 --- /dev/null +++ b/translations/es-ES/data/reusables/package_registry/viewing-packages.md @@ -0,0 +1 @@ +Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/manage-packages/viewing-packages)". diff --git a/translations/es-ES/data/reusables/pages/about-front-matter.md b/translations/es-ES/data/reusables/pages/about-front-matter.md new file mode 100644 index 0000000000000..25ba903e24fc4 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/about-front-matter.md @@ -0,0 +1 @@ +Para configurar variables y metadatos, tales como el título y diseño, de una página o publicación en tu sitio, puedes agregar YAML front matter a la parte superior de cualquier archivo Markdown o HTML. Para obtener más información, consulta la sección "[Front Matter](https://jekyllrb.com/docs/front-matter/)" en la documentación de Jekyll. diff --git a/translations/es-ES/data/reusables/pages/add-jekyll-theme.md b/translations/es-ES/data/reusables/pages/add-jekyll-theme.md new file mode 100644 index 0000000000000..fa6c7c6fa7a4a --- /dev/null +++ b/translations/es-ES/data/reusables/pages/add-jekyll-theme.md @@ -0,0 +1 @@ +Puedes agregar un tema de Jekyll a tu sitio de {% data variables.product.prodname_pages %} para personalizar la apariencia de tu sitio. diff --git a/translations/es-ES/data/reusables/pages/admin-must-push.md b/translations/es-ES/data/reusables/pages/admin-must-push.md new file mode 100644 index 0000000000000..fc60e337a548d --- /dev/null +++ b/translations/es-ES/data/reusables/pages/admin-must-push.md @@ -0,0 +1,5 @@ +{% tip %} + +**Nota**: Si los archivos fuente de tu sitio de {% if currentVersion ver_lt "enterprise-server@2.23" %} se ubican en la fuente de publicación predeterminada—`master` para sitios de usuario o de organización, o en `gh-pages` para los sitios de proyecto—pero tu sitio{% endif %} no se publició automáticamente, asegúrate de que alguien con permisos administrativos y una dirección de correo electrónico verificada haya subido la información a la fuente de publicación. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/pages/best-with-supported-themes.md b/translations/es-ES/data/reusables/pages/best-with-supported-themes.md new file mode 100644 index 0000000000000..6c9be5d7fac7c --- /dev/null +++ b/translations/es-ES/data/reusables/pages/best-with-supported-themes.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Estas instrucciones funcionan mejor con los temas que son oficialmente compatibles con +{% data variables.product.prodname_pages %}. Para ver una lista completa de temas compatibles, consulta "[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %}. +{% endif %} diff --git a/translations/es-ES/data/reusables/pages/build-failure-email-server.md b/translations/es-ES/data/reusables/pages/build-failure-email-server.md new file mode 100644 index 0000000000000..6bef48f3aa22f --- /dev/null +++ b/translations/es-ES/data/reusables/pages/build-failure-email-server.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + {% tip %} + + Solo recibiras un correo electrónico si habilitas la compatibilidad con correo externo en {% data variables.product.product_location %}. Para obtener más información, contacta a tu administrador de sitio. + + {% endtip %} +{% endif %} diff --git a/translations/es-ES/data/reusables/pages/build-locally-download-cname.md b/translations/es-ES/data/reusables/pages/build-locally-download-cname.md new file mode 100644 index 0000000000000..b6a36a45bcd10 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/build-locally-download-cname.md @@ -0,0 +1 @@ +1. Si utilizas un generador de sitio estático para construir tu sitio localmente y subes los archivos generados a {% data variables.product.product_name %}, extrae la confirmación que agregó el archivo _CNAME_ a tu repositorio local. Para obtener más información, consulta la sección "[Resolver problemas en dominios personalizados y en {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#cname-errors)". diff --git a/translations/es-ES/data/reusables/pages/configure-publishing-source.md b/translations/es-ES/data/reusables/pages/configure-publishing-source.md new file mode 100644 index 0000000000000..33256406b9b52 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/configure-publishing-source.md @@ -0,0 +1 @@ +1. Configura tu fuente de publicción. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". diff --git a/translations/es-ES/data/reusables/pages/contact-dns-provider.md b/translations/es-ES/data/reusables/pages/contact-dns-provider.md new file mode 100644 index 0000000000000..2216af6827b59 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/contact-dns-provider.md @@ -0,0 +1 @@ +Para obtener más información acerca de cómo crear el registro correcto, consulta la documentación de tu proveedor de DNS. diff --git a/translations/es-ES/data/reusables/pages/create-repo-name.md b/translations/es-ES/data/reusables/pages/create-repo-name.md new file mode 100644 index 0000000000000..d4d7aad0bfa67 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/create-repo-name.md @@ -0,0 +1 @@ +1. Escribe un nombre para tu repositorio y una descripción opcional. Si estás creando un sitio de usuario u organización, tu repositorio se debe nombrar `.github.io` o `.github.io`. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites)". ![Crear un campo de repositorio](/assets/images/help/pages/create-repository-name-pages.png) diff --git a/translations/es-ES/data/reusables/pages/decide-publishing-source.md b/translations/es-ES/data/reusables/pages/decide-publishing-source.md new file mode 100644 index 0000000000000..ab45ace81fff7 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/decide-publishing-source.md @@ -0,0 +1 @@ +1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}Decide{% else %}Si estás creando un sitio de proyecto, decide{% endif %} qué fuente de publicación quieres utilizar. {% if currentVersion ver_lt "enterprise-server@2.23" %}Si estás creando un sitio de usuario o de organización, debes almacenar el código fuente de tu sitio en la rama `master`.{% endif %} Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/es-ES/data/reusables/pages/default-domain-information.md b/translations/es-ES/data/reusables/pages/default-domain-information.md new file mode 100644 index 0000000000000..9d94c5ca60f8f --- /dev/null +++ b/translations/es-ES/data/reusables/pages/default-domain-information.md @@ -0,0 +1 @@ +Para obtener más información acerca del dominio predeterminado para tu sitio, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites)". diff --git a/translations/es-ES/data/reusables/pages/enforce-https-custom-domain.md b/translations/es-ES/data/reusables/pages/enforce-https-custom-domain.md new file mode 100644 index 0000000000000..e127c49bd71d4 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/enforce-https-custom-domain.md @@ -0,0 +1 @@ +1. Opcionalmente, para requerir cifrado HTTPS para tu sitio, selecciona **Requerir HTTPS**. Puede tomar hasta 24 horas antes de que esta opción se encuentre disponible. Para obtener más información, consulta "[Asegurar tu sitio de {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)". ![Opción de Requerir HTTPS para dominios personalizados](/assets/images/help/pages/enforce-https-custom-domains.png) diff --git a/translations/es-ES/data/reusables/pages/jekyll-install-troubleshooting.md b/translations/es-ES/data/reusables/pages/jekyll-install-troubleshooting.md new file mode 100644 index 0000000000000..1be46228486d3 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/jekyll-install-troubleshooting.md @@ -0,0 +1,9 @@ +{% mac %} + +{% tip %} + +**Sugerencia:** si ves un error de Ruby cuando tratas de instalar Jekyll utilizando Bundler, es posible que necesites utilizar un administrador de paquete, como [RVM](https://rvm.io/) o [Homebrew](http://brew.sh/), para administrar tu instalación de Ruby. Para obtener más información, consulta la sección "[Solución de problemas](https://jekyllrb.com/docs/troubleshooting/#jekyll--macos)" en la documentación de Jekyll. + +{% endtip %} + +{% endmac %} diff --git a/translations/es-ES/data/reusables/pages/must-have-repo-first.md b/translations/es-ES/data/reusables/pages/must-have-repo-first.md new file mode 100644 index 0000000000000..d11746390d3a0 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/must-have-repo-first.md @@ -0,0 +1 @@ +Antes de que puedas crear tu sitio, debes tener un repositorio para el mismo en {% data variables.product.product_name %}. Si no estás creando tu sitio en un repositorio existente, consulta la sección "[Crear un repositorio para tu sitio](#creating-a-repository-for-your-site)". diff --git a/translations/es-ES/data/reusables/pages/navigate-publishing-source.md b/translations/es-ES/data/reusables/pages/navigate-publishing-source.md new file mode 100644 index 0000000000000..5bfdb6c0075b2 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/navigate-publishing-source.md @@ -0,0 +1 @@ +1. Navega a la fuente de publicación para tu sitio. Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/es-ES/data/reusables/pages/navigate-site-repo.md b/translations/es-ES/data/reusables/pages/navigate-site-repo.md new file mode 100644 index 0000000000000..ff62cd8199fa3 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/navigate-site-repo.md @@ -0,0 +1 @@ +1. En {% data variables.product.product_name %}, navega al repositorio de tu sitio. diff --git a/translations/es-ES/data/reusables/pages/new-or-existing-repo.md b/translations/es-ES/data/reusables/pages/new-or-existing-repo.md new file mode 100644 index 0000000000000..e4df9329e31ba --- /dev/null +++ b/translations/es-ES/data/reusables/pages/new-or-existing-repo.md @@ -0,0 +1,3 @@ +Si tu sitio es un proyecto independiente, puedes crear un repositorio nuevo para almacenar el código fuente del mismo. Si tu sitio se asocia con un proyecto existente, puedes agregar el código fuente{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}al repositorio de ese proyecto en una carpeta de `/docs` en la rama predeterminada o en una rama diferente.{% else %}para tu sitio a una rama de `gh-pages` o una carpeta de `docs` en la rama `master` en el repositorio de ese proyecto.{% endif %} Por ejemplo, si creas un sitio para publicar documentos para un proyecto que ya está en {% data variables.product.product_name %}, tal vez quieras almacenar el código fuente para este sitio en el mismo repositorio del proyecto. + +Si quieres crear un sitio en un repositorio existente, salta hasta la sección "[Crear tu sitio](#creating-your-site)". diff --git a/translations/es-ES/data/reusables/pages/no_sensitive_data_pages.md b/translations/es-ES/data/reusables/pages/no_sensitive_data_pages.md new file mode 100644 index 0000000000000..0c36e74e9baab --- /dev/null +++ b/translations/es-ES/data/reusables/pages/no_sensitive_data_pages.md @@ -0,0 +1 @@ +Los sitios {% data variables.product.prodname_pages %} no se deben usar para realizar transacciones que impliquen el envío de información confidencial como contraseñas o números de tarjeta de crédito. diff --git a/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md new file mode 100644 index 0000000000000..0dfaa7f40ba0e --- /dev/null +++ b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md @@ -0,0 +1,5 @@ + {% warning %} + + **Advertencia**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet, aún si el repositorio del sitio es privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %}. Si tienes datos sensibles en el repositorio de tu sitio, tal vez quieras eliminarlos antes de publicarlo. Para obtener más información, consulta las secciones{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configurar {% data variables.product.prodname_pages %} para tu empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" y {% endif %} "[Acerca de la visibilidad del repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + + {% endwarning %} diff --git a/translations/es-ES/data/reusables/pages/recommend-bundler.md b/translations/es-ES/data/reusables/pages/recommend-bundler.md new file mode 100644 index 0000000000000..27e38cb734cb2 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/recommend-bundler.md @@ -0,0 +1,4 @@ +Recomendamos utilizando [Bundler](http://bundler.io/) para instalar y ejecutar Jekyll. Bundler administra las dependencias de gema de Ruby, reduce los errores de construcción de Jekyll y evita los errores relacionados con el entorno. Para instalar Bundler: + + 1. Instala Ruby. Para obtener más información, consulta "[Instalar Ruby](https://www.ruby-lang.org/en/documentation/installation/)" en la documentación de Ruby. + 2. Instala Bundler. Para obtener más información, visita "[Bundler](https://bundler.io/)". diff --git a/translations/es-ES/data/reusables/pages/remove-submodule.md b/translations/es-ES/data/reusables/pages/remove-submodule.md new file mode 100644 index 0000000000000..65c0f17f10155 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/remove-submodule.md @@ -0,0 +1,9 @@ +Para resolver problemas, primero decide si quieres utilizar un submódulo, lo cual es un proyecto de Git dentro de otro proyecto de Git; ya que estos a veces se crean por accidente. + +Si no quieres utilizar un submódilo, elimínalo reemplazando PATH-TO-SUBMODULE con la ruta del submódulo: +```shell +$ git submodule deinit PATH-TO-SUBMODULE +$ git rm PATH-TO-SUBMODULE +$ git commit -m "Remove submodule" +$ rm -rf .git/modules/PATH-TO-SUBMODULE +``` diff --git a/translations/es-ES/data/reusables/pages/save-custom-domain.md b/translations/es-ES/data/reusables/pages/save-custom-domain.md new file mode 100644 index 0000000000000..5873d54c62320 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/save-custom-domain.md @@ -0,0 +1 @@ +1. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-domain.png) diff --git a/translations/es-ES/data/reusables/pages/search-for-includes.md b/translations/es-ES/data/reusables/pages/search-for-includes.md new file mode 100644 index 0000000000000..a4cd1d6d81228 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/search-for-includes.md @@ -0,0 +1 @@ +Para solucionar problemas, busca el archivo `include` en el mensaje de error para ver dónde has referenciado otros archivos tales como {% raw %}`{% include example_header.html %}`{% endraw %}. diff --git a/translations/es-ES/data/reusables/pages/test-locally.md b/translations/es-ES/data/reusables/pages/test-locally.md new file mode 100644 index 0000000000000..a86da44fc28cf --- /dev/null +++ b/translations/es-ES/data/reusables/pages/test-locally.md @@ -0,0 +1 @@ +Los cambios en tu sitio se publican automáticamente cuando se fusionan con la fuente de publicación de tu sitio. Si quieres pre-visualizar tus cambios primero, puedes hacer los cambios localmente en vez de en {% data variables.product.product_name %}. Después, prueba tu sitio localmente. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". diff --git a/translations/es-ES/data/reusables/pages/theme-customization-help.md b/translations/es-ES/data/reusables/pages/theme-customization-help.md new file mode 100644 index 0000000000000..e57294b65e18f --- /dev/null +++ b/translations/es-ES/data/reusables/pages/theme-customization-help.md @@ -0,0 +1 @@ +El repositorio fuente de tu tema podría ofrecer algo de ayuda para personalizarlo. Por ejemplo, ve el "[_README_ de Minima](https://github.com/jekyll/minima#customizing-templates)." diff --git a/translations/es-ES/data/reusables/pages/update_your_dns_settings.md b/translations/es-ES/data/reusables/pages/update_your_dns_settings.md new file mode 100644 index 0000000000000..33f05b7544802 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/update_your_dns_settings.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}1. Si hay un dominio personalizado para tu sitio, para evitar que alguien más lo tome, actualiza tu configuración de DNS. Para obtener más información, consulta la sección "[Configurar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/configuring-a-custom-domain-for-your-github-pages-site)".{% endif %} diff --git a/translations/es-ES/data/reusables/pages/visit-site.md b/translations/es-ES/data/reusables/pages/visit-site.md new file mode 100644 index 0000000000000..8333125c3751c --- /dev/null +++ b/translations/es-ES/data/reusables/pages/visit-site.md @@ -0,0 +1,7 @@ +1. Para ver tu sitio publicado, debajo de "{% data variables.product.prodname_pages %}", da clic en la URL del mismo. ![URL de tu sitio publicado](/assets/images/help/pages/click-pages-url-to-preview.png) + + {% note %} + + **Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. Si no ves los cambios reflejados en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + + {% endnote %} diff --git a/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md b/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md new file mode 100644 index 0000000000000..e7f527e8c7c56 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/wildcard-dns-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** Es altamente recomendable no utilizar registros DNS comodines, como `*.example.com`. Un registro DNS comodín le permitirá a cualquiera que aloje un sitio {% data variables.product.prodname_pages %} en uno de tus subdominios. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md new file mode 100644 index 0000000000000..23c373719cab3 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -0,0 +1 @@ +Si estás utilizando un dominio apex como tu dominio personalizado, te recomendamos configurar un subdominio `www`. Si configuras los registros correctos para cada dominio, teclea a tu proveedor de DNS, {% data variables.product.prodname_pages %} creará automáticamente redireccionamientos entre los dominios. Por ejemplo, si configuras `www.example.com` como el dominio personalizado para tu sitio, y tienes registros de `ALIAS` y `CNAME` configurados para los dominios de apex y de `www`, entonces `example.com` redireccionará a `www.example.com`. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)". diff --git a/translations/es-ES/data/reusables/pages/yaml-linter.md b/translations/es-ES/data/reusables/pages/yaml-linter.md new file mode 100644 index 0000000000000..6b661167bca12 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/yaml-linter.md @@ -0,0 +1 @@ +Para identificar cualquier error, puedes copiar y pegar el contenido de tu archivo YAML en un filtro de YAML, tal como [YAML Validator](http://codebeautify.org/yaml-validator). diff --git a/translations/es-ES/data/reusables/pages/yaml-rules.md b/translations/es-ES/data/reusables/pages/yaml-rules.md new file mode 100644 index 0000000000000..523c3ec6a1a4b --- /dev/null +++ b/translations/es-ES/data/reusables/pages/yaml-rules.md @@ -0,0 +1,5 @@ +- Utiliza espacios en vez de tabulaciones. +- Incluye un espacio después del `:` para cada valor de par de valor de claves, como `timezone: Africa/Nairobi`. +- Utiliza únicamente caracteres con codificación UTF-8. +- Cita cualquier caracter especial, tal como `:`, como en `title: "my awesome site: an adventure in parse errors"`. +- Para valores de líneas múltiples, utiliza `|` para crear líneas nuevas y `>` para ignorar líneas nuevas. diff --git a/translations/es-ES/data/reusables/policies/abuse.md b/translations/es-ES/data/reusables/policies/abuse.md new file mode 100644 index 0000000000000..a067ceb55d962 --- /dev/null +++ b/translations/es-ES/data/reusables/policies/abuse.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} no tolera abusos.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información sobre las políticas de {% data variables.product.prodname_dotcom %}, consulta nuestras [Condiciones de servicio](/articles/github-terms-of-service) y [Lineamientos comunitarios](/articles/github-community-guidelines).{% endif %} diff --git a/translations/es-ES/data/reusables/policies/github-community-guidelines-and-terms.md b/translations/es-ES/data/reusables/policies/github-community-guidelines-and-terms.md new file mode 100644 index 0000000000000..d4a323671f3ab --- /dev/null +++ b/translations/es-ES/data/reusables/policies/github-community-guidelines-and-terms.md @@ -0,0 +1 @@ +{% data variables.product.company_short %} proporciona un código de conducta básico para todos los que utilizan {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[{% data variables.product.company_short %} Términos de servicio](/github/site-policy/github-terms-of-service)y[{% data variables.product.company_short %} Pautas de la comunidad](/github/site-policy/github-community-guidelines)." diff --git a/translations/es-ES/data/reusables/policies/translation.md b/translations/es-ES/data/reusables/policies/translation.md new file mode 100644 index 0000000000000..a45d7a38e4ce0 --- /dev/null +++ b/translations/es-ES/data/reusables/policies/translation.md @@ -0,0 +1,3 @@ +Este documento está traducido del inglés. En caso de conflicto, incertidumbre o aparente inconsistencia entre esta versión y la versión en inglés de este documento, la versión en inglés es la versión controladora. + +Si tienes sugerencias para mejorar nuestra traducción, por favor abre una propuesta en nuestro repositorio site-policy. diff --git a/translations/es-ES/data/reusables/pre-release-program/api-preview-warning.md b/translations/es-ES/data/reusables/pre-release-program/api-preview-warning.md new file mode 100644 index 0000000000000..73a6284c78630 --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/api-preview-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Advertencia:** La API podría cambiar sin previo aviso durante el periodo de vista previa. Las características de la vista previa no son compatibles con un uso productivo. Si experimentas cualquier problema, contacta a {% data variables.contact.contact_support %}. + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/pre-release-program/content-attachments-public-beta.md b/translations/es-ES/data/reusables/pre-release-program/content-attachments-public-beta.md new file mode 100644 index 0000000000000..7ff031b1c393c --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/content-attachments-public-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** La API de {% data variables.product.prodname_unfurls %} se encuentra actualmente en beta y solo está disponible para su uso con GitHub Apps. Las características y los requisitos podrían cambiar en cualquier momento durante este periodo. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/pre-release-program/corsair-preview.md b/translations/es-ES/data/reusables/pre-release-program/corsair-preview.md new file mode 100644 index 0000000000000..df92902010cb7 --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/corsair-preview.md @@ -0,0 +1,9 @@ +{% note %} + +**Nota:** Para acceder a la API de {% data variables.product.prodname_unfurls %} durante el periodo de previsualización, debes proporcionar un [tipo de medios](/rest/overview/media-types) en el encabezado `Accept`: + +``` +application/vnd.github.corsair-preview+json +``` + +{% endnote %} diff --git a/translations/es-ES/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/es-ES/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md new file mode 100644 index 0000000000000..8bde96271631f --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota:** Los tokens de usuario con caducidad son actualmente parte del beta de tokens de usuario a servidor y están sujetos a cambios. Para participar en la característica beta de tokens de usuario a servidor con caducidad, consulta la sección "[Activar las características beta para las aplicaciones](/developers/apps/activating-beta-features-for-apps)". Para obtener más información, consulta la sección "[Tokens de acceso con caducidad de usuario a servidor para las GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)". + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/pre-release-program/fury-pre-release.md b/translations/es-ES/data/reusables/pre-release-program/fury-pre-release.md new file mode 100644 index 0000000000000..6101f9ee074e3 --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/fury-pre-release.md @@ -0,0 +1,11 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} +{% note %} + +**Nota:** Los Manifiestos de las {% data variables.product.prodname_github_app %}s se encuentran actualmente disponibles para que los desarrolladores los previsualicen. Para acceder a esta API durante el periodo de vista previa, debes proporcionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado de `Accept`: + +``` +application/vnd.github.fury-preview+json +``` + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/pre-release-program/machine-man-preview.md b/translations/es-ES/data/reusables/pre-release-program/machine-man-preview.md new file mode 100644 index 0000000000000..9b76263c667ae --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/machine-man-preview.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% note %} + +**Nota:** Para acceder a la API con tu GitHub App, debes proporcionar un [tipo de medios personalizado](/rest/overview/media-types) en el encabezado de `Accept` para tus solicitudes. + +`application/vnd.github.machine-man-preview+json` + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/pre-release-program/sailor-v-preview.md b/translations/es-ES/data/reusables/pre-release-program/sailor-v-preview.md new file mode 100644 index 0000000000000..1421642b9fb4a --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/sailor-v-preview.md @@ -0,0 +1,11 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +{% note %} + +**Nota:** Ahora puedes utilizar la API de REST para agregar una razón cuando fijas un informe de problemas y verás las razones de haberlo fijado en las respuestas que incluyan informes de problemas o solicitudes de extracción. También verás las razones de haberlo fijado en los eventos que se muestren como `locked`. Esta característica se encuentra disponible actualmente para que los desarrolladores la previsualicen. Consulta la [publicación del blog](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) para encontrar todos los detalles. Para acceder a esta característica, debes proprocionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado de `Accept`: + +``` +application/vnd.github.sailor-v-preview+json +``` + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/pre-release-program/starfox-preview.md b/translations/es-ES/data/reusables/pre-release-program/starfox-preview.md new file mode 100644 index 0000000000000..d9e02026ba022 --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/starfox-preview.md @@ -0,0 +1,11 @@ +{% note %} + +**Nota:** Los detalles de la tarjeta de proyectos ahora se meustran en las respuestas de la API de REST para los eventos de informes de problemas y línea de tiempo relacionados con el proyecto. Esta característica está ahora disponible para que los desarrolladores la previsualicen. Para obtener más detalles, consulta la [publicación del blog](https://developer.github.com/changes/2018-09-05-project-card-events). + +Para recibir el atributo `project_card`, los tableros de proyecto deben [habilitarse](/articles/disabling-project-boards-in-a-repository) para un repositorio, y debes proprocionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado `Accept`: + +``` +application/vnd.github.starfox-preview+json +``` + +{% endnote %} diff --git a/translations/es-ES/data/reusables/pre-release-program/suspend-installation-beta.md b/translations/es-ES/data/reusables/pre-release-program/suspend-installation-beta.md new file mode 100644 index 0000000000000..f500d74c609fc --- /dev/null +++ b/translations/es-ES/data/reusables/pre-release-program/suspend-installation-beta.md @@ -0,0 +1 @@ +El suspender una instalación de {% data variables.product.prodname_github_app %} se encuentra actualmente en beta y está sujeto a cambios. Antes de que puedas suspender una {% data variables.product.prodname_github_app %}, el propietario de ésta debe habilitar la suspeción de instalaciones al decidir integrarse en el beta. Para participar en la característica beta de suspención de instalaciones, consulta la sección "[Activar las características beta para las aplicaciones](/developers/apps/activating-beta-features-for-apps)". diff --git a/translations/es-ES/data/reusables/products/product-roadmap.md b/translations/es-ES/data/reusables/products/product-roadmap.md new file mode 100644 index 0000000000000..c5dbc5773a9bf --- /dev/null +++ b/translations/es-ES/data/reusables/products/product-roadmap.md @@ -0,0 +1 @@ +Para obtener más información sobre los planes y las características planeados, consulta la sección [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %}). diff --git a/translations/es-ES/data/reusables/products/which-product-to-use.md b/translations/es-ES/data/reusables/products/which-product-to-use.md new file mode 100644 index 0000000000000..29a81813d9a82 --- /dev/null +++ b/translations/es-ES/data/reusables/products/which-product-to-use.md @@ -0,0 +1,3 @@ +Si no estás seguro si {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, o ambos son la mejor opción para tu organización, contacta a {% data variables.contact.contact_enterprise_sales %}. + +Las organizaciones con 12 o más programadores normalmente se benefician más con {% data variables.product.prodname_enterprise %}. Si tu organización tiene 11 o menos desarrolladores, considera {% data variables.product.prodname_team %}. Para obtener más información, consulta los productos de "{% data variables.product.prodname_dotcom %}" diff --git a/translations/es-ES/data/reusables/profile/access_org.md b/translations/es-ES/data/reusables/profile/access_org.md new file mode 100644 index 0000000000000..36f9fc193c722 --- /dev/null +++ b/translations/es-ES/data/reusables/profile/access_org.md @@ -0,0 +1 @@ +1. En la parte izquierda de tu página de perfil, debajo de "Organizaciones", da clic en el icono de tu organización. ![iconos de organización](/assets/images/help/profile/profile_orgs_box.png) diff --git a/translations/es-ES/data/reusables/profile/access_profile.md b/translations/es-ES/data/reusables/profile/access_profile.md new file mode 100644 index 0000000000000..89abd24e1cffd --- /dev/null +++ b/translations/es-ES/data/reusables/profile/access_profile.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %}1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. + ![Foto de perfil](/assets/images/help/profile/top_right_avatar.png){% else %} +1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Profile photo](/assets/images/enterprise/settings/top_right_avatar.png){% endif %} diff --git a/translations/es-ES/data/reusables/profile/activity-overview-summary.md b/translations/es-ES/data/reusables/profile/activity-overview-summary.md new file mode 100644 index 0000000000000..b5edb397a4b16 --- /dev/null +++ b/translations/es-ES/data/reusables/profile/activity-overview-summary.md @@ -0,0 +1 @@ +Cuando habilitas la sección de resumen de actividades en tu perfil, las personas podrán ver más información acerca de los tipos de contribuciones que haces y los repositorios en donde tienes más actividad. Quien esté viendo solo podrá encontrar información del resumen de actividad sobre los repositorios en los cuales tengan permisos de lectura. Una vez habilitadas, las personas pueden filtrar tu gráfica de contribuciones y línea de tiempo de actividad para una organización específica. diff --git a/translations/es-ES/data/reusables/profile/enterprise_access_profile.md b/translations/es-ES/data/reusables/profile/enterprise_access_profile.md new file mode 100644 index 0000000000000..197c5a4e75f2d --- /dev/null +++ b/translations/es-ES/data/reusables/profile/enterprise_access_profile.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de {% data variables.product.prodname_ghe_server %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Foto de perfil](/assets/images/enterprise/settings/top_right_avatar.png) diff --git a/translations/es-ES/data/reusables/profile/profile-readme.md b/translations/es-ES/data/reusables/profile/profile-readme.md new file mode 100644 index 0000000000000..e7e8a0aa59378 --- /dev/null +++ b/translations/es-ES/data/reusables/profile/profile-readme.md @@ -0,0 +1 @@ +Si agregas un archivo de README a la raíz de un repositorio público con el mismo nombre que tu nombre de usuario, dicho README aparecerá automáticamente en tu página de perfil. Puedes editar el README de tu perfil con el Marcado Enriquecido de {% data variables.product.company_short %} para crear una sección personalizada en tu perfil. Para obtener más información, consulta la sección "[Administrar el README de tu perfil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". diff --git a/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md b/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md new file mode 100644 index 0000000000000..e87269f62d6dc --- /dev/null +++ b/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, debajo de la foto de perfil del usuario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Bloquear o reportar usuario**. ![Enlace para reportar o bloquear usuario](/assets/images/help/profile/profile-block-or-report-button.png) diff --git a/translations/es-ES/data/reusables/profile/user_profile_page_navigation.md b/translations/es-ES/data/reusables/profile/user_profile_page_navigation.md new file mode 100644 index 0000000000000..2e3835f5c34dd --- /dev/null +++ b/translations/es-ES/data/reusables/profile/user_profile_page_navigation.md @@ -0,0 +1 @@ +1. Visita la página de perfil de usuario. diff --git a/translations/es-ES/data/reusables/project-management/access-collaboration-settings.md b/translations/es-ES/data/reusables/project-management/access-collaboration-settings.md new file mode 100644 index 0000000000000..d0460c2736c12 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/access-collaboration-settings.md @@ -0,0 +1 @@ +1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, posteriormente, da clic en **Configuración**. ![Opción de configuración en menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-settings.png) diff --git a/translations/es-ES/data/reusables/project-management/add-collaborator.md b/translations/es-ES/data/reusables/project-management/add-collaborator.md new file mode 100644 index 0000000000000..f5e8cd27c3fc1 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/add-collaborator.md @@ -0,0 +1 @@ +10. En los resultados de la búsqueda, da clic en el nombre de usuario correcto y luego da clic en **Agregar colaborador**. diff --git a/translations/es-ES/data/reusables/project-management/add-column-new-project.md b/translations/es-ES/data/reusables/project-management/add-column-new-project.md new file mode 100644 index 0000000000000..d56d8abcfb385 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/add-column-new-project.md @@ -0,0 +1 @@ +1. En tu nuevo tablero de proyecto, para agregar tu primera columna, **Agrega una columna**. ![Botón para agregar columna en un tablero de proyecto vacío](/assets/images/help/projects/add-column.png) diff --git a/translations/es-ES/data/reusables/project-management/add-more-columns.md b/translations/es-ES/data/reusables/project-management/add-more-columns.md new file mode 100644 index 0000000000000..dfc1b4f0bdd6f --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/add-more-columns.md @@ -0,0 +1 @@ +1. Agrega columnas para que se adapten a tu flujo de trabajo. diff --git a/translations/es-ES/data/reusables/project-management/automate-project-board-permissions.md b/translations/es-ES/data/reusables/project-management/automate-project-board-permissions.md new file mode 100644 index 0000000000000..67aeb85afd3d4 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/automate-project-board-permissions.md @@ -0,0 +1 @@ +Para configurar flujos de trabajo automáticos para un tablero de proyecto de un repositorio, debes tener acceso de escritura al mismo. Los miembros y propietarios de una organización pueden configurar flujos de trabajo automáticos en un tablero de proyecto que contemple a toda la organización. diff --git a/translations/es-ES/data/reusables/project-management/cascading-permissions.md b/translations/es-ES/data/reusables/project-management/cascading-permissions.md new file mode 100644 index 0000000000000..95f9c64fe69db --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/cascading-permissions.md @@ -0,0 +1 @@ +Si una persona cuenta con múltiples avenidas de acceso a un tablero de proyecto de una organización (individualmente, a través de un equipo o como miembro de una organización), el nivel de permiso más alto del tablero de proyecto invalida los niveles de permiso más bajos. diff --git a/translations/es-ES/data/reusables/project-management/choose-template.md b/translations/es-ES/data/reusables/project-management/choose-template.md new file mode 100644 index 0000000000000..94744bc70ea09 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/choose-template.md @@ -0,0 +1 @@ +5. Opcionalmente, para agregar una plantilla a tu tablero de proyecto, utiliza el menú desplegable de **Plantilla:** y da clic en alguna de las opciones. ![Menú desplegable mostrando las opciones de plantilla para el tablero de proyecto](/assets/images/help/projects/project_board_template_drop_down_menu.png) diff --git a/translations/es-ES/data/reusables/project-management/choose-visibility.md b/translations/es-ES/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..a9c327e7ac1f3 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. Para obtener más información, consulta "[Cambiar la visibilidad del tablero de proyecto](/github/managing-your-work-on-github/changing-project-board-visibility)". ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/es-ES/data/reusables/project-management/click-create-column.md b/translations/es-ES/data/reusables/project-management/click-create-column.md new file mode 100644 index 0000000000000..bb25125540935 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/click-create-column.md @@ -0,0 +1 @@ +1. Da clic en **Crear columna**. diff --git a/translations/es-ES/data/reusables/project-management/click-edit-sidebar-menu-project-board.md b/translations/es-ES/data/reusables/project-management/click-edit-sidebar-menu-project-board.md new file mode 100644 index 0000000000000..e28498488cbe8 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/click-edit-sidebar-menu-project-board.md @@ -0,0 +1 @@ +1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, posteriormente, da clic en **Editar**. ![Opción de editar en el menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-edit-settings.png) diff --git a/translations/es-ES/data/reusables/project-management/click-menu.md b/translations/es-ES/data/reusables/project-management/click-menu.md new file mode 100644 index 0000000000000..03cc44dc05cf6 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/click-menu.md @@ -0,0 +1 @@ +1. En la parte superior derecha del tablero de proyecto, da clic en {% octicon "three-bars" aria-label="The three-bars octicon" %}**Menu**. diff --git a/translations/es-ES/data/reusables/project-management/click-new-project.md b/translations/es-ES/data/reusables/project-management/click-new-project.md new file mode 100644 index 0000000000000..2f7382451ce46 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/click-new-project.md @@ -0,0 +1 @@ +1. Da clic en **Proyecto Nuevo**. ![Botón de proyecto nuevo](/assets/images/help/projects/new-project-button.png) diff --git a/translations/es-ES/data/reusables/project-management/collaborator-option.md b/translations/es-ES/data/reusables/project-management/collaborator-option.md new file mode 100644 index 0000000000000..2588a939da324 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/collaborator-option.md @@ -0,0 +1 @@ +8. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Opción de menú de colaboradores en la barra lateral izquierda](/assets/images/help/projects/project-board-collaborator-setting.png) diff --git a/translations/es-ES/data/reusables/project-management/collaborator-permissions.md b/translations/es-ES/data/reusables/project-management/collaborator-permissions.md new file mode 100644 index 0000000000000..15a7231e65af0 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/collaborator-permissions.md @@ -0,0 +1 @@ +11. Opcionalmente, junto al nombre del colaborador nuevo, utiliza el menú desplegable y da clic en el nivel de permiso que le quieras otorgar: **Read**, **Write**, o **Admin**. ![Menú desplegable de permisos de colaborador con opciones read, write y admin](/assets/images/help/projects/org-project-collaborators-choose-permissions.png) diff --git a/translations/es-ES/data/reusables/project-management/confirm-label-deletion.md b/translations/es-ES/data/reusables/project-management/confirm-label-deletion.md new file mode 100644 index 0000000000000..ab1018eb0f2fa --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/confirm-label-deletion.md @@ -0,0 +1 @@ + 1. Lee la advertencia y da clic en **OK**. diff --git a/translations/es-ES/data/reusables/project-management/copy-project-boards.md b/translations/es-ES/data/reusables/project-management/copy-project-boards.md new file mode 100644 index 0000000000000..6ab2e21a80640 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/copy-project-boards.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +También puedes copiar un tablero de proyecto para reutilizar sus configuraciones personalizadas en proyectos similares. Para obtener más información, consulta "[Copiar un tablero de proyecto](/articles/copying-a-project-board)". +{% endif %} diff --git a/translations/es-ES/data/reusables/project-management/create-label.md b/translations/es-ES/data/reusables/project-management/create-label.md new file mode 100644 index 0000000000000..a14085126a4f4 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/create-label.md @@ -0,0 +1 @@ + 1. Para guardar la nueva etiqueta, haz clic en **Crear etiqueta**. diff --git a/translations/es-ES/data/reusables/project-management/create-project-button.md b/translations/es-ES/data/reusables/project-management/create-project-button.md new file mode 100644 index 0000000000000..051c367980149 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/create-project-button.md @@ -0,0 +1 @@ +1. Da clic en **Crear proyecto**. diff --git a/translations/es-ES/data/reusables/project-management/create-project-name-description.md b/translations/es-ES/data/reusables/project-management/create-project-name-description.md new file mode 100644 index 0000000000000..de2edcc0e3304 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/create-project-name-description.md @@ -0,0 +1 @@ +1. Teclea un nombre y descripción para tu tablero de proyecto. ![Campos para nombre y descripción de proyecto y botón de crear proyecto](/assets/images/help/projects/name-description-create-button.png) diff --git a/translations/es-ES/data/reusables/project-management/delete-label.md b/translations/es-ES/data/reusables/project-management/delete-label.md new file mode 100644 index 0000000000000..a8e8b751087c9 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/delete-label.md @@ -0,0 +1 @@ + 1. En la lista de etiquetas, a la derecha de la etiqueta que quieres borrar, da clic en **Borrar**. diff --git a/translations/es-ES/data/reusables/project-management/edit-in-project.md b/translations/es-ES/data/reusables/project-management/edit-in-project.md new file mode 100644 index 0000000000000..a7379a106cd50 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/edit-in-project.md @@ -0,0 +1 @@ +Puedes ver las propuestas y solicitudes de extracción en tu tablero de proyecto y hacerles ediciones leves haciendo clic en el título de la propuesta o solicitud de extracción. diff --git a/translations/es-ES/data/reusables/project-management/edit-label.md b/translations/es-ES/data/reusables/project-management/edit-label.md new file mode 100644 index 0000000000000..947c45c8ba1a4 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/edit-label.md @@ -0,0 +1 @@ + 1. En la lista de etiquetas, a la derecha de la etiqueta que quieres editar, da clic en **Editar**. diff --git a/translations/es-ES/data/reusables/project-management/edit-project-columns.md b/translations/es-ES/data/reusables/project-management/edit-project-columns.md new file mode 100644 index 0000000000000..fef4685dda60c --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/edit-project-columns.md @@ -0,0 +1,5 @@ +{% tip %} + +**Tip:** Para editar o eliminar una columna de tu tablero de proyecto, en la esquina superior derecha de la columna, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md b/translations/es-ES/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md new file mode 100644 index 0000000000000..e2a658482f2ca --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md @@ -0,0 +1 @@ +Para obtener más información acerca de los atajos de teclado, consulta la sección "Tableros de Proyecto" en "[Atajos de teclado](/articles/keyboard-shortcuts/#project-boards)". diff --git a/translations/es-ES/data/reusables/project-management/label-color-randomizer.md b/translations/es-ES/data/reusables/project-management/label-color-randomizer.md new file mode 100644 index 0000000000000..0e17b2fabea6f --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/label-color-randomizer.md @@ -0,0 +1 @@ +1. De manera opcional, para personalizar el color de tu etiqueta, edita el número hexadecimal, o da clic en el botón de actualización para obtener otra selección aleatoria. ![Emite un nuevo color de etiqueta cuando actualiza](/assets/images/help/issues/issues-color-refresh.png) diff --git a/translations/es-ES/data/reusables/project-management/label-description.md b/translations/es-ES/data/reusables/project-management/label-description.md new file mode 100644 index 0000000000000..4f582a8146ada --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/label-description.md @@ -0,0 +1 @@ +1. Debajo de "Descripción", teclea una descripción para ayudar a que los demás entiendan y utilicen tu etiqueta. ![Campo para teclear una descripción de etiqueta](/assets/images/help/issues/label-description-field.png) diff --git a/translations/es-ES/data/reusables/project-management/labels.md b/translations/es-ES/data/reusables/project-management/labels.md new file mode 100644 index 0000000000000..8240097a3c74f --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/labels.md @@ -0,0 +1 @@ +1. Sobre la lista de informes de problemas o solicitudes de extracción, da clic en **Etiquetas**. ![Pestaña de etiquetas en la página de informes de problemas o solicitudes de extracción de un repositorio](/assets/images/help/issues/issues_labels_button.png) diff --git a/translations/es-ES/data/reusables/project-management/link-repos-to-project-board.md b/translations/es-ES/data/reusables/project-management/link-repos-to-project-board.md new file mode 100644 index 0000000000000..33208c0dae2ff --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/link-repos-to-project-board.md @@ -0,0 +1 @@ +Puedes vincular hasta 25 repositorios a tu tablero de proyecto de organización o de usuario. Vincular repositorios facilita el agregar informes de problemas y solicitudes de extracción desde dichos repositorios a tu tablero de proyecto utilizando las **Tarjetas de adición de {% octicon "plus" aria-label="The Plus icon" %}** o desde la barra lateral del informe de problemas o de la solicitud de extracción. diff --git a/translations/es-ES/data/reusables/project-management/linked-repositories.md b/translations/es-ES/data/reusables/project-management/linked-repositories.md new file mode 100644 index 0000000000000..ed88bee9ce84a --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/linked-repositories.md @@ -0,0 +1 @@ +1. Opcionalmente, debajo de **Repositorios vinculados**, busca un repositorio que te gustaría vincular a tu tablero de proyecto. ![Campo de búsqueda para vincular repositorios](/assets/images/help/projects/search-to-link-repository-on-create.png) diff --git a/translations/es-ES/data/reusables/project-management/milestones.md b/translations/es-ES/data/reusables/project-management/milestones.md new file mode 100644 index 0000000000000..2e8e655a891ba --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/milestones.md @@ -0,0 +1 @@ +1. Junto al campo de búsqueda, da clic en **Hitos**. ![Botón de propuestas del hito](/assets/images/help/issues/issues_milestone_button.png) diff --git a/translations/es-ES/data/reusables/project-management/name-label.md b/translations/es-ES/data/reusables/project-management/name-label.md new file mode 100644 index 0000000000000..2935e37fc6dca --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/name-label.md @@ -0,0 +1 @@ +1. Debajo de "Nombre de etiqueta", teclea un nombre para tu etiqueta. ![Campo para teclear un nombre de etiqueta](/assets/images/help/issues/Issues-Label-Create.png) diff --git a/translations/es-ES/data/reusables/project-management/name-project-board-column.md b/translations/es-ES/data/reusables/project-management/name-project-board-column.md new file mode 100644 index 0000000000000..32f4c7f709471 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/name-project-board-column.md @@ -0,0 +1 @@ +1. Debajo de "Nombre de columna", teclea el nombre de la columna que quieres crear. ![Teclea un nombre de columna](/assets/images/help/projects/type-column-name.png) diff --git a/translations/es-ES/data/reusables/project-management/project-board-import-with-api.md b/translations/es-ES/data/reusables/project-management/project-board-import-with-api.md new file mode 100644 index 0000000000000..fab93a787a852 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/project-board-import-with-api.md @@ -0,0 +1 @@ +Puedes utilizar la API de {% data variables.product.prodname_dotcom %} para importar un tablero de proyecto. Para obtener más información, consulta la mutación "[importProject](/graphql/reference/mutations#importproject/)". diff --git a/translations/es-ES/data/reusables/project-management/project-board-permissions.md b/translations/es-ES/data/reusables/project-management/project-board-permissions.md new file mode 100644 index 0000000000000..e6cf167a44bb3 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/project-board-permissions.md @@ -0,0 +1,3 @@ +- **Read** (Lectura), es el que otorga permiso a las personas para que vean un tablero de proyecto. +- **Write** (Escritura), es el que otorga permiso a las personas para que vean un tablero de proyecto, vinculen repositorios con un tablero de proyecto e interactúen con un tablero de proyecto. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". +- **Admin** (Administración), es el que otorga permiso a las personas para que vean un tablero de proyecto, interactúen con un tablero de proyecto, administren los parámetros de un tablero de proyecto y administren el acceso de otras personas al tablero de proyecto. diff --git a/translations/es-ES/data/reusables/project-management/project-board-visibility.md b/translations/es-ES/data/reusables/project-management/project-board-visibility.md new file mode 100644 index 0000000000000..a39023f3f8cc7 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/project-board-visibility.md @@ -0,0 +1 @@ +Por defecto, tu tablero de proyecto es privado y solo está visible para las personas con permisos de lectura, escritura o administración para el tablero de proyecto. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/es-ES/data/reusables/project-management/project-note-more-options.md b/translations/es-ES/data/reusables/project-management/project-note-more-options.md new file mode 100644 index 0000000000000..baf7065881299 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/project-note-more-options.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de las notas, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.![Icono de kebab horizontal en la esquina superior derecha de la nota](/assets/images/help/projects/note-more-options.png) diff --git a/translations/es-ES/data/reusables/project-management/project-progress-locations.md b/translations/es-ES/data/reusables/project-management/project-progress-locations.md new file mode 100644 index 0000000000000..95440f5c8dee6 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/project-progress-locations.md @@ -0,0 +1 @@ +Si se habilita el rastreo de progreso, aparecerá una barra de progreso sobre el tablero de proyecto, en la página de listado del proyecto, en la barra lateral de la propuesta, y en las referencias del proyecto en otros tableros de proyecto. diff --git a/translations/es-ES/data/reusables/project-management/remove-collaborator.md b/translations/es-ES/data/reusables/project-management/remove-collaborator.md new file mode 100644 index 0000000000000..217a1fec5bf42 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/remove-collaborator.md @@ -0,0 +1 @@ +4. Junto al colaborador que quieres eliminar, da clic en **X**. ![Icono de eliminación "X" junto al nombre de usuario del colaborador](/assets/images/help/projects/remove-project-board-collaborator.png) diff --git a/translations/es-ES/data/reusables/project-management/resync-automation.md b/translations/es-ES/data/reusables/project-management/resync-automation.md new file mode 100644 index 0000000000000..2277ccfcf4026 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/resync-automation.md @@ -0,0 +1 @@ +Cuando cierras un tablero de proyecto, se pausará cualquier automatización de flujo de trabajo configurada para el mismo. Si vuelves a abrir un tablero de proyecto, tienes la opción de sincronizar la automatización, lo que actualiza la posición de las tarjetas en el tablero de acuerdo con los parámetros de automatización configurados para el tablero. Para obtener más información, consulta la sección "[Reabrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board)" o "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". diff --git a/translations/es-ES/data/reusables/project-management/save-label.md b/translations/es-ES/data/reusables/project-management/save-label.md new file mode 100644 index 0000000000000..e2d07f2ce4428 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/save-label.md @@ -0,0 +1 @@ + 1. Haz clic en **Guardar cambios**. diff --git a/translations/es-ES/data/reusables/project-management/select-automation-options-new-column.md b/translations/es-ES/data/reusables/project-management/select-automation-options-new-column.md new file mode 100644 index 0000000000000..fd8568027cc67 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/select-automation-options-new-column.md @@ -0,0 +1 @@ +1. Selecciona las automatizaciones del flujo de trabajo que deseas configurar para la columna. ![Lista de opciones para automatizar la columna](/assets/images/help/projects/select-automation-options-new-column.png) diff --git a/translations/es-ES/data/reusables/project-management/select-column-preset.md b/translations/es-ES/data/reusables/project-management/select-column-preset.md new file mode 100644 index 0000000000000..f77389cee78b3 --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/select-column-preset.md @@ -0,0 +1 @@ +1. Opcionalmente, debajo de "Automatización", selecciona una configuración predeterminada utilizando el menú desplegable. ![Selecciona preestablecer la automatización desde el menú](/assets/images/help/projects/select-automation.png) diff --git a/translations/es-ES/data/reusables/project-management/select-project.md b/translations/es-ES/data/reusables/project-management/select-project.md new file mode 100644 index 0000000000000..9bb5104d03b7f --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/select-project.md @@ -0,0 +1 @@ +1. En la lista de proyectos, da clic en el nombre del tablero de proyecto. ![Selecciona el proyecto](/assets/images/help/projects/select-project.png) diff --git a/translations/es-ES/data/reusables/project-management/use-automated-template.md b/translations/es-ES/data/reusables/project-management/use-automated-template.md new file mode 100644 index 0000000000000..84e39f88df13c --- /dev/null +++ b/translations/es-ES/data/reusables/project-management/use-automated-template.md @@ -0,0 +1 @@ +Puedes utilizar una plantilla de tablero de proyecto para crear un tablero de proyecto que ya tenga configurada la automatización. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards#templates-for-project-boards)." diff --git a/translations/es-ES/data/reusables/projects/disabled-projects.md b/translations/es-ES/data/reusables/projects/disabled-projects.md new file mode 100644 index 0000000000000..f7e175a7e12c9 --- /dev/null +++ b/translations/es-ES/data/reusables/projects/disabled-projects.md @@ -0,0 +1 @@ +Únicamente verás este evento en las respuestas cuando se [habiliten](/articles/disabling-project-boards-in-a-repository) los tableros de proyecto en el repositorio. diff --git a/translations/es-ES/data/reusables/pull_requests/auto-merge-release-phase.md b/translations/es-ES/data/reusables/pull_requests/auto-merge-release-phase.md new file mode 100644 index 0000000000000..e10a760711f7c --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/auto-merge-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** La fusión automática para las solicitudes de cambios se encuentra actualmente en beta y está sujeta a cambios. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pull_requests/automatically-delete-branches.md b/translations/es-ES/data/reusables/pull_requests/automatically-delete-branches.md new file mode 100644 index 0000000000000..9e827fb2f33ef --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/automatically-delete-branches.md @@ -0,0 +1 @@ +Puedes hacer que se eliminen automáticamente ramas centrales después de que se fusionen solicitudes de extracción en tu repositorio. Para obtener más información, consulta la sección "[Administrar el borrado automático de ramas](/articles/managing-the-automatic-deletion-of-branches)". diff --git a/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md new file mode 100644 index 0000000000000..93f3863523ea6 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md @@ -0,0 +1 @@ +Puedes enlazar una solicitud de cambios con una propuesta para{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} mostrar que se está corrigiendo un error y para{% endif %} cerrar la propuesta automáticamente cuando alguien fusione la solicitud de cambios. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". diff --git a/translations/es-ES/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md b/translations/es-ES/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md new file mode 100644 index 0000000000000..e5c2f5191e78e --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md @@ -0,0 +1 @@ +1. Recolecta el nombre y la dirección de correo electrónico de cada coautor.{% if currentVersion == "free-pro-team@latest" %} Si una persona elige mantener su dirección de correo electrónico como privada, debes utilizar su dirección de correo electrónico de tipo `no-reply` que proporcionó {% data variables.product.product_name %} para proteger su privacidad.{% endif %} diff --git a/translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md b/translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md new file mode 100644 index 0000000000000..09fddb9c9fb4a --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md @@ -0,0 +1 @@ +Puedes configurar las opciones de fusión para una solicitud de extracción en {% data variables.product.product_location %} para que éstas satisfagan las necesidades de tu flujo de trabajo y tus preferencias para administrar el historial de Git. Para obtener más información, consulta la sección "[Configurar las fusiones de solicitudes de extracción](/articles/configuring-pull-request-merges)". diff --git a/translations/es-ES/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md b/translations/es-ES/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md new file mode 100644 index 0000000000000..1a25a1bdf1a02 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md @@ -0,0 +1 @@ +1. Decide si quieres mantener únicamente los cambios de tu rama, mantener únicamente los cambios de las demás ramas, o hacer un cambio nuevo, el cual puede incorporar cambios de ambas ramas. Borra los marcadores de conflicto `<<<<<<<`, `=======`, `>>>>>>>` y realiza los cambios que quieras en la fusión final. diff --git a/translations/es-ES/data/reusables/pull_requests/default-commit-message-squash-merge.md b/translations/es-ES/data/reusables/pull_requests/default-commit-message-squash-merge.md new file mode 100644 index 0000000000000..ae613d84863a4 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/default-commit-message-squash-merge.md @@ -0,0 +1 @@ +Para obtener información acerca de los mensajes de confirmación predeterminados para las fusiones de combinación, consulta "[Acerca de las fusiones de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#merge-message-for-a-squash-merge)." diff --git a/translations/es-ES/data/reusables/pull_requests/default_merge_option.md b/translations/es-ES/data/reusables/pull_requests/default_merge_option.md new file mode 100644 index 0000000000000..d504b9634f0aa --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/default_merge_option.md @@ -0,0 +1,5 @@ +Cuando haces clic en la opción predeterminada **Merge pull request** (Fusionar solicitud de extracción) en una solicitud de extracción de {% data variables.product.product_location %}, todas las confirmaciones de la rama de característica se agregan a la rama de base en una confirmación de fusión. La solicitud de extracción se fusiona usando [la opción `--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge). + +Para fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) sobre el repositorio. + +![standard-merge-commit-diagram](/assets/images/help/pull_requests/standard-merge-commit-diagram.png) diff --git a/translations/es-ES/data/reusables/pull_requests/dismiss_review.md b/translations/es-ES/data/reusables/pull_requests/dismiss_review.md new file mode 100644 index 0000000000000..119e0f10a0859 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/dismiss_review.md @@ -0,0 +1 @@ +Si una solicitud de extracción ha cambiado desde que fue revisada y la persona que solicitó los cambios no se encuentra disponible para realizar una revisión en la que estos cambios se aprueben, los administradores del repositorio o las personas con acceso de escritura pueden descartar la revisión. diff --git a/translations/es-ES/data/reusables/pull_requests/mark-ready-review.md b/translations/es-ES/data/reusables/pull_requests/mark-ready-review.md new file mode 100644 index 0000000000000..f34b5999ebbd8 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/mark-ready-review.md @@ -0,0 +1 @@ +Cuando estés listo para obtener retroalimentación sobre tu solicitud de extracción, puedes marcar tu borrador de solicitud de extracción como listo para revisión. Con esto, solicitarás las revisiones de cualquier propietario de código en cuestión. diff --git a/translations/es-ES/data/reusables/pull_requests/perms-to-open-pull-request.md b/translations/es-ES/data/reusables/pull_requests/perms-to-open-pull-request.md new file mode 100644 index 0000000000000..65e3192495d65 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/perms-to-open-pull-request.md @@ -0,0 +1,9 @@ +{% if currentVersion == "free-pro-team@latest" %} + +{% note %} + +**Nota**: Para abrir una solicitud de extracción en un repositorio público, debes tener acceso de escritura en el encabezado de la rama origen o, para los repositorios que pertenecen a una organización, debes ser miembro de la organización propietaria del mismo para hacerlo. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md new file mode 100644 index 0000000000000..fcf08004cb057 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -0,0 +1,7 @@ +{% note %} + +**Notas:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Para que aparezcan en el gráfico de contribución de tu perfil, las confirmaciones de confirmación conjunta deben reunir los mismos criterios que las confirmaciones de un único autor.{% endif %} +- Cuando se cambian de base las confirmaciones, los autores originales de la confirmación y la persona que cambió de base las confirmaciones, ya sea en la línea de comando o en la {% data variables.product.product_location %}, recibe crédito de contribución. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/pull_requests/re-request-review.md b/translations/es-ES/data/reusables/pull_requests/re-request-review.md new file mode 100644 index 0000000000000..97fa4ea166337 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/re-request-review.md @@ -0,0 +1 @@ +Puedes volver a solicitar una revisión, por ejemplo, después de que hayas hecho cambios sustanciales a tu solicitud de cambios. Para solicitar que un revisor haga una revisión nueva, en la barra lateral de la pestaña de **Conversación**, da clic en el icono de {% octicon "sync" aria-label="The sync icon" %}. diff --git a/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md new file mode 100644 index 0000000000000..1c7d07ad87e9a --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -0,0 +1,7 @@ +Cuando seleccionas la opción **Rebase and merge** (Cambiar de base y fusionar) en la {% data variables.product.product_location %}, todas las confirmaciones de la rama de tema (o rama de encabezado) se agregan a la rama de base por separado sin una confirmación de fusión. Las solicitudes de extracción con confirmaciones con cambio de base se fusionan usando la [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge) (opción de avance rápido). + +Para cambiar de base y fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) en el repositorio, y el repositorio debe [permitir la fusión de cambio de base](/articles/configuring-commit-rebasing-for-pull-requests/). + +El comportamiento de cambio de base y de fusión en {% data variables.product.product_name %} varía levemente con respecto a `git rebase`. El cambio de base y la fusión en {% data variables.product.prodname_dotcom %} siempre actualizarán la información de la persona que confirma el cambio y crearán nuevas SHA de confirmación, mientras que el `git rebase` externo a {% data variables.product.prodname_dotcom %} no cambia la información de la persona que confirma el cambio cuando ocurre el cambio de base superponiendo un compromiso de antepasado. Para obtener más información sobre `git rebase`, consulta [el capítulo "Git rebase" del libro _Pro Git_](https://git-scm.com/docs/git-rebase). + +Para obtener una representación visual de `git rebase`, consulta [el capítulo "Ramas de Git - Cambio de base" del libro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/es-ES/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/es-ES/data/reusables/pull_requests/required-checks-must-pass-to-merge.md new file mode 100644 index 0000000000000..0db583ae97952 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -0,0 +1 @@ +Si un repositorio requiere verificaciones de estado, éstas deben pasar antes de que fusiones tu rama con la rama protegida. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". diff --git a/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md new file mode 100644 index 0000000000000..3526e39a78da3 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -0,0 +1 @@ +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/es-ES/data/reusables/pull_requests/resolving-conversations.md b/translations/es-ES/data/reusables/pull_requests/resolving-conversations.md new file mode 100644 index 0000000000000..55f9e1b93bb83 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/resolving-conversations.md @@ -0,0 +1,13 @@ +### Resolver conversaciones + +Puedes resolver una conversación en una solicitud de extracción si abriste la solicitud de extracción o si tienes acceso de escritura al repositorio en el que se abrió la solicitud de extracción. + +Para indicar que se completó una conversación en la pestaña de **Archivos cambiados**, da clic en **Resolver conversación**. + +![Conversación de solicitud de extracción con botón Resolve conversation (Resolver conversación)](/assets/images/help/pull_requests/conversation-with-resolve-button.png) + +Toda la conversación se colapsará y se marcará como resuelta, y será más sencillo encontrar conversaciones que se deban seguir considerando. + +![Conversación resuelta](/assets/images/help/pull_requests/resolved-conversation.png) + +Si la sugerencia en un comentario está fuera del alcance de tu solicitud de extracción, puedes abrir un nuevo informe de problemas que rastree la retroalimientación y se vincule con el comentario original. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". diff --git a/translations/es-ES/data/reusables/pull_requests/retargeted-on-branch-deletion.md b/translations/es-ES/data/reusables/pull_requests/retargeted-on-branch-deletion.md new file mode 100644 index 0000000000000..69fe3e0fd8e71 --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/retargeted-on-branch-deletion.md @@ -0,0 +1 @@ +Si borras una rama de encabezado después de haber fusionado su solicitud de extracción, {% data variables.product.prodname_dotcom %} verificará cualquier solicitud de extracción abierta en el mismo repositorio que especifique la rama borrada como su rama base. {% data variables.product.prodname_dotcom %} actualiza automáticamente cualquier solicitud de extracción, cambiando su rama base a la rama base de la solicitud de extracción que se ha fusionado. diff --git a/translations/es-ES/data/reusables/pull_requests/squash_and_merge_summary.md b/translations/es-ES/data/reusables/pull_requests/squash_and_merge_summary.md new file mode 100644 index 0000000000000..302b1153e6e6a --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/squash_and_merge_summary.md @@ -0,0 +1,7 @@ +Cuando seleccionas la opción **Squash and merge** (Combinar y fusionar) en una solicitud de extracción en la {% data variables.product.product_location %}, las confirmaciones de la solicitud de extracción se combinan en una única confirmación. En lugar de ver todas las confirmaciones individuales de un contribuyente de una rama de tema, las confirmaciones se combinan en una confirmación y se fusionan en la rama predeterminada. Las solicitudes de extracción con confirmaciones combinadas se fusionan usando la [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge) (opción de avance rápido). + +Para combinar y fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) en el repositorio, y el repositorio debe [permitir la fusión de combinaciones](/articles/configuring-commit-squashing-for-pull-requests/). + +![commit-squashing-diagram](/assets/images/help/pull_requests/commit-squashing-diagram.png) + +Puedes combinar y fusionar para crear un historial Git más optimizado en tu repositorio. Los compromisos de trabajo en curso son útiles cuando se trabaja en una rama de característica, pero no son tan importantes para retenerlos en el historial Git. Si combinas estas confirmaciones en una única confirmación al fusionar con la rama predeterminada, puedes conservar los cambios originales usando un historial Git claro. diff --git a/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md b/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md new file mode 100644 index 0000000000000..9c4ceacd247ff --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Puedes configurar una solicitud de cambios para que se fusione automáticamente cuando se cumplan todos los requisitos de fusión. Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md b/translations/es-ES/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md new file mode 100644 index 0000000000000..c412bd6107fed --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md @@ -0,0 +1 @@ +Los recordatorios programados ayudan a los equipos en enfocarse en las solicitudes de revisión más importantes que requieren su atención. Los recordatorios programados para las solicitudes de extracción enviarán un mensaje a tu equipo en Slack en una hora específica, el cual incluirá todas las solicitudes de extracción que tú o tu equipo estén pendientes de revisar. Por ejemplo, puedes crear un recordatorio programado para mandar un mensaje al canal principal de comunicación en Slack, incluyendo todas las solicitudes de extracción abiertas en las cuales se necesite la revisión del equipo, cada miércoles a las 9:00 a.m. diff --git a/translations/es-ES/data/reusables/reminders/add-reminder.md b/translations/es-ES/data/reusables/reminders/add-reminder.md new file mode 100644 index 0000000000000..ae3e5d2d366ad --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/add-reminder.md @@ -0,0 +1 @@ +1. Debajo de "Recordatorios programados", da clic en **Agregar tu primer recordatorio**. ![Botón de agregar recordatorio](/assets/images/help/settings/scheduled-reminders-add-button.png) diff --git a/translations/es-ES/data/reusables/reminders/approved-prs.md b/translations/es-ES/data/reusables/reminders/approved-prs.md new file mode 100644 index 0000000000000..a54f1ad5e72e4 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/approved-prs.md @@ -0,0 +1 @@ +1. Opcionalmente, para apagar los recordatorios programados para las solicitudes de extracción que ya se han revisado y aprobado, selecciona **Ignorar las solicitudes de extracción aprobadas**. Posteriormente, da clic en **Ignorar si tiene 1 o más aprobaciones** para escoger cuántas aprobaciones debe tener una solicitud de extracción para que se le ingnore. ![Casilla de ignorar solicitudes de extracción aprobadas](/assets/images/help/settings/scheduled-reminders-ignore-approved-prs.png) diff --git a/translations/es-ES/data/reusables/reminders/author-reviews.md b/translations/es-ES/data/reusables/reminders/author-reviews.md new file mode 100644 index 0000000000000..375c99f8e6506 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/author-reviews.md @@ -0,0 +1 @@ +1. De forma opcional, para enviar recordatorios a los autores de la solicitud de extracción después de que se hayan completado las solicitudes de revisión, selecciona **Recordar a los autores después de las revisiones** y elige la cantidad de revisiones requeridas antes de que se envíe un recordatorio. ![Casilla de recordar a los autores después de la revisión](/assets/images/help/settings/scheduled-reminders-remind-authors.png) diff --git a/translations/es-ES/data/reusables/reminders/authorize-slack.md b/translations/es-ES/data/reusables/reminders/authorize-slack.md new file mode 100644 index 0000000000000..40416aa2f0b62 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/authorize-slack.md @@ -0,0 +1 @@ +1. Debajo de "Espacio de trabajo de Slack", da clic en **Autorizar espacio de trabajo de Slack** y sigue las instrucciones. ![Botón de Autorizar espacio de trabajo de Slack](/assets/images/help/settings/scheduled-reminders-authorize-slack.png) diff --git a/translations/es-ES/data/reusables/reminders/create-reminder.md b/translations/es-ES/data/reusables/reminders/create-reminder.md new file mode 100644 index 0000000000000..4ab80323d91c3 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/create-reminder.md @@ -0,0 +1 @@ +1. Da clic en **Crear recordatorio**. diff --git a/translations/es-ES/data/reusables/reminders/days-dropdown.md b/translations/es-ES/data/reusables/reminders/days-dropdown.md new file mode 100644 index 0000000000000..796c064a4b12a --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/days-dropdown.md @@ -0,0 +1 @@ +1. Debajo de "Días", da clic en **Días de la semana**{% octicon "triangle-down" aria-label="The down triangle icon" %} para seleccionar uno o más días en los que quieras recibir recordatorios programados. ![Menú desplegable de días](/assets/images/help/settings/scheduled-reminders-days.png) diff --git a/translations/es-ES/data/reusables/reminders/delete.md b/translations/es-ES/data/reusables/reminders/delete.md new file mode 100644 index 0000000000000..e38f239283734 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/delete.md @@ -0,0 +1,2 @@ +1. Al final del la página, da clic en **Borrar este recordatorio**. ![Boton de borrar un recordatorio programado](/assets/images/help/settings/scheduled-reminders-delete.png) +1. Para confirmar que quieres borrar el recordatorio programado, da clic en **OK**. diff --git a/translations/es-ES/data/reusables/reminders/edit-existing.md b/translations/es-ES/data/reusables/reminders/edit-existing.md new file mode 100644 index 0000000000000..c1be9e16fb643 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/edit-existing.md @@ -0,0 +1 @@ +1. Junto al recordatorio programado que quieras actualizar, da clic en **Editar**. ![Editar el recordatorio programado existente](/assets/images/help/settings/scheduled-reminders-edit-existing.png) diff --git a/translations/es-ES/data/reusables/reminders/edit-page.md b/translations/es-ES/data/reusables/reminders/edit-page.md new file mode 100644 index 0000000000000..5be33e81c05f1 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/edit-page.md @@ -0,0 +1 @@ +1. Haz uno o más cambios a tu recordatorio programado. diff --git a/translations/es-ES/data/reusables/reminders/ignore-drafts.md b/translations/es-ES/data/reusables/reminders/ignore-drafts.md new file mode 100644 index 0000000000000..c312dcae87981 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/ignore-drafts.md @@ -0,0 +1 @@ +1. Opcionalmente, para excluir las solicitudes de extracción de los recordatorios programados, selecciona **Ignorar borradores**. Para obtener más información, consulta la sección "[Borradores de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". ![Casilla de ignorar borradores de solicitudes de extracción](/assets/images/help/settings/scheduled-reminders-ignore-drafts.png) diff --git a/translations/es-ES/data/reusables/reminders/ignored-labels.md b/translations/es-ES/data/reusables/reminders/ignored-labels.md new file mode 100644 index 0000000000000..6bca7532c97a6 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/ignored-labels.md @@ -0,0 +1 @@ +1. Debajo de "etiquetas ignoradas", teclea una lista de etiquetas separadas por comas. Los recordatorios programados no incluirán ninguna solicitud de extracción que tenga una o más de estas etiquetas. ![Campo de etiquetas ignoradas](/assets/images/help/settings/scheduled-reminders-ignored-labels-field.png) diff --git a/translations/es-ES/data/reusables/reminders/ignored-terms.md b/translations/es-ES/data/reusables/reminders/ignored-terms.md new file mode 100644 index 0000000000000..b7ba011fb7978 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/ignored-terms.md @@ -0,0 +1 @@ +1. Debajo de "condiciones ignoradas", teclea una lista separada por comas de los términos que podrían aparecer en los títulos de las solicitudes de extracción. Los recordatorios programados no incluirán ninguna solicitud de extracción que contenga uno o más de estos términos en sus títulos. ![Campo de términos ignorados](/assets/images/help/settings/scheduled-reminders-ignored-terms-field.png) diff --git a/translations/es-ES/data/reusables/reminders/min-age.md b/translations/es-ES/data/reusables/reminders/min-age.md new file mode 100644 index 0000000000000..d7ba6e67a14cc --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/min-age.md @@ -0,0 +1 @@ +1. Debajo de "Edad mínima", teclea la edad de una solicitud de extracción en horas. Los recordatorios programados no incluirán solicitudes de extracción que sean más recientes que éste límite de edad. ![Campo de etiquetas ignoradas](/assets/images/help/settings/scheduled-reminders-min-age-field.png) diff --git a/translations/es-ES/data/reusables/reminders/min-staleness.md b/translations/es-ES/data/reusables/reminders/min-staleness.md new file mode 100644 index 0000000000000..d2e1b402855ab --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/min-staleness.md @@ -0,0 +1 @@ +1. Debajo de "Tiempo mínimo transcurrido", teclea la hora de la última actividad en una solicitud de extracción, en horas. Los recordatorios programados no incluirán aquellas solicitudes de extracción cuya última actividad haya sido más reciente que el de esta hora. ![Campo de tiempo mínimo transcurrido](/assets/images/help/settings/scheduled-reminders-min-staleness-field.png) diff --git a/translations/es-ES/data/reusables/reminders/no-review-requests.md b/translations/es-ES/data/reusables/reminders/no-review-requests.md new file mode 100644 index 0000000000000..90a23c791d3f5 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/no-review-requests.md @@ -0,0 +1 @@ +1. Opcionalmente, para incluir únicamente las solicitudes de extracción en donde se solicita específicamente una revisión del equipo o de un miembro del equipo, selecciona **Requerir solicitudes de revisión**. Si no seleccionas esta opción, todas las solicitudes de extracción se incluirán en el recordatorio programado. ![Casilla de ignorar solicitudes de extracción sin solicitudes de revisión](/assets/images/help/settings/scheduled-reminders-prs-without-requests.png) diff --git a/translations/es-ES/data/reusables/reminders/real-time-alerts.md b/translations/es-ES/data/reusables/reminders/real-time-alerts.md new file mode 100644 index 0000000000000..7a56a422fadac --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/real-time-alerts.md @@ -0,0 +1 @@ +1. Opcionalmente, para recibir mensajes de Slack tan pronto sucedan ciertos eventos, selecciona **Habilitar alertas en tiempo real** y selecciona los eventos en los que éstas se recibirán. diff --git a/translations/es-ES/data/reusables/reminders/required-labels.md b/translations/es-ES/data/reusables/reminders/required-labels.md new file mode 100644 index 0000000000000..3947ba0b09962 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/required-labels.md @@ -0,0 +1 @@ +1. Debajo de "Etiquetas requeridas", teclea una lista de etiquetas separadas por comas. Los recordatorios programados solo incluirán las solicitudes de extracción que no se hayan ignorado en caso de que tengan una o más de estas etiquetas. ![Campo de etiquetas requeridas](/assets/images/help/settings/scheduled-reminders-required-labels-field.png) diff --git a/translations/es-ES/data/reusables/reminders/scheduled-reminders.md b/translations/es-ES/data/reusables/reminders/scheduled-reminders.md new file mode 100644 index 0000000000000..36fd7c9f38d31 --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/scheduled-reminders.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Recordatorios programados**. diff --git a/translations/es-ES/data/reusables/reminders/slack-channel.md b/translations/es-ES/data/reusables/reminders/slack-channel.md new file mode 100644 index 0000000000000..a9a40def0be6e --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/slack-channel.md @@ -0,0 +1 @@ +1. Debajo de "Canal de Slack", teclea el nombre del canal de Slack en donde quieres recibir notificaciones. ![Campo de canal de Slack](/assets/images/help/settings/scheduled-reminders-slack-channel.png) diff --git a/translations/es-ES/data/reusables/reminders/times-dropdowns.md b/translations/es-ES/data/reusables/reminders/times-dropdowns.md new file mode 100644 index 0000000000000..b26d121a65e3f --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/times-dropdowns.md @@ -0,0 +1 @@ +1. Debajo de "Seleccionar Horario(s)", da clic en **9:00 AM** {% octicon "triangle-down" aria-label="The down triangle icon" %} para seleccionar uno o más horarios en los cuales deseas recibir recordatorios programados. Opcionalmente, para cambiar tu huso horario, da clic en {% octicon "triangle-down" aria-label="The down triangle icon" %} junto a tu huso horario actual y selecciona un huso horario diferente. ![Menús desplegables de seleccionar horario(s)](/assets/images/help/settings/scheduled-reminders-times.png) diff --git a/translations/es-ES/data/reusables/reminders/tracked-repos.md b/translations/es-ES/data/reusables/reminders/tracked-repos.md new file mode 100644 index 0000000000000..30d62942abe5a --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/tracked-repos.md @@ -0,0 +1,5 @@ +1. Debajo de "Repositorios rastreados", escoge sobre cuáles repositorios te gustaría que el equipo recibiera recordatorios de las revisiones de solicitudes de rastreo. + - Para recibir recordatorios de todos los repositorios a los cuales tiene acceso el equipo elegido, da clic en **Todos los repositorios**. + - Para recibir recordatorios de un subconjunto de repositorios, da clic en **Seleccionar únicamente repositorios**, y luego selecciona uno o más repositorios a los que tenga acceso el equipo elegido. + + ![Elige los repositorios rastreados](/assets/images/help/settings/scheduled-reminders-tracked-repos.png) diff --git a/translations/es-ES/data/reusables/reminders/update-buttons.md b/translations/es-ES/data/reusables/reminders/update-buttons.md new file mode 100644 index 0000000000000..9fc787133ee8e --- /dev/null +++ b/translations/es-ES/data/reusables/reminders/update-buttons.md @@ -0,0 +1 @@ +1. Para guardar tus cambios, da clic en **Actualizar recordatorio**. Opcionalmente, para probar tus cambios mientras los actualizas, da clic en **Actualizar y probar recordatorio**. ![Botones de actualización](/assets/images/help/settings/scheduled-reminders-update-buttons.png) diff --git a/translations/es-ES/data/reusables/repositories/a-vulnerability-is.md b/translations/es-ES/data/reusables/repositories/a-vulnerability-is.md new file mode 100644 index 0000000000000..3c7913490fece --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/a-vulnerability-is.md @@ -0,0 +1 @@ +Una vulnerabilidad es un problema en el código de un proyecto que se puede aprovechar para dañar la confidencialidad, la integridad o la disponibilidad del proyecto o de otros proyectos que usan su código. Las vulnerabilidades varían en tipo, severidad y método de ataque. diff --git a/translations/es-ES/data/reusables/repositories/about-github-actions.md b/translations/es-ES/data/reusables/repositories/about-github-actions.md new file mode 100644 index 0000000000000..e93b7ceb941fc --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/about-github-actions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} te ayuda a automatizar tus flujos de trabajo de desarrollo de software en el mismo lugar en el que almacenas código y colaboras con informes de problemas y solicitudes de extracción. Puedes escribir tareas individuales, llamadas acciones, y combinarlas para crear un flujo de trabajo personalizado. diff --git a/translations/es-ES/data/reusables/repositories/about-github-archive-program.md b/translations/es-ES/data/reusables/repositories/about-github-archive-program.md new file mode 100644 index 0000000000000..9bf2b263b2b8d --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/about-github-archive-program.md @@ -0,0 +1 @@ +Predeterminadamente, todos los repositorios públicos se incluyen en el {% data variables.product.prodname_archive %}, una sociedad entre {% data variables.product.prodname_dotcom %} y organizaciones tales como Software Heritage Foundation e Internet Archive para garantizar la preservación a largo plazo del software de código abierto en el mundo. diff --git a/translations/es-ES/data/reusables/repositories/about-internal-repos.md b/translations/es-ES/data/reusables/repositories/about-internal-repos.md new file mode 100644 index 0000000000000..629497f587518 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/about-internal-repos.md @@ -0,0 +1 @@ +Puedes utilizar los repositorios internos para practivar el "innersource" dentro de tu empresa. Los miembros de tu empresa pueden colaborar utilizando metodologías de código abierto sin compartir información propietaria al público{% if enterpriseServerVersions contains currentVersion %}, aún cuando se inhabilite el modo privado{% endif %}. diff --git a/translations/es-ES/data/reusables/repositories/accessing-repository-graphs.md b/translations/es-ES/data/reusables/repositories/accessing-repository-graphs.md new file mode 100644 index 0000000000000..08f7bf2b8cdca --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/accessing-repository-graphs.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de repositorio, da clic en {% octicon "graph" aria-label="The bar graph icon" %}**Perspectivas**. ![Pestaña de perspectivas en la barra de navegación del repositorio principal](/assets/images/help/repository/repo-nav-insights-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/accessing-repository-people.md b/translations/es-ES/data/reusables/repositories/accessing-repository-people.md new file mode 100644 index 0000000000000..2877e8412b8c6 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/accessing-repository-people.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Personas**. ![Pestaña de personas en la barra lateral del repositorio](/assets/images/help/repository/accessing-repository-people.png) diff --git a/translations/es-ES/data/reusables/repositories/action-root-user-required.md b/translations/es-ES/data/reusables/repositories/action-root-user-required.md new file mode 100644 index 0000000000000..db25da04f9f73 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/action-root-user-required.md @@ -0,0 +1 @@ +**Nota:**{% data variables.product.prodname_actions %} debe ejecutarse por el usuario predeterminado (root) de Docker. Asegúrate de que tu Dockerfile no configure la instrucción de `USER`, de lo contrario, no podrás acceder a `GITHUB_WORKSPACE`. diff --git a/translations/es-ES/data/reusables/repositories/actions-ci-cd.md b/translations/es-ES/data/reusables/repositories/actions-ci-cd.md new file mode 100644 index 0000000000000..f620d66af6723 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-ci-cd.md @@ -0,0 +1 @@ +Con {% data variables.product.prodname_actions %} puedes crear capacidades de integración continua (CI, por sus siglas en inglés) de extremo a extremo y de funcionamiento continuo (CD, por sus siglas en inglés) directamente en tu repositorio. diff --git a/translations/es-ES/data/reusables/repositories/actions-env-var-note.md b/translations/es-ES/data/reusables/repositories/actions-env-var-note.md new file mode 100644 index 0000000000000..4362e3e21faac --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-env-var-note.md @@ -0,0 +1 @@ +Cuando se define más de una variable de ambiente con el mismo nombre, {% data variables.product.prodname_dotcom %} utiliza la más específica. Por ejemplo, una variable de ambiente definida en un paso anulará aquellas de los jobs y flujos de trabajo con el mismo nombre, mientras ejecuta el paso. Una variable definida para un trabajo anulará aquella de un flujo de trabajo si tienen el mismo nombre, mientras ejecuta el job. diff --git a/translations/es-ES/data/reusables/repositories/actions-matrix-builds-os.md b/translations/es-ES/data/reusables/repositories/actions-matrix-builds-os.md new file mode 100644 index 0000000000000..0433de1e12578 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-matrix-builds-os.md @@ -0,0 +1 @@ +Cuando defines una matriz de sistemas operativos, debes modificar el valor de `runs-on` a la propiedad de contexto de `matrix.os` que definiste. diff --git a/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md new file mode 100644 index 0000000000000..506768d0f04b2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -0,0 +1,11 @@ +Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes ejecutar flujos de trabajo programados es una vez cada 5 minutos. + +Este ejemplo activa el flujo de trabajo cada 15 minutos: + +```yaml +on: + schedule: + # * is a special character in YAML so you have to quote this string + - cron: '*/15 * * * *' + +``` diff --git a/translations/es-ES/data/reusables/repositories/actions-tab.md b/translations/es-ES/data/reusables/repositories/actions-tab.md new file mode 100644 index 0000000000000..6ad37f4246e18 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-tab.md @@ -0,0 +1 @@ +1. Debajo del nombre de tu repositorio, da clic en **Acciones**. ![Pestaña de acciones en la navegación del repositorio principal](/assets/images/help/repository/actions-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/actions-workflow-status-badge-into.md b/translations/es-ES/data/reusables/repositories/actions-workflow-status-badge-into.md new file mode 100644 index 0000000000000..e8bacc2f25aa9 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/actions-workflow-status-badge-into.md @@ -0,0 +1,3 @@ +Una insignia de estado muestra si un flujo de trabajo falla o pasa actualmente. Un lugar común para agregar una insignia de estado es el archivo README.md de tu repositorio, pero puedes agregarlo a cualquier página web que quieras. Predeterminadamente, las insignias muestran el estado de tu rama predeterminada. También puedes mostrar el estado de la ejecución de un flujo de trabajo para una rama o evento específicos utilizando los parámetros de query `branch` y `event` en la URL. + +![ejemplo de insignia de estado](/assets/images/help/repository/actions-workflow-status-badge.png) diff --git a/translations/es-ES/data/reusables/repositories/add-branch-protection-rules.md b/translations/es-ES/data/reusables/repositories/add-branch-protection-rules.md new file mode 100644 index 0000000000000..f0d1f9909a180 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/add-branch-protection-rules.md @@ -0,0 +1,2 @@ +4. Junto a "Reglas de protección de rama", da clic en **Agregar regla**. ![Botón de agregar regla de protección de rama](/assets/images/help/branches/add-branch-protection-rule.png) +5. Debajo del "Patrón del nombre de la rama", teclea el nombre de la rama o el patrón que quieras proteger. ![Campo de regla de rama ](/assets/images/help/branches/specify-branch-protection-rule.png) diff --git a/translations/es-ES/data/reusables/repositories/administrators-can-disable-issues.md b/translations/es-ES/data/reusables/repositories/administrators-can-disable-issues.md new file mode 100644 index 0000000000000..3f1b447601c91 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/administrators-can-disable-issues.md @@ -0,0 +1 @@ +Los administradores de repositorio pueden inhabilitar las propuestas de un repositorio. Para obtener más información, consulta la sección "[Inhabilitar propuestas](/github/managing-your-work-on-github/disabling-issues)". diff --git a/translations/es-ES/data/reusables/repositories/allow-maintainers-user-forks.md b/translations/es-ES/data/reusables/repositories/allow-maintainers-user-forks.md new file mode 100644 index 0000000000000..21fe6f6b62377 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/allow-maintainers-user-forks.md @@ -0,0 +1,7 @@ +1. En las bifurcaciones que pertenecen a un usuario, si no quieres permitir que las personas con acceso de escritura en el repositorio ascendente realicen cambios en tu solicitud de extracción, deselecciona **Permitir ediciones de los mantenedores**. + + {% warning %} + + **Advertencia:** Si tu bifuración contiene flujos de trabajo de {% data variables.product.prodname_actions %}, la opción es **Permitir que los mantenedores hagan ediciones y tengan acceso a los secretos**. El permitir las ediciones en la rama de una bifurcación que contiene flujos de trabajo de {% data variables.product.prodname_actions %} también permite que un mantenedor edite los flujos de trabajo del repositorio, lo cual podría revelar los valores de los secretos y otorgar acceso a otras ramas potencialmente. + + {% endwarning %} diff --git a/translations/es-ES/data/reusables/repositories/archiving-repositories-recommendation.md b/translations/es-ES/data/reusables/repositories/archiving-repositories-recommendation.md new file mode 100644 index 0000000000000..6525dcb673ecb --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/archiving-repositories-recommendation.md @@ -0,0 +1 @@ +Recomendamos que cierres todas las propuestas y solicitudes de extracción, y que además actualices la descripción y el archivo README antes de que archives un repositorio. diff --git a/translations/es-ES/data/reusables/repositories/asking-for-review.md b/translations/es-ES/data/reusables/repositories/asking-for-review.md new file mode 100644 index 0000000000000..f79f4ffb06e75 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/asking-for-review.md @@ -0,0 +1,5 @@ +{% tip %} + +**Tip:** Después de que crees una solicitud de extracción, puedes pedir a alguien en específico que [revise tus cambios propuestos](/articles/reviewing-proposed-changes-in-a-pull-request). Para obtener más información, consulta "[Solicitar la revisión de una solicitud de extracción](/articles/requesting-a-pull-request-review/)". + +{% endtip %} diff --git a/translations/es-ES/data/reusables/repositories/assign-an-issue-as-project-maintainer.md b/translations/es-ES/data/reusables/repositories/assign-an-issue-as-project-maintainer.md new file mode 100644 index 0000000000000..21e754aeab0b3 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/assign-an-issue-as-project-maintainer.md @@ -0,0 +1 @@ +1. Si eres un mantenedor de proyecto, puedes [asignar el informe de problemas a alguien](/articles/assigning-issues-and-pull-requests-to-other-github-users), [agregarlo a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar), [asociarlo con un hito](/articles/associating-milestones-with-issues-and-pull-requests), o [aplicar una etiqueta](/articles/applying-labels-to-issues-and-pull-requests). diff --git a/translations/es-ES/data/reusables/repositories/autolink-references.md b/translations/es-ES/data/reusables/repositories/autolink-references.md new file mode 100644 index 0000000000000..a7e2430c1f7ec --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/autolink-references.md @@ -0,0 +1 @@ +Si se configuran las referencias autovinculadas personalizadas para un repositorio, entonces las referencias a recursos externos, como un informe de problemas de JIRA o un ticket de Zendesk, se convertirán en vínculos acortados. Para saber qué autovínculos se encuentran disponibles en tu repositorio, contacta a alguien con permisos administrativos sobre el mismo. Para obtener más información, consulta la sección "[Configurar autovínculos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)". diff --git a/translations/es-ES/data/reusables/repositories/blocked-passwords.md b/translations/es-ES/data/reusables/repositories/blocked-passwords.md new file mode 100644 index 0000000000000..c16073112129a --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/blocked-passwords.md @@ -0,0 +1,6 @@ +{% if currentVersion == "free-pro-team@latest" %} +Cuando tecleas una contraseña para iniciar sesión, crear una cuenta, o cambiar tu contraseña, +{% data variables.product.product_name %} verificará si la contraseña que ingresaste se considera débil de acuerdo con los conjuntos de datos como en HaveIBeenPwned. La contraseña se puede considerar débil, incluso si no la usaste nunca antes. + +{% data variables.product.product_name %} solo inspecciona la contraseña cuando la escribes, pero nunca almacena la contraseña que ingresaste como texto simple. Para obtener más información, consulta [HaveIBeenPwned](https://haveibeenpwned.com/). +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/branch-rules-example.md b/translations/es-ES/data/reusables/repositories/branch-rules-example.md new file mode 100644 index 0000000000000..ea81704455211 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/branch-rules-example.md @@ -0,0 +1 @@ +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/es-ES/data/reusables/repositories/changed-files.md b/translations/es-ES/data/reusables/repositories/changed-files.md new file mode 100644 index 0000000000000..733080c30bbd7 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/changed-files.md @@ -0,0 +1 @@ +1. En la solicitud de extracción, da clic en {% octicon "diff" aria-label="The file diff icon" %}**Archivos cambiados**. ![Pestaña de Archivos Cambiados](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) diff --git a/translations/es-ES/data/reusables/repositories/changed-repository-access-permissions.md b/translations/es-ES/data/reusables/repositories/changed-repository-access-permissions.md new file mode 100644 index 0000000000000..6919fa62835d6 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/changed-repository-access-permissions.md @@ -0,0 +1 @@ +8. Lee acerca de los permisos de acceso a repositorios que se han modificado. diff --git a/translations/es-ES/data/reusables/repositories/choose-line-or-range.md b/translations/es-ES/data/reusables/repositories/choose-line-or-range.md new file mode 100644 index 0000000000000..5696832849fe8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/choose-line-or-range.md @@ -0,0 +1,3 @@ +1. Decide si seleccionar una única línea o un rango: + - Para seleccionar una única línea del código, haz clic en el número de línea para resaltarla. ![Archivo con una única línea del código seleccionada](/assets/images/help/repository/highlight-line-of-code.png) + - Para seleccionar un rango de código, haz clic en el número de la primera línea del rango para resaltar la línea del código. Luego lleva el puntero hasta la última línea del rango del código, presiona Shift y haz clic en el número de línea para resaltar el rango. ![Archivo con un rango del código seleccionado](/assets/images/help/repository/highlight-range-of-code.png) diff --git a/translations/es-ES/data/reusables/repositories/choose-pr-review.md b/translations/es-ES/data/reusables/repositories/choose-pr-review.md new file mode 100644 index 0000000000000..d91f18aebdcb4 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/choose-pr-review.md @@ -0,0 +1 @@ +1. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas revisar. diff --git a/translations/es-ES/data/reusables/repositories/choose-repo-visibility.md b/translations/es-ES/data/reusables/repositories/choose-repo-visibility.md new file mode 100644 index 0000000000000..88101c9b4be62 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/choose-repo-visibility.md @@ -0,0 +1 @@ +1. Elige la visibilidad del repositorio. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". ![Botones radiales para seleccionar la visibilidad del repositorio](/assets/images/help/repository/create-repository-public-private.png) diff --git a/translations/es-ES/data/reusables/repositories/click-dependency-graph.md b/translations/es-ES/data/reusables/repositories/click-dependency-graph.md new file mode 100644 index 0000000000000..94479c621439c --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/click-dependency-graph.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, da clic en **Gráfica de dependencias**. ![Pestaña de gráfica de dependencias en la barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-dependency-graph.png) diff --git a/translations/es-ES/data/reusables/repositories/copy-clone-url.md b/translations/es-ES/data/reusables/repositories/copy-clone-url.md new file mode 100644 index 0000000000000..37ce4e0f0c0d2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/copy-clone-url.md @@ -0,0 +1,15 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +1. Debajo del nombre del repositorio, da clic en **Clonar o descargar**. ![Botón Clone or download (Clonar o descargar)](/assets/images/help/repository/clone-repo-clone-url-button.png) +2. Para clonar el repositorio utilizando HTTPS, debajo de "Clonar con HTTPS", da clic en +{% octicon "clippy" aria-label="The clipboard icon" %}. +Para clonar el repositorio utilizando una llave SSH, incluyendo un certificado que haya emitido la autoridad de certificados SSH de tu organización, da clic en **Usar SSH** y luego en +{% octicon "clippy" aria-label="The clipboard icon" %}. +![Botón Clone URL (Clonar URL)](/assets/images/help/repository/https-url-clone.png) +{% else %} +1. Sobre la lista de archivos, da clic en {% octicon "download" aria-label="The download icon" %} **Código**. ![Botón de "Código"](/assets/images/help/repository/code-button.png) +1. Para clonar el repositorio utilizando HTTPS, debajo de "Clonar con HTTPS", da clic en +{% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar el repositorio utilizando una llave de SSH, incluyendo un certificado que emita la autoridad de certificados SSH de tu organización, da clic en **Utilizar SSH**, y luego da clic en {% octicon "clippy" aria-label="The clipboard icon" %}.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} Para clonar un repositorio utiilzando {% data variables.product.prodname_cli %}, da clic en **Utilizar {% data variables.product.prodname_cli %}**, y luego da clic en {% octicon "clippy" aria-label="The clipboard icon" %}.{% endif %} + ![El icono de portapapeles para copiar la URL para clonar un repositorio](/assets/images/help/repository/https-url-clone.png) + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} + ![El icono del portapapeles para copiar la URL para clonar un repositorio con el CLI de GitHub](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/create-pull-request.md b/translations/es-ES/data/reusables/repositories/create-pull-request.md new file mode 100644 index 0000000000000..0cd97fc67eef1 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/create-pull-request.md @@ -0,0 +1 @@ +1. Para crear una solicitud de extracción que está lista para revisión, haz clic en **Create Pull Request** (Crear solicitud de extracción). Para crear un borrador de solicitud de extracción, utiliza el menú desplegable y selecciona **Crear Borrador de Solicitud de Extracción**, y posteriormente da clic en **Borrador de Solicitud de Extracción**. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)".![Botón Create pull request (Crear una solicitud de extracción)](/assets/images/help/pull_requests/pullrequest-send.png) diff --git a/translations/es-ES/data/reusables/repositories/create-repo.md b/translations/es-ES/data/reusables/repositories/create-repo.md new file mode 100644 index 0000000000000..867b7608f8258 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/create-repo.md @@ -0,0 +1 @@ +1. Da clic en **Crear repositorio**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} diff --git a/translations/es-ES/data/reusables/repositories/create_new.md b/translations/es-ES/data/reusables/repositories/create_new.md new file mode 100644 index 0000000000000..92090980ee0ce --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/create_new.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, utiliza el menú desplegable {% octicon "plus" aria-label="Plus symbol" %} y selecciona **Repositorio Nuevo**. ![Menú desplegable con opción para crear un repositorio nuevo](/assets/images/help/repository/repo-create.png) diff --git a/translations/es-ES/data/reusables/repositories/default-issue-templates.md b/translations/es-ES/data/reusables/repositories/default-issue-templates.md new file mode 100644 index 0000000000000..ba88a1acdcb2e --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/default-issue-templates.md @@ -0,0 +1,2 @@ +Puedes crear plantillas predeterminadas para propuestas{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} y un archivo de configuración predeterminado para estas plantillas{% endif %} para tu cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)." + diff --git a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md new file mode 100644 index 0000000000000..04cde59f3b0bf --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -0,0 +1,11 @@ +{% warning %} + +**Advertencia:** + +- Si eliminas el acceso de una persona a un repositorio privado, todas sus bifurcaciones de ese repositorio privado se eliminarán. Los clones locales del repositorio privado se conservarán. Si se revoca el acceso de un equipo a un repositorio privado o se elimina un equipo con acceso a un repositorio privado, y los miembros del equipo no tienen acceso al repositorio a través de otro equipo, las bifurcaciones privadas del repositorio se eliminarán.{% if enterpriseServerVersions contains currentVersion %} +- Cuando [LDAP Sync esté habilitado](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), si eliminas a una persona de un repositorio, perderá acceso, pero sus bifurcaciones no se eliminarán. Si la persona se agrega a un equipo con acceso al repositorio original de la organización dentro de los tres meses, su acceso a las bifurcaciones se restaurarán de manera automática la próxima vez que ocurra una sincronización.{% endif %} +- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. + +- Las personas con permisos administrativos en un repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} pueden dejar de permitir la bifurcación de dicho repositorio, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} en una organización. Para obtener más información, consulta la sección "[Administrar la política de bifurcación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" y "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/repositories/dependency-review.md b/translations/es-ES/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000000..239ff8e838dd6 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/dependency-review.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Adicionalmente, +{% data variables.product.prodname_dotcom %} puede revisar cualquier dependencia que se agregue, actualice o elimine en una solicitud de cambios que se haga contra la rama predeterminada de un repositorio así como marcar cualquier cambio que pudiera introducir una vulnerabilidad en tu proyecto. Esto te permite ubicar y tratar las dependencias vulnerables antes, en vez de después, de que lleguen a tu base de código. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/deploy-keys-write-access.md b/translations/es-ES/data/reusables/repositories/deploy-keys-write-access.md new file mode 100644 index 0000000000000..e32d6199c14f9 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/deploy-keys-write-access.md @@ -0,0 +1 @@ +Las claves de despliegue con acceso de escritura pueden llevar a cabo las mismas acciones que un miembro de la organización con acceso administrativo o que un colaborador en un repositorio personal. Para obtener más información, consulta las secciones "[Niveles de permiso en los repositorios para una organización](/articles/repository-permission-levels-for-an-organization/)" y "[Niveles de permiso para un repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/)". diff --git a/translations/es-ES/data/reusables/repositories/deploy-keys.md b/translations/es-ES/data/reusables/repositories/deploy-keys.md new file mode 100644 index 0000000000000..e0acb459da660 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/deploy-keys.md @@ -0,0 +1 @@ +Puedes lanzar proyectos desde un repositorio de {% data variables.product.product_name %} hacia tu servidor al utilizar una llave de despliegue, la cual es una llave SSH que otorga acceso a un repositorio específico. {% data variables.product.product_name %} adjunta la parte pública de la llave directamente en tu repositorio en vez de hacerlo a una cuenta de usuario, y la parte privada de ésta permanece en tu servidor. Para obtener más información, consulta la sección "[Entregar despliegues](/rest/guides/delivering-deployments)". diff --git a/translations/es-ES/data/reusables/repositories/desktop-fork.md b/translations/es-ES/data/reusables/repositories/desktop-fork.md new file mode 100644 index 0000000000000..b1d59bc6b863b --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/desktop-fork.md @@ -0,0 +1 @@ +Puedes utilizar {% data variables.product.prodname_desktop %} para bifurcar un repositorio. Para obtener más información, consulta la sección "[Clonar y bifurcar repositorios desde {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)". diff --git a/translations/es-ES/data/reusables/repositories/edit-file.md b/translations/es-ES/data/reusables/repositories/edit-file.md new file mode 100644 index 0000000000000..01a0b1450af19 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/edit-file.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Botón Editar archivo](/assets/images/help/repository/edit-file-edit-button.png) diff --git a/translations/es-ES/data/reusables/repositories/edited-comment-list.md b/translations/es-ES/data/reusables/repositories/edited-comment-list.md new file mode 100644 index 0000000000000..d92ee5268b7e0 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/edited-comment-list.md @@ -0,0 +1,9 @@ +2. En la parte superior del comentario, da clic en **editado** para abrir el historial de edición. + + {% note %} + + **Nota:** si no ves la opción de **editado**, entonces el comentario no tiene un historial de edición. + + {% endnote %} + +3. Para ver los detalles de un cambio específico, selecciónalo de la lista de ediciones. ![Ver los detalles de edición de un comentario](/assets/images/help/repository/choose-comment-edit-to-expand.png) diff --git a/translations/es-ES/data/reusables/repositories/enable-security-alerts.md b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md new file mode 100644 index 0000000000000..8ce1c88390056 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md @@ -0,0 +1,4 @@ +{% if enterpriseServerVersions contains currentVersion %} +Tu administrador de sitio debe habilitar +{% if currentVersion ver_gt "enterprise-server@2.21" %}Las alertas de seguridad{% else %}del {% data variables.product.prodname_dependabot %}{% endif %} para las dependencias vulnerables para {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/github-reviews-security-advisories.md b/translations/es-ES/data/reusables/repositories/github-reviews-security-advisories.md new file mode 100644 index 0000000000000..a44a3be33cc21 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/github-reviews-security-advisories.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} revisará cada asesoría de seguridad que se haya publicado, la agregará a la {% data variables.product.prodname_advisory_database %}, y podría utilzar esta asesoría de seguridad para enviar {% data variables.product.prodname_dependabot_alerts %} a los repositorios que se vean afectados. Si la asesoría de seguridad viene de una bifurcación, únicamente enviaremos una alerta si ésta tiene un paquete que se publique con un nombre único y esté en un registro de paquetes público. Este proceso puede tomar hasta 72 horas y {% data variables.product.prodname_dotcom %} podría contactarte para obtener más información. + +Para obtener más informació acera de las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". Para obtener más información acerca de la {% data variables.product.prodname_advisory_database %}, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)". diff --git a/translations/es-ES/data/reusables/repositories/github-security-lab.md b/translations/es-ES/data/reusables/repositories/github-security-lab.md new file mode 100644 index 0000000000000..b4dac7c01fca8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/github-security-lab.md @@ -0,0 +1 @@ +También puedes unirte a [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) para buscar temas relacionados con seguridad y contribuir con las herramientas y proyectos de seguridad. diff --git a/translations/es-ES/data/reusables/repositories/initialize-with-readme.md b/translations/es-ES/data/reusables/repositories/initialize-with-readme.md new file mode 100644 index 0000000000000..14150f67e0349 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/initialize-with-readme.md @@ -0,0 +1 @@ +1. Selecciona **Inicializar este repositiro con un README**. ![Inicializar este repositorio con una casilla de verificación README](/assets/images/help/repository/initialize-with-readme.png) diff --git a/translations/es-ES/data/reusables/repositories/internal-repo-default.md b/translations/es-ES/data/reusables/repositories/internal-repo-default.md new file mode 100644 index 0000000000000..91e0c929e512f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/internal-repo-default.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Los repositorios internos son la configuración predeterminada de todo repositorio nuevo que se cree en una organización que pertenezca a una empresa empresarial. +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/issue-template-config.md b/translations/es-ES/data/reusables/repositories/issue-template-config.md new file mode 100644 index 0000000000000..5d4af5128f5be --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/issue-template-config.md @@ -0,0 +1 @@ +Puedes personalizar el selector de plantilla de informe de problemas que ven las personas cuando crean un nuevo informe de problemas en tu repositorio si añades un archivo *config.yml* a la carpeta `.github/ISSUE_TEMPLATE`. diff --git a/translations/es-ES/data/reusables/repositories/legacy-issue-template-tip.md b/translations/es-ES/data/reusables/repositories/legacy-issue-template-tip.md new file mode 100644 index 0000000000000..cc31378d2ccc3 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/legacy-issue-template-tip.md @@ -0,0 +1,6 @@ + +{% warning %} + +Este es el flujo de trabajo tradicional para crear una plantilla de informe de problemas. Te recomendamos utilizar el creador múltiple de plantillas de informe de problemas mejorado para crear varias plantillas. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/repositories/list-closed-pull-requests.md b/translations/es-ES/data/reusables/repositories/list-closed-pull-requests.md new file mode 100644 index 0000000000000..488f1155b36be --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/list-closed-pull-requests.md @@ -0,0 +1 @@ +1. Da clic en **Cerrado** para ver una lista de solicitudes de extracción cerradas. ![Pestaña de cerrado](/assets/images/help/branches/branches-closed.png) diff --git a/translations/es-ES/data/reusables/repositories/merge-all-pulls-together.md b/translations/es-ES/data/reusables/repositories/merge-all-pulls-together.md new file mode 100644 index 0000000000000..7834ade19ee7f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/merge-all-pulls-together.md @@ -0,0 +1 @@ +No puedes fusionar solicitudes de fusión individuales en una bifurcación privada temporal. En vez de esto, fusionas todas las solicitudes de extracción al mismo tiempo en la asesoría de seguridad correspondiente. diff --git a/translations/es-ES/data/reusables/repositories/migrating-from-codeplex.md b/translations/es-ES/data/reusables/repositories/migrating-from-codeplex.md new file mode 100644 index 0000000000000..27ba5cb6375aa --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/migrating-from-codeplex.md @@ -0,0 +1 @@ +Si estás migrándo tu proyecto desde CodePlex, lee la [guía de migración](https://aka.ms/codeplex-guide) para obtener más información. diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-branches.md b/translations/es-ES/data/reusables/repositories/navigate-to-branches.md new file mode 100644 index 0000000000000..43150a9ad0e3d --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-branches.md @@ -0,0 +1 @@ +1. Sobre la lista de archivos, da clic en {% octicon "git-branch" aria-label="The branch icon" %}**NUMBER branches**. ![Vínculo de ramas en página de resumen](/assets/images/help/branches/branches-link.png) diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/es-ES/data/reusables/repositories/navigate-to-job-superlinter.md new file mode 100644 index 0000000000000..ae717f6fc8812 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-job-superlinter.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Debajo de **Jobs** o en la gráfica de visualización, da clic en el job que quieras ver. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} +1. En la barra lateral izquierda, da clic en el job que quieres ver. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job.png) +{% else %} +1. En la barra lateral izquierda, da clic en el job que quieres ver. ![Seleccionar un job de flujo de trabajo](/assets/images/help/repository/workflow-job.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-manage-access.md b/translations/es-ES/data/reusables/repositories/navigate-to-manage-access.md new file mode 100644 index 0000000000000..969bd44c027dd --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-manage-access.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Administrar acceso**. ![pestaña de "Administrar acceso"](/assets/images/help/repository/manage-access-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-repo.md b/translations/es-ES/data/reusables/repositories/navigate-to-repo.md new file mode 100644 index 0000000000000..b65b86f93e796 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-repo.md @@ -0,0 +1 @@ +1. En {% data variables.product.product_name %}, visita la página principal del repositorio. diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md new file mode 100644 index 0000000000000..9bf9d43bf1724 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![pestaña de "Seguridad & análisis" en la configuración de repositorio](/assets/images/help/repository/security-and-analysis-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-workflow-superlinter.md b/translations/es-ES/data/reusables/repositories/navigate-to-workflow-superlinter.md new file mode 100644 index 0000000000000..4aeeeecf65b86 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-workflow-superlinter.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres ver. ![Lista de flujos de trabajo en la barra lateral izquierda](/assets/images/help/repository/superlinter-workflow-sidebar.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-workflow.md b/translations/es-ES/data/reusables/repositories/navigate-to-workflow.md new file mode 100644 index 0000000000000..3ce7bea39c065 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/navigate-to-workflow.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres ver. ![Lista de flujos de trabajo en la barra lateral izquierda](/assets/images/help/repository/workflow-sidebar.png) diff --git a/translations/es-ES/data/reusables/repositories/new-pull-request.md b/translations/es-ES/data/reusables/repositories/new-pull-request.md new file mode 100644 index 0000000000000..5e91db9aa3079 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/new-pull-request.md @@ -0,0 +1,7 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +1. A la derecha del menú de rama, da clic en **Nueva solicitud de extracción**. ![Enlace de "Solicitud de extracción" sobre la lsita de archivos](/assets/images/help/pull_requests/pull-request-start-review-button.png) +{% else %} +1. Sobre la lista de archivos, da clic en +{% octicon "git-pull-request" aria-label="The pull request icon" %} **Solicitud de cambios**. + ![Enlace de "Solicitud de extracción" sobre la lsita de archivos](/assets/images/help/pull_requests/pull-request-start-review-button.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/open-with-github-desktop.md b/translations/es-ES/data/reusables/repositories/open-with-github-desktop.md new file mode 100644 index 0000000000000..9ab7609932c42 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/open-with-github-desktop.md @@ -0,0 +1,11 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} +1. Debajo del nombre del repositorio, haz clic en **Clone or download** (Clonar o descargar). ![Botón Clone or download (Clonar o descargar)](/assets/images/help/repository/clone-repo-clone-url-button.png) +1. Da clic en **Abrir en escritorio** para clonar el repositorio y abrirlo en +{% data variables.product.prodname_desktop %}. +![Botón Open in Desktop (Abrir en escritorio)](/assets/images/help/desktop/open-in-desktop-button.png) +{% else %} +1. Sobre la lista de archivos, da clic en {% octicon "download" aria-label="The download icon" %} **Código**. ![Botón de "Código"](/assets/images/help/repository/code-button.png) +1. Da clic en +{% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Abrir con {% data variables.product.prodname_desktop %}** para clonar y abrir el repositorio con {% data variables.product.prodname_desktop %}. + ![Botón de "Abrir con {% data variables.product.prodname_desktop %}"](/assets/images/help/repository/open-with-desktop.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/owner-drop-down.md b/translations/es-ES/data/reusables/repositories/owner-drop-down.md new file mode 100644 index 0000000000000..d7d89499dd1c1 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/owner-drop-down.md @@ -0,0 +1 @@ +1. Utiliza el menú desplegable de **Propietario** y selecciona la cuenta que quieres sea propietaria del repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) diff --git a/translations/es-ES/data/reusables/repositories/permissions-statement-read.md b/translations/es-ES/data/reusables/repositories/permissions-statement-read.md new file mode 100644 index 0000000000000..954a12f176059 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/permissions-statement-read.md @@ -0,0 +1 @@ +Se requiere tener acceso de lectura en el repositorio para llevar a cabo estos pasos. diff --git a/translations/es-ES/data/reusables/repositories/permissions-statement-write.md b/translations/es-ES/data/reusables/repositories/permissions-statement-write.md new file mode 100644 index 0000000000000..7c44b96e0918f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/permissions-statement-write.md @@ -0,0 +1 @@ +Se requiere tener acceso de escritura en el repositorio para llevar a cabo estos pasos. diff --git a/translations/es-ES/data/reusables/repositories/pr-title-description.md b/translations/es-ES/data/reusables/repositories/pr-title-description.md new file mode 100644 index 0000000000000..718347844a0f2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/pr-title-description.md @@ -0,0 +1 @@ +1. Escribe un título y una descripción para tu solicitud de extracción. ![Título y campos de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png) diff --git a/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md new file mode 100644 index 0000000000000..e3fa8870081cc --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md @@ -0,0 +1 @@ +Las bifurcaciones privadas heredan la estructura de permisos del repositorio ascendente o padre. Por ejemplo, si el repositorio ascendente es privado y otorga acceso de lectura/escritura a un equipo, entonces el mismo equipo tendrá este tipo de acceso en cualquier bifurcación de dicho repositorio ascendente. Esto ayuda a que los propietarios de repositorios privados mantengan el control sobre su código. diff --git a/translations/es-ES/data/reusables/repositories/protected-branches-block-web-edits-uploads.md b/translations/es-ES/data/reusables/repositories/protected-branches-block-web-edits-uploads.md new file mode 100644 index 0000000000000..da4c12713a31b --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/protected-branches-block-web-edits-uploads.md @@ -0,0 +1,3 @@ +Si un repositorio cuenta con alguna rama protegida, no podrás editar o cargar archivos en ésta utilizando {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". + +Puedes utilizar {% data variables.product.prodname_desktop %} para mover tus cambios a una rama nueva y confirmarlos. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)". diff --git a/translations/es-ES/data/reusables/repositories/reaction_list.md b/translations/es-ES/data/reusables/repositories/reaction_list.md new file mode 100644 index 0000000000000..7851fb8b55b72 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/reaction_list.md @@ -0,0 +1,10 @@ +| contenido | emoji | +| ------------ | ---------- | +| `+1` | :+1: | +| `-1` | :-1: | +| `risa` | :smile: | +| `confundido` | :confused: | +| `corazón` | :heart: | +| `viva` | :tada: | +| `cohete` | :rocket: | +| `ojos` | :eyes: | diff --git a/translations/es-ES/data/reusables/repositories/relative-links.md b/translations/es-ES/data/reusables/repositories/relative-links.md new file mode 100644 index 0000000000000..3b5392ae0637c --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/relative-links.md @@ -0,0 +1,11 @@ +Puedes definir enlaces relativos y rutas de imagen en los archivos representados para ayudar a que los lectores naveguen hasta otros archivos de tu repositorio. + +Un enlace relativo es un enlace que es relativo al archivo actual. Por ejemplo, si tienes un archivo README en la raíz de tu repositorio y tienes otro archivo en _docs/CONTRIBUTING.md_, el enlace relativo a _CONTRIBUTING.md_ en tu archivo README podría verse así: + +``` +[Contribution guidelines for this project](docs/CONTRIBUTING.md) +``` + +{% data variables.product.product_name %} transformará de manera automática el enlace relativo o la ruta de imagen en cualquier rama en la que te encuentres actualmente, de modo que el enlace o ruta siempre funcione. Puedes usar todos los operandos del enlace relativo, como `./` y `../`. + +Los enlaces relativos son más sencillos para los usuarios que clonan tu repositorio. Puede que los enlaces absolutos no funcionen en los clones de tu repositorio. Recomendamos usar enlaces relativos para consultar los archivos dentro de tu repositorio. diff --git a/translations/es-ES/data/reusables/repositories/releases.md b/translations/es-ES/data/reusables/repositories/releases.md new file mode 100644 index 0000000000000..062c3f10b3dd2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/releases.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} + +1. Debajo del nombre de tu repositorio, da clic en **Lanzamientos**. ![Pestaña de lanzamientos](/assets/images/help/releases/release-link.png) + +{% else %} + +1. A la derecha de la lista de archivos, da clic en **Releases** o **Latest release**. ![Sección de lanzamientos en la barra lateral de lado derecho](/assets/images/help/releases/release-link.png) + +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/repo-name.md b/translations/es-ES/data/reusables/repositories/repo-name.md new file mode 100644 index 0000000000000..d293eb0f1d5bf --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/repo-name.md @@ -0,0 +1 @@ +1. Teclea el nombre de tu repositorio, y una descripción opcional. ![Crear un campo de repositorio](/assets/images/help/repository/create-repository-name.png) diff --git a/translations/es-ES/data/reusables/repositories/repo-size-limit.md b/translations/es-ES/data/reusables/repositories/repo-size-limit.md new file mode 100644 index 0000000000000..c990aecee50c4 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/repo-size-limit.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Los repositorios y archivos individuales están sujetos a límites de tamaño. Para obtener más información, consulta "[¿Cuál es mi cuota de disco?](/articles/what-is-my-disk-quota)" +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/reported-content-resolved-tab.md b/translations/es-ES/data/reusables/repositories/reported-content-resolved-tab.md new file mode 100644 index 0000000000000..972bab252f534 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/reported-content-resolved-tab.md @@ -0,0 +1 @@ +1. Debajo de "Reportes de abuso", da clic en **Resueltos**. ![Pestaña de "Resueltos" debajo de "Reportes de abuso"](/assets/images/help/repository/reported-content-resolved-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/repository-branches.md b/translations/es-ES/data/reusables/repositories/repository-branches.md new file mode 100644 index 0000000000000..59a1ebb75b394 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/repository-branches.md @@ -0,0 +1 @@ +1. En el menú izquierdo, da clic en **Ramas**. ![Sub-menú de opciones de repositorio](/assets/images/help/repository/repository-options-branch.png) diff --git a/translations/es-ES/data/reusables/repositories/request-changes-tips.md b/translations/es-ES/data/reusables/repositories/request-changes-tips.md new file mode 100644 index 0000000000000..b68d3eba204c9 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/request-changes-tips.md @@ -0,0 +1,9 @@ +{% tip %} + +**Tips**: +- Si se habilita las revisiones requeridas y un colaborador con acceso de _write_, _admin_, u _owner_ emite una revisión solicitando cambios, la solicitud de extracción no se podrá fusionar hasta queel mismo colaborador emita otra revisión aprobando los cambios en dicha solicitud de extracción. +- Los propietarios y administradores del repositorio pueden fusionar una solicitud de extracción, incluso si no recibió una revisión de aprobación o si un revisor que solicitó modificaciones abandonó la organización o no está disponible. +- Si están habilitadas las revisiones requeridas y el descarte de una revisión en espera, y se sube una confirmación de modificación de código a la rama de una solicitud de extracción aprobada, se descarta la aprobación. La solicitud de extracción se debe volver a revisar y aprobar antes de que se pueda fusionar. +- Cuando varias solicitudes de extracción abiertas tienen una rama de encabezado que apunta a la misma confirmación, no podrás fusionarlas si una o ambas tienen una revisión pendiente o rechazada. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md new file mode 100644 index 0000000000000..74c0f82b9ab5a --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md @@ -0,0 +1 @@ +Si aún no tienes un número de identificación CVE para la vulnerabilidad de seguridad en tu proyecto, puedes solicitar un número de identificación de CVE de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} habitualmente revisa la solicitud dentro de las primeras 72 horas de su recepción. El solicitar un número de identificación de CVE no convierte tu asesoría de seguridad en pública. Si tu asesoría de seguridad es elegible para un CVE, {% data variables.product.prodname_dotcom %} rservará un número de identificación de CVE para ésta. Después publicaremos los detalles del CVE después de que publiques la asesoría de seguridad. diff --git a/translations/es-ES/data/reusables/repositories/return-to-source-diff.md b/translations/es-ES/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..89edde383ebff --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![El botón de diff origen](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/es-ES/data/reusables/repositories/review-changes.md b/translations/es-ES/data/reusables/repositories/review-changes.md new file mode 100644 index 0000000000000..aeeb7df617e23 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/review-changes.md @@ -0,0 +1 @@ +1. Sobre el código que ha cambiado, da clic en **Revisar cambios**. ![Botón para revisar cambios](/assets/images/help/pull_requests/review-changes-button.png) diff --git a/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md new file mode 100644 index 0000000000000..cfe413d8a0cef --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md @@ -0,0 +1 @@ +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/es-ES/data/reusables/repositories/review-pr-commits.md b/translations/es-ES/data/reusables/repositories/review-pr-commits.md new file mode 100644 index 0000000000000..6607d8bb9b499 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/review-pr-commits.md @@ -0,0 +1 @@ +1. En la solicitud de extracción, da clic en {% octicon "git-commit" aria-label="The commit icon" %}**Confirmaciones**. ![Pestaña de confirmaciones en una solicitud de extracción](/assets/images/help/pull_requests/pull-request-tabs-commits.png) diff --git a/translations/es-ES/data/reusables/repositories/review-summary-comment.md b/translations/es-ES/data/reusables/repositories/review-summary-comment.md new file mode 100644 index 0000000000000..c1451d0eb2ff1 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/review-summary-comment.md @@ -0,0 +1 @@ +1. Teclea un comentario que resuma tu retroalimentación sobre los cambios propuestos. ![Ventana de comentarios para el resumen de la revisión](/assets/images/help/pull_requests/review-summary-comment-window.png) diff --git a/translations/es-ES/data/reusables/repositories/section-links.md b/translations/es-ES/data/reusables/repositories/section-links.md new file mode 100644 index 0000000000000..864b211c597d8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/section-links.md @@ -0,0 +1,3 @@ +Puedes vincular directamente a una sección en un archivo expedido si deslizas el puntero sobre el encabezado de la sección para exponer el enlace: + +![Enlace de sección con el archivo README para el repositorio de github/scientist](/assets/images/help/repository/readme-links.png) diff --git a/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md b/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md new file mode 100644 index 0000000000000..a481c37252692 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md @@ -0,0 +1 @@ +También puedes utilizar {% data variables.product.prodname_security_advisories %} para volver a publicar los detalles de una vulnerabilidad de seguridad que ya has divulgado en otro lugar si copias y pegas los detalles de la vulnerabilidad en una asesoría de seguridad nueva. diff --git a/translations/es-ES/data/reusables/repositories/security-advisory-admin-permissions.md b/translations/es-ES/data/reusables/repositories/security-advisory-admin-permissions.md new file mode 100644 index 0000000000000..0fe5180481263 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-advisory-admin-permissions.md @@ -0,0 +1,3 @@ +Cualquier usuario con permisos de administrador puede crear un aviso de seguridad. + +Cualquiera con permisos de administrador en un repositorio tendrá también permisos de administrador en todas las asesorías de seguridad del mismo. Las personas con permisos de administrador en una asesoría de seguridad pueden agregar colaboradores, y estos tendrán permisos de escritura en dicha asesoría. diff --git a/translations/es-ES/data/reusables/repositories/security-advisory-collaborators-public-repositories.md b/translations/es-ES/data/reusables/repositories/security-advisory-collaborators-public-repositories.md new file mode 100644 index 0000000000000..7802889f79365 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-advisory-collaborators-public-repositories.md @@ -0,0 +1 @@ +Si eliminas a un usuario de un repositorio u organización, y éste también es un colaborador en una asesoría de seguridad, dicho usuario aún tendrá acceso a esta asesoría. diff --git a/translations/es-ES/data/reusables/repositories/security-advisory-edit-description.md b/translations/es-ES/data/reusables/repositories/security-advisory-edit-description.md new file mode 100644 index 0000000000000..d52cf5c151cf3 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-advisory-edit-description.md @@ -0,0 +1 @@ +1. Escribe una descripción de la vulnerabilidad de seguridad. ![Descripción de vulnerabilidad en la asesoría de seguridad](/assets/images/help/security/security-advisory-description.png) diff --git a/translations/es-ES/data/reusables/repositories/security-advisory-edit-details.md b/translations/es-ES/data/reusables/repositories/security-advisory-edit-details.md new file mode 100644 index 0000000000000..883a034ccd13f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-advisory-edit-details.md @@ -0,0 +1 @@ +1. Teclea los detalles de la vulnerabilidad de seguridad que está tratando la asesoría de seguridad. ![Metadatos de asesoría de seguridad](/assets/images/help/security/security-advisory-metadata.png) diff --git a/translations/es-ES/data/reusables/repositories/security-alert-delivery-options.md b/translations/es-ES/data/reusables/repositories/security-alert-delivery-options.md new file mode 100644 index 0000000000000..4304ea81eca87 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-alert-delivery-options.md @@ -0,0 +1,4 @@ +{% if currentVersion != "github-ae@latest" %} +Si tu repositorio cuenta con un manifiesto compatible de la dependencia +{% if currentVersion == "free-pro-team@latest" %} (y si configuraste la gráfica de dependencias en caso de que sea un repositorio privado){% endif %}, cada que {% data variables.product.product_name %} detecte una dependencia vulnerable en éste, recibirás un resumen semanal por correo electrónico. También puedes configurar tus alertas de seguridad y notificaciones web, notificaciones individuales por correo electrónico, resúmenes diarios por correo electrónico o alertas en la interfaz de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/es-ES/data/reusables/repositories/security-alerts-x-github-severity.md new file mode 100644 index 0000000000000..dededf4943b19 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-alerts-x-github-severity.md @@ -0,0 +1 @@ +Notificaciones de correo electrónico para las {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las alertas de seguridad{% else %}del{% data variables.product.prodname_dependabot_alerts %}{% endif %} que afectan a uno o más repositorios incluyendo el campo de encabezado `X-GitHub-Severity`. Puedes utilizar el valor del campo de enabezado `X-GitHub-Severity` para filtrar las notificaciones por correo electrónico para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las alertas de seguridad{% else %}del{% data variables.product.prodname_dependabot_alerts %}{% endif %}. diff --git a/translations/es-ES/data/reusables/repositories/security-guidelines.md b/translations/es-ES/data/reusables/repositories/security-guidelines.md new file mode 100644 index 0000000000000..cb47dfe5d2189 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/security-guidelines.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Puedes crear una política de seguridad para dar instrucciones a las personas para reportar las vulnerabilidades de seguridad de manera responsable en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)". +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/select-items-in-issue-or-pr-list.md b/translations/es-ES/data/reusables/repositories/select-items-in-issue-or-pr-list.md new file mode 100644 index 0000000000000..e0ef9b0d0104b --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/select-items-in-issue-or-pr-list.md @@ -0,0 +1 @@ +3. Selecciona la casilla junto a los elementos a los que quieras aplicar la etiqueta. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) diff --git a/translations/es-ES/data/reusables/repositories/select-marketplace-apps.md b/translations/es-ES/data/reusables/repositories/select-marketplace-apps.md new file mode 100644 index 0000000000000..747c7b45b3f47 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/select-marketplace-apps.md @@ -0,0 +1,5 @@ +{% if currentVersion == "free-pro-team@latest" %} +1. Opcionalmente, si la cuenta personal o la organización en la que estás haciendo esta creación utiliza cualquier +{% data variables.product.prodname_github_app %} de {% data variables.product.prodname_marketplace %}, selecciona cualquier app que quieras utilizar en el repositorio. + ![Lista de las {% data variables.product.prodname_github_app %} de tu cuenta de {% data variables.product.prodname_marketplace %} y opción para dar acceso](/assets/images/help/repository/create-repository-choose-marketplace-apps.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/sensitive-info-warning.md b/translations/es-ES/data/reusables/repositories/sensitive-info-warning.md new file mode 100644 index 0000000000000..8f11eb71bc45e --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sensitive-info-warning.md @@ -0,0 +1,14 @@ +{% warning %} + +**Advertencia:** Si tratas con información sensible, nunca realices `git add`, `commit`, o `push` en un repositorio. La información sensible puede incluir, pero no se limita a: + +- Contraseñas +- SSH keys (Claves SSH) +- [Llaves de acceso AWS](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSGettingStartedGuide/AWSCredentials.html) +- Llaves API +- Números de tarjetas de crédito +- Números de NIP + +Para obtener más información, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". + +{% endwarning %} diff --git a/translations/es-ES/data/reusables/repositories/settings-sidebar-actions.md b/translations/es-ES/data/reusables/repositories/settings-sidebar-actions.md new file mode 100644 index 0000000000000..1a8897c829128 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/settings-sidebar-actions.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Acciones**. ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-advisories.md b/translations/es-ES/data/reusables/repositories/sidebar-advisories.md new file mode 100644 index 0000000000000..43ade4f435641 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-advisories.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haga clic en **Security advisories (Avisos de seguridad)**. ![Pestaña de avisos de seguridad](/assets/images/help/security/advisories-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/es-ES/data/reusables/repositories/sidebar-code-scanning-alerts.md new file mode 100644 index 0000000000000..133c7dd251be6 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **alertas de escaneo de código**. Opcionalmente, selecciona la herramienta de escaneo de código que utilizaste. ![pestaña de "Alertas de escaneo de código"](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md new file mode 100644 index 0000000000000..fdd8e95478284 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md @@ -0,0 +1 @@ +1. En la barra lateral de seguridad, da clic en **{% data variables.product.prodname_dependabot_alerts %}**. ![Pestaña {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-issue-pr.md b/translations/es-ES/data/reusables/repositories/sidebar-issue-pr.md new file mode 100644 index 0000000000000..ac1e240ced09d --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-issue-pr.md @@ -0,0 +1 @@ +1. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %}**Informes de problemas** o en {% octicon "git-pull-request" aria-label="The pull request icon" %}**Solicitudes de extracción**. ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-settings-issues-pull-requests.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-issues.md b/translations/es-ES/data/reusables/repositories/sidebar-issues.md new file mode 100644 index 0000000000000..29c90c226999b --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-issues.md @@ -0,0 +1 @@ +2. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %}**Informe de problemas**. ![Pestaña de informe de problemas](/assets/images/help/repository/repo-tabs-issues.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-moderation-reported-content.md b/translations/es-ES/data/reusables/repositories/sidebar-moderation-reported-content.md new file mode 100644 index 0000000000000..9220abe3a7da2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-moderation-reported-content.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Contenido reportado**. !["Contenido reportado" en la barra lateral de configuración del repositorio](/assets/images/help/repository/repo-settings-reported-content.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md new file mode 100644 index 0000000000000..86344532720c2 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md @@ -0,0 +1 @@ +1. Da clic en **Notificaciones**. ![Botón de notificaciones en la barra lateral](/assets/images/help/settings/notifications_menu.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-pr.md b/translations/es-ES/data/reusables/repositories/sidebar-pr.md new file mode 100644 index 0000000000000..acf69601ea6ef --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-pr.md @@ -0,0 +1 @@ +1. Debajo del nombre de tu repositorio, da clic en {% octicon "git-pull-request" aria-label="The pull request icon" %}**Solicitudes de extracción**. ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-security.md b/translations/es-ES/data/reusables/repositories/sidebar-security.md new file mode 100644 index 0000000000000..08919b826c9b8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-security.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de repositorio, da clic en **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**. ![Pestaña de seguridad](/assets/images/help/repository/security-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-settings.md b/translations/es-ES/data/reusables/repositories/sidebar-settings.md new file mode 100644 index 0000000000000..b0e17a8591e33 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-settings.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de repositorio, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Botón de configuración del repositorio](/assets/images/help/repository/repo-actions-settings.png) diff --git a/translations/es-ES/data/reusables/repositories/sidebar-wiki.md b/translations/es-ES/data/reusables/repositories/sidebar-wiki.md new file mode 100644 index 0000000000000..0e89e0e51cd7c --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/sidebar-wiki.md @@ -0,0 +1 @@ +1. Debajo de tu nombre de repositorio, da clic en {% octicon "book" aria-label="Book symbol" %}**Wiki**. ![Enlace de menú del Wiki](/assets/images/help/wiki/wiki_menu_link.png) diff --git a/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md new file mode 100644 index 0000000000000..60b005a4e76a8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}Si existe una regla de rama protegida en tu repositorio, la cual requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, la fusión por rebase, o ambas. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/start-line-comment.md b/translations/es-ES/data/reusables/repositories/start-line-comment.md new file mode 100644 index 0000000000000..810248301ffe9 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/start-line-comment.md @@ -0,0 +1 @@ +1. Pasa el puntero del mouse sobre la línea de código en donde quieras agregar un comentario, da clic en el icono azul de comentario.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} Para agregar un comentario con líneas múltiples, da clic y arrastra para seleccionar el rango de líneas y luego da clic en el icono azul de comentario.{% endif %} ![Icono de comentario azul](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/es-ES/data/reusables/repositories/submit-new-issue.md b/translations/es-ES/data/reusables/repositories/submit-new-issue.md new file mode 100644 index 0000000000000..99d68f14def80 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/submit-new-issue.md @@ -0,0 +1 @@ +1. Cuando termines, da clic en **Emitir nuevo informe de problemas**. diff --git a/translations/es-ES/data/reusables/repositories/submit-review.md b/translations/es-ES/data/reusables/repositories/submit-review.md new file mode 100644 index 0000000000000..e079e1d77f798 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/submit-review.md @@ -0,0 +1 @@ +1. Da clic en **Emitir revisión**. diff --git a/translations/es-ES/data/reusables/repositories/suggest-changes.md b/translations/es-ES/data/reusables/repositories/suggest-changes.md new file mode 100644 index 0000000000000..10268b1988cbe --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/suggest-changes.md @@ -0,0 +1 @@ +1. De forma opcional, para sugerir algún cambio específico a la línea{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} o líneas{% endif %}, da clic en {% octicon "diff" aria-label="The diff symbol" %} y luego edita el texto dentro del bloque de sugerencias. ![Bloque de sugerencia](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/es-ES/data/reusables/repositories/task-list-markdown.md b/translations/es-ES/data/reusables/repositories/task-list-markdown.md new file mode 100644 index 0000000000000..afb04a5bb2dfc --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/task-list-markdown.md @@ -0,0 +1,9 @@ +Para crear una lista de tareas, introduce los elementos de la lista con un caracter de espacio regular, seguido de `[ ]`. Para marcar una tarea como completada, utiliza `[x]`. + +``` +- [x] Finish my changes +- [ ] Push my commits to GitHub +- [ ] Open a pull request +``` + +![Lista de tareas generada](/assets/images/help/writing/task-list-rendered.png) diff --git a/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md b/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md new file mode 100644 index 0000000000000..24c546f2b809f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/tracks-vulnerabilities.md @@ -0,0 +1,5 @@ +Agregamos vulnerabilidades a la {% data variables.product.prodname_advisory_database %} desde las siguientes fuentes: +- La [National Vulnerability Database](https://nvd.nist.gov/) +- Una combinación de aprendizaje automático y revisión humana para detectar vulnerabilidades en confirmaciones públicas en {% data variables.product.prodname_dotcom %} +- Asesorías de seguridad que se reportan en {% data variables.product.prodname_dotcom %} +- La base de datos de [Asesorías de seguridad de npm](https://www.npmjs.com/advisories) database diff --git a/translations/es-ES/data/reusables/repositories/transfer-repository-steps.md b/translations/es-ES/data/reusables/repositories/transfer-repository-steps.md new file mode 100644 index 0000000000000..2ce7ede881c0f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/transfer-repository-steps.md @@ -0,0 +1,10 @@ +{% if currentVersion == "free-pro-team@latest" %} +1. En "Danger Zone" (Zona de peligro), haz clic en **Transfer** (Transferir). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer.png) +1. Lee la información acerca de transferir un repositorio, luego escribe el nombre del usuario u organización al que le quieres transferir la titularidad del repositorio. ![Información acerca de la transferencia del repositorio y campo para escribir el nombre de usuario del propietario nuevo](/assets/images/help/repository/transfer-repo-new-owner-name.png) +1. Lee las advertencias acerca de la posible pérdida de características en función de la suscripción del propietario nuevo. ![Advertencias acerca de la transferencia de un repositorio a una persona que usa un producto gratuito](/assets/images/help/repository/repo-transfer-free-plan-warnings.png) +1. Escribe el nombre del repositorio que quieres transferir, luego haz clic en **I understand, transfer this repository** (Comprendo, transferir este repositorio). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer-complete.png) +{% else %} +1. Da clic en **Transferir**. ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer.png) +1. Lee las advertencias e ingresa el nombre del repositorio para confirmar que lo has hecho. +1. Escribe el nombre del propietario nuevo y haz clic en **I understand, transfer this repo** (Comprendo, trasferir este repositorio). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer-complete.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/es-ES/data/reusables/repositories/two-dot-diff-comparison-example-urls.md new file mode 100644 index 0000000000000..23532d66d26d4 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -0,0 +1 @@ +Por ejemplo, esta URL utiliza los códigos de SHA acortados a siete caracteres para comparar las confirmaciones `c3a414e` y `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/es-ES/data/reusables/repositories/type-issue-title-and-description.md b/translations/es-ES/data/reusables/repositories/type-issue-title-and-description.md new file mode 100644 index 0000000000000..20ae5bf3662b3 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/type-issue-title-and-description.md @@ -0,0 +1 @@ +1. Teclea un título y descripción para tu informe de problemas. ![Un ejemplo de informe de problemas](/assets/images/help/issues/sample_issue.png) diff --git a/translations/es-ES/data/reusables/repositories/type-line-comment.md b/translations/es-ES/data/reusables/repositories/type-line-comment.md new file mode 100644 index 0000000000000..026672f6e5b9d --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/type-line-comment.md @@ -0,0 +1 @@ +1. Teclea tu comentario en el campo de comentario. ![Campo de comentario](/assets/images/help/pull_requests/comment-field.png) diff --git a/translations/es-ES/data/reusables/repositories/valid-community-issues.md b/translations/es-ES/data/reusables/repositories/valid-community-issues.md new file mode 100644 index 0000000000000..6363c3a421041 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/valid-community-issues.md @@ -0,0 +1 @@ +Para que se incluyan en el listado de perfiles de la comunidad, las plantillas de informe de problemas deben ubicarse en la carpeta `.github/ISSUE_TEMPLATE` y contener campos de `name:` y `about:` de YAML front matter válidos. diff --git a/translations/es-ES/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/es-ES/data/reusables/repositories/view-failed-job-results-superlinter.md new file mode 100644 index 0000000000000..58de8ec8cf7c1 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -0,0 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +1. Cualquier paso que falle se expandirá automáticamente para mostrar los resultados. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Resultados del flujo de trabajo de Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} +{% else %} +1. Expande el paso de **Ejecutar Super-Lnter** para ver los resultados. ![Resultados del flujo de trabajo de Super linter](/assets/images/help/repository/super-linter-workflow-results.png) +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/view-run-superlinter.md b/translations/es-ES/data/reusables/repositories/view-run-superlinter.md new file mode 100644 index 0000000000000..6537e80030710 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/view-run-superlinter.md @@ -0,0 +1 @@ +1. Desde la lista de ejecuciones de flujo de trabajo, da clic en el nombre de la ejecución que quieres ver. ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/superlinter-run-name.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/view-run.md b/translations/es-ES/data/reusables/repositories/view-run.md new file mode 100644 index 0000000000000..85ef725866a82 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/view-run.md @@ -0,0 +1 @@ +1. Desde la lista de ejecuciones de flujo de trabajo, da clic en el nombre de la ejecución que quieres ver. ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/run-name.png) diff --git a/translations/es-ES/data/reusables/repositories/view-specific-line-superlinter.md b/translations/es-ES/data/reusables/repositories/view-specific-line-superlinter.md new file mode 100644 index 0000000000000..77af379c3345a --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/view-specific-line-superlinter.md @@ -0,0 +1,10 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +1. De manera opcional, para obtener un enlace a una línea específica de los registros, haz clic en el número de línea del paso. Ahora podrás copiar el enlace de la barra de direcciones de tu buscador web. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Botón para copiar enlace](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![Botón para copiar enlace](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} +{% else %} +1. De manera opcional, para obtener un enlace a una línea específica de los registros, haz clic en el número de línea del paso. Ahora podrás copiar el enlace de la barra de direcciones de tu buscador web. ![Botón para copiar enlace](/assets/images/help/repository/copy-link-button.png) +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/workflow-notifications.md b/translations/es-ES/data/reusables/repositories/workflow-notifications.md new file mode 100644 index 0000000000000..12184e589e3f8 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/workflow-notifications.md @@ -0,0 +1,5 @@ +Si habilitas las notificaciones web o por correo electrónico para {% data variables.product.prodname_actions %}, recibirás una notificación cuando alguna ejecución de flujo de trabajo que hayas activado se complete. La notificación incluirá el estado de la ejecución de flujo de trabajo (que incluye ejecuciones exitosas, fallidas, neutrales y canceladas). También puedes elegir recibir una notificación solo cuando falle una ejecución de flujo de trabajo. + +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + +También puedes ver el estado de las ejecuciones de flujo de trabajo en la pestaña Actions (Acciones) de un repositorio. Para obtener más información, consulta la sección "[Administrar una ejecución de flujo de trabajo](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". diff --git a/translations/es-ES/data/reusables/repositories/you-can-fork.md b/translations/es-ES/data/reusables/repositories/you-can-fork.md new file mode 100644 index 0000000000000..0de96294b141b --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/you-can-fork.md @@ -0,0 +1,7 @@ +{% if currentVersion == "github-ae@latest" %}Si las políticas de tu empresa permiten bifurcar los repositorios internos y privados, puedes{% else %}Puedes{% endif %} bifurcar un repositorio hacia tu cuenta de usuario o hacia cualquier organización en donde tengas permisos de creación de repositorios. Para obtener más información, consulta "[Niveles de permisos para una organización](/articles/permission-levels-for-an-organization)". + +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + +Si tienes acceso a un repositorio privado y el propietario permite las bifurcaciones, puedes bifurcar el repositorio hacia tu cuenta de usuario o hacia cualquier organización en {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} en donde tengas permisos de creación de repositorios. {% if currentVersion == "free-pro-team@latest" %}No puedes bifurcar un repositorio privado hacia una organización que utilice {% data variables.product.prodname_free_team %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)".{% endif %} + +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/about-authorized-credentials.md b/translations/es-ES/data/reusables/saml/about-authorized-credentials.md new file mode 100644 index 0000000000000..a50d20815e598 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/about-authorized-credentials.md @@ -0,0 +1 @@ +Puedes ver cada token de acceso personal y llave de SSH que se haya autorizado a un miembro para obtener acceso a la API y a Git. Sólo se pueden ver los últimos caracteres de cada token o llave. De ser necesario, trabaja en conjunto con el miembro para determinar qué credenciales deberías revocar. diff --git a/translations/es-ES/data/reusables/saml/about-linked-identities.md b/translations/es-ES/data/reusables/saml/about-linked-identities.md new file mode 100644 index 0000000000000..af16354569dd1 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/about-linked-identities.md @@ -0,0 +1,3 @@ +Puedes ver la identidad de inicio de sesión único que cualquier miembro tenga vinculada con su cuenta de {% data variables.product.product_name %}. Cuando esté disponible, la entrada incluirá datos de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". + +Si un miembro vincula la identidad incorrecta a la cuenta de {% data variables.product.product_name %}, podrás revocar dicha identidad para permitir que el miembro lo intente de nuevo. diff --git a/translations/es-ES/data/reusables/saml/about-saml-access-enterprise-account.md b/translations/es-ES/data/reusables/saml/about-saml-access-enterprise-account.md new file mode 100644 index 0000000000000..ebaf2e8eb6d5e --- /dev/null +++ b/translations/es-ES/data/reusables/saml/about-saml-access-enterprise-account.md @@ -0,0 +1 @@ +Para acceder a los recursos de cada organización en {% data variables.product.product_name %}, el miembro debe tener una sesión activa de SAML en su buscador. Para acceder a los recursos protegidos de cada organización utilizando la API y Git, el miembro debe tener un token de acceso personal o llave de SSH que se le haya autorizado para su uso con la organización. Los propietarios de la empresa pueden ver y revocar la identidad vinculada de un miembro, las sesiones activas, o las credenciales autorizadas en cualquier momento. diff --git a/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..58afa24340695 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Los propietarios de empresa pueden habilitar el SSO de SAML y la autenticación centralizada a través de el IdP de SAML para todas las organizaciones que pertenezcan a su cuenta empresarial. Una vez que habilitas SAML SSO para tu cuenta de empresa, SAML SSO se habilita de manera predeterminada para todas las organizaciones que sean propiedad de tu cuenta de empresa. Se les exigirá a todos los miembros que se autentiquen usando SAML SSO para obtener acceso a las organizaciones de las que son miembros, y se les exigirá a los propietarios de empresas que se autentiquen usando SAML SSO cuando accesan a la cuenta de empresa. diff --git a/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md new file mode 100644 index 0000000000000..ba92edc2a7fbd --- /dev/null +++ b/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -0,0 +1 @@ +Si utilizas a Okta como tu IdP, puedes utilizar SCIM para adminsitrar la membrecía de tu organización en tu cuenta empresarial. SCIM invita a las personas o las elimina de una organización en tu cuenta empresarial automáticamente con base en si son miembros del grupo que corresponde a cada organización en tu IdP o no. diff --git a/translations/es-ES/data/reusables/saml/add-okta-application.md b/translations/es-ES/data/reusables/saml/add-okta-application.md new file mode 100644 index 0000000000000..0b10dd6c1d53a --- /dev/null +++ b/translations/es-ES/data/reusables/saml/add-okta-application.md @@ -0,0 +1 @@ +2. Da clic en **Agregar aplicación**. ![Botón de "Agregar aplicación" en la pestaña de Aplicaciones del tablero de Okta](/assets/images/help/saml/okta-add-application.png) diff --git a/translations/es-ES/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md b/translations/es-ES/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md new file mode 100644 index 0000000000000..594306395fb80 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md @@ -0,0 +1 @@ +Configurarás la administración de accesos e identidad para {% data variables.product.product_name %} al ingresar los detalles para tu IdP de SAML durante la inicialización. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)". diff --git a/translations/es-ES/data/reusables/saml/ae-uses-saml-sso.md b/translations/es-ES/data/reusables/saml/ae-uses-saml-sso.md new file mode 100644 index 0000000000000..48fff3d4ed97c --- /dev/null +++ b/translations/es-ES/data/reusables/saml/ae-uses-saml-sso.md @@ -0,0 +1 @@ +{% data variables.product.product_name %} utiliza el SSO de SAML para la autenticación de usuarios. Puedes administrar centralmente el acceso a {% data variables.product.prodname_ghe_managed %} desde un IdP que sea compatible con el estándar de SAML 2.0. diff --git a/translations/es-ES/data/reusables/saml/assert-the-administrator-attribute.md b/translations/es-ES/data/reusables/saml/assert-the-administrator-attribute.md new file mode 100644 index 0000000000000..aefcec9c16621 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/assert-the-administrator-attribute.md @@ -0,0 +1 @@ +Para convertir a una persona en propietario de la empresa, debes delegar el permiso de propiedad en tu IdP. Incluye el atributo de `administrator` en la aserción de SAML para la cuenta de usuario en el IdP, con el valor de `true`. Para obtener más información acerca de los propietarios de las empresas, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". diff --git a/translations/es-ES/data/reusables/saml/assign-yourself-to-okta.md b/translations/es-ES/data/reusables/saml/assign-yourself-to-okta.md new file mode 100644 index 0000000000000..f1d78020b4fca --- /dev/null +++ b/translations/es-ES/data/reusables/saml/assign-yourself-to-okta.md @@ -0,0 +1 @@ +1. Asigna la aplicación a tu usuario en Okta. Para obtener más información, consulta la sección [Asignar aplicaciones a los usuarios](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm) en la documentación de Okta. diff --git a/translations/es-ES/data/reusables/saml/click-enterprise-account-application.md b/translations/es-ES/data/reusables/saml/click-enterprise-account-application.md new file mode 100644 index 0000000000000..7ed854b3a7711 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/click-enterprise-account-application.md @@ -0,0 +1 @@ +1. Da clic en la etiqueta de la aplicación que creaste para tu cuenta empresarial. diff --git a/translations/es-ES/data/reusables/saml/click-person-revoke-credentials.md b/translations/es-ES/data/reusables/saml/click-person-revoke-credentials.md new file mode 100644 index 0000000000000..2dc2102774427 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/click-person-revoke-credentials.md @@ -0,0 +1 @@ +1. Da clic en el nombre del miembro cuyas credenciales autorizadas quisieras ver o revocar. diff --git a/translations/es-ES/data/reusables/saml/click-person-revoke-identity.md b/translations/es-ES/data/reusables/saml/click-person-revoke-identity.md new file mode 100644 index 0000000000000..3ffa3edfa3526 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/click-person-revoke-identity.md @@ -0,0 +1 @@ +1. Da clic en el nombre del miembro cuya identidad vinculada quisieras ver o revocar. diff --git a/translations/es-ES/data/reusables/saml/click-person-revoke-session.md b/translations/es-ES/data/reusables/saml/click-person-revoke-session.md new file mode 100644 index 0000000000000..2e07596954c58 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/click-person-revoke-session.md @@ -0,0 +1 @@ +1. Da clic en el nombre del miembro cuya sesión de SAML quisieras ver o revocar. diff --git a/translations/es-ES/data/reusables/saml/confirm-revoke-credentials.md b/translations/es-ES/data/reusables/saml/confirm-revoke-credentials.md new file mode 100644 index 0000000000000..4e3ee61f682c4 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/confirm-revoke-credentials.md @@ -0,0 +1 @@ +1. Lee la información, posteriormente, da clic en **Entiendo, revocar el acceso para este token**. diff --git a/translations/es-ES/data/reusables/saml/confirm-revoke-identity.md b/translations/es-ES/data/reusables/saml/confirm-revoke-identity.md new file mode 100644 index 0000000000000..e5f8bb13d3dd2 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/confirm-revoke-identity.md @@ -0,0 +1 @@ +1. Lee la información y da clic en **Revocar identidad externa**. diff --git a/translations/es-ES/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/es-ES/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md new file mode 100644 index 0000000000000..854ae0eac6c80 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md @@ -0,0 +1 @@ +Si no puedes ingresar a tu empresa porque {% data variables.product.product_name %} no puede comunicarse con tu IdP de SAML, puedes contactar a {% data variables.contact.github_support %}, quien te ayudará a acceder a {% data variables.product.product_name %} para actualizar la configuración del SSO de SAML. Para obtener más información, consulta la sección "[Recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)". diff --git a/translations/es-ES/data/reusables/saml/create-a-machine-user.md b/translations/es-ES/data/reusables/saml/create-a-machine-user.md new file mode 100644 index 0000000000000..32c721cd9b516 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/create-a-machine-user.md @@ -0,0 +1 @@ +Crea y utiliza una cuenta de usuario máquina dedicada en tu IdP para asociarla con la cuenta del primer dueño de la empresa en {% data variables.product.product_name %}. Almacena las credenciales para la cuenta de usuario de forma segura en un administrador de contraseñas. diff --git a/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md new file mode 100644 index 0000000000000..be784eeb4f31c --- /dev/null +++ b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md @@ -0,0 +1 @@ +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/es-ES/data/reusables/saml/okta-admin-button.md b/translations/es-ES/data/reusables/saml/okta-admin-button.md new file mode 100644 index 0000000000000..13c78bc376130 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-admin-button.md @@ -0,0 +1 @@ +1. En Okta, en la esquina superior derecha, da clic en **Admin**. ![Botón de Admin en Okta](/assets/images/help/saml/okta-admin-button.png) diff --git a/translations/es-ES/data/reusables/saml/okta-applications-click-ghec-application-label.md b/translations/es-ES/data/reusables/saml/okta-applications-click-ghec-application-label.md new file mode 100644 index 0000000000000..6da8596cfae40 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-applications-click-ghec-application-label.md @@ -0,0 +1 @@ +1. En la lista de aplicaciones, da clic en la etiqueta para la aplicación que creaste para la organización que utiliza {% data variables.product.prodname_ghe_cloud %}. ![Aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta](/assets/images/help/saml/okta-ghec-application.png) diff --git a/translations/es-ES/data/reusables/saml/okta-configure-api-integration.md b/translations/es-ES/data/reusables/saml/okta-configure-api-integration.md new file mode 100644 index 0000000000000..aa81cae71b2c9 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-configure-api-integration.md @@ -0,0 +1 @@ +1. Da clic en **Configurar la integraciòn de la API**. ![Botón "Configurar Integración de API" para la aplicación de Okta](/assets/images/help/saml/okta-configure-api-integration.png) diff --git a/translations/es-ES/data/reusables/saml/okta-dashboard-click-applications.md b/translations/es-ES/data/reusables/saml/okta-dashboard-click-applications.md new file mode 100644 index 0000000000000..b5c901f3cefb6 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-dashboard-click-applications.md @@ -0,0 +1 @@ +1. En el tablero de Okta, da clic en **Aplicaciones**. ![Elemento "Aplicaciones" en la barra de navegación del tablero de Okta](/assets/images/help/saml/okta-applications.png) diff --git a/translations/es-ES/data/reusables/saml/okta-edit-provisioning.md b/translations/es-ES/data/reusables/saml/okta-edit-provisioning.md new file mode 100644 index 0000000000000..7836cbc9ccab2 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-edit-provisioning.md @@ -0,0 +1,5 @@ +10. A la derecha de "Aprovisionar a la App", da clic en **Editar**. ![Botón "Editar" para las opciones de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-to-app-edit-button.png) +11. A la derecha de "Crear Usuarios", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Crear Usuarios" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-create-users.png) +12. A la derecha de "Actualizar Atributos de Usuario", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Actualizar Atributos de Usuario" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png) +13. A la derecha de "Desactivar Usuarios", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Desactivar Usuarios" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png) +14. Haz clic en **Save ** (guardar). ![Botón "Guardar" ára la configuración de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-save.png) diff --git a/translations/es-ES/data/reusables/saml/okta-enable-api-integration.md b/translations/es-ES/data/reusables/saml/okta-enable-api-integration.md new file mode 100644 index 0000000000000..8880fd4c1994a --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-enable-api-integration.md @@ -0,0 +1 @@ +1. Selecciona **Habilitar la Integraciòn de la API**. ![Casilla "Habilitar la integración de la API" para la aplicación de Okta](/assets/images/help/saml/okta-enable-api-integration.png) diff --git a/translations/es-ES/data/reusables/saml/okta-provisioning-tab.md b/translations/es-ES/data/reusables/saml/okta-provisioning-tab.md new file mode 100644 index 0000000000000..813ac462c23fd --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-provisioning-tab.md @@ -0,0 +1 @@ +1. Debajo del nombre de la aplicación, da clic en **Aprovisionamiento**. ![Pestaña de "Aprovisionar" para la aplicación de Okta](/assets/images/help/saml/okta-provisioning-tab.png) diff --git a/translations/es-ES/data/reusables/saml/okta-save-provisioning.md b/translations/es-ES/data/reusables/saml/okta-save-provisioning.md new file mode 100644 index 0000000000000..1f5ef8e4b4f67 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-save-provisioning.md @@ -0,0 +1 @@ +1. Haz clic en **Save ** (guardar). ![Botón "Guardar" ára la configuración de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-tab-save.png) diff --git a/translations/es-ES/data/reusables/saml/okta-sign-on-tab.md b/translations/es-ES/data/reusables/saml/okta-sign-on-tab.md new file mode 100644 index 0000000000000..28f0c1336712d --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-sign-on-tab.md @@ -0,0 +1 @@ +1. Debajo del nombre de la aplicación, da clic en **Iniciar sesión**. ![Pestaña "Registrarse" para la aplicación de Okta](/assets/images/help/saml/okta-sign-on-tab.png) diff --git a/translations/es-ES/data/reusables/saml/okta-view-setup-instructions.md b/translations/es-ES/data/reusables/saml/okta-view-setup-instructions.md new file mode 100644 index 0000000000000..f79dd8a08e504 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-view-setup-instructions.md @@ -0,0 +1 @@ +1. Debajo de "MÉTODOS DE REGISTRO", da clic en **Ver las instrucciones de configuración". ![Botón de "Ver instrucciones de configuración" en la pestaña "Registrarse" de la aplicación de Okta](/assets/images/help/saml/okta-view-setup-instructions.png) diff --git a/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md new file mode 100644 index 0000000000000..a464f145b6a26 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** No se requiere que los colaboradores externos se autentiquen con un IdP para acceder a los recursos de una organización que cuente con el SSO de SAML. Para obtener más información sobre los colaboradores externos, consulta la sección "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". + +{% endnote %} diff --git a/translations/es-ES/data/reusables/saml/revoke-authorized-credentials.md b/translations/es-ES/data/reusables/saml/revoke-authorized-credentials.md new file mode 100644 index 0000000000000..e7a118ae402da --- /dev/null +++ b/translations/es-ES/data/reusables/saml/revoke-authorized-credentials.md @@ -0,0 +1 @@ +1. Para revocar las credenciales, a la derecha de aquellas que quieras revocar, da clic en **Revocar**. ![Botón revocar](/assets/images/help/saml/revoke-credentials.png) diff --git a/translations/es-ES/data/reusables/saml/revoke-saml-session.md b/translations/es-ES/data/reusables/saml/revoke-saml-session.md new file mode 100644 index 0000000000000..3f755d3088cf1 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/revoke-saml-session.md @@ -0,0 +1 @@ +1. Para revocar una sesión, a la derecha de aquella que quieras revocar, da clic en **Revocar**. ![Botón revocar](/assets/images/help/saml/revoke-session.png) diff --git a/translations/es-ES/data/reusables/saml/revoke-sso-identity.md b/translations/es-ES/data/reusables/saml/revoke-sso-identity.md new file mode 100644 index 0000000000000..a4e367ac6409f --- /dev/null +++ b/translations/es-ES/data/reusables/saml/revoke-sso-identity.md @@ -0,0 +1 @@ +1. Para revocar la identidad vinculada, da clic en **Revocar** a la derecha de ésta. ![Botón revocar](/assets/images/help/saml/revoke-identity.png) diff --git a/translations/es-ES/data/reusables/saml/saml-identity-linked.md b/translations/es-ES/data/reusables/saml/saml-identity-linked.md new file mode 100644 index 0000000000000..0dab669030855 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/saml-identity-linked.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Identidad de SAML vinculada**. ![Identidad vinculada de SAML](/assets/images/help/saml/saml-identity-linked.png) diff --git a/translations/es-ES/data/reusables/saml/saml-session-oauth.md b/translations/es-ES/data/reusables/saml/saml-session-oauth.md new file mode 100644 index 0000000000000..edfd3436b4ff2 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/saml-session-oauth.md @@ -0,0 +1 @@ +Si perteneces a cualquier organización que requiera el inicio de sesión único de SAML, puede que se te pida autenticarte a través de tu proveedor de identidad antes de que se te autorice un {% data variables.product.prodname_oauth_app %}. Para obtener más información acerca de SAML, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". diff --git a/translations/es-ES/data/reusables/saml/saml-single-logout-not-supported.md b/translations/es-ES/data/reusables/saml/saml-single-logout-not-supported.md new file mode 100644 index 0000000000000..a54a71e0ce8fb --- /dev/null +++ b/translations/es-ES/data/reusables/saml/saml-single-logout-not-supported.md @@ -0,0 +1 @@ +{% data variables.product.product_name %} no es compatible con el cierre de sesión único de SAML. Para terminar una sesión de SAML activa, los usuarios deben salir directamente en tu IdP de SAML. diff --git a/translations/es-ES/data/reusables/saml/saml-supported-idps.md b/translations/es-ES/data/reusables/saml/saml-supported-idps.md new file mode 100644 index 0000000000000..c418507661b5d --- /dev/null +++ b/translations/es-ES/data/reusables/saml/saml-supported-idps.md @@ -0,0 +1,7 @@ +Ofrecemos soporte limitado para todos los proveedores de identidad que implementan SAML 2.0 estándar. Ofrecemos soporte oficial de estos proveedores de identidad que se han probado internamente: +- Active Directory Federation Services (AD FS) +- Azure Active Directory (Azure AD) +- Okta +- OneLogin +- PingOne +- Shibboleth diff --git a/translations/es-ES/data/reusables/saml/search-ghec-okta.md b/translations/es-ES/data/reusables/saml/search-ghec-okta.md new file mode 100644 index 0000000000000..44d467b5d0a03 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/search-ghec-okta.md @@ -0,0 +1 @@ +3. En el campo de búsqueda, teclea "GitHub Enterprise Cloud".![Campo "Buscar una aplicación" de Okta](/assets/images/help/saml/okta-search-for-an-application.png) diff --git a/translations/es-ES/data/reusables/saml/testing-saml-sso.md b/translations/es-ES/data/reusables/saml/testing-saml-sso.md new file mode 100644 index 0000000000000..cc174933143e0 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/testing-saml-sso.md @@ -0,0 +1 @@ +Cuando configuras el SSO de SAML en tu organización, puedes probar tu implementación sin que afecte a los miembros de tu organización cuando dejas sin marcar la opción **Requerir la autenticación con el SSO de SAML para todos los miembros de la organización _nombre de organización_**. diff --git a/translations/es-ES/data/reusables/saml/use-classic-ui.md b/translations/es-ES/data/reusables/saml/use-classic-ui.md new file mode 100644 index 0000000000000..840ba7ce0b049 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/use-classic-ui.md @@ -0,0 +1,3 @@ +Debes utilizar la "IU Clásica" en Okta. Para obtener más información, consulta la sección [Organized Navigation](https://developer.okta.com/blog/2017/09/25/all-new-developer-console#new-look--feel) en el blog de Okta. + +![Seleccionar "IU Clásica" en el selector de estilos de UI de Okta sobre el tablero](/assets/images/help/saml/okta-classic-ui.png) diff --git a/translations/es-ES/data/reusables/saml/view-authorized-credentials.md b/translations/es-ES/data/reusables/saml/view-authorized-credentials.md new file mode 100644 index 0000000000000..ad4f78f8c0f6a --- /dev/null +++ b/translations/es-ES/data/reusables/saml/view-authorized-credentials.md @@ -0,0 +1 @@ +1. Visualiza las credenciales autorizadas para el miembro debajo de "Credenciales autorizadas". diff --git a/translations/es-ES/data/reusables/saml/view-saml-sessions.md b/translations/es-ES/data/reusables/saml/view-saml-sessions.md new file mode 100644 index 0000000000000..97bca6424f7b1 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/view-saml-sessions.md @@ -0,0 +1 @@ +1. Visualiza las sesiones activas de SAML para el miembro debajo de "Sesiones de SAML activas". diff --git a/translations/es-ES/data/reusables/saml/view-sso-identity.md b/translations/es-ES/data/reusables/saml/view-sso-identity.md new file mode 100644 index 0000000000000..7f79c9d0cbcc5 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/view-sso-identity.md @@ -0,0 +1 @@ +1. Visualiza la identidad de SSO vinculada para el miembro debajo de "Identidad de SSO vinculada". diff --git a/translations/es-ES/data/reusables/saml/you-must-periodically-authenticate.md b/translations/es-ES/data/reusables/saml/you-must-periodically-authenticate.md new file mode 100644 index 0000000000000..0ccd4bac91233 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/you-must-periodically-authenticate.md @@ -0,0 +1 @@ +Debes autenticarte frecuentemente con tu IdP de SAML para obtener acceso a {% if currentVersion == "free-pro-team@latest" %}los recursos organizacionales en {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que te vuelvas a identificar para continuar. {% if currentVersion == "free-pro-team@latest" %}Puedes visualizar y administrar tus sesiones activas de SAML en tus ajustes de seguridad. Para obtener más información, consulta la sección "[Visualizar y administrar tus sesiones activas de SAML](/articles/viewing-and-managing-your-active-saml-sessions)".{% endif %} diff --git a/translations/es-ES/data/reusables/scim/after-you-configure-saml.md b/translations/es-ES/data/reusables/scim/after-you-configure-saml.md new file mode 100644 index 0000000000000..f1e92cdde4a2a --- /dev/null +++ b/translations/es-ES/data/reusables/scim/after-you-configure-saml.md @@ -0,0 +1 @@ +Predeterminadamente, tus IdP no se comunican con {% data variables.product.product_name %} automáticamente cuando asignas o desasignas la aplicación. {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}aprovisiona el acceso a tus recursos en {% else %}crea una cuenta de usuario {% endif %}utilizando Just-in-Time (JIT) de SAML aprovisionando la primera vez que alguien navega a {% if currentVersion == "free-pro-team@latest" %}tus recursos en {% endif %} {% data variables.product.product_name %} e inicia sesión autenticándose con tu IdP. Puede que necesites notificar a los usuarios manualmente cuando les otorgas acceso a {% data variables.product.product_name %}, y debes {% if currentVersion == "free-pro-team@latest" %}desaprovisionar el acceso manualmente {% else %}desactivar la cuenta de usuario manualmente en {% endif %}{% data variables.product.product_name %} durante el proceso de salida. Puedes utilizar SCIM para aprovisionar y desaprovisionar {% if currentVersion == "free-pro-team@latest" %}el acceso a las organizaciones que pertenezcan a tu empresa en las cuentas de usuario y el acceso de {% data variables.product.prodname_dotcom_the_website %} {% else %} para {% data variables.product.product_name %} {% endif %}automáticamente cuando asignas o desasignas la aplicación en tu IdP. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/scim/enterprise-account-scim.md b/translations/es-ES/data/reusables/scim/enterprise-account-scim.md new file mode 100644 index 0000000000000..c8c986ab5a8d0 --- /dev/null +++ b/translations/es-ES/data/reusables/scim/enterprise-account-scim.md @@ -0,0 +1 @@ +Si estás participando en el beta privado para el aprovisionamiento de usuario para cuentas empresariales, cuando habilites SAML para tu cuenta empresarial, se habilitará predeterminadamente el aprovisionamiento y desaprovisionamiento de SCIM en {% data variables.product.product_name %}. Puedes utilizar el aprovisionamiento para administrar la membrecía de la organización si configuras SCIM en tu IdP. diff --git a/translations/es-ES/data/reusables/scim/supported-idps.md b/translations/es-ES/data/reusables/scim/supported-idps.md new file mode 100644 index 0000000000000..3c34e31d2b525 --- /dev/null +++ b/translations/es-ES/data/reusables/scim/supported-idps.md @@ -0,0 +1,5 @@ +Los siguientes IdP pueden aprovisionar o desaprovisionar las cuentas de usuario en {% data variables.product.product_location %} utilizando SCIM. + +{% if currentVersion == "github-ae@latest" %} +- Azure AD +{% endif %} diff --git a/translations/es-ES/data/reusables/search/date_gt_lt.md b/translations/es-ES/data/reusables/search/date_gt_lt.md new file mode 100644 index 0000000000000..e25a9b2d393ef --- /dev/null +++ b/translations/es-ES/data/reusables/search/date_gt_lt.md @@ -0,0 +1 @@ +Cuando buscas una fecha, puedes utilizar los calificadores de mayor qué, menor qué y rango para filtrar aún más los resultados. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". diff --git a/translations/es-ES/data/reusables/search/requested_reviews_search.md b/translations/es-ES/data/reusables/search/requested_reviews_search.md new file mode 100644 index 0000000000000..e90c48dde3455 --- /dev/null +++ b/translations/es-ES/data/reusables/search/requested_reviews_search.md @@ -0,0 +1 @@ +Puedes encontrar una solicitud de extracción en donde se te haya solicitado una revisión, ya sea a ti o a algún equipo del que seas miembro, con el calificador de búsqueda `review-requested:[USERNAME]` o `team-review-requested:[TEAMNAME]`. Para obtener más información, consulta la sección "[Buscar informes de problemas y solicitudes de extracción](/articles/searching-issues-and-pull-requests)". diff --git a/translations/es-ES/data/reusables/search/requested_reviews_search_tip.md b/translations/es-ES/data/reusables/search/requested_reviews_search_tip.md new file mode 100644 index 0000000000000..4332eb09a3713 --- /dev/null +++ b/translations/es-ES/data/reusables/search/requested_reviews_search_tip.md @@ -0,0 +1,5 @@ +{% tip %} + +**Tip:** Puedes encontrar una solicitud de extracción en donde se te haya solicitado una revisión, ya sea a ti o a algún equipo del que seas miembro, con el calificador de búsqueda `review-requested:[USERNAME]` o `team-review-requested:[TEAMNAME]`. Para obtener más información, consulta la sección "[Buscar informes de problemas y solicitudes de extracción](/articles/searching-issues-and-pull-requests)". + +{% endtip %} diff --git a/translations/es-ES/data/reusables/search/required_login.md b/translations/es-ES/data/reusables/search/required_login.md new file mode 100644 index 0000000000000..54aebc09c41ae --- /dev/null +++ b/translations/es-ES/data/reusables/search/required_login.md @@ -0,0 +1 @@ +Debes haber iniciado sesión en una cuenta de usuario en {% data variables.product.product_name %} para buscar el código en todos los repositorios públicos. diff --git a/translations/es-ES/data/reusables/search/search_issues_and_pull_requests_shortcut.md b/translations/es-ES/data/reusables/search/search_issues_and_pull_requests_shortcut.md new file mode 100644 index 0000000000000..64fee4a7a06ca --- /dev/null +++ b/translations/es-ES/data/reusables/search/search_issues_and_pull_requests_shortcut.md @@ -0,0 +1 @@ +Puedes enfocar tu cursor en la barra de búsqueda que está sobre el listado de informe de problemas o solicitud de extracción con un atajo de teclado. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#issue-and-pull-request-lists)". diff --git a/translations/es-ES/data/reusables/search/syntax_tips.md b/translations/es-ES/data/reusables/search/syntax_tips.md new file mode 100644 index 0000000000000..92a0843e0fbb1 --- /dev/null +++ b/translations/es-ES/data/reusables/search/syntax_tips.md @@ -0,0 +1,8 @@ +{% tip %} + +**Tips:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + - Este artículo contiene enlaces a las búsquedas de muestra en el sitio web de {% data variables.product.prodname_dotcom_the_website %}, pero puedes utilizar los mismos filtros de búsqueda con {% data variables.product.product_name %}. En las búsquedas de ejemplos vinculadas, reemplaza `github.com` con el nombre de host para {% data variables.product.product_location %}.{% endif %} + - Para obtener una lista de sintaxis de búsqueda que puedas agregar a cualquier calificador para mejorar aún más tus resultados, consulta "[Comprender la sintaxis de búsqueda](/articles/understanding-the-search-syntax)". + - Utiliza comillas alrededor de los términos de búsqueda que contengan varias palabras. Por ejemplo, si deseas buscar propuestas con la etiqueta "In progress" (En curso), buscarías por la etiqueta `label:"in progress"`. Buscar no distingue entre mayúsculas y minúsculas. + +{% endtip %} diff --git a/translations/es-ES/data/reusables/search/you-can-search-globally.md b/translations/es-ES/data/reusables/search/you-can-search-globally.md new file mode 100644 index 0000000000000..d3fcf5d6d5a38 --- /dev/null +++ b/translations/es-ES/data/reusables/search/you-can-search-globally.md @@ -0,0 +1 @@ +Puedes buscar globalmente en todo {% data variables.product.product_name %} o limitar tu búsqueda a un repositorio o a una organización en particular diff --git a/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md b/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/es-ES/data/reusables/secret-scanning/api-beta.md b/translations/es-ES/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000000..4ac69e4a6a002 --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** La API de {% data variables.product.prodname_secret_scanning %} se encuentra actualmente en beta y está sujeta a cambios. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/secret-scanning/beta.md b/translations/es-ES/data/reusables/secret-scanning/beta.md new file mode 100644 index 0000000000000..82fdadded9388 --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/beta.md @@ -0,0 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/es-ES/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..27b76d94cfc8c --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Nota:** Tu administrador de sitio debe habilitar el {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_secret_scanning %} en tu aplicativo](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/es-ES/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md b/translations/es-ES/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md new file mode 100644 index 0000000000000..4e4e6e84995af --- /dev/null +++ b/translations/es-ES/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Si eres un investigador de seguridad, debes contactar directamente a los mantenedores para pedirles que creen asesorías de seguridad o que emitan CVEs en tu nombre en los repositorios que no administras. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/security/security-and-analysis-features-enable-read-only.md b/translations/es-ES/data/reusables/security/security-and-analysis-features-enable-read-only.md new file mode 100644 index 0000000000000..57959a33de7a7 --- /dev/null +++ b/translations/es-ES/data/reusables/security/security-and-analysis-features-enable-read-only.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Si habilitas las características de seguridad y de análisis, +{% data variables.product.company_short %} realizará análisis de solo lectura en tu repositorio. Para obtener más información, consulta la sección "[Acerca de cómo {% data variables.product.company_short %} utiliza tus datos](/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data)". +{% endif %} diff --git a/translations/es-ES/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/es-ES/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md new file mode 100644 index 0000000000000..ae8e3e369cdc9 --- /dev/null +++ b/translations/es-ES/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Nota**: No puedes inhabilitar algunas características de seguridad y análisis que están habilitadas predeterminadamente para los repositorios públicos. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/shortdesc/authenticating_github_app.md b/translations/es-ES/data/reusables/shortdesc/authenticating_github_app.md new file mode 100644 index 0000000000000..b3abd88d6ff6a --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/authenticating_github_app.md @@ -0,0 +1 @@ +Para obtener información sobre cómo autenticarte como una GitHub App, consulta la sección "[Opciones de Autenticación para GitHub Apps](/apps/building-github-apps/authentication-options-for-github-apps#authenticating-as-a-github-app)". diff --git a/translations/es-ES/data/reusables/shortdesc/authenticating_with_github_apps.md b/translations/es-ES/data/reusables/shortdesc/authenticating_with_github_apps.md new file mode 100644 index 0000000000000..17f72d31e84c5 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/authenticating_with_github_apps.md @@ -0,0 +1 @@ +Puedes autenticarte como una {% data variables.product.prodname_github_app %} o como una instalación. diff --git a/translations/es-ES/data/reusables/shortdesc/authorizing_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/authorizing_oauth_apps.md new file mode 100644 index 0000000000000..4a33e5da5de9a --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/authorizing_oauth_apps.md @@ -0,0 +1 @@ +Puedes habilitar a otros usuarios para que autoricen tu App de OAuth. diff --git a/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_github_apps.md b/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_github_apps.md new file mode 100644 index 0000000000000..967d4e1bf6d23 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_github_apps.md @@ -0,0 +1 @@ +Puedes reemplazar la insignia predeterminada en tu GitHub App si cargas tu propia imagen de logo y personalizas el fondo. diff --git a/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md new file mode 100644 index 0000000000000..bb4d2e94835c7 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md @@ -0,0 +1 @@ +Puedes reemplazar la insignia predeterminada en tu App de OAuth si cargas tu propia imagen de logo y personalizas el fondo. diff --git a/translations/es-ES/data/reusables/shortdesc/creating_github_apps.md b/translations/es-ES/data/reusables/shortdesc/creating_github_apps.md new file mode 100644 index 0000000000000..a38af482fe0f1 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/creating_github_apps.md @@ -0,0 +1 @@ +Puedes crear y registrar una GitHub App bajo tu cuenta personal o bajo cualquier organización en la que tengas acceso administrativo. diff --git a/translations/es-ES/data/reusables/shortdesc/creating_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/creating_oauth_apps.md new file mode 100644 index 0000000000000..760c0f64faca5 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/creating_oauth_apps.md @@ -0,0 +1 @@ +Puedes crear y registrar una App de OAuth bajo tu cuenta personal o bajo cualquier organización en la que tengas acceso administrativo. Cuando ceras tu app de OAuth, recuerda proteger tu privacidad al utilizar únicamente la información que consideras pública. diff --git a/translations/es-ES/data/reusables/shortdesc/deleting_github_apps.md b/translations/es-ES/data/reusables/shortdesc/deleting_github_apps.md new file mode 100644 index 0000000000000..60cda19199a28 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/deleting_github_apps.md @@ -0,0 +1 @@ +Puedes borrar las GitHub Apps cuando ya no las utilices. diff --git a/translations/es-ES/data/reusables/shortdesc/deleting_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/deleting_oauth_apps.md new file mode 100644 index 0000000000000..f5731e4e80157 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/deleting_oauth_apps.md @@ -0,0 +1 @@ +Puedes borrar las Apps de OAuth cuando ya no las utilices. diff --git a/translations/es-ES/data/reusables/shortdesc/editing_permissions_for_github_apps.md b/translations/es-ES/data/reusables/shortdesc/editing_permissions_for_github_apps.md new file mode 100644 index 0000000000000..8ad4c69506d77 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/editing_permissions_for_github_apps.md @@ -0,0 +1 @@ +Después de registrar una GitHub App, puedes modificar sus permisos. diff --git a/translations/es-ES/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md b/translations/es-ES/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md new file mode 100644 index 0000000000000..df319723abda6 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md @@ -0,0 +1 @@ +Tu GitHub App puede realizar acciones en nombre de un usuario, como crear un informe de problemas, crear un despliegue, y utilizar otras terminales compatibles. diff --git a/translations/es-ES/data/reusables/shortdesc/iso_8601.md b/translations/es-ES/data/reusables/shortdesc/iso_8601.md new file mode 100644 index 0000000000000..87070e39a6faf --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/iso_8601.md @@ -0,0 +1 @@ +Esta es una marca de tiempo en formato [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601): `AAAA-MM-DDTHH:MM:SSZ`. diff --git a/translations/es-ES/data/reusables/shortdesc/making-a-github-app-public-or-private.md b/translations/es-ES/data/reusables/shortdesc/making-a-github-app-public-or-private.md new file mode 100644 index 0000000000000..1aa24b6b7ef1a --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/making-a-github-app-public-or-private.md @@ -0,0 +1 @@ +Cuando configuras una GitHub App, puedes hacer que su instalación sea pública para que cualquier usario u organización de GitHub pueda instalarla, o privada para que solo la puedas instalar en la cuenta que la creó. diff --git a/translations/es-ES/data/reusables/shortdesc/modifying_github_apps.md b/translations/es-ES/data/reusables/shortdesc/modifying_github_apps.md new file mode 100644 index 0000000000000..22d20675c1b56 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/modifying_github_apps.md @@ -0,0 +1 @@ +Después de crear una GitHub App, puedes hacerle cambios. diff --git a/translations/es-ES/data/reusables/shortdesc/modifying_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/modifying_oauth_apps.md new file mode 100644 index 0000000000000..edf8f666724a2 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/modifying_oauth_apps.md @@ -0,0 +1 @@ +Despues de crear y registrar una App de OAuth, puedes hacerle cambios. diff --git a/translations/es-ES/data/reusables/shortdesc/permissions_github_apps.md b/translations/es-ES/data/reusables/shortdesc/permissions_github_apps.md new file mode 100644 index 0000000000000..7181e277591b5 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/permissions_github_apps.md @@ -0,0 +1 @@ +Cuando creas una GitHub App, configuras los permisos que definen los recursos a los cuales puede acceder a través de la API de REST. diff --git a/translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md new file mode 100644 index 0000000000000..a0de297409cf4 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md @@ -0,0 +1 @@ +Los límites de tasa para las GitHub Apps ayudan a controlar la tasa de tráfico. diff --git a/translations/es-ES/data/reusables/shortdesc/suspending_a_github_app.md b/translations/es-ES/data/reusables/shortdesc/suspending_a_github_app.md new file mode 100644 index 0000000000000..e11e92f6192d2 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/suspending_a_github_app.md @@ -0,0 +1 @@ +Puedes bloquear temporalmente el acceso de una {% data variables.product.prodname_github_app %} a los recursos de tu cuenta si la suspendes. diff --git a/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_github_apps.md b/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_github_apps.md new file mode 100644 index 0000000000000..28b7aff5fd37a --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_github_apps.md @@ -0,0 +1 @@ +Puedes transferir la propiedad de una GitHub App a otro usuario u organización. diff --git a/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md new file mode 100644 index 0000000000000..de48d701ada45 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md @@ -0,0 +1 @@ +Puedes transferir la propiedad de una App de OAuth a otro usuario u organización. diff --git a/translations/es-ES/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md new file mode 100644 index 0000000000000..c3a2f108ac0c7 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md @@ -0,0 +1 @@ +Cuando intercambias un código por un token de acceso, existe un conjunto de errores adicionales que pueden presentarse. El formato de estas respuestas se determina por el encabezado de aceptación que pases. diff --git a/translations/es-ES/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md new file mode 100644 index 0000000000000..b802be22f503d --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md @@ -0,0 +1 @@ +Cuando obtienes un token de OAuth para un usuario, pueden ocurrir algunos errores durante la fase inicial de solicitud de autorización. diff --git a/translations/es-ES/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md b/translations/es-ES/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md new file mode 100644 index 0000000000000..9c5d10b065e90 --- /dev/null +++ b/translations/es-ES/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md @@ -0,0 +1 @@ +Los alcances te permiten especificar exactamente el tipo de acceso que necesitas. Los alcances _limitan_ el acceso para los tokens de OAuth. No otorgan ningún permiso adicional más allá de aquél que el usuario ya tiene. diff --git a/translations/es-ES/data/reusables/sponsors/accept-legal-terms.md b/translations/es-ES/data/reusables/sponsors/accept-legal-terms.md new file mode 100644 index 0000000000000..8129f38507151 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/accept-legal-terms.md @@ -0,0 +1 @@ +1. Revisa las [Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms) y la [Declaración de Privacidad de {% data variables.product.prodname_dotcom %}](/articles/github-privacy-statement), posteriormente da clic en **Únete a la lista de espera**. diff --git a/translations/es-ES/data/reusables/sponsors/activity-tab.md b/translations/es-ES/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..0eb300f274d46 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Actividad**. ![Pestaña de actividad](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/add-active-triggers.md b/translations/es-ES/data/reusables/sponsors/add-active-triggers.md new file mode 100644 index 0000000000000..583aa902ba86e --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-active-triggers.md @@ -0,0 +1 @@ +1. Para recibir actualizaciones del Evento de Patrocinio, selecciona **Activo**. ![Seleccionar eventos activos](/assets/images/help/sponsors/webhook-active.png) diff --git a/translations/es-ES/data/reusables/sponsors/add-introduction.md b/translations/es-ES/data/reusables/sponsors/add-introduction.md new file mode 100644 index 0000000000000..3be76170ed16e --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-introduction.md @@ -0,0 +1 @@ +1. Debajo de "introducción", teclea una descripción del trabajo que realizarás con tus patrocinios. ![Campo de texto para detalles de perfil](/assets/images/help/sponsors/introduction-box.png) diff --git a/translations/es-ES/data/reusables/sponsors/add-more-tiers.md b/translations/es-ES/data/reusables/sponsors/add-more-tiers.md new file mode 100644 index 0000000000000..41dc59e2da60e --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-more-tiers.md @@ -0,0 +1 @@ + 1. Repite los pasos anteriores hasta que hayas publicado todos los niveles que quieres ofrecer. diff --git a/translations/es-ES/data/reusables/sponsors/add-payload-url.md b/translations/es-ES/data/reusables/sponsors/add-payload-url.md new file mode 100644 index 0000000000000..6480484b6bfc1 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-payload-url.md @@ -0,0 +1 @@ +1. Escribe una URL de carga, luego opcionalmente personaliza la configuración. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/#creating-webhooks)". ![Campos para la URL de carga y otras opciones de personalización](/assets/images/help/sponsors/webhook-payload-url.png) diff --git a/translations/es-ES/data/reusables/sponsors/add-webhook.md b/translations/es-ES/data/reusables/sponsors/add-webhook.md new file mode 100644 index 0000000000000..139d82c698ee3 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-webhook.md @@ -0,0 +1 @@ +1. Haz clic en **Add webhook** (Agregar webhook). ![Botón para agregar webhook en la barra lateral Webhooks](/assets/images/help/sponsors/add-webhook-sponsors-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/billing-switcher.md b/translations/es-ES/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000000..ec2f61b53cbfb --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Opcionalmente, para administrar tu patrocinio en nombre de una organización, en la esquina superior izquierda, utiliza el menú desplegable de **Ajustes personales** y da clic en la organización. ![Menú desplegable para cambiar de cuenta para los ajustes](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/es-ES/data/reusables/sponsors/change-tier.md b/translations/es-ES/data/reusables/sponsors/change-tier.md new file mode 100644 index 0000000000000..e2c20ac2c198b --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/change-tier.md @@ -0,0 +1 @@ +1. Debajo de "{% data variables.product.prodname_sponsors %}", a la derecha de la cuenta patrocinada, da clic en {% octicon "triangle-down" aria-label="The down triangle octicon" %} junto con tu cantidad de nivel y luego da clic en **cambiar nivel**. ![Botón de cambiar nivel](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/es-ES/data/reusables/sponsors/choose-updates.md b/translations/es-ES/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000000..f6ee9116cfa71 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/choose-updates.md @@ -0,0 +1 @@ +4. Decide si quieres recibir actualizaciones por correo electrónico desde la cuenta patrocinada y después selecciona o deselecciona "Recibir actualizaciones desde _CUENTA_". ![Casilla de verificación para recibir actualizaciones de la cuenta patrocinada](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/es-ES/data/reusables/sponsors/click-add-tier.md b/translations/es-ES/data/reusables/sponsors/click-add-tier.md new file mode 100644 index 0000000000000..a224aba3acbb8 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/click-add-tier.md @@ -0,0 +1 @@ +1. En la parte inferior de la página, da clic en **Agregar un nivel**. ![Botón de agregar nivel](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/confirm-add-webhook.md b/translations/es-ES/data/reusables/sponsors/confirm-add-webhook.md new file mode 100644 index 0000000000000..c90594754284a --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/confirm-add-webhook.md @@ -0,0 +1 @@ +1. Da clic en **Crear webhook**. ![Botón de crear webhook en la barra lateral de Webhooks](/assets/images/help/sponsors/create-webhook-sponsors-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/contact-info.md b/translations/es-ES/data/reusables/sponsors/contact-info.md new file mode 100644 index 0000000000000..21c9ed24f3d58 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/contact-info.md @@ -0,0 +1 @@ +1. Sigue las propuestas para completar tu información de contacto. diff --git a/translations/es-ES/data/reusables/sponsors/country-of-residence.md b/translations/es-ES/data/reusables/sponsors/country-of-residence.md new file mode 100644 index 0000000000000..f7b71bb6f1fbe --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/country-of-residence.md @@ -0,0 +1,2 @@ +1. Debajo de "País o región de residencia", utiliza el menú desplegable y selecciona tu ubicación de residencia. ![Menú desplegable de país o región de residencia](/assets/images/help/sponsors/country-of-residence-drop-down.png) +2. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/data/reusables/sponsors/create-stripe-account.md b/translations/es-ES/data/reusables/sponsors/create-stripe-account.md new file mode 100644 index 0000000000000..39a619c541955 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/create-stripe-account.md @@ -0,0 +1,2 @@ +1. Da clic en **Cuenta de Stripe Connect**. ![Enlace para crear la cuenta de Stripe Connect](/assets/images/help/sponsors/create-stripe-connect-account.png) +2. Sigue las indicaciones para crear tu cuenta. diff --git a/translations/es-ES/data/reusables/sponsors/double-check-stripe-info.md b/translations/es-ES/data/reusables/sponsors/double-check-stripe-info.md new file mode 100644 index 0000000000000..ed23abf61d658 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/double-check-stripe-info.md @@ -0,0 +1 @@ +Al solicitar una cuenta Stripe Connect, asegúrate de que toda la información sea correcta antes de enviar tu solicitud. Una vez que enviaste tu solicitud, es difícil actualizar la información de identidad, como tu nombre y fecha de nacimiento. diff --git a/translations/es-ES/data/reusables/sponsors/draft-new-update.md b/translations/es-ES/data/reusables/sponsors/draft-new-update.md new file mode 100644 index 0000000000000..5d8b27e202647 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/draft-new-update.md @@ -0,0 +1 @@ +4. A la derecha de "Email updates to your sponsorss" (Actualizaciones por correo electrónico para tus patrocinadores), haz clic en **New update** (Actualización nueva). ![Botón New update (Actualización nueva)](/assets/images/help/sponsors/new-update-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/edit-bank-information.md b/translations/es-ES/data/reusables/sponsors/edit-bank-information.md new file mode 100644 index 0000000000000..882bca0c04887 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/edit-bank-information.md @@ -0,0 +1 @@ +4. En "Payouts information" (Información de pago), haz clic en **Edit your bank information** (Editar tu información bancaria). ![Editar tu enlace de información bancaria](/assets/images/help/sponsors/edit-bank-info.png) diff --git a/translations/es-ES/data/reusables/sponsors/edit-featured-work.md b/translations/es-ES/data/reusables/sponsors/edit-featured-work.md new file mode 100644 index 0000000000000..0676a739f010d --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/edit-featured-work.md @@ -0,0 +1,3 @@ +1. Opcionalmente, escoge los repositorios que se exhiben en tu perfil de {% data variables.product.prodname_sponsors %}. + - A la derecha de "Trabajo destacado", da clic en **Editar**. ![Botón de editar para trabajo destacado](/assets/images/help/sponsors/featured-work-edit-button.png) + - Selecciona hasta 6 repositorios y luego da clic en **Guardar**. ![Casillas para seleccionar los repositorios](/assets/images/help/sponsors/featured-work-select.png) diff --git a/translations/es-ES/data/reusables/sponsors/edit-goal.md b/translations/es-ES/data/reusables/sponsors/edit-goal.md new file mode 100644 index 0000000000000..e7e1c0756b8bd --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/edit-goal.md @@ -0,0 +1 @@ +1. A la derecha de tu meta, da clic en **Editar**. ![Botón editar](/assets/images/help/sponsors/edit-goal-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/edit-tier.md b/translations/es-ES/data/reusables/sponsors/edit-tier.md new file mode 100644 index 0000000000000..57012f3cb1345 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/edit-tier.md @@ -0,0 +1 @@ +1. A la derecha del nivel que quieras editar, da clic en **Editar**. ![Botón Edit tier (Editar nivel)](/assets/images/help/sponsors/edit-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/github-contact-applicants.md b/translations/es-ES/data/reusables/sponsors/github-contact-applicants.md new file mode 100644 index 0000000000000..33aedc6add3da --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/github-contact-applicants.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} podría contactar a los solicitantes o participantes de {% data variables.product.prodname_sponsors %} pidiendo información adicional sobre su perfil o actividad de patrocinio para determinar la elegibilidad de dicho patrocinio o candidatura, o como parte de una investigación para la violación potencial de las condiciones. diff --git a/translations/es-ES/data/reusables/sponsors/github-review-app.md b/translations/es-ES/data/reusables/sponsors/github-review-app.md new file mode 100644 index 0000000000000..eafd3d5e915af --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/github-review-app.md @@ -0,0 +1 @@ +Es posible que {% data variables.product.prodname_dotcom %} tarde algunos días en revisar tu aplicación. Una vez que aprobemos tu aplicación, tu perfil automáticamente estará activo en [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-ES/data/reusables/sponsors/legal-additional-terms.md b/translations/es-ES/data/reusables/sponsors/legal-additional-terms.md new file mode 100644 index 0000000000000..e4233f92f0893 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/legal-additional-terms.md @@ -0,0 +1 @@ +El {% data variables.product.prodname_matching_fund %} es un regalo diseñado para motivar el financiamiento comunitario del trabajo realizado en código abierto y está sujeto a términos y condiciones adicionales. Para obtener información detallada sobre el {% data variables.product.prodname_matching_fund %}, consulta las "[Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms)". diff --git a/translations/es-ES/data/reusables/sponsors/manage-existing-webhooks.md b/translations/es-ES/data/reusables/sponsors/manage-existing-webhooks.md new file mode 100644 index 0000000000000..f5ee044875e64 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/manage-existing-webhooks.md @@ -0,0 +1 @@ +1. Para editar un webhook existente, da clic en **Editar**. Para eliminar un webhook existente, da clic en **Borrar**. ![Botones para administrar un webhook](/assets/images/help/sponsors/webhook-edit-delete-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/manage-sponsorship.md b/translations/es-ES/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000000..cdb5ecd16ecb2 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. A la derecha de tu nivel actual, da clic en **Administrar**. ![Botón para administrar tu patrocinio](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/es-ES/data/reusables/sponsors/manage-updates-for-orgs.md new file mode 100644 index 0000000000000..a7eaaf6393f3f --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +1 @@ +Puedes designar qué dirección de correo electrónico recibe actualizaciones de las cuentas que patrocina tu organización. Para obtener más información, consulta la sección "[Administrar las actualizaciones de las cuentas que patrocina tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)". diff --git a/translations/es-ES/data/reusables/sponsors/matching-fund-eligible.md b/translations/es-ES/data/reusables/sponsors/matching-fund-eligible.md new file mode 100644 index 0000000000000..a85734aa0e318 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/matching-fund-eligible.md @@ -0,0 +1 @@ +El periodo de elegibilidad para el {% data variables.product.prodname_matching_fund %} ha terminado. Las aplicaciones que se reciban después de la fecha límite del 1 de enero de 2020 no serán elegibles para el {% data variables.product.prodname_matching_fund %}. diff --git a/translations/es-ES/data/reusables/sponsors/maximum-tier.md b/translations/es-ES/data/reusables/sponsors/maximum-tier.md new file mode 100644 index 0000000000000..8b45dc0040c35 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/maximum-tier.md @@ -0,0 +1 @@ +El precio máximo es de $12,000 dólares estadounidenses mensuales. diff --git a/translations/es-ES/data/reusables/sponsors/meet-the-team.md b/translations/es-ES/data/reusables/sponsors/meet-the-team.md new file mode 100644 index 0000000000000..8d7ca20c24793 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/meet-the-team.md @@ -0,0 +1,5 @@ +1. Opcionalmente, elige a los miembros de la organización que están resaltados en tu perfil de {% data variables.product.prodname_sponsors %}. + - A la derecha de "Conoce al equipo", da clic en **Editar**. + ![Botón de editar miembros de organización en el perfil](/assets/images/help/sponsors/edit-org-members-profile-button.png) + - Selecciona hasta seis miembros de la organización y luego da clic en **Guardar**. ![Seleccionar miembros de la organización que se han resaltado](/assets/images/help/sponsors/select-highlighted-org-members.png) + - Opcionalmente, debajo de cada nombre de miembro resaltado, teclea una descripción del mismo. ![Descripción de los miembros de la roganización que se han resaltado](/assets/images/help/sponsors/description-highlighted-org-members.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-github-sponsors.md b/translations/es-ES/data/reusables/sponsors/navigate-to-github-sponsors.md new file mode 100644 index 0000000000000..9b012a163e760 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-github-sponsors.md @@ -0,0 +1 @@ +1. Navega a [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-payouts-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-payouts-tab.md new file mode 100644 index 0000000000000..b1fc1d59b42bb --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-payouts-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Pagos**. ![Pestaña de niveles de patrocinio](/assets/images/help/sponsors/payouts-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-profile-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-profile-tab.md new file mode 100644 index 0000000000000..c9a44cd179c2c --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-profile-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Detalles de perfil**. ![Pestaña de detalles de perfil](/assets/images/help/sponsors/profile-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md new file mode 100644 index 0000000000000..deb67e590b93f --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Niveles de patrocinio**. ![Pestaña de niveles de patrocinio](/assets/images/help/sponsors/sponsor-tiers-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000000..077f7a4b75cdc --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. En {% data variables.product.product_name %}, navega al perfil de la cuenta patrocinada. diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000000..980c618defe27 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. En la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y, posteriormente, da cilc en **{% data variables.product.prodname_sponsors %}**. ![Botón de {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. Si se muestra una lista de tus cuentas patrocinadas y elegiles, a la derecha de la cuenta que quieras administrar, da clic en **Tablero**. ![Botón de tablero para patrocinadores del desarrollador](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-tab.md new file mode 100644 index 0000000000000..1e3bf44b1ea45 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-sponsors-tab.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, da clic en **Tus patrocinadores**. ![Pestaña de patrocinadores](/assets/images/help/sponsors/sponsors-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-webhooks-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-webhooks-tab.md new file mode 100644 index 0000000000000..78b8ed9faf3c8 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-webhooks-tab.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, da clic en **Webhooks**. ![Pestaña de webhooks](/assets/images/help/sponsors/webhooks-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/navigate-to-your-goals-tab.md b/translations/es-ES/data/reusables/sponsors/navigate-to-your-goals-tab.md new file mode 100644 index 0000000000000..65c2cfdd7a0d5 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/navigate-to-your-goals-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Tus metas**. ![Pestaña de tus metas](/assets/images/help/sponsors/your-goals-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/no-fees.md b/translations/es-ES/data/reusables/sponsors/no-fees.md new file mode 100644 index 0000000000000..2df52e45af28a --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/no-fees.md @@ -0,0 +1 @@ +{% data variables.product.prodname_sponsors %} no cobra ninguna cuota por patrocinio de las cuentas de usuario, así que el 100% de éstos van a la organización o al desarrollador patrocinado. No habrá la cueta de 10% para patrocinios de las organizaciones durante el beta. diff --git a/translations/es-ES/data/reusables/sponsors/no-refunds.md b/translations/es-ES/data/reusables/sponsors/no-refunds.md new file mode 100644 index 0000000000000..abd192f3a6b12 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/no-refunds.md @@ -0,0 +1 @@ +No se realizan reembolsos de pagos para {% data variables.product.prodname_sponsors %}. diff --git a/translations/es-ES/data/reusables/sponsors/opt-in-to-being-featured.md b/translations/es-ES/data/reusables/sponsors/opt-in-to-being-featured.md new file mode 100644 index 0000000000000..7679dd3907c25 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/opt-in-to-being-featured.md @@ -0,0 +1 @@ +1. Opcionalmente, selecciona **Ingresar para ser candidato potencial de github.com/sponsors**. ![Casilla para ingresar para ser considerado](/assets/images/help/sponsors/opt-in-to-being-featured.png) diff --git a/translations/es-ES/data/reusables/sponsors/org-sponsored-choose-updates.md b/translations/es-ES/data/reusables/sponsors/org-sponsored-choose-updates.md new file mode 100644 index 0000000000000..d2d41a3bcd034 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/org-sponsored-choose-updates.md @@ -0,0 +1 @@ +4. Decide si quieres recibir actualizaciones por correo electrónico de la organización patrocinada y luego selecciona o deselecciona "Recibir actualizaciones de _ORGANIZACIÓN_." ![Casilla para recibir actualizaciones de la organización patrocinada](/assets/images/help/sponsors/org-updates-checkbox-manage.png) diff --git a/translations/es-ES/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/es-ES/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000000..6ece9c65e550d --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Los patrocinios en nombre de una organización se encuentran actualmente en beta y están sujetos a cambios. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/overview-tab.md b/translations/es-ES/data/reusables/sponsors/overview-tab.md new file mode 100644 index 0000000000000..004a8bf7c627f --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/overview-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Resumen**. ![Pestaña de resumen](/assets/images/help/sponsors/overview-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000000..d0d6f06bafec0 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +1 @@ +1. Opcionalmente, si estás haciendo un patrocinio como una organización, para pagar una cantidad prorrateada en vez de hacer un pago mensual completo, debajo de "Vence hoy", da clic en **Pagar $X.XX prorrateados hoy**. ![Enlace para pagar una cantidad prorrateada](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/payout-info.md b/translations/es-ES/data/reusables/sponsors/payout-info.md new file mode 100644 index 0000000000000..55f4306875550 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/payout-info.md @@ -0,0 +1 @@ +Para obtener información acerca de los tiempos de pago de {% data variables.product.prodname_sponsors %}, consulta la sección "[Condiciones Adicionales de GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms#43-payment-timing)". diff --git a/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md new file mode 100644 index 0000000000000..6e8d08c906ba1 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md @@ -0,0 +1 @@ +Si estás patrocinando a alguien en nombre de tu cuenta de usuario, inmediatamente se te cargará una cantidad prorrateada por el tiempo hasta que llegue tu próxima fecha de facturación normal. Si estás patrocinando a alguien en nombre de una organización, puedes elegir pagar la cantidad prorrateada o hacer un pago completo mensual. diff --git a/translations/es-ES/data/reusables/sponsors/publish-goal.md b/translations/es-ES/data/reusables/sponsors/publish-goal.md new file mode 100644 index 0000000000000..3300f86cb8368 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/publish-goal.md @@ -0,0 +1 @@ +1. Da clic en **Publicar**. ![Botón Publicar](/assets/images/help/sponsors/publish-goal-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/publish-sponsor-update.md b/translations/es-ES/data/reusables/sponsors/publish-sponsor-update.md new file mode 100644 index 0000000000000..88fca3d181d5c --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/publish-sponsor-update.md @@ -0,0 +1 @@ +7. Da clic en **Publicar**. diff --git a/translations/es-ES/data/reusables/sponsors/request-approval.md b/translations/es-ES/data/reusables/sponsors/request-approval.md new file mode 100644 index 0000000000000..8d6719314116c --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/request-approval.md @@ -0,0 +1 @@ +1. Haz clic en **Request approval** (Solicitar aprobación). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/sponsors/request-approval-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/retire-goal.md b/translations/es-ES/data/reusables/sponsors/retire-goal.md new file mode 100644 index 0000000000000..4cfc00bfaa789 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/retire-goal.md @@ -0,0 +1,2 @@ +1. Al final de la página, da clic en **Retrar**. ![El botón de retirar](/assets/images/help/sponsors/retire-goal-button.png) +2. Lee la advertencia y da clic en **OK**. ![Advertencia acerca de retirar una meta](/assets/images/help/sponsors/confirm-retire-goal.png) diff --git a/translations/es-ES/data/reusables/sponsors/retire-tier.md b/translations/es-ES/data/reusables/sponsors/retire-tier.md new file mode 100644 index 0000000000000..48336675cfce1 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/retire-tier.md @@ -0,0 +1 @@ +7. Para retirar un nivel, da clic en **Retirar nivel** y luego da clic en **OK**. ![Botón Retire tier (Retirar nivel)](/assets/images/help/sponsors/retire-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md new file mode 100644 index 0000000000000..837f5bfa7f0b8 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md @@ -0,0 +1 @@ +1. Revisa tu nivel y da clic en **Publicar nivel**. ![Botón de publicar nivel](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/save-profile.md b/translations/es-ES/data/reusables/sponsors/save-profile.md new file mode 100644 index 0000000000000..1e555637563ce --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/save-profile.md @@ -0,0 +1 @@ +1. Haz clic en **Update profile (Actualizar perfil)**. diff --git a/translations/es-ES/data/reusables/sponsors/save-tier-draft.md b/translations/es-ES/data/reusables/sponsors/save-tier-draft.md new file mode 100644 index 0000000000000..c1899371f7549 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/save-tier-draft.md @@ -0,0 +1 @@ +1. Da clic en **Guardar borrador**. ![Botón de guardar borrador](/assets/images/help/sponsors/save-tier-draft.png) diff --git a/translations/es-ES/data/reusables/sponsors/select-a-tier.md b/translations/es-ES/data/reusables/sponsors/select-a-tier.md new file mode 100644 index 0000000000000..9e6cbb42ae70e --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/select-a-tier.md @@ -0,0 +1 @@ +1. En el lado derecho de la página, debajo de "Selecciona un nivel", revisa los niveles de patrocinio disponibles. Posteriormente, a la derecha del nivel que escojas, da clic en **Seleccionar**. ![Caja de selección de nivel](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/es-ES/data/reusables/sponsors/select-goal-type.md b/translations/es-ES/data/reusables/sponsors/select-goal-type.md new file mode 100644 index 0000000000000..748959ba2f104 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/select-goal-type.md @@ -0,0 +1,4 @@ +1. Debajo de "¿En qué se basa tu meta?", selecciona la **Cantidad de patrocinadores**" o **Patrocinios por mes**. ![Tipos de meta disponibles ](/assets/images/help/sponsors/select-goal-type.png) +2. Teclea la cantidad de patrocinadores que te gustaría tener, o la cantidad mensual a la que aspiras. +3. Debajo de "Describe tu meta", teclea una descripción de tu meta. ![Configuración de metas](/assets/images/help/sponsors/goal-settings.png) +5. Si eliges una meta basada en patrocinios por mes, selecciona "Entiendo que esto mostrará públicamente la cantidad de fondos de patrocinio que recibo mensualmente". ![Casilla en donde aceptas que entiendes que el fondo de tus patrocinios se publicará](/assets/images/help/sponsors/sponsorships-published-checkbox.png) diff --git a/translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md b/translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md new file mode 100644 index 0000000000000..65d1eb187e2b3 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md @@ -0,0 +1 @@ +4. Dentro de "Billing information" (Información de facturación), revisa tus detalles de pago. Como alternativa, para cambiar los detalles de pago para toda tu cuenta {% data variables.product.product_name %}, haz clic en **Edit (Editar)**. Después, sigue las instrucciones para completar el formulario de pago. diff --git a/translations/es-ES/data/reusables/sponsors/send-update-to-sponsors.md b/translations/es-ES/data/reusables/sponsors/send-update-to-sponsors.md new file mode 100644 index 0000000000000..bd5cd81ee4514 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/send-update-to-sponsors.md @@ -0,0 +1 @@ +5. Opcionalmente, para enviar un correo electrónico a los patrocinadores en niveles específicos, usa el menú desplegable **All sponsors** (Todos los patrocinadores) y selecciona uno o más niveles. ![Selecciona el menú desplegable de los niveles de patrocinio](/assets/images/help/sponsors/select-tiers-email.png) diff --git a/translations/es-ES/data/reusables/sponsors/set-a-goal.md b/translations/es-ES/data/reusables/sponsors/set-a-goal.md new file mode 100644 index 0000000000000..8effa275dc029 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/set-a-goal.md @@ -0,0 +1 @@ +1. Debajo de "Tus metas", da clic en **Configurar una meta**. ![Botón de configurar una meta ](/assets/images/help/sponsors/set-a-goal-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/settings-tab.md b/translations/es-ES/data/reusables/sponsors/settings-tab.md new file mode 100644 index 0000000000000..c2aff80f7399f --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/settings-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Configuración**. ![Pestaña Parámetros](/assets/images/help/sponsors/settings-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/short-bio.md b/translations/es-ES/data/reusables/sponsors/short-bio.md new file mode 100644 index 0000000000000..48c7bfd3f2acd --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/short-bio.md @@ -0,0 +1 @@ +1. Debajo de "Biografía corta", teclea una descripción breve de ti y de tu trabajo. ![Campo de biografía corta](/assets/images/help/sponsors/short-bio.png) diff --git a/translations/es-ES/data/reusables/sponsors/sponsor-account.md b/translations/es-ES/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000000..b25ce7fd983e6 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Da clic en **Patrocinar _CUENTA_**. ![Botón de Patrocinador](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/sponsors-updates-tab.md b/translations/es-ES/data/reusables/sponsors/sponsors-updates-tab.md new file mode 100644 index 0000000000000..36dce476e76b2 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/sponsors-updates-tab.md @@ -0,0 +1 @@ +3. En la barra lateral izquierda, haz clic en **Updates** (Actualizaciones). ![Pestaña Updates (Actualizaciones)](/assets/images/help/sponsors/updates-tab.png) diff --git a/translations/es-ES/data/reusables/sponsors/sponsorship-dashboard.md b/translations/es-ES/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000000..b69699d2c6b38 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navega a tu panel de patrocinios para la cuenta. + - Si estás patrocinando a una cuenta de usuario, bajo el nombre del usuario, da clic en **Patrocinio**. ![Botón de patrocinio](/assets/images/help/profile/sponsoring-button.png) + - Si estás patrocinando a una organización, a la derecha de su nombre, da clic en **Patrocinio**. ![Botón de patrocinio](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Opcionalmente, para administrar un patrocinio en nombre de una organización, a la derecha de la página, utiliza el menú desplegable **Patrocinando como**, y da clic en la organización. ![Menú desplegable para elegir la cuenta bajo la cual patrocinas](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/es-ES/data/reusables/sponsors/sponsorship-details.md b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md new file mode 100644 index 0000000000000..0549a3f417c4c --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md @@ -0,0 +1 @@ +Puedes patrocinar a cualquiera que tenga un perfil de desarrollador patrocinado o de organización patrocinada en nombre de tu cuenta de usuario o de una organización. Puedes elegir de entre varios niveles de patrocinio, con cantidades de pago mensuales y beneficios que configura la cuenta patrocinada. Tu patrocinio compartirá la fecha de facturación de tu cuenta, así como el método de pago y recibos. diff --git a/translations/es-ES/data/reusables/sponsors/sponsorships-not-tax-deductible.md b/translations/es-ES/data/reusables/sponsors/sponsorships-not-tax-deductible.md new file mode 100644 index 0000000000000..d1ce5fa2dec03 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/sponsorships-not-tax-deductible.md @@ -0,0 +1 @@ +Generalmente, los patrocionios no se deducen de impuestos, pero pueden hacerlo en ciertos casos. Es responsabilidad del colaborador de código abierto patrocinado—y no así de {% data variables.product.prodname_dotcom %}— informar a los patrocinadores si las contribuciones se están realizando a una entidad libre de impuestos como un 501(c)(3), y si los patrocinios pueden ser deducibles de impuestos. diff --git a/translations/es-ES/data/reusables/sponsors/stripe-supported-regions.md b/translations/es-ES/data/reusables/sponsors/stripe-supported-regions.md new file mode 100644 index 0000000000000..69d37bbf22669 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/stripe-supported-regions.md @@ -0,0 +1 @@ +Para encontrar una lista de regiones compatibles, consulta [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors#countries). diff --git a/translations/es-ES/data/reusables/sponsors/tax-form-information-dev.md b/translations/es-ES/data/reusables/sponsors/tax-form-information-dev.md new file mode 100644 index 0000000000000..77db328094747 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tax-form-information-dev.md @@ -0,0 +1,4 @@ +Para obtener más información acerca de los formatos de impuestos que necesitas llenar, consulta las siguientes instrucciones en el sitio web del Servicio de Impuestos Internos de los Estados Unidos. + +- [Instrucciones para el formulario W-9](https://www.irs.gov/pub/irs-pdf/iw9.pdf), para residentes de los EE.UU. +- [Instrucciones para el formulario W-8BEN](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf), para residentes no estadounidenses diff --git a/translations/es-ES/data/reusables/sponsors/tax-form-information-org.md b/translations/es-ES/data/reusables/sponsors/tax-form-information-org.md new file mode 100644 index 0000000000000..a867de87541cf --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tax-form-information-org.md @@ -0,0 +1 @@ +Para obtener más información acerca de los formatos de impuestos que deben completar las organizaciones, consulta la sección [Instrucciones para el Formato W-8BEN-E](https://www.irs.gov/pub/irs-pdf/iw8bene.pdf) en el sitio web del Servicio de Impuestos Internos de los Estados Unidos. diff --git a/translations/es-ES/data/reusables/sponsors/tax-form-link.md b/translations/es-ES/data/reusables/sponsors/tax-form-link.md new file mode 100644 index 0000000000000..a575b6cfed435 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tax-form-link.md @@ -0,0 +1,2 @@ +1. Da clic en **Formulario de impuestos**. ![Enlace para llenar el formato de impuestos](/assets/images/help/sponsors/tax-form-link.png) +2. Completa, firma y emite el formato de impuestos. diff --git a/translations/es-ES/data/reusables/sponsors/tier-details.md b/translations/es-ES/data/reusables/sponsors/tier-details.md new file mode 100644 index 0000000000000..e77cfda36f216 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tier-details.md @@ -0,0 +1,3 @@ +Puedes crear hasta diez niveles de patrocinio que podrán escoger los patrocinadores. Cada nivel tiene sus propias cantidades de pago mensual en dólares estadounidenses y sus beneficios, tal como recibir acceso anticipado a las nuevas versiones o recibir menciones en el archivo README del proyecto. + +Una vez que tengas a un patrocinador en un nivel, no podrás editar el precio de éste. En vez de eso, deberás retirar el nivel y crear uno nuevo. Los patrocinadores existentes permanecerán en el nivel retirado hasta que cambien su nivel de patrocinio o cancelen su patrocinio. diff --git a/translations/es-ES/data/reusables/sponsors/tier-price-description.md b/translations/es-ES/data/reusables/sponsors/tier-price-description.md new file mode 100644 index 0000000000000..d7dde173e5f80 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tier-price-description.md @@ -0,0 +1 @@ +1. Teclea un precio mensual y descripción del nivel. ![Campos de texto para precio y descripción del nivel](/assets/images/help/sponsors/tier-price-description.png) diff --git a/translations/es-ES/data/reusables/sponsors/tier-update.md b/translations/es-ES/data/reusables/sponsors/tier-update.md new file mode 100644 index 0000000000000..c2f4c896cc147 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/tier-update.md @@ -0,0 +1 @@ +6. Revisa tu nivel y luego haz clic en **Update** (Actualizar). ![Botón Update tier (Actualizar nivel)](/assets/images/help/sponsors/update-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/update-sponsorship.md b/translations/es-ES/data/reusables/sponsors/update-sponsorship.md new file mode 100644 index 0000000000000..15a7c1f53aa87 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/update-sponsorship.md @@ -0,0 +1 @@ +1. Da clic en **Actualizar patrocinio**. ![Botón de actualizar patrocinio](/assets/images/help/sponsors/update-sponsorship-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/view-eligible-accounts.md b/translations/es-ES/data/reusables/sponsors/view-eligible-accounts.md new file mode 100644 index 0000000000000..f2282c169cb5c --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/view-eligible-accounts.md @@ -0,0 +1 @@ +1. Da clic en **Ver tus cuentas elegibles**. ![Botón para ver tus cuentas elegibles](/assets/images/help/sponsors/view-eligible-accounts.png) diff --git a/translations/es-ES/data/reusables/sponsors/webhook-content-formatting.md b/translations/es-ES/data/reusables/sponsors/webhook-content-formatting.md new file mode 100644 index 0000000000000..d84dfcf656337 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/webhook-content-formatting.md @@ -0,0 +1 @@ +4. Debajo de "Tipo de contenido", selecciona qué formato de datos quisieras recibir. Para obtener más información, consulta la sección "[Crear webhooks](/webhooks/creating/#content-type)" ![Menú para dar formato a los webhooks](/assets/images/help/sponsors/webhook-content-menu.png) diff --git a/translations/es-ES/data/reusables/sponsors/webhook-secret-token.md b/translations/es-ES/data/reusables/sponsors/webhook-secret-token.md new file mode 100644 index 0000000000000..8a20b410978ce --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/webhook-secret-token.md @@ -0,0 +1 @@ +5. Teclea un token secreto. Para obtener más información, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/#securing-your-secret-token)". ![Campos para token secreto y otras opciones de personalización](/assets/images/help/sponsors/webhook-secret-token.png) diff --git a/translations/es-ES/data/reusables/sponsors/who-can-see-your-sponsorship.md b/translations/es-ES/data/reusables/sponsors/who-can-see-your-sponsorship.md new file mode 100644 index 0000000000000..e9df98186ed25 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/who-can-see-your-sponsorship.md @@ -0,0 +1 @@ +1. Elegir quién puede ver tu patrocinio. diff --git a/translations/es-ES/data/reusables/sponsors/write-sponsor-update.md b/translations/es-ES/data/reusables/sponsors/write-sponsor-update.md new file mode 100644 index 0000000000000..88e704ebd43ba --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/write-sponsor-update.md @@ -0,0 +1 @@ +6. Escribe un asunto y un mensaje para tu actualización.![Campos de asunto y cuerpo](/assets/images/help/sponsors/subject-body-update.png) diff --git a/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-developer.md b/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-developer.md new file mode 100644 index 0000000000000..94341edc2e463 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-developer.md @@ -0,0 +1 @@ +Cualquiera que colabore con un proyecto de código abierto y viva en una región compatible será elegible para convertirse en un desarrollador patrocinado. Las contribuciones incluyen, entre otras, informes de errores, evaluación de propuestas, código, documentación, liderazgo, desarrollo comercial, gestión de proyectos, mentoría y diseño. Si vives en una región que aún no es compatible con {% data variables.product.prodname_sponsors %}, puedes inscribirte a la llista de espera para participar en el beta de {% data variables.product.prodname_sponsors %}. diff --git a/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-organization.md b/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-organization.md new file mode 100644 index 0000000000000..267bfb794b2ed --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/you-can-be-a-sponsored-organization.md @@ -0,0 +1 @@ +Cualquier organización que colabore con un proyecto de código abierto y que opere legalmente en una región compatible será elegible para convertirse en una organización patrocinada. Si tu organización opera en una región que no sea compatible con {% data variables.product.prodname_sponsors %} actualmente, únete a la lista de espera en [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md new file mode 100644 index 0000000000000..415f86736de32 --- /dev/null +++ b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -0,0 +1,3 @@ +```shell +$ ssh-add ~/.ssh/id_ed25519 +``` diff --git a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md new file mode 100644 index 0000000000000..c07831e466ff1 --- /dev/null +++ b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -0,0 +1 @@ +Si creaste tu llave con un nombre diferente, o si estás agregando una llave existente que tiene un nombre diferente, reemplaza *id_ed25519* en el comando con el nombre de tu archivo de llave privada. diff --git a/translations/es-ES/data/reusables/ssh/dsa-support.md b/translations/es-ES/data/reusables/ssh/dsa-support.md new file mode 100644 index 0000000000000..c4035d4bd3eaf --- /dev/null +++ b/translations/es-ES/data/reusables/ssh/dsa-support.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** Las llaves de DSA (SSH-DSS) ya no son compatibles. Las llaves existentes seguirán funcionando, pero no puedes agregar una llave DSA nueva a tu cuenta de {% data variables.product.product_name %}. + +{% endnote %} diff --git a/translations/es-ES/data/reusables/support/about-premium-plans.md b/translations/es-ES/data/reusables/support/about-premium-plans.md new file mode 100644 index 0000000000000..4355fa6714e26 --- /dev/null +++ b/translations/es-ES/data/reusables/support/about-premium-plans.md @@ -0,0 +1,23 @@ + +### Planes {% data variables.contact.premium_support %} + +Existen dos planes de {% data variables.contact.premium_support %}: Premium y Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. + +| | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} +| --------------------------- | ---------------------------------------------------- | -------------------------------------------------------- | +| Horas de operación | 24 x 7 | 24 x 7 | +| Tiempo de respuesta inicial |
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 horas para {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 horas para {% data variables.product.support_ticket_priority_high %}
| +| Canales de soporte técnico |
  • Emisión de ticket en línea
  • Soporte vía telefónica
|
  • Emisión de ticket en línea
  • Soporte vía telefónica
  • Compartir pantalla en problemas críticos
| +| Capacitación | Acceso a contenido prémium. |
  • Acceso a contenido prémium.
  • 1 clase de capacitación virtual por año
| +| Contactos autorizados | 10 | 25 | +| Recursos | Procesamiento de ticket con prioridad |
  • Procesamiento de ticket con prioridad
  • Gerente de Cuenta de Soporte Técnico Nombrado
| +| Revisiones programadas | Revisión de estado y elaboración de informes bianual |
  • Reporte y verificación de salud trimestral
  • Revisiones de cuenta trimestrales
| +| Administración | | 4 horas de Servicios administrados por mes | + + {% note %} + + **Notas:** + - Las revisiones programadas se limitan a una organización por trimestre. En cualquier momento puedes agregar revisiones programadas para más organizaciones por una tarifa adicional [contactándote con nuestro equipo de gestión de cuentas](https://enterprise.github.com/contact) o llamando al [+1 (877) 448-4820](tel:+1-877-448-4820). + - Para el {% data variables.product.premium_plus_support_plan %}, el 50 % de las horas de Servicios administrados no utilizadas se transfieren al siguiente mes y vencen al final del trimestre. + + {% endnote %} diff --git a/translations/es-ES/data/reusables/support/accessing-premium-content.md b/translations/es-ES/data/reusables/support/accessing-premium-content.md new file mode 100644 index 0000000000000..dfb86f10603be --- /dev/null +++ b/translations/es-ES/data/reusables/support/accessing-premium-content.md @@ -0,0 +1,4 @@ + +### Acceder a contenido prémium + +Puedes acceder al contenido premium iniciando sesión en el {% data variables.contact.contact_enterprise_portal %}. diff --git a/translations/es-ES/data/reusables/support/ask-and-answer-forum.md b/translations/es-ES/data/reusables/support/ask-and-answer-forum.md new file mode 100644 index 0000000000000..052dbc2d8407a --- /dev/null +++ b/translations/es-ES/data/reusables/support/ask-and-answer-forum.md @@ -0,0 +1 @@ +Puedes conectarte con desarrolladores de todo el mundo en el [{% data variables.product.prodname_gcf %}](https://github.community) para preguntar y responder preguntas, aprender e interactuar directamente con el personal de {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/support/connect-in-the-forum-bootcamp.md b/translations/es-ES/data/reusables/support/connect-in-the-forum-bootcamp.md new file mode 100644 index 0000000000000..e10ff24e88f84 --- /dev/null +++ b/translations/es-ES/data/reusables/support/connect-in-the-forum-bootcamp.md @@ -0,0 +1 @@ +Conéctate con personas de todo el mundo en el [{% data variables.product.prodname_gcf %}](https://github.community) diff --git a/translations/es-ES/data/reusables/support/contacting-premium-support.md b/translations/es-ES/data/reusables/support/contacting-premium-support.md new file mode 100644 index 0000000000000..df17b4d8deaa5 --- /dev/null +++ b/translations/es-ES/data/reusables/support/contacting-premium-support.md @@ -0,0 +1,4 @@ + +### Comunicarse con {% data variables.contact.premium_support %} + +Los clientes de {% data variables.contact.premium_support %} pueden utilizar el {% data variables.contact.contact_enterprise_portal %} para reportar problemas por escrito, en inglés. También puedes recibir soporte técnico en inglés por teléfono. Para obtener el número de teléfono de la {% data variables.contact.premium_support %}, consulta "[24x7 Phone Support](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)" (Soporte técnico telefónico 24x7) en el {% data variables.contact.enterprise_portal %}. diff --git a/translations/es-ES/data/reusables/support/data-protection-and-privacy.md b/translations/es-ES/data/reusables/support/data-protection-and-privacy.md new file mode 100644 index 0000000000000..94fe6f433a9ee --- /dev/null +++ b/translations/es-ES/data/reusables/support/data-protection-and-privacy.md @@ -0,0 +1 @@ +Cuando utilizas las ofertas de soporte de {% data variables.product.prodname_dotcom %}, se aplicará tanto la Declaración de Privacidad de {% data variables.product.prodname_dotcom %} como la Adenda de Protección de Datos de {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md new file mode 100644 index 0000000000000..9261e567c4132 --- /dev/null +++ b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md @@ -0,0 +1,5 @@ +{% data variables.contact.enterprise_support %} podría considerar a un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, {% if currentVersion == "github-ae@latest" %}o {% endif %} instrucciones de solución alternativa{% if enterpriseServerVersions contains currentVersion %}, o recomendándote un lanzamiento disponible que trate el problema{% endif %}. + +Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.enterprise_support %} puede pedirte que elimines complementos, módulos o códigos no compatibles al intentar resolver el problema. Si el problema se arregla cuando el plug-in, módulo, o código personalizado no compatibles se eliminan, {% data variables.contact.enterprise_support %} podría considerar el ticket como resuelto. + +{% data variables.contact.enterprise_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.enterprise_support %} cierra un ticket por falta de respuesta, puedes solicitar que lo vuelva a abrir. diff --git a/translations/es-ES/data/reusables/support/ghae-priorities.md b/translations/es-ES/data/reusables/support/ghae-priorities.md new file mode 100644 index 0000000000000..5bdbffd39eb0d --- /dev/null +++ b/translations/es-ES/data/reusables/support/ghae-priorities.md @@ -0,0 +1,6 @@ +| Prioridad | Descripción | Ejemplos | +|:---------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} - Sev A | No se puede acceder a {% data variables.product.product_name %} o hay un fallo total, y dicho fallo impacta directamente en la operación de tu negocio.

_Después de que emitas un ticket de soporte, llama a {% data variables.contact.github_support %} por teléfono_ |
  • Errores o suspensiones que afectan la funcionalidad central de Git o de la aplicación web para todos los usuarios
  • Degradación severa del rendmimiento o de la red para la mayoría de los usuarios
  • Almacenamiento agotado, o que se llena muy rápidamente
  • Incidentes de seguridad conocidos o una violación de acceso
| +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falla en un ambiente productivo, con un impacto limitado a tus procesos de negocio, o afectando únicamente a ciertos clientes. |
  • Degradación del rendimiento que reduce la productividad para muchos usuarios
  • Preocupaciones de redundancia reducida ocasionada por los fallos o la degradación del servicio
  • Errores o fallos que impactan a los ambientes productivos
  • {% data variables.product.product_name %} configuration security concerns
| +| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} está presentando problemas moderados o limitados y errores con {% data variables.product.product_name %}, o tienes problemas o preguntas en general sobre la operación de {% data variables.product.product_name %}. |
  • Consejos sobre como utilizar las API y las características de {% data variables.product.prodname_dotcom %}, o preguntas sobre cómo integrar los flujos de trabajo de negocios
  • Problemas con las herramientas de usuario y los métodos de recolección de datos
  • Actualizaciones
  • Reportes de errores, preguntas generales sobre la seguridad, u otras preguntas relacionadas con las características
    • | +| {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} funciona de acuerdo a lo esperado, sin embargo, tienes una pregunta o sugerencia sobre {% data variables.product.product_name %} que no es urgente o que no bloquea de otra forma la productividad de tu equipo. |
    • Solicitudes de características y retroalimentación sobre el producto
    • Las preguntas generales sobre la configuración o el uso general de {% data variables.product.product_name %}
    • Notificar a {% data variables.contact.github_support %} de cualquier cambio planeado
    | diff --git a/translations/es-ES/data/reusables/support/ghec-premium-priorities.md b/translations/es-ES/data/reusables/support/ghec-premium-priorities.md new file mode 100644 index 0000000000000..4404a61414a25 --- /dev/null +++ b/translations/es-ES/data/reusables/support/ghec-premium-priorities.md @@ -0,0 +1,6 @@ +| Prioridad | Descripción | Ejemplos | +|:-------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} | Los flujos de trabajo de producción para tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} fallan debido a los errores o suspensiones de servicios críticos, y las fallas impactan directamente a la operación de tu negocio. |
    • Los errores o suspenciones en {% data variables.product.prodname_dotcom_the_website %} afectan la funcionalidad principal de Git o de las aplicaciones web para todos los miembros de tu organización o empresa
    | +| {% data variables.product.support_ticket_priority_high %} | Los problemas de cuenta o de seguridad con tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} están causando un impacto limitado en tu negocio. |
    • Un propietario de organización o empresa borró una organización sin querer
    • Un miembro de una organización o empresa subió datos sensibles en una confirmación, informe de problemas, solicitud de extracción o adjunto en el informe de problemas
    | +| {% data variables.product.support_ticket_priority_normal %} | Los miembros de tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} están experimentando problemas moderados o limitados con {% data variables.product.prodname_dotcom_the_website %}, o tienes preocupaciones o dudas generales sobre tu organización o empresa. |
    • Preguntas sobre el uso de las API o de las características para tu organización o empresa
    • Problemas con herramientas para migración de datos de una organización que proporciona {% data variables.product.company_short %}
    • Características relacionadas con que tu organización o empresa no funcione como se espera
    • Preguntas generales de seguridad de tu organización o empresa
    | +| {% data variables.product.support_ticket_priority_low %} | Tienes una pregunta o sugerencia sobre tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} que no es urgente, o no bloquea la productividad de tu equipo en alguna otra forma. |
    • Uso excesivo de recursos para tu organización o empresa
    • Solicitudes de verificaciones de estado
    • Ayuda con el uso de Gists, notificaciones, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, Atom, u otros servicios periféricos o características en tu organización o empresa
    • Solicitudes de características
    • Retroalimentación de producto
    | diff --git a/translations/es-ES/data/reusables/support/ghes-priorities.md b/translations/es-ES/data/reusables/support/ghes-priorities.md new file mode 100644 index 0000000000000..5beba0d12364e --- /dev/null +++ b/translations/es-ES/data/reusables/support/ghes-priorities.md @@ -0,0 +1,6 @@ +| Prioridad | Descripción | Ejemplos | +|:-------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} | {% data variables.product.prodname_ghe_server %} está fallando en un ambiente productivo, y dicha falla impacta en la operación de tu negocio.

    _{% data reusables.support.priority-urgent-english-only %}_ |
    • Errores o suspensiones que afectan la funcionalidad central de Git o de la aplicación web para todos los usuarios
    • Degradación grave de rendimiento para la mayoría de los usuarios
    • Almacenamiento agotado, o que se llena muy rápidamente
    • Incapacidad para instalar un archivo de licencia renovado
    • Incidente de seguridad
    • Pérdida de acceso administrativo para la instancia sin solución alternativa conocida
    • Falla para restaurar un respaldo en un ambiente productivo
    | +| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_ghe_server %} está fallando en un ambiente productivo, pero el impacto a tu negocio es limitado. |
    • Degradación del rendimiento que reduce la productividad para muchos usuarios
    • Redundancia reducida por fallo en la Alta Disponibilidad (HA) o nodos de agrupación
    • Fallo en respaldar la instancia
    • Fallo para restaurar un respaldo en un ambiente de prueba o de montaje que podría poner en riesgo la restauración exitosa a un ambiente productivo
    | +| {% data variables.product.support_ticket_priority_normal %} | Estás experimentando problemas limitados o moderados con {% data variables.product.prodname_ghe_server %}, o tienes preocupaciones o dudas generales sobre la operación de tu instancia. |
    • Problemas en un ambiente de pruebas o de montaje
    • Consejo sobre utilizar las características y APIS de {% data variables.product.prodname_dotcom %}, o dudas sobre configurar las integraciones de terceros desde tu instancia
    • Problemas con las herramientas para la migración de datos de usuario que proporciona {% data variables.product.company_short %}
    • Actualizaciones
    • Reporte de errores
    • Características que no funcionan como se espera
    • Preguntas generales sobre seguridad
    | +| {% data variables.product.support_ticket_priority_low %} | Tienes una pregunta o sugerencia acerca de {% data variables.product.prodname_ghe_server %} que no es urgente o que no bloquea la productividad de tu equipo de otra forma. |
    • Solicitudes de características
    • Retroalimentación de producto
    • Solicitudes de verificación de estado (por el momento, únicamente disponible para clientes con un {% data variables.product.premium_support_plan %})
    • Notificar a {% data variables.product.company_short %} sobre mantenimiento planeado para tu instancia
    | diff --git a/translations/es-ES/data/reusables/support/github-can-modify-ticket-priority.md b/translations/es-ES/data/reusables/support/github-can-modify-ticket-priority.md new file mode 100644 index 0000000000000..68f0f1cd65557 --- /dev/null +++ b/translations/es-ES/data/reusables/support/github-can-modify-ticket-priority.md @@ -0,0 +1 @@ +{% data variables.product.company_short %} tiene la absoluta discreción para modificar la prioridad de un ticket en cualquier momento, y puede bajar la prioridad de un ticket después de determinar y mitigar la causa principal de un problema. diff --git a/translations/es-ES/data/reusables/support/government-response-times-may-vary.md b/translations/es-ES/data/reusables/support/government-response-times-may-vary.md new file mode 100644 index 0000000000000..9cc3e8706a4df --- /dev/null +++ b/translations/es-ES/data/reusables/support/government-response-times-may-vary.md @@ -0,0 +1,7 @@ +{% if currentVersion == "github-ae@latest" %} +{% note %} + +**Nota:** Los tiempos de respuesta y las horas operativas podrían diferir para {% data variables.product.prodname_ghe_managed %} en el caso de las entidades gubernamentales. El Administrador de Soporte Técnico para tu Cuenta (TSAM) lo confirmará durante tu incorporación. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/support/help_resources.md b/translations/es-ES/data/reusables/support/help_resources.md new file mode 100644 index 0000000000000..cdbc31c89dbfb --- /dev/null +++ b/translations/es-ES/data/reusables/support/help_resources.md @@ -0,0 +1,7 @@ +Para preguntas, reportes de errores y debates sobre las {% data variables.product.prodname_github_app %}, {% data variables.product.prodname_oauth_app %}, y el desarrollo de API, explora el {% data variables.product.prodname_support_forum_with_url %}. El foro se modera y mantiene con el personal de {% data variables.product.company_short %}, pero no se garantiza que el personal de {% data variables.product.company_short %} responda las preguntas que se publiquen en el mismo. + +Considera contactar al [Soporte de GitHub](https://github.com/contact) directamente utilizando el formato de contacto para: + - respuestas garantizadas del personal de {% data variables.product.product_name %} + - solicitudes de soporte que involucren preocupaciones sobre datos sensibles o privados + - solicitudes de características + - retroalimentación sobre los productos de {% data variables.product.product_name %} diff --git a/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md new file mode 100644 index 0000000000000..bda2be6cf1464 --- /dev/null +++ b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md @@ -0,0 +1,5 @@ +{% data variables.contact.premium_support %} podría considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, instrucciones de solución alternativa, o recomendándote un lanzamiento disponible que trata el problema. + +Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible. + +{% data variables.contact.premium_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra. diff --git a/translations/es-ES/data/reusables/support/priority-urgent-english-only.md b/translations/es-ES/data/reusables/support/priority-urgent-english-only.md new file mode 100644 index 0000000000000..ddd1bd88148ec --- /dev/null +++ b/translations/es-ES/data/reusables/support/priority-urgent-english-only.md @@ -0,0 +1 @@ +El soporte para tickets con prioridad {% data variables.product.support_ticket_priority_urgent %} se encuentra disponible únicamente en inglés. diff --git a/translations/es-ES/data/reusables/support/receiving-credits.md b/translations/es-ES/data/reusables/support/receiving-credits.md new file mode 100644 index 0000000000000..c5951cb8a4880 --- /dev/null +++ b/translations/es-ES/data/reusables/support/receiving-credits.md @@ -0,0 +1,19 @@ + +### Recibir créditos por falta de respuesta a los tickets de soporte + +Si no recibes una respuesta inicial dentro del tiempo de respuesta garantizado en más de cuatro tickets en un trimestre basándote en el año fiscal de {% data variables.product.company_short %}, serás elegible para que se te dé crédito. En cumplimiento del Acuerdo de nivel de servicio, {% data variables.product.company_short %} te reembolsará el 20 % de la tarifa {% data variables.contact.premium_support %} trimestral en efectivo. Para recibir el reembolso, debes enviar una solicitud de crédito. + +La solicitud de crédito se debe hacer dentro de los 30 días del final del trimestre durante el cual {% data variables.contact.premium_support %} no respondió a tus tickets dentro del tiempo designado de respuesta. Las solicitudes de crédito no serán reconocidas luego del plazo establecido para su presentación. Una vez que este plazo se haya cumplido, habrás renunciado a la posibilidad de reclamar un reembolso por el crédito que te hubiera correspondido. + +Para recibir un reembolso, debes enviar una solicitud de crédito completa a . Para ser aceptada, la solicitud de crédito debe cumplir con las siguientes condiciones: +- Enviarse desde una dirección de correo electrónico que esté asociada a tu cuenta {% data variables.product.product_name %} +- Ser recibida por {% data variables.product.company_short %} en el plazo de 30 días a partir del cierre del trimestre en el que se produjeron los cuatro créditos calificados +- Pon "Credit Request" en la línea de asunto + +La siguiente información **se debe incluir** en tu solicitud de crédito: +- **Fecha** (la fecha debe estar comprendida en un plazo de 30 días a partir del cierre del trimestre de acuerdo con el cierre del año fiscal de {% data variables.product.company_short %} durante el que cual se produjeron los créditos que se reclaman [31 de enero, 30 de abril, 31 de julio o 31 de octubre]) +- **Contacto del cliente** (Debes especificar tanto el nombre como la dirección de correo electrónico) +- **Domicilio del cliente** +- **Créditos de calificación** (Debes proporcionar la fecha de cada crédito de calificación y el número de ticket asociado.){% if currentVersion == "free-pro-team@latest" %} +- **Nombre de la organización {% data variables.product.prodname_ghe_cloud %}**{% endif %} +- **Número de ticket** diff --git a/translations/es-ES/data/reusables/support/scope-of-support.md b/translations/es-ES/data/reusables/support/scope-of-support.md new file mode 100644 index 0000000000000..c4c583d6885cd --- /dev/null +++ b/translations/es-ES/data/reusables/support/scope-of-support.md @@ -0,0 +1,12 @@ + +### Alcance del soporte técnico + +Si tu solicitud de soporte técnico está fuera del alcance de lo que puede hacer nuestro equipo para ayudarte, podemos recomendarte los siguientes pasos para resolver el problema por fuera del {% data variables.contact.github_support %}. Es probable que tu solicitud de soporte técnico esté fuera del alcance de {% data variables.contact.github_support %} si se trata principalmente de lo siguiente: +- Integraciones de terceros +- Configuración del hardware +- CI/CD, como Jenkins +- Escribir scripts +- Configuración de sistemas de autenticación externos, como proveedores de identidad SAML +- Proyectos de código abierto + +Si no estás seguro de si el problema está fuera de nuestro alcance, abre un ticket y nos complacerá ayudarte a determinar la mejor manera de continuar. diff --git a/translations/es-ES/data/reusables/support/service-level-agreement-response-times.md b/translations/es-ES/data/reusables/support/service-level-agreement-response-times.md new file mode 100644 index 0000000000000..4109437378f09 --- /dev/null +++ b/translations/es-ES/data/reusables/support/service-level-agreement-response-times.md @@ -0,0 +1,8 @@ +### Tiempos de respuesta del Acuerdo de nivel de servicio + +Para los tickets que envías, el soporte técnico está disponible las 24 horas del día, los 7 días de la semana. El tiempo de respuesta inicial que garantiza el SLA depende del nivel de prioridad del ticket. El tiempo de respuesta comienza cuando {% data variables.contact.premium_support %} elige el nivel de prioridad del ticket. Una respuesta no implica que el problema se haya resuelto. + +| Nivel de prioridad del ticket | Tiempo de respuesta inicial | +| ------------------------------------------------------------- | --------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} | 30 minutos | +| {% data variables.product.support_ticket_priority_high %} | 4 horas | diff --git a/translations/es-ES/data/reusables/support/signing-up-for-premium-support.md b/translations/es-ES/data/reusables/support/signing-up-for-premium-support.md new file mode 100644 index 0000000000000..b3334655c2fc9 --- /dev/null +++ b/translations/es-ES/data/reusables/support/signing-up-for-premium-support.md @@ -0,0 +1,4 @@ + +### Registrarse en {% data variables.contact.premium_support %} + +Para registrarte en {% data variables.contact.premium_support %} o actualizar tu plan, puedes [ponerte en contacto con nuestro equipo de administración de cuentas](https://enterprise.github.com/contact) o llamar a [+1 (877) 448-4820](tel:+1-877-448-4820). diff --git a/translations/es-ES/data/reusables/time_date/date_format.md b/translations/es-ES/data/reusables/time_date/date_format.md new file mode 100644 index 0000000000000..9644f0e2f9df4 --- /dev/null +++ b/translations/es-ES/data/reusables/time_date/date_format.md @@ -0,0 +1 @@ +El formato de fecha debe seguir el estándar [ISO8601](http://en.wikipedia.org/wiki/ISO_8601), el cual es `YYYY-MM-DD` (año-mes-día). diff --git a/translations/es-ES/data/reusables/time_date/time_format.md b/translations/es-ES/data/reusables/time_date/time_format.md new file mode 100644 index 0000000000000..10c6a4fc54420 --- /dev/null +++ b/translations/es-ES/data/reusables/time_date/time_format.md @@ -0,0 +1 @@ +También puedes agregar información de tiempo ocpional `THH:MM:SS+00:00` después de la fecha, para buscar por hora, minuto y segundo. Se hace agregando `T`, seguido de `HH:MM:SS` (hora-minutos-segundos), y un intervalo de UTC (`+00:00`). diff --git a/translations/es-ES/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md b/translations/es-ES/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md new file mode 100644 index 0000000000000..5ee02e8903f80 --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md @@ -0,0 +1 @@ +No se soporta o administra en el aplicativo de {% data variables.product.prodname_ghe_server %}, pero puede que sí lo haga el proveedor de autenticación externo. No está disponible la implementación de la autenticación de dos factores en organizaciones. diff --git a/translations/es-ES/data/reusables/two_fa/about-2fa.md b/translations/es-ES/data/reusables/two_fa/about-2fa.md new file mode 100644 index 0000000000000..931ce4098d33f --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/about-2fa.md @@ -0,0 +1 @@ +La autenticación bifactorial (2FA) es una capa de seguridad adicional que seutiliza cuando ingresas en sitios web o en apps. diff --git a/translations/es-ES/data/reusables/two_fa/about-recovery-codes.md b/translations/es-ES/data/reusables/two_fa/about-recovery-codes.md new file mode 100644 index 0000000000000..2022d3b1287ea --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/about-recovery-codes.md @@ -0,0 +1 @@ +Cuando configuras la autenticación bifactorial, descargarás y guardarás los códigos de recuperación de dos factores. Si pierdes acceso a tu teléfono, puedes autenticarte en {% data variables.product.product_name %} utilizando tus códigos de recuperación. diff --git a/translations/es-ES/data/reusables/two_fa/after-2fa-add-security-key.md b/translations/es-ES/data/reusables/two_fa/after-2fa-add-security-key.md new file mode 100644 index 0000000000000..6a78293fe6a94 --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/after-2fa-add-security-key.md @@ -0,0 +1 @@ +Después de que configuras la 2FA utilizando una app móvil{% if currentVersion == "free-pro-team@latest" %} o a través de un mensaje de texto{% endif %}, puedes agregar una llave de seguridad, como una lector de huella digital o Windows Hello. La tecnología que habilita la autenticación con una llave de seguridad se llama WebAuthn. WebAuthn es el sucesor de la autenticación bifactorial y funciona en todos los buscadores modernos. Para obtener más información, consulta la sección "[WebAuthn](https://webauthn.guide/)" y "[Puedo utilizar](https://caniuse.com/#search=webauthn)". diff --git a/translations/es-ES/data/reusables/two_fa/auth_methods_2fa.md b/translations/es-ES/data/reusables/two_fa/auth_methods_2fa.md new file mode 100644 index 0000000000000..ae4291b31a1ab --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/auth_methods_2fa.md @@ -0,0 +1,10 @@ +{% if enterpriseServerVersions contains currentVersion %} +### Métodos de autenticación que admiten la 2FA + +| Método de autenticación | Descripción | Soporte técnico de la autenticación de dos factores | +| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Incorporada | La autenticación se realiza para las cuentas de usuario que están almacenadas en el aparato del {% data variables.product.prodname_ghe_server %}. | Recibe soporte técnico y se administra en el aparato del {% data variables.product.prodname_ghe_server %}. Los administradores de la organización pueden solicitar que se habilite la 2FA para los miembros de la organización. |{% if enterpriseServerVersions contains currentVersion %} +| Autenticación incorporada con un proveedor de identidad | La autenticación se realiza para las cuentas de usuario que están almacenadas en el proveedor de identidad. | Depende del proveedor de identidad.{% endif %} +| LDAP | Permite la integración con el servicio de directorio de tu empresa para la autenticación. | Recibe soporte técnico y se administra en el aparato del {% data variables.product.prodname_ghe_server %}. Los administradores de la organización pueden solicitar que se habilite la 2FA para los miembros de la organización. | +| SAML | La autenticación se realiza en un proveedor de identidad externo. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %} +| CAS | El servicio de inicio de sesión único lo proporciona un servidor externo. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %}{% endif %} diff --git a/translations/es-ES/data/reusables/two_fa/enable-two-factor-authentication.md b/translations/es-ES/data/reusables/two_fa/enable-two-factor-authentication.md new file mode 100644 index 0000000000000..b2a1c4d7e342f --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/enable-two-factor-authentication.md @@ -0,0 +1 @@ +1. Debajo de "Autenticación bifactorial", da clic en **Habilitar la autenticación bifactorial**. ![Habilitar la opción de autenticación bifactorial](/assets/images/help/2fa/enable-two-factor-authentication-dialoge.png) diff --git a/translations/es-ES/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md b/translations/es-ES/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md new file mode 100644 index 0000000000000..7f1044ef0381d --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md @@ -0,0 +1,5 @@ +6. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso. + - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar). + - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir). + - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) +7. Después de guardar tu código de recuperación de dos factores, haz clic en **Next** (Siguiente). diff --git a/translations/es-ES/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md b/translations/es-ES/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md new file mode 100644 index 0000000000000..64e9b815c0153 --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" %} +Puedes enviar una invitación para reinstalar los privilegios del usuario y el acceso a la organización antes de que hayan habilitado la autenticación bifactorial. Los usuarios deben habilitar dicha autenticación antes de aceptar tu invitación de unirse nuevamente a la organización. +{% endif %} diff --git a/translations/es-ES/data/reusables/two_fa/show-recovery-codes.md b/translations/es-ES/data/reusables/two_fa/show-recovery-codes.md new file mode 100644 index 0000000000000..04e5957a8938f --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/show-recovery-codes.md @@ -0,0 +1 @@ +1. A un costado de "Códigos de recuperación", da clic en **Mostrar**. ![Botón para mostrar los códigos de recuperación](/assets/images/help/2fa/show-recovery-codes-button.png) diff --git a/translations/es-ES/data/reusables/two_fa/support-may-not-help.md b/translations/es-ES/data/reusables/two_fa/support-may-not-help.md new file mode 100644 index 0000000000000..122f6807aa281 --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/support-may-not-help.md @@ -0,0 +1 @@ +Por razones de seguridad, la Asistencia de {% data variables.product.product_name %} no puede restaurar el acceso a las cuentas con autenticación de dos factores habilitada si pierdes tus credenciales de autenticación de dos factores o si pierdes acceso a los métodos de recuperación de tu cuenta. diff --git a/translations/es-ES/data/reusables/two_fa/test_2fa_immediately.md b/translations/es-ES/data/reusables/two_fa/test_2fa_immediately.md new file mode 100644 index 0000000000000..60792f0f6189a --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/test_2fa_immediately.md @@ -0,0 +1 @@ +1. Después de que hayas guardado tus códigos de recuperación y hayas habilitado la autenticación bifactorial, te recomendamos salir y volver a entrar en tu cuenta. En caso de encontrar problemas tales como olvidar tu contraseña o un error de escritura en tu dirección de correo electrónico, puedes utilizar los códigos de recuperación para acceder a tu cuenta y corregir el problema. diff --git a/translations/es-ES/data/reusables/two_fa/username-password.md b/translations/es-ES/data/reusables/two_fa/username-password.md new file mode 100644 index 0000000000000..b188dd4c973ba --- /dev/null +++ b/translations/es-ES/data/reusables/two_fa/username-password.md @@ -0,0 +1 @@ +1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. diff --git a/translations/es-ES/data/reusables/user-settings/access_settings.md b/translations/es-ES/data/reusables/user-settings/access_settings.md new file mode 100644 index 0000000000000..f38634500bae9 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/access_settings.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en **Configuración**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/settings/userbar-account-settings_post2dot12.png) diff --git a/translations/es-ES/data/reusables/user-settings/developer_settings.md b/translations/es-ES/data/reusables/user-settings/developer_settings.md new file mode 100644 index 0000000000000..d2c0a1b661403 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/developer_settings.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Sección Developer settings (Parámetros del programador)](/assets/images/settings/developer_settings.png) diff --git a/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md b/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md new file mode 100644 index 0000000000000..8fbdcdb4c6fdb --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md @@ -0,0 +1 @@ +5. Desplázate hacia abajo a la sección de Marketplace y da clic en **Editar listado de Marketplace**. La sección de Marketplace solo se encuentra visible si permites que cualquier usuario u organización instale tu app cuando la registras. Para obtener más información, consulta la lista de [Requisitos de Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![enlace para editar tu listado de GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/es-ES/data/reusables/user-settings/github_apps.md b/translations/es-ES/data/reusables/user-settings/github_apps.md new file mode 100644 index 0000000000000..bab37320634f6 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/github_apps.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **GitHub Apps**. ![Sección GitHub Apps](/assets/images/settings/github_apps.png) diff --git a/translations/es-ES/data/reusables/user-settings/github_apps_advanced.md b/translations/es-ES/data/reusables/user-settings/github_apps_advanced.md new file mode 100644 index 0000000000000..c7362fc03a1c4 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/github_apps_advanced.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Avanzado**. ![pestaña de avanzado](/assets/images/github-apps/github_apps_advanced.png) diff --git a/translations/es-ES/data/reusables/user-settings/marketplace_apps.md b/translations/es-ES/data/reusables/user-settings/marketplace_apps.md new file mode 100644 index 0000000000000..a8d57ea8506a5 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/marketplace_apps.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +1. En la barra lateral izquierda, da clic ya sea en **Apps de OAuth** o en **GitHub Apps** dependiendo del listado de {% data variables.product.prodname_marketplace %} que quieras administrar. **Nota:** También puedes administrar tu listado si navegas a https://github.com/marketplace/manage. ![Selección del tipo de app](/assets/images/settings/apps_choose_app.png) + +{% endif %} diff --git a/translations/es-ES/data/reusables/user-settings/modify_github_app.md b/translations/es-ES/data/reusables/user-settings/modify_github_app.md new file mode 100644 index 0000000000000..a7a099365f8b8 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/modify_github_app.md @@ -0,0 +1 @@ +1. Selecciona la GitHub App que quieres modificar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) diff --git a/translations/es-ES/data/reusables/user-settings/modify_oauth_app.md b/translations/es-ES/data/reusables/user-settings/modify_oauth_app.md new file mode 100644 index 0000000000000..53ce1f3abffeb --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/modify_oauth_app.md @@ -0,0 +1 @@ +1. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) diff --git a/translations/es-ES/data/reusables/user-settings/oauth_apps.md b/translations/es-ES/data/reusables/user-settings/oauth_apps.md new file mode 100644 index 0000000000000..e902161c02373 --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/oauth_apps.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Apps de OAuth**. ![Sección de la App de OAuth](/assets/images/settings/oauth_apps_post2dot12.png) diff --git a/translations/es-ES/data/reusables/user-settings/update_oauth_app.md b/translations/es-ES/data/reusables/user-settings/update_oauth_app.md new file mode 100644 index 0000000000000..56d16c6109f4e --- /dev/null +++ b/translations/es-ES/data/reusables/user-settings/update_oauth_app.md @@ -0,0 +1 @@ +1. Da clic en **Actualizar aplicación**. ![Botón para actualizar la aplicación](/assets/images/oauth-apps/oauth_apps_update_application.png) diff --git a/translations/es-ES/data/reusables/user_settings/about-commit-email-addresses.md b/translations/es-ES/data/reusables/user_settings/about-commit-email-addresses.md new file mode 100644 index 0000000000000..b228f2d2bf7df --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/about-commit-email-addresses.md @@ -0,0 +1 @@ +Para obtener más información sobre las direcciones de correo electrónico para las confirmaciones,{% if currentVersion == "free-pro-team@latest" %} incluyendo tu dirección de correo electrónico de tipo `noreply` que proporcionó {% data variables.product.product_name %},{% endif %} consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/articles/setting-your-commit-email-address)". diff --git a/translations/es-ES/data/reusables/user_settings/access_applications.md b/translations/es-ES/data/reusables/user_settings/access_applications.md new file mode 100644 index 0000000000000..090911a90e526 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/access_applications.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de aplicaciones](/assets/images/help/settings/settings-applications.png) diff --git a/translations/es-ES/data/reusables/user_settings/access_authorized_oauth_apps.md b/translations/es-ES/data/reusables/user_settings/access_authorized_oauth_apps.md new file mode 100644 index 0000000000000..dc25de86aa356 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/access_authorized_oauth_apps.md @@ -0,0 +1 @@ +1. Da clic en la pestaña **Aplicaciones OAuth Autorizadas**. ![Pestaña de Aplicaciones OAuth autorizadas](/assets/images/help/settings/settings-authorized-oauth-apps-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/access_settings.md b/translations/es-ES/data/reusables/user_settings/access_settings.md new file mode 100644 index 0000000000000..d39891130f238 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/access_settings.md @@ -0,0 +1 @@ +1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en **Configuración**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/es-ES/data/reusables/user_settings/account_settings.md b/translations/es-ES/data/reusables/user_settings/account_settings.md new file mode 100644 index 0000000000000..c38c7bbe42890 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/account_settings.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Cuenta**. ![Opción de menú de configuración de cuenta](/assets/images/help/settings/settings-sidebar-account-settings.png) diff --git a/translations/es-ES/data/reusables/user_settings/add_and_verify_email.md b/translations/es-ES/data/reusables/user_settings/add_and_verify_email.md new file mode 100644 index 0000000000000..e9574dd3a935b --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/add_and_verify_email.md @@ -0,0 +1,4 @@ +{% if currentVersion != "github-ae@latest" %} +1. En "Agregar dirección de correo electrónico", teclea tu dirección de correo electrónico y da clic en **Agregar**. ![Email addition button](/assets/images/help/settings/add-email-address.png){% if currentVersion == "free-pro-team@latest" %} +2. [Verifica tu dirección de correo electrónico](/articles/verifying-your-email-address).{% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/automatic_watching_box.md b/translations/es-ES/data/reusables/user_settings/automatic_watching_box.md new file mode 100644 index 0000000000000..a4c5ce0d12537 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/automatic_watching_box.md @@ -0,0 +1 @@ +1. Debajo de "Observar automáticamente", diff --git a/translations/es-ES/data/reusables/user_settings/billing.md b/translations/es-ES/data/reusables/user_settings/billing.md new file mode 100644 index 0000000000000..fc5108d5f6461 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/billing.md @@ -0,0 +1 @@ +1. En tu barra lateral de configuración de usuario, da clic en **Facturación**. ![Configuración de facturación](/assets/images/help/settings/settings-sidebar-billing.png) diff --git a/translations/es-ES/data/reusables/user_settings/blocked_users.md b/translations/es-ES/data/reusables/user_settings/blocked_users.md new file mode 100644 index 0000000000000..6ad845af3d953 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/blocked_users.md @@ -0,0 +1 @@ +1. En tu barra lateral de configuración, da clic en **Usuarios bloqueados**. ![Pestaña de usuarios bloqueados](/assets/images/help/settings/settings-sidebar-blocked-users.png) diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/confirm_git_email_address_correct.md b/translations/es-ES/data/reusables/user_settings/confirm_git_email_address_correct.md new file mode 100644 index 0000000000000..ec6e3181f3e97 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/confirm_git_email_address_correct.md @@ -0,0 +1 @@ +Confirma que has establecido correctamente la dirección de correo electrónico en Git: diff --git a/translations/es-ES/data/reusables/user_settings/confirm_git_username_correct.md b/translations/es-ES/data/reusables/user_settings/confirm_git_username_correct.md new file mode 100644 index 0000000000000..069f35f72c652 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/confirm_git_username_correct.md @@ -0,0 +1 @@ +Confirma que has establecido correctamente el nombre de usuario en Git: diff --git a/translations/es-ES/data/reusables/user_settings/cost-management-tab.md b/translations/es-ES/data/reusables/user_settings/cost-management-tab.md new file mode 100644 index 0000000000000..a1ab891af101d --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/cost-management-tab.md @@ -0,0 +1 @@ +1. Debajo de "Facturación", da clic en **Administración de costos**. ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/deleted-repos.md b/translations/es-ES/data/reusables/user_settings/deleted-repos.md new file mode 100644 index 0000000000000..db48d0f6624fd --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/deleted-repos.md @@ -0,0 +1 @@ +1. Debajo de "Repositorios", da clic en **Repositorios borrados**". ![Pestaña de repositorios borrados](/assets/images/help/settings/deleted-repos.png) diff --git a/translations/es-ES/data/reusables/user_settings/developer_settings.md b/translations/es-ES/data/reusables/user_settings/developer_settings.md new file mode 100644 index 0000000000000..e1268dd5a00a6 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/developer_settings.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Configuración de desarrollador](/assets/images/help/settings/developer-settings.png) diff --git a/translations/es-ES/data/reusables/user_settings/emails.md b/translations/es-ES/data/reusables/user_settings/emails.md new file mode 100644 index 0000000000000..793d3d5e6e733 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/emails.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Correos Electrónicos**. ![Pestaña de correos electrónicos](/assets/images/help/settings/settings-sidebar-emails.png) diff --git a/translations/es-ES/data/reusables/user_settings/export-data.md b/translations/es-ES/data/reusables/user_settings/export-data.md new file mode 100644 index 0000000000000..f0505af0a5169 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/export-data.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" %} +Puedes exportar y revisar los metadatos que +almacena {% data variables.product.product_name %} sobre tu cuenta personal. +{% endif %} diff --git a/translations/es-ES/data/reusables/user_settings/jira_help_docs.md b/translations/es-ES/data/reusables/user_settings/jira_help_docs.md new file mode 100644 index 0000000000000..6de6f0f30d480 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/jira_help_docs.md @@ -0,0 +1 @@ +1. Vincula tu cuenta de GitHub con Jira. Para obtener más información, consulta la [Documentación de ayuda de Atlassian](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html). diff --git a/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md new file mode 100644 index 0000000000000..522e297d6161d --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md @@ -0,0 +1 @@ +5. Para mantener tu dirección de correo electrónico como privada cuando realices operaciones de Git basadas en la web, da clic en **Mantener mi dirección de correo electrónico como privada**. ![Imagen de casilla para mantener tu dirección de correo electrónico como privada](/assets/images/help/settings/email_privacy.png) diff --git a/translations/es-ES/data/reusables/user_settings/link_email_with_your_account.md b/translations/es-ES/data/reusables/user_settings/link_email_with_your_account.md new file mode 100644 index 0000000000000..07f5f0a989dd4 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/link_email_with_your_account.md @@ -0,0 +1,4 @@ +{% if currentVersion != "github-ae@latest" %} +Agrega la dirección de correo electrónico a tu cuenta en +{% data variables.product.product_name %}, para que se te atribuyan tus confirmaciones y aparezcas en la gráfica de colaboradores. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)". +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/no-verification-disposable-emails.md b/translations/es-ES/data/reusables/user_settings/no-verification-disposable-emails.md new file mode 100644 index 0000000000000..715c0215928c3 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/no-verification-disposable-emails.md @@ -0,0 +1 @@ +No puedes verificar una dirección de correo electrónico de dominios desechables. Si te gustaría mantener tu dirección de correo electrónico como privada, puedes utilizar la dirección de correo electrónico de `noreply` proporcionada por {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones en {% data variables.product.prodname_dotcom %}](/articles/setting-your-commit-email-address#setting-your-commit-email-address-on-github)". diff --git a/translations/es-ES/data/reusables/user_settings/notifications.md b/translations/es-ES/data/reusables/user_settings/notifications.md new file mode 100644 index 0000000000000..e44f6f590b86c --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/notifications.md @@ -0,0 +1 @@ +1. En la barra lateral de la configuración de usuario, da clic en **Notificaciones**. ![Centro de notificaciones](/assets/images/help/settings/settings-sidebar-notifications.png) diff --git a/translations/es-ES/data/reusables/user_settings/organizations.md b/translations/es-ES/data/reusables/user_settings/organizations.md new file mode 100644 index 0000000000000..78aed7402bf24 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/organizations.md @@ -0,0 +1 @@ +1. En la barra lateral de configuración de usuario, da clic en **Organizaciones**. ![Configuración de usuario para organizaciones](/assets/images/help/settings/settings-user-orgs.png) diff --git a/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation-desktop.md b/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation-desktop.md new file mode 100644 index 0000000000000..9c46a6be7d9ac --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation-desktop.md @@ -0,0 +1,5 @@ + {% warning %} + + **Advertencia**: Autenticarse en {% data variables.product.prodname_dotcom %} utilizand tu nombre de usuario y contraseña está en desuso. En vez de esto, te recomendamos autenticarte utilizando el buscador. + + {% endwarning %} diff --git a/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation.md b/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation.md new file mode 100644 index 0000000000000..f2bda806be77b --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/password-authentication-deprecation.md @@ -0,0 +1 @@ +Cuando Git pide tu contraseña, ingresa tu token de acceso personal (PAT) en vez de ésta.{% if currentVersion != "github-ae@latest" %} Para Git, se ha obsoletizado la autenticación basada en contraseñas y utilizar un PAT es más seguro.{% endif %} Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". diff --git a/translations/es-ES/data/reusables/user_settings/payment-info-tab.md b/translations/es-ES/data/reusables/user_settings/payment-info-tab.md new file mode 100644 index 0000000000000..5bcf1150fc982 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/payment-info-tab.md @@ -0,0 +1 @@ +1. Da clic en **Información de pago**. ![Pestaña de información de pago](/assets/images/help/settings/payment-info-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/personal_access_tokens.md b/translations/es-ES/data/reusables/user_settings/personal_access_tokens.md new file mode 100644 index 0000000000000..e7421efd7a0cb --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/personal_access_tokens.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Tokens de acceso personal**. ![Tokens de acceso personal](/assets/images/help/settings/personal_access_tokens_tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/personal_dashboard.md b/translations/es-ES/data/reusables/user_settings/personal_dashboard.md new file mode 100644 index 0000000000000..43025541c26f9 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/personal_dashboard.md @@ -0,0 +1 @@ +{% if currentVersion == "free-pro-team@latest" %}[tablero personal](https://github.com/dashboard){% else %}tablero personal(`https://[hostname]/dashboard`){% endif %} diff --git a/translations/es-ES/data/reusables/user_settings/removes-personal-access-tokens.md b/translations/es-ES/data/reusables/user_settings/removes-personal-access-tokens.md new file mode 100644 index 0000000000000..307f8f807e9ad --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/removes-personal-access-tokens.md @@ -0,0 +1 @@ +Como precaución de seguridad, {% data variables.product.prodname_dotcom %} elimina automáticamente los tokens de acceso personales que no se han usado durante un año. diff --git a/translations/es-ES/data/reusables/user_settings/repo-tab.md b/translations/es-ES/data/reusables/user_settings/repo-tab.md new file mode 100644 index 0000000000000..bbf235fd23df3 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/repo-tab.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/repos-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/restore-confirmation.md b/translations/es-ES/data/reusables/user_settings/restore-confirmation.md new file mode 100644 index 0000000000000..feb88597f50db --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/restore-confirmation.md @@ -0,0 +1 @@ +1. Lee la advertencia y da clic en **Entiendo, restaurar este repositorio**. ![Botón para confirmar restauración](/assets/images/help/settings/confirm-restoration-button.png) diff --git a/translations/es-ES/data/reusables/user_settings/restore-repo.md b/translations/es-ES/data/reusables/user_settings/restore-repo.md new file mode 100644 index 0000000000000..81ad52fe061fd --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/restore-repo.md @@ -0,0 +1 @@ +1. Junto al repositorio que quieres restaurar, da clic en **Restaurar**. ![Botón de restaurar](/assets/images/help/settings/restore-button.png) diff --git a/translations/es-ES/data/reusables/user_settings/review-oauth-apps.md b/translations/es-ES/data/reusables/user_settings/review-oauth-apps.md new file mode 100644 index 0000000000000..b052fef60f3c7 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/review-oauth-apps.md @@ -0,0 +1 @@ +1. Revisa los tokens que tienen acceso a tu cuenta. Para aquellos que no reconoces o que han caducado, da clic en **{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}**, y luego en **Revocar**. Para revocar todos los tokens, da clic en **Revocar todos**. ![Lista de {% data variables.product.prodname_oauth_app %} autorizadas](/assets/images/help/settings/revoke-oauth-app.png) diff --git a/translations/es-ES/data/reusables/user_settings/review_oauth_tokens_tip.md b/translations/es-ES/data/reusables/user_settings/review_oauth_tokens_tip.md new file mode 100644 index 0000000000000..9f2210b237bb8 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/review_oauth_tokens_tip.md @@ -0,0 +1 @@ +Te recomendamos que revises frecuentemente tus integraciones autorizadas. Elimina cualquier aplicación y tokens que no se hayan utilizado en mucho tiempo. Para obtener más información, consulta la sección "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)". diff --git a/translations/es-ES/data/reusables/user_settings/saved_replies.md b/translations/es-ES/data/reusables/user_settings/saved_replies.md new file mode 100644 index 0000000000000..e021c903da748 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/saved_replies.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Respuestas guardadas**. ![Pestaña de respuestas guardadas](/assets/images/help/settings/saved-replies-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/security-analysis.md b/translations/es-ES/data/reusables/user_settings/security-analysis.md new file mode 100644 index 0000000000000..833c5cd4edda4 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/security-analysis.md @@ -0,0 +1 @@ +1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Configuración de análisis y seguridad](/assets/images/help/settings/settings-sidebar-security-analysis.png) diff --git a/translations/es-ES/data/reusables/user_settings/security.md b/translations/es-ES/data/reusables/user_settings/security.md new file mode 100644 index 0000000000000..ede6944d474e7 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/security.md @@ -0,0 +1,4 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}1. En la barra lateral izquierda, da clic en **Seguridad de cuenta**. +![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-account-security.png) +{% else %}1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). +![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-security.png){% endif %} diff --git a/translations/es-ES/data/reusables/user_settings/select_primary_email.md b/translations/es-ES/data/reusables/user_settings/select_primary_email.md new file mode 100644 index 0000000000000..4414ceb0a43de --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/select_primary_email.md @@ -0,0 +1 @@ +1. En la lista de "Dirección de correo electrónico principal", selecciona la dirección que quieres asociar con tus operaciones de Git basadas en web. ![Selección de dirección de correo electrónico principal](/assets/images/help/settings/email_primary.png) diff --git a/translations/es-ES/data/reusables/user_settings/set_your_email_address_in_git.md b/translations/es-ES/data/reusables/user_settings/set_your_email_address_in_git.md new file mode 100644 index 0000000000000..58218a38a0baa --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/set_your_email_address_in_git.md @@ -0,0 +1 @@ +Configurar una dirección de correo electrónico en Git. Puedes utilizar {% if currentVersion == "free-pro-team@latest"%}tu [dirección de correo electrónico de tipo `no-reply` que proporcionó {% data variables.product.product_name %}](/articles/setting-your-commit-email-address) o {% endif %}cualquier dirección de correo electrónico. diff --git a/translations/es-ES/data/reusables/user_settings/set_your_git_username.md b/translations/es-ES/data/reusables/user_settings/set_your_git_username.md new file mode 100644 index 0000000000000..5d4c47fcea45d --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/set_your_git_username.md @@ -0,0 +1 @@ +Establece un nombre de usuario en Git: diff --git a/translations/es-ES/data/reusables/user_settings/ssh.md b/translations/es-ES/data/reusables/user_settings/ssh.md new file mode 100644 index 0000000000000..f646ee2d0da44 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/ssh.md @@ -0,0 +1 @@ +1. En la barra lateral de configuración de usuario, da clic en **Llaves SSH y GPG**. ![Llaves de autenticación](/assets/images/help/settings/settings-sidebar-ssh-keys.png) diff --git a/translations/es-ES/data/reusables/user_settings/subscriptions-tab.md b/translations/es-ES/data/reusables/user_settings/subscriptions-tab.md new file mode 100644 index 0000000000000..1aeacc4ea27a2 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/subscriptions-tab.md @@ -0,0 +1 @@ +1. Da clic en **Suscripciones**. ![Pestaña Subscriptions (Suscripciones)](/assets/images/help/settings/subscriptions-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/sudo-mode-popup.md b/translations/es-ES/data/reusables/user_settings/sudo-mode-popup.md new file mode 100644 index 0000000000000..ab61ec0cb47af --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/sudo-mode-popup.md @@ -0,0 +1 @@ +1. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) diff --git a/translations/es-ES/data/reusables/user_settings/verify-org-approved-email-domain.md b/translations/es-ES/data/reusables/user_settings/verify-org-approved-email-domain.md new file mode 100644 index 0000000000000..d5e274fad2b4e --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/verify-org-approved-email-domain.md @@ -0,0 +1 @@ +Si alguna organización de la cual eres miembro restringe las notificaciones por correo electrónico a un dominio de correo electrónico aprobado, deberás verificar la dirección en el dominio para recibir las notificaciones de actividad en la organización por este medio. Para obtener más información, consulta "[Restringir las notificaciones por correo electrónico a un dominio aprobado](/articles/restricting-email-notifications-to-an-approved-domain)". diff --git a/translations/es-ES/data/reusables/webhooks/action_type_desc.md b/translations/es-ES/data/reusables/webhooks/action_type_desc.md new file mode 100644 index 0000000000000..acc176d75af9a --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/action_type_desc.md @@ -0,0 +1 @@ +El tipo de actividad se especifica en la propiedad `action` del objeto de la carga útil. diff --git a/translations/es-ES/data/reusables/webhooks/app_always_desc.md b/translations/es-ES/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000000..11a956d348617 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | La instalación de {% data variables.product.prodname_github_app %}. diff --git a/translations/es-ES/data/reusables/webhooks/app_desc.md b/translations/es-ES/data/reusables/webhooks/app_desc.md new file mode 100644 index 0000000000000..131628794bfa9 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/app_desc.md @@ -0,0 +1 @@ +`installation` | `object` | La instalación de {% data variables.product.prodname_github_app %}. Las cargas útiles de los webhooks contienen la propiedad `installation` cuando el evento se envía y se configura para una {% data variables.product.prodname_github_app %}. diff --git a/translations/es-ES/data/reusables/webhooks/authorization_event.md b/translations/es-ES/data/reusables/webhooks/authorization_event.md new file mode 100644 index 0000000000000..89c9f520975e6 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/authorization_event.md @@ -0,0 +1 @@ +Cualquiera puede revocar su autorización a una GitHub App desde su [página de ajustes de cuenta de GitHub](https://github.com/settings/apps/authorizations). Revocar la autorización de una GitHub App no la desinstalará. Debes programar tu GitHub App para que cuando reciba su webhook deje de llamar a la API en nombre de la persona que revocó el token. Si tu GitHub App sigue utilizando un token de acceso revocado, esta recibirá el error `401 Bad Credentials`. diff --git a/translations/es-ES/data/reusables/webhooks/check_run_properties.md b/translations/es-ES/data/reusables/webhooks/check_run_properties.md new file mode 100644 index 0000000000000..52cd67ae99370 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/check_run_properties.md @@ -0,0 +1,11 @@ +| Clave | Type | Descripción | +| --------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
    • `created` - Se creó una ejecución de verificación.
    • `completed` - El `status` de la ejecución de verificación es `completed`.
    • `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción de tipo `rerequested`, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
    • `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y las acciones solicitadas, consulta la sección "[Ejecuciones de ferificación y acciones solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
    | +| `check_run` | `object` | La [check_run](/rest/reference/checks#get-a-check-run). | +| `check_run[status]` | `secuencia` | El estado actual de la ejecución de verificación. Puede ser `queued`, `in_progress`, o `completed`. | +| `check_run[conclusion]` | `secuencia` | El resultado de la ejecución de verificación que se completó. Puede ser uno de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | +| `check_run[name]` | `secuencia` | El nombre de la ejecución de verificación. | +| `check_run[check_suite][id]` | `número` | La id de la suite de verificaciones de la cual es parte esta ejecución de verificación. | +| `check_run[check_suite][pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de extracción que empata con una suite de verificaciones si tienen el mismo `head_sha` y `head_branch`. Cuando la `head_branch` de la suite de verificaciones está en un repositorio bifurcado, este será `null` y la matriz de `pull_requests` estará vacía. | +| `requested_action` | `object` | La acción que solicitó el usuario. | +| `requested_action[identifier]` | `secuencia` | La referencia del integrador de la acción que solicitó el usuario. | diff --git a/translations/es-ES/data/reusables/webhooks/check_run_short_desc.md b/translations/es-ES/data/reusables/webhooks/check_run_short_desc.md new file mode 100644 index 0000000000000..2e853417becf4 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/check_run_short_desc.md @@ -0,0 +1 @@ +Ha ocurrido una actividad de ejecución de verificación. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[ejecuciones de verificación](/rest/reference/checks#runs)". diff --git a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md new file mode 100644 index 0000000000000..2788d1bb49693 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md @@ -0,0 +1,10 @@ +| Clave | Type | Descripción | +| ---------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser:
    • `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
    • `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuando recibes un evento de acción de tipo `requested`, necesitarás [Crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run).
    • `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibes los eventos de una acción de tipo `rerequested, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
    | +| `check_suite` | `object` | La [check_suite](/rest/reference/checks#suites). | +| `check_suite[head_branch]` | `secuencia` | El nombre de la rama principal en la cual están los cambios. | +| `check_suite[head_sha]` | `secuencia` | El SHA de la confirmación más reciente para esta suite de verificaciones. | +| `check_suite[status]` | `secuencia` | El estado de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser `requested`, `in_progress`, o `completed`. | +| `check_suite[conclusion]` | `secuencia` | La conclusión de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser uno de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | +| `check_suite[url]` | `secuencia` | La URL que apunta al recurso de la API de suite de verificación. | +| `check_suite[pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de extracción que empata con una suite de verificaciones si tienen el mismo `head_sha` y `head_branch`. Cuando la `head_branch` de la suite de verificaciones está en un repositorio bifurcado, este será `null` y la matriz de `pull_requests` estará vacía. | diff --git a/translations/es-ES/data/reusables/webhooks/check_suite_short_desc.md b/translations/es-ES/data/reusables/webhooks/check_suite_short_desc.md new file mode 100644 index 0000000000000..62eeae9d66a02 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/check_suite_short_desc.md @@ -0,0 +1 @@ +Ha ocurrido una actividad de suite de verificaciones. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[suites de verificaciones](/rest/reference/checks#suites)". diff --git a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md new file mode 100644 index 0000000000000..6e32e080efb28 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md @@ -0,0 +1,6 @@ +| Clave | Type | Descripción | +| ------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Este puede ser uno de entre `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, o `reopened`. | +| `alert` | `object` | La alerta de escaneo de código involucrada en el evento. | +| `ref` | `secuencia` | La referencia de Git de la alerta de escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío. | +| `commit_oid` | `secuencia` | El SHA de la confirmación de la alerta del escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío. | diff --git a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_short_desc.md b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000000..e4dabddb96cbc --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Actividad relacionada con las alertas de escaneo de código en un repositorio. El tipo de actividad se especifica en la propiedad de la acción del objeto de la carga útil. Para obtener más información, consulta la sección "[Acerca del escaneo de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". diff --git a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md new file mode 100644 index 0000000000000..a612edded178d --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| --------- | ----------- | ------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | +| `comment` | `object` | El recurso de [comentario de la confirmación](/rest/reference/repos#get-a-commit-comment). | diff --git a/translations/es-ES/data/reusables/webhooks/commit_comment_short_desc.md b/translations/es-ES/data/reusables/webhooks/commit_comment_short_desc.md new file mode 100644 index 0000000000000..caa7ece53ae84 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/commit_comment_short_desc.md @@ -0,0 +1 @@ +Se creó un comentario de una confirmación. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentario de confirmación](/rest/reference/repos#comments)". diff --git a/translations/es-ES/data/reusables/webhooks/content_reference_short_desc.md b/translations/es-ES/data/reusables/webhooks/content_reference_short_desc.md new file mode 100644 index 0000000000000..49dc1f765c70e --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/content_reference_short_desc.md @@ -0,0 +1 @@ +Una referencia de contenido nueva se muestra como `created`. Se crea una referenci de contenido nueva cuando el cuerpo o el comentario de un informe de problemas o solicitud de extracción incluye un URL que empte con un dominio de referencia de contenido configurado. Para obtener más información, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments/)" para aprender más sobre las referencias de contenido y sus adjuntos. diff --git a/translations/es-ES/data/reusables/webhooks/content_type.md b/translations/es-ES/data/reusables/webhooks/content_type.md new file mode 100644 index 0000000000000..d26accf02a58e --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/content_type.md @@ -0,0 +1,6 @@ +Los webhooks pueden entregarse utilizando diferentes tipos de contenido: + +- El tipo de contenido `application/json` entregará la carga útil de JSON directametne como el cuerpo de la solicitud `POST`. +- El tipo de contenido `application/x-www-form-urlencoded` enviará la carga útil de JSON como un parámetro de forma llamado `payload`. + +Elige el que se adapte mejor a tus necesidades. diff --git a/translations/es-ES/data/reusables/webhooks/create_properties.md b/translations/es-ES/data/reusables/webhooks/create_properties.md new file mode 100644 index 0000000000000..987b737e98175 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/create_properties.md @@ -0,0 +1,6 @@ +| Clave | Type | Descripción | +| --------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference). | +| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`. | +| `master_branch` | `secuencia` | El nombre de la rama predeterminada del repositorio (habitualmente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | +| `description` | `secuencia` | La descripción actual del repositorio. | diff --git a/translations/es-ES/data/reusables/webhooks/create_short_desc.md b/translations/es-ES/data/reusables/webhooks/create_short_desc.md new file mode 100644 index 0000000000000..4de4665ba33cb --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/create_short_desc.md @@ -0,0 +1 @@ +Se crea una rama o etiqueta de Git. Para obtener más información, consulta la API de REST de "[Datos de Git](/rest/reference/git)". diff --git a/translations/es-ES/data/reusables/webhooks/delete_properties.md b/translations/es-ES/data/reusables/webhooks/delete_properties.md new file mode 100644 index 0000000000000..727ad32af7da0 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/delete_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| ---------- | ----------- | ---------------------------------------------------------------------------------------- | +| `ref` | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference). | +| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se borró en el repositorio. Puede ser `branch` o `tag`. | diff --git a/translations/es-ES/data/reusables/webhooks/delete_short_desc.md b/translations/es-ES/data/reusables/webhooks/delete_short_desc.md new file mode 100644 index 0000000000000..5e721a774b40b --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/delete_short_desc.md @@ -0,0 +1 @@ +Se borra una rama o etiqueta de Git. Para obtener más información, consulta la API de REST de "[Datos de Git](/rest/reference/git)". diff --git a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md new file mode 100644 index 0000000000000..f359bc37f46d8 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`. | +| `clave` | `object` | El recurso [`deploy key`](/rest/reference/repos#get-a-deploy-key). | diff --git a/translations/es-ES/data/reusables/webhooks/deploy_key_short_desc.md b/translations/es-ES/data/reusables/webhooks/deploy_key_short_desc.md new file mode 100644 index 0000000000000..8b55a7b9f12f5 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/deploy_key_short_desc.md @@ -0,0 +1 @@ +Una llave de despliegue se agrega o se elimina de un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Llaves de despliegue](/rest/reference/repos#keys)". diff --git a/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md b/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md new file mode 100644 index 0000000000000..3a24e63128b80 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md @@ -0,0 +1 @@ +Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[despliegue](/rest/reference/repos#list-deployments)". diff --git a/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md b/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md new file mode 100644 index 0000000000000..77c5609e152fa --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md @@ -0,0 +1 @@ +Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados de despliegue](/rest/reference/repos#list-deployment-statuses)". diff --git a/translations/es-ES/data/reusables/webhooks/enterprise_short_desc.md b/translations/es-ES/data/reusables/webhooks/enterprise_short_desc.md new file mode 100644 index 0000000000000..c21df92bde5ac --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/enterprise_short_desc.md @@ -0,0 +1 @@ +Un administrador de repositorio o de sitio habilita o inhabilita el acceso de lectura anónimo de Git. Consulta "[Permitir que los administradores habiliten el acceso de lectura anónimo de Git en los repositorios públicos](/enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)" para obtener más detalles. Este evento no está disponible en la API de Eventos. diff --git a/translations/es-ES/data/reusables/webhooks/events_api_payload.md b/translations/es-ES/data/reusables/webhooks/events_api_payload.md new file mode 100644 index 0000000000000..2c699ef99f073 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/events_api_payload.md @@ -0,0 +1 @@ +El [objeto del evento](#event-object-common-properties) incluye propiedades que son comunes para todos los eventos. Cada objeto de evento incluye una propiedad de `payload` y el valor es único para cada tipo de evento. El objeto de `payload` para este evento se describe a continuación. diff --git a/translations/es-ES/data/reusables/webhooks/fork_properties.md b/translations/es-ES/data/reusables/webhooks/fork_properties.md new file mode 100644 index 0000000000000..1480462d774f2 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/fork_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | -------- | --------------------------------------------------------------------------------- | +| `forkee` | `object` | El recurso de [`repository`](/rest/reference/repos#get-a-repository) que se creó. | diff --git a/translations/es-ES/data/reusables/webhooks/fork_short_desc.md b/translations/es-ES/data/reusables/webhooks/fork_short_desc.md new file mode 100644 index 0000000000000..5527572038c46 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/fork_short_desc.md @@ -0,0 +1 @@ +Un usuario bifurca un repositorio. Para obtener más información, consulta la API de REST de "[bifurcaciones](/rest/reference/repos#forks)". diff --git a/translations/es-ES/data/reusables/webhooks/gollum_properties.md b/translations/es-ES/data/reusables/webhooks/gollum_properties.md new file mode 100644 index 0000000000000..98ca0e4bf3473 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/gollum_properties.md @@ -0,0 +1,8 @@ +| Clave | Type | Descripción | +| -------------------- | ----------- | ---------------------------------------------------------------------- | +| `páginas` | `arreglo` | Las páginas que se actualizaron. | +| `pages[][page_name]` | `secuencia` | El nombre de la página. | +| `pages[][title]` | `secuencia` | El título de la página actual. | +| `pages[][action]` | `secuencia` | La acción que se realizó en la página. Puede ser `created` o `edited`. | +| `pages[][sha]` | `secuencia` | El SHA de confirmación más reciente de la página. | +| `pages[][html_url]` | `secuencia` | Apunta a la página de wiki de HMTL. | diff --git a/translations/es-ES/data/reusables/webhooks/gollum_short_desc.md b/translations/es-ES/data/reusables/webhooks/gollum_short_desc.md new file mode 100644 index 0000000000000..362fef5bebe56 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/gollum_short_desc.md @@ -0,0 +1 @@ +Se crea o actualiza una página de wiki. Para obtener más información, consulta la sección "[Acerca de las wikis](/github/building-a-strong-community/about-wikis)". diff --git a/translations/es-ES/data/reusables/webhooks/installation_properties.md b/translations/es-ES/data/reusables/webhooks/installation_properties.md new file mode 100644 index 0000000000000..882919b414283 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/installation_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| -------------- | ----------- | ----------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
    • `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
      • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
    • `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
    • `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
      • {% endif %}
    • `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
    | +| `repositories` | `arreglo` | Un areglo de objetos de repositorio al que puede acceder la instalación. | diff --git a/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md new file mode 100644 index 0000000000000..ecbe522cdbca1 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md @@ -0,0 +1,6 @@ +| Clave | Type | Descripción | +| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser tanto `added` como `removed`. | +| `repository_selection` | `secuencia` | La elección de repositorios en los cuales se encuentra la instalación. Puede ser tanto `selected` como `all`. | +| `repositories_added` | `arreglo` | Una matriz de objetos del repositorio, los cuales se agregaron a la instalación. | +| `repositories_removed` | `arreglo` | Una matriz de objetos del repositorio, los cuales se eliminaron de la instalación. | diff --git a/translations/es-ES/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/es-ES/data/reusables/webhooks/installation_repositories_short_desc.md new file mode 100644 index 0000000000000..1766da69b7d3b --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/installation_repositories_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con los repositorios que se está agregando a la instalación de la GitHub App. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Instalación de GitHub Apps](/rest/reference/apps)". diff --git a/translations/es-ES/data/reusables/webhooks/installation_short_desc.md b/translations/es-ES/data/reusables/webhooks/installation_short_desc.md new file mode 100644 index 0000000000000..05bdcdafde1ae --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/installation_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con la instalación de una GitHub App. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Instalación de GitHub Apps](/rest/reference/apps)". diff --git a/translations/es-ES/data/reusables/webhooks/issue_comment_properties.md b/translations/es-ES/data/reusables/webhooks/issue_comment_properties.md new file mode 100644 index 0000000000000..4e5787b73e3d5 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_comment_properties.md @@ -0,0 +1 @@ +`changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `issue`|`object` | El [issue](/rest/reference/issues) al cual pertenece el comentario. `comment`|`object` | El [comment](/rest/reference/issues#comments) mismo. diff --git a/translations/es-ES/data/reusables/webhooks/issue_comment_short_desc.md b/translations/es-ES/data/reusables/webhooks/issue_comment_short_desc.md new file mode 100644 index 0000000000000..b59d7c0d38502 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_comment_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con el comentario de un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentrios del informe de problemas](/rest/reference/issues#comments)". diff --git a/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md new file mode 100644 index 0000000000000..517915c39f43d --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | -------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | diff --git a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md new file mode 100644 index 0000000000000..42e5ad095fa8f --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, o `unlabeled`. | diff --git a/translations/es-ES/data/reusables/webhooks/issue_properties.md b/translations/es-ES/data/reusables/webhooks/issue_properties.md new file mode 100644 index 0000000000000..37b844378d9ac --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_properties.md @@ -0,0 +1 @@ +`issue`|`object` | El [issue](/rest/reference/issues) mismo. `changes`|`object`| Los cambios al informe de problemas si la acción está como `edited`. `changes[title][from]`|`string` | La versión previa del título si la acción fue `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `assignee`|`object` | El usuario opcional que se asignó o se desasignó del informe de problemas. `label`|`object` | La etiqueta opcional que se agregó o que se eliminó del informe de problemas. diff --git a/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md new file mode 100644 index 0000000000000..0b69e0fa291a4 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`, `transferred`, `milestoned`, o `demilestoned`. | diff --git a/translations/es-ES/data/reusables/webhooks/issues_short_desc.md b/translations/es-ES/data/reusables/webhooks/issues_short_desc.md new file mode 100644 index 0000000000000..a73bee3ebef69 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/issues_short_desc.md @@ -0,0 +1 @@ +La actividar relacionada con un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[informe de problemas](/rest/reference/issues#comments)". diff --git a/translations/es-ES/data/reusables/webhooks/label_short_desc.md b/translations/es-ES/data/reusables/webhooks/label_short_desc.md new file mode 100644 index 0000000000000..2bd53a6f815db --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/label_short_desc.md @@ -0,0 +1 @@ +La actividar relacionada con un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[etiquetas](/rest/reference/issues#labels)". diff --git a/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md new file mode 100644 index 0000000000000..46d749a875810 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ---------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `added` para indicar que un usuario aceptó una invitación al repositorio. | diff --git a/translations/es-ES/data/reusables/webhooks/member_properties.md b/translations/es-ES/data/reusables/webhooks/member_properties.md new file mode 100644 index 0000000000000..babbf914f8fc1 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/member_properties.md @@ -0,0 +1 @@ +`member`|`object` | El [user](/rest/reference/users) que se agregó. `changes`|`object`| Los cambios a los permisos del colaborador si la acción fue `edited`. `changes[old_permission][from]`|`string` | Los permisos previos del colaborador si la acción fue `edited`. diff --git a/translations/es-ES/data/reusables/webhooks/member_short_desc.md b/translations/es-ES/data/reusables/webhooks/member_short_desc.md new file mode 100644 index 0000000000000..86bac111d2032 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/member_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con los colaboradores del repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[colaboradores](/rest/reference/repos#collaborators)". diff --git a/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md new file mode 100644 index 0000000000000..ff479a4024485 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ----------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `added` - Un usuario acepta una invitación a un repositorio.
    • `removed` - Se elimina a un usuario como colaborador de un repositorio.
    • `edited` - Han cambiado los permisos de colaborador de un usuario.
    | diff --git a/translations/es-ES/data/reusables/webhooks/membership_properties.md b/translations/es-ES/data/reusables/webhooks/membership_properties.md new file mode 100644 index 0000000000000..44c7354e3819f --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/membership_properties.md @@ -0,0 +1,6 @@ +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `added` o `removed`. | +| `scope` | `secuencia` | El alcance de la membrecía. Acutalmente, solo puede ser `team`. | +| `member` | `object` | El [usuario](/rest/reference/users) que se agregó o se eliminó. | +| `team` | `object` | El [equipo](/rest/reference/teams) para la membrecía. | diff --git a/translations/es-ES/data/reusables/webhooks/membership_short_desc.md b/translations/es-ES/data/reusables/webhooks/membership_short_desc.md new file mode 100644 index 0000000000000..e9106987ec54a --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/membership_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con la membrecía del equipo. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[miembros del equipo](/rest/reference/teams#members)". diff --git a/translations/es-ES/data/reusables/webhooks/milestone_properties.md b/translations/es-ES/data/reusables/webhooks/milestone_properties.md new file mode 100644 index 0000000000000..06486c0027653 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/milestone_properties.md @@ -0,0 +1,8 @@ +| Clave | Type | Descripción | +| ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre: `created`, `closed`, `opened`, `edited`, o `deleted`. | +| `milestone` | `object` | El hito mismo. | +| `changes` | `object` | Los cambios al hito si la acción se encuentra como `edited`. | +| `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | +| `changes[due_on][from]` | `secuencia` | La versión previa de la fecha límite si la acción se puso como `edited`. | +| `changes[title][from]` | `secuencia` | La versión previa del título si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/milestone_short_desc.md b/translations/es-ES/data/reusables/webhooks/milestone_short_desc.md new file mode 100644 index 0000000000000..4a9e2b8fab980 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/milestone_short_desc.md @@ -0,0 +1 @@ +La actividar relacionada con los hitos. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[hitos](/rest/reference/issues#milestones)". diff --git a/translations/es-ES/data/reusables/webhooks/org_block_short_desc.md b/translations/es-ES/data/reusables/webhooks/org_block_short_desc.md new file mode 100644 index 0000000000000..0cd4d1202dbad --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/org_block_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con las personas que se bloquearon en una organización. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST "[bloquear a usuarios de una organización](/rest/reference/orgs#blocking)". diff --git a/translations/es-ES/data/reusables/webhooks/org_desc.md b/translations/es-ES/data/reusables/webhooks/org_desc.md new file mode 100644 index 0000000000000..bd0bbf323e095 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/org_desc.md @@ -0,0 +1 @@ +`organization` | `object` | Las cargas útiles de webhook contienen el objeto [`organization`](/rest/reference/orgs#get-an-organization) cuando el webhook se configura para para una organización o cuando el evento ocurre desde una actividad en un repositorio que pertenezca a la organización. diff --git a/translations/es-ES/data/reusables/webhooks/organization_short_desc.md b/translations/es-ES/data/reusables/webhooks/organization_short_desc.md new file mode 100644 index 0000000000000..56a7091b14c1e --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/organization_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con una organización y sus miembros. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[organizaciones](/rest/reference/orgs)". diff --git a/translations/es-ES/data/reusables/webhooks/package_properties.md b/translations/es-ES/data/reusables/webhooks/package_properties.md new file mode 100644 index 0000000000000..6771591f64b88 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/package_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| --------- | ----------- | ------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `published` o `updated`. | +| `package` | `object` | La información sobre el paquete. | diff --git a/translations/es-ES/data/reusables/webhooks/page_build_short_desc.md b/translations/es-ES/data/reusables/webhooks/page_build_short_desc.md new file mode 100644 index 0000000000000..eeac88aa79e97 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/page_build_short_desc.md @@ -0,0 +1 @@ +Representa un intento de compilación de un sitio de {% data variables.product.prodname_pages %}, haya sido exitoso o no. Una subida a la rama habilitada de {% data variables.product.prodname_pages %} (`gh-pages` para las páginas de proyecto, la rama predeterminada para las páginas de usuario y de organización) desencadena este evento. diff --git a/translations/es-ES/data/reusables/webhooks/payload_url.md b/translations/es-ES/data/reusables/webhooks/payload_url.md new file mode 100644 index 0000000000000..f1e8760426cec --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/payload_url.md @@ -0,0 +1 @@ +La URL de carga útil es la URL del servidor que recibirá las solicitudes de `POST` del webhook. diff --git a/translations/es-ES/data/reusables/webhooks/ping_short_desc.md b/translations/es-ES/data/reusables/webhooks/ping_short_desc.md new file mode 100644 index 0000000000000..6b29d483427dc --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/ping_short_desc.md @@ -0,0 +1 @@ +Cuando creas un webhook nuevo, te enviaremos un evento de `ping` sencillo para informarte que configuraste el webhook correctamente. Este evento no se almacena, así que no se puede recuperar mediante la terminal de la [API de Eventos](/rest/reference/activity#ping-a-repository-webhook). diff --git a/translations/es-ES/data/reusables/webhooks/project_card_properties.md b/translations/es-ES/data/reusables/webhooks/project_card_properties.md new file mode 100644 index 0000000000000..37ceb89f5cb5a --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_card_properties.md @@ -0,0 +1,7 @@ +| Clave | Type | Descripción | +| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción llevada a cabo en la tarjeta del proyecto. Puede ser `created`, `edited`, `moved`, `converted`, o `deleted`. | +| `changes` | `object` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. | +| `changes[note][from]` | `secuencia` | La versión previa de la nota si la acción se puso como `edited` o `converted`. | +| `after_id` | `número` | La id de la tarjeta a la cual sigue esta tarjeta ahora si la acción se "movió". Será `null` si es la primera tarjeta en una columna. | +| `project_card` | `object` | La [tarjeta de proyecto](/rest/reference/projects#cards) misma. | diff --git a/translations/es-ES/data/reusables/webhooks/project_card_short_desc.md b/translations/es-ES/data/reusables/webhooks/project_card_short_desc.md new file mode 100644 index 0000000000000..bae59e814dd15 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_card_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con las tarjetas de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[tarjetas de proyecto](/rest/reference/projects#cards)". diff --git a/translations/es-ES/data/reusables/webhooks/project_column_properties.md b/translations/es-ES/data/reusables/webhooks/project_column_properties.md new file mode 100644 index 0000000000000..25cf36d5857ed --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_column_properties.md @@ -0,0 +1,7 @@ +| Clave | Type | Descripción | +| --------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó en la columna de proyecto. Puede ser una de entre `created`, `edited`, `moved` o `deleted`. | +| `changes` | `object` | Los cambios a la columna del proyecto si la acción se puso como `edited`. | +| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | +| `after_id` | `número` | La id de la columna a la cual sigue ahora esta coumna si la acción se "movió". Será `null` si es la primera columna en un proyecto. | +| `project_column` | `object` | La [columna de proyecto](/rest/reference/projects#columns) misma. | diff --git a/translations/es-ES/data/reusables/webhooks/project_column_short_desc.md b/translations/es-ES/data/reusables/webhooks/project_column_short_desc.md new file mode 100644 index 0000000000000..97f1196342615 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_column_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con las columnas en un tablero de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[columnas de proyecto](/rest/reference/projects#columns)". diff --git a/translations/es-ES/data/reusables/webhooks/project_properties.md b/translations/es-ES/data/reusables/webhooks/project_properties.md new file mode 100644 index 0000000000000..74323f9c8d852 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_properties.md @@ -0,0 +1,7 @@ +| Clave | Type | Descripción | +| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó en el proyecto. Puede ser uno de entre: `created`, `edited`, `closed`, `reopened`, o `deleted`. | +| `changes` | `object` | Los cambios al proyecto si la acción se puso como `edited`. | +| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | +| `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | +| `project` | `object` | El [proyecto](/rest/reference/projects) mismo. | diff --git a/translations/es-ES/data/reusables/webhooks/project_short_desc.md b/translations/es-ES/data/reusables/webhooks/project_short_desc.md new file mode 100644 index 0000000000000..a8dd6a2eb1838 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/project_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con los tableros de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[proyectos](/rest/reference/projects)". diff --git a/translations/es-ES/data/reusables/webhooks/public_short_desc.md b/translations/es-ES/data/reusables/webhooks/public_short_desc.md new file mode 100644 index 0000000000000..4da05f654ed2b --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/public_short_desc.md @@ -0,0 +1 @@ +Cuando un repositorio privado se hace público. Sin duda alguna: el mejor evento de {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md new file mode 100644 index 0000000000000..03fe366d0b3b4 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, y `synchronize`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_properties.md new file mode 100644 index 0000000000000..d79db18bf1c8d --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_properties.md @@ -0,0 +1 @@ +`number`|`integer` | El número de la solicitud de extracción. `changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[title][from]`|`string` | La versión previa del título si la acción fue `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `pull_request`|`object` | La [solicitud de extracción](/rest/reference/pulls) misma. diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md new file mode 100644 index 0000000000000..108cda8365926 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_properties.md new file mode 100644 index 0000000000000..421dd88f367fb --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_properties.md @@ -0,0 +1 @@ +`changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `pull_request`|`object` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece el comentario. `comment`|`object` | El [comentario](/rest/reference/pulls#comments) mismo. diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_short_desc.md new file mode 100644 index 0000000000000..8c92098c376f6 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_short_desc.md @@ -0,0 +1 @@ +La actividar relacionada con los comentarios de revisión de la solicitud de extracción en el diff unificado de la misma. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentrios de revisión de la solicitud de extracción](/rest/reference/pulls#comments)". diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md new file mode 100644 index 0000000000000..517915c39f43d --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | -------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md new file mode 100644 index 0000000000000..4871b22562039 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md @@ -0,0 +1,6 @@ +| Clave | Type | Descripción | +| ---------------------- | ----------- | ------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `submitted` - Se emitió una solicitud de extracción en un estado no pendiente.
    • `edited` - el cuerpo de una revisión se editó.
    • `dismissed` - Se descartó una revisión.
    | +| `solicitud_extracción` | `object` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece la revisión. | +| `review` | `object` | La revisión que se afectó. | +| `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_short_desc.md new file mode 100644 index 0000000000000..d22ec74105133 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con las revisiones de la solicitudes de extracción. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[revisiones de la solicitud de extracción](/rest/reference/pulls#reviews)". diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_short_desc.md b/translations/es-ES/data/reusables/webhooks/pull_request_short_desc.md new file mode 100644 index 0000000000000..78866e42839b8 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con las solicitudes de extracción. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[solicitudes de extracción](/rest/reference/pulls)". diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md new file mode 100644 index 0000000000000..99319e4126260 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, o `reopened`. Si la acción se muestra como `closed` y la llave `merged` es `false`, esto significa que la solicitud de extracción se cerró con las confirmaciones sin fusionar. Si la acción se muestra como `closed` y la llave `merged` es `true`, la solicitud de extracción se fusionó. | diff --git a/translations/es-ES/data/reusables/webhooks/push_short_desc.md b/translations/es-ES/data/reusables/webhooks/push_short_desc.md new file mode 100644 index 0000000000000..060ac1d19d6e0 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/push_short_desc.md @@ -0,0 +1 @@ +Se cargó una o más confirmaciones a la rama o etiqueta de un repositorio. diff --git a/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md new file mode 100644 index 0000000000000..32e6fa2985459 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `published`. | diff --git a/translations/es-ES/data/reusables/webhooks/release_properties.md b/translations/es-ES/data/reusables/webhooks/release_properties.md new file mode 100644 index 0000000000000..281ea0103c9a4 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/release_properties.md @@ -0,0 +1 @@ +`changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `changes[name][from]` |`string` | La versión previa del nombre si la acción aparece como `edited`. `release`|`object` | El objeto de [release](/rest/reference/repos/#get-a-release). diff --git a/translations/es-ES/data/reusables/webhooks/release_short_desc.md b/translations/es-ES/data/reusables/webhooks/release_short_desc.md new file mode 100644 index 0000000000000..1035c57929765 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/release_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con un lanzamiento. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[lanzamientos](/rest/reference/repos#releases)". diff --git a/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md new file mode 100644 index 0000000000000..fff2412103351 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `published`: se publica un lanzamiento, pre-lanzamiento, o borrador de un lanzamiento
    • `unpublished`: se borra un lanzamiento o pre-lanzamiento
    • `created`: se guarda un borrador, o se publica un lanzamiento o pre-lanzamiento sin que se haya guardado previamente como un borrador
    • `edited`: se edita un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `deleted`: se borra un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `prereleased`: se crea un pre-lanzamiento
    • `released`: se publica un lanzamiento o borrador de un lanzamiento, o se cambia un prelanzamiento a lanzamiento
      • | diff --git a/translations/es-ES/data/reusables/webhooks/repo_desc.md b/translations/es-ES/data/reusables/webhooks/repo_desc.md new file mode 100644 index 0000000000000..35266c9e9505c --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repo_desc.md @@ -0,0 +1 @@ +`repository` | `object` | El [`repositorio`](/rest/reference/repos#get-a-repository) en donde ocurrió el evento. diff --git a/translations/es-ES/data/reusables/webhooks/repository_import_properties.md b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md new file mode 100644 index 0000000000000..99b3bc9b4a1be --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------------------- | +| `status` | `secuencia` | El estado final de la importación. Este puede ser alguno de entre: `success`, `cancelled`, o `failure`. | diff --git a/translations/es-ES/data/reusables/webhooks/repository_import_short_desc.md b/translations/es-ES/data/reusables/webhooks/repository_import_short_desc.md new file mode 100644 index 0000000000000..5728e5f77643a --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repository_import_short_desc.md @@ -0,0 +1 @@ +La actividad relacionad con un repositorio que se está importando a GitHub. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[importaciones de código fuente](/rest/reference/migrations#source-imports)". diff --git a/translations/es-ES/data/reusables/webhooks/repository_short_desc.md b/translations/es-ES/data/reusables/webhooks/repository_short_desc.md new file mode 100644 index 0000000000000..52276d392d5c0 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repository_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[repositorios](/rest/reference/repos)". diff --git a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md new file mode 100644 index 0000000000000..423ee34b5e305 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Este puede ser alguno de entre: `create`, `dismiss`, o `resolve`. | +| `alert` | `object` | La alerta de seguridad de la dependencia vulnerable. | diff --git a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md new file mode 100644 index 0000000000000..08a5c71af4051 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md @@ -0,0 +1 @@ +Actividad relacionada con las alertas de vulnerabilidades de seguridad en un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la sección "[Acerca de las alertas de seguridad para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies)". diff --git a/translations/es-ES/data/reusables/webhooks/secret.md b/translations/es-ES/data/reusables/webhooks/secret.md new file mode 100644 index 0000000000000..936e87509e90c --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/secret.md @@ -0,0 +1 @@ +El configurar un secreto de webhook te permite garantizar que las solicitudes `POST` que se enviaron a la URL de la carga útil sean de {% data variables.product.product_name %}. Cuando configuras un secreto, recibirás los encabezados de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`X-Hub-Signature` y de `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 %} en la solicitud de `POST` del webhook. Para obtener más información sobre cómo utilizar uns ecreto con un encabezado de firma para asegurar tus cárgas útiles de webhook, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000000..a3ff7ef9298f0 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser ya sea `created`, `resolved`, o `reopened`. | +| `alert` | `object` | La alerta del escaneo de secretos involucrada en el evento. | diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000000..d6ce60ee0cb1c --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Actividad relacionada con las alertas del escaneo de secretos en un repositorio. El tipo de actividad se especifica en la propiedad de la acción del objeto de la carga útil. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)". diff --git a/translations/es-ES/data/reusables/webhooks/sender_desc.md b/translations/es-ES/data/reusables/webhooks/sender_desc.md new file mode 100644 index 0000000000000..b0e685a06a6d2 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/sender_desc.md @@ -0,0 +1 @@ +`sender` | `object` | El usuario que activó el evento. diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md new file mode 100644 index 0000000000000..178dc2e34dd84 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ---------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. | diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_properties.md new file mode 100644 index 0000000000000..2ff70bb3e8fbc --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_properties.md @@ -0,0 +1 @@ +`effective_date` | `string` | Los tipos de evento `pending_cancellation` y `pending_tier_change` incluirán la fecha en la que se hará válida la cancelación o el cambio de nivel. `changes[tier][from]` | `object` | El `tier_changed` o el `pending_tier_change` incluirán el nivel original antes del cambio o del cambio pendiente. Para obtener más información, consulta la sección "[carga útil de cambios para el nivel pendiente](/webhooks/event-payloads#webhook-payload-example-when-someone-downgrades-a-sponsorship)". `changes[privacy_level][from]` | `string` | Los tipos de evento `edited` incluyen los detalles sobre el cambio cuando alguien edita un patrocinio para cambiar su privacidad. diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md b/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md new file mode 100644 index 0000000000000..85ba1b3eafd73 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con un listado de patrocinio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta "[Acerca de los Patrocinadores de GitHub](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)". diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md new file mode 100644 index 0000000000000..ec56af4f778aa --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de entre: `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation`, o `pending_tier_change`. | diff --git a/translations/es-ES/data/reusables/webhooks/star_properties.md b/translations/es-ES/data/reusables/webhooks/star_properties.md new file mode 100644 index 0000000000000..634104251a375 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/star_properties.md @@ -0,0 +1,4 @@ +| Clave | Type | Descripción | +| ------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created` o `deleted`. | +| `starred_at` | `secuencia` | La hora en la cual se creó un marcado con estrella. {% data reusables.shortdesc.iso_8601 %} Será `null` para las acciones que estén como `deleted`. | diff --git a/translations/es-ES/data/reusables/webhooks/star_short_desc.md b/translations/es-ES/data/reusables/webhooks/star_short_desc.md new file mode 100644 index 0000000000000..72af3471ffb13 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/star_short_desc.md @@ -0,0 +1 @@ +La actividad relacionad con un repositorio que se está marcando con una estrella. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[marcar con una estrella](/rest/reference/activity#starring)". diff --git a/translations/es-ES/data/reusables/webhooks/status_short_desc.md b/translations/es-ES/data/reusables/webhooks/status_short_desc.md new file mode 100644 index 0000000000000..478f28d33f228 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/status_short_desc.md @@ -0,0 +1 @@ +Cuando el estado de una confirmación de Git cambia. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados](/rest/reference/repos#statuses)". diff --git a/translations/es-ES/data/reusables/webhooks/team_add_short_desc.md b/translations/es-ES/data/reusables/webhooks/team_add_short_desc.md new file mode 100644 index 0000000000000..96027ab03a2f9 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/team_add_short_desc.md @@ -0,0 +1 @@ +Cuando se [agrega un repositorio a un equipo](/rest/reference/teams#add-or-update-team-repository-permissions). diff --git a/translations/es-ES/data/reusables/webhooks/team_short_desc.md b/translations/es-ES/data/reusables/webhooks/team_short_desc.md new file mode 100644 index 0000000000000..824e798092e91 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/team_short_desc.md @@ -0,0 +1 @@ +La actividad relacionada con el equipo de una organización. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[equipos](/rest/reference/teams)". diff --git a/translations/es-ES/data/reusables/webhooks/watch_properties.md b/translations/es-ES/data/reusables/webhooks/watch_properties.md new file mode 100644 index 0000000000000..21b3643e64b7f --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/watch_properties.md @@ -0,0 +1,3 @@ +| Clave | Type | Descripción | +| -------- | ----------- | ---------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Acutalmente, solo puede ser `started`. | diff --git a/translations/es-ES/data/reusables/webhooks/watch_short_desc.md b/translations/es-ES/data/reusables/webhooks/watch_short_desc.md new file mode 100644 index 0000000000000..22f7f62cdbbb4 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/watch_short_desc.md @@ -0,0 +1 @@ +Cuando alguien marca un repositorio con una estrella. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[marcar con una estrella](/rest/reference/activity#starring)". diff --git a/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md new file mode 100644 index 0000000000000..88ed5a60225de --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md @@ -0,0 +1,4 @@ +Puedes utilizar las API de REST del webhook de una app, organización o repositorio para crear, actualizar, borrar y hacer ping a los webhooks. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}También puedes utilizar la API de REST para cambiar la configuración del webhook. Por ejemplo, puedes modificar la URL de la carga útil, el tipo de contenido, la verificación de SSL, y el secreto. {% endif %}Para obtener más información, consulta: +- [API de REST para los webhooks de los repositorios](/rest/reference/repos#webhooks) +- [API de REST para los Webhooks de las Organizaciones](/rest/reference/orgs#webhooks){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +- [API de REST para los Webhooks de las GitHub Apps](/rest/reference/apps#webhooks){% endif %} diff --git a/translations/es-ES/data/reusables/webhooks/webhooks_intro.md b/translations/es-ES/data/reusables/webhooks/webhooks_intro.md new file mode 100644 index 0000000000000..7459e7faa4102 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/webhooks_intro.md @@ -0,0 +1 @@ +Cuando configuras un webhook, puedes utilizar la IU o la API para elegir qué eventos te enviarán cargas útiles. El suscribirte únicamente a los eventos específicos que pretendes gestionar limita la cantidad de solicitudes HTTP a tu servidor. También puedes suscribirte a todos los eventos futuros y actuales. Predeterminadamente, los webhooks solo se suscriben al evento de carga. Puedes cambiar la lista de eventos a los que te suscribiste en cualquier momento. diff --git a/translations/es-ES/data/reusables/webhooks/webhooks_ssl.md b/translations/es-ES/data/reusables/webhooks/webhooks_ssl.md new file mode 100644 index 0000000000000..f0d4f1e0835b7 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/webhooks_ssl.md @@ -0,0 +1 @@ +Si tu "URL de carga útil" es un sitio seguro (HTTPS), tendrás la opción de configurar los ajustes de verificación de SSL. Si tu "URL de carga útil" no es segura (HTTP), GitHub no mostrará esta opción. Predeterminadamente, GitHub verifica el certificado SSL de tu sitio web cuando entrega cargas útiles de webhooks. La verificación de SSL ayuda a garantizar que las cargas útiles de los ganchos se entregan en tu terminal URL de forma segura. Tienes la opción de inhabilitar SSL, pero te recomendamos que mantengas seleccionado **Habilitar la verificación SSL**. diff --git a/translations/es-ES/data/reusables/webhooks/workflow_run_desc.md b/translations/es-ES/data/reusables/webhooks/workflow_run_desc.md new file mode 100644 index 0000000000000..7a2f3ccf9d493 --- /dev/null +++ b/translations/es-ES/data/reusables/webhooks/workflow_run_desc.md @@ -0,0 +1,4 @@ + +Este evento ocurre cuando una ejecución de flujo de trabajo se solicita o se completa, y te permite ejecutar un flujo de trabajo con base en el resultado terminado de otro flujo de trabajo. Por ejemplo, si tu flujo de trabajo de `pull_request` genera artefactos de compilación, puedes crear un nuevo flujo de trabajo que utilice a `workflow_run` para analizar los resultados y agregar un comentario la solicitud de extracción original. + +El flujo de trabajo que inició el evento `workflow_run` puede acceder a los secretos y tokens escritos que se utilizan en el flujo de trabajo original. diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml new file mode 100644 index 0000000000000..8a8200d9d2c47 --- /dev/null +++ b/translations/es-ES/data/ui.yml @@ -0,0 +1,146 @@ +--- +header: + github_docs: GitHub Docs + contact: Contacto + notices: + ghae_silent_launch: GitHub AE está actualmente en un lanzamiento limitado. Por favor, contacta a nuestro equipo de ventas para conocer más sobre esto. + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' + localization_complete: Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos. + localization_in_progress: '¡Hola, explorador! Esta página está bajo desarrollo activo o todavía está en la etapa de traducción. Para obtener información más actualizada y precisa, visita nuestra documentación en inglés.' + early_access: '📣 Por favor, no compartas esta URL públicamente. Esta página tiene contenido sobre una característica de acceso temprano.' +search: + need_help: '¿Necesitas ayuda?' + placeholder: Busca temas, productos... +homepage: + explore_by_product: Explorar por producto + version_picker: Versión +toc: + getting_started: Empezar + popular_articles: Popular + guides: Guías + whats_new: Qué hay de nuevo +pages: + article_version: 'Versión del artículo:' + miniToc: En este artículo +errors: + oops: '¡Ups!' + something_went_wrong: Parece que algo salió mal. + we_track_errors: Realizamos el seguimiento de estos errores automáticamente, pero si el problema continúa, no dudes en contactarnos. + page_doesnt_exist: Al parecer, esta página no existe. +support: + still_need_help: '¿Aún necesitas ayuda?' + contact_support: Contactar con soporte técnico + ask_community: Pregúntale a la comunidad de GitHub +helpfulness: + able_to_find: '¿Te ayudó este documento?' + yes: true + no: false + yes_feedback: '¿Quieres saber sobre las características y actualizaciónes de los documentos nuevos? ¡Regístrate para recibir actualizaciones!' + email_placeholder: email@ejemplo.com + no_feedback: Estamos mejorando nuestros documentos constantemente. Nos encantaría saber cómo crees que podemos hacerlo aún mejor. + category_label: '¿Qué problema tuviste?' + category_default: Elige una opción + category_unclear: La información no estaba clara + category_confusing: El contenido era confuso + category_unhelpful: El artículo no respondió a mi pregunta + category_other: Otro + comment_label: Déjanos saber lo que podemos mejorar + optional: Opcional + required: Requerido + email_label: '¿Podemos contactarte si tenemos más preguntas?' + send: Enviar + feedback: '¡Gracias! Tu retroalimentación se ha emitido.' +contribution_cta: + title: '¡Ayúdanos a hacer geniales estos documentos!' + body: Todos los documentos de GitHub son de código abierto. ¿Notas algo que esté mal o que no sea claro? Emite una solicitud de cambios. + button: Haz una contribución + or: O, + to_guidelines: aprende cómo contribuir. +enterprise_releases_list: + title: Lanzamientos de Enterprise Server + currently_supported: Actualmente compatibles + currently_supported_message: Consulta la sección de GitHub Enterprise para obtener más información sobre el último lanzamiento. + deprecated: Obsoletizado + deprecated_message: 'Estos documentos siguen estando disponibles, pero ya no se mantienen:' + deprecated_developer: Obsoletizado en developer.github.com + deprecated_developer_message: 'Estos documentos siguen estando disponibles en el sitio de desarrollador tradicional pero ya no se mantienen:' +products: + graphql: + reference: + fields: Campos + arguments: Argumentos + name: Nombre + type: Type + description: Descripción + input_fields: Campos de entrada + return_fields: Campos de retorno + implemented_by: Implementado por + values: Valores + possible_types: Tipos posibles + preview_notice: Aviso de previsualización + deprecation_notice: Aviso de depreciación + rest: + reference: + parameters: Parámetros + response: Respuesta + code_sample: Ejemplo de código + code_samples: Ejemplos de código + preview_notice: Aviso de previsualización + preview_notices: Avisos de previsualización + see_preview_notice: Ver aviso de previsualización + see_preview_notices: Ver avisos de previsualización + preview_header_is_required: El encabezado es requerido +footer: + all_rights_reserved: All rights reserved + terms: Términos + privacy: Privacy + security: Seguridad + product: + heading: Producto + links: + features: Características + security: Seguridad + enterprise: Empresa + case_studies: Estudios de caso + pricing: Precios + resources: Recursos + platform: + heading: Plataforma + links: + developer_api: API de desarrollo + partners: Socios + atom: Atom + electron: Electron + github_desktop: GitHub Desktop + support: + heading: Asistencia + links: + help: Ayuda + community_forum: Foro de la comunidad + training: Capacitación + status: Estado + contact_github: Ponte en contacto con GitHub + company: + heading: Empresa + links: + about: Acerca de + blog: Blog + careers: Carreras + press: Prensa + shop: Tienda +product_landing: + quick_start: Inicio Rápido + reference_guides: Guías de referencia + overview: Resumen +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: más guías + guideTypes: + overview: Resumen + quick_start: Inicio Rápido + tutorial: Tutorial + how_to: How-to guide + reference: Referencia diff --git a/translations/es-ES/data/variables/action_code_examples.yml b/translations/es-ES/data/variables/action_code_examples.yml new file mode 100644 index 0000000000000..90a7b96cf999f --- /dev/null +++ b/translations/es-ES/data/variables/action_code_examples.yml @@ -0,0 +1,335 @@ +--- +- + title: Servicios de ejemplo + description: Flujos de trabajo de ejemplo que utilizan contenedores de servicio + languages: JavaScript + href: actions/example-services + tags: + - contenedores de servicio +- + title: Configurar las etiquetas de GitHub de forma declaratoria + description: Acción de GitHub para configurar las etiquetas de forma declaratoria a través de los repositorios + languages: JavaScript + href: lannonbr/issue-label-manager-action + tags: + - propuestas + - etiquetas +- + title: Sincronizar las etiquetas de GitHub de forma declaratoria + description: Acción de GitHub para sincronizar las etiquetas de GitHub en la forma declaratoria + languages: 'Go, Dockerfile' + href: micnncim/action-label-syncer + tags: + - propuestas + - etiquetas +- + title: Agregar lanzamientos a GitHub + description: Publicar los lanzamientos de GitHub en una acción + languages: 'Dockerfile, Shell' + href: elgohr/Github-Release-Action + tags: + - releases + - publicar +- + title: Publicar una imagen de docker en Dockerhub + description: Una acción de GitHub que se utiliza para crear y publicar imágenes de Docker + languages: 'Dockerfile, Shell' + href: elgohr/Publish-Docker-Github-Action + tags: + - docker + - publicar + - build +- + title: Crear una propuesta utilizando el contenido de un archivo + description: Una acción de GitHub para crear una propuesta utilizando el contenido de un archivo + languages: 'JavaScript, Python' + href: peter-evans/create-issue-from-file + tags: + - propuestas +- + title: Publicar Lanzamientos de GitHub con Activos + description: Acción de GitHub para crear Lanzamientos de GitHub + languages: 'TypeScript, Shell, JavaScript' + href: softprops/action-gh-release + tags: + - releases + - publicar +- + title: GitHub Project Automation+ + description: Automatizar tarjetas de proyectos de GitHub con cualquier evento de webhook + languages: JavaScript + href: alex-page/github-project-automation-plus + tags: + - proyectos + - automatización + - propuestas + - solicitudes de extracción +- + title: Ejecutar GitHub Actions localmente con una interface web + description: Ejecuta flujos de trabajo de GitHub Actions localmente (local) + languages: 'JavaScript, HTML, Dockerfile, CSS' + href: phishy/wflow + tags: + - local-development + - devops + - docker +- + title: Ejecuta tus GitHub Actions localmente + description: Ejecuta GitHub Actions localmente en la Terminal + languages: 'Go, Shell' + href: nektos/act + tags: + - local-development + - devops + - docker +- + title: Crea y publica una APK de depuración en Android + description: Crea y lanza la APK de depuración desde tu proyecto de Android + languages: 'Shell, Dockerfile' + href: ShaunLWM/action-release-debugapk + tags: + - android + - build +- + title: Genera números de compilación secuenciales para GitHub Actions + description: Acción de GitHub para generar números de compilación secuenciales. + languages: JavaScript + href: einaregilsson/build-number + tags: + - build + - automatización +- + title: Acciones de GitHub para subir de vuelta a un repositorio + description: Subir cambios de Git a un repositorio de GitHub sin dificultades de autenticación + languages: 'JavaScript, Shell' + href: ad-m/github-push-action + tags: + - publicar +- + title: Generar notas de lanzamiento en tus eventos + description: Acción para autogenerar una nota de lanzamiento que se base en tus eventos + languages: 'Shell, Dockerfile' + href: Decathlon/release-notes-generator-action + tags: + - releases + - publicar +- + title: Crear una página de wiki de GitHub en el archivo de markdown proporcionado + description: Crear una página de wiki de GitHub en el archivo de markdown proporcionado + languages: 'Shell, Dockerfile' + href: Decathlon/wiki-page-creator-action + tags: + - wiki + - publicar +- + title: Etiqueta tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados) + description: Acción de Github para etiquetar tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados) + languages: 'TypeScript, Dockerfile, JavaScript' + href: Decathlon/pull-request-labeler-action + tags: + - proyectos + - propuestas + - etiquetas +- + title: Agregar una etiqueta a tus solicitudes de cambios en nombre del equipo autor + description: Acción de GitHub para etiquetar tus solicitudes de cambios con base en el nombre del autor + languages: 'TypeScript, JavaScript' + href: JulienKode/team-labeler-action + tags: + - solicitud de cambios + - etiquetas +- + title: Obtén una lista de cambios a los archivos con una PR/Subida + description: Esta acción obtendrá y te proporcionará las salidas de los archivos que hayan cambiado en tu repositorio + languages: 'TypeScript, Shell, JavaScript' + href: trilom/file-changes-action + tags: + - workflow + - repositorio +- + title: Acciones privadas en cualquier flujo de trabajo + description: Permite que se reutilicen las GitHub Actions privadas fácilmente + languages: 'TypeScript, JavaScript, Shell' + href: InVisionApp/private-action-loader + tags: + - workflow + - tools +- + title: Etiqueta tus propuestas utilizando sus contenidos + description: Una GitHub Action para etiquetar automáticamente las propuestas con etiquetas y asignados + languages: 'JavaScript, TypeScript' + href: damccorm/tag-ur-it + tags: + - workflow + - tools + - etiquetas + - propuestas +- + title: Revertir un lanzamiento de GitHub + description: Una GitHub Action para revertir o borrar un lanzamiento + languages: 'JavaScript' + href: author/action-rollback + tags: + - workflow + - releases +- + title: Bloquear propuestas y solicitudes de cambios cerradas + description: Una GitHub Action que bloquea propuestas y solicitudes de cambios cerrads después de un periodo de inactividad + languages: 'JavaScript' + href: dessant/lock-threads + tags: + - propuestas + - solicitudes de extracción + - workflow +- + title: Obtiene un conteo de diferencias en confirmaciones entre dos ramas + description: Esta GitHub Action compara dos ramas y te proporciona el conteo de confirmaciones entre ellas + languages: 'JavaScript, Shell' + href: jessicalostinspace/commit-difference-action + tags: + - commit + - diff + - workflow +- + title: Genera notas de lanzamiento con base en las referencias de Git + description: GitHub Action para generar registros de cambios y notas de lanzamiento + languages: 'JavaScript, Shell' + href: metcalfc/changelog-generator + tags: + - cicd + - notas de lanzamiento + - workflow + - bitácora de Cambios +- + title: Requiere políticas en las confirmaciones y repositorios de GitHub + description: Requerimiento de políticas para tus redes de comunicación interna + languages: 'Go, Makefile, Dockerfile, Shell' + href: talos-systems/conform + tags: + - docker + - build-automation + - workflow +- + title: Auto Etiquetado Basado en Propuestas + description: Etiqueta automáticamente una propuesta con base en su descripción + languages: 'TypeScript, JavaScript, Dockerfile' + href: Renato66/auto-label + tags: + - etiquetas + - workflow + - automatización +- + title: Actualiza las GitHub Actions configuradas a sus últimas versiones + description: Herramienta de CLI para verificar si todas tus acciones están actualizadas o no + languages: 'C#, Inno Setup, PowerSHell, Shell' + href: fabasoad/ghacu + tags: + - versions + - cli + - workflow +- + title: Crear Rama de Propuesta + description: GitHub Action que automatiza la creación de ramas de propuestas + languages: 'JavaScript, Shell' + href: robvanderleek/create-issue-branch + tags: + - probot + - propuestas + - etiquetas +- + title: Elimina artefactos antiguos + description: Personaliza la limpieza de artefactos + languages: 'JavaScript, Shell' + href: c-hive/gha-remove-artifacts + tags: + - artefactos + - workflow +- + title: Sincroniza los archivos/binarios definidos a un Wiki o a repositorios externos + description: GitHub Action para sincronizar automáticamente los cambios a los repositorios externos, como el wiki, por ejemplo + languages: 'Shell, Dockerfile' + href: kai-tub/external-repo-sync-action + tags: + - wiki + - sync + - workflow +- + title: Crea/Actualiza/Borra una página de Wiki de GitHub con base en cualquier archivo + description: Actualiza tu wiki de GitHub utilizando rsync, lo cual permite la exclusión de archivops y directorios y el borrado real de los archivos + languages: 'Shell, Dockerfile' + href: Andrew-Chen-Wang/github-wiki-action + tags: + - wiki + - docker + - workflow +- + title: GitHub Actions de Prow + description: Automatización del requerimiento de políticas, chat-ops y fusión automática de PR + languages: 'TypeScript, JavaScript' + href: jpmcb/prow-github-actions + tags: + - chat-ops + - prow + - workflow +- + title: Verifica el estado de GitHub en tu flujo de trabajo + description: Verifica el estado de GitHub en tu flujo de trabajo + languages: 'TypeScript, JavaScript' + href: crazy-max/ghaction-github-status + tags: + - status + - supervisar + - workflow +- + title: Administra etiquetas en GitHub como código + description: GitHub Action para administrar etiquetas (create/rename/update/delete) + languages: 'TypeScript, JavaScript' + href: crazy-max/ghaction-github-labeler + tags: + - etiquetas + - workflow + - automatización +- + title: Distribuir los fondos en los proyectos gratuitos y de código abierto + description: Distribución contínua de los fondos para los contribuyentes y dependencias de los proyectos + languages: 'Python, Dockerfile, Shell, Ruby' + href: protontypes/libreselery + tags: + - sponsors + - financiamiento + - payment +- + title: Reglas de Herald para GitHub + description: Agregar revisores, suscriptores, etiquetas y asignados a tu PR + languages: 'TypeScript, JavaScript' + href: gagoar/use-herald-action + tags: + - reviewers + - etiquetas + - asignatarios + - solicitud de cambios +- + title: Validador de Codeowner + description: Garantiza la exactitud de tu archivo de GitHub CODEOWNERS, apoya a los repositorios públicos y privados de GitHub y también a las instalaciones de GitHub Enterprise + languages: 'Go, Shell, Makefile, Dockerfile' + href: mszostok/codeowners-validator + tags: + - codeowners + - validar + - workflow +- + title: Acción Copybara + description: Mueve y transfora el código entre los repositorios (ideal para mantener varios repositorios fuera de un mono-repositorio) + languages: 'TypeScript, JavaScript, Shell' + href: olivr/copybara-action + tags: + - monorepo + - copybara + - workflow +- + title: Despliega archivos estáticos a GitHub Pages + description: GitHub Action para publcar un sitio web en GitHub Pages automáticamente + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publicar diff --git a/translations/es-ES/data/variables/command_line.yml b/translations/es-ES/data/variables/command_line.yml new file mode 100644 index 0000000000000..5d1f568716df9 --- /dev/null +++ b/translations/es-ES/data/variables/command_line.yml @@ -0,0 +1,10 @@ +--- +#Use this variable wherever backticks are necessary +backticks: >- + {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} +#Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) +codeblock: >- + {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}hostname{% endif %} +#GitHub URL example +git_url_example: >- + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}github.example.com{% endif %} diff --git a/translations/es-ES/data/variables/contact.yml b/translations/es-ES/data/variables/contact.yml new file mode 100644 index 0000000000000..c93b9272c1aae --- /dev/null +++ b/translations/es-ES/data/variables/contact.yml @@ -0,0 +1,33 @@ +--- +contact_ent_support: 'GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) o [GitHub Premium Support](https://premium.githubsupport.com)' +contact_support: >- + {% if currentVersion == "free-pro-team@latest" %}[GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://premium.githubsupport.com){% else %}tu administrador de sitio{% endif %} +report_abuse: >- + {% if currentVersion == "free-pro-team@latest" %}[Reportar abuso](https://github.com/contact/report-abuse){% endif %} +report_content: >- + {% if currentVersion == "free-pro-team@latest" %}[Reportar contenido](https://github.com/contact/report-content){% endif %} +contact_dmca: >- + {% if currentVersion == "free-pro-team@latest" %}[Formato de reclamaciones de derechos de autor](https://github.com/contact/dmca){% endif %} +contact_privacy: >- + {% if currentVersion == "free-pro-team@latest" %}[Formato de contacto de privacidad](https://github.com/contact/privacy){% endif %} +contact_enterprise_sales: "[Equipo de ventas de GitHub](https://enterprise.github.com/contact)" +contact_feedback_actions: '[Formulario para retroalimentación de GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' +#The team that provides Standard Support +enterprise_support: 'Soporte para GitHub Enterprise' +#The larger team that includes Enterprise Support and Premium Support +github_support: 'Soporte de GitHub' +#The team that provides Premium Support +premium_support: 'Soporte prémium de GitHub' +#Enterprise Support portal +enterprise_portal: 'Portal de Soporte de GitHub Enterprise' +contact_enterprise_portal: '[Portal de Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us)' +#Azure support (GitHub AE) portal +ae_azure_portal: 'Portal de Soporte de Azure' +contact_ae_portal: '[Portal de Soporte de Azure](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)' +#GitHub Support portal (for dotcom) +support_portal: 'Portal de soporte de GitHub' +contact_support_portal: '[GitHub Support portal](https://support.github.com/contact)' +#The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) +community_support: 'Soporte de la Comunidad de GitHub' +#The GitHub Community forum +community_support_forum: '[Foro de la comunidad de GitHub](https://github.community/)' diff --git a/translations/es-ES/data/variables/desktop.yml b/translations/es-ES/data/variables/desktop.yml new file mode 100644 index 0000000000000..2480a54e7df47 --- /dev/null +++ b/translations/es-ES/data/variables/desktop.yml @@ -0,0 +1,4 @@ +--- +#Supported platforms +mac-osx-versions: macOS 10.10 o posterior +windows-versions: Windows 7 64-bit o posterior diff --git a/translations/es-ES/data/variables/discussions_community_examples.yml b/translations/es-ES/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000000..108eeeb915825 --- /dev/null +++ b/translations/es-ES/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: El marco de trabajo de React +- + repo: gatsbyjs/gatsby + description: Crear apps y sitios web modernos e increíblemente rápidos con React +- + repo: nodejs/node + description: Tiempo de ejecución de JavaScript para Node.js ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: Un marco de trabajo de CSS de primera utilidad para el desarrollo rápido de IU. +- + repo: laravel/framework + description: Laravel es un marco de trabajo de aplicaciones web con sintaxis expresiva y elegante. +- + repo: prisma/prisma + description: El acceso moderno a las bases de datos (alternativa a ORM) para Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'El repositorio oficial para el diseño del lenguaje de programación C#' +- + repo: home-assistant/frontend + description: '🍭 Frontend para Home Assistant' +- + repo: jspsych/jsPsych + description: Una biblioteca de JavaScript para crear y ejecutar experimentos conductuales en un buscador web +- + repo: adonisjs/core + description: '🚀 El marco de trabajo de Node.js Framework altamente enfocado en la ergonomía, estabilidad y confianza del desarrollador' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 Ganchos de React para la validación de formas (Web + React Native)' diff --git a/translations/es-ES/data/variables/enterprise.yml b/translations/es-ES/data/variables/enterprise.yml new file mode 100644 index 0000000000000..b4884d8468ad0 --- /dev/null +++ b/translations/es-ES/data/variables/enterprise.yml @@ -0,0 +1,2 @@ +--- +management_console: 'Management Console' diff --git a/translations/es-ES/data/variables/explore.yml b/translations/es-ES/data/variables/explore.yml new file mode 100644 index 0000000000000..ba64c1e164887 --- /dev/null +++ b/translations/es-ES/data/variables/explore.yml @@ -0,0 +1,7 @@ +--- +explore_github: >- + {% if currentVersion == "free-pro-team@latest" %}[Explorar GitHub](https://github.com/explore){% else %}Explorar GitHub (`https://[hostname]/explore`){% endif %} +your_stars_page: >- + {% if currentVersion == "free-pro-team@latest" %}[página de favoritos](https://github.com/stars){% else %}página de favoritos (`https://[hostname]/stars`){% endif %} +trending_page: >- + {% if currentVersion == "free-pro-team@latest" %}[Página de tendencias](https://github.com/trending){% else %}Página de tendencias (`https://[hostname]/trending`){% endif %} diff --git a/translations/es-ES/data/variables/gists.yml b/translations/es-ES/data/variables/gists.yml new file mode 100644 index 0000000000000..12c745fd3ceb3 --- /dev/null +++ b/translations/es-ES/data/variables/gists.yml @@ -0,0 +1,7 @@ +--- +gist_homepage: >- + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} +gist_search_url: >- + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} +discover_url: >- + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/es-ES/data/variables/large_files.yml b/translations/es-ES/data/variables/large_files.yml new file mode 100644 index 0000000000000..b66af68568bf1 --- /dev/null +++ b/translations/es-ES/data/variables/large_files.yml @@ -0,0 +1,15 @@ +--- +product_name_long: 'Almacenamiento de archivos de gran tamaño Git' +product_name_short: 'Git LFS' +warning_size: '50 MB' +max_github_size: '100 MB' +max_github_browser_size: '25 MB' +initial_bandwidth_quota: '1 GB' +initial_storage_quota: '1 GB' +max_lfs_size: '2 GB' +max_file_size: '2 GB' +command_name: lfs +version_name: https://git-lfs.github.com/spec/v1 +pack_monthly_price: '$5 por mes' +pack_monthly_bandwidth: '50 GB' +pack_monthly_storage: '50 GB' diff --git a/translations/es-ES/data/variables/migrations.yml b/translations/es-ES/data/variables/migrations.yml new file mode 100644 index 0000000000000..fd3edd8f1d37d --- /dev/null +++ b/translations/es-ES/data/variables/migrations.yml @@ -0,0 +1,7 @@ +--- +user_migrations_intro: >- + Puedes utilizar esta API para revisar, respaldar, o migrar tus datos de usuario que se almacenan en {% data variables.product.product_name %},com. +organization_migrations_intro: >- + La API de migraciones de organización te permite migrar un repositorio de GitHub a {% data variables.product.prodname_ghe_server %}. +source_imports_intro: >- + La API de Importaciones de Código Fuente te permite comenzar una importación desde un repositorio de origen en Git, Subversion, Mercurial o Team Foundation Server. Esta es la misma funcionalidad que tiene el importador de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Importar un repositorio con el importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)". diff --git a/translations/es-ES/data/variables/notifications.yml b/translations/es-ES/data/variables/notifications.yml new file mode 100644 index 0000000000000..15885a5b2105a --- /dev/null +++ b/translations/es-ES/data/variables/notifications.yml @@ -0,0 +1,5 @@ +--- +no_reply_address: >- + {% if currentVersion == "free-pro-team@latest" %}`noreply@github.com`{% else %}la dirección de correo electrónico de tipo no-reply que configuró tu administrador de sitio{% endif %} +cc_address: >- + {% if currentVersion == "free-pro-team@latest" %}`@noreply.github.com`{% else %}basado en la dirección de correo electrónico de tipo no-reply que configuró tu administrador de sitio{% endif %} diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml new file mode 100644 index 0000000000000..47951b55309e0 --- /dev/null +++ b/translations/es-ES/data/variables/product.yml @@ -0,0 +1,167 @@ +--- +#Contains versioned and unversioned variables for all of our product names +## WARNING: Versioned variables don't work as expected in articles under "content/enterprise/admin/". Use unversioned variables instead. +#Company +company_short: 'GitHub' +#GitHub's flagship products +## Until we have versioning to support GitHub Enterprise Cloud content, avoid using this variable if the output should specifically be GitHub Enterprise Cloud or GitHub Enterprise Server +product_name: >- + {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% else %}GitHub{% endif %} +## Use this variable when the output should always be GitHub, regardless of the product the user is using +prodname_dotcom: 'GitHub' +## Use this variable when the output should always be GitHub Enterprise, regardless of the product the user is using +prodname_enterprise: 'GitHub Enterprise' +## Use this variable only when the output should specifically be GitHub.com, to distinguish from GitHub the company or other GitHub products (e.g. connecting GHE to GitHub.com) +prodname_dotcom_the_website: 'GitHub.com' +## Use these variables when the output should reflect one of our two specific GitHub Enterprise offerings +prodname_ghe_server: 'GitHub Enterprise Server' +prodname_ghe_cloud: 'Nube de GitHub Enterprise' +prodname_ghe_managed: 'GitHub AE' +prodname_ghe_one: 'GitHub One' +## Use these variables when referring specifically to a location within a product +product_location: >- + {% if enterpriseServerVersions contains currentVersion %}tu instancia de GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}tu empresa{% else %}GitHub{% endif %} +#Used ONLY when you need to refer to a GHES instance in an article that is versioned for non-GHES versions. +#Do not use in other situations! +product_location_enterprise: 'tu instancia de servidor de GitHub Enterprise' +prodname_free_user: 'GitHub Free' +prodname_pro: 'GitHub Pro' +prodname_team: 'GitHub Team' +prodname_free_team: 'GitHub Free' +prodname_enterprise_backup_utilities: 'Utilidades de respaldo del servidor de GitHub Enterprise' +#GitHub Connect (enterprise accounts, other unified features) +## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence. +prodname_github_connect: 'GitHub Connect' +prodname_unified_contributions: 'unified contributions' +prodname_unified_search: 'unified search' +#GitHub Education +prodname_education: 'GitHub Education' +prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'la [Comunidad Educativa de GitHub](https://education.github.community)' +prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'Programa del Campus de GitHub' +prodname_student_pack: 'Paquete de desarrollo para estudiantes de GitHub' +#GitHub CLI +prodname_cli: 'CLI de GitHub' +#GitHub Desktop +prodname_desktop: 'GitHub Desktop' +desktop_link: 'https://desktop.github.com/' +#GitHub for Mobile +prodname_mobile: 'GitHub para móviles' +prodname_ios: 'GitHub para iOS' +prodname_android: 'GitHub para Android' +#GitHub Pages +prodname_pages: 'GitHub Pages' +#CodeQL +prodname_codeql: 'CodeQL' +prodname_ql: 'QL' +#Apps, GitHub Marketplace, and integrations +prodname_marketplace: 'GitHub Marketplace' +prodname_github_app: 'GitHub App' +prodname_github_apps: 'GitHub Apps' +prodname_oauth_app: 'OAuth App' +#API and developer docs +prodname_enterprise_api: 'las API de {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %}' +prodname_support_forum_with_url: '[Foro de desarrollo y soporte de la API de GitHub](https://github.community/c/github-api-development-and-support/37)' +prodname_unfurls: 'Adjuntos de Contenido' +#Azure AD +ae_azure_ad_app_link: 'la [Aplicación de GitHub AE](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterpriseserver)' +#GitHub Actions +## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more. +prodname_actions: 'GitHub Actions' +#GitHub Debug +prodname_debug: 'Depuración de GitHub' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' +#GitHub Packages +prodname_registry: 'Registro del paquete de GitHub' +prodname_github_container_registry: 'Registro de Contenedores de GitHub' +prodname_container_registry: 'registro de contenedores' +#GitHub Insights +prodname_insights: 'GitHub Insights' +#GitHub Sponsors +prodname_sponsors: 'Patrocinadores de GitHub' +prodname_matching_fund: 'GitHub Sponsors Matching Fund' +#GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' +prodname_advanced_security: 'Advanced Security' +#Codespaces +prodname_codespaces: 'Codespaces' +prodname_vs_codespaces: 'Codespaces de Visual Studio' +prodname_github_codespaces: 'Acerca de GitHub Codespaces' +#GitHub resources: blog, jobs, Learning Lab +prodname_gcf: 'Soporte de la Comunidad de GitHub' +prodname_blog: 'el blog de GitHub' +prodname_jobs: 'GitHub Jobs' +prodname_learning: 'Laboratorio de aprendizaje de GitHub' +prodname_learning_link: 'https://lab.github.com/' +prodname_roadmap: 'Itinerario público de GitHub' +prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap' +#GitHub support +premium_support_plan: 'Plan prémium' +premium_plus_support_plan: 'Premium Plus Plan/GitHub Engineering Direct' +microsoft_premium_plus_support_plan: 'GitHub Engineering Direct' +support_ticket_priority_urgent: 'Urgent' +support_ticket_priority_high: 'High' +support_ticket_priority_normal: 'Normal' +support_ticket_priority_low: 'Low' +#Security features / code scanning platform / Security Lab +prodname_security: 'GitHub Security Lab' +prodname_security_link: 'https://securitylab.github.com/' +prodname_security_advisories: 'GitHub Security Advisories' +#Security features and code scanning platform +prodname_secret_scanning: 'escaneo de secretos' +prodname_secret_scanning_caps: 'Escaneo de secretos' +prodname_code_scanning: 'escaneo de código' +prodname_code_scanning_capc: 'Escaneo de código' +prodname_codeql_runner: 'Ejecutor de CodeQL' +prodname_advisory_database: 'GitHub Advisory Database' +prodname_codeql_workflow: 'Flujo de trabajo de análisis de CodeQL' +#Visual Studio +prodname_vs: 'Visual Studio' +prodname_vscode: 'Visual Studio Code' +prodname_vss_ghe: 'Suscripción de Visual Studio con GitHub Enterprise' +prodname_vss_admin_portal_with_url: 'el [portal de admnistrador para las suscripciones de Visual Studio](https://visualstudio.microsoft.com/subscriptions-administration/)' +#GitHub Dependabot +prodname_dependabot: 'Dependabot' +prodname_dependabot_alerts: 'Las alertas del dependabot' +prodname_dependabot_security_updates: 'Actualizaciones de seguridad del dependabot' +prodname_dependabot_version_updates: 'Actualizaciones de versión del dependabot' +#GitHub Archive Program +prodname_archive: 'Programa de Archivo de GitHub' +prodname_arctic_vault: 'Bóveda de Código del Ártico' +#Links +product_url: >- + {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} +pricing_url: 'https://github.com/pricing' +signin_link: >- + {% if currentVersion == "free-pro-team@latest" %}[Iniciar sesión](https://github.com/login){% else %}Iniciar sesión (`https://[hostname]/login`){% endif %} +signout_link: >- + {% if currentVersion == "free-pro-team@latest" %}[Salir de sesión](https://github.com/logout){% else %}Salir de sesión (`https://[hostname]/logout`){% endif %} +raw_github_com: >- + {% if currentVersion == "free-pro-team@latest" %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %} +#GitHub Enterprise Server past versions +current-340-version: '11.10.354' +#Developer site product variables +#Use this inside command-line and other code blocks +doc_url_pre: >- + {% if currentVersion == "free-pro-team@latest" %}https://developer.github.com{% else %}https://developer.github.com/enterprise/{{currentVersion}}{% endif %} +#Use this inside command-line code blocks +api_url_pre: >- + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://[hostname]/api/v3{% endif %} +#Use this inside command-line code blocks +#Enterprise OAuth paths that don't include "/graphql" or "/api/v3" +oauth_host_code: >- + {% if currentVersion == "free-pro-team@latest" %}https://github.com{% else %}http(s)://[hostname]{% endif %} +device_authorization_url: >- + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`https://github.com/login/device`](https://github.com/login/device){% else %}`http(s)://[hostname]/login/device`{% endif %} +#Use this all other code blocks +api_url_code: >- + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://[hostname]/api/v3{% endif %} +#Use this inside command-line code blocks +graphql_url_pre: >- + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://[hostname]/api/graphql{% endif %} +#Use this all other code blocks +graphql_url_code: >- + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://[hostname]/api/graphql{% endif %} diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml new file mode 100644 index 0000000000000..71234017daf78 --- /dev/null +++ b/translations/es-ES/data/variables/release_candidate.yml @@ -0,0 +1,2 @@ +--- +version: enterprise-server@3.0 diff --git a/translations/es-ES/data/variables/search.yml b/translations/es-ES/data/variables/search.yml new file mode 100644 index 0000000000000..77e62b719933c --- /dev/null +++ b/translations/es-ES/data/variables/search.yml @@ -0,0 +1,5 @@ +--- +advanced_url: >- + {% if currentVersion == "free-pro-team@latest" %}[búsqueda avanzada](https://github.com/search/advanced) página{% else %}página de búsqueda avanzada (`https://[hostname]/search/advanced`){% endif %} +search_page_url: >- + {% if currentVersion == "free-pro-team@latest" %}[search](https://github.com/search) página{% else %}página de búsqueda (`https://[hostname]/search`){% endif %} diff --git a/translations/ja-JP/content/actions/creating-actions/about-actions.md b/translations/ja-JP/content/actions/creating-actions/about-actions.md index 34f0e751bf00f..e63b6a950dbd8 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-actions.md @@ -10,18 +10,19 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### アクションについて {% data variables.product.prodname_dotcom %}の API やパブリックに利用可能なサードパーティAPIとのインテグレーションなど、好きな方法でリポジトリを操作するカスタムコードを書いて、アクションを作成することができます。 たとえば、アクションでnpmモジュールを公開する、緊急のIssueが発生したときにSMSアラートを送信する、本番対応のコードをデプロイすることなどが可能です。 {% if currentVersion == "free-pro-team@latest" %} -独自のアクションの作成、または -{% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 ビルドしたアクションをシェアするには、リポジトリをパブリックにする必要があります。 +ワークフローで利用する独自のアクションを作成したり、 +構築したアクションを{% data variables.product.prodname_dotcom %} コミュニティと共有したりできます。 ビルドしたアクションをシェアするには、リポジトリをパブリックにする必要があります。 {% endif %} アクションはマシン上で直接実行することも、Dockerコンテナで実行することもできます。 アクションの入力、出力、環境変数を定義できます。 @@ -30,27 +31,27 @@ versions: DockerコンテナのアクションとJavaScriptのアクションをビルドできます。 アクションには、アクションの入力、出力、およびメインのエントリポイントを定義するメタデータファイルが必要です。 このメタデータのファイル名は`action.yml`もしくは`action.yaml`でなければなりません。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions)」を参照してください。 -| 種類 | オペレーティングシステム | -| ---------- | --------------------- | -| Dockerコンテナ | Linux | -| JavaScript | Linux, macOS, Windows | -| 複合実行ステップ | Linux, macOS, Windows | +| 種類 | オペレーティングシステム | +| ---------- | ------------------- | +| Dockerコンテナ | Linux | +| JavaScript | Linux、MacOS、Windows | +| 複合実行ステップ | Linux、MacOS、Windows | -#### Docker コンテナーアクション +#### Docker コンテナアクション Dockerコンテナは、{% data variables.product.prodname_actions %}コードで環境をパッケージ化します。 アクションの利用者がツールや依存関係を考慮しなくて済むため、作業単位の一貫性と信頼性が向上します。 -Dockerコンテナを使用すると、Osのバージョン、依存関係、ツール、コードを限定することができます。 特定の環境設定で実行しなければならないアクションの場合、オペレーティングシステムとツールを選択できるので、Dockerは理想的な選択肢です。 コンテナのビルドおよび取得のレイテンシにより、DockerコンテナのアクションはJavaScriptアクションより遅くなります。 +Dockerコンテナを使用すると、OSのバージョン、依存関係、ツール、コードを限定することができます。 特定の環境設定で実行しなければならないアクションの場合、オペレーティングシステムとツールを選択できるので、Dockerは理想的な選択肢です。 コンテナのビルドおよび取得のレイテンシにより、DockerコンテナのアクションはJavaScriptアクションより遅くなります。 Docker コンテナアクションは、Linux オペレーティングシステムのランナーでのみ実行できます。 {% data reusables.github-actions.self-hosted-runner-reqs-docker %} -#### アクション +#### JavaScriptアクション -JavaScriptアクションはランナーマシン上で直接実行でき、アクションのコードはそのコードを実行するのに使われた環境から分離できます。 JavaScriptのアクションを使うと、アクションコードが単純になり、実行も Dockerコンテナのアクションより速くなります。 +JavaScriptアクションはランナーマシン上で直接実行でき、アクションのコードはそのコードを実行するのに使われる環境から分離できます。 JavaScriptのアクションを使うと、アクションコードが単純になり、実行も Dockerコンテナのアクションより速くなります。 {% data reusables.github-actions.pure-javascript %} -Node.jsプロジェクトの開発では、{% data variables.product.prodname_actions %} Toolkitで提供するパッケージを使って、開発の速度を上げることができます。 詳しい情報については、[actions/toolkit](https://github.com/actions/toolkit) リポジトリ以下を参照してください。 +Node.jsプロジェクトの開発では、{% data variables.product.prodname_actions %} Toolkitで提供するパッケージを使って、開発の速度を上げることができます。 詳しい情報については、[actions/toolkit](https://github.com/actions/toolkit) リポジトリを参照してください。 #### 複合実行ステップアクション @@ -82,9 +83,9 @@ _複合実行ステップ_ アクションを使用すると、1 つのアクシ #### リリース管理の良い方法 -他のユーザが使用するアクションを開発している場合は、リリース管理を使用して、更新の配布方法を管理することをお勧めします。 既存のワークフローとの互換性を維持しつつ、アクションのメジャーバージョンに必要な重要な修正およびセキュリティパッチも含まれます。 変更が互換性に影響する場合は、新しいメジャーバージョンのリリースを検討する必要があります。 +他のユーザが使用するアクションを開発している場合は、リリース管理を使用して、更新の配布方法を管理することをお勧めします。 アクションのメジャーバージョンには、既存のワークフローとの互換性を維持しつつ、必要となる重要な修正およびセキュリティパッチも含まれることが期待できます。 変更が互換性に影響する場合は、新しいメジャーバージョンのリリースを検討する必要があります。 -このリリース管理アプローチでは、アクションが最新のコードを含む可能性が高く、結果として不安定になる可能性があるため、ユーザはアクションのデフォルトブランチを参照しないでください。 代わりに、ユーザにアクションの使用時にメジャーバージョンを指定するように勧めて、問題が発生した場合にのみ、特定のバージョンを指定するようにすることができます。 +このリリース管理アプローチでは、アクションが最新のコードを含む可能性が高く、結果として不安定になる可能性があるため、ユーザはアクションのデフォルトブランチを参照しないでください。 代わりに、ユーザにアクションの使用時にメジャーバージョンを指定するように勧めて、問題が発生した場合にのみ、さらに特定したバージョンを指定するようにすることができます。 特定のアクションのバージョンを使用するために、ユーザは {% data variables.product.prodname_actions %} ワークフローを設定して、タグ、コミットの SHA、またはリリースの名前が付けられたブランチをターゲットにすることができます。 @@ -132,7 +133,7 @@ steps: ### アクションのREADMEファイルを作成する -アクションをパブリックに共有する予定がある場合には、アクションの使用方法を伝えるため README ファイルを作成することをお勧めします。 `README.md` には、以下の情報を含めることができます: +アクションの使用方法を伝えるため、README ファイルを作成することをお勧めします。 `README.md` には、以下の情報を含めることができます: - アクションが実行する内容の説明 - 必須の入力引数と出力引数 @@ -157,7 +158,7 @@ steps: {% data variables.product.prodname_actions %}は： * 継続的インテグレーションや継続的デプロイメントを実行する自動化を提供します。 -* ランナーマシン上でもDockerコンテナ内でも直接実行できます。 +* ランナーマシン上で直接、あるいはDockerコンテナ内で実行できます。 * リポジトリのクローンへのアクセスを含めて、コードにアクセスするツール、コードフォーマッタ、コマンドラインツールをデプロイしたり公開したりできます。 * コードのデプロイやアプリケーションの提供が必要ありません。 * シークレットの生成と利用のためのシンプルなインターフェースを持っており、アクションを利用する人の認証情報を保存せずにサードパーティのサービスとアクションを連携できます。 diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md index edb6bf2bda58a..d4cbafbf51037 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,31 +5,36 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに -このガイドでは、パッケージ化された複合実行ステップ アクションを作成および使用するために必要な基本的なコンポーネントについて説明します。 アクションのパッケージ化に必要なコンポーネントのガイドに焦点を当てるため、アクションのコードの機能は最小限に留めます。 アクションは「ハローワールド」と「さよなら」を印刷するか、カスタム名を指定すると「こんにちは [who-to-greet]」と「さようなら」を出力します。 このアクションでは、乱数も `乱数` 出力変数にマップされ、 `goodbye.sh`という名前のスクリプトが実行されます。 +このガイドでは、パッケージ化された複合実行ステップ アクションを作成および使用するために必要な基本的なコンポーネントについて説明します。 アクションのパッケージ化に必要なコンポーネントのガイドに焦点を当てるため、アクションのコードの機能は最小限に留めます。 アクションは「Hello World」と「Goodbye」を出力するか、カスタムの名前を指定すると「Hello [who-to-greet]」と「Goodbye」を出力します。 このアクションは、乱数を `random-number`という出力変数にマップし、 `goodbye.sh`という名前のスクリプトを実行することもします。 -このプロジェクトを完了したら、独自の複合実行ステップ アクションをビルドし、ワークフローでテストする方法を理解する必要があります。 +このプロジェクトを完了すれば、独自の複合実行ステップ アクションをビルドし、ワークフローでテストする方法を理解できるでしょう。 ### 必要な環境 始める前に、{% data variables.product.product_name %} リポジトリを作成します。 -1. {% data variables.product.product_location %} に新しいパブリックリポジトリを作成します。 任意のリポジトリ名を選択するか、hello-world コンポジット実行ステップアクション 例 `次の方法を使用できます。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 詳しい情報については、「新しいリポジトリの作成」を参照してください。

      -

    • リポジトリをお手元のコンピューターにクローンします。 詳しい情報についてはリポジトリのクローンを参照してください。

      • -

    • ターミナルから、ディレクトリを新しいリポジトリに変更します。 -

        cd ハローワールドコンポジット実行ステップアクション
-`
      +1. {% data variables.product.product_location %} に新しいパブリックリポジトリを作成します。 任意のリポジトリ名を選択するか、以下の`hello-world-composite-run-steps-action`の例を利用できます。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 詳しい情報については、「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 + +1. リポジトリをお手元のコンピューターにクローンします。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。 + +1. ターミナルから、ディレクトリを新しいリポジトリに変更します。 + + ```shell + cd hello-world-composite-run-steps-action + ``` 2. `hello-world-composite-run-steps-action` リポジトリで、 `goodbye.sh`という名前の新しいファイルを作成し、次のコード例を追加します。 ```bash - エコー"さようなら" + echo "Goodbye" ``` 3. ターミナルから、`goodbye.sh` を実行可能にします。 @@ -38,19 +43,19 @@ versions: chmod +x goodbye.sh ``` -1. 端末から、 `goodbye.sh` ファイルをチェックインします。 +1. ターミナルから、 `goodbye.sh` ファイルをチェックインします。 ```shell - git を追加goodbye.sh - git コミット -m "さよならスクリプトを追加" - git プッシュ + git add goodbye.sh + git commit -m "Add goodbye script" + git push ``` ### アクションのメタデータファイルの作成 -1. `hello-world-composite-run-steps-action` リポジトリで、action.yml `という名前の新しいファイルを作成し、次のコード例を追加します。 この構文の詳細については、「実行` 」を参照してください。 +1. `hello-world-composite-run-steps-action` リポジトリで、`action.yml`という名前の新しいファイルを作成し、次のコード例を追加します。 この構文の詳細については、「[複合実行ステップの`runs` ](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-run-steps-actions)」を参照してください。 {% raw %} - **アクション.yml** + **action.yml** ```yaml name: 'Hello World' description: 'Greet someone' @@ -75,47 +80,35 @@ versions: shell: bash ``` {% endraw %} - This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. また、複合実行ステップアクションの実行方法をランナーに指示します。 - - 出力の管理の詳細については、「複合実行手順の出力 を[`する」参照してください。

      - -

      github.action_path`の使用方法の詳細については、「github コンテキスト](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-run-steps-actions)の + このファイルは`who-to-greet`入力を定義し、ランダムに生成された数値を`random-number`出力変数にマップし、`goodbye.sh`スクリプトを実行します。 また、複合実行ステップアクションの実行方法をランナーに指示します。 -`」を参照してください。

      • -

    • ターミナルから、action.yml` ファイルをチェックインします。 + 出力の管理の詳細については、「[複合実行ステップの`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-run-steps-actions)」を参照してください。 + `github.action_path`の使用方法の詳細については、「[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)」を参照してください。 +1. ターミナルから、`action.yml` ファイルをチェックインします。 ```shell git add action.yml git commit -m "Add action" git push ``` -

      • -1 ターミナルから、タグを追加します。 この例では、`v1` というタグを使用しています。 詳しい情報については、「[アクションについて](/actions/creating-actions/about-actions#using-release-management-for-actions)」を参照してください。 - - +1. ターミナルから、タグを追加します。 この例では、`v1` というタグを使用しています。 詳しい情報については、「[Actionsについて](/actions/creating-actions/about-actions#using-release-management-for-actions)」を参照してください。 ```shell git tag -a -m "Description of this release" v1 git push --follow-tags ``` - +### ワークフローでアクションをテストする +次のワークフローのコードでは、「[Actionsのメタデータファイルの作成](/actions/creating-actions/creating-a-composite-run-steps-action#creating-an-action-metadata-file)」で作成したhello world Actionを使用しています。 -### ワークフローでアクションを試す - -次のワークフロー コードでは、「アクション メタデータ ファイルの作成」で行った完了した hello world アクション[使用](/actions/creating-actions/creating-a-composite-run-steps-action#creating-an-action-metadata-file)。 - -ワークフローコードを別のリポジトリの `.github/workflows/main.yml` ファイルにコピーしますが、`actions/hello-world-composite-run-steps-action@v1` は作成したリポジトリとタグに置き換えます。 `who-to-greet` 入力を自分の名前に置き換えることもできます。 +ワークフローコードを別のリポジトリの `.github/workflows/main.yml` ファイルにコピーしますが、`actions/hello-world-composite-run-steps-action@v1` は作成したリポジトリとタグに置き換えます。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% raw %} - -**.github/ワークフロー/メイン.yml** - - +**.github/workflows/main.yml** ```yaml on: [push] @@ -132,8 +125,6 @@ jobs: - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` - - {% endraw %} -リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 出力には、「こんにちはモナオクトキャット」、"Goodbye"スクリプトの結果、および乱数が含まれている必要があります。 +リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 出力には、「Hello Mona the Octocat」、"Goodbye"スクリプトの結果、および乱数が含まれているはずです。 diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md index 37554afa8f611..5f50de09d5f1d 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,10 +10,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -51,8 +52,7 @@ versions: # コードを実行するコンテナイメージ FROM alpine:3.10 -# アクションのリポジトリからコードファイルをファイルシステムパスへコピー -`/` of the container +# アクションのリポジトリからコードファイルをコンテナのファイルシステムパス `/`にコピー COPY entrypoint.sh /entrypoint.sh # dockerコンテナが起動する際に実行されるコードファイル (`entrypoint.sh`) @@ -64,7 +64,7 @@ ENTRYPOINT ["/entrypoint.sh"] 新しい `action.yml` ファイルを、上で作成した `hello-world-docker-action` ディレクトリの中に作成します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions)」を参照してください。 {% raw %} -**アクション.yml** +**action.yml** ```yaml # action.yml name: 'Hello World' @@ -154,7 +154,7 @@ with: who-to-greet: 'Mona the Octocat' ``` -### アクションの GitHub へのコミットとタグ、プッシュ +### アクションの{% data variables.product.product_name %}へのコミットとタグ、プッシュ ターミナルから、`action.yml`、`entrypoint.sh`、`Dockerfile`、および `README.md` ファイルをコミットします。 @@ -167,7 +167,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -### ワークフローでアクションを試す +### ワークフローでアクションをテストする これで、ワークフローでアクションをテストできるようになりました。 プライベートリポジトリにあるアクションは、同じリポジトリのワークフローでしか使用できません。 パブリックアクションは、どのリポジトリのワークフローでも使用できます。 @@ -175,10 +175,10 @@ git push --follow-tags #### パブリックアクションを使用する例 -次のワークフローコードでは、[`actions/hello-world-docker-container-action`](https://github.com/actions/hello-world-docker-action)というパブリックリポジトリにある完成した hello world アクションを使っています。 次のワークフローサンプルコードを `.github/workflows/main.yml` にコピーし、`actions/hello-world-docker-action` をあなたのリポジトリとアクション名に置き換えてください。 `who-to-greet` 入力を自分の名前に置き換えることもできます。 +次のワークフローコードでは、[`actions/hello-world-docker-container-action`](https://github.com/actions/hello-world-docker-action)というパブリックリポジトリにある完成した hello world アクションを使っています。 次のワークフローサンプルコードを `.github/workflows/main.yml` にコピーし、`actions/hello-world-docker-action` をあなたのリポジトリとアクション名に置き換えてください。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% raw %} -**.github/ワークフロー/メイン.yml** +**.github/workflows/main.yml** ```yaml on: [push] @@ -200,10 +200,10 @@ jobs: #### プライベートアクションを使用する例 -次のワークフローコードサンプルを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet` 入力を自分の名前に置き換えることもできます。 +次のワークフローコードサンプルを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% raw %} -**.github/ワークフロー/メイン.yml** +**.github/workflows/main.yml** ```yaml on: [push] @@ -227,7 +227,7 @@ jobs: ``` {% endraw %} -リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[**Jobs**] または視覚化グラフで、[**A job to say hello**] をクリックします。 {% endif %}"Hello Mona the Octocat"、または `who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/docker-action-workflow-run-updated.png) diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md index d6d02ce5c408c..79e6e352ae0ee 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,10 +10,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -54,7 +55,7 @@ versions: `hello-world-javascript-action`ディレクトリに、以下のサンプルコードで新しく`action.yml`というファイルを作成してください。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions)」を参照してください。 -**アクション.yml** +**action.yml** ```yaml name: 'Hello World' description: 'Greet someone and record the time' @@ -176,7 +177,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. +`node_modules` ディレクトリをチェックインすると、問題が発生する可能性があります。 別の方法として、[`@vercel/ncc`](https://github.com/vercel/ncc) というツールを使用して、コードとモジュールを配布に使用する 1 つのファイルにコンパイルできます。 1. ターミナルで次のコマンドを実行し、`vercel/ncc` をインストールします: `npm i -g @vercel/ncc` @@ -196,7 +197,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -### ワークフローでアクションを試す +### ワークフローでアクションをテストする これで、ワークフローでアクションをテストできるようになりました。 プライベートリポジトリにあるアクションは、同じリポジトリのワークフローでしか使用できません。 パブリックアクションは、どのリポジトリのワークフローでも使用できます。 @@ -204,10 +205,10 @@ git push --follow-tags #### パブリックアクションを使用する例 -次のワークフローコードでは、`actions/hello-world-javascript-action` というリポジトリにある完全な hello world アクションを使っています。 ワークフローコードを `.github/workflows/main.yml` ファイルにコピーし、`actions/hello-world-javascript-action` リポジトリをあなたが作成したリポジトリに置き換えます。 `who-to-greet` 入力を自分の名前に置き換えることもできます。 +次のワークフローコードでは、`actions/hello-world-javascript-action` というリポジトリにある完全な hello world アクションを使っています。 ワークフローコードを `.github/workflows/main.yml` ファイルにコピーし、`actions/hello-world-javascript-action` リポジトリをあなたが作成したリポジトリに置き換えます。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% raw %} -**.github/ワークフロー/メイン.yml** +**.github/workflows/main.yml** ```yaml オン hello_world_job: [push] @@ -229,10 +230,10 @@ git push --follow-tags #### プライベートアクションを使用する例 -ワークフローコードを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet` 入力を自分の名前に置き換えることもできます。 +ワークフローコードを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% raw %} -**.github/ワークフロー/メイン.yml** +**.github/workflows/main.yml** ```yaml on: [push] @@ -256,7 +257,7 @@ jobs: ``` {% endraw %} -リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[**Jobs**] または視覚化グラフで、[**A job to say hello**] をクリックします。 {% endif %}"Hello Mona the Octocat"、または `who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 4d588ae276fe8..d4ecebaaa2645 100644 --- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### Dockerfileの命令について @@ -19,7 +20,7 @@ versions: ### Dockerfileの命令とオーバーライド -Dockerの命令の中にはGitHub Actionと関わるものがあり、アクションのメタデータファイルはDockerの命令のいくつかをオーバーライドできます。 予期しない動作を避けるために、Dockerfileが{% data variables.product.prodname_actions %}とどのように関わるかについて馴染んでおいてください。 +Dockerの命令の中にはGitHub Actionsと関わるものがあり、アクションのメタデータファイルはDockerの命令のいくつかをオーバーライドできます。 予期しない動作を避けるために、Dockerfileが{% data variables.product.prodname_actions %}とどのように関わるかについて馴染んでおいてください。 #### USER @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] アクションのメタデータファイルに定義された`args`を、`ENTRYPOINT`中で_exec_形式を使うDockerコンテナに渡すには、`ENTRYPOINT`命令から呼ぶ`entrypoint.sh`というシェルスクリプトを作成することをおすすめします。 ##### *Dockerfile*の例 -``` +``` # コードを実行するコンテナイメージ FROM debian:9.5-slim -# アクションリポジトリからコンテナのファイルシステムパスの`/`にコードファイルをコピー +# アクションのリポジトリからコードをコンテナのファイルシステムパス `/` にコピー COPY entrypoint.sh /entrypoint.sh -# Dockerコンテナの起動時に`entrypoint.sh`を実行 +# Dockerコンテナの起動時に `entrypoint.sh` を実行 ENTRYPOINT ["/entrypoint.sh"] ``` @@ -79,13 +80,13 @@ ENTRYPOINT ["/entrypoint.sh"] #!/bin/sh # `$*`は`array`内で渡された`args`を個別に展開するか、 -# を空白で区切られた文字列中の`args`を分割します。 +# 空白で区切られた文字列中の`args`を分割します。 sh -c "echo $*" ``` コードは実行可能になっていなければなりません。 `entrypoint.sh`ファイルをワークフロー中で使う前に、`execute`権限が付けられていることを確認してください。 この権限は、ターミナルから以下のコマンドで変更できます。 ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` `ENTRYPOINT`シェルスクリプトが実行可能ではなかった場合、以下のようなエラーが返されます。 diff --git a/translations/ja-JP/content/actions/creating-actions/index.md b/translations/ja-JP/content/actions/creating-actions/index.md index 29dbbb1ada874..7def0708fbd8e 100644 --- a/translations/ja-JP/content/actions/creating-actions/index.md +++ b/translations/ja-JP/content/actions/creating-actions/index.md @@ -6,14 +6,14 @@ redirect_from: - /github/automating-your-workflow-with-github-actions/building-actions - /actions/automating-your-workflow-with-github-actions/building-actions - /actions/building-actions - - /記事/作成-githubアクション/ + - /articles/creating-a-github-action/ versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% link_in_list /about-actions %} {% link_in_list /creating-a-docker-container-action %} diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 39c5300031e40..0ff1beeb293e9 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,10 +11,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### {% data variables.product.prodname_actions %}のYAML構文について @@ -26,11 +27,11 @@ Docker及びJavaScriptアクションにはメタデータファイルが必要 **必須**アクションの名前。 {% data variables.product.prodname_dotcom %}は`name`を**Actions**タブに表示して、それぞれのジョブのアクションを見て区別しやすくします。 -### `作者` +### `author` **オプション** アクションの作者の名前。 -### `説明` +### `description` **必須** アクションの短い説明。 @@ -71,7 +72,7 @@ inputs: #### `inputs..default` -**オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されたなかった場合に使われます。 +**オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されなかった場合に使われます。 ### `outputs` @@ -95,7 +96,7 @@ outputs: **必須** 出力パラメーターの`文字列`での説明。 -### `outputs` for composite run steps actions +### 複合実行ステップアクションのための`outputs` **オプション** `outputs` `outputs.` および `outputs..description`（「[{% data variables.product.prodname_actions %} の `outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)」を参照）と同じパラメーターを使用しますが、`value` トークンも含まれます。 @@ -104,12 +105,12 @@ outputs: {% raw %} ```yaml outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - id: random-number-generator run: echo "::set-output name=random-id::$(echo $RANDOM)" shell: bash @@ -122,7 +123,7 @@ runs: コンテキストと式の構文の使用方法について詳しくは、「[{% data variables.product.prodname_actions %} のコンテキストと式の構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -### `runs` for JavaScript actions +### JavaScriptアクションのための`runs` **必須** アクションのコードと、コードを実行するのに使われるアプリケーションへのパスを設定します。 @@ -193,7 +194,7 @@ runs: post-if: 'runner.os == linux' ``` -### `runs` for composite run steps actions +### 複合実行ステップアクションのための`runs` **必須** 複合アクションへのパス、およびコードの実行に使用されるアプリケーションを設定します。 @@ -213,7 +214,7 @@ runs: ```yaml runs: using: "composite" - steps: + steps: - run: ${{ github.action_path }}/test/script.sh shell: bash ``` @@ -224,7 +225,7 @@ runs: ```yaml runs: using: "composite" - steps: + steps: - run: $GITHUB_ACTION_PATH/script.sh shell: bash ``` @@ -251,14 +252,14 @@ runs: **オプション** コマンドを実行する作業ディレクトリを指定します。 -### `runs` for Docker actions +### Dockerアクションのための`runs` **必須** Dockerアクションのために使われるイメージを設定します。 #### リポジトリでのDockerfileの利用例 ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -266,7 +267,7 @@ runs: #### パブリックなDockerレジストリコンテナを利用する例 ```yaml -runs: +runs: using: 'docker' image: 'docker://debian:stretch-slim' ``` @@ -369,7 +370,7 @@ branding: - + @@ -384,7 +385,7 @@ branding: - + @@ -463,10 +464,10 @@ branding: - + - + @@ -516,12 +517,12 @@ branding: - + - + @@ -539,7 +540,7 @@ branding: - + @@ -641,7 +642,7 @@ branding: - + @@ -666,7 +667,7 @@ branding: - + @@ -688,7 +689,7 @@ branding: - + @@ -718,14 +719,14 @@ branding: - + - + diff --git a/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 6d72889ed5176..3aac3119318de 100644 --- a/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- {% data variables.product.prodname_marketplace %}でアクションを公開するには、利用規約に同意していなければなりません。 diff --git a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md index 7a2819f55fa3e..4da8f5878f7cb 100644 --- a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 終了コードについて @@ -38,7 +39,7 @@ try { ### Docker コンテナアクションで失敗終了コードを設定する -Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトに設定できます。 例: +Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトで設定できます。 例: ``` if ; then diff --git a/translations/ja-JP/content/actions/guides/about-continuous-integration.md b/translations/ja-JP/content/actions/guides/about-continuous-integration.md index c3e3275f05994..43db3e7bd0609 100644 --- a/translations/ja-JP/content/actions/guides/about-continuous-integration.md +++ b/translations/ja-JP/content/actions/guides/about-continuous-integration.md @@ -10,32 +10,33 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 継続的インテグレーションについて -継続的インテグレーション (CI) とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの検出が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 開発者がコードの記述にばかり時間をとられ、エラーのデバッグやマージコンフリクトの解決にかける時間が少ないときに威力を発揮します。 +継続的インテグレーション (CI) とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの検出が早くなり、開発者がエラーの原因を見つけるためにデバッグしなければならないコードの量も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 コードの記述により多くの時間をかけられるようになり、エラーのデバッグやマージコンフリクトの解決にかける時間が減るので、これは開発者にとって素晴らしいやり方です。 -コードをリポジトリにコミットするとき、コミットによってエラーが発生しないように、コードのビルドとテストを継続的に行うことができます。 テストには、コードの文法チェッカー (スタイルフォーマットをチェックする)、セキュリティチェック、コード網羅率、機能テスト、その他のカスタムチェックを含めることができます。 +コードをリポジトリにコミットするとき、コミットによってエラーが発生しないように、コードのビルドとテストを継続的に行うことができます。 テストには、コードの文法チェッカー (スタイルフォーマットをチェックする)、セキュリティチェック、コードカバレッジ、機能テスト、その他のカスタムチェックを含めることができます。 コードをビルドしてテストするには、サーバーが必要です。 ローカルでアップデートのビルドとテストを行ってからコードをリポジトリにプッシュする方法もありますし、リポジトリ での新しいコードのコミットをチェックするCIサーバーを使用する方法もあります。 ### {% data variables.product.prodname_actions %} を使用する継続的インテグレーションについて -{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ内のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ内のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」および「[セルフホストランナーについて](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 -CI ワークフローは、{% data variables.product.product_name %} イベントが発生したとき（たとえば、新しいコードがリポジトリにプッシュされたとき）、設定されたスケジュールで、またはリポジトリディスパッチ Webhook を使用して外部イベントが発生したときに実行するように設定できます。 +CI ワークフローは、{% data variables.product.product_name %} イベントが発生したとき（たとえば、新しいコードがリポジトリにプッシュされたとき）や、設定されたスケジュール、またはリポジトリディスパッチ webhook を使用して外部イベントが発生したときに実行するように設定できます。 -{% data variables.product.product_name %} は CI テストを実行して、プルリクエストで各テストの結果を提供するため、ブランチの変更によってエラーが発生したかどうかを確認できます。 ワークフローのテストがすべて成功すると、プッシュした変更をチームメンバーがレビューできるように、またはマージできるようになります。 テストが失敗した場合は、いずれかの変更がその原因になっている可能性があります。 +{% data variables.product.product_name %} は CI テストを実行して、Pull Requestで各テストの結果を提供するため、ブランチの変更によってエラーが発生したかどうかを確認できます。 ワークフローのテストがすべて成功すると、プッシュした変更をチームメンバーがレビューできるように、またはマージできるようになります。 テストが失敗した場合は、いずれかの変更がその原因になっている可能性があります。 -リポジトリに CI を設定すると、{% data variables.product.product_name %} がリポジトリ内のコードを分析し、リポジトリ内の言語とフレームワークに基づいて CI ワークフローを推奨します。 たとえば、[Node.js](https://nodejs.org/en/) を使用する場合、{% data variables.product.product_name %} は、Node.js パッケージをインストールしてテストを実行するテンプレートファイルを提案します。 {% data variables.product.product_name %} によって提案された CI ワークフローテンプレートを使用しても、提案されたテンプレートをカスタマイズしてもかまいませんし、独自のカスタムワークフローファイルを作成して CI テストを実行することもできます。 +リポジトリに CI を設定する際には、{% data variables.product.product_name %} がリポジトリ内のコードを分析し、リポジトリ内の言語とフレームワークに基づいて CI ワークフローを推奨します。 たとえば、[Node.js](https://nodejs.org/en/) を使用する場合、{% data variables.product.product_name %} は、Node.js パッケージをインストールしてテストを実行するテンプレートファイルを提案します。 {% data variables.product.product_name %} によって提案された CI ワークフローテンプレートを使用しても、提案されたテンプレートをカスタマイズしてもかまいませんし、独自のカスタムワークフローファイルを作成して CI テストを実行することもできます。 ![提案された継続的インテグレーションテンプレートのスクリーンショット](/assets/images/help/repository/ci-with-actions-template-picker.png) -プロジェクトの CI ワークフローの設定だけでなく、{% data variables.product.prodname_actions %} を使用してソフトウェア開発のライフサイクル全体でワークフローを作成することもできます。 たとえば、アクションを使用してプロジェクトをデプロイ、パッケージ、またはリリースすることが可能です。 詳しい情報については、「[{% data variables.product.prodname_actions %} について](/articles/about-github-actions)」を参照してください。 +プロジェクトの CI ワークフローの設定だけでなく、{% data variables.product.prodname_actions %} を使用してソフトウェア開発のライフサイクル全体に渡るワークフローを作成することもできます。 たとえば、Actionを使用してプロジェクトをデプロイ、パッケージ、またはリリースすることが可能です。 詳しい情報については、「[{% data variables.product.prodname_actions %} について](/articles/about-github-actions)」を参照してください。 一般的な用語の定義については「[{% data variables.product.prodname_actions %} の中核的概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)」を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md index d78c6b8040acf..db817ec6bf94c 100644 --- a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### パッケージングのステップについて @@ -21,9 +22,9 @@ versions: ### 継続的インテグレーションワークフロー内でのパッケージング -継続的インテグレーションワークフローの終わりにパッケージを作成すれば、プルリクエストに対するコードレビューの間に役立つことがあります。 コードをビルドしてテストした後、パッケージングのステップで実行可能な、あるいはデプロイ可能な成果物を生成できます。 そしてワークフローはワークフローの一部として、この成果物をアップロードできます。 +継続的インテグレーションワークフローの終わりにパッケージを作成すれば、Pull Requestに対するコードレビューの間に役立つことがあります。 コードをビルドしてテストした後、パッケージングのステップで実行可能な、あるいはデプロイ可能な成果物を生成できます。 そしてワークフローはワークフローの一部として、この成果物をアップロードできます。 -そうすれば、プルリクエストをレビューする際には、ワークフローの実行を見て生成された成果物をダウンロードできるでしょう。 +そうすれば、Pull Requestをレビューする際には、ワークフローの実行を見て生成された成果物をダウンロードできるでしょう。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png) @@ -31,7 +32,7 @@ versions: ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png) {% endif %} -こうすれば、プルリクエスト中のコードを自分のマシン上で実行できるので、プルリクエストのデバッグやテストに役立ちます。 +こうすれば、Pull Request中のコードを自分のマシン上で実行できるので、Pull Requestのデバッグやテストに役立ちます。 ### パッケージを公開するためのワークフロー @@ -42,7 +43,8 @@ versions: デフォルトブランチへのプッシュごとに、パッケージを {% data variables.product.prodname_registry %} に公開することをお勧めします。 そうすれば、プロジェクトの開発者は常にmasterからの最新のビルドを{% data variables.product.prodname_registry %}からインストールして実行及びテストできるようになります。 -* **パッケージレジストリへのパッケージの公開** 多くのプロジェクトで、新しいバージョンのプロジェクトがリリースされたときにパッケージレジストリへの公開が行われます。 たとえば、JARファイルを生成するプロジェクトは、新しいリリースをMaven Centralリポジトリにアップロードするかもしれません。 あるいは、.NETのプロジェクトはnugetのパッケージを生成し、NuGet Galleryへアップロードするかもしれません。 +* **パッケージレジストリへのパッケージの公開** + 多くのプロジェクトで、新しいバージョンのプロジェクトがリリースされたときにパッケージレジストリへの公開が行われます。 たとえば、JARファイルを生成するプロジェクトは、新しいリリースをMaven Centralリポジトリにアップロードするかもしれません。 あるいは、.NETのプロジェクトはnugetのパッケージを生成し、NuGet Galleryへアップロードするかもしれません。 これは、リリースが作成される度にパッケージをパッケージレジストリに公開するワークフローを作成すれば、自動化できます。 詳しい情報については「[リリースの作成](/github/administering-a-repository/creating-releases)」を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/about-service-containers.md b/translations/ja-JP/content/actions/guides/about-service-containers.md index 0b931f43ee5bb..d177f529dd7af 100644 --- a/translations/ja-JP/content/actions/guides/about-service-containers.md +++ b/translations/ja-JP/content/actions/guides/about-service-containers.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### サービスコンテナについて @@ -53,7 +54,7 @@ on: push jobs: # コンテナジョブのラベル container-job: - # コンテナはLinuxベースのオペレｰ手イングシステム内で実行する + # コンテナはLinuxベースのオペレーティングシステム内で実行する runs-on: ubuntu-latest # `container-job`が実行されるDocker Hubイメージ container: node:10.18-jessie diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md index 71b644ec947c7..350380014fc63 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -91,7 +92,7 @@ steps: ### 成果物としてのワークフローのデータのパッケージ化 -ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、プルリクエストをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 +ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 Antは通常、JAR、EAR、WARのような出力ファイルを`build/jar`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md index 29ed37dea29f5..368eb41645ed7 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -91,7 +92,7 @@ steps: ### 依存関係のキャッシング -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml @@ -116,7 +117,7 @@ steps: ### 成果物としてのワークフローのデータのパッケージ化 -ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、プルリクエストをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 +ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 Gradleは通常、JAR、EAR、WARのような出力ファイルを`build/libs`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md index cc681c5aabc14..29d17e36097c7 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,14 +7,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに -このガイドは、ソフトウェアプロジェクト管理ツールのMavenを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、プルリクエストに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 +このガイドは、ソフトウェアプロジェクト管理ツールのMavenを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 {% data variables.product.prodname_dotcom %}ホストランナーは、Java Development Kits（JDKs）及びMavenを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。 JDK および Maven のソフトウェアとプリインストールされたバージョンのリストについては、「[{% data variables.product.prodname_dotcom %} でホストされているランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 @@ -73,7 +74,7 @@ jobs: ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 -スターターワークフローは、デフォルトで`package`タスクを実行します。 デフォルトのMavenの設定では、このコマンドは依存関係をダウンロードし、クラスをビルドし、テストを実行し、たとえばJARファイルのような配布可能なフォーマットにクラスをパッケージします。 +スターターワークフローは、デフォルトで`package`ターゲットを実行します。 デフォルトのMavenの設定では、このコマンドは依存関係をダウンロードし、クラスをビルドし、テストを実行し、たとえばJARファイルのような配布可能なフォーマットにクラスをパッケージします。 プロジェクトのビルドに異なるコマンドを使ったり、異なるターゲットを使いたいのであれば、それらを指定できます。 たとえば、_pom-ci.xml_ファイル中で設定された`verify`ターゲットを実行したいこともあるでしょう。 @@ -91,7 +92,7 @@ steps: ### 依存関係のキャッシング -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-net.md b/translations/ja-JP/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..acdc49f777636 --- /dev/null +++ b/translations/ja-JP/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: .NETでのビルドとテスト +intro: .NETプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。 +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### はじめに + +このガイドは、.NETパッケージのビルド、テスト、公開の方法を紹介します。 + +{% data variables.product.prodname_dotcom %}ホストランナーは、.NET Core SDKを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。 最新のソフトウェアとプリインストールされたバージョンの.NET Core SDKの完全なリストについては、[{% data variables.product.prodname_dotcom %}ホストランナー上にインストールされているソフトウェア](/actions/reference/specifications-for-github-hosted-runners)を参照してください。 + +### 必要な環境 + +YAMLの構文と、{% data variables.product.prodname_actions %}でのYAMLの使われ方に馴染んでいる必要があります。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。 + +.NET Core SDKの基本的な理解をしておくことをおすすめします。 詳細は「[Getting started with .NET](https://dotnet.microsoft.com/learn)」を参照してください。 + +### .NETワークフローテンプレートを使い始める + +{% data variables.product.prodname_dotcom %}は、ほとんどの.NETプロジェクトで動作する.NETワークフローテンプレートを提供しており、このガイドにはこのテンプレートのカスタマイズ方法を示す例が含まれています。 詳しい情報については[.NETワークフローテンプレート](https://github.com/actions/setup-dotnet)を参照してください。 + +手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### .NETのバージョンの指定 + +{% data variables.product.prodname_dotcom %}ホストランナーにプリインストールされたバージョンの.NET Core SDKを使うには、`setup-dotnet`アクションを使ってください。 このアクションは各ランナーのツールキャッシュから指定されたバージョンの.NETを見つけ、必要なバイナリを`PATH`に追加します。 これらの変更は、ジョブの残りの部分で保持されます。 + +`setup-dotnet`アクションは、{% data variables.product.prodname_actions %}で.NETを使うための推奨される方法です。これは、それによって様々なランナーや様々なバージョンの.NETに渡って一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、.NETをインストールして`PATH`に追加しなければなりません。 詳しい情報については[`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet)を参照してください。 + +#### 複数の.NETバージョンの利用 + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### 特定のバージョンの.NETの利用 + +`3.1.3`というような、特定のバージョンの.NETを使うようにジョブを設定できます。 あるいは、最新のマイナーリリースを取得するためにセマンティックバージョン構文を使うこともできます。 この例では.NET 3の最新のマイナーリリースを使っています。 + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### 依存関係のインストール + +{% data variables.product.prodname_dotcom %}ホストランナーには、NuGetパッケージマネージャーがインストールされています。 コードをビルドしてテストする前に、dotnetCLIを使って依存関係をNuGetパッケージレジストリからインストールしておくことができます。 たとえば、以下のYAMLは`Newtonsoft`パッケージをインストールします。 + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### 依存関係のキャッシング + +ユニークなキーを使ってNuGetｎ依存関係をキャッシュしておくことができ、そうすることで将来のワークフローで[`cache`](https://github.com/marketplace/actions/cache)アクションによってその依存関係をリストアできます。 たとえば、以下のYAMLは`Newtonsoft`パッケージをインストールします。 + +詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/guides/caching-dependencies-to-speed-up-workflows)」を参照してください。 + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**ノート：** 依存関係の数によっては、依存関係キャッシュを使う方が高速になることがあります。 多くの大きな依存関係を持つプロジェクトでは、ダウンロードに必要な時間を節約できるので、パフォーマンスの向上が見られるでしょう。 依存関係が少ないプロジェクトでは、大きなパフォーマンスの向上は見られないかもしれず、NuGetがキャッシュされた依存関係をインストールする方法のために、パフォーマンスがやや低下さえするかもしれません。 パフォーマンスはプロジェクトによって異なります。 + +{% endnote %} + +{% endif %} + +### コードのビルドとテスト + +ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 以下の例は、ジョブで`dotnet build`と`dotnet test`を使う方法を示します。 + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### 成果物としてのワークフローのデータのパッケージ化 + +ワークフローが完了すると、結果の成果物を分析のためにアップロードできます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 以下の例は、`upload-artifact`アクションを使ってテスト結果をアップロードする方法を示しています。 + +詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # always()を使い、テストが失敗したときにテスト結果が公開されるよう、このステップが必ず実行されるようにする + if: ${{ always() }} +``` +{% endraw %} + +### パッケージレジストリへの公開 + +CIテストにパスしたら、Dotnetパッケージをパッケージレジストリに公開するようにワークフローを設定できます。 バイナリを公開するのに必要なトークンや認証情報を保存するために、リポジトリシークレットを使うことができます。 以下の例では、`dotnet core cli`を使ってパッケージを作成し、{% data variables.product.prodname_registry %}に公開しています。 + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md index b28baf91afe8a..983ba8667b01c 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -36,7 +37,11 @@ Node.js、YAML、ワークフローの設定オプションと、ワークフロ ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ jobs: `setup-node`アクションはNode.jsのバージョンを入力として取り、ランナー上でそのバージョンを設定します。 `setup-node`は各ランナー上のツールキャッシュから指定されたNode.jsのバージョンを見つけ、必要なバイナリを`PATH`に追加します。設定されたバイナリは、ジョブでそれ以降永続化されます。 `setup-node`アクションの利用は、{% data variables.product.prodname_actions %}でNode.jsを使うための推奨される方法です。これは、そうすることで様々なランナーや様々なバージョンのNode.jsで一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、Node.jsをインストールして`PATH`に追加しなければなりません。 -以下のテンプレートには、Node.jsのバージョン8.x、10.x、12.ｘでコードをビルドしてテストするマトリクス戦略が含まれています。 この'x'はワイルドカードキャラクターで、そのバージョンで利用できる最新のマイナー及びパッチリリースにマッチします。 `node-version`配列で指定されたNode.jsの各バージョンに対して、同じステップを実行するジョブが作成されます。 +このテンプレートには、Node.jsの4つのバージョン、10.x、12.x、14.x、15.xでコードをビルドしてて酢と酢とマトリクス戦略が含まれています。 この'x'はワイルドカードキャラクターで、そのバージョンで利用できる最新のマイナー及びパッチリリースにマッチします。 `node-version`配列で指定されたNode.jsの各バージョンに対して、同じステップを実行するジョブが作成されます。 それぞれのジョブは、配列`node-version` のマトリクスで定義された値に、`matrix`コンテキストを使ってアクセスできます。 `setup-node`アクションは、このコンテキストを`node-version`のインプットとして使います。 `setup-node`アクションは、コードのビルドとテストに先立って、様々なNode.jsのバージョンで各ジョブを設定します。 マトリクス戦略とコンテキストに関する詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)」及び「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 @@ -77,7 +80,7 @@ jobs: ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -129,7 +130,7 @@ Node.jsのバージョンを指定しなかった場合、{% data variables.prod {% data variables.product.prodname_dotcom %}ホストランナーには、依存関係マネージャーのnpmとYarnがインストールされています。 コードのビルドとテストに先立って、npmやYarnを使ってワークフロー中で依存関係をインストールできます。 Windows及びLinuxの{% data variables.product.prodname_dotcom %}ホストランナーには、Grunt、Gulp、Bowerもインストールされています。 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 #### npmの利用例 @@ -193,9 +194,9 @@ steps: {% data reusables.github-actions.setup-node-intro %} -To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +プライベートレジストリに対して認証するには、npm 認証トークンをシークレットとして保存する必要があります。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 -以下の例では、`NPM_TOKEN`というシークレットにはnpmの認証トークンが保存されます。 `setup-node`アクションは、環境変数の`NODE_AUTH_TOKEN`からnpmの認証トークンを読み取るよう*.npmrc*ファイルを設定します。 When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token. +以下の例では、`NPM_TOKEN`というシークレットにはnpmの認証トークンが保存されます。 `setup-node`アクションは、環境変数の`NODE_AUTH_TOKEN`からnpmの認証トークンを読み取るよう*.npmrc*ファイルを設定します。 `setup-node` アクションを使用して *.npmrc* ファイルを作成する場合は、npm 認証トークンを含むシークレットを使用して `NODE_AUTH_TOKEN` 環境変数を設定する必要があります。 依存関係をインストールする前に、`setup-node`アクションを使って*.npmrc*ファイルを作成してください。 このアクションには2つの入力パラメーターがあります。 `node-version`パラメーターはNode.jsのバージョンを設定し、`registry-url`パラメーターはデフォルトのレジストリを設定します。 パッケージレジストリがスコープを使うなら、`scope`パラメーターを使わなければなりません。 詳しい情報については[`npm-scope`](https://docs.npmjs.com/misc/scope)を参照してください。 @@ -227,7 +228,7 @@ always-auth=true #### 依存関係のキャッシングの例 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 +{% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用して依存関係をキャッシュし、`cache` アクションを使用して将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} ```yaml 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 8872f5c1c1c68..16d175ea048db 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 @@ -1,38 +1,39 @@ --- -title: Building and testing PowerShell -intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project. +title: PowerShell のビルドとテスト +intro: PowerShell プロジェクトのビルドとテストのための継続的インテグレーション (CI) ワークフローを作成できます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' authors: - potatoqualitee +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに -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. +このガイドでは、CIのためのPowerShellの使用方法を示します。 Pesterの使い方、依存関係のインストール、モジュールのテスト、PowerShell Galleryへの公開について説明します。 -{% 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)". +{% data variables.product.prodname_dotcom %}ホストランナーは、PowerShell及びPesterを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。 最新のソフトウェアと、PowerShellおよびPesterのプリインストールされたバージョンの完全なリストについては、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 ### 必要な環境 YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。 -We recommend that you have a basic understanding of PowerShell and Pester. 詳しい情報については、以下を参照してください。 -- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) +PowerShell及びPesterの基本的な理解をしておくことをおすすめします。 詳しい情報については、以下を参照してください。 +- [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 +### 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. +PowerShellとPesterでテストを自動化するには、変更がリポジトリにプッシュされるたびに実行されるワークフローを追加できます。 以下の例では、`resultsfile.log`というファイルがあるかをチェックするために`Test-Path`が使われます。 -This example workflow file must be added to your repository's `.github/workflows/` directory: +以下の例のワークフローファイルは、リポジトリの`.github/workflows/`ディレクトリに追加しなければなりません。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-python.md b/translations/ja-JP/content/actions/guides/building-and-testing-python.md index 4c5c232c37a91..3dc828060bc56 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-python.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-python.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -122,7 +123,7 @@ jobs: #### 　特定のバージョンのPythonの利用 -Pythonの特定バージョンを設定することができます。 たとえば3.8が利用できます。 あるいは、セマンティックバージョン構文を使い、最新のマイナーリリースを使うことができます。 以下の例では、Python 3の最新のマイナーリリースを使います。 +Pythonの特定バージョンを設定することができます。 たとえば3.8が利用できます。 Alternatively, you can use semantic version syntax to get the latest minor release. 以下の例では、Python 3の最新のマイナーリリースを使います。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md index f8d8cc1d4e858..ee3cebbd119f8 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md @@ -5,10 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 209d641a5c33f..27fb3aeab9971 100644 --- a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: 'tutorial' --- ### ワークフローの依存関係のキャッシングについて @@ -38,15 +39,15 @@ versions: ワークフローは、現在のブランチ、ベースブランチ（フォークされたリポジトリのベースブランチを含む）、またはデフォルトブランチ（通常は `main`）で作成されたキャッシュにアクセスして復元できます。 たとえば、デフォルトブランチで作成されたキャッシュは、どのプルリクエストからもアクセスできます。 また、`feature-b` ブランチに `feature-a` ベースブランチがある場合、`feature-b` でトリガーされたワークフローは、デフォルトのブランチ（`main`）、`feature-a`、および `feature-b` で作成されたキャッシュにアクセスできます。 -アクセス制限は、異なるワークフローとブランチ間の論理的な境界を作成することによって、キャッシュの分離とセキュリティを提供します。 たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のプルリクエストにアクセスできません。 +アクセス制限は、様々なワークフローとブランチ間の論理的な境界を作成することによって、キャッシュの分離とセキュリティを提供します。 たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のプルリクエストにアクセスできません。 ### `cache`アクションの利用 -`cache`アクションは、提供された`key`に基づいてキャッシュをリストアしようとします。 このアクションは、キャッシュを見つけるとそのキャッシュファイルを設定された`path`にリストアします。 +`cache`アクションは、提供された`key`に基づいてキャッシュをリストアしようとします。 このアクションは、キャッシュを見つけるとそのキャッシュされたファイルを設定された`path`にリストアします。 正確なマッチがなければ、ジョブが成功したならこのアクションは新しいキャッシュエントリを作成します。 新しいキャッシュは提供された`key`を使い、`path`ディレクトリ内にファイルを保存します。 -既存のキャッシュに`key`がマッチしなかった場合に使われる、`restore-keys`のリストを提供することもできます。 `restore-keys`のリストは、 `restore-keys`が部分的にしかキャッシュキーとマッチしないために、他のブランチからのキャッシュをリストアする場合に役立ちます。 `restore-keys`のマッチに関する詳しい情報については「[キャッシュキーのマッチ](#matching-a-cache-key)」を参照してください。 +既存のキャッシュに`key`がマッチしなかった場合に使われる、`restore-keys`のリストを提供することもできます。 `restore-keys`のリストは、 `restore-keys`がキャッシュキーと部分的にマッチできるので、他のブランチからのキャッシュをリストアする場合に役立ちます。 `restore-keys`のマッチに関する詳しい情報については「[キャッシュキーのマッチ](#matching-a-cache-key)」を参照してください。 詳しい情報については「[`actions/cache`](https://github.com/actions/cache)」を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md index 252709d5ac777..24253ff7ba85a 100644 --- a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md @@ -9,10 +9,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md b/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md index 7901e089a4fd1..896e920f4d5f2 100644 --- a/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md @@ -9,10 +9,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md index af233a2d590c9..ff82cd3f12aad 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md b/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md index d509e5364f069..11642fef92c02 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md index 1ac60c04779ad..7b120d4cb5c6b 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/index.md b/translations/ja-JP/content/actions/guides/index.md index 45d9b8067d4fe..e033b156ba403 100644 --- a/translations/ja-JP/content/actions/guides/index.md +++ b/translations/ja-JP/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 - -### カスタム継続的インテグレーションワークフローを作成する - -{% data variables.product.prodname_actions %} を使用して、さまざまなプログラミング言語で記述されたプロジェクトを設定およびテストするカスタム継続的インテグレーション (CI) ワークフローを作成できます。 - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### Creating custom continuous deployment workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous deployment (CD) workflows that deploy projects to a number of cloud partner ecosystems. - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### ソフトウェア パッケージを公開する - -継続的デリバリ (CD) ワークフローの一部として、ソフトウェア パッケージの公開を自動化できます。 パッケージは、任意のパッケージ ホストおよび {% data reusables.gated-features.packages %} に公開できます。 - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### ワークフローデータのキャッシングと保存 - -依存関係をキャッシュし、成果物を保存して、ワークフローの実行を効率化してください。 - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### ワークフローでサービスコンテナを使用する - -サービス コンテナを使用して、サービスをワークフローに接続します。 - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/ja-JP/content/actions/guides/publishing-docker-images.md b/translations/ja-JP/content/actions/guides/publishing-docker-images.md index 1a95f1b78fec0..da81741c298b2 100644 --- a/translations/ja-JP/content/actions/guides/publishing-docker-images.md +++ b/translations/ja-JP/content/actions/guides/publishing-docker-images.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md index e8638a6b63132..130f7eb968a98 100644 --- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md index 3e6a7ad009750..46453f5bcb92b 100644 --- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに 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 fd72447502b52..4bb69c41ab20c 100644 --- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -44,7 +45,7 @@ Node.jsプロジェクトのためのCIワークフローの作成に関する 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればnpmレジストリにパッケージを公開します。 -To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 デフォルトでは、npmは*package.json*ファイルの`name`フィールドを使ってnpmレジストリを決めます。 グローバルな名前空間に公開する場合は、パッケージ名だけを含める必要があります。 たとえば`https://www.npmjs.com/package/npm-hello-world-test`に`npm-hello-world-test`という名前のパッケージを公開できます。 @@ -87,9 +88,28 @@ always-auth=true 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。 -デフォルトでは、{% data variables.product.prodname_registry %}は*package.json*ファイルの`name`フィールドで指定された{% data variables.product.prodname_dotcom %}のリポジトリにパッケージを公開します。 たとえば`@my-org/test`という名前のパッケージを{% data variables.product.prodname_dotcom %}リポジトリの`my-org/test`に公開します。 詳しい情報については、npmドキュメンテーション中の[`npm-scope`](https://docs.npmjs.com/misc/scope)を参照してください。 +#### Configuring the destination repository -ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 `GITHUB_TOKEN`は、デフォルトでリポジトリ中に存在し、ワークフローが実行されるリポジトリ中のパッケージには読み書きの権限があります。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. + +However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Authenticating to the destination repository + +To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." + +If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +#### Example workflow 以下の例は、`GITHUB_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。 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 9bf8f04fcda01..60358c25a22a2 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 @@ -1,7 +1,7 @@ --- title: ワークフローテンプレートを使用して継続的インテグレーションを設定する shortTitle: テンプレートを使用した CI の設定 -intro: 使用したい言語とツールに一致するワークフローテンプレートを使用して、プロジェクトに継続的インテグレーションを設定することができます。 +intro: 使用したい言語とツールにマッチするワークフローテンプレートを使用して、プロジェクトに継続的インテグレーションを設定することができます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -11,10 +11,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} リポジトリへの書き込み権限があるユーザなら誰でも {% data variables.product.prodname_actions %} を使用して継続的インテグレーション (CI) を設定することができます。 @@ -22,7 +23,7 @@ CIを設定すると、必要に応じてワークフローをカスタマイズ {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. 使用したい言語とツールに一致するテンプレートを探し、[**Set up this workflow**] をクリックします。 ![[Setup workflow] ボタン](/assets/images/help/repository/setup-workflow-button.png) +1. 使用したい言語とツールにマッチするテンプレートを探し、[**Set up this workflow**] をクリックします。 ![[Setup workflow] ボタン](/assets/images/help/repository/setup-workflow-button.png) 5. [**Start commit**] をクリックします。 ![[Start commit]ボタン](/assets/images/help/repository/start-commit.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md index 649df5503d1ab..eb069b0071694 100644 --- a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -1,7 +1,7 @@ --- title: ワークフロー データをアーティファクトとして保存する shortTitle: ワークフロー アーティファクトを保存する -intro: アーティファクトを使うと、ワークフローが完了したときに、そのワークフローのジョブとストアデータの間でデータを共有することができます。 +intro: 成果物を使うと、ワークフロー内のジョブ間でデータを共有し、ワークフローが完了したときに、そのワークフローのデータを保存できます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/persisting-workflow-data-using-artifacts @@ -11,14 +11,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### ワークフローの成果物について -成果物を使えば、ジョブの完了後にデータを永続化でき、そのデータを同じワークフロー中の他のジョブと共有できます。 アーティファクトとは、ワークフロー実行中に生成されるファイル、またはファイルのコレクションです。 たとえば、成果物を使ってワークフローの実行が終了した後、ビルドとテストの出力を保存しておけます。 +成果物を使えば、ジョブの完了後にデータを永続化でき、そのデータを同じワークフロー中の他のジョブと共有できます。 成果物とは、ワークフロー実行中に生成されるファイル、またはファイルのコレクションです。 たとえば、ワークフローの実行が終了した後、成果物を使ってビルドとテストの出力を保存しておけます。 {% data reusables.github-actions.artifact-log-retention-statement %} プルリクエストの保持期間は、ユーザが新しいコミットをプルリクエストにプッシュするたびに再開されます。 @@ -27,7 +28,7 @@ versions: - ログファイルとコアダンプ - テスト結果、エラー、スクリーンショット - バイナリあるいは圧縮されたファイル -- ストレステストのパフォーマンス出力およびコード網羅率の結果 +- ストレステストのパフォーマンス出力およびコードカバレッジの結果 {% if currentVersion == "free-pro-team@latest" %} @@ -54,13 +55,13 @@ versions: 継続的インテグレーション（CI）ワークフローを作成して、コードのビルドやテストを行えます。 {% data variables.product.prodname_actions %} を使用して CI を実行する方法の詳細については、「[継続的インテグレーションについて](/articles/about-continuous-integration)」を参照してください。 -コードのビルドおよびテストを出力すると多くの場合、エラーのデバッグに使用できるファイルと、デプロイできる本番コードが生成されます。 リポジトリにプッシュされるコードをビルドしてテストし、成功または失敗のステータスをレポートするワークフローを構成することができます。 デプロイメントに使用するビルドおよびテスト出力をアップロードし、失敗したテストまたはクラッシュをデバッグしてテストスイートの範囲を確認できます。 +コードのビルドおよびテストからの出力によって、多くの場合、エラーのデバッグに使用できるファイルと、デプロイできる本番コードが生成されます。 リポジトリにプッシュされるコードをビルドしてテストし、成功または失敗のステータスをレポートするワークフローを構成することができます。 デプロイメントに使用するビルドおよびテスト出力をアップロードし、失敗したテストまたはクラッシュをデバッグしてテストスイートのカバレッジを確認できます。 -成果物をアップロードするには、`upload-artifact`アクションが使用できます。 成果物をアップロードする場合は、単一のファイルまたはディレクトリー、または複数のファイルまたはディレクトリーを指定できます。 また、特定のファイルやディレクトリを除外したり、ワイルドカードパターンを使用したりすることもできます。 アーティファクトの名前を指定することをお勧めしますが、名前を指定しない場合は、 `アーティファクト` が既定の名前として使用されます。 構文の詳細については、 {% data variables.product.product_location %} 上の {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) アクション{% else %} `actions/upload-artifact` アクション{% endif %}を参照してください。 +成果物をアップロードするには、`upload-artifact`アクションが使用できます。 成果物をアップロードする場合は、単一のファイルまたはディレクトリ、あるいは複数のファイルまたはディレクトリを指定できます。 また、特定のファイルやディレクトリを除外したり、ワイルドカードパターンを使用したりすることもできます。 成果物の名前を指定することをおすすめしますが、名前を指定しない場合は、 `artifact` がデフォルトの名前として使用されます。 構文の詳細については、 {% data variables.product.product_location %} 上の {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) アクション{% else %} `actions/upload-artifact` アクション{% endif %}を参照してください。 #### サンプル -たとえば、リポジトリあるいはWebアプリケーションにはCSSやJavaScriptに変換しなければならないSASSやTypeScriptが含まれているかもしれません。 ビルド構成が`dist`ディレクトリにコンパイル後のファイルを出力すると仮定すると、テストがすべて正常に完了した場合、`dist`ディレクトリにあるファイルがWebアプリケーションにデプロイされます。 +たとえば、リポジトリあるいはWebアプリケーションにはCSSやJavaScriptに変換しなければならないSASSやTypeScriptが含まれているかもしれません。 ビルド構成が`dist`ディレクトリにコンパイル後のファイルを出力すると仮定すると、テストがすべて正常に完了した場合、`dist`ディレクトリにあるファイルがWebアプリケーションサーバーにデプロイされます。 ``` |-- hello-world (repository) @@ -74,38 +75,38 @@ versions: | ``` -この例では、srcディレクトリにコードを`builds`して、`tests`ディレクトリでテストを実行するNode.jsプロジェクトのワークフローを作成しています。 実行中の`npm test`が、`code-coverage.html`という名前で、`output/test/`ディレクトリに保存されるコード網羅率レポートを生成すると想定できます。 +この例では、srcディレクトリにコードを`builds`して、`tests`ディレクトリでテストを実行するNode.jsプロジェクトのワークフローを作成しています。 実行中の`npm test`が、`code-coverage.html`という名前で、`output/test/`ディレクトリに保存されるコードカバレッジレポートを生成すると想定できます。 -ワークフローは、 `dist` ディレクトリにプロダクション アーティファクトをアップロードしますが、マークダウン ファイルは除きます。 また、 `の code-coverage.html` レポートを別のアーティファクトとしてアップロードします。 +このワークフローは `dist` ディレクトリにプロダクションの成果物をアップロードしますが、Markdownファイルはその対象外です。 また、 `code-coverage.html`レポートは別の成果物としてアップロードされます。 ```yaml -名前: ノード CI +name: Node CI -: [push] +on: [push] -ジョブ: +jobs: build_and_test: - 実行: ubuntu-最新 - ステップ: - - 名前: チェックアウト リポジトリ - 使用: アクション/checkout@v2 - - 名前: npm インストール、ビルド、テスト - 実行: | - npm のインストール - npm 実行ビルド --if-present - npm テスト - - 名前: アーカイブ制作アーティファクト - 使用: アクション/アップロードartifact@v2 - : - 名: dist-マークダウンなし - パス: | + runs-on: ubuntu-latest + steps: + - name: Checkout repository + uses: actions/checkout@v2 + - name: npm install, build, and test + run: | + npm install + npm run build --if-present + npm test + - name: Archive production artifacts + uses: actions/upload-artifact@v2 + with: + name: dist-without-markdown + path: | dist !dist/**/*.md - - 名前: アーカイブ コード カバレッジ結果 - 使用: アクション/アップロードartifact@v2 - と共に: - 名: コード カバレッジ レポート - パス: output/test/code-coverage.html + - name: Archive code coverage results + uses: actions/upload-artifact@v2 + with: + name: code-coverage-report + path: output/test/code-coverage.html ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} @@ -137,23 +138,24 @@ versions: {% note %} -**注意:** 同じワークフロー実行中にアップロードされたワークフロー内のアーティファクトのみをダウンロードできます。 +**ノート:** ダウンロードできるのは、同じワークフロー実行中にアップロードされたワークフロー内の成果物のみです。 {% endnote %} -個々の成果物をダウンロードする成果物の名前を指定します。 名前を指定せずにアーティファクトをアップロードした場合、デフォルト名はアーティファクト`されます。

      +個々の成果物をダウンロードするには、成果物の名前を指定します。 名前を指定せずに成果物をアップロードした場合、デフォルトで名前は`artifact`になります。 -
      - 名前: 使用
-  単一のアーティファクトをダウンロード: アクション/ダウンロードartifact@v2
-  と共に:
-    名: my-artifact
-`
      +```yaml +- name: Download a single artifact + uses: actions/download-artifact@v2 + with: + name: my-artifact +``` -また、名前を指定しないことで、ワークフロー実行のすべての成果物をダウンロードすることもできます。 これは、多数のアーティファクトを扱っている場合に便利です。 +また、名前を指定しないことで、ワークフロー実行のすべての成果物をダウンロードすることもできます。 これは、多数の成果物を扱っている場合に便利です。 ```yaml -- 名前: 使用 - すべてのワークフロー実行アーティファクトをダウンロード: アクション/ダウンロードartifact@v2 +- name: Download all workflow run artifacts + uses: actions/download-artifact@v2 ``` ワークフロー実行のすべての成果物をダウンロードすると、各成果物のディレクトリーがその名前を使用して作成されます。 @@ -164,7 +166,7 @@ versions: `upload-artifact`アクションと`download-artifact`アクションを使うと、ワークフローのジョブ間でデータを共有できます。 以下のワークフローの例では、同じワークフローのジョブ間でデータを受け渡す方法を説明しています。 詳しい情報については、 {% data variables.product.product_location %} 上の {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) および [download-artifact](https://github.com/actions/download-artifact) アクション{% else %} `actions/upload-artifact` および `download-artifact` アクション{% endif %}を参照してください。 -前のジョブのアーティファクトに依存するジョブは、前のジョブが正常に完了するまで待つ必要があります。 このワークフローは、`needs`キーワードを使用して`job_1`、`job_2`、`job_3`を順次実行することができます。 たとえば、`job_2`には`needs: job_1`構文を使用する`job_1`が必要です。 +前のジョブの成果物に依存するジョブは、前のジョブが正常に完了するまで待つ必要があります。 このワークフローは、`needs`キーワードを使用して`job_1`、`job_2`、`job_3`を順次実行することができます。 たとえば、`job_2`は`needs: job_1`構文を使って`job_1`を必要とすることができます。 ジョブ1は、以下のステップを実行します。 - 数式の計算を実行し、その結果を`math-homework.txt`というテキストファイルに保存します。 @@ -182,64 +184,64 @@ versions: このワークフロー例で実行される完全な数式は、`(3 + 7) x 9 = 90`です。 ```yaml -名前: +name: Share data between jobs -ジョブ間でデータを共有: [push] +on: [push] -ジョブ: +jobs: job_1: - 名: 3 と 7 - 実行を追加: ubuntu 最新 - ステップ: - - シェル: バッシュ - 実行: | + name: Add 3 and 7 + runs-on: ubuntu-latest + steps: + - shell: bash + run: | expr 3 + 7 > math-homework.txt - - 名前: ジョブ1の数学の結果をアップロード - 使用: アクション/アップロードartifact@v2 - 使用: - 名: 宿題 - パス: math-homework.txt + - name: Upload math result for job 1 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt job_2: - 名: job_1 - の - ニーズ: job_1 実行: windows-最新 - ステップ: - - 名前: ジョブ1 - の数学結果をダウンロード使用: アクション/ダウンロードartifact@v2 - - - - : - 値='cat math-homework.txt' - は、数学-homework.txt - $value 9 > - 名前:ジョブ2 - の数学の結果をアップロード使用:アクション/アップロードartifact@v2 - : - 名:宿題 - パス:数学-宿題.txt + name: Multiply by 9 + needs: job_1 + runs-on: windows-latest + steps: + - name: Download math result for job 1 + uses: actions/download-artifact@v2 + with: + name: homework + - shell: bash + run: | + value=`cat math-homework.txt` + expr $value \* 9 > math-homework.txt + - name: Upload math result for job 2 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt job_3: - 名 結果 - 表示:のニーズを表示する:job_2 - 実行:macOS最新 - ステップ: - - 名前:ジョブ2の数学の結果をダウンロード - 使用:アクション/ダウンロードartifact@v2 - : - 名:宿題 - - 名前:シェル - 最終結果を印刷する:バッシュ - 実行: | - 値='cat数学宿題.txt' - エコー 結果は $value + name: Display results + needs: job_2 + runs-on: macOS-latest + steps: + - name: Download math result for job 2 + uses: actions/download-artifact@v2 + with: + name: homework + - name: Print the final result + shell: bash + run: | + value=`cat math-homework.txt` + echo The result is $value ``` The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -![ジョブ間でデータを受け渡して数学を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +![ジョブ間でデータを受け渡して計算を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) {% else %} -![ジョブ間でデータを受け渡して数学を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +![ジョブ間でデータを受け渡して計算を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index e78ba9eec54a4..840fe066d7ae3 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 自己ホストランナーについて diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 082809a89ed31..9e07f48fea036 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,10 +7,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{{ site.data.variables.product.prodname_actions }}にセルフホストランナーを追加できます。 + +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. セルフホストランナーでサポートされているオペレーティングシステム、あるいはプロキシサーバーとセルフホストランナーを使う方法に関する情報については、「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 @@ -44,6 +49,8 @@ versions: {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### セルフホストランナーを Enterprise に追加する セルフホストランナーを Enterprise に追加して、複数の Organization に割り当てることができます。 Organization の管理者は、そのリポジトリの使用対象を制御できます。 @@ -62,3 +69,13 @@ versions: 1. [**Add new**] をクリックし、[**New runner**] をクリックします。 新しいランナーがデフォルトグループに割り当てられます。 ランナーを登録した後、ランナーのグループを変更できます。 詳しい情報については、「[セルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Making enterprise runners available to repositories + +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. + +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. + +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index b707eab552f93..eefc59113764d 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,11 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% capture service_first_step %}1. セルフホストランナー アプリケーションが現在実行中の場合は、そのアプリケーションを停止します。{% endcapture %} {% capture service_non_windows_intro_shell %}ランナー マシンで、セルフホストランナー アプリケーションをインストールしたディレクトリでシェルを開きます。 以下のコマンドを使って、セルフホストランナーサービスをインストール及び管理します。{% endcapture %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md index 8bbdc36e457f6..c69fca7ab38df 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md @@ -9,8 +9,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% link_in_list /about-self-hosted-runners %} {% link_in_list /adding-self-hosted-runners %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index ce58d29bd42ca..3a2dca8808067 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,10 +6,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### セルフホストランナーのグループについて diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 01d246ca361aa..0cf61e9b67548 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,11 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### {{ site.data.variables.product.prodname_dotcom }}を使ったセルフホストランナーのステータスのチェック diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index b4d5993737ca3..7b25bee88c47e 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### リポジトリからのランナーの削除 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 64582fcec0c4e..98b4abfbec5ab 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,10 +6,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 環境変数を利用したプロキシサーバーの設定 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 32062b7863ace..c46df77faf445 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,10 +4,11 @@ intro: ラベルを使い、セルフホストランナーを特徴を基に整 versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} 特定の種類のセルフホストランナーにジョブをまわすためのラベルの利用方法に関する情報については、「[ワークフロー内でのセルフホストランナーの利用](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)」を参照してください。 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 4ddf5ec58ea89..0500f05a61a7a 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} カスタム及びデフォルトラベルの作成に関する情報については「[セルフホストランナーでのラベルの利用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md index 8c3b1ce73cb65..8b81ab992625f 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,10 +5,11 @@ intro: '{% data variables.product.prodname_actions %} は、堅牢で動的な versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 @@ -57,7 +58,7 @@ jobs: ### ジョブ間でデータを共有する -ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_アーティファクト_として {% data variables.product.prodname_dotcom %} に保存できます。 アーティファクトとは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、アーティファクトには、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 アーティファクトは、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 +ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_アーティファクト_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 アーティファクトは、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 たとえば、ファイルを作成し、それをアーティファクトとしてアップロードできます。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md index b49364b109f62..143f2bd8dd19b 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -10,10 +10,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 @@ -21,7 +22,7 @@ versions: - パブリック リポジトリ - ワークフローファイルがアクションを参照するのと同じリポジトリ -- Docker ハブで公開された Docker コンテナー イメージ +- Docker Hubで公開された Docker コンテナイメージ {% data variables.product.prodname_marketplace %}は、{% data variables.product.prodname_dotcom %}コミュニティによって構築されたアクションを見つけるための中央となる場所です。 [{% data variables.product.prodname_marketplace %} ページ](https://github.com/marketplace/actions/)では、アクションをカテゴリでフィルタできます。 @@ -76,7 +77,7 @@ steps: #### ブランチの使用 -Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. この例では、`@main` という名前のブランチを対象としています。 +Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. この例では、`@main` という名前のブランチを対象としています。 ```yaml steps: @@ -106,47 +107,47 @@ outputs: description: "Path to results file" ``` -### ワークフロー ファイルでアクションを使用する同じリポジトリ内のアクションの参照 +### ワークフロー ファイルでアクションを使用するのと同じリポジトリ内のアクションの参照 -ワークフロー ファイルがアクションを使用するのと同じリポジトリでアクションが定義されている場合は、ワークフロー ファイル内の`{owner}/{repo}@{ref}` または `./path/to/dir` 構文を使用してアクションを参照できます。 +ワークフロー ファイルがアクションを使用するのと同じリポジトリでアクションが定義されている場合、そのアクションはワークフロー ファイル内の`{owner}/{repo}@{ref}` または `./path/to/dir` 構文を使用して参照できます。 リポジトリ ファイル構造の例: ``` -|-- ハローワールド (リポジトリ) -| github -| └─ ワークフロー -| └─ 私の最初のワークフロー.yml -| └─ -アクション | |__ ハローワールドアクション -| └── アクション.yml +|-- hello-world (repository) +| |__ .github +| └── workflows +| └── my-first-workflow.yml +| └── actions +| |__ hello-world-action +| └── action.yml ``` ワークフロー ファイルの例: ```yaml -ジョブ: - ビルド: - 実行: ubuntu 最新 - ステップ: +jobs: + build: + runs-on: ubuntu-latest + steps: # このステップは、リポジトリのコピーをチェックアウトします。 - - 用途: アクション/checkout@v2 + - uses: actions/checkout@v2 # このステップは、アクションを含むディレクトリを参照します。 - - 用途: ./.github/アクション/ハローワールドアクション + - uses: ./.github/actions/hello-world-action ``` `action.yml` ファイルは、アクションのメタデータを提供するために使用されます。 このファイルの内容については、「[GitHub Actions のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions)」をご覧ください。 -### Docker ハブでのコンテナーの参照 +### Docker Hubでのコンテナーの参照 -アクションが Docker Hub の公開された Docker コンテナー イメージで定義されている場合は、ワークフロー ファイル内の `docker://{image}:{tag}` 構文を使用してアクションを参照する必要があります。 コードとデータを保護するために、ワークフローで使用する前に Docker Hub から Docker コンテナー イメージの整合性を確認することを強くお勧めします。 +アクションが Docker Hub の公開された Docker コンテナイメージで定義されている場合は、そのアクションはワークフロー ファイル内の `docker://{image}:{tag}` 構文を使用して参照する必要があります。 コードとデータを保護するために、ワークフローで使用する前に Docker HubからのDocker コンテナイメージの整合性を確認することを強くおすすめします。 ```yaml -ジョブ: +jobs: my_first_job: - ステップ: - - 名前: 使用 - 私の最初のステップ: docker://alpine:3.8 + steps: + - name: My first step + uses: docker://alpine:3.8 ``` Docker アクションの例については、[Docker-image.yml のワークフロー](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) および「[Docker コンテナのアクションを作成する](/articles/creating-a-docker-container-action)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/index.md b/translations/ja-JP/content/actions/learn-github-actions/index.md index aa6c9031bb09a..1d4fd61936308 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/index.md +++ b/translations/ja-JP/content/actions/learn-github-actions/index.md @@ -12,11 +12,11 @@ redirect_from: - /actions/getting-started-with-github-actions/getting-started-with-github-actions - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/ - /actions/configuring-and-managing-workflows/configuring-a-workflow - - /記事/ワークフローを作成する -github アクション/ - - /記事/ワークフローの構成 - - /github/自動化-ワークフローをgithubアクションで/ワークフローを設定する - - /アクション/自動化-ワークフローをgithubアクションで/ワークフローを設定する - - /アクション/作成ワークフロー/ワークフロー構成オプション + - /articles/creating-a-workflow-with-github-actions/ + - /articles/configuring-a-workflow + - /github/automating-your-workflow-with-github-actions/configuring-a-workflow + - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow + - /actions/creating-workflows/workflow-configuration-options - /articles/configuring-workflows - /github/automating-your-workflow-with-github-actions/configuring-workflows - /actions/automating-your-workflow-with-github-actions/configuring-workflows 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 dff0eb5dcedaa..972d0d916d0c1 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 @@ -9,10 +9,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 diff --git a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md index 5cb3e9aa80d0d..898837ae9185f 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md @@ -5,10 +5,11 @@ intro: 'This guide shows you how to use the advanced features of {% data variabl versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 @@ -154,6 +155,15 @@ jobs: You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." {% endif %} +### ワークフロー テンプレートの使用 + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. リポジトリに既存のワークフローが既に存在する場合: 左上隅にある [**New workflow（新しいワークフロー）**] をクリックします。 ![新規ワークフローの選択](/assets/images/help/repository/actions-new-workflow.png) +1. 使いたいテンプレート名の下で、**Set up this workflow（このワークフローをセットアップする）**をクリックしてください。 ![このワークフローを設定します](/assets/images/help/settings/actions-create-starter-workflow.png) + ### 次のステップ {% data variables.product.prodname_actions %} について詳しくは、「[Organization とワークフローを共有する](/actions/learn-github-actions/sharing-workflows-with-your-organization)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 4342e715e6d96..5ddafbb92aa6b 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,10 +6,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -328,4 +329,3 @@ jobs:
      アクティビティactivity airplay alert-circle alert-octagonalign-right anchor apertureアーカイブarchive
      arrow-down-circlecloud-rain cloud-snow cloudコードcode
      コマンドcommand compass copy corner-down-left
      file-plus file-textファイルfile film
      filterフラグflag folder-minus folder-plus
      hard-driveハッシュhash headphones heart
      repeat巻き戻しrewind rotate-ccw rotate-cw
      shopping-cart shuffleサイドバーsidebar skip-back
      tablet
      タグtag target terminal thermometerupload-cloud
      アップロードupload user-check user-minus user-plus
      user-xユーザuser users video-off
      ワークフロー中で利用できるアクションは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)で見つけることも、独自のactionsを作成することもできます。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。 - diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 09c761b8fa3b9..b59a5885b3368 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,10 +6,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 5402d2151e4bb..a979e521a8b8d 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,10 +4,11 @@ intro: '{% data variables.product.prodname_actions %} と GitLab CI/CDはいく versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 4ef768ff7854c..579e597f2b72e 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,10 +6,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -166,7 +167,7 @@ Jenkinsのパイプライン maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Jenkinsのパイプライン needs: job1 job3: needs: [job1, job2] - + ``` diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index e014f54682e2b..6c2514f744b96 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- ### はじめに @@ -193,7 +194,7 @@ The concurrent jobs and workflow execution times in {% data variables.product.pr 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: - [Node.js のビルドとテスト](/actions/guides/building-and-testing-nodejs) - - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell) + - [PowerShell のビルドとテスト](/actions/guides/building-and-testing-powershell) - [Python のビルドとテスト](/actions/guides/building-and-testing-python) - [MavenでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-maven) - [GradleでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-gradle) diff --git a/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 750532fb57323..8dde92c821ea3 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,10 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 @@ -33,7 +34,7 @@ versions: - **シークレットの処理方法を監査する** - シークレットの使用方法を監査し、シークレットが想定どおりに処理されていることを確認します。 これを行うには、ワークフローを実行しているリポジトリのソースコードを確認し、ワークフローで使用されているアクションを確認します。 たとえば、意図しないホストに送信されていないか、またはログ出力に明示的に出力されていないかを確認します。 - 有効/無効な入力をテストした後、ワークフローの実行ログを表示し、シークレットが正しく編集されているか、表示されていないかを確認します。 呼び出しているコマンドまたはツールがどのようにしてエラーを `STDOUT` および `STDERR` に送信するかは必ずしも明らかではなく、シークレットはその後エラーログに記録される可能性があります。 そのため、有効な入力と無効な入力をテストした後、ワークフローログを手動で確認することをお勧めします。 -- **スコープが最小限の資格情報を使用する** +- **スコープが最小限の認証情報を使用する** - ワークフロー内で使用されている認証情報に必要な最小限の権限があることを確認し、リポジトリへの書き込みアクセスを持つすべてのユーザが、リポジトリで設定されたすべてのシークレットへの読み取りアクセスを持っていることに注意してください。 - **登録されたシークレットの監査とローテーション** - 登録されたシークレットを定期的に確認して、現在も必要であることを確認します。 不要になったものは削除してください。 @@ -45,7 +46,7 @@ versions: ### サードパーティアクションを使用する -ワークフロー内の個々のジョブは、他のジョブと相互作用（および侵害）する場合があります。 たとえば、後のジョブで使用される環境変数をクエリするジョブ、後のジョブが処理する共有ディレクトリにファイルを書き込むジョブ、または Docker ソケットとやり取りして他の実行中のコンテナを検査してコマンドを実行することにより、さらに多くのディレクトリを作成するジョブなどです。 +ワークフロー内の個々のジョブは、他のジョブと相互作用（および侵害）する場合があります。 たとえば、後のジョブで使用される環境変数をクエリするジョブ、後のジョブが処理する共有ディレクトリにファイルを書き込むジョブ、あるいはもっと直接的にDocker ソケットとやり取りして他の実行中のコンテナを検査してコマンドを実行するジョブなどです。 これは、ワークフロー内の 1 つのアクションへの侵害が非常に重要になる可能性があるということです。その侵害されたアクションがリポジトリに設定されたすべてのシークレットにアクセスし、`GITHUB_TOKEN` を使用してリポジトリに書き込むことができるためです。 したがって、{% data variables.product.prodname_dotcom %} のサードパーティリポジトリからアクションを調達することには大きなリスクがあります。 次のような適切な方法に従うことで、このリスクを軽減することができます。 @@ -96,7 +97,7 @@ versions: **{% data variables.product.product_name %} のセルフホスト**ランナーは、一過性でクリーンな仮想マシンでの実行に関する保証がなく、ワークフロー内の信頼されていないコードによって永続的に侵害される可能性があります。 -そのため、[{% data variables.product.product_name %} のパブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、ユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得して、セルフホストのランナー環境を危険にさらすことができるためです。 +そのため、[{% data variables.product.product_name %} のパブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、ユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得することを含め、セルフホストのランナー環境を危険にさらすことができるためです。 When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index a0d5d9e251624..1658a8f155f7c 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,10 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 概要 @@ -18,87 +19,89 @@ versions: ### ワークフロー テンプレートの作成 -ワークフローテンプレートは、組織の `.github` リポジトリへの書き込みアクセス権を持つユーザーによって作成できます。 その後、ワークフローを作成する権限を持つ組織メンバーがテンプレートを使用できます。 ワークフロー テンプレートを使用すると、組織のパブリック リポジトリに新しいワークフローを作成できます。テンプレートを使用してプライベートリポジトリにワークフローを作成するには、組織がエンタープライズプランまたはGitHub Oneプランの一部である必要があります。 +ワークフローテンプレートは、Organizationの `.github` リポジトリへの書き込みアクセス権を持つユーザが作成できます。 その後、ワークフローを作成する権限を持つOrganizationのメンバーがテンプレートを使用できます。 ワークフロー テンプレートを使用すると、Organizationのパブリック リポジトリに新しいワークフローを作成できます。テンプレートを使用してプライベートリポジトリにワークフローを作成するには、OrganizationがエンタープライズプランまたはGitHub Oneプランの一部である必要があります。 -この手順では、ワークフロー テンプレートとメタデータ ファイルを作成する方法を示します。 メタデータ ファイルには、ユーザーが新しいワークフローを作成するときにテンプレートがどのように表示されるかについて説明します。 +この手順では、ワークフロー テンプレートとメタデータ ファイルを作成する方法を示します。 メタデータ ファイルには、ユーザが新しいワークフローを作成するときにテンプレートがどのように表示されるかについて説明します。 -1. 存在しない場合は、組織内で .github `という名前の新しいパブリック リポジトリを作成します。 -
    • ワークフロー テンプレートという名前のディレクトリ 作成`。 -1. `ワークフローテンプレート` ディレクトリ内に新しいワークフローファイルを作成します。 +1. 存在しない場合は、Organization内で`.github`という名前の新しいパブリック リポジトリを作成します。 +1. `workflow-templates`という名前のディレクトリを作成します。 +1. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。 リポジトリのデフォルトブランチを参照する必要がある場合は、 `$default-branch` プレースホルダを使用できます。 テンプレートを使用してワークフローを作成すると、プレースホルダはリポジトリのデフォルトブランチの名前に自動的に置き換えられます。 - たとえば、octo-organization-ci.yml `名前のこのファイルは、基本的なワークフローを示しています。 -
         name: Octo Organization CI
+   たとえば、`octo-organization-ci.yml`という名前のこのファイルは、基本的なワークフローを示しています。
 
-   :
-     プッシュ:
-       ブランチ: [ $default-ブランチ ]
+   ```yaml
+   name: Octo Organization CI
+
+   on:
+     push:
+       branches: [ $default-branch ]
      pull_request:
-       ブランチ: [ $default-ブランチ]
-
-   ジョブ:
-     ビルド:
-       実行: ubuntu-最新
-
-       ステップ:
-       - 使用: アクション/checkout@v2
-
-       - 名前: 1 行スクリプトを実行
-         実行します: Octo Organization から hello をエコーします
-`
      -1. `ワークフローテンプレート` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば、octo-organization-ci.properties.json `名前のこのファイルには` 、octo-organization-ci.yml`名前のワークフローファイルのメタデータが含まれています。 -
         { "名前"
-       " " " " " " " " " "説明"
-       " "説明" " " "" "アイコン"
-       " "example-icon"
-       "" "  "" "
-       " " [
-           "go"  ]
-       "filePatterns" [
-           "package.json$" 」
-   
-       
-           、
-           "^Dockerfile"
-`
      - * `名` - 必須 **。** ワークフロー テンプレートの名前。 これは、使用可能なテンプレートの一覧に表示されます。 - * `説明` - 必須 **。** ワークフロー テンプレートの説明。 これは、使用可能なテンプレートの一覧に表示されます。 - * `アイコン名前` - 必須 **。** テンプレート リスト内のワークフローのエントリのアイコンを定義します。 `iconName` は、同じ名前の SVG アイコンである必要があり、 `ワークフローテンプレート` ディレクトリに格納する必要があります。 たとえば、example-icon.svg `名前の SVG ファイルは、 例アイコン`として参照されます。 - * `カテゴリ` - オプション **。** ワークフローの言語カテゴリを定義します。 ユーザーが使用可能なテンプレートを表示すると、同じ言語に一致するテンプレートの機能が顕著になります。 使用可能な言語カテゴリについては、「https://github.com/github/linguist/blob/master/lib/linguist/languages.yml」を参照してください。 - * `ファイルパターン` - オプション **。** 定義された正規表現に一致するファイルがユーザーのリポジトリのルート ディレクトリにある場合に、テンプレートを使用できるようにします。 - -別のワークフロー テンプレートを追加するには、同じ `ワークフロー テンプレート` ディレクトリにファイルを追加します。 例: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +1. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。 + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **必須。** ワークフロー テンプレートの名前。 これは、使用可能なテンプレートの一覧に表示されます。 + * `description` - **必須。** ワークフロー テンプレートの説明。 これは、使用可能なテンプレートの一覧に表示されます。 + * `iconName` - **必須。** テンプレート リスト内のワークフローのエントリのアイコンを定義します。 `iconName` は、同じ名前の SVG アイコンである必要があり、 `workflow-templates` ディレクトリに格納する必要があります。 たとえば、`example-icon.svg`という名前の SVG ファイルは、 `example-icon`として参照されます。 + * `categories` - **オプション。** ワークフローの言語カテゴリを定義します。 ユーザーが使用可能なテンプレートを表示する際に、同じ言語に一致するテンプレートが目立つようにになります。 使用可能な言語カテゴリについては、「https://github.com/github/linguist/blob/master/lib/linguist/languages.yml」を参照してください。 + * `filePatterns` - **オプション 。** 定義された正規表現に一致するファイルがユーザーのリポジトリのルート ディレクトリにある場合に、テンプレートを使用できるようにします。 + +別のワークフロー テンプレートを追加するには、同じ `workflow-templates` ディレクトリにファイルを追加します。 例: ![ワークフロー テンプレート ファイル](/assets/images/help/images/workflow-template-files.png) -### ワークフロー テンプレートの使用 +### Using a workflow template from your organization -この手順では、組織のメンバーがワークフロー テンプレートを検索して使用して新しいワークフローを作成する方法を示します。 組織のワークフロー テンプレートは、組織のメンバーであるすべてのユーザーが使用できます。 +この手順では、Organizationのメンバーがワークフロー テンプレートを検索して利用し、新しいワークフローを作成する方法を示します。 Organizationのワークフロー テンプレートは、Organizationのメンバーであるすべてのユーザーが使用できます。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. リポジトリに既存のワークフローが既に存在する場合: 左上隅にある [新しいワークフロー**] をクリックします。 ![新規ワークフローの選択](/assets/images/help/repository/actions-new-workflow.png)

      • -1 -組織のワークフロー テンプレートは、組織名で作成されたワークフロー"というタイトルの独自 _セクションにあります。 使いたいテンプレート名の下で、**Set up this workflow（このワークフローをセットアップする）**をクリックしてください。 ![このワークフローを設定します](/assets/images/help/settings/actions-create-starter-workflow.png)

      +1. リポジトリに既存のワークフローが既に存在する場合: 左上隅にある [**New workflow（新しいワークフロー）**] をクリックします。 ![新規ワークフローの選択](/assets/images/help/repository/actions-new-workflow.png) +1. Organizationのワークフロー テンプレートは、「_Organizationの名前_によって作成されたワークフロー」というタイトルの独自セクションにあります。 使いたいテンプレート名の下で、**Set up this workflow（このワークフローをセットアップする）**をクリックしてください。 ![このワークフローを設定します](/assets/images/help/settings/actions-create-starter-workflow.png) ### Organization 内でシークレットを共有する Organization 内でシークレットを一元管理し、選択したリポジトリで使用できるようにすることができます。 これは、1 つの場所でシークレットを更新し、その変更をシークレットを使用するすべてのリポジトリワークフローに適用できるということを示します。 -組織でシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 +Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 {% data reusables.github-actions.permissions-statement-secrets-organization %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} -1. [新しいシークレット ****] をクリックします。 -1. [名前] 入力ボックスにシークレットの名前 **入力します。 -1 シークレットの **値** を入力します。 -1 [ **リポジトリアクセス** ドロップダウン リストから、アクセス ポリシーを選択します。 -1 [**Add secret**] をクリックします。 +1. [**New secret（新しいシークレット）**] をクリックします。 +1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 +1. シークレットの **Value（値）** を入力します。 +1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 +1. [**Add secret（シークレットの追加）**] をクリックします。 ### Organization 内でセルフホストランナーを共有する diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 9a8473de66939..b2673969bab1f 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -7,54 +7,57 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.actions-workflow-status-badge-into %} -ワークフローで `名` キーワードを使用する場合は、ワークフローを名前で参照する必要があります。 ワークフローの名前に空白が含まれている場合は、URL エンコード文字列 `%20`にスペースを置き換える必要があります。 `name` キーワードに関する詳しい情報については、「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions#name)」を参照してください。 +ワークフローが`name` キーワードを使用する場合は、ワークフローを名前で参照する必要があります。 ワークフローの名前に空白が含まれている場合は、URL エンコード文字列の`%20`で空白を置き換えなければなりません。 `name` キーワードに関する詳しい情報については、「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions#name)」を参照してください。 ``` -https://github.com///ワークフロー//badge.svg +https://github.com///workflows//badge.svg ``` -または、ワークフローに `名が含まれていない場合`は、リポジトリのルート ディレクトリに対する相対ファイル パスを使用してワークフロー ファイルを参照する必要があります。 +または、ワークフローに `name`が含まれていない場合は、リポジトリのルート ディレクトリに対する相対ファイル パスを使用してワークフロー ファイルを参照する必要があります。 {% note %} -**注意:** ワークフローに `名が含まれていない場合、ファイル パスを使用してワークフロー ファイルを参照`機能しません。 +**ノート:** ワークフローに `name`が含まれていない場合、ファイル パスを使用してワークフロー ファイルを参照するのは機能しません。 {% endnote %} ``` -https://github.com///ワークフロー//badge.svg +https://github.com///workflows//badge.svg ``` ### ワークフロー名を使用する -この Markdown の例では、"すべてのユーザーを出す" という名前のワークフローのステータス バッジを追加します。 リポジトリの `OWNER` は、組織       `アクションであり、 リポジトリ` 名はハローワールド`。

      +このMarkdownの例では、"Greet Everyone" という名前のワークフローにステータス バッジを追加します。 リポジトリの `OWNER` は、`actions`というOrganizationであり、 `REPOSITORY`の名前は`hello-world`です。 -
      ![ワークフロー名の例](https://github.com/actions/hello-world/workflows/Greet%20E非常に一つ/バッジ.svg)
-`
      +``` +![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) +``` ### ワークフローのファイルパスを使用する -この Markdown の例では、ファイル パスを持つワークフローのステータス バッジを追加します `.github/workflow/main.yml`。 リポジトリの `OWNER` は、組織 `アクションであり、 リポジトリ` 名はハローワールド`。

      +この Markdown の例では、`.github/workflow/main.yml`というファイル パスのワークフローにステータス バッジを追加します 。 リポジトリの `OWNER` は、`actions`というOrganizationであり、 `REPOSITORY`の名前は`hello-world`です。 -
      ![ワークフロー ファイルのパスの例](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg)
-`
      +``` +![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) +``` ### `branch` パラメータを使用する -この Markdown の例では、機能 1の名前 `分岐のステータス バッジを追加します。

      +この Markdown の例では、`feature-1`という名前のブランチにステータス バッジを追加します。 -
      ![分岐パラメータの例](https://github.com/actions/hello-world/workflows/Greet%20E非常に一人/バッジ.svg?ブランチ=フィーチャー-1)
-`
      +``` +![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) +``` ### `event` パラメータを使用する -この Markdown の例では、 `pull_request` イベントによってトリガーされたワークフロー実行の状態を示すバッジを追加します。 +この Markdown の例では、 `pull_request` イベントによってトリガーされたワークフロー実行のステータスを示すバッジを追加します。 ``` -![イベント パラメーターの例](https://github.com/actions/hello-world/workflows/Greet%20E非常に一人/バッジ.svg?イベント=pull_request) +![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md index 641cd4b668815..ae5c7d834ae57 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-write %} @@ -29,8 +29,8 @@ versions: ワークフローの実行をキャンセルする場合、ワークフローの実行に関連するリソースを使用する他のソフトウェアを実行している可能性があります。 ワークフロー実行に関連するリソースを解放するため、{% data variables.product.prodname_dotcom %} がワークフロー実行をキャンセルする際のステップを知っておくと役立つ場合があります。 -1. ワークフローの実行をキャンセルするには、現在実行中のすべてのジョブに対して条件 `を再評価します。 条件が true`に評価 `場合、ジョブはキャンセルされません。 例えば、条件 : always()` が true と評価され、ジョブの実行が継続されます。 条件がない場合、前のステップが正常に終了した場合にのみ実行される条件 `の条件と同等です`。 +1. ワークフローの実行をキャンセルするために、サーバーは現在実行中のすべてのジョブに対して`if`条件を再評価します。 条件が`true`に評価された場合、ジョブはキャンセルされません。 例えば、`if: always()`はtrueと評価され、ジョブの実行は継続されるでしょう。 条件がない場合は`if:success()`と等価なので、前のステップが正常に終了した場合にのみ実行されます。 2. キャンセルする必要があるジョブについては、サーバーは、キャンセルする必要があるジョブを持つすべてのランナー マシンにキャンセル メッセージを送信します。 -3. 実行を継続するジョブの場合、サーバーは、未完了のステップの条件 場合、 `を再評価します。 条件が true`に `評価された場合、ステップは引き続き実行されます。 -
    • キャンセルが必要なステップの場合、ランナーマシンは、ステップのエントリープロセスに SIGINT/Ctrl-C` を送信します(javascriptアクションの`ノード` 、コンテナアクションのドッカー を `、ステップで実行` `を使用する場合は のbash/cmd/pwd` を送信します)。 プロセスが 7500 ミリ秒以内に終了しない場合、ランナーは `SIGTERM/Ctrl-Break` をプロセスに送信し、プロセスが終了するまで 2500 ミリ秒待ちます。 プロセスがまだ実行中の場合、ランナーはプロセスツリーを強制終了します。 +3. 実行を継続するジョブの場合、サーバーは、未完了のステップの`if` 条件を再評価します。 条件が `true`に評価された場合、ステップは引き続き実行されます。 +4. キャンセルが必要なステップの場合、ランナーマシンは、ステップのエントリープロセス（javascriptアクションの`node` 、コンテナアクションの`docker` 、ステップで`run` を使用する場合は `bash/cmd/pwd`）に `SIGINT/Ctrl-C` を送信します。 プロセスが7500ミリ秒以内に終了しない場合、ランナーは `SIGTERM/Ctrl-Break` をプロセスに送信し、プロセスが終了するまで2500ミリ秒待ちます。 プロセスがそれでも実行中のままなら、ランナーはプロセスツリーを強制終了します。 5. 5 分間のキャンセル タイムアウト期間が経過すると、サーバーは、実行を完了しないか、キャンセルプロセスを完了できなかったすべてのジョブとステップを強制的に終了します。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index fbddb708feb3e..c23a718d07259 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -7,17 +7,17 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -1. ワークフロー実行を削除するには、[ {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ] ドロップダウン メニューを使用して、[ワークフローの削除 ****を実行する] を選択します。 +1. ワークフロー実行を削除するには、[ {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}] ドロップダウン メニューを使用して、[**Delete workflow run（ワークフロー実行の削除）**] を選択します。 ![ワークフロー実行の削除](/assets/images/help/settings/workflow-delete-run.png) -2. 確認プロンプトを確認し、[はい、このワークフロー実行を完全に削除 **をクリックします。

      +2. 確認プロンプトを確認し、[**Yes, permanently delete this workflow run（はい、このワークフロー実行を完全に削除）**をクリックします。 - ![ワークフロー実行確認の削除](/assets/images/help/settings/workflow-delete-run-confirmation.png)
      • + ![ワークフロー実行確認の削除](/assets/images/help/settings/workflow-delete-run-confirmation.png) diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index 5cc85172efd21..8ee66f870f6a6 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.23' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。 REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[アクション REST API](/rest/reference/actions#workflows)」を参照してください。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 7b5bb2e735689..ffd2da0704cfc 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}デフォルトでは、{% data variables.product.product_name %} はビルドログとアーティファクトを 90 日間保存します。リポジトリのタイプに応じて、この保持期間をカスタマイズできます。 詳しい情報については、「[リポジトリ内の GitHub Actions アーティファクトとログの保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)」を参照してください。{% endif %} {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログとアーティファクトが 90 日間保存されます。{% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/enabling-debug-logging.md b/translations/ja-JP/content/actions/managing-workflow-runs/enabling-debug-logging.md index 3c05a81c794a3..b6313e6b0a6da 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/enabling-debug-logging.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/enabling-debug-logging.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} これらの追加ログは、ワークフローを含むリポジトリにシークレットを設定することで有効になるため、同じ権限要件が適用されます。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/index.md b/translations/ja-JP/content/actions/managing-workflow-runs/index.md index 4c44aec33f959..3d33423233d5c 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md @@ -15,8 +15,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 42a903b3a90bf..c801bd2fac3d1 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### Configuring a workflow to run manually @@ -23,11 +23,11 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} 1. 左側のサイドバーで、実行するワークフローをクリックします。 ![アクション選択ワークフロー](/assets/images/actions-select-workflow.png) -1. ワークフロー実行の一覧の上にある [ワークフローの実行 ****を実行する] を選択します。 ![アクション ワークフローのディスパッチ](/assets/images/actions-workflow-dispatch.png) -1. ワークフローを実行する分岐を選択し、ワークフローで使用される入力パラメータを入力します。 [ ワークフロー**実行 ] をクリックします。 ![アクションはワークフローを手動で実行します](/assets/images/actions-manually-run-workflow.png)

      +1. ワークフロー実行の一覧の上にある**Run workflow（ワークフローの実行）**を選択します。 ![アクション ワークフローのディスパッチ](/assets/images/actions-workflow-dispatch.png) +1. ワークフローを実行するブランチを選択し、ワークフローで使用される入力パラメータを入力します。 **Run workflow（ワークフローの実行）**をクリックします。 ![アクションはワークフローを手動で実行します](/assets/images/actions-manually-run-workflow.png) ### REST API を使用してワークフローを実行する -REST API を使用する場合は、 `入力` を構成し、要求本文パラメーターとして ref       します。 入力を省略すると、ワークフロー ファイルで定義されている既定値が使用されます。

      +REST API を使用する場合は、 `inputs`と`ref`をリクエストボディのパラメータとして設定してください。 入力を省略すると、ワークフロー ファイルで定義されているデフォルト値が使用されます。 -

      REST API の使用の詳細については、「ワークフローディスパッチ イベントの作成」を参照してください。

      +REST API の使用の詳細については、「[ワークフローディスパッチ イベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」を参照してください。 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 c1f12a08d0eb7..a300a7ea8d0da 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 @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 6b5f85b900d59..2a676da7e7b95 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### アーティファクトを削除する diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md index c3cefc5f383b8..f1ef803e42028 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -7,9 +7,9 @@ versions: enterprise-server: '>=3.1' --- -{% data variables.product.prodname_actions %} の支払いを管理する +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.visualization-beta %} -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 5f94cedce9d84..7b71a4727f227 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -7,12 +7,12 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ワークフローの実行ページから、ワークフローの実行が進行中か完了しているかを確認できます。 パブリックなリポジトリの分も含むワークフローの実行情報を見るには、{% data variables.product.prodname_dotcom %}のアカウントにログインしなければなりません。 詳細は「[GitHub 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 -実行が完了している場合には、結果が成功か失敗か、キャンセルされたか、またはニュートラルかを確認できます。 実行が失敗した場合には、ビルドログを表示して検索し、失敗の原因を診断してワークフローを再実行することもできます。 また、課金対象のジョブ実行時間を表示したり、ログをダウンロードして成果物をビルドすることもできます。 +実行が完了している場合には、結果が成功か失敗か、キャンセルされたか、またはニュートラルかを確認できます。 実行が失敗した場合には、ビルドログを表示して検索し、失敗の原因を診断してワークフローを再実行することもできます。 また、課金対象のジョブ実行時間を表示したり、ログやビルドの成果物をダウンロードすることもできます。 {% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 For more information about the Checks API, see "[Checks](/rest/reference/checks)." @@ -20,7 +20,7 @@ versions: ### ログを表示してエラーを診断する -ワークフローの実行を失敗した場合には、どのステップが失敗の原因になったかを確認し、失敗したステップのビルドログを確かめてトラブルシューティングすることができます。 各ステップの実行にかかった時間もわかります。 ログファイルの特定の行のパーマリンクをコピーして、チームで共有することもできます。 {% data reusables.repositories.permissions-statement-read %} +ワークフローの実行が失敗した場合には、どのステップが失敗の原因になったかを確認し、失敗したステップのビルドログを確かめてトラブルシューティングすることができます。 各ステップの実行にかかった時間もわかります。 ログファイルの特定の行のパーマリンクをコピーして、チームで共有することもできます。 {% data reusables.repositories.permissions-statement-read %} ワークフローファイルで設定されたステップに加えて、{% data variables.product.prodname_dotcom %} はジョブの実行をセットアップして完了するために、各ジョブに 2 つの追加ステップを追加します。 これらのステップは、「Set up job」および「Complete job」として実行されるワークフローに記録されます。 @@ -44,7 +44,7 @@ versions: {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. ログ出力の右上隅にある [**Search logs**] 検索ボックスに、検索語句を入力します。 +1. ログ出力の右上隅にある [**Search logs（ログの検索）**] 検索ボックスに、検索クエリを入力します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated-2.png) {% else %} @@ -52,7 +52,7 @@ versions: {% endif %} {% else %} 1. 検索に含めたい各ステップを展開するには、そのステップをクリックします。![ステップの名前](/assets/images/help/repository/failed-check-step.png) -1. ログ出力の右上隅にある [**Search logs**] 検索ボックスに、検索語句を入力します。 ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box.png) +1. ログ出力の右上隅にある [**Search logs（ログの検索）**] 検索ボックスに、検索クエリを入力します。 ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box.png) {% endif %} ### ログのダウンロード diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md index 6b30dc01b0bfb..4ff2a9fcf93dd 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -6,8 +6,8 @@ versions: free-pro-team: '*' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} 請求可能なジョブ実行時間（分）は、{% data variables.product.prodname_dotcom %} ホストランナーを使用するプライベートリポジトリで実行されるジョブに対してのみ表示されます。 パブリックリポジトリで {% data variables.product.prodname_actions %} を使用する場合、またはセルフホストランナーで実行されるジョブの場合、請求対象となる実行時間はありません。 @@ -19,6 +19,6 @@ versions: {% note %} - **注:** 表示される請求可能な時間には、丸めや分数の乗数は含まれません。 四捨五入や分乗数を含む {% data variables.product.prodname_actions %} の使用状況の合計を表示するには、「[{% data variables.product.prodname_actions %} の使用状況を表示する](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage)」を参照してください。 + **ノート:** 表示される請求可能な時間には、丸めや分数の乗数は含まれません。 四捨五入や分乗数を含む {% data variables.product.prodname_actions %} の使用状況の合計を表示するには、「[{% data variables.product.prodname_actions %} の使用状況を表示する](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md index 43aabb1d9c40e..4fc35546ea236 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index 18dfa49480547..7e2529c423c1d 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -9,8 +9,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### はじめに @@ -66,9 +66,9 @@ versions: {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### その他のスターターワークフロー +### More workflow templates -{% data variables.product.prodname_dotcom %} では、事前設定されたワークフローテンプレートが用意されており、継続的インテグレーションワークフローの自動化や作成が可能です。 {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) リポジトリ{% else %} {% data variables.product.product_location %} の `actions/starter-workflows` リポジトリで、ワークフローテンプレートの完全なリストを閲覧できます{% endif %}。 +{% data reusables.actions.workflow-template-overview %} ### 次のステップ @@ -120,7 +120,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workfow you want to run. +1. In the left sidebar, click the workflow you want to run. ![Select say hello job](/assets/images/help/repository/say-hello-job.png) 1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow. ![Trigger the manual workflow](/assets/images/help/repository/manual-workflow-trigger.png) @@ -131,9 +131,9 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o 1. In the workflow logs, expand the 'Run echo "Hello World!"' section. ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Next steps diff --git a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md index 15dbfc52534ba..cbf0c6b3881a0 100644 --- a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md @@ -11,8 +11,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### `GITHUB_TOKEN`シークレットについて @@ -79,18 +79,18 @@ versions: {% data variables.product.prodname_github_apps %} が各権限でアクセできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。 -| 権限 | アクセスタイプ | フォークしたリポジトリからのアクセス | -| ----------- | --------- | ------------------ | -| actions | 読み取り/書き込み | 読み取り | -| チェック | 読み取り/書き込み | 読み取り | -| コンテンツ | 読み取り/書き込み | 読み取り | -| デプロイメント | 読み取り/書き込み | 読み取り | -| issues | 読み取り/書き込み | 読み取り | -| メタデータ | 読み取り | 読み取り | -| パッケージ | 読み取り/書き込み | 読み取り | -| プルリクエスト | 読み取り/書き込み | 読み取り | -| リポジトリプロジェクト | 読み取り/書き込み | 読み取り | -| ステータス | 読み取り/書き込み | 読み取り | +| 権限 | アクセスタイプ | フォークしたリポジトリからのアクセス | +| ------------------- | --------- | ------------------ | +| actions | 読み取り/書き込み | 読み取り | +| checks | 読み取り/書き込み | 読み取り | +| contents | 読み取り/書き込み | 読み取り | +| deployments | 読み取り/書き込み | 読み取り | +| issues | 読み取り/書き込み | 読み取り | +| メタデータ | 読み取り | 読み取り | +| パッケージ | 読み取り/書き込み | 読み取り | +| pull requests | 読み取り/書き込み | 読み取り | +| repository projects | 読み取り/書き込み | 読み取り | +| statuses | 読み取り/書き込み | 読み取り | `GITHUB_TOKEN`で利用できない権限を要求するトークンが必要な場合は、個人アクセストークンを生成して、それをリポジトリのシークレットに設定できます。 diff --git a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md index f7f02d16d9710..bb4c7d215d494 100644 --- a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -13,8 +13,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### コンテキストと式について @@ -75,6 +75,10 @@ env: - `a-Z` または `_` で始まる。 - `a-Z` 、`0-9`、 `-`、または`_`が続く。 +#### Determining when to use contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### `github` コンテキスト `github` コンテキストは、ワークフローの実行および、その実行をトリガーしたイベントの情報を含みます。 ほとんどの `github` コンテキストデータは、環境変数で読み取ることができます。 環境変数に関する詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。 @@ -107,15 +111,14 @@ env: `env`コンテキストには、ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 ワークフローでの環境変数の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)」を参照してください。 -`env`の構文で、ワークフローファイル中の環境変数の値を利用できます。 ランナー中で環境変数の値を使いたい場合は、ランナーのオペレーティングシステムで環境変数を読み取る通常の方法を使ってください。 +`env`の構文で、ワークフローファイル中の環境変数の値を利用できます。 You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. ステップの構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)」を参照してください。 -`env`は`with`及び`name`キーの値の中で、あるいはステップの`if`条件の中でのみ使えます。 ステップの構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)」を参照してください。 +ランナー中で環境変数の値を使いたい場合は、ランナーのオペレーティングシステムで環境変数を読み取る通常の方法を使ってください。 | プロパティ名 | 種類 | 説明 | | ---------------------- | -------- | -------------------------------------------------------------- | | `env` | `オブジェクト` | このコンテキストは、ジョブのステップごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。 | -| `env.` | `string` | 特定の環境変数の値。 | - +| `env.` | `string` | 特定の環境変数の値。 | #### `job` コンテキスト @@ -172,7 +175,7 @@ env: {% data reusables.github-actions.github-context-warning %} -**.github/ワークフロー/メイン.yml** +**.github/workflows/main.yml** {% raw %} ```yaml on: push diff --git a/translations/ja-JP/content/actions/reference/encrypted-secrets.md b/translations/ja-JP/content/actions/reference/encrypted-secrets.md index 209a748147aa8..0acafdc02e1e7 100644 --- a/translations/ja-JP/content/actions/reference/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/reference/encrypted-secrets.md @@ -11,9 +11,9 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.environments-beta %} -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-github-hosted-runners %} ### 暗号化されたシークレットについて @@ -69,9 +69,9 @@ REST API を使用してシークレットを管理することもできます {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-secret %} 1. Click **New repository secret**. -1. [名前] 入力ボックスにシークレットの名前 **入力します。 -1 シークレットの値を入力します。 -1 [**Add secret**] をクリックします。 +1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 +1. シークレットの値を入力します。 +1. [**Add secret（シークレットの追加）**] をクリックします。 If your repository {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page. @@ -85,15 +85,14 @@ If your repository {% if currentVersion == "free-pro-team@latest" or currentVers {% data reusables.github-actions.sidebar-environment %} 1. Click on the environment that you want to add a secret to. 1. Under **Environment secrets**, click **Add secret**. -1. [名前] 入力ボックスにシークレットの名前 **入力します。 -1 シークレットの値を入力します。 -1 -[**Add secret**] をクリックします。 -{% endif %} +1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 +1. シークレットの値を入力します。 +1. [**Add secret（シークレットの追加）**] をクリックします。 +{% endif %} -### 組織の暗号化されたシークレットの作成 +### Organizationの暗号化されたシークレットの作成 -組織でシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 +Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 {% data reusables.github-actions.permissions-statement-secrets-organization %} @@ -101,20 +100,20 @@ If your repository {% if currentVersion == "free-pro-team@latest" or currentVers {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} 1. Click **New organization secret**. -1. [名前] 入力ボックスにシークレットの名前 **入力します。 -1 シークレットの **値** を入力します。 -1 [ **リポジトリアクセス** ドロップダウン リストから、アクセス ポリシーを選択します。 -1 [**Add secret**] をクリックします。 +1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 +1. シークレットの **Value（値）** を入力します。 +1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 +1. [**Add secret（シークレットの追加）**] をクリックします。 -### 組織レベルのシークレットへのアクセスの確認 +### Organizationレベルのシークレットへのアクセスの確認 -組織内のシークレットに適用されているアクセス ポリシーを確認できます。 +Organization内のシークレットに適用されているアクセス ポリシーを確認できます。 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} -1. シークレットのリストには、構成済みのアクセス許可とポリシーが含まれます。 例: ![シークレットリスト](/assets/images/help/settings/actions-org-secrets-list.png) -1. 各シークレットに構成されているアクセス許可の詳細については、[更新**] をクリックしてください。

      +1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: ![シークレットリスト](/assets/images/help/settings/actions-org-secrets-list.png) +1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。 ### 暗号化されたシークレットのワークフロー内での利用 @@ -184,7 +183,7 @@ You can store up to 1,000 secrets per organization{% if currentVersion == "free- {% warning %} -**警告**: アクションを実行する際、シークレットは出力されないので注意してください。 この回避策を用いる場合、{% data variables.product.prodname_dotcom %}はログに出力されたシークレットを削除しません。 +**警告**: アクションを実行する際、シークレットが出力されないよう注意してください。 この回避策を用いる場合、{% data variables.product.prodname_dotcom %}はログに出力されたシークレットを削除しません。 {% endwarning %} @@ -205,12 +204,12 @@ You can store up to 1,000 secrets per organization{% if currentVersion == "free- ``` shell #!/bin/sh - # mkdir $HOME/secrets - # --batch - ファイルを復号化して、インタラクティブなコマンド - # --yes を防ぎ、質問に対して "はい" を - -- yes --はい --パスフレーズを解読する ="$LARGE_SECRET_PASSPHRASE" \ - -- $HOME/secrets/my_secret.json my_secret.json.gpg + # ファイルを復号化 + mkdir $HOME/secrets + # --batchでインタラクティブなコマンドを防ぎ、 + # --yes で質問に対して "はい" が返るようにする + gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \ + --output $HOME/secrets/my_secret.json my_secret.json.gpg ``` 1. リポジトリにチェックインする前に、シェルスクリプトが実行可能であることを確かめてください。 @@ -222,27 +221,27 @@ You can store up to 1,000 secrets per organization{% if currentVersion == "free- $ git push ``` -1. ワークフローから、`step`を使用してシェルスクリプトを呼び出し、シークレットを復号化します。 ワークフローを実行している環境にリポジトリのコピーを作成するには、[`actions/checkout`](https://github.com/actions/checkout)アクションを使用する必要があります。 リポジトリのルートを基準として、`run`コマンドを使用することで、シェルスクリプトを参照します。 +1. ワークフローから、`step`を使用してシェルスクリプトを呼び出し、シークレットを復号化します。 ワークフローを実行している環境にリポジトリのコピーを作成するには、[`actions/checkout`](https://github.com/actions/checkout)アクションを使用する必要があります。 リポジトリのルートを基準として`run`コマンドを使用し、シェルスクリプトを参照します。 {% raw %} ```yaml - 名前: 大きな - - 秘密を持つワークフロー: プッシュ - - ジョブ - : プッシュジョブ: - 名:のジョブ - 実行: ubuntu 最新 - ステップ: - - 使用: アクション/checkout@v2 - - 名前: 大規模な秘密 - を復号化 - 実行: ./.github/scripts/decrypt_secret.sh env: + name: Workflows with large secrets + + on: push + + jobs: + my-job: + name: My Job + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Decrypt large secret + run: ./.github/scripts/decrypt_secret.sh + env: LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }} # このコマンドは、あなたの秘密が印刷されていることを示す例 - # あなたの印刷シークレットを削除します。 GitHub does - # not hide secrets that use this workaround. + # シークレットを出力する文は必ず削除してください。 GitHubは + # この回避先を使うシークレットは隠蔽しません。 - name: Test printing your secret (Remove this step in production) run: cat $HOME/secrets/my_secret.json ``` diff --git a/translations/ja-JP/content/actions/reference/environment-variables.md b/translations/ja-JP/content/actions/reference/environment-variables.md index 465269fb243f0..a128797a9c75e 100644 --- a/translations/ja-JP/content/actions/reference/environment-variables.md +++ b/translations/ja-JP/content/actions/reference/environment-variables.md @@ -11,12 +11,12 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 環境変数について -{% data variables.product.prodname_dotcom %}は、ワークフローの実行におけるどのステップでも使用できる、デフォルトの環境変数を設定します。 環境変数では、大文字小文字は区別されます。 アクションあるいはステップ内のコマンド実行は、環境変数を作成、読み取り、変更することができます。 +{% data variables.product.prodname_dotcom %}は、ワークフローの実行におけるどのステップでも使用できる、デフォルトの環境変数を設定します。 環境変数では、大文字小文字は区別されます。 アクションあるいはステップ内で実行されるコマンドは、環境変数を作成、読み取り、変更することができます。 カスタムの環境変数を設定するには、ワークフローファイル中でその変数を指定しなければなりません。 You can define environment variables for a step, job, or entire workflow using the [`jobs..steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs..env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 @@ -44,7 +44,7 @@ steps: | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} | `GITHUB_ACTION` | アクションの一意の識別子 (`id`)。 | | `GITHUB_ACTIONS` | {% data variables.product.prodname_actions %}がワークフローを実行しているときは常に`true`に設定されます。 この変数は、テストがローカルで実行されているときと、{% data variables.product.prodname_actions %}によって実行されているときを区別するために利用できます。 | -| `GITHUB_ACTOR` | ワークフローを開始するユーザーまたはアプリの名前。 `octocat`などです。 | +| `GITHUB_ACTOR` | ワークフローを開始するユーザまたはアプリの名前。 `octocat`などです。 | | `GITHUB_REPOSITORY` | 所有者およびリポジトリの名前。 `octocat/Hello-World`などです。 | | `GITHUB_EVENT_NAME` | ワークフローをトリガーしたwebhookイベントの名前。 | | `GITHUB_EVENT_PATH` | 完了したwebhookイベントペイロードのファイルのパス。 `/github/workflow/event.json`などです。 | @@ -57,12 +57,22 @@ steps: | `GITHUB_API_URL` | API URL を返します。 For example: `https://api.github.com`. | | `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `https://api.github.com/graphql`. | +{% tip %} + +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determining when to use default environment variables or contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### 環境変数の命名規則 {% note %} -**メモ:** {% data variables.product.prodname_dotcom %}では、`GITHUB_`という環境変数接頭辞は、{% data variables.product.prodname_dotcom %}が内部で使用するために予約されています。 `GITHUB_`接頭辞を使用して環境変数またはシークレットを設定すると、エラーになります。 +**Note:** {% data variables.product.prodname_dotcom %} reserves the `GITHUB_` environment variable prefix for internal use by {% data variables.product.prodname_dotcom %}. `GITHUB_`プレフィックスを使用して環境変数またはシークレットを設定すると、エラーになります。 {% endnote %} -ファイルシステム上の場所にそのポイントを設定した新しい環境変数がある場合は、`_PATH`接尾辞を指定する必要があります。 デフォルトの変数`HOME`と`GITHUB_WORKSPACE`は、「home」および「workspace」という言葉で最初から場所がわかっているため、この規則の例外です。 +ファイルシステム上の場所を指すように設定した新しい環境変数がある場合は、`_PATH`サフィックスを指定する必要があります。 デフォルトの変数`HOME`と`GITHUB_WORKSPACE`は、「home」および「workspace」という言葉で最初から場所であることがわかっているため、この規則の例外です。 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 9921a26477c42..8c91a1f43fa01 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 @@ -12,8 +12,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### ワークフローイベントを設定する @@ -80,6 +80,8 @@ versions: [crontab guru](https://crontab.guru/) を使うと、クーロン構文の生成および実行時間の確認に役立ちます。 また、クーロン構文の生成を支援するため、[crontab guru のサンプル](https://crontab.guru/examples.html)リストもあります。 +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." + ### 手動イベント ワークフローの実行を手動でトリガーできます。 リポジトリ内の特定のワークフローをトリガーするには、`workflow_dispatch` イベントを使用します。 リポジトリで複数のワークフローをトリガーし、カスタムイベントとイベントタイプを作成するには、`repository_dispatch` イベントを使用します。 @@ -108,7 +110,7 @@ on: workflow_dispatch ##### ワークフロー設定の例 -この例では、 `名` 定義し、入力       ` github.event.inputs.name` を使用してそれらを出力し、github.event.inputs.home コンテキスト `します。 If a home` isn't provided, the default value 'The Octoverse' is printed. +この例では、 `code`と`home`を入力として定義し、`github.event.inputs.name`及び`github.event.inputs.home`コンテキストを使用してそれらを出力します。 If a `home` isn't provided, the default value 'The Octoverse' is printed. {% raw %} ```yaml @@ -143,7 +145,7 @@ jobs: {% data reusables.github-actions.branch-requirement %} -{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.prodname_dotcom %} API を使って、[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳しい情報については、「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。 +{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.prodname_dotcom %} API を使って、[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳細については、「[リポジトリディスパッチ イベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。 カスタム `repository_dispatch` webhook イベントをトリガーするには、{% data variables.product.product_name %} API エンドポイントに `POST` リクエストを送信して、アクティビティのタイプを説明する `event_type` 名を提供する必要があります。 ワークフローの実行をトリガーするには、`repository_dispatch` イベントを使用するようワークフローを設定する必要もあります。 @@ -224,7 +226,7 @@ on: #### `delete` -誰かがブランチまたはタグを作成し、それによって `delete` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの削除](/rest/reference/git#delete-a-reference)」を参照してください。 +誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの削除](/rest/reference/git#delete-a-reference)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -414,7 +416,7 @@ on: #### `page_build` -誰かが {% data variables.product.product_name %} ページ対応のブランチを作成し、それによって `page_build` イベントがトリガーされるときにワークフローを実行します。 For information about the REST API, see "[Pages](/rest/reference/repos#pages)." +誰かが {% data variables.product.product_name %} ページ対応のブランチを作成し、それによって `page_build` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ページ](/rest/reference/repos#pages)」を参照してください。 {% data reusables.github-actions.branch-requirement %} @@ -512,7 +514,7 @@ on: {% note %} -**Note:** By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. 他のアクティビティタイプについてもワークフローをトリガーするには、`types` キーワードを使用してください。 +**注:** デフォルトでは、ワークフローが実行されるのは`pull_request` のアクティビティタイプが `opened`、`synchronize`、または `reopened` の場合だけです。 他のアクティビティタイプについてもワークフローをトリガーするには、`types` キーワードを使用してください。 {% endnote %} @@ -593,7 +595,8 @@ This event runs in the context of the base of the pull request, rather than in t たとえば、プルリクエストが `assigned`、`opened`、`synchronize`、または `reopened` だったときにワークフローを実行できます。 ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` diff --git a/translations/ja-JP/content/actions/reference/index.md b/translations/ja-JP/content/actions/reference/index.md index 1387d28de8074..c29abf789d1fc 100644 --- a/translations/ja-JP/content/actions/reference/index.md +++ b/translations/ja-JP/content/actions/reference/index.md @@ -8,8 +8,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### ワークフロー構文 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 cf44d43c68f42..cb0f79cb0190f 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 @@ -14,8 +14,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### {% data variables.product.prodname_dotcom %}ホストランナーについて @@ -83,44 +83,11 @@ Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効 {% endnote %} -WindowsとUbuntuのランナーはAzureでホストされ、IPアドレスの範囲がAzureデータセンターと同じになります。 現在、すべてのWindows及びUbuntuの{% data variables.product.prodname_dotcom %}ホストランナーは、以下のAzureリージョン内にあります。 - -- 米国東部(`eastus`) -- 米国東部2 (`eastus2`) -- 米国西部2 (`westus2`) -- 米国中部 (`centralus`) -- 米国中南部(`southcentralus`) - -Microsoftは、AzureのIPアドレスの範囲をJSONファイルで毎週更新しています。このファイルは、[Azure IP Ranges and Service Tags - Public Cloud (AzureのIPアドレス範囲とサービスタグ - パブリッククラウド)](https://www.microsoft.com/en-us/download/details.aspx?id=56519)のウェブサイトからダウンロードできます。 内部リソースに対する不正アクセスを防ぐために許可リストが必要な場合には、このIPアドレスの範囲を利用できます。 - -JSONファイルには、`values`という配列があります。 この配列のうち、たとえば`"AzureCloud.eastus2"`というようなAzureのリージョンの`name`と`id`があるオブジェクトで、サポート対象のIPアドレスが見つかります。 - -サポート対象のIPアドレスの範囲は、`"addressPrefixes"`オブジェクトにあります。 次に示すのは、JSONファイルを縮めたサンプルです。 - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. + +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. + +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### ファイルシステム diff --git a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md index 779277908616a..88c6b1d610717 100644 --- a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md @@ -9,8 +9,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### {% data variables.product.prodname_actions %}の支払いについて diff --git a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md index 38ef1f86b0f44..b3a74b06e745e 100644 --- a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md @@ -14,8 +14,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### ワークフローコマンドについて 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 282be096f1790..e20f0e055a109 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 @@ -12,8 +12,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### ワークフロー用のYAML構文について @@ -118,7 +118,7 @@ on: `paths-ignore` および `paths` キーワードは、`*` と `**` のワイルドカード文字を使って複数のパス名と一致させる glob パターンを受け付けます。 詳しい情報については、「[フィルタパターンのチートシート](#filter-pattern-cheat-sheet)」を参照してください。 -#### バスを無視する例 +#### パスを無視する例 パス名が `paths-ignore` のパターンとマッチする場合は常に、ワークフローは実行されません。 {% data variables.product.prodname_dotcom %} は、`paths-ignore` に定義されているパターンを、パス名に対して評価します。 以下のパスフィルタを持つワークフローは、リポジトリのルートにある `docs`ディレクトリ外のファイルを少なくとも1つ含む`push`イベントでのみ実行されます。 @@ -187,7 +187,7 @@ cron構文に関する詳しい情報については、「[ワークフローを ### `env` -ワークフロー中のすべてのジョブやステップから利用できる環境変数の`map`です。 1つのジョブあるいはステップからだけ利用できる環境変数を設定することもできます。 For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. 詳しい情報については「[`jobs..env`](#jobsjob_idenv)」及び「[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。 {% data reusables.repositories.actions-env-var-note %} @@ -223,7 +223,7 @@ defaults: 1つのワークフロー実行は、1つ以上のジョブからなります。 デフォルトでは、ジョブは並行して実行されます。 ジョブを逐次的に実行するには、`jobs..needs`キーワードを使用して他のジョブに対する依存関係を定義します。 -Each job runs in a runner environment specified by `runs-on`. +それぞれのジョブは、`runs-on`で指定されたランナー環境で実行されます。 ワークフローの利用限度内であれば、実行するジョブ数に限度はありません。 詳細については、{% data variables.product.prodname_dotcom %} ホストランナーの「[使用制限と支払い](/actions/reference/usage-limits-billing-and-administration)」、およびセルフホストランナーの使用制限については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。 @@ -249,7 +249,7 @@ jobs: ### `jobs..needs` -このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. +このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 1つのジョブが失敗した場合、失敗したジョブを続行するような条件式を使用していない限り、そのジョブを必要としている他のジョブはすべてスキップされます。 #### Example requiring dependent jobs to be successful @@ -288,7 +288,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al **必須** ジョブを実行するマシンの種類。 マシンは{% data variables.product.prodname_dotcom %}ホストランナーあるいはセルフホストランナーのいずれかです。 -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-github-hosted-runners %} #### {% data variables.product.prodname_dotcom %}ホストランナー @@ -303,7 +303,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al ##### サンプル ```yaml -ランオン:Ubuntu-最新 +runs-on: ubuntu-latest ``` 詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーの仮想環境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。 @@ -582,11 +582,11 @@ jobs: [Docker Hub](https://hub.docker.com/)で公開されているDockerイメージ。 ```yaml -ジョブ: +jobs: my_first_job: - ステップ: - - 名前: 使用 - 私の最初のステップ: docker://alpine:3.8 + steps: + - name: My first step + uses: docker://alpine:3.8 ``` #### Dockerパブリックレジストリアクションを使用する例 @@ -639,14 +639,15 @@ jobs: `shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルを上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 -| サポートされているプラットフォーム | `shell` パラメータ | 説明 | 内部で実行されるコマンド | -| ----------------- | ------------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| すべて | `bash` | 非Windowsプラットフォームのデフォルトシェルで、`sh`へのフォールバックがあります。 Windowsでbashシェルを指定すると、Windows用Gitに含まれるbashシェルが使用されます。 | `bash --noprofile --norc -eo pipefail {0}` | -| すべて | `pwsh` | PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `pwsh -command ". '{0}'"` | -| すべて | `python` | Pythonのコマンドを実行します。 | `python {0}` | -| Linux / macOS | `sh` | 非Windowsプラットフォームにおいてシェルが提供されておらず、パス上で`bash`が見つからなかった場合のフォールバック動作です。 | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | これはWindowsで使われるデフォルトのシェルです。 デスクトップPowerShellです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `powershell -command ". '{0}'"`. | +| サポートされているプラットフォーム | `shell` パラメータ | 説明 | 内部で実行されるコマンド | +| ----------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| すべて | `bash` | 非Windowsプラットフォームのデフォルトシェルで、`sh`へのフォールバックがあります。 Windowsでbashシェルを指定すると、Windows用Gitに含まれるbashシェルが使用されます。 | `bash --noprofile --norc -eo pipefail {0}` | +| すべて | `pwsh` | PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `pwsh -command ". '{0}'"` | +| すべて | `python` | Pythonのコマンドを実行します。 | `python {0}` | +| Linux / macOS | `sh` | 非Windowsプラットフォームにおいてシェルが提供されておらず、パス上で`bash`が見つからなかった場合のフォールバック動作です。 | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | これはWindowsで使われるデフォルトのシェルです。 PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `powershell -command ". '{0}'"`. | #### bashを使用してスクリプトを実行する例 @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### Python scriptを実行する例 ```yaml @@ -1149,7 +1159,7 @@ volumes: - `**`ゼロ個以上の任意のキャラクタにマッチします。 - `?`: ゼロ個もしくは1個のキャラクタにマッチします。 たとえば`Octoc?t`は`Octocat`にマッチします。 - `+`: 直前の文字の 1 つ以上に一致します。 -- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 たとえば`[0-9a-f]`という範囲は、任意の数字もしくは小文字にマッチします。 たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。 +- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 For example, the range`[0-9a-z]` matches any digit or lowercase letter. たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。 - `!`: パターンの先頭に置くと、肯定のパターンを否定にします。 先頭のキャラクタではない場合は、特別な意味を持ちません。 YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パターンを`*`、`[`、`!`で始める場合、そのパターンをクオートで囲まなければなりません。 @@ -1167,35 +1177,35 @@ YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パタ #### ブランチやタグにマッチするパターン -| パターン | 説明 | マッチの例 | -| --------------------------------------------- | ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `feature/*` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 | -`feature/my-branch`
      -`feature/your-branch` | -| `feature/**` | ワイルドカードの`**`は、ブランチ及びタグ名のスラッシュ（`/`）を含む任意のキャラクタにマッチします。 | -`feature/beta-a/my-branch`
      -`feature/your-branch`
      -`feature/mona/the/octocat` | -| -`main`
      -`releases/mona-the-octcat` | ブランチあるいはタグ名に完全に一致したときにマッチします。 | -`main`
      -`releases/mona-the-octocat` | -| `'*'` | スラッシュ（`/`）を含まないすべてのブランチ及びタグ名にマッチします。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | -`main`
      -`releases` | -| `'**'` | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。 | -`all/the/branches`
      -`every/tag` | -| `'*feature'` | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | -`mona-feature`
      -`feature`
      -`ver-10-feature` | -| `v2*` | `v2`で始めるブランチ及びタグ名にマッチします。 | -`v2`
      -`v2.0`
      -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングタグにマッチします。 | -`v1.10.1`
      -`v2.0.0` | +| パターン | 説明 | マッチの例 | +| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 | `feature/my-branch`

      `feature/your-branch` | +| `feature/**` | ワイルドカードの`**`は、ブランチ及びタグ名のスラッシュ（`/`）を含む任意のキャラクタにマッチします。 | `feature/beta-a/my-branch`

      `feature/your-branch`

      `feature/mona/the/octocat` | +| `main`

      `releases/mona-the-octcat` | ブランチあるいはタグ名に完全に一致したときにマッチします。 | `main`

      `releases/mona-the-octocat` | +| `'*'` | スラッシュ（`/`）を含まないすべてのブランチ及びタグ名にマッチします。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `main`

      `releases` | +| `'**'` | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。 | `all/the/branches`

      `every/tag` | +| `'*feature'` | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `mona-feature`

      `feature`

      `ver-10-feature` | +| `v2*` | `v2`で始めるブランチ及びタグ名にマッチします。 | `v2`

      `v2.0`

      `v2.9` | +| `v[12].[0-9]+.[0-9]+` | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングタグにマッチします。 | `v1.10.1`

      `v2.0.0` | #### ファイルパスにマッチするパターン パスパターンはパス全体にマッチしなければならず、リポジトリのルートを出発点とします。 -| パターン | マッチの説明 | マッチの例 | -| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | -| `'*'` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | -`README.md`
      -`server.rb` | -| `'*.jsx?'` | `?`はゼロ個以上の先行するキャラクタにマッチします。 | -`page.js`
      -`page.jsx` | -| `'**'` | ワイルドカードの`**`は、スラッシュ（`/`）を含む任意のキャラクタにマッチします。 これは `path`フィルタを使わない場合のデフォルトの動作です。 | -`all/the/files.md` | -| `'*.js'` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 リポジトリのルートにあるすべての`.js`ファイルにマッチします。 | -`app.js`
      -`index.js` | -| `'**.js'` | リポジトリ内のすべての`.js`ファイルにマッチします。 | -`index.js`
      -`js/index.js`
      -`src/js/app.js` | -| `docs/*` | リポジトリのルートの`docs`のルートにあるすべてのファイルにマッチします。 | -`docs/README.md`
      -`docs/file.txt` | -| `docs/**` | リポジトリのルートの`docs`内にあるすべてのファイルにマッチします。 | -`docs/README.md`
      -`docs/mona/octocat.txt` | -| `docs/**/*.md` | `docs`ディレクトリ内にある`.md`というサフィックスを持つファイルにマッチします。 | -`docs/README.md`
      -`docs/mona/hello-world.md`
      -`docs/a/markdown/file.md` | -| `'**/docs/**'` | リポジトリ内にある`docs`ディレクトリ内のすべてのファイルにマッチします、 | -`/docs/hello.md`
      -`dir/docs/my-file.txt`
      -`space/docs/plan/space.doc` | -| `'**/README.md'` | リポジトリ内にあるREADME.mdファイルにマッチします。 | -`README.md`
      -`js/README.md` | -| `'**/*src/**'` | リポジトリ内にある`src`というサフィックスを持つフォルダ内のすべてのファイルにマッチします。 | -`a/src/app.js`
      -`my-src/code/js/app.js` | -| `'**/*-post.md'` | リポジトリ内にある`-post.md`というサフィックスを持つファイルにマッチします。 | -`my-post.md`
      -`path/their-post.md` | -| `'**/migrate-*.sql'` | リポジトリ内の`migrate-`というプレフィックスと`.sql`というサフィックスを持つファイルにマッチします。 | -`migrate-10909.sql`
      -`db/migrate-v1.0.sql`
      -`db/sept/migrate-v1.sql` | -| -`*.md`
      -`!README.md` | 感嘆符（`!`）をパターンの前に置くと、そのパターンの否定になります。 あるファイルがあるパターンにマッチし、ファイル中でその後に定義されている否定パターンにマッチした場合、そのファイルは含まれません。 | -`hello.md`
      _マッチしない_
      -`README.md`
      -`docs/hello.md` | -| -`*.md`
      -`!README.md`
      -`README*` | パターンは順番にチェックされます。 先行するパターンを否定するパターンで、ファイルパスが再度含まれるようになります。 | -`hello.md`
      -`README.md`
      -`README.doc` | +| パターン | マッチの説明 | マッチの例 | +| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `README.md`

      `server.rb` | +| `'*.jsx?'` | `?`はゼロ個以上の先行するキャラクタにマッチします。 | `page.js`

      `page.jsx` | +| `'**'` | ワイルドカードの`**`は、スラッシュ（`/`）を含む任意のキャラクタにマッチします。 これは `path`フィルタを使わない場合のデフォルトの動作です。 | `all/the/files.md` | +| `'*.js'` | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 リポジトリのルートにあるすべての`.js`ファイルにマッチします。 | `app.js`

      `index.js` | +| `'**.js'` | リポジトリ内のすべての`.js`ファイルにマッチします。 | `index.js`

      `js/index.js`

      `src/js/app.js` | +| `docs/*` | リポジトリのルートの`docs`のルートにあるすべてのファイルにマッチします。 | `docs/README.md`

      `docs/file.txt` | +| `docs/**` | リポジトリのルートの`docs`内にあるすべてのファイルにマッチします。 | `docs/README.md`

      `docs/mona/octocat.txt` | +| `docs/**/*.md` | `docs`ディレクトリ内にある`.md`というサフィックスを持つファイルにマッチします。 | `docs/README.md`

      `docs/mona/hello-world.md`

      `docs/a/markdown/file.md` | +| `'**/docs/**'` | リポジトリ内にある`docs`ディレクトリ内のすべてのファイルにマッチします、 | `/docs/hello.md`

      `dir/docs/my-file.txt`

      `space/docs/plan/space.doc` | +| `'**/README.md'` | リポジトリ内にあるREADME.mdファイルにマッチします。 | `README.md`

      `js/README.md` | +| `'**/*src/**'` | リポジトリ内にある`src`というサフィックスを持つフォルダ内のすべてのファイルにマッチします。 | `a/src/app.js`

      `my-src/code/js/app.js` | +| `'**/*-post.md'` | リポジトリ内にある`-post.md`というサフィックスを持つファイルにマッチします。 | `my-post.md`

      `path/their-post.md` | +| `'**/migrate-*.sql'` | リポジトリ内の`migrate-`というプレフィックスと`.sql`というサフィックスを持つファイルにマッチします。 | `migrate-10909.sql`

      `db/migrate-v1.0.sql`

      `db/sept/migrate-v1.sql` | +| `*.md`

      `!README.md` | 感嘆符（`!`）をパターンの前に置くと、そのパターンの否定になります。 あるファイルがあるパターンにマッチし、ファイル中でその後に定義されている否定パターンにマッチした場合、そのファイルは含まれません。 | `hello.md`

      _Does not match_

      `README.md`

      `docs/hello.md` | +| `*.md`

      `!README.md`

      `README*` | パターンは順番にチェックされます。 先行するパターンを否定するパターンで、ファイルパスが再度含まれるようになります。 | `hello.md`

      `README.md`

      `README.doc` | diff --git a/translations/ja-JP/content/admin/authentication/using-saml.md b/translations/ja-JP/content/admin/authentication/using-saml.md index 26ad9447829b9..0a5b1e7e252c4 100644 --- a/translations/ja-JP/content/admin/authentication/using-saml.md +++ b/translations/ja-JP/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod ### SAMLのメタデータ -{% data variables.product.prodname_ghe_server %} インスタンスのサービスプロバイダメタデータは、`http(s)://[hostname]/saml/metadata` にあります。 +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. アイデンティティプロバイダを手動で設定するなら、Assertion Consumer Service (ACS) URLは`http(s)://[hostname]/saml/consume`です。 これは`urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`バインディングを利用します。 diff --git a/translations/ja-JP/content/admin/configuration/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/command-line-utilities.md index ee16d97d44fe5..362f26c8ebf9e 100644 --- a/translations/ja-JP/content/admin/configuration/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/command-line-utilities.md @@ -467,18 +467,21 @@ ghe-webhook-logs ``` 過去1日の失敗したフックデリバリーを表示するには、以下のようにします。 +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -フックのペイロードの全体や結果、デリバリーの例外を表示するには、以下のようにします。 +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -グローバルな webhook のデリバリーを表示するには、以下のようにします。 +フックのペイロードの全体や結果、デリバリーの例外を表示するには、以下のようにします。 ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### クラスタリング diff --git a/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index 4364096b86b1f..650ce4c9a088e 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ versions: {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. **HTTP Proxy Server（HTTPプロキシサーバ）**の下に、プロキシサーバのURLを入力してください。 ![HTTP プロキシサーバーのURLを入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-field.png) -5. オプションで、プロキシのアクセスを要しないホストがあれば**HTTP Proxy Exclusion（HTTPプロキシの除外）**の下にカンマ区切りで入力してください。 ![HTTP プロキシの除外を入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. オプションで、プロキシのアクセスを要しないホストがあれば**HTTP Proxy Exclusion（HTTPプロキシの除外）**の下にカンマ区切りで入力してください。 To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![HTTP プロキシの除外を入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md index 5a9cc64016aef..a2355341d2a4f 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ versions: 万が一、プライマリサイトで長時間の停止または壊滅的なイベントが発生した場合は、別の {% data variables.product.prodname_enterprise %} アプライアンスをプロビジョニングしてバックアップホストから復元を実行することで、{% data variables.product.product_location %} を復元できます。 アプライアンスを復元する前に、バックアップホストの SSH キーをターゲットの {% data variables.product.prodname_enterprise %} アプライアンスに認証済み SSH キーとして追加する必要があります。 +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + 最後に成功したスナップショットから {% data variables.product.product_location %} を復元するには、`ghe-restore` コマンドを使用します。 以下と同じような出力が表示されるでしょう: ```shell diff --git a/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 9f961ba3daffb..95fec3e63c6ed 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ versions: {% data reusables.enterprise_site_admin_settings.management-console %} 1. 左のサイドバーに **{% data variables.product.prodname_advanced_security %}** エントリがあるかどうかを確認します。 ![[Advanced Security] サイドバー](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -サイドバーに **{% data variables.product.prodname_advanced_security %}** が表示されない場合は、ライセンスに {% data variables.product.prodname_code_scanning %} を含む {% data variables.product.prodname_advanced_security %} 機能のサポートが含まれていないということです。 {% data variables.product.prodname_advanced_security %} ライセンスを使用すると、リポジトリとコードのセキュリティを強化するのに役立つ機能にアクセスできます。 +{% data reusables.enterprise_management_console.advanced-security-license %} ### {% data variables.product.prodname_code_scanning %} の有効化 -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ versions: #### セルフホストランナーを設定する -{% data variables.product.prodname_actions %} ベータに登録している場合、{% data variables.product.prodname_ghe_server %} は {% data variables.product.prodname_actions %} ワークフローを使用して {% data variables.product.prodname_code_scanning %} を実行できます。 まず、環境内に 1 つ以上のセルフホスト {% data variables.product.prodname_actions %} ランナーをプロビジョニングする必要があります。 セルフホストランナーは、リポジトリ、Organization、または Enterprise アカウントレベルでプロビジョニングできます。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」および「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 +{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. まず、環境内に 1 つ以上のセルフホスト {% data variables.product.prodname_actions %} ランナーをプロビジョニングする必要があります。 セルフホストランナーは、リポジトリ、Organization、または Enterprise アカウントレベルでプロビジョニングできます。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」および「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 {% data variables.product.prodname_codeql %} アクションを実行するために使用するセルフホストランナーの PATH 変数に Git が含まれていることを確認する必要があります。 -#### アクションをプロビジョニングする -{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_code_scanning %} を実行するには、適切なアクションがローカルで使用可能である必要があります。 アクションを 3 つの方法で利用可能にすることができます。 +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisioning the actions +To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **推奨** [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) を使用して、{% data variables.product.prodname_dotcom_the_website %} からアクションを自動的にダウンロードできます。 インスタンスをホストするマシンは、{% data variables.product.prodname_dotcom_the_website %} にアクセス可能である必要があります。 この方法で、最新のソフトウェアを自動的に入手できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)」を参照してください。 +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. インスタンスをホストするマシンは、{% data variables.product.prodname_dotcom_the_website %} にアクセス可能である必要があります。 この方法で、最新のソフトウェアを自動的に入手できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)」を参照してください。 - {% data variables.product.prodname_codeql_workflow %} を使用する場合は、[https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) にある {% data variables.product.prodname_codeql %} Action 同期ツールを使用して、リポジトリを {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.prodname_ghe_server %} に同期できます。 コンピューターで {% data variables.product.product_location %} と {% data variables.product.prodname_dotcom_the_website %} の両方に同時にアクセスできる限り、{% data variables.product.product_location %} または {% data variables.product.prodname_actions %} ランナーがインターネットにアクセスできるかどうかに関係なく、このツールを使用できます。 -- アクションで {% data variables.product.prodname_dotcom_the_website %} リポジトリをクローンすることにより、サーバーにアクションのリポジトリのローカルコピーを作成できます。 たとえば、{% data variables.product.prodname_codeql %} アクションを使用する場合、インスタンス `github/codeql-action` と呼ばれるリポジトリを作成し、{% data variables.product.prodname_dotcom_the_website %} から[リポジトリ](https://github.com/github/codeql-action)を複製して、そのリポジトリをインスタンスの `github/codeql-action` リポジトリにプッシュできます。 また、{% data variables.product.prodname_dotcom_the_website %} のリポジトリからリリースをダウンロードし、リリースとしてインスタンスの `github/codeql-action` リポジトリにアップロードする必要があります。 - +- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. また、{% data variables.product.prodname_dotcom_the_website %} のリポジトリからリリースをダウンロードし、リリースとしてインスタンスの `github/codeql-action` リポジトリにアップロードする必要があります。 ##### {% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する - 1. {% data variables.product.prodname_dotcom_the_website %} からオンデマンドでアクションワークフローをダウンロードする場合は、{% data variables.product.prodname_github_connect %} を有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を有効化する](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)」を参照してください。 -2. また、{% data variables.product.product_location %} に対して {% data variables.product.prodname_actions %} を有効化する必要があります。 詳しい情報については、「[{% data variables.product.prodname_actions %} の有効化とストレージの設定](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)」をご覧ください。 +2. また、{% data variables.product.product_location %} に対して {% data variables.product.prodname_actions %} を有効化する必要があります。 For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. 次のステップは、{% data variables.product.prodname_github_connect %} を使用して、{% data variables.product.prodname_dotcom_the_website %} に対するアクションへのアクセスを設定することです。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 4. セルフホストランナーをリポジトリ、Organization、または Enterprise アカウントに追加します。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configuring {% data variables.product.prodname_codeql %} on a server without internet access +If the server on which you are running +{% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} Action sync tool to copy the {% data variables.product.prodname_codeql %} actions and query bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -セルフホストランナーを設定した後、ユーザは {% data variables.product.product_location %} の個々のリポジトリに対して {% data variables.product.prodname_code_scanning %} を有効化できます。 デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`on.push` イベントを使用して、ワークフローファイルを含むブランチへのプッシュごとにコードスキャンをトリガーします。 +#### Enabling code scanning for individual repositories +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`on.push` イベントを使用して、ワークフローファイルを含むブランチへのプッシュごとにコードスキャンをトリガーします。 ### {% data variables.product.prodname_codeql_runner %} を使用して {% data variables.product.prodname_code_scanning %} を実行する -Organization が {% data variables.product.prodname_actions %} のベータに参加していない場合、または {% data variables.product.prodname_actions %} を使用しない場合は、{% data variables.product.prodname_codeql_runner %} を使用して {% data variables.product.prodname_code_scanning %} を実行できます。 +If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. {% data variables.product.prodname_codeql_runner %} は、サードパーティの CI/CD システムに追加できるコマンドラインツールです。 このツールは、{% data variables.product.prodname_dotcom %} リポジトリのチェックアウトに対して {% data variables.product.prodname_codeql %} 分析を実行します。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を CI システムで実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」を参照してください。 ### {% data variables.product.prodname_code_scanning %} を無効にする -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..883058bd63e82 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configuring secret scanning for your appliance +shortTitle: Configuring secret scanning +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### {% data variables.product.prodname_secret_scanning %} について + +{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +### 必要な環境 + +To use {% data variables.product.prodname_secret_scanning %} in {% data variables.product.product_location %} you need these two prerequisites. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- You need an {% data variables.product.prodname_advanced_security %} license. + +#### Checking support for the SSSE3 flag on your vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. + +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 +2. Enter the following command: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling secret scanning](#enabling-secret-scanning)" below. + +If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. + +#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. 左のサイドバーに **{% data variables.product.prodname_advanced_security %}** エントリがあるかどうかを確認します。 ![[Advanced Security] サイドバー](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### {% data variables.product.prodname_secret_scanning %} の有効化 + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. [ +{% data variables.product.prodname_advanced_security %}] の下にある [**{% data variables.product.prodname_secret_scanning_caps %}**] をクリックします。 +![{% data variables.product.prodname_secret_scanning %} を有効化または無効化するチェックボックス](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### {% data variables.product.prodname_secret_scanning %} を無効にする + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. [ +[{% data variables.product.prodname_advanced_security %}] の下にある [**{% data variables.product.prodname_secret_scanning_caps %}**] を選択解除します。 +![{% data variables.product.prodname_secret_scanning %} を有効化または無効化するチェックボックス](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md index c267a795090a9..cab1140a6d3c5 100644 --- a/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ Subdomain Isolationは、クロスサイトスクリプティングや関連す Subdomain Isolation が有効な場合、{% data variables.product.prodname_ghe_server %} はいくつかのパスをサブドメインで置き換えます。 -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} Docker を {% data variables.product.prodname_registry %} で使用するには、Subdomain Isolation も有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_registry %} で使用するために Docker を設定する](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)」を参照してください。 {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Subdomain Isolationなしのパス | Subdomain Isolationされたパス | -| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A、{% data variables.product.prodname_registry %} を使用した Docker は、Subdomain Isolation を無効化すると機能しません。 | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Subdomain Isolationなしのパス | Subdomain Isolationされたパス | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled for the {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### 必要な環境 diff --git a/translations/ja-JP/content/admin/configuration/index.md b/translations/ja-JP/content/admin/configuration/index.md index 1540ac770998e..51a50ada0ba9b 100644 --- a/translations/ja-JP/content/admin/configuration/index.md +++ b/translations/ja-JP/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..a8baff8a775b6 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Managing GitHub for mobile for your enterprise +intro: You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}. +permissions: Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### {% data variables.product.prodname_mobile %} について + +{% data reusables.mobile.about-mobile %} For more information, see "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." + +Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data. + +### Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/enterprise-management/about-clustering.md b/translations/ja-JP/content/admin/enterprise-management/about-clustering.md index 2c67a5e322e67..99193f74b09b3 100644 --- a/translations/ja-JP/content/admin/enterprise-management/about-clustering.md +++ b/translations/ja-JP/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ versions: クラスタリングは冗長性を提供しますが、High Availability構成を置き換えることを意図したものではありません。 詳細は「[High Availability 構成](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)」を参照してください。 プライマリ／セカンダリフェイルオーバー設定はクラスタリングよりもはるかにシンプルであり、多くの組織の要求に応えます。 詳しくは[クラスタリングと高可用性との違い](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)を参照してください。 +{% data reusables.package_registry.packages-cluster-support %} + ### クラスタリングを利用するには？ クラスタリングは特定のスケーリングの状況のために設計されており、すべての組織を対象としたものではありません。 クラスタリングをご検討される場合は、専任の担当者または {% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 diff --git a/translations/ja-JP/content/admin/enterprise-management/index.md b/translations/ja-JP/content/admin/enterprise-management/index.md index 8b6af438ef44e..a284e8a4f2832 100644 --- a/translations/ja-JP/content/admin/enterprise-management/index.md +++ b/translations/ja-JP/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md index f854d721ccfb6..3c2dc664a24e8 100644 --- a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + + {% endnote %} + {% endif %} diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 9dea765b38452..0d74965bfef78 100644 --- a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ High Availability と Geo-replication が設定されたアプライアンスは #### フィーチャリリースのロールバック フィーチャリリースからロールバックするには、ルートおよびデータパーティションが整合した状態になることを保証するため、VM スナップショットからリストアしてください。 詳細は「[スナップショットを取得する](#taking-a-snapshot)」を参照してください。 + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 参考リンク + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md index 799120ecc2411..decd682e302b0 100644 --- a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md @@ -59,7 +59,9 @@ $ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt - `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} 設定ログ - `collectd/logs/collectd.log`：Collectdのログ - `mail-logs/mail.log`：SMTPのメール配送ログ +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`：webhookのデリバリエラー +{% endif %} 詳細は「[監査ログ](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)」を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..037e1e40868b5 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: About using actions on GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} には、ほとんどの {% data variables.product.prodname_dotcom %} 作成のアクションが含まれ、{% data variables.product.prodname_dotcom_the_website %} および {% data variables.product.prodname_marketplace %} からの他のアクションへのアクセスを有効にするためのオプションがあります。' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 + +{% data reusables.actions.enterprise-no-internet-actions %} + +### {% data variables.product.prodname_ghe_server %} にバンドルされている公式アクション + +ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.prodname_ghe_server %} にバンドルされ、{% data variables.product.prodname_marketplace %} からある時点でキャプチャされます。 When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. + +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. + +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. + +{% note %} + +**注釈:** セルフホストランナーを使用して {% data variables.product.prodname_ghe_server %} でセットアップアクション（`actions/setup-LANGUAGE` など）を使用する場合、インターネットにアクセスできないランナーでツールキャッシュをセットアップする必要がある場合があります。 For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." + +{% endnote %} + +### {% data variables.product.prodname_dotcom_the_website %} でアクションへのアクセスを設定する + +Enterprise インスタンスのユーザが {% data variables.product.prodname_dotcom_the_website %} または {% data variables.product.prodname_marketplace %} から他のアクションにアクセスする必要がある場合、いくつかの設定オプションがあります。 + +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 {% data reusables.actions.enterprise-limit-actions-use %} + +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. 詳しい情報については、「[{% data variables.product.prodname_dotcom_the_website %} からのアクションを手動で同期する](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)」を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..ca8cd4f13168c --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Advanced configuration and troubleshooting +intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..a2556020e8d72 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. + +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: + +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. +1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 03f1898ac9ea7..4c643744f7954 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -8,12 +8,12 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} デフォルトでは、{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} ワークフローは {% data variables.product.prodname_dotcom_the_website %} または [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) から直接アクションを使用できません。 -{% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションを Enterprise インスタンスで使用できるようにするには、{% data variables.product.prodname_github_connect %} を使用して{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} に接続します。 {% data variables.product.prodname_dotcom_the_website %} からアクションにアクセスする他の方法については、「[{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_dotcom_the_website %} アクションの使用について](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)」を参照してください。 +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." ### すべての {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する @@ -23,3 +23,4 @@ versions: {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..097155565b393 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..4ee287b789dcb --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with Amazon S3 storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' +versions: + enterprise-server: '>=3.0' +--- + +### 必要な環境 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..1a377bd6efc11 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Enabling GitHub Actions with Azure Blob storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' +versions: + enterprise-server: '>=3.0' +--- + +### 必要な環境 + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..14c79c03e0395 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' +versions: + enterprise-server: '>=3.0' +--- + +### 必要な環境 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. +* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The URL to your MinIO service. たとえば、`https://my-minio.example:9000` などです。 + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 1e04f11655ac1..fad9d47882bec 100644 --- a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -7,8 +7,7 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} ### Enterprise の {% data variables.product.prodname_actions %} 権限について diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..e4700459c71d5 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**注釈:** {% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. + +### Review hardware considerations + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### External storage requirements + +{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にするには、外部 Blob ストレージにアクセスできる必要があります。 + +{% data variables.product.prodname_actions %} は、blob ストレージを使用して、ワークフローログやユーザがアップロードしたビルドアーティファクトなど、ワークフロー実行によって生成されたアーティファクトを保存します。 必要なストレージ容量は、{% data variables.product.prodname_actions %} の使用状況によって異なります。 Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} は、次のストレージプロバイダをサポートしています。 + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Amazon S3 permissions + +{% data reusables.actions.enterprise-s3-permission %} + +### {% data variables.product.prodname_actions %} の有効化 + +{% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 [Sign up for the beta](https://resources.github.com/beta-signup/). + +### 参考リンク + +- 「[{% data variables.product.prodname_ghe_server %} インスタンスを設定する](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)」のプラットフォームに関する「ハードウェアの留意点」 + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +### 自己ホストランナーの追加 + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 + +### Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." + +### General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." + +{% endif %} diff --git a/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..4d2a829fc5ebb --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: High availability for GitHub Actions +intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +versions: + enterprise-server: '>=3.0' +--- + +### Replication or redundancy of your {% data variables.product.prodname_actions %} data + +{% data reusables.actions.enterprise-storage-ha-backups %} + +We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: + +* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### High availability replicas + +#### Promoting a replica + +When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. + +For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." + +#### High Availabilityレプリカの削除 + +Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. diff --git a/translations/ja-JP/content/admin/github-actions/index.md b/translations/ja-JP/content/admin/github-actions/index.md index f07be6dc31e93..5bd5d7b290cec 100644 --- a/translations/ja-JP/content/admin/github-actions/index.md +++ b/translations/ja-JP/content/admin/github-actions/index.md @@ -7,16 +7,27 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### 目次 -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 4ab38b54c0cbb..dfb6c7256d962 100644 --- a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -7,12 +7,14 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-no-internet-actions %} -{% data variables.product.prodname_dotcom_the_website %} の特定のアクションをワークフローで使用できるようにするには、{% data variables.product.company_short %} のオープンソースの [`actions-sync`](https://github.com/actions/actions-sync) ツールを使用して、アクションリポジトリを {% data variables.product.prodname_dotcom_the_website %} から Enterprise インスタンスに同期します。 {% data variables.product.prodname_dotcom_the_website %} からアクションにアクセスする他の方法については、「[{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_dotcom_the_website %} アクションの使用について](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)」を参照してください。 +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 + +However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. ### About the `actions-sync` tool diff --git a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 33e41103dce08..1321a822c4d4a 100644 --- a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -7,8 +7,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### About the included setup actions and the runner tool cache diff --git a/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..55ba376bc7ea5 --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' +versions: + enterprise-server: '>=3.0' +--- + +### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + +#### Installing the certificate on the runner machine + +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. + +For the steps required to install a certificate, refer to the documentation for your runner's operating system. + +#### Configuring Node.JS to use the certificate + +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +例: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. 詳しい情報については「[セルフホストランナーの削除](/actions/hosting-your-own-runners/removing-self-hosted-runners)」及び「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..285cf6b65804b --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). 例: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). 例: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md index 37b95b8bb5d27..7c48be358bab2 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ aws ec2 run-instances \ ### 参考リンク -- "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md index 00b9e5cf5970b..35fdf2a75683e 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ versions: {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### 参考リンク - ### 参考リンク - - - "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index 952600434eed2..72f0fb2288e0d 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ GCE 仮想マシンは、ファイアウォールが存在するネットワー ### 参考リンク -- "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index 5f5bd9b049b84..8d1f5caf036cb 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### 参考リンク - - "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 8341a690ada89..2c616566fa874 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ versions: ### 参考リンク - - "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 2a4358806ccc7..ecb0c3713e4e8 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### 参考リンク - - "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 195ceedb89a72..68c29478c261c 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### 参考リンク - - "[システムの概要](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md index 2ab369f81e4f0..92075ec1fb40c 100644 --- a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ versions: 1. {% data variables.product.prodname_enterprise_backup_utilities %}を使って本番インスタンスをバックアップしてください。 詳細は「[アプライアンスでバックアップを設定する](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)」の「{% data variables.product.prodname_enterprise_backup_utilities %} について」セクションを参照してください。 2. 新しいインスタンスをステージング環境として動作するようにセットアップしてください。 ステージングインスタンスのプロビジョニングとインストールについては、本番インスタンスと同じガイドが利用できます。 詳細は「[{% data variables.product.prodname_ghe_server %}インスタンスをセットアップする](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)」を参照してください。 3. バックアップをステージングインスタンスにリストアしてください。 詳しい情報については "[アプライアンスでのバックアップの設定](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)"の"バックアップのリストア"セクションを参照してください。 + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 参考リンク + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..76ae50c528639 --- /dev/null +++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### 参考リンク + +- `github/roadmap` リポジトリの [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) diff --git a/translations/ja-JP/content/admin/overview/index.md b/translations/ja-JP/content/admin/overview/index.md index c0cb524f64618..cf2e674ef8b29 100644 --- a/translations/ja-JP/content/admin/overview/index.md +++ b/translations/ja-JP/content/admin/overview/index.md @@ -15,5 +15,6 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..cdc4fa4546265 --- /dev/null +++ b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. 詳しい情報については、「[Subdomain Isolation の有効化](/enterprise/admin/configuration/enabling-subdomain-isolation)」を参照してください。 +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. [Ecosystem Toggles] の下で、パッケージの種類ごとに [**Enabled**]、[**Read-Only**]、または [**Disabled**] を選択します。 ![エコシステムの切り替え](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| 資料 | Destination | ポート | 種類 | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### 次のステップ + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..26350b2f76963 --- /dev/null +++ b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**警告:** +- It is critical that you configure any restrictive access policies you need 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 to 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 %} + +### 必要な環境 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. [AWS Service URL] で、バケットのリージョンの S3 エンドポイント URL を入力します。 ![[AWS Service URL] フィールド](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. [AWS S3 Bucket] で、パッケージアーティファクトの保存に使用する S3 バケットの名前を入力します。 ![[AWS S3 Bucket] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. [AWS S3 Access Key] で、S3 のアクセスキーを入力します。 ![[AWS S3 Access Key] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. [AWS S3 Secret Key] で、S3 の秘密鍵を入力します。 ![[AWS S3 Secret Key] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. [AWS S3 Region] で、S3 のリージョンを入力します。 ![[AWS S3 Region] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 次のステップ + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..39f4ca308c518 --- /dev/null +++ b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**警告:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} + +### 必要な環境 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### 次のステップ + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..af2829738e8cf --- /dev/null +++ b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**警告:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} +### 必要な環境 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![[AWS Service URL] フィールド](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![[AWS S3 Bucket] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![[AWS S3 Access Key] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![[AWS S3 Secret Key] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![[AWS S3 Region] フィールド](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 次のステップ + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..674e3fb31e0ad --- /dev/null +++ b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_ghe_server %} 上の {% data variables.product.prodname_registry %} は、外部の blob ストレージを使用してパッケージを保存します。 + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. 各パッケージのホスト URL に `https://` が含まれていることを確認します。 + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. パッケージホスト URL の詳しい情報については、「[Subdomain Isolation を有効化する](/enterprise/admin/configuration/enabling-subdomain-isolation)」を参照してください。 {% data variables.product.product_name %} への TLS 証明書のアップロード方法について詳しくは、「[TLS を設定する](/enterprise/admin/configuration/configuring-tls)」を参照してください。 diff --git a/translations/ja-JP/content/admin/packages/index.md b/translations/ja-JP/content/admin/packages/index.md index 3ca9c8e5751f1..36d7a73dca194 100644 --- a/translations/ja-JP/content/admin/packages/index.md +++ b/translations/ja-JP/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..0de0e05bf3047 --- /dev/null +++ b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your third-party storage solution. + +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. + +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). + +### 1. Choose a MinIO mode for your needs + +| MinIO mode | Optimized for | Storage infrastructure required | +| ----------------------------------------------- | ------------------------------ | ------------------------------------ | +| Standalone MinIO (on a single host) | Fast setup | なし | +| MinIO as a NAS gateway | NAS (Network-attached storage) | NAS devices | +| Clustered MinIO (also called Distributed MinIO) | Data security | Storage servers running in a cluster | + +For more information about your options, see the official [MinIO docs](https://docs.min.io/). + +### 2. Install, run, and sign in to MinIO + +1. Set up your preferred environment variables for MinIO. + + These examples use `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Install MinIO. + + ```shell + $ docker pull minio/minio + ``` + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." + +3. Sign in to MinIO using your MinIO access key and secret. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + You can access your MinIO keys using the environment variables: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Run MinIO in your chosen mode. + + * Run MinIO using Docker on a single host: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." + + * Run MinIO using Docker as a NAS gateway: + + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + For more information, see "[MinIO Gateway for NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)." + + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} + +1. Install the MinIO client. + + ```shell + $ docker pull minio/mc + ``` + +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. + + * Local deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + This example can be used for MinIO standalone or MinIO as a NAS gateway. + + * Clustered deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### 次のステップ + +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/ja-JP/content/admin/user-management/audited-actions.md b/translations/ja-JP/content/admin/user-management/audited-actions.md index f21212f704977..df39cc1fb1766 100644 --- a/translations/ja-JP/content/admin/user-management/audited-actions.md +++ b/translations/ja-JP/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### Team -| 名前 | 説明 | -| --------------:| --------------------------------- | -| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | -| `team.delete` | ユーザアカウントまたはリポジトリが Team から削除されました。 | -| `team.destroy` | Teamが削除されました。 | +| 名前 | 説明 | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### ユーザ -| 名前 | 説明 | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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` | 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` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `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` | サイトアドミンがユーザアカウント停止を解除しました。 | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [デプロイキー]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 2f769cf6fd1c0..070837a43b2b9 100644 --- a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,13 +4,18 @@ 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: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -メッセージの書式設定には Markdown を使用できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github/)」を参照してください。 +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ versions: {% endnote %} +メッセージの書式設定には Markdown を使用できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github/)」を参照してください。 + ### カスタムサインインメッセージの作成 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. [Sign in page] の下で [**Add message**] または [**Edit message**] をクリックします。 ![[Edit message] ボタン](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. [**Sign in message**] の下に、ユーザに見せたいメッセージを入力します。 ![サインインメッセージ](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. [**Sign in message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. 表示されたメッセージを確認します。 ![サインインメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### カスタムサインアウトメッセージを作成する @@ -37,12 +45,35 @@ versions: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. [Sign out page] の下で [**Add message**] または [**Edit message**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. [**Sign out message**] の下に、ユーザに見せたいメッセージを入力します。 ![サイン two_factor_auth_header メッセージ](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. [**Sign out message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. 表示されたメッセージを確認します。 ![サインアウトメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Creating a global announcement banner @@ -50,9 +81,8 @@ versions: You can set a global announcement banner to be displayed to all users at the top of every page. {% 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)." - +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)." {% else %} You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." @@ -62,9 +92,8 @@ You can also set an announcement banner in the administrative shell using a comm {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. [Sign out page] の下で [**Add message**] または [**Edit message**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", use the calendar drop-down menu, and select an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. [Sign in page] の下で [**Add message**] または [**Edit message**] をクリックします。 ![プレビューボタン](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. [**Save changes**] をクリックします。 ![[Edit message] ボタン](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md b/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md index ea678905057e6..181973fb8a071 100644 --- a/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 ##### パラメータ -| 名前 | 種類 | 説明 | -| --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **必須。** {% data variables.product.prodname_github_app %}に対して{% data variables.product.product_name %}から受け取ったクライアントID。 | -| `client_secret` | `string` | **必須。** {% data variables.product.prodname_github_app %}に対して{% data variables.product.product_name %}から受け取ったクライアントシークレット。 | -| `code` | `string` | **必須。** ステップ1でレスポンスとして受け取ったコード。 | -| `redirect_uri` | `string` | 認可の後にユーザが送られるアプリケーション中のURL。 | -| `state` | `string` | ステップ1で提供した推測できないランダムな文字列。 | +| 名前 | 種類 | 説明 | +| --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **必須。** {% data variables.product.prodname_oauth_app %}に対して{% data variables.product.product_name %}から受け取ったクライアントID。 | +| `client_secret` | `string` | **必須。** {% data variables.product.prodname_oauth_app %}に対して{% data variables.product.product_name %}から受け取ったクライアントシークレット。 | +| `code` | `string` | **必須。** ステップ1でレスポンスとして受け取ったコード。 | +| `redirect_uri` | `string` | 認可の後にユーザが送られるアプリケーション中のURL。 | +| `state` | `string` | ステップ1で提供した推測できないランダムな文字列。 | ##### レスポンス @@ -213,7 +213,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### デバイスフローのレート制限 -ユーザがブラウザ上で検証コードをサブミットする場合、アプリケーションごとに1時間に50回のサブミットというレート制限があります。 +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. リクエスト間で要求される最小の時間間隔（あるいは`interval`）内で複数のアクセストークンリクエスト（`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`）を発行すると、レート制限に達し、`slow_down`のエラーレスポンスが返されます。 `slow_down`エラーレスポンスは、最後の`interval`に5秒を追加します。 詳しい情報については[デバイスフローのエラー](#errors-for-the-device-flow)を参照してください。 diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md index f7be3190f7579..9fb0397865f7e 100644 --- a/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -78,7 +78,7 @@ versions: | [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | [Code scanning API](/rest/reference/code-scanning/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`ステータス`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} | `vulnerability_alerts` | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に対するセキュリティアラートについて](/articles/about-security-alerts-for-vulnerable-dependencies)」を参照。 `none`、`read` のいずれかです。{% endif %} | `Watch` | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。 | @@ -87,16 +87,16 @@ versions: | Webhook イベント名 | 必要な権限 | 説明 | | -------------------------------------------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| [`check_run`](/webhooks/event-payloads/#check_run) | `チェック` | {% data reusables.webhooks.check_run_short_desc %} -| [`check_suite`](/webhooks/event-payloads/#check_suite) | `チェック` | {% data reusables.webhooks.check_suite_short_desc %} -| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `コンテンツ` | {% data reusables.webhooks.commit_comment_short_desc %} +| [`check_run`](/webhooks/event-payloads/#check_run) | `checks` | {% data reusables.webhooks.check_run_short_desc %} +| [`check_suite`](/webhooks/event-payloads/#check_suite) | `checks` | {% data reusables.webhooks.check_suite_short_desc %} +| [`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %} | [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} -| [`create`](/webhooks/event-payloads/#create) | `コンテンツ` | {% data reusables.webhooks.create_short_desc %} -| [`delete`](/webhooks/event-payloads/#delete) | `コンテンツ` | {% data reusables.webhooks.delete_short_desc %} -| [`deployment`](/webhooks/event-payloads/#deployment) | `デプロイメント` | {% data reusables.webhooks.deployment_short_desc %} -| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `デプロイメント` | {% data reusables.webhooks.deployment_status_short_desc %} -| [`fork`](/webhooks/event-payloads/#fork) | `コンテンツ` | {% data reusables.webhooks.fork_short_desc %} -| [`gollum`](/webhooks/event-payloads/#gollum) | `コンテンツ` | {% data reusables.webhooks.gollum_short_desc %} +| [`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %} +| [`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %} +| [`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %} +| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %} +| [`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %} +| [`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %} | [`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} | [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} | [`label`](/webhooks/event-payloads/#label) | `メタデータ` | {% data reusables.webhooks.label_short_desc %} @@ -113,11 +113,11 @@ versions: | [`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} | [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} | [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -| [`push`](/webhooks/event-payloads/#push) | `コンテンツ` | {% data reusables.webhooks.push_short_desc %} -| [`release`](/webhooks/event-payloads/#release) | `コンテンツ` | {% data reusables.webhooks.release_short_desc %} +| [`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %} +| [`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %} | [`repository`](/webhooks/event-payloads/#repository) | `メタデータ` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} -| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `コンテンツ` | GitHub Action を使用するインテグレーターがカスタムイベントをトリガーできるようにします。{% endif %} -| [`status`](/webhooks/event-payloads/#status) | `ステータス` | {% data reusables.webhooks.status_short_desc %} +| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | GitHub Action を使用するインテグレーターがカスタムイベントをトリガーできるようにします。{% endif %} +| [`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} | [`Team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} | [`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} | [`Watch`](/webhooks/event-payloads/#watch) | `メタデータ` | {% data reusables.webhooks.watch_short_desc %} 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 a3743928e1ba7..e4012ee3929db 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 @@ -14,7 +14,7 @@ versions: このガイドでは、[Github App](/apps/) と [Checks API](/rest/reference/checks) について紹介します。Checks API は、テストを実行する継続的インテグレーション (CI) サーバーを構築するために使用します。 -CI とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの発生が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 開発者がコードの記述にばかり時間をとられ、エラーのデバッグやマージコンフリクトの解決にかける時間が少ないときに威力を発揮します。 🙌 +CI とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの発生が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 コードの記述により多くの時間をかけられるようになり、エラーのデバッグやマージコンフリクトの解決にかける時間が減るので、これは開発者にとって素晴らしいやり方です。 🙌 CI サーバーは、コードの文法チェッカー (スタイルフォーマットをチェックする)、セキュリティチェック、コード網羅率、その他のチェックといった CI テストをリポジトリの新しいコードコミットに対して実行するコードをホストします。 CI サーバーは、ステージングサーバーや本番サーバーにコードを構築しデプロイすることも可能です。 GitHub App で作成できる CI テストのタイプの例については、GitHub Marketplace で入手できる[継続的インテグレーションアプリケーション](https://github.com/marketplace/category/continuous-integration)を確認してください。 @@ -24,7 +24,7 @@ CI サーバーは、コードの文法チェッカー (スタイルフォーマ [Checks API](/rest/reference/checks) を使用すると、リポジトリでコミットされている各コードに対して自動的に実行される CI テストを設定できます。 Checks API は、プルリクエストの [**Checks**] タブにおいて、各チェックについての詳細情報をレポートします。 Checks API を使用すると、コードの特定の行に対して追加的な情報を含むアノテーションを作成できます。 アノテーションは [**Checks**] タブに表示されます。 プルリクエストの一部であるファイルに対してアノテーションを作成すると、そのアノテーションは [**Files changed**] タブにも表示されます。 -_チェックスイート_とは、 _チェック実行_ (個々の CI テスト) をグループ化したものです。 チェックスイートにもチェック実行にも_ステータス_が含まれており、GitHub のプルリクエストで表示できます。 ステータスを使用して、コードコミットがエラーを発生させるタイミングを決定できます。 これらのステータスを[保護されたブランチ](/rest/reference/repos#branches)で使用すると、プルリクエストを早まってマージすることを防げます。 詳細は「[ステータスチェック必須の有効化](/articles/enabling-required-status-checks/)」を参照してください。 +_チェックスイート_とは、 _チェック実行_ (個々の CI テスト) をグループ化したものです。 チェックスイートにもチェック実行にも_ステータス_が含まれており、GitHub のプルリクエストで表示できます。 ステータスを使用して、コードコミットがエラーを発生させるタイミングを決定できます。 これらのステータスを[保護されたブランチ](/rest/reference/repos#branches)で使用すると、プルリクエストを早まってマージすることを防げます。 See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. Checks API は、新しいコードがリポジトリにプッシュされるたびに、リポジトリにインストールされている全ての GitHub App に [`check_suite` webhook イベント](/webhooks/event-payloads/#check_suite)を送信します。 Checks API イベントの全てのアクションを受信するには、アプリケーションに `checks:write` 権限が必要です。 GitHub はデフォルトのフローを使ってリポジトリの新しいコードのコミットに `check_suite` イベントを自動的に作成しますが、[チェックスイートのためのリポジトリプリファレンスの更新](/rest/reference/checks#update-repository-preferences-for-check-suites)を行っても構いません。 デフォルトのフローは以下の通りです。 diff --git a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md index bbab98d9c1bf1..620d4b437f5f8 100644 --- a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### 利用できるスコープ -| 名前 | 説明 | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 名前 | 説明 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`(スコープなし)`** | パブリックな情報への読み取りのみのアクセスを許可します（パブリックなユーザのプロフィール情報、パブリックリポジトリの情報、Gist）。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | サイト管理者に[{% data variables.product.prodname_ghe_server %}の管理APIエンドポイント](/rest/reference/enterprise-admin)へのアクセスを許可します。{% endif %} -| **`repo`** | プライベート及びパブリックなリポジトリへの完全なアクセスを許可します。 これにはコード、コミットのステータス、リポジトリ及びOrganizationのプロジェクト、招待、コラボレータ、Teamのメンバーシップの追加、デプロイメントのステータス、パブリック及びプライベートのリポジトリとOrganizationのためのリポジトリwebhookが含まれます。 また、ユーザプロジェクトを管理する機能も許可します。 | -|  `repo:status` | パブリック及びプライベートのリポジトリのコミットステータスの読み書きアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにプライベートリポジトリのコミットステータスへのアクセスを許可したい場合のみです。 | -|  `repo_deployment` | パブリック及びプライベートのリポジトリに対する[デプロイメントステータス](/rest/reference/repos#deployments)へのアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにデプロイメントステータスへのアクセスを許可したい場合のみです。 | -|  `public_repo` | アクセスをパブリックリポジトリのみに制限します。 これには、コード、コミットステータス、リポジトリプロジェクト、コラボレータ、パブリックリポジトリ及びOrganizationのデプロイメントステータスへの読み書きアクセスが含まれます。 パブリックリポジトリにStarするためにも必要です。 | +| **`repo`** | プライベート及びパブリックなリポジトリへの完全なアクセスを許可します。 これにはコード、コミットのステータス、リポジトリ及びOrganizationのプロジェクト、招待、コラボレータ、Teamのメンバーシップの追加、デプロイメントのステータス、パブリック及びプライベートのリポジトリとOrganizationのためのリポジトリwebhookが含まれます。 また、ユーザプロジェクトを管理する機能も許可します。 | +|  `repo:status` | パブリック及びプライベートのリポジトリのコミットステータスの読み書きアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにプライベートリポジトリのコミットステータスへのアクセスを許可したい場合のみです。 | +|  `repo_deployment` | パブリック及びプライベートのリポジトリに対する[デプロイメントステータス](/rest/reference/repos#deployments)へのアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにデプロイメントステータスへのアクセスを許可したい場合のみです。 | +|  `public_repo` | アクセスをパブリックリポジトリのみに制限します。 これには、コード、コミットステータス、リポジトリプロジェクト、コラボレータ、パブリックリポジトリ及びOrganizationのデプロイメントステータスへの読み書きアクセスが含まれます。 パブリックリポジトリにStarするためにも必要です。 | |  `repo:invite` | リポジトリでのコラボレーションへの招待の承認／拒否を許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*招待へのアクセスをユーザあるいはサービスに許可する場合のみです。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | 許可:
      [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み書きアクセス。
      [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)中のセキュリティイベントへの読み書きアクセス。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み書きアクセスを許可します。{% endif %} -| **`admin:repo_hook`** | パブリック及びプライベートリポジトリのリポジトリフックへの読み書き、ping、削除アクセスを許可します。 `repo`及び`public_repo`スコープは、リポジトリフックを含むリポジトリへの完全なアクセスを許可します。 アクセスをリポジトリフックのみに限定するには、`admin:repo_hook`スコープを使ってください。 | -|  `write:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み書き及びpingアクセスを許可します。 | -|  `read:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み取り及びpingアクセスを許可します。 | -| **`admin:org`** | OrganizationとそのTeam、プロジェクト、メンバーシップを完全に管理できます。 | -|  `write:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み書きアクセス。 | -|  `read:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み取りのみのアクセス。 | -| **`admin:public_key`** | 公開鍵を完全に管理できます。 | -|  `write:public_key` | 公開鍵の作成、リスト、詳細の表示。 | -|  `read:public_key` | 公開鍵のリストと詳細の表示。 | -| **`admin:org_hook`** | Organizationフックへの読み書き、ping、削除アクセスを許可します。 **ノート:** OAuthトークンがこれらのアクションを行えるのは、OAuth Appが作成したOrganizationフックに対してのみです。 個人アクセストークンがこれらのアクションを行えるのは、ユーザが作成したOrganizationフックに対してのみです。 | -| **`gist`** | Gistへの書き込みアクセスを許可します。 | -| **`notifications`** | 許可するアクセス:
      * ユーザの通知に対する読み取りアクセス
      * スレッドへの既読アクセス
      * リポジトリへのWatch及びWatch解除のアクセス
      * スレッドのサブスクリプションに対する読み書き及び削除アクセス。 | -| **`user`** | プロフィール情報にのみ読み書きアクセスを許可します。 このスコープには`user:email`と`user:follow`が含まれることに注意してください。 | -|  `read:user` | ユーザのプロフィールデータへの読み取りアクセスを許可します。 | -|  `user:email` | ユーザのメールアドレスへの読み取りアクセスを許可します。 | -|  `user:follow` | 他のユーザのフォローあるいはフォロー解除のアクセスを許可します。 | -| **`delete_repo`** | 管理可能なリポジトリの削除アクセスを許可します。 | -| **`write:discussion`** | Teamのディスカッションの読み書きアクセスを許可します。 | +|  `security_events` | Grants:
      read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
      read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
      This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +| **`admin:repo_hook`** | パブリック及びプライベートリポジトリのリポジトリフックへの読み書き、ping、削除アクセスを許可します。 `repo`及び`public_repo`スコープは、リポジトリフックを含むリポジトリへの完全なアクセスを許可します。 アクセスをリポジトリフックのみに限定するには、`admin:repo_hook`スコープを使ってください。 | +|  `write:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み書き及びpingアクセスを許可します。 | +|  `read:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み取り及びpingアクセスを許可します。 | +| **`admin:org`** | OrganizationとそのTeam、プロジェクト、メンバーシップを完全に管理できます。 | +|  `write:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み書きアクセス。 | +|  `read:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み取りのみのアクセス。 | +| **`admin:public_key`** | 公開鍵を完全に管理できます。 | +|  `write:public_key` | 公開鍵の作成、リスト、詳細の表示。 | +|  `read:public_key` | 公開鍵のリストと詳細の表示。 | +| **`admin:org_hook`** | Organizationフックへの読み書き、ping、削除アクセスを許可します。 **ノート:** OAuthトークンがこれらのアクションを行えるのは、OAuth Appが作成したOrganizationフックに対してのみです。 個人アクセストークンがこれらのアクションを行えるのは、ユーザが作成したOrganizationフックに対してのみです。 | +| **`gist`** | Gistへの書き込みアクセスを許可します。 | +| **`notifications`** | 許可するアクセス:
      * ユーザの通知に対する読み取りアクセス
      * スレッドへの既読アクセス
      * リポジトリへのWatch及びWatch解除のアクセス
      * スレッドのサブスクリプションに対する読み書き及び削除アクセス。 | +| **`user`** | プロフィール情報にのみ読み書きアクセスを許可します。 このスコープには`user:email`と`user:follow`が含まれることに注意してください。 | +|  `read:user` | ユーザのプロフィールデータへの読み取りアクセスを許可します。 | +|  `user:email` | ユーザのメールアドレスへの読み取りアクセスを許可します。 | +|  `user:follow` | 他のユーザのフォローあるいはフォロー解除のアクセスを許可します。 | +| **`delete_repo`** | 管理可能なリポジトリの削除アクセスを許可します。 | +| **`write:discussion`** | Teamのディスカッションの読み書きアクセスを許可します。 | |  `read:discussion` | Teamのディスカッションの読み取りアクセスを許可します。{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | {% data variables.product.prodname_registry %}でのパッケージのアップロードあるいは公開のアクセスを許可します。 詳しい情報については「[パッケージの公開](/github/managing-packages-with-github-packages/publishing-a-package)」を参照してください。 | -| **`read:packages`** | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 詳しい情報については「[パッケージのインストール](/github/managing-packages-with-github-packages/installing-a-package)」を参照してください。 | +| **`write:packages`** | {% data variables.product.prodname_registry %}でのパッケージのアップロードあるいは公開のアクセスを許可します。 詳しい情報については「[パッケージの公開](/github/managing-packages-with-github-packages/publishing-a-package)」を参照してください。 | +| **`read:packages`** | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 詳しい情報については「[パッケージのインストール](/github/managing-packages-with-github-packages/installing-a-package)」を参照してください。 | | **`delete:packages`** | {% data variables.product.prodname_registry %}からのパッケージの削除アクセスを許可します。 詳しい情報については「[パッケージの削除](/github/managing-packages-with-github-packages/deleting-a-package)」を参照してください。{% endif %} -| **`admin:gpg_key`** | GPGキーを完全に管理できます。 | -|  `write:gpg_key` | GPGキーの作成、リスト、詳細の表示ができます。 | +| **`admin:gpg_key`** | GPGキーを完全に管理できます。 | +|  `write:gpg_key` | GPGキーの作成、リスト、詳細の表示ができます。 | |  `read:gpg_key` | GPGキーのリストと詳細の表示ができます。{% if currentVersion == "free-pro-team@latest" %} | **`workflow`** | {% data variables.product.prodname_actions %}のワークフローファイルの追加と更新機能を許可します。 同じリポジトリ内の他のブランチに同じファイル（パスと内容が同じ）が存在する場合、ワークフローファイルはこのスコープがなくてもコミットできます。 ワークフローファイルは異なるスコープのセットを持ちうる`GITHUB_TOKEN`を公開できます。詳細については https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token を参照してください。{% endif %} diff --git a/translations/ja-JP/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index a865527965332..720944379c4e2 100644 --- a/translations/ja-JP/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/ja-JP/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: リストの取引の表示 -intro: '{% data variables.product.prodname_marketplace %}の取引ページでは、{% data variables.product.prodname_marketplace %}リストのすべての取引をダウンロードしたり表示したりできます。 過去の日（24時間）、週、月、あるいは{% data variables.product.prodname_github_app %}がリストされた期間全体に対する取引を見ることができます。' +intro: '{% data variables.product.prodname_marketplace %}の取引ページでは、{% data variables.product.prodname_marketplace %}リストのすべての取引をダウンロードしたり表示したりできます。 You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/ja-JP/content/education/guides.md b/translations/ja-JP/content/education/guides.md index e4edf7fc06891..3511be37027a0 100644 --- a/translations/ja-JP/content/education/guides.md +++ b/translations/ja-JP/content/education/guides.md @@ -22,7 +22,7 @@ Administer a classroom, assign and review work from your students, and teach the - [Basics of setting up {% data variables.product.prodname_classroom %} ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) - [Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms) - [Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) -- [Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment) +- [グループ課題の作成](/education/manage-coursework-with-github-classroom/create-a-group-assignment) - [Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository) - [Leave feedback with pull requests](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests) - [Use autograding](/education/manage-coursework-with-github-classroom/use-autograding) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md index 3a678b866c1e0..2a6f08a529aae 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -10,19 +10,19 @@ redirect_from: ### MakeCode Arcadeについて -MakeCode Arcadeとは、ドラッグアンドドロップのブロックプログラミングとJavaScriptを使用してレトロなアーケードゲームを開発するためのオンライン統合開発環境 (IDE) です。 生徒はMakeCode Arcadeを使ってブラウザでコードを記述、編集、実行、テスト、デバッグできます。 オンラインIDEおよび{% data variables.product.prodname_classroom %}に関する詳しい情報については、「[{% data variables.product.prodname_classroom %}とオンラインIDEの統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)」を参照してください。 +MakeCode Arcadeとは、ドラッグアンドドロップのブロックプログラミングとJavaScriptを使用してレトロなアーケードゲームを開発するためのオンライン統合開発環境 (IDE) です。 学生はMakeCode Arcadeを使ってブラウザでコードを記述、編集、実行、テスト、デバッグできます。 オンラインIDEおよび{% data variables.product.prodname_classroom %}に関する詳しい情報については、「[{% data variables.product.prodname_classroom %}とオンラインIDEの統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)」を参照してください。 {% data reusables.classroom.readme-contains-button-for-online-ide %} -生徒がボタンをクリックして、初めてMakeCode Arcadeにアクセスする際は、{% data variables.product.product_name %}認証情報でMakeCode Arcadeにサインインする必要があります。 サインインすると、生徒はMakeCode Arcadeで完全に構成された、課題リポジトリのコードが含まれる開発環境にアクセスできます。 +学生がボタンをクリックして、初めてMakeCode Arcadeにアクセスする際は、{% data variables.product.product_name %}認証情報でMakeCode Arcadeにサインインする必要があります。 サインインすると、学生はMakeCode Arcadeで完全に構成された、課題リポジトリのコードが含まれる開発環境にアクセスできます。 MakeCode Arcadeにおける作業についての詳細は、[MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour)およびMakeCode Arcadeウェブサイトの[ドキュメント](https://arcade.makecode.com/docs)を参照してください。 -MakeCode Arcadeは、グループ課題のための複数人による編集をサポートしていません。 その代わり、生徒はブランチやプルリクエストのようなGitおよび{% data variables.product.product_name %}の機能でコラボレートできます。 +MakeCode Arcadeは、グループ課題のための複数人による編集をサポートしていません。 その代わり、学生はブランチやプルリクエストのようなGitおよび{% data variables.product.product_name %}の機能でコラボレートできます。 ### MakeCode Arcadeによる課題の提出について -デフォルトでは、MakeCode Arcadeは{% data variables.product.product_location %}の課題リポジトリにプッシュするよう設定されています。 MakeCode Arcadeで課題を進めた後、生徒は画面下部にある{% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %}ボタンで、変更を{% data variables.product.product_location %}にプッシュする必要があります。 +デフォルトでは、MakeCode Arcadeは{% data variables.product.product_location %}の課題リポジトリにプッシュするよう設定されています。 MakeCode Arcadeで課題を進めた後、学生は画面下部にある{% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %}ボタンで、変更を{% data variables.product.product_location %}にプッシュする必要があります。 ![MakeCode Arcadeのバージョン管理機能](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index f8c4b2924c504..d800a839de3ce 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -10,19 +10,19 @@ redirect_from: ### Repl.itについて -Repl.itは、複数の複数のプログラミング言語をサポートするオンライン統合開発環境 (IDE) です。 生徒はRepl.itを使ってブラウザでコードを記述、編集、実行、テスト、デバッグできます。 オンラインIDEおよび{% data variables.product.prodname_classroom %}に関する詳しい情報については、「[{% data variables.product.prodname_classroom %}とオンラインIDEの統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)」を参照してください。 +Repl.itは、複数の複数のプログラミング言語をサポートするオンライン統合開発環境 (IDE) です。 学生はRepl.itを使ってブラウザでコードを記述、編集、実行、テスト、デバッグできます。 オンラインIDEおよび{% data variables.product.prodname_classroom %}に関する詳しい情報については、「[{% data variables.product.prodname_classroom %}とオンラインIDEの統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)」を参照してください。 {% data reusables.classroom.readme-contains-button-for-online-ide %} -生徒がボタンをクリックして、初めてRepl.itにアクセスする際は、{% data variables.product.product_name %}認証情報でMakeCode Arcadeにサインインする必要があります。 サインインすると、生徒はRepl.itで完全に構成された、課題リポジトリのコードが含まれる開発環境にアクセスできます。 +学生がボタンをクリックして、初めてRepl.itにアクセスする際は、{% data variables.product.product_name %}認証情報でMakeCode Arcadeにサインインする必要があります。 サインインすると、学生はRepl.itで完全に構成された、課題リポジトリのコードが含まれる開発環境にアクセスできます。 Repl.itでの作業に関する詳しい情報については、[Repl.itクイックスタートガイド](https://docs.repl.it/misc/quick-start#the-repl-environment)を参照してください。 -グループ課題の場合、生徒はRepl.it Multiplayerを利用して共同作業を行うことができます。 詳しい情報については、[Repl.it Multiplayer](https://repl.it/site/multiplayer)のウェブサイトを参照してください。 +グループ課題の場合、学生はRepl.it Multiplayerを利用して共同作業を行うことができます。 詳しい情報については、[Repl.it Multiplayer](https://repl.it/site/multiplayer)のウェブサイトを参照してください。 ### Repl.itによる課題の提出について -デフォルトでは、Repl.itは{% data variables.product.product_location %}の課題リポジトリにプッシュするよう設定されています。 MakeCode Arcadeで課題を進めた後、生徒は左サイドバーのバージョン管理機能を使って、変更を{% data variables.product.product_location %}にプッシュする必要があります。 +デフォルトでは、Repl.itは{% data variables.product.product_location %}の課題リポジトリにプッシュするよう設定されています。 MakeCode Arcadeで課題を進めた後、学生は左サイドバーのバージョン管理機能を使って、変更を{% data variables.product.product_location %}にプッシュする必要があります。 ![Repl.itのバージョン管理機能](/assets/images/help/classroom/ide-replit-version-control-button.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 3a06dfafb01da..91066d7f24e3e 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -13,12 +13,12 @@ versions: {% data variables.product.prodname_classroom %}の用語に関する詳細については、「[用語集](/education/manage-coursework-with-github-classroom/glossary)」を参照してください。 1.       はじめに {% octicon "link-external" aria-label="The external link icon" %} -2. 生徒の名簿を追加する {% octicon "link-external" aria-label="The external link icon" %} +2. 学生の名簿を追加する {% octicon "link-external" aria-label="The external link icon" %} 3. 課題を作成する - {% data variables.product.prodname_dotcom %} リポジトリを使用して課題を作成する {% octicon "link-external" aria-label="The external link icon" %} - オンラインIDEにMicrosoft MakeCodeを使用して課題を作成する {% octicon "link-external" aria-label="The external link icon" %} - オンラインIDEにRepl.itを使用して課題を作成する {% octicon "link-external" aria-label="The external link icon" %} -4. 生徒が課題を仕上げる方法 {% octicon "link-external" aria-label="The external link icon" %} +4. 学生が課題を仕上げる方法 {% octicon "link-external" aria-label="The external link icon" %} 5. 教師が課題を確認する方法 {% octicon "link-external" aria-label="The external link icon" %} 6. グループ課題を作成する {% octicon "link-external" aria-label="The external link icon" %} 7. 開始するための次のステップ {% octicon "link-external" aria-label="The external link icon" %} diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md index 8d6866e2db25a..9365fa4607a54 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -1,50 +1,50 @@ --- title: 課題リポジトリのデフォルト設定の構成 shortTitle: 課題リポジトリのデフォルトの構成 -intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. -permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +intro: Probot Settings アプリケーションを使って、{% data variables.product.prodname_classroom %}で課題用に作成したリポジトリのデフォルト設定を構成できます。 +permissions: Organizationのオーナーは、Organizationに対し{% data variables.product.prodname_github_app %}をインストールすることで、課題リポジトリのデフォルト設定を構成できます。 versions: free-pro-team: '*' redirect_from: - /education/manage-coursework-with-github-classroom/probot-settings --- -### About configuration of defaults for assignment repositories +### 課題リポジトリのデフォルトの構成について -{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." +{% data variables.product.prodname_classroom %}は、課題を受ける各学生またはチームに属するリポジトリを作成します。 このリポジトリは、{% data variables.product.prodname_classroom %}で使用するOrganizationに属します。 課題リポジトリは空か、テンプレートリポジトリを使用できます。 詳しい情報については、「[テンプレートリポジトリからの課題の作成](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)」を参照してください。 {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} -With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. +Probot Settingsアプリケーションを使用すると、リポジトリの設定リストが含まれる、_.github/settings.yml_という名前のファイルをリポジトリ内に作成でき、その後、その設定をリポジトリに対して自動的に設定した{% data variables.product.prodname_github_app %}をOrganization用にインストールできます。 -You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. +{% data variables.product.prodname_classroom %}で課題に使用するテンプレートリポジトリには、_.github/settings.yml_を含めることができます。 個人またはチームが課題を受け入れると、{% data variables.product.prodname_classroom %}は課題リポジトリを作成し、Settingsアプリケーションは_.github/settings.yml_から自動的に設定を適用します。 -Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. +Probotは、{% data variables.product.product_name %}を自動化するための、プロジェクト、フレームワーク、および無料アプリケーションを集めたものです。 Probotアプリケーションは、新しいコミット、コメント、およびIssueの作成といったリポジトリのイベントをリッスンし、そのイベントに自動的に応答できます。 -For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." +詳しい情報については、[Probotのウェブサイト](https://probot.github.io)および[「Settings」アプリケーションのウェブサイト](https://probot.github.io/apps/settings/)を参照してください。 {% data variables.product.prodname_github_apps %}の詳細については、「[アプリケーションについて](/developers/apps/about-apps)」を参照してください。 -### Adding the Settings app to your organization +### SettingsアプリケーションをOrganizationに追加する -After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. +Probot SettingsアプリケーションをOrganizationに対してインストールした後、アプリケーションは_.github/settings.yml_ で定義した設定を、{% data variables.product.prodname_classroom %}が作成した新しい課題を含めてOrganizationのあらゆるリポジトリに適用します。 -1. Navigate to the [Settings app page](https://github.com/apps/settings). -1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) +1. [アプリケーションの設定](https://github.com/apps/settings)ページに移動します。 +1. [**Install**]をクリックし、{% data variables.product.prodname_classroom %}で使うOrganizationをクリックします。 Organizationが所有するすべてのリポジトリに対し、アプリケーションに完全なアクセスを与えてください。 ![Probot Settingsアプリケーションをインストールする](/assets/images/help/classroom/probot-settings.gif) -### Configuring default settings for an assignment repository +### 課題リポジトリのデフォルト設定を構成する -1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." +1. _.github/settings.yml_ファイルを含むテンプレートリポジトリを作成します。 設定の完全なリストについては、`probot/settings`リポジトリの[README](https://github.com/probot/settings#github-settings)を参照してください。 {% data variables.product.prodname_classroom %}の、スターターコードにテンプレートリポジトリを用いることに関する詳細については、「[テンプレートリポジトリから課題を作成する](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)」を参照してください。 {% warning %} - **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + **警告:** テンプレートリポジトリ用の_.github/settings.yml_ファイルでは、`collaborators`を定義しないでください。 {% data variables.product.prodname_classroom %}は、教師およびティーチングアシスタントに、課題リポジトリへのアクセス権を自動的に付与します。 {% endwarning %} -1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} +1. スターターコードとして_.github/settings.yml_を含んだテンプレートリポジトリを使用し、課題を作成します。 {% data reusables.classroom.for-more-information-about-assignment-creation %} -The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. +OrganizationのProbot Settingsアプリケーションは、{% data reusables.classroom.you-may-want-to-predefine-repository-settings %}が学生またはチーム用に作成したすべての課題リポジトリに対し、テンプレートリポジトリの_.github/settings.yml_で定義した設定を適用します。 ### 参考リンク -- [Probot apps](https://probot.github.io/apps/) -- [Probot documentation](https://probot.github.io/docs/) +- [Probotアプリケーション](https://probot.github.io/apps/) +- [Probotドキュメント](https://probot.github.io/docs/) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md index 16239d43de37f..ec1c5bad6a446 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -1,6 +1,6 @@ --- -title: Connect a learning management system to GitHub Classroom -intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +title: 学習管理システムをGitHub Classroomに接続する +intro: LTI準拠の学習管理システム (LMS) を{% data variables.product.prodname_classroom %}に接続するよう設定することで、クラスルームの名簿をインポートできます。 versions: free-pro-team: '*' redirect_from: @@ -12,127 +12,127 @@ redirect_from: - /education/manage-coursework-with-github-classroom/setup-moodle --- -### About configuration of your LMS +### LMSの設定について -You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. +学習管理システム (LMS) を{% data variables.product.prodname_classroom %}に接続でき、{% data variables.product.prodname_classroom %}はLMSから学生の名簿をインポートできます。 LMSを{% data variables.product.prodname_classroom %}に接続するには、LMSで{% data variables.product.prodname_classroom %}の構成認証情報を入力する必要があります。 ### 必要な環境 -To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." +LMSを{% data variables.product.prodname_classroom %}に接続するよう構成するには、まずクラスルームを作成する必要があります。 詳しい情報については、「[クラスルームを管理する](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)」を参照してください。 -### Supported LMSes +### サポートするLMS -{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. +{% data variables.product.prodname_classroom %}は、Learning Tools Interoperability (LTI) 規格を実装するLMSからの、名簿データのインポートをサポートしています。 -- LTI version 1.0 and/or 1.1 +- LTIバージョン1.0および1.1 - LTI Names and Roles Provisioning 1.X -Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. +LTIは、情報の安全性と機密性を保つために役立ちます。 LTIは業界標準のプロトコルであり、GitHub ClassroomによるLTIの利用は、教育管理システム (IMS) グローバル・ラーニング・コンソーシアムにより認定されています。 詳しい情報については、IMSグローバル・ラーニング・コンソーシアムのウェブサイト上にある[Learning Tools Interoperability (学習ツールの相互運用性) ](https://www.imsglobal.org/activity/learning-tools-interoperability)および[About IMS Global Learning Consortium (IMSグローバル・ラーニング・コンソーシアムについて) ](http://www.imsglobal.org/aboutims.html)を参照してください。 -{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. +{% data variables.product.company_short %}は、以下のLMSから{% data variables.product.prodname_classroom %}への名簿のインポートを確認しています。 - Canvas - Google Classroom - Moodle - Sakai -Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace +現在のところ、{% data variables.product.prodname_classroom %}はBlackboardおよびBrightspaceからの名簿のインポートはサポートしていません。 -### Generating configuration credentials for your classroom +### クラスルームの構成認証情報を生成する {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-students %} -1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. - - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." - - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." -1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) -1. Read about connecting your LMS, then click **Connect to _LMS_**. -1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) +1. クラスルームに既に名簿がある場合は、その名簿を更新するか、その名簿を削除して新しい名簿を作成できます。 + - 名簿の削除や作成に関する詳細については、「[クラスルームの名簿を削除する](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)」および「[クラスルームの名簿を作成する](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)」を参照してください。 + - 名簿の更新に関する詳細については、「[クラスルームの名簿に学生を追加する](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)」を参照してください。 +1. LMSのリストの中から、お使いのLMSをクリックします。 お使いのLMSがサポートされていない場合、[**Other LMS**] をクリックします。 ![LMSのリスト](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. LMSの接続について読み、[**Connect to _LMS_**] をクリックします。 +1. クラスルームへの接続に用いる、[Consumer Key]、[Shared Secret]、および [Launch URL] をコピーします。 ![認証情報のコピー](/assets/images/help/classroom/classroom-copy-credentials.png) -### Configuring a generic LMS +### 一般的なLMSを設定する -You must configure the privacy settings for your LMS to allow external tools to receive roster information. +外部ツールが名簿情報を受信できるよう、LMSのプライバシー設定を行う必要があります。 -1. Navigate to your LMS. -1. Configure an external tool. -1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. +1. お使いのLMSに移動します。 +1. 外部ツールを設定します。 +1. {% data variables.product.prodname_classroom %}で生成された構成認証情報を入力します。 - Consumer key - Shared secret - - Launch URL (sometimes called "tool URL" or similar) + - Launch URL (「ツールURL」などと呼ばれることもあります) -### Configuring Canvas +### Canvasを設定する -You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). +{% data variables.product.prodname_classroom %}をCanvasの外部アプリケーションとして設定し、クラスルームに名簿データをインポートできます。 Canvasに関する詳細は、[Canvasのウェブサイト](https://www.instructure.com/canvas/)を参照してください。 -1. Sign into [Canvas](https://www.instructure.com/canvas/#login). -1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. [Canvas](https://www.instructure.com/canvas/#login)にサインインします。 +1. {% data variables.product.prodname_classroom %}と連携するCanvasのコースを選択します。 1. 左のサイドバーで、**Settings（設定）**をクリックしてください。 -1. Click the **Apps** tab. -1. Click **View app configurations**. -1. Click **+App**. -1. Select the **Configuration Type** drop-down menu, and click **By URL**. -1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." - - | Field in Canvas app configuration | Value or setting | - |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | - | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} - | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} - | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | - | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} +1. [**Apps**] タブをクリックします。 +1. [**View app configurations**] をクリックします。 +1. [**+App**] をクリックします。 +1. [**Configuration Type**] ドロップダウンメニューで、[**By URL**] をクリックします。 +1. {% data variables.product.prodname_classroom %}からコピーした構成認証情報を貼り付けます。 詳しい情報については、「[クラスルームの構成認証情報を生成する](#generating-configuration-credentials-for-your-classroom)」を参照してください。 + + | Canvasアプリケーション構成のフィールド | 値または設定 | + |:------------------------------------------------------------------------- |:--------------------------------------------------------------- | + | **Consumer Key** | {% data variables.product.prodname_classroom %}からのConsumer key | + | **Shared Secret** | {% data variables.product.prodname_classroom %}からのShared secret | + | **Allow this tool to access the IMS Names and Role Provisioning Service** | 有効 | + | **Configuration URL** | {% data variables.product.prodname_classroom %}からのLaunch URL | {% note %} - **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + **注釈**: [Allow this tool to access the IMS Names and Role Provisioning Service] というラベルのチェックボックスがCanvasで表示されていない場合、Canvasの管理者がCanvasサポートに連絡し、お使いのCanvasアカウントでメンバーシップサービス設定を有効化する必要があります。 この機能を有効化しないと、Canvasから名簿を同期できません。 詳しい情報については、Canvasウェブサイトの[How do I contact Canvas Support? (Canvasサポートに連絡する方法)](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) を参照してください。 {% endnote %} 1. **Submit（サブミット）**をクリックしてください。 -1. In the left sidebar, click **Home**. -1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. - -### Configuring Moodle - -You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). - -You must be using Moodle version 3.0 or greater. - -1. Sign into [Moodle](https://moodle.org/login/index.php). -1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. -1. Click **Turn editing on**. -1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. -1. Choose **External tool** and click **Add**. -1. In the "Activity name" field, type "GitHub Classroom". -1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. -1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." - - | Field in Moodle app configuration | Value or setting | - |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

      **Note**: You can use any name, but we suggest this value for clarity. | - | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} - | **LTI version** | LTI 1.0/1.1 | - | **Default launch container** | New window | - | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} - | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} - -1. Scroll to and click **Services**. -1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. -1. Scroll to and click **Privacy**. -1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. 左のサイドバーで [**Home**] をクリックします。 +1. 左のサイドバーで [**GitHub Classroom**] をクリックし、Canvasが確認メールを送信するようにします。 メールの指示に従い、{% data variables.product.prodname_classroom %}との連携を完了します。 + +### Moodleを設定する + +{% data variables.product.prodname_classroom %}をMoodleのアクティビティとして設定し、クラスルームに名簿データをインポートできます。 Moodleに関する詳細は、[Moodleのウェブサイト](https://moodle.org)を参照してください。 + +Moodleのバージョンは3.0以上である必要があります。 + +1. [Moodle](https://moodle.org/login/index.php)にサインインします。 +1. {% data variables.product.prodname_classroom %}と連携するMoodleのコースを選択します。 +1. [**Turn editing on**] をクリックします。 +1. Moodleで{% data variables.product.prodname_classroom %}を利用するところで、[**Add an activity or resource**] をクリックします。 +1. [**External tool**] を選択し、[**Add**] をクリックします。 +1. [Activity name] フィールドに、「GitHub Classroom」と入力します。 +1. [**Preconfigured tool**] フィールドで、ドロップダウンメニューの右にある [**+**] をクリックします。 +1. [External tool configuration] の下に、{% data variables.product.prodname_classroom %} からコピーしたした構成認証情報を貼り付けます。 詳しい情報については、「[クラスルームの構成認証情報を生成する](#generating-configuration-credentials-for-your-classroom)」を参照してください。 + + | Moodleアプリケーション設定のフィールド | 値または設定 | + |:---------------------------- |:--------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _あなたのクラスルーム名_

      **注釈**: 任意の名前を設定できますが、わかりやすいよう、この値をお勧めします。 | + | **Tool URL** | {% data variables.product.prodname_classroom %}からのLaunch URL | + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | 新規ウィンドウ | + | **Consumer key** | {% data variables.product.prodname_classroom %}からのConsumer key | + | **Shared secret** | {% data variables.product.prodname_classroom %}からのShared secret | + +1. [**Services**] までスクロールしてクリックします。 +1. [IMS LTI Names and Role Provisioning] の右にあるドロップダウンメニューを選択し、[**Use this service to retrieve members' information as per privacy settings**] をクリックします。 +1. [**Privacy**] までスクロールしてクリックします。 +1. [**Share launcher's name with tool**] と [**Share launcher's email with tool**] の右にあるドロップダウンメニューをそれぞれ選択し、[**Always**] をクリックします。 1. ページの下部で**Save changes（変更の保存）**をクリックしてください。 -1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. -1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. -1. At the bottom of the page, click **Save and return to course**. -1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. +1. [**Preconfigure tool**] メニューで、[**GitHub Classroom - _あなたのクラスルーム名_**] をクリックします。 +1. [Common module settings] で、[Availability] の右にあるドロップダウンメニューを選択し、[**Hide from students**] をクリックします。 +1. ページの下部で、[**Save and return to course**] をクリックします +1. {% data variables.product.prodname_classroom %} を表示したい場所に移動し、{% data variables.product.prodname_classroom %}アクティビティをクリックします。 -### Importing a roster from your LMS +### LMSから名簿をインポートする -For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." +LMSから{% data variables.product.prodname_classroom %}への名簿のインポートに関する詳細については、「[クラスルームの管理](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)」を参照してください。 -### Disconnecting your LMS +### LMSを切断する {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) -1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) +1. [Connect to a learning management system (LMS)] の下にある、[**Connection Settings**] をクリックします。 ![クラスルーム設定の [Connection settings]](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. [Delete Connection to your learning management system] の下にある、[**Disconnect from your learning management system**] をクリックします。 ![クラスルームへの接続設定にある [Disconnect from your learning management system] ボタン](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index abbd937a0bf29..fdb54de2a6649 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -1,94 +1,94 @@ --- -title: Create a group assignment -intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +title: グループ課題の作成 +intro: 'コースに参加している学生のチームのために、共同課題を作成できます。' versions: free-pro-team: '*' redirect_from: - /education/manage-coursework-with-github-classroom/create-group-assignments --- -### About group assignments +### グループ課題について -{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. +{% data reusables.classroom.assignments-group-definition %}学生は、プロフェッショナルな開発者チームと同じように、共有リポジトリでグループ課題に協力して取り組むことができます。 -When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. +グループ課題を受け入れた学生は、新しいTeamを作成するか、既存のTeamに参加できます。 {% data variables.product.prodname_classroom %}は、課題のためのTeamをセットとして保存します。 課題を作成する際、特定の課題に対するTeamのセットに名前を付けることができます。また、後の課題でTeamのセットを再利用できます。 {% data reusables.classroom.classroom-creates-group-repositories %} {% data reusables.classroom.about-assignments %} -You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. 詳細は「[Team について](/github/setting-up-and-managing-organizations-and-teams/about-teams)」を参照してください。 +1つの課題に取り組むチームの数と、各Teamのメンバーの数を決めることができます。 学生が課題ために作成する各グループは、{% data variables.product.product_name %}のOrganization内のTeamです。 Teamの可視性はシークレットとなります。 {% data variables.product.product_name %}上で作成したTeamは、{% data variables.product.prodname_classroom %}では表示されません。 詳細は「[Team について](/github/setting-up-and-managing-organizations-and-teams/about-teams)」を参照してください。 -For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +グループ課題作成の方法を説明する動画については、「[{% data variables.product.prodname_classroom %}の設定の基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」を参照してください。 ### 必要な環境 {% data reusables.classroom.assignments-classroom-prerequisite %} -### Creating an assignment +### 課題を作成する {% data reusables.classroom.assignments-guide-create-the-assignment %} -### Setting up the basics for an assignment +### 課題の基本情報をセットアップする -Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. +課題に名前を付け、期限を設定するか、Teamを定義するかを決定し、課題リポジトリの可視性を選択します。 -- [Naming an assignment](#naming-an-assignment) -- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) -- [Choosing an assignment type](#choosing-an-assignment-type) -- [Defining teams for an assignment](#defining-teams-for-an-assignment) -- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) +- [課題に名前を付ける](#naming-an-assignment) +- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment) +- [課題のタイプを選択する](#choosing-an-assignment-type) +- [課題のTeamを定義する](#defining-teams-for-an-assignment) +- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories) -#### Naming an assignment +#### 課題に名前を付ける -For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. +グループ課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスとTeamの名前から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に「assignment-1」と名付け、{% data variables.product.product_name %}のチーム名が「student-team」である場合、そのTeamのメンバーの課題リポジトリ名は「`assignment-1-student-team`」となります。 {% data reusables.classroom.assignments-type-a-title %} -#### Assigning a deadline for an assignment +#### 課題に期限を設定する {% data reusables.classroom.assignments-guide-assign-a-deadline %} -#### Choosing an assignment type +#### 課題のタイプを選択する -Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." +[Individual or group assignment] の下で、ドロップダウンメニューを選択し、[**Group assignment**] をクリックします。 課題の作成後は、課題タイプを変更できません。 個人課題を作成する場合は、「[個人課題の作成](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)」を参照してください。 -#### Defining teams for an assignment +#### 課題のTeamを定義する -If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. +すでにクラスルームに対してグループ課題を作成している場合は、新しい課題にTeamのセットを再利用できます。 学生が課題用に作成したTeamで新しいセットを作成するには、そのセットの名前を入力します。 必要に応じて、Teamメンバーと合計チーム数の上限を入力してください。 {% tip %} **ヒント**: -- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. +- セットの名前には、Teamのセットについの情報を含めることをお勧めします。 たとえば、1つの課題用にTeamのセットを使う場合は、その課題にちなんだ名前を付けます。 学期またはコースを通じてセットを再利用する場合は、学期またはコースにちなんだ名前を付けます。 -- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. +- 特定のTeamに学生を割り当てる場合は、学生にTeamの名前を伝え、メンバーのリストを提供します。 {% endtip %} ![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) -#### Choosing a visibility for assignment repositories +#### 課題リポジトリの可視性を選択する {% data reusables.classroom.assignments-guide-choose-visibility %} {% data reusables.classroom.assignments-guide-click-continue-after-basics %} -### Adding starter code and configuring a development environment +### スターターコードを追加し、開発環境を構成する {% data reusables.classroom.assignments-guide-intro-for-environment %} -- [Choosing a template repository](#choosing-a-template-repository) -- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) +- [テンプレートリポジトリを作成する](#choosing-a-template-repository) +- [オンライン統合開発環境 (IDE) を選択する](#choosing-an-online-integrated-development-environment-ide) -#### Choosing a template repository +#### テンプレートリポジトリを作成する -By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." +デフォルトでは、新しい課題では学生が作成した各Teamに対し、空のリポジトリが作成されます。 {% data reusables.classroom.you-can-choose-a-template-repository %}テンプレートリポジトリに関する詳しい情報については、「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」を参照してください。 {% data reusables.classroom.assignments-guide-choose-template-repository %} -#### Choosing an online integrated development environment (IDE) +#### オンライン統合開発環境 (IDE) を選択する {% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 660c1da533dc6..2fcd6b76a4ca0 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -22,55 +22,55 @@ For a video demonstration of the creation of an individual assignment, see "[Bas {% data reusables.classroom.assignments-classroom-prerequisite %} -### Creating an assignment +### 課題を作成する {% data reusables.classroom.assignments-guide-create-the-assignment %} -### Setting up the basics for an assignment +### 課題の基本情報をセットアップする Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. -- [Naming an assignment](#naming-an-assignment) -- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) -- [Choosing an assignment type](#choosing-an-assignment-type) -- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) +- [課題に名前を付ける](#naming-an-assignment) +- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment) +- [課題のタイプを選択する](#choosing-an-assignment-type) +- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories) -#### Naming an assignment +#### 課題に名前を付ける -For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. {% data reusables.classroom.assignments-type-a-title %} -#### Assigning a deadline for an assignment +#### 課題に期限を設定する {% data reusables.classroom.assignments-guide-assign-a-deadline %} -#### Choosing an assignment type +#### 課題のタイプを選択する -Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. 課題の作成後は、課題タイプを変更できません。 If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." -#### Choosing a visibility for assignment repositories +#### 課題リポジトリの可視性を選択する {% data reusables.classroom.assignments-guide-choose-visibility %} {% data reusables.classroom.assignments-guide-click-continue-after-basics %} -### Adding starter code and configuring a development environment +### スターターコードを追加し、開発環境を構成する {% data reusables.classroom.assignments-guide-intro-for-environment %} -- [Choosing a template repository](#choosing-a-template-repository) -- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) +- [テンプレートリポジトリを作成する](#choosing-a-template-repository) +- [オンライン統合開発環境 (IDE) を選択する](#choosing-an-online-integrated-development-environment-ide) -#### Choosing a template repository +#### テンプレートリポジトリを作成する -By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}テンプレートリポジトリに関する詳しい情報については、「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」を参照してください。 {% data reusables.classroom.assignments-guide-choose-template-repository %} {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -#### Choosing an online integrated development environment (IDE) +#### オンライン統合開発環境 (IDE) を選択する {% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md index bca1150346077..eb57bcdc1eac5 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -1,6 +1,6 @@ --- -title: Learn with GitHub Classroom -intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +title: GitHub Classroomで学ぶ +intro: '{% data variables.product.prodname_classroom %} の授業に参加し、教師からの評価を見ることができます。' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index bf6b8dcc5b5ff..ac7bcbb9935f5 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ You can archive a classroom that you no longer use on {% data variables.product. {% data reusables.classroom.click-settings %} 1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **警告を読みます**。 -1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md index 73369d7f6e002..cccdc2112604e 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -43,3 +43,7 @@ versions: {% data reusables.dependabot.supported-package-managers %} リポジトリですでに依存関係管理にインテグレーションを使用している場合は、{% data variables.product.prodname_dependabot %} を有効にする前にそれを無効にする必要があります。 詳しい情報については、「[インテグレーションについて](/github/customizing-your-github-workflow/about-integrations)」を参照してください。 + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。 diff --git a/translations/ja-JP/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/ja-JP/content/github/administering-a-repository/about-merge-methods-on-github.md index e58c34ecdbfa0..7023d57c18ff0 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 詳しい情報については「[直線状のコミット履歴を必須とする](/github/administering-a-repository/requiring-a-linear-commit-history)」を参照してください。{% endif %} +デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### マージコミットのsquash diff --git a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md index 0bc422b92998a..d864e219caefd 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,142 @@ --- title: 保護されたブランチについて -intro: '保護されたブランチは、リポジトリのコラボレーターが回復不能な変更をブランチに行えないようにしてくれます。 保護されたブランチを有効にすると、ステータスチェック必須やレビュー必須といった他のオプションのチェックや必須事項を有効にすることもできるようになります。' +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### 保護されたブランチについて +### About branch protection rules -{% data reusables.pull_requests.about-protected-branches %} プルリクエストのリポジトリへのマージ方法に制限を適用することができます。 +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -リポジトリのオーナーおよびリポジトリの管理権限を持つ人は、コラボレーターがリポジトリでブランチをマージする前に特定のワークフローや必須事項を強制できます。そのためには保護されたブランチのルールを作成します。 +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -{% data reusables.repositories.branch-rules-example %}詳しい情報については[保護されたブランチの設定](/articles/configuring-protected-branches/)を参照してください。 +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -### 保護されたブランチのルールの優先順位付け +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [署名済みコミットの必須化](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. ベースブランチに関する詳しい情報については「[プルリクエストについて](/articles/about-pull-requests)」を参照してください。 + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. 詳しい情報については[プルリクエストレビューの却下](/articles/dismissing-a-pull-request-review)を参照してください。 + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +必須ステータスチェックにより、コラボレータが保護されたブランチに変更を加える前に、すべての必須 CI テストにパスしていることが保証されます。 詳細は「[保護されたブランチを設定する](/articles/configuring-protected-branches/)」および「[必須ステータスチェックを有効にする](/articles/enabling-required-status-checks)」を参照してください。 詳しい情報については、「[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)」を参照してください。 + +ステータスチェック必須を有効にする前に、ステータス API を使用するようにリポジトリを設定する必要があります。 For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. 必須ステータスチェックをパスしたら、コミットを別のブランチにプッシュしてから、マージするか、保護されたブランチに直接プッシュする必要があります。 + +{% note %} + +**注釈:** リポジトリへの書き込み権限があるユーザまたはインテグレーションなら誰でも、リポジトリのステータスチェックを任意のステータスに設定できます。 {% data variables.product.company_short %} は、チェックの作者が、特定の名前でチェックを作成したり、既存のステータスを変更したりする権限を持っているかを確認しません。 プルリクエストをマージする前に、マージボックスにリストされている各ステータスの作者が想定された人物であることを確認する必要があります。 + +{% endnote %} + +必須ステータスチェックのタイプは、\[loose\] (寛容)、\[strict\] (厳格) のいずれかに設定できます。 The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| 必須ステータスチェックのタイプ | 設定 | マージの要件 | 留意点 | +| --------------- | --------------------------------------------------------------------------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| **Strict** | [**Require branches to be up-to-date before merging**] チェックボックスにチェックする | マージ前、ブランチは、base ブランチとの関係で**最新でなければならない**。 | これは、必須ステータスチェックのデフォルト動作です。 他のコラボレーターが、保護された base ブランチにプルリクエストをマージした後に、あなたは head ブランチをアップデートする必要が出てくる可能性があるため、追加のビルドが必要になるかもしれません。 | +| **Loose** | [**Require branches to be up-to-date before merging**] チェックボックスにチェック**しない** | マージ前、ブランチは base ブランチとの関係で**最新でなくてもよい**。 | 他のコラボレーターがプルリクエストをマージした後に head ブランチをアップデートする必要はないことから、必要となるビルドは少なくなります。 base ブランチと競合する変更がある場合、ブランチをマージした後のステータスチェックは失敗する可能性があります。 | +| **無効** | [**Require status checks to pass before merging**] チェックボックスにチェック**しない** | ブランチのマージについての制限はない | 必須ステータスチェックが有効化されていない場合、base ブランチにあわせてアップデートされているかどうかに関わらず、コラボレーターはいつでもブランチをマージできます。 このことで、変更の競合が発生する可能性が高まります。 | + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### 署名済みコミットの必須化 + +When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. 詳細については、「[コミット署名の検証について](/articles/about-commit-signature-verification)」を参照してください。 + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +コミットが署名および検証されている場合は、いつでもローカルコミットをブランチにプッシュできます。 {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. 詳しい情報については、「[プルリクエストをローカルでチェック アウトする](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. つまり、保護されたブランチにマージされたプルリクエストは、squash マージまたはリベースマージを使用する必要があります。 A strictly linear commit history can help teams reverse changes more easily. マージ方法に関する詳しい情報については「[プルリクエストマージについて](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)」を参照してください。 + +直線状のコミット履歴をリクエストする前に、リポジトリで squash マージまたはリベースマージを許可する必要があります。 詳しい情報については、「[プルリクエストマージを設定する](/github/administering-a-repository/configuring-pull-request-merges)」を参照してください。 + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using +{% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. + +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. + +#### Allow force pushes -リポジトリが同じブランチに影響する複数の保護されたブランチのルールを持っているなら、特定のブランチ名を含むルールがもっとも高い優先順位を持ちます。 同じ特定のブランチ名を参照する保護されたブランチのルールが複数あるなら、最初に作成されたブランチルールが高い優先順位を持ちます。 +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. 保護されたブランチのフォースプッシュを有効にすると、少なくともリポジトリへの書き込み権限を持つユーザは、管理者権限を持つブランチを含め、ブランチをフォースプッシュできます。 -`*`、`?`、`]`などの特殊文字を含む保護されたブランチのルールは、作成された順序で適用されるので、これらの文字を持つ古いルールが高い優先順位を持ちます。 +フォースプッシュを有効化しても、他のブランチ保護ルールは上書きされません。 たとえば、ブランチに直線状のコミット履歴が必要な場合、そのブランチにマージコミットをフォースプッシュすることはできません。 -### ブランチの保護の設定 +{% 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. 詳しい情報については、「[ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)」を参照してください。 -リポジトリにブランチ保護ルールを作成すると、コラボレータは保護されたブランチに強制的にプッシュしたり、デフォルトでブランチを削除{% if currentVersion == "free-pro-team@latest" %}したりすることはできません{% endif %}。 他のブランチ保護設定を有効にすることができます。 詳細については、「[プルリクエストのマージ可能性を定義](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)」を参照してください。 +サイト管理者がデフォルトブランチへのフォースプッシュのみをブロックしている場合、他の保護されたブランチに対してフォースプッシュを有効にできます。{% endif %} -### 参考リンク +#### Allow deletions -- [ステータスチェック必須について](/articles/about-required-status-checks) -- [プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests) -- 「[必須のコミット署名について](/articles/about-required-commit-signing)」 +デフォルトでは、保護されたブランチは削除できません。 When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/ja-JP/content/github/administering-a-repository/about-releases.md b/translations/ja-JP/content/github/administering-a-repository/about-releases.md index 55991292e1bf5..229c335395459 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-releases.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-releases.md @@ -25,7 +25,7 @@ versions: リポジトリへの読み取りアクセス権を持つ人はリリースを表示および比較できますが、リリースの管理はリポジトリへの書き込み権限を持つ人のみができます。 詳細は「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} リポジトリへの管理者権限を持つユーザは、 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) オブジェクトを {% data variables.product.product_name %} がリリースごとに作成する ZIP ファイルと tarball に含めるかどうかを選択できます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 {% endif %} diff --git a/translations/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 fe17372460888..d7f50ef87c409 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + プロジェクトを外部サービスと通信させる場合、認証にトークンまたは秘密鍵を使用できます。 トークンや秘密鍵は、サービスプロバイダが発行できるシークレットです。 リポジトリにシークレットをチェックインする場合、リポジトリへの読み取りアクセスを持つすべてのユーザがシークレットを使用して、自分の権限で外部サービスにアクセスできます。 シークレットは、プロジェクトのリポジトリの外の、安全な専用の場所に保存することをお勧めします。 +Service providers can partner with -誰かが {% data variables.product.company_short %} パートナーのシークレットをパブリックまたはプライベートリポジトリにチェックインすると、{% data variables.product.prodname_secret_scanning %} がシークレットを検出し、リークの影響を軽減することができます。 +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} -サービスプロバイダは {% data variables.product.company_short %} と提携して、スキャンのためのシークレットフォーマットを提供することができます。 詳しい情報については、「[シークレットスキャニング](/partnerships/secret-scanning)」を参照してください。 +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### パブリックリポジトリの {% data variables.product.prodname_secret_scanning %} について - {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)." +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. パブリックリポジトリにプッシュすると、{% data variables.product.product_name %} がコミットの内容をスキャンしてシークレットを探します。 プライベートリポジトリをパブリックに切り替えると、{% data variables.product.product_name %} はリポジトリ全体をスキャンしてシークレットを探します。 -パブリックリポジトリにプッシュすると、{% data variables.product.product_name %} がコミットの内容をスキャンしてシークレットを探します。 プライベートリポジトリをパブリックに切り替えると、{% data variables.product.product_name %} はリポジトリ全体をスキャンしてシークレットを探します。 - -{% data variables.product.prodname_secret_scanning %} が認証情報一式を検出すると、弊社はそのシークレットを発行したサービスプロバイダに通知します。 サービスプロバイダは認証情報を検証し、シークレットを取り消すか、新しいシークレットを発行するか、または直接連絡する必要があるかを決定します。これは、ユーザまたはサービスプロバイダに関連するリスクに依存します。 +{% data variables.product.prodname_secret_scanning %} が認証情報一式を検出すると、弊社はそのシークレットを発行したサービスプロバイダに通知します。 サービスプロバイダは認証情報を検証し、シークレットを取り消すか、新しいシークレットを発行するか、または直接連絡する必要があるかを決定します。これは、ユーザまたはサービスプロバイダに関連するリスクに依存します。 For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." 現在 {% data variables.product.product_name %} は、パブリックリポジトリをスキャンして、次のサービスプロバイダが発行したシークレットを探します。 -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### プライベートリポジトリの {% data variables.product.prodname_secret_scanning %} について +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for private repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization. {% data variables.product.prodname_secret_scanning_caps %} is not available for user account-owned private repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} -{% data variables.product.prodname_secret_scanning %} が有効化されているプライベートリポジトリにコミットをプッシュすると、{% data variables.product.product_name %} はコミットの内容をスキャンしてシークレットを探します。 +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." -{% data variables.product.prodname_secret_scanning %} がプライベートリポジトリでシークレットを検出すると、{% data variables.product.prodname_dotcom %} はアラートを送信します。 +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. + +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. - {% data variables.product.prodname_dotcom %} は、リポジトリ管理者と Organizationのオーナーにメールアラートを送信します。 - {% data variables.product.prodname_dotcom %} は、リポジトリにアラートを表示します。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。 -Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." - -To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." - -現在 {% data variables.product.product_name %} は、プライベートリポジトリをスキャンして、次のサービスプロバイダが発行したシークレットを探します。 - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} @@ -128,4 +71,4 @@ To monitor results from {% data variables.product.prodname_secret_scanning %} ac ### 参考リンク - 「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository)」 -- [アカウントとデータをセキュアに保つ](/github/authenticating-to-github/keeping-your-account-and-data-secure) +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md index 215aaa2b6cd4a..17fee43a33a5c 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md @@ -3,6 +3,7 @@ title: リポジトリの保護について intro: '{% data variables.product.product_name %} には、リポジトリを安全に保つために役立つさまざまな方法があります。' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### リポジトリの保護設定をする @@ -13,6 +14,7 @@ versions: {% data variables.product.prodname_dotcom %} には、コードを安全に保つために役立つセキュリティ機能が追加されています。 これらは、リポジトリの [**セキュリティ**] タブにあります。 +{% if currentVersion == "free-pro-team@latest" %} - **セキュリティポリシー** リポジトリで見つけたセキュリティの脆弱性を内密に報告しやすくします。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)」を参照してください。 @@ -24,18 +26,32 @@ versions: - **{% data variables.product.prodname_dependabot_alerts %} and security updates** セキュリティの脆弱性を含むことを把握している依存関係に関するアラートを表示し、プルリクエストを自動的に生成してこれらの依存関係を更新するかどうかを選択します。 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)." + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **{% data variables.product.prodname_dependabot %} version updates** +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. 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 + {% endif %} - 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. 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_code_scanning_capc %} アラート** 新しいコードまたは変更されたコードのセキュリティの脆弱性とコーディングエラーを自動的に検出します。 潜在的な問題が強調表示され、あわせて詳細情報も確認できるため、デフォルトのブランチにマージする前にコードを修正できます。 詳しい情報については、「[コードスキャニングについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。 - **検出されたシークレット** +View any secrets that - {% data variables.product.prodname_dotcom %} がコードで検出したシークレットが表示されます。 リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 + {% data variables.product.prodname_dotcom %} has found in your code. リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 + {% endif %} ### 依存関係を調べる {% data variables.product.prodname_dotcom %} の依存関係グラフを使用すると、次の情報を調べることができます。 diff --git a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md index 4259793bd2e2f..b06f523087dc3 100644 --- a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..28a54a01e30fb --- /dev/null +++ b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +*secret_scanning.yml* ファイルを使用して、{% data variables.product.prodname_secret_scanning %} からディレクトリを除外できます。 たとえば、テストまたはランダムに生成されたコンテンツを含むディレクトリを除外できます。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. ファイル名フィールドに、*.github/secret_scanning.yml* と入力します。 +4. [**Edit new file**] に `paths-ignore:` と入力してから、{% data variables.product.prodname_secret_scanning %} から除外するパスを入力します。 + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + `*` などの特殊文字を使用して、パスをフィルタできます。 フィルタパターンに関する詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)」を参照してください。 + + {% note %} + + **ノート:** + - `paths-ignore` に 1,000 以上のエントリがある場合、{% data variables.product.prodname_secret_scanning %} は最初の 1,000 ディレクトリのみをスキャン対象から除外します。 + - *secret_scanning.yml* が 1MB 以上ある場合、{% data variables.product.prodname_secret_scanning %} はファイル全体を無視します。 + + {% endnote %} + +{% data variables.product.prodname_secret_scanning %} からの個々のアラートを無視することもできます。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)」を参照してください。 + +### 参考リンク + +- 「[Organization のセキュリティと分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」 diff --git a/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 888c02c1e2771..c6e2e1b37de9c 100644 --- a/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -6,8 +6,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### リポジトリの {% data variables.product.prodname_actions %} 権限について diff --git a/translations/ja-JP/content/github/administering-a-repository/index.md b/translations/ja-JP/content/github/administering-a-repository/index.md index 02f66579340da..dac34c24e8fb0 100644 --- a/translations/ja-JP/content/github/administering-a-repository/index.md +++ b/translations/ja-JP/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..d5430e2e7529c --- /dev/null +++ b/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. {% data variables.product.company_short %}は、`File.fnmatch` 構文に `File::FNM_PATHNAME` フラグを使用するので、ワイルドカードはディレクトリの区切り文字 (`/`) には一致しません。 たとえば、`qa/*` は、`qa/` で始まり、1 つのスラッシュが含まれるすべてのブランチにマッチします。 You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. ブランチのルールに関する構文オプションの詳しい情報については、 [fnmatch ドキュメンテーション](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)を参照してください。 + +リポジトリが同じブランチに影響する複数の保護されたブランチのルールを持っているなら、特定のブランチ名を含むルールがもっとも高い優先順位を持ちます。 同じ特定のブランチ名を参照する保護されたブランチのルールが複数あるなら、最初に作成されたブランチルールが高い優先順位を持ちます。 + +`*`、`?`、`]`などの特殊文字を含む保護されたブランチのルールは、作成された順序で適用されるので、これらの文字を持つ古いルールが高い優先順位を持ちます。 + +既存のブランチのルールに例外を作成するため、特定のブランチ名に対するルールなど、優先度の高いブランチ保護ルールを新しく作成できます。 + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![プルリクエストレビューの制限チェックボックス](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![必須とするレビュー承認の数を選択するドロップダウンメニュー](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![新たなコミットがチェックボックスにプッシュされた際に古いプルリクエストの承認を却下するチェックボックス](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。 ![コードオーナーのレビューを必要とする](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. 詳しい情報については[プルリクエストレビューの却下](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![[Restrict who can dismiss pull request reviews] チェックボックス](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. + - [**Require status checks to pass before merging**] を選択します。 ![必須ステータスチェックのオプション](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png) + - 使用可能なステータスチェックのリストから、必須とするものを選択します。 ![利用可能なステータスチェックの一覧](/assets/images/help/repository/required-statuses-list.png) +1. Optionally, select **Require signed commits**. ![[Require signed commits] オプション](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. ![必須の直線状の履歴オプション](/assets/images/help/repository/required-linear-history.png) +1. オプションとして、[**Include administrators**] を選択します。 ![[Include administrators] チェックボックス](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. ![ブランチ制限のチェックボックス](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![ブランチ制限の検索](/assets/images/help/repository/restrict-branch-search.png) +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![フォースプッシュオプションを許可する](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. ![ブランチ削除オプションを許可する](/assets/images/help/repository/allow-branch-deletions.png) +1. ** Create（作成）**をクリックしてください。 + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to edit, click **Edit**. ![編集ボタン](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. [**Save changes**] をクリックします。 ![[Edit message] ボタン](/assets/images/help/repository/save-branch-protection-rule.png) + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to delete, click **Delete**. ![削除ボタン](/assets/images/help/repository/delete-branch-protection-rule.png) 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 4e268a2394432..333dd3fadf0c3 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 @@ -4,6 +4,7 @@ intro: リポジトリにチェックインしたシークレットのアラー product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. 左サイドバーで、[**Detected secrets**] をクリックします。 !["Detected secrets" タブ](/assets/images/help/repository/sidebar-secrets.png) -4. [Secret scanning] の下で、表示するアラートをクリックします。 ![シークレットスキャンからのアラートのリスト](/assets/images/help/repository/secret-scanning-click-alert.png) -5. 必要に応じて、[Resolve] ドロップダウンメニューを使用して、アラートを解決する理由をクリックします。 ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. [Secret scanning] の下で、表示するアラートをクリックします。 + {% if currentVersion == "free-pro-team@latest" %} + ![シークレットスキャンからのアラートのリスト](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![シークレットスキャンからのアラートのリスト](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### 侵害されたシークレットを保護する シークレットがリポジトリにコミットされたら、シークレットが侵害されたと考える必要があります。 {% data variables.product.prodname_dotcom %} は、侵害されたシークレットに対して次のアクションを行うことをおすすめします。 - 侵害された {% data variables.product.prodname_dotcom %} の個人アクセストークンについては、侵害されたトークンを削除し、新しいトークンを作成し、古いトークンを使っていたサービスを更新してください。 詳しい情報については[コマンドラインのための個人のアクセストークンの作成](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)を参照してください。 -- それ以外のすべてのシークレットについては、最初に {% data variables.product.prodname_dotcom %} にコミットされたシークレットが有効であることを確認してください。 有効である場合は、新しいシークレットを作成し、古いシークレットを使用するサービスを更新してから、古いシークレットを削除します。 +- それ以外のすべてのシークレットについては、最初に {% data variables.product.product_name %} にコミットされたシークレットが有効であることを確認してください。 有効である場合は、新しいシークレットを作成し、古いシークレットを使用するサービスを更新してから、古いシークレットを削除します。 diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index 6ba470ea84a88..fd4a740593ac0 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -5,7 +5,7 @@ intro: '{% data variables.large_files.product_name_long %}（{% data variables.l permissions: 'リポジトリの管理者権限を持つユーザは、{% data variables.large_files.product_name_short %} オブジェクトがリポジトリのアーカイブに含まれているかどうかを管理できます。' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ 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 currentVersion == "free-pro-team@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)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md index 14b298a7771ed..7a4c2e80a4ee4 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### リリース管理について diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 743adbd6009d8..ca6118fe297c9 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### セキュリティおよび分析機能の有効化または無効化 +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### セキュリティアラートへのアクセスを許可する @@ -35,7 +53,13 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. + {% if currentVersion == "free-pro-team@latest" %} + ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. [**Save changes**] をクリックします。 ![セキュリティアラート設定を変更するための "Save changes" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### セキュリティアラートへのアクセスを削除する @@ -43,7 +67,14 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) diff --git a/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md index a68232fd16095..04d2c9c04d150 100644 --- a/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,8 @@ Organization のオーナーは、リポジトリの可視性を変更する機 * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ Organization のオーナーは、リポジトリの可視性を変更する機 #### リポジトリをパブリックにする * {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). リポジトリがパブリックになったら、コントリビューターをサポートするための最適な手法にプロジェクトが合致しているかどうかを確認するため、リポジトリのコミュニティプロフィールを表示できます。 詳細は「[コミュニティプロフィールを見る](/articles/viewing-your-community-profile)」を参照してください。{% endif %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). リポジトリがパブリックになったら、コントリビューターをサポートするための最適な手法にプロジェクトが合致しているかどうかを確認するため、リポジトリのコミュニティプロフィールを表示できます。 For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} diff --git a/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..a2a901cf661fd --- /dev/null +++ b/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: 必須ステータスチェックのトラブルシューティング +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. 詳しい情報については、「[チェック](/rest/reference/checks)」を参照してください。 + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. これによって、ブランチがベースブランチからの最新のコードでテストされたことが保証されます。 ブランチが古い場合、ベースブランチをブランチにマージする必要があります。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 + +{% note %} + +**注釈:** Git リベースを使用してブランチをベースブランチに対して最新にすることもできます。 詳しい情報については、「[Git リベースについて](/github/using-git/about-git-rebase)」を参照してください。 + +{% endnote %} + +必須ステータスチェックにすべてパスするまでは、ローカルでの変更を保護されたブランチにプッシュすることはできません。 その代わりに、以下のようなエラーメッセージが返されます. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. これはマージコミット自体でステータスチェックを実行せずに行えます。 + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 If the test merge commit has a status, the test merge commit must pass. それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md index 10ef6e90445c3..8cef4e8550925 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -19,11 +19,13 @@ versions: コミットあるいはタグが検証できない署名を持っている場合、{% data variables.product.product_name %} はそのコミットあるいはタグを未検証としてマークします。 -リポジトリ管理者は、ブランチでコミット署名を必須として、署名および検証されていないすべてのコミットをブロックできます。 詳しい情報については[必須のコミット署名について](/articles/about-required-commit-signing)を参照してください。 +リポジトリ管理者は、ブランチでコミット署名を必須として、署名および検証されていないすべてのコミットをブロックできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-signed-commits)を参照してください。 {% data variables.product.product_name %}上の署名されたコミットあるいはタグの検証ステータスをチェックして、コミットの署名が検証されない理由を見ることができます。 詳細は「[コミットおよびタグの署名の検証のステータスをチェックする](/articles/checking-your-commit-and-tag-signature-verification-status)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} は自動的に GPG を使用して、{% data variables.product.product_name %} Web インターフェースを使用して行ったコミットに署名します。ただし、作者ではないプルリクエストを squash してマージする場合を除きます。 {% data variables.product.product_name %}によって署名されたコミットは、{% data variables.product.product_name %}で認証済みのステータスになります。 署名は、https://github.com/web-flow.gpgから利用できる公開鍵を使ってローカルに検証できます。{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. {% data variables.product.product_name %}によって署名されたコミットは、{% data variables.product.product_name %}で認証済みのステータスになります。 署名は、https://github.com/web-flow.gpgから利用できる公開鍵を使ってローカルに検証できます。 For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} ### GPG コミット署名の検証 diff --git a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md index 2e084d0369ff2..f2d7401ae2f46 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -39,6 +39,7 @@ versions: | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} | [`account_recovery_token`](#account_recovery_token-category-actions) | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。 | | [`支払い`](#billing-category-actions) | 自分の支払い情報に関連するすべての活動が対象です。 | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。 | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 | | [`marketplace_listing`](#marketplace_listing-category-actions) | {% data variables.product.prodname_marketplace %} に一覧表示しているアプリに関連するすべての活動が対象です。{% endif %} | [`oauth_access`](#oauth_access-category-actions) | 接続している [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) に関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %} @@ -82,6 +83,12 @@ versions: | `change_billing_type` | {% data variables.product.prodname_dotcom %} の[支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 | | `change_email` | [自分のメール アドレスを変更する](/articles/changing-your-primary-email-address)ときにトリガーされます。 | +#### `codespaces` category actions + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### `marketplace_agreement_signature` カテゴリアクション | アクション | 説明 | @@ -227,20 +234,20 @@ versions: #### `user` カテゴリアクション -| アクション | 説明 | -| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | {% if currentVersion != "github-ae@latest" %}[新しいメールアドレスを追加する](/articles/changing-your-primary-email-address){% else %}新しいメールアドレスを追加する{% endif %}とトリガーされます。 | -| `create` | 新しいユーザアカウントを作成するとトリガーされます。{% if currentVersion != "github-ae@latest" %} -| `change_password` | 自分のパスワードを変更するときにトリガーされます。 | -| `forgot_password` | [パスワード のリセット](/articles/how-can-i-reset-my-password)を要求したときにトリガーされます。{% endif %} -| `hide_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。 | -| `login` | {% data variables.product.product_location %} にログインするときにトリガーされます | -| `failed_login` | 正常にログインできなかったときにトリガーされます | -| `remove_email` | メール アドレスを削除するときにトリガーされます。 | -| `rename` | アカウントの名前を変更するとトリガーされます。{% if currentVersion == "free-pro-team@latest" %} -| `report_content` | [Issue または Pull Request、あるいは Issue、Pull Request、または Commit でのコメントを報告する](/articles/reporting-abuse-or-spam)ときにトリガーされます。{% endif %} -| `show_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションをパブリックにする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。{% if currentVersion != "github-ae@latest" %} -| `two_factor_requested` | {% data variables.product.product_name %} が[自分の 2 要素認証コード](/articles/accessing-github-using-two-factor-authentication)を要求するときにトリガーされます。{% endif %} +| アクション | 説明 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} +| `create` | 新しいユーザアカウントを作成するとトリガーされます。{% if currentVersion != "github-ae@latest" %} +| `change_password` | 自分のパスワードを変更するときにトリガーされます。 | +| `forgot_password` | [パスワード のリセット](/articles/how-can-i-reset-my-password)を要求したときにトリガーされます。{% endif %} +| `hide_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。 | +| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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` カテゴリアクション @@ -249,4 +256,3 @@ versions: | `update` | 自分のプロファイルでステータスを設定または変更するときにトリガーされます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。 | | `destroy` | 自分のプロファイルでステータスを消去するときにトリガーされます。 | - diff --git a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index f5c583b985d4c..18177dab2bfcd 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ SSH キーにより、誰かがあなたのコンピュータにアクセスす 次のコマンドを入力して、鍵ペアを再生成せずに既存の秘密鍵のパスフレーズを変更できます: ```shell -$ ssh-keygen -p -# SSH キー作成プロセスを開始します -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/ja-JP/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/ja-JP/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index cef143c7f7682..9a69bf5bab746 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/ja-JP/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ Organization またはユーザアカウント用にデフォルトの行動規 3. ファイル名フィールドに、ファイルの名前と拡張子を入力します。 ![新しい行動規範ファイル名](/assets/images/help/repository/new-code-of-conduct-file-name.png) - 行動規範をリポジトリのルートディレクトリに表示するには、ファイル名フィールドに *CODE_OF_CONDUCT* と入力します。 - 行動規範をリポジトリの `docs` ディレクトリに表示するには、*docs/CODE_OF_CONDUCT* と入力します。 - - 行動規範をリポジトリの `.github` ディレクトリに表示するには、 *.github/CODE_OF_CONDUCT* と入力します。 + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. 4. 新しいファイルに、カスタムの行動規範を追加します。 {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 8390cd0f948e8..2e8ec863b6295 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,7 +74,7 @@ versions: - ブランチでステータスチェック必須が有効化されていると、必要なCIテストがすべてパスするまで、変更をブランチにマージできません。 詳しい情報については[ステータスチェックについて](/articles/about-status-checks)を参照してください。 - ブランチでプルリクエストレビュー必須が有効化されている場合、プルリクエストレビューポリシー中のすべての要求が満たされるまでは、ブランチに変更をマージできません。 詳しい情報については[プルリクエストのマージ](/articles/merging-a-pull-request)を参照してください。 - ブランチでコードオーナーからの必須レビューが有効化されており、プルリクエストがオーナーを持つコードを変更している場合、コードオーナーがプルリクエストを承認しなければ、そのプルリクエストはマージできません。 詳細は「[コードオーナーについて](/articles/about-code-owners)」を参照してください。 -- ブランチでコミット署名必須が有効化されている場合、署名および検証されていないコミットはブランチにプッシュできません。 詳しい情報については、「[コミット署名の検証について](/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" %} +- ブランチでコミット署名必須が有効化されている場合、署名および検証されていないコミットはブランチにプッシュできません。 For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% 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/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 3dc6099086899..a34bfa5280018 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,9 +44,7 @@ versions: ### 必須のレビュー -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -詳しい情報については[プルリクエストのための必須のレビューについて](/articles/about-required-reviews-for-pull-requests)を参照してください。 +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% tip %} @@ -57,6 +55,5 @@ versions: ### 参考リンク - [プルリクエストで提案された変更のレビュー](/articles/reviewing-proposed-changes-in-a-pull-request) -- [プルリクエストの必須レビューの有効化](/articles/enabling-required-reviews-for-pull-requests) - [プルリクエストレビューの表示](/articles/viewing-a-pull-request-review) - [リポジトリコントリビューターのためのガイドラインを定める](/articles/setting-guidelines-for-repository-contributors) diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index fb0505bc95242..3dd9c600f35d1 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -必須レビューに関する詳しい情報については[プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests)を参照してください。 +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -プルリクエストにコメントしたり、変更を承認したり、承認に先立って改善をリクエストしたりできます。 詳しい情報については[プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests)及び[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)を参照してください。 +プルリクエストにコメントしたり、変更を承認したり、承認に先立って改善をリクエストしたりできます。 詳細は「[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ versions: ### 参考リンク -- [プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests) - [プルリクエストで提案された変更のレビュー](/articles/reviewing-proposed-changes-in-a-pull-request) - [プルリクエストへのコメント](/articles/commenting-on-a-pull-request) diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index dad732d4c651d..c80a466670d65 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ versions: - あなたがプッシュアクセス権限を持つリポジトリでオープンされ、かつそのリポジトリのフォークから作成されている - ユーザ所有のフォーク上にある - プルリクエストの作者から権限を付与されている -- コミットを妨げる[ブランチ制限](/articles/about-branch-restrictions)がない +- コミットを妨げる[ブランチ制限](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches)がない プルリクエストを作成したユーザのみが、ユーザー所有のフォークにコミットをプッシュする権限を与えることができます。 詳しい情報については、「[フォークから作成されたプルリクエストブランチへの変更を許可する](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)」を参照してください。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index 6378c75918c84..d5b88cbaed995 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: プルリクエストレビューの却下 -intro: 'リポジトリに[レビューが必要](/articles/about-required-reviews-for-pull-requests)な場合は、有効でなくなった、またはレビュー担当者による承認不可のプルリクエストレビューを却下できます。' +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ versions: - "[プルリクエストのレビューについて](/articles/about-pull-request-reviews)" - [プルリクエストで提案された変更のレビュー](/articles/reviewing-proposed-changes-in-a-pull-request) -- [プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests) +- [保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) \ No newline at end of file diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index 5a7be18cfecdd..4862893244b42 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### GitHub のフローに従う 1. リポジトリから[ブランチを作成](/articles/creating-and-deleting-branches-within-your-repository)します。 -2. ファイルの[作成](/articles/creating-new-files)、[編集](/articles/editing-files)、[名前の変更](/articles/renaming-a-file)、[移動](/articles/moving-a-file-to-a-new-location)、または[削除](/articles/deleting-files)を行います。 +2. ファイルの[作成](/articles/creating-new-files)、[編集](/articles/editing-files)、[名前の変更](/articles/renaming-a-file)、[移動](/articles/moving-a-file-to-a-new-location)、または[削除](/github/managing-files-in-a-repository/deleting-files-in-a-repository)を行います。 3. ブランチから、提案する変更で[プルリクエストを送信](/articles/creating-a-pull-request)して、ディスカッションを始めます。 4. 必要に応じてブランチで変更を行います。 プルリクエストは自動的に更新されます。 5. ブランチをマージする準備ができたら、[プルリクエストをマージ](/articles/merging-a-pull-request)します。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 94e785995f516..b09eb899a909b 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### プルリクエストのマージについて -プルリクエストでは、head ブランチに加えた変更をベースブランチにマージすることを提案します。 {% data reusables.pull_requests.about-protected-branches %}ただし、プルリクエストを特定のブランチにマージできるタイミングには制限がある場合があります。 たとえば、必須のステータスチェックに合格した場合にのみ、プルリクエストをデフォルトブランチにマージできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。 +プルリクエストでは、head ブランチに加えた変更をベースブランチにマージすることを提案します。 デフォルトでは、head ブランチがベースブランチとコンフリクトしていない限り、どのプルリクエストもいつでもマージできます。 However, there may be restrictions on when you can merge a pull request into a specific branch. たとえば、必須のステータスチェックに合格した場合にのみ、プルリクエストをデフォルトブランチにマージできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。 {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 064c72b73a003..234a878a67b1b 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ versions: ![ファイルフィルタメニュー](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. マニフェストまたはロックファイルのヘッダの右側で、リッチ diff ボタンをクリックして依存関係のレビューを表示します。 +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ versions: * 脆弱性の重要度。 * 脆弱性が修正された依存関係のバージョン。 誰かのプルリクエストを確認している場合は、パッチを適用したバージョンまたはそれ以降のリリースに依存関係を更新するようにコントリビューターに依頼することができます。 -1. ソースの diff ボタンをクリックすると、ファイルの元のビューに戻ることができます。 - - ![ソース diff ボタン](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 3ee02dedaa04d..02ef65cd3a675 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,9 +36,11 @@ versions: {% data reusables.repositories.changed-files %} -1. マニフェストまたはロックファイルのヘッダの右側で、リッチ diff ボタンをクリックして依存関係のレビューを表示します。 +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### ファイルをレビュー済みとしてマークする @@ -65,5 +67,5 @@ versions: ### 参考リンク -- [プルリクエストのための必須レビューについて](/github/administering-a-repository/about-required-reviews-for-pull-requests) +- [保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) - 「[プルリクエストをレビューステータスでフィルタリングする](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)」 diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index b877ed982246d..c1ed35193806b 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ Organization は、オープンソースの取り組みにおいて、`name@orga ### コマンドラインで `on-behalf-of` バッジを付けてコミットを作成する -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. コミットメッセージと、変更の短く分かりやすい説明を入力してください。 コミットの説明の後に、閉じる引用符の代わりに 2 つの空の行を追加してください。 + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} 2. コミットメッセージの次の行に、`on-behalf-of: @org ` と入力して、引用符で閉じます。 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 c41b86f5ffb3f..deb2f7ce5a6f0 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 @@ -39,7 +39,17 @@ versions: {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. コミットメッセージと、変更の短く分かりやすい説明を入力してください。 コミットの説明の後に、閉じる引用符の代わりに 2 つの空の行を追加してください。 + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** コミットメッセージを入力するのにコマンドライン上のテキストエディタを使っているなら、コミットの説明とコミットトレーラーの`Co-authored-by:`との間に新しい2行があることを確認してください。 + + {% endtip %} 3. コミットメッセージの次の行に、各共作者の情報を `Co-authored-by: name ` という形式で入力します。 共同作者の情報の後に、閉じる引用符を追加します。 diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index df6710d6f7147..d115ece6a1ea6 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -19,7 +19,7 @@ versions: コードオーナーは、他者が所有するコードを変更するプルリクエストをオープンすると、自動的にレビューをリクエストされます。 コードオーナーはドラフトのプルリクエストのレビューを自動的にリクエストされません。 ドラフトのプルリクエストに関する詳しい情報については「[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)」を参照してください。 コードオーナーはドラフトのプルリクエストのレビューを自動的にリクエストされません。 プルリクエストをドラフトに変換する場合、通知を既にサブスクライブしているユーザは自動的にサブスクライブ解除されません。 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)」を参照してください。 -管理者あるいはオーナー権限を持つ誰かがレビュー必須を有効化した場合、作者がリポジトリ中でプルリクエストをマージできるための条件としてコードオーナーからの承認を必須とすることもできます。 詳しい情報については、「[プルリクエストの必須レビューを有効にする](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)」を参照してください。 +管理者あるいはオーナー権限を持つ誰かがレビュー必須を有効化した場合、作者がリポジトリ中でプルリクエストをマージできるための条件としてコードオーナーからの承認を必須とすることもできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)を参照してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Team がコードレビューの割り当てを有効にしている場合、個々の承認は、保護されたブランチでのコードオーナーの承認要件を満たしません。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index 8580c2d6605d0..8b234e6588b59 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ With {% endif %} リポジトリを使用して、作業を管理し、他のユーザと共同作業を行うことができます。 -- Issue を使用して、ユーザフィードバックの収集、ソフトウェアバグの報告、および実行するタスクの整理を行うことができます。 詳しい情報については、「[Issue について](/github/managing-your-work-on-github/about-issues)」を参照してください。 -- {% data reusables.discussions.you-can-use-discussions %} +- Issue を使用して、ユーザフィードバックの収集、ソフトウェアバグの報告、および実行するタスクの整理を行うことができます。 For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - プルリクエストを使用して、リポジトリへの変更を提案できます。 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)を参照してください。 - プロジェクトボードを使用して、Issue とプルリクエストを整理して優先順位を付けることができます。 詳細は「[プロジェクトボードについて](/github/managing-your-work-on-github/about-project-boards)」を参照してください。 diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 2200537d9d31e..e4619e0a4c958 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ When you search by a family license, your results will include all licenses in t ### Detecting a license -[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md index 24beb51bc16aa..73a4efe76daf9 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ versions: {% data reusables.codespaces.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)」を参照してください。 +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/index.md b/translations/ja-JP/content/github/developing-online-with-codespaces/index.md index ac321be2e33af..5d950494537b0 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/index.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..fd782e5a69b5a --- /dev/null +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. [**Add secret（シークレットの追加）**] をクリックします。 + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. [**Save changes**] をクリックします。 + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. 警告を読んで、**OK**をクリックしてください。 ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/ja-JP/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index a9d2938c2b0b9..ffbc7947dd6d6 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ versions: {% endnote %} +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." ### 参考リンク 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 77591e2c59405..4aa8d8ba48ee4 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ versions: {% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用します。 For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." {% data variables.product.prodname_code_scanning %} を始めるには、「[{% data variables.product.prodname_code_scanning %} の有効化](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)」を参照してください。 @@ -54,7 +54,7 @@ versions: ### 参考リンク -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) - 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-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index d11a128b1c2ea..612c2f62274d4 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -238,7 +238,9 @@ 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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +The settings in the file are written in YAML format. #### Specifying additional queries 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 855a318c4a144..74bf2ff7acbfa 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 @@ -17,7 +17,7 @@ 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. 詳しい情報については、「[{% 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 %} @@ -40,13 +40,16 @@ You decide how you generate {% data variables.product.prodname_code_scanning %} 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. +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + ### Viewing the logging output from {% 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. {% 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'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 3664ed3528d5c..82d80089deb16 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ You can use the {% data variables.product.prodname_codeql_runner %} to run {% da The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**ノート:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} ### Downloading the {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi ### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux In addition to this, each CI server also needs: -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." +- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: 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 721b4060208d5..572a1b0ed1971 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 @@ -15,7 +15,7 @@ versions: In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the 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. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository 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)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. For more information, see "[About required status checks](/github/administering-a-repository/about-required-status-checks)." +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index 4b0e0ffff8ea6..005fdcc976958 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### The `init` command takes too long 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 9cd2e13464936..38d2f5c523db3 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### コンパイル言語の自動ビルドの失敗 @@ -83,17 +84,6 @@ For more information about specifying build steps, see "[Configuring the {% data {% data variables.product.prodname_codeql %} の `autobuild` 機能は、ヒューリスティックスを使用してリポジトリにコードをビルドしますが、このアプローチでは、リポジトリの分析が不完全になることがあります。 たとえば、単一のリポジトリに複数の `build.sh` コマンドが存在する場合、`autobuild` ステップはコマンドの 1 つしか実行しないため、分析が完了しない場合があります。 これを解決するには、`autobuild` ステップを、分析するすべてのソースコードをビルドするビルドステップに置き換えます。 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)." -### エラー: 「サーバーエラー」 - -サーバーエラーにより {% data variables.product.prodname_code_scanning %} のワークフローが実行できない場合は、ワークフローを再実行してください。 問題が解決しない場合は、{% data variables.contact.contact_support %} にお問い合わせください。 - -### エラー:「ディスク不足」または「メモリ不足」 -On very large projects, - -{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - ### ビルドに時間がかかりすぎる {% data variables.product.prodname_codeql %} 分析でのビルドの実行に時間がかかりすぎる場合は、ビルド時間を短縮するための方法がいくつかあります。 @@ -128,3 +118,54 @@ If you are analyzing code written in Python, you may see different results depen On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." {% endif %} + +### エラー: 「サーバーエラー」 + +サーバーエラーにより {% data variables.product.prodname_code_scanning %} のワークフローが実行できない場合は、ワークフローを再実行してください。 問題が解決しない場合は、{% data variables.contact.contact_support %} にお問い合わせください。 + +### エラー:「ディスク不足」または「メモリ不足」 +On very large projects, + +{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index fcc9132014162..46eee216d4ce5 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -27,11 +27,13 @@ You can upload the results using {% data variables.product.prodname_actions %}{% - {% data variables.product.prodname_dotcom %} は、リポジトリにアップロードされた SARIF ファイルからの {% data variables.product.prodname_code_scanning %} アラートを表示します。 If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, 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)"). - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)"). +{% data reusables.code-scanning.not-available %} + ### {% data variables.product.prodname_actions %} での {% data variables.product.prodname_code_scanning %} 分析をアップロードする サードパーティの SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードするには、{% data variables.product.prodname_actions %} ワークフローが必要です。 For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -ワークフローは、`upload-sarif` アクションを使用する必要があります。 これには、アップロードの設定に使用できる入力パラメータがあります。 使用する主な入力パラメータは、アップロードする SARIF ファイルのファイルまたはディレクトリを設定する `sarif-file` です。 ディレクトリまたはファイルのパスは、リポジトリのルートからの相対パスです。 詳しい情報については、「[`upload-sarif` アクション](https://github.com/github/codeql-action/tree/HEAD/upload-sarif)」を参照してください。 +ワークフローは、`upload-sarif` アクションを使用する必要があります。 これには、アップロードの設定に使用できる入力パラメータがあります。 使用する主な入力パラメータは、アップロードする SARIF ファイルのファイルまたはディレクトリを設定する `sarif-file` です。 ディレクトリまたはファイルのパスは、リポジトリのルートからの相対パスです。 For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/HEAD/upload-sarif). `upload-sarif` アクションは、`push` および `scheduled` イベントが発生したときに実行するように設定できます。 {% data variables.product.prodname_actions %} イベントについて詳しい情報は、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..edc7c1d5257d5 --- /dev/null +++ b/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### {% data variables.product.prodname_GH_advanced_security %} について + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。 + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} について](/github/administering-a-repository/about-secret-scanning)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md index e028a76373ce5..958b2014079cc 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: GitHub for mobile -intro: '{% data variables.product.company_short %} での作業をモバイルデバイスからトリアージ、コラボレーション、および管理します。' +intro: '{% data variables.product.product_name %} での作業をモバイルデバイスからトリアージ、コラボレーション、および管理します。' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### {% data variables.product.prodname_mobile %} について -現在、{% data variables.product.prodname_mobile %} は {% data variables.product.prodname_dotcom_the_website %} ユーザが Android および iOS アプリとして利用できます。 +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} を使用すると、{% data variables.product.prodname_dotcom %} に対してインパクトのある作業をすばやく、どこからでも行うことができます。 {% data variables.product.prodname_mobile %} は、信頼できるファーストパーティクライアントアプリケーションを介して {% data variables.product.prodname_dotcom %} データにアクセスする安心で安全な方法です。 +{% data variables.product.prodname_mobile %} を使用すると、{% data variables.product.product_name %} に対してインパクトのある作業をすばやく、どこからでも行うことができます。 {% data variables.product.prodname_mobile %} は、信頼できるファーストパーティクライアントアプリケーションを介して {% data variables.product.product_name %} データにアクセスする安心で安全な方法です。 {% data variables.product.prodname_mobile %} では、次のことができます。 - 通知の管理、トリアージ、クリア @@ -23,12 +26,38 @@ versions: Android または iOS に {% data variables.product.prodname_mobile %} をインストールするには、「[{% data variables.product.prodname_mobile %}](https://github.com/mobile)」を参照してください。 +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### 必要な環境 + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + ### {% data variables.product.prodname_mobile %} でサポートされている言語 {% data variables.product.prodname_mobile %} は次の言語で利用できます。 +- 英語 - 日本語 - ポルトガル語 (ブラジル) +- Simplified Chinese - スペイン語 デバイスの言語をサポートされている言語に設定すると、{% data variables.product.prodname_mobile %} はデフォルトでその言語になります。 {% data variables.product.prodname_mobile %} の [**Settings**] メニューで {% data variables.product.prodname_mobile %} の言語を変更できます。 @@ -37,9 +66,9 @@ Android または iOS に {% data variables.product.prodname_mobile %} をイン {% data variables.product.prodname_mobile %} は、iOS のユニバーサルリンクを自動的に有効にします。 {% data variables.product.product_name %} リンクをタップすると、リンク先 URL が Safari ではなく {% data variables.product.prodname_mobile %} で開きます。 詳しい情報については、Apple Developer サイトの「[Universal Links](https://developer.apple.com/ios/universal-links/)」を参照してください。 -ユニバーサルリンクを無効にするには、{% data variables.product.prodname_dotcom %} リンクを長押しして、[**Open**] をタップします。 今後 {% data variables.product.prodname_dotcom %} リンクをタップするたびに、リンク先 URL は {% data variables.product.prodname_mobile %} ではなく Safari で開きます。 +ユニバーサルリンクを無効にするには、{% data variables.product.product_name %} リンクを長押しして、[**Open**] をタップします。 今後 {% data variables.product.product_name %} リンクをタップするたびに、リンク先 URL は {% data variables.product.prodname_mobile %} ではなく Safari で開きます。 -ユニバーサルリンクを再度有効にするには、{% data variables.product.prodname_dotcom %} リンクを長押しして、[**Open in {% data variables.product.prodname_dotcom %}**] をタップします。 +ユニバーサルリンクを再度有効にするには、{% data variables.product.product_name %} リンクを長押しして、[**Open in {% data variables.product.prodname_dotcom %}**] をタップします。 ### フィードバックを送る diff --git a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md index e3bca9f5cf181..5a31b272c619a 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: GitHub の製品 +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」および「[{% data variables.product.prodname_secret_scanning %}について](/github/administering-a-repository/about-secret-scanning) (ベータ)」を参照してください。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (ベータ)」を参照してください。{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} - [Organization の {% data variables.product.prodname_learning %}](https://lab.github.com/organizations) -{% data variables.product.prodname_ghe_one %} へのサインアップの詳細については、[{% data variables.product.product_name %} の販売チーム](https://enterprise.github.com/contact)にお問い合わせください。 +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ja-JP/content/github/getting-started-with-github/index.md b/translations/ja-JP/content/github/getting-started-with-github/index.md index 0ea87e1cc3129..aeb62f09a0763 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/index.md +++ b/translations/ja-JP/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md index 379146676ac88..71601cb90a2ca 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -29,14 +29,14 @@ versions: ### リポジトリ -| キーボードショートカット | 説明 | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | [**Code**] タブに移動します | -| g i | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | -| g p | [**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 c | [**Code**] タブに移動します | +| g i | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | +| g p | [**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" %} | g a | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %} -| g b | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | -| g w | [**Wiki**] タブに移動します。 詳細は「[ウィキについて](/articles/about-wikis)」を参照してください。 | +| g b | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | +| g w | [**Wiki**] タブに移動します。 詳細は「[ウィキについて](/articles/about-wikis)」を参照してください。 | ### ソースコード編集 @@ -159,6 +159,10 @@ versions: | キーボードショートカット | 説明 | | ---------------------------------------------------------- | ------------------------------------ | | command + space または control + space | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 | +| g f | Go to the workflow file | +| shift + t or T | Toggle timestamps in logs | +| shift + f or F | Toggle fullscreen logs | +| esc | Exit fullscreen logs | {% endif %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..a5d7bb10b9d86 --- /dev/null +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)を参照してください。 + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. 詳細は「[機密データをリポジトリから削除する](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)」を参照してください。 + +### Deleting a file + +1. リポジトリ内で削除対象のファイルを見つけます。 +2. ページの上部で、次をクリックします。 +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/index.md b/translations/ja-JP/content/github/managing-files-in-a-repository/index.md index ae3336bd8c9fc..558a218cd8a03 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/index.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index 5e7beafa67356..ced2621a6caff 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ GitHub では、*.csv* (カンマ区切り) 形式および *.tsv* (タブ区切 ### データを検索する -データセットから特定の値を見つけるには、ファイルの上にある検索バーで直接、入力を開始します。 行が自動的にフィルタリングされます。 +データセットから特定の値を見つけるには、ファイルの上にある検索バーで直接、入力を開始します。 The rows will filter automatically: ![値を検索する](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 75af6d6ecc015..824bd5d3d597a 100644 --- a/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ versions: - 500 MB のファイルを {% data variables.large_files.product_name_short %} にプッシュすると、あなたに割り当てられた 500 MB のストレージを使うことになりますが、あなたの帯域は消費されません。 1 バイト分の変更を加えてそのファイルを再度プッシュすると、さらに 500 MB のストレージが使われ、帯域は消費されません。これらの 2 つのプッシュによる合計で、1 GB のストレージが使われ、帯域の消費はありません。 - LFS で追跡されている 500 MB のファイルをダウンロードした場合、リポジトリのオーナーに割り当てられている帯域を 500 MB 消費します。 コラボレータがそのファイルに変更をプッシュし、あなたが新しいバージョンをローカルのリポジトリにプルしたなら、あなたは 500 MB の帯域を新たに消費するため、この 2 つのダウンロードでの合計の使用帯域は 1 GB になります。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) オブジェクトがリポジトリのソースコードアーカイブに含まれている場合、それらのアーカイブのダウンロードは、リポジトリの帯域幅使用量にカウントされます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md index 0cfe396906a96..e572946ec55b9 100644 --- a/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ versions: ### 参考リンク -- 「[{% 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" %} +- 「[{% 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@3.0" or currentVersion == "github-ae@latest" %} - 「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」{% endif %} diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index a9d9d757dd9be..01d6f159846ac 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -33,3 +33,7 @@ When you merge a pull request that contains a security update, the corresponding ### 互換性スコアについて {% 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. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index e4cc7ae2629c6..e2aee7064078d 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -42,16 +42,18 @@ You can enable {% data variables.product.prodname_dependabot_security_updates %} ### リポジトリの {% data variables.product.prodname_dependabot_security_updates %} を管理する -個別のリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にできます。 +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にすることもできます。 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)」または「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 {% data variables.product.prodname_dependabot_security_updates %} には特定のリポジトリ設定が必要です。 詳しい情報については、「[サポートされているリポジトリについて](#supported-repositories)」を参照してください。 +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. アラート一覧の上にあるドロップダウンメニューで [**{% data variables.product.prodname_dependabot %} security updates**] を選択または選択解除します。 ![{% data variables.product.prodname_dependabot_security_updates %} を有効にするオプションを含むドロップダウンメニュー](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index d82367ea2434a..5bc5088286147 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ You can configure notification settings for yourself or your organization from t {% note %} -**Note:** You can filter your {% data variables.product.company_short %} inbox notifications to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)」を参照してください。 +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index 09eb6eef11b34..a4de534abf299 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,13 +78,15 @@ The best way to resolve this error is to merge or close some of the existing pul #### {% data variables.product.prodname_dependabot %} can't resolve your dependency files -**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a 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**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index f9fe7e5e5529c..7d40212a2c15e 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### 通知とサブスクリプション サブスクリプションを通じて、{% data variables.product.product_name %} の特定のアクティビティに関する継続的な更新を受信するかを選択できます。 通知では、サブスクライブしている特定のアクティビティについての更新を受信します。 @@ -50,7 +54,7 @@ versions: ### 通知とサブスクリプションをカスタマイズする -[https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} の通知インボックスと {% data variables.product.prodname_mobile %} アプリ{% endif %}、メール、またはこれらのオプションの組み合わせから通知を表示できます。 +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. 通知設定で、受信する更新の種類と更新の送信先をカスタマイズできます。 詳しい情報については「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」を参照してください。 @@ -58,7 +62,7 @@ versions: 特定のプルリクエストやプルリクエストの更新の受信方法をカスタマイズするには、Issue またはプルリクエスト内で設定できます。 詳しい情報については、「[単一の通知をトリアージする](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} ー {% data variables.product.prodname_mobile %} アプリケーションでプッシュ通知を有効にできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)」を参照してください。 {% endif %} @@ -89,7 +93,7 @@ versions: ### 通知のインボックスをカスタマイズする -{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} または {% data variables.product.prodname_mobile %}{% endif %}のインボックスにある通知のグループにフォーカスするために、カスタムフィルタを作成できます。 たとえば、自分がコントリビュートしているオープンソースプロジェクトのカスタムフィルタを作成し、自分がメンションされているリポジトリの通知のみを表示することができます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 トリアージしているワークフローをカスタマイズする方法のその他の例については、「[通知をトリアージするためのワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。 +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. たとえば、自分がコントリビュートしているオープンソースプロジェクトのカスタムフィルタを作成し、自分がメンションされているリポジトリの通知のみを表示することができます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 トリアージしているワークフローをカスタマイズする方法のその他の例については、「[通知をトリアージするためのワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。 ### 通知の保持ポリシー diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 4b1f265a45c0d..64f25bd77b44d 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notification delivery options You can receive notifications for activity on {% data variables.product.product_name %} in the following locations. - - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." {% endif %} @@ -35,7 +39,7 @@ You can receive notifications for activity on {% data variables.product.product_ #### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - Triage multiple notifications at once. - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. @@ -45,7 +49,7 @@ The notifications inbox on {% data variables.product.product_name %}{% if curren - Create custom filters to focus on different notifications when you want. - Group notifications in your inbox by repository or date to get a quick overview with less context switching -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} In addition, the notifications inbox on {% data variables.product.prodname_mobile %} allows you to triage notifications in dark mode and receive push notifications for direct mentions. For more information, see "[Enabling push notifications with GitHub for mobile](#enabling-push-notifications-with-github-for-mobile)" or "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." {% endif %} @@ -75,7 +79,7 @@ You can customize notifications for a repository, for example, you can choose to #### Participating in conversations Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox. -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %}. +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. ![Participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -83,7 +87,7 @@ For example: - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications. - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating". -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}, then your notifications inbox will not have any updates. +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. ### Customizing your email notifications @@ -195,13 +199,15 @@ Choose how you want to receive workflow run updates for repositories that you ar {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Enabling push notifications with {% data variables.product.prodname_mobile %} When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. You can then enable push notifications for direct mentions within the app. You can only receive notifications for pushes to repositories on {% data variables.product.prodname_mobile %} at this time. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Enabling push notifications with {% data variables.product.prodname_ios %} 1. Above "Home", tap your profile photo. @@ -210,6 +216,7 @@ You can only receive notifications for pushes to repositories on {% data variabl 3. To update your notification settings, tap **Push notifications**. 4. To turn on push notifications for direct mentions, use the **Direct Mentions** toggle. +{% if currentVersion == "free-pro-team@latest" %} #### Enabling push notifications with {% data variables.product.prodname_android %} 1. Above "Home", tap your profile photo. @@ -217,3 +224,4 @@ You can only receive notifications for pushes to repositories on {% data variabl ![Settings icon for GitHub for Android](/assets/images/help/mobile/android-settings-icon.png) 3. To turn on push notifications for direct mentions, use the **Direct mentions** toggle. {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index d312bb24fa0e6..b2b3ba21b0c45 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: インボックスからの通知を管理する -intro: 'インボックスを使用して、メール{% if currentVersion == "free-pro-team@latest" %}とモバイル{% endif %}間で通知をすばやくトリアージして同期します。' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### インボックスについて -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)」を参照してください。 {% endif %} @@ -86,31 +90,16 @@ versions: ### カスタムフィルタでサポートされているクエリ -使用できるフィルタには、次の 3 種類があります。 +These are the types of filters that you can use: - `repo:` を使用したリポジトリによるフィルタ - `is:` を使用したディスカッションタイプによるフィルタ - - `reason:` を使用した通知理由によるフィルタ - -`repo:` フィルタを追加するには、リポジトリの所有者をクエリに含める必要があります。 たとえば、`repo:atom/atom` は、Atom Organization が所有する Atom リポジトリを表します。 + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -#### サポートされている `reason:` クエリ +#### Supported `repo:` queries -更新を受信した理由で通知をフィルタするには、`reason:` クエリを使用できます。 たとえば、自分 (または自分が所属する Team) がプルリクエストのレビューをリクエストされたときに通知を表示するには、`reason:review-requested` を使用します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)」を参照してください。 - -| クエリ | 説明 | -| ------------------------- | -------------------------------------------------------------------------------------------- | -| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | -| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | -| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | -| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | -| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | -| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | -| `reason:mention` | 直接@メンションされたとき。 | -| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% if currentVersion != "github-ae@latest" %} -| `reason:security-alert` | リポジトリに対してセキュリティアラートが発行されたとき。{% endif %} -| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | -| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | -| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. #### サポートされている `is:` クエリ @@ -138,3 +127,59 @@ versions: - `is:done` - `is:unread` - `is:read` + +#### サポートされている `reason:` クエリ + +更新を受信した理由で通知をフィルタするには、`reason:` クエリを使用できます。 たとえば、自分 (または自分が所属する Team) がプルリクエストのレビューをリクエストされたときに通知を表示するには、`reason:review-requested` を使用します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)」を参照してください。 + +| クエリ | 説明 | +| ------------------------- | -------------------------------------------------------------------------------------------- | +| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | +| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | +| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | +| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | +| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | +| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | +| `reason:mention` | 直接@メンションされたとき。 | +| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% if currentVersion != "github-ae@latest" %} +| `reason:security-alert` | リポジトリに対してセキュリティアラートが発行されたとき。{% endif %} +| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | +| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | +| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index b3a639bf8ef47..6bded781cab7a 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ versions: {% data reusables.notifications.access_notifications %} 1. 通知インボックスから、サブスクライブ解除する通知を選択します。 -2. **選択した** {% octicon "triangle-down" aria-label="The down triangle icon" %} ドロップダウンを使用して、[**Unsubscribe**] をクリックします。 ![メインインボックスからの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. **選択した** {% octicon "triangle-down" aria-label="The down triangle icon" %} ドロップダウンを使用して、[**Unsubscribe**] をクリックします。 ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### サブスクリプションページで通知をサブスクライブ解除する @@ -64,4 +64,4 @@ versions: - リポジトリの Watch 解除 - リポジトリのすべての通知を無視 - 通知を受け取るイベントの種類をカスタマイズ (Issue、プルリクエスト、リリース、ディスカッションが有効の場合) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md b/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md index dea0a6b3f86be..5cbcc3a2c4151 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md @@ -14,9 +14,11 @@ versions: リポジトリ中の Issue で、ユーザフィードバックの収集、ソフトウェアバグの報告、完了したいタスクの編成ができます。 Issueは、単なるソフトウェアのバグを報告する場所以上の働きをします。 +{% if currentVersion == "free-pro-team@latest" %} Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/ja-JP/content/github/managing-your-work-on-github/changing-project-board-visibility.md index e4d2edec8c8e2..4c77ebc8f3a7e 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: プロジェクトボードの表示設定の変更 -intro: 'Organization のオーナーあるいはプロジェクトボードの管理者は、プロジェクトボードをパブリックまたはプライベートに設定できます。' +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**ヒント:** プロジェクトボードをパブリックに設定すると、Organization のメンバーにはデフォルトで読み取りアクセスの権限が与えられます。 特定の Organization メンバーに書き込み権限や管理者権限を与えるには、参加している Team にプロジェクトボードへのアクセス権限を与えるか、プロジェクトボードにコラボレータとして追加してください。 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. 特定の Organization メンバーに書き込み権限や管理者権限を与えるには、参加している Team にプロジェクトボードへのアクセス権限を与えるか、プロジェクトボードにコラボレータとして追加してください。 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endtip %} -1. パブリックまたはプライベートに設定したいプロジェクトボードに移動します。 +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. [Visibility] の下にある、[**Public**] または [**Private**] を選択します。 次に、[**Save**] をクリックします。 ![[Public] と [Private] のラジオボタン](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/ja-JP/content/github/managing-your-work-on-github/copying-a-project-board.md index 1be6b89a765bb..1b55f4431ba9b 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ versions: 5. 必要に応じて、[Project board name] の下に、コピーしたプロジェクトボードの名前を入力します。 ![コピーされたプロジェクトボードの名前を入力するフィールド](/assets/images/help/projects/copied-project-board-name.png) 6. 必要に応じて、他の人に読んでもらうために、[Description] の下に、コピーしたプロジェクトボードについての説明を入力します。 ![コピーしたプロジェクトボードの説明を入力するフィールド](/assets/images/help/projects/copied-project-board-description.png) 7. 必要に応じて、[Automation settings] の下で、設定済みの自動化されたワークフローをコピーするかどうかを選択します。 このオプションはデフォルトで有効になっています。 詳しい情報については「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards/)」を参照してください。 ![コピーしたプロジェクトボードの自動化設定を選択](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. Organization が所有するプロジェクトボードをコピーする場合、[Visibility] の下で、コピーしたプロジェクトボードをパブリックにするかプライベートにするかを選択します。 ![コピーしたプロジェクトボードの表示設定を選択](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. [**Copy project**] をクリックします。 ![コピーを確定するボタン](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/ja-JP/content/github/managing-your-work-on-github/creating-a-project-board.md index a97686d695d98..7fe34fe851ad1 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ versions: {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ versions: {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/ja-JP/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 6dd6b9d47323f..8ba3ea46f221b 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: プルリクエストのリポジトリのリストをフィルタリングして、次の検索を行えます: - まだ[レビュー](/articles/about-pull-request-reviews)されていないプルリクエスト -- マージの前に[レビューが必要](/articles/about-required-reviews-for-pull-requests)なプルリクエスト +- マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なプルリクエスト - レビュー担当者が承認したプルリクエスト - レビュー担当者が変更を求めているプルリクエスト - 自分がレビューしたプルリクエスト diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md index b30fc95af491f..33e3394039ba2 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: 作業を管理するとき、{% data variables.product.product_name %} ラベルを作成して Issue とプルリクエストを分類することができます。 You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. -リポジトリへの読み取りアクセスを持つ人は、誰でもリポジトリのラベルを表示・検索できます。 ラベルの作成、編集、適用、削除をするためには、リポジトリに書き込みアクセスができなければなりません。 +リポジトリへの読み取りアクセスを持つ人は、誰でもリポジトリのラベルを表示・検索できます。 Anyone with triage access to a repository can apply/dismiss existing labels. ラベルの作成、編集、適用、削除をするためには、リポジトリに書き込みアクセスができなければなりません。 ### About default labels @@ -91,7 +91,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### 参考リンク -- [ラベルについて](/articles/about-labels) - "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index d4f2acb7a90c2..486e2600e8087 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -36,7 +36,7 @@ Issueについては、以下も検索に利用できます。 プルリクエストについては、検索を利用して以下の操作もできます。 - [ドラフト](/articles/about-pull-requests#draft-pull-requests)プルリクエストのフィルタリング: `is:draft` - まだ[レビュー](/articles/about-pull-request-reviews)されていないプルリクエストのフィルタリング: `state:open type:pr review:none` -- マージされる前に[レビューを必要とする](/articles/about-required-reviews-for-pull-requests)プルリクエストのフィルタリング: `state:open type:pr review:required` +- マージされる前に[レビューを必要とする](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)プルリクエストのフィルタリング: `state:open type:pr review:required` - レビュー担当者が承認したプルリクエストのフィルタリング: `state:open type:pr review:approved` - レビュー担当者が変更を要求したプルリクエストのフィルタリング: `state:open type:pr review:changes_requested` - [レビュー担当者](/articles/about-pull-request-reviews/)によるプルリクエストのフィルタリング: `state:open type:pr reviewed-by:octocat` diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-commits.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-commits.md index 44ff688aae976..ef3a55b482bed 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-commits.md @@ -48,10 +48,10 @@ versions: {% data reusables.search.date_gt_lt %} -| 修飾子 | サンプル | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) は、2016 年 1 月 1 日より前に作成されたコミットにマッチします。 | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits)は、2016 年 1 月 1 日以降にコミットされたコミットにマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) は、2016 年 1 月 1 日より前に作成されたコミットにマッチします。 | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | ### マージコミットのフィルタリング diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 8d869a54189c7..605d6720d6372 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: SAML SSO を設定すると、{% data variables.product.prodname_dotcom %} Organization のメンバーは {% data variables.product.prodname_dotcom %} 上の各自のユーザアカウントに引き続きログインできるようになります。 SAML SSO を使用する Organization 内のリソースにメンバーがアクセスすると、{% data variables.product.prodname_dotcom %} は認証のためにメンバーを IdP にリダイレクトします。 認証に成功すると、IdP はメンバーを {% data variables.product.prodname_dotcom %} にリダイレクトして戻し、そこでメンバーは Organization のリソースにアクセスできます。 -Enterprise のオーナーは、Enterprise アカウントのすべての Organization について SAML SSO を施行できます。 詳細は「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」を参照してください。 +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. 詳しい情報については、「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」参照してください。 {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ Organization で SAML SSO を有効化する前に、IdP を Organization に接 {% data variables.product.prodname_oauth_app %}を認可するために、Organization メンバーにはアクティブな SAML セッションが必要です。 {% data variables.contact.contact_support %} に連絡すれば、この要件をオプトアウトできます。 ただし、この要件をオプトアウトすることを {% data variables.product.product_name %} はお勧めしません。Organization でアカウント乗っ取りやデータ漏えいのリスクが高くなるからです。 +{% data reusables.saml.saml-single-logout-not-supported %} + ### サポートされているSAMLサービス {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ Organization で SAML SSO を有効化する前に、IdP を Organization に接 SAML SSO を有効化後、Organization に新しいメンバーを追加する方法はいくつかあります。 Organization のオーナーは、{% data variables.product.product_name %} で手作業または API を使って、新しいメンバーを招待できます。 詳細は {} の「[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization)」および「[メンバー](/rest/reference/orgs#add-or-update-organization-membership)」を参照してください。 -{% data reusables.organizations.team-synchronization %} - 新しいユーザを、Organization のオーナーから招待せずにプロビジョニングするには、`https://github.com/orgs/ORGANIZATION/sso/sign_up` の URL の _ORGANIZATION_ をあなたの Organization 名に置き換えてアクセスします。 たとえば、あなたの IdP にアクセスできる人なら誰でも、IdP のダッシュボードにあるリンクをクリックして、あなたの {% data variables.product.prodname_dotcom %} Organization に参加できるよう、IdP を設定できます。 IdP が SCIM をサポートしている場合、{% data variables.product.prodname_dotcom %} は、IdP でアクセス権限が付与されたとき Organization に参加するよう自動的にメンバーを招待できます。 SAML IdP での メンバーの {% data variables.product.prodname_dotcom %} Organization へのアクセス権限を削除すると、そのメンバーは {% data variables.product.prodname_dotcom %} Organization から自動的に削除されます。 詳しい情報については「[SCIMについて](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index e86afea2ef66d..b450f9d921b4e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ Organization の {% data variables.product.product_name %} の SCIM API と連 - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。 +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index 5a0be7f54eae7..10dc7365e2ad0 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ Organization が所有しているリポジトリで外部のコラボレータ {% data reusables.organizations.people_tab_outside_collaborators %} 5. [**X pending collaborators**] をクリックします。 ![[Pending collaborators] ボタン](/assets/images/help/organizations/pending-collaborator-list.png) 6. 招待をキャンセルする人の隣で、[**Cancel invitations**] をクリックします。 ![[Cancel invitation] ボタン](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. [**Cancel invitations for pending collaborators**] をクリックします。 ![キャンセルの確認ボタン](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. [**Cancel invitations for pending collaborators**] をクリックします。 ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md index 750ef4b2fb04a..d8cf32f692ebc 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md @@ -6,8 +6,8 @@ versions: enterprise-server: '>=2.22' --- -{% data variables.product.prodname_actions %} の支払いを管理する -{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} ### Organization の {% data variables.product.prodname_actions %} 権限について diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md index 4518bee2a5c8d..e821691e3c0f0 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 37f5984aa9bf8..d9c45b5812957 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Organization のセキュリティおよび分析設定を管理する intro: '{% data variables.product.prodname_dotcom %} 上の Organization のプロジェクトでコードを保護し分析する機能を管理できます。' permissions: Organization のオーナーは、Organization のリポジトリのセキュリティおよび分析設定を管理できます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### セキュリティおよび分析設定の管理について -{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 +{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Enabling or disabling a feature for all existing repositories +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +1. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 + {% if currentVersion == "free-pro-team@latest" %} + ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 + {% if currentVersion == "free-pro-team@latest" %} + ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 + {% if currentVersion == "free-pro-team@latest" %} + ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -### Enabling or disabling a feature for all new repositories when they are added +### Enabling or disabling a feature automatically when new repositories are added 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. [Configure security and analysis features] にある機能の右側で、Organization の新規のリポジトリに対して機能をデフォルトで有効または無効にします。 ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Allowing Dependabot to access private repositories -{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." 1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) 1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. 1. Click **Select repositories**. - +{% endif %} ### 参考リンク -{% if currentVersion == "free-pro-team@latest" %}- [リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository) -- [シークレットスキャンニングについて](/github/administering-a-repository/about-secret-scanning) -- [依存関係を自動的に更新する](/github/administering-a-repository/keeping-your-dependencies-updated-automatically) -{% endif %} +- 「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository)」 +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) - [プロジェクトの依存関係にある脆弱性を管理する](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index 745c024e52eb7..a88a6ef2c84ba 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ Organization のオーナーと、プロジェクトボードに対する管理 ### プロジェクトボードの可視性 -{% data reusables.project-management.project-board-visibility %}プロジェクトボードの可視性を、プライベートからパブリックへ、またその逆に変更することができます。 詳細は「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」を参照してください。 +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. 詳細は「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」を参照してください。 ### 参考リンク 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 4ea25ff8d1b84..ba9089e98e4f7 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,91 +43,94 @@ 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** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| マイルストーンの適用 | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| [セキュリティアドバイザリ](/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 %}{% if currentVersion == "free-pro-team@latest" %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| リポジトリアクション | 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 %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| マイルストーンの適用 | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| 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#granting-access-to-security-alerts) | | | | | **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** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index eda65531519ec..38454becd7c52 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -64,8 +64,8 @@ The audit log lists events triggered by activities that affect your organization | [`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. 詳しい情報については、「[シークレットスキャニングについて](/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) | Organization の Team に関連するすべてのアクティビティが対処です。{% endif %} +| [`sponsors`](#sponsors-category-actions) | スポンサーボタンに関連するすべてのアクティビティが対象です (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %} +| [`Team`](#team-category-actions) | Organization内のチームに関連するすべてのアクティビティを含みます。 | | [`team_discussions`](#team_discussions-category-actions) | Organization の Team ディスカッションに関連するすべてのアクティビティが対象です。 | 次の用語を使用すれば、特定の一連の行動を検索できます。 例: @@ -198,7 +198,7 @@ An overview of some of the most common actions that are recorded as events in th | アクション | 説明 | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `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. | +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | #### `dependabot_security_updates` category actions @@ -325,6 +325,8 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | アクション | 説明 | | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." | +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | | `audit_log_export` | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。 | | `block_user` | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/articles/blocking-a-user-from-your-organization)ときにトリガーされます。 | | `cancel_invitation` | Organization の招待が取り消されている場合にトリガーされます。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} @@ -448,15 +450,17 @@ For more information about the audit log REST API, see "[Organizations](/rest/re #### `repo` カテゴリアクション -| アクション | 説明 | -| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | -| `add_member` | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。 | -| `add_topic` | リポジトリの管理者がリポジトリに[トピックを追加する](/articles/classifying-your-repository-with-topics)ときにトリガーされます。 | +| アクション | 説明 | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `add_member` | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。 | +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." | +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | リポジトリの管理者が[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% if enterpriseServerVersions contains currentVersion %} -| `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)ときにトリガーされます。 | +| `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)ときにトリガーされます。 | | `config.unlock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/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).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} @@ -465,12 +469,12 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | `enable` | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.{% endif %} | `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} -| `remove_topic` | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。 | -| `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 | -| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | -| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 | +| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `remove_topic` | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。 | +| `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 | +| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | +| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 | | `unarchived` | Triggered when a repository admin unarchives a repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret.{% endif %} @@ -560,7 +564,7 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)") | | `sponsor_sponsorship_tier_change` | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を変更する](/articles/changing-your-sponsorship-tiers)」を参照) | @@ -569,20 +573,18 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` カテゴリアクション -| アクション | 説明 | -| -------------------- | ---------------------------------------------------------------------------------------------------- | -| `add_member` | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。 | -| `add_repository` | リポジトリの管理が Team に任せられるときにトリガーされます。 | -| `change_parent_team` | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。 | -| `change_privacy` | Team のプライバシー レベルが変更されるときにトリガーされます。 | -| `create` | 新たな Team が作成されるときにトリガーされます。 | -| `destroy` | Team が Organization から削除されるときにトリガーされます。 | -| `remove_member` | Organization のメンバーが[Team から削除される](/articles/removing-organization-members-from-a-team)ときにトリガーされます。 | -| `remove_repository` | リポジトリが Team の管理下でなくなるときにトリガーされます。 | -{% endif %} +| アクション | 説明 | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。 | +| `add_repository` | リポジトリの管理が Team に任せられるときにトリガーされます。 | +| `change_parent_team` | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。 | +| `change_privacy` | Team のプライバシー レベルが変更されるときにトリガーされます。 | +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. #### `team_discussions` category actions diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index b2f38c494a180..61cad6f13e229 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: 1 つの {% data variables.product.prodname_dotcom %} Team には、最大 5 つまでの IdP グループを接続できます。。 1 つのIdP グループは制限なく複数の {% data variables.product.prodname_dotcom %} Team に割り当てることができます。 +Team synchronization does not support IdP groups with more than 5000 members. + いったん {% data variables.product.prodname_dotcom %} Team が IdP グループに接続されたら、IdP 管理者はアイデンティティプロバイダを通して Team メンバーシップを変更する必要があります。 Team のメンバーシップを {% data variables.product.product_name %} で、または API を使用して管理することはできません。 IdP を通じた Team メンバーシップ変更はすべて、Team 同期ボットによる変更として {% data variables.product.product_name %} の Audit log に記載されます。 IdP は、Team メンバーシップのデータを 1 時間に 1 回 {% data variables.product.prodname_dotcom %} に送信します。 Team を IdP グループに接続すると、Team メンバーが削除される場合があります。 詳細は「[同期される Team のメンバーに関する要件](#requirements-for-members-of-synchronized-teams)」を参照してください。 @@ -27,19 +29,22 @@ Team 同期を API で管理することもできます。 詳しい情報につ ### 同期される Team のメンバーに関する要件 -Team の同期を有効化した後、ユーザが {% data variables.product.prodname_dotcom %} で引き続き同じ SSO アイデンティティの SAML SSO を使用して認証し続け、接続先の IdP グループのメンバーであり続ける場合、各 Team メンバーのメンバーシップデータが同期されます。 +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -既存の Team またはグループのメンバーは、{% data variables.product.prodname_dotcom %} でその Team から自動的に削除されます。 SSO を使用して Organization または Enterprise アカウントに認証されていない既存の Team またはグループのメンバーは、リポジトリにアクセスできなくなります。 接続先の IdP グループにいない既存の Team またはグループのメンバーも、リポジトリにアクセスできなくなる可能性があります。 +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." 削除された Team メンバーは、SSO を使って Organization または Enterprise アカウントに認証され、接続先の IdP グループに移動すれば、再び Team に自動的に追加できます。 -意図しない Team メンバーの削除を避けるために、Organization または Enterprise アカウントで SAML SSO を施行し、メンバーシップデータを同期するため新しい Team を作成し、IdP グループのメンバーシップを確認してから既存の Team を同期することをおすすめします。 詳細は「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 +意図しない Team メンバーの削除を避けるために、Organization または Enterprise アカウントで SAML SSO を施行し、メンバーシップデータを同期するため新しい Team を作成し、IdP グループのメンバーシップを確認してから既存の Team を同期することをおすすめします。 For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Organization が Enterprise アカウントによって所有されている場合、その Enterprise アカウントに Team の同期を有効化すると、Organization レベルの Team の同期はオーバーライドされます。 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)」を参照してください。 +Organization が Enterprise アカウントによって所有されている場合、その Enterprise アカウントに Team の同期を有効化すると、Organization レベルの Team の同期はオーバーライドされます。 For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." ### 必要な環境 -Team をアイデンティティプロバイダグループに接続するには、Organization または Enterprise オーナーが自分の Organization または Enterprise のアカウントについて Team 同期を有効にする必要があります。 詳細は、「[Organization の Team 同期を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)」と「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)」を参照してください。 +Team をアイデンティティプロバイダグループに接続するには、Organization または Enterprise オーナーが自分の Organization または Enterprise のアカウントについて Team 同期を有効にする必要があります。 For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." Team メンバーを誤って削除しないように、お使いの IdP の管理ポータルにアクセスし、現在の各 Team メンバーが、接続しようとしている IdP グループにも属していることを確認してください。 アイデンティティプロバイダにこうしたアクセスができない場合は、IdP 管理者にお問い合わせください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index f305f13bb57d0..8df136644e908 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ Organization に対する SAML シングルサインオンを有効にすると {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..6d20b0cf8bc5b --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. + +| IdP | SAML | User provisioning | Team の同期 | +| ------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory フェデレーションサービス (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..47f27234131fb --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} オプションで、SAML プロビジョニングを有効にして、別々にデプロビジョニングすることもできます。 + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. SAML プロビジョニングを有効にすると、Enterprise アカウントの SAML 設定で保護されているリソースに Enterprise のメンバーがアクセスするたびに、その SAML アサーションによってプロビジョニングがトリガーされすま。 + +SCIM 呼び出しまたは SAML アサーションのたびに、{% data variables.product.product_name %} はユーザが所属する IdP グループをチェックし、以下の操作を実行します。 + +- ユーザが、Enterprise アカウントによって所有されている Organization に対応する IdP グループのメンバーであり、現在その Organization のメンバーでない場合は、そのユーザーを Organization に追加する (SAML アサーション) か、Organization に参加するよう招待メールを送信 (SCIM 呼び出し) します。 +- Enterprise アカウントによって所有される Organization にそのユーザが参加する既存の招待がある場合は、キャンセルします。 + +SCIM 呼び出しのたびに、また SAML デプロビジョニングを有効にしている場合には SAML アサーションのたびに、 {% data variables.product.product_name %} は以下の操作も実行します。 + +- ユーザが、Enterprise アカウントによって所有されている Organization に対応する IdP グループのメンバーではなく、現在その Organization のメンバーである場合は、そのユーザーを Organization から削除します。 + +デプロビジョニングによって、最後に残ったオーナーが Organization から削除されると、その Organization はオーナーのいない状態になります。 Enterprise オーナーは、オーナーのいない Organization の所有権を取得できます。 詳しい情報については、「[Enterprise アカウントでオーナーのいない Organization を管理する](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)」参照してください。 + +Okta を使用して Enterprise アカウントのユーザプロビジョニングを有効にするには、「[Okta を使用して Enterprise アカウントの SAML シングルサインオンおよび SCIM を設定する](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index 522281760330d..abdfe20dd24f6 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ SCIM を有効にすると、Okta で {% data variables.product.prodname_ghe_clo 1. ドロップダウンメニューの右に `.*.*` と入力します。 1. [**Save**] をクリックします。 {% data reusables.saml.okta-view-setup-instructions %} -1. 設定手順の情報を使用して、Enterprise アカウントの SAML を有効にします。 詳細は「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」を参照してください。 +1. 設定手順の情報を使用して、Enterprise アカウントの SAML を有効にします。 詳しい情報については、「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」参照してください。 ### Okta でグループを作成する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..c5cb842c9c420 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %}詳細は「[Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)」を参照してください。 + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} プライベートベータに参加していない場合、Enterprise アカウント に対して SCIM はサポートされません。 For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. + +{% endnote %} + +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. **Sign on URL**フィールドに、使用する IdP のシングルサインオンのリクエストのための HTTPS エンドポイントを入力してください。 この値は Idp の設定で使用できます。 ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png) +8. [**Public Certificate**] で、証明書を貼り付けて SAML の応答を認証します。 ![アイデンティティプロバイダからの公開の証明書のフィールド](/assets/images/help/saml/saml_public_certificate.png) +9. SAML 発行者からのリクエストの完全性を確認するには、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png) +10. Enterprise で SAML SSO を有効化する前に、[**Test SAML configuration**] をクリックして、入力した情報が正しいか確認します。 ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png) +11. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 9972b33de75cf..fad4a28e578b9 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ Enterprise のオーナーは、特定の IP アドレスに対する許可リ {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする - -{% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 - -Enterprise のオーナーは、Enterprise アカウントが所有するすべての Organization 全体で、SAML IdP によって SAML SSO と中央での認証を有効にすることができます。 Enterprise アカウントで SAML SSO を有効にした後は、SAML SSO は Enterprise アカウントによって所有されているすべての Organization に対してデフォルトで有効となります。 すべてのメンバーは、自分がメンバーである Organization にアクセスするために SAML SSO を使用して認証するよう求められ、企業のオーナーは Enterprise アカウントにアクセスする際に SAML SSO を使用して認証するよう求められます。 - -{% data reusables.saml.about-saml-access-enterprise-account %}詳細は「[Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)」を参照してください。 - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} プライベートベータに参加していない場合、Enterprise アカウント に対して SCIM はサポートされません。 詳しい情報については、「[Enterprise アカウントで Organization のユーザプロビジョニングを管理する](#managing-user-provisioning-for-organizations-in-your-enterprise-account)」参照してください。 - -{% note %} - -**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. - -{% endnote %} - -Okta を使用して SAML を有効にする方法については、「[Okta を使用して Enterprise アカウントの SAML シングルサインオンおよび SCIM を設定する](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)」を参照してください。 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. **Sign on URL**フィールドに、使用する IdP のシングルサインオンのリクエストのための HTTPS エンドポイントを入力してください。 この値は Idp の設定で使用できます。 ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url_business.png) -7. または、[**Issuer**] フィールドに、SAML の発行者の名前を入力します。 これにより、送信メッセージの信ぴょう性が検証されます。 ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png) -8. [**Public Certificate**] で、証明書を貼り付けて SAML の応答を認証します。 ![アイデンティティプロバイダからの公開の証明書のフィールド](/assets/images/help/saml/saml_public_certificate.png) -9. SAML 発行者からのリクエストの完全性を確認するには、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 その後、[Signature Method] および [Digest Method] のドロップダウンから、SAML 発行者が使用するハッシュアルゴリズムを選択します。 ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png) -10. Enterprise で SAML SSO を有効化する前に、[**Test SAML configuration**] をクリックして、入力した情報が正しいか確認します。 ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png) -11. [**Save**] をクリックします。 - -### Enterprise アカウントで Organization のユーザプロビジョニングを管理す - -Enterprise のオーナーは、Enterprise アカウントの Organization のメンバーシップを直接アイデンティティプロバイダ (IdP) から管理できます。 - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} オプションで、SAML プロビジョニングを有効にして、別々にデプロビジョニングすることもできます。 - -IdP で SCIM を構成すると、IdP でグループのメンバーシップに変更を加えるたびに IdP が {% data variables.product.prodname_dotcom %} に SCIM 呼び出しを行い、対応する組織のメンバーシップを更新します。 SAML プロビジョニングを有効にすると、Enterprise アカウントの SAML 設定で保護されているリソースに Enterprise のメンバーがアクセスするたびに、その SAML アサーションによってプロビジョニングがトリガーされすま。 - -SCIM 呼び出しまたは SAML アサーションのたびに、{% data variables.product.product_name %} はユーザが所属する IdP グループをチェックし、以下の操作を実行します。 - -- ユーザが、Enterprise アカウントによって所有されている Organization に対応する IdP グループのメンバーであり、現在その Organization のメンバーでない場合は、そのユーザーを Organization に追加する (SAML アサーション) か、Organization に参加するよう招待メールを送信 (SCIM 呼び出し) します。 -- Enterprise アカウントによって所有される Organization にそのユーザが参加する既存の招待がある場合は、キャンセルします。 - -SCIM 呼び出しのたびに、また SAML デプロビジョニングを有効にしている場合には SAML アサーションのたびに、 {% data variables.product.product_name %} は以下の操作も実行します。 - -- ユーザが、Enterprise アカウントによって所有されている Organization に対応する IdP グループのメンバーではなく、現在その Organization のメンバーである場合は、そのユーザーを Organization から削除します。 - -デプロビジョニングによって、最後に残ったオーナーが Organization から削除されると、その Organization はオーナーのいない状態になります。 Enterprise オーナーは、オーナーのいない Organization の所有権を取得できます。 詳しい情報については、「[Enterprise アカウントでオーナーのいない Organization を管理する](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)」参照してください。 - -Okta を使用して Enterprise アカウントのユーザプロビジョニングを有効にするには、「[Okta を使用して Enterprise アカウントの SAML シングルサインオンおよび SCIM を設定する](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)」を参照してください。 - -### Enterprise アカウントで Organization の Team 同期を管理する - -Enterprise オーナーが IdP と {% data variables.product.product_name %} の間で Team の同期を有効化すると、Organization のオーナーとチームメンテナは Enterprise アカウントで所有されている Organization の Team を IdP グループに接続できるようになります。 - -{% data reusables.identity-and-permissions.about-team-sync %} - -Azure AD で Enterprise アカウントとの Team 同期を使用できます。 - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -Organization ごとの Team 同期の設定と管理も可能です。 詳細は「[Organization の Team 同期を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)」を参照してください。 - -#### 必要な環境 - -Enterprise アカウントに対して Team の同期を有効化する前提条件は、以下のとおりです。 - - あなた、または Azure AD の管理者は Azure AD のグローバル管理者、または特権ロール管理者になっている必要があります。 - - サポート対象の IdP で、Enterprise アカウントの Organization に対して SAMLシングルサインオンを有効にする必要があります。 詳しい情報については、「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」参照してください。 - - SAML SSO とサポートされる IdP を使用して Enterprise アカウントに認証される必要があります。 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。 - -#### Azure AD で Team の同期を管理する - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Enterprise アカウントに接続するアイデンティティプロバイダのテナント情報を確認してから、[**Approve**] をクリックします。 ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png) -8. Team 同期を無効にするには、 [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png) - ### Enterprise アカウントの SSH 認証局を管理する Enterprise オーナーは、Enterprise アカウントの SSH 認証局 (CA) を追加および削除できます。 @@ -203,3 +112,7 @@ CAを削除すると、元に戻すことはできません。 同じCAを使用 {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### 参考リンク + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md index 0c9ac7508a6cd..84528000d4a6a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + 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 671edbda8e938..1579cd05aadce 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 @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. {% data variables.product.prodname_enterprise %} の詳細は、「[{% data variables.product.company_short %} の製品](/github/getting-started-with-github/githubs-products#github-enterprise)」を参照してください。 For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." @@ -27,11 +29,13 @@ After you assign a license for {% data variables.product.prodname_vss_ghe %} to 3. On {% data variables.product.prodname_dotcom_the_website %}, create at least one organization owned by your enterprise account. For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." -4. The subscriber must create a user account on {% data variables.product.prodname_dotcom_the_website %}, and the email address for the account must be the same email address as the email address in the {% data variables.product.prodname_vs %} portal. For more information, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." - ### Inviting a subscriber to use {% data variables.product.prodname_enterprise %} -To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber must join an organization owned by your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Organization owners can invite new members to an organization. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." ### Viewing {% data variables.product.prodname_enterprise %} licensing diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..aa2633281dfe7 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Enterprise アカウントで Organization の Team 同期を管理する +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +Organization ごとの Team 同期の設定と管理も可能です。 詳細は「[Organization の Team 同期を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)」を参照してください。 + +### 必要な環境 + +あなた、または Azure AD の管理者は Azure AD のグローバル管理者、または特権ロール管理者になっている必要があります。 + +サポート対象の IdP で、Enterprise アカウントの Organization に対して SAMLシングルサインオンを有効にする必要があります。 詳しい情報については、「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」参照してください。 + +SAML SSO とサポートされる IdP を使用して Enterprise アカウントに認証される必要があります。 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。 + +### Azure AD で Team の同期を管理する + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png) +8. Team 同期を無効にするには、 [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index 1196ad42c21cb..77a489af09d75 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -ユーザのデプロビジョニングを有効にして Enterprise アカウントの Organization メンバーシップを管理していると、Organization のオーナーがいなくなることもあります。 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。 +ユーザのデプロビジョニングを有効にして Enterprise アカウントの Organization メンバーシップを管理していると、Organization のオーナーがいなくなることもあります。 For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." {% data reusables.enterprise-accounts.access-enterprise %} 2. 検索フィールドの右側で、[**X unowned**] をクリックします。 ![オーナーのいない Organization を表示するボタン](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index b110ca0516052..136ad456371a1 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,6 +18,8 @@ Enterprise アカウントに対する SAML シングルサインオンを有効 {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index c9f58c0d8b15d..a0c077b2f70c3 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -22,8 +22,8 @@ For more information about managing billing managers, see "[Inviting people to m {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Under "User +1. 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. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Enterprise 支払い設定のライセンスおよびプラン情報](/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 %}**. +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index c59c3d3ba0e8d..91663d82d16bd 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -39,20 +39,20 @@ Git では、オーサー日付とは、誰かが `git commit` でコミット $ git show Your commit SHA number --pretty=fuller commit Your commit SHA number Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` 作者日付とコミット日付が異なる場合は、URL のコミット日付を手動で変更して、コミットの詳細を表示できます。 例: -- この URL の作者日付は `2016-07-13`: +- この URL の作者日付は `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- この URL は、コミット日付 `2016-07-19` を使っています: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- この URL は、コミット日付 `2018-04-10` を使っています: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` URL をコミット日付で修正して開くと、コミットの詳細を見ることができます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 224816a015b87..852af46e61fc0 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### カウントされるコントリビューション -#### Issue およびプルリクエスト +#### Issues, pull requests and discussions -Issue とプルリクエストは、フォークではなく、スタンドアロンのリポジトリで開かれた場合、コントリビューショングラフに表示されます。 +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. #### コミット 次の条件の**すべて**を満たしている場合、コミットはコントリビューショングラフに表示されます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 4d1d7ca9f4756..7a6f941dd9fa3 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -24,7 +24,7 @@ versions: {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %} 8. オプションで、自分が割り当てられているレビュー担当者のスケジュールされたリマインダーを受け取るには、[**Review requests assigned to you**] を選択します。 ![[Review requests assigned to you] チェックボックス](/assets/images/help/profile/scheduled-reminders-your-requests.png) -9. オプションで、自分がメンバー担っている Team に割り当てられているレビュー担当者のスケジュールされたリマインダーを受け取るには、[**Review requests assigned to your team**] を選択します。 ![[Review requests assigned to your team] チェックボックス](/assets/images/help/profile/scheduled-reminders-your-team-requests.png) +9. オプションで、自分がメンバーになっている Team に割り当てられているレビュー担当者のスケジュールされたリマインダーを受け取るには、[**Review requests assigned to your team**] を選択します。 ![[Review requests assigned to your team] チェックボックス](/assets/images/help/profile/scheduled-reminders-your-team-requests.png) {% data reusables.reminders.real-time-alerts %} ![[Enable real-time alerts] チェックボックス](/assets/images/help/settings/scheduled-reminders-real-time-alerts-personal.png) {% data reusables.reminders.create-reminder %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index fc04420622d21..174d11ce61345 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,7 +14,7 @@ versions: For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. {% data reusables.user_settings.access_settings %} -1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) 1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index cbb2d8b029f68..b57ff84ab20d6 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,7 +30,8 @@ You can also {% if currentVersion == "free-pro-team@latest" %}invite{% else %}ad | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | [個人リポジトリへのコラボレータの招待](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) | | | Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | [保護されたブランチについて](/github/administering-a-repository/about-protected-branches) | | リポジトリを削除する | 「[リポジトリを削除する](/github/administering-a-repository/deleting-a-repository)」 | | Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} @@ -63,7 +64,8 @@ Collaborators can also perform the following actions. | アクション | 詳細情報 | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | 「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」 | +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Create, edit, and delete comments on commits, pull requests, and issues in the repository |
      • "[About issues](/github/managing-your-work-on-github/about-issues)"
      • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
      • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
      | | Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | | Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index b75dac80ba43e..7339f4f84026b 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ versions: 管理者アクセス権を持つプロジェクトボードのオーナーとコラボレーターは、プロジェクトボードを完全制御できます。 プロジェクトボードのコラボレーターによって許可される権限すべてに加え、管理者権限を持つプロジェクトボードのオーナーとコラボレーターは、次の操作が可能です: - [コラボレーターを管理、表示、追加する](/articles/managing-access-to-your-user-account-s-project-boards) -- [プロジェクトボードをパブリックまたはプライベートとして設定する](/articles/changing-project-board-visibility) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) - [プロジェクトボードを削除する](/articles/deleting-a-project-board/) - [プロジェクトボードをクローズする](/articles/closing-a-project-board/) - [クローズしたプロジェクトボードを再オープンする](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ versions: ### プロジェクトボードの可視性 -プロジェクトボードの可視性を、プライベートからパブリックへ、またその逆に変更することができます。 デフォルトでは、ユーザー所有のプロジェクトボードはプライベートです。 詳細は「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」を参照してください。 +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. デフォルトでは、ユーザー所有のプロジェクトボードはプライベートです。 詳細は「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」を参照してください。 ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md index 0d263f4248caf..aa6880fdde8b5 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md @@ -62,7 +62,7 @@ To ensure that commits are attributed to you and appear in your contributions gr ### Git のコミットメールアドレスを設定する -`git config`コマンドを使用して、Git コミットに関連付けたられているメールアドレスを変更できます。 設定した新しいメールアドレスは、コマンドラインから {% data variables.product.product_name %} にプッシュするこれからのコミットに表示されます。 コミットメールアドレスを変更する前のコミットは、まだ過去のメールアドレスに関連付けられます。 +`git config`コマンドを使用して、Git コミットに関連付けられているメールアドレスを変更できます。 設定した新しいメールアドレスは、コマンドラインから {% data variables.product.product_name %} にプッシュするこれからのコミットに表示されます。 コミットメールアドレスを変更する前のコミットは、まだ過去のメールアドレスに関連付けられます。 #### コンピュータにあるすべてのリポジトリ用にメールアドレスを設定する diff --git a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md index 8254f3970a274..ab6a7724e07cd 100644 --- a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com、GitHub Enterprise Server、およびあなたがいずれかの製品にアップロードする情報は、米輸出管理規則（EAR）を含む貿易管理規制の対象となる場合があります。 Export Administration Regulations (the EAR). -GitHub のビジョンは、開発者たちがどこからでもコラボレーションに参加できるグローバルなプラットフォームを築くことです。 当社は、政府の命令を精査し、ユーザーおよびお客様が法律で要求される範囲を超えた影響を受けることがないようにする責任を真摯に受け止めています。 こうした取り組みには、オープンソースプロジェクトのサービスを含むパブリックリポジトリサービスを利用可能かつアクセス可能に保つことで、制裁対象地域の開発者が参加する個人的なコミュニケーションをサポートすることも含まれます。 +GitHub のビジョンは、開発者たちがどこからでもコラボレーションに参加できるグローバルなプラットフォームを築くことです。 当社は、政府の命令を精査し、ユーザーおよびお客様が法律で要求される範囲を超えた影響を受けることがないようにする責任を真摯に受け止めています。 This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. -To comply with U.S. trade control laws, GitHub made some required changes to the way we conduct our services. As U.S. trade controls laws evolve, we will continue to work with U.S. regulators about the extent to which we can offer free code collaboration services to developers in sanctioned markets. 当社は、これらの無料サービスを提供することが、 foreign policy of encouraging the free flow of information and free speech in those markets. 当社のアプローチと制裁がグローバルなソフトウェアコラボレーションに与える影響について詳しくは、[制裁に関するブログ](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/)をご覧ください。 +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Although we've provided the following information below for your convenience, it is ultimately your responsibility to ensure that your use of GitHub's products and services complies with all applicable laws and regulations, including U.S. export control laws. @@ -25,9 +25,9 @@ Although we've provided the following information below for your convenience, it ユーザには、GitHub.com で開発および共有するコンテンツが、EAR や米国際武器取引規制（ITAR）などの米輸出管理法を遵守していることを確認する責任があります。 export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). [GitHub.com](https://github.com) で利用可能なクラウドホスト型サービスは、ITAR に基づいてデータをホストするように設計されておらず、現在、国ごとにリポジトリアクセスを制限する機能を提供していません。 ITAR などの輸出管理対象データを扱うコラボレーションを検討している場合は、GitHub のオンプレミス製品である [GitHub Enterprise Server](https://enterprise.github.com) を検討することをお勧めします。 -アメリカ合衆国の祝日 米貿易管理法により、特定の国および地域のユーザが利用できる GitHub.com サービスは制限されます。 GitHub may allow users in or ordinarily resident in countries and territories subject to U.S. GitHub は、米国の制裁の対象となる国や地域に所在または通常居住しているユーザが、米財務省の外国資産管理局（OFAC）によって発行された承認に従って、個人通信のために GitHub.com の特定の無料サービスにアクセスすることを許可する場合があります。 Treasury Department’s Office of Foreign Assets Controls (OFAC). 対象の国や地域に所在または通常居住している人物は、GitHub.com サービスにアクセスするときに IP プロキシ、VPN、またはその他の方法を使用して自身の所在地を偽装することを禁じられており、また非営利目的の個人的な通信にのみ GitHub.com を使用できます。 +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -特別指定国民（SDN）および米国およびその他の適用法の下で拒否または遮断されたその他の人物は、GitHub.com へのアクセスまたは使用を禁止されています。 and other applicable law are prohibited from accessing or using GitHub.com. また、ユーザは、制裁対象国の政府を含む上記の人物のために、またはその代理として GitHub.com を使用することはできません。 さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。 +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. また、ユーザは、制裁対象国の政府を含む上記の人物のために、またはその代理として GitHub.com を使用することはできません。 さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。 #### GitHub Enterprise Server @@ -41,7 +41,7 @@ GitHub Enterprise Server は商用の大衆市場製品であり、`5D992.c` の #### On which countries and territories are U.S. government sanctions applied? -クリミア、キューバ、イラン、北朝鮮、シリアです。 +クリミア、キューバ、イラン、北朝鮮、シリアです。 With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. #### 制裁対象国/地域に住んでいない人や、制裁対象国/地域と職業的なつながりを持たない人がアクセスしたり異議を申し立てたりすることができるよう、GitHub は何か対策をしていますか？ @@ -55,23 +55,23 @@ Travel in these regions may impact your account status, but availability may be #### 何が利用できて何が利用できないのですか？ -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -However, due to U.S. 米国の貿易管理法の制限により、GitHub は米国の制裁対象地域のアカウントにプライベートリポジトリサービスと有料サービスを提供できません。 sanctioned regions like North Korea, Iran, Syria, and Crimea. The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. -For paid organizational accounts in sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 - 当社は、これらの無料サービスを提供することが、 各地域での情報の自由な流れと言論の自由を奨励するという米国の外交政策をサポートすることに繋がると信じています。 +GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. #### 対象のユーザをどのように定義しているのですか？ -If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. こうした法的制限の対象となるユーザやお客様の所在地の判断は、IP アドレスや支払い履歴など、いくつもの根拠から導き出されます。 なお、国籍と民族は制裁によるユーザの制限には使用されません。 +If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. こうした法的制限の対象となるユーザやお客様の所在地の判断は、IP アドレスや支払い履歴など、いくつもの根拠から導き出されます。 なお、国籍と民族は制裁によるユーザの制限には使用されません。 #### Organization アカウントにはどのような影響がありますか？ -If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. -The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### 貿易制限のあるユーザのプライベートリポジトリを公開できますか？ @@ -81,3 +81,16 @@ The restriction suspends access to private repository services and paid services 残念ながら、当社による法律の解釈では、米国政府の許可がない限り、プライベートリポジトリのコンテンツのダウンロードまたは削除を許可することはできません。 GitHub Enterprise Server is a self-hosted virtual appliance that can be run within Customer’s own datacenter or virtual private cloud. We will strongly advocate, with U.S. 私たちは、貿易制限のあるユーザがプライベートリポジトリのコンテンツを確保する権利を、米国の規制当局に強く主張する予定です。 また、制裁対象市場の開発者が GitHub サービスをもっと利用できるようになるよう求め、開発者のグローバルな個人通信をサポートすることで実現するコードコラボレーションの重要性をさらに強調するつもりです。 +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/ja-JP/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/ja-JP/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index af0057706ffed..bd697297bec82 100644 --- a/translations/ja-JP/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/ja-JP/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ versions: ### 3. 他のサイトポリシーについての限定的な免責 -セキュリティ調査活動が当社の[関連するサイトポリシー](/categories/site-policy/)に反しているものの、当社のBug Bounty Programの規約には従っている限りにおいて、本Bug Bounty Programの下、セキュリティ調査を許可するという限定された目的のみに限り、これらの制限を免除します。 前述の通り、疑問がある場合は、まずご質問ください。 +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. 前述の通り、疑問がある場合は、まずご質問ください。 diff --git a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md index 8502452463707..11376b0e95bf8 100644 --- a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **December 30, 2020** +Effective date: **January 6, 2021** GitHubは、お客様のデータを当社が利用する方法、お客様のデータを当社が収集する方法、およびお客様のデータを共有する対象について、高い透明性を提供します。 To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -25,12 +25,9 @@ GitHubは、お客様のデータを当社が利用する方法、お客様の | Braintree (PayPal) | プランのクレジットカード決済処理業者 | 米国 | 米国 | | Clearbit | マーケティングデータのエンリッチメントサービス | 米国 | 米国 | | Discourse | コミュニティフォーラムのソフトウェアプロバイダ | 米国 | 米国 | -| DiscoverOrg | マーケティングデータのエンリッチメントサービス | 米国 | 米国 | | Eloqua | マーケティングキャンペーンの自動化 | 米国 | 米国 | | Google Apps | 社内インフラストラクチャ | 米国 | 米国 | | Google Analytics | Analytics and performance | 米国 | 米国 | -| LinkedIn Navigator | Data enrichment service | 米国 | 米国 | -| Magic Robot | キャンペーンレポート (Salesforceのアドオン) | 米国 | 米国 | | MailChimp | 顧客チケットメールサービスプロバイダ | 米国 | 米国 | | Mailgun | トランザクションメールサービスプロバイダ | 米国 | 米国 | | Microsoft | Microsoft Services | 米国 | 米国 | diff --git a/translations/ja-JP/content/github/site-policy/index.md b/translations/ja-JP/content/github/site-policy/index.md index 68e8cac7f21f0..c8ede5e96341a 100644 --- a/translations/ja-JP/content/github/site-policy/index.md +++ b/translations/ja-JP/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index b76532a6036fd..d823dd8942e77 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ versions: ### 最近のスポンサーシップアクティビティを表示する {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. 左のサイドバーで**Activity（アクティビティ）**をクリックしてください。 ![アクティビティタブ](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### スポンサーシップデータをエクスポートする -If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. [**Export all**] をクリックします。 ![[Export all] ボタン](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![エクスポートボタン](/assets/images/help/sponsors/export-all.png) 1. エクスポートしたいデータの時間枠と形式を選択し、[**Start export**] をクリックします。 ![データエクスポートのオプション](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index 9ac3d3f7adc49..a8d7a00db74e0 100644 --- a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -21,7 +21,7 @@ When you enable data use for your private repository, you'll be able to access t {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/using-git/adding-a-remote.md b/translations/ja-JP/content/github/using-git/adding-a-remote.md index bc5728adbc6dd..cc005f9aed45d 100644 --- a/translations/ja-JP/content/github/using-git/adding-a-remote.md +++ b/translations/ja-JP/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ $ git remote -v このエラーは、ローカルのリポジトリにすでに存在している名前でリモートを追加しようとしたということです。 ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/ja-JP/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/ja-JP/content/github/using-git/using-git-rebase-on-the-command-line.md index 8360dd1a3ac7f..ad5e200636027 100644 --- a/translations/ja-JP/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/ja-JP/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,6 +124,10 @@ i cant' typ goods Git の履歴を変更したので、通常の `git push origin` **は動作しません**。 最新の変更を「強制プッシュ」して、コマンドを変更する必要があります: ```shell +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes $ git push origin main --force ``` diff --git a/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index ca453d7cfbab9..ce85d129682ce 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ Jekyll サイトのコンテンツとして 2 つの主なタイプは、ペー {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### 次のステップ {% data reusables.pages.add-jekyll-theme %}詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)」を参照してください。 diff --git a/translations/ja-JP/content/github/working-with-github-support/about-github-support.md b/translations/ja-JP/content/github/working-with-github-support/about-github-support.md index 1e403fae9a02e..4b6c76f706f26 100644 --- a/translations/ja-JP/content/github/working-with-github-support/about-github-support.md +++ b/translations/ja-JP/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ versions: ### {% data variables.contact.github_support %}への連絡 -{% data variables.product.prodname_free_user %}のユーザ及びOrganizationのアカウントは、トピックの閲覧、質問、ソリューションの共有、{% data variables.contact.community_support %}との直接のやりとりのために{% data variables.contact.community_support_forum %}を利用できます。 アカウント、セキュリティ、悪用の問題をレポートするために{% data variables.contact.contact_support %}に連絡することもできます。 +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -有料のアカウントでは{% data variables.contact.contact_support %}に連絡することも、そしてプランによっては{% data variables.contact.premium_support %}もしくは{% data variables.contact.contact_ent_support %}に連絡することもできます。 {% data variables.contact.premium_support %}への連絡に関する詳しい情報については「[{% data variables.product.prodname_ghe_cloud %}の{% data variables.contact.premium_support %}について](/articles/about-github-premium-support-for-github-enterprise-cloud)」もしくは「[{% data variables.product.prodname_ghe_server %}の{% data variables.contact.premium_support %}について](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)」を参照してください。 +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. ### プライベートリポジトリへの{% data variables.contact.github_support %}の一時的なアクセスの許可 diff --git a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index e72777e617b60..7a4bdd83c5bff 100644 --- a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -215,7 +215,7 @@ To see content attachments, you must have a {% data variables.product.prodname_g `:` を入力すると、絵文字のサジェストリストが表示されます。 このリストは、入力を進めるにつれて絞り込まれていくので、探している絵文字が見つかったら、**Tab** または **Enter** を押すと、ハイライトされているものが入力されます。 -利用可能な絵文字とコードの完全なリストについては、[emoji-cheat-sheet.com](http://emoji-cheat-sheet.com)を参照してください。 +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). ### パラグラフ diff --git a/translations/ja-JP/content/github/writing-on-github/creating-gists.md b/translations/ja-JP/content/github/writing-on-github/creating-gists.md index a9e881d292ce3..080eaf495ecaa 100644 --- a/translations/ja-JP/content/github/writing-on-github/creating-gists.md +++ b/translations/ja-JP/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- title: Gist の作成 -intro: '2 種類の Gist、つまりパブリックとシークレットを作成できます。 自分のアイデアを共有する準備ができていればパブリック Gist を、まだの場合はシークレット Gist を作成します。' +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,13 @@ versions: ### Gistについて -すべての Gist は Git のリポジトリであり、フォークしたりクローンしたりできます。 Gist を作成する際 {% data variables.product.product_name %} にサインインしている場合、その Gist は自分のアカウントに関連付けられ、{% data variables.gists.gist_homepage %} に移動すると自分の Gist リストに表示されます。 +すべての Gist は Git のリポジトリであり、フォークしたりクローンしたりできます。 {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -Gist はパブリックまたはプライベートにできます。 パブリックGistは{% data variables.gists.discover_url %}に表示されます。ここでは作成されたばかりの新しいGistをブラウズできます。 それらのGistは検索もできるので、他の人々に自分の作業を探して見てもらうために使うこともできます。 {% data reusables.gist.cannot-convert-public-gists-to-secret %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. それらのGistは検索もできるので、他の人々に自分の作業を探して見てもらうために使うこともできます。 -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 %}シークレット Gist は、プライベートではありません。 シークレット Gist の URL を友人に送信すれば、見てもらえるようになります。 ただし、知人ではない誰かがその URL を見つけたなら、その人もその Gist を見ることができます。 好奇心の強い眼から自分のコードを守っておきたいなら、[プライベートリポジトリを作成](/articles/creating-a-new-repository)するとよいでしょう。 +Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. 好奇心の強い眼から自分のコードを守っておきたいなら、[プライベートリポジトリを作成](/articles/creating-a-new-repository)するとよいでしょう。 + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -39,7 +41,7 @@ You can pin gists to your profile so other people can see them easily. 詳しい {% endif %} -他の人が作成した Gist は、{% data variables.gists.gist_homepage %} にアクセスして [**All Gists**] をクリックすることで見つけることができます。 こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/articles/searching-code)と同じ検索構文を使います。 +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/articles/searching-code)と同じ検索構文を使います。 Gist は Git リポジトリであるため、完全なコミット履歴を diff とともに表示させることができます。 Gist はフォークしたりクローンしたりすることもできます。 詳細は「[Gist のフォークおよびクローン](/articles/forking-and-cloning-gists)」を参照してください。 @@ -69,12 +71,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 4. Gist のテキストを Gist テキストボックスに入力します。 ![Gist テキストボックス](/assets/images/help/gist/gist_text_box.png) -5. 以下のいずれかを行います: - - パブリック Gist を作成するには [**Create public gist**] をクリックします。 - - シークレット Gist を作成するには [**Create secret Gist**] をクリックします。 ![Gist 作成ボタン](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **メモ:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md index 935c8dea16f55..a421543d8796f 100644 --- a/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Gist をフォークする -各 Gist はどのフォークにアクティビティがあるのかを示すため、同僚や知らないユーザによる興味深い変更を簡単に確認できます。 +Each gist indicates which forks have activity, making it easy to find interesting changes from others. ![Gist フォーク](/assets/images/help/gist/gist_forks.png) diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md index 623c032f8c78e..f6d70a3ab3736 100644 --- a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ GraphQLのクエリは、指定したデータのみを返します。 クエリ 
      mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
      この例の入力オブジェクトは`MuitationNameInput`であり、ペイロードオブジェクトは `MuitationNamePayload` です。 diff --git a/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md index 4068888e0730d..95ff9e7a2791a 100644 --- a/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: `docker` loginコマンドを使い、Dockerで{% data variables.product.prodname_registry %}の認証を受けることができます。 -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} Docker レジストリを {% data variables.product.prodname_registry %} で使用する前に、{% data variables.product.product_location %} のサイト管理者がインスタンスに対し Docker のサポートとand Subdomain Isolation を有効化する必要があります。 詳しい情報については、「[Enterprise 向けの GitHub Packages を管理する](/enterprise/admin/packages)」を参照してください。 @@ -30,8 +30,6 @@ Docker レジストリを {% data variables.product.prodname_registry %} で使 ### {% data variables.product.prodname_registry %} への認証を行う -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### 個人アクセストークンでの認証 @@ -51,6 +49,10 @@ Docker レジストリを {% data variables.product.prodname_registry %} で使 {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} {% raw %} ```shell $ docker images @@ -65,6 +67,16 @@ $ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. @@ -103,9 +115,19 @@ To use this example login command, replace `USERNAME` with your {% data variable $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + {% endif %} ```shell $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. パッケージ用のDockerイメージをまだ構築していないなら、イメージを構築してください。 *OWNER*をリポジトリを所有しているユーザあるいはOrganizationのアカウント名で、*REPOSITORY*をプロジェクトを含むリポジトリ名で、*IMAGE_NAME*をパッケージもしくはイメージの名前で、*VERSION*をビルド時点のパッケージバージョンで置き換え、イメージが現在のワーキングディレクトリにないなら*PATH*をイメージへのパスで置き換えてください。 {% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. @@ -114,9 +136,19 @@ To use this example login command, replace `USERNAME` with your {% data variable $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. イメージを {% data variables.product.prodname_registry %}. @@ -125,9 +157,19 @@ To use this example login command, replace `USERNAME` with your {% data variable $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -137,7 +179,14 @@ To use this example login command, replace `USERNAME` with your {% data variable #### Dockerイメージのプッシュの例 -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} `monalisa`イメージのバージョン1.0を、イメージIDを使って`octocat/octo-app`に公開できます。 @@ -207,9 +256,19 @@ You can use the `docker pull` command to install a docker image from {% data var $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index fabc683365bc9..7ea129424197a 100644 --- a/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -79,10 +79,35 @@ versions: ### パッケージを公開する -*nuget.config*で認証を受けることによって、パッケージを{% data variables.product.prodname_registry %}に公開できます。 公開の際には、*nuget.config*認証ファイルで使用する*csproj*ファイル中で、`OWNER`に同じ値を使わなければなりません。 *.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. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. 新しいプロジェクトを作成してください。 + ```shell + dotnet new console --name OctocatApp + ``` +2. プロジェクトをパッケージ化してください。 + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +公開の際には、*nuget.config*認証ファイルで使用する*csproj*ファイル中で、`OWNER`に同じ値を使わなければなりません。 *.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. + {% data reusables.package_registry.authenticate-step %} 2. 新しいプロジェクトを作成してください。 ```shell @@ -119,6 +144,8 @@ versions: dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### 同じリポジトリへの複数パッケージの公開 複数のパッケージを同じリポジトリに公開するには、同じ{% data variables.product.prodname_dotcom %}リポジトリURLをすべての*.csproj*プロジェクトファイル中の`RepositoryURL`フィールドに含めることができます。 {% data variables.product.prodname_dotcom %}は、そのフィールドに基づいてリポジトリをマッチします。 diff --git a/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md index 65182579867be..ecdaed600e60a 100644 --- a/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -209,6 +209,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### 参考リンク - [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md index 207f85ba18006..21f02d6c6be07 100644 --- a/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. Dockerfile に以下の行を追加します。`OWNER` と `REPO` は、あなたの情報に置き換えてください。 ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` たとえば、あなたのユーザ名が `monalisa` で、`my-repo` を所有している場合は、以下の行を Dockerfile に追加します。 ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` 詳しい情報については、公式の Docker ドキュメンテーションの「[LABEL](https://docs.docker.com/engine/reference/builder/#label)」、および `opencontainers/image-spec` リポジトリの「[事前定義されたアノテーションキー](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)」を参照してください。 diff --git a/translations/ja-JP/content/packages/guides/using-github-packages-with-github-actions.md b/translations/ja-JP/content/packages/guides/using-github-packages-with-github-actions.md index bb4ed48ec696c..8f9a3f5c6d7a9 100644 --- a/translations/ja-JP/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/ja-JP/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,274 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{ ### Publishing a package using an action -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
      + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
      + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
      + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
      + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
      + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
      + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
      + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
      + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
      + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
      + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
      + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
      + +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Installing a package using an action You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. diff --git a/translations/ja-JP/content/packages/learn-github-packages/about-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/about-github-packages.md index 94a4586b2061f..9c7d984ebc7f7 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/ja-JP/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ versions: 1つのリポジトリで複数のパッケージをホストし、各パッケージのREADMEを見たり、統計をダウンロードしたり、バージョン履歴を見たりすることで、各パッケージに関する詳しい情報を見ることができます。 + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/guides/about-github-container-registry)」を参照してください。 {% 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) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ For more information about Docker and ### パッケージの管理 -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、「[パッケージの削除](/packages/manage-packages/deleting-a-package)」と「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、「[パッケージの削除](/packages/manage-packages/deleting-a-package)」と「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 webhookを設定して、パッケージの公開や更新といったパッケージ関連のイベントにサブスクライブできます。 詳しい情報については、「[`package` webhookイベント](/webhooks/event-payloads/#package)」を参照してください。 diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md index e97891ce2e473..d08ce35065650 100644 --- a/translations/ja-JP/content/rest/overview/api-previews.md +++ b/translations/ja-JP/content/rest/overview/api-previews.md @@ -70,14 +70,6 @@ API を介して[インテグレーション](/v3/integrations)を管理しま **カスタムメディアタイプ:** `cloak-preview` **発表日:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} -### ユーザブロック - -ユーザは[他のユーザをブロック](/rest/reference/users#blocking)できます。 Organization も[ユーザをブロック](/rest/reference/orgs#blocking)できます。 - -**カスタムメディアタイプ:** `giant-sentry-fist-preview` **発表日:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **更新日1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **更新日 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - ### リポジトリトピック リポジトリの結果を返す[呼び出し](/rest/reference/repos)で[リポジトリトピック](/articles/about-topics/)のリストを表示します。 diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md index f32deffc52752..8b83e771d3a0c 100644 --- a/translations/ja-JP/content/rest/overview/libraries.md +++ b/translations/ja-JP/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ versions: ### Python -ライブラリ名 | リポジトリ |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 ac1d206892b15..ef8ff48e1fccd 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 @@ -30,7 +30,7 @@ GitHub の GraphQL API についての情報は、[v4 ドキュメント](/graph JSON として送受信されます。 ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -124,7 +124,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/ 無効な認証情報で認証すると、`401 Unauthorized` が返されます。 ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -323,7 +323,7 @@ Basic 認証または OAuth を使用する API リクエストの場合、1 時 API リクエストの返された HTTP ヘッダは、現在のレート制限ステータスを示しています。 ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -421,7 +421,7 @@ User-Agent: Awesome-Octocat-App cURL はデフォルトで有効な `User-Agent` ヘッダを送信します。 cURL（または代替クライアント）を介して無効な `User-Agent` ヘッダを提供すると、`403 Forbidden` レスポンスが返されます。 ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -448,7 +448,7 @@ $ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -459,7 +459,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -470,7 +470,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -488,7 +488,7 @@ API は、任意のオリジンからの AJAX リクエストに対して、オ `http://example.com` にアクセスするブラウザから送信されたサンプルリクエストは次のとおりです。 ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval @@ -497,7 +497,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra CORS プリフライトリクエストは次のようになります。 ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With diff --git a/translations/ja-JP/content/rest/reference/code-scanning.md b/translations/ja-JP/content/rest/reference/code-scanning.md index 5594e46c99536..eac0073d13fac 100644 --- a/translations/ja-JP/content/rest/reference/code-scanning.md +++ b/translations/ja-JP/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Code scanning redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/ja-JP/content/rest/reference/pulls.md b/translations/ja-JP/content/rest/reference/pulls.md index 8c7eb39b33f87..5af4edccf13ae 100644 --- a/translations/ja-JP/content/rest/reference/pulls.md +++ b/translations/ja-JP/content/rest/reference/pulls.md @@ -42,7 +42,7 @@ diff が破損している場合は、{% data variables.contact.contact_support | `review_comments` | プルリクエストの [レビューコメント](/rest/reference/pulls#comments) の API ロケーション。 | | `review_comment` | プルリクエストのリポジトリで、[レビューコメント](/rest/reference/pulls#comments)の API ロケーションを構築するための[URL テンプレート](/rest#hypermedia)。 | | `commits` | プルリクエストの [コミット](#list-commits-on-a-pull-request) の API ロケーション。 | -| `ステータス` | プルリクエストの[コミットステータス](/rest/reference/repos#statuses)、すなわち`head` ブランチのステータスの API ロケーション。 | +| `statuses` | プルリクエストの[コミットステータス](/rest/reference/repos#statuses)、すなわち`head` ブランチのステータスの API ロケーション。 | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index d17ae73ea1a0c..ecd4409c02fb6 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -123,7 +123,7 @@ - term: コミット description: >- - コミット、または「リビジョン」とは、ファイル（またはファイルのセット）に対する個々の変更です。コミットをして変更を保存すると、Git では一意の ID（別名「SHA」または「ハッシュ」）が作成され、コミットした特定の変更に加え、誰がいつ変更したかの記録を保持できます。コミットには通常、何の変更が加えられたかを手短に記載したコミットメッセージ が含まれます。 + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. - term: コミット作者 description: コミットをするユーザ。 @@ -137,7 +137,7 @@ - term: コミットメッセージ description: >- - コミットに付随し、コミットで導入されてくる変更について伝達する、手短な説明のテキスト。 + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. - term: 比較ブランチ description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - Gist とは共有可能なファイルであり、GitHub 上で編集、クローン作成、フォークできます。Gist はパブリックにすることもシークレットにすることもできますが、シークレット Gist は URL のある個人なら誰でも使用できます。 + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- @@ -436,7 +436,7 @@ - term: 通知 description: >- - 興味のあるアクティビティについての情報を提供するアップデート。設定によってウェブかメールのいずれかで配布されます。 + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. - term: OAuth App description: >- diff --git a/translations/ja-JP/data/glossaries/internal.yml b/translations/ja-JP/data/glossaries/internal.yml index 9f5d0a9fa8141..65aa2ed692c99 100644 --- a/translations/ja-JP/data/glossaries/internal.yml +++ b/translations/ja-JP/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: 中央処理装置。 - term: 認証情報ヘルパー - description: Git 資格情報を格納して fet するプログラム。 + description: A program that stores and fetches Git credentials. - term: creole description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - What You See Is What You Get。画面上のテキストは、レンダリングされた際に全く同様に表示される、という意味の頭字語。 + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. - term: XenServer description: 仮想化プラットフォーム。 diff --git a/translations/ja-JP/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..9354a47f0224a --- /dev/null +++ b/translations/ja-JP/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: パッケージのバージョン削除へのアクセス + description: >- + このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。 + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: デプロイメント + description: >- + このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。 + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - プルリクエストのマージ状態に関する詳細な情報。 + description: >- + このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。 + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。 + description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。 + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: プロジェクトイベントの詳細 + description: >- + このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。 + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: コンテンツ添付ファイルの作成 + description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。 + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: ピン止めされたIssueのプレビュー + description: このプレビューは、ピン止めされたIssueのサポートを追加します。 + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: ラベルのプレビュー + description: >- + このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。 + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: プロジェクトのインポート + description: このプレビューは、プロジェクトのインポートのサポートを追加します。 + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Teamレビューの割り当てプレビュー + description: >- + このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/ja-JP/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..f90a51675b932 --- /dev/null +++ b/translations/ja-JP/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' + date: '2019-04-01T00:00:00+00:00' + criticality: 破壊的 + owner: tambling + - + location: AssignedEvent.user + 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`に置き換えられます。' + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BlakeWilliams + - + location: UnassignedEvent.user + 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`は削除されます。' + date: '2020-04-01T00:00:00+00:00' + criticality: 破壊的 + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + 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`フィールドを使用してください。' + reason: リポジトリの招待は、招待者だけではなくメールにも関連づけられるようになりました。 + date: '2020-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: jdennes + - + location: Issue.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`は削除されます。' + date: '2020-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: mikesea + - + location: RepositoryInvitationOrderField.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`は削除されます。' + date: '2020-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + 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.' + 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.' + 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.' + reason: DRAFT state will be removed from this enum and `isDraft` should be used instead + date: '2021-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: nplasterer diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..6aed744879310 --- /dev/null +++ b/translations/ja-JP/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Get started with {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'セルフホストランナーを作成し、非常にカスタマイズ性の高い環境でワークフローを実行できます。' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/ja-JP/data/release-notes/2-22/0.yml b/translations/ja-JP/data/release-notes/2-22/0.yml index 49d4808c59268..544ebbea8063f 100644 --- a/translations/ja-JP/data/release-notes/2-22/0.yml +++ b/translations/ja-JP/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/3-0/0-rc.yml b/translations/ja-JP/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..a331b395d0f52 --- /dev/null +++ b/translations/ja-JP/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API の変更 + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ja-JP/data/reusables/actions/enterprise-actions-permissions.md b/translations/ja-JP/data/reusables/actions/enterprise-actions-permissions.md index 5262dd004303d..9ee67981cd0c8 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. [Policies] で、オプションを選択します。 ![この Enterprise アカウントについてアクションを無効化、無効化、または制限](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![この Enterprise アカウントについてアクションを無効化、無効化、または制限](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/ja-JP/data/reusables/actions/enterprise-beta.md b/translations/ja-JP/data/reusables/actions/enterprise-beta.md index 7a869095a132f..0a8ab6cecd5da 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-beta.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**注釈:** {% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 To review the external storage requirements and request access to the beta, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +**注釈:** {% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md b/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..28640248bb4b3 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **注釈:** {% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/ja-JP/data/reusables/actions/enterprise-enable-checkbox.md b/translations/ja-JP/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md b/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..e2f4ed9452634 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." diff --git a/translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..ff266a314542b --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### 次のステップ + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/ja-JP/data/reusables/actions/enterprise-s3-permission.md b/translations/ja-JP/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/ja-JP/data/reusables/actions/enterprise-s3-support-warning.md b/translations/ja-JP/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/enterprise-self-signed-cert.md b/translations/ja-JP/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/ja-JP/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/ja-JP/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/ja-JP/data/reusables/actions/forked-secrets.md b/translations/ja-JP/data/reusables/actions/forked-secrets.md index 93fb22dadbe90..c51a35d2d3a36 100644 --- a/translations/ja-JP/data/reusables/actions/forked-secrets.md +++ b/translations/ja-JP/data/reusables/actions/forked-secrets.md @@ -1 +1 @@ -`GITHUB_TOKEN`を除き、フォークしたリポジトリからワークフローがトリガーされた場合、シークレットは runner に渡されません。 +`GITHUB_TOKEN`を除き、フォークしたリポジトリからワークフローがトリガーされた場合、シークレットはランナーに渡されません。 diff --git a/translations/ja-JP/data/reusables/actions/workflow-template-overview.md b/translations/ja-JP/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..9135d6574804c --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. たとえばリポジトリにNode.jsのコードが含まれているなら、Node.jsプロジェクトのためのサジェッションが提示されます。 ワークフローテンプレートは、カスタムワークフローの構築の出発点として利用することも、そのまま利用することもできます。 + +{% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) リポジトリ{% else %} {% data variables.product.product_location %} の `actions/starter-workflows` リポジトリで、ワークフローテンプレートの完全なリストを閲覧できます{% endif %}。 diff --git a/translations/ja-JP/data/reusables/advanced-security/more-info-ghas.md b/translations/ja-JP/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..73305fbe14a4d --- /dev/null +++ b/translations/ja-JP/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。 +{% endif %} diff --git a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/beta.md b/translations/ja-JP/data/reusables/code-scanning/beta.md index 0494a25f451d6..7d1b5dbc94798 100644 --- a/translations/ja-JP/data/reusables/code-scanning/beta.md +++ b/translations/ja-JP/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**ノート:** {% data variables.product.prodname_code_scanning_capc %}は現在ベータで、変更されることがあります。 For more information about taking part in the beta, [sign up here](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/ja-JP/data/reusables/code-scanning/not-available.md b/translations/ja-JP/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..6531f5e1d0875 --- /dev/null +++ b/translations/ja-JP/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." + +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md b/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md index b8d2b78cbceae..18554c0ce1388 100644 --- a/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. 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#allowing-dependabot-to-access-private-repositories)." +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. 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#allowing-dependabot-to-access-private-repositories)." -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/ja-JP/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index fb760e600afd1..e1f6df0639a42 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**ノート:** Enterproseアカウントのユーザプロビジョニングは現在プライベートベータであり、変更されることがあります。 ベータへのアクセスをリクエストするには、[営業チームにお問い合わせ](https://enterprise.github.com/contact)ください。 +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. ベータへのアクセスをリクエストするには、[営業チームにお問い合わせ](https://enterprise.github.com/contact)ください。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 756b5c40e8d0e..d3dc0111205b6 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Minimum requirements](#minimum-requirements) -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [ストレージ](#storage) - [CPU and memory](#cpu-and-memory) @@ -7,10 +8,10 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。 -- You must configure external blob storage. 詳しい情報については、「[{% data variables.product.prodname_actions %} の有効化とストレージの設定](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)」をご覧ください。 +- You must configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Maximum jobs per minute | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ We recommend a high-performance SSD with high input/output operations per second Your instance requires a persistent data disk separate from the root disk. 詳しい情報については「[システムの概要](/enterprise/admin/guides/installation/system-overview)」を参照してください。 -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable the beta of {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 2.22, you'll need to configure external blob storage. 詳しい情報については、「[{% data variables.product.prodname_actions %} の有効化とストレージの設定](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)」をご覧ください。 +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endif %} @@ -48,4 +49,4 @@ You can resize your instance's root disk by building a new instance or using an {% endwarning %} -You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md index df1cd374c411f..c621d139a7012 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| ユーザライセンス | vCPUs | メモリ | アタッチされたストレージ | ルートストレージ | +|:---------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| --------:| +| トライアル、デモ、あるいは10人の軽量ユーザ | 2
      or [**4**](#optional-features) | 16 GB
      or [**32 GB**](#optional-features) | 100 GB
      or [**150 GB**](#optional-features) | 200 GB | +| 10-3000 | 4
      or [**8**](#optional-features) | 32 GB
      or [**48 GB**](#optional-features) | 250 GB
      or [**300 GB**](#optional-features) | 200 GB | +| 3000-5000 | 8
      or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12
      or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16
      or [**20**](#optional-features) | 128 GB
      or [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | ユーザライセンス | vCPUs | メモリ | アタッチされたストレージ | ルートストレージ | |:---------------------- | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| --------:| | トライアル、デモ、あるいは10人の軽量ユーザ | 2{% if currentVersion == "enterprise-server@2.22" %}
      or [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
      or [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
      or [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
      or [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
      or [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
      or [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/actions.md b/translations/ja-JP/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..5fecd812f5323 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. サイドバーで**Actions（アクション）**をクリックしてください。 ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/ja-JP/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..47296b1ec8754 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_advanced_security %} ライセンスを使用すると、リポジトリとコードのセキュリティを強化するのに役立つ機能にアクセスできます。 {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..4b1379243ea91 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +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. You should time this change carefully, to minimize downtime. + +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..02ab911684782 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. [**Save changes**] をクリックします。 ![[Edit message] ボタン](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gated-features/code-scanning.md b/translations/ja-JP/data/reusables/gated-features/code-scanning.md index 2bcd80c1d4af9..69e6abf27f4f7 100644 --- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/gated-features/environments.md b/translations/ja-JP/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/ja-JP/data/reusables/gated-features/environments.md +++ b/translations/ja-JP/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/protected-branches.md b/translations/ja-JP/data/reusables/gated-features/protected-branches.md index a9745fcec2b68..ffae769bab961 100644 --- a/translations/ja-JP/data/reusables/gated-features/protected-branches.md +++ b/translations/ja-JP/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 %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/secret-scanning.md b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md index bd279034eee82..7396ad8e24141 100644 --- a/translations/ja-JP/data/reusables/gated-features/secret-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/ja-JP/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 09e1a366f4c1e..535fa5cd9df20 100644 --- a/translations/ja-JP/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/ja-JP/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -パブリックとして作成したGistを後からシークレットにすることはできません。 +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..3a31b6f490c23 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/ja-JP/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..cff796ad75085 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. 詳しい情報については、「[デフォルトの環境変数](/actions/reference/environment-variables#default-environment-variables)」を参照してください。 +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. 詳細については、「[コンテキスト](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)」を参照してください。 + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/ja-JP/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/ja-JP/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index 6461d81ef457d..69749f39b0335 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -Azure ADでTeam同期を有効化するには、Azure ADの環境に以下の権限が必要です。 +To enable team synchronization for Azure AD, your Azure AD installation needs the following permissions. - すべてのユーザに対するフルプロフィールの読み取り - サインインおよびユーザプロフィールの読み取り - ディレクトリデータの読み取り diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm.md index 655660dc27925..1464bd4f943c0 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. Team の同期を確認するには、以下を実行します: +5. Confirm team synchronization. - IdP にアクセスできる場合は、[**Enable team synchronization**] をクリックします。 アイデンティティプロバイダの SAML SSO ページにリダイレクトされ、アカウントを選択して、要求された権限を確認するよう求められます。 - IdP にアクセスできない場合は、IdP のリダイレクトリンクをコピーして IdP の管理者に渡し、Team 同期の有効化を続けてください。 ![[Enable team synchronization redirect] ボタン](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/ja-JP/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/ja-JP/data/reusables/large_files/can-include-lfs-objects-archives.md index ed5b215d8bca1..2fb45cee4b4a0 100644 --- a/translations/ja-JP/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/ja-JP/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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} You can choose whether {% 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)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/mobile/about-mobile.md b/translations/ja-JP/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/ja-JP/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/ja-JP/data/reusables/mobile/ghes-release-phase.md b/translations/ja-JP/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/ja-JP/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/mobile/push-notifications-on-ghes.md b/translations/ja-JP/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/ja-JP/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/organizations/can-require-ssh-cert.md b/translations/ja-JP/data/reusables/organizations/can-require-ssh-cert.md index 6da37763232e5..1ed5f3afb99ac 100644 --- a/translations/ja-JP/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/ja-JP/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -You can require that members use SSH certificates to access organization resources,, unless SSH is disabled in your repository. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/ja-JP/data/reusables/organizations/click-codespaces.md b/translations/ja-JP/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/ja-JP/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ja-JP/data/reusables/organizations/team-synchronization.md b/translations/ja-JP/data/reusables/organizations/team-synchronization.md index 636b3041f72a3..fa100b3912850 100644 --- a/translations/ja-JP/data/reusables/organizations/team-synchronization.md +++ b/translations/ja-JP/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -Teamの同期を使い、アイデンティティプロバイダを通じてOrganizationのメンバーの追加や削除を自動的に行えます。 詳しい情報については「[Team をアイデンティティプロバイダグループと同期する](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. 詳しい情報については「[Team をアイデンティティプロバイダグループと同期する](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/ja-JP/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ja-JP/data/reusables/package_registry/packages-cluster-support.md b/translations/ja-JP/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/ja-JP/data/reusables/package_registry/packages-ghes-release-stage.md index 03d9b25f84162..04e4ffd9ea459 100644 --- a/translations/ja-JP/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/ja-JP/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your instance, use the [sign-up form](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/project-management/choose-visibility.md b/translations/ja-JP/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..a17daff3d93b7 --- /dev/null +++ b/translations/ja-JP/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. 詳しい情報については「[プロジェクトボードの表示設定を変更する](/github/managing-your-work-on-github/changing-project-board-visibility)」を参照してください。 ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/ja-JP/data/reusables/project-management/project-board-visibility.md b/translations/ja-JP/data/reusables/project-management/project-board-visibility.md index 39ab9f19b7f6b..acf775d7ca01c 100644 --- a/translations/ja-JP/data/reusables/project-management/project-board-visibility.md +++ b/translations/ja-JP/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -デフォルトでは、プロジェクトボードはプライベートに設定されており、プロジェクトボードへの読み取り、書き込み、または管理者権限を持つメンバーだけが表示できます。 パブリックなプロジェクトボードは、プロジェクトボードの URL で誰でも表示可能です。 +デフォルトでは、プロジェクトボードはプライベートに設定されており、プロジェクトボードへの読み取り、書き込み、または管理者権限を持つメンバーだけが表示できます。 {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/ja-JP/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/ja-JP/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index 2276ebd888b6a..a059d0b480e7f 100644 --- a/translations/ja-JP/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/ja-JP/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -リポジトリでステータスチェックが要求されているなら、必須のステータスチェックをパスしてからでないと保護されたブランチにあなたのブランチはマージできません。 詳しい情報については[必須のステータスチェックについて](/articles/about-status-checks)を参照してください。 +リポジトリでステータスチェックが要求されているなら、必須のステータスチェックをパスしてからでないと保護されたブランチにあなたのブランチはマージできません。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 diff --git a/translations/ja-JP/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/ja-JP/data/reusables/pull_requests/required-reviews-for-prs-summary.md index 705636a81e88c..3526e39a78da3 100644 --- a/translations/ja-JP/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/ja-JP/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -リポジトリ管理者は、保護されたブランチにマージされる前に、すべてのプルリクエストがリポジトリに*書き込み*あるいは*管理*権限を持つ人々から、あるいは指定されたコードオーナーから指定した数の承認レビューを受けなければならないようにすることができます。 詳しい情報については[保護されたブランチについて](/articles/about-protected-branches)を参照してください。 - -必須レビューが有効化されると、リポジトリへのアクセス権を持つ人は誰でもプルリクエスト中の変更を承認できます。 ただし、リポジトリに*書き込み*もしくは*管理*権限を持つ必要な数のレビュー担当者がプルリクエストの変更をレビューで承認するまでは、プルリクエストはマージできません。 リポジトリの権限レベルに関する詳しい情報については「[Organizationのリポジトリの権限レベル](/articles/repository-permission-levels-for-an-organization/)」を参照してください。 指定されたコードオーナーからのレビューが必須で、プルリクエストが指定されたオーナーのコードに影響するものなら、そのオーナーからの承認が必要です。 +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/ja-JP/data/reusables/repositories/branch-rules-example.md b/translations/ja-JP/data/reusables/repositories/branch-rules-example.md index 840c70b61dee9..ea81704455211 100644 --- a/translations/ja-JP/data/reusables/repositories/branch-rules-example.md +++ b/translations/ja-JP/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -リポジトリ中のブランチルールは、特定のブランチ、すべてのブランチ、fnmatch構文で指定された名前のパターンにマッチするブランチに対して作成できます。 たとえば`release`という語を含むブランチに対し、マージ前に最低でも2つのプルリクエストレビューを必須とするなら、`*release*`に対してブランチルールを作成できます。 +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md b/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..372512e850e04 --- /dev/null +++ b/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![ソース diff ボタン](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md index 594092108ff09..cfe413d8a0cef 100644 --- a/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -すべての必須レビュー担当者がプルリクエストを承認した後で、ペンディングあるいは拒否されたレビューを持つオープンのプルリクエストが他にあり、それらのプルリクエストが同じコミットを指しているheadブランチを持っているなら、プルリクエストはマージできません。 マージするには、*書き込み*もしくは*管理*権限を持つ誰かが他のプルリクエスト上のブロックしているレビューを承認もしくは却下しなければなりません。 +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 3e658a60582ff..ba73880189979 100644 --- a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. 詳しい情報については「[直線状のコミット履歴を必須とする](/github/administering-a-repository/requiring-a-linear-commit-history)」を参照してください。{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md index 7ef45300464dc..106d0e87ba7b2 100644 --- a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md +++ b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ {% data variables.product.prodname_actions %}に対するメールあるいはWeb通知を有効化すると、あなたが起動したワークフローランが完了すると通知されます。 この通知には、ワークフローランのステータス（成功、失敗、ニュートラル、キャンセルされたランが含まれます）が含まれます。 ワークフローランが失敗したときにだけ通知を受けるようにすることもできます。 +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + リポジトリのActionsタブでワークフローランのステータスを見ることもできます。 詳細については、「[ワークフロー実行の管理](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/ja-JP/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..2f096a39e3928 --- /dev/null +++ b/translations/ja-JP/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Enterprise のオーナーは、Enterprise アカウントが所有するすべての Organization 全体で、SAML IdP によって SAML SSO と中央での認証を有効にすることができます。 Enterprise アカウントで SAML SSO を有効にした後は、SAML SSO は Enterprise アカウントによって所有されているすべての Organization に対してデフォルトで有効となります。 すべてのメンバーは、自分がメンバーである Organization にアクセスするために SAML SSO を使用して認証するよう求められ、企業のオーナーは Enterprise アカウントにアクセスする際に SAML SSO を使用して認証するよう求められます。 diff --git a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md index 30b8d952de4e7..be784eeb4f31c 100644 --- a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML SSOは、{% data variables.product.prodname_dotcom %}上のOrganizationのオーナー及びEnterpriseのオーナーに対し、リポジトリ、Issue、プルリクエストのようなOrganizationのリソースに対するアクセスをコントロールし、セキュアに保つ方法を提供します。 +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md b/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md index c968a25d6f560..82fdadded9388 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/beta.md +++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**ノート:** プライベートリポジトリのための{% data variables.product.prodname_secret_scanning_caps %}は現在ベータで、変更されることがあります。 +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..eb0329e7fe346 --- /dev/null +++ b/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/ja-JP/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/ja-JP/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index ac7d6058f6ff7..1de7fb3bf54d3 100644 --- a/translations/ja-JP/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/ja-JP/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **ノート**: パブリックリポジトリにデフォルトで有効化されているセキュリティ及び分析の機能の中には、無効化できないものがあります。 {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/sponsors/activity-tab.md b/translations/ja-JP/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..88739ba99b160 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. 左のサイドバーで**Activity（アクティビティ）**をクリックしてください。 ![アクティビティタブ](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/support/ghae-priorities.md b/translations/ja-JP/data/reusables/support/ghae-priorities.md index 9069a8701ec4a..6c472bc308cd9 100644 --- a/translations/ja-JP/data/reusables/support/ghae-priorities.md +++ b/translations/ja-JP/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | 優先度 | 説明 | サンプル | |:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

      _After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
      • すべてのユーザーについて、中核的なGitあるいはWebアプリケーションの機能に影響するエラーもしくは中断
      • Severe network or performance degradation for majority of users
      • ストレージがフル、もしくは急速に埋まりつつある
      • Known security incidents or a breach of access
      | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
      • 多くのユーザの生産性を引き下げるパフォーマンスの低下
      • Reduced redundancy concerns from failures or service degradation
      • Production-impacting bugs or errors
      • {% data variables.product.product_name %} configuraton security concerns
      | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
      • 多くのユーザの生産性を引き下げるパフォーマンスの低下
      • Reduced redundancy concerns from failures or service degradation
      • Production-impacting bugs or errors
      • {% data variables.product.product_name %} configuration security concerns
      | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
      • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
      • Issues with user tools and data collection methods
      • アップグレード
      • Bug reports, general security questions, or other feature related questions
        • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
        • Feature requests and product feedback
        • General questions on overall configuration or use of {% data variables.product.product_name %}
        • Notifying {% data variables.contact.github_support %} of any planned changes
        | diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index f0aa25b75b5fb..0a1c0cbd38261 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -4,7 +4,7 @@ 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.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' localization_complete: ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。 localization_in_progress: こんにちは！このページは開発中か、まだ翻訳中です。最新の正しい情報を得るには、英語のドキュメンテーションにアクセスしてください。 early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,15 @@ product_landing: quick_start: クイックスタート reference_guides: Reference guides overview: 概要 +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: その他のガイド + guideTypes: + overview: 概要 + quick_start: クイックスタート + tutorial: チュートリアル + how_to: How-to guide + reference: リファレンス diff --git a/translations/ja-JP/data/variables/action_code_examples.yml b/translations/ja-JP/data/variables/action_code_examples.yml index b816b4df25f20..6d27178d24fea 100644 --- a/translations/ja-JP/data/variables/action_code_examples.yml +++ b/translations/ja-JP/data/variables/action_code_examples.yml @@ -63,7 +63,7 @@ - projects - automation - issues - - プルリクエスト + - pull requests - title: Run GitHub Actions Locally with a web interface description: Runs GitHub Actions workflows locally (local) @@ -179,7 +179,7 @@ href: dessant/lock-threads tags: - issues - - プルリクエスト + - pull requests - ワークフロー - title: Get Commit Difference Count Between Two Branches @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/ja-JP/data/variables/gists.yml b/translations/ja-JP/data/variables/gists.yml index 9d1fea10acf46..12c745fd3ceb3 100644 --- a/translations/ja-JP/data/variables/gists.yml +++ b/translations/ja-JP/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index cddfec0f16d1b..00c61c887c921 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'GitHub Sponsors Matching Fund' #GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/ja-JP/data/variables/release_candidate.yml +++ b/translations/ja-JP/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/ko-KR/content/actions/creating-actions/about-actions.md b/translations/ko-KR/content/actions/creating-actions/about-actions.md index 9640844ccbb6f..b1122cbf0236d 100644 --- a/translations/ko-KR/content/actions/creating-actions/about-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/about-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md index eb43f3a49bd0a..d113dcfbf29df 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md index 9b1416053e01b..f64f0dcaeb4a7 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md index 76711c4bbab12..73c7dbd4522cc 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 02a494062d847..a38c66beb85c4 100644 --- a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '참조' --- {% data reusables.actions.enterprise-beta %} @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction: ##### Example *Dockerfile* -``` +``` # Container image that runs your code FROM debian:9.5-slim # Copies your code file from your action repository to the filesystem path `/` of the container COPY entrypoint.sh /entrypoint.sh -# Executes `entrypoint.sh` when the Docker container starts up +# Executes `entrypoint.sh` when the Docker container starts up ENTRYPOINT ["/entrypoint.sh"] ``` @@ -78,14 +79,14 @@ Using the example Dockerfile above, {% data variables.product.product_name %} wi ``` sh #!/bin/sh -# `$*` expands the `args` supplied in an `array` individually +# `$*` expands the `args` supplied in an `array` individually # or splits `args` in a string separated by whitespace. sh -c "echo $*" ``` Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command: ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this: diff --git a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 926657401a5dd..51c2a464be8c6 100644 --- a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '참조' --- {% data reusables.actions.enterprise-beta %} @@ -104,12 +105,12 @@ outputs: {% raw %} ```yaml outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - id: random-number-generator run: echo "::set-output name=random-id::$(echo $RANDOM)" shell: bash @@ -213,7 +214,7 @@ For example, this `cleanup.js` will only run on Linux-based runners: ```yaml runs: using: "composite" - steps: + steps: - run: ${{ github.action_path }}/test/script.sh shell: bash ``` @@ -224,7 +225,7 @@ Alternatively, you can use `$GITHUB_ACTION_PATH`: ```yaml runs: using: "composite" - steps: + steps: - run: $GITHUB_ACTION_PATH/script.sh shell: bash ``` @@ -258,7 +259,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### Example using a Dockerfile in your repository ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -266,7 +267,7 @@ runs: #### Example using public Docker registry container ```yaml -runs: +runs: using: 'docker' image: 'docker://debian:stretch-slim' ``` diff --git a/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 2a2f153359510..f22f2a2a381d6 100644 --- a/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. diff --git a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md index d329dc9af4b3e..1edcdcee6ea3f 100644 --- a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/about-continuous-integration.md b/translations/ko-KR/content/actions/guides/about-continuous-integration.md index baf265429346c..ffb01fc4b589b 100644 --- a/translations/ko-KR/content/actions/guides/about-continuous-integration.md +++ b/translations/ko-KR/content/actions/guides/about-continuous-integration.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md index 81c4419e79d25..b600ef4726ff3 100644 --- a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/about-service-containers.md b/translations/ko-KR/content/actions/guides/about-service-containers.md index ceeba28c1ca80..88705ae3914fc 100644 --- a/translations/ko-KR/content/actions/guides/about-service-containers.md +++ b/translations/ko-KR/content/actions/guides/about-service-containers.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md index ef34837e3a22f..798cfedb9708c 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md index 00a4c6143fa9e..8102ae80bd1f3 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md index f56207004e0c3..98b36f6b2832b 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-net.md b/translations/ko-KR/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..117006bbec812 --- /dev/null +++ b/translations/ko-KR/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Building and testing .NET +intro: You can create a continuous integration (CI) workflow to build and test your .NET project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introduction + +This guide shows you how to build, test, and publish a .NET package. + +{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners). + +### 빌드전 요구 사양 + +You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." + +We recommend that you have a basic understanding of the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn). + +### Starting with the .NET workflow template + +{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet). + +To get started quickly, add the template to the `.github/workflows` directory of your repository. + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Specifying a .NET version + +To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. + +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Using multiple .NET versions + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Using a specific .NET version + +You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### Installing dependencies + +{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Caching dependencies + +You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package. + +For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project. + +{% endnote %} + +{% endif %} + +### Building and testing your code + +You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### Packaging workflow data as artifacts + +After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results. + +For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### Publishing to package registries + +You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md index 95de8c5f8fa3a..664dd8083a888 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +37,11 @@ To get started quickly, add the template to the `.github/workflows` directory of ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ The easiest way to specify a Node.js version is by using the `setup-node` action The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`. -The template includes a matrix strategy that builds and tests your code with three Node.js versions: 8.x, 10.x, and 12.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps. +The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps. Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." @@ -77,7 +80,7 @@ Each job can access the value defined in the matrix `node-version` array using t ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} 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 01d01bcd7851d..40c2f949b7de3 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 @@ -7,6 +7,7 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-python.md b/translations/ko-KR/content/actions/guides/building-and-testing-python.md index ec0b8c3bab1de..1fb1cf75d2d07 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-python.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-python.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} @@ -122,7 +123,7 @@ jobs: #### Using a specific Python version -You can configure a specific version of python. For example, 3.8. Alternatively, you can semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. +You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. {% raw %} ```yaml diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md index 1a7698f789de2..acee994c00433 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 497bcad57e586..bd1391b8651aa 100644 --- a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: '튜토리얼' --- ### About caching workflow dependencies diff --git a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md index bde966be19ff3..765cb8d47eefe 100644 --- a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md b/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md index ba3278085fd90..f34c0739e2ede 100644 --- a/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/index.md b/translations/ko-KR/content/actions/guides/index.md index 642a9e37fd3e5..c4c3c5a9c0e9d 100644 --- a/translations/ko-KR/content/actions/guides/index.md +++ b/translations/ko-KR/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Creating custom continuous integration workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous integration (CI) workflows that build and test projects written in different programming languages. - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### Creating custom continuous deployment workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous deployment (CD) workflows that deploy projects to a number of cloud partner ecosystems. - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### Publishing software packages - -You can automate publishing software packages as part your continuous delivery (CD) workflow. Packages can be published to any package host and to {% data reusables.gated-features.packages %}. - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### Caching and storing workflow data - -Cache dependencies and store artifacts to make your workflow runs more efficient. - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### Using service containers in a workflow - -Connect services to your workflow using service containers. - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/ko-KR/content/actions/guides/publishing-docker-images.md b/translations/ko-KR/content/actions/guides/publishing-docker-images.md index 471181a1f11ca..2f4287c24c19b 100644 --- a/translations/ko-KR/content/actions/guides/publishing-docker-images.md +++ b/translations/ko-KR/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md index 379a48545658c..21c7ba7e06c3d 100644 --- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md index 5e415b926f1b1..7e10e0b45cbbe 100644 --- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} 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 63e608ec3d7d3..9e306dd15a130 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} @@ -87,9 +88,28 @@ always-auth=true Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass. -By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope) in the npm documentation. +#### Configuring the destination repository -To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. + +However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Authenticating to the destination repository + +To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." + +If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +#### Example workflow This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. 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 deaf7f498a01f..294e7b41d8448 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md index 3d929426f3b34..f375980a66a32 100644 --- a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 28591c40bfb9e..8110e5d167922 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 43374dea979a4..ee059f6532ae9 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,11 +7,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +You can add a self-hosted runner to a repository, an organization, or an enterprise. + +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. + For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% warning %} @@ -44,6 +49,8 @@ You can add self-hosted runners at the organization level, where they can be use {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### Adding a self-hosted runner to an enterprise You can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. @@ -62,3 +69,13 @@ To add a self-hosted runner at the enterprise level of 1. Click **Add new**, then click **New runner**. New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Making enterprise runners available to repositories + +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. + +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. + +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index b24159ce49673..822d1dd1ae4d9 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' defaultPlatform: linux --- diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index dc2b208d2a12b..0136a825f00b7 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index bdaeed7caae0a..572f9f9635581 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' defaultPlatform: linux --- diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 62c39ed3c61dd..174c5b70ad7fc 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 9bf1bd24226b5..a4ec90c92c04d 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 5d1500e7570f4..7274bcfeb8260 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,6 +4,7 @@ intro: You can use labels to organize your self-hosted runners based on their ch versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 4ba6809cef574..30ad9d91dc447 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md index f8ce1472ef39d..5f8870183127c 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,6 +5,7 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md index 5bd9b1da45276..e109e9fa30fcf 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -76,7 +77,7 @@ steps: #### Using branches -Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`: +Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`: ```yaml steps: 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 2740523926920..b3b4742c38793 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 @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md index 13deaaa494bd6..3faf2e2dc7ef4 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -5,6 +5,7 @@ intro: 'This guide shows you how to use the advanced features of {% data variabl versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -154,6 +155,15 @@ For more information, see ["Using labels with self-hosted runners](/actions/hos You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." {% endif %} +### Using a workflow template + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. If your repository already has existing workflows: In the upper-left corner, click **New workflow**. ![Create a new workflow](/assets/images/help/repository/actions-new-workflow.png) +1. Under the name of the template you'd like to use, click **Set up this workflow**. ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png) + ### 다음 단계 To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 2d794e5443a72..0350f4407f55e 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} @@ -324,4 +325,3 @@ jobs: You can find actions that you can use in your workflow in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Creating actions](/actions/creating-actions)." - diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 497f6175fc14c..b750afb5690c0 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 80d2f12511368..1275b42ee3f9a 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,6 +4,7 @@ intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share sev versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 6c7b2ae264efa..c20ffe4884a72 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- {% data reusables.actions.enterprise-beta %} @@ -166,7 +167,7 @@ Jenkins Pipeline maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Jenkins Pipeline needs: job1 job3: needs: [job1, job2] - + ``` diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 1f2dabdd03b79..071fac3971fee 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '튜토리얼' --- ### Introduction diff --git a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md index f6968cbd0fb11..5a403d6aa1c5e 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: '개요' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 0c9626cb20610..37138428dea4a 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -44,10 +45,10 @@ This procedure demonstrates how to create a workflow template and metadata file. runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`: ```yaml @@ -75,7 +76,7 @@ To add another workflow template, add your files to the same `workflow-templates ![Workflow template files](/assets/images/help/images/workflow-template-files.png) -### Using a workflow template +### Using a workflow template from your organization This procedure demonstrates how a member of your organization can find and use a workflow template to create a new workflow. An organization's workflow templates can be used by anyone who is a member of the organization. diff --git a/translations/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index 586344c270ddd..362146f7e6e32 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -66,9 +66,9 @@ Committing the workflow file in your repository triggers the `push` event and ru {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### 다음 단계 @@ -120,7 +120,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workfow you want to run. +1. In the left sidebar, click the workflow you want to run. ![Select say hello job](/assets/images/help/repository/say-hello-job.png) 1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow. ![Trigger the manual workflow](/assets/images/help/repository/manual-workflow-trigger.png) @@ -131,9 +131,9 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o 1. In the workflow logs, expand the 'Run echo "Hello World!"' section. ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Next steps diff --git a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 3740b490573d1..2d3f94f4795cd 100644 --- a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,6 +75,10 @@ In order to use property dereference syntax, the property name must: - start with `a-Z` or `_`. - be followed by `a-Z` `0-9` `-` or `_`. +#### Determining when to use contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### `github` context The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." @@ -107,15 +111,14 @@ The `github` context contains information about the workflow run and the event t The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)." -The `env` context syntax allows you to use the value of an environment variable in your workflow file. If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables. +The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." -You can only use the `env` context in the value of the `with` and `name` keys, or in a step's `if` conditional. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." +If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables. | Property name | 유형 | 설명 | | ---------------------- | ----- | ------------------------------------------------------------------------------------------------ | | `env` | `개체` | This context changes for each step in a job. You can access this context from any step in a job. | -| `env.` | `문자열` | The value of a specific environment variable. | - +| `env.` | `문자열` | The value of a specific environment variable. | #### `job` context diff --git a/translations/ko-KR/content/actions/reference/environment-variables.md b/translations/ko-KR/content/actions/reference/environment-variables.md index dfe3f897f0b87..06df24a88673e 100644 --- a/translations/ko-KR/content/actions/reference/environment-variables.md +++ b/translations/ko-KR/content/actions/reference/environment-variables.md @@ -57,6 +57,16 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. | +{% tip %} + +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determining when to use default environment variables or contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### Naming conventions for environment variables {% note %} 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 e0a6771dd96a4..71f4ecceb3721 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 @@ -80,6 +80,8 @@ You can use these operators in any of the five fields: You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html). +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." + ### Manual events You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event. @@ -593,7 +595,8 @@ By default, a workflow only runs when a `pull_request_target`'s activity type is For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`. ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` 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 ee818e09cf431..912148bcae470 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 @@ -83,44 +83,11 @@ If there is a tool that you'd like to request, please open an issue at [actions/ {% endnote %} -Windows and Ubuntu runners are hosted in Azure and have the same IP address ranges as Azure Data centers. Currently, all Windows and Ubuntu {% data variables.product.prodname_dotcom %}-hosted runners are in the following Azure regions: - -- East US (`eastus`) -- East US 2 (`eastus2`) -- West US 2 (`westus2`) -- Central US (`centralus`) -- South Central US (`southcentralus`) - -Microsoft updates the Azure IP address ranges weekly in a JSON file that you can download from the [Azure IP Ranges and Service Tags - Public Cloud](https://www.microsoft.com/en-us/download/details.aspx?id=56519) website. You can use this range of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. - -The JSON file contains an array called `values`. Inside that array, you can find the supported IP addresses in an object with a `name` and `id` of the Azure region, for example `"AzureCloud.eastus2"`. - -You can find the supported IP address ranges in the `"addressPrefixes"` object. This is a condensed example of the JSON file. - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. + +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. + +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### File systems 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 7a63ff729da62..4f92ed5fd64ec 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 @@ -187,7 +187,7 @@ For more information about cron syntax, see "[Events that trigger workflows](/ac ### `env` -A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} @@ -639,14 +639,15 @@ Using the `working-directory` keyword, you can specify the working directory of You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. -| Supported platform | `shell` parameter | 설명 | Command run internally | -| ------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | -| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | -| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | -| All | `python` | Executes the python command. | `python {0}` | -| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | +| Supported platform | `shell` parameter | 설명 | Command run internally | +| ------------------ | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | +| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | +| All | `python` | Executes the python command. | `python {0}` | +| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | #### Example running a script using bash @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### Example running a python script ```yaml @@ -1149,7 +1159,7 @@ You can use special characters in path, branch, and tag filters. - `**`: Matches zero or more of any character. - `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`. - `+`: Matches one or more of the preceding character. -- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. +- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. - `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. @@ -1167,35 +1177,35 @@ For more information about branch, tag, and path filter syntax, see "[`on.-`feature/your-branch` | -| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`
        -`feature/your-branch`
        -`feature/mona/the/octocat` | -| -`main`
        -`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`
        -`releases/mona-the-octocat` | -| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`
        -`releases` | -| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`
        -`every/tag` | -| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`
        -`feature`
        -`ver-10-feature` | -| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`
        -`v2.0`
        -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`
        -`v2.0.0` | +| Pattern | 설명 | Example matches | +| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | `feature/my-branch`

        `feature/your-branch` | +| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`

        `feature/your-branch`

        `feature/mona/the/octocat` | +| `main`

        `releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | `main`

        `releases/mona-the-octocat` | +| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`

        `releases` | +| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`

        `every/tag` | +| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`

        `feature`

        `ver-10-feature` | +| `v2*` | Matches branch and tag names that start with `v2`. | `v2`

        `v2.0`

        `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | `v1.10.1`

        `v2.0.0` | #### Patterns to match file paths Path patterns must match the whole path, and start from the repository's root. -| Pattern | Description of matches | Example matches | -| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | -| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`
        -`server.rb` | -| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`
        -`page.jsx` | -| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` | -| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`
        -`index.js` | -| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`
        -`js/index.js`
        -`src/js/app.js` | -| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`
        -`docs/file.txt` | -| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`
        -`docs/mona/octocat.txt` | -| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`
        -`docs/mona/hello-world.md`
        -`docs/a/markdown/file.md` | -| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`
        -`dir/docs/my-file.txt`
        -`space/docs/plan/space.doc` | -| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`
        -`js/README.md` | -| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`
        -`my-src/code/js/app.js` | -| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`
        -`path/their-post.md` | -| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`
        -`db/migrate-v1.0.sql`
        -`db/sept/migrate-v1.sql` | -| -`*.md`
        -`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`
        _Does not match_
        -`README.md`
        -`docs/hello.md` | -| -`*.md`
        -`!README.md`
        -`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`
        -`README.md`
        -`README.doc` | +| Pattern | Description of matches | Example matches | +| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`

        `server.rb` | +| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`

        `page.jsx` | +| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` | +| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`

        `index.js` | +| `'**.js'` | Matches all `.js` files in the repository. | `index.js`

        `js/index.js`

        `src/js/app.js` | +| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`

        `docs/file.txt` | +| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`

        `docs/mona/octocat.txt` | +| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`

        `docs/mona/hello-world.md`

        `docs/a/markdown/file.md` | +| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | `/docs/hello.md`

        `dir/docs/my-file.txt`

        `space/docs/plan/space.doc` | +| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`

        `js/README.md` | +| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`

        `my-src/code/js/app.js` | +| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`

        `path/their-post.md` | +| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`

        `db/migrate-v1.0.sql`

        `db/sept/migrate-v1.sql` | +| `*.md`

        `!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`

        _Does not match_

        `README.md`

        `docs/hello.md` | +| `*.md`

        `!README.md`

        `README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`

        `README.md`

        `README.doc` | diff --git a/translations/ko-KR/content/admin/authentication/using-saml.md b/translations/ko-KR/content/admin/authentication/using-saml.md index 465cdf945fc68..cc0da8403b45b 100644 --- a/translations/ko-KR/content/admin/authentication/using-saml.md +++ b/translations/ko-KR/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod ### SAML metadata -Your {% data variables.product.prodname_ghe_server %} instances's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. To configure your identity provider manually, the Assertion Consumer Service (ACS) URL is `http(s)://[hostname]/saml/consume`. It uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. diff --git a/translations/ko-KR/content/admin/configuration/command-line-utilities.md b/translations/ko-KR/content/admin/configuration/command-line-utilities.md index 45e8b6fceaf43..088c3ab5c41b6 100644 --- a/translations/ko-KR/content/admin/configuration/command-line-utilities.md +++ b/translations/ko-KR/content/admin/configuration/command-line-utilities.md @@ -468,18 +468,21 @@ ghe-webhook-logs ``` To show all failed hook deliveries in the past day: +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -To show the full hook payload, result, and any exceptions for the delivery: +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -To show global webhook deliveries: +To show the full hook payload, result, and any exceptions for the delivery: ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### Clustering diff --git a/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index aa528d974c472..c66e7118ea04c 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md index f88b3310b3ac4..8acab8920f618 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ If backup attempts overlap, the `ghe-backup` command will abort with an error me In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. You should see output similar to this: ```shell diff --git a/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index adb8908409a4a..08a27ed2a365f 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ For the users of {% data variables.product.product_location %} to be able to ena {% data reusables.enterprise_site_admin_settings.management-console %} 1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features including {% data variables.product.prodname_code_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. +{% data reusables.enterprise_management_console.advanced-security-license %} ### Enabling {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ If you can't see **{% data variables.product.prodname_advanced_security %}** in #### Setting up a self-hosted runner -If you are enrolled in the {% data variables.product.prodname_actions %} beta, then {% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." +{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions. -#### Provisioning the action -To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate action must be available locally. You can make the action available in three ways. +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisioning the actions +To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended** You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. -- You can create a local copy of the action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository with the action. For example, if you want to use the {% data variables.product.prodname_codeql %} action, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. - +- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. ##### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} - 1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configuring {% data variables.product.prodname_codeql %} on a server without internet access +If the server on which you are running +{% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} Action sync tool to copy the {% data variables.product.prodname_codeql %} actions and query bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -After you configure a self-hosted runner, users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." +#### Enabling code scanning for individual repositories +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} -If your organization isn't taking part in the beta for {% data variables.product.prodname_actions %}, or if you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. +If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, 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)." ### Disabling {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/ko-KR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..435d207f20621 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configuring secret scanning for your appliance +shortTitle: Configuring secret scanning +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### About {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +### 빌드전 요구 사양 + +To use {% data variables.product.prodname_secret_scanning %} in {% data variables.product.product_location %} you need these two prerequisites. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- You need an {% data variables.product.prodname_advanced_security %} license. + +#### Checking support for the SSSE3 flag on your vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. + +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Enter the following command: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling secret scanning](#enabling-secret-scanning)" below. + +If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. + +#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### Enabling {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Disabling {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md index f8c44f21261b9..c6791beb6a01a 100644 --- a/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} To use Docker with {% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Path without subdomain isolation | Path with subdomain isolation | -| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled. | `http(s)://docker.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Path without subdomain isolation | Path with subdomain isolation | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled for the {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### 빌드전 요구 사양 diff --git a/translations/ko-KR/content/admin/configuration/index.md b/translations/ko-KR/content/admin/configuration/index.md index 4efeb57618b89..ee042551f25e2 100644 --- a/translations/ko-KR/content/admin/configuration/index.md +++ b/translations/ko-KR/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..23e5d6e6fda33 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Managing GitHub for mobile for your enterprise +intro: You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}. +permissions: Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### About {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} For more information, see "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." + +Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data. + +### Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ko-KR/content/admin/enterprise-management/about-clustering.md b/translations/ko-KR/content/admin/enterprise-management/about-clustering.md index ee94eff1e93c5..8b3345da85472 100644 --- a/translations/ko-KR/content/admin/enterprise-management/about-clustering.md +++ b/translations/ko-KR/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ Learn more about [services required for clustering](/enterprise/{{ currentVersio Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). +{% data reusables.package_registry.packages-cluster-support %} + ### How do I get access to clustering? Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ko-KR/content/admin/enterprise-management/index.md b/translations/ko-KR/content/admin/enterprise-management/index.md index 0736f9e81df54..faaf069973dcb 100644 --- a/translations/ko-KR/content/admin/enterprise-management/index.md +++ b/translations/ko-KR/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md index a5c633d5c3eff..cf1da55ec1058 100644 --- a/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + + {% endnote %} + {% endif %} diff --git a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 34a8fd4d34738..2da8d02184f20 100644 --- a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ For more information, see "[Command-line utilities](/enterprise/{{ currentVersio #### Rolling back a feature release To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 더 읽을거리 + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md index 9ebe94e918821..128f0fb52a6b2 100644 --- a/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md @@ -59,7 +59,9 @@ After you submit your support request, we may ask you to share a support bundle - `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs - `collectd/logs/collectd.log`: Collectd logs - `mail-logs/mail.log`: SMTP email delivery logs +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`: Webhook delivery errors +{% endif %} For more information, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." diff --git a/translations/ko-KR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..3b3b6da7eb2e0 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: About using actions on GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. + +{% data reusables.actions.enterprise-no-internet-actions %} + +### Official actions bundled with {% data variables.product.prodname_ghe_server %} + +Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. + +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. + +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. + +{% note %} + +**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.prodname_ghe_server %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." + +{% endnote %} + +### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} + +If users on your enterprise instance need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. + +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} + +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/ko-KR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/ko-KR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..ca8cd4f13168c --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Advanced configuration and troubleshooting +intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..a2556020e8d72 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. + +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: + +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. +1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f1a923878847e..e744c6d757ffd 100644 --- a/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can connect {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} using {% data variables.product.prodname_github_connect %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions @@ -23,3 +23,4 @@ Before enabling access to all actions from {% data variables.product.prodname_do {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..097155565b393 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..bfa92ffd8ad83 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with Amazon S3 storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### 빌드전 요구 사양 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..44d2bc2eaef6c --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Enabling GitHub Actions with Azure Blob storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### 빌드전 요구 사양 + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..45d224d832795 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### 빌드전 요구 사양 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. +* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 37a543f948384..d47cc8b225a01 100644 --- a/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### About {% data variables.product.prodname_actions %} permissions for your enterprise diff --git a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..5d3815c6e1d6a --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. + +### Review hardware considerations + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### External storage requirements + +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. + +{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} supports these storage providers: + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Amazon S3 permissions + +{% data reusables.actions.enterprise-s3-permission %} + +### Enabling {% data variables.product.prodname_actions %} + +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/). + +### 더 읽을거리 + +- "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +### Adding self-hosted runners + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." + +### General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." + +{% endif %} diff --git a/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..26ccc90fba599 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: High availability for GitHub Actions +intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +versions: + enterprise-server: '>=3.0' +--- + +### Replication or redundancy of your {% data variables.product.prodname_actions %} data + +{% data reusables.actions.enterprise-storage-ha-backups %} + +We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: + +* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### High availability replicas + +#### Promoting a replica + +When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. + +For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." + +#### Removing a high availability replica + +Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. diff --git a/translations/ko-KR/content/admin/github-actions/index.md b/translations/ko-KR/content/admin/github-actions/index.md index 2202fdb4d4ce5..55495f30bc2f6 100644 --- a/translations/ko-KR/content/admin/github-actions/index.md +++ b/translations/ko-KR/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### Table of Contents -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 7419d7f562372..f14442789035c 100644 --- a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -To make specific actions from {% data variables.product.prodname_dotcom_the_website %} available to use in workflows, you can use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. ### About the `actions-sync` tool diff --git a/translations/ko-KR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..abbef8967ee89 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' +versions: + enterprise-server: '>=3.0' +--- + +### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + +#### Installing the certificate on the runner machine + +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. + +For the steps required to install a certificate, refer to the documentation for your runner's operating system. + +#### Configuring Node.JS to use the certificate + +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +예시: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md b/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..7287c664160e7 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). 예시: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). 예시: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-aws.md index cfd2028f7328f..3f4c7a72dace6 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ Both primary and replica instances should be assigned separate EIPs in productio ### 더 읽을거리 -- "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-azure.md index ee92ac32b8936..f375efa5782a8 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ We recommend you use a DS v2 instance type with at least 14 GB of RAM. You can u {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### 더 읽을거리 - ### 더 읽을거리 - - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index 71f0fc7669a8f..c53eec65c4af6 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll ### 더 읽을거리 -- "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index 0ff67897cec48..c27d4ec46f64e 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### 더 읽을거리 - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 95332eef1d06f..5a9d85f4753e1 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ versions: ### 더 읽을거리 - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 1e302ba6a2a74..c2810dd1fea28 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### 더 읽을거리 - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 944220eb181af..7e808d755a0d4 100644 --- a/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/ko-KR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### 더 읽을거리 - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md b/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md index 58587b35ecc05..40423fb7ded6f 100644 --- a/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ To thoroughly test a {% data variables.product.prodname_ghe_server %} appliance 1. Perform a backup of your production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the "About {% data variables.product.prodname_enterprise_backup_utilities %}" section of "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)." 2. Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." 3. Restore your backup onto your staging instance. For more information, see the "Restoring a backup" section of "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 더 읽을거리 + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..de825706c5bf8 --- /dev/null +++ b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### 더 읽을거리 + +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository diff --git a/translations/ko-KR/content/admin/overview/index.md b/translations/ko-KR/content/admin/overview/index.md index 2ff5cad9501b4..34dad300caea8 100644 --- a/translations/ko-KR/content/admin/overview/index.md +++ b/translations/ko-KR/content/admin/overview/index.md @@ -15,5 +15,6 @@ For more information, or to purchase {% data variables.product.prodname_enterpri {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..7cf17b78997ff --- /dev/null +++ b/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. For more information, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**. ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| Source | Destination | Port | 유형 | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### 다음 단계 + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ko-KR/content/admin/packages/enabling-github-packages-with-aws.md b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..f80eab1b00e9a --- /dev/null +++ b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnings:** +- It is critical that you configure any restrictive access policies you need 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 to 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 %} + +### 빌드전 요구 사양 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the S3 endpoint URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the S3 bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for S3. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for S3. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for S3. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 다음 단계 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..9b8e35c52c6f5 --- /dev/null +++ b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**Warnings:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} + +### 빌드전 요구 사양 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### 다음 단계 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ko-KR/content/admin/packages/enabling-github-packages-with-minio.md b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..f67832cf6b3aa --- /dev/null +++ b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnings:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} +### 빌드전 요구 사양 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 다음 단계 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..46a402df723f4 --- /dev/null +++ b/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`. + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." diff --git a/translations/ko-KR/content/admin/packages/index.md b/translations/ko-KR/content/admin/packages/index.md index f73f907259955..9808ef3fde913 100644 --- a/translations/ko-KR/content/admin/packages/index.md +++ b/translations/ko-KR/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..e4945e60a7454 --- /dev/null +++ b/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your third-party storage solution. + +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. + +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). + +### 1. Choose a MinIO mode for your needs + +| MinIO mode | Optimized for | Storage infrastructure required | +| ----------------------------------------------- | ------------------------------ | ------------------------------------ | +| Standalone MinIO (on a single host) | Fast setup | N/A | +| MinIO as a NAS gateway | NAS (Network-attached storage) | NAS devices | +| Clustered MinIO (also called Distributed MinIO) | Data security | Storage servers running in a cluster | + +For more information about your options, see the official [MinIO docs](https://docs.min.io/). + +### 2. Install, run, and sign in to MinIO + +1. Set up your preferred environment variables for MinIO. + + These examples use `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Install MinIO. + + ```shell + $ docker pull minio/minio + ``` + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." + +3. Sign in to MinIO using your MinIO access key and secret. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + You can access your MinIO keys using the environment variables: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Run MinIO in your chosen mode. + + * Run MinIO using Docker on a single host: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." + + * Run MinIO using Docker as a NAS gateway: + + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + For more information, see "[MinIO Gateway for NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)." + + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} + +1. Install the MinIO client. + + ```shell + $ docker pull minio/mc + ``` + +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. + + * Local deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + This example can be used for MinIO standalone or MinIO as a NAS gateway. + + * Clustered deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### 다음 단계 + +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/ko-KR/content/admin/user-management/audited-actions.md b/translations/ko-KR/content/admin/user-management/audited-actions.md index 744a09907d157..ad5dd28b4c0cf 100644 --- a/translations/ko-KR/content/admin/user-management/audited-actions.md +++ b/translations/ko-KR/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### Teams -| 이름 | 설명 | -| --------------:| ----------------------------------------------------- | -| `team.create` | A user account or repository was added to a team. | -| `team.delete` | A user account or repository was removed from a team. | -| `team.destroy` | A team was deleted. | +| 이름 | 설명 | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | A user account or repository was added to a team. | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### Users -| 이름 | 설명 | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | An email address was added to a user account. | -| `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` | A new user account was created. | -| `user.delete` | A user account was destroyed by an asynchronous job. | -| `user.demote` | A site admin was demoted to an ordinary user account. | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | A user tried to sign in with an incorrect username, password, or two-factor authentication code. | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | A user signed in. | -| `user.promote` | An ordinary user account was promoted to a site admin. | -| `user.remove_email` | An email address was removed from a user account. | -| `user.rename` | A username was changed. | -| `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` | A user account was unsuspended by a site admin. | +| 이름 | 설명 | +| -------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | An email address was added to a user account. | +| `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` | A new user account was created. | +| `user.delete` | A user account was destroyed by an asynchronous job. | +| `user.demote` | A site admin was demoted to an ordinary user account. | +| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | A user tried to sign in with an incorrect username, password, or two-factor authentication code. | +| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} +| `user.login` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `user.promote` | An ordinary user account was promoted to a site admin. | +| `user.remove_email` | An email address was removed from a user account. | +| `user.rename` | A username was changed. | +| `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` | A user account was unsuspended by a site admin. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [deploy key]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 984feddd818d7..2941a377b4dd5 100644 --- a/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,13 +4,18 @@ 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: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ You can use Markdown to format your message. For more information, see "[About w {% endnote %} +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." + ### Creating a custom sign in message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Under "Sign in page", click **Add message** or **Edit message**. ![Edit message button](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Under **Sign in message**, type the message you'd like users to see. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. Review the rendered message. ![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### Creating a custom sign out message @@ -37,12 +45,35 @@ You can use Markdown to format your message. For more information, see "[About w {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Under "Sign out page", click **Add message** or **Edit message**. ![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Under **Sign out message**, type the message you'd like users to see. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. Review the rendered message. ![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Add message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Add message button](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Creating a global announcement banner @@ -50,9 +81,8 @@ You can use Markdown to format your message. For more information, see "[About w You can set a global announcement banner to be displayed to all users at the top of every page. {% 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)." - +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)." {% else %} You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." @@ -62,9 +92,8 @@ You can also set an announcement banner in the administrative shell using a comm {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. Under "Announcement", click **Add announcement**. ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", use the calendar drop-down menu, and select an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. Optionally, to see what the banner will look like, click **Preview**. ![Preview button](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Click **Save changes**. ![Save changes button](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md b/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md index afeb51ed31866..443e4236d3cc4 100644 --- a/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ Exchange this `code` for an access token: ##### 매개변수 -| 이름 | 유형 | 설명 | -| --------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `문자열` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `client_secret` | `문자열` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `코드` | `문자열` | **Required.** The code you received as a response to Step 1. | -| `redirect_uri` | `문자열` | The URL in your application where users are sent after authorization. | -| `state` | `문자열` | The unguessable random string you provided in Step 1. | +| 이름 | 유형 | 설명 | +| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `문자열` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `문자열` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `코드` | `문자열` | **Required.** The code you received as a response to Step 1. | +| `redirect_uri` | `문자열` | The URL in your application where users are sent after authorization. | +| `state` | `문자열` | The unguessable random string you provided in Step 1. | ##### 응답 @@ -213,7 +213,7 @@ Once the user has authorized, the app will receive an access token that can be u #### Rate limits for the device flow -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). diff --git a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 2331b96d76a19..21b90267771e3 100644 --- a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ A CI server hosts code that runs CI tests such as code linters (which check styl The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: diff --git a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md index 5e7984982f059..c0637f8ed150b 100644 --- a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Available scopes -| 이름 | 설명 | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 이름 | 설명 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`(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](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | -|  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | -|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | +| **`repo`** | 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](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | Grants:
        read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
        read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | -|  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | -|  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | -| **`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. | -| **`사용자`** | 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. | +|  `security_events` | Grants:
        read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
        read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
        This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% 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. | +| **`사용자`** | 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)". | +| **`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. | +| **`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" %} | **`워크플로`** | 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 %} diff --git a/translations/ko-KR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/ko-KR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 15ede21ee3044..592796f7b2f9c 100644 --- a/translations/ko-KR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/ko-KR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Viewing transactions for your listing -intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transations 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.' +intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index f9a64fc41120d..0b58a1f3e5982 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ You can archive a classroom that you no longer use on {% data variables.product. {% data reusables.classroom.click-settings %} 1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **Read the warnings**. -1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md index b792b6c4a3ba0..359935372b7b1 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -43,3 +43,7 @@ You can configure version updates for repositories that contain a dependency man {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." diff --git a/translations/ko-KR/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/ko-KR/content/github/administering-a-repository/about-merge-methods-on-github.md index 02d653158a2fa..d8928317a6d96 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### Squashing your merge commits diff --git a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md index 13bde7762136f..c235c019e67e9 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,142 @@ --- title: About protected branches -intro: 'Protected branches ensure that collaborators on your repository cannot make irrevocable changes to branches. Enabling protected branches also allows you to enable other optional checks and requirements, like required status checks and required reviews.' +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### About protected branches +### About branch protection rules -{% data reusables.pull_requests.about-protected-branches %} You can choose to enforce restrictions on how a pull request is merged into your repository. +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -Repository owners and people with admin permissions for a repository can enforce certain workflows or requirements, before a collaborator can merge a branch in your repository by creating protected branch rules. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -{% data reusables.repositories.branch-rules-example %} For more information, see "[Configuring protected branches](/articles/configuring-protected-branches/)." +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -### Prioritization of protected branch rules +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/articles/about-pull-requests)." + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/articles/dismissing-a-pull-request-review)." + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." + +Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. + +{% note %} + +**Note:** Any person or integration with write permissions to a repository can set the state of any status check in the repository. {% data variables.product.company_short %} does not verify that the author of a check is authorized to create a check with a certain name or modify an existing status. Before merging a pull request, you should verify that the author of each status, listed in the merge box, is expected. + +{% endnote %} + +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| Type of required status check | Setting | Merge requirements | Considerations | +| ----------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Strict** | The **Require branches to be up-to-date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | +| **Loose** | The **Require branches to be up-to-date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. | + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### Require signed commits + +When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)." + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +You can always push local commits to the branch if the commits are signed and verified. {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)." + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + +Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)." + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using +{% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. + +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. + +#### Allow force pushes -If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. -Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. +Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -### Branch protection settings +{% 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. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -When you create a branch protection rule in a repository, collaborators cannot force push to the protected branch or delete the branch{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}. You can enable other branch protection settings. For information, see "[Defining the mergeability of pull requests](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)." +If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} -### 더 읽을거리 +#### Allow deletions -- "[About required status checks](/articles/about-required-status-checks)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[About required commit signing](/articles/about-required-commit-signing)" +By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/ko-KR/content/github/administering-a-repository/about-releases.md b/translations/ko-KR/content/github/administering-a-repository/about-releases.md index 194786ffab413..2ac0b5314e070 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-releases.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-releases.md @@ -25,7 +25,7 @@ You can receive notifications when new releases are published in a repository wi Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md b/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md index 013bb9b8bffcf..490a865191c33 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project. +Service providers can partner with -If someone checks a secret from a {% data variables.product.company_short %} partner into a public or private repository, {% data variables.product.prodname_secret_scanning %} can detect the secret and help you mitigate the impact of the leak. +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} -Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. For more information, see "[Secret scanning](/partnerships/secret-scanning)." +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### About {% data variables.product.prodname_secret_scanning %} for public repositories - {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)." +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. -When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. - -When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. +When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." {% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### About {% data variables.product.prodname_secret_scanning %} for private repositories +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for private repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization. {% data variables.product.prodname_secret_scanning_caps %} is not available for user account-owned private repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} -When you push commits to a private repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.product_name %} scans the contents of the commits for secrets. +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." -When {% data variables.product.prodname_secret_scanning %} detects a secret in a private repository, {% data variables.product.prodname_dotcom %} sends alerts. +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. + +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. - {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. - {% data variables.product.prodname_dotcom %} displays an alert in the repository. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." - -To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." - -{% data variables.product.product_name %} currently scans private repositories for secrets issued by the following service providers. - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} diff --git a/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md index 2718b4c036643..3ff44718d7dbd 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md @@ -3,6 +3,7 @@ title: About securing your repository intro: '{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Setting up your repository securely @@ -13,6 +14,7 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +{% if currentVersion == "free-pro-team@latest" %} - **Security policy** Make it easy for people to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)." @@ -24,18 +26,32 @@ The first step to securing a repository is to set up who can see and modify your - **{% data variables.product.prodname_dependabot_alerts %} and security updates** View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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)." + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **{% data variables.product.prodname_dependabot %} version updates** +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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." + {% endif %} - 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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** +View any secrets that - View any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: diff --git a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md index ed6802238dee4..bde7a18dd0d6d 100644 --- a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..49fe064a2659f --- /dev/null +++ b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type *.github/secret_scanning.yml*. +4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}. + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)." + + {% note %} + + **참고:** + - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans. + - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file. + + {% endnote %} + +You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)." + +### 더 읽을거리 + +- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ko-KR/content/github/administering-a-repository/index.md b/translations/ko-KR/content/github/administering-a-repository/index.md index 34e848ad4e2c2..d729992798ec0 100644 --- a/translations/ko-KR/content/github/administering-a-repository/index.md +++ b/translations/ko-KR/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/ko-KR/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..0e16b4b0291a5 --- /dev/null +++ b/translations/ko-KR/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). + +If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. + +Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. + +To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name. + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)." ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. + - Select **Require status checks to pass before merging**. ![Required status checks option](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png) + - From the list of available status checks, select the checks you want to require. ![List of available status checks](/assets/images/help/repository/required-statuses-list.png) +1. Optionally, select **Require signed commits**. ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. ![Required linear history option](/assets/images/help/repository/required-linear-history.png) +1. Optionally, select **Include administrators**. ![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png) +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png) +1. Click **Create**. + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to edit, click **Edit**. ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Click **Save changes**. ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png) + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to delete, click **Delete**. ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png) 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 9127ad2090f05..929577a15328e 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 @@ -4,6 +4,7 @@ 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: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. In the left sidebar, click **Detected secrets**. !["Detected secrets" tab](/assets/images/help/repository/sidebar-secrets.png) -4. Under "Secret scanning" click the alert you want to view. ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Optionally, use the "Resolve" drop-down menu and click a reason for resolving an alert. ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. Under "Secret scanning" click the alert you want to view. + {% if currentVersion == "free-pro-team@latest" %} + ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### Securing compromised secrets Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets: - For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old 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)." -- For all other secrets, first verify that the secret committed to {% data variables.product.prodname_dotcom %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. +- For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index 957b83f2df9a9..95e2c23fe462a 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -5,7 +5,7 @@ intro: 'You can choose whether {% data variables.large_files.product_name_long % permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ versions: {% data variables.product.product_name %} creates source code archives of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. -{% if currentVersion != "github-ae@latest" %} +{% if currentVersion == "free-pro-team@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. Each account receives {% data variables.large_files.initial_bandwidth_quota %} per month of bandwidth for free, and you can pay for additional usage. For more information, see "[About storage and bandwidth usage](/github/managing-large-files/about-storage-and-bandwidth-usage)" and "[Managing billing for {% 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 %} diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md index 90b2670783f05..fc44254ee353b 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### About release management diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index a85aa34def2c0..2fd7c6f98d873 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### Enabling or disabling security and analysis features +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### Granting access to security alerts @@ -35,7 +53,13 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. + {% if currentVersion == "free-pro-team@latest" %} + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. Click **Save changes**. !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### Removing access to security alerts @@ -43,7 +67,14 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) diff --git a/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md index b6106c1a28f84..4e0753bce3cd0 100644 --- a/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,8 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ We recommend reviewing the following caveats before you change the visibility of #### Making a repository public * {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."{% endif %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} diff --git a/translations/ko-KR/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/ko-KR/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..d07532b5f4078 --- /dev/null +++ b/translations/ko-KR/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: Troubleshooting required status checks +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." + +{% note %} + +**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/using-git/about-git-rebase)." + +{% endnote %} + +You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. This can be done without status checks running on the merge commit itself. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md index 1a76e4b67b1e3..2cb4340f51e1b 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -19,11 +19,13 @@ You can sign commits and tags locally, so other people can verify that your work If a commit or tag has a signature that cannot be verified, {% data variables.product.product_name %} marks the commit or tag as unverified. -Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About required commit signing](/articles/about-required-commit-signing)." +Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)." You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)." -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} ### GPG commit signature verification diff --git a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md index ec31f9eaff13f..ecab4e8bb862b 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -39,6 +39,7 @@ The events listed in your security log are triggered by your actions. Actions ar | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} | [`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-category-actions) | Contains all activities related to your billing information. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)." | | [`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" %} @@ -82,6 +83,12 @@ An overview of some of the most common actions that are recorded as events in th | `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). | +#### `codespaces` category actions + +| 동작 | 설명 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### `marketplace_agreement_signature` category actions | 동작 | 설명 | @@ -227,20 +234,20 @@ An overview of some of the most common actions that are recorded as events in th #### `user` category actions -| 동작 | 설명 | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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 %} +| 동작 | 설명 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% 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 %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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 @@ -249,4 +256,3 @@ An overview of some of the most common actions that are recorded as events in th | `업데이트` | 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. | - diff --git a/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index 4a006435fe993..75e04b9649619 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ With SSH keys, if someone gains access to your computer, they also gain access t You can change the passphrase for an existing private key without regenerating the keypair by typing the following command: ```shell -$ ssh-keygen -p -# Start the SSH key creation process -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/ko-KR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/ko-KR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index 621faf552a19b..be55c9339c95b 100644 --- a/translations/ko-KR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/ko-KR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ If the code of conduct you want to use isn't available in the provided templates 3. In the file name field, type the name and extension for the file. ![New code of conduct file name](/assets/images/help/repository/new-code-of-conduct-file-name.png) - To make your code of conduct visible in the repository's root directory, type *CODE_OF_CONDUCT* in the file name field. - To make your code of conduct visible in the repository's `docs` directory, type *docs/CODE_OF_CONDUCT*. - - To make your code of conduct visible in the respository's `.github` directory, type *.github/CODE_OF_CONDUCT*. + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. 4. In the new file, add your custom code of conduct. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index ac8592ffee3e7..a0a5fa25061f5 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,7 +74,7 @@ When a branch is protected: - If required status checks are enabled on the branch, you won't be able to merge changes into the branch until all of the required CI tests pass. For more information, see "[About status checks](/articles/about-status-checks)." - If required pull request reviews are enabled on the branch, you won't be able to merge changes into the branch until all requirements in the pull request review policy have been met. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)." - If required review from a code owner is enabled on a branch, and a pull request modifies code that has an owner, a code owner must approve the pull request before it can be merged. For more information, see "[About code owners](/articles/about-code-owners)." -- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. 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" %} +- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. For more information, see "[Resolving a merge conflict on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)."{% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 231340acb59be..892a82d240cb1 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,9 +44,7 @@ You can view all of the reviews a pull request has received in the Conversation ### Required reviews -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -For more information, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)." +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% tip %} @@ -57,6 +55,5 @@ For more information, see "[About required reviews for pull requests](/articles/ ### 더 읽을거리 - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Enabling required reviews for pull requests](/articles/enabling-required-reviews-for-pull-requests)" - "[Viewing a pull request review](/articles/viewing-a-pull-request-review)" - "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index 8e67b2f190375..13234c409b266 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -For more information about required reviews, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)." +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -You can comment on a pull request, approve the changes, or request improvements before approving. For more information, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" and "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." +You can comment on a pull request, approve the changes, or request improvements before approving. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ You can comment on a pull request, approve the changes, or request improvements ### 더 읽을거리 -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Commenting on a pull request](/articles/commenting-on-a-pull-request)" diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index aa0ddc953ef00..87f3cbaca7357 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ You can only make commits on pull request branches that: - are opened in a repository that you have push access to and that were created from a fork of that repository - are on a user-owned fork - have permission granted from the pull request creator -- don't have [branch restrictions](/articles/about-branch-restrictions) that will prevent you from committing +- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)." diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index 080075e5da8bf..fca424e929c4d 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Dismissing a pull request review -intro: 'If your repository [requires reviews](/articles/about-required-reviews-for-pull-requests), you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ This changes the status of the review to a review comment. When you dismiss a re - "[About pull request reviews](/articles/about-pull-request-reviews)" - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" +- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index 419f234613f5e..f34801e48694f 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### Following the GitHub flow 1. [Create a branch](/articles/creating-and-deleting-branches-within-your-repository) from the repository. -2. [Create](/articles/creating-new-files), [edit](/articles/editing-files), [rename](/articles/renaming-a-file), [move](/articles/moving-a-file-to-a-new-location), or [delete](/articles/deleting-files) files. +2. [Create](/articles/creating-new-files), [edit](/articles/editing-files), [rename](/articles/renaming-a-file), [move](/articles/moving-a-file-to-a-new-location), or [delete](/github/managing-files-in-a-repository/deleting-files-in-a-repository) files. 3. [Send a pull request](/articles/creating-a-pull-request) from your branch with your proposed changes to kick off a discussion. 4. Make changes on your branch as needed. Your pull request will update automatically. 5. [Merge the pull request](/articles/merging-a-pull-request) once the branch is ready to be merged. diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 505a76c8cee66..2feea860ffabe 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### About pull request merges -In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. {% data reusables.pull_requests.about-protected-branches %} However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 308d7f0f335ce..3d042481667c5 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ Dependency review supports the same languages and package management ecosystems ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ Dependency review supports the same languages and package management ecosystems * The severity of the vulnerability. * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. -1. You can return to the original view of the file by clicking the source diff button. - - ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index ed9d6ec646acc..b27e679777441 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,9 +36,11 @@ If the pull request contains changes to dependencies you can use the dependency {% data reusables.repositories.changed-files %} -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### Marking a file as viewed @@ -65,5 +67,5 @@ After you've finished reviewing all the files you want in the pull request, subm ### 더 읽을거리 -- "[About required reviews for pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 5359a129f5dc8..92c72b204e335 100644 --- a/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/ko-KR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ Organization's can use the `name@organization.com` email as a public point of co ### Creating commits with an `on-behalf-of` badge on the command line -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} 2. On the next line of the commit message, type `on-behalf-of: @org `, then a closing quotation mark. 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 02095f93753c0..c75426276807e 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 @@ -39,7 +39,17 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer. + + {% endtip %} 3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 28792050765c8..97cf8f92a7b52 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -19,7 +19,7 @@ The people you choose as code owners must have write permissions for the reposit Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)." -When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[Enabling required reviews for pull requests](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)." +When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% 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. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index 00fb2c63f3e2d..07dd62caa9888 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ Each person and organization can own unlimited repositories and invite an unlimi {% endif %} You can use repositories to manage your work and collaborate with others. -- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." -- {% data reusables.discussions.you-can-use-discussions %} +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." - You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 45018e2271d09..fd92f5e5883a0 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ When you search by a family license, your results will include all licenses in t ### Detecting a license -[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/ko-KR/content/github/developing-online-with-codespaces/about-codespaces.md index 6c0e0d29f1231..2413aeac6d416 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ Each developer can create one or more codespace for any public repository, or fo {% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/index.md b/translations/ko-KR/content/github/developing-online-with-codespaces/index.md index d53f3e92fbc89..1ec4ada1215cd 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/index.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..51a8db1372fa6 --- /dev/null +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Click **Add secret**. + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Click **Save changes**. + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/ko-KR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index b91786592aca6..82f3e06a5e0d4 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ For more information, see [Personalizing](https://docs.microsoft.com/visualstudi {% endnote %} +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 767b7ad31133d..f2b6b52495f76 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." @@ -54,7 +54,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam ### 더 읽을거리 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[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 diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index bf973e9662b45..20b3fb7313bc4 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -236,7 +236,9 @@ 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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +The settings in the file are written in YAML format. #### Specifying additional queries 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 da95b53eef48f..f1204140aeb1f 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 @@ -40,13 +40,16 @@ You decide how you generate {% data variables.product.prodname_code_scanning %} 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. +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + ### Viewing the logging output from {% 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. {% 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'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index d825538c9916f..db74c3cd53abe 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ You can use the {% data variables.product.prodname_codeql_runner %} to run {% da The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**참고:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} ### Downloading the {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi ### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux In addition to this, each CI server also needs: -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." +- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: 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 721b4060208d5..b2eded39f15cb 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 @@ -15,7 +15,7 @@ versions: In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the 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. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository 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)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. For more information, see "[About required status checks](/github/administering-a-repository/about-required-status-checks)." +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index 05cc0e7610ba4..9f9f6427bb61b 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### The `init` command takes too long 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 43c891b98ffaf..d9f4af97edf41 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Automatic build for a compiled language fails @@ -83,17 +84,6 @@ For more information about specifying build steps, see "[Configuring the {% data The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. 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)." -### Error: "Server error" - -If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. - -### Error: "Out of disk" or "Out of memory" -On very large projects, - -{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - ### The build takes too long If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. @@ -128,3 +118,54 @@ If you are analyzing code written in Python, you may see different results depen On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." {% endif %} + +### Error: "Server error" + +If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. + +### Error: "Out of disk" or "Out of memory" +On very large projects, + +{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index fc2866d1fa26a..cbf5073a9dfe9 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -24,9 +24,11 @@ You can upload the results using {% data variables.product.prodname_actions %}{% - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis. - {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). -- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, 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)"). +- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)"). +{% data reusables.code-scanning.not-available %} + ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %} To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." @@ -110,5 +112,5 @@ jobs: - "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" - "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)" -- "[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)" +- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)" - "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)" diff --git a/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..b923b08a6cfd9 --- /dev/null +++ b/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### About {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)." + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md b/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md index fd1bc6113d99f..ccb0d5f42c8a7 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: GitHub for mobile -intro: 'Triage, collaborate, and manage your work on {% data variables.product.company_short %} from your mobile device.' +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### About {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} is currently available for {% data variables.product.prodname_dotcom_the_website %} users as an Android and iOS app. +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.prodname_dotcom %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.prodname_dotcom %} data through a trusted, first-party client application. +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. With {% data variables.product.prodname_mobile %} you can: - Manage, triage, and clear notifications @@ -23,12 +26,38 @@ For more information about notifications for {% data variables.product.prodname_ To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### 빌드전 요구 사양 + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + ### Supported languages for {% data variables.product.prodname_mobile %} {% data variables.product.prodname_mobile %} is available in the following languages. +- 영어 - Japanese - Brazilian Portuguese +- Simplified Chinese - 스페인어 If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. @@ -37,9 +66,9 @@ If you configure the language on your device to a supported language, {% data va {% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. -To disable Universal Links, long-press any {% data variables.product.prodname_dotcom %} link, then tap **Open**. Every time you tap a {% data variables.product.prodname_dotcom %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -To re-enable Universal Links, long-press any {% data variables.product.prodname_dotcom %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. ### Sharing feedback diff --git a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md index 3735db6d8132a..becafddba7efd 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: GitHub's products +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ For more information about hosting your own instance of [{% data variables.produ - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} - [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations) -For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact [{% data variables.product.product_name %}'s Sales team](https://enterprise.github.com/contact). +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ko-KR/content/github/getting-started-with-github/index.md b/translations/ko-KR/content/github/getting-started-with-github/index.md index 7616a6b80d916..567c6262b3f6c 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/index.md +++ b/translations/ko-KR/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md index b775002844ce4..a4407409b5796 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -29,14 +29,14 @@ Below is a list of some of the available keyboard shortcuts. ### Repositories -| Keyboard shortcut | 설명 | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Go to the **Code** tab | -| g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." | -| g p | Go to the **Pull requests** tab. 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" %} +| Keyboard shortcut | 설명 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | Go to the **Code** tab | +| g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." | +| g p | Go to the **Pull requests** tab. 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" %} | g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} -| g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." | -| g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." | +| g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." | +| g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." | ### Source code editing @@ -159,6 +159,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | 설명 | | --------------------------------------------------------- | --------------------------------------------------------------- | | command + space or control + space | In the workflow editor, get suggestions for your workflow file. | +| g f | Go to the workflow file | +| shift + t or T | Toggle timestamps in logs | +| shift + f or F | Toggle fullscreen logs | +| esc | Exit fullscreen logs | {% endif %} diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..33a59c439b213 --- /dev/null +++ b/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. For more information, see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)." + +### Deleting a file + +1. Browse to the file in your repository that you want to delete. +2. At the top of the file, click +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/index.md b/translations/ko-KR/content/github/managing-files-in-a-repository/index.md index d1765daf5e40a..faf07b3fb4585 100644 --- a/translations/ko-KR/content/github/managing-files-in-a-repository/index.md +++ b/translations/ko-KR/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/ko-KR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index 871ca7b29bf8e..f98e0eb12198d 100644 --- a/translations/ko-KR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/ko-KR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ You can link to a particular row by clicking the row number, or select multiple ### Searching data -If you want to find a certain value in your dataset, you can start typing in the search bar directly above the file. The rows will filter automagically: +If you want to find a certain value in your dataset, you can start typing in the search bar directly above the file. The rows will filter automatically: ![Searching for values](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/ko-KR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/ko-KR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 3f93be6abaede..fe1c28f5d3c35 100644 --- a/translations/ko-KR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/ko-KR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ When you commit and push a change to a file tracked with {% data variables.large - If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth. - If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ko-KR/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/ko-KR/content/github/managing-large-files/configuring-git-large-file-storage.md index 4c5d794c94e55..2f6c7c6afbbbe 100644 --- a/translations/ko-KR/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/ko-KR/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ If there are existing files in your repository that you'd like to use {% data va ### 더 읽을거리 -- "[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" %} +- "[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@3.0" or currentVersion == "github-ae@latest" %} - "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index c242a0d8b6740..67fe17daa4e6e 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -33,3 +33,7 @@ When you merge a pull request that contains a security update, the corresponding ### About compatibility scores {% 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. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." \ No newline at end of file diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index 035e314e87377..31b8e2af0a5fd 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -42,16 +42,18 @@ If security updates are not enabled for your repository and you don't know why, ### Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories -You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository. +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} 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)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Above the list of alerts, use the drop-down menu and select or unselect **{% data variables.product.prodname_dependabot %} security updates**. ![Drop-down menu with the option to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 266167b8040da..06d0cf9902844 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ You can configure notification settings for yourself or your organization from t {% note %} -**Note:** You can filter your {% data variables.product.company_short %} inbox notifications to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)." +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." {% endnote %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index dd179ef0df0c7..c6d6ca09fe44a 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,13 +78,15 @@ The best way to resolve this error is to merge or close some of the existing pul #### {% data variables.product.prodname_dependabot %} can't resolve your dependency files -**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a 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**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 3c15a48c54317..27b9df7ff82ad 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notifications and subscriptions You can choose to receive ongoing updates about specific activity on {% data variables.product.product_name %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to. @@ -50,7 +54,7 @@ To unsubscribe from conversations you're automatically subscribed to, you can ch ### Customizing notifications and subscriptions -You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see “[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).” @@ -58,7 +62,7 @@ To keep your subscriptions manageable, review your subscriptions and watched rep To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see “[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).” -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} You can enable push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." {% endif %} @@ -89,7 +93,7 @@ From your inbox you can also triage multiple notifications at once. For more inf ### Customizing your notifications inbox -To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Notification retention policy diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index b229070b4fd07..1da15e38ce329 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notification delivery options You can receive notifications for activity on {% data variables.product.product_name %} in the following locations. - - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." {% endif %} @@ -35,7 +39,7 @@ You can receive notifications for activity on {% data variables.product.product_ #### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - Triage multiple notifications at once. - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. @@ -45,7 +49,7 @@ The notifications inbox on {% data variables.product.product_name %}{% if curren - Create custom filters to focus on different notifications when you want. - Group notifications in your inbox by repository or date to get a quick overview with less context switching -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} In addition, the notifications inbox on {% data variables.product.prodname_mobile %} allows you to triage notifications in dark mode and receive push notifications for direct mentions. For more information, see "[Enabling push notifications with GitHub for mobile](#enabling-push-notifications-with-github-for-mobile)" or "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." {% endif %} @@ -77,7 +81,7 @@ You can customize notifications for a repository, for example, you can choose to #### Participating in conversations Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox. -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %}. +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. ![Participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -85,7 +89,7 @@ For conversations you're watching or participating in, you can choose whether yo - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications. - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating". -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}, then your notifications inbox will not have any updates. +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. ### Customizing your email notifications @@ -197,13 +201,15 @@ Choose how you want to receive workflow run updates for repositories that you ar {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Enabling push notifications with {% data variables.product.prodname_mobile %} When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. You can then enable push notifications for direct mentions within the app. You can only receive notifications for pushes to repositories on {% data variables.product.prodname_mobile %} at this time. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Enabling push notifications with {% data variables.product.prodname_ios %} 1. Above "Home", tap your profile photo. @@ -211,9 +217,11 @@ You can only receive notifications for pushes to repositories on {% data variabl 3. To update your notification settings, tap **Push notifications**. 4. To turn on push notifications for direct mentions, use the **Direct Mentions** toggle. +{% if currentVersion == "free-pro-team@latest" %} #### Enabling push notifications with {% data variables.product.prodname_android %} 1. Above "Home", tap your profile photo. 2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. ![Settings icon for GitHub for Android](/assets/images/help/mobile/android-settings-icon.png) 3. To turn on push notifications for direct mentions, use the **Direct mentions** toggle. {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 2540bee0afc9f..dd7f63681efd4 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: Managing notifications from your inbox -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}.' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### About your inbox -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} @@ -86,31 +90,16 @@ Custom filters do not currently support: ### Supported queries for custom filters -There are three types of filters that you can use: +These are the types of filters that you can use: - Filter by repository with `repo:` - Filter by discussion type with `is:` - - Filter by notification reason with `reason:` - -To add a `repo:` filter, you must include the owner of the repository in the query. For example, `repo:atom/atom` represents the Atom repository owned by the Atom organization. + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -#### Supported `reason:` queries +#### Supported `repo:` queries -To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." - -| Query | 설명 | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. | -| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. | -| `reason:comment` | When you commented on an issue, pull request, or team discussion. | -| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. | -| `reason:invitation` | When you're invited to a team, organization, or repository. | -| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | -| `reason:mention` | You were directly @mentioned. | -| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | -| `reason:team-mention` | When a team you're a member of is @mentioned. | -| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. | +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. #### Supported `is:` queries @@ -138,3 +127,59 @@ You can also use the `is:` query to describe how the notification was triaged. - `is:done` - `is:unread` - `is:read` + +#### Supported `reason:` queries + +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." + +| Query | 설명 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. | +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. | +| `reason:comment` | When you commented on an issue, pull request, or team discussion. | +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. | +| `reason:invitation` | When you're invited to a team, organization, or repository. | +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | +| `reason:mention` | You were directly @mentioned. | +| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | +| `reason:team-mention` | When a team you're a member of is @mentioned. | +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. | + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 66278fee44646..7c9b4621a13af 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ When you unsubscribe from notifications in your inbox, they will automatically d {% data reusables.notifications.access_notifications %} 1. From the notifications inbox, select the notifications you want to unsubscribe to. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubcribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Unsubscribing from notifications on the subscriptions page @@ -64,4 +64,4 @@ When you unwatch a repository, you unsubscribe from future updates from that rep - unwatch a repository - ignore all notifications for a repository - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md b/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md index 9897fe9bb54dc..a5b734a43876d 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md @@ -14,9 +14,11 @@ versions: You can collect user feedback, report software bugs, and organize tasks you'd like to accomplish with issues in a repository. Issues can act as more than just a place to report software bugs. +{% if currentVersion == "free-pro-team@latest" %} Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/ko-KR/content/github/managing-your-work-on-github/changing-project-board-visibility.md index bbe7533159b35..2800bfde73f51 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Changing project board visibility -intro: 'As an organization owner or project board admin, you can make a project board public or private.' +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**Tip:** When you make your project board public, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} -1. Navigate to the project board you want to make public or private. +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. Under "Visibility", select **Public** or **Private**. Then, click **Save**. ![Public and private radio buttons](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. Click **Save**. diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/ko-KR/content/github/managing-your-work-on-github/copying-a-project-board.md index f1dd5e244212f..98b0314ce833c 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ A project board's automation is also enabled by default. For more information, s 5. Optionally, under "Project board name", type the name of the copied project board. ![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png) 6. Optionally, under "Description", type a description of the copied project board that other people will see. ![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png) 7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)." ![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. If you are copying an organization-owned project board, under "Visibility", select whether you want your copied project board to be private or public. ![Select visibility settings for copied project board](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. Click **Copy project**. ![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/ko-KR/content/github/managing-your-work-on-github/creating-a-project-board.md index 2a4163a430ce8..bcf53097cd460 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/ko-KR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 3831b27b8012f..bfdf885363657 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: You can filter a repository's list of pull requests to find: - Pull requests that haven't been [reviewed](/articles/about-pull-request-reviews) yet -- Pull requests that [require a review](/articles/about-required-reviews-for-pull-requests) before they can be merged +- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged - Pull requests that a reviewer has approved - Pull requests in which a reviewer has asked for changes - Pull requests that you have reviewed diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md index 97c332fe04f9b..e04d5b2d5865c 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize issues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. -Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository. +Anyone with read access to a repository can view and search the repository’s labels. Anyone with triage access to a repository can apply/dismiss existing labels. To create, edit, apply, or delete a label, you must have write access to the repository. ### About default labels @@ -91,7 +91,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### 더 읽을거리 -- "[About labels](/articles/about-labels)" - "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index e8f62a0662a4f..d121c952db713 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -36,7 +36,7 @@ For issues, you can also use search to: For pull requests, you can also use search to: - Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft` - Filter pull requests that haven't been [reviewed](/articles/about-pull-request-reviews) yet: `state:open type:pr review:none` -- Filter pull requests that [require a review](/articles/about-required-reviews-for-pull-requests) before they can be merged: `state:open type:pr review:required` +- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required` - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` - Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-commits.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-commits.md index 3c370b8deed36..fe2785b22853d 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-commits.md @@ -51,7 +51,7 @@ Use the `author-date` and `committer-date` qualifiers to match commits authored | Qualifier | 예시 | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) matches commits committed after 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | ### Filter merge commits diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index b1c8f2ef96e52..26ff911ddf42c 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: After you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. When a member accesses resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}, where the member can access your organization's resources. -Enterprise owners can also enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ If members are signed in with a SAML SSO session when they create a new reposito Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. +{% data reusables.saml.saml-single-logout-not-supported %} + ### Supported SAML services {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ Some IdPs support provisioning access to a {% data variables.product.prodname_d After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." -{% data reusables.organizations.team-synchronization %} - To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization. If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 3365dae5aba48..0bd50389d9f34 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ These identity providers are compatible with the {% data variables.product.produ - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index adf67062b63fa..a63e3238f8609 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ For each pending collaborator, you can cancel all invitations to join organizati {% data reusables.organizations.people_tab_outside_collaborators %} 5. Click **X pending collaborators**. !["Pending collaborators" button](/assets/images/help/organizations/pending-collaborator-list.png) 6. To the right of the person you want to cancel invitations for, click **Cancel invitations**. !["Cancel invitation" button](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Click **Cancel invitations for pending collaborators**. ![Button to confirm cancelation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. Click **Cancel invitations for pending collaborators**. ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md index d1c440e8c5762..a3ee6b1216a88 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index cdd76927c42c0..8e1a5def02fd9 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Managing security and analysis settings for your organization intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.' permissions: Organization owners can manage security and analysis settings for repositories in the organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### About management of security and analysis settings -{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. +{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Enabling or disabling a feature for all existing repositories +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -### Enabling or disabling a feature for all new repositories when they are added +### Enabling or disabling a feature automatically when new repositories are added 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Allowing Dependabot to access private repositories -{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." 1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) 1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. 1. Click **Select repositories**. - +{% endif %} ### 더 읽을거리 -{% if currentVersion == "free-pro-team@latest" %}- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)" -- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} +- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" - "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index f3dc5c0b34b38..4cac60e0c5d17 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ For example, if an organization owner has given all organization members read pe ### Project board visibility -{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to public and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." ### 더 읽을거리 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 70abab0725beb..2a26e5b6d0e13 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,91 +43,94 @@ 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** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %}{% if currentVersion == "free-pro-team@latest" %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| 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#granting-access-to-security-alerts) 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** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 1fe1d8b2938aa..bc454f6548675 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -64,8 +64,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`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-category-actions) | Contains all activities related to teams in your organization.{% endif %} +| [`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 %} +| [`팀`](#team-category-actions) | Contains all activities related to teams in your organization. | | [`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. 예시: @@ -198,7 +198,7 @@ An overview of some of the most common actions that are recorded as events in th | 동작 | 설명 | | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `비활성화` | 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)." | -| `활성화` | Triggered when an organization owner enbles {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | +| `활성화` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | #### `dependabot_security_updates` category actions @@ -325,6 +325,8 @@ For more information, see "[Restricting publication of {% data variables.product | 동작 | 설명 | | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." | +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. | | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). | | `cancel_invitation` | Triggered when an organization invitation has been revoked. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} @@ -448,15 +450,17 @@ For more information, see "[Restricting publication of {% data variables.product #### `repo` category actions -| 동작 | 설명 | -| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `액세스` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | -| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). | -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. | +| 동작 | 설명 | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `액세스` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). | +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." | +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `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).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} @@ -465,12 +469,12 @@ For more information, see "[Restricting publication of {% data variables.product | `활성화` | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.{% endif %} | `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} -| `remove_topic` | Triggered when a repository admin removes a topic from a repository. | -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). | -| `전송` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). | -| `transfer_start` | Triggered when a repository transfer is about to occur. | +| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `remove_topic` | Triggered when a repository admin removes a topic from a repository. | +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). | +| `전송` | 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 admin unarchives a repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret.{% endif %} @@ -560,7 +564,7 @@ For more information, see "[Restricting publication of {% data variables.product | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `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)") | @@ -569,20 +573,18 @@ For more information, see "[Restricting publication of {% data variables.product | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` category actions -| 동작 | 설명 | -| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). | -| `add_repository` | Triggered when a team is given control of a repository. | -| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | -| `change_privacy` | Triggered when a team's privacy level is changed. | -| `create` | Triggered when a new team is created. | -| `destroy` | Triggered when a team 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). | -| `remove_repository` | Triggered when a repository is no longer under a team's control. | -{% endif %} +| 동작 | 설명 | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). | +| `add_repository` | Triggered when a team is given control of a repository. | +| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | +| `change_privacy` | Triggered when a team's privacy level is changed. | +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. #### `team_discussions` category actions diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index e9991559b706f..8ceeae0759ca4 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: You can connect up to five IdP groups to a {% data variables.product.prodname_dotcom %} team. An IdP group can be assigned to multiple {% data variables.product.prodname_dotcom %} teams without restriction. +Team synchronization does not support IdP groups with more than 5000 members. + Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %} or using the API. All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." @@ -27,19 +29,22 @@ You can also manage team synchronization with the API. For more information, see ### Requirements for members of synchronized teams -After you connect a team to an IdP group, membership data for each team member will synchronize if the person continues to authenticate using SAML SSO with the same SSO identity on {% data variables.product.prodname_dotcom %}, and if the person remains a member of the connected IdP group. +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -Existing teams or group members can be automatically removed from the team on {% data variables.product.prodname_dotcom %}. Any existing teams or group members not authenticating to the organization or enterprise account using SSO may lose access to repositories. Any existing teams or group members not in the connected IdP group may potentially lose access to repositories. +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. -To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." +To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." ### 빌드전 요구 사양 -Before you can connect a team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Before you can connect a team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index a493f836a2086..d398b01a7c57e 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ You can view and revoke each member's linked identity, active sessions, and auth {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..f8e9441c103dc --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. + +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..9ffac5db1a019 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. + +For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: + +- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). +- Cancel any existing invitations for the user to join an organization owned by your enterprise account. + +For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: + +- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. + +If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." + +To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index f6026095da574..11efdfaee1eaf 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ After you enable SCIM, the following provisioning features are available for any 1. To the right of the drop-down menu, type `.*.*`. 1. Click **Save**. {% data reusables.saml.okta-view-setup-instructions %} -1. Enable SAML for your enterprise account using the information in the setup instructions. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +1. Enable SAML for your enterprise account using the information in the setup instructions. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." ### Creating groups in Okta diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..98de9573eab39 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: Enabling SAML single sign-on for organizations in your enterprise account +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)." + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. + +{% endnote %} + +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) +8. Under **Public Certificate**, paste a certificate to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) +9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) +10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) +11. Click **Save**. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index dbcff8becf87b..8b564bc174010 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ You can also configure allowed IP addresses for an individual organization. For {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### Enabling SAML single sign-on for organizations in your enterprise account - -{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)." - -Enterprise owners can enable SAML SSO and centralized authentication through a SAML IdP across all organizations owned by an enterprise account. After you enable SAML SSO for your enterprise account, SAML SSO is enabled by default for all organizations owned by your enterprise account. All members will be required to authenticate using SAML SSO to gain access to the organizations where they are a member, and enterprise owners will be required to authenticate using SAML SSO when accessing an enterprise account. - -{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[Managing user provisioning for organizations in your enterprise account](#managing-user-provisioning-for-organizations-in-your-enterprise-account)." - -{% note %} - -**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. - -{% endnote %} - -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -8. Under **Public Certificate**, paste a certificate to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -11. Click **Save**. - -### Managing user provisioning for organizations in your enterprise account - -Enterprise owners can manage organization membership in an enterprise account directly from an identity provider (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. - -If you configure SCIM in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. - -For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: - -- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). -- Cancel any existing invitations for the user to join an organization owned by your enterprise account. - -For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: - -- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. - -If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." - -To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." - -### Managing team synchronization for organizations in your enterprise account - -Enterprise owners can enable team synchronization between an IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in the organizations owned by your enterprise account with IdP groups. - -{% data reusables.identity-and-permissions.about-team-sync %} - -You can use team synchronization with your enterprise account with Azure AD. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -You can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." - -#### 빌드전 요구 사양 - -Before you can enable team synchronization for your enterprise account: - - You or your Azure AD administrator must be a Global administrator or a Privileged Role administrator in Azure AD. - - You must enable SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." - - You must authenticate to your enterprise account using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." - -#### Managing team synchronization for Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Review the identity provider tenant information you want to connect to your enterprise account, then click **Approve**. ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png) -8. To disable team synchronization, click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) - ### Managing your enterprise account's SSH certificate authorities Enterprise owners can add and delete an enterprise account's SSH certificate authorities (CA). @@ -203,3 +112,7 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### 더 읽을거리 + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md index 6d144e7ecc7d8..4dae4a37df1c6 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + 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 cf50de80748be..d5f6884ead6d3 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 @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." @@ -27,11 +29,13 @@ For more information about {% data variables.product.prodname_enterprise %}, see 3. On {% data variables.product.prodname_dotcom_the_website %}, create at least one organization owned by your enterprise account. For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." -4. The subscriber must create a user account on {% data variables.product.prodname_dotcom_the_website %}, and the email address for the account must be the same email address as the email address in the {% data variables.product.prodname_vs %} portal. For more information, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." - ### Inviting a subscriber to use {% data variables.product.prodname_enterprise %} -To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber must join an organization owned by your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Organization owners can invite new members to an organization. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." ### Viewing {% data variables.product.prodname_enterprise %} licensing diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..6ee2e5104ffeb --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Managing team synchronization for organizations in your enterprise account +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +You can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." + +### 빌드전 요구 사양 + +You or your Azure AD administrator must be a Global administrator or a Privileged Role administrator in Azure AD. + +You must enable SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +You must authenticate to your enterprise account using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +### Managing team synchronization for Azure AD + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png) +8. To disable team synchronization, click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index 20b9ebbda5ea5..5ac9d2f572908 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." {% data reusables.enterprise-accounts.access-enterprise %} 2. To the right of the search field, click **X unowned**. ![Button to view unowned organizations](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index e887ccc08c9cd..6b854249eaf5b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,6 +18,8 @@ When you enable SAML single sign-on for your enterprise account, each enterprise {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index e799f3f2379a7..3b2c0ceb764ff 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -22,8 +22,8 @@ For more information about managing billing managers, see "[Inviting people to m {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Under "User +1. 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. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![License and subscription information in enterprise billing settings](/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 %}**. +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index b53c1b31ddcec..7ae019b08119b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -39,20 +39,20 @@ You can use the `git show` command with the `--pretty=fuller` flag to check if t $ git show Your commit SHA number --pretty=fuller commit Your commit SHA number Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` If the author and commit date are different, you can manually change the commit date in the URL to see the commit details. 예시: -- This URL uses the author date of `2016-07-13`: +- This URL uses the author date of `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- This URL uses the commit date of `2016-07-19`: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- This URL uses the commit date of `2018-04-10`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` When you open the URL with the modified commit date, you can see the commit details. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 38eab27d21bc5..ca94ed460612c 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### Contributions that are counted -#### Issues and pull requests +#### Issues, pull requests and discussions -Issues and pull requests will appear on your contribution graph if they were opened in a standalone repository, not a fork. +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. #### Commits Commits will appear on your contributions graph if they meet **all** of the following conditions: diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index 3a12936ae62a3..0be3994f157bc 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,7 +14,7 @@ versions: For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. {% data reusables.user_settings.access_settings %} -1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) 1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 9a65b427d8ffc..ae379d699dd67 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,7 +30,8 @@ The repository owner has full control of the repository. In addition to the acti | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" | | Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" | | Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} @@ -63,7 +64,8 @@ Collaborators can also perform the following actions. | 동작 | More information | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Create, edit, and delete comments on commits, pull requests, and issues in the repository |
        • "[About issues](/github/managing-your-work-on-github/about-issues)"
        • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
        • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
        | | Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | | Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 0cc007518b202..c96f9e898a3c3 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ There are three levels of permissions for project board collaborators: The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can: - [Manage, view, and add collaborators](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configure a project board as public or private](/articles/changing-project-board-visibility) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) - [Delete a project board](/articles/deleting-a-project-board/) - [Close a project board](/articles/closing-a-project-board/) - [Reopen a closed project board](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ Collaborators with write access to a user-owned project board can: ### Project board visibility -You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md b/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md index 1ad06f6c82d4f..4f17ebc9955d1 100644 --- a/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com, GitHub Enterprise Server, and the information you upload to either product may be subject to trade control regulations, including under the U.S. Export Administration Regulations (the EAR). -GitHub’s vision is to be the global platform for developer collaboration, no matter where developers reside. We take seriously our responsibility to examine government mandates thoroughly to be certain that users and customers are not impacted beyond what is required by law. This includes keeping public repositories services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. +GitHub’s vision is to be the global platform for developer collaboration, no matter where developers reside. We take seriously our responsibility to examine government mandates thoroughly to be certain that users and customers are not impacted beyond what is required by law. This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. -To comply with U.S. trade control laws, GitHub made some required changes to the way we conduct our services. As U.S. trade controls laws evolve, we will continue to work with U.S. regulators about the extent to which we can offer free code collaboration services to developers in sanctioned markets. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those markets. For more insight on our approach and how sanctions affect global software collaboration, read our [blog on sanctions](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Although we've provided the following information below for your convenience, it is ultimately your responsibility to ensure that your use of GitHub's products and services complies with all applicable laws and regulations, including U.S. export control laws. @@ -25,9 +25,9 @@ Under our [Terms of Service](/articles/github-terms-of-service), users may only Users are responsible for ensuring that the content they develop and share on GitHub.com complies with the U.S. export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). The cloud-hosted service offering available at [GitHub.com](https://github.com) has not been designed to host data subject to the ITAR and does not currently offer the ability to restrict repository access by country. If you are looking to collaborate on ITAR- or other export-controlled data, we recommend you consider [GitHub Enterprise Server](https://enterprise.github.com), GitHub's on-premises offering. -U.S. trade control laws restrict what GitHub.com services can be made available to users in certain countries and territories. GitHub may allow users in or ordinarily resident in countries and territories subject to U.S. sanctions to access certain free GitHub.com services for personal communications in accordance to authorizations issued by the U.S. Treasury Department’s Office of Foreign Assets Controls (OFAC). Persons in or ordinarily resident in these countries and territories are prohibited from using IP proxies, VPNs, or other methods to disguise their location when accessing GitHub.com services, and may only use GitHub.com for non-commercial, personal communications. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs) and other denied or blocked parties under U.S. and other applicable law are prohibited from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### GitHub Enterprise Server @@ -41,7 +41,7 @@ GitHub Enterprise Server may not be sold to, exported, or re-exported to any cou #### On which countries and territories are U.S. government sanctions applied? -Crimea, Cuba, Iran, North Korea, and Syria. +Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. #### How is GitHub ensuring that folks not living in and/or having professional links to the sanctioned countries and territories still have access or ability to appeal? @@ -55,23 +55,23 @@ Travel in these regions may impact your account status, but availability may be #### What is available and not available? -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -However, due to U.S. trade controls law restrictions, GitHub is unable to provide private repository services and paid services to accounts in U.S. sanctioned regions like North Korea, Iran, Syria, and Crimea. The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. -For paid organizational accounts in sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. #### How do you define these specific users? -If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. +If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. #### How are organization accounts impacted? -If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. -The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### Can trade-restricted users’ private repositories be made public? @@ -81,3 +81,16 @@ Free individual account users can make restricted private repositories public, f Unfortunately, our understanding of the law does not give us the option to allow downloads or deletion of private repository content, until otherwise authorized by the U.S. government. We will strongly advocate, with U.S. regulators, for the right of trade-restricted users to secure the contents of their private repositories. We will also advocate for more availability of GitHub services for developers in sanctioned markets, and further underscore the importance of code collaboration in supporting personal communications for developers globally. +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/ko-KR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/ko-KR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index 5ea4f4e319457..97bff67a756e9 100644 --- a/translations/ko-KR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/ko-KR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ That said, if legal action is initiated by a third party, including law enforcem ### 3. Limited Waiver of Other Site Polices -To the extent your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but are consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first! +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first! diff --git a/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md index 682a7ad013ca2..0b0e7594bfe8e 100644 --- a/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **December 30, 2020** +Effective date: **January 6, 2021** GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -25,12 +25,9 @@ When we share your information with third party subprocessors, such as our vendo | Braintree (PayPal) | Subscription credit card payment processor | United States | United States | | Clearbit | Marketing data enrichment service | United States | United States | | Discourse | Community forum software provider | United States | United States | -| DiscoverOrg | Marketing data enrichment service | United States | United States | | Eloqua | Marketing campaign automation | United States | United States | | Google Apps | Internal company infrastructure | United States | United States | | Google Analytics | Analytics and performance | United States | United States | -| LinkedIn Navigator | Data enrichment service | United States | United States | -| Magic Robot | Campaign reporting (Salesforce Add-on) | United States | United States | | MailChimp | Customer ticketing mail services provider | United States | United States | | Mailgun | Transactional mail services provider | United States | United States | | Microsoft | Microsoft Services | United States | United States | diff --git a/translations/ko-KR/content/github/site-policy/index.md b/translations/ko-KR/content/github/site-policy/index.md index 2fb09f3fabffc..03094d4478abd 100644 --- a/translations/ko-KR/content/github/site-policy/index.md +++ b/translations/ko-KR/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 62daa89c406e4..a283f8c2ee8d4 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ You can view analytics on your current and past sponsorships, the payments you'v ### Viewing recent sponsorship activity {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### Exporting your sponsorship data -If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Click **Export all**. ![Export all button](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Export button](/assets/images/help/sponsors/export-all.png) 1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index 3a8fdee7902a9..066559c59fd7b 100644 --- a/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/ko-KR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -21,7 +21,7 @@ When you enable data use for your private repository, you'll be able to access t {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/using-git/adding-a-remote.md b/translations/ko-KR/content/github/using-git/adding-a-remote.md index 0c1d9cdb1d605..7b5dd630955f0 100644 --- a/translations/ko-KR/content/github/using-git/adding-a-remote.md +++ b/translations/ko-KR/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ You may encounter these errors when trying to add a remote. This error means you've tried to add a remote with a name that already exists in your local repository: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/ko-KR/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/ko-KR/content/github/using-git/using-git-rebase-on-the-command-line.md index a6aa32ba7b999..abaf31556db62 100644 --- a/translations/ko-KR/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/ko-KR/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,6 +124,10 @@ As before, Git is showing the commit message for you to edit. You can change the Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes: ```shell +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes $ git push origin main --force ``` diff --git a/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 873337f03e417..d4abc47c21ea8 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ Your theme includes default layouts, includes, and stylesheets that will automat {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### 다음 단계 {% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." diff --git a/translations/ko-KR/content/github/working-with-github-support/about-github-support.md b/translations/ko-KR/content/github/working-with-github-support/about-github-support.md index c91e7c31732da..77bd872631c17 100644 --- a/translations/ko-KR/content/github/working-with-github-support/about-github-support.md +++ b/translations/ko-KR/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ To see if there are currently any incidents affecting services on {% data variab ### Contacting {% data variables.contact.github_support %} -{% data variables.product.prodname_free_user %} user and organization accounts can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. You can also contact {% data variables.contact.contact_support %} to report account, security, and abuse issues. +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -On paid accounts, you can either contact {% data variables.contact.contact_support %} and, depending on your plan, contact {% data variables.contact.premium_support %} or {% data variables.contact.contact_ent_support %}. For more information about contacting {% data variables.contact.premium_support %}, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud) or "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)." +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. ### Granting {% data variables.contact.github_support %} temporary access to a private repository diff --git a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index d779a6dd1b5ac..955f447af33aa 100644 --- a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -215,7 +215,7 @@ You can add emoji to your writing by typing `:EMOJICODE:`. Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result. -For a full list of available emoji and codes, check out [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). ### Paragraphs diff --git a/translations/ko-KR/content/github/writing-on-github/creating-gists.md b/translations/ko-KR/content/github/writing-on-github/creating-gists.md index d5655b46bb085..eaa67a64c2ef2 100644 --- a/translations/ko-KR/content/github/writing-on-github/creating-gists.md +++ b/translations/ko-KR/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- title: Creating gists -intro: 'You can create two kinds of gists: public and secret. Create a public gist if you''re ready to share your ideas with the world or a secret gist if you''re not.' +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,13 @@ versions: ### About gists -Every gist is a Git repository, which means that it can be forked and cloned. If you are signed in to {% data variables.product.product_name %} when you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. +Every gist is a Git repository, which means that it can be forked and cloned. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -Gists can be public or secret. Public gists show up in {% data variables.gists.discover_url %}, where people can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. {% data reusables.gist.cannot-convert-public-gists-to-secret %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. -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 %} Secret gists aren't private. If you send the URL of a secret gist to a friend, they'll be able to see it. However, if someone you don't know discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead. +Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead. + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -39,7 +41,7 @@ You can pin gists to your profile so other people can see them easily. For more {% endif %} -You can discover gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists). @@ -69,12 +71,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 4. Type the text of your gist into the gist text box. ![Gist text box](/assets/images/help/gist/gist_text_box.png) -5. Do one of the following: - - To create a public gist, click **Create public gist**. - - To create a secret gist, click **Create secret Gist**. ![Gist create button](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **Note:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/ko-KR/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/ko-KR/content/github/writing-on-github/forking-and-cloning-gists.md index 04f68e84c4225..0b7a42b681f3a 100644 --- a/translations/ko-KR/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/ko-KR/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Forking gists -Each gist indicates which forks have activity, making it easy to find interesting changes from coworkers or complete strangers. +Each gist indicates which forks have activity, making it easy to find interesting changes from others. ![Gist forks](/assets/images/help/gist/gist_forks.png) diff --git a/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md b/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md index 5ab7b8a8edb3e..c7b9821f28c22 100644 --- a/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ko-KR/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ Mutations are structured like this: 
        mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
        The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. diff --git a/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md index 61833f3204419..bed6d72c52982 100644 --- a/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." @@ -30,8 +30,6 @@ Before you can use the Docker registry on {% data variables.product.prodname_reg ### Authenticating to {% data variables.product.prodname_registry %} -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### Authenticating with a personal access token @@ -51,11 +49,25 @@ To keep your credentials secure, we recommend you save your personal access toke {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} {% raw %} ```shell $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. @@ -94,9 +106,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, {% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. @@ -105,9 +127,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. Publish the image to {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen #### Example publishing a Docker image -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. @@ -197,9 +246,19 @@ You can use the `docker pull` command to install a docker image from {% data var $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 5a16a9b1c8483..8f1c9b0076d04 100644 --- a/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -78,10 +78,35 @@ If your instance has subdomain isolation disabled: ### Publishing a package -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +2. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. + {% data reusables.package_registry.authenticate-step %} 2. Create a new project. ```shell @@ -118,6 +143,8 @@ You can publish a package to {% data variables.product.prodname_registry %} by a dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### Publishing multiple packages to the same repository To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. diff --git a/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md index fc4e09b87750e..c7835ae5e1951 100644 --- a/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -206,6 +206,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### 더 읽을거리 - "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md index 545d19db19190..de241d4749aa4 100644 --- a/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. diff --git a/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md b/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md index b66eb8628ac3b..6477a4f743110 100644 --- a/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,272 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{ ### Publishing a package using an action -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
        + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
        + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
        + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
        + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
        + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
        + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
        + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
        + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
        + +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Installing a package using an action You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. diff --git a/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md b/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md index e95c3765a2a98..f8f7a26955969 100644 --- a/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ You can integrate {% data variables.product.prodname_registry %} with {% data va {% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_registry %} also offers a {% data variables.product.prodname_container_registry %} designed to support the unique needs of container images. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% 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) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ For more information, see: ### Managing packages -You can a delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/ko-KR/content/rest/overview/api-previews.md b/translations/ko-KR/content/rest/overview/api-previews.md index 3fbdab9ba2c85..425760ccbe205 100644 --- a/translations/ko-KR/content/rest/overview/api-previews.md +++ b/translations/ko-KR/content/rest/overview/api-previews.md @@ -70,14 +70,6 @@ Manage [projects](/rest/reference/projects). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} -### User blocking - -Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. - -**Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - ### Repository topics View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md index 6f14bb96cf5d4..6dc2e0240c261 100644 --- a/translations/ko-KR/content/rest/overview/libraries.md +++ b/translations/ko-KR/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 9067d671ac01a..150978d28552f 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 @@ -30,7 +30,7 @@ For information about GitHub's GraphQL API, see the [v4 documentation](/graphql) sent and received as JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -124,7 +124,7 @@ Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated- Authenticating with invalid credentials will return `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -324,7 +324,7 @@ Note that [the Search API has custom rate limit rules](/rest/reference/search#ra The returned HTTP headers of any API request show your current rate limit status: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -422,7 +422,7 @@ User-Agent: Awesome-Octocat-App cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -449,7 +449,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -460,7 +460,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -471,7 +471,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -489,7 +489,7 @@ The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any Here's a sample request sent from a browser hitting `http://example.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval @@ -498,7 +498,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra This is what the CORS preflight request looks like: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With diff --git a/translations/ko-KR/content/rest/reference/code-scanning.md b/translations/ko-KR/content/rest/reference/code-scanning.md index 42f1f093fec7e..efd7f361f7cf1 100644 --- a/translations/ko-KR/content/rest/reference/code-scanning.md +++ b/translations/ko-KR/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Code scanning redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/ko-KR/data/glossaries/external.yml b/translations/ko-KR/data/glossaries/external.yml index 6ebca09a60d68..a7e0591036336 100644 --- a/translations/ko-KR/data/glossaries/external.yml +++ b/translations/ko-KR/data/glossaries/external.yml @@ -123,7 +123,7 @@ - term: 커밋 description: >- - 커밋 또는 "개정"은 파일(또는 파일 집합)에 대한 개별 변경입니다. 작업을 저장하기 위해 커밋을 할 때 Git은 고유 ID(일명 "SHA" 또는 "해시")를 만들어 누가, 언제 만들었는지와 함께 커밋된 특정 변경 사항을 기록할 수 있습니다. 커밋에는 일반적으로 변경된 내용에 대한 간략한 설명인 커밋 메시지가 포함되어 있습니다. + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. - term: 커밋 작성자 description: 커밋을 수행한 사용자입니다. @@ -137,7 +137,7 @@ - term: 커밋 메시지 description: >- - 커밋을 수반하고 커밋이 도입하는 변경 내용을 전달하는 짧고 설명적인 텍스트입니다. + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. - term: 비교 브랜치 description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - gist는 GitHub에서 편집, 복제 및 포크할 수 있는 공유 가능한 파일입니다. URL을 가진 모든 사람이 비밀 gist를 사용할 수 있지만, 사용자가 gist를 공개 또는 비밀로 만들 수 있습니다. + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- @@ -436,7 +436,7 @@ - term: 알림 description: >- - 설정에 따라 웹 또는 이메일로 제공되는 업데이트로 관심 있는 활동에 대한 정보를 제공합니다. + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. - term: OAuth 앱 description: >- diff --git a/translations/ko-KR/data/glossaries/internal.yml b/translations/ko-KR/data/glossaries/internal.yml index 20f7367ab96c1..5044398dc710b 100644 --- a/translations/ko-KR/data/glossaries/internal.yml +++ b/translations/ko-KR/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: 중앙 처리 장치 - term: 자격 증명 도우미 - description: Git 자격 증명을 저장하는 프로그램입니다. + description: A program that stores and fetches Git credentials. - term: 크리올 description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - What You See Is What You Get. 화면에 있는 텍스트를 의미하는 약어로, 렌더링될 때와 똑같이 보입니다. + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. - term: XenServer description: 가상화 플랫폼입니다. diff --git a/translations/ko-KR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/ko-KR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..f957e0b7bcffa --- /dev/null +++ b/translations/ko-KR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: Access to package version deletion + description: >- + This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Deployments + description: >- + This preview adds support for deployments mutations and new deployments features. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - More detailed information about a pull request's merge state. + description: >- + This preview adds support for accessing fields that provide more detailed information about a pull request's merge state. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Update multiple refs in a single operation. + description: This preview adds support for updating multiple refs in a single operation. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Project Event Details + description: >- + This preview adds project, project card, and project column details to project-related issue events. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Create content attachments + description: This preview adds support for creating content attachments. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Pinned Issues Preview + description: This preview adds support for pinned issues. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Labels Preview + description: >- + This preview adds support for adding, updating, creating and deleting labels. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Import Project + description: This preview adds support for importing projects. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Team Review Assignments Preview + description: >- + This preview adds support for updating the settings for team review assignment. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/ko-KR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..10f9989a1239f --- /dev/null +++ b/translations/ko-KR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +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.' + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + 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.' + 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.' + 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.' + 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 + owner: nplasterer diff --git a/translations/ko-KR/data/learning-tracks/actions.yml b/translations/ko-KR/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..678519414c344 --- /dev/null +++ b/translations/ko-KR/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Get started with {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'You can create self-hosted runners to run workflows in a highly customizable environment.' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/ko-KR/data/release-notes/2-22/0.yml b/translations/ko-KR/data/release-notes/2-22/0.yml index cb67278fcae8a..5231cfd2ae3b6 100644 --- a/translations/ko-KR/data/release-notes/2-22/0.yml +++ b/translations/ko-KR/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/3-0/0-rc.yml b/translations/ko-KR/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..4794284f4ac0a --- /dev/null +++ b/translations/ko-KR/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ko-KR/data/reusables/actions/enterprise-actions-permissions.md b/translations/ko-KR/data/reusables/actions/enterprise-actions-permissions.md index 72c38f66bcaed..e66c8787334c4 100644 --- a/translations/ko-KR/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/ko-KR/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. Under "Policies", select an option. ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/ko-KR/data/reusables/actions/enterprise-beta.md b/translations/ko-KR/data/reusables/actions/enterprise-beta.md index 5c456da70dfdc..b10237e2827ed 100644 --- a/translations/ko-KR/data/reusables/actions/enterprise-beta.md +++ b/translations/ko-KR/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md b/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..ee9ba1dca8396 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **Note:** {% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/ko-KR/data/reusables/actions/enterprise-enable-checkbox.md b/translations/ko-KR/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/ko-KR/data/reusables/actions/enterprise-http-proxy.md b/translations/ko-KR/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/ko-KR/data/reusables/actions/enterprise-limit-actions-use.md b/translations/ko-KR/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..e2f4ed9452634 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." diff --git a/translations/ko-KR/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/ko-KR/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..24c8caf7df137 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### 다음 단계 + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/ko-KR/data/reusables/actions/enterprise-s3-permission.md b/translations/ko-KR/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/ko-KR/data/reusables/actions/enterprise-s3-support-warning.md b/translations/ko-KR/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/enterprise-self-signed-cert.md b/translations/ko-KR/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/ko-KR/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/ko-KR/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/ko-KR/data/reusables/actions/workflow-template-overview.md b/translations/ko-KR/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..a08dedbf2a197 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. You can use workflow templates as a starting place to build your custom workflow or use them as-is. + +You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. diff --git a/translations/ko-KR/data/reusables/advanced-security/more-info-ghas.md b/translations/ko-KR/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..4a510456e92ed --- /dev/null +++ b/translations/ko-KR/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." +{% endif %} diff --git a/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/code-scanning/beta.md b/translations/ko-KR/data/reusables/code-scanning/beta.md index 3dfd7cae7dc0c..7d1b5dbc94798 100644 --- a/translations/ko-KR/data/reusables/code-scanning/beta.md +++ b/translations/ko-KR/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_code_scanning_capc %} is currently in beta and subject to change. For more information about taking part in the beta, [sign up here](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/ko-KR/data/reusables/code-scanning/not-available.md b/translations/ko-KR/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..6531f5e1d0875 --- /dev/null +++ b/translations/ko-KR/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." + +{% endnote %} +{% endif %} diff --git a/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md b/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md index b8d2b78cbceae..18554c0ce1388 100644 --- a/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. 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#allowing-dependabot-to-access-private-repositories)." +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. 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#allowing-dependabot-to-access-private-repositories)." -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/ko-KR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index f57ed274394cc..e9533a00f72ff 100644 --- a/translations/ko-KR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/ko-KR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Note:** User provisioning for enterprise accounts is currently in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). {% endnote %} diff --git a/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 1ef7257106f6b..1bdc5adca7700 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Minimum requirements](#minimum-requirements) -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [Storage](#storage) - [CPU and memory](#cpu-and-memory) @@ -7,10 +8,10 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- You must configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +- You must configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Maximum jobs per minute | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ We recommend a high-performance SSD with high input/output operations per second Your instance requires a persistent data disk separate from the root disk. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview)." -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable the beta of {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 2.22, you'll need to configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endif %} @@ -48,4 +49,4 @@ You can resize your instance's root disk by building a new instance or using an {% endwarning %} -You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md index 97997e7d4f3a8..a9ffb7473a5c3 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| +| Trial, demo, or 10 light users | 2
        or [**4**](#optional-features) | 16 GB
        or [**32 GB**](#optional-features) | 100 GB
        or [**150 GB**](#optional-features) | 200 GB | +| 10 to 3,000 | 4
        or [**8**](#optional-features) | 32 GB
        or [**48 GB**](#optional-features) | 250 GB
        or [**300 GB**](#optional-features) | 200 GB | +| 3,000 to 5000 | 8
        or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | 12
        or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | 16
        or [**20**](#optional-features) | 128 GB
        or [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | User licenses | vCPUs | Memory | Attached storage | Root storage | |:------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------:| | Trial, demo, or 10 light users | 2{% if currentVersion == "enterprise-server@2.22" %}
        or [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
        or [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
        or [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5,000 to 8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
        or [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8,000 to 10,000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
        or [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
        or [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise_management_console/actions.md b/translations/ko-KR/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..15dbf50384e3d --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Actions**. ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/ko-KR/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/ko-KR/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..a999a5edfc417 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..4b1379243ea91 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +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. You should time this change carefully, to minimize downtime. + +{% endwarning %} diff --git a/translations/ko-KR/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/ko-KR/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..2c4dec3daa201 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Click **Save changes**. ![Save changes button](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/gated-features/code-scanning.md b/translations/ko-KR/data/reusables/gated-features/code-scanning.md index 2bcd80c1d4af9..69e6abf27f4f7 100644 --- a/translations/ko-KR/data/reusables/gated-features/code-scanning.md +++ b/translations/ko-KR/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ko-KR/data/reusables/gated-features/environments.md b/translations/ko-KR/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/ko-KR/data/reusables/gated-features/environments.md +++ b/translations/ko-KR/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ko-KR/data/reusables/gated-features/protected-branches.md b/translations/ko-KR/data/reusables/gated-features/protected-branches.md index a9745fcec2b68..ffae769bab961 100644 --- a/translations/ko-KR/data/reusables/gated-features/protected-branches.md +++ b/translations/ko-KR/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 %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ko-KR/data/reusables/gated-features/secret-scanning.md b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md index bd279034eee82..7396ad8e24141 100644 --- a/translations/ko-KR/data/reusables/gated-features/secret-scanning.md +++ b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ko-KR/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/ko-KR/data/reusables/gist/cannot-convert-public-gists-to-secret.md index f34b2701d8a5d..535fa5cd9df20 100644 --- a/translations/ko-KR/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/ko-KR/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -After creating a gist, you cannot convert it from public to secret. +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..cd1cc8d5fec37 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/ko-KR/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..44708fbdf62c9 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. For more information, see "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)." +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. For more information, see "[Contexts](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)." + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/ko-KR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/ko-KR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index 7070f89368e2a..742712357e45c 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -To enable team synchronization for Azure AD, your Azure AD installation needs the following permissions: +To enable team synchronization for Azure AD, your Azure AD installation needs the following permissions. - Read all users’ full profiles - Sign in and read user profile - Read directory data diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm.md index 1735680d5e454..8f6a50e6a5028 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. To confirm team synchronization: +5. Confirm team synchronization. - If you have IdP access, click **Enable team synchronization**. You'll be redirected to your identity provider's SAML SSO page and asked to select your account and review the requested permissions. - If you don't have IdP access, copy the IdP redirect link and share it with your IdP administrator to continue enabling team synchronization. ![Enable team synchronization redirect button](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/ko-KR/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/ko-KR/data/reusables/large_files/can-include-lfs-objects-archives.md index d63ea5bb6d0a2..e9ee6e5220b96 100644 --- a/translations/ko-KR/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/ko-KR/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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} You can choose whether {% 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. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ko-KR/data/reusables/mobile/about-mobile.md b/translations/ko-KR/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/ko-KR/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/ko-KR/data/reusables/mobile/ghes-release-phase.md b/translations/ko-KR/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/ko-KR/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/mobile/push-notifications-on-ghes.md b/translations/ko-KR/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/ko-KR/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/organizations/can-require-ssh-cert.md b/translations/ko-KR/data/reusables/organizations/can-require-ssh-cert.md index 6da37763232e5..1ed5f3afb99ac 100644 --- a/translations/ko-KR/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/ko-KR/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -You can require that members use SSH certificates to access organization resources,, unless SSH is disabled in your repository. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/ko-KR/data/reusables/organizations/click-codespaces.md b/translations/ko-KR/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/ko-KR/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ko-KR/data/reusables/organizations/team-synchronization.md b/translations/ko-KR/data/reusables/organizations/team-synchronization.md index 870153231374a..121340e06b008 100644 --- a/translations/ko-KR/data/reusables/organizations/team-synchronization.md +++ b/translations/ko-KR/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -You can use team synchronization to automatically add and remove team members in an organization through an identity provider. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/ko-KR/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/ko-KR/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/ko-KR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/ko-KR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ko-KR/data/reusables/package_registry/packages-cluster-support.md b/translations/ko-KR/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/ko-KR/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/ko-KR/data/reusables/package_registry/packages-ghes-release-stage.md index 03d9b25f84162..04e4ffd9ea459 100644 --- a/translations/ko-KR/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/ko-KR/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your instance, use the [sign-up form](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/ko-KR/data/reusables/project-management/choose-visibility.md b/translations/ko-KR/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..d0d1877d65c92 --- /dev/null +++ b/translations/ko-KR/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. For more information, see "[Changing project board visibility](/github/managing-your-work-on-github/changing-project-board-visibility)." ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/ko-KR/data/reusables/project-management/project-board-visibility.md b/translations/ko-KR/data/reusables/project-management/project-board-visibility.md index eec92c411476d..c9091f06bf10e 100644 --- a/translations/ko-KR/data/reusables/project-management/project-board-visibility.md +++ b/translations/ko-KR/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. A public project board is visible to anyone with the project board's URL. +By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/ko-KR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/ko-KR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index 089efbf2bea5b..345f7941ee206 100644 --- a/translations/ko-KR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/ko-KR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -If status checks are required for a repository, the required status checks must pass before you can merge your branch into the protected branch. For more information, see "[About required status checks](/articles/about-required-status-checks)." +If status checks are required for a repository, the required status checks must pass before you can merge your branch into the protected branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." diff --git a/translations/ko-KR/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/ko-KR/data/reusables/pull_requests/required-reviews-for-prs-summary.md index ef0b0a397bd4d..3526e39a78da3 100644 --- a/translations/ko-KR/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/ko-KR/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -Repository administrators can require that all pull requests receive a specific number of approving reviews from people with *write* or *admin* permissions in the repository or from a designated code owner before they're merged into a protected branch. For more information, see "[About protected branches](/articles/about-protected-branches)." - -When required reviews are enabled, anyone with access to the repository can approve changes in a pull request. However, you won't be able to merge your pull request until the required number of reviewers with *write* or *admin* permissions in the repository approve your pull request's changes in their review. For more information about repository permission levels, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)." If review is required from a designated code owner and the pull request affects code that has a designated owner, approval from that owner is required. +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/ko-KR/data/reusables/repositories/branch-rules-example.md b/translations/ko-KR/data/reusables/repositories/branch-rules-example.md index b9cd9572f0235..ea81704455211 100644 --- a/translations/ko-KR/data/reusables/repositories/branch-rules-example.md +++ b/translations/ko-KR/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -You can create a branch rule in a repository for a specific branch, all branches, or any branch that matches a naming pattern specified with the fnmatch syntax. For example, to require any branch containing the word `release` to have at least two pull request reviews before merging, you can create a branch rule for `*release*`. +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/ko-KR/data/reusables/repositories/return-to-source-diff.md b/translations/ko-KR/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..c918830348fb3 --- /dev/null +++ b/translations/ko-KR/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/ko-KR/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/ko-KR/data/reusables/repositories/review-policy-overlapping-commits.md index d5fba7504a1a1..cfe413d8a0cef 100644 --- a/translations/ko-KR/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/ko-KR/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -After all required reviewers have approved a pull request, you won't be able to merge it if there are other open pull requests with pending or rejected reviews and those pull requests have a head branch pointing to the same commit. Someone with *write* or *admin* permissions will need to approve or dismiss the blocking review on the other pull requests before you can merge. +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/ko-KR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ko-KR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index b74d5905b1e47..ba73880189979 100644 --- a/translations/ko-KR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/ko-KR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/ko-KR/data/reusables/repositories/workflow-notifications.md b/translations/ko-KR/data/reusables/repositories/workflow-notifications.md index c353f20cf9834..e2d943102dcc6 100644 --- a/translations/ko-KR/data/reusables/repositories/workflow-notifications.md +++ b/translations/ko-KR/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + You can also see the status of workflow runs on a repository's Actions tab. For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." diff --git a/translations/ko-KR/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/ko-KR/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..e5be6752e0ef6 --- /dev/null +++ b/translations/ko-KR/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Enterprise owners can enable SAML SSO and centralized authentication through a SAML IdP across all organizations owned by an enterprise account. After you enable SAML SSO for your enterprise account, SAML SSO is enabled by default for all organizations owned by your enterprise account. All members will be required to authenticate using SAML SSO to gain access to the organizations where they are a member, and enterprise owners will be required to authenticate using SAML SSO when accessing an enterprise account. diff --git a/translations/ko-KR/data/reusables/saml/dotcom-saml-explanation.md b/translations/ko-KR/data/reusables/saml/dotcom-saml-explanation.md index ddf9ab0bd50dc..be784eeb4f31c 100644 --- a/translations/ko-KR/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/ko-KR/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML SSO gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/ko-KR/data/reusables/secret-scanning/about-secret-scanning.md b/translations/ko-KR/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/ko-KR/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/ko-KR/data/reusables/secret-scanning/beta.md b/translations/ko-KR/data/reusables/secret-scanning/beta.md index 3625bb7a3e260..82fdadded9388 100644 --- a/translations/ko-KR/data/reusables/secret-scanning/beta.md +++ b/translations/ko-KR/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/ko-KR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/ko-KR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..eb0329e7fe346 --- /dev/null +++ b/translations/ko-KR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/ko-KR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/ko-KR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index 9da98434c3759..74c33553abbc5 100644 --- a/translations/ko-KR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/ko-KR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note**: You can't disable some security and analysis features that are enabled by default for public repositories. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/sponsors/activity-tab.md b/translations/ko-KR/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..507a5a0351706 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/support/ghae-priorities.md b/translations/ko-KR/data/reusables/support/ghae-priorities.md index 960a13b3b3f25..1f8430b012aac 100644 --- a/translations/ko-KR/data/reusables/support/ghae-priorities.md +++ b/translations/ko-KR/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Priority | 설명 | 예시 | |:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

        _After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
        • Errors or outages that affect core Git or web application functionality for all users
        • Severe network or performance degradation for majority of users
        • Full or rapidly filling storage
        • Known security incidents or a breach of access
        | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
        • Performance degradation that reduces productivity for many users
        • Reduced redundancy concerns from failures or service degradation
        • Production-impacting bugs or errors
        • {% data variables.product.product_name %} configuraton security concerns
        | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
        • Performance degradation that reduces productivity for many users
        • Reduced redundancy concerns from failures or service degradation
        • Production-impacting bugs or errors
        • {% data variables.product.product_name %} configuration security concerns
        | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
        • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
        • Issues with user tools and data collection methods
        • 업그레이드
        • Bug reports, general security questions, or other feature related questions
          • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
          • Feature requests and product feedback
          • General questions on overall configuration or use of {% data variables.product.product_name %}
          • Notifying {% data variables.contact.github_support %} of any planned changes
          | diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md b/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml index 52909bb40bba1..62720ac52ee6a 100644 --- a/translations/ko-KR/data/ui.yml +++ b/translations/ko-KR/data/ui.yml @@ -4,7 +4,7 @@ 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.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' localization_complete: 문서에 대한 업데이트가 자주 게시되며, 이 페이지의 번역이 아직 진행 중일 수 있습니다. 최신 정보는영어 설명서를 방문하십시오. 이 페이지에서 번역에 문제가 있는 경우 알려주십시오. localization_in_progress: 안녕하세요! 이 페이지는 현재 개발 중이거나 아직 번역 중입니다. 정확한 최신 정보를 확인하려면 영어 설명서를 방문하십시오. early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,15 @@ product_landing: quick_start: Quickstart reference_guides: Reference guides overview: 개요 +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: more guides + guideTypes: + overview: 개요 + quick_start: Quickstart + tutorial: 튜토리얼 + how_to: How-to guide + reference: Reference diff --git a/translations/ko-KR/data/variables/action_code_examples.yml b/translations/ko-KR/data/variables/action_code_examples.yml index 6eee91014274e..a1a9e462d737e 100644 --- a/translations/ko-KR/data/variables/action_code_examples.yml +++ b/translations/ko-KR/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/ko-KR/data/variables/gists.yml b/translations/ko-KR/data/variables/gists.yml index 9d1fea10acf46..12c745fd3ceb3 100644 --- a/translations/ko-KR/data/variables/gists.yml +++ b/translations/ko-KR/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml index 80107ee7b50bd..ba1a19ad12e18 100644 --- a/translations/ko-KR/data/variables/product.yml +++ b/translations/ko-KR/data/variables/product.yml @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'GitHub 스폰서 매칭 펀드' #GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/ko-KR/data/variables/release_candidate.yml b/translations/ko-KR/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/ko-KR/data/variables/release_candidate.yml +++ b/translations/ko-KR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/pt-BR/content/actions/creating-actions/about-actions.md b/translations/pt-BR/content/actions/creating-actions/about-actions.md index 356198c401eef..0ae4b11b73dad 100644 --- a/translations/pt-BR/content/actions/creating-actions/about-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/about-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 87d5f9ffaf12d..112c0e6ff831c 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md index cb4e7011e4c5c..59a5e5d3ec6d8 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md index 14ba855124c84..e8d84aaf697ed 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index e1fd4d4e11bff..a92adf20ea3be 100644 --- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] Para fornecer os `args` definidos no arquivo de metadados da ação para um contêiner Dock que usa a forma _exec_ no `ENTRYPOINT`, recomendamos criar um script do shell denominado `entrypoint.sh` que você pode acessar a partir da instrução `ENTRYPOINT`: ##### Exemplo *arquivo Docker* -``` -# Imagem do contêiner que executa o seu código -DE debian:9.5-slim +``` +# Container image that runs your code +FROM debian:9.5-slim -# Cópias do seu arquivo de código do seu repositório de ação para o caminho do sistema do arquivo `/` do contêiner -CÓPIA entrypoint.sh /entrypoint.sh +# Copies your code file from your action repository to the filesystem path `/` of the container +COPY entrypoint.sh /entrypoint.sh -# Executa `entrypoint.sh` quando o contêiner Docker é inicializado +# Executes `entrypoint.sh` when the Docker container starts up ENTRYPOINT ["/entrypoint.sh"] ``` @@ -78,14 +79,14 @@ Ao usar o arquivo Docker acima, {% data variables.product.product_name %}, envia ``` sh #!/bin/sh -# `$*` expande os `args` fornecidos em um `array` individualmente -# ou separa os `args` em uma string separados por um espaço em branco. +# `$*` expands the `args` supplied in an `array` individually +# or splits `args` in a string separated by whitespace. sh -c "echo $*" ``` O seu código deve ser executável. Certifique-se de que o arquivo `entrypoint.sh`tenha permissões `de execução` antes de usá-lo em um fluxo de trabalho. Você pode modificar as permissões a partir do seu terminal usando este comando: ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` Quando o script do shell de um `ENTRYPOINT` não for executável, você receberá uma mensagem de erro semelhante à mensagem a seguir: diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index e35c2198e1b4e..b311f35db8354 100644 --- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -104,12 +105,12 @@ As **saídas** `opcionais` usam os mesmos parâmetros que `outputs.` {% raw %} ```yaml outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - id: random-number-generator run: echo "::set-output name=random-id::$(echo $RANDOM)" shell: bash @@ -213,7 +214,7 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin ```yaml runs: using: "composite" - steps: + steps: - run: ${{ github.action_path }}/test/script.sh shell: bash ``` @@ -224,7 +225,7 @@ Como alternativa, você pode usar `$GITHUB_ACTION_PATH`: ```yaml runs: using: "composite" - steps: + steps: - run: $GITHUB_ACTION_PATH/script.sh shell: bash ``` @@ -258,7 +259,7 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c #### Exemplos de uso do arquivo Docker no repositório ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -266,7 +267,7 @@ runs: #### Exemplo usando um contêiner de registro Docker público ```yaml -runs: +runs: using: 'docker' image: 'docker://debian:stretch-slim' ``` diff --git a/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index cdd85e3052c44..49abf8ef237a9 100644 --- a/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- Você deve aceitar os termos de serviço para publicar ações em {% data variables.product.prodname_marketplace %}. diff --git a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md index 450fe7d325cdb..01c0580ecea9a 100644 --- a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/about-continuous-integration.md b/translations/pt-BR/content/actions/guides/about-continuous-integration.md index 83014b908f12a..310fe14a71fba 100644 --- a/translations/pt-BR/content/actions/guides/about-continuous-integration.md +++ b/translations/pt-BR/content/actions/guides/about-continuous-integration.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md index 3919a65e7c497..ca286dd834725 100644 --- a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/about-service-containers.md b/translations/pt-BR/content/actions/guides/about-service-containers.md index d46a142665c88..8abe96e9bd860 100644 --- a/translations/pt-BR/content/actions/guides/about-service-containers.md +++ b/translations/pt-BR/content/actions/guides/about-service-containers.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} 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 53bf3338844b6..72fe60fc707e0 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 @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} 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 373f4ef7854fc..97c15212246f2 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 @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} 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 83ccbade3e339..95b58cab2585b 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 @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-net.md b/translations/pt-BR/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..857bf965d3a1a --- /dev/null +++ b/translations/pt-BR/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Criar e testar .NET +intro: Você pode criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto .NET. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introdução + +Este guia mostra como criar, testar e publicar um pacote no .NET. + +Os executores hospedados em {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado, que inclui o .NET Core SDK. Para uma lista completa de software atualizado e as versões pré-instaladas do .NET Core SDK, consulte [o software instalado nos executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners). + +### Pré-requisitos + +Você já deve estar familiarizado com a sintaxe YAML e como é usado com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." + +Recomendamos que você tenha um entendimento básico do .NET Core SDK. Para obter mais informações, consulte [Primeiros passos com o .NET](https://dotnet.microsoft.com/learn). + +### Começando com o modelo do fluxo de trabalho do .NET + +{% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do .NET que deve funcionar para a maioria dos projetos .NET e este guia inclui exemplos que mostram como personalizar este modelo. Para obter mais informações, consulte o [modelo do fluxo de trabalho do .NET](https://github.com/actions/setup-dotnet). + +Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Especificando uma versão do .NET + +Para usar uma versão pré-instalada do .NET Core SDK em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `setup-dotnet`. Esta ação encontra uma versão específica do .NET do cache de ferramentas em cada executor e adiciona os binários necessários para `PATH`. Estas alterações persistirão para o resto do trabalho. + +A ação `setup-dotnet` é a forma recomendada de usar .NET com {% data variables.product.prodname_actions %}, porque garante um comportamento consistente em executores diferentes e versões diferentes do .NET. Se você estiver usando um executor auto-hospedado, você deverá instalar o .NET e adicioná-lo ao `PATH`. Para obter mais informações, consulte a [`configuração-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Usar múltiplas versões do .NET + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Usar uma versão específica do .NET + +Você pode configurar o seu trabalho para usar uma versão específica do .NET, como `3.1.3`. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a versão mais recente do .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### Instalar dependências + +Os executores hospedados em {% data variables.product.prodname_dotcom %} têm o gerenciador do pacote NuGet instalado. Você pode usar o dotnet CLI para instalar dependências do registro do pacote NuGet antes de criar e testar seu código. Por exemplo, o YAML abaixo instala o pacote `Newtonsoft`. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Memorizar dependências + +Você pode armazenar em cache dependências do NuGet 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). Por exemplo, o YAML abaixo instala o pacote `Newtonsoft`. + +Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/guides/caching-dependencies-to-speed-up-workflows)". + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**Observação:** Dependendo do número de dependências, pode ser mais rápido para usar o armazenamento de dependências. Os projetos com muitas dependências grandes devem ver um aumento no desempenho conforme reduz o tempo necessário para fazer o download. Os projetos com menos dependências podem não ver um aumento significativo no desempenho e até mesmo ver um ligeiro diminuir devido à forma como o NuGet instala dependências armazenadas em cache. O desempenho varia de projeto para projeto. + +{% endnote %} + +{% endif %} + +### Criar e testar seu código + +Você pode usar os mesmos comandos usados localmente para criar e testar seu código. Este exemplo demonstra como usar a `dotnet build` e o `dotnet test` em um trabalho: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### Empacotar dados do fluxo de trabalho como artefatos + +Após a conclusão de um fluxo de trabalho, você poderá fazer o upload dos artefatos resultantes para análise. 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. O exemplo a seguir demonstra como você pode usar a ação `upload-artefato` para fazer o upload de resultados de testes. + +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)". + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### Publicar nos registros do pacote + +É possível configurar o seu fluxo de trabalho para publicar o pacote Dotnet em um pacote de registro quando o CI teste passa. Você pode usar segredos do repositório para armazenar quaisquer tokens ou credenciais necessárias para publicar seu binário. O exemplo a seguir cria e publica um pacote em {% data variables.product.prodname_registry %} usando `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% 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 16f59d7ca99c3..155d76b53badb 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 @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +37,11 @@ Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ A maneira mais fácil de especificar uma versão do Node.js é usar a ação `se A ação `setup-node` considera uma versão do Node.js como uma entrada e configura essa versão no executor. A ação `setup-node` localiza uma versão específica do Node.js da cache das ferramentas em casa executor e adiciona os binários necessários ao `PATH`, que persiste no resto do trabalho. Usar a ação `setup-node` é a forma recomendada de usar o Node.js com {% data variables.product.prodname_actions %}, pois garante um comportamento consistente nos diferentes executores e nas diferentes versões do Node.js. Se você estiver usando um executor auto-hospedado, você deverá instalar o Node.js e adicioná-lo ao `PATH`. -O modelo inclui uma estratégia de matriz que cria e testa o seu código com três versões do Node.js: 8.x, 10.x, e 12.x. O "x" é um caractere curinga que corresponde à última versão menor e à versão do patch disponível para uma versão. Cada versão do Node.js especificada na matriz `node-version` cria uma tarefa que executa as mesmas etapas. +O modelo inclui uma estratégia matriz que cria e testa seu código com quatro versões de Node.js: 10.x, 12.x, 14.x e 15.x. O "x" é um caractere curinga que corresponde à última versão menor e à versão do patch disponível para uma versão. Cada versão do Node.js especificada na matriz `node-version` cria uma tarefa que executa as mesmas etapas. Cada trabalho pode acessar o valor definido na matriz `node-version` usando o contexto `matriz`. A ação `setup-node` usa o contexto como entrada de `node-version`. A ação `setup-node` configura cada tarefa com uma versão diferente de Node.js antes de criar e testar o código. Para obter mais informações sobre os contextos e estratégias da matriz, consulte ""[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" e "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". @@ -77,7 +80,7 @@ Cada trabalho pode acessar o valor definido na matriz `node-version` usando o co ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} 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 f6d007864b9b3..13a1c1bb0f624 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 @@ -7,6 +7,7 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-python.md b/translations/pt-BR/content/actions/guides/building-and-testing-python.md index 737e265f7f7d7..09567d6ee3474 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-python.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md index 6c5e5d714653f..3caf3699d888e 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 89a0019428b90..046f307f628c8 100644 --- a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: 'tutorial' --- ### Sobre a memorização das dependências do fluxo de trabalho diff --git a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md index 4e9c9992990bc..cd9b89ae89a56 100644 --- a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md index 2889b501366e7..5dfa890c32e25 100644 --- a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/index.md b/translations/pt-BR/content/actions/guides/index.md index 26ee8a09354a7..3b3df1b640d5d 100644 --- a/translations/pt-BR/content/actions/guides/index.md +++ b/translations/pt-BR/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Criar fluxos de trabalho personalizados de integração contínua - -Você pode usar o {% data variables.product.prodname_actions %} para criar fluxos de trabalho personalizados de integração contínua (CI) que criam e testam projetos escritos em diferentes linguagens de programação. - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### Criar fluxos de trabalho personalizados de de implantação contínua - -Você pode usar {% data variables.product.prodname_actions %} para criar fluxos de trabalho personalizados de implantação contínua (CDD) que implementam projetos em vários ecossistemas parceiros em nuvem. - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### Publicar pacotes de software - -Você pode automatizar pacotes de software de publicação como parte do fluxo de trabalho de entrega contínua (CD). Os pacotes podem ser publicados em qualquer host de pacote e em {% data reusables.gated-features.packages %}. - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### Memorizando e armazenando os dados do fluxo de trabalho - -Memorize as dependências e armazene os artefatos para fazer com que o seu fluxo de trabalho seja executado de modo mais eficiente. - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### Usar contêineres de serviço em um fluxo de trabalho - -Conecte os serviços ao seu fluxo de trabalho usando contêineres de serviço. - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/pt-BR/content/actions/guides/publishing-docker-images.md b/translations/pt-BR/content/actions/guides/publishing-docker-images.md index f8445c5ffdfdd..d4ebfa73948c3 100644 --- a/translations/pt-BR/content/actions/guides/publishing-docker-images.md +++ b/translations/pt-BR/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -46,7 +47,7 @@ Neste guia, usaremos a ação `build-push-action` do Docker para criar a imagem No exemplo do fluxo de trabalho abaixo, usamos a ação `build-push-action` do Docker para criar a imagem e, se a construção for bem-sucedida, faça o push da imagem criada para o Docker Hub. -Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation. +Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. Para obter mais informações, consulte "[Fazer push de uma imagem de contêiner do Docker para o Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" na documentação do Docker. As opções `build-push-action` necessárias para o Docker Hub são: diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md index 724bc0bb81230..674e789539985 100644 --- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md index 4802e76abc777..a29d017411c5a 100644 --- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} 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 01b61818fd1ef..f89d16a2e54d6 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -87,9 +88,28 @@ always-auth=true Cada vez que você criar uma nova versão, você poderá acionar um fluxo de trabalho para publicar o seu pacote. O fluxo de trabalho no exemplo abaixo é executado sempre que ocorre o evento `versão` com o tipo `criado`. O fluxo de trabalho publica o pacote em {% data variables.product.prodname_registry %} se o teste de CI for aprovado. -Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo `nome` do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope) na documentação do npm. +#### Configurar o repositório de destino -Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. Por exemplo, um pacote denominado `@my-org/test` é publicado no `my-org/test` repositório de {% data variables.product.prodname_dotcom %}. + +No entanto, se você fornecer a chave `repositório`, o repositório nessa chave será usado como o registro de npm de destino para {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Efetuar a autenticação no repositório de destino + +Para efetuar a autenticação no registro de {% data variables.product.prodname_registry %} no seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN` do seu repositório. Ele é criado automaticamente e tem permissão de _leitura_ e _gravação_ para pacotes no repositório, em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)". + +Se você quiser publicar seu pacote em um repositório diferente, você deverá usar um token de acesso pessoal (PAT) que tenha permissão para escrever pacotes no repositório de destino. Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)". + +#### Exemplo de fluxo de trabalho Este exemplo armazena o segredo `GITHUB_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`. 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 631a3792dde6c..4cad6cca72e98 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% 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 d9c5358029cf7..fdc3cf0894db0 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 @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 859a4af749c92..08f7e6dd7a9a5 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index a39ca068a8b32..58c9548d99acf 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,11 +7,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +Você pode adicionar um executor auto-hospedado a {{ site.data.variables.product.prodname_actions }}. + +Se você é um administrador de empresa ou organização, talvez você queira adicionar seus executores auto-hospedados a nível da organização ou empresa. Esta abordagem torna o executor disponível para vários repositórios na sua organização ou empresa, e também permite gerenciar seus executores em um só lugar. + Para obter informações sobre sistemas operacionais compatíveis com executores auto-hospedados ou sobre como usar executores auto-hospedados com um servidor proxy, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% warning %} @@ -44,6 +49,8 @@ Você pode adicionar executores auto-hospedados no nível da organização, onde {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### Adicionar um executor auto-hospedado a uma empresa Você pode adicionar executores auto-hospedados a uma empresa, onde podem ser atribuídos a várias organizações. Os administradores da organização poderão então controlar quais repositórios podem usá-los. @@ -62,3 +69,13 @@ Para adicionar um executor auto-hospedado no nível de empresa de 1. Clique em **Adicionar novo** e depois clique em **Novo executor**. Novos runners são atribuídos ao grupo padrão. Você pode modificar o grupo do executor depois de registrar o runner (executor). Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Disponibilizar executores corporativos para repositórios + +Por padrão, os executores do grupo de executores "Padrão" de uma empresa estão disponíveis para todas as organizações da empresa, mas não estão disponíveis para todos os repositórios em cada organização. + +Para tornar um grupo de executores auto-hospedado de nível empresarial disponível para um repositório da organização, você pode precisar alterar as configurações herdadas da organização para o grupo de executores a fim de tornar o executor disponível para repositórios na organização. + +Para mais informações sobre como alterar as configurações de acesso de grupo de executor, consulte "[Gerenciar acesso a executores auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index 91bdf822e16fe..e1d212c1245ba 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index b0906aa35eb2b..b9147c848f41e 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index f5732142bf09f..a08e087168e7f 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 37e5b6671004c..b75f0794fd9df 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 5cdc1b414cdfd..134c183c8229b 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 806b02ed70a49..504b116cfece4 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,6 +4,7 @@ intro: Você pode usar etiquetas para organizar os seus executores auto-hospedad versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 5e191af624866..fd1a28aba5228 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md index 9488aa6f72028..84341e9610c3b 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,6 +5,7 @@ intro: '{% data variables.product.prodname_actions %} foram projetados para ajud versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} 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 75468b9522cb9..64a0e3d24b7e0 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 @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -76,7 +77,7 @@ etapas: #### Usar branches -Fazer referência a um branch específico significa que a ação sempre usará as atualizações mais recentes no branch de destino, mas pode criar problemas se essas atualizações incluírem alterações significativas. Este exemplo é direcionado a um branch denominado `@main`: +Especificar um branch de destino para a ação significa que ele sempre irá executar a versão atualmente nesse branch. Essa abordagem pode criar problemas se uma atualização do branch incluir mudanças significativas. Este exemplo é direcionado a um branch denominado `@main`: ```yaml steps: 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 c9305bee90d33..b92cf8d63718a 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 @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md index e2c8617945642..9e8b4915b758c 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -1,10 +1,11 @@ --- title: Gerenciar fluxos de trabalhos complexos shortTitle: Gerenciar fluxos de trabalhos complexos -intro: 'Este guia mostra como usar os recursos avançados de {% data variables.product.prodname_actions %}, com gestão de segredo, trabalhos dependentes, cache, matrizes de compilação{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ambientes,{% endif %} e etiquetas.' +intro: 'Este guia mostra como usar os recursos avançados de {% data variables.product.prodname_actions %}, com gestão de segredo, trabalhos dependentes, cache, matrizes de compilação{{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ambientes,{% endif %} e etiquetas.' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -154,6 +155,15 @@ Para obter mais informações, consulte ["Usar etiquetas com executores auto-ho Você pode configurar ambientes com regras de proteção e segredos. Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)". {% endif %} +### Usar um modelo do fluxo de trabalho + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. Caso o seu repositório tenha fluxos de trabalho existentes: No canto superior esquerdo, clique em **Novo fluxo de trabalho**. ![Criar um novo fluxo de trabalho](/assets/images/help/repository/actions-new-workflow.png) +1. Sob, nome do template que você gostaria de usar, clique em **Configurar este fluxo de trabalho**. ![Configurar este fluxo de trabalho](/assets/images/help/settings/actions-create-starter-workflow.png) + ### Próximas etapas Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Compartilhar fluxos de trabalho com a sua organização](/actions/learn-github-actions/sharing-workflows-with-your-organization)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 8a1c8107ae044..624f959e6b296 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -324,4 +325,3 @@ trabalhos: Você pode encontrar ações que podem ser usadas em seu fluxo de trabalho em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) ou você pode criar suas próprias ações. Para obter mais informações, consulte "[Criar ações](/actions/creating-actions)". - diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 2c935c122f68a..a24bf3bd0a70d 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index e608f5123c51c..2e7c8a489efa4 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,6 +4,7 @@ intro: '{% data variables.product.prodname_actions %} e GitLab CI/CD compartilha versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index b65744e7819ac..fab03b1da13cd 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -166,7 +167,7 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} needs: job1 job3: needs: [job1, job2] - + ``` 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 38f4f27efc27d..1a101001172a7 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 @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- ### Introdução 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 67c1c08365049..9506977915d13 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 @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} 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 75e45c99f4483..acb668557462a 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 @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -44,10 +45,10 @@ Este procedimento demonstra como criar um modelo de fluxo de trabalho e um arqui runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. Crie um arquivo de metadados dentro do diretório `workflow-templates`. O arquivo de metadados deve ter o mesmo nome do arquivo de fluxo de trabalho, mas em vez da extensão `.yml`, deve-se adicionar `.properties.json`. Por exemplo, este arquivo denominado `octo-organization-ci.properties.json` contém os metadados para um arquivo de fluxo de trabalho denominado `octo-organization-ci.yml`: ```yaml @@ -75,7 +76,7 @@ Para adicionar outro modelo de fluxo de trabalho, adicione seus arquivos ao mesm ![Arquivos do modelo do fluxo de trabalho](/assets/images/help/images/workflow-template-files.png) -### Usar um modelo do fluxo de trabalho +### Usar um modelo de fluxo de trabalho da sua organização Este procedimento demonstra como um membro da sua organização pode localizar e usar um modelo de fluxo de trabalho para criar um novo fluxo de trabalho. Os modelos de fluxo de trabalho de uma organização podem ser usados por qualquer pessoa que seja integrante da organização. diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index d762304a99fa1..a0e420946d4bc 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -66,9 +66,9 @@ Fazer commit do arquivo de fluxo de trabalho no repositório aciona o evento `pu {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### Mais fluxos de trabalho iniciais +### Mais modelos de fluxo de trabalho -O {% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados com os quais você pode começar para automatizar ou criar fluxos de trabalho de integração contínua. Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório de {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` e no repositório {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Próximas etapas @@ -120,7 +120,7 @@ Imprimir "Olá, mundo!" é uma ótima maneira de explorar a configuração e a s {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Na barra lateral esquerda, clique no fluxo de trabalho que você deseja executar. +1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja executar. ![Selecione o trabalho "say hello"](/assets/images/help/repository/say-hello-job.png) 1. À direita, clique no menu suspenso **Executar fluxo de trabalho** e clique em **Executar fluxo de trabalho**. Opcionalmente, você pode inserir uma mensagem personalizada na entrada "Pessoa a saudar" antes de executar o fluxo de trabalho. ![Acionar o fluxo de trabalho manual](/assets/images/help/repository/manual-workflow-trigger.png) @@ -129,15 +129,15 @@ Imprimir "Olá, mundo!" é uma ótima maneira de explorar a configuração e a s 1. Na barra lateral esquerda, clique no trabalho "say_hello". ![Lista de trabalhos do fluxo de trabalho](/assets/images/help/repository/workflow-job-listing.png) 1. Nos registros do fluxo de trabalho, expanda a seção 'Run echo "Hello World!"'. - ![Detalhe do fluxo de trabalho(/assets/images/help/repository/workflow-log-listing.png) + ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### Mais fluxos de trabalho iniciais +### More workflow templates -{% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados dos quais você pode partir para automatizar ou criar fluxos de trabalho de integração contínua. Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %} repositorio `actions/starter-workflows` em {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} -### Próximas etapas +### Next steps -O fluxo de trabalho hello-world que você acabou de adicionar é um exemplo simples de um fluxo de trabalho acionado manualmente. Esse é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}. O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos. O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}: +The hello-world workflow you just added is a simple example of a manually triggered workflow. Esse é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}. O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos. O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}: - "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para um tutorial detalhado - "[Guides](/actions/guides)" para casos específicos de usos e exemplos diff --git a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 654b6591e2fe2..b94ab7fc23fe1 100644 --- a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,6 +75,10 @@ Para usar a sintaxe de propriedade de desreferência, o nome da propriedade deve - começar com `a-Z` ou `_`; - ser seguido por `a-Z` `0-9` `-` ou `_`. +#### Determinar quando usar contextos + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### Contexto `github` O contexto `github` context contém informações sobre a execução do fluxo de trabalho e sobre o evento que a acionou. Você pode ler a maioria dos dados de contexto `github` em variáveis de ambiente. Para obter mais informações sobre as variáveis de ambiente, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". @@ -107,15 +111,14 @@ O contexto `github` context contém informações sobre a execução do fluxo de O contexto `env` contém variáveis de ambiente que foram definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações sobre como configurar variáveis de ambiente em seu fluxo de trabalho, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". -A sintaxe de contexto `env` permite que você use o valor de uma variável de ambiente no seu arquivo de fluxo de trabalho. Se você desejar usar o valor de uma variável de ambiente dentro de um executor, use o método normal do sistema operacional do executor para ler as variáveis de ambiente. +A sintaxe de contexto `env` permite que você use o valor de uma variável de ambiente no seu arquivo de fluxo de trabalho. Você pode usar o contexto `env` no valor de qualquer chave em uma **etapa**, exceto para as chaves `id` e `uses`. Para obter mais informações sobre a sintaxe da etapa, consulte "[Sintaxe do fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". -Você só pode usar o contexto `env` no valor de `com` e as chaves do `nome` ou em uma condição `se` da etapa. Para obter mais informações sobre a sintaxe da etapa, consulte "[Sintaxe do fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". +Se você desejar usar o valor de uma variável de ambiente dentro de um executor, use o método normal do sistema operacional do executor para ler as variáveis de ambiente. | Nome da propriedade | Tipo | Descrição | | ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------------- | | `env` | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. | -| `env.` | `string` | O valor de uma variável de ambiente específica. | - +| `env.` | `string` | O valor de uma variável de ambiente específica. | #### Contexto `trabalho` @@ -391,7 +394,7 @@ trabalhos `hashFiles(path)` -Retorna um único hash para o conjunto de arquivos que correspondem ao padrão do `caminho`. Você pode fornecer um único padrão de `caminho` ou vários padrões de `caminho` separados por vírgulas. O `caminho` é relativo ao diretório `GITHUB_WORKSPACE` e pode incluir apenas arquivos dentro do `GITHUB_WORKSPACE`. Essa função calcula um hash SHA-256 individual para cada arquivo correspondente e, em seguida, usa esses hashes para calcular um hash SHA-256 final para o conjunto de arquivos. Para obter mais informações sobre o SHA-256, consulte "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". +Retorna um único hash para o conjunto de arquivos que correspondem ao padrão do `caminho`. Você pode fornecer um único padrão de `caminho` ou vários padrões de `caminho` separados por vírgulas. O `caminho` é relativo ao diretório `GITHUB_WORKSPACE` e pode incluir apenas arquivos dentro do `GITHUB_WORKSPACE`. Essa função calcula uma hash SHA-256 individual para cada arquivo correspondente e, em seguida, usa esses hashes para calcular um hash SHA-256 final para o conjunto de arquivos. Para obter mais informações sobre o SHA-256, consulte "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". Você pode usar a correspondência de padrão de caracteres para corresponder os nomes dos arquivos. No Windows, a correspondência do padrão diferencia maiúsculas e minúsculas. Para obter mais informações sobre caracteres de correspondência de padrões suportados, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)". diff --git a/translations/pt-BR/content/actions/reference/environment-variables.md b/translations/pt-BR/content/actions/reference/environment-variables.md index e25c71a480ab3..268ac2862c7e6 100644 --- a/translations/pt-BR/content/actions/reference/environment-variables.md +++ b/translations/pt-BR/content/actions/reference/environment-variables.md @@ -57,6 +57,16 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr | `GITHUB_API_URL` | Retorna a URL da API. Por exemplo: `https://api.github.com`. | | `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `https://api.github.com/graphql`. | +{% tip %} + +**Observação:** Se você precisar usar o URL de um fluxo de trabalho em um trabalho, você poderá combinar estas variáveis de ambiente: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determinar quando usar variáveis de ambiente padrão ou contextos + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### Convenções de nomenclatura para variáveis de ambiente {% note %} 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 46241217e8c36..a614144e1d12f 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 @@ -80,6 +80,8 @@ Você pode usar estes operadores em qualquer um dos cinco campos: Você pode usar [crontab guru](https://crontab.guru/) para ajudar a gerar a sintaxe cron e confirmar a hora em que ela será executada. Para ajudar você a começar, há também uma lista de [exemplos de crontab guru](https://crontab.guru/examples.html). +As notificações de fluxos de trabalho agendados são enviadas ao usuário que modificou a sintaxe cron no arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Notificações para execuções do fluxo de trabalho](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)". + ### Eventos manuais Você pode acionar as execuções de fluxo de trabalho manualmente. Para acionar fluxos de trabalho específicos em um repositório, use o evento `workflow_dispatch`. Para acionar mais de um fluxo de trabalho em um repositório e criar eventos personalizados e tipos de eventos, use o evento `repository_dispatch`. @@ -593,7 +595,8 @@ Por padrão, um fluxo de trabalho só é executado quando o tipo de atividade de Por exemplo, você pode executar um fluxo de trabalho quando um pull request tiver sido `atribuído`, `aberto`, `sincronizado` ou `reaberto`. ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` 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 c20ede373b039..5d4c1fe7e98ec 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 @@ -83,44 +83,11 @@ Se houver uma ferramenta que você queira solicitar, abra um problema em [action {% endnote %} -Executores do Windows e Ubuntu são hospedados no Azure e têm os mesmos intervalos de endereços IP dos centros de dados Azure. Atualmente, todos os executores hospedados em {% data variables.product.prodname_dotcom %} do Windows e Ubuntu encontram-se nas seguintes regiões do Azure: - -- Leste dos EUA (`eastus`) -- Leste dos EUA 2 (`eastus2`) -- Oeste dos EU 2 (`westus2`) -- Centro dos EUA (`centralus`) -- Centro-sul dos EUA (`southcentralus`) - -A Microsoft atualiza os intervalos de endereços IP Azure semanalmente em um arquivo JSON que você pode baixar no site [Azure intervalos IP e tags de serviço - nuvem pública](https://www.microsoft.com/en-us/download/details.aspx?id=56519). Você pode usar esse intervalo de endereços IP se precisar de uma lista de permissão para evitar acesso não-autorizado em seus recursos internos. - -O arquivo JSON contém um array chamado `values` (valores). Dentro desse array, você pode encontrar os endereços IP suportados em um objeto com `name` e `id` da região Azure, por exemplo `"AzureCloud. astus2"`. - -Você pode encontrar os intervalos de endereços IP compatíveis no objeto `"addressPrefixes"`. Este é um exemplo resumido do arquivo JSON. - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Os executores do Windows e Ubuntu são hospedados no Azure e, consequentemente, têm as mesmas faixas de endereços IP que os centros de dados do Azure. Os executores do macOS estão hospedados na própria nuvem do macOS de {% data variables.product.prodname_dotcom %}. + +Para obter uma lista de intervalos de endereços IP que {% data variables.product.prodname_actions %} usa para executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá usar a API REST de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a chave de `ações` na resposta do ponto de extremidade "[Obtenha as metainformações do GitHub](/rest/reference/meta#get-github-meta-information)". Você pode usar essa lista de endereços IP se precisar de uma lista de permissão para evitar acesso não autorizado para os seus recursos internos. + +A lista de endereços IP de {% data variables.product.prodname_actions %} retornados pela API é atualizada uma vez por semana. ### Sistemas de arquivos 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 fd32c916748b4..0f97f1cc64994 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 @@ -305,11 +305,11 @@ steps: `echo "{path}" >> $GITHUB_PATH` -Prepends a directory to the system `PATH` variable and makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. +Prepara um diretório para a variável `PATH` do sistema e o torna disponível para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação. #### Exemplo -This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: +Este exemplo demonstra como adicionar o diretório `$HOME/.local/bin` ao `PATH`: ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH 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 7f993432080df..1ebfc4e8d585d 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 @@ -187,7 +187,7 @@ For more information about cron syntax, see "[Events that trigger workflows](/ac ### `env` -A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} @@ -646,7 +646,8 @@ You can override the default shell settings in the runner's operating system usi | All | `python` | Executes the python command. | `python {0}` | | Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | | Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | +| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | #### Example running a script using bash @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### Example running a python script ```yaml @@ -1149,7 +1159,7 @@ You can use special characters in path, branch, and tag filters. - `**`: Matches zero or more of any character. - `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`. - `+`: Matches one or more of the preceding character. -- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. +- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. - `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. @@ -1169,14 +1179,14 @@ For more information about branch, tag, and path filter syntax, see "[`on.-`feature/your-branch` | -| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`
          -`feature/your-branch`
          -`feature/mona/the/octocat` | -| -`main`
          -`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`
          -`releases/mona-the-octocat` | -| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`
          -`releases` | -| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`
          -`every/tag` | -| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`
          -`feature`
          -`ver-10-feature` | -| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`
          -`v2.0`
          -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`
          -`v2.0.0` | +| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | `feature/my-branch`

          `feature/your-branch` | +| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`

          `feature/your-branch`

          `feature/mona/the/octocat` | +| `main`

          `releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | `main`

          `releases/mona-the-octocat` | +| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`

          `releases` | +| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`

          `every/tag` | +| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`

          `feature`

          `ver-10-feature` | +| `v2*` | Matches branch and tag names that start with `v2`. | `v2`

          `v2.0`

          `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | `v1.10.1`

          `v2.0.0` | #### Patterns to match file paths @@ -1184,18 +1194,18 @@ Path patterns must match the whole path, and start from the repository's root. | Pattern | Description of matches | Example matches | |---------|------------------------|-----------------| -| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`
          -`server.rb` | -| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`
          -`page.jsx` | -| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` | -| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`
          -`index.js` -| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`
          -`js/index.js`
          -`src/js/app.js` | -| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`
          -`docs/file.txt` | -| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`
          -`docs/mona/octocat.txt` | -| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`
          -`docs/mona/hello-world.md`
          -`docs/a/markdown/file.md` -| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`
          -`dir/docs/my-file.txt`
          -`space/docs/plan/space.doc` -| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`
          -`js/README.md` -| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`
          -`my-src/code/js/app.js` -| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`
          -`path/their-post.md` | -| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`
          -`db/migrate-v1.0.sql`
          -`db/sept/migrate-v1.sql` | -| -`*.md`
          -`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`
          _Does not match_
          -`README.md`
          -`docs/hello.md` | -| -`*.md`
          -`!README.md`
          -`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`
          -`README.md`
          -`README.doc`| +| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`

          `server.rb` | +| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`

          `page.jsx` | +| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` | +| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`

          `index.js` +| `'**.js'` | Matches all `.js` files in the repository. | `index.js`

          `js/index.js`

          `src/js/app.js` | +| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`

          `docs/file.txt` | +| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`

          `docs/mona/octocat.txt` | +| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`

          `docs/mona/hello-world.md`

          `docs/a/markdown/file.md` +| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | `/docs/hello.md`

          `dir/docs/my-file.txt`

          `space/docs/plan/space.doc` +| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`

          `js/README.md` +| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`

          `my-src/code/js/app.js` +| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`

          `path/their-post.md` | +| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`

          `db/migrate-v1.0.sql`

          `db/sept/migrate-v1.sql` | +| `*.md`

          `!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`

          _Does not match_

          `README.md`

          `docs/hello.md` | +| `*.md`

          `!README.md`

          `README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`

          `README.md`

          `README.doc`| diff --git a/translations/pt-BR/content/admin/authentication/using-saml.md b/translations/pt-BR/content/admin/authentication/using-saml.md index 3304f0e0487c0..df1afc92da283 100644 --- a/translations/pt-BR/content/admin/authentication/using-saml.md +++ b/translations/pt-BR/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam prese ### Metadados SAML -Os metadados do provedor de serviços da sua instância do {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`. +Os metadados do seu provedor de serviço da instância de {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`. Para configurar seu provedor de identidade manualmente, a URL do serviço de consumidor de declaração (ACS, Assertion Consumer Service) é `http(s)://[hostname]/saml/consume` e usa a associação `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. diff --git a/translations/pt-BR/content/admin/configuration/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/command-line-utilities.md index 3f33b5b25d66c..55e674915256e 100644 --- a/translations/pt-BR/content/admin/configuration/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/command-line-utilities.md @@ -468,18 +468,21 @@ ghe-webhook-logs ``` Para exibir todas as entregas de hook falhas do último dia: +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -Para exibir a carga útil total do hook, o resultado e quaisquer exceções para a entrega: +O formato da data deve ser `AAAA-MM-DD`, `AAAA-MM-DD HH:MM:SS`, ou `AAAA-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -Para exibir entregas globais do webhook: +Para exibir a carga útil total do hook, o resultado e quaisquer exceções para a entrega: ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### Clustering diff --git a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index 9c188cf99ff92..889718c4666e3 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ Quando houver um servidor proxy habilitado para a {% data variables.product.prod {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. Em **HTTP Proxy Server** (Servidor proxy HTTP), digite a URL do seu servidor proxy. ![Campo para digitar a URL do servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. Para excluir todos os hosts de um domínio que exige acesso ao proxy, você pode usar `.` como um prefixo curinga. Por exemplo: `octo-org.tentacle` ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md index c23d3ecceef99..1678921982973 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ Se houver sobreposição de tentativas de backup, o comando `ghe-backup` será i Em caso de interrupção prolongada ou evento catastrófico no site primário, é possível restaurar a {% data variables.product.product_location %} provisionando outro appliance do {% data variables.product.prodname_enterprise %} e executando uma restauração no host de backup. Antes de restaurar um appliance, você deve adicionar a chave SSH do host de backup ao appliance de destino do {% data variables.product.prodname_enterprise %} como chave SSH autorizada. +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Nota:** Se {% data variables.product.product_location %} tiver {% data variables.product.prodname_actions %} habilitado, você deverá primeiro configurar o provedor de armazenamento externo de {% data variables.product.prodname_actions %} no aplicativo de substituição antes de executar o comando `ghe-restore`. Para obter mais informações, consulte "[Backup e restauração de {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %} ativado](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + Para restaurar a {% data variables.product.product_location %} do instantâneo mais recente bem-sucedido, use o comando `ghe-restore`. Você verá um conteúdo semelhante a este: ```shell diff --git a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 732e2dde1a132..e0b46b7b9c4cd 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ Para os usuários do {% data variables.product.product_location %} conseguirem h {% data reusables.enterprise_site_admin_settings.management-console %} 1. Verificar se há uma **{% data variables.product.prodname_advanced_security %}** entrada na barra lateral esquerda. ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -Se você não puder ver **{% data variables.product.prodname_advanced_security %}** na barra lateral, isso significa que sua licença não inclui suporte para recursos do {% data variables.product.prodname_advanced_security %}, incluindo {% data variables.product.prodname_code_scanning %}. A licença do {% data variables.product.prodname_advanced_security %} dá a você e aos seus usuários acesso a recursos que ajudam a tornar seus repositórios e códigos mais seguros. +{% data reusables.enterprise_management_console.advanced-security-license %} ### Habilitar o {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ Se você não puder ver **{% data variables.product.prodname_advanced_security % #### Configurar um executor auto-hospedado -Se você estiver inscrito no beta de {% data variables.product.prodname_actions %}, {% data variables.product.prodname_ghe_server %} poderá executar {% data variables.product.prodname_code_scanning %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}. Primeiro, você precisa fornecer um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} em seu ambiente. É possível fornecer executores auto-hospedados no nível da conta do repositório, organização ou empresa. 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)". +{% data variables.product.prodname_ghe_server %} pode executar {% data variables.product.prodname_code_scanning %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}. Primeiro, você precisa fornecer um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} em seu ambiente. É possível fornecer executores auto-hospedados no nível da conta do repositório, organização ou empresa. 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)". Você deve garantir que o Git esteja na variável do PATH em qualquer executor auto-hospedados que você usar para executar ações de {% data variables.product.prodname_codeql %}. -#### Provisionar a ação -Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, a ação apropriada deve estar disponível localmente. Você pode disponibilizar a ação de três maneiras. +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisionar ações +Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, as ações apropriadas devem estar disponíveis localmente. Você pode disponibilizar as ações de três maneiras. -- **Recomendado** Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". +- **Recomendado**: Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". - Se você desejar usar o {% data variables.product.prodname_codeql_workflow %}, você pode sincronizar o repositório do {% data variables.product.prodname_dotcom_the_website %} ao {% data variables.product.prodname_ghe_server %}, usando a ferramenta de sincronização de Ação do {% data variables.product.prodname_codeql %} disponível em [https://github. om/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Você pode usar essa ferramenta independentemente se {% data variables.product.product_location %} ou seus executores de {% data variables.product.prodname_actions %} terem acesso à internet, contanto que você possa acessar {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} simultaneamente no seu computador. -- Você pode criar uma cópia local do repositório da ação no seu servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} com a ação. Por exemplo, se você desejar usar a ação {% data variables.product.prodname_codeql %}, você poderá criar um repositório na sua instância denominada `github/codeql-action` e, em seguida, clonar o [repositório](https://github.com/github/codeql-action) a partir do {% data variables.product.prodname_dotcom_the_website %} e, posteriormente, fazer push desse repositório no repositório da sua instância `github/codeql-action`. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões. - +- É possível criar uma cópia local do repositório de uma ação no servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} que contém a ação. Por exemplo, se você quiser usar as ações para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você poderá criar um repositório na sua instância denominado `github/codeql-action`. Em seguida, clone o [repositório](https://github.com/github/codeql-action) de {% data variables.product.prodname_dotcom_the_website %} depois faça push desse repositório no repositório `github/codeql-action` da instância. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões. ##### Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %} - 1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)". -2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". 3. A próxima etapa é configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 4. Adicione um executor auto-hospedado ao seu repositório, organização ou conta corporativa. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configurar {% data variables.product.prodname_codeql %} em um servidor sem acesso à internet +Se o servidor em que você está executando +{% data variables.product.prodname_ghe_server %} não estiver conectado à internet, e você deseja permitir que os usuários habilitem {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para seus repositórios, você deverá usar a ferramenta de sincronização de {% data variables.product.prodname_codeql %} para copiar as ações de {% data variables.product.prodname_codeql %} e consultar o pacote de {% data variables.product.prodname_dotcom_the_website %} para o seu servidor. A ferramenta e os detalhes de como usá-la estão disponíveis em [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -Depois de configurar um executor auto-hospedado, os usuários podem habilitar o {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. 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). +#### Habilitar a verificação de código para repositórios individuais +Depois que você configurar um executor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}e provisionar as ações,{% endif %} os usuários poderão habilitar {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. 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). ### Executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %} -Se sua organização não está participando da versão beta do {% data variables.product.prodname_actions %} ou se você não desejar usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}. +Se você não quiser usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}. O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que você pode adicionar ao seu sistema CI/CD de terceiros. A ferramenta executa a análise do {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Executar o {% 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)". ### Desabilitar {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..237c778c3e1b9 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configurar a varredura de segredo para o seu dispositivo +shortTitle: Configurar a varredura de segredo +intro: 'Você pode habilitar, configurar e desabilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### Sobre o {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)". + +### Pré-requisitos + +Para usar {% data variables.product.prodname_secret_scanning %} em {% data variables.product.product_location %} você precisa destes dois pré-requisitos. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- Você precisa de uma licença de {% data variables.product.prodname_advanced_security %}. + +#### Verificar suporte para o sinalizador SSSE3 nos seus vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 está habilitado para a maioria das CPUs modernas. Você pode verificar se o SSSE3 está habilitado para oa vCPUs disponíveis para sua instância de {% data variables.product.prodname_ghe_server %}. + +1. Conecte ao shell administrativo para sua instância de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +2. Insira o seguinte comando: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +Se ele retornar o valor `0`, significa que o sinalizador SSSE3 está disponível e habilitado. Agora você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar a varredura de segredo](#enabling-secret-scanning)" abaixo. + +Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você precisa consultar a documentação do hardware/hipervisor sobre como habilitar o sinalizador ou disponibilizá-lo para VMs convidados. + +#### Verificar se você tem uma licença de {% data variables.product.prodname_advanced_security %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Verificar se há uma **{% data variables.product.prodname_advanced_security %}** entrada na barra lateral esquerda. ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### Habilitar {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Em " +{% data variables.product.prodname_advanced_security %}," clique em **{% data variables.product.prodname_secret_scanning_caps %}**. +![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Desabilitar {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Em " +{% data variables.product.prodname_advanced_security %}", desmarque **{% data variables.product.prodname_secret_scanning_caps %}**. +![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md index 62464419a5bd6..8d4ae91ade8e3 100644 --- a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ O isolamento de subdomínios reduz os problemas de script entre sites e outras v Quando o isolamento do subdomínio está ativado, o {% data variables.product.prodname_ghe_server %} substitui vários caminhos pelos subdomínios. -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} Para usar o Docker com {% data variables.product.prodname_registry %}, você também deve habilitar o isolamento de subdomínio. Para obter mais informações, consulte "[Configurar Docker para uso com o {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)". {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Caminho sem isolamento de subdomínio | Caminho com isolamento de subdomínio | -| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker com {% data variables.product.prodname_registry %} não funcionará com o isolamento de subdomínio desabilitado. | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Caminho sem isolamento de subdomínio | Caminho com isolamento de subdomínio | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker com {% data variables.product.prodname_registry %} não funcionará com o isolamento do subdomínio desabilitado para o beta 2.22 de {% data variables.product.prodname_registry %}. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### Pré-requisitos diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md index fb4e38d0a3f6d..2aaa7dcfe33e5 100644 --- a/translations/pt-BR/content/admin/configuration/index.md +++ b/translations/pt-BR/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..7f34387f45185 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Gerenciamento do GitHub para dispositivos móveis para sua empresa +intro: Você pode decidir se usuários autenticados podem se conectar-se a {% data variables.product.product_location %} com {% data variables.product.prodname_mobile %}. +permissions: Os proprietários da empresa podem gerenciar {% data variables.product.prodname_mobile %} para uma empresa em {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### Sobre o {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} Para obter mais informações, consulte "[GitHub para celular](/github/getting-started-with-github/github-for-mobile)". + +Os membros da sua empresa podem usar {% data variables.product.prodname_mobile %} para triar, colaborar e gerenciar o trabalho em {% data variables.product.product_location %} em um dispositivo móvel. Por padrão, {% data variables.product.prodname_mobile %} está habilitado para {% data variables.product.product_location %}. Você pode permitir ou impedir que os membros corporativos usem {% data variables.product.prodname_mobile %} para efetuar a autenticação em {% data variables.product.product_location %} e acessar os dados da sua empresa. + +### Habilitar ou desabilitar {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. Na barra lateral esquerda, clique em **Celular**. !["Celular" na barra lateral esquerda para o console de gerenciamento de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md index b6fb46e24de33..4103eb9cfddf4 100644 --- a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md +++ b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ O {% data variables.product.prodname_ghe_server %} requer baixa latência entre O clustering fornece redundância, mas não foi feito para substituir uma configuração de alta disponibilidade. Para obter mais informações, consulte [Configuração de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A configuração de um failover primário/secundário é muito mais simples do que o clustering e funcionará perfeitamente para várias organizações. Para obter mais informações, consulte [Diferenças entre clustering e alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). +{% data reusables.package_registry.packages-cluster-support %} + ### Como faço para obter acesso ao clustering? O clustering foi feito para situações específicas de dimensionamento e não se aplica a todas as organizações. Se você está pensando em usar o clustering, converse com seu representante exclusivo ou {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/admin/enterprise-management/index.md b/translations/pt-BR/content/admin/enterprise-management/index.md index 8ad69b03391f1..54497054f07f2 100644 --- a/translations/pt-BR/content/admin/enterprise-management/index.md +++ b/translations/pt-BR/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md index 31ff8160ee7e6..b05ec2f3bf808 100644 --- a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Observação:** Se você tiver {% data variables.product.prodname_actions %} habilitado, você deverá desabilitar o antigo servidor de réplica ou atualizar sua configuração de {% data variables.product.prodname_actions %} para usar um armazenamento externo diferente. Para obter mais informações, consulte "[Alta disponibilidade para {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)". + + {% endnote %} + {% endif %} diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 710c056503b9e..7e52b13a56d6d 100644 --- a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ Para obter mais informações, consulte "[Utilitários de linha de comando](/ent #### Voltar a uma versão de recurso Para voltar a partir de uma versão de recurso, faça a restauração partindo de um instantâneo da VM para garantir o estado consistente das partições raiz e de dados. Para obter mais informações, consulte "[Obter um instantâneo](#taking-a-snapshot)". + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Leia mais + +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file 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 b1d5b8a546120..48471918043eb 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 @@ -59,7 +59,9 @@ Depois do envio da sua solicitação de suporte, podemos pedir que você compart - `configuration-logs/ghe-config.log`: logs de configuração do {% data variables.product.prodname_ghe_server %}; - `collectd/logs/collectd.log`: logs coletados; - `mail-logs/mail.log`: logs de entrega de e-mail por SMTP; +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`: erros de entrega por webhook. +{% endif %} Para obter mais informações, consulte "[Gerar logs de auditoria](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". diff --git a/translations/pt-BR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..b9a56c4e78542 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: Sobre como usar ações no GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} inclui a maioria das ações de autoria de {% data variables.product.prodname_dotcom %} e tem opções para permitir o acesso a outras ações de {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. + +{% data reusables.actions.enterprise-no-internet-actions %} + +### Ações oficiais agrupadas com {% data variables.product.prodname_ghe_server %} + +A maioria das ações oficiais de autoria de {% data variables.product.prodname_dotcom %} são automaticamente agrupadas com {% data variables.product.prodname_ghe_server %} e são capturadas em um momento a partir do {% data variables.product.prodname_marketplace %}. Quando sua instância do {% data variables.product.prodname_ghe_server %} é atualizada, as ações oficiais agrupadas também são atualizadas. + +As ações oficiais empacotadas incluem `ações/checkout`, `actions/upload-artefact`, `actions/download-artefact`, `actions/labeler`, e várias ações de `actions/setup-`, entre outras. Para ver todas as ações oficiais incluídas na instância da sua empresa, acesse a organização das `ações` na sua instância: https://HOSTNAME/actions. + +Cada ação é um repositório na organização de `ações`, e cada repositório de ação inclui as tags necessárias, branches e commit de SHAs que seus fluxos de trabalho podem usar para fazer referência à ação. + +{% note %} + +**Observação:** Ao usar ações de configuração (como `actions/setup-LANGUAGE`) em {% data variables.product.prodname_ghe_server %} com executores auto-hospedados, você pode precisar configurar o cache de ferramentas em executores que não possuem acesso à Internet. Para obter mais informações, consulte "[Configurar o cache da ferramenta em executores auto-hospedados sem acesso à internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". + +{% endnote %} + +### Configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} + +Se os usuários na instância corporativa precisarem de acesso a outras ações de {% data variables.product.prodname_dotcom_the_website %} ou {% data variables.product.prodname_marketplace %}, há algumas opções de configuração. + +A abordagem recomendada é habilitar o acesso automático para todas as ações a partir de {% data variables.product.prodname_dotcom_the_website %}. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} + +Como alternativa, se você quiser ter um controle mais rigoroso sobre quais as ações que são permitidas na sua empresa, você pode fazer o download e sincronizar manualmente as ações na instância da sua empresa usando a ferramenta de `actions-sync`. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..eea887e137cb4 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Configuração avançada e solução de problemas +intro: 'Configurar alta disponibilidade para {% data variables.product.prodname_actions %} e solução de problemas, {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..7e06b7bac2d13 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Fazer backup e restaurar o GitHub Enterprise Server com o GitHub Actions habilitado +shortTitle: Backup e restauração +intro: 'Os dados de {% data variables.product.prodname_actions %} no seu provedor de armazenamento externo não estão incluídos em backups regulares de {% data variables.product.prodname_ghe_server %} e precisam ser salvos separadamente.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +Se você usar {% data variables.product.prodname_enterprise_backup_utilities %} para fazer backup de {% data variables.product.product_location %}, é importante observar que os dados de {% data variables.product.prodname_actions %} armazenados no seu provedor de armazenamento externo não serão incluídos no backup. + +Esta é uma visão geral das etapas necessárias para restaurar {% data variables.product.product_location %} com {% data variables.product.prodname_actions %} para um novo dispositivo: + +1. Confirme se o dispositivo original está off-line. +1. Defina manualmente as configurações de rede no dispositivo de {% data variables.product.prodname_ghe_server %}. As configurações de rede são excluídas do instantâneo de backup e não são substituídas por `ghe-restore`. +1. Configurar o dispositivo de substituição para usar a mesma configuração de armazenamento externo de {% data variables.product.prodname_actions %} do dispositivo original. +1. Habilite {% data variables.product.prodname_actions %} no dispositivo de substituição. Isto conectará o dispositivo de substituição ao mesmo armazenamento externo para {% data variables.product.prodname_actions %}. +1. Depois que {% data variables.product.prodname_actions %} estiver configurado com o provedor de armazenamento externo, use o comando `ghe-restore` para restaurar o restante dos dados do backup. Para obter mais informações, consulte "[Restaurar um backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)". +1. Registre novamente seus executores auto-hospedados no dispositivo de substituição. Para obter mais informações, consulte [Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +Para obter mais informações sobre backup e restauração de {% data variables.product.prodname_ghe_server %}, consulte "[Configurar backups no seu dispositivo](/admin/configuration/configuring-backups-on-your-appliance)". diff --git a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index e03339a86163f..d4d579a362d6f 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} não podem usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -Para tornar todas as ações do {% data variables.product.prodname_dotcom_the_website %} disponíveis na instância empresarial, você pode conectar {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %} usando {% data variables.product.prodname_github_connect %}. Para outras formas de acessar as ações de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações de {% data variables.product.prodname_dotcom_the_website %} no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)". +Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_website %} disponíveis na sua instância corporativa, você pode usar {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}. Para conhecer outras formas de acessar ações a partir de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre ações em {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server). ### Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} @@ -23,3 +23,4 @@ Antes de permitir o acesso a todas as ações de {% data variables.product.prodn {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. Em "Servidor pode usar ações do GitHub.com em execuções de fluxos de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..d2dc28aed5ead --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Habilitar GitHub Actions para o GitHub Enterprise Server +intro: 'Aprenda como configurar o armazenamento e habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..f45c627ec9637 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Habilitar o GitHub Actions com armazenamento do Amazon S3 +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar o armazenamento Amazon S3 para armazenar artefatos gerados por execuções de fluxo de trabalho.' +permissions: 'Os administradores de site podem ativar o {% data variables.product.prodname_actions %} e definir as configurações empresariais.' +versions: + enterprise-server: '>=3.0' +--- + +### Pré-requisitos + +{% data reusables.actions.enterprise-s3-support-warning %} + +Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: + +* Crie seu bucket do Amazon S3 para armazenar artefatos gerados pelas execuções do fluxo de trabalho. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar {% data variables.product.prodname_actions %} com armazenamento do Amazon S3 + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Em "Artefato & Registro de Armazenamento", selecione **Amazon S3**, e insira as informações do seu grupo de armazenamento: + + * **URL de serviço do AWS**: A URL do serviço para seu bucket. Por exemplo, se o seu bucket S3 foi criado na região `us-west-2`, esse valor deverá ser `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **Balde S3 AWS**: O nome do seu bucket S3. + * **Chave de acesso do AWS S3** e **Chave de segredo do AWS S3**: A chave de acesso AWS e chave do segredo para o seu bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Botão de opção para selecionar o armazenamento do Amazon S3 e campos para configuração S3](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..8c582d9b8f252 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Habilitar o o GitHub Actions com armazenamento do Azure Blob +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: 'Os administradores de site podem ativar o {% data variables.product.prodname_actions %} e definir as configurações empresariais.' +versions: + enterprise-server: '>=3.0' +--- + +### Pré-requisitos + +Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: + +* Crie sua conta de armazenamento do Azure para armazenar artefatos de fluxo de trabalho. {% data variables.product.prodname_actions %} armazena seus dados como blobs de bloco, e dois tipos de conta de armazenamento são compatíveis: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + Para obter mais informações sobre os tipos de conta de armazenamento do Azure e níveis de desempenho, consulte a [Documentação do Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar {% data variables.product.prodname_actions %} com o armazenamento do Azure Blob + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Botão de opção para selecionar o armazenamento do Azure Blob e o campo de string de conexão](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..e5a7a940c8ac6 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar MinIO Gateway para armazenamento NAS para armazenar artefatos gerados por execuções de fluxo de trabalho.' +permissions: 'Os administradores de site podem ativar o {% data variables.product.prodname_actions %} e definir as configurações empresariais.' +versions: + enterprise-server: '>=3.0' +--- + +### Pré-requisitos + +{% data reusables.actions.enterprise-s3-support-warning %} + +Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: + +* Para evitar contenção de recursos no dispositivo, recomendamos que o MinIO seja hospedado separadamente de {% data variables.product.product_location %}. +* Crie seu bucket para armazenar artefatos de fluxo de trabalho. Para configurar seu bucket e chave de acesso, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Habilitar {% data variables.product.prodname_actions %} com MinIO Gateway para armazenamento NAS + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Em "Artefato & Registro de Armazenamento", selecione **Amazon S3**, e insira as informações do seu grupo de armazenamento: + + * **URL de serviço do AWS**: A URL para p serviço do seu MinIO. Por exemplo, `https://my-minio.example:9000`. + * **Balde S3 AWS**: O nome do seu bucket S3. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} 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 3123ee09862df..bc2216f32b136 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 @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### Sobre as permissões de {% data variables.product.prodname_actions %} para sua empresa diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..155ef3b7489e3 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server +intro: 'Saiba mais sobre como habilitar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} pela primeira vez.' +permissions: 'Os administradores de site podem ativar o {% data variables.product.prodname_actions %} e definir as configurações empresariais.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. Revise os requisitos de armazenamento externo abaixo e [inescreva-se para a versão beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}. Ele abrange os requisitos de hardware e software, apresenta as opções de armazenamento e descreve as políticas de gestão de segurança. + +### Revise as considerações de hardware + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### Requisitos de armazenamento externo + +Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob. + +O {% data variables.product.prodname_actions %} usa armazenamento do blob para armazenar artefatos gerados pelas execuções do fluxo de trabalho, como registros de fluxo de trabalho e artefatos de criação enviados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo. + +{% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento: + +* Armazenamento do Azure Blob +* Amazon S3 +* MinIO Gateway compatível com S3 para NAS + +{% note %} + +**Observação:** Estes são os únicos provedores de armazenamento com os quais {% data variables.product.company_short %} é compatível e podem fornecer ajuda. Outros provedores de armazenamento compatíveis com a API do S3 provavelmente não funcionarão devido a diferenças em relação à API do S3. [Entre em contato conosco](https://support.github.com/contact) para pedir suporte para provedores de armazenamento adicionais. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Permissões do Amazon S3 + +{% data reusables.actions.enterprise-s3-permission %} + +### Habilitar {% data variables.product.prodname_actions %} + +O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. [Inscreva-se para a versão beta](https://resources.github.com/beta-signup/). + +### Leia mais + +- "Considerações de hardware" para sua plataforma em "[Configurando uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento + +Siga um dos procedimentos abaixo para habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento escolhido: + +* [Habilitar o o GitHub Actions com armazenamento do Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Habilitar o GitHub Actions com armazenamento do Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres + +Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". + +### Adicionar executores auto-hospedados + +{% data reusables.actions.enterprise-github-hosted-runners %} + +Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores auto-hospedados. Você pode adicionar executores auto-hospedados nos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". + +### Gerenciar quais ações podem ser usadas na sua empresa + +Você pode controlar quais ações os usuários têm permissão para usar na sua empresa. Isso inclui a configuração de {% data variables.product.prodname_github_connect %} para acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %}, ou a sincronização manual das ações de {% data variables.product.prodname_dotcom_the_website %}. + +Para obter mais informações, consulte "[Sobre o uso de ações em {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)". + +### Fortalecimento geral de segurança para {% data variables.product.prodname_actions %} + +Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)". + +{% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..22aff2dabbd50 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: Alta disponibilidade para o GitHub Actions +intro: 'Há algumas considerações especiais para administrar {% data variables.product.prodname_actions %} em uma configuração de alta disponibilidade.' +versions: + enterprise-server: '>=3.0' +--- + +### Replicação ou redundância dos seus dados de {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-storage-ha-backups %} + +Recomendamos que você configure o seu {% data variables.product.prodname_actions %} armazenamento externo para usar redundância de dados ou replicação. Para obter mais informações, consulte a documentação do seu provedor de armazenamento: + +* [Documentação de redundância de armazenamento do Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Documentação de replicação do Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### Réplicas de alta disponibilidade + +#### Promover uma réplica + +Ao habilitar uma configuração de alta disponibilidade, todas as réplicas são configuradas automaticamente para usar a configuração de armazenamento externo de {% data variables.product.prodname_actions %}. Se você precisa iniciar uma falha para promover uma réplica, nenhuma alteração de configuração adicional será necessária para {% data variables.product.prodname_actions %}. + +Para obter mais informações, consulte "[Iniciar uma falha na réplica do seu dispositivo](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)". + +#### Remover réplica de alta disponibilidade + +Evitar deixar várias instâncias para serem gravadas no mesmo armazenamento externo de {% data variables.product.prodname_actions %}. Isso pode ocorrer ao usar o comando `ghe-repl-teardown` para parar e remover permanentemente uma réplica de habilitada por {% data variables.product.prodname_actions %}. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +Para evitar esse problema, recomendamos desativar o servidor de réplica ou atualizar a sua configuração de {% data variables.product.prodname_actions %} com um armazenamento externo diferente. diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md index aae61ee08a6db..b5230dc084d02 100644 --- a/translations/pt-BR/content/admin/github-actions/index.md +++ b/translations/pt-BR/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### Índice -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} 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 51abb54c9c251..0fc94d0c9422b 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 @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -Para tornar as ações específicas de {% data variables.product.prodname_dotcom_the_website %} disponíveis para uso em fluxos de trabalho, você pode usar a ferramenta de código aberto [`actions-sync`](https://github.com/actions/actions-sync) do {% data variables.product.company_short %} para sincronizar repositórios de ações de {% data variables.product.prodname_dotcom_the_website %} para a instância corporativa. Para outras formas de acessar as ações de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações de {% data variables.product.prodname_dotcom_the_website %} no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)". +A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +No entanto, se você quer ter um controle mais rigoroso sobre quais as ações permitidas na sua empresa, você pode seguir esse guia para usar a ferramenta de código aberto de {% data variables.product.company_short %}de [`actions-sync`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} com sua instância corporativa. ### Sobre a ferramenta `actions-sync` diff --git a/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..c972c4d6cd217 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Os administradores do site podem resolver problemas de {% data variables.product.prodname_actions %} e modificar configurações de {% data variables.product.prodname_ghe_server %}.' +versions: + enterprise-server: '>=3.0' +--- + +### Configurar executores auto-hospedados ao usar um certificado autoassinado por {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} Para obter mais informações, consulte "[Configurar TLS](/admin/configuration/configuring-tls)". + +#### Instalar o certificado na máquina do executor + +Para um executor auto-hospedado conectar-se a um {% data variables.product.prodname_ghe_server %} usando um certificado autoassinado, você deverá instalar o certificado na máquina do executor para que a conexão seja mais rígida. + +Para as etapas necessárias para instalar um certificado, consulte a documentação do sistema operacional do seu executor. + +#### Configurar o Node.JS para usar o certificado + +A maioria das ações são escritas em JavaScript e são executadas usando Node.js, que não usa o armazenamento de certificados do sistema operacional. Para o aplicativo runner auto-hospedado usar o certificado, você deve definir a variável de ambiente `NODE_EXTRA_CA_CERTS` na máquina do executor. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +Por exemplo: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. Para obter mais informações, consulte "[Removendo os executores auto-hospedados](/actions/hosting-your-own-runners/removing-self-hosted-runners)" e "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. Para obter mais informações, consulte "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..b315bb23f4318 --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Por exemplo: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Por exemplo: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md index d59a78075b89c..9e23ba6f2e5be 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ As instâncias primária e de réplica devem receber EIPs separados nas configur ### Leia mais -- [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md index 84cb9430dfd17..893156054b0d4 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ O {% data variables.product.prodname_ghe_server %} dá suporte a qualquer regiã {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### Leia mais - ### Leia mais - - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index d65028341502f..6bf5be953c23f 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ Para criar a instância do {% data variables.product.prodname_ghe_server %}, voc ### Leia mais -- [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index d56c5ad415f4b..bbaf1f38a9138 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index b6eca49787efa..a2ac14611a938 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ imagem de {% data variables.product.prodname_ghe_server %} que você baixou. Par ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 683cda227b27a..c9f14f3886cc4 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index f20dc92601c1e..551a8adef72f3 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md index e3de812be9535..efc25895f5145 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ Para fazer um teste completo em todo o appliance do {% data variables.product.pr 1. Faça backup da sua instância de produção usando o {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte a seção "Sobre o {% data variables.product.prodname_enterprise_backup_utilities %}" em "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)". 2. Configure uma nova instância para funcionar como ambiente de preparo. Você pode usar os mesmos guias para provisionar e instalar sua instância de preparo, assim como fez na instância de produção. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)". 3. Restaure o backup na sua instância de preparo. Para obter mais informações, consulte a seção "Restaurar backup" em "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)". + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Leia mais + +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 6d55813c0c11e..901052ae6fd71 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -18,11 +18,11 @@ Uma conta corporativa permite gerenciar várias organizações{% if enterpriseSe - Segurança {% if enterpriseServerVersions contains currentVersion %}(logon único, autenticação de dois fatores) - Compartilhamento de pacotes de solicitação e {% if enterpriseServerVersions contains currentVersion %}suporte {% endif %} com {% data variables.contact.enterprise_support %}{% endif %} -{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about the management of your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.product_name %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} Para obter mais informações sobre o gerenciamento da sua assinatura de {% data variables.product.prodname_ghe_cloud %}, consulte "[Visualizar a assinatura e o uso da sua conta corporativa](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)". {% endif %}Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.product_name %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". -For more information about the management of users, organizations, data, and policies for {% data variables.product.product_location %}, see "[Managing users, organizations, and repositories](/admin/user-management)" and "[Setting policies for your enterprise](/admin/policies)." +Para obter mais informações sobre o gerenciamento de usuários, organizações, dados e políticas para {% data variables.product.product_location %}, consulte "[Gerenciar usuários, organizações e repositórios](/admin/user-management)" e "[Definir políticas para a sua empresa](/admin/policies)." -For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +Para obter mais informações sobre o gerenciamento de contas corporativas usando a API do GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". {% if enterpriseServerVersions contains currentVersion %} diff --git a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..3cd0d506d3913 --- /dev/null +++ b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### Leia mais + +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) no repositório `github/roadmap` diff --git a/translations/pt-BR/content/admin/overview/index.md b/translations/pt-BR/content/admin/overview/index.md index 5e243d5ad1fa7..250f64afb745c 100644 --- a/translations/pt-BR/content/admin/overview/index.md +++ b/translations/pt-BR/content/admin/overview/index.md @@ -15,5 +15,6 @@ Para obter mais informações ou comprar o {% data variables.product.prodname_en {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..b0ed0877fb4c7 --- /dev/null +++ b/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configurar o suporte ao ecossistema de pacote para sua empresa +intro: 'Você pode configurar {% data variables.product.prodname_registry %} para a sua empresa habilitando ou desabilitando globalmente os ecossistemas de pacotes individuais na sua empresa, incluindo Docker, RubyGems, npm, Apache Maven, Gradle ou NuGet. Conheça outros requisitos de configuração para dar suporte aos ecossistemas de pacote específicos.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Habilitar ou desabilitar os ecossistemas de cada pacote + +Para evitar que novos pacotes sejam carregados, você pode definir um ecossistema que você previamente habilitou como **Read-Only**, ao mesmo tempo que permite que pacotes existentes sejam baixados. + +{% if currentVersion == "enterprise-server@2.22" %} +Para usar +{% data variables.product.prodname_registry %} com o Docker, você precisa ter o isolamento de subdomínio habilitado para sua instância. Para obter mais informações, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. Em "Alternância de ecossistema", para cada tipo de pacote, selecione **habilitado**, **somente leitura** ou **Desabilitado**. ![Alternância de ecossistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Conectar ao registro oficial do NPM + +Se você habilitou os pacotes do npm na sua empresa e deseja permitir acesso ao registro oficial do NPM, bem como ao registro npm do {% data variables.product.prodname_registry %}, você deverá executar uma configuração adicional. + +{% data variables.product.prodname_registry %} usa um proxy transparente para o tráfego de rede que se conecta ao registro NPM oficial em `registry.npmjs.com`. O proxy está habilitado por padrão e não pode ser desabilitado. + +Para permitir conexões de rede para o registro NPM, você precisa configurar as ACLs de rede que permitem que {% data variables.product.prodname_ghe_server %} envie tráfego de HTTPS para o `registry.npmjs.com` por meio da porta 443: + +| Fonte | Destino | Porta | Tipo | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Observe que as conexões com `registry.npmjs.com` atravessam a rede Cloudflare e, consequentemente, não se conectam a um único endereço IP estático; em vez disso, é feita uma conexão com um endereço IP dentro dos intervalos de CIDR listados aqui: https://www. loudflare.com/ips/. + +{% endif %} + +### Próximas etapas + +Como a próxima etapa, recomendamos que verifique se precisa atualizar ou carregar um certificado TLS para a URL do seu pacote de host. Para obter mais informações, consulte "[Primeiros passos com o GitHub Packages para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..8944f71044d11 --- /dev/null +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Avisos:** +- It is critical that you configure any restrictive access policies you need 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 to 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. +- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. +- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. + +{% endwarning %} + +### Pré-requisitos + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Em "URL de serviço do AWS", digite a URL do ponto de extremidade S3 para a região do seu bucket. ![Campo da URL do Serviço do AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Em "Bucket do AWS S3", digite o nome do bucket S3 que você deseja usar para armazenar artefatos do pacote. ![Campo de Bucket para AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Em "Chave de acesso do AWS S3", digite sua chave de acesso para o S3. ![Campo Chave de acesso do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Em "Chave secreta do AWS S3", digite sua chave secreta para S3. ![Campo Chave Secreta do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Em "Região do AWS S3", digite sua região para o S3. ![Campo Região do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Próximas etapas + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..99f0a51308fff --- /dev/null +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**Avisos:** +- It is critical that you set the restrictive access policies you need 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. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. +- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. +- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. + +{% endwarning %} + +### Pré-requisitos + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### Próximas etapas + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..43a52044966cf --- /dev/null +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Avisos:** +- It is critical that you set the restrictive access policies you need 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. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. +- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. +- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. + +{% endwarning %} +### Pré-requisitos +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![Campo da URL do Serviço do AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![Campo de Bucket para AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![Campo Chave de acesso do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![Campo Chave Secreta do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![Campo Região do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Próximas etapas + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..66ebd448bba49 --- /dev/null +++ b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_registry %} em {% data variables.product.prodname_ghe_server %} usa armazenamento externo de blob para armazenar seus pacotes. + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Certifique-se de que o host de cada pacote contém `https://`. + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. Para obter mais informações sobre as URLs de host do pacote, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obter mais informações sobre o upload de certificados TLS para {% data variables.product.product_name %}, consulte "[Configurar TLS](/enterprise/admin/configuration/configuring-tls)". diff --git a/translations/pt-BR/content/admin/packages/index.md b/translations/pt-BR/content/admin/packages/index.md index 2a5c94fda0d58..09289e3b934a0 100644 --- a/translations/pt-BR/content/admin/packages/index.md +++ b/translations/pt-BR/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..348cd102eae85 --- /dev/null +++ b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você deverá preparar sua solução de armazenamento de terceiros. + +O MinIO oferece armazenamento de objetos com suporte para a API S3 e {% data variables.product.prodname_registry %} na sua empresa. + +Este início rápido mostra como configurar o MinIO usando o Docker para uso com {% data variables.product.prodname_registry %}. No entanto, você tem outras opções para gerenciar o MinIO além do Docker. Para obter mais informações sobre o MinIO, consulte a [Documentação oficial do MinIO](https://docs.min.io/). + +### 1. Escolha um modo MinIO para suas necessidades + +| Modo MinIO | Otimizado para | Infraestrutura de armazenamento necessária | +| ---------------------------------------------------- | --------------------------- | ----------------------------------------------------- | +| MinIO independente (em um único host) | Configuração rápida | N/A | +| MinIO como um gateway NAS | NAS (Armazenamento de rede) | Dispositivos NAS | +| MinIO agrupado (também denominado MinIO Distribuído) | Segurança de dados | Servidores de armazenamento em execução em um cluster | + +Para obter mais informações sobre suas opções, consulte [Documentação oficial do MinIO](https://docs.min.io/). + +### 2. Instalar, executar e efetuar o login no MinIO + +1. Configure suas variáveis de ambiente preferidas para o MinIO. + + Estes exemplos usam `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Instalar MinIO. + + ```shell + $ docker pull minio/minio + ``` + Para obter mais informações, consulte o "[Guia do início rápido do MinIO](https://docs.min.io/docs/minio-quickstart-guide)". + +3. Efetue o login no MinIO usando sua chave e segredo de acesso do MinIO. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + Você pode acessar suas chaves do MinIO usando as variáveis de ambiente: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Execute o MinIO no modo escolhido. + + * Execute o MinIO usando Docker em um único host: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + Para obter mais informações, consulte "[Guia de início rápido do Docker do MinIO](https://docs.min.io/docs/minio-docker-quickstart-guide.html)". + + * Executar o MinIO usando Docker como um gateway NAS: + + Esta configuração é útil para implantações em que já existe um NAS que você deseja usar como armazenamento de backup para {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + Para obter mais informações, consulte "[Gateway do MinIO para NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)". + + * Executar o MinIO usando Docker como um cluster. Esta implantação do MinIO usa vários hosts e a codificação de eliminação do MinIO para uma proteção de dados mais forte. Para executar o MinIO em um modo de cluster, consulte o "[Guia de início rápido do MinIO distribuído](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Crie o seu bucket do MinIO para {% data variables.product.prodname_registry %} + +1. Instalar o cliente do MinIO. + + ```shell + $ docker pull minio/mc + ``` + +2. Criar um bucket com uma URL de host que {% data variables.product.prodname_ghe_server %} pode acessar. + + * Exemplo de implantação local: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + Este exemplo pode ser usado para MinIO independente ou MinIO como um gateway NAS. + + * Exemplo de implantações agrupadas: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### Próximas etapas + +Para concluir a configuração de armazenamento para {% data variables.product.prodname_registry %}, você precisará copiar a URL de armazenamento do MinIO: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." 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 a0e8616d25fe8..0be360ee441e8 100644 --- a/translations/pt-BR/content/admin/user-management/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### Equipes -| Nome | Descrição | -| --------------:| --------------------------------------------------------------- | -| `team.create` | Um repositório ou conta de usuário foi adicionado a uma equipe. | -| `team.delete` | Um repositório ou conta de usuário foi removido de uma equipe. | -| `team.destroy` | Uma equipe foi excluída. | +| Nome | Descrição | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | Um repositório ou conta de usuário foi adicionado a uma equipe. | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### 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` | 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. | +| 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` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `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 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 c298b992da8d6..b55adb067a0b6 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 @@ -4,13 +4,18 @@ 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: '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 %}.' +intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -Você pode usar markdown para formatar sua mensagem. 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/)". +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ {% endnote %} +Você pode usar markdown para formatar sua mensagem. 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/)". + ### Criar mensagem personalizada de login {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Em "Sign in page" (Página de login), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Em **Sign in message** (Mensagem de login), digite a mensagem que você pretende exibir para os usuários. ![Mensagem de login](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Em **Sign in message** (Mensagem de login), digite a mensagem que você pretende exibir para os usuários. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. Revise a mensagem renderizada. ![Mensagem de login renderizada](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### Criar mensagem personalizada de logout @@ -37,12 +45,35 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Em "Sign out page" (Página de logout), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Em **Sign out message** (Mensagem de logout), digite a mensagem que você pretende exibir para os usuários. ![Mensagem de login two_factor_auth_header](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Em **Sign out message** (Mensagem de logout), digite a mensagem que você pretende exibir para os usuários. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. Revise a mensagem renderizada. ![Mensagem de logout renderizada](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Criar um banner de anúncio global @@ -50,9 +81,8 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ Você pode definir um banner de anúncio global para ser exibido para todos os usuários na parte superior de cada página. {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -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)". - +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. 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 %} Você também pode definir um banner de anúncio no shell administrativo usando um utilitário de linha de comando. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)". @@ -62,9 +92,8 @@ Você também pode definir um banner de anúncio no shell administrativo usando {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. Em "Sign in page" (Página de login), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Em "Anúncio", no campo de texto, digite o anúncio que deseja exibir em um banner. ![Campo de texto para digitar o anúncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Opcionalmente, em "Vence em", use o menu suspenso do calendário e selecione uma data de validade. ![Menu suspenso do calendário para escolher data de vencimento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. Opcionalmente, para ver como ficará o banner, clique em **Pré-visualizar**. ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Menu suspenso do calendário para escolher data de vencimento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md index a69a98cceafde..a82079004e2a8 100644 --- a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ Troque este `código` por um token de acesso: ##### Parâmetros -| Nome | Tipo | Descrição | -| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | -| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | -| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | -| `redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. | -| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | +| Nome | Tipo | Descrição | +| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. | +| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | +| `redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. | +| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | ##### Resposta @@ -213,7 +213,7 @@ Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de aces #### Limites de taxa para o fluxo do dispositivo -Quando um usuário envia o código de verificação no navegador, existe um limite de taxa máximo de 50 submissões em uma hora por aplicativo. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. Se você fizer mais de uma solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`) no período mínimo necessário entre solicitações (ou `intervalo`), você atingirá o limite de taxa e receberá uma resposta de erro `slow_down`. A resposta de erro `slow_down`adiciona 5 segundos ao último `intervalo`. Para obter mais informações, consulte [Erros para o fluxo do dispositivo](#errors-for-the-device-flow). 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 b0c7342f1ec26..c9e800460890a 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 @@ -24,7 +24,7 @@ Um código de host do servidor de CI que executa testes de CI, como, por exemplo A [API de verificação](/rest/reference/checks) permite que você configure testes de CI executados automaticamente em cada commit de código em um repositório. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. -Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/rest/reference/repos#branches) pode impedir que as pessoas mesclem de pull requests prematuramente. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. +Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/rest/reference/repos#branches) pode impedir que as pessoas mesclem de pull requests prematuramente. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. O GitHub cria automaticamente eventos `check_suite` para novos códigos de commits em um repositório usando o fluxo-padrão, embora [Atualizar preferências do repositório para o conjunto de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites) esteja disponível se desejar. Veja como funciona o fluxo-padrão: 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 b88c9088c19b8..950c01d633494 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 @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Escopos disponíveis -| Nome | Descrição | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Nome | Descrição | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (inclui informações de perfil do usuário público, informações de repositório público e gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Concede acesso total a repositórios privados e públicos. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | -|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e privado. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código. | -|  `repo_deployment` | Concede acesso aos [status de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | -|  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados com uma estrela. | +| **`repo`** | Concede acesso total a repositórios privados e públicos. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | +|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e privado. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código. | +|  `repo_deployment` | Concede acesso aos [status de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | +|  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados com uma estrela. | |  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou serviços acesso a convites *sem* conceder acesso ao código. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | Concede:
          acesso de leitura e gravação para eventos de segurança na [ API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).
          acesso de leitura e gravação para eventos de segurança da [ API de {% data variables.product.prodname_secret_scanning %} ](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | Concede acesso de leitura e escrita a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Concede acesso de leitura, gravação e ping aos hooks do repositório em repositórios públicos e privados. O escopos do `repo` e `public_repo` concede acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório. | -|  `write:repo_hook` | Concede acesso de leitura, escrita e ping para os hooks em repositórios públicos ou privados. | -|  `read:repo_hook` | Concede acesso de leitura e ping para hooks em repositórios públicos ou privados. | -| **`admin:org`** | Gerencia totalmente a organização e suas equipes, projetos e associações. | -|  `write:org` | Acesso de leitura e gravação à associação da organização, aos projetos da organização e à associação da equipe. | -|  `read:org` | Acesso somente leitura à associação da organização, aos projetos da organização e à associação da equipe. | -| **`admin:public_key`** | Gerenciar totalmente as chaves públicas. | -|  `write:public_key` | Criar, listar e visualizar informações das chaves públicas. | -|  `read:public_key` | Listar e visualizar informações para as chaves públicas. | -| **`admin:org_hook`** | Concede acesso de leitura, gravação, ping e e exclusão de hooks da organização. **Observação:** Os tokens do OAuth só serão capazes de realizar essas ações nos hooks da organização que foram criados pelo aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário. | -| **`gist`** | Concede acesso de gravação aos gists. | -| **`notificações`** | Condece:
          * acesso de gravação a notificações de um usuário
          * acesso para marcar como leitura nos threads
          * acesso para inspecionar e não inspecionar um repositório e
          * acesso de leitura, gravação e exclusão às assinaturas dos threads. | -| **`usuário`** | Concede acesso de leitura/gravação apenas às informações do perfil. Observe que este escopo inclui `user:email` e `user:follow`. | -|  `read:user` | Concede acesso para ler as informações do perfil de um usuário. | -|  `usuário:email` | Concede acesso de leitura aos endereços de e-mail de um usuário. | -|  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | -| **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | -| **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | +|  `security_events` | Grants:
          read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
          read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
          This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% 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)". | +| **`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. | +| **`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 %} diff --git a/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index c5f6b30520666..27233dd4e23fd 100644 --- a/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Visualizar transações para a sua listagem -intro: 'A página de transações do {% data variables.product.prodname_marketplace %} permite que você faça o download e visualize todas as transações para a sua listagem do {% data variables.product.prodname_marketplace %}. Você pode visualizar as transações para o último dia (24 horas), semana, mês ou referente a todo o tempo em que sua {% data variables.product.prodname_github_app %} foi listado.' +intro: 'A página de transações do {% data variables.product.prodname_marketplace %} permite que você faça o download e visualize todas as transações para a sua listagem do {% data variables.product.prodname_marketplace %}. You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/pt-BR/content/developers/overview/viewing-deployment-history.md b/translations/pt-BR/content/developers/overview/viewing-deployment-history.md index 1d28c56aa52d4..60b4eb9aa7f36 100644 --- a/translations/pt-BR/content/developers/overview/viewing-deployment-history.md +++ b/translations/pt-BR/content/developers/overview/viewing-deployment-history.md @@ -9,7 +9,7 @@ versions: {% data reusables.actions.environments-beta %} -Você pode entregar implantações através de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_actions %} e ambientes ou com {% endif %}API REST e aplicativos de terceiros. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[{% data variables.product.prodname_actions %}](/actions) {% endif %}Para obter mais informações sobre implantações com a API REST, consulte "[Repositórios](/rest/reference/repos#deployments)". +Você pode entregar implantações através de % if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_actions %} e ambientes ou com {% endif %}API REST e aplicativos de terceiros. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[{% data variables.product.prodname_actions %}](/actions) {% endif %}Para obter mais informações sobre implantações com a API REST, consulte "[Repositórios](/rest/reference/repos#deployments)". Para visualizar implantações atuais e anteriores, clique em **Ambientes** na página inicial do repositório. ![Ambientes](/assets/images/environments-sidebar.png) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index 505b06b61c24c..e09104ada0250 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ Você pode arquivar uma sala de aula que você não usa mais em {% data variable {% data reusables.classroom.click-settings %} 1. À direita de "Excluir essa sala de aula", clique em **Excluir sala de aula**. ![Botão "Excluir repositório"](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **Leia os avisos**. -1. Para verificar se você está excluindo a sala de aula correta, digite o nome da sala de aula que você deseja excluir. ![Modal para excluir uma sala de aula com avisos e campo de texto para nome da sala de aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Para verificar se você está excluindo a sala de aula correta, digite o nome da sala de aula que você deseja excluir. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Clique em **Excluir sala de aula**. ![Botão "Excluir sala de aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) 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 50ca42cd02b22..69d502db69568 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 @@ -43,3 +43,7 @@ Se tiver habilitado atualizações de segurança, às vezes você verá atualiza {% data reusables.dependabot.supported-package-managers %} Se o seu repositório já usa uma integração para gerenciamento de dependências, você precisará desativar isso antes de habilitar o {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre integrações](/github/customizing-your-github-workflow/about-integrations)". + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". diff --git a/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md index 47147dae5757c..7652ef0657c82 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, consulte "[Exigindo um histórico de commit linear](/github/administering-a-repository/requiring-a-linear-commit-history)".{% endif %} +O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### Combinar por squash os commits de merge diff --git a/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md b/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md index 9f441bd405a4a..a7a826705fc60 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,141 @@ --- -title: Sobre branches protegidos -intro: 'Os branches protegidos garantem que colaboradores no seu repositório não possam fazer alterações irreversíveis nos branches. Habilitar branches protegidos também permite habilitar outros requisitos e verificações opcionais, como verificação de status obrigatória e revisões obrigatórias.' +title: About protected branches +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### Sobre branches protegidos +### About branch protection rules -{% data reusables.pull_requests.about-protected-branches %} Você pode optar por aplicar restrições sobre como um pull request é mesclado no seu repositório. +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -Os proprietários de repositório e as pessoas com permissões de administrador para um repositório podem impor determinados fluxos de trabalho ou requisitos, antes que um colaborador possa fazer merge em seu repositório criando regras de branch protegido. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -{% data reusables.repositories.branch-rules-example %} Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)." +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -### Priorização de regras de branches protegidos +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/articles/about-pull-requests)." + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/articles/dismissing-a-pull-request-review)." + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." + +Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. + +{% note %} + +**Note:** Any person or integration with write permissions to a repository can set the state of any status check in the repository. {% data variables.product.company_short %} does not verify that the author of a check is authorized to create a check with a certain name or modify an existing status. Before merging a pull request, you should verify that the author of each status, listed in the merge box, is expected. + +{% endnote %} + +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| Type of required status check | Setting | Merge requirements | Considerations | +| --- | --- | --- | --- | +| **Strict** | The **Require branches to be up-to-date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.| +| **Loose** | The **Require branches to be up-to-date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### Require signed commits + +When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)." + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +You can always push local commits to the branch if the commits are signed and verified. {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)." + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + +Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)." + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. + +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. + +#### Allow force pushes -Se um repositório tiver várias regras de branch protegido que afetem os mesmos branches, as regras que incluírem um nome de branch específico terão a prioridade mais alta. Se houver mais de uma regra de branch protegido que faça referência ao mesmo nome de branch específico, a regra de branch criada primeiro terá a prioridade mais alta. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. -As regras de branch protegido que mencionam um caractere especial, como `*`, `?` ou `]`, são aplicadas na ordem em que foram criadas, de modo que as regras mais antigas com esses caracteres têm uma prioridade mais alta. +Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -### Configurações de proteção de branch +{% 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. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -Ao criar uma regra de proteção de branch em um repositório, os colaboradores não podem fazer push forçado no branch protegido ou excluir o branch{% if currentVersion == "free-pro-team@latest" %} por padrão{% endif %}. Você pode habilitar outras configurações de proteção de branch. Para obter informações, consulte "[Definir a possibilidade de mesclagem de pull requests](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)". +If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} -### Leia mais +#### Allow deletions -- "[Sobre verificações de status obrigatórias](/articles/about-required-status-checks)" -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[Sobre a assinatura de commit obriagória](/articles/about-required-commit-signing)" +By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. 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 b43680a4f6f2f..9bfc0deb569c4 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 @@ -25,7 +25,7 @@ Você pode receber notificações quando novas versões são publicadas em um re 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)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Pessoas com permissões de administrador para um repositório podem escolher se {% data variables.large_files.product_name_long %} os objetos de ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " 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 4bd9474d0add9..96e2d372f0902 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + Se o seu projeto se comunicar com um serviço externo, você pode usar um token ou uma chave privada para autenticação. Tokens e chaves privadas são exemplos de segredos que um provedor de serviços pode publicar. Se você marcar um segredo em um repositório, qualquer pessoa que tenha acesso de leitura ao repositório pode usar o segredo para acessar o serviço externo com seus privilégios. Recomendamos que você armazene segredos em um local dedicado e seguro fora do repositório do seu projeto. +Service providers can partner with -Se alguém verificar um segredo de um parceiro {% data variables.product.company_short %} em um repositório público ou privado, {% data variables.product.prodname_secret_scanning %} pode detectar o segredo e ajudar você a mitigar o impacto do vazamento. +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} -Os provedores de serviço podem fazer parceria com o {% data variables.product.company_short %} para fornecer os respectivos formatos de segredo para verificação. Para obter mais informações, consulte "[Verificação de segredo](/partnerships/secret-scanning)". +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios públicos - {% data variables.product.prodname_secret_scanning_caps %} é automaticamente habilitado em repositórios públicos, em que faz a varredura de código para saber se há segredos, para verificar os formatos de segredos conhecidos. Quando uma correspondência do seu formato de segredo é encontrada em um repositório público, {% data variables.product.company_short %} não divulga publicamente as informações como um alerta, mas envia uma carga para um ponto de extremidade de HTTP da sua escolha. Para uma visão geral de como a varredura de segredo funciona em repositórios públicos, consulte "[Varredura de segredo](/developers/overview/secret-scanning)". - -Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório. +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório. -Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. +Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios privados +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} + +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} -Se você for um administrador de repositório ou um proprietário da organização, você poderá habilitar {% data variables.product.prodname_secret_scanning %} para repositórios privados que pertençam a organizações. Você pode habilitar {% data variables.product.prodname_secret_scanning %} para todos os seus repositórios ou para todos os novos repositórios da organização. {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados de contas de usuário. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." -Quando você faz push de commits em um repositório privado com o {% data variables.product.prodname_secret_scanning %} habilitado, o {% data variables.product.product_name %} verifica o conteúdo dos commits em busca de segredos. +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. -Quando o {% data variables.product.prodname_secret_scanning %} detecta um segredo em um repositório privado, o {% data variables.product.prodname_dotcom %} envia alertas. +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. - O {% data variables.product.prodname_dotcom %} envia um alerta de email para os administradores do repositório e proprietários da organização. - O {% data variables.product.prodname_dotcom %} exibe um alerta no repositório. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Os administradores do repositório e proprietários da organização podem conceder acesso a alertas de {% data variables.product.prodname_secret_scanning %} aos usuários e à equipe. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". -Para monitorar os resultados de {% data variables.product.prodname_secret_scanning %} nos seus repositórios privados ou na sua organização, você pode usar a API de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações sobre pontos de extremidade da API, consulte "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)". +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} -O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} @@ -128,4 +71,4 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p ### Leia mais - "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)" -- "[Manter a conta e os dados seguros](/github/authenticating-to-github/keeping-your-account-and-data-secure)" +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" 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 0033ab237c7d7..8709e919dbfba 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 @@ -3,6 +3,7 @@ title: Sobre proteger seu repositório intro: 'O {% data variables.product.product_name %} fornece uma série de maneiras que você pode ajudar a manter seu repositório protegido.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Configurar o seu repositório com segurança @@ -13,6 +14,7 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod {% data variables.product.prodname_dotcom %} tem um conjunto crescente de recursos de segurança que ajudam você a manter seu código protegido. Você pode encontrá-los na aba **Segurança** do seu repositório. +{% if currentVersion == "free-pro-team@latest" %} - **Política de segurança** Facilita para as pessoas relatar, de modo confidencial, vulnerabilidades de segurança que encontram no seu repositório. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)". @@ -24,18 +26,32 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod - **{% 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. 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)". + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **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. 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)". + {% endif %} - 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)". +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **Alertas de {% data variables.product.prodname_code_scanning_capc %}** Detectar automaticamente vulnerabilidades de segurança e erros de codificação em códigos novos ou modificados. São destacados os problemas potenciais, com informações detalhadas, o que permite que você corrija o código antes que seja mesclado no seu branch-padrão. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". - **Segredos detectados** +View any secrets that - Visualize todos os segredos que {% data variables.product.prodname_dotcom %} encontrou no seu código. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." + {% data variables.product.prodname_dotcom %} has found in your code. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." + {% endif %} ### Explorar dependências O gráfico de dependências de {% data variables.product.prodname_dotcom %} permite que você explore: diff --git a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md index d24a6f5205fe1..0cfdb435a4933 100644 --- a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ Você pode escolher o branch-padrão para um repositório. O branch-padrão é o {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..3e49ab0c8cc53 --- /dev/null +++ b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +Você pode usar um arquivo *secret_scanning.yml* para excluir diretórios do {% data variables.product.prodname_secret_scanning %}. Por exemplo, você pode excluir diretórios que contenham testes ou conteúdo gerado aleatoriamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. No campo do nome de arquivo, digite *.github/secret_scanning.yml*. . +4. Em **Editar o novo arquivo**, digite `paths-ignore:` seguido pelos paths que você deseja excluir do {% data variables.product.prodname_secret_scanning %}. + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + Você pode usar caracteres especiais, como `*` para filtrar paths. Para obter mais informações sobre padrões de filtro, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)". + + {% note %} + + **Notas:** + - Se houver mais de 1.000 entradas em `paths-ignore`, {% data variables.product.prodname_secret_scanning %} excluirá apenas os primeiros 1.000 diretórios das verificações. + - Se *secret_scanning.yml* for maior que 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo o arquivo. + + {% endnote %} + +Você também pode ignorar alertas individuais de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)." + +### Leia mais + +- "[Gerenciando configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/pt-BR/content/github/administering-a-repository/index.md b/translations/pt-BR/content/github/administering-a-repository/index.md index 5e42bcfd200c6..d98fe1b8e14a6 100644 --- a/translations/pt-BR/content/github/administering-a-repository/index.md +++ b/translations/pt-BR/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..f366971fc7b86 --- /dev/null +++ b/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,115 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Pelo fato de o {% data variables.product.company_short %} usar o sinalizador `File::FNM_PATHNAME` para a sintaxe `File.fnmatch`, o curinga não corresponde aos separadores de diretório (`/`). Por exemplo, `qa/*` pode fazer correspondência com todos os branches que começam com `qa/` e contêm uma única barra. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. Para obter mais informações sobre opções de sintaxe para regras de branch, consulte a [documentação de fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). + +Se um repositório tiver várias regras de branch protegido que afetem os mesmos branches, as regras que incluírem um nome de branch específico terão a prioridade mais alta. Se houver mais de uma regra de branch protegido que faça referência ao mesmo nome de branch específico, a regra de branch criada primeiro terá a prioridade mais alta. + +As regras de branch protegido que mencionam um caractere especial, como `*`, `?` ou `]`, são aplicadas na ordem em que foram criadas, de modo que as regras mais antigas com esses caracteres têm uma prioridade mais alta. + +Para criar uma exceção a uma regra de branch existente, você pode criar outra regra de proteção de branch que tenha prioridade superior, como uma regra para um nome de branch específico. + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. Para obter mais informações, consulte " +Ignorar uma revisão de pull request". ![Caixa de seleção Restrict who can dismiss pull request reviews (Restringir quem pode ignorar revisões de pull request)](/assets/images/help/repository/PR-review-required-dismissals.png)

        + + 1. Optionally, enable required status checks. + - Selecione **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge). ![Opção Required status checks (Verificações de status obrigatórias)](/assets/images/help/repository/required-status-checks.png) + + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.png) + + - Na lista de verificações de status disponíveis, selecione as verificações que você deseja tornar obrigatórias.![Lista de verificações de status disponíveis](/assets/images/help/repository/required-statuses-list.png) + +1. Optionally, select **Require signed commits**. ![Opção Require signed commits (Exigir commits assinados)](/assets/images/help/repository/require-signed-commits.png) + +1. Optionally, select **Require linear history**. ![Opção de histórico linear necessária](/assets/images/help/repository/required-linear-history.png) + +1. Outra opção é selecionar **Include administrators** (Incluir administradores). ![Caixa de seleção Include administrators (Incluir administradores)](/assets/images/help/repository/include-admins-protected-branches.png) + +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + + - Select **Restrict who can push to matching branches**. ![Caixa de seleção Branch restriction (Restrição de branch)](/assets/images/help/repository/restrict-branch.png) + + - Procurar e selecionar pessoas, equipes ou aplicativos que tenham permissão para fazer push para o branch protegido. ![Pesquisa de restrição de branch](/assets/images/help/repository/restrict-branch-search.png) + +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.png) + +1. Optionally, select **Allow deletions**. ![Permitir a opção de exclusão de branch](/assets/images/help/repository/allow-branch-deletions.png) + +1. Clique em **Criar**. + + + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} + + + +{% data reusables.repositories.sidebar-settings %} + + + +{% data reusables.repositories.repository-branches %} + +1. To the right of the branch protection rule you want to edit, click **Edit**. ![Botão editar](/assets/images/help/repository/edit-branch-protection-rule.png) + +1. Make your desired changes to the branch protection rule. + +1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/help/repository/save-branch-protection-rule.png) + + + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} + + + +{% data reusables.repositories.sidebar-settings %} + + + +{% data reusables.repositories.repository-branches %} + +1. To the right of the branch protection rule you want to delete, click **Delete**. ![Botão excluir](/assets/images/help/repository/delete-branch-protection-rule.png) 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 48918cac69db2..dc29c9f3a364b 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 @@ -4,6 +4,7 @@ intro: Você pode visualizar e fechar alertas de segredos verificados para seu r product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. Na barra lateral esquerda, clique em **Segredos detectados**. ![Aba "Segredos detectados" ](/assets/images/help/repository/sidebar-secrets.png) -4. Em "Escaneamento de segredos", clique no alerta que desejar visualizar. ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Opcionalmente, use o menu suspenso "Resolver" e clique em um motivo para resolver um alerta. ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. Em "Escaneamento de segredos", clique no alerta que desejar visualizar. + {% if currentVersion == "free-pro-team@latest" %} + ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### Protegendo segredos comprometidos Uma vez que um segredo tenha sido committed a um repositório, você deve considerar o segredo comprometido. O {% data variables.product.prodname_dotcom %} recomenda as seguintes ações para segredos comprometidos: - Para um token de acesso pessoal do {% data variables.product.prodname_dotcom %}, exclua o token comprometido, crie outro token e atualize os serviços que usam o token antigo. 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)". -- Para todos os outros segredos, primeiro, verifique se o segredo commited para {% data variables.product.prodname_dotcom %} é válido. Se sim, crie um novo segredo, atualize quaisquer serviços que utilizam o segredo antigo, e depois exclua o segredo antigo. +- Para todos os outros segredos, primeiro, verifique se o segredo commited para {% data variables.product.product_name %} é válido. Se sim, crie um novo segredo, atualize quaisquer serviços que utilizam o segredo antigo, e depois exclua o segredo antigo. 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 97346e253b313..11cf15a17ff63 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 @@ -5,7 +5,7 @@ intro: 'Você pode escolher se os objetos {% data variables.large_files.product_ permissions: 'Pessoas com permissões de administrador para um repositório podem gerenciar se os objetos {% data variables.large_files.product_name_short %} estão incluídos nos arquivos do repositório.' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ 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 currentVersion == "free-pro-team@latest" %} 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 %} diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md index 02118acafafd3..83e1edc9c06e6 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### Sobre o gerenciamento da versão diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 7e05aa25dafae..52867efb5022a 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### Habilitar ou desabilitar recursos de segurança e análise +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### Conceder acesso aos alertas de segurança @@ -35,7 +53,13 @@ Os proprietários e administradores da organização só podem conceder acesso p {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. + {% if currentVersion == "free-pro-team@latest" %} + ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. Clique em **Save changes** (Salvar alterações). ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### Remover o acesso aos alertas de segurança @@ -43,7 +67,14 @@ Os proprietários e administradores da organização só podem conceder acesso p {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}. ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) 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 4346db4ef80dc..7ea5208e39435 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 @@ -24,7 +24,8 @@ Recomendamos revisar as seguintes advertências antes de alterar a visibilidade * Se você alterar a visibilidade de um repositório interno para privado, {% data variables.product.prodname_dotcom %} removerá bifurcações que pertencem a qualquer usuário sem acesso ao repositório privado recente. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}A visibilidade de qualquer bifurcação também será alterada para privada.{% elsif currentVersion == "github-ae@latest" %}Se o repositório interno tiver alguma bifurcação, significa que a visibilidade das bifurcações já é privada.{% endif %} Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou a visibilidade é alterada?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * Se você estiver usando {% data variables.product.prodname_free_user %} para contas de usuário ou organizações, alguns recursos não estarão disponíveis no repositório depois de alterar a visibilidade para privada. {% data reusables.gated-features.more-info %}{% endif %} * Qualquer site de {% data variables.product.prodname_pages %} publicado terá a publicação cancelada automaticamente.{% if currentVersion == "free-pro-team@latest" %} Se você adicionou um domínio personalizado ao site de {% data variables.product.prodname_pages %} você deve remover ou atualizar seus registros de DNS antes de tornar o repositório privado para evitar o risco de tomada de um domínio. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. Para obter mais informações, consulte "[Sobre sobre arquivamento de conteúdo e dados em {% 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 %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * O 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 %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ Recomendamos revisar as seguintes advertências antes de alterar a visibilidade #### Tornar um repositório público * O {% data variables.product.product_name %} irá destacar bifurcações privadas e transformá-las em um repositório privado independente. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* Se você estiver convertendo seu repositório privado em um repositório público, como parte de um movimento para a criação de um projeto de código aberto, consulte os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis. Você também pode fazer um curso grátis sobre gerenciamento de projeto de código aberto com [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, consulte "[Exibir o perfil da comunidade](/articles/viewing-your-community-profile)."{% endif %} +* Se você estiver convertendo seu repositório privado em um repositório público, como parte de um movimento para a criação de um projeto de código aberto, consulte os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis. Você também pode fazer um curso grátis sobre gerenciamento de projeto de código aberto com [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..b18df7ad6412c --- /dev/null +++ b/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: Solução de problemas de verificações de status necessárias +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)". + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. Isso garante que o branch foi testado com o código mais recente do branch base. Se o branch estiver desatualizado, você precisará fazer merge do branch base no seu branch. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". + +{% note %} + +**Observação:** também é possível atualizar o seu branch com o branch base usando o rebase do Git. Para obter mais informações, consulte "[Rebase no Git](/github/using-git/about-git-rebase)". + +{% endnote %} + +Não será possível fazer push de alterações locais em um branch protegido enquanto todas as verificações de status obrigatórias não forem aprovadas. Sendo assim, você receberá uma mensagem de erro semelhante a esta. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. Isso pode ser feito sem verificações de status em execução no próprio commit de merge. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. If the test merge commit has a status, the test merge commit must pass. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md index fd4100bc43c33..92ef46ce931d3 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 @@ -19,11 +19,13 @@ Você pode assinar commits e tags localmente para que outras pessoas possam veri Se um commit ou uma tag tiver uma assinatura que não possa ser verificada, o {% data variables.product.product_name %} marcará o commit ou a tag como não verificado(a). -Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre a assinatura de commit obrigatória](/articles/about-required-commit-signing)". +Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits)". Você pode conferir o status de verificação de seus commits ou tags assinados no {% data variables.product.product_name %} e ver por que as assinaturas de commit podem não ter sido verificadas. Para obter mais informações, consulte "[Conferir o status de verificação da assinatura de commit ou tag](/articles/checking-your-commit-and-tag-signature-verification-status)". -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} usará automaticamente o GPG para assinar commits que você criar usando a interface web do {% data variables.product.product_name %}, exceto quando você faz combinação por squash e merge de um pull request do qual você não é o autor. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} ### Verificação da assinatura de commit 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 73c964f158370..099a4ff282efd 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 @@ -39,6 +39,7 @@ Os eventos listados no seu registro de segurança são acionados por suas açõe | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} | [`account_recovery_token`](#account_recovery_token-category-actions) | Contém todas as atividade relacionadas a [adicionar um token de recuperação](/articles/configuring-two-factor-authentication-recovery-methods). | | [`cobrança`](#billing-category-actions) | Contém todas as atividades relacionadas às suas informações de cobrança. | +| [`espaços de código`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contém todas as atividades relacionadas aos aplicativos listados no {% data variables.product.prodname_marketplace %}.{% endif %} | [`oauth_access`](#oauth_access-category-actions) | Contém todas as atividades relacionadas a [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) com as quais você se conectou.{% if currentVersion == "free-pro-team@latest" %} @@ -82,6 +83,12 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `change_billing_type` | Acionada quando você [altera o modo de pagamento](/articles/adding-or-editing-a-payment-method) do {% data variables.product.prodname_dotcom %}. | | `change_email` | Acionada quando você [altera o endereço de e-mail](/articles/changing-your-primary-email-address). | +#### `codespaces` category actions + +| Ação | Descrição | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### ações de categoria de `marketplace_agreement_signature` | Ação | Descrição | @@ -227,20 +234,20 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev #### ações de categoria `user` -| Ação | Descrição | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | Acionada quando você {% if currentVersion != "github-ae@latest" %}[adiciona um novo endereço de email](/articles/changing-your-primary-email-address){% else %}adiciona um novo endereço de email{% endif %}. | -| `create` | Acionada quando você cria uma nova conta de usuário.{% if currentVersion != "github-ae@latest" %} -| `change_password` | Acionada quando você altera a senha. | -| `forgot_password` | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %} -| `hide_private_contributions_count` | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | -| `login` | Acionada quando você faz login no {% data variables.product.product_location %}. | -| `failed_login` | Acionada quando você não consegue fazer login. | -| `remove_email` | Acionada quando você remove um endereço de e-mail. | -| `rename` | Acionada quando você renomeia a conta.{% if currentVersion == "free-pro-team@latest" %} -| `report_content` | Acionada quando você [denuncia um problema ou uma pull request, ou um comentário em um problema, uma pull request, ou commit](/articles/reporting-abuse-or-spam).{% endif %} -| `show_private_contributions_count` | Acionada quando você [divulga contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} -| `two_factor_requested` | Acionada quando {% data variables.product.product_name %} pede a você por [seu código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %} +| Ação | Descrição | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} +| `create` | Acionada quando você cria uma nova conta de usuário.{% if currentVersion != "github-ae@latest" %} +| `change_password` | Acionada quando você altera a senha. | +| `forgot_password` | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count` | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | +| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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 %} #### ações de categoria `user_status` @@ -249,4 +256,3 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `update` | Acionada quando você configura ou altera o status no perfil. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". | | `destroy` | Acionada quando você remove o status no perfil. | - diff --git a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index 1bccf1ef61880..b4b36e337d96f 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ Com as chaves SSH, se alguém conseguir acessar seu computador, terá acesso a t É possível alterar a frase secreta de uma chave privada sem gerar novamente o par de chaves. Basta digitar o seguinte comando: ```shell -$ ssh-keygen -p -# Start the SSH key creation process -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' -> Enter new passphrase (empty for no passphrase): [Digite a nova frase secreta] -> Enter same passphrase again: [Digite mais uma vez para garantir] +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' +> Enter new passphrase (empty for no passphrase): [Type new passphrase] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/pt-BR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/pt-BR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index 217c0a28d3cd4..8e590f86b79ab 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/pt-BR/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ Se o código de conduta que você deseja usar não estiver disponível nos model 3. No campo do nome de arquivo, digite o nome e a extensão do arquivo. ![Nome do arquivo do novo código de conduta](/assets/images/help/repository/new-code-of-conduct-file-name.png) - Para tornar seu código de conduta visível no diretório raiz do repositório, digite *CODE_OF_CONDUCT* no campo do nome do arquivo. - Para tornar seu código de conduta visível no diretório `docs` do repositório, digite *docs/CODE_OF_CONDUCT*. - - Para tornar seu código de conduta visível no diretório `.github` do repositório, digite *.github/CODE_OF_CONDUCT*. + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. 4. No novo arquivo, adicione seu código de conduta personalizado. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} 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 e4df9034b3629..89b14e6784da8 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 @@ -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. 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 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 protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% 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 solicitação de pull request que você criou a partir de um branch protegido, {% data variables.product.prodname_dotcom %} ajudará você a criar um branch alternativo para a solicitação de pull request, para que a resolução dos 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-pull-request-reviews.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index ee98e3cd533d4..56da5b441ea8a 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 @@ -44,9 +44,7 @@ Você pode exibir todas as revisões que uma pull request recebeu na linha do te ### Revisões obrigatórias -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -Para obter mais informações, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)". +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% tip %} @@ -57,6 +55,5 @@ Para obter mais informações, consulte "[Sobre revisões obrigatórias para pul ### Leia mais - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Habilitar revisões obrigatórias para pull requests](/articles/enabling-required-reviews-for-pull-requests)" - "[Exibir uma revisão de pull request](/articles/viewing-a-pull-request-review)" - "[Configurar diretrizes para os contribuidores do repositório](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index 38aaa27b45490..455f3c9108302 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -Para obter mais informações sobre revisões obrigatórias, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)". +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -Você pode comentar em uma pull request, aprovar as alterações ou solicitar melhorias antes da aprovação. Para obter mais informações, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" e "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". +Você pode comentar em uma pull request, aprovar as alterações ou solicitar melhorias antes da aprovação. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ Você pode comentar em uma pull request, aprovar as alterações ou solicitar me ### Leia mais -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Comentar em uma pull request](/articles/commenting-on-a-pull-request)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 32c04eecaf742..c9c7b9a713cb4 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ Só é possível fazer commits em branches da pull request que: - esteja aberta em um repositório em que você tem acesso push e que foi criada de uma bifurcação desse repositório - estão em uma bifurcação de propriedade do usuário - tiver permissão concedida pelo criador da pull request -- não tenha [restrições de branch](/articles/about-branch-restrictions) que impedirá você de fazer commit +- não tenha [restrições de branch](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) que impedirá você de fazer commit Somente o usuário que criou a pull request pode dar a você permissão para fazer push de commits na bifurcação de propriedade do usuário. Para obter mais informações, consulte "[Permitir alterações no branch de uma pull request criada de uma bifurcação](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)". diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index a81bb4db563e3..d8cfb23c6eecd 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Ignorar uma revisão de pull request -intro: 'Se o seu repositório [exige revisões](/articles/about-required-reviews-for-pull-requests), você pode ignorar revisões de pull request que já não sejam mais válidas ou que não tenham sido aprovadas pelo revisor.' +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ Isso altera o status da revisão para um comentário de revisão. Quando você i - "[Sobre revisões de solicitação pull](/articles/about-pull-request-reviews)" - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" +- "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index 332e399b36e6f..f1846410707dc 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### Seguir o fluxo GitHub 1. [Crie um branch](/articles/creating-and-deleting-branches-within-your-repository) do repositório. -2. [Crie](/articles/creating-new-files), [edite](/articles/editing-files), [renomeie](/articles/renaming-a-file), [mova](/articles/moving-a-file-to-a-new-location) ou [exclua](/articles/deleting-files) arquivos. +2. [Crie](/articles/creating-new-files), [edite](/articles/editing-files), [renomeie](/articles/renaming-a-file), [mova](/articles/moving-a-file-to-a-new-location) ou [exclua](/github/managing-files-in-a-repository/deleting-files-in-a-repository) arquivos. 3. [Envie uma pull request](/articles/creating-a-pull-request) de seu branch com as modificações propostas para iniciar uma discussão. 4. Faça as modificações necessárias em seu branch. Sua pull request atualizará automaticamente. 5. [Faça o merge da pull request](/articles/merging-a-pull-request) assim que o branch estiver pronto. 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 f6ec4ef7e35f8..b084c467366f4 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 @@ -12,7 +12,7 @@ versions: ### Sobre merges de pull request -Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. {% data reusables.pull_requests.about-protected-branches %} No entanto, pode haver restrições sobre quando você pode fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". +Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. Por padrão, qualquer pull request pode sofrer merge a qualquer momento, a menos que o branch head esteja em conflito com o branch base. However, there may be restrictions on when you can merge a pull request into a specific branch. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ddbc77cdfaf78..7b2f8fae7df0b 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ A revisão de dependências é compatível com as mesmas linguagens e os mesmos ![Menu de filtro de arquivos](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. À direita do cabeçalho para um manifesto ou arquivo de bloqueio, mostre a revisão de dependências clicando no botão de diff avançado. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ A revisão de dependências é compatível com as mesmas linguagens e os mesmos * A gravidade da vulnerabilidade. * A versão da dependência na qual a vulnerabilidade foi corrigida. Se você estiver revisando um pull request para alguém, você pode pedir ao contribuidor para atualizar a dependência para a versão corrigida ou para uma versão posterior. -1. Você pode retornar para a visualização original do arquivo clicando no botão de diff de fonte. - - ![Botão de diff de fonte](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 877349b5cdcdc..f4499a3266e4d 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,9 +36,11 @@ Se o pull request contiver alterações em dependências, você poderá usar a r {% data reusables.repositories.changed-files %} -1. À direita do cabeçalho para um manifesto ou arquivo de bloqueio, mostre a revisão de dependências clicando no botão de diff avançado. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### Marcar um arquivo como visualizado @@ -65,5 +67,5 @@ Quando terminar de revisar os arquivos que deseja incluir na pull request, envie ### Leia mais -- "[Sobre revisões obrigatórias para pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[Filtrar pull requests por status de revisão](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 61fc34b59c2f9..4885aba90b69d 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ A organização pode usar o e-mail `name@organization.com` como um ponto públic ### Criar commits com um selo `on-behalf-of` na linha de comando -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} 2. Na próxima linha da mensagem do commit, digite `on-behalf-of: @org ` e, em seguida, aspas de fechamento. 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 06b1572e0e7ce..8174acfbb090e 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 @@ -39,7 +39,17 @@ Você pode usar o {% data variables.product.prodname_desktop %} para criar um co {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Dica:** Se estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, certifique-se de que existam duas novas linhas entre o final da sua descrição de commit e o indicador `Co-authored-by:`. + + {% endtip %} 3. Na próxima linha da mensagem do commit, digite `Co-authored-by: name ` com informações específicas para cada coautor. Depois das informações do coautor, adicione aspas de fechamento. 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 fa35031901cf1..163aaade01f84 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 @@ -19,7 +19,7 @@ As pessoas que você escolhe como proprietários do código devem ter permissõe Solicita-se automaticamente que os proprietários do código revisem quando alguém abre um pull request que modifica o código que possuem. Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Para obter mais informações sobre pull requests em rascunho, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Se você converter um pull request em rascunho, as pessoas que já assinaram as notificações não terão suas assinaturas canceladas automaticamente. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". -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)". +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 "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". {% 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 %} 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 a1bb1230702b9..968bc7e8b089d 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 @@ -13,7 +13,7 @@ versions: ### Sobre READMEs -É possível adicionar um arquivo LEIAME a um repositório para comunicar informações importantes sobre o seu projeto. Um LEIAME, junto com uma licença de repositório{% if currentVersion == "free-pro-team@latest" %}, diretrizes de contribuição, e um código de conduta{% elsif enterpriseServerVersions contains currentVersion %} e diretrizes de contribuição{% endif %}, comunica as expectativas para o seu projeto e ajuda você a gerenciar contribuições. +É possível adicionar um arquivo README a um repositório para comunicar informações importantes sobre o seu projeto. Um README, junto com uma licença de repositório{% if currentVersion == "free-pro-team@latest" %}, diretrizes de contribuição, e um código de conduta{% elsif enterpriseServerVersions contains currentVersion %} e diretrizes de contribuição{% endif %}, comunica as expectativas para o seu projeto e ajuda você a gerenciar contribuições. Para obter mais informações sobre como fornecer diretrizes para o seu projeto, consulte {% if currentVersion == "free-pro-team@latest" %}"[Adicionar um código de conduta ao seu projeto](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)e {% endif %}"[Configurar o seu projeto para contribuições saudáveis](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)". @@ -42,7 +42,7 @@ Se você colocar o arquivo README na raiz do repositório, `docs`, ou no diretó ### 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 README diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index c28b4e307c250..d498f136d3a6b 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ Cada pessoa e organização podem ter repositórios ilimitados e convidar um nú {% endif %} Você pode usar repositórios para gerenciar seu trabalho e colaborar com outras pessoas. -- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. Para obter mais informações, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues)". -- {% data reusables.discussions.you-can-use-discussions %} +- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - É possível usar pull requests para propor alterações em um repositório. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". - Você pode usar quadros de projeto para organizar e priorizar seus problemas e pull requests. Para obter mais informações, consulte "[Sobre quadros de projeto](/github/managing-your-work-on-github/about-project-boards)". diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 40c6e4d0b9606..b62b8d4ac62fa 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ Quando você pesquisar uma família de licenças, os resultados incluirão todas ### Identificar uma licença -[A licenciada de código aberto Ruby gem ](https://github.com/benbalter/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[A licenciada de código aberto Ruby gem ](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja detectada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *LEIAME* do repositório. diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md index bd92c65f73511..41b97d171fd64 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ Todos os desenvolvedores podem criar um ou mais codespaces para qualquer reposit {% data reusables.codespaces.about-personalization %} Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/index.md b/translations/pt-BR/content/github/developing-online-with-codespaces/index.md index 9cef2e35f9c27..9bb126005cdf8 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/index.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..117a0bac282eb --- /dev/null +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Clique em **Add secret** (Adicionar segredo). + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Clique em **Save changes** (Salvar alterações). + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Leia o alerta e clique em **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index af356b836810c..a1e797a52af9f 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ Para obter mais informações, consulte [Personalizar](https://docs.microsoft.co {% endnote %} +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." ### Leia mais 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 c562deae1aabe..f53f4ba088069 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 @@ -20,7 +20,7 @@ Você pode usar {% data variables.product.prodname_code_scanning %} para encontr 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)". -{% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. Para mais informações sobre endpoints de API, consulte "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 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)." @@ -54,7 +54,7 @@ Você pode visualizar e contribuir para as consultas do {% data variables.produc ### Leia mais -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) - [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 50dcf8d90b579..381e699eeec53 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 @@ -234,7 +234,9 @@ No arquivo de workflow use o parâmetro `config-file` da ação `init` para espe config-file: ./.github/codeql/codeql-config.yml ``` -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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +As configurações no arquivo são escritas no formato YAML. #### Especificar consultas adicionais 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 39c41a2402d0b..f999e6f71ea73 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 @@ -40,13 +40,16 @@ Você decide como gerar alertas do {% data variables.product.prodname_code_scann 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. +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + ### Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} 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 %} - Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. + Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. The text of the entry is the title you gave your commit message. ![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) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 39018f0f9fd2d..364767b738cbb 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ Você pode usar {% data variables.product.prodname_codeql_runner %} para executa O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que executa a análise de {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao seu sistema de terceiros e, em seguida, chama o executor para analisar o código e fazer o upload dos resultados para o {% data variables.product.product_location %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**Notas:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, consulte "[{% data variables.product.product_name %} Termos e Condições](https://securitylab.github.com/tools/codeql/license) de do CLI de {% data variables.product.prodname_codeql %} " e "[{% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} ### Fazer o download do {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração ### Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de CI -Após concluído o download do {% data variables.product.prodname_codeql_runner %} e verificado que pode ser executado, você deve disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. É importante notar que cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %} deve ter o {% data variables.product.prodname_codeql_runner %}. Você pode configurar cada servidor para copiar o executor a partir de um local central interno ou você pode usar a API REST para obter o executor direto do GitHub, por exemplo: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux Além disso, cada servidor de CI também precisa: -- Um {% data variables.product.prodname_github_apps %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. Para repositórios privados, o token deve ter o escopo do `repositório`. Para público, o token precisa apenas dos escopos `public_repo` e `repo:security_events`. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". -- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém CLI de {% data variables.product.prodname_codeql %}, consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %}. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://help.semmle.com/codeql/codeql-cli.html)". +- Um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são: 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 ab553d6878ad4..d10a87bf69ccc 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 @@ -15,7 +15,7 @@ versions: 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. 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)". +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 branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ![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) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index e5e86c2b05d0a..d8878480d1830 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### O comando `init` leva muito tempo 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 0b9026a06ae7a..4653f3b5daea5 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Ocorreu uma falha durante a criação automática para uma linguagem compilada @@ -81,17 +82,6 @@ Para obter mais informações sobre a especificação de etapas de criação, co O recurso de {% data variables.product.prodname_codeql %} `autobuild` usa heurística para criar o código em um repositório. No entanto, às vezes, essa abordagem resulta em uma análise incompleta de um repositório. Por exemplo, quando uma compilação múltipla de `build.sh` existe em um único repositório, é possível que a análise não seja concluída, já que a etapa `autobuild` executará apenas um dos comandos. A solução é substituir a etapa `autobuild` pelas etapas de criação que criam todo o código-fonte que você deseja analisar. 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)". -### Error: "Erro do servidor" - -Se a execução de um fluxo de trabalho para {% data variables.product.prodname_code_scanning %} falhar devido a um erro no servidor, tente executar o fluxo de trabalho novamente. Se o problema persistir, entre em contato com {% data variables.contact.contact_support %}. - -### Erro: "Fora do disco" ou "Sem memória" -Em projetos muito grandes, - -{% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor. -{% if currentVersion == "free-pro-team@latest" %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema. -{% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %} - ### A criação demora muito tempo Se a sua criação com a análise de {% data variables.product.prodname_codeql %} demorar muito para ser executada, existem várias abordagens que você pode tentar para reduzir o tempo de criação. @@ -126,3 +116,54 @@ Se você estiver analisando o código escrito no Python, você poderá ver resul Nos executores hospedados no GitHub que usam o Linux, o {% data variables.product.prodname_codeql_workflow %} tenta instalar e analisar as dependências do Python, o que pode gerar mais resultados. Para desabilitar a instalação automática, adicione `setup-python-dependencies: false` à etapa "Inicializar CodeQL" do fluxo de trabalho. Para obter mais informações sobre a configuração da análise de dependências do Python, consulte "[Analisar as dependências do Python](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)". {% endif %} + +### Error: "Erro do servidor" + +Se a execução de um fluxo de trabalho para {% data variables.product.prodname_code_scanning %} falhar devido a um erro no servidor, tente executar o fluxo de trabalho novamente. Se o problema persistir, entre em contato com {% data variables.contact.contact_support %}. + +### Erro: "Fora do disco" ou "Sem memória" +Em projetos muito grandes, + +{% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor. +{% if currentVersion == "free-pro-team@latest" %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema. +{% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 23f0938c8e5ee..fba3fa7041469 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -27,6 +27,8 @@ Você pode fazer o upload dos resultados usando {% data variables.product.prodna - {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. Se você bloquear o upload automático, quando você estiver pronto para fazer o upload de resultados, você poderá usar o comando `upload` (para obter mais informações, 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)"). - Uma ferramenta que gera resultados como um artefato fora do seu repositório, você pode usar a API de {% data variables.product.prodname_code_scanning %} para fazer o upload do arquivo (para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF](/rest/reference/code-scanning#upload-a-sarif-file)"). +{% data reusables.code-scanning.not-available %} + ### Fazer o upload uma análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_actions %} Para fazer o upload de um arquivo SARIF de terceiros para {% data variables.product.prodname_dotcom %}, você precisará de um fluxo de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" e "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". diff --git a/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..d5628a36694b5 --- /dev/null +++ b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### Sobre o {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} 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 f8e64d3dc58e2..1396d8228d35a 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 @@ -1,15 +1,18 @@ --- title: GitHub para dispositivos móveis -intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.company_short %} do seu dispositivo móvel.' +intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.product_name %} do seu dispositivo móvel.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### Sobre o {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} está atualmente disponível para usuários {% data variables.product.prodname_dotcom_the_website %} como app Android e iOS. +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} oferece a você uma maneira de realizar trabalhos de alto impacto {% data variables.product.prodname_dotcom %} rapidamente e de qualquer lugar. O {% data variables.product.prodname_mobile %}é uma maneira segura e confiável de acessar seus dados {% data variables.product.prodname_dotcom %} através de um aplicativo cliente confiável e primordial. +{% data variables.product.prodname_mobile %} oferece a você uma maneira de realizar trabalhos de alto impacto {% data variables.product.product_name %} rapidamente e de qualquer lugar. O {% data variables.product.prodname_mobile %}é uma maneira segura e confiável de acessar seus dados {% data variables.product.product_name %} através de um aplicativo cliente confiável e primordial. Com o {% data variables.product.prodname_mobile %} você pode: - Gerenciar, fazer triagem e limpar notificações @@ -23,12 +26,38 @@ Para mais informações sobre notificações para {% data variables.product.prod Para instalar {% data variables.product.prodname_mobile %} para Android ou iOS, consulte [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### Pré-requisitos + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + ### Idiomas compatíveis com {% data variables.product.prodname_mobile %} {% data variables.product.prodname_mobile %} está disponível nos seguintes idiomas. +- English - Japanese - Português do Brasil +- Simplified Chinese - Spanish Se você configurar o idioma do seu dispositivo para um idioma compatível, {% data variables.product.prodname_mobile %} será o idioma-padrão. Você pode alterar o idioma para {% data variables.product.prodname_mobile %} no no menu **Configurações** de {% data variables.product.prodname_mobile %}. @@ -37,9 +66,9 @@ Se você configurar o idioma do seu dispositivo para um idioma compatível, {% d {% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, consulte [Universal Links](https://developer.apple.com/ios/universal-links/) no site de desenvolvedor da Apple -Para desabilitar os links universais, mantenha qualquer link {% data variables.product.prodname_dotcom %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.prodname_dotcom %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}. +Para desabilitar os links universais, mantenha qualquer link {% data variables.product.product_name %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.product_name %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}. -Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.prodname_dotcom %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. +Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. ### Compartilhando feedback diff --git a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md index 3735db6d8132a..becafddba7efd 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md +++ b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: GitHub's products +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ For more information about hosting your own instance of [{% data variables.produ - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} - [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations) -For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact [{% data variables.product.product_name %}'s Sales team](https://enterprise.github.com/contact). +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/github/getting-started-with-github/index.md b/translations/pt-BR/content/github/getting-started-with-github/index.md index 97e4f61fac87c..ac9638c73c1ef 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/index.md +++ b/translations/pt-BR/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} 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 f3f7cbdb3b693..2983f732dc685 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 @@ -33,7 +33,7 @@ Below is a list of some of the available keyboard shortcuts. |-----------|------------ |g c | Go to the **Code** tab |g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." -|g p | Go to the **Pull requests** tab. 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" %} +|g p | Go to the **Pull requests** tab. 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" %} |g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} |g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." |g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." @@ -159,6 +159,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ |command + space or control + space | In the workflow editor, get suggestions for your workflow file. +|g f | Go to the workflow file +|shift + t or T | Toggle timestamps in logs +|shift + f or F | Toggle fullscreen logs +|esc | Exit fullscreen logs {% endif %} diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..357a797e843e1 --- /dev/null +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". + +### Deleting a file + +1. Navegue até o arquivo no repositório que deseja excluir. +2. Na parte superior do arquivo, clique +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md index d7b9a300d9ae9..1bdba524cf490 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/pt-BR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index fdd2dc9d0d813..f0282746c68e1 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ Você pode criar um link para uma linha específica clicando no número da linha ### Pesquisar dados -Para encontrar um valor específico no conjunto de dados, comece a inserir o valor na barra de pesquisa logo acima do arquivo. As linhas serão filtradas automaticamente: +Para encontrar um valor específico no conjunto de dados, comece a inserir o valor na barra de pesquisa logo acima do arquivo. The rows will filter automatically: ![Pesquisa de valores](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index d2fdab32363a5..ec015036f935b 100644 --- a/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ Por exemplo: - Se você fizer push de um arquivo de 500 MB no {% data variables.large_files.product_name_short %}, serão usados 500 MB do armazenamento alocado e nada da largura de banda. Se você fizer uma alteração de 1 byte e fizer push do arquivo novamente, serão usados outros 500 MB do armazenamento e nada a largura de banda, totalizando 1 GB de uso total do armazenamento e zero de largura de banda para esses dois pushes. - Se você baixar um arquivo de 500 MB que é rastreado com o LFS, serão usados 500 MB da largura de banda alocada do proprietário do repositório. Se um colaborador fizer push de uma alteração no arquivo e você fizer pull da nova versão no repositório local, serão usados outros 500 MB de largura de banda, totalizando 1 GB de uso total da largura de banda para esses dois downloads. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Se {% data variables.large_files.product_name_long %} objetos de ({% data variables.large_files.product_name_short %}) estiverem incluídos nos arquivos do código-fonte do seu repositório, os downloads desses arquivos contarão para o uso de banda larga no repositório. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

        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 f97112a8672d8..4a0f441acbde3 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 @@ -59,5 +59,5 @@ Se houver arquivos no seu repositório com os quais deseja usar o {% data variab ### Leia mais -- "[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" %} +- "[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@3.0" 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-security-vulnerabilities/about-dependabot-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index 45a9faeff077b..096efc6fa6c30 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 @@ -33,3 +33,7 @@ Ao fazer merge de um pull request que contém uma atualização de segurança, o ### Sobre pontuações de compatibilidade 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. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". \ No newline at end of file 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 528e4bfc9a4c7..b2e4b50952cda 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 @@ -42,16 +42,18 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit ### Gerenciar {% data variables.product.prodname_dependabot_security_updates %} para seus repositórios -Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} em um repositório individual. +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} 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)". O {% data variables.product.prodname_dependabot_security_updates %} exige configurações específicas do repositório. Para obter mais informações, consulte "[Repositórios compatíveis](#supported-repositories)". +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Acima da lista de alertas, use o menu suspenso e selecione ou desmarque as atualizações de segurança do **{% data variables.product.prodname_dependabot %}**. ![Menu suspenso com a opção de ativar {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### Leia mais diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 1ec7743a2f04e..41e5af8e7a39c 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ Você pode definir as configurações de notificação para si mesmo ou para sua {% note %} -**Observação:** Você pode filtrar suas notificações da caixa de entrada de {% data variables.product.company_short %} para mostrar {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %} alertas de segurança{% endif %}. Para obter mais informações, consulte "[Gerenciar notificações da sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)". +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". {% endnote %} 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 c9d9ce7b78b7b..9fbcec561398e 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 @@ -78,13 +78,15 @@ A melhor maneira de resolver este erro é fazer o merge ou fechar alguns dos pul #### {% data variables.product.prodname_dependabot %} não pode resolver seus arquivos de dependência -**Somente atualizações da versão.** Se {% data variables.product.prodname_dependabot %} tentar verificar se referências de dependências precisam ser atualizadas em um repositório, mas não for possível acessar um ou mais arquivos referenciados, você verá a mensagem de erro "{% data variables.product.prodname_dependabot %} não pode resolver seus arquivos de dependência de LANGUAGE". +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, {% data variables.product.prodname_dependabot %} não é compatível com dependências privadas {% data variables.product.prodname_dotcom %} para todos os gerenciadores de pacote. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". ### Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente Se você desbloquear {% data variables.product.prodname_dependabot %}, você poderá iniciar manualmente uma nova tentativa de criar um pull request. - **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**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 97ab1fd06e03f..c3a7e0c0acb5e 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notificações e assinaturas Você pode optar por receber atualizações em curso sobre a atividade específica no {% data variables.product.product_name %} por meio de uma assinatura. As notificações são atualizações que você recebe para atividades específicas que você assinou. @@ -50,7 +54,7 @@ Para cancelar a inscrição de conversas que você se inscreveu automaticamente, ### Personalizando notificações e assinaturas -Você pode optar por visualizar suas notificações através da caixa de entrada de notificações [https://github. um/notificações](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} e no {% data variables.product.prodname_mobile %} aplicativo{% endif %}, através do seu e-mail ou de uma combinação dessas opções. +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. Para personalizar os tipos de atualizações que você gostaria de receber e para onde enviar essas atualizações, configure suas configurações de notificação. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". @@ -58,7 +62,7 @@ Para manter suas assinaturas gerenciáveis, revise suas assinaturas e os reposit Para personalizar como você gostaria de receber atualizações de pull requests ou problemas específicos, é possível configurar suas preferências dentro do problema ou da pull request. Para obter mais informações, consulte “[Fazendo triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} Você pode habilitar notificações push no aplicativo {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)". {% endif %} @@ -89,7 +93,7 @@ Em sua caixa de entrada, você também pode fazer triagem de várias notificaç ### Personalizando sua caixa de entrada de notificações -Para se concentrar em um grupo de notificações na sua caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} ou em {% data variables.product.prodname_mobile %}{% endif %}, você pode criar filtros personalizados. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para mais exemplos de como personalizar a triagem de seu fluxo de trabalho, consulte "[Personalizando um fluxo de trabalho para triagem de suas notificações.](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications) +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para mais exemplos de como personalizar a triagem de seu fluxo de trabalho, consulte "[Personalizando um fluxo de trabalho para triagem de suas notificações.](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications) ### Política de retenção de notificações 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 0a07850cfc728..b095fd8e74834 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 @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Opções de entrega de notificação Você pode receber notificações de atividades em {% data variables.product.product_name %} nos locais a seguir. - - Caixa de notificações na interface web de {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - A caixa de entrada no {% data variables.product.prodname_mobile %}, que sincroniza com a caixa de entrada em {% data variables.product.product_name %}{% endif %} - - Um cliente de e-mail que usa um endereço de e-mail verificado, que também pode sincronizar com a caixa de entrada de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, consulte "[Escolhendo suas configurações de notificação](#choosing-your-notification-settings)". {% endif %} @@ -35,7 +39,7 @@ Você pode receber notificações de atividades em {% data variables.product.pro #### Benefícios da caixa de entrada de notificações -A caixa de entrada de notificações em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %} inclui opções de triagem projetadas especificamente para o seu fluxo de notificações de {% data variables.product.product_name %} e inclui opções para: +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - Fazer triagem de várias notificações ao mesmo tempo. - Marcar as notificações concluídas como **Concluído** e removê-las da sua caixa de entrada. Para ver todas as suas notificações marcadas como **Concluído**, use a consulta `is:done`. - Salvar uma notificação para revisar mais tarde. As notificações salvas são sinalizadas na sua caixa de entrada e mantidas indefinidamente. Para visualizar todas as suas notificações salvas, use a consulta `is:saved`. @@ -45,7 +49,7 @@ A caixa de entrada de notificações em {% data variables.product.product_name % - Criar filtros personalizados para focar em notificações diferentes quando quiser. - Notificações em grupo em sua caixa de entrada por repositório ou data para obter uma visão geral rápida com menos comutação de contexto -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} Além disso, a caixa de entrada de notificações em {% data variables.product.prodname_mobile %} permite que você faça triagem de notificações no modo escuro e receba notificações push para menções diretas. Para obter mais informações, consulte "[Habilitar notificações push com GitHub para celular](#enabling-push-notifications-with-github-for-mobile)" ou "[GitHub para celular](/github/getting-started-with-github/github-for-mobile)". {% endif %} @@ -77,7 +81,7 @@ Você pode configurar as notificações para um repositório na página do repos #### Participar de conversas A qualquer momento que você comentar em uma conversa ou quando alguém @mencionar seu nome de usuário, você estará _participando_ de uma conversa. Por padrão, você é inscrito automaticamente em uma conversa ao participar dela. Você pode cancelar manualmente a inscrição de uma conversa que você participou, clicando em **Cancelar inscrição** no problema ou na pull request ou através da opção **Cancelar inscrição** na caixa de entrada de notificações. -Para conversas que você está inspecionando ou participando, você pode escolher se deseja receber notificações por e-mail ou através da caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %}. +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. ![Opções de notificações de participação e inspeção](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -85,7 +89,7 @@ Por exemplo: - Se você não quiser que as notificações sejam enviadas para o seu e-mail, desmarque **e-mail** para participar e inspecionar as notificações. - Se quiser receber notificações por e-mail quando você participou de uma conversa, então selecione **e-mail** abaixo de "Participar". -Se você não permite assistir ou participar de notificações da web{% if currentVersion == "free-pro-team@latest" %} e móvel{% endif %}, sua caixa de entrada de notificações não terá nenhuma atualização. +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. ### Personalizando suas notificações por e-mail @@ -197,13 +201,15 @@ Escolha como você deseja receber atualizações de execução de fluxo de traba {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Habilitando notificações push com {% data variables.product.prodname_mobile %} Quando você instalar {% data variables.product.prodname_mobile %}, você será automaticamente incluído em notificações da web. Você poderá então ativar notificações push para menções diretas no app. Você só pode receber notificações de pushes para repositórios no {% data variables.product.prodname_mobile %} neste momento. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Habilitar notificações de push com {% data variables.product.prodname_ios %} 1. Acima de "Home", clique na foto do seu perfil. @@ -211,9 +217,11 @@ Você só pode receber notificações de pushes para repositórios no {% data va 3. Para atualizar suas configurações de notificação, clique em **Notificações push**. 4. Para ativar as notificações push para menções diretas, use a alternância **Menções Diretas**. +{% if currentVersion == "free-pro-team@latest" %} #### Habilitar notificações de push com {% data variables.product.prodname_android %} 1. Acima de "Home", clique na foto do seu perfil. 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de configurações para GitHub para iOS](/assets/images/help/mobile/android-settings-icon.png) 3. Para ativar as notificações push para menções diretas, use a alternância **Menções Diretas**. {% endif %} +{% endif %} \ No newline at end of file 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 f8fda0941b9c2..5e5c8949b4f56 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 @@ -1,6 +1,6 @@ --- title: Managing notifications from your inbox -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}.' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### About your inbox -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} @@ -86,31 +90,16 @@ Custom filters do not currently support: ### Supported queries for custom filters -There are three types of filters that you can use: +These are the types of filters that you can use: - Filter by repository with `repo:` - Filter by discussion type with `is:` - - Filter by notification reason with `reason:` - -To add a `repo:` filter, you must include the owner of the repository in the query. For example, `repo:atom/atom` represents the Atom repository owned by the Atom organization. + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -#### Supported `reason:` queries +#### Supported `repo:` queries -To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." - -| Query | Description | -|-----------------|-------------| -| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. -| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. -| `reason:comment`| When you commented on an issue, pull request, or team discussion. -| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. -| `reason:invitation` | When you're invited to a team, organization, or repository. -| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. -| `reason:mention` | You were directly @mentioned. -| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. -| `reason:team-mention` | When a team you're a member of is @mentioned. -| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. #### Supported `is:` queries @@ -137,3 +126,55 @@ You can also use the `is:` query to describe how the notification was triaged. - `is:done` - `is:unread` - `is:read` + +#### Supported `reason:` queries + +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." + +| Query | Description | +|-----------------|-------------| +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. +| `reason:comment`| When you commented on an issue, pull request, or team discussion. +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. +| `reason:invitation` | When you're invited to a team, organization, or repository. +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. +| `reason:mention` | You were directly @mentioned. +| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. +| `reason:team-mention` | When a team you're a member of is @mentioned. +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. + +For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. + +For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 3fdbc3e4d916d..cdaedf9c552c9 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ Ao cancelar a assinatura de notificações em sua caixa de entrada, elas desapar {% data reusables.notifications.access_notifications %} 1. Na caixa de entrada de notificações, selecione as notificações das quais você deseja cancelar sua assinatura. -2. Use o menu suspenso **selecionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para clicar em **Cancelar inscrição.** ![Opção de cancelamento de assinatura da caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Use o menu suspenso **selecionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para clicar em **Cancelar inscrição.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Cancelar assinatura de notificações na página de assinaturas @@ -64,4 +64,4 @@ Quando você deixa de inspecionar um repositório, você cancela sua assinatura - deixar de inspecionar um repositório - ignorar todas as notificações de um repositório - personalizar os tipos de eventos para os quais você recebe notificações (problemas, pull requests, versões ou discussões, se habilitado) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md index 273387a467958..95004080719a5 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,9 +14,11 @@ versions: You can collect user feedback, report software bugs, and organize tasks you'd like to accomplish with issues in a repository. Issues can act as more than just a place to report software bugs. +{% if currentVersion == "free-pro-team@latest" %} Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md index 6351ff3088242..09efee1be2aab 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Alterar a visibilidade dos quadros de projeto -intro: 'Como proprietário da organização ou administrador do quadro de projeto, você pode tornar um quadro de projeto público ou privado.' +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**Dica:** quando você torna seu quadro de projeto público, os integrantes da organização recebem acesso de leitura por padrão. Você pode conceder a integrantes específicos da organização permissões de gravação ou de administrador dando às equipes acesso ao quadro de projeto em que eles estão ativos ou adicionando-os ao quadro de projeto como um colaborador. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. Você pode conceder a integrantes específicos da organização permissões de gravação ou de administrador dando às equipes acesso ao quadro de projeto em que eles estão ativos ou adicionando-os ao quadro de projeto como um colaborador. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". {% endtip %} -1. Navegue até o quadro de projeto que deseja tornar público ou privado. +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. Em "Visibility" (Visibilidade), selecione **Public** (Público) ou **Private** (Privado). Em seguida, clique em **Save** (Salvar). ![Botões de opção Public (Público) e Private (Privado)](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md index cc8267c7040d4..1e595a54e1308 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ A automação de um quadro de projeto também é habilitada por padrão. Para ob 5. Se preferir, em "Project board name" (Nome do quadro de projeto), digite o nome do quadro de projeto copiado. ![Campo para digitar um nome para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-name.png) 6. Se desejar, em "Description" (Descrição), digite uma descrição do quadro de projeto copiado que outras pessoas verão. ![Campo para digitar uma descrição para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-description.png) 7. Se desejar, em "Automation settings" (Configurações de automação), selecione se deseja copiar os fluxos de trabalho automáticos configurados. Essa opção é habilitada por padrão. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards/)". ![Configurações de seleção de automação para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. Se você estiver copiando um quadro de projeto pertencente à organização, em "Visibility" (Visibilidade), selecione se deseja que o quadro de projeto copiado seja privado ou público. ![Configurações de seleção de visibilidade para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. Clique em **Copy project** (Copiar projeto). ![Botão Confirm Copy (Confirmar cópia)](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md index c51ec25f2ee55..4d9ed904205aa 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 0d30cc38e1e68..3d837fcd29471 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: Você pode filtrar uma lista de pull requests do repositório para encontrar: - Pull requests que ainda não foram [revisadas](/articles/about-pull-request-reviews) -- Pull requests que [necessitam de revisão](/articles/about-required-reviews-for-pull-requests) antes de serem mescladas +- Pull requests que [necessitam de revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de serem mescladas - Pull requests que um revisor aprovou - Pull requests nas quais um revisor solicitou alterações - Pull requests que você revisou diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md b/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md index 305bb5a45e93b..09e093c6b8f6c 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize issues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. -Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository. +Anyone with read access to a repository can view and search the repository’s labels. Anyone with triage access to a repository can apply/dismiss existing labels. To create, edit, apply, or delete a label, you must have write access to the repository. ### About default labels @@ -92,7 +92,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### Further reading -- "[About labels](/articles/about-labels)" - "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/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 d71d54c91b460..cb6f4cdaf328f 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 @@ -36,7 +36,7 @@ Para problemas, você também pode usar a busca para: Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests de [rascunho](/articles/about-pull-requests#draft-pull-requests): `is:draft` - Filtrar pull requests que não tenham sido [revisadas](/articles/about-pull-request-reviews) yet: `state:open type:pr review:none` -- Filtrar pull requests que [exijam uma revisão](/articles/about-required-reviews-for-pull-requests) para que o merge possa ser feito: `state:open type:pr review:required` +- Filtrar pull requests que [exijam uma revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) para que o merge possa ser feito: `state:open type:pr review:required` - Filtrar pull requests que tenham sido aprovadas por um revisor: `state:open type:pr review:approved` - 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` diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md index 48ccd45b3cf4d..8a57d92e3785a 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md @@ -48,10 +48,10 @@ Use os qualificadores `author-date` e `committer-date` para identificar commits {% data reusables.search.date_gt_lt %} -| Qualifier | Exemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) identifica os commits criados antes de 01-01-2016. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) identifica os commits feitos depois de 01-01-2016. | +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) identifica os commits criados antes de 01-01-2016. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | ### Filtrar commits de merge diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 93e44adb097a4..176d0d16a6acc 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: Depois de configurar o SAML SSO, os integrantes da sua organização de {% data variables.product.prodname_dotcom %} continuarão a fazer login em suas contas de usuário no {% data variables.product.prodname_dotcom %}. Quando um membro acessa recursos dentro de sua organização que usa o SAML SSO, o {% data variables.product.prodname_dotcom %} redireciona o integrante para o seu IdP para efetuar a autenticação. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. -Os proprietários das empresas também podem aplicar SAML SSO para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um n Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados. +{% data reusables.saml.saml-single-logout-not-supported %} + ### Serviços SAML compatíveis {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ Alguns IdPs suportam acesso de provisionamento a uma organização do {% data va Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)". -{% data reusables.organizations.team-synchronization %} - Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}. Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 82058028857a4..ddbf8b7022240 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ Estes provedores de identidade são compatíveis com a API de SCIM de {% data va - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Aplicando configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index fd9220fe7003e..cb90477d16334 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ Para cada colaborador pendente, você pode cancelar todos os convites para junta {% data reusables.organizations.people_tab_outside_collaborators %} 5. Clique em **X colaboradores pendentes**. ![Botão "Colaboradores pendentes"](/assets/images/help/organizations/pending-collaborator-list.png) 6. Clique em **Cancelar convites** à direita da pessoa para quem você deseja cancelar os convites. ![Botão "Cancelar convite"](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Clique em **Cancelar convites para colaboradores pendentes**. ![Botão para confirmar o cancelamento](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. Clique em **Cancelar convites para colaboradores pendentes**. ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md index db435ffb356bc..103d7933a34d4 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index c3df4b4ca215c..489c4eb19f2df 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Gerenciar as configurações de segurança e análise para a sua organização intro: 'Você pode controlar recursos que protegem e analisam o código nos projetos da sua organização no {% data variables.product.prodname_dotcom %}.' permissions: Os proprietários da organização podem gerenciar as configurações de segurança e análise de repositórios na organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Sobre a gestão de configurações de segurança e análise -O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. +O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os reposit {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -A página exibida permite que você habilite ou desabilite os recursos de segurança e análise dos repositórios na sua organização. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Habilitar ou desabilitar um recurso para todos os repositórios existentes +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +1. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. + {% if currentVersion == "free-pro-team@latest" %} + ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. + {% if currentVersion == "free-pro-team@latest" %} + ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. + {% if currentVersion == "free-pro-team@latest" %} + ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -### Habilitar ou desabilitar um recurso para todos os novos repositórios quando forem adicionados +### Enabling or disabling a feature automatically when new repositories are added 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Em "Configurar recursos de segurança e análise", à direita do recurso, habilite ou desabilite o recurso por padrão para novos repositórios na sua organização. ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Permitir que o Dependabot acesse repositórios privados -{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso aos arquivos de dependência de destino. Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências localizadas em repositórios privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. Para obter mais informações, incluindo detalhes das limitações para o suporte de dependências privadas, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências localizadas em repositórios privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. Para obter mais informações, incluindo detalhes das limitações para o suporte de dependências privadas, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". 1. Na seção "acesso ao repositório de {% data variables.product.prodname_dependabot %}" clique no botão de configurações **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) Uma lista é exibida mostrando todos os repositórios privados da sua organização. ![A lista de repositórios](/assets/images/help/organizations/repositories-dialog.png) 1. Selecione os repositórios que {% data variables.product.prodname_dependabot %} pode acessar. 1. Clique em **Selecionar repositórios**. - +{% endif %} ### Leia mais -{% if currentVersion == "free-pro-team@latest" %}- "[Sobre proteger o seu repositório](/github/administering-a-repository/about-securing-your-repository)" -- "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)" -- "[Manter suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} +- "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" - "[Gerenciar vulnerabilidades nas dependências do seu projeto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index cf3176d34332a..48307be68d915 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ Por exemplo, se um proprietário da organização concedeu a todos os integrante ### Visibilidade do quadro de projeto -{% data reusables.project-management.project-board-visibility %} Você pode alterar a visibilidade do quadro de projeto de privada para pública e vice-versa. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". ### Leia mais 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 b02423a03494f..899f0a6a52c52 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 @@ -58,7 +58,7 @@ Além de gerenciar as configurações da organização, os proprietários da org | 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** | +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | | Criar, editar, excluir etiquetas | | | **X** | **X** | **X** | | Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} | [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} @@ -100,25 +100,27 @@ Além de gerenciar as configurações da organização, os proprietários da org | 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** | +| Editar o branch padrão do repositório | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} | 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** | +| [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#granting-access-to-security-alerts) 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" %} +| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **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 %} +| [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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %}{% if currentVersion == "free-pro-team@latest" %} | [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **X** | **X** | | [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | | [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | @@ -127,7 +129,8 @@ Além de gerenciar as configurações da organização, os proprietários da org | [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | | [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | | [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### Leia mais 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 fcb5bd5ba785a..dd8a9367f69c5 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 @@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`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 %} +| [`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 %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. | [`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: @@ -197,7 +197,7 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. #### `dependabot_security_updates` category actions @@ -218,14 +218,14 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `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. +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. {% endif %} @@ -324,10 +324,12 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|-------------------{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). | `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} +| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} | `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. | `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} | `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} @@ -451,7 +453,9 @@ For more information, see "[Restricting publication of {% data variables.product |------------------|------------------- | `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} | `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. @@ -527,7 +531,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `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" %} @@ -536,7 +540,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. +| `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 @@ -559,7 +563,7 @@ For more information, see "[Restricting publication of {% data variables.product | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `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)") @@ -568,7 +572,6 @@ For more information, see "[Restricting publication of {% data variables.product | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` category actions | Action | Description @@ -577,11 +580,12 @@ For more information, see "[Restricting publication of {% data variables.product | `add_repository` | Triggered when a team is given control of a repository. | `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | `change_privacy` | Triggered when a team's privacy level is changed. -| `create` | Triggered when a new team is created. -| `destroy` | Triggered when a team is deleted from the organization. +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} +| `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. -{% endif %} #### `team_discussions` category actions diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 424cab5098450..eb1cfbafd2ef5 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: Você pode conectar até cinco grupos de IdP a uma equipe do {% data variables.product.prodname_dotcom %}. Um grupo de IdP pode ser atribuído a várias equipes do {% data variables.product.prodname_dotcom %} sem restrição. +Team synchronization does not support IdP groups with more than 5000 members. + Uma vez que uma equipe do {% data variables.product.prodname_dotcom %} está conectada a um grupo de IdP, o administrador do IdP deve efetuar as alterações da associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação na equipe em {% data variables.product.product_name %} ou usar a API. Todas as alterações de membros da equipe feitas através do seu IdP aparecerão no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização de equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora. A conexão de uma equipe a um grupo de IdP pode remover alguns integrantes da equipe. Para obter mais informações, consulte "[Requisitos para integrantes de equipes sincronizadas](#requirements-for-members-of-synchronized-teams)". @@ -27,19 +29,22 @@ Você também pode gerenciar a sincronização de equipe com a API. Para obter m ### Requisitos para integrantes de equipes sincronizadas -Após conectar uma equipe a um grupo de IdP, os dados da associação para cada integrante da equipe serão sincronizados se a pessoa continuar a efetuar a autenticação usando o SAML SSO com a mesma identidade SSO em {% data variables.product.prodname_dotcom %} e se a pessoa continuar como integrante do grupo de IdP conectado. +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -As equipes ou integrantes de grupo existentes podem ser automaticamente removidos da equipe em {% data variables.product.prodname_dotcom %}. Todas as equipes ou membros de grupo que não efetuem a autenticação na conta da organização ou da empresa usando SSO podem perder o acesso aos repositórios. Todas as equipes existentes ou integrantes de grupo que não estiverem no grupo de IdP conectado podem perder o acesso aos repositórios. +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." Um integrante removido da equipe pode ser adicionado de volta a uma equipe automaticamente após efetuar a autenticação na conta da organização ou na conta corporativa usando SSO e será movidos para o grupo de IdP conectado. -Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Se sua organização pertencer a uma conta corporativa, habilitar a sincronização de equipes para a conta corporativa irá substituir as configurações de sincronização de equipe no nível da organização. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". +Se sua organização pertencer a uma conta corporativa, habilitar a sincronização de equipes para a conta corporativa irá substituir as configurações de sincronização de equipe no nível da organização. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." ### Pré-requisitos -Antes poder conectar uma equipe a um grupo de provedores de identidade, uma organização ou dono da empresa deve habilitar a sincronização de equipes para sua organização ou conta corporativa. Para mais informações consulte "[Gerenciar a sincronização de equipes para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" e "[Aplicar configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". +Antes poder conectar uma equipe a um grupo de provedores de identidade, uma organização ou dono da empresa deve habilitar a sincronização de equipes para sua organização ou conta corporativa. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." Para evitar a remoção involuntária dos integrantes da equipe, visite o portal administrativo do seu IdP e confirme se cada integrante atual da equipe está também nos grupos de IdP aos quais você deseja conectar a esta equipe. Se você não tiver acesso ao provedor de identidade, entre em contato com o administrador do IdP. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index 8a120580cd251..f8ac672a82082 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ Você pode visualizar e revogar a identidade vinculada de cada integrante, as se {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..048042ddfa25f --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. Para obter mais informações, consulte a [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS. + +| IdP | SAML | User provisioning | Sincronização de equipes | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..88bcd9d2709cd --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} Opcionalmente, você também pode habilitar o provisionamento de SAML e, separadamente, o desprovisionamento. + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. Se você ativar o provisionamento de SAML, toda vez que um integrante da empresa acessar um recurso protegido pela configuração de SAML da conta corporativa, essa declaração de SAML irá acionar o provisionamento. + +Para cada chamada de SCIM ou declaração de SAML, {% data variables.product.product_name %} irá verificar os grupos de IdP aos quais o usuário pertence e executar as operações a seguir: + +- Se o usuário for integrante de um grupo de IdP que corresponde a uma organização pertencente à conta corporativa e o usuário não for, atualmente, um membro dessa organização, adicione o usuário à organização (declaração de SAML) ou envie um convite por e-mail para participar da organização (chamada de SCIM). +- Cancele quaisquer convites existentes para o usuário juntar-se a uma organização que pertencem à conta corporativa. + +Para cada chamada de SCIM e, no caso de habilitar o desprovisionamento de SAML, em cada declaração de SAML, o {% data variables.product.product_name %} também executará a operação a seguir: + +- Se o usuário não for membro de um grupo de IdP que corresponde a uma organização pertencente à sua conta corporativa, e o usuário for, atualmente, um integrante dessa organização, remova o usuário da organização. + +Se desprovisionamento remover o último proprietário de uma organização, a organização ficará sem proprietário. Os proprietários das empresas podem assumir a propriedade de organizações sem proprietários. Para obter mais informações, consulte "[Gerenciar organizações sem proprietários na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)". + +Para habilitar o provisionamento de usuários para sua conta corporativa usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)". diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index c5a43dcdf1792..71aaf5ec90b8d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponív 1. À direita do menu suspenso, digite `.*.*`. 1. Clique em **Salvar**. {% data reusables.saml.okta-view-setup-instructions %} -1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". ### Criar grupos no Okta diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..559e516aac60e --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: Habilitar logon único de SAML para organizações na conta corporativa +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, consulte "[Visualizar e gerenciar o acesso de SAML de um usuário à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} Se você não estiver participando do beta privado, o SCIM não será compatível para as contas corporativas. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Observação**: se você habilitar a autenticação com logon único SAML para a conta corporativa, as configurações SAML existentes no nível da organização serão substituídas. + +{% endnote %} + +Para obter informações mais detalhadas sobre como ativar o SAML usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) +8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) +9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) +10. Antes de habilitar o SAML SSO para sua empresa, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) +11. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 804ea9da4a9f9..3196ce1599c2a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ Você também pode configurar endereços IP permitidos para uma organização in {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### Habilitar logon único de SAML para organizações na conta corporativa - -{% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". - -Os proprietários empresariais podem ativar o SAML SSO e autenticação centralizada através de um IdP de SAML em todas as organizações que pertencem a uma conta corporativa. Depois que você habilita o SAML SSO para a conta corporativa, ele é habilitado por padrão para todas as organizações pertencentes a ela. Todos os integrantes deverão autenticar usando o SAML SSO para obter acesso às organizações de que fazem parte, e os proprietários corporativos precisarão autenticar usando o SAML SSO ao acessar uma conta corporativa. - -{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, consulte "[Visualizar e gerenciar o acesso de SAML de um usuário à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} Se você não estiver participando do beta privado, o SCIM não será compatível para as contas corporativas. Para obter mais informações, consulte "[Gerenciar o provisionamento de usuários para organizações na sua conta corporativa](#managing-user-provisioning-for-organizations-in-your-enterprise-account)". - -{% note %} - -**Observação**: se você habilitar a autenticação com logon único SAML para a conta corporativa, as configurações SAML existentes no nível da organização serão substituídas. - -{% endnote %} - -Para obter informações mais detalhadas sobre como ativar o SAML usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Isso confirma a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) -8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) -9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, nos menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação), escolha o algoritmo de hash usado pelo emissor de SAML. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) -10. Antes de habilitar o SAML SSO para sua empresa, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) -11. Clique em **Salvar**. - -### Gerenciar o provisionamento de usuários para organizações na conta corporativa - -Os proprietários das empresas podem gerenciar a participação na organização de uma conta corporativa diretamente de um provedor de identidade (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Opcionalmente, você também pode habilitar o provisionamento de SAML e, separadamente, o desprovisionamento. - -Se você configurar o SCIM no seu IdP, toda vez que fizer alterações na associação do grupo no seu IdP, este fará uma chamada de SCIM para {% data variables.product.prodname_dotcom %} afim de atualizar a associação da organização correspondente. Se você ativar o provisionamento de SAML, toda vez que um integrante da empresa acessar um recurso protegido pela configuração de SAML da conta corporativa, essa declaração de SAML irá acionar o provisionamento. - -Para cada chamada de SCIM ou declaração de SAML, {% data variables.product.product_name %} irá verificar os grupos de IdP aos quais o usuário pertence e executar as operações a seguir: - -- Se o usuário for integrante de um grupo de IdP que corresponde a uma organização pertencente à conta corporativa e o usuário não for, atualmente, um membro dessa organização, adicione o usuário à organização (declaração de SAML) ou envie um convite por e-mail para participar da organização (chamada de SCIM). -- Cancele quaisquer convites existentes para o usuário juntar-se a uma organização que pertencem à conta corporativa. - -Para cada chamada de SCIM e, no caso de habilitar o desprovisionamento de SAML, em cada declaração de SAML, o {% data variables.product.product_name %} também executará a operação a seguir: - -- Se o usuário não for membro de um grupo de IdP que corresponde a uma organização pertencente à sua conta corporativa, e o usuário for, atualmente, um integrante dessa organização, remova o usuário da organização. - -Se desprovisionamento remover o último proprietário de uma organização, a organização ficará sem proprietário. Os proprietários das empresas podem assumir a propriedade de organizações sem proprietários. Para obter mais informações, consulte "[Gerenciar organizações sem proprietários na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)". - -Para habilitar o provisionamento de usuários para sua conta corporativa usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)". - -### Gerenciar a sincronização de equipes para organizações na conta corporativa - -Os proprietários das empresas podem habilitar a sincronização de equipes entre um IdP e {% data variables.product.product_name %} para permitir que os proprietários da organização e os mantenedores de equipe conectem equipes nas organizações pertencentes à sua conta corporativa com grupos de IdP. - -{% data reusables.identity-and-permissions.about-team-sync %} - -Você pode usar a sincronização de equipes com a sua conta corporativa com o Azure AD. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -Você também pode configurar e gerenciar a sincronização da equipe para uma organização individual. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)". - -#### Pré-requisitos - -Antes de poder habilitar a sincronização de equipes para a sua conta corporativa: - - Você ou o administrador do Azure AD deve ser um administrador global ou um administrador com função privilegiada no Azure AD. - - Você deve habilitar o logon único SAML para organizações na conta corporativa com o IdP compatível. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". - - Você deve efetuar a autenticação na sua conta corporativa usando o SAML SSO e o IdP compatível. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". - -#### Gerenciar a sincronização de equipe para o Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Revise as informações do locatário do provedor de identidade que você deseja conectar à conta corporativa e clique em **Aprovar**. ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png) -8. Para desativar a sincronização de equipe, clique **Desativar sincronização de equipe**. ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png) - ### Gerenciar autoridades certificadas de SSH da conta corporativa Os proprietários corporativos podem adicionar e excluir autoridades certificadas (CAs) de SSH de uma conta corporativa. @@ -203,3 +112,7 @@ A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### Leia mais + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" 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 aafad0d5d94a3..2f7c5e8091494 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 @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + 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 f71e6b4e4bfd3..15471686bd5c1 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 @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} é uma oferta combinada da Microsoft que permite que um assinante use {% data variables.product.prodname_enterprise %} e {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} está disponível na Microsoft nos termos do Contrato da Microsoft. Para obter mais informações, consulte [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) no site {% data variables.product.prodname_vs %} -Depois de atribuir uma licença de {% data variables.product.prodname_vss_ghe %} a um assinante, o integrante usará a parte {% data variables.product.prodname_enterprise %} da licença, juntando-se a uma organização na sua conta corporativa com uma conta de usuário no {% data variables.product.prodname_dotcom_the_website %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. Para obter mais informações sobre o {% data variables.product.prodname_enterprise %}, consulte "[Produtos do {% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)". Para obter mais informações sobre contas em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". @@ -27,11 +29,13 @@ Para obter mais informações sobre o {% data variables.product.prodname_enterpr 3. Em {% data variables.product.prodname_dotcom_the_website %}, crie pelo menos uma organização pertencente à conta corporativa. Para obter mais informações, consulte "[Adicionar organizações à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)". -4. O assinante deve criar uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e o endereço de e-mail para a conta deve ser o mesmo endereço de e-mail que o endereço de e-mail no portal {% data variables.product.prodname_vs %}. Para obter mais informações, consulte "[Inscrever-se em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" e " "[Gerenciar preferências de e-mail](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". - ### Convidar um assinante para usar {% data variables.product.prodname_enterprise %} -Para usar a parte de {% data variables.product.prodname_enterprise %} da licença, o integrante deve participar de uma organização pertencente à sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Os proprietários da organização podem convidar novos integrantes para uma organização. Para obter mais informações, consulte "[Convidar usuários para participar da sua organização](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)". +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." ### Visualizar licenciamento de {% data variables.product.prodname_enterprise %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..040ed9f953655 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Gerenciar a sincronização de equipes para organizações na conta corporativa +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +Você também pode configurar e gerenciar a sincronização da equipe para uma organização individual. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)". + +### Pré-requisitos + +Você ou o administrador do Azure AD deve ser um administrador global ou um administrador com função privilegiada no Azure AD. + +Você deve habilitar o logon único SAML para organizações na conta corporativa com o IdP compatível. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". + +Você deve efetuar a autenticação na sua conta corporativa usando o SAML SSO e o IdP compatível. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". + +### Gerenciar a sincronização de equipe para o Azure AD + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png) +8. Para desativar a sincronização de equipe, clique **Desativar sincronização de equipe**. ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index c34c8c04cfe31..98fb09a9334de 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -Se você habilitar o desprovisionamento de usuários para gerenciar a associação da organização na sua conta corporativa, você poderá acabar com uma organização sem proprietários. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". +Se você habilitar o desprovisionamento de usuários para gerenciar a associação da organização na sua conta corporativa, você poderá acabar com uma organização sem proprietários. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." {% data reusables.enterprise-accounts.access-enterprise %} 2. À direita do campo de pesquisa, clique **X sem proprietário**. ![Botão para visualizar organizações sem proprietários](/assets/images/help/business-accounts/unowned-organizations-button.png) 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 a1ab984a6e8dc..07f981664961e 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 @@ -18,6 +18,8 @@ Ao ativar o logon único do SAML para a sua conta corporativa, cada integrante d {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} 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 d93885da2f85a..ec46f8a414208 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 @@ -22,8 +22,8 @@ Para obter mais informações sobre como administrar gerentes de cobrança, cons {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Em +1. 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. 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 %}**. +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index d5fbb28c3aec7..8e9c2168cbcd2 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -36,23 +36,23 @@ Na maioria das vezes, a data de criação e a data do commit são as mesmas, mas Você pode usar o comando `git show` com o sinalizador `--pretty=fuller` para verificar se a data de criação do commit e a data do commit são diferentes. ```shell -$ git show O número de SHA do commit --pretty=fuller -commit O número de SHA do commit -Author: octocat e-mail do usuário -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 -Commit: Sally Johnson e-mail do usuário -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +$ git show Your commit SHA number --pretty=fuller +commit Your commit SHA number +Author: octocat user email +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 +Commit: Sally Johnson user email +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` Se a data de criação e do commit forem diferentes, é possível alterar manualmente a data do commit na URL para ver os detalhes do commit. Por exemplo: -- Esta URL usa a data de criação `2016-07-13`: +- Esta URL usa a data de criação `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- Esta URL usa a data do commit `2016-07-19`: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- Esta URL usa a data do commit `2018-04-10`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` Quando você abrir a URL com a data do commit modificada, poderá ver os detalhes do commit. 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 c06161402167e..fd666320b67f5 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 @@ -11,9 +11,9 @@ versions: ### Contribuições que são contabilizadas -#### Problemas e pull requests +#### Issues, pull requests and discussions -Os problemas e as pull requests aparecerão no gráfico de contribuições se tiverem sido abertos em um repositório autônomo, e não em uma bifurcação. +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. #### Commits Os commits aparecerão no gráfico de contribuições se atenderem a **todas** estas condições: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index 227108831c2a8..a91fd03d445f4 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,7 +14,7 @@ versions: Por escolha e flexibilidade sobre como e quando você usa {% data variables.product.product_name %}, você pode configurar configurações de tema para mudar como {% data variables.product.product_name %} fica para você. Você pode escolher dois temas, claro e escuro, ou você pode configurar {% data variables.product.product_name %} para seguir as configurações do seu sistema. Alguns desenvolvedores usam tema escuro para preferências pessoais, para reduzir o consumo de energia em certos dispositivos ou para reduzir o cansaço da vista em condições de pouco brilho. {% data reusables.user_settings.access_settings %} -1. Na barra lateral de configurações do usuário, clique em **Aparência**. ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png) +1. Na barra lateral de configurações do usuário, clique em **Aparência**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) 1. Em "Tema", selecione uma preferência de tema. ![Botões de opção para configurações de tema](/assets/images/help/settings/theme-settings-radio-buttons.png) ### Leia mais 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 fd56d5542362e..e58d449d54ec2 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 @@ -30,7 +30,8 @@ O proprietário do repositório tem controle total do repositório. Além das a | {% if currentVersion == "free-pro-team@latest" %}Convidar colaboradores{% else %}Adicionar colaboradores{% endif %} | | | "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | Alterar a visibilidade do repositório | "[Configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)" {% if currentVersion == "free-pro-team@latest" %} -| Limitar interações com o repositório | "[Limitar interações no seu repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository)",{% endif %} +| Limitar interações com o repositório | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)" | | Excluir o repositório | "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)" | | Gerenciar tópicos do repositório | "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" {% if currentVersion == "free-pro-team@latest" %} @@ -63,7 +64,8 @@ Collaborators can also perform the following actions. | Ação | Mais informações | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Bifurcar o repositório | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Create, edit, and delete comments on commits, pull requests, and issues in the repository |
        • "[About issues](/github/managing-your-work-on-github/about-issues)"
        • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
        • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
        | | Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | | Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 24fb71f04c09c..c64bb540d9d48 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ Existem três níveis de permissões para colaboradores de quadro de projeto: O proprietário do quadro de projeto e colaboradores com acesso de administrador têm controle total do quadro de projeto. Além de todas as permissões de colaboradores de quadro de projeto, um proprietário de quadro de projeto e um colaborador com acesso de administrador podem: - [Gerenciar, visualizar e adicionar colaboradores](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configurar um quadro de projeto como público ou privado](/articles/changing-project-board-visibility) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) - [Excluir um quadro de projeto](/articles/deleting-a-project-board/) - [Fechar um quadro de projeto](/articles/closing-a-project-board/) - [Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ Colaboradores com acesso de gravação em um quadro de projeto pertencente a um ### Visibilidade do quadro de projeto -Você pode alterar a visibilidade do quadro de projeto de privada para pública e vice-versa. Por padrão, os quadros de projeto pertencentes a um usuário são privados. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Por padrão, os quadros de projeto pertencentes a um usuário são privados. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". ### Leia mais diff --git a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md index adf108e0203c3..4c94a0e2b6611 100644 --- a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md +++ b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com, GitHub Enterprise Server, e as informações que você enviar para qualquer produto podem estar sujeitas a regulamentações de controle de negociação, inclusive sob Regulamentos da Administração de Exportação dos EUA (EAR). Regulamentos Administrativos de Exportação (EAR). -O objetivo do GitHub é ser a plataforma global para a colaboração de desenvolvedores, não importa onde os desenvolvedores estiverem. Levamos a sério a nossa responsabilidade de examinar minuciosamente as ordens governamentais para ter a certeza de que os usuários e clientes não sejam impactados para além do que seja exigido por lei. Isso inclui manter serviços de repositórios públicos, incluindo os destinados a projetos de código aberto, disponíveis e acessíveis para apoiar comunicações pessoais que envolvam desenvolvedores em regiões sancionadas. +O objetivo do GitHub é ser a plataforma global para a colaboração de desenvolvedores, não importa onde os desenvolvedores estiverem. Levamos a sério a nossa responsabilidade de examinar minuciosamente as ordens governamentais para ter a certeza de que os usuários e clientes não sejam impactados para além do que seja exigido por lei. This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. -Para estar em conformidade com os E.U.A. Para cumprir as leis de controle de negociação dos EUA, o GitHub realizou algumas alterações necessárias na forma como conduzimos nossos serviços. Como as leis de controle de comércio evoluem, continuaremos a trabalhar com as leis À medida que as leis de controle de negociação dos EUA evoluem, continuaremos a trabalhar com os reguladores dos EUA para saber em que medida podemos oferecer serviços gratuitos de colaboração em código aos desenvolvedores de mercados sancionados. Acreditamos que oferecer esses serviços grátis apoia os EUA. Acreditamos que oferecer esses serviços gratuitos ajuda a política externa dos EUA de incentivo ao livre fluxo de informação e à liberdade de expressão nesses mercados. Para saber mais sobre nossa abordagem e como as sanções afetam a colaboração do software global, leia nosso [blog sobre sanções](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Embora tenhamos fornecido as seguintes informações para sua conveniência, em última análise, é sua responsabilidade garantir que o seu uso de produtos e serviços GitHub esteja de acordo com todas as leis e regulamentações aplicáveis, incluindo as leis de controle exportação dos EUA. de controle de exportação dos EUA. @@ -25,9 +25,9 @@ De acordo com nossos [Termos de Serviço](/articles/github-terms-of-service), os Os usuários são responsáveis por garantir que o conteúdo que eles desenvolvem e compartilham no GitHub.com esteja em conformidade com as leis de controle de exportação dos EUA, incluindo o EAR e os Regulamentos de Tráfego Internacional de Armas dos EUA (ITAR). leis de controle de exportação, incluindo a EAR e os EUA Tráfego Internacional em Regulamentos de Armas (ITAR). A oferta de serviço hospedado na nuvem disponível no [GitHub.com](https://github.com) não foi projetado para hospedar dados sujeitos ao ITAR e, atualmente, não oferece a capacidade de restringir o acesso a repositório por país. Se você estiver procurando colaborar em ITAR ou em outros dados controlados por exportação, recomendamos que você considere o [GitHub Enterprise Server](https://enterprise.github.com), a oferta local do GitHub. -EUA As leis de controle de negociação dos EUA restringem quais serviços o GitHub.com pode tornar disponíveis para usuários em determinados países e territórios. O GitHub pode permitir aos usuários que residem normalmente em países e territórios sujeitos aos E.U.A. O GitHub pode permitir que usuários que residem normalmente em países e territórios sujeitos a sanções dos EUA acessem determinados serviços GitHub.com gratuitos para comunicação pessoal, de acordo com autorizações emitidas pelo Departamento de Controle de Ativos Estrangeiros do Departamento do Tesouro dos EUA (OFAC). Gabinete do Tesouro de Controle de Ativos Externos (OFAC). Pessoas localizadas ou normalmente residentes nesses países e territórios são proibidas de usar proxies de IP, VPNs, ou outros métodos para disfarçar sua localização ao acessar os serviços do GitHub.com para comunicações não comerciais e pessoais. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA Nacionais Especialmente Designados (SDNs) e outros grupos negados ou bloqueados pelas leis dos EUA e outras aplicáveis são proibidos de acessar ou usar o GitHub.com. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo os governos de países sancionados. Além disso, GitHub.com não pode ser utilizado para fins proibidos conforme as leis de controle de exportação aplicáveis, incluindo usos finais proibidos descritos em [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo os governos de países sancionados. Além disso, GitHub.com não pode ser utilizado para fins proibidos conforme as leis de controle de exportação aplicáveis, incluindo usos finais proibidos descritos em [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### GitHub Enterprise Server @@ -41,7 +41,7 @@ O GitHub Enterprise Server não pode ser vendido, exportado ou reexportado para #### Em que países e territórios são aplicadas sanções governamentais dos EUA? aplicadas sanções governamentais? -Crimeia, Cuba, Irã, Coreia do Norte e Síria. +Crimeia, Cuba, Irã, Coreia do Norte e Síria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. #### Como o GitHub garante que as pessoas que não vivem e/ou tenham ligações profissionais com os países e territórios sancionados ainda tenham acesso ou capacidade de recorrer? @@ -55,23 +55,23 @@ Viajar para essas regiões pode impactar o status de sua conta, mas a disponibil #### O que está e o que não está disponível? -O GitHub está comprometido em continuar a oferecer serviços gratuitos de repositório público para desenvolvedores com contas individuais e organizacionais em regiões sancionadas pelos EUA. Isso inclui acesso limitado a serviços gratuitos, como repositórios públicos para projetos de código aberto (e páginas públicas associadas), gists públicos e minutos de Ação gratuitos alocados, apenas para comunicações pessoais, e não para fins comerciais. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -No entanto, devido aos Estados Unidos Devido às restrições legais de controles comerciais dos EUA, o GitHub não pode fornecer serviços de repositório privados e serviços pagos a contas em regiões sancionadas pelos EUA. regiões sancionadas como a Coreia do Norte, o Irã, Síria e a Crimeia. A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. +O GitHub está comprometido em continuar a oferecer serviços gratuitos de repositório público para desenvolvedores com contas individuais e organizacionais em regiões sancionadas pelos EUA. Isso inclui acesso limitado a serviços gratuitos, como repositórios públicos para projetos de código aberto (e páginas públicas associadas), gists públicos e minutos de Ação gratuitos alocados, apenas para comunicações pessoais, e não para fins comerciais. -Para contas organizacionais pagas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas em regiões sancionadas, no entanto, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados gratuitos. +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -O GitHub continuará defendendo junto com os EUA. O GitHub continuará defendendo junto aos reguladores dos EUA o maior acesso possível a serviços gratuitos de colaboração de códigos para desenvolvedores em regiões sancionadas, incluindo repositórios privados gratuitos. Acreditamos que oferecer esses serviços grátis apoia os EUA. Acreditamos que oferecer esses serviços gratuitos ajuda a política externa dos EUA de incentivo ao livre fluxo de informação e à liberdade de expressão nessas regiões. +O GitHub continuará defendendo junto com os EUA. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. #### Como você define esses usuários específicos? -Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. restrições de controle comercial, ou um usuário tem restrições de outra forma nos EUA sanções econômicas. Portanto a conta afiliada foi restrita para cumprir esses requisitos legais. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. +Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. #### Como as contas da organização são impactadas? -Se uma organização tiver sede em, ou as principais pessoas ou membros de uma organização mostram laços suficientes a, um território ou país sancionado, ou se a organização parecer estar sujeita às sanções econômicas dos EUA, então a conta da organização e a conta do proprietário afiliado serão limitadas. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas. -A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. Para contas organizacionais pagas associadas com regiões sancionadas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas em regiões sancionadas, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados gratuitos. +A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### Os repositórios privados dos usuários com negociação restrita podem ser tornados públicos? @@ -81,3 +81,16 @@ Os usuários de contas individuais gratuitas podem tornar repositórios privados Infelizmente, a nossa interpretação da lei não nos dá a opção de permitir downloads ou exclusão de conteúdo de repositórios privados até que seja autorizado de outra forma pelo governo dos EUA. governo. Defenderemos energicamente com os EUA. Defenderemos, fortemente, junto dos órgãos reguladores dos EUA, o direito de usuários restritos à negociação protegerem o conteúdo de seus repositórios privados. Também defenderemos uma maior disponibilidade de serviços do GitHub para desenvolvedores em mercados sancionados, e reforçaremos ainda mais a importância da colaboração de códigos no apoio a comunicações pessoais para desenvolvedores em todo o mundo. +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. sanções econômicas. Portanto, o sinalizador será removido. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index be828c565ba59..254fc399a00b5 100644 --- a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ Dito isto, se uma ação legal for iniciada por terceiros, incluindo a aplicaç ### 3. Renúncia limitada a outras políticas do site -Na medida em que suas atividades de pesquisa de segurança são inconsistentes com certas restrições em nossas [políticas relevantes do site](/categories/site-policy/) mas são consistentes com os termos do nosso programa de recompensa de bugs, renunciamos a essas restrições com o único e limitado propósito de permitir sua pesquisa de segurança sob este programa de recompensa de bugs. Assim como acima, em caso de dúvida, pergunte-nos primeiro! +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Assim como acima, em caso de dúvida, pergunte-nos primeiro! 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 8738ffd486b99..bc0e0aae76bc4 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: '*' --- -Entrada em vigor: **30 de dezembro de 2020** +Effective date: **January 6, 2021** O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -25,12 +25,9 @@ Quando compartilhamos suas informações com terceiros subprocessadores, tais co | Braintree (PayPal) | Processador de pagamento de assinatura com cartão de crédito | Estados Unidos | Estados Unidos | | Clearbit | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | | Discourse | Provedor de software do fórum comunitário | Estados Unidos | Estados Unidos | -| 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 | Análise e desempenho | Estados Unidos | Estados Unidos | -| LinkedIn Navigator | Data enrichment service | 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 | | Mailgun | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | | Microsoft | Microsoft Services | Estados Unidos | Estados Unidos | diff --git a/translations/pt-BR/content/github/site-policy/index.md b/translations/pt-BR/content/github/site-policy/index.md index 61457e9ae8c4e..35e6ed0bf8e66 100644 --- a/translations/pt-BR/content/github/site-policy/index.md +++ b/translations/pt-BR/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 200240de30dab..e54561263b63c 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ Você pode ver a análise sobre seus patrocínios atuais e anteriores, os pagame ### Visualizando atividade de patrocínio recente {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. Na barra lateral esquerda, clique em **Atividade**. ![Aba de atividade](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### Exportando seus dados de patrocínio -Se você tiver patrocinadores, você poderá exportar os seus dados de patrocínio. {% data variables.product.prodname_dotcom %} enviará um e-mail com os dados de exportação de todos os seus patrocinadores para o mês que você selecionar. Depois que a exportação estiver concluída, você poderá exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas contas patrocinadas. +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. Depois que a exportação estiver concluída, você poderá exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas contas patrocinadas. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Clique em **Exportar tudo**. ![Botão Exportar tudo](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Botão de exportação](/assets/images/help/sponsors/export-all.png) 1. Escolha um período de tempo e um formato para os dados que você gostaria de exportar, e clique em **Iniciar a exportação**. ![Opções de Exportar dados](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file 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 301577ca6b259..5338ab78beba9 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 @@ -21,7 +21,7 @@ Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gr {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### Leia mais diff --git a/translations/pt-BR/content/github/using-git/adding-a-remote.md b/translations/pt-BR/content/github/using-git/adding-a-remote.md index c689c24f7282c..a5d34379d9176 100644 --- a/translations/pt-BR/content/github/using-git/adding-a-remote.md +++ b/translations/pt-BR/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ Você pode se deparar com estes erros ao tentar adicionar um remote. Esse erro significa que você tentou adicionar um remote com um nome que já existe no repositório local: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md index 0799f74ad2154..8d812510f8c10 100644 --- a/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,7 +124,11 @@ Como antes, o Git mostra a mensagem do commit para você editar. Altere o texto Como você alterou o histórico do Git, o `git push origin` normal **não** funcionará. É preciso modificar o comando forçando o push das alterações mais recentes: ```shell -$ git push origin master --force +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes +$ git push origin main --force ``` {% warning %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 7cfca48654479..6cd1db23e4d95 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ O tema engloba layouts, inclusões e folhas de estilo padrão que serão aplicad {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### Próximas etapas {% data reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". diff --git a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md index 5fbbbd90c75ee..f787c870a1d3e 100644 --- a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md +++ b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ Para verificar se, atualmente, há algum incidente afetando os serviços no {% d ### Entrar em contato com o {% data variables.contact.github_support %} -As contas de usuário e organização {% data variables.product.prodname_free_user %} podem usar o {% data variables.contact.community_support_forum %} para navegar em tópicos, fazer perguntas, compartilhar soluções e interagir diretamente com {% data variables.contact.community_support %}. Você também pode entrar em contato com {% data variables.contact.contact_support %} para relatar problemas de conta, segurança e abuso. +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -Em contas pagas, você pode entrar em contato com {% data variables.contact.contact_support %} e, dependendo do seu plano, entrar em contato com {% data variables.contact.premium_support %} ou {% data variables.contact.contact_ent_support %}. Para mais informações sobre contato {% data variables.contact.premium_support %}, consulte [Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud) ou [Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)." +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. ### Conceder acesso temporário do {% data variables.contact.github_support %} a um repositório privado 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 4c0e0608898ae..cc409e010f5dc 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 @@ -215,7 +215,7 @@ You can add emoji to your writing by typing `:EMOJICODE:`. Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result. -For a full list of available emoji and codes, check out [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). ### Paragraphs 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 df4494e9326f8..8d55d6245a8cb 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 @@ -1,6 +1,6 @@ --- title: Criar gists -intro: 'Você pode criar dois tipos de gist: público e secreto. Crie um gist público se estiver pronto para compartilhar suas ideias com o mundo; caso contrário, crie um gist secreto.' +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,13 @@ versions: ### Sobre gists -Cada gist é um repositório Git, o que significa que ele pode ser bifurcado e clonado. Se estiver conectado ao {% data variables.product.product_name %} quando criar um gist, o gist será associado à sua conta e você o verá na lista de gists quando navegar para sua {% data variables.gists.gist_homepage %}. +Cada gist é um repositório Git, o que significa que ele pode ser bifurcado e clonado. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -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 %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. Eles também são pesquisáveis, de modo que é possível usá-los se desejar que outras pessoas encontrem e vejam seu trabalho. -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). +Os gists secretos não aparecem em {% data variables.gists.discover_url %} e não são pesquisáveis. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your 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). + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -39,7 +41,7 @@ Você pode fixar os gists no seu perfil para que outras pessoas possam vê-los f {% endif %} -É possível descobrir gists que outras pessoas criaram acessando a {% data variables.gists.gist_homepage %} e clicando em **All Gists** (Todos os gists). Isso levará você a uma página com todos os gists classificados e exibidos por data de criação ou atualização. Também é possível pesquisar gists por linguagem com {% data variables.gists.gist_search_url %}. A pesquisa de gist usa a mesma sintaxe de pesquisa que a [pesquisa de código](/articles/searching-code). +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Isso levará você a uma página com todos os gists classificados e exibidos por data de criação ou atualização. Também é possível pesquisar gists por linguagem com {% data variables.gists.gist_search_url %}. A pesquisa de gist usa a mesma sintaxe de pesquisa que a [pesquisa de código](/articles/searching-code). Uma vez que os gists são repositórios Git, você pode exibir o histórico completo de commits deles, com diffs. Também é possível bifurcar ou clonar gists. Para obter mais informações, consulte ["Bifurcar e clonar gists"](/articles/forking-and-cloning-gists). @@ -69,12 +71,6 @@ Você também pode criar um gist usando o {% data variables.product.prodname_cli 4. Digite o texto do seu gist na caixa de texto do gist. ![Caixa de texto do gist](/assets/images/help/gist/gist_text_box.png) -5. Siga um destes procedimentos: - - Para criar um gist público, clique em **Criar gist público**. - - Para criar um gist secreto, clique em **Criar gist secreto**. ![Botão de criação do gist](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **Observação:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md index b41eb1615ba3e..c75a15dc7273c 100644 --- a/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Bifurcar gists -Cada gist indica quais bifurcações possuem atividade, o que facilita a localização de modificações interessantes feitas por colegas de trabalho ou pessoas desconhecidas. +Each gist indicates which forks have activity, making it easy to find interesting changes from others. ![Bifurcações gist](/assets/images/help/gist/gist_forks.png) diff --git a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md index ffddcf72cb845..e6b1211c57f46 100644 --- a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ As mutações são estruturadas da seguinte forma: 
        mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
        Neste exemplo, o objeto de entrada é `MutationNameInput` e o objeto de carga é `MutationNamePayload`. diff --git a/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md index d59297d76a085..a9bbf53162fa5 100644 --- a/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: Ao instalar ou publicar uma imagem do docker, o {% data variables.product.prodname_registry %} não é compatível camadas externas, como imagens do Windows. -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} Antes de poder usar o registro do Docker no {% data variables.product.prodname_registry %}, o administrador do site para {% data variables.product.product_location %} deve habilitar o suporte do Docker e o isolamento do subdomínio para a sua instância. Para obter mais informações, consulte "[Gerenciar pacotes do GitHub para a sua empresa](/enterprise/admin/packages)". @@ -30,8 +30,6 @@ Antes de poder usar o registro do Docker no {% data variables.product.prodname_r ### Autenticar-se no {% data variables.product.prodname_registry %} -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### Efetuando a autenticação com um token de acesso pessoal @@ -51,11 +49,25 @@ Para manter suas credenciais seguras, recomendamos que você salve seu token de {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} {% raw %} ```shell $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} Para usar este exemplo de comando de login, substitua `NOME DE USUÁRIO` pelo seu nome de usuário de {% data variables.product.product_name %} {% if enterpriseServerVersions contains currentVersion %}, `NOME DE HOST` pela URL para {% data variables.product.product_location %},{% endif %} e `~/TOKEN. xt` pelo caminho do arquivo para o seu token de acesso pessoal para {% data variables.product.product_name %}. @@ -94,9 +106,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. Se você ainda não criou uma imagem do docker para o pacote, crie a imagem, substituindo *PROPRIETÁRIO* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo o nome do repositório que contém o seu projeto, *IMAGE_NAME* pelo o nome do pacote ou imagem, *VERSÃO* com a versão do pacote no momento da criação, {% if enterpriseServerVersions contains currentVersion %} *NOME DE HOST* pelo o nome de host de {% data variables.product.product_location %},{% endif %} e *PATH* para a imagem se não estiver no diretório de trabalho atual. @@ -105,9 +127,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. Publicar a imagem em {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke #### Exemplo de publicação de uma imagem do Docker -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} Você pode publicar a versão 1.0 da imagem de `monalisa` para o repositório `octocat/octo-app` usando um ID de imagem. @@ -198,9 +247,19 @@ Você pode usar o comando `docker pull` para instalar uma imagem docker a partir $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio desabilitado: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/pt-BR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 4c70530c6fb7d..92d0ea3f87675 100644 --- a/translations/pt-BR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -78,10 +78,35 @@ 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. 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. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. Criar um novo projeto + ```shell + dotnet new console --name OctocatApp + ``` +2. Empacotar o projeto. + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +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.authenticate-step %} 2. Criar um novo projeto ```shell @@ -118,6 +143,8 @@ Você pode publicar um pacote no {% data variables.product.prodname_registry %}, dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### Publicar vários pacotes no mesmo repositório Para publicar vários pacotes no mesmo repositório, você pode incluir a mesma URL do repositório do {% data variables.product.prodname_dotcom %} nos campos de `ReposityURL` em todos os arquivos de projeto *.csproj*. O {% data variables.product.prodname_dotcom %} corresponde ao repositório baseado nesse campo. diff --git a/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md index 4cff9b09243cb..cd1ef0037878c 100644 --- a/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -209,6 +209,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### Leia mais - "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md index f93f99d14a066..63ab1cfacef1e 100644 --- a/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. No seu arquivo Docker, adicione esta linha, substituindo `PROPRIETÁRIO` e `REPO` pelas suas informações: ```shell - ETIQUETA org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` Por exemplo, se você é o usuário de `monalisa` e proprietário de `my-repo`, você adicionaria essa linha ao seu arquivo Docker: ```shell - ETIQUETA org.opencontainers.image.source https://github.com/monalisa/my-repo + ETIQUETA org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` Para obter mais informações, consulte "[ETIQUETA](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de anotação pré-definidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`. diff --git a/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md index cdb03488b8e1a..0f5589f9917b7 100644 --- a/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,272 @@ Você pode fazer referência ao `GITHUB_TOKEN` no seu arquivo de fluxo de trabal ### Publicar um pacote usando uma ação -Você pode publicar pacotes como parte do fluxo da sua integração contínua (CI) usando o {% data variables.product.prodname_actions %}. Por exemplo, você pode configurar um fluxo de trabalho para que sempre que um desenvolvedor fizer push do código para o branch-padrão, o fluxo de trabalho executará testes de CI. Se esses testes passarem, o fluxo de trabalho publicará uma nova versão de pacote no {% data variables.product.prodname_registry %}. Este fluxo de trabalho automatiza a criação de novas versões de pacotes somente se o código atender aos seus padrões de qualidade. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
        + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
        + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
        + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
        + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
        + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
        + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
        + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
        + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
        + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
        + +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Instalar um pacote usando uma ação Você pode instalar pacotes como parte de seu fluxo de CI usando o {% data variables.product.prodname_actions %}. Por exemplo, você poderia configurar um fluxo de trabalho para que sempre que um desenvolvedor fizesse push do código para um pull request, o fluxo de trabalho resolveria as dependências, fazendo o download e instalando pacotes hospedados pelo {% data variables.product.prodname_registry %}. Em seguida, o fluxo de trabalho pode executar testes de CI que exigem as dependências. diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md index 021a4427eacc0..9894fc8bb16bc 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ Você pode integrar {% data variables.product.prodname_registry %} com as APIs d You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% 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) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ Para obter mais informações, consulte: ### Gerenciar pacotes -Você pode excluir uma versão de um pacote privado em {% data variables.product.product_name %} ou usar a API do GraphQL. Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/graphql/guides/forming-calls-with-graphql)". +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/graphql/guides/forming-calls-with-graphql)". Você pode configurar webhooks para assinar eventos relacionados aos pacotes, como quando um pacote é publicado ou atualizado. Para obter mais informações, consulte o evento de webhook de "[`pacote`](/webhooks/event-payloads/#package)". diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index 7111220899e91..87b2b09aa516e 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -83,17 +83,6 @@ Gerencie [projetos](/rest/reference/projects). **Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} - - -### Bloqueio de usuário - -Os usuários podem [bloquear outros usuários](/rest/reference/users#blocking). As organizações também podem [bloquear usuários](/rest/reference/orgs#blocking). - -**Tipo de mídia personalizado:** `giant-sentry-fist-preview` **Anunciado em:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Atualização 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Atualização 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) - -{% endif %} - ### Tópicos do repositório diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index d07518ca711f6..706fd1da5431e 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 062ccc1e80bd1..812762ce3b08f 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 @@ -31,7 +31,7 @@ For information about GitHub's GraphQL API, see the [v4 documentation](/graphql) sent and received as JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -137,7 +137,7 @@ Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated- Authenticating with invalid credentials will return `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -369,7 +369,7 @@ Note that [the Search API has custom rate limit rules](/rest/reference/search#ra The returned HTTP headers of any API request show your current rate limit status: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -469,7 +469,7 @@ User-Agent: Awesome-Octocat-App cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -501,7 +501,7 @@ whenever possible. {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -512,7 +512,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -523,7 +523,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -546,7 +546,7 @@ Here's a sample request sent from a browser hitting `http://example.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval @@ -555,7 +555,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra This is what the CORS preflight request looks like: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With diff --git a/translations/pt-BR/content/rest/reference/code-scanning.md b/translations/pt-BR/content/rest/reference/code-scanning.md index 4c8232da7ef4f..d7b11664cadfc 100644 --- a/translations/pt-BR/content/rest/reference/code-scanning.md +++ b/translations/pt-BR/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Varredura de código redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml index ec1b5ac095c51..a95ec2698b635 100644 --- a/translations/pt-BR/data/glossaries/external.yml +++ b/translations/pt-BR/data/glossaries/external.yml @@ -123,7 +123,7 @@ - term: commit description: >- - Commit, ou "revisão", é uma alteração individual em um arquivo (ou conjunto de arquivos). Quando você faz um commit para salvar seu trabalho, o Git cria um ID exclusivo (também conhecido como "SHA" ou "hash") que mantém um registro das alterações, dos autores e de quando as alterações foram feitas. Em geral, os commits têm uma mensagem que mostra uma breve descrição das alterações. + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. - term: autor do commit description: Usuário que fez o commit. @@ -137,7 +137,7 @@ - term: mensagem do commit description: >- - Texto breve e descritivo que acompanha um commit e comunica a alteração que o commit apresenta. + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. - term: comparar branches description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - Gist é um arquivo compartilhável que você pode editar, clonar e bifurcar no GitHub. É possível deixar um gist público ou secreto, embora os secretos sempre fiquem disponíveis para qualquer pessoa que tenha a URL. + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- @@ -436,7 +436,7 @@ - term: notificação description: >- - Atualizações enviadas pela web ou por e-mail, dependendo das suas configurações, que informam sobre as atividades do seu interesse. + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. - term: aplicativo OAuth description: >- diff --git a/translations/pt-BR/data/glossaries/internal.yml b/translations/pt-BR/data/glossaries/internal.yml index aa9c2cccb2695..534ba0215d37f 100644 --- a/translations/pt-BR/data/glossaries/internal.yml +++ b/translations/pt-BR/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: Unidade de processamento central. - term: auxiliar de credenciais - description: Programa que armazena e regula as credenciais do Git. + description: A program that stores and fetches Git credentials. - term: creole description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - What You See Is What You Get, acrônimo indicativo de que o texto na tela é exatamente igual ao texto exibido após a renderização. + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. - term: XenServer description: Plataforma de virtualização. diff --git a/translations/pt-BR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..849d74eb1d224 --- /dev/null +++ b/translations/pt-BR/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: Acesso à exclusão de versão pacote + description: >- + Esta pré-visualização adiciona suporte para a mudança do DeletePackageVersion que permite a exclusão de versões privadas de pacotes. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implantações + description: >- + Esta visualização adiciona suporte para mudanças e novos recursos nos deployments. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - Mais informações detalhadas sobre o estado de merge de uma pull request. + description: >- + Esta visualização adiciona suporte para acessar campos que fornecem informações mais detalhadas sobre o estado de merge de uma pull request. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Atualiza vários refs em uma única operação. + description: Essa pré-visualização adiciona suporte para atualizar múltiplas refs em uma única operação. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Detalhes Tarefa Projeto + description: >- + Esta visualização adiciona detalhes de projeto, cartão de projeto e coluna de projetos para eventos de questões relacionadas ao projeto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Criar anexos de conteúdo + description: Esta visualização adiciona suporte para a criação de anexos de conteúdo. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Visualização de Issues fixados + description: Esta visualização adiciona suporte para os issues fixos. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Visualização de Etiquetas + description: >- + Esta visualização adiciona suporte para adicionar, atualizar, criar e excluir etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Projeto + description: Esta visualização adiciona suporte para a importação de projetos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Pré-visualização da Revisão da Equipe + description: >- + Esta pré-visualização adiciona suporte para atualizar as configurações da atribuição de revisão de equipe. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/pt-BR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..344e4d9d970f0 --- /dev/null +++ b/translations/pt-BR/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +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.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + 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' + 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' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + 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.' + date: 'RegistryPackageDependency.dependencyType' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + 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.' + 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.' + 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.' + reason: O status DRAFT será removido deste enum e o `isDraft` deverá ser usado + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: nplasterer diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..db126f55d5d09 --- /dev/null +++ b/translations/pt-BR/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Primeiros passos com {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'Você pode criar executores auto-hospedados para executar fluxos de trabalho em um ambiente altamente personalizável.' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/pt-BR/data/release-notes/2-22/0.yml b/translations/pt-BR/data/release-notes/2-22/0.yml index f25e465abdd97..48c31b169de4e 100644 --- a/translations/pt-BR/data/release-notes/2-22/0.yml +++ b/translations/pt-BR/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/3-0/0-rc.yml b/translations/pt-BR/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..3773b01888a3d --- /dev/null +++ b/translations/pt-BR/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Package Registry + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md index fecdc8ac9ced4..4babe46a83816 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. Em "Políticas", selecione uma opção. ![Habilita, desabilita ou limita ações para esta conta corporativa](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Habilita, desabilita ou limita ações para esta conta corporativa](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/pt-BR/data/reusables/actions/enterprise-beta.md b/translations/pt-BR/data/reusables/actions/enterprise-beta.md index d86df3736c446..4ec540e93d0e2 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-beta.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. Para revisar os requisitos de armazenamento externo e solicitar acesso ao beta, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md b/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..8b69ae48d3a35 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **Observação:** {% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md b/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md b/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md b/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md b/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..b3c04633baee8 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". diff --git a/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..fd06c5eb4c915 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### Próximas etapas + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md b/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md b/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md b/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..aaf92af3dee4b --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. Por exemplo, se o seu repositório contiver o código Node.js, você verá sugestões para projetos Node.js. Você pode usar os modelos do fluxo de trabalho como um ponto de partida para criar o fluxo de trabalho personalizado ou usá-los como se apresentam. + +Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório de {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` e no repositório {% data variables.product.product_location %}{% endif %}. diff --git a/translations/pt-BR/data/reusables/advanced-security/more-info-ghas.md b/translations/pt-BR/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..8398145e55ae9 --- /dev/null +++ b/translations/pt-BR/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)". +{% endif %} diff --git a/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/code-scanning/beta.md b/translations/pt-BR/data/reusables/code-scanning/beta.md index aaeb4a91f1e74..7d1b5dbc94798 100644 --- a/translations/pt-BR/data/reusables/code-scanning/beta.md +++ b/translations/pt-BR/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Nota:** {% data variables.product.prodname_code_scanning_capc %} está atualmente em versão beta e sujeito a alterações. Para obter mais informações sobre a participação no beta, [inscreva-se aqui](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/pt-BR/data/reusables/code-scanning/not-available.md b/translations/pt-BR/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..652243c6a1325 --- /dev/null +++ b/translations/pt-BR/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". + +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md index dc1266d067e6e..ba307a636c6ae 100644 --- a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index 21c5a40e6182f..afcce000901df 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Nota:**O fornecimento de usuários para contas corporativas está atualmente em versão beta privada e sujeita a alterações. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). {% endnote %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 41ce9977403e0..29c948b6c8813 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Requisitos mínimos](#minimum-requirements) -- [Recursos do beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [Armazenamento](#storage) - [CPU e memória](#cpu-and-memory) @@ -7,10 +8,10 @@ Recomendamos diferentes configurações de hardware, dependendo do número de licenças de usuário para {% data variables.product.product_location %}. Se você fornecer mais recursos do que os requisitos mínimos, sua instância terá um desempenho e uma escala melhores. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - Você deve configurar pelo menos um executor para fluxos de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- Você deve configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +- Você deve configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Máximo de trabalhos por minuto | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ Recomendamos um SSD de alto desempenho com operações de alta entrada/saída po A sua instância exige um disco de dados persistente separado do disco raiz. Para obter mais informações, consulte "[System overview](/enterprise/admin/guides/installation/system-overview)." -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -Se você habilitar o beta de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22, você precisará configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". {% endif %} @@ -48,4 +49,4 @@ O {% data variables.product.prodname_ghe_server %} exige mais recursos de CPU e {% endwarning %} -Você pode aumentar os recursos de memória ou da CPU na sua instância. Para obter mais informações, consulte "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +Você pode aumentar os recursos de memória ou da CPU na sua instância. Para obter mais informações, consulte "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md index cf565549b26f9..461702e2fd872 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Os requisitos mínimos para uma instância com recursos beta habilitados estão em **negrito** na tabela a seguir. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | +|:---------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------------:| +| Teste, demonstração ou 10 usuários leves | 2
        ou [**4**](#optional-features) | 16 GB
        ou [**32 GB**](#optional-features) | 100 GB
        ou [**150 GB**](#optional-features) | 200 GB | +| 10-3000 | 4
        ou [**8**](#optional-features) | 32 GB
        ou [**48 GB**](#optional-features) | 250 GB
        ou [**300 GB**](#optional-features) | 200 GB | +| 3000-5000 | 8
        ou [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12
        ou [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16
        ou [**20**](#optional-features) | 128 GB
        ou [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | |:---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------------:| | Teste, demonstração ou 10 usuários leves | 2{% if currentVersion == "enterprise-server@2.22" %}
        ou [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
        ou [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
        ou [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
        ou [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
        ou [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
        ou [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/actions.md b/translations/pt-BR/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..4c789eca69cfd --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. Na barra lateral esquerda, clique em **Actions** (Ações). ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..29c2a88163d31 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. A licença do {% data variables.product.prodname_advanced_security %} dá a você e aos seus usuários acesso a recursos que ajudam a tornar seus repositórios e códigos mais seguros. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..1e053507afc4c --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +1,5 @@ +{% warning %} + +**Aviso**: Alterar essa configuração fará com que {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} seja reiniciado. Você deve programar essa mudança com cuidado para minimizar o tempo de inatividade. + +{% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..c834bf66b443d --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md index 328f24279eeb2..69e6abf27f4f7 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/gated-features/environments.md b/translations/pt-BR/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/pt-BR/data/reusables/gated-features/environments.md +++ b/translations/pt-BR/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/protected-branches.md b/translations/pt-BR/data/reusables/gated-features/protected-branches.md index 6cbe4e3a9f0d7..ffae769bab961 100644 --- a/translations/pt-BR/data/reusables/gated-features/protected-branches.md +++ b/translations/pt-BR/data/reusables/gated-features/protected-branches.md @@ -1 +1 @@ -Os branches protegidos estão disponíveis em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md index 5f48619eca59d..696d1f2755cf6 100644 --- a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} está disponível em repositórios públicos e em repositórios privados pertencentes a organizações com uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 0e89045792ac2..535fa5cd9df20 100644 --- a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -Depois de criar um gist, não é possível convertê-lo de público para secreto. +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..f4a9bc14f5b4e --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/pt-BR/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..703d7485911ae --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. Para obter mais informações, consulte "[Variáveis de ambiente padrão](/actions/reference/environment-variables#default-environment-variables)". +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. Para obter mais informações, consulte "[Contextos](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)". + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/pt-BR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/pt-BR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index b1977a35f28d4..6db69c0441e05 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -Para habilitar a sincronização de equipes para Azure AD, sua instalação Azure AD precisa das seguintes permissões: +Para habilitar a sincronização de equipes para Azure AD, sua instalação Azure AD precisa das seguintes permissões. - Ler os perfis completos de todos os usuários - Entrar e ler o perfil do usuário - Ler dados do diretório diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md index 11ee9d9ae5330..24e48ac246f53 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. Para confirmar a sincronização de equipes: +5. Confirm team synchronization. - Se você tiver acesso ao IdP, clique em **Enable team synchronization** (Habilitar sincronização de equipes). Você será redirecionado para a página do SAML SSO do provedor de identidade e precisará selecionar sua conta e revisar as permissões solicitadas. - Se você não tiver acesso ao IdP, copie o link de redirecionamento do IdP e compartilhe-o com o administrador do IdP para continuar habilitando a sincronização de equipes. ![Botão de redirecionamento Enable team synchronization (Habilitar sincronização de equipes)](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md index 1bac09c271256..2943695c941f6 100644 --- a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Você pode escolher se Os objetos de {% data variables.large_files.product_name_short %} estão incluídos nos arquivos do código-fonte, como arquivos ZIP e tarballs, que {% data variables.product.product_name %} cria para o seu repositório. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

        diff --git a/translations/pt-BR/data/reusables/mobile/about-mobile.md b/translations/pt-BR/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/pt-BR/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/pt-BR/data/reusables/mobile/ghes-release-phase.md b/translations/pt-BR/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/pt-BR/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/mobile/push-notifications-on-ghes.md b/translations/pt-BR/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/pt-BR/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md b/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md index c01231495329e..1ed5f3afb99ac 100644 --- a/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -Você pode exigir que os integrantes usem certificados SSH para acessar os recursos da organização, a menos que o SSH esteja desabilitado no seu repositório. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/pt-BR/data/reusables/organizations/click-codespaces.md b/translations/pt-BR/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/pt-BR/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/pt-BR/data/reusables/organizations/team-synchronization.md b/translations/pt-BR/data/reusables/organizations/team-synchronization.md index e66864f92fde7..b59010df120cd 100644 --- a/translations/pt-BR/data/reusables/organizations/team-synchronization.md +++ b/translations/pt-BR/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -Você pode usar a sincronização de equipe para adicionar e remover automaticamente os membros da equipe em uma organização por meio de um provedor de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/pt-BR/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/pt-BR/data/reusables/package_registry/packages-cluster-support.md b/translations/pt-BR/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md index 445ac117f31ae..3f98063d3495d 100644 --- a/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Observação:** {% data variables.product.prodname_registry %} está atualmente em beta para {% data variables.product.prodname_ghe_server %} 2.22. Para participar da versão beta da sua instância, use o [formulário de inscrição](https://resources.github.com/beta-signup/). +**Observação:** {% data variables.product.prodname_registry %} está atualmente em beta para {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/profile/profile-readme.md b/translations/pt-BR/data/reusables/profile/profile-readme.md index b19f129859211..2c6a027c88c5a 100644 --- a/translations/pt-BR/data/reusables/profile/profile-readme.md +++ b/translations/pt-BR/data/reusables/profile/profile-readme.md @@ -1 +1 @@ -Se você adicionar um arquivo LEIAME à raiz de um repositório público com o mesmo nome de usuário, esse LEIAME aparecerá automaticamente na sua página de perfil. You can edit your profile README with {% data variables.product.company_short %} Flavored Markdown to create a personalized section on your profile. Para obter mais informações, consulte "[Gerenciar seu perfil LEIAME](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". +Se você adicionar um arquivo README à raiz de um repositório público com o mesmo nome de usuário, esse README aparecerá automaticamente na sua página de perfil. Você pode editar seu perfil README com {% data variables.product.company_short %} Flavored Markdown para criar uma seção personalizada no seu perfil. Para obter mais informações, consulte "[Gerenciar seu perfil README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." diff --git a/translations/pt-BR/data/reusables/project-management/choose-visibility.md b/translations/pt-BR/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..23d59907fa2d4 --- /dev/null +++ b/translations/pt-BR/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. Para obter mais informações, consulte "[Alterar visibilidade do quadro de projeto](/github/managing-your-work-on-github/changing-project-board-visibility)". ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md index 3692d90c14e7f..b3eea8ab502b6 100644 --- a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md +++ b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -Por padrão, o quadro de projeto é privado e fica visível apenas para pessoas com permissões de leitura, gravação ou de administrador ao quadro de projeto. Um quadro de projeto público fica visível para qualquer pessoa com o URL do quadro de projeto. +Por padrão, o quadro de projeto é privado e fica visível apenas para pessoas com permissões de leitura, gravação ou de administrador ao quadro de projeto. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index dd4d5866e6089..7fc764345da5d 100644 --- a/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -Se as verificações de status forem necessárias para um repositório, as verificações de status necessárias devem passar antes que você possa fazer merge do seu branch no branch protegido. Para obter mais informações, consulte "[Sobre verificações de status obrigatórias](/articles/about-required-status-checks)". +Se as verificações de status forem necessárias para um repositório, as verificações de status necessárias devem passar antes que você possa fazer merge do seu branch no branch protegido. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". diff --git a/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md index 75c4abeb18cfe..3526e39a78da3 100644 --- a/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -Os administradores do repositório podem exigir que todos os pull requests recebam um número específico de revisões de aprovações de pessoas com permissões de *gravação* ou *administrador* no repositório ou de um proprietário do código designado, antes de serem mesclados em um branch protegido. Para obter mais informações, consulte "[Sobre branches protegidos](/articles/about-protected-branches)". - -Quando as revisões necessárias estão ativadas, qualquer pessoa com acesso ao repositório poderá aprovar alterações em um pull request. No entanto você não conseguirá fazer merge do seu pull request até que o número necessário de revisores com permissões de *gravação* ou *admin* no repositório aprove as alterações do seu pull request na sua revisão. Para obter mais informações sobre os níveis de permissão do repositório, consulte "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization/)". Se a revisão for necessária de um proprietário do código designado e o pull request afetar o código que tem um proprietário designado, a aprovação deste proprietário será obrigatória. +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/pt-BR/data/reusables/repositories/branch-rules-example.md b/translations/pt-BR/data/reusables/repositories/branch-rules-example.md index 9cadc0abab384..ea81704455211 100644 --- a/translations/pt-BR/data/reusables/repositories/branch-rules-example.md +++ b/translations/pt-BR/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -Você pode criar uma regra de branch em um repositório para um branch específico, todos os branches, ou qualquer branch que corresponda a um padrão de nomenclatura especificado com a sintaxe fnmatch. Por exemplo, para exigir que qualquer branch que contenha a palavra `versão` tenha pelo menos duas revisões de pull request antes do merge, você pode criar uma regra de branch para `*versão*`. +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/pt-BR/data/reusables/repositories/relative-links.md b/translations/pt-BR/data/reusables/repositories/relative-links.md index 04d1b025e2e31..d532da34de5ba 100644 --- a/translations/pt-BR/data/reusables/repositories/relative-links.md +++ b/translations/pt-BR/data/reusables/repositories/relative-links.md @@ -1,6 +1,6 @@ É possível definir links relativos e caminhos de imagens em seus arquivos representados para ajudar os leitores a acessar outros arquivos no repositório. -Um link relativo é um link que é relativo ao arquivo atual. Por exemplo, se você tiver um arquivo LEIAME na raiz do seu repositório e tiver outro arquivo em _docs/CONTRIBUTING.md_, o link relativo para _CONTRIBUTING.md_ no seu README pode se parecer com isso: +Um link relativo é um link que é relativo ao arquivo atual. Por exemplo, se você tiver um arquivo README na raiz do seu repositório e tiver outro arquivo em _docs/CONTRIBUTING.md_, o link relativo para _CONTRIBUTING.md_ no seu README pode se parecer com isso: ``` [Diretrizes de contribuição para este projeto](docs/CONTRIBUTING.md) diff --git a/translations/pt-BR/data/reusables/repositories/return-to-source-diff.md b/translations/pt-BR/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..0532588e3bbba --- /dev/null +++ b/translations/pt-BR/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![Botão de diff de fonte](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md index b7c5860f68ab3..cfe413d8a0cef 100644 --- a/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -Depois que todos os revisores necessários tiverem aprovado um pull request, você não conseguirá fazer o merge se houver outros pull requests abertos com revisões pendentes ou rejeitadas e esses pull requests tiverem um branch principal apontando para o mesmo commit. Alguém com as permissões de *gravação* ou *admin* deverá aprovar ou ignorar a revisão de bloqueio nos outros pull requests antes que você possa fazer o merge. +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/pt-BR/data/reusables/repositories/section-links.md b/translations/pt-BR/data/reusables/repositories/section-links.md index 2ed662658f40e..fbf15f7f9ae7c 100644 --- a/translations/pt-BR/data/reusables/repositories/section-links.md +++ b/translations/pt-BR/data/reusables/repositories/section-links.md @@ -1,3 +1,3 @@ Você pode vincular diretamente a uma seção de um arquivo interpretado, passando o mouse sobre o título da seção para expor o link: -![Link da seção no arquivo LEIAME para o repositório github/scientist](/assets/images/help/repository/readme-links.png) +![Link da seção no arquivo README para o repositório github/scientist](/assets/images/help/repository/readme-links.png) diff --git a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index b74d5905b1e47..ba73880189979 100644 --- a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md index 9884c951fb1a8..fbf7214e602aa 100644 --- a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md +++ b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ Se você habilitar o e-mail ou as notificações da web para {% data variables.product.prodname_actions %}, você receberá uma notificação quando qualquer fluxo de trabalho que tenha sido acionado for concluído. A notificação incluirá o status da execução do fluxo de trabalho (incluindo execuções bem-sucedidas, com falhas, neutras e canceladas). Também pode optar por receber uma notificação apenas quando a execução de um fluxo de trabalho falhar. +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + Você também pode visualizar o status do fluxo de trabalho executado na aba Ações de um repositório. Para obter mais informações, consulte "[Gerenciar a execução de fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". diff --git a/translations/pt-BR/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/pt-BR/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..7b2ccf36dbc76 --- /dev/null +++ b/translations/pt-BR/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Os proprietários empresariais podem ativar o SAML SSO e autenticação centralizada através de um IdP de SAML em todas as organizações que pertencem a uma conta corporativa. Depois que você habilita o SAML SSO para a conta corporativa, ele é habilitado por padrão para todas as organizações pertencentes a ela. Todos os integrantes deverão autenticar usando o SAML SSO para obter acesso às organizações de que fazem parte, e os proprietários corporativos precisarão autenticar usando o SAML SSO ao acessar uma conta corporativa. diff --git a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md index f99d2436af8e6..be784eeb4f31c 100644 --- a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -O SAML SSO concede aos proprietários corporativos da organização em {% data variables.product.prodname_dotcom %} uma forma de controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/pt-BR/data/reusables/secret-scanning/about-secret-scanning.md b/translations/pt-BR/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md index e4664002b63f0..82fdadded9388 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta e sujeitos a alterações. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..c70a1b1f29321 --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Observação:** O administrador do site deve habilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %} antes de usar este recurso. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_secret_scanning %} para seu aplicativo ](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)". + +{% endnote %} + +{% endif %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index fff14d2294e9a..7dfe02992908b 100644 --- a/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Nota**: Você não pode desabilitar alguns recursos de segurança e análise que estão habilitados por padrão para repositórios públicos. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/activity-tab.md b/translations/pt-BR/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..e7d9f32aaec88 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. Na barra lateral esquerda, clique em **Atividade**. ![Aba de atividade](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/support/ghae-priorities.md b/translations/pt-BR/data/reusables/support/ghae-priorities.md index 21df4d4ca4c0f..76aadfdb77c55 100644 --- a/translations/pt-BR/data/reusables/support/ghae-priorities.md +++ b/translations/pt-BR/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Prioridade | Descrição | Exemplos | |:---------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} não pode ser acessado ou há uma falha total e esta afeta diretamente a operação do seu negócio.

        _Depois que você arquivar um tíquete de suporte, entre em contato com {% data variables.contact.github_support %} por telefone._ |
        • Erros ou falhas que afetam a funcionalidade central do Git ou do aplicativo web para todos os usuários
        • Degradação grave da rede ou desempenho para a maioria dos usuários
        • Armazenamento esgotado ou que se preenche rapidamente
        • Incidentes de segurança conhecidos ou uma violação do acesso
        | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falha em um ambiente de produção, com impacto limitado nos seus processos de negócios ou afeta apenas determinados clientes. |
        • Redução de desempenho que reduz a produtividade para muitos usuários
        • Problemas de redundância reduzidos provenientes de falhas ou degradação de serviço
        • Erros ou falhas que impactam a produção
        • Problemas de segurança de configuração de {% data variables.product.product_name %}
        | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falha em um ambiente de produção, com impacto limitado nos seus processos de negócios ou afeta apenas determinados clientes. |
        • Redução de desempenho que reduz a produtividade para muitos usuários
        • Problemas de redundância reduzidos provenientes de falhas ou degradação de serviço
        • Erros ou falhas que impactam a produção
        • {% data variables.product.product_name %} configuration security concerns
        | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} está passando por problemas e erros limitados ou moderados com {% data variables.product.product_name %} ou você tem preocupações ou dúvidas gerais sobre a operação de {% data variables.product.product_name %}. |
        • Orientação sobre a utilização das APIs e recursos de {% data variables.product.prodname_dotcom %} ou questões sobre a integração de fluxos de trabalho de negócios
        • Problemas com ferramentas de usuário e métodos de coleta de dados
        • Atualizações
        • Relatórios de erros, perguntas gerais de segurança ou outras questões relacionadas a recursos
          • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} está funcionando como esperado. No entanto, você tem uma dúvida ou sugestão sobre {% data variables.product.product_name %} que não é sensível ao tempo, ou não bloqueia a produtividade da sua equipe. |
          • Solicitações de recursos e feedback de produtos
          • Dúvidas gerais sobre a configuração geral ou o uso de {% data variables.product.product_name %}
          • Notificar {% data variables.contact.github_support %} de qualquer alteração planejada
          | diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md b/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index f959350afea0d..08624f1058592 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -4,7 +4,7 @@ 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.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' 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. early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,15 @@ product_landing: quick_start: QuickStart reference_guides: Reference guides overview: Visão Geral +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: mais guias + guideTypes: + overview: Visão Geral + quick_start: QuickStart + tutorial: Tutorial + how_to: How-to guide + reference: Referência diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml index cb6d66ecf9d61..8f9aecb699274 100644 --- a/translations/pt-BR/data/variables/action_code_examples.yml +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/pt-BR/data/variables/gists.yml b/translations/pt-BR/data/variables/gists.yml index d263d6bccf770..12c745fd3ceb3 100644 --- a/translations/pt-BR/data/variables/gists.yml +++ b/translations/pt-BR/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[Página inicial do gist](https://gist.github.com/){% else %}página inicial do gist, `http(s)://[hostname]/gist` ou `http(s)://gist.[hostname]` se os subdomínios estiverem habilitados {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Pesquisa do Gist](https://gist.github.com/search){% else %}Pesquisa do Gist, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` se os subdomínios estiverem habilitados{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Descubra, `http(s)://[hostname]/gist/discover` ou `http(s)://gist.[hostname]/discover` se os subdomínios estiverem habilitados{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index e9fc1d446a7a6..fb8d680c191bc 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'Fundo Correspondentes para Patrocinadores do GitHub' #GitHub Advanced Security +prodname_GH_advanced_security: 'Segurança Avançada GitHub' prodname_advanced_security: 'Segurança Avançada' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/pt-BR/data/variables/release_candidate.yml +++ b/translations/pt-BR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/ru-RU/content/actions/creating-actions/about-actions.md b/translations/ru-RU/content/actions/creating-actions/about-actions.md index c9e81f04b7b8c..3ba6a3504eb5d 100644 --- a/translations/ru-RU/content/actions/creating-actions/about-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/about-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 91bf1072283a6..ee6eadec266b4 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md index b4e0de332264f..ac11463d80d1c 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md index dde101d2a868b..ac6cd8748b1ca 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 0699d42e73d61..f336e760fae27 100644 --- a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'ссылка' --- {% data reusables.actions.enterprise-beta %} @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction: ##### Example *Dockerfile* -``` +``` # Container image that runs your code FROM debian:9.5-slim # Copies your code file from your action repository to the filesystem path `/` of the container COPY entrypoint.sh /entrypoint.sh -# Executes `entrypoint.sh` when the Docker container starts up +# Executes `entrypoint.sh` when the Docker container starts up ENTRYPOINT ["/entrypoint.sh"] ``` @@ -78,14 +79,14 @@ Using the example Dockerfile above, {% data variables.product.product_name %} wi ``` sh #!/bin/sh -# `$*` expands the `args` supplied in an `array` individually +# `$*` expands the `args` supplied in an `array` individually # or splits `args` in a string separated by whitespace. sh -c "echo $*" ``` Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command: ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this: diff --git a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 76b68f23101a6..9c1d7a8233691 100644 --- a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'ссылка' --- {% data reusables.actions.enterprise-beta %} @@ -104,12 +105,12 @@ outputs: {% raw %} ```yaml outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - id: random-number-generator run: echo "::set-output name=random-id::$(echo $RANDOM)" shell: bash @@ -213,7 +214,7 @@ For example, this `cleanup.js` will only run on Linux-based runners: ```yaml runs: using: "composite" - steps: + steps: - run: ${{ github.action_path }}/test/script.sh shell: bash ``` @@ -224,7 +225,7 @@ Alternatively, you can use `$GITHUB_ACTION_PATH`: ```yaml runs: using: "composite" - steps: + steps: - run: $GITHUB_ACTION_PATH/script.sh shell: bash ``` @@ -258,7 +259,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### Example using a Dockerfile in your repository ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -266,7 +267,7 @@ runs: #### Example using public Docker registry container ```yaml -runs: +runs: using: 'docker' image: 'docker://debian:stretch-slim' ``` diff --git a/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index a22537d463514..75a5c267a281d 100644 --- a/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. diff --git a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md index 86592860fdd77..df854ddf2cc66 100644 --- a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/about-continuous-integration.md b/translations/ru-RU/content/actions/guides/about-continuous-integration.md index 2df3ff6117e50..cf8d21e5a4f4e 100644 --- a/translations/ru-RU/content/actions/guides/about-continuous-integration.md +++ b/translations/ru-RU/content/actions/guides/about-continuous-integration.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md index ccc1b09e9c46a..fc8e30e426cba 100644 --- a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/about-service-containers.md b/translations/ru-RU/content/actions/guides/about-service-containers.md index 39724306f07e6..b705735032a57 100644 --- a/translations/ru-RU/content/actions/guides/about-service-containers.md +++ b/translations/ru-RU/content/actions/guides/about-service-containers.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md index b083489f23699..c9a67cf08536a 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md index 295781441790a..92bb9e22c2a71 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md index d3dbce807e92b..bd75623a94a6b 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-net.md b/translations/ru-RU/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..e244b11f7d18c --- /dev/null +++ b/translations/ru-RU/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Building and testing .NET +intro: You can create a continuous integration (CI) workflow to build and test your .NET project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introduction + +This guide shows you how to build, test, and publish a .NET package. + +{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners). + +### Требования + +You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." + +We recommend that you have a basic understanding of the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn). + +### Starting with the .NET workflow template + +{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet). + +To get started quickly, add the template to the `.github/workflows` directory of your repository. + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Specifying a .NET version + +To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. + +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Using multiple .NET versions + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Using a specific .NET version + +You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### Installing dependencies + +{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Caching dependencies + +You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package. + +For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project. + +{% endnote %} + +{% endif %} + +### Building and testing your code + +You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### Packaging workflow data as artifacts + +After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results. + +For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### Publishing to package registries + +You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md index 9961095056084..7a1bb014a9f3a 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +37,11 @@ To get started quickly, add the template to the `.github/workflows` directory of ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ The easiest way to specify a Node.js version is by using the `setup-node` action The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`. -The template includes a matrix strategy that builds and tests your code with three Node.js versions: 8.x, 10.x, and 12.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps. +The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps. Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." @@ -77,7 +80,7 @@ Each job can access the value defined in the matrix `node-version` array using t ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} 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 cad875bc84792..fc03f419662cd 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 @@ -7,6 +7,7 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-python.md b/translations/ru-RU/content/actions/guides/building-and-testing-python.md index ac05b2e4d7d6d..9c4c0c9703d9c 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-python.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-python.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} @@ -122,7 +123,7 @@ jobs: #### Using a specific Python version -You can configure a specific version of python. For example, 3.8. Alternatively, you can semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. +You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. {% raw %} ```yaml diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md index 1fe46e9133c8a..8dc0c358f92ce 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 497bcad57e586..daffa2cb6bbb0 100644 --- a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: 'руководство' --- ### About caching workflow dependencies diff --git a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md index f1f40f88647c3..fa571dc029891 100644 --- a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md b/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md index 98b3650c5751a..ed162bb97a26f 100644 --- a/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/index.md b/translations/ru-RU/content/actions/guides/index.md index 19b976dfcca47..6c9940f419deb 100644 --- a/translations/ru-RU/content/actions/guides/index.md +++ b/translations/ru-RU/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Creating custom continuous integration workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous integration (CI) workflows that build and test projects written in different programming languages. - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### Creating custom continuous deployment workflows - -You can use {% data variables.product.prodname_actions %} to create custom continuous deployment (CD) workflows that deploy projects to a number of cloud partner ecosystems. - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### Publishing software packages - -You can automate publishing software packages as part your continuous delivery (CD) workflow. Packages can be published to any package host and to {% data reusables.gated-features.packages %}. - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### Caching and storing workflow data - -Cache dependencies and store artifacts to make your workflow runs more efficient. - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### Using service containers in a workflow - -Connect services to your workflow using service containers. - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/ru-RU/content/actions/guides/publishing-docker-images.md b/translations/ru-RU/content/actions/guides/publishing-docker-images.md index 9d74b3db6823f..0b906c5d9caeb 100644 --- a/translations/ru-RU/content/actions/guides/publishing-docker-images.md +++ b/translations/ru-RU/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md index 9ce0de758136a..bcfeb2b04c7e0 100644 --- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md index 6279546b58684..07ffac448c67d 100644 --- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} 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 542c50c2b86cf..ac54eaf68b6b7 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} @@ -87,9 +88,28 @@ always-auth=true Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass. -By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope) in the npm documentation. +#### Configuring the destination repository -To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. + +However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Authenticating to the destination repository + +To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." + +If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +#### Example workflow This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. 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 b04280b5701c9..0a5c6a8bbbc62 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md index e4c841fe286dd..1f8698cda6eb2 100644 --- a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 28591c40bfb9e..5b5debce0498e 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 43374dea979a4..8189d1b188310 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,11 +7,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +You can add a self-hosted runner to a repository, an organization, or an enterprise. + +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. + For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% warning %} @@ -44,6 +49,8 @@ You can add self-hosted runners at the organization level, where they can be use {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### Adding a self-hosted runner to an enterprise You can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. @@ -62,3 +69,13 @@ To add a self-hosted runner at the enterprise level of 1. Click **Add new**, then click **New runner**. New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Making enterprise runners available to repositories + +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. + +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. + +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index b24159ce49673..5a1e3f65fbc56 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' defaultPlatform: linux --- diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 795ee89f10c9c..273606beb5d00 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index b7aa8e6513bec..1c181ca2a78f0 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' defaultPlatform: linux --- diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 62c39ed3c61dd..e326272ba54ea 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 46e8674cb5f1a..90e07d9e6b808 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index fc0a3e51ed296..c36e91739e798 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,6 +4,7 @@ intro: You can use labels to organize your self-hosted runners based on their ch versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 4ba6809cef574..e3719281440d0 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md index 3ae109ef0fe1b..442799764b18f 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,6 +5,7 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md index be8b6c25f2425..3c30b355f5a31 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -76,7 +77,7 @@ steps: #### Using branches -Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`: +Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`: ```yaml steps: 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 be54e37e62c3c..444cf11661b98 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 @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md index 5bc71b6958017..4fa6171158a55 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md @@ -5,6 +5,7 @@ intro: 'This guide shows you how to use the advanced features of {% data variabl versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -154,6 +155,15 @@ For more information, see ["Using labels with self-hosted runners](/actions/hos You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." {% endif %} +### Using a workflow template + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. If your repository already has existing workflows: In the upper-left corner, click **New workflow**. ![Create a new workflow](/assets/images/help/repository/actions-new-workflow.png) +1. Under the name of the template you'd like to use, click **Set up this workflow**. ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png) + ### Дальнейшие шаги To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 2d794e5443a72..938adb3f831d9 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} @@ -324,4 +325,3 @@ jobs: You can find actions that you can use in your workflow in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Creating actions](/actions/creating-actions)." - diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 497f6175fc14c..81211bae372b7 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 80d2f12511368..9e486eb227578 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,6 +4,7 @@ intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share sev versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index c1a4b1bb0af96..c35f28f041c5c 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- {% data reusables.actions.enterprise-beta %} @@ -166,7 +167,7 @@ Jenkins Pipeline maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Jenkins Pipeline needs: job1 job3: needs: [job1, job2] - + ``` diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 9f34eb94af730..f63ba3fd2fb5b 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'руководство' --- ### Introduction diff --git a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md index c6a734ce0807e..d9a3598533bb6 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'обзор' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 55f42d195420e..c36a1ee1794bb 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -44,10 +45,10 @@ This procedure demonstrates how to create a workflow template and metadata file. runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`: ```yaml @@ -75,7 +76,7 @@ To add another workflow template, add your files to the same `workflow-templates ![Workflow template files](/assets/images/help/images/workflow-template-files.png) -### Using a workflow template +### Using a workflow template from your organization This procedure demonstrates how a member of your organization can find and use a workflow template to create a new workflow. An organization's workflow templates can be used by anyone who is a member of the organization. diff --git a/translations/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index 9410275136995..12893c57bd6b2 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -66,9 +66,9 @@ Committing the workflow file in your repository triggers the `push` event and ru {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Дальнейшие шаги @@ -120,7 +120,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workfow you want to run. +1. In the left sidebar, click the workflow you want to run. ![Select say hello job](/assets/images/help/repository/say-hello-job.png) 1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow. ![Trigger the manual workflow](/assets/images/help/repository/manual-workflow-trigger.png) @@ -131,9 +131,9 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o 1. In the workflow logs, expand the 'Run echo "Hello World!"' section. ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Next steps diff --git a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 3830d74d03042..403079128a75d 100644 --- a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,6 +75,10 @@ In order to use property dereference syntax, the property name must: - start with `a-Z` or `_`. - be followed by `a-Z` `0-9` `-` or `_`. +#### Determining when to use contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### `github` context The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." @@ -107,15 +111,14 @@ The `github` context contains information about the workflow run and the event t The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)." -The `env` context syntax allows you to use the value of an environment variable in your workflow file. If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables. +The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." -You can only use the `env` context in the value of the `with` and `name` keys, or in a step's `if` conditional. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)." +If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables. | Property name | Тип | Description | | ---------------------- | -------- | ------------------------------------------------------------------------------------------------ | | `env` | `объект` | This context changes for each step in a job. You can access this context from any step in a job. | -| `env.` | `строка` | The value of a specific environment variable. | - +| `env.` | `строка` | The value of a specific environment variable. | #### `job` context diff --git a/translations/ru-RU/content/actions/reference/environment-variables.md b/translations/ru-RU/content/actions/reference/environment-variables.md index d87be6dcc32f8..34fef4132b5c9 100644 --- a/translations/ru-RU/content/actions/reference/environment-variables.md +++ b/translations/ru-RU/content/actions/reference/environment-variables.md @@ -57,6 +57,16 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. | +{% tip %} + +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determining when to use default environment variables or contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### Naming conventions for environment variables {% note %} 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 233474b017238..2476a4192f5d4 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 @@ -80,6 +80,8 @@ You can use these operators in any of the five fields: You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html). +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." + ### Manual events You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event. @@ -593,7 +595,8 @@ By default, a workflow only runs when a `pull_request_target`'s activity type is For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`. ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` 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 3c419f5b284e1..f81a2a8d431af 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 @@ -83,44 +83,11 @@ If there is a tool that you'd like to request, please open an issue at [actions/ {% endnote %} -Windows and Ubuntu runners are hosted in Azure and have the same IP address ranges as Azure Data centers. Currently, all Windows and Ubuntu {% data variables.product.prodname_dotcom %}-hosted runners are in the following Azure regions: - -- East US (`eastus`) -- East US 2 (`eastus2`) -- West US 2 (`westus2`) -- Central US (`centralus`) -- South Central US (`southcentralus`) - -Microsoft updates the Azure IP address ranges weekly in a JSON file that you can download from the [Azure IP Ranges and Service Tags - Public Cloud](https://www.microsoft.com/en-us/download/details.aspx?id=56519) website. You can use this range of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. - -The JSON file contains an array called `values`. Inside that array, you can find the supported IP addresses in an object with a `name` and `id` of the Azure region, for example `"AzureCloud.eastus2"`. - -You can find the supported IP address ranges in the `"addressPrefixes"` object. This is a condensed example of the JSON file. - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. + +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. + +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### File systems 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 954d2a359f50f..5b5d69a686367 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 @@ -187,7 +187,7 @@ For more information about cron syntax, see "[Events that trigger workflows](/ac ### `env` -A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} @@ -639,14 +639,15 @@ Using the `working-directory` keyword, you can specify the working directory of You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. -| Supported platform | `shell` parameter | Description | Command run internally | -| ------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | -| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | -| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | -| All | `python` | Executes the python command. | `python {0}` | -| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | +| Supported platform | `shell` parameter | Description | Command run internally | +| ------------------ | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | +| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | +| All | `python` | Executes the python command. | `python {0}` | +| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | #### Example running a script using bash @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### Example running a python script ```yaml @@ -1149,7 +1159,7 @@ You can use special characters in path, branch, and tag filters. - `**`: Matches zero or more of any character. - `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`. - `+`: Matches one or more of the preceding character. -- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. +- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. - `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. @@ -1167,35 +1177,35 @@ For more information about branch, tag, and path filter syntax, see "[`on.-`feature/your-branch` | -| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`
          -`feature/your-branch`
          -`feature/mona/the/octocat` | -| -`main`
          -`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`
          -`releases/mona-the-octocat` | -| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`
          -`releases` | -| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`
          -`every/tag` | -| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`
          -`feature`
          -`ver-10-feature` | -| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`
          -`v2.0`
          -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`
          -`v2.0.0` | +| Pattern | Description | Example matches | +| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | `feature/my-branch`

          `feature/your-branch` | +| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`

          `feature/your-branch`

          `feature/mona/the/octocat` | +| `main`

          `releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | `main`

          `releases/mona-the-octocat` | +| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`

          `releases` | +| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`

          `every/tag` | +| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`

          `feature`

          `ver-10-feature` | +| `v2*` | Matches branch and tag names that start with `v2`. | `v2`

          `v2.0`

          `v2.9` | +| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | `v1.10.1`

          `v2.0.0` | #### Patterns to match file paths Path patterns must match the whole path, and start from the repository's root. -| Pattern | Description of matches | Example matches | -| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | -| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`
          -`server.rb` | -| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`
          -`page.jsx` | -| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` | -| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`
          -`index.js` | -| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`
          -`js/index.js`
          -`src/js/app.js` | -| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`
          -`docs/file.txt` | -| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`
          -`docs/mona/octocat.txt` | -| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`
          -`docs/mona/hello-world.md`
          -`docs/a/markdown/file.md` | -| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`
          -`dir/docs/my-file.txt`
          -`space/docs/plan/space.doc` | -| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`
          -`js/README.md` | -| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`
          -`my-src/code/js/app.js` | -| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`
          -`path/their-post.md` | -| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`
          -`db/migrate-v1.0.sql`
          -`db/sept/migrate-v1.sql` | -| -`*.md`
          -`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`
          _Does not match_
          -`README.md`
          -`docs/hello.md` | -| -`*.md`
          -`!README.md`
          -`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`
          -`README.md`
          -`README.doc` | +| Pattern | Description of matches | Example matches | +| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`

          `server.rb` | +| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`

          `page.jsx` | +| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` | +| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`

          `index.js` | +| `'**.js'` | Matches all `.js` files in the repository. | `index.js`

          `js/index.js`

          `src/js/app.js` | +| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`

          `docs/file.txt` | +| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`

          `docs/mona/octocat.txt` | +| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`

          `docs/mona/hello-world.md`

          `docs/a/markdown/file.md` | +| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | `/docs/hello.md`

          `dir/docs/my-file.txt`

          `space/docs/plan/space.doc` | +| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`

          `js/README.md` | +| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`

          `my-src/code/js/app.js` | +| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`

          `path/their-post.md` | +| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`

          `db/migrate-v1.0.sql`

          `db/sept/migrate-v1.sql` | +| `*.md`

          `!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`

          _Does not match_

          `README.md`

          `docs/hello.md` | +| `*.md`

          `!README.md`

          `README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`

          `README.md`

          `README.doc` | diff --git a/translations/ru-RU/content/admin/authentication/using-saml.md b/translations/ru-RU/content/admin/authentication/using-saml.md index 39ffe4272c35e..f1c4317b290af 100644 --- a/translations/ru-RU/content/admin/authentication/using-saml.md +++ b/translations/ru-RU/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod ### SAML metadata -Your {% data variables.product.prodname_ghe_server %} instances's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. To configure your identity provider manually, the Assertion Consumer Service (ACS) URL is `http(s)://[hostname]/saml/consume`. It uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. diff --git a/translations/ru-RU/content/admin/configuration/command-line-utilities.md b/translations/ru-RU/content/admin/configuration/command-line-utilities.md index bb958600508bb..23452731fd9ba 100644 --- a/translations/ru-RU/content/admin/configuration/command-line-utilities.md +++ b/translations/ru-RU/content/admin/configuration/command-line-utilities.md @@ -468,18 +468,21 @@ ghe-webhook-logs ``` To show all failed hook deliveries in the past day: +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -To show the full hook payload, result, and any exceptions for the delivery: +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -To show global webhook deliveries: +To show the full hook payload, result, and any exceptions for the delivery: ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### Clustering diff --git a/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index aa528d974c472..c66e7118ea04c 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md index 00b54d32741ec..2fc6729e5f37f 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ If backup attempts overlap, the `ghe-backup` command will abort with an error me In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. You should see output similar to this: ```shell diff --git a/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index adb8908409a4a..08a27ed2a365f 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ For the users of {% data variables.product.product_location %} to be able to ena {% data reusables.enterprise_site_admin_settings.management-console %} 1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features including {% data variables.product.prodname_code_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. +{% data reusables.enterprise_management_console.advanced-security-license %} ### Enabling {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ If you can't see **{% data variables.product.prodname_advanced_security %}** in #### Setting up a self-hosted runner -If you are enrolled in the {% data variables.product.prodname_actions %} beta, then {% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." +{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. 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)." You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions. -#### Provisioning the action -To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate action must be available locally. You can make the action available in three ways. +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisioning the actions +To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended** You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. -- You can create a local copy of the action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository with the action. For example, if you want to use the {% data variables.product.prodname_codeql %} action, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. - +- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. ##### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} - 1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configuring {% data variables.product.prodname_codeql %} on a server without internet access +If the server on which you are running +{% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} Action sync tool to copy the {% data variables.product.prodname_codeql %} actions and query bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -After you configure a self-hosted runner, users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." +#### Enabling code scanning for individual repositories +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} -If your organization isn't taking part in the beta for {% data variables.product.prodname_actions %}, or if you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. +If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, 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)." ### Disabling {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/ru-RU/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..8d83fa78ac119 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configuring secret scanning for your appliance +shortTitle: Configuring secret scanning +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### About {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +### Требования + +To use {% data variables.product.prodname_secret_scanning %} in {% data variables.product.product_location %} you need these two prerequisites. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- You need an {% data variables.product.prodname_advanced_security %} license. + +#### Checking support for the SSSE3 flag on your vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. + +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Enter the following command: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling secret scanning](#enabling-secret-scanning)" below. + +If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. + +#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### Enabling {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### Disabling {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under " +{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md index e82e80ce1f918..1d763af000ebe 100644 --- a/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} To use Docker with {% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Path without subdomain isolation | Path with subdomain isolation | -| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled. | `http(s)://docker.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Path without subdomain isolation | Path with subdomain isolation | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled for the {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### Требования diff --git a/translations/ru-RU/content/admin/configuration/index.md b/translations/ru-RU/content/admin/configuration/index.md index 4efeb57618b89..ee042551f25e2 100644 --- a/translations/ru-RU/content/admin/configuration/index.md +++ b/translations/ru-RU/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..23e5d6e6fda33 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Managing GitHub for mobile for your enterprise +intro: You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}. +permissions: Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### About {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} For more information, see "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." + +Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data. + +### Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ru-RU/content/admin/enterprise-management/about-clustering.md b/translations/ru-RU/content/admin/enterprise-management/about-clustering.md index ee94eff1e93c5..8b3345da85472 100644 --- a/translations/ru-RU/content/admin/enterprise-management/about-clustering.md +++ b/translations/ru-RU/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ Learn more about [services required for clustering](/enterprise/{{ currentVersio Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). +{% data reusables.package_registry.packages-cluster-support %} + ### How do I get access to clustering? Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ru-RU/content/admin/enterprise-management/index.md b/translations/ru-RU/content/admin/enterprise-management/index.md index 0736f9e81df54..faaf069973dcb 100644 --- a/translations/ru-RU/content/admin/enterprise-management/index.md +++ b/translations/ru-RU/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md index a5c633d5c3eff..cf1da55ec1058 100644 --- a/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + + {% endnote %} + {% endif %} diff --git a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md index b2bb53fab5a1f..1a14b5b5682ff 100644 --- a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ For more information, see "[Command-line utilities](/enterprise/{{ currentVersio #### Rolling back a feature release To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Дополнительная литература + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md index 62ccf132cf633..c07df2a55839b 100644 --- a/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md @@ -59,7 +59,9 @@ After you submit your support request, we may ask you to share a support bundle - `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs - `collectd/logs/collectd.log`: Collectd logs - `mail-logs/mail.log`: SMTP email delivery logs +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`: Webhook delivery errors +{% endif %} For more information, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." diff --git a/translations/ru-RU/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..3b3b6da7eb2e0 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: About using actions on GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. + +{% data reusables.actions.enterprise-no-internet-actions %} + +### Official actions bundled with {% data variables.product.prodname_ghe_server %} + +Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. + +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. + +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. + +{% note %} + +**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.prodname_ghe_server %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." + +{% endnote %} + +### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} + +If users on your enterprise instance need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. + +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} + +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/ru-RU/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/ru-RU/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..ca8cd4f13168c --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Advanced configuration and troubleshooting +intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..a2556020e8d72 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. + +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: + +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. +1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f1a923878847e..e744c6d757ffd 100644 --- a/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can connect {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} using {% data variables.product.prodname_github_connect %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions @@ -23,3 +23,4 @@ Before enabling access to all actions from {% data variables.product.prodname_do {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..097155565b393 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..25cd172efd74f --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with Amazon S3 storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Требования + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..95e6dc91adad6 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Enabling GitHub Actions with Azure Blob storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Требования + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..c63b973301e36 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +versions: + enterprise-server: '>=3.0' +--- + +### Требования + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. +* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 37a543f948384..d47cc8b225a01 100644 --- a/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### About {% data variables.product.prodname_actions %} permissions for your enterprise diff --git a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..93e0cf66c1383 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. + +### Review hardware considerations + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### External storage requirements + +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. + +{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} supports these storage providers: + +* Azure Blob storage +* Amazon S3 +* S3-compatible MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Amazon S3 permissions + +{% data reusables.actions.enterprise-s3-permission %} + +### Enabling {% data variables.product.prodname_actions %} + +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/). + +### Дополнительная литература + +- "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +### Adding self-hosted runners + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." + +### General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." + +{% endif %} diff --git a/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..26ccc90fba599 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: High availability for GitHub Actions +intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +versions: + enterprise-server: '>=3.0' +--- + +### Replication or redundancy of your {% data variables.product.prodname_actions %} data + +{% data reusables.actions.enterprise-storage-ha-backups %} + +We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: + +* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### High availability replicas + +#### Promoting a replica + +When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. + +For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." + +#### Removing a high availability replica + +Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. diff --git a/translations/ru-RU/content/admin/github-actions/index.md b/translations/ru-RU/content/admin/github-actions/index.md index 2202fdb4d4ce5..55495f30bc2f6 100644 --- a/translations/ru-RU/content/admin/github-actions/index.md +++ b/translations/ru-RU/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### Table of Contents -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index c4f769fc23b5a..e917e17ebb5ae 100644 --- a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -To make specific actions from {% data variables.product.prodname_dotcom_the_website %} available to use in workflows, you can use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. ### About the `actions-sync` tool diff --git a/translations/ru-RU/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..0398e291daae1 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' +versions: + enterprise-server: '>=3.0' +--- + +### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + +#### Installing the certificate on the runner machine + +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. + +For the steps required to install a certificate, refer to the documentation for your runner's operating system. + +#### Configuring Node.JS to use the certificate + +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +Например: + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md b/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..c73102e2ec7b6 --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Например: + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Например: + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-aws.md index 99f9a206ca9e5..30957b2eb679a 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ Both primary and replica instances should be assigned separate EIPs in productio ### Дополнительная литература -- "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-azure.md index 9122a83f02e58..fc4cc741b917e 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ We recommend you use a DS v2 instance type with at least 14 GB of RAM. You can u {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### Дополнительная литература - ### Дополнительная литература - - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index db7f2444cdf13..db7460ae503f3 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll ### Дополнительная литература -- "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index 52cf02e1ec638..c3f54f887fdba 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### Дополнительная литература - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 19cf8dad17176..4c6c2e18992b6 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ versions: ### Дополнительная литература - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 9a86d7984c00a..63e9a16836bee 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### Дополнительная литература - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index b33134f5f5354..a93195996cf06 100644 --- a/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/ru-RU/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### Дополнительная литература - - "[System overview](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md b/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md index 58587b35ecc05..0f92dac3c7220 100644 --- a/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ To thoroughly test a {% data variables.product.prodname_ghe_server %} appliance 1. Perform a backup of your production instance using {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the "About {% data variables.product.prodname_enterprise_backup_utilities %}" section of "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)." 2. Set up a new instance to act as your staging environment. You can use the same guides for provisioning and installing your staging instance as you did for your production instance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." 3. Restore your backup onto your staging instance. For more information, see the "Restoring a backup" section of "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Дополнительная литература + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..8cfbb127b4473 --- /dev/null +++ b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### Дополнительная литература + +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository diff --git a/translations/ru-RU/content/admin/overview/index.md b/translations/ru-RU/content/admin/overview/index.md index 3b8fee8b8cdb3..bc184ca3e3327 100644 --- a/translations/ru-RU/content/admin/overview/index.md +++ b/translations/ru-RU/content/admin/overview/index.md @@ -15,5 +15,6 @@ For more information, or to purchase {% data variables.product.prodname_enterpri {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..0a418fe44fd68 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. For more information, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**. ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| Source | Destination | Port | Тип | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### Дальнейшие шаги + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ru-RU/content/admin/packages/enabling-github-packages-with-aws.md b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..e72f2f8c8b650 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnings:** +- It is critical that you configure any restrictive access policies you need 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 to 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 %} + +### Требования + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the S3 endpoint URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the S3 bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for S3. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for S3. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for S3. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Дальнейшие шаги + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..9b0785ebd17c9 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**Warnings:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} + +### Требования + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### Дальнейшие шаги + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ru-RU/content/admin/packages/enabling-github-packages-with-minio.md b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..dd16eed61d304 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**Warnings:** +- It is critical that you set the restrictive access policies you need 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. +- 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 %} +### Требования +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### Дальнейшие шаги + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..46a402df723f4 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`. + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." diff --git a/translations/ru-RU/content/admin/packages/index.md b/translations/ru-RU/content/admin/packages/index.md index f73f907259955..9808ef3fde913 100644 --- a/translations/ru-RU/content/admin/packages/index.md +++ b/translations/ru-RU/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..027b73f5fe973 --- /dev/null +++ b/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your third-party storage solution. + +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. + +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). + +### 1. Choose a MinIO mode for your needs + +| MinIO mode | Optimized for | Storage infrastructure required | +| ----------------------------------------------- | ------------------------------ | ------------------------------------ | +| Standalone MinIO (on a single host) | Fast setup | Нет | +| MinIO as a NAS gateway | NAS (Network-attached storage) | NAS devices | +| Clustered MinIO (also called Distributed MinIO) | Data security | Storage servers running in a cluster | + +For more information about your options, see the official [MinIO docs](https://docs.min.io/). + +### 2. Install, run, and sign in to MinIO + +1. Set up your preferred environment variables for MinIO. + + These examples use `MINIO_DIR`: + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. Install MinIO. + + ```shell + $ docker pull minio/minio + ``` + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." + +3. Sign in to MinIO using your MinIO access key and secret. + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + You can access your MinIO keys using the environment variables: + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. Run MinIO in your chosen mode. + + * Run MinIO using Docker on a single host: + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." + + * Run MinIO using Docker as a NAS gateway: + + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + For more information, see "[MinIO Gateway for NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)." + + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + +### 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} + +1. Install the MinIO client. + + ```shell + $ docker pull minio/mc + ``` + +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. + + * Local deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + This example can be used for MinIO standalone or MinIO as a NAS gateway. + + * Clustered deployments example: + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### Дальнейшие шаги + +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/ru-RU/content/admin/user-management/audited-actions.md b/translations/ru-RU/content/admin/user-management/audited-actions.md index 76a8ffbf10ef2..d49ce13fdc331 100644 --- a/translations/ru-RU/content/admin/user-management/audited-actions.md +++ b/translations/ru-RU/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### Teams -| Name | Description | -| --------------:| ----------------------------------------------------- | -| `team.create` | A user account or repository was added to a team. | -| `team.delete` | A user account or repository was removed from a team. | -| `team.destroy` | A team was deleted. | +| Name | Description | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | A user account or repository was added to a team. | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### Users -| Name | Description | -| ---------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | An email address was added to a user account. | -| `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` | A new user account was created. | -| `user.delete` | A user account was destroyed by an asynchronous job. | -| `user.demote` | A site admin was demoted to an ordinary user account. | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | A user tried to sign in with an incorrect username, password, or two-factor authentication code. | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | A user signed in. | -| `user.promote` | An ordinary user account was promoted to a site admin. | -| `user.remove_email` | An email address was removed from a user account. | -| `user.rename` | A username was changed. | -| `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` | A user account was unsuspended by a site admin. | +| Name | Description | +| -------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | An email address was added to a user account. | +| `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` | A new user account was created. | +| `user.delete` | A user account was destroyed by an asynchronous job. | +| `user.demote` | A site admin was demoted to an ordinary user account. | +| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | A user tried to sign in with an incorrect username, password, or two-factor authentication code. | +| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} +| `user.login` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `user.promote` | An ordinary user account was promoted to a site admin. | +| `user.remove_email` | An email address was removed from a user account. | +| `user.rename` | A username was changed. | +| `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` | A user account was unsuspended by a site admin. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [deploy key]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 984feddd818d7..2941a377b4dd5 100644 --- a/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,13 +4,18 @@ 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: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ You can use Markdown to format your message. For more information, see "[About w {% endnote %} +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." + ### Creating a custom sign in message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Under "Sign in page", click **Add message** or **Edit message**. ![Edit message button](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Under **Sign in message**, type the message you'd like users to see. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. Review the rendered message. ![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### Creating a custom sign out message @@ -37,12 +45,35 @@ You can use Markdown to format your message. For more information, see "[About w {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Under "Sign out page", click **Add message** or **Edit message**. ![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Under **Sign out message**, type the message you'd like users to see. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. Review the rendered message. ![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Add message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Add message button](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Creating a global announcement banner @@ -50,9 +81,8 @@ You can use Markdown to format your message. For more information, see "[About w You can set a global announcement banner to be displayed to all users at the top of every page. {% 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)." - +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)." {% else %} You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." @@ -62,9 +92,8 @@ You can also set an announcement banner in the administrative shell using a comm {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. Under "Announcement", click **Add announcement**. ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", use the calendar drop-down menu, and select an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. Optionally, to see what the banner will look like, click **Preview**. ![Preview button](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Click **Save changes**. ![Save changes button](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md b/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md index 2ac221d7dcb90..00001c4ef54c4 100644 --- a/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ Exchange this `code` for an access token: ##### Parameters -| Name | Тип | Description | -| --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `строка` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `client_secret` | `строка` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. | -| `код` | `строка` | **Required.** The code you received as a response to Step 1. | -| `redirect_uri` | `строка` | The URL in your application where users are sent after authorization. | -| `state` | `строка` | The unguessable random string you provided in Step 1. | +| Name | Тип | Description | +| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `строка` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `строка` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. | +| `код` | `строка` | **Required.** The code you received as a response to Step 1. | +| `redirect_uri` | `строка` | The URL in your application where users are sent after authorization. | +| `state` | `строка` | The unguessable random string you provided in Step 1. | ##### Response @@ -213,7 +213,7 @@ Once the user has authorized, the app will receive an access token that can be u #### Rate limits for the device flow -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). diff --git a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 1b0011c690dcf..d2bbcdffea668 100644 --- a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ A CI server hosts code that runs CI tests such as code linters (which check styl The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab. -A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[Enabling required status checks](/articles/enabling-required-status-checks/)" for more details. +A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works: diff --git a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md index bc626b0025ffb..c3f2da625e410 100644 --- a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Available scopes -| Name | Description | -| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | -|  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | -|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | +| **`repo`** | 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](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | +|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | |  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | Grants:
          read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
          read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | -|  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | -|  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | -| **`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. | -| **`notification (Оповещения)`** | 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. | -| **`пользователь`** | 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. | +|  `security_events` | Grants:
          read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
          read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
          This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% 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. | +| **`notification (Оповещения)`** | 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. | +| **`пользователь`** | 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)". | +| **`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. | +| **`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" %} | **`рабочий процесс`** | 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 %} diff --git a/translations/ru-RU/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/ru-RU/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 15ede21ee3044..592796f7b2f9c 100644 --- a/translations/ru-RU/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/ru-RU/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Viewing transactions for your listing -intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transations 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.' +intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index e72ff05c12899..e2a803f7792a1 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ You can archive a classroom that you no longer use on {% data variables.product. {% data reusables.classroom.click-settings %} 1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **Read the warnings**. -1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md index b792b6c4a3ba0..359935372b7b1 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -43,3 +43,7 @@ You can configure version updates for repositories that contain a dependency man {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." + +### About notifications for {% data variables.product.prodname_dependabot %} version updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." diff --git a/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md index 02d653158a2fa..d8928317a6d96 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### Squashing your merge commits diff --git a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md index b6eec6faa9e3e..c235c019e67e9 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,142 @@ --- title: About protected branches -intro: 'Protected branches ensure that collaborators on your repository cannot make irrevocable changes to branches. Enabling protected branches also allows you to enable other optional checks and requirements, like required status checks and required reviews.' +intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### About protected branches +### About branch protection rules -{% data reusables.pull_requests.about-protected-branches %} You can choose to enforce restrictions on how a pull request is merged into your repository. +You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. -Repository owners and people with admin permissions for a repository can enforce certain workflows or requirements, before a collaborator can merge a branch in your repository by creating protected branch rules. +By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings. -{% data reusables.repositories.branch-rules-example %} For more information, see "[Configuring protected branches](/articles/configuring-protected-branches/)." +By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too. + +{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." {% data reusables.pull_requests.you-can-auto-merge %} -### Prioritization of protected branch rules +### About branch protection settings + +For each branch protection rule, you can choose to enable or disable the following settings. +- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) +- [Require status checks before merging](#require-status-checks-before-merging) +- [Require signed commits](#require-signed-commits) +- [Require linear history](#require-linear-history) +- [Include administrators](#include-administrators) +- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches) +- [Allow force pushes](#allow-force-pushes) +- [Allow deletions](#allow-deletions) + +#### Require pull request reviews before merging + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions. + +If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review. + +{% data reusables.repositories.review-policy-overlapping-commits %} + +If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/articles/about-pull-requests)." + +Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/articles/dismissing-a-pull-request-review)." + +Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch. + +#### Require status checks before merging + +Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." + +Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. + +After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. + +{% note %} + +**Note:** Any person or integration with write permissions to a repository can set the state of any status check in the repository. {% data variables.product.company_short %} does not verify that the author of a check is authorized to create a check with a certain name or modify an existing status. Before merging a pull request, you should verify that the author of each status, listed in the merge box, is expected. + +{% endnote %} + +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. + +| Type of required status check | Setting | Merge requirements | Considerations | +| ----------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Strict** | The **Require branches to be up-to-date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | +| **Loose** | The **Require branches to be up-to-date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. | + +For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." + +#### Require signed commits + +When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)." + +{% note %} + +**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. + +{% endnote %} + +You can always push local commits to the branch if the commits are signed and verified. {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)." + +{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} + +#### Require linear history + +Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." + +Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)." + +#### Include administrators + +By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules. + +#### Restrict who can push to matching branches + +{% if currentVersion == "free-pro-team@latest" %} +You can enable branch restrictions if your repository is owned by an organization using +{% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. + +You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch. + +#### Allow force pushes -If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. +By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. -Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. +Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -### Branch protection settings +{% 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. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." -When you create a branch protection rule in a repository, collaborators cannot force push to the protected branch or delete the branch{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}. You can enable other branch protection settings. For information, see "[Defining the mergeability of pull requests](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)." +If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} -### Дополнительная литература +#### Allow deletions -- "[About required status checks](/articles/about-required-status-checks)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[About required commit signing](/articles/about-required-commit-signing)" +By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. diff --git a/translations/ru-RU/content/github/administering-a-repository/about-releases.md b/translations/ru-RU/content/github/administering-a-repository/about-releases.md index 194786ffab413..2ac0b5314e070 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-releases.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-releases.md @@ -25,7 +25,7 @@ You can receive notifications when new releases are published in a repository wi Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md b/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md index 78fdf8996cddf..ad935ba6123b6 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project. +Service providers can partner with -If someone checks a secret from a {% data variables.product.company_short %} partner into a public or private repository, {% data variables.product.prodname_secret_scanning %} can detect the secret and help you mitigate the impact of the leak. +{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% endif %} -Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. For more information, see "[Secret scanning](/partnerships/secret-scanning)." +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### About {% data variables.product.prodname_secret_scanning %} for public repositories - {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)." +{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. -When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets. - -When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. +When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." {% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### About {% data variables.product.prodname_secret_scanning %} for private repositories +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for private repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization. {% data variables.product.prodname_secret_scanning_caps %} is not available for user account-owned private repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. +{% endif %} -When you push commits to a private repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.product_name %} scans the contents of the commits for secrets. +If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." -When {% data variables.product.prodname_secret_scanning %} detects a secret in a private repository, {% data variables.product.prodname_dotcom %} sends alerts. +When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. + +When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. - {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. - {% data variables.product.prodname_dotcom %} displays an alert in the repository. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." - -To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." - -{% data variables.product.product_name %} currently scans private repositories for secrets issued by the following service providers. - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +To monitor results from +{% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %} + +{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} diff --git a/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md index 2718b4c036643..3ff44718d7dbd 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md @@ -3,6 +3,7 @@ title: About securing your repository intro: '{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Setting up your repository securely @@ -13,6 +14,7 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +{% if currentVersion == "free-pro-team@latest" %} - **Security policy** Make it easy for people to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)." @@ -24,18 +26,32 @@ The first step to securing a repository is to set up who can see and modify your - **{% data variables.product.prodname_dependabot_alerts %} and security updates** View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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)." + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **{% data variables.product.prodname_dependabot %} version updates** +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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." + {% endif %} - 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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** +View any secrets that - View any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + {% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: diff --git a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md index f49ec66d59265..998ba16e7acce 100644 --- a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..664c05919850f --- /dev/null +++ b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: Configuring secret scanning for your repositories +intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' +permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. + +{% endnote %} +{% endif %} + +### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. When you enable +{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. To the right of " +{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories + +You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type *.github/secret_scanning.yml*. +4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}. + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)." + + {% note %} + + **Замечания:** + - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans. + - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file. + + {% endnote %} + +You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)." + +### Дополнительная литература + +- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ru-RU/content/github/administering-a-repository/index.md b/translations/ru-RU/content/github/administering-a-repository/index.md index 1f27602bae779..5ed179703c13c 100644 --- a/translations/ru-RU/content/github/administering-a-repository/index.md +++ b/translations/ru-RU/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..0e16b4b0291a5 --- /dev/null +++ b/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: Managing a branch protection rule +intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with admin permissions to a repository can manage branch protection rules. +--- + +### About branch protection rules + +{% data reusables.repositories.branch-rules-example %} + +You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). + +If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority. + +Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority. + +To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name. + +For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." + +### Creating a branch protection rule + +When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. Optionally, enable required pull request reviews. + - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png) + - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png) + - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)." ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) +1. Optionally, enable required status checks. + - Select **Require status checks to pass before merging**. ![Required status checks option](/assets/images/help/repository/required-status-checks.png) + - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png) + - From the list of available status checks, select the checks you want to require. ![List of available status checks](/assets/images/help/repository/required-statuses-list.png) +1. Optionally, select **Require signed commits**. ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png) +1. Optionally, select **Require linear history**. ![Required linear history option](/assets/images/help/repository/required-linear-history.png) +1. Optionally, select **Include administrators**. ![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png) +1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions. + - Select **Restrict who can push to matching branches**. ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png) + - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png) +1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) +1. Optionally, select **Allow deletions**. ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png) +1. Click **Create**. + +### Editing a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to edit, click **Edit**. ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png) +1. Make your desired changes to the branch protection rule. +1. Click **Save changes**. ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png) + +### Deleting a branch protection rule + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. To the right of the branch protection rule you want to delete, click **Delete**. ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png) 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 9127ad2090f05..929577a15328e 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 @@ -4,6 +4,7 @@ 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: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. In the left sidebar, click **Detected secrets**. !["Detected secrets" tab](/assets/images/help/repository/sidebar-secrets.png) -4. Under "Secret scanning" click the alert you want to view. ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Optionally, use the "Resolve" drop-down menu and click a reason for resolving an alert. ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. Under "Secret scanning" click the alert you want to view. + {% if currentVersion == "free-pro-team@latest" %} + ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. + {% if currentVersion == "free-pro-team@latest" %} + ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### Securing compromised secrets Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets: - For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old 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)." -- For all other secrets, first verify that the secret committed to {% data variables.product.prodname_dotcom %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. +- For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index 957b83f2df9a9..95e2c23fe462a 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -5,7 +5,7 @@ intro: 'You can choose whether {% data variables.large_files.product_name_long % permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ versions: {% data variables.product.product_name %} creates source code archives of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. -{% if currentVersion != "github-ae@latest" %} +{% if currentVersion == "free-pro-team@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. Each account receives {% data variables.large_files.initial_bandwidth_quota %} per month of bandwidth for free, and you can pay for additional usage. For more information, see "[About storage and bandwidth usage](/github/managing-large-files/about-storage-and-bandwidth-usage)" and "[Managing billing for {% 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 %} diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md index 726a264da3980..5428288a847e7 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### About release management diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index c8d4a41ef911e..1a157fd60dfdf 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### Enabling or disabling security and analysis features +{% if currentVersion == "free-pro-team@latest" %} +### Enabling or disabling security and analysis features for public repositories -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} + +You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. +{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### Granting access to security alerts @@ -35,7 +53,13 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. + {% if currentVersion == "free-pro-team@latest" %} + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. Click **Save changes**. !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### Removing access to security alerts @@ -43,7 +67,14 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0748625b6b036 --- /dev/null +++ b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: Renaming a branch +intro: You can change the name of a branch in a repository. +permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch. +versions: + free-pro-team: '*' +--- + +### About renaming branches + +You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." + +If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. + +### Renaming a branch + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) diff --git a/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md index 08c5381597c72..9aa53e370b2ed 100644 --- a/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,8 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ We recommend reviewing the following caveats before you change the visibility of #### Making a repository public * {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."{% endif %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} diff --git a/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..d07532b5f4078 --- /dev/null +++ b/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: Troubleshooting required status checks +intro: 'You can check for common errors and resolve issues with required status checks.' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)." + +After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." + +{% note %} + +**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/using-git/about-git-rebase)." + +{% endnote %} + +You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. This can be done without status checks running on the merge commit itself. + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." + +![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md index 2c538aa761393..fb17a727f81bd 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -19,11 +19,13 @@ You can sign commits and tags locally, so other people can verify that your work If a commit or tag has a signature that cannot be verified, {% data variables.product.product_name %} marks the commit or tag as unverified. -Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About required commit signing](/articles/about-required-commit-signing)." +Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)." You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)." -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% endif %} ### GPG commit signature verification diff --git a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md index fb61dd8974f76..eedd393e0badc 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -39,6 +39,7 @@ The events listed in your security log are triggered by your actions. Actions ar | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} | [`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-category-actions) | Contains all activities related to your billing information. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)." | | [`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" %} @@ -82,6 +83,12 @@ An overview of some of the most common actions that are recorded as events in th | `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). | +#### `codespaces` category actions + +| Действие | Description | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### `marketplace_agreement_signature` category actions | Действие | Description | @@ -227,20 +234,20 @@ An overview of some of the most common actions that are recorded as events in th #### `user` category actions -| Действие | 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.{% 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 %} +| Действие | 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 %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% 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 %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `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 @@ -249,4 +256,3 @@ An overview of some of the most common actions that are recorded as events in th | `обновление` | 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. | - diff --git a/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index 36a051b7eb7d1..7cc8ad1aa78bb 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ With SSH keys, if someone gains access to your computer, they also gain access t You can change the passphrase for an existing private key without regenerating the keypair by typing the following command: ```shell -$ ssh-keygen -p -# Start the SSH key creation process -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/ru-RU/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/ru-RU/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index 621faf552a19b..be55c9339c95b 100644 --- a/translations/ru-RU/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/ru-RU/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ If the code of conduct you want to use isn't available in the provided templates 3. In the file name field, type the name and extension for the file. ![New code of conduct file name](/assets/images/help/repository/new-code-of-conduct-file-name.png) - To make your code of conduct visible in the repository's root directory, type *CODE_OF_CONDUCT* in the file name field. - To make your code of conduct visible in the repository's `docs` directory, type *docs/CODE_OF_CONDUCT*. - - To make your code of conduct visible in the respository's `.github` directory, type *.github/CODE_OF_CONDUCT*. + - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. 4. In the new file, add your custom code of conduct. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 4a56f8edddfcc..f75c5ac9836ad 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,7 +74,7 @@ When a branch is protected: - If required status checks are enabled on the branch, you won't be able to merge changes into the branch until all of the required CI tests pass. For more information, see "[About status checks](/articles/about-status-checks)." - If required pull request reviews are enabled on the branch, you won't be able to merge changes into the branch until all requirements in the pull request review policy have been met. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)." - If required review from a code owner is enabled on a branch, and a pull request modifies code that has an owner, a code owner must approve the pull request before it can be merged. For more information, see "[About code owners](/articles/about-code-owners)." -- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. 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" %} +- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. For more information, see "[Resolving a merge conflict on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)."{% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 64279b2fdd80d..1638e45730b79 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,9 +44,7 @@ You can view all of the reviews a pull request has received in the Conversation ### Required reviews -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -For more information, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)." +{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% tip %} @@ -57,6 +55,5 @@ For more information, see "[About required reviews for pull requests](/articles/ ### Дополнительная литература - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Enabling required reviews for pull requests](/articles/enabling-required-reviews-for-pull-requests)" - "[Viewing a pull request review](/articles/viewing-a-pull-request-review)" - "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index d0d540d229350..de51fe92cb445 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -For more information about required reviews, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)." +For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." -You can comment on a pull request, approve the changes, or request improvements before approving. For more information, see "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" and "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." +You can comment on a pull request, approve the changes, or request improvements before approving. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ You can comment on a pull request, approve the changes, or request improvements ### Дополнительная литература -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Commenting on a pull request](/articles/commenting-on-a-pull-request)" diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index d92eee40fdaae..e56a7e8c25c54 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ You can only make commits on pull request branches that: - are opened in a repository that you have push access to and that were created from a fork of that repository - are on a user-owned fork - have permission granted from the pull request creator -- don't have [branch restrictions](/articles/about-branch-restrictions) that will prevent you from committing +- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)." diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index 39938f0e1b581..40fe8f5e73d3a 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Dismissing a pull request review -intro: 'If your repository [requires reviews](/articles/about-required-reviews-for-pull-requests), you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' +intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ This changes the status of the review to a review comment. When you dismiss a re - "[About pull request reviews](/articles/about-pull-request-reviews)" - "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" +- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index e63c5693b9d1b..4c45fc3a8633d 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### Following the GitHub flow 1. [Create a branch](/articles/creating-and-deleting-branches-within-your-repository) from the repository. -2. [Create](/articles/creating-new-files), [edit](/articles/editing-files), [rename](/articles/renaming-a-file), [move](/articles/moving-a-file-to-a-new-location), or [delete](/articles/deleting-files) files. +2. [Create](/articles/creating-new-files), [edit](/articles/editing-files), [rename](/articles/renaming-a-file), [move](/articles/moving-a-file-to-a-new-location), or [delete](/github/managing-files-in-a-repository/deleting-files-in-a-repository) files. 3. [Send a pull request](/articles/creating-a-pull-request) from your branch with your proposed changes to kick off a discussion. 4. Make changes on your branch as needed. Your pull request will update automatically. 5. [Merge the pull request](/articles/merging-a-pull-request) once the branch is ready to be merged. diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 2bf18ecfac073..0621b60adcd19 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### About pull request merges -In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. {% data reusables.pull_requests.about-protected-branches %} However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 308d7f0f335ce..3d042481667c5 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ Dependency review supports the same languages and package management ecosystems ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ Dependency review supports the same languages and package management ecosystems * The severity of the vulnerability. * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. -1. You can return to the original view of the file by clicking the source diff button. - - ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 9df09823e9ab8..ad1cb23689fdf 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,9 +36,11 @@ If the pull request contains changes to dependencies you can use the dependency {% data reusables.repositories.changed-files %} -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### Marking a file as viewed @@ -65,5 +67,5 @@ After you've finished reviewing all the files you want in the pull request, subm ### Дополнительная литература -- "[About required reviews for pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 2dd387129ada3..373d799ceb474 100644 --- a/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/ru-RU/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ Organization's can use the `name@organization.com` email as a public point of co ### Creating commits with an `on-behalf-of` badge on the command line -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. + + {% endtip %} 2. On the next line of the commit message, type `on-behalf-of: @org `, then a closing quotation mark. 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 921afd3c0eea4..0b184b1b067c4 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 @@ -39,7 +39,17 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer. + + {% endtip %} 3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 9c16a5ffd45ef..5fd954aedf467 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -19,7 +19,7 @@ The people you choose as code owners must have write permissions for the reposit Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)." -When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[Enabling required reviews for pull requests](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)." +When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." {% 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. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index 08a397f1d341a..88b7c828332c2 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ Each person and organization can own unlimited repositories and invite an unlimi {% endif %} You can use repositories to manage your work and collaborate with others. -- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." -- {% data reusables.discussions.you-can-use-discussions %} +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." - You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 8321b47291e27..8d8e09ab5b4a3 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ When you search by a family license, your results will include all licenses in t ### Detecting a license -[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/ru-RU/content/github/developing-online-with-codespaces/about-codespaces.md index 6c0e0d29f1231..2413aeac6d416 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ Each developer can create one or more codespace for any public repository, or fo {% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." +You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/index.md b/translations/ru-RU/content/github/developing-online-with-codespaces/index.md index d53f3e92fbc89..1ec4ada1215cd 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/index.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..51a8db1372fa6 --- /dev/null +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Click **Add secret**. + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Click **Save changes**. + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/ru-RU/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index 16bff0f06fdba..c9754fb2d1ed9 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ For more information, see [Personalizing](https://docs.microsoft.com/visualstudi {% endnote %} +You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." ### Дополнительная литература diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index cb09e6bdecd6e..20afd7d49b833 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ You can use {% data variables.product.prodname_code_scanning %} to find, triage, If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." @@ -54,7 +54,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam ### Дополнительная литература -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[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 diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 75ca962666587..ba9b492ab9d54 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -236,7 +236,9 @@ 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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +The settings in the file are written in YAML format. #### Specifying additional queries 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 b62aafb4534d3..5ef2ac5f5adc8 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 @@ -40,13 +40,16 @@ You decide how you generate {% data variables.product.prodname_code_scanning %} 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. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +### Bulk enabling {% data variables.product.prodname_code_scanning %} +You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + ### Дальнейшие шаги 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'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 39f1264f5e8c7..4bccd25f77fc0 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ You can use the {% data variables.product.prodname_codeql_runner %} to run {% da The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**Замечания:** +{% if currentVersion == "free-pro-team@latest" %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% else %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{% endnote %} ### Downloading the {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi ### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux In addition to this, each CI server also needs: -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." +- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: 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 721b4060208d5..b2eded39f15cb 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 @@ -15,7 +15,7 @@ versions: In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the 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. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository 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)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. For more information, see "[About required status checks](/github/administering-a-repository/about-required-status-checks)." +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index 05cc0e7610ba4..9f9f6427bb61b 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### The `init` command takes too long 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 43c891b98ffaf..d9f4af97edf41 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Automatic build for a compiled language fails @@ -83,17 +84,6 @@ For more information about specifying build steps, see "[Configuring the {% data The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. 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)." -### Error: "Server error" - -If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. - -### Error: "Out of disk" or "Out of memory" -On very large projects, - -{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - ### The build takes too long If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. @@ -128,3 +118,54 @@ If you are analyzing code written in Python, you may see different results depen On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." {% endif %} + +### Error: "Server error" + +If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. + +### Error: "Out of disk" or "Out of memory" +On very large projects, + +{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 0703c0a8239c6..65f590f3d9f80 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -27,6 +27,8 @@ You can upload the results using {% data variables.product.prodname_actions %}{% - The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, 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)"). - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)"). +{% data reusables.code-scanning.not-available %} + ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %} To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..b923b08a6cfd9 --- /dev/null +++ b/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### About {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)." + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md b/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md index c1233faf10abb..a3686af2fad08 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: GitHub for mobile -intro: 'Triage, collaborate, and manage your work on {% data variables.product.company_short %} from your mobile device.' +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### About {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} is currently available for {% data variables.product.prodname_dotcom_the_website %} users as an Android and iOS app. +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.prodname_dotcom %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.prodname_dotcom %} data through a trusted, first-party client application. +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. With {% data variables.product.prodname_mobile %} you can: - Manage, triage, and clear notifications @@ -23,12 +26,38 @@ For more information about notifications for {% data variables.product.prodname_ To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +### Managing accounts + +You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + +{% data reusables.mobile.push-notifications-on-ghes %} + +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. + +#### Требования + +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." + +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}. + +#### Adding, switching, or signing out of accounts + +You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. + +After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. + +If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. + ### Supported languages for {% data variables.product.prodname_mobile %} {% data variables.product.prodname_mobile %} is available in the following languages. +- Английский - Японский - Brazilian Portuguese +- Simplified Chinese - Испанский If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. @@ -37,9 +66,9 @@ If you configure the language on your device to a supported language, {% data va {% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. -To disable Universal Links, long-press any {% data variables.product.prodname_dotcom %} link, then tap **Open**. Every time you tap a {% data variables.product.prodname_dotcom %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -To re-enable Universal Links, long-press any {% data variables.product.prodname_dotcom %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. ### Sharing feedback diff --git a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md index 3735db6d8132a..becafddba7efd 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: GitHub's products +intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ For more information about hosting your own instance of [{% data variables.produ - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} - [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations) -For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact [{% data variables.product.product_name %}'s Sales team](https://enterprise.github.com/contact). +For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ru-RU/content/github/getting-started-with-github/index.md b/translations/ru-RU/content/github/getting-started-with-github/index.md index c8b857b90edf4..d5970dd910b3e 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/index.md +++ b/translations/ru-RU/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md index 103e1e49c9534..d643b718b876e 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -29,14 +29,14 @@ Below is a list of some of the available keyboard shortcuts. ### Repositories -| Keyboard shortcut | Description | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Go to the **Code** tab | -| g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." | -| g p | Go to the **Pull requests** tab. 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" %} +| Keyboard shortcut | Description | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | Go to the **Code** tab | +| g i | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)." | +| g p | Go to the **Pull requests** tab. 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" %} | g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} -| g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." | -| g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." | +| g b | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)." | +| g w | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)." | ### Source code editing @@ -159,6 +159,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description | | --------------------------------------------------------- | --------------------------------------------------------------- | | command + space or control + space | In the workflow editor, get suggestions for your workflow file. | +| g f | Go to the workflow file | +| shift + t or T | Toggle timestamps in logs | +| shift + f or F | Toggle fullscreen logs | +| esc | Exit fullscreen logs | {% endif %} diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..33a59c439b213 --- /dev/null +++ b/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. For more information, see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)." + +### Deleting a file + +1. Browse to the file in your repository that you want to delete. +2. At the top of the file, click +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md index d1765daf5e40a..faf07b3fb4585 100644 --- a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md +++ b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index 871ca7b29bf8e..f98e0eb12198d 100644 --- a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ You can link to a particular row by clicking the row number, or select multiple ### Searching data -If you want to find a certain value in your dataset, you can start typing in the search bar directly above the file. The rows will filter automagically: +If you want to find a certain value in your dataset, you can start typing in the search bar directly above the file. The rows will filter automatically: ![Searching for values](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/ru-RU/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/ru-RU/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 3535b453221aa..cfbef3ac8f724 100644 --- a/translations/ru-RU/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/ru-RU/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ When you commit and push a change to a file tracked with {% data variables.large - If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth. - If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ru-RU/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/ru-RU/content/github/managing-large-files/configuring-git-large-file-storage.md index 1cc370db949ff..bd64809cf51e7 100644 --- a/translations/ru-RU/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/ru-RU/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ If there are existing files in your repository that you'd like to use {% data va ### Дополнительная литература -- "[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" %} +- "[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@3.0" or currentVersion == "github-ae@latest" %} - "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index 3a25827652c2d..b06586d60b5a4 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -33,3 +33,7 @@ When you merge a pull request that contains a security update, the corresponding ### About compatibility scores {% 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. + +### About notifications for {% data variables.product.prodname_dependabot %} security updates + +You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." \ No newline at end of file diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index b4ebdcfa9faae..5754f956058b2 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -42,16 +42,18 @@ If security updates are not enabled for your repository and you don't know why, ### Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories -You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository. +You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} 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)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." +#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Above the list of alerts, use the drop-down menu and select or unselect **{% data variables.product.prodname_dependabot %} security updates**. ![Drop-down menu with the option to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["Configure security and analysis features" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### Дополнительная литература diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index a1001d67e4bc4..0b0c3973f4027 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ You can configure notification settings for yourself or your organization from t {% note %} -**Note:** You can filter your {% data variables.product.company_short %} inbox notifications to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)." +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." {% endnote %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index dd179ef0df0c7..c6d6ca09fe44a 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,13 +78,15 @@ The best way to resolve this error is to merge or close some of the existing pul #### {% data variables.product.prodname_dependabot %} can't resolve your dependency files -**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". +If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." +To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. + +**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a 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**. +- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**. diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 3c15a48c54317..27b9df7ff82ad 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notifications and subscriptions You can choose to receive ongoing updates about specific activity on {% data variables.product.product_name %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to. @@ -50,7 +54,7 @@ To unsubscribe from conversations you're automatically subscribed to, you can ch ### Customizing notifications and subscriptions -You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see “[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).” @@ -58,7 +62,7 @@ To keep your subscriptions manageable, review your subscriptions and watched rep To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see “[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).” -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} You can enable push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." {% endif %} @@ -89,7 +93,7 @@ From your inbox you can also triage multiple notifications at once. For more inf ### Customizing your notifications inbox -To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." ### Notification retention policy diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index c2e7cb92cba80..0ca44a070d093 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notification delivery options You can receive notifications for activity on {% data variables.product.product_name %} in the following locations. - - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" %} + - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." {% endif %} @@ -35,7 +39,7 @@ You can receive notifications for activity on {% data variables.product.product_ #### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: +The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - Triage multiple notifications at once. - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. @@ -45,7 +49,7 @@ The notifications inbox on {% data variables.product.product_name %}{% if curren - Create custom filters to focus on different notifications when you want. - Group notifications in your inbox by repository or date to get a quick overview with less context switching -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} In addition, the notifications inbox on {% data variables.product.prodname_mobile %} allows you to triage notifications in dark mode and receive push notifications for direct mentions. For more information, see "[Enabling push notifications with GitHub for mobile](#enabling-push-notifications-with-github-for-mobile)" or "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." {% endif %} @@ -77,7 +81,7 @@ You can customize notifications for a repository, for example, you can choose to #### Participating in conversations Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox. -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %}. +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. ![Participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -85,7 +89,7 @@ For conversations you're watching or participating in, you can choose whether yo - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications. - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating". -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}, then your notifications inbox will not have any updates. +If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. ### Customizing your email notifications @@ -197,13 +201,15 @@ Choose how you want to receive workflow run updates for repositories that you ar {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Enabling push notifications with {% data variables.product.prodname_mobile %} When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. You can then enable push notifications for direct mentions within the app. You can only receive notifications for pushes to repositories on {% data variables.product.prodname_mobile %} at this time. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Enabling push notifications with {% data variables.product.prodname_ios %} 1. Above "Home", tap your profile photo. @@ -211,9 +217,11 @@ You can only receive notifications for pushes to repositories on {% data variabl 3. To update your notification settings, tap **Push notifications**. 4. To turn on push notifications for direct mentions, use the **Direct Mentions** toggle. +{% if currentVersion == "free-pro-team@latest" %} #### Enabling push notifications with {% data variables.product.prodname_android %} 1. Above "Home", tap your profile photo. 2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. ![Settings icon for GitHub for Android](/assets/images/help/mobile/android-settings-icon.png) 3. To turn on push notifications for direct mentions, use the **Direct mentions** toggle. {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 08fe0842d6164..4c97948c43426 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: Managing notifications from your inbox -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}.' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### About your inbox -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} @@ -86,31 +90,16 @@ Custom filters do not currently support: ### Supported queries for custom filters -There are three types of filters that you can use: +These are the types of filters that you can use: - Filter by repository with `repo:` - Filter by discussion type with `is:` - - Filter by notification reason with `reason:` - -To add a `repo:` filter, you must include the owner of the repository in the query. For example, `repo:atom/atom` represents the Atom repository owned by the Atom organization. + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -#### Supported `reason:` queries +#### Supported `repo:` queries -To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." - -| Query | Description | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. | -| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. | -| `reason:comment` | When you commented on an issue, pull request, or team discussion. | -| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. | -| `reason:invitation` | When you're invited to a team, organization, or repository. | -| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | -| `reason:mention` | You were directly @mentioned. | -| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | -| `reason:team-mention` | When a team you're a member of is @mentioned. | -| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. | +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. #### Supported `is:` queries @@ -138,3 +127,59 @@ You can also use the `is:` query to describe how the notification was triaged. - `is:done` - `is:unread` - `is:read` + +#### Supported `reason:` queries + +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." + +| Query | Description | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. | +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. | +| `reason:comment` | When you commented on an issue, pull request, or team discussion. | +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. | +| `reason:invitation` | When you're invited to a team, organization, or repository. | +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | +| `reason:mention` | You were directly @mentioned. | +| `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:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | +| `reason:team-mention` | When a team you're a member of is @mentioned. | +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. | + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. + +#### Supported `org:` queries + +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use +{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +For more information about + +{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} + +{% endif %} diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 66278fee44646..7c9b4621a13af 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ When you unsubscribe from notifications in your inbox, they will automatically d {% data reusables.notifications.access_notifications %} 1. From the notifications inbox, select the notifications you want to unsubscribe to. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubcribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Unsubscribing from notifications on the subscriptions page @@ -64,4 +64,4 @@ When you unwatch a repository, you unsubscribe from future updates from that rep - unwatch a repository - ignore all notifications for a repository - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md b/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md index 144b772e0fba3..d4b8099ea1f10 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md @@ -14,9 +14,11 @@ versions: You can collect user feedback, report software bugs, and organize tasks you'd like to accomplish with issues in a repository. Issues can act as more than just a place to report software bugs. +{% if currentVersion == "free-pro-team@latest" %} Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md index bbe7533159b35..2800bfde73f51 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Changing project board visibility -intro: 'As an organization owner or project board admin, you can make a project board public or private.' +intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**Tip:** When you make your project board public, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} -1. Navigate to the project board you want to make public or private. +1. Navigate to the project board you want to make + +{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. Under "Visibility", select **Public** or **Private**. Then, click **Save**. ![Public and private radio buttons](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. Click **Save**. diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md index f1dd5e244212f..98b0314ce833c 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ A project board's automation is also enabled by default. For more information, s 5. Optionally, under "Project board name", type the name of the copied project board. ![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png) 6. Optionally, under "Description", type a description of the copied project board that other people will see. ![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png) 7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)." ![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. If you are copying an organization-owned project board, under "Visibility", select whether you want your copied project board to be private or public. ![Select visibility settings for copied project board](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. Click **Copy project**. ![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/ru-RU/content/github/managing-your-work-on-github/creating-a-project-board.md index 818f69d796966..29ee3eec75793 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/ru-RU/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 3c58fb4bf600e..bd23443a9b8f2 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: You can filter a repository's list of pull requests to find: - Pull requests that haven't been [reviewed](/articles/about-pull-request-reviews) yet -- Pull requests that [require a review](/articles/about-required-reviews-for-pull-requests) before they can be merged +- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged - Pull requests that a reviewer has approved - Pull requests in which a reviewer has asked for changes - Pull requests that you have reviewed diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md index 332071d1f5a5f..234e353753bf4 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize issues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. -Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository. +Anyone with read access to a repository can view and search the repository’s labels. Anyone with triage access to a repository can apply/dismiss existing labels. To create, edit, apply, or delete a label, you must have write access to the repository. ### About default labels @@ -91,7 +91,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### Дополнительная литература -- "[About labels](/articles/about-labels)" - "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index e1d6c5d4dbc99..e16fc45bcebc4 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -36,7 +36,7 @@ For issues, you can also use search to: For pull requests, you can also use search to: - Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft` - Filter pull requests that haven't been [reviewed](/articles/about-pull-request-reviews) yet: `state:open type:pr review:none` -- Filter pull requests that [require a review](/articles/about-required-reviews-for-pull-requests) before they can be merged: `state:open type:pr review:required` +- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required` - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` - Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-commits.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-commits.md index 8bbb3acb16229..1bfb8103cbb9e 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-commits.md @@ -51,7 +51,7 @@ Use the `author-date` and `committer-date` qualifiers to match commits authored | Qualifier | Пример | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) matches commits committed after 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | ### Filter merge commits diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 62fde838c0090..e661e51a2ffe4 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: After you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. When a member accesses resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}, where the member can access your organization's resources. -Enterprise owners can also enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ If members are signed in with a SAML SSO session when they create a new reposito Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. +{% data reusables.saml.saml-single-logout-not-supported %} + ### Supported SAML services {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ Some IdPs support provisioning access to a {% data variables.product.prodname_d After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." -{% data reusables.organizations.team-synchronization %} - To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization. If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index adc17332afe21..63344922ca0ed 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ These identity providers are compatible with the {% data variables.product.produ - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index adf67062b63fa..a63e3238f8609 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ For each pending collaborator, you can cancel all invitations to join organizati {% data reusables.organizations.people_tab_outside_collaborators %} 5. Click **X pending collaborators**. !["Pending collaborators" button](/assets/images/help/organizations/pending-collaborator-list.png) 6. To the right of the person you want to cancel invitations for, click **Cancel invitations**. !["Cancel invitation" button](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Click **Cancel invitations for pending collaborators**. ![Button to confirm cancelation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. Click **Cancel invitations for pending collaborators**. ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md index d1c440e8c5762..a3ee6b1216a88 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index c69629d63779c..0107a236ecefc 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Managing security and analysis settings for your organization intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.' permissions: Organization owners can manage security and analysis settings for repositories in the organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### About management of security and analysis settings -{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. +{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% if currentVersion == "free-pro-team@latest" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. + +![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Enabling or disabling a feature for all existing repositories +You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: + +- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories. +- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories. +- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -### Enabling or disabling a feature for all new repositories when they are added +### Enabling or disabling a feature automatically when new repositories are added 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories +{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. + {% if currentVersion == "free-pro-team@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Allowing Dependabot to access private repositories -{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." 1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) 1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. 1. Click **Select repositories**. - +{% endif %} ### Дополнительная литература -{% if currentVersion == "free-pro-team@latest" %}- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)" -- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} +- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" +- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" - "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index 1e3cd0929567e..52b371374e12a 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ For example, if an organization owner has given all organization members read pe ### Project board visibility -{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to public and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." +{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." ### Дополнительная литература 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 96c038aaae114..1fcbaea87e9bd 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,91 +43,94 @@ 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** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %}{% if currentVersion == "free-pro-team@latest" %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 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/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} +| 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#granting-access-to-security-alerts) 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** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (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)") | | | | | **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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 7f8fbaceef07c..e43cb2c7d5291 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -64,8 +64,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`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-category-actions) | Contains all activities related to teams in your organization.{% endif %} +| [`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 %} +| [`команда`](#team-category-actions) | Contains all activities related to teams in your organization. | | [`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. Например: @@ -198,7 +198,7 @@ An overview of some of the most common actions that are recorded as events in th | Действие | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `отключить` | 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)." | -| `включить` | Triggered when an organization owner enbles {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | +| `включить` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | #### `dependabot_security_updates` category actions @@ -325,6 +325,8 @@ For more information, see "[Restricting publication of {% data variables.product | Действие | Description | | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." | +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. | | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). | | `cancel_invitation` | Triggered when an organization invitation has been revoked. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} @@ -448,15 +450,17 @@ For more information, see "[Restricting publication of {% data variables.product #### `repo` category actions -| Действие | Description | -| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | -| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). | -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. | +| Действие | Description | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). | +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." | +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `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).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} @@ -465,12 +469,12 @@ For more information, see "[Restricting publication of {% data variables.product | `включить` | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.{% endif %} | `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} -| `remove_topic` | Triggered when a repository admin removes a topic from a repository. | -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). | -| `передача` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). | -| `transfer_start` | Triggered when a repository transfer is about to occur. | +| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `remove_topic` | Triggered when a repository admin removes a topic from a repository. | +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). | +| `передача` | 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 admin unarchives a repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret.{% endif %} @@ -560,7 +564,7 @@ For more information, see "[Restricting publication of {% data variables.product | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `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)") | @@ -569,20 +573,18 @@ For more information, see "[Restricting publication of {% data variables.product | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` category actions -| Действие | Description | -| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). | -| `add_repository` | Triggered when a team is given control of a repository. | -| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | -| `change_privacy` | Triggered when a team's privacy level is changed. | -| `create` | Triggered when a new team is created. | -| `destroy` | Triggered when a team 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). | -| `remove_repository` | Triggered when a repository is no longer under a team's control. | -{% endif %} +| Действие | Description | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). | +| `add_repository` | Triggered when a team is given control of a repository. | +| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | +| `change_privacy` | Triggered when a team's privacy level is changed. | +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. #### `team_discussions` category actions diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 2b910f9530409..03846adcbbd3f 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: You can connect up to five IdP groups to a {% data variables.product.prodname_dotcom %} team. An IdP group can be assigned to multiple {% data variables.product.prodname_dotcom %} teams without restriction. +Team synchronization does not support IdP groups with more than 5000 members. + Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %} or using the API. All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." @@ -27,19 +29,22 @@ You can also manage team synchronization with the API. For more information, see ### Requirements for members of synchronized teams -After you connect a team to an IdP group, membership data for each team member will synchronize if the person continues to authenticate using SAML SSO with the same SSO identity on {% data variables.product.prodname_dotcom %}, and if the person remains a member of the connected IdP group. +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: +- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. +- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -Existing teams or group members can be automatically removed from the team on {% data variables.product.prodname_dotcom %}. Any existing teams or group members not authenticating to the organization or enterprise account using SSO may lose access to repositories. Any existing teams or group members not in the connected IdP group may potentially lose access to repositories. +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. -To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." +To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." ### Требования -Before you can connect a team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Before you can connect a team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index a06f75f7acf78..b4b7a1022f343 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ You can view and revoke each member's linked identity, active sessions, and auth {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..f8e9441c103dc --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. + +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..9ffac5db1a019 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. + +For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: + +- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). +- Cancel any existing invitations for the user to join an organization owned by your enterprise account. + +For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: + +- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. + +If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." + +To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index f9bb0cfd2fa8e..6412a4b710789 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ After you enable SCIM, the following provisioning features are available for any 1. To the right of the drop-down menu, type `.*.*`. 1. Click **Save**. {% data reusables.saml.okta-view-setup-instructions %} -1. Enable SAML for your enterprise account using the information in the setup instructions. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +1. Enable SAML for your enterprise account using the information in the setup instructions. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." ### Creating groups in Okta diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..98de9573eab39 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: Enabling SAML single sign-on for organizations in your enterprise account +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)." + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. + +{% endnote %} + +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) +8. Under **Public Certificate**, paste a certificate to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) +9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) +10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) +11. Click **Save**. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 93cd621d8df92..79a4ce134105d 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ You can also configure allowed IP addresses for an individual organization. For {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### Enabling SAML single sign-on for organizations in your enterprise account - -{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)." - -Enterprise owners can enable SAML SSO and centralized authentication through a SAML IdP across all organizations owned by an enterprise account. After you enable SAML SSO for your enterprise account, SAML SSO is enabled by default for all organizations owned by your enterprise account. All members will be required to authenticate using SAML SSO to gain access to the organizations where they are a member, and enterprise owners will be required to authenticate using SAML SSO when accessing an enterprise account. - -{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} If you're not participating in the private beta, SCIM is not supported for enterprise accounts. For more information, see "[Managing user provisioning for organizations in your enterprise account](#managing-user-provisioning-for-organizations-in-your-enterprise-account)." - -{% note %} - -**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations. - -{% endnote %} - -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -8. Under **Public Certificate**, paste a certificate to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -11. Click **Save**. - -### Managing user provisioning for organizations in your enterprise account - -Enterprise owners can manage organization membership in an enterprise account directly from an identity provider (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Optionally, you can also enable SAML provisioning and, separately, deprovisioning. - -If you configure SCIM in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. If you enable SAML provisioning, each time an enterprise member accesses a resource protected by your enterprise account's SAML configuration, that SAML assertion will trigger provisioning. - -For each SCIM call or SAML assertion, {% data variables.product.product_name %} will check the IdP groups the user belongs to and perform the following operations: - -- If the user is a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is not currently a member of that organization, add the user to the organization (SAML assertion) or send the user an email invitation to join the organization (SCIM call). -- Cancel any existing invitations for the user to join an organization owned by your enterprise account. - -For each SCIM call and, if you enable SAML deprovisioning, each SAML assertion, {% data variables.product.product_name %} will also perform the following operation: - -- If the user is not a member of an IdP group that corresponds to an organization owned by your enterprise account, and the user is currently a member of that organization, remove the user from the organization. - -If deprovisioning removes the last remaining owner from an organization, the organization will become unowned. Enterprise owners can assume ownership of unowned organizations. For more information, see "[Managing unowned organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)." - -To enable user provisioning for your enterprise account using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." - -### Managing team synchronization for organizations in your enterprise account - -Enterprise owners can enable team synchronization between an IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in the organizations owned by your enterprise account with IdP groups. - -{% data reusables.identity-and-permissions.about-team-sync %} - -You can use team synchronization with your enterprise account with Azure AD. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -You can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." - -#### Требования - -Before you can enable team synchronization for your enterprise account: - - You or your Azure AD administrator must be a Global administrator or a Privileged Role administrator in Azure AD. - - You must enable SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." - - You must authenticate to your enterprise account using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." - -#### Managing team synchronization for Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Review the identity provider tenant information you want to connect to your enterprise account, then click **Approve**. ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png) -8. To disable team synchronization, click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) - ### Managing your enterprise account's SSH certificate authorities Enterprise owners can add and delete an enterprise account's SSH certificate authorities (CA). @@ -203,3 +112,7 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### Дополнительная литература + +- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md index 6d144e7ecc7d8..4dae4a37df1c6 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + 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 77d43864e77ae..39d222f390a5b 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 @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. + +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." @@ -27,11 +29,13 @@ For more information about {% data variables.product.prodname_enterprise %}, see 3. On {% data variables.product.prodname_dotcom_the_website %}, create at least one organization owned by your enterprise account. For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." -4. The subscriber must create a user account on {% data variables.product.prodname_dotcom_the_website %}, and the email address for the account must be the same email address as the email address in the {% data variables.product.prodname_vs %} portal. For more information, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." - ### Inviting a subscriber to use {% data variables.product.prodname_enterprise %} -To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber must join an organization owned by your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Organization owners can invite new members to an organization. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. + +Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. + +For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." ### Viewing {% data variables.product.prodname_enterprise %} licensing diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..1483a936d0d3e --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: Managing team synchronization for organizations in your enterprise account +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +You can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)." + +### Требования + +You or your Azure AD administrator must be a Global administrator or a Privileged Role administrator in Azure AD. + +You must enable SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +You must authenticate to your enterprise account using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +### Managing team synchronization for Azure AD + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png) +8. To disable team synchronization, click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index 20b9ebbda5ea5..5ac9d2f572908 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)." +If you enable user deprovisioning to manage organization membership in your enterprise account, you could end up with an organization that has no organization owners. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." {% data reusables.enterprise-accounts.access-enterprise %} 2. To the right of the search field, click **X unowned**. ![Button to view unowned organizations](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 35c485a789d2d..cdfed2ee4ae46 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,6 +18,8 @@ When you enable SAML single sign-on for your enterprise account, each enterprise {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index e799f3f2379a7..3b2c0ceb764ff 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -22,8 +22,8 @@ For more information about managing billing managers, see "[Inviting people to m {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Under "User +1. 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. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![License and subscription information in enterprise billing settings](/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 %}**. +1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index 834310c11d1af..c0469e24b7b09 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -39,20 +39,20 @@ You can use the `git show` command with the `--pretty=fuller` flag to check if t $ git show Your commit SHA number --pretty=fuller commit Your commit SHA number Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` If the author and commit date are different, you can manually change the commit date in the URL to see the commit details. Например: -- This URL uses the author date of `2016-07-13`: +- This URL uses the author date of `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- This URL uses the commit date of `2016-07-19`: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- This URL uses the commit date of `2018-04-10`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` When you open the URL with the modified commit date, you can see the commit details. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 99cf4f7da1e49..727c1691ba20f 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### Contributions that are counted -#### Issues and pull requests +#### Issues, pull requests and discussions -Issues and pull requests will appear on your contribution graph if they were opened in a standalone repository, not a fork. +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. #### Commits Commits will appear on your contributions graph if they meet **all** of the following conditions: diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index 66f66f6b8289e..a64740d677230 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,7 +14,7 @@ versions: For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. {% data reusables.user_settings.access_settings %} -1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) 1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 53e3c3a3d6be0..1d674cf9b1d1f 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,7 +30,8 @@ The repository owner has full control of the repository. In addition to the acti | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" | | Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" | | Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} @@ -63,7 +64,8 @@ Collaborators can also perform the following actions. | Действие | More information | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" | +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} | Create, edit, and delete comments on commits, pull requests, and issues in the repository |
          • "[About issues](/github/managing-your-work-on-github/about-issues)"
          • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
          • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
          | | Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | | Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 7138446d68f12..2b62f9bbb23e1 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ There are three levels of permissions for project board collaborators: The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can: - [Manage, view, and add collaborators](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configure a project board as public or private](/articles/changing-project-board-visibility) +- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) - [Delete a project board](/articles/deleting-a-project-board/) - [Close a project board](/articles/closing-a-project-board/) - [Reopen a closed project board](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ Collaborators with write access to a user-owned project board can: ### Project board visibility -You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." +You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." ### Дополнительная литература diff --git a/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md b/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md index 9a8549cbd9d48..cc88aa48cbcad 100644 --- a/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com, GitHub Enterprise Server, and the information you upload to either product may be subject to trade control regulations, including under the U.S. Export Administration Regulations (the EAR). -GitHub’s vision is to be the global platform for developer collaboration, no matter where developers reside. We take seriously our responsibility to examine government mandates thoroughly to be certain that users and customers are not impacted beyond what is required by law. This includes keeping public repositories services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. +GitHub’s vision is to be the global platform for developer collaboration, no matter where developers reside. We take seriously our responsibility to examine government mandates thoroughly to be certain that users and customers are not impacted beyond what is required by law. This includes keeping public repository services, including those for open source projects, available and accessible to support personal communications involving developers in sanctioned regions. This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community. -To comply with U.S. trade control laws, GitHub made some required changes to the way we conduct our services. As U.S. trade controls laws evolve, we will continue to work with U.S. regulators about the extent to which we can offer free code collaboration services to developers in sanctioned markets. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those markets. For more insight on our approach and how sanctions affect global software collaboration, read our [blog on sanctions](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). +As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Although we've provided the following information below for your convenience, it is ultimately your responsibility to ensure that your use of GitHub's products and services complies with all applicable laws and regulations, including U.S. export control laws. @@ -25,9 +25,9 @@ Under our [Terms of Service](/articles/github-terms-of-service), users may only Users are responsible for ensuring that the content they develop and share on GitHub.com complies with the U.S. export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). The cloud-hosted service offering available at [GitHub.com](https://github.com) has not been designed to host data subject to the ITAR and does not currently offer the ability to restrict repository access by country. If you are looking to collaborate on ITAR- or other export-controlled data, we recommend you consider [GitHub Enterprise Server](https://enterprise.github.com), GitHub's on-premises offering. -U.S. trade control laws restrict what GitHub.com services can be made available to users in certain countries and territories. GitHub may allow users in or ordinarily resident in countries and territories subject to U.S. sanctions to access certain free GitHub.com services for personal communications in accordance to authorizations issued by the U.S. Treasury Department’s Office of Foreign Assets Controls (OFAC). Persons in or ordinarily resident in these countries and territories are prohibited from using IP proxies, VPNs, or other methods to disguise their location when accessing GitHub.com services, and may only use GitHub.com for non-commercial, personal communications. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs) and other denied or blocked parties under U.S. and other applicable law are prohibited from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### Корпоративный сервер GitHub @@ -41,7 +41,7 @@ GitHub Enterprise Server may not be sold to, exported, or re-exported to any cou #### On which countries and territories are U.S. government sanctions applied? -Crimea, Cuba, Iran, North Korea, and Syria. +Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. #### How is GitHub ensuring that folks not living in and/or having professional links to the sanctioned countries and territories still have access or ability to appeal? @@ -55,23 +55,23 @@ Travel in these regions may impact your account status, but availability may be #### What is available and not available? -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -However, due to U.S. trade controls law restrictions, GitHub is unable to provide private repository services and paid services to accounts in U.S. sanctioned regions like North Korea, Iran, Syria, and Crimea. The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. -For paid organizational accounts in sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. #### How do you define these specific users? -If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. +If GitHub determines that a user or customer is located in a region that is subject to U.S. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. The determination of user and customer location to implement these legal restrictions are derived from a number of sources, including IP addresses and payment history. Nationality and ethnicity are not used to flag users for sanctions restrictions. #### How are organization accounts impacted? -If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. economic sanctions, then the organization account and the affiliated owner account will be restricted. -The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. +The restriction suspends access to private repository services and paid services, such as availability of free or paid private repositories, secret gists, paid Action minutes, Sponsors, and GitHub Marketplace services. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### Can trade-restricted users’ private repositories be made public? @@ -81,3 +81,16 @@ Free individual account users can make restricted private repositories public, f Unfortunately, our understanding of the law does not give us the option to allow downloads or deletion of private repository content, until otherwise authorized by the U.S. government. We will strongly advocate, with U.S. regulators, for the right of trade-restricted users to secure the contents of their private repositories. We will also advocate for more availability of GitHub services for developers in sanctioned markets, and further underscore the importance of code collaboration in supporting personal communications for developers globally. +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. diff --git a/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index 5ea4f4e319457..97bff67a756e9 100644 --- a/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ That said, if legal action is initiated by a third party, including law enforcem ### 3. Limited Waiver of Other Site Polices -To the extent your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but are consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first! +To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first! diff --git a/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md index 23e97cf6a38c7..d54b593789e33 100644 --- a/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **December 30, 2020** +Effective date: **January 6, 2021** GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -25,12 +25,9 @@ When we share your information with third party subprocessors, such as our vendo | Braintree (PayPal) | Subscription credit card payment processor | United States | United States | | Clearbit | Marketing data enrichment service | United States | United States | | Discourse | Community forum software provider | United States | United States | -| DiscoverOrg | Marketing data enrichment service | United States | United States | | Eloqua | Marketing campaign automation | United States | United States | | Google Apps | Internal company infrastructure | United States | United States | | Google Analytics | Analytics and performance | United States | United States | -| LinkedIn Navigator | Data enrichment service | United States | United States | -| Magic Robot | Campaign reporting (Salesforce Add-on) | United States | United States | | MailChimp | Customer ticketing mail services provider | United States | United States | | Mailgun | Transactional mail services provider | United States | United States | | Microsoft | Microsoft Services | United States | United States | diff --git a/translations/ru-RU/content/github/site-policy/index.md b/translations/ru-RU/content/github/site-policy/index.md index 2fb09f3fabffc..03094d4478abd 100644 --- a/translations/ru-RU/content/github/site-policy/index.md +++ b/translations/ru-RU/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 62daa89c406e4..a283f8c2ee8d4 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ You can view analytics on your current and past sponsorships, the payments you'v ### Viewing recent sponsorship activity {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### Exporting your sponsorship data -If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. +You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Click **Export all**. ![Export all button](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Export button](/assets/images/help/sponsors/export-all.png) 1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index d4c1698b280f7..070fc1f50ddf5 100644 --- a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -21,7 +21,7 @@ When you enable data use for your private repository, you'll be able to access t {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### Дополнительная литература diff --git a/translations/ru-RU/content/github/using-git/adding-a-remote.md b/translations/ru-RU/content/github/using-git/adding-a-remote.md index bed66e0493b86..87b0e9c2cd8f6 100644 --- a/translations/ru-RU/content/github/using-git/adding-a-remote.md +++ b/translations/ru-RU/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ You may encounter these errors when trying to add a remote. This error means you've tried to add a remote with a name that already exists in your local repository: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/ru-RU/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/ru-RU/content/github/using-git/using-git-rebase-on-the-command-line.md index e68037cb22146..738f9af8ca501 100644 --- a/translations/ru-RU/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/ru-RU/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,7 +124,11 @@ As before, Git is showing the commit message for you to edit. You can change the Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes: ```shell -$ git push origin master --force +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes +$ git push origin main --force ``` {% warning %} diff --git a/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 6425b245ecd64..83f3757ccaa9f 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ Your theme includes default layouts, includes, and stylesheets that will automat {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### Дальнейшие шаги {% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." diff --git a/translations/ru-RU/content/github/working-with-github-support/about-github-support.md b/translations/ru-RU/content/github/working-with-github-support/about-github-support.md index c91e7c31732da..77bd872631c17 100644 --- a/translations/ru-RU/content/github/working-with-github-support/about-github-support.md +++ b/translations/ru-RU/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ To see if there are currently any incidents affecting services on {% data variab ### Contacting {% data variables.contact.github_support %} -{% data variables.product.prodname_free_user %} user and organization accounts can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. You can also contact {% data variables.contact.contact_support %} to report account, security, and abuse issues. +You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. -On paid accounts, you can either contact {% data variables.contact.contact_support %} and, depending on your plan, contact {% data variables.contact.premium_support %} or {% data variables.contact.contact_ent_support %}. For more information about contacting {% data variables.contact.premium_support %}, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud) or "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)." +To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. ### Granting {% data variables.contact.github_support %} temporary access to a private repository diff --git a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 93eb012c3a088..9596f7de91f2b 100644 --- a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -215,7 +215,7 @@ You can add emoji to your writing by typing `:EMOJICODE:`. Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result. -For a full list of available emoji and codes, check out [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). +For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). ### Paragraphs diff --git a/translations/ru-RU/content/github/writing-on-github/creating-gists.md b/translations/ru-RU/content/github/writing-on-github/creating-gists.md index d5655b46bb085..eaa67a64c2ef2 100644 --- a/translations/ru-RU/content/github/writing-on-github/creating-gists.md +++ b/translations/ru-RU/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- title: Creating gists -intro: 'You can create two kinds of gists: public and secret. Create a public gist if you''re ready to share your ideas with the world or a secret gist if you''re not.' +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,13 @@ versions: ### About gists -Every gist is a Git repository, which means that it can be forked and cloned. If you are signed in to {% data variables.product.product_name %} when you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. +Every gist is a Git repository, which means that it can be forked and cloned. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -Gists can be public or secret. Public gists show up in {% data variables.gists.discover_url %}, where people can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. {% data reusables.gist.cannot-convert-public-gists-to-secret %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. -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 %} Secret gists aren't private. If you send the URL of a secret gist to a friend, they'll be able to see it. However, if someone you don't know discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead. +Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead. + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -39,7 +41,7 @@ You can pin gists to your profile so other people can see them easily. For more {% endif %} -You can discover gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists). @@ -69,12 +71,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 4. Type the text of your gist into the gist text box. ![Gist text box](/assets/images/help/gist/gist_text_box.png) -5. Do one of the following: - - To create a public gist, click **Create public gist**. - - To create a secret gist, click **Create secret Gist**. ![Gist create button](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **Note:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/ru-RU/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/ru-RU/content/github/writing-on-github/forking-and-cloning-gists.md index 04f68e84c4225..0b7a42b681f3a 100644 --- a/translations/ru-RU/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/ru-RU/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Forking gists -Each gist indicates which forks have activity, making it easy to find interesting changes from coworkers or complete strangers. +Each gist indicates which forks have activity, making it easy to find interesting changes from others. ![Gist forks](/assets/images/help/gist/gist_forks.png) diff --git a/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md b/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md index 98b4fba1b50fa..fe21b30abf397 100644 --- a/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ru-RU/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ Mutations are structured like this: 
          mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
          The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. diff --git a/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md index eafc9638b326c..f99857189fe2f 100644 --- a/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." @@ -30,8 +30,6 @@ Before you can use the Docker registry on {% data variables.product.prodname_reg ### Authenticating to {% data variables.product.prodname_registry %} -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### Authenticating with a personal access token @@ -51,11 +49,25 @@ To keep your credentials secure, we recommend you save your personal access toke {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} {% raw %} ```shell $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. @@ -94,9 +106,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, {% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. @@ -105,9 +127,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. Publish the image to {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + If your instance has subdomain isolation disabled: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen #### Example publishing a Docker image -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. @@ -197,9 +246,19 @@ You can use the `docker pull` command to install a docker image from {% data var $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +If your instance has subdomain isolation disabled: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index ad3f8a39b56ed..df2102b1d1edd 100644 --- a/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -78,10 +78,35 @@ If your instance has subdomain isolation disabled: ### Publishing a package -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +2. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. 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. + {% data reusables.package_registry.authenticate-step %} 2. Create a new project. ```shell @@ -118,6 +143,8 @@ You can publish a package to {% data variables.product.prodname_registry %} by a dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### Publishing multiple packages to the same repository To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. diff --git a/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md index e986d3d16cddb..768b01b327a96 100644 --- a/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -206,6 +206,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### Дополнительная литература - "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md index 2ae7987139fa8..83d75341401fb 100644 --- a/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. diff --git a/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md b/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md index b66eb8628ac3b..6477a4f743110 100644 --- a/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,272 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{ ### Publishing a package using an action -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
          + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
          + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
          + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
          + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
          + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
          + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
          + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
          + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
          + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
          + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
          + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
          + +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Installing a package using an action You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. diff --git a/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md b/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md index cc1409285c399..d987658db4cd4 100644 --- a/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ You can integrate {% data variables.product.prodname_registry %} with {% data va {% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_registry %} also offers a {% data variables.product.prodname_container_registry %} designed to support the unique needs of container images. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% 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) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca ### Managing packages -You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." diff --git a/translations/ru-RU/content/rest/overview/api-previews.md b/translations/ru-RU/content/rest/overview/api-previews.md index 4fae0855c38f6..1db9d6169d971 100644 --- a/translations/ru-RU/content/rest/overview/api-previews.md +++ b/translations/ru-RU/content/rest/overview/api-previews.md @@ -70,14 +70,6 @@ Manage [projects](/rest/reference/projects). **Custom media type:** `cloak-preview` **Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} -### User blocking - -Users can [block other users](/rest/reference/users#blocking). Organizations can [block users](/rest/reference/orgs#blocking), too. - -**Custom media type:** `giant-sentry-fist-preview` **Announced:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Update 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Update 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - ### Repository topics View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results. diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md index 6f14bb96cf5d4..6dc2e0240c261 100644 --- a/translations/ru-RU/content/rest/overview/libraries.md +++ b/translations/ru-RU/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 5a1540afd3662..a9f8c699658ce 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 @@ -30,7 +30,7 @@ For information about GitHub's GraphQL API, see the [v4 documentation](/graphql) sent and received as JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -124,7 +124,7 @@ Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated- Authenticating with invalid credentials will return `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -324,7 +324,7 @@ Note that [the Search API has custom rate limit rules](/rest/reference/search#ra The returned HTTP headers of any API request show your current rate limit status: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -422,7 +422,7 @@ User-Agent: Awesome-Octocat-App cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -449,7 +449,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -460,7 +460,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -471,7 +471,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -489,7 +489,7 @@ The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any Here's a sample request sent from a browser hitting `http://example.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval @@ -498,7 +498,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra This is what the CORS preflight request looks like: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With diff --git a/translations/ru-RU/content/rest/reference/code-scanning.md b/translations/ru-RU/content/rest/reference/code-scanning.md index 42f1f093fec7e..efd7f361f7cf1 100644 --- a/translations/ru-RU/content/rest/reference/code-scanning.md +++ b/translations/ru-RU/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Code scanning redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/ru-RU/data/glossaries/external.yml b/translations/ru-RU/data/glossaries/external.yml index a0b87986d52d4..aca717cf82b56 100644 --- a/translations/ru-RU/data/glossaries/external.yml +++ b/translations/ru-RU/data/glossaries/external.yml @@ -123,7 +123,7 @@ - term: коммит description: >- - Коммит или «версия» — это отдельное изменение файла (или набора файлов). При создании коммита для сохранения своей работы Git присваивает уникальный ID (также называемый «SHA» или «хэш»), который позволяет регистрировать конкретные изменения вместе с данными о том, кто и когда их внес. Обычно коммиты содержат сообщение о коммите, в котором кратко описаны сделанные изменения. + A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. - term: автор коммита description: Пользователь, выполняющий коммит. @@ -137,7 +137,7 @@ - term: сообщение коммита description: >- - Краткий описательный текст, который присутствует в коммите и содержит информацию об изменении, которое вносит коммит. + Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. - term: сравнить ветвь description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - Gist — это файл совместного доступа, который можно редактировать, клонировать и порождать его копию в GitHub. Gist может быть общедоступным или скрытым, хотя скрытый gist будет доступен всем, у кого есть URL. + A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- @@ -436,7 +436,7 @@ - term: оповещение description: >- - Обновления, доставляемые через Интернет или по электронной почте, в зависимости от ваших настроек, в которых содержится информация об интересующих вас действиях. + Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. - term: Приложение OAuth description: >- diff --git a/translations/ru-RU/data/glossaries/internal.yml b/translations/ru-RU/data/glossaries/internal.yml index 6599533df7987..71a3c8ee165a8 100644 --- a/translations/ru-RU/data/glossaries/internal.yml +++ b/translations/ru-RU/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: Центральный процессор. - term: вспомогательное приложение для управления учетными данными - description: Программа, которая хранит и оценивает учетные данные Git. + description: A program that stores and fetches Git credentials. - term: creole description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - Отображение редактируемого текста максимально похожим на конечный результат образом. Аббревиатура означает, что текст на экране выглядит таким же, каким его будет видеть пользователь. + What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. - term: XenServer description: Платформа виртуализации. diff --git a/translations/ru-RU/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/ru-RU/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..f957e0b7bcffa --- /dev/null +++ b/translations/ru-RU/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: Access to package version deletion + description: >- + This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Deployments + description: >- + This preview adds support for deployments mutations and new deployments features. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - More detailed information about a pull request's merge state. + description: >- + This preview adds support for accessing fields that provide more detailed information about a pull request's merge state. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Update multiple refs in a single operation. + description: This preview adds support for updating multiple refs in a single operation. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Project Event Details + description: >- + This preview adds project, project card, and project column details to project-related issue events. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Create content attachments + description: This preview adds support for creating content attachments. + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: Pinned Issues Preview + description: This preview adds support for pinned issues. + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: Labels Preview + description: >- + This preview adds support for adding, updating, creating and deleting labels. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Import Project + description: This preview adds support for importing projects. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Team Review Assignments Preview + description: >- + This preview adds support for updating the settings for team review assignment. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/ru-RU/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..10f9989a1239f --- /dev/null +++ b/translations/ru-RU/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +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.' + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-04-01T00:00:00+00:00' + criticality: breaking + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + 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.' + 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' + 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' + 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.' + 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.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + 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.' + 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.' + 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.' + 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 + owner: nplasterer diff --git a/translations/ru-RU/data/learning-tracks/actions.yml b/translations/ru-RU/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..678519414c344 --- /dev/null +++ b/translations/ru-RU/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: 'Get started with {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: 'You can create self-hosted runners to run workflows in a highly customizable environment.' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/ru-RU/data/release-notes/2-22/0.yml b/translations/ru-RU/data/release-notes/2-22/0.yml index 2070890751cff..6f2bbb20de133 100644 --- a/translations/ru-RU/data/release-notes/2-22/0.yml +++ b/translations/ru-RU/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/3-0/0-rc.yml b/translations/ru-RU/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..93307df85e25f --- /dev/null +++ b/translations/ru-RU/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: Изменения API + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ru-RU/data/reusables/actions/enterprise-actions-permissions.md b/translations/ru-RU/data/reusables/actions/enterprise-actions-permissions.md index 72c38f66bcaed..e66c8787334c4 100644 --- a/translations/ru-RU/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/ru-RU/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. Under "Policies", select an option. ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/ru-RU/data/reusables/actions/enterprise-beta.md b/translations/ru-RU/data/reusables/actions/enterprise-beta.md index 5c456da70dfdc..b10237e2827ed 100644 --- a/translations/ru-RU/data/reusables/actions/enterprise-beta.md +++ b/translations/ru-RU/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md b/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..ee9ba1dca8396 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **Note:** {% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/ru-RU/data/reusables/actions/enterprise-enable-checkbox.md b/translations/ru-RU/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/ru-RU/data/reusables/actions/enterprise-http-proxy.md b/translations/ru-RU/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/ru-RU/data/reusables/actions/enterprise-limit-actions-use.md b/translations/ru-RU/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..e2f4ed9452634 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." diff --git a/translations/ru-RU/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/ru-RU/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..dd9fe3fe4e656 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### Дальнейшие шаги + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/ru-RU/data/reusables/actions/enterprise-s3-permission.md b/translations/ru-RU/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/ru-RU/data/reusables/actions/enterprise-s3-support-warning.md b/translations/ru-RU/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/enterprise-self-signed-cert.md b/translations/ru-RU/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/ru-RU/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/ru-RU/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/ru-RU/data/reusables/actions/workflow-template-overview.md b/translations/ru-RU/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..a08dedbf2a197 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. You can use workflow templates as a starting place to build your custom workflow or use them as-is. + +You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. diff --git a/translations/ru-RU/data/reusables/advanced-security/more-info-ghas.md b/translations/ru-RU/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..4a510456e92ed --- /dev/null +++ b/translations/ru-RU/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." +{% endif %} diff --git a/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/code-scanning/beta.md b/translations/ru-RU/data/reusables/code-scanning/beta.md index 3dfd7cae7dc0c..7d1b5dbc94798 100644 --- a/translations/ru-RU/data/reusables/code-scanning/beta.md +++ b/translations/ru-RU/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_code_scanning_capc %} is currently in beta and subject to change. For more information about taking part in the beta, [sign up here](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/ru-RU/data/reusables/code-scanning/not-available.md b/translations/ru-RU/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..6531f5e1d0875 --- /dev/null +++ b/translations/ru-RU/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." + +{% endnote %} +{% endif %} diff --git a/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md b/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md index b8d2b78cbceae..18554c0ce1388 100644 --- a/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. 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#allowing-dependabot-to-access-private-repositories)." +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. 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#allowing-dependabot-to-access-private-repositories)." -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/ru-RU/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index f57ed274394cc..e9533a00f72ff 100644 --- a/translations/ru-RU/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/ru-RU/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Note:** User provisioning for enterprise accounts is currently in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact). {% endnote %} diff --git a/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 1ef7257106f6b..1bdc5adca7700 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Minimum requirements](#minimum-requirements) -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [Storage](#storage) - [CPU and memory](#cpu-and-memory) @@ -7,10 +8,10 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- You must configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +- You must configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Maximum jobs per minute | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ We recommend a high-performance SSD with high input/output operations per second Your instance requires a persistent data disk separate from the root disk. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview)." -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable the beta of {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 2.22, you'll need to configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endif %} @@ -48,4 +49,4 @@ You can resize your instance's root disk by building a new instance or using an {% endwarning %} -You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md index 97997e7d4f3a8..a9ffb7473a5c3 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| +| Trial, demo, or 10 light users | 2
          or [**4**](#optional-features) | 16 GB
          or [**32 GB**](#optional-features) | 100 GB
          or [**150 GB**](#optional-features) | 200 GB | +| 10 to 3,000 | 4
          or [**8**](#optional-features) | 32 GB
          or [**48 GB**](#optional-features) | 250 GB
          or [**300 GB**](#optional-features) | 200 GB | +| 3,000 to 5000 | 8
          or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | 12
          or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | 16
          or [**20**](#optional-features) | 128 GB
          or [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | User licenses | vCPUs | Memory | Attached storage | Root storage | |:------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------:| | Trial, demo, or 10 light users | 2{% if currentVersion == "enterprise-server@2.22" %}
          or [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
          or [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
          or [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5,000 to 8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
          or [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8,000 to 10,000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
          or [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
          or [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise_management_console/actions.md b/translations/ru-RU/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..15dbf50384e3d --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Actions**. ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/ru-RU/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/ru-RU/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..a999a5edfc417 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..4b1379243ea91 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +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. You should time this change carefully, to minimize downtime. + +{% endwarning %} diff --git a/translations/ru-RU/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/ru-RU/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..2c4dec3daa201 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Click **Save changes**. ![Save changes button](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/gated-features/code-scanning.md b/translations/ru-RU/data/reusables/gated-features/code-scanning.md index 2bcd80c1d4af9..69e6abf27f4f7 100644 --- a/translations/ru-RU/data/reusables/gated-features/code-scanning.md +++ b/translations/ru-RU/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ru-RU/data/reusables/gated-features/environments.md b/translations/ru-RU/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/ru-RU/data/reusables/gated-features/environments.md +++ b/translations/ru-RU/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ru-RU/data/reusables/gated-features/protected-branches.md b/translations/ru-RU/data/reusables/gated-features/protected-branches.md index a9745fcec2b68..ffae769bab961 100644 --- a/translations/ru-RU/data/reusables/gated-features/protected-branches.md +++ b/translations/ru-RU/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 %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ru-RU/data/reusables/gated-features/secret-scanning.md b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md index bd279034eee82..7396ad8e24141 100644 --- a/translations/ru-RU/data/reusables/gated-features/secret-scanning.md +++ b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ru-RU/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/ru-RU/data/reusables/gist/cannot-convert-public-gists-to-secret.md index f34b2701d8a5d..535fa5cd9df20 100644 --- a/translations/ru-RU/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/ru-RU/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -After creating a gist, you cannot convert it from public to secret. +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..cd1cc8d5fec37 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/ru-RU/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..44708fbdf62c9 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. For more information, see "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)." +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. For more information, see "[Contexts](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)." + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/ru-RU/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/ru-RU/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index 7070f89368e2a..742712357e45c 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -To enable team synchronization for Azure AD, your Azure AD installation needs the following permissions: +To enable team synchronization for Azure AD, your Azure AD installation needs the following permissions. - Read all users’ full profiles - Sign in and read user profile - Read directory data diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm.md index 1735680d5e454..8f6a50e6a5028 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. To confirm team synchronization: +5. Confirm team synchronization. - If you have IdP access, click **Enable team synchronization**. You'll be redirected to your identity provider's SAML SSO page and asked to select your account and review the requested permissions. - If you don't have IdP access, copy the IdP redirect link and share it with your IdP administrator to continue enabling team synchronization. ![Enable team synchronization redirect button](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/ru-RU/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/ru-RU/data/reusables/large_files/can-include-lfs-objects-archives.md index d63ea5bb6d0a2..e9ee6e5220b96 100644 --- a/translations/ru-RU/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/ru-RU/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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} You can choose whether {% 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. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ru-RU/data/reusables/mobile/about-mobile.md b/translations/ru-RU/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/ru-RU/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/ru-RU/data/reusables/mobile/ghes-release-phase.md b/translations/ru-RU/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/ru-RU/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/mobile/push-notifications-on-ghes.md b/translations/ru-RU/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/ru-RU/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/organizations/can-require-ssh-cert.md b/translations/ru-RU/data/reusables/organizations/can-require-ssh-cert.md index 6da37763232e5..1ed5f3afb99ac 100644 --- a/translations/ru-RU/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/ru-RU/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -You can require that members use SSH certificates to access organization resources,, unless SSH is disabled in your repository. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/ru-RU/data/reusables/organizations/click-codespaces.md b/translations/ru-RU/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/ru-RU/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ru-RU/data/reusables/organizations/team-synchronization.md b/translations/ru-RU/data/reusables/organizations/team-synchronization.md index 870153231374a..121340e06b008 100644 --- a/translations/ru-RU/data/reusables/organizations/team-synchronization.md +++ b/translations/ru-RU/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -You can use team synchronization to automatically add and remove team members in an organization through an identity provider. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/ru-RU/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/ru-RU/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/ru-RU/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/ru-RU/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/ru-RU/data/reusables/package_registry/packages-cluster-support.md b/translations/ru-RU/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/ru-RU/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/ru-RU/data/reusables/package_registry/packages-ghes-release-stage.md index 03d9b25f84162..04e4ffd9ea459 100644 --- a/translations/ru-RU/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/ru-RU/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your instance, use the [sign-up form](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/ru-RU/data/reusables/project-management/choose-visibility.md b/translations/ru-RU/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..d0d1877d65c92 --- /dev/null +++ b/translations/ru-RU/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. For more information, see "[Changing project board visibility](/github/managing-your-work-on-github/changing-project-board-visibility)." ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/ru-RU/data/reusables/project-management/project-board-visibility.md b/translations/ru-RU/data/reusables/project-management/project-board-visibility.md index eec92c411476d..c9091f06bf10e 100644 --- a/translations/ru-RU/data/reusables/project-management/project-board-visibility.md +++ b/translations/ru-RU/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. A public project board is visible to anyone with the project board's URL. +By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/ru-RU/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/ru-RU/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index 089efbf2bea5b..345f7941ee206 100644 --- a/translations/ru-RU/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/ru-RU/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -If status checks are required for a repository, the required status checks must pass before you can merge your branch into the protected branch. For more information, see "[About required status checks](/articles/about-required-status-checks)." +If status checks are required for a repository, the required status checks must pass before you can merge your branch into the protected branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." diff --git a/translations/ru-RU/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/ru-RU/data/reusables/pull_requests/required-reviews-for-prs-summary.md index ef0b0a397bd4d..3526e39a78da3 100644 --- a/translations/ru-RU/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/ru-RU/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -Repository administrators can require that all pull requests receive a specific number of approving reviews from people with *write* or *admin* permissions in the repository or from a designated code owner before they're merged into a protected branch. For more information, see "[About protected branches](/articles/about-protected-branches)." - -When required reviews are enabled, anyone with access to the repository can approve changes in a pull request. However, you won't be able to merge your pull request until the required number of reviewers with *write* or *admin* permissions in the repository approve your pull request's changes in their review. For more information about repository permission levels, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)." If review is required from a designated code owner and the pull request affects code that has a designated owner, approval from that owner is required. +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/ru-RU/data/reusables/repositories/branch-rules-example.md b/translations/ru-RU/data/reusables/repositories/branch-rules-example.md index b9cd9572f0235..ea81704455211 100644 --- a/translations/ru-RU/data/reusables/repositories/branch-rules-example.md +++ b/translations/ru-RU/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -You can create a branch rule in a repository for a specific branch, all branches, or any branch that matches a naming pattern specified with the fnmatch syntax. For example, to require any branch containing the word `release` to have at least two pull request reviews before merging, you can create a branch rule for `*release*`. +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/ru-RU/data/reusables/repositories/return-to-source-diff.md b/translations/ru-RU/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..c918830348fb3 --- /dev/null +++ b/translations/ru-RU/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/ru-RU/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/ru-RU/data/reusables/repositories/review-policy-overlapping-commits.md index d5fba7504a1a1..cfe413d8a0cef 100644 --- a/translations/ru-RU/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/ru-RU/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -After all required reviewers have approved a pull request, you won't be able to merge it if there are other open pull requests with pending or rejected reviews and those pull requests have a head branch pointing to the same commit. Someone with *write* or *admin* permissions will need to approve or dismiss the blocking review on the other pull requests before you can merge. +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/ru-RU/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ru-RU/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index b74d5905b1e47..ba73880189979 100644 --- a/translations/ru-RU/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/ru-RU/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/ru-RU/data/reusables/repositories/workflow-notifications.md b/translations/ru-RU/data/reusables/repositories/workflow-notifications.md index c353f20cf9834..e2d943102dcc6 100644 --- a/translations/ru-RU/data/reusables/repositories/workflow-notifications.md +++ b/translations/ru-RU/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + You can also see the status of workflow runs on a repository's Actions tab. For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." diff --git a/translations/ru-RU/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/ru-RU/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..e5be6752e0ef6 --- /dev/null +++ b/translations/ru-RU/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +Enterprise owners can enable SAML SSO and centralized authentication through a SAML IdP across all organizations owned by an enterprise account. After you enable SAML SSO for your enterprise account, SAML SSO is enabled by default for all organizations owned by your enterprise account. All members will be required to authenticate using SAML SSO to gain access to the organizations where they are a member, and enterprise owners will be required to authenticate using SAML SSO when accessing an enterprise account. diff --git a/translations/ru-RU/data/reusables/saml/dotcom-saml-explanation.md b/translations/ru-RU/data/reusables/saml/dotcom-saml-explanation.md index ddf9ab0bd50dc..be784eeb4f31c 100644 --- a/translations/ru-RU/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/ru-RU/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML SSO gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/ru-RU/data/reusables/secret-scanning/about-secret-scanning.md b/translations/ru-RU/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/ru-RU/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/ru-RU/data/reusables/secret-scanning/beta.md b/translations/ru-RU/data/reusables/secret-scanning/beta.md index 3625bb7a3e260..82fdadded9388 100644 --- a/translations/ru-RU/data/reusables/secret-scanning/beta.md +++ b/translations/ru-RU/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/ru-RU/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/ru-RU/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..eb0329e7fe346 --- /dev/null +++ b/translations/ru-RU/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." + +{% endnote %} + +{% endif %} diff --git a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/ru-RU/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/ru-RU/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index 9da98434c3759..74c33553abbc5 100644 --- a/translations/ru-RU/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/ru-RU/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Note**: You can't disable some security and analysis features that are enabled by default for public repositories. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/sponsors/activity-tab.md b/translations/ru-RU/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..507a5a0351706 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/support/ghae-priorities.md b/translations/ru-RU/data/reusables/support/ghae-priorities.md index f369d0c39ae51..5f4c120d03db9 100644 --- a/translations/ru-RU/data/reusables/support/ghae-priorities.md +++ b/translations/ru-RU/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Priority | Description | Примеры | |:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

          _After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
          • Errors or outages that affect core Git or web application functionality for all users
          • Severe network or performance degradation for majority of users
          • Full or rapidly filling storage
          • Known security incidents or a breach of access
          | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
          • Performance degradation that reduces productivity for many users
          • Reduced redundancy concerns from failures or service degradation
          • Production-impacting bugs or errors
          • {% data variables.product.product_name %} configuraton security concerns
          | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
          • Performance degradation that reduces productivity for many users
          • Reduced redundancy concerns from failures or service degradation
          • Production-impacting bugs or errors
          • {% data variables.product.product_name %} configuration security concerns
          | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
          • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
          • Issues with user tools and data collection methods
          • Улучшения
          • Bug reports, general security questions, or other feature related questions
            • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
            • Feature requests and product feedback
            • General questions on overall configuration or use of {% data variables.product.product_name %}
            • Notifying {% data variables.contact.github_support %} of any planned changes
            | diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md b/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml index c144b9cb54b1e..2f05bd3a73104 100644 --- a/translations/ru-RU/data/ui.yml +++ b/translations/ru-RU/data/ui.yml @@ -4,7 +4,7 @@ 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.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' 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. early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,15 @@ product_landing: quick_start: Quickstart reference_guides: Reference guides overview: Обзор +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: more guides + guideTypes: + overview: Обзор + quick_start: Quickstart + tutorial: Руководство + how_to: How-to guide + reference: Reference diff --git a/translations/ru-RU/data/variables/action_code_examples.yml b/translations/ru-RU/data/variables/action_code_examples.yml index b4c356a4fd18a..9aee540dac599 100644 --- a/translations/ru-RU/data/variables/action_code_examples.yml +++ b/translations/ru-RU/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/ru-RU/data/variables/gists.yml b/translations/ru-RU/data/variables/gists.yml index 9d1fea10acf46..12c745fd3ceb3 100644 --- a/translations/ru-RU/data/variables/gists.yml +++ b/translations/ru-RU/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml index d187b76b370c0..8ad45b6cef360 100644 --- a/translations/ru-RU/data/variables/product.yml +++ b/translations/ru-RU/data/variables/product.yml @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'Фонд подбора спонсоров GitHub' #GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/ru-RU/data/variables/release_candidate.yml b/translations/ru-RU/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/ru-RU/data/variables/release_candidate.yml +++ b/translations/ru-RU/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/zh-CN/content/actions/creating-actions/about-actions.md b/translations/zh-CN/content/actions/creating-actions/about-actions.md index 27e403461ae09..4acf4eba0bd92 100644 --- a/translations/zh-CN/content/actions/creating-actions/about-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/about-actions.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 857325f15f34c..6b2ccdaf0de9d 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -64,12 +65,12 @@ versions: required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -121,7 +122,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md index 088e6e7dbe525..11dd9b3de18c5 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md index 4a6165a10ce36..6ac8369ec21ed 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md index b378538d96fb4..56f10a66f214e 100644 --- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -60,14 +61,14 @@ ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] 要将操作元数据文件中定义的 `args` 提供到在 `ENTRYPOINT` 中使用 _exec_ 形式的 Docker 容器，建议创建一个可从 `ENTRYPOINT` 指令调用、名为 `entrypoint.sh` 的 shell 脚本。 ##### 示例 *Dockerfile* -``` +``` # Container image that runs your code FROM debian:9.5-slim # Copies your code file from your action repository to the filesystem path `/` of the container COPY entrypoint.sh /entrypoint.sh -# Executes `entrypoint.sh` when the Docker container starts up +# Executes `entrypoint.sh` when the Docker container starts up ENTRYPOINT ["/entrypoint.sh"] ``` @@ -78,14 +79,14 @@ ENTRYPOINT ["/entrypoint.sh"] ``` sh #!/bin/sh -# `$*` expands the `args` supplied in an `array` individually +# `$*` expands the `args` supplied in an `array` individually # or splits `args` in a string separated by whitespace. sh -c "echo $*" ``` 您的代码必须是可执行的。 在用于工作流程之前，确保 `entrypoint.sh` 文件有 `execute` 权限。 您可以使用此命令从终端修改权限： ``` sh - chmod +x entrypoint.sh + chmod +x entrypoint.sh ``` 当 `ENTRYPOINT` shell 脚本不可执行时，您将收到一个类似于以下内容的错误： diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md index c1a89a776ac3b..6ac4b60449bad 100644 --- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'reference' --- {% data reusables.actions.enterprise-beta %} @@ -110,12 +111,12 @@ outputs: ```yaml outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - id: random-number-generator run: echo "::set-output name=random-id::$(echo $RANDOM)" shell: bash @@ -186,7 +187,7 @@ runs: #### `pre-if` -**可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 请注意，`step` 上下文不可用，因为尚未运行任何步骤。 +**可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 请注意，`step` 上下文不可用，因为尚未运行任何步骤。 在此示例中，`cleanup.js` 仅在基于 Linux 的运行器上运行： @@ -264,7 +265,7 @@ runs: ```yaml runs: using: "composite" - steps: + steps: - run: ${{ github.action_path }}/test/script.sh shell: bash ``` @@ -279,7 +280,7 @@ runs: ```yaml runs: using: "composite" - steps: + steps: - run: $GITHUB_ACTION_PATH/script.sh shell: bash ``` @@ -321,7 +322,7 @@ runs: ### 用于 Docker 操作的 `runs` -**必要** 配置用于 Docker 操作的图像。 +**必要** 配置用于 Docker 操作的图像。 @@ -330,7 +331,7 @@ runs: ```yaml -runs: +runs: using: 'docker' image: 'Dockerfile' ``` @@ -343,7 +344,7 @@ runs: ```yaml -runs: +runs: using: 'docker' image: 'docker://debian:stretch-slim' ``` diff --git a/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 2acf48e01dda2..d355eac3db171 100644 --- a/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -8,6 +8,7 @@ redirect_from: - /actions/building-actions/publishing-actions-in-github-marketplace versions: free-pro-team: '*' +type: 'how_to' --- 您必须接受服务条款才能在 {% data variables.product.prodname_marketplace %} 中发布操作。 diff --git a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md index f98b9ad8d682f..424a4937fae47 100644 --- a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/about-continuous-integration.md b/translations/zh-CN/content/actions/guides/about-continuous-integration.md index 0dfe6383df079..8c7e5af352d52 100644 --- a/translations/zh-CN/content/actions/guides/about-continuous-integration.md +++ b/translations/zh-CN/content/actions/guides/about-continuous-integration.md @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md index f94d639aed51c..3222d22887d9e 100644 --- a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/about-service-containers.md b/translations/zh-CN/content/actions/guides/about-service-containers.md index d2ff9bd4b5d7c..42e392f307713 100644 --- a/translations/zh-CN/content/actions/guides/about-service-containers.md +++ b/translations/zh-CN/content/actions/guides/about-service-containers.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md index 9aac79c2505aa..efb60e9ae4205 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md index 5ae46db35c8ad..8168fcc6cc974 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md index 1bb19a4044a06..6b49fe092c353 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-net.md b/translations/zh-CN/content/actions/guides/building-and-testing-net.md new file mode 100644 index 0000000000000..8ddd5accf2b9a --- /dev/null +++ b/translations/zh-CN/content/actions/guides/building-and-testing-net.md @@ -0,0 +1,248 @@ +--- +title: Building and testing .NET +intro: You can create a continuous integration (CI) workflow to build and test your .NET project. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### 简介 + +This guide shows you how to build, test, and publish a .NET package. + +{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners). + +### 基本要求 + +You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。 + +We recommend that you have a basic understanding of the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn). + +### Starting with the .NET workflow template + +{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet). + +要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup .NET Core SDK ${{ matrix.dotnet }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: {{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Build + run: dotnet build --configuration Release --no-restore + - name: Test + run: dotnet test --no-restore --verbosity normal +``` +{% endraw %} + +### Specifying a .NET version + +To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. + +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). + +#### Using multiple .NET versions + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet ${{ matrix.dotnet-version }} + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + # You can test your matrix by printing the current dotnet version + - name: Display dotnet version + run: dotnet --version +``` +{% endraw %} + +#### Using a specific .NET version + +You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3. + +{% raw %} +```yaml + - name: Setup .NET 3.x + uses: actions/setup-dotnet@v2 + with: + # Semantic version range syntax or exact version of a dotnet version + dotnet-version: '3.x' +``` +{% endraw %} + +### 安装依赖项 + +{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package. + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### 缓存依赖项 + +You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package. + +更多信息请参阅“[缓存依赖项以加快工作流程](/actions/guides/caching-dependencies-to-speed-up-workflows)”。 + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- uses: actions/cache@v2 + with: + path: ~/.nuget/packages + # Look to see if there is a cache hit for the corresponding requirements file + key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }} + restore-keys: | + ${{ runner.os }}-nuget +- name: Install dependencies + run: dotnet add package Newtonsoft.Json --version 12.0.1 +``` +{% endraw %} + +{% note %} + +**注意：**取决于依赖项的数量，使用依赖项缓存可能会更快。 有很多大型依赖项的项目应该能看到性能明显提升，因为下载所需的时间会缩短。 Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. 性能因项目而异。 + +{% endnote %} + +{% endif %} + +### 构建和测试代码 + +您可以使用与本地相同的命令来构建和测试代码。 This example demonstrates how to use `dotnet build` and `dotnet test` in a job: + +{% raw %} +```yaml +steps: +- uses: actions/checkout@v2 +- name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: '3.1.x' +- name: Install dependencies + run: dotnet restore +- name: Build + run: dotnet build +- name: Test with the dotnet CLI + run: dotnet test +``` +{% endraw %} + +### 将工作流数据打包为构件 + +After a workflow completes, you can upload the resulting artifacts for analysis. 例如，您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 The following example demonstrates how you can use the `upload-artifact` action to upload test results. + +更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。 + +{% raw %} +```yaml +name: dotnet package + +on: [push] + +jobs: + build: + + runs-on: ubuntu-latest + strategy: + matrix: + dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + + steps: + - uses: actions/checkout@v2 + - name: Setup dotnet + uses: actions/setup-dotnet@v1.6.0 + with: + dotnet-version: ${{ matrix.dotnet-version }} + - name: Install dependencies + run: dotnet restore + - name: Test with dotnet + run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}" + - name: Upload dotnet test results + uses: actions/upload-artifact@v2 + with: + name: dotnet-results-${{ matrix.dotnet-version }} + path: TestResults-${{ matrix.dotnet-version }} + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} +``` +{% endraw %} + +### 发布到包注册表 + +You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`. + +{% raw %} +```yaml +name: Upload dotnet package + +on: + release: + types: [created] + +jobs: + deploy: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-dotnet@v1 + with: + dotnet-version: '3.1.x' # SDK Version to use. + source-url: https://nuget.pkg.github.com//index.json + env: + NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + - run: dotnet build + - name: Create the package + run: dotnet pack --configuration Release + - name: Publish the package to GPR + run: dotnet nuget push /bin/Release/*.nupkg +``` +{% endraw %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md index 26de7a86f35c8..6769fa2be605c 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +37,11 @@ versions: ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +50,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +58,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,7 +72,7 @@ jobs: `setup-node` 操作采用 Node.js 版本作为输入，并在运行器上配置该版本。 `setup-node` 操作从每个运行器上的工具缓存中查找特定版本的 Node.js，并将必要的二进制文件添加到 `PATH`，这可继续用于作业的其余部分。 使用 `setup-node` 操作是 Node.js 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Node.js 行为一致。 如果使用自托管运行器，则必须安装 Node.js 并将其添加到 `PATH`。 -模板包含一个矩阵策略：用三个 Node.js 版本 8.x、10.x 和 12.x 构建和测试代码，其中“x”是通配符，匹配可用于版本的最新次要版和补丁版。 "x" 是一个通配符，与版本的最新次要版本和修补程序版本匹配。 `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。 +The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. "x" 是一个通配符，与版本的最新次要版本和修补程序版本匹配。 `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。 每个作业都可以使用 `matrix` 上下文访问矩阵 `node-version` 阵列中定义的值。 `setup-node` 操作使用上下文作为 `node-version` 输入。 `setup-node` 操作在构建和测试代码之前使用不同的 Node.js 版本配置每个作业。 有关矩阵策略和上下文的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)”和“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 @@ -77,7 +80,7 @@ jobs: ```yaml strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -115,11 +118,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} 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 e5b28ca34c162..15f0d06c90b60 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 @@ -7,6 +7,7 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md index 37ae706004bfe..3aae7481b7573 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-python.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -132,7 +133,7 @@ jobs: #### 使用特定的 Python 版本 -您可以配置 python 的特定版本。 例如，3.8。 或者，您也可以通过语义版本语法来获得最新的次要版本。 此示例使用 Python 3 最新的次要版本。 +您可以配置 python 的特定版本。 例如，3.8。 Alternatively, you can use semantic version syntax to get the latest minor release. 此示例使用 Python 3 最新的次要版本。 {% raw %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md index 60267aff9795d..b451a5b83655c 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 964a58b8abaab..f1be01c12b250 100644 --- a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,6 +9,7 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' +type: 'tutorial' --- ### 关于缓存工作流程依赖项 diff --git a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md index 107f29ffad619..3400e60c5832e 100644 --- a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md b/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md index 07041c4386f81..0480c254364bd 100644 --- a/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md +++ b/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/index.md b/translations/zh-CN/content/actions/guides/index.md index 35efe5e3857c7..045f218b3c7a9 100644 --- a/translations/zh-CN/content/actions/guides/index.md +++ b/translations/zh-CN/content/actions/guides/index.md @@ -17,54 +17,35 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - hosting_your_own_runners + - create_actions +layout: product-sublanding --- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### 创建自定义持续集成工作流程 - -您可以使用 {% data variables.product.prodname_actions %} 来创建自定义的持续集成 (CI) 工作流程，以构建并测试以不同编程语言编写的项目。 - -{% link_in_list /about-continuous-integration %} -{% link_in_list /setting-up-continuous-integration-using-workflow-templates %} -{% 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 %} - -### 创建自定义持续部署工作流程 - -您可以使用 {% data variables.product.prodname_actions %} 创建自定义连续部署 (CD) 工作流程，将项目部署到多个云合作伙伴生态系统。 - - {% link_in_list /deploying-to-amazon-elastic-container-service %} - {% link_in_list /deploying-to-azure-app-service %} - {% link_in_list /deploying-to-google-kubernetes-engine %} - -### 发布软件包 - -您可以自动发布软件包，作为持续交付 (CD) 工作流程的一部分。 软件包可以发布到任何软件包主机以及 {% data reusables.gated-features.packages %}。 - -{% link_in_list /about-packaging-with-github-actions %} -{% link_in_list /publishing-nodejs-packages %} -{% link_in_list /publishing-java-packages-with-maven %} -{% link_in_list /publishing-java-packages-with-gradle %} -{% link_in_list /publishing-docker-images %} - -### 缓存和存储工作流程数据 - -缓存依赖项和存储构件以提高工作流程运行效率。 - -{% link_in_list /storing-workflow-data-as-artifacts %} -{% link_in_list /caching-dependencies-to-speed-up-workflows %} - -### 在工作流程中使用服务容器 - -使用服务容器将服务连接到您的工作流程。 - -{% link_in_list /about-service-containers %} -{% link_in_list /creating-redis-service-containers %} -{% link_in_list /creating-postgresql-service-containers %} + + + + + + + + + + + + + + + + + + + + + + + diff --git a/translations/zh-CN/content/actions/guides/publishing-docker-images.md b/translations/zh-CN/content/actions/guides/publishing-docker-images.md index daf0b4c1fe2a4..e6aeab7fd8a07 100644 --- a/translations/zh-CN/content/actions/guides/publishing-docker-images.md +++ b/translations/zh-CN/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md index 911b1574a2550..65372e31854d5 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md index d1f30725d3051..8190da631dfe7 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} 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 6c3431e83e15f..cc9d59aa49a45 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -87,9 +88,28 @@ always-auth=true 每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。 -默认情况下，{% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，您要发布一个名为 `@my-org/test` 的包到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅 npm 文档中的 [`npm-scope`](https://docs.npmjs.com/misc/scope)。 +#### Configuring the destination repository -要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中，并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。 +If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. + +However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Authenticating to the destination repository + +To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." + +If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +#### 示例工作流程 此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。 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 e6e6040685fcf..018c15b1887de 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,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md index d5e1ddc82bdce..e0ff4a238059f 100644 --- a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,6 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 3f1808fa473e6..2304c7813cc17 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 958a51dc129c3..b949e2be9aa4d 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -7,11 +7,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +您可以将自托管的运行器添加到 {{ site.data.variables.product.prodname_actions }}。 + +If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. + 如果需要支持自托管运行器的操作系统的信息，或通过代理服务器的自托管运行器，请参阅“[关于自托管运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。 {% warning %} @@ -44,6 +49,8 @@ versions: {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + ### 添加自托管运行器到企业 您可以将自托管运行器添加到企业，在该企业中可以将它们分配给多个组织。 然后，组织管理员能够控制哪些仓库可以使用它。 @@ -52,7 +59,7 @@ versions: 要将自托管的运行器添加到企业帐户，您必须是组织所有者。 {% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} 要在 -{% data variables.product.product_location %} 的企业级添加自托管运行器，您必须是网站管理员。 +{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} @@ -62,3 +69,13 @@ versions: 1. 单击 **Add new（新增）**，然后单击 **New runner（新运行器）**。 新运行器被分配到默认组。 您可以在注册运行器后修改运行器组。 更多信息请参阅“[管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} + +{% data reusables.github-actions.self-hosted-runner-public-repo-access %} + +#### Making enterprise runners available to repositories + +By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization. + +To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization. + +For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index d4468bd9f008b..33b7eb195e1e6 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index cafe8453c0ab8..3b1d6efe96666 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index f38fdfe8c54da..accca577dbe33 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' defaultPlatform: linux --- diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index df8e61e85f594..816985f81b518 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index c7e79007151fb..176352878cf08 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index ab023c5d37fcf..aaa0c1ce6c4ea 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,6 +4,7 @@ intro: 您可以使用标签以基于其特性来组织自托管运行器。 versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 3e81714645fda..57d2d2fdd0a89 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md index a38a150a5c353..41e016dccfc42 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,6 +5,7 @@ intro: '{% data variables.product.prodname_actions %} 旨在帮助您建立强 versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} 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 1aedb779c1bc7..8b339cffc8588 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 @@ -10,6 +10,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -76,7 +77,7 @@ steps: #### 使用分支 -引用特定分支意味着操作将始终使用目标分支上的最新更新，但如果这些更新包括重大更改，则可能会造成问题。 此示例针对名为 `@main`的分支： +Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. 此示例针对名为 `@main`的分支： ```yaml steps: 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 06a2654ede3e2..b1b91b2cbe56e 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 @@ -9,6 +9,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md index 7a92ef605510a..366d26f47829f 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md @@ -5,6 +5,7 @@ intro: '本指南说明如何使用 {% data variables.product.prodname_actions % versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -154,6 +155,15 @@ jobs: 您可以使用保护规则和机密配置环境。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[环境](/actions/reference/environments)”。 {% endif %} +### 使用工作流程模板 + +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. 如果您的仓库已经有工作流程：在左上角单击 **New workflow（新工作流程）**。 ![创建新工作流程](/assets/images/help/repository/actions-new-workflow.png) +1. 在您想要使用的模板名称下，单击 **Set up this workflow（设置此工作流程）**。 ![设置此工作流程](/assets/images/help/settings/actions-create-starter-workflow.png) + ### 后续步骤 要继续了解 {% data variables.product.prodname_actions %}，请参阅“[与组织共享工作流程](/actions/learn-github-actions/sharing-workflows-with-your-organization)”。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 15963c3d2ef57..d80d7fb12071c 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -104,7 +105,7 @@ In Azure Pipelines, scripts can be configured to error if any output is sent to In Azure Pipelines, the default shell for scripts on Windows platforms is the Command shell (_cmd.exe_). In {% data variables.product.prodname_actions %}, the default shell for scripts on Windows platforms is PowerShell. PowerShell has several differences in built-in commands, variable expansion, and flow control. -If you're running a simple command, you might be able to run a Command shell script in PowerShell without any changes. But in most cases, you will either need to update your script with PowerShell syntax or instruct {% data variables.product.prodname_actions %} to run the script with the Command shell instead of PowerShell. You can do this by specifying `shell` as `cmd`. +If you're running a simple command, you might be able to run a Command shell script in PowerShell without any changes. But in most cases, you will either need to update your script with PowerShell syntax or instruct {% data variables.product.prodname_actions %} to run the script with the Command shell instead of PowerShell. You can do this by specifying `shell` as `cmd`. Below is an example of the syntax for each system: @@ -324,4 +325,3 @@ jobs: You can find actions that you can use in your workflow in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Creating actions](/actions/creating-actions)." - diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index fd02f04ef27b6..3f299ece382da 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 51c89c8fa0cfb..0c45970d4048e 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,6 +4,7 @@ intro: '{% data variables.product.prodname_actions %} 和 GitLab CI/CD 具有一 versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index edc9443b15d55..5bb48f709a33c 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- {% data reusables.actions.enterprise-beta %} @@ -166,7 +167,7 @@ Jenkins Pipeline maven-build: env: MAVEN_PATH: '/usr/local/maven' - + ``` @@ -209,7 +210,7 @@ Jenkins Pipeline needs: job1 job3: needs: [job1, job2] - + ``` diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 54b836cab86f9..5dd0564e8161e 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,6 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' --- ### 简介 diff --git a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md index a3f10c7573ac3..e78bdb92591b1 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,6 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 354be580ab48b..3f67ba6102552 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -44,10 +45,10 @@ versions: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据： ```yaml @@ -75,7 +76,7 @@ versions: ![工作流程模板文件](/assets/images/help/images/workflow-template-files.png) -### 使用工作流程模板 +### Using a workflow template from your organization 此程序展示组织成员如何查找并使用工作流程模板来创建新的工作流程。 只要是组织成员，都可以使用组织的工作流程模板。 diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index d482db8316f5e..7e5df38e5b57d 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -66,9 +66,9 @@ versions: {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### 更多入门工作流程 +### More workflow templates -{% data variables.product.prodname_dotcom %} 提供预配置的工作流程模板，您可以从这些模板开始自动执行或创建持续集成工作流程。 您可以在 {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) 仓库{% else %} {% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览工作流程模板的完整列表。 +{% data reusables.actions.workflow-template-overview %} ### 后续步骤 @@ -120,7 +120,7 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. 在左侧边栏中，单击您想要运行的工作流程。 +1. In the left sidebar, click the workflow you want to run. ![选择 say hello 作业](/assets/images/help/repository/say-hello-job.png) 1. 在右侧，单击 **Run workflow（运行工作流程）**下拉菜单，然后单击 **Run workflow（运行工作流程）**。 （可选）您可以在运行工作流程之前在“问候的人（Person to greet）”输入中输入自定义消息。 ![触发手动工作流程](/assets/images/help/repository/manual-workflow-trigger.png) @@ -129,15 +129,15 @@ versions: 1. 在左侧栏中，单击 "say_hello" 作业。 ![工作流程作业列表](/assets/images/help/repository/workflow-job-listing.png) 1. 在工作流程日志中，展开 'Run echo "Hello World!"' 部分。 - ![工作流程详细信息](/assets/images/help/repository/workflow-log-listing.png) + ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### More starter workflows +### More workflow templates -{% data variables.product.prodname_dotcom %} 提供预配置的工作流程模板，可用于开始自动化或创建持续集成工作流程。 您可以在 {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) 仓库{% else %} {% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览工作流程模板的完整列表。 +{% data reusables.actions.workflow-template-overview %} ### Next steps -您刚才添加的 hello-world 工作流程是手动触发的工作流程的简单示例。 这只是您可以对 {% data variables.product.prodname_actions %} 执行操作的开始。 您的仓库可以包含多个基于不同事件触发不同任务的工作流程。 {% data variables.product.prodname_actions %} 可以帮助您自动执行应用程序开发过程的几乎每个方面。 准备好开始了吗？ 下面是一些可帮助您执行 {% data variables.product.prodname_actions %} 后续步骤的有用资源： +The hello-world workflow you just added is a simple example of a manually triggered workflow. 这只是您可以对 {% data variables.product.prodname_actions %} 执行操作的开始。 您的仓库可以包含多个基于不同事件触发不同任务的工作流程。 {% data variables.product.prodname_actions %} 可以帮助您自动执行应用程序开发过程的几乎每个方面。 准备好开始了吗？ 下面是一些可帮助您执行 {% data variables.product.prodname_actions %} 后续步骤的有用资源： - “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，用于深入的教程 - “[Guides](/actions/guides)”，用于特定的使用情况和示例 diff --git a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md index f94651bec68cc..972fec2790fad 100644 --- a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,6 +75,10 @@ env: - 以 `a-Z` 或 `_` 开头。 - 后跟 `a-Z` `0-9` `-` 或 `_`。 +#### Determining when to use contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### `github` 上下文 `github` 上下文包含有关工作流程运行以及触发运行的事件相关信息。 您可以读取环境变量中的大多数 `github` 上下文数据。 有关环境变量的更多信息，请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。 @@ -107,15 +111,14 @@ env: `env` 上下文包含已在工作流程、作业或步骤中设置的环境变量。 有关在工作流程中设置环境变量的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)”。 -`env` 上下文语法允许您在工作流程文件中使用环境变量的值。 如果您想要在运行器中使用环境变量的值，请使用运行器操作系统的正常方法来读取环境变量。 +`env` 上下文语法允许您在工作流程文件中使用环境变量的值。 You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. 有关步骤语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。 -您只能将 `env` 上下文用在 `with` 和 `name` 键值，或用在步骤的 `if` 条件中。 有关步骤语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。 +如果您想要在运行器中使用环境变量的值，请使用运行器操作系统的正常方法来读取环境变量。 | 属性名称 | 类型 | 描述 | | ---------------------- | ----- | -------------------------------------- | | `env` | `对象` | 此上下文针对作业中的每个步骤而改变。 您可以从作业中的任何步骤访问此上下文。 | -| `env.` | `字符串` | 特定环境变量的值。 | - +| `env.` | `字符串` | 特定环境变量的值。 | #### `job` 上下文 diff --git a/translations/zh-CN/content/actions/reference/environment-variables.md b/translations/zh-CN/content/actions/reference/environment-variables.md index cf69ee11e7379..5ad15c65e0df9 100644 --- a/translations/zh-CN/content/actions/reference/environment-variables.md +++ b/translations/zh-CN/content/actions/reference/environment-variables.md @@ -57,6 +57,16 @@ steps: | `GITHUB_API_URL` | 返回 API URL。 返回 {% data variables.product.product_name %} 服务器的 URL。 例如：`https://github.com`。 | | `GITHUB_GRAPHQL_URL` | 返回 GraphQL API URL。 例如：`https://api.github.com/graphql`。 | +{% tip %} + +**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determining when to use default environment variables or contexts + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### 环境变量命名约定 {% note %} 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 a63197d176acd..b2d0f7424ca4d 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 @@ -80,6 +80,8 @@ versions: 您可以使用 [crontab guru](https://crontab.guru/) 帮助生成计划任务语法并确认它在何时运行。 为帮助您开始，我们还提供了一系列 [crontab guru 示例](https://crontab.guru/examples.html)。 +Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." + ### 手动事件 您可以手动触发工作流程运行。 要触发仓库中的特定工作流程，请使用 `workflow_dispatch` 事件。 要触发仓库中的多个工作流程并创建自定义事件和事件类型，请使用 `repository_dispatch` 事件。 @@ -593,7 +595,8 @@ on: 例如，您可以在拉取请求为 `assigned`、`opened`、`synchronize` 或 `reopened` 时运行工作流程。 ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` 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 a6b25c56185ec..bf8e5733bacb8 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 @@ -83,44 +83,11 @@ Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身 {% endnote %} -Windows 和 Ubuntu 运行程序托管在 Azure 中，具有与 Azure 数据中心相同的 IP 地址范围。 目前，所有 Windows 和 Ubuntu {% data variables.product.prodname_dotcom %} 托管的运行器都在以下 Azure 地区： - -- 美国东部 (`eastus`) -- 美国东部 2 (`eastus2`) -- 美国西部 2 (`westus2`) -- 美国中部 (`centralus`) -- 美国中南部 (`southcentralus`) - -Microsoft 每周通过 JSON 文件更新 Azure IP 地址范围，您可以从 [Azure IP 范围和服务标签 - 公共云](https://www.microsoft.com/en-us/download/details.aspx?id=56519)网站下载该文件。 如果需要一个允许列表来阻止未经授权访问您的内部资源，您可以使用此 IP 地址范围。 - -JSON 文件包含一个名为 `values` 的数组。 例如，在该数组内，您可以通过包含 `"AzureCloud.eastus2"` 的 `name` 和 `id` 的对象找到支持的 IP 地址。 - -您可以在 `"addressPrefixes"` 对象中找到支持的 IP 地址范围。 这是 JSON 文件的精简示例。 - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. + +To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. + +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### 文件系统 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 455168e9fdd4a..979993124e0d1 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 @@ -187,7 +187,7 @@ on: ### `env` -环境变量的 `map` 可用于工作流程中的所有作业和步骤。 您还可以设置仅适用于作业或步骤的环境变量。 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv)。 +A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv)。 {% data reusables.repositories.actions-env-var-note %} @@ -639,14 +639,15 @@ jobs: 您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 -| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | -| ------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | -| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | -| 所有 | `python` | 执行 python 命令。 | `python {0}` | -| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | 这是 Windows 上使用的默认 shell。 Desktop PowerShell。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | +| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | +| ------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | +| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | +| 所有 | `python` | 执行 python 命令。 | `python {0}` | +| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | #### 使用 bash 运行脚本的示例 @@ -675,6 +676,15 @@ steps: shell: pwsh ``` +#### Example: Using PowerShell Desktop to run a script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + #### 运行 python 脚本的示例 ```yaml @@ -1149,7 +1159,7 @@ volumes: - `**`： 匹配零个或多个任何字符。 - `?`：匹配零个或一个字符。 例如 `Octoc?t` 匹配 `Octocat`。 - `+`: 匹配一个或多个前置字符。 -- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 例如，范围 `[0-9a-f]` 匹配任何数字或小写字母。 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。 +- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 For example, the range`[0-9a-z]` matches any digit or lowercase letter. 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。 - `!`：在模式开始时，它将否定以前的正模式。 如果不是第一个字符，它就没有特殊的意义。 字符 `*`、`[` 和 `!` 是 YAML 中的特殊字符。 如果模式以 `*`、`[` 或 `!` 开头，必须用引号括住模式。 @@ -1167,35 +1177,35 @@ volumes: #### 匹配分支和标记的模式 -| 模式 | 描述 | 示例匹配 | -| --------------------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | -`feature/my-branch`
            -`feature/your-branch` | -| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | -`feature/beta-a/my-branch`
            -`feature/your-branch`
            -`feature/mona/the/octocat` | -| -`main`
            -`releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | -`main`
            -`releases/mona-the-octocat` | -| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | -`main`
            -`releases` | -| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | -`all/the/branches`
            -`every/tag` | -| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | -`mona-feature`
            -`feature`
            -`ver-10-feature` | -| `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | -`v2`
            -`v2.0`
            -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制标记与主要版本 1 或 2 匹配 | -`v1.10.1`
            -`v2.0.0` | +| 模式 | 描述 | 示例匹配 | +| ------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | `feature/my-branch`

            `feature/your-branch` | +| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | `feature/beta-a/my-branch`

            `feature/your-branch`

            `feature/mona/the/octocat` | +| `main`

            `releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | `main`

            `releases/mona-the-octocat` | +| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`

            `releases` | +| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

            `every/tag` | +| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

            `feature`

            `ver-10-feature` | +| `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | `v2`

            `v2.0`

            `v2.9` | +| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制标记与主要版本 1 或 2 匹配 | `v1.10.1`

            `v2.0.0` | #### 匹配文件路径的模式 路径模式必须匹配整个路径，并从仓库根开始。 -| 模式 | 匹配描述 | 示例匹配 | -| ---------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | -| `'*'` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | -`README.md`
            -`server.rb` | -| `'*.jsx?'` | `?` 个字符匹配零个或一个前缀字符。 | -`page.js`
            -`page.jsx` | -| `'**'` | The `**` 通配符匹配任何字符，包括斜杠 (`/`)。 这是不使用 `path` 过滤器时的默认行为。 | -`all/the/files.md` | -| `'*.js'` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 匹配仓库根目录上的所有 `.js` 文件。 | -`app.js`
            -`index.js` | -| `'**.js'` | 匹配仓库中的所有 `.js` 文件。 | -`index.js`
            -`js/index.js`
            -`src/js/app.js` | -| `文档/*` | 仓库根目录下 `docs` 根目录中的所有文件。 | -`docs/README.md`
            -`docs/file.txt` | -| `文档/**` | 仓库根目录下 `/docs` 目录中的任何文件。 | -`docs/README.md`
            -`docs/mona/octocat.txt` | -| `docs/**/*.md` | `docs` 目录中任意位置具有 `.md` 后缀的文件。 | -`docs/README.md`
            -`docs/mona/hello-world.md`
            -`docs/a/markdown/file.md` | -| `'**/文档/**'` | 仓库中任意位置 `docs` 目录下的任何文件。 | -`/docs/hello.md`
            -`dir/docs/my-file.txt`
            -`space/docs/plan/space.doc` | -| `'**/README.md'` | 仓库中任意位置的 README.md 文件。 | -`README.md`
            -`js/README.md` | -| `'**/*src/**'` | 仓库中任意位置具有 `src` 后缀的文件夹中的任何文件。 | -`a/src/app.js`
            -`my-src/code/js/app.js` | -| `'**/*-post.md'` | 仓库中任意位置具有后缀 `-post.md` 的文件。 | -`my-post.md`
            -`path/their-post.md` | -| `'**/migrate-*.sql'` | 仓库中任意位置具有前缀 `migrate-` 和后缀 `.sql` 的文件。 | -`migrate-10909.sql`
            -`db/migrate-v1.0.sql`
            -`db/sept/migrate-v1.sql` | -| -`*.md`
            -`!README.md` | 模式前使用感叹号 (`!`) 对其进行否定。 当文件与模式匹配并且也匹配文件后面定义的否定模式时，则不包括该文件。 | -`hello.md`
            _Does not match_
            -`README.md`
            -`docs/hello.md` | -| -`*.md`
            -`!README.md`
            -`README*` | 按顺序检查模式。 否定前一个模式的模式将重新包含文件路径。 | -`hello.md`
            -`README.md`
            -`README.doc` | +| 模式 | 匹配描述 | 示例匹配 | +| ----------------------------------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `README.md`

            `server.rb` | +| `'*.jsx?'` | `?` 个字符匹配零个或一个前缀字符。 | `page.js`

            `page.jsx` | +| `'**'` | The `**` 通配符匹配任何字符，包括斜杠 (`/`)。 这是不使用 `path` 过滤器时的默认行为。 | `all/the/files.md` | +| `'*.js'` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 匹配仓库根目录上的所有 `.js` 文件。 | `app.js`

            `index.js` | +| `'**.js'` | 匹配仓库中的所有 `.js` 文件。 | `index.js`

            `js/index.js`

            `src/js/app.js` | +| `文档/*` | 仓库根目录下 `docs` 根目录中的所有文件。 | `docs/README.md`

            `docs/file.txt` | +| `文档/**` | 仓库根目录下 `/docs` 目录中的任何文件。 | `docs/README.md`

            `docs/mona/octocat.txt` | +| `docs/**/*.md` | `docs` 目录中任意位置具有 `.md` 后缀的文件。 | `docs/README.md`

            `docs/mona/hello-world.md`

            `docs/a/markdown/file.md` | +| `'**/文档/**'` | 仓库中任意位置 `docs` 目录下的任何文件。 | `/docs/hello.md`

            `dir/docs/my-file.txt`

            `space/docs/plan/space.doc` | +| `'**/README.md'` | 仓库中任意位置的 README.md 文件。 | `README.md`

            `js/README.md` | +| `'**/*src/**'` | 仓库中任意位置具有 `src` 后缀的文件夹中的任何文件。 | `a/src/app.js`

            `my-src/code/js/app.js` | +| `'**/*-post.md'` | 仓库中任意位置具有后缀 `-post.md` 的文件。 | `my-post.md`

            `path/their-post.md` | +| `'**/migrate-*.sql'` | 仓库中任意位置具有前缀 `migrate-` 和后缀 `.sql` 的文件。 | `migrate-10909.sql`

            `db/migrate-v1.0.sql`

            `db/sept/migrate-v1.sql` | +| `*.md`

            `!README.md` | 模式前使用感叹号 (`!`) 对其进行否定。 当文件与模式匹配并且也匹配文件后面定义的否定模式时，则不包括该文件。 | `hello.md`

            _Does not match_

            `README.md`

            `docs/hello.md` | +| `*.md`

            `!README.md`

            `README*` | 按顺序检查模式。 否定前一个模式的模式将重新包含文件路径。 | `hello.md`

            `README.md`

            `README.doc` | diff --git a/translations/zh-CN/content/admin/authentication/using-saml.md b/translations/zh-CN/content/admin/authentication/using-saml.md index 2403bfc9e06c8..6843880fcc0fb 100644 --- a/translations/zh-CN/content/admin/authentication/using-saml.md +++ b/translations/zh-CN/content/admin/authentication/using-saml.md @@ -46,7 +46,7 @@ versions: ### SAML 元数据 -您的 {% data variables.product.prodname_ghe_server %} 实例的服务提供程序元数据位于 `http(s)://[hostname]/saml/metadata` 下。 +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. 要手动配置您的身份提供程序，断言使用者服务 (ACS) URL 为 `http(s)://[hostname]/saml/consume`。 它使用 `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` 绑定。 diff --git a/translations/zh-CN/content/admin/configuration/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/command-line-utilities.md index e464619972b37..b5bbf5bb12dc5 100644 --- a/translations/zh-CN/content/admin/configuration/command-line-utilities.md +++ b/translations/zh-CN/content/admin/configuration/command-line-utilities.md @@ -468,18 +468,21 @@ ghe-webhook-logs ``` 要显示过去一天所有失败的挂钩交付： +{% if currentVersion ver_gt "enterprise-server@2.22" %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -要显示交付的完整挂钩有效负载、结果以及任何异常： +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} -要显示全局 web 挂钩交付： +要显示交付的完整挂钩有效负载、结果以及任何异常： ```shell -ghe-webhook-logs --global +ghe-webhook-logs -g delivery-guid -v ``` ### 集群 diff --git a/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index 8a453a729239d..60d1071672d01 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ versions: {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. 在 **HTTP Proxy Server** 下，输入代理服务器的 URL。 ![用于输入 HTTP 代理服务器 URL 的字段](/assets/images/enterprise/management-console/http-proxy-field.png) -5. 或者在 **HTTP Proxy Exclusion** 下输入不需要进行代理访问的任意主机，并以逗号分隔主机。 ![输入任何 HTTP 代理排除项的字段](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. 或者在 **HTTP Proxy Exclusion** 下输入不需要进行代理访问的任意主机，并以逗号分隔主机。 To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![输入任何 HTTP 代理排除项的字段](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md index be9e9fe888152..54360a16ad2fe 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ versions: 如果主要站点发生的故障或灾难性事件的时间较长，要还原 {% data variables.product.product_location %}，请提供另一个 {% data variables.product.prodname_enterprise %} 设备并从备份主机执行还原。 在还原设备之前，您必须将备份主机的 SSH 密钥作为已授权 SSH 密钥添加到目标 {% data variables.product.prodname_enterprise %} 设备。 +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + 要通过上一个成功快照还原 {% data variables.product.product_location %}，请使用 `ghe-restore` 命令。 您看到的输出应类似于： ```shell diff --git a/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index b04f61c58ded8..cc2f9fc931c58 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ versions: {% data reusables.enterprise_site_admin_settings.management-console %} 1. 检查左侧边栏中是否有 **{% data variables.product.prodname_advanced_security %}** 条目。 ![高级安全侧边栏](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -如果您在侧边栏中看不到 **{% data variables.product.prodname_advanced_security %}**，这意味着您的许可不支持 {% data variables.product.prodname_advanced_security %} 功能，包括 {% data variables.product.prodname_code_scanning %}。 {% data variables.product.prodname_advanced_security %} 的许可使您和您的用户能够访问那些有助于提高仓库和代码安全性的功能。 +{% data reusables.enterprise_management_console.advanced-security-license %} ### 启用 {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -47,35 +47,42 @@ versions: #### 设置自托管运行器 -如果您参加 {% data variables.product.prodname_actions %} 公测，则 {% data variables.product.prodname_ghe_server %} 可以使用 {% data variables.product.prodname_actions %} 工作流程运行 {% data variables.product.prodname_code_scanning %}。 首先，您需要在环境中预配一个或多个自托管的 {% data variables.product.prodname_actions %} 运行器。 您可以在仓库、组织或企业帐户级别预配自托管运行器。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 +{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. 首先，您需要在环境中预配一个或多个自托管的 {% data variables.product.prodname_actions %} 运行器。 您可以在仓库、组织或企业帐户级别预配自托管运行器。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 您必须确保 Git 在用于运行 {% data variables.product.prodname_codeql %} 操作的任何自托管运行器上的 PATH 变量中。 -#### 预配操作 -要在 {% data variables.product.prodname_ghe_server %} 上使用 {% data variables.product.prodname_actions %} 运行 {% data variables.product.prodname_code_scanning %}，必须在本地可以进行适当的操作。 您可以通过三种方式使操作可用。 +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisioning the actions +To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **推荐** 您可以使用 [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) 自动从 {% data variables.product.prodname_dotcom_the_website %} 下载操作。 托管实例的机器必须能够访问 {% data variables.product.prodname_dotcom_the_website %}。 此方法可确保自动获取最新软件。 更多信息请参阅“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。 +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. 托管实例的机器必须能够访问 {% data variables.product.prodname_dotcom_the_website %}。 此方法可确保自动获取最新软件。 更多信息请参阅“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。 - 如果要使用 {% data variables.product.prodname_codeql_workflow %}，可以使用 [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) 上的 {% data variables.product.prodname_codeql %} 操作同步工具将仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.prodname_ghe_server %}。 无论您的 {% data variables.product.product_location %} 或 {% data variables.product.prodname_actions %} 运行器是否可以访问互联网， 只要您可以同时在计算机上访问 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}，您都可以使用此工具。 -- 您可以通过使用操作克隆仓库，在服务器上创建 {% data variables.product.prodname_dotcom_the_website %} 仓库的本地副本。 例如，如果要使用 {% data variables.product.prodname_codeql %} 操作，可以在实例中创建一个名为 `github/codeql-action` 的仓库，然后从 {% data variables.product.prodname_dotcom_the_website %} 克隆[仓库](https://github.com/github/codeql-action)，再将该仓库推送到实例的 `github/codeql-action` 仓库。 您还需要从 {% data variables.product.prodname_dotcom_the_website %} 上的仓库下载任何发行版，并将它们作为发行版上传到实例的 `github/codeql-action` 仓库。 - +- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. 您还需要从 {% data variables.product.prodname_dotcom_the_website %} 上的仓库下载任何发行版，并将它们作为发行版上传到实例的 `github/codeql-action` 仓库。 ##### 配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %} - 1. 如果要从 {% data variables.product.prodname_dotcom_the_website %} 下载按需操作工作流程，则需要启用 {% data variables.product.prodname_github_connect %}。 更多信息请参阅“[启用 {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)”。 -2. 您还需要为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_actions %}。 更多信息请参阅“[启用 {% data variables.product.prodname_actions %} 和配置存储](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)”。 +2. 您还需要为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_actions %}。 For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. 下一步是使用 {% data variables.product.prodname_github_connect %} 配置对 {% data variables.product.prodname_dotcom_the_website %} 上的操作的访问权限。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 4. 将自托管运行器添加到仓库、组织或企业帐户。 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configuring {% data variables.product.prodname_codeql %} on a server without internet access +If the server on which you are running +{% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} Action sync tool to copy the {% data variables.product.prodname_codeql %} actions and query bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} -在配置自托管运行器后，用户可以对 {% data variables.product.prodname_code_scanning %} 上的单个仓库启用 {% data variables.product.product_location %}。 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 +#### Enabling code scanning for individual repositories +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 ### 使用 {% data variables.product.prodname_codeql_runner %} 运行 {% data variables.product.prodname_code_scanning %} -如果您的组织未参加 {% data variables.product.prodname_actions %} 的测试版，或者您不想使用 {% data variables.product.prodname_actions %}，则可以使用 {% data variables.product.prodname_codeql_runner %} 运行 {% data variables.product.prodname_code_scanning %}。 +If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. 该 {% data variables.product.prodname_codeql_runner %} 是一个命令行工具，您可以将其添加到第三方 CI/CD 系统中。 该工具在 {% data variables.product.prodname_dotcom %} 仓库检出时运行 {% data variables.product.prodname_codeql %} 分析。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。 ### 禁用 {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% data reusables.enterprise_management_console.enable-disable-security-features %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md new file mode 100644 index 0000000000000..311efe8341ed7 --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -0,0 +1,70 @@ +--- +title: Configuring secret scanning for your appliance +shortTitle: Configuring secret scanning +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +product: '{% data reusables.gated-features.secret-scanning %}' +miniTocMaxHeadingLevel: 4 +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} + +### 关于 {% data variables.product.prodname_secret_scanning %} + +{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +### 基本要求 + +To use {% data variables.product.prodname_secret_scanning %} in {% data variables.product.product_location %} you need these two prerequisites. + +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. + +- You need an {% data variables.product.prodname_advanced_security %} license. + +#### Checking support for the SSSE3 flag on your vCPUs + +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. + +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)。” +2. Enter the following command: + +```shell +grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? +``` + +If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling secret scanning](#enabling-secret-scanning)" below. + +If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. + +#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. 检查左侧边栏中是否有 **{% data variables.product.prodname_advanced_security %}** 条目。 ![高级安全侧边栏](/assets/images/enterprise/management-console/sidebar-advanced-security.png) + +{% data reusables.enterprise_management_console.advanced-security-license %} + +### 启用 {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. 在“ +{% data variables.product.prodname_advanced_security %}”下，单击 **{% data variables.product.prodname_secret_scanning_caps %}**。 +![用于启用或禁用 {% data variables.product.prodname_secret_scanning %} 的复选框](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} + +### 禁用 {% data variables.product.prodname_secret_scanning %} + +{% data reusables.enterprise_management_console.enable-disable-security-features %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. 在“ +{% data variables.product.prodname_advanced_security %}”下，取消选择 **{% data variables.product.prodname_secret_scanning_caps %}**。 +![用于启用或禁用 {% data variables.product.prodname_secret_scanning %} 的复选框](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md index 002c1fa208cb1..e1191703b2387 100644 --- a/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ versions: 启用子域隔离后，{% data variables.product.prodname_ghe_server %} 会以子域替代多个路径。 -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} 要将 Docker 与 {% data variables.product.prodname_registry %} 一起使用，您还必须启用子域隔离。 更多信息请参阅“[配置 Docker 与 {% data variables.product.prodname_registry %} 一起使用](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)”。 {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| 未使用子域隔离的路径 | 使用子域隔离的路径 | -| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| （不适用）装有 {% data variables.product.prodname_registry %} 的 Docker 不适用于禁用的子域隔离。 | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| 未使用子域隔离的路径 | 使用子域隔离的路径 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled for the {% data variables.product.prodname_registry %} 2.22 beta. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### 基本要求 diff --git a/translations/zh-CN/content/admin/configuration/index.md b/translations/zh-CN/content/admin/configuration/index.md index 7e2e815484729..7ed1f04345d68 100644 --- a/translations/zh-CN/content/admin/configuration/index.md +++ b/translations/zh-CN/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md new file mode 100644 index 0000000000000..e9e9177ba1deb --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -0,0 +1,26 @@ +--- +title: Managing GitHub for mobile for your enterprise +intro: You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}. +permissions: Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}. +versions: + enterprise-server: '>=3.0' +--- + +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + +### 关于 {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} For more information, see "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." + +Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data. + +### Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/enterprise-management/about-clustering.md b/translations/zh-CN/content/admin/enterprise-management/about-clustering.md index f058d288b2e4f..eea34264810d2 100644 --- a/translations/zh-CN/content/admin/enterprise-management/about-clustering.md +++ b/translations/zh-CN/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ versions: 集群提供了冗余功能，但不适用于替换高可用性配置。 更多信息请参阅[高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)。 主设备/辅助设备故障切换配置远比集群简单，可以满足许多组织的需求。 更多信息请参阅[集群与高可用性之间的差异](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)。 +{% data reusables.package_registry.packages-cluster-support %} + ### 如何获得集群？ 集群针对特定扩展情况而设计，并不一定适用于每个组织。 如果想要考虑集群，请联系您的专业代表或 {% data variables.contact.contact_enterprise_sales %}。 diff --git a/translations/zh-CN/content/admin/enterprise-management/index.md b/translations/zh-CN/content/admin/enterprise-management/index.md index 0f50986a42bf2..6b226c2af6bf5 100644 --- a/translations/zh-CN/content/admin/enterprise-management/index.md +++ b/translations/zh-CN/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md index 67d8f79cbc42b..2e90f9227aebc 100644 --- a/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + + {% endnote %} + {% endif %} diff --git a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md index c4ea77d66b078..cb06da99923cd 100644 --- a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ versions: #### 回滚功能版本 要从功能版本回滚，请从 VM 快照恢复，以确保根分区和数据分区处于一致的状态。 更多信息请参阅“[生成快照](#taking-a-snapshot)”。 + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 延伸阅读 + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file 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 c86d05845b228..e41e576418bd5 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 @@ -59,7 +59,9 @@ $ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt - `configuration-logs/ghe-config.log`：{% data variables.product.prodname_ghe_server %} 配置日志 - `collectd/logs/collectd.log`：Collectd 日志 - `mail-logs/mail.log`：SMTP 电子邮件交付日志 +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`：Web 挂钩交付错误 +{% endif %} 更多信息请参阅“[审核日志](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)”。 diff --git a/translations/zh-CN/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md new file mode 100644 index 0000000000000..d4029836e4e51 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -0,0 +1,38 @@ +--- +title: About using actions on GitHub Enterprise Server +intro: '{% data variables.product.prodname_ghe_server %} 包含了大多数 {% data variables.product.prodname_dotcom %} 编写的操作，并且有选项允许访问来自 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_marketplace %} 的其他操作。' +redirect_from: + - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server + - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。 + +{% data reusables.actions.enterprise-no-internet-actions %} + +### {% data variables.product.prodname_ghe_server %} 随附的官方操作 + +大多数官方 {% data variables.product.prodname_dotcom %} 编写的操作都会自动与 {% data variables.product.prodname_ghe_server %} 捆绑在一起，并且会在某个时间点从 {% data variables.product.prodname_marketplace %} 获取。 When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. + +捆绑的官方操作包括 `actions/checkout`、`actions/upload-artifact`、`actions/download-artifact`、`actions/labeler` 以及各种 `actions/setup-` 操作等。 To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. + +每个操作都是 `actions` 组织中的一个仓库，并且每个操作仓库都包含必要的标记、分支和提交 SHA，您的工作流程可以使用它们来引用操作。 + +{% note %} + +**注：**在包含自托管运行器的 {% data variables.product.prodname_ghe_server %} 上使用设置操作（例如 `actions/setup-LANGUAGE`）时，您可能需要在没有连接互联网的运行器上设置工具缓存。 更多信息请参阅“[在没有互联网连接的自托管运行器上设置工具缓存](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)”。 + +{% endnote %} + +### 配置对 {% data variables.product.prodname_dotcom_the_website %} 上操作的访问权限 + +如果企业实例上的用户需要访问来自 {% data variables.product.prodname_dotcom_the_website %} 或 {% data variables.product.prodname_marketplace %} 的其他操作，有几个配置选项。 + +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 {% data reusables.actions.enterprise-limit-actions-use %} + +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. 更多信息请参阅“[手动同步来自 {% data variables.product.prodname_dotcom_the_website %} 的操作](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)”。 diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting.md new file mode 100644 index 0000000000000..ca8cd4f13168c --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -0,0 +1,8 @@ +--- +title: Advanced configuration and troubleshooting +intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=3.0' +--- + diff --git a/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md new file mode 100644 index 0000000000000..a2556020e8d72 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -0,0 +1,22 @@ +--- +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +versions: + enterprise-server: '>=3.0' +--- + +{% data reusables.actions.enterprise-storage-ha-backups %} + +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. + +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: + +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. +1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 387f901200b7e..a31688d2ac88a 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: 默认情况下，{% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_actions %} 工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 或 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。 -要使 {% data variables.product.prodname_dotcom_the_website %} 上的所有操作可用于您的企业实例，您可以使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}。 有关访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的其他方式，请参阅“[关于 {% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)”。 +To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." ### 启用对所有 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问 @@ -23,3 +23,4 @@ versions: {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 1. 在“Server can use actions from GitHub.com in workflows runs（服务器在工作流程运行中可以使用 GitHub.com 上的操作）”下，使用下拉菜单选择 **Enabled（已启用）**。 ![工作流程运行中用于访问 GitHub.com 上操作的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..097155565b393 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -0,0 +1,8 @@ +--- +title: Enabling GitHub Actions for GitHub Enterprise Server +intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +mapTopic: true +versions: + enterprise-server: '>=2.22' +--- + diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md new file mode 100644 index 0000000000000..4f5c878e761c7 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with Amazon S3 storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +permissions: '站点管理员可以启用 {% data variables.product.prodname_actions %} 并配置企业设置。' +versions: + enterprise-server: '>=3.0' +--- + +### 基本要求 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md new file mode 100644 index 0000000000000..35a61fd893414 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -0,0 +1,35 @@ +--- +title: Enabling GitHub Actions with Azure Blob storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +permissions: '站点管理员可以启用 {% data variables.product.prodname_actions %} 并配置企业设置。' +versions: + enterprise-server: '>=3.0' +--- + +### 基本要求 + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: + * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + + {% warning %} + + **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + + {% endwarning %} + * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + + For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md new file mode 100644 index 0000000000000..540e123638a78 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -0,0 +1,36 @@ +--- +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +permissions: '站点管理员可以启用 {% data variables.product.prodname_actions %} 并配置企业设置。' +versions: + enterprise-server: '>=3.0' +--- + +### 基本要求 + +{% data reusables.actions.enterprise-s3-support-warning %} + +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: + +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. +* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} + +{% data reusables.actions.enterprise-common-prereqs %} + +### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: + + * **AWS Service URL**: The URL to your MinIO service. 例如，`https://my-minio.example:9000`。 + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% data reusables.actions.enterprise-postinstall-nextsteps %} 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 542018e046346..1822dfc660644 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 @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### 关于企业的 {% data variables.product.prodname_actions %} 权限 diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md new file mode 100644 index 0000000000000..a284dbad9e240 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -0,0 +1,96 @@ +--- +title: Getting started with GitHub Actions for GitHub Enterprise Server +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +permissions: '站点管理员可以启用 {% data variables.product.prodname_actions %} 并配置企业设置。' +redirect_from: + - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage + - /admin/github-actions/enabling-github-actions-and-configuring-storage +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} +{% note %} + +**注：**{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 查看下面的外部存储要求并[注册测试版](https://resources.github.com/beta-signup/)。 + +{% endnote %} +{% endif %} + +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. + +### Review hardware considerations + +{% data reusables.actions.enterprise-hardware-considerations %} + +{% endif %} + +### External storage requirements + +要在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}，您必须有权访问外部 Blob 存储。 + +{% data variables.product.prodname_actions %} 使用 Blob 存储来存储工作流程运行生成的构件，如工作流程日志和用户上传的构建构件。 所需存储量取决于您使用 {% data variables.product.prodname_actions %} 的情况。 Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. + +{% data variables.product.prodname_actions %} 支持以下存储提供商： + +* Azure Blob 存储 +* Amazon S3 +* S3 兼容的 MinIO Gateway for NAS + +{% note %} + +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. + +{% endnote %} + +{% if currentVersion == "enterprise-server@2.22" %} + +#### Amazon S3 权限 + +{% data reusables.actions.enterprise-s3-permission %} + +### 启用 {% data variables.product.prodname_actions %} + +{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 [注册测试版](https://resources.github.com/beta-signup/)。 + +### 延伸阅读 + +- “[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)”中平台的“硬件考量因素”。 + +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +### Enabling {% data variables.product.prodname_actions %} with your storage provider + +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: + +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) + +### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise + +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." + +### 添加自托管的运行器 + +{% data reusables.actions.enterprise-github-hosted-runners %} + +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 + +### Managing which actions can be used in your enterprise + +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. + +For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." + +### General security hardening for {% data variables.product.prodname_actions %} + +If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)." + +{% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md b/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md new file mode 100644 index 0000000000000..5fa3bcda7c61a --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md @@ -0,0 +1,29 @@ +--- +title: High availability for GitHub Actions +intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +versions: + enterprise-server: '>=3.0' +--- + +### Replication or redundancy of your {% data variables.product.prodname_actions %} data + +{% data reusables.actions.enterprise-storage-ha-backups %} + +We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: + +* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) + +### High availability replicas + +#### Promoting a replica + +When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. + +For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." + +#### 移除高可用性副本 + +Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. + +To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. diff --git a/translations/zh-CN/content/admin/github-actions/index.md b/translations/zh-CN/content/admin/github-actions/index.md index b232c3ec2dbc4..672a5f9f8c4c8 100644 --- a/translations/zh-CN/content/admin/github-actions/index.md +++ b/translations/zh-CN/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### 目录 -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} 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 758369d4a5293..531d5feb68beb 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 @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -要使 {% data variables.product.prodname_dotcom_the_website %} 中的特定操作可用于工作流程，您可以使用 {% data variables.product.company_short %} 的开源 [`actions-sync`](https://github.com/actions/actions-sync) 工具将操作仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业实例。 有关访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的其他方式，请参阅“[关于 {% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)”。 +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 + +However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. ### 关于 `actions-sync` 工具 diff --git a/translations/zh-CN/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md new file mode 100644 index 0000000000000..7af208d0e49f0 --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' +versions: + enterprise-server: '>=3.0' +--- + +### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} + +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + +#### Installing the certificate on the runner machine + +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. + +For the steps required to install a certificate, refer to the documentation for your runner's operating system. + +#### Configuring Node.JS to use the certificate + +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. + +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +例如： + +```shell +NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt +``` + +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. + +#### Configuring Docker containers to use the certificate + +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. + +### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} + +{% data reusables.actions.enterprise-http-proxy %} + +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. + +### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname + +If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. + +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: + +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. 更多信息请参阅“[删除自托管的运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 + +### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits + +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.product.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. + +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. + +#### 1. Check the overall CPU and memory usage in the management console + +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." + +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.product.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." + +#### 2. Check the Nomad Jobs CPU and memory usage in the management console + +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. + +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: + +* `mps_frontend` +* `mps_backend` +* `token_frontend` +* `token_backend` +* `actions_frontend` +* `actions_backend` + +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. + +#### 3. Increase the resource allocation for services at their limit + +1. Log in to the administrative shell using SSH. 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)。” +1. Run the following command to see what resources are available for allocation: + + ```shell + nomad node status -self + ``` + + In the output, find the "Allocated Resources" section. It looks similar to the following example: + + ``` + Allocated Resources + CPU Memory Disk + 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB + ``` + + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. + + {% warning %} + + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + + {% endwarning %} +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: + + ```shell + cd /etc/consul-templates/etc/nomad-jobs/actions + ``` + + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + + * `mps.hcl.ctmpl` + * `token.hcl.ctmpl` + * `actions.hcl.ctmpl` +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: + + ``` + resources { + cpu = 512 + memory = 2048 + network { + port "http" { } + } + } + ``` + + The values are in MHz for CPU resources, and MB for memory resources. + + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: + + ``` + resources { + cpu = 1024 + memory = 4096 + network { + port "http" { } + } + } + ``` +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. + + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. diff --git a/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md b/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md new file mode 100644 index 0000000000000..60e85acc4346c --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md @@ -0,0 +1,27 @@ +--- +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +versions: + enterprise-server: '>=3.0' +--- + +It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. + +A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. + +When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. + +Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. + +Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. + +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). 例如： + + ```shell + azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive + ``` +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). 例如： + + ```shell + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + ``` diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-aws.md index 3e8b108fa7ea8..97e97311d9f3e 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ aws ec2 run-instances \ ### 延伸阅读 -- "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-azure.md index b4267d391c52d..b6157631677bd 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ versions: {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### 延伸阅读 - ### 延伸阅读 - - - "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index ca42c161178bf..bbb6d95828af7 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ GCE 虚拟机作为具有防火墙的网络的成员创建。 对于与 {% data ### 延伸阅读 -- "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index a0f40695389f3..53c7c03a97dc9 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### 延伸阅读 - - "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 37962cec9b0ea..65dbcb1d8925c 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ versions: ### 延伸阅读 - - "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 68c533c690753..844f9aa75bfa1 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### 延伸阅读 - - "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 4e5e59cae9587..2807a5a0fb3e3 100644 --- a/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/zh-CN/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### 延伸阅读 - - "[系统概述](/enterprise/admin/guides/installation/system-overview)" +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md b/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md index c90d710e4bdcb..a88fc4064f996 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ versions: 1. 使用 {% data variables.product.prodname_enterprise_backup_utilities %} 执行生产实例备份。 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)”的“关于 {% data variables.product.prodname_enterprise_backup_utilities %} ”部分。 2. 设置新实例作为暂存环境。 配置和安装暂存实例的方法与生产实例所用方法相同。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)”。 3. 在暂存实例上还原备份。 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)”的“还原备份”部分。 + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### 延伸阅读 + +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md new file mode 100644 index 0000000000000..d4a3a0caee40f --- /dev/null +++ b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md @@ -0,0 +1,33 @@ +--- +title: About upgrades to new releases +shortTitle: About upgrades +intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +versions: + enterprise-server: '>=3.0' +--- + +{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. + +Major releases include new functionality and feature upgrades and typically occur quarterly. + +Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. + +You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." + +Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." + +We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. + +{% warning %} + +**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." + +{% endwarning %} + +Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. + +To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." + +### 延伸阅读 + +- `github/roadmap` 仓库中的 [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) diff --git a/translations/zh-CN/content/admin/overview/index.md b/translations/zh-CN/content/admin/overview/index.md index 4d29f3b3c3109..d415cc1e5ba9a 100644 --- a/translations/zh-CN/content/admin/overview/index.md +++ b/translations/zh-CN/content/admin/overview/index.md @@ -15,5 +15,6 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md new file mode 100644 index 0000000000000..333a7e6d00d12 --- /dev/null +++ b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -0,0 +1,47 @@ +--- +title: Configuring package ecosystem support for your enterprise +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +redirect_from: + - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise + - /admin/packages/configuring-packages-support-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Enabling or disabling individual package ecosystems + +To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. + +{% if currentVersion == "enterprise-server@2.22" %} +To use +{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. 更多信息请参阅“[启用子域隔离](/enterprise/admin/configuration/enabling-subdomain-isolation)”。 +{% endif %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +1. 在“Ecosystem Toggles（生态系统切换）”下，为每个包类型选择 **Enabled（启用）**、**Read-Only（只读）**或 **Disabled（禁用）**。 ![生态系统切换](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) +{% data reusables.enterprise_management_console.save-settings %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Connecting to the official NPM registry + +If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. + +{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. + +To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: + +| Source | Destination | 端口 | 类型 | +| -------------------------------------------------- | -------------------- | ------- | ----- | +| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | + +Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. + +{% endif %} + +### 后续步骤 + +As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md new file mode 100644 index 0000000000000..6a3188f585d7b --- /dev/null +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md @@ -0,0 +1,60 @@ +--- +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**警告：** +- It is critical that you configure any restrictive access policies you need 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 to 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. +- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 +- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 + +{% endwarning %} + +### 基本要求 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). + +Ensure your AWS access key ID and secret have the following permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with AWS external storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. 在“AWS Service URL（AWS 服务 URL）”下，请为存储桶的区域键入S3 端点 URL。 ![AWS 服务 URL 字段](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. 在“AWS S3 Bucket（AWS S3 存储桶）”下，键入您想要用来存储软件包工件的 S3 存储桶。 ![AWS S3 存储桶字段](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. 在“AWS S3 Access Key（AWS S3 访问密钥）”下，键入 S3 的访问密钥。 ![AWS S3 访问密钥字段](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. 在“AWS S3 Secret Key（AWS S3 密码密钥”下，请输入 S3 的密码密钥。 ![AWS S3 密码密钥字段](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. 在“AWS S3 Region（AWS S3 区域）”下，键入 S3 的区域。 ![AWS S3 区域字段](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. + + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 后续步骤 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md new file mode 100644 index 0000000000000..dbb5a4d856ac0 --- /dev/null +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -0,0 +1,33 @@ +--- +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +versions: + enterprise-server: '>=3.0' +--- + +{% warning %} + +**警告：** +- It is critical that you set the restrictive access policies you need 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. 例如，如果将存储桶设为公共，则在公共互联网上可以访问存储桶中的数据。 +- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 +- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 + +{% endwarning %} + +### 基本要求 + +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). + +### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) + +{% data reusables.enterprise_management_console.save-settings %} + +### 后续步骤 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md new file mode 100644 index 0000000000000..6984b282ad441 --- /dev/null +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md @@ -0,0 +1,56 @@ +--- +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +versions: + enterprise-server: '>=2.22' +--- + +{% warning %} + +**警告：** +- It is critical that you set the restrictive access policies you need 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. 例如，如果将存储桶设为公共，则在公共互联网上可以访问存储桶中的数据。 +- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 +- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。 + +{% endwarning %} +### 基本要求 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." + +Ensure your MinIO external storage access key ID and secret have these permissions: + - `s3:PutObject` + - `s3:GetObject` + - `s3:ListBucketMultipartUploads` + - `s3:ListMultipartUploadParts` + - `s3:AbortMultipartUpload` + - `s3:DeleteObject` + - `s3:ListBucket` + +### Enabling {% data variables.product.prodname_registry %} with MinIO external storage + +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +{% if currentVersion == "enterprise-server@2.22" %} +1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![AWS 服务 URL 字段](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![AWS S3 存储桶字段](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Under "AWS S3 Access Key", type your access key for MinIO. ![AWS S3 访问密钥字段](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![AWS S3 密码密钥字段](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Under "AWS S3 Region", type your region for MinIO. ![AWS S3 区域字段](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. + + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} + +### 后续步骤 + +{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md new file mode 100644 index 0000000000000..9feb07d0da406 --- /dev/null +++ b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -0,0 +1,49 @@ +--- +title: Getting started with GitHub Packages for your enterprise +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +redirect_from: + - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise + - /admin/packages/enabling-github-packages-for-your-enterprise +versions: + enterprise-server: '>=2.22' +--- + +{% if currentVersion == "enterprise-server@2.22" %} + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% note %} + +**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.packages-cluster-support %} + +### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage + +{% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_registry %} 使用外部 Blob 存储来存储您的软件包。 + +After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. + +Supported external storage providers +- Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} +- Azure Blob Storage {% endif %} +- MinIO + +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" + +### Step 2: Specify the package ecosystems to support on your instance + +Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +### Step 3: Ensure you have a TLS certificate for your package host URL, if needed + +If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. 确保每个软件包主机 URL 包含 `https:///`。 + + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. 有关包主机 URL 的更多信息，请参阅“[启用子域隔离](/enterprise/admin/configuration/enabling-subdomain-isolation)”。 有关将 TLS 证书上载到 {% data variables.product.product_name %} 的更多信息，请参阅“[配置 TLS](/enterprise/admin/configuration/configuring-tls)”。 diff --git a/translations/zh-CN/content/admin/packages/index.md b/translations/zh-CN/content/admin/packages/index.md index a063b109e8583..b00a4f99481c0 100644 --- a/translations/zh-CN/content/admin/packages/index.md +++ b/translations/zh-CN/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md new file mode 100644 index 0000000000000..460efb1611157 --- /dev/null +++ b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -0,0 +1,132 @@ +--- +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +versions: + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前，您必须准备第三方存储解决方案。 + +MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.product.prodname_registry %}。 + +此快速入门将演示如何使用 Docker 设置 MinIO 以与 {% data variables.product.prodname_registry %} 使用，但除了 Docker 之外，您还有其他用于管理 MinIO 的选项。 有关 MinIO 的更多信息，请参阅官方的 [MinIO 文档](https://docs.min.io/)。 + +### 1. 根据您的需求选择 MinIO 模式 + +| MinIO 模式 | 针对以下平台优化 | 需要存储基础架构 | +| ----------------------- | ----------- | ------------ | +| 独立 MinIO（在单个主机上） | 快速设置 | 不适用 | +| MinIO 作为 NAS 网关 | NAS（网络连接存储） | NAS 设备 | +| 群集式 MinIO（也称为分布式 MinIO） | 数据安全 | 在群集中运行的存储服务器 | + +有关您的选项的更多信息，请参阅官方的 [MinIO 文档](https://docs.min.io/)。 + +### 2. 安装、运行和登录到 MinIO + +1. 为 MinIO 设置首选环境变量。 + + 以下示例使用 `MINIO_DIR`： + ```shell + $ export MINIO_DIR=$(pwd)/minio + $ mkdir -p $MINIO_DIR + ``` + +2. 安装 MinIO。 + + ```shell + $ docker pull minio/minio + ``` + 更多信息请参阅官方的“[MinIO 快速入门指南](https://docs.min.io/docs/minio-quickstart-guide)”。 + +3. 使用您的 MinIO 访问密钥登录 MinIO。 + + {% linux %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endlinux %} + + {% mac %} + ```shell + $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + # this one is actually a secret, so careful + $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) + ``` + {% endmac %} + + 您可以使用环境变量访问 MinIO 密钥： + + ```shell + $ echo $MINIO_ACCESS_KEY + $ echo $MINIO_SECRET_KEY + ``` + +4. 在您选择的模式下运行 MinIO。 + + * 在单一主机上使用 Docker 运行 MinIO： + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio server /data + ``` + + 更多信息请参阅“[MinIO Docker 快速入门指南](https://docs.min.io/docs/minio-docker-quickstart-guide.html)”。 + + * 使用 Docker 作为 NAS 网关运行 MinIO： + + 此设置对于已经有 NAS 用作 {% data variables.product.prodname_registry %} 的备份存储的部署非常有用。 + + ```shell + $ docker run -p 9000:9000 \ + -v $MINIO_DIR:/data \ + -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \ + -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \ + minio/minio gateway nas /data + ``` + + 更多信息请参阅“[NAS 的 MinIO 网关](https://docs.min.io/docs/minio-gateway-for-nas.html)”。 + + * 使用 Docker 作为集群运行 MinIO： 此 MinIO 部署使用多个主机和 MinIO 的擦除编码来提供最强的数据保护。 要在群集模式下运行 MinIO，请参阅“[分布式 MinIO 快速入门指南](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)”。 + +### 3. 为 {% data variables.product.prodname_registry %} 创建 MinIO 存储桶 + +1. 安装 MinIO 客户端。 + + ```shell + $ docker pull minio/mc + ``` + +2. 使用 {% data variables.product.prodname_ghe_server %} 可以访问的主机 URL 创建存储桶。 + + * 本地部署示例： + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" + $ docker run minio/mc BUCKET-NAME + ``` + + 此示例可用于 MinIO 单机版或作为 NAS 网关的 MinIO。 + + * 集群部署示例： + + ```shell + $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" + $ docker run minio/mc mb packages + ``` + +### 后续步骤 + +要完成 {% data variables.product.prodname_registry %} 的存储配置，您需要复制 MinIO 存储 URL： + + ``` + echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" + ``` + +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." 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 72c7fad1fbbd3..eda254a8bd0d4 100644 --- a/translations/zh-CN/content/admin/user-management/audited-actions.md +++ b/translations/zh-CN/content/admin/user-management/audited-actions.md @@ -107,32 +107,36 @@ versions: #### 团队 -| 名称 | 描述 | -| --------------:| --------------- | -| `team.create` | 已向团队添加用户帐户或仓库。 | -| `team.delete` | 已从团队中移除用户帐户或仓库。 | -| `team.destroy` | 已删除团队。 | +| 名称 | 描述 | +| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | 已向团队添加用户帐户或仓库。 | +| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} +| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} + #### 用户 -| 名称 | 描述 | -| ---------------------------:| ------------------------------------------------------------------------------------------ | -| `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` | 站点管理员已取消挂起用户帐户。 | +| 名称 | 描述 | +| -------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `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 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 47be845fbd49a..b32d948cb163f 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 @@ -4,13 +4,18 @@ 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: '您可以创建用户将在{% if enterpriseServerVersions contains currentVersion %} 登录和注销页面{% else %} 注销页面{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} 或每个页面顶部的公告横幅中{% endif %} 看到的自定义消息。' +intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -您可以使用 Markdown 格式化消息。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/articles/about-writing-and-formatting-on-github/)”。 +### About user messages + +There are several types of user messages. +- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Announcement banners, which appear at the top of every page{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ versions: {% endnote %} +您可以使用 Markdown 格式化消息。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/articles/about-writing-and-formatting-on-github/)”。 + ### 创建自定义登录消息 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. 在“Sign in page”下，单击 **Add message** 或 **Edit message**。 ![Edit message 按钮](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. 在 **Sign in message** 下，输入您想要用户看到的消息。 ![登录消息](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. 在 **Sign in message** 下，输入您想要用户看到的消息。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview 按钮](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. 预览呈现的消息。 ![呈现的登录消息](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### 创建自定义退出消息 @@ -37,12 +45,35 @@ versions: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. 在“Sign out page”下，单击 **Add message** 或 **Edit message**。 ![Add message 按钮](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. 在 **Sign out message** 下，输入您想要用户看到的消息。 ![签名 two_factor_auth_header 消息](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Add message 按钮](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. 在 **Sign out message** 下，输入您想要用户看到的消息。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Preview 按钮](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. 预览呈现的消息。 ![呈现的注销消息](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Creating a mandatory message + +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. + +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} + +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. + +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. ![Add message 按钮](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. ![Add message 按钮](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### 创建全局公告横幅 @@ -50,9 +81,8 @@ versions: 您可以设置全局公告横幅，以便在每个页面顶部向所有用户显示。 {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -您也可以{% 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)”。 - +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. 更多信息请参阅 {% if enterpriseServerVersions contains currentVersion %}“[命令行实用工具](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”和 {% endif %}“[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)”。 {% else %} 您还可以使用命令行工具在管理 shell 中设置公告横幅。 更多信息请参阅“[命令行实用程序](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”。 @@ -62,9 +92,8 @@ versions: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. 在“Sign out page”下，单击 **Add message** 或 **Edit message**。 ![Add message 按钮](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Add message 按钮](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. 在“Announcement（公告）”下的在文本字段中键入要显示在横幅中的公告。 ![用于输入公告的文本字段](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. （可选）在“Expires on（到期日）”下，使用日历下拉菜单选择一个到期日。 ![用于选择到期日期的日历下拉菜单](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. 在“Sign in page”下，单击 **Add message** 或 **Edit message**。 ![Preview 按钮](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. 单击 **Save changes（保存更改）**。 ![Edit message 按钮](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![用于选择到期日期的日历下拉菜单](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md index 28b15cd200738..49d058670c237 100644 --- a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ versions: ##### 参数 -| 名称 | 类型 | 描述 | -| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_github_app %} 的客户端 ID。 | -| `client_secret` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_github_app %} 的客户端密钥。 | -| `代码` | `字符串` | **必填。**您收到的响应第 1 步的代码。 | -| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 | -| `state` | `字符串` | 您在第 1 步提供的不可猜测的随机字符串。 | +| 名称 | 类型 | 描述 | +| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------ | +| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 | +| `client_secret` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端密钥。 | +| `代码` | `字符串` | **必填。**您收到的响应第 1 步的代码。 | +| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 | +| `state` | `字符串` | 您在第 1 步提供的不可猜测的随机字符串。 | ##### 响应 @@ -213,7 +213,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### 设备流程的速率限制 -当用户在浏览器上提交验证码时，每个应用程序在一个小时内的提交速率限制为 50 个。 +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. 如果您在请求之间所需的最短时间段（或 `interval`）内发出多个访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`)，您将达到速率限制并收到 `slow_down` 错误响应。 `slow_down` 错误响应将给最近的`间隔`增加 5 秒。 更多信息请参阅“[设备流程的错误](#errors-for-the-device-flow)”。 diff --git a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md index a543940b63793..655dc278f03ea 100644 --- a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ CI 服务器托管运行 CI 测试的代码，如代码语法检查（检查样 [检查 API](/rest/reference/checks) 允许您设置针对仓库中的每个代码提交自动运行的 CI 测试。 检查 API 在拉取请求的 **Checks（检查）**选项卡中报告 GitHub 上每个检查的详细信息。 使用检查 API，您可以创建带有特定代码行附加细节的注释。 注释在 **Checks（检查）**选项卡中可见。 当您为拉取请求中的文件创建注释时，注释也会显示在 **Files changed（文件已更改）**选项卡中。 -_检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行都包含 GitHub 上的拉取请求中可见的_状态_。 您可以使用状态来确定何时代码提交引入错误。 对[受保护分支](/rest/reference/repos#branches)使用这些状态可防止用户草率地合并拉取请求。 更多信息请参阅“[启用必需状态检查](/articles/enabling-required-status-checks/)”。 +_检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行都包含 GitHub 上的拉取请求中可见的_状态_。 您可以使用状态来确定何时代码提交引入错误。 对[受保护分支](/rest/reference/repos#branches)使用这些状态可防止用户草率地合并拉取请求。 See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. 每当有新代码推送到仓库时，检查 API 会将 [`check_suite` web 挂钩事件](/webhooks/event-payloads/#check_suite)发送到仓库中安装的所有 GitHub 应用程序。 要接收所有检查 API 事件操作，应用程序必须具有 `checks:write` 权限。 GitHub 使用默认流程自动为仓库中的新代码提交创建 `check_suite` 事件，但您可以根据需要[更新检查套件的仓库首选项](/rest/reference/checks#update-repository-preferences-for-check-suites)。 以下是默认流程的工作方式： diff --git a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md index fa4937a0cbb12..f961f5cde1041 100644 --- a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### 可用作用域 -| 名称 | 描述 | -| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 名称 | 描述 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`（无作用域）`** | 授予对公共信息的只读访问权限（包括公开的用户个人资料、公共仓库信息和 gist）{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | 授予站点管理员对 [{% data variables.product.prodname_ghe_server %} 管理 API 端点](/rest/reference/enterprise-admin)的访问权限。{% endif %} -| **`repo`** | 授予对私有和公共仓库的完全访问权限。 这包括对公共和私有仓库及组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 | -|  `repo:status` | 授予对公共和私有仓库提交状态的读取/写入权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | -|  `repo_deployment` | 授予对公共和私有仓库[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | -|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。 | +| **`repo`** | 授予对私有和公共仓库的完全访问权限。 这包括对公共和私有仓库及组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 | +|  `repo:status` | 授予对公共和私有仓库提交状态的读取/写入权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `repo_deployment` | 授予对公共和私有仓库[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。 | |  `repo:invite` | 授予接受/拒绝仓库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | 授予：
            对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。
            对 [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) 中安全事件的读取和写入权限。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | 授予对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。{% endif %} -| **`admin:repo_hook`** | 授予对公共和私有仓库中仓库挂钩的读取、写入、ping 和删除权限。 `repo` 和 `public_repo` 作用域授予对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 | -|  `write:repo_hook` | 授予对公共或私有仓库中挂钩的读取、写入和 ping 权限。 | -|  `read:repo_hook` | 授予对公共或私有仓库中挂钩的读取和 ping 权限。 | -| **`admin:org`** | 全面管理组织及其团队、项目和成员。 | -|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 | -|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 | -| **`admin:public_key`** | 全面管理公钥。 | -|  `write:public_key` | 创建、列出和查看公钥的详细信息。 | -|  `read:public_key` | 列出和查看公钥的详细信息。 | -| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 | -| **`gist`** | 授予对 gist 的写入权限。 | -| **`通知`** | 授予：
            * 对用户通知的读取权限
            * 对线程的标记读取权限
            * 对仓库的关注和取消关注权限，以及
            * 对线程订阅的读取、写入和删除权限。 | -| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 | -|  `read:user` | 授予读取用户个人资料数据的权限。 | -|  `user:email` | 授予对用户电子邮件地址的读取权限。 | -|  `user:follow` | 授予关注或取消关注其他用户的权限。 | -| **`delete_repo`** | 授予删除可管理仓库的权限。 | -| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | +|  `security_events` | Grants:
            read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
            read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
            This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +| **`admin:repo_hook`** | 授予对公共和私有仓库中仓库挂钩的读取、写入、ping 和删除权限。 `repo` 和 `public_repo` 作用域授予对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 | +|  `write:repo_hook` | 授予对公共或私有仓库中挂钩的读取、写入和 ping 权限。 | +|  `read:repo_hook` | 授予对公共或私有仓库中挂钩的读取和 ping 权限。 | +| **`admin:org`** | 全面管理组织及其团队、项目和成员。 | +|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 | +|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 | +| **`admin:public_key`** | 全面管理公钥。 | +|  `write:public_key` | 创建、列出和查看公钥的详细信息。 | +|  `read:public_key` | 列出和查看公钥的详细信息。 | +| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 | +| **`gist`** | 授予对 gist 的写入权限。 | +| **`通知`** | 授予：
            * 对用户通知的读取权限
            * 对线程的标记读取权限
            * 对仓库的关注和取消关注权限，以及
            * 对线程订阅的读取、写入和删除权限。 | +| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 | +|  `read:user` | 授予读取用户个人资料数据的权限。 | +|  `user:email` | 授予对用户电子邮件地址的读取权限。 | +|  `user:follow` | 授予关注或取消关注其他用户的权限。 | +| **`delete_repo`** | 授予删除可管理仓库的权限。 | +| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | |  `read:discussion` | 授予对团队讨论的读取权限。{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | -| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | +| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | +| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | | **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除包](/github/managing-packages-with-github-packages/deleting-a-package)”。{% endif %} -| **`admin:gpg_key`** | 全面管理 GPG 密钥。 | -|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | +| **`admin:gpg_key`** | 全面管理 GPG 密钥。 | +|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | |  `read:gpg_key` | 列出和查看 GPG 密钥的详细信息。{% if currentVersion == "free-pro-team@latest" %} | **`工作流程`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可能公开 `GITHUB_TOKEN`，它可能具有一组不同的作用域，更多信息请参阅 https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token。{% endif %} diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index c211742c78584..12d3e480fc0fb 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: 查看上架产品的交易 -intro: '{% data variables.product.prodname_marketplace %} 交易页面允许您下载和查看 {% data variables.product.prodname_marketplace %} 上架产品的所有交易。 您可以查看 {% data variables.product.prodname_github_app %} 在过去一天（24 小时）、一周、一月或整个上架期间的交易。' +intro: '{% data variables.product.prodname_marketplace %} 交易页面允许您下载和查看 {% data variables.product.prodname_marketplace %} 上架产品的所有交易。 You can view transactions 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.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 37216b8af98da..3402d72f8cb9d 100644 --- a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -16,5 +16,5 @@ versions: ### 延伸阅读 - "[搜索讨论](/github/searching-for-information-on-github/searching-discussions)" -- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" -- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" +- "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[管理社区的讨论](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index 76cfa929ced56..2d7b187420c2e 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ redirect_from: {% data reusables.classroom.click-settings %} 1. 在“Delete this classroom（删除此教室）”右侧，单击 **Delete classroom（删除教室）**。 !["删除仓库"按钮](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **阅读警告**。 -1. 要验证删除的是否为正确的教室，请键入要删除的教室的名称。 ![用于删除包含警告的教室的模式和教室名称的文本字段](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. 要验证删除的是否为正确的教室，请键入要删除的教室的名称。 ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. 单击 **Delete classroom（删除教室）**。 !["删除教室"按钮](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md index ced5a30049b97..c49dbf391f38c 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -1,5 +1,5 @@ --- -title: About Dependabot version updates +title: 关于 Dependabot 版本更新 intro: '您可以使用 {% data variables.product.prodname_dependabot %} 来确保您使用的包更新到最新版本。' redirect_from: - /github/administering-a-repository/about-dependabot @@ -18,7 +18,7 @@ versions: 当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 -如果启用安全更新，{% data variables.product.prodname_dependabot %} 还会发起拉取请求以更新易受攻击依赖项。 For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +如果启用安全更新，{% data variables.product.prodname_dependabot %} 还会发起拉取请求以更新易受攻击依赖项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 {% data reusables.dependabot.dependabot-tos %} @@ -36,10 +36,14 @@ versions: {% note %} -{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 See the details in the table below. +{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 详见下表。 {% endnote %} {% data reusables.dependabot.supported-package-managers %} 如果您的仓库已使用集成进行依赖项管理，则在启用 {% data variables.product.prodname_dependabot %} 前需要禁用此集成。 更多信息请参阅“[关于集成](/github/customizing-your-github-workflow/about-integrations)”。 + +### 关于 {% data variables.product.prodname_dependabot %} 版本更新通知 + +您可以在 {% data variables.product.company_short %} 上过滤通知以显示 {% data variables.product.prodname_dependabot %} 版本更新。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/zh-CN/content/github/administering-a-repository/about-merge-methods-on-github.md index b1ea7b0a5433f..183dd6bdaa7b2 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[需要线性提交历史记录](/github/administering-a-repository/requiring-a-linear-commit-history)”。{% endif %} +默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。{% endif %} ### 压缩合并提交 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md index 58eea3005e022..f29845fe8ec19 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md @@ -1,38 +1,142 @@ --- title: 关于受保护分支 -intro: '受保护分支确保仓库的协作者无法对分支进行不可撤销的更改。 启用受保护分支也可让您启用其他可选检查和要求，例如必要的状态检查和必要的审查。' +intro: '您可以通过设置分支保护规则来保护重要分支，这些规则定义协作者是否可以删除或强制推送到分支以及设置任何分支推送要求，例如通过状态检查或线性提交历史记录。' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks + - /articles/about-branch-restrictions + - /github/administering-a-repository/about-branch-restrictions + - /articles/about-required-status-checks + - /github/administering-a-repository/about-required-status-checks + - /articles/types-of-required-status-checks + - /github/administering-a-repository/types-of-required-status-checks + - /articles/about-required-commit-signing + - /github/administering-a-repository/about-required-commit-signing + - /articles/about-required-reviews-for-pull-requests + - /github/administering-a-repository/about-required-reviews-for-pull-requests versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' --- -### 关于受保护分支 +### 关于分支保护规则 -{% data reusables.pull_requests.about-protected-branches %} 您可以选择对拉取请求如何合并到存储库中实施限制。 +您可以通过创建分支保护规则，实施某些工作流程或要求，以规定协作者如何向您仓库中的分支推送更改，包括将拉取请求合并到分支。 -仓库所有者以及对仓库具有管理员权限的用户可以实施特定的工作流程或要求，然后协作者才可创建受保护的分支规则来合并仓库中的分支。 +默认情况下，每个分支保护规则都禁止强制推送到匹配的分支并阻止删除匹配的分支。 您可以选择禁用这些限制并启用其他分支保护设置。 -{% data reusables.repositories.branch-rules-example %} 更多信息请参阅“[配置受保护分支](/articles/configuring-protected-branches/)”。 +默认情况下，分支保护规则的限制不适用于对仓库具有管理员权限的人。 您也可以选择包括管理员。 + +{% data reusables.repositories.branch-rules-example %} 关于分支名称模式的更多信息，请参阅“[管理分支保护规则](/github/administering-a-repository/managing-a-branch-protection-rule)”。 {% data reusables.pull_requests.you-can-auto-merge %} -### 排列受保护分支规则的优先级 +### 关于分支保护设置 + +对于每个分支保护规则，您可以选择启用或禁用以下设置。 +- [合并前必需拉取请求审查](#require-pull-request-reviews-before-merging) +- [合并前必需状态检查](#require-status-checks-before-merging) +- [要求签名提交](#require-signed-commits) +- [需要线性历史记录](#require-linear-history) +- [包括管理员](#include-administrators) +- [限制谁可以推送到匹配的分支](#restrict-who-can-push-to-matching-branches) +- [允许强制推送](#allow-force-pushes) +- [允许删除](#allow-deletions) + +#### 合并前必需拉取请求审查 + +{% data reusables.pull_requests.required-reviews-for-prs-summary %} + +如果启用必需审查，则协作者只能通过由所需数量的具有写入权限之审查者批准的拉取请求向受保护分支推送更改。 + +如果具有管理员权限的人在审查中选择 **Request changes（申请更改）**选项，则拉取请求必需经此人批准后才可合并。 如果申请更改拉取请求的审查者没有空，则具有仓库写入权限的任何人都可忽略阻止审查。 + +{% data reusables.repositories.review-policy-overlapping-commits %} + +如果协作者尝试将待处理或被拒绝审查的拉取请求合并到受保护分支，则该协作者将收到错误消息。 + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +（可选）您可以选择在推送提交时忽略旧拉取请求批准。 如果有人将修改代码的提交推送到已批准的拉取请求，则该批准将被忽略，拉取请求无法合并。 这不适用于协作者推送不修改代码的提交，例如将基础分值合并到拉取请求的分支。 有关基础分支的信息，请参阅“[关于拉取请求](/articles/about-pull-requests)”。 + +（可选）您可以限制特定人员或团队忽略拉取请求审查的权限。 更多信息请参阅“[忽略拉取请求审查](/articles/dismissing-a-pull-request-review)”。 + +（可选）您可以选择要求代码所有者进行审查。 如果这样做，则任何影响代码的拉取请求都必须得到代码所有者的批准，才能合并到受保护分支。 + +#### 合并前必需状态检查 + +必需状态检查确保在协作者可以对受保护分支进行更改前，所有必需的 CI 测试都已通过。 更多信息请参阅“[配置受保护分支](/articles/configuring-protected-branches/)”和“[启用必需状态检查](/articles/enabling-required-status-checks)”。 更多信息请参阅“[关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks)”。 + +必须配置仓库使用状态 API 后才可启用必需状态检查。 更多信息请参阅 REST 文档中的“[仓库](/rest/reference/repos#statuses)”。 + +启用必需状态检查后，必须通过所有必需状态检查，协作者才能将更改合并到受保护分支。 所有必需状态检查通过后，必须将任何提交推送到另一个分支，然后合并或直接推送到受保护分支。 + +{% note %} + +**注：**对仓库具有写入权限的任何个人或集成可以在仓库中设置任何状态检查的状态。 {% data variables.product.company_short %} 无法验证检查的作者是否被授权创建具有特定名称的检查或修改现有状态。 在合并拉取请求之前，应验证合并框中列出的每个状态的作者是否符合预期。 + +{% endnote %} + +您可以将必需状态检查设置为“宽松”或“严格”。 您选择的必需状态检查类型确定合并之前是否需要使用基础分支将您的分支保持最新状态。 + +| 必需状态检查的类型 | 设置 | 合并要求 | 考虑因素 | +| --------- | ------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- | +| **严格** | 选中 **Require branches to be up-to-date before merging（合并前需要分支保持最新状态）**复选框。 | 在合并之前，**必须**使用基础分支使分支保持最新状态。 | 这是必需状态检查的默认行为。 可能需要更多构建，因为在其他协作者将拉取请求合并到受保护基础分支后，您需要使头部分支保持最新状态。 | +| **宽松** | **不**选中 **Require branches to be up-to-date before merging（合并前需要分支保持最新状态）**复选框。 | 在合并之前，**不**必使用基础分支使分支保持最新状态。 | 您将需要更少的构建，因为在其他协作者合并拉取请求后，您不需要使头部分支保持最新状态。 如果存在与基础分支不兼容的变更，则在合并分支后，状态检查可能会失败。 | +| **已禁用** | **不**选中 **Require status checks to pass before merging（合并前需要状态检查通过）**复选框。 | 分支没有合并限制。 | 如果未启用必需状态检查，协作者可以随时合并分支，无论它是否使用基础分支保持最新状态。 这增加了不兼容变更的可能性。 | + +有关故障排除信息，请参阅“[必需状态检查故障排除](/github/administering-a-repository/troubleshooting-required-status-checks)”。 + +#### 要求签名提交 + +在分支上启用必需提交签名时，贡献者{% if currentVersion == "free-pro-team@latest" %}和自动程序{% endif %}只能将已经签名并验证的提交推送到分支。 更多信息请参阅“[关于提交签名验证](/articles/about-commit-signature-verification)”。 + +{% note %} + +**注：**如果协作者将未签名的提交推送到要求提交签名的分支，则协作者需要变基提交以包含验证的签名，然后将重写的提交强制推送到分支。 + +{% endnote %} + +如果提交已进行签名和验证，则始终可以将本地提交推送到分支。 {% if currentVersion == "free-pro-team@latest" %}您也可以使用 {% data variables.product.product_name %} 上的拉请求将已经签名和验证的提交合并到分支。 但除非您是拉取请求的作者，否则不能将拉取请求压缩并合并到 {% data variables.product.product_name %} 。{% else %}但不能将拉取请求合并到 {% data variables.product.product_name %} 上的分支。{% endif %} 您可以在本地 {% if currentVersion == "free-pro-team@latest" %}压缩和{% endif %}合并拉取请求。 更多信息请参阅“[在本地检出拉取请求](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)”。 + +{% if currentVersion == "free-pro-team@latest" %} 有关合并方法的更多信息，请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的合并方法](/github/administering-a-repository/about-merge-methods-on-github)”。{% endif %} + +#### 需要线性历史记录 + +强制实施线性提交历史记录可阻止协作者将合并提交推送到分支。 这意味着合并到受保护分支的任何拉取请求都必须使用压缩合并或变基合并。 严格的线性提交历史记录可以帮助团队更容易回溯更改。 有关合并方法的更多信息，请参阅“[关于拉取请求合并](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)”。 + +在需要线性提交历史记录之前，仓库必须允许压缩合并或变基合并。 更多信息请参阅“[配置拉取请求合并](/github/administering-a-repository/configuring-pull-request-merges)”。 + +#### 包括管理员 + +默认情况下，受保护分支规则不适用于对仓库具有管理员权限的人。 您可以启用此设置将管理员纳入受保护分支规则。 + +#### 限制谁可以推送到匹配的分支 + +{% if currentVersion == "free-pro-team@latest" %} +如果您的仓库由组织拥有，您可以使用 +{% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 启用分支限制。 +{% endif %} + +启用分支限制时，只有已授予权限的用户、团队或应用程序才能推送到受保护的分支。 您可以在受保护分支的设置中查看和编辑对受保护分支具有推送权限的用户、团队或应用程序。 + +您只能向对仓库具有 write 权限的用户、团队或已安装的 {% data variables.product.prodname_github_apps %} 授予推送到受保护分支的权限。 对仓库具有管理员权限的人员和应用程序始终能够推送到受保护分支。 + +#### 允许强制推送 -如果仓库有多个影响相同分支的受保护分支规则，则包含特定分支名称的规则具有最高优先级。 如果有多个受保护分支规则引用相同的特定规则名称，则最先创建的分支规则优先级更高。 +默认情况下，{% data variables.product.product_name %} 阻止对所有受保护分支的强制推送。 对受保护分支启用强制推送时，只要具有仓库写入权限，任何人（包括具有管理员权限的人）都可以强制推送到该分支。 -提及特殊字符（如 `*`、`?` 或 `]`）的受保护分支按其创建的顺序应用，因此含有这些字符的规则创建时间越早，优先级越高。 +启用强制推送不会覆盖任何其他分支保护规则。 例如，如果分支需要线性提交历史记录，则无法强制推送合并提交到该分支。 -### 分支保护设置 +{% 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)”。 -在仓库中创建分支保护规则时，{% if currentVersion == "free-pro-team@latest" %} 默认情况下{% endif %} 协作者无法强制推送到受保护的分支或删除分支。 您可以启用其他分支保护设置。 有关信息，请参阅“[定义拉取请求的可合并性](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)”。 +如果站点管理员只阻止强制推送到默认分支，您仍然可以为任何其他受保护分支启用强制推送。{% endif %} -### 延伸阅读 +#### 允许删除 -- "[关于必需状态检查](/articles/about-required-status-checks)" -- "[关于拉取请求的必要审查](/articles/about-required-reviews-for-pull-requests)" -- "[关于必需提交签名](/articles/about-required-commit-signing)" +默认情况下，您不能删除受保护的分支。 启用删除受保护分支后，任何对仓库至少拥有写入权限的人都可以删除分支。 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 c52945f514773..1906fb8f071c7 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 @@ -25,7 +25,7 @@ versions: 对仓库具有读取访问权限的任何人都可以查看和比较发行版，但只有对仓库具有写入权限的人员才能管理发行版。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 对仓库具有管理员权限的人员可以选择是否 将 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在 {% data variables.product.product_name %} 为每个发行版创建的 ZIP 文件和 tarball 中。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md b/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md index 625ff2a2c4c85..4d0e1329f02e8 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 @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + 如果项目与外部服务通信，您可能使用令牌或私钥进行身份验证。 令牌和私钥是服务提供商可以签发的典型密码。 如果将密码检入仓库，则对仓库具有读取权限的任何人都可以使用该密码以您的权限访问外部服务。 建议将密码存储在项目仓库外部专用的安全位置。 +服务提供者可以与 -如果有人将密码从 {% data variables.product.company_short %} 合作伙伴检入公共或私有仓库，则 {% data variables.product.prodname_secret_scanning %} 可以检测该密码，帮助您减小密码泄露的影响。 +{% data variables.product.company_short %} 合作提供其用于扫描的密码格式。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[密码扫描](/developers/overview/secret-scanning)”。 +{% endif %} -服务提供商可与 {% data variables.product.company_short %} 合作提供用于扫描的密码格式。 更多信息请参阅“[密码扫描](/partnerships/secret-scanning)”。 +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### 关于公共仓库的 {% data variables.product.prodname_secret_scanning %} - {% data variables.product.prodname_secret_scanning_caps %} 在公共仓库上自动启用，在其中会扫描密钥代码来检查已知的密码格式。 当在公共仓库中找到您的密码格式的匹配项时，{% data variables.product.company_short %} 不将信息作为警报公开，而是将有效负载发送到您选择的 HTTP 端点。 有关密码扫描如何在公共仓库上运行的概述，请参阅“[密码扫描](/developers/overview/secret-scanning)”。 +{% data variables.product.prodname_secret_scanning_caps %} 自动对公共仓库启用。 当您推送到公共仓库时，{% data variables.product.product_name %} 会扫描提交的内容中是否有密码。 如果将私有仓库切换到公共仓库，{% data variables.product.product_name %} 会扫描整个仓库中的密码。 -当您推送到公共仓库时，{% data variables.product.product_name %} 会扫描提交的内容中是否有密码。 如果将私有仓库切换到公共仓库，{% data variables.product.product_name %} 会扫描整个仓库中的密码。 - -当 {% data variables.product.prodname_secret_scanning %} 检测一组凭据时，我们会通知发布密码的服务提供商。 服务提供商会验证该凭据，然后决定是否应撤销密钥、颁发新密钥或直接与您联系，具体取决于与您或服务提供商相关的风险。 +当 {% data variables.product.prodname_secret_scanning %} 检测一组凭据时，我们会通知发布密码的服务提供商。 服务提供商会验证该凭据，然后决定是否应撤销密钥、颁发新密钥或直接与您联系，具体取决于与您或服务提供商相关的风险。 有关如何使用令牌颁发合作伙伴的概述，请参阅“[密码扫描](/developers/overview/secret-scanning)”。 {% data variables.product.product_name %} 当前会扫描公共仓库，查找以下服务提供商发布的密码。 -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### 关于私有仓库的 {% data variables.product.prodname_secret_scanning %} +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### 关于 {% data variables.product.product_name %} 上的 {% data variables.product.prodname_secret_scanning %} -如果您是仓库管理员或组织所有者，您可以为组织拥有的私有仓库启用 {% data variables.product.prodname_secret_scanning %}。 您可以启用对您所有的仓库或者您组织中的所有新仓库启用 {% data variables.product.prodname_secret_scanning %}。 {% data variables.product.prodname_secret_scanning_caps %} 不适用于用户帐户拥有的私有仓库。 更多信息请参阅“[管理仓库的安全性和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”或“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”。 +{% data variables.product.prodname_secret_scanning_caps %} 作为 {% data variables.product.prodname_GH_advanced_security %} 的一部分，在组织拥有的所有仓库上可用。 它不适用于用户拥有的仓库。 +{% endif %} -将提交推送到启用了 {% data variables.product.prodname_secret_scanning %} 的私有仓库时，{% data variables.product.product_name %} 会扫描提交的内容中是否有密码： +如果您是仓库管理员或组织所有者，您可以为组织拥有的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %}。 您可以对您的所有仓库或您组织内的所有新仓库启用 {% data variables.product.prodname_secret_scanning %}。{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} 不适用于用户拥有的私有仓库。{% endif %}更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”和“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”。 -当 {% data variables.product.prodname_secret_scanning %} 在私有仓库中检测到密码时，{% data variables.product.prodname_dotcom %} 会发送警报。 +将提交推送到启用了 {% data variables.product.prodname_secret_scanning %} 的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库时，{% data variables.product.prodname_dotcom %} 会扫描提交的内容中是否有密码。 + +当 {% data variables.product.prodname_secret_scanning %} 在{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库中检测到密码时，{% data variables.product.prodname_dotcom %} 会发送警报。 - {% data variables.product.prodname_dotcom %} 向仓库管理员和组织所有者发送电子邮件警报。 - {% data variables.product.prodname_dotcom %} 在仓库中显示警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 -仓库管理员和组织所有者可以授予用户和团队访问 {% data variables.product.prodname_secret_scanning %} 警报。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 - -要监控来自私有仓库或组织中的 {% data variables.product.prodname_secret_scanning %} 的结果，可以使用 {% data variables.product.prodname_secret_scanning %} API。 有关 API 端点的更多信息，请参阅“[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)”。 - -{% data variables.product.product_name %} 当前会扫描私有仓库，查找以下服务提供商发布的密码。 - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +仓库管理员和组织所有者可以授权用户和团队访问 {% data variables.product.prodname_secret_scanning %} 警报。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +要监控 +私有仓库或组织的 {% data variables.product.prodname_secret_scanning %} 结果，您可以使用 {% data variables.product.prodname_secret_scanning %} API。 有关 API 端点的更多信息，请参阅“[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)”。{% endif %} + +{% data variables.product.prodname_dotcom %} 目前扫描{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库，以检查由以下服务提供者颁发的密码。 + +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} 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 6f8776974a1bd..7f8d6a345d116 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 @@ -3,6 +3,7 @@ title: 关于保护仓库 intro: '{% data variables.product.product_name %} 提供了许多可帮助您保护仓库安全的方法。' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### 安全地设置仓库 @@ -13,6 +14,7 @@ versions: {% data variables.product.prodname_dotcom %} 有越来越多的安全功能，可帮助您保护代码安全。 您可以在仓库的 **Security（安全）**选项卡上找到这些功能。 +{% if currentVersion == "free-pro-team@latest" %} - **安全策略** 让人们能够轻松地秘密报告他们在仓库中发现的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)”。 @@ -24,18 +26,32 @@ versions: - **{% 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)”。 + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + 查看有关已知包含安全漏洞的依赖项的警报，并管理这些警报。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **{% data variables.product.prodname_dependabot %} 版本更新** +使用 + + {% data variables.product.prodname_dependabot %} 自动提出拉取请求以保持依赖项的更新。 这有助于减少您暴露于旧版本依赖项。 如果发现安全漏洞，使用更新后的版本就更容易打补丁，{% data variables.product.prodname_dependabot_security_updates %} 也更容易成功地提出拉取请求以升级有漏洞的依赖项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)”。 + {% endif %} - 使用 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以保持依赖项的更新。 这有助于减少您暴露于旧版本依赖项。 如果发现安全漏洞，使用更新后的版本就更容易打补丁，{% data variables.product.prodname_dependabot_security_updates %} 也更容易成功地提出拉取请求以升级有漏洞的依赖项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)”。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_code_scanning_capc %} 警报** 自动检测新代码或修改代码中的安全漏洞和编码错误。 潜在的问题被高亮显示，并附有详细信息，允许您在将代码合并到默认分支之前修复它。 更多信息请参阅“[关于代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。 - **检测到的密钥** +查看 - 查看 {% data variables.product.prodname_dotcom %} 在您的代码中找到的任何密钥。 应将已检入仓库的令牌或凭据视为已泄露。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 + {% data variables.product.prodname_dotcom %} 在您的代码中找到的任何密钥。 应将已检入仓库的令牌或凭据视为已泄露。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 + {% endif %} ### 探索依赖项 {% data variables.product.prodname_dotcom %} 的依赖项图允许您探索： diff --git a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md index bfbb96ed5dcd6..b6e3fde060b8c 100644 --- a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md @@ -1,7 +1,7 @@ --- -title: Changing the default branch -intro: 'If you have more than one branch in your repository, you can configure any branch as the default branch.' -permissions: People with admin permissions to a repository can change the default branch for the repository. +title: 更改默认分支 +intro: '如果仓库中有多个分支，您可以将任何分支配置为默认分支。' +permissions: 拥有仓库管理员权限的人可更改仓库的默认分支。 versions: free-pro-team: '*' enterprise-server: '*' @@ -11,19 +11,25 @@ redirect_from: - /articles/setting-the-default-branch --- -### About changing the default branch +### 关于更改默认分支 -You can choose the default branch for a repository. The default branch is the base branch for pull requests and code commits. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." +您可以选择仓库的默认分支。 默认分支是拉取请求和代码提交的基础分支。 有关默认分支的更多信息，请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。 {% if currentVersion != "github-ae@latest" %} {% note %} -**Note**: If you use the Git-Subversion bridge, changing the default branch will affect your `trunk` branch contents and the `HEAD` you see when you list references for the remote repository. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)" and [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) in the Git documentation. +**注**：如果您使用 Git-Subversion 桥，则更改默认分支将影响 `trunk` 分支内容和您列出远程仓库的引用时看到的 `HEAD`。 更多信息请参阅 Git 文档中的“[Subversion 客户端支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”和 [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html)。 {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} + +您也可以重命名默认分支。 更多信息请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} @@ -31,19 +37,19 @@ You can choose the default branch for a repository. The default branch is the ba ### 基本要求 -To change the default branch, your repository must have more than one branch. 更多信息请参阅“[创建和删除仓库中的分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)”。 +要更改默认分支，您的仓库必须有多个分支。 更多信息请参阅“[创建和删除仓库中的分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)”。 -### Changing the default branch +### 更改默认分支 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. Under "Default branch", to the right of the default branch name, click {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Switch icon with two arrows to the right of current default branch name](/assets/images/help/repository/repository-options-defaultbranch-change.png) -1. Use the drop-down, then click a branch name. ![Drop-down to choose new default branch](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) -1. 单击 **Update（更新）**。 !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-update.png) -1. Read the warning, then click **I understand, update the default branch.** !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) +1. 在“Default branch（默认分支）”下，在默认分支名称的右侧单击 {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}。 ![当前默认分支名称右侧的两个箭头切换图标](/assets/images/help/repository/repository-options-defaultbranch-change.png) +1. 使用下拉菜单，然后单击分支名称。 ![选择新默认分支的下拉菜单](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) +1. 单击 **Update（更新）**。 ![选择新默认分支后的"更新"按钮](/assets/images/help/repository/repository-options-defaultbranch-update.png) +1. 阅读警告，然后单击 **I understand, update the default branch（我了解，请更新默认分支）**。 ![选择新默认分支后的"更新"按钮](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) {% else %} diff --git a/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md new file mode 100644 index 0000000000000..e12b0e396a628 --- /dev/null +++ b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -0,0 +1,69 @@ +--- +title: 配置仓库的密码扫描 +intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何扫描您仓库中的密码。' +permissions: '拥有仓库管理员权限的人可启用仓库的 {% data variables.product.prodname_secret_scanning %}。' +redirect_from: + - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories +product: '{% data reusables.gated-features.secret-scanning %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**注：**{% data variables.product.prodname_secret_scanning_caps %} 默认在公共仓库上启用，无法关闭。 您只能配置私有仓库的 {% data variables.product.prodname_secret_scanning %}。 + +{% endnote %} +{% endif %} + +### 为{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} + +{% if currentVersion == "free-pro-team@latest" %} +4. 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 未显示在页面上，您需要先启用 {% data variables.product.prodname_GH_advanced_security %}。 在“{% data variables.product.prodname_GH_advanced_security %}”右边单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-dotcom.png) +5. 单击**为此仓库启用 {% data variables.product.prodname_GH_advanced_security %}** 以确认操作。 ![确认为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. 当您启用 +{% data variables.product.prodname_GH_advanced_security %} 时，可能会自动为仓库启用 {% data variables.product.prodname_secret_scanning %}（这是由组织配置控制的）。 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 显示 **Enable（启用）**按钮，则您仍需通过单击 **Enable（启用）**来启用 {% data variables.product.prodname_secret_scanning %}。 如果您看到 **Disable（禁用）**按钮，则表明 {% data variables.product.prodname_secret_scanning %} 已启用。 + ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +4. 在 " +{% data variables.product.prodname_secret_scanning_caps %}" 的右侧，单击 **Enable（启用）**。 + ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-ghe.png) + {% endif %} + +### 排除{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库中的 {% data variables.product.prodname_secret_scanning %} 警报 + +您可以使用 *secret_scanning.yml* 文件从 {% data variables.product.prodname_secret_scanning %} 排除目录。 例如，可以排除包含测试或随机生成内容的目录。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. 在文件名字段中，键入 *.github/secret_scanning.yml*。 +4. 在 **Edit new file（编辑新文件）**下，键入 `paths-ignore:`，后接您想要从 {% data variables.product.prodname_secret_scanning %} 排除的路径。 + ``` yaml + paths-ignore: + - "foo/bar/*.js" + ``` + + 您可以使用特殊字符（如 `*`）来过滤路径。 有关过滤模式的更多信息，请参阅“[GitHub 操作的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)”。 + + {% note %} + + **注意：** + - 如果 `paths-ignore` 中的条目超过 1,000 个，{% data variables.product.prodname_secret_scanning %} 只会从扫描中排除前 1,000 个目录。 + - 如果 *secret_scanning.yml* 大于 1 MB，{% data variables.product.prodname_secret_scanning %} 将忽略整个文件。 + + {% endnote %} + +您也可以忽略来自 {% data variables.product.prodname_secret_scanning %} 的个别警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)”。 + +### 延伸阅读 + +- “[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)” diff --git a/translations/zh-CN/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md index c759845dad4ef..8c62547aaecac 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md @@ -1,6 +1,6 @@ --- -title: Configuring the retention period for GitHub Actions artifacts and logs in your repository -intro: 'You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.' +title: 为仓库中的 GitHub Actions 构件和日志配置保留期 +intro: '您可以为仓库中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。' versions: free-pro-team: '*' enterprise-server: '>=2.23' @@ -8,9 +8,9 @@ versions: {% data reusables.actions.about-artifact-log-retention %} -You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)." +您还可以为工作流程创建的特定构件自定义保留期。 更多信息请参阅“[设置构件的保留期](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)”。 -## Setting the retention period for a repository +## 设置仓库的保留期 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md index 070048507fbbd..5d936c190c7bc 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -1,20 +1,20 @@ --- -title: Enabling or disabling GitHub Discussions for a repository -intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +title: 启用或禁用仓库的 GitHub 讨论 +intro: '您可以使用仓库中的讨论为社区提供对话、提问和发布答案的空间，而无需界定议题的范围。' product: '{% data reusables.gated-features.discussions %}' -permissions: People with admin permissions to a repository can enable discussions for the repository. +permissions: 拥有仓库管理员权限的人可为仓库启用讨论。 versions: free-pro-team: '*' --- {% data reusables.discussions.beta %} -### Enabling or disabling discussions for your repository +### 为仓库启用或禁用讨论 {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} -1. To disable discussions, under "Features", unselect **Discussions**. +1. 要禁用讨论，请在“Features（功能）”下，取消选择 **Discussions（讨论）**。 ### 延伸阅读 -- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" -- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" +- "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[管理社区的讨论](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/github/administering-a-repository/index.md b/translations/zh-CN/content/github/administering-a-repository/index.md index e0e53b9b3d50e..d9c52432b3a1a 100644 --- a/translations/zh-CN/content/github/administering-a-repository/index.md +++ b/translations/zh-CN/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/zh-CN/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md b/translations/zh-CN/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md index bfc8b75dbbf46..5fb21007d8c9e 100644 --- a/translations/zh-CN/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/zh-CN/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: 使用 Dependabot 保持操作的最新状态 intro: '您可以使用 {% data variables.product.prodname_dependabot %} 来确保您使用的操作更新到最新版本。' redirect_from: - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/zh-CN/content/github/administering-a-repository/managing-a-branch-protection-rule.md new file mode 100644 index 0000000000000..b20d2b4fb44c2 --- /dev/null +++ b/translations/zh-CN/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -0,0 +1,82 @@ +--- +title: 管理分支保护规则 +intro: '您可以创建分支保护规则对一个或多个分支实施某些工作流程，例如要求批准审查或通过状态检查才能将拉取请求合并到受保护分支。' +product: '{% data reusables.gated-features.protected-branches %}' +redirect_from: + - /articles/configuring-protected-branches + - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks + - /articles/enabling-required-status-checks + - /github/administering-a-repository/enabling-required-status-checks + - /articles/enabling-branch-restrictions + - /github/administering-a-repository/enabling-branch-restrictions + - /articles/enabling-required-reviews-for-pull-requests + - /github/administering-a-repository/enabling-required-reviews-for-pull-requests + - /articles/enabling-required-commit-signing + - /github/administering-a-repository/enabling-required-commit-signing + - /github/administering-a-repository/requiring-a-linear-commit-history + - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch + - /github/administering-a-repository/enabling-deletion-of-a-protected-branch +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 拥有仓库管理员权限的人可以管理分支保护规则。 +--- + +### 关于分支保护规则 + +{% data reusables.repositories.branch-rules-example %} + +您还可以使用通配符语法 `*` 为仓库中的所有当前和未来分支创建规则。 由于 {% data variables.product.company_short %} 对 `File.fnmatch` 语法使用 `File::FNM_PATHNAME` 标记，因此通配符与目录分隔符 (`/`) 不匹配。 例如，`qa/*` 将匹配以 `qa/` 开头并包含单个斜杠的所有分支。 您可以通过 `qa/**/*` 包含多个斜杠，也可以通过 `qa**/**/*` 扩展 `qa` 字符串，使规则更具包容性。 有关分支规则语法选项的更多信息，请参阅 [fnmatch 文档](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)。 + +如果仓库有多个影响相同分支的受保护分支规则，则包含特定分支名称的规则具有最高优先级。 如果有多个受保护分支规则引用相同的特定规则名称，则最先创建的分支规则优先级更高。 + +提及特殊字符（如 `*`、`?` 或 `]`）的受保护分支按其创建的顺序应用，因此含有这些字符的规则创建时间越早，优先级越高。 + +要创建对现有分支规则的例外，您可以创建优先级更高的新分支保护规则，例如针对特定分支名称的分支规则。 + +有关每个可用分支保护设置的更多信息，请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 + +### 创建分支保护规则 + +创建分支规则时，指定的分支不必是仓库中现有的分支。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +{% data reusables.repositories.add-branch-protection-rules %} +1. （可选）启用必需拉取请求审查。 + - 在“Protect matching branches（保护匹配分支）”下，选择 **Require pull request reviews before merging（合并前必需拉取请求审查）**。 ![拉取请求审查限制复选框](/assets/images/help/repository/PR-reviews-required.png) + - 单击 **Required approving reviews（必需批准审查）**下拉菜单，然后选择要对分支要求的批准审查数量。 ![用于选择必需审查批准数量的下拉菜单](/assets/images/help/repository/number-of-required-review-approvals.png) + - （可选）要在将代码修改提交推送到分支时忽略拉取请求批准审查，请选择 **Dismiss stale pull request approvals when new commits are pushed（推送新提交时忽略旧拉取请求批准）**。 ![在推送新提交时，关闭旧拉取请求批准的复选框](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) + - （可选）要在拉取请求影响具有指定所有者的代码时要求代码所有者审查，请选择 **Require review from Code Owners（需要代码所有者审查）**。 更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。 ![代码所有者的必需审查](/assets/images/help/repository/PR-review-required-code-owner.png) + - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 然后，搜索并选择有权忽略拉取请求审查的人员或团队。 更多信息请参阅“[忽略拉取请求审查](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)”。 ![限制可以忽略拉取请求审查的人员复选框](/assets/images/help/repository/PR-review-required-dismissals.png) +1. （可选）启用必需状态检查。 + - 选中 **Require status checks to pass before merging（合并前必需状态检查通过）**。 ![必需状态检查选项](/assets/images/help/repository/required-status-checks.png) + - （可选）要确保使用受保护分支上的最新代码测试拉取请求，请选择 **Require branches to be up to date before merging（要求分支在合并前保持最新）**。 ![宽松或严格的必需状态复选框](/assets/images/help/repository/protecting-branch-loose-status.png) + - 从可用状态检查列表中，选择您想要设为必需的检查。 ![可用状态检查列表](/assets/images/help/repository/required-statuses-list.png) +1. （可选）选择 **Require signed commits（必需签名提交）**。 ![必需签名提交选项](/assets/images/help/repository/require-signed-commits.png) +1. （可选）选择 **Require linear history（必需线性历史记录）**。 ![必需的线性历史记录选项](/assets/images/help/repository/required-linear-history.png) +1. 视情况可选择 **Include administrators（包括管理员）**。 ![包括管理员复选框](/assets/images/help/repository/include-admins-protected-branches.png) +1. （可选）{% if currentVersion == "free-pro-team@latest" %}如果仓库由组织拥有，可使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}{% endif %} 启用分支限制。 + - 选择 **Restrict who can push to matching branches（限制谁可以推送到匹配分支）**。 ![分支限制复选框](/assets/images/help/repository/restrict-branch.png) + - 搜索并选择有权限推送到受保护分支的人员、团队或应用程序。 ![分支限制搜索](/assets/images/help/repository/restrict-branch-search.png) +1. （可选）在“Rules applied to everyone including administrators（适用于包括管理员在内的所有人规则）”下，选择 **Allow force pushes（允许强制推送）**。 ![允许强制推送选项](/assets/images/help/repository/allow-force-pushes.png) +1. （可选）选择 **Allow deletions（允许删除）**。 ![允许分支删除选项](/assets/images/help/repository/allow-branch-deletions.png) +1. 单击 **Create（创建）**。 + +### 编辑分支保护规则 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. 在要编辑的分支保护规则的右侧，单击 **Edit（编辑）**。 ![编辑按钮](/assets/images/help/repository/edit-branch-protection-rule.png) +1. 对分支保护规则进行所需的更改。 +1. 单击 **Save changes（保存更改）**。 ![Edit message 按钮](/assets/images/help/repository/save-branch-protection-rule.png) + +### 删除分支保护规则 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.repository-branches %} +1. 在要删除的分支保护规则的右侧，单击 **Delete（删除）**。 ![删除按钮](/assets/images/help/repository/delete-branch-protection-rule.png) 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 5b376eac0858b..1a0933ee0bc62 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 @@ -4,6 +4,7 @@ intro: 您可以查看并关闭已检入仓库的密码的警报。 product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. 在左侧边栏中，单击 **Detected secrets（检测到的密码）**。 !["检测到的密码"选项卡](/assets/images/help/repository/sidebar-secrets.png) -4. 在“Secret scanning（密码扫描）”下，单击要查看的警报。 ![来自密码扫描的警报](/assets/images/help/repository/secret-scanning-click-alert.png) -5. （可选）使用“Resolve（解决）”下拉菜单，单击原因以解决警报。 ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. 在“Secret scanning（密码扫描）”下，单击要查看的警报。 + {% if currentVersion == "free-pro-team@latest" %} + ![来自密码扫描的警报](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![来自密码扫描的警报](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. （可选）使用“Mark as（标记为）”下拉菜单，单击原因以解决警报。 + {% if currentVersion == "free-pro-team@latest" %} + ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### 保护受到威胁的密码 只要密码被提交到仓库，便应视为受到威胁。 {% data variables.product.prodname_dotcom %} 建议对受到威胁的密码执行以下操作： - 对于受到威胁的 {% data variables.product.prodname_dotcom %} 个人访问令牌，请删除该令牌，创建新令牌，然后更新使用旧令牌的任何服务。 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)。” -- 对于所有其他密码，请先确认提交到 {% data variables.product.prodname_dotcom %} 的密码是有效的。 如果有效，请创建新密码，更新使用旧密码的任何服务，然后删除旧密码。 +- 对于所有其他密码，请先确认提交到 {% data variables.product.product_name %} 的密码是有效的。 如果有效，请创建新密码，更新使用旧密码的任何服务，然后删除旧密码。 diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index e19203c0666a3..05da1b5ce3af3 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -1,16 +1,16 @@ --- -title: Managing auto-merge for pull requests in your repository -intro: "You can allow or disallow auto-merge for pull requests in your repository." +title: 管理仓库中拉取请求的自动合并 +intro: "您可以允许或禁止仓库中拉取请求的自动合并。" product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' -permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository. +permissions: 具有维护员权限的人可以管理仓库中拉取请求的自动合并。 --- {% data reusables.pull_requests.auto-merge-release-phase %} -If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." +如果您允许自动合并仓库中的拉取请求，则用户可以配置仓库中的单个拉取请求在满足所有合并要求时自动合并。 更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. 在“Merge button（合并按钮）”下，选择或取消选择 **Allow auto-merge（允许自动合并）**。 ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file 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 355af0816406c..6d6436758c68e 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 @@ -5,7 +5,7 @@ intro: '您可以选择是否将 {% data variables.large_files.product_name_long permissions: '对仓库具有管理员权限的人可以管理是否将 {% data variables.large_files.product_name_short %} 对象包含在仓库的存档中。' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ 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 currentVersion == "free-pro-team@latest" %} 如果您选择在仓库存档中包含 {% 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 %} diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md index 5b94165d247fe..ac9267e40262e 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### 关于发行版管理 diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 36a21fff9c040..cd851305f8334 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### 启用或禁用安全和分析功能 +{% if currentVersion == "free-pro-team@latest" %} +### 为公共仓库启用或禁用安全和分析功能 -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +您可以管理公共仓库的一部分安全和分析功能。 其他功能是永久启用的，包括依赖项图和密码扫描。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 ![公共仓库中"Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### 为私有仓库启用或禁用安全和分析功能{% if currentVersion == "free-pro-team@latest" %}{% endif %} + +您可以管理{% if currentVersion == "free-pro-team@latest" %}私有或内部{% endif %}仓库的安全和分析功能。 如果您的组织或企业拥有 {% data variables.product.prodname_GH_advanced_security %} 的许可，则可以使用额外选项。 {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 +{% if currentVersion == "free-pro-team@latest" %}如果 "{% data variables.product.prodname_secret_scanning_caps %}" 未显示，您可能需要先启用 {% data variables.product.prodname_GH_advanced_security %}。 + !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### 授予对安全警报的访问权限 @@ -35,7 +53,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. 在“Access to alerts（访问警报）”下，在搜索字段中开始键入您要查找的个人或团队的名称，然后单击匹配列表中的名称。 ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. 在“Access to alerts（访问警报）”下，在搜索字段中开始键入您要查找的个人或团队的名称，然后单击匹配列表中的名称。 + {% if currentVersion == "free-pro-team@latest" %} + ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. 单击 **Save changes（保存更改）**。 ![用于更改安全警报设置的"Save changes（保存更改）"按钮](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### 删除对安全警报的访问权限 @@ -43,7 +67,14 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. 在“Access to alerts（访问警报）”下，在要删除其访问权限的个人或团队的右侧，单击 {% octicon "x" aria-label="X symbol" %}。 ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. 在“Access to alerts（访问警报）”下，在要删除其访问权限的个人或团队的右侧，单击 +{% octicon "x" aria-label="X symbol" %}。 + {% if currentVersion == "free-pro-team@latest" %} + ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md new file mode 100644 index 0000000000000..0357c13f7067c --- /dev/null +++ b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md @@ -0,0 +1,21 @@ +--- +title: 重命名分支 +intro: 您可以更改仓库中分支的名称。 +permissions: 拥有仓库写入权限的人可重命名仓库中的分支。 具有管理员权限的人可以重命名默认分支。 +versions: + free-pro-team: '*' +--- + +### 关于重命名分支 + +您可以重命名 {% data variables.product.product_location %} 上仓库中的分支。 有关分支的更多信息，请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches)”。 + +如果重命名分支，{% data variables.product.prodname_dotcom %} 会自动将 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} 上包含旧分支名称的链接重定向到重命名分支上的对应链接。 {% data variables.product.prodname_dotcom %} 还将更新分支保护策略，以及用于开启拉取请求和草稿发行版的基础分支。 + +### 重命名分支 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. 在分支列表中，在要重命名的分支的右侧，单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![要重命名的分支右侧的铅笔图标](/assets/images/help/branch/branch-rename-edit.png) +1. 为分支输入新名称。 ![输入新分支名称的文本字段](/assets/images/help/branch/branch-rename-type.png) +1. 查看有关本地环境的信息，然后单击 **Rename branch（重命名分支）**。 ![本地环境信息和"重命名分支"按钮](/assets/images/help/branch/branch-rename-rename.png) 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 b373dbd6cdea5..aae985e75fcd6 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 @@ -24,7 +24,8 @@ versions: * 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}任何复刻的可见性也将更改为私有。{% elsif currentVersion == "github-ae@latest" %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”{% if currentversion == "free proteam@latest" %} * 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 {% data reusables.gated-features.more-info %}{% endif %} * 任何已发布的 {% data variables.product.prodname_pages %} 站点将自动取消发布。{% if currentVersion == "free-pro-team@latest" %} 如果将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应先删除或更新 DNS 记录后再将仓库设为私有，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% 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 %} +* {% 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 currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_GH_advanced_security %} 功能，例如 {% data variables.product.prodname_code_scanning %}，将停止工作，除非拥有仓库的组织具有 {% data variables.product.prodname_advanced_security %} 许可。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * 匿名 Git 读取权限不再可用。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -46,7 +47,10 @@ versions: #### 将仓库设为公共 * {% data variables.product.product_name %} 将会分离私有复刻并将它们变成独立的私有仓库。 更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)”{% if currentVersion == "free-pro-team@latest" %} -* 如果在创建开源项目时将私有仓库转换为公共仓库，请参阅[开放源码指南](http://opensource.guide)以了解有用的提示和指南。 您还可以通过 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) 免费学习管理开源项目的课程。 您的仓库设为公共后，您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 更多信息请参阅“[查看您的社区资料](/articles/viewing-your-community-profile)”。{% endif %} +* 如果在创建开源项目时将私有仓库转换为公共仓库，请参阅[开放源码指南](http://opensource.guide)以了解有用的提示和指南。 您还可以通过 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) 免费学习管理开源项目的课程。 您的仓库设为公共后，您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 更多信息请参阅“[查看您的社区资料](/articles/viewing-your-community-profile)”。 +* 仓库将自动获得对 {% data variables.product.prodname_GH_advanced_security %} 功能的使用权限。 + +有关改善仓库安全性的信息，请参阅“[关于保护仓库](/github/administering-a-repository/about-securing-your-repository)”。{% endif %} {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/zh-CN/content/github/administering-a-repository/troubleshooting-required-status-checks.md new file mode 100644 index 0000000000000..b56bc940f82d4 --- /dev/null +++ b/translations/zh-CN/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -0,0 +1,38 @@ +--- +title: 必需状态检查故障排除 +intro: '您可以检查必需状态检查的常见错误并解决问题，' +product: '{% data reusables.gated-features.protected-branches %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +--- + +如果您有名称相同的检查和状态，并且选择该名称作为必需状态检查，则检查和状态都是必需的。 更多信息请参阅“[检查](/rest/reference/checks)”。 + +在启用必需状态检查后，您的分支在合并之前可能需要使用基础分支更新。 这可确保您的分支已经使用基本分支的最新代码做过测试。 如果您的分支过期，则需要将基本分支合并到您的分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 + +{% note %} + +**注：**您也可以使用 Git 变基以基础分支更新您的分支。 更多信息请参阅“[关于 Git 变基](/github/using-git/about-git-rebase)”。 + +{% endnote %} + +在通过所有必需状态检查之前，无法向受保护分支推送本地更改。 反而会收到类似如下的错误消息。 + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Required status check "ci-build" is failing +``` +{% note %} + +**注：**最新且通过必需状态检查的拉取请求可以本地合并，并且推送到受保护分支。 此操作无需对合并提交本身运行状态检查。 + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + +有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则测试合并提交必须通过。 否则，必须传递头部提交的状态后才可合并该分支。 有关测试合并提交的更多信息，请参阅“[拉取](/rest/reference/pulls#get-a-pull-request)”。 + +![具有冲突的合并提交的分支](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) +{% 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 8c4705f29fae9..3d1767fa7fb67 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 @@ -19,11 +19,13 @@ versions: 如果提交或标记具有无法验证的签名，则 {% data variables.product.product_name %} 会将提交或标记标示为未验证。 -仓库管理员可对分析实施必要的提交签名，以阻止未签名和验证的所有提交。 更多信息请参阅"[关于必需提交签名](/articles/about-required-commit-signing)"。 +仓库管理员可对分析实施必要的提交签名，以阻止未签名和验证的所有提交。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-signed-commits)”。 您可以在 {% data variables.product.product_name %} 上检查已签名提交或标记的验证状态，并查看提交签名未验证的原因。 更多信息请参阅“[检查提交和标记签名验证状态](/articles/checking-your-commit-and-tag-signature-verification-status)”。 -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} 将自动使用 GPG 通过 {% data variables.product.product_name %} web 界面对您创建的提交进行签名，当您压缩且合并您不是其作者的拉取请求时除外。 由 {% data variables.product.product_name %} 签名的提交在 {% data variables.product.product_name %} 上将具有已验证的状态。 您可以使用 https://github.com/web-flow.gpg 上的公钥本地验证签名。{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} 将自动使用 GPG 通过 {% data variables.product.product_name %} web 界面对您创建的提交进行签名，当您压缩且合并您不是其作者的拉取请求时除外。 您可以选择在 {% data variables.product.prodname_codespaces %} 中使用 {% data variables.product.product_name %} 对您的提交进行签名。 由 {% data variables.product.product_name %} 签名的提交在 {% data variables.product.product_name %} 上将具有已验证的状态。 您可以使用 https://github.com/web-flow.gpg 上的公钥本地验证签名。 有关对您的代码空间启用 GPG 验证的更多信息，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”。 +{% endif %} ### 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 8b098a15296d6..824b686e352cd 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 @@ -39,6 +39,7 @@ versions: | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} | [`account_recovery_token`](#account_recovery_token-category-actions) | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。 | | [`计费，帐单`](#billing-category-actions) | 包含与帐单信息相关的所有活动。 | +| [`codespaces`](#codespaces-category-actions) | 包含与 {% data variables.product.prodname_codespaces %} 相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)”。 | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。 | | [`marketplace_listing`](#marketplace_listing-category-actions) | 包含与 {% data variables.product.prodname_marketplace %} 中列出的应用程序相关的所有活动。{% endif %} | [`oauth_access`](#oauth_access-category-actions) | 包含与您已连接的 [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) 相关的所有活动。{% if currentVersion == "free-pro-team@latest" %} @@ -82,6 +83,12 @@ versions: | `change_billing_type` | 当您[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 | | `change_email` | 当您[更改您的电子邮件地址](/articles/changing-your-primary-email-address)时触发。 | +#### `codespaces` 类操作 + +| 操作 | 描述 | +| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `trusted_repositories_access_update` | 当您更改用户帐户的 [{% data variables.product.prodname_codespaces %} 访问权限和安全设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)时触发。 | + #### `marketplace_agreement_signature` 类操作 | 操作 | 描述 | @@ -176,7 +183,7 @@ versions: | `repo_funding_link_button_toggle` | 在仓库中启用或禁用赞助按钮时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”） | | `repo_funding_links_file_action` | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”） | | `sponsor_sponsorship_cancel` | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”） | -| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_create` | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)”） | | `sponsor_sponsorship_preference_change` | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/articles/managing-your-sponsorship)”） | | `sponsor_sponsorship_tier_change` | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”） | | `sponsored_developer_approve` | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） | @@ -227,20 +234,20 @@ versions: #### `user` 类操作 -| 操作 | 描述 | -| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | 在您{% if currentVersion != "github-ae@latest" %}[新增电子邮件地址](/articles/changing-your-primary-email-address){% else %}新增电子邮件地址{% endif %}时触发。 | -| `create` | 在创建新帐户时触发。{% if currentVersion != "github-ae@latest" %} -| `change_password` | 当您更改密码时触发。 | -| `forgot_password` | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %} -| `hide_private_contributions_count` | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | -| `login` | 当您登录 {% data variables.product.product_location %} 时触发。 | -| `failed_login` | 当您未能成功登录时触发。 | -| `remove_email` | 当您删除电子邮件地址时触发。 | -| `rename` | 在重命名帐户时触发。{% if currentVersion == "free-pro-team@latest" %} -| `report_content` | 当您[举报议题或拉取请求，或者举报对议题、拉取请求或提交的评论](/articles/reporting-abuse-or-spam)时触发。{% endif %} -| `show_private_contributions_count` | 当您[在个人资料中公开私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。{% if currentVersion != "github-ae@latest" %} -| `two_factor_requested` | 当 {% data variables.product.product_name %} 要求您提供[双重身份验证代码](/articles/accessing-github-using-two-factor-authentication)时触发。{% endif %} +| 操作 | 描述 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email` | 当您 | +| {% if currentVersion != "github-ae@latest" %}[添加新电子邮件地址](/articles/changing-your-primary-email-address){% else %}添加新电子邮件地址{% endif %}时触发。{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | 当您[允许为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 | +| `codespaces_trusted_repo_access_revoked` | 当您[禁止为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 |{% endif %} +| `create` | 在创建新帐户时触发。{% if currentVersion != "github-ae@latest" %} +| `change_password` | 当您更改密码时触发。 | +| `forgot_password` | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %} +| `hide_private_contributions_count` | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | +| `login` | 当您登录到 {% data variables.product.product_location %} 时触发。{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | 当您查看必读消息时触发（更多信息请参阅“[自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise)” | |{% endif %}| | `failed_login` | 当您未能成功登录时触发。 | `remove_email` | 当您删除电子邮件地址时触发。 | `rename` | 当您重命名帐户时触发。{% if currentVersion == "free-pro-team@latest" %} | `report_content` | 当您[举报议题或拉取请求，或者举报对议题、拉取请求或提交的评论](/articles/reporting-abuse-or-spam)时触发。{% endif %} | `show_private_contributions_count` | 当您[在个人资料中公布私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | 当 {% data variables.product.product_name %} 要求您提供[双重身份验证代码](/articles/accessing-github-using-two-factor-authentication)时触发。{% endif %} #### `user_status` 类操作 @@ -249,4 +256,3 @@ versions: | `update` | 当您在个人资料中设置或更改状态时触发。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。 | | `destroy` | 当您在个人资料中清除状态时触发。 | - diff --git a/translations/zh-CN/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/zh-CN/content/github/authenticating-to-github/testing-your-ssh-connection.md index 8d156940eb719..cddb380be2931 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/testing-your-ssh-connection.md +++ b/translations/zh-CN/content/github/authenticating-to-github/testing-your-ssh-connection.md @@ -31,7 +31,7 @@ versions: > Are you sure you want to continue connecting (yes/no)? ``` -3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: +3. 验证所看到消息中的指纹是否匹配 {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %} 的 RSA 公钥指纹](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %}您企业的公钥指纹{% endif %}。 如果是，则输入 `yes`： ```shell > Hi username! You've successfully authenticated, but GitHub does not > provide shell access. diff --git a/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index ec82a5973ba78..fd6f936f9f97f 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ versions: 通过输入以下命令，您可以更改现有私钥的密码而无需重新生成密钥对： ```shell -$ ssh-keygen -p -# Start the SSH key creation process -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md b/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md index bac8998d41dbf..f7abcd265c3b3 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md +++ b/translations/zh-CN/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: 限制用户帐户的交互 +intro: '您可以在用户帐户拥有的所有公共仓库中对某些用户临时限制活动一段时间。' versions: free-pro-team: '*' -permissions: Anyone can limit interactions for their own user account. +permissions: 任何人都可以限制他们自己的用户帐户的交互。 --- -### About temporary interaction limits +### 关于临时交互限制 -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 %} +限制用户帐户的交互可对用户帐户拥有的所有公共仓库启用临时交互限制。 {% 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 %} 在限制期过后，用户可以在您的公共仓库中恢复正常活动。 {% 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)." +启用用户范围的活动限制时，无法对单个仓库启用或禁用交互限制。 有关限制单个仓库活动的更多信息，请参阅“[限制仓库中的交互](/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)." +您还可以阻止用户。 更多信息请参阅“[阻止用户访问个人帐户](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)”。 -### Limiting interactions for your user account +### 限制用户帐户的交互 {% 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. 在在用户设置侧边栏中的“Moderation settings（管理设置）”下，单击 **Interaction limits（交互限制）**。 ![用户设置侧边栏中的"交互限制"选项卡](/assets/images/help/settings/settings-sidebar-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png) \ No newline at end of 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 c6776434fbe2c..46786078999c7 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 @@ -9,7 +9,7 @@ versions: permissions: 组织所有者可限制组织中的交互。 --- -### About temporary interaction limits +### 关于临时交互限制 限制组织中的交互可对组织拥有的所有公共仓库启用临时交互限制。 {% data reusables.community.interaction-limits-restrictions %} @@ -19,7 +19,7 @@ permissions: 组织所有者可限制组织中的交互。 组织成员不受任何限制类型的影响。 -在整个组织范围内启用活动限制时，无法对个别仓库启用或禁用交互限制。 For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." +在整个组织范围内启用活动限制时，无法对个别仓库启用或禁用交互限制。 有关限制单个仓库活动的更多信息，请参阅“[限制仓库中的交互](/articles/limiting-interactions-in-your-repository)”。 组织所有者也可在特定的时间段内阻止用户。 在阻止到期后，该用户会自动解除阻止。 更多信息请参阅“[阻止用户访问组织](/articles/blocking-a-user-from-your-organization)”。 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 d6dc06d38f0ab..bb99926fd4b5e 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 @@ -9,7 +9,7 @@ versions: permissions: 对仓库具有管理员权限的人可以临时限制该仓库中的交互。 --- -### About temporary interaction limits +### 关于临时交互限制 {% data reusables.community.interaction-limits-restrictions %} 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 92a6dba43e774..67b9bc8c9b2ff 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 @@ -74,7 +74,7 @@ versions: - 如果对分支启用了必需状态检查，则在所有必需 CI 测试通过之前，无法将更改合并到分支。 更多信息请参阅“[关于状态检查](/articles/about-status-checks)”。 - 如果对分支启用了必需拉取请求审查，则在满足拉取请求审查策略中的所有要求之前，无法将更改合并到分支。 更多信息请参阅“[合并拉取请求](/articles/merging-a-pull-request)”。 - 如果对分支启用了代码所有者的必需审查，并且拉取请求修改具有所有者的代码，则代码所有者必须批准拉取请求后才可合并。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners)”。 -- 如果对分支启用了必需提交签名，则无法将任何提交推送到未签名和验证的分支。 更多信息请参阅“[关于提交签名验证](/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" %} +- 如果对分支启用了必需提交签名，则无法将任何提交推送到未签名和验证的分支。 更多信息请参阅“[关于提交签名验证](/articles/about-commit-signature-verification)”和“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-signed-commits)”。{% 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-pull-request-reviews.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index e42f3a7fa2c20..31379b610e5d0 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 @@ -44,9 +44,7 @@ versions: ### 必要的审查 -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -更多信息请参阅“[关于拉取请求的必需审查](/articles/about-required-reviews-for-pull-requests)”。 +{% data reusables.pull_requests.required-reviews-for-prs-summary %} 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。 {% tip %} @@ -57,6 +55,5 @@ versions: ### 延伸阅读 - "[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[启用拉取请求的必需审查](/articles/enabling-required-reviews-for-pull-requests)" - "[查看拉取请求审查](/articles/viewing-a-pull-request-review)" - "[设置仓库贡献者的指导方针](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index 51f633f1ba25b..5f17442d40dfc 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -有关必需审查的更多信息，请参阅“[关于拉取请求的必需审查](/articles/about-required-reviews-for-pull-requests)”。 +有关必需审查的更多信息，请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。 -您可以评论拉取请求、批准更改或在批准前申请改进。 更多信息请参阅“[关于拉取请求的必需审查](/articles/about-required-reviews-for-pull-requests)”和“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 +您可以评论拉取请求、批准更改或在批准前申请改进。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ versions: ### 延伸阅读 -- "[关于拉取请求的必要审查](/articles/about-required-reviews-for-pull-requests)" - "[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[评论拉取请求](/articles/commenting-on-a-pull-request)" diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 2f87444e67c2c..c20d56ccde3ae 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ versions: - 该拉取请求分支在您拥有推送权限的仓库中打开，并且是从仓库的复刻创建的 - 在用户拥有的复刻上 - 拥有拉取请求创建者授予的许可 -- 没有阻止您提交的[分支限制](/articles/about-branch-restrictions) +- 没有阻止您提交的[分支限制](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) 只有创建拉取请求的用户才能授予您向用户拥有的复刻推送提交的权限。 更多信息请参阅“[允许更改从复刻创建的拉取请求分支](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)”。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index d18fd968a03e2..32ddf6fec8eaf 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: 忽略拉取请求审查 -intro: '如果仓库 [要求审查](/articles/about-required-reviews-for-pull-requests)，可以忽略不再有效或无法被审查者批准的拉取请求审查。' +intro: '如果仓库要求审查，可以忽略不再有效或无法被审查者批准的拉取请求审查。' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ versions: - “[关于拉取请求审查](/articles/about-pull-request-reviews)” - "[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[关于拉取请求的必要审查](/articles/about-required-reviews-for-pull-requests)" +- "[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index bcd414ff3c3e4..ad2067c388434 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### 遵循 GitHub 流程 1. 从仓库[创建分支](/articles/creating-and-deleting-branches-within-your-repository)。 -2. [创建](/articles/creating-new-files)、[编辑](/articles/editing-files)、[重命名](/articles/renaming-a-file)、[移动](/articles/moving-a-file-to-a-new-location)或[删除](/articles/deleting-files)文件。 +2. [创建](/articles/creating-new-files)、[编辑](/articles/editing-files)、[重命名](/articles/renaming-a-file)、[移动](/articles/moving-a-file-to-a-new-location)或[删除](/github/managing-files-in-a-repository/deleting-files-in-a-repository)文件。 3. 从您的分支[发送拉取请求](/articles/creating-a-pull-request)，让您提议的更改引发讨论。 4. 根据需要在您的分支上进行更改。 您的拉取请求将自动更新。 5. 在分支处理就绪，可以合并时，[合并拉取请求](/articles/merging-a-pull-request)。 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 095fb8ad8e932..fe77de58a8e89 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 @@ -12,7 +12,7 @@ versions: ### 关于拉取请求合并 -在拉取请求中，您提议将您对头部分支所做的更改合并到基础分支。 {% data reusables.pull_requests.about-protected-branches %} 但是，对于何时可以将拉取请求合并到特定分支可能会有限制。 例如，如果必需状态检查通过，您可能只能将拉取请求合并到默认分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 +在拉取请求中，您提议将您对头部分支所做的更改合并到基础分支。 默认情况下，任何拉取请求都可随时合并，除非头部分支与基本分支冲突。 但是，何时可以将拉取请求合并到特定分支中可能会有一些限制。 例如，如果必需状态检查通过，您可能只能将拉取请求合并到默认分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 20744e85beb11..901072691bfc3 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,74 +1,72 @@ --- -title: Reviewing dependency changes in a pull request -intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +title: 审查拉取请求中的依赖项更改 +intro: '如果拉取请求包含对依赖项的更改，您可以查看已更改内容摘要以及任何依赖项中是否存在已知漏洞。' versions: free-pro-team: '*' --- {% note %} -**Note:** Dependency review is currently in beta and subject to change. +**注意：**依赖项审查目前处于测试阶段，可能会更改。 {% endnote %} -### About dependency review +### 关于依赖项审查 -If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. +如果拉取请求针对仓库的默认分支并且包含对包清单或锁定文件的更改，您可以显示依赖项审查以查看更改的内容。 依赖项审查包括对锁定文件中间接依赖项的更改详情，并告诉您任何已添加或更新的依赖项是否包含已知漏洞。 -Dependency review is available in: +依赖项审查适用于： -* All public repositories. -* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”。 +* 所有公共仓库。 +* 由具有 {% data variables.product.prodname_advanced_security %} 许可的组织所拥有并且启用了依赖关系图的私有仓库。 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”。 -Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. +有时，您可能只想更新清单中一个依赖项的版本并生成拉取请求。 但是，如果此直接依赖项的更新版本也更新了依赖项，则拉取请求的更改可能超过您的预期。 每个清单和锁定文件的依赖项审查提供了一种简单的方法来查看更改的内容，以及任何新的依赖项版本是否包含已知的漏洞。 -By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." +通过检查拉取请求中的依赖项审查并更改被标记为有漏洞的任何依赖项，可以避免将漏洞添加到项目中。 {% data variables.product.prodname_dependabot_alerts %} 将会查找依赖项中存在的漏洞，但避免引入潜在问题比在以后修复它们要好得多。 有关 {% data variables.product.prodname_dependabot_alerts %} 的更多信息，请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。 -Dependency review supports the same languages and package management ecosystems as the dependency graph. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 +依赖项审查支持与依赖关系图相同的语言和包管理生态系统。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 -### Reviewing dependencies in a pull request +### 审查拉取请求中的依赖项 {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %} -1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. +1. 如果拉取请求包含许多文件，请使用 **File filter（文件过滤器）**下拉菜单折叠所有不记录依赖项的文件。 这将有助于您将审查的重点放在依赖项更改上。 - ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![文件过滤器菜单](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. 在清单或锁定文件标头的右侧，单击 **{% octicon "file" aria-label="The rich diff icon" %}** 多差异按钮以显示依赖项审查。 - ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + ![多差异按钮](/assets/images/help/pull_requests/dependency-review-rich-diff.png) {% note %} - **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + **注：**依赖项审查提供关于大型锁定文件中已更改内容的更清晰视图，源差异在默认情况下不会呈现。 {% endnote %} -1. Check the dependencies listed in the dependency review. +1. 检查依赖项审查中列出的依赖项。 - ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + ![依赖项审查中的漏洞警告](/assets/images/help/pull_requests/dependency-review-vulnerability.png) - Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + 任何已添加或更改的有漏洞依赖项先按严重程度排序，然后按依赖项名称排序。 这意味着严重程度最高的依赖项始终处于依赖项审查的顶部。 其他依赖项按其名称的字母顺序排列。 - The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + 每个依赖项旁边的图标指示该依赖项在此拉取请求中已添加 ({% octicon "diff-added" aria-label="Dependency added icon" %})、更新 ({% octicon "diff-modified" aria-label="Dependency modified icon" %}) 或删除 ({% octicon "diff-removed" aria-label="Dependency removed icon" %})。 - Other information includes: + 其他信息包括： - * The version, or version range, of the new, updated, or deleted dependency. - * For a specific version of a dependency: - * The age of that release of the dependency. - * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. - * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + * 新、更新或删除的依赖项的版本或版本范围。 + * 对于依赖项的特定版本： + * 依赖项的发布时间。 + * 依赖此软件的项目数量。 此信息取自依赖关系图。 检查依赖项的数量可以帮助您避免意外添加错误的依赖项。 + * 此依赖项使用的许可（如果此信息可用）。 如果要避免在项目中使用具有某些许可的代码，此选项非常有用。 - Where a dependency has a known vulnerability, the warning message includes: + 如果依赖项具有已知漏洞，则警告消息包括： - * A brief description of the vulnerability. - * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. - * The severity of the vulnerability. - * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + * 漏洞的简要说明。 + * 通用漏洞披露 (CVE) 或 {% data variables.product.prodname_security_advisories %} (GHSA) 标识号。 您可以单击此 ID 以查找有关漏洞的更多信息。 + * 漏洞的严重程度。 + * 修复漏洞的依赖项版本。 审查某人的拉取请求时，您可以要求参与者将依赖项更新到修补版本或更新版本。 -1. You can return to the original view of the file by clicking the source diff button. - - ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} 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 907fa03d1190d..62eb44ca5a974 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 @@ -32,13 +32,15 @@ versions: {% if currentVersion == "free-pro-team@latest" %} ### 查看依赖项更改 -如果拉取请求包含对依赖项的更改，您可以使用清单或锁定文件的依赖项审阅来查看更改的内容，并检查更改是否引入安全漏洞。 For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +如果拉取请求包含对依赖项的更改，您可以使用清单或锁定文件的依赖项审阅来查看更改的内容，并检查更改是否引入安全漏洞。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% data reusables.repositories.changed-files %} -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. +1. 在清单或锁定文件标头的右侧，单击 **{% octicon "file" aria-label="The rich diff icon" %}** 多差异按钮以显示依赖项审查。 - ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + ![多差异按钮](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### 将文件标记为已查看 @@ -65,5 +67,5 @@ versions: ### 延伸阅读 -- "[关于拉取请求的必要审查](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[按审查状态过滤拉取请求](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 602779e14fd78..b75f9c601a242 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ versions: ### 在命令行上使用 `on-behalf-of` 徽章创建提交 -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. 输入提交消息以及简短、有意义的更改描述。 在提交描述后，不要加上右引号，而是添加两个空行。 + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **提示：** 如果您使用文本编辑器在命令行上输入提交消息，请确保在提交描述末尾与 `on-behalf-of:` 提交尾行之间有两个换行符。 + + {% endtip %} 2. 在提交消息的下一行，键入 `on-behalf-of: @org `，然后键入右引号。 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 3ef52bd5cf987..30c3ae9a25ccf 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 @@ -39,7 +39,17 @@ versions: {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +1. 输入提交消息以及简短、有意义的更改描述。 在提交描述后，不要加上右引号，而是添加两个空行。 + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **提示：** 如果您使用文本编辑器在命令行上输入提交消息，请确保在提交描述末尾与 `Co-authored-by:` 提交尾行之间有两个换行符。 + + {% endtip %} 3. 在提交消息的下一行，根据每个合作作者的特定信息键入 `Co-authored-by: name `。 在合作作者的信息后面，添加一个右引号。 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 f478fec023524..bee5e35f90c55 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 @@ -19,7 +19,7 @@ versions: 当有人打开修改代码的拉取请求时，将自动请求代码所有者进行审查。 不会自动请求代码所有者审查拉取请求草稿。 有关拉取请求草稿的更多信息，请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)”。 不会自动请求代码所有者审查拉取请求草稿。 如果将拉取请求转换为草稿，则已订阅通知的用户不会自动取消订阅。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)”。 -当具有管理员或所有者权限的人员启用必需审查时，他们也可选择性要求代码所有者批准后，作者才可合并仓库中的拉取请求。 更多信息请参阅“[启用拉取请求的必需审查](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)”。 +当具有管理员或所有者权限的人员启用必需审查时，他们也可选择性要求代码所有者批准后，作者才可合并仓库中的拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。 {% 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 %} diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index ec769955bea8d..d407044a68a9d 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ versions: {% endif %} 您可以使用仓库管理您的工作并与他人合作。 -- 您可以使用议题来收集用户反馈，报告软件缺陷，并组织您想要完成的任务。 更多信息请参阅“[关于议题](/github/managing-your-work-on-github/about-issues)”。 -- {% data reusables.discussions.you-can-use-discussions %} +- 您可以使用议题来收集用户反馈，报告软件缺陷，并组织您想要完成的任务。 更多信息请参阅“[关于议题](/github/managing-your-work-on-github/about-issues)”。{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - 您可以使用拉取请求来建议对仓库的更改。 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 - 您可以使用项目板来组织议题和拉取请求并排定优先级。 更多信息请参阅“[关于项目板](/github/managing-your-work-on-github/about-project-boards)”。 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 17c0ae58b6cd5..3ad42991687c8 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ versions: ### 检测许可 -[开源 Ruby gem 被许可人](https://github.com/benbalter/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/rest/reference/licenses) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](http://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。 +[开源 Ruby gem 被许可人](https://github.com/licensee/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/rest/reference/licenses) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](http://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。 如果您的仓库使用的许可列在“选择许可”网站中，但未明确显示在仓库页面顶部，其中可能包含多个许可或存在其他复杂性。 为使您的许可被检测到，请简化*许可*文件，并在其他位置注明复杂性，例如在仓库的*自述文件*中。 diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md index 0871503bf3766..aa56ee1d043b8 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: About billing for Codespaces -intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.' +title: 关于代码空间的计费 +intro: '当 {% data variables.product.prodname_codespaces %} 公开发布时，将按存储和计算使用情况计费。' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,18 +10,18 @@ versions: {% data reusables.codespaces.about-billing-for-codespaces %} -Compute costs are incurred only when a codespace is active. When you're using a codespace, the codespace is active. After 30 minutes of inactivity, a codespace becomes suspended automatically. +只有在代码空间处于活动状态时，才产生计算费用。 使用代码空间时，代码空间即处于活动状态。 处于非活动状态 30 分钟后，代码空间将自动挂起。 -Compute usage is billed per hour, at a rate that depends on your codespace's instance type. During the beta, {% data variables.product.prodname_codespaces %} offers a single, Linux instance type. At general availability, we'll support three Linux instance types. +计算使用按小时计费，其费率取决于代码空间的实例类型。 在测试期间， {% data variables.product.prodname_codespaces %} 提供单一的 Linux 实例类型。 在公开发布后，我们将提供三种 Linux 实例类型。 -| Instance Type (Linux) | Per-hour rate | -| --------------------------------------- | ------------- | -| Basic (2 cores, 4GB RAM, 32 GB SSD) | $0.085 | -| Standard (4 cores, 8 GB RAM, 32 GB SSD) | $0.169 | -| Premium (8 cores, 16 GB RAM, 32 GB SSD) | $0.339 | +| 实例类型 (Linux) | 每小时费率 | +| --------------------------- | -------- | +| 基础（2 内核，4GB RAM，32 GB SSD） | 0.085 美元 | +| 标准（4 内核，8GB RAM，32 GB SSD） | 0.169 美元 | +| 高级（8 内核，16GB RAM，32 GB SSD） | 0.339 美元 | -Compute pricing may vary for additional instance types and operating systems supported in the future. +对于将来支持的其他实例类型和操作系统，计算定价可能会有所不同。 -Each codespace also incurs monthly storage costs until you delete the codespace. Storage costs for all instance types are $0.10/GB-month. +每个代码空间还会产生每月存储费用，直到您删除该代码空间。 所有实例类型的存储费用为 0.10 美元/GB-月。 -We'll share more information about any compute and storage usage included in each plan at general availability. +我们将在公开发布时分享有关每个计划中计算和存储使用情况的更多信息， diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/about-codespaces.md index 8328dc22cae17..31632919714df 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ versions: {% data reusables.codespaces.about-personalization %} 更多信息请参阅“[个性化您帐户的 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)”。 +您可以配置设置以添加加密密码、启用 GPG 验证以及允许代码空间访问其他仓库。 更多信息请参阅“[管理 {% data variables.product.prodname_codespaces %} 的加密密码](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)”、“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”以及“[管理 {% data variables.product.prodname_codespaces %} 的访问权限和设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)”。 + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/index.md b/translations/zh-CN/content/github/developing-online-with-codespaces/index.md index df194c0a02d61..e74bab9623a8b 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/index.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md new file mode 100644 index 0000000000000..0de052636d90b --- /dev/null +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -0,0 +1,37 @@ +--- +title: Managing access and security for Codespaces +intro: You can manage the repositories that codespaces can access. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### Managing security and access for your user account + +When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +### Managing security and access for your organization + +Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. + +When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.click-codespaces %} +5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. + ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md new file mode 100644 index 0000000000000..ad4d6a4a16f3a --- /dev/null +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -0,0 +1,53 @@ +--- +title: Managing encrypted secrets for Codespaces +intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +### About encrypted secrets for {% data variables.product.prodname_codespaces %} + +You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- Personal access tokens to cloud services +- Service principals +- Subscription identifiers + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. + +### Adding a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. 单击 **Add secret（添加密码）**。 + +### Editing a secret + +You can update the value of an existing secret, and you can change which repositories can access a secret. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user_settings.codespaces-secret-value %} +{% data reusables.user_settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. 单击 **Save changes（保存更改）**。 + +### Deleting a secret + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. 阅读警告，然后单击 **OK（确定）**。 ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md new file mode 100644 index 0000000000000..a326f5be89c93 --- /dev/null +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -0,0 +1,20 @@ +--- +title: Managing GPG verification for Codespaces +intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +product: '{% data reusables.gated-features.codespaces %}' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. + +{% endnote %} + +After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.codespaces-tab %} +1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/zh-CN/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index 4d90f659c4f89..bacd9daa040cf 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ Dotfiles 是类似 Unix 的系统上以 `.` 开头的文件和文件夹，用于 {% endnote %} +您还可以配置用户帐户的设置以添加加密密码、启用 GPG 验证以及允许代码空间访问其他仓库。 更多信息请参阅“[管理 {% data variables.product.prodname_codespaces %} 的加密密码](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)”、“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”以及“[管理 {% data variables.product.prodname_codespaces %} 的访问权限和设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index 27efd7e74b58c..cece5af4d1bd5 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -46,12 +46,12 @@ versions: ### 配置 {% data variables.product.prodname_vs %} 的代码空间 -A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. +使用 {% data variables.product.prodname_vs %} 创建的代码空间可以通过名为 devinit 的新工具进行自定义，该工具是 {% data variables.product.prodname_vs %} 附带的命令行工具。 #### devinit -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. +[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) 允许您将额外的框架和工具安装到 Windows 开发代码空间中以及修改环境变量等。 -devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. +devinit 支持名为 [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json) 的配置文件。 如果要创建自定义且可重复的开发环境，可以将此文件添加到项目中。 当您将 devinit 与 [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) 文件结合使用时，您的代码空间将在创建时自动配置。 -有关 Windows 代码空间配置和 devinit 的更多信息，请参阅 {% data variables.product.prodname_vs %} 文档中的[自定义代码空间](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces)。 For more information about devinit, see [Getting started with devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). +有关 Windows 代码空间配置和 devinit 的更多信息，请参阅 {% data variables.product.prodname_vs %} 文档中的[自定义代码空间](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces)。 有关 devinit 的更多信息，请参阅 [devinit 使用入门](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit)。 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 c276e19fea07b..7359928c50456 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ versions: 如果 {% data variables.product.prodname_code_scanning %} 发现您的代码中可能存在漏洞或错误，{% data variables.product.prodname_dotcom %} 会在仓库中显示警报。 在修复触发警报的代码之后，{% data variables.product.prodname_dotcom %} 将关闭警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}。 有关 API 端点的更多信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)”。 +要监控您的仓库或组织的 {% data variables.product.prodname_code_scanning %} 结果，您可以使用 web 挂钩和 {% data variables.product.prodname_code_scanning %} API。 有关用于 {% data variables.product.prodname_code_scanning %} 的 web 挂钩的信息，请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)”。 有关 API 端点的信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)”。 要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 @@ -54,7 +54,7 @@ versions: ### 延伸阅读 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) - 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/configuring-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index d11a128b1c2ea..612c2f62274d4 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -238,7 +238,9 @@ 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. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. + +The settings in the file are written in YAML format. #### Specifying additional queries 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 02103784f37c3..5110a6aca1fea 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 @@ -1,5 +1,5 @@ --- -title: Configuring CodeQL code scanning in your CI system +title: 在 CI 系统中配置 CodeQL 代码扫描 shortTitle: 在 CI 中配置 intro: '您可以配置 {% data variables.product.prodname_codeql_runner %} 如何扫描项目中的代码并将结果上传到 {% data variables.product.prodname_dotcom %}。' product: '{% data reusables.gated-features.code-scanning %}' @@ -15,9 +15,9 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system +### 关于在 CI 系统中配置 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %} -要将 {% data variables.product.prodname_code_scanning %} 集成到 CI 系统中，您可以使用 {% data variables.product.prodname_codeql_runner %}。 For more information, see "[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_code_scanning %} 集成到 CI 系统中，您可以使用 {% data variables.product.prodname_codeql_runner %}。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。 一般情况下，调用 {% data variables.product.prodname_codeql_runner %} 如下所示。 @@ -89,13 +89,13 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` -如果 `autobuild` 命令无法构建您的代码，您可以在 `init` 与 `analyze` 步骤之间手动运行构建步骤。 For more information, see "[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#compiled-language-example)." +如果 `autobuild` 命令无法构建您的代码，您可以在 `init` 与 `analyze` 步骤之间手动运行构建步骤。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system#compiled-language-example)”。 ### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %} 默认情况下，当您运行 `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-the-alerts-for-a-repository)." +上传数据后，{% 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#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/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 47d98b6437925..411391e51713e 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -3,7 +3,7 @@ title: 为编译语言配置 CodeQL 工作流程 shortTitle: 为编译语言配置 intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何使用 {% data variables.product.prodname_codeql_workflow %} 扫描用编译语言编写的代码以查找漏洞和错误。' 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: '如果您拥有仓库的写入权限，您可以为该仓库配置 {% data variables.product.prodname_code_scanning %}。' 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 @@ -20,8 +20,8 @@ versions: To enable {% data variables.product.prodname_code_scanning %} for your repository, you add to the repository a {% data variables.product.prodname_actions %} workflow which includes {% data variables.product.prodname_codeql %} analysis. 更多信息请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，您可以添加 {% data variables.product.prodname_codeql_workflow %}。 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 {% data reusables.code-scanning.edit-workflow %} -For general information about configuring -{% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +有关配置 +{% data variables.product.prodname_code_scanning %} 和编辑工作流程文件的一般信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 ### 关于 {% data variables.product.prodname_codeql %} 的自动构建 @@ -39,17 +39,17 @@ For general information about configuring #### C/C++ -| 支持的系统类型 | 系统名称 | -| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| 操作系统 | Windows, macOS, and Linux | -| 构建系统 | Windows: MSbuild and build scripts
            Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts | +| 支持的系统类型 | 系统名称 | +| ------- | ---------------------------------------------------------------------------------------------------------- | +| 操作系统 | Windows、macOS 和 Linux | +| 构建系统 | Windows：MSbuild 和构建脚本
            Linux 和 macOS：Autoconf、Make、CMake、qmake、Meson、Waf、SCons、Linux Kbuild 和构建脚本 | -`autobuild` 步骤的行为因提取运行所在的操作系统而异。 On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach: +`autobuild` 步骤的行为因提取运行所在的操作系统而异。 在 Windows 上，`autobuild` 步骤尝试使用以下方法自动检测合适的 C/C# 构建方法： -1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root. 如果 `autobuild` 在顶层目录下的相同深度（最短）检测到多个解决方案或项目文件，它将尝试构建所有这些文件。 -2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order). +1. 在最接近根目录的解决方案 (`.sln`) 或项目 (`.vcxproj`) 文件上调用 `MSBuild.exe`。 如果 `autobuild` 在顶层目录下的相同深度（最短）检测到多个解决方案或项目文件，它将尝试构建所有这些文件。 +2. 调用看起来像构建脚本的脚本—_build.bat_、_build.cmd_ _和 build.exe_（按此顺序）。 -On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used: +在 Linux 和 macOS 上，`autobuild` 步骤检查仓库中存在的文件，以确定所使用的构建系统： 1. 在根目录中查找构建系统。 2. 如果未找到，则搜索子目录以查找含有 C/C++ 构建系统的唯一目录。 @@ -70,10 +70,10 @@ On Linux and macOS, the `autobuild` step reviews the files present in the reposi #### Java -| 支持的系统类型 | 系统名称 | -| ------- | ------------------------------------------ | -| 操作系统 | Windows, macOS, and Linux (no restriction) | -| 构建系统 | Gradle、Maven 和 Ant | +| 支持的系统类型 | 系统名称 | +| ------- | -------------------------- | +| 操作系统 | Windows、macOS 和 Linux（无限制） | +| 构建系统 | Gradle、Maven 和 Ant | `autobuild` 进程尝试通过应用此策略来确定 Java 代码库的构建系统： 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 b355df593ca63..061488ea3bd57 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 @@ -40,13 +40,16 @@ versions: 在默认 {% data variables.product.prodname_codeql_workflow %} 中，{% data variables.product.prodname_code_scanning %} 配置为在每次将更改推送到默认分支或任何受保护分支或者对默认分支提出拉取请求时分析代码。 因此，{% data variables.product.prodname_code_scanning %} 将立即开始。 +### 批量启用 {% data variables.product.prodname_code_scanning %} +您可以使用脚本在多个仓库中批量启用 {% data variables.product.prodname_code_scanning %}。 有关提出拉取请求以向多个仓库添加 {% data variables.product.prodname_actions %} 工作流程的脚本示例，请参阅 [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) 仓库。 + ### 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 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 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)." + 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)." 条目的文本是提交消息的标题。 ![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) @@ -58,7 +61,7 @@ After you enable {% data variables.product.prodname_code_scanning %}, you can mo 1. 查看此工作流运行时操作的日志记录输出。 -1. 在所有作业完成后，您可以查看已识别的任何 {% 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#viewing-the-alerts-for-a-repository)." +1. 在所有作业完成后，您可以查看已识别的任何 {% 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#viewing-the-alerts-for-a-repository)”。 {% note %} 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 4a9e665f1fbcd..30fabe29bd868 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,9 +1,9 @@ --- -title: Managing code scanning alerts for your repository +title: 管理仓库的代码扫描警报 shortTitle: 管理警报 -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.' +intro: '从安全视图中，您可以查看、修复、{% if currentVersion == "enterprise-server@2.22" %}或关闭{% else %}忽略或删除{% endif %}项目代码中潜在漏洞或错误的警报。' 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: '如果您拥有仓库的写入权限，您可以管理该仓库的 {% data variables.product.prodname_code_scanning %} 警报。' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -16,11 +16,11 @@ redirect_from: ### 关于 {% data variables.product.prodname_code_scanning %} 中的警报 -You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 +您可以设置 {% data variables.product.prodname_code_scanning %}，以使用默认 {% data variables.product.prodname_codeql %} 分析、第三方分析或多种类型的分析来检查仓库中的代码。 分析完成后，生成的警报将并排显示在仓库的安全视图中。 第三方工具或自定义查询的结果可能不包括您在 {% data variables.product.company_short %} 的默认 {% data variables.product.prodname_codeql %} 分析所检测的警报中看到的所有属性。 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 -By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, 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)." +默认情况下， {% data variables.product.prodname_code_scanning %} 定期在默认分支和拉取请求中分析您的代码。 有关管理拉取请求中的警报的更多信息，请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 -### About alerts details +### 关于警报详细信息 每个警报都会高亮显示代码的问题以及识别该问题的工具名称。 您可以看到触发警报的代码行以及警报的属性，例如问题的严重程度和性质。 警报还会告知该问题第一次被引入的时间。 对于由 {% data variables.product.prodname_codeql %} 分析确定的警报，您还会看到如何解决问题的信息。 @@ -30,59 +30,59 @@ 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 %} annotations on pull requests. 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 +任何对仓库有读取权限的人都可以查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 注释。 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/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. +您需要写入权限才能在 **Security（安全）**选项卡上查看仓库所有警报的摘要。 默认情况下，显示默认分支的警报。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) -1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png) -1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) +1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 ![警报摘要](/assets/images/help/repository/code-scanning-click-alert.png) +1. （可选）如果警报突出显示数据流的问题，请单击 **Show paths（显示路径）**以显示从数据源到使用它的接收者的路径。 ![警报上的"显示路径"链接](/assets/images/help/repository/code-scanning-show-paths.png) +1. 来自 {% data variables.product.prodname_codeql %} 分析的警报包括对问题的描述。 单击 **Show more（显示更多）**以获取有关如何修复代码的指导。 ![警报的详细信息](/assets/images/help/repository/code-scanning-alert-details.png) -### Fixing an alert +### 修复警报 -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)." +任何对仓库具有写入权限的人都可以通过提交对代码的更正来修复警报。 如果仓库已安排对拉取请求运行 {% data variables.product.prodname_code_scanning %}，则最好通过拉取请求提交您的更正。 这将触发对更改的 {% data variables.product.prodname_code_scanning %} 分析，并测试您的修复是否会带来任何新的问题。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”和“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/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 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 %}. +如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户{% if currentVersion == "enterprise-server@2.22" %}已关闭{% else %}已忽略{% 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. +警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。 -![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![按分支过滤警报](/assets/images/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} ### 关闭警报 -Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} +关闭警报是解决您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %} {% else %} -### Dismissing or deleting alerts +### 忽略或删除警报 -There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. +有两种方法可以关闭警报。 您可以修复代码中的问题，也可以忽略警报。 或者，如果您具有仓库的管理员权限，您可以删除警报。 删除警报适用于以下情况：您启用了 {% data variables.product.prodname_code_scanning %} 工具，然后决定删除它，或者您启用了 {% data variables.product.prodname_codeql %} 分析，但查询集超出您的需求，于是您从工具中删除了某些查询。 在这两种情况下，删除警报允许您清理 {% data variables.product.prodname_code_scanning %} 结果。 您可以在 **Security（安全）**选项卡中从摘要列表删除警报。 -Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. +忽略警报是关闭您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %} 您可以从代码中的 {% data variables.product.prodname_code_scanning %} 注释忽略警报，或者从 **Security（安全）**选项卡中的摘要列表忽略警报。 -When you dismiss an alert: +当您忽略警报时： -- It's dismissed in all branches. -- The alert is removed from the number of current alerts for your project. -- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required. -- The reason why you closed the alert is recorded. -- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert. +- 它在所有分支中被忽略。 +- 警报将从项目的当前警报数中删除。 +- 警报被移动到警报摘要中的“Closed（已关闭）”列表，需要时您可以在其中重新打开它。 +- 将记录您关闭警报的原因。 +- {% data variables.product.prodname_code_scanning %} 下次运行时，相同的代码将不会生成警报。 -When you delete an alert: +当您删除警报时： -- It's deleted in all branches. -- The alert is removed from the number of current alerts for your project. -- It is _not_ added to the "Closed" list in the summary of alerts. -- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results. +- 它在所有分支中被删除。 +- 警报将从项目的当前警报数中删除。 +- 它_不会_添加到警报摘要中的“Closed（已关闭）”列表。 +- 如果生成警报的代码保持不变，并且相同的 {% data variables.product.prodname_code_scanning %} 工具在不更改任何配置的情况下再次运行，则该警报将再次显示在您的分析结果中。 -To dismiss or delete alerts: +要忽略或删除警报： {% endif %} @@ -91,39 +91,39 @@ To dismiss or delete alerts: {% 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. - ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) +1. 选择 **Close（关闭）**下拉菜单，然后单击关闭警报的原因。 + ![通过 Close（关闭）下拉菜单选择关闭警报的原因](/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. 如果您拥有仓库管理员权限，想要删除此 {% data variables.product.prodname_code_scanning %} 工具的警报，请选中部分或全部复选框，然后单击 **Delete（删除）**。 - ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) + ![删除警报](/assets/images/help/repository/code-scanning-delete-alerts.png) - Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. + （可选）您可以使用过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。 - ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![按规则过滤警报](/assets/images/help/repository/code-scanning-filter-by-rule.png) -1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. +1. 如果要忽略警报，请务必先了解警报，以便选择正确的忽略原因。 单击要了解的警报。 - ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) + ![从摘要列表中打开警报](/assets/images/help/repository/code-scanning-click-alert.png) -1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) +1. 查看警报，然后单击 **Dismiss（忽略）**并选择关闭警报的原因。 ![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} {% data reusables.code-scanning.false-positive-fix-codeql %} -#### Dismissing multiple alerts at once +#### 一次忽略多个警报 -If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability. +如果项目有多个由于相同原因要忽略的警报，您可以从警报摘要中批量忽略它们。 通常，您需要过滤列表，然后忽略所有匹配的警报。 例如，您可能想要忽略项目中所有已标记为特定通用缺陷枚举 (CWE) 漏洞的当前警报。 {% endif %} ### 延伸阅读 -- "[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)" -- "[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)" -- "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" +- “[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)” +- “[为仓库启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)” +- "[关于与 {% data variables.product.prodname_code_scanning %} 集成](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index 04564d1fff7dc..63ff9a5620a9d 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -1,7 +1,7 @@ --- -title: Running CodeQL code scanning in a container -shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container' -intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.' +title: 在容器中运行 CodeQL 代码扫描 +shortTitle: '容器中的 {% data variables.product.prodname_code_scanning_capc %}' +intro: '通过确保所有进程都在同一容器中运行，您可以在容器中运行 {% data variables.product.prodname_code_scanning %}。' product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' @@ -10,23 +10,23 @@ versions: {% data reusables.code-scanning.beta %} -### About {% data variables.product.prodname_code_scanning %} with a containerized build +### 关于使用容器化构建的 {% data variables.product.prodname_code_scanning %} -If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled. +如果为编译语言设置 {% data variables.product.prodname_code_scanning %}，并且在容器化环境中构建代码，则分析可能会失败，并返回错误消息“No source code was seen during the build（在构建过程中没有看到源代码）”。 这表明 {% data variables.product.prodname_codeql %} 在代码编译过程中无法监视代码。 -You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)”。 If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." +您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 这适用于您使用 {% data variables.product.prodname_codeql_runner %} 或 {% data variables.product.prodname_actions %}。 如果您使用 {% data variables.product.prodname_codeql_runner %}，请在代码构建容器中运行它。 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)”。 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。 ### 依赖项 -You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: +如果您使用的容器缺少某些依赖项（例如，Git 必须安装并添加到 PATH 变量），您可能难以运行 {% data variables.product.prodname_code_scanning %}。 如果遇到依赖项问题，请查看通常包含在 {% data variables.product.prodname_dotcom %} 虚拟环境中的软件列表。 有关更多信息，请在以下位置查看特定于版本的 `readme` 文件： * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win -### Example workflow +### 示例工作流程 -This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)”。 +此示例工作流程在容器化环境中使用 {% data variables.product.prodname_actions %} 运行 {% data variables.product.prodname_codeql %} 分析。 `container.image` 的值标识要要使用的容器。 在此示例中，映像名称为 `codeql-container`，标记为 `f0f91db`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)”。 ``` yaml name: "{% data variables.product.prodname_codeql %}" 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 cbaa80d551815..3a898491ba7a4 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 @@ -1,7 +1,7 @@ --- -title: Running CodeQL code scanning in your CI system +title: 在 CI 系统中运行 CodeQL 代码扫描 shortTitle: 在 CI 中运行 -intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' +intro: '您可以使用 {% data variables.product.prodname_codeql_runner %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system @@ -18,7 +18,7 @@ versions: ### 将 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 与现有的 CI 系统一起使用 -If you use a continuous integration or continuous delivery/deployment (CI/CD) system other than {% data variables.product.prodname_actions %}, you can use your existing system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. To do this, use the {% data variables.product.prodname_codeql_runner %}. +如果您使用 {% data variables.product.prodname_actions %} 以外的持续集成或持续交付/部署 (CI/CD) 系统，您可以使用现有系统运行 {% data variables.product.prodname_dotcom %} 的 {% data variables.product.prodname_codeql %}，并将结果上传到 {% data variables.product.prodname_dotcom %}。 为此，请使用 {% data variables.product.prodname_codeql_runner %}。 ### 关于 {% data variables.product.prodname_codeql_runner %} @@ -28,7 +28,16 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy {% data variables.product.prodname_codeql_runner %} 是在 {% data variables.product.prodname_dotcom %} 仓库的检出上运行 {% data variables.product.prodname_codeql %} 分析的命令行工具。 您可以将运行器添加到第三方系统，然后调用运行器以分析代码并将结果上传到 {% data variables.product.product_location %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。 -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**注意：** +{% if currentVersion == "free-pro-team@latest" %} +* {% data variables.product.prodname_codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码，因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库，并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”和“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 +{% else %} +* {% data variables.product.prodname_codeql_runner %} 可用于拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户。 +{% endif %} +* 请勿将 {% data variables.product.prodname_codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 {% data variables.product.prodname_codeql %} CLI 是一个交互式命令行接口，允许您创建用于安全研究的 {% data variables.product.prodname_codeql %} 数据库并运行 {% data variables.product.prodname_codeql %} 查询。 更多信息请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 +{% endnote %} ### 下载 {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ You should call the {% data variables.product.prodname_codeql_runner %} from the ### 将 {% data variables.product.prodname_codeql_runner %} 添加到 CI 系统 -下载 {% data variables.product.prodname_codeql_runner %} 并确认它可执行后，应将运行器提供给您打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: +下载 {% data variables.product.prodname_codeql_runner %} 并确认它可执行后，应将运行器提供给您打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如，您可以配置每台服务器从中央内部位置复制运行器。 或者，您可以使用 REST API 直接从 GitHub 获取运行器，例如： ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux 除此之外，每个 CI 服务器还需要： -- {% data variables.product.prodname_github_apps %} 或供 {% data variables.product.prodname_codeql_runner %} 使用的个人访问令牌。 对于私有仓库，令牌必须具有 `repo` 作用域。 对于公共仓库，令牌只需要 `public_repo` 和 `repo:security_events` 作用域。 更多信息请参阅“[构建 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 -- 访问与此 {% data variables.product.prodname_codeql_runner %} 发行版相关联的 {% data variables.product.prodname_codeql %} 包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的 {% data variables.product.prodname_codeql %} CLI、查询和库。 更多信息请参阅“[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)”。 +- {% data variables.product.prodname_github_app %} 或供 {% data variables.product.prodname_codeql_runner %} 使用的个人访问令牌。 您必须使用具有 `security_events` 作用域的访问令牌，或者具有 `security_events` 写入权限的 {% data variables.product.prodname_github_app %}。 更多信息请参阅“[构建 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +- 访问与此 {% data variables.product.prodname_codeql_runner %} 发行版相关联的 {% data variables.product.prodname_codeql %} 包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的查询和库，以及供运行器内部使用的 {% data variables.product.prodname_codeql %} CLI。 更多信息请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 提供 {% data variables.product.prodname_codeql %} 包访问权限的选项： 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 71400c1fe226d..ea7682afc7076 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 @@ -1,9 +1,9 @@ --- -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.' +title: 鉴定拉取请求中的代码扫描警报 +shortTitle: 鉴定拉取请求中的警报 +intro: '当 {% data variables.product.prodname_code_scanning %} 在拉取请求中发现问题时，您可以审查高亮的代码并解决警报。' product: '{% data reusables.gated-features.code-scanning %}' -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.' +permissions: '如果您拥有仓库的读取权限，您可以查看对拉取请求的注释。 如果拥有写入权限，您可以查看详细信息并解决该仓库的 {% data variables.product.prodname_code_scanning %} 警报。' versions: free-pro-team: '*' enterprise-server: '>=2.22' @@ -11,56 +11,56 @@ versions: {% data reusables.code-scanning.beta %} -### About {% data variables.product.prodname_code_scanning %} results on pull requests +### 关于拉取请求上的 {% data variables.product.prodname_code_scanning %} 结果 -In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the 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. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository 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)." +在仓库中，如果 {% data variables.product.prodname_code_scanning %} 被配置为拉取请求检查，则 {% data variables.product.prodname_code_scanning %} 将检查拉取请求中的代码。 默认情况下，这仅限于针对默认分支的拉取请求，但是您可以在 {% data variables.product.prodname_actions %} 或第三方 CI/CD 系统中更改此配置。 如果合并分支给目标分支带来新的 {% data variables.product.prodname_code_scanning %} 警报，这些警报将在拉取请求中被报告为检查结果。 警报还将在拉取请求的 **Files changed（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% 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)”。 -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. 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. 更多信息请参阅“[关于必要的状态检查](/github/administering-a-repository/about-required-status-checks)”。 +如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对已为 {% data variables.product.prodname_code_scanning %} 启用的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或{% if currentVersion == "enterprise-server@2.22" %}关闭{% else %}忽略{% endif %}所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 -![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) +![拉取请求上失败的 {% data variables.product.prodname_code_scanning %} 检查](/assets/images/help/repository/code-scanning-check-failure.png) -### About {% data variables.product.prodname_code_scanning %} as a pull request check +### 关于 {% data variables.product.prodname_code_scanning %} 作为拉取请求检查 -There are many options for configuring {% data variables.product.prodname_code_scanning %} as a pull request check, so the exact setup of each repository will vary and some will have more than one check. The check that contains the results of {% data variables.product.prodname_code_scanning %} is: **Code scanning results**. +有许多选项可将 {% data variables.product.prodname_code_scanning %} 配置为拉取请求检查，因此每个仓库的确切设置会有所不同，有些仓库还会有多个检查。 包含 {% data variables.product.prodname_code_scanning %} 结果的检查为：**代码扫描结果**。 -If the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java). As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" or "[Troubleshooting {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)." +如果仓库使用 {% data variables.product.prodname_codeql_workflow %}，则在结果检查运行之前，将针对每种语言运行 **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** 检查。 如果存在配置问题，或者拉取请求中断了分析需要编译的语言（例如 C/C ++、C# 或 Java）的构建，则分析检查可能会失败。 与其他拉取请求检查一样，您可以在 **Checks（检查）**选项卡上查看检查失败的完整细节。 有关配置和故障排除的详细信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”或“[排查 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)”。 -### Triaging an alert on your pull request +### 鉴定拉取请求上的警报 -When you look at the **Files changed** tab for a pull request, you see annotations for any lines of code that triggered the alert. +查看拉取请求的 **Files changed（文件已更改）**选项卡时，您会看到任何触发警报的代码行的注释。 -![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png) +![拉取请求差异中的警报注释](/assets/images/help/repository/code-scanning-pr-annotation.png) -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)." +如果您拥有仓库的写入权限，则某些注释将包含警报额外上下文的链接。 在上例中，您可以在 {% data variables.product.prodname_codeql %} 分析中单击 **user-provided value（用户提供的值）**，以查看不受信任的数据进入数据流的位置（这被称为源）。 在此例中，您还可以通过单击 **Show paths（显示路径）**来查看从源到使用数据的代码（池）的完整路径。 这样就很容易检查数据是否不受信任，或者分析是否无法识别源与池之间的数据净化步骤。 有关使用 {% data variables.product.prodname_codeql %} 分析数据流的信息，请参阅“[关于数据流分析](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)”。 -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. +要查看有关警报的更多信息，拥有写入权限的用户可单击注释中所示的 **Show more details（显示更多详情）**链接。 这允许您在警报视图中查看工具提供的所有上下文和元数据。 在下例中，您可以查看显示问题的严重性、类型和相关通用缺陷枚举 (CWE) 的标记。 该视图还显示哪个提交引入了问题。 -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. +在警报的详细视图中，有些 {% data variables.product.prodname_code_scanning %} 工具，例如 {% data variables.product.prodname_codeql %} 分析，还包括问题描述和 **Show more（显示更多）**链接以指导您如何修复代码。 -![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png) +![显示更多信息的警报说明和链接](/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" %}解决{% else %}修复{% endif %}拉取请求上的警报 -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. +任何对拉取请求具有推送权限的人都可以修复在该拉取请求上已识别的 {% data variables.product.prodname_code_scanning %} 警报。 如果将更改提交到拉取请求，这将触发拉取请求检查的新运行。 如果您的更改修复了问题，则警报将被关闭，注释将被删除。 {% if currentVersion == "enterprise-server@2.22" %} -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.close-alert-examples %} 如果您对仓库有写入权限，则 **Close（关闭）**按钮在注释和警报视图中可用。 {% data reusables.code-scanning.false-positive-fix-codeql %} {% else %} -### Dismissing an alert on your pull request +### 忽略拉取请求上的警报 -An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert. +关闭警报的另一种办法是忽略它。 您可以忽略您认为不需要修复的警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Dismiss（忽略）**按钮在代码注释和警报摘要中可用。 单击 **Dismiss（忽略）**时，您将被提示选择关闭警报的原因。 -![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) +![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} {% data reusables.code-scanning.false-positive-fix-codeql %} -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)." +有关忽略警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。 {% endif %} diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index 068aded2d7c5c..acd1eaa90e1f3 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Troubleshooting CodeQL code scanning in your CI system -shortTitle: Troubleshooting in your CI -intro: 'If you''re having problems with the {% data variables.product.prodname_codeql_runner %}, you can troubleshoot by using these tips.' +title: CI 系统中的 CodeQL 代码扫描故障排除 +shortTitle: CI 中的故障排除 +intro: '如果您在 {% data variables.product.prodname_codeql_runner %} 方面遇到问题，可使用这些提示来排除故障。' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system @@ -12,41 +12,43 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} -### The `init` command takes too long +### `init` 命令耗时太长 -Before the {% data variables.product.prodname_codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries. +在 {% data variables.product.prodname_codeql_runner %} 可以构建和分析代码之前，它需要访问 {% data variables.product.prodname_codeql %} 包，其中包含 {% data variables.product.prodname_codeql %} CLI 和 {% data variables.product.prodname_codeql %} 库。 -When you use the {% data variables.product.prodname_codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes. The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.product.prodname_codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again. +首次在计算机上使用 {% data variables.product.prodname_codeql_runner %} 时，`init` 命令会将 {% data variables.product.prodname_codeql %} 包下载到您的计算机上。 此下载可能需要几分钟时间。 +{% data variables.product.prodname_codeql %} 包在运行之间缓存，因此如果您在同一台计算机上再次使用 {% data variables.product.prodname_codeql_runner %}，它不会再次下载 {% data variables.product.prodname_codeql %} 包。 -To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command. +为避免这种自动下载，您可以手动将 {% data variables.product.prodname_codeql %} 包下载到您的计算机上，并使用 `init` 命令的 `--codeql-path` 标志指定路径。 ### 构建过程中找不到代码 -If the `analyze` command for the {% data variables.product.prodname_codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure. +如果用于 {% data variables.product.prodname_codeql_runner %} 的 `analyze` 命令失败并返回错误 `No source code was seen during the build`，这表明 {% data variables.product.prodname_codeql %} 无法监视您的代码。 有几个原因可以解释这种失败。 -1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)." +1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 要解决此问题，您可以使用 `init` 命令的 `--languages` 标志，手动定义要分析的语言。 更多信息请参阅“[在 CI 系统中配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)”。 -1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the code. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command. - - On macOS and Linux: +1. 您没有使用 `autobuild` 命令分析编译语言，并且在 `init` 步骤后手动运行构建步骤。 要使构建正常工作，您必须设置环境，使 {% data variables.product.prodname_codeql_runner %} 能够监视代码。 `init` 命令生成如何导出所需环境变量的指令， 因此您可以在运行 `init` 命令后复制和运行脚本。 + - 在 macOS 和 Linux 上： ```shell $ . codeql-runner/codeql-env.sh ``` - - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`): + - 在 Windows 上，使用命令 shell (`cmd`) 或批处理文件 (`.bat`)： ```shell > call codeql-runner\codeql-env.bat ``` - - On Windows, using PowerShell: + - 在 Windows 上，使用 PowerShell ： ```shell > cat codeql-runner\codeql-env.sh | Invoke-Expression ``` - The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead. + 环境变量也存储在文件 `codeql-runner/codeql-env.json` 中。 此文件包含单个 JSON 对象，它将环境变量键映射到值。 如果无法运行由 `init` 命令生成的脚本，您可以改用 JSON 格式的数据。 {% note %} - **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different. + **注：**如果您使用 `init` 命令的 `--temp-dir` 标志来指定临时文件的自定义目录，则 `codeql-env` 文件的路径可能不同。 {% endnote %} -1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.product.prodname_codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)." +1. 代码在容器或在单独的计算机上构建。 如果您使用容器化的构建，或者将构建外包给另一台计算机，请确保在容器或您执行构建任务的计算机上运行 {% data variables.product.prodname_codeql_runner %}。 更多信息请参阅“[在容器中运行 CodeQL 代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)”。 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 e3c8e6452344b..f1c4d3e53a375 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 @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Automatic build for a compiled language fails @@ -83,16 +84,6 @@ For more information about specifying build steps, see "[Configuring the {% data The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. 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)." -### Error: "Server error" - -If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. - -### Error: "Out of disk" or "Out of memory" - -On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - ### The build takes too long If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. @@ -127,3 +118,53 @@ If you are analyzing code written in Python, you may see different results depen On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." {% endif %} + +### Error: "Server error" + +If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. + +### Error: "Out of disk" or "Out of memory" + +On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} + +### Warning: "git checkout HEAD^2 is no longer necessary" + +If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: + +``` +Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +The revised `steps` section of the workflow will look like this: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file 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 5f9f57a2ff8f7..9361ebae6a8f1 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 @@ -27,6 +27,8 @@ versions: - {% data variables.product.prodname_dotcom %} 将在仓库中显示来自上传的 SARIF 文件的 {% data variables.product.prodname_code_scanning %} 警报。 如果您阻止自动上传，在准备上传结果时可以使用 `upload` 命令（更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”）。 - 作为仓库外部构件生成结果的工具，您可以使用 {% data variables.product.prodname_code_scanning %} API 上传文件（更多信息请参阅“[上传 SARIF 文件](/rest/reference/code-scanning#upload-a-sarif-file)”）。 +{% data reusables.code-scanning.not-available %} + ### 通过 {% data variables.product.prodname_actions %} 上传 {% data variables.product.prodname_code_scanning %} 分析 要将第三方 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}，需要 {% data variables.product.prodname_actions %} 工作流程。 更多信息请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md index af71f4047d5b8..49dfcd2549eda 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md @@ -1,7 +1,7 @@ --- -title: Using CodeQL code scanning with your existing CI system -shortTitle: CodeQL CI system support -intro: 'The {% data variables.product.prodname_codeql_runner %} allows you to use your existing CI system to run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}.' +title: 在现有 CI 系统上使用 CodeQL 代码扫描 +shortTitle: CodeQL CI 系统支持 +intro: '{% data variables.product.prodname_codeql_runner %} 允许您使用现有的 CI 系统运行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。' mapTopic: true product: '{% data reusables.gated-features.code-scanning %}' versions: diff --git a/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md new file mode 100644 index 0000000000000..87ae5d07fb990 --- /dev/null +++ b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md @@ -0,0 +1,48 @@ +--- +title: About GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +--- + +### 关于 {% data variables.product.prodname_GH_advanced_security %} + +{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) + +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." + +### About {% data variables.product.prodname_advanced_security %} features + +A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: + +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。 + +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. 更多信息请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)”。 + +{% if currentVersion == "free-pro-team@latest" %} +- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 +{% endif %} + +For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} + +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)." + +Once your system is set up, you can enable and disable these features at the organization or repository level. 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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} + +### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} + +For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. + +For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}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)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +For information about purchasing a license for + +{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% endif %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md index b3407415d2362..cadfa0ec2c034 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: 手机版 GitHub -intro: '从移动设备对 {% data variables.product.company_short %} 上的工作进行分类、协作和管理。' +intro: '从移动设备对 {% data variables.product.product_name %} 上的工作进行分类、协作和管理。' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### 关于 {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} 目前作为 Android 和 iOS app 提供给 {% data variables.product.prodname_dotcom_the_website %} 用户。 +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} 为您提供随时随地快速高效使用 {% data variables.product.prodname_dotcom %} 的方式。 {% data variables.product.prodname_mobile %} 是通过可信的第一方客户端应用程序访问 {% data variables.product.prodname_dotcom %} 数据的安全可靠方式。 +{% data variables.product.prodname_mobile %} 为您提供随时随地快速高效使用 {% data variables.product.product_name %} 的方式。 {% data variables.product.prodname_mobile %} 是通过可信的第一方客户端应用程序访问 {% data variables.product.product_name %} 数据的安全可靠方式。 通过 {% data variables.product.prodname_mobile %}，您可以： - 管理、分类和清除通知 @@ -23,12 +26,38 @@ versions: 要安装 Android 或 iOS 版 {% data variables.product.prodname_mobile %}，请参阅 [{% data variables.product.prodname_mobile %}](https://github.com/mobile)。 +### 管理帐户 + +您可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的一个用户帐户和 {% data variables.product.prodname_ghe_server %} 上的一个用户帐户同时登录移动版。 + +{% data reusables.mobile.push-notifications-on-ghes %} + +如果您需要通过 VPN 访问企业，{% data variables.product.prodname_mobile %} 可能不适用于您的企业。 + +#### 基本要求 + +您必须在设备上安装 {% data variables.product.prodname_mobile %} 1.4 或更高版本，才能使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}。 + +要使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}，{% data variables.product.product_location %} 必须为 3.0 或更高版本，并且企业所有者必须为企业启用移动版支持。 更多信息请参阅“[发行说明](/enterprise-server/admin/release-notes)”和“[管理企业的 {% data variables.product.prodname_mobile %}](/admin/configuration/managing-github-for-mobile-for-your-enterprise)”。 + +在 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %} 测试期间，您必须使用 {% data variables.product.prodname_dotcom_the_website %} 上的用户帐户登录。 + +#### 添加、切换或登出账户 + +您可以使用 {% data variables.product.product_location %} 上的帐户登录移动版。 在应用程序的底部，长按 {% octicon "person" aria-label="The person icon" %} **Profile（个人资料）**，然后点击 {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account（添加企业帐户）**。 按照提示登录。 + +使用 {% data variables.product.product_location %} 上的帐户登录移动版后，您可以在该帐户与 {% data variables.product.prodname_dotcom_the_website %} 帐户之间切换。 在应用程序的底部，长按 {% octicon "person" aria-label="The person icon" %} **Profile（个人资料）**，然后点击要切换到的帐户。 + +如果您不再需要从 {% data variables.product.prodname_mobile %} 访问 {% data variables.product.product_location %} 帐户的数据，您可以登出帐户。 在应用程序的底部，长按 {% octicon "person" aria-label="The person icon" %} **Profile（个人资料）**，向左滑动要登出的帐户，然后点击 **Sign out（登出）**。 + ### {% data variables.product.prodname_mobile %} 支持的语言 {% data variables.product.prodname_mobile %} 支持以下语言。 +- 英语 - 日语 - 巴西葡萄牙语 +- 简体中文 - 西班牙语 如果将设备上的语言配置为受支持的语言，则 {% data variables.product.prodname_mobile %} 默认为该语言。 您可以在 {% data variables.product.prodname_mobile %} 的 **Settings（设置）**菜单中更改 {% data variables.product.prodname_mobile %} 的语言。 @@ -37,9 +66,9 @@ versions: {% data variables.product.prodname_mobile %} 自动启用 iOS 的通用链接。 当您点击任何 {% data variables.product.product_name %} 链接时，目标 URL 都会在 {% data variables.product.prodname_mobile %} 中打开，而不是在 Safari 中打开。 更多信息请参阅 Apple Developer 网站上的[通用链接](https://developer.apple.com/ios/universal-links/)。 -要禁用通用链接，长按任意 {% data variables.product.prodname_dotcom %} 链接，然后点击 **Open（打开）**。 以后每次点击 {% data variables.product.prodname_dotcom %} 链接时，目标地址将在 Safari 中打开，而不是在 {% data variables.product.prodname_mobile %} 中打开。 +要禁用通用链接，长按任意 {% data variables.product.product_name %} 链接，然后点击 **Open（打开）**。 以后每次点击 {% data variables.product.product_name %} 链接时，目标地址将在 Safari 中打开，而不是在 {% data variables.product.prodname_mobile %} 中打开。 -要重新启用通用链接，长按任意 {% data variables.product.prodname_dotcom %} 链接，然后点击 **Open in {% data variables.product.prodname_dotcom %}（在 GitHub 中打开）**。 +要重新启用通用链接，长按任意 {% data variables.product.product_name %} 链接，然后点击 **Open in {% data variables.product.prodname_dotcom %}（在 GitHub 中打开）**。 ### 分享反馈 diff --git a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md index 495cf930cebfe..f26634bbe4a7c 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md +++ b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- title: GitHub 的产品 +intro: '{% data variables.product.prodname_dotcom %} 的产品和定价计划概述。' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -97,7 +98,7 @@ versions: - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”和“[关于 {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)（测试版）”。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}。 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)（测试版）“。{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}。 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)“。{% endif %} - [组织的 {% data variables.product.prodname_learning %}](https://lab.github.com/organizations) -有关注册 {% data variables.product.prodname_ghe_one %} 的更多信息，请联系 [{% data variables.product.product_name %} 的销售团队](https://enterprise.github.com/contact)。 +有关注册 {% data variables.product.prodname_ghe_one %} 的更多信息，请联系 {% data variables.contact.contact_enterprise_sales %}。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/index.md b/translations/zh-CN/content/github/getting-started-with-github/index.md index 45a93b67f4573..8cc2f1a74f476 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/index.md +++ b/translations/zh-CN/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md index dd3cf27debcd3..9f8104c532dd5 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -29,14 +29,14 @@ versions: ### 仓库 -| 键盘快捷键 | 描述 | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | 转到 **Code（代码）**选项卡 | -| g i | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | -| g p | 转到 **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 c | 转到 **Code（代码）**选项卡 | +| g i | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | +| g p | 转到 **Pull requests（拉取请求）**选项卡。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | g a | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %} -| g b | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | -| g w | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wikis](/articles/about-wikis)”。 | +| g b | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | +| g w | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wikis](/articles/about-wikis)”。 | ### 源代码编辑 @@ -159,6 +159,10 @@ versions: | 键盘快捷键 | 描述 | | -------------------------------------------------------- | ----------------------- | | command + space 或 control + space | 在工作流程编辑器中，获取对工作流程文件的建议。 | +| g f | 转到工作流程文件 | +| shift + t 或 T | 切换日志中的时间戳 | +| shift + f 或 F | 切换全屏日志 | +| esc | 退出全屏日志 | {% endif %} diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md new file mode 100644 index 0000000000000..2efb71d008c38 --- /dev/null +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -0,0 +1,43 @@ +--- +title: Deleting files in a repository +intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +redirect_from: + - /articles/deleting-files + - /github/managing-files-in-a-repository/deleting-files + - /github/managing-files-in-a-repository/deleting-a-file-or-directory +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +--- + +### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion + +You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. + +If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 + +If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. 更多信息请参阅“[从仓库中删除敏感数据](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)”。 + +### Deleting a file + +1. 浏览到要删除仓库中的文件。 +2. 在文件顶部，单击 +{% octicon "trashcan" aria-label="The trashcan icon" %}. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Deleting a directory + +1. Browse to the directory in your repository that you want to delete. +1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) +1. Review the files you will delete. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/index.md b/translations/zh-CN/content/github/managing-files-in-a-repository/index.md index a12db9770613a..8b1fc6e29bad4 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/index.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 79bb57c2365b6..bc3906d61e153 100644 --- a/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ versions: - 如果将 500 MB 文件推送到 {% data variables.large_files.product_name_short %}，您将使用 500 MB 的分配存储空间，而不使用带宽。 如果进行 1 个字节的更改后再次推送文件，您会使用另外 500 MB 的存储空间，但仍然不使用带宽，所以两次推送的总使用量是 1 GB 存储空间和零带宽。 - 如果下载一个使用 LFS 跟踪的 500 MB 文件，您将使用仓库所有者分配的 500 MB 带宽。 如果协作者推送文件更改并将新版本拉取到本地仓库，您将使用另外 500 MB 的带宽，所以两次下载的总使用量是 1 GB 带宽。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 如果 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在仓库的源代码存档中，则下载这些存档将会计入仓库的带宽使用量。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md index 179b2e6497b84..c282269bb6a95 100644 --- a/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ versions: ### 延伸阅读 -- "[与 {% 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" %} +- "[与 {% 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@3.0" or currentVersion == "github-ae@latest" %} - "[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index b40cf7f660eb1..71d7d4c5cd8db 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/zh-CN/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: 关于 Dependabot 安全更新 +intro: '{% data variables.product.prodname_dependabot %} 可通过提出安全更新拉取请求为您修复有漏洞依赖项。' +shortTitle: 关于 Dependabot 安全更新 redirect_from: - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates versions: @@ -10,26 +10,30 @@ versions: ### 关于 {% 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 %} 使您更容易修复仓库中的有漏洞依赖项。 如果启用此功能，当 {% data variables.product.prodname_dependabot %} 针对仓库依赖关系图中的有漏洞依赖项发出警报时，{% data variables.product.prodname_dependabot %} 将自动尝试修复它。 更多信息请参阅“[关于漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[配置 {% 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 %} 将检查是否可以在不破坏仓库依赖关系图的情况下将有漏洞依赖项升级到已修复版本。 然后，{% data variables.product.prodname_dependabot %} 提出拉取请求以将依赖项更新到包含补丁的最低版本，并将拉取请求链接到 {% data variables.product.prodname_dependabot %} 警报，或者在警报中报告错误。 更多信息请参阅“[排查 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”。 {% note %} **注** -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. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)”。 +{% data variables.product.prodname_dependabot_security_updates %} 功能适用于已启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %} 的仓库。 您将在完整的依赖关系图中看到针对已发现的每个有漏洞依赖项的 {% data variables.product.prodname_dependabot %} 警报。 但是，安全更新仅针对清单或锁定文件中指定的依赖项而触发。 {% data variables.product.prodname_dependabot %} 无法更新未明确定义的间接或过渡依赖项。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)”。 {% endnote %} -### About pull requests for security updates +### 关于安全更新的拉取请求 -Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. 这包括漏洞的相关信息，如发行说明、变更日志条目和提交详细信息。 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. +每个拉取请求都包含快速、安全地查看提议的修复程序并将其合并到项目中所需的全部内容。 这包括漏洞的相关信息，如发行说明、变更日志条目和提交详细信息。 无法访问仓库的 {% data variables.product.prodname_dependabot_alerts %} 的任何人都看不到拉取请求所解决的漏洞详细信息。 -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)." +当您合并包含安全更新的拉取请求时，仓库的相应 {% data variables.product.prodname_dependabot %} 警报将被标记为已解决。 有关 {% data variables.product.prodname_dependabot %} 拉取请求的更多信息，请参阅“[管理依赖项更新的拉取请求](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)”。 {% data reusables.dependabot.automated-tests-note %} ### 关于兼容性分数 -{% 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. +{% data variables.product.prodname_dependabot_security_updates %} 可能包括兼容性分数，以便您了解更新漏洞是否可能导致对项目的重大更改。 这些分数是根据已生成相同安全更新的其他公共仓库中的 CI 测试计算的。 更新的兼容性分数是在依赖项的特定版本之间进行更新时，CI 运行被视为通过的百分比。 + +### 关于 {% data variables.product.prodname_dependabot %} 安全更新通知 + +您可以在 {% data variables.product.company_short %} 上过滤通知以显示 {% data variables.product.prodname_dependabot %} 安全更新。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)”。 \ No newline at end of file diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md index 9eea6bed5f877..a72ee076844c3 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -1,23 +1,23 @@ --- -title: About managing vulnerable dependencies -intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +title: 关于管理有漏洞依赖项 +intro: '{% data variables.product.prodname_dotcom %} 有助于避免使用包含已知漏洞的第三方软件。' versions: free-pro-team: '*' --- -{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. +{% data variables.product.prodname_dotcom %} 提供以下工具来删除和避免有漏洞依赖项。 -#### Dependency graph +#### 依赖关系图 依赖项图是存储在仓库中的清单和锁定文件的摘要。 It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 #### Dependency review -By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 #### {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. 该警报包括指向项目中受影响的文件的链接，以及有关修复的版本的信息。 {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 #### {% data variables.product.prodname_dependabot_security_updates %} -When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 #### {% data variables.product.prodname_dependabot_version_updates %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index b5d8bbad1f900..58e1647582ddf 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -13,7 +13,7 @@ versions: ### 关于配置 {% 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)." +您可以为任何使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的仓库启用 {% data variables.product.prodname_dependabot_security_updates %}。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 您可以对个别仓库或所有由您的用户帐户或组织拥有的仓库禁用 {% data variables.product.prodname_dependabot_security_updates %}。 更多信息请参阅下面的“[管理仓库的 {% data variables.product.prodname_dependabot_security_updates %}](#managing-dependabot-security-updates-for-your-repositories)”。 @@ -42,16 +42,18 @@ You can enable {% data variables.product.prodname_dependabot_security_updates %} ### 管理仓库的 {% data variables.product.prodname_dependabot_security_updates %} -您可以对单个仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}。 +您可以对单个仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}（见下文）。 您也可以为用户帐户或组织拥有的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}。 更多信息请参阅“[管理用户帐户的安全和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)”或“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”。 {% data variables.product.prodname_dependabot_security_updates %} 需要特定的仓库设置。 更多信息请参阅“[支持的仓库](#supported-repositories)”。 +#### 对单个仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %} + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. 在警报列表的上方，使用下拉菜单并选择或取消选择 **{% data variables.product.prodname_dependabot %} security updates（Dependabot 安全更新）**。 ![包含启用 {% data variables.product.prodname_dependabot_security_updates %} 的选项的下拉菜单](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. 在“Configure security and analysis features（配置安全和分析功能）”下，在“{% data variables.product.prodname_dependabot %} security updates（安全更新）”的右侧，单击 **Enable（启用）**或 **Disable（禁用）**。 !["配置安全和分析功能"部分中启用 {% data variables.product.prodname_dependabot_security_updates %} 的按钮](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### 延伸阅读 diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index f85505ecafb33..b1097a9342ebd 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -40,7 +40,7 @@ You can configure notification settings for yourself or your organization from t {% note %} -**Note:** You can filter your {% data variables.product.company_short %} inbox notifications to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)." +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." {% endnote %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index 36367d556c9b5..ea03f091673eb 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/zh-CN/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: 排查 Dependabot 错误 +intro: '有时，{% data variables.product.prodname_dependabot %} 无法提出拉取请求以更新依赖项。 您可以查看错误并取消阻止 {% data variables.product.prodname_dependabot %}。' shortTitle: 排查错误 redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors @@ -10,81 +10,83 @@ versions: {% data reusables.dependabot.beta-note %} -### About {% data variables.product.prodname_dependabot %} errors +### 关于 {% 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. +如果有任何因素阻止 {% data variables.product.prodname_dependabot %} 提出拉取请求，则报告为错误。 -### Investigating errors with {% data variables.product.prodname_dependabot_security_updates %} +### 使用 {% 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. +当 {% data variables.product.prodname_dependabot %} 被阻止创建拉取请求以修复 {% data variables.product.prodname_dependabot %} 警报时，它会在警报上发布错误消息。 {% data variables.product.prodname_dependabot_alerts %} 视图显示尚未解决的所有警报列表。 要访问警报视图，请单击仓库 **Security（安全）**选项卡上的 **{% data variables.product.prodname_dependabot_alerts %}**。 如果旨在修复有漏洞依赖项的拉取请求已生成，则警报将包括指向该拉取请求的链接。 -![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png) +![{% data variables.product.prodname_dependabot_alerts %} 视图显示拉取请求链接](/assets/images/help/dependabot/dependabot-alert-pr-link.png) -There are three reasons why an alert may have no pull request link: +有三个原因可能导致警报中没有拉取请求链接： -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 %} 未对仓库启用。 +1. 警报针对未在锁文件中显式定义的间接或过渡依赖项。 +1. 某个错误阻止了 {% data variables.product.prodname_dependabot %} 创建拉取请求。 -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. +如果某个错误阻止了 {% data variables.product.prodname_dependabot %} 创建拉取请求，您可以通过单击警报来显示错误详情。 -![{% 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) +![{% data variables.product.prodname_dependabot %} 警报显示阻止创建拉取请求的错误](/assets/images/help/dependabot/dependabot-security-update-error.png) -### Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} +### 使用 {% 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. +当 {% data variables.product.prodname_dependabot %} 被阻止创建拉取请求以更新生态系统中的依赖项时，它将在清单文件中发布错误图标。 由 {% data variables.product.prodname_dependabot %} 管理的清单文件列于 {% data variables.product.prodname_dependabot %} 选项卡上。 要访问此选项卡，请在仓库的 **Insights（洞察）**选项卡上单击 **Dependency graph（依赖项图）**，然后单击 **{% data variables.product.prodname_dependabot %}** 选项卡。 -![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png) +![{% data variables.product.prodname_dependabot %} 视图显示错误](/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. +要查看任何清单文件的日志文件，请单击 **Last checked TIME ago（上次检查时间以前）**链接。 当您显示一个带有错误符号的清单(例如上面截图中的 Maven）的日志文件时，也会显示任何错误。 -![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) +![{% data variables.product.prodname_dependabot %} 版本更新错误和日志 ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png) -### Understanding {% data variables.product.prodname_dependabot %} errors +### 了解 {% 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. +安全更新拉取请求用于将有漏洞依赖项升级到包含漏洞修复的最低版本。 而版本更新拉取请求用于将依赖项升级到包清单文件和 {% data variables.product.prodname_dependabot %} 配置文件允许的最新版本。 因此，某些错误特定于一种类型的更新。 -#### {% data variables.product.prodname_dependabot %} cannot update DEPENDENCY to a non-vulnerable version +#### {% data variables.product.prodname_dependabot %} 无法将依赖项更新到无漏洞版本 -**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. +**仅限安全更新。** {% data variables.product.prodname_dependabot %} 无法创建拉取请求以将有漏洞依赖项更新到安全版本，而又不破坏此仓库依赖项图中的其他依赖项。 -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. +每个具有依赖项的应用程序都有一个依赖关系图，即应用程序直接或间接依赖的每个包版本的定向非循环图。 每次更新依赖项时，必须解决此图，否则将无法构建应用程序。 当生态系统具有深刻而复杂的依赖关系图（例如 npm 和 RubyGems）时，如果不升级整个生态系统，往往难以升级单个依赖项。 -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. 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 +避免这个问题的最佳办法是跟上最新发布的版本，例如启用版本更新。 这增加了通过不破坏依赖关系图的简单升级解决一个依赖项中的漏洞的可能性。 更多信息请参阅“[启用和禁用版本更新](/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 %} 无法更新到所需的版本，因为已经为最新版本打开了拉取请求 -**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. +**仅限安全更新。** {% data variables.product.prodname_dependabot %} 不会创建拉取请求以将有漏洞依赖项更新到安全版本，因为已存在更新此依赖项的打开拉取请求。 如果在一个依赖项中检测到漏洞，但已经存在将该依赖项更新到最新版本的打开拉取请求时，您将会看到此错误。 -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)." +有两个选项：您可以查看打开的拉取请求，确认更改安全后合并它，或者关闭该拉取请求并触发新的安全更新拉取请求。 更多信息请参阅“[手动触发 {% data variables.product.prodname_dependabot %} 拉取请求](#triggering-a-dependabot-pull-request-manually)”。 -#### {% data variables.product.prodname_dependabot %} timed out during its update +#### {% data variables.product.prodname_dependabot %} 在更新过程中超时 -{% 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 %} 评估所需更新和准备拉取请求所用的时间超过了允许的最大时间。 此错误一般只出现在具有许多清单文件的大型仓库，例如具有数百个 *package.json* 文件的 npm 或 yarn 单仓库项目。 对 Composer 生态系统的更新也需要较长的时间来评估，可能会超时。 -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. +此错误难以解决。 如果版本更新超时，您可以使用 `allow` 参数来指定更新最重要的依赖项，或者使用 `ignore` 参数从更新中排除某些依赖项。 更新配置可能使 {% data variables.product.prodname_dependabot %} 能够在规定时间内检查版本更新并生成请求。 -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. 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 +如果安全更新超时，您可以通过保持依赖项更新（例如，启用版本更新）来减少更新需要。 更多信息请参阅“[启用和禁用版本更新](/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 %} 无法再打开拉取请求 -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. +{% data variables.product.prodname_dependabot %} 生成的打开拉取请求数量存在限制。 如果达到此限制，将无法打开新的拉取请求，并报告此错误。 解决此错误的最佳方法是审查并合并一些打开的拉取请求。 -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. 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)。” +安全性和版本更新拉取请求有各自的限制，因此打开版本更新拉取请求不会阻止安全更新拉取请求的创建。 安全更新拉取请求的限制是 10。 默认情况下，版本更新的限制是 5，但您可以使用配置文件中的 `open-pull-requests-limit` 参数来更改它。 更多信息请参阅“[依赖项更新的配置选项](/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)." +解决此错误的最佳方法是合并或关闭一些现有拉取请求，然后手动触发新的拉取请求。 更多信息请参阅“[手动触发 {% data variables.product.prodname_dependabot %} 拉取请求](#triggering-a-dependabot-pull-request-manually)”。 -#### {% data variables.product.prodname_dependabot %} can't resolve your dependency files +#### {% data variables.product.prodname_dependabot %} 无法解析依赖项文件 -**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". +如果 {% data variables.product.prodname_dependabot %} 尝试检查是否需要更新仓库中的依赖项引用，但无法访问一个或多个依赖项文件，则操作将失败，并返回错误消息“{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files（无法解析语言依赖项文件）”。 API 错误类型为 `git_dependencies_not_reachable`。 -{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 更多信息请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)”。 +要让 {% data variables.product.prodname_dependabot %} 成功更新依赖项引用，请确保所有引用依赖项都托管在可访问的位置。 -### Triggering a {% data variables.product.prodname_dependabot %} pull request manually +**仅限版本更新。**{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 更多信息请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)”。 -If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. +### 手动触发 {% data variables.product.prodname_dependabot %} 拉取请求 -- **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**. +如果取消阻止了 {% data variables.product.prodname_dependabot %}，您可以手动触发新的尝试来创建拉取请求。 + +- **安全更新**—显示 {% data variables.product.prodname_dependabot %} 警报，查看您修复的错误，然后单击 **Create {% data v{% data variables.product.prodname_dependabot %} security update（创建安全更新）**。 +- **版本更新**—在仓库的 **Insights（洞察）**选项卡上单击 **Dependency graph（依赖项图）**，然后单击 **Dependabot** 选项卡。 单击 **Last checked *TIME* ago**（上次检查时间以前），查看 {% data variables.product.prodname_dependabot %} 在上次检查版本更新时生成的日志文件。 单击 **Check for Updates（检查更新）**。 diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 339016b8eab47..040df046516a0 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -11,7 +11,7 @@ versions: 仓库的 {% data variables.product.prodname_dependabot %} 警报选项卡列出所有打开和关闭的 {% data variables.product.prodname_dependabot_alerts %} 以及对应的 {% data variables.product.prodname_dependabot_security_updates %}。 您可以使用下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 -您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 {% data reusables.repositories.dependency-review %} diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index be621ae2689d2..0940204d91e91 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### 通知和订阅 您可以选择通过订阅接收有关 {% data variables.product.product_name %} 上特定活动的持续更新。 通知是您收到的已订阅特定活动的更新。 @@ -50,7 +54,7 @@ versions: ### 自定义通知和订阅 -您可以选择通过 [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} 上和 {% data variables.product.prodname_mobile %} 应用程序{% endif %}中的通知收件箱、电子邮件或这些选项的某些组合来查看通知。 +您可以选择通过 [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 上和 {% data variables.product.prodname_mobile %} 应用程序{% endif %}中的通知收件箱、电子邮件或这些选项的某些组合来查看通知。 要自定义您希望接收的更新类型以及将这些更新发送至何处，请配置通知设置。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。 @@ -58,7 +62,7 @@ versions: 要自定义如何接收特定拉取请求或议题的更新，可以在议题或拉取请求中配置首选项。 更多信息请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)”。 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} 您可以在 {% data variables.product.prodname_mobile %} 应用中启用推送通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)”。 {% endif %} @@ -89,7 +93,7 @@ versions: ### 自定义通知收件箱 -要在 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} 或 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱中关注一组通知，您可以创建自定义过滤器。 例如，您可以为您参与的开源项目创建自定义过滤器，只查看您被提及的仓库的通知。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。 有关如何自定义分类工作流程的更多示例，请参阅“[自定义对通知分类的工作流程](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。 +要在 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 或 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱中关注一组通知，您可以创建自定义过滤器。 例如，您可以为您参与的开源项目创建自定义过滤器，只查看您被提及的仓库的通知。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。 有关如何自定义分类工作流程的更多示例，请参阅“[自定义对通知分类的工作流程](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。 ### 通知保留策略 diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index d5cd29ac6ca9e..62d95cd92327e 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### 通知递送选项 您可以在以下位置的 {% data variables.product.product_name %} 上接收活动的通知。 - - {% data variables.product.product_name %} Web 界面{% if currentversion == "free-pro-team@latest" %}中的通知收件箱 + - {% data variables.product.product_name %} Web 界面{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %}中的通知收件箱 - {% data variables.product.prodname_mobile %} 上的通知收件箱，它与 {% data variables.product.product_name %} 上的收件箱同步{% endif %} - - 使用经验证电子邮件地址的电子邮件客户端，也可以与 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} 及 {% data variables.product.prodname_mobile %}{% endif %} 上的通知收件箱同步 + - 使用经验证电子邮件地址的电子邮件客户端，也可以与 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 及 {% data variables.product.prodname_mobile %}{% endif %} 上的通知收件箱同步 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} 更多信息请参阅“[选择通知设置](#choosing-your-notification-settings)”。 {% endif %} @@ -35,7 +39,7 @@ versions: #### 通知收件箱的优点 -{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} 和 {% data variables.product.prodname_mobile %}{% endif %} 上的通知收件箱包含专为您的 {% data variables.product.product_name %} 通知流程设计的分类选项，包括： +{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 和 {% data variables.product.prodname_mobile %}{% endif %} 上的通知收件箱包含专为您的 {% data variables.product.product_name %} 通知流程设计的分类选项，包括： - 一次对多种通知进行分类。 - 将已完成的通知标记为**完成**并从收件箱中删除它们。 要查看标记为**完成**的所有通知，请使用 `is:done` 查询。 - 保存通知以供以后查看。 保存的通知将在收件箱中标记并无限期保留。 要查看所有已保存的通知，请使用 `is:saved` 查询。 @@ -45,7 +49,7 @@ versions: - 创建自定义过滤器，以便按需要关注不同的通知。 - 按仓库或日期对收件箱中的通知进行分组，以快速概览通知，减少上下文切换 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 此外， {% data variables.product.prodname_mobile %} 上的通知收件箱允许您在黑暗模式下对通知进行分类，并接收直接提及的推送通知。 更多信息请参阅“[为移动版 GitHub 启用推送通知](#enabling-push-notifications-with-github-for-mobile)”或“[移动版 GitHub](/github/getting-started-with-github/github-for-mobile)”。 {% endif %} @@ -77,7 +81,7 @@ versions: #### 参与对话 每当您在对话中发表评论或有人 @提及您的用户名时，您都在_参与_对话。 默认情况下，当您参与对话时，会自动订阅该对话。 您可以通过单击议题或拉取请求上的 **Unsubscribe（取消订阅）**或通过通知收件箱中的 **Unsubscribe（取消订阅）**选项，手动取消订阅已参与的对话。 -对于您关注或参与的对话，您可以选择是通过电子邮件还是 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} 和 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱接收通知。 +对于您关注或参与的对话，您可以选择是通过电子邮件还是 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" % 和 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱接收通知。 ![参与和关注通知选项](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -85,7 +89,7 @@ versions: - 如果您不希望将通知发送到您的电子邮件地址，请取消选中 **email（电子邮件）**以便参与和查看通知。 - 如果您希望在参与对话时通过电子邮件接收通知，则可以选中“Participating（参与）”下的 **email（电子邮件）**。 -如果您未对 Web{% if currentVersion == "free-pro-team@latest" %} 和移动{% endif %} 启用关注或参与通知，则您的通知收件箱不会收到任何更新。 +如果您未对 Web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 和移动{% endif %} 启用关注或参与通知，则您的通知收件箱不会收到任何更新。 ### 自定义电子邮件通知 @@ -197,13 +201,15 @@ versions: {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### 使用 {% data variables.product.prodname_mobile %} 启用推送通知 安装 {% data variables.product.prodname_mobile %} 时，您将自动选择 web 通知。 然后，您可以针对应用程序中的直接提及启用推送通知。 目前，您只能针对 {% data variables.product.prodname_mobile %} 上仓库的推送接收通知。 +{% data reusables.mobile.push-notifications-on-ghes %} + #### 使用 {% data variables.product.prodname_ios %} 启用推送通知 1. 在“Home（主页）”上，点击您的个人资料照片。 @@ -211,9 +217,11 @@ versions: 3. 要更新通知设置，请点击 **Push notifications（推送通知）**。 4. 要针对直接提及开启推送通知，请使用 **Direct Mentions（直接提及）**切换按钮。 +{% if currentVersion == "free-pro-team@latest" %} #### 使用 {% data variables.product.prodname_android %} 启用推送通知 1. 在“Home（主页）”上，点击您的个人资料照片。 2. 要查看设置，请点击 {% octicon "gear" aria-label="The Gear icon" %}。 ![Android 版 GitHub 的设置图标](/assets/images/help/mobile/android-settings-icon.png) 3. 要针对直接提及开启推送通知，请使用 **Direct mentions（直接提及）**切换按钮。 {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 2f8865ec21462..8ed442f6d7a31 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: 从收件箱管理通知 -intro: '使用收件箱快速分类并在电子邮件{% if currentVersion == "free-pro-team@latest" %} 与手机{% endif %} 之间同步您的通知。' +intro: '使用收件箱快速分类并在电子邮件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 与手机{% endif %} 之间同步您的通知。' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### 关于收件箱 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)”。 {% endif %} @@ -86,31 +90,16 @@ versions: ### 支持的自定义过滤器查询 -您可以使用三种类型的过滤器： +以下是您可以使用的过滤器类型： - 使用 `repo:` 按仓库过滤 - 使用 `is:` 按讨论类型过滤 - - 使用 `reason:` 按通知原因过滤 - -要添加 `repo:` 过滤器，您必须在查询中包含仓库的所有者。 例如，`repo:atom/atom` 表示 Atom 组织拥有的 Atom 仓库。 + - 使用 `reason:` 按通知原因过滤{% if currentVersion == "free-pro-team@latest" %} + - 使用 `author:` 按通知作者过滤 + - 使用 `org:` 按组织过滤{% endif %} -#### 支持的 `reason:` 查询 +#### 支持的 `repo:` 查询 -要根据收到更新的原因过滤通知，您可以使用 `reason:` 查询。 例如，要查看当您（或您所属团队）被请求审查拉取请求时的通知，请使用 `reason:review-requested`。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)”。 - -| 查询 | 描述 | -| ------------------------- | --------------------------------------------------------------- | -| `reason:assign` | 分配给您的议题或拉取请求有更新时。 | -| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 | -| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 | -| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 | -| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 | -| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 | -| `reason:mention` | 您被直接@提及。 | -| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% if currentVersion != "github-ae@latest" %} -| `reason:security-alert` | 为仓库发出安全警报时。{% endif %} -| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 | -| `reason:team-mention` | 您所在的团队被@提及时。 | -| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 | +要添加 `repo:` 过滤器，您必须在查询中包含仓库的所有者：`repo:owner/repository`。 所有者是拥有触发通知的 {% data variables.product.prodname_dotcom %} 资产的组织或用户。 例如，`repo:octo-org/octo-repo` 将会显示在 octo-org 组织内的 octo-repo 仓库中触发的通知。 #### 支持的 `is:` 查询 @@ -138,3 +127,59 @@ versions: - `is:done` - `is:unread` - `is:read` + +#### 支持的 `reason:` 查询 + +要根据收到更新的原因过滤通知，您可以使用 `reason:` 查询。 例如，要查看当您（或您所属团队）被请求审查拉取请求时的通知，请使用 `reason:review-requested`。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)”。 + +| 查询 | 描述 | +| ------------------------- | --------------------------------------------------------------- | +| `reason:assign` | 分配给您的议题或拉取请求有更新时。 | +| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 | +| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 | +| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 | +| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 | +| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 | +| `reason:mention` | 您被直接@提及。 | +| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% if currentVersion != "github-ae@latest" %} +| `reason:security-alert` | 为仓库发出安全警报时。{% endif %} +| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 | +| `reason:team-mention` | 您所在的团队被@提及时。 | +| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 | + +{% if currentVersion == "free-pro-team@latest" %} +#### 支持的 `author:` 查询 + +要按用户过滤通知，您可以使用 `author:` 查询。 作者是指与通知相关的线程（议题、拉取请求、Gist、讨论等）的原作者。 例如，要查看与 Octocat 用户创建的线程相关的通知，请使用 `author:octocat`。 + +#### 支持的 `org:` 查询 + +要按组织过滤通知，您可以使用 `org` 查询。 您需要在查询中指定的组织是与您在 {% data variables.product.prodname_dotcom %} 上收到的通知相关之仓库所属的组织。 如果您属于多个组织，并且想要查看特定组织的通知，则此查询很有用。 + +例如，要查看来自 octo-org 组织的通知，请使用 `org:octo-org`。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} 自定义过滤器 + +{% if currentVersion == "free-pro-team@latest" %} +如果您使用 +{% data variables.product.prodname_dependabot %} 来保持依赖项更新，您可以使用并保存这些自定义过滤器： +- `is:repository_vulnerability_alert`，显示 {% data variables.product.prodname_dependabot_alerts %} 的通知。 +- `reason:security_alert`，显示 {% data variables.product.prodname_dependabot_alerts %} 的通知和安全更新拉取请求。 +- `author:app/dependabot`，显示 {% data variables.product.prodname_dependabot %} 生成的通知。 这包括 {% data variables.product.prodname_dependabot_alerts %}、安全更新拉取请求和版本更新拉取请求。 +有关 + +{% data variables.product.prodname_dependabot %} 的更多信息，请参阅“[关于管理有漏洞依赖项](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)”。 +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +如果您使用 +{% data variables.product.prodname_dependabot %} 以保持依赖项更新，您可以使用并保存 `is:repository_vulnerability_alert` 自定义过滤器以显示 {% data variables.product.prodname_dependabot_alerts %} 的通知。 +有关 + +{% data variables.product.prodname_dependabot %} 的更多信息，请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +{% endif %} + +{% endif %} diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 13c2ce2702e76..fb197ce9e8eea 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -64,4 +64,4 @@ versions: - 取消关注仓库 - 忽略某仓库的所有通知 - 自定义接收通知的事件类型（议题、拉取请求、发布或讨论，如有启用） -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md b/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md index d854252bf9c27..4f667f49e17a9 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md @@ -14,9 +14,11 @@ versions: 您可以在仓库中使用议题收集用户反馈，报告软件漏洞，并且组织要完成的任务。 议题不只是一个报告软件漏洞的地方。 +{% if currentVersion == "free-pro-team@latest" %} 其他对话更适合讨论。 {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/zh-CN/content/github/managing-your-work-on-github/changing-project-board-visibility.md index b7f94258bcbf9..3da3c7efb55cc 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: 更改项目板可见性 -intro: '作为组织所有者或项目板管理员，您可以将项目板设为公共或私有。' +intro: '作为组织所有者或项目板管理员，您可以将项目板设为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}或私有。' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**提示：**将项目板设为公共时，默认情况下组织成员会获得读取权限。 您可以为特定组织成员提供写入或管理权限，方法是为他们所在的团队提供项目板访问权限或将他们作为协作者添加到项目板。 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。 +**提示：**将项目板设为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}时，组织成员默认获得读取权限。 您可以为特定组织成员提供写入或管理权限，方法是为他们所在的团队提供项目板访问权限或将他们作为协作者添加到项目板。 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。 {% endtip %} -1. 导航到您要设为公共或私有的项目板。 +1. 导航到要设为 + +{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}或私有的项目板。 {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. 在“Visibility（可见性）”下，选择 **Public（公共）**或 **Private（私有）**。 然后单击 **Save（保存）**。 ![公共和私有单选按钮](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/zh-CN/content/github/managing-your-work-on-github/copying-a-project-board.md index a63f394f665ae..8c2837b476ee6 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ versions: 5. （可选）在“Project board name（项目板名称）”下，键入所复制项目板的名称。 ![用于键入所复制项目板名称的字段](/assets/images/help/projects/copied-project-board-name.png) 6. （可选）在“Description（说明）”下，键入其他人将看到的有关所复制项目板的说明。 ![用于键入所复制项目板说明的字段](/assets/images/help/projects/copied-project-board-description.png) 7. （可选）在“Automation settings（自动化设置）”下，选择是否要复制已配置的自动工作流程。 默认情况下会启用此选项。 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards/)”。 ![为所复制的项目板选择自动化设置](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. 如果复制组织拥有的项目板，请在“Visibility（可见性）”下，选择是否要将所复制的项目板设为私密或公开。 ![为所复制的项目板选择可见性设置](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. 单击 **Copy project（复制项目）**。 ![确认复制按钮](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/zh-CN/content/github/managing-your-work-on-github/creating-a-project-board.md index 3aeca6a1431f6..3abf9990e7f1d 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ versions: {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ versions: {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/zh-CN/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 67b33d7808016..00a9269caecd3 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: 您可以过滤仓库的拉取请求列表以查找： - 尚未[审查](/articles/about-pull-request-reviews)的拉取请求 -- [需要审查](/articles/about-required-reviews-for-pull-requests)后才能合并的拉取请求 +- [需要审查](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)后才能合并的拉取请求 - 审查者已批准的拉取请求 - 审查者要求更改的拉取请求 - 您已审查的拉取请求 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md index 4c283386f0558..6a20db70ee167 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md @@ -1,6 +1,6 @@ --- title: 将拉取请求链接到议题 -intro: '您可以将拉取请求链接到议题，以显示修复正在进行中，并在合并拉取请求时自动关闭该议题。' +intro: '您可以将拉取请求链接到议题，以显示修复正在进行中，并在拉取请求被合并时自动关闭该议题。' redirect_from: - /articles/closing-issues-via-commit-message/ - /articles/closing-issues-via-commit-messages/ @@ -14,17 +14,17 @@ versions: {% note %} -**Note:** The special keywords in a pull request description are interpreted when the pull request targets the repository's *default* branch. However, if the PR's base is *any other branch*, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.** +**注：**当拉取请求指向仓库的*默认*分支时，将解析拉取请求说明中的特殊关键字。 但是，如果拉取请求的基础是*任何其他分支*，则将忽略这些关键字，不创建任何链接，并且合并拉取请求对议题没有影响。 **如果要使用关键字将拉取请求链接到议题，则拉取请求必须在默认分支上。** {% endnote %} ### 关于链接的议题和拉取请求 -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. +您可以{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}手动或{% endif %}在拉取请求说明中使用支持的关键字将议题链接到拉取请求。 -当您将拉取请求链接到拉取请求指向的议题，如果有人正在操作该议题，协作者可以看到。 {% if currentVersion ver_lt "enterprise-server@2.21" %}If the pull request and the issue are in different repositories, {% data variables.product.product_name %} will display the link after the pull request is merged, if the person who merges the pull request also has permission to close the issue.{% endif %} +当您将拉取请求链接到拉取请求指向的议题，如果有人正在操作该议题，协作者可以看到。 {% if currentVersion ver_lt "enterprise-server@2.21" %}如果拉取请求和议题在不同的仓库中，{% data variables.product.product_name %} 将在拉取请求合并后并且合并拉取请求的人有权限关闭议题时才会显示链接。{% endif %} -将链接的拉取请求合并到仓库的默认分支时，其链接的议题将自动关闭。 For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +将链接的拉取请求合并到仓库的默认分支时，其链接的议题将自动关闭。 有关默认分支的更多信息，请参阅“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### 手动将拉取请求链接到议题 @@ -42,7 +42,7 @@ You can link an issue to a pull request {% if currentVersion == "free-pro-team@l ### 使用关键词将拉取请求链接到议题 -You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message (please note that the pull request must be on the default branch). +您可以在拉取请求说明或提交消息中使用支持的关键字将拉取请求链接到议题（请注意，拉取请求必须在默认分支上）。 * close * closes @@ -62,9 +62,9 @@ You can link a pull request to an issue by using a supported keyword in the pull | 不同仓库中的议题 | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | 多个议题 | 对每个议题使用完整语法 | `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. 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}只有手动链接的拉取请求才可以手动取消链接。 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。{% endif %} -您也可以在提交消息中使用关闭关键词。 The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request. +您也可以在提交消息中使用关闭关键词。 议题将在提交合并到默认分支时关闭，但包含提交的拉取请求不会列为链接的拉取请求。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md b/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md index 1769e32fec739..b4e94b77bca55 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md @@ -11,7 +11,7 @@ versions: {% note %} -**Note:** In order to link a repository to your organization or user owned project board the repository needs to have issues enabled. For information on how to see if issues are disabled for a repository, see "[Disabling issues](/github/managing-your-work-on-github/disabling-issues) ." +**注：**要将仓库链接到组织或用户拥有的项目板，仓库需要启用议题。 有关如何查看仓库是否禁用了议题，请参阅“[禁用议题](/github/managing-your-work-on-github/disabling-issues)”。 {% endnote %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md index c4c2ab9de1261..04f569d705b42 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md @@ -1,6 +1,6 @@ --- -title: Managing labels -intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +title: 管理标签 +intro: '您可以通过创建、编辑、应用和删除标签对议题和拉取请求进行分类。' redirect_from: - /articles/managing-Labels - /articles/labeling-issues-and-pull-requests @@ -25,25 +25,25 @@ versions: ### 关于标签 -您可以创建标签对议题和拉取请求分类，以管理您在 {% data variables.product.product_name %} 上的工作。 You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue or pull request within that repository. +您可以创建标签对议题和拉取请求分类，以管理您在 {% data variables.product.product_name %} 上的工作。 您可以在创建标签的仓库中应用标签。 添加标签后，便可在该仓库的任何议题或拉取请求中使用该标签。 -对仓库具有读取权限的任何人都能查看和搜索仓库的标签。 要创建、编辑、应用或删除标签，必须对仓库具有写入权限。 +对仓库具有读取权限的任何人都能查看和搜索仓库的标签。 对仓库具有鉴定权限的任何人都可以应用/忽略现有标签。 要创建、编辑、应用或删除标签，必须对仓库具有写入权限。 -### About default labels +### 关于默认标签 -{% data variables.product.product_name %} 在每个新仓库中提供默认标签。 You can use these default labels to help create a standard workflow in a repository. +{% data variables.product.product_name %} 在每个新仓库中提供默认标签。 您可以使用这些默认标签帮助在仓库中创建标准工作流程。 -| 标签 | 描述 | -| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| 标签 | 描述 | +| ------------------ | -------------------------------------------------------------------------------------------------------------- | +| `bug` | 表示意外问题或意外行为{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} | `文档` | 表示文档需要改进或补充{% endif %} -| `duplicate` | 表示类似的议题或拉取请求 | -| `enhancement` | 表示新功能申请 | -| `good first issue` | 表示适用首次贡献者的议题 | -| `help wanted` | 表示维护员需要议题或拉取请求方面的帮助 | -| `invalid` | 表示议题或拉取请求不再相关 | -| `question` | 表示议题或拉取请求需要更多信息 | -| `wontfix` | 表示不会继续处理议题或拉取请求 | +| `duplicate` | 表示类似的议题或拉取请求 | +| `enhancement` | 表示新功能申请 | +| `good first issue` | 表示适用首次贡献者的议题 | +| `help wanted` | 表示维护员需要议题或拉取请求方面的帮助 | +| `invalid` | 表示议题或拉取请求不再相关 | +| `question` | 表示议题或拉取请求需要更多信息 | +| `wontfix` | 表示不会继续处理议题或拉取请求 | 创建仓库时，每个新仓库中均包含默认标签，但您稍后可以编辑或删除标签。 @@ -83,7 +83,7 @@ versions: {% data reusables.project-management.save-label %} ### 删除标签 -Deleting a label will remove the label from issues and pull requests. +删除标签将从议题和拉取请求中删除标签。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -91,7 +91,6 @@ Deleting a label will remove the label from issues and pull requests. {% data reusables.project-management.delete-label %} ### 延伸阅读 -- "[关于标签](/articles/about-labels)" -- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- "[Encouraging helpful contributions to your project with labels](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} +- "[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- "[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[通过标签鼓励对项目做出有益的贡献](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md index c9f3017c71c00..17f22c2c6fe6b 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -1,5 +1,5 @@ --- -title: Managing your work with issues and pull requests +title: 使用议题和拉取请求管理工作 intro: '您可以创建议题来跟踪想法、增强、任务或漏洞，以管理您在 {% data variables.product.product_name %} 上的工作。' mapTopic: true redirect_from: diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md b/translations/zh-CN/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md index 88ddc7203f1d6..dc719ad168995 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md @@ -1,6 +1,6 @@ --- title: 跟踪项目板上的进度 -intro: You can see the overall progress of your project in a progress bar. +intro: 您可以在进度条中看到项目的总体进度。 redirect_from: - /articles/tracking-progress-on-your-project-board versions: @@ -11,7 +11,7 @@ versions: {% data reusables.project-management.project-progress-locations %} -1. Navigate to the project board where you want to enable or disable project progress tracking. +1. 导航到您想在其中启用或禁用项目进度跟踪的项目板。 {% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Select or deselect **Track project progress**. +4. 选择或取消选择 **Track project progress（跟踪项目进度）**。 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index e96b2c3fef6d7..a4d183fd2891a 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,9 +11,9 @@ versions: 要将打开的议题转让给另一个仓库，必须对议题所在的仓库以及议题要转让到的仓库都有写入权限。 更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。 -You can only transfer issues between repositories owned by the same user or organization account.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} +只能在同一用户或组织帐户拥有的仓库之间转让议题。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}不能将议题从私有仓库转让到公共仓库。{% endif %} -转让议题时，评论和受理人将保留。 The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 +转让议题时，评论和受理人将保留。 不会保留议题的标签和里程碑。 此议题将留在任何用户拥有或组织范围的项目板上，并从任何仓库项目板中删除。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 议题中提及的人员或团队将收到通知，告知他们该议题已转让给新仓库。 原来的 URL 会重定向到新议题的 URL。 在新仓库中没有读取权限的人员将看到一个横幅，告知他们该议题已转让给他们无法访问的新仓库。 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 761d7a9b19580..bcf1eaed441fd 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,7 +25,7 @@ versions: - 过滤涉及但不一定[**@提及**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)的特定人员的议题和拉取请求：`state:open type:issue involves:octocat` - 按受理人过滤议题和拉取请求：`state:open type:issue assignee:octocat` - 按标签过滤议题和拉取请求：`state:open type:issue label:"bug"` -- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` +- 使用 `-` before the term: `state:open type:issue -author:octocat` 过滤搜索词。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} 对于议题，您还可以使用搜索来： @@ -36,12 +36,12 @@ versions: 对于拉取请求，您还可以使用搜索来： - 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft` - 过滤尚未[审查](/articles/about-pull-request-reviews)的拉取请求：`state:open type:pr review:none` -- 过滤[需要审查](/articles/about-required-reviews-for-pull-requests)然后才能合并的拉取请求：`state:open type:pr review:required` +- 过滤[需要审查](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)然后才能合并的拉取请求：`state:open type:pr review:required` - 过滤审查者已批准的拉取请求：`state:open type:pr review:approved` - 过滤审查者要求更改的拉取请求：`state:open type:pr review:changes_requested` - 按[审查者](/articles/about-pull-request-reviews/)过滤拉取请求：`state:open type:pr reviewed-by:octocat` - 按[请求审查](/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" %} +- 按申请审查的团队过滤拉取请求：`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" %} - 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md index 2ef06e144458a..d294c1f2b0e71 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md @@ -16,4 +16,4 @@ versions: ### 延伸阅读 -- {% 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" %}”[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}”[列出关注的仓库](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-notifications.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-notifications.md index adcebcb5d24b4..36223df49b77b 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-notifications.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-notifications.md @@ -33,7 +33,7 @@ versions: #### 查看通知 -您查看的仓库或团队讨论如有更新，{% data variables.product.product_name %} 会发送*查看*通知。 {% data reusables.notifications.auto-watch %}For more information, see "[Watching and unwatching repositories](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)." +您查看的仓库或团队讨论如有更新，{% data variables.product.product_name %} 会发送*查看*通知。 {% data reusables.notifications.auto-watch %}更多信息请参阅“[关注和取消关注仓库](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)”。 您在以下情况下会收到通知： - 新开了一个议题。 - 打开的议题新增了评论。 diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md index e7d5e7ba30372..f76a8887746e3 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md @@ -7,7 +7,7 @@ versions: 有关*参与*和*关注*通知之间差异的更多信息，请参阅“[关于通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)”。 -为帐户启用 web 通知后，您可以单击通知页面中的项目，并且会重定向到通知所参考的对话。 For more information on enabling web notifications, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)." 有关启用 web 通知的更多信息，请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。 +为帐户启用 web 通知后，您可以单击通知页面中的项目，并且会重定向到通知所参考的对话。 有关启用 web 通知的更多信息，请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。 有关启用 web 通知的更多信息，请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。 {% data reusables.notifications.shared_state %} diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md index 27297b722e5e0..769928b5b94ae 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md @@ -12,7 +12,7 @@ versions: 3. 选择要订阅的议题或拉取请求。 4. 在右侧边栏中，单击 **Subscribe（订阅）**或 **Unsubscribe（取消订阅）**。 ![对话订阅按钮](/assets/images/help/notifications/subscribe_button_with_gear.png) 5. 要自定义您的通知，请单击 {% octicon "gear" aria-label="The gear icon" %}。 ![对话订阅旁边的齿轮按钮](/assets/images/help/notifications/subscribe_button_with_gear_chosen.png) -6. 选择您要为此对话接收的通知类型，然后单击 **Save（保存）**。 ![Conversation Subscribe options list](/assets/images/help/notifications/subscribe_options.png) You can see a list of all the issues and pull requests you're subscribed to. 更多信息请参阅“[列出您订阅的议题和拉取请求](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to)”。 +6. 选择您要为此对话接收的通知类型，然后单击 **Save（保存）**。 ![Conversation Subscribe options list](/assets/images/help/notifications/subscribe_options.png) 您可以看到订阅的所有议题和拉取请求的列表。 更多信息请参阅“[列出您订阅的议题和拉取请求](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to)”。 ### 订阅团队讨论 diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md index 7d30fc693cbb5..5cffbaad7c1b0 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md @@ -33,7 +33,7 @@ versions: {% note %} -**注：**您也可以选择忽略仓库。 如果忽略仓库，将不会收到任何通知。 我们不建议忽略仓库，因为这样您被@提及时将不会收到通知。 {% if currentVersion == "free-pro-team@latest" %}If you experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %} +**注：**您也可以选择忽略仓库。 如果忽略仓库，将不会收到任何通知。 我们不建议忽略仓库，因为这样您被@提及时将不会收到通知。 {% if currentVersion == "free-pro-team@latest" %}如果您发现滥用问题并且想忽略某个仓库，请联系 {% data variables.contact.contact_support %} 获取帮助。 {% data reusables.policies.abuse %}{% endif %} {% endnote %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md index a3f6133f889e3..cd5b08da6d428 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -1,6 +1,6 @@ --- title: 关于在 GitHub 上搜索 -intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' +intro: '我们的集成搜索涵盖了 {% data variables.product.product_name %} 上的许多仓库、用户和代码行。' redirect_from: - /articles/using-the-command-bar/ - /articles/github-search-basics/ @@ -26,8 +26,8 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - {% data reusables.search.required_login %}{% endif %} - {% data variables.product.prodname_pages %} 网站在 {% data variables.product.product_name %} 上不可搜索。 但如果源代码内容存在于仓库的默认分支中，您可以使用代码搜索来搜索。 更多信息请参阅“[搜索代码](/articles/searching-code)”。 有关 {% data variables.product.prodname_pages %} 的更多信息，请参阅“[什么是 GitHub Pages？ ](/articles/what-is-github-pages/)” -- Currently our search doesn't support exact matching. -- Whenever you are searching in code files, only the first two results in each file will be returned. +- 目前我们的搜索不支持精确匹配。 +- 每当您在代码文件中搜索时，将仅返回每个文件中的前两个结果。 {% endnote %} @@ -37,15 +37,15 @@ versions: ### {% data variables.product.prodname_dotcom %} 上的搜索类型 -You can search for the following information across all repositories you can access on {% data variables.product.product_location %}. +您可以在 {% data variables.product.product_location %} 上可以访问的所有仓库中搜索以下信息。 - [仓库](/articles/searching-for-repositories) - [主题](/articles/searching-topics) -- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} -- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} +- [议题和拉取请求](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [讨论](/github/searching-for-information-on-github/searching-discussions){% endif %} - [代码](/articles/searching-code) - [提交](/articles/searching-commits) -- [Users](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} +- [用户](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} - [包](/github/searching-for-information-on-github/searching-for-packages){% endif %} - [Wikis](/articles/searching-wikis) @@ -65,9 +65,9 @@ You can search for the following information across all repositories you can acc 只能从 {% data variables.product.prodname_enterprise %} 搜索这两个环境。 要按环境限制搜索范围，可以使用 {% data variables.search.advanced_url %} 上的过滤选项，或者使用 `environment:` 搜索前缀。 若只搜索 {% data variables.product.prodname_enterprise %} 上的内容，请使用搜索语法 `environment:local`。 若只搜索 {% data variables.product.prodname_dotcom_the_website %} 上的内容，则使用 `environment:github`。 {% data variables.product.prodname_enterprise %} 网站管理员可对连接的 {% data variables.product.prodname_ghe_cloud %} 组织中的所有公共仓库、私有仓库或特定私有仓库启用 {% data variables.product.prodname_unified_search %}。 -If your site administrator enables +如果站点管理员 -{% 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. {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_enterprise %} 管理员和组织所有者无法搜索您的帐户所拥有的私有仓库。 要搜索相关的私有仓库，必须在 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_enterprise %} 上对您的个人帐户启用私有仓库搜索。 更多信息请参阅“[在 {% data variables.product.prodname_enterprise %} 帐户中启用私有 {% data variables.product.prodname_dotcom_the_website %} 仓库搜索](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)”。 +在私有仓库中启用 {% data variables.product.prodname_unified_search %}，您只能在连接的 {% data variables.product.prodname_dotcom_the_website %} 组织中搜索管理员启用了 {% data variables.product.prodname_unified_search %} 并且您具有访问权限的私有仓库。 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_enterprise %} 管理员和组织所有者无法搜索您的帐户所拥有的私有仓库。 要搜索相关的私有仓库，必须在 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_enterprise %} 上对您的个人帐户启用私有仓库搜索。 更多信息请参阅“[在 {% data variables.product.prodname_enterprise %} 帐户中启用私有 {% data variables.product.prodname_dotcom_the_website %} 仓库搜索](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)”。 {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md index 5428cd4ccca96..e8fb341de7a30 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/articles/about-searching-on-github)." +{% data reusables.search.you-can-search-globally %} 更多信息请参阅“[关于在 GitHub 上搜索](/articles/about-searching-on-github)”。 您只能使用这些代码搜索限定符搜索代码。 搜索代码时，专用于仓库、用户或提交的搜索限定符将不起作用。 @@ -24,11 +24,11 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - {% data reusables.search.required_login %}{% endif %} - [复刻](/articles/about-forks)中的代码仅当复刻的星号超过父级仓库时可搜索。 星号少于父仓库的复刻**不**为代码搜索编索引。 要在搜索结果中包括星号比其父项多的复刻，您需要将 `fork:true` 或 `fork:only` 添加到查询。 更多信息请参阅“[在复刻中搜索](/articles/searching-in-forks)”。 -- Only the _default branch_ is indexed for code search.{% if currentVersion == "free-pro-team@latest" %} +- 只有_默认分支_被索引用于代码搜索。{% if currentVersion == "free-pro-team@latest" %} - 只有小于 384 KB 的文件可搜索。{% else %}* 只有小于 5 MB 的文件可搜索。 - 只有每个文件的前 500 KB 可搜索。{% endif %} -- Only repositories with fewer than 500,000 files are searchable.{% if currentVersion == "free-pro-team@latest" %} -- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- 只能搜索少于 500,000 个文件的仓库。{% if currentVersion == "free-pro-team@latest" %} +- 只能搜索去年有活动或已在搜索结果中返回的仓库。{% endif %} - 除了 [`filename`](#search-by-filename) 搜索以外，搜索源代码时必须始终包括至少一个搜索词。 例如，搜索 [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) 无效，而搜索 [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) 有效。 - 搜索结果最多可显示同一文件的两个分段，但文件内可能有更多结果。 - 您无法使用以下通配符作为搜索查询的一部分：. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]. 搜索只会忽略这些符号。 @@ -103,5 +103,5 @@ versions: ### 延伸阅读 - “[排序搜索结果](/articles/sorting-search-results/)” -- "[Searching in forks](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %} +- "[在复刻中搜索](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %} - "[在 {% data variables.product.prodname_dotcom %} 上导航代码](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-commits.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-commits.md index 444f6c68a07a2..3d0784e345c84 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-commits.md @@ -48,10 +48,10 @@ versions: {% data reusables.search.date_gt_lt %} -| 限定符 | 示例 | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) 匹配 2016-01-01 之前创作的提交。 | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) 匹配 2016-01-01 之后提交的提交。 | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) 匹配 2016-01-01 之前创作的提交。 | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) 匹配 2016-01-01 之后的提交。 | ### 过滤合并提交 @@ -96,11 +96,11 @@ versions: | org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) 匹配 @github 拥有的仓库中含有 "test" 字样的提交消息。 | | repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) 匹配 @defunkt 的 "gibberish" 仓库中含有 "language" 字样的提交消息。 | -### Filter by repository visibility +### 按仓库可见性过滤 -The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility). +`is` 限定符匹配具有指定可见性的仓库中的提交。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 -| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. +| 限定符 | 示例 | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) 匹配对公共仓库的提交。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) 匹配对内部仓库的提交。 | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) 匹配对私有仓库的提交。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md index 190b2a11c00f9..73e5d63599cf1 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md @@ -1,109 +1,109 @@ --- -title: Searching discussions -intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +title: 搜索讨论 +intro: 您可以在 {% data variables.product.product_name %} 上搜索讨论，并使用搜索限定符缩小结果范围。 versions: free-pro-team: '*' --- {% data reusables.discussions.beta %} -### About searching for discussions +### 关于搜索讨论 -You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 +您可以在所有 {% data variables.product.product_name %} 中全局搜索讨论，也可以在特定组织或仓库内搜索讨论。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 {% data reusables.search.syntax_tips %} ### 按标题、正文或评论搜索 -With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. +使用 `in` 限定符可将讨论搜索范围限制在标题、正文或注释中。 您还可以组合限定符来搜索标题、正文或注释的组合。 省略 `in` 限定符时，{% data variables.product.product_name %} 将搜索标题、正文和注释。 -| 限定符 | 示例 | -|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | -| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | -| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | +| 限定符 | 示例 | +|:------------- |:----------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) 匹配标题中含有 "welcome" 的讨论。 | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) 匹配标题或正文中含有 "onboard" 的讨论。 | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) 匹配讨论注释中含有 "thanks" 的讨论。 | ### 在用户或组织的仓库内搜索 -To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. +要在特定用户或组织拥有的所有仓库中搜索讨论，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索讨论，您可以使用 `repo` 限定符。 -| 限定符 | 示例 | -|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | -| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | -| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) 匹配 @octocat 拥有的仓库中含有单词 "feedback" 的讨论。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的讨论。 | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) 匹配 @nodejs' Node.js 运行时项目中在 2021 年 1 月之前创建的讨论。 | -### Filter by repository visibility +### 按仓库可见性过滤 -You can filter by the visibility of the repository containing the discussions using the `is` qualifier. 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 +您可以使用 `is` 限定符，按包含讨论的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 -| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. +| 限定符 | 示例 | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) 匹配公共仓库中的讨论。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) 匹配内部仓库中的讨论。 | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) 匹配您有权访问的私有仓库含有单词 "tiramisu" 的讨论。 ### 按作者搜索 -The `author` qualifier finds discussions created by a certain user. +`author` 限定符查找由特定用户创建的讨论。 -| 限定符 | 示例 | -|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | -| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的含有单词 "cool" 的讨论。 | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的正文中含有单词 "bootstrap" 的讨论。 | ### 按评论者搜索 -The `commenter` qualifier finds discussions that contain a comment from a certain user. +`commenter` 限定符查找含有特定用户评论的讨论。 -| 限定符 | 示例 | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) 匹配 GitHub 拥有的仓库中含有单词 "github" 并且由 @becca 评论的讨论。 | -### Search by a user that's involved in a discussion +### 按涉及讨论的用户搜索 -You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. +您可以使用 `involves` 限定符查找涉及特定用户的讨论。 该限定符返回由特定用户创建、提及该用户或包含该用户评论的讨论。 `involves` 限定符是单一用户 `author`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。 -| 限定符 | 示例 | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | -| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | +| 限定符 | 示例 | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** 匹配涉及 @becca 或 @octocat 的讨论。 | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) 匹配涉及 @becca 且正文中不包含单词 "beta" 的讨论。 | ### 按评论数量搜索 -You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用 `comments` 限定符以及大于、小于和范围限定符以按评论数量搜索。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 -| 限定符 | 示例 | -|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | +| 限定符 | 示例 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) 匹配超过 100 条评论的讨论。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) 匹配具有 500 到 1,000 条评论的讨论。 | ### 按交互数量搜索 -You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用 `interactions` 限定符以及大于、小于和范围限定符按交互数量过滤讨论。 交互数量是对讨论的反应和评论数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 -| 限定符 | 示例 | -|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2,000 个交互的讨论。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的讨论。 | ### 按反应数量搜索 -You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用 `reactions` 限定符以及大于、小于和范围限定符按反应数量过滤讨论。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 -| 限定符 | 示例 | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | +| 限定符 | 示例 | +|:------------------------- |:---------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) 匹配超过 500 个反应的讨论。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1,000 个反应的讨论。 | -### Search by when a discussion was created or last updated +### 按讨论创建或上次更新时间搜索 -You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. +您可以基于创建时间或上次更新时间过滤讨论。 对于讨论创建，您可以使用 `created` 限定符；要了解讨论上次更新的时间，请使用 `updated` 限定符。 -Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +两个限定符都使用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| 限定符 | 示例 | -|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | -| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | +| 限定符 | 示例 | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) 匹配 2020 年 11 月 15 日之后创建的讨论。 | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) 匹配 2020 年 12 月之后更新的正文中含有单词 "weird" 的讨论。 | ### 延伸阅读 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-packages.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-packages.md index f62c34ef82077..73df4e117ddcf 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-packages.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-packages.md @@ -16,8 +16,8 @@ versions: 您可以在所有 {% data variables.product.product_name %} 中全局搜索包，也可以在特定组织内搜索包。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/articles/about-searching-on-github)”。 {% if enterpriseServerVersions contains currentVersion %} -You can only search for packages on -{% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled. +您只能搜索 +{% data variables.product.product_name %} 上的包，而不是 {% data variables.product.prodname_dotcom_the_website %} 上的包，即使启用了 {% data variables.product.prodname_github_connect %}。 {% endif %} {% data reusables.search.syntax_tips %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-repositories.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-repositories.md index ad58a1c41b9fd..5573406b66b64 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-repositories.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-for-repositories.md @@ -20,22 +20,22 @@ versions: 通过 `in` 限定符，您可以将搜索限制为仓库名称、仓库说明、自述文件内容或这些的任意组合。 如果省略此限定符，则只搜索仓库名称和说明。 -| 限定符 | 示例 | -| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. | -| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. | -| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. | -| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) 匹配特定仓库名称。 | +| 限定符 | 示例 | +| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) 匹配仓库名称中含有 "jquery" 的仓库。 | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) 匹配仓库名称或说明中含有 "jquery" 的仓库。 | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "jquery" 的仓库。 | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) 匹配特定仓库名称。 | ### 基于仓库的内容搜索 -You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. 更多信息请参阅“[关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)”。 +您可以使用 `in:readme` 限定符，通过搜索仓库自述文件中的内容来查找仓库。 更多信息请参阅“[关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)”。 除了使用 `in:readme` 以外，无法通过搜索仓库内的特定内容来查找仓库。 要搜索仓库内的特定文件或内容，您可以使用查找器或代码特定的搜索限定符。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上查找文件](/articles/finding-files-on-github)”和“[搜索代码](/articles/searching-code)”。 -| 限定符 | 示例 | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. | +| 限定符 | 示例 | +| ----------- | --------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "octocat" 的仓库。 | ### 在用户或组织的仓库内搜索 @@ -48,7 +48,7 @@ You can find a repository by searching for content in the repository's README fi ### 按仓库大小搜索 -The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +`size` 限定符使用大于、小于和范围限定符查找匹配特定大小（以千字节为单位）的仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 | 限定符 | 示例 | | ------------------------- | -------------------------------------------------------------------------------------------------------------- | @@ -59,7 +59,7 @@ The `size` qualifier finds repositories that match a certain size (in kilobytes) ### 按关注者数量搜索 -You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用 `followers` 限定符以及大于、小于和范围限定符，基于关注仓库的用户数量过滤仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 | 限定符 | 示例 | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -68,7 +68,7 @@ You can filter repositories based on the number of users who follow the reposito ### 按复刻数量搜索 -The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +`forks` 限定符使用大于、小于和范围限定符指定仓库应具有的复刻数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 | 限定符 | 示例 | | ------------------------- | -------------------------------------------------------------------------------------------------------------- | @@ -79,7 +79,7 @@ The `forks` qualifier specifies the number of forks a repository should have, us ### 按星号数量搜索 -You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用大于、小于和范围限定符，基于仓库的星标数量来搜索仓库。 更多信息请参阅“[使用星标保存仓库](/github/getting-started-with-github/saving-repositories-with-stars)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 | 限定符 | 示例 | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -103,7 +103,7 @@ You can search repositories based on the number of stars the repositories have, ### 按语言搜索 -You can search repositories based on the language of the code in the repositories. +您可以根据仓库中代码的语言搜索仓库。 | 限定符 | 示例 | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | @@ -111,7 +111,7 @@ You can search repositories based on the language of the code in the repositorie ### 按主题搜索 -You can find all of the repositories that are classified with a particular topic. 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。 +您可以找到按特定主题分类的所有仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。 | 限定符 | 示例 | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | @@ -119,7 +119,7 @@ You can find all of the repositories that are classified with a particular topic ### 按主题数量搜索 -You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +您可以使用 `topics` 限定符以及大于、小于和范围限定符，根据应用于仓库的主题数量来搜索仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 | 限定符 | 示例 | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------- | @@ -130,7 +130,7 @@ You can search repositories by the number of topics that have been applied to th ### 按许可搜索 -You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. 更多信息请参阅“[许可仓库](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)”。 +您可以根据仓库中许可的类型搜索仓库。 您必须使用许可关键字，按特定许可或许可系列来过滤仓库。 更多信息请参阅“[许可仓库](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)”。 | 限定符 | 示例 | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -138,33 +138,33 @@ You can search repositories by the type of license in the repositories. You must {% endif %} -### Search by repository visibility +### 按仓库可见性搜索 -You can filter your search based on the visibility of the repositories. 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 +您可以根据仓库的可见性过滤搜索。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 -| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." +| 限定符 | 示例 | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) 匹配 {% data variables.product.company_short %} 拥有的公共仓库。{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) 匹配您可以访问并且包含单词 "test" 的内部仓库。 | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) 匹配您可以访问并且包含单词 "pages" 的私有仓库。 {% if currentVersion == "free-pro-team@latest" %} ### 基于仓库是否为镜像搜索 -You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 +您可以根据仓库是否为镜像以及托管于其他位置托管来搜索仓库。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 -| 限定符 | 示例 | -| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." | -| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." | +| 限定符 | 示例 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) 匹配是镜像且包含 "GNOME" 字样的仓库。 | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) 匹配并非镜像且包含 "GNOME" 字样的仓库。 | {% endif %} ### 基于仓库是否已存档搜索 -You can search repositories based on whether or not the repositories are archived. For more information, see "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)." +您可以基于仓库是否已存档来搜索仓库。 更多信息请参阅“[关于存档仓库](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)”。 -| 限定符 | 示例 | -| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." | -| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." | +| 限定符 | 示例 | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) 匹配已存档且包含 "GNOME" 字样的仓库。 | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) 匹配未存档且包含 "GNOME" 字样的仓库。 | {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 3fde5351e108c..05df7ddbea021 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -14,7 +14,7 @@ versions: {% tip %} -**Tips:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +**提示：**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - 本文章包含在 {% data variables.product.prodname_dotcom %}.com 网站上的示例搜索，但您可以在 {% data variables.product.product_location %} 上使用相同的搜索过滤器。{% endif %} - 有关可以添加到任何搜索限定符以进一步改善结果的搜索语法列表，请参阅“[了解搜索语法](/articles/understanding-the-search-syntax)”。 - 对多个字词的搜索词使用引号。 例如，如果要搜索具有标签 "In progress" 的议题，可搜索 `label:"in progress"`。 搜索不区分大小写。 @@ -64,63 +64,63 @@ versions: | `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) 匹配含有 "performance" 字样的开放议题。 | | `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) 匹配含有 "android" 字样的已关闭议题和拉取请求。 | -### Filter by repository visibility +### 按仓库可见性过滤 -You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 +您可以使用 `is` 限定符，按包含议题和拉取请求的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 -| Qualifier | Example | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. +| 限定符 | 示例 | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) 匹配公共仓库中的议题和拉取请求。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) 匹配内部仓库中的议题和拉取请求。{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) 匹配您可以访问的仓库中包含单词 "cupcake" 的议题和拉取请求。 ### 按作者搜索 `author` 限定符查找由特定用户或集成帐户创建的议题和拉取请求。 -| 限定符 | 示例 | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. | -| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. | -| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) 匹配含有 "cool" 字样、由 @gjtorikian 创建的议题和拉取请求。 | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) 匹配由 @mdo 撰写、正文中含有 "bootstrap" 字样的议题。 | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) 匹配由名为 "robot" 的集成帐户创建的议题。 | ### 按受理人搜索 -`assignee` 限定符查找分配给特定用户的议题和拉取请求。 You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). +`assignee` 限定符查找分配给特定用户的议题和拉取请求。 您无法搜索具有 _any_ 受理人的议题和拉取请求，但可以搜索[没有受理人的议题和拉取请求](#search-by-missing-metadata)。 -| 限定符 | 示例 | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. | +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) 匹配分配给 @vmg 的 libgit2 项目 libgit2 中的议题和拉取请求。 | ### 按提及搜索 `mentions` 限定符查找提及特定用户的议题。 更多信息请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”。 -| 限定符 | 示例 | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) 匹配含有 "resque" 字样、提及 @defunkt 的议题。 | ### 按团队提及搜索 对于您所属的组织和团队，您可以使用 `team` 限定符查找提及该组织内特定团队的议题或拉取请求。 将这些示例名称替换为您的组织和团队的名称以执行搜索。 -| 限定符 | 示例 | -| ------------------------- | ----------------------------------------------------------------------------------------------------- | -| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. | -| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** 匹配提及 `@jekyll/owners` 团队的议题。 | +| | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。 | ### 按评论者搜索 `commenter` 限定符查找含有来自特定用户评论的议题。 -| 限定符 | 示例 | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. | +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) 匹配位于 GitHub 拥有的仓库中、含有 "github" 字样且由 @defunkt 评论的议题。 | ### 按议题或拉取请求中涉及的用户搜索 您可以使用 `involves` 限定符查找以某种方式涉及特定用户的议题。 `involves` 限定符是单一用户 `author`、`assignee`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。 换句话说，此限定符查找由特定用户创建、分配给该用户、提及该用户或由该用户评论的议题和拉取请求。 -| 限定符 | 示例 | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. | -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** 匹配涉及 @defunkt 或 @jlord 的议题。 | +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) 匹配涉及 @mdo 且正文中未包含 "bootstrap" 字样的议题。 | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} ### 搜索链接的议题和拉取请求 @@ -227,7 +227,7 @@ You can filter by the visibility of the repository containing the issues and pul ### 搜索草稿拉取请求 您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。 -| Qualifier | Example | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) 匹配可供审查的拉取请求。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) 匹配拉取请求草稿。{% endif %} +| 限定符 | 示例 | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) 匹配拉取请求草稿。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) 匹配可供审查的拉取请求。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) 匹配拉取请求草稿。{% endif %} ### 按拉取请求审查状态和审查者搜索 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md index b7bf79e14b494..94dc56e4d5000 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ versions: `is:featured` 搜索限定符会将搜索结果范围缩小为 {% data variables.product.product_name %} 上具有最多仓库的主题。 这些主题还会在 https://github.com/topics/ 上提供。 -`is:curated` 搜索限定符可将搜索结果范围缩小到社区成员已向其添加额外信息的主题。 For more information, see the [explore repository](https://github.com/github/explore). +`is:curated` 搜索限定符可将搜索结果范围缩小到社区成员已向其添加额外信息的主题。 更多信息请参阅[探索仓库](https://github.com/github/explore)。 您可以使用日期参数和 `created:` 根据创建时间过滤主题，也可以使用 `repositories:n` 根据与此主题关联的仓库数量过滤主题。 这两个限定符都可以使用[大于和小于范围限定符](/articles/understanding-the-search-syntax)。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index f2a41cafb48ab..cd33442a3bd2a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -10,7 +10,7 @@ versions: {% data reusables.github-actions.actions-billing %} -{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +{% data reusables.github-actions.actions-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。 分钟数每月都会重置，而存储使用量不重置。 @@ -53,7 +53,7 @@ versions: 在月末，{% data variables.product.prodname_dotcom %} 会计算您使用的超过帐户自带限额的分钟数和存储空间费用。 例如，如果您的组织使用 {% data variables.product.prodname_team %} 并允许无限制支出，则使用 15,000 分钟可能会产生 56 美元的总存储空间和分钟数超额费用，具体取决于用于运行作业的操作系统。 - 5,000（3,000 Linux 加 2,000 Windows）分钟 = $56 ($24 + $32)。 - - 3,000 Linux minutes at $0.008 per minute = $24. + - 3,000 Linux 分钟（每分钟 $0.008）= $24。 - 2,000 Windows 分钟（每分钟 $0.016）= $32。 到月底，{% data variables.product.prodname_dotcom %} 会将您的数据传输舍入到最接近的 GB。 @@ -73,6 +73,6 @@ versions: {% data reusables.github-actions.actions-spending-limit-detailed %} -For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." +有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)”。 {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index e8c42362b589f..a20304d0fa9e9 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,7 +10,7 @@ versions: {% data reusables.package_registry.packages-billing %} -{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +{% data reusables.package_registry.packages-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。 {% data reusables.package_registry.container-registry-beta-billing-note %} @@ -54,6 +54,6 @@ versions: {% data reusables.package_registry.packages-spending-limit-detailed %} -For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." +有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_registry %} 的支出限制](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)”。 {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 84e699acfb85f..a97eca67f3cd1 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### 个人帐户折扣 -拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." +拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 更多信息请参阅“[申请学生开发包](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)”。 ### 学校和大学折扣 -经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)." 更多信息请参阅“[在课堂和研究中使用 {{ site.data.variables.product.prodname_dotcom }}](/articles/using-github-in-your-classroom-and-research)”。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。 +经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 更多信息请参阅“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)”。 更多信息请参阅“[在课堂和研究中使用 {{ site.data.variables.product.prodname_dotcom }}](/articles/using-github-in-your-classroom-and-research)”。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。 ### 非赢利组织和图书馆折扣 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index 6a0aecc2d924b..5c4dbf6918388 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -9,9 +9,9 @@ versions: {% data reusables.sponsors.org-sponsors-release-phase %} -### About sponsorship downgrades +### 关于赞助降级 -When you downgrade or cancel a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %} +降级或取消赞助后，更改将在下一个结算日期生效。 {% data reusables.sponsors.no-refunds %} ### 降级赞助 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 37c851edcd335..44f9992b45c6f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -12,11 +12,11 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} -{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_actions %} usage, 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 reusables.actions.actions-packages-set-spending-limit %} 有关 {% 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)”。 -As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且创建将当月存储使用量从 1.9GB 增加到 2.1GB 的工作流程工件，那么您使用的存储空间将比产品包含的 2GB 稍高。 +只要您将支出限额设定在 0 美元以上，您就要对当前结算周期内发生的任何超额费用负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且创建将当月存储使用量从 1.9GB 增加到 2.1GB 的工作流程工件，那么您使用的存储空间将比产品包含的 2GB 稍高。 -Because you have not enabled overages, your next attempt to create a workflow artifact will fail. 您不会收到该月 0.1GB 超额费用的帐单。 However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. +由于您尚未启用超额，因此下次尝试创建工作流程构件将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您启用了超额，您的第一个帐单将包括当前结算周期中 0.1GB 的现有超额以及您累积的任何其他超额。 ### 管理您用户帐户的 {% data variables.product.prodname_actions %} 支出限额 @@ -48,7 +48,7 @@ Because you have not enabled overages, your next attempt to create a workflow ar {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 1. 在“ -{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**. +{% data variables.product.prodname_actions %} and Packages monthly usage（GitHub 操作和包每月使用）”下，单击 **Cost management（成本管理）**。 ![成本管理选项卡](/assets/images/help/settings/cost-management-tab-enterprise.png) {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 4785921f31fd5..008164e5f0798 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -12,11 +12,11 @@ versions: {% data reusables.package_registry.packages-spending-limit-brief %} -{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_registry %} usage, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." +{% data reusables.actions.actions-packages-set-spending-limit %} 有关 {% data variables.product.prodname_registry %} 使用价格的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)”。 -As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且发布新版私有包，将当月存储使用量从 1.9GB 增加到 2.1GB，那么发布该版本使用的存储空间将比产品包含的 2GB 稍高。 +只要您将支出限额设定在 0 美元以上，您就要对当前结算周期内发生的任何超额费用负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且发布新版私有包，将当月存储使用量从 1.9GB 增加到 2.1GB，那么发布该版本使用的存储空间将比产品包含的 2GB 稍高。 -由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.1GB 超额费用的帐单。 However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. +由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您启用了超额，您的第一个帐单将包括当前结算周期中 0.1GB 的现有超额以及您累积的任何其他超额。 ### 管理您用户帐户的 {% data variables.product.prodname_registry %} 支出限额 @@ -48,7 +48,7 @@ As soon as you set a spending limit other than $0, you will be responsible for a {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 1. 在“ -{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**. +{% data variables.product.prodname_actions %} and Packages monthly usage（GitHub 操作和包每月使用）”下，单击 **Cost management（成本管理）**。 ![成本管理选项卡](/assets/images/help/settings/cost-management-tab-enterprise.png) {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index 6239dd115ea57..0c9d8b244b1fd 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -9,7 +9,7 @@ versions: {% data reusables.sponsors.org-sponsors-release-phase %} -### About sponsorship upgrades +### 关于赞助升级 当您升级赞助等级后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 734644bf11f7e..ecba5e7aac492 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -28,8 +28,8 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} {% data reusables.user_settings.subscriptions-tab %} -4. Next to " -{% data variables.product.prodname_free_user %}", click **Upgrade**. +4. 在“ +{% data variables.product.prodname_free_user %}”旁边，单击 **Upgrade（升级）**。 ![升级按钮](/assets/images/help/billing/settings_billing_user_upgrade.png) {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md index ceaad001941ef..593baec1c66ff 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -还可以查看单个工作流程运行的计费作业执行分钟数。 For more information, see "[Viewing job execution time](/actions/managing-workflow-runs/viewing-job-execution-time)." +还可以查看单个工作流程运行的计费作业执行分钟数。 更多信息请参阅“[查看作业执行时间](/actions/managing-workflow-runs/viewing-job-execution-time)”。 ### 查看用户帐户的 {% data variables.product.prodname_actions %} 使用情况 @@ -44,7 +44,7 @@ versions: {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 1. 在“ -{% data variables.product.prodname_actions %}", view details of usage of data transfer by each organization in your enterprise account. +{% data variables.product.prodname_actions %}”下，查看您的企业帐户中每个组织的数据传输使用详情。 ![分钟数使用详情](/assets/images/help/billing/actions-minutes-enterprise.png) {% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} {% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md index 2dc330daa84d7..f5287cd5e10f8 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md @@ -42,7 +42,7 @@ versions: {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 1. 在“ -{% data variables.product.prodname_registry %}", view details of usage of data transfer by each organization in your enterprise account. +{% data variables.product.prodname_registry %}”下，查看您的企业帐户中每个组织的数据传输使用详情。 ![数据传输使用详情](/assets/images/help/billing/packages-data-enterprise.png) {% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} {% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 20b6f904add17..83334a9327da6 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: 配置 SAML SSO 后，{% data variables.product.prodname_dotcom %} 组织的成员将继续登录到他们在 {% data variables.product.prodname_dotcom %} 上的用户帐户。 当成员访问组织内使用 SAML SSO 的资源时，{% data variables.product.prodname_dotcom %} 会将该成员重定向到 IdP 进行身份验证。 身份验证成功后，IdP 将该成员重定向回 {% data variables.product.prodname_dotcom %}，然后成员可以访问组织的资源。 -企业所有者还可以对企业帐户中的所有组织强制实施 SAML SSO。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 +组织所有者可以对单个组织强制实施 SAML SSO，企业所有者可以为企业帐户中的所有组织强制实施 SAML SSO。 更多信息请参阅“[为企业帐户中的组织启用 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ versions: 组织成员还必须具有活动的 SAML 会话才可授权 {% data variables.product.prodname_oauth_app %}。 您可以联系 {% data variables.contact.contact_support %} 选择退出此要求。 {% data variables.product.product_name %} 不建议退出此要求，因为它会使您的组织面临更高的帐户接管风险和潜在的数据丢失风险。 +{% data reusables.saml.saml-single-logout-not-supported %} + ### 支持的 SAML 服务 {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ versions: 在启用 SAML SSO 后，可通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 更多信息请参阅“[邀请用户加入组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/rest/reference/orgs#add-or-update-organization-membership)”。 -{% data reusables.organizations.team-synchronization %} - 要供应新用户而不使用组织所有者的邀请，您可以使用 URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`，将 _ORGANIZATION_ 替换为组织的名称。 例如，您可以配置 IdP，让能访问 IdP 的任何人都可单击 IdP 仪表板上的链接加入 {% data variables.product.prodname_dotcom %} 组织。 如果您的 IdP 支持 SCIM，当您在 IdP 上授予访问权限时，{% data variables.product.prodname_dotcom %} 可以自动邀请成员加入您的组织。 如果您删除成员对 SAML IdP 上 {% data variables.product.prodname_dotcom %} 组织的访问权限，该成员将自动从 {% data variables.product.prodname_dotcom %} 组织删除。 更多信息请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 65db75ec3363f..8b75cb24a8393 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ versions: - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)”。 +{% data reusables.scim.enterprise-account-scim %}更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md index ad670e9ecbc03..997358bd4f106 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities.md @@ -12,7 +12,7 @@ versions: SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 如果使用 SSH 认证中心 (CA) 为组织成员提供已签名的 SSH 证书，您可以将 CA 添加到企业帐户或组织，以便组织成员使用其证书访问组织资源。 更多信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”。 -在将 SSH CA 添加到组织或企业帐户后，您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库（并且只访问您组织的仓库）。 You can require that members use SSH certificates to access organization resources.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Enforcing security settings in your enterprise account](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)."{% endif %} +在将 SSH CA 添加到组织或企业帐户后，您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库（并且只访问您组织的仓库）。 您可以要求成员使用 SSH 证书访问组织资源。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[在企业帐户中实施安全设置](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)”。{% endif %} 例如，您可以构建内部系统，每天早上向开发者颁发新证书。 每个开发者可以使用其每日证书处理组织在 {% data variables.product.product_name %} 上的仓库。 在一天结束时，证书会自动到期，以保护仓库，避免证书以后被窃取。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md index 557ea854062ca..eb055c55afc09 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard.md @@ -29,7 +29,7 @@ versions: 在消息馈送的“All activity（所有活动）”部分，您可以查看来自组织中其他团队和仓库的更新。 -“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 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)." +“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关注和取消关注仓库](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}”和“[关注人员](/articles/following-people)”。 例如，当组织中有人执行以下操作时，组织消息馈送会显示更新： - 创建新分支。 @@ -37,8 +37,8 @@ versions: - 提交拉取请求审查评论。 - 对仓库复刻。 - 创建 wiki 页面。 - - Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - - Creates a public repository.{% endif %} + - 推送提交。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - 创建公共仓库。{% endif %} ### 更多信息 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md index 830698869e61c..656dc775a1130 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed.md @@ -18,5 +18,5 @@ versions: 1. {% data variables.product.signin_link %} 到 {% data variables.product.product_name %} 帐户。 2. 打开 {% data reusables.user_settings.personal_dashboard %}。 3. 单击页面左上角的帐户上下文切换器。 ![Enterprise 中的上下文切换器按钮](/assets/images/help/organizations/account_context_switcher.png) -4. Select an organization from the drop-down menu.{% if currentVersion == "free-pro-team@latest" %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} +4. 从下拉菜单中选择组织。{% if currentVersion == "free-pro-team@latest" %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md index 8b490717813a4..0a447009041dc 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -18,8 +18,8 @@ versions: {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} -9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or -{% data variables.product.prodname_dotcom %} email. +9. 在“Search by username, full name or email address（按用户名、全名或电子邮件地址搜索）”下，输入外部协作者的姓名、用户名或 +{% data variables.product.prodname_dotcom %} 电子邮件。 ![在搜索字段中输入了 Octocat 用户名的协作者部分](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md index 6ebdc58277bfd..8d5f5ce79436f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md @@ -26,7 +26,7 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} 1. 在“ -{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to add a {% data variables.product.prodname_github_app %} manager for. +{% data variables.product.prodname_github_app %}" 下，单击要为其添加 {% data variables.product.prodname_github_app %} 管理员的应用程序的头像。 ![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} 1. 在“App managers（应用程序管理员）”下，输入要指定为应用程序 GitHub App 管理员的人员，然后单击 **Grant（授权）**。 ![添加特定应用程序的 {% data variables.product.prodname_github_app %} 管理员](/assets/images/help/organizations/add-github-app-manager-for-app.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md index 776eec55c1f8f..f0ef5ab9fbede 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md @@ -1,6 +1,6 @@ --- title: 添加组织成员到团队 -intro: '拥有所有者或团队维护员权限的人员可以添加成员到团队。 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.' +intro: '拥有所有者或团队维护员权限的人员可以添加成员到团队。 具有所有者权限的人员也可{% if currentVersion == "free-pro-team@latest" %}邀请非成员加入{% else %}添加非成员到{% endif %}团队和组织。' redirect_from: - /articles/adding-organization-members-to-a-team-early-access-program/ - /articles/adding-organization-members-to-a-team diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md index bd567f3af76ee..5563cf9fd575d 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md +++ b/translations/zh-CN/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: '组织所有者可以向组织添加人员。' --- {% if currentVersion != "github-ae@latest" %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md index 5934c07381540..e1582b0bcc9b8 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Configuring the retention period for GitHub Actions artifacts and logs in your organization -intro: 'You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization.' +title: 为组织中的 GitHub Actions 构件和日志配置保留期 +intro: '您可以为组织中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。' versions: free-pro-team: '*' enterprise-server: '>=2.23' @@ -8,7 +8,7 @@ versions: {% data reusables.actions.about-artifact-log-retention %} -## Setting the retention period for an organization +## 设置组织的保留期 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md index 15dbc93e1ad71..9a5680ed56934 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md @@ -24,7 +24,7 @@ versions: 建议查看组织成员对仓库的访问权限，以确保其访问权限符合您的预期。 更多信息请参阅“[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)”。 -When you convert an organization member to an outside collaborator, their privileges as organization members are saved for three months so that you can restore their membership privileges if you{% if currentVersion == "free-pro-team@latest" %} invite them to rejoin{% else %} add them back to{% endif %} your organization within that time frame. 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 +将组织成员转换为外部协作者时，他们作为组织成员的权限将保存三个月，因此，如果您在该时间范围内{% if currentVersion == "free-pro-team@latest" %} 邀请他们重新加入{% else %} 将他们重新添加到{% endif %} 您的组织，您可以恢复其成员权限。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md index a53383df08472..55a11392c5200 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md @@ -1,5 +1,5 @@ --- -title: 将外部协作者转换为组织成员 +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.' redirect_from: - /articles/converting-an-outside-collaborator-to-an-organization-member @@ -9,14 +9,11 @@ versions: github-ae: '*' permissions: Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization. --- - {% if currentVersion == "free-pro-team@latest" %} -如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 -{% data reusables.organizations.org-invite-expiration %}{% endif %} +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 %} {% 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 %} +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 %} {% endif %} {% data reusables.profile.access_profile %} @@ -24,10 +21,9 @@ 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. 在要成为成员的外部协作者名称的右侧，使用 -{% octicon "gear" aria-label="The gear icon" %} 下拉菜单，然后单击 **Invite to organization（邀请加入组织）**。![邀请外部协作者加入组织](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +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) {% else %} -5. 在您希望其成为成员的外部协作者姓名右侧，单击 **Invite to organization（邀请加入组织）**。![邀请外部协作者加入组织](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) +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) {% endif %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role-send-invitation %} @@ -35,6 +31,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 -- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md index b80b592b88c11..3f4874ade30e5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md @@ -15,7 +15,7 @@ redirect_from: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.organizations %} {% data reusables.organizations.new-organization %} -4. 按照提示创建组织。 {% if currentVersion == "free-pro-team@latest" %}For more information about the plans available for your team, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."{% endif %} +4. 按照提示创建组织。 {% if currentVersion == "free-pro-team@latest" %}要详细了解可用于您的团队的计划，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index aabc49714d0cb..f359ca492dfd5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -1,6 +1,6 @@ --- title: 删除组织帐户 -intro: '删除组织时，所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% if currentVersion == "free-pro-team@latest" %}The organization name becomes available for use on a new user or organization account, and your billing will end.{% endif %}' +intro: '删除组织时，所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% if currentVersion == "free-pro-team@latest" %}组织名称可用于新用户或组织帐户，并且计费将结束。{% endif %}' redirect_from: - /articles/deleting-an-organization-account versions: @@ -20,7 +20,7 @@ versions: ### 1. 备份组织内容 -删除组织后，GitHub **无法恢复内容**。 Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. +删除组织后，GitHub **无法恢复内容**。 因此，在删除组织之前，请确保您拥有该帐户中所有仓库、wiki、议题和项目板的副本。 ### 2. 删除组织 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index 44b8e80bc27b1..02787718dbee2 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 单击 **Remove restrictions（删除限制）**。 ![删除限制按钮](/assets/images/help/settings/settings-third-party-remove-restrictions.png) -6. 审查有关禁用第三方应用程序限制的信息后，请单击 **Yes, remove application restrictions（是，删除应用程序限制）**。 ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) +6. 审查有关禁用第三方应用程序限制的信息后，请单击 **Yes, remove application restrictions（是，删除应用程序限制）**。 ![删除确认按钮](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md index 920b137541dda..08fd67deae275 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization.md @@ -34,13 +34,13 @@ versions: ### 管理组织的 {% data variables.product.prodname_actions %} 权限 -You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization. +您可以禁用组织的所有工作流程，或者设置策略来配置哪些操作可用于组织中。 {% data reusables.actions.actions-use-policy-settings %} {% note %} -**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, {% 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)."{% else %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**注：**如果您的组织由具有覆盖策略的企业管理，您可能无法管理这些设置。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)”。{% else %}“[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。{% endif %} {% endnote %} @@ -48,7 +48,7 @@ You can disable all workflows for an organization or set a policy that configure {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Under **Policies**, select an option. ![设置此组织的操作策略](/assets/images/help/organizations/actions-policy.png) +1. 在 **Policies（策略）**下，选择一个选项。 ![设置此组织的操作策略](/assets/images/help/organizations/actions-policy.png) 1. 单击 **Save（保存）**。 ### 允许特定操作运行 @@ -59,7 +59,7 @@ You can disable all workflows for an organization or set a policy that configure {% 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. ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png) +1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png) 1. 单击 **Save（保存）**。 {% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md index 15356ac63397c..c8923479cff86 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization.md @@ -13,7 +13,7 @@ versions: 您可以控制组织成员是否可以使用 {% data variables.product.prodname_pages %} 从组织中的仓库发布网站。 有关 {% data variables.product.prodname_pages %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)”。 -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +{% if enterpriseServerVersions 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 %}。 更多信息请参阅{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}“[为企业配置 {% data variables.product.prodname_pages %}](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)”和{% endif %}“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 ### 禁止发布 {% data variables.product.prodname_pages %} 站点 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md index 52d7297490b32..07c5185093647 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md index 15b6141e96797..04851636c6d7c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md @@ -1,7 +1,7 @@ --- title: 邀请用户参加您的组织 intro: '您可以使用任何人的 {% data variables.product.product_name %} 用户名或电子邮件地址邀请其成为组织的成员。' -permissions: Organization owners can invite users to join an organization. +permissions: 组织所有者可以邀请用户加入组织。 redirect_from: - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ - /articles/inviting-users-to-join-your-organization @@ -13,7 +13,7 @@ versions: **提示**： - 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-expiration %} -- If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." +- 如果您的组织要求成员使用双重身份验证，则您邀请的用户在接受邀请之前必须启用双重身份验证。 更多信息请参阅“[在组织中要求双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”和“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 {% endtip %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md index 658bca40601e0..c8142375f22c6 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md @@ -3,7 +3,7 @@ title: 保护组织安全 redirect_from: - /articles/preventing-unauthorized-access-to-organization-information/ - /articles/keeping-your-organization-secure -intro: '组织所有者有多项功能来帮助保护其项目和数据的安全。 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: '组织所有者有多项功能来帮助保护其项目和数据的安全。 如果您是组织的所有者，应定期检查组织的审核日志{% if currentVersion != "github-ae@latest" %}、成员 2FA 状态{% endif %} 和应用程序设置，以确保没有未授权或恶意的活动。' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md index 9b04682a56f7c..1b2558df03708 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md @@ -25,8 +25,8 @@ versions: {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} -9. Under "Search by username, full name or email address", type the collaborator's name, username, or -{% data variables.product.prodname_dotcom %} email. +9. 在“Search by username, full name or email address（按用户名、全名或电子邮件地址搜索）”下，输入协作者的姓名、用户名或 +{% data variables.product.prodname_dotcom %} 电子邮件。 ![在搜索字段中输入了 Octocat 用户名的协作者部分](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md index 11ae32412a4f4..6c38d4b4fa53a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md @@ -31,5 +31,5 @@ versions: ### 延伸阅读 -{% if currentVersion == "free-pro-team@latest" %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[限制与仓库的交互](/articles/limiting-interactions-with-your-repository)"{% endif %} - "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md index f63fb4c26d0f1..60e23264a26e7 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team.md @@ -18,7 +18,7 @@ versions: ### 路由算法 -Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. +代码审查分配根据两种可能的算法之一自动选择和分配审查者。 循环算法根据最近收到最少审查请求的人员选择审查者，侧重于在团队所有成员之间的轮替，而不管他们目前拥有多少未完成的审查。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md index 4bd9e0620a98c..96514ef7b9c77 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -1,25 +1,25 @@ --- -title: Managing discussion creation for repositories in your organization -intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. -permissions: Organization owners can manage discussion creation for repositories owned by the organization. +title: 管理您组织中仓库的讨论创建 +intro: 您可以选择成员在组织拥有的仓库中创建讨论所需的权限级别。 +permissions: 组织所有者可以管理组织拥有的仓库的讨论创建。 versions: free-pro-team: '*' --- {% data reusables.discussions.beta %} -### Allowing or disallowing users with read access to create discussions +### 允许或禁止具有读取权限的用户创建讨论 -By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. +默认情况下，如果仓库管理员或组织所有者为组织拥有的仓库启用了讨论，则具有读取权限的组织成员可以创建讨论。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} -5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) -6. 单击 **Save（保存）**。 !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png) +5. 在“Repository discussions（仓库讨论）”下，选择或取消选择 **Allow users with read access to create discussions（允许有读权限的用户创建讨论）**。 ![允许有读取权限的人创建讨论的复选框](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. 单击 **Save（保存）**。 ![讨论设置的"保存"按钮](/assets/images/help/discussions/click-save.png) ### 延伸阅读 -- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" -- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" +- "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[管理社区的讨论](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md index d982d34535f23..7a175aaab28b4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md @@ -1,6 +1,6 @@ --- title: 管理组织中的成员资格 -intro: 'After you create your organization, you can {% if currentVersion == "free-pro-team@latest" %}invite people to become{% else %}add people as{% endif %} members of the organization. 您也可以删除组织的成员，以及恢复前成员。' +intro: '在创建组织后，您可以{% if currentVersion == "free-pro-team@latest" %}邀请人员成为{% else %}添加人员为{% endif %}组织的成员。 您也可以删除组织的成员，以及恢复前成员。' redirect_from: - /articles/removing-a-user-from-your-organization/ - /articles/managing-membership-in-your-organization diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 7c41cc549a456..6f81953cadd47 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,52 +2,101 @@ title: 管理组织的安全性和分析设置 intro: '您可以控制功能以保护组织在 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。' permissions: 组织所有者可以管理组织中仓库的安全性和分析设置。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### 关于安全性和分析设置的管理 -{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 +{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 {% if currentVersion == "free-pro-team@latest" %}如果您拥有 {% data variables.product.prodname_GH_advanced_security %} 许可，则您还可以管理对这些功能的访问。 {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} -### Displaying the security and analysis settings +### 显示安全和分析设置 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. +显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。 {% if currentVersion == "free-pro-team@latest" %}如果您的组织或拥有它的企业具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 -### Enabling or disabling a feature for all existing repositories +![{% data variables.product.prodname_GH_advanced_security %} 功能](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} -1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. （可选）为组织中的新仓库默认启用该功能。 ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +### 为所有现有仓库启用或禁用功能 -### Enabling or disabling a feature for all new repositories when they are added +您可以启用或禁用所有仓库的功能。 {% if currentVersion == "free-pro-team@latest" %}您的更改对组织中仓库的影响取决于其可见性： -1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. 在功能右侧的“Configure security and analysis features（配置安全和分析功能）”下，默认对组织中的新仓库启用或禁用该功能。 ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +- **依赖项图** - 您的更改仅影响私有仓库，因为该功能对公共仓库始终启用。 +- **{% data variables.product.prodname_dependabot_alerts %}** - 您的更改影响所有仓库。 +- **{% data variables.product.prodname_dependabot_security_updates %}** - 您的更改影响所有仓库。 +- **{% data variables.product.prodname_GH_advanced_security %}** - 您的更改仅影响私有仓库，因为 {% data variables.product.prodname_GH_advanced_security %} 和相关功能对公共仓库始终启用。 +- **{% data variables.product.prodname_secret_scanning_caps %}** - 您的更改仅影响还启用了 {% data variables.product.prodname_GH_advanced_security %} 的私有仓库。 {% data variables.product.prodname_secret_scanning_caps %} 对公共仓库始终启用。{% endif %} -### Allowing Dependabot to access private repositories +{% data reusables.advanced-security.note-org-enable-uses-seats %} -{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +1. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 + {% if currentVersion == "free-pro-team@latest" %} + !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. （可选）为组织中的新仓库默认启用该功能。 + {% if currentVersion == "free-pro-team@latest" %} + ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 + {% if currentVersion == "free-pro-team@latest" %} + ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} -1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." -1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) -1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. -1. Click **Select repositories**. +### 添加新仓库时自动启用或禁用功能 +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +1. 在功能右侧的“Configure security and analysis features（配置安全和分析功能）”下，默认对组织中的新仓库 +{% if currentVersion == "free-pro-team@latest" %} 或所有新私有仓库{% endif %} 启用或禁用该功能。 + {% if currentVersion == "free-pro-team@latest" %} + ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} -### 延伸阅读 + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} + +### 允许 Dependabot 访问私有仓库 + +{% data reusables.dependabot.beta-note %} -{% if currentVersion == "free-pro-team@latest" %}- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[关于密码扫描](/github/administering-a-repository/about-secret-scanning)" -- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" +{% data variables.product.prodname_dependabot %} 可以检查项目中过时的依赖项引用，并自动生成拉取请求来更新它们。 为此，{% data variables.product.prodname_dependabot %} 必须有权访问所有目标依赖项文件。 通常，如果一个或多个依赖项无法访问，版本更新将失败。 + +默认情况下，{% data variables.product.prodname_dependabot %} 无法更新位于私有仓库中的依赖项。 但是，如果依赖项位于与使用该依赖项之项目相同的组织内的私有 {% data variables.product.prodname_dotcom %} 仓库中，则可以通过授予对主机仓库的访问权限来允许 {% data variables.product.prodname_dependabot %} 成功更新版本。 有关更多信息，包括对私有依赖项支持的限制详情，请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。 + +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +1. 在“{% data variables.product.prodname_dependabot %} repository access（仓库访问权限）”部分，单击设置按钮**{% octicon "gear" aria-label="The Gear icon" %}**。 ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) 将显示一个列表，显示组织中的所有私有仓库。 ![仓库列表](/assets/images/help/organizations/repositories-dialog.png) +1. 选择 {% data variables.product.prodname_dependabot %} 可以访问的仓库。 +1. 单击 **Select repositories（选择仓库）**。 {% endif %} + +### 延伸阅读 + +- “[关于保护仓库](/github/administering-a-repository/about-securing-your-repository)” +- "[关于密码扫描](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)” - "[管理项目依赖项中的漏洞](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md index 310daf419ad79..6d337985b9482 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -10,11 +10,11 @@ versions: ### About the default branch name -When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. When a member of your organization creates a new repository, {% data variables.product.prodname_dotcom %} will create a single branch and set it as the repository's default branch. {% data variables.product.prodname_dotcom %} currently names the default branch `master`, but you can set the default branch to be named anything that makes sense for your development environment. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." +当组织成员在组织中创建一个新仓库时，该仓库将包含一个分支，它就是默认分支。 When a member of your organization creates a new repository, {% data variables.product.prodname_dotcom %} will create a single branch and set it as the repository's default branch. {% data variables.product.prodname_dotcom %} currently names the default branch `master`, but you can set the default branch to be named anything that makes sense for your development environment. 有关默认分支的更多信息，请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。 {% data reusables.branches.set-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)." +如果企业所有者为您的企业强制实施了默认分支名称策略，您将无法为组织设置默认分支名称。 但是，您可以更改单个仓库的默认分支。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %}“[在企业中实施仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)”{% else %}“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)”{% endif %} 和“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。 ### 设置默认分支名称 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md index 47d22460d0993..f725377f83957 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md @@ -1,6 +1,6 @@ --- title: 管理组织的复刻政策 -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.' +intro: '您可以允许或阻止对组织拥有的任何私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 和内部{% endif %} 仓库进行复刻。' 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 @@ -11,9 +11,9 @@ versions: github-ae: '*' --- -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 currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 和内部{% endif %} 仓库。 -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. 更多信息请参阅“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。 +如果您在组织级别上允许复刻私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 和内部{% endif %} 仓库，则还可以配置复刻特定{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库的权限。 更多信息请参阅“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。 {% data reusables.organizations.internal-repos-enterprise %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 0bb43e1db2b87..77db5ca74954c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -12,7 +12,7 @@ versions: ### 组织的权限级别 -Organization members can have *owner*{% if currentVersion == "free-pro-team@latest" %}, *billing manager*,{% endif %} or *member* roles: +组织成员可以是*所有者*{% if currentVersion == "free-pro-team@latest" %}、*帐单管理员*{% endif %} 或*成员*角色。 - **所有者**对组织具有全面的管理权限。 此角色应限于组织中的少数几个人，但不少于两人。 更多信息请参阅“[管理组织的所有权连续性](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)”。 {% if currentVersion == "free-pro-team@latest" %} @@ -39,7 +39,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | 访问组织审核日志 | **X** | | | | 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | | 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”） | **X** | | | -| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| 将电子邮件通知限制为经验证的域（更多信息请参阅“[将电子邮件通知限制为经批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”） | **X** | | | | 删除**所有团队** | **X** | | | | 删除组织帐户，包括所有仓库 | **X** | | | | 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | | @@ -56,9 +56,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”） | **X** | | |{% endif %} | 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | | -| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | -| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | +| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”） | **X** | **X** | | +| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)”） | **X** | | | +| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)”） | **X** | | | | 禁止从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[为组织禁止发布 {% data variables.product.prodname_pages %} 站点](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | | | 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | | | 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | @@ -68,7 +68,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序 | **X** | | | | 列出 {% data variables.product.prodname_marketplace %} 中的应用程序 | **X** | | |{% if currentVersion != "github-ae@latest" %} | 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | **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 %} +| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”） | **X** | | |{% endif %} | [管理复刻策略](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | | [限制组织中公共仓库的活动](/articles/limiting-interactions-in-your-organization) | **X** | | | | 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md index a530f0c3429fd..ccb8fe75c4146 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -8,7 +8,7 @@ versions: enterprise-server: '*' --- -We recommend that you notify {% if currentVersion == "free-pro-team@latest" %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} at least one week before you require 2FA in your organization. +如果您的组织中需要 2FA，建议至少提前一周通知{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}。 需要对您的组织使用双重身份验证时，不使用 2FA 的成员、外部协作者和帐单管理员（包括自动程序帐户）将从组织中删除，并且失去访问其仓库的权限。 他们还会失去对组织私有仓库的复刻的访问权限。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index f78cedea3a19e..b17a594dc7d3f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ versions: ### 项目板可见性 -{% data reusables.project-management.project-board-visibility %} 您可以将项目板的可见性从私人更改为公共，反之亦然。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。 +{% data reusables.project-management.project-board-visibility %} 您可以将项目板的可见性从私有更改为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}，反之亦然。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md index 530fae07e370d..e5b0bd22f8e2a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md @@ -1,18 +1,18 @@ --- title: 恢复组织的前成员 -intro: 'Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite former organization members to rejoin{% else %}add former members to{% endif%} your organization, and choose whether to restore the person''s former role, access permissions, forks, and settings.' +intro: '组织所有者可以{% if currentVersion == "free-pro-team@latest" %}邀请前组织成员重新加入{% else %}将前成员添加到{% endif%}您的组织，并可选择是否恢复该人员以前的角色、访问权限、复刻和设置。' redirect_from: - /articles/reinstating-a-former-member-of-your-organization versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: 'Organization owners can reinstate a former member of an organization.' +permissions: '组织所有者可以恢复组织的前成员。' --- -### About member reinstatement +### 关于成员恢复 -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. 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. +如果您[从组织中删除用户](/articles/removing-a-member-from-your-organization){% if currentVersion == "github-ae@latest" %} 或{% else %}、{% endif %}[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion != "github-ae@latest" %} 或者由于您[要求成员和外部协作者启用双重身份验证 (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} 而从组织中删除用户，则用户的访问权限和设置将保存三个月。 如果您在该时间范围内将用户{% if currentVersion =="free-pro-team@latest" %}邀请{% else %}添加{% endif %}回组织，则可以恢复该用户的权限。 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md index ff5f28a21f5c9..3462d061a25ee 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -1,6 +1,6 @@ --- title: 恢复前外部协作者对组织的访问权限 -intro: "You can reinstate a former outside collaborator's access permissions for organization repositories, forks, and settings." +intro: "您可以恢复前外部协作者对组织仓库、复刻和设置的访问权限。" redirect_from: - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization @@ -10,7 +10,7 @@ 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. +当外部协作者对组织私有仓库的权限被删除时，该用户的访问权限和设置将保存三个月。 如果您在该时间范围内将用户{% if currentVersion == "free-pro-team@latest" %}邀请{% else %}添加{% endif %}回组织，则可以恢复该用户的权限。 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} @@ -27,7 +27,7 @@ When an outside collaborator's access to your organization's private repositorie **提示**： - 只有组织所有者才能恢复外部协作者对组织的访问权限。 更多信息请参阅“[组织的权限级别](/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" %} + - {% data variables.product.product_location %} 上的恢复成员流程可能使用术语“成员”来描述恢复外部协作者，但如果您恢复此人员并保留其以前的权限，则他们将只拥有以前的[外部协作者权限](/articles/permission-levels-for-an-organization/#outside-collaborators)。{% if currentVersion == "free-pro-team@latest" %} - 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。{% endif %} {% endtip %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md index 2eb437878cab1..ca05391dbe1bb 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md @@ -26,7 +26,7 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} 1. 在“ -{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to remove a {% data variables.product.prodname_github_app %} manager from. +在 "{% data variables.product.prodname_github_app %}" 下，单击要从其删除 {% data variables.product.prodname_github_app %}管理员的应用程序的头像。 ![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} 1. 在“App managers（应用程序管理员）”下，找到您要从其删除 {% data variables.product.prodname_github_app %}管理员权限的人员的用户名，然后单击 **Revoke（撤销）**。 ![撤销 {% data variables.product.prodname_github_app %}管理员权限](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md index 4ac549789f2e0..b836598daf00b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md @@ -29,7 +29,7 @@ versions: #### 并非自动的更改 更改组织的名称后： -- 指向以前组织资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previousorgname`）将返回 404 错误。 We recommend you update links to your organization from other sites{% if currentVersion == "free-pro-team@latest" %}, such as your LinkedIn or Twitter profiles{% endif %}. +- 指向以前组织资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previousorgname`）将返回 404 错误。 我们建议您更新从其他站点指向组织的链接{% if currentVersion == "free-pro-team@latest" %}，例如 LinkedIn 或 Twitter 个人资料{% endif %}。 - 使用旧组织名称的 API 请求将返回 404 错误。 我们建议您更新 API 请求中的旧组织名称。 - 对于使用旧组织名称的团队，没有自动[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)重定向。 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 3991182fce694..2e2297fd96359 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,91 +43,94 @@ 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** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| 应用里程碑 | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| 创建[安全通告](/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 %}{% if currentVersion == "free-pro-team@latest" %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 从人员或团队的已分配仓库拉取 | **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** |{% if currentVersion == "free-pro-team@latest" %} +| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| 应用里程碑 | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | +| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** |{% endif %} +| 管理 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#granting-access-to-security-alerts) | | | | | **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** | +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [列出、忽略和删除 {% 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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报，并解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | +| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | +| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库 | | | **X** | **X** | **X** | +| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md index 19c8b554bc010..ae058d1580714 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md @@ -1,6 +1,6 @@ --- title: 您的组织中需要双重身份验证 -intro: 'Organization owners can require {% if currentVersion == "free-pro-team@latest" %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to enable two-factor authentication for their personal accounts, making it harder for malicious actors to access an organization''s repositories and settings.' +intro: '组织所有者可以要求{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}为其个人帐户启用双重身份验证，从而使恶意行为者更难以访问组织的仓库和设置。' redirect_from: - /articles/requiring-two-factor-authentication-in-your-organization versions: @@ -8,13 +8,13 @@ versions: enterprise-server: '*' --- -### About two-factor authentication for organizations +### 关于组织的双重身份验证 -{% data reusables.two_fa.about-2fa %} You can require all {% if currentVersion == "free-pro-team@latest" %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.product_name %}. For more information about two-factor authentication, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." +{% data reusables.two_fa.about-2fa %} 您可以要求组织中的所有{% if currentVersion == "free-pro-team@latest" %}成员、外部协作者和帐单管理员{% else %}成员和外部协作者{% endif %}在 {% data variables.product.product_name %} 上启用双重身份验证。 有关双重身份验证的更多信息，请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 {% if currentVersion == "free-pro-team@latest" %} -You can also require two-factor authentication for organizations in an enterprise. 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)”。 +您还可以要求企业中的组织使用双重身份验证。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)”。 {% endif %} @@ -22,8 +22,8 @@ You can also require two-factor authentication for organizations in an enterpris **警告：** -- When you require use of two-factor authentication for your organization, {% if currentVersion == "free-pro-team@latest" %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以[恢复其访问权限和设置](/articles/reinstating-a-former-member-of-your-organization)。 -- If an organization owner, member,{% if currentVersion == "free-pro-team@latest" %} billing manager,{% endif %} or outside collaborator disables 2FA for their personal account after you've enabled required two-factor authentication, they will automatically be removed from the organization. +- 要求您的组织使用双重身份验证时，不使用 2FA 的{% if currentVersion == "free-pro-team@latest" %}成员、外部协作者和帐单管理员{% else %}成员和外部协作者{% endif %}（包括自动程序帐户）将从组织中删除，并且失去访问其仓库的权限。 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以[恢复其访问权限和设置](/articles/reinstating-a-former-member-of-your-organization)。 +- 如果组织所有者、成员{% if currentVersion == "free-pro-team@latest" %}、帐单管理员{% endif %} 或外部协作者在您启用所需的双重身份验证后为其个人帐户禁用 2FA，则系统会自动将其从组织中删除。 - 如果您是某个要求双重身份验证的组织的唯一所有者，则在不为组织禁用双重身份验证要求的情况下，您将无法为个人帐户禁用双重身份验证。 {% endwarning %} @@ -32,9 +32,9 @@ You can also require two-factor authentication for organizations in an enterpris ### 基本要求 -Before you can require {% if currentVersion == "free-pro-team@latest" %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable two-factor authentication for your account on {% data variables.product.product_name %}. 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 +在要求{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}使用双重身份验证之前，您必须对 {% data variables.product.product_name %} 上的帐户启用双重身份验证。 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 -Before you require use of two-factor authentication, we recommend notifying {% if currentVersion == "free-pro-team@latest" %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} and asking them to set up 2FA for their accounts. You can see if members and outside collaborators already use 2FA. 更多信息请参阅“[查看组织中的用户是否已启用 2FA](/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled)”。 +在您要求使用双重身份验证之前，我们建议您通知{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}，要求他们为其帐户设置 2FA。 您可以查看成员和外部协作者是否已经使用 2FA。 更多信息请参阅“[查看组织中的用户是否已启用 2FA](/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled)”。 ### 您的组织中需要双重身份验证 @@ -59,7 +59,7 @@ Before you require use of two-factor authentication, we recommend notifying {% i {% data reusables.audit_log.audit_log_sidebar_for_org_admins %} 4. 输入您的搜索查询。 要搜索： - 删除的组织成员，请在搜索查询中使用 `action:org.remove_member` - - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% if currentVersion == "free-pro-team@latest" %} + - 删除的外部协作者，请在搜索查询中使用 `action:org.remove_outside_collaborator`{% if currentVersion == "free-pro-team@latest" %} - 删除的帐单管理员，请在搜索查询中使用 `action:org.remove_billing_manager`{% endif %} 您还可以在搜索中使用[时间范围](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action)查看从组织中删除的人员。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md index 4b53c88b98ac0..d536781184354 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md @@ -9,13 +9,13 @@ versions: free-pro-team: '*' --- -### About email restrictions +### 关于电子邮件限制 -When restricted email notifications are enabled in an organization, members can only use an email address associated with the organization's verified domains to receive email notifications about organization activity. 更多信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”。 +当组织中启用了受限电子邮件通知时，成员只能使用与组织的已验证域相关联的电子邮件地址来接收有关组织活动的电子邮件通知。 更多信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”。 外部协作者不受限于已验证域的电子邮件通知。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)”。 -If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." ### 将电子邮件通知限于已批准的域 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md index 92c314aa4c5f1..1b32e3f4bb711 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -您可以选择成员是否可以在组织中创建仓库。 If you allow members to create repositories, you can choose which types of repositories members can create.{% if currentVersion == "free-pro-team@latest" %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %} For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +您可以选择成员是否可以在组织中创建仓库。 如果允许成员创建仓库，您可以选择允许创建哪些类型的仓库。{% if currentVersion == "free-pro-team@latest" %}若只允许成员创建私有仓库，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。{% endif %}更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 组织所有者始终可以创建任何类型的仓库。 -{% if currentVersion == "free-pro-team@latest" %}Enterprise owners{% else %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy. 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" %}企业所有者{% else %}站点管理员{% endif %}可以限制用于组织仓库创建策略的选项。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account)”。{% else %}“[限制企业中的仓库创建](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% endif %} {% warning %} @@ -27,5 +27,5 @@ versions: {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} -5. Under "Repository creation", select one or more options. ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +5. 在“Repository creation（仓库创建）”下，选择一个或多个选项。 ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) 6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md index f383b8846804b..36dbbb2cc814f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -You can restrict the ability to change repository visibility to organization owners only, or allow members with admin privileges for a repository to also change visibility. +您可以将更改仓库可见性的权限仅限于组织所有者，或者允许具有仓库管理员权限的成员也可以更改仓库可见性。 {% warning %} 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 fcb5bd5ba785a..dd8a9367f69c5 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 @@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`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 %} +| [`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 %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. | [`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: @@ -197,7 +197,7 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. #### `dependabot_security_updates` category actions @@ -218,14 +218,14 @@ An overview of some of the most common actions that are recorded as events in th | 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. +| `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. +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. {% endif %} @@ -324,10 +324,12 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|-------------------{% if currentVersion == "free-pro-team@latest"%} +| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal 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)." +| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). | `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} +| `create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization).{% endif %} {% if currentVersion == "free-pro-team@latest"%} | `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. | `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} | `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} @@ -451,7 +453,9 @@ For more information, see "[Restricting publication of {% data variables.product |------------------|------------------- | `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `advanced_security_enabled` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} | `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. | `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. @@ -527,7 +531,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `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" %} @@ -536,7 +540,7 @@ For more information, see "[Restricting publication of {% data variables.product | Action | Description |------------------|------------------- | `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. +| `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 @@ -559,7 +563,7 @@ For more information, see "[Restricting publication of {% data variables.product | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization 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 organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | `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)") @@ -568,7 +572,6 @@ For more information, see "[Restricting publication of {% data variables.product | `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") {% endif %} -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} #### `team` category actions | Action | Description @@ -577,11 +580,12 @@ For more information, see "[Restricting publication of {% data variables.product | `add_repository` | Triggered when a team is given control of a repository. | `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). | `change_privacy` | Triggered when a team's privacy level is changed. -| `create` | Triggered when a new team is created. -| `destroy` | Triggered when a team is deleted from the organization. +| `create` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} +| `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control. -{% endif %} #### `team_discussions` category actions diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md index b91ad3887ec5d..7b17c19189cf5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md @@ -12,7 +12,7 @@ versions: 您可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 基本权限不适用于外部协作者。 -{% if currentVersion == "free-pro-team@latest" %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %} +{% if currentVersion == "free-pro-team@latest" %}默认情况下，组织成员具有对组织仓库的**读取**权限。{% endif %} 如果拥有组织仓库管理员权限的人向组织成员授予更高级别的仓库权限，则更高级别的权限将覆盖基本权限。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md index d30dfd07e8bb1..4302e8685a47c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators.md @@ -19,6 +19,6 @@ versions: {% 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 %} +5. 在“Repository invitations（仓库邀请）”下，选择 **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. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index b7b953ccf109d..1204887acbb48 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: 您最多可以将五个 IdP 组连接到 {% data variables.product.prodname_dotcom %} 团队。 IdP 组可以不受限制地分配给多个 {% data variables.product.prodname_dotcom %} 团队。 +团队同步不支持成员数超过 5000 的 IdP 组。 + {% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您无法在 {% data variables.product.product_name %} 上或使用 API 管理团队成员资格。 通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 审核日志中显示为团队同步自动程序所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %}，每小时一次。 将团队连接到 IdP 组可能会删除一些团队成员。 更多信息请参阅“[已同步团队成员的要求](#requirements-for-members-of-synchronized-teams)”。 @@ -27,19 +29,22 @@ versions: ### 已同步团队成员的要求 -将团队连接到 IdP 组后，如果团队成员继续在 {% data variables.product.prodname_dotcom %} 上使用 SAML SSO 验证相同的 SSO 身份，并且仍然是所连接 IdP 组的成员，则每个团队成员的成员资格数据都会同步。 +将团队连接到 IdP 组后，团队同步将 IdP 组的每个成员添加到 {% data variables.product.prodname_dotcom %} 上的相应团队，但需满足以下条件： +- 此人是 {% data variables.product.prodname_dotcom %} 上的组织的成员。 +- 此人已使用 {% data variables.product.prodname_dotcom %} 上的用户帐户登录，并且至少一次通过 SAML 单点登录向组织或企业帐户验证。 +- 此人的 SSO 身份是 IdP 组的成员。 -现有团队或组成员可能会自动从 {% data variables.product.prodname_dotcom %} 上的团队中删除。 未使用 SSO 向组织或企业帐户验证的任何现有团队或组成员都可能会失去对仓库的访问权限。 未在所连接 IdP 组中的任何现有团队或组成员都可能会失去对仓库的访问权限。 +不符合这些条件的现有团队或组成员将被从 {% data variables.product.prodname_dotcom %} 团队中自动删除，并失去对仓库的访问权限。 撤销用户关联的身份也会将用户从映射到 IdP 组的任何团队中删除。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”和“[查看和管理用户对企业的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)”。 删除后的团队成员在使用 SSO 向组织或企业帐户进行身份验证后可以自动添加回团队，并移动到已连接的 IdP 组。 -为避免无意中删除团队成员，建议在组织或企业帐户中强制实施 SAML SSO，创建新团队以同步成员资格数据，并在同步现有团队之前检查 IdP 组成员资格。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 +为避免无意中删除团队成员，建议在组织或企业帐户中强制实施 SAML SSO，创建新团队以同步成员资格数据，并在同步现有团队之前检查 IdP 组成员资格。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”和“[对企业帐户中的组织启用 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 -如果您的组织由企业帐户拥有，则对企业帐户启用团队同步将覆盖组织级的团队同步设置。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 +如果您的组织由企业帐户拥有，则对企业帐户启用团队同步将覆盖组织级的团队同步设置。 更多信息请参阅“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 ### 基本要求 -在将团队连接到身份提供程序组之前，组织或企业所有者必须为组织或企业帐户启用团队同步。 更多信息请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”和“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 +在将团队连接到身份提供程序组之前，组织或企业所有者必须为组织或企业帐户启用团队同步。 更多信息请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”和“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 为避免无意中删除团队成员，请访问 IdP 的管理门户，并确认每个当前团队成员也位于要连接到此团队的 IdP 组中。 如果您没有身份提供程序的这一访问权限，在可以联系 IdP 管理员。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md index 19d85d7f61856..34095f66660d5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership.md @@ -3,7 +3,7 @@ title: 转让组织所有权 redirect_from: - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ - /articles/transferring-organization-ownership -intro: 'To make someone else the owner of an organization account, you must add a new owner{% if currentVersion == "free-pro-team@latest" %}, ensure that the billing information is updated,{% endif %} and then remove yourself from the account.' +intro: '要使其他人成为组织帐户的所有者，您必须添加新所有者{% if currentVersion == "free-pro-team@latest" %}，确保帐单信息已更新，{% endif %} 然后将自身从该帐户中删除。' versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md index 7e59d8b0a7bee..b0323f65f7f93 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md @@ -11,7 +11,7 @@ versions: 1. 联系我们 -{% data variables.contact.contact_support %} to request an upgrade to the Corporate Terms of Service. 他们将在组织的仪表板上启用横幅，从而允许您接受公司服务条款。 +{% data variables.contact.contact_support %}以请求升级到公司服务条款。 他们将在组织的仪表板上启用横幅，从而允许您接受公司服务条款。 {% data reusables.dashboard.access-org-dashboard %} 3. 在页面顶部，服务条款横幅的右侧，单击 **Sign now（立即签署）**。 ![立即签署按钮](/assets/images/help/organizations/sign-now-button.png) 4. 阅读关于公司服务条款的信息，然后选择 **Yes, I want to sign these terms on behalf of my business.（是，我想代表我的公司签署这些条款。）** ![代表您的公司签署的复选框](/assets/images/help/organizations/sign-on-behalf-business.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md index 939656ed0d73a..ed41be65cece5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md @@ -8,13 +8,13 @@ versions: free-pro-team: '*' --- -### About domain verification +### 关于域验证 要在 {% data variables.product.product_name %} 上验证域，您必须拥有组织中的所有者权限。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 您还需要访问权限以使用您的域托管服务修改域记录。 验证组织域的所有权后，将在组织的资料中显示“Verified（已验证）”徽章。 如果您的组织位于 {% data variables.product.prodname_ghe_cloud %} 上并且已同意公司服务条款，则组织所有者将能够通过查看验证域内每个成员的电子邮件地址来验证组织成员的身份。 更多信息请参阅“[关于组织的资料页面](/articles/about-your-organization-s-profile/)”和“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。 -If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +如果您的组织由企业帐户拥有，则“已验证”徽章将显示在组织的基本资料上，除了显示组织的任何已验证域之外，还能够显示企业帐户的任何已验证域。 For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." {% data reusables.organizations.verified-domains-details %} @@ -29,7 +29,7 @@ If your organization is owned by an enterprise account, a "Verified" badge will 5. 单击 **Add a domain（添加域）**。 ![添加域按钮](/assets/images/help/organizations/add-a-domain-button.png) {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %} -1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. 您应看到命令输出中列出的新 TXT 记录。 +1. 等待 DNS 配置更改，最多可能需要 72 小时。 您可以通过在命令行上运行 `dig` 命令来确认您的 DNS 配置已更改，将 `ORGANIZATION` 替换为您组织的名称，将 `example.com` 替换为要验证的域。 您应看到命令输出中列出的新 TXT 记录。 ```shell $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT ``` diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index 8106890a98cc4..62b1dd3f1c610 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ versions: {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md index 5f352e894a332..17302a153a19a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md @@ -36,7 +36,7 @@ versions: 3. 在组织名称下，单击 {% octicon "graph" aria-label="The bar graph icon" %} **Insights（洞察）**。 ![主要组织导航栏中的洞察选项卡](/assets/images/help/organizations/org-nav-insights-tab.png) 4. 要查看此组织的依赖项，请单击 **Dependencies（依赖项）**。 ![主要组织导航栏下的依赖项选项卡](/assets/images/help/organizations/org-insights-dependencies-tab.png) 5. 要查看所有您的 {% data variables.product.prodname_ghe_cloud %} 组织的依赖项洞察，请单击 **My organizations（我的组织）**。 ![依赖项选项卡下的我的组织按钮](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) -6. 您可以单击 **Open security advisories（未解决安全通告）**和 **Licenses（许可证）**图表中的结果，按漏洞状态、许可证或两者的组合进行过滤。 ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +6. 您可以单击 **Open security advisories（未解决安全通告）**和 **Licenses（许可证）**图表中的结果，按漏洞状态、许可证或两者的组合进行过滤。 ![我的组织漏洞和许可证图表](/assets/images/help/organizations/org-insights-dependencies-graphs.png) 7. 您可以单击每个漏洞旁边的 {% octicon "package" aria-label="The package icon" %} **dependents（从属者）**，以了解组织中的哪些从属者正在使用每个库。 ![我的组织有漏洞的从属者](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md index c7d06858907a1..629f02ebab34f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -10,7 +10,7 @@ versions: {% note %} -**Note:** You can require that all members{% if currentVersion == "free-pro-team@latest" %}, including, owners, billing managers and{% else %} and{% endif %} outside collaborators in your organization have two-factor authentication enabled. 更多信息请参阅“[您的组织中需要双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)”。 +**注：**您可以要求所有成员{% if currentVersion == "free-pro-team@latest" %}（包括组织中的所有者、帐单管理员和{% else %} 和{% endif %} 外部协作者）均启用双因素身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)”。 {% endnote %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md index 908d5acaa49d7..9619ff70c106b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md @@ -20,11 +20,11 @@ versions: - 安全性（单点登录、双重身份验证） - 与 {% data variables.contact.enterprise_support %} 共享请求和支持包 -{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." For more information about managing your {% data variables.product.prodname_ghe_server %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +{% data reusables.enterprise-accounts.enterprise-accounts-billing %}有关管理 {% data variables.product.prodname_ghe_cloud %} 订阅的更多信息，请参阅“[查看企业帐户的订阅和使用情况](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)”。 有关管理 {% data variables.product.prodname_ghe_server %} 帐单设置的更多信息，请参阅“[管理企业的帐单](/admin/overview/managing-billing-for-your-enterprise)”。 有关 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_ghe_server %} 之间差异的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。 要升级至 {% data variables.product.prodname_enterprise %} 或开始使用企业帐户，请联系 {% data variables.contact.contact_enterprise_sales %}。 -For more information about 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 %}." +有关成员权限和管理的更多信息，请参阅“{% if currentVersion == "free-pro-team@latest" %}[管理企业中的用户](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[管理用户、组织和仓库](/admin/user-management){% endif %}”。 有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..8515671786500 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,31 @@ +--- +title: About identity and access management for your enterprise account +intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +### About identity and access management for your enterprise account + +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." + +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. + +{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." + +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." + +### Supported IdPs + +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 + +| IdP | SAML | User provisioning | 团队同步 | +| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | + diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..340cafd61d496 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,28 @@ +--- +title: About user provisioning for organizations in your enterprise account +intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +product: '{% data reusables.gated-features.enterprise-accounts %}' +versions: + free-pro-team: '*' +--- + +{% data reusables.enterprise-accounts.user-provisioning-release-stage %} + +{% data reusables.saml.about-user-provisioning-enterprise-account %} + +{% data reusables.scim.enterprise-account-scim %}（可选）您也可以启用 SAML 预配和单独取消预配。 + +If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. 如果启用 SAML 预配，则每当企业成员访问受企业帐户 SAML 配置保护的资源时，该 SAML 断言都将触发预配。 + +对于每个 SCIM 呼叫或 SAML 断言，{% data variables.product.product_name %} 都将检查用户所属的 IdP 组并执行以下操作： + +- 如果用户是企业帐户拥有的组织对应的 IdP 组的成员，并且该用户当前不是该组织的成员，请将该用户添加到组织（SAML 断言）或向用户发送电子邮件邀请其加入组织（SCIM 呼叫）。 +- 取消邀请用户加入您的企业帐户所拥有的组织的任何现有邀请。 + +对于每个 SCIM 呼叫，如果您启用 SAML 解除预配，则对于每个 SAML 断言，{% data variables.product.product_name %} 也会执行以下操作： + +- 如果用户不是企业帐户拥有的组织对应的 IdP 组的成员，并且该用户当前是该组织的成员，请将组织中删除该用户。 + +如果解除预配从组织中删除最后一个剩余的所有者，组织将变得没有所有者。 企业所有者可以接管无所有者组织的所有权。 更多信息请参阅“[管理企业帐户中无所有者的组织](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)”。 + +要使用 Okta 为您的企业帐户启用用户预配，请参阅“[使用 Okta 为企业帐户配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md new file mode 100644 index 0000000000000..5ccf47f7ada3c --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -0,0 +1,9 @@ +--- +title: Configuring identity and access management for your enterprise account +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +product: '{% data reusables.gated-features.enterprise-accounts %}' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index 7a0afd3585319..c887b19e77ef8 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ SAML SSO 控制并保护对企业帐户资源（如组织、仓库、议题和 1. 在下拉菜单右侧键入 `.*.*`。 1. 单击 **Save（保存）**。 {% data reusables.saml.okta-view-setup-instructions %} -1. 使用设置说明中的信息为企业帐户启用 SAML。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 +1. 使用设置说明中的信息为企业帐户启用 SAML。 更多信息请参阅“[为企业帐户中的组织启用 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 ### 在 Okta 中创建组 diff --git a/translations/zh-CN/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/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account.md index 2bd1d3b7665fb..932dce5f9f169 100644 --- a/translations/zh-CN/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/zh-CN/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: 为企业帐户中的 GitHub Actions 构件和日志配置保留期 +intro: '企业所有者可以为企业帐户中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。' 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 +## 设置企业的保留期 {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..d32250482fada --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,42 @@ +--- +title: 为企业帐户中的组织启用 SAML 单点登录 +intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +versions: + free-pro-team: '*' +--- + +### About SAML single sign-on for enterprise accounts + +{% data reusables.saml.dotcom-saml-explanation %}更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)”。 + +{% data reusables.saml.about-saml-enterprise-accounts %} + +{% data reusables.saml.about-saml-access-enterprise-account %} 更多信息请参阅“[查看和管理用户对企业帐户的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)”。 + +{% data reusables.saml.saml-supported-idps %} + +{% data reusables.scim.enterprise-account-scim %} 如果您没有参与私人测试，那么 SIM 卡不支持企业账户。 更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 + +### Enabling SAML single-sign on for organizations in your enterprise account + +{% note %} + +**注：**对企业帐户启用 SAML 单点登录身份验证将覆盖任何现有的组织级 SAML 配置。 + +{% endnote %} + +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. 在 **Sign on URL（登录 URL）**字段中，为单点登录请求输入您的 IdP 的 HTTPS 端点。 此值可在 IdP 配置中找到。 ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png) +8. 在 **Public Certificate（公共证书）**下，粘贴证书以验证 SAML 响应。 ![身份提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) +9. 要验证来自 SAML 签发者的请求的完整性，请单击 {% octicon "pencil" aria-label="The edit icon" %}。 Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) +10. 在为企业启用 SAML SSO 之前，单击 **Test SAML configuration（测试 SMAL 配置）** ，以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) +11. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md index 5003d0771d422..02e0c16bf0fa9 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -17,7 +17,7 @@ versions: ### 管理企业帐户的 {% data variables.product.prodname_actions %} 权限 -You can disable all workflows for an enterprise or set a policy that configures which actions can be used in an organization. +您可以禁用企业的所有工作流程，或者设置策略来配置哪些操作可用于组织中。 {% data reusables.actions.actions-use-policy-settings %} @@ -34,7 +34,7 @@ You can disable all workflows for an enterprise or set a policy that configures {% 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. ![添加操作到允许列表](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) +1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) ### 为私有仓库复刻启用工作流程 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md index eda576b022ffc..2f9ab210f0444 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md @@ -49,7 +49,7 @@ versions: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 3. 在 **Repository policies（仓库策略）**选项卡中的“Repository invitations（仓库邀请）”下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -4. Under "Repository invitations", use the drop-down menu and choose a policy. ![带有外部协作者邀请策略选项的下拉菜单](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) +4. 在“Repository invitations（仓库邀请）”下，使用下拉菜单并选择策略。 ![带有外部协作者邀请策略选项的下拉菜单](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) ### 实施有关更改仓库可见性的策略 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 342ff4e8c69d1..30575d4629dd5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ versions: {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### 为企业帐户中的组织启用 SAML 单点登录 - -{% data reusables.saml.dotcom-saml-explanation %}更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)”。 - -企业所有者可以通过 SAML IdP 跨企业帐户拥有的所有组织启用 SAML SSO 和集中式身份验证。 为企业帐户启用 SAML SSO 后，默认情况下会为您的企业帐户拥有的所有组织启用 SAML SSO。 所有成员都需要使用 SAML SSO 进行身份验证才能访问其所属的组织，并且企业所有者在访问企业帐户时需要使用 SAML SSO 进行身份验证。 - -{% data reusables.saml.about-saml-access-enterprise-account %} 更多信息请参阅“[查看和管理用户对企业帐户的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)”。 - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} 如果您没有参与私人测试，那么 SIM 卡不支持企业账户。 更多信息请参阅“[管理企业帐户中组织的用户配置](#managing-user-provisioning-for-organizations-in-your-enterprise-account)”。 - -{% note %} - -**注：**对企业帐户启用 SAML 单点登录身份验证将覆盖任何现有的组织级 SAML 配置。 - -{% endnote %} - -有关如何使用 Okta 启用 SAML 的更多详细信息，请参阅[使用 Okta 为企业帐户配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)。 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. 在 **Sign on URL（登录 URL）**字段中，为单点登录请求输入您的 IdP 的 HTTPS 端点。 此值可在 IdP 配置中找到。 ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) -7. （可选）在 **Issuer（签发者）** 字段中，输入您的 SAML 签发者的姓名。 此操作验证已发送消息的真实性。 ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png) -8. 在 **Public Certificate（公共证书）**下，粘贴证书以验证 SAML 响应。 ![身份提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) -9. 要验证来自 SAML 签发者的请求的完整性，请单击 {% octicon "pencil" aria-label="The edit icon" %}。 然后，在 Signature Method（签名方法）和 Digest Method（摘要方法）下拉菜单中，选择 SAML 签发者使用的哈希算法。 ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) -10. 在为企业启用 SAML SSO 之前，单击 **Test SAML configuration（测试 SMAL 配置）** ，以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) -11. 单击 **Save（保存）**。 - -### 管理企业帐户中组织的用户配置 - -企业所有者可直接从身份提供程序 (IdP) 管理企业帐户中的组织成员身份。 - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %}（可选）您也可以启用 SAML 预配和单独取消预配。 - -如果您在 IdP 中配置 SCIM，每次更改您在 IdP 中的成员身份时， 您的 IdP 将向 {% data variables.product.prodname_dotcom %} 发出 SCIM 呼叫来更新对应组织的成员身份。 如果启用 SAML 预配，则每当企业成员访问受企业帐户 SAML 配置保护的资源时，该 SAML 断言都将触发预配。 - -对于每个 SCIM 呼叫或 SAML 断言，{% data variables.product.product_name %} 都将检查用户所属的 IdP 组并执行以下操作： - -- 如果用户是企业帐户拥有的组织对应的 IdP 组的成员，并且该用户当前不是该组织的成员，请将该用户添加到组织（SAML 断言）或向用户发送电子邮件邀请其加入组织（SCIM 呼叫）。 -- 取消邀请用户加入您的企业帐户所拥有的组织的任何现有邀请。 - -对于每个 SCIM 呼叫，如果您启用 SAML 解除预配，则对于每个 SAML 断言，{% data variables.product.product_name %} 也会执行以下操作： - -- 如果用户不是企业帐户拥有的组织对应的 IdP 组的成员，并且该用户当前是该组织的成员，请将组织中删除该用户。 - -如果解除预配从组织中删除最后一个剩余的所有者，组织将变得没有所有者。 企业所有者可以接管无所有者组织的所有权。 更多信息请参阅“[管理企业帐户中无所有者的组织](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)”。 - -要使用 Okta 为您的企业帐户启用用户预配，请参阅“[使用 Okta 为企业帐户配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)”。 - -### 管理企业帐户中组织的团队同步 - -企业所有者可以在 IdP 与 {% data variables.product.product_name %} 之间启用团队同步，以让组织所有者和团队维护员将企业帐户拥有的组织中的团队与 IdP 组连接起来。 - -{% data reusables.identity-and-permissions.about-team-sync %} - -您可通过 Azure AD 对企业帐户使用团队同步。 - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -您也可以配置和管理单个组织的团队同步。 更多信息请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”。 - -#### 基本要求 - -在可以为企业帐户启用团队同步之前： - - 您或您的 Azure AD 管理员必须是 Azure AD 中的全局管理员或特权角色管理员。 - - 您必须使用受支持的 IdP 为企业帐户中的组织启用 SAML 单点登录。 更多信息请参阅“[为企业帐户中的组织启用 SAML 单点登录](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 - - 您必须使用 SAML SSO 和支持的 IdP 向企业帐户进行身份验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 - -#### 管理 Azure AD 的团队同步 - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. 查看要连接到企业帐户的身份提供程序租户信息，然后单击 **Approve（批准）**。 ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png) -8. 要禁用团队同步，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png) - ### 管理企业帐户的 SSH 认证中心 企业所有者可以添加和删除企业帐户的 SSH 认证中心 (CA)。 @@ -203,3 +112,7 @@ versions: {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### 延伸阅读 + +- "[为企业帐户配置身份和访问权限管理](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md index 4fab6a88285d9..99f6f505c2fbf 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/zh-CN/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: 设置和管理企业 +shortTitle: 您的企业 product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md index 79df2fcacc025..ccac8b47ea1ab 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/zh-CN/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: 邀请人员管理企业 intro: 您可以邀请人员成为企业帐户的企业所有者或帐单管理员。 也可以删除不再需要访问企业帐户的企业所有者或帐单管理员。 product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: @@ -13,7 +13,7 @@ versions: ### 关于邀请人员管理企业帐户 -{% 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 %} 更多信息请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)”。 {% tip %} 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 c6f135ef0a877..ae108398db391 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 @@ -1,6 +1,6 @@ --- -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 %}.' +title: 管理包含 GitHub Enterprise 的 Visual Studio 订阅 +intro: '您可以管理 {% data variables.product.prodname_vss_ghe %} 的 {% data variables.product.prodname_enterprise %} 许可。' 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 @@ -13,32 +13,36 @@ versions: ### 关于 {% data variables.product.prodname_vss_ghe %} -{% data variables.product.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. +{% data variables.product.prodname_vss_ghe %} 是 Microsoft 的组合产品，允许订阅者使用 {% data variables.product.prodname_enterprise %} 和 {% data variables.product.prodname_vs %}。 {% data variables.product.prodname_vss_ghe %} 由 Microsoft 根据 Microsoft 企业协议的条款提供。 更多信息请参阅 {% data variables.product.prodname_vs %} 网站上的 [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/)。 -After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. +将 {% data variables.product.prodname_vss_ghe %} 许可分配给订阅者后，订阅者将使用 {% data variables.product.prodname_dotcom_the_website %} 上的用户帐户加入您企业帐户中的组织，从而使用许可的 {% data variables.product.prodname_enterprise %} 部分。 如果 {% data variables.product.prodname_dotcom_the_website %} 上的企业成员用户帐户电子邮件地址匹配订阅 {% data variables.product.prodname_vs %} 帐户的用户主名 (UPN)，则 {% data variables.product.prodname_vs %} 订阅者将自动占用一个 {% data variables.product.prodname_vss_ghe %} 许可。 -有关 {% data variables.product.prodname_enterprise %} 的更多信息，请参阅“[{% data variables.product.company_short %} 的产品](/github/getting-started-with-github/githubs-products#github-enterprise)”。 For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." +您的企业在 {% data variables.product.prodname_dotcom %} 上的许可总数等于任何标准 {% data variables.product.prodname_enterprise %} 许可和包括 {% data variables.product.prodname_dotcom %} 访问权限的 {% data variables.product.prodname_vs %} 订阅许可数量的总和。 如果企业成员的用户帐户与 {% data variables.product.prodname_vs %} 订阅者的电子邮件地址不对应，则该用户帐户占用的许可不适用于 {% data variables.product.prodname_vs %} 订阅者。 + +有关 {% data variables.product.prodname_enterprise %} 的更多信息，请参阅“[{% data variables.product.company_short %} 的产品](/github/getting-started-with-github/githubs-products#github-enterprise)”。 有关 {% data variables.product.prodname_dotcom_the_website %} 帐户的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户类型](/github/getting-started-with-github/types-of-github-accounts)”。 ### 基本要求 -1. After you buy {% data variables.product.prodname_vss_ghe %}, contact {% data variables.contact.contact_enterprise_sales %} and mention "{% data variables.product.prodname_vss_ghe %}." You'll work with the Sales team to create an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. If you already have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, please tell our Sales team. +1. 购买 {% data variables.product.prodname_vss_ghe %} 后，请联系 {% data variables.contact.contact_enterprise_sales %} 并提及 "{% data variables.product.prodname_vss_ghe %}"。 您将与销售团队合作，在 {% data variables.product.prodname_dotcom_the_website %} 上创建企业帐户。 如果您已经拥有 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户，或者您不确定，请告知我们的销售团队。 + +2. 在 {% data variables.product.prodname_vss_admin_portal_with_url %} 中向订阅者分配 {% data variables.product.prodname_vss_ghe %} 许可。 有关分配许可的更多信息，请参阅 Microsoft 文档中的[管理包含 {% data variables.product.prodname_enterprise %} 的 {% data variables.product.prodname_vs %} 订阅](https://docs.microsoft.com/visualstudio/subscriptions/assign-github)。 -2. Assign licenses for {% data variables.product.prodname_vss_ghe %} to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information about assigning licenses, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/assign-github) in the Microsoft Docs. +3. 在 {% data variables.product.prodname_dotcom_the_website %} 上，至少创建一个由企业帐户拥有的组织。 更多信息请参阅“[将组织添加到企业帐户](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)”。 -3. On {% data variables.product.prodname_dotcom_the_website %}, create at least one organization owned by your enterprise account. For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." +### 邀请订阅者使用 {% data variables.product.prodname_enterprise %} -4. The subscriber must create a user account on {% data variables.product.prodname_dotcom_the_website %}, and the email address for the account must be the same email address as the email address in the {% data variables.product.prodname_vs %} portal. For more information, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." +要使用许可的 {% data variables.product.prodname_enterprise %} 部分，订阅者在 {% data variables.product.prodname_dotcom_the_website %} 上的用户帐户必须是或成为 {% data variables.product.prodname_dotcom_the_website %} 上的企业所拥有组织的成员。 -### Inviting a subscriber to use {% data variables.product.prodname_enterprise %} +组织所有者可以通过电子邮件地址邀请新成员加入组织。 组织所有者邀请的电子邮件地址必须匹配 {% data variables.product.prodname_vs %} 订阅者的用户主名 (UPN)，它应该是一个电子邮件地址。 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有用户帐户或创建一个新帐户来接受邀请。 -To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber must join an organization owned by your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Organization owners can invite new members to an organization. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +更多信息请参阅“[邀请用户加入组织](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)”、“[注册 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)”和“[管理电子邮件首选项](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)”。 -### Viewing {% data variables.product.prodname_enterprise %} licensing +### 查看 {% data variables.product.prodname_enterprise %} 许可 -After assigning a license for {% data variables.product.prodname_vss_ghe %} in {% data variables.product.prodname_vss_admin_portal_with_url %}, you can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise account. 更多信息请参阅"[查看企业帐户的订阅和使用](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)"。 +在 {% data variables.product.prodname_vss_admin_portal_with_url %} 中分配 {% data variables.product.prodname_vss_ghe %} 许可后，您可以查看企业帐户中可用的 {% data variables.product.prodname_enterprise %} 许可数量。 更多信息请参阅"[查看企业帐户的订阅和使用](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)"。 -You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise account. 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)." +您也可以在 {% data variables.product.prodname_vss_admin_portal_with_url %} 中查看对订阅者的待处理 {% data variables.product.prodname_enterprise %} 邀请。 待处理邀请列表包括尚未加入企业帐户中至少一个组织的订阅者。 更多信息请参阅“[查看企业中的人员](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)”。 ### 延伸阅读 -- [Introducing Visual Studio subscriptions with GitHub Enterprise](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in the Microsoft Docs +- Microsoft 文档中的[包含 GitHub Enterprise 的 Visual Studio 订阅简介](https://docs.microsoft.com/visualstudio/subscriptions/access-github) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md new file mode 100644 index 0000000000000..8f683ebc6356a --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -0,0 +1,41 @@ +--- +title: 管理企业帐户中组织的团队同步 +intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +permissions: Enterprise owners can manage team synchronization for an enterprise account. +versions: + free-pro-team: '*' +--- + +### About team synchronization for enterprise accounts + +If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% data reusables.identity-and-permissions.sync-team-with-idp-group %} + +{% data reusables.identity-and-permissions.team-sync-disable %} + +您也可以配置和管理单个组织的团队同步。 更多信息请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”。 + +### 基本要求 + +您或您的 Azure AD 管理员必须是 Azure AD 中的全局管理员或特权角色管理员。 + +您必须使用受支持的 IdP 为企业帐户中的组织启用 SAML 单点登录。 更多信息请参阅“[为企业帐户中的组织启用 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 + +您必须使用 SAML SSO 和支持的 IdP 向企业帐户进行身份验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 + +### 管理 Azure AD 的团队同步 + +{% data reusables.identity-and-permissions.team-sync-azure-permissions %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.identity-and-permissions.team-sync-confirm-saml %} +{% data reusables.identity-and-permissions.enable-team-sync-azure %} +{% data reusables.identity-and-permissions.team-sync-confirm %} +7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png) +8. 要禁用团队同步，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index dfc6aefedcb94..f55a1cababc38 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -如果允许用户取消预配来管理企业帐户中的组织成员身份，最终可能会获得一个没有组织所有者的组织。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)”。 +如果允许用户取消预配来管理企业帐户中的组织成员身份，最终可能会获得一个没有组织所有者的组织。 更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 {% data reusables.enterprise-accounts.access-enterprise %} 2. 在搜索字段的右侧，单击 **X unowned（没有所有者）**。 ![用于查看没有所有者的组织的按钮](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 53d7df9447cbe..a6d7bee5c517a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -20,42 +20,42 @@ Everyone in an enterprise is a member of the enterprise. You can also assign adm 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 %}". -### 企业所有者 +### Enterprise owner Enterprise owners have complete control over the enterprise and can take every action, including: -- 管理管理员 +- Managing administrators - {% 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 -- 管理企业设置 -- 在组织范围内强制实施政策 +- Managing enterprise settings +- Enforcing policy across organizations {% if currentVersion == "free-pro-team@latest" %}- Managing billing settings{% endif %} -企业所有者无法访问组织设置或内容，除非将其设为组织所有者或授予直接访问组织所拥有仓库的权限。 Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. +Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. 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. -### 企业成员 +### Enterprise members 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 %}. -People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. 您可以查看每个人具有访问权限的资源。 For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)." +People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)." -有关组织级权限的更多信息，请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 +For more information about organization-level permissions, see "[Permission levels for an organization](/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. 有关外部协作者的更多信息，请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization#outside-collaborators)”。 +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. For more information about outside collaborators, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#outside-collaborators)." {% if currentVersion == "free-pro-team@latest" %} -### 帐单管理员 +### Billing manager Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can: -- 查看和管理用户许可证、{% data variables.large_files.product_name_short %} 包以及其他计费设置 -- 查看帐单管理员列表 -- 添加或删除其他帐单管理员 +- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings +- View a list of billing managers +- Add or remove other billing managers -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. 帐单管理员必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。 +Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. -### 延伸阅读 +### Further reading -- “[关于企业帐户](/articles/about-enterprise-accounts)” +- "[About enterprise accounts](/articles/about-enterprise-accounts)" {% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index 83b1e856f71cd..e45f2fc0a5f5c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -12,7 +12,7 @@ redirect_from: {% data reusables.enterprise-accounts.verifying-domains-release-phase %} -### About domain verification +### 关于域验证 You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account, and organization owners can verify additional domains for their organizations. 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 @@ -34,7 +34,7 @@ To verify your enterprise account's domain, you must have access to modify domai 1. 单击 **Add a domain（添加域）**。 ![添加域按钮](/assets/images/help/enterprises/add-a-domain-button.png) {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %} -1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. 您应看到命令输出中列出的新 TXT 记录。 +1. 等待 DNS 配置更改，最多可能需要 72 小时。 You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. 您应看到命令输出中列出的新 TXT 记录。 ```shell dig _github-challenge-ENTERPRISE-ACCOUNT.example.com +nostats +nocomments +nocmd TXT ``` diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 4232c29f019aa..b0061c3300cea 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/zh-CN/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: 查看和管理用户对企业的 SAML 访问 intro: '您可以查看和撤销企业成员的链接身份、活动会话和授权凭据。' permissions: 企业所有者可以查看和管理成员对组织的 SAML 访问。 product: '{% data reusables.gated-features.enterprise-accounts %}' @@ -18,6 +18,8 @@ versions: {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md index 115d9ad287a55..479f00c3f1ab3 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/zh-CN/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: 查看企业中的人员 +intro: '要审核对企业拥有的资源或用户许可证使用的访问权限，企业所有者可以查看企业的每个管理员和成员。' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account @@ -11,28 +11,28 @@ versions: github-ae: '*' --- -### Viewing enterprise owners{% if currentVersion == "free-pro-team@latest" %} and billing managers{% endif %} +### 查看企业所有者{% if currentVersion == "free-pro-team@latest" %}和帐单管理员{% 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 %}. 您可以通过搜索其用户名或全名查找特定人员。 +您可以查看企业所有者{% if currentVersion == "free-pro-team@latest" %}和帐单管理员，{% endif %}以及待处理邀请成为所有者{% if currentVersion == "free-pro-team@latest" %}和帐单管理员的列表。 您可以按角色过滤企业管理员列表{% endif %}。 您可以通过搜索其用户名或全名查找特定人员。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %} -{% if currentVersion == "free-pro-team@latest" %}1. Optionally, to view a list of pending invitations, click **_NUMBER_ pending**. - !["NUMBER pending" button to the right of search and filter options](/assets/images/help/enterprises/administrators-pending.png){% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. （可选）要查看待处理邀请列表，请单击 **_NUMBER_ pending（待处理）**。 + ![搜索和过滤选项右侧的 "NUMBER 待处理" 按钮](/assets/images/help/enterprises/administrators-pending.png){% endif %} ### 查看成员和外部协作者 -您可以查看待处理成员和外部协作者的数量。 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. 您可以按协作者具有访问权限的仓库的可见性来过滤外部协作者列表。 您可以通过搜索其用户名或显示名称查找特定人员。 +您可以查看待处理成员和外部协作者的数量。 您可以按{% if currentVersion == "free-pro-team@latest" %}部署（{% data variables.product.prodname_ghe_cloud %} 或 {% data variables.product.prodname_ghe_server %}）、{% endif %}角色{% if currentVersion == "free-pro-team@latest" %}和{% elsif currentVersion == "github-ae@latest" %}或{% endif %}组织过滤成员列表。 您可以按协作者具有访问权限的仓库的可见性来过滤外部协作者列表。 您可以通过搜索其用户名或显示名称查找特定人员。 -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. +通过单击人员姓名，您可以查看{% if currentVersion == "free-pro-team@latest" %}该成员所属的所有 {% data variables.product.prodname_ghe_cloud %} 组织和 {% data variables.product.prodname_ghe_server %} 实例，以及{% endif %}外部协作者能够访问的仓库{% if currentVersion == "free-pro-team@latest" %} {% endif %} 。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} 1. （可选）要查看外部协作者列表而不是成员列表，请单击 **Outside collaborators（外部协作者）**。 ![组织成员页面上的外部协作者选项卡](/assets/images/help/business-accounts/outside-collaborators-tab.png) -{% if currentVersion == "free-pro-team@latest" %}1. Optionally, to view a list of pending invitations, click **_NUMBER_ pending**. - !["NUMBER pending" button to the right of search and filter options](/assets/images/help/enterprises/members-pending.png){% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. （可选）要查看待处理邀请列表，请单击 **_NUMBER_ pending（待处理）**。 + ![搜索和过滤选项右侧的 "NUMBER 待处理" 按钮](/assets/images/help/enterprises/members-pending.png){% endif %} ### 延伸阅读 -- "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" +- "[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 5ad4ff9e68f7b..cb24a0fa1c94b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,15 +15,15 @@ versions: 企业帐户目前适用于通过发票付费的 {% data variables.product.prodname_enterprise %} 客户。 对与企业帐户关联的所有组织和 {% data variables.product.prodname_ghe_server %} 实例的结算将汇总为所有付费 {% data variables.product.prodname_dotcom_the_website %} 服务（包括组织中的付费许可、{% data variables.large_files.product_name_long %} 数据包和 {% 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)." +有关管理帐单管理员的更多信息，请参阅“[邀请人员管理企业](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)”。 ### 查看企业帐户的订阅和使用情况 {% 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. +1. 在“User +{% if currentVersion == "free-pro-team@latest" %}Licenses{% else %}licenses{% endif %}（用户许可）”下，查看您的总许可数、已消耗许可数以及订阅到期日期。 {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![企业计费设置中的许可证和订阅信息](/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 %}**. +1. （可选）要查看许可使用详情或下载包含许可详情的 {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} 文件{% if currentVersion == "free-pro-team@latest" %}，请在“User Licenses（用户许可）”的右侧{% endif %}，单击**查看{% if currentVersion == "free-pro-team@latest" %}详细信息{% elsif enterpriseServerVersions contains currentVersion %}用户{% endif %}**或{% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage（导出许可使用信息）**{% endif %}。{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index 93ab0a3eddbdd..3e089724f9526 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -12,7 +12,7 @@ versions: 您可以选择为组织添加说明、地点、网站和电子邮件地址，以及将重要仓库固定于页面顶部。 -{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 +{% if currentVersion == "free-pro-team@latest" %}要确认组织的身份并在组织资料页面显示“已验证”徽章，必须使用 {% data variables.product.product_name %} 验证组织的域。 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 ![验证过的组织资料页面示例](/assets/images/help/profile/org_profile_verified.png) {% else %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md index 45132aa5fe988..e63ae04939e9c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md @@ -23,12 +23,12 @@ versions: 人们在访问您的个人资料时会看到您的贡献活动时间表，如您打开的议题和拉取请求、您进行的提交，以及您审查的拉取请求。 您可以选择只显示公共贡献或同时包含私人的匿名化贡献。 更多信息请参阅“[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)”或“[在您的个人资料中公开或隐藏私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。 -People who visit your profile can also see the following information. +访问您的个人资料的人也可以看到以下信息。 -- 你拥有或参与的仓库和 gists。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can showcase your best work by pinning repositories and gists to your profile. 更多信息请参阅“[将项目嵌入到个人资料](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)”。{% endif %} -- 您标星的仓库。 For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)." -- 您在经常参与的组织、仓库和团队中的活动概述。 For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %} -- Badges that show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)”。{% endif %} +- 你拥有或参与的仓库和 gists。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}您可以通过在个人资料中置顶仓库和 Gist 来展示您的得意之作。 更多信息请参阅“[将项目嵌入到个人资料](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)”。{% endif %} +- 您标星的仓库。 更多信息请参阅“[使用星标保存仓库](/articles/saving-repositories-with-stars/)”。 +- 您在经常参与的组织、仓库和团队中的活动概述。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。{% if currentVersion == "free-pro-team@latest" %} +- 徽章，显示您是否使用 {% data variables.product.prodname_pro %} 或参与计划，例如 {% data variables.product.prodname_arctic_vault %}、{% data variables.product.prodname_sponsors %} 或 {% data variables.product.company_short %} 开发者计划。 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)”。{% endif %} 您还可以在个人资料上设置状态，以提供有关您的可用性的信息。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md index b15c14b1c24e3..df3df89ea31a4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md @@ -41,7 +41,7 @@ versions: ### 更改个人资料名称 -您可以更改显示在个人资料中的名称。 This name may also be displayed next to comments you make on private repositories owned by an organization. 更多信息请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。 +您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 更多信息请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。 {% data reusables.user_settings.access_settings %} 2. 在“Name（名称）”下，键入要显示在个人资料中的名称。 ![个人资料设置中的名称字段](/assets/images/help/profile/name-field.png) @@ -52,7 +52,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -要以更长和更突出的方式显示有关自己的自定义信息，您还可以使用个人资料自述文件。 For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." +要以更长和更突出的方式显示有关自己的自定义信息，您还可以使用个人资料自述文件。 更多信息请参阅“[管理个人资料自述文件](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。 {% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md index 44ec02ad5171a..37625c7a3401a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md @@ -1,6 +1,6 @@ --- title: 在个人资料中嵌入项目 -intro: 'You can pin gists and repositories to your profile so other people can quickly see your best work.' +intro: '您可以将 Gist 和仓库置顶在个人资料中，使其他人可以很快看到您的得意之作。' redirect_from: - /articles/pinning-repositories-to-your-profile/ - /articles/pinning-items-to-your-profile diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 729b8dde2612c..49bf9f5428088 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- title: 在个人资料中公开或隐藏您的私人贡献 -intro: '您的 {% data variables.product.product_name %} 个人资料显示过去一年中您的仓库贡献图。 You can choose to show anonymized activity from {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}private and internal{% else %}private{% endif %} repositories{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} in addition to the activity from public repositories{% endif %}.' +intro: '您的 {% data variables.product.product_name %} 个人资料显示过去一年中您的仓库贡献图。 除了显示公共仓库中的活动之外，您还可以选择匿名显示{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}私有和内部{% else %}私有{% endif %}仓库中的活动{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}{% endif %}。' redirect_from: - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile versions: diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index b5a2e61068e91..33bb4740a5148 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -39,20 +39,20 @@ versions: $ git show Your commit SHA number --pretty=fuller commit Your commit SHA number Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` 如果创作和提交日期不同，您可以在 URL 中手动更改提交日期以查看提交详细信息。 例如： -- 以下 URL 使用的创作日期为 `2016-07-13`： +- 以下 URL 使用的创作日期为 `2018-04-03`： - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- 以下 URL 使用的提交日期为 `2016-07-19`： + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- 以下 URL 使用的提交日期为 `2018-04-10`： - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` 使用修改后的提交日期打开 URL 时，您可以看到提交详细信息。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 906c318ffec51..57acc9009add8 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- title: 在个人资料中查看贡献 -intro: 'Your {% data variables.product.product_name %} profile shows off {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.' +intro: '您的 {% data variables.product.product_name %} 个人资料突出显示{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}您置顶的仓库以及{% endif %}过去一年的仓库贡献图。' redirect_from: - /articles/viewing-contributions/ - /articles/viewing-contributions-on-your-profile-page/ @@ -11,11 +11,11 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. 更多信息请参阅“[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。 +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}您的贡献图显示公共仓库的活动。 {% endif %}您可以选择显示{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}公共和{% endif %}私有仓库的活动，并将私有仓库中活动的具体详细信息匿名化。 更多信息请参阅“[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。 {% note %} -**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)” +**注：**仅当您用于创作提交的电子邮件地址与您在 {% data variables.product.product_name %} 上的帐户相连时，提交才会显示在您的贡献图中。 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)” {% endnote %} @@ -26,14 +26,14 @@ versions: - 提交到仓库的默认分支或 `gh-pages` 分支 - 打开议题 - 提议拉取请求 -- Submitting a pull request review{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- 提交拉取请求审查{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - 合作创作仓库默认分支或 `gh-pages` 分支中的提交{% endif %} {% data reusables.pull_requests.pull_request_merges_and_contributions %} ### 受欢迎的仓库 -此部分显示具有最多查看者的仓库。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %} +此部分显示具有最多查看者的仓库。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}一旦您[在个人资料置顶仓库](/articles/pinning-repositories-to-your-profile)，此部分将更改为“置顶的仓库”。{% endif %} ![受欢迎的仓库](/assets/images/help/profile/profile_popular_repositories.png) @@ -86,9 +86,9 @@ versions: {% if currentVersion != "github-ae@latest" %} ### 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.product_location_enterprise %}的贡献 -If your site administrator has enabled +如果站点管理员已启用 -{% 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. 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 贡献发送到 {% 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 %}，您可以将 {% data variables.product.prodname_enterprise %} 贡献计数发送到您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 贡献发送到 {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)”。 {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index f68ee15c7f4b0..521badd316fef 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### 计算的贡献 -#### 议题和拉取请求 +#### 议题、拉取请求和讨论 -如果议题和拉取请求在独立的仓库而不是复刻中打开，它们将在您的贡献图中显示。 +如果议题、拉取请求和讨论在独立的仓库而不是复刻中打开，它们将在您的贡献图中显示。 #### 提交 如果提交符合以下**所有**条件，则会在您的贡献图中显示： @@ -39,9 +39,9 @@ versions: 进行满足计为贡献要求的提交后，您可能需要等待最长 24 小时才能看到在贡献图中显示的贡献。 -#### Your local Git commit email isn't connected to your account +#### 您的本地 Git 提交电子邮件地址未连接到您的帐户 -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 %} +必须使用已连接到 {% data variables.product.product_name %} 帐户的电子邮件地址{% if currentVersion == "free-pro-team@latest" %}或 {% data variables.product.product_name %} 在电子邮件设置中提供的 `noreply` 电子邮件地址进行提交，{% endif %} 提交才会显示在您的贡献图中。{% if currentVersion == "free-pro-team@latest" %} 有关 `noreply` 电子邮件地址的更多信息，请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)”。{% endif %} 您可以通过将 `.patch` 添加到提交 URL 结尾来检查用于提交的电子邮件地址，例如 https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch： @@ -54,7 +54,7 @@ Subject: [PATCH] updated index for better welcome message `From:` 字段中的电子邮件地址是在[本地 git 配置设置](/articles/set-up-git)中设置的地址。 在本例中，用于提交的电子邮件地址是 `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 %} +如果用于提交的电子邮件地址未连接到您的 {% data variables.product.product_name %} 帐户，{% if currentVersion == "github-ae@latest" %}请更改用于在 Git 中创作提交的电子邮件地址。 更多信息请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。{% else %}您必须[添加电子邮件地址](/articles/adding-an-email-address-to-your-github-account)到您的 {% data variables.product.product_name %} 帐户。 您的贡献图将在添加新地址后自动重建。{% endif %} {% warning %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md index 882d6ed7f6fee..7951054fec90a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -29,7 +29,7 @@ versions: ![不同组织中的仓库和团队列表](/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. +常用仓库列表自动生成，可以包括您与之交互的任何仓库，无论它是否由您的帐户直接拥有。 交互包括提交和打开或评论议题和拉取请求。 常用仓库列表无法编辑，但其中的仓库将在您最后一次与之交互 4 个月后从列表中删除。 您也可以点击 {% data variables.product.product_name %} 上任何页面顶部的搜索栏，查找近期访问过的仓库、团队及项目板列表。 @@ -39,17 +39,17 @@ The list of top repositories is automatically generated, and can include any rep 当您关注的用户执行以下操作时，您会在消息馈送中看到更新： - 对仓库标星。 -- Follows another user.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- Creates a public repository.{% endif %} +- 关注其他用户。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- 创建公共仓库。{% endif %} - 在您关注的仓库上打开具有“需要帮助”或“良好的第一个议题”标签的议题或拉取请求。 -- Pushes commits to a repository you watch.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- Forks a public repository.{% endif %} +- 向您关注的仓库推送提交。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +- 复刻公共仓库。{% endif %} 有关对仓库标星和关注人员的更多信息，请参阅“[使用星标保存仓库](/articles/saving-repositories-with-stars/)" and "[关注人员](/articles/following-people)”。 ### 探索推荐的仓库 -在仪表板右侧的“Explore repositories（浏览仓库）”部分，您可以浏览社区中推荐的仓库。 Recommendations are based on repositories you've starred or visited, the people you follow, and activity within repositories that you have access to.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %} +在仪表板右侧的“Explore repositories（浏览仓库）”部分，您可以浏览社区中推荐的仓库。 建议基于您已经标星或访问过的仓库、您关注的人以及您可以访问的仓库中的活动。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md index 158ae686cb188..8b7681fd8d2c2 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md @@ -14,7 +14,7 @@ versions: ### 关于用户名更改 -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. +您可以将用户名更改为当前未使用的另一个用户名。{% if currentVersion == "free-pro-team@latest" %} 如果所需的用户名不可用，您在键入所需的用户名时将看到您是否可以申请释放该用户名的信息。 如果该用户名不符合释放条件，并且您不持有该用户名的商标，则可选择其他用户名或保留您当前的用户名。 {% data variables.contact.github_support %} 无法为您释放不可用的用户名。 更多信息请参阅“[更改用户名](#changing-your-username)”。{% endif %} @@ -34,11 +34,11 @@ You can change your username to another username that is not currently in use.{% ### 指向以前的个人资料页面的链接 -更改用户名后，指向以前的个人资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previoususername`）将返回 404 错误。 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 %}. +更改用户名后，指向以前的个人资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previoususername`）将返回 404 错误。 我们建议从其他位置更新指向 {% data variables.product.product_name %} 帐户的所有链接{% if currentVersion == "free-pro-team@latest" %}，例如您的 LinkedIn 或 Twitter 个人资料{% endif %}。 ### 您的 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. 有关设置电子邮件地址的更多详细信息，请参阅“[设置您的提交电子邮件地址](/articles/setting-your-commit-email-address)”。 +{% if currentVersion == "free-pro-team@latest"%}与您的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址关联的 Git 提交不会归于新的用户名，并且不会在您的贡献图中显示。{% endif %}如果您的 Git 提交与您已[添加到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)的其他电子邮件地址关联，{% if currentVersion == "free-pro-team@latest"%}包括基于 ID 的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址，{% endif %}它们在您更改用户名后将继续归于您并在您的贡献图中显示。 有关设置电子邮件地址的更多详细信息，请参阅“[设置您的提交电子邮件地址](/articles/setting-your-commit-email-address)”。 ### 更改用户名 @@ -53,5 +53,5 @@ You can change your username to another username that is not currently in use.{% ### 延伸阅读 - “[更改远程的 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" %} +- “[我的提交为什么链接到错误的用户？](/articles/why-are-my-commits-linked-to-the-wrong-user)”{% if currentVersion == "free-pro-team@latest" %} - "[{% data variables.product.prodname_dotcom %} 用户名策略](/articles/github-username-policy)"{% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md index aa32121fa50c6..28e216cd806d4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md @@ -21,8 +21,8 @@ versions: 5. 要从帐户中删除旧电子邮件地址，请在旧电子邮件地址旁边单击 {% octicon "trashcan" aria-label="The trashcan symbol" %}. {% if currentVersion == "free-pro-team@latest" %} -6. 验证新的主电子邮件地址。 Without a verified email address, you won't be able to use all of -{% data variables.product.product_name %}'s features. 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。 +6. 验证新的主电子邮件地址。 如果没有经验证的电子邮件地址，您将无法使用所有 +{% data variables.product.product_name %} 的功能。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。 {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index c572f9f8564ac..a815b6a56bcb9 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -17,7 +17,7 @@ versions: - 您将**不再**能够登录被转换的用户帐户。 - 您将**不再**能够创建或修改被转换的用户帐户所拥有的 Gist。 - **无法**将组织转换回用户。 - - The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. 这只适用于被转换的用户帐户，而不适用于该用户帐户的任何协作者。 + - SSH 密钥、OAuth 令牌、作业档案、 反应、及关联的用户信息**不会**传输到组织。 这只适用于被转换的用户帐户，而不适用于该用户帐户的任何协作者。 - 使用被转换用户帐户进行的任何提交**将不再链接**到该帐户。 提交本身**将**保持原状。 {% endwarning %} @@ -35,7 +35,7 @@ versions: 也可以将个人用户帐户直接转换为组织。 转换帐户： - 按原样保留仓库，无需手动将其转让给另一个帐户 - 自动邀请协作者加入与他们以前的权限相当的团队 - {% if currentVersion == "free-pro-team@latest" %}- For user accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %} + {% if currentVersion == "free-pro-team@latest" %}-对 {% data variables.product.prodname_pro %} 上的用户帐户，自动将帐单转移到[付费 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts)，任何时候都无需重新输入付款信息、调整结算周期或双重付费{% endif %} 1. 创建新的个人帐户，转换后您将用它来登录 GitHub 以及访问组织和仓库。 2. [离开](/articles/removing-yourself-from-an-organization)要转换的用户帐户此前加入的任何组织。 @@ -56,5 +56,5 @@ versions: ### 延伸阅读 - "[设置团队](/articles/setting-up-teams)" -{% if currentVersion == "free-pro-team@latest" %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %} +{% if currentversion == "free proteam@latest" %}-"[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)"{% endif %} - “[访问组织](/articles/accessing-an-organization)” diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md index bbe94cd1612b8..66e274d548ac7 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md @@ -9,9 +9,9 @@ versions: enterprise-server: '*' --- -删除用户帐户会移除帐户所拥有的所有仓库、私有仓库分支、wiki、议题、拉取请求和页面。 {% if currentVersion == "free-pro-team@latest" %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %} +删除用户帐户会移除帐户所拥有的所有仓库、私有仓库分支、wiki、议题、拉取请求和页面。 {% if currentVersion == "free-pro-team@latest" %} 在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除，而是与我们的[Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除。{% endif %} -{% if currentVersion == "free-pro-team@latest" %} The account name also becomes available to anyone else to use on a new account, and we stop billing you. 与该账户关联的电子邮件地址可用于不同的 {% data variables.product.product_name %} 帐户。 {% endif %} +{% if currentVersion == "free-pro-team@latest" %} 其他人也可以在新帐户中使用该帐户名称，我们会停止向您收费。 与该账户关联的电子邮件地址可用于不同的 {% data variables.product.product_name %} 帐户。 {% endif %} 如果您是组织的唯一所有者，则必须先将所有权转让给其他人或删除该组织，然后才能删除您的用户帐户。 如果组织中有其他所有者，则必须先从组织中删除自己，然后才能删除用户帐户。 @@ -38,7 +38,7 @@ versions: - 如果您是组织中的唯一所有者，则必须将所有权转让给其他人或删除您的组织。 - 如果组织中有其他组织所有者，则必须将自己从组织中删除。 ![帐户删除按钮](/assets/images/help/settings/settings-account-delete.png) 4. 在“Make sure you want to do this（确保要执行此操作）”对话框中，完成以下步骤，以确认您了解删除帐户时会发生什么： ![删除帐户确认对话框](/assets/images/help/settings/settings-account-deleteconfirm.png) - {% if currentVersion == "free-pro-team@latest" %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, your billing will end, and your username will be available to anyone for use on {% data variables.product.product_name %}. + {% if currentVersion == "free-pro-team@latest" %}- 重新考虑一下，您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除，您的计费将会终止，并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。 {% else %}- 重新考虑一下，您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除，并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。 {% endif %}- 在第一个字段中，输入您的 {% data variables.product.product_name %} 用户名或电子邮件。 - 在第二个字段中，键入提示短语。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 30f6c04c71a8e..a134b8bb4b1e5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -10,7 +10,7 @@ versions: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} -3. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_app %}**。 ![{% data variables.product.prodname_oauth_app %}s tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png) +3. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_app %}**。 ![左侧边栏中的 {% data variables.product.prodname_oauth_app %} 选项卡](/assets/images/help/settings/developer-settings-oauth-apps.png) 3. 单击 **Register a new application（注册新应用程序）**。 4. 在 **Application name（应用程序名称）**下输入 "Jira"。 5. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index 6be9f1153d98e..5525774a8e0df 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -1,6 +1,6 @@ --- title: 邀请协作者参加个人仓库 -intro: 'You can {% if currentVersion == "free-pro-team@latest" %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.' +intro: '您可以{% if currentVersion == "free-pro-team@latest" %}邀请用户成为{% else %}添加用户成为{% endif %}个人仓库的协作者。' redirect_from: - /articles/how-do-i-add-a-collaborator/ - /articles/adding-collaborators-to-a-personal-repository/ @@ -30,7 +30,7 @@ versions: 1. 询问您要邀请成为合作者的人员的用户名。 -{% if currentVersion == "free-pro-team@latest" %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %} +{% if currentVersion == "free-pro-team@latest" %} 如果他们还没有用户名，他们可以注册 {% data variables.product.prodname_dotcom %} 更多信息请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md index a94bfc0927e4a..2d48ea9ae224b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md @@ -19,8 +19,8 @@ versions: {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} -5. Under "Search by username, full name or email address", type the collaborator's name, username, or -{% data variables.product.prodname_dotcom %} email. +5. 在“Search by username, full name or email address（按用户名、全名或电子邮件地址搜索）”下，输入协作者的姓名、用户名或 +{% data variables.product.prodname_dotcom %} 电子邮件。 ![在搜索字段中输入了 Octocat 用户名的协作者部分](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} 7. 新协作者默认具有读取权限。 在新协作者名称旁边，可以选择使用下拉菜单选择不同的权限级别。 ![选择了权限下拉菜单的协作者部分](/assets/images/help/projects/user-project-collaborators-edit-permissions.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md index 1e5f0df17a4c6..72d239dda67d8 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md @@ -35,4 +35,4 @@ versions: - “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)” - "[管理项目依赖项中的漏洞](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" -{% if currentVersion == "free-pro-team@latest" %}- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index df7cd669b925e..3069ac6f3127b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -9,7 +9,7 @@ versions: ### About the default branch name -When you create a new repository on {% data variables.product.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." +当您在 {% data variables.product.product_location %} 上创建一个新仓库时，仓库将包含一个分支，它就是默认分支。 您可以更改 {% data variables.product.product_name %} 用于您新建仓库中默认分支的名称。 有关默认分支的更多信息，请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。 {% data reusables.branches.set-default-branch %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index 9d0358aadc12f..c539820368e85 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -1,21 +1,21 @@ --- -title: Managing your theme settings -intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +title: 管理主题设置 +intro: 通过设置主题首选项以遵循系统设置或始终使用浅色模式或深色模式，您可以管理 {% data variables.product.product_name %} 的外观， versions: free-pro-team: '*' --- {% note %} -**Note:** Theme settings is currently in beta and subject to change. +**注意：**主题设置目前处于测试阶段，可能会更改。 {% endnote %} -For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. +为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。 有些开发者出于个人喜好使用深色主题，以减少某些设备的功耗，或者在低光条件下减少眼睛疲劳。 {% data reusables.user_settings.access_settings %} -1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) -1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) +1. 在用户设置侧边栏中，单击 **Appearance（外观）**。 ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png) +1. 在“Theme（主题）”下，选择主题首选项。 ![主题设置的单选按钮](/assets/images/help/settings/theme-settings-radio-buttons.png) ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index a72ea5c42b1d5..933de4126ee45 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -1,6 +1,6 @@ --- title: 用户帐户仓库的权限级别 -intro: 'A repository owned by a user account has two permission levels: the repository owner and collaborators.' +intro: '用户帐户拥有的仓库有两种权限级别：仓库所有者和协作者。' redirect_from: - /articles/permission-levels-for-a-user-account-repository versions: @@ -9,49 +9,50 @@ versions: github-ae: '*' --- -### About permissions levels for a user account repository +### 关于用户帐户仓库的权限级别 -Repositories owned by user accounts have one owner. Ownership permissions can't be shared with another user account. +用户帐户拥有的仓库有一个所有者。 所有权权限无法与其他用户帐户共享。 -You can also {% if currentVersion == "free-pro-team@latest" %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)." +您还可以{% if currentVersion == "free-pro-team@latest" %}邀请{% else %}添加{% endif %} {% data variables.product.product_name %} 上的用户成为仓库的协作者。 更多信息请参阅“[邀请协作者参加个人仓库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)”。 {% tip %} -**Tip:** If you require more granular access to a repository owned by your user account, consider transferring the repository to an organization. 更多信息请参阅“[转让仓库](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)”。 +**提示：**如果需要对用户帐户拥有的仓库实施更细致的权限，请考虑将仓库转让给组织。 更多信息请参阅“[转让仓库](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)”。 {% endtip %} -### Owner access for a repository owned by a user account - -仓库所有者对仓库具有完全控制权。 In addition to the actions that any collaborator can perform, the repository owner can perform the following actions. - -| 操作 | 更多信息 | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | -| "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | -| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %} -| 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | -| 删除仓库 | "[删除仓库](/github/administering-a-repository/deleting-a-repository)" | -| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} -| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| 删除包 | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} -| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| Receive | | -| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | -| Manage data use for a private repository | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} -| 定义仓库的代码所有者 | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | -| Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} -| Create security advisories | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | -| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} - -### Collaborator access for a repository owned by a user account - -Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. +### 所有者对用户帐户拥有仓库的权限 + +仓库所有者对仓库具有完全控制权。 除了任何协作者可以执行的操作外，仓库所有者还可以执行以下操作。 + +| 操作 | 更多信息 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% if currentVersion == "free-pro-team@latest" %}邀请协作者{% else %}添加协作者{% endif %} | | +| "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | +| 更改仓库的可见性 | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% if currentVersion == "free-pro-team@latest" %} +| 限制与仓库的交互 | "[限制仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| 重命名分支，包括默认分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | +| 删除仓库 | "[删除仓库](/github/administering-a-repository/deleting-a-repository)" | +| 管理仓库的主题 | "[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} +| 管理仓库的安全性和分析设置 | "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| 为私有仓库启用依赖项图 | “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)” |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| 删除包 | “[删除包](/github/managing-packages-with-github-packages/deleting-a-package)” |{% endif %} +| 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} +| 接收 | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}有漏洞依赖项{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %} | "[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)”|{% endif %} +| 定义仓库的代码所有者 | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| 存档仓库 | "[关于存档仓库](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} +| 创建安全通告 | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| 显示赞助按钮 | “[在仓库中显示赞助按钮](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)” | +| 允许或禁止自动合并拉取请求 | "[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} + +### 协作者对用户帐户拥有仓库的权限 + +个人仓库的协作者可以拉取（读取）仓库的内容并向仓库推送（写入）更改。 {% note %} @@ -59,26 +60,27 @@ Collaborators on a personal repository can pull (read) the contents of the repos {% endnote %} -Collaborators can also perform the following actions. - -| 操作 | 更多信息 | -|:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" | -| Create, edit, and delete comments on commits, pull requests, and issues in the repository |
            • "[About issues](/github/managing-your-work-on-github/about-issues)"
            • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
            • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
            | -| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | -| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | -| Manage milestones for issues and pull requests in the repository | "[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | -| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | -| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" %} -| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} -| Apply suggested changes to pull requests in the repository | "[Incorporating feedback in your pull request](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | -| Create a pull request from a fork of the repository | "[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | -| Submit a review on a pull request that affects the mergeability of the pull request | "[审查拉取请求中提议的更改](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | -| Create and edit a wiki for the repository | "[关于 wikis](/github/building-a-strong-community/about-wikis)" | -| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | -| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} -| 作为仓库协作者删除自己 | "[从协作者的仓库删除您自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | +协作者还可以执行以下操作。 + +| 操作 | 更多信息 | +|:--------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 复刻仓库 | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} +| 重命名除默认分支以外的分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 |
            • "[关于议题](/github/managing-your-work-on-github/about-issues)"
            • "[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
            • "[管理破坏性评论](/github/building-a-strong-community/managing-disruptive-comments)"
            | +| 在仓库中创建、分配、关闭和重新打开议题 | "[使用议题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| 在仓库中管理议题和拉取请求的标签 | "[标记议题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| 在仓库中管理议题和拉取请求的里程碑 | "[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| 将仓库中的议题或拉取请求标记为重复项 | "[关于重复的议题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| 在仓库中创建、合并和关闭拉取请求 | "[通过拉取请求提议工作更改](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" %} +| 启用或禁用自动合并拉取请求 | "[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} +| 将建议的更改应用于仓库中的拉取请求 | "[在拉取请求中加入反馈](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | +| 从仓库的复刻创建拉取请求 | "[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| 提交影响拉取请求可合并性的拉取请求审查 | "[审查拉取请求中提议的更改](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| 为仓库创建和编辑 wiki | "[关于 wikis](/github/building-a-strong-community/about-wikis)" | +| 为仓库创建和编辑发行版 | “[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)” | +| 作为仓库的代码所有者 | "[关于代码所有者](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} +| 发布、查看或安装包 | "[发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| 作为仓库协作者删除自己 | "[从协作者的仓库删除您自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index c05fcf00f4f35..f5ebdb8fb0b73 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ versions: 项目板所有者和具有管理员权限的协作者对项目板有完全控制权限。 除了项目板协作者拥有的所有权限之外，项目板所有者和具有管理员权限的协作者还可以： - [管理、查看和添加协作者](/articles/managing-access-to-your-user-account-s-project-boards) -- [将项目板配置为公共或私有](/articles/changing-project-board-visibility) +- [将项目板配置为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}或私有](/articles/changing-project-board-visibility) - [删除项目板](/articles/deleting-a-project-board/) - [关闭项目板](/articles/closing-a-project-board/) - [重新打开关闭的项目板](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ versions: ### 项目板可见性 -您可以将项目板的可见性从私有改为公共以及反向更改。 默认情况下，用户拥有的项目板为私有。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。 +您可以将项目板的可见性从私有更改为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}，反之亦然。 默认情况下，用户拥有的项目板为私有。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md index cb303167f43df..674ede1321b26 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md @@ -1,6 +1,6 @@ --- title: 设置备用电子邮件地址 -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: 使用备用电子邮件地址作为安全相关帐户通知的额外目标地址{% if currentVersion != "github-ae@latest" %}，在您无法再访问主电子邮件地址时用于安全地重置您的密码{% endif %}。 redirect_from: - /articles/setting-a-backup-email-address versions: diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md index 5d60bebbc697f..0d52922c98f50 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md @@ -1,6 +1,6 @@ --- title: 设置提交电子邮件地址 -intro: 'You can set the email address that is used to author commits on {% data variables.product.product_name %} and on your computer.' +intro: '您可以设置用于在 {% data variables.product.product_name %} 和计算机上创作提交的电子邮件地址。' redirect_from: - /articles/keeping-your-email-address-private/ - /articles/setting-your-commit-email-address-on-github/ @@ -22,7 +22,7 @@ versions: 对于基于 web 的 Git 操作，您可以在 {% data variables.product.product_name %} 上设置提交电子邮件地址。 对于从命令行推送的提交，您可以在 Git 中设置提交电子邮件地址。 -{% if currentVersion == "free-pro-team@latest" %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %} +{% if currentVersion == "free-pro-team@latest" %}在更改提交电子邮件地址之前进行的提交仍与之前的电子邮件地址关联。{% else %}在 {% data variables.product.product_name %} 上更改提交电子邮件地址之后，新电子邮件地址默认在所有未来基于 web 的 Git 操作中可见。 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -34,11 +34,11 @@ versions: {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you'd like to keep your personal email address private, you can use a {% data variables.product.product_name %}-provided `no-reply` email address as your commit email address. 要将 `noreply` 电子邮件地址用于从命令行推送的提交，请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 web 的 Git 操作，请在 GitHub 上设置提交电子邮件地址并选择**对我的电子邮件地址保密**。 +{% if currentVersion == "free-pro-team@latest" %}如果要对个人电子邮件地址保密，可以使用 {% data variables.product.product_name %}-provided `no-reply` 电子邮件地址作为提交电子邮件地址。 要将 `noreply` 电子邮件地址用于从命令行推送的提交，请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 web 的 Git 操作，请在 GitHub 上设置提交电子邮件地址并选择**对我的电子邮件地址保密**。 您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 更多信息请参阅“[阻止推送的命令行显示您的个人电子邮件地址](/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 %} +为确保提交归因于您并且出现在您的贡献图表中，请使用已连接到 {% data variables.product.product_name %} 帐户的电子邮件地址{% if currentVersion == "free-pro-team@latest" %}，或者在电子邮件设置中提供给您的 `noreply` 电子邮件地址{% endif %}。 {% if currentVersion != "github-ae@latest" %}更多信息请参阅“[添加电子邮件地址到 {% 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/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 f7fb9cf454c14..72709b3019bd3 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,7 +37,7 @@ versions: - 骚扰、辱骂、威胁或煽动暴力对待任何个人或团体，包括我们的员工、高管和代理或其他用户； -- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users; +- 发布与主题无关的内容，或者以严重影响或反复干扰其他用户体验的方式使用平台功能。 - 将我们的服务器用于任何形式的过度自动化批量活动（如发送垃圾邮件或加密货币挖矿），通过自动化方式对我们的服务器施加不当的负担，或者通过我们的服务器转发任何其他形式的主动广告或招揽，如快速致富方案； @@ -50,17 +50,17 @@ versions: ### 4. 服务使用限制 未获明确的书面同意，不得重制、重复、复制、销售、转售或利用服务的任何部分、使用服务或访问服务。 -### 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: +### 5. 信息使用限制 +您可以出于以下原因使用我们服务中的信息，无论是爬取、通过我们的 API 收集还是以其他方式获取信息： -- 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. +- 研究人员可以出于研究目的而从服务中爬取公开的非个人信息，但仅当来自该研究的出版物[开放访问时](https://en.wikipedia.org/wiki/Open_access)才可爬取。 +- 存档人员可以将本服务中的公开信息用于存档目的。 -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 部分。 +爬取是指通过自动化过程（如自动程序或网络爬虫 ）从我们的服务中提取数据。 爬取不是指通过我们的 API 收集信息。 有关我们的 API 条款，请参阅我们[服务条款](/articles/github-terms-of-service#h-api-terms)的 H 部分。 -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. +不得将服务中的信息（无论是爬取、通过我们的 API 收集的还是以其他方式获取的信息）用于垃圾邮件目的，包括向用户发送未经请求的电子邮件或出售用户个人信息（定义见 [GitHub 隐私声明](/github/site-policy/github-privacy-statement)），例如向招聘人员、猎头或职介所出售此类信息。 -Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). +对服务信息的使用必须遵守 [GitHub 隐私声明](/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 22e1655cdc945..5fb314384f26a 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,13 +4,13 @@ versions: free-pro-team: '*' --- -Version Effective Date: December 14, 2020 +版本生效日期：2020 年 12 月 14 日 -创建帐户后，您有权访问许多不同的功能和产品，它们都是服务的一部分。 由于其中许多功能和产品具有不同的功能，因此可能需要特定于该功能或产品的附加条款和条件。 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. +使用服务须遵守适用的条款（“协议”）。 使用附加产品和功能即表示您也同意这些附加产品条款、 任何违反附加产品条款的行为都构成违反协议。 附加产品条款中未定义的大写术语，将采用协议中规定的含义。 -If you are using GitHub AE, then you may only access the following features and products: Third Party Integrations, Git LFS Support, Pages. +如果您使用的是 GitHub AE，则只能访问以下功能和产品：第三方集成、Git LFS 支持、Pages。 ### 1. Marketplace @@ -39,18 +39,18 @@ If you are using GitHub AE, then you may only access the following features and ### 4. 页面 -Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). 这种托管服务旨在为所有用户托管静态网页，但主要用作个人和组织项目的展示。 页面上允许一些货币化工作，如捐款按钮和筹款链接。 +每个帐户都可以访问 [GitHub Pages 静态托管服务](/github/working-with-github-pages/about-github-pages)。 这种托管服务旨在为所有用户托管静态网页，但主要用作个人和组织项目的展示。 页面上允许一些货币化工作，如捐款按钮和筹款链接。 GitHub Pages 受某些特定带宽和使用限制的约束，可能不适用于某些高带宽用途或其他禁止用途。 请参阅我们的 [GitHub Pages 指南](/github/working-with-github-pages/about-github-pages)了解更多信息。 GitHub 保留随时收回任何 GitHub 子域而不承担任何责任的权利。 ### 5. Actions 和 Packages #### a. Actions 的使用 -GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. +GitHub Actions 按用量计费。 [Actions 文档](/actions)包含详细信息，包括计算和存储量（取决于您的帐户计划）以及如何监控您的 Actions 分钟使用和设置使用限制。 -Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). 此外，Actions 不得用于： +对 Actions 和任何 Action 服务元素的使用，不得违反协议、[GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)或 [Actions 文档](/actions)规定的 GitHub Actions 服务限制。 此外，Actions 不得用于： - 密码破解; -- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); +- 使用我们的服务器破坏、非授权访问或尝试非授权访问任何服务、设备、数据、帐户或网络（[GitHub 漏洞赏金计划](https://bounty.github.com)授权的活动除外）； - 出于商业目的，提供兜售 Actions 或任何 Actions 元素的独立或集成应用程序或服务； - 任何给我们的服务器带来负担的活动，如果这种负担与提供给用户的收益不成比例（例如，不要将 Action 用作内容交付网络或作为无服务器应用程序的一部分，但收益低负担也低的 Action 可能没问题）；或 - 与使用 GitHub Actions 的仓库相关的软件项目创建、测试、部署或发布无关的任何其他活动。 @@ -58,7 +58,7 @@ Actions and any elements of the Actions service may not be used in violation of 为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub Actions 可能会导致作业终止，或者您使用 GitHub Actions 的权限受限。 #### b. Packages 的使用 -GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). +GitHub Packages 按用量计费。 [Packages 文档](/packages)包含详细信息，包括带宽和存储量（取决于您的帐户计划）以及如何监控您的 Packages 使用和设置使用限制。 Packages 带宽使用受 [GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)限制。 ### 6. Learning Lab @@ -70,7 +70,7 @@ GitHub Packages is billed on a usage basis. The [Packages documentation](/packag ### 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. GitHub Connect 可用于执行自动化任务。 此外，多个用户可通过 GitHub Connect 导向某些操作。 Customer is responsible for actions that are performed on or through its Accounts. GitHub 可收集有关客户如何使用 GitHub Connect 的信息，以提供和改进功能。 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. 客户还授权将识别实例信息通过 GitHub Connect 传输到 GitHub，这些信息受“GitHub 隐私声明”管辖。 +要访问 GitHub Connect，客户必须至少在 GitHub.com 上有一 (1) 个帐户以及一 (1) 个许可的软件实例。 客户通过 Connect 访问和使用 github.com 受适用的服务使用协议管辖。 GitHub Connect 可用于执行自动化任务。 此外，多个用户可通过 GitHub Connect 导向某些操作。 客户应对在其帐户上或通过其帐户执行的操作负责。 GitHub 可收集有关客户如何使用 GitHub Connect 的信息，以提供和改进功能。 只要使用 GitHub Connect，即表示客户授权 GitHub 从客户帐户收集受保护的数据，包括私人仓库数据和用户个人信息（如“GitHub 隐私声明”中定义）。 客户还授权将识别实例信息通过 GitHub Connect 传输到 GitHub，这些信息受“GitHub 隐私声明”管辖。 ### 8. 赞助计划 @@ -78,7 +78,7 @@ In order to access GitHub Connect, Customer must have at least one (1) Account o ### 9. GitHub Advanced Security -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 操作。 +GitHub Advanced Security 按“唯一提交者”许可。 “唯一提交者”是 GitHub Enterprise、GitHub Enterprise Cloud、GitHub Enterprise Server 或 GitHub AE 的许可用户，他们在过去 90 天内向激活了 GitHub Advanced Security 功能的任意仓库提交过代码。 您必须为每个唯一提交者获取 GitHub Advanced Security 用户许可。 您只能在由您开发或为您开发的代码库上使用 GitHub Advanced Security。 如果您将 GitHub Advanced Security 用作 GitHub Enterprise Cloud 的一部分，GitHub Advanced Security 的许多功能（包括对私有仓库的自动化代码扫描）还需要使用 GitHub 操作。 ### 10. Dependabot Preview @@ -100,10 +100,10 @@ GitHub Advisory Database 的许可采用[知识共享署名 4.0 许可](https:// ### 13. GitHub Enterprise Server -#### a. SQL Server Images +#### a. SQL Server 映像 -You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation 可随时禁用 SQL Server 映像。 +您可以下载用于 Linux 文件的 Microsoft SQL Server 标准版容器映像（“SQL Server 映像”）。 当您使用本软件的权利结束时，您必须卸载 SQL Server 映像。 Microsoft Corporation 可随时禁用 SQL Server 映像。 -#### b. Third-party components +#### b. 第三方组件 软件包含第三方许可给 GitHub 的组件，其中包括其许可证需要 GitHub 为可用组件提供源代码的软件。 这些组件的源代码将在请求时提供。 diff --git a/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md b/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md index 8e1d09cecf45b..ff692bdcd180b 100644 --- a/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md +++ b/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com、GitHub Enterprise Server 以及您上传至其中任一产品的信息都需遵守贸易管制法规，包括美国出口管理条例（Export Administration Regulations，EAR）。 出口管理条例 (EAR)。 -GitHub 的愿景是成为开发者合作的全球平台，不管开发者居住在哪里都可参与。 我们认真履行全面研究政府法规的职责，以确保用户和客户不受法律以外因素的影响。 这包括保持公共仓库服务，其中包括提供开放源码项目并帮助用户访问，以支持受制裁区域开发人员的个人沟通。 +GitHub 的愿景是成为开发者合作的全球平台，不管开发者居住在哪里都可参与。 我们认真履行全面研究政府法规的职责，以确保用户和客户不受法律以外因素的影响。 这包括保持公共仓库服务，其中包括提供开放源码项目并帮助用户访问，以支持受制裁区域开发人员的个人沟通。 这也意味着 GitHub 将提倡受制裁区域的开发者享有更大的平台访问权，并充分进入全球开源社区。 -为了遵守美国 为了遵守美国贸易管制法律，GitHub 对其提供服务的方式作了一些必要的更改。 随着美国 随着美国贸易管制法律的发展，我们将继续配合美国监管机构，在允许的范围内向受制裁市场的开发者提供免费代码协作服务。 监管机构，在允许的范围内向受制裁市场的开发者提供免费代码协作服务。 我们认为，提供这些免费服务有助于美国关于鼓励这些地区的信息自由流动和言论自由的外交政策。 我们认为，提供这些免费服务有助于美国关于鼓励这些市场的信息自由流动和言论自由的外交政策。 有关我们的方法和制裁如何影响全球软件合作的更多见解，请参阅我们[关于制裁的博客](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/)。 +由于我们的积极倡导以及与美国 监管机构的通力合作，GitHub 已获得美国 财政部外国资产控制办公室 (OFAC) 的许可，允许向伊朗的开发者恢复我们的云服务。 我们将继续与美国 监管机构合作，以获取类似的许可证，以便为叙利亚和克里米亚的开发者提供协作服务。 我们致力于倡导尽可能广泛的开发者访问权限，因为我们相信，为受制裁地区的开发者提供代码协作服务，可以使全球开发者社区变得更强大，促进人类进步，并支持美国 促进言论自由和信息自由流通的一贯外交政策。 有关我们为伊朗开发者获取的许可的信息，请阅读[博客文章](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran)。 虽然我们为了方便您而提供了以下信息，但您要最终负责确保对 GitHub 产品和服务的使用符合所有适用法律和法规，包括美国出口管制法律。 出口管制法律。 @@ -25,9 +25,9 @@ GitHub 的愿景是成为开发者合作的全球平台，不管开发者居住 用户负责确保他们在 GitHub.com 上开发和分享的内容符合美国出口管制法律，包括 EAR 和美国国际武器贩运条例（International Traffic in Arms Regulations，ITAR）。 出口管制法律，包括 EAR 和美国 国际武器贩运条例（International Traffic in Arms Regulations，ITAR）。 [GitHub.com](https://github.com) 上提供的云端托管服务不托管受 ITAR 约束的数据，目前也无法按国家或地区限制仓库访问。 如果寻求就 ITAR 或其他出口管制数据进行合作，我们建议您考虑 [GitHub Enterprise Server](https://enterprise.github.com) - GitHub 的本地服务。 -美国 美国贸易管制法律限制向某些国家和地区的用户提供 GitHub.com 服务。 根据美国财政部外国资产管制办公室（Office of Foreign Assets Controls，OFAC）颁发的授权，GitHub 可能允许受美国制裁的国家和地区的用户或常住居民 使用某些免费的 GitHub 服务， 以用于个人通信。 在这些国家和地区的个人或常住居民在访问 GitHub 时不得使用 IP 代理、VPN 或掩盖其位置的其他方法，并且只能将 GitHub.com 用于非商业个人通信。 +GitHub 现在获得了 OFAC 的许可，可以为位于或居住在伊朗的开发者提供云服务。 这包括为个人和组织提供的一切免费和有偿的公共和私人服务。 -根据美国及其他适用法律，特别指定国民 (SDN) 及其他被拒绝或被阻止的当事方 不得访问或使用GitHub.com。 此外，用户不得为包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 此外，GitHub.com 不得用于适用的出口管制法律所禁止的目的，包括 [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) 中所述的被禁止最终用途。 +特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub.com。 此外，用户不得为包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 此外，GitHub.com 不得用于适用的出口管制法律所禁止的目的，包括 [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) 中所述的被禁止最终用途。 #### GitHub Enterprise Server @@ -41,7 +41,7 @@ GitHub Enterprise Server 不能出售、出口或再出口到 EAR 的补充编 #### 美国政府对哪些国家和地区 实行制裁？ -克里米亚、古巴、伊朗、朝鲜和叙利亚。 +克里米亚、古巴、伊朗、朝鲜和叙利亚。 但是，就伊朗而言，GitHub 现在已获得美国 财政部外国资产控制办公室 (OFAC) 的许可，可为位于该国或居住在该国的开发者提供云服务。 #### GitHub 如何确保不在受制裁国家及地区生活和/或与受制裁国家及地区有专业联系的民间团体仍然能够访问或上诉？ @@ -55,23 +55,23 @@ GitHub Enterprise Server 不能出售、出口或再出口到 EAR 的补充编 #### 什么可用和不可用？ -GitHub 承诺继续向受美国制裁地区拥有个人和组织帐户的开发者免费提供公共仓库服务。 包括有限制地访问免费服务，例如用于开源项目（和相关公共页面）的公共仓库、公共Gist 以及分配的免费操作分钟数，但只能用于个人通信，而不得用于商业目的。 +GitHub 现在获得了 OFAC 的许可，可以向位于或居住在美国制裁国家——伊朗的开发者提供云服务。 该许可为个人和组织提供的一切免费和有偿的公共和私人服务。 但是，特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 -但是，由于美国 Due to U.S. trade controls law restrictions, GitHub is unable to provide private repository services and paid services to accounts in U.S. sanctioned regions. GitHub has preserved, however, access to free public repository services. 请阅读 [GitHub 和贸易管制](https://help.github.com/github/site-policy/github-and-trade-controls)了解更多信息。 制裁地区，例如朝鲜、伊朗、叙利亚和克里米亚。 该限制将暂停对私有仓库服务和付费服务的访问，例如免费或付费私有仓库、秘密 Gist、付费操作分钟数、赞助商和 GitHub Marketplace 服务的可用性。 +GitHub 承诺继续向受美国制裁地区拥有个人和组织帐户的开发者免费提供公共仓库服务。 包括有限制地访问免费服务，例如用于开源项目（和相关公共页面）的公共仓库、公共Gist 以及分配的免费操作分钟数，但只能用于个人通信，而不得用于商业目的。 -对于受制裁地区付费的组织级帐户，用户能够有限制地访问其公共仓库，这些仓库已降级为存档的只读仓库。 但是，对于受制裁地区的免费组织级帐户，用户仍然可以完全访问用于开源项目（和相关公共页面）的免费公共仓库、公共 Gist 和分配的免费操作分钟数。 +对于这些受制裁地区的付费组织级帐户，用户对其公共仓库的访问有限，这些仓库已降级为存档的只读仓库。 但是，对于这些受制裁地区的免费组织级帐户，用户仍然可以完全访问用于开源项目（和相关公共页面）的免费公共仓库、公共 Gist 和分配的免费操作分钟数。 -GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. 监管机构提倡让受制裁地区的开发者尽可能获得免费代码协作服务，包括访问免费私有仓库。 我们认为，提供这些免费服务有助于美国关于鼓励这些地区的信息自由流动和言论自由的外交政策。 关于鼓励这些市场的信息自由流动和言论自由的外交政策。 +GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. 监管机构提倡让受制裁地区的开发者尽可能获得代码协作服务，例如 Syria 和 Crimea，包括访问私有仓库。 我们相信，提供这些服务可以促进人类进步、国际交流和美国一贯的 促进言论自由和信息自由流通的一贯外交政策。 #### 如何定义这些特定用户？ -如果 GitHub 确定用户或客户位于受美国贸易管制限制约束的区域，或用户受到美国经济制裁的限制，则关联帐户需遵守这些法律要求。 贸易管制限制约束的区域，或用户受到美国 经济制裁的限制，则关联帐户需遵守这些法律要求。 为执行这些法律限制而确定用户和客户的位置时，从多个来源进行考虑，包括 IP 地址和付款记录。 国籍和族裔不用于标记适用于制裁限制的用户。 +如果 GitHub 确定用户或客户位于受美国贸易管制限制约束的区域，或用户受到美国经济制裁的限制，则关联帐户需遵守这些法律要求。 贸易管制限制约束的区域，或用户受到美国 经济制裁的限制， 则关联帐户需遵守这些法律要求。 为执行这些法律限制而确定用户和客户的位置时，从多个来源进行考虑，包括 IP 地址和付款记录。 国籍和族裔不用于标记适用于制裁限制的用户。 #### 组织帐户受到何种影响？ -如果组织的基地位于被制裁的地区或国家，或者组织的主要个人或成员显示与被制裁的地区或国家有充分的联系，或者该组织似乎受到美国 经济制裁的限制，则该组织帐户和关联的所有者帐户将受到限制。 +如果组织的基地位于 GitHub 尚未获得美国政府许可的被制裁地区或国家，或者组织的主要个人或成员显示与被制裁的地区或国家有充分的联系， 或者该组织似乎受到美国 经济制裁的限制，则该组织帐户和关联的所有者帐户将受到限制。 -该限制将暂停对私有仓库服务和付费服务的访问，例如免费或付费私有仓库、秘密 Gist、付费操作分钟数、赞助商和 GitHub Marketplace 服务的可用性。 对于与受制裁地区相关的付费组织级帐户，用户能够有限制地访问其公共仓库，这些仓库已降级为存档的只读仓库。 对于与受制裁地区相关的免费组织级帐户，用户仍然可以完全访问用于开源项目（和相关公共页面）的免费公共仓库、公共 Gist 和分配的免费操作分钟数。 +该限制将暂停对私有仓库服务和付费服务的访问，例如免费或付费私有仓库、秘密 Gist、付费操作分钟数、赞助商和 GitHub Marketplace 服务的可用性。 对于与此类受制裁地区相关的付费组织级帐户，用户对其公共仓库的访问有限，这些仓库已降级为存档的只读仓库。 对于与此类受制裁地区相关的免费组织级帐户，用户仍然可以完全访问用于开源项目（和相关公共页面）的免费公共仓库、公共 Gist 和分配的免费操作分钟数。 #### 是否可将受交易限制的用户私有仓库设为公共？ @@ -81,3 +81,16 @@ GitHub will continue advocating with U.S. regulators for the greatest possible a 遗憾的是，我们对法律的理解并不能让我们选择允许下载或删除私有仓库内容，除非得到美国政府的批准。 政府。 我们将向美国大力倡议 我们将向美国监管机构大力倡议让受贸易限制的用户有权保护其私有仓库的内容。 我们还将提倡向受制裁市场的开发人员提供更多的 GitHub 服务，并进一步强调代码协作在支持全球开发人员个人通信方面的重要性。 +#### 根据 GitHub 从 OFAC 获得的许可，将在伊朗提供哪些类型的帐户？ + +我们获得的许可包括为个人和组织提供一切免费和有偿的公共和私人服务。 + +例如，伊朗的开发者可以注册一个免费或专业计划供个人使用，伊朗的大学可设立一个组织帐户以支持学生协作。 + +特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 + +如果 GitHub 确定某人属于受限制类别（SDN、其他被阻止的当事方或某些政府官员），则他们的帐户将被标记，并且他们将无法使用任何 GitHub 功能。 如果他们认为自己被错误标记，他们有机会使用我们的[个人帐户申诉申请表](https://airtable.com/shrGBcceazKIoz6pY)向 GitHub 提供验证信息，对此类标记提出申诉。 如果 GitHub 收到足够的信息，核实此人不属于受美国限制的类别 经济制裁限制的地区，则会撤销该标记。 + +#### 伊朗 GitHub 用户能否在许可下使用付费服务？ + +根据我们从 OFAC 获得的许可，我们正在为伊朗用户恢复所有云服务，包括付费服务。 我们接受所有主要的信用卡，但是第三方为我们处理付款，因此付款受付款处理方的条款和条件的约束。 这些第三方可能规定阻止伊朗付款的限制。 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 0627e1c1ceb66..d8697b4fd2272 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 %}。 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 服务条款的公共内容。 +我们依靠社区成员传达期望、[仲裁](#what-if-something-or-someone-offends-you)他们的项目以及{% data variables.contact.report_abuse %}或{% data variables.contact.report_content %}。 通过概述我们期望社区内出现的情况，我们希望帮助您理解如何在 GitHub 上进行最佳的协作，以及哪种操作或内容可能违反我们的[服务条款](#legal-notices)，包括我们的[可接受使用政策](/github/site-policy/github-acceptable-use-policies)。 我们将调查任何滥用举报，并且可能在我们的网站上仲裁我们确定违反了 GitHub 服务条款的公共内容。 ### 建立强大的社区 @@ -47,25 +47,25 @@ 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 上发布。 在非常情况下， 如果我们认为可能存在真正的人身伤害风险或公共安全威胁，我们可能会向执法机构报告暴力威胁。 +- #### 暴力威胁 不得暴力威胁他人，也不得利用网站组织、宣传或煽动现实世界中的暴力或恐怖主义行为。 仔细考虑您使用的文字、发布的图像、编写的软件以及其他人会如何解读它们。 即使您只是开个玩笑，但别人不见得这样理解。 如果您认为别人*可能*会将您发布的内容解读为威胁或者煽动暴力或恐怖主义， 不要在 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. +- ### 破坏其他用户的体验 成为社区的一部分包括认识到您的行为如何影响他人，并与他人及其依赖的平台进行有意义和富有成效的互动。 不允许重复发布与主题无关的评论、开启空洞或无意义的议题或拉取请求，或者以不断破坏其他用户体验的方式使用任何其他平台功能等行为。 虽然我们鼓励维护人员根据个别情况调整自己的项目，但 GitHub 员工可能会对从事此类行为的帐户采取进一步的限制措施。 -- #### 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. 在视频游戏、新闻报道以及对历史事件的描述中通常可以包含暴力内容，但我们不允许不加选择地发布暴力内容，或者以其他用户很难避开的方式发布（例如头像或议题评论）。 在其他情况下发布明确警告或免责声明有助于用户就他们是否想要参与这类内容作出明智的决定。 +- #### 过激的暴力内容 不得在没有合理的上下文或警告的情况下发布暴力图像、文本或其他内容。 在视频游戏、新闻报道以及对历史事件的描述中通常可以包含暴力内容，但我们不允许不加选择地发布暴力内容，或者以其他用户很难避开的方式发布（例如头像或议题评论）。 在其他情况下发布明确警告或免责声明有助于用户就他们是否想要参与这类内容作出明智的决定。 -- #### 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 传递恶意的可执行文件）或攻击基础设施（例如，组织拒绝服务攻击或支配命令和控制服务器）。 但请注意，我们不禁止发布可用于开发恶意软件或漏洞利用程序的源代码，因为此类源代码的发布和分发具有教育价值，并且能够为安全社区带来净收益。 +- #### 主动恶意软件或漏洞利用程序 本社区不允许恶意利用社区的其他成员。 我们不允许任何人利用我们的平台传递漏洞利用程序（例如，利用 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 a616081ce70b0..370c87fee93b6 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 公司服务条款 -Version Effective Date: November 16, 2020 +版本生效日期：2020 年 11 月 16 日 本协议适用于以下 GitHub 产品（详细定义见下文，统称为**“产品”**）： - 服务； @@ -133,13 +133,13 @@ GitHub 在[企业服务等级协议](/github/site-policy/github-enterprise-servi 客户保留客户创建或拥有的客户内容的所有权。 客户承认：(a) 对客户内容负责，(b) 只会提供客户有权利发布的客户内容（包括第三方或用户生成的内容），以及 (c) 客户将完全遵守与客户发布的客户内容相关的任何第三方许可。 客户免费授予第 D.3 至 D.6 条所述的权利，用于这两条所述的目的，直到客户从 GitHub 服务器中删除客户内容，但公开发布以及外部用户已经复刻的内容除外，这些内容的有效期直到所有客户内容复刻从 GitHub 服务器中删除。 如果客户上传的客户内容具有已经向 GitHub 授予运行服务所需的许可，则无需其他许可。 #### 3. 向我们授予许可 -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 授予以无归属方式使用客户内容所需的权利，以及根据提供服务的需要对客户内容进行合理改编的权利。 +客户向 GitHub 授予存储、存档、解析和显示客户内容以及制作附带副本的权利，但仅限于提供服务的目的，包括逐步改进服务。 这些许可包括将客户内容复制到 GitHub 数据库和制作备份；向客户以及客户选择要向其显示内容的人员显示客户内容；将客户内容解析为搜索索引或在 GitHub 的服务器上分析；与客户选择要共享的外部用户共享客户内容；以及执行客户内容，例如音乐或视频等。 这些权利适用于公共和私有仓库。 此许可不授予 GitHub 出售客户内容的权利。 它也不授予 GitHub 出于提供服务之外的目的分发或使用客户内容的权利，但作为存档客户内容的权利的一部分，GitHub 可能允许我们的合作伙伴在与 GitHub Arctic Code Vault 和 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,13 +153,13 @@ Whenever Customer adds Content to a repository containing notice of a license, i GitHub 将客户私有仓库中的客户内容视为客户的机密信息。 GitHub 将根据本第 P 条对私有仓库的客户内容实施保护和严格保密。 #### 3. 访问 -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). +GitHub 工作人员只能在我们的[隐私声明](/github/site-policy/github-privacy-statement#repository-contents)所述的情况下访问客户的私有仓库。 客户可选择对其私有仓库启用其他访问权限。 例如，客户可向不同的 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. +GitHub 将提供有关我们访问私有仓库内容的通知，访问的目的无外乎[为了法律披露](/github/site-policy/github-privacy-statement#for-legal-disclosure)，为了履行我们的法律义务或遵循法律要求的其他约束，提供自动扫描，或者应对安全威胁或其他安全风险。 ### F. 知识产权通告 @@ -191,7 +191,7 @@ GitHub will provide notice regarding our access to private repository content, u #### 1. 定价；费用 -**付款条款** 我们的定价发布于 [github.com/price](https://github.com/pricing)（除非当事方另有协议并在订单中说明）。 客户同意以美元全额支付费用，预先付款没有任何扣减或折扣。 Dollars. 客户必须在 GitHub 发票日期三十 (30) 天内支付费用。 除本协定另有规定外，根据本协议应付的金额不可退款。 如果客户未及时支付任何费用，GitHub 有权寻求法律或公平裁决的任何行动，并且 (i) 以每月 1.0% 或法律允许的最高利率（取较小者）对逾期金额收取利息，并收取所有恢复费用，以及 (ii) 终止适用的订单或 SOW。 客户独自负责本协议造成或与之相关的所有税、费、关税和政府评估（基于 GitHub 净收入的税除外）。 +**付款条款** 我们的定价发布于 [github.com/price](https://github.com/pricing)（除非当事方另有协议并在订单中说明）。 客户同意以美元全额支付费用，预先付款没有任何扣减或折扣。 美元。 客户必须在 GitHub 发票日期三十 (30) 天内支付费用。 除本协定另有规定外，根据本协议应付的金额不可退款。 如果客户未及时支付任何费用，GitHub 有权寻求法律或公平裁决的任何行动，并且 (i) 以每月 1.0% 或法律允许的最高利率（取较小者）对逾期金额收取利息，并收取所有恢复费用，以及 (ii) 终止适用的订单或 SOW。 客户独自负责本协议造成或与之相关的所有税、费、关税和政府评估（基于 GitHub 净收入的税除外）。 **基于使用情况的计费** 一些服务功能根据使用情况计费。 这些服务功能的数量有限，可能包含在您的限期计划中，无需额外收费。 如果您选择购买超出计划所含数量的付费服务功能，则根据您上月的实际使用情况支付这些服务功能。 对于购买了付费功能的客户，将根据提前开具的发票每月定期收取付款。 详情请参阅 [GitHub 附加产品条款](/github/site-policy/github-additional-product-terms)。 @@ -273,12 +273,12 @@ _测试版预览。_客户可自行决定选择使用测试版预览。 测试 在客户申请专业服务后，GitHub 将提供详述该等专业服务的 SOW。 GitHub 将执行每个 SOW 中描述的专业服务。 GitHub 将控制专业服务执行的方式和途径，并保留确定分配人员的权利。 GitHub 可能使用第三方执行专业服务，但 GitHub 对他们的行为和疏漏负责。 客户承认并同意，GitHub 保留在执行专业服务时使用或开发的任何内容的权利、资格和利益，包括软件、工具、规格、想法、概念、发明、流程、技术和知识。 对于 GitHub 在履行专业服务时向客户提供的任何交付项，GitHub 授予客户非独占、不可转让、全球、免版税、有限期的许可，允许他们在本协议有效期内使用这些交付项，但只能用于与客户使用服务相关的用途。 ### R. 服务或条款的更改 -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 有权利独自裁量随时修订本协议，并在发生任何此类修正时更新本协议。 如果本协议发生重大变更，例如价格上涨，我们会在变更生效之前至少 30 天通知用户 - 在服务上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 客户在这 30 天后继续使用服务即构成对本协议修订的同意。 对于任何其他修改，客户继续使用服务即表示同意我们对本协议的修订。 客户在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看本协议的所有更改。 GitHub 通过更新和添加新功能来更改服务。 对于 GitHub 在履行专业服务时向客户提供的任何交付项，GitHub 授予客户非独占、不可转让、全球、免版税、有限期的许可，允许他们在本协议有效期内使用这些交付项，但只能用于与客户使用服务相关的用途。 ### S. 支持 -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. +GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对服务提供标准技术支持，不收取额外费用。 GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美国全国性假日）对软件提供标准技术支持，不收取额外费用。 标准支持只通过 GitHub 以基于 web 的支持单提供，支持请求必须从 GitHub 支持团队可与之交互的用户发起。 GitHub 按订单或 SOW 规定的支持级别、费用和订阅期为服务提供高级支持（根据 [GitHub 对 Enterprise Cloud 的高级支持](/articles/about-github-premium-support)条款）或专门的技术支持。 ### T. 其他 @@ -310,4 +310,4 @@ GitHub 如果因其合理控制力之外的特殊原因（包括天灾、自然 每一方都是关于本协议主题的独立缔约方。 本协议中的任何内容都不得视为或以任何方式构成在双方之间建立法律关联、伙伴关系、合资企业、雇用、代理、信托或其他类似关系，任一方不得以合同来约束另一方。 #### 10. 问题 -对服务条款有疑问吗？ [Contact us](https://github.com/contact/). +对服务条款有疑问吗？ [请联系我们](https://github.com/contact/)。 diff --git a/translations/zh-CN/content/github/site-policy/github-marketplace-developer-agreement.md b/translations/zh-CN/content/github/site-policy/github-marketplace-developer-agreement.md index 1e2cd74a254fb..3f1ce7bf0f0ab 100644 --- a/translations/zh-CN/content/github/site-policy/github-marketplace-developer-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-marketplace-developer-agreement.md @@ -8,7 +8,7 @@ versions: **参与 GITHUB 的 MARKETPLACE 计划必须遵守这些条款和条件（以下简称“协议”）。 注册参与 MARKETPLACE 计划或单击下面的“I ACCEPT（我接受）”，即表示您确认自己理解本协议，并接受其所有条款和条件。 如果您代表公司或其他法律实体签订本协议，则表示您拥有让该实体受本协议约束的法律权限，在这种情况下，“您”即表示您所代表的实体。** -Effective Date: January 1, 2021 +生效日期：2021 年 1 月 1 日。 ### 1. 定义 @@ -169,7 +169,7 @@ GitHub 可能：阻止该产品推介在 Marketplace 上展示；从 Marketplace **10.3** GitHub 在 (a) 您违反了本协议的任何规定或 (b) 法律要求 GitHub 终止协议时可随时终止本协议。 -**10.4** 开发者终止的影响。 在收到开发者的四十五 (45) 天提前书面终止通知后，将被禁止开发者通过 Marketplace 吸收新客户。 在 Marketplace 中终止并删除开发者产品时，将向您支付任何未付款项。 If termination is initiated as a result of a GitHub modification to these terms (Section 11), the terms in effect immediately prior to such modification shall govern for the duration of the 45-day notice period until the date of actual termination. +**10.4** 开发者终止的影响。 在收到开发者的四十五 (45) 天提前书面终止通知后，将被禁止开发者通过 Marketplace 吸收新客户。 在 Marketplace 中终止并删除开发者产品时，将向您支付任何未付款项。 如果终止是因 GitHub 修改这些条款（第 11 条）而发起的，则在此类修改之前有效的条款适用于 45 天通知期至实际终止之日的期间。 **10.5** 第 2、3、4、5、8、9 以及 第12-18 条规定的义务在本协议到期或终止后仍然有效。 diff --git a/translations/zh-CN/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-marketplace-terms-of-service.md index 5229beb21be8f..cc985cfe83509 100644 --- a/translations/zh-CN/content/github/site-policy/github-marketplace-terms-of-service.md +++ b/translations/zh-CN/content/github/site-policy/github-marketplace-terms-of-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' --- -欢迎使用 GitHub Marketplace ("Marketplace")！ 我们很高兴在这里与您邂逅。 在访问或使用 GitHub Marketplace 之前，请仔细阅读这些服务条款（“Marketplace 条款”）。 GitHub Marketplace is a platform that allows you to select developer apps or actions (for free or for a charge) that can be used with your GitHub.com account ("Developer Products"). Although offered by GitHub, Inc. ("GitHub", "we", "us"), Developer Products may be developed and maintained by either GitHub or by third-party software providers. Your selection or use of Developer Products is subject to these Marketplace Terms and any applicable fees, and may require you to agree to additional terms as provided by the third party licensor of that Developer Product (the "Product Provider"). +欢迎使用 GitHub Marketplace ("Marketplace")！ 我们很高兴在这里与您邂逅。 在访问或使用 GitHub Marketplace 之前，请仔细阅读这些服务条款（“Marketplace 条款”）。 GitHub Marketplace 是一个供您选择（免费或付费）可用于 GitHub.com 帐户的开发者应用程序或操作（“开发者产品”）的平台。 尽管开发者产品由 GitHub, Inc.（"GitHub"、“我们”）提供，但可能由 GitHub 或第三方软件提供商开发和维护。 选择或使用开发者产品需遵守这些 Marketplace 条款，需支付任何适用的费用，可能还需要遵守该开发者产品的第三方许可者（“产品提供者”）规定的其他条款。 使用 Marketplace，即表示您同意遵守这些 Marketplace 条款。 -Effective Date: November 20, 2020 +生效日期：2020 年 11 月 20 日 ### A. GitHub.com 的服务条款 @@ -50,11 +50,11 @@ Marketplace 由 GitHub 提供，受 ### E. 您的数据和 GitHub 隐私政策 -**Privacy.** When you select or use a Developer Product, GitHub may share certain Personal Information (as defined in the [GitHub Privacy Statement](/articles/github-privacy-statement/)) with the Product Provider (if any such Personal Information is received from you) in order to provide you with the Developer Product, regardless of your privacy settings. GitHub 分享信息的多少取决于您所选开发者产品的要求，最少会分享您的用户帐户名称、ID 和主电子邮件地址，最多会分享您仓库内容的访问权限，包括阅读和修改您私有数据的权限。 通过 OAuth 授予权限时，您可以查看开发者产品要求的权限范围，然后选择接受或拒绝。 +**隐私。**当您选择或使用开发者产品时，GitHub 必须与产品提供者分享某些个人信息（定义见 GitHub 隐私声明）（如果收到您的任何此类个人信息），以便为您提供开发者产品，无论您的隐私设置如何。 GitHub 分享信息的多少取决于您所选开发者产品的要求，最少会分享您的用户帐户名称、ID 和主电子邮件地址，最多会分享您仓库内容的访问权限，包括阅读和修改您私有数据的权限。 通过 OAuth 授予权限时，您可以查看开发者产品要求的权限范围，然后选择接受或拒绝。

            -If you cease using the Developer Product and revoke access through your account settings, the Product Provider will no longer be able to access your account. 产品提供者负责在其规定的时间内从其系统中删除您的个人信息。 请联系产品提供者以确保您的帐户以被正确终止。 +如果您停止使用开发者产品并通过帐户设置撤消访问权限，则产品提供者将无法再访问您的帐户。 产品提供者负责在其规定的时间内从其系统中删除您的个人信息。 请联系产品提供者以确保您的帐户以被正确终止。 -**Data Security and Privacy Disclaimer.** When you select or use a Developer Product, the security of the Developer Product and the custodianship of your data, including your Personal Information (if any), is the responsibility of the Product Provider. You are responsible for understanding the security and privacy considerations of the selection or use of the Developer Product for your own security and privacy risk and compliance considerations. +**数据安全和隐私免责声明。** 当您选择或使用开发者产品时， 开发者产品的安全性及其对您数据（包括您的个人信息，如果有）的保管是产品提供者的责任。 您有责任出于自己的安全性 、隐私风险和合规性考虑，了解选择或使用开发者产品的相关安全和隐私因素。 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 1cdcb8a6fa5bf..49785b1a4ba9e 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: December 19, 2020 +生效日期：2020 年 12 月 19 日 感谢您将自己的源代码、项目和个人信息交托给 GitHub Inc. （“GitHub”、“我们”）。 保管您的私人信息是一项重大责任，我们希望您了解我们的处理方式。 @@ -26,24 +26,24 @@ Effective date: December 19, 2020 ### 摘要 -| 节 | 说明 | -| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| [GitHub 收集哪些信息](#what-information-github-collects) | GitHub 直接从您的注册、付款、交易和用户个人资料中收集信息。 We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub 可能还会从第三方收集用户个人信息。 我们只收集极少量的必要个人信息，除非您自己选择提供更多信息。 | -| [GitHub_不_收集哪些信息](#what-information-github-does-not-collect) | 我们不会有意收集 13 岁以下儿童的信息，也不会收集[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)。 | -| [GitHub 如何使用您的信息](#how-github-uses-your-information) | 本节介绍我们使用个人信息的方式，包括为您提供服务、与您沟通、出于安全和合规目的以及改善我们的服务。 我们还介绍了在法律要求的情况下处理个人信息的法律依据。 | -| [我们如何分享所收集的信息](#how-we-share-the-information-we-collect) | 在以下情况下，我们可能会与第三方分享您的信息：经您同意、与我们的服务提供商分享、出于安全目的、为履行我们的法律义务，或者公司实体或业务单位的控制权发生变更或出售。 我们不会出售您的个人信息，也不会在 GitHub 上发布广告。 您可以查看可访问您信息的服务提供商列表。 | -| [其他重要信息](#other-important-information) | 我们针对 GitHub 上的仓库内容、公共信息和组织而提供的附加说明。 | -| [其他服务](#additional-services) | 我们提供有关其他服务产品的信息，包括第三方应用程序、GitHub Pages 和 GitHub 应用程序。 | -| [您如何访问和控制我们收集的信息](#how-you-can-access-and-control-the-information-we-collect) | 我们为您提供访问、更改或删除个人信息的途径。 | -| [我们使用 cookie 和跟踪技术](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. 我们提供了一个非常透明地说明此技术的网页。 请参阅本节了解更多信息。 | -| [GitHub 如何保护您的信息](#how-github-secures-your-information) | 我们采取所有合理必要的措施，保护 GitHub 上个人信息的机密性、完整性和可用性，并保护我们服务器的弹性。 | -| [GitHub 的全球隐私实践](#githubs-global-privacy-practices) | 我们为世界各地的所有用户提供同样的高标准隐私保护。 | -| [我们如何与您交流](#how-we-communicate-with-you) | 我们通过电子邮件与您通信。 您可以在帐户设置中或通过联系我们来控制我们与您联系的方式。 | -| [解决投诉](#resolving-complaints) | 万一我们无法快速彻底地解决隐私问题，我们提供一条解决争议的途径。 | -| [隐私声明的变更](#changes-to-our-privacy-statement) | 如果本隐私声明发生重大变更，我们会在任何此类变更生效之前 30 天通知您。 您也可以在我们的站点政策仓库中跟踪变更。 | -| [许可](#license) | 本隐私声明的许可采用[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则。 | -| [联系 GitHub](#contacting-github) | 如果您对我们的隐私声明有疑问，请随时联系我们。 | -| [翻译](#translations) | 我们提供本隐私声明的一些翻译版本的链接。 | +| 节 | 说明 | +| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub 收集哪些信息](#what-information-github-collects) | GitHub 直接从您的注册、付款、交易和用户个人资料中收集信息。 我们还自动从您的使用信息、cookie 和设备信息中收集，但在必要时会征得您的同意。 GitHub 可能还会从第三方收集用户个人信息。 我们只收集极少量的必要个人信息，除非您自己选择提供更多信息。 | +| [GitHub_不_收集哪些信息](#what-information-github-does-not-collect) | 我们不会有意收集 13 岁以下儿童的信息，也不会收集[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)。 | +| [GitHub 如何使用您的信息](#how-github-uses-your-information) | 本节介绍我们使用个人信息的方式，包括为您提供服务、与您沟通、出于安全和合规目的以及改善我们的服务。 我们还介绍了在法律要求的情况下处理个人信息的法律依据。 | +| [我们如何分享所收集的信息](#how-we-share-the-information-we-collect) | 在以下情况下，我们可能会与第三方分享您的信息：经您同意、与我们的服务提供商分享、出于安全目的、为履行我们的法律义务，或者公司实体或业务单位的控制权发生变更或出售。 我们不会出售您的个人信息，也不会在 GitHub 上发布广告。 您可以查看可访问您信息的服务提供商列表。 | +| [其他重要信息](#other-important-information) | 我们针对 GitHub 上的仓库内容、公共信息和组织而提供的附加说明。 | +| [其他服务](#additional-services) | 我们提供有关其他服务产品的信息，包括第三方应用程序、GitHub Pages 和 GitHub 应用程序。 | +| [您如何访问和控制我们收集的信息](#how-you-can-access-and-control-the-information-we-collect) | 我们为您提供访问、更改或删除个人信息的途径。 | +| [我们使用 cookie 和跟踪技术](#our-use-of-cookies-and-tracking) | 我们只是使用绝对必要的 cookie 来提供、保障和改进我们的服务。 我们提供了一个非常透明地说明此技术的网页。 请参阅本节了解更多信息。 | +| [GitHub 如何保护您的信息](#how-github-secures-your-information) | 我们采取所有合理必要的措施，保护 GitHub 上个人信息的机密性、完整性和可用性，并保护我们服务器的弹性。 | +| [GitHub 的全球隐私实践](#githubs-global-privacy-practices) | 我们为世界各地的所有用户提供同样的高标准隐私保护。 | +| [我们如何与您交流](#how-we-communicate-with-you) | 我们通过电子邮件与您通信。 您可以在帐户设置中或通过联系我们来控制我们与您联系的方式。 | +| [解决投诉](#resolving-complaints) | 万一我们无法快速彻底地解决隐私问题，我们提供一条解决争议的途径。 | +| [隐私声明的变更](#changes-to-our-privacy-statement) | 如果本隐私声明发生重大变更，我们会在任何此类变更生效之前 30 天通知您。 您也可以在我们的站点政策仓库中跟踪变更。 | +| [许可](#license) | 本隐私声明的许可采用[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则。 | +| [联系 GitHub](#contacting-github) | 如果您对我们的隐私声明有疑问，请随时联系我们。 | +| [翻译](#translations) | 我们提供本隐私声明的一些翻译版本的链接。 | ## GitHub 隐私声明 @@ -75,7 +75,7 @@ Effective date: December 19, 2020 如果您访问我们的服务或网站，我们将与大多数服务商一样自动收集一些基本信息，但在必要时会征得您的同意。 这包括有关您如何使用服务的信息，例如您查看的页面、推荐站点、您的 IP 地址和会话信息，以及每个请求的日期和时间。 这是我们针对网站的每个访客收集的信息，无论他们是否有帐户。 此类信息可能包括用户个人信息。 ##### Cookie -As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service. +如下所述，我们通过 cookie 自动收集信息（例如 cookie ID 和设置）以保持您的登录状态、记住您的首选项、识别您和您的设备以及分析您使用服务的情况 。 ##### 设备信息 我们可能会收集有关您设备的某些信息，例如其 IP 地址、浏览器或客户端应用程序信息、语言首选项、操作系统和应用程序版本、设备类型和 ID 以及设备型号和制造商。 此类信息可能包括用户个人信息。 @@ -152,25 +152,25 @@ GitHub 可能会从第三方收集用户个人信息。 例如，如果您报名 ### 仓库内容 -#### 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 +如果您的仓库是私有仓库，您可以控制对内容的访问。 如果其中包含用户个人信息或敏感个人信息，则 GitHub 只能根据本隐私声明访问该信息。 GitHub 工作人员[不得访问私有仓库内容](/github/site-policy/github-terms-of-service#e-private-repositories)，除非 +- 出于安全目的 +- 协助仓库所有者处理支持事项 +- 保持服务的完整性 +- 履行我们的法律义务 +- 我们有理由认为其内容违法，或 - 经您同意. -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). +不过，虽然我们一般不搜索您的仓库中的内容，但可能扫描我们的服务器和内容，以根据算法指纹技术检测某些令牌或安全签名、已知活动的恶意软件、已知的依赖项漏洞或其他已知违反我们服务条款的内容，例如暴力极端主义或恐怖主义内容或儿童剥削图片（统称为“自动扫描”）。 我们的服务条款提供了有关[私有仓库](/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). +请注意，您可以选择禁用对私有仓库的某些访问权限，它们是在为您提供服务的过程中默认启用的（例如，自动扫描需要启用依赖项图和 Dependabot 警报）。 -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. +GitHub 将提供有关我们访问私有仓库内容的通知，访问的目的无外乎[为了法律披露](/github/site-policy/github-privacy-statement#for-legal-disclosure)，为了履行我们的法律义务或遵循法律要求的其他约束，提供自动扫描，或者应对安全威胁或其他安全风险。 -#### 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. +如果您的仓库是公共仓库，则任何人都可以查看其内容。 如果您的公共仓库中含有用户个人信息、[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)或机密信息，例如电子邮件地址或密码，该信息可能会被搜索引擎索引或被第三方使用。 更多信息请参阅[公共仓库中的用户个人信息](/github/site-policy/github-privacy-statement#public-information-on-github)。 @@ -182,7 +182,7 @@ GitHub 的许多服务和功能都是面向公众的。 如果您的内容是面 与您的内容相关的用户个人信息可能被第三方收集在这些 GitHub 数据汇编中。 如果您不希望自己的用户个人信息出现在第三方的 GitHub 数据汇编中，请不要公开自己的用户个人信息，并确保在您的用户个人资料和 [Git 提交设置](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)中[将您的电子邮件地址配置为私密](https://github.com/settings/emails)。 在当前版本中，用户的电子邮件地址默认设置为私密，但旧版 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-acceptable-use-policies#5-information-usage-restrictions)和[隐私](/github/site-policy/github-acceptable-use-policies#6-privacy)的服务条款，并且只能出于我们用户授权的目的使用所收集的任何面向公众的用户个人信息。 例如，如果 GitHub 用户出于识别和归因的目的而公开电子邮件地址，请不要将该电子邮件地址用于向用户发送未经请求的电子邮件或出售用户个人信息（例如向招聘人员、猎头和职介所出售）或用于商业广告。 我们希望您合理地保护从 GitHub 收集的任何用户个人信息，并且必须及时回应 GitHub 或 GitHub 用户的投诉以及删除和“别碰”要求。 同样，GitHub 上项目包含的公开用户个人信息可能在协作过程中被收集。 如果您要针对 GitHub 上的任何用户个人信息问题提出投诉，请参阅我们的[解决投诉](/github/site-policy/github-privacy-statement#resolving-complaints)部分。 @@ -235,17 +235,17 @@ If you would like to compile GitHub data, you must comply with our Terms of Serv #### Cookie -GitHub only uses strictly necessary cookies. Cookie 是网站通常存储在访客的计算机硬盘或移动设备上的小型文本文件。 +GitHub 仅使用绝对必要的 Cookie。 Cookie 是网站通常存储在访客的计算机硬盘或移动设备上的小型文本文件。 -We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers. +我们仅使用 Cookie 来提供、保障和改进我们的服务。 例如，我们使用它们来保持您的登录状态、记住您的偏好、出于安全目的识别您的设备、分析您使用服务的情况、编译统计报告以及为 GitHub 的未来发展提供信息。 我们使用自己的 Cookie 进行分析，但不使用任何第三方分析服务提供商。 -By using our service, 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 our service. +使用我们的服务，即表示您同意我们将这些类型的 cookie 放在您的计算机或设备上。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用我们的服务。 我们提供了一个有关 [cookie 和跟踪技术](/github/site-policy/github-subprocessors-and-cookies)的网页，介绍我们设置的 cookie、对这些 cookie 的需求以及它们的类型（临时或永久）。 #### DNT -"[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. GitHub 响应浏览器的 DNT 信号，并遵循[关于响应 DNT 信号的 W3C 标准](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. 还有一些很适合阻止在线跟踪的应用程序，例如 [Privacy Badger](https://privacybadger.org/)。 +“[别跟踪](https://www.eff.org/issues/do-not-track)”(DNT) 是有一种隐私首选项，如果您不希望在线服务（特别是广告网络）通过第三方跟踪服务收集和分享有关您在线活动的某类信息，您可以在浏览器中设置该选项。 GitHub 响应浏览器的 DNT 信号，并遵循[关于响应 DNT 信号的 W3C 标准](https://www.w3.org/TR/tracking-dnt/)。 如果您要设置浏览器以传达不希望被跟踪的信号，请查看浏览器的文档以了解如何启用该信号。 还有一些很适合阻止在线跟踪的应用程序，例如 [Privacy Badger](https://privacybadger.org/)。 ### GitHub 如何保护您的信息 @@ -318,7 +318,7 @@ GitHub 处理美国境内外的个人信息，并依靠标准合同条款作为 ### 隐私声明的变更 -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. +GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 对于本隐私声明的其他更改，我们建议用户[关注](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)或经常查看我们的网站政策仓库。 ### 许可 diff --git a/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md b/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md index 12fb2225c8ac3..15c1a461f9f25 100644 --- a/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ GitHub 很荣幸看到众多开发者融入我们的平台。 我们受宠若惊 13. **专有权利** - 您同意，GitHub 及其许可人拥有以下内容的所有权利、所有权和权益：API、预发布材料以及所有其他 GitHub 产品和服务；有关其配置和组合的所有信息和数据；以及对上述任何内容的所有修改和派生作品。 You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. + 您同意，GitHub 及其许可人拥有以下内容的所有权利、所有权和权益：API、预发布材料以及所有其他 GitHub 产品和服务；有关其配置和组合的所有信息和数据；以及对上述任何内容的所有修改和派生作品。 您同意，不得删除、更改、覆盖或混淆我们在 API、预发布材料或任何其他 GitHub 产品和服务上放置或嵌入的任何版权或其他专有权声明。 14. **政府用户** diff --git a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md index 3e7c4454a96c8..41837df3596c5 100644 --- a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,73 +10,70 @@ versions: free-pro-team: '*' --- -Effective date: **December 30, 2020** +生效日期：**2021 年 1 月 6 日** -GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). +GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 为此，我们提供此页面，以详细介绍了我们的[子处理商](#github-subprocessors)，以及我们如何使用 [cookie](#cookies-on-github)。 ### GitHub 子处理商 我们与第三方子处理商（例如我们的供应商和服务提供商）分享您的信息时，我们仍对您的信息负责。 我们在引入新供应商时，会竭尽所能保持您的信任，并且要求所有供应商与我们签订数据保护协议，以约束他们对用户个人信息（定义见[隐私声明](/articles/github-privacy-statement/)）的处理。 -| 子处理商名称 | 处理说明 | 处理地点 | 公司地点 | -|:------------------ |:----------------------- |:---- |:---- | -| Automattic | 博客服务 | 美国 | 美国 | -| AWS Amazon | 数据托管 | 美国 | 美国 | -| Braintree (PayPal) | 订阅费用信用卡支付处理商 | 美国 | 美国 | -| Clearbit | 营销数据充实服务 | 美国 | 美国 | -| Discourse | 社区论坛软件提供商 | 美国 | 美国 | -| DiscoverOrg | 营销数据充实服务 | 美国 | 美国 | -| Eloqua | 营销活动自动化 | 美国 | 美国 | -| Google Apps | 公司内部基础设施 | 美国 | 美国 | -| Google Analytics | 网站分析和性能 | 美国 | 美国 | -| LinkedIn Navigator | Data enrichment service | 美国 | 美国 | -| Magic Robot | 活动报告（Salesforce 加载项） | 美国 | 美国 | -| MailChimp | 客户事件单邮件服务提供商 | 美国 | 美国 | -| Mailgun | 交易邮件服务提供商 | 美国 | 美国 | -| Microsoft | Microsoft 服务 | 美国 | 美国 | -| Monday.com | 团队协作和项目管理平台 | 美国 | 以色列 | -| Nexmo | 短信通知提供商 | 美国 | 美国 | -| Salesforce.com | 客户关系管理 | 美国 | 美国 | -| Sendgrid | 交易邮件服务提供商 | 美国 | 美国 | -| Sentry.io | 应用程序监控提供商 | 美国 | 美国 | -| Stripe | 支付服务提供商 | 美国 | 美国 | -| Twilio | 短信通知提供商 | 美国 | 美国 | -| Zendesk | 客户支持事件单系统 | 美国 | 美国 | -| Zuora | 公司计费系统 | 美国 | 美国 | +| 子处理商名称 | 处理说明 | 处理地点 | 公司地点 | +|:------------------ |:------------ |:---- |:---- | +| Automattic | 博客服务 | 美国 | 美国 | +| AWS Amazon | 数据托管 | 美国 | 美国 | +| Braintree (PayPal) | 订阅费用信用卡支付处理商 | 美国 | 美国 | +| Clearbit | 营销数据充实服务 | 美国 | 美国 | +| Discourse | 社区论坛软件提供商 | 美国 | 美国 | +| Eloqua | 营销活动自动化 | 美国 | 美国 | +| Google Apps | 公司内部基础设施 | 美国 | 美国 | +| Google Analytics | 网站分析和性能 | 美国 | 美国 | +| MailChimp | 客户事件单邮件服务提供商 | 美国 | 美国 | +| Mailgun | 交易邮件服务提供商 | 美国 | 美国 | +| Microsoft | Microsoft 服务 | 美国 | 美国 | +| Monday.com | 团队协作和项目管理平台 | 美国 | 以色列 | +| Nexmo | 短信通知提供商 | 美国 | 美国 | +| Salesforce.com | 客户关系管理 | 美国 | 美国 | +| Sendgrid | 交易邮件服务提供商 | 美国 | 美国 | +| Sentry.io | 应用程序监控提供商 | 美国 | 美国 | +| Stripe | 支付服务提供商 | 美国 | 美国 | +| Twilio | 短信通知提供商 | 美国 | 美国 | +| Zendesk | 客户支持事件单系统 | 美国 | 美国 | +| Zuora | 公司计费系统 | 美国 | 美国 | 在我们引入新的子处理商来处理用户个人信息、删除子处理商或更改使用子处理商的方式时，我们将更新本页面。 如果您对新的子处理商有疑问或疑虑，我们乐意提供帮助。 请通过 {% data variables.contact.contact_privacy %} 联系我们。 ### GitHub 上的 Cookie -GitHub uses 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. 为此，我们制作了本页面，详细介绍[我们的子处理商](#github-subprocessors)、我们如何使用 [cookie](#cookies-on-github)、在何处进行跟踪以及如何[在 GitHub 上执行跟踪](#tracking-on-github)。 +GitHub 使用 Cookie 来提供和保护我们的网站，并分析我们网站的使用情况，以便为您提供出色的用户体验。 为此，我们制作了本页面，详细介绍[我们的子处理商](#github-subprocessors)、我们如何使用 [cookie](#cookies-on-github)、在何处进行跟踪以及如何[在 GitHub 上执行跟踪](#tracking-on-github)。 -Since the number and names of cookies may change,the table below may be updated from time to time. +由于 Cookie 的数量和名称可能会发生变化，下表可能会不时更新。 -| Cookie 名称 | 原因 | 描述 | Expiration* | -|:--------- |:------------------------------------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- | -| GitHub | `app_manifest_token` | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。 | five minutes | -| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year | -| GitHub | `dotcom_user` | 此 cookie 用于向我们表明用户已登录。 | 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` | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。 | 会话 | -| GitHub | `gist_oauth_csrf` | 此 cookie 由 Gist 设置，以确保启动 oauth 流的用户与完成它的用户是同一个用户。 | deleted when oauth state is validated | -| GitHub | `gist_user_session` | 此 cookie 由 Gist 在单独主机上运行时使用。 | 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` | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | two weeks | -| GitHub | `__Host-user_session_same_site` | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | two weeks | -| GitHub | `logged_in` | 此 cookie 用于向我们表明用户已登录。 | one year | -| GitHub | `marketplace_repository_ids` | 此 cookie 用于您的登录。 | one hour | -| GitHub | `marketplace_suggested_target_id` | 此 cookie 用于您的登录。 | one hour | -| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year | -| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour | -| GitHub | `github.com/personal` | 此 cookie 用于 Google Analytics。 | two weeks | -| GitHub | `saml_csrf_token` | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。 | until user closes browser or completes authentication request | -| GitHub | `saml_csrf_token_legacy` | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。 | until user closes browser or completes authentication request | -| GitHub | `saml_return_to` | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。 | until user closes browser or completes authentication request | -| GitHub | `saml_return_to_legacy` | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。 | until user closes browser or completes authentication request | -| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | 会话 | -| GitHub | `user_session` | 此 cookie 用于您的登录。 | two weeks | +| Cookie 名称 | 原因 | 描述 | 过期* | +|:--------- |:------------------------------------ |:------------------------------------------------------- |:------------------ | +| GitHub | `app_manifest_token` | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。 | 5 分钟 | +| GitHub | `_device_id` | 出于安全考虑，此 Cookie 用于跟踪已识别的设备。 | 1 年 | +| GitHub | `dotcom_user` | 此 cookie 用于向我们表明用户已登录。 | 1 年 | +| GitHub | `_gh_ent` | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如客户在多步骤表单中处于哪一步。 | 两周 | +| GitHub | `_gh_sess` | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。 | 会话 | +| GitHub | `gist_oauth_csrf` | 此 cookie 由 Gist 设置，以确保启动 oauth 流的用户与完成它的用户是同一个用户。 | 验证 oauth 状态时删除 | +| GitHub | `gist_user_session` | 此 cookie 由 Gist 在单独主机上运行时使用。 | 两周 | +| GitHub | `has_recent_activity` | 此 Cookie 用于防止向最近访问过应用程序的用户显示安全插页。 | 1 小时 | +| GitHub | `__Host-gist_user_session_same_site` | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | 两周 | +| GitHub | `__Host-user_session_same_site` | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | 两周 | +| GitHub | `logged_in` | 此 cookie 用于向我们表明用户已登录。 | 1 年 | +| GitHub | `marketplace_repository_ids` | 此 cookie 用于您的登录。 | 1 小时 | +| GitHub | `marketplace_suggested_target_id` | 此 cookie 用于您的登录。 | 1 小时 | +| GitHub | `_octo` | 此 Cookie 用于会话管理，包括动态内容缓存、条件功能访问、支持请求元数据和第一方分析。 | 1 年 | +| GitHub | `org_transform_notice` | 此 Cookie 用于在组织转换期间提供通知。 | 1 小时 | +| GitHub | `github.com/personal` | 此 cookie 用于 Google Analytics。 | 两周 | +| GitHub | `saml_csrf_token` | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。 | 直到用户关闭浏览器或完成身份验证请求 | +| GitHub | `saml_csrf_token_legacy` | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。 | 直到用户关闭浏览器或完成身份验证请求 | +| GitHub | `saml_return_to` | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。 | 直到用户关闭浏览器或完成身份验证请求 | +| GitHub | `saml_return_to_legacy` | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。 | 直到用户关闭浏览器或完成身份验证请求 | +| GitHub | `tz` | 此 Cookie 允许我们根据您的时区自定义时间戳。 | 会话 | +| GitHub | `user_session` | 此 cookie 用于您的登录。 | 两周 | _*_ GitHub 出于以下原因在用户设备上放置以下 cookie： -(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. 例如，我们可能会嵌入来自其他网站的内容（例如视频），而该网站可能放置 cookie。 虽然我们尽可能减少这些第三方 cookie，但我们无法始终控制这些第三方内容放置哪些 cookie。 +(!) 请注意，虽然我们将第三方 Cookie 的使用限制在呈现外部内容时提供外部功能的需要，但我们网站上的某些页面可能会设置其他第三方 Cookie。 例如，我们可能会嵌入来自其他网站的内容（例如视频），而该网站可能放置 cookie。 虽然我们尽可能减少这些第三方 cookie，但我们无法始终控制这些第三方内容放置哪些 cookie。 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 26f4f2aed8b21..b23a805dae8b4 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,26 +14,26 @@ 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) | We may modify this agreement, but we will give you 30 days' notice of material changes. | -| [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) | 我们可能会修改本协议，但对于重大变更，我们会提前 30 天通知您。 | +| [R. 其他](#r-miscellaneous) | 关于法律详情，包括我们对法律的选择，请参阅本节内容。 | ### GitHub 服务条款 生效日期：2020 年 11 月 16 日 @@ -98,7 +98,7 @@ versions: 您在使用服务时可能创建或上传用户生成的内容。 对于您发布、上传、链接或通过服务提供的任何用户生成内容，无论内容的形式如何，您对其内容以及由此造成的任何伤害负有全部责任。 我们对用户生成内容的任何公开显示或滥用概不负责。 #### 2. GitHub 可删除内容 -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. +我们有权删除我们认为违反了任何法律或 [GitHub 条款或政策](/github/site-policy)的用户生成内容。 移动版 GitHub 上显示的用户生成内容可能受移动应用商店附加条款的约束。 #### 3. 内容所有权、发布权利和许可授予 您对您的内容保有所有权和责任。 如果您发布不是您自己创建或者您没有所有权的内容，则您同意对您发布的任何内容负责；您只会提交您有权发布的内容；并且您将完全遵守与您发布的内容有关的任何第三方许可。 @@ -106,9 +106,9 @@ We have the right to refuse or remove any User-Generated Content that, in our so 因为您对您的内容保有所有权和责任，所以我们需要授予我们——及其他 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. +我们需要合法的权利来为您服务，例如托管、发布以及分享您的内容。 您授权我们和我们的合法继承者存储、存档、解析和显示您的内容，以及制作附带副本，但限于提供服务的目的，包括逐步改进服务。 此许可包括如下权利：将您的内容复制到我们的数据库并制作备份；向您及其他用户显示；将其解析为搜索索引或在我们的服务器上分析；与其他用户分享；执行（如果您的内容是音乐或视频之类的内容）。 -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/). +此许可不授予 GitHub 出售您的内容的权利。 它也不授予 GitHub 出于提供服务之外的目的分发或使用您的内容的权利，但作为存档内容的权利的一部分，GitHub 可能允许我们的合作伙伴在与 [GitHub Arctic Code Vault 和 GitHub Archive Program](https://archiveprogram.github.com/) 相关联的公共仓库中存储和存档您的内容。 #### 5. 向其他用户授予许可 您公开发布的任何用户生成内容，包括议题、评论以及对其他用户仓库的贡献，都可供其他人查看。 设置公开显示您的仓库，即表示您同意允许他人查看和“复刻”您的仓库（这意味着他人可以从他们控制的仓库自行复制您仓库中的内容）。 @@ -116,7 +116,7 @@ This license does not grant GitHub the right to sell Your Content. It also does 如果您将页面和仓库设为公开显示，则表示您向每个用户授予非独占、全球许可，允许他们通过 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 @@ Whenever you add Content to a repository containing notice of a license, you lic 在适用法律不能强制执行本协议的范围内，您授权 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,14 +135,14 @@ Whenever you add Content to a repository containing notice of a license, you lic GitHub 将私有仓库的内容视为您的机密。 GitHub 将保护私有仓库的内容，防止受未授权的使用和访问，在披露时就像处理我们自己性质类似的机密信息一样，在任何情况下都不低于合理的谨慎程度。 #### 3. 访问 -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/site-policy/github-privacy-statement#repository-contents)所述的情况下访问您私有仓库的内容。 您可选择对您私有仓库启用其他访问权限。 例如： - 例如，您可向不同的 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. +GitHub 将提供有关我们访问私有仓库内容的通知，访问的目的无外乎[为了法律披露](/github/site-policy/github-privacy-statement#for-legal-disclosure)，为了履行我们的法律义务或遵循法律要求的其他约束，提供自动扫描，或者应对安全威胁或其他安全风险。 ### F. 版权侵权和 DMCA 政策 如果您认为我们网站上的内容侵犯了您的版权， 请按照我们的[数字千禧年版权法政策](/articles/dmca-takedown-policy/)联系我们。 如果您是版权所有者并且您认为 GitHub 上的内容侵犯了您的权利，请通过[我们便利的 DMCA 表](https://github.com/contact/dmca)联系我们，或发送电子邮件到 copyright@github.com。 发出虚假或无聊的撤销通知可能会产生法律后果。 在发送撤销请求之前，您必须考虑合法用途，如公平使用和许可使用。 @@ -215,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. 授权 同意这些条款即表示您许可我们从您备案的信用卡、PayPal 帐户或您授权给 GitHub 的其他已批准付款方式扣费。 @@ -285,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.* +**短版本：** *我们希望用户了解我们条款的重要变化，但有些更改并不是那么重要——我们不想每次修复错误时都打扰您。 因此，虽然我们可以随时修改本协议，但对于任何重大更改，我们都会通知用户，并给您时间进行调整。* -我们有权利独自裁量随时修订这些服务条款，并在发生任何此类修正时更新这些服务条款。 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)仓库中可查看这些条款的所有变更。 +我们有权利独自裁量随时修订这些服务条款，并在发生任何此类修正时更新这些服务条款。 如果本协议发生重大变更，例如价格上涨，我们会在变更生效之前至少 30 天通知用户 - 在我们网站上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 客户在这 30 天后继续使用服务即构成对本协议修订的同意。 对于任何其他修改，您继续使用网站即表示同意我们对这些服务条款的修订。 在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看这些条款的所有变更。 我们保留随时和不时修改或停用（临时或永久）网站或其任何部分的权利，可能通知，也可能不通知。 diff --git a/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index 98ab7d3d4674f..7d8ee0223cea2 100644 --- a/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/zh-CN/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -28,7 +28,7 @@ CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基 加州居民有权要求企业披露：在过去 12 个月内从他们那里收集的个人信息的类别和具体部分；此类个人信息收集来源的类别；收集或出售此类个人信息的业务或商业目的；以及企业与其分享个人信息的第三方类别。 -如果您要求企业披露所收集的有关您的个人信息类别和具体部分，您有权每年两次免费接收该披露信息。 该信息可通过邮寄或电子方式传递，如果以电子方式提供，应采用可移植且易于使用的格式（在技术上可行的范围内），以便加州居民能够相对容易地将该信息传输给其他实体。 You can use GitHub’s [User Migration API](/rest/reference/migrations#users) to access and download your data. 单击[此处](https://github.blog/2018-12-19-download-your-data/)了解更多信息。 +如果您要求企业披露所收集的有关您的个人信息类别和具体部分，您有权每年两次免费接收该披露信息。 该信息可通过邮寄或电子方式传递，如果以电子方式提供，应采用可移植且易于使用的格式（在技术上可行的范围内），以便加州居民能够相对容易地将该信息传输给其他实体。 您可以使用 GitHub 的[用户迁移 API](/rest/reference/migrations#users) 来访问和下载您的数据。 单击[此处](https://github.blog/2018-12-19-download-your-data/)了解更多信息。 ### 2. 了解您的个人信息是否出于商业目的而出售或披露以及接收方是谁的权利 diff --git a/translations/zh-CN/content/github/site-policy/index.md b/translations/zh-CN/content/github/site-policy/index.md index ec89c1fc750e6..8c4f73f9a3ee9 100644 --- a/translations/zh-CN/content/github/site-policy/index.md +++ b/translations/zh-CN/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index 52e15a6e1d6ad..1db59c500b25d 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -23,11 +23,11 @@ versions: {% note %} -**Note:** {% data reusables.sponsors.matching-fund-eligible %} +**注：**{% data reusables.sponsors.matching-fund-eligible %} {% endnote %} -{% data variables.product.prodname_matching_fund %} 旨在使 {% data variables.product.prodname_dotcom %} 社区开发开源软件的成员获益，宣传 [{% data variables.product.prodname_dotcom %} 社区指导方针](/github/site-policy/github-community-guidelines)。 Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. +{% data variables.product.prodname_matching_fund %} 旨在使 {% data variables.product.prodname_dotcom %} 社区开发开源软件的成员获益，宣传 [{% data variables.product.prodname_dotcom %} 社区指导方针](/github/site-policy/github-community-guidelines)。 对被赞助组织的付款和来自组织的付款均不符合 {% data variables.product.prodname_matching_fund %} 资格。 若要符合 {% data variables.product.prodname_matching_fund %} 的资格，您必须创建吸引社区长期维持您发展的个人资料。 有关创建有吸引力的个人资料的更多信息，请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)”。 diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 12392039c0b83..d80dc1956a117 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -22,7 +22,7 @@ versions: {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} -### Editing or retiring a tier +### 编辑或撤销等级 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index 5aa3adde70845..8cee9ea8b278f 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,11 @@ versions: free-pro-team: '*' --- -### About webhooks for events in your sponsored account +### 关于被赞助帐户中事件的 web 挂钩 -要监视赞助变更，例如在付款期结束时取消，您可以为被赞助的用户或组织帐户创建 web 挂钩。 When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. 更多信息请参阅 [`sponsorship` web 挂钩事件](/webhooks/event-payloads/#sponsorship)。 +要监视赞助变更，例如在付款期结束时取消，您可以为被赞助的用户或组织帐户创建 web 挂钩。 为被赞助帐户创建 web 挂钩后，在创建、编辑或删除赞助时您将会收到更新消息。 更多信息请参阅 [`sponsorship` web 挂钩事件](/webhooks/event-payloads/#sponsorship)。 -### Managing webhooks for events in your sponsored account +### 管理被赞助帐户中事件的 web 挂钩 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index dd150b65ed83e..a34e0ec2b6dfb 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -7,11 +7,11 @@ versions: free-pro-team: '*' --- -### About sponsorship updates +### 关于赞助升级 您的赞助者可选择是否接收有关您工作更新的电子邮件。 更多信息请参阅“[管理您的赞助](/articles/managing-your-sponsorship)”。 -For sponsored developer accounts, the update will come from your user account's primary email address. 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 +对于被赞助开发者帐户，更新将来自您用户帐户的主电子邮件地址。 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 对于被赞助的组织，更新将来自组织的 `noreply@github.com` 电子邮件地址。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 ### 联系赞助者 diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index bec0740f5b65b..0181afaa1912b 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,12 +10,12 @@ versions: ### 关于赞助者个人资料 -您的 {% data variables.product.prodname_sponsors %} 个人资料会告诉潜在的赞助者，他们为什么应该支持您。 People see your sponsor profile when they click the **Sponsor** button on your profile. 我们建议个人资料中包括以下信息。 +您的 {% data variables.product.prodname_sponsors %} 个人资料会告诉潜在的赞助者，他们为什么应该支持您。 用户单击您个人资料上的 **Sponsor（赞助）** 按钮，就会看到您的赞助个人资料。 我们建议个人资料中包括以下信息。 -- Open source work that you contribute to -- Why you are committed to open source development +- 您参与的开源工作 +- 您为什么致力于开源开发 -### Editing your profile details +### 编辑您的个人资料详细信息 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index 1ed66eadaf2f7..c0fcd11109618 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,7 +13,7 @@ versions: {% data reusables.sponsors.payout-info %} -### Viewing and editing payout information +### 查看和编辑付款信息 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index 58aa3533f6785..25bebf50404b1 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -1,17 +1,17 @@ --- title: 管理您的赞助目标 -intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. +intro: 您可以为被赞助开发者或被赞助组织帐户设置目标，以帮助社区了解赞助您的影响。 versions: free-pro-team: '*' --- ### 关于赞助目标 -You can set a funding goal for your sponsored account and share the goal with your community. 目标可帮助您了解您在开源社区中的影响，并扩大您在 {% data variables.product.prodname_sponsors %} 计划中的影响力。 +您可以为被赞助帐户设置一个融资目标，并与您的社区共享该目标。 目标可帮助您了解您在开源社区中的影响，并扩大您在 {% data variables.product.prodname_sponsors %} 计划中的影响力。 您的目标可设为您想要的赞助者数量或您希望每月赚取的金额。 每次只能设置一个目标。 一个目标达成后，可以设置另一个目标。 -### Setting a goal +### 设置目标 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 4ab3b130a17af..754758b8e2de9 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,6 +1,6 @@ --- title: 管理赞助 -intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. +intro: 您可以管理谁能看到您的赞助，以及您是否要接收来自被赞助帐户的电子邮件更新。 redirect_from: - /articles/managing-your-sponsorship versions: @@ -17,9 +17,9 @@ versions: {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Managing email updates for your sponsorship +### 管理赞助的电子邮件更新 -You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. +您可以选择您赞助的帐户能否以电子邮件向您发送其工作的更新。 被赞助帐户无法访问您的电子邮件地址。 {% data reusables.sponsors.manage-updates-for-orgs %} @@ -31,5 +31,5 @@ You can choose whether an account you sponsor can send you email updates about t ### 延伸阅读 -- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" -- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file +- "[升级赞助](/articles/upgrading-a-sponsorship)" +- "[降级赞助](/articles/downgrading-a-sponsorship)" \ No newline at end of file diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 4521f3c7efd0c..f8f6517e56262 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -7,32 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' -permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. +permissions: 任何人都可以代表自己的用户帐户赞助帐户。 组织所有者和帐单管理员可以代表其组织赞助帐户。 --- {% data reusables.sponsors.org-sponsors-release-phase %} -### About sponsorships +### 关于赞助 {% data reusables.sponsors.sponsorship-details %} -You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. -- Sustaining specific libraries that your organization's work depends on -- Investing in the ecosystem you rely on as a organization (such as blockchain) -- Developing brand awareness as an organization that values open source -- Thanking open source developers for building libraries that complement the product your organization offers +您可以代表您的用户帐户赞助一个帐户，以投资您个人受益的项目。 您可以代表您的组织赞助帐户，原因有很多。 +- 维护组织工作所依赖的特定库 +- 投资于作为一个组织所依赖的生态系统（如区块链） +- 作为重视开源的组织，培养品牌知名度 +- 感谢开源开发者构建库来补充您的组织提供的产品 -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +您可以使用信用卡赞助 {% data variables.product.product_name %} 上的帐户。 如果您的组织要开发票，请[联系我们](https://support.github.com/contact/org-sponsors-waitlist)。 {% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 -When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} +使用信用卡赞助帐户后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %} {% data reusables.sponsors.manage-updates-for-orgs %} -If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 +如果被赞助帐户撤销的等级，您将仍保留在该等级，直到您选择其他等级或取消订阅。 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 -If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, 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)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. +如果您要赞助的帐户在 {% data variables.product.prodname_sponsors %} 上还没有个人资料，您可以建议该帐户加入。 For more information, 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)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -42,15 +42,15 @@ If the account you want to sponsor does not have a profile on {% data variables. {% endnote %} -### Sponsoring an account +### 赞助帐户 -Before you can sponsor an account, you must have a verified email address. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。 +在赞助帐户之前，您必须拥有经过验证的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。 -1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. -1. Navigate to your sponsorship dashboard for the account. - - To sponsor a developer, under the developer's name, click **Sponsor**. ![赞助按钮](/assets/images/help/profile/sponsor-button.png) - - To sponsor an organization, to the right of the the organization's name, click **Sponsor**. ![赞助按钮](/assets/images/help/sponsors/sponsor-org-button.png) -1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) +1. 在 {% data variables.product.product_name %} 上，导航到您要赞助的用户或组织的个人资料。 +1. 导航到帐户的赞助仪表板。 + - 要赞助开发者，请在开发者的名称下单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/profile/sponsor-button.png) + - 要赞助组织，请在组织名称的右侧单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/sponsors/sponsor-org-button.png) +1. （可选），在页面的右侧，要代表您的组织赞助帐户，请使用 **Sponsor as（赞助者）**下拉菜单，然后单击组织。 ![选择将作为赞助者的帐户](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 659890d9029e2..dbede873c4389 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,7 +7,7 @@ versions: free-pro-team: '*' --- -### About sponsors and sponsorships +### 关于赞助者和赞助 您可以查看有关您当前和过去的赞助、从赞助者收到的付款以及事件（例如赞助取消和赞助等级变更）的分析。 您还可以查看新的赞助、赞助变更和赞助取消等活动。 您可以按日期过滤活动列表。 您还可以导出帐户的赞助数据以 CSV 或 JSON 格式查看。 @@ -19,13 +19,13 @@ versions: ### 查看最近的赞助活动 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. 在左侧边栏中，单击 **Activity（活动）**。 ![活动选项卡](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### 导出赞助数据 -If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. +您可以按月导出赞助事务。 {% data variables.product.company_short %} 将向您发送一封电子邮件，其中包含您所选月份所有赞助者的事务数据。 导出完成后，您可以导出另一个月的数据。 对于您的任何被赞助帐户，您每小时最多可以导出 10 组数据。 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. 单击 **Export all（全部导出）**。 ![全部导出按钮](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. 单击 {% octicon "download" aria-label="The download icon" %} **Export（导出）**。 ![导出按钮](/assets/images/help/sponsors/export-all.png) 1. 选择您想导出的数据的时间范围和格式，然后单击 **Start export（开始导出）**。 ![数据导出选项](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index 5a4a461c27f7a..79147698797d4 100644 --- a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -10,7 +10,7 @@ versions: ### 关于私有仓库的数据使用 -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. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。 +启用私有仓库的数据使用后，您可以访问依赖项图，从中可以跟踪仓库的依赖项，在 {% data variables.product.product_name %} 检测到漏洞依赖项时接收 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。 ### 启用或禁用数据使用功能 @@ -21,7 +21,7 @@ When you enable data use for your private repository, you'll be able to access t {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### 延伸阅读 diff --git a/translations/zh-CN/content/github/using-git/about-git-subtree-merges.md b/translations/zh-CN/content/github/using-git/about-git-subtree-merges.md index dd0cd1877db55..c8b18e11252e6 100644 --- a/translations/zh-CN/content/github/using-git/about-git-subtree-merges.md +++ b/translations/zh-CN/content/github/using-git/about-git-subtree-merges.md @@ -105,5 +105,5 @@ $ git pull -s subtree spoon-knife main ### 延伸阅读 -- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) +- [_Pro Git_ 书籍中的“高级合并”一章](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) - "[如何使用子树合并策略](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/zh-CN/content/github/using-git/adding-a-remote.md b/translations/zh-CN/content/github/using-git/adding-a-remote.md index cfa0d531bfce6..546b787a5e28b 100644 --- a/translations/zh-CN/content/github/using-git/adding-a-remote.md +++ b/translations/zh-CN/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ $ git remote -v 此错误消息表示您尝试添加的远程与本地仓库中的远程名称相同： ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/zh-CN/content/github/using-git/changing-a-remotes-url.md b/translations/zh-CN/content/github/using-git/changing-a-remotes-url.md index be4df2fee39d9..7db2a8a94f60f 100644 --- a/translations/zh-CN/content/github/using-git/changing-a-remotes-url.md +++ b/translations/zh-CN/content/github/using-git/changing-a-remotes-url.md @@ -53,7 +53,7 @@ git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY 下次对远程仓库执行 `git fetch`、`git pull` 或 `git push` 操作时，您需要提供 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. +您可以[使用凭据小助手](/github/using-git/caching-your-github-credentials-in-git)让 Git 在每次与 GitHub 会话时记住您的 GitHub 用户名和个人访问令牌。 ### 将远程 URL 从 HTTPS 切换到 SSH diff --git a/translations/zh-CN/content/github/using-git/getting-changes-from-a-remote-repository.md b/translations/zh-CN/content/github/using-git/getting-changes-from-a-remote-repository.md index 69e0a6f12f7c7..add913c8b6120 100644 --- a/translations/zh-CN/content/github/using-git/getting-changes-from-a-remote-repository.md +++ b/translations/zh-CN/content/github/using-git/getting-changes-from-a-remote-repository.md @@ -71,5 +71,5 @@ $ git pull remotename branchname ### 延伸阅读 -- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% if currentVersion == "free-pro-team@latest" %} +- [_Pro Git_ 手册中的“使用远程仓库”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% if currentVersion == "free-pro-team@latest" %} - “[连接问题故障排除](/articles/troubleshooting-connectivity-problems)”{% endif %} diff --git a/translations/zh-CN/content/github/using-git/pushing-commits-to-a-remote-repository.md b/translations/zh-CN/content/github/using-git/pushing-commits-to-a-remote-repository.md index 742f097df41e2..aa2a0d34bb762 100644 --- a/translations/zh-CN/content/github/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/zh-CN/content/github/using-git/pushing-commits-to-a-remote-repository.md @@ -13,7 +13,7 @@ versions: `git push` 命令使用两个参数： * 远程命令，如 `origin` -* A branch name, for example, `main` +* 分支名称，如 `main` 例如： @@ -21,7 +21,7 @@ versions: git push <REMOTENAME> <BRANCHNAME> ``` -As an example, you usually run `git push origin main` to push your local changes to your online repository. +例如，您通常运行 `git push origin main` 来推送本地更改到在线仓库。 ### 重命名分支 @@ -98,4 +98,4 @@ git fetch upstream - [`git remote` 手册页](https://git-scm.com/docs/git-remote.html) - "[Git 小抄](/articles/git-cheatsheet)" - "[Git 工作流程](/articles/git-workflows)" -- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" +- "[Git 手册](https://guides.github.com/introduction/git-handbook/)" diff --git a/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 7d1da8c393567..e1cad82d9d9b4 100644 --- a/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -34,7 +34,7 @@ versions: {% endtip %} {% endwindows %} - - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. + - `BRANCH-NAME`：当前项目的默认分支，例如 `main` 或 `gh-pages`。 ```shell $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME # Filter the specified branch in your directory and remove empty commits diff --git a/translations/zh-CN/content/github/using-git/updating-credentials-from-the-macos-keychain.md b/translations/zh-CN/content/github/using-git/updating-credentials-from-the-macos-keychain.md index 13868b3ea8304..dca71ee6a3f12 100644 --- a/translations/zh-CN/content/github/using-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/zh-CN/content/github/using-git/updating-credentials-from-the-macos-keychain.md @@ -1,6 +1,6 @@ --- title: 更新 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: '如果在 {% data variables.product.product_name %} 上更改您的{% if currentVersion != "github-ae@latest" %}用户名、密码或{% endif %}个人访问令牌，您需要在 "git-credit al-osxkeychain" 小助手中更新您保存的凭据。' redirect_from: - /articles/updating-credentials-from-the-osx-keychain - 密钥链中的 GitHub 密码条目 @@ -21,7 +21,7 @@ versions: ### 通过命令行删除凭据 -Through the command line, you can use the credential helper directly to erase the keychain entry. +通过命令行，您可以使用凭据小助手直接擦除密钥链条目。 ```shell $ git credential-osxkeychain erase @@ -30,7 +30,7 @@ protocol=https > [Press Return] ``` -如果成功，则不会打印出任何内容。 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. +如果成功，则不会打印出任何内容。 要测试其是否有效，请尝试并克隆 {% data variables.product.product_location %} 仓库。 如果提示您输入密码，则该密钥链条目已删除。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/zh-CN/content/github/using-git/using-git-rebase-on-the-command-line.md index c36ecb5365bde..415fd65df9e28 100644 --- a/translations/zh-CN/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/zh-CN/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,7 +124,11 @@ i cant' typ goods 由于您已更改 Git 历史记录，因此通常的 `git push origin` **不起**作用。 您需要通过“强制推送”最新更改来修改命令： ```shell -$ git push origin master --force +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes +$ git push origin main --force ``` {% warning %} diff --git a/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md b/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md index 692e403766a2a..d4bf6abc49186 100644 --- a/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/zh-CN/content/github/using-git/which-remote-url-should-i-use.md @@ -16,7 +16,7 @@ versions: ### 使用 HTTPS URL 克隆 -The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. +`https://` 克隆 URL 在所有仓库中提供，与可见性无关。 即使您在防火墙或代理后面，`https://` 克隆 URL 也有效。 当您在命令行中使用 HTTPS URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，Git 将要求您输入 {% data variables.product.product_name %} 用户名和密码。 {% data reusables.user_settings.password-authentication-deprecation %} @@ -32,7 +32,7 @@ The `https://` clone URLs are available on all repositories, regardless of visib {% endtip %} - {% if currentVersion == "free-pro-team@latest" %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. 更多信息请参阅“[通过 HTTPS 端口使用 SSH](/github/authenticating-to-github/using-ssh-over-the-https-port)”。{% endif %} + {% if currentVersion == "free-pro-team@latest" %}如果您希望使用 SSH，但不能通过端口 22 进行连接，则可通过 HTTPS 端口使用 SSH。 更多信息请参阅“[通过 HTTPS 端口使用 SSH](/github/authenticating-to-github/using-ssh-over-the-https-port)”。{% endif %} ### 使用 SSH URL 克隆 @@ -40,7 +40,7 @@ SSH URL 通过 SSH（一种安全协议）提供 Git 仓库的访问权限。 使用 SSH URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，系统将提示您输入密码，并且必须提供您的 SSH 密钥密码。 更多信息请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。 -{% if currentVersion == "free-pro-team@latest" %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”和“[授权 SSH 密码以用于 SAML 单点登录](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。{% endif %} +{% if currentVersion == "free-pro-team@latest" %}如果要访问使用 SAML 单点登录 (SSO) 的组织，您在进行身份验证之前必须授权 SSH 密钥以访问组织。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”和“[授权 SSH 密码以用于 SAML 单点登录](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。{% endif %} {% tip %} @@ -60,9 +60,9 @@ SSH URL 通过 SSH（一种安全协议）提供 Git 仓库的访问权限。 ### 使用 Subversion 克隆 您还可以使用 [Subversion](https://subversion.apache.org/) 客户端访问 {% data variables.product.prodname_dotcom %} 上的任何仓库。 Subversion 提供不同于 Git 的功能集。 更多信息请参阅“[Subversion 与 Git 之间有何差异？](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)” -You can also access repositories on +您还可以 -{% data variables.product.prodname_dotcom %} from Subversion clients. 更多信息请参阅“[Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”。 +从 Subversion 客户端访问 {% data variables.product.prodname_dotcom %} 上的仓库。 更多信息请参阅“[Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”。 {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/using-git/why-is-git-always-asking-for-my-password.md b/translations/zh-CN/content/github/using-git/why-is-git-always-asking-for-my-password.md index 04acd89bcfddd..919f03771822b 100644 --- a/translations/zh-CN/content/github/using-git/why-is-git-always-asking-for-my-password.md +++ b/translations/zh-CN/content/github/using-git/why-is-git-always-asking-for-my-password.md @@ -9,11 +9,11 @@ versions: github-ae: '*' --- -与使用 SSH 相比，使用 HTTPS 远程 URL 具有一些优势。 它比 SSH 更容易设置，通常通过严格的防火墙和代理进行工作。 However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository. +与使用 SSH 相比，使用 HTTPS 远程 URL 具有一些优势。 它比 SSH 更容易设置，通常通过严格的防火墙和代理进行工作。 但是，每次拉取或推送仓库时，它也会提示您输入 {% data variables.product.product_name %} 凭据。 {% data reusables.user_settings.password-authentication-deprecation %} -通过配置 Git 为您[缓存凭据](/github/using-git/caching-your-github-credentials-in-git)，您可以避免提示输入密码。 Once you've configured credential caching, Git automatically uses your cached personal access token when you pull or push a repository using HTTPS. +通过配置 Git 为您[缓存凭据](/github/using-git/caching-your-github-credentials-in-git)，您可以避免提示输入密码。 在配置凭据缓存后，当您使用 HTTPS 拉取或推送仓库时，Git 会自动使用缓存的个人访问令牌。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md index 7e62a9e8852f0..d9c4c720b817a 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md @@ -10,7 +10,7 @@ versions: github-ae: '*' --- -A repository's graphs give you information on {% if currentVersion == "free-pro-team@latest" %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. 如果是您维护仓库，您可以使用此数据更好地了解谁在使用您的仓库，以及为什么使用。 +仓库图提供有关 {% if currentVersion == "free-pro-team@latest" %} 流量、依赖于仓库的项目、{% endif %} 仓库贡献者和提交以及仓库复刻和网络的信息。 如果是您维护仓库，您可以使用此数据更好地了解谁在使用您的仓库，以及为什么使用。 {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md index a306cbf25f878..80c75d58229b1 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md @@ -1,6 +1,6 @@ --- title: 访问基本仓库数据 -intro: 'You can view basic information about a repository, such as the repository''s activity{% if currentVersion == "free-pro-team@latest" %}, traffic,{% endif %} and contribution activity.' +intro: '您可以查看仓库的基本信息，如仓库的活动{% if currentVersion == "free-pro-team@latest" %}、流量{% endif %} 和贡献活动。' mapTopic: true redirect_from: - /articles/accessing-basic-repository-data diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 1af04888d2d43..ca572243723d5 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -1,6 +1,6 @@ --- title: 探索仓库的依赖项 -intro: 'Using the dependency graph, you can see the packages your project depends on{% if currentVersion == "free-pro-team@latest" %} and the repositories that depend on it{% endif %}. 此外，您还可以看到在其依赖项中检测到的任何漏洞。' +intro: '使用依赖项图，您可以看到项目所依赖的包{% if currentVersion == "free-pro-team@latest" %}以及依赖它的仓库{% endif %}。 此外，您还可以看到在其依赖项中检测到的任何漏洞。' redirect_from: - /articles/listing-the-packages-that-a-repository-depends-on - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on @@ -16,7 +16,7 @@ versions: {% data reusables.repositories.enable-security-alerts %} -The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. 有关依赖项检测以及支持哪些生态系统的信息，请参阅“[关于依赖关系图”](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)。 +依赖项图显示仓库的依赖项{% if currentVersion == "free-pro-team@latest" %}和依赖关系{% endif %}。 有关依赖项检测以及支持哪些生态系统的信息，请参阅“[关于依赖关系图”](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} @@ -26,8 +26,8 @@ The dependency graph shows the dependencies{% if currentVersion == "free-pro-tea #### 依赖项视图 {% if currentVersion == "free-pro-team@latest" %} -依赖项按生态系统分组。 您可以展开依赖项以查看其依赖项。 For dependencies on public repositories hosted on -{% data variables.product.product_name %}, you can also click a dependency to view the repository. 私有仓库、私有包或无法识别文件上的依赖项以纯文本显示。 +依赖项按生态系统分组。 您可以展开依赖项以查看其依赖项。 对于托管在 +{% data variables.product.product_name %} 上的公共仓库中的依赖项，您也可以单击依赖来查看仓库。 私有仓库、私有包或无法识别文件上的依赖项以纯文本显示。 如果在仓库中检测到漏洞，这些漏洞将显示在视图顶部，供有权访问 {% data variables.product.prodname_dependabot_alerts %} 的用户查看。 @@ -36,7 +36,7 @@ The dependency graph shows the dependencies{% if currentVersion == "free-pro-tea {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} -在仓库的清单或锁定文件中指定的任何直接或间接依赖项按生态系统分组列出。 If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to +在仓库的清单或锁定文件中指定的任何直接或间接依赖项按生态系统分组列出。 如果在仓库中检测到漏洞，这些漏洞将显示在视图顶部，供有权访问的用户查看 {% data variables.product.prodname_dependabot_alerts %} 的通知。 ![依赖关系图](/assets/images/help/graphs/dependencies_graph_server.png) @@ -82,22 +82,22 @@ The dependency graph shows the dependencies{% if currentVersion == "free-pro-tea 您可以随时单击 Security & analysis（安全性和分析）选项卡上“Dependency Graph（依赖关系图）”旁边的 **Disable（禁用）**来禁用依赖关系图。 -### Changing the "Used by" package +### 更改“Used by（使用者）”包 -If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +如果启用了依赖项图，并且您的仓库包含已发布在受支持包生态系统上的包，则 {% data variables.product.prodname_dotcom %} 将在仓库的 **Code（代码）**选项卡的边栏中显示“Used by（使用者）”部分。 有关受支持包生态系统的更多信息，请参阅“[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 -The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects. +“Used by（使用者）”部分显示已发现对包的公开引用数量，并显示某些依赖项所有者的头像。 -!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png) +!["使用者"边栏部分](/assets/images/help/repository/used-by-section.png) -Clicking any item in this section takes you to the **Dependents** tab of the dependency graph. +单击此部分的任何项都会转到依赖项图的 **Dependents（依赖项）**选项卡。 -The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents. +“Used by（使用者）”部分表示仓库中的单个包。 如果您对包含多个包的仓库拥有管理员权限，您可以选择“Used by（使用者）”部分表示哪个包。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png) +4. 在“Configure security and analysis features（配置安全和分析功能）”下，单击“Used by counter（使用者计数）”部分中的下拉菜单并选择一个包。 ![选择"使用者"包](/assets/images/help/repository/choose-used-by-package.png) {% endif %} @@ -106,14 +106,14 @@ The "Used by" section represents a single package from the repository. If you ha 如果依赖关系图为空，则包含依赖项的文件可能有问题。 检查该文件以确保其格式对文件类型是正确的。 {% if currentVersion == "free-pro-team@latest" %} -如果文件格式正确，请检查文件大小。 The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a -{% data variables.product.prodname_enterprise %} user. 默认情况下，每个仓库最多处理 20 个清单或锁定文件，因此您可以在仓库子目录中将依赖项拆分为较小的文件。{% endif %} +如果文件格式正确，请检查文件大小。 依赖项图忽略单个清单并锁定超过 0.5 Mb 的文件，除非您是 +{% data variables.product.prodname_enterprise %} 用户。 默认情况下，每个仓库最多处理 20 个清单或锁定文件，因此您可以在仓库子目录中将依赖项拆分为较小的文件。{% endif %} 如果清单或锁定文件未获处理，其依赖项将从依赖关系图中省略，而不能接受有漏洞依赖项的检查。 ### 延伸阅读 -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} +- "[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} - "[查看组织的洞察](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" - "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/github/understanding-how-github-uses-and-protects-your-data)" diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md index d5dde27a993d8..f4842d4ad8f04 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md @@ -1,6 +1,6 @@ --- title: 了解仓库之间的连接 -intro: 'You can better understand the connections that exist between repositories by viewing a repository''s network{% if currentVersion == "free-pro-team@latest" %}, projects that depend on the repository,{% endif %} and its forks.' +intro: '通过查看仓库的网络{% if currentVersion == "free-pro-team@latest" %}、依赖该仓库的项目{% endif %} 及其复刻，您可以更好地了解仓库之间存在的连接。' mapTopic: true redirect_from: - /articles/understanding-connections-between-repositories diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index 765684457a419..1204537f1a996 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -1,6 +1,6 @@ --- title: 查看项目的贡献者 -intro: 'You can see who contributed commits to a repository{% if currentVersion == "free-pro-team@latest" %} and its dependencies{% endif %}.' +intro: '您可以查看向仓库{% if currentVersion == "free-pro-team@latest" %}及其依赖项{% endif %}贡献提交的人员。' redirect_from: - /articles/i-don-t-see-myself-in-the-contributions-graph/ - /articles/viewing-contribution-activity-in-a-repository/ @@ -14,7 +14,7 @@ versions: ### 关于贡献者 -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. 合并提交和空提交不会计为此图的贡献。 +您可以在贡献者图中查看对仓库贡献最大的 100 个贡献者{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}，包括提交合作作者{% endif %}。 合并提交和空提交不会计为此图的贡献。 {% if currentVersion == "free-pro-team@latest" %} 您还可以看到为项目的 Python 依赖项做出贡献的人员列表。 要访问此社区贡献者列表，请访问 `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`。 @@ -32,7 +32,7 @@ You can view the top 100 contributors to a repository{% if enterpriseServerVersi 如果您没有在仓库的贡献者图中显示，可能是因为： - 您并非前 100 名贡献者之一。 - 您的提交尚未合并到默认分支。 -- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. +- 您用于创作提交的电子邮件地址未连接到到您的 {% data variables.product.product_name %} 帐户。 {% tip %} @@ -42,4 +42,4 @@ You can view the top 100 contributors to a repository{% if enterpriseServerVersi 如果仓库中的所有提交均位于非默认分支中，则您不在贡献者图中。 例如，除非 `gh-pages` 是仓库的默认分支，否则 `gh-pages` 分支上的提交不包含在图中。 要将您的提交合并到默认分支，您可以创建拉取请求。 更多信息请参阅“[关于拉取请求](/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 %}." +如果您用于创作提交的电子邮件地址未连接到您的 {% data variables.product.product_name %} 帐户，则提交不会链接到您的帐户，并且您不会在贡献者图中显示。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}”和“[添加电子邮件地址到 {% data variables.product.product_name %} 帐户](/articles/adding-an-email-address-to-your-github-account){% endif %}”。 diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md index eba985831a8f4..925d881e4fbb2 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md @@ -1,7 +1,7 @@ --- title: 查看仓库的流量 intro: '具有仓库推送权限的任何人都可以查看其流量，包括完整克隆（不是提取）、过去 14 天的访问者、推荐站点以及流量图中的热门内容。' -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 %}' +product: '此仓库洞察图可用于具有 {% 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 == "free-pro-team@latest" %}更多信息请参阅“[关于仓库图](/articles/about-repository-graphs)”和“[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)。”{% endif %}' redirect_from: - /articles/viewing-traffic-to-a-repository versions: diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index 290e65f946588..352e1e62c0596 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -28,7 +28,7 @@ versions: Jekyll 是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持和简化的构建过程。 Jekyll 使用 Markdown 和 HTML 文件，并根据您选择的布局创建完整静态网站。 Jekyll 支持 Markdown 和 Lick，这是一种可在网站上加载动态内容的模板语言。 更多信息请参阅 [Jekyll](https://jekyllrb.com/)。 -Windows 并未正式支持 Jekyll。 For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. +Windows 并未正式支持 Jekyll。 更多信息请参阅 Jekyll 文档中的“[Windows 上的 Jekyll](http://jekyllrb.com/docs/windows/#installation)”。 我们建议将 Jekyll 用于 {% data variables.product.prodname_pages %}。 如果您喜欢，可以使用其他静态站点生成器或者在本地或其他服务器上自定义构建过程。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)”。 @@ -70,10 +70,10 @@ kramdown: {% data reusables.pages.add-jekyll-theme %} 更多信息请参阅 Jekyll 文档中的“[主题](https://jekyllrb.com/docs/themes/)”。 {% if currentVersion == "free-pro-team@latest" %} -You can add a supported theme to your site on -{% data variables.product.prodname_dotcom %}. 更多信息请参阅 {% data variables.product.prodname_pages %} 站点上“[支持的主题](https://pages.github.com/themes/)"和"[使用主题选择器添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)”。 +您可以将支持的主题添加到 +{% data variables.product.prodname_dotcom %} 上的站点。 更多信息请参阅 {% data variables.product.prodname_pages %} 站点上“[支持的主题](https://pages.github.com/themes/)"和"[使用主题选择器添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)”。 -To use any other open source Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, you can add the theme manually.{% else %} You can add a theme to your site manually.{% endif %} For more information, see{% if currentVersion == "free-pro-team@latest" %} [themes hosted on {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) and{% else %} "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and{% endif %} "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." +要使用 {% data variables.product.prodname_dotcom %} 上托管的任何其他开源 Jekyll 主题，您可以手动添加主题。{% else %} 您可以手动添加主题到站点。{% endif %} 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %} [{% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) 上托管的主题和 {% else %}{% data variables.product.prodname_pages %} 站点上 "[支持的主题](https://pages.github.com/themes/)"和{% endif %}“[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。 您可以通过编辑主题文件来覆盖任何主题的默认值。 更多信息请参阅您的主题文档和 Jekyll 文档中的“[覆盖主题默认值](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)“。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md index b40c4142d98ae..0add2b3391cf3 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub Pages -intro: '您可以使用 {% data variables.product.prodname_pages %} 直接从 {% data variables.product.product_name %} 仓库托管关于自己、您的组织或您的项目的站点。' +title: About GitHub Pages +intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a {% data variables.product.product_name %} repository.' redirect_from: - /articles/what-are-github-pages/ - /articles/what-is-github-pages/ @@ -16,48 +16,45 @@ versions: github-ae: '*' --- -### 关于 {% data variables.product.prodname_pages %} +### About {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} 是一项静态站点托管服务，它直接从 {% data variables.product.product_name %} 上的仓库获取 HTML、CSS 和 JavaScript 文件，（可选）通过构建过程运行文件，然后发布网站。 您可以在 [{% data variables.product.prodname_pages %} 示例集合](https://github.com/collections/github-pages-examples)中查看 {% data variables.product.prodname_pages %} 站点的示例。 +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). {% if currentVersion == "free-pro-team@latest" %} -You can host your site on -{% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. 更多信息请参阅“[对 {% data variables.product.prodname_pages %} 使用自定义域](/articles/using-a-custom-domain-with-github-pages)”。 +You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." {% endif %} -要开始使用，请参阅“[创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site)”。 +To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -Organization owners can disable the publication of -{% data variables.product.prodname_pages %} sites from the organization's repositories. 更多信息请参阅“[为组织禁止发布 {% data variables.product.prodname_pages %} 站点](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)”。 +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling 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 %} -### {% data variables.product.prodname_pages %} 站点的类型 +### Types of {% data variables.product.prodname_pages %} sites -有三种类型的 {% data variables.product.prodname_pages %} 站点：项目、用户和组织。 项目站点连接到 {% data variables.product.product_name %} 上托管的特定项目，例如 JavaScript 库或配方集合。 用户和组织站点连接到特定的 {% data variables.product.product_name %} 帐户。 +There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific {% data variables.product.product_name %} account. 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 %}. To publish an organization site, you must create a repository owned by an organization that's named {% 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 %} -项目站点的源文件与其项目存储在同一个仓库中。 {% 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 %} +The source files for a project site are stored in the same repository as their project. {% 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 %} {% if currentVersion == "free-pro-team@latest" %} -有关自定义域如何影响站点 URL 的更多详细，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)”。 +For more information about how custom domains affect the URL for your site, see "[About custom domains and {% 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 %}. 项目站点（无论是组织还是用户帐户拥有）没有限制。 +You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a user account, are unlimited. {% if enterpriseServerVersions contains currentVersion %} -The URL where your site is available depends on whether subdomain isolation is enabled for -{% data variables.product.product_location %}. +The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.product.product_location %}. -| 站点类型 | 子域隔离已启用 | 子域隔离已禁用 | -| ---- | ------- | ------- | -| | | | - User | +| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | +| ------------ | --------------------------- | ---------------------------- | +User | `http(s)://pages./` | `http(s):///pages/` | +Organization | `http(s)://pages./` | `http(s):///pages/` | +Project site owned by user account | `http(s)://pages.///` | `http(s):///pages///` +Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` -`http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Project site owned by user account | `http(s)://pages.///` | `http(s):///pages///` Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` - -更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)”或联系您的站点管理员。 +For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -68,86 +65,85 @@ The URL where your site is available depends on whether subdomain isolation is e {% endnote %} {% endif %} -### {% data variables.product.prodname_pages %} 站点的发布来源 +### Publishing sources for {% data variables.product.prodname_pages %} sites -{% data variables.product.prodname_pages %} 站点的发布来源是存储站点源文件的分支和文件夹。 +The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored. {% data reusables.pages.private_pages_are_public_warning %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -如果默认发布源在您的仓库中，{% data variables.product.prodname_pages %} 将自动从该源发布站点。 用户和组织站点的默认发布源是仓库默认分支的根目录。 项目站点的默认发布来源是 `gh-pages` 分支的根目录。 +If the default publishing source exists in your repository, {% data variables.product.prodname_pages %} will automatically publish a site from that source. The default publishing source for user and organization sites is the root of the default branch for the repository. The default publishing source for project sites is the root of the `gh-pages` branch. -如果要将站点的源文件保留在不同的位置，您可以更改站点的发布源。 您可以从仓库的任何分支发布站点 - 从该分支上仓库的根目录 `/` 或从该分支上的 `/docs` 文件夹发布。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 +If you want to keep the source files for your site in a different location, you can change the publishing source for your site. You can publish your site from any branch in the repository, either from the root of the repository on that branch, `/`, or from the `/docs` folder on that branch. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." -If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} +If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} {% else %} -用户和组织站点的默认发布来源是 `master` 分支。 如果用户和组织站点的仓库是 `master` 分支，您的站点将从该分支自动发布。 您无法为用户或组织站点选择不同的发布来源。 +The default publishing source for user and organization sites is the `master` branch. If the repository for your user or organization site has a `master` branch, your site will publish automatically from that branch. You cannot choose a different publishing source for user or organization sites. -项目站点的默认发布来源是 `gh-pages` 分支。 如果项目站点的仓库有 `gh-pages` 分支，您的站点将从该分支自动发布。 +The default publishing source for a project site is the `gh-pages` branch. If the repository for your project site has a `gh-pages` branch, your site will publish automatically from that branch. -项目站点也可以从 `master` 分支或 `master` 分支上的 `/docs` 文件夹发布。 要从这些来源之一发布站点，您必须配置不同的发布来源。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 +Project sites can also be published from the `master` branch or a `/docs` folder on the `master` branch. To publish your site from one of these sources, you must configure a different publishing source. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." - If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} + If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} - 您不能从任何其他分支发布项目站点，即使默认分支不是 `master` 或 `gh-pages`。 + You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. {% endif %} -### 静态站点生成器 +### Static site generators -{% data variables.product.prodname_pages %} 会发布您推送到仓库的任何静态文件。 您可以创建自己的静态文件或使用静态站点生成器为您构建站点。 您还可以在本地或其他服务器上自定义自己的构建过程。 我们建议使用 Jekyll，它是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持和简化的构建流程。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。 +{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -默认情况下，{% data variables.product.prodname_pages %} 将使用 Jekyll 来构建您的站点。 如果您想使用除 Jekyll 以外的静态站点生成器，通过在发布来源的根目录中创建一个名为 `.nojekyll` 的空文件来禁用 Jekyll 构建过程，然后按照静态站点生成器的说明在 本地构建站点。 +{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. -{% data variables.product.prodname_pages %} 不支持服务器端语言，例如 PHP、Ruby 或 Python。 +{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. -### 使用 {% data variables.product.prodname_pages %} 的指南 +### Guidelines for using {% data variables.product.prodname_pages %} {% if currentVersion == "free-pro-team@latest" %} -- 2016 年 6 月 15 日后创建并使用 `github.io` 域的 {% data variables.product.prodname_pages %} 站点通过 HTTPS 提供服务。 如果您在 2016 年 6 月 15 日之前创建站点，您可以为站点的流量启用 HTTPS 支持。 更多信息请参阅“[使用 HTTPS 保护 {% data variables.product.prodname_pages %}](/articles/securing-your-github-pages-site-with-https)”。 +- {% data variables.product.prodname_pages %} sites created after June 15, 2016 and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)." - {% data reusables.pages.no_sensitive_data_pages %} -- 您对 {% data variables.product.prodname_pages %} 的使用受 [GitHub 服务条款](/articles/github-terms-of-service/)的约束，包括禁止转售。 +- Your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/articles/github-terms-of-service/), including the prohibition on reselling. -#### 使用限制 +#### Usage limits {% endif %} -{% data variables.product.prodname_pages %} 站点受到以下使用限制的约束： +{% data variables.product.prodname_pages %} sites are subject to the following usage limits: - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - - 发布的 {% data variables.product.prodname_pages %} 站点不得超过 1 GB。 + - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. {% if currentVersion == "free-pro-team@latest" %} - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100GB per month. - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour. -如果您的站点超出这些使用配额，我们可能无法为您的站点提供服务；或者您可能收到来自 {% data variables.contact.contact_support %} 的礼貌电子邮件，建议降低站点对服务器影响的策略，包括将第三方内容分发网络 (CDN) 置于您的站点前，利用其他 {% data variables.product.prodname_dotcom %} 功能（如发行版）或转用可能更符合您需求的其他托管服务。 +If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. -#### 禁止使用 +#### Prohibited uses -{% data variables.product.prodname_pages %} 并非旨在用于或允许用作免费的 Web 托管服务来运行您的在线业务、电子商务站点或主要针对促进商业交易或提供商业软件即服务 (SaaS) 的任何其他网站。 +{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). -此外，{% data variables.product.prodname_pages %} 站点必须避免： +Additionally, {% data variables.product.prodname_pages %} sites must refrain from: - - 非法或者我们的[服务条款](/articles/github-terms-of-service/)或[社区指导方针](/articles/github-community-guidelines/)禁止的内容或活动 - - 暴力或有威胁的内容或活动 - - 过多的自动批量活动（例如，垃圾邮件） - - 危害 GitHub 用户或 GitHub 服务的活动 - - 快速致富计划 - - 性淫秽内容 - - 歪曲您的身份或站点目的的内容 -If you have questions about whether your use or intended use falls into these categories, please contact + - Content or activity that is illegal or otherwise prohibited by our [Terms of Service](/articles/github-terms-of-service/) or [Community Guidelines](/articles/github-community-guidelines/) + - Violent or threatening content or activity + - Excessive automated bulk activity (for example, spamming) + - Activity that compromises GitHub users or GitHub services + - Get-rich-quick schemes + - Sexually obscene content + - Content that misrepresents your identity or site purpose -{% data variables.contact.contact_support %}. +If you have questions about whether your use or intended use falls into these categories, please contact {% data variables.contact.contact_support %}. {% endif %} -### {% data variables.product.prodname_pages %} 上的 MIME 类型 +### MIME types on {% data variables.product.prodname_pages %} -MIME 类型是服务器发送到浏览器的标头，提供有关浏览器所请求文件性质和格式的信息。 {% data variables.product.prodname_pages %} 支持数千种文件扩展名中 750 多种 MIME 类型。 支持的 MIME 类型列表从 [mime-db project](https://github.com/jshttp/mime-db) 生成。 +A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). -虽然无法基于每个文件或每个仓库指定自定义 MIME 类型，但您可以添加或修改 MIME 类型以在 {% data variables.product.prodname_pages %} 上使用。 更多信息请参阅 [mime-db 参与指南](https://github.com/jshttp/mime-db#adding-custom-media-types)。 +While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). -### 延伸阅读 +### Further reading -- {% data variables.product.prodname_learning %} 上的 [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) +- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index ce355ff29c545..a6bf36fdf7fa6 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -14,7 +14,7 @@ versions: ### 关于 Jekyll 构建错误 -Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} +有时，在您推送更改到站点的发布源之后，{% data variables.product.prodname_pages %} 不会尝试构建您的站点。{% if currentVersion == "free-pro-team@latest" %} - 推送更改的人尚未验证他们的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。{% endif %} - 您使用部署密钥推送。 如果要自动推送到站点的仓库，您可以改为设置计算机用户。 更多信息请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys#machine-users)”。 - 您使用的是未配置为构建发布源的 CI 服务。 例如，Travis CI 不会构建 `gh-pages` 分支，除非您将该分支添加到安全列表。 更多信息请参阅 Travis CI 上的“[定制构建](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)”或者 CI 服务的文档。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 43ecb772d32b0..e9e69f89f7245 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -23,8 +23,8 @@ versions: 2. 导航到 *_config.yml*。 {% data reusables.repositories.edit-file %} 4. 为主题名称添加新行。 - - To use a supported theme, type `theme: THEME-NAME`, replacing _THEME-NAME_ with the name of the theme as shown in the README of the theme's repository. 有关支持的主题列表，请参阅 {% data variables.product.prodname_pages %} 网站上的“[支持的主题](https://pages.github.com/themes/)”。 ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png) - - 要使用托管于 {% data variables.product.prodname_dotcom %} 的任何其他 Jekyll 主题，请键入 `remote_theme: THEME-NAME`，将 THEME-NAME 替换为主题仓库的 README 中显示的主题名称。 ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png) + - 要使用支持的主题，请键入 `theme: THEME-NAME`，将 _THEME-NAME_ 替换为主题仓库的 README 中显示的主题名称。 有关支持的主题列表，请参阅 {% data variables.product.prodname_pages %} 网站上的“[支持的主题](https://pages.github.com/themes/)”。 ![配置文件中支持的主题](/assets/images/help/pages/add-theme-to-config-file.png) + - 要使用托管于 {% data variables.product.prodname_dotcom %} 的任何其他 Jekyll 主题，请键入 `remote_theme: THEME-NAME`，将 THEME-NAME 替换为主题仓库的 README 中显示的主题名称。 ![配置文件中不支持的主题](/assets/images/help/pages/add-remote-theme-to-config-file.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 9505554e5f4a5..dea4644b9035b 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ Jekyll 站点中内容的主要类型是页面和帖子。 页面是指与某个 {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +您的帖子现在应该显示在您的站点上！ 如果站点的基础 URL 是 `https://octocat.github.io`，则您的新帖子将位于 `https://octocat.github.io/YYYY/MM/DD/TITLE.html`。 + ### 后续步骤 {% data reusables.pages.add-jekyll-theme %}更多信息请参阅“[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index 757bacf9f0e56..c4baf3d7ae87f 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -1,6 +1,6 @@ --- title: 配置 GitHub Pages 站点的发布源 -intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@2.23" %} project{% endif %} site from a different branch or folder.' +intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 您也可以从不同的分支或文件夹发布{% if currentVersion ver_lt "enterprise-server@2.23" %}项目{% endif %}站点。' redirect_from: - /articles/configuring-a-publishing-source-for-github-pages/ - /articles/configuring-a-publishing-source-for-your-github-pages-site @@ -16,7 +16,7 @@ versions: ### 选择发布源 -Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@2.23" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@2.23" %} For example, before you can publish your project site from the `/docs` folder on the `master` branch of your repository, you or a collaborator must create a `/docs` folder on the default `master` branch of your repository.{% endif %} +在配置发布源之前，请确保要用作发布源的分支{% if currentVersion ver_lt "enterprise-server@2.23" %}或文件夹{% endif %}已存在于您的仓库中。{% if currentVersion ver_lt "enterprise-server@2.23" %}例如，从仓库的 `master` 分支上的 `/docs` 文件夹中发布项目站点之前，您或协作者必须在仓库的默认 `master` 分支上创建 `/docs` 文件夹。{% endif %} {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} @@ -26,7 +26,7 @@ Before you configure a publishing source, make sure the branch{% if currentVersi 5. 单击 **Save（保存）**。 ![用于保存对发布源设置的更改的按钮](/assets/images/help/pages/publishing-source-save.png) {% else %} 3. 在“ -{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select a publishing source. +{% data variables.product.prodname_pages %}”下，使用 **Source（源）**下拉菜单选择发布源。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) {% endif %} @@ -34,4 +34,4 @@ Before you configure a publishing source, make sure the branch{% if currentVersi {% data reusables.pages.admin-must-push %} -If you choose the `docs` folder on {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}any{% else %}the `master`{% endif %} branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)”。 +如果选择 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}任意{% else %} `master`{% endif %} 分支上的 `docs` 文件夹作为发布源，然后从仓库的该分支中删除了 `/docs` 文件夹，则您的站点将不会构建，并且您将收到提示缺失 `/docs` 文件夹的页面构建错误。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index abaf5c4c233d0..84434b743dd53 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -81,7 +81,7 @@ gem "github-pages", "~> VERSION", group: :jekyll_plugins ``` 10. 保存并关闭 Gemfile。 11. （可选）在本地测试您的站点。 更多信息请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。 -12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository. +12. 将您的 {% data variables.product.product_name %} 仓库添加为远程仓库，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ 替换为您企业的主机名，将 {% endif %} _USER_ 替换为拥有该仓库的帐户{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}，{% endif %}并将 _REPOSITORY_ 替换为仓库名称。 ```shell {% if currentVersion == "free-pro-team@latest" %} $ git remote add origin https://github.com/USER/REPOSITORY.git diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md index 04c0f96d38c62..45a9a6493cfba 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -43,9 +43,9 @@ versions: ### 后续步骤 -您可以通过创建更多新文件向网站添加更多页面。 每个文件都将在网站上与发布源相同的目录结构中。 For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md` 下。 +您可以通过创建更多新文件向网站添加更多页面。 每个文件都将在网站上与发布源相同的目录结构中。 例如，如果项目网站的发布源是 `gh-pages` 分支，并且您在 `gh-pages` 分支上创建了名为 `/about/contact-us.md` 的新文件，该文件将在 {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md` 下。 -您还可以添加主题以自定义网站的外观。 For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." +您还可以添加主题以自定义网站的外观。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %}“[使用主题选择器添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}”[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}”。 要更多地自定义您的站点，您可以使用 Jekyl - 内置 {% data variables.product.prodname_pages %} 支持的静态站点生成器。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md index 567524f080136..a487d506e0d57 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md @@ -40,7 +40,7 @@ versions: {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.save-custom-domain %} -5. 导航到您的 DNS 提供程序并创建 `CNAME` 记录，使子域指向您站点的默认域。 例如，如果要对您的用户站点使用子域 `www.example.com`，您可以创建 `CNAME` 记录，使 `www.example.com` 指向 `.github.io`。 如果要对您的组织站点使用子域 `www.anotherexample.com`，您可以创建 `CNAME` 记录，使 `www.anotherexample.com` 指向 `.github.io`。 The `CNAME` record should always point to `.github.io` or `.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +5. 导航到您的 DNS 提供程序并创建 `CNAME` 记录，使子域指向您站点的默认域。 例如，如果要对您的用户站点使用子域 `www.example.com`，您可以创建 `CNAME` 记录，使 `www.example.com` 指向 `.github.io`。 如果要对您的组织站点使用子域 `www.anotherexample.com`，您可以创建 `CNAME` 记录，使 `www.anotherexample.com` 指向 `.github.io`。 `CNAME` 记录应该始终指向 `.github.io` 或 `.github.io`，不包括仓库名称。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} {% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %} diff --git a/translations/zh-CN/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md index 6de6c448eff1e..010d305b5f36c 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -14,7 +14,7 @@ versions: 拥有仓库写入权限的人可为 {% data variables.product.prodname_pages %} 站点设置 Markdown 处理器。 -{% 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 %}. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/articles/about-writing-and-formatting-on-github)”。 +{% data variables.product.prodname_pages %} 支持两种 Markdown 处理器：[kramdown](http://kramdown.gettalong.org/) 和 {% data variables.product.prodname_dotcom %} 自己的扩展 [CommonMark](https://commonmark.org/) 处理器，后者用于在整个 {% data variables.product.product_name %} 中呈现 {% data variables.product.prodname_dotcom %} 风格的 Markdown。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/articles/about-writing-and-formatting-on-github)”。 您可以在任一处理器上使用 {% data variables.product.prodname_dotcom %} 风格的 Markdown，但只有我们的 CommonMark 处理器始终与您在 {% data variables.product.product_name %} 上看到的结果相匹配。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 89ee3bb8b807d..3e47fc7041b5b 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -36,7 +36,7 @@ versions: 如果在本地或 {% data variables.product.product_name %} 上构建 {% data variables.product.prodname_pages %} 站点时发生 Jekyll 错误，您可以使用错误消息排查故障。 有关构建错误以及如何查看它们的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 如果您收到一般错误消息，请检查常见问题。 -- 您使用的插件不受支持。 For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %} +- 您使用的插件不受支持。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll#plugins)”。{% if currentVersion == "free-pro-team@latest" %} - 您的仓库已超过我们的仓库大小限制。 更多信息请参阅“[我的磁盘配额是多少？](/articles/what-is-my-disk-quota)”{% endif %} - 您更改了 *_config.yml* 文件中的 `source` 设置。 {% data variables.product.prodname_pages %} 在构建过程中会覆盖此设置。 - 发布源中的文件名包含不受支持的冒号 (`:`)。 @@ -159,7 +159,7 @@ encoding: UTF-8 此错误意味着您的站点包含站点发布源中不存在的符号链接。 有关符号链接的更多信息，请参阅维基百科上的“[符号链接](https://en.wikipedia.org/wiki/Symbolic_link)”。 -要排除故障，请确定错误消息中的文件是否用于构建站点。 如果否，或者您不希望文件成为符号链接，请删除该文件。 如果符号链接文件是构建站点的必需项，请确保符号链接引用的文件或目录存在于站点的发布源中。 To include external assets, consider using {% if currentVersion == "free-pro-team@latest" %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %} +要排除故障，请确定错误消息中的文件是否用于构建站点。 如果否，或者您不希望文件成为符号链接，请删除该文件。 如果符号链接文件是构建站点的必需项，请确保符号链接引用的文件或目录存在于站点的发布源中。 要包括外部资产，请考虑使用 {% if currentVersion == "free-pro-team@latest" %}`git submodule` 或{% endif %}第三方包管理器，例如 [Bower](https://bower.io/)。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[将子模块用于 {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)。”{% endif %} ### 'for' 循环中的语法错误 @@ -183,6 +183,6 @@ encoding: UTF-8 此错误意味着您的代码包含无法识别的 Liquid 标记。 -要排除故障，请确保错误消息所指文件中的所有 Liquid 标记都与 Jekyll 的默认变量相匹配，并且标记名称没有拼写错误。 For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. +要排除故障，请确保错误消息所指文件中的所有 Liquid 标记都与 Jekyll 的默认变量相匹配，并且标记名称没有拼写错误。 有关默认变量列表，请参阅 Jekyll 文档中的“[变量](https://jekyllrb.com/docs/variables/)”。 不受支持的插件是无法识别标记的常见来源。 如果您通过在本地生成站点并将静态文件推送到 {% data variables.product.product_name %} 的方法在站点中使用不受支持的插件，请确保该插件未引入 Jekyll 默认变量中没有的标记。 有关受支持插件的列表，请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll#plugins)”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index 617653fc6ee07..d67f7dc2ee42a 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: 取消发布 GitHub Pages 站点 -intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available to {% if currentVersion == "free-pro-team@latest" %}the public{% else %}everyone using {% data variables.product.product_location %}{% endif %}.' +intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再对{% if currentVersion == "free-pro-team@latest" %}公众{% else %}所有 {% data variables.product.product_location %} 用户{% endif %}开放。' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ @@ -20,10 +20,10 @@ versions: {% data reusables.repositories.navigate-to-repo %} 2. 如果仓库中存在 `gh-pages` 分支，请删除 `gh-pages` 分支。 更多信息请参阅“[创建和删除仓库中的分支](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”。 3. 如果 `gh-pages` 分支是您的发布源， -{% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% if currentVersion == "free-pro-team@latest" %}跳到步骤 6{% else %}您的站点现已取消发布，您可以跳过其余步骤{% endif %}。 {% data reusables.repositories.sidebar-settings %} 5. 在“ -{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.** +{% data variables.product.prodname_pages %}”下，使用 **Source（源）**下拉菜单并选择 **None（无）**。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) {% data reusables.pages.update_your_dns_settings %} diff --git a/translations/zh-CN/content/github/working-with-github-support/about-github-support.md b/translations/zh-CN/content/github/working-with-github-support/about-github-support.md index fb8aa36f90334..a95091dd870f5 100644 --- a/translations/zh-CN/content/github/working-with-github-support/about-github-support.md +++ b/translations/zh-CN/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ versions: ### 联系 {% data variables.contact.github_support %} -{% data variables.product.prodname_free_user %} 用户和组织帐户可以使用 {% data variables.contact.community_support_forum %} 浏览主题、提出问题、分享解决方案以及直接与 {% data variables.contact.community_support %} 交互。 您还可以联系 {% data variables.contact.contact_support %} 以报告帐户、安全和滥用问题。 +您可以使用 {% data variables.contact.community_support_forum %} 浏览主题、提出问题、分享解决方案以及直接与 {% data variables.contact.community_support %} 交互。 -在付费帐户上，您可以联系 {% data variables.contact.contact_support %}，并根据您的计划，联系 {% data variables.contact.premium_support %} 或 {% data variables.contact.contact_ent_support %}。 有关联系 {% data variables.contact.premium_support %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.contact.premium_support %}](/articles/about-github-premium-support-for-github-enterprise-cloud)”或“[关于 {% data variables.product.prodname_ghe_server %} 的 {% data variables.contact.premium_support %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)”。 +要报告帐户、安全和滥用问题，或获得付费帐户的辅助支持，请访问 {% data variables.contact.contact_support_portal %}。 如果您是 {% data variables.product.prodname_ghe_server %} 的管理员，但在 {% data variables.product.prodname_dotcom_the_website %} 上没有用户帐户，请访问 {% data variables.contact.contact_enterprise_portal %}。 ### 授予 {% data variables.contact.github_support %} 临时访问私有仓库的权限 diff --git a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 4bc1811c828a8..aa5eb8a22083f 100644 --- a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -171,7 +171,7 @@ git commit ### 提及人员和团队 -您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 `@` 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 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 %}." +您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 `@` 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的更多信息，请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 `@github/support 您如何看待这些更新？` @@ -199,7 +199,7 @@ git commit ![内容附件](/assets/images/help/writing/content-attachment.png) -To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %} +要查看内容附件，您必须拥有使用仓库中安装的内容附件 API 的 {% data variables.product.prodname_github_app %}。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[在个人帐户中安装应用程序](/articles/installing-an-app-in-your-personal-account)”和“[在组织中安装应用程序](/articles/installing-an-app-in-your-organization)”。{% endif %} 内容附件不会显示在属于 markdown 链接的 URL 中。 @@ -215,7 +215,7 @@ To see content attachments, you must have a {% data variables.product.prodname_g 键入 `:` 将显示建议的表情符号列表。 列表将在您键入时进行过滤，因此一旦找到所需表情符号，请按 **Tab** 或 **Enter** 键以填写选中的结果。 -有关可用表情符号和代码的完整列表，请查看 [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com)。 +有关可用表情符号和代码的完整列表，请查看[表情符号备忘清单](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md)。 ### 段落 diff --git a/translations/zh-CN/content/github/writing-on-github/creating-gists.md b/translations/zh-CN/content/github/writing-on-github/creating-gists.md index be81e726ab29f..f6ca69abb93bd 100644 --- a/translations/zh-CN/content/github/writing-on-github/creating-gists.md +++ b/translations/zh-CN/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- -title: 创建 Gist -intro: '您可以创建两种 Gist：公开和机密 Gist。 如果您准备与世界分享您的想法，请创建公开 Gist，否则请创建机密 Gist。' +title: Creating gists +intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -12,69 +12,69 @@ versions: github-ae: '*' --- -### 关于 gists +### About gists -每个 gist 都是一个 Git 仓库，意即可以复刻和克隆。 如果您在创建 Gist 时登录了 {% data variables.product.product_name %}，则该 Gist 将与您的帐户相关联， 当您导航到 {% data variables.gists.gist_homepage %} 时，您会在 Gist 列表中看到它。 +Every gist is a Git repository, which means that it can be forked and cloned. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. -Gist 可为公共或秘密。 公共 gists 显示在 {% data variables.gists.discover_url %} 中，人们可在其中浏览新建的 gists。 它们也可供搜索，因此，如果您希望其他人查找和查看您的工作，便可使用公共 gists。 {% data reusables.gist.cannot-convert-public-gists-to-secret %} +Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. -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 %} 秘密 gists 不是私人的。 如果将秘密 gist 的 URL 发送给朋友，他们可以查看。 但是，如果您不认识的人发现该 URL，也能看到您的 gist。 如果需要让您的代码不被偷窥，可能要改为[创建私有仓库](/articles/creating-a-new-repository)。 +Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead. + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} -如果您的站点管理员禁用了私有模式，您也可以使用匿名 gists，可以是公共 gists 或秘密 gists。 +If your site administrator has disabled private mode, you can also use anonymous gists, which can be public or secret. {% data reusables.gist.anonymous-gists-cannot-be-deleted %} {% endif %} -您在以下情况下会收到通知： -- 您是新 gist 的作者。 -- 有人在 gist 中提及您。 -- 您单击任何 gist 顶部的 **Subscribe（订阅）**订阅了 gist。 +You'll receive a notification when: +- You are the author of a gist. +- Someone mentions you in a gist. +- You subscribe to a gist, by clicking **Subscribe** at the top any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -您可以在个人资料中置顶 Gist，使其他人更容易看到它们。 更多信息请参阅“[将项目嵌入到个人资料](/articles/pinning-items-to-your-profile)”。 +You can pin gists to your profile so other people can see them easily. For more information, see "[Pinning items to your profile](/articles/pinning-items-to-your-profile)." {% endif %} -您可以到 {% data variables.gists.gist_homepage %} 单击 **All Gists（所有 Gists）**发现其他人创建的 gists。 将会显示所有 gists 存储的页面，gist 按创建或更新时间显示。 您也可以通过 {% data variables.gists.gist_search_url %} 按语言搜索 gist。 Gist 搜索使用的搜索语法与[代码搜索](/articles/searching-code)相同。 +You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). -由于 gists 是 Git 仓库，因此您可以查看其整个提交历史记录，包括差异。 您也可以复刻或克隆 gists。 更多信息请参阅[“复刻和克隆 gists”](/articles/forking-and-cloning-gists)。 +Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists). -您可以单击 gist 顶部的 **Download ZIP（下载 ZIP）**按钮下载 gist 的 ZIP 文件。 您可以将 gist 嵌入到支持 Javascript 的任何文本字段中，如博文。 要获取嵌入的代码，请单击 gist 的**嵌入** URL 旁边的剪贴板图标。 要嵌入特定的 gist 文件，请使用 `?file=FILENAME` 附加**嵌入** URL。 +You can download a ZIP file of a gist by clicking the **Download ZIP** button at the top of the gist. You can embed a gist in any text field that supports Javascript, such as a blog post. To get the embed code, click the clipboard icon next to the **Embed** URL of a gist. To embed a specific gist file, append the **Embed** URL with `?file=FILENAME`. {% if currentVersion == "free-pro-team@latest" %} -Gist 支持地图 GeoJSON 文件。 这些地图显示在嵌入的 Gist 中，因此您可以轻松分享和嵌入地图。 更多信息请参阅“[{% data variables.product.product_name %} 上的地图 GeoJSON 文件](/articles/mapping-geojson-files-on-github)”。 +Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, so you can easily share and embed maps. For more information, see "[Mapping GeoJSON files on {% data variables.product.product_name %}](/articles/mapping-geojson-files-on-github)." {% endif %} -### 创建 Gist +### Creating a gist -也可以将桌面上的文本文件直接拖放到 Gist 编辑器中。 +You can also drag and drop a text file from your desktop directly into the gist editor. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} -您也可以使用 {% data variables.product.prodname_cli %} 创建 Gist。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh Gist 创建`](https://cli.github.com/manual/gh_gist_create)”。 +You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. {% endnote %} {% endif %} -1. 登录 {% data variables.product.product_name %}。 -2. 导航到 {% data variables.gists.gist_homepage %}。 -3. 键入 Gist 的说明（可选）和名称。 ![Gist 名称说明](/assets/images/help/gist/gist_name_description.png) - -4. 在 Gist 文本框中键入 Gist 的文本内容。 ![Gist 文本框](/assets/images/help/gist/gist_text_box.png) - -5. 执行以下操作之一： - - 要创建公开 gist，请单击 **Create public gist（创建公开 gist）**。 - - 要创建机密 gist，请单击 **Create public Gist（创建机密 Gist）**。 ![Gist 创建按钮](/assets/images/help/gist/gist_create_btn.png) +1. Sign in to {% data variables.product.product_name %}. +2. Navigate to your {% data variables.gists.gist_homepage %}. +3. Type an optional description and name for your gist. +![Gist name description](/assets/images/help/gist/gist_name_description.png) - {% note %} +4. Type the text of your gist into the gist text box. +![Gist text box](/assets/images/help/gist/gist_text_box.png) - **注：**{% data reusables.gist.cannot-convert-public-gists-to-secret %} +5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. +![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} - {% endnote %} +6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. + ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/zh-CN/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/zh-CN/content/github/writing-on-github/forking-and-cloning-gists.md index 5dbc9c5ba0e7b..14c8cb1e61ab0 100644 --- a/translations/zh-CN/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/zh-CN/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### 复刻 Gist -每个 Gist 都指示哪些复刻中有活动，使您更容易找到来自同事或陌生人的有趣更改。 +每个 Gist 都指示哪些复刻中有活动，使您更容易找到他人的有趣更改。 ![Gist 复刻](/assets/images/help/gist/gist_forks.png) diff --git a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md index 323b7488f831f..ecc48374f679c 100644 --- a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ GraphQL 查询仅返回您指定的数据。 要建立查询，必须指定[字 
            mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
            本示例中的输入对象为 `MutationNameInput`，有效负载对象为 `MutationNamePayload`。 diff --git a/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md index 798453372e2ca..8a77f0bb3084f 100644 --- a/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -22,7 +22,7 @@ versions: 您可以使用 `docker` 登录命令，通过 Docker 向 {% data variables.product.prodname_registry %} 验证。 -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} 必须在 {% data variables.product.product_location %} 的网站管理员为您的实例启用 Docker 支持和子域隔离后，您才可在 {% data variables.product.prodname_registry %} 上使用 Docker 注册表。 更多信息请参阅“[为企业管理 GitHub Packages](/enterprise/admin/packages)”。 @@ -30,8 +30,6 @@ versions: ### 向 {% data variables.product.prodname_registry %} 验证 -{% data reusables.package_registry.docker_registry_deprecation_status %} - {% data reusables.package_registry.authenticate-packages %} #### 使用个人访问令牌进行身份验证 @@ -51,11 +49,25 @@ versions: {% endif %} {% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} {% raw %} ```shell $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` {% endraw %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + {% endif %} 要使用此示例登录命令，请将 `USERNAME` 替换为您的 {% data variables.product.product_name %} 用户名{% if enterpriseServerVersions contains currentVersion %}，将 `HOSTNAME` 替换为 {% data variables.product.product_location %},{% endif %} 的 URL，并将 `~/TOKEN.txt` 替换为您用于 {% data variables.product.product_name %} 的个人访问令牌的文件路径。 @@ -94,9 +106,19 @@ versions: $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + {% endif %} ```shell 如果尚未为包构建 docker 映像，请构建映像，将 OWNER 替换为拥有仓库的用户或组织帐户的名称，将 REPOSITORY 替换为包含项目的仓库的名称，将 IMAGE_NAME 替换为包或映像的名称，将 VERSION 替换为构建时的包版本，将 PATH 替换为映像路径（如果映像未在当前工作目录中）。 ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + ```shell + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} 3. 您可能首次发布新的 Docker 映像并将其命名为 `monalisa`。 {% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* 使用 {% data variables.product.product_location %} 的主机名，{% endif %}以及映像的 *PATH*（如果不在当前工作目录中）。 @@ -105,9 +127,19 @@ versions: $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + ```shell + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} {% endif %} 4. 将映像发布到 {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ versions: $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ versions: #### 发布 Docker 映像的示例 -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +These examples assume your instance has subdomain isolation enabled. +{% endif %} + + +{% endif %} 您可以使用映像 ID 将 `monalisa` 映像的 1.0 版本发布到 `octocat/octo-app` 仓库。 @@ -197,9 +246,19 @@ $ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 0c3df3fcd3b6e..91e1531e08909 100644 --- a/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -79,10 +79,35 @@ versions: ### 发布包 -您可以使用 *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)”。 +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Publishing a package using a GitHub PAT as your API key + +If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +1. 创建一个新项目。 + ```shell + dotnet new console --name OctocatApp + ``` +2. 打包项目。 + ```shell + dotnet pack --configuration Release + ``` + +3. Publish the package using your PAT as the API key. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + ``` {% data reusables.package_registry.viewing-packages %} +{% endif %} + +#### Publishing a package using a *nuget.config* file + +发布时，您需要将 *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.authenticate-step %} 2. 创建一个新项目。 ```shell @@ -119,6 +144,8 @@ versions: dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` +{% data reusables.package_registry.viewing-packages %} + ### 将多个包发布到同一个仓库 要将多个包发布到同一个仓库，您可以在所有 *.csproj* 项目文件的 `RepositoryURL` 字段中包含相同的 {% data variables.product.prodname_dotcom %} 仓库 URL。 {% data variables.product.prodname_dotcom %} 根据该字段匹配仓库。 diff --git a/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md index baf86f41d851f..3dcf4e1a1332a 100644 --- a/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -209,6 +209,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### Using the official NPM registry + +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% endif %} + ### 延伸阅读 - “[删除包](/packages/publishing-and-managing-packages/deleting-a-package/)” diff --git a/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md index 5280f0a2bb084..efbc357dc8829 100644 --- a/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. 在 Dockerfile 中添加此行，将 `OWNER` 和 `REPO` 替换为您的详细信息： ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` 例如，如果您是用户 `monalisa` 并且拥有 `my-repo`，您会将此行添加到 Dockerfile： ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` 更多信息请参阅官方 Docker 文档中的“[LABEL](https://docs.docker.com/engine/reference/builder/#label)”，以及 `opencontainers/image-spec` 仓库中的“[预定义的标注键](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)”。 diff --git a/translations/zh-CN/content/packages/guides/using-github-packages-with-github-actions.md b/translations/zh-CN/content/packages/guides/using-github-packages-with-github-actions.md index bb4ed48ec696c..8f9a3f5c6d7a9 100644 --- a/translations/zh-CN/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/zh-CN/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,274 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{ ### Publishing a package using an action -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. +You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}: + +- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + The relevant settings are explained in the following table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
            + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. +
            + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + This job installs NPM and uses it to build the app. +
            + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + This job uses npm test to test the code. The needs: run-npm-build command makes this job dependent on the run-npm-build job. +
            + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Creates a new step called Build container image. This step runs as part of the build-and-push-image job. The needs: run-npm-test command makes this job dependent on the run-npm-test job. +
            + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Uses the Docker build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}. +
            + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. +
            + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. +
            + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Defines the password that is used to access {% data variables.product.prodname_registry %}. +
            + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. +
            + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Defines which repository will host the resulting package, and sets the name of the published package. Replace octo-image with the name you want for your package. +
            + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. +
            + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags the published package with the git ref. This can be the name of the branch used to create the package. +
            + +- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." + ### Installing a package using an action You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. diff --git a/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md index 5259887ea769a..eb4d90d700aba 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ versions: 您可以在一个仓库中托管多个包，并通过查看包的自述文件、下载统计、版本历史等，了解每个包的更多信息。 + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} 创建 {% data variables.product.prodname_actions %} 工作流程时，您可以使用 `GITHUB_TOKEN` 发布和安装 {% data variables.product.prodname_registry %} 中的包，无需存储和管理个人访问令牌。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)”。 {% data reusables.package_registry.container-registry-beta %} -![显示节点、RubyGems、Apache Maven、Gradle、Nuget 和容器注册表及其托管 Url 的图表](/assets/images/help/package-registry/packages-overview-diagram.png) +![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -143,7 +150,7 @@ versions: ### 管理包 -您可以在 {% data variables.product.product_name %} 上或使用 GraphQL API 删除私有包的版本。 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/graphql/guides/forming-calls-with-graphql)”。 +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/graphql/guides/forming-calls-with-graphql)”。 您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。 diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md index 29951886f2b8a..90eb03f35ec67 100644 --- a/translations/zh-CN/content/packages/quickstart.md +++ b/translations/zh-CN/content/packages/quickstart.md @@ -28,7 +28,7 @@ versions: ``` {% endraw %} 4. 初始化 npm 包。 在包初始化向导中，输入包名称：_`@YOUR-USERNAME/YOUR-REPOSITORY`_，如果您没有任何测试，请将测试脚本设置为 `exit 0`。 提交更改并推送以 -{% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_dotcom %} 上的站点。 {% raw %} ```shell $ npm init 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 b87c5e846510f..f26ce95e39c05 100644 --- a/translations/zh-CN/content/rest/guides/basics-of-authentication.md +++ b/translations/zh-CN/content/rest/guides/basics-of-authentication.md @@ -1,6 +1,6 @@ --- -title: 身份验证基础知识 -intro: 通过一些示例了解几种不同的身份验证方法。 +title: Basics of authentication +intro: Learn about the different ways to authenticate with some examples. redirect_from: - /guides/basics-of-authentication - /v3/guides/basics-of-authentication @@ -12,27 +12,36 @@ versions: --- -在本节中，我们将重点介绍身份验证的基础知识。 具体来说，我们将创建一个 Ruby 服务器（使用 [Sinatra][Sinatra])， 以几种不同的方式实现应用程序的 [web 流][webflow]。 +In this section, we're going to focus on the basics of authentication. Specifically, +we're going to create a Ruby server (using [Sinatra][Sinatra]) that implements +the [web flow][webflow] of an application in several different ways. {% tip %} -您可以[从平台样本仓库](https://github.com/github/platform-samples/tree/master/api/)下载此项目的完整源代码。 +You can download the complete source code for this project [from the platform-samples repo](https://github.com/github/platform-samples/tree/master/api/). {% endtip %} -### 注册您的应用程序 +### Registering your app -首先，您需要注册[您的应用程序][new oauth app]。 每个注册的 OAuth 应用程序都被分配了一个唯一的客户端 ID 和客户端密钥。 不应共享客户端密钥！ 也不应将该字符串检入您的仓库。 +First, you'll need to [register your application][new oauth app]. Every +registered OAuth application is assigned a unique Client ID and Client Secret. +The Client Secret should not be shared! That includes checking the string +into your repository. -您可以根据喜好填写任何信息，但**授权回调 URL** 除外。 这往往是设置应用程序中最重要的部分。 它是在身份验证成功后，{% data variables.product.product_name %} 将用户返回到的回调 URL。 +You can fill out every piece of information however you like, except the +**Authorization callback URL**. This is easily the most important piece to setting +up your application. It's the callback URL that {% data variables.product.product_name %} returns the user to after +successful authentication. -由于我们运行常规的 Sinatra 服务器，因此本地实例的位置设置为 `http://localhost:4567`。 回调 URL 应填写为 `http://localhost:4567/callback`。 +Since we're running a regular Sinatra server, the location of the local instance +is set to `http://localhost:4567`. Let's fill in the callback URL as `http://localhost:4567/callback`. -### 接受用户授权 +### Accepting user authorization {% data reusables.apps.deprecating_auth_with_query_parameters %} -现在开始设置我们简单的服务器。 创建一个名为 _server.rb_ 的文件并将以下代码粘贴到其中： +Now, let's start filling out our simple server. Create a file called _server.rb_ and paste this into it: ``` ruby require 'sinatra' @@ -47,12 +56,12 @@ get '/' do end ``` -客户端 ID 和客户端密钥[来自应用程序的配置页面][app settings]。 -{% if currentVersion == "free-pro-team@latest" %} **永远_不要_**将该事项的这些值存储在 -{% data variables.product.product_name %} 中或任何其他公共的地方。{% endif %} 建议将它们存储为 -[环境变量][about env vars]--我们正是这样做的。 +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 +[environment variables][about env vars]--which is exactly what we've done here. -接下来，在 _views/index.erb_ 中粘贴此内容： +Next, in _views/index.erb_, paste this content: ``` erb @@ -73,19 +82,26 @@ end ``` -（如果您不熟悉 Sinatra 的工作方式，建议您阅读 [ Sinatra 指南][Sinatra guide]）。 +(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra guide].) -另请注意，URL 使用 `scope` 查询参数来定义应用程序请求的[作用域][oauth scopes]。 对于我们的应用程序，我们请求 `user:email` 作用域来读取私密电子邮件地址。 +Also, notice that the URL uses the `scope` query parameter to define the +[scopes][oauth scopes] requested by the application. For our application, we're +requesting `user:email` scope for reading private email addresses. -将浏览器导航到 `http://localhost:4567`。 单击链接后，您应该会转到 {% data variables.product.product_name %}，并显示如下所示的对话框： ![GitHub 的 OAuth 提示](/assets/images/oauth_prompt.png) +Navigate your browser to `http://localhost:4567`. After clicking on the link, you +should be taken to {% data variables.product.product_name %}, and presented with a dialog that looks something like this: +![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png) -如果您觉得没问题，请单击 **Authorize App（授权应用程序）**。 哇！ Sinatra 弹出 `404` 错误。 是什么原因呢？ +If you trust yourself, click **Authorize App**. Wuh-oh! Sinatra spits out a +`404` error. What gives?! -哦，还记得我们指定了一个回调 URL 用于 `callback` 吗？ 我们没有为它提供路由，因此 {% data variables.product.product_name %} 在用户授权应用程序后不知道将他们带去哪里。 现在我们来解决这个问题！ +Well, remember when we specified a Callback URL to be `callback`? We didn't provide +a route for it, so {% data variables.product.product_name %} doesn't know where to drop the user after they authorize +the app. Let's fix that now! -#### 提供回调 +#### Providing a callback -在 _server.rb_ 中，添加路由以指定回调应执行的操作： +In _server.rb_, add a route to specify what the callback should do: ``` ruby get '/callback' do @@ -104,13 +120,18 @@ get '/callback' do end ``` -在应用程序身份验证成功后，{% data variables.product.product_name %} 将提供一个临时的 `code` 值。 您需要将此代码 `POST` 到 {% data variables.product.product_name %} 以换取 `access_token`。 为了简化我们的 GET 和 POST HTTP 请求，我们使用 [rest-client][REST Client]。 请注意，您可能永远不会通过 REST 访问 API。 对于更重要的应用程序，您可能需要使用[一个用您选择的语言编写的库][libraries]。 +After a successful app authentication, {% data variables.product.product_name %} provides a temporary `code` value. +You'll need to `POST` this code back to {% data variables.product.product_name %} in exchange for an `access_token`. +To simplify our GET and POST HTTP requests, we're using the [rest-client][REST Client]. +Note that you'll probably never access the API through REST. For a more serious +application, you should probably use [a library written in the language of your choice][libraries]. -#### 检查授予的作用域 +#### Checking granted scopes -用户可以通过直接更改 URL 来编辑您请求的范围。 这可以授予您的应用程序比您最初请求的更少的访问权限。 因此，在使用令牌发出任何请求之前，您应该检查用户为令牌授予的作用域。 有关请求和授予的范围的更多信息，请参阅“[OAuth 应用程序的范围](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)”。 +Users can edit the scopes you requested by directly changing the URL. This can grant your application less access than you originally asked for. Before making any requests with the token, check the scopes that were granted for the token by the user. For more information about requested and granted scopes, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)." -授予的作用域在交换令牌的响应中返回。 +The scopes that were granted are returned as a part of the response from +exchanging a token. ``` ruby get '/callback' do @@ -124,17 +145,34 @@ get '/callback' do end ``` -在我们的应用程序中，我们使用 `scopes.include?` 来检查我们是否被授予获取经验证用户的私密电子邮件地址所需的 `user:email` 作用域。 如果应用程序请求了其他作用域，我们也会进行相应检查。 +In our application, we're using `scopes.include?` to check if we were granted +the `user:email` scope needed for fetching the authenticated user's private +email addresses. Had the application asked for other scopes, we would have +checked for those as well. -此外，由于作用域之间存在层次关系，因此您应该检查您是否被授予了最低层级的必需作用域。 例如，如果应用程序请求了 `user` 作用域，但可能只被授予 `user:email` 作用域。 在这种情况下，应用程序并未获得它要求的作用域，不过被授予的作用域仍是足够的。 +Also, since there's a hierarchical relationship between scopes, you should +check that you were granted the lowest level of required scopes. For example, +if the application had asked for `user` scope, it might have been granted only +`user:email` scope. In that case, the application wouldn't have been granted +what it asked for, but the granted scopes would have still been sufficient. -仅在发出请求之前检查作用域是不够的，因为用户可能会在检查与实际请求之间的时间段更改作用域。 如果发生这种情况，您期望成功的 API 调用可能会以 `404` 或 `401` 状态失败，或者返回不同的信息子集。 +Checking for scopes only before making requests is not enough since it's possible +that users will change the scopes in between your check and the actual request. +In case that happens, API calls you expected to succeed might fail with a `404` +or `401` status, or return a different subset of information. -为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 除此之外，OAuth 应用程序 API 还提供 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[检查令牌的有效性\]\[/rest/reference/apps#check-a-token\]{% else %}\[检查令牌的有效性\]\[/rest/reference/apps#check-an-authorization\]{% endif %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 +To help you gracefully handle these situations, all API responses for requests +made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes]. +This header contains the list of scopes of the token that was used to make the +request. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +[check a token for validity][/rest/reference/apps#check-a-token]{% else %}[check a token for validity][/rest/reference/apps#check-an-authorization]{% endif %}. +Use this information to detect changes in token scopes, and inform your users of +changes in available application functionality. -#### 发出经过身份验证的请求 +#### Making authenticated requests -最后，使用此访问令牌，您将能够将在用户登录时发出经过身份验证的请求： +At last, with this access token, you'll be able to make authenticated requests as +the logged in user: ``` ruby # fetch user information @@ -151,7 +189,7 @@ end erb :basic, :locals => auth_result ``` -我们可以用我们的结果做任何我们想做的事。 在这种情况下，我们将它们直接转储到 _basic.erb_ 中： +We can do whatever we want with our results. In this case, we'll just dump them straight into _basic.erb_: ``` erb

            Hello, <%= login %>!

            @@ -170,19 +208,29 @@ erb :basic, :locals => auth_result

            ``` -### 实现“持久”身份验证 +### Implementing "persistent" authentication -如果我们要求用户每次访问网页时都必须登录应用程序，这将是一个非常糟糕的模式。 例如，尝试直接导航到 `http://localhost:4567/basic`。 您会收到一个错误。 +It'd be a pretty bad model if we required users to log into the app every single +time they needed to access the web page. For example, try navigating directly to +`http://localhost:4567/basic`. You'll get an error. -如果我们能够绕过整个 “点击这里”过程会怎么样：只需_记住_，只要用户登录到 -{% data variables.product.product_name %}，他们就应该能够访问此应用程序？ 不用担心， -因为_这正是我们要做的_。 +What if we could circumvent the entire +"click here" process, and just _remember_ that, as long as the user's logged into +{% data variables.product.product_name %}, they should be able to access this application? Hold on to your hat, +because _that's exactly what we're going to do_. -我们的上述小服务器相当简单。 为了加入一些智能身份验证功能，我们将切换到使用会话来存储令牌。 这将使身份验证对用户透明化。 +Our little server above is rather simple. In order to wedge in some intelligent +authentication, we're going to switch over to using sessions for storing tokens. +This will make authentication transparent to the user. -此外，由于我们在会话中保留作用域，因此我们需要处理用户在经过我们检查后更新作用域或撤消令牌的情况。 为此，我们将使用 `rescue` 块，并检查第一个 API 调用是否成功，以验证令牌是否仍然有效。 后，我们将检查 `X-OAuth-Scopes` 响应标头，以验证用户是否尚未撤消 `user:email` 作用域。 +Also, since we're persisting scopes within the session, we'll need to +handle cases when the user updates the scopes after we checked them, or revokes +the token. To do that, we'll use a `rescue` block and check that the first API +call succeeded, which verifies that the token is still valid. After that, we'll +check the `X-OAuth-Scopes` response header to verify that the user hasn't revoked +the `user:email` scope. -创建一个名为 _advanced_server.rb_ 的文件，并将以下行粘贴到其中： +Create a file called _advanced_server.rb_, and paste these lines into it: ``` ruby require 'sinatra' @@ -262,11 +310,15 @@ get '/callback' do end ``` -许多代码应该看起来很熟悉。 例如，我们仍使用 `RestClient.get` 来调用 {% data variables.product.product_name %} API，仍将结果传递到 ERB 模板（在此处被称为 `advanced.erb`）中进行呈现。 +Much of the code should look familiar. For example, we're still using `RestClient.get` +to call out to the {% data variables.product.product_name %} API, and we're still passing our results to be rendered +in an ERB template (this time, it's called `advanced.erb`). -此外，我们现在采用 `authenticated?` 方法来检查用户是否已通过身份验证。 如果否，则调用 `authenticate!` 方法，该方法执行 OAuth 流并使用授予的令牌和作用域更新会话。 +Also, we now have the `authenticated?` method which checks if the user is already +authenticated. If not, the `authenticate!` method is called, which performs the +OAuth flow and updates the session with the granted token and scopes. -接下来，在名为 _advanced.erb_ 的_视图_中创建一个文件，并将以下标记粘贴到其中： +Next, create a file in _views_ called _advanced.erb_, and paste this markup into it: ``` erb @@ -291,11 +343,18 @@ end ``` -从命令行调用 `ruby advanced_server.rb`，这将在端口 `4567`（即我们用于简单 Sinatra 应用程序的端口）上启动服务器。 当您导航到 `http://localhost:4567` 时，应用程序会调用 `authenticate!` 将您重定向到 `/callback`。 然后，`/callback` 将我们送回 `/`，由于我们已通过身份验证，因此将呈现 _advanced.erb_。 +From the command line, call `ruby advanced_server.rb`, which starts up your +server on port `4567` -- the same port we used when we had a simple Sinatra app. +When you navigate to `http://localhost:4567`, the app calls `authenticate!` +which redirects you to `/callback`. `/callback` then sends us back to `/`, +and since we've been authenticated, renders _advanced.erb_. -我们只需将 {% data variables.product.product_name %} 中的回调 URL 更改为 `/` 即可完全简化此往返路由。 但是，由于 _server.rb_ 和 _advanced.rb_ 都依赖于相同的回调 URL，因此我们必须费一点力气使其行之有效。 +We could completely simplify this roundtrip routing by simply changing our callback +URL in {% data variables.product.product_name %} to `/`. But, since both _server.rb_ and _advanced.rb_ are relying on +the same callback URL, we've got to do a little bit of wonkiness to make it work. -此外，如果我们从未授权此应用程序访问我们的 {% data variables.product.product_name %} 数据，我们会在早期的弹出和警告窗口中看到相同的确认对话框。 +Also, if we had never authorized this application to access our {% data variables.product.product_name %} data, +we would've seen the same confirmation dialog from earlier pop-up and warn us. [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [Sinatra]: http://www.sinatrarb.com/ @@ -304,6 +363,6 @@ end [REST Client]: https://github.com/archiloque/rest-client [libraries]: /libraries/ [oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ +[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/basics-of-authentication [new oauth app]: https://github.com/settings/applications/new [app settings]: https://github.com/settings/developers diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md index 42ae4326b2268..b1cd6fcd48631 100644 --- a/translations/zh-CN/content/rest/overview/api-previews.md +++ b/translations/zh-CN/content/rest/overview/api-previews.md @@ -70,14 +70,6 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 **自定义媒体类型：** `cloak-preview` **公布日期：** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} -### 用户阻止 - -用户可以[阻止其他用户](/rest/reference/users#blocking)。 组织也可以[阻止用户](/rest/reference/orgs#blocking)。 - -**自定义媒体类型：** `giant-sentry-fist-preview` **公布日期：** [2011-05-31](https://github.com/blog/862-block-the-bullies) **更新日期 1：** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **更新日期 2：** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - ### 仓库主题 在返回仓库结果的[调用](/rest/reference/repos)中查看[仓库主题](/articles/about-topics/)列表。 diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index 82e03b01ad4f9..6da1c33ad0d6f 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -73,7 +73,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby 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 f19f8ebf4caa9..812762ce3b08f 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 @@ -1,6 +1,6 @@ --- -title: REST API 中的资源 -intro: '了解如何导航 {% data variables.product.prodname_dotcom %} API 提供的资源。' +title: Resources in the REST API +intro: 'Learn how to navigate the resources provided by the {% data variables.product.prodname_dotcom %} API.' redirect_from: - /rest/initialize-the-repo/ versions: @@ -10,27 +10,28 @@ versions: --- -本文介绍构成官方 {% data variables.product.product_name %} REST API 的资源。 如果您有任何问题或要求，请联系 {% data variables.contact.contact_support %}。 +This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}. -### 当前版本 +### Current version -默认情况下，对 `{% data variables.product.api_url_code %}` 的所有请求都会收到 REST API 的 **v3** [版本](/developers/overview/about-githubs-apis)。 我们建议您[通过 `Accept` 标头明确请求此版本](/rest/overview/media-types#request-specific-version)。 +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. +We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -有关 GitHub GraphQL API 的信息，请参阅 [v4 文档](/graphql)。 有关迁移到 GraphQL 的信息，请参阅“[从 REST 迁移](/graphql/guides/migrating-from-rest-to-graphql)”。 +For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." {% endif %} -### 架构 +### Schema -{% if currentVersion == "free-pro-team@latest" %}所有 API 访问都通过 HTTPS 进行，{% else %}API{% endif %} 从 `{% data variables.product.api_url_code %}` 访问。 所有数据都 -作为 JSON 发送和接收。 +{% if currentVersion == "free-pro-team@latest" %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. All data is +sent and received as JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -49,43 +50,55 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs > X-Content-Type-Options: nosniff ``` -空白字段作为 `null` 包含在其中，而不是被忽略。 +Blank fields are included as `null` instead of being omitted. -所有时间戳以 ISO 8601 格式返回： +All timestamps return in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ -有关时间戳中时区的更多信息，请参阅[此节](#timezones)。 +For more information about timezones in timestamps, see [this section](#timezones). -#### 摘要表示 +#### Summary representations -当您获取资源列表时，响应包括该资源的属性_子集_。 这就是资源的“摘要”表示。 （API 提供某些属性需要大量计算。 出于性能考虑，摘要表示排除了这些属性。 要获得这些属性，请获取“详细”表示。) +When you fetch a list of resources, the response includes a _subset_ of the +attributes for that resource. This is the "summary" representation of the +resource. (Some attributes are computationally expensive for the API to provide. +For performance reasons, the summary representation excludes those attributes. +To obtain those attributes, fetch the "detailed" representation.) -**示例**：当您获取仓库列表时，您将获得每个仓库的摘要表示。 在本例中，我们获取 [octokit](https://github.com/octokit) 组织拥有的仓库列表： +**Example**: When you get a list of repositories, you get the summary +representation of each repository. Here, we fetch the list of repositories owned +by the [octokit](https://github.com/octokit) organization: GET /orgs/octokit/repos -#### 详细表示 +#### Detailed representations -当您获取单个资源时，响应通常包括该资源的_所有_属性。 这就是资源的“详细”表示。 （请注意，授权有时会影响表示中包含的详细信息数量。） +When you fetch an individual resource, the response typically includes _all_ +attributes for that resource. This is the "detailed" representation of the +resource. (Note that authorization sometimes influences the amount of detail +included in the representation.) -**示例**：当您获取单个仓库时，您将获得该仓库的详细表示。 在本例中，我们获取 [octokit/octokit.rb](https://github.com/octokit/octokit.rb) 仓库： +**Example**: When you get an individual repository, you get the detailed +representation of the repository. Here, we fetch the +[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository: GET /repos/octokit/octokit.rb -本文档提供每种 API 方法的示例响应。 示例响应说明了该方法返回的所有属性。 +The documentation provides an example response for each API method. The example +response illustrates all attributes that are returned by that method. -### 身份验证 +### Authentication -{% 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`。 这是为了防止私有仓库意外泄露给未经授权的用户。 +{% 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. -#### 基本验证 +#### Basic authentication ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -#### OAuth2 令牌（在标头中发送） +#### OAuth2 token (sent in a header) ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -93,14 +106,14 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% note %} -注：GitHub 建议使用授权标头发送 OAuth 令牌。 +Note: GitHub recommends sending OAuth tokens using the Authorization header. {% endnote %} -阅读[关于 OAuth2 的更多信息](/apps/building-oauth-apps/)。 请注意，OAuth2 令牌可使用生产应用程序的 [web 应用程序流](/developers/apps/authorizing-oauth-apps#web-application-flow)来获取。 +Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -#### OAuth2 键/密钥 +#### OAuth2 key/secret {% data reusables.apps.deprecating_auth_with_query_parameters %} @@ -108,23 +121,23 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' ``` -使用 `client_id` 和 `client_secret`_不会_验证为用户，只会识别您的 OAuth 应用程序以提高速率限制。 权限仅授予用户，而不授予应用程序，因此只会返回未经验证用户可以看到的数据。 因此，您应该仅在服务器到服务器的场景中使用 OAuth2 键/密钥。 不要将 OAuth 应用程序的客户端密钥泄露给用户。 +Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users. -在私有模式下无法使用 OAuth2 键和密钥进行身份验证，尝试验证时会返回 `401 Unauthorized`。 更多信息请参阅“[启用私有模式](/enterprise/admin/installation/enabling-private-mode)”。 +You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/enterprise/admin/installation/enabling-private-mode)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} -阅读[有关未经验证速率限制的更多信息](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)。 +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). {% endif %} -#### 失败登录限制 +#### Failed login limit -使用无效凭据进行身份验证将返回 `401 Unauthorized`： +Authenticating with invalid credentials will return `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -133,7 +146,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar > } ``` -在短时间内检测到多个使用无效凭据的请求后，API 将暂时拒绝该用户的所有身份验证尝试（包括使用有效凭据的尝试），并返回 `403 Forbidden`： +After detecting several requests with invalid credentials within a short period, +the API will temporarily reject all authentication attempts for that user +(including ones with valid credentials) with `403 Forbidden`: ```shell $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} @@ -145,59 +160,66 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > } ``` -### 参数 +### Parameters -许多 API 方法采用可选参数。 对于 `GET` 请求，任何未指定为路径段的参数都可以作为 HTTP 查询字符串参数进行传递： +Many API methods take optional parameters. For `GET` requests, any parameters not +specified as a segment in the path can be passed as an HTTP query string +parameter: ```shell $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" ``` -在此例中，'vmg' 和 'redcarpet' 是为路径中的 `:owner` 和 `:repo` 参数提供的值，而 `:state` 是查询字符串中传递的参数。 +In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner` +and `:repo` parameters in the path while `:state` is passed in the query +string. -对于 `POST`、`PATCH`、`PUT` 和 `DELETE` 请求，未包含在 URL 中的参数应编码为 JSON，内容类型为 'application/json'： +For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON +with a Content-Type of 'application/json': ```shell $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations ``` -### 根端点 +### Root endpoint -您可以向根端点发出 `GET` 请求，以获取 REST API 支持的所有端点类别： +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 == "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 %} ``` -### GraphQL 全局节点 ID +### GraphQL global node IDs -请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 +See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. -### 客户端错误 +### Client errors -接收请求正文的 API 调用上可能存在三种类型的客户端错误： +There are three possible types of client errors on API calls that +receive request bodies: + +1. Sending invalid JSON will result in a `400 Bad Request` response. -1. 发送无效的 JSON 将导致 `400 Bad Request` 响应。 - HTTP/1.1 400 Bad Request Content-Length: 35 - + {"message":"Problems parsing JSON"} -2. 发送错误类型的 JSON 值将导致 `400 Bad -Request` 响应。 - +2. Sending the wrong type of JSON values will result in a `400 Bad + Request` response. + HTTP/1.1 400 Bad Request Content-Length: 40 - + {"message":"Body should be a JSON object"} -3. 发送无效的字段将导致 `422 Unprocessable Entity` 响应。 - +3. Sending invalid fields will result in a `422 Unprocessable Entity` + response. + HTTP/1.1 422 Unprocessable Entity Content-Length: 149 - + { "message": "Validation Failed", "errors": [ @@ -209,122 +231,145 @@ Request` 响应。 ] } -所有错误对象都具有资源和字段属性，以便客户端可以知道问题所在。 还有一个错误代码，让您知道该字段有什么问题。 以下是可能的验证错误代码： +All error objects have resource and field properties so that your client +can tell what the problem is. There's also an error code to let you +know what is wrong with the field. These are the possible validation error +codes: -| 错误代码名称 | 描述 | -| ---------------- | -------------------------------------------------- | -| `missing` | 资源不存在。 | -| `missing_field` | 资源上的必需字段尚未设置。 | -| `invalid` | 字段的格式无效。 请查看文档以了解更具体的信息。 | -| `already_exists` | 另一个资源具有与此字段相同的值。 在必须具有某些唯一键（例如标签名称）的资源中可能会发生这种情况。 | -| `unprocessable` | 提供的输入无效。 | +Error code name | Description +-----------|-----------| +`missing` | A resource does not exist. +`missing_field` | A required field on a resource has not been set. +`invalid` | The formatting of a field is invalid. Review the documentation for more specific information. +`already_exists` | Another resource has the same value as this field. This can happen in resources that must have some unique key (such as label names). +`unprocessable` | The inputs provided were invalid. -资源还可能发送自定义验证错误（其中 `code` 为 `custom`）。 自定义错误始终包括一个描述错误的 `message` 字段，大多数错误还包括 `documentation_url` 字段，该字段指向一些可能有助于解决错误的内容。 +Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error. -### HTTP 重定向 +### HTTP redirects -API v3 酌情使用 HTTP 重定向。 客户端应假定任何请求都可能会导致重定向。 接收 HTTP 重定向*不是*错误，客户端应该遵循该重定向。 重定向响应将包括 `Location` 标头字段，其中包含客户端应向其重复请求的资源的 URI。 +API v3 uses HTTP redirection where appropriate. Clients should assume that any +request may result in a redirection. Receiving an HTTP redirection is *not* an +error and clients should follow that redirect. Redirect responses will have a +`Location` header field which contains the URI of the resource to which the +client should repeat the requests. -| 状态代码 | 描述 | -| ----------- | ------------------------------------------------------------------------------- | -| `301` | 永久重定向。 用于发出请求的 URI 已被 `Location` 标头字段中指定的 URL 所取代。 此请求以及对此资源的所有未来请求都应定向到新的 URI。 | -| `302`、`307` | 临时重定向。 该请求应按 `Location` 标头字段中指定的 URI 逐字重复，但客户端应对未来的请求继续使用原来的 URI。 | +Status Code | Description +-----------|-----------| +`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI. +`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests. -其他重定向状态代码可根据 HTTP 1.1 规范使用。 +Other redirection status codes may be used in accordance with the HTTP 1.1 spec. -### HTTP 请求方法 +### HTTP verbs -API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 +Where possible, API v3 strives to use appropriate HTTP verbs for each +action. -| 请求方法 | 描述 | -| -------- | ------------------------------------------------------------------------------ | -| `HEAD` | 可以针对任何资源发出以仅获取 HTTP 标头信息。 | -| `GET` | 用于检索资源。 | -| `POST` | 用于创建资源。 | -| `PATCH` | 用于通过部分 JSON 数据更新资源。 例如，议题资源具有 `title` 和 `body` 属性。 `PATCH` 请求可以接受一个或多个属性来更新资源。 | -| `PUT` | 用于替换资源或集合。 对于没有 `body` 属性的 `PUT` 请求，请确保将 `Content-Length` 标头设置为零。 | -| `DELETE` | 用于删除资源。 | +Verb | Description +-----|----------- +`HEAD` | Can be issued against any resource to get just the HTTP header info. +`GET` | Used for retrieving resources. +`POST` | Used for creating resources. +`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource. +`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero. +`DELETE` |Used for deleting resources. -### 超媒体 +### Hypermedia -所有资源都可以具有一个或多个链接到其他资源的 `*_url` 属性。 这些属性旨在提供明确的 URL，使适当的 API 客户端不需要自己构建 URL。 强烈建议 API 客户端使用这些属性。 这样做有助于开发者未来更容易升级 API。 所有 URI 都应成为适当的 [RFC 6570][rfc] URI 模板。 +All resources may have one or more `*_url` properties linking to other +resources. These are meant to provide explicit URLs so that proper API clients +don't need to construct URLs on their own. It is highly recommended that API +clients use these. Doing so will make future upgrades of the API easier for +developers. All URLs are expected to be proper [RFC 6570][rfc] URI templates. -然后，您可以使用 [uri_template][uri] gem 等命令扩展这些模板： +You can then expand these templates using something like the [uri_template][uri] +gem: >> tmpl = URITemplate.new('/notifications{?since,all,participating}') >> tmpl.expand => "/notifications" - + >> tmpl.expand :all => 1 => "/notifications?all=1" - + >> tmpl.expand :all => 1, :participating => 1 => "/notifications?all=1&participating=1" -### 分页 +[rfc]: http://tools.ietf.org/html/rfc6570 +[uri]: https://github.com/hannesg/uri_template + +### Pagination -默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `page` 参数指定更多页面。 对于某些资源，您还可以使用 `per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 +Requests that return multiple items will be paginated to 30 items by +default. You can specify further pages with the `page` parameter. For some +resources, you can also set a custom page size up to 100 with the `per_page` parameter. +Note that for technical reasons not all endpoints respect the `per_page` parameter, +see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -请注意，页码从 1 开始，省略 `page` 参数将返回第一页。 +Note that page numbering is 1-based and that omitting the `page` +parameter will return the first page. -有些端点使用基于光标的分页。 光标是指向结果集中位置的字符串。 使用基于光标的分页时，结果集中没有固定的“页”概念，因此无法导航到特定页面。 相反，您可以使用 `before` 或 `after` 参数遍历结果。 +Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set. +With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page. +Instead, you can traverse the results by using the `before` or `after` parameters. -有关分页的更多信息，请查看我们的[分页浏览][pagination-guide]指南。 +For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. -#### 链接标头 +#### Link header {% note %} -**注：**确保使用链接标头值构成调用，而不是构建自己的 URL。 +**Note:** It's important to form calls with Link header values instead of constructing your own URLs. {% endnote %} -[链接标头](http://tools.ietf.org/html/rfc5988)包括分页信息： 例如： +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. For example: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" -_该示例包括换行符，以提高可读性。_ +_The example includes a line break for readability._ -或者，如果端点使用基于光标的分页： +Or, if the endpoint uses cursor-based pagination: Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", -此 `Link` 响应标头包含一个或多个[超媒体](/rest#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). -可能的 `rel` 值为： +The possible `rel` values are: -| 名称 | 描述 | -| ------- | ------------ | -| `下一个` | 结果下一页的链接关系 | -| `last` | 结果最后一页的链接关系。 | -| `first` | 结果第一页的链接关系。 | -| `prev` | 结果前一页的链接关系。 | +Name | Description +-----------|-----------| +`next` |The link relation for the immediate next page of results. +`last` |The link relation for the last page of results. +`first` |The link relation for the first page of results. +`prev` |The link relation for the immediate previous page of results. -### 速率限制 +### Rate limiting -对于使用基本验证或 OAuth 的 API 请求，每小时最多可发出 5,000 个请求。 无论是使用[基本验证](#basic-authentication)还是 [OAuth 令牌](#oauth2-token-sent-in-a-header)，经验证的请求都与经验证的用户相关联。 这意味着在使用同一用户拥有的不同令牌进行验证时，该用户授权的所有 OAuth 应用程序将共享同一配额——每小时 5,000 个请求。 +For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user. {% if currentVersion == "free-pro-team@latest" %} -对于属于 {% data variables.product.prodname_ghe_cloud %} 帐户的用户，使用 OAuth 令牌对相同 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的资源发出的请求上限已提升至每小时 15,000 点。 +For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour. {% endif %} -对于未经验证的请求，速率限制允许每小时最多 60 个请求。 未经验证的请求与原始 IP 地址相关联，与发出请求的用户无关。 +For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests. {% data reusables.enterprise.rate_limit %} -请注意，[搜索 API 具有自定义速率限制规则](/rest/reference/search#rate-limit)。 +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). -任何 API 请求返回的 HTTP 标头都显示当前速率限制状态： +The returned HTTP headers of any API request show your current rate limit status: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -333,20 +378,20 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat > X-RateLimit-Reset: 1372700873 ``` -| 标头名称 | 描述 | -| ----------------------- | ---------------------------------------------------------------------- | -| `X-RateLimit-Limit` | 每小时允许您发出的最大请求数。 | -| `X-RateLimit-Remaining` | 当前速率限制窗口中剩余的请求数。 | -| `X-RateLimit-Reset` | 当前费率限制窗口重置时间，以 [UTC 标准时间秒](http://en.wikipedia.org/wiki/Unix_time)为单位。 | +Header Name | Description +-----------|-----------| +`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour. +`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window. +`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time). -如果您需要不同格式的时间，任何现代编程语言都可以实现您的目标。 例如，如果您在 Web 浏览器上打开控制台，您可以轻松地以 JavaScript Date 对象获取重置时间。 +If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object. ``` javascript new Date(1372700873 * 1000) // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) ``` -如果超过速率限制，错误响应将返回： +If you exceed the rate limit, an error response returns: ```shell > HTTP/1.1 403 Forbidden @@ -362,11 +407,11 @@ new Date(1372700873 * 1000) > } ``` -您可以[检查速率限制状态](/rest/reference/rate-limit)，而不会引发 API 命中。 +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. -#### 提高 OAuth 应用程序的未经验证速率限制 +#### Increasing the unauthenticated rate limit for OAuth applications -如果您的 OAuth 应用程序需要以更高的速率限制进行未经验证的调用， 您可以在端点路由之前传递应用程序的客户端 ID 和密钥。 +If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route. ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos @@ -380,21 +425,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% note %} -**注：**切勿与任何人共享客户端密钥，也不要将其包含在客户端浏览器代码中。 仅将此处显示的方法用于服务器到服务器的调用。 +**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls. {% endnote %} -#### 保持在速率限制之内 +#### Staying within the rate limit -如果使用基本验证或 OAuth 时超出了速率限制，您可以通过缓存 API 响应和使用[条件请求](#conditional-requests)来解决此问题。 +If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests). -#### 滥用速率限制 +#### Abuse rate limits -为了在 {% data variables.product.product_name %} 上提供优质的服务，使用 API 时，某些操作可能会受到额外的速率限制。 例如，使用 API 快速创建内容、主动轮询而不是使用 web 挂钩、发出多个并发请求或重复请求计算成本高昂的数据，可能会导致滥用速率限制。 +In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in abuse rate limiting. -滥用速率限制无意干扰 API 的合法使用。 您的正常速率限制应该是您目标的唯一限制。 为确保您成为 API 的好公民，请查看我们的[最佳实践指南](/guides/best-practices-for-integrators/)。 +Abuse rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/). -如果您的应用程序触发此速率限制，您将收到信息响应： +If your application triggers this rate limit, you'll receive an informative response: ```shell > HTTP/1.1 403 Forbidden @@ -409,47 +454,54 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% if currentVersion == "free-pro-team@latest" %} -### 必需用户代理 +### User agent required -所有 API 请求都必须包含有效的 `User-Agent` 标头。 没有 `User-Agent` 标头的请求将被拒绝。 我们要求您使用 {% data variables.product.product_name %} 用户名或应用程序的名称作为 `User-Agent` 标头值。 这是为了方便我们在发现问题时与您联系 。 +All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent` +header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your +application, for the `User-Agent` header value. This allows us to contact you if there are problems. -例如： +Here's an example: ```shell User-Agent: Awesome-Octocat-App ``` -默认情况下，cURL 会发送有效的 `User-Agent` 标头。 如果您通过 cURL（或通过备用客户端）提供了无效的 `User-Agent` 标头，将会收到 `403 Forbidden` 响应： +cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html > Request forbidden by administrative rules. > Please make sure your request has a User-Agent header. -> 检查其他可能的原因。 +> Check for other possible causes. ``` {% endif %} -### 条件请求 +### Conditional requests -大多数响应返回 `ETag` 标头。 许多响应还会返回 `Last-Modified` 标头。 您可以根据这些标头的值，分别使用 `If-None-Match` 和 `If-Modified-Since` 标头对这些资源发出后续请求。 如果资源没有更改，服务器将返回 `304 Not Modified`。 +Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values +of these headers to make subsequent requests to those resources using the +`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource +has not changed, the server will return a `304 Not Modified`. {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**注**：发出条件请求并收到 304 响应不会计入您的[速率限制](#rate-limiting)，因此我们建议您尽可能使用它。 +**Note**: Making a conditional request and receiving a 304 response does not +count against your [Rate Limit](#rate-limiting), so we encourage you to use it +whenever possible. {% endtip %} {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -460,7 +512,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -471,7 +523,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -482,23 +534,28 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -### 跨源资源共享 +### Cross origin resource sharing -API 支持适用于任何来源 AJAX 请求的跨源资源共享 (CORS)。 您可以阅读 [CORS W3C 建议](http://www.w3.org/TR/cors/)或 HTML 5 安全指南中的[这方面介绍](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki)。 +The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from +any origin. +You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or +[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the +HTML 5 Security Guide. -以下是从浏览器点击发送的示例请求 `http://example.com`： +Here's a sample request sent from a browser hitting +`http://example.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval ``` -以下是 CORS 预检请求的示例： +This is what the CORS preflight request looks like: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With @@ -507,9 +564,13 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -### JSON-P 回调 +### JSON-P callbacks -您可以向任何 GET 调用发送 `?callback` 参数，以便让结果包裹在 JSON 函数中。 当浏览器希望绕开跨域问题将 {% data variables.product.product_name %} 内容嵌入网页时，通常使用此方法。 响应包括与常规 API 相同的数据输出，加上相关的 HTTP 标头信息。 +You can send a `?callback` parameter to any GET call to have the results +wrapped in a JSON function. This is typically used when browsers want +to embed {% data variables.product.product_name %} content in web pages by getting around cross domain +issues. The response includes the same data output as the regular API, +plus the relevant HTTP Header information. ```shell $ curl {% data variables.product.api_url_pre %}?callback=foo @@ -530,7 +591,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo > }) ``` -您可以编写一个 JavaScript 处理程序来处理回调。 以下是一个最小的处理程序示例，您可以尝试编写： +You can write a JavaScript handler to process the callback. Here's a minimal example you can try out: @@ -541,26 +602,28 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo console.log(meta); console.log(data); } - + var script = document.createElement('script'); script.src = '{% data variables.product.api_url_code %}?callback=foo'; - + document.getElementsByTagName('head')[0].appendChild(script); - +

            Open up your browser's console.

            -所有标头都具有与 HTTP 标头相同的字符串值，但有一个值得注意的例外 ：链接。 链接标头已预先解析，并以 `[url, options]` 元组的数组形式出现。 +All of the headers are the same String value as the HTTP Headers with one +notable exception: Link. Link headers are pre-parsed for you and come +through as an array of `[url, options]` tuples. -链接如下所示： +A link that looks like this: Link: ; rel="next", ; rel="foo"; bar="baz" -... 在回调输出中将如下所示： +... will look like this in the Callback output: ```json { @@ -582,40 +645,37 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo } ``` -### 时区 +### Timezones -某些创建新数据的请求（例如创建新的提交）允许您在指定或生成时间戳时提供时区信息。 我们按照优先顺序应用以下规则来确定 API 调用的时区信息。 +Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for API calls. -* [明确提供带有时区信息的 ISO 8601 时间戳](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) -* [使用 `Time-Zone` 标头](#using-the-time-zone-header) -* [使用用户的最后一个已知时区](#using-the-last-known-timezone-for-the-user) -* [在没有其他时区信息的情况下默认使用 UTC](#defaulting-to-utc-without-other-timezone-information) +* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) +* [Using the `Time-Zone` header](#using-the-time-zone-header) +* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user) +* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information) -#### 明确提供带有时区信息的 ISO 8601 时间戳 +#### Explicitly providing an ISO 8601 timestamp with timezone information -对于允许指定时间戳的 API 调用，我们使用这种明确的时间戳。 这方面的示例是[提交 API](/rest/reference/git#commits)。 +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -这些时间戳看起来像 `2014-02-27T15:05:06+01:00`。 另请参阅[本示例](/rest/reference/git#example-input)，了解如何指定这些时间戳。 +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. -#### 使用 `Time-Zone` 标头 +#### Using the `Time-Zone` header -可以提供根据 [Olson 数据库中的名称列表](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)定义时区的 `Time-Zone` 标头。 +It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```shell $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -这意味着当您在这个标题定义的时区做出 API 调用时，我们会生成一个时间戳。 例如，[内容 API](/rest/reference/repos#contents)为每个添加或更改生成 git 提交，并使用当前时间作为时间戳。 此标头将确定用于生成当前时间戳的时区。 - -#### 使用用户的最后一个已知时区 +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. -如果未指定 `Time-Zone` 标头，并且您对 API 进行验证过身份的调用，则我们对经过身份验证的用户使用最后一个已知时区。 最新一个已知的时区在您浏览 {% data variables.product.product_name %} 网站时都会更新。 +#### Using the last known timezone for the user -#### 在没有其他时区信息的情况下默认使用 UTC +If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website. -如果上述步骤未产生任何信息，我们将使用 UTC 作为时区来创建 git 提交。 +#### Defaulting to UTC without other timezone information -[rfc]: http://tools.ietf.org/html/rfc6570 -[uri]: https://github.com/hannesg/uri_template +If the steps above don't result in any information, we use UTC as the timezone to create the git commit. [pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/zh-CN/content/rest/reference/code-scanning.md b/translations/zh-CN/content/rest/reference/code-scanning.md index 9307eb41f65fe..d328a424a2aa4 100644 --- a/translations/zh-CN/content/rest/reference/code-scanning.md +++ b/translations/zh-CN/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: 代码扫描 redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index 2428be2110fd0..070d56e43493e 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -252,7 +252,7 @@ - term: Gist description: >- - gist 是一种可共享的文件，可用于在 GitHub 上编辑、克隆和分叉。您可以将 gist 设为公共或私密，但私密 gist 可供具有 URL 的任何人访问。 + Gist 是一个您可以在 GitHub 上编辑、克隆和复刻的可共享文件。您可以将 Gist 设为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}或机密，但机密 gist 可用于具有 URL 的{% if currentVersion == "github-ae@latest" %}任何企业成员{% else %}任何人{% endif %}。 - term: Git description: >- @@ -436,7 +436,7 @@ - term: 通知 description: >- - web 或电子邮件（根据您的设置）传送的更新，提供您感兴趣的活动的相关信息。 + Web 或电子邮件（根据您的设置）传送的更新，提供您感兴趣的活动的相关信息。 - term: OAuth 应用程序 description: >- diff --git a/translations/zh-CN/data/graphql/ghes-3.0/graphql_previews.enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.0/graphql_previews.enterprise.yml new file mode 100644 index 0000000000000..f34be4a794c6e --- /dev/null +++ b/translations/zh-CN/data/graphql/ghes-3.0/graphql_previews.enterprise.yml @@ -0,0 +1,149 @@ +--- +- + title: 使用包版本删除 + description: >- + 此预览支持允许删除私有包版本 DeletePackageVersion 突变。 + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: 部署 + description: >- + 此预览支持部署突变和新部署功能。 + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/ecosystem-api' +- + title: >- + MergeInfoPreview - 有关拉取请求合并状态的更多详细信息。 + description: >- + 此预览支持访问提供有关拉取请求合并状态的更多详细信息的字段。 + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - 在单个操作中更新多个 ref。 + description: 此预览支持在单个操作中更新多个 ref。 + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: 项目事件详细信息 + description: >- + 此预览将项目、项目卡和项目列详细信息添加到与项目相关的议题事件。 + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: 创建内容附件 + description: 此预览支持创建内容附件。 + toggled_by: ':corsair-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createContentAttachment + owning_teams: + - '@github/feature-lifecycle' +- + title: 固定议题预览 + description: 此预览增加了对固定议题的支持。 + toggled_by: ':elektra-preview' + announcement: null + updates: null + toggled_on: + - Repository.pinnedIssues + - PinnedIssue + - PinnedIssueEdge + - PinnedIssueConnection + - Mutation.pinIssue + - Mutation.unpinIssue + owning_teams: + - '@github/pe-pull-requests' +- + title: 标签预览 + description: >- + 此预览支持添加、更新、创建和删除标签。 + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: 导入项目 + description: 此预览增加了对导入项目的支持。 + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: 团队审查任务预览 + description: >- + 此预览支持更新团队审查任务的设置。 + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/zh-CN/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000000..f73100b64db20 --- /dev/null +++ b/translations/zh-CN/data/graphql/ghes-3.0/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: Migration.uploadUrlTemplate + description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。' + reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。' + date: '2019-04-01T00:00:00+00:00' + criticality: 重大 + owner: tambling + - + location: AssignedEvent.user + 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`，以便更明确地表示要返回的值' + date: '2020-01-01T00:00:00+00:00' + criticality: 重大 + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。' + reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值' + date: '2020-01-01T00:00:00+00:00' + criticality: 重大 + owner: BlakeWilliams + - + location: UnassignedEvent.user + 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` 将被删除。' + date: '2020-04-01T00:00:00+00:00' + criticality: 重大 + owner: antn + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: '`isUnlicensed` 将被删除。' + reason: 所有挂起的成员都会使用许可证 + date: '2020-07-01T00:00:00+00:00' + criticality: 重大 + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: '`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。' + reason: 仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。 + date: '2020-10-01T00:00:00+00:00' + criticality: 重大 + owner: jdennes + - + location: Issue.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` 将被删除' + date: '2020-10-01T00:00:00+00:00' + criticality: 重大 + owner: mikesea + - + location: RepositoryInvitationOrderField.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` 将被删除。' + date: '2020-10-01T00:00:00+00:00' + criticality: 重大 + owner: nholden + - + location: EnterpriseMemberEdge.isUnlicensed + description: '`isUnlicensed` 将被删除。' + reason: 所有成员都会使用许可证 + date: '2021-01-01T00:00:00+00:00' + criticality: 重大 + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: '`isUnlicensed` 将被删除。' + reason: 所有外部协作者使用许可证 + date: '2021-01-01T00:00:00+00:00' + criticality: 重大 + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: '`isUnlicensed` 将被删除。' + reason: 所有挂起的协作者使用许可证 + date: '2021-01-01T00:00:00+00:00' + criticality: 重大 + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: '`DRAFT` 将被删除。改为使用 PullRequest.isDraft。' + reason: DRAFT 状态将从这个枚举中删除，应改用 `isDraft` + date: '2021-01-01T00:00:00+00:00' + criticality: 重大 + owner: nplasterer diff --git a/translations/zh-CN/data/learning-tracks/actions.yml b/translations/zh-CN/data/learning-tracks/actions.yml new file mode 100644 index 0000000000000..211a50ea959a7 --- /dev/null +++ b/translations/zh-CN/data/learning-tracks/actions.yml @@ -0,0 +1,57 @@ +--- +getting_started: + title: '开始使用 {% data variables.product.prodname_actions %}' + description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + guides: + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/learn-github-actions/finding-and-customizing-actions + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/security-hardening-for-github-actions +continuous_integration: + title: 'Build and test code' + description: 'You can create custom continuous integration (CI) workflows right in your repository.' + guides: + - /actions/guides/about-continuous-integration + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/about-service-containers + - /actions/guides/building-and-testing-nodejs + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant +continuous_deployment: + title: 'Automate your deployments' + description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + guides: + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/publishing-docker-images +hosting_your_own_runners: + title: 'Host your own runners' + description: '您可以创建自托管的运行器，在一个可高度自定义的环境中运行工作流程。' + guides: + - /actions/hosting-your-own-runners/about-self-hosted-runners + - /actions/hosting-your-own-runners/adding-self-hosted-runners + - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service + - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners + - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow + - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups + - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners +create_actions: + title: 'Create an action' + description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + guides: + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/creating-actions/metadata-syntax-for-github-actions + - /actions/creating-actions/dockerfile-support-for-github-actions + - /actions/creating-actions/setting-exit-codes-for-actions + - /actions/creating-actions/publishing-actions-in-github-marketplace diff --git a/translations/zh-CN/data/release-notes/2-22/0.yml b/translations/zh-CN/data/release-notes/2-22/0.yml index cb67278fcae8a..5231cfd2ae3b6 100644 --- a/translations/zh-CN/data/release-notes/2-22/0.yml +++ b/translations/zh-CN/data/release-notes/2-22/0.yml @@ -7,7 +7,7 @@ sections: heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - @@ -90,6 +90,19 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - + heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} @@ -113,8 +126,8 @@ sections: heading: Deprecation of OAuth Application API notes: - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + backups: + - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/3-0/0-rc.yml b/translations/zh-CN/data/release-notes/3-0/0-rc.yml new file mode 100644 index 0000000000000..4794284f4ac0a --- /dev/null +++ b/translations/zh-CN/data/release-notes/3-0/0-rc.yml @@ -0,0 +1,144 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. + + {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/zh-CN/data/reusables/actions/actions-not-verified.md b/translations/zh-CN/data/reusables/actions/actions-not-verified.md index f56e55afbcfe8..b2616e93e0b70 100644 --- a/translations/zh-CN/data/reusables/actions/actions-not-verified.md +++ b/translations/zh-CN/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} 验证一些合作伙伴组织，这些组织显示为已验证的创建者。 diff --git a/translations/zh-CN/data/reusables/actions/enterprise-actions-permissions.md b/translations/zh-CN/data/reusables/actions/enterprise-actions-permissions.md index ccaff3565825c..7274b1092016e 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. 在“Policies（策略）”下，选择一个选项。 ![启用、禁用或限制此企业帐户的操作](/assets/images/help/organizations/enterprise-actions-policy.png) +1. 在“Policies（策略）”下选择选项。 + + 您可以在您的企业中选择哪些组织可以使用 {% data variables.product.prodname_actions %}，并且可以限制对公共操作的访问。 + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **注意：**要启用对公共操作的访问，必须先配置 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_marketplace %}。 更多信息请参阅“[使用 GitHub Connect 启用对 GitHub.com 操作的自动访问](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 + + {% endnote %} + {% endif %} + ![启用、禁用或限制此企业帐户的操作](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/zh-CN/data/reusables/actions/enterprise-beta.md b/translations/zh-CN/data/reusables/actions/enterprise-beta.md index 33a0ba2b51574..ef497fcaf4e6c 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-beta.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**注：**{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 要查看外部存储要求并请求访问测试版，请参阅“[启用 {% data variables.product.prodname_actions %} 和配置存储](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)”。 +**注：**{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 要查看外部存储要求并请求访问测试版，请参阅“[开始对 {% data variables.product.prodname_ghe_server %} 使用 {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)”。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md b/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md new file mode 100644 index 0000000000000..0856d5e5834df --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md @@ -0,0 +1,9 @@ +* {% data reusables.actions.enterprise-hardware-considerations %} +* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." + + {% note %} + + **注：**{% data reusables.actions.enterprise-self-signed-cert %} + + {% endnote %} +* {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-enable-checkbox.md b/translations/zh-CN/data/reusables/actions/enterprise-enable-checkbox.md new file mode 100644 index 0000000000000..0d01d079f4449 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-enable-checkbox.md @@ -0,0 +1 @@ +1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md b/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md new file mode 100644 index 0000000000000..24c077bbae75d --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. diff --git a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md new file mode 100644 index 0000000000000..8bc7f63d59606 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md @@ -0,0 +1 @@ +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/zh-CN/data/reusables/actions/enterprise-limit-actions-use.md b/translations/zh-CN/data/reusables/actions/enterprise-limit-actions-use.md new file mode 100644 index 0000000000000..e2f4ed9452634 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-limit-actions-use.md @@ -0,0 +1 @@ +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." diff --git a/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md new file mode 100644 index 0000000000000..510f20bc93a04 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -0,0 +1,3 @@ +### 后续步骤 + +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." diff --git a/translations/zh-CN/data/reusables/actions/enterprise-s3-permission.md b/translations/zh-CN/data/reusables/actions/enterprise-s3-permission.md new file mode 100644 index 0000000000000..b53432227edf9 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-s3-permission.md @@ -0,0 +1,9 @@ +{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: + +* `s3:PutObject` +* `s3:GetObject` +* `s3:ListBucketMultipartUploads` +* `s3:ListMultipartUploadParts` +* `s3:AbortMultipartUpload` +* `s3:DeleteObject` +* `s3:ListBucket` diff --git a/translations/zh-CN/data/reusables/actions/enterprise-s3-support-warning.md b/translations/zh-CN/data/reusables/actions/enterprise-s3-support-warning.md new file mode 100644 index 0000000000000..26e34ef8a4d85 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-s3-support-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." + +{% endwarning %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/enterprise-self-signed-cert.md b/translations/zh-CN/data/reusables/actions/enterprise-self-signed-cert.md new file mode 100644 index 0000000000000..10c5efee2fa2f --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-self-signed-cert.md @@ -0,0 +1 @@ +We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. diff --git a/translations/zh-CN/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/zh-CN/data/reusables/actions/enterprise-storage-ha-backups.md new file mode 100644 index 0000000000000..d7fd554d79053 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/enterprise-storage-ha-backups.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/zh-CN/data/reusables/actions/workflow-template-overview.md b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md new file mode 100644 index 0000000000000..1019643e6ad1c --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md @@ -0,0 +1,3 @@ +{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. 例如，如果仓库包含 Node.js 代码，您就会看到 Node.js 项目的建议。 您可以使用工作流程模板作为基础来构建自定义工作流程，或按原样使用模板。 + +您可以在 {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) 仓库{% else %} {% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览工作流程模板的完整列表。 diff --git a/translations/zh-CN/data/reusables/advanced-security/more-info-ghas.md b/translations/zh-CN/data/reusables/advanced-security/more-info-ghas.md new file mode 100644 index 0000000000000..ec48cd9a54b51 --- /dev/null +++ b/translations/zh-CN/data/reusables/advanced-security/more-info-ghas.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。 +{% endif %} diff --git a/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md new file mode 100644 index 0000000000000..48f3c5a99aeb4 --- /dev/null +++ b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md index 6995459369467..af689fad906cd 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -3,7 +3,7 @@ **弃用通知：** {% data variables.product.prodname_dotcom %} 将停止使用查询参数向 API 验证。 向 API 验证应使用 [HTTP 基本身份验证](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)完成。{% if currentVersion == "free-pro-team@latest" %} 使用查询参数向 API 验证在 2021 年 5 月 5 日将不再有效。 {% endif %}有关详细信息，包括预定的限电，请参阅[博客文章](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)。 -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. 相反，我们建议集成商在标头中移动其访问令牌 `client_id` 或 `client_secret`。 {% data variables.product.prodname_dotcom %} 将宣布删除通过查询参数进行身份验证，并且会提前通知。 {% endif %} +{% if enterpriseServersions contains currentversion or currentversion == "github-ae@latest" %} 使用查询参数向 API 验证仍然可用，但出于安全考虑不再支持。 相反，我们建议集成商在标头中移动其访问令牌 `client_id` 或 `client_secret`。 {% data variables.product.prodname_dotcom %} 将宣布删除通过查询参数进行身份验证，并且会提前通知。 {% endif %} {% endwarning %} {% endif %} diff --git a/translations/zh-CN/data/reusables/apps/expiring_user_authorization_tokens.md b/translations/zh-CN/data/reusables/apps/expiring_user_authorization_tokens.md index 58b480efc0d22..b6aff60e2eb5d 100644 --- a/translations/zh-CN/data/reusables/apps/expiring_user_authorization_tokens.md +++ b/translations/zh-CN/data/reusables/apps/expiring_user_authorization_tokens.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -为使用户到服务器的访问令牌更安全，您可以使用将在 8 小时后过期的访问令牌，以及可交换新访问令牌的刷新令牌。 For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." +为使用户到服务器的访问令牌更安全，您可以使用将在 8 小时后过期的访问令牌，以及可交换新访问令牌的刷新令牌。 更多信息请参阅“[刷新用户到服务器访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/branches/set-default-branch.md b/translations/zh-CN/data/reusables/branches/set-default-branch.md index c9c1d21abb0d0..4724f27f26d8c 100644 --- a/translations/zh-CN/data/reusables/branches/set-default-branch.md +++ b/translations/zh-CN/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -您可以为新仓库设置默认分支名称。 For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)," and {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)."{% endif %} +您可以为新仓库设置默认分支名称。 更多信息请参阅“[管理仓库的默认分支](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)”、“[管理组织中仓库的默认分支](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)”和 {% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)”。{% else %}“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/about-code-scanning.md b/translations/zh-CN/data/reusables/code-scanning/about-code-scanning.md index 3dbaf64e32d16..dd054a581b6d3 100644 --- a/translations/zh-CN/data/reusables/code-scanning/about-code-scanning.md +++ b/translations/zh-CN/data/reusables/code-scanning/about-code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} 是一项功能，可用于分析 {% data variables.product.prodname_dotcom %} 仓库中的代码，以查找安全漏洞和编码错误。 Any problems identified by the analysis are shown in {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +{% data variables.product.prodname_code_scanning_capc %} 是一项功能，可用于分析 {% data variables.product.prodname_dotcom %} 仓库中的代码，以查找安全漏洞和编码错误。 分析发现的任何问题都在 {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} 中显示。 diff --git a/translations/zh-CN/data/reusables/code-scanning/beta.md b/translations/zh-CN/data/reusables/code-scanning/beta.md index db2725e5ca501..b0672fd3de9de 100644 --- a/translations/zh-CN/data/reusables/code-scanning/beta.md +++ b/translations/zh-CN/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**注意：**{% data variables.product.prodname_code_scanning_capc %} 目前处于测试阶段，可能会更改。 有关参加公测的更多信息，请[在此注册](https://resources.github.com/beta-signup/)。 +**注：** {% data variables.product.prodname_code_scanning_capc %} 正在测试用于 {% data variables.product.prodname_ghe_server %} 2.22。 对于代码扫描的一般可用版本，请升级到最新版本的 {% data variables.product.prodname_ghe_server %}。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md index 0107bd5af7b06..cb72da50c7536 100644 --- a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -以下配置文件禁用默认查询，并指定一组要运行的自定义查询。 It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. +以下配置文件禁用默认查询，并指定一组要运行的自定义查询。 它还配置 {% data variables.product.prodname_codeql %} 扫描 _src_ 目录中的文件（相对于根目录），并且排除 _src/node_modules_ 目录以及名称以 _.test.js_ 结尾的任何文件。 因此，_src/node_modules_ 中的文件以及名称以 _.test.js_ 结尾的文件被排除在分析之外。 ``` yaml name: "My {% data variables.product.prodname_codeql %} config" diff --git a/translations/zh-CN/data/reusables/code-scanning/not-available.md b/translations/zh-CN/data/reusables/code-scanning/not-available.md new file mode 100644 index 0000000000000..621faf031eeb4 --- /dev/null +++ b/translations/zh-CN/data/reusables/code-scanning/not-available.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 + +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md index 1793f62a87b7e..72c8cd8a84d95 100644 --- a/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md +++ b/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md @@ -1 +1 @@ -{% data variables.product.prodname_codespaces %} 在测试期间可免费使用。 When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage. +{% data variables.product.prodname_codespaces %} 在测试期间可免费使用。 当 {% data variables.product.prodname_codespaces %} 公开发布时，将按存储和计算使用情况计费。 diff --git a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md index b8d2b78cbceae..18554c0ce1388 100644 --- a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. 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#allowing-dependabot-to-access-private-repositories)." +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. 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#allowing-dependabot-to-access-private-repositories)." -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md index e13cb3f19d076..3ad535c2caad3 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -1,23 +1,23 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. - -| 包管理器 | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| Git 子模块：`gitsubmodule` | **✓** | | -| GitHub 操作：`github-actions` | **✓** | | -| Go 模块：`gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +下表显示对于每个包管理器，{% data variables.product.prodname_dependabot %} 是否支持：私有 {% data variables.product.prodname_dotcom %} 仓库中的依赖项，以及供应的依赖项。 + +| 包管理器 | 私有 {% data variables.product.prodname_dotcom %} 仓库 | 供应 | +| -------------------------- |:--------------------------------------------------:|:-----:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir：`hex` | | | +| Elm: `elm` | **✓** | | +| Git 子模块：`gitsubmodule` | **✓** | | +| GitHub 操作：`github-actions` | **✓** | | +| Go 模块：`gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} @@ -25,7 +25,7 @@ The following table shows, for each package manager, whether {% data variables.p -`yarn`（仅限 v1）（指定 `npm`） --`.gradle.kts` files, for Kotlin projects (specify `gradle`) +-`.gradle.kts` 文件，用于 Kotlin 项目（指定 `gradle`） -`pipenv`、`pip-compile` 和 `poetry`（指定 `pip`） diff --git a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md index a3e76b2d05982..a7291396ff99a 100644 --- a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -10,4 +10,4 @@ 默认情况下，工作流程不在复刻仓库上运行。 您必须在复刻仓库的 **Actions（操作）**选项卡中启用 GitHub 操作。 -{% data reusables.actions.forked-secrets %} The permissions for the `GITHUB_TOKEN` in forked repositories is read-only. 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。 +{% data reusables.actions.forked-secrets %} 对复刻仓库中 `GITHUB_TOKEN` 的权限是只读的。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md index b4d889bf00792..0e4fae8c9df6a 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md @@ -1 +1 @@ -{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}Currently, there are two administrative roles available in enterprises: enterprise owners, who can access and manage all settings across the enterprise, and billing managers, who can access and manage only the enterprise's billing settings. {% endif %}Enterprise owners can {% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}also {% endif %} see all of the members and outside collaborators for every organization owned by the enterprise. +{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/options-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/options-tab.md index 8a67ace0e1cb5..436e4b1df2624 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/options-tab.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/options-tab.md @@ -1 +1 @@ -1. Under {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} {% octicon "law" aria-label="The law icon" %} **Policies**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Settings"{% endif %}, click **Options**. ![企业帐户设置侧边栏中的 Options（选项）选项卡](/assets/images/enterprise/business-accounts/settings-options-tab.png) +1. 在{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} {% octicon "law" aria-label="The law icon" %} **Policies（政策）**{% else %}“{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）”{% endif %} 下，单击 **Options（选项）**。 ![企业帐户设置侧边栏中的 Options（选项）选项卡](/assets/images/enterprise/business-accounts/settings-options-tab.png) diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/zh-CN/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index bb7cef7cd7e24..a2bd07e0dca37 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**注：**企业帐户的用户预配目前处于私测阶段，可能会发生变化。 要申请使用测试版，[请联系我们的客户管理团队](https://enterprise.github.com/contact)。 +**注：**企业帐户中的组织的用户预配目前仅支持 Okta，正在私有测试版中，可能会更改。 要申请使用测试版，[请联系我们的客户管理团队](https://enterprise.github.com/contact)。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/enterprise/rate_limit.md b/translations/zh-CN/data/reusables/enterprise/rate_limit.md index 6202c5e583b0d..b9db6fbfd7543 100644 --- a/translations/zh-CN/data/reusables/enterprise/rate_limit.md +++ b/translations/zh-CN/data/reusables/enterprise/rate_limit.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -Note that the limits mentioned above are the default rate limits for +请注意，上述限制是 {% data variables.product.product_name %} 上的企业设置来设置公告横幅。 请与站点管理员联系，确认是否启用了速率限制以及如何配置它们。 {% endif %} 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 c03db262a489f..e2468cdaba476 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. 无法将用户提供的 {% data variables.product.prodname_pages %} 内容与其余企业数据分隔。 更多信息请参阅“[为企业配置 {% data variables.product.prodname_pages %}](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/)”。 +**警告：**如果禁用子网分隔，建议同时在企业上禁用 {% data variables.product.prodname_pages %}。 无法将用户提供的 {% 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_installation/hardware-considerations-all-platforms.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 0a7dc3ed9e1e9..c4d45fc7ce872 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [最低要求](#minimum-requirements) -- [{% data variables.product.prodname_ghe_server %} 2.22 中的测试功能](#beta-features-in-github-enterprise-server-222) +- [最低要求](#minimum-requirements){% if currentversion == "enterprise-server@2.22" %} +- [ {% data variables.product.prodname_ghe_server %} 2.22 的测试版功能](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentversion ver_gt "enterprise-server@2.22" %} +- [可选功能](#optional-features){% endif %} - [存储器](#storage) - [CPU 和内存](#cpu-and-memory) @@ -7,18 +8,18 @@ 建议根据 {% data variables.product.product_location %} 的用户许可数选择不同的硬件配置。 如果预配的资源超过最低要求，您的实例将表现出更好的性能和扩展。 -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} 如果您对 {% endif %}{% data variables.product.prodname_actions %} 启用 {% if currentVersion == "enterprise-server@2.22" %}测试版，请查看以下要求和建议。 - 您必须为 {% data variables.product.prodname_actions %} 工作流程配置至少一个运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。 -- 您必须配置外部 Blob 存储。 更多信息请参阅“[启用 {% data variables.product.prodname_actions %} 和配置存储](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)”。 -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. +- 您必须配置外部 Blob 存储。 For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." +- 您可能需要配置额外的 CPU 和内存资源。 需要为 {% data variables.product.prodname_actions %} 预配的额外 CPU 和内存资源取决于用户同时运行的工作流程数量，以及用户活动、自动化和集成的总体水平。 - | 每分钟最大作业数 | Additional vCPUs | Additional memory | - |:-------- | ----------------:| -----------------:| - | 轻型测试 | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | + | 每分钟最大作业数 | 额外的 vCPU | 额外内存 | + |:-------- | --------:| -------:| + | 轻型测试 | 4 | 30.5 GB | + | 25 | 8 | 61 GB | + | 35 | 16 | 122 GB | + | 100 | 32 | 244 GB | {% endif %} @@ -28,9 +29,9 @@ 您的实例需要一个独立于根磁盘的持久数据磁盘。 更多信息请参阅“[系统概述](/enterprise/admin/guides/installation/system-overview)”。 -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -如果您在 {% data variables.product.prodname_ghe_server %} 2.22 中启用 {% data variables.product.prodname_actions %} 的测试版，则需要配置外部 blob 存储。 更多信息请参阅“[启用 {% data variables.product.prodname_actions %} 和配置存储](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)”。 +如果启用{% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %}测试版{% endif %}，则需要配置外部 Blob 存储。 For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md index e528fa16cafce..6ab51e8163525 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. 启用测试功能的实例的最低要求在下表中用**粗体**表示。 For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**注**：如果您在 {% data variables.product.prodname_actions %} 或 {% data variables.product.prodname_registry %} 中启用测试功能，则您的实例需要额外的硬件资源。 {% if currentVersion == "enterprise-server@2.22" %}测试{% else %}可选{% endif %}功能启用的实例的最低要求在下表中**加粗**。 更多信息请参阅“{% if currentVersion == "enterprise-server@2.22" %}[{% data variables.product.prodname_ghe_server %} 2.22 中的测试功能](#beta-features-in-github-enterprise-server-222){% else %}[可选功能](#optional-features){% endif %}”。 {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | +|:----------------- | -------------------------------------------:| ---------------------------------------------------:| ---------------------------------------------------:| ------:| +| 试用版、演示版或 10 个轻度用户 | 2
            或 [**4**](#optional-features) | 16 GB
            或 [**32 GB**](#optional-features) | 100 GB
            或 [**150 GB**](#optional-features) | 200 GB | +| 10-3000 | 4
            或 [**8**](#optional-features) | 32 GB
            或 [**48 GB**](#optional-features) | 250 GB
            或 [**300 GB**](#optional-features) | 200 GB | +| 3000-5000 | 8
            或 [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12
            或 [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16
            或 [**20**](#optional-features) | 128 GB
            或 [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | |:----------------- | -------------------------------------------------------------------------------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------:| ------:| | 试用版、演示版或 10 个轻度用户 | 2{% if currentVersion == "enterprise-server@2.22" %}
            或 [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
            或 [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
            或 [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,14 +26,24 @@ | 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
            或 [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
            或 [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
            或 [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | -For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." +{% endif %} + +有关为现有实例调整资源的更多信息，请参阅“[增加存储容量](/enterprise/admin/installation/increasing-storage-capacity)”和“[增加 CPU 或内存资源](/enterprise/admin/installation/increasing-cpu-or-memory-resources)”。 {% if currentVersion == "enterprise-server@2.22" %} #### {% data variables.product.prodname_ghe_server %} 2.22 中的测试功能 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +您可以注册 {% data variables.product.prodname_ghe_server %} 2.22 中可用的试用功能，例如 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅 {% data variables.product.prodname_enterprise %} 网站上的 [2.22 系列发行说明](https://enterprise.github.com/releases/series/2.22#release-2.22.0)。 + +如果您为 {% data variables.product.prodname_ghe_server %} 2.22 启用测试功能，则您的实例需要额外的硬件资源。 更多信息请参阅“[最低要求](#minimum-requirements)”。 + +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### 可选功能 + +您可以启用 {% data variables.product.prodname_ghe_server %} 的可选功能，如 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %}。 更多信息请参阅“[对 {% data variables.product.prodname_ghe_server %} 开始使用 {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)”或“[对企业开始使用 {% data variables.product.prodname_registry %}](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。 -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +如果启用可选功能，则实例需要额外的硬件资源。 更多信息请参阅“[最低要求](#minimum-requirements)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md index 2a26ad6d64f7a..d97f8b0e52d11 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% if enterpriseServerVersions contains currentVersion %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.product.product_location %}{% endif %}.{% if currentVersion == "github-ae@latest" %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."{% endif %} +**警告：**如果您在拉取请求或议题评论中添加了图像附件，则任何人都可以查看匿名图像 URL，无需身份验证{% if enterpriseServerVersions contains currentVersion %}，即使该拉取请求位于私有仓库中或者启用了私有模式。 为防止未经授权而访问映像，请确保限制从网络访问提供映像的系统，包括 {% data variables.product.product_location %}{% endif %}。{% if currentVersion == "github-ae@latest" %}为防止未经授权而访问 {% data variables.product.product_name %} 上的映像 URL，请考虑限制到企业的网络流量。 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。{% endif %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/actions.md b/translations/zh-CN/data/reusables/enterprise_management_console/actions.md new file mode 100644 index 0000000000000..22fef0dbe17c4 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise_management_console/actions.md @@ -0,0 +1 @@ +1. 在左侧边栏中，单击 **Actions（操作）**。 ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/zh-CN/data/reusables/enterprise_management_console/advanced-security-license.md new file mode 100644 index 0000000000000..32e03e301e684 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise_management_console/advanced-security-license.md @@ -0,0 +1 @@ +If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_advanced_security %} 的许可使您和您的用户能够访问那些有助于提高仓库和代码安全性的功能。 {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md new file mode 100644 index 0000000000000..a82992ae5605f --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md @@ -0,0 +1,5 @@ +{% warning %} + +**警告**：更改此设置将导致 {% 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/enterprise_site_admin_settings/access-settings.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/access-settings.md index 72a1416da36e9..57d4cb43dfbb6 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/access-settings.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/access-settings.md @@ -1 +1 @@ -1. From an administrative account on {% data variables.product.product_name %}, click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page. ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. 从 {% data variables.product.product_name %} 上的管理帐户，点击任何页面右上角的 {% octicon "rocket" aria-label="The rocket ship" %}。 ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png) diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/business.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/business.md index 227f36c0dca4b..8230a9b1cf163 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/business.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/business.md @@ -1 +1 @@ -1. In the left sidebar, click **Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %}**. ![Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %} tab in the Site admin settings](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) +1. 在左侧边栏中，单击 **Enterprise（企业）{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} 概述{% endif %}**。 ![站点管理设置中的 Enterprise（企业）{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}概述{% endif %}选项卡](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/message-preview-save.md new file mode 100644 index 0000000000000..a0e2e8f0517d4 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -0,0 +1,2 @@ +1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. 单击 **Save changes（保存更改）**。 ![Edit message 按钮](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/gated-features/autolinks.md b/translations/zh-CN/data/reusables/gated-features/autolinks.md index d545d6a5b4ac1..780b82804aed2 100644 --- a/translations/zh-CN/data/reusables/gated-features/autolinks.md +++ b/translations/zh-CN/data/reusables/gated-features/autolinks.md @@ -1 +1 @@ -Autolinks are available in repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +自动链接可用于具有 {% 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/code-owners.md b/translations/zh-CN/data/reusables/gated-features/code-owners.md index 3dc4547af8f22..a3903ac5ebc2f 100644 --- a/translations/zh-CN/data/reusables/gated-features/code-owners.md +++ b/translations/zh-CN/data/reusables/gated-features/code-owners.md @@ -1 +1 @@ -You can define code owners in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +您可以在具有 {% 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/code-review-assignment.md b/translations/zh-CN/data/reusables/gated-features/code-review-assignment.md index 009a81f7b4281..c1f8078d9cc3a 100644 --- a/translations/zh-CN/data/reusables/gated-features/code-review-assignment.md +++ b/translations/zh-CN/data/reusables/gated-features/code-review-assignment.md @@ -1 +1 @@ -Code review assignment is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.20+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_cloud %}. 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 +代码审查任务可用于 {% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_server %} 2.20+、{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} 和 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 diff --git a/translations/zh-CN/data/reusables/gated-features/code-scanning.md b/translations/zh-CN/data/reusables/gated-features/code-scanning.md index b55ea29ced940..2bfe160a80ae7 100644 --- a/translations/zh-CN/data/reusables/gated-features/code-scanning.md +++ b/translations/zh-CN/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} 可用于{% if currentVersion == "free-pro-team@latest" %}公共仓库，以及具有{% else %}您有{% endif %} {% data variables.product.prodname_advanced_security %} 许可的组织拥有的私有仓库。 {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} 适用于所有公共仓库以及组织拥有的启用了 {% data variables.product.prodname_GH_advanced_security %} 的所有私有仓库。{% else %}{% data variables.product.prodname_code_scanning_capc %} 在您拥有 {% data variables.product.prodname_GH_advanced_security %} 的许可时可用。{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/zh-CN/data/reusables/gated-features/display-names.md b/translations/zh-CN/data/reusables/gated-features/display-names.md index cc5cbf0481f3c..3e6d82293cb1a 100644 --- a/translations/zh-CN/data/reusables/gated-features/display-names.md +++ b/translations/zh-CN/data/reusables/gated-features/display-names.md @@ -1 +1 @@ -Allowing members to see comment authors' profile names is available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.18+,{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_cloud %}. 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 +允许成员查看评论作者的个人资料名称可用于 {% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_server %} 2.18+、{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[GitHub's products](/articles/githubs-products)”。 diff --git a/translations/zh-CN/data/reusables/gated-features/environments.md b/translations/zh-CN/data/reusables/gated-features/environments.md index 77cd45f6aa02a..916fe9c1d3230 100644 --- a/translations/zh-CN/data/reusables/gated-features/environments.md +++ b/translations/zh-CN/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/pages.md b/translations/zh-CN/data/reusables/gated-features/pages.md index 31caf392d2d37..f3410c13edf22 100644 --- a/translations/zh-CN/data/reusables/gated-features/pages.md +++ b/translations/zh-CN/data/reusables/gated-features/pages.md @@ -1 +1 @@ -{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} is available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}. {% endif %}{% data variables.product.prodname_pages %} is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentversion == "github-ae@latest" %}{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_ghe_managed %} 的内部和私有仓库。 {% 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 %} 和 {% 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 c5b2cde05ba7d..9cbe630494c6f 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 @@ -受保护分支适用于具有 {% 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 %} +{% if currentVersion == "github-ae@latest" %}受保护分支适用于具有 {% data variables.product.prodname_ghe_managed %} 的内部和私有仓库，{% else%} 受保护分支适用于{% 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 %} 和 {% 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/secret-scanning.md b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md index bd279034eee82..47fdb70e58d02 100644 --- a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md +++ b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} 可用于{% if currentVersion == "free-pro-team@latest" %}公共仓库，以及具有{% else %}您有{% endif %} {% data variables.product.prodname_advanced_security %} 许可的组织拥有的私有仓库。 {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/zh-CN/data/reusables/gated-features/wikis.md b/translations/zh-CN/data/reusables/gated-features/wikis.md index d7611dc3638cd..787d0b0b21cb4 100644 --- a/translations/zh-CN/data/reusables/gated-features/wikis.md +++ b/translations/zh-CN/data/reusables/gated-features/wikis.md @@ -1 +1 @@ -{% if currentVersion == "github-ae@latest" %}Wikis are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}.{% endif %} Wikis are available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Wiki 适用于具有 {% data variables.product.prodname_ghe_managed %} 的内部和私有仓库。{% endif %} Wiki 适用于具有 {% 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 %} 和 {% 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/gist/cannot-convert-public-gists-to-secret.md b/translations/zh-CN/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 0d340176f9637..02511f7fd70bc 100644 --- a/translations/zh-CN/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/zh-CN/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -创建 gist 后，无法将其从公共转换为机密。 +在创建 Gist 后，不可将其从{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}转换为机密。 diff --git a/translations/zh-CN/data/reusables/github-actions/actions-billing.md b/translations/zh-CN/data/reusables/github-actions/actions-billing.md index 027a6b7f42402..18766c9e7c126 100644 --- a/translations/zh-CN/data/reusables/github-actions/actions-billing.md +++ b/translations/zh-CN/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -公共仓库和自托管运行器免费使用 {% data variables.product.prodname_actions %}。 对于私有仓库，每个 {% data variables.product.prodname_dotcom %} 帐户可获得一定数量的免费记录和存储，具体取决于帐户所使用的产品。 Any usage beyond the included amounts is controlled by spending limits. +公共仓库和自托管运行器免费使用 {% data variables.product.prodname_actions %}。 对于私有仓库，每个 {% data variables.product.prodname_dotcom %} 帐户可获得一定数量的免费记录和存储，具体取决于帐户所使用的产品。 超出包含金额的任何使用量都由支出限制控制。 diff --git a/translations/zh-CN/data/reusables/github-actions/contacting-support.md b/translations/zh-CN/data/reusables/github-actions/contacting-support.md index b86167e223483..ebb1a98546f59 100644 --- a/translations/zh-CN/data/reusables/github-actions/contacting-support.md +++ b/translations/zh-CN/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). +如果需要任何与工作流程配置相关的帮助，比如语法、{% data variables.product.prodname_dotcom %} 托管的运行器或构建操作，请在 [{% data variables.product.prodname_gcf %} 的 {% data variables.product.prodname_actions %} 类别](https://github.community/c/code-to-cloud/github-actions/41)中查找现有主题或发起一个新主题。 如果您有对 {% data variables.product.prodname_actions %} 的反馈或功能请求，请在 {% data variables.contact.contact_feedback_actions %} 中分享。 diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md index 23430339496cf..fbde5b5afcb7b 100644 --- a/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 +运行 `mvn --batch-mode deploy` 命令以发布到 `ossrh` 仓库。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md index e025f2b31f7c6..04aeb59a73b14 100644 --- a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 +运行 `mvn --batch-mode deploy` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 21decb40c1118..eba8f92c9841b 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,5 +1,5 @@ 1. 在设置页面的 **Self-hosted runners（自托管运行器）**部分，单击要配置的运行器组旁边的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit name and [organization|repository] access（编辑名称和[组织|仓库]权限）**。 ![管理仓库权限](/assets/images/help/settings/actions-runner-manage-permissions.png) -1. Modify your policy options, or change the runner group name. +1. 修改策略选项，或更改运行器组名称。 {% warning %} diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-public-repo-access.md new file mode 100644 index 0000000000000..c8e6452ad00f0 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。 + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/zh-CN/data/reusables/github-actions/using-context-or-environment-variables.md new file mode 100644 index 0000000000000..62acfaedf853c --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/using-context-or-environment-variables.md @@ -0,0 +1,21 @@ +{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: + +- **Default environment variables:** These variables exist only on the runner that is executing your job. 更多信息请参阅“[默认环境变量](/actions/reference/environment-variables#default-environment-variables)”。 +- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. 更多信息请参阅“[上下文](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)”。 + +The following example demonstrates how these different types of environment variables can be used together in a job: + +{% raw %} +```yaml +name: CI +on: push +jobs: + prod-check: + if: github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - run: echo "Deploying to production server on branch $GITHUB_REF" +``` +{% endraw %} + +In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. diff --git a/translations/zh-CN/data/reusables/github-insights/download-latest-release.md b/translations/zh-CN/data/reusables/github-insights/download-latest-release.md index e480cb08d5cee..96001975b4194 100644 --- a/translations/zh-CN/data/reusables/github-insights/download-latest-release.md +++ b/translations/zh-CN/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. +1. 从应用程序服务器中 `github/insights-releases` 的发行版页面上，找到 {% data variables.product.prodname_insights %} 的最新版本。 2. 要下载最新版本，请在“Assets（资产）”下单击 `insights-VERSION.tar.gz`。 ![安装资产](/assets/images/help/insights/installation-tgz.png) 3. 解压缩目录。 diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/zh-CN/data/reusables/identity-and-permissions/revoking-identity-team-sync.md new file mode 100644 index 0000000000000..b2c935e89352e --- /dev/null +++ b/translations/zh-CN/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." + +{% endwarning %} diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm.md index 8990f72d8fc2f..42e0918e75e3a 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. 要确认团队同步： +5. 确认团队同步。 - 如果您有 IdP 访问权限，则单击 **Enable team synchronization（启用团队同步）**。 您将被重定向到身份提供程序的 SAML SSO 页面，并要求选择您的帐户和查看请求的权限。 - 如果您没有 IdP 访问权限，请复制 IdP 重定向链接并将其与您的 IdP 管理员共享以继续启用团队同步。 ![启用团队同步重定向按钮](/assets/images/help/teams/confirm-team-synchronization-redirect.png) 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 03bb8da83e29a..14b5628283a65 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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 您可以选择是否 您可以选择是否将 {% 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/marketplace/launch-with-free.md b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md index 2151c241cce9b..16053ece27e75 100644 --- a/translations/zh-CN/data/reusables/marketplace/launch-with-free.md +++ b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +您可以请求发布，无论是否经过验证。 无需验证即可请求发布，可以快速启动应用程序的免费版本。 如果您随后请求发布并验证，则当您完成验证和财务入职时，您的列表将更新，以包括已验证的创建者徽章和任何付费定价计划。 diff --git a/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md index b5936198c3da1..e7bc045680e19 100644 --- a/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} 强烈建议允许客户重新启用他们以前的计划。 -- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` -- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. -- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: +- 取消从 {% data variables.product.prodname_marketplace %} 购买的付费计划的客户应自动降级到该应用程序的免费计划（如果有）。 {% data reusables.marketplace.cancellation-clarification %} 强烈建议允许客户重新启用他们以前的计划。 +- 如果您用以下格式提供[升级 URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls)，客户应能从应用程序的用户界面升级：`https://www.github.com/marketplace//upgrade//` +- 如果客户购买了席位（单位定价计划）或支持无限协作者的计划，他们应该能够修改哪些用户可以从应用程序的网站访问应用程序。 +- 客户应该能够在应用程序网站的帐单、个人资料或帐户设置部分立即看到其帐户的以下变动： - 当前计划和价格。 - 购买的新计划。 - 升级、降级、取消以及免费试用剩余天数。 diff --git a/translations/zh-CN/data/reusables/mobile/about-mobile.md b/translations/zh-CN/data/reusables/mobile/about-mobile.md new file mode 100644 index 0000000000000..3f4846f7a9b92 --- /dev/null +++ b/translations/zh-CN/data/reusables/mobile/about-mobile.md @@ -0,0 +1 @@ +{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/zh-CN/data/reusables/mobile/ghes-release-phase.md b/translations/zh-CN/data/reusables/mobile/ghes-release-phase.md new file mode 100644 index 0000000000000..57edb6b54aa50 --- /dev/null +++ b/translations/zh-CN/data/reusables/mobile/ghes-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/mobile/push-notifications-on-ghes.md b/translations/zh-CN/data/reusables/mobile/push-notifications-on-ghes.md new file mode 100644 index 0000000000000..94535c20d34b7 --- /dev/null +++ b/translations/zh-CN/data/reusables/mobile/push-notifications-on-ghes.md @@ -0,0 +1 @@ +For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md b/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md index 732a48aff3547..09e5326dac4dd 100644 --- a/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md +++ b/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} {% note %} -**Note**: You'll only receive email notifications if outbound email support is enabled on {% data variables.product.product_location %}. 更多信息请联系站点管理员。 +**注**：如果在 {% data variables.product.product_location %} 上启用了出站电子邮件支持，您将只收到邮件通知。 更多信息请联系站点管理员。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/notifications/shared_state.md b/translations/zh-CN/data/reusables/notifications/shared_state.md index 541fa5ae554a1..28837e167bc4a 100644 --- a/translations/zh-CN/data/reusables/notifications/shared_state.md +++ b/translations/zh-CN/data/reusables/notifications/shared_state.md @@ -1,5 +1,5 @@ {% tip %} -**提示：**如果您同时接收 Web 和电子邮件通知，您可以自动同步通知的已读或未读状态，以便在您阅读相应的电子邮件通知后，Web 通知自动标记为已读。 To enable this sync, your email client must be able to view images from {% if currentVersion == "free-pro-team@latest" %}`notifications@github.com`{% else %}the `no-reply` email address {% if currentVersion == "github-ae@latest" %}for your {% data variables.product.product_name %} hostname{% elsif enterpriseServerVersions contains currentVersion %}for {% data variables.product.product_location %}, which your site administrator configures{% endif %}{% endif %}. +**提示：**如果您同时接收 Web 和电子邮件通知，您可以自动同步通知的已读或未读状态，以便在您阅读相应的电子邮件通知后，Web 通知自动标记为已读。 要启用此同步，您的电子邮件客户端必须能够查看来自 {% if currentVersion == "free-pro-team@latest" %}`notifications@github.com`{% else %} `无需回复`电子邮件地址 {% if currentVersion == "github-ae@latest" %}您的 {% data variables.product.product_name %} 主机名{% elsif enterpriseServerVersions contains currentVersion %}您的 {% data variables.product.product_location %}（您的站点管理员可以配置）{% endif %}{% endif %}的图像。 {% endtip %} diff --git a/translations/zh-CN/data/reusables/organizations/click-codespaces.md b/translations/zh-CN/data/reusables/organizations/click-codespaces.md new file mode 100644 index 0000000000000..6a15dd7757d6f --- /dev/null +++ b/translations/zh-CN/data/reusables/organizations/click-codespaces.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/zh-CN/data/reusables/organizations/team-synchronization.md b/translations/zh-CN/data/reusables/organizations/team-synchronization.md index 5c4ee9747c90a..51138ff03f485 100644 --- a/translations/zh-CN/data/reusables/organizations/team-synchronization.md +++ b/translations/zh-CN/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -您可以使用团队同步通过身份提供程序自动添加和删除组织中的团队成员。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +您可以使用团队同步通过身份提供程序自动添加和删除团队中的组织成员。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 {% 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 9ca5a7c5e6777..3f255bab1b610 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 %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 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/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 要使用 {% data variables.product.prodname_github_container_registry %}，您必须启用功能预览。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)”和“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/zh-CN/data/reusables/package_registry/enable-enterprise-github-packages.md new file mode 100644 index 0000000000000..e1733916de65f --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -0,0 +1,3 @@ +{% if currentVersion ver_gt "enterprise-server@2.22" %} +1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +{% endif %} diff --git a/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md new file mode 100644 index 0000000000000..f9080682a0ec5 --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -0,0 +1,3 @@ +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." + +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/zh-CN/data/reusables/package_registry/packages-billing.md b/translations/zh-CN/data/reusables/package_registry/packages-billing.md index 3d870ad218cbe..37af1cd889aeb 100644 --- a/translations/zh-CN/data/reusables/package_registry/packages-billing.md +++ b/translations/zh-CN/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -公共包免费使用 {% data variables.product.prodname_registry %}。 对于私有包，每个 {% data variables.product.product_name %} 帐户可获得一定数量的免费存储和数据传输，具体取决于帐户所使用的产品。 Any usage beyond the included amounts is controlled by spending limits. +公共包免费使用 {% data variables.product.prodname_registry %}。 对于私有包，每个 {% data variables.product.product_name %} 帐户可获得一定数量的免费存储和数据传输，具体取决于帐户所使用的产品。 超出包含金额的任何使用量都由支出限制控制。 diff --git a/translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md b/translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md new file mode 100644 index 0000000000000..cb1e4bbb4e3c5 --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md @@ -0,0 +1,7 @@ +{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. + +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/zh-CN/data/reusables/package_registry/packages-ghes-release-stage.md index 38654cd2a5a89..d06f85c752721 100644 --- a/translations/zh-CN/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/zh-CN/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**注：** {% data variables.product.prodname_registry %} 目前正在测试用于 {% data variables.product.prodname_ghe_server %} 2.22。 要加入您的实例的测试版，请使用[注册表单](https://resources.github.com/beta-signup/)。 +**注：** {% data variables.product.prodname_registry %} 目前正在测试用于 {% data variables.product.prodname_ghe_server %} 2.22。 要加入 {% data variables.product.product_location %} 的测试版，请使用[注册表单](https://resources.github.com/beta-signup/)。 {% endnote %} {% endif %} 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 27cc3feb0b442..78e3599281641 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 %} - **警告**：{% 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)." + **警告**：{% 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 %}。 如果站点的仓库中有敏感数据，您可能想要在发布前删除它。 更多信息请参阅{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}“[为企业配置 {% data variables.product.prodname_pages %}](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)”和{% endif %}“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/pre-release-program/suspend-installation-beta.md b/translations/zh-CN/data/reusables/pre-release-program/suspend-installation-beta.md index 2a94ae254476e..7e13dfdd8fd7c 100644 --- a/translations/zh-CN/data/reusables/pre-release-program/suspend-installation-beta.md +++ b/translations/zh-CN/data/reusables/pre-release-program/suspend-installation-beta.md @@ -1 +1 @@ -Suspending a {% data variables.product.prodname_github_app %} installation is currently in beta and subject to change. 在可以挂起 {% data variables.product.prodname_github_app %} 之前，应用程序所有者必须通过选择加入测试版来启用挂起应用程序的安装。 要选择加入挂起安装测试版功能，请参阅“[激活应用程序的测试版功能](/developers/apps/activating-beta-features-for-apps)”。 +挂起 {% data variables.product.prodname_github_app %} 安装目前处于测试阶段，可能会更改。 在可以挂起 {% data variables.product.prodname_github_app %} 之前，应用程序所有者必须通过选择加入测试版来启用挂起应用程序的安装。 要选择加入挂起安装测试版功能，请参阅“[激活应用程序的测试版功能](/developers/apps/activating-beta-features-for-apps)”。 diff --git a/translations/zh-CN/data/reusables/profile/profile-readme.md b/translations/zh-CN/data/reusables/profile/profile-readme.md index 630be86909f9e..d71cd853f843a 100644 --- a/translations/zh-CN/data/reusables/profile/profile-readme.md +++ b/translations/zh-CN/data/reusables/profile/profile-readme.md @@ -1 +1 @@ -如果将 README 文件添加到与用户名同名的公共仓库的根目录，则该 README 将自动显示在您的个人资料页面上。 You can edit your profile README with {% data variables.product.company_short %} Flavored Markdown to create a personalized section on your profile. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." +如果将 README 文件添加到与用户名同名的公共仓库的根目录，则该 README 将自动显示在您的个人资料页面上。 您可以使用 {% data variables.product.company_short %} Flavored Markdown 编辑您的个人资料以在您的个人资料 README，以在您的个人资料上创建个性化的区域。 更多信息请参阅“[管理个人资料自述文件](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。 diff --git a/translations/zh-CN/data/reusables/project-management/choose-visibility.md b/translations/zh-CN/data/reusables/project-management/choose-visibility.md new file mode 100644 index 0000000000000..5bcea696d10ba --- /dev/null +++ b/translations/zh-CN/data/reusables/project-management/choose-visibility.md @@ -0,0 +1 @@ +1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. 更多信息请参阅“[更改项目板可见性](/github/managing-your-work-on-github/changing-project-board-visibility)”。 ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/zh-CN/data/reusables/project-management/project-board-visibility.md b/translations/zh-CN/data/reusables/project-management/project-board-visibility.md index f0085053538fb..aa02576e2d42a 100644 --- a/translations/zh-CN/data/reusables/project-management/project-board-visibility.md +++ b/translations/zh-CN/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -默认情况下，您的项目板为私有，只有对项目板具有读取、写入或管理权限的人才能看到。 公共项目板对有项目板 URL 的任何人都可见。 +默认情况下，您的项目板为私有，只有对项目板具有读取、写入或管理权限的人才能看到。 {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md index d02007d8bb449..9a19aa03c106e 100644 --- a/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -1,6 +1,6 @@ {% note %} -**Notes:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +**注：**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - 要显示在您的个人资料贡献图中，合作提交必须符合与只有一个作者的提交相同的条件。{% endif %} - 在变基提交时，提交的原作者和提交的变基者（无论是在命令行还是 {% data variables.product.product_location %} 上）都会获得贡献积分。 diff --git a/translations/zh-CN/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/zh-CN/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index effd87279c4fa..b990892b3c3c9 100644 --- a/translations/zh-CN/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/zh-CN/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -如果需要对仓库进行状态检查，必须通过所需的状态检查后，您才可将分支合并到受保护分支。 更多信息请参阅“[关于必要的状态检查](/articles/about-required-status-checks)”。 +如果需要对仓库进行状态检查，必须通过所需的状态检查后，您才可将分支合并到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 diff --git a/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md index b67d4fba25e5d..3526e39a78da3 100644 --- a/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -仓库管理员可以要求所有合并请求在合并到受保护分支之前，获取必要数量的具有仓库*写入*或*管理*权限的人员或者指定代码所有者的批准。 更多信息请参阅“[关于受保护分支](/articles/about-protected-branches)”。 - -启用所需的审查时，具有仓库访问权限的任何人都可以批准拉取请求中的更改。 但若没有必要数量的具有仓库*写入*或*管理*权限的审查者批准您的拉取请求，您将无法合并拉取请求。 有关仓库权限级别的更多信息，请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization/)”。 如果要求获得指定代码所有者的审查，并且拉取请求会影响具有指定所有者的代码， 则需要该所有者的批准。 +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md b/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md index 410aec2a8ee8c..a5bcbffeae34c 100644 --- a/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." +You can configure a pull request to merge automatically when all merge requirements are met. 更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/about-internal-repos.md b/translations/zh-CN/data/reusables/repositories/about-internal-repos.md index 61358584cde6b..056c87b95066c 100644 --- a/translations/zh-CN/data/reusables/repositories/about-internal-repos.md +++ b/translations/zh-CN/data/reusables/repositories/about-internal-repos.md @@ -1 +1 @@ -You can use internal repositories to practice "innersource" within your enterprise. Members of your enterprise can collaborate using open source methodologies without sharing proprietary information publicly{% if enterpriseServerVersions contains currentVersion %}, even with private mode disabled{% endif %}. +您可以使用内部仓库充分利用企业中的“内部资源”。 企业的成员可使用开源方法进行协作，而无需公开共享专有信息{% if enterpriseServerVersions contains currentVersion %}，即使禁用了私有模式{% endif %}。 diff --git a/translations/zh-CN/data/reusables/repositories/branch-rules-example.md b/translations/zh-CN/data/reusables/repositories/branch-rules-example.md index f2bed6d72d26d..ea81704455211 100644 --- a/translations/zh-CN/data/reusables/repositories/branch-rules-example.md +++ b/translations/zh-CN/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -您可以在仓库中为特定分支、所有分支或者与使用 fnmatch 语法指定的命名模式匹配的任何分支创建分支规则。 例如，若要求包含文字 `release` 的任何分支在合并之前至少有两次拉取请求审查，则可为 `*release*` 创建分支规则。 +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/zh-CN/data/reusables/repositories/copy-clone-url.md b/translations/zh-CN/data/reusables/repositories/copy-clone-url.md index fd2e7172ae5be..0b6da2ae142e5 100644 --- a/translations/zh-CN/data/reusables/repositories/copy-clone-url.md +++ b/translations/zh-CN/data/reusables/repositories/copy-clone-url.md @@ -8,7 +8,7 @@ {% else %} 1. 在文件列表上方，单击 {% octicon "download" aria-label="The download icon" %} ****Code（代码）。 !["代码"按钮](/assets/images/help/repository/code-button.png) 1. 要使用 HTTPS 克隆仓库，请在“Clone with HTTPS（使用 HTTPS 克隆）”下单击 -{% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% endif %} +{% octicon "clippy" aria-label="The clipboard icon" %}. 要使用 SSH 密钥克隆仓库，包括由组织的 SSH 证书颁发机构颁发的证书，请单击 **Use SSH（使用 SSH）**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} 要使用 {% data variables.product.prodname_cli %} 克隆仓库，请单击**使用 {% data variables.product.prodname_cli %}**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。{% endif %} ![用于复制 URL 以克隆仓库的剪贴板图标](/assets/images/help/repository/https-url-clone.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ![用于复制 URL 以使用 GitHub CLI 克隆仓库的剪贴板图标](/assets/images/help/repository/https-url-clone-cli.png){% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/create-repo.md b/translations/zh-CN/data/reusables/repositories/create-repo.md index 59c1040772409..a630c0dc92419 100644 --- a/translations/zh-CN/data/reusables/repositories/create-repo.md +++ b/translations/zh-CN/data/reusables/repositories/create-repo.md @@ -1 +1 @@ -1. Click **Create repository**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} +1. 单击 **Create repository（创建仓库）**。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/default-issue-templates.md b/translations/zh-CN/data/reusables/repositories/default-issue-templates.md index 23f337b33e0fb..0284568990528 100644 --- a/translations/zh-CN/data/reusables/repositories/default-issue-templates.md +++ b/translations/zh-CN/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1,2 @@ -You can create default issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and a default configuration file for issue templates{% endif %} for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or user account{% endif %}. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以创建默认的议题模板{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 和议题模板的默认配置文件{% endif %}，适用于您的组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或用户帐户{% endif %}。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 diff --git a/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 4f0d2ab6c58fb..2a01a2e977a34 100644 --- a/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - 当 [LDAP 同步启用](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync)后，如果从仓库删除某用户，此用户将失去访问权，但其复刻不会被删除。 如果此用户在三个月内被加入具有原组织仓库访问权限的团队，则其对复刻的访问权限将在下次同步时自动恢复。{% endif %} - 您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 -- People with admin permissions to a private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository can disallow forking of that repository, and organization owners can disallow forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository in an organization. 更多信息请参阅“[管理组织的复刻政策](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)”和“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。 +- 对私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库拥有管理员权限的人可以禁止对该仓库进行复刻，组织所有者可以禁止对组织中的任何私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)”和“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/repositories/dependency-review.md b/translations/zh-CN/data/reusables/repositories/dependency-review.md index e780074c3c8eb..45f0101765546 100644 --- a/translations/zh-CN/data/reusables/repositories/dependency-review.md +++ b/translations/zh-CN/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ {% if currentVersion == "free-pro-team@latest" %} Additionally, -{% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/desktop-fork.md b/translations/zh-CN/data/reusables/repositories/desktop-fork.md index d26ecea68a150..ae2f30e9a98d2 100644 --- a/translations/zh-CN/data/reusables/repositories/desktop-fork.md +++ b/translations/zh-CN/data/reusables/repositories/desktop-fork.md @@ -1 +1 @@ -您可以使用 {% data variables.product.prodname_desktop %} 复刻仓库。 For more information, see "[Cloning and forking repositories from {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)." +您可以使用 {% data variables.product.prodname_desktop %} 复刻仓库。 更多信息请参阅“[从 {% data variables.product.prodname_desktop %} 克隆和复刻仓库](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)”。 diff --git a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md index 426c78df94379..6576ea2523bb0 100644 --- a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md +++ b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion %} 您的站点管理员必须启用 -{% data variables.product.product_location %} 的漏洞依赖项的{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报，然后您才可使用此功能。 For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% data variables.product.product_location %} 的漏洞依赖项的{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报，然后您才可使用此功能。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/return-to-source-diff.md b/translations/zh-CN/data/reusables/repositories/return-to-source-diff.md new file mode 100644 index 0000000000000..c918830348fb3 --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/return-to-source-diff.md @@ -0,0 +1,5 @@ +1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. + + To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md index deafaa6191ae5..cfe413d8a0cef 100644 --- a/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -在所有必需的审查者批准某个拉取请求后，如果其他打开的拉取请求具有待定或被拒绝的审查，并且这些拉取请求有头部分支指向同一提交，则您无法合并该拉取请求。 具有*写入*或*管理员*权限的人需要批准或忽略其他拉取请求的阻止审查，然后您才可以合并。 +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/zh-CN/data/reusables/repositories/security-alert-delivery-options.md b/translations/zh-CN/data/reusables/repositories/security-alert-delivery-options.md index 7a4c6593ae543..bbe51e1cb3bcc 100644 --- a/translations/zh-CN/data/reusables/repositories/security-alert-delivery-options.md +++ b/translations/zh-CN/data/reusables/repositories/security-alert-delivery-options.md @@ -1,4 +1,4 @@ {% if currentVersion != "github-ae@latest" %} -If your repository has a supported dependency manifest -{% if currentVersion == "free-pro-team@latest" %} (and if you've set up the dependency graph if it's a private repository){% endif %}, whenever {% data variables.product.product_name %} detects a vulnerable dependency in your repository, you will receive a weekly digest email. 您也可以在 {% data variables.product.product_name %} 界面中将安全警报配置为 web 通知、单个电子邮件通知、每日电子邮件摘要或警报。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +如果您的仓库具有受支持的依赖项清单 +{% if currentVersion == "free-pro-team@latest" %}（并且对私有仓库设置了依赖图）{% endif %}，则只要 {% data variables.product.product_name %} 检测到仓库中易受攻击的依赖项，您就会收到每周摘要电子邮件。 您也可以在 {% data variables.product.product_name %} 界面中将安全警报配置为 web 通知、单个电子邮件通知、每日电子邮件摘要或警报。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md index ee168c3ae24e5..100ac3c323d76 100644 --- a/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md +++ b/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md @@ -1 +1 @@ -1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![{% data variables.product.prodname_dependabot_alerts %} 选项卡](/assets/images/help/repository/dependabot-alerts-tab.png) +1. 在安全侧边栏中，单击 **{% data variables.product.prodname_dependabot_alerts %}**。 ![{% data variables.product.prodname_dependabot_alerts %} 选项卡](/assets/images/help/repository/dependabot-alerts-tab.png) diff --git a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index f42e7d220d55b..1562d46e0c503 100644 --- a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. 更多信息请参阅“[需要线性提交历史记录](/github/administering-a-repository/requiring-a-linear-commit-history)”。{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}如果你的仓库中有需要线性提交历史记录的受保护分支规则，必须允许压缩合并和/或变基合并。 For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/start-line-comment.md b/translations/zh-CN/data/reusables/repositories/start-line-comment.md index 35a6f09a2ca76..60f48a02c4124 100644 --- a/translations/zh-CN/data/reusables/repositories/start-line-comment.md +++ b/translations/zh-CN/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon.{% endif %} ![蓝色评论图标](/assets/images/help/commits/hover-comment-icon.gif) +1. 将鼠标悬停在您要添加评论的代码行上，然后单击蓝色评论图标。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 要在多行上添加评论，请单击并拖动以选择行范围，然后单击蓝色评论图标。{% endif %} ![蓝色评论图标](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/zh-CN/data/reusables/repositories/suggest-changes.md b/translations/zh-CN/data/reusables/repositories/suggest-changes.md index 1508f264688aa..456734497feda 100644 --- a/translations/zh-CN/data/reusables/repositories/suggest-changes.md +++ b/translations/zh-CN/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. Optionally, to suggest a specific change to the line{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![建议块](/assets/images/help/pull_requests/suggestion-block.png) +1. （可选）要建议对一行{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} 或多行{% endif %} 进行特定更改，请单击 {% octicon "diff" aria-label="The diff symbol" %}，然后在建议块内编辑文本。 ![建议块](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 1a25944892803..e0fad7b0e7d90 100644 --- a/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. +例如，此 URL 使用简短的 7 字符 SHA 代码比较提交 `c3a414e` 与 `faf7c6f`：`https://github.com/github/linguist/compare/c3a414e..faf7c6f`。 diff --git a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md index d0fc38b567abe..0645c355d90c7 100644 --- a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md +++ b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ 如果为 {% data variables.product.prodname_actions %} 启用电子邮件或 web 通知，则在触发的任何工作流程运行完成时，您将收到通知。 通知将包括工作流程运行的状态（包括成功、失败、中立和取消的运行）。 您也可以选择仅在工作流程运行失败时接收通知。 +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + 您也可以在仓库的 Actions（操作）选项卡上查看工作流程的状态。 更多信息请参阅“[管理工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)”。 diff --git a/translations/zh-CN/data/reusables/repositories/you-can-fork.md b/translations/zh-CN/data/reusables/repositories/you-can-fork.md index 79505c5db733c..4d7a785609098 100644 --- a/translations/zh-CN/data/reusables/repositories/you-can-fork.md +++ b/translations/zh-CN/data/reusables/repositories/you-can-fork.md @@ -1,7 +1,7 @@ -{% if currentVersion == "github-ae@latest" %}If the policies for your enterprise permit forking internal and private repositories, you{% else %}You{% endif %} can fork a repository to your user account or any organization where you have repository creation permissions. 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 +{% if currentVersion == "github-ae@latest" %}如果企业的策略允许复刻内部和私有仓库{% else %}您{% endif %}可以将仓库复刻到您的用户帐户或具有仓库创建权限的任何组织。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -If you have access to a private repository and the owner permits forking, you can fork the repository to your user account or any organization on {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} where you have repository creation permissions. {% if currentVersion == "free-pro-team@latest" %}You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}. For more information, see "[GitHub's products](/articles/githubs-products)."{% endif %} +如果您可以访问私有仓库且所有者允许复刻，则您可以将该仓库复刻到您的用户帐户或者 {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} 上您具有仓库创建权限的任何组织。 {% if currentversion == "free proteam@latest" %}您不能将私有仓库复刻到使用 {% data variables.product.prodname_free_team %} 的组织。 更多信息请参阅“[GitHub 的产品](/articles/githubs-products)”。{% endif %} {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/zh-CN/data/reusables/saml/about-saml-enterprise-accounts.md new file mode 100644 index 0000000000000..fce7bd28eea6e --- /dev/null +++ b/translations/zh-CN/data/reusables/saml/about-saml-enterprise-accounts.md @@ -0,0 +1 @@ +企业所有者可以通过 SAML IdP 跨企业帐户拥有的所有组织启用 SAML SSO 和集中式身份验证。 为企业帐户启用 SAML SSO 后，默认情况下会为您的企业帐户拥有的所有组织启用 SAML SSO。 所有成员都需要使用 SAML SSO 进行身份验证才能访问其所属的组织，并且企业所有者在访问企业帐户时需要使用 SAML SSO 进行身份验证。 diff --git a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md index 59a8d4c96c059..be784eeb4f31c 100644 --- a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML SSO 为 {% data variables.product.prodname_dotcom %} 上的组织所有者和企业所有者提供一种控制安全访问仓库、议题和拉取请求等组织资源的方法。 +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/zh-CN/data/reusables/search/date_gt_lt.md b/translations/zh-CN/data/reusables/search/date_gt_lt.md index 57a206f28cbd5..a8b36a6c46a80 100644 --- a/translations/zh-CN/data/reusables/search/date_gt_lt.md +++ b/translations/zh-CN/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." +搜索日期时，可以使用大于、小于和范围限定符来进一步筛选结果。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 diff --git a/translations/zh-CN/data/reusables/search/required_login.md b/translations/zh-CN/data/reusables/search/required_login.md index 6d8598a94a38a..b6ae1604f3623 100644 --- a/translations/zh-CN/data/reusables/search/required_login.md +++ b/translations/zh-CN/data/reusables/search/required_login.md @@ -1 +1 @@ -You must be signed into a user account on {% data variables.product.product_name %} to search for code across all public repositories. +您必须登录到 {% data variables.product.product_name %} 上的用户帐户才能在所有公共仓库中搜索代码。 diff --git a/translations/zh-CN/data/reusables/search/syntax_tips.md b/translations/zh-CN/data/reusables/search/syntax_tips.md index 05e65d415ae9f..2cd8147263e74 100644 --- a/translations/zh-CN/data/reusables/search/syntax_tips.md +++ b/translations/zh-CN/data/reusables/search/syntax_tips.md @@ -1,7 +1,7 @@ {% tip %} -**Tips:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.product.product_location %}.{% endif %} +**提示：**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + - 本文章包含 {% data variables.product.prodname_dotcom_the_website %} 网站上示例搜索的链接，但您可以对 {% data variables.product.product_name %} 使用相同的搜索过滤器。 在链接的示例搜索中，将 `github.com` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} - 有关可以添加到任何搜索限定符以进一步改善结果的搜索语法列表，请参阅“[了解搜索语法](/articles/understanding-the-search-syntax)”。 - 对多个字词的搜索词使用引号。 例如，如果要搜索具有标签 "In progress" 的议题，可搜索 `label:"in progress"`。 搜索不区分大小写。 diff --git a/translations/zh-CN/data/reusables/secret-scanning/about-secret-scanning.md b/translations/zh-CN/data/reusables/secret-scanning/about-secret-scanning.md new file mode 100644 index 0000000000000..51b8c7a7d10a0 --- /dev/null +++ b/translations/zh-CN/data/reusables/secret-scanning/about-secret-scanning.md @@ -0,0 +1 @@ +If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md index 5f853efcb3eb6..82fdadded9388 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**注：**私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于公测阶段，可能会有变动。 +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md new file mode 100644 index 0000000000000..ad53fa8b216c3 --- /dev/null +++ b/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -0,0 +1,9 @@ +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + +{% note %} + +**注：**站点管理员必须为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_secret_scanning %}，然后您才可使用此功能。 更多信息请参阅“[为设备配置 {% data variables.product.prodname_secret_scanning %}](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)”。 + +{% endnote %} + +{% endif %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md new file mode 100644 index 0000000000000..8e221eef6d759 --- /dev/null +++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -0,0 +1,70 @@ +| Partner | Supported secret | API slug | +| ------------------------- | -------------------------------------- | ---------------------------------------- | +| n/a | JSON Web Token | json_web_token | +| n/a | OAuth Client Credential | api_credential_assignment | +| Adafruit IO | Adafruit IO Key | adafruit_io_key | +| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | +| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | +| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | +| Atlassian | Atlassian API Token | atlassian_api_token | +| Atlassian | Atlassian JSON Web Token | atlassian_jwt | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | clojars_deploy_token | +| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | +| Databricks | Databricks Access Token | databricks_access_token | +| Discord | Discord Bot Token | discord_bot_token | +| Doppler | Doppler Personal Token | doppler_personal_token | +| Doppler | Doppler Service Token | doppler_service_token | +| Doppler | Doppler CLI Token | doppler_cli_token | +| Doppler | Doppler SCIM Token | doppler_scim_token | +| Dropbox | Dropbox Access Token | dropbox_access_token | +| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | +| Dynatrace | Dynatrace Access Token | dynatrace_access_token | +| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | +| Finicity | Finicity App Key | finicity_app_key | +| Frame.io | Frame.io JSON Web Token | frameio_jwt | +| Frame.io | Frame.io Developer Token | frameio_developer_token | +| GitHub | GitHub SSH Private Key | github_ssh_private_key | +| GitHub | GitHub Personal Access Token | github_personal_access_token | +| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | +| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | +| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | +| Google Cloud | Google API Key | google_api_key | +| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | +| Hubspot | Hubspot API Key | hubspot_api_key | +| Mailchimp | Mailchimp API Key | mailchimp_api_key | +| Mailgun | Mailgun API Key | mailgun_api_key | +| npm | npm Access Token | npm_access_token | +| NuGet | NuGet API Key | nuget_api_key | +| Palantir | Palantir JSON Web Token | palantir_jwt | +| Postman | Postman API Key | postman_api_key | +| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | +| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | +| Proctorio | Proctorio Registration Key | proctorio_registration_key | +| Proctorio | Proctorio Secret Key | proctorio_secret_key | +| Pulumi | Pulumi Access Token | pulumi_access_token | +| Samsara | Samsara API Token | samsara_api_token | +| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | +| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | +| Shopify | Shopify Access Token | shopify_access_token | +| Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token | +| Shopify | Shopify Private App Password | shopify_private_app_password | +| Slack | Slack API Token | slack_api_token | +| Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url | +| Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url | +| SSLMate | SSLMate API Key | sslmate_api_key | +| SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret | +| Stripe | Stripe API Key | stripe_api_key | +| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | +| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | +| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | +| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | +| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | +| Twilio | Twilio Account String Identifier | twilio_account_sid | +| Twilio | Twilio API Key | twilio_api_key | diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md new file mode 100644 index 0000000000000..c6d391e3b62aa --- /dev/null +++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -0,0 +1,69 @@ +| Partner | Supported secret | +| ------------------------- | --------------------------------------------------------------------------- | +| Adafruit IO | Adafruit IO Key | +| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | +| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | +| Atlassian | Atlassian API Token | +| Atlassian | Atlassian JSON Web Token | +| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | +| Azure | Azure SAS Token | azure_sas_token | +| Azure | Azure Service Management Certificate | azure_management_certificate | +| Azure | Azure SQL Connection String | azure_sql_connection_string | +| Azure | Azure Storage Account Key | azure_storage_account_key | +| Clojars | Clojars Deploy Token | +| CloudBees CodeShip | CloudBees CodeShip Credential | +| Databricks | Databricks Access Token | +| Datadog | Datadog API Key | +| Discord | Discord Bot Token | +| Doppler | Doppler Personal Token | +| Doppler | Doppler Service Token | +| Doppler | Doppler CLI Token | +| Doppler | Doppler SCIM Token | +| Dropbox | Dropbox Access Token | +| Dropbox | Dropbox Short Lived Access Token | +| Dynatrace | Dynatrace Access Token | +| Dynatrace | Dynatrace Internal Token | +| Finicity | Finicity App Key | +| Frame.io | Frame.io JSON Web Token | +| Frame.io | Frame.io Developer Token | +| GitHub | GitHub SSH Private Key | +| GitHub | GitHub Personal Access Token | +| GitHub | GitHub App Installation Access Token | +| GoCardless | GoCardless Live Access Token | +| GoCardless | GoCardless Sandbox Access Token | +| Google Cloud | Google API Key | +| Google Cloud | Google Cloud Private Key ID | +| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | +| Hubspot | Hubspot API Key | +| Mailchimp | Mailchimp API Key | +| Mailchimp | Mandrill API Key | +| Mailgun | Mailgun API Key | +| MessageBird | MessageBird API Key | +| npm | npm Access Token | +| NuGet | NuGet API Key | +| Palantir | Palantir JSON Web Token | +| Plivo | Plivo Auth Token | +| Postman | Postman API Key | +| Proctorio | Proctorio Consumer Key | +| Proctorio | Proctorio Linkage Key | +| Proctorio | Proctorio Registration Key | +| Proctorio | Proctorio Secret Key | +| Pulumi | Pulumi Access Token | +| Samsara | Samsara API Token | +| Samsara | Samsara OAuth Access Token | +| Shopify | Shopify App Shared Secret | +| Shopify | Shopify Access Token | +| Shopify | Shopify Custom App Access Token | +| Shopify | Shopify Private App Password | +| Slack | Slack API Token | +| Slack | Slack Incoming Webhook URL | +| Slack | Slack Workflow Webhook URL | +| SSLMate | SSLMate API Key | +| SSLMate | SSLMate Cluster Secret | +| Stripe | Stripe Live API Secret Key | +| Stripe | Stripe Test API Secret Key | +| Stripe | Stripe Live API Restricted Key | +| Stripe | Stripe Test API Restricted Key | +| Tencent Cloud | Tencent Cloud Secret ID | +| Twilio | Twilio Account String Identifier | +| Twilio | Twilio API Key | diff --git a/translations/zh-CN/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/zh-CN/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index 1c06dc72db319..f6b1f66d1e325 100644 --- a/translations/zh-CN/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/zh-CN/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **注**：您不能对公共仓库禁用默认启用的一些安全和分析功能。 {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/activity-tab.md b/translations/zh-CN/data/reusables/sponsors/activity-tab.md new file mode 100644 index 0000000000000..9983dd101a67a --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/activity-tab.md @@ -0,0 +1 @@ +1. 在左侧边栏中，单击 **Activity（活动）**。 ![活动选项卡](/assets/images/help/sponsors/activity-tab.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/change-tier.md b/translations/zh-CN/data/reusables/sponsors/change-tier.md index 28beec6902a60..7d25b70449f83 100644 --- a/translations/zh-CN/data/reusables/sponsors/change-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![更改等级按钮](/assets/images/help/billing/edit-sponsor-billing.png) +1. 在“{% data variables.product.prodname_sponsors %}”下，在被赞助帐户的右侧，单击等级帐户旁边的 {% octicon "triangle-down" aria-label="The down triangle octicon" %}，然后单击 **Change tier（更改等级）**。 ![更改等级按钮](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/zh-CN/data/reusables/sponsors/no-fees.md b/translations/zh-CN/data/reusables/sponsors/no-fees.md index 9f3119de50a4a..43105753b0e8d 100644 --- a/translations/zh-CN/data/reusables/sponsors/no-fees.md +++ b/translations/zh-CN/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} 不从用户帐户收取赞助费，因此这些赞助 100% 会转到被赞助的开发者或组织。 The 10% fee for sponsorships from organizations is waived during the beta. +{% data variables.product.prodname_sponsors %} 不从用户帐户收取赞助费，因此这些赞助 100% 会转到被赞助的开发者或组织。 在测试期间，组织免除 10% 的赞助费。 diff --git a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md index 56a047d86788f..ee10ac2b03afa 100644 --- a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. +如果您代表您的用户帐户进行赞助，将立即向您收取按比例支付的金额，直到您的下一个常规计费日期。 如果您代表组织进行赞助，可以选择按比例支付金额或按月全额付款。 diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md index e730f9e0a7fb6..1e4d4c446969b 100644 --- a/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md +++ b/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md @@ -1,4 +1,4 @@ -1. Navigate to your sponsorship dashboard for the account. +1. 导航到帐户的赞助仪表板。 - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![赞助按钮](/assets/images/help/profile/sponsoring-button.png) - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![赞助按钮](/assets/images/help/sponsors/org-sponsoring-button.png) 1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md index 28cc3635f65cf..b96c2c47f4d4e 100644 --- a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md +++ b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -You can sponsor anyone with a sponsored developer profile or sponsored organization profile on behalf of your user account or an organization. You can choose from multiple sponsorship tiers, with monthly payment amounts and benefits that are set by the sponsored account. 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。 +您可以代表您的用户帐户或组织赞助具有被赞助的开发者配置文件或赞助组织配置文件的任何人。 有多个赞助等级可供选择，每月支付金额和福利由被赞助帐户设定。 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。 diff --git a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index fb1ca5ec34282..35d15c8f5266b 100644 --- a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file. +如果您创建了不同名称的密钥，或者您要添加不同名称的现有密钥，请将命令中的 *id_ed25519* 替换为您的私钥文件的名称。 diff --git a/translations/zh-CN/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/zh-CN/data/reusables/support/enterprise-resolving-and-closing-tickets.md index 43cfeb7d77eef..989472a569a58 100644 --- a/translations/zh-CN/data/reusables/support/enterprise-resolving-and-closing-tickets.md +++ b/translations/zh-CN/data/reusables/support/enterprise-resolving-and-closing-tickets.md @@ -1,5 +1,5 @@ -{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, {% if currentVersion == "github-ae@latest" %}or {% endif %} workaround instructions{% if enterpriseServerVersions contains currentVersion %}, or by advising you of an available release that addresses the issue{% endif %}. +{% data variables.contact.enterprise_support %} 在提供解释、建议、使用说明、 {% if currentVersion == "github-ae@latest" %}或{% endif %}变通方法{% if enterpriseServerVersions contains currentVersion %}或向您推荐可解决问题的版本{% endif %}后，可能认为事件单已解决。 如果您使用自定义或不支持的插件、模块或自定义代码，{% data variables.contact.enterprise_support %} 可能要求您在尝试解决问题时删除不支持的插件、模块或代码。 如果在不受支持的插件、模块或自定义代码删除后问题得以解决，{% data variables.contact.enterprise_support %} 可能认为事件单已解决。 -{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. 如果 {% data variables.contact.enterprise_support %} 因为未获回复而关闭事件单，您可以请求 {% data variables.contact.enterprise_support %} 重新开启事件单。 +如果事件单超出支持范围，或者多次联系您但未获回复，{% data variables.contact.enterprise_support %} 可能会关闭事件单。 如果 {% data variables.contact.enterprise_support %} 因为未获回复而关闭事件单，您可以请求 {% data variables.contact.enterprise_support %} 重新开启事件单。 diff --git a/translations/zh-CN/data/reusables/support/ghae-priorities.md b/translations/zh-CN/data/reusables/support/ghae-priorities.md index adc143351c5ce..e2a72ac7d55a0 100644 --- a/translations/zh-CN/data/reusables/support/ghae-priorities.md +++ b/translations/zh-CN/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | 优先级 | 描述 | 示例 | |:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

            _After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
            • 影响所有用户的核心 Git 或 web 应用程序功能的错误或中断
            • Severe network or performance degradation for majority of users
            • 用完或快速占用存储空间
            • Known security incidents or a breach of access
            | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
            • 性能下降，影响许多用户的工作效率
            • Reduced redundancy concerns from failures or service degradation
            • Production-impacting bugs or errors
            • {% data variables.product.product_name %} configuraton security concerns
            | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
            • 性能下降，影响许多用户的工作效率
            • Reduced redundancy concerns from failures or service degradation
            • Production-impacting bugs or errors
            • {% data variables.product.product_name %} configuration security concerns
            | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
            • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
            • Issues with user tools and data collection methods
            • 升级
            • Bug reports, general security questions, or other feature related questions
              • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
              • Feature requests and product feedback
              • General questions on overall configuration or use of {% data variables.product.product_name %}
              • Notifying {% data variables.contact.github_support %} of any planned changes
              | diff --git a/translations/zh-CN/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/zh-CN/data/reusables/support/premium-resolving-and-closing-tickets.md index 3412e59b4d7f9..d7f10664b2362 100644 --- a/translations/zh-CN/data/reusables/support/premium-resolving-and-closing-tickets.md +++ b/translations/zh-CN/data/reusables/support/premium-resolving-and-closing-tickets.md @@ -2,4 +2,4 @@ 如果您使用自定义或不支持的插件、模块或自定义代码，{% data variables.contact.premium_support %} 可能要求您在尝试解决问题时删除不支持的插件、模块或代码。 如果在不受支持的插件、模块或自定义代码删除后问题得以解决，{% data variables.contact.premium_support %} 可能认为事件单已解决。 -{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. 如果 {% data variables.contact.premium_support %} 因为未获回复而关闭事件单，您可以请求 {% data variables.contact.premium_support %} 重新开启事件单。 +如果事件单超出支持范围，或者多次联系您但未获回复，{% data variables.contact.premium_support %} 可能会关闭事件单。 如果 {% data variables.contact.premium_support %} 因为未获回复而关闭事件单，您可以请求 {% data variables.contact.premium_support %} 重新开启事件单。 diff --git a/translations/zh-CN/data/reusables/support/scope-of-support.md b/translations/zh-CN/data/reusables/support/scope-of-support.md index 9616375179d03..dc1687efbc957 100644 --- a/translations/zh-CN/data/reusables/support/scope-of-support.md +++ b/translations/zh-CN/data/reusables/support/scope-of-support.md @@ -1,7 +1,7 @@ ### 支持范围 -如果您的支持申请超出了我们团队可以帮助您的范围， 我们可能会提出后续措施建议，以便在 {% data variables.contact.github_support %} 之外解决您的问题。 Your support request is possibly out of {% data variables.contact.github_support %}'s scope if the request is primarily about: +如果您的支持申请超出了我们团队可以帮助您的范围， 我们可能会提出后续措施建议，以便在 {% data variables.contact.github_support %} 之外解决您的问题。 您的支持申请如果主要是关于以下方面，可能超出了 {% data variables.contact.github_support %} 的范围： - 第三方集成 - 硬件设置 - CI/CD，如 Jenkins diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md new file mode 100644 index 0000000000000..ae43f35c1f00c --- /dev/null +++ b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -0,0 +1 @@ +1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md new file mode 100644 index 0000000000000..82cb0fbffeae7 --- /dev/null +++ b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md @@ -0,0 +1 @@ +1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md b/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md new file mode 100644 index 0000000000000..e4908fcf75e15 --- /dev/null +++ b/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md @@ -0,0 +1 @@ +1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/link_email_with_your_account.md b/translations/zh-CN/data/reusables/user_settings/link_email_with_your_account.md index a1fa5e4664081..e09a7fdd228d8 100644 --- a/translations/zh-CN/data/reusables/user_settings/link_email_with_your_account.md +++ b/translations/zh-CN/data/reusables/user_settings/link_email_with_your_account.md @@ -1,4 +1,4 @@ {% if currentVersion != "github-ae@latest" %} -Add the email address to your account on -{% data variables.product.product_name %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)." +将电子邮件地址添加到您在 +{% data variables.product.product_name %} 上的帐户，以便您的提交归因于您并且出现在您的贡献图中。 更多信息请参阅“[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)”。 {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/password-authentication-deprecation.md b/translations/zh-CN/data/reusables/user_settings/password-authentication-deprecation.md index bd247793cef3b..9473f8836c389 100644 --- a/translations/zh-CN/data/reusables/user_settings/password-authentication-deprecation.md +++ b/translations/zh-CN/data/reusables/user_settings/password-authentication-deprecation.md @@ -1 +1 @@ -When Git prompts you for your password, enter your personal access token (PAT) instead.{% if currentVersion != "github-ae@latest" %} Password-based authentication for Git is deprecated, and using a PAT is more secure.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +当 Git 提示您输入密码时，请输入您的个人访问令牌 (PAT)。{% if currentVersion != "github-ae@latest" %} 基于密码的身份验证对 Git 已弃用，使用 PAT 更安全。{% endif %} 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 diff --git a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md index 17110f4cef791..80fb1f9d778dc 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md @@ -1,11 +1,11 @@ -| 键 | 类型 | 描述 | -| --------------------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
              • `created` - 创建了新的检查运行。
              • `completed` - 检查运行的“状态”为“已完成”。
              • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
              • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
              | -| `check_run` | `对象` | [check_run](/rest/reference/checks#get-a-check-run)。 | -| `check_run[status]` | `字符串` | 检查运行的当前状态。 可以是 `queued`、`in_progress` 或 `completed`。 | -| `check_run[conclusion]` | `字符串` | 已完成检查运行的结果。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. 此值将为 `null`，直到检查运行 `completed`。 | -| `check_run[name]` | `字符串` | 检查运行的名称。 | -| `check_run[check_suite][id]` | `整数` | 此检查运行所属检查套件的 ID。 | -| `check_run[check_suite][pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 拉取请求与检查套件匹配的条件是它们有相同的 `head_sha` 和 `head_branch`。 检查套件的 `head_branch` 在复刻仓库中时，它将为 `null`，并且 `pull_requests` 数组将为空。 | -| `requested_action` | `对象` | 用户请求的操作。 | -| `requested_action[identifier]` | `字符串` | 用户请求的操作的集成器引用。 | +| 键 | 类型 | 描述 | +| --------------------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
              • `created` - 创建了新的检查运行。
              • `completed` - 检查运行的“状态”为“已完成”。
              • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 收到 `rerequested` 操作时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
              • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 有关检查运行和请求操作的更多信息，请参阅“[检查运行和请求操作](/rest/reference/checks#check-runs-and-requested-actions)”。
              | +| `check_run` | `对象` | [check_run](/rest/reference/checks#get-a-check-run)。 | +| `check_run[status]` | `字符串` | 检查运行的当前状态。 可以是 `queued`、`in_progress` 或 `completed`。 | +| `check_run[conclusion]` | `字符串` | 已完成检查运行的结果。 可以是以下项之一：：`success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` 或 `stale`{% else %}或 `action_required`{% endif %}。 此值将为 `null`，直到检查运行 `completed`。 | +| `check_run[name]` | `字符串` | 检查运行的名称。 | +| `check_run[check_suite][id]` | `整数` | 此检查运行所属检查套件的 ID。 | +| `check_run[check_suite][pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 拉取请求与检查套件匹配的条件是它们有相同的 `head_sha` 和 `head_branch`。 检查套件的 `head_branch` 在复刻仓库中时，它将为 `null`，并且 `pull_requests` 数组将为空。 | +| `requested_action` | `对象` | 用户请求的操作。 | +| `requested_action[identifier]` | `字符串` | 用户请求的操作的集成器引用。 | diff --git a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md index bb341aa3c0e03..b0eedaf62dbda 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| 键 | 类型 | 描述 | -| ---------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是：
              • `completed` - 检查套件中的所有检查运行已完成。
              • `requested` - 新代码被推送到应用程序的仓库时发生。 When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).
              • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
              | -| `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | -| `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | -| `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | -| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `requested`、`in_progress` 或 `completed`。 | -| `check_suite[conclusion]` | `字符串` | 检查套件中所有检查运行的摘要结论。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. 此值将为 `null`，直到检查运行 `completed`。 | -| `check_suite[url]` | `字符串` | 指向检查套件 API 资源的 URL。 | -| `check_suite[pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 拉取请求与检查套件匹配的条件是它们有相同的 `head_sha` 和 `head_branch`。 检查套件的 `head_branch` 在复刻仓库中时，它将为 `null`，并且 `pull_requests` 数组将为空。 | +| 键 | 类型 | 描述 | +| ---------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是：
              • `completed` - 检查套件中的所有检查运行已完成。
              • `requested` - 新代码被推送到应用程序的仓库时发生。 收到 `requested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。
              • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 收到 `rerequested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
              | +| `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | +| `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | +| `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | +| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `requested`、`in_progress` 或 `completed`。 | +| `check_suite[conclusion]` | `字符串` | 检查套件中所有检查运行的摘要结论。 可以是以下项之一：：`success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` 或 `stale`{% else %}或 `action_required`{% endif %}。 此值将为 `null`，直到检查运行 `completed`。 | +| `check_suite[url]` | `字符串` | 指向检查套件 API 资源的 URL。 | +| `check_suite[pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 拉取请求与检查套件匹配的条件是它们有相同的 `head_sha` 和 `head_branch`。 检查套件的 `head_branch` 在复刻仓库中时，它将为 `null`，并且 `pull_requests` 数组将为空。 | diff --git a/translations/zh-CN/data/reusables/webhooks/installation_properties.md b/translations/zh-CN/data/reusables/webhooks/installation_properties.md index 47269ff43b859..ada5e57ca9030 100644 --- a/translations/zh-CN/data/reusables/webhooks/installation_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | ---------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
              • `created` - 有人安装 {% data variables.product.prodname_github_app %}。
              • `deleted` - 有人卸载 {% data variables.product.prodname_github_app %}
                • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
              • `suspend` - 有人挂起 {% data variables.product.prodname_github_app %} 安装。
              • `unsuspend` - 有人取消挂起 {% data variables.product.prodname_github_app %} 安装。
                • {% endif %}
              • `new_permissions_accepted` - 有人接受 {% data variables.product.prodname_github_app %} 安装的新权限。 当 {% data variables.product.prodname_github_app %} 所有者请求新权限时，安装 {% data variables.product.prodname_github_app %} 的人必须接受新权限请求。
              | -| `仓库` | `数组` | An array of repository objects that the installation can access. | +| 键 | 类型 | 描述 | +| -------- | ----- | -------------------------------------------- | +| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
              • `created` - 有人安装 {% data variables.product.prodname_github_app %}。
              • `deleted` - 有人卸载 {% data variables.product.prodname_github_app %}
                • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
              • `suspend` - 有人挂起 {% data variables.product.prodname_github_app %} 安装。
              • `unsuspend` - 有人取消挂起 {% data variables.product.prodname_github_app %} 安装。
                • {% endif %}
              • `new_permissions_accepted` - 有人接受 {% data variables.product.prodname_github_app %} 安装的新权限。 当 {% data variables.product.prodname_github_app %} 所有者请求新权限时，安装 {% data variables.product.prodname_github_app %} 的人必须接受新权限请求。
              | +| `仓库` | `数组` | 安装设施可访问的仓库对象数组。 | diff --git a/translations/zh-CN/data/reusables/webhooks/member_webhook_properties.md b/translations/zh-CN/data/reusables/webhooks/member_webhook_properties.md index cebd803bbcadb..b62bed51736e4 100644 --- a/translations/zh-CN/data/reusables/webhooks/member_webhook_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/member_webhook_properties.md @@ -1,3 +1,3 @@ | 键 | 类型 | 描述 | | -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
              • `added` - 用户接受加入仓库的邀请。
              • `removed` - 用户被删除仓库协作者角色。
              • `edited` - A user's collaborator permissions have changed.
              | +| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
              • `added` - 用户接受加入仓库的邀请。
              • `removed` - 用户被删除仓库协作者角色。
              • `edited` - 用户的协作者权限已更改。
              | diff --git a/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md b/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md index 8918e36a2cddd..74f22d357bb6c 100644 --- a/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -与组织中被阻止人员相关的活动。 {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. +与组织中被阻止人员相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[阻止组织用户](/rest/reference/orgs#blocking)”REST API。 diff --git a/translations/zh-CN/data/reusables/webhooks/ping_short_desc.md b/translations/zh-CN/data/reusables/webhooks/ping_short_desc.md index bc64c6da5b797..9db7fb883ff11 100644 --- a/translations/zh-CN/data/reusables/webhooks/ping_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/ping_short_desc.md @@ -1 +1 @@ -当您创建新的 web 挂钩时，我们将向您发送一个简单的 `ping` 事件，让您知道您已正确设置 web 挂钩。 This event isn't stored so it isn't retrievable via the [Events API](/rest/reference/activity#ping-a-repository-webhook) endpoint. +当您创建新的 web 挂钩时，我们将向您发送一个简单的 `ping` 事件，让您知道您已正确设置 web 挂钩。 此事件不会存储，因此无法通过[事件 API](/rest/reference/activity#ping-a-repository-webhook) 端点检索它。 diff --git a/translations/zh-CN/data/reusables/webhooks/repo_desc.md b/translations/zh-CN/data/reusables/webhooks/repo_desc.md index e0eca4218dc4d..214d7ec25a5da 100644 --- a/translations/zh-CN/data/reusables/webhooks/repo_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/repo_desc.md @@ -1 +1 @@ -`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred. +`repository` | `object` | 事件发生所在的 [`repository`](/rest/reference/repos#get-a-repository)。 diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index b56a5e817e69a..4a82e2e98eea1 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -4,10 +4,10 @@ header: contact: 联系我们 notices: 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.''' + release_candidate: '# 版本名称是通过 includes/header-notification.html 在以下文本之前呈现：目前可用作发行版候选。更多信息请参阅“关于升级到新版本”。' localization_complete: 我们经常发布文档更新，此页面的翻译可能仍在进行中。有关最新信息，请访问英文文档。如果此页面上的翻译有问题，请告诉我们。 localization_in_progress: 你好，探索者！ 此页面正在积极开发或仍在翻译中。有关最新和最准确的信息，请访问我们的英文文档。 - early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' + early_access: '📣请不要公开分享此 URL。此页包含有关早期访问功能的内容。' search: need_help: 需要帮助？ placeholder: 搜索主题、产品... @@ -57,13 +57,13 @@ contribution_cta: or: 或, to_guidelines: 了解如何参与。 enterprise_releases_list: - title: Enterprise Server Releases - currently_supported: Currently supported - currently_supported_message: See GitHub Enterprise for information about the latest release. - deprecated: Deprecated - deprecated_message: 'These docs remain available but are no longer maintained:' - deprecated_developer: Deprecated on developer.github.com - deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' + title: Enterprise Server 发行版 + currently_supported: 当前支持 + currently_supported_message: 请参阅 GitHub Enterprise 以获取最新版本的信息。 + deprecated: 已废弃 + deprecated_message: '这些文档仍然可用，但不再维护：' + deprecated_developer: 在 developer.github.com 上已废弃 + deprecated_developer_message: '这些文档在旧开发者站点上仍然可用，但不再维护：' products: graphql: reference: @@ -132,3 +132,15 @@ product_landing: quick_start: 快速入门 reference_guides: 参考指南 overview: 概览 +product_sublanding: + start: 开始 + start_path: 开始路径 + learning_paths: 学习路径 + learning_paths_desc: 学习路径是一系列帮助您掌握特定主题的指南。 + more_guides: 更多指南 + guideTypes: + overview: 概览 + quick_start: 快速入门 + tutorial: 教程 + how_to: 操作方法指南 + reference: 参考 diff --git a/translations/zh-CN/data/variables/action_code_examples.yml b/translations/zh-CN/data/variables/action_code_examples.yml index 76dd4ac209f5e..6978c32a73e2a 100644 --- a/translations/zh-CN/data/variables/action_code_examples.yml +++ b/translations/zh-CN/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/zh-CN/data/variables/contact.yml b/translations/zh-CN/data/variables/contact.yml index ff70bf19af0da..b8e54b2b9c599 100644 --- a/translations/zh-CN/data/variables/contact.yml +++ b/translations/zh-CN/data/variables/contact.yml @@ -1,7 +1,7 @@ --- contact_ent_support: '[GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) 或 [GitHub 高级支持](https://premium.githubsupport.com)' contact_support: >- - {% if currentVersion == "free-pro-team@latest" %}[GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://premium.githubsupport.com){% else %}your site administrator{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[GitHub 支持](https://support.github.com/contact) 或 [GitHub 高级支持](https://premium.githubsupport.com){% else %}您的站点管理员{% endif %} report_abuse: >- {% if currentVersion == "free-pro-team@latest" %}[报告滥用](https://github.com/contact/report-abuse){% endif %} report_content: >- @@ -22,8 +22,8 @@ premium_support: 'GitHub 高级支持' enterprise_portal: 'GitHub Enterprise 支持门户' contact_enterprise_portal: '[GitHub Enterprise 支持门户](https://enterprise.githubsupport.com/hc/en-us)' #Azure support (GitHub AE) portal -ae_azure_portal: 'Azure Support portal' -contact_ae_portal: '[Azure Support portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)' +ae_azure_portal: 'Azure 支持门户' +contact_ae_portal: '[Azure 支持门户](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)' #GitHub Support portal (for dotcom) support_portal: 'GitHub 支持门户' contact_support_portal: '[GitHub 支持门户](https://support.github.com/contact)' diff --git a/translations/zh-CN/data/variables/gists.yml b/translations/zh-CN/data/variables/gists.yml index 01b778f1012f0..db6f91bed7e2a 100644 --- a/translations/zh-CN/data/variables/gists.yml +++ b/translations/zh-CN/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist 主页](https://gist.github.com/){% else %}gist 主页，`http(s)://[hostname]/gist` 或 `http(s)://gist.[hostname]`，如果启用了子域 {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist 主页](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist 主页 `http(s)://gist.[hostname)`，{% else %}gist 主页 `http(s)://[hostname]/gist` 或 `http(s)://gist.[hostname]` 如果启用了子域{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist 搜索](https://gist.github.com/search){% else %}Gist 搜索，`http(s)://[hostname]/gist/search` 或 `http(s)://gist.[hostname]/search`，如果启用了子域{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist 搜索](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist 搜索 `http(s)://gist.[hostname]/search`，{% else %}Gist 搜索 `http(s)://[hostname]/gist/search` 或 `http(s)://gist.[hostname]/search`（如果启用了子域）{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}发现，`http(s)://[hostname]/gist/discover` 或 `http(s)://gist.[hostname]/discover`，如果启用了子域{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`，{% else %}Discover `http(s)://[hostname]/gist/discover` 或 `http(s)://gist.[hostname]/discover`（如果启用了子域）{% endif %} diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 74d512c6d4c3e..0a3f340e0f71d 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -20,7 +20,7 @@ prodname_ghe_managed: 'GitHub AE' prodname_ghe_one: 'GitHub One' ## Use these variables when referring specifically to a location within a product product_location: >- - {% if enterpriseServerVersions contains currentVersion %}your GitHub Enterprise Server instance{% elsif currentVersion == "github-ae@latest" %}your enterprise{% else %}GitHub{% endif %} + {% if enterpriseServerVersions contains currentVersion %}您的 GitHub Enterprise Server 实例{% elsif currentVersion == "github-ae@latest" %}您的企业{% else %}GitHub{% endif %} #Used ONLY when you need to refer to a GHES instance in an article that is versioned for non-GHES versions. #Do not use in other situations! product_location_enterprise: '您的 GitHub Enterprise Server 实例' @@ -37,10 +37,10 @@ prodname_unified_search: '统一搜索' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: '教育社区' -prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' +prodname_education_community_with_url: '[GitHub Education 社区](https://education.github.community)' prodname_classroom: 'GitHub 课堂' prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' -prodname_campus_program: 'GitHub Campus Program' +prodname_campus_program: 'GitHub 校园计划' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -66,7 +66,7 @@ prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVer prodname_support_forum_with_url: '[GitHub API 开发和支持论坛](https://github.community/c/github-api-development-and-support/37)' prodname_unfurls: '内容附件' #Azure AD -ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterpriseserver)' +ae_azure_ad_app_link: '[GitHub AE 应用程序](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterpriseserver)' #GitHub Actions ## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more. prodname_actions: 'GitHub Actions' @@ -84,6 +84,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub 赞助者' prodname_matching_fund: 'GitHub 赞助者匹配基金' #GitHub Advanced Security +prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' #Codespaces prodname_codespaces: 'Codespaces' @@ -124,9 +125,9 @@ prodname_vss_ghe: '包含 GitHub Enterprise 的 Visual Studio 订阅' prodname_vss_admin_portal_with_url: '[Visual Studio 订阅的管理员门户](https://visualstudio.microsoft.com/subscriptions-administration/)' #GitHub Dependabot prodname_dependabot: 'Dependabot' -prodname_dependabot_alerts: 'Dependabot alerts' -prodname_dependabot_security_updates: 'Dependabot security updates' -prodname_dependabot_version_updates: 'Dependabot version updates' +prodname_dependabot_alerts: 'Dependabot 警报' +prodname_dependabot_security_updates: 'Dependabot 安全更新' +prodname_dependabot_version_updates: 'Dependabot 版本更新' #GitHub Archive Program prodname_archive: 'GitHub 存档计划' prodname_arctic_vault: 'Arctic 代码库' diff --git a/translations/zh-CN/data/variables/release_candidate.yml b/translations/zh-CN/data/variables/release_candidate.yml index ec65ef6f94453..71234017daf78 100644 --- a/translations/zh-CN/data/variables/release_candidate.yml +++ b/translations/zh-CN/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0